[ROM][11.0][OFFICIAL][CEPHEUS] crDroid v7.22 [12.09.2022][EOL]

[toscha42]

Just installed crDroid 7.7. Some feedback:
- I needed to flash NikGapps after the ROM due to bootloop. Not too surprising as it was the same with previous versions and had been mentioned in XDA thread as well.
- I needed to flash WiFi fix. Not too surprising as it was the same with previous versions.
- SafetyNet is passed as before.
- Widevine level is still L1, as it was before.

In a nutshell, everything's working fine so far, no unexpected issues to be seen.

Thanks for the great work, @raystef66!

Cheers
Toscha

 

[toscha42]

Just one question. Is there a setting available to get rid of these annoying animations in the Settings sections? It's totally useless taking away a lot of screen real estate and does not provide any benefit or any information at all.

Cheers
Toscha

 

[ai5g]

One question, maybe a bit off-topic: I am still on crDroid 7.3. I understand that dirty flashing is not possible from this version, so my question is, do you have a recommendation for a backup solution which allows backing up almost everything [apps (incl. settings and data, such as entire chats, photos etc. in WhatsApp, or the settings in Magisk, stored credit cards in gPay), system settings, SMS, call history) for restoring after flashing to the current crDroid version?

Thanks in advance!

 

[LoganDeveloper]

There is a big in the latest 7.7 build. Indeed if you flash Gapps and your country allows Google pay, the power menu will crash because it can't show the Google pay card

 

[Bigman6969]

One question, maybe a bit off-topic: I am still on crDroid 7.3. I understand that dirty flashing is not possible from this version, so my question is, do you have a recommendation for a backup solution which allows backing up almost everything [apps (incl. settings and data, such as entire chats, photos etc. in WhatsApp, or the settings in Magisk, stored credit cards in gPay), system settings, SMS, call history) for restoring after flashing to the current crDroid version?

Thanks in advance!

use swift backup or migrate

 

[toscha42]

There is a big in the latest 7.7 build. Indeed if you flash Gapps and your country allows Google pay, the power menu will crash because it can't show the Google pay card

Can't confirm this. I've GPay activated with one credit card connected. Power menu works like always before.

Cheers
Toscha

 

[LoganDeveloper]

Can't confirm this. I've GPay activated with one credit card connected. Power menu works like always before.

Cheers
Toscha

Really? which gapps package do you use? I used the nikGapps full (june 17th) and i have this error:

dogbin - stuwidamar

time: 1624088592864 msg: java.lang.UnsupportedOperationException: Can't convert to ComplexColor: typ

del.dog

 

[toscha42]

Really? which gapps package do you use? I used the nikGapps full (june 17th) and i have this error:

dogbin - stuwidamar

time: 1624088592864 msg: java.lang.UnsupportedOperationException: Can't convert to ComplexColor: typ

del.dog

Using NikGapps Core and no error here.

Cheers
Toscha

 

[Ladap]

Really? which gapps package do you use? I used the nikGapps full (june 17th) and i have this error:

dogbin - stuwidamar

time: 1624088592864 msg: java.lang.UnsupportedOperationException: Can't convert to ComplexColor: typ

del.dog

I'm using NIkgapps stock (20210612) and no error..

 

[LoganDeveloper]

It's weird, I'm not on this build anymore, but I used blur, so it's maybe an issue related to this feature

 

[toscha42]

Sounds reasonable. When I changed from Paranoid Android to crDroid I flashed the then current Xiaomi stock ROM first. Just to set back the device into a defined state. Only then I flashed crDroid.

Cheers
Toscha

 

[phoinix_gr]

I have to say this is an absolutely great Rom.
Blazingly fast, and almost everything is in working order. Also the Battery performance is much better than stock MIUI. Awesome!

---
I did run with an issue with Android Auto, failing to launch.
It seems that installing NikGapps-basic-arm64-11-20201212-signed with TWRP, and Then installing android-auto as an apk from within the OS(crDroid), brakes android auto.


I had to start fresh, and after flashing NikGapps-basic-arm64-11-20201212-signed, also flash the nikGapps android-auto add-on with TWRP. Then boot into system.
That fixed my android auto issues.

---
Other than that, I have only one thing that does not work.
That is the `google` application com.google.android.googlequicksearchbox.

I constantly get "Google keeps stopping' error on Android ...
The version is 12.23.16.29.arm64 installed from PlayStore.

I also tryied the beta version 12.24.7.29.arm64, same result


Any thoughts?

 

[phoinix_gr]

