Has anyone else seen this? Battery has a good charge, but suddenly drops to zero.... running TWA_privs latest ROM
Sent from my Amazon Kindle Fire using xda premium
Did you calibrate the battery after the ROM install?
guitarman2010 said:
Did you calibrate the battery after the ROM install?
Click to expand...
Click to collapse
No, haven't done that before. Is this done in recovery?
Sent from my Amazon Kindle Fire using xda premium
When you wipe dalvik cache this is usually taken care of. Maybe you need a new battery.
Logically it doesn't make sense for a battery to instantly lose that much charge, and a bad connection wouldn't explain why it would continue to charge from zero. I think what most likely happened is the OS wasn't reporting the battery level correctly, and as a result, died with no warning.
You're running a mod on twa_priv's ROM which may make report inaccurate or cause something to go rogue such as battery stats. Test a clean flash without the mod to see if there is any effect.
Thepooch said:
You're running a mod on twa_priv's ROM which may make report inaccurate or cause something to go rogue such as battery stats. Test a clean flash without the mod to see if there is any effect.
Click to expand...
Click to collapse
You are correct, I'll try that and check back. Been running the theme for some time though without this issue... strange!
Sent from my Amazon Kindle Fire using xda premium
Thepooch said:
You're running a mod on twa_priv's ROM which may make report inaccurate or cause something to go rogue such as battery stats. Test a clean flash without the mod to see if there is any effect.
Click to expand...
Click to collapse
Okay, clean install done. I'll let you know if the problem comes back.....
Sent from my Amazon Kindle Fire using xda premium
bflobills said:
Okay, clean install done. I'll let you know if the problem comes back.....
Sent from my Amazon Kindle Fire using xda premium
Click to expand...
Click to collapse
Update; clean install of priv's 11/08 build with no theme installed, and still getting a sudden crash to zero charge...
Time for a new battery?
Sent from my Amazon Kindle Fire using xda premium
Could be it does seem very strange. I take it that you have not rebooted during this time period? I have noticed small drops after a reboot but not an utter dive to 0 that you are getting.
Thepooch said:
Could be it does seem very strange. I take it that you have not rebooted during this time period? I have noticed small drops after a reboot but not an utter dive to 0 that you are getting.
Click to expand...
Click to collapse
No reboots, just left on all the time. Only thing I'll say is that this problem seemed to coincide with me using an Amazon 9w charger (made for the KF however).
Perhaps I'll go back to the stock charger and monitor again.
Here is the charger I am using;
Amazon Kindle PowerFast for Accelerated Charging (not included with device, for use with the Kindle Fire or Kindle Fire HD models) http://www.amazon.com/dp/B006GWO5WK/ref=cm_sw_r_an_am_ap_am_us?ie=UTF8
Sent from my Amazon Kindle Fire using xda premium
Not intended for the 1st gen kindle. Fast charge, fast drop, wrong charger, wrong charge. Makes sense and could equal damage to the battery itself.
Related
See this thread：http://forum.xda-developers.com/showthread.php?p=31538978#post31538978
Question : can we update our 1st Kindle Fire's 6.3.1 Rom?
I will try it!
We wait for results gl
Amazon Kindle Fire - CM10
It won't work out the box, already tried. It's partitioned differently.
Iced666 said:
We wait fo results gl
Amazon Kindle Fire - CM10
Click to expand...
Click to collapse
it's exciting!
i can't waiting any seconds!
read post number 12 http://forum.xda-developers.com/showthread.php?t=1881476
I might attempt to port when I get home.
Edit: I decided not to try...I have other things I have to do.
powerpoint45 said:
I might attempt to port when I get home.
Click to expand...
Click to collapse
waiting for your results!
I DON'T know many about MLO and xloader partition what's in the update-script.
I wonder whether we can modify the update-script according to 6.3.1's ?
Please don't try flashing the original Amazon 2nd gen file. I'll see what I can do w/ the ROM using our existing 3.0 kernel when I get time.
It would be even more fantastic if you guys might can use the new ics stock's kernel to fix the charging detector problem, it's ics right? Is it possible?
Hashcode said:
Please don't try flashing the original Amazon 2nd gen file. I'll see what I can do w/ the ROM using our existing 3.0 kernel when I get time.
Click to expand...
Click to collapse
Thanks hashcode!
I had learnt many things from you!
Can you give me some advise to modify the updater-script of the 2nd gen file?
it needs to flash MLO, needs to read xloader partition.
shahabk818 said:
It would be even more fantastic if you guys might can use the new ics stock's kernel to fix the charging detector problem, it's ics right? Is it possible?
Click to expand...
Click to collapse
it's hard work.
maybe i must give up!
i don't know anything about MLO.
wait till amazon pushes the 1st gen the update. I'm sure they will just package it with the 3.0 kernel and send it out very soon
Sent from my Kindle Fire
shravbits said:
wait till amazon pushes the 1st gen the update. I'm sure they will just package it with the 3.0 kernel and send it out very soon
Sent from my Kindle Fire
Click to expand...
Click to collapse
This is what I'm waiting for myself. The differences in hardware and partition table make this an exercise in futility when a device specific version is probably not to far off.
Sent from my LG-P999 using xda app-developers app
shravbits said:
wait till amazon pushes the 1st gen the update. I'm sure they will just package it with the 3.0 kernel and send it out very soon
Sent from my Kindle Fire
Click to expand...
Click to collapse
Im pretty sure admin isn't going to update the original fires, performance wise with their skinned android it will most likely cause way too many issues
cm9 lg-lg855
k28king1 said:
Im pretty sure admin isn't going to update the original fires, performance wise with their skinned android it will most likely cause way too many issues
cm9 lg-lg855
Click to expand...
Click to collapse
I don't think the would update the 1th generation at least not for now
They want to sell the new ones, hashcode is working on porting it, just if he does some magic!
shahabk818 said:
I don't think the would update the 1th generation at least not for now
They want to sell the new ones, hashcode is working on porting it, just if he does some magic!
Click to expand...
Click to collapse
it will be nice to try something new for the kindle fire 1st gen
I also do not think Amazon will do anything for kindle fire. It is simply not an aspect of their business plan. You and I play with the hardware like it is hardware. Amazon is looking at sales from subscribers. This is why a diminished is works for them, but not for us.
Sent from my Amazon Kindle Fire using xda app-developers app
Ixthusdan said:
I also do not think Amazon will do anything for kindle fire. It is simply not an aspect of their business plan. You and I play with the hardware like it is hardware. Amazon is looking at sales from subscribers. This is why a diminished is works for them, but not for us.
Sent from my Amazon Kindle Fire using xda app-developers app
Click to expand...
Click to collapse
That might actually be in our favour, if they are selling the fire at the bare minimum price and their target is selling their digital goods, then they have no reason not to continue to cater to all their user base. Since better software makes users more inclined to just stick with Amazon and continue consuming.
Of course one never knows, so take this as just my 2 cents.
Can anybody just get the apps to install just the launcher on cm9? That is all that I want.
Sent from my Kindle Fire using xda app-developers app
2390 said:
Can anybody just get the apps to install just the launcher on cm9? That is all that I want.
Sent from my Kindle Fire using xda app-developers app
Click to expand...
Click to collapse
Yes It would be great if you make tutorial of how to run the amazon launcher on cm10-cm9... since hashcodes kernel is stable now i don't want to move to anything else
Don't know what happened, my phone has been going strong with a the SuperGalaxy rom 1.7 with no problems. I recently updated to 1.8 and it ran fine for the past two days with no problems. Then after leaving the phone on the charger at work yesterday, the phone kept resetting randomly. I unplugged it, hard reset, flashed a different rom, everything, and it still keep resetting randomly. Not sure what the problem is, any suggestions?
Edit: I'm a dumbass, realized my cpu was under clocked to 800mhz, running smooth at 1400mhz now.
okay, i'm not a dumbass (maybe). Phone keeps resetting on its own randomly still but less frequently after I overclocked.
How is your battery condition? Like how old is it? Do you have and tweaks (kobridge or phakker scripts)
Cpusleep app? And you said it happens on a few ROMs, I would say it maybe a battery or hardware issue. Also, do you check the MD5 sums before you flash the different ROMs?
Sent from my SPH-D710 using XDA
Battery condition is good, I actually have two oem batteries that I use daily and swap them when one dies.
I'm not running any tweaks currently, but when I flashed the roms recently its been through a nandroid backup of my previous working rom. But I'll try a clean install without a backup and see if that works. Thanks
Sent from my SPH-D710 using xda premium
Okay, just did a fresh clean install from recovery. The phone still resets, I've noticed if it's plugged in to a charger though instead of resetting it will just turn off and show me the battery charging screen.
Also, how do you check the MD5 sums? I always thought the phone recovery automatically checks this before it flashes a rom?
Sent from my SPH-D710 using xda premium
Subiegsr said:
Okay, just did a fresh clean install from recovery. The phone still resets, I've noticed if it's plugged in to a charger though instead of resetting it will just turn off and show me the battery charging screen.
Also, how do you check the MD5 sums? I always thought the phone recovery automatically checks this before it flashes a rom?
Sent from my SPH-D710 using xda premium
Click to expand...
Click to collapse
Are you using a stock battery charger? Is the charging cable damaged or loose? I had an issue with an after market charger making my phone freeze up before.
Not to my knowladge, but it never hurts to check it. I use md5sum app.
Sent from my SPH-D710 using XDA
Okay, I flashed a totally different ROM and it seemed to have solved the problem for now. Most likely it was a ROM issue, which is kind of weird since it was using the same rom before without any issues, even when I did a recovery of it. Oh well, maybe it was the right combination of apps and crap. But so far right now, everything is good. Thanks for the help g_ding84!
What were you using to under/overclock? Setcpu specifically has been known to cause the exact issue you were having, namely random reboots, however I would not be shocked to find other overclocking utilities that could cause the same problem. Regardless I'd be willing to bet that whatever you were were using to adjust the clock speeds was the source of the issue as opposed to the ROM.
Sent from my SPH-D710 using Tapatalk 2
Subiegsr said:
Okay, I flashed a totally different ROM and it seemed to have solved the problem for now. Most likely it was a ROM issue, which is kind of weird since it was using the same rom before without any issues, even when I did a recovery of it. Oh well, maybe it was the right combination of apps and crap. But so far right now, everything is good. Thanks for the help g_ding84!
Click to expand...
Click to collapse
No problem, just wanna find out the root cause of the reboots.
Sent from my SPH-D710 using XDA
---------- Post added at 11:29 PM ---------- Previous post was at 11:26 PM ----------
cp320703 said:
What were you using to under/overclock? Setcpu specifically has been known to cause the exact issue you were having, namely random reboots, however I would not be shocked to find other overclocking utilities that could cause the same problem. Regardless I'd be willing to bet that whatever you were were using to adjust the clock speeds was the source of the issue as opposed to the ROM.
Sent from my SPH-D710 using Tapatalk 2
Click to expand...
Click to collapse
You may be right on the money with that. It could be causing script confliction. Between the ROM and the CPU app. But I do know that cpu app scripts will override the ROMs cpu scripts, but not all the time.
Sent from my SPH-D710 using XDA
Subiegsr said:
Don't know what happened, my phone has been going strong with a the SuperGalaxy rom 1.7 with no problems. I recently updated to 1.8 and it ran fine for the past two days with no problems. Then after leaving the phone on the charger at work yesterday, the phone kept resetting randomly. I unplugged it, hard reset, flashed a different rom, everything, and it still keep resetting randomly. Not sure what the problem is, any suggestions?
Edit: I'm a dumbass, realized my cpu was under clocked to 800mhz, running smooth at 1400mhz now.
Click to expand...
Click to collapse
This has been happening to me all day today even after Changing roms and removing every tweak related app. It even reboots inside the recovery menu wtf
Sent from my SPH-D710 using xda app-developers app
FuMMoD said:
This has been happening to me all day today even after Changing roms and removing every tweak related app. It even reboots inside the recovery menu wtf
Sent from my SPH-D710 using xda app-developers app
Click to expand...
Click to collapse
I would bring your battery in sprint. You may need a new one.
Sent from my SPH-D710 using XDA
g_ding84 said:
I would bring your battery in sprint. You may need a new one.
Sent from my SPH-D710 using XDA
Click to expand...
Click to collapse
I have 3 OEM and 4 extended they all do the same thing.
Sent from my SPH-D710 using xda app-developers app
You might try this thread...
http://forum.xda-developers.com/showthread.php?t=1916817
tysonrj said:
You might try this thread...
http://forum.xda-developers.com/showthread.php?t=1916817
Click to expand...
Click to collapse
Thank you very much. I didnt know this was an issue with the phone.
FuMMoD said:
This has been happening to me all day today even after Changing roms and removing every tweak related app. It even reboots inside the recovery menu wtf
Sent from my SPH-D710 using xda app-developers app
Click to expand...
Click to collapse
Does it reboot in download mode? If not..I would odin to stock and go from there see if that fixes things.
Update: still resetting. :crying:
Today its been resetting probably about once every few minutes to ten minutes. It's stupid, like the battery will say 60% and when it reboots on its own, the battery will be at like 10%. No idea what the issue may be, but I might try to see if it will reboot in download mode as some of you suggest and maybe try to flash a stock rom. It seems that when it does go in reboot crackhead mode it will do it even in recovery.
The power button will not be as functional during the crackhead reboot mode as well. I'll press it and nothing will happen, but the screen will come on itself (not sure if this is a delay or just the screen coming on by itself lol).
I'm not too worried about exchanging it as of now, since I'm in the market for a new phone, but would like to fix this issue so I can sell the phone; if not I'll just do the trade in thing with Sprint (even though I won't get as much).
Subiegsr said:
Update: still resetting. :crying:
Today its been resetting probably about once every few minutes to ten minutes. It's stupid, like the battery will say 60% and when it reboots on its own, the battery will be at like 10%. No idea what the issue may be, but I might try to see if it will reboot in download mode as some of you suggest and maybe try to flash a stock rom. It seems that when it does go in reboot crackhead mode it will do it even in recovery.
The power button will not be as functional during the crackhead reboot mode as well. I'll press it and nothing will happen, but the screen will come on itself (not sure if this is a delay or just the screen coming on by itself lol).
I'm not too worried about exchanging it as of now, since I'm in the market for a new phone, but would like to fix this issue so I can sell the phone; if not I'll just do the trade in thing with Sprint (even though I won't get as much).
Click to expand...
Click to collapse
Trade in is roughly $80 bucks (i'm looking to do that with mine this weekend hopefully for the S3) Sorry your having issues.. Mine has done it once ina great while.. but nothing crazy. Good luck on new phone! (I'm a craigslist junky so i'll shop on there for temp replacements lol) Got my Touch for $50 which was an upgrade from my OG Epic.
milky1112 said:
Trade in is roughly $80 bucks (i'm looking to do that with mine this weekend hopefully for the S3) Sorry your having issues.. Mine has done it once ina great while.. but nothing crazy. Good luck on new phone! (I'm a craigslist junky so i'll shop on there for temp replacements lol) Got my Touch for $50 which was an upgrade from my OG Epic.
Click to expand...
Click to collapse
Thanks man. It started doing it today and I took out the SD card and it hasn't done it since. So maybe it was the SD card this whole time?
Hopefully it is.
Sent from my SPH-D710 using xda premium
This is the second Fire I've had where the contacts went bad. Now I have a rooted modded fire and can't send it back. What gives with the way it went bad again? Design flaw? Bad luck? Misuse (I often use it while its plugged in and its hard to not apply pressure to the cord.
Anybody w/ experience messing with the case/contacts/etc. Want to give me some advice or how to fix this?
sent from my original Kindle Fire masquerading as a Galaxy Nexus
Any time a structure is mounted to the board, this problem can occur. The way to avoid it is to mount the port on the case or some other way and use connectors to the board. This requires more space and increased production costs. So, it is simply a design flaw, but not a design intent. The fix is actually a solder on the board, a skill I certainly do not have!
Sent from my Amazon Kindle Fire using xda app-developers app
Josepho1997 said:
What are the contacts? And you can always flash the 6.3.1.zip file from amazon, and then do a factory reset. That will unroot you and delete TWRP and FFF.
Sent from my Kindle Fire
Click to expand...
Click to collapse
I mean the contacts where the charger plugs in. I may do the flash/return bit but what a pain lol! I was hoping someone had this problem and fixed it themselves - you know just straightening a contact or something. I'm grasping at straws here. SORRY!
sent from my original Kindle Fire masquerading as a Galaxy Nexus
Ixthusdan said:
Any time a structure is mounted to the board, this problem can occur. The way to avoid it is to mount the port on the case or some other way and use connectors to the board. This requires more space and increased production costs. So, it is simply a design flaw, but not a design intent. The fix is actually a solder on the board, a skill I certainly do not have!
Sent from my Amazon Kindle Fire using xda app-developers app
Click to expand...
Click to collapse
Thanks. Makes perfect sense. Sounds like I'll need to return to stock and try to get Amazon to fix/replace it. Yuck.
sent from my original Kindle Fire masquerading as a Galaxy Nexus
Yeah be very careful on your return to stock do that order specific wipe before flashing update.zip its not a bad idea to flash Modaco first then wipe all to flash update.zip it could make the transition smoother here is Modaco http://forum.xda-developers.com/showthread.php?t=1439916 not the altrom sharonbw that is for dual booting.
Thepooch said:
Yeah be very careful on your return to stock do that order specific wipe before flashing update.zip its not a bad idea to flash Modaco first then wipe all to flash update.zip it could make the transition smoother here is Modaco http://forum.xda-developers.com/showthread.php?t=1439916 not the altrom sharonbw that is for dual booting.
Click to expand...
Click to collapse
Thank you very much! I discovered I have exactly one month left on my warranty so back it goes!
This is actually the 2nd time I've had to send it back for the same reason. I thought it was a fluke the first time. Now that I understand the problem I'm surprised it doesn't happen to everybody!
sent from my original Kindle Fire masquerading as a Galaxy Nexus
I've had my Kindle Fire replaced and want to stick with stock ROM so I can use Kindle Launcher/Reader (it's rooted with googleapps installed). However I find that a lot of my apps from Google Play claim to be incompatible with my device. I previously changed its "appearance" to galaxy nexus on my JB ROM but I can't get it to work on this ROM. Am I really forced to choose between Google and Amazon? D*MN THEM!
EDIT: I realized I had MoDaCo before. I flashed it on this device and Googleplay "sees" me now. I think as a galaxy tab. Nice.
Sent from my Kindle Fire using xda app-developers app
sharonbw said:
I've had my Kindle Fire replaced and want to stick with stock ROM so I can use Kindle Launcher/Reader (it's rooted with googleapps installed). However I find that a lot of my apps from Google Play claim to be incompatible with my device. I previously changed its "appearance" to galaxy nexus on my JB ROM but I can't get it to work on this ROM. Am I really forced to choose between Google and Amazon? D*MN THEM!
Sent from my Kindle Fire using xda app-developers app
Click to expand...
Click to collapse
For curiosity's sake, what software version is your new Kindle Fire running?
soupmagnet said:
For curiosity's sake, what software version is your new Kindle Fire running?
Click to expand...
Click to collapse
6.3.1 (MoDaCo Gr9)
Sent from my Kindle Fire using xda app-developers app
sharonbw said:
6.3.1 (MoDaCo Gr9)
Sent from my Kindle Fire using xda app-developers app
Click to expand...
Click to collapse
Okay, so they are still replacing 1st gen. with 1st gen. Good to know.
Alright, As the title says I'm having a battery issue. I just bought the phone used, unlocked it, Flashed CM 10.1, and ever since changing ROMs the battery hasn`t gone down below 100%. I've let the battery go flat, wipe Battery_stats.bin. Issue remains un resolved. I also tried to recalibrate using an app, still no improvement. Any ideas on how it can be fixed? Anyone out there having same/similar problems?
EDIT: Also, I`m rooted & have CWM installed.
let me get this straight
your battery is always full?
Try With Change Your Kernel. But Must Match with Recomendation ROM Kernel.
Sent from my ST15i using xda premium
raymuy said:
let me get this straight
your battery is always full?
Click to expand...
Click to collapse
So it claims to be, But isn't, I wish it was an eternal battery! That'd be awesome
SigitCGumilars said:
Try With Change Your Kernel. But Must Match with Recomendation ROM Kernel.
Sent from my ST15i using xda premium
Click to expand...
Click to collapse
Alright, Is there a thread or tutorial i could follow? Thanks for the help!
This happened yesterday, I had the usual random freeze on my phone. Thought I just had to wait for it to restart, but this time it didn't. So I had to pull the battery out, and power it on from there.
Only, it didn't want to. No matter how long I press the power button, no response. I can't get into recovery or download mode. I have a spare stock battery and it won't power up with that too. The phone does however, heat up when the battery is inside. I tried leaving it without the battery overnight and then placing the battery back, but still no luck.
My phone is rooted, running AOSPAL ParanoidAndroid (4.3), with fancy kernel.
I hope someone can help me, and I hope my phone isn't bricked.
That happened to me once and yes, the phone was briked...
Just bricked randomly? No real cause?
Sent from my Galaxy Nexus using xda app-developers app
frimpasi said:
That happened to me once and yes, the phone was briked...
Click to expand...
Click to collapse
was it random just like mine?
kalizu said:
was it random just like mine?
Click to expand...
Click to collapse
Yep...
kalizu said:
This happened yesterday, I had the usual random freeze on my phone. Thought I just had to wait for it to restart, but this time it didn't. So I had to pull the battery out, and power it on from there.
Only, it didn't want to. No matter how long I press the power button, no response. I can't get into recovery or download mode. I have a spare stock battery and it won't power up with that too. The phone does however, heat up when the battery is inside. I tried leaving it without the battery overnight and then placing the battery back, but still no luck.
My phone is rooted, running AOSPAL ParanoidAndroid (4.3), with fancy kernel.
I hope someone can help me, and I hope my phone isn't bricked.
Click to expand...
Click to collapse
Generally speaking if the device doesn't even power up, then yes its bricked. sorry to tell you my friend. The main part of the device that powers up initially is the main bootloader in the logic board, so what has happened most likely is it just failed. kinda of like the bios on a pc. if the bios fails, then the computer can no longer be told to turn on.
Try omap flash..
Sent from my Galaxy Nexus using XDA Premium HD app
mrgnex said:
Try omap flash..
Sent from my Galaxy Nexus using XDA Premium HD app
Click to expand...
Click to collapse
Already tried that. I just get stuck on a failed operation. Something about an EMMC driver missing. Would you happen to know a solution to that?
kalizu said:
Already tried that. I just get stuck on a failed operation. Something about an EMMC driver missing. Would you happen to know a solution to that?
Click to expand...
Click to collapse
http://lmgtfy.com/?q=omap+4460+driver
Sent from my Galaxy Nexus using XDA Premium HD app