[ROM][T][OFFICIAL] LineageOS 20 for Xiaomi Mi 9 SE [grus]

[givemerobot]

I am experiencing a lot of phone crashes using this rom.
The same happened with kaysu rom but in much less extent.

 

[topongo]

I found this https://forum.xda-developers.com/t/android-11-buffer-fix-by-nullby.4221549/ that is not for Mi 9 SE, it's for the Mi CC9 / Mi 9 Lite, but it worked for me.

But actually the best gcam mod I found and that shoud be newer, fancier and use all three lenses: https://www.celsoazevedo.com/files/android/google-camera/dev-bsg/

It shoots videos but doens't take photos, specifically it shuts but the foto isn't saved to gallery. Did some else had the same issue? Fixes? I'll watch into it later using adb logcat.

 

[shirosaru]

Hello. I have a problem trying to flash this ROM. I try to follow instructions from the official LineageOS wiki, but on the step 5 (Flash empty super image) it does nothing. I type the command
fastboot wipe-super super_empty.img
but I get the output < waiting for any device >
What do I do wrong?

 

[tavoc]

Are you in fastboot mode or ADB?

 

[shirosaru]

In fasboot I guess, I select Advanced, Enter fastboot in Recovery menu

 

[tavoc]

What happenes if your write fastboot devices -l

 

[shirosaru]

What happenes if your write fastboot devices -l

I tried fastboot devices (without -l flag) and it outputted nothing.
I also tried adb devices, and got:

List of devices attached
f1718886        unauthorized

I then tried to skip this step and adb sideload lineage zip, but it failed with an error. So for now I rebooted back into MIUI.

 

[shirosaru]

Soo... A little update. I figured out my problem (kind of...). I tried to repeat all the steps from the beginning, and again after I flashed recovery fastboot couldn't detect my device. So I live-booted into Linux to try install ROM from there, and... all worked. So apparently the problem was somewhere in Windows, maybe some adb/usb drivers or something

 

[Subarashii Árpád]

I assume you have just used an outdated driver or fastboot program version.

Soo... A little update. I figured out my problem (kind of...). I tried to repeat all the steps from the beginning, and again after I flashed recovery fastboot couldn't detect my device. So I live-booted into Linux to try install ROM from there, and... all worked. So apparently the problem was somewhere in Windows, maybe some adb/usb drivers or something

 

[Subarashii Árpád]

I updated to 19.1 Dec. 26. version, and I can no longer use Bluetooth. When I try to open the Bluetooth settings, it is crashing out without any message. I installed Lineage with the previous 19.1 release, and everything worked flawlessly.

This is the crash log (attached jpg), except the 3rd line all of it seems gibberish to me. My phone is rooted with the standard Magisk method, I haven't modified anything else.

Edit: In the meantime, I figured it out from the logs that it was a rooting related issue (Hide My Applist hid Settings app from GMS (Play Services), so I had to fix it).

I considered upgrading to Official Lineage 20, but I am unsure. It may solve my Bluetooth issue, but I don't know whether the GCam will work with it or not. Btw GCam works for me with this patch: Buffer fix by Nullby

Edit: Lineage 20 is pretty stabile. Latest GCam v8.7 from BSG (MGC_8.7.250_A11_V6) works with the same patch.

 

[Kaisar999]

Custom fonts request
This room is incredible, thank you for your hard work is there any way to add custom fonts or can you bring google sans/product sans in next build? Would be appreciated

 

[maross]

I updated to 19.1 Dec. 26. version, and I can no longer use Bluetooth. When I try to open the Bluetooth settings, it is crashing out without any message. I installed Lineage with the previous 19.1 release, and everything worked flawlessly.

This is the crash log (attached jpg), except the 3rd line all of it seems gibberish to me. My phone is rooted with the standard Magisk method, I haven't modified anything else.

Edit: In the meantime, I figured it out from the logs that it was a rooting related issue (Hide My Applist hid Settings app from GMS (Play Services), so I had to fix it).

I considered upgrading to Official Lineage 20, but I am unsure. It may solve my Bluetooth issue, but I don't know whether the GCam will work with it or not. Btw GCam works for me with this patch: Buffer fix by Nullby

Edit: Lineage 20 is pretty stabile. Latest GCam v8.7 from BSG (MGC_8.7.250_A11_V6) works with the same patch.

Hi Subarashii
I experience lagging gcam preview even after applying the patch you mentioned. Did you do anything else to make it go away ?
Thank you

 

[Subarashii Árpád]

Hi Subarashii
I experience lagging gcam preview even after applying the patch you mentioned. Did you do anything else to make it go away ?
Thank you

