11–20 of 28 posts
Question for any US-based PinePhone aficionados: what carrier are you using (where/how did you get a SIM card)? I recently got an ATT pre-paid SIM (that I was planning on putting in an Android phone eventually). I thought I would give it a try in the PinePhone just to see what happens and found that it would not activate... (Note that this was just a normal pre-paid SIM direct from ATT and not from some 3rd-party MNV…
Question for any US-based PinePhone aficionados: what carrier are you using (where/how did you get a SIM card)? I recently got an ATT pre-paid SIM (that I was planning on putting in an Android phone eventually). I thought I would give it a try in the PinePhone just to see what happens and found that it would not activate... (Note that this was just a normal pre-paid SIM direct from ATT and not from some 3rd-party MNV…
I use t-mobile. The SIM they sent me worked out of the box.
General info is documented at https://wiki.pine64.org/wiki/PinePhone_Carrier_Support
Can anyone who has extensively tried out most of the available distros for PinePhone comment on how close any of them are to a "daily driver" state? I suspect they're all still far from it but it'd be interesting to know which are worth keeping an eye on.
Instead, please ask what it is you want the phone to do, and then people can give you a clear answer.
Can anyone who has extensively tried out most of the available distros for PinePhone comment on how close any of them are to a "daily driver" state? I suspect they're all still far from it but it'd be interesting to know which are worth keeping an eye on.
Can anyone who has extensively tried out most of the available distros for PinePhone comment on how close any of them are to a "daily driver" state? I suspect they're all still far from it but it'd be interesting to know which are worth keeping an eye on.
I just received my PinePhone (not the pro one), and buying the SD card later today to try out this demo image (hence I posted it here as I came across it :) ). Can leave a status report once I've tried them out. Even from before trying it out, seems I'll try at least the updated images of the Majaro Phosh as I've heard it's the most stable and responsive one of the bunch, together with the Arch Linux Arm edition. The…
Earlier quoted context omitted.
Honestly none of them will be daily driver ready, given how broken the Quectel EG25 modem is. I would never want to, have to call emergency services with my Pinephone while the modem is down
Have you tried replacing the modem firmware? The community firmware is supposed to be much more stable.
For me the Quectel firmware was very stable whereas the OSS firmware wasn't. "Stable" as in it would periodically crash, but would come back on its own within a minute. The OSS firmware would also crash but would usually not come back until a reboot.
This was with v0.5.5 IIRC. It seems to have gotten better since the 0.6.x versions of the OSS firmware.
Really the bigger reason to switch to the OSS firmware is that there's a privilege escalation vulnerability in the Quectel firmware that IIRC they still haven't fixed. In any case even if they fixed it in a new firmware release you wouldn't hear about it to know you should install it, whereas the OSS firmware is now being distributed through fwupd so it could be almost as mindless as updating your distro.
Question for any US-based PinePhone aficionados: what carrier are you using (where/how did you get a SIM card)? I recently got an ATT pre-paid SIM (that I was planning on putting in an Android phone eventually). I thought I would give it a try in the PinePhone just to see what happens and found that it would not activate... (Note that this was just a normal pre-paid SIM direct from ATT and not from some 3rd-party MNV…
Question for any US-based PinePhone aficionados: what carrier are you using (where/how did you get a SIM card)? I recently got an ATT pre-paid SIM (that I was planning on putting in an Android phone eventually). I thought I would give it a try in the PinePhone just to see what happens and found that it would not activate... (Note that this was just a normal pre-paid SIM direct from ATT and not from some 3rd-party MNV…
Can anyone who has extensively tried out most of the available distros for PinePhone comment on how close any of them are to a "daily driver" state? I suspect they're all still far from it but it'd be interesting to know which are worth keeping an eye on.
Previously I used SXMO and Mobian. SXMO is fun to script. I got tired of having to script everything after a while. Mobian works out of the box. But they don't have the newest software, so I switched to Arch.
Can anyone who has extensively tried out most of the available distros for PinePhone comment on how close any of them are to a "daily driver" state? I suspect they're all still far from it but it'd be interesting to know which are worth keeping an eye on.
Every time this topic comes up I have to remind people that the definition of "daily driver" is different for everyone. I've been daily-driving the phone for a year without problems because it does everything I need it to do. That doesn't mean you'd have no problems with it. Instead, please ask what it is you want the phone to do, and then people can give you a clear answer.
+ phone call audio quality is as good as some cheapo Android phone I can buy at Walmart, across all the distros in this multi-distro image
I mean, you have a report above that the Pinephone can't even achieve that. (And worse, the user is considering diving into ALSA configuration to fix this!)
If it's true that a phone device cannot be depended on to achieve bog standard audio quality for a phone call, then the player isn't ready to fight in the "daily driver" quest.
I'm willing to write a command line prog that plays the Legend of Zelda secret discovery melody and prints your comment when the the Pinephone achieves bog standard "phone-ness."