After the battery of my Pinebook (non-Pro) 14" had a swollen battery I removed it from the case.
But now it seems that it cant boot completly, becuase when armbian IoT (trixie) does start I firstly get some good startup messages and then it does reset and restart in u-boot ans then try to boot armbian trixie again

My Battery is a WTL-400110175 with 7 cables (3x red (PB+) , 3x black (PB- / GND) and in the middle a white or yellow cable (PCM / Overvoltage?)

Did anyone get the normal Pinebook to boot completly without a battery?
Or has anyone build a "new" battery from the old connector and a new 10.00mAh cell?
Something like this: https://www.n11.com/urun/1260110-37v-100...a-87767963
because I couldnt fine only a new battery far away from me for the Pinbook Pro (also 7 Pin)

Thanks for Info in advance

   

   

   

Like the title says, I ran apt dist-upgrade and now I get no automatic touch keyboard on any app.
I checked that the touch virtual keyboard was enabled in the mobile settings, holding the line on the bottom just caused it to wiggle left and right like a failed login box in some distros.
It will probably be back in a day or two though I don't like being without and would like an easy way to force the touch keyboard.

I'm selling my 2020 model ANSI(US keyboard) Pinebook Pro. No issues and everything works as expected. Very low usage.
For anybody in Southern California, local pick up only in Thousand Oaks, CA. I won't ship it.
Send me a direct message if you are interested.
Thanks.

I downloaded mobian-sunxi-plasma-mobile-13.0.[img.bmap|img.xz|sha256sums|sha256sums.sig] from https://images.mobian.org/sunxi/ and failed to verify the signature.

I'm working on a custom OS in Zig for the PinePhone v1.2b.  I am struggling to find some documentation on various parts of the hardware.  Today the compass.  I tried the I2C address for the AKM compass, and no response, so I am hoping I have the VTC compass, otherwise my TWI1 code is doing something very wrong 

But I dont have the I2C address, and the documentation linked from the component page on the wiki has expired.  Can anyone shed some light on this please.  A good start would be the I2C address, but a copy of the data sheet would be best please.  I am unable to decode linux source tree structure to find this.

Also, are the PinePhone sensors always powered, since DLD01 seems to be used everywhere.  For the LCD and touch I had to switch on some pio pins, but I dont see that on schematics, only EINT pins.  Iḿ worried about power usage from unused sensors.
I am used to following @lupyuen  amazing tutorials, but I think he focuses more on new devices and didnt cover the sensors

I have a Pine64 PineTab2 device. I have accidentally destroyed the Linux kernel on it, and there is no way to boot into Linux. However, I can access U-Boot. What should I do to install Arch Linux ARM with U-Boot only?

By the way, I am not familiar to U-Boot commands. Are there any suggestions for installing Arch Linux ARM? (especially U-Boot commands)

This newly released operating system outperforms FydeOS's ecosystem with broader support and is specifically designed for low-power PCs.

Hi,
I wrote a Kivy app on my mobian pinephone (phosh). Main screen is just 3 buttons and a label.
If I switch to another app, the touches on the display are still sent to the kivy app. 
Even if the display is turned off, the touches on the black display are sent to the kivy app...
Is that behavior expected?
How to avoid this?
Best,
Jean-Charles

Hello,

https://medium.com/@mathias-steiner/mobi...9dd60aee42

Ciao
Walter

Now as easy as sudo pacman -Syu
Try it out, Bluetooth is now active for me, paired my BT mouse and it works!

No cameras yet...
I am also trying to get a USB NMEA receiver to work for in-car navigation.
_____________________________

So this will allow use of bluetooth stylus as a touch mouse with left-click now?
If so which styluses are compatible?
________________________
is this driver/hardware currently compatible with BT-low energy?