Hello folks, 

I am about to repair the broken screen on my Pinephone that has been sitting in a drawer for years. 

I want to attempt to daily drive. Given that I haven't tested and distro-hopped this device in years, I thought I would appeal to you all for info. 

What is currently the best distro and UI for battery life running phone calls, texts, and perhaps GPS. 

For background, I have no issue with using a command line. I am looking for function over bells and whistles. Calls, text, working GPS is a plus but not required. 

Also remind me, Wifi will drain more than cellular data? 

Thanks for your time.

The installation was installed via a debian mobian-installer image close to a year ago.
There were over 600 packages to upgrade, previous upgrade was about 30 days prior.
The upgrade process took quite some time, done over ssh.
At least two times during this process, my network dropped and I restarted the upgrade.
The upgrade did finish without any errors.

When I attempt to boot now, the screen goes blank and this message appeared at the top of the screen.

I just received my new Pinephone, after a week-long struggle with DHL. I purchased the Pinephone in order to have a device for which I can source replacement parts, but the debacle with DHL makes me think that idea is impractical.

At best, the phone is unusably slow at nearly all tasks except making and receiving calls. With the factory image running, no updates could be installed (first for unspecified unresolved dependencies, and then because PackageKit kept crashing).  "Discover" app takes >1m to start.

With PostmarketOS installed to sdcard, the phone sort-of works, and was able to make and receive phone calls, which is almost all I care about (apart from replacement parts, and the nice-to-have of other basic phone operations). It still takes "Software" app takes <20sec to start, "Shattered Pixel Dungeon" took about 40min to install and about 15sec to start.

Everything is clunky, stuttery and slow. The phone eats battery and gets warm for no apparent reason; the case does not fit well; the speaker makes constant snapping, popping noises. It is expensive junk. I cannot afford another phone, and time taken to fix this one's constant breakage (assuming I can get it "working" from the current state) takes away time I need for other things.

Apps don't work well on Pinephone, none of the repositories have phone apps. Apps don't sleep when the screen locks. I was exited to install Shattered Pixed Dungeon, because I thought it was the Android version. Silly me, thinking a Linux device could run Android apps!

The phone is not currently at its best: I tried to install TowBoot and messed up: now TowBoot Installer is installed to the eMMC and will not leave. I tried the instructions at https://tow-boot.org/devices/pine64-pinephoneA64.html to remove the boot partition data, but the installer still comes up when I boot the phone, sdcard or no sdcard. I will write another card and fix this, but it's not great.

I don't know what to think. Nothing I read on these forums prepared me for how crap this phone is, at this late date.

I guess I'm not looking for advice, just venting. I wouldn't know what to ask.

Since we use towboot we can access our filesystem and fix stuff as needed
After an upgrade which seems to throw a fake 0% and shutdown command at bootup no matter what the battery charge level or plugged in status is;
I am looking for the file which flags shutdown at 0% battery, my battery is charged but now the OS thinks it is dead and will not see charging even done under towboot blue light mountable disk mode.
I have looked at (edited out my local machine to show location in PPp mobian trixie) these files

Hello Everybody,

I have a Pine Time which was (slightly) bricked, in that it had 1.5.0 on it, a mistake when I should have put 1.15.0 on it. So as it was just $26, I bought another one. When it arrived I put it on charge and waited until it had 68% charge. But it would not do anything, so I put it back on charge. I waited until it had 100% charge and then I was able to use it. I put 1.15.0 on it and it works!

So, I wondered, what about the old pine time? I put it on charge and waited until it was at 100%. Then I used Siglo on my Pine Phone and it not only paired, but allowed me to put 1.15.0 on it! So I now have 2 pine times and I thought that this would be usefull to anybody like me who was just stuck!

Chris Burmajster

Hi

Im creating an OnScreen Gamepad for linux for touch devices like pinephone or linux tablets:

This is my repo:
https://github.com/paju1986/VirtualJoy

I consider it already usable for playing games on touch devices.

Hi all. The M.2 accessory for the Pinebook Pro is no longer available from the Pine64 Store. Has anyone come across similar parts that may work?
For example is their such a thing as a flexible cable and M.2 card holder? As the Pinebook Pro is older hardware now, the suppliers may not be interested in replacing these original parts.
It would be nice if a new Pinebook was released with updated hardware, but Pine64 seems to be occupied with other things.

Hello all,

If you are currently "stuck" on an operating system that can only use up to Python 3.8 and are trying to use the img2logo python script to create your own custom boot logos for IronOS, you may find yourself staring at the following error in your console after trying to run the conversion:



This "'type' object is not subscriptable" error occurs because type annotation was added in Python 3.9 and is not present in 3.8 and earlier versions. Thankfully the fix is incredibly simple and does not require changing the part of the code doing the actual work. All you need to do is add a single line at the very top of the file:

Has the keyboard case for the PinePhone Pro been discontinued? It shows up as out of stock and I can't find anywhere that carries it.

Thanks!

Apache NuttX RTOS is officially supported on Avaota-A1 Arm64 SBC (Allwinner A527 SoC). Let’s take Unicorn Emulator and create a Software Emulator for Avaota SBC...

(1) We call Unicorn Library to create our Barebones Emulator

(2) Emulate the 16550 UART hardware by intercepting I/O Memory

(3) Recompile NuttX with 4 Tiny Tweaks and boot on Unicorn

(4) NuttX makes a Context Switch and fails

(5) Because Unicorn doesn’t handle Arm64 SysCalls?

(6) No worries we’ll Emulate Arm64 SysCalls ourselves!

(7) By jumping into the Arm64 Vector Table

(8) NuttX on Unicorn boots to NSH Shell! (Almost)

(9) How exactly does NuttX boot on Avaota SBC? We have a Detailed Boot Flow

Why are we doing this?

-- So we can create NuttX Drivers and Apps on Avaota SBC Emulator (without the actual hardware)

-- Avaota Emulator is helpful for NuttX Continuous Integration, making sure that all Code Changes will run correctly on Avaota SBC

-- The Trade Tariffs are Terribly Troubling. Some of us NuttX Folks might need to hunker down and emulate Avaota SBC, for now.

-- Or maybe we should provide Remote Access to a Real Avaota SBC? ?

Check out the article: https://lupyuen.org/articles/unicorn4.html



Lup