The PinePhone being an open source option to break free from the Apple/Google duopoly is what I've been waiting on for a long time now.  The potential and freedom this platform demonstrates got me to thinking about a more performant version.

My initial list:
SoC: (ARM/Risc-V) Octo Core SoC with ?? GPU TDP ?? watts (ideally PicoRio RISC-V type SoC)
RAM size, speed, type: 4GB
Display: ??
Onboard storage (NVMe): 64GB
Cellular modem: Worldwide bands major providers
WiFi: 802.11ax
Bluetooth: 5
GNSS module: ??
Rear camera MP: 12 wide
Front camera MP: 6
Extra sensors: ?
Extra radios: NFC
Extra switches: NFC
Extra busses: PCIe
Battery form-factor: ??

BOM cost <= $250
Open firmware, or at least a friendly company that is responsive and maintains support.
Manufacturing, sourcing, recycling, and repair goals similar to the Fairphone.
Total cost <= 500


I'd like to pull together a BOM with costs, openness, etc. to see what the off the shelf options are today.  I'd like to see other ideas around what hardware, requirements, and constraints others are interested in.

I was in a phone call yesterday and after what felt like about five minutes the call disconnected seemingly out of nowhere. Looking at the screen of the phone it was black and after pressing the unlock button, the icon that indicates searching for wifi and the cellular connection signal strength bars appeared. I had a feeling that the screen locked itself automatically and in so doing also ended the active call. I went into settings > power > power saving and deactivated "dim screen when inactive" and next to "blank screen" in the drop down menu I choose "never" because to be honest, I have no idea what the difference between "dim screen when inactive" and "blank screen" is.

I called again and after what felt like the exact same ammount of time as before the call just ended. Black screen, unlocked it, wifi icon and cellular connection signal icon appear. I again went into settings and this time I turned off "Automatic suspend".

Now when I called again it lasted for 40+ minutes until I ended the call myself. It would seem to me that I have an issue where automatic suspend activates even while I am in an active call. I guess this activates crust which shuts off cellular and wifi service to save battery. Looking around the forum I havnt found something similar so not sure if its only a problem for me or anyone else. I do remember that I have been making a call longer than five minutes before without autosuspend kicking in so could be something new or maybe just me messing around to much in terminal.

I did see https://wiki.mobian-project.org/doku.php?id=tweaks mentioning prevent suspend and keep the screen on for different apps but I have no idea to implement that on the nmcli. Not really sure what to do from here..

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-09-10-TMobile.html
             mobian/2020-09-10-Verizon.html


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


Notes: The Microphone is still really sensitive. The audio out quality is suffering. Camera still super laggy. Firefox and the settings app are taking 15+ seconds to load. I have noticed that the UI is smoother. Scrolling has improved. Ring Back tone only on TMobile on 3G.

Hi,
I updated my braveheart last night to stable build 6 and I am getting the error message (twice) Failed to add storage device, make sure the storage device device is formated correctly.
I am booting SD card and didn't get this message before.

I am wondering what may be causing this.

Thanks

Ashley

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-09-10-TMobile

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

Notes: Still open to the idea that the camera button is to reverse the image not switch to the 'selfie camera' if anyone can confirm either way I would appreciate it. Failed 4G outbound call still an issue; the failed call no longer kills audio on all other calls. 3G calls are see a little bit of improvement. Able to connect, wasn't getting a count up on call timer. No audio passed either direction. Rebooted phone and tried again, nothing. Good to see some changes going through that portion of the code base though. 3G SMS outbound issue present today. Hopefully the VoLTE fixes are underway.

Issues:
4G outbound calls broken.
Phone gets stuck in a weird lock state when spamming power button.
Outbound SMS over 3g is broken.
Audio cuts out after "No Calls" error is handled on inbound/outbound calls.

Hi all, 

Received my pinetab today and noticed on first boot the top row of the onscreen keyboard was unresponsive and I was unable to enter most things for the setup. Once I got to the desktop I verified that there is a strip that runs the full width that doesn't respond to any touch input. The plastic screen protector also came with a bunch of scratches and fingerprints, removing it did help touch sensitivity somewhat on the rest of the screen but that strip was still dead. On top of that, the keyboard case only a few keys work. I verified with an external keyboard that it can receive those inputs. 

I'm leaning towards a hardware problem (which is a bummer given how long the wait was) but wanted to check to see if anyone else encountered similar and if there's an easy solution. Thanks.

Edit 1: Tested multiple operating systems, problem persists. Screen rotations don't change where the bad strip is. Gotta be a hardware issue, went ahead and submitted a ticket. Am sad.

Edit 2: Attached image to show what I'm talking about. Drawn horizontal lines with gimp roughly covering the possible y-axis points when in landscape mode. Turns out, there's actually two dead strips. When trying to draw in between those two white spots on the bottom input just goes above or below. Sometimes it would cross over due to momentum and gimp approximating things but it's impossible for anything to register inside those bounds

Attached Files

  pinetab_bad_touchscreen.jpg (Size: 232.74 KB / Downloads: 605)

When I press Power to turn the screen off, the touch screen stays active. For example, I turn screen off, scroll down on a black screen, turn screen on to find the bottom of the web page or whatever was opened.

I set "Blank Screen" to Never. The touch screen does not turn off after 25 minutes. Same results when set to 1 minute. I can tap screen, scroll up, then press the PIN keys, THEN turn the screen on and see numbers have been entered into PIN field.

I cat /sys/bus/i2c/devices/1-005d/power/control and get:
auto

I've not confirmed it yet, but my touch screen may never turn off.

Has anyone else found this to be the case?


3GB, Phosh

Linux pine64-pinephone 5.7.0 #3-postmarketos-allwinner SMP Tue Sep 1 15:05:31 UTC 2020 aarch64 Linux

Linux version 5.7.0 (pmos@build) (gcc version 9.3.0 (Alpine 9.3.0), GNU ld (GNU Binutils) 2.34) #3-postmarketos-allwinner SMP Tue Sep 1 15:05:31 UTC 2020

For anyone who wants a cheap mouse for their PBP. Here's my pics https://forum.pine64.org/newthread.php?fid=74  and here is the purchase link https://www.amazon.com/gp/product/B07KNQ...UTF8&psc=1

Hi,

I would like to return and get a refund on my items but the support doesn't want to respect its policy about it, instead they either ghost me or bounce me around sales@pine64.org and https://support.pine64.org. Each claiming it's the other support that deal with this...

During one exchange they even told me to sell my items on ebay, I am still within 15 days the return and refund policy.

Any idea on how to deal with this situation?

Hi folks!
Whats the best place to ask more detailed questions about hardware of Pine products and have them answered by a HW developer? Is there such place?