I finally figured out how to get around the screen turning off and on with the current version of sailfish. Looks like the issue is the with the light sensor, I found that it would the screen would turn off less often if I angled it just right into some strong light. I was able to get into the settings and turn off the "Adjust automatically" setting in the "Display" settings. Once that was turned off everything worked as normal.

I'm really excited about the PinePhone and look forward to being able to buy one. However, I'll only be able to use it if I can get work email from Exchange or Office 365 (activesync) and possibly the Lyft app for when I'm traveling. Is there a native linux mobile email app that can handle activesync? Will Android emulation be good at handling Lyft? Thank you for any insight you can give.

Suspend stopped working after I installed an NVME drive.  It appears the PBP goes into suspend.   The screen goes black and the led turns red.  However, when pressing the power button the PBP will never wake up again.  I have to hold the power button 6 seconds to reset it and then boot from scratch.
 
The drive I installed was the Intel 660p SSDPEKNW512G8X1 

I am setting power limiting on boot.  I added "sudo nvme set-feature /dev/nvme0 -f 2 -v 2" in /etc/rc.local and have verified that it is setting the feature correctly on boot.

Any ideas how to troubleshoot?  Has anyone else gotten suspend to work with an NVME drive installed?

See here

See here

The RK3399 has hardware for h264 encoding and decoding.
But it looks like the default Debian image doesn't have it activated in the kernel?

I read the wiki: https://wiki.pine64.org/index.php?title=...el_options
When I use this command:
$ zgrep HANTRO /proc/config.gz

Nothing comes up.

Is it easy to compile a new kernel?
Will the future default Debian image come with hardware video acceleration activated?

Got the device, tested everything. Seems the headphone jack wasn't producing sound (From either headphone). Interesting, didn't mind too much because the speaker was working.

However, It seems that Ubuntu Touch is locked in Headphone mode. Not entirely sure if this is because of the OS, or because something in the jack port is locked up.

Any ideas how I should go about troubleshooting this? 


EDIT:

Okay while writing this up i decided to do some logical testing. Silly me forgot about the kill switches on the back. While the headphone switch was on, it was still not producing anything. After killing it I got the tell tale electrical interference sound, so I knew it wasn't a solder issue. When i Re-enabled the switch the audio seem to come back after testing again. 

For anyone landing here from google, or other wise, remember that audio is only produced in the left headphone during the test. This should probably be changed to 'front left' 'front right' 'front left'.

For Ubuntu Touch, it seems it's a OS issue as it worked fine during main testing.

When I downloaded the "0.5 image" linked from the wiki, it was just a tarball from the rootfs (including kernel, but no boot script), I tried copying everything to a ext4 partition, but it did not boot that way. Any hints?

Also if someone could point me to build instuctions that would be awesome.

Hello,

My problem is similar to thread https://forum.pine64.org/showthread.php?tid=8993 but I create this thread to add details specific to my case:

I was able to power up the phone when it arrived and I tested Ubuntu touch and postmarketOS which both are looking promising.
The battery indicator was showing around 20% I think.
I used a raspberry pi to connect to the UART using the headphone jack and I was able to communicate with postmarketOS.
While doing this the phone was plugged in (2A charger)  to let it charge but it did not seem to charge (I do not remember seeing a red light or a charging indicators in the OSes). I though maybe this as a OS bug and maybe it was actually charging.
Then I switched the phone off by typing "sudo poweroff" in the serial terminal, and let off to  charge for a while (still no red light though).

A few hours later the phone does not power up and does not seem to charge (led not turning on).
I also tried to power up without the battery but that does not work either. I know a 3A charger is advised but someone in the chat said 1A is sufficient to boot without the battery, so my 2A charger should work  ?


I will not be able to get a multimeter until a few days, but then I will look at the battery voltage and the power drawn from the usb cable. In the meantime any idea is welcome

Could it be a PMIC problem similar to what can happen on the pinebook when the battery is totally drained ? (https://forum.pine64.org/showthread.php?tid=4632)

Hi,

Any hardware devs able to answer this?

Basically, does the display on the PinePhone use PWM to control brightness?
I hope not! But if so, what's the duty cycle?

Looking at the DTS, it seems it uses Linux kernel's PWM driver(?) to adjust brightness, does that imply PMW at the hardware level or not neccessarly?

Thanks.

PS: Whilst at it, how about the PineTab?