Updated to 4.4 and still keeps crashing.
4.5 and the issue still remains
1 Like
Don’t you consider a simple reflash?
Not only remains, but also no information on how to debug this behaviour. Even happens on gallery app with videos I took with the xperia 10 ii.
I know this is just stock advice, I’m just curious, have any of you (other than the dev) collected logs for us to see?
In a terminal
- devel-su
- start gallery or like
- journalctl -k -f | grep Fatal
The allocation error noted by @Alex looks deadly but it would be nice to see if it’s consistently that.
2 Likes
I guess not, cause videos are pretty much broken right now, i mean, videos on fb for example lags like crazy, microtube lags like crazy, i have some videos on the phone that are probably 2k and they lag, so i guess it’s the same for most people since the 4.5 update, at least i didn’t have this problem on 4.4
Therefore I thought about a reflash with 4.4.0.72, but unfortunately forgot to write explicitly.
hey @poetaster,
I installed and run 9gag app, it has a lot of videos, and i did the journalctl -k -f | grep Fatal . It took a while but finally it stuck-frozed and after a while the "Wait - Exit"popup appeared on the top of the screen. Nothing appeared on grep. The only log I got without grep was:
[root@Xperia10II-SailfishX defaultuser]# journalctl -k -f
-- Logs begin at Wed 2023-06-28 14:04:09 EEST. --
Jun 28 14:59:21 Xperia10II-SailfishX kernel: msm_vidc: info: Opening video instance: 0000000000000000, 1
Jun 28 14:59:23 Xperia10II-SailfishX kernel: i2c_geni 4a88000.i2c: i2c error :-107
Jun 28 14:59:34 Xperia10II-SailfishX kernel: i2c_geni 4a88000.i2c: i2c error :-107
Jun 28 14:59:35 Xperia10II-SailfishX kernel: msm_vidc: info: Closed video instance: 0000000000000000
Jun 28 14:59:36 Xperia10II-SailfishX kernel: msm_vidc: info: Opening video instance: 0000000000000000, 1
Jun 28 14:59:36 Xperia10II-SailfishX kernel: msm_vidc: info: Closed video instance: 0000000000000000
Jun 28 14:59:36 Xperia10II-SailfishX kernel: msm_vidc: info: Opening video instance: 0000000000000000, 1
Jun 28 14:59:45 Xperia10II-SailfishX kernel: BUG: Bad rss-counter state mm:ffffffc0a905db00 idx:4 val:487609
Jun 28 14:59:45 Xperia10II-SailfishX kernel: msm_vidc: info: Closed video instance: 0000000000000000
Jun 28 14:59:45 Xperia10II-SailfishX kernel: msm_vidc: info: Closed video instance: 0000000000000000
Jun 28 15:00:04 Xperia10II-SailfishX kernel: i2c_geni 4a88000.i2c: i2c error :-107
Since you mention Alex, check his 2 years old comment here: GagBook | OpenRepos.net — Community Repository System
Is there any way to get logs from gstreamer or whatever video player/ system sailfishOS uses ?
You can just do a generic journalctl > log.txt to catch everything and grep through it looking for. Sometimes if I know I can trigger an error I use -r which shows newest entries first. Then I can quickly hit CTRL-C if something shows up since you see it a bit longer. One can also use specifiers to limit to systemd units (-u) or SYSLOG_IDENTIFIERS (-t). and of course, use -g to sepecify a grep pattern (perl style).
EDIT: -g is not supported on device.
If desperate strace 
I have to admit I’m not the best at this …
It looks like he’s creating exra logs. But for the sake of simplicity, if the bug is also showing up for the Jolla Gallery, it makes sense to focus on that since it will be familiar to @mal & co. @mal, you any advice for capturing logs for debugging this?
1 Like
I should have linked this:
There you can find a script that produces generic logs. That would probably be the most useful way to proceed.
1 Like
From terminal I did:
journalctl -f
I did run Gallery app and used it for 2 - 3 mins, the logs few seconds before and after the freeze/ crash:
:26095 total_time:2924049 (cc_soc:2724->3456)
Jun 28 16:06:37 Xperia10II-SailfishX kernel: i2c_geni 4a88000.i2c: i2c error :-107
Jun 28 16:06:40 Xperia10II-SailfishX /usr/libexec/mapplauncherd/booster-qt5[5534]: warning: terminating: booster:5976 invoker:7010 socket:20
Jun 28 16:06:40 Xperia10II-SailfishX /usr/libexec/mapplauncherd/booster-qt5[5534]: warning: Daemon: sending exit(1) to invoker(7010)
Jun 28 16:06:40 Xperia10II-SailfishX /usr/libexec/mapplauncherd/booster-qt5[5534]: warning: sending SIGTERM to booster (pid=5976)
Jun 28 16:06:40 Xperia10II-SailfishX booster-qt5[5534]: *** signal=17 pid=5534
Jun 28 16:06:40 Xperia10II-SailfishX kernel: msm_vidc: info: Closed video instance: 0000000000000000
Jun 28 16:06:41 Xperia10II-SailfishX kernel: msm_vidc: info: Opening video instance: 0000000000000000, 1
Jun 28 16:06:47 Xperia10II-SailfishX kernel: i2c_geni 4a88000.i2c: i2c error :-107
Jun 28 16:06:48 Xperia10II-SailfishX kernel: pmi632_charger: somc_aicl_irq_handler: IRQ: aicl-done
Jun 28 16:06:48 Xperia10II-SailfishX kernel: ALG: cap_learning_update: [SOMC CL][LERANING] charge_status:1 msoc:36 bsoc_cp:3531 batt_soc_cp_drop:0 cc_soc_drop:0 hold_time:39141 total_time:2937095 (cc_soc:2724->3456)
Jun 28 16:06:57 Xperia10II-SailfishX kernel: i2c_geni 4a88000.i2c: i2c error :-107
Jun 28 16:07:01 Xperia10II-SailfishX kernel: pmi632_charger: somc_aicl_irq_handler: IRQ: aicl-done
Jun 28 16:07:01 Xperia10II-SailfishX kernel: ALG: cap_learning_update: [SOMC CL][LERANING] charge_status:1 msoc:36 bsoc_cp:3531 batt_soc_cp_drop:0 cc_soc_drop:0 hold_time:52170 total_time:2950124 (cc_soc:2724->3456)
Jun 28 16:07:02 Xperia10II-SailfishX kernel: msm_vidc: info: Closed video instance: 0000000000000000
Jun 28 16:07:03 Xperia10II-SailfishX kernel: msm_vidc: info: Opening video instance: 0000000000000000, 1
Jun 28 16:07:08 Xperia10II-SailfishX kernel: i2c_geni 4a88000.i2c: i2c error :-107
Jun 28 16:07:11 Xperia10II-SailfishX lipstick[5741]: [D] onTriggered:102 - Application "Gallery" with PID 29143 is not responding
Jun 28 16:07:11 Xperia10II-SailfishX lipstick[5741]: [D] onClicked:89 - User terminated the unresponsive application "Gallery" with PID 29143
Jun 28 16:07:12 Xperia10II-SailfishX lipstick[5741]: [D] onClicked:89 - User terminated the unresponsive application "Gallery" with PID 29143
Jun 28 16:07:12 Xperia10II-SailfishX kernel: BUG: Bad rss-counter state mm:ffffffc0a8ddb480 idx:4 val:117958
Jun 28 16:07:12 Xperia10II-SailfishX booster-generic[5542]: *** signal=17 pid=5542
Jun 28 16:07:12 Xperia10II-SailfishX /usr/libexec/mapplauncherd/booster-generic[5542]: warning: Boosted process (pid=26508) exit(255)
Jun 28 16:07:12 Xperia10II-SailfishX /usr/libexec/mapplauncherd/booster-generic[5542]: warning: Daemon: sending exit(255) to invoker(29102)
Jun 28 16:07:12 Xperia10II-SailfishX invoker[29102]: warning: application (pid=-1) exit(255) signal(0)
Jun 28 16:07:12 Xperia10II-SailfishX kernel: msm_vidc: info: Closed video instance: 0000000000000000
Jun 28 16:07:14 Xperia10II-SailfishX kernel: pmi632_charger: somc_aicl_irq_handler: IRQ: aicl-done
Jun 28 16:07:14 Xperia10II-SailfishX kernel: ALG: cap_learning_update: [SOMC CL][LERANING] charge_status:1 msoc:36 bsoc_cp:3547 batt_soc_cp_drop:-16 cc_soc_drop:-13 hold_time:65222 total_time:2963176 (cc_soc:2724->3469)
Jun 28 16:07:14 Xperia10II-SailfishX kernel: ALG: cap_learning_update: [SOMC CL]max bsoc/ccsoc updated. bsoc_cp:3547 ccsoc:3469
^C
[root@Xperia10II-SailfishX defaultuser]#
I played several videos and swap from right to left, I played one video and when I pressed the play button in the ecenter of the screen to rewatch it I got black screen and “Wait - Exit” popup on the top. At “Jun 28 16:07:03” I preessed the play button.
At your disposal for further tries / experiments / investigation!
Also I run collect-logs.sh it created a .tar with 20 .txt files, which one do you believe it could help?
I wonder what’s wrong on the i2c bus? But that’s not relevant (maybe a battery thing?)
All of them But that’s a general overview of al things. It does contain a journal.txt file which is probably not going to look any different than what you’re getting
I’m just testing with this combination:
[root@Phone22 defaultuser]# journalctl --no-pager -f _PID=4404
-- Logs begin at Wed 2023-06-28 15:20:52 CEST. --
Jun 28 15:22:32 Phone22 jolla-gallery[4404]: [W] unknown:1154 - file:///usr/lib64/qt5/qml/Sailfish/Silica/PageStack.qml:1154:13: QML Binding: Binding loop detected for property "value"
So, using follow and specifying the _PID (which I grabbed from an initial run of just journalctl) I get updates ONLY for the app as errors related to it pop up.
Yes, I did. Already there are a lot of bug reports regarding this issue.
This is not applicable for that case. Two phones, arm7 and aarch64 are affected. I have already flashed a Galaxy Tab S6 Lite using SFOS 4.3 and video is crashing as well.
1 Like
Since I am using an XA2 Ultra upgraded step by step from 3.x till the current version I also do not think that reflashing will solve it. I see the exact same behavior on my phone with different HW and it all started with SF4.x. So this was the only change that happened right when the behavior started.
Yeah, I’ve been following, but failing to find a common thread. Although it seems like if it’s a constant hassle with the browser crashing on youtube and other apps you’d think it was a gstreamer video thing.
However, I don’t have any issues with video on the volla/gs phones, BUT youtube crashes the jolla browser consistently. I’m just trying to find a common thread.
I don’t think flashing is the right answer either. There is something foul.
YouTube on the XA2 Ultra is unusable in the built-in browser on 4.5.x.x. Videos just freeze after a few frames and that’s it (sound keeps playing while video is frozen). Same videos play fine in Android browsers like e.g. Fennec (“fine” means they don’t freeze, but there’s still some frame drop).
I’m having problems playing videos with any native player but the official camera app as well.
Picoplayer gets me a “Could not load page” error; LLs vPlayer starts with a white screen and no nothing instead.
For such a trivial thing I’m now forced to use an android app. 
Any suggestions?