[ROM][OFFICIAL][ginkgo][10] LineageOS 17.1 for Redmi Note 8 / 8T

[iozho]

Also there is another issue (which causes UI restart). Crash in resolver.

*** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
LineageOS Version: '17.1-20210719-NIGHTLY-ginkgo'
Build fingerprint: 'xiaomi/ginkgo/ginkgo:10/QKQ1.200114.002/20.7.9:user/release-keys'
Revision: '0'
ABI: 'arm64'
Timestamp: 2021-08-11 07:23:48+0300
pid: 606, tid: 30299, name: netd >>> /system/bin/netd <<<
uid: 0
signal 7 (SIGBUS), code 2 (BUS_ADRERR), fault addr 0x7775290000
x0 000000777528ffed x1 000000000000000a x2 000000000007263a x3 0000007775290000
x4 000000000000001a x5 0000000040100401 x6 0000000000000000 x7 000000000000e000
x8 00000000000118b9 x9 000000000000000d x10 000000000000000d x11 0000000000000000
x12 ffffffffffffffff x13 0000000000000039 x14 6f8711007faa8e48 x15 0000000000000068
x16 00000077887f83c8 x17 00000077895dbef0 x18 0000007775c08000 x19 000000000000003c
x20 000000777528ffec x21 000000777528ffec x22 000000777528ffed x23 0000007779127020
x24 000000000021dfce x25 0000000000014831 x26 000000777530263a x27 0000000000000020
x28 0000007775072000 x29 0000007779126840
sp 0000007779126760 lr 00000077886cdd30 pc 00000077895dbf50

backtrace:
#00 pc 000000000007df50 /apex/com.android.runtime/lib64/bionic/libc.so (memchr+96) (BuildId: bf14cf7a62d1f91755beddd4a937354d)
#01 pc 000000000004dd2c /apex/com.android.resolv/lib64/libnetd_resolv.so (_hcfilemmap()+524) (BuildId: 93ad0890938908dd44a07a9699e045ff)
#02 pc 000000000004d858 /apex/com.android.resolv/lib64/libnetd_resolv.so (hc_getaddrinfo(char const*, addrinfo const*, addrinfo**)+92) (BuildId: 93ad0890938908dd44a07a9699e045ff)
#03 pc 0000000000048aa4 /apex/com.android.resolv/lib64/libnetd_resolv.so (android_getaddrinfofornetcontext(char const*, char const*, addrinfo const*, android_net_context const*, addrinfo**, android::net::NetworkDnsEventReported*)+2432) (BuildId: 93ad0890938908dd44
a07a9699e045ff)
#04 pc 000000000005d224 /apex/com.android.resolv/lib64/libnetd_resolv.so (android::net:nsProxyListener::GetAddrInfoHandler::run()+240) (BuildId: 93ad0890938908dd44a07a9699e045ff)
#05 pc 0000000000061650 /apex/com.android.resolv/lib64/libnetd_resolv.so (void* android::netdutils::runAndDelete<android::net:nsProxyListener::GetAddrInfoHandler>(android::netdutils::runAndDelete<android::net:nsProxyListener::GetAddrInfoHandler>)+16) (BuildId:
93ad0890938908dd44a07a9699e045ff)
#06 pc 00000000000e2390 /apex/com.android.runtime/lib64/bionic/libc.so (__pthread_start(void*)+36) (BuildId: bf14cf7a62d1f91755beddd4a937354d)
#07 pc 0000000000083ab0 /apex/com.android.runtime/lib64/bionic/libc.so (__start_thread+64) (BuildId: bf14cf7a62d1f91755beddd4a937354d)

stack:
00000077791266e0 0000000000000000
00000077791266e8 d5ac6cc16dd354a2
00000077791266f0 0000007779126a50
00000077791266f8 0000000000000000
0000007779126700 0000007779126a10
0000007779126708 0000007779127020
0000007779126710 0000007788c4a5c0 [anon:libc_malloc]
0000007779126718 000000000029063a
0000007779126720 00000077887f9028 [anon:.bss]
0000007779126728 00000000000a4188
0000007779126730 0000007779126750
0000007779126738 000000778959e354 /apex/com.android.runtime/lib64/bionic/libc.so
0000007779126740 000000000000003c
0000007779126748 000000000000003c
0000007779126750 0000007779126840
0000007779126758 00000077886cdcf8 /apex/com.android.resolv/lib64/libnetd_resolv.so
#00 0000007779126760 0000000000010337
................ ................

