Any one here please help me to fix this problem.
My Mi5 screen always turning on randomly with no reason, no notification or something waking up phone like normal.
You can watch this https://www.youtube.com/watch?v=gQDONn-2mqQ&t=1s or https://www.youtube.com/watch?v=FGRCZSTcLBY to more clearly what happened.
Many users on MiForum discussed about this issue but no one solved.
I had that problem, the solution was(like for many other ppl) disable "wake device" option from the home button, I'm using LOS 16
i have faced this problem. as he suggested bydefault we have option in various custom rom you can do it. if you want to do it in miui roms, or the custom roms which doesnt have it.
if not, than i recommend editing system/usr/gpio-keys file & generic file and add # to home button in both files. reboot . problem will disappear.
a detailed guide is avialable here.
https://forum.xda-developers.com/mi-5s/how-to/tip-how-to-disable-hardware-key-enable-t3513058
https://forum.xda-developers.com/mi-max-2/themes/mod-disable-hardware-keys-lineageos-rom-t3696108
and use this method to enable softkey and disable hardware keys. i have done it. it works great.
Have you enabled Ambient display at: Settings-Display-Advanced-Ambient display?
Related
i flashed to the auxura rom last night from clean factory stock, havent had any issues thus far. started messing with gps settings (sensor aid, jm9 flash, etc) when i turned off the sensor aid option and hit the back button, the menu fc and then the phone went to the boot screen and stayed there. did a battery pull and then rebooted the phone and everything seemed normal until i realized that auto-rotate wont work for anything. tried switching it on/off, rebooting, etc and cannot get it to work for ANYTHING.
having searched and seeing that there is a similar thread in the galazy s19000 q/a it says that auto rotate sometimes simply stops working for no reason, issue is not reproducable, and the only way to fix it is to reset the phone. would that be the case for the captivate since they are similar and the auxura is based off of the 19000 rom?
anyone have any ideas on how to troubleshoot?
Try disabling and enabling the button for Auto Rotate in the tray.
MikeyMike01 said:
Try disabling and enabling the button for Auto Rotate in the tray.
Click to expand...
Click to collapse
yup, did that (sorry should of been specific that i did it in setting menu as well as the tray), made no difference. i suspect this situation is similar to the 19000 situation and have no choice but to re-flash again and see what happens.
couldnt figure out what caused the problem through the forums so i'm just gonna mark it up to it being a random 19000 thing and reflash. lets hope it doesnt happen again.
Pvster said:
couldnt figure out what caused the problem through the forums so i'm just gonna mark it up to it being a random 19000 thing and reflash. lets hope it doesnt happen again.
Click to expand...
Click to collapse
I have a Samsung S Captivate from At&T. I'm experiencing that same issue of not being able to auto rotate the user interface.
Settings are correct. But I think I have issues with my gyroscope and I'm not able to calibrate the compass either. Any ideas?
I found this interesting post to calibrate a messed up gyroscope, and it worked for my captivate.
You have to be rooted. Place the phone on a flat surface, then type the following in terminal:
Code:
adb shell
su
/system/bin/sensorcalibutil_yamaha
heY STOP DONT CALIBRATE ANYTHING!!!
the new axura rom LAUNCHER doesnt have auto rotate , only in the messenger and web browser. If you use launcher pro, you will have your auto rotate back just make sure the box is checked and you will be golden.
I too encounterd this issue so thats how I know
I had rooted my phone and fash rom Cezar's Basic include root by voodoo. But when i tick auto rotate in Setting>Dislay> Auto rotate then monitor auto rotate horizontal on message, browse and memo and I rotate phone to vertical -> Monitor not rotate to vertical-> Any one help me!
Running Cog 2.3b8 I magically lost auto-rotate. Checked the setting in the notification tray, Settings > Display and the settings for LauncherPro. Nothing worked, rebooting did nothing.
Running /system/bin/sensorcalibutil_yamaha in ADB SHELL as su worked. Problem solved and saved me from having to reflash the ROM.
The volume level for the HTC phone app resets to maximum volume (and blasts the speaker's voice) after a certain period of time. I normally like to keep it at two volume levels from the bottom. The problem existed on ViperOne versions 5.0 and subsequent versions (all flashed after a complete wipe and run on either of the latest 401.8 or .9 firmware). Because of this issue, I have switched to another ROM, where the problem doesn't exist. I haven't tried version 5.7 because nothing in the changelog suggests this problem was addressed. I want to go back to ViperOne because the customizations offered are astounding.
I have tried the following to fix the problem, but none have worked:
1. killing the phone app
2. disabling Beats
3. upgrading to .9 firmware
I didn't mess with any phone or sound customizations in Venom Tweaks.
It appears another user posted about this problem in the ViperOne thread but nobody answered it.
@Turge, @j to the 4n, @hansbert: I have done a complete wipe and flashed the latest version, 5.8, but the problem still exists. I've also disabled Sound Enhancer and Beats and changed media permission with the phone app, to no avail. Any suggestions?
mpmtx said:
@Turge, @j to the 4n, @hansbert: I have done a complete wipe and flashed the latest version, 5.8, but the problem still exists. I've also disabled Sound Enhancer and Beats and changed media permission with the phone app, to no avail. Any suggestions?
Click to expand...
Click to collapse
I call or getting called daily...and never experienced that issue. I think if if would be a general issue, we would have more reports.
When you did the clean install, I hope you didnt restore any 3rd party apps before testing it?
j to the 4n said:
I call or getting called daily...and never experienced that issue. I think if if would be a general issue, we would have more reports.
When you did the clean install, I hope you didnt restore any 3rd party apps before testing it?
Click to expand...
Click to collapse
I did not install any third party apps. I don't think third party apps are the problem because I have used the same apps on other ROMs w/o the same issue. After searching, I found other people have experienced the same problem on different phones. A few reported the problem was a third party app, but I don't have the apps they deemed the culprit on my phone.
I'm running the same firmware as the ROM base. I did a complete wipe, chose stock config, ATT tweaks, and I did choose the option in AROMA to remove some apps and selected some HTC apps (although I can't think of a reason why this would affect the volume). If nobody else is reporting the same issue, it may be due to the extent my phone configuration differs from others'. It may be the combination of options I chose in the installer. I will to do an install with only default options selected and report back.
I think the source of the reset is remapping, in Venom Tweaks, any of the buttons (except of course the power button) to the action of turning off the screen. I installed the Volume Locker app, which locks the call volume and sets off the LED when there is an attempt to change the call volume. By accident, I noticed when I turned off the screen, many times the Volume Locker program would set off the LED and notify me that there was an attempt to change the call volume (what it called the "voice volume"). After some experimenting, I found I could replicate the problem every time I turned off the screen by a long press of the home button (I had always mapped this particular input to turn the screen off in Venom Tweaks).
Also, if any other button (e.g., double tap of home, volume down) except the power button is mapped to turn off the screen, there is an attempt to change the call volume by increasing it one level. If the button is used repeatedly to turn off the screen and the volume level is not readjusted, the volume level reaches maximum. On the other hand, if I use only the power button to turn off the screen and disable Volume Locker, no change in call volume occurs. So I think there may be an issue in the way the buttons are mapped to turn off the screen.
Can somebody else try to replicate this issue to verify I'm not mistaken?
@j to the 4n: If you think this problem merits attention, I can send you a bug report log. Just let me know.
Hi, i'm not allowed to reply to the original thread, so i will ask here.
First of all logcat seems to be disabled in this rom, and i can't find out how to enable it. I tried searching in the options, and while it points out to the "kernel performance" section, there is no "disable logging" option there (see attached pictures).
I also tried searching in the init.d folder but couldn't find the line.
Now to the real bug.
The "phone proximity" app in this rom is crashing 50% of the time when receiving a call. This causes problems as it doesn't re enable the screen when it is supposed to, and the error messages are making it difficult for my father to operate the phone.
Is it a known bug in this rom or is it fixable with wiping and reflashing? How should i fix this?
Also while we are on the topic which gapps are recommended? I used "pa_gapps-modular-nano-4.4.4-20150410".
@mkaluza any thoughts ?
Hi!
To enable logcat either type "modprobe logger" as root in a terminal or use any module loading app (KoControl) to load logger module.
As for gapps - i used pa_gapps-modular-micro-4.4.4-20140725-signed.zip because I simply have them They update affterwards anyway so I'm not sure if it matters.
As for the bug - I doesn't happen on my phone. But now that you know how to enable logcat, try getting one so we have sth to work with.
Thanks for helping.
Unfortunately i couldn't replicate the crashing of "speaker proximity" today. I tried calling from a different phone a dozen times, but it never happened.
I hope it was magically fixed because i'm not the one using the phone so i can't monitor it on a day to day basis.
Hello, I'm having issues with double tap to wake screen on custom ROMs.
I tried different ROMs(rr pie, dotos extended..) and sometimes double tap won't work, this happens randomly sometimes it's working sometimes don't. I tried with custom kernel available in xda and still the same issue occurs .
Anyone facing the same problem or is it just me, is there any way to solve this?
Edit: just perform a full wipe (system,data, cache...) and a fresh installation and now double tap don't work at all. Am I missing something ?
Solved!!!! Miui camera port was the culprit as soon as I uninstalled it dt2w worked again
Hi
I have a strange issue when using Android Auto on car head unit through my Mi9 MIUI Global 11.0.5.
Everything connects fine as expected and everything displays correctly until the phone screen times out, then the car head unit loses roughly a quarter of the right hand display (has overlay of black bar from top to bottom of screen). The icons / screens still work if pressed where graphics would be, but they are not displayed.
i have tried altering notch setting / full screen display settings but nothing corrects the issue.
......any ideas?
Thanks in advance.
Mr E Weasel
This is the same problem as in a non MIUI (AOSP) rom. Disable HW overlay in developer option solves this.
However. This shouldn't be a problem on a MIUI rom that's why I don't use the AOSP ROMs for now.
So it's very weird.
......thanks for the reply and good call @KaiseRRUby. I tried that but as you probably suspected it did not solve the issue, also the state does not persist after a reboot.
DUPE
Having the same issue since updating to Miui 11. Have you found a solution?
taliesyn said:
Having the same issue since updating to Miui 11. Have you found a solution?
Click to expand...
Click to collapse
......not yet, I will endeavour to post back with any successes
Same problem on Mi 9T Pro here.
I have enabled developer options and enabled the option to keep phone awake while charging.
taliesyn said:
Having the same issue since updating to Miui 11. Have you found a solution?
Click to expand...
Click to collapse
I did a workarround by using the free Android application "Automate" by LLamaLab. I setup a basic script looking if i am in my car (Check car bluetooth connectivity) and then delay the screen lock. When not in my car anymore (no more car bluetooth connectivity) re enable the screen lock as it was.
It is working like a charm.
I had same problem, you can turn on Always on display it will fix it
UPDATE:
Only way round it I have found so far is to use tasker (https://play.google.com/store/apps/details?id=net.dinglisch.android.taskerm) to display full black screen and set screen time out to max time when it see Android Auto launched.
discerrrr said:
I had same problem, you can turn on Always on display it will fix it
Click to expand...
Click to collapse
I've always had AOD activated and it does not help.
The solution for me was to enable keep screen on while charging in developer settings. Since the phone is always plugged in for AA, it works fine.
I don't know why some resolve to using scripting apps for this. Did you try this setting and it did not help, or maybe you don't want to keep the screen on while charging ? You can always turn it off by pressing the power button, so it seems like the almost perfect solution to me.