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

Rycow

New member
Nov 12, 2020
4
0
0
The ROM itself rund great. Any luck running Google Pay?
I pass the safetynet test and have google services and google pay hidden with magisk. Still won't allow me to pay contactless due to device not meeting some standards.
Also settings regarding NFC payments are not available (like change to HCE and so on).
How did you pass the safetynet? Im having problem with this

Helping would mean a lot to me
 

Rycow

New member
Nov 12, 2020
4
0
0
Dear @DarkJoker360 do OTA updates work? if using Gapps and TWRP (God bless @mauronofrio ), what is the correct procedure?

Thanks.
I actually just did OTA update yesterday. I am having gapps and TWRP running and they would just ask you to install and it'll lead directly to TWRP where it would automatically install the update. Reboot to system and the update is done
 

M.Tullius

Member
Jul 21, 2019
41
0
6
I actually just did OTA update yesterday. I am having gapps and TWRP running and they would just ask you to install and it'll lead directly to TWRP where it would automatically install the update. Reboot to system and the update is done
What can I say.. wonderful job and ROM.
 

velocitysages

New member
Oct 29, 2020
1
0
1
I actually just did OTA update yesterday. I am having gapps and TWRP running and they would just ask you to install and it'll lead directly to TWRP where it would automatically install the update. Reboot to system and the update is done
Did you faced error block.map on twrp when install update via OTA?
 

Bumbee6

New member
Dec 15, 2017
3
0
1
For me there is an issue using volume control via wired headphones on the latest build. Playback start/stop works fine. Volume keys do nothing. I came from Resurrection Remix and the same setup worked out of the box there. I found "Volume Control" in the Lineage settings. It is activated, but has no effect. Can anyone else reproduce this?
 

xmasman

New member
Feb 18, 2011
3
0
21
Family Link for Kids not working

Hello,

i tried to sign in my kid, but it says i have to update the OS.
I tried it with different OpenGapps (Nano, micro, mini, stock), but it didn't work.
I have used the latest LineageOS Version 20201110.

With the latest MIUI 12 does it work.

Any solution for me?

Thanks!

Greets
xmasman
 

xmasman

New member
Feb 18, 2011
3
0
21
Do you mean that you are stuck on an updating screen ?

Maybe the opengapps zip is corrupted, did you try to re-download the nano package, or with no gapps at all ?

No, if i want to login with the google credentials, it checks, that the account is from my kid. Then it says to use it, i have to update the OS.
When i login with my google credentials, it works fine.

Normally after login with the credentials from my child, it will ask for my credentials and install Google Family Link for children.

I tried different Gapps. Also it works with the old phone of my kid. Galaxy S4 with LineageOS 17 and nano Gapps.
 

majadoo

Member
Apr 23, 2020
10
0
0
There is still problem with the phone hanging and rebooting when switching from Wi-Fi to mobile data on the newest build.

Also, how can I use the speaker cleaning feature from MIUI on this ROM? Is there an app that can do that?
 

Uluru25

Member
Nov 27, 2016
38
2
18
Never having used Lineage but being very concerned of privacy I always rooted my phones to protect them with XPrivacy (Lua). Unfortunately, XPrivacy Lua will not be adapted to Android versions beyond 10.

Thus, I am checking to switch to a different custom ROM which will not need XPrivacy. I understood that LOS is featured with an inbuilt feature called privacy guard.

Please, could anybody comment whether the LOS "privacy guard" works equivalent to XPrivacy. What will I miss if coming from XPrivacy.

Thanks a lot for any little help.
 

MotoXT1032

Member
May 24, 2020
6
0
0
Just flashed the rom on my willow. Everything works great except for two issues.
First, it seems that I can't get 4G+, only 4G. Already had this issue on the build of LOS 17 from tarkzim and others android 10 ROMs. I thought the official android 10 firmware would fix this issue but it didn't.
Second, it seems that sensors doesn't work properly. For example, screen rotation doesn't work. I downloaded the app 'sensors toolbox' to check if my sensors are working properly but it can't find any sensor except battery, gps and wifi...

I tried several firmwares versions, even downgraded to android 9 firmware, but it didn't change anything. So I believe there is an issue with the ROM, or my phone in particular...
What kind of info could I provide to help figuring out this issue ?

Thanks for your great work nonetheless, I really appreciate this official LineageOs support.

Small update: re-did a clean install by wiping everything AND formating data, no luck :(
Going to try CAF Android 11 next
 
Last edited:

gr8Tomato

Member
Nov 8, 2016
21
3
0
I have data working, I think its LTE I'm not sure but it works well enough for me, and screen rotation is working perfectly fine personally... But! My phone lags and freeze since last update. Anyone has this too? I'm not sure if its because of an update of the web browser or the ROM itself. That and screen ghosting are the main issues I have.
 

MotoXT1032

Member
May 24, 2020
6
0
0
Okay, somehow managed to fix my sensors issues by flashing official MIUI 12 ROM then after full wipe and flashing LOS17 my sensors are finally recognised. Still no clue about that 4G+ issue, it seems like event MIUI 12 does not get it so...

Anyway I'm happy to finally be able to use Android 10 LOS daily :D
 

2faraway2

Senior Member
Apr 24, 2016
150
19
18
Tried the latest build with very good results (thanks @DarkJoker360 :)) regarding stability and performance.
Nevertheless I found 2 major issues in terms of navigation / location services:

- No other gnss except gps (LOS can't 'see' any glonass or beidou satellites)
- Network location (gsm or wifi) doesn't work. Neither with google play services nor with microG.
For navigation only gps is used ..

Someone out there with similiar experiences ?
Any idea how to fix that or recommendations for a workaround ?
 
Last edited: