[OFFICIAL][ROM][PAYTON]LineageOS 20 (Android 13)

[rhcohen]

Build of 0131 (today) failed with messages:

failures/payton/f3a139dc1cc944ad9eda5918ad010823/

Failed to add the ECDSA host key for IP address '167.71.188.173' to the list of known hosts (/root/.ssh/known_hosts).

Failed to add the ECDSA host key for IP address '167.71.188.173' to the list of known hosts (/root/.ssh/known_hosts).

android-sync.log 100% 7577 73.5KB/s 00:00

Failed to add the ECDSA host key for IP address '167.71.188.173' to the list of known hosts (/root/.ssh/known_hosts).

android-build.log 100% 17MB 11.2MB/s 00:01

Build on 0124 (last week) failed with same messages. Same error messages also fore some other devices.

So, if nobody looks after these errors, build next week will fail again.

Did the builds fail because of this error or some other one? It is an SSH error, and Googling it I find that for some other projects it is not fatal.

 

[ThE_MarD]

Unfortunately the fix for Lineage Updater's Prioritize Update Process broke our kernel so a fix for that was needed

I've uploaded a test build here if someone can confirm it works fine

lineage-20.0-20230131-UNOFFICIAL-payton

Release lineage-20 lineage-20.0-20230131-UNOFFICIAL-payton - lineageos-for-payton - OSDN

Release lineage-20 lineage-20.0-20230131-UNOFFICIAL-payton - lineageos-for-payton #osdn

osdn.net

 

[rseiler]

@ThE_MarD Thanks for finding that. Was it just blind luck that 0124 never came out then? What would have happened on upgrade with a broken kernel?

