Battery meter news

[numus]

Well thought i would give an update since i just woke up after dealing with the battery meter all night..
It doesn't look like it will be possible to output real percentages on the moment.. this is due to the adc values being to small. Samsung must have switched the adc chip from the spica to the moment even though they use the same board
Good news is i have new values for the voltages instead of the made up ones we were using before thanks to converting the Behold II values and recalculating ADC values.. one problem i noted about Samsungs original code is the numbers were wrong... So hopefully the new code will be a little more accurate and i am going to try to get reported values to do integers of 5 instead of 10....
The new reporting levels will hopefully be Anything x9-x5 will report as x5 on the meter.. and anything x4-x0 will report x0 on the meter...
Example 99,98,97,96,95 will report as 95 instead of how 99, 98, 97,96,95 all report as 100 right now and 94,93,93,91,90 will all report as 90 instead of 94,93,92,91,90,89,88,87,86,85 all reporting as 90

 

[latinmaxima]

This is great to hear. Between you and Zefie and others we all technicaly have maintenance releases already for our phones by reflashing and rooting. (atleast those willing to take the risk right now) You guys are awesome!

 

[numus]

Well i got an integer 10 recode done and found there are 2 reporting values.. a mid and a low level.. not sure which uses what but mid value assumes anything less then x0 is (x-1)0 and low level assumes anything between x5->(x-1)6 is just x0 ...

 

[flu13]

So, Numus, I'm relatively new to the community here, but you sure as heck sound like you know what you're talking about, so I'm curious... Are you an actual developer on the Android OS (or Samsung firmware), or are you just talking about modifying the OS on your own since it's open source?

 

[numus]

So, Numus, I'm relatively new to the community here, but you sure as heck sound like you know what you're talking about, so I'm curious... Are you an actual developer on the Android OS (or Samsung firmware), or are you just talking about modifying the OS on your own since it's open source?

I am a graduate student in Chemical Oceanography at FSU along with a state employee working for the Department of Health
Me and TBone have already modified the OS (yes it is open source thankfully).. Currently myself and zefie are beta testing a new rom that has compiled in a new battery source code... It seems to be very stable so far and it reports values at 5% intervals with a pretty good accuracy... The original code that samsung released was garbage.. It turns out no matter how much you "cycled" the battery, you were not calibrating the meter and it wasent getting any closer to real values.. it is because they grossly miscoded the static variables and those had to be changed..

 

[flu13]

Cool to know, thanks. So for those of us who never had any intention of rooting our phone or anything crazy like that, will you have some nice, detailed instructions about how to do it when the time comes?

 

[Johnny Cakes]

Would it be possible to have low values intentionally mis-reported to the OS? Many feel that the #1 problem of the Moment is its restrictions once the battery level is reported below 15%. For example, the camera and keyboard lights do not work and the screen dims. If the OS could be falsely told that the battery was over 15%, then these restrictions would not be imposed.

 

[numus]

Would it be possible to have low values intentionally mis-reported to the OS? Many feel that the #1 problem of the Moment is its restrictions once the battery level is reported below 15%. For example, the camera and keyboard lights do not work and the screen dims. If the OS could be falsely told that the battery was over 15%, then these restrictions would not be imposed.

No.. because it was coded wrong.. the new meter code has the correct values so when the phone hits 15% it is pretty much 15% in the battery.. I had to redo the entire coding values with the correct ones (they were really off) that i built based upon the BEHOLD II's voltage reports (same battery).. at that point you need the conservative battery mode...

 

[Johnny Cakes]

No.. because it was coded wrong.. the new meter code has the correct values so when the phone hits 15% it is pretty much 15% in the battery.. I had to redo the entire coding values with the correct ones (they were really off) that i built based upon the BEHOLD II's voltage reports (same battery).. at that point you need the conservative battery mode...

Many of us feel that the phone is useless when it reaches the under 15% mark. So we are losing 15% (even if accurately coded) of the value of the battery.

