Just finished up setting up Small EUI 5.9 by aurel V5. Amazing Rom BTW. Not able to post in dev thread so I thought I should post here. After setting up all my apps and tweaks, I always use AccuBattery Pro to check estimated battery life to check that all the battery tweaks I have installed works(greenify etc.). I noticed that the screen off time was estimated using significantly more power than screen on and the device had become very warm(nearly hot). I nailed it down to the finger print sensor. Its disabled now and the screen off time is back to normal. Changes to the finger print scanner in the ROM made it faster but this battery drain began to occur. Hopefully this will be fixed in an OTA. Anyone else experiencing this?
edit: disabling and re-enabling finger print security has fixed it for now.
Related
I'm starting to see a correlation between absolute crap-for-crap batter life and having the ambient light detector enabled. I'll do a test tomorrow, but I'm pretty sure if I just left my screen on full brightness all day, that I wouldn't get as bad of battery life as I do with the ambient light detector turned on.
Is there a problem with the fascinate's polling period? or possibly how much power is being sent TO the sensor? This might explain the problems on hacked roms where people are noticing a buzzing/hissing noise coming from the phone right around the area of the ambient light sensor when in the middle of a call (and the screen is on).
Has anybody seen where in the code the ambient light sensor is handled? (is it in the kernel, or somewhere in the drivers?).
*EDIT*
Thanks for moving my post. I was pretty annoyed with myself for posting in the wrong section.
*edit* Now that the thread has been moved, This post could probably be deleted.
--------------
Well, since nobody has moved this to the other forum yet and it's received a few views, Has anybody else noticed this before?
My personal experience had been full brightness ate battery fast and low brightness was a combination of hard to read and similar drain to auto. Then again my phone has never hissed at me except for godawful noises using skype wifi sometimes, and I have never messed with brightness under froyo.
My only observation with froyo roms is that "stock" eb01 was awful but superclean and AOSP were pretty good, particularly under EB+ kernels.
Also, I lose more battery than I would like to from signal loss overnight, but turning off 3G seems to help with that.
Swyped grumpily from my advertised as "can be upgraded to Android 2.2" device.
i noticed that the automatic brightness setting is absolutely terrible at choosing the correct brightness.
the froyo roms added the ability to hold down on the status bar and move left and right to adjust the brightness, so i just use this to adjust it on the fly when necessary.
this doesn't really answer your question, but i figured i'd add my 2 cents
lane32x said:
This might explain the problems on hacked roms where people are noticing a buzzing/hissing noise coming from the phone right around the area of the ambient light sensor when in the middle of a call (and the screen is on).
Click to expand...
Click to collapse
The noise comes from having the key backlights on during a call.
If you are referring to the softkeys, there were some assumptions that this was the case, but I have tested this out and have heard the noise even when those lights were turned off.
Also, I ran my phone at about half brightness today all day. I've had it off the charger for 15 hours, made 3 hours worth of phone calls, and it's still at 41% battery life.
2 days ago when I just had my phone in the pocket, not doing anything and leaving the screen off (with auto brightness enabled) my battery was dropping significantly after only 6 hours and no phone calls or Internet usage.
I have to say that the update did improve the performance of the device but I have two problems.
When I turn on the screen I see one ripple effect on the lock screen like if I touched it in the middle bottom half part screen.
Did some one has this bug?
About the second bug I'm still not sure 100%, It's battery life.
The battery holds much longer in sleep mode (screen turned off) but while in use it drains more battery. I know that its suppose to be like this but in my case it changed since I upgraded. (I hope u'll understand what I mean).
Hi All,
I'm from Germany, new to the forum and have straight a question about my new Samsung Galaxy Alpha.
Since a month now I'm using the Alpha.
I'm quiet happy with the overall performance and handling and really love that phone.
Of course I rooted the Alpha to remove bloat ware and to tweak the autorun behavior of some apps.
When the phone is sitting there connected to WiFi or/and GSM with the screen off waiting for calls, text and mails coming in, it consumes roughly 1% of the battery per hour. What IMHO is a good performance, compared to the SGS2 I owned before.
Anyway, when checking the details of battery usage with 3C Toolbox Pro I figured out, that
MPL Significant Motion in the Google Play Service eats appr. 40% of my battery capacity in standby.
I'm wondering what that service/process is doing (and who started it) as there is no reason for the phone to detect motion in this state. Or I'm totally wrong and MPL Significant Motion is something different???
Even Google couldn't help in this specific case.
The only motion detection I can think off are the Automatic screen orientation and the Flip over to mute function which I have activated.
To narrow down the options I switched these off, but this doesn't change anything regarding the power consumption. These detections should only be active just when the screen is on or in case of an incoming call anyway.
Could somebody out there check if it is a normal behavior to have that MPL Significant Motion thing running more or less constantly?
And does somebody know what this service/process is doing and how to circumvent an auto start?
The 2 Screenshots attached (Battery01/02) showing the usage of MPL Significant Motion (2% out of 5% are used by this process).
The other Screenshots (Apps01-05) showing all the apps and services running on the phone currently.
Thanx for your help in advance!
So. I too have been afflicted with the Note 4 crazy CPU issue, and would LOOOOOVE a fix. I'm using an old phone at the moment because the Note runs so hot and drains so fast I'm worried it'll become damaged.
Steps so far:
* Started with V9.6.3.0.NCFMIFD (MIUI9)
* Woke up to phone running super hot (It charges overnight), the day before all had been well. Have to assume some system app or other update happened overnight.
* Tried to charge it, but it was running flat fast.
* Let it discharge to 0%, and then it refused to charge all day, only flashing red LED
* Left it unplugged all night and next morning charged it, after a few minutes of still showing the flashing red led, started charging normally, but hot still
* Tried downgrading to V9.6.2.0.NCFMIFD
* Same issue
* Tried upgrading to 8.10.18 (MIUI10) Same issue (MIUI 10 is pretty though )
* Have tried factory resetting (via recovery mode wipe)
* Have tried within MIUI10 uninstalling all google apps it allows me to, and downgrading all I can
It's just burning up, running hot, and not getting any better. When is Xiaomi going to fix this issue that, based on how many threads there are here, and on MIUI forums, and on reddit, is widespread?
Hi spoco2,
Just back from a local store with the same issue in my Xiaomi note 4X and it seems like a known problem due to google duo from his words.
The solution that he made - remove last update of google duo , disable auto update from playstore for specific app only.
Please let me know if that helps you , i'll trt to check if that works and update.
Best,
Roee
Yeah. I have tried that, and it does seem to help a bunch of people, but not all of us it seems.
?
It's utterly flat at the moment. But even after a complete factory reset and return back to V9.6.3.0.NCFMIFD (MIUI9) it's still doing it.
Downloading https://play.google.com/store/apps/details?id=com.dp.sysmonitor.app and running it showed that all eight cores had their frequency up at 1.69Ghz, all the time. One of the cores was sitting at almost 100% usage for the whole time, while the others moved around a lot, but still had their frequencies right up high.
As it got to almost flat MIUI said I should turn on battery saver. I did that, and I'm not sure if that did it, but then four of the cores were shown as 'offline'. But there was still one core with high cpu usage, and all remaining cores still had their frequencies high.
have you tried flashing a custom ROM?
You might try flashing a custom kernel. I use storm guard kernel. Works great. Also you might try turning off MIUI optimization in dev options. It's at the bottom of the list.
Hey guys, I am using Accubattery to monitor my battery performance and I noticed that after the last software update the battery performance dropped significantly. On the previous version, my stats were roughly 9%/h screen on and 1,5%/h screen off. After the update, the screen on discharge jumped to 22,9%/h. I used to charge my phone once in 3 days, now I have to charge it every day. Also, I noticed that the phone was significantly warm while reading an ebook and drained the battery really fast.
Something is really off. Any idea how to report back to Realme?
Seriously, no one has a similar issue? I tried pretty much everything except for a full factory reset. I tried to turn off GPS, LTE, Wifi, and Bluetooth with negligible improvement in battery consumption. I froze and force shutdown Zepp app and Notify for Amazfit ( I bought a new Amazfit watch recently) - with no visible improvement. What helped - at least a little bit was Battery->Performance mode->No performance improvement. Smart performance mode causes huge battery drain and the phone gets significantly hot during normal usage - web browser, ebook. etc.
I checked if there is a misbehaving app - nope there is not. Checked for malware, just in case - no problem there either.
My theory is they somehow tweaked governor in an update and screwed up.
I get some weird data from AIDA and CPU monitor. It seems that the triple-core cluster is running at full-speed 2,42 GHz all the time. That would explain the battery drain.
Check this screenshot.
The latest update to Android 11 and Realme UI 2.0 seems to fix the high battery consumption, also the tri-core cluster frequencies are finally adjusted normally.
I just hope they didn´t introduce more bugs with the latest release