Same issue here, since when I started with the Suomenlina version and now the Vanha Rauma version (4.4.0.58). I use the paid version on a Xperia 10 ii.
1 Like
It just happened on my Xperia 10 III as well. The button in utilities is really quite handy.
3 Likes
same on >> Xperia 10 II + OS 4.4.0.64
This has happened to me two times already, both of the times are with the latest OS at that time.
Last time was today, with 4.4.0.68. And after losing the fingerprint pattern, I can’t record a second finger because I am greeted with a message “Virhe! Sormenjälkeäsi ei tunnistettu”. I didn’t even touch the sensor.
I found a way to log oom kills by watching dmesg while browsing a heavy web site using the Browser:
dmesg -w | egrep "lowmemorykiller|oom_reaper|^ {19}.*"
Using that I get output like this:
[140539.580703] lowmemorykiller: Killing 'ec_fdroid:tab21' (22126), adj 905,
to free 85860kB on behalf of 'HwBinder:3801_1' (23173) because
cache 475268kB is below limit 668640kB for oom_score_adj 0
Free memory is 647552kB above reserved.
Free CMA is 0kB
Total reserve is 136256kB
Total free pages is 71000kB
Total file cache is 553396kB
Slab Reclaimable is 123100kB
Slab UnReclaimable is 417072kB
Total Slab is 540172kB
GFP mask is 0x6280c2
Kernel Memory Reclaimable is 13556kB
Free Swap 699252kB
queue len is 1 of max 1 reason:0x2 margin:-16314
[140539.581611] lowmemorykiller: Killing 'AndroidUI' (22051), adj 900,
to free 148920kB on behalf of 'HwBinder:3801_1' (23173) because
cache 475268kB is below limit 668640kB for oom_score_adj 0
Free memory is 647552kB above reserved.
Free CMA is 0kB
Total reserve is 136256kB
Total free pages is 71000kB
Total file cache is 553396kB
Slab Reclaimable is 123100kB
Slab UnReclaimable is 417072kB
Total Slab is 540172kB
GFP mask is 0x6280c2
Kernel Memory Reclaimable is 13556kB
Free Swap 699252kB
queue len is 1 of max 1 reason:0x2 margin:-16314
[140539.587560] lowmemorykiller: Killing 'com.whatsapp' (23989), adj 104,
to free 78024kB on behalf of 'HwBinder:3801_1' (23173) because
cache 474812kB is below limit 668640kB for oom_score_adj 0
Free memory is 656144kB above reserved.
Free CMA is 0kB
Total reserve is 136256kB
Total free pages is 80104kB
Total file cache is 552940kB
Slab Reclaimable is 123100kB
Slab UnReclaimable is 417072kB
Total Slab is 540172kB
GFP mask is 0x6280c2
Kernel Memory Reclaimable is 13556kB
Free Swap 698740kB
queue len is 1 of max 1 reason:0x2 margin:-14038
[140539.591645] lowmemorykiller: Killing 'jolla-email' (31314), adj 103,
to free 137720kB on behalf of 'lipstick' (5980) because
cache 474132kB is below limit 668640kB for oom_score_adj 0
Free memory is 658960kB above reserved.
Free CMA is 0kB
Total reserve is 136256kB
Total free pages is 83632kB
Total file cache is 552256kB
Slab Reclaimable is 123100kB
Slab UnReclaimable is 417072kB
Total Slab is 540172kB
GFP mask is 0x6000c0
Kernel Memory Reclaimable is 13100kB
Free Swap 698484kB
queue len is 1 of max 1 reason:0x2 margin:-13156
[140539.594922] oom_reaper: reaped process 22126 (ec_fdroid:tab21), now anon-rss:0kB, file-rss:0kB, shmem-rss:24kB
[140539.623615] oom_reaper: reaped process 31314 (jolla-email), now anon-rss:0kB, file-rss:0kB, shmem-rss:84kB
[140539.646406] oom_reaper: reaped process 23989 (com.whatsapp), now anon-rss:0kB, file-rss:0kB, shmem-rss:2780kB
[140539.681563] oom_reaper: reaped process 22051 (AndroidUI), now anon-rss:0kB, file-rss:128kB, shmem-rss:760kB
The good thing is that I can now see every OOM kill. The bad thing is that it’s very frequent… It’s a few kills per minute, give or take.
Edit: This is pretty much offtopic, so I started a new thread instead.
4 Likes
My SailfishOS 4.4.0.68 running on Xperia 10 III just lost the saved fingerprint for the third time - again, after about a week…
I don’t know whether it is the same problem as described, because no fingerprint is shown in the settings page after the act:
It is very annoying.
I have to say I haven’t lost a fp once yet.
Using 10mk3 for 2 months.
I lost it once, but reboot helped, and all were back.
But I can imagine how awful it must be for others
It’s been mentioned in this thread already, but just as a reminder, there’s now a button in the Settings app (Settings > System > Utilities > Restart fingerprint service) that will restart the fingerprint daemon and should bring the sensor back to life.
While this is a workaround rather than a fix, if you do discover your fingerprints aren’t being recognised, please give this a go. There shouldn’t be any need to re-register your prints or reboot your device.
5 Likes
I haven’t had the fingerprints missing once since I adjusted the minfree values; before that it was about once every two days in my normal device use. I’m quite confident at this point that oom was the cause all along.
3 Likes