Question about Epic Experience - Epic 4G Android Development

The add-on and patches, do you just put these on the sd card and flash from clockwork recovery like you do with a mod or kernel? Are all of them safe to install and is there any information about them?
Here they are
Add-Ons & Patches
Backgrounds (Non-Flashable)
Samsung Widgets
Stock MMS/SMS
Modified MMS/SMS (Stock Icon)
Modified MMS/SMS (International Galaxy S Icon)
TouchWiz Lock Screen
Live Wallpapers
Vanilla Lock Screen
Launcher
ThinkOffice
Thanks.

mynewepic10 said:
The add-on and patches, do you just put these on the sd card and flash from clockwork recovery like you do with a mod or kernel? Are all of them safe to install and is there any information about them?
Here they are
Add-Ons & Patches
Backgrounds (Non-Flashable)
Samsung Widgets
Stock MMS/SMS
Modified MMS/SMS (Stock Icon)
Modified MMS/SMS (International Galaxy S Icon)
TouchWiz Lock Screen
Live Wallpapers
Vanilla Lock Screen
Launcher
ThinkOffice
Thanks.
Click to expand...
Click to collapse
yes, sd card and flash from cwm recovery

All of them are flashable except the backgroudns

Thanks for the info.
Does anyone have any info on what they do?

Basically they are what they say.
-Backgrounds gives you background pictures.
-Samsung widgets flashes the stock Samsung Widgets
-Stock MMS/SMS gives you the stock Epic icons for MMS/SMS (because Schizo has modified the ones in his rom)
-Modified MMS/SMS is similar to stock icons but slight different
-The second modified MMS/SMS gives you the same icons is the international i9000 Galaxy S
-TouchWiz lock screen gives the default Epic lock screen for those have a different one and want to go back
-Live Wallpapers gives you the live wallpapers that came stock on the phone
-Vanilla lock screen gives you the original AOSP lock screen
-Launcher reinstalls the vanilla Android launcher to the phone
-ThinkOffice adds ThinkOffice back to the phone

Yup. They are what they say. Always remember to back up before flashing w/ CWM. Occasionally you will run into instability issues when flashing mods/addons. After I flashed vanilla lockscreen and then back to touchwiz lock, I had some instability issues with the phone. Had to restore to my backup that I just made.

plapczyn said:
Yup. They are what they say. Always remember to back up before flashing w/ CWM. Occasionally you will run into instability issues when flashing mods/addons. After I flashed vanilla lockscreen and then back to touchwiz lock, I had some instability issues with the phone. Had to restore to my backup that I just made.
Click to expand...
Click to collapse
Yes I have learn to make backups before any major changes and have had to use them. Right now my phone is just turning itself off when I am using phoeix kernel .49 and the latest EE. I know it must be EE, because I restore and still run Phoenix .49 with 2.1 w/o any issues.

mynewepic10 said:
Yes I have learn to make backups before any major changes and have had to use them. Right now my phone is just turning itself off when I am using phoeix kernel .49 and the latest EE. I know it must be EE, because I restore and still run Phoenix .49 with 2.1 w/o any issues.
Click to expand...
Click to collapse
I'd recommend wiping everything three times at least (factory, cache, and davlik) before flashing something new. I know it seems excessive, but when I had the EVO there were reported issues with Clockwork not wiping properly and causing issues for some. I've recommened the three wipes to several on the Epic forums who were having issues and theyve noted that this helped fix their problems. Just saying.

mynewepic10 said:
Yes I have learn to make backups before any major changes and have had to use them. Right now my phone is just turning itself off when I am using phoeix kernel .49 and the latest EE. I know it must be EE, because I restore and still run Phoenix .49 with 2.1 w/o any issues.
Click to expand...
Click to collapse
Your issues may be linked to the interactive governor that .49 uses. I was having issues but changed the governor to conservative with setcpu and have had zero problems since.

wjsmaggle said:
Your issues may be linked to the interactive governor that .49 uses. I was having issues but changed the governor to conservative with setcpu and have had zero problems since.
Click to expand...
Click to collapse
I see a free setcpu and a setcpu for 1.99. Which one should be used?

mynewepic10 said:
I see a free setcpu and a setcpu for 1.99. Which one should be used?
Click to expand...
Click to collapse
The 1.99 one is the one, but Setcpu is free for xda members. Do a forum search for the post with the apk attached
Sent from my SPH-D700 using XDA App

Ok still having the same issue. I went back to stock phone and reflashed EE and Phoenix kernel. It was going well until the phone decided to turn itself off and would not come back on without a battery pull.
Can anyone give me an idea of what may be wrong or what I could try?

