[ROM] [OFFICIAL] crDroidAndroid for Redmi 9 / Poco M2 (lancelot, galahad, shiva)

Search This thread

Evan_Ferrao

Member
Aug 12, 2020
45
128
Redmi Note 9
BE3pE0l.png

Code:
*** Disclaimer
I am not responsible for any damage you made to your device
You have been warned


crDroid is designed to increase performance and reliability over stock Android for your device also attempting to bringing many of the best features existent today


Features:
https://github.com/crdroidandroid/crdroid_features/blob/11.0/README.mkdn

Read (THIS) If You Have Issues With Dialer App

Flashing Instructions:

Pre-installation:
[*]IMEI-BACKUP-SCRIPT (Download from here)
[*]FIRMWARE (Download from here)

#KEEP IMEI BACKUP IN SAFE PLACE, ITS IMPOSSIBLE TO COMPLETELY RESTORE IMEI IF LOST!


First time installation:
  • step 0: Make Sure You Have IMEI Backup, Take From link above
  • step 1 : Assuming You Have Your Bootloader Unlocked Already, Go to fastboot mode, Flash recovery(shrp in this case)
  • step 2: Reboot To Recovery, Format Dalvik, Art Cache And Cache, Click on format data --> type yes
  • step 3: Flash Your Device FW(skip if on MIUI Android 11), then Flash crDroidAndroid Zip
  • step 4: Flash The Suggested Gapps Package(optional)
  • step 5: If you want magisk, flash after you've setup the phone from the setup wizard

Update installation:
  • step 1: If You're On Non-OSS rom, Or OSS-Q rom, Follow "First Time Installation" Guide
  • step 2: First Unroot Your Device!(**IMPORTANT**), Now Assuming Youre on OSS-R Rom, or an Old Crdroid Build, Reboot To Recovery, Format Dalvik, Art Cache And Cache
  • step 3: Flash crDroidAndroid Zip
  • step 4: Flash The Suggested Gapps Package(optional)
  • step 5: If you want magisk, flash after you've setup the phone from the setup wizard


Sources:
ROM: https://github.com/crdroidandroid
Kernel: kernel url

Download:
ROM Download-Link
Changelog: Changelog


Visit official website @ crDroid.net
Support Group(Telegram)
crDroid Community Telegram
crDroid Updates Channel
Donate to help our team pay server costs
 
Last edited:

kongtapapple

New member
May 12, 2019
3
4
Redmi 9
Followed the installation instruction, everything has been smooth so far. Played some game and the performance is great. Prop to the maintainer for writing such detail instruction rather than having me search though everything on my own. Keep it up!
 

Ironheist6

Member
Feb 20, 2019
6
2
Redmi 9
Xiaomi 11 Lite 5g NE
Can someone tell me how is the stability?
Like the camera and is the issue of low volume when calling still there on this ROM?

Please do let me know as im very much in need to escape MIUI and try something better

Thank you.
 

Ironheist6

Member
Feb 20, 2019
6
2
Redmi 9
Xiaomi 11 Lite 5g NE
And im on MIUI 12.5.1 android 11.

Do i have to downgrade or something in order to flash this ROM because when i flashed other custom ROM it did require me to downgrade to miui 12.0.2 android 10

Thank you in advance.
 

rambomhtri

Senior Member
This custom ROM is probably one of the best in terms of customization, it passes safety net, it's certified, OTA works, it is smooth... I think I've tried one before that was a tiny bit smoother, but I would not give everything else for a bit more fluidity. I think I'm staying with this ROM for good. I recommend you flash latest 12.5.1 FW A11 before flashing this ROM.
 

blast_beat_ns

Member
Nov 3, 2015
18
2
Novi Sad
Thanks for info. I must find some solution for that volume custom ROM problem since MIUI gives me headache with WiFi problem that has no solution.
 

morfikov

Senior Member
Oct 22, 2016
162
52
Warsaw
morfikov.github.io
Redmi 9
Fist of all I don't use GAPPS, only microG installed via Magisk. Everything seems to be working just fine except two things.

1. It looks like something is wrong with sensors. Compass shows wrong directions (I use the Trial Sense app, form F-Droid) and also the position (x-y) of the phone seems to be switched (it can be visualized better in the Bubble lvl in the app) -- it wrongly recognizes horizontal/vertical angle, apparently it thinks the right-left plane of the phone is the top-bottom one. When I hit the compass icon in the phone's nav bar, it hangs the whole phone after 10-20 seconds. There's no way to switch the icon back to the off state, and I have to reboot the phone.

