As an aside, this thread gave me the nudge I needed to fix the performance problems I was having. Seems Advanced Launcher was grinding my Galaxy to a halt (as per the original poster's description). Uninstalled and it's been rapid since. So, thanks for that.
Maybe the most important thing is that you shouldn't install ADW Launcher from the Market. You should download the system version from inFECT's site and install it from recovery. Most of your problems with the dialer are because of ADW.
Sounds familiar all those FC's while navigating. Had the same problem the other day when I used Mobile Maps 10. Really annoying. I also had it overclocked at 710 Mhz. So I made a back-up of all the apps using Titanium, wiped using recovery and then applied the update.zip and installed G.apps. Then I just re-installed all my apps with one click (Titanium: real time-saver!) and didn't overclock. Now everything seems to work fine with better Linpack scores. Could it be all those FC's have something to do with overclocking the CPU?
I doubt it. I just tried my phone without overclocking and still got tons of FCs. I've been reluctant to go the complete wipe route (I believe the apps, but not the app settings are backed up by Titanium) , but at this point, it sounds like that's one of the few solutions that I haven't tried.
I doubt it. I just tried my phone without overclocking and still got tons of FCs. I've been reluctant to go the complete wipe route (I believe the apps, but not the app settings are backed up by Titanium) , but at this point, it sounds like that's one of the few solutions that I haven't tried.
With Titanium all apps with data are backed up. Considering the fact that I'm switching between ROM's quite often this app is definitely worth the money.
With Titanium all apps with data are backed up. Considering the fact that I'm switching between ROM's quite often this app is definitely worth the money.
I went ahead and bit the bullet with a wipe and reinstall. (Actually several wipes and reinstalls, I had to get the sequence just right in terms of installing the JIT and ADW zips).
Things are much better (although there are still too many FCs for my taste). It also eliminated a variety of other problems I was having including intermittent camera failure (getting blank pictures) and the inability to install infect's ADW Launcher.
The only bad part is I've had enormous problems with Titanium (instant crashes on startup, failure to get root authorization, and consistent failure to do batch operations such as restore). I've updated and reinstalled Titanium several times, and even updated my superuser program, but in the end just did a lot of redownloading of various apps and putting in settings again. I'd love Titanium if it worked, but it's just is not reliable in the "restoration" department.
I did an interesting test last time. Playing a video with rock player at either 614 or 710 mhz is unusable (614mhz is better, but lots of not responding errors). The video lags enormously, and after a while the sound disapears. At 528 Mhz? Everything runs smooth.
Making an analogy to PC: you can boot to windows and run light apps, but your system is not "prime-stable" (or x264 stable, or whatever). You need more voltage and/or cooling, or less clock. Not all chips overclock the same.
Overclocking any cpu can shorten its lifespan. The key is temperature. The cooler the better. Since its virtually impossible to improve cooling on our phones, we would need to know how far our cpu can be pushed without overheating. 710 is probably near the limit. Some people have had strange things happen when overclocked that fast. To me that is a warning sign. I chose 614.
Lower temperatures help overclock, but your overclock can become instable well before the CPU overheat. ARM chips generally don't get too hot. Even if you use an liquid nitrogen cooling, I doubt that galaxy's CPU can reach 2Ghz for example, while an netburst celeron can reach 4+Ghz @ 70~80
looks like you know your stuff, I dought anyone would start arguing with you . but as I said before the difference of over clocking this phone's cpu is so unnoticeable that it just not worth the risk.
Well I moved on to 1.3.4 and that seems to have improved things dramatically. Still too many FCs for my taste, but far far better than I was ever able to do with 1.3.3 (even with memory threshold tweaking).
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.