VP22 Upgrade from 24.04-1.0 to 24.04-1.1 failed
-
Great I have found a solution, I have removed
.cache/gstreamer-1.0/registry.aarch64.binThe rebooted, and I can record a video and view it again!
Thank you everyone!
EDIT: And playback performance seem better than before the upgrade!
-
wow great job !
I'd think that the upgrade could have removed the cache all by itself though, so filing an issue at gitlab would be interesting nonetheless. -
@gpatel-fr said in VP22 Upgrade from 24.04-1.0 to 24.04-1.1 failed:
I'd think that the upgrade could have removed the cache all by itself though, so filing an issue at gitlab would be interesting nonetheless.
Maybe it would have done so, if it hadn't failed in the first place...
-
maybe (I did not check the code on that) but you installed a new version successfully right ? Even if you checked 'don't erase user data', if a new version can be not compatible with the cached data, the cached data should go (after all, it should not hold any interesting data if it conforms to its name)
-
Where should I report the bug?
-
Logic would say the installer on Github. However the issues are not actively followed, it's obvious that there is not a lot of people monitoring or even janitoring the list. So maybe give a first try to the port for your device, after all we don't know if there are special handling per device for this.
-
Got hit by the failed OTA on my VP22 (stable channel). How long does the ubports installer usually take to flash from recovery? 3 attempts with the appimage have resulted in 15 minutes+ of the installer stuck at "Activating slot a" with the phone showing the fastboot menu along with the incredibly unhelpful "Text" as the output log.
-
3600 seconds limit for edits? Really?!?
Anyway, another attempt on a Mint Debian Edition computer instead of my usual minimal Devuan install gets further along. Hopefully it's ready within an hour so I can update my post.
EDIT: flashing worked fine, also VoLTE is active now, which is nice.
-
Since last upgrade I seem to experience occasionally system crashes, or rather freezes: the system does not respond and I have to reboot. I did not have such problems before the upgrade.
It seems to happen more when recording a video, when terminating a call, but It also happened in random moments like, just after starting Signal UT.
Anyone else noticed that?
-
While I don't have a VP22, I also did the same upgrade on my FP5, I have triggered a similar looking crash by doing more or less cheesy things with the dialer (I did not manage to repro it unfortunately).
I could connect to the phone via ssh and to launch top, all the signs of an oom were presents (no more free swap, swap process taking all the cpu time). I did not have the time to do any tests, at this point a Linux system is all but finished.
Another symptom was that the phone was unnaturally hot. -
I've tried to access the shell when the phone freezed, but It does not reply.
Honestly the frequency of freezes is quite alarming, it almost never happened before 24.04.1.1 .
-
maybe this problem could be related ?
-
I almost do not use Waydroid, the crashes and freezes happen when waydroid is not started and have not been started since boot.
Well I've investigated and it seems to be an out of memory problem.
Because I realize that now if I start a few apps (like the Morph browser + whatsweb + Signal UT ) then I rapidly run out of Ram AND Swap. (I can see it in top)
Then my question is why did it not happen before? Is the memory usage is higher in 24.04-1.1 compared to 24.04-1.0 and if so why ?
And secondly why do we have so few swap (2 Go) if there are Out of Memory problems? Or maybe we had more swap in 24.04-1.0 and it was reduced ?
Is it possible to increase the swap?
Edit: By the way I've reported the problem here. https://gitlab.com/ubports/porting/reference-device-ports/android11/volla-phone-22/volla-mimameid/-/issues/24
-
Ps: I also just experimented a black screen when receiving a call. In Adb I could see the phone was not in out of memory at that time. The phone was vibrating and I could not turn on the screen to see the call.
Although previously in this boot I had an Out of Memory problem, it freezed temporarilly, but the system recovered, so I wonder if some important system processes may have been killed in the process.
Honestly I'm wondering whether I should downgrade, because this starts to be a real problem.
-
@pparent said in VP22 Upgrade from 24.04-1.0 to 24.04-1.1 failed:
I can see it in top
When using top, did you have enough time to notice if one particular application's Ram use was growing without limit ?
To elaborate, here is the grand total of my experience with OOM.
First generally with Linux (desktop and servers): it has always happened in the context of a 'rogue' application, never because I loaded too much the system. If I was loading too many apps on a given Linux system, I could always unload one of them and get back to a more normal behaviour; when a rogue application was running, I could see this application eating more and more Ram and if I could not kill it fast enough (before I lost control of the console to use kill -9) the system was all but dead, only a hard reset could get it back. Needless to say (it's a pretty well known fact of using Linux) the system OOM handler was never of any help.
Then with UT
First I have found a 'rogue' app that can reliably hang my phone. This was the first experience of it, and I could see the very same behaviour using top (it is hanging progressively, it takes a few minutes to eat all my 4 GB of swap)
Then with the dialer: this has happened very recently, while I was trying to experiment with some advanced particularities of it and suddenly the system became sluggish and the UI unusable, connecting with ssh I could see with top that lomiri-dialer-app was growing more and more and the swap was eaten. The ssh session got soon unresponsive (the phone UI itself was already gone so it was another hard reboot. I am sure that at this point the dialer was the only application active, so it's the dialer or more probably one of its libraries that is the culprit. As the dialer use quite a lot of libraries, it's not helping much, but it's possible that one of the apps you were using has triggered the same bad code path. Unfortunately I could not repro it with the dialer.
I don't know if you have noticed it, but in the system there is something of a special OOM handling, application can submit a specific OOM profile when starting. Unfortunately I have not seen it any more useful than the pretty useless kernel default handling, the rogue applications can do their evil deeds without being bothered by it.
A last detail: on my FP5 (I'd suprised if your Volla was different because it's using half of your Ram like for my FP5, it's a giveaway), the swap handling is not the 'classical' sort, it's the more advanced type of 'compressed Ram'. I don't think it's a novelty of 24.04.1.1.
-
About the dialer, I cannot exclude that the app was opened (or had been used) at the time of every crash.
It's true also that I now use VoLTE, that I did not use before 24.04.1 , so it could have a impact on the RAM(?)
It's also true that I cannot reproduce the bug by opening a lot of apps straight after a reboot.
-
@pparent said in VP22 Upgrade from 24.04-1.0 to 24.04-1.1 failed:
if some important system processes may have been killed in the process.
Well, the OOM killer is legendary for it's lack of discrimination. If the system recovered somehow, there should be some trace in the system log.
I know from experience that when the system has to be rebooted after an OOM, there is no trace at all in the sytem log (and that is by itself a very major problem as it makes diagnostic impossible) -
@gpatel-fr for me when my system black screens all i can do is type, i still have access to ssh though and can run commands from my laptop.
-
@killclique said in VP22 Upgrade from 24.04-1.0 to 24.04-1.1 failed:
when my system black screens
See my reply in your dedicated thread, I think that your problem may be specific to the Fairphone 5 and so be different from the problem as explained by @pparent (who said that the problem occurred without any use of Waydroid).
-
Here is a situation where I'm close to Out-of-Memory, (my phone freezed for 15s and then recovered). If I reboot the phone and open the same apps I will have a lot more swap availiable. Surely if I keep using it like that, it will crash at some point. I have not made a call today, but I've taken pictures. I don't understand why the swap use is so much higher than normal because top does not show any processes that use abnormal amount of Ram. Could the problem come from swap itself?
top - 13:31:14 up 1 day, 25 min, 2 users, load average: 21.65, 22.07, 20.99 Tasks: 640 total, 1 running, 587 sleeping, 2 stopped, 50 zombie %Cpu(s): 12.1 us, 4.9 sy, 0.1 ni, 82.1 id, 0.0 wa, 0.0 hi, 0.8 si, 0.0 st MiB Mem : 81.1/3498.4 [ ] MiB Swap: 82.5/1924.1 [ ] PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND 3415 phablet 20 0 6229920 388144 303092 S 0.7 10.8 32:31.70 lomiri 22255 phablet 20 0 196.4g 162708 60184 S 0.3 4.5 0:26.95 signal-desktop 17763 phablet 20 0 3545708 152084 145080 S 0.3 4.2 1:46.33 qmlscene 17888 phablet 20 0 14.0g 130968 25928 S 0.7 3.7 4:06.44 QtWebEngineProc 22374 phablet 20 0 2414496 112092 61980 S 2.0 3.1 0:11.02 lomiri-camera-a 22131 phablet 20 0 204.4g 105492 23376 S 7.9 2.9 0:42.14 signal-desktop 4854 phablet 20 0 2283820 63164 59408 S 0.3 1.8 1:39.14 maliit-server 2551 1047 20 0 12.7g 57016 28064 S 99.3 1.6 3:21.46 camerahalserver 22343 phablet 20 0 1977936 42924 41036 S 2.3 1.2 0:05.77 qmlscene 22221 phablet 20 0 32.5g 40492 38812 S 0.0 1.1 0:05.71 signal-desktop 5103 phablet 20 0 2132348 40060 40060 T 0.0 1.1 1:53.34 lomiri-system-s 5222 phablet 20 0 1919912 39960 39960 T 0.0 1.1 0:34.41 lomiri-dialer-a 21580 phablet 20 0 293540 30952 30472 S 0.0 0.9 0:17.62 Xwayland 2520 1013 20 0 10.9g 13532 12296 S 8.9 0.4 0:16.99 minimediaservic 712 root 19 -1 83872 11136 10304 S 0.0 0.3 0:52.47 systemd-journal 2148 root 20 0 1214404 9508 7156 S 1.3 0.3 16:42.81 lomiri-system-c 1 root 20 0 24248 9496 5516 S 0.0 0.3 0:57.16 systemd 22745 phablet 20 0 178464 9164 7852 S 0.0 0.3 0:00.08 mtp-server 22738 phablet 20 0 326744 9056 8216 S 0.0 0.3 0:00.14 adbd 22755 root 20 0 1155836 8052 5828 S 0.0 0.2 0:00.05 adbd-pam-sessio 2465 phablet 20 0 22468 7728 5136 S 0.0 0.2 0:16.46 systemd 4858 phablet 20 0 2666196 7260 4108 S 0.0 0.2 0:31.06 lomiri-push-ser 1654 root 20 0 2286604 6788 1184 S 0.0 0.2 0:58.29 snapd 22773 phablet 20 0 57208 5608 3388 R 1.6 0.2 0:01.15 top 4855 phablet 20 0 294540 5496 4320 S 0.0 0.2 0:03.85 mtp-server-usb- 5261 phablet 20 0 350504 5320 4488 S 0.0 0.1 0:06.35 zeitgeist-fts 4857 phablet 20 0 405916 5188 4340 S 0.0 0.1 0:16.78 lomiri-indicato 22763 phablet 20 0 53404 5080 3584 S 0.0 0.1 0:00.08 bash
