Welcome, Guest
You have to register before you can post on our site.

Username
  

Password
  





Search Forums



(Advanced Search)

Forum Statistics
» Members: 29,303
» Latest member: jackleen
» Forum threads: 16,143
» Forum posts: 116,676

Full Statistics

Latest Threads
Third-party cheap touchsc...
Forum: PinePhone Hardware
Last Post: mikeb
4 hours ago
» Replies: 2
» Views: 772
eMMC failed
Forum: Pinebook Pro Hardware and Accessories
Last Post: Der Geist der Maschine
4 hours ago
» Replies: 17
» Views: 12,032
(real) Mainline U-boot fi...
Forum: General Discussion on ROCKPRO64
Last Post: aleksei
Today, 06:21 AM
» Replies: 0
» Views: 46
Thoughts after a year wit...
Forum: General Discussion on Pinebook Pro
Last Post: ksosn
Yesterday, 03:00 AM
» Replies: 0
» Views: 69
Pinebook Pro in EU for Sa...
Forum: General Discussion on Pinebook Pro
Last Post: shelfaberrant
06-19-2025, 02:14 AM
» Replies: 4
» Views: 2,533
Axolotl on PinePhone / Mo...
Forum: Mobian on PinePhone
Last Post: zetabeta
06-19-2025, 01:52 AM
» Replies: 222
» Views: 237,596
touchscreeh doesn't accep...
Forum: PinePhone Pro Hardware
Last Post: teekay
06-19-2025, 01:13 AM
» Replies: 5
» Views: 444
Wake-up call
Forum: General Discussion on PinePhone
Last Post: KC9UDX
06-18-2025, 08:38 PM
» Replies: 9
» Views: 621
bookworm vs trixie discus...
Forum: Mobian on PinePhone
Last Post: anonymous
06-17-2025, 06:27 AM
» Replies: 64
» Views: 20,859
VoIP account on mobian di...
Forum: Mobian on PinePhone
Last Post: j_s
06-15-2025, 04:19 PM
» Replies: 0
» Views: 86

 
  Issues with Biktorgj Custom Modem Firmware
Posted by: JadenSki - 12-11-2024, 04:32 PM - Forum: General Discussion of PinePhone Pro - Replies (4)

So I recently decided to install Biktorgj's Custom Modem Firmware on my ppp, as it said in the documentation, there is no reason not to, and only added benefit. I installed it using this guide. After the installation, everything seemed to work fine (eg. sms, calls...). I then tried to communicate with the modem using sms as is described here. My messages didn't send, however, and I never received any responses. I also discovered a weird bug where my audio and mic will completely stop working for calls. I cannot hear or be heard by the other phone. Also when I check my voicemail, I hear no audio either. I don't know for sure if the firmware is causing the issue or not, but, it didn't happen until after the installation. Rebooting does not seem to do anything, however, it will randomly start working again before it quits once again. Any insight or advice on these issues will be greatly appreciated. I am currently running the latest stable version of Mobian with Posh. Thanks in advance!


  Mobian, Suspend, and Audio Playback
Posted by: biketool - 12-11-2024, 12:56 AM - Forum: Mobian on PinePhone - No Replies

I have had a pocket linux device in use since around Y2k starting with a Sharp Zaurus SL-5500 on to an Openmoko, then the N900.
One of the most important purposes of these devices was to play audiobooks when driving, cycling, working, or riding public transportation.
On all other devices I was able to get at least 5-8 hours of audiobook playback minimum along with other uses of the device, even with the Openmoko which like the Pine devices didn't have a major corporate Linux lab supporting the effort.
The pinephone(and pro) under mobian gives me around 3 hours maximum as suspend also kills off audio playback.
This severely limits my use of the PP if I cannot provide external power.
I know there are several ways to except the hardware audio acceleration chip from suspend and buffer only the audio stream as well as waking only one of the smaller CPUs for a fraction of a second to do a disk read and reload the audio buffer.
I am not sure how it was done on the N900 but I am sure someone on the forum has better insight into a power saving way to keep a streaming audio app working even when the system is in suspend, even if it is a lower level system hack.
<edit>
For example I can go most of the day dropping to ~80% battery if I don't use my phone much, I can still reliably receive calls and SMS but have it set to suspend after 1 minute. Same Mobian Trixie install drops to 30-40% after 2 hours if I set suspend to 30 minutes but blank the screen so I can listen to an audiobook on the bus/train. Once the 30 minutes are up if I have not touched the phone the audio playback will stop and I have to restart the Cozy(flatpak install) audiobook app to get it's audio to work.


  Booting Issues
