yashsingh1/xdaforums huggingface dataset:
[Nexus One Android Development] RogerPodacter:
How ironic, all this week I've had identical issue with fastboot on my atrix, the zImage would just fail to flash. I finally solved it by entering the bootloader in a different way, the proper way I guess. Sometimes it said successful flash, other times it said failed.

On my nexus I just type the fastboot command, then use quickboot to force directly into bootloader mode. This worked fine everytime on the nexus. Not so with atrix. Instead I have to enter bootloader mode beforehand, cable connected, the run the command. Finally it flashes! Then fastboot reboot to turn on.

Fastboot is very safe, it will never flash anything unless it wont flash properly, so don't worry about keep trying different ways till you get it.
[Nexus One Android Development] RogerPodacter:
I think I might know why its possible to sometimes not see the timeout bug, and it gas to do with if you left the phone aline while it charged fir that hour, or if you woke it up at all.

And of course we already know that the timeout bug only happens every 60 minutes, so you wont see it tills the first hour exactly.

But my first point above, in deep sleep the poll counter timer progressively gets thrown off, more and more out of whack. You'll notice your dmesg logs sometimes the time stamp is way off. This makes it possible to sometimes avoid the timeout, and sometimes not. More testing needed and I think your change likely will fix this.
[Nexus One Android Development] Dr Byte:
Thanks for that, and I think the ManU 2.0 version of the code might work with it, but I'm pretty sure now that the current code (in 7.1rc1, and in the github) won't exhibit this behaviour. EViollet's next kernel will be based on thalamus' current driver, which has the CM7 logic.

Of course, the whole "lastseen" logic is flawed; there should be a simple, unambiguous, unconditionally executed if() in the driver, followed by another if, not an else-if: "is the charging circuit on, and current flowing into the battery? then update last_seen." Nothing else. The other "lastseen" stuff can be removed elsewhere in the function. The bug originated in the convoluted branching and selective updating of last_seen.

If you follow the codepath in the old driver, the "approximately 60 minute" timeouts are inevitable. I think the old test (line 845, if battery_full == 1) is actually the problem - it should be "== 0") ie, "are we still charging" which is what the CM-current driver tests (is the current >1ma?)

This is clearly old-hat to thalamus (and whoever updated the CM driver), so I think we can drop this here and thank them.

In shock-horror on-topic news [ :) ] I actually managed to get a proper calibration last night, on my "old" battery, which has about a year's worth of wear on it. It didn't actually complete perfectly, but I have the numbers that matter. In my bleary-eyed condition this AM, I forgot to do two steps: 1) unplug the charger before checking the age; and 2) reboot before pushing the age manually. Damn.

So I don't know if it would have written the age away properly, but I'm now confident the "effective age" is 87% and the capacity 1238mAh. That's where it maxed out just before jumping to 100% and BATOFF/full.

I pushed that number in with the program and went back to sleep :D If I had been more coherent at that hour (impossible!) I might have let the learn "complete" by unpluging first. Oh well. There's always next time! This LEARN cycle and the other one last night are the ONLY ones that have given "true" results - the dozen or more attempts on CM7.0.3/ManU 2.0 all claimed 1416 or so mAh capacity... and all had timeouts, AFAIK.

I am quite confident of this age, because before I started on this whole calibration journey, it was dying at 13% :D

All ducks in a row now :)

So: if you're getting TIMEOUT errors, try updating to CM7.1rc1 - it has fixed all the problems I had with 7.0.3, including these.

It's probably also worth mentioning that the chances of getting a proper LEARN cycle without an AC charger are slim, unless you disable all the radios and background software. My first attempt last night was a PC-USB learn... which lasted all of 15 seconds before the learnflag went off (current went < 0) - before I could even turn the "max drain" settings back to normal! Maybe the app should warn about this?

Next experiment: drain it again, do an overnight PC-USB slow forming charge with age=100, drain it, and calibrate again :D It's amazing how fast you can drain the battery if you try. Camera, GPS, and bright screen do wonders. Think about this as you geo-tag your photos outdoors... :)
[Nexus One Android Development] Treatcon:
Need a little advice from the pros here if you don't mind.

In June I bought a new Innocell 1600mAh Extended Life Battery directly from Seido's website. Used it for two months and decided to calibrate it.

Click thumbnail. 76 KB -- 480 w X 800 h

First pic here just a screenshot before the learn mode was activated.

