I am curious to hear from you the longest you had your Librem/Liberty phones up without restarting, while having it fully functional.
The longest I’ve managed while using Waydroid was 1,5 day.
Without Waydroid, 6 days.
2 Likes
I don use Waydroid and will never do.
Since the kernel fix was installed, it’s again many days:
purism@pureos:~$ uptime
09:25:23 up 3 days, 3:11, 2 users, load average: 0.27, 0.20, 0.09
2 Likes
Usually the only reason I reboot is either working on the kernel or having the battery go flat. Due to the former, my current uptime is exactly 1.5 day and it seems that in the last week (which is as far as my journal goes) I only managed to get 2 days before booting into a different kernel 
I used to keep one Librem 5 docked in the past and that one reached uptimes in months.
1 Like
Wow.
I’d always reach one of the three situations:
- the wifi card would not work, even after restarting network services or turning it off via hardware key switch, waiting a minute, then restarting it.
- modem data connection would not work, even after power-cycling the modem
- millions of zombie processes (waydroid), even after force quitting every single android application from within waydroid
The first problem only bothers me when I am abroad. At home, I am always on data. The problem was still happening as of my last long stay abroad last month.
The second problem stopped happening after upgrading the modem firmware.
The third problem is still with me. When I go out and I know I can’t risk running out of battery, I restart the phone just to be sure waydroid won’t prevent standby, giving me a nicely warmed bag from within.
I wish I didn’t need Android.
And yes, the docked Librem 5 is lovely. It does 120Hz @ 1080p very nicely on my OLED, and even 4K but very choppy 24 Hz, and the CPU is not very happy at 4K. The Librem 5 is NEVER slow, unless you need to access the Bloatnet.
1 Like
Is there any reason you keep the container running when not needed? waydroid session stop. “Force quitting every single Android application” doesn’t sound like a very convenient or effective method 
There’s also a way to configure it to stop the container automatically when no Waydroid window is open, though I do it manually to be sure it’s done anyway.
I’m generally not having problems with the modem nor WiFi that can’t be solved with power cycling them. In cases when I do, it’s usually a deeper problem with the kernel, but kernels 6.6.40 and now 6.6.83 have been rock solid for me so far.
1 Like
Hum, as I’m usually not able to start charging my phone while it’s turned on, I often have to shut down the phone, plug the charger and turn it back on. So in general my uptime is a couple of hours at most 
1 Like
Because of heat? Is there some process going haywire with the CPU perhaps? What about system suspend? These days my phone rarely overheats, usually only when I use it for an extended time in the summer while in a poorly climate-conditioned train or something like that 
1 Like
No, it seems it doesn’t notice the charger at all, the red light doesn’t come up.
I wrote about that in another post last December.
It’s not the heat because when it refuses to charge because of heat it at least starts blinking the red light. And anyway nowadays in central Europe it’s sometimes just a couple degrees above freezing and the phone is cold. And sometimes when it’s charging properly, if I unplug and replug the charger immediately, it doesn’t resume charging until next power cycling.
I tried suspending and plugging the charger when it’s suspended, but it doesn’t register either.
It all started happening after that day me and my Librem 5 got caught into the rain, USB port facing up in my raincoat pocket, so I suspect the USB board suffered water damage. DP alt mode is also mostly broken. And even when it does charge, it needs something like one hour to increase the battery level by 10% if the phone is turned on, screen off, doing nothing.
1 Like
Do this then:
Knowing how the phone reacts to these scenarios, I’ll likely be able to give you some advice to make your life with that phone easier.
1 Like
Ever since (fixed) LTE connectivity lost very often - #17 by pi-rp my need to reboot my phone is virtually gone.
Kernel updates and I reboot. Occasional wonkiness (phone gets in a weird state sometimes where apps take forever to respond or open, but this is really rare) and I reboot. Battery dies, and I reboot 
But that’s it. The phone stays on many days at a time now.
1 Like
Oh sweet summer child…
I have a desktop icon that calls a script to stop waydroid session, then sleep a bit, then stop the waydroid service. I realize my phone is not going into suspend, so I try to restart and I see the dreadful “WAYDROID IS INHIBITING IDLE” message, and I want to jump off the window.
Then I try experimenting force quitting every single Android application and I still see the same problem.
Then I take my phone out of my bag. It is warm. 30% of the battery are gone. Then I fire terminal, launch top, run ps aux, and I conclude that there’s nothing out of the ordinary, so why is my phone warm?
Then I start troubleshooting it, dig into DBus shenanigans, curse the fates, and realize that I just hate modern software.
I hate that my stupid camera exposure application, that has literally 400 lines of C code and does less than 20 math operations on demand, launching literally 5 GTK Widgets, compiles to a multimegabyte binary and takes 15MB of RAM to run and takes 8 seconds to launch.
Then I look into the nightmares of systemds, dbuses and all the stupid crap that is everywhere, and why the hell does it take gigabytes of RAM to boot to desktop.
Then I turn my HP 712 60 MHz on, with nextstep 3.3, and I realize it is the most responsive computer I own. I launch a few text editor windows, spreadsheet, 3-4 SSH sessions, get my actual work done and hate every single operating system and computer released after year 2000.
Then I wonder whether it is too much to task that MY computer does what it is supposed to do. Open the stupid program, run it. Close ALL child processes when I am done. No telemetry. No background daemons. No bizarre interprocess communications. Be a tool. No “We are getting your computer ready”. Who is we? You are a stupid computer.
Give me a proper progress bar, show me what processes are running and what files are being written. Stop trying to pretend to be a stupid human. Be a tool. Let me do my job. Don´t load 10MB of code to show me 1KB of the text I actually want to read.
Then I realize what absurd it is that a phone with 4x 1.5GHz cores and 3GB struggles sometimes to scroll a few lines of text with a image, and I think: well, it is really not the phone.
Then I feel like moving to a cave and throwing every single electronic appliance I own out of the window, for disrespecting my time, my money and the environment.
and ugh, rant over.
2 Likes
It is very similar to my case… When after a week of active use together with Nexdock I lost the ability to screen sharing and normal charging. Now I have only one charger that works with one orientation with the special usb-c cable 
.
Hopefully, I just received the USB-C board for repair that I asked from Purism support and going to replace on this weekend.
Another issue that limits my uptime is the display problem. However, it looks like I managed to fix it by configuring i2c restore routine in the dts file. So, I hope already on the next week I have no reason for reboot my phone 
1 Like
The Android image I’m using is still from before idle inhibition has been added there, so I had avoided this bug entirely. I get it that it’s frustrating, though it’s not necessary to reboot to drop that inhibitor - restarting phosh session would be enough. But now it’s best to simply apply the recent patch for phoc
1 Like
That happened to me as well, so I got the usb board replaced
1 Like
What patch? The only fix I know is the improvement you mentioned in the other thread.
It has actually crossed my mind to restart phosh, but then I was afraid of just ending up with a black screen and having to start it again (or reboot) via serial console.
What’s your strategy to dealing with Waydroid upgrades? I upgrade whenever images show up. Another problem that started happening a while back is corrupted audio. For example, notification sounds are distorted, like if something with the audio sync or a mismatch in sampling frequency. It sounds like if the speaker is under water. If I start playing audio for a minute or two, then it clears up. It also works for recording audio (tested via Signal call).
Perhaps I should be conservative with upgrading Waydroid and only do it if required.
Your uptimes are very inspiring! =))
1 Like
I meant idle-inhibit: Fix mapped property and potential uninhibit (!668) · Merge requests · World / Phosh / phoc · GitLab - haven’t checked, but chances are it should be backportable.
No real strategy. I’m just still on an Android 10 image from the time I’ve been working on making Waydroid work on Librem 5 at all, because there’s no easy upgrade path (signing keys are different) and I’ve been too lazy to set everything up from scratch again. I should do it one day… but not today 
My Waydroid usage is minimal, so having it outdated hasn’t bothered me enough so far.
2 Likes
Always, since I never restart.
I don’t know the longest … it’s about months, not days … Only restarting on updates.
1 Like
What about when you reflash?
1 Like
Technically reflashing is not restarting.