Found a pretty nifty bug on the evo... not sure if it is software or hardware.
* turn wifi on
* plug evo into computer USB port
* start watching streaming video (or any other CPU intensive task)
* eventually the battery will be at 0 and the thing will shut off with a blinking orange light.
The bug:
* the phone never warns you. Because it is "charging" the phone never gives you the low battery warning (quack,quack, orange warning light, etc).
* If you are connected to a power source that isn't sufficient to charge and power a fully loaded phone, it just dies without warning.
* I have no idea what the solution for this would be, it kind of is a catch 22.
Most devices have the same issue and I've found many that don't give the warning either.
Remember, USB through computer or whatnot maxes at 500ma, normal usage of the cpu/phone, etc draws more than that. The AC charger was 1a and should be sufficient.
Does it suck they didn't warn you? Yeah, but now you know and probably won't let it happen again. I suspect you can make your own warning system using something like Locale or Tasker and have a SETCPU profile to throttle down your CPU to save power. That's the nice thing about android, it's open enough that you can find a BETTER way of doing things than relying on the devs of the phone.
Related
Hi,
I have an XDA-Orbit which is automatically turning itself on every couple of minutes, which is obviously draining my battery and effectively rendering my device useless.
I have "BatteryStatus" installed which, amongst other things, displays an icon on the today screen that tells you the current power drain on the device in milliAmps. If the device is plugged into the mains, this software tells you the positive current that is being added to the device.
I am almost certain that this program is pointing the the problem I have, since whenever the screen lights up (or when the device turns itself on fully), BatteryStatus is reporting that the consumption has changed from being a negative (drain) on the device to a positive input of current. The icon also changes to a plug, implying that it's been connected to the mains and power is being supplied. For some unknown reason, the device seems to think that it's connected to the mains and is having a positive amount of power being put into it when there's nothing connected to the device.
Has anyone else come across this problem? Can anyone suggest how I might fix it?
The device is NOT plugged into the mains! And there's no power actually going into it.
Many Thanks,
Rob
Quite a few smartphones out there support hibernate. HTC is amongst the manufacturers that makes it possible to completely shutdown the phone and write all memory to a file on the nand which is put back in memory when the phone is turned back on. This way it only takes a few seconds to go from off to fully functioning, practically the same thing computers can do for years. Now I wonder if this could be done with the Defy (and possibly any other Android phone for that matter). I don't know how HTC does it but I guess it's pure software as in not an integrated Android feature. And if they can do it I'm sure some of the XDA guys can do it. Or is that wishful thinking??
Well if you want to save battery, then there are certain task killers which actually closes all the tasks which are not in use but running (excluding ignore list) and this way whenever the screen is turned off, it closes those tasks, that improves the battery. If that is what you meant?
I found this on google:
http://www.androidzoom.com/android_applications/tools/hibernate_ctp.html
No what I mean is in the event you have to shut down the phone entirely that all content in the RAM gets written to nand (or maybe sd). This way when it boots again it simply restores its RAM within seconds, effectively cutting boot time to only a few seconds instead of 40. Compare this with Windows' hibernate function for the pc.
Turns out HTC calls it Fast Boot. It's not a real hibernation function because if you put the phone to sleep with it and remove/replace the battery it would perform a normal cold boot. So it's more of a very low power sleep mode, guess more like a computer's S3 sleepstate where only the RAM stays powered while all the rest (cpu, chipset, video, audio etc) is turned off.
Sounds like a very interesting option, very curious if this would be possible on a defy.
This would be a nice feature.
Sent from my MB525 using XDA App
Totally pointless if you ask me. Just enable airplane mode if you want epic battery life?
sarge78 said:
Totally pointless if you ask me. Just enable airplane mode if you want epic battery life?
Click to expand...
Click to collapse
Or turn it all the way off and save even more power.
There are also plenty of 'smarter' ways to safe power, such as scheduling the handset to automatically disabling 3G overnight etc, which don't even require you to switch the handset off.
Airplane mode still leaves the cpu switched on. The purpose of that mode is to be still able to use the device without a working connection.
Say you are away from home and didn't bring the charger. Now the battery is almost dead. Then a very low power sleep mode would come in handy because it boots in only a few seconds and after a few more seconds you can turn it 'off' again. Fast and snappy, hardly using any power. And this is XDA so another extremely valid reason to have it is simply because we can. For pc's it's everyday technology so why not make it available on our pocket sized super computers?
I always disable hibernate in my PC.
Actually me too but I do use the sleep mode quite often with my laptop. Works great when you move your laptop a lot to other places but don't want long boot times. It could actually survive days in this mode on a full battery.
Hi everyone!
OK, I have pretty much isolated issues with battery since I found faulty wiring with Samsung USB cables that come with their chargers.
Not everyone will find issues with the USB cable, but the way it is made will be an issue eventually.
One, the cable is very thin and flexible, so many will stretch over a near by wall outlet to use the charger while using the tablet.
Eventually the wire at the connecter on the tablet end gets bent up to 90 degrees, Eventually causing two issues. One intermittent charging. The other a short. I have had both happen since Owning it in November 2013.I almost had a fire, as the plug had a meltdown. Super dangerous!
Now while messing with trimming down apps and memory, I found a few apps that I use have the ability of keeping the CPU and GPU at their highest frequency. They call it boost mode. Even if you have it disabled, toggling it on and off may clear out the setting if you notice your tablet's battery depleting fairly fast and heating up on the left side.
Now for a odd issue with Google apps... I removed the Google Play Music Player, and disabled DRM/Downloads and made a few adjustments to Media Server. What happens is Music Player will cause playback automatically and Media Server will loop into high CPU usage even during reboot. DRM and Media server can cause this condition quite easily. So far Google is not working on a fix for JellyBean. Only KitKat has this fix, all other previous Androids,Gingerbread for example, do not have the issue. Corrupt files or files with _ or strange symbols will cause this loop until the tablet is turned off completely and restarted.
.
gooberdude said:
Hi everyone!
OK, I have pretty much isolated issues with battery since I found faulty wiring with Samsung USB cables that come with their chargers.
Not everyone will find issues with the USB cable, but the way it is made will be an issue eventually.
One, the cable is very thin and flexible, so many will stretch over a near by wall outlet to use the charger while using the tablet.
Eventually the wire at the connecter on the tablet end gets bent up to 90 degrees, Eventually causing two issues. One intermittent charging. The other a short. I have had both happen since Owning it in November 2013.I almost had a fire, as the plug had a meltdown. Super dangerous!
Now while messing with trimming down apps and memory, I found a few apps that I use have the ability of keeping the CPU and GPU at their highest frequency. They call it boost mode. Even if you have it disabled, toggling it on and off may clear out the setting if you notice your tablet's battery depleting fairly fast and heating up on the left side.
Now for a odd issue with Google apps... I removed the Google Play Music Player, and disabled DRM/Downloads and made a few adjustments to Media Server. What happens is Music Player will cause playback automatically and Media Server will loop into high CPU usage even during reboot. DRM and Media server can cause this condition quite easily. So far Google is not working on a fix for JellyBean. Only KitKat has this fix, all other previous Androids,Gingerbread for example, do not have the issue. Corrupt files or files with _ or strange symbols will cause this loop until the tablet is turned off completely and restarted.
Click to expand...
Click to collapse
bro I will suggest you to take your note 8 to near by samsung service centre....
rabichowdhary said:
bro I will suggest you to take your note 8 to near by samsung service centre....
Click to expand...
Click to collapse
why??? I have no issues.
Oh here is more about draining batterys with 4.2.2
Many who don't have battery drain issues are running 4.2.1 or earlier.
Google Music Player after December 2013 will drain the battery on 4.2.2 ROMs.
Found Samsung OEM USB / Charging cables too weak and flimsy. Gone to Blackberry / Sony / Ericson cables, as they are the best in the business for OEM cables. Not only they are robust they have built-in passive filtering for high throughput connectivity. Also they allow for a good quality USB extension cable to be used with fast charging. I do not recommend any combined lengths beyond 1.8 Meters, or 5 Feet.
Use nomedia in folders not containing media on the SD card. If you are not sure about how to properly use nomedia, redirect your Internet browsers cache to SD, and copy the file from the cache directory anywhere that is needed.
Remove or edit any '_' in a media file's name, as media will run constantly when detecting an underscore.
Watch the data and battery tools in the android system, to assist in diagnoses of rogue apps running.
Beware of Xposed modules... I ran across a few that their updates caused slow booting and errors. Watch your Xposed log after a few reboots with any Xposed updates.
I'll repeat myself from the original entry on top of this thread... Watch for any module or app that has boost/benchmark capabilities. Disable it by all means. I have tweaked with OC tools with custom ROMs and found very little benefit. For those who scoff, here are my current battery and performance info for daily activities.
Charge rate while on AC and active: 20% every 45 minutes.
Sleep with Wifi on during a 12 hour period, total drain: 3%
Drain per hour while being active: 10%
Drain per hour Miracasting Netflix to tv: 12%
Netflix operation no lag or sync issues with high resolution. Note: this is with small tweaks with a stock ROM.
Even with performance tweaks for audio and CPU throughput. No overclocking or under volting was performed. I probably would get better battery drain performance by removing Viper4AndroidFX and keeping with OEM audio driver.
Here are my tweaks.
Xposed App Settings... 220dpi 1000x1600 even though stock parameters default to 320dpi, the system defaults to 180dpi and needs overridden.
360 security with active Android security patch update (Works when you do a manual full scan) and built-in app performance & cleanup tool.
Greenify & Xposed donation with Greenify extras.
Xposed boot manager.
Disabled Google Music Player.
Viper4androidFX set to Medium efficiency with Neon driver.
Trickster Mod with settings for 1024 cache, Zbuffer, and Ondemand set.
Since Lenovo P2 has an incredible battery life you rarely have to make full charges. I've been searching a long time for a method to set a charging limit, for instance at 80%, to preserve the battery health. It is possible to use the BCL app, Tasker as well as the Magisk Charging Switch module.
The path of the battery files responsible for the charging is /sys/class/power_supply/battery where you'll find two interesting files, battery_charging_enabled and charging_enabled.
There's only one problem; as soon as the screen turns off any limit set by you will be ignored. Now, there has to be a way to force the charging to stop while the phone is in idle state. Any ideas? I've already tried the obvious solution to whitelist BCL, Tasker respectively Magisk in the battery optimization settings, but it didn't work.
RR-O-v6.2.1-20190130-kuntao-Unofficial + battery charge limiter
RR-O-v6.2.1-20190130-kuntao-Unofficial + magisk + Battery Charge Limit works for me
I guess your limiters go to sleep when the screen goes off. Try to force that the screen stays on. Try to exclude them in the battery saving options. If you try the app Battery Charge Limit than it is working for me with a normal charger but not while chargeing through a PC.
Hello,
I was looking for a way to use Battery charg limit on my pixel 6 Pro, using a pixel stand 2. (because I'm using it a lot)
So when A13 came out, I rooted the phone, and started my research.
I found a message in a thread that specified a way to do what I want.
[APP][ROOT][4.0+]Battery Charge Limit v1.1.1
jazic said:
I finally found the ability to 'pause' charging on the Pixel 5, 6 and maybe 6 Pro?
This work only with wireless charging but I'm sure the /dc/ folder for wired.
I use tasker to control the file:
/sys/class/power_supply/wireless/current_max
I did figure out how to have it always have the file set to rw with the profile itself by using "run shell" and enabling root:
chmod 0777 /sys/class/power_supply/wireless/current_max
Obviously you can set up a profile to control it with tasker but personally I have mine set to start charging full speed when the battery is 0 to 65% then start trickle charging half speed until it reaches 72%. Once it reaches 72% you can set the current level really low and it'll basically keep the charger cycling on and off at a very low input voltage so the battery will hang at whatever you set it at without dropping then charging back up all the time which imo is better than cycling power off at a certain level then charging back up.
I'm still experimenting with current levels but if you set it to higher than your charger can handle then it will just simply charge at max speed of your charger.
For trickle half speed charge I use: "500000" (500mA?)
For full speed charging I use: "2200000" (2200mA?)
For Battery Charge Limit I'm sure you can set the file to:
/sys/class/power_supply/wireless/current_max
Enable: 5000000
Disable: 1000
You will need to set the file as writeable maybe?
Any questions hit me up. Maybe it's another source to look for other phones.
Click to expand...
Click to collapse
I was thinking it all worked but in fact not...
For me now, wireless charging is very buggy.
Using Amper, i'm often in "not charging" or I'm charging at 4V and max 600mA.
I don't know if it's my fault or if it's related to the bug with the Pixel 6 wireless charging issue ?
Also, can someone give me the default value of this file "/sys/class/power_supply/wireless/current_max" mine is now set at 250000, to double check.
Thank you !
I found a solution on reddit !
Going to App > See all apps + show system apps > Search "pixel stand" > clear cache + clear storage
This fixed my issue so I guess it was A13 and not BCL.
Hops it cals help someone.
That's awesome! Thanks for letting us know.