Click thumbnail. 81 KB -- 480 w X 800 h

Second pic here is when I woke up the phone for the first time and as you can see from the time it was almost 5 hours later.

Click thumbnail. 86 KB -- 480 w X 800 h

Now I unplugged my phone from the wall charger, powered it down and turned it back on. Immediately lost 2% of the battery. Now I loose about 5% an hour with minimal apps running. I understand how apps running effect the battery, but what I don't understand is that before I enter learn mode the voltage is always pretty steady around 3.6-3.7 and mAh is always increased by 200 twice, so 400 total. I never see that 400 mAh. Aged capacity says 1412, but the way the battery drops is like I'm loosing 400 off the top somewhere hence the quick battery drainage. This will make the third time I've calibrated the battery this week in an attempt to get it to calibrate properly and the mAh is always increased by 400 so it doesn't shutoff because the mAh is low and the mV is still around 3600.

The stock battery still holds a better charge than this Seido. Is it possible I got a lemon? I just ordered a new Mugen, but would like to save the Seido if possible as a spare.

Advise I guess on possibly saving this battery??

**EDIT**

Using OxygeN1mod by ch33kybutt and he has the battery calibration built in.

http://xdaforums.com/showpost.php?p=16875060&postcount=160
[Nexus One Android Development] mtw4991:
Most kernels lately will allow a current(mA) discharge even while plugged in once the battery reaches 100%. This is to avoid constant recharging, which increases the number of charge cycles and prematurely reduces battery age. Standard is to discharge to 89% or less, then recharge. Not sure how ch33kybutt does his.

Mine will show -1% in battery monitor soon after reaching full charge while still plugged in. The 400mAh (ACR Adjustment?) you refer to is only visible during learn mode on the General tab under Empty Current until charge capacity(mAh) equals or exceeds the 400mAh, then it gets cleared. Not quite sure what you are asking, but 1-2% decrease after boot is fairly normal.
[Nexus One Android Development] Treatcon:
I guess the short and skinny is, can I recover that 400 mAh permanately and make it useable? Seems its wasted.

When my battery gets to say 5% I can run your battery calibration app, enter learn mode and because the voltage is still 3.6+ and mAh is around 40 the ACR adjustment adds 200 mAh and viola I now have 18% battery left. When that 18% gets down to 5% I can repeat that step and get 18% battery life back.

Or am I misunderstanding what calibrating the battery means? Shouldn't the voltage be 3201 with 0 mAh at 0% battery?

Thanks for the help.
[Nexus One Android Development] mtw4991:
In a perfect world, 0mAh/3201mV/0% are all achieved at exactly the same time :D However, I've never been to "that" world. Theoretically, you can continue bumping the ACR to trick the chip into thinking it has 400mAh left in it until you reach 3201mV, then it will die regardless of how many mAh it thinks it has left.

Temaseks' battery will get really close to 0mAh and 3201mV, but mine doesn't. It will reach 0mAh and still have 3300-3400mV left, no matter what I do. The point of calibrating the battery is to charge to a true 100% and have it die at 0% while properly calculating its' age as time goes by. That's what the app does. An added bonus is we get to squeeze a bit more juice out of it with a few tweaks.

Hope this helps! ;)
[Nexus One Android Development] Treatcon:
Thank you for clarifying that. I was under the impression that the battery calibration app did more than what it currently does and puts all batteries on the same playing field. My original N1 battery will nearly make it to 3201/0/0% before it dies, same as Temaseks. I initially thought that the battery calibration app made my battery like so and was hoping it would do the same for the new Seido battery! Just like everything else, each battery is unique. I just thought I had bought a lemon battery at first, guess they all differ.

Thanks again!
[Nexus One Android Development] mtw4991:
Mine will occasionally get close, depending on the activity I'm doing at the time, fyi. Glad I could help as I know it is a complicated thread and very technical. Just hit the thanks button if you like as I removed my "buy me a beer" button ;)
[Nexus One Android Development] Dr Byte:
Slow-charge calibration

Ran a slow-charge calibration overnight. A normal charge reaches 100% after 3 hours. This one took 6 hours.

