#mobilelinux

Severe weather in the area recently, and my OnePlus 6T phone running #postmarketos received the cell broadcast alert! Certainly many to thank for this feature being available on #mobilelinux, including @phosh@social.phosh.mobi @postmarketOS@social.treehouse.systems and many more I don't even know. #phosh #duranium

@heiseonline@social.heise.de "Bürger könnten die #App auf ihren #Smartphones nutzen", wenn es Android oder iOS ist. Andere Systeme wie #Mobian oder #postmarketOS sind der @Bundesregierung@social.bund.de egal. Solange das so bleibt ist mir die #EUDIWallet egal 🤷 #MobileLinux #freieSoftware #digitaleSouveränität

BengalOS is now booting on the Pixel 3! 🎉 Just two weeks after @agx@ruhr.social got it running on the Pixel 3a, support is already expanding. Next up: Snapdragon 845 devices, including the OnePlus 6, OnePlus 6T, Xiaomi Pocophone F1, Xiaomi Mi 8, and more. https://bengalos.phosh.mobi/ #BengalOS #Phosh #LinuxMobile #MobileLinux #Pixel3 #sdm845

Weekly GNU-like #MobileLinux Update (30/2026): 24.04-1.4 and -2.0 https://linmob.net/weekly-update-30-2026/ #UbuntuTouch #Jolla #SailfishOS #postmarketOS #FairPhone6 #PinePhone #PinePhonePro #PlasmaMobile #Phosh #Sxmo #LinuxMobile

wow grapheneos people are so insistant on being called a #linuxphone and a part of #linuxmobile initiative.. its like a traditional chess player appearing at a hexagonal Glinsky's chess tournament claiming he knows how to play chess so he should be there! yes, technically android uses the linux kernel and runs on mobile devices, but that doesnt give grapheneos a right to come to #mobilelinux (pine64, postmarketos) party and ask to be treaned as equal. android ecosystem is it's own thing, and mobile linux projects are a completely different thing. theyre not "systemd mobile" either as some do not use systemd there. there is a substantial difference between mobile linux distros and android roms, and i can't imagine what kind of bully you need to be to claim that your android rom has a right to stand in the same row as #linux distros https://grapheneos.social/@GrapheneOS/116975553767986938

In-band deep sleep works now too. That drops the idle power usage when connected to wifi (measured WLAN+BT rail only) from nearly 400mW to 130mW. Still too high compared to downstream, but a big improvement. And while both GPT-5.5 and Claude Opus 4.8 were unable to pinpoint previous issues I've had, Fable 5 did nail it in one prompt. Not sure what to think of that... #mobilelinux #pixel9a

Update: I got the Exynos 5300 modem booting and was able to send a simple text message! Sadly, all very proprietary with no existing integration into e.g. ModemManager #mobilelinux #pixel9a

Mobile data works now with some hacks. I also found the reason for a weird modem crash. The modem requests extra carrier data over a separate oem channel in protobuf format. It retries this a couple of times and while it does, data stalls. And if those requests are ignored for too long, an internal queue fills up until the modem crashes hard #mobilelinux #pixel9a

There we go! Exynos 5300 with custom ModemManager SIT plugin #mobilelinux #pixel9a

YES! I got the full audio pipeline working and the speakers actually sound great now after struggling with it for a couple of days. A prerequisite for audio was the AoC (the always on compute chip). It also provides access to almost all physical sensors. After reverse engineering the USF (googles AoC sensor framework) and bridging it to IIO, Phosh now properly rotates the screen when rotating the device. A couple more weeks and this could be an actually usable phone! #mobilelinux #pixel9a

Oh and speaker safety is also working, so it doesn’t even fry your speakers! #mobilelinux #pixel9a

So something that wouldn’t have been possible without LLMs for me: yesterday I debugged BCM4383 wifi host wake, so the host can almost fully power down the bus and still be reachable. There’s a GPIO that triggers an interrupt when the chip wants to wake the host, but I was unable to get it to be activated. So Claude casually patched the Broadcom firmware (approach from Nexmon) to dump the ROM (not accessible over host memory). Then deassmebled the code. 1/2 #mobilelinux #pixel9a

