| Welcome, Guest |
You have to register before you can post on our site.
|
| Latest Threads |
OpenClaw
Forum: Linux on Rock64
Last Post: keithy
Yesterday, 11:57 AM
» Replies: 0
» Views: 25
|
Wi-Fi Issues (Plasma and ...
Forum: Manjaro on PinePhone
Last Post: krissprat73
02-20-2026, 12:16 PM
» Replies: 11
» Views: 17,885
|
installed devuan 5/6 - mi...
Forum: General Discussion on ROCKPRO64
Last Post: kapqa
02-20-2026, 11:36 AM
» Replies: 0
» Views: 76
|
Powering two disks from R...
Forum: RockPro64 Hardware and Accessories
Last Post: some_pinephone_user
02-19-2026, 09:31 PM
» Replies: 2
» Views: 159
|
How many HD's can I utili...
Forum: RockPro64 Hardware and Accessories
Last Post: some_pinephone_user
02-19-2026, 06:10 PM
» Replies: 4
» Views: 3,474
|
Official Debian support!
Forum: News
Last Post: kapqa
02-18-2026, 12:58 PM
» Replies: 86
» Views: 190,650
|
Pine 64 Mount hole Dimens...
Forum: General Discussion on PINE A64-LTS / SOPINE
Last Post: Piney64
02-18-2026, 11:27 AM
» Replies: 0
» Views: 89
|
Replacement battery for P...
Forum: Pinebook Pro Hardware and Accessories
Last Post: mexsudo
02-18-2026, 07:24 AM
» Replies: 4
» Views: 5,433
|
StarPro64 Irradium (based...
Forum: Getting Started
Last Post: mara
02-18-2026, 03:46 AM
» Replies: 15
» Views: 7,690
|
broken?
Forum: Pinecil Hardware and Accessories
Last Post: excitedfermion
02-17-2026, 06:55 PM
» Replies: 2
» Views: 2,195
|
|
|
| Any fix for bluetooth crash when entering pairing password? |
|
Posted by: kk22 - 06-18-2022, 07:51 PM - Forum: Mobian on PinePhone
- No Replies
|
 |
This has been an issue I've noticed for ~1 year: if entering a password to pair with a bluetooth device, the password entry dialog will crash almost as soon as it displays, and the selected device will be lost while the phone scans for available bluetooth devices again.
The fact that this apparent issue hasn't been fixed for so long tells me this may just be something specific to my installation. Is there a fix for this?
|
|
|
|
Open box, upgrade, dead watch? |
|
Posted by: ahaplesshappenstance - 06-18-2022, 07:18 PM - Forum: General Discussion on PineTime
- Replies (5)
|
 |
Hi all,
Received my first 2 sealed PineTimes today. One I was able to open, sync to, upgrade and is operating happily (it is SO COOL!)
The second however:
Powered on when I placed it into the cradle to charge (from PC USB port). I connected to it, began the upgrade process (Infinitime 1.6 -> Infinitime 1.9), and got called away. Returned hours later, grabbed the cradle+PineTime from the computer and began commute home. But: I cannot wake the screen. The device appears dead - screen is black/no backlighting, and unresponsive (I've tried holding the button for durations ranging from a single click to >60 seconds; no apparent change in state).
Did I somehow break it? Is there a timeout to successfully completing InfiniTime upgrades? Is it a DOA unit?
I tried searching online (although not yet in the Discord chats) but didn't find anything related to this sort of problem.
Any advice please is welcomed, thanks
|
|
|
|
| Can't connect to cellular network |
|
Posted by: phytocube - 06-18-2022, 05:20 PM - Forum: General Discussion on PinePhone
- No Replies
|
 |
I have an Airvoice SIM card* I've been trying to get to connect, but it's not working. NetworkManager seems to detect it properly and lists the correct SIM ID and even reports that the carrier is AT&T. I've tried using both "reseller" (no quotes) and "NXTGENPHONE" (no quotes) as the APN, but it never successfully connects. Here is some of my journalctl output matching /modem/i:
Failure mode 1: roaming-in-location-area-not-allowed
Code: eg25-manager[2963]: GNSS assistance upload step (2/9): disabling GNSS engine through ModemManager
ModemManager[3180]: <info> [modem0] simple connect started...
ModemManager[3180]: <info> [modem0] simple connect state (4/8): wait to get fully enabled
ModemManager[3180]: <info> [modem0] simple connect state (5/8): register ModemManager[3180]: <warn> [modem0] network reject indication received
ModemManager[3180]: <warn> [modem0] service domain: ps
ModemManager[3180]: <warn> [modem0] radio interface: umts
ModemManager[3180]: <warn> [modem0] reject cause: roaming-in-location-area-not-allowed ModemManager[3180]: <warn> [modem0] network reject indication received
ModemManager[3180]: <warn> [modem0] service domain: cs
ModemManager[3180]: <warn> [modem0] radio interface: umts
ModemManager[3180]: <warn> [modem0] reject cause: roaming-in-location-area-not-allowed
eg25-manager[2963]: Modem is up for 120 seconds and fully ready
Failure mode 2: no-suitable-cells-in-location-area
Code: ModemManager[3180]: <info> [modem0] simple connect started...
ModemManager[3180]: <info> [modem0] simple connect state (4/8): wait to get fully enabled
ModemManager[3180]: <info> [modem0] simple connect state (5/8): register
NetworkManager[3086]: <warn> [1655592789.5434] modem-broadband[cdc-wdm0]: failed to connect modem: Network timeout
ModemManager[3180]: <info> [modem0] simple connect started...
ModemManager[3180]: <info> [modem0] simple connect state (4/8): wait to get fully enabled
ModemManager[3180]: <info> [modem0] simple connect state (5/8): register
ModemManager[3180]: <warn> [modem0] network reject indication received
ModemManager[3180]: <warn> [modem0] service domain: cs-ps
ModemManager[3180]: <warn> [modem0] radio interface: lte
ModemManager[3180]: <warn> [modem0] reject cause: no-suitable-cells-in-location-area
Failure mode 3: plmn-not-allowed
Code: ModemManager[3180]: <info> [modem0] simple connect started...
ModemManager[3180]: <info> [modem0] simple connect state (4/8): wait to get fully enabled
ModemManager[3180]: <info> [modem0] simple connect state (5/8): register
ModemManager[3180]: <warn> [modem0] network reject indication received
ModemManager[3180]: <warn> [modem0] service domain: cs-ps
ModemManager[3180]: <warn> [modem0] radio interface: lte
ModemManager[3180]: <warn> [modem0] reject cause: plmn-not-allowed
ModemManager[3180]: <warn> [modem0] network reject indication received
ModemManager[3180]: <warn> [modem0] service domain: cs-ps
ModemManager[3180]: <warn> [modem0] radio interface: lte
ModemManager[3180]: <warn> [modem0] reject cause: plmn-not-allowed
ModemManager[3180]: <warn> [modem0] network reject indication received
ModemManager[3180]: <warn> [modem0] service domain: cs-ps
ModemManager[3180]: <warn> [modem0] radio interface: lte
ModemManager[3180]: <warn> [modem0] reject cause: plmn-not-allowed
Failure mode 4: No MCC/MNC or operator id:
Code: ModemManager[3180]: <info> [modem0] simple connect started...
ModemManager[3180]: <info> [modem0] simple connect state (4/8): wait to get fully enabled
ModemManager[3180]: <info> [modem0] simple connect state (5/8): register
ModemManager[3180]: <info> [modem0] 3GPP registration state changed (idle -> searching)
ModemManager[3180]: <info> [modem0] state changed (enabled -> searching)
ModemManager[3180]: <warn> [modem0] couldn't load operator code: Current operator MCC/MNC is still unknown
ModemManager[3180]: <warn> [modem0] couldn't load operator name: Current operator id is still unknown
NetworkManager[3086]: <info> [1655594076.4347] modem["cdc-wdm0"]: modem state changed, 'enabled' --> 'searching' (reason: unknown)
modem-daemon[3725]: kf.modemmanagerqt: Unknown Mobile Country Code: 0
kscreenlocker_greet[3475]: kf.modemmanagerqt: Unknown Mobile Country Code: 0
plasmashell[3548]: kf.modemmanagerqt: Unknown Mobile Country Code: 0
ModemManager[3180]: <info> [modem0] 3GPP registration state changed (searching -> idle)
- Do I need to issue modem commands manually to troubleshoot/fix this? I don't know how to do this, having relied on NM/MM so far; if it is, what's the best way to do this?
- Am I just not in the service area? I somewhat doubt this because I'm in a relatively densely populated area, but what I can understand from searching the reject causes suggests this might be the case. (I'm reluctant to switch to other providers mostly because I haven't found any prepaid plans less than 3x as expensive, but if it can't be avoided...)
* Compatibility unknown per the wiki
ADDENDUM:
Per this thread, it appears AT&T is no longer a viable carrier for PinePhones: https://forum.pine64.org/showthread.php?tid=15988
|
|
|
|
| apt-get update "The following signatures were invalid..." |
|
Posted by: grump_fiddle_reinstall - 06-18-2022, 04:19 AM - Forum: Mobian on PinePhone
- Replies (13)
|
 |
From the terminal
"The following signatures were invalid: EXPKEYSIG 951D61F2BC232697 Mobian Project <admin@mobian-project.org>
Reading package lists... Done
W: An error occurred during the signature verification. The repository is not updated and the previous index files will be used. GPG error: http://repo.mobian-project.org bookworm InRelease: The following signatures were invalid: EXPKEYSIG 951D61F2BC232697 Mobian Project <admin@mobian-project.org>
W: Failed to fetch http://repo.mobian-project.org/dists/bookworm/InRelease The following signatures were invalid: EXPKEYSIG 951D61F2BC232697 Mobian Project <admin@mobian-project.org>
W: Some index files failed to download. They have been ignored, or old ones used instead."
I remember having similar problems with other repos but cannot find the fix. Where can I find the new key?
|
|
|
|
| digitizer dead |
|
Posted by: Uturn - 06-18-2022, 01:56 AM - Forum: PinePhone Hardware
- Replies (1)
|
 |
since quite a while, I realize my pinephone does not accept the letter Y on the onscreen keyboard. This happens in Manjaro Plasma mobile, and also in Postmarket OS SXMO. The screen is delaminating. Could this be a hardware related problem, or is it a software thing?
|
|
|
|
| Hardware switch for the PPKB battery? |
|
Posted by: theResonant - 06-17-2022, 04:25 PM - Forum: PinePhone Accessories
- Replies (3)
|
 |
Has anyone opened up their PPKB to add a hardware kill-switch for its battery? This way, the USB port of the phone could be used safely (when the switch is off).
Would this make sense?
Alternatively, a slider-switch could be added to the back of the phone, made accessible from the outside (by drilling), which would slide under the Pogo pins that feed power from the battery, disconnecting them when desired.
No matter how it's done, it really looks like the battery inside the PPKB needs some sort of hardware switch. This way, it will truly behave as what it really is: a powerbank, not just an extra battery. A powerbank which you manually connect and disconnect, and charge separately on its own port.
|
|
|
|
| Compatible replacement battery for the Pinephone Pro |
|
Posted by: tpoacher - 06-17-2022, 03:13 PM - Forum: PinePhone Pro Accessories
- Replies (3)
|
 |
As of the time of writing this post, the official pinephone lithium battery is out of stock.
The wikipage to which the above page redirects to (namely this one) says:
Quote:The supplied battery is meant to be compatible with Samsung part number EB-BJ700BBC / BBE / CBE from the 2015 J7 phone. The extended life aftermarket BBU does fit, although it is a tight fit.
Based on the above, I went ahead and purchased a Samsung EB-BJ700CBE battery.
However, this is a REALLY tight fit in the phone. If you wedge it in enough, it fits, but it feels to me like there is a lot of pressure on the battery from the case.
E.g., it is impossible to get the battery out with your nail alone; I had to get a spoon and use it as a lever over the side of the case, to even get the battery to get unstuck enough to pull it out. And when you cram it in, it's so tight you can see part of the covering over the battery 'crinkle' a little bit.
I'm very reluctant to use this battery, despite the fact that I can, in theory, "cram" it in; to me that sounds like a recipe for trouble somehow. Samsung batteries have enough of an 'explosive' reputation even in the absence of undue pressure on the battery as it is ...
Has anyone else had any experience with this battery? Is it safe to use despite the tight fit?
If my worries are not unwarranted, does anyone recommend any other battery which fits a bit more reasonably?
Better yet, is the official Pinephone lithium battery expected to be back in stock anytime soon?
Many thanks
|
|
|
|
|