Hi everyone, i'd like to post my experience with Android Lollipop on my GS5 which is awesome except that since the first day i have the last Lollipop update ( ....L9) my heart rate sensor is always ON . Yep, if the screen is on, even in the lock screen mode, the HR sensor is always ON and if i touch with my finger the sensor, the red light turns on. The big problem is if i place my phone on the table, the red light will be always on. I've noticed that the red light remains turned on the time S Health takes to measure the heartbeat and then it turns off for like 2 mins then turn back on and the problem starts again. I've tried to kill S Health process and Health Service process, but nothing.
It really makes me annoyed.
Thanks everyone.
Tried a factory reset after updating to Lollipop?, heard a few people suggest that it fixes issues with left over trash files from KK
After 2 days trying to figure out and making a lot of factory reset, i found a partial solution ( because i like the app ). The problem is Google Fit. When it is installed on the phone, i don't know why it keeps the proximity sensor of the Heart Rate always on, when the screen is turned on. Disinstalling Google Fit and wiping the cache app, as i said, i solved the problem.
Sballa said:
After 2 days trying to figure out and making a lot of factory reset, i found a partial solution ( because i like the app ). The problem is Google Fit. When it is installed on the phone, i don't know why it keeps the proximity sensor of the Heart Rate always on, when the screen is turned on. Disinstalling Google Fit and wiping the cache app, as i said, i solved the problem.
Click to expand...
Click to collapse
I have the same problem, but i solved it with a disable of activity detection in google fit and a reboot.
It sucks since i have a smartwatch, but i don't want to burn out the heartrate monitor.
Strange Ive heard a few people saying the HR sensor is stuck permanently on, not had that problem this end
Just noticed the same issue with the red light from the heart rate sensor. It was lit when I put down my S5 when the screen was on, will go out as soon as the screen goes black. I do have Google Fit installed, going to disable that next.
Had the same issue with the heartbeat sensor turning on. Turned off Motion Detection in Google Fit and rebooted - issue resolved. Thanks for the tip
Related
Hey guys. Phone's been good for a long time. Ran cm6 and CM7 nightlys for a long time.. Tonight is real first big issue
WTH.. I already tried Wiping, and nandroiding.
Now booting with old builds, and new build #33 when the screen goes to sleep after initial boot. I can't get it back on no matter what. Needs a battery pull first. Odd.. I'm hoping something isn't wrong with my nexus one. It's really acting up now.. Basically the phone turns on and runs, but the minute it falls asleep it's done for. I can wake it with my Power button, but only the soft capacitive key's light up. No screen. but I can turn the screen/key's off and on with no problems with the button. Just the screen never comes on. but I can watch those softkey's do it. So the power button is working, but it could be going out. but seems to work every time.
I've officially wiped tonight. I tried a nandroid to a past build, I'm thinking I might have a hardware issue.
Any idea's. Screen wont come on after falling asleep. At all, requires a battery pull. (saw this in CM forum) guy said fix permissions fixed it. any idea's?
This might be happening because of the WiFi/BT connectivity bug. If you watch the logcat (or maybe it was in kmesg), you'll probably see lots of errors regarding mmc0.
On the other hand, anything that would get the CPU stuck at 100% throughtput, might do the same, and it might be some other bug.
Try to turn off WiFi and BT and do the same, see if it helps any.
Neither are enabled.. Now it is doing this For sure, completely everytime. I can pull battery and boot phone. Seems to run ok, can open apps. go to market. whatever. but when I go into settings I get Activity FC and it freaks out. I just tried to power off my phone. It's been at the Shutting Down spinning circle part for over 15 minutes. Is it possible the build it 512mb went bad and thats why it can't resume from standby, and stuff?
I'm still testing things. but I've completely wiped and had no luck. and also nandroided to a good working version also. Basically if my phone goes to sleep at all. I can't turn it back on. I have to pull battery.
Same thing here..
Screen will not wakeup from sleep unless I do a battery pull... Any updates?
Its been 1 year since nobody posted, anybody came up with an explanation/solution?
This Issue just appeared in my phone after two years of use.
-When the screen goes to sleep it won't be possible to switch it on again. Either via the power button, time up or proximity sensor.
-The phone and the touchscreen work as always, haptic feedback reveals my unlock slider is still active and the phone can recieve calls and notifications.
-Plugging in the phone or using another button won't revive the screen either.
-The backlight of the screen turns on, but the screen remains black.
-Only removing the battery and waiting at least 10 seconds before putting it in again will let the screen to come back.
-Shouldn't be a software problem as i have wiped several times everything that could be wiped and instaled diffrent Roms, even tested ICS.
-In my case, removing the microSD doesn't change anything.
-Swapping batteries also doesn't help.
Anybody out there with the same problem?
Programmed obsolescense on HTC?
http://forum.xda-developers.com/showpost.php?p=22625457&postcount=11
My N1 developed this issue just a few days ago- I'm looking for a solution as well. I have all of the symptoms you've described, apart from the backlight turning on as I have an AMOLED display. It's interesting to know that the backlight turns on, as it and the video signal are controlled separately (and impossible to distinguish on an AMOLED display).
I've reverted mine back to an official shipping ROM, something really ancient, and it still occurs.
Mine is also right around the 2 year mark. There are a handful of other threads on various forums which describe the same issue with the only resolution being sent in for servicing. I don't know whether it was the screen or the motherboard that was replaced, which would be very helpful to root causing the issue.
I'm not sure whether it's an issue with initializing the screen itself as it is is functional and can turn on after a battery pull/sitting for a few hours. I would guess it's something to do with a capacitor or similar, since the way to get the screen to work is a battery pull +time or to wait a long time before turning the screen back on.
It's a shame, too, because everything else is working just fine in my N1 and I think it is the perfect combination of a phone.
anomalyconcept said:
My N1 developed this issue just a few days ago- I'm looking for a solution as well. I have all of the symptoms you've described, apart from the backlight turning on as I have an AMOLED display. It's interesting to know that the backlight turns on, as it and the video signal are controlled separately (and impossible to distinguish on an AMOLED display).
I've reverted mine back to an official shipping ROM, something really ancient, and it still occurs.
Mine is also right around the 2 year mark. There are a handful of other threads on various forums which describe the same issue with the only resolution being sent in for servicing. I don't know whether it was the screen or the motherboard that was replaced, which would be very helpful to root causing the issue.
I'm not sure whether it's an issue with initializing the screen itself as it is is functional and can turn on after a battery pull/sitting for a few hours. I would guess it's something to do with a capacitor or similar, since the way to get the screen to work is a battery pull +time or to wait a long time before turning the screen back on.
It's a shame, too, because everything else is working just fine in my N1 and I think it is the perfect combination of a phone.
Click to expand...
Click to collapse
Format your SD-Card. It's known to fix it.
Thanks for your suggestion, but unfortunately it does not fix my issue.
I've tried different SD cards, repartitioned & formatted the card (previously had a sd-ext partition), and even running it without an SD card- all either won't turn the screen on during boot (starting with the battery out) or will fail to wake the screen.
My logs don't show the mmc0 errors which would indicate an issue with the card; it seems to be pretty normal for the screen turning on and off, just that the screen doesn't actually initialize and display anything.
About a week before the screen wake issue developed, I had a problem with the camera and gallery thinking that the SD card was not present. I eventually wiped and reloaded an older ROM and the problem went away.
I replaced the AMOLED screen and it now properly works. Since the screen was able to turn on by itself after an hour or so, I suspect it might be a capacitor or something that's gone bad on the flex cable itself. I'm not sure how much effort I'll spend tracing it down, but I might at least give it a shot.
Change the Screen
Had same issue with a Nexus 5. I changed the screen and it worked great.
xguntherc said:
Hey guys. Phone's been good for a long time. Ran cm6 and CM7 nightlys for a long time.. Tonight is real first big issue
WTH.. I already tried Wiping, and nandroiding.
Now booting with old builds, and new build #33 when the screen goes to sleep after initial boot. I can't get it back on no matter what. Needs a battery pull first. Odd.. I'm hoping something isn't wrong with my nexus one. It's really acting up now.. Basically the phone turns on and runs, but the minute it falls asleep it's done for. I can wake it with my Power button, but only the soft capacitive key's light up. No screen. but I can turn the screen/key's off and on with no problems with the button. Just the screen never comes on. but I can watch those softkey's do it. So the power button is working, but it could be going out. but seems to work every time.
I've officially wiped tonight. I tried a nandroid to a past build, I'm thinking I might have a hardware issue.
Any idea's. Screen wont come on after falling asleep. At all, requires a battery pull. (saw this in CM forum) guy said fix permissions fixed it. any idea's?
Click to expand...
Click to collapse
Hello!
Last night as I was toggling on TeslaLED to shine some light with the flash for the camera, the light turned on for about a half second and then turned off...at the time I just assumed that TeslaLED had crashed or something and didn't think anything of it...however, now in testing the flash for the camera as well as TeslaLED and the Torch app that is built into my ROM I am finding that nothing is able to make the light come back on...
So far I've tried:
1) rebooting the phone
2) using the camera app, TeslaLED, and Torch to make the light turn on
3) rebooting the phone and clearing all app cached data (which has apparently been a fix for others: http://www.droidforums.net/forum/droid-razr-support/218009-camera-flash-not-right.html)
Anyone else have any suggestions? I am not knowledgeable about LEDs or anything but I'm wondering if it "burnt out" (if that's even possible)?
I'm no stranger to replacing hardware--I've already replaced the motherboard in this phone once, and I see that replacement LED/flash things on eBay are pretty cheap...but opening up the phone is such a pain! I'd like to exhaust all other options first.
Thanks!
My rear camera flash is lit up. When I power it off, the flash is still lit. I have tried clearing my cache, a full factory reset, and even tried taking a picture to try and turn it off. It is still on. I'm currently running the battery til its dead, at 65% now, and do a full recharge to see it if fixes it. I'm running on a fully stock Rom with no updates to install. Any ideas are more than welcome. Thanks.
Looks like nobody replied to this. Given the few days that have past, you may have already resolved this issue, but I'll have a go at it anyways. My first thought is that since the light stays on even when the device is off, it could very well be a hardware defect. My second thought is that you should open up the flashlight app (or download one from the play store if it didn't come with a rom) and attempt to toggle the LED via the app.
Hi,
I'm having an issue with my Gear Live : sometimes the screen won't turn off (or dim) by itself. when I stop using it it will just dim slightly but still display the whole watch face and not get as dark as when it dims properly. It seems to happen randomly after I use it (with an "OK google" command or something) and then it will only turn off if I use the button or cover the screen. From the moment it starts acting up, it will never turn off automatically untill I reboot the watch...
Has any one else experienced this, or even have a solution ?
I hoped today's update would fix the problem but it didn't, so it keeps happily eating all the battery if I don't pay attention.
Thanks.
BlueScreenJunky said:
Has any one else experienced this, or even have a solution ?
Click to expand...
Click to collapse
My wife and I each have a Gear Live. We've experienced this problem repeatedly over the last 2 years. Restarting the watch fixes the problem temporarily. Sometimes the problem will go away for months on end. Other times it happens over and for over days. I'm guessing it's some kind of hardware fluke on the Gear Live.
Occasionally my phone will just go crazy, screen will get all jittery,touching on a menu doesn't work ,it mainly happens on noughat stock and custom ROMs.,random apps popping up.any experience anything like that?a simple reboot fixes the problem.
russ722 said:
Occasionally my phone will just go crazy, screen will get all jittery,touching on a menu doesn't work ,it mainly happens on noughat stock and custom ROMs.,random apps popping up.any experience anything like that?a simple reboot fixes the problem.
Click to expand...
Click to collapse
It's an inherent issue with some displays present on the Moto G4. It most often happens when you charge your phone. Too much current builds into the frame of the display and you get weird ghost and jitter touches.
No way around it unless you send it in, and even then it may be only a temporary fix.
I also face this issue. Unable to find solid solution for this. Finally i decied to go for custom rom like RR and Invicta. This still comes occasionally(when Heats too much during phone charging)
russ722 said:
Occasionally my phone will just go crazy, screen will get all jittery,touching on a menu doesn't work ,it mainly happens on noughat stock and custom ROMs.,random apps popping up.any experience anything like that?a simple reboot fixes the problem.
Click to expand...
Click to collapse
On my phone this happens while not charging. Seems to happen about one out of every 3 times the phone is unlocked using the fingerprint sensor. Locking the screen and unlocking via a pin seems to be a reliable way of getting past the issue. Though occasionally it happens on the pin entry screen before it the pin has been entered. Needless to say, it IS annoying.
Same problem which is fixed.
I had this problem with the factory firmware too, intermittent bouts of the phone going crazy with phantom touches on my Moto G4. I sent it to Motorola/Lenovo after the supplier gave me their phone number and they did find the problem and fix it. Now I can play graphic intensive games even during fast charge and the phone is awesome for once. : )
Please note they will fix it for free if in warranty and bootloader not yet modified.
Pressing power button to turn off the display and then pressing power button again to turn the display back on will provide temporary relief from jittery screen. I noticed that the jittery screen has twice subsided over time but came back twice immediately after OS upgrade so blaming the problem on charging, or hardware doesn't seem accurate.
Updated 5/20/2018
As a last ditch effort prior to buying a replacement phone I deleted all apps I installed, reset phone and reinstalled fresh copies of most if the apps I needed.
I don't recall every thing I did but my focus was to delete everything I could and then reset phone back to factory state. After reinstalling, my jittery problem went away and has not returned. Your millage may very, so no promises. Phil
. I have touch screen issue(ghost touch) but this time not screen burn issue.. Now there is in winter.. I have checked battery temperature with ex kernel manager. When i go outside in fog or cool weather and when battery temprature goes to less than 20 degree Celsius phone gonna mad..back key home button automatically pressed..Is there any solution? Without going service center And fix battery battery temperature to 25 degree.?
phone going crazy
Hi,
I am having the same exact problem. I have observed that Google Assistant is intruding because each time this happens, Google Assistant is trying to run. Reboot is a temporary fix but the problem persists. I have removed most of the third party apps just to see if anything changes but it did not work.
This is not something that was happening from the start. I have the phone for about 2 months put the problem only started a couple weeks ago. I would love to hear if there is a solution and what. Thanks
Sadly, but compared to the issues visible indoors, in outdoors this Lenovo gift turns complete crap:
youtu.be/dTcHclVEfCg
"Lenovo Moto Z2 Force touchscreen gets completely unusable when getting outdoors! The video is made at about 0 degrees Celsius. So it takes about 30 sec from getting MotoZ2 Frc to sleep with pwr btn (and wakeing up back) to see the touchscreen goes crazy. At -10C, it takes ~5 sec. At +15-20C, after several min it becomes unresponsive and have to use pwr button to recover.
Lenovo, what you have done to Motorola ?!!"
Can it be fixed somehow with changing the upper protective part? I have seen comments that the touchscreen can stop working completely, if peel off the cover part..