I updated to the most recent version today (19.11), skipping 2 or 3 previous builds. Now I have a bug were only the speaker works during a call. I cannot switch to the normal phone speaker.
Am I alone with this?
hello;
i do have last week update (the previous one)ā and i do not have the issue. i can hear in the ear speaker.
1 Like
Hi, if you mean that youāre only on loudspeaker, with no possibility to switch to the ear speaker, so yes, I noticed that too (but if use jack earphones, and bluetooth speakers, these work).
I thought it was some mishandling from my part that I didnāt have time to investigate.
On this note, Iāve experienced intermittent disconnections between my phone and the carās Bluetooth system for many years, perhaps since the beginning of my FP3 days ā I donāt recall. Sometimes, this occurs in the middle of a conversation. Itās very inconvenient. Am I the only one?
1 Like
About Android 16, I have seen that lineageos have added basic support to mainline kernel, mainline kernel have some improvement on FP3 and FP3+ (Luca weiss @z3ntu) have added camera support!!! Maybe this can be a solution in the long therm? (Sure not tomorrow).
Nov 19ās update fixed the problem for me.
Weird. For me it introduced the problem. Will try next weekās version. Maybe that fixes it againā¦
Nevermind. I donāt know why, but yet another reboot resolved it.
1 Like
maybe related to the issue iām facing sometimes where plugging headphones jack makes android crash and restarting but itās not a cold reboot since it crashes again when I plug again. The issue disappears when I reboot the phone until it appears again later.
Hereās the unfortunate news for all FP3/3+ LineageOS users.
With the release of 25Q4(Android 16 QPR2), it has been decided that there will be no support for devices running 4.4 and 4.9 kernels since the minimum kernel requirement has been raised to 5.10.
Hence, I had to abandon my bpf attempt.
But the good news is lineage-22.2 branch will continue to receive security updates for 2 more years.
Thank you all for your support once again.
9 Likes
Would it not theoretically be possible to update the FP3/+ all the way to 23.1 still, which includes a lot of quality of life improvements ? Or is that not possible because we then wouldnāt get security updates past 23.1 ?
To be fair though I donāt know if the FP3/+ would have handled Android 16ās new design changes very well, with all the blur and new animations potentially being a bit rough on the phone.
I say that because Iāve noticed since Android 15 the quick settings and notification shade have intense framerate drops whenever the music player notification is visible, which as far as I can tell might be linked to the āfogā animation that was added when tapping the play button, even when said animation is not visible.
I seem to remember at once point this issue to have been resolved or dampened somehow but it has very clearly re-appeared since then, might it be possible to remove or disable this animation so the notification shade doesnāt run at 10 fps whenever playing music ?
On an unrelated note, Iāve noticed issues and glitches with the GPS taking extremely long to start (or not starting at all) and applications sometimes not picking it up for a bit now, have any of you experienced this, or is it a known hardware or software issue ?
Similarly my FP3 has a LOT of trouble to autofocus on any app besides the native camera app, to the point it is practically impossible to scan QR codes; here again, have any of you experienced this, or is it a known hardware or software issue ?
Thanks a lot to everyone for your support and being part of this community, and thanks @TeamB58 for the OUTSTANDING work you have done for us over the years - I never got the occasion to tell you this before, so I really wanted to add that here. If I werenāt broke asf currently Iād definitely tip you a fair bit for all that work, but may I know if you have a donation page for future reference ?
2 Likes
This is a real pity, but thank you very much for trying (and for all these years). I will definitely keep using this phone until the end.
@Lurux yes, GPS got kinda slow to āconnectā at some point this year I think, but eventually it always works. I canāt really give meaningful feedback on the cameras, as the rear one has always been kinda sh*t for me and the front one Iāve never used.
2 Likes
Hmmm so Iāve only started meaningfully using the GPS a few months back but I vaguely remember it being faster to load in the past, are you implying there might indeed be a software issue here ?
Are you also experiencing the framerate drops in the notification shade when the music player notification is visible ?
Just a wild though but is it plausible to ever upgrade the phoneās kernel to keep it updated for longer ? My understanding is this is not anywhere near standard practice in the Android sphere (if even ever seen before), but would that theoretically be possible ?
That is a damn shame. Thank you for the very appreciated attempt to get the FP3 to Android 16. it would have been cool to be able to use the phone safely for longer. That means that I have to replace this phone in two years time. Maybe a FP7 then?
2 Likes
Same here. Loading up Waze, can take up to a couple of minutes to adjust. So I got the habit to launch it even before I leave home.
Again, same here, I often get blurry pics, even with the native LOS camera app. Its gets worse in low light.
Has the GPS issue always been there or is it a recent one and I just so happen to have started using it more meaningfully since then ?
As for the camera personally the native LOS camera app works fine.
Also have you experienced the framerate drops in the notification shade when the music player notification is visible ?
Thanks a lot for this. Sure, itās here.
After reading your overwhelming response(nice to see there are atleast 2-3 loyal users of LineageOS for FP3) it makes me feel that I should not give up.
I have raised this request again with the 4.9 qcom maintainers and shall hope that some maintainers would volunteer so that we could continue maintaining the 23.0 branch at least.
Fingers crossed, Iāll update you all if something happens related to this.
Thanks once again.
8 Likes
@TeamB58 I still hope that mainlining the kernel will solve this, in the mean time we will use android 15. Thank you (*^^*)
Thanks again over your hard work over the past few years <3 <3 <3