Database Develop

[Q] to lolipop rom users

Hello guys,
I've been testing all lolipop roms that had listed everything as working. Such as crDroid, CandyRom, SlimLP. On every of those lolipop roms pretty much most of the important stuff worked. There were stuff like equalizer not working or too dim notification LED, but from time to time I got touchscreen freezes. I mean I could use phone for a couple hours and then the touchscreen would freeze really often, sometimes it froze for couple of seconds and that was it and sometimes it could last for 10 minutes. This is really annoying and unacceptable if developer says that the touchscreen works.
I ended up contacting crDroid developer - davidteri81 and he said that the touchscreen works fine for him. I asked in the thread and I got only a single response saying he doesn't have this issue, but the sensivity is too high.
I've tried like literally 4 lolipop roms on my Z1 and each one of them had those touchscreen freezes. I even ended up flashing liquidsmooth in which I didn't had this issue, or it just didnt had the chance to happen since most stuff doesn't work there and it isn't usable as a daily driver so I quickly got rid of it.
My question here is:
Do you get touchscreen freezes? Please reply only after minimum 24h of usage. If you don't have any touchscreen freezes on lolipop rom on the Z1 then please, tell me what Lolipop rom do you use as I couldn't find any that wouldn't have a buggy touchscreen.
Please tell me if it works for you without issues or do you also have this issue on the Z1 as I'm puzzled because it couldn't be just me since I did a full phone wipe, flashed the phone clean, even wiping internal memory, but it still happens and I cant find a way to use any Lolipop rom everyday on my Z1. The more replies I get, the better.

@olokos: I'm on CM12 official and use it now for many days. In this time I never faced any touch freezes on my Z1.
I've got some other "bugs" that confused me a bit and make some manual fixes like Wi-Fi MAC. But for me I can say that this ROM is really stable and I use it as my daily driver.

schickel said:
@olokos: I'm on CM12 official and use it now for many days. In this time I never faced any touch freezes on my Z1.
I've got some other "bugs" that confused me a bit and make some manual fixes like Wi-Fi MAC. But for me I can say that this ROM is really stable and I use it as my daily driver.
Click to expand...
Click to collapse
Same for me, although, the touch screen did freeze once, but I locked it and unlocked it and it worked again. It's probably hardware since I got my Z1 replaced because of this issue that even happened on stock ROM occasionally.

using CandyRom 5.0.2
I never faced any touch freezes issue

@olokos: I'm on 20150214 and now I've got touchscreen freezes. This is the first time for me on Z1.
But I think that this could be a global Cm12 issue, because my Nexus 7 also get some freezes and I thought that something is wrong with my fingers or tempered glass.
The problem is how to debug this?

im on candy 5 and my screen dont freeze, but my screen percieves touches from nowhere... but only if i have earphone plugged in .. thats more than just annoying
anyone has the same prob?
sry for my really bad english

Touchscreen freezing issue definitely isn't hardware issue on custom roms. I haven't tried CM12 or any other apart from those listed on XDA, but I will propably build some lolipop rom from source by myself if I get enough reports that will be useful for me. If touchscreen works for you then please, tell me what rom you are using and for how long you use it, what't the way you flashed it.
I only need those 3 things. If touchscreen doesn't work just for me then I'll build my own stock based rom based on Sony sources. I just have to make sure that the touchscreen issue isn't just on my side.
All I need is:
Do you have touchscreen issues? Yes/no
What ROM/Kernel you are using? CandyRom 5.0
For how long? 5 weeks
Answer those 3 questions, legitimately and I'll consider that. I'm not sure If I'll have enough time to work on this, so please, be honest with your answers because I'm not going to fix the touchscreen, or maybe I will if it doesn't happen for everyone.

I experience dramatic touch screen freezes as well since the first time I installed Lollipop nightlies. (4 weeks now). Tried clearing cache, factory restores, de- and reinstalling apps. Reflash kernel, format SD, reinstalling gapps, puzzeling at logcat logs etc. Nothing helps. Random freezes from seconds till minutes. Only thing that 90% of the time will help is keep pressing powerbutton until screen becomes responsive. It happens more when I have a lot of (hangout or whatsapp) notifications, or when trying to type something (stock keyboard). Tried other keyboards: no luck. Tried every toggle: WiFi , Bluetooth etc. : no luck.
I experience dozens of freezes a day. Almost to the point that cm12 is completely unusable. Love this ROM, but this is a real showstopper.

1. No
2. AOSP Vanir 5.02
3. Since first availibility (12/14)

