Development [ROM][12.1] crDroid 8 [OFFICIAL][MIUI Cam included]

[interferometry4]

vân tay mở khóa rom của bạn rất chậm, mở camera cũng chậm, chỉnh sửa ảnh không nét, sạc nhanh không vào. Mong nhà phát triển sửa lỗi. Cảm ơn!

english please

 

[SimonGut]

phone goes crazy out of nowhere

 

[oRAZY]

phantom clicks appeared in the last update.

phone goes crazy out of nowhere

Can confirm that occasionally random touch inputs are recognized.
Seems to be directly related to the latest build.

Trying to downgrade by dirty flashing leads to ui crashing after lockscreen input. Puts me right back to the lockscreen. So had to dirty flash latest build over to be able to use the phone again. Gonna try different kernel.

 

[Kinsoku]

I can confirm too the ghost touching bug is back.

Plus, is there any solution regarding the sensor when on call? It keeps turning on the screen and I end up touching stuff with my ear..

 

[jhhat]

Games and applications do not start, more specifically Fortnite mobile and spotify.

I get a message that says: "the application has stopped" version 8.7

 

[interferometry4]

Yes.. random ghost touch in latest build.
Had to shut down or restart

 

[interferometry4]

Can confirm that occasionally random touch inputs are recognized.
Seems to be directly related to the latest build.

Trying to downgrade by dirty flashing leads to ui crashing after lockscreen input. Puts me right back to the lockscreen. So had to dirty flash latest build over to be able to use the phone again. Gonna try different kernel.

is the kernel be the culprit??

 

[oRAZY]

is the kernel be the culprit??

Honestly, I don't know but seems like it. Been using NoGravity kernel 2.2.0 and the NoGravity app 5.2 for a few hours now. So far no glitchy touch. Even has a touch firmware selector for testing two different versions of the firmware. Default has been fine. Unfortunately battery drain seems higher even with battery saver profile selected.

 

[interferometry4]

Honestly, I don't know but seems like it. Been using NoGravity kernel 2.2.0 and the NoGravity app 5.2 for a few hours now. So far no glitchy touch. Even has a touch firmware selector for testing two different versions of the firmware. Default has been fine. Unfortunately battery drain seems higher even with battery saver profile selected.

I am using perry the kernel since before this latest version.. it was fine
after updating to the latest version, ghost touch happens randomly.
should I use nogravity kernel? but I dont want to root

 

[oRAZY]

I am using perry the kernel since before this latest version.. it was fine
after updating to the latest version, ghost touch happens randomly.
should I use nogravity kernel? but I dont want to root

According to posts from that Thread you can still use the kernel but can't use the app without root. So you can't select any profiles. And I do have higher drain and more heat even with battery profile. I guess best bet is wait for a fix.
People in the telegram group have the same problem with latest update. Sometimes there is a test build in that group. But not yet for latest update.

 

[manojkrs]

Ghost touch issue is back

 

[felixpaz1992]

I want to know 2 things

1. Changing the kernel to NoGravityKernel 2.2.1 the ghost touches disappear?

2. Can you update GPU drivers to v614v2 with CRDroid?

 

[oRAZY]

I want to know 2 things

1. Changing the kernel to NoGravityKernel 2.2.1 the ghost touches disappear?

2. Can you update GPU drivers to v614v2 with CRDroid?

I did not have ghost touches the last 24 hours since I flashed NoGravity kernel 2.2.1.
In my post I said 2.2.0. Because under system info and in the NoGravity app it says so. Just reflashed the 2.2.1 zip file to check. Seems to be a bug because in recovery it says 2.2.1 in the log.
Anyway, so far working well enough. No ghost touches. Only battery drain is higher even with battery profile. Might try another kernel.

 

[vicl89]

In my case I don't have any ghost touches, but some random reboots when I'm playing games or changing apps.

 

[Flr Power]

I don't have any issues on my side except for the infamous delayed notifications when I'm not using phone for a while.

 

[Tomo123]

@neobuddy89 Will you be implementing fixes for OTA update spoofing issues as seen in this post/thread?

https://xdaforums.com/t/fixed-root-...to-google-play-services.4406617/post-87183433

All Pixel based roms are affected, because spoofing. crDroid dev for Moto G5 Plus solved the issue.

 

[TheNewbie212]

having a weird problem when everytime i use Earphone/Headphone/Headset i can't hear my friend or teammate voice in games. even when using discord. but my voice still can be heared by my friends. is there any solutions to this?

 

[neobuddy89]

Update - Android 12

25th July, 2022

Build type: Weekly / Stable
Device: POCO X3 Pro (vayu/bhima)
Device maintainer: PacMM79 & neobuddy89

Short changelog:
* GameSpace - Added notifications customization to choose between heads up, ticker and danmaku style
* GameSpace - Added "Do not change" ringer mode
* GameSpace - Added launcher icon
* GameSpace - Fixed issues with multiple users
* Added Meow icon shape
* Updated sqlite from upstream
* Fixed issue with text select and copy with GBoard
* vayu: Removed unsupported compress input sound configurations (fixes low mic sound on some apps)
* vayu: Reverted back to old touch firmware in kernel (fixes Ghost touch issue)
* vayu: Upstreamed kernel to v4.14.289 stable release
* vayu: Merged latest CAF tag LA.UM.9.1.r1-12100-SMxxx0.QSSI12.0 in kernel
* vayu: Updated blobs from V13.0.5.0.SJUMIXM
* vayu: Relaxed cpu frequency boosting in few cases (better throttling)
* vayu: Silenced spamming sepolicy denials

Download:

crDroid.net - Download crDroid v8 for Poco X3 Pro (vayu)

official crDroid v8 for Poco X3 Pro (vayu)

crdroid.net

 

[Barker88]

I'm running the latest build. I'm having problems with the volume controls. If I'm playing music, i can't have notifications silent. Same goes the other way, if i turn notification volume so the way down, my Spotify volume goes all the way down. I did a clean flash. Considering doing a clean flash of the June build to see if that fixes it.

Anyone else have this problem?

 

[nikapos]

any regrets from moving to crdroid 8 from 7 and moving back?