Without the proper tools, no. But you can edit the dtbo to modify the refresh rate's value. Only problem is, I don't know how you can do that.
Surely they will be problems. With how well ROM works, I wouldn't touch anythingWithout the proper tools, no. But you can edit the dtbo to modify the refresh rate's value. Only problem is, I don't know how you can do that.
According to the installatiom instructions I need to "Flash the latest Android 11 firmware of your device variant". Where do I download this firmware? And what command to install it?
It works for me now, thanks! (Redmi k20 Pro 8/256)Greetings everyone! For those who are having troubles with LineageOS recovery rebooting into fastboot mode please flash this LineageOS recovery and verify if this works for you.
Thanks for your reply! Waiting for any other feedback.
Didn't work for me. I'm using LineageOS 19 with latest twrp. Phone boots, logo shows and goes off...Greetings everyone! For those who are having troubles with LineageOS recovery rebooting into fastboot mode please flash this LineageOS recovery and verify if this works for you.
Thanks for your reply. I would like feedback from someone who actually uses LineageOS 20 built by me not from someone else.Didn't work for me. I'm using LineageOS 19 with latest twrp. Phone boots, logo shows and goes off...
Same thing with the recovery from OP.
Ah ok. Well, I've tried to flash 20 but didn't work also. I guess installing it is missing some step.Thanks for your reply. I would like feedback from someone who actually uses LineageOS 20 built by me not from someone else.
Reading the release information I advice you never flash DFE zips.I have DFE and the January version. Upon update will I have to reflash dfe?
I have installed it. It has entered Recovery LineageOs, before it had not succeeded. At the moment everything is correct. Next update, I'll try it better.Greetings everyone! For those who are having troubles with LineageOS recovery rebooting into fastboot mode please flash this LineageOS recovery and verify if this works for you.
The question is clear. I am not looking for advice. I just don't want the rom to play tricks on my Data partition.Reading the release information I advice you never flash DFE zips.
It does work now , Mi 9T Pro 6/128Greetings everyone! For those who are having troubles with LineageOS recovery rebooting into fastboot mode please flash this LineageOS recovery and verify if this works for you.
Thanks for your feedback! It seems that the issue is eliminated for all users.I have installed it. It has entered Recovery LineageOs, before it had not succeeded. At the moment everything is correct. Next update, I'll try it better.
The release notes are also crystal clear. The ROM itself "won't play tricks" with your data partition as long as you don't **** things up.The question is clear. I am not looking for advice. I just don't want the rom to play tricks on my Data partition.
Never mind, when this time comes I'll just reflash dfe to be sure.
Thanks for your feedback! It seems that the issue is eliminated for all users.
I'm using the default AOSP values, it can be tweaked though.Thanks once again for your work. The only issue (if we can call it that) for me is that the night light is too bright, even at its maximum intensity. No biggie though, I use the very outdated f.lux app, that still do its job.
You have to manually update the recovery. Making it updating automatically means I have to force LineagOS recovery for everyone.Hello @Englezos
if I use the internal update function, will the recovery be updated automatically or do I always
Auto nightlight on scheduled time is fixed for the next release. About the status bar notification issue did you reported it to LineageOS team? It seems this implementation behaves like that for notch devices.Hey, thanks so much for the great ROM. I would appreciate if you could take a look at these issues:
I use auto night light on a scheduled time and on the latest update, for some reason it's reversed, it turns on when it should turn off vice versa. (User workaround is to reverse times too)
And this is a long standing bug, that I think was mentioned before, when the clock is in the middle of the status bar, it works ok for a while but then the notifications start behaving like the clock is on the left corner. So there's a blank space in the corner and if you have a lot of notifications, they overlap with the clock
About VoLTE ringback tone reports maybe its carrier dependant? I've seen couple reports online on devices like Google Pixel, Oneplus and Xiaomi. I've tested that personally on iPhone 12, Redmi Note 6 pro and Google Pixel 6a none of these devices had ringback tone when VoLTE functionality was enabled on my carrier. Any suggestions is welcomed.I also have this issue. Only happens ringing other mobile users who have VoLTE enabled.
I've installed dropbox and logged in successfully.Hello, thanks for this rom, really loving it. But for some reason I can't use dropbox app, after login screen it's shows nothing, after restart it doesn't get through start up screen with logo.
About VoLTE ringback tone reports maybe its carrier dependant? I've seen couple reports online on devices like Google Pixel, Oneplus and Xiaomi. I've tested that personally on iPhone 12, Redmi Note 6 pro and Google Pixel 6a none of these devices had ringback tone when VoLTE functionality was enabled on my carrier. Any suggestions is welcomed.When I make an outgoing call, there's no ringing sound. There's just silence for several seconds until the other person answers. Has anyone else experienced this?
EDIT: After a bit of testing, I've worked out that it only occurs when ringing mobile numbers (not landlines) and with VoLTE enabled. As soon as VoLTE is disabled, I hear the ringing sound.
I also have this issue. Only happens ringing other mobile users who have VoLTE enabled.When I make an outgoing call, there's no ringing sound. There's just silence for several seconds until the other person answers. Has anyone else experienced this?
EDIT: After a bit of testing, I've worked out that it only occurs when ringing mobile numbers (not landlines) and with VoLTE enabled. As soon as VoLTE is disabled, I hear the ringing sound.
Just did an OTA update from January version to May version without any problems.
I'll only needed to reflash the latest recovery by hand (as I only was booting to fastboot).
But now Magisk isn't detected by the magisk manager app, I've reflashed magisk trough the recovery (adb sideload magisk.zip) but still, the magisk manager doesn't detect it.
Anyone got an idea how to solve this problem?
So far I've tried:
- reflashing Magisk 26.1 (and installing the corresponding manager)
- flashing Magisk 25.2 (and installing the corresponding manager)
- clearing the cache of the manager
- clearing the device cache via recovery
EDIT:
- patching the boot.img via the manager and reflashing also doesn't work (tried with magisk 25.2 and 26.1)
Also, the sideloading procedure in the recovery said that everything was working (found ramdisk, patched boot.img, flashed boot.img)