While a wifi hotspot is useful in a situation where you can plug-in your phone and get fast internet for your computer or laptop Bluetooth PAN is so far the best solution(except usb cable link which ideally will also be packaged for) for mobile users trying to conserve battery power.
This really should be a core optional or bundled packages for not just Mobian but all phosh and plasma builds.
We have a working 100% Debian linux based(Maemo 5) solution here for a system current around 2009 pre-systemd.
https://bugs.maemo.org/Bluetooth_PAN (getting dead link)
https://talk.maemo.org/showthread.php?t=58570

What is required is to install the PAN bluetooth wireless base station bluez service and then create iptables routing and automated DHCP service like we already have in the WiFi service.
here is how it is done with openwrt user firmware routers.
https://openwrt.org/docs/guide-user/hard...th.6lowpan
https://www.multitech.net/developer/soft...pan-setup/

I have gotten the bluetooth PAN service to work once about four years ago on a PP running then current mobian though I had to in the end tunnel using SSH(works like a duct-tape fast socks VPN) to the phone from the client laptop as I had not configured the iptables routing correctly(ssh -D user@pinephoneIPaddress).

Since then I have not been able to replicate the bluez setup of the PAN BT service which is the base component toconnect to everything else.

Hi
in Gnome all works fine

But in SDDM and Plasma i get black rectangle behind mouse indicator/cursor?
Any hints?

Hi, My ppp started being super sensitive to any bumps, or too much pressure on it and I don't know why. if i slightly bump it or barely tap it against something it will immediately stop working and the screen will go blank, I don't think it's completely off because the screen, though black, still is slightly back lit. I've also found that if i even squeeze the phone slightly it does the same thing. I then have to turn it off, and then back on, which is not easy. I have to pop the battery out and back in, shake it, and sometimes tap on the back of it while holding the power button to get it to come back on, and then more often than not, it starts to boot, and then gets stuck, and  I have to repeat the process until it turns back on. im not sure what happened to cause this, I thought at first the battery was not making good contact with the terminals in the phone, but that isnt it. its like something is loose but im not sure where to begin in fixing it, has anyone else had this issue? are there any suggestions? Any help will be very much appreciated as my ppp is pretty much completely unusable right now. Thanks!

Lately I only have the selfie camera as an option, there is no touch switch to choose the main camera.
How do I scan the I2P buss to verify the camera socket is properly seated so I can rule that out?
I did have it unplugged but I dont really want to pent the phone again until my new system board arrives as I dont want to add any stress to the ribbon cables.
Is there a keyboard command to switch cameras?
running mobian trixie until I upgrade to forky

Hi!

I have an old pinephone that I stopped using (due to broken battery pins).

I'm trying to recycle it as a home server, without a battery (I don't want it to catch fire) but:

- Either I plug it using an USB-C charger, it boots, but does not gets Wi-Fi (known behavior), so I'm stuck.
- Either I use the Pinephone convergence dock to use RJ45, but it looks like it lacks power or something as the phone bootloops.

I though about using a voltage regulator to fake the battery BUT I fear the moment the phone tries to "charge" it, lol.

Can someone try to boot its pinephone without a battery and with a convergence dock to see if there's any chance this way?

Or is there another way I missed?

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