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

[Stan m]

Has anyone else faced problems with touch?
I tried Arrowos 13 and this, both had the problem.

 

[Synt4x3rror]

Hello, I installed fresh on that same version but the fast charging seems to not work correctly (some days it doesnt go higher than 10-12 watts and even stays stuck at 7 watts), just wanted to know if it was happening to anyone else

Charging from 15% I've gotten about 20W from my charger (Rated up to 30W).

Check your charger and cable, also remember that fast charging really occurs when the phone battery is low.

 

[Zacatk]

Charging from 15% I've gotten about 20W from my charger (Rated up to 30W).

Check your charger and cable, also remember that fast charging really occurs when the phone battery is low.

Cable is new and original, also have tried similar cable that works on other phones with fast charging, but when I connect the cable to the phone after a few seconds it shows as it were disconnected and connected really fast. Then proceeds to charge at ~7 watts even when low on battery like 10%.

 

[BotoxxotoB]

Has anyone else faced problems with touch?
I tried Arrowos 13 and this, both had the problem.

I can confirm this issue. Sometimes the display misinterpret a short touch as long press and persist the loop till touch somewhere else. I activated the touch feedback in developer options. When the bug occurs the glowing feedback of touch keeps glowing. I am just not sure if it's ROM based or hardware based.

 

[Laptapper]

I can confirm this issue. Sometimes the display misinterpret a short touch as long press and persist the loop till touch somewhere else. I activated the touch feedback in developer options. When the bug occurs the glowing feedback of touch keeps glowing. I am just not sure if it's ROM based or hardware based.

ROM based.
It was already a few months ago with other ROMS in A12.....

 

[BotoxxotoB]

ROM based.
It was already a few months ago with other ROMS in A12.....

Sounds like good news, because if it's ROM based it's possible to fix it

 

[diogofd8]

Alright, I've used this rom for about a week, here's a list of bugs I've encountered which weren't present in crDroid 8. I don't know whether they are A13 specific issues or crDroid 9 issues but I guess other users can test it out and give continuous feedback.

1) Pinch to zoom on pictures is broken in some cases. Instagram used to let me pinch on feed pictures and zoom them with crDroid 8 but not with this version. In GalleryGo (Goggle Gallery) the pinch zoom mostly works but I've had situations where I needed to restart the app and try again for it to work.

2) Some apps load poor resolution images and won't ever reload with a better resolution one. Off the top of my head, Tachiyomi (a manga app) is unreadable with this fw and also Relay for reddit has these issues. There's no way I can see the original quality of the image unless I open it with a browser (i.e. Firefox). Again, I've got no idea if this is related to problem 1) or if it is an app related bug as A13 is still quite "new".

3) Swipe-up on the lockscreen to get to the unlocking pattern isn't working properly. We used to be able to swipe half of the screen pretty fast to get to that menu but with this crDroid 9 the only way I can trigger the unlocking menu is by swiping the entire screen vertically, if I miss 1% of the screen it won't stay there and won't let me unlock the phone.

4) The fingerprint sensor got worse? I might have just have sweaty fingers throughout this week but I'd say unlocking the phone has gotten pretty inconsistent. Sometimes I actually give up and just enter the pattern. I've tried resetting the fingers on settings but it didn't get any better.


Now some suggestions/questions about further development:

- Leica cam - I've seen people making videos on YouTube about a LOS A13 custom rom on our "sweet" phone with Leica cam included and working. Is it something crDroid devs are looking to import for crDroid 9 hence they've dropped the MIUI camera from previous versions?

- Kernel/wakelocks/deepSleep - The first 3 days of using this rom I had to keep the phone pretty much hugging the charger. It was never entering deepSleep and was always getting high Google Play Services usage. I decided testing out some 3rd party kernels such as Vantom (the christmas release) and some other that was based on Vantom but had a more recent update (sorry, I don't remember its name). They both managed to get the phone to enter deepSleep and battery life improved quite a lot due to that. Is this a confirmed issue with the provided kernel or something that isn't being tackled? Flashing a different kernel and reporting issues is quite unproductive so I made sure everything I've reported here was reproducible with a clean crDroid9 installation.

- crDroid Settings - 3-key navigation bar lacks some settings (such as clear all) in the recents menu. It also tends to vibrate the phone twice with one single tap of the back button in some apps (Instagram and WhatsApp did this a lot but I think it is something that I even caught happening while navigating through the settings app). This was also reproducible in crDroid8, but not 7. The status bar clock settings, if one sets a custom date format and moves the clock to appear on the right side, it will be too close to the battery icon, no space at all available in-between, I don't know if it is intended or not. It is a minor non-important thing but I felt like giving feedback about it also.

 

[Molvol]

I can confirm this issue. Sometimes the display misinterpret a short touch as long press and persist the loop till touch somewhere else. I activated the touch feedback in developer options. When the bug occurs the glowing feedback of touch keeps glowing. I am just not sure if it's ROM based or hardware based.

I also have an issue. I sometimes registers a touch and highlights the item, but doesn't execute the intended action. A second touch then works as expected.

1) Pinch to zoom on pictures is broken in some cases. Instagram used to let me pinch on feed pictures and zoom