However, despite recording no timeout errors, the calibration failed again (like all before it.) The battery age remained at 100% afterward, after removing the charging cable, and after a reboot. :(

Unfortunately, I don't know exactly how much energy was stored, because the battery log history had long since scrolled off the top of the buffer by the time I woke up :(

I am expecting it to "die" at 13% though. Time will tell. I'm going to try this battery for a week or so, and charge it only via the slow (computer) method and see whether it can be rejuvenated.

Still haven't seen a single TIMEOUT since 7.1rc1...
[Nexus One Android Development] Patsfan123:
A few quick question. My battery seems to have 1136mAh left. Is it better to set the Full40 to 1452 and set the battery age to 78%=1136/1452? Or should I set the Full40 to 1136 and set the battery age to 100%?

Also, do you need to run another learn mode/calibration if you already know these values?
[Nexus One Android Development] temasek:
Either way u set, the result is the same so its personal preference. Also if u knew your values, no need to redo learn cycle.
[Nexus One Android Development] Sharks8:
Does a battery wipe stats in Amon-Ra recovery reset a bad calibration ? In fact, I had a problem during the process and i want to reset everything.

Thank you
[Nexus One Android Development] temasek:
No.

Battery stats just a history of your battery usage and nothing else.
[Nexus One Android Development] Sharks8:
So is there any other ways to reset everything ?

Thanks a lot
[Nexus One Android Development] temasek:
Only way is to manually set your values back to whatever it was before.
[Nexus One Android Development] Dr Byte:
Battery age or Full40?

Ran into this issue myself, like a recent poster (Patsfan).

My "old" battery was topping out at around 88% & 1250mAh before jumping to 100% on a calibration charge... so I set the age manually to 88% after several attempts failed exactly the same way.

After a "normal" (slow) charge, it reached 1250mAh and was still going strong at >150mA charge current, all the way to 1350mAh.

As a result, I have now changed the battery to "100% at 1350mAh Full40" and will see how that works out. Clearly, 88% @ 1452 is wrong, and it's closer to 93%.

It does SEEM to be a more logical way to proceed after calibration: set the Full40 to the actual level achieved, and "age" from 100% from there. It seems a more exact way to tell the chip what to expect. Mind you, I'm deliberately deep-cycling the battery and doing slow charges to try and rejuvenate the capacity during this testing. We'll see how it goes :)
[Nexus One Android Development] invisiblewave:
Can someone tell me what I'm doing wrong???

I can get to learning mode, airplane mode is activated, I plug in the power, everything looks good, then about two minutes later without me touching a thing and with nothing else running, it drops out of learning mode and airplane mode switches off. I've tried numerous times, always with the same result.
[Nexus One Android Development] theGanymedes:
It didn't work for me.. All readings were empty. I'm using SNQ_'s latest kernel for GingerBread...

PS: I have a Desire, not a N1
[Nexus One Android Development] mtw4991:
It will only work with phones/kernels that have the ds2784 battery drivers in /sys/devices/platform/ds2784-battery

---------- Post added at 11:58 AM ---------- Previous post was at 11:57 AM ----------

What phone and what kernel are you using?
[Nexus One Android Development] Treatcon:
Got my new Google Nexus One 1600mAh Mugen battery in last week and I've been conditioning it. Let it drain down to between 10-15% and charge it back up for a full 12 hours on a wall charger overnight. BEST battery to date!! The new Seido I had would only last about 18 hours before it would die on me. This Mugen has lasted 2 full days on a single charge and it shut down at 2%. I get around 2% battery loss per hour. I haven't calibrated it yet, kinda scared to LOL This battery far exceeds my expectations!!!!

Phone usage:

3g and Edge data enabled on 24/7, Wifi on when I get home and set wifi to shutoff when phone sleeps, gps enabled, about ten 4 minute phone calls and 20 text messages per day, trackball light notifications on for Gmail, SMS and MMS. ROM info in my sig :)
[Nexus One Android Development] mtw4991:
Mugen is a quality battery and can be calibrated. Sounds like just a bit of tweaking and you'll have a great battery :D I'd calibrate it..can't hurt it!
[Nexus One Android Development] Retrolock:
I must have done something wrong. I've set all the setreg and I finished the learnf mode and when I rebooted the battery age is still 100%. This is for a year old phone. I'm using cm 7.1rc and wildmonk kernel.

looking at the log

Capacity: 1270mAH

Voltage: 4187.31mV

Current: 20.368mAH

Age:100

battery: 88%

Capacity: 1443mAH

Voltage: 4187.31mV

Current: 20.301mAH

Age:100

battery: 88%

Capacity: 1443mAH

Voltage: 4187.31mV

Current: 0.0671mAH

Age:100