I have applied it via Magisk (module name: Mi 9 lite Buffer Fix for R). I am using BSG's MGC_8.7.25 build, but it seems like most BSG builds work.
Which method did you use? Flashing via recovery (TWRP) or Magisk? In my understanding, it is a script which copies a file to the vendor partition, so the method shouldn't really matter. Check out Mi 9 lite's Gcam topics, maybe you can find something helpful there.

 

[maross]

I have applied it via Magisk (module name: Mi 9 lite Buffer Fix for R). I am using BSG's MGC_8.7.25 build, but it seems like most BSG builds work.
Which method did you use? Flashing via recovery (TWRP) or Magisk? In my understanding, it is a script which copies a file to the vendor partition, so the method shouldn't really matter. Check out Mi 9 lite's Gcam topics, maybe you can find something helpful there.

Thanks for the reply.

I have flashed it through Lineage custom recovery by using ADB sideload. I will try to flash it through magisk, even though, as you said, it should not matter what method is used. Will try and report back if that worked.

Are you able to use OTA updates when you have magisk installed, or you need to uninstall first before downloading and applying the system update ?

Maros.

 

[Subarashii Árpád]

Thanks for the reply.

I have flashed it through Lineage custom recovery by using ADB sideload. I will try to flash it through magisk, even though, as you said, it should not matter what method is used. Will try and report back if that worked.

Are you able to use OTA updates when you have magisk installed, or you need to uninstall first before downloading and applying the system update ?

Maros.

Try out TWRP at first. And I think Lineage also supports adb root mode, so if you unzip the package, you can also run the script via accessing the shell via adb (never tried out this function, just an idea).
Magisk is a good software, but it takes a few extra steps to hide it from apps like banking apps etc.

OTA update works with Magisk. You just have to reboot, then re-flash the magisk.zip in Lineage's recovery every time. Otherwise nothing happens, but your system will be unrooted, as the Magisk binaries are not present, only the Magisk UI app.
It's not a bad practice to not to install every single update, anyways. It's enough to update in the middle of every months, so you will always get the latest Android Security Update.

 

[Devzerofr]

Hi, I installed lineageOS 20 on my Mi 9 se (without gapps) since 1 week and everything works well ! Thanks for that

But I experiencing an issue with fingerprint, same as described here https://gitlab.com/LineageOS/issues/android/-/issues/4642

It work well during a day and suddenly it not responding (but the green light under screen works) and I need to reboot

I try to disable pocketmode but it not present on this release (LineageOS 20).

 

[maross]

Try out TWRP at first. And I think Lineage also supports adb root mode, so if you unzip the package, you can also run the script via accessing the shell via adb (never tried out this function, just an idea).
Magisk is a good software, but it takes a few extra steps to hide it from apps like banking apps etc.

OTA update works with Magisk. You just have to reboot, then re-flash the magisk.zip in Lineage's recovery every time. Otherwise nothing happens, but your system will be unrooted, as the Magisk binaries are not present, only the Magisk UI app.
It's not a bad practice to not to install every single update, anyways. It's enough to update in the middle of every months, so you will always get the latest Android Security Update.

Hi Subarashii

Just tried to install Magisk and flashed the module you mentioned through it. It works like charm. However, I flashed the same module through Recovery and it did not work - no idea what is the difference.

Either way, thanks for the tip and help

 

[Genius123]

Just installed LOS20 on my mi9se. Runs fine so far.
The only thing I noticed is, that the fingerprint sensor is not as responsive as I am used to it in MIUI original rom. I have to move my thumb over the sensor on the screen before the sensor gets activated.
Furthermore the notch hides the network speed indicator, looks like LOS just ignores the notch.

Other than that, very nice build, thank you!

 

[Genius123]

There's another issue I have right now:
I've got a Cardo Freecom 4X intercom, which I can connect to via bluetooth.
I can listen to music, but I can't control the volume or anything else from the Cardo intercom buttons. I can just control the volume from my mi9se, which is not good, when sitting on my motorcycle.
See EDIT2!

Furthermore the bluetooth apt / aptx profile ist not available.

Any idea if this is fixable?

Thank you!

EDIT: The key for resume music works on my cardo, PAUSE / STOP not.
EDIT2: Just checked another Music Player app, with "Music" the buttons on my Cardo work, on MX Player Pro not. It seems, that the app is the problem not lineageos.

 

[makrei]

Hello! Does anyone here have a backup of the last LOS19.1 build for grus? Please upload it here, I'd like to try multi-lens GCam but it appears none work with LOS20/A13.