I got a gTab from TD the other day and I wanted to play around with stock for a bit(the horror) anyways...Its using 4039 my guess as I went to update and it say I have latest version and saw mentions of 4039. I never flashed anything to it yet..
= summary of usage =
I turned it on early before charging and to my surprise it had 0 battery life(unhealthy for the battery), which is weird as batteries are suppose to be around 25% - half charged..so anyways I connected it to the outlet and then powered it on, once it got to ~100% I took it off and used it, afterwards I pressed power button and left, when I came back I pressed power and realized it shut itself off and by that I mean completely off not screen (is this normal?)..throughout the day I realize that it kept shutting itself off after some time..
= end summary =
To the point, I last time I turned it on and it goes on to the birds and gtablet screen and then just shuts off, I can get into recovery and I tried wiping cache and factory reset to no avail, I am guessing next step is NVFlash but is this normal? or do I have a defective unit? (battery is 100%)
Edit: I just ran a downgrade.zip and it started working...but still is the behavior normal? out of curiosity is there a way to check if device is refurbished?
(1) Only you can know if you have a refurb device. Just look for some signs like scratches.
(2) I highly recommend nvflash. If the problem doesn't go away, then perhaps you really do have a defective product.
(3) One possibility is you have a severe case of the sleep of death. This can be solved by flashing a custom kernel. I highly recommend Klemsyn's kernel. He really worked hard on it to stop the sleep of death issue.
(4) Don't forget to repartition to 2048/0 after you put in cwm. This preemptively stop the force closing issue.
(5) Don't forget that 1.1 requires cwm v8 and 1.2 requires cwm 3052 (or something like that, can't remember the number). You will semi-brick your device if you use the wrong version and you will totally brick your device if you flash the wrong branch.
(6) Good luck.
Added by edit.
Me running honeycomb. Me loves it.
goodintentions said:
(1) Only you can know if you have a refurb device. Just look for some signs like scratches.
(2) I highly recommend nvflash. If the problem doesn't go away, then perhaps you really do have a defective product.
(3) One possibility is you have a severe case of the sleep of death. This can be solved by flashing a custom kernel. I highly recommend Klemsyn's kernel. He really worked hard on it to stop the sleep of death issue.
(4) Don't forget to repartition to 2048/0 after you put in cwm. This preemptively stop the force closing issue.
(5) Don't forget that 1.1 requires cwm v8 and 1.2 requires cwm 3052 (or something like that, can't remember the number). You will semi-brick your device if you use the wrong version and you will totally brick your device if you flash the wrong branch.
(6) Good luck.
Added by edit.
Me running honeycomb. Me loves it.
Click to expand...
Click to collapse
yeah I figured out all of that the hard way that day lol..also running honeycomb now ..though too bad no hardware video decode...had to bump up to 1.5ghz to have it stop lagging in 720p mkvs...still subtitles seem to be a bit off :/
So, I've rooted my TF and been running the latest Revolver ROM for about a week. Everything ran awesome with very few flaws. I also recently RMA'd my dock for the sleep issue and just got it back yesterday.
I hooked up the dock to my TF and it ran great all last night and this morning. Everything charged just fine. I packed it up to take to work, took it out at work and...nothing.
My TF would not wake from sleep. I thought maybe I had suddenly encountered the sleep of death issue that I had heard about but never experienced, so I held in the power button and restarted.
The TF restarted just fine. Booted past the first screen and the custom animation screen. But as soon as it was supposed to boot into the homescreen, it goes blank. The TF is on as I can hear email notifications and stuff, but there is nothing on the screen. I tried booting and re-booting with the same result.
So I wiped cache. Same result.
After getting an MD5 Checksum error from the one backup I had of my system through CWM, I wiped data/factory reset. I actually got past the boot animation and started setting up my TF again. However, the screen was set to auto-bright (I like it at fairly bright) so I started to adjust it. As soon as I touched the brightness controls, the screen went black. TF still on, just no screen.
I booted back into recovery again, wiped data/factory reset again and again it booted up just fine and took me to setup. Went to adjust brightness in the actual settings menu and as soon as my finger touched the brightness bar, the entire screen went black.
WTF? Has anyone else gotten similar experience with your TF, either rooted with a new ROM or not? Not a whole lot I can do with a tablet with no screen.
Here are the things it is not based on my observations:
1. It is not a dead screen. On boot up, the screen works. Animation plays well. I can access the CWM recovery menu.
2. It's not a dead touch screen. I can factory reset and go into the setup using the touchscreen.
Here are the things I suspect it COULD be:
1. Something up with the Revolver ROM. I had refrained from applying the 2.1.1 update as the update immediately after that just reverts it back to the version before the 2.1.1. update. However, I did apply the update after the second time of factory resetting.
2. Something up with my dock/dock software? I didn't have any of this issue before I received my dock back.
Please, can anyone help me out here? Sorry for the long post, but wanted to include as many details as possible.
Does the issue occur not docked? Can you use the dock brightness buttons to bring back the screen?
It happens both docked and undocked . Dock brightness buttons do nothing.
I left the tablet alone for about twenty minutes and when I came back the screen was on. Brightness was at max. But again as soon as I touched the brightness controls no screen.
Sent from my DROIDX using XDA App
Actually (after wiping and restarting yet again) I found that even the dock brightness buttons cause the screen ti go blank.
Sent from my DROIDX using XDA App
Okay so after searching high and low for others with this issue i found two unresolved threads. It seems to be a software problem that will not allow the backlight to go beyond 50% brightness when not plugged into the charger. I'm at work now so I can't test this for sure until I go home later this evening. If this is the case, then it could be a problem with my root and ROM installation. I will try the following things in order.
1. Restore from backup done right after I gained root access. This is basically my system with the original software. After gaining root, I did delete some things through Titanium Backup that I felt were bloatware. This might have had something to do with it so restoring the original backup should return these things to their normal state. The only problem with this is that when I tried to restore from recovery, the MD5 checksum gave me an error. I have found a thread that allows you to override using ADB and will try once I get home.
2. Unroot completely and flash back to stock. It worked when I was unrooted and stock, so theoretically it should work again.
3. If the above two methods don't work, I'll just RMA it back to ASUS. I already called in and got an RMA number for the issue. At least by doing the above two things I can ready the tablet to be within warrany specs in case it's just a dud and needs to be replaced.
Will update with results.
Results
1. When plugged into the charger (with or without the dock) I can up my tablet to full brightness just as the other couple of threads I read stated. Even with brightness up at full and running on battery (blank screen) there is still HDMI out. Wish I had realized this BEFORE I did a complete data wipe.
2. Had to use terminal emulator and the following link to recover the CWM backup with the checksum error: http://forums.androidcentral.com/epic-4g-rooting-roms-hacks/70519-md5-sum-mismatch.html
It worked awesomely to bring my precious tablet back to stock with all applications I ran previously. Still no change in the brightness issue though
Now on to try to unroot and see what I get...
sounds like you're taking the right steps.
I hope so Malandro2011.
Looks like I will have to RMA after all. I unrooted, went back to stock recovery and a completely new install of the most current firmware. No dice. The issue is still there.
My tablet's all packed up and ready to ship off to the god awful Texas facility for repair/replacement. Since they sent my dock back with a bend in the metal near the adapter port, I made sure to take pictures of the entire tablet before replacement as well as leaving a note to them under the RMA slip about the condition of the tablet when I shipped.
My biggest question is what triggered this to happen. Was it rooting and installing a new ROM? So many people have done this without incident it is hard to believe this was the problem. Was it whatever changes they made to my dock? I was running smoothly for a week before charging it in the dock overnight.
many people have rooted and your the first I've heard with this particular issue so i doubt these roms caused it...but could be wrong.
Seems power related since adjusting the brightness sends more power to the screen or less then the screen fails.
I reckon its just faulty...
I wonder if they'll replace it with the newer models that cant be rooted yet..
Yeah, I agree it seems power related. My unsubstantiated theory is that when they adjusted the I/O board in the dock, perhaps it changed some of the power settings and caused some sort of overload/short in my tablet when I used the dock.
Such a shame to send it back. It was one of the earliest models and beyond this was one with the fewest problems. No light bleed, no stuck pixels, no sleep of death, good QC on the hardware. Here's hoping that what I receive back will be just as good (and hopefully not one of the unrootable new models).
Update for anyone following this thread. Received my repaired TF two days ago. Total away time was around 2weeks. It looks like hey had to replace the entire screen. Looks nice with even less lightbleed than before but the screen has a faint yellow tint that I have heard is common with later model TFs. Not sure if I should send back again as I really don't want it gone for any longer time...
I will pay FIFTY DOLLARS ($50.00) to the person or team that provides a solution to this problem.
After swapping batteries in my Droid Charge, I often (but not always) get a huge number of force close crashes when it boots up. The apps that usually force close on reboot are Google Docs, FlexT9 keyboard, GoSMS Pro and App Protector.
My phone is running Imnuts's Infinity Rom 1211, plus his battery addin and his widgets. However, this problem also existed when I was running Gummy Charged 2.1.
I own several batteries. In fact, I own seven of them. I have a drop-in charger at home, at work and in my car. There's always at least one fresh battery at all locations. I mention this because I realize that there is something about "battery stats" that you can wipe (using CWM Recovery). Maybe the phone is not smart enough to keep track of so many unique batteries?
When I swap a battery and then I get an a~~load of force close crashes, the phone will come up as though the ROM had just been installed. It asks me for my Google Account info just like it was being configured for the very first time.
When this happens, I have to reconfigure my two Google accounts (home and work), let it resync all the data on those two accounts, then reinstall many applications.
I asked about this once when I was still running Gummy Charged and the suggestion came back that it was a software issue that could most easily be remedied by changing to a newer ROM. The poster said that Gummy Charged wasn't being actively supported anymore, but Infinity was and suggested I go that route.
Q. -- What sort of process / event related to swapping batteries (or merely rebooting) could cause the phone to come up like it's never been configured before?
Whenever I install a ROM, I always wipe the Dalvik Cache and wipe the internal SD (but not the 32 gb removable SD card). Whenever I move from one ROM to another ROM, I always fall back to factory stock first. Any time I installed Infinity ROM, I received no errors of any kind (and same for when I installed other ROMs in the past).
When my phone works correctly, I really like the Droid Charge. When it doesn't, I want to take a large cache of weapons and ammunition to a postal facility. I can't tolerate this any longer. I have to solve the problem (forever) or I have to give up and buy another phone.
FIFTY BUCKS BY PAYPAL FOR THE SOLUTION.
SoonerLater said:
I will pay FIFTY DOLLARS ($50.00) to the person or team that provides a solution to this problem.
After swapping batteries in my Droid Charge, I often (but not always) get a huge number of force close crashes when it boots up. The apps that usually force close on reboot are Google Docs, FlexT9 keyboard, GoSMS Pro and App Protector.
My phone is running Imnuts's Infinity Rom 1211, plus his battery addin and his widgets. However, this problem also existed when I was running Gummy Charged 2.1.
I own several batteries. In fact, I own seven of them. I have a drop-in charger at home, at work and in my car. There's always at least one fresh battery at all locations. I mention this because I realize that there is something about "battery stats" that you can wipe (using CWM Recovery). Maybe the phone is not smart enough to keep track of so many unique batteries?
When I swap a battery and then I get an a~~load of force close crashes, the phone will come up as though the ROM had just been installed. It asks me for my Google Account info just like it was being configured for the very first time.
When this happens, I have to reconfigure my two Google accounts (home and work), let it resync all the data on those two accounts, then reinstall many applications.
I asked about this once when I was still running Gummy Charged and the suggestion came back that it was a software issue that could most easily be remedied by changing to a newer ROM. The poster said that Gummy Charged wasn't being actively supported anymore, but Infinity was and suggested I go that route.
Q. -- What sort of process / event related to swapping batteries (or merely rebooting) could cause the phone to come up like it's never been configured before?
Whenever I install a ROM, I always wipe the Dalvik Cache and wipe the internal SD (but not the 32 gb removable SD card). Whenever I move from one ROM to another ROM, I always fall back to factory stock first. Any time I installed Infinity ROM, I received no errors of any kind (and same for when I installed other ROMs in the past).
When my phone works correctly, I really like the Droid Charge. When it doesn't, I want to take a large cache of weapons and ammunition to a postal facility. I can't tolerate this any longer. I have to solve the problem (forever) or I have to give up and buy another phone.
FIFTY BUCKS BY PAYPAL FOR THE SOLUTION.
Click to expand...
Click to collapse
are all these batteries OEM (Samsung made for the Charge) ones? I wouldn't know even where to begin for a fix as I've never heard of this before... the only issue I could see would be if they were third party batteries but even then they wouldn't crash the system they would just maybe not charge unless in a separate battery charger
Please use the Q&A Forum for questions Thanks
Moving to Q&A
anoninja118 said:
are all these batteries OEM (Samsung made for the Charge) ones?
Click to expand...
Click to collapse
Yep. Every one of them is the real McCoy, made by Samsung and either purchased from the local Verizon store or from Amazon (not an Amazon vendor, but from Amazon itself).
SoonerLater said:
I will pay FIFTY DOLLARS ($50.00) to the person or team that provides a solution to this problem.
After swapping batteries in my Droid Charge, I often (but not always) get a huge number of force close crashes when it boots up. The apps that usually force close on reboot are Google Docs, FlexT9 keyboard, GoSMS Pro and App Protector.
My phone is running Imnuts's Infinity Rom 1211, plus his battery addin and his widgets. However, this problem also existed when I was running Gummy Charged 2.1.
I own several batteries. In fact, I own seven of them. I have a drop-in charger at home, at work and in my car. There's always at least one fresh battery at all locations. I mention this because I realize that there is something about "battery stats" that you can wipe (using CWM Recovery). Maybe the phone is not smart enough to keep track of so many unique batteries?
When I swap a battery and then I get an a~~load of force close crashes, the phone will come up as though the ROM had just been installed. It asks me for my Google Account info just like it was being configured for the very first time.
When this happens, I have to reconfigure my two Google accounts (home and work), let it resync all the data on those two accounts, then reinstall many applications.
I asked about this once when I was still running Gummy Charged and the suggestion came back that it was a software issue that could most easily be remedied by changing to a newer ROM. The poster said that Gummy Charged wasn't being actively supported anymore, but Infinity was and suggested I go that route.
Q. -- What sort of process / event related to swapping batteries (or merely rebooting) could cause the phone to come up like it's never been configured before?
Whenever I install a ROM, I always wipe the Dalvik Cache and wipe the internal SD (but not the 32 gb removable SD card). Whenever I move from one ROM to another ROM, I always fall back to factory stock first. Any time I installed Infinity ROM, I received no errors of any kind (and same for when I installed other ROMs in the past).
When my phone works correctly, I really like the Droid Charge. When it doesn't, I want to take a large cache of weapons and ammunition to a postal facility. I can't tolerate this any longer. I have to solve the problem (forever) or I have to give up and buy another phone.
FIFTY BUCKS BY PAYPAL FOR THE SOLUTION.
Click to expand...
Click to collapse
have you tried flashing back to stock rom and keeping it that way for a day or two seeing if that made a difference?
*edit* i did read that you do flash back to stock but i dont know if you automatically flashed back to the other ROM without trying it out first
The solution is make a full backup of your apps and data (use mybackup or titanium. I used mybackup since it's faster and it only show your installed apps, not the system apps). Odin stock EP4d and Pit files then boot up to normal screen. Shutdown and Odin either TweakStock + kernel or Tweakstock with immosey kernel if you want Ext4 lagfix. If you're using Mybackup, first restore data, reboot, then restore apps. You should be good to go. I had this issue before, after done all above, I'm currently use all kind of batteries with all kind of different voltages without any problem (1600mah, 1800mah, 3500mah, 3600mah). I swapped them in and out everyday without issue. Good luck. Just want to help you out.
buhohitr said:
The solution is make a full backup of your apps and data (use mybackup or titanium. I used mybackup since it's faster and it only show your installed apps, not the system apps). Odin stock EP4d and Pit files then boot up to normal screen. Shutdown and Odin either TweakStock + kernel or Tweakstock with immosey kernel if you want Ext4 lagfix. If you're using Mybackup, first restore data, reboot, then restore apps. You should be good to go. I had this issue before, after done all above, I'm currently use all kind of batteries with all kind of different voltages without any problem (1600mah, 1800mah, 3500mah, 3600mah). I swapped them in and out everyday without issue. Good luck. Just want to help you out.
Click to expand...
Click to collapse
yea that about sums it up
but fyi im having issues with the flash player on tweakstock and i dont know if it is just mine,
if you dont really use the flash player then go for it, its a great rom
ferny_dx said:
have you tried flashing back to stock rom and keeping it that way for a day or two seeing if that made a difference?
*edit* i did read that you do flash back to stock but i dont know if you automatically flashed back to the other ROM without trying it out first
Click to expand...
Click to collapse
I flash back to stock. Let it boot. Verify that it seems to be running ok, then I flash the custom rom on top of it. I don't go back to stock and then run stock for a day or two. I'm back on stock for... about... ten minutes.
I don't completely 100% wipe the phone, since to install a new rom, I use Clockwork Mod which reads the new rom from a zip file on the internal memory. If I wiped the phone, then the zip wouldn't be there to install. I suppose that I could use ODIN to install the rom instead, but installing from a zip using CWM is so easy by comparison to Odin.
I don't wipe the 32gb external SD card -- ever. I suppose that there could be some sort of latent flaw in the card that might be remedied by reformatting the external SD card, then rewriting all the data. However, if it had a flaw, I wonder why it would only become evident when the phone reboots.
I don't know, but I assume that the phone keeps "battery stats" on different batteries (that they have some sort of unique identifier that is read by the phone so it can tell one battery from another). If that's the case.... I wonder... do I simply have more batteries than any moderately sane human has? Do I have so many batteries that I've exposed a flaw in the operating system when it tries to keep track of more batteries than it's designed for?
buhohitr said:
The solution is make a full backup of your apps and data (use mybackup or titanium. I used mybackup since it's faster and it only show your installed apps, not the system apps). Odin stock EP4d and Pit files then boot up to normal screen. Shutdown and Odin either TweakStock + kernel or Tweakstock with immosey kernel if you want Ext4 lagfix. If you're using Mybackup, first restore data, reboot, then restore apps. You should be good to go. I had this issue before, after done all above, I'm currently use all kind of batteries with all kind of different voltages without any problem (1600mah, 1800mah, 3500mah, 3600mah). I swapped them in and out everyday without issue. Good luck. Just want to help you out.
Click to expand...
Click to collapse
You're the first person I've found that had a similar problem. I'll go to Tweakstock tonight and report back. Thank you for your help. I note your just want to help you out and I appreciate the generosity of your time.
SoonerLater said:
I flash back to stock. Let it boot. Verify that it seems to be running ok, then I flash the custom rom on top of it. I don't go back to stock and then run stock for a day or two. I'm back on stock for... about... ten minutes.
I don't completely 100% wipe the phone, since to install a new rom, I use Clockwork Mod which reads the new rom from a zip file on the internal memory. If I wiped the phone, then the zip wouldn't be there to install. I suppose that I could use ODIN to install the rom instead, but installing from a zip using CWM is so easy by comparison to Odin.
I don't wipe the 32gb external SD card -- ever. I suppose that there could be some sort of latent flaw in the card that might be remedied by reformatting the external SD card, then rewriting all the data. However, if it had a flaw, I wonder why it would only become evident when the phone reboots.
I don't know, but I assume that the phone keeps "battery stats" on different batteries (that they have some sort of unique identifier that is read by the phone so it can tell one battery from another). If that's the case.... I wonder... do I simply have more batteries than any moderately sane human has? Do I have so many batteries that I've exposed a flaw in the operating system when it tries to keep track of more batteries than it's designed for?
Click to expand...
Click to collapse
i dont think so, the FCs shouldn't have anything to do with the battery thats something else completely in my opinion,
I would say give it a shot on stock rom, just restart it a few times see if there are still FCs
do you use the ALL-IN-ONE file to flash it?
---------- Post added at 11:36 AM ---------- Previous post was at 11:31 AM ----------
how ive fixed most isssues on my Charge has involved flashing files from this thread
http://forum.xda-developers.com/showthread.php?t=1111486
just find what version you want download the PIT and put them in odin,
i don't know if you should or not but i have a habit of taking out my sd just in case
i uncheck all of the options except for re-partition and i have have a completely stock phone
i do lose all contacts and such which should be backed up prior to this process, although im pretty sure you know that
How are you shutting down the phone? through the power menu, holding down power, pulling battery...
It seems all your FC issues are of apps that normally run in background. An improper shutdown could corrupt the file while it's reading/writing.
Sent from my SCH-I510 using xda premium
ferny_dx said:
yea that about sums it up
but fyi im having issues with the flash player on tweakstock and i dont know if it is just mine,
if you dont really use the flash player then go for it, its a great rom
Click to expand...
Click to collapse
flash player issue fixed heres the thread
http://forum.xda-developers.com/showthread.php?p=21536370#post21536370
SoonerLater said:
I flash back to stock. Let it boot. Verify that it seems to be running ok, then I flash the custom rom on top of it. I don't go back to stock and then run stock for a day or two. I'm back on stock for... about... ten minutes.
I don't completely 100% wipe the phone, since to install a new rom, I use Clockwork Mod which reads the new rom from a zip file on the internal memory. If I wiped the phone, then the zip wouldn't be there to install. I suppose that I could use ODIN to install the rom instead, but installing from a zip using CWM is so easy by comparison to Odin.
I don't wipe the 32gb external SD card -- ever. I suppose that there could be some sort of latent flaw in the card that might be remedied by reformatting the external SD card, then rewriting all the data. However, if it had a flaw, I wonder why it would only become evident when the phone reboots.
I don't know, but I assume that the phone keeps "battery stats" on different batteries (that they have some sort of unique identifier that is read by the phone so it can tell one battery from another). If that's the case.... I wonder... do I simply have more batteries than any moderately sane human has? Do I have so many batteries that I've exposed a flaw in the operating system when it tries to keep track of more batteries than it's designed for?
Click to expand...
Click to collapse
Same here, check out my collections
fc after battery swap
Galaxy Note
I find my battery is pretty loose, and it has dropped out on me a couple times and if the phone is running it force closes everything on boot and requires a flash to even become useable again.
Wyrez said:
Galaxy Note
I find my battery is pretty loose, and it has dropped out on me a couple times and if the phone is running it force closes everything on boot and requires a flash to even become useable again.
Click to expand...
Click to collapse
Wrong forum
Sent from my handheld Linux computer using electromagnetic radiation.
Charge Note
I had the same thing happen to me once. Both removed and inserted batteries were stock. It was last fall sometime, so I prolly was on an infinity build. Maybe. Anyhow, you're not alone. Except for the frequency I have this notion that perhaps I did not let it fully power down, but I can't say for sure. Fortunately, it only happened the one time. I only data wiped reflashed in cwm, titanium, blah blah blah, and that was it.
A Note Sent from my SCH-I510 using Tapatalk 2
Fix permissions? lol
I have noticed that I will always seem to have some sort of issue when flashing while docked(keyboard). most time just small detail stuff. undocked the flashes always go fine.
I am just wondering if this is a known issue with certian recoveries or something specific to me.
running twrp 2.3.2.3 but have noticed with other recoveries as well.
Oh want to take this time to send out a HUGE :good: THANKS :good: to all those working on roms etc.. and making my transformer usefull again as it was an expensive paper weight the way asus left it
Can you explain your issues further? I'm flashing docked almost daily so I can get back to you if I notice anything.
Lethe6 said:
Can you explain your issues further? I'm flashing docked almost daily so I can get back to you if I notice anything.
Click to expand...
Click to collapse
by issues i mean bad flashes. from the rom getting stuck on logo to smaller issues like browser crashing bad lag and constant reboots.
I have tested this somewhat and if i reflash with out dock the problems are gone. I have even went and reflashed over a good flash with dock attached and again the random problems arise again. (all with full wipes including internal/system etc....)
not a big issue over all. just flash with out dock. just thinking that this might be an problem for others who are having problems getting a good flash of rom.
MessyMarv said:
by issues i mean bad flashes. from the rom getting stuck on logo to smaller issues like browser crashing bad lag and constant reboots.
I have tested this somewhat and if i reflash with out dock the problems are gone. I have even went and reflashed over a good flash with dock attached and again the random problems arise again. (all with full wipes including internal/system etc....)
not a big issue over all. just flash with out dock. just thinking that this might be an problem for others who are having problems getting a good flash of rom.
Click to expand...
Click to collapse
***update***
well did some more testing and in truth when i 1st put on twrp i had 1 bad flash and just and just assumed that it was same as last recovery.
but not liking not knowing for sure i have been doing all my recent flashes while docked and all has gone smooth.
So Im left with the conclusion that there must have been problem with old recovery and that twrp work just fine with dock.
Way to go TWRP :highfive:
MessyMarv said:
I have noticed that I will always seem to have some sort of issue when flashing while docked(keyboard).
Click to expand...
Click to collapse
Flashing with nvflash or with CWM/TWRP?
I'm always flashing with dock and I never have issues.
I used this 1-click to root and install recovery. was like months ago too.
http://forum.xda-developers.com/showthread.php?t=1689193
but did have to undock to get problem free installs.
did start to test with dock again and last 10 or so installs with twrp have gone perfectly while docked tho so for me problem is solved
If you dont know what nvflash is, you are not using nvflash.
And no, I never undock.
To me, it sounds like you should upgrade to latest TWRP. It is supported by most ROMs (and even required by some).
It is actively developed, supports touch, dock, internal storage, external SD-cards, USB, etc and has no issues like this.
Yeah I've flashed a couple of times since I replied to you and I haven't had any issues at all. I tried the same flash with or without the dock and haven't noticed any weirdness or unstability (well nothing new anyway).
Hello great people of XDA,
About one month ago, my digitizer cracked, and I ordered a new screen & digitizer combo from ebay.
Two days ago the replacement arrived and the whole process went smoothly! Everything was working fine, except one thing. The Battery Percentage went crazy. It shows the remainder percentage in thousands.
eg. 3603 % and it always appear full! As soon as i put the phone to charge it appears as "Charged" but thankfully, the battery does indeed charge.
Check the screenshots in the attachments below.
The last screenshot (from the app Battery Stats Plus) says "Charging" but the phone is unplugged. Actually it's pretty obvious that all readings all wrong!
A friend of mine has also a Nexus 5, I tried replacing my battery with his, but the problem remains. Even with a different battery, the readings and percentage are wrong!
It's pretty frustrating. I tried solving one issue, then another came along. Do you have ANY ideas? Oh and one more thing. The "Battery" option from Settings is nowhere to be found!! I have to tap in the battery icon in notification drop-down to enter Battery settings.
Thank you in advance for your time!
Are you running a custom kernel on a stock ROM?
audit13 said:
Are you running a custom kernel on a stock ROM?
Click to expand...
Click to collapse
Hey audit13. Thank you for your reply.
I'm running Stock rooted ROM 6.0.1 (MMB29V) & stock kernel
Hmm, weird that a screen change would cause this. Try the following: (1) clear cache from recovery mode; (2) clear data from recovery mode (this will wipe your data, apps, etc.); or (3) flash a stock ROM without flashing the userdata.img partition or erasing data.
audit13 said:
Hmm, weird that a screen change would cause this. Try the following: (1) clear cache from recovery mode; (2) clear data from recovery mode (this will wipe your data, apps, etc.); or (3) flash a stock ROM without flashing the userdata.img partition or erasing data.
Click to expand...
Click to collapse
I'm afraid that a factory reset/re-flash rom has crossed my mind, but it's something that I do not have time to do right now. I'm pretty sure that it's a software-related issue. Not a hardware one.
I was purely asking for something quick.
Thank you for your suggestion though (and of course your time) If anything else pops in your mind, i'm eager to hear it.
I also think it is software related which is why I suggested flashing a stock rom. If it was hardware related,flashing would not fix the issue.
Gonik said:
I'm afraid that a factory reset/re-flash rom has crossed my mind, but it's something that I do not have time to do right now. I'm pretty sure that it's a software-related issue. Not a hardware one.
I was purely asking for something quick.
Thank you for your suggestion though (and of course your time) If anything else pops in your mind, i'm eager to hear it.
Click to expand...
Click to collapse
It only takes like 60 seconds to flash a stock rom and ten more to log into your google account once its booted and everything it restored for you pretty much. Its the easiest way to fix software issues for the most part.