2) Some apps load poor resolution images and won't ever reload with a better resolution one. Off the top of my head,

3) Swipe-up on the lockscreen to get to the unlocking pattern isn't working properly. We used to be able to swipe half

4) The fingerprint sensor got worse? I might have just have sweaty fingers throughout this week but I'd say

1) haven't had an issue except on some webpages, but believed it to be a website problem
2) Not noticed
3) definitely don't have that issue, the slightest swipe up works
4) mine works very well and sensitive

I also am using TWRP twrp-3.7.0_12-0-sweet.img and haven't had any issues.

I do have huge issues with VPN and Voip. They don't connect properly, disabling IPv6 worked for VPN but is not permanent, even with Magisk module (wish the ROM had an option). Also internet connection broke down several times. Browsers reported "not reachable" or were extremly slow, ping, however, worked fine. Disabling Wifi cured it.

 

[Sheist!]

Alright, I've used this rom for about a week, here's a list of bugs I've encountered which weren't present in crDroid 8. I don't know whether they are A13 specific issues or crDroid 9 issues but I guess other users can test it out and give continuous feedback.

1) Pinch to zoom on pictures is broken in some cases. Instagram used to let me pinch on feed pictures and zoom them with crDroid 8 but not with this version. In GalleryGo (Goggle Gallery) the pinch zoom mostly works but I've had situations where I needed to restart the app and try again for it to work.

2) Some apps load poor resolution images and won't ever reload with a better resolution one. Off the top of my head, Tachiyomi (a manga app) is unreadable with this fw and also Relay for reddit has these issues. There's no way I can see the original quality of the image unless I open it with a browser (i.e. Firefox). Again, I've got no idea if this is related to problem 1) or if it is an app related bug as A13 is still quite "new".

3) Swipe-up on the lockscreen to get to the unlocking pattern isn't working properly. We used to be able to swipe half of the screen pretty fast to get to that menu but with this crDroid 9 the only way I can trigger the unlocking menu is by swiping the entire screen vertically, if I miss 1% of the screen it won't stay there and won't let me unlock the phone.

4) The fingerprint sensor got worse? I might have just have sweaty fingers throughout this week but I'd say unlocking the phone has gotten pretty inconsistent. Sometimes I actually give up and just enter the pattern. I've tried resetting the fingers on settings but it didn't get any better.


Now some suggestions/questions about further development:

- Leica cam - I've seen people making videos on YouTube about a LOS A13 custom rom on our "sweet" phone with Leica cam included and working. Is it something crDroid devs are looking to import for crDroid 9 hence they've dropped the MIUI camera from previous versions?

