[UNOFFICIAL] crDroid R Mod //crDRom11

[eremitein]

Is there "double tap to wake" option in this version?

yes, and works on my phone. but for your device maybe will not work

 

[tauhid.91]

yes, and works on my phone. but for your device maybe will not work

In previous update it didn't work for my device (Galaxy A30)

 

[juandi34]

yes, and works on my phone. but for your device maybe will not work

I just flash this ROM in my Blackview BV9600E and works very fine. I thinks it´s the most complete. I try using LiR, CAOS and many others, but I think it´s the most complete, but in my phone has a problem that it wasn´t in LiR and CAOS: the location is very slow, and doesn´t works fine (google maps, location in whatsapp ... etc).

eremitein : is there a patch to apply in TWRP to solve it ???

Thank you and congratulations.

 

[eremitein]

I just flash this ROM in my Blackview BV9600E and works very fine. I thinks it´s the most complete. I try using LiR, CAOS and many others, but I think it´s the most complete, but in my phone has a problem that it wasn´t in LiR and CAOS: the location is very slow, and doesn´t works fine (google maps, location in whatsapp ... etc).

eremitein : is there a patch to apply in TWRP to solve it ???

sorry, i have no fix
did you flashed same gapps zip which used in CAOS/LiR? or you using gappsed builds always?

 

[juandi34]

sorry, i have no fix
did you flashed same gapps zip which used in CAOS/LiR? or you using gappsed builds always?

Yes: I have flashed same gapps that I flashed in CAOS/LIR.

 

[meechyy]

p

 

[lfom]

