Development [ROM][13][OFFICIAL] crDroid Android v9.10 [mojito/sunny]

[tvrctkmytfln]

Disable "Gradually increase volume" in clock app settings.

Thank you so much! I'll try.

And I just found another issue which is the voice call has no input. I can record sound with the recorder and WhatsApp, but the voice call has no input. The other one can never hear my voice and I used the voice call recorder to try recording my voice but found my voice cannot be recorded but the other's voice can be recorded. Any suggestions would be appreciated.

I had such issue before when I was using android 11 with Gapps installed on it (both for crDroid and HavocOS), but the issue was solved if I changed to the vanilla version. But on this crDroid android 12 and 13, the issue is always there in built-in dialer and manually-installed Google dialer.

I have tried `mojito_global_images_V13.0.10.0.SKGMIXM_20220829.0000.00_12.0_global` and `mojito_in_global_images_V12.5.6.0.RKGINXM_20220316.0000.00_11.0_in` as the firmware.

Does anyone know what could be the reason?

 

[tvrctkmytfln]

I found I have to toggle the speaker on first and then toggle it off during a call to make it work every time after I boot my phone.

 

[tvrctkmytfln]

Thank you so much! I'll try.

And I just found another issue which is the voice call has no input. I can record sound with the recorder and WhatsApp, but the voice call has no input. The other one can never hear my voice and I used the voice call recorder to try recording my voice but found my voice cannot be recorded but the other's voice can be recorded. Any suggestions would be appreciated.

I had such issue before when I was using android 11 with Gapps installed on it (both for crDroid and HavocOS), but the issue was solved if I changed to the vanilla version. But on this crDroid android 12 and 13, the issue is always there in built-in dialer and manually-installed Google dialer.

I have tried `mojito_global_images_V13.0.10.0.SKGMIXM_20220829.0000.00_12.0_global` and `mojito_in_global_images_V12.5.6.0.RKGINXM_20220316.0000.00_11.0_in` as the firmware.

Does anyone know what could be the reason?

I found I have to toggle the speaker on first and then toggle it off during a call to make it work every time after I boot my phone.

 

[Spaceboy60]

OK, where to download a13 versions?? Can't find link on first page

 

[alonsoj636MW]

OK, where to download a13 versions?? Can't find link on first page

Here

 

[Spaceboy60]

Here

Thanks, overlooked the section below. Can I flash latest a13 build of twrp before or after flashing this?

 

[alonsoj636MW]

Thanks, overlooked the section below. Can I flash latest a13 build of twrp before or after flashing this?

you mean flashing twrp?
you can do before (for flashing the rom with it)
or you can do after (for having twrp installed)

 

[Spaceboy60]

Can this be flashed with pixelos recovery??

 

[Spaceboy60]

What slot do I flash magisk??? Same one as ROM??

 

[alonsoj636MW]

Can this be flashed with pixelos recovery??

don't
use twrp/ofox

What slot do I flash magisk??? Same one as ROM??

forget about slot just flash magisk on twrp/ofox

 

[Spaceboy60]

OK, big problem after install. Can't install Gapps, TWRP has been replaced by crdroid recovery.

And when I attach phone to PC I get no notification on phone with regards to being connected to my PC or options to change connection mode, and when I run abd commands or fastboot commands phone simply isn't recognised. Usb debugging is enabled

Tried two different cables, different USB shots to no avail. Any ideas? Miflash doesn't even recognise it now ( has been working fine with PIXELOS, this is the first time I've had PROBLEMS)

Suggestions??

 

[x3r0.13urn]

OK, big problem after install. Can't install Gapps, TWRP has been replaced by crdroid recovery.

And when I attach phone to PC I get no notification on phone with regards to being connected to my PC or options to change connection mode, and when I run abd commands or fastboot commands phone simply isn't recognised. Usb debugging is enabled

Tried two different cables, different USB shots to no avail. Any ideas? Miflash doesn't even recognise it now ( has been working fine with PIXELOS, this is the first time I've had PROBLEMS)

