[ROM][T][mata] Unofficial, optimized LineageOS 20 - June 3rd

[Tomoms]

@Tomoms

For some reason after flashing the 3/11 build, there is an update available for the same build. Same size too. Updating doesnt change anything. It goes through the whole process but the build stays the same and the same update is available again. The updater is showing 2/17 as the current build. Weird.

Screenshots attached.

Yes, this happens because it looks like there are two separate build timestamps. One is updated every time a new flashable zip of the ROM is generated (this is the one you see under "LineageOS version" in your second screenshot), while the other is apparently only changed on full rebuilds (or more precisely, when "some" build artifact is changed during compilation - I don't know which one(s) exactly). The latter one is still set to February 17th because I do incremental builds (thus not every artifact is regenerated during compilation), and you can notice this also looking at "Build number" in your second screenshot. I suspect the updater looks at this timestamp and compares it to the compilation timestamp (i.e. the first I mentioned) of the build available via OTA, and since the compilation timestamp is ahead, an update is offered.
I could try to change the updater's behaviour in order to avoid this, but I honestly don't care too much about it. It's something you can simply ignore. Just look at "LineageOS version" in About phone to make sure you're on the latest build.

Has anyone tried the dual speaker mod on lineage 20? Need to know before going forward with it.

Never tried this, sorry. But now I'm curious! I'll take a look at it in the next few days.

 

[LineArc]

Yes, this happens because it looks like there are two separate build timestamps. One is updated every time a new flashable zip of the ROM is generated (this is the one you see under "LineageOS version" in your second screenshot), while the other is apparently only changed on full rebuilds (or more precisely, when "some" build artifact is changed during compilation - I don't know which one(s) exactly). The latter one is still set to February 17th because I do incremental builds (thus not every artifact is regenerated during compilation), and you can notice this also looking at "Build number" in your second screenshot. I suspect the updater looks at this timestamp and compares it to the compilation timestamp (i.e. the first I mentioned) of the build available via OTA, and since the compilation timestamp is ahead, an update is offered.
I could try to change the updater's behaviour in order to avoid this, but I honestly don't care too much about it. It's something you can simply ignore. Just look at "LineageOS version" in About phone to make sure you're on the latest build.


Never tried this, sorry. But now I'm curious! I'll take a look at it in the next few days.

Thank you, I am very much interested. Can't try coz I am using my essential as my main phone.

 

[morphius88]

Yes, this happens because it looks like there are two separate build timestamps. One is updated every time a new flashable zip of the ROM is generated (this is the one you see under "LineageOS version" in your second screenshot), while the other is apparently only changed on full rebuilds (or more precisely, when "some" build artifact is changed during compilation - I don't know which one(s) exactly). The latter one is still set to February 17th because I do incremental builds (thus not every artifact is regenerated during compilation), and you can notice this also looking at "Build number" in your second screenshot. I suspect the updater looks at this timestamp and compares it to the compilation timestamp (i.e. the first I mentioned) of the build available via OTA, and since the compilation timestamp is ahead, an update is offered.
I could try to change the updater's behaviour in order to avoid this, but I honestly don't care too much about it. It's something you can simply ignore. Just look at "LineageOS version" in About phone to make sure you're on the latest build.


Never tried this, sorry. But now I'm curious! I'll take a look at it in the next few days.

I dont really care either as long am I am on the latest build. I will try the dual speaker mod shortly as I am interested in that as well.

 

[Tomoms]

Hi,
a new build is available, now LineageOS has integrated the latest Android T QPR2, which also brings March's security patches.
Unfortunately a new visual bug has appeared, and I have no idea why: there is no black/gray background in the pull-down notification menu (below the quick settings tiles). The background is transparent, and as a consequence the notifications are superimposed on the currently active app. It doesn't affect functionality but is quite ugly to see. I apologize for the annoyance, I'm trying to address this as quickly as possible.

@morphius88 I suggest that you don't flash the stereo speaker mod at the moment. I've checked it out and it could potentially introduce audio-related issues in your phone, as the modifications it introduces are not tailored to the PH-1. I will write a better version of the mod in a couple of days, and post it here.

 

[morphius88]

Hi,
a new build is available, now LineageOS has integrated the latest Android T QPR2, which also brings March's security patches.
Unfortunately a new visual bug has appeared, and I have no idea why: there is no black/gray background in the pull-down notification menu (below the quick settings tiles). The background is transparent, and as a consequence the notifications are superimposed on the currently active app. It doesn't affect functionality but is quite ugly to see. I apologize for the annoyance, I'm trying to address this as quickly as possible.

@morphius88 I suggest that you don't flash the stereo speaker mod at the moment. I've checked it out and it could potentially introduce audio-related issues in your phone, as the modifications it introduces are not tailored to the PH-1. I will write a better version of the mod in a couple of days, and post it here.

Sounds good. I will be on the lookout for that. I think I will also hold off on the new build for now or maybe I can try to fix the background issue by messing around with something like Project Themer.

 

[temporarium]

Hi,
a new build is available, now LineageOS has integrated the latest Android T QPR2, which also brings March's security patches.
Unfortunately a new visual bug has appeared, and I have no idea why: there is no black/gray background in the pull-down notification menu (below the quick settings tiles). The background is transparent, and as a consequence the notifications are superimposed on the currently active app. It doesn't affect functionality but is quite ugly to see. I apologize for the annoyance, I'm trying to address this as quickly as possible.

@morphius88 I suggest that you don't flash the stereo speaker mod at the moment. I've checked it out and it could potentially introduce audio-related issues in your phone, as the modifications it introduces are not tailored to the PH-1. I will write a better version of the mod in a couple of days, and post it here.

Thank you for your continued work on this device, and for the heads-up on potential issues. I'll also hold off till this is resolved.

 

[Tomoms]

Sounds good. I will be on the lookout for that. I think I will also hold off on the new build for now or maybe I can try to fix the background issue by messing around with something like Project Themer.

Thank you for your continued work on this device, and for the heads-up on potential issues. I'll also hold off till this is resolved.

Well, you guys need not wait any longer. I've released another build which addresses that issue

 

[morphius88]

Well, you guys need not wait any longer. I've released another build which addresses that issue

Sweet! The option of using Themer did not work anyway. Neither did AOSP Mods.

 

[danz852]

Hi, thanks for the rom. I have problem when using WhatsApp video call. I can hear the voice of ppl on the opposite but they can't hear my voice. I need to end the video call and restart the call to make it work.

And one more thing related to WhatsApp. When using WhatsApp's Fingerprint Lock, sometimes it work the other times it's not working.

Does anyone have the same problems with voice on WhatsApp video call and WhatsApp's Fingerprint Lock?

 

[Tomoms]

Hi, thanks for the rom. I have problem when using WhatsApp video call. I can hear the voice of ppl on the opposite but they can't hear my voice. I need to end the video call and restart the call to make it work.

And one more thing related to WhatsApp. When using WhatsApp's Fingerprint Lock, sometimes it work the other times it's not working.

Does anyone have the same problems with voice on WhatsApp video call and WhatsApp's Fingerprint Lock?

While I was sure I had addressed all audio issues in the past, a few users (such as you) are still facing some. I'll check and see what I can do. If you could provide me with a logcat taken after a WhatsApp video call, it'd be great.
It seems weird to me that WA's fingerprint lock works only sometimes. I've never used this feature, but I'll enable it now to test it.

 

[danz852]

While I was sure I had addressed all audio issues in the past, a few users (such as you) are still facing some. I'll check and see what I can do. If you could provide me with a logcat taken after a WhatsApp video call, it'd be great.
It seems weird to me that WA's fingerprint lock works only sometimes. I've never used this feature, but I'll enable it now to test it.

Thanks for the reply.
At the moment, I think WA video call audio issue gone after I restart the phone several times. I hope it stay that way.

WA's fingerprint lock still randomly working. Not a big deal as I can still use Lineage Hidden & Protected app.

 

[temporarium]

@Tomoms , to go from your lineage 19 to this latest one, do you think a dirty upgrade will work (without wiping data)?

 

[Tomoms]

@Tomoms , to go from your lineage 19 to this latest one, do you think a dirty upgrade will work (without wiping data)?

@MuddyDog tried this with one of my very first LineageOS 20 builds, and it worked.
@danz852 if the audio issue comes back, do grab a log though. It'll be useful for me.

 

[MuddyDog]

hi, as @Tomoms said, a dirty upgrade from his 19.1 to his very early 20 build worked smoothly.

but... i'm not reckless enough to have done that without a complete backup on hand. i don't recall whether i used Google Backup or Swift Backup.

also, @Tomoms current build has merged QPR2 and the Updater installs this build correctly. But, both @Tomoms and i found that going back to a previous build to do some checks (pre-QPR2 to QPR2) resulted in a lot of breakage. i think @Tomoms rolled back, while i just switched slots and rebooted.

so, @Tomoms newest build is really great, the Updater works fine, and i can't think of a reason to downgrade back to 19.1.
but be advised that going back to an earlier build will require a clean reinstall... and keep a healthy backup handy.

 

[temporarium]

hi, as @Tomoms said, a dirty upgrade from his 19.1 to his very early 20 build worked smoothly.

but... i'm not reckless enough to have done that without a complete backup on hand. i don't recall whether i used Google Backup or Swift Backup.

also, @Tomoms current build has merged QPR2 and the Updater installs this build correctly. But, both @Tomoms and i found that going back to a previous build to do some checks (pre-QPR2 to QPR2) resulted in a lot of breakage. i think @Tomoms rolled back, while i just switched slots and rebooted.

so, @Tomoms newest build is really great, the Updater works fine, and i can't think of a reason to downgrade back to 19.1.
but be advised that going back to an earlier build will require a clean reinstall... and keep a healthy backup handy.

Thanks for the feedback. Yes, backups without question. Just want to save time by not having to reconfigure everything again.

 

[Tomoms]

Thanks for the feedback. Yes, backups without question. Just want to save time by not having to reconfigure everything again.

Yes, I have faced strange problems when rolling back after the QPR2 merge.
Sometimes I also faced visual glitches after normal 20->20 updates, but this only happened on some private testing builds I keep for myself. Builds released on xda are always free from these issues.
So in the end, I'd say you have a 95% probability of success. This is not official LineageOS, I don't want nor can give absolute guarantees of any kind, this is why I'm saying 95% and not 100%.

 

[temporarium]

Yes, I have faced strange problems when rolling back after the QPR2 merge.
Sometimes I also faced visual glitches after normal 20->20 updates, but this only happened on some private testing builds I keep for myself. Builds released on xda are always free from these issues.
So in the end, I'd say you have a 95% probability of success. This is not official LineageOS, I don't want nor can give absolute guarantees of any kind, this is why I'm saying 95% and not 100%.

Well, the dirty upgrade went smoothly - all seems to work... EXCEPT: no DNS resolution! As a result, no network at all! This is with the latest stable (March 21), though I also tried latest beta (March 26) with same results...

Mobile works, and Wifi connects and shows strong signal. I can ping my router by IP, but can't ping any hostname. I've tried different options under Private DNS (including Off and Automatic, of course). I've restarted numerous times. I've cleare the cache. I've uninstalled and reinstalled Adguard (which updates the filters correctly - must be by direct IP).

Any thoughts/suggestions?

 

[izombiev]

While I was sure I had addressed all audio issues in the past, a few users (such as you) are still facing some. I'll check and see what I can do. If you could provide me with a logcat taken after a WhatsApp video call, it'd be great.
It seems weird to me that WA's fingerprint lock works only sometimes. I've never used this feature, but I'll enable it now to test it.

I would say that every single custom rom for this phone has suffered from this. I used your version right after facing such bugs on another LOS maintainer, but your visual bugs drove me nuts (no offense).
Yeah, such bug seems to disappear right after a reboot but it's just a matter of time before you're again at it.
Regarding this, I've been using LOS 19.1 for as long as a week and I can guarantee that this does not exist here.
Restarting the phone every time this happens is not a big deal, but it does happen like 10 min. after the phone boots up xD

 

[Tomoms]

Well, the dirty upgrade went smoothly - all seems to work... EXCEPT: no DNS resolution! As a result, no network at all! This is with the latest stable (March 21), though I also tried latest beta (March 26) with same results...

Mobile works, and Wifi connects and shows strong signal. I can ping my router by IP, but can't ping any hostname. I've tried different options under Private DNS (including Off and Automatic, of course). I've restarted numerous times. I've cleare the cache. I've uninstalled and reinstalled Adguard (which updates the filters correctly - must be by direct IP).

Any thoughts/suggestions?

Side note: don't flash the beta builds unless you're told so. They can be potentially dangerous. Though you've been lucky: it is not the case of the 03-26 one.
We can surely fix your problem.
Can you ping by IP a server outside your local network?
Please reboot the phone and grab a logcat after it has booted up.

I would say that every single custom rom for this phone has suffered from this. I used your version right after facing such bugs on another LOS maintainer, but your visual bugs drove me nuts (no offense).
Yeah, such bug seems to disappear right after a reboot but it's just a matter of time before you're again at it.
Regarding this, I've been using LOS 19.1 for as long as a week and I can guarantee that this does not exist here.
Restarting the phone every time this happens is not a big deal, but it does happen like 10 min. after the phone boots up xD

What visual bugs are you talking about?
I'm waiting for the log

 

[izombiev]

Side note: don't flash the beta builds unless you're told so. They can be potentially dangerous. Though you've been lucky: it is not the case of the 03-26 one.
We can surely fix your problem.
Can you ping by IP a server outside your local network?
Please reboot the phone and grab a logcat after it has booted up.

What visual bugs are you talking about?
I'm waiting for the log

I will install your rom once again, Sir, in order to get logs and get this bug (audio one) fixed once and for all. I was talking about the transparent notification panel and the one that made me wanna cry was lock screen messages, which, despite being fully charged/disconnected from the charger, the phone kept showing "unlock to use all functions"; "charged" messages.