- Kernel/wakelocks/deepSleep - The first 3 days of using this rom I had to keep the phone pretty much hugging the charger. It was never entering deepSleep and was always getting high Google Play Services usage. I decided testing out some 3rd party kernels such as Vantom (the christmas release) and some other that was based on Vantom but had a more recent update (sorry, I don't remember its name). They both managed to get the phone to enter deepSleep and battery life improved quite a lot due to that. Is this a confirmed issue with the provided kernel or something that isn't being tackled? Flashing a different kernel and reporting issues is quite unproductive so I made sure everything I've reported here was reproducible with a clean crDroid9 installation.

- crDroid Settings - 3-key navigation bar lacks some settings (such as clear all) in the recents menu. It also tends to vibrate the phone twice with one single tap of the back button in some apps (Instagram and WhatsApp did this a lot but I think it is something that I even caught happening while navigating through the settings app). This was also reproducible in crDroid8, but not 7. The status bar clock settings, if one sets a custom date format and moves the clock to appear on the right side, it will be too close to the battery icon, no space at all available in-between, I don't know if it is intended or not. It is a minor non-important thing but I felt like giving feedback about it also.

I see #3 as well, but it isn't 100% and usually goes away in microseconds... but I am annoyed in those microseconds.

 

[Molvol]

The volume keys on my old phone with AEX worked such that they adjusted ring volume and vibrate/off unless some audio was playing. Only then did they adjust media volume. I used this daily to adjust/quiet the phone in my pocket with one hand. Never had to look at it or take it out.
I'm quite bummed that I can only adjust media volume on CrDroid and the only shortcut I found can only do EITHER vibrate OR quiet and requires two key presses (volume and off). But it doesn't work on lockscreen, so useless for my purpose.

Any ideas to get this functionality back?

 

[Skynet00]

Has anyone else noticed issues with audio playback volume fluctuating?

It's happening when I listen to songs on NewPipe through wired headphones.

It doesn't seem to happen for internal speakers
It doesn't seem to happen on my other phone running NewPipe or when I play the same song on desktop.

 

[Zirila]

hey there, testing this rom as daily driver now for my brand new RM10pro. first things I noticed in the first day:

- I also noticed the touch issues a lot, esp. in settings menu. you have to touch something else to finish the incomplete-touch from before - and retouch again. it gets annoying over time.

- @Skynet00 I also noticed the volume changes in audio playback.. listening to an audio book the volume drives roller coaster. noticed this with internal speaker. I suspected the preinstalled dolby atmos app for this or some other loudness equation setting somewhere. so far I've disabled dolby atmos and it MIGHT have helped but I need to evaluate further. try it for yourself, setup and disable dolby atmos setting (it has something like "intelligent" setting by default)

- first impression on battery usage: system drains a lot more than I suspected. pure lineageOS had double the battery time. again, I still need to evaluate further as I'm using the phone a lot currently, so don't count on it.

 

[Skynet00]

- @Skynet00 I also noticed the volume changes in audio playback.. listening to an audio book the volume drives roller coaster. noticed this with internal speaker. I suspected the preinstalled dolby atmos app for this or some other loudness equation setting somewhere. so far I've disabled dolby atmos and it MIGHT have helped but I need to evaluate further. try it for yourself, setup and disable dolby atmos setting (it has something like "intelligent" setting by default)

Thanks! That fixed it for me. I wonder why this proprietary garbage got included?

 

[Zirila]

google changed some logic behind safetynet attestation in the last days...
safetynet doesn't work anymore with universal safetynet fix.

the custom rom maintainers need to change update their props values. hope we get this in crdroid soon.

more details: USNF thread

 

[jnsson]

google changed some logic behind safetynet attestation in the last days...
safetynet doesn't work anymore with universal safetynet fix.

the custom rom maintainers need to change update their props values. hope we get this in crdroid soon.

more details: USNF thread

This may work https://github.com/Displax/safetynet-fix/releases/tag/v2.3.1-MOD_3.0
I have not tested it myself

 

[Sheist!]

This may work https://github.com/Displax/safetynet-fix/releases/tag/v2.3.1-MOD_3.0
I have not tested it myself

It does not. Crap.

 

[Laptapper]

google changed some logic behind safetynet attestation in the last days...
safetynet doesn't work anymore with universal safetynet fix.

the custom rom maintainers need to change update their props values. hope we get this in crdroid soon.

more details: USNF thread

It does not. Crap.

Try out this (for me it's working)

Post in thread ' [SHARED][ROM] [ANDROID 13] [OSS] PULKITS lineage os 20 18.01.23/ checked by myself' https://forum.xda-developers.com/t/...01-23-checked-by-myself.4514085/post-88045439

 

[Zirila]

Try out this (for me it's working)

Post in thread ' [SHARED][ROM] [ANDROID 13] [OSS] PULKITS lineage os 20 18.01.23/ checked by myself' https://forum.xda-developers.com/t/...01-23-checked-by-myself.4514085/post-88045439

are you talking about hiding root from banking apps, or passing safetynet fix? because thats different. some banking apps don't care about safetynet at all, they just want to check for root. in that case, these apps can still be used even without working safetynet.

for users with google pay, safetynet is important of course.

the method you mention might work for you, because you are using lineageOS, which usually doesn't spoof device fingerprints by default. crDroid and other customROMs are probably different here. and as the guy in the linked thread mentions: if the rom integrates it's own prop changes/spoofing, it's likely that it doesn't work anymore. in this case the ROM has to be changed and updated.

 

[Zirila]

I just saw crDroid already fixed it:

crDroid.net - Changelog week 6 - 2023

fixing SafetyNet as Google changed it again

crdroid.net

it just needs to be released for this phone

 

[Sheist!]

are you talking about hiding root from banking apps, or passing safetynet fix? because thats different. some banking apps don't care about safetynet at all, they just want to check for root. in that case, these apps can still be used even without working safetynet.

for users with google pay, safetynet is important of course.

the method you mention might work for you, because you are using lineageOS, which usually doesn't spoof device fingerprints by default. crDroid and other customROMs are probably different here. and as the guy in the linked thread mentions: if the rom integrates it's own prop changes/spoofing, it's likely that it doesn't work anymore. in this case the ROM has to be changed and updated.

Good. The crDroid recovery offers no such cache deletion ability.