Posted by: Halfgreek - 12-10-2024, 08:13 AM - Forum: PineNote Software - Replies (17)

I just receved my new PineNote 2 days ago with Debian installed and was working well with it until I woke up yesterday and the device will not boot into anything, The display remains at "Booting..." or "PineNote is Booting" and i am unable to get to Uboot or anything to see what I can do to fix it. Any Suggestions?


  pine64 gpio interrupts
Posted by: fractal - 12-09-2024, 07:43 PM - Forum: General Discussion on PINE A64-LTS / SOPINE - No Replies

Not sure if this is a general question or a linux question but here goes.

I am coming back to a project after an extended interruption -- life got in the way of my play.

I have a number of GPS units running on a variety of hardware.   The board I use for most of them is also allwiner based and run the same armbian as the pine64.  But, I like pine64's as a general purpose board and have several on my desk so decided to track down why I couldn't get them to work the way I wanted last time.

That background information is not particularly normative but it offers some background.  You don't need any special hardware to reproduce this issue.

My notes from many years ago says there was a post on IRC which confirmed we can not get interrupts from some of the GPIO banks.    I can no longer find that reference but that seems to be true.

I can confirm that

Code:
overlays=pps-gpio
param_pps_pin=PH9

in armbianEnv.txt works with dmesg containing

Code:
[Mon Dec  9 23:58:56 2024] pps pps0: new PPS source pps@0.-1
[Mon Dec  9 23:58:56 2024] pps pps0: Registered IRQ 100 as PPS source

I can also confirm that

Code:
overlays=pps-gpio
param_pps_pin=PC8

in armbianEnv.txt fails with dmesg containing

Code:
[Tue Dec 10 00:04:25 2024] pps-gpio pps@0: failed to map GPIO to IRQ: -22
[Tue Dec 10 00:04:25 2024] pps-gpio: probe of pps@0 failed with error -22

I got as far as https://github.com/torvalds/linux/blob/m...pio.c#L175 returning -EINVAL (-22) where I found it using deprecated functions to get the interrupt so it might just be something to do with the pps-gpio client.

The board that pps-gpio likes has pin 12 of the pi2 bus going to gpio PA6 whereas the pine64 connects pin 12 to gpio PC8 -- different banks on controller 0.

Anyway, for the question - are GPIO's on bank C expected to be able to generate interrupts?   If so, I'll queue further investigation.   Otherwise I'll limit my selection to pins in the PH bank, or use the euler bus.


  Pinepower suitable for an s23 (and a pinecil)
Posted by: its_lieseeeee - 12-09-2024, 01:41 PM - Forum: General Discussion on Pinecil - No Replies

Sorry if this is really obvious but I'm looking at buying a pinecil and a pinepower 65w unit. Just wondered if I could get the 25w super fast charge through the power supply. Doesn't have to be at the same time as the phone, it'd just streamline things having one psu for both


  Pine Phone in Australaa and Telstra
Posted by: tracyanne - 12-05-2024, 03:22 AM - Forum: General Discussion on PinePhone - Replies (2)

Does it work?


  Pinephone compatibility with Telstra, now that 3 G shutdown and 5 G available
Posted by: tracyanne - 12-04-2024, 10:53 PM - Forum: General Discussion on PinePhone - No Replies

I'm trying to find out Pinephone and or Pinephone pro have any issues now that Telstra has shut down 3 G networks.


  Can't complete update of manjaro: wwan0 stays disabled; no phone/text
Posted by: gilford - 12-04-2024, 12:21 PM - Forum: General Discussion on PinePhone - Replies (3)

I started an upgrade and am unable to complete it.


To even see the relevant iface (and confirm it failed to grab an IP), I had to do

Code:
ifconfig wwan0 up
ifconfig wwan0


The modem is "disabled", and I do not know how  to enable it.

Code:
mmcli -m any | grep state
           |                   state: disabled
           |             power state: off
           |    packet service state: detached
nmcli r wifi on
mmcli -m any | grep state
           |                   state: disabled
           |             power state: off
           |    packet service state: detached


Now, my PPP lacks phone and internet .

Everything other than the modem (including WiFi, but not bluetooth, which I will comment on separately if need be) seems fine, so far.

Here is what I see when I answer the default Y, to all save libgpiod,

