Develop Bugs

i had great lattery life till today, not sure why?

I'm going through battery. Like its water while the phone is sitting idle. If done every trick and starting today its draining. Sending a feeler out there for advise.

which phone do you have?

Sorry, an EVO

thank you...sorry but i dont know much about evo but i can suggest you post in the evo forum and since your phone is new...it can be replaced easily

Quick question after permrooting with visionary

Hey everyone! I'm new here in a way with this being my first post but have been on xda for months lurking the forums and absorbing information having to do with samsung vibrant to now the g2. Before i ask my question I must say this website is the best website i have EVER got any sort of information about phones and everything and anything you can possibly do with them! And want to say thank you to EVERYONE who makes it possibly! Now for the question and some sort of problem. I permrooted my g2 last night and everything to my knowledge has gone well. I also even turned S-Off and now i can boot into recovery no problem. The only problem I seem to have and can't find the solution through google or on the forums is that when I have my phone completely powered down and put it on the charger after it's powered down the phone will just automatically boot into recovery without me even doing it. It says "go back to end debugging" when I go to check the key test and I really don't understand what and where it's talking about debugging when I just have my phone plugged into a outlet. If anyone has this problem or maybe has solved this with some sort of solution your insight would be greatly appreciated.

Nickb1989 said:
Hey everyone! I'm new here in a way with this being my first post but have been on xda for months lurking the forums and absorbing information having to do with samsung vibrant to now the g2. Before i ask my question I must say this website is the best website i have EVER got any sort of information about phones and everything and anything you can possibly do with them! And want to say thank you to EVERYONE who makes it possibly! Now for the question and some sort of problem. I permrooted my g2 last night and everything to my knowledge has gone well. I also even turned S-Off and now i can boot into recovery no problem. The only problem I seem to have and can't find the solution through google or on the forums is that when I have my phone completely powered down and put it on the charger after it's powered down the phone will just automatically boot into recovery without me even doing it. It says "go back to end debugging" when I go to check the key test and I really don't understand what and where it's talking about debugging when I just have my phone plugged into a outlet. If anyone has this problem or maybe has solved this with some sort of solution your insight would be greatly appreciated.
Click to expand...
Click to collapse
It is a known issue of ClockWork Recovery. Nothing we can do now, until/IF Koush-the author of CW OR anyone knowledgeable enough to sort it out.

androidtoy09 said:
It is a known issue of ClockWork Recovery. Nothing we can do now, until/IF Koush-the author of CW OR anyone knowledgeable enough to sort it out.
Click to expand...
Click to collapse
on the dot.
its specifically within cwm, even other phones are experiencing the same issues with cwm

So no possible fix or something like that to keep it from happening? I mean I usually shut my phone at night just to give it a rest and to charge but now I can't because of recovery. Does everyone who permroots their phone experience this or only some?
Sent from my T-Mobile G2 using XDA App

Nickb1989 said:
So no possible fix or something like that to keep it from happening? I mean I usually shut my phone at night just to give it a rest and to charge but now I can't because of recovery. Does everyone who permroots their phone experience this or only some?
Sent from my T-Mobile G2 using XDA App
Click to expand...
Click to collapse
No possible fix I've seen as of yet. I'm sure many people do witness this happening, but I personally never turn my phone off at night just to charge it. I hear its not good for batteries to over charge them again and again. I usually charge mine in morning and throughout the day and leave it be over night.

r3s-rt said:
No possible fix I've seen as of yet. I'm sure many people do witness this happening, but I personally never turn my phone off at night just to charge it. I hear its not good for batteries to over charge them again and again. I usually charge mine in morning and throughout the day and leave it be over night.
Click to expand...
Click to collapse
There's no such thing as over charging Lithium Ion battery lol. You can plug it in 24/7 and be safe. It is a myth.
Read this: http://batteryuniversity.com/index.php/learn/article/charging_lithium_ion_batteries
It is impossible to overcharge Lithium Ion Battery.

Well I guess I'll just have to wait and deal with it until a fix hopefully comes out for it. And ya I never heard of overcharging lithium ion batteries...but idk. Now while waiting for a fix for that little bug i'd like a flashable overclock
Sent from my T-Mobile G2 using XDA App

