Related
Okay, so for a while I was among those fortunate to have their Batteru Usage Stats not force close. For those not sure what I'm talking about, it's under Settings -> Battery Manager then touching the "battery indicator".
Well as of recent I started to get force closes like others, and decided to charge up the battery 100% and wipe my battery stats using Koush's bootstrap.
Upon rebooting my force close issues are gone (for now). Now I don't know for sure if this was a fluke or what, and I'm not sure how many ways one can wipe their battery stats but if you are getting force closes then give it a try.
Anyways, hope it helps.
What do you exactly mean by "wipe my battery stats" ??
InfamousDX said:
What do you exactly mean by "wipe my battery stats" ??
Click to expand...
Click to collapse
I can only vouch for Koush's bootstrap recovery, which has an option to wipe battery stats.
That being said the problem came back, so it may just be a temporary fix.
Sent from my DROIDX using XDA App
Okay, another update to this thread:
After the force close in battery usage statistics came back I let it go for a while. Just today after a complete recharge I went back into recovery and wiped stats again. Upon rebooting I was able to see my usage statistics again without force closing.
Well, I plugged the phone into the PC to transfer a blackbar theme to my SD card, and after that hastily opened droid x bootstrap and rebooted back to koush's recovery to flash it.
After flashing it successfully, and upon rebooting I now get my force close again.
Sooooo.....
Now to figure out if my hasty boot to recovery (it was doing the preparing SD card thing when I had the app boot to recovery) is what's causing this or the actual flashing of the blackbar mod (for whatever reason) is the culprit.
Of course all this was done with an "I wonder...." approach so I'm going to try and narrow it down when I get a chance.
I am not sure if there is a clear "flash this or mod that" root to the problem.
I have had this problem and it persists from full sbf's, different roms etc...
It comes and goes as it pleases even when I do nothing different to my system, so I think it is more of a base kernel issue with 2.2.
Hopefully this will be fixed in 2.3 (if we get it etc..) but until then I just live with it working/not working as its mood dictates.
Just my opinion
D.
I can't begin to describe how frustrated this phone has made me. I am not an Android "n00b" by any stretch. I have had 4 different Android phones, have flashed at LEAST 100 different roms, made complete rom themes, and even glued together one of the first complete Gingerbread roms to flash from recovery for the Motorola Droid (not from source, but first posted rom with working camera, Gapps, and all from standard recovery - not nandroid). With that being said, this phone is next to impossible for me to use. I've lost track of all of the problems I have had with this thing. Everything from CWM not being able to restore any backups, horrible battery life, boot loops galore, the phone freezing anytime it is plugged into the computer or wall (not the car charger, oddly enough), boot loops, tried the Yellow Clockwork (and everything failed that could on that), flashing roms that would work great until you reboot the first time, and so on and so forth. WHEN the phone works, it's great. However, that is starting to become quite rare. Most recently I have been stuck on trying to get either Evil Fascinate to work or MIUIWiz with no luck for either. EF works great...until I restore my apps. Once I reboot, it's all over. EVERYTHING force closes and it becomes completely unusable. Doesn't matter what kernel I use, it always happens. And this is now happening with both 3.5.1 and 3.6.0. Plus I could just watch the battery life plummet as I was using it. I even tried the EC01 radio with it, as it was suggested that might be better. So, I decided to try MIUIWiz. Followed the directions perfectly. Wiped everything, flashed a JT Kernel from 4/15, flashed rom, and...guess what? Boot loops. I am on ClockworkMod 3.0.2.7. I am familiar with how to wipe data/cache/dalvik. There were no voltage settings to wipe. I did check to see if Voodoo was enabled before booting. I just don't know what else to do. This isn't exactly rocket science and I really feel it can't just be user error at this stage with all of the different issues I have ran across. I'm pretty much at the stage that I am gonna return it to stock and sell it, but would really like to enjoy it for a little while longer... Thoughts?
Just for laughs, I downloaded Community Rom 1.3. Was on EF 3.6 (with nothing restored, just signed into Google). Rebooted to Recovery, wiped everything, installed Comm Rom and never got past the Samsung screen. *sigh* Seems odds since they are based on the same base, but yea, that's how it's been going for me.
I think since you are so god awfully experienced that you are looking over something that probably seems useless to you, ive NEVER experienced any of your problems and I can tell you its not the phone.. I would read up about your specific problems or ask a specific question and you might get the help you need.
Edit:Bootloops are user error nearly every time. Unless you have a corrupt download or something.
Sent from my SCH-I500 using XDA App
As much as your sarcasm warrants a rude response, I'll choose not to stoop to that level. The point of the post was that there is not a "specific" problem. Hence the title, "Nothing works as it should..." Not every phone is the same, and just because you have experienced any of these problems does not determine whether my issues are phone related or not. Battery life issues are very common place, which is evident in many threads. The phone lagging when plugged in is most CERTAINLY a phone issue and has nothing to do with rom flashing. It appears this is a firmware issue and is not likely to be fixed at all. Also, I pointed out the steps used to flash the rom, which are posted in the thread, and still have problems with boot loops. So, I guess every rom I download is corrupted? Even though on different networks and computers? That's some luck I have...
Are you referring to "download" mode when you said yellow cwm? If so then maybe reinstall the samsung drivers and give it a clean flash including the pit with voodoo disabled. If you have bad problems like you are having that fixes anything I encounter.
Edit: if you use odin, try heimdall
Sent from my SCH-I500 using XDA App
The newest imnuts kernel installs a yellow CWM, and nothing worked right at all on that. Every verification failed. SO I ODINed back to stock and retried everything anew. Anytime I restore my apps with Titanium, the next reboot fails. I even just went back to stock again, flashed CWM Red 3.0.2.8ti and the stock kernel with recovery fix, restored apps again and rebooted and it did the same thing. I didn't have any issues with Titanium restoring stuff before, having successfully used it on EF 3.5.1 and ComRom 1.3 but not those don't work for me either anymore. I've tried restoring just the apps with no data and that doesn't seem to make a difference either.
EDIT - It must have something to do with Titanium. Gonna try an older version and see if that works. It looks like they updated it recently and maybe it is just not playing nice with anything for my phone.
When you restore try not restoring system data, that is check the box for user applications only. That might be the issue.
yea, I'm going to say Ti backup is the problem because you mention ti every time you have a problem. personally I don't use ti cause its never played nice for me, but did you try manually reinstalling a couple of apps reboot and see if the same problem happened? that would really narrow it down almost completely to ti.
Fascinate 2.2 1.2GHz(uv)
download the imnuts peanut butta jellytime kernel of choice and put it on your sdcard. Odin back to the stock rom of your choice (i recommended eb01 as other odin packages cause bad music quality.), and let the phone boot up.
Next, pull the battery and go back into download mode. Odin one of times_infinity's cwm packages. Then replace the battery and boot straight into CWM. Wipe data, cache, and dalbik and then flash community rom 1.3. IMMEDIATELY AFTER (meaning in the same cwm as when you flashed comm rom 1.3) flash the imnuts kernel that you put on your sdcard. Phone should boot up fine and be fully functional. As mentioned earlier by someone, dont restore system data with titanium backup.
It's not just the system data that is causing issues, as I have tried it both ways, and of course, only restoring system data that is labeled green when attempting to do so. And, it did work previously on EF 3.5.1 but no longer does. I'll give it another shot using thefunkbot's directions. Still confused as to why EF is the only rom that boots normally.
Alright, so that did get Com Rom running. I had actually tried that method before, but it took so long on the Samsung screen that I was sure that it was froze. I just let it go this time, and after about 5 minutes it finally started. None on the other roms I tried took that long, but whatever works...
that's probably due to voodoo, which takes about that time to install/initiate.
Yea, you can hear the creepy robot lady telling you what's going on, but it took a couple of minutes after that even. Also, I skipped Titanium and restored the apps manually. Some were from my SD card and some from the Market, and only about half of them worked after rebooting. Meh
Flash com rom, then flash the otb kernel. Comrom will boot and you will enjoy your phone.
I got Com Rom to boot, but alot of the apps won't reinstall without force closing after rebooting. Not being able to use Titanium is a major PITA to me. But it's not just Com Rom, it's EF, and even the stock rom. Just never had an issue with it before now. But even installing apps through the Market or from the SD card also created issues, so I dunno what is going on.
If you're getting a **** ton of FCs, try fixing permissions via Terminal Emulator. Run 'fxpms' and it *should* solve some FC issues. Also, the phone generally takes much longer than a couple minutes to boot up after doing a full wipe, because the dalvik cache has to be rebuilt. Guarantee that if you had just left the phone alone the first time it was stuck on the Samsung screen, it would've booted just fine.
There are many guides that should help if you run into problems. First odin back to stock update to get new modem (doesn't have to be the newest but might a well), use the pit as well. Second odin cwm. Then flash kern and rom with a voodoo conversion if desired.
At first don't restore any backups. Don't use any themes. Or make any other changes until you see how out runs. Also don't play with the under volting until you've used it a while.
After running it awhile "stock" a it were then start making your changes one by one. This way at least you will know what its causing the trouble.
That happened to me as well when flashed com rom. I took 3 batt pulls before I just let it go to find it was working all along just took its sweet time on first boot. Was not voodoo here. I also agree with your charger problem, but for me its reversed, only happens on the car charger. And I hate to say it but no froyo rom, stock or otherwise, plays nice with my fascinate. I get all kinds of weird bugs. And battery life got worse. Since I have come to the realization that no fascinate aosp or cm rom will ever have bluetooth headset support, I finally threw in the towel and spent an hour on the phone with verizon to get an upgrade. Sad but after all this time it was time to give up.
Sent from my SCH-I500 using XDA App
Wiping Davlik causes unusually long boot times on Froyo ROMs on the Fascinate. If you just wait it out (if it's more than 15 minutes, though, something's wrong) you should be golden. By the way, PBJ 5/23 is literally a non-starter, so I would suggest nemesis2all's OTB kernel until imnuts updates.
Another Fascinating post by my XDA app...
Thanks for all the help and advice everyone. After trying five different roms, I finally found one that works for me. Blackhole. I set it up just like the others, the difference being that Titanium and everything else works. Still have to test battery life, but just having all my apps and no force closes or boot loops is enough for now...
es0tericcha0s said:
Thanks for all the help and advice everyone. After trying five different roms, I finally found one that works for me. Blackhole. I set it up just like the others, the difference being that Titanium and everything else works. Still have to test battery life, but just having all my apps and no force closes or boot loops is enough for now...
Click to expand...
Click to collapse
Blackhole 4.4? Or an earlier version? I miss SonOfSkywalker's work since he added the Thunderbolt to his arsenal (he also devs for the Vibrant)
Another Fascinating post by my XDA app...
4.4. Haven't had any issues with it so far. Battery life is probably not the best so far it seems, however I don't even care at this stage as long as everything works. I also have not run it down and reset the battery or played with many settings yet so not ready to say it is the rom or anything of the sort. Everyone has their deal breakers with their phone, and not having Titanium work is one of my biggest things. I love that app. I didn't donate for it to not use it, you know? I'm a themer, and I have a lot of themed apps saved with it that makes the Market pretty much useless to reinstall stuff for me. Plus it is an easy way to uninstall system apps without screwing anything else up.
Okay, I have honestly searched everywhere - Google, the xda forums, other forums and I still can't find something to help me with this strange problem I have.
PAST SITUATION
I installed TyphooN CyanogenMod ROM v3.5.8 around a month ago and I used it with no major problems (few android.acore repeated force closes that was dealt with by re-installation). During this time, I could power the phone off and power it on with no problems.
PRESENT SITUATION
This is where things go wrong. Recently, I decided to install TyphooN CyanogenMod ROMv3.8.5 (the latest one) by booting into MGDLR, doing a factory reset, wiping the system and dalvik caches and then installing the new 3.8.5 zip file. It installed properly and I booted into Android and was enjoying the new improvements and bug fixes. I had no problems until everything started force closing suddenly so I decided maybe a reset would fix it. AND THIS IS WHAT THE PROBLEM IS It boots to the Android Logo and stops there. I waited for 30 mins but it was still stuck at the Android logo and no matter how many times I took the battery out and put it back in and rebooted it, it was still stuck at the Android logo.
HOWEVER when I did a hard reset and wiped the system and dalvik caches and installed it again, it installed fine and booted into the system. When I tried to power it off and power it on again, the same problem happened where it was stuck on the android logo.
WHAT I TRIED TO FIX IT
1) A clean installtion, did a task 29 and installed everything again. Same problem happens.
2) I did a hard reset (wiped system and dalvik caches as well) AND THIS TIME I installed the previous version I was using with no problems (v3.5.8) and I had the same problem! Even with that version it still gets stuck on the Android logo screen.
I can use the ROM perfectly and my phone works fine, but if ever I need to reboot my phone for any issue it won't start up again and gets stuck on the android logo. I have to do a hard reset and re installation for it to work again but that means all my data, files and messages will be lost each time. So you can see the inconvenience I'm facing.
WHAT I THINK IS THE PROBLEM
1) I'm using a fairly old version of ClockworkMod Recovery. That is version 3.0.2.5 (150MB with 5MB Cache as per Typhoon's Requirements). Is this the problem?
2) I didn't remove the SIM and SD card during the entire flashing/reinstallation process. Could this be it?
Should I do a clean installation (task29) and install the previous ROM version I used with no problems and see if the problem still persists or if its only since I installed the new ROM version first?
Thanks for your help. And also I'm sorry I can't post this on the Typhoon ROM thread since I still don't have 10 posts.
did you get things sorted?:cyclops:
Well not yet. I am working on it. Does anyone have a download link to the latest version of ClockworkMod Recovery with 150MB and 5MB cache? I tried the HD2Toolkit and it just doesn't work for me, I plugged in my USB, it indicated USB Debugging was on and meh, it didn't click.
Anyways, I'm going to try task29ing the phone and installing MGDLR and the version of ClockWorkMod Recovery I have and installing the previous version of typhoonmod i used without any problems at all. Hopefully it'll just be a new version of the ROM issue.
I'll post my results here soon.
SpoonyVoid said:
WHAT I THINK IS THE PROBLEM
1) I'm using a fairly old version of ClockworkMod Recovery. That is version 3.0.2.5 (150MB with 5MB Cache as per Typhoon's Requirements). Is this the problem?
2) I didn't remove the SIM and SD card during the entire flashing/reinstallation process. Could this be it?
Thanks for your help. And also I'm sorry I can't post this on the Typhoon ROM thread since I still don't have 10 posts.
Click to expand...
Click to collapse
Sadly I can't give you any new suggestions, but I can certainly rule these two out as possibilities. I've never taken out the SIM when flashing, and you can't flash without the SD card. Recovery 3.0.2.5 is actually (from what I've heard) the most stable version. Have you tried other ROMs? Although again I highly doubt it's the issue, it's worth a shot.
You might want to consider the possibility of bad blocks, from what I've heard it can cause issues such as this (I don't actually have experience with them) so check for them (a simple forum search should give you a method as to how to do this).
SpoonyVoid said:
Well not yet. I am working on it. Does anyone
Anyways, I'm going to try task29ing the phone and installing MGDLR and the version of ClockWorkMod Recovery I have and installing the previous version of typhoonmod i used without any problems at all. Hopefully it'll just be a new version of the ROM issue.
Click to expand...
Click to collapse
Okay, So I tried this. The ROM installed fine but when I tried to power off and power on again it didn't work, the same problem happened where it got stuck on the Android logo.
WHAT I DID THEN
I decided enough's enough and that I can't really use my phone with Android if in some case something happens and I have to reboot it, I'll lose all my data and I'll have to reinstall it all over again.
So I switched to Windows 6.5 version 2.10.531.1 running Radio 2.15.50.14 and everything installed perfectly and I even rebooted the phone after installation and it worked. It came on with no problems. I'm guessing this is an issue that only affects Android then.
Nigeldg said:
Have you tried other ROMs? Although again I highly doubt it's the issue, it's worth a shot.
You might want to consider the possibility of bad blocks, from what I've heard it can cause issues such as this (I don't actually have experience with them) so check for them (a simple forum search should give you a method as to how to do this).
Click to expand...
Click to collapse
Thanks for the reply. I have not tried other ROMs out of fear of bricking my phone to be honest. Typhoon ROM is like one of the easiest for a newbie to install.
And yes, when I was searching around the forum, I did come across the issue of bad blocks. Sadly, I totally forgot to check whether it was affecting my NAND before installing WinMo 6.5. I'll try and look around the forums and google on whether I can check my bad block status on WinMo 6.5 somehow. If I can't, I think I'll use WinMo 6.5 for a while now, I can't really bear having to install and reinstall and install and reinstall, I feel like it'll make the bad block situation (If I do have it) worse.
I'm going to play around with WinMo 6.5 ROMs now. But if ever there is any development on my problem, I'll post on this thread and keep people updated.
I do have one question though, will upgrading to WinMo 7.5 be affected by the bad blocks? (If I have it)
Just saying, although it doesn't really matter, it's Windows Phone 7 (not WinMo 7). One's sh*t, and one's brilliant I don't have any actual experience with Windows Phone though, so I wouldn't know.
As for your concern about bricking your phone, there isn't any way you can do that outside of flashing an incorrect radio, and if you have an EU HD2 then AFAIK there isn't really ANY way of bricking it. Try other ROMs, they have exactly the same install process as TyphooN. In fact, starting fresh from WinMo might actually help. As long as you stick to this guide and use the correct partition size, you will never really go wrong. You can obviously also check for bad blocks after you install Android again (if you decide to do so, of course).
I have quite exciting news! well for me at least
I flashed Windows Phone 7.5 on my HD2 and was very impressed with it. It worked nicely and I really liked all the features. One thing I didn't like however was the battery drainage. The battery drained in 6 hours, and the next day it took 15 hours to drain and then again it took 6 hours to drain. I realized I couldn't use a phone daily with such uncertain battery capacity.
So I decided...*breathe*...to try out Android again, the NexusHD2 ROM by tytung in particular and hope and pray I don't have bad blocks and the rebooting problem doesn't occur.
So I uninstalled WP7, repartitioned my SD card, installed Windows 6.5 STOCK and the right radio and MAGDLR, Clockwork Recovery and flashed NexusHD2 and then did the Bad Blocks thingamabob I was supposed to do and accessed the recovery.log but I couldn't find any mention of "bad blocks" or anything related to "bad". But I dunno...
Anyways the good news is NexusHD2 Gingerbread 3.5.7 works really well and I don't have the rebooting problem anymore. Just a few android.process.media force close issues that I'm trying to figure out but the main problem is gone!
SpoonyVoid said:
I have quite exciting news! well for me at least
I flashed Windows Phone 7.5 on my HD2 and was very impressed with it. It worked nicely and I really liked all the features. One thing I didn't like however was the battery drainage. The battery drained in 6 hours, and the next day it took 15 hours to drain and then again it took 6 hours to drain. I realized I couldn't use a phone daily with such uncertain battery capacity.
So I decided...*breathe*...to try out Android again, the NexusHD2 ROM by tytung in particular and hope and pray I don't have bad blocks and the rebooting problem doesn't occur.
So I uninstalled WP7, repartitioned my SD card, installed Windows 6.5 STOCK and the right radio and MAGDLR, Clockwork Recovery and flashed NexusHD2 and then did the Bad Blocks thingamabob I was supposed to do and accessed the recovery.log but I couldn't find any mention of "bad blocks" or anything related to "bad". But I dunno...
Anyways the good news is NexusHD2 Gingerbread 3.5.7 works really well and I don't have the rebooting problem anymore. Just a few android.process.media force close issues that I'm trying to figure out but the main problem is gone!
Click to expand...
Click to collapse
Good to hear that, and it's also good that you don't have any bad blocks. Even then, you shouldn't have the FC problems, so this is quite confusing.
Nigeldg said:
Good to hear that, and it's also good that you don't have any bad blocks. Even then, you shouldn't have the FC problems, so this is quite confusing.
Click to expand...
Click to collapse
Funny thing really, I did some testing and the process.android.media force closes every time I try to open the android market ONLY AFTER I have powered off and powered on the device AFTER flashing the ROM. If I don't power off the device after flashing the ROM, I don't have that problem at all and I can access the android market with no problems.
Just to be on the safe side however and since I've decided to keep on using NexusHD2 daily, I've backed up all the system files (after a clean re-installation) with Titanium backup so if ever I have to reboot the device, I can hopefully prevent the force close messages from appearing. I've also updated the android market to the latest version just for kicks.
When trying to fix the force close problems earlier, I went to the MAGDLR bootloader screen, proceeded to the CWM menu, tapped into Advanced and fixed permissions. When I booted into Android, the force close messages stopped appearing, however the android market wouldn't open. It would appear briefly and then close automatically without displaying any sort of error message. Strange.
I seriously think I haven't done the bad blocks check properly. I'm sure I have some since this phone is around two and half years old now and was passed on to me by my brother after he experimented around with it as well. I followed AngelDeath's post in the Bad Block Awareness thread but couldn't find any mention of bad blocks and found only a few mentions of the word "block" itself on the recover.log. I didn't find anything similar to his extract of his log on the first post of that thread as well. I'm doing something wrong.
SpoonyVoid said:
Funny thing really, I did some testing and the process.android.media force closes every time I try to open the android market ONLY AFTER I have powered off and powered on the device AFTER flashing the ROM. If I don't power off the device after flashing the ROM, I don't have that problem at all and I can access the android market with no problems.
Just to be on the safe side however and since I've decided to keep on using NexusHD2 daily, I've backed up all the system files (after a clean re-installation) with Titanium backup so if ever I have to reboot the device, I can hopefully prevent the force close messages from appearing. I've also updated the android market to the latest version just for kicks.
When trying to fix the force close problems earlier, I went to the MAGDLR bootloader screen, proceeded to the CWM menu, tapped into Advanced and fixed permissions. When I booted into Android, the force close messages stopped appearing, however the android market wouldn't open. It would appear briefly and then close automatically without displaying any sort of error message. Strange.
I seriously think I haven't done the bad blocks check properly. I'm sure I have some since this phone is around two and half years old now and was passed on to me by my brother after he experimented around with it as well. I followed AngelDeath's post in the Bad Block Awareness thread but couldn't find any mention of bad blocks and found only a few mentions of the word "block" itself on the recover.log. I didn't find anything similar to his extract of his log on the first post of that thread as well. I'm doing something wrong.
Click to expand...
Click to collapse
Ah that may be the problem then. You shouldn't really be touching anything immediately after flashing. Let the ROM settle for 5 minutes, complete the set up and then reboot a few times. As for why the Android Market isn't opening, once again am completely stumped, sorry. Try clearing the app data and cache then opening it again. I don't know whether or not this would work, but try to install a new play store.apk (e.g. the updated one in the HD2 Android Themes and Apps section) and try again. On no ROMs have I ever had this issue.
As for your being unsure about the bad blocks, I would be inclined to agree with you there, as it seems unlikely that after so long there would still be no bad blocks, especially if you and your brother were often flashing things.
dmesg command from a terminal emulator might give some info on the presence of bad blocks, if you haven't already tried it.
Sent from my Nexus One using xda premium
A logcat would be really useful when:
-ever your ROM gets stuck after a reboot.
- You face any random force close.
I used to have issues with the market closing without any error, it turned out to be unsupported where I was. In the new google play, it'd open, but nothing shows up. Fixed it by using DroidVPN.
Was the market working prior to this problem?
Also, have you checked the battery pins? (sometimes, they cause unpredictable problems)
You could also give cLK a shot, and see if the problem persists.
I searched but could not find a similar thread.
On my Defy (green lens), I was running 10.1 July build.
I got a new battery and used it one day. When it was low, I turned off the phone and put my old battery and rebooted. Everything was fine.
Since I have also a battery charger, I charged my new battery through it and when the old one was draining, I swapped it with the new one again and turned on the phone.
Ever since, the phone is stuck on the CM animation.
I would like to know what is the best way forward for me.
s_u_n said:
I searched but could not find a similar thread.
On my Defy (green lens), I was running 10.1 July build.
I got a new battery and used it one day. When it was low, I turned off the phone and put my old battery and rebooted. Everything was fine.
Since I have also a battery charger, I charged my new battery through it and when the old one was draining, I swapped it with the new one again and turned on the phone.
Ever since, the phone is stuck on the CM animation.
I would like to know what is the best way forward for me.
Click to expand...
Click to collapse
Wipe your /data and /cache partitions and reboot. If that doesn't work, wipe everything and reflash the ROM. If you're worried about your data you can make a backup, before wiping, and then restore your apps+data with Titanium backup from the TWRP backup. I wouldn't restore system apps/settings.
Recovery
I did a stock recovery. Somehow it did not fix my problem. Then I did a custom recovery and wiped data, cache and dalvik.
As a result, all my apps were wiped out (not a problem) and perhaps some of my data as well.
However the result was a much better 4.1.2 experience.
Everything works fast - no lags whatsoever.
Only problem is that the icons for People and Messaging in the Dock disappear after some time. This has happened more than 3 times in the last 24 hours.
The title says it all. I was having issues with errors and apps not responding or force closing, So I thought in would wipe the cache and Dalvik cache in TWRP, just in case there was something corrupted. Upon reboot, my battery life stayed at 65% when full charged, but would eventually charge to 100% when it was being used while charging. Now the batter dies in a very short amount of time! It happened, like that! No slow degradation, just boom! And it was done. Anyone have any ideas, or seen something similar with their Tab A 10.1?
ShadNuke said:
The title says it all. I was having issues with errors and apps not responding or force closing, So I thought in would wipe the cache and Dalvik cache in TWRP, just in case there was something corrupted. Upon reboot, my battery life stayed at 65% when full charged, but would eventually charge to 100% when it was being used while charging. Now the batter dies in a very short amount of time! It happened, like that! No slow degradation, just boom! And it was done. Anyone have any ideas, or seen something similar with their Tab A 10.1?
Click to expand...
Click to collapse
I always wipe cache/dalvik when dirty flashing my rom updates and never had that problem.
I'm guessing you have a bad battery, otherwise it wouldn't have behaved as you described. If you're lucky it's just a glitch - try a few charge cycles :fingers-crossed:
ShadNuke said:
The title says it all. I was having issues with errors and apps not responding or force closing, So I thought in would wipe the cache and Dalvik cache in TWRP, just in case there was something corrupted. Upon reboot, my battery life stayed at 65% when full charged, but would eventually charge to 100% when it was being used while charging. Now the batter dies in a very short amount of time! It happened, like that! No slow degradation, just boom! And it was done. Anyone have any ideas, or seen something similar with their Tab A 10.1?
Click to expand...
Click to collapse
It could be that something other than cache is corrupted. I'd try a factory reset after making sure OEM is enable in dev mode. In my experience, batteries don't go bad all of a sudden. Or, better yet, restore from TWRP backup. You do have a backup, don't you?
lewmur said:
It could be that something other than cache is corrupted. I'd try a factory reset after making sure OEM is enable in dev mode. In my experience, batteries don't go bad all of a sudden. Or, better yet, restore from TWRP backup. You do have a backup, don't you?
Click to expand...
Click to collapse
Never had a back up. All I did was root the tablet when root was first achieved a couple years ago. Should I try a system reset through TWRP or through the tablet itself? I ran it through the system, and lost root, and supposedly shouldn't have. Would I just be better off loading a new ROM through TWRP off the SD card? I'm sure I could find a stock OEM ROM on here somewhere, now at least. When I rooted the tablet, there was no aftermarket anything... Just the ability to root the device.
ShadNuke said:
Never had a back up. All I did was root the tablet when root was first achieved a couple years ago. Should I try a system reset through TWRP or through the tablet itself? I ran it through the system, and lost root, and supposedly shouldn't have. Would I just be better off loading a new ROM through TWRP off the SD card? I'm sure I could find a stock OEM ROM on here somewhere, now at least. When I rooted the tablet, there was no aftermarket anything... Just the ability to root the device.
Click to expand...
Click to collapse
Rule of thumb, flash stock ROMs via odin and custom ROMs via TWRP. My choice would be a custom ROM and then BACKUP!!!:laugh:
edit: If you rooted the device a long time ago, that means you haven't been getting any updates. You may well be clear back on Android 6 while the latest custom ROMs are 10 and the latest stock is 8.1. You can get the latest stock with Frija, which is a free download.
I'll have to take a look on my SD card, I recall using Titanium backup, so I'll have to check. Do you have any recommendations? Warranty is gone, so I'll likely install a new ROM, I usually do once it's up anyway
I only browse Reddit, Facebook, a couple other social media apps and I'll play the odd game.