A little update, with no definitive information. @Sharks has came up with a helper that seems to achieve a good outcome - it is currently working here. It seems almost ready to work ‘out of the box’, and is very likely to be working when Sharks gets a chance to finalise the changes. So hopefully in a few days, battery ageing protection is finally working on the 10V. Hooray!
To all users of the Zambezi port, please zypper ref && zypper dup - you should then have working charge control per commit 6b818da.
This change adds a helper service which monitors a temporary file controlled by MCE and edits restrict_chg and restrict_cur accordingly, getting around the watchdog.
@juz got the update a day early and was able to confirm overnight charging was sucessfully limited between 78-80%, which is the same behaviour I see on Murray.
Please install the update and let me know how it goes for you! And thanks to @juz and @bardoftruth for your detailed reports of this issue!
I can observe the same as @juz . For me, the charging restriction is now working as expected.
That’s great to hear. Thanks for reporting.
Haven’t been here for a while, now this port is amazing news, especially after having this phone on kinda limited stage for quite some time!
Are there any news I missed on 5G? This would be indeed very useful for me.
And as I read on the meeting logs there will be AAS support or is there already? That’s a requirement for me unfortunately…
Anyway, thanks a lot for this port, now there is hope in sight to finally have a fully working phone ![]()
Hi there @Smirftsch.
Re: 5G, I do not have a 5G service to test with and it seems we expect results to vary by country / area (read from this post). 5G was reported to work in Germany on the basically identical Murray port (further details). 4G & VoLTE however are both fully functional.
Re: AAS, fingers crossed we hear something overnight, Jolla should address it in the community meeting about 10 hours from now.
Re: current status / fully working phone, my current project is fingerprint support, no promises yet but I’m getting closer every day. Hope to have it shipped in a few weeks. Other outstanding issues I’m also still working on, no ETA yet but they haven’t been forgotten. Bluetooth audio in calls particularly is something I want to sort out sooner rather than later, but the device is certainly at a state currently where it can be used as a primary phone if you do not require AAS.
At yesterday’s community meeting, Jolla again committed to bringing AppSupport to community ports, specifically the 10IV and 10V community ports initially. They also noted that their first steps would be to bring A15 based AppSupport to the C2, and then hopefully this work would allow them to take the next step of bringing AppSupport to the 10IV and 10V. So I wouldn’t hold your breath, Jolla’s soon™ can sometimes be not so soon. Also, they stopped short of saying they were going to be doing the work of getting it going, so it might not be in the bag yet. However, to me, as a user of this currently very good port, it is reassuring and positive messaging. Something to look forward to, I guess. So if you are thinking of trying this port for the 10V, I couldn’t recommend it more highly as a solid reliable option, and AppSupport might appear in the (distant?) future.
Anyone having problems to connect wifi5 or wifi2.4 with wlan roaming enabled?
What do you mean by “wlan roaming” - as in a mesh network? I have not tested that use case, but I’ve also not done anything special with regards to the WiFi adaptation.
Do you see any authentication failures etc. in the journal logs relating to wpa_supplicant / connman / etc?
‘mesh’ is not exact name for this, it is commercial name mostly used by tplink and others.
i mean roaming between multiple APs: 802.11r, 802.11k and 802.11v
it is working fine with jolla port, also tested during flashing in android 14, then tested in lineage - all fine, but in SF it says cant connect, tomorrow i will post messages from journal. on the AP (i use openwrt firmwares) i have seen authenticated, but then nothing and after some time disconnect
tried to create another wlan on the openwrt without roaming at 2.4GHz and it was without problem, did not tried same on 5GHz. will try tomorrow
but tested that i also can not connect to my AP from the provider (gigacube 5G router), there is no roaming just basic wifi with same name for 2.4GHz an 5GHz, i think that phone tried to use 5GHz band and failed too. - will test temporaly disable 5GHz to isolate if it is AP related isue or trully 5GHz and 802.11r for 2.4 and 5 too
so in sum i can connect without issues to 2.4GHz hotspots from other phones, or basic APs
the rest of the port is absolutely perfect in compare to jolla port, BT works fine, device is not overheating without reasons, LTE, VoLTE, 5G works fine.
thank so much for making thins port. and i hope you setup some https://ko-fi.com so we can buy some for you ![]()