After 1 day after restart the phone this sensor stop working until a phone restart again.
SO annoying, before android 10 I did not have this problem. every update the phone goes to worst.
Related
I have a HTC Touch Pro2 (ATT) with the stock Windows Mobile 6.5 ROM installed.
The g-sensor works fine after you first boot up, and then completely stops working at some random interval. After this occurs, trying to calibrate the sensor results in the two animated levels freezing after first twitching a bit. Attempting calibration obviously does not fix the problem.
I tried using sktools to restart the g-sensor driver. The driver will apparently stop, but it will not restart.
The only thing that works is a reboot. Honestly, I wouldn't mind rebooting this damn thing every time but it also freezes for like 15 minutes after I restart it. If you hit the power button to put the phone to sleep right after booting up, it will remain asleep and not respond to anything for almost a half hour. Sometimes calling it will wake it up though... and then it freezes again when you put it to sleep if it's within 20 minutes of boot up. The service process (services.exe) and manila show high CPU usage during this time.
Also the notification manager does not start up automatically; its service needs to be started manually each time. Setting it to manual startup mode does not fix anything.
Halp
Stock ROM?
Have you tried some of the aftermarket ones? Some of the issues in the stock ROM were fixed by the community.
Have you tried a hard reset to see if there is an app messing with your phone?
So many threads about proximity sensor problems, but none of them with the right answer...
I have this problem with my Sensor were everytime I reboot my phone or do a Factory reset using recovery,
EVERYTHING starts to work normal. It last for about 5 minutes when the screen no longer turns off when I get a call and get it close to my ears.
I dont know what it is i've tried different Roms and going back to ICS but the problem keeps showing after some time. There must be some Gnex users with the same problem and yet there isnt a solution... perhaps is a hardware problem? maybe not because each time yo reboot or factory reset... the problem goes away. Any help will be appreciated.
So it seems theres something wrong with my sensor.. trying to tap the screen to wake the device doesnt always work and when the screen is on, gesturing through cards the screen will just shut off. I suspected it might have to do with the sensor so i just tested by keeping ambient mode turned on and now everything works fine.. But as soon as ambient mode is turned off it starts acting buggy.
It happened to me a few weeks back and i thought a reboot solved it but yesterday the problem returned and even after a factory reset the problem persists. Not sure if its related to the last update.. could the Android Wear app cause issues?
At this point im not sure what to do except for keeping it in ambient mode..which i really dont want to have to do. Im hoping its software related.. the watch itself is in great shape..never been dropped or anything..the only other thing i can think of is it started happening again last night after i finished running and the watch back and band was pretty sweaty. This watch should be able to withstand some sweat though no? ..it is water resistant after all.
My phone is a non-developer version that I bought from the verizon store about a year and a half ago. I installed the OTA update from verizon a couple of weeks ago for Marshmallow and ever since I updated my phone no longer vibrates for anything. The haptic feedback vibrations have stopped, notifications and the phone ringing don't vibrate either. I've gone through all of the sound settings on the device and no matter what settings I use the phone just doesn't vibrate. Oddly enough the other day when I powered off my device and removed the battery then put it back in and turned it on the vibrations came back for only a few seconds before stopping completely again. Seems to me like there's some sort of hardware problem but I don't understand how that could've been caused by the update. Vibrations worked perfectly fine for me before updating and even though I like Marshmallow i'm starting to wish I never upgraded in the first place. I almost constantly keep my phone in Vibrate mode when i'm out and about but this update has forced me to keep my ringer on at all times now. Please let me know if there's any suggestions out there on how to fix this annoying issue!
You can do a factory reset, save what ever is important to you before do the factory reset..
Hi everybody,
Is anybody else having the issue that the screen starts blinking (turning off and on) when you turned the screen off and later back on again?
At the moment I can use my phone only right after rebooting, after that the screen will keep going on and off till I reboot.
I have experienced this a couple times so far. The screen just keeps waking up a few seconds after it turns off (either from timeout or manually turning it off) and it loops until I reboot.
Interestingly it also happened on my 6P once. It might be an Android 7 issue or a rogue app? I think it happened to my 6P before I got the 7.1 beta OTA.
Kicking this one up cause I get the feeling I bought a broken phone.
I also checked and when I do a factory reset the screen flashing also happens during the setup wizard.