Okay it all started when I updated my original Samsung Galaxy S i9000 running Eclair to Froyo I9000XXJP3 using Samsung Kies. Since then its been really slow and very laggy. I ran around Google for a bit and found some clues about doing a factory reset just after updating to Froyo. To do this I would like to download all apps that can be installed onto and SD card to my SD card so I dont have to re-install all the 111 apps I have after factory reset. It would be pretty cool if someone told me how to backup my contacts, ALL of my settings, my email, basically EVERYTHING on my phone that I would have added on myself after I started using it. Of course I am guessing that the default Samsung Apps that came with the phone and are still available on Froyo will still be available after the factory reset.
My next problem. While someone on these forums tell me how to backup ALL of my data (apps, contacts, media, etc........) onto an SD card before factory resetting I decided I will try to root my phone and apply OneClickLagFix V2.2+. So I used an Windows app called SuperOneClick to root my phone, successfully. After this I installed OneClickLagFix, gave it permission. Then I installed the OneClickLagFix V2.2+, also successfully. After this I tested my phone with Quadrant Benchmark and I got a score of 1956 (which is amazing because I had got 915 before I had applied the LagFix). This is all amazing, but I realised that my battery is draining really fast, because usually if I don't use my phone in the night while sleeping for approx.6-8 hours it drains little to nothing of the battery, but after applying the lag fix I left it on at night (with full battery) while sleeping and when I woke up it had only half of its battery left, so I am guessing OneClickLagFix V2.2+ drains my battery while trying to speed up my phone which is really not helpful (which is why I would like to try to factory reset as a means of speeding up my phone without draining battery).
The third thing, still related to the topic of battery power and speeding up Froyo. I realised that even after applying the OneClickLagFix V2.2+ and gaining a Quadrant mark of 1956, my Galaxy S still did not have the iPhone style smoothness I would expect from the powerful 1Ghz processor in the phone, so please dose anyone have any ways of basically speeding up the phone (with iPhone style smoothness) and not draining battery.
My next thing is not a problem, it's just for fun. I heard that the Galaxy S's CPU can be overclocked to 1.2GHz and 1.6GHz. Could someone post a guide that explained in detail what I have to do to overclock my Galaxy S because I am quite new to hacking my phone and things like that.
So my questions so far:
How to speed up my Froyo phone (make it very fast and smooth like the iOS) without draining too much battery?
How to backup EVERYTHING (like all my downloaded apps, contacts, SMS, etc..) before factory resetting?
How to overclock CPU to 1.2GHz and 1.6GHz?
Hi, I'm still running 2.1 Eclair but maybe i can help a bit. I very much doubt that its OneClickLagFix draining your battery, ive been running it for over 6 months without any problems and so have thousands of others but you could try looking through the OneClickLagFix thread just in case
http://forum.xda-developers.com/showthread.php?t=784691&highlight=oneclicklagfix
Next thing, are you running a task manager or process killer? they can drain the battery while they kill a process and it starts again and gets killed again and starts agai...... you get the idea
I use AutoKiller Memory manager from the market. This works with the built in android process killer and just tweaks it to work better. I find the moderate preset setting to be good but others have suggested going further so you may need to experiment on that.
Also are you sure you didnt install another 'rogue' app? some apps are known to stop the phone from going into sleep mode and that would also cause battery loss at night.
As for backing your things up, AppBrain from the market will take care of your apps if you make an account with them and use your Google log in. It will remember which were installed and put them back when you are ready, I dont think it will save 'in game' data like saves and such though. I cant help with contacts, messages and the rest, sorry.
Lastly, to overclock it you will need to be rooted (as you said you are) and use an app called SetCPU from the market. But be warned, firstly it is guaranteed to cost more battery power overclocking it and the phone will get hotter in use. It will however speed things up a little IF it doesnt blow up LOL. The opposite would be to underclock and save power but then it would run slower and you don't seem to be aiming for that
Good Luck
Thanks!
Thanks for the help, I used App Brain to sync apps and also backed up my apps using Titanium Backup to my SD card, which also backed up the app data. Also, I backed up my contacts by pressing the menu button on the contacts screen and exporting. To backup my messages I used SMSBackup. It all worked well.
I will look into the battery matter, yes, I am using Advanced Task Killer but after reading your response I did not re install it after the factory reset. I will definitely try AutoKiller Memory manager and look into the battery matter further if it doesnt change things.
I tried SetCPU but it only lets me move the sliders upto 1GHz, not higher. Any help is appreciated. And also I just want to try the 1.2GHz, because I am guessing 1.6GHz will REALLY push things past the limit and might mess things up. If things mess up with 1.2GHz I will put it back to 1GHz, and if you had not told me I wouldnt have known about the heating problem, thanks .
How does overclocking work anyway?
Similar issues like whoosh with my phone too.
Pre froyo (no root no lagfix) - app drawer page transition smoothness superb. No lag or stutter in transitions.
Post froyo (pre root and lagfix) - stuttery app drawer page transitions.
Root and voodoo lagfix have not fixed that problem.
- Quadrant ~1500
- formatted internal sd card.
- factory reset post froyo install.
- formatted ext sd card.
- ext sd card sandisk class 4 16gb.
Any solutions to above issues would be greatly appreciated as i would assume would also assist op with their issues.
Cheers
Sent from my GT-I9000 using XDA App
Hey, erm, I thought the Galaxy S has 512MB of RAM but the RAM manager is 300 and something MB of RAM. Maybe thats why it is so slow, because i would expect iPhone-style smoothness from a 1GHz Processor and 512MB of RAM, but looks like it has a cap on. Is there anyway we can fully uncap the RAM usage, so all the 512MB is used? that would be helpful
problems fixed
I used the power of my rooted phone to titanium backup (pro recommended) and then backed up all apps with user data. I factory reset my phone which speeded everything up A BIT. then i discovered Darky's ROM 5.5 (maybe higher by the time some read this post) and installed that following the CLEAN guide written very well (video too) on his forum (CLEAN recommended to upgrade from normal galaxy s firmware to darky's ROM then EASY guide for upgrading from past versions of Darky's ROM).
After following the guide, everything booted up perfectly (amazing gingerbread experience, it feels and looks a lot like it, just missing vibration from gingerbread keyboard and some gingerbread icons, also if darky reads this, maybe you should integrate the new Nexus wallpaper in, but its not that hard to install it yourself either so its fine).
I set the phone up, redownloaded Titanium Backup and it took about half an hour to restore all my apps (with all data). Also note that before I had installed Darky's ROM 5.5 it had taken me 1 and a half hours to restore apps using Titanium Backup so you can see how significantly fast Darky's ROM is. It is amazing!
Well done!
Related
i was doing my 5k run with my recently updated hero and about a mile into the run pandora radio started skipping and then stopped. when i looked at my phone it was rebooting. i have task manager and killed all the apps before i started and unchecked jogtracker and pandora so i could use them. it didnt last long. the phones screen froze and dimmed then crashed until it finally restarted. is there a reason for the crash. seems to me like a memory problem. i have a two gig card with one pt. five left on it. and the internal memory is at 91mb. it always worked before i rooted and installed cm6. the phone in general is way faster and more responsive since i put cm6 on it but for some reason the two apps running together arent working. thanks for any help
Try removing the task manger reboot into recovery and wipe Dev/ cache and try it then might work good luck
Root-Hack-Mod-Always™
I've tried running with and without various task managers and always wind up uninstalling and reminding myself that I should know better.
I seriously don't think Froyo and these mods need a task killer. If anything, they seem to cludge things up. My phone was running beautifully for two weeks and earlier today I thought I'd try out a different task killer. Mistake. I uninstalled it after 1/2 hour because it just made the phone feel funky.
Try running without for a couple weeks....
jwhistler said:
I've tried running with and without various task managers and always wind up uninstalling and reminding myself that I should know better.
I seriously don't think Froyo and these mods need a task killer. If anything, they seem to cludge things up. My phone was running beautifully for two weeks and earlier today I thought I'd try out a different task killer. Mistake. I uninstalled it after 1/2 hour because it just made the phone feel funky.
Try running without for a couple weeks....
Click to expand...
Click to collapse
+1, CM6 does not need a task killer/manager. The best method is to download AutoKiller (which lets you alter Android's internal memory manager, much more effective than task killers) and change the settings to Strict or Aggressive. Also, two of the biggest problems that create soft reboots that you describe is (a) the VM heap size being too small and (b) CPU speeds being too high. So, steps to take:
1) Uninstall task killer
2) Install AutoKiller and change settings to Aggressive
3) Change SetCPU/Overclock Widget settings to 691 max/595 min with screen on, 480 max/245 min screen off
4) Change VM Heap size (in Cyanogenmod Settings) to 24 MB and reboot
The only other possibility I can think of would be kernel instability. If you flash Decand3nce's #14 Stable kernel found here it is far more stable than the stock kernel and (IMHO) has much better performance than the stock kernel.
These steps should rectify any memory and/or CPU overconsumption problems you are having that could cause the reboots (as well as make your phone much faster, smoother, and more stable). If these steps don't fix it, it most likely is a problem with one of the apps themselves.
Good luck!
thanks for the help.
also on the restart i got this message Sorry the applicating spring updater (process com.sprint.ce.updater) has stopped unexpectedly. please try again. force close. this is probably the cause of all the problems thanks
the changes u pointed out seemed to have fixed the phone so far. thanks so much for the great instructions. u da man.
i noticed a couple times a day the phone reboots. should i back off of some of the settings.
kevinr12345 said:
i noticed a couple times a day the phone reboots. should i back off of some of the settings.
Click to expand...
Click to collapse
Yup, lower the max cpu.
Froyo Hero to the rescue
what is the VM Heap size for what does it change. mine is at 16 right now.
clutch_08 said:
what is the VM Heap size for what does it change. mine is at 16 right now.
Click to expand...
Click to collapse
Its the amount of memory each application can take up maximum. You tend to get smoother running stops with higher vms; I set mine to 24.
Froyo Hero to the rescue
heya fellas
question here is with all the lagfixes/kernals
is everybody happy with how fast/reliable the phone is ?
im mainly a tester and was happy since i wont keep a single setup for more than a few days, and since my latest setup,in my situation all it takes is a week and the lag is back ....
wether i was OC'd or not the lag is haunting my phone T_T
current setup is darkys v7 rom and SO 4_5_3 kernal with 1.4mhz set on boot
1 week of normal use with 80 apps installed and lag ranges from 1-8 secs wether it was moving between homescreens/app pages in menu/call log/msgs
last lagfix i was completly happy with was longback when i was on voodoo and OCLF on top of it. i remember the phone was seriously blazing fast like it had everything done before i asked for it, and that setup only lasted a month or so before froyo was out.
i sound like an old hag complaining but seriously who out there is very pleased with a certain setup? anything yall recommend?
I'm on Darky's 7.0 JPY (Have been on Darky's ROMs since 5.1) without a lagfix and the phone is snappy fast, as are all apps I use (about 4 pages of them). Haven't seen it lag in weeks.
Do you face a lag after you launch up multiple apps? Or generally from boot onwards itself?
from boot i know its the media scanner taking over 100% of the cpu
clearing ram clears most of the lag but i notice the crazy lag whenever i have any amount of available ram of 80mb and less
mainly ram jumps between 130mb and 60mb from what i see
got a few widgets to monitor ram/cpu/temp/battery/ and the control widget with 3g/wifi/bluetooth/data/gps/brightness/media scan/reboot and a black background
trying to maintain a small amount of widgets to keep free ram available, pretty much doing my best
I use Autokiller Memory Optimizer with an Aggressive preset, it helps keep multi-task going smooth (Usually have 130~ MB free with it running). Have you tried that application?
I'm on Darky's 7.0 JPY (Have been on Darky's ROMs since 5.1) without a lagfix and the phone is snappy fast, as are all apps I use (about 4 pages of them). Haven't seen it lag in weeks.
Likewise no lag at all .
jje
Most lag comes from bad app.
The only on i can't get lagfree is twlauncher. So i use golauncher instead. I don't se any lag.
I also use ext2 file system.
This with my kernel.
Im happy with this lagfix and i don't think it will be laggy over time.
**Using my own JPX kernel, z4mod, 345MB Ram and ext2 filesystem**
Whilst it never really bothered me in 2.2, in JPX/2.2.1, honestly, I'm not running any hacks. I seriously haven't seen any remotely long stalls anymore. Also, all OS's stall, it isn't only because of "bad apps"; it can also happen when swapping and such. We really don't know enough about the lag problem to say where most lag comes from.
Since JPX also introduces over the air updates (one major flaw with earlier firmwares), if the GPS turns out to perform like fitness-grade GPS (I still need to test that), I'll be extremely happy. But no longer entirely dissatisfied. Taking GPS out of the equation though, I am now happier than I've ever been. If Samsung frees up more RAM, I might even start overlook the GPS problems.
After I test GPS, I'll know for sure.
(PS, I don't use any lag optimisations, because I don't feel they solve the problem properly).
Did you read what this tread was.about?
I can also say with lagfix the phone is better then stock. The latest firmware did alot for the lag, but it still things to do.
**Using my own JPX kernel, z4mod, 345MB Ram and ext2 filesystem**
thanx for all the suggestions fellas
just reverted back to 2.2 (missing darkys already T_T)
will test it out n check how things go
first things first gps surely seems worse than darkys rom for some reason (could it be the modem file ?)
I've had a 16gb Samsung Galaxy S on Three in the UK since they launched last year, and it's the only Android phone I've used.
It's pretty laggy, but since I'd read a lot about Galaxy lag online, I assumed this was to be expected.
However, I had to help a colleague with a problem on their HTC Wildfire today (a lower spec phone, as far as I know), and was amazed how much more responsive than my Galaxy S.
It didn't seem to show any of the laggy, hanging-ey behaviour I experience. I have more apps installed than the Wildfire, but I'm quite careful not to install anything that's going to run at startup or cause problems (mostlly just games, no widgets, etc.)
As an example, if I turn the phone on clean, wait for everything to be loaded and ready (media scanning to finish, etc.) then poke the "Market" button, it takes 28 seconds for it to be loaded and responsive. Close that, poke the Facebook button, over 20 seconds until I'm shown the news feed. Sometimes when the phone rings on my desk, I literally won't be able to get it to respond enough to answer the call before the caller hangs up. If I try to switch from program to program, I end up getting quite a lot of frustrating 20-30s hangs and pauses. This is all on a decent wifi connection, so the problem isn't data related.
The question is - how laggy should a Galaxy S be? Would it work better if I added an SD card (with the 16gb phone memory, I didn't see the need)? Is it worth installing a lagfix under Froyo (I tried one back on 2.1, but didn't notice a huge amount of difference)?
Any help would be greatly appreciated!
I think its sometimes very busy rebuilding it's wifi connection. Or some other process.
Am not sure.
Sent from my GT-I9000 using XDA App
I didn't see any speed difference with SD card IN/OUT so i don't think you will have faster phone by inserting it (SD card).
Why don't you try a reset and see if that works? Also are you on eclair or froyo because that would make a world of difference if you upgraded
I just got my sgs from bell Canada last Tuesday. It has all stock with launcherpro and a few Widgets. So far (knock wood) its been a big step up over my HTC dream. I experience maybe 10 seconds of startup lag and then for the rest of the day its awesome. My firmware version is the newest one bell offers (jl2 Frito). What android version are you running?
Sent from my GT-I9000M using XDA App
monkeyhat said:
Any help would be greatly appreciated!
Click to expand...
Click to collapse
That's exactly my experience. The only way to solve it is with a good lagfix and/or flashing JPY firmware
This will get almost instant loading of apps and only minor lags when switching apps. It's still slow when scrolling icons and such... my previous phone, iphoe 3g, is still faster than this crap-phone
Cheers,
Soulbrighter
My Galaxy S was laggy as hell brand new out of the box. Sometimes it would hang for what seemed like 10 seconds. I didn't like the Samsung launcher anyway, so I did my homework, made sure I could get into 3-button download mode, and then rooted, wiped and flashed a custom Froyo ROM. I've tried a few ROMs since then and have landed on Insanity with EXT4 lagfix.
Now my Galaxy S is _awesome_ ... I don't even bother overclocking it, everything is smooth.
try a task killer and set it up to auto kill when screens goes off done a few tests with it ,one with no killer and one with and the one with was faster and had no lag fix running too go to the market and get quadrant standard try it for yourself and see
What's the current firmware you're using ? I suggest flashing to JPY and testing it out.
Update to JPY!
If not possible, install a lagfix on your current ROM/kernel.
The amount of lag you describe is terrible, I have never seen it that bad...
I don't think the lag should be that bad, I did experience some occassional lag back on eclair, but never exceeded 5-10 seconds. Usually after loading whatever that app was once, it'd be okay on the next open too.
Since I've upgraded to JPY i see 1-2 second lag extremely rarely.
Maybe you can get a task manager and see if anything is hogging memory?
Thanks for all the responses. The firmware is FROYO.XXJPO, so I'll definitely try flashing to JPY and will report back! Thanks so much for the tip!
I don;t know what is wrong with my captivate.
I have flashed a lot of roms and no matter what I am having this issue.. I install a ROM, set up only my email, and only 1 or two apps.. nothing special
and everything seems to be slow and laggy and just not very usable.
any ideas on what I can do , my last resort is to try to install just a stock rom and see what happens.
its getting me pretty mad really.
ideas, help, i have searched and found this issue with other phones, but not with the captivate.
Hmm weird,probably try getting back to stock and then master clear and then again flash back to the rom of your choice.....!
note:master clear will delete everything on your internal memory card make a backup of imp data before clearing.
Try installing a cutting edge rom with voodoo lagfix. If this doesn't work, you can always just send it back to At&t for a new one if your warranty is still valid.
Its always a good idea to ODIN back to stock and/or Wiping data, cahce and Dalvid cache a few times.
How slow is slow? Quadrant is not always the most useful, but it might be nice to know what your score is for the sake of a baseline.
Just fyi, my current setup gets me around 1700, but stock was pretty solid at 975. If you are getting decent scores, then try using a system monitor to see if a service or app is chewing up your CPU cycles. If your scores are very low, then you may have a lemon.
Sent from my Cappy using Swype and my finger.
OwenW71 said:
How slow is slow? Quadrant is not always the most useful, but it might be nice to know what your score is for the sake of a baseline.
Just fyi, my current setup gets me around 1700, but stock was pretty solid at 975. If you are getting decent scores, then try using a system monitor to see if a service or app is chewing up your CPU cycles. If your scores are very low, then you may have a lemon.
Sent from my Cappy using Swype and my finger.
Click to expand...
Click to collapse
it just seems laggy and almost unusable. example: a compleatly clean phone with no data but Gmail set up, when i go into the market it seems really slow to load the market, then i insall Facebook, its slow as hell, laggy no matter what i do.
there is nothing installed on the phone
i will try odin back to 2.2 stock and see what happens.
SuperCharger made a huge speed difference for me. Unfortunately I still have occasional stability issues, so I'm considering installing ThunderBolt!, which uses Supercharger's script but with their own LMK/ADJ/OOM.
I'm running cm7.1 stable, running off emmc, and every now and then my beautiful NC just locks up, I have it OC to 1.2ghz, I did a search and only end up with results from older nightly threads. Is this a common issue or just me?
PS... I have reflashed and cleared, data,cache, etc..
Thanks
Sent from my NookColor using XDA
Have you always had the issue or did it start recently? I would look at uninstalling any new apps you downloaded prior to the issue starting. There is a good chance you might find a bad app to be your problem.
It wasnt happening before, I tried cm9 with opengl, after I reverted back to cm7(fresh install not nandroid) it started happening, the apps I am running were the same apps I was running before trying cm9(and the freezing problem wasn't happening)
Sent from my HTC Sensation 4G using XDA
Since you are going for a clean install anyway and there is no issue with the CM7 install script did you try the factory reset option or was it just the caches that you cleared? Have you confirmed that you have a good download of the CM7 zip?
Also you might want to try flashing your latest nandroid and make sure that is still running the same as when you created it. If so and you still want to install fresh try it coming off of that one instead of from CM9.
JP
I've had trouble with both Beautiful Widgets and Google Currents locking up my CM7. Got rid of those and I essentially never get lockups any more.
511pf said:
I've had trouble with both Beautiful Widgets and Google Currents locking up my CM7. Got rid of those and I essentially never get lockups any more.
Click to expand...
Click to collapse
I do have beautiful widgets installed, let me remove it and see if it helps
Sent from my HTC Sensation 4G using XDA
So did removing BW resolve the random freeze? My wife's NC is doing the exact same thing and she has BW too. But I just installed CM7 on hers last night so not sure if BW is the culprit or not yet.
I've been running CM 7.2.0 RC1 from SD card about a month now, and I've experienced a number of freezes. On April 5, I had two freezes within a few hours, and I started keeping track of the freezes, hoping a pattern would emerge.
From April 5 through April 17, there were a total of eight freezes. I don't know what the uptime was when the first freeze occurred on April 5, but all subsequent freezes occurred with less than two days uptime. During those 13 days, uptime got above two days on two occasions; both times a "Sleep of Death" occurred before uptime reached three days.
Was there a pattern? Yes! Every single freeze occurred while I was using Opera Mobile browser, and browsing these forums at forum.xda-developers.com.
On April 18 I started using Dolphin to browse the xda forums, and there has not been a single freeze so far. (I still use Opera Mobile for other browsing.) Uptime had reached five days when I voluntarily rebooted this morning.
I realize this may not be relevant to the rest of the discussion in this thread, which seems to deal with CM 7.1. Then again, maybe it is. This seemed the logical place to report the observation.
Update: Opera Mobile has updated to version 12.00.ADR-1204201824 on April 25. I'll revert to using Opera Mobile on the xda forums, to see if it still freezes.
My freezing problem was resolved by moving a bunch of apps from SD back to phone. I left on the SD partition apps I don't use often, and I made sure all apps on my launcher page in ADW were on phone.
threebeers said:
My freezing problem was resolved by moving a bunch of apps from SD back to phone. I left on the SD partition apps I don't use often, and I made sure all apps on my launcher page in ADW were on phone.
Click to expand...
Click to collapse
You really don't gain much and lose a lot by running apps installed to sd. Since everything is automatically on 'sd' with an sd install, those that say they are installed to phone are really still on sd (in /data, which is also on sd). The only reason to install apps to sdcard is if you have so many installed that you have no more room in /data. And with sd installs, usually the /data is made of a generous size. Installing apps to sd slows your system since it has more system overhead to work through.
I know it sounds confusing, but with sd installs, installing to phone means installed to /data which is a partition of your sd. If it says installed to sd, it means it is installed to sdcard, which is another partition of your sd. So no matter where you tell it, it is all on sd and /data is faster because of less system overhead.
For anyone else having this problem, I found that if it was overclocked for me, it would freeze a lot more frequently. But, that may have just been bad luck on my part!
pink401k said:
For anyone else having this problem, I found that if it was overclocked for me, it would freeze a lot more frequently. But, that may have just been bad luck on my part!
Click to expand...
Click to collapse
Came to post the same thing. My nook color will run max OC 1200 but often it will freeze for no reason. After many attempts of uninstalling the many different apps I thought were causing it I started moving the OC lower in small increments and running for a long as possible without a freeze. Finally got down to 975 and haven't had a freeze in days.
Kinda disappointed though since someone got it at 1600 and most run at 1200 and all I can get is less than 1000. I'm probably moving to a Asus Transformer Infinity soon anyways though.
It has been known since the early days of Dalingrin's overclocking kernels that many of the NC's have issues with anything above 1100 MHz and undervolting can create a great deal of instability.
My recommendations are to try 1100 MHz max... and lower voltage .05 mV at each step. I personally never have issues with these settings...
You can then try lowering voltage .05 mV at a time until you start having issues... then increase it back to the last one you had no issues with.
I just leave mine at 1100 and .05 mV lower than the reported "Stock Voltage"