Related
I'm running the newest SC and I keep running into this prblm. I've unrooted and rooted thinking that would fix it. I've ran a pacth file hoping it would be fixed.
I have been reading some post about it and really haven't found the fix or I just missed it. Can some one point me in the right direction.
Sent from my SCH-I500 using Tapatalk
The right direction would be asking your questions in Q&A.
Sent from my SCH-I500 using Tapatalk
First off, wrong section... should be in Q&A.
One way to fix it was to get SetCPU, and make sure the minimum CPU speed is 200MHz
You should also give more information. Have you flashed eb01 with odin before installing SC? How often do these sod's happen? Do you use the clock app?
Sent from my SCH-I500 using XDA App
Questions go in the Q&A subforum.
Here is the only answer that you will probably get that will work (taken from the CWM thread):
GizmoDroid said:
[SIZE=+1]Most Thorough Method of Fixing Every Problem You Might Have[/SIZE]
If you have an issue with applications force closing or a continual boot loop, a lot of times you can fix this issue by running the Fix Permissions option.
If you would like to see your phone be able to have fully functioning Nandroids, and less problems with permission related errors when flashing different ROM's, I encourage you to do the following (this will make your phone as clean and healthy as possible):
ODIN the full stock EB01 package in PDA, the atlas_v2.2.pit in PIT, and "Re-Partition" checked
Let your phone fully boot into the OS and verify everything is working correctly
Remove your battery
ODIN the CWM Recovery package ROM from this post
While reinserting your battery, hold both the volume keys and the power button down until a second after you see the Samsung boot logo
You should see CWM recovery now
Flash the SuperClean ROM from this post, Wipe Cache/Dalvik Cache only.
Reboot. If you have installed the Voodoo ROM, then you should hear a Sexy Robot lady telling you that she is converting your partitions. This process will take 10 minutes or so. If you pull the battery, you will have to start all over again.
Let your phone fully boot into the OS and verify everything is working correctly
If you need to install a theme, reboot, enter CWM and flash theme, Wipe Cache/Dalvik Cache only.
Make a fresh nandroid backup. If you try to restore a Nandroid made with the old CWM, you will probably have problems.
Click to expand...
Click to collapse
If you do this and it still happens, install your apps one at a time. A lot of times it is a faulty application that's doing it (apps that mess with cpu speed/voltage, apps that control power settings, a clock app, and even youmail have all been blamed for it).
Another issue some people have is a certain lockscreen mod with music controls.
str8havoc said:
I'm running the newest SC and I keep running into this prblm. I've unrooted and rooted thinking that would fix it. I've ran a pacth file hoping it would be fixed.
I have been reading some post about it and really haven't found the fix or I just missed it. Can some one point me in the right direction.
Sent from my SCH-I500 using Tapatalk
Click to expand...
Click to collapse
Are you running setcpu ? And if u are and u have a profile for when the screen is off, disable it. That should to the trick
Sent From My Samsung Galaxy S Fascinate Using XDA Premium App - Running Superclean 2.9.1 - 2.2 Froyo
sneakysolidbake said:
The right direction would be asking your questions in Q&A.
Sent from my SCH-I500 using Tapatalk
Click to expand...
Click to collapse
Way to be the post police, but that post was completely uncalled for. You didn't help in the slightest bit. At least the person under you had the courtesy to try and give him a solution, while telling him its in the wrong section.
Thacallmehess said:
Way to be the post police, but that post was completely uncalled for. You didn't help in the slightest bit. At least the person under you had the courtesy to try and give him a solution, while telling him its in the wrong section.
Click to expand...
Click to collapse
Your post isn't helpful to the forum at all, at least there's some community members who like to help keep our forums organized and clean so our Mods aren't overwhelmed. (See how easy that was)
@ OP, there is definitely a SOD patch somewhere in the Fascinate forums that Adrynalyne put out a bit back. I apply it along with the Camera mod every time I flash any new version of Superclean based on EB01/EB16. I'll see if I can post a mirror later when I get back home and you still haven't found it.
The SOD patch is already incorporated in to the latest SC. Gizmodroid's process (based on Adryn's solution to problems with SC2.7 iirc) is your best bet at this stage and worked for me. I would also recommend avoiding TiB as much as possible based on Adryn's comments in the SC2.9.2 thread. If you use Gizmodroid's process, please post your results in the relevant thread. I'd be interested in finding out the degree to which that process solves the issues generally.
I had the same problem. Follow the directions above flashing the stock and then upgrading and avoiding the apps noted above (I think youmail was a big part of my problem) and you should be good to go.
GizmoDroid said:
Questions go in the Q&A subforum.
Here is the only answer that you will probably get that will work (taken from the CWM thread):
If you do this and it still happens, install your apps one at a time. A lot of times it is a faulty application that's doing it (apps that mess with cpu speed/voltage, apps that control power settings, a clock app, and even youmail have all been blamed for it).
Another issue some people have is a certain lockscreen mod with music controls.
Click to expand...
Click to collapse
Thanks everyone for the fast replies even the one telling me i was in the wrong section. Sorry about that
I use both Youmail and the clock app all the time, so thats probbealy why i'm getting the SOD. I also install my apps from my SD card using Astro File Manager and it sounds like that could be causing my problem to.
I installed SetCPU and set the min. to 200mhz, hope that will fix my problems if not
Q1: can I download another clock app and be ok or will it do the same thing
Q2: is there any way of fixing the Youmail app or should I use another voice mail app.
Just want to thank everyone that keeps XDA up and running you guys rock. Love this Forum!
its funny this was posted today since i was literally coming to the forums to post about this very issue.
i have never had the SOD until i followed the instructional to flash back to EB01 with the new CWM.
it started waking slow a day after the wipe and reload, progressively getting worse. i started getting it yesterday bad where i had to restart the phone 4 or 5 times a day to wake it up. then by last night the phone would either freeze, or the 3G or wifi would show as working but i got errors saying no network connection then it would freeze.
PREFACE : FROM MY OWN experience it must be caused by one of 3 things. either the CWM itself, superclean rom, or something with the EB01 file. i have not installed any new programs since the ODIN flash, i did not restore data with TIBU, and i dont use Youmail.
i have also tried reflashing the modem and tried a nandroid restore from the instant i got it running after new cwm proceedure.
its still doing it and has never done it before the flashing.
EDIT: by the way i just realized that my signature here is wrong - forgot to change it.. running stock superclean 2.9.2 with the included kernel, no theme
Samsung Fascinate
SuperClean 2.9.2 & 3/30 -50 Voodoo
Nitro Vivid 1.0 Theme
Member of Android Anonymous, as a recovering Android bricking addict. I have been brick free for over 30 days.
mrjake1970 said:
its funny this was posted today since i was literally coming to the forums to post about this very issue.
i have never had the SOD until i followed the instructional to flash back to EB01 with the new CWM.
it started waking slow a day after the wipe and reload, progressively getting worse. i started getting it yesterday bad where i had to restart the phone 4 or 5 times a day to wake it up. then by last night the phone would either freeze, or the 3G or wifi would show as working but i got errors saying no network connection then it would freeze.
PREFACE : FROM MY OWN experience it must be caused by one of 3 things. either the CWM itself, superclean rom, or something with the EB01 file. i have not installed any new programs since the ODIN flash, i did not restore data with TIBU, and i dont use Youmail.
i have also tried reflashing the modem and tried a nandroid restore from the instant i got it running after new cwm proceedure.
its still doing it and has never done it before the flashing.
EDIT: by the way i just realized that my signature here is wrong - forgot to change it.. running stock superclean 2.9.2 with the included kernel, no theme
Click to expand...
Click to collapse
Are you using the voodoo lag fix?
I think the majority of the incompatibility people are seeing with the fixed cwm is might be some broken compatibility with rfs. It's supposed to be able to handle both, but I think changes in jt's initramfs or changes in the project voodoo files in the kernel that CWM is put into are the root of the problem.
Maybe I'll get some time this weekend to look at it.
In the meantime, everyone should go voodoo/lagfix
yeah giz, im using the superclean "stock" voodoo...
r
tonight im going to go flash happy with the original odin file i used to bump to froyo, and the other old cwm with the broken fixpms and the non fixed superclean 2.9.2 and see if that helps.
i cant be late for work again tomorrow with no alarm from a frozen phone lol
Samsung Fascinate
SuperClean 2.9.2 Voodoo
Member of Android Anonymous, as a recovering Android bricking addict. I have been brick free for over 30 days.
What is the sleep of death?
Update...
I reflashed the original EB01 tar file, modem and the 3/30 red CWM, along with the original copy of the non-fixed superclean 2.9.2 ROM and i am running fine so far with no SOD issues.
As long as this holds true for the remainder of the day I'm going to flash the updated CWM tonight to try and narrow down which of the 3 things i suspect in my previous post is causing it.
Samsung Fascinate
SuperClean 2.9.2 & 3/30 -50 Voodoo
Nitro Vivid 1.0 Theme
Member of Android Anonymous, as a recovering Android bricking addict. I have been brick free for over 30 days.
I downloaded setcpu and put it to 200mhz and been running fine since yesterday. I hope it will last the rest of the day.
Sent from my SCH-I500 using Tapatalk
created a sleep of death..
so, guess what? i created the sleep of death on my phone, and i know exactly what caused it.. not only that, but remembering back to my last sleep of death experience - it was the same exact scenerio..
i was running EC10 debloated, jt's 4/8 voodoo.. i flashed a theme to check it out.. didnt like it, so i re-flashed EC10 over it, with wiping dalvik and reg cache..
booted fine, however i started to notice clock lag almost immediately.. screen went off, and next time i tried to open the phone, i had to hit the power key 4 times before it would light up.. sounded familiar to me from last time, so i let it go about 1.5 hours.. sure enough, would not wake up.. had to pull battery to get it to boot..
i did a nandroid back to prior to the theme flash, and seem to be running ok.. however i am going to do the "clean" flash again tomorrow back to EB01 again just to be sure..
im convinced that is what caused mine both times..i will also be doing that every time i get tired of a theme instead of just flashing a new ROM..im guessing themes are leaving pieces parts behind somewhere that don't play nice with a ROM reflash over it..
I have been having SOD issues ever since I rooted and got set up on SC 2.9.2. However today, I decided to leave my GPS on and since I did that I have not had any SOD. Granted today is not a perfect example because not 45 minutes went by without using my phone, but it seems to have made things better for now, except my battery drains because of it.
Here is the Tutorial I used for Root
http://www.fascinateforums.com/foru...21-how-root-your-fascinate-install-froyo.html
Then I used this tutorial for SC 2.9.2 (non Voodoo, yes i got the right zip)
http://forum.xda-developers.com/showthread.php?t=983395
I'm running
Firmware Version
2.2.1
Baseband version
S:i500.04 V.EB01
Kernel version
2.6.32.9
Build Number
SCH-I500.EB01
I did TiB but have since uninstalled and used My Backup (free). I'm using GoLauncher and related apps. I do use YouMail and will not stop. I know its redundant but I installed the SOD patch too.
I'm going to try all the bandaid fixes first before re-flashing everything.
Search adrenalyne's threads. He had one with a sod patch.
Sent from my SCH-I500 using XDA App
This phone was an insurance replacement from ATT, so alway a bit wary of these refurbished phones.
So for the longest time it has always been a bit glitchy, hanging, and unstable. I assumed it was a software problem, and something i had done wrong when flashing...but now I am wondering if maybe my phone is a lemon. Lately it has been rebooting randomly on its own,
I wanted to try flashing back to stock, just to start from scratch, and I did with Da G's stock rom . Then i just rooted it with Da G's root, and put on CWR. Then I flashed King Kang Rom. It's been still real buggy. Maybe I need to to stock ICS or JB then flash a ROM? OR maybe it's just this phone....either way not real happy with the stability i've been dealing with.
If youve tried multiple roms and stock roms and its still buggy then its probably the phone, I have got so many replacement phones that were duds
Are you doing a wipe between all those roms or just flashing one over the other? That could be a major problem that is easily fixed.
Yes, i do full wipes/factory reset in CWM every time.
I know i have seen some guys say you must flash like 3 times, so maybe i'm not flashing it enough times or something..? i also saw someone say don't touch your phone for 15 minutes after flashing. i have no idea if these tricks actually work or what. doesn't seem to be a definitive rule book on how to flash the right way
How are you restoring your apps? TB or letting Play reinstall them?
using TB. I usually do a just apps reinstall, then data
Was the TB backup from a different version of android, i.e. GB, ICS then installed on JB?
yes, i did create it on an ICS rom. you think that could be causing me problems?
Good possibility. I had the same issue. Moved from CM9 to CM10 and restored through TB. Lots of FC and reboots. Wiped and let Play reinstall everything, now its smooth.
great thought and worth a shot if that's what could be causing a problem. so did you lose all your data then with all apps? msgs, etc? sucks to start from complete scratch. i'll even miss call log
Lost data, but was able to d/l everything else. Messages and call logs were gone. It is worth it to have a working phone with out glitches. Let me know if it works.
Well a good test is to install a known solid ics problem free ROM like Padawan or Black ice? (exact name escapes me). If it works for u then over clock it to 1836 with setcpu and u will have a ROM VERY close to the JB rom smoothness but actually works.
If u still have problems then u may very well have a flaky phone.
(Oh yeah don't get to worried about stuff like wipe 3 times etc...old wifes tales. I haven't done that for over a year on 3 android phones. ). Also it is Safe to restore apps AND data with titaniumb (just not system data).
Sent from my SAMSUNG-SGH-I717 using Tapatalk 2
+1 on the old wives tale. Seems more like a placebo effect. I only wipe once, and I've flashed roms on tons of phones.
Sent from my Galaxy Nexus using xda premium
tried installing padawan...so far so good, have not overclocked yet....will report back
Some roms will format your system partition prior to flashing the rom while others do not.
Beyond the wipe of data, cache, dalvik and such, it is wise to go into " mounts and storage" and format the system partition while in CWM recovery.
This ensures that nothing remains on the device before the new rom image is pushed to the system partition.
I agree that wiping 3 times is a bit over the top, but wiping the entire image base before flashing a new one is almost always mandatory.....g
For future reference, you can back up call and sms logs and restore them without causing lags or fc. The logs are simple .xml files.
What's good, guys? I'm using CM10.0 (relatively)stable on my SGH-i717. I've used the bundled kernel as well as the h0tcakez kernel (currently using that) 3.0.2 and the UCLF6 modem.
These random reboots are exactly what they seem, random. I haven't been able to accurately fund a concrete reason they appear and I've done numerous swaps of sdcard, battery, radio and firmware. Everyone else seems particularly stumped on this one, so this thread is just me doing digging on a good way to read the logs from the last boot. I've tried outputting logcats to a text file on my external sdcard but I have only succeeded in filling up my sdcard or having terminal emulator crash. What I'm going to try next is take my SIM out, put it in my captivate, then plug the note up to my computer, use adb to pull the log and/or the kmsg to my desktop and use tasker or something to run some apps in a cycle to (hopefully) automate the process.
I used the search function and didn't find any threads like this (maybe in blind).
Anyone else have any good suggestions?
Wipe your phone...
I was having pretty much the same problem. I have BB insurance on it, but wanted to see if I could figure out something software wise first. Since I rooted, I've installed pretty much every i717 ROM. I finally settled on flapp's cm10 based one, as it seemed the most stable. After a week of running it, I started to get about >10 random reboots/day. I tried flashing different roms, and sticking with them to no avail. My last ditch effort was to return the phone to stock, see if it still happened, if so, bring back to BB. I hooked it up to Kies, did an emergency flash thru there to get back to stock, but couldn't bring myself to keep it stock for more than 30 seconds. I immediately rooted, and flashed ParanoidKANGdroid. I have only had 1 random reboot in the last 4 days. I'm hoping it stays the same. I briefly tried Xylon and supernexus, but came back to PK, where I will stay (for now anyway). Hope this helps.
Use kies to bring back to stock. (you need your serial number for this, not IMEI)
Root using some method from super everything thread.
Flash favorite rom and enjoy
Also, if you have to update Kies, wait for it to finish. It gets to the point where you think something is wrong and you want to throw your computer away. But after the hangups, it actually finishes the sequence....
Noob android modder...
HTC unlocked and rooted my Rez back in late Dec 13. I have had battery issues ever since. I know (through extensive reading these forums and others) this isn't due to root. And my issues are beyond battery, No ROM I have tasted has been stable. Tachyon ION, Paranoid Android, Cyanogenmod 11....similar issues with each, some worse than others. I downloaded BetterBatteryStats yesterday to try and diagnose this, but I am skeptical this is the problem. Biggest issue: battery doesn't give a true reading of its charge, or the rom running (again, all of them) can't accurately read the battery. Case in point: yesterday I wiped phone and installed the cyanogenmod 11 from NEO. I installed better battery stats and fully charged. Battery lasted less than 2 hrs. Plugged in at 10% and let charge for a few hrs. When I unplugged, cyanogen tells me that battery has 44% charge. After immediate reboot, battery shows 94% charge. This has been consistant over the different ROMS.
The other big problem is the constant reboots I experience. Many apps seem to overload the system and forced reboots happen. I realize that I am likely the problem, but I can't seem to figure out why.
I apologize, I know its an old bit, complaining about battery life after root, but compounded with the instability of the ROMS...I suspect I am doing something wrong that I haven't figured out.
Questions:
1. Do I need to manually flash a kernel after/before flashing a ROM?
2. Does being S-ON have anything to do with this?
3. Any tips?
I appreciate any help
loswr86 said:
Noob android modder...
HTC unlocked and rooted my Rez back in late Dec 13. I have had battery issues ever since. I know (through extensive reading these forums and others) this isn't due to root. And my issues are beyond battery, No ROM I have tasted has been stable. Tachyon ION, Paranoid Android, Cyanogenmod 11....similar issues with each, some worse than others. I downloaded BetterBatteryStats yesterday to try and diagnose this, but I am skeptical this is the problem. Biggest issue: battery doesn't give a true reading of its charge, or the rom running (again, all of them) can't accurately read the battery. Case in point: yesterday I wiped phone and installed the cyanogenmod 11 from NEO. I installed better battery stats and fully charged. Battery lasted less than 2 hrs. Plugged in at 10% and let charge for a few hrs. When I unplugged, cyanogen tells me that battery has 44% charge. After immediate reboot, battery shows 94% charge. This has been consistant over the different ROMS.
The other big problem is the constant reboots I experience. Many apps seem to overload the system and forced reboots happen. I realize that I am likely the problem, but I can't seem to figure out why.
I apologize, I know its an old bit, complaining about battery life after root, but compounded with the instability of the ROMS...I suspect I am doing something wrong that I haven't figured out.
Questions:
1. Do I need to manually flash a kernel after/before flashing a ROM?
2. Does being S-ON have anything to do with this?
3. Any tips?
I appreciate any help
Click to expand...
Click to collapse
Answers to your first two questions:
1) After (although it S-ON it technically shouldn't matter)
2) No
Here are some tips, this could be as simple as a battery going bad, i consider a replacement one, either original HTC or Laza would be my recommendation. Also, I would consider going S-OFF, then going through @REV3NT3CH's full downgrade/upgrade guide from start to finish, this seems to be fix for many "odd" issues in the Rezound, I can't really explain why and it somewhat defies logic to downgrade to the oldest version of software available and then upgrade step-by-step through every version, but it has definitely shown it's value as a working solution to many issues.
I kind of suspect a battery, charger, charge port, bad cable, or even dirty/tarnished contact here though... three hours on the charger on a good stock battery that is charging correctly should bring it near full after 3-4 hours, if you are only getting it to 44% something is not right.
acejavelin said:
I kind of suspect a battery, charger, charge port, bad cable, or even dirty/tarnished contact here though... three hours on the charger on a good stock battery that is charging correctly should bring it near full after 3-4 hours, if you are only getting it to 44% something is not right.
Click to expand...
Click to collapse
That's the thing, it says 44% when I pull it off the charger, but if I reboot it, it says 90%+. Multiple cables/ports have been used. Same issue.
Regarding your statement about flashing a kernel post ROM flash, I attempted this with Tachyon and the fuzzy kernel yesterday. ROM installed as expected, it crashed a few times while installing backups from Titanium, and then I flashed the Fuzzy kernel. After the kernel flash the phones screen wouldn't work....I believe the phone was booting, but no screen, just LED notificaion light. Thats when I started over with the Cyanogenmod 11 ROM, which has been the most stable.
Thanks for the advice, I will likely attempt your suggestion about downgrading/upgrading.
loswr86 said:
That's the thing, it says 44% when I pull it off the charger, but if I reboot it, it says 90%+. Multiple cables/ports have been used. Same issue.
Regarding your statement about flashing a kernel post ROM flash, I attempted this with Tachyon and the fuzzy kernel yesterday. ROM installed as expected, it crashed a few times while installing backups from Titanium, and then I flashed the Fuzzy kernel. After the kernel flash the phones screen wouldn't work....I believe the phone was booting, but no screen, just LED notificaion light. Thats when I started over with the Cyanogenmod 11 ROM, which has been the most stable.
Thanks for the advice, I will likely attempt your suggestion about downgrading/upgrading.
Click to expand...
Click to collapse
Always use the kernel that comes with a ROM, until you know it's stable and unless you have a good reason to switch... it is the best match to the ROM and the benefits you get from another kernel are generally marginal at best unless you need a specific feature that is not included in the ROM's kernel.
Proper sequence when installing a ROM when S-ON would be to wipe everything but external SD, then flash ROM, immediately reboot into bootloader and start fastboot, flash the boot.img with "fastboot flash boot boot.img" then reboot. Any other sequence could give questionable results.
Using Titanium backup to restore information in between JB and KitKat (either way) is not recommended, even with root access TiBu has issues restoring into /system in KitKat. It is highly recommended to reinstall all apps from the Play Store and use something like SMS Backup & Restore to handle text message migration.
I would again recommend a new battery, and going S-OFF especially now that the "wire trick" is no longer required using Rumrunner or Firewater S-OFF, then going through the downgrade/upgrade process I mentioned earlier.
So I have been unsuccessful at getting Windows drivers working for my rez. HTC sync and Windows used to identify it, but after I originally rooted it back in Dec, I wiped my laptop clean and set up a dual boot. Since then I haven't been able to get HTC sync to identify the phone, and ADB only works if I am in the TWRP or bootloader. Same with mounting and moving files, recovery only. Since the rumrunner S-OFF exploit needs me to be in Android, I'm in a pickle.
Things I have tried:
Current HTC sync software (Doesn't recognize the phone)
Downloaded and installed the driver from the Rav3nt3ch guide mentioned earlier
Also tried the old version of HTC sync that is mentioned in the same article
acejavelin said:
I can't really explain why and it somewhat defies logic to downgrade to the oldest version of software available and then upgrade step-by-step through every version, but it has definitely shown it's value as a working solution to many issues.
Click to expand...
Click to collapse
to make sense of it. the reason it works is through some flashings or wrong deleteion of files the files that are integrated in system that a ROM does not have these RUU.exe files and OTA (ph98img.zip) files do have and repairs the phone to its neccesary needed state again. a good example to prove it is a typical rom is about 160mb in size and only contains bare necessities really..where as the ruu or ota is usually around 600mb in size and also full flashes the phone to proper partitions and such...as stated in my guide be sure to let phone fully boot and go through first setup of those particular roms....some people skip this step thus not activating their verizon service
---------- Post added at 02:14 PM ---------- Previous post was at 02:12 PM ----------
loswr86 said:
So I have been unsuccessful at getting Windows drivers working for my rez.
Click to expand...
Click to collapse
Are you using windows 8? if so thats your issue.... drivers and programs only fully work and recommended for Windows 7 only bud
Edit: As for your battery issue...is your phone getting rediculously hot....if so this is a hardware issue based on the HT1 motherboards and is not fixable for anyone....my current rez has this issue and is an HT1 motherboard...also very typical issue for this version of the rez...also after a full charge have you tried wiping the battery stats in recovery? this will help give a much more accurate reading
REV3NT3CH said:
Are you using windows 8? if so thats your issue.... drivers and programs only fully work and recommended for Windows 7 only bud
Edit: As for your battery issue...is your phone getting rediculously hot....if so this is a hardware issue based on the HT1 motherboards and is not fixable for anyone....my current rez has this issue and is an HT1 motherboard...also very typical issue for this version of the rez...also after a full charge have you tried wiping the battery stats in recovery? this will help give a much more accurate reading
Click to expand...
Click to collapse
Windows 7. The drivers worked fine back in December prior to me wiping my HDD and setting up a Ubuntu/Win 7 dual boot. I can use ADB just fine if the phone is at the bootloader/recovery. Its only the OS the causes a problem.
Yes, the phone does get quite warm, though since switching to CM11 both heat and battery have improved. Still unacceptable, but improved.
I'll attempt to wipe the battery stats after it charges back up, but I don't see that option in the TWRP 2.5.0.0 I have installed.
**//After being out this evening, I got home and plugged the phone in about 30 min ago. It was at 8% according to CM11. After rebooting into the recovery, TWRP informs me that there is a 66% charge.
loswr86 said:
Windows 7. The drivers worked fine back in December prior to me wiping my HDD and setting up a Ubuntu/Win 7 dual boot. I can use ADB just fine if the phone is at the bootloader/recovery. Its only the OS the causes a problem.
Yes, the phone does get quite warm, though since switching to CM11 both heat and battery have improved. Still unacceptable, but improved.
I'll attempt to wipe the battery stats after it charges back up, but I don't see that option in the TWRP 2.5.0.0 I have installed.
**//After being out this evening, I got home and plugged the phone in about 30 min ago. It was at 8% according to CM11. After rebooting into the recovery, TWRP informs me that there is a 66% charge.
Click to expand...
Click to collapse
wait your on twrp 2.5.0.0 theres a big issue there and prolly why battery stays showing at 66%....you need to be on 2.6.3.0 for jb or kitkat bud....as for wiping battery stats i believe that may be cwm
REV3NT3CH said:
wait your on twrp 2.5.0.0 theres a big issue there and prolly why battery stays showing at 66%....you need to be on 2.6.3.0 for jb or kitkat bud....as for wiping battery stats i believe that may be cwm
Click to expand...
Click to collapse
Clockworkmod 6.0.3.1 is now my recovery, fully installed on the phone. I had been using cwm as the recovery img that I would fastboot boot, then install a ROM. But the actual recovery installed on the phone was TWRP 2.5. Might this be the underlying cause of much of my boggle?
loswr86 said:
Clockworkmod 6.0.3.1 is now my recovery, fully installed on the phone. I had been using cwm as the recovery img that I would fastboot boot, then install a ROM. But the actual recovery installed on the phone was TWRP 2.5. Might this be the underlying cause of much of my boggle?
Click to expand...
Click to collapse
could be...but why a low version of clockworkmod too.... http://forum.xda-developers.com/showthread.php?t=1914215 this is what you want....and if flashing plain andy that uses philz touch and a certain install method
The battery power can not be recognised by the phone?
REV3NT3CH said:
could be...but why a low version of clockworkmod too.... http://forum.xda-developers.com/showthread.php?t=1914215 this is what you want....and if flashing plain andy that uses philz touch and a certain install method
Click to expand...
Click to collapse
Thanks for the link. I simply dl'd what was at the cwm website for the Rez.
loswr86 said:
Thanks for the link. I simply dl'd what was at the cwm website for the Rez.
Click to expand...
Click to collapse
eh...always search the threads bud...all of what you need and updated is here
---------- Post added at 07:50 PM ---------- Previous post was at 07:49 PM ----------
Hermosa said:
The battery power can not be recognised by the phone?
Click to expand...
Click to collapse
on older twrp or miscompiled recoveries it will simply just read as 66% and stay there....a good example...phils touch needs this battery reading part fixed as well as it shows 66% for battery currently
6.0.3.6 installed. Hopefully this oversight is what it takes to improve my experience with android modding. Thanks for your help fellas.
I don't remember having this much trouble modding my old HTC tilt back in the day.
Flashing clockworkmod 6.0.3.6, reinstalling CM 11 via CWM and then flashing the boot.img seems to have fixed my battery issues. After a few days of use, battery is holding charge much better. A note on what I think I was doing wrong, for others:
-I had originally flashed TWRP 5.X
-Then I followed this article explaining how to install custom roms whlie s-on
-I then loaded the various custom roms via the above method with the CWM 6.0.3.1 (Listed on their website)
-Chaos insued
Don't do this.
So my girlfriend's EVO 4G LTE is a bit of.. well, I'm gonna say bastard. I'm not new when it comes to rooting devices but I've never had to deal with one that fought me so much.
I've been through this adventure many times with it, and it gets more complicated each time. Here is what's happened with it so far.
It was stock, and it was terrible. It lagged so much, despite factory resets, that apps like google maps were completely unusable. It got no battery life AT ALL, and was generally freeze-happy and miserable.
So then I s-off'd it and after learning all its quirks, installed recovery and CM 11.2 (I think? It's been a year)
This worked great! For.. a few days. The phone worked, we went on vacation to a roaming area where Sprint had no coverage. We come back, and only the data works, texts and calls do not, and the phone acts like it's not activated. Yay. All attempts to get it activated are met with failure, much to the confusion of the poor sprint person on the line. The phone just will not take, at all. (damn lack of real sim cards..) We tried recovering back to a backup from twrp of the stock firmware but that won't work either? It wouldn't register with sprint even on the backed up version of stock sense. The phone seemed dead at this point. Bricked radio?
So we give up. We bring it to the sprint store, and they do some magic to it, and its back to stock, slow and terrible, but functional. We don't touch it until about three weeks ago.
But, my girlfriend is tired, again, of the terribleness, and asks me to try again. Okay, sure.
I install TWRP again, so far so good. The phone is still S-OFF from last time, which is nice. I go to install CM11.2 from the files used from last time (the MD5 does check out correct) But, the phone complains about not having a new enough bootloader. ???? (So I assume sprint downgraded the bootloader in the process of fixing it. somehow)
I forget the exact numbers, but we can't install CM11.2, only 10. or 10.whatever. the newest 10. Okay, fine. I gather a new set of cyanogen files, gapps, whatever, and flash all of that, so far so good.
This time it works, and stays working! Yay! So I thought.
As it turns out, its on a very old version of android (so old that it goes into a special usb file host mode when usb is plugged in) and more importantly, the camera is TERRIBLE. I've read that the evo 4g lte uses a special ImageSense chip to boost camera performance, and that cyanogen 10 does not support it. I can tell, because the camera is absolutely terrible. The battery life also is terrible, presumably because it lacks optimizations. It had way better battery life on CM11.2 when it worked. Other then that, its working just fine, but the camera is just unacceptable.
So, I want to know what to do from here. I see a few paths.
plan A:
update HBOOT to a newer version to allow the install of CM11.2
(how do I do that? I heard you have to use an RUU, but which RUU? I read that there is some touchscreen driver that is an issue depending on what version you run)
(Once I install the ruu is it business as usual, install twrp and then flash cyanogen like normal? Will it do the crazy not activation thing again? was that a fluke??)
plan B:
update HBOOT, but to a much newer one that allows the install of CM12 or whatever the newer ones are. Presumably updating past the touch screen driver issue and not allowing us to go back to an old version.
(once again, what do I need to do that? Is this advisable? I quite prefer the idea of running a newer version. So if this is the better idea, I will do it.)
I thank you greatly for your help. I'm not used to it being this complicated. I've read a lot of things about this phone and it seems very conflicting at times. I just want to get straightened out.
yeah, it's probably running like crap because the firmware is so out of date.
use this RUU http://forum.xda-developers.com/showthread.php?t=2653730
then re-flash twrp and another ROM if you want (i've been running cm12.1 for MONTHS) but she might be able to survive just like that. only fear would be staying vulnerable to security threats, but you've been living in that house this whole time anyway.
for a good while i was running this stock 4.3 with root and some xposed modules installed to get the cm functionality that i missed. but seriously, run the RUU, let it activate, then go under settings and update profile and PRL, fire up maps/navigation with GPS on so that it gets a good lock and its cache populated, then you should be good from there.
Thank you!
Can I use the same utility that I used to flash twrp (that one-click thing that seems to support a half million phones) or do I need something special? This sounds very easy to do. Almost too easy, given that the story of this phone's life is that the easiest thing I've ever done to it was take it completely apart to replace its battery.
never used the one-click stuff. flashing recovery via fastboot is simple enough.
get the adb tools, here's some easy instructions for that http://lifehacker.com/the-easiest-way-to-install-androids-adb-and-fastboot-to-1586992378
get the latest twrp from here https://dl.twrp.me/jewel/
then follow these directions to flash twrp https://wiki.cyanogenmod.org/w/Install_CM_for_jewel#Installing_a_custom_recovery_using_fastboot
if not installing cm or any other rooted rom (you want to root stock) get supersu from here http://forum.xda-developers.com/showthread.php?t=1538053 and use the twrp installable zip
If you've gone through the trouble to S-Off, then fastboot flash the latest TWRP (3.0.2.0, I believe), which supports the new partition layout (extra 4gig of internal SD space).
From there, flash the official 651.4 developers version, go through the device setup which updates your PRL, then shut it down and reboot to TWRP and flash the latest CM12.1 and a proper gapps package (I use "stock", which is a bit much for some, but I like having everything available to me).
The one thing I do that most don't is to disable zRam and enable swap with my own script I wrote specifically for the external SD I formatted as vFat/ext4/swap.
After doing all this, I do not have the issues you seem to have, and the PRL seems to stay from the last install of stock Sense 5. Even with all the apps I have installed, it's still fairly snappy. Facebook/Messenger, and other memory hogging apps run smooth with no discernable lag, unless there's network issues.
YMMV, but look into using an app like "Ampre" to measure battery life and gauge if the battery is going bad or not.
Outside of that, there's not much left to do with these older devices that hasn't been done already.