mynewepic10 said:
Ok still having the same issue. I went back to stock phone and reflashed EE and Phoenix kernel. It was going well until the phone decided to turn itself off and would not come back on without a battery pull.
Can anyone give me an idea of what may be wrong or what I could try?
Click to expand...
Click to collapse
I had a similar issue and did the 3x wipe of everything. I also stopped using profiles in setcpu and have it set to interactive. So far I am getting killer battery life and no freezes yet. Prior to the wipe I tried 3 or 4 different versions of kernels and was having the same freeze about once a day. I'm using Phoenix 1.49 and EE 1.2.4.

mictek said:
I had a similar issue and did the 3x wipe of everything. I also stopped using profiles in setcpu and have it set to interactive. So far I am getting killer battery life and no freezes yet. Prior to the wipe I tried 3 or 4 different versions of kernels and was having the same freeze about once a day. I'm using Phoenix 1.49 and EE 1.2.4.
Click to expand...
Click to collapse
I know the wipe is in clockwork, but what exactly did you wipe or I should say what did you choose to wipe in clockwork?
How long have you been running it without freezing?

Well so far I did 3 wipes of everything and reinstalled and no freezes yet. Does anyone think that the wi fi tether program could be causing my phone to freeze up and turn off? I have not installed it yet and all is well so far.

chino0131 said:
I'd recommend wiping everything three times at least (factory, cache, and davlik) before flashing something new. I know it seems excessive, but when I had the EVO there were reported issues with Clockwork not wiping properly and causing issues for some. I've recommened the three wipes to several on the Epic forums who were having issues and theyve noted that this helped fix their problems. Just saying.
Click to expand...
Click to collapse
The Factory, cache and davlik. Prior to doing that I only did a single wipe. This time I followed the instructions according to the emotionless beast theme. I've only had it running for 20 hours, but no freeze up yet and the battery life is much better. My phone is at 74% with very light use during 9 hours. I had about 15 min of phone calls and a short time playing angry birds the rest was standby. I am running Juice Defender, but before I could never get this much life out of my battery. Normally I would be around 50-60% with just standby in 9 hours.

Oh yeah. Im running setcpu at interactive, no profiles and disable the drm process after boot.

mynewepic10 said:
Well so far I did 3 wipes of everything and reinstalled and no freezes yet. Does anyone think that the wi fi tether program could be causing my phone to freeze up and turn off? I have not installed it yet and all is well so far.
Click to expand...
Click to collapse
Thought I had it and then it froze up again. I am going back to stock and starting over.
mictek said:
The Factory, cache and davlik. Prior to doing that I only did a single wipe. This time I followed the instructions according to the emotionless beast theme. I've only had it running for 20 hours, but no freeze up yet and the battery life is much better. My phone is at 74% with very light use during 9 hours. I had about 15 min of phone calls and a short time playing angry birds the rest was standby. I am running Juice Defender, but before I could never get this much life out of my battery. Normally I would be around 50-60% with just standby in 9 hours.
Click to expand...
Click to collapse
I will give this a try. Returning to stock and starting over again.

Related

CM7 vs stock android - benefits?