androidtoy09 said:
There's no such thing as over charging Lithium Ion battery lol. You can plug it in 24/7 and be safe. It is a myth.
Read this: http://batteryuniversity.com/index.php/learn/article/charging_lithium_ion_batteries
It is impossible to overcharge Lithium Ion Battery.
Click to expand...
Click to collapse
Nickb1989 said:
Well I guess I'll just have to wait and deal with it until a fix hopefully comes out for it. And ya I never heard of overcharging lithium ion batteries...but idk. Now while waiting for a fix for that little bug i'd like a flashable overclock
Sent from my T-Mobile G2 using XDA App
Click to expand...
Click to collapse
Meh. I've had a bunch of people tell me they had to buy new batteries from leaving their phone charging all night and a few reps have told me not to do it. I think specifically that was when I had my BlackBerry. That's only reason I thought that. =P Either way, thanks for the info. Learning is great. =]

Well i can tell you i had an adp1 and my wife had a g1 she would charge throughout the day and i only charged at night. While we both had to get new bats because of swelling hers died a lot faster then mine. So i say charge when its dead at night is better but thats just mho.
Sent from my HTC Vision using XDA App

shortlived said:
Well i can tell you i had an adp1 and my wife had a g1 she would charge throughout the day and i only charged at night. While we both had to get new bats because of swelling hers died a lot faster then mine. So i say charge when its dead at night is better but thats just mho.
Sent from my HTC Vision using XDA App
Click to expand...
Click to collapse
I agree. Night time charging to me seems to be the best amd I've never had a problem with a battery from doing that. Even if the phone wasn't completely dead. Seems to be ok with me lol
Sent from my T-Mobile G2 using XDA App

ever notice ur phones charging led change colors when its full? we have a smartphone fellas, its smart enough to hold a charge, stop charging, let it trickle, and maintain a full charge safely.
Sent from my T-Mobile G2 using XDA App

[Q] Getting a new epic 4g touch

So I'm getting a new epic 4g touch on Tuesday. What steps do you guys recommend doing on a new epic 4g touch? A couple things I wasn't sure about was calibrating the battery and which version ROM I should install? Any other tips/advice from the start would be appreciative!

GHOSTIVVI said:
So I'm getting a new epic 4g touch on Tuesday. What steps do you guys recommend doing on a new epic 4g touch? A couple things I wasn't sure about was calibrating the battery and which version ROM I should install? Any other tips/advice from the start would be appreciative!
Click to expand...
Click to collapse
My friend welcome to xda and your new purchase. I suggest the best thing to do because you can get a lot of different answers to your questions is to check out this thread here.
Do a lot of reading more over the next couple of days to get a hang of how things operate in here. I dont know what phone you are coming from but this is definitely a nice phone and easy to root w/ a few rom choices.
Like I said start with what I linked and just go through development section and read, read, read and then read some more.. I know it sucks but its going to pay off. Oh yea don't lose your mind over LOS either its been solved for mostly everyone...lol
Quick Answers:
Q: calibrating the battery
A: recovery has option and there are apps on the market
Q: which version ROM
A: Your choice I advise try them all if you like. Thats what nandroid is all about
Again welcome

Thankyou for the insight! I am coming from iphone 3G/3Gs and currently have had the iphone 4 since it came out. I've always loved android but up until now haven't had an android-based phone. I've become bored of iOS and seems that android is a lot more open which is something that I like. With the phone being new and all is the battery calibration really recommended/needed? Again, thanks for your input!

Battery calibration isn't really needed, that is to say that your phone will work fine without doing this. However, after flashing new roms or even after a few months of discharge cycles, it's adviseable to clear the battery stats referenced by the OS. You will need root access to do this.
Easiest way to do this is plug the phone to the charger, go to sleep, when you wake up, open the app Battery Calibration, press the button, unplug, and use the phone all day and night until it dies on its own. It's important to charge the phone fully after that in a single session.
For starter roms, I recommend sticking with the latest stock Samsung release. Use it for a week or two in order to get a baseline of what you like, dislike, and to help find your own personal preferences. You can then start test-driving the other offerings, while making nandroid backups as needed for the ability to quickly go back. I find myself cycling back and forth between Calkulin's rom and Blazer. The former for the reputed battery life and the latter for general eye candy. Neither comes with a kernel capable of being overclocked with the easy methods, so if that's what you're after, you can try the "Desperado" (v1.3 is latest) and clock it up to 1.6ghz if you find a game that needs it. Suffice it to say, my E4GT is now underclocked at 1GHZ whereas my Epic 4G was typically at 1.5-1.6ghz... yes, the phone is quick.

