Sometimes they skip one week. It happened before. We should see another one next Monday.
2 weeks I would say. This is the start of the 3rd week..
19.0 stuff threw us off for a short time, then an APK edit to fix some telephony bugs resulted in signing issues. Will be fixed by next build
Thanks for the update, hope the telephony stuff incls lower call volume, personally I'd be happy enough with monthly updates (assuming no significant bugs need fixing), especially if it's due to Lineage 19 dev! Thanks again for your work.
Thanks you so much to letting this device keeps having update. I am having a question about the volte. May I know that whether it is working or not? As I see in the settings, it has enabled but seems not working. The ims is registered, but volte is unavailable.
Works for me in the UK. Unfortunately, LineageOS ROMs don't show the volte logo
It works on stock rom. But it seems that the new build makes volte work again. Thanks.
Ok. But where's the setting? Can't find it anywhere. Used to be under system > status bar
- Your warranty is now void.
- You have been warned.
- Use at your own risk.Works in Google maps here....
weird - can't replicate in youtube, file a bug ticket as per the wiki instructions please?
uhhh - sounds like you need to wipe data - something sounds messed up.
Just follow the wiki guide and all will work fine.
you need to format /data and just follow the wiki guide, thing shouldn't crash, so long as you use lineage, and (if you want) mindthegapps
please don't discuss other ROMs here - go elsewhere for that.Try crDroid, although not official but OP update regularly and the rom is stable, good enough for daily useage.
[ROM][10.0][UNOFFICIAL][MATA][microg][VoLTE][WireGuard] crDroid v6.19
*** Disclaimer I am not responsible for any...forum.xda-developers.com
please don't discuss other ROMs here - go elsewhere for that.
Their firmware fix is placebo - it's the same firmware - I'm looking into the webview issue, and strongly suspect it'll be fixed in the next build (newer webview version built in).
Apologies, sepolicy mismatch after a merge on the qcom-common sepolicy repo. I've fixed it, the next build will not have this issue!
Apologies, sepolicy mismatch after a merge on the qcom-common sepolicy repo. I've fixed it, the next build will not have this issue!
Apologies, sepolicy mismatch after a merge on the qcom-common sepolicy repo. I've fixed it, the next build will not have this issue!
Apologies, sepolicy mismatch after a merge on the qcom-common sepolicy repo. I've fixed it, the next build will not have this issue!
Apologies, sepolicy mismatch after a merge on the qcom-common sepolicy repo. I've fixed it, the next build will not have this issue!
Apologies, sepolicy mismatch after a merge on the qcom-common sepolicy repo. I've fixed it, the next build will not have this issue!
cool. it's not a huge deal. i just turn the call volume up and hold it away from my head. it's speakerphone'ish. thanks for the work you all do
There's a bug ticket open for it, unsure what the cause is, but we know about it and are trying.@npjohnson since you seem to be involved with the development of LOS, do you have any idea what's going on, on phone calls, with the loud speakerphone that doesn't respond to the volume keys? i can't remember, anymore, which versions of essential's builds had the same problem and i never read anything about what they did to fix it. i do remember that it wasn't an immediate fix.
the fact that it did exist in essential's builds, oi LOS17.1, and now in LOS18.1, makes me think that it's something deeper than a ROM typically goes. but that is just my not-understanding-the-nuts-and-bolts-of-things thought.