I've had my NS for over 2 months now - love it. Since I bought it, I've been running completely stock android 2.3.3
Like most on this forum, I like to tweak settings and make improvements.
I just want to know if that if I were to root and load CM7 rom on the NS would it improve the speed/battery? (they are the most important factors to me)
Yes it would improve your battery life. Especially when you flash a custom kernel. With this combination, I currently get 24 hours+ with maybe ~30% remaining.
http://www.cyanogenmod.com/about/features are some of the highlights of the features.
Some benefits on top of my head:
Flashing custom kernel (I suggest you do, its easy)
- Voodoo Sound (Better sound quality, you'd be amazed)
- Voodoo Color (Don't like 2.3.3 colors? Change it back to <2.3.3)
- Overclock (If you're into that) or Underclock
- CFS or BFS
Kernel.. i'd go with Netarchy's 1.2.8 CFS
CM7 Benefits
- Widget Folders (When you add a widget, no more 5 widgets showing Beautiful Widgets.. instead its in a folder; better organization)
- Power Widgets (Notification Pulldown)
- If you use your NS as a music player, it adds a lot of features such as lock screen controls. Using volume rocker to adjust volume while phone screen not on.
- Custom Boot Screens
- Sync with Facebook
Rest are here: http://wiki.cyanogenmod.com/index.php?title=CyanogenMod_Settings
Thanks for your tips. Before I had my NS I had modded my Hero beyond belief!
Would it be easy to send the phone back to a stock ROM and stock kernel? Lets say I had to send the phone back to Samsung to get warranty repaired.
Following on to that question, which is the best way to root?
How's the stability of CM7 on the NS. I just upgraded from my G1 to the NS yesterday, and I was thinking of just running stock until CM7 goes final.
JTopaz said:
Thanks for your tips. Before I had my NS I had modded my Hero beyond belief!
Would it be easy to send the phone back to a stock ROM and stock kernel? Lets say I had to send the phone back to Samsung to get warranty repaired.
Following on to that question, which is the best way to root?
Click to expand...
Click to collapse
Yes all you have to do is download a nandroid backup of 2.3.3 or whatever that is stock unrooted. And thats it.
Root: http://forum.xda-developers.com/showthread.php?t=895545
@Apre: It's stable. The latest nightly (#19) is more stable than RC2 itself. And dang G1 lol, I upgraded from a G1 last year in Juneish. Looking back on that phone now, the screens so small.
I have CM7 RC2 and i find that my battery drains faster. How do I flash Netarchy kernel?
Put it in SD and update it? or do I do it the ADB way by putting the kernel in the tools folder and with command prompt?
I ran stock for quite awhile after buying this phone because I didn't see any need for custom ROMs with vanilla Android. But I finally decided to give it a shot, and I'd never go back. Vanilla is great, but CM7 and all the other Custom Roms for the Nexus S (Axura, Modaco, etc) all bring more great features and customizations. If nothing else, however, I'd at least root and flash a custom kernel with stock - so you can have some overclock goodness
Edit: In specific reference to your post's questions, I run Axura, and I get both better battery life AND what seems to be a snappier phone (Axura has Netarchy 1.2.5 kernel baked right in). On CM7 I didn't notice much of a speed boost, and I think my battery life might have actually been a little worse, but CM7 packs in a lot of extra features. So it all comes down to preference.
apreichner said:
How's the stability of CM7 on the NS. I just upgraded from my G1 to the NS yesterday, and I was thinking of just running stock until CM7 goes final.
Click to expand...
Click to collapse
CM7 will never go final, until its time for CM8. its always being inproved.
cyberdentist said:
I have CM7 RC2 and i find that my battery drains faster. How do I flash Netarchy kernel?
Put it in SD and update it? or do I do it the ADB way by putting the kernel in the tools folder and with command prompt?
Click to expand...
Click to collapse
yes. put it in SD, boot into CWR
flash .zip
and you're done.. its the same as flashing a ROM
and as far as battery life.. make sure you disabled latitude (automatic and that other feature) in CM7.. not sure if its still working even though if latitude is disabled, id disable it anyway
apreichner said:
How's the stability of CM7 on the NS. I just upgraded from my G1 to the NS yesterday, and I was thinking of just running stock until CM7 goes final.
Click to expand...
Click to collapse
I was so happy with my stock NS that I'd not bothered with CM (my ROM of choice on Nexus 1) until just two days ago. In the first 24 hours I had two issues that I've not had, or at least not seen in a very long time.
First issue - I was at 84% battery after about 4 hours. Put the phone to the side of my desk and 3 hours later it was 100% drained to 0 battery juice. Status graph showed nothing unusual, not long wakelocks, no time without cell signal, screen on only 1.5 hours.
Second issue - 24 hours after install, while listening to a podcast with my long time app for those that's not given crash issues, the playback goes into a constant stutter loop for about 30 seconds, then the phone rebooted.
EDIT: a third issue, happening right as I type this. I'm happily tethered away on my laptop via the NS with CM7, but I just went to check something on the screen and the phone is locked up...won't respond to power button. Screen is black, menu buttons are lit. Still tethering me, though.
Seems there are still some slight issues. I did full wipe/format before installing and am on the stock CM7 kernel still.
cyberdentist said:
I have CM7 RC2 and i find that my battery drains faster. How do I flash Netarchy kernel?
Put it in SD and update it? or do I do it the ADB way by putting the kernel in the tools folder and with command prompt?
Click to expand...
Click to collapse
It's an update.zip file you flash from CW recovery. I agree CM7 appears to be harder on the battery.
simms22 said:
CM7 will never go final, until its time for CM8. its always being inproved.
Click to expand...
Click to collapse
I suppose that you're technically correct that CM mods never go final because they're always improved, but all prior iterations of CM at least got out of BETA/ReleaseCandidate status at some point.
I fully expect that CM7 will eventually see a version that doesn't have a beta, nightly or RC tacked on to the end of it. Then we'll see all the .x releases with their betas/rc, etc.
I was going to hold off on CM7 until it was past RC stage because I feared it would have some issues, despite all the glowing reports, and it does, but not enough for me to go back to stock. Probably time to flash netarchy on top of this.
zephiK said:
yes. put it in SD, boot into CWR
flash .zip
and you're done.. its the same as flashing a ROM
and as far as battery life.. make sure you disabled latitude (automatic and that other feature) in CM7.. not sure if its still working even though if latitude is disabled, id disable it anyway
Click to expand...
Click to collapse
I haven't even activated latitude . I don't have background data enabled either. Not sure what is killing the battery life in CM7 ..
Also, if you're interested. Check out frank707's "NS Collab" ROM. It's basically CM7 without ADW launcher, which is good if you like using CM7 but miss the stock launcher or just frankly don't like ADW.
cyberdentist said:
I haven't even activated latitude . I don't have background data enabled either. Not sure what is killing the battery life in CM7 ..
Click to expand...
Click to collapse
hence why i said.. not sure if its still working even though if latitude is disabled, id disable it anyway
I have tried CM7 and felt that its bugs and constant state of upgrading and updating to fix things caused me too many issues for daily use.
I do think that CM7 does perform a bit better than the other ROMS due to it being AOSP based but i feel thats why there are also some of these bugs.
I have been using AXURA by Master and its been flawless for me, the one issue I had with a reboot was due to testing a new overclock, but now I keep it at 1200 max ondemand and it hasn't gave me any issues, The lack of full easy theme support like CM7 is a con but the performance is up there with CM7 and the stability is sooo much better for me, I feel this is because its the Stock 2.3.3 ROM that has been decomplied and tweaked and then compiled again.
Its worth looking at some of the other options as well.

random reboots with weapon

alright when I use weapon 3 on stock kernel I get random reboots when I am not using it or I would have to pull out the battery in order to use it. I have done format system, data, cache, dalvik and then used g2x scrubber and I install it through my extrenal SD. tsugi on stock so far had no problems. I want to use weapon though because my battery life with tauting is horrible. with light use I can only use about 7 hours with set CPU lowering the clock and having it set to the lowest clock on screen off.
minaru said:
alright when I use weapon 3 on stock kernel I get random reboots when I am not using it or I would have to pull out the battery in order to use it. I have done format system, data, cache, dalvik and then used g2x scrubber and I install it through my extrenal SD. tsugi on stock so far had no problems. I want to use weapon though.
Click to expand...
Click to collapse
This is a known issue for G2x, it varies from phone to phone, and for rom to rom. Devs are working hard to reduce this, but trust me, they re not as bad as stock...
Sent from my G2X XDA app cuz I'm stalking your mom....
yes I do realize that custom roms are better than stock but my brother has weapon and his battery life is phenomenal! he can use his phone for 2 days and he isn't using any CPU optimizer or juice defender while I am using all those on tsugi rom and still only get about 7 hours of light use. iono maybe I am doing something wrong with tsugi rom?
minaru said:
yes I do realize that custom roms are better than stock but my brother has weapon and his battery life is phenomenal! he can use his phone for 2 days and he isn't using any CPU optimizer or juice defender while I am using all those on tsugi rom and still only get about 7 hours of light use. iono maybe I am doing something wrong with tsugi rom?
Click to expand...
Click to collapse
Setup your phone just like your brother's and swap fully charged batteries then give your phone to him to use and you use his (this is to try to have your phone tested under the same use as your brother uses his phone) to find out if the problem is the phone or the battery. If your brother's phone with your battery in it doesn't last as long or nearly as long as it did with his own battery in it, then it is definitely your battery. If, while your brother uses your phone with his battery in it, your phone doesn't last as long as his phone does with his battery in it, then it's your phone. Your phone should still be under warranty so, if you need to get service you will know what needs replacement.
Try phoenixblood rom with faux kernel, no reboots and great battery life!
Sent from my LG-P999 using xda premium
I'll +1 that for PhoenixBlood
plus: if you are having any stability issues, remove everything that might cause that, including CPU "optimizer" and Jdefender. They could conflict with the kernel. OTB PhoenixBlood is really great for speed and battery.
Also, if you've had previous problems, such as overheating, you may have damaged your battery. I'd first try running your brother's battery (with his permission), to see if that changes things. One rule to use is that you shouldn't change more than one variable at a time if you care to know what it is that fixed it. Changing ROMs, phones, batteries, SIMS and SD cards all at once will maybe fix the problem but it won't tell you what you did to fix it.
Maybe you're just undervolting too low? My phone can hardly handle it so I usually just don't mess with it.
Keep stock kernel.
thank you for all your replies. I have tried pheonix blood and liked it but even on stock or faux kernel I still get reboots. I did not download those extra applications either. so I am back on tsugi stock kernel and it has no reboots yet, but I found that if I enable the toggle 2g application that came with it and set the radio frequency to wcdma only, it increases the battery life by a lot. I can now go through the whole day with about 50 percent with light use. I do like pheonix or cm7 better though because I feel that it is going to keep updating for the better. also it seems customizable. I was wondering if there is a way to record when the phone experienced a reboot or sod to a log so I can find out why?

phone keeps restaring every 30 mins

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.

[Q] Battery Level Stuck at 100%

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 ?

What is killing my phone's performance?

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?

Categories

Resources