[ROM] [OFFICIAL] crDroidAndroid for Redmi 9 / Poco M2 (lancelot, galahad, shiva) - Redmi 9 / Poco M2 ROMs/Kernels/Recoveries/Dev.

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
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:
SHRP(recovery) (Download from here)
gapps (Download from here)
Magisk 23.0 or newer for root (after first boot) - (Download from here)
[*]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

---

How is the stability?

---

oldukça başarılı

---

There is a bug in FM radio app it crash soon as I open it
Here is some crash log generated
crDroid paste - share logs, bugs, code and whatever else remains in plan text
paste.crdroid.net

---

dj3s said:
There is a bug in FM radio app it crash soon as I open it
Here is some crash log generated
crDroid paste - share logs, bugs, code and whatever else remains in plan text
paste.crdroid.net
Click to expand...
Click to collapse
Besides that, how has your experience been with the ROM?

---

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!

---

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.

---

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.

---

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.

---

Somebody asked before but no answer. How is the situation with low in call volume, is it present like in all custom roms for this phone?

---

blast_beat_ns said:
Somebody asked before but no answer. How is the situation with low in call volume, is it present like in all custom roms for this phone?
Click to expand...
Click to collapse
hello, yeah it is present in this custom rom... its a problem with all custom roms for redmi 9... i switched back to miui because of this issue

---

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.

---

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?

---

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

---

kongtapapple said:
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!
Click to expand...
Click to collapse
Is this rom smooth in Poco M2? Pls reply.

---

iClutch7 said:
Is this rom smooth in Poco M2? Pls reply.
Click to expand...
Click to collapse
Someone mentioned earlier that it is smooth, my dear NEWB fan

---

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?

---

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.

---

Hi

---

HELP!
at the time of installing the rom it gives me an error
says: error installing zip