Here, quick google qoute seeing as your not a fan of google
Batterystats.bin
"This file is used to maintain, across reboots, low-level data about the kinds of operations the device and your apps are doing between battery changes. That is, it is solely used to compute the blame for battery usage shown in the "Battery Use" UI in settings.
That is, it has deeply significant things like "app X held a wake lock for 2 minutes" and "the screen was on at 60% brightness for 10 minutes."
It has no impact on the current battery level shown to you.
It has no impact on your battery life.
Deleting it is not going to do anything to make your more device more fantastic and wonderful... well, unless you have some deep hatred for seeing anything shown in the battery usage UI. And anyway, it is reset every time you unplug from power with a relatively full charge (thus why the battery usage UI data resets at that point), so this would be a much easier way to make it go away."
The file stores NOTHING regarding mAh or similar and doesn't even reference anything "battery" besides the name...
And if u had of read my post you would of seen I stated "rare" regarding data loss
And I am solely stating for the system, not sdcard, and ye I did mean journalism, thanks for the correction and no **** on the "not 100%" thing, but if used correctly, does just fine. and yes apps can freeze the phone, no **** xD but aswell batterystats.bin IN EVERY SENSE is ONLY a reference file nothing more and controls NO variables regarding ANYTHING TO DO WITH THE SYSTEM
If your such a genius you must realize that androids files are mostly ALL loaded read only? Aswell, Droids "multitasking" preloads the files to ram then loads, when put in background, the app exits leaving a page file, storing runtime information that gets called when you launch it again, putting it back to the same state, meaning "changes" on the system besides settings ofc, are done in the ram, before saving to disk, meaning 9/10 times, incorrect shutdowns just "loses" that data, THATS droids standardized data loss.
If a user has the old bin after flashing/upgrading their rom, their an idiot and didn't flash right in the first place,
And yes I'm fully aware of googles policys..
And u SHOULD realize that even though extended batteries are outside the warrenty (how can u expect them to warrenty another companies product?) There is NOTHING inflicting the use and android IN NO WAY PROHIBITS THE USE OR EVEN USES A LINE OF CODE REGARDING THE USE OF A SPECIFIC cell.....
I use 3 cells and never did this AND NEVER HAVE ISSUES
There is NO WAY POSSIBLE said file can effect performance OR battery drain
Also, I do believe fsk is a busybox runtime, by default is not in system, rather /sbin (kernel)
D to run properly, said drive CANNOT BE MOUNTED.
Case in point all you can run it properly on from inside the OS is the sdcard (not its purpose)
And would have little to no effect "fixing" system partitions anywhere besides recovery or through adb. Also, unless your on a flash frenzy and not properly wiping, would have little effect in these either.
What would potentially fix the system from drain is:
Scrubbing the databases
Wiping cache
Disabling system logger
And even remounting nodev would help -
Aswell as the usuall, not leaving wifi on, gps doesnt actually have a huge impact, mines on 24/7
And still get fantastic life (12hrs+)
Saying u got ppl askig you 2 do it aint enough for me, unless your a DEV, get PAYED for it, or your job is related, it really doesnt apply, this IS my line of work (repair/Custom builds on pcs) and even run a side-business doing so.
I have my degree, what do you have?
Im saying straight out your theory has no basis and clearly DOES NOT REFLECT RESEARCH.
If that pisses you off i really dont care, i didnt get as far as i am "playing nice" with kids
Saying enough people verify it, also false, those who do are (same as you) going on hear-say
Nothing more. And more then likely other steps were taken, which again, totally wipes your supposed theory of anything credible. Have a good day
Batterystats.bin
"This file is used to maintain, across reboots, low-level data about the kinds of operations the device and your apps are doing between battery changes. That is, it is solely used to compute the blame for battery usage shown in the "Battery Use" UI in settings.
That is, it has deeply significant things like "app X held a wake lock for 2 minutes" and "the screen was on at 60% brightness for 10 minutes."
It has no impact on the current battery level shown to you.
It has no impact on your battery life.
Deleting it is not going to do anything to make your more device more fantastic and wonderful... well, unless you have some deep hatred for seeing anything shown in the battery usage UI. And anyway, it is reset every time you unplug from power with a relatively full charge (thus why the battery usage UI data resets at that point), so this would be a much easier way to make it go away."
The file stores NOTHING regarding mAh or similar and doesn't even reference anything "battery" besides the name...
And if u had of read my post you would of seen I stated "rare" regarding data loss
And I am solely stating for the system, not sdcard, and ye I did mean journalism, thanks for the correction and no **** on the "not 100%" thing, but if used correctly, does just fine. and yes apps can freeze the phone, no **** xD but aswell batterystats.bin IN EVERY SENSE is ONLY a reference file nothing more and controls NO variables regarding ANYTHING TO DO WITH THE SYSTEM
If your such a genius you must realize that androids files are mostly ALL loaded read only? Aswell, Droids "multitasking" preloads the files to ram then loads, when put in background, the app exits leaving a page file, storing runtime information that gets called when you launch it again, putting it back to the same state, meaning "changes" on the system besides settings ofc, are done in the ram, before saving to disk, meaning 9/10 times, incorrect shutdowns just "loses" that data, THATS droids standardized data loss.
If a user has the old bin after flashing/upgrading their rom, their an idiot and didn't flash right in the first place,
And yes I'm fully aware of googles policys..
And u SHOULD realize that even though extended batteries are outside the warrenty (how can u expect them to warrenty another companies product?) There is NOTHING inflicting the use and android IN NO WAY PROHIBITS THE USE OR EVEN USES A LINE OF CODE REGARDING THE USE OF A SPECIFIC cell.....
I use 3 cells and never did this AND NEVER HAVE ISSUES
There is NO WAY POSSIBLE said file can effect performance OR battery drain
Also, I do believe fsk is a busybox runtime, by default is not in system, rather /sbin (kernel)
D to run properly, said drive CANNOT BE MOUNTED.
Case in point all you can run it properly on from inside the OS is the sdcard (not its purpose)
And would have little to no effect "fixing" system partitions anywhere besides recovery or through adb. Also, unless your on a flash frenzy and not properly wiping, would have little effect in these either.
What would potentially fix the system from drain is:
Scrubbing the databases
Wiping cache
Disabling system logger
And even remounting nodev would help -
Aswell as the usuall, not leaving wifi on, gps doesnt actually have a huge impact, mines on 24/7
And still get fantastic life (12hrs+)
Saying u got ppl askig you 2 do it aint enough for me, unless your a DEV, get PAYED for it, or your job is related, it really doesnt apply, this IS my line of work (repair/Custom builds on pcs) and even run a side-business doing so.
I have my degree, what do you have?
Im saying straight out your theory has no basis and clearly DOES NOT REFLECT RESEARCH.
If that pisses you off i really dont care, i didnt get as far as i am "playing nice" with kids
Saying enough people verify it, also false, those who do are (same as you) going on hear-say
Nothing more. And more then likely other steps were taken, which again, totally wipes your supposed theory of anything credible. Have a good day