Would it be possible to write code which would report over 15% until the battery reaches 2% or some lesser value? Granted this might not be for everyone, but it seems like if you have solved the secret to the battery life coding, this could be an option for those of us to load who wanted it. Wouldn't this just involve changing numbers in the code you have already cracked? If so, couldn't this be a variation for those who wanted it?

 

[numus]

Many of us feel that the phone is useless when it reaches the under 15% mark. So we are losing 15% (even if accurately coded) of the value of the battery.

Would it be possible to write code which would report over 15% until the battery reaches 2% or some lesser value? Granted this might not be for everyone, but it seems like if you have solved the secret to the battery life coding, this could be an option for those of us to load who wanted it. Wouldn't this just involve changing numbers in the code you have already cracked? If so, couldn't this be a variation for those who wanted it?

No.. The battery code was originally made to report 15% at 3.74 volts.. nominal voltage is at 3.7 on this battery so i have recoded all the voltages to hit around 50% at 3.7 where it is suppose to be.. when it hits 15% you are at the end of an almost linear decay and it needs battery saving after that...
http://www.samsungmomentforum.com/rooting/working-on-the-battery-issue-i-think/msg4427/#msg4427
I dont get into technical detail on this forum but that is where you can read about developments that went on for the battery code.. that specific post has an excel sheet that can you show yout eh new adc values i calculated, along with a graph of the battery discharge

 

[Johnny Cakes]

No.. The battery code was originally made to report 15% at 3.74 volts.. nominal voltage is at 3.7 on this battery so i have recoded all the voltages to hit around 50% at 3.7 where it is suppose to be.. when it hits 15% you are at the end of an almost linear decay and it needs battery saving after that...
Working on the battery issue... I think - New battery code based on BEHOLD II
I dont get into technical detail on this forum but that is where you can read about developments that went on for the battery code.. that specific post has an excel sheet that can you show yout eh new adc values i calculated, along with a graph of the battery discharge

Honestly, I'm not trying to pick a fight, but I don't get it.

You say that when it goes under 15% "it needs battery saving after that." Isn't that a value judgment? When it hits that mark, many of us feel that the phone is virtually useless, since it has no keyboard light, no camera, and a reduced display brightness.

So, for us under 15% is game over -- turn off the phone and/or install a new battery. I'd like to get use of that last 15% of the battery by NOT having the battery go into conservation mode.

It sounds like you could accomplish this from your coding, if you chose to do so. Since it is just changing numbers in the code, why not have two versions, one which does a traditional 15% battery conservation, and another which lets those who want to run the battery all the way down in full power mode?

 

[flu13]

It would be nice if it was a user configurable thing. Maybe tell it what functions to limit and at what battery percentage. Or even have the option to enable "power saver" mode.

 

[numus]

Seriously? You guys even know what the code is or how it is done? It is compiled into zImage.. there is no user defined variables.. and it is unsafe to alter anything below the 15% mark.. if you want to do it, go ahead.. the files are open sourced.. i have attached copies of my recoded code and header files on samsungmomentforum ... alter them all you want and compile them yourself... Just dont ask me to fix it if you screw up your phone by trying to make it do something it really shouldnt do.. all i did was put the code back to how it should have been in teh first place

 

[CriticalCritic]

...all i did was put the code back to how it should have been in teh first place

That's exactly how I would like it to be I like the 15% warning. Sure it disables the smart features, but it limits it to a sort of emergency phone-only mode. I admit that we do not need 5-10 hours of emergency phone mode, so I am looking forward to seeing the 15% mark hit where it's supposed to be

 

[numus]

That's exactly how I would like it to be I like the 15% warning. Sure it disables the smart features, but it limits it to a sort of emergency phone-only mode. I admit that we do not need 5-10 hours of emergency phone mode, so I am looking forward to seeing the 15% mark hit where it's supposed to be

2 hour 30 minute mark on the newest battery code and showing 80% (as reported by spare parts and openhome)

 

[MobstaJ]

I think the take away message for people like me who know nothing about coding or battery chemistry is that these guys have by and large fixed the 15% issue. I recently installed one of zeffie's kernals and this isn't an issue anymore. I can use the phone until it is almost dead. With no screen or keyboard dimming. Much thanks to Numus, Zeffie, Tbone, and all the other brilliant individuals out there who keep making this phone better (or more normal).

 