Suggestions??

You are new to A/B device.

Boot to crdroid recovery, choose install update / adb sideload, connect usb and run "adb sideload <your_gapp_zip>", after that format data then reboot.

 

[Spaceboy60]

You are new to A/B device.

Boot to crdroid recovery, choose install update / adb sideload, connect usb and run "adb sideload <your_gapp_zip>", after that format data then reboot.

I can't run abd sideload, adb doesn't find any devices and ROM is already INSTALLED anyhow.

 

[Spaceboy60]

Back to stock, working fine now. Could be the cable plus Windows issue as all commands are working fine in fedora Linux (they weren't when I had crdroid installed though for some reason)

 

[YiMonk]

Hi! I have a problem, I use version 9.0 and the GPS doesn't work as it should, for example when I send my location it doesn't show where I really am. Is there any solution?

On the other hand, when I use gmaps, it indicates where I am but it does not point to the direction I am going.

 

[_.ebin.__]

Is anybody else facing issues with battery drain. I have a battery drain of atleast 8% when the screen is off and the phones at idle.
And 11-12% drain when screens on

 

[Anush02198]

New Build is UP:-


Changelogs:-
==== 22 January 2023 ====
+ Used latest WCSF
+ Update Blobs from mojito qssi-user 12 SKQ1.210908.001 V13.0.11.0.SKGMIXM release-keys
+ sm6150-common: Switch to legacy sepolicy_vndr
+ sm6150-common:Remove vendor_debugfs_clk
+ sm6150-common: Kill IMS logspam
+ sm6150-common: Clean debug properties for graphics layer
+ sm6150-common: props: Use HintManager for HWUI
+ sm6150-common: Enable config_avoidGfxAccel
+ Alter Partitions to Fit bit larger gapps
+ sm6150-common: Disable blur on app launch
+ sm6150-common: Disable Async MTE on System Server
+ sm6150-common: Switch to SkiaGL
+ sm6150-common: props: Disable Skia tracing by default
+ sm6150-common: Compile HWUI for performance
+ sm6150-common: overlay: Compact cached app heaps in the background
+ sm6150-common: overlay: Allow more cached apps in the background
+ sm6150-common: overlay: Offload WM shell to another thread
+ Enable F2FS Compression
+ Initial User build

 

[LaMarMôt]

New Build is UP:-


Changelogs:-
==== 22 January 2023 ====
+ Used latest WCSF
+ Update Blobs from mojito qssi-user 12 SKQ1.210908.001 V13.0.11.0.SKGMIXM release-keys
+ sm6150-common: Switch to legacy sepolicy_vndr
+ sm6150-common:Remove vendor_debugfs_clk
+ sm6150-common: Kill IMS logspam
+ sm6150-common: Clean debug properties for graphics layer
+ sm6150-common: props: Use HintManager for HWUI
+ sm6150-common: Enable config_avoidGfxAccel
+ Alter Partitions to Fit bit larger gapps
+ sm6150-common: Disable blur on app launch
+ sm6150-common: Disable Async MTE on System Server
+ sm6150-common: Switch to SkiaGL
+ sm6150-common: props: Disable Skia tracing by default
+ sm6150-common: Compile HWUI for performance
+ sm6150-common: overlay: Compact cached app heaps in the background
+ sm6150-common: overlay: Allow more cached apps in the background
+ sm6150-common: overlay: Offload WM shell to another thread
+ Enable F2FS Compression
+ Initial User build

Cheers !!

 

[PTX64]

-

 

[kaem84]

(...)* the screen sometimes refuses to turn on after sleep while everything else works > reboot by holding power button required.
(...)
It all seem kernel related issues. Not easy to debug because the kernel throws many warnings.

Same for me - black screen after unlocking with fingerprint. The screen appears after a dozen or so seconds. I went back to crDroid 8.9 and the problem was gone. Two days ago I updated only kelner to the same as crDroid 9.1 with android 13 and so far there is no problem with the black screen.