In any case, I tried this unofficial build, and nothing blew up. Everything still seems to work fine (well, except for the narrow Verizon issue mentioned above, but that's unrelated). The only thing that I noticed that I think is new: subtle shifts in the brightness (this was at night), but I disabled Adaptive Brightness to fix that. Not that I know if that was on before, since I never gave it any thought, but I assume it was. I didn't see anything about it in the release notes, but there are a lot of them and they're not always overly descriptive.

 

[ThE_MarD]

@rseiler thanks for testing it

Tbh Android 12 sucks for automatic brightness lol... It definitely messed with a lot of devices. Heck, even my Motorola Edge 30 which launched with A12 and I tried those values on LOS? It's super dark most of the time so I just chopped out a bunch of the minimum brightness values and upped the LuX values a bunch to help compensate because automatic brightness was super broken

We could try and modify our values for Payton if you find it's too dark? I could do a test build with a similar change to this:

dubai: Modify automatic brightness values · LineageOS/[email protected]

The values extracted from Stock ROM are quite dim on average and the minimum brightness is low, So let's remove the three minimum light sensor values on config_autoBrightnessLevels and the bott...

github.com

 

[paukenschlag]

I've uploaded a test build here if someone can confirm it works fine

Just installed on my bike phone without add-ons as an upgrade using LOS recovery. No problems so far.

 

[woodpe]

I also installed the test build and everything seem to work fine.
Thanks

 

[rseiler]

@ThE_MarD Appreciate the offer, but the brightness levels are fine for me. It can go really low or incredibly bright, but around 40% is good most of the time indoors.

I think what I noticed last night might have been me stumbling on Adaptive Brightness for the first time, since it turns out, as you probably knew, that you can enable it quite accidentally via the brightness slider (there's a little gear that appears on it. and tapping it will turn it into an "A,," meaning Adaptive Brightness has just been enabled). Adaptive Brightness seems possessed for me, changing brightness multiple times a minute, so I'll just keep it off, no loss.

 

[spyblue]

Hi guys! Thank you for this great rom! It mostly working but bank apps are not, even after install Magisk, Shamiko and Universal Safety Net fix.

I tried to Logcat the errors but it's does not show what may be.... anyone have a clue please?


Regards

 

[woodpe]

@spyblue:
My banking app works fine.
Did you in Magisk
activate Zygisk
Enforce DenyList
Configure Denylist?

 

[dougo007]

If you look at your Phone info screen now (* # * # 4636 # * # *), at the Voice Network Type line, I'd be curious what it says (and it would be really interesting to know back on stock, but too late for that). In September, on a working LOS, mine said "1xRTT," which I'm reading is a technology associated with 3G and CDMA (and something that's now gone). That probably explains why the line reads "Unknown" today, because without VoLTE it's stymied. I imagine yours says something else on that line, but is it what it should be given that yours is not completely working yet?

Update: Just to address some of my own questions, for "fun" today I went back to stock, because last year when I was on stock I had already moved to LOS before ever properly provisioning the phone., explaining why last year the voice part was using 1xRTT.

Anyway, that went well:
-VoLTE was Provisioned and enabled (and also appears as a live toggle in the main Verizon area in Settings)
-"Mobile voice network type" was LTE, as was the data network type, answering the above question.
-IMS Status was Registered
-Calling and texting was working fully.

Then I went from there to the final 19.1 version and as expected all things continued to be well, and there was even one improvement, as "Wifi Calling Provisioned" went to Enabled.

On Tuesday, I'll go to the new build of 20 and expect to hit the wall then...but who knows, maybe not.

Update 2: I have now upgraded to 20 (20230117) and can confirm the earlier findings mentioned up the thread. Outgoing texts are the only thing that stopped working despite all indicators looking exactly as they did in 19.1 (VoLTE on, etc), when everything was fully working. The stock text program says "Can't send message with Verizon. Error 0." while Google's says "Can't send. This recipient's phone number can't be confirmed. Error code 0."

Update 3: A workaround, of sorts, is to use RCS instead of SMS (RCS uses a different system than SMS and is more like chat). Google Messages, for example, supports RCS when you're fully opted in to its "Chat features" function, as seen in its Settings. Not everyone supports RCS though on the other end, but it's better than 100% of your texts failing.

I wanted to drop a note on this. I'm still using my Moto X4 that I got from a few years back and am on the Verizon Post-Paid network. I am using HAVOC w/ Android 10, to my recollection the pre-installed Messenger app did NOT work but QKSMS does, so I use that on my phone instead. I hope that helps.

 

[spyblue]

@spyblue:
My banking app works fine.
Did you in Magisk
activate Zygisk
Enforce DenyList
Configure Denylist?

Did all this, nothing worked!
I am an advanced user, I even tried to decompile the bank app but didn't work.
How can I debug it to check what is the problem? I already tried Logcat but found nothing.

 

[rseiler]

Did all this, nothing worked!
I am an advanced user, I even tried to decompile the bank app but didn't work.
How can I debug it to check what is the problem? I already tried Logcat but found nothing.

You also leveraged Magisk's rename function, installed the SafetyNet fix, and froze Magisk? If after doing that and clearing data on the bank app doesn't work, then this is probably the thread to go further:

[Discussion] Magisk - The Age of Zygisk.

This is a discussion and help thread for the newer versions of Magisk. The main goal of this thread is to help users migrate to Magisk v24+ SafetyNet Basic integrity Pass CTS profile match Pass Play Protect certification Device is certified...

forum.xda-developers.com

 

[rseiler]

Just a heads up, I assume thanks to @ThE_MarD, that the first official build in some time is now available:

lineage-20.0-20230207-nightly-payton-signed.zip

 

[ThE_MarD]

Thanks @rseiler but it's mainly thanks to you guys reporting it that it was fixed. Juggling 6 devices with whatever spare time I get for this hobby doesn't always pan out... Tbh, I seem to get more spare time when I'm at work than I do oh days off lol... But it isn't a big margin there either

 

[skiwarz]

I have verizon phone service. I'll back up what others have said - I needed to revert to stock and then re-install 20 in order to make calls and texts work. Specifically, the "ensuring all firmware partitions are consistend" step of the instructions is what is needed, for anyone wondering. Still can't SEND sms messages however. Calls, mms, and receiving sms all work.

 

[rseiler]

@skiwarz I have no explanation why VoLTE went off for you. It should show as on in the hidden menu (albeit greyed out) and on (and accessible) in the normal Settings/Verizon area. Only suggestion I can make is when you're back on stock, check the hamburger menu on the hidden screen you mentioned to check your provisioning status there.

Note that even if it was on when you got to LOS20, you'd still have the outgoing SMS problem, unless you can crack that problem, which no one has so far (outgoing RCS definitely works and apparently so does MMS, though I didn't test that). If you're one who actually uses SMS and can't depend on everyone having RCS, you might stick to 19.1 for now.

 

[wkn000]

Thanks @ThE_MarD , you did it again!

With this build from today, would i be able to "try" for next OTA in System Updater with process option enabled?

 

[skiwarz]

@skiwarz I have no explanation why VoLTE went off for you. It should show as on in the hidden menu (albeit greyed out) and on (and accessible) in the normal Settings/Verizon area. Only suggestion I can make is when you're back on stock, check the hamburger menu on the hidden screen you mentioned to check your provisioning status there.

Note that even if it was on when you got to LOS20, you'd still have the outgoing SMS problem, unless you can crack that problem, which no one has so far (outgoing RCS definitely works and apparently so does MMS, though I didn't test that). If you're one who actually uses SMS and can't depend on everyone having RCS, you might stick to 19.1 for now.

Sorry to mislead you. I completely re-wrote my comment as you were typing this, I assume. My error was not re-running the copy-partitions update before flashing lineageos. That fixed it, except for outgoing sms as others have said lol.

 

[rseiler]

@skiwarz That's good, though I certainly hadn't heard of that particular flavor of problem as a result of not doing the copy. I thought it only impacted when you do an OTA, and in a much more significant way than what you found (the phone won't boot, which you would have found later).

 

[frustro]

Hi all, I thought I would share.
Latest adb/fastboot
NET10 /Verizon
Moto X4 Android One, Project Fi.
Start with latest OEM Pie 9
Factory wipe/reset 2x via OS GUI 2x via Recovery.

Perform bootloader unlock process
1x OS and 1 Recovery wipe/reset.
I installed Lineage-20.0-20230117* , copy-partitions-20220613-signed.zip and Mind the Gapps following the official guide.

Calls both directions work fine, VoLTE works.

Native SMS app inbound works outbound fails.

Attempt to disable Automatically Detect Network opens dialogue "couldn't find networks, try again"

Updater notification for lineage-20.0-20230207-nightly-payton-signed.zip
2x failed install.
Installed when Prioritize Update Process disabled.

1x OS and 1 Recovery wipe/reset.

Native SMS app inbound works outbound fails.

I don't believe I have anything new to add that isn't already known. I'm just throwing my hat in the ring.