Evo DESIGN 4G battery doesn't fully charge

I have a Sprint Evo Design 4G that I am preparing to sell and I need to resolve this problem. The phone is stock and unrooted. Prior to the ICS update, the phone worked perfectly fine without any problems. Ever since the update was installed, the phone will charge the battery until about 75% or so, then proceeds to go into some kind of trickle-charge mode. The most success I've had getting it charged is to physically turn the phone off and let it charge overnight, in where it charged to the high 80s%.
This is not a battery problem, or a charger problem. Everything indicates to me it's a software problem, so I'm looking for a software solution. I'm comfortable with rooting the phone, but I do not want to install a non-stock ROM and would prefer to lock the bootloader on the phone again after I'm finished.
Prior to this phone, I had a Nexus S 4G that went completely to hell after it's ICS update, which is why I bought this phone. I had all but given up on it when a friend suggested I take the phone back to it's out of box ROM, then let Sprint do it's over the air update. After doing that, the phone came back to life, which is why I'm selling this one. The idea of doing this again on this phone appeals to me greatly, but primarily I just want to resolve this battery problem. Any help would be appreciated.

kericr said:
I have a Sprint Evo Design 4G that I am preparing to sell and I need to resolve this problem. The phone is stock and unrooted. Prior to the ICS update, the phone worked perfectly fine without any problems. Ever since the update was installed, the phone will charge the battery until about 75% or so, then proceeds to go into some kind of trickle-charge mode. The most success I've had getting it charged is to physically turn the phone off and let it charge overnight, in where it charged to the high 80s%.
This is not a battery problem, or a charger problem. Everything indicates to me it's a software problem, so I'm looking for a software solution. I'm comfortable with rooting the phone, but I do not want to install a non-stock ROM and would prefer to lock the bootloader on the phone again after I'm finished.
Prior to this phone, I had a Nexus S 4G that went completely to hell after it's ICS update, which is why I bought this phone. I had all but given up on it when a friend suggested I take the phone back to it's out of box ROM, then let Sprint do it's over the air update. After doing that, the phone came back to life, which is why I'm selling this one. The idea of doing this again on this phone appeals to me greatly, but primarily I just want to resolve this battery problem. Any help would be appreciated.
Click to expand...
Click to collapse
U r in the wrong forum device. This is supersonic evo 4g nope design
Sent from my PC36100 using Tapatalk 2

There is no forum for the Evo Design 4G. Thanks for your help.
TroNit said:
U r in the wrong forum device. This is supersonic evo 4g nope design
Sent from my PC36100 using Tapatalk 2
Click to expand...
Click to collapse

Thread locked. So because there is no forum your gonna ask in the wrong forum just in case....
XDA Moderator

