Se how the minimum changes around 5000 seconds, then drops a bit around 12000, and then jumps at 48000? I need to find out why it doesn’t drop all the way back (presuming you had the same programs open at the low times).
I think I need to postpone further testing a bit and update again to the most recent kernel, because this debug kernel seems to bork my modem functionality (or revert back to the previously poor behaviour). Today I have had three modem crashes already that haven’t been recoverable without a phone restart.
I have triggered a rebase of that kernel branch - it was old enough to be very incompatible with current userspace. Once the CI produces the artifacts you should be able to install it again without losing modem reliability.
Excellent! Just as a side note, a recent call with the debug kernel triggered a change to 3G (before it crashed for the 3rd time today), while after upgrading to newest kernel VoLTE seems to work again (at least indicator stayed on 4G).
True, but I had VoLTE working before on this kernel, so I am guessing it is LTE this time too. But that was just a side note, so let’s keep this thread to Millipixels .
After reverting back by doing apt full-upgrade and rebooting. I managed to take one picture, closed the millipixels ap, opened it back up, and it failed to get another picture. Its hung again. Something is different about the test kernel that made my camera work.
Definitely helpful, thanks for the offer. After @dos fixed up the kernel package, you’ll have to download and install it again to get stability on par with the regular one.
I feel like you’re asking me to reproduce a problem that this kernel has fixed. I have taken many pictures without issue. I’ll keep logging data every second but I’m thinking the storage space will run out before I ever see this problem again.
I don’t know if it’s fixed. But I need to have someone confirm whether it is or not, by using it for some prolonged time (days?) and reporting the results.
If the problems come out, it will be regardless of how many pictures you take.
I’m not sure if what I’ve noticed is the same, but as i started to use the camera more, it’s been doing eternal saves of pics more often, freezing the cam picture as well. Only identifiable theme seems to be that I have other apps running as well.
I have resumed testing again, logging with 5s interval. So far so good, but I have seen a couple of spikes in cma.log. Values have returned to the previous ones right after though.
Here are some observation after about an hour of intense testing:
I didn’t get gnuplot to work, so I plotted the chart in LibreOffice Calc instead.
As seen in the chart, there are some outliers, but directly after returning to the previous value. However, the values trend higher probably due to more open apps.
I have taken over 20 photos without Millipixels hanging. I opened more and more apps during the tests and at the end had the following open apps in addition to Millipixels:
Telegram
Geary
Firefox
Markets
Loupe
Calls
Chatty
Calendar
Contacts
Tootle
Weather
Terminal
Settings
Password safe
PureOS store
Maps
Free42 (calculator)
DejaDup backup (backing up phone)
Lollipop
htop
System usage
Nautilus
uPlayer (playing video)
Hi,
I haven’t read all the backlog of this thread (sorry).
How do I test the fix/kernel? Just by making a system update on the phone?
Or is this some dev-build where I have to do something more?