My PP CE reaches about 60 degree while charging. I use there Mobian.

Does somebody else have this issue?

I just went into the local verizon store a few hours ago to activate my Pinephone. I was told that it was not compatible with verizon after they put in the IMEI. I have seen a few other people on the forum using their Pinephone with verizon. Any idea what is going on?

Be aware, these tests are being executed using an out-of-box testing methodology. All tests are preformed with minimal interaction/setup of devices outside of: OS imaging/updating,  SIM installation, Wifi Configuration,  and Power Cycling the devices.

Results: ubports/2020-08-26-TMobile
            ubports/2020-08-26-Verizon

Conclusion: This OS is not ready for the pinephone to become a daily driver.

Notes: A lot better than the previous build. I did have the UI crash while attempting an outbound call.  Inbound text messaging is broken on Verizon. There are some stability issues with this build. Camera still laggy. 

Known issues: 4G Unable to Make calls.
                     Locking gets in stuck state.

If you want to help push some progress begin issuing bugs to the ubports team on gitlab.

So ive had a feel for UB touch and PHOSH. I think UB is pretty great, but i think the PHOSH ui is pretty terrible. Personal preference, admittedly. Plasma looked awesome though. Havent tested it yet because from all the threads here i can infer plasma builds have less working, and devs have stopped working on a lot of them. What's the reason for this? If we could port whats working between Mobian, Arch and UB and put it on plasma we'd have the perfect phone!

Be aware, these tests are being executed using an out-of-box testing methodology. All tests are preformed with minimal interaction/setup of devices outside of: OS imaging/updating,  SIM installation, Wifi Configuration,  and Power Cycling the devices.


Results: mobian/2020-08-26-Verizon.html
              mobian/2020-08-26-TMoblie.html

Conclusion: OS is not Ready for pinephone to be daily driver.

Notes: We starting test MMS messaging. Sadly we failed those tests today. Something i noticed, we started getting a ring back when calling out but only on Verizon. Speaker Phone took a turn for the worst in this build. UI just as responsive as last build.

Hello all,

I have been working on getting Xen EFI working on the RockPro64 with Alpine Linux as a dom0. I have managed to get as far as the initial ramdisk mounting the root filesystem for dom0 but unfortunately that is where I get stuck and I fall into a emergency shell. Listing out /dev I can´t see any block devices to mount:

• Uboot is able to see all storage devices
  
• No storage devices are found including arbitrary usb drives in the initramfs emergency shell
  
• fdisk -l yields no output 
  
• Issue is present on both microsd card and emmc
  
• Attempts to mount the various ramdisks to /sysroot but this fail
  

• All kernels, EFI binaries, initial ramdisks and configuration files must reside on the EFI partition under /EFI/BOOT/
  
• The EFI binary must be named BOOTAA64.EFI 
  
• The EFI configuration file must be named BOOTAA64.CFG
  

I like to be on the edge of developement but most development releases made the Pinephone less usable when I hoped for more. That's why I've been using the RC builds for some time. Still buggy but not strange-sounds-meet-reboots-and-the-clock-is-not-updating-anymore-buggy ;-)

Now Ubuntu touch 6 is available on the RC channel and we've got a working camera out of the box! A working camera, not two. And not working well. The preview picture is reversed and updates very, very slowly. Like point, wait, wait, wait a little more and there is what you're pointing at. The pictures are quite noisy but at least they are the right way around.

Otherwise I don't see big changes. Morph browser still has no private taps, the dialer can't use the + to replace the 0 or 00 in front of the country code and the sound in calls isn't really good. I've included the mounting of my SD card in /lib/init/fstab and the upgrade from 5 to 6 didn't revert this like previous updates did.

Nothing to do with the update content, but im noticing lately several recent updates havent gone all the way through the proper reboot/install process. Many have just crashed, or frozen, and the started upon hard reboot. Probably not too healthy...

I mentioned part of this somewhere before, but it seems to be a recurring problem. However it's gotten more complex. A few times now, after updating im noticing apps ive installed have gone missing. This has now happened 3 times.

Im also noticing every now and then after a fresh boot my phone says its running a previous build from a few days ago even if i just updated a more recent one.

Now I'm starting to wonder if sometimes im booting from SD and updating/installing apps there whereas sometimes im getting booted to eMMC and updating/installing there. 

My understanding is this shouldn't technically be possible, but i also understand that if there's a flip flop in the circuit, previous state could be affected by random conditions which could trigger a decision to boot from one or the other. That said, i haven't found some of my apps that have disappeared regardless of the version it shows im running

Hey everyone,

I'm loving my PBP but one thing I'm struggling with (when switching from my MBP or XPS) is not having a backlit keyboard in the evenings.

I wonder if anyone played around with any kind of mods to make a "backlit keyboard effect"... I was thinking something along these lines: https://www.youtube.com/watch?v=mJoHfzQNK3k but for a laptop.

I know there are these bendy USB LED lights than can stick up on the side of your laptop but I'm wondering if my hands would cast a shadow over most of the keyboard.

Thanks and looking forward to hear your ideas!