Related
I am running DC v1.0 and i feel like ever since installing this ROM
after being on Fresh 1.1, my batter takes forever to charge via the wall
outlet (AC power). I followed all of the steps on xda as far as properly getting damage's rom to install on my phone. Running 1.6.2 recovery, and i did not upgrade my radio but that really shouldnt have any effect on how long it now takes to charge my phone. I have yet to monitor how long it would take using USB cable. Anyone else experiencing this? When i was running 1.5 while rooted, the phone would charge in no time (could go from 25% to full in about 1.5 hrs). Now it seems that an hour charging will only net me another 15% or so in battery life. Any suggestions on something i can tweak/fix or even monitor why this is happening?
ringer79 said:
I have yet to monitor how long it would take using USB cable.
Click to expand...
Click to collapse
I'm also running DC v1.0 and from what I can tell, if I plug into a USB port and am actually using the phone, it pretty much only "keeps up". Meaning that the battery doesn't go down, but it doesn't seem to be charging significantly either.
Haven't noticed any difference plugged into the wall. I can go from dead to fully charged in a couple hours (haven't timed it, but I'd guess about 2 1/2).
Same here, really annoying. I've been charging the thing all day...
:/
Try this. It allows the phone to sleep properly, and also helps charge time.
this is one of those off the wall things that made me flash back to fresh 1.1...lol there were to many little things that would work. but then wouldnt,, and im sure its a combo of things etc.. but i got tired lol and went back..
spiritcrusher33 said:
this is one of those off the wall things that made me flash back to fresh 1.1...lol there were to many little things that would work. but then wouldnt,, and im sure its a combo of things etc.. but i got tired lol and went back..
Click to expand...
Click to collapse
Haha I read all the positive things, decide I will take the plunge, then this makes me just go right back to fresh...jeez lol
Well last night, I decided to flash a NAND build of gingerbread. Never thought it would be the last time my touch screen worked properly again.
Since then, my touch screen has been sporadic, working off and on. WP7 or Android.
I flashed back to stock ROM + Radio and the problem still exists. And Im not the first person this has happened to.
Be weary of the NAND builds, ladies and gentlemen.
From what I understand this can happen under any OS. It has nothing to do with just nand builds. It can happen under a 3rd party 6.5 build, Android SD build, WP7........etc
If the temperature of the phone reaches a certain point you can kiss the touch screen good bye.
This is an issue HTC will repair if u send back. But return everything to stock. It's not the roms its the screen. Android. Rocks
Sent from my HTC HD2 using XDA App
But I wasnt even overclocking it. I was at 990MHz when I ran every build.
It has to be software related.
trill12 said:
But I wasnt even overclocking it. I was at 990MHz when I ran every build.
It has to be software related.
Click to expand...
Click to collapse
Harware related not software.
trill12 said:
But I wasnt even overclocking it. I was at 990MHz when I ran every build.
It has to be software related.
Click to expand...
Click to collapse
I fail to see how flashing a ROM could affect your digitizer in any way (read: it can't).
Just unfortunate coincidence, time to call HTC!
No, it's like blaming Shell for a flat tyre which occurred after you had just filled your tank with their petrol....
Return phone to Factory condition. Contact HTC and send it back. It'll be fine.
trill12 said:
But I wasnt even overclocking it. I was at 990MHz when I ran every build.
It has to be software related.
Click to expand...
Click to collapse
It is related to ignorance and hardware not software.
This is NOT a common occurrence, It can and does happen in ANY OS, Its simply that on those occasions that it actually happens while you are using android you get n00bs posting saying "hey android killed my phone", this simply isnt the case.
Its just pure coincidence that your screen decided to fail whilst you was using android. IF it was an Android issue the forums would be flooded with topics/replies about if from everybody who uses Android. Its like saying, "hey I was using linux in a VM on my machine and my monitor failed, must be software related "
I have been using Android on HD1/HD2 for a year+ and have never experienced any TS failure, even in the early days of android builds when power management was an issue and CPU would heat up, plus ive used countless different builds.
Virginise your phone and sent it to HTC for repair.
Well since you decided to reply in such a condescending matter, Ive been doing IT work for the majority of my life.
If NAND builds do indeed increase the heat, that would be a software related issue. IE, the phone wouldnt overheat unless the software said to.
Pure coincidences of this magnitude are rare. And with the amount of time it took to happen, its more then just a mere coincidence.
Get off your high horse for a second. You arent getting paid for posting, so stop acting like it
trill12 said:
Well since you decided to reply in such a condescending matter, Ive been doing IT work for the majority of my life.
If NAND builds do indeed increase the heat, that would be a software related issue. IE, the phone wouldnt overheat unless the software said to.
Pure coincidences of this magnitude are rare. And with the amount of time it took to happen, its more then just a mere coincidence.
Get off your high horse for a second. You arent getting paid for posting, so stop acting like it
Click to expand...
Click to collapse
and this is exactly why i fix my own computer at work rather than call IT; 2 weeks of trade school in IT programs dont beat my 20 years of computer knowledge as a gamer (build my own rigs) and programmer. most people working IT know very little.
I have to agree......while running a rom for the first time or even after the first couple restarts the phone runs very very hot.....sometimes freezing n only choice left is to pull the battery....but if the phone is still too hot magdlr displays fatal error n wont boot till phone cools off takes a minute or 2....but once the rom settles no more issues.....no such behavior on sd roms.....my experience
Sent from my HTC HD2 using XDA App
These phones are not supposed to be used while they are being charged. Plugging in the USB cable to flash the phone not only charges it but also put the screen on. Then it runs a pretty heavy process. That is almost surely how most (if not all) of these screens are damaged. Do you notice it is almost always right after flashing a build that the screen is damaged and not after using adroidn for a day or so?
How about this? How many users do you think plug their phone into a wall charger and charge at around 800ma, and then play Angry Birds? You want to heat up your phone and damage it try that.
Slightly side note: I do not think NAND builds increase the heat. I actaully they reduce energy consumption (evidence in longer run times). You have to use energy (in this case from the battery) to heat up the phone. NAND uses less current and has longer run times. This should result in a cooler phone on average (assuming the phone stays in this demension ;-))
-Unconnected
All in all, this discussion is irrelevant now. HTC has my phone now (luckily, I live 10 minutes from the Nationwide service center, how quaint) and I should have it repaired by monday.
My experience with this issue
I have been flashing various roms for years here at this site. Including Android Nand Roms here for the last few weeks while they have been available on my HD2 without any issues.
About 5 days ago I installed MDJ's 2.5 (I had previously been using 2.4 with no issue). Right after flashing, the screen would not respond. Went back and tried it again with the same issue. Tried another android rom that had been working fine previously, and the screen would still not respond.
Did a task29 and went back to windows mobile and the screen still would not respond. The hardware buttons always worked.
Finally I started to get some screen response and went back to my NexusHD2-Gingerbread by tytung and was able to restore everything and the screen was fine from then on out.
Thinking it must have been a fluke, the next day I tried it all again. Guess what? Same exact problems happened. Went back to NexusHD2-Gingerbread and it would not respond either. I eventually just started hitting buttons rapidly while hitting the screen and it started to work. Restored everything and the phone (and screen) have been flawless for the last several days.
If this is strictly a hardware problem as several people claim here, it is very unusual.
We'll see what happens from this point forward but I am not convinced it is strictly a hardware issue.
deweylima said:
We'll see what happens from this point forward but I am not convinced it is strictly a hardware issue.
Click to expand...
Click to collapse
IMO it is definitely a hardware issue, maybe affected by excessive flashing/heat/etc but not due to software/roms.
Btw, my own HD2 also suffered from a total defective TS some months ago (phone was about 3 months old) and it happened without any flashing with stock WM6.5 out of the blue. No TS response whatever I did. Had to send it to HTC for warranty repair. Got it back repaired and it's working rocksolid since w/o any issues. ATM I am using Gauners HD-FI nand rom and also used some custom WM6.5 roms before. So....
Just my 2 cents here.
Cheers, Olioaglio
Olioaglio said:
IMO it is definitely a hardware issue, maybe affected by excessive flashing/heat/etc but not due to software/roms.
Btw, my own HD2 also suffered from a total defective TS some months ago (phone was about 3 months old) and it happened without any flashing with stock WM6.5 out of the blue. No TS response whatever I did. Had to send it to HTC for warranty repair. Got it back repaired and it's working rocksolid since w/o any issues. ATM I am using Gauners HD-FI nand rom and also used some custom WM6.5 roms before. So....
Just my 2 cents here.
Cheers, Olioaglio
Click to expand...
Click to collapse
I am not suggesting it is not a hardware issue, but I can't seem to figure why it has happened in this manner.
Screen has been rock solid in the almost one year that I have had the phone.
Twice it has happened right after flashing mdj roms. Once was even via clockwork so there was no usb cable connected (and therefore the battery/heat issue via usb theory doesn't apply).
And then once I finally get it to work again, screen is rock solid again.
If anyone has any ideas or theories, I would love to hear them.
Thanks
deweylima said:
I have been flashing various roms for years here at this site. Including Android Nand Roms here for the last few weeks while they have been available on my HD2 without any issues.
About 5 days ago I installed MDJ's 2.5 (I had previously been using 2.4 with no issue). Right after flashing, the screen would not respond. Went back and tried it again with the same issue. Tried another android rom that had been working fine previously, and the screen would still not respond.
Did a task29 and went back to windows mobile and the screen still would not respond. The hardware buttons always worked.
Finally I started to get some screen response and went back to my NexusHD2-Gingerbread by tytung and was able to restore everything and the screen was fine from then on out.
Thinking it must have been a fluke, the next day I tried it all again. Guess what? Same exact problems happened. Went back to NexusHD2-Gingerbread and it would not respond either. I eventually just started hitting buttons rapidly while hitting the screen and it started to work. Restored everything and the phone (and screen) have been flawless for the last several days.
If this is strictly a hardware problem as several people claim here, it is very unusual.
We'll see what happens from this point forward but I am not convinced it is strictly a hardware issue.
Click to expand...
Click to collapse
Weirdly enough, that was the EXACT SAME ROM I flashed when the touchscreen started dying. I kid you not.
MDJ's build (i think) is already over-clocked. Many times i used his build, my phone heats up fast.I don't know but in my case.this is what i experience. So every time i think my phone is heating. I eventually stop using it and let it rest for a while.Abuse the phone=brick phone.
Is there a way or a tool (Coolant maybe) that we can use so that our phone wouldn't heat up fast? (Couldn't imagine a fan tied to my phone..Haha)
I had my touch screen/phone completely died on me after flashing a nand build. It was fine before nand came out (and i've been flashing for many months now). But, sent it back to tmobile and got a new one. Don't know what the problem was but I had the same issue with OP. Not blaming NAND or anything but yeah...
archiesnet said:
MDJ's build (i think) is already over-clocked. Many times i used his build, my phone heats up fast.I don't know but in my case.this is what i experience. So every time i think my phone is heating. I eventually stop using it and let it rest for a while.Abuse the phone=brick phone.
Is there a way or a tool (Coolant maybe) that we can use so that our phone wouldn't heat up fast? (Couldn't imagine a fan tied to my phone..Haha)
Click to expand...
Click to collapse
Maybe because you have many app's running on the background? I'm using his last rom 2.5 and I'm not experiencing any problems..
My HD2 recently froze, so i decided to pull out the battery, and now it wont turn back on
This is after i upgraded to Android 2.3.5 Gingerbread
How can i fix this?
More info would be really helpful. when did it freeze, during boot, after boot..did it ever boot up correctly and get pass the setup? are you using clk or magldr? can you link to which gingerbread ROM you used? sorry for all the questions but without some more accurate info we would only be taking an educated guess.
So my guess would be that it might just be coininsidense it froze and really the battery is just dead. Magldr does not charge when the phone is turned off so try and get a spare battery if you can to test it out. You might have some luck going into T-mobile and asking them about it only because they might be able to grab a battery out the back to test it for you. If your not using magldr other issues could be a bad download or you flashed the wrong ROM.
I use magldr and i had this problem once, infact it took me several days to get it up and running again. If you do find out its this which hopefully its all it is you can get a spare off ebay rather cheap. I bought three spare batteries plus a wall charger for them for around $10 or so...maybe $15.
Sounds like bent battery pins, which can happen when doing battery pulls.
Take out your battery again and look at the 3 pins that stick out and make sure none are bent and all connect to the battery.
Try this... Pull the battery, plug the phone into the charger, then while plugged in, insert the batter back into the phone.
The same thing just happened to my HD2. It froze so I pulled the battery out and now it wont turn on. The only difference with mine is that I was running stock software. I had not done any tinkering with it at all such as flashing ROMs to it and whatnot. Is it completely dead or could it just be a battery issue?
JosepHenry said:
The same thing just happened to my HD2. It froze so I pulled the battery out and now it wont turn on. The only difference with mine is that I was running stock software. I had not done any tinkering with it at all such as flashing ROMs to it and whatnot. Is it completely dead or could it just be a battery issue?
Click to expand...
Click to collapse
Did you try as I suggested in this thread?
orangekid said:
Did you try as I suggested in this thread?
Click to expand...
Click to collapse
Yes. I tried everything that was suggested but with no luck. =/
JosepHenry said:
Yes. I tried everything that was suggested but with no luck. =/
Click to expand...
Click to collapse
Battery might be fubar, I'd try another one.
To me it sounds like the battery pins if it wasn't for he said it froze, there is no description of when it froze but that it happened after he flashed a new ROM. If it was working fine for several hours and he hadn't pulled the battery out in that time then I would think its something else since it was working at one point. With out a little more info though we are just taking an educated guess...one of many things that could have happened.
Sent from my HTC HD2 using XDA App
htccraze said:
More info would be really helpful. when did it freeze, during boot, after boot..did it ever boot up correctly and get pass the setup? are you using clk or magldr? can you link to which gingerbread ROM you used? sorry for all the questions but without some more accurate info we would only be taking an educated guess.
So my guess would be that it might just be coininsidense it froze and really the battery is just dead. Magldr does not charge when the phone is turned off so try and get a spare battery if you can to test it out. You might have some luck going into T-mobile and asking them about it only because they might be able to grab a battery out the back to test it for you. If your not using magldr other issues could be a bad download or you flashed the wrong ROM.
I use magldr and i had this problem once, infact it took me several days to get it up and running again. If you do find out its this which hopefully its all it is you can get a spare off ebay rather cheap. I bought three spare batteries plus a wall charger for them for around $10 or so...maybe $15.
Click to expand...
Click to collapse
It froze when i was just going through my messages, i am using Magldr,. and the rom is Cyanogen MOD 7 Gingerbread 2.3.5, (TyphooN_CM7_v3.5.8-MAGLDR)
And yes i do have a spare battery, ive tried using new battery, but same problem applies. and the pins are all aligned
htccraze said:
To me it sounds like the battery pins if it wasn't for he said it froze, there is no description of when it froze but that it happened after he flashed a new ROM. If it was working fine for several hours and he hadn't pulled the battery out in that time then I would think its something else since it was working at one point. With out a little more info though we are just taking an educated guess...one of many things that could have happened.
Sent from my HTC HD2 using XDA App
Click to expand...
Click to collapse
Hey thanks for this information... my pins were bent and you saved me some hair pulling!
SOLVED!
orangekid said:
Sounds like bent battery pins, which can happen when doing battery pulls.
Take out your battery again and look at the 3 pins that stick out and make sure none are bent and all connect to the battery.
Click to expand...
Click to collapse
Man, your suggest has just solved my problem! many thanks :angel:
pull out the battery. press the 'on'button for several seconds. press the reset button. plug the phone into charger. insert battery.
that worked for me
I installed the Energy ROM from this thread http://forum.xda-developers.com/showthread.php?t=1528024 a few hours ago and everything worked well. I used the kindle a little and decided to charge it up, so, I plugged in the AC adapter and let it charge for like 1 hour.
When I come back, the adapter is all hot, like unusually hot. The led was red, which means the kindle was charging. Now I unplug it and hit the power button and nothing happens! Nothing, like no led, no nothing. I long-press it and still nothing. I press and let go a couple times and still nothing!
What does this mean? Is my Kindle fried? Because of a ROM!? What can I do now? Please help me
EDIT:
Ok, I fixed the problem. It looks like the Kindle Fire was overheating while connected to the AC adapter. So, I let it lay down a fan for a while and I tried to turn it on and it did. Very dangerous ROM that one, I think I'm going to get CM7 or something until this issue gets fixed.
Unfortunately for now all ICS ROMs have the potential to have that happen if you leave your KF on for extended periods of time when you aren't using it. The widely held solution to that is to shutdown when you know you won't be using it for a while such as while charging or when you go to bed.
If it's fried I don't believe that depends of a rom.... I think it was the fault of the AC adapter...try to charge the KF with another adapter...
jlocohustler said:
I installed the Energy ROM from this thread http://forum.xda-developers.com/showthread.php?t=1528024 a few hours ago and everything worked well. I used the kindle a little and decided to charge it up, so, I plugged in the AC adapter and let it charge for like 1 hour.
When I come back, the adapter is all hot, like unusually hot. The led was red, which means the kindle was charging. Now I unplug it and hit the power button and nothing happens! Nothing, like no led, no nothing. I long-press it and still nothing. I press and let go a couple times and still nothing!
What does this mean? Is my Kindle fried? Because of a ROM!? What can I do now? Please help me
EDIT:
Ok, I fixed the problem. It looks like the Kindle Fire was overheating while connected to the AC adapter. So, I let it lay down a fan for a while and I tried to turn it on and it did. Very dangerous ROM that one, I think I'm going to get CM7 or something until this issue gets fixed.
Click to expand...
Click to collapse
Don't go flaming a ROM when it is a great rom, that is a good way to run a dev off from our community. I have been running the rom since it came out with no issues other than the standard HWA and other listed bugs. Many people have had the same results as me and most of the people who haven't it was because of a bad download and/or a bad flash. The rom is no more dangerous than the general process of rooting and customizing is. Did you get a log cat of what happened at all? Or do any sort of searching for a solution of what caused the issue so on the very slight chance it is a bug it could be fixed?
---------- Post added at 01:36 PM ---------- Previous post was at 01:32 PM ----------
BluesHawk said:
Unfortunately for now all ICS ROMs have the potential to have that happen if you leave your KF on for extended periods of time when you aren't using it. The widely held solution to that is to shutdown when you know you won't be using it for a while such as while charging or when you go to bed.
Click to expand...
Click to collapse
It shouldn't overheat, just freeze and force a hard restart (hold power button for about 20 seconds then turn on). If it is overheating there is something else going on like the AC adapter or some sort of major malfunction from a bad flash. Most likely the AC adapter though.
dnathan13 said:
Don't go flaming a ROM when it is a great rom, that is a good way to run a dev off from our community. I have been running the rom since it came out with no issues other than the standard HWA and other listed bugs. Many people have had the same results as me and most of the people who haven't it was because of a bad download and/or a bad flash. The rom is no more dangerous than the general process of rooting and customizing is. Did you get a log cat of what happened at all? Or do any sort of searching for a solution of what caused the issue so on the very slight chance it is a bug it could be fixed?
Click to expand...
Click to collapse
I believe there's some misconception here. I didn't flame or try to hurt the reputation of the dev or anything. I just posted about an issue and I'm sure, like any other issue, more people must have encountered it. Most people come to find solutions on forums, so, I believe I did the right thing by starting this thread.
Did you even read my OP? I posted an update long before you replied...
EDIT:
AC adapter is fine. Used it just fine on stock ROM before flashing to the new ROM.
jlocohustler said:
I believe there's some misconception here. I didn't flame or try to hurt the reputation of the dev or anything. I just posted about an issue and I'm sure, like any other issue, more people must have encountered it. Most people come to find solutions on forums, so, I believe I did the right thing by starting this thread.
Did you even read my OP? I posted an update long before you replied...
EDIT:
AC adapter is fine. Used it just fine on stock ROM before flashing to the new ROM.
Click to expand...
Click to collapse
Yes I read the op where you claim... "very dangerous rom that one" that is the part that I would say is harsh.
Many people have been running the show rom for days with no issues, but one or two people claiming it will overheat and kill their fire is all it takes for everyone to start bashing a rom and make a dev want to leave.
Sorry I came off as a jerk I just get upset when claims are made based on one bad experience that could have been caused by a number of things (bad flash, left over bits of stock conflicting with rom, lack of knowledge of ICS issues about screen timeout, kernel issue ratjer than rom issue although related, etc...)
Sent from my SPH-D700 using xda premium
No over-heating problems at all for me -- I installed Kang ICS ROM three days ago.
My N10 started to automatically power off a few months ago when the battery indicator showed 10%, and that power-off number gradually increased over the past few months. Two days ago it automatically powered off when the battery was 25%. But the trouble now is that, when plugged in with a power adaptor, the battery does not seem to get charged even though it shows charging when I push the power button. I tried to power it on once, but it automatically powered off again.
Is it an indication that the battery is dead?
Also, when I was trying to remove the battery, I broke some piece around the pins on the orange ribbon cable on the left. What is this cable for? Digitizer? Can this cable be replaced somehow?
Mine started doing the same thing. It only does it if I leave it on standby for a few days. When I start using it, it will say 25% left but it will auto power down immediately. If you plug it in and turn it back on, it says 0%.
Sent from my XT1585 using Tapatalk
Mine started having an issue of not charging, even though it says it is. The battery is currently stuck at 66%. It doesn't shut down on me though. But I powered it off until I could find a solution. I don't think it's a software issue that would be fixed with a factory reset since I tried turning the tablet off overnight and charging it. Still stuck at 66%. When plugged in, it's not discharging. But it doesn't seem to be taking a charge either. Or at least not enough to charge it any higher. My guess is that the battery needs to be replaced. They go for about $30-$40 on ebay. So it looks like that's going to be my best option. I just hope the battery is the issue and I'm not buying a new one for nothing.
After I disconnected the battery for a short while and cleaned the USB port with alcohol, now the battery can be fully charged. However, the orange ribbon cable (under the guy's left hand thumb in this picture http://www.powerbookmedic.com/wordpress/wp-content/uploads/2012/11/nexus10-takeapart-006.jpg) on the left side is broken when I tried to remove the battery. Anyone know what is the cable for? I couldn't find it anywhere (ebay or anywhere else) to buy.
Hi, I had the same problem when did an update to latest cm versions, something around 23.8. And later. I did a rollback to 16.8. CM and charging works, so I am really suspecting latest CM updates for nexus 10 are a root cause of this behaviour. But not tested intensively. Could you try to install older CM versions?
Edit: i havent noticed months ago, I thought few days ago, so my comment is not valid
mark.l said:
Hi, I had the same problem when did an update to latest cm versions, something around 23.8. And later. I did a rollback to 16.8. CM and charging works, so I am really suspecting latest CM updates for nexus 10 are a root cause of this behaviour. But not tested intensively. Could you try to install older CM versions?
Edit: i havent noticed months ago, I thought few days ago, so my comment is not valid
Click to expand...
Click to collapse
I updated my N10 with the August 24 version of CM. Maybe you're right that the battery could be caused by the recent CM version.
mark.l said:
Hi, I had the same problem when did an update to latest cm versions, something around 23.8. And later. I did a rollback to 16.8. CM and charging works, so I am really suspecting latest CM updates for nexus 10 are a root cause of this behaviour. But not tested intensively. Could you try to install older CM versions?
Edit: i havent noticed months ago, I thought few days ago, so my comment is not valid
Click to expand...
Click to collapse
I'm running CM as well. I'll try flashing the newest version. If that's the issue, maybe they have fixed it. If not, I'll try rolling back to an older version and see if that does it and report back. To roll back, do you just simply flash an old version over the existing one? I've never had to go backwards before.
Coming back in here to confirm that my issue was indeed Cyanogenmod. Went back to the last Snapshot and it charged up again.
So I can reinstall Cyanogenmod again without it messing up ?
BackDaws said:
So I can reinstall Cyanogenmod again without it messing up ?
Click to expand...
Click to collapse
Yeah, just flash the latest snapshot. I think the date is 8/20
jsgraphicart said:
Coming back in here to confirm that my issue was indeed Cyanogenmod. Went back to the last Snapshot and it charged up again.
Click to expand...
Click to collapse
How to report it? I am not sure what version does not have this issue. Still running on older version. When having time, Ill try September's version.
mark.l said:
How to report it? I am not sure what version does not have this issue. Still running on older version. When having time, Ill try September's version.
Click to expand...
Click to collapse
Go check out the Nexus 10 cm13 thread. There's a lot of talk about it already
jsgraphicart said:
Go check out the Nexus 10 cm13 thread. There's a lot of talk about it already
Click to expand...
Click to collapse
Hi, thanks, found it and the yalready have JIRA issue for tracking the fix
so we can close this thread I assume as all of us are happy that CM caused drainig our batteries