It quickly found the gate: an IOVAR named host_access (sounds obvious in hindsight) and a check on it actually receiving a D3 interrupt from the PCIe controller. With that, wifi idles between 10 and 30 mW now. Before we were at ~120mW (associated). There’s the possibility to further lower this by completely stopping the PCIe link and fully retrain it on wake, that’s what Android does. It idles wifi between 0 and 6mW (measured on the rail). All of this in ~1h. 2/2 #mobilelinux #pixel9a

You really can’t self host a git forge any more. A couple days ago Meta‘s crawler bombarded my forgejo instance and filled the disk with 500+GB of tar archives. Now I took it down because a fleet of residential proxies tries to crawl the Linux repository. Guess I have to set up Anubis after all or move public repos to GitHub… #mobilelinux #pixel9a

@alienghic@timeloop.cafe @rockario@kind.social I use the #Librem5 as my daily phone. I use the 3.5 mm jack nearly daily to listen to podcasts and internet radio. I really like that the Librem 5 is a full Linux handheld device where I can use all Linux commands, and have full freedom. No AI by default on the Librem 5, no ads, focus on #privacy and #security. It also has three hardware kill switches to disable mic, camera, wifi and bluetooth, and mobile data. #Linux #MobileLinux #opensource #FOSS #PureOS

For some reason I have decided that daily driving the PinePhone Pro for a month is a good idea. With encouragement from the PINE64 community chatrooms, I am prepared to endure this potential pain. For science!!!

Before we get into things, here are some ground rules and boundaries that I wish to lay out for potential readers.

1. My employment requires an app that doesn’t work, even with MicroG. I will have my Android device with me for this reason, but my primary SIM will be in the PinePhone Pro.

2. No Android apps, Waydroid or Android translation layer. I must use native and Flatpak Linux apps.

3. My primary SIM must be in the PinePhone Pro for the duration of the month.

(rules subject to change, I think)

This thread will continue to get updated every day/few days when I can.

Hopefully this goes fine /s

#pine64 #pinephone #pinephonepro #mobilelinux #linuxmobile

Beginning day of daily driving my PinePhone Pro (1) – 18/07/2026 Today I start my journey daily driving the PinePhone Pro for a month. I started by asking abcde and xmn from the PINE64 chatrooms which distro I should use. I personally wanted to use something different so I was personally thinking either Mobian or Arch Linux/DanctNIX. In the end we decided that I will use Mobian with Phosh as the distro I will use for the month. After I finished installing Mobian to the internal storage, I had switched some settings around (pin, timezone, etc). While doing that, I accidentally disabled cellular networking in Gnome settings. Around five minutes after this I tried calling the PinePhone Pro from my main phone and it failed as both devices went to voicemail immediately. I fixed this by rebooting the device, I tested on both PostmarketOS edge and the latest Mobian weekly image afterwards and calls worked no problem. Some initial observations is how hot the device gets from doing nothing. The RK3399S found in the PinePhone Pro is a binned variant of the SOC in the PineBook Pro (less power usage and better thermals). Even after binning, the power usage is high (3.0W-4.0W idle) and the device is constantly hot. While I was setting this all up, it had been around 35 minutes. Battery life went from 70% to 17% within that time. The performance however is good, I am happy with how web browsing and general navigation feel. Web browsing hitches a little bit, but once the page loads scrolling is smooth on Firefox. So far I have installed Tuba for managing the PINE64 community Mastodon on the go, Telegram for online messaging, Speech Note for voice to text notes, Pure Maps for navigation, LocalSend for file transfer and FreeTube for watching stuff. That’s about it, I’m going to bed. See you next log! #pine64 #pinephone #pinephonepro #mobilelinux #linuxmobile #mobian #phosh

Day two of daily driving my PinePhone Pro – 19/07/2026 Day two went well. Mainly because I was at work all day. In the morning I installed "gnome-secrets" to open my KeePass database. Since I was mostly at work today, I didn't use my phone much. Notably, I did receive a call from deep sleep midway through the day. This went through fine, I have not experienced any modem crashing or anything like that today. I need to call my doctor tomorrow morning to book an appointment, so let's hope that all goes well. I will end up getting some actual usage tomorrow on day three. See you then! #pine64 #pinephone #pinephonepro #mobilelinux #linuxmobile