[numus]

So ya.. zef tried change the values below 15% to get more juice out of the phone and the funniest thing happened..
Every time he pushed the call button he got tasered by his phone!!!

 

[pizzachef]

Every time he pushed the call button he got tasered by his phone!!!

This sounds like a practical joke "feature" in the making

 

[CriticalCritic]

This sounds like a practical joke "feature" in the making

Yeah, id pay serious $ for an app that does that

 

[Johnny Cakes]

Seriously? You guys even know what the code is or how it is done?

I am so sorry. I bow to your greatness.

 

[zippy]

HI Numus, great job on all the work you guys have accomplished! Although I think it wise for most to wait on the 2.1 update, myself included, to ensure the least amount of problems, I think your battery work and the modem changes also listed at the Samsung forums are both serious enough changes for me to try and at least get those implemented. Could you simply explain the length of time needed and difficulty level to institute just those two updates to my phone? I am a game programmer, but a light phone modifier .

thanks

 

[numus]

HI Numus, great job on all the work you guys have accomplished! Although I think it wise for most to wait on the 2.1 update, myself included, to ensure the least amount of problems, I think your battery work and the modem changes also listed at the Samsung forums are both serious enough changes for me to try and at least get those implemented. Could you simply explain the length of time needed and difficulty level to institute just those two updates to my phone? I am a game programmer, but a light phone modifier .

thanks

I can't isolate out a battery only update (zef is the one who does all the compiling and patch work, i just supplied a new battery C code and header).. it is part of zefie's rom patch.. but the rom patch as a whole is very stable and shows vast improvements in phone function.. there really isnt anything in there to break the phone that we have noticed yet.. It is incredibly easy to apply the new kernel patch tho and a lot of people have been making easier to follow guides... I can tell you that at the 10 hour mark i was showing 55% battery remaining tho

I am so sorry. I bow to your greatness.

Step up or STFU

 

[flu13]

Seriously? You guys even know what the code is or how it is done?

Wow. Sorry, dude. I didn't realize that saying, "It would be nice if it did xxx," was akin to stepping on your balls. I think everyone was sounding very impressed by your work in figuring this out and appreciative of a potential fix. Dreaming of something a bit more was in no way meant to belittle that.

 

[zippy]

I can't isolate out a battery only update (zef is the one who does all the compiling and patch work, i just supplied a new battery C code and header).. it is part of zefie's rom patch.. but the rom patch as a whole is very stable and shows vast improvements in phone function.. there really isnt anything in there to break the phone that we have noticed yet.. It is incredibly easy to apply the new kernel patch tho and a lot of people have been making easier to follow guides... I can tell you that at the 10 hour mark i was showing 55% battery remaining tho

No problem, I just followed Wiki instructions and flashed to the dev build and will let you guys know of any issues. Seems only thing right now is that my notification lights are staying on when display times out and blackens out. I am hooked up via usb, so maybe has something to do with it. Mainly wanted the battery benefit and GPS help. Thanks!

edit: unhooked form USB and notification lights are now off ...

 

[numus]

Wow. Sorry, dude. I didn't realize that saying, "It would be nice if it did xxx," was akin to stepping on your balls. I think everyone was sounding very impressed by your work in figuring this out and appreciative of a potential fix. Dreaming of something a bit more was in no way meant to belittle that.

Assisting or coming up with REAL ideas is helpful.. Trying to pass off bullshit ideas without having a clue what you are talk about is really starting to piss off a lot of the development community.. to the point most of them wont even post on this forum anymore and stick to samsungmomentforum.com only.. I was trying to be helpful and letting those who don't actually follow the dev community know about potential fixes to common problems but if i am going to get bullshit responses and someone trying to tell me what i should do and doesn't take the hint the first time that i have no intention of doing that and it is unsafe/not possible, then i will just stop coming here.. I am already getting sick of posting the same thing over and over again because no one utilizes the search function or even reads the thread they are posting in...