Related
I see these post where people are running there cpu at 1.5 even a few at 1.8.
If i set mine to anything over 1267 my phone locks up instantly and i have to pull the battery.
Am i doing something wrong or something ??
I have used both setcpu and no frills.
Every CPU is different. Yours, unfortunately, is terrible at OCing.
Sucks, but there's nothing you can do about it.
LOL just my luck !!
Have you tried it on any other roms? I could be mistaken, but the kernle could have a bit to do w/ it too.
I can take mine to the highest the CM7 allows w/out issue, not that I'd do it w/ an regularity. That's be a 50% OC.
Ive tried about every rom ... lol They are all the same anything over 1267 locks up... so i just run at 1190 smartass.
That blows.
My wife says she is surprised it even still works .. Ive flashed it 50 or 60 times ...LOL
david032766 said:
My wife says she is surprised it even still works .. Ive flashed it 50 or 60 times ...LOL
Click to expand...
Click to collapse
like a boss
lol, what kernel are you working with?
LeeDroid 3.0.1
Try MDeeJays new kernel it rocks. Always been a flawless flash for me. Just makes sure your rom will run it.
I had this issue with several ROMS. I recently flashed phoenix gb cm rom and oc work awesome Max settings. I'm also surprised my phone still works considering I flash multiple times daily.
Sent from my HTC Inspire 4G
It's hit and miss for me on CM7, I can run 1.5oc pretty easily though.
Ok, sorry if this seems like a stupid question but... I have flashed/tested all of the Tiamat Kernels onto my xoom and it seems that I can only run the 1.4 Ghz Kernel with no random reboots. So I thought that if i download the higher 1.5Ghz or the 1.6Ghz and just under-clock it to 1.4Ghz that should stop it from doing random reboots, but sadly it doesnt and I still get random reboots even with Setcpu Under-clocking it to 1.4Ghz. Now is this typical or am I missing or misunderstanding something? Is there a reason why I cant use the higher Kernels and Under-clock them to 1.4Ghz and get no random reboots? I am only asking because I flashed the Riptide and under-clocked it to 1.4Ghz and it really made my xoom feel much faster and nicer in my hands and would love to keep using the Riptide Kernel.
Thanks in advance,
-Dez
I have the same issues and have been wondering the same thing.
I have similar , with 1.6 with ums
only flashed to get ums , and had a few crash/reboots for the first time since i bought my xoom about a month ago.
what i could do with is a stock speed kernal with all the bells on !
nexan21 said:
I have similar , with 1.6 with ums
only flashed to get ums , and had a few crash/reboots for the first time since i bought my xoom about a month ago.
what i could do with is a stock speed kernal with all the bells on !
Click to expand...
Click to collapse
I too have noticed this, after reading your post I tried keeping the Kernels but with no OC and left it at 1.0Ghz and it still has random reboots. So is there something in the Higher Kernels that are causing it to be unstable regardless of what Ghz you clock it to?
watch setcpu at times. It doesn't matter what you set the clock at in setcpu it will still go to the max clock the kernel allows. I am not sure if it is a bug with setcpu or if it is just the way the kernel works. If you reboot your Xoom when setcpu is at 1ghz, then go and play with the xoom after reboot for awhile. Go back into setcpu and look under the info tab. You will see that the cpu has indeed been running the higher clocks then 1ghz at times. It doesn't run those higher clocks much but it does. Which is most likely why you are getting lockups or reboots. My Xoom seems to love the 1.5ghz kernel but hates the 1.6ghz one.
Funny I was on the same boat. Started out with 1.6...reboots. went to 1.4 no problems. Tried riptide. Got app force closes. Now on 1.5...stable once again. The thing is im not even using OC on any of them
Sent from my SGH-T959 using Tapatalk
tribalb said:
Funny I was on the same boat. Started out with 1.6...reboots. went to 1.4 no problems. Tried riptide. Got app force closes. Now on 1.5...stable once again. The thing is im not even using OC on any of them
Sent from my SGH-T959 using Tapatalk
Click to expand...
Click to collapse
The oc is in the kernal i think , i dont have setcpu installed but cpu still at times peaks at the max 1.504 ghz ac ording to
"Temp+cpu"
https://market.android.com/details?id=com.sanels.tempcpuv2&feature=more_from_developer
Just a quick question for you guys: I recently purchased an Infuse from the marketplace here, and so far I've gotten an absolute TON of lag using the device. I've flashed Infused 1.5 and Bionix with the Infusion kernel, and so far the lag has gotten better, but it's not totally cleared up. I'm definitely not new to Android, but I haven't seen anything like this before. I know that Quadrant isn't a reliable benchmark, but I'm scoring about 1900, OCed to 1.5Ghz.
Just to give an example: I'm using desktop visualizer to add some custom icons to my screen. When I go to select an icon image, it's fine, but it freezes for about 90 seconds when a list of my apps comes up.
Anyone experience this before? And if so, how did you solve it? If this was widespread, I'd imagine there would be complaints all over here.
Which app are you using to set your overclock settings, how many clock speeds do you have enabled, are you under or over volting, and *which governor* are you running?
I have seen some similar problems here when I was using conservative governor with poor choices of clock speed. Right now Infusion 1.5.2 kernel has some issues with not liking the ondemand governor, so I reduced my number of available clock speeds so it would jump to the top more quickly while using the conservative governor.
Also, did you use either the return to stock, or the ultimate unbrick flash before you flashed your ROM? If it was a used Infuse, I would do one of the above before I start looking anywhere else, then reflash your rom/kernel of choice.
I'm using SetCPU with the OnDemand gov (400/1500), no undervolting. I have a profile set to underclock it to 300/700 on conservative when I'm charging, but that's about it.
I think I'm going to use GTG's unbrick/return to stock and root the thing myself, I figured I'd ask before I did anything drastic. My UI is a ***** to set up every time, and I hate wiping because of it.
Just a quick note, I've had some serious lag using the oc kernel... Like real world usage got worse after oc'ing
Sent from my SAMSUNG-SGH-I997 using XDA App
Although it is counter intuitive to the way governors should work I have seen less lag on Infusion 1.5.2 when I use conservative. The ondemand governor seems to be having some issues with the most recent update. If you flash back to 1.0 Infusion you get a max overclock of 1.4, but it is much more stable IMHO. Also FFC is presently broken in 1.5.2 and will hard freeze the phone (battery pull).
I'm debating flashing back to community kernel, but I am going to wait and see how long it takes my battery to drain because I am using some undervolting. You might try using conservative governor and only enable 100, 400, (800 or 1000), (1200 or 1300) and 1500. Honestly the infuse is my first smartphone, but I've tinkered with desktop hardware the last 15 years. It literally amazes me everytime I pull the battery out of this phone and feel how light it is.
I also used the desktop vis app and yes it lagged when chosing apps however it seemed to get better after three or four times but that seems to be the only place it lags for me im using the oc-uv kernal 1.0 clocked to 1.4 seems bulletproof compared to later versions im getting great speed and batt life with this kernal but i had the same lag in the same event as you
Sent from my SAMSUNG-SGH-I997 using XDA Premium App
I'm going to try bringing it back to stock and re-rooting it myself, if only because I trust myself with adb//scripts/rooting, and I'm hesitant to trust someone I don't know. Lag has gotten a lot better since switching to conservative, OCing to 1.6 and undervolting a tad, but it still lags when opening apps or scrolling through long lists. Desktop Vis is of course, still a nightmare.
Oh well, I'll report my findings tomorrow I guess. Hopefully I'll be scoring higher than the 1700 I just pulled in quadrant.
entropism said:
I'm going to try bringing it back to stock and re-rooting it myself, if only because I trust myself with adb//scripts/rooting, and I'm hesitant to trust someone I don't know. Lag has gotten a lot better since switching to conservative, OCing to 1.6 and undervolting a tad, but it still lags when opening apps or scrolling through long lists. Desktop Vis is of course, still a nightmare.
Oh well, I'll report my findings tomorrow I guess. Hopefully I'll be scoring higher than the 1700 I just pulled in quadrant.
Click to expand...
Click to collapse
Sent from my SAMSUNG-SGH-I997 using XDA App
Do you use spareparts?
usually yes, but I dont believe I installed it yet on the infuse. Why?
lag on stock also
I'm 100% stock & get lag also. Definitely in the situation you describe, when the app list comes up for adding shortcuts to any homescreen. Takes forever for that list to come up. Secondly, simply from running for a while, i have to kill all the apps using the built in task manager in order to get it to run smoothly again. It's like it never closes an app. I'm new to android, but guessing this is a problem inherit to android. Can't see how samsung or at&t could have screwed this soo badly to cause it to never close an app. Hoping memory management is better in Gingerbread.
Blario, you're new to Android, so you need to read up on how memory management works with Android. It's not SUPPOSED to kill apps, and that's not what's lagging your phone. In your case, I'd think it was more of a case of WHICH apps you were running.
yeah, the longer I have the phone the more it lags it seems
probably going to push me towards the Evo3D
If you're on stock and after a week or two your phone gets slow as hell (mine did), install a Voodoo lagfix kernel. All the current ROMs include it.
superweapons said:
If you're on stock and after a week or two your phone gets slow as hell (mine did), install a Voodoo lagfix kernel. All the current ROMs include it.
Click to expand...
Click to collapse
I did
I still have random slow downs when it gets bogged down with stuff
I'd give a left nut to have this phone with dual core
entropism said:
Blario, you're new to Android, so you need to read up on how memory management works with Android. It's not SUPPOSED to kill apps, and that's not what's lagging your phone. In your case, I'd think it was more of a case of WHICH apps you were running.
Click to expand...
Click to collapse
I don't do much. Twitter, "Web" (some mozilla stock ish), SMS, phone, Android Market app (browsing), and Maps. I've had it lag up using only those. Far less often, I use Yelp... that's about it.
Not supposed to kill apps? When I kill them it fixes the problem. Maybe it *should* be killing apps?? If its supposed to flush their state to disk... it seems to be doing a poor job at it.
I would be suspicious of your microSD card (if you have one). Do you know what class it is? Have you tried removing it and performing the same functions in which you see lag?
hydrogenman said:
I did
I still have random slow downs when it gets bogged down with stuff
I'd give a left nut to have this phone with dual core
Click to expand...
Click to collapse
I'd more readily assume the 512MB RAM is the issue. Looking forward to SGSII
SolusCado said:
I would be suspicious of your microSD card (if you have one). Do you know what class it is? Have you tried removing it and performing the same functions in which you see lag?
Click to expand...
Click to collapse
It's the stock card that came with the phone. Any way to check? The apps are installed to it... so removing it I wouldn't have the apps available anymore.
A little update: I returned back to stock and re-rooted. I installed 3E, then CWM, then threw on Infused 1.5 and Infusion, OCed to 1.6Ghz and slightly undervolted (about 25-100mv along the range) using SetCPU.
As of right now, it still lags on occasion, but not as bad as it did. Quadrant is giving me a whopping 1300 average score, with a low of 800 and a high of 1600. This is just pathetic.
Will these ever go away on my nexus s? I have gotten them in everything from stock 2.3, cyanogenmod 7, stock ICS, oxygen, and every single ICS rom I have used. I understand some software bugs take a while to find but I have had this bug for over a year, will it every get a fixed? (Or is this not a software bug but an actual issue with my phone?)
Could be cause from UV settings if you touched them
Sent from my Nexus S using XDA
ThisNight said:
Could be cause from UV settings if you touched them
Sent from my Nexus S using XDA
Click to expand...
Click to collapse
Nope. I usually run 200 mhz minimum and 1200 max for my cpu. On stock I also ran stock volts.
tominater12 said:
Nope. I usually run 200 mhz minimum and 1200 max for my cpu. On stock I also ran stock volts.
Click to expand...
Click to collapse
Well, you're running an overclock... Try running without.
CM7 has a sleep of death/reboot bug, so try another ROM not based on CM7 too.
Highly recommend Oxygen 2.3.2 coupled with Franco 08.12.2011 GB kernel.
If you're interested in ICS ROM, give AOKP ROM and Matr1x kernel a try. It's rock stable for me. I just rebooted to flash the new build, but before that it lasted for couple weeks for me without rebooting. Link to AOKP ROM is in my sig.
tominater12 said:
Nope. I usually run 200 mhz minimum and 1200 max for my cpu. On stock I also ran stock volts.
Click to expand...
Click to collapse
There's your problem. Perhaps increase the voltage? Your phone may not be able to handle the frequency without extra voltage.
There should be no random reboots if you never touched anything kernel related. If so, then bear the consequences.
I've been using CM9 v2.2 for about 3 months now haven't overclocked or undervolted and haven't had any "random" reboots ever.
I'd highly recommend the Androxide ROM along with Air Kernel. I've been running this combo overclocked to 1200 without any voltage setting changes for a decent amount of time.
random reboot frequency - about once a week ..
AeroEchelon said:
There's your problem. Perhaps increase the voltage? Your phone may not be able to handle the frequency without extra voltage.
There should be no random reboots if you never touched anything kernel related. If so, then bear the consequences.
I've been using CM9 v2.2 for about 3 months now haven't overclocked or undervolted and haven't had any "random" reboots ever.
Click to expand...
Click to collapse
I second that. Usually OCing requires raising voltages across the board. I use +25mV (arm and int). If you're suing a matr1x kernel that's even more reason to raise voltages, because afaik that kernel is undervolted by default.
Best of luck.
zgomot said:
I second that. Usually OCing requires raising voltages across the board. I use +25mV (arm and int). If you're suing a matr1x kernel that's even more reason to raise voltages, because afaik that kernel is undervolted by default.
Best of luck.
Click to expand...
Click to collapse
Thirding it.
If you are having problems then roll everything back to stock... its not good enough to say you have run every rom , yet fail to mention you OC. What other tweaks do you run? Deep Idle?
I'd bet if you flash CM9 with no tweaking it, it will be fine.
bringonblink said:
I'd bet if you flash CM9 with no tweaking it, it will be fine.
Click to expand...
Click to collapse
Or just about *ANY* rom for that matter. First ensure you can run it stable without OC, UV, didle, mods, themes etc then, by all means, go ahead and tweak to your hearts's content.
Overclocking to 1200mhz CPU only does NOT require extra voltage across the board, but possibly a boost at the 1200mhz voltage. Each frequency runs at a different, changeable voltage which has nothing to do with all the others. LiveOC, however, raises the frequency of each step and as such generally requires a boost in voltage across the board or thereabouts.
As for the problem the OP is having, who knows. Could you describe any specific things you've done, though? Full wipes (detail what you wipe), titanium backup restores, etc.
First thing i would be trying now is to do a full wipe (factory/data reset, format /boot, format /system), flashing either stock 2.3.6 or 4.0.3 and installing only necesseties and try for a week or so. If there are still reboot problems, describe them and hopefully i can give you some useful things to try. If you had this problem before the 1 year mark you could have probably gotten the phone fixed/replaced under warranty, though. If it is now over a year i'm afraid that's too late though.
Just for info:
ALWAYS on stock, unrooted, right now 4.0.3 OTA. Since 4.0.3 random reboots, w/o any culprit cause I can find..
So, I guess, has nothing to do with ROM, voltage, solar storms, etc..
Well this is all bullcrap. . . i installed CM7.0.1 and CM7 RC1 and the latest ICS from CM team and her phone either randomly reboots or switches off totally while charging in the night.
Its got bugger all to do with the kernel because i used the standard kernel with all the CM7 & CM9 roms and the same things happen over and over.
Also the OC'ing idea is BS, i don't OC my nexus S or hers and even mine suffers random reboots.
there has to be some code somewhere thats not behaving a sit should and google never sorted it and CM team never found it, or the hardware is just ****ty in this hand set.
Have you tried other ROM besides CM7? I remember when I flashed CM7 for the first time. My phone never liked it, it was all bugs for me. I even noticed that OC'ing would generate problems on any ROM.
I just ran away from CM7 and OC'ing.
Try Oxygen ROM (or stock as they stated before) with all set up to defaults and test for a while.
hutzdani said:
Well this is all bullcrap. . . i installed CM7.0.1 and CM7 RC1 and the latest ICS from CM team and her phone either randomly reboots or switches off totally while charging in the night.
Its got bugger all to do with the kernel because i used the standard kernel with all the CM7 & CM9 roms and the same things happen over and over.
Also the OC'ing idea is BS, i don't OC my nexus S or hers and even mine suffers random reboots.
there has to be some code somewhere thats not behaving a sit should and google never sorted it and CM team never found it, or the hardware is just ****ty in this hand set.
Click to expand...
Click to collapse
I admit I had reboots with cm7' but with latest cm9 nightly I have none. Stock kernel stock oc and stock voltage with deep idle off
Sent from my Nexus S using Tapatalk 2 Beta-2
bmszabo said:
Just for info:
ALWAYS on stock, unrooted, right now 4.0.3 OTA. Since 4.0.3 random reboots, w/o any culprit cause I can find..
So, I guess, has nothing to do with ROM, voltage, solar storms, etc..
Click to expand...
Click to collapse
The update was pulled for many reasons. Try stock GB or Oxygen ROM and enjoy life without freeze, sleep of death or reboot...
For those of us that have dealt with lag on JB 4.1.2 and are using Touchwiz I've created this thread to spitball, trouble shoot or even complain about it.
From what I understand it's Android 4.1.2 related. I've been reading that it's an issue with TW and 4.1.2 itself. Some have suggested that using a custom launcher will help get rid of the lag. I've seen this be true on Nova. I have been able to get no lag on TW only by not having any widgets on the home screen. This leads me to believe that part of the lag is a result of having to render the widgets and load the information there within.
Others complain of lag during gaming (Temple Run 2 is a big one). I've looked through the forums, and searched multiple threads and it appears that other S3 variants and even tablets like the Tab 2 is having issues with 4.1.2. My G Note 10.1 had it as well.
So in the hopes of figuring out what the culprit actually is or even to vent frustration at such things here we are.
If there is a thread already like this MODs please let me know and/or close it. :good:
I don't use any widgets and I get crazy lag while playing ingress. I've only ran touchwiz and its lagged on all. Sucks but not that big of a deal.
Sent from my SCH-I535 using xda app-developers app
I also get lag and/or lockups on occasions. On stock rooted 4.1.2. So is not just CleanROM. I may go back to 4.1.1. I can't seem to find enough benefit to stay on the current stuff. I've tried different kernels, etc. No dice. The only game I play is candy crush, and it's HORRIBLE. Everything moves in slow motion. LOL. It sticks how the mods handled this, I feel it is relevant. It's an issue, well known. There are MANY complaints about it.
I've had the same issues with Candy Crush. No lag on 4.1.1, and tons of lag in 4.1.2. Like you said, it almost looks like the app is in slow motion. I have yet to find a solution to this.
Man you guys are right on the money. I've reverted back to 4.1.1 because of all the lag. I'm currently on GalaxyMod Rls 13, which to me has the least amount of lag. Homescreens don't redraw, menus are smooth (for the most part anyway, you scroll back to the top of the settings menu and it tends to jump on occasions, no matter what ROM I'm using). I hope 5.0 addresses these issues. I remember how excited I was when 4.1 first dropped... Arguably the best build Android has ever made.
Sent from my SCH-I535 using xda premium
Some say they don't get lag. Just a theory here, but I went the OTA route, then rooted and unlocked. Got lag, even flashing back to 4.1.1. Thing is, I still had the current OTA partitions. So, I Odined back to K3. TADA! No more lag. Makes me think that possibly those that took the OTA are getting the lag because of the partitions that are updated. Those NOT experiencing lag are ones still on K3 partitions, but have flashed up to MB1 ROMs. Maybe? Just a theory.
countryfolk07 said:
Some say they don't get lag. Just a theory here, but I went the OTA route, then rooted and unlocked. Got lag, even flashing back to 4.1.1. Thing is, I still had the current OTA partitions. So, I Odined back to K3. TADA! No more lag. Makes me think that possibly those that took the OTA are getting the lag because of the partitions that are updated. Those NOT experiencing lag are ones still on K3 partitions, but have flashed up to MB1 ROMs. Maybe? Just a theory.
Click to expand...
Click to collapse
Which K3 tar did you use? I'd like to try this myself on my wife's phone. Thanks.
NVM I got it.
Sent from my Nexus 7 using XDA Premium HD app
I have two s3 phones in the family. One of them is on cleanrom and one is on stock unrooted. Both of them suffer from lag. We do not play games on our phones. The last that we notice is when doing things like texting. The keyboard is really slow to come up. And when the auto correct list comes up, it is very slow. Scrolling also seems to bog it down. I am not sure what is going on, but it is a definite step backward from 4.1.1. I how that there is a solution that does not involve going back to 4.1.1.
Sent from my Nexus 7 using Tapatalk 2
usmaak said:
I have two s3 phones in the family. One of them is on cleanrom and one is on stock unrooted. Both of them suffer from lag. We do not play games on our phones. The last that we notice is when doing things like texting. The keyboard is really slow to come up. And when the auto correct list comes up, it is very slow. Scrolling also seems to bog it down. I am not sure what is going on, but it is a definite step backward from 4.1.1. I how that there is a solution that does not involve going back to 4.1.1.
Sent from my Nexus 7 using Tapatalk 2
Click to expand...
Click to collapse
I wonder if the GS3 suffers from graphic redraws? Maybe it's not caching the images perpetually, only drawing them when needed. I've noticed this when it loads widgets, scrolling through menus, and when you have a lot of notifications(the drop down shade hesitates when it's opening and closing). I don't think it's hardware, as there are a few HTC phones with the same adreno GPU and they don't lag. My previous phone, the EVO 4G LTE, didn't lag at all, and they share the same adreno graphics hardware. Hero's Axis Rom addresses most of these issues, as my experience with his roms have been positive. It's not completely gone, but it's better than stock. I'd recommend using his rom if you have these issues.
fix, maybe?
Hey, all. So I had gotten the i757m, same problem as here. Got a new one from Bell, and it was slow as hell too.. Here's what I did.
I disabled everything I could, all the bloatware.
100% HD Games
Asphalt 6
Google Play Books
Google Play Movies
Google Play Music
GPS Navigator(Let's be real here, it sucks anyways.. use google maps)
Let's Golf 3
Mobile TV
Sympatico.ca
Yahoo! Finance
Yahoo! News
This helps(after a 4.1.2 upgrade via kies)
Next step: Developer options
Turned off animations(Transition Animation Scale)
under apps > Do not keep activities check box. Destroys processes after the user leaves them. Not so awesome for multitasking, but hey, whatever works, right? 262 MB used 1.7GB free . Seems like a win to me.
Do you guys overclock? This is just a theory, but overclocking or undervolting overclocking or flashing too many times seems to slow down phones. Have any of you guys tried to go back to stock and then factory reset and started over? I think that might help. Also, I do see lag, however I only see minimal lag, maybe its because I rarely have anything on my phone? I am also on stock kernel and that seems to work the best for me right now, I used to run custom kernels, but some of them keep causing issues and weren't stable enough or gave me worse battery life. I will try the new leankernel as I like leankernel from the galaxy nexus and have previously tried lean before and had a good experience. Hopefully this at least partially answers the OP's question
Well there have been 3 Touchwiz kernels that worked for me and that's leankernel, kt747 and Zeus. I only overclock to 1.8 ghz or 1.6 ghz those speeds give me the least problems.
I just ran temple run 2 just fine. Here is my setup. MOAR ver.18 latest firmware mf1, KT747 kernal.
undervolt
1175 1160 1160 1150 1150 1125 1125 1100 1100 1050 1050 1050 1025 1000 1000 950 950 925 925 900 900 900 900 880
min 189
max 1512
i/o cfq
governor
ktoonservative
screen off set too 810mhz
Thats it.
I get at least 22hrs of charge with 39% left. I can't let drain down fully because i need it to be fully charged every night before bedtime. I basically charge it fully before bed and i'm left with 39 to 20% by 9pm the next day. I'm on wifi at home and 4glte at work.
---------- Post added at 11:26 PM ---------- Previous post was at 11:23 PM ----------
last night i had a 3% battery drain within 5hrs. I think that's pretty awesome. While i'm asleep.
I'm with Verizon running BoneStock 3.2 and no lag at all. Fastest ROM I've used so far. With stock kernel
Sent from my SCH-I535 using xda app-developers app