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?

https://yro.slashdot.org/story/25/10/31/...ng-details

"Someone recently managed to get on a Microsoft Teams call with representatives from phone hacking company Cellebrite, and then leaked a screenshot of the company's capabilities against many Google Pixel phones,"

"The Support Matrix also shows Cellebrite's capabilities against Pixel devices running GrapheneOS, with some differences between phones running that operating system and stock Android. Cellebrite does support, for example, Pixel 9 devices BFU. Meanwhile the screenshot indicates Cellebrite cannot unlock Pixel 9 devices running GrapheneOS BFU."

Hello,
The PinePhone automatically powers on when plugged in. While I know there are workarounds and suggestions like "using a better charger," I’m not interested in those.

What I’d like to know is:

Is there a command I can enter in the terminal to prevent it from doing that, so it only turns on when I press the power button?

I have a 64 G eMMC that came with my Pinebook pro and I decided to upgrade to 128. I got a new one here from pine64 and also the USB adapter. My plan was to use the USB adapter with the 128 G drive and do a dd copy from the existing drive to the new one, then swap them out. I understand that there may be some UUIDs or some other values I will need to change, but before I start messing around and killing a weekend I thought I would ask around and see if my general plan is sound.

Any problems I should look out for or other friendly advice anyone wants to give?

(I also got the audio-serial adapter to debug things when it DOES go wrong)

Hi,
I have written my first Kivy app for my pinephone running latest mobian. I run it launching it from a console...
I spend half a day wondering how to add an icon for it on my phosh phone and did not found any documentation about that topic.
Do you have any doc or pointer?
Thanks
Jean-Charles

Pinephone received yesterday. Ran it through basic phone and web browser functionality tests.
This phone is apha not beta.
Access to voice and data dropped multiple times.
PO resets and battery removal and replacement to clear.
Other basic functionality such as camera would require a complete overhaul of both SW and HW to even get to minimal functionality . 
Will try to get this not ready for prime time phone returned for refund.

So I'm still playing with my Zig toy OS for PinePhone, and I reached the point where I can draw on screen the A53 CPU core temperature   

Does anyone know what temperatures I need to set for the alarm/shutdown limits please?  It seems to get hot quite fast, although that is probably my code  

I guess I should consider the GPU sensors too, but since I am streaming a framebuffer direct to LCD, I doubt they are doing much temperature wise.

So I'm having trouble with my Pinephone which only worked properly for a day and I'm trying to work out which part I need to replace. Today, I remembered that I had the hub that has HDMI output so I tried booting it with that connected with both the regular install (the preloaded plasma) and the jumpdrive SD card. Neither gave me HDMI output. So the question is, is it supposed to work from boot, which would point to the mainboard being the issue - or not, in which case, I'm still up in the air.

Just to forestall the obvious questions, the phone *is* technically booting. I can see output on the serial console, it gets a DHCP address etc, I just don't get any kind of display on the screen (though the backlight does come on). I don't *think* it's the software (though I'd be happy to be proven wrong) so I think it comes down to the mainboard or the display. I'd be happy to pay for either but don't want to shotgun things.