Day three of daily driving my PinePhone Pro – 20/07/2026 Today was the big day and I had a lot of things to do. This time, I used my PinePhone Pro to navigate, which went very well. I noticed that the navigation of the GPS kept up quite well. It wasn't immediate, like you'd find on something like Google Maps on an Android phone, but it was more than usable and I was happy with it. While I was waiting at the doctors I was texting my friend using SMS. I had no issues with this and I had a decent uptime with no modem issues until later in the day (keep reading to find out more!). Unfortunately, I did end up running into some issues today. My haptic feedback, and my sensors for proximity and light detection did not work correctly. I tried to diagnose this issue, but I did not have any luck at all. The best thing that I could do was check I2C and IIO devices in sysfs but I couldn't find anything. I ended up just rebooting device, and that ended up working. So, I'm not sure why that happened. It was quite frustrating to diagnose, and I never actually got to a conclusion. My second big issue today was when my modem just completely stopped being able to make or receive calls. I didn't really know what to do, so I started flashing various ADSP firmwares to no avail. But, after reading many issues and forum posts online, I realized that this is a known issue with later PinePhone Pro models. What I ended up doing was finding a recovery guide for EFS on the modem distro website, which I followed and I had to put in my IMEI number back into the modem. Apparently part of this issue is that your IMEI number just straight up disappears. This took most of my afternoon to diagnose and figure out, I was swapping between a few operating systems on SD cards to make sure things were working again. I think it would be pretty rude of me to leave out what actually fixed my issue in the end in this post. Here’s the link: https://themodemdistro.com/efs_recovery Overall, I would consider this a pretty successful day, albeit with a lot of annoyances. I'm currently still running Mobian/Debian, but I'm also switching between Arch Linux now too. This is going pretty well, I helped Danct12 out with a callaudiod segfaulting issue, a patch has been submitted upstream to hopefully fix this issue. So far, I'm learning that not a lot of things are going to go right for me. I'm hoping that not too many other issues will plague my journey. But, it's only day 3, and I've already been plagued with some tough issues that would deter normal folk or even people with a bit of experience. So, I'm getting a bit worried now as to how many problems I will face. It’s like 3am right now so I’m going to bed. See you on day four! #pine64 #pinephone #pinephonepro #mobilelinux #linuxmobile #danctNIX #mobian

Day four of daily driving my PinePhone Pro – 21/07/2026 Today was pretty relaxing with minimal need to pull out my phone. I only encountered one modem issue where it decided not to show up when I turned on my phone. I decided to restart ModemManager and the modem itself and it came back. Other than that the modem did not crash and I received all of my texts during the day reliably. I checked my Mastodon account using Tuba a couple of times during the day. I have noticed that it runs pretty poorly due to all of the constant post loading it has to do (that’s what I’m assuming). An update on the proximity and light sensors disappearing problem I was having yesterday. I have noticed that it seems to happen randomly. Sometimes they won’t even be initialized at boot. I’m going to take a look at this problem tomorrow in the hope I can find the root of the problem. I know most people don’t care about these sensors but it’s genuinely bugging me. Like why are they randomly dipping? WHY!? RAGHHHH!!! Anyway, sorry for the short one today, not much happened on my phone! (which is probably a good thing) Overall my experience is positive thus far, minus the blaring modem and sensor issues. Battery is currently manageable when I’m not using my phone intensely so I can warm my hands during winter. I’m also using a 20K powerbank to top up on the go when required. One last thing that is peeving me is how the time difference for getting things done between my Android and Linux phone is making me use my laptop a bit more for web browsing tasks. Don’t get me wrong, the performance is fine, but the difference is large enough to annoy me. ALRIGHT! I am going to go to bed at a slightly more reasonable hour this time. I will see you peeeeeeeeps in the next log! *backflips* #pine64 #pinephone #pinephonepro #mobilelinux #linuxmobile