I experienced this issue on 2 roms in 2 forms
1. No (coming from Stock 14.4.A.0.108)
2. KitSlim_AMG [Evo 8.1] / iHackers advanced Stock Kernel
3. Since installing the Rom
This was the first time i experienced touch-issues. Not a freeze of the screen, but the screen sometimes started registering touch-events on the wrong places. This was temporarly fixed by locking/unlocking the display.
1. Yes (coming from KitSlim_AMG [Evo 8.1] )
2. crDroid-5.0.2-20150303-honami / 3.4.0-crDroid (packaged with rom)
3. Since installing the Rom a day ago
This time i get freezes. And they are much more frequent than those "ghost-inputs" from KitSlim_AMG. Unlocking the device also fixes it temporarly.

Rotation bug with EVERY available rom!

Hi guys,
Whatever rom I install on my xiaomi mi5, after a certain time, the screen rotation does not work anymore.
To prevent software errors I run always by a clean flash.
In many forums write user that this bug after the update to a specific version Miui disappears.
This is not a' solution for me.
Has anyone else this problem?
Perhaps it is also a hardware defect...

dont think its a software problem, maybe you should get your phone checked out

njuz said:
Hi guys,
Whatever rom I install on my xiaomi mi5, after a certain time, the screen rotation does not work anymore.
To prevent software errors I run always by a clean flash.
In many forums write user that this bug after the update to a specific version Miui disappears.
This is not a' solution for me.
Has anyone else this problem?
Perhaps it is also a hardware defect...
Click to expand...
Click to collapse
Its of course a well know bug for all mi5 roms. I read yesterday that last thursday rom update fix this:
"Fix - Accelerometer and gyroscope didn't work after and OTA update (08-12)
Fix - Accelerometer and gyroscope didn't work normally (08-12)"

The problem occured with miui as well as with unofficial CM build, what i am using now. This indicates to me that it has nothing to do with the installed rom directly.
After rebooting, everything works fine again.
I suspect apps like Pokémon go to stay in relation to the bug. Since i am not playing that game anymore it occures much rarer...

I am too having this problem with no solution, i guess its not an hardware issue, otherwise dozens of people like us have an defective hardware on their mi 5. I tried MIUI 7.5.2.0 and 8.0.2.0, both global stable, occurs when i play pokemon go for a while, then i go back to any app and the screen does not rotate anymore.
I wonder if it is related to the kernel, since we dont have the kernel sources, all the roms available are based on the kernel miui have, so... Any help would be apreciated.

I was having the same problem. I dont play pokemon. Im still on vendor rom. But now the bug gone i tried to simulate the bug but it rotate normally

I have this issue. I'm on the latest CM 13 build and I get issues where the camera won't take in landscape and full screen videos won't switch to landscape when you rotate the phone. It's so nearly perfect apart from that.

shucrut said:
I am too having this problem with no solution, i guess its not an hardware issue, otherwise dozens of people like us have an defective hardware on their mi 5. I tried MIUI 7.5.2.0 and 8.0.2.0, both global stable, occurs when i play pokemon go for a while, then i go back to any app and the screen does not rotate anymore.
I wonder if it is related to the kernel, since we dont have the kernel sources, all the roms available are based on the kernel miui have, so... Any help would be apreciated.
Click to expand...
Click to collapse
Did you ever fix this bug as a matter of interest? I've just done a full-wipe reset and reinstall of the latest CM13 build and I still have auto-rotate issues. It's really annoying me now because it's a great build in all other respects.

I installed a couple of Sensor Test apps and neither one can see my accelerometer sensor to even test it. So it's like the sensor isn't even there. I know it works because one of Shade.sh's beta CM 13 builds was able to detect the sensor OK! Any ideas?

Here's the sensors detected in the Check My Android app. There seems to be only two axis detectors working. How does this compare to a healthy Mi 5?

sharkyblunt said:
Did you ever fix this bug as a matter of interest? I've just done a full-wipe reset and reinstall of the latest CM13 build and I still have auto-rotate issues. It's really annoying me now because it's a great build in all other respects.
Click to expand...
Click to collapse
Yes, i actualy did. After installing developer version 6.9.18 the problem never appeared again. Now im on 6.9.22 and the rotation bug is gone

Hmm, I've just tried SlimRom and the same bug is present, presumably because it's derived from the same tree as CM 13.
I'm actually tempted to give MIUI 6.9.22 a go then if it's the only way to get this fixed.