Just a quick follow up from my port (#33), after I installed phhusson's AOSP 11.0 v313. All issues I reported besides #2 and #6 also happen with vanilla AOSP, #2 is related to the crDRom11 while #6 is just generic (it would happen with any ROM).
I was able to build an overlay for FIG-LX1 and battery seems to be OK, not as good as stock ROM tho, but I think this is expected. I downgraded the stock system to EMUI8 so I could use the Aonly version, but it seems that some NFC service keeps crashing all the time, slowing down the whole system after a while, and also demanding more battery. So I moved to EMUI9 again and installed the AB version. (small parenthesis here: EMUI8 is Aonly = SAS = System as System, while EMUI9 is AB = SAR = System as Root, at least on FIG-LX1)
The main problem that remains is the cell signal, what is broken. It seems that there is workaround using in some other ROM, but I have found it only on Android Q (A10) ROMs, not A11. If anyone has any tip on how to fix it on Android R ROMs it would be great.
There is another minor issue with cdDRom that I forgot: the Simple Gallery app included is not signed using the same keys as the F-Droid version, so it is not possible to update the app easily. Not a big deal, but I wonder why the F-Droid version wasn't used.
Thanks to @eremitein for all his builds again.

 

[CosmicDan]

Just a quick follow up from my port (#33), after I installed phhusson's AOSP 11.0 v313. All issues I reported besides #2 and #6 also happen with vanilla AOSP, #2 is related to the crDRom11 while #6 is just generic (it would happen with any ROM).
I was able to build an overlay for FIG-LX1 and battery seems to be OK, not as good as stock ROM tho, but I think this is expected. I downgraded the stock system to EMUI8 so I could use the Aonly version, but it seems that some NFC service keeps crashing all the time, slowing down the whole system after a while, and also demanding more battery. So I moved to EMUI9 again and installed the AB version. (small parenthesis here: EMUI8 is Aonly = SAS = System as System, while EMUI9 is AB = SAR = System as Root, at least on FIG-LX1)
The main problem that remains is the cell signal, what is broken. It seems that there is workaround using in some other ROM, but I have found it only on Android Q (A10) ROMs, not A11. If anyone has any tip on how to fix it on Android R ROMs it would be great.
There is another minor issue with cdDRom that I forgot: the Simple Gallery app included is not signed using the same keys as the F-Droid version, so it is not possible to update the app easily. Not a big deal, but I wonder why the F-Droid version wasn't used.
Thanks to @eremitein for all his builds again.

If its only the cell signal display, it sounds like an overlay issue. Its probably the fact that Android 11 has some new values that aren't in 10, and they're just using defaults.

You said you made an overlay, so you know what you're doing. What I do with making stock ROM overlays is to merge all the xmls I can find relevant to framework, with one set merged on stock ROM only and the second set merged with a Treble ROM. You can do this easily by just whacking in the extra xml's into values and recompiling with apktool - any value that comes *after* will overwrite previous. Vendor is read first I think, so you want vendor xmls to have a filename appearing first (so the /system xmls can overwrite the vendor ones when you recompile).

Then, you end up with two apk's - one is a combined framework-res with *all* values aggregated from stock ROM, the other is a framework apk that's supplanted with GSI values. You can simply decompile these recompiled framework apk's and diff them, since apktool will remove dupes (remember: replacing with what comes in a later xml) and sort the values.

I hope that makes sense. Not only does it ensure that you have gotten *every* value from your stock ROM, but it also allows you to see all the new values in Android 11. Do note that many of those new values will be new defaults of A11 that don't need to be changed, though.

If you're sure you've gotten all overlay values, and also cannot find a new Android 11 signal display values (if they exist or not, I don't know), then you would have to report to Phh as its likely some custom Huwaei framework code.

 

[eremitein]

Just a quick follow up from my port (#33), after I installed phhusson's AOSP 11.0 v313. All issues I reported besides #2 and #6 also happen with vanilla AOSP, #2 is related to the crDRom11 while #6 is just generic (it would happen with any ROM).
I was able to build an overlay for FIG-LX1 and battery seems to be OK, not as good as stock ROM tho, but I think this is expected. I downgraded the stock system to EMUI8 so I could use the Aonly version, but it seems that some NFC service keeps crashing all the time, slowing down the whole system after a while, and also demanding more battery. So I moved to EMUI9 again and installed the AB version. (small parenthesis here: EMUI8 is Aonly = SAS = System as System, while EMUI9 is AB = SAR = System as Root, at least on FIG-LX1)
The main problem that remains is the cell signal, what is broken. It seems that there is workaround using in some other ROM, but I have found it only on Android Q (A10) ROMs, not A11. If anyone has any tip on how to fix it on Android R ROMs it would be great.
There is another minor issue with cdDRom that I forgot: the Simple Gallery app included is not signed using the same keys as the F-Droid version, so it is not possible to update the app easily. Not a big deal, but I wonder why the F-Droid version wasn't used.
Thanks to @eremitein for all his builds again.

i know for EMUI8 need patch AIO from @Hami_Do, it will fix NFC and other things

 

[lfom]

@CosmicDan Thanks. I think I got you, but I also think it is something else, perhaps some other patch in framework-res.apk. Actually, there is a patched cdDroid v7.10 that has the cell signal patch, but I did not figure out yet what exactly was changed.

@eremitein Now I am not sure if his patch fixed the crash or not, but I do remember I was not able to make NFC work, only using the AB version (his patch is only for Aonly ROMs if I recall correctly), but even to make it work I had to install a Magisk module for Kirin 659 devices, apply Alf patch to /vendor partition manually, and then remove the Magisk module, only then I could enable NFC successfully.

I am still looking for a fix to the cell signal. Thanks again.

 

[GroovyG]

In case anyone wonders what happens when you put this ROM on a WP15 with microg



This is after my first flash, so with a lot of installing, setting up, rebooting, testing etc. going on.
Under normal use scenario it'll probably get to around 50h SOT

 

[eremitein]

In case anyone wonders what happens when you put this ROM on a WP15 with microg

This is after my first flash, so with a lot of installing, setting up, rebooting, testing etc. going on.
Under normal use scenario it'll probably get to around 50h SOT

what is WP15?

 

[GroovyG]

what is WP15?

WP15

 

[eremitein]

WP15

wow insane battery!

 

[GroovyG]

Indeed, it's a beautiful piece of hardware all round. Only the stock software is total garbage as usual (which is really the case for any device haha), but there's your crDroid for that

I charged it for the first time today, let's see how long it lasts under normal use. Prediction in battery stats now says 17 days left

 

[Hiamah.777@outlook.com]

where is the arquiv of b arm32 or a arm32 ​

 

[juandi34]

sorry, i have no fix
did you flashed same gapps zip which used in CAOS/LiR? or you using gappsed builds always?

I have reflashed yesterday on my BV9600E when I was experimenting another roms, but in this time, I have downloaded and flashed another file: crdrom-v313+211013-arm64-boZ.img (for not to have to flash GAPPS).

Great surprise: ... now, location runs quick and fine (only a little magnetic adjust using the 8 movement).

Congratulations.

 

[eremitein]

crDRom R 2021.12.19
download /// changelog

 

[MuddyDog]

crDRom R 2021.12.19
download /// changelog

hi, hope you re well and thanks for updating crDRom. except for one show stopper on my PH-1 it is running great.
the bug is that there is no in-call audio. this bug showed up in phh's v400 builds, affecting the ph-1 and some pixel phones. since none of your earlier crDRom builds have this bug, it been introduced (most likely) by something backported from v400.
phh knows about this problem and has it on his Android 12 todo list. hope that it can be backed out or fixed in crDRom.

 

[eremitein]

hi, hope you re well and thanks for updating crDRom. except for one show stopper on my PH-1 it is running great.
the bug is that there is no in-call audio. this bug showed up in phh's v400 builds, affecting the ph-1 and some pixel phones. since none of your earlier crDRom builds have this bug, it been introduced (most likely) by something backported from v400.
phh knows about this problem and has it on his Android 12 todo list. hope that it can be backed out or fixed in crDRom.

hi, can you grab logs "adb logcat -b all -d > logs.txt" ? right after reboot and one call
much better without VoLTE