Discharging rate
The loss of battery capacity (discharging rate) during inactivity (mainly at night) is approximately 3.2%/h on my 10 IV. I charge between 25% and 80% (note: Battery Buddy does not turn off charging at the set value). I have the same applications from Jolla Store, OpenRepos, Chum installed on the both 10 IV and 10 III, but on the 10 III the battery capacity decreases by about 1%/h when idle.
GPS works much better to 10 III (finds satellites faster and finds more). The bad news is that after a while of using the GPS, the same error as on the 10 III occurs, sound stops working.
I found another issue, which occurred the third time. Enabling Bluetooth is not possible. If you enable it via the gui, the button will blink for ~1-2 minutes and after that it stay disabled.
[defaultuser@Xperia10IV ~]$ dmesg -T | grep bluetooth
[Do Sep 26 10:47:22 2024] droid-hal-init: Service 'vendor.bluetooth-1-0' (pid 23321) received signal 6
[Do Sep 26 10:47:22 2024] droid-hal-init: Sending signal 9 to service 'vendor.bluetooth-1-0' (pid 23321) process group... HYBRIS: killing PID instead of process group.
[Do Sep 26 10:47:22 2024] droid-hal-init: starting service 'vendor.bluetooth-1-0'...
[Do Sep 26 10:47:22 2024] droid-hal-init: ... started service 'vendor.bluetooth-1-0' has pid 11652
[Do Sep 26 10:47:22 2024] droid-hal-init: service 'vendor.bluetooth-1-0' requested start, but it is already running (flags: 4)
[Do Sep 26 10:47:22 2024] droid-hal-init: Control message: Processed ctl.interface_start for 'android.hardware.bluetooth@1.0::IBluetoothHci/default' from pid: 1169 (/system/system_ext/bin/
hwservicemanager)
[Do Sep 26 10:47:41 2024] droid-hal-init: Service 'vendor.bluetooth-1-0' (pid 11652) received signal 6
[Do Sep 26 10:47:41 2024] droid-hal-init: Sending signal 9 to service 'vendor.bluetooth-1-0' (pid 11652) process group... HYBRIS: killing PID instead of process group.
[Do Sep 26 10:47:41 2024] droid-hal-init: starting service 'vendor.bluetooth-1-0'...
[Do Sep 26 10:47:41 2024] droid-hal-init: ... started service 'vendor.bluetooth-1-0' has pid 11981
[Do Sep 26 10:47:41 2024] droid-hal-init: service 'vendor.bluetooth-1-0' requested start, but it is already running (flags: 4)
[Do Sep 26 10:47:41 2024] droid-hal-init: Control message: Processed ctl.interface_start for 'android.hardware.bluetooth@1.0::IBluetoothHci/default' from pid: 1169 (/system/system_ext/bin/
hwservicemanager)
I am not sure if these messages are related to the problem because if I am trying to enable bluetooth again, these messages won’t appear again.
Looks like the service is running (but not working):
[defaultuser@Xperia10IV ~]$ systemctl status bluetooth.service
● bluetooth.service - Bluetooth service
Loaded: loaded (/usr/lib/systemd/system/bluetooth.service; disabled; vendor preset: enabled)
Active: active (running) since Tue 2024-09-24 07:37:20 CEST; 2 days ago
Docs: man:bluetoothd(8)
Main PID: 3188 (bluetoothd)
Status: "Running"
Memory: 3.1M
CGroup: /system.slice/bluetooth.service
└─3188 /usr/libexec/bluetooth/bluetoothd -n
Restarting the service via SailfishUtilities won’t solve the problem, even if the service has been restarted:
[defaultuser@Xperia10IV ~]$ systemctl status bluetooth.service
● bluetooth.service - Bluetooth service
Loaded: loaded (/usr/lib/systemd/system/bluetooth.service; disabled; vendor preset: enabled)
Active: active (running) since Thu 2024-09-26 11:01:44 CEST; 1min 18s ago
Docs: man:bluetoothd(8)
Main PID: 13374 (bluetoothd)
Status: "Running"
Memory: 1.1M
CGroup: /system.slice/bluetooth.service
└─13374 /usr/libexec/bluetooth/bluetoothd -n
[defaultuser@Xperia10IV ~]$ dmesg -T | grep bluetooth
[Do Sep 26 11:02:26 2024] droid-hal-init: Service 'vendor.bluetooth-1-0' (pid 11981) received signal 6
[Do Sep 26 11:02:26 2024] droid-hal-init: Sending signal 9 to service 'vendor.bluetooth-1-0' (pid 11981) process group... HYBRIS: killing PID instead of process group.
[Do Sep 26 11:02:26 2024] droid-hal-init: starting service 'vendor.bluetooth-1-0'...
[Do Sep 26 11:02:26 2024] droid-hal-init: ... started service 'vendor.bluetooth-1-0' has pid 13412
[Do Sep 26 11:02:26 2024] droid-hal-init: service 'vendor.bluetooth-1-0' requested start, but it is already running (flags: 4)
[Do Sep 26 11:02:26 2024] droid-hal-init: Control message: Processed ctl.interface_start for 'android.hardware.bluetooth@1.0::IBluetoothHci/default' from pid: 1169 (/system/system_ext/bin/hwservicemanager)
[Do Sep 26 11:02:49 2024] droid-hal-init: Service 'vendor.bluetooth-1-0' (pid 13412) received signal 6
[Do Sep 26 11:02:49 2024] droid-hal-init: Sending signal 9 to service 'vendor.bluetooth-1-0' (pid 13412) process group... HYBRIS: killing PID instead of process group.
[Do Sep 26 11:02:49 2024] droid-hal-init: starting service 'vendor.bluetooth-1-0'...
[Do Sep 26 11:02:49 2024] droid-hal-init: ... started service 'vendor.bluetooth-1-0' has pid 13491
[Do Sep 26 11:02:49 2024] droid-hal-init: Control message: Processed ctl.interface_start for 'android.hardware.bluetooth@1.0::IBluetoothHci/default' from pid: 1169 (/system/system_ext/bin/hwservicemanager)
Even if it is still failing I have the feeling that the UI (blink checkbox/button) is trying it longer than usual.
EDIT:
looks similar [3.4.0 onwards] Bluetooth turning on doesn't work
This issue is related to Xperia 10 V also. Just restarting phone helped me.
Quick question, does SFOS use both speakers in videos/music (loud and earpiece)?
I have this problem with my Xperia 10 V only when no sim card is inserted.
Yes please, go ahead, there is no bug about call recording yet. There are bugs about audio routing problems, though.
EDIT: On my Xperia 10 V (4.6.0.15), the Audio recorder starts fine both from the CLI and the app grid. When started from the CLI, it lists those “not founds” but opens up despite them. But it does not record anything. The volume display remains a straight line. The app does not “hear” anything.
After a few hours of use, I am pleased that Sailfish is running on the 10 IV after a long wait. First I had problems with the backup from the XA2 Plus because an error message appeared when restoring the notes. So I had to transfer all my contacts manually.
From my point of view, the following points need to be fixed.
very important
- sound during calls via the loudspeaker (so you can only make calls with a headset)
- I very often lose the mobile connection (A1, Austria), I always have wifi deactivated
- known missing support of android and camera
medium importance
- the flashlight does not work yet
- the t9 input dictionary is missing in the store
low importance
- the question of “charging only” when I plug in the phone with the sony charging equipment
Furthermore, due to the reduced content in the Jolla store, I am missing apps I have used so far and I have not yet found an alternative there or in chum (e.g. hunger meter).
Hi! Im new Jolla user with my Xperia 10IV. Is there going to be a full version of Jolla 5.0 to this device?
Problems so far: Slow charging and camera wont work at all, just black.
There’s another X10IV user with slow charging issue, but using a USB 2.0 cable with a Sony branded charger made it go up to ~1500mA. His charging issues started before flashing Sailfish OS, so this issue could be something that’s X10IV specific.
Let’s gather more user feedback and see what comes up.
Until now, I have not paid attention to the charging current, because I am comfortable with charging at a lower current. I verified my 10 IV
- on chargers up to approx. 1600 mA (3 pieces from different manufacturers), the charging current was according to the charger (from 1000 to 1600 mA),
- on chargers with a high current (fast charger, not Sony), the 10 IV only charged approx. 400 - 500 mA.
An interesting but unpleasant finding. I did not detect the status before flashing SFOS.
I have exactly this issue. What does dmesg
give you, when connecting via a high-speed USB interface and a USB 3 cable?
[274849.396528] usb usb1-port2: Cannot enable. Maybe the USB cable is bad?
[274850.284557] usb usb1-port2: Cannot enable. Maybe the USB cable is bad?
[274850.284716] usb usb1-port2: attempt power cycle
[274851.236581] usb usb1-port2: Cannot enable. Maybe the USB cable is bad?
[274852.124644] usb usb1-port2: Cannot enable. Maybe the USB cable is bad?
[274852.124825] usb usb1-port2: unable to enumerate USB device
[274855.309164] usb usb1-port2: Cannot enable. Maybe the USB cable is bad?
[274856.197192] usb usb1-port2: Cannot enable. Maybe the USB cable is bad?
[274856.197363] usb usb1-port2: attempt power cycle
[274857.149252] usb usb1-port2: Cannot enable. Maybe the USB cable is bad?
[274858.036779] usb usb1-port2: Cannot enable. Maybe the USB cable is bad?
[274858.036964] usb usb1-port2: unable to enumerate USB device
I had to flash the IV via my old USB 1.1 hub :’-)
The fast charger has a fixed (USB) cable, it cannot be replaced. I tried two different fast chargers (ASUS, EVE), the result was the same. What parameter did you use for dmesg
? Without the parameter, I did not find a similar status for USB in the listing.
Ah, I meant dmesg
on my computer, and then attaching the phone to the computer via some high-speed connection. It triggers like that both on USB-A 3 and USB-C on my Frame.work, but it’s working perfectly on my USB 1.1 hub :’-)
After reboot web links in grid is missing icons. After rebooting home screen, web link icons is back.
Another issue happened multiple times: AUX port is not working, even after restart the audio service via the utilities tool
Isn’t it a known issue that the headphone jack will not work on IV and V Xperias at this time with the beta release?
If I am not mistaken it was announced somewhere
Would it be possible to publish an OS update that updates the browser and what else the C2 got?
I mean this despite the new binaries fixing everything and maybe taking more time, more like tossing us 10iv (and 10v) users a bone.
Please toss us a bone for xmas!
You can follow the steps here to update the browser: Install
From what I understand, SFOS 5 and the paid license with Android App Support, etc. is hopefully to be released before the end of the year and will include the new Sony binaries.
Sure I installed ESR91, and quite sure I didn’t mess it up, but essentially nothing works, from the sfos forum app’s web view to sites showing as mobile.
I have my work phone which I use for browsing, because this is the kind of stuff a Jolla release simply wouldn’t have (me maybe making a mistake, or there being some ancillary issue).
Samesies for running Android apps on it.
So to re-iterate, there is no guarantee the new blobs will work by the end of the year, so it would be nice to get whatever Jolla has in their CI pipeline and passes the same tests they had for the current release.
Not just what hopefully will exist.