Never mind regarding this issue - it turned out it is an android bug. I used AdAware which modified /etc/hosts file while function hcfilemmap() in libc is using advisory lock hence the race issue.

 

[kevinsatria]

I feel the battery drain faster approximately 5 hours SOT using social media apps only, is it normal?

 

[general.nie7]

I feel the battery drain faster approximately 5 hours SOT using social media apps only, is it normal?

In my case it's 10h SOT, but mine is degoogled.

 

[adamuadamu]

hi, just tried to flash latest nightly over previous build via TWRP and my phone keeps restarting to recovery. What are recommended steps to update to a newer build?

EDIT: nevermind, I tried to tamper with the ROM as the compass turned out to behave really oddly - i.e. no stable direction no matter what. After efortlessly flashing newest firmware files, trying factory reset and wiping data and internal memory, I ended up going back to LOS16 and surprise - using the same fw files the compass seems to behave correctly and overall ROM smoothness seems to improve. So - staying with LOS16, I don't care about numbers thanks for hard work maintaing LOS for our device(s)!

 

[Zep0th]

latest magisk not working properly, due to this, netflix and other banking apps not showing on playstore, what version do i need of magisk? help.

 

[velocitysages]

latest magisk not working properly, due to this, netflix and other banking apps not showing on playstore, what version do i need of magisk? help.

fix safetynet,

 

[madeskjet]

Redmi Note 8T
lineage-17.1-20210823-nightly-ginkgo-signed.zip

No work fingerprint.

 

[Zep0th]

Latest ROM bootlop, even after clean flash.

 

[Kostareka]

Bootloop after clean flash

 

[tablord]

I too have issues with the bootloop (after clean flash).

