Dunno why, but that sounds nonsense. I’ve installed 7 (seven!) X10iii to friends of mine and nobody has ever complained with issues like that.
Any logs available as proof?
On C2 automatic rotation can be fixed with shell-command:
systemctl restart sensorfwd.service
1 Like
Just search for “Xperia 10 III audio” here in this forum, there are many reports.
There’s another longstanding unfixed bug that most SMS get received multiple times.
after the first restart, I was still on .68, but after the second attempt, it worked without any problems on my 10IV.
Guys, one question:
Don’t you prepare your devices before upgrading? I always do a restart BEFORE and AFTER upgrade.
How can it be, that “solutions” like this emerge, after a restart renders that useless?x
Cannot support that statement. Works nicely for me all around on my C2, Xperia 10 III and Xperia 10 II.
Best regards
Fuchur
Yup among other things (backup, AAS stopped …). I cant recall last time I had issue after an update (might have been on my Jolla phone.)
Do you keep AppSupport enabled all time or do you only start AppSupport when using an Android App and stop AppSupport thereafter?
Unfortunately, I can’t insert or attach the tar.gz file here. How can I send it to you?
yea i persistently get the audio issues on my 10III. for me, it seems to be a single bug in the audio routing daemon, and restarting ohmd fixes it 100% of the time.
the bug seems to be that ohmd crashes or freezes. the symptoms vary, and sometimes it gets ‘stuck’ on the audio subsystem for calling and will make no media or system sounds. sometimes it will only switch to wired headphones in sailfish, sometimes only in android apps. sometimes bluetooth audio routing doesn’t work. sometimes the phone app will crash when making a call with ‘call failed’ and then the phone app opens up again on its own and starts dialing a second later (this one is awful because the dialer app stays a little broken and you cannot use speaker/mute/etc buttons). this one may be two separate bugs, dunno.
also, if you use an app like AudioOutputChooser, it will have no effect whatsoever once the bug gets triggered. the only fix is restarting ohmd, and then sometimes also restarting pulse.
this bug never affected me on 10 II or XA2 or XZ2c
i have tons of logs of the bug happening in several flavors, but i haven’t turned up anything interesting. anyway, i promise it’s true, and i’ve seen several users with similar reports. it happened to me twice today.
youre right that some people dont have this issue, of course. it could be something really strange, like different carriers somehow causing it, or it could be straightforward like no appsupport no bug. could be a specific app or patch, could be a certain class of bluetooth devices. i can never reliably reproduce it, but it happens almost every day, and sometimes multiple times a day.
I also had the audio loss (after GPS), multiple users were affected.
Maybe different subsets of device configurations exist? The Volla Quintus phone has different batches with newer batches the camera and flashlight are not supported, my older batch device produces nice images with the camera and I use the flashlight nearly daily as torch
I just updated my daily driver Xperia 10 II over GUI standard). So far so good, no new problem. AAS works (no change here). Did not test everything yet.
This latest update proceeded normally on my Jolla C2 phone, but got stuck in Recovery 2.0 mode. I used Telnet connection, but I can’t get any further. The phone is unusable at this point (I haven’t tried resetting the phone yet).
On Jolla C2 stuck in recovery mode, running the following command in the recovery shell should get you out of it
dd if=/dev/zero of=/dev/sda3 count=1 bs=32
then exit the shell and reboot the device
5 Likes
on my C2 since last patch battery is draining faaaaast! And flashlight stopped working
Equal app support starts stops starts … Every now and then. I have Xperia 10 V so I can not say if that happening is due to every other problems in 10 V.
In general it is kept on at my smartphones.
I had to reboot both phones this morning around 8:00. In order to figure out how long it would take until the start-stop loop begins, I enabled AppSupport on both devices and kept it running. So far (for more than six hours now) no problem, still running fine
2 Likes
I have an interesting bug since the latest 5.0.0.71 upgrade a couple of days ago. I have android mobile data and wifi internet, however all the Sailfish OS apps now dont have internet access any longer. Time is correct, rebooted, restarted network services, tried wifi and/or mobile data no cigar.