I experienced the same problem. But then I forced a complete restart and then it suddenly showed 65% but then I tried to charge and it just shows 65% all the time. It definitely seems to be something with the charging that is buggy
It is clearly stated in the release notes
4 Likes
Very true, but there’s one problem I ran into. Current situation is that /sys/class/power_supply/battery/capacity is only updated with a reboot, while current_now and voltage_now from the same directory work properly.
When you configure your device to apply a charging threshold (90% in my case) and at reboot the device’s capacity exceeds that thrashold, it will never charge.
I could therefore see a decreasing voltage_now and a negative current_now while the 10 V was connected to a charger. That only changed after I removed the threshold.
2 Likes
It leads me to a question. Since SailfishOs is not aware of the level of the battery, what happens when the real battery level is 0?
The phone stops brutally and ungracefully?
I tried it the quick route to run AOSP on the Xperia V to check screen brightness, but AOSP refused to boot and hang in a bootloop after flashing.
I can confirm that with different stock Androids (13 and 14) screen brightness is excellent. In Sailfish OS the brightness of the Xperia 10 V is much worse than on Xperia 10 iii. It is definitely not hardware related, since as soon as Android is on the same device, the screen is bright and not dim as on Sailfish.
Would be a pity, if in the final Sailfish release the brightness would not improve.
For me, the screen brightness was one major reason to choose the Xperia 10 V, and hardware is capable.
In the coming days I will definitely not find the time to tackle AOSP and the bootloop further
Hi all,
I am seeking some assistance with the 10V and VoLTE. Any help would be appreciated.
I have a XQ-DC72.
I flashed Sailfish OS to it.
I allowed dual sim as per the suggestion of @chris_bavaria here https://forum.sailfishos.org/t/sony-10-v-sailfish-images/19193/51 .
I am in Australia, and I have an Exetel sim card (Telstra reseller). I cannot get VoLTE to work. This is important considering in a few days that will be the only way to make calls.
So looking around other threads I tried:
getprop persist.vendor.somc.cust.modem0
That did not return any feedback. No S??? was given. Is that expected on this phone, or have a mucked something up with the configuration of the dual sim?
I looked in a table (SonyOpenTelephony/ModemConfig/res/xml/service_provider_sim_configs.xml at master · MarijnS95/SonyOpenTelephony · GitHub) to find out I should be MCC 505 and MNC 01, and thus S38.1.
I looked through /vendor/oem/modem-config/ and that did not show any S38.1 subdirectory.
I also looked though /vendor/firmware_mnt/image/modem_pr/mcfg/configs/ . Unfortunately there was no /AUNZ directory there at all, so no sign of the correct mcfg_sw.mbn, at least I think. I can see from https://xdaforums.com/t/getting-volte-and-vowifi-on-unlisted-carriers-by-flashing-mbn-file.4467745/ that there are at times on some Xperia’s the correct mbn files. Is the one in the .zip attached to that XDA link for the 1III close enough to the 10V to use? If so, how do I go about using it?
So I guess my questions are many, and perhaps it cannot be solved by those here, but in summary:
- Should the
getprop persist.vendor.somc.cust.modem0return a value on the Xperia 10V? - Is there any chance of getting the correct
mcfg_sw.mbnfile for Telstra on the 10V? - If there is, how do I get it to the right spot on the 10V?
Thanks anyone for there input. Hopefully someone has some answers, or perhaps some ideas.
Unfortunately my Sony V 10 (both that I ordered) where broken. So I repaired my XA2 and I am now waiting for the C2.
Anyway, I will save your link!
As we are a Sailfish familiy (my wife is also using Sony and Sailfish), we may need your page later on.
Thank you!
Is anyone able to comfirm the output of
getprop persist.vendor.somc.cust.modem0
on there device? Or the correct equivalent for the 10V
Thanks,
Justin.
I can confirm that getprop did return no value on my Xperia 10 V.
When executing the same comnand on my Xperia 10 iii, the response is
S77.2
Thanks for checking it out - I wonder if that is due to the software’s beta status or if there is an equivalent for the 10V or if the whole VoLTE system is different. Thanks again,
Presumably just different. I can’t imagine these props being anchored in SFOS in any way.
1 Like
Thanks @attah. It seems it might not be worth me trying harder. All indications are that the 10V will be blocked from australian networks regardless of if it works or not based on IMEI.
Will come back to this in a few days if it seems that there may be hope in getting it working in Australia.
I will keep fingers crossed that we can run this device with Sailfish in full effect.
From Hardware perspective it is such a nice device. Sailfish OS can really shine on this device if fully functional.
I did not choose the C2, because I did not buy a non-OLED phone since the Nokia N9, only exception was the BlackBerry Passport.
But for me: no OLED, no buy.
Being blocked from the (Australian) network renders this lovely device useless. But should it be blocked? Who has a benefit out of it?
EDIT - saw in AU thread about current and upcoming changes in AU network. Weird
1 Like
It’s too late for me to keep thinking about this, and it might all be for nothing too - if the device gets blocked.
But here are the AUNZ modem files - proper mcfg-sw.mbn for Australia - Vodafone, Optus and Telstra. These are off the 10IV. I don’t know if they are close enough to put on the 10V, but I was going to try if I could work it out.
Anyone know?
Thanks!
I will not ask for release dates, I’m a software developer myself and hate date related questions, but could you give some feedback on your progress on a usable version for the 10 V? Especially battery handling, camera and android app support would be necessary for me to let it replace my 10 II.
It seems with all the discussions about the C2 the state of 10 IV and V is completely ignored.
1 Like
I think Jolla will be fully occupied on sorting out all the problems with the C2 phone, especially for all those that have non-functioning devices which they have paid for. My guess (and it is only that) is that work on the Xperia 10 iv and v will probably be on the back burner for a while as it is currently only the free version.
1 Like
Additionally, if I understood correctly everyone is waiting for Sony’s new blobs, on the website there are still the ones from August
7 Likes
Currently it is not in our hands. That said, when we have something to deliver as a software update + instructions, we’ll align these also with Sailfish 5 fixes in general.
I’d be happy if can deliver commercial paid versions of 10 IV and 10 V before end of the year.
28 Likes
Thanks for the update and approximate roadmap what to expect.
I will happily pay for a license to take the V to full potential, looking forward to unlock the potential of this great device
8 Likes
OK, found some time and maximm screen brightness on AOSP appears to be somewhere between Stock Android and SFOS 4.6.15 beta.
SFOS is similar to 85% screen brightness on AOSP (non-scientifically judged by eye).
Stock Android has a much, much higher maximal screen brightness.
Next question from my petspective is, if we can estimate what that means for next Sailfish release and maximal screen brightness.
Having experienced what the hardware of the Xperia 10 V under Stock Android can delver in terms of easily readable screen in any environment, it would be sad, if Sailfish OS would cripple this nice device display directly, or indirectly, via an underlying AOSP.
4 Likes