I have just flashed the MIUI developer ROM 6.9.2.2 and my sensors are working perfectly now. So it must be something for flaky in the CM stack or Kernel version. See screenshot.

SOS for ROM no MIUI with programmed start

hi everyone, I have problems with the latest MIUI roms, they overheat the device until the touch is blocked. Now I'm looking for a different rom from MIUI that has integrated support for "programmed power" . For me it's an important function and I don't want to lose it. I have tried some aosp Pie roms but none has integrated the programmed ignition such as MIUI. Why no one puts it in the rom ..?

bettuccio said:
hi everyone, I have problems with the latest MIUI roms, they overheat the device until the touch is blocked. Now I'm looking for a different rom from MIUI that has integrated support for "programmed power" . For me it's an important function and I don't want to lose it. I have tried some aosp Pie roms but none has integrated the programmed ignition such as MIUI. Why no one puts it in the rom ..?
Click to expand...
Click to collapse
Because it's a proprietary blob. A few old AOSP roms tried importing it, but it was bugged and unreliable. You'll have the alarm turning on the phone, or programmed switch on/off only on MIUI based roms.
Give RevOS a try.
Wipe cache, dalvik, system and data. Install it, wait 15 minutes for first boot. Set up everything. Wait more 10 minutes. It will become more responsive and stop heating up after a couple of reboots.

dev>null said:
Because it's a proprietary blob. A few old AOSP roms tried importing it, but it was bugged and unreliable. You'll have the alarm turning on the phone, or programmed switch on/off only on MIUI based roms.
Give RevOS a try.
Wipe cache, dalvik, system and data. Install it, wait 15 minutes for first boot. Set up everything. Wait more 10 minutes. It will become more responsive and stop heating up after a couple of reboots.
Click to expand...
Click to collapse
dear friend I have already tried everything, I changed 4 different ROMs Aosp (clean installation) but I understood now that the problem is not the overheating of the processor but it is the touch screen that is blocked. As for the programmed switch-on I discovered that in some ROMs Aosp Pie if I set the alarm and turn off the phone, this causes the system to start one minute before the alarm sounds. A great solution for me. I did not understand if it is a bug of Aosp as the phone does not charge the battery if it is on but if it is off or I have to plug in the power cord and then restart then charge. I have a feeling it's time to switch phones. Thanks anyway ; }

All cool !
bettuccio said:
... in some ROMs Aosp Pie if I set the alarm and turn off the phone, this causes the system to start one minute before the alarm sounds....
Click to expand...
Click to collapse
which Aosp roms? I'm curious to test

dev>null said:
All cool !
which Aosp roms? I'm curious to test
Click to expand...
Click to collapse
I remember 2 of the latest updates. One is "CrDroid" and the other is "Syberia" the one I have right now.

Pixel 4XL Face Unlock

I couldnt find a solution or the same issue on the forums.. so here is my problem:
Pixel 4XLs face unlock is so bad. After a few unlocks the phone says "clean sensor". Rebooting usually does the job for a few hours.
I browsed the web and this error is common on so many Pixel 4/XL devices.
Is there a solution to this? Any CustomROM or Kernel solving this issue?
I am on stock kernel/ROM and wiped the whole thing before freshly installing Android 12.
Thanks!

Matzeus said:
I couldnt find a solution or the same issue on the forums.. so here is my problem:
Pixel 4XLs face unlock is so bad. After a few unlocks the phone says "clean sensor". Rebooting usually does the job for a few hours.
I browsed the web and this error is common on so many Pixel 4/XL devices.
Is there a solution to this? Any CustomROM or Kernel solving this issue?
I am on stock kernel/ROM and wiped the whole thing before freshly installing Android 12.
Thanks!
Click to expand...
Click to collapse
Probably a hardware issue. Find one of the many sensor testing apps and run it several times to identify a weak or defective sensor. There is not going to be a cleaning or software solution. If you do find a sensor not working 100%, do another clean wipe and test again before looking into replacement. Normally the FR on the P4 is extremely fast and accurate.

Thanks @v12xke for your reply!
To be honest, i dont think it's an hardware issue. See this link on the google forums: https://support.google.com/pixelpho...ing-the-dreaded-clean-the-top-of-screen?hl=en
There are countless other posts and threads about this error.
I should mention that the issue was there from time to time on Android 11 too. Looking at googles changelog, they tried to "fix" the issue in their updates. Nothing helped yet.

