Now, normally I wouldn't even bother posting such a trivial thing, but it has peaked my interest and I'd like some community feedback.
After several wipes of all partitions (dalvik, cache etc...) and a fresh reinstall, titanium restore, underclocking and undervolting, I can usually manage 12-14 hours total on time with 1.5 hours on-screen, on any ROM, tw, aokp, cm, doesnt matter. This even extends to GB 2.3, ICS 4.0 and JB 4.1.
Now, here is where it gets interesting. When I back up the ROM setup in cwm, and perform a fresh ROM install, I'll set it up again and try it out for a few hours. Not liking the setup, I'll go back into cwm and perform several wipes again and complete a restore.
All of a sudden battery performance jumps to posted below. So u be the judge, and tell me if this basically backup restore method worked for u.
So you backup, wipe, install a new rom, wipe and then restore the first rom? Theoretically you're exactly where you began.
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
promiseofcake said:
So you backup, wipe, install a new rom, wipe and then restore the first rom? Theoretically you're exactly where you began.
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
Click to expand...
Click to collapse
Basically yeah, sounds stupid I know. You'd think with my knowledge level I'd at least be able to explain why, I'm theorizing its equivalent to a more complete fix permissons
icenight89 said:
Basically yeah, sounds stupid I know. You'd think with my knowledge level I'd at least be able to explain why, I'm theorizing its equivalent to a more complete fix permissons
Click to expand...
Click to collapse
I'm theorizing that you don't use the backup as much as you use the new ROM. Cause you are exactly where you where before. It does not change or fix any permissions. They are exactly the same. Same with dalvik and cache. I would love for this to be true but I gotta go with placebo here.
hechoen said:
I'm theorizing that you don't use the backup as much as you use the new ROM. Cause you are exactly where you where before. It does not change or fix any permissions. They are exactly the same. Same with dalvik and cache. I would love for this to be true but I gotta go with placebo here.
Click to expand...
Click to collapse
No placebo, and change of permission s is incorrect. A cwm backup/restore is basically a copy to/from partition with compression. Upon restore file permissions are set, just the same as they would be for any file system, be it NTFS, HFS+,or ext4. My point being that maybe some libraries in this process may have received read only or write privileges that weren't available before, possibly leading to the increase.
I use the ROM for days if not weeks at a time once I find something I like before backing it up to test something new and then restoring a few hours later. It is not a case of building up cache or dalvik cache. I understand your doubt but this is not a case of user ignorance, I'm quite well informed.
icenight89 said:
No placebo, and change of permission s is incorrect. A cwm backup/restore is basically a copy to/from partition with compression. Upon restore file permissions are set, just the same as they would be for any file system, be it NTFS, HFS+,or ext4. My point being that maybe some libraries in this process may have received read only or write privileges that weren't available before, possibly leading to the increase.
I use the ROM for days if not weeks at a time once I find something I like before backing it up to test something new and then restoring a few hours later. It is not a case of building up cache or dalvik cache. I understand your doubt but this is not a case of user ignorance, I'm quite well informed.
Click to expand...
Click to collapse
I wasn't trying to say you where ignorant. lol Hope it didn't come across that way. Rather I was trying to point out that maybe use was part of it. If you really feel that your getting better life after a restore I believe you but I did it myself yesterday and have seen NO improvement from it. I restored a ROM a was very familiar with and have used the phone the same way I always do. There has not been a noticeable difference in battery life after restore. Maybe we can get some other people to do the same and see if they get better or the same.
Interesting
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
xcrazydx said:
Interesting
Click to expand...
Click to collapse
You up for running a backup for a day and testing the theory?
I'll do it. But just to be sure of the process.
1. I back up my current (r4ins aokp)
2. Clean/full wipe whatever ROM
3. Run that ROM for a day
4. Restore.
I think I have the process incorrect somewhere.
Sent from my SGH-I727
Jhong209 said:
I'll do it. But just to be sure of the process.
1. I back up my current (r4ins aokp)
2. Clean/full wipe whatever ROM
3. Run that ROM for a day
4. Restore.
I think I have the process incorrect somewhere.
Sent from my SGH-I727
Click to expand...
Click to collapse
Nope. That's pretty much it lol
Let it be known that I should mention I went from what I consider TERRIBLE battery, (i.e. 12 hours total, 1.5 on screen) to the posted above after I backup and then restored. If you're already getting over 20 hours standby with 3 hours onscreen this will do absolutely zilch for u
icenight89 said:
Nope. That's pretty much it lol
Let it be known that I should mention I went from what I consider TERRIBLE battery, (i.e. 12 hours total, 1.5 on screen) to the posted above after I backup and then restored. If you're already getting over 20 hours standby with 3 hours onscreen this will do absolutely zilch for u
Click to expand...
Click to collapse
Well, i already do 20 hours+ with 4 or so hours screen on. So I'm out of the testing.
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
icenight89 said:
Nope. That's pretty much it lol
Let it be known that I should mention I went from what I consider TERRIBLE battery, (i.e. 12 hours total, 1.5 on screen) to the posted above after I backup and then restored. If you're already getting over 20 hours standby with 3 hours onscreen this will do absolutely zilch for u
Click to expand...
Click to collapse
Okay just got out of classes and no school tmw. So I'm ready. Going back to M6 until tmw.
BTW I get 12 hours with around 2-3 hr screen time normally with all location services on.
Sent from my SGH-I727
Sad to say after I restored I'm getting about the same battery life. I'm at 45% with about an hour of screen time. Total time its been on is about 2 1/2 hours.
Sent from my SGH-I727
Well that takes care of that. On a couple instances a backup restore has fixed low battery life for me, but if its an isolated incident it means nothing.
Worth a shot anyway, requesting thread b closed
icenight89 said:
Well that takes care of that. On a couple instances a backup restore has fixed low battery life for me, but if its an isolated incident it means nothing.
Worth a shot anyway, requesting thread b closed
Click to expand...
Click to collapse
Actually back during Gingerbread and ICS leaks I've had better battery life doing these steps, but I blew it off thinking my usage pattern might've been different. I'll keep you posted if i am able to replicate it as I tend to flash new ROMs often.
Catch you later.
Sent from my SGH-I727
Related
my phone keeps restarting itself and i was wondering if anyone knew whats wrong, i have the valhalla-blackedition and my kernel is Subtly Modified Stock with CWM5 + Voodoo Lagfix
You may wanna go to the development section and remove gremlins(eg start from scratch) there is probably an issue with you CSC.
First things first - by default - always go into CWM and do three things. Wipe cache partition, wipe dalvik cache and fix permissions. Then reboot and let your phone sit untouched for around 10 minutes and see how your phone acts. Next uninstall your recently added apps and see if that could be the issue. One by one. It is even a good idea to wipe caches after doing so.
What you described happening is something you would have done to the phone. VB is solid. If you can't undo it with the steps I suggested - then start over as the last poster suggested.
But when you mess with your phone - keeps tabs what you do so that you can undo it and/or not do it again.
And if you can't undo it - be hesitant restoring backed up data from TB or CWM. If you must restore - restore data for apps one at a time and see if your phone acts up so you can try and figure out the problem.
i Wiped cache partition and wiped dalvik cache hopefully that will fix it
i wiped the cache and delvik cache and it was working good and then again out of nowhere it started to keep rebooting randomly, is my only option to use the gremlin remover?? or can i do something more basic to see if it will solve my problem
Bryan (the guy that created the kernel you're using) thinks he and FBis251 may have found the issue with the random reboots. Bryan said it might be a couple of days, though, before we see anything about it.
I updated to the rc3 version of the kernel in the hopes that it would get better but it actually got worse for me. I've done a few steps in the gremelin remover, have flashed & reflashed, but the problem persists. Hopefully Bryan & FB have nailed this thing down and those of us suffering the issue will have some relief
thanks for the reply stephen_w, i will wait till FB releases a new kernel
I would go with the gremlin remover its very easy to use and doesn't take a lot of time it really works it taking out any little problems with the phone.
Sent from my galaxy s 4g using XDA app
m0bstr said:
thanks for the reply stephen_w, i will wait till FB releases a new kernel
Click to expand...
Click to collapse
If you haven't seen it already, it's out: [KERNEL] bhundven's SMS KJ6 v0.2.0 [Apr 11]
stephen_w said:
If you haven't seen it already, it's out: [KERNEL] bhundven's SMS KJ6 v0.2.0 [Apr 11]
Click to expand...
Click to collapse
That kernel was stable but there's battery drain issues
Sent from my galaxy s 4g using XDA app
im using the update right now and no more reboots
falcons2 said:
That kernel was stable but there's battery drain issues
Click to expand...
Click to collapse
Don't say that until you have tested it a few days. He released it less than 24 hours ago.
Bryan also stated in the OP for that kernel that it's still beta. There are/will be issues. He said somewhere in that thread that it seems what he and FB did to the kernel did not actually fix the random reboot issue, rather it prevents it from happening. They're working on it for us
I see the battery drain, too. I have to say though, it's better than having the random reboots. It's a "pick your poison" situation for the moment.
lumin30 said:
Don't say that until you have tested it a few days. He released it less than 24 hours ago.
Click to expand...
Click to collapse
That's true I should of given it more time
Sent from my GT-P7510 using XDA
I think right around now we're about at stock battery usage levels. It'll be just like when your phone was brand new and had all that bloatware that killed your battery.
stephen_w said:
It's a "pick your poison" situation for the moment.
Click to expand...
Click to collapse
How about go back to V0.0.2d which had no issues at all. Just can't do nand backups or restores from it. Also no BLN. It's a solid kernel and it's easy enough to keep it and V2 on the sdcard to flash between. Use V2 when in need of backup or restores. Used V0.0.2d the rest of the time until the kernel issues are resolved. Just a thought.
falcons2 said:
That kernel was stable but there's battery drain issues
Sent from my galaxy s 4g using XDA app
Click to expand...
Click to collapse
Battery Drains can be controlled significantly by the User even though some kernels perform better than others. No need to have apps,wifi,etc constantly running unless needed. Useful info @ http://www.makeuseof.com/tag/5-ways-cut-battery-drain-rooted-android/
tozo3 said:
Battery Drains can be controlled significantly by the User even though some kernels perform better than others. No need to have apps,wifi,etc constantly running unless needed. Useful info @ http://www.makeuseof.com/tag/5-ways-cut-battery-drain-rooted-android/
Click to expand...
Click to collapse
When I see these kinds of posts I have to ask. Why did you even buy a SMARTphone to begin with?
If there is issues with battery drain they need to be addressed. Either in the OS or the apps causing the drain. Putting a bandaide (the battery saver apps) on only make the issues worse. Why? Because then nobody reports the problems because they are unaware of the problems because of the bandaide.
I have had this problem for a couple of months not and just got sick of it. My battery percentage is stuck at 100%. I have tried everything; reflashing, clearing battery stats, using battery calibration tools, completely draining (a few times) and fully charging and clearing bat stats again to no avail. I can see in multiple places that the battery voltages levels are dropping but having no effect on the percentage.
My phone info:
G2x flashed with Cyanogenmod 7 11 01 2011 nightly (I can not up date for a few weeks as I am on a ship), Faux123-v0.4.7r.
Anybody experience the before or have a idea of a fix?
could be a few things...
1) have you tried any other rom/kernel combo's and does it still happen?
2) you say you are using faux123's kernel, if it is the DS version of it the battery driver percentage readings are a bit strange on that version. you could just be getting a VERY extreme case of that, try the CM version if you haven't already. (should be in the same thread as the DS version)
3) if you want to give it a shot, you could try using This. its a batch file that will completely and 100% wipe your phone (and the internal SD card) clean, its fixed some strange issues for people, and it might just help you too.
3) if none of the above work, try picking up a cheap battery on ebay/amazon for the phone, from what i hear you can get one in the $10-$25 range pretty easily. it could be that something in the battery itself is messed up thats causing it too.
Klathmon said:
could be a few things...
1) have you tried any other rom/kernel combo's and does it still happen?
2) you say you are using faux123's kernel, if it is the DS version of it the battery driver percentage readings are a bit strange on that version. you could just be getting a VERY extreme case of that, try the CM version if you haven't already. (should be in the same thread as the DS version)
3) if you want to give it a shot, you could try using This. its a batch file that will completely and 100% wipe your phone (and the internal SD card) clean, its fixed some strange issues for people, and it might just help you too.
3) if none of the above work, try picking up a cheap battery on ebay/amazon for the phone, from what i hear you can get one in the $10-$25 range pretty easily. it could be that something in the battery itself is messed up thats causing it too.
Click to expand...
Click to collapse
1. This only started happening without correcting itself this past ROM. I am currently out to sea and can not download a new one. I have a few previous ROMS on my computer that I can try.
2. I am using the more stable CM version of the kernel.
3. I would like to avoid a complete wipe at the moment as I will have no viable way to reload all of my stuff. I have done a NAND backup just though just in case.
4. Buying a battery would take weeks to get here. Will consider this if steps above don't work.
Thank you very much, going to go flash a different ROM right now!
iceman3kco said:
1. This only started happening without correcting itself this past ROM. I am currently out to sea and can not download a new one. I have a few previous ROMS on my computer that I can try.
2. I am using the more stable CM version of the kernel.
3. I would like to avoid a complete wipe at the moment as I will have no viable way to reload all of my stuff. I have done a NAND backup just though just in case.
4. Buying a battery would take weeks to get here. Will consider this if steps above don't work.
Thank you very much, going to go flash a different ROM right now!
Click to expand...
Click to collapse
yeah, if you can swing it, a full wipe is most likely going to help. otherwise either just try to live with it, or try dirty-flashing a new rom.
Ok, I tried the dirty-flash to no joy. Just broke down, backed everything up with Titanium Backup and did the complete wipe and install. Battery is back to normal. I would still really like to know what caused the battery not to register (before I did all of this, messed with the Cyanogenmod settings for status bar. Went back to just the icon of the battery and it showed a question mark with no level).
iceman3kco said:
Ok, I tried the dirty-flash to no joy. Just broke down, backed everything up with Titanium Backup and did the complete wipe and install. Battery is back to normal. I would still really like to know what caused the battery not to register (before I did all of this, messed with the Cyanogenmod settings for status bar. Went back to just the icon of the battery and it showed a question mark with no level).
Click to expand...
Click to collapse
You most likely f'ed up the system ui because of a bug in the status bar mods or a theme. Honestly most of the time these things are fixable, but the fix is a helluva lot more complicated and time consuming than just wiping.
I'm glad you got it worked out though.
Sent from my LG-P999 using Tapatalk 2
I would either flash a different kernel, flash a different rom or wipe EVERYTHING and start over.
its because you probably got a leak of one of the new nuclear batteries, so i think you can use it for like 5000 years or so, but with juice defender you might be able to get like 7500 out of it!...
just be sure not to under volt it too much! or els the fission becomes unstable...
and you know... Kaboom!
You have achieved infinite battery life. You are the envy of all smartphones.
Sent from my LG-P999 using xda premium
wyldkard said:
You have achieved infinite battery life. You are the envy of all smartphones.
Sent from my LG-P999 using xda premium
Click to expand...
Click to collapse
I don't know why but when I read that, the voice in my head sounded like Beavis..
Try it it sounds funnier...
Sent from my LG-P999 using XDA
iceman3kco said:
I have had this problem for a couple of months not and just got sick of it. My battery percentage is stuck at 100%. I have tried everything; reflashing, clearing battery stats, using battery calibration tools, completely draining (a few times) and fully charging and clearing bat stats again to no avail. I can see in multiple places that the battery voltages levels are dropping but having no effect on the percentage.
My phone info:
G2x flashed with Cyanogenmod 7 11 01 2011 nightly (I can not up date for a few weeks as I am on a ship), Faux123-v0.4.7r.
Anybody experience the before or have a idea of a fix?
Click to expand...
Click to collapse
hi.
Do you have fixed this problem ?
I was on CM7 then went to AOKP, didnt like it and went back to CM7, now my phone is super laggy.
I have found out it is running at 200mhz almost constantly unless i set my minimum to 800 or 1200, but then my battery would die in minutes.
Nothing seems to fix this. it is SOOO bad that the skateboard cm7 droid dude, lags. the first samsung logo takes like 30 seconds or more, then when it jumps to the skateboard guy it lags and the circle arrow skips frames horribly. not like usual.
The only thing i can think of is when i was on AOKP (ICS) i "v6 super charged it" when i went back could there be remnance of issues?
please help i am pulling my hair out in stress and annoyance.
I have reflashed 5 times, reset with heimdall to stock, then back to CWM recovery RED, (entropy) and back to CM7... no fix. im wondering if a certain file is causing the cpu to underclock.
what file do i delete and reset.
please help
Go back to stock...and then once on stock go to settings>privacy>reset to factory defaults>format USB drive....let it do its thing and you should be good...make sure you back up important data first...this will wipe everything!!!!
Sent from my HTC PH39100 using XDA
is this honestly my only option? seems a bit harsh to wipe everything
Skwerl23 said:
is this honestly my only option? seems a bit harsh to wipe everything
Click to expand...
Click to collapse
Yes...remember you dealing with files...folders...that sometimes leave a trail of stuff....so a good wipe and kill all, reload clears...so being lazy will have it's effect....
My thing if ya gonna do it..do it right, work now, rest/enjoy it later......
all i should have to back up is my titanium, and my pictures i believe.
im not against doing it right, problem is i have reflashed probably 50 times, and this is the first time ive had an issue. its weird.
so when i reset to stock, it boots normal speed. im not so sure its the folders. this is so weird. but im trying this step anyhow
Skwerl23 said:
all i should have to back up is my titanium, and my pictures i believe.
Click to expand...
Click to collapse
Pics should be on your ext sd card...and yes you can back up via tibu your apps only...
usb wiped from stock. no change. am i missing a certain kernel?
fixing permissions helps some what for one boot then back to where it was.
tried going back a month to may 1st of CM7 release. no go.
my wifes infuse is just like mine and works fine. difference is i was on ICS im gonna flash that and see how ICS works.
ive been working on this for around 14 hours, this is insane.
everything i do is no good.
i honestly think supercharger messed it up, but i dont know how. either that or my CPU is some how fried, but it works fine from time to time, and when i set it to 1200 mhz minimum speed
its as if my governor's are jacked up, but it is slow in boot up and recovery as well. which is what really confuses me
just installed ics AOKP Brocolli, and its as smooth as ics has been, i dont like the random crashes and problems i get from ICS so i want to go to CM7
plus this AOKP Broccoli theme is god awful to me.
i think im just to old to look at circuit board designs all day.
After a search, I know other people have had this issue with the MT4GS. I'm currently running Virtuous Inquisition 4.02. I'm pretty sure i've flashed any updates. Also, I don't remember having this issue on any other ROM that I have ran in the past (virtuous unity, CM 7). The issue is the soft keyboard not responding randomly to certain keys. The weirder thing is if i use a different finger, it usually responds, but if i keep using the same finger, it won't. Is this my digitizer going bad, or just a soft keyboard thing? I haven't experienced the issue in any other part of android, just when using the soft keyboard. is there a touchscreen driver to flash or anything i can do to fix this? thank you!
At least someone else has my same problem
anitgandhi said:
After a search, I know other people have had this issue with the MT4GS. I'm currently running Virtuous Inquisition 4.02. I'm pretty sure i've flashed any updates. Also, I don't remember having this issue on any other ROM that I have ran in the past (virtuous unity, CM 7). The issue is the soft keyboard not responding randomly to certain keys. The weirder thing is if i use a different finger, it usually responds, but if i keep using the same finger, it won't. Is this my digitizer going bad, or just a soft keyboard thing? I haven't experienced the issue in any other part of android, just when using the soft keyboard. is there a touchscreen driver to flash or anything i can do to fix this? thank you!
Click to expand...
Click to collapse
It isn't anything related to the digitizer aparently. I say this because it never gave me a problem using stock rom. This usually happens when the phone gets too hot (you can feel this on the touchscreen). It starts lagging from what i could see, i mean my touches are not recognized properly.
If anyone has a screen calibration .zip laying around i would highly appreciate you to share it
ahh ok thanks for the info. after flashing cm 9.1.0 i can definitely tell the phone isn't getting as hot (according to spare parts, on inquisition the battery would go upwards of 35 celsius regularly, with cm it hasn't gone above 25), and the issue isn't happening anymore. thanks for the help!
rafaelrfq said:
It isn't anything related to the digitizer aparently. I say this because it never gave me a problem using stock rom. This usually happens when the phone gets too hot (you can feel this on the touchscreen). It starts lagging from what i could see, i mean my touches are not recognized properly.
If anyone has a screen calibration .zip laying around i would highly appreciate you to share it
Click to expand...
Click to collapse
You won't believe it but I do have something. This will help to increase sensitivity but for the life of me I can't remember where I got it.
anitgandhi said:
ahh ok thanks for the info. after flashing cm 9.1.0 i can definitely tell the phone isn't getting as hot (according to spare parts, on inquisition the battery would go upwards of 35 celsius regularly, with cm it hasn't gone above 25), and the issue isn't happening anymore. thanks for the help!
Click to expand...
Click to collapse
That's something I just can't understand...when people have troubles with Virtual Inquisition, that is. My wife runs it ALWAYS and I will jump back to it at least once a month for a while myself. It's always been one of the most stable, coolest running and longest battery life ROMs in my nandroids of my favorites. ANYway....give that flashable a try & see if it helps. The best I remember, you can reflash it until you achieve the sensitivity you're looking for. Good Luck!
WeekendsR2Short said:
That's something I just can't understand...when people have troubles with Virtual Inquisition, that is. My wife runs it ALWAYS and I will jump back to it at least once a month for a while myself. It's always been one of the most stable, coolest running and longest battery life ROMs in my nandroids of my favorites. ANYway....give that flashable a try & see if it helps. The best I remember, you can reflash it until you achieve the sensitivity you're looking for. Good Luck!
Click to expand...
Click to collapse
inquisition definitely was very stable and had great battery life, there is little doubt about that. i'm guessing i just didn't flash it correctly, and that caused some really high temps. other than that, i had no issues with it...for example, though, when i was running inquisition, if i left the phone in my pocket and forgot about it until say someone texted me/called me/i got a notification, and i checked the temps, it was at 30-35 celsius, and felt burning. again, i'm guessing i didn't flash it right.
also, thanks for the touchscreen fixer zip, if i have the issue again, i will flash it. fingers crossed i don't need it.
side questions about kernel flashing: 1) do i wipe cache and dalvik cache then flash the kernel zip? 2) is there a way to go back to the original kernel without having to flash the rom all over again?
thanks!
anitgandhi said:
inquisition definitely was very stable and had great battery life, there is little doubt about that. i'm guessing i just didn't flash it correctly, and that caused some really high temps. other than that, i had no issues with it...for example, though, when i was running inquisition, if i left the phone in my pocket and forgot about it until say someone texted me/called me/i got a notification, and i checked the temps, it was at 30-35 celsius, and felt burning. again, i'm guessing i didn't flash it right.
also, thanks for the touchscreen fixer zip, if i have the issue again, i will flash it. fingers crossed i don't need it.
side questions about kernel flashing: 1) do i wipe cache and dalvik cache then flash the kernel zip? 2) is there a way to go back to the original kernel without having to flash the rom all over again?
thanks!
Click to expand...
Click to collapse
Wipe user data/cache .....cache....dalvik....battery stats. All of them 3 times. (CWM has some small issues getting everything on the first shot) Then you flash your Rom. Let it set a minute or two. Lastly....Flash your Boot.img. Be sure not to just let windows just show what's in the .zip file and copy it out but highlightit and open it with Winzip (or whatever you use). EXTRACT it to where you flash your files from. If you don't do it like that it will remain partially compressed and you'll forfet the parts of your kernel that are. Once flashed, let it rest for 5 minutes and you should be good to go.
If flashing another ROM ALWAYS follow those rules but if reflashing with another kernel you can forgo clearing user data so you will keep your apps & their placement in your ROM. Just clear everything else reflash your ROM again & then your kernel. It will look just like it did but with the new kernel. If by chance you then have an issue with force closes just go back to recovery & fix permissions & it should straighten that right out.
BTW....If you are unlocked & S-On you will not be able to flash it from recovery in any form or fashion. You will always need to extract the boot.img file and "ADB fastboot flast boot boot.img" from your command window.
WeekendsR2Short said:
Wipe user data/cache .....cache....dalvik....battery stats. All of them 3 times. (CWM has some small issues getting everything on the first shot) Then you flash your Rom. Let it set a minute or two. Lastly....Flash your Boot.img. Be sure not to just let windows just show what's in the .zip file and copy it out but highlightit and open it with Winzip (or whatever you use). EXTRACT it to where you flash your files from. If you don't do it like that it will remain partially compressed and you'll forfet the parts of your kernel that are. Once flashed, let it rest for 5 minutes and you should be good to go.
If flashing another ROM ALWAYS follow those rules but if reflashing with another kernel you can forgo clearing user data so you will keep your apps & their placement in your ROM. Just clear everything else reflash your ROM again & then your kernel. It will look just like it did but with the new kernel. If by chance you then have an issue with force closes just go back to recovery & fix permissions & it should straighten that right out.
BTW....If you are unlocked & S-On you will not be able to flash it from recovery in any form or fashion. You will always need to extract the boot.img file and "ADB fastboot flast boot boot.img" from your command window.
Click to expand...
Click to collapse
i'm s-off so i don't need to worry about the boot.img extraction and all that, but the rest was very helpful, thank you very much!
:good:
anitgandhi said:
it was at 30-35 celsius, and felt burning.
Click to expand...
Click to collapse
Whenever anyone mentions overheating issues with the device - the first questions should always be:
Are you on a stock battery?
If so, then that is your problem.
I've forgotten to manage setcpu and left it running at 1.7 more often then anything, yet very rarely run into overheating issues...unless I go back to a stock battery (even without overclocking)
Blue6IX said:
Whenever anyone mentions overheating issues with the device - the first questions should always be:
Are you on a stock battery?
If so, then that is your problem.
I've forgotten to manage setcpu and left it running at 1.7 more often then anything, yet very rarely run into overheating issues...unless I go back to a stock battery (even without overclocking)
Click to expand...
Click to collapse
i am on stock battery. good to know that it usually causes overheating...glad it's not happening with cm 9.1.0 though
WeekendsR2Short said:
You won't believe it but I do have something. This will help to increase sensitivity but for the life of me I can't remember where I got it.
Click to expand...
Click to collapse
the issue came back (although not as frequently) so i went to flash the zip that you attached... it says it's something relating to beats audio and then it errors out and the installation aborts. i looked at the files inside all have "beats" and "audio" in the filenames...
Hi all,
I've been struggling for the past few months with terrible performance issues on my Droid Charge. Things like redrawing the home screen and lag between switching programs I can live with, but when it takes several minutes to pull up the dialer to make a phone call or to answer a text message, my phone kind of stops being useful as a phone.
I started off on stock when I got the phone last year, then I rooted it a few months later. Everything was great until June. Gradually, my phone had become less responsive (taking forever to make calls, view and send texts). That plus something weird was eating >2GB data/month, and I could only identify it as "Android OS/others" via Onavo. I decided to go clean and try Tweaked 2.2w/PBJ. Things were pretty good for a couple of weeks until the major lag started coming back. I stepped back and uninstalled many apps, hoping to find one that was the main culprit, but my phone continues to act like it's trying to calculate a billion values of pi or something.
I tried following the steps from the rootzwiki "5 Steps to Keep Your Phone Snappy/Lagfree" (not allowed to link yet ), which helped somewhat, but it has not eliminated the problem. I often find myself resetting my phone to make phone calls. SwiftKey often doesn't load correctly and requires me to enter and exit applications frequently to get it to allow me to type. I had to wait nearly 2 minutes to get my home screen to display until I removed Holo Launcher and went back to TouchWiz.
Sorry for the essay--I'd be happy to provide additional details if needed. What can I do to a) figure out what's wrong with my phone and b) fix it?
Thanks in advance!
petrivka said:
Hi all,
I've been struggling for the past few months with terrible performance issues on my Droid Charge. Things like redrawing the home screen and lag between switching programs I can live with, but when it takes several minutes to pull up the dialer to make a phone call or to answer a text message, my phone kind of stops being useful as a phone.
I started off on stock when I got the phone last year, then I rooted it a few months later. Everything was great until June. Gradually, my phone had become less responsive (taking forever to make calls, view and send texts). That plus something weird was eating >2GB data/month, and I could only identify it as "Android OS/others" via Onavo. I decided to go clean and try Tweaked 2.2w/PBJ. Things were pretty good for a couple of weeks until the major lag started coming back. I stepped back and uninstalled many apps, hoping to find one that was the main culprit, but my phone continues to act like it's trying to calculate a billion values of pi or something.
I tried following the steps from the rootzwiki "5 Steps to Keep Your Phone Snappy/Lagfree" (not allowed to link yet ), which helped somewhat, but it has not eliminated the problem. I often find myself resetting my phone to make phone calls. SwiftKey often doesn't load correctly and requires me to enter and exit applications frequently to get it to allow me to type. I had to wait nearly 2 minutes to get my home screen to display until I removed Holo Launcher and went back to TouchWiz.
Sorry for the essay--I'd be happy to provide additional details if needed. What can I do to a) figure out what's wrong with my phone and b) fix it?
Thanks in advance!
Click to expand...
Click to collapse
could any number of issues - ranging from a rogue app to the ROM not sticking correctly. when you installed Tweaked, did you do it via CWM or ODIN?
also, did you enable the build.prop tweaks to help with redraws and making calls?
otherwise, I would suggest to try wiping cache and dalvik (sometimes that cleans it up a bit as well rebooting the phone once every few days) to help clear out some of the clutter.
do you have any "force close" messages (such as SyncMLSvc)?
Thanks for the quick reply.
I installed Tweaked through ODIN. I haven't heard about the build.prop tweaks though. Is there a resource you can point me to or a quick process to enabling them? I thought that a lot of these tweaks were "cooked" into the Tweaked ROM.
I've got App Cache Cleaner dejunking me every 4 hours, and I try and hit the davlik every day...I still have issues.
I do have the SyncMLSvc force close on boot. I figured it was a known bug in Tweaked and that it'd be addressed in a later revision. Is it a symptom of something more ominous?
petrivka said:
Thanks for the quick reply.
I installed Tweaked through ODIN. I haven't heard about the build.prop tweaks though. Is there a resource you can point me to or a quick process to enabling them? I thought that a lot of these tweaks were "cooked" into the Tweaked ROM.
I've got App Cache Cleaner dejunking me every 4 hours, and I try and hit the davlik every day...I still have issues.
I do have the SyncMLSvc force close on boot. I figured it was a known bug in Tweaked and that it'd be addressed in a later revision. Is it a symptom of something more ominous?
Click to expand...
Click to collapse
i don't use App cache cleaner, and thus do not have any issues. also, if you have TiBu, you can uninstall that syncmlsvc. see if that does the trick.
regarding the build.prop tweak, remove the # from ro.home_app_adj=1
here is a link to some others: http://www.s3forums.com/forum/galaxy-s3-hacking-mods/474-list-some-build-prop-tweaks.html
Do you have facebook installed? That P.O.S. kills my phone everytime. I install it from time to time just to see if they are coming close to fixing it. Needless to say it gets uninstalled in under 10 minutes.
I know everybody will jump all over me on this but why not try stock rooted FP5 for a couple of days. It will give you a baseline to compare other roms and app impact with. If your phone still acts up it would seem to be pointing to a hardware error IMHO.
What can it hurt?
Still Charged Up
Reilly1812 said:
Do you have facebook installed? That P.O.S. kills my phone everytime. I install it from time to time just to see if they are coming close to fixing it. Needless to say it gets uninstalled in under 10 minutes.
I know everybody will jump all over me on this but why not try stock rooted FP5 for a couple of days. It will give you a baseline to compare other roms and app impact with. If your phone still acts up it would seem to be pointing to a hardware error IMHO.
What can it hurt?
Still Charged Up
Click to expand...
Click to collapse
Apparently Facebook is making their employees switch from ios to android so they finally so something about the app.
Sent from my SCH-I510 using Tapatalk 2
JihadSquad said:
Apparently Facebook is making their employees switch from ios to android so they finally so something about the app.
Sent from my SCH-I510 using Tapatalk 2
Click to expand...
Click to collapse
LOL! They're all too busy dumping their worthless stock to care.
Still Charged Up
Reilly1812 said:
LOL! They're all too busy dumping their worthless stock to care.
Still Charged Up
Click to expand...
Click to collapse
Abandon ship!
Sent from my SCH-I510 using xda premium
I started usin Fast for Facebook. U cant do as much, but its not a battery hog which i think is super important
Sent from my SCH-I510 using xda app-developers app
cnoevl21 said:
I started usin Fast for Facebook. U cant do as much, but its not a battery hog which i think is super important
Sent from my SCH-I510 using xda app-developers app
Click to expand...
Click to collapse
It probably doesn't make you believe your running Froyo again either : crawling and littered with FC's
Still Charged Up
Most importantly out of everything is to always check out your md5's and make sure they match. Also try going back to stock with the pit file too for a full fresh install. But I think the problem is the md5 sums unless you download apps off the internet
Edit: also remember to mount system when flashing roms
Reilly1812 said:
Do you have facebook installed? That P.O.S. kills my phone everytime. I install it from time to time just to see if they are coming close to fixing it. Needless to say it gets uninstalled in under 10 minutes.
I know everybody will jump all over me on this but why not try stock rooted FP5 for a couple of days. It will give you a baseline to compare other roms and app impact with. If your phone still acts up it would seem to be pointing to a hardware error IMHO.
What can it hurt?
Still Charged Up
Click to expand...
Click to collapse
So, an update: I thought it was SwiftKey that was killing my phone, because I was doing better after I removed it. It was crappified even then, even after removing Facebook. I bit the bullet yesterday and went back to stock, updated all the way to FP5. I kept Facebook off (I've mostly moved over to G+ anyways). Everything is great. I put SwiftKey back on, and everything is still great.
I hate to say it, but even though the loss of customization in Tweaked is disappointing, I'm more satisfied with the phone in general with the stock ROM. My battery even lasts more than 3 hours too.
If it ain't broke...
petrivka said:
So, an update: I thought it was SwiftKey that was killing my phone, because I was doing better after I removed it. It was crappified even then, even after removing Facebook. I bit the bullet yesterday and went back to stock, updated all the way to FP5. I kept Facebook off (I've mostly moved over to G+ anyways). Everything is great. I put SwiftKey back on, and everything is still great.
I hate to say it, but even though the loss of customization in Tweaked is disappointing, I'm more satisfied with the phone in general with the stock ROM. My battery even lasts more than 3 hours too.
If it ain't broke...
Click to expand...
Click to collapse
my phone usually has that affect after flashing a new ROM. basically it's the wiping of data and cache/dalvik that helps cleans out the problems.
jco23 said:
my phone usually has that affect after flashing a new ROM. basically it's the wiping of data and cache/dalvik that helps cleans out the problems.
Click to expand...
Click to collapse
Maybe...but I've been wiping the cache/davlik fairly often. I had uninstalled most my apps...maybe some weird bug was still manifesting itself. I don't think my phone has been this responsive even after first going to Tweaked. :-/
petrivka said:
Maybe...but I've been wiping the cache/davlik fairly often. I had uninstalled most my apps...maybe some weird bug was still manifesting itself. I don't think my phone has been this responsive even after first going to Tweaked. :-/
Click to expand...
Click to collapse
Well as long as your happy that's all that really matters. To be fair - there is nothing in Tweaked that should degrade performance at all compared to what is normally seen in stock. The one difference I could see is that Tweaked is deodexed - and many swear the odexed approach is faster/snappier/whatever-adjective-you-want-to-say-that-means-better than the deodexed one. Hopefully things stay functioning well.
dwitherell said:
Well as long as your happy that's all that really matters. To be fair - there is nothing in Tweaked that should degrade performance at all compared to what is normally seen in stock. The one difference I could see is that Tweaked is deodexed - and many swear the odexed approach is faster/snappier/whatever-adjective-you-want-to-say-that-means-better than the deodexed one. Hopefully things stay functioning well.
Click to expand...
Click to collapse
I hear ya. I figure I'll give stock a go for a while, at least until Tweaked comes out of beta. I'm still counting down the days until I can upgrade to something with ICS. Or maybe even a Lumia 920...
petrivka said:
...at least until Tweaked comes out of beta...
Click to expand...
Click to collapse
It's out of beta - check it out here if interested
I tried forever to get PBJ to play nice. RFS & ext4. Gemini App Manager autostart tweaks. MinFree tweaks. All the TweakTool init.d tweaks. The SQL index tweaks. overclocking. Autokiller, other memory apps, JuiceDefender, other build.prop tweaks, etc. I tried it all...
I'm not sure if it was my hardware version or what, but I just could not get it to work well. It always seemed like it ran out of memory and couldn't automatically manage the apps in an overloaded situation. If i manually ran some of the SQL scripts, and killed running apps, it would be ok, but not for long. I had problems losing text messages because I think the text message handler got killed or didn't run in time. I've tried GoSMS and the stock SMS. I ended up relying on Ghostly SMS to help catch the texts I lost.
Once I went back to stock FP1, most of my problems went away. It's been much more stable. So, since then, it's been stock kernel (obviously on RFS). I've been on FP5 with various versions of Tweaked 3 beta/RC and now I'm no the final. All good.
So, as much promise PBJ has or had (who knows what the FP1/FP5 hybrid will turn out like), stock kernel with Tweak 3 is the way to go for me!
CalPolyRock said:
I tried forever to get PBJ to play nice. RFS & ext4. Gemini App Manager autostart tweaks. MinFree tweaks. All the TweakTool init.d tweaks. The SQL index tweaks. overclocking. Autokiller, other memory apps, JuiceDefender, other build.prop tweaks, etc. I tried it all...
I'm not sure if it was my hardware version or what, but I just could not get it to work well. It always seemed like it ran out of memory and couldn't automatically manage the apps in an overloaded situation. If i manually ran some of the SQL scripts, and killed running apps, it would be ok, but not for long. I had problems losing text messages because I think the text message handler got killed or didn't run in time. I've tried GoSMS and the stock SMS. I ended up relying on Ghostly SMS to help catch the texts I lost.
Once I went back to stock FP1, most of my problems went away. It's been much more stable. So, since then, it's been stock kernel (obviously on RFS). I've been on FP5 with various versions of Tweaked 3 beta/RC and now I'm no the final. All good.
So, as much promise PBJ has or had (who knows what the FP1/FP5 hybrid will turn out like), stock kernel with Tweak 3 is the way to go for me!
Click to expand...
Click to collapse
You're 100% correct!!
Please correct me if I'm wrong because I really want to know. The way I see it is, the real improvements over FP1 came from what Samsung did with FP5. Then what Dwitherell did was remove the useless bloat and ugliness then add the useful features and beautify it without changing anything that would hurt the performance.
The first time I upgraded to FP5 stock I noticed the speed increase right off. I checked it out a little and was amazed. But of course it had all of Verizon's bloat garbage in it and none of the awesome tweaks from Dwith. And it had no user installed apps in it at all. It has always seemed like the more apps I install the slower the phone gets.
So am I right?