Oh! Missed that but I'm seeing it now... Thanks.
Are the files/devs the same as for the RN10Pro?
Development [ROM][13.0] crDroid 9 [OFFICIAL]
- Thread starter neobuddy89
- Start date
Oh! Missed that but I'm seeing it now... Thanks.
Are the files/devs the same as for the RN10Pro?
These Redmi's are hardware crapshoots. I believe all the reports I have seen about the touchscreen problem has been only on the RN10P and not the RN11, since mine is fts and worked.Oh! Missed that but I'm seeing it now... Thanks.
Are the files/devs the same as for the RN10Pro?
how comes RN11 is even a thing for this thread/ROM? I mean this rom (-version) and thread is all about crDroid on RN10pro?
if some problems do not exist on RN11 crDroid, fine. but that has nothing to do with RN10Pro and the things we are talking about in this thread. different phone, different rom, different problems.
lets focus on RN10PRO in this thread and the version of CrDroid that is explicitely compiled for RN10pro.
if some problems do not exist on RN11 crDroid, fine. but that has nothing to do with RN10Pro and the things we are talking about in this thread. different phone, different rom, different problems.
lets focus on RN10PRO in this thread and the version of CrDroid that is explicitely compiled for RN10pro.
I am also curious of "are the files/devs the same as for the RN10P", since crDroid provides official ROM's for both phones. crDroid developers may be able to port the spes "fix" to the RN10P.
The following new spes thread might provide clues to the official crDroid devs:
forum.xda-developers.com
The following new spes thread might provide clues to the official crDroid devs:
Kernel source finally released
It finally happened the source code is released https://github.com/MiCode/Xiaomi_Kernel_OpenSource/tree/spes-r-oss Leaving this also as a place for first discussions. So, go for it. 🤘
forum.xda-developers.com
Hi guys, first at all = big thanks for such a beautiful ROM.. I am using it since 2018 now on second phone.
Just to report one annoying issue: I am on the last version 9.5 build number TQ2A.230505.002
Clean flashed 9.4 than OTA update to 9.5m but in both cases volume is going up and down strangely.
It's like there is a kind of limiter or compressor of sound. In example: media volume set to level 5, but I clearly hear, that in YouTube, waze and all other apps sound level is going up and down during listening on load speaker (mean no headphones connected). After restart issue persists. But without restart -mean system is running for a few days issue disappears, then suddenly after restart. Anybody found such issue? Or it's app depending ? Thx for any help.
Just to report one annoying issue: I am on the last version 9.5 build number TQ2A.230505.002
Clean flashed 9.4 than OTA update to 9.5m but in both cases volume is going up and down strangely.
It's like there is a kind of limiter or compressor of sound. In example: media volume set to level 5, but I clearly hear, that in YouTube, waze and all other apps sound level is going up and down during listening on load speaker (mean no headphones connected). After restart issue persists. But without restart -mean system is running for a few days issue disappears, then suddenly after restart. Anybody found such issue? Or it's app depending ? Thx for any help.
see: https://forum.xda-developers.com/t/rom-13-0-crdroid-9-official.4516207/post-88110699
in short: disable dolby atmos app.
Hi all, enybody has troubles with call recordings ? Sometimes it doesn't displaying during a call, sometime it displays, but is not able to start. I am not using daily, but remember that worked well in previous ver. 9.4.
Any idea, what can causes this ? THX
Anyway the best ROM ever !
Any idea, what can causes this ? THX
Anyway the best ROM ever !
I disabled it as well. Sound was fluctuating using wifi and Google Meet, even on speaker. Maybe this app exacerbated the problem.
I am experiencing battery drain issues. I am monitoring my battery usage with GSAM app and its reflecting wakelock issues. The device never goes into deep sleep state. I think this was happening to me also on pixel experience rom so might be a kernel related thing. Any tip on that matter? Thanks a lot.
Tricky to determine which you can use on your particular ROM, though, or if it will help or even break anything new. https://forum.xda-developers.com/t/...on-kewl-aghisna-kernel-anotherkernel.4398423/
I tried all versions of crdroid, there is a problem on the lock screen, when the clock is always show, the lock screen goes and goes, double-clicking it does not open or a ridiculous screen occurs. There is no such error in other roms I tried.
afaik gsi roms work with fts_ts touchscreenSo, as I'm still looking, let me re-ask this...
had this issue too, as well as on lineage os, don't know what triggers that.
Update on my experience with the may build:
It's consuming a LOT of battery. System is very stable tho.
It's consuming a LOT of battery. System is very stable tho.
run optimizer script, either with adb(adb shell pm bg-dexopt-job) or with termux(pm bg-dexopt-job)
Or use aghisna manager
[SHARED] [OSS] [MIUI] [KERNEL] newest sweet/in quantum, vantom, sleepy, yuki, delta, doraemon, kewl, aghisna, another, dark, electro, zelo
Update 8.8.23 Imo best kernel with fast charging time Page 19 Update 12.6.23 Zelo kernel Page 18 Update 8.6 Newest vantom ekectrokernel Newest kernelsu Page 18 Update 6.6.23 Newest sleepy page 18 Update 28.5.23 Aghisna manager Dark...
forum.xda-developers.com
I tried this, I got marginally better battery life. Might try the kernel suggestion later.
Similar threads
Top Liked Posts
-
There are no posts matching your filters.
-
1
Yep, Touch & camera seem to be working fine.
But am on 8/128gb not the 8/256gb.
Additionally its Smooth for a daily usage. Just a few discovery;
D1: occasionally, charging is unstable (i.e Quick charging at first instance of charger connection, then, Slow charging after reconnecting charger ( So keep charger plugged-in to once charging starts to avoid slow charging). [ Smart charging at work I believe (smiles)]
D2: Sometimes the OS automatically connects and disconnects charging process when >80% charged or more. But disabled/enabling charging limit to 99-100%" Fix it for me.
Device: M2101k6G -
16
Code:*** Disclaimer I am not responsible for any damage you made to your device You have been warned
Features:
* Encrypted build
* Vanilla build (no gapps)
* Selinux enforcing and Safety net passes by default
* More info - Click here
First Time Installation:
* Backup before you begin
* Reboot to provided or TWRP based recovery.
* Format Data , even coming from crDroid 8.x
(otherwise you may not able to boot ROM due to encryption complexities)
* Flash ROM via adb sideload
* Flash Nik Gapps core + Gapps Search addon + Google Device Personalization addon via adb sideload
* Reboot and profit!
Update Installation:
* Backup before you begin
* Ensure you are on provided 12/13 recovery
* Use Updater app to download update and flash
(or download update separately and use Updater app with Local update option)
* No need to flash gapps if already flashed.
Download:
Click Here
Known issues:
* None.
Sources:
ROM: https://github.com/crdroidandroid
Device tree: https://github.com/crdroidandroid/android_device_xiaomi_sm6150-common
Visit official website @ crDroid.net
crDroid sweet/sweetin - crDroid Telegram
Donate to help me in development
crDroid Community Telegram
Donate to help CrDroid team pay server costs3
NiceRead here
I really don't understand why so many people just say wipe everything and make a clean install. Even with backups of everything I still need 1 or 2 full days to completely redo all my system customizations and it's such an insane amount of work.2I had been using crDroid for about a year, I really like the ROM and I decided to do a clean install to version 9 (A13). Everything works including MTP, camera, bluetooth, wifi, hotspot.. I didn't find any problems in use, but... but there is a battery drain problem, the phone in airplane mode consumed 20% of the battery in 8 hours battery, while before with the same apps installed the consumption in this mode was about 3%, I hope that you will be able to have a good battery life even with this ROM because currently with moderate use of the phone, you are not even able to get to the end of the day with 5000mha of battery. I thank the developer for the excellent work done so far and I look forward to solving these problems.
Thank you!2Ok. Finally got Magisk working with banking and intune company portal app. Thank you @Laptapper for valuable hint.
2 3 things to remember.
If you are installing Magisk after installing all other apps, its good. You will see all apps you need to hide in Zygisk. BUT after installing Magisk,
1. Reboot your phone first.
2. DONT open anything. First open Magisk and hide it in settings.
3. Enable Zygisk and add apps in denylist there Eg banking apps, intune company portal etc.
4. Hide every google process (tip. Enable "Show system apps" and "Show os apps". Blindly hide all google process there).
5. Clear cache and storage of not only google but all the apps also which you have hidden in zygisk denylist. This may result in reconfigure the apps again like login again etc.
6. Reboot the phone again.
7. Now open all the apps and configure.
For Outlook and MS Team, delete and add the work account again.
Some feedback about new build of 23Dec.
Ok. Dirty flashed the new 23Dec build of this ROM over 17Dec build. Long press on home button still not working. I mean not doing anything.
Another issue which I found was Alarm was not working in 17Dec build.IIts working in 23Dec Build.
Another issue which I found is when you try to change the font from settings-- crdroid setting -- user interface -- font, it will only be applied to system settings and not to other areas like app drawer or whatsapp. In earlier version, changing fonts gets applied to all areas like app drawer and whatsapp also.
Touch is comparatively better than 17Dec build. Atleast in last 1 hour usages.
And that Battery drain issue is back. Lost 6% in 1 hour of usage. Lets monitor this for another week or two. Lets hope this 6% is only because of my usages.
Thanks once again @Laptapper and @HidetoraChishu
2
You should think that we don't all have telegram accounts ... I don't have one...
