Opened my phone to check connectors (re issue https://forum.pine64.org/showthread.php?tid=10882).
Freed the inner frame around the edges only to discover that it is fused to the motherboard at an area next to the battery connectors.
https://www.flickr.com/photos/185472830@...ed-public/
Coincidently(?) this area is where the usb ribbon cable passes to the SOC. Presumably this could also relate to my usb issue? The frame sits normally flat so hasn't been distorted.
https://www.flickr.com/photos/185472830@...ed-public/
Is heating recommended to help removal? Otherwise removal might be destructive.

When trying to install the openstore https://open-store.io I get the following output

mobian@mobian:~/Downloads$ pkcon install-local --allow-untrusted openstore.openstore-team_3.2.1_armhf.click -v
11:59:39 PackageKit          Verbose debugging enabled (on console 1)
11:59:39 PackageKit          filter=(null), filters=0
11:59:39 PackageKit          adding state 0xaaaabf619ca0
11:59:39 PackageKit          doing install files
11:59:39 PackageKit          role now install-files
Installing files              [                        ] (0%)  11:59:39 PackageKit          notify::connected
                              [                        ] (0%)  11:59:39 PackageKit          using frontend dialog
11:59:39 PackageKit          using socket in /tmp/gpk-53_dbdadbae.socket
                              [=========================]       
Testing changes              [=========================]       
Finished                      [                        ] (0%)  11:59:40 PackageKit          remove state 0xaaaabf619ca0
                              [=========================]       
Fatal error: Could not find package(s)

Does anybody know what I am doing wrong?

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-28-TMobile

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

Notes: Alright, after a couple weeks off, I was hoping for some different results. I guess not; 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. 3G outbound texting is still broken. No real Progress.

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. - Unable to replicate this one at this time, but it is still an issue.

I'm not booting from sd card. Tried copying and pasting the updat_sh in terminal after downloading the files but still not working. Am I doing something wrong.

My PBP makes a regular, intermittent, quiet but audible, whining/buzzing sound. It goes about 4 seconds on, 4 seconds off. I started noticing it today, but I'm not sure if it started today. It's irritating enough that I've been playing music to cover it up, but that's not an ideal long-term solution.

Any thoughts?

What is the pre order deadline for the Manjaro OS PinePhone date?

Simple question I know. But I can't seem to find an answer for it here?

Hi all!

So a makepkg of moonlight-qt works pretty well (https://aur.archlinux.org/packages/moonlight-qt/). I adjusted the version to 2.2.0 and got a working package.

It even streams from another machine on my home network, but that's where my success kinda ends. Streaming at 1080p/60fps seems to be just too much given the software-based decoding from ffmpeg. Even though I've run the hardware acceleration patching scripts from the pbp-tools repo (https://github.com/xmixahlx/pbp-tools), the streaming client still can't pick up the available devices:

Hey all,
I'm currently trying to get a 1GB R64 up and running with the Rooted Android 9.0 image and things have been going pretty well, but I do have an issue I'd like to cover here before I try to make any serious changes and that issue is with the Pluto TV app.
 Let me first explain that I already have the PlutoTV app installed on a 1GB R64 with the Android 8.0 image. I installed PlutoTV onto it from the Google Play store, which I installed through the ADB, as suggested in another post on this board.

My current project is the 1G-Rock64 with the following
Image: ROCK64_dd_20190618_stock_rooted_android_9.0_emmcboot-16GB.img.gz (using Etcher to program 16GB eMMC)
Google Play Services: version 20.36.15 (080406-333172415)
Google Services Framework: Ver: 9-6475783
Google Play store Ver: 21.9.47-21[0][PR]331897675
At this point everything seems to be working well, as Play store works. I also had to figure out to unplug the keyboard and use the on screen keyboard to input the wireless password but the apps I've tried so far work. Except for Pluto.
Pluto, as loaded from the Play store gives the following error:
 INCOMPATIBLE VERSION
The installed APK is not compatible with this device. Please download a supported version from Google Play.

My question(s) are: Has anyone else had this issue with this app, on this image? Could this be an issue with the image, or that it's not the AndroidTV version? Should I load the un-rooted image (ROCK64_dd_20190617_stock_android_9.0_emmcboot-16GB.img.gz ) to correct this issue? I truly don't mind having to reload this card with another image, the question is more about saving myself a bit of time testing another image, because this one had been going well so far.

Sincerely,
Deanne

I've been using the newly-arrived PBP, usually plugged in. In some sessions, the charge indicator drops below 100%, but still says it's charging. If that's true, it suggests that the wall-wart is unable to charge the machine at the rate it uses power. (Modest use, nothing dramatic.)

Is this a software problem, a failing unit, or is it an indication that a more puissant charger might be a good idea?