battery: 100%

Is the battery age 88% @ 1270mAH now? The charge suddenly went from 88-100.

I'm using the stock battery by the way, thanks!
[Nexus One Android Development] Retrolock:
and oh the reading was 0x87 instead of 0x81.. maybe that's it :(
[Nexus One Android Development] Retrolock:
finally did it! 88% @ 1265mah :D
[Nexus One Android Development] temasek:
1265mAh your full40?
[Nexus One Android Development] Retrolock:
I haven't done a capacity test yet but looking at the log its the highest reached before it hits 100%

Is that correct sir?
[Nexus One Android Development] temasek:
What full40 were u using?
[Nexus One Android Development] Retrolock:
I was using 1452, the default one.
[Nexus One Android Development] temasek:
Oh ok. If u are on stock battery, no such thing as a capacity test.

U are good now.
[Nexus One Android Development] DirkStorck:
Hi...I am trying your app with an Desire Classic...

That battery was drained and the pop up was shown thats says that the learing starts....Now I have a question. Should that button thas says that is is learing be active all the time till the phone is charing up ?

Thanks!
[Nexus One Android Development] DirkStorck:
Hi....

it downloaded until 84% and than it jumped up to 100%...I think someting went wrong...what should I do ? It shows a battery age of 94...
[Nexus One Android Development] mtw4991:
The learn mode flag(button) will turn itself off after a little while even though it is still in learning mode. Not to worry.
[Nexus One Android Development] glitchies:
Not sure if this is normal, but i was setting up my N1 as instructed, and after inputting one of the values, not sure which one, my battery% went from 95% to 35%. I realized after that i was supposed to be doing this with an almost empty battery. is this going to harm my battery? i didnt do any of the learning, just the setup for it.
[Nexus One Android Development] mtw4991:
Nope, won't hurt the battery at all. Re-read the instructions before trying again and follow the steps. If you need assistance, post here and one of us will be happy to help you, just give it time, we aren't here all day/night long. :eek:
[Nexus One Android Development] bobomankc:
I did what tutorial said but my mV won't drop to 3201... even at 0% it's around 35xx mV :S pls help
[Nexus One Android Development] temasek:
It's because your mAh depleted before your empty voltage point.

What u need is to bump up your mah. 2 ways to do it

1. Enable ACR adjustment in the battery app settings, or

2. Manually bump up your mAh by entering the following to the app

10 x 01 .... for additional 100mAh

10 x 02 .... for additional 200mAh

Bump up as much as needed.
[Nexus One Android Development] :
I'm doing the procedure right now, with the Calibrator app.. my n1 is in learn mode.. do i have to keep the phone with the screen on or i can leave it with the screen turned off and go away, and then pick it up at 9.45 pm? :)
[Nexus One Android Development] temasek:
Airplane mode with screen off.

Go to sleep or something more productive. No need to watch over it.
[Nexus One Android Development] :
Ok thanks temasek i'll do something else ;)
[Nexus One Android Development] :
Another question.. do i have to unplug and reboot the phone exactly after 4 hours? Something will go wrong if i leave it plugged in charge for more hours?
[Nexus One Android Development] bassmadrigal:
I actually recommend enabling the option to keep the screen on while plugged in (I think it is under Settings -> Applications -> Development). This way, you can monitor the percentage of the phone (since it will go green at 90% but still won't be charged). Once the phone is at 100%, it is safe to take off the charger. Check what the app shows for the Battery Age and make a note of it (you sometimes have to reinput that number into the app when the age gets reset).

If you leave the screen off, you just need to make sure you give the phone enough time to charge. So, I don't know if a 4-hour window is enough (I usually charge my phone overnight), but I would think it would be enough. Either way, if you leave it charging after it reaches 100%, you won't cause any issues with the learning process (as it completes when you hit 100%).
[Nexus One Android Development] sparkster84:
Hi, guys, I hope you can help me. I think my nexus one battery is a little broken, and before admit it, I would like to explore all the posibilities I have to try to solve the situation. Let me explain: since some weeks ago, after flashing a cyanogenmod nightly build ROM, I noticed that the phone shut down while it lasted near the 20% of the battery. These days I tried to calibrate it and I noticed that when it is charging, the level of the battery jumps from near 83% directly to 100%. I tried the following calibration methods:

At this point I found this post, so I tried all the methods in here:

Well, I think there is no more methods I can try to use that 13% of battery.

What do you think, could it be a ROM version problem, am I doing anything wrong or the battery is definitively broken? This is starting to be a huge pain in the ass.

Thanks for your time, guys.
[Nexus One Android Development] sparkster84:
Well... now when charging it jumps from 90 to 100%, and it shuts down at 9%. It's a little better... Should I use the calibration app again to improve it?
[Nexus One Android Development] bassmadrigal:
If the battery age got set to 100% (aka, brand-new), then it means the calibration wasn't performed properly (same if it gets to 94%). If you are shutting down at 13%, I would think your battery age would be somewhere in the 80s. You can always guess and play around with it from there. 85% is probably a decent starting point.
[Nexus One Android Development] sparkster84:
Well, I used it again and now it's set at 85%. I'll let you now if it works properly now. Thanks.
[Nexus One Android Development] Treatcon:
Just started to calibrate my battery for the first time since I bought it (quote above) and the mAh by default was set to 1755 with learn mode set to activate at 3006mV. This Mugen battery is worth every cent!
[Nexus One Android Development] sparkster84:
As you said it wasn't performed properly. Now it turns off at 0%. Thanks.
[Nexus One Android Development] cyberon:
Hi guys, having N1 shutdown on MIUI at 15%, so decided to take a look at this. :)