2. The volume buttons on my earphones don't work. The only button that seems to work is the power one. The phone's hardware buttons seem to work without issues. I tried two different earphones (connected via minijack and also the usb-c port), and I got the same result, which is I can't change volume via the buttons. Pressing vol+ or vol- on the earphones seems to be issuing a tap action on the screen, so for instance I can tap on a Firefox icon using either one of the volume buttons.

Does anyone experience such behavior?
 
  • Like
Reactions: OverkillSRB

morfikov

Senior Member
Oct 22, 2016
162
52
Warsaw
morfikov.github.io
Redmi 9
It looks like the camera also have issues. Nothing what you would see while using it, but when you start any camera app, for instance the stock one, or OpenCamera, you will get the following spam in logs (this scrolls the output at the speed of light):

Code:
10-01 22:51:41.228   721   823 E android.hardware.sensors@2.0-service-mediatek: akm_log Enter wrapper_set_mag
10-01 22:51:41.228   721   823 E android.hardware.sensors@2.0-service-mediatek: akm_log lili_akm_wrapper_set_mag(uT) , -79, -108, -421,
10-01 22:51:41.228   721   823 E android.hardware.sensors@2.0-service-mediatek: akm_log AKM_SetData time_stamp = 3574390682790, stype = 1
10-01 22:51:41.228   721   823 E android.hardware.sensors@2.0-service-mediatek: akm_log lili_setData_gprm(uT) , 459, -530, -573,
10-01 22:51:41.228   721   823 E android.hardware.sensors@2.0-service-mediatek: akm_log lili_setData_data(uT) , -79, -108, -421,
10-01 22:51:41.228   721   823 E android.hardware.sensors@2.0-service-mediatek: akm_log lili_setv_mag(uT) , 459, -530, -573,
10-01 22:51:41.228   721   823 E android.hardware.sensors@2.0-service-mediatek: akm_log setv_mag-hdt_ag(msQ4) = 320
10-01 22:51:41.228   721   823 E android.hardware.sensors@2.0-service-mediatek: akm_log lili_Enter DOEEX Calib
10-01 22:51:41.228   721   823 E android.hardware.sensors@2.0-service-mediatek: akm_log AKM_SetData time_stamp_afterSetVector = 3574390682790, stype = 1
10-01 22:51:41.228   721   823 E android.hardware.sensors@2.0-service-mediatek: Enter AKL_CalcFusion
10-01 22:51:41.228   721   823 E android.hardware.sensors@2.0-service-mediatek: akm_log pg_mag_lili(uT): 28, -33, -35, -1, 6, 7, dt: 320
10-01 22:51:41.228   721   823 E android.hardware.sensors@2.0-service-mediatek: akm_log pg_mag(uT): 320, 459, -533, -571, -76, 460, dt: 554
10-01 22:51:41.228   721   823 E android.hardware.sensors@2.0-service-mediatek: akm_log akm_pg_amp_limit, akm_d6d_phone_state is 1
10-01 22:51:41.228   721   823 E android.hardware.sensors@2.0-service-mediatek: akm_log lili_pg_gyr(d/s*16*1000): -2246, -420, -1494, dt: 320
10-01 22:51:41.228   721   823 E android.hardware.sensors@2.0-service-mediatek: Enter if, typeis: 1
10-01 22:51:41.228   721   823 E android.hardware.sensors@2.0-service-mediatek: akm_log save data:2,2
10-01 22:51:41.228   721   823 E android.hardware.sensors@2.0-service-mediatek: PGLILI TimeStamp:3574390682790, PGLILI Mag data:-79.650002, -108.900002,-421.800018 ,
10-01 22:51:41.228   721   823 E android.hardware.sensors@2.0-service-mediatek: akm_log AKM_GetData lili_time_stamp_GetData:3574322956760, stype =1, ,
10-01 22:51:41.228   721   823 E android.hardware.sensors@2.0-service-mediatek: akm_log akl_getv_mag(uT) , 27, -31, -34, Lv: 2
10-01 22:51:41.228   721   823 E android.hardware.sensors@2.0-service-mediatek: akm_log akl_getv_mag(uT) offset: -107, -76, -387
10-01 22:51:41.228   721   823 E android.hardware.sensors@2.0-service-mediatek: akm_log AKM_GetData time_stamp11=3574390682790, stype =1
10-01 22:51:41.228   721   823 E android.hardware.sensors@2.0-service-mediatek: akm_log akm_wrapper_calibrate is 27.539999, -31.980000, -34.259998
10-01 22:51:41.228   721   823 E android.hardware.sensors@2.0-service-mediatek: akm_log Enter wrapper_set_mag
10-01 22:51:41.228   721   823 E android.hardware.sensors@2.0-service-mediatek: akm_log lili_akm_wrapper_set_mag(uT) , -80, -108, -422,
10-01 22:51:41.228   721   823 E android.hardware.sensors@2.0-service-mediatek: akm_log AKM_SetData time_stamp = 3574410679463, stype = 1
10-01 22:51:41.228   721   823 E android.hardware.sensors@2.0-service-mediatek: akm_log lili_setData_gprm(uT) , 459, -533, -571,
10-01 22:51:41.228   721   823 E android.hardware.sensors@2.0-service-mediatek: akm_log lili_setData_data(uT) , -80, -108, -422,
10-01 22:51:41.228   721   823 E android.hardware.sensors@2.0-service-mediatek: akm_log lili_setv_mag(uT) , 459, -533, -571,
10-01 22:51:41.228   721   823 E android.hardware.sensors@2.0-service-mediatek: akm_log setv_mag-hdt_ag(msQ4) = 319
10-01 22:51:41.228   721   823 E android.hardware.sensors@2.0-service-mediatek: akm_log lili_Enter DOEEX Calib
10-01 22:51:41.228   721   823 E android.hardware.sensors@2.0-service-mediatek: akm_log AKM_SetData time_stamp_afterSetVector = 3574410679463, stype = 1
10-01 22:51:41.228   721   823 E android.hardware.sensors@2.0-service-mediatek: Enter AKL_CalcFusion
10-01 22:51:41.228   721   823 E android.hardware.sensors@2.0-service-mediatek: akm_log pg_mag_lili(uT): 28, -33, -35, -1, 6, 7, dt: 319
10-01 22:51:41.228   721   823 E android.hardware.sensors@2.0-service-mediatek: akm_log pg_mag(uT): 319, 462, -532, -570, -76, 460, dt: 554
10-01 22:51:41.228   721   823 E android.hardware.sensors@2.0-service-mediatek: akm_log akm_pg_amp_limit, akm_d6d_phone_state is 1
10-01 22:51:41.228   721   823 E android.hardware.sensors@2.0-service-mediatek: akm_log lili_pg_gyr(d/s*16*1000): -1955, 279, -1909, dt: 319
10-01 22:51:41.228   721   823 E android.hardware.sensors@2.0-service-mediatek: Enter if, typeis: 1
10-01 22:51:41.228   721   823 E android.hardware.sensors@2.0-service-mediatek: akm_log save data:2,2
10-01 22:51:41.228   721   823 E android.hardware.sensors@2.0-service-mediatek: PGLILI TimeStamp:3574410679463, PGLILI Mag data:-80.250000, -108.750008,-422.550018 ,
10-01 22:51:41.228   721   823 E android.hardware.sensors@2.0-service-mediatek: akm_log AKM_GetData lili_time_stamp_GetData:3574322956760, stype =1, ,
10-01 22:51:41.228   721   823 E android.hardware.sensors@2.0-service-mediatek: akm_log akl_getv_mag(uT) , 27, -31, -34, Lv: 2
10-01 22:51:41.228   721   823 E android.hardware.sensors@2.0-service-mediatek: akm_log akl_getv_mag(uT) offset: -107, -76, -387
10-01 22:51:41.228   721   823 E android.hardware.sensors@2.0-service-mediatek: akm_log AKM_GetData time_stamp11=3574410679463, stype =1
10-01 22:51:41.228   721   823 E android.hardware.sensors@2.0-service-mediatek: akm_log akm_wrapper_calibrate is 27.719999, -31.920000, -34.200001
10-01 22:51:41.228   721   823 E android.hardware.sensors@2.0-service-mediatek: akm_log Enter wrapper_set_magNull
10-01 22:51:41.228   721   823 E android.hardware.sensors@2.0-service-mediatek: akm_log Enter wrapper_set_magNull

