Howdy All,

I've newly acquired a RockPro64 and an LCD Touch display, this is the first time that I have ever used such devices, so everything is new for me. After discovering that the original eMMC chip I purchased was faulty I'm now having issues with the LCD display. 

The display works fine except that the image displayed is reversed, or flipped along the vertical axis? It's difficult to describe but it looks like I'm looking at the image via a mirror.

Has anyone experienced this issue before? If so, what I am I doing wrong?

I'm using Etcher to flash a 32gb eMMC chip via a USB adaptor on my Mac running OSX 10.14.6. The image I am using is:

ROCKPro64_dd_20200804_stock_android_9.0_emmcboot-32GB.img

The SBC I have is a RockPro64 v2.1 2018-07-02. 

I'm not sure what other details may help troubleshoot this issue, I've run out of ideas...

There is some weird battery issue with this pinecone. Battery level dropped from 88% to 26% in 5 minutes. Feeling the battery temperature with the left hand with the cover off and navigating apps on the phone ( reproduced both with Ubuntu touch and Postmarket OS ) I am feeling the battery getting very hot then dropping back to room temperature as I am navigating apps on the phone. When the battery gets hot, the battery indicator level is visually decrementing percentages as I am looking at the display.

Any other users experiencing this issue?

I am considering getting the PinePhone to complement my PineBook, PineBookPro and PineTab.  I'm absolutely interested in convergence, however I already own a few USB-C adapters that I have used with the Macbook Pro. They all have video (HDMI and/or VGA) and USB and one has gigabit Ethernet. Am I likely to find that these work with the PinePhone, or should I order the convergence package to be certain?

Hello,
Am I missing something here ? I've following the instruction on how to get ubuntu touch on a SD and I always end up with that little red light in the top left of the phone and a black / blank screen. i have the SD Card formatted to FAT32. I'm using Mint 20. I've used the built in writer ( Not sure what the disk imager / writer is called on Mint ) I've simply take the image and drop it into the SD Card and the outcome is still the same.
I assume its me missing a step or something, but don't know what it could be. The SD Card works, I previously used it to put jumpstart on it when I got locked out of my phone. I'm using the PMOS release.

Image used : https://ci.ubports.com/job/rootfs/job/ro...sfulBuild/
Instructions followed : https://gitlab.com/ubports/community-ports/pinephone

I am using a San Disk micro sd 32GB, it's compatible with the the PinePhone as jumpstart worked and copied to it. Sorry trying to list everything I can think of in one post.I think that's it. Any help or suggestions are greatly appreciated.
Thanks !!

Not much concrete information about activating SIM cards. This is how I got lucky and got things to work without too much trouble. I can make and receive calls, send and receive texts, and have 4G data with PMOS. Hope this helps.

1. Bought a Tracfone SIM and plan kit from eBay. I chose the T-Mobile network because Pinephone supports 3 of its LTE bands (2, 4, 12).
   
2. Installed SIM on Pinephone and tried to activate on Tracfone website, but got an error at the IMEI information step.
   
3. Installed SIM on Moto G5S+ and tried to activate, but got the same error.
   
4. Reinstalled SIM on Pinephone and booted.
   
5. Called customer support and successfully activated the SIM through their automated system. It never asked for IMEI information. I never even spoke to an actual human being.
   
6. Rebooted phone.
   
7. Profit.
   

What are the chances of getting a line64 mini arm based computer similar to Apple mini with a arm linux distro for a OS?

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-03-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. Although there were 4 builds between yesterday and today, I didn't notice any improvements directly. Still no outbound SMS on 3g. Still no outbound calls on 4g (volte). Just to note: This seems like an issue with a couple of providers specifically, I am aware that 4G calling (VOLTE) is different between carriers. I make this note because it seems to be debated. If anyone can give help troubleshoot this issue we can pin information on the tickets listed below. Failed 4G calls still kills call audio.

Issues:
Failed outbound 4G calls kills call audio.
Unable to send 3G SMS Since Dev-158
4G outbound calls broken.
Phone gets stuck in a weird lock state when spamming power button.

PostmarketOS convergence edition phone. Software fully up to date. Plugging in the dock shuts off the screen immediately, no matter what is in (or not in) the dock, even if it's empty. Unplugging it immediately restores the display.

When plugging in a basic 4-port USB3 to type C hub I had laying around, the screen dims significantly. Thinking perhaps the screen shuts off when power draw is too high I plugged an LED keyboard into that USB hub, but screen brightness did not change, the keyboard just lit for a moment then shut off.

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: [/url]mobian/09-03-2020-Verizon.html
               mobian/09-03-2020-TMobile.html[url=https://tosstalk.com/pinephone/mobian/2020-08-28-TMobile.html]

[b]Conclusion: [/b]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. Boot time when up to 34 seconds. The UI seems much more glitchy. Its less smooth and apps take forever to open.

I have a Pinebook (not Pro), bought in March. Last week I updated to the current Manjaro-ARM, using wifi to connect to my router. The next day wifi did not work. No access points were visible. The command 'nmcli device wifi' told me that wifi was enabled. How do I find out whether the wifi chip is broken or has simply been disabled (accidentally?) by a privacy switch (if there is one)?