Hi guys, my mom owns a Huawei Ideos X5 U8800 which is maintained by me and currently running on MIUI Project-X dated back to June 1. Been running fine for the past couple of months with superb battery life, until recently. After updating some applications in the Google Play Store, the battery life dropped tremendously. After checking with BetterBatteryStats, I noticed that 'Proximity' is on the top list under Kernel Wakelocks clocking in 22 minutes after restarting the phone and leaving it on idle for almost 30 minutes. Looked at the proximity sensor and it was flashing red constantly even with the screen locked. So anybody out there care to enlighten me of any solutions for my case? The battery life is seriously bad now since the phone rarely enters deep sleep mode.
Thanks.
My battery life also suddenly dropped and I have a red light blinking to, what does that light mean? I'm also very curious to what is causing the drain.
Sent from my U8800 using Tapatalk 2
Some app must be using it. The led flashes if it detects proximity, so check if you have installed any apps that use it ( like smart screenoff and such).
Btw, the led uses 50ma on Huawei kernels. It's actually possible to decrease it to 6.25ma, but that and much more is to come in the future .
Sent from my U8800
Sorry if this is a dumb question but what is proximity?
Sent from my U8800 using Tapatalk 2
It is a know bug of the latest Viber update..
Ahh, then I know what's causing the problem. Thanks
Sent from my U8800 using Tapatalk 2
Proximity sensor is used to measure the distance between sensor and near located object. For example, when you hold your phone against your ear, proximity sensor tells the phone to shut down the screen, so your ear won't quit your call by mistake.
ezet said:
It is a know bug of the latest Viber update..
Click to expand...
Click to collapse
Problem solved! Thanks bro!
Just rolled back to a previous version of Viber which i backed up earlier with Titanium Backup and I see the proximity sensor had stopped blinking. Only tomorrow I'll know the final results but for the moment it seems that Viber was the main cause of the battery drain.
Related
Hello people.
I've just installed JPF on my phone, running really smooth, GPS Fixed, Battery 36 hr+ with normal use.
Fixed gallery using up all battery with SGS tools.
But now i've got that display is using more than 80% of the battery
Any way to fix this? I have it at the lowest brightnest possible.
I've been told that this could be an error with the sensors.
Any advice?
Thanks
That could indeed be an error of the sensor. Could you try using the phone and posting real time battery life? That might help you decide if the display using 80 pc of battery is negligible issue our not
Sent from my GT-I5801 using XDA App
spsiddharth007 said:
That could indeed be an error of the sensor. Could you try using the phone and posting real time battery life? That might help you decide if the display using 80 pc of battery is negligible issue our not
Sent from my GT-I5801 using XDA App
Click to expand...
Click to collapse
battery worked for 40 hours then dropped from 40% to 5%
How to fix sensors not working??
Battery sudden drop is just a stat problem. Could be a internal calculation math problem. JPF firmware have good battery backup compared to all android phones. What is the sensor issue.
apollo5801 said:
Battery sudden drop is just a stat problem. Could be a internal calculation math problem. JPF firmware have good battery backup compared to all android phones. What is the sensor issue.
Click to expand...
Click to collapse
Battery doesn't last longer if i activate data, else battery is fine.
Still looking to fix sensors, display consuming 90% of battery right now
With data activated, i managed to get 12 hours of battery without even turning up the phone display.
I was looking around some of the battery stats and it came to my attention that some sensors seem to be operating alot of the time. I figure this has alot to do with the standby power consumption ive been experiencing with CM7.
The point is, i cant find any way to control sensor behaviour to test this out. Is anyone aware of any app or script which helps with this? Because i have not been able to find any.
Sent from my MB860 using XDA App
seriously? nothing?
im sure someone can come up with something
What sensors are you talking about?
Im not sure, but when i go in spare parts and look as sensor usage it says android system has been using sensors for 3 and something hours and the same goes for dialer and gallery.
whats for sure is that my screen hasnt even been on for half that long, so what im thinking is some of the sensors must be collecting data while the phone is supposed to be sleeping and that should account for some of the phone idle battery usage.
my idea is to turn off all the sensors (which i dont use anyway except for maybe the proximity one during calls) and see how it affects battery usage.
however i have yet to find a way to manipulate or turn off any of the sensors on this phone.
If you disable screen rotation, that will probably shut down the accelerometer/orientation sensor.
turl1 said:
If you disable screen rotation, that will probably shut down the accelerometer/orientation sensor.
Click to expand...
Click to collapse
that one is pretty obvious and while i doubt that will turn off the sensor (might just tell the device to ignore its readings but it doesn't mean the sensor is shut down) there are still 5-6 more sensors running on this device and what im looking for is a way to shut them down on the hardware level. i figure this is kernel-related but still this can't be the first time anyone has brought this up.
Then delete /system/lib/hw/sensors.olympus.so, that will disable them all, they won't even be initialized
Not sure if your phone will like it though, nandroid backup first
turl1 said:
Then delete /system/lib/hw/sensors.olympus.so, that will disable them all, they won't even be initialized
Not sure if your phone will like it though, nandroid backup first
Click to expand...
Click to collapse
currently in the army so i cant say i'm in an environment to be getting my phone into boot loops but do you figure there is a more friendly way to edit that file rather then deleting it?
There's no source for the sensors library, so unless someone wants to disassemble it and rewrite from scratch, no.
and you dont figure that will be something worth looking into in the great journy towards great battery life?
Sorry for hijacking this but how do you enable the the spare parts app?
guybanda said:
and you dont figure that will be something worth looking into in the great journy towards great battery life?
Click to expand...
Click to collapse
I already get more than a full day with pretty heavy use, enough greatness for me
---------- Post added at 10:34 PM ---------- Previous post was at 10:33 PM ----------
Spectre51 said:
Sorry for hijacking this but how do you enable the the spare parts app?
Click to expand...
Click to collapse
CM7 has it on the ROM, for other ROMs you can install one from the market
Not much help, but to confirm your findings, if the proximity sensor is on, a little red light appears. Look out for it. If it is always on, you have a problem.
Sent from my MB860 using XDA App
matthew5025 said:
Not much help, but to confirm your findings, if the proximity sensor is on, a little red light appears. Look out for it. If it is always on, you have a problem.
Sent from my MB860 using XDA App
Click to expand...
Click to collapse
True. However running elixir i see that this phone has 8 sensors in total. It also claims that some of them use between 6 to 8 mA while in use. Cant really say what that means battery wise or even if its correct but i still think its worth looking into
Sent from my MB860 using XDA App
Any sensor in particular you are concerned about?
If im trusting elixir.. the magnetometor, rotation vector and orientation are what we should be concernef about. It claims the rest use negligible amounts but i dont know if we can believe that (says light sensor uses no power at all which i find a little hard to believe)
Sent from my MB860 using XDA App
guybanda said:
True. However running elixir i see that this phone has 8 sensors in total. It also claims that some of them use between 6 to 8 mA while in use. Cant really say what that means battery wise or even if its correct but i still think its worth looking into
Sent from my MB860 using XDA App
Click to expand...
Click to collapse
8 mA draw would kill your battery after 9-10 days. Not a very significant drain...
Sent from my MB860 using xda premium
guybanda said:
If im trusting elixir.. the magnetometor, rotation vector and orientation are what we should be concernef about. It claims the rest use negligible amounts but i dont know if we can believe that (says light sensor uses no power at all which i find a little hard to believe)
Sent from my MB860 using XDA App
Click to expand...
Click to collapse
Hmmm. The 3-axis geomagnetic sensor in the atrix, the AK8975/B has a
consumption of
- 3-axis magnetism measurement (ave.): 350μA (typ.) at 8 Hz repetition rate
-Power-down: 3 μA (typ.)
That is 0.00035A if it is constantly pooling at 8x a second!
The accelerometer in the atrix is the KXTF9 series and assuming the atrix has the most power hungry version, the KXTF9-2050, it can only draw a maximum of 940μA and typically draws a current of 840μA. It's standby current draw is 0.1μA or 0.0000001A and at that rating, our 1930 mAh battery can keep it in standby for about 2 million years!
In short, the sensors don't draw alot of power, despite what the apps say, it the people who made those sensors say they cannot exceed such a current draw, that's that. You might want to look at apps who are actually requesting the data from the sensors, and not the sensors themselves.
Well then like i said the programs which seem to be using the data are noted as android services, dialer and gallery. So i dont know if theres much you can do about that....
Sent from my MB860 using XDA App
xfinrodx said:
8 mA draw would kill your battery after 9-10 days. Not a very significant drain...
Sent from my MB860 using xda premium
Click to expand...
Click to collapse
Well then according to your calculations: if thats one sensor theb that means 3 sensors would kill the battery in 3 days. Which ofcourse means they would use about a third of the battery in one day.
I personally find this hard to believe but it still means significant drain.
Sent from my MB860 using XDA App
Today while I was in a store and my Defy was in airplane mode, with the screen off in my back pocket - it got super-dooper hot - so hot I felt it through a gel case and my jeans.
I took it out and started to take off the case to get to the battery in a panic but by the time I got to it, the phone had already turned itself off (which is nice if that is some kind of safety feature).
It is a genuine, factory original motorola battery so this is not a problem with a fake battery - it was made in 2011.
Only thing I did recently was upgrade to CyanogenMod 7.2 on the 17th or so but I have been using it since then without problems.
Overclocking options are not on, I'm running with the stock Cyanogen cpu settings.
Airplane mode was on, gps was on, but that's it.
Remember, it wasn't doing anything, screen off in my pocket.
Any ideas? This was kinda scary - glad the phone shut down.
Is there any history of defective batteries from Motorola?
Maybe some program was running and loaded the cpu which drained the battery. The heat came from the cpu and the cpu is just next to the battery.
Sent from my MB525 using Tapatalk 2
Hmmm. Maybe, but when I yanked the battery out it was like a hot potato. Very very hot. I doubt the cpu could overheat it that thoroughly, more like it was being drained fast or possibly shorting?
I turn my phone on every morning from a cold start, the only program that was running was "MyTracks" (hence the gps being on)
I guess I'll keep an eye out for any problem reports with 7.2 on the Defy
It just worries me the times the phone is not in my pocket so I won't feel it overheating.
Is there any kind of app I can run that detects long periods of CPU use and shuts down the phone BEFORE the thermal trigger from the battery?
Does the Defy know it's own battery temperature by any chance? Maybe an app for that for the status bar?
I'm on CM 7.2 and my phone gets hot when I use 3G...
_ck_ said:
...gps was on...
Click to expand...
Click to collapse
There's your potato burner Phone heats up a lot when GPS is on... On the top of that, you kept it in a gel case in your pocket on a (probably) hot day... What did you expect?
Thanks for all the ideas/feedback.
I turn the gps on every day and I have never had this hot battery problem before.
In fact it's on now while I test it and it's not even warm.
This was definitely an unusual event of some kind.
I just updated MyTracks in case there was some kind of bug fix.
As far as 3G, I do not have a sim in this phone (cannot afford any dataplan right now) and I keep it in airplane mode to keep the cell part off.
I found another similar report of the Defy strangely overheating the battery from last year:
http://forum.xda-developers.com/showthread.php?t=1023423
I had this issue abt 2 weeks ago.... it was under my pillow and I went to grab it to check something n I had to let it go at once... I was on cm7.2, my guess was I had flashed so many Roms the day before and maybe the settings of CPU changed from 1 rom to another ... but did NT have this issue again so far .. now am on miui but never knew y it was burning hot zat day
Sent from MB526 using Xda
Same problem here with cm 9; some days ago I found some stuck (blue) pixels on my device.no gps no wireless no data connectivity: it was the usb charger. It happened some months ago too and the stuck pixels disappeared but this time they are a lot....maybe I would put my device in freezer a night in order to recover my display ?_?
Sent from my MB525 using xda app-developers app
i'm still with the original phone (bought about a month ago). didn't change a thing, even not rooted.
a few days ago, was a hot day (about 32 c), same thing happen to me.
the phone was in my pocket in a rubber guard.
i guess it gets really hot in this protector... i took it down and waited a few minutes, then everything was alright.
i think this model might have some problem with overheating, so what i do is try not to leave it in the sun and take the guard on a hot day.
serfus said:
i think this model might have some problem with overheating, so what i do is try not to leave it in the sun and take the guard on a hot day.
Click to expand...
Click to collapse
Thanks for your report, especially since it was stock - but I am sure it's not a regular "running hot" problem - because I have a very repetitive weekly routine and I've never had this burning hot problem before, never in a year.
Remember if they are in our pockets, the screen is off and typically programs are not running hard so the CPU should scale down to 300mhz, which should be very cool.
I installed this very basic and simple temperature monitor to put the temp in the status bar and so far I've never seen it go above 35c
http://www.appbrain.com/app/tempmonitor-lite/org.alldroid.apps.tempmonitorlite
It polls every 15 seconds which is all I need and no permissions.
Apparently the Defy only has a battery temp sensor and not a CPU temp sensor?
I'd like a better monitor with vibration alarm and a log but I am tired of all the overbearing apps with ads and "buy the pro version" nonsense and such.
Hi!
I used to have a CM7 with a chinese (really-really cheap) 1800mAh battery after the stock ROM (2.2 CEE); and I haven't experinced things like that. Mostly I measure the temp. with a widget (Elixir 2) and it was always below 35°C if I'm not wrong.
These 3 wakelocks are always about even with each other at anywhere from 50% to 90% of the time "since last unplugged". Anyone know what these are, if they're normal, or how to get rid of them?
turn off latitude helps a lot
but they are Android 4.2 bug, i think Google will fix them
Probably normal if you were on the phone or doing lots of texting.
Sent from my Nexus 4 using xda premium
Hmm they're actually increasing almost the whole time the phone is idle with screen off though. Latitude is off as well. I'll try a clean ROM flash after factory reset and report back. Thanks guys.
Sent from my Nexus 4 using Tapatalk 2
whittikins said:
Hmm they're actually increasing almost the whole time the phone is idle with screen off though. Latitude is off as well. I'll try a clean ROM flash after factory reset and report back. Thanks guys.
Sent from my Nexus 4 using Tapatalk 2
Click to expand...
Click to collapse
Unfortunately these are still present (and high) after a full wipe and flash of the latest AOKP. Anyone else see these at the top of your wakelock list?
Not on MINCO
I am having this issue too, I believe it might be an AOKP problem:
http://forum.xda-developers.com/showthread.php?p=37451238#post37451238
Well, I searched for hours, and hours for this wakelock too, and I think I finally found what it is, basically this wakelock is caused by the signal processor going berserk and waking up your phone constantly, most of the time this is caused by something disturbing it, and in that you have to think about something that could change or capture a signal in really the root and not through the official Android ways, like Viper4Android, it changes the audio kernel, this could disturb it, or automatic call recorder, this one picks out the voice signal, and this applies to almost all the sensors and signal processors
Hey guys,
I have an S3 Neo since 8 months, it was all good, but now i started to face a problem, a big one.
Whenever i charge my phone and i use it, for all.the day the battery is good, but when the percentage reaches around (38%-43%) the phone's screen starts doing some strange waves (flickering) then it turns off, and it won't boot up unless i plug it to the charger and it indicates that the battery is 0% (fully discharged). I tried to replace battery 2 times, but it's always the same, i tried that "Quick Start" Battery gauge chip reset. But no result.
So.... anyone knows what I'm really facing?
Hi i had the same problem... U must buy new battery your battery is dead.
I did bought two batteries, problem persists !
An example of what I'm facing
This is an example, now I'm trying to calibrate the phone by only charging to 50%
My screen also flickers, but only when it's below 10 percent. Maybe it's a kernel issue. Is see you have a custom rom, have you tried switching kernels?
GT-I9301I rom: cm 12.1 (nikola)
Use an app called Battery Calibration to calibrate your battery. You can download it throught Play Store.
But tell us: What ROM are you using? Whar kernel?
Sent from my S3 Neo+ (GT-I9301I) running Stock ROM with @sev3n1985 Kernel
I tried many roms and kernels and all of them have the same issue with my device. I have already tried battery calibration, not working :/ . Now i found that it won't happen if i don't charge my phone more than 60%. And battery is holding more (2h30min sot with 45%) so I'm gonna grab a kmesg and attach here.
Yeah I had that problem to when I was in motion rom but it was fixed when I restored it to stock can any one tell's us why????
moh842 said:
Yeah I had that problem to when I was in motion rom but it was fixed when I restored it to stock can any one tell's us why????
Click to expand...
Click to collapse
Its a bug in motion rom. Try changing lockscreen effects to none. That ll help u in terms of flickering
Sent from my SM-G800H using XDA-Developers mobile app
ziad311 said:
Hey guys,
I have an S3 Neo since 8 months, it was all good, but now i started to face a problem, a big one.
Whenever i charge my phone and i use it, for all.the day the battery is good, but when the percentage reaches around (38%-43%) the phone's screen starts doing some strange waves (flickering) then it turns off, and it won't boot up unless i plug it to the charger and it indicates that the battery is 0% (fully discharged). I tried to replace battery 2 times, but it's always the same, i tried that "Quick Start" Battery gauge chip reset. But no result.
So.... anyone knows what I'm really facing?
Click to expand...
Click to collapse
I had the same problem 6 months ago! I decided to buy an original S3 battery (the difference is that it's made in Korea, NOT in China) and now I always have 4h+ screen on time with the stock rom and s3ven kernel!
Sent from my s3ve3g using XDA Labs