Thanks for the information,
I did reflash from Android_14_5.4_V3a_zambezi to Android_13_5.4_v4b_zambezi
Now the battery status indicator is woking
for flashing I used:
I try Software binaries for AOSP Android 14.0– Kernel 5.10- Zambezi (v5a),
first seem good because in fact the downloarded file is: SW_binaries_for_Xperia_Android_14_5.4_v5a_zambezi.img
and we want kernel 5.4,
first it seems to work like Android_13_5.4_v4b_zambezi,
but after 10 minutes I had crash while running an Android app.
Not really sure why you are so upset, the NSA advice is for android users, if android devs decided to implement it at driver level and softly push users to reboot once a week as their drivers become unstable after few days/week, you would be experiencing exactly the same thing with sfos or any other linux that is on top of android drivers, this wasn’t snarky, it was full on tinfoil hat, cheers
I will only re-state what I said many times: jolla needs to drop sony, unreliable partner shitting out non-working blobs that only give fuel for negative nancies like you, cya (get a C2 and enjoy sfos as it should be, no weekly restart needed)
I am reading the issues people face with the C2 … it doesn’t sound enjoyable at all.
Now laughter aside, I am considering buying it just for fun … I bought so many sh*t phones (last one was PinePhone), which are completely useless. I guess I can open a museum or at least an exhibition.
Anyway … for now the 10 II is working more or less fine with 4.4.0.72. May be end of the year, it will be time to buy a new one.
I will wait to see how C2 develops and what feedback I get. Otherwise I consider also buying the Volla with Lineage OS. I have few friends using it and are very satisfied. I hope I’ll have the time in the summer to prepare the transition to NextCloud for my contacts and calendars.
Dude C2 is close to C1 in support, pls go ahead and mention what was not working on C1, we have whole week, think hard, C2 is the same, J devs got access to drivers and it is already smoother experience than sony AOSP™ XIII, while having 3x slower cpu/gpu, geee what people can achieve without sony 3rd rate team that can’t be counted on to do no typos, kek
And seriously if you are angry about sony blobs/aosp state how about you send Sony some angry words instead of shitting this forum instead? I know very weird ask
Yes 10 II is working fine most of the time. From time to time sound disappears, fingerprint daemon needs restarting,Android (AlienDalvik) restarts etc.
But it is the best I have and I got used to.
Pragmatically seen it is a crap, but I have one use case that makes me use it so far.
Having 3rd rate sony team and 1st rate Jolla seems compatible to me
I don’t have C1 - no idea what you mean … I read posts here of people who have severe issues especially with the new SFOS v5 … so I will wait until Q4 this year and will decide what I’ll do. I do not have time anyway to “play” with new toys now.
If they manage to release C3 before my 10 IV dies I’ll gladly change, for now I patiently wait for working sfos. Thought it’s really foolish of me to say this few months after C2 got released.
Edit 1:
…but it has now frozen completely 3 times. So probably worth waiting for an official update on the matter if it is just not an experiment device.
Edit 2:
After flashing the binaries one more time, it seems to work much better.
No, you don’t get it, Sony is specifically keeping two teams as separate so there is no open source controversy/cross pollination (aosp team member copied some of closed source team member’s code from a meeting etc), you can compare their ‘rates’ from how sony’s closed versions work vs their open versions, it’s in the open and it shows, jolla should not waste time on this bs anymore until sony cleans up their act
You’re linking to when sony B team finally releases a workable product vs when jolla team releases theirs, they already released a very workable/usable C2 while we’re still waiting for sony, so not sure C3 is needed, a proper aosp release for IV/V might come never