Development [ROM][13.0] crDroid 9 [OFFICIAL]

[Im1Random]

There seems to be a problem with version 2023-03-19. As already mentioned the phone crashes multiple times a day when leaving it in standby for a while and after every crash all hidden/password locked apps get revealed again and the keyboard settings from FlorisBoard get reset.

Downgrading to 2023-02-23 causes a bootloop unfortunately.

 

[lukaszkosyna]

That's very unfortunate for you guys I'm sorry...
Lucky me, I don't have any issues. Camera works including panorama mode. Slow mo never worked. Phone doesn't crash or freeze, alarm works fine in the morning. Perfect ROM right now.
I've changed kernel to Agnisha (14-03 build), but I ran the original kernel for a day and no problems apart from dodgy colours on screen. Agnisha has solved it for me and seems to work well.
Also my car's Bluetooth is showing all my track titles on car's screen, Finally!!

Btw I format data, flashed a full MIUI 13v global firmware, no reboot, then format data, then CrDroid (23-02-23), then latest NikGapps core + all add-ons apart from Pixel launcher (done all this back in Feb).
Finally then updated to latest CrDroid via system updater in settings couple of days ago. All good for me.

 

[Zirila]

it's a dilemma. either I try downgroading and risk ending up in a bootloop or I try another kernel.
I'll probably just wait a few more days and see if @neobuddy89 manages to release a hotfix or something.

luckily camera is working.. it's just the crashes/freezes, no screen/touch responses, reddish low-light screen and the alarm clock which I can't rely on any longer.

 

[Laptapper]

it's a dilemma. either I try downgroading and risk ending up in a bootloop or I try another kernel.
I'll probably just wait a few more days and see if @neobuddy89 manages to release a hotfix or something.

luckily camera is working.. it's just the crashes/freezes, no screen/touch responses, reddish low-light screen and the alarm clock which I can't rely on any longer.

I like your posts writing style

Did you've tried lineageos 20 vanilla or like me the pulkits ensemble?

 

[s3andnexus5]

I have the 8/256 model. I just got this phone. Touch does not work in twrp and it doesn't work in the CRdroid operating system either.

What is the problem?

 

[RanjanJain]

I have solved the crashes/Freezes issue by deploying Sleepy Kernel. Bluetooth is working fine.
Track info is getting displayed properly in Car Connect now.
only issue pending is No ringtone when connected to BlueTooth. Any help will be appreciated.

 

[Zirila]

AAudio driver is again not working with the latest release. We had this issue a few releases before.

the thing that previously fixed the issue was probably called:

* Added missing QCOM audio effect libraries

Some games and emulators can choose from AAudio driver or OpenSL ES driver for audio playback. Some unfortunately only use AAudio driver and these have currently no audio playback anymore.

 

[Zirila]

Did you've tried lineageos 20 vanilla or like me the pulkits ensemble?

at the time I was instaling my phone there was no vanilla lineageos 20 ROM. I tried pulkits lineage, but as said it wasn't a lineage, it was rather a pixel rom with bloated gapps. so I ended up using vanilla crdroid, and it was actually great, except the latest buggy release and some rumours of miui parts that are still calling home.

if the current problems get solved anytime soon, I don't see a necessity to move to another rom. so I just wait and see how everything turns out.

 

[minax007]

at the time I was instaling my phone there was no vanilla lineageos 20 ROM. I tried pulkits lineage, but as said it wasn't a lineage, it was rather a pixel rom with bloated gapps. so I ended up using vanilla crdroid, and it was actually great, except the latest buggy release and some rumours of miui parts that are still calling home.

if the current problems get solved anytime soon, I don't see a necessity to move to another rom. so I just wait and see how everything turns out.

I have made the same experiences and changed after GApps bloated "LineageOS" kind of thing and crDroid to LineageOS vanilla ROM form @2spirit :

[ROM] [UNOFFICIAL] [Android 13] [OSS] LineageOS 20.0 Vanilla & MicroG version

Hello, I have build for myself a vanilla version of LineageOS 20.0 because I don't find any simple and pure version of LineageOS and I want to share my build here. This work is based from fork of the device / kernel and vendor tree of "Pulkit...

forum.xda-developers.com

That one is rock solid stable ... with long battery lifetime ... and does not "call home".

Of course it also has some downsides:
- A little bit effort in installing microG as GApps alternative (description is in the thread)
- No LEICA / MIUI camera (GCam is bad in video)

But summarizing it is the best and most secure ROM for this device yet.

And there is hope that it will become official as @2spirit is trying to get it official.

 

