Hi, wondering if anyone can help?
I need a battery monitor program, but I need something with the following features.
1. It must run in the background, so that the device can be used as normal
2. It must record battery usage over time, and must store the data to a text file for later analysis and graphing
3. Ideally, it would also give me matching data for the battery temperature
4. It needs to run on a VGA device
5. It must run under Windows Mobile 6.1 Professional
Anyone know of a program that can do all these? HomeScreenUI is great, but doesn't log the battery levels, and can't get the battery temperature of the device I'm using. abcTaskMan graphs battery use, but doesn't run in the background, and doesn't log the data to a file either (or get the temperature).
Maybe Pocket Battery Analyzer may suit your needs but non free.
(http://www.wizcode.com/products/view/pocket_battery_analyzer)
Regards,
Thomas
Related
All
my xdaII is suffering lethargic performance after upgrading the ROM to latest version from o2! I reloaded all of my applications and now the device is really slow to switch between apps. I have attached acouple of screen shots detailing the device/memory status. Additionally my active synch will not now synchronise files and contacts data, it just keeps on rolling around saying 0 of ?? files synched. I accept it is probably something I've done but I dont know what...
If anybody has any ideas on how to cure this I'd be very grateful. Thanks
Pete
I suspect the performance problem on the XDA II is because it's reaching the process limit - 32. PPC Phone Edition uses more processes than the standard version. There's only a handful of processes available after all the standard stuff is loaded. Basically you should load as little at startup which means editing the contents of the Windows\StartUp directory. Make a backup of this directory before you start deleting things. Below is the standard shortcuts I have left in the directory:
ChgDfLnk
FSK Loader
IA_Caller_ID
This also means you should use as little utilities that run in the background as possible. I don't know if today plug-ins use up an extra process. I have heard that it is possible to write a program to run as a service but most developers don't bother - I don't know enough about PPC development to know whether this is true.
Also Activesync uses 3 processes, maybe it can't get enough free processes to run properly.
I've been searching for software that would allow me to watch my PC status in real time on my phone, I mean realtime CPU, GPU Temp, usage, RAM usage, and such thing for android device, but unfortunately could find anything, maybe you know anything better, please suggest, thanks you beforehand.
FYI, I don't have a Nexus 5, but I've been following the Android L news for the past few weeks and have yet to see any reports on the battery historian developer tool. I'm really curious to see detailed battery usage reports for apps that are known to cause frequent wakeups from deep sleep (e.g. facebook). From what I can tell, you need 3 things to use this tool:
1.) adb
2.) The actual Python script: https://raw.githubusercontent.com/google/battery-historian/master/historian.py (just right-click and "Save as" to the directory from which you run 'adb')
3.) Also need to install Python 2.7 on your system (for Window users): https://www.python.org/download/
4.) Obviously, a browser to view the generated html.
There are some comments at the beginning of historian.py script that describe how to generate the required data with adb. Note for Windows users: open up the file in Wordpad, not Notepad.
Also for Windows users: assuming you have installed Python 2.7 in c:\Python27, use the following command line to run the script:
c:\Python27\python.exe historian.py [OPTIONS] [FILE]
Also note that this tool is NOT part of the built-in Android battery settings/stats and there is no native Android UI for it. It is meant to be a developer tool. However, this doesn't mean that users with access to 'adb' can't play with it...
I manage to get this work...even i have no idea about development...
First it need python 2.7 not 3.4
After that you have to mix some commands from the OT and the info inside the .py file...so what i do
After installing python 2.7 i use the command to get a bugreport from the phone...
Code:
adb bugreport > bugreport.txt
then i use the OT command to make the bugreport to an html file with a bit of change
Code:
c:\Python27\python.exe historian.py -a bugreport.txt > battery.html
Thats it...now..i don't know if it has the correct data...im just achived the html look of what we saw on I/O
I think first you need to use this command
Code:
adb shell dumpsys batterystats --enable full-wake-history
To let the phone start dumping stats...and then after some use time to gather the bugreport from your phone....anyone with better knowlage im sure it will figure it out!!!
On the attachment i use the command
Code:
adb shell dumpsys batterystats --reset
to reset my values cause im not using my L rom...
Oh btw this will work only on L....
I can't use "--enable" option.
I can't use this command.
Code:
adb shell dumpsys batterystats --enable full-wake-history
Please tell me how to use "--enable" option.
My phone is Android4.4.2.
("--enable" option is Android "L" only ??)
k-matoo777 said:
I can't use this command.
Code:
adb shell dumpsys batterystats --enable full-wake-history
Please tell me how to use "--enable" option.
My phone is Android4.4.2.
("--enable" option is Android "L" only ??)
Click to expand...
Click to collapse
This is only for Android L.
thomase00 said:
This is only for Android L.
Click to expand...
Click to collapse
How is it that we are a month after Google I/O, and no one with Android L has played with this yet?
IMHO, this is one of the most important new features.
Yep, i think this is the most recent problems the two guys from project Volta have. They have to be rely on the help of the programmers which develop the software.
Daimonion1980 said:
Yep, i think this is the most recent problems the two guys from project Volta have. They have to be rely on the help of the programmers which develop the software.
Click to expand...
Click to collapse
They have to rely on Developer to use JobScheduler API but not for finding you bad apps that are killing the battery. And to that effect, those guys are doing a terrible job with a botched tool.
It's amazing how there is NOTHING on the Internet about the Battery Historian tool. It's like no one has used it. In my case, I can't get the command to builds the html file from the bugreport. It keeps giving me a invalid html error.
Yep, I did ask chamonix from BBS if he can use the generated stats and he will take a look into it. I hope he will do it in the near future.
Using battery historian
After playing with this for a while I've figured out how to use the basic function (this is part of project volta, so it will only work on Android 5.0+)
enable full wake history and then output your batterystats to a text file
./adb shell dumpsys batterystats --enable full-wake-history
./adb shell dumpsys batterystats > batterystats.txt
navigate to wherever you placed historian.py and output the data to a html file (you need python 2.7)
./historian.py [location of batterystats.txt] > batterystats.html
open the batterystats.html file and you're done! For basic use at least. I'm still figuring out the rest myself.
So after having problems on lollipop with mobile radio active bug (https://code.google.com/p/android/i...id&colspec=ID+Type+Status+Owner+Summary+Stars)
i managed to get an dump from battery historian. But at the moment a see not the culprit in my log. The only thing i see is that my device although it was not heavily used this morning has a tons of wakelocks.... and an running par between 10:45 and 10:55 where i don't know it's coming from......
Have a look at it:
http://picture-diamonds.de/private/Thomas/Dumpsys.html
Is anyone able to interpret this chart?
I finally got 5.1 on my Verizon Moto X (1st gen). One of the first things I did was collect battery stats and run Battery Historian 2.0. The following guide was very helpful in getting this set up on Windows 7:
http://ph0b.com/battery-historian-2-0-windows/
Anyway, it turns out that while sitting untouched on my desk at work, the phone pretty consistently wakes up about once per minute (only for a second or 2), with the partial wakelock held by GOOGLE_SERVICES. Most of the time, it seems to be related to location reporting. This doesn't sound like a lot, but I think there is a relatively big cost associated with powering the up and down.
Other than location, the ONLY reason I can think of for waking up the phone periodically is for TCP keep-alive (to keep GCM push notifications working), but once per minute seems kind of excessive even for that. My theory is that there is an app using the Google Play Services Geofencing API, and I just happen to be parked near a geofence boundary. According to my understanding, the Google geofencing service adjusts location polling frequency according to your distance from a geofence. If I am correct, the problem is that it is not smart enough to understand that you are stationary and therefore avoid excessive polling.
I'll try to collect more stats from different locations.
I'm sure this ground has been tread before...
thomase00 said:
I finally got 5.1 on my Verizon Moto X (1st gen). One of the first things I did was collect battery stats and run Battery Historian 2.0. The following guide was very helpful in getting this set up on Windows 7:
http://ph0b.com/battery-historian-2-0-windows/
Anyway, it turns out that while sitting untouched on my desk at work, the phone pretty consistently wakes up about once per minute (only for a second or 2), with the partial wakelock held by GOOGLE_SERVICES. Most of the time, it seems to be related to location reporting. This doesn't sound like a lot, but I think there is a relatively big cost associated with powering the up and down.
Other than location, the ONLY reason I can think of for waking up the phone periodically is for TCP keep-alive (to keep GCM push notifications working), but once per minute seems kind of excessive even for that. My theory is that there is an app using the Google Play Services Geofencing API, and I just happen to be parked near a geofence boundary. According to my understanding, the Google geofencing service adjusts location polling frequency according to your distance from a geofence. If I am correct, the problem is that it is not smart enough to understand that you are stationary and therefore avoid excessive polling.
I'll try to collect more stats from different locations.
I'm sure this ground has been tread before...
Click to expand...
Click to collapse
Thanks for sharing ph0b's work here with Battery Historian.
Is it possible to create a user-facing setting to manually enter the actual capacity of the battery in use? Perhaps under either settings->battery or settings->performance->battery? I've read through this and I think I have a decent grasp of all the moving parts behind the graph the system prints in settings->battery.
For my part, I've always used a larger-than-stock battery, and furthermore I use my batteries long enough that they start to show a noticeable dip in effective capacity. I'm assuming that if I could set the value manually (in the later case, I'm aware that there are apps that will try to calculate the effective capacity of an aged battery), my battery statistics would be a bit more accurate, especially the feature in lollipop that attempts to estimate remaining battery life. I'm aware that I could accomplish this be decompiling the framework and modifying the value in power_profile.xml, but that seems tedious to do if I'm flashing nightlies somewhat regularly.
JoeSyr said:
Is it possible to create a user-facing setting to manually enter the actual capacity of the battery in use? Perhaps under either settings->battery or settings->performance->battery? I've read through this and I think I have a decent grasp of all the moving parts behind the graph the system prints in settings->battery.
For my part, I've always used a larger-than-stock battery, and furthermore I use my batteries long enough that they start to show a noticeable dip in effective capacity. I'm assuming that if I could set the value manually (in the later case, I'm aware that there are apps that will try to calculate the effective capacity of an aged battery), my battery statistics would be a bit more accurate, especially the feature in lollipop that attempts to estimate remaining battery life. I'm aware that I could accomplish this be decompiling the framework and modifying the value in power_profile.xml, but that seems tedious to do if I'm flashing nightlies somewhat regularly.
Click to expand...
Click to collapse
Last time I checked, the power_profile number was not actually USED anywhere by anything. (This might have changed with Lollipop though, I need to check that... It could be, or it may be simply based on how fast the SoC percentage changes.)
All of the statistics are measured based on:
1) State of Charge percentages, which are always handled by the fuel gauge chipset itself. If these are inaccurate, something is wrong with your device's kernel or hardware.
2) Estimation of what certain components within the system consume when they're in a given state. e.g. the various components OTHER than total capacity in power_profile.xml
Thanks for the insight. I also just picked through a few battery tester apps to try to gauge where my batteries are at, and one of them asked me if I wanted to use the system value (I'm assuming it read this from power_profile.xml, it was the incorrect stock value), or the actual value as reported by the battery(which was accurate).
So I guess the information is there all the same if anything wants to use it (assuming that the author knew what to use).
JoeSyr said:
Thanks for the insight. I also just picked through a few battery tester apps to try to gauge where my batteries are at, and one of them asked me if I wanted to use the system value (I'm assuming it read this from power_profile.xml, it was the incorrect stock value), or the actual value as reported by the battery(which was accurate).
So I guess the information is there all the same if anything wants to use it (assuming that the author knew what to use).
Click to expand...
Click to collapse
Hmm, so maybe the capacity in power_profile is used by some apps but not anything in the system itself...
Entropy512 said:
Hmm, so maybe the capacity in power_profile is used by some apps but not anything in the system itself...
Click to expand...
Click to collapse
Err, actually I 'dun goofed when I was tinkering around with that app. For the record, it's Battery Widget Monitor and it only seems to present those options during the first-run wizard(after that you can set it manually in a different dialogue). I started thinking I had a 2100 mAh battery in the phone (which was true), but when I saw those options I assumed that one of them was correct, so I basically convinced myself that I had my 1850 in (I peaked but the label faces inward, and I have two batteries that are the same color...ugh).
Long story short, what the app actually offers is "from battery files" and "from battery profile". I think the latter is being read from battery_profile.xml, because I decompiled my framework-res.apk and it matches (and the value is correct for stock toro battery, 1850). I think the first option must be that app's own database, because it's using the maguro value of 1750, and it seems most likely that the app just can't differentiate any finer than "Galaxy Nexus".
So I guess that's actually sort of back to square one; the app does rely on what's in power_profile.xml (or manual input), but that doesn't really say anything about what the system does or doesn't use it for.
Hi,
i'm looking for a fast way to analyse the apps installed on some phones in my company. I need to get an overview of all apps and some properties. I would like to list the permissions, check if they are allowed to run on mobile data and/or Wifi, the space the app is consuming, maybe battery usage... We don't have any mobile management.
I need all this for analysis, so preferably in a Csv export, or something similar. To avoid to bother the owner too much, i want to reduce the time I need the phone to do the job.
My only idea until now is to take screenshots of all needed settings. That's of course not very comfortable.
Any ideas?
Thanks