The only way to make it stop is to disable all the sensors via the tile in developer options. Also it looks like disabling sensors per app doesn't work at all. I mean the stock one which can be accessed via app info and also the one that crDroid provides in its settings.

The same thing happens when GPS gets a fix.
 
Last edited:

morfikov

Senior Member
Oct 22, 2016
162
52
Warsaw
morfikov.github.io
Redmi 9
It looks like, there are some issues with the notification mechanism. Basically all apps, which don't use the google push system, can't receive notifications. It's the case for Telegram FOSS, Signal, and K9-mail. They all have disabled battery optimization and they all have a visible notification displayed in the nav bar/lock screen.. But the network connection breaks after a few minutes you turn the screen off. Often notifications don't work when the screen is on -- you have to access the app to receive them (as soon as you access the app, the notification is delivered). Is there any fix for this issue? Does anyone noticed this behavior?
 

morfikov

Senior Member
Oct 22, 2016
162
52
Warsaw
morfikov.github.io
Redmi 9
Good news is that, it looks like the official (the newest) firmware is bugged somehow. The same errors can be observed in the stock MIUI12A11. So it's not the crDroid's fault.

But still the delay in receiving notifications in the case of crDroid is really weird.
 

Top Liked Posts

  • There are no posts matching your filters.
  • 18
    BE3pE0l.png

    Code:
    *** Disclaimer
    I am not responsible for any damage you made to your device
    You have been warned


    crDroid is designed to increase performance and reliability over stock Android for your device also attempting to bringing many of the best features existent today


    Features:
    https://github.com/crdroidandroid/crdroid_features/blob/11.0/README.mkdn

    Read (THIS) If You Have Issues With Dialer App

    Flashing Instructions:

    Pre-installation:
    [*]IMEI-BACKUP-SCRIPT (Download from here)
    [*]FIRMWARE (Download from here)

    #KEEP IMEI BACKUP IN SAFE PLACE, ITS IMPOSSIBLE TO COMPLETELY RESTORE IMEI IF LOST!


    First time installation:
    • step 0: Make Sure You Have IMEI Backup, Take From link above
    • step 1 : Assuming You Have Your Bootloader Unlocked Already, Go to fastboot mode, Flash recovery(shrp in this case)
    • step 2: Reboot To Recovery, Format Dalvik, Art Cache And Cache, Click on format data --> type yes
    • step 3: Flash Your Device FW(skip if on MIUI Android 11), then Flash crDroidAndroid Zip
    • step 4: Flash The Suggested Gapps Package(optional)
    • step 5: If you want magisk, flash after you've setup the phone from the setup wizard

    Update installation:
    • step 1: If You're On Non-OSS rom, Or OSS-Q rom, Follow "First Time Installation" Guide
    • step 2: First Unroot Your Device!(**IMPORTANT**), Now Assuming Youre on OSS-R Rom, or an Old Crdroid Build, Reboot To Recovery, Format Dalvik, Art Cache And Cache
    • step 3: Flash crDroidAndroid Zip
    • step 4: Flash The Suggested Gapps Package(optional)
    • step 5: If you want magisk, flash after you've setup the phone from the setup wizard


    Sources:
    ROM: https://github.com/crdroidandroid
    Kernel: kernel url

    Download:
    ROM Download-Link
    Changelog: Changelog


    Visit official website @ crDroid.net
    Support Group(Telegram)
    crDroid Community Telegram
    crDroid Updates Channel
    Donate to help our team pay server costs
    3
    @tiga05, yes, I've managed to solve it, but I don't really know what consequences of my deeds can be, so be careful if you want to follow what's below.

    Basically, you probably are right about some buggy ROM<->google relationship. To deal with this spam log, you have to disable com.google.android.gms/.chimera.GmsIntentOperationService . You can do it via ADB:

    Code:
    # pm disable com.google.android.gms/.chimera.GmsIntentOperationService

    I'm not sure what this service is used for (it's just a part of google GMS, i.e. google play services), but it looks like everything works well so far.

    I've also been playing with google play services optimization for battery utilization and RAM usage. Basically I disabled these activities/services, which reduced RAM from 450M to around 140M, which is really nice.
    2
    Followed the installation instruction, everything has been smooth so far. Played some game and the performance is great. Prop to the maintainer for writing such detail instruction rather than having me search though everything on my own. Keep it up!
    1
    How is the stability?
    1
    You are right, this is similar problem. When I reboot phone in airplane mode, then I get all channels working. If I enable GSM and restart WiFi, then channels 149 - 173 stop working. I can see in logcat, that country is set to PL, but regulatory info looks the same (or I don't know what to look for).