Matzeus said:
Thanks @v12xke for your reply!
To be honest, i dont think it's an hardware issue. See this link on the google forums: https://support.google.com/pixelpho...ing-the-dreaded-clean-the-top-of-screen?hl=en
There are countless other posts and threads about this error.
I should mention that the issue was there from time to time on Android 11 too. Looking at googles changelog, they tried to "fix" the issue in their updates. Nothing helped yet.
Click to expand...
Click to collapse
Google forums are a joke, this issue has *nothing* to do with Android11 or 12... and no, there is not a fix coming from anywhere. You're going to have to fix it yourself. Have you removed and re-added your facial profile at least once or twice since this started? Have you been able to replicate in safe mode? How can you know it is not a hardware issue if you don't test the sensors? It's just one step in the process of elimination. Try these and you may discover something you didn't know before.

v12xke said:
Google forums are a joke, this issue has *nothing* to do with Android11 or 12... and no, there is not a fix coming from anywhere. You're going to have to fix it yourself. Have you removed and re-added your facial profile at least once or twice since this started? Have you been able to replicate in safe mode? How can you know it is not a hardware issue if you don't test the sensors? It's just one step in the process of elimination. Try these and you may discover something you didn't know before.
Click to expand...
Click to collapse
How can you say google forums are a joke when literally hundreds of people are having the same issue? I dont want to believe that we all have hardware issues. Otherwise the hardware would be some hot garbage.
I removed and readded the face multiple times already.
I booted into safe mode. It works there. But like I said, it also works after a normal reboot for some hours/days before it needs a reboot again.
I also did test the sensors, no errors there. However my next step is to run the test when the error is present.
Any specific suggestion on which app I should use for testing?
Thanks again.

@Matzeus
No specific sensor app. Facial data is stored on the Titan M chip, and the only way I know to wipe that facial data and potentially fix it is by doing a factory reset from the stock recovery. Fastboot flashing will not wipe the Titan data and even from recovery is only a partial wipe. If you've ever had TWRP installed, there is a looong thread on broken face lock there. FDR from both recovery and setup would be my next suggestion.

@v12xke
In the past i ran the factory default from the system settings, didnt help. After that I used Googles "Android Flash Tool", which didnt help either.
Additional information: the device has never been rooted or anything. Always been on stock firmware.
Anyways, small update on the whole thing:
The issue occured again, I ran the app "Soli Sandbox" and it simply didnt do anything. So far so good.
After closing Soli Sandbox and clicking on the face unlock option in the system settings, magically everything worked properly again. Even without a reboot.
I am not sure what solved the error now..
I guess its safe to say, that all motion gestures stop working once the problem occurs.
Will keep this thread updated as I find out more.

I've had absolutely no major issues with my Pixel 4 XL's face unlock. I've upgraded from android 11 to 12 and still working perfectly. Yeah, i get the odd clean the bar notification but goes away after a bit and it just works.
The face unlock is fantastic on the Pixel 4 XL

The march update claims to have brought some improvements to Pixel 4s face unlock feature. At least thats what they say in the official changelog.
Biometrics
General improvements for face unlock stability & performance *[4]
Lets see if the problem is gone now. Will keep this thread updated.

sufy1000 said:
I've had absolutely no major issues with my Pixel 4 XL's face unlock. I've upgraded from android 11 to 12 and still working perfectly. Yeah, i get the odd clean the bar notification but goes away after a bit and it just works.
The face unlock is fantastic on the Pixel 4 XL
Click to expand...
Click to collapse
It's uncannily good. I keep the phone upright in a cradle by my PC so I can monitor it, and all I have to do is turn my head to peek, and it unlocks every time. It's pretty amazing. I've never had a problem with it.

The last official update didnt help either. My hope for a fix from Google is gone.
-------------------
I have now installed LineageOS. Its been a week and Face Unlock is now working perfectly fine.
Will keep this thread updated in case anything stops working

Matzeus said:
The last official update didnt help either. My hope for a fix from Google is gone.
-------------------
I have now installed LineageOS. Its been a week and Face Unlock is now working perfectly fine.
Will keep this thread updated in case anything stops working
Click to expand...
Click to collapse
Still going strong? And did you notice this issue on Android 10?

@puzzlefighter
Still on LineageOS 18.1, no Face Unlock issues since I installed the ROM.
I am honestly not quite sure if this issue occured on Android 10 already. But i think so, yeah.