I have to say this is an absolutely great Rom.
Blazingly fast, and almost everything is in working order. Also the Battery performance is much better than stock MIUI. Awesome!

---
I did run with an issue with Android Auto, failing to launch.
It seems that installing NikGapps-basic-arm64-11-20201212-signed with TWRP, and Then installing android-auto as an apk from within the OS(crDroid), brakes android auto.


I had to start fresh, and after flashing NikGapps-basic-arm64-11-20201212-signed, also flash the nikGapps android-auto add-on with TWRP. Then boot into system.
That fixed my android auto issues.

---
Other than that, I have only one thing that does not work.
That is the `google` application com.google.android.googlequicksearchbox.

I constantly get "Google keeps stopping' error on Android ...
The version is 12.23.16.29.arm64 installed from PlayStore.

I also tryied the beta version 12.24.7.29.arm64, same result


Any thoughts?

Seems like the problem is related to

Is your Google app crashing? You're not alone. (Updated: Fix incoming)

Is the Google app crashing on your phone? You are not alone. An update to the app seems to be causing the problem. Here's how you can fix it.

www.androidauthority.com

https://www.worldstockmarket.net/go...sung-smartphones-around-the-world-how-to-fix/

Coincidence that I've installed crDroid the same day !

 

[antykat]

@raystef66

After restoring Widevine L1 with xiaomi.eu rom and flashing crDroid I have L3. I guess it should be fixed like in last update of PixelExpierience.

Everything else works properly. Very good rom. Thank you very much.

 

[AJSRO]

Hello everybody!

With the use I give this ROM I have no problem. Just one question, why don't the apps appear in the Screen > Applications in Full Screen section? Only MatLog appears. I wish there was a way for it to work, it is useful in some cases not to avoid the notch and take advantage of the entire screen.
Greetings and thank you very much for your work, dev!

 

[phoinix_gr]

@raystef66

After restoring Widevine L1 with xiaomi.eu rom and flashing crDroid I have L3. I guess it should be fixed like in last update of PixelExpierience.

From 12.0.5.0.QFAEUXM, I did "wipe system, vendor, data, dalvik/cache, format data, reboot twrp, flashed crdroid" per OP instructions, and I have Widevine L1 in crDroid

Hello everybody!

With the use I give this ROM I have no problem. Just one question, why don't the apps appear in the Screen > Applications in Full Screen section? Only MatLog appears. I wish there was a way for it to work, it is useful in some cases not to avoid the notch and take advantage of the entire screen.
Greetings and thank you very much for your work, dev!

That troubled me also.

Settings-> crDroid Settings -> Navigation -> Stock Navbar Settings -> System navigation -> Gesture Navigation -> Gears Icon

Move "Gesture bar length" all way to the left (Hidden)

 

[antykat]

@phoinix_gr​

Have you ever lost L1? I have lost it because I had to flash new persist.img (sensors didn't work). Now I have recovered L1 with weekly build of xiaomi.eu. There is such a new option since v21.6.2. After that I flashed crDroid and there was L3. Then I flashed PixelExpierience rom and I have L1. Changelog of the newest PE says: "Fix widevine L1 for all devices(restore your widevine key from xiaomi.eu first)". So, I guess there must be something to do in crDroid to have L1.

 

[phoinix_gr]

@phoinix_gr​

Have you ever lost L1? I have lost it because I had to flash new persist.img (sensors didn't work). Now I have recovered L1 with weekly build of xiaomi.eu. There is such a new option since v21.6.2. After that I flashed crDroid and there was L3. Then I flashed PixelExpierience rom and I have L1. Changelog of the newest PE says: "Fix widevine L1 for all devices(restore your widevine key from xiaomi.eu first)". So, I guess there must be something to do in crDroid to have L1.

Aha!
Indeed, I have not ever lost L1



---
Is there a way to map the Mi AI button under crDroid ?
I've tryied using https://xdaforums.com/t/mod-magisk-mi-ai-button-remapper.3918291/ with no success

 

[pavoleo]

Aha!
Indeed, I have not ever lost L1



---
Is there a way to map the Mi AI button under crDroid ?
I've tryied using https://xdaforums.com/t/mod-magisk-mi-ai-button-remapper.3918291/ with no success

Yep, you have to modify gpio.keys in system/usr/keylayout (use a root browser), remapping the key 689 (ai button).

For example, I mapped as MEDIA_NEXT (just like this: key 689 MEDIA_NEXT), so I can change songs by pressing AI button, but you can map it as you want.

 

[toscha42]

Where can I find valid values, e. g. as in your case 'MEDIA_NEXT'?

Cheers
Toscha