3 ms·
Note that both PinePhone and pmOS have yet to reach "daily driver" status, especially if you actually care about using the phone featureset, want to run a prope
by zozbot234 5y ago
Note that both PinePhone and pmOS have yet to reach "daily driver" status, especially if you actually care about using the phone featureset, want to run a proper mainline (not vendor) kernel and (as for pmOS) want to go outside the narrow subset of hardware that's endorsed by that project as 'working properly'.
Also, many users have noticed that phone/tablet/mobile hardware in general tends to become super flaky when you actively try to use it for intensive general-purpose workloads, as with mainstream Linux apps. It seems that some power and/or thermal limits are easily exceeded with no real warning, and lockups/reboots can result. Dealing with this would require extra features in the kernel and/or the basic system software to assess indicators of available resources, and throttle the system if it seems to be running outside "reasonable" conditions. Implementing this in a way that can work generally on different kinds of hardware is of course possible, but not easy by any means.
- chrismorgan 5y agoAs an example of the flakiness: if I use my PinePhone heavily, the screen tends to stop working spontaneously, so that if on at the time of failure, it ceases to update, and when turned off and on again it will be black. Touch input still works. Restarting the graphical session (e.g. ssh in and run `systemctl restart phosh` for phosh or `systemctl restart tinydm` for sxmo) fixes it. “Heavily” tends to mean at least three of (a) heavy hotspot usage, (b) heavy CPU usage, (c) plugged in/charging, and (d) screen on, but if I’m physically using it it seems less likely to happen. Note that this is mostly with ambient temperatures of 25–30°C; come winter, I suspect it will happen less often. Plus there’s also the screen flickering thing, that sometimes, mostly when it’s been being used heavily but sometimes when it’s been idle and barely even warm, the screen is all flickery and ghosty when you turn it on one time, in which case it will normally stay like that for quite some time. That I observed right from the very start, under whatever the default OS was (Alpine, I think?, with Plasma; I subsequently switched to DanctNIX Arch with Phosh, and more recently from Phosh to sxmo). I have no idea if these things are typical or not, or if there are known solutions. I haven’t looked. They don’t tend to bother me much, I don’t really depend on a phone except for my internet supply.
- robbedpeter 5y agoMaybe tie those systemctl commands to the power button and state, so it restarts the screen every time you blank the screen, or when coming back on use a restart for the service? I have a feeling mainstream phones use all sorts of these ux hacks in the background - it only looks good, under the hood is just as messy and chaotic as any other software/hardware collision.
- megous 5y agoLCD controller is restarted/reinitialized every time you "blank" it. So this would be useless. Likely GPU driver/mesa/compositor crashing. I never have any issues with the screen when using i3wm (with GPU acceleration disabled). These bug reports would be more useful, if the OP did some debugging/log hunting.
- spijdar 5y agoIn this case, what's happening (based on what GP says, not personal experience) is the window server (phosh as a wayland compositor or Xorg in sxmo's case) is crashing, possibly (probably?) due to a crash in the Mali driver or some sunxi component managing the physical display output. Restarting the window server here would "reset" the relevant GPU bits, and get the display back. It also will (effectively) restart the whole graphical session, e.g. close all GUI things, so not feasible to do every time you cycle the screen, at least for most people. (some OSes and window servers like the Windows GUI stack can restart the GPU driver without killing the GUI, but Linux isn't ... particularly capable of this, at any part of the stack, AFAIK at least)
- chrismorgan 5y agoSway in sxmo’s case, actually. I’m not sure what exactly is falling over, but the session is all still there, with the compositor (Sway or Phosh) still responding to I/O, and, from my very limited probing, still working perfectly… except that its screen output is dead and it doesn’t realise it. Nothing interesting in the journal or dmesg, for example. If the compositor had crashed, it would have been restarted automatically.
- chriswarbo 5y ago> Note that both PinePhone and pmOS have yet to reach "daily driver" status Meh, I don't find such blanket statements compelling. My Pinephone is a perfectly good "daily driver": I use it for phone calls, SMS, email, scanning QR codes, displaying QR codes (train tickets, parcel deliveries, etc.), Web browsing, etc. People also said the same thing about OpenMoko, yet that was my "daily driver" for a decade.