Help is on the way. The State of our elderly Evo :(

First off the evo was officially released in june 2010. Only a few months till we are wishing our evo happy third birthday. Oh I have heard a rumor floating around that the Og Evo is one of the most active devices on XDA.
I have been a member here for a few years. I started with the cricket zio. Then the Og Evo, a 3vo for my girlfriend at the time, and then I fell victim to a boot loop of death. So back to my old a$$ Samsung Messenger II (I had already given the zio to my son as a music/media/911 device) till I could pick up another evo. Found a bad esn hybrid black front/white back og with no battery and seller stated vibration did not work. For $40 shipping paid. Thankfully I didn't sell my 3500 mA extended battery or mid-grade otter box case when I sold my first evo on ebay for $80. Remember it had bootloop of death and also a bad esn.
With some of our phones actually being three years old there are bound to be cataclysmic failures showing up. Over the past few weeks I have noticed a common problem spread out over the massive selection of roms we have. There was nothing really that the roms shared except for the fact that just this one person, never the same one that I can remember, would have this STATUS 7 ERROR during the flash causing the installer to abort. The first couple of times it came up I just passed it over as some wierd error due to something completely different than the real problem.
The following is from a the cm7 unchained thread.
Well with these problems popping up I have been thinking about implementing an old trick. You know about changing partion sizes. We can enlarge the boot and system partions and reduce the data size. We then use a2sd to make up for what we used on the other two. Now all I need to do is add the adjustment to the installer-script.
Although there is a side effect of this. When a different kernel is flashed it will not know how to read the partions. So then the user has to flash another script to change the partion parameters in the new kernel.
Now to shine a light on what the issue is that is causing what seems to be a random problem. The evo has been around since June 2010 and is getting old. The more recovery logs I see the more bad blocks I see. The memory only has so many write cycles before it burns out.
Now with all rom flashing we do just takes another write cycle from the evos life. If we start digging further into the lives of our users we will notice two groups with issues. The older phones (from '10 or '11) and the addicted flashers/developers. Both of which have used up some of their lives testing and flashing.
True be told we can bandaid the evos memory with symlinks to the sdext till we only have the files needed to symlink everything else to the sdext. Only problem will be the transfer rate of sdcard.
Hope this was enlightening and informative. Also if you have not noticed I am working on the TNN Rom toolbox which will help everyone in finding a solving the problems as they pop up.
The thread is in general discussion but only gives highlights of what will be coming. I still have to write the install script to copy logcat automatically to the TNN folder and create a md5sum of the rom flashed. Now I will have to add in the partion adjustments and make a kernel fix script so different kernels can be flashed.
Peace,
Love, and
Happiness

Extra power for my development
Well I have recently lost my job which is why I have been able to get all the roms out so quickly and with very few if any bugs.
Then on a few days ago PlatinumPenguin tells me that he has a 3vo sitting unused in his desk drawer. He states that the Og Evo just sounds so much better than the 3vo on his headphones. Long story short he is packing up the 3vo and giving it to me. Talk about a nice guy. So I will move to the 3vo as my phone with service and have the Og completely free for developing purposes.
Then yesterday my buddy tells me that he has an Inspire that his wife wants to put back on att. The problem is that he dropped it and shattered the screen. Then got upset about it and threw it at the wall damaging the power button and volume keys. No power button no phone right. Well it just so happens that I know a trick or two. He hands me the phone and started to walk away. I quickly do my trick and power up the phone before he gets a few feet away. I tell him to watch this phone boot up. Trick is you take the battery out, connect the charger to phone and wall, and then reinsert the battery. B.I.N.G.O. Houston we have lift off.
Now he offers me his bad esn evo with shattered screen if I can replace the screen and get the buttons working on the Inspire. For those unfamiliar with the Inspire it is part of the evo family. It was an att phone almost exactly like the Thunderbolt except it has no ffc.
Now I have two Og Evo's to use for development purposes. Now I can flash two roms at the same time First I have to root the two new to me evos and an Inspire.
Then maybe I can get the TNN Toolbox written up on post 1. With a collection of other tips and tricks for our evo on post two.
Umm time to hit the rooting section of all three phone. It has been awhile since I have done the Og (hw003 latest update from sprint installed Nov '11) the second evo came rooted. I did the 3vo back around august of last year. It took me some time to figure out exactly how to do it. I didn't use the wire trick which had just come out for the 3vo.
Anyways stay tuned for more innovations from Team No Name. They will be coming to a server near you soon. Long live the Evo. Even if we end up running 90% of our roms from a symlinked sdext. Heck who needs internal storage anyways.
Peace,
Love, and
Happiness

Re: The State of the elderly Evo Hopefully help will be on the way.
Two
Look forward to this. Count me in to assist where I can. Still noobish as far as development but pretty savvy in regards to understanding how this works and a quick learner.
Sent from my Galaxy Nexus using xda premium

Re: The State of the elderly Evo Hopefully help will be on the way.
Oh wow I just powered up this bone stock evo 4.67.651.3. I am going to do a timed boot comparison but it sure looks like the stock one takes twice as long to boot.
It is kind of mind blowing to think that there really is that much difference between a stock and modded phone. They are both hw004 so I can use all my nands on both phones. Oh just so you know I had already booted my newly acquired evo a few time before I started both at the same time. No cheating since both already had a dc made.

Re: The State of the elderly Evo Hopefully help will be on the way.
This is almost like finding out my old EVO has cancer and the more I flash it the more the cancer spreads.

I've had my OG Evo since December 2010 (still stock and unrooted). I recently BOYD'd it over to Ting and bought my wife a used OG Evo off of Glyde. Hers I rooted (my first root ever) without issue and am running MBQsniper's Triple S. I am planning to root my device once I get all the bugs worked out of hers, get SMS copied over, etc.
So, needless to say, I've recommitted to the OG Evo at least until Sprint (and therefore Ting) kills wimax and maybe longer. I'm glad there are people around that are much more knowledgable than I that are still paying attention to this device. It's also funny how everyone seems to be from Texas...

jlmancuso said:
The evo has been around since June 2010 and is getting old. The more recovery logs I see the more bad blocks I see. The memory only has so many write cycles before it burns out.
Click to expand...
Click to collapse
If this is the point you are making the thread title camouflages it somewhat. But it's a very good point.
Can I add another important point regarding the advanced age of our "elderly" Evos?
Batteries also decline with age.
There was a recent discussion around here about buying a replacement battery, which size, which brand, blah blah.
If you are replacing an original launch day stock battery that has been through hundreds of charge/discharge cycles, I can guarantee the details of your replacement battery do not matter as long as it is new.
I had been using a replacement battery for a while and just for the hell of it put in my original battery a week ago. After calibrating and letting it go through a few cycles, I was completely blown away by how bad the battery life was. Same ROM, same usage pattern, just went back to the old battery. I just ended a 13 minute call and watched my battery go from 50 to 15. What is that, 40 minutes of talk time on a full charge? No one would sell a mobile phone like that (not today, not three years ago, 1986 or ever).
So all you people inheriting old Evos (or trying to find new life for your own vintage Evos), please, before you clutter up ROM development threads with comments on battery life, REPLACE YOUR FREAKIN BATTERY FIRST.
Now if they could just "recondition" the non-replaceable flash memory to get rid of those bad blocks..

NxNW said:
If this is the point you are making the thread title camouflages it somewhat. But it's a very good point.
Can I add another important point regarding the advanced age of our "elderly" Evos?
Batteries also decline with age.
There was a recent discussion around here about buying a replacement battery, which size, which brand, blah blah.
If you are replacing an original launch day stock battery that has been through hundreds of charge/discharge cycles, I can guarantee the details of your replacement battery do not matter as long as it is new.
I had been using a replacement battery for a while and just for the hell of it put in my original battery a week ago. After calibrating and letting it go through a few cycles, I was completely blown away by how bad the battery life was. Same ROM, same usage pattern, just went back to the old battery. I just ended a 13 minute call and watched my battery go from 50 to 15. What is that, 40 minutes of talk time on a full charge? No one would sell a mobile phone like that (not today, not three years ago, 1986 or ever).
So all you people inheriting old Evos (or trying to find new life for your own vintage Evos), please, before you clutter up ROM development threads with comments on battery life, REPLACE YOUR FREAKIN BATTERY FIRST.
Now if they could just "recondition" the non-replaceable flash memory to get rid of those bad blocks..
Click to expand...
Click to collapse
True that. I had to go back to my original battery and it's stupid how bad battery life is.
As for the bad blocks, funny how 2 years ago, we believed you could write/re-write millions of times with no ill effects

Looks like you've been doing your homework brother,this looks to be promising.

Well actually most of the partition adjusting is old stuff. I just have to find a way to change the boot size. They were doing this back in the hero days.
Sent from my PC36100 using xda app-developers app

I am getting a status 7 error. Sucks, I loved my OG Evo
Sent from stock rooted Galaxy SIII

Status 7 error is a fail on installing boot image. I suggest removing the lines in the installer script for the boot.img and flashing a kernel separate. The use of a smaller kernel may solve the issue.
Sent from my PC36100 using xda app-developers app

Write cycles for NAND chips are in the order of 10k. Do we have fruity modders surpassing this number?!?
Wild!
0_o

Well lets look at it this way. 10,000 writes over 3 years (oldest evo) over 365 days and we have 9.13 writes a day. So while a 10k life sounds long it is over quicker than you think.
Hope this helped shine some light on the subject.
Sent from my PC36100 using xda app-developers app