Note on the last RC Volla update (June 3)
-
Sorry, my bad English.
On last RC I have had the same experience with my Volla. Plus strange volume drops when I switch between the speakers and Bluetooth. And an almost inaudible alarm clock even though the volume was turned up. So I had to go to stable.
-
@domubpkm : My Volla (on RC) also has sudden restarts as of recently (don't know exactly, 1 week?).
I thought it was only me, and maybe related to Dekko2 which I installed around that time. The program has full system access. Besides the OS update nothing else changed, I think. -
RC generally no longer supports two apps open at the same time. For example, five minutes ago, I had Radio (patrickjane) and I wanted to read a received SMS. So I opened messaging app and Lomiri crashed.
-
Went back to OTA-22 to verify return to normal working.
-
@domubpkm :
Did you already verify that with the old RC version of the OS, OTA-22, the Volla Phone works in a stable way, or are you still testing?
If the newer RC version of the OS causes the phone to restart if more than 1 app is open, that is bad.
I'm not a power user, but having more than 1 app open at one time is a daily thing for me. -
@alter Unfortunately, in my experience, it is an observation that the Volla manages multitasking very badly (alas!) which has always caused various malfunctions, even for OTA-22 and previous OTAs, or while being on RC or DEV. I just find that crashes are much more frequent now on RCs that have followed OTA-22.
-
@domubpkm : Okay.
For me, the Volla Phone worked okay (apart from a sudden restart once in a while), but I guess the experience depends on usage too.
This last week or so, I feel things have gotten much worse (frequent restarts). -
D domubpkm referenced this topic on
-
Confirm here too, lot of lomiri crash since latest RC for my volla phone. I can't open a bug, because I don't find a reliable way to reproduce it, someone can?
-
-
@manland I am no longer under RC immediately because my Volla had caught Lomirite (new contagious disease?
) and it was too much!
However, I have had many different crash scenarios, most often (but not only) when two apps (any) were open at the same time and with the fact of wanting to switch from one app to another , or an app and a webapp. Clicking on a link, for example github in the Openstore of an app can cause a crash too. I had a crash when opening only the gallery and pressing a photo to view it. It seems that restarting the smartphone improves things for a short time (memory reset?) which makes crashes less systematicI switched to OTA-22 through the settings and I wonder if now the stable channel has not been contaminated to some extent because, although less frequent, I find lomiri crashes on occasion.
When OTA-23, I think I will do a total reflash by the installer without keeping anything.
-
@domubpkm You could try switching off and on, it's not the same as rebooting.
-
@bolly Of course, i tested that too. There is a problem, that's for sure.
-
For those on RC, does the new June 10th update fix the Lomiry crashing issue ?
-
@domubpkm : I only noticed RC update 53 now. I just downloaded it and will check.
-
I'm in RC again.
Radio app playing + wanting to fully display MMS image at the same time = Lomiri crash : during the relaunch of Lomiri, the song became very loud then back to normal. -
@domubpkm : Okay. I don't use that app or MMS. Up till now no restarts. Maybe just luck.
EDIT: Axolotl freezes and auto restart now -
Perhaps currently a temporary solution may be to restart Lomiri manually from time to time with UTTT (System /services), which would have the effect of resetting certain temporary memories (assumption) and avoiding a crash at the wrong time.
I try.. -
Please update again to latest RC from Friday. Its labelled 2022-W24 (and not the number you see in the update screen, but please check "About" section after phone has been updated for the real version number) and retest that stuff.
-
@flohack Personally, I updated RC right away and it seems to me that RC has indeed stabilized. In addition I installed to test the all rescent QtWebEngine on top and nothing exploded!
Can you explain in a easy way what you fixed? -
@domubpkm Its basically a memory leak we created during updating a few things, and it was fixed in devel and now moved to RC on Friday: https://gitlab.com/ubports/development/core/hybris-support/mir-android-platform/-/merge_requests/31