[JackDCalloway]

I have solved the crashes/Freezes issue by deploying Sleepy Kernel. Bluetooth is working fine.
Track info is getting displayed properly in Car Connect now.
only issue pending is No ringtone when connected to BlueTooth. Any help will be appreciated.

The freeze and force reboot issue hit me right now. Sleepy Kernel doesn't change a thing. Plus TWRP fails to backup with error 255, tarkfork or something.

Anyone had success with a dirty flash to alst build?

 

[caotics]

The freeze and force reboot issue hit me right now. Sleepy Kernel doesn't change a thing. Plus TWRP fails to backup with error 255, tarkfork or something.

Anyone had success with a dirty flash to alst build?

I found, that wiping the cache in twrp helped. After that the freezes stayed away for a day or a half

 

[JackDCalloway]

I found, that wiping the cache in twrp helped. After that the freezes stayed away for a day or a half

Half an hour would be enough to create one or two backups. System freezes too soon.
Wiping all the caches?

 

[RanjanJain]

The freeze and force reboot issue hit me right now. Sleepy Kernel doesn't change a thing. Plus TWRP fails to backup with error 255, tarkfork or something.

Anyone had success with a dirty flash to alst build?

Agreed. Yesterday morning, my phone started freezing again. I agree that wiping delvic and cache might help for day or half but this freezing issue will eventually come back.

So shifted to 24-Feb built. Phone is critical with office access and data so cant keep with freezing issue.

 

[Fostel]

I have the 8/256 model. I just got this phone. Touch does not work in twrp and it doesn't work in the CRdroid operating system either.

What is the problem?

New 256gb version and updates

So with the new 256gb version Will i get minimum 2 years updates? Or because its only memory change updates will stop same as older models? Ps. Howlong we can expect updates still on older versions?

forum.xda-developers.com

Xiaomi Sensor Lottery - The Ultimate Poll

Hi folks. :) It came to the attention of some users that Xiaomi mixes a lot the sensors that are used in this device. It´s indeed a lottery. Although this might not greatly affect conventional user experience, there are still some differences...

forum.xda-developers.com

 

[unlokomukuerdo]

I have the 8/256 model. I just got this phone. Touch does not work in twrp and it doesn't work in the CRdroid operating system either.

What is the problem?

Due to differences in the hardware, our model is not compatible with the current roms and recoveries , i have tried a few roms and the touch does not work.

 

[ManuD_Linux]

Agreed. Yesterday morning, my phone started freezing again. I agree that wiping delvic and cache might help for day or half but this freezing issue will eventually come back.

So shifted to 24-Feb built. Phone is critical with office access and data so cant keep with freezing issue.

I have exactly the same freeze. It happens when the phone is in deep sleep so I would be tempted to say that it comes from the compilation of the new kernel (I did not have the problem with the previous version, which admittedly contained some Xiaomi bloat, but which did not crash).

 

[Zirila]

So shifted to 24-Feb built. Phone is critical with office access and data so cant keep with freezing issue.

how did you downgrade? clean install or dirty flash over latest version?


the freezes and crashes seem to happen more often over time.
unfortunately there hasn't been a fix or update yet.. and I'm also looking for a way to switch back to a working version.
has anybody successfully downgraded to the previous version with dirty-flashing? I'm not gonna go for a clean install; if it won't work with dirty flashing I'll stick with the current version.

 

[RanjanJain]

I have exactly the same freeze. It happens when the phone is in deep sleep so I would be tempted to say that it comes from the compilation of the new kernel (I did not have the problem with the previous version, which admittedly contained some Xiaomi bloat, but which did not crash).

Agree. After flashing sleepy kernel, I thought its resolved but after day or half, it started again.

 

[RanjanJain]

how did you downgrade? clean install or dirty flash over latest version?


the freezes and crashes seem to happen more often over time.
unfortunately there hasn't been a fix or update yet.. and I'm also looking for a way to switch back to a working version.
has anybody successfully downgraded to the previous version with dirty-flashing? I'm not gonna go for a clean install; if it won't work with dirty flashing I'll stick with the current version.

Clean install. No other way.

 

[JackDCalloway]

So regarding freezing issues I decided to switch the ROM, I'm with arrowOS now. I liked a few things better with crdroid, it's much more open to customization.
On the other hand I went to bed with 85% battery and got up with 84 or 83%. Also better battery stats shows a big amount of deep sleep time.
It didn't with crdroid, no matter which kernel.

Maybe that's also caused by hardware differences, I don't know.