What is really weird and frustrating: This bootloop occurs with any LOS17.1 no matter the version or date. I checked several versions from 2020 and 2021 and also the microg versions (from https://download.lineage.microg.org/ginkgo/). No matter which Recovery (TWRP or OrangeFox) I use to wipe/format data and install or if I install a MIUI 11 or MIUI 12 ROM xiaomi.eu before. It always ends in the same bootloop.

What is even more absurd: I can flash pretty much any other custom rom including LOS18.1, crDroid or ArrowOS successfully and without any bootloop problems.

An exactly identical RN8T that a friend uses has received LOS17.1 early on in 2020 and has not had any issues at all, despite having received monthly updates. The later being the same ROM.zips that I failed to clean install on my RN8T without getting a bootloop...

I'd really love to have an explanation and at best a solution for that

 

[tablord]

Latest ROM bootlop, even after clean flash.

Bootloop after clean flash

Have you also tried older ROM versions and maybe the LOS17.1 microg versions (from https://download.lineage.microg.org/ginkgo/)? Different Recoveries (OrangeFox, TWRP)?

 

[Zep0th]

Have you also tried older versions and maybe the LOS17.1 microg versions (from https://download.lineage.microg.org/ginkgo/)?

Yup, nothing is working, tried every recovery possible.

 

[oneser]

I too have issues with the bootloop (after clean flash).

What is really weird: This bootloop occurs with any LOS17.1 no matter the version or date. I checked several versions from 2020 and 2021 and also the microg versions (from https://download.lineage.microg.org/ginkgo/). No matter which Recovery (TWRP or OrangeFox) I use to wipe/format data and install or if I install a MIUI 11 or MIUI 12 ROM xiaomi.eu before. It always ends in the same bootloop.

What is even more absurd: I can flash pretty much any other custom rom, including LOS18.1, crDroid or ArrowOS successfully and without any bootloop problems.

I'd really love to have an explanation and at best a solution for that

I had a similar issue. Found it was a 12.xx update and MIUI made a change to the boot image.
There is a link to the custom TWRP here:

[RN8] Problems with TWRP recovery

I need some advice and or possibly an explanation on what I did wrong and if possibly some solution. I had some errors in TWRP after the latest weekly (20.12.09) installation (Cannot read.., Operation not permitted) but the decryption was working as usual -in Official TWRP 3.4.0-1. I decided to...

xiaomi.eu

 

[[email protected]]

Hi, I tryed both LOS17.1 and LOS18.1. I found LOS17.1 works well with old XIAOMI firmware, while LOS18.1 works well only with latest xiaomi firmware. I was on 17.1, made clean flash of 18.1 and nothing worked until flashed latest firmware...
Maybe the cause of bootlops could be the firmware...

 

[tablord]

Hi, I tryed both LOS17.1 and LOS18.1. I found LOS17.1 works well with old XIAOMI firmware, while LOS18.1 works well only with latest xiaomi firmware. I was on 17.1, made clean flash of 18.1 and nothing worked until flashed latest firmware...
Maybe the cause of bootlops could be the firmware...

What exactly do you mean with "old XIAOMI firmware"? Which one exactly?
I tried various MIUI 11.x and 12.x firmwares, all to no avail. Somewhere I read that changes to boot.img might have caused the (bootloop) issues so maybe I should have tested even older MIUI 11 firmwares from say 2020-08 or older. But now I have already switched to LOS18.1 meaning no more testing for me at the moment...

 

[temblor55]

Try this guys to fix ov13b10 camera

 

[tomacto]

Hi there. I'm having a problem updating to the latest version, 20th September 2021, (from v. 16 Aug 2021.)

I download the update and click to install, it does it's pre-reboot processing of the update without error but then on reboot fails the signature verification in recovery.

I see:
E: footer is wrong E: Signature verification failed E: 21

I can reboot back into the old system okay, but have tried to redownload and re-run the update a couple of times now and get the same error.

Anyone else with the same problem or insights on anything I can try.

Thanks.
T.

 

[pastapesto]

Hi there, my microphone doesn't work in signal and whatsapp voicemails– sometimes when i call somebody with the dialer app too. i tried some record apps. some work fine, others don't. the "background-noisy-sound" is the same as in the messenger-apps. if the recording app allows to change the input, it actually work fine then. the video in the "open camera" app for example also doesn't have any sound but if i go to settings --> video settings --> audio source and then change to "camcorder" everything works fine.
does anybody else have such microphone problems? thank you in advance

ps: no gapps, no microg, root via magisk

 

[pastapesto]

Hi there, my microphone doesn't work in signal and whatsapp voicemails– sometimes when i call somebody with the dialer app too. i tried some record apps. some work fine, others don't. the "background-noisy-sound" is the same as in the messenger-apps. if the recording app allows to change the input, it actually work fine then. the video in the "open camera" app for example also doesn't have any sound but if i go to settings --> video settings --> audio source and then change to "camcorder" everything works fine.
does anybody else have such microphone problems? thank you in advance

ps: no gapps, no microg, root via magisk

edit: is it possible, that i have to "downgrade" my firmware? before flashing LOS about 3 days ago i updated the stock rom (so i think android 11). does the firmware have to match to android 10 in this case?

my actual baseband-version: MPSS.AT.4.3.11-00270-NICOBAR_GEN_PACK-1.380402.1.388696.6

and to make my issue clearer:
Phone: Redmi 8T
LineageOS version:
lineage-17.1-20210920-nightly-ginkgo
LineageOS Download url:

https://mirrorbits.lineageos.org/full/ginkgo/20210920/lineage-17.1-20210920-nightly-ginkgo-signed.zip

Gapps version:
no gapps installed

Did you--
wipe:
yes, installed like described in official installation guide
restore with titanium backup:
no
reboot after having the issue:
yes

Are you using--
a task killer: no
a non-stock kernel: no?
other modifications: rooted with magiskv23; no google services

 

[[email protected]]

edit: is it possible, that i have to "downgrade" my firmware? before flashing LOS about 3 days ago i updated the stock rom (so i think android 11). does the firmware have to match to android 10 in this case?

my actual baseband-version: MPSS.AT.4.3.11-00270-NICOBAR_GEN_PACK-1.380402.1.388696.6

and to make my issue clearer:
Phone: Redmi 8T
LineageOS version:
lineage-17.1-20210920-nightly-ginkgo
LineageOS Download url:

https://mirrorbits.lineageos.org/full/ginkgo/20210920/lineage-17.1-20210920-nightly-ginkgo-signed.zip

Gapps version:
no gapps installed

Did you--
wipe:
yes, installed like described in official installation guide
restore with titanium backup:
no
reboot after having the issue:
yes

Are you using--
a task killer: no
a non-stock kernel: no?
other modifications: rooted with magiskv23; no google services

maybe it could be the firmware... i had similar problem passing from 17.1 to 18.1, see my post...