Code:
:: libgpiod1 and libgpiod are in conflict. Remove libgpiod? [y/N]
error: unresolvable package conflicts detected
error: failed to prepare transaction (conflicting dependencies)
:: libgpiod1 and libgpiod are in conflict
Answering Y, gives,

Code:
:: libgpiod1 and libgpiod are in conflict. Remove libgpiod? [y/N] Y
error: failed to prepare transaction (could not satisfy dependencies)
:: removing kcoreaddons breaks dependency 'kcoreaddons' required by kdav2
:: removing kcoreaddons breaks dependency 'kcoreaddons' required by kimap2
:: removing kcontacts breaks dependency 'kcontacts' required by kpeoplesink
:: removing kpeople breaks dependency 'kpeople' required by kpeoplesink
:: removing kcontacts breaks dependency 'kcontacts' required by sink
:: removing kcalendarcore breaks dependency 'kcalendarcore' required by sink


When I try to remove the culprits, I have the following.

Code:
looking for conflicting packages...
warning: removing 'libgpiod' from target list because it conflicts with 'libgpiod1'
:: libgpiod1 and libgpiod are in conflict. Remove libgpiod? [y/N] y
error: failed to prepare transaction (could not satisfy dependencies)
:: removing kcoreaddons breaks dependency 'kcoreaddons' required by kdav2
:: removing kcoreaddons breaks dependency 'kcoreaddons' required by kimap2
:: removing kcontacts breaks dependency 'kcontacts' required by kpeoplesink
:: removing kpeople breaks dependency 'kpeople' required by kpeoplesink
:: removing kcontacts breaks dependency 'kcontacts' required by sink
:: removing kcalendarcore breaks dependency 'kcalendarcore' required by sink
From the forum, I found

New PinePhone user issues - https://forum.pine64.org/showthread.php?...#pid123017

Pacman update cannot resolve plasma-mobile dependencies. · Issue #75 · manjaro-pinephone/plasma-mobile · GitHub — https://github.com/manjaro-pinephone/pla.../issues/75

I recently posted something as detailed as possible about this on the pine64 forum: (See above)

https://forum.pine64.org/showthread.php?...#pid123017

To sum up:

You need to delete all foreign packages at once with the following two commands:

pacman -Qmq > list.txt

pacman -R - < list.txt

(Be careful to sort out the packages that have been installed by the user from the AUR)

Then, of course, you need to remove the orphaned packages.



So guided, I tried removing each of the culprits. (I did not want to remove anything not required.)



Code:
pacman -R kcoreaddons
checking dependencies...
error: failed to prepare transaction (could not satisfy dependencies)
:: removing kcoreaddons breaks dependency 'kcoreaddons' required by kactivities
:: removing kcoreaddons breaks dependency 'kcoreaddons' required by kalk
:: removing kcoreaddons breaks dependency 'kcoreaddons' required by kauth
:: removing kcoreaddons breaks dependency 'kcoreaddons' required by kcontacts        <--SHOULD DO 2nd
:: removing kcoreaddons breaks dependency 'kcoreaddons' required by kcrash
:: removing kcoreaddons breaks dependency 'kcoreaddons' required by kdav2
:: removing kcoreaddons breaks dependency 'kcoreaddons' required by kdesignerplugin
:: removing kcoreaddons breaks dependency 'kcoreaddons' required by kfilemetadata
:: removing kcoreaddons breaks dependency 'kcoreaddons' required by kimap2
:: removing kcoreaddons breaks dependency 'kcoreaddons' required by kjobwidgets
:: removing kcoreaddons breaks dependency 'kcoreaddons' required by knotifications
:: removing kcoreaddons breaks dependency 'kcoreaddons' required by kpackage
:: removing kcoreaddons breaks dependency 'kcoreaddons' required by kpeople
:: removing kcoreaddons breaks dependency 'kcoreaddons' required by kpipewire
:: removing kcoreaddons breaks dependency 'kcoreaddons' required by kpty
:: removing kcoreaddons breaks dependency 'kcoreaddons' required by krecorder
:: removing kcoreaddons breaks dependency 'kcoreaddons' required by kservice
:: removing kcoreaddons breaks dependency 'kcoreaddons' required by kweather
:: removing kcoreaddons breaks dependency 'kcoreaddons' required by qmlkonsole

