KM> This is the state of my freerunner after an upgrade of SHR-U a few KM> hours ago: KM> KM> KM> resolved issues: KM> KM> * My sim card seems to be detected on every boot now. :-)
great KM> * Thanks to the hint of Christ v.W. I got the shr-settings icon KM> back on desktop. that helps :) KM> persitstent issues: KM> KM> * insane times for dim-prelock-lock-suspend please customize by conf in home dir. for example i am perfectly happy about the default times. i use disply/cpu locking if needed. KM> * My FR dims, locks and suspends when on usb. It always did, since KM> I flashed SHR-U two months ago for the first time. if usb is plugged in while boot this is the issue, unless there is anything new, if you replug, it should stay on. Please check this. I have a feeling that new bug is causing sleep on usb again, but in my case not or not all the time. KM> * My FR still enters blank-screen-with-a-single-cursor mode on KM> automatic suspend. Most of the time, I can still communicate via KM> usb and reboot either via the power button or with the reboot KM> command. But twice I got into deep freeze mode with no reaction KM> whatsoever to the power button. The only way to get the FR working KM> was to remove the battery. is this system on NAND or uSD? KM> * GPS yields no valid position, even though GPS radio is on. KM> I have [fsotdl.provider_gps_nmea] and [fsotdl.provider_gps] KM> commented out in fsotdld.conf like recommended a few days ago. Is KM> this still correct? GPS OK here, but have A5 where fsotdld is not even present and GPS issues appeared... KM> * After automatic suspend, I wasn't able to unlock the screen. I KM> could move the slider from left to right, but the screen just did KM> not unlock. However, I had this incident only once. KM> * With every reboot the clock is exactly two more hours in the KM> past. Since we are currently two hours before UTC, I suspect, some KM> script assumes UTC while it actually is local time. KM> * xandr -o 1; xrandr --o 1 KM> yields a garbled screen. It does so too, if the two xrandr commands KM> are given manually with minutes in between. The screen can be KM> ungarbled with xrandr -o0 this is for sure the X drivers, has been an issue here for a long time, i don't rotate at all yet, as it has been unusable. KM> * ventura does not use the whole screen after the option "rotate" KM> is activated in the menu. It does however use all available space KM> when restarted. this has been an issue with E. it happens in other applications too. KM> * power_button->lock just returns to the desktop rather than lock KM> the screen. suspend and power off work, though. KM> Ironically, I had this the other way around about a week ago. booting now to test KM> Conclusion: KM> Unfortunately the two most serious issues remain -- Freeze on KM> automatic suspend and lack of valid GPOS position. thank you for the reports Petr _______________________________________________ Shr-User mailing list [email protected] http://lists.shr-project.org/mailman/listinfo/shr-user