Matzeus said:
@puzzlefighter
Still on LineageOS 18.1, no Face Unlock issues since I installed the ROM.
I am honestly not quite sure if this issue occured on Android 10 already. But i think so, yeah.
Click to expand...
Click to collapse
Thanks. I've got a new 4 XL that definitely has this issue but I didn't spend much time with it before updating to 12 from 10. It's a real PITA. I've never installed a custom ROM, but thinking I may need to do what you've done as this is irritating af.

@puzzlefighter
Just go for it man.
I was so upset about face unlock and i regret that i didnt install a custom ROM earlier.
Share your results afterwards please if you installed a custom ROM

this is not a hardware problem, but a software one, it started with the release of android 12, the problem is not in the face unlock sensor, but in the proximity sensor, it sticks, as if it was closed with a finger, I use Pixel experience + 12, this firmware does not have this problem, I'm disappointed with google developers(

Question Buggy software issues

I recently bought the redmi note 11 and updated it to the latest rom of miui 13.0.1.0 stable which is on top of Android 12
Now I am seeing the following issues
1. Ringtone / Alarm / Notification sounds not working
2. Keyboard not opening sometimes and gets stuck, only restart helps
3. Apps start to hang and after that phone does not connect to internet at all even if wifi is connected.
Anyone else facing the same issues if so how to resolve them?
I am looking to install a custom rom if things persists but I don't want to void the warranty yet so any official way to resolve them?

It's always good to do a factory reset after bigger OTA update. I'm not saying it will fix your problem but give it a try. There were many similar situations like yours and this helped them.

I did it multiple times but did not help

asuna594 said:
I did it multiple times but did not help
Click to expand...
Click to collapse
Just in case you didn't do it this way, it's not the same, flashing firstly, then wiping, but the reversed way, formatting data, to receive a major update, and search for the fastboot latest version, if it exists, I didn't look for, so I don't know.

@asuna594 Did you somehow fixed that problem? After upgrading to A12 I have similar problems: Often no notifications (like Whatsapp), even after unlocking the phone (I manually have to open WhatsApp to get new messages).

I tried ROM flashing the phone with an official ROM from Xiaomi website. But it did not work. So I got a new phone under warranty. It was a painful experience after buying a new phone.

Oh, great I'll try factory resetting the phone and hope it helps. If not I have to contact Xiaomi... thanks!

I had a lot of problems on A12 from battery, performance, to questionable feature implementations. Downgrading to latest A11 was the most stable option for me, though you will miss out on the security patches and some new features. Maybe you can try Xiaomi.eu or custom ROMs and see if it works for you.
Currently using an Android 13 custom ROM and have almost the same performance and battery usage, if not better than the previous Android 11. Definitely better than stock MIUI A12

Thanks. I just resetted my phone and reinstalled (almost) everything. Will see if it works now... if not I'll also try to find a custom ROM (which might be difficult since I have the 11s, not the 11).

joerg78 said:
Thanks. I just resetted my phone and reinstalled (almost) everything. Will see if it works now... if not I'll also try to find a custom ROM (which might be difficult since I have the 11s, not the 11).
Click to expand...
Click to collapse
Ah I see. There are little or no development for Mediatek SoC since they don't release the source codes to public. Hopefully the reset will fix the problem
Another thing that might help is to let some apps to run without restrictions, let them autostart, and disabling Battery and Performance either by revocation or ADB to prevent it from being closed. More details on here
[PSA]: com.miui.powerkeeper acts like a malware, remove it trough ADB for increased performance
This is MIUI battery optimization service that aggressively kills apps in background for a negligible battery gain. This device already has more than efficient chip, and does not need this aggressive background app killing to get to 8-10h of...
forum.xda-developers.com

notBradPitt said:
Another thing that might help is to let some apps to run without restrictions, let them autostart, and disabling Battery and Performance either by revocation or ADB to prevent it from being closed. More details on here
[PSA]: com.miui.powerkeeper acts like a malware, remove it trough ADB for increased performance
This is MIUI battery optimization service that aggressively kills apps in background for a negligible battery gain. This device already has more than efficient chip, and does not need this aggressive background app killing to get to 8-10h of...
forum.xda-developers.com
Click to expand...
Click to collapse
Thanks for your link, I will try to remove powerkeeper if my phone is still buggy because of MIUIs aggressive power management

I hope my problems are fixed now, at least most of the time notifications work well. What I did:
- Factory reset
- In Settings I've search for "Special Permissions", went to "Unrestricted Data" and toggled WhatsApp to "on"
- Switched the region of the phone to "India", searched in Settings for "intelligent scenarios" (at least that's the translation german to english) and switched that setting to "off"
- Disabled Memory Extension

Indonesia rom work good