pacman -R kcontacts
checking dependencies...
error: failed to prepare transaction (could not satisfy dependencies)
:: removing kcontacts breaks dependency 'kcontacts' required by kpeoplesink    <--REMOVE WITH kpeople, 1st
:: removing kcontacts breaks dependency 'kcontacts' required by kpeoplevcard    <--REMOVE WITH kpeople, 1st
:: removing kcontacts breaks dependency 'kcontacts' required by libkgapi
:: removing kcontacts breaks dependency 'kcontacts' required by plasma-dialer
:: removing kcontacts breaks dependency 'kcontacts' required by plasma-phonebook
:: removing kcontacts breaks dependency 'kcontacts' required by sink
:: removing kcontacts breaks dependency 'kcontacts' required by spacebar

pacman -R kpeople
checking dependencies...
error: failed to prepare transaction (could not satisfy dependencies)
:: removing kpeople breaks dependency 'kpeople' required by calindori
:: removing kpeople breaks dependency 'kpeople' required by kpeoplesink
:: removing kpeople breaks dependency 'kpeople' required by kpeoplevcard
:: removing kpeople breaks dependency 'kpeople' required by plasma-mobile
:: removing kpeople breaks dependency 'kpeople' required by plasma-phonebook
:: removing kpeople breaks dependency 'kpeople' required by plasma-workspace

    MUST COMBINE WITH REMOVAL OF kcontacts
pacman -R kcalendarcore
checking dependencies...
error: failed to prepare transaction (could not satisfy dependencies)
:: removing kcalendarcore breaks dependency 'kcalendarcore' required by calindori    <--REMOVE WITH kpeople, 1st
:: removing kcalendarcore breaks dependency 'kcalendarcore' required by libkgapi
:: removing kcalendarcore breaks dependency 'kcalendarcore' required by sink        <--REMOVE WITH kcontacts, 2nd


With the information above, I attempted to remove kpeople.

Code:
pacman -R kpeople
checking dependencies...
error: failed to prepare transaction (could not satisfy dependencies)
:: removing kpeople breaks dependency 'kpeople' required by calindori
:: removing kpeople breaks dependency 'kpeople' required by kpeoplesink
:: removing kpeople breaks dependency 'kpeople' required by kpeoplevcard
:: removing kpeople breaks dependency 'kpeople' required by plasma-mobile
:: removing kpeople breaks dependency 'kpeople' required by plasma-phonebook
:: removing kpeople breaks dependency 'kpeople' required by plasma-workspace
I grew suspicious here. I found hard to believe that pacman considered plasma-mobile to be foreign

plasma-mobile

Code:
pacman -Qmq | grep plasma-mobile
gave no matches.

NOTA BENE: the above post makes no mention of this dependency when it says  to remove all foreign packages.

Clearly, such is not possible on my system.

Daunted, I continued for completeness.

Code:
pacman -R kpeople calindori kpeoplesink kpeoplevcard plasma-mobile plasma-phonebook plasma-workspace plasma-mobile-nm plasma-dialer plasma-pa plasma-wayland-session plasma-wayland-session powerdevil systemsettings
checking dependencies...
error: failed to prepare transaction (could not satisfy dependencies)
:: removing kpeoplevcard breaks dependency 'kpeoplevcard' required by kdeconnect
:: removing systemsettings breaks dependency 'systemsettings' required by plasma-desktop
:: removing powerdevil breaks dependency 'powerdevil' required by plasma-desktop
No. Way.

I find myself in an absurd situation: an upgrade knocked out the modem.



How may I disentangle this Gordian Knot, and at least restore my modem,

ideally, complete the upgrade?


  Suspend functionality broken?
Posted by: grump_fiddle_reinstall - 12-04-2024, 01:24 AM - Forum: Mobian on PinePhone - Replies (4)

I have a PinePhone and a Pro both updated fully (as far as I am aware) running mobian/Phosh and mobian/Phosh + mobian/XFCE respectively.

In the last week it appears that suspend functionality is now broken.

Both seem to sleep but when I try to wake them after they have been suspended overnight both have drained their batteries and I have to charge them for a few minutes before booting,

Has anyone else noticed a similar change in the suspend functionality?


  Manjaro plasma mobile Wifi
Posted by: Uturn - 12-04-2024, 12:58 AM - Forum: PinePhone Pro Software - Replies (2)

Manjaro plasma mobile (edge) disconnects Wifi every seconds, asking again for WPA password. Somehow given passwords do not seem to get stored where they should or something... Also in the wifi setings trying to connect results in recurring a password popup. Is there a way to fix that behaviour?

Actually, wifi connects but immediately disconnects, system messages *no secrets were provided* followed by a new request for WPA password.