My questions are, where are the new battery values stored and, if by using this method will it be required re-installing the app and redoing the entire process after a hboot update or a simple Rom change?

Thanks.

Ps: I should set my battery age to 85% right!?
[Nexus One Android Development] temasek:
The battery values that u input into the app are stored in the eeprom of the battery. Once u input it will not be lost when u change rom or hboot. Once thing u will lose will be the battery age if u let the phone auto shutdown.
[Nexus One Android Development] cyberon:
My battery age should be around 85% so, from now on, if i let my phone auto shutdown, the only thing i will need to do, is add battery age through the app?

Thanks!
[Nexus One Android Development] temasek:
U are right.
[Touch Diamond, MDA Compact IV ROM Development] csjneek:
This rom was made using Eto X2.1 Ervius Kitchen.

The main goal is maximum ram and speed while using sense 2.5

Beware! I removed a lot of packages

Following sense tabs are disabled:

Internet

Photo video (htc album is included and also core player)

Music (htc audiomanager is excluded so if trying to enable this tab you'll get lot of errors, instead you have nitrogen player)

Facebook

Twitter

Stocks

Tachi dialer is removed - using default wmdialer with ryon black skin

Pagepool is 18mb for speed, ram free 40-50mb

Download

http://jump.fm/IGVNQ

mirror

http://www.multiupload.com/3BSC6DD7ZZ
[Touch Diamond, MDA Compact IV ROM Development] dlo2008:
Sounds interesting... thx

Is the documents tab included? :) (joking)

I'll try that tonight if I find the time
[Touch Diamond, MDA Compact IV ROM Development] Sica:
Helooo

Music tab does not work, says file "Audio manager_eng" can not be opened, and my location is not updated. Thanks very much!
[Touch Diamond, MDA Compact IV ROM Development] csjneek:
it seems that you did not read the first post
[Touch Diamond, MDA Compact IV ROM Development] imrock:
awesome work chef..especially the looks n the slider feels very responsive on our diamonds!! installed the audio manager attached below n got the music tab working but the calendar tab has problems adding new appointments and the twitter tab also doesn't work!! overall a very fast and responsive with low memory consumption rom made for everyday use!! cheers:D:D
[Touch Diamond, MDA Compact IV ROM Development] meteorain08:
Wow this looks great, really :) downloading and will try in a minute.... :)
[Vibrant General] jrwingate6:
Launcher Pro is by far my favorite launcher application but I have noticed a few bugs with it on my Vibrant lately. I know it's Launcher Pro causing them because my device doesn't duplicate them when running stock TouchWiz or ADW Launcher.

Bug #1 - When activating GPS it causes the entire phone to freeze and sometimes restart.

Bug #2 - Sometimes apps will not launch at all until I reset my device. If I click on a app it closes will open and close within 1 second.

Has anyone else experienced these bugs?
[Vibrant General] Alkaloid:
Been using LP for a few weeks now and haven't noticed either of those bus. In fact, LP has given me no problems at all.
[Vibrant General] CappyQ:
I've had LauncherPro installed since the day I purchased my phone in mid-July. Experienced none of these bugs. I don't think it's LP-related on your end.