I was struggling to connect to my Raspberry Pi VNC server, it's impossible without RealVNC Viewer, even with turned off encryption. There is vncviewer for Raspbian, but it's for armhf architecture (and for Debian) and is proprietary. The chromium-docker uses Chromium for armhf architecture in docker and it works perfectly on Manjaro, so I've decided to tinker with it.
First you need to download code from @hthiemann docker-chromium-armhf using your favourite method.
https://github.com/HenningThiemann/docke...mium-armhf
Then you will need to modify Dockerfile and dependencies folder to your needs. I would recommend to change ubuntu image to debian by changing FROM line:

Results: ubports/2020-09-30-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. 3G outbound texting worked without issues. I noticed that there were some issues getting all of my carrier settings after initial update. Reboot solved this, but 3g calls were broken today.

Issues:
4G outbound calls broken.
Phone gets stuck in a weird lock state when spamming power button.

When looking at the results of GPS reception by typing in the console

I purchased a rock64 1gig board that includes an lcd module. I want to flash kodi onto an sd card. I still want the lcd to read "kodi box" 
Is there a way that I can make this possible?
Thanks in advance

Hi all.

I'd been running the stock Manjaro 20.08 distro, and somehow in playing around with trying to get sleep to work (Since realized it probably is the magnet positioning) I can no longer boot my Pinebook Pro off of emmc.

In fact, I can't boot it *at all* if the emmc is enabled, even if have a distro that works great if emmc is disabled in the SD slot, like Manjaro 20.08 or mrfixit 2001 debian stretch.

I have a new bigger emmc chip and the emmc to usb adapter coming from HK, but:

A) How could I have gotten myself into such a state? It seems incongruous that you could 'brick' a laptop in this way through software.
B) Is there anything I can do short of replacing the emmc chip?

Thanks in advance. I love the platform and am committed to diving as deep as I need to in order to get going

-Chris

Hi,

I'm interested to develop software for pinephone. I dont know much about the phone.

Sorry if this is the wrong forum, but is there a thread/forum/wiki for developing, not the OS itself, but apps.

I read that pinephone can run Qt5 is this true? Is this the Ubuntu version?

Is it possible, for example, to compile on a desktop pine edition (or otherwise), then copy onto the phone. Ideally, a Qt5 binary.

Thanks for any help to get me started!

I got the RockPro64 yesterday and finally got it up and running with Debian Bullseye. I just thought I'd let people know that it works reasonably well with an HP 560 SFP+ 10Gb NIC using the ixgbe driver. It's limited to 8Gb due to the PCIe bus being 4x but 8Gb is good enough for my needs. 

Just thought I'd confirm that this NIC does indeed work with the RockPro64.

Mod edit: Amended title to reflect that it's in relation to a 10GB NIC

I have been trying to determine what sim cards and carriers will work on the current Pine phone OS releases,

I have tried multiple sim card 'kits' from TracFone and Net 10,  they come with   AT&T,  T-Mobile, and Verizon carrier sim cards.

Verizon sim cards always show "NO SIM CARD"  from both TracFone and Net 10  'sim card kits'   ?

The T-Mobile sim cards take a while "searching"  when looking in the settings >  'Modem'  but they do eventually show a carrier, signal and network type.
  I did activate an account with 'Simple Mobile' (T-Mobile NVMO) that works, but T-Mobile is weak in many of the areas I am in.
    I picked Simple Mobile over TracFone as they offer more service for the same price,   for T-Mobile carrier service.

The TracFone, Net 10/AT&T sim cards do show a sim card but they do not (for me) show a carrier, signal or network type, even waiting over an hour.
   But,  I do have a PMOS Pine phone on an activated TracFone/AT&T account that is working 'ok'.
-------

> I also tested an un-activated  AT&T sim card that was direct, not through an NVMO and it shows a strong signal, carrier, and network type pretty quickly. 

My 'daily driver' Brave Heart phone is running 'very well' on an official  "AT&T Prepaid account"...
-------

Note:  I am semi-rural, so my results may not be typical.

I hope to hear some others mention their experiences with getting Verizon to work..?  NVMO's ?  ?
    ( I personally dislike Verizon, but there are some places,  that is the only carrier )
  ( When Verizon came to Tucson, Arizona, (1980's)  they bought all the existing communication services, and shut them down ) 

-------

While the hardware and software are important to any smart phone,  actually connecting to a carrier is also kind of vital....

* Deals can be had with carriers, but they do prioritize,  The top of the list are the full price consumers on post pay,
  then their direct PrePay customers, at the bottom of the list,  is the discount NVMO customers
   "Check-out Pure Talk NVMO" for some great deals !

So a couple of days ago my pinephone stopped booting into the OS after the Pine64 Logo. Today I tried this fix https://forum.pine64.org/showthread.php?tid=10130 and at first it seemed like it was working, booting into recovery started the installing update screen but about half way through the update my phone crashed and booting into recovery just shows the "awaiting command" screen. I obviously tried to power through with the rest of the fix but after the reboot command the phone still fails to boot.

Is my UBPorts image fucked or is there still a way to recover? If not does anyone have a good guide on how to reflash UBPorts on the Pinephone.

Greeting and Thanks
Defekto

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-29-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. 3G outbound texting is still broken. No audio on outbound calls. Unable to detect Verizon carrier. Interesting set of problems. Seems like there is very little noticeable progress as far as phone feature is concerned at the moment. Phone is running a little hotter than normal. 

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, closed report.
Verizon carrier issues

Other Notes: Although there have been updates outside of the nightly builds, I am close to a point of treating this software as abandon-ware. Lack of response and triage through the teams issue tracker has only made this testing process mildly more frustrating. With that in mind, there are other distros that can support the phone in a much better fashion. I would suggest looking at Manjaro or Mobian. Although both OSes are still alpha.