Related
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.
I'm really very happy with my Nexus S 4G. It's unlocked and rooted, but otherwise pure stock and I really like it that way.
Coming from the Hero it's a pleasure to have a phone that doesn't require heavy modification to make it perform properly. Still, I miss the thrill of flashing ROM's and kernels.
I would like to try a kernel...mainly to simply o/c a bit, but I don't want it to suffer stable and reliable operation. I recall with the Hero, some of the kernels would adversely affect things like the GPS, making it something I couldn't rely on.
So my question: what kernel can I use that is uncapped, but will otherwise be as close to stock as possible?
Thanks for your thoughts!
Kernels are pretty different over here. I don't even know what's closest to stock. They pretty much all have mods in them. Matr1x kernel is pretty popular. You may have to up the voltage for it if you oc to 14xx. 1200 seemed pretty stable to me with default voltages. Currently franco kernel is pretty popular. You can't oc it, but it seems pretty snappy without oc. GLaDOS is also being used a bit but i've read some mixed reviews and for me at least it did seem a little lagging at times for the short period I ran it. I tried Trinity kernel when I first moved over from the hero and it seemed kind of flaky though it's possible that could have been due to the kang I was running. There are a few others out there. Cm7 kernel has a lot of the same mods cooked in though it's likely not the latest updates. You will see a lot of mention of BLN and Voodoo. There are apps on the market for those features and there's an app nstools that has some kernel config settings you can adjust depending on kernel. Mainly just try to read a lot. Most of the roms and kernels haven't given me any major issues beyond the random reboot, which coming from the hero, just means "normal" lol.
Sent from my Nexus S 4G running CM7/franco.Kernel
Once you flash you can't stop O_O that my experience i'll direct you to Peteralfonso's kernel on his website here
Searching the forums would help you more than anything. You will get more info by searching, rather waiting people to reply here. These questions are asked on daily basis. And get the same replies everyday. I don't sound to be mean but seriously there is more info than you can get by starting another thread, only thing is you need to dig the info.
I have tried a few different roms and kernels and for once cm7 runs perfect for me w the supplied kernel. No reboots. Has been stable at 1440 performance for testing but I usually leave it at 1000 on demand.
Yeah they all have this blinking light crap in it now by default which I hate, and the lights turn off and I don't like that either. I want the light on when I'm using the phone and off when I'm not, not the other way around!
Sent from my Nexus S using XDA App
I like the bln mod, but I do not like the one that turns off the backlights when using the phone. It's just easier to use the buttons imo and gives a quicker visual reference for everything. Otherwise I mostly am left wondering what is up with all the black space.
Sent from my Nexus S 4G running CM7/franco.Kernel
suhas_sm said:
Searching the forums would help you more than anything. You will get more info by searching, rather waiting people to reply here. These questions are asked on daily basis. And get the same replies everyday. I don't sound to be mean but seriously there is more info than you can get by starting another thread, only thing is you need to dig the info.
Click to expand...
Click to collapse
I hear you on that, and spent a lot of time reading comments and concerns and problems about the various kernels available. They all seem to pretty much be experimental, with various idiosyncratic problems and lots of bells and whistles such as aforementioned BLN, Voodoo, deep idle, etc.
I thought maybe I was missing something in my search for a kernel that would allow o/c, but not have the stability concerns of a the feature-rich, highly customizable kernels.
I think the Matr1x kernel will be your best option, u can OC it till 1400mhz, what I don't recommend to do, but at 1200/1300mhz its pretty stable.
It also got many options like BLN, BLX, Live OC, touch wake, etc.
But if you don't want them, why you just don't use 'em?
Like just flash the kernel and keep it like it is, and maybe do some overclocking.
wanna stable ? stock kernel
basically , there is no kernel more stable then stock ...
qtwrk said:
wanna stable ? stock kernel
basically , there is no kernel more stable then stock ...
Click to expand...
Click to collapse
True, but he prefers to OC it a bit.
Sent from my Nexus S
franciscofranco's kernel (link) works best for me. It's fast (no lags even without OC, I'm running at stock 1000 MHz), reliable (I've been using it for at least month and I haven't got any random reboots or application hangs) and battery efficient (thanks to deep idle and other tweaks).
irizwan said:
Once you flash you can't stop O_O that my experience i'll direct you to Peteralfonso's kernel on his website here
Click to expand...
Click to collapse
+1
Never found a more stable kernel than Pete's. However, I've been on Glados for the last week or so and am seeing excellent battery life with Deep Idle.
Icecoldmeat said:
True, but he prefers to OC it a bit.
Sent from my Nexus S
Click to expand...
Click to collapse
personally i think overclock is totally unnecessary , why ? 1 GHz is sufficient to handle all job you require to the phone...
Best thing to do would be compile your own stock kernel with oc.
qtwrk said:
personally i think overclock is totally unnecessary , why ? 1 GHz is sufficient to handle all job you require to the phone...
Click to expand...
Click to collapse
True again. I love 1100mhz because it gives you a bit more speed with no lagg, and you batterylife is still awesome.
Sent from my Nexus S
deville~> said:
franciscofranco's kernel (link) works best for me. It's fast (no lags even without OC, I'm running at stock 1000 MHz), reliable (I've been using it for at least month and I haven't got any random reboots or application hangs) and battery efficient (thanks to deep idle and other tweaks).
Click to expand...
Click to collapse
with deep idle OFF, the difference between the two is minimal, idle stats displayed deep idle has been 0
Downloaded and testing peter alfonso's kernel now. Its very minimalistic, no options like deep idle etc, and u can OC it up to 1400mhz. Running 400-1100mhz for a day now and the battery life is just awesome.
U can find it on:
http://www.peteralfonso.com
Sent from my Nexus S
albundy2010 said:
Best thing to do would be compile your own stock kernel with oc.
Click to expand...
Click to collapse
Or one with LiveOC which is kinda better cause it also OC the GPU =D
+1
Click to expand...
Click to collapse
the akward moment when someone said they +1'd you but actually didn't -_-
there're too many to choose.i don't like the ones that update so often indeed.
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...
Now that ics is out and working great on the transformer (i have a sl101 myself but same thing basically) and being able to force
the gpu to do the 2d stuff i thought it might be worth a shot to make a kernel with lower clock speed like 500-600 mhz max
and lower voltages maybe its also possible in the kernel to lower the wifi strength to get the absolute max battery life.
Other kernels are all for more speed so battery life isnt as great as stock.
Im no programmer or would know how to do this myself else id try but it seems like a feasable idea if anyone wants to try,
now we can force the gpu to do the 2d stuff the cpu should be able to go lower without a performance hit.
so good idea or bad? lol
If you're using another kernel, you can already set the min-max speeds if you want to underclock. Some of them allow undervolting too.
Sent from my Transformer TF101 using xda premium
No i run stock as that seems to be most stable and best battery life.
I know a custom kernel can be underclocked with additional program but im guessing more can be done when
compiling your own kernel but im not too sure.
Imoseyon gave me permission to link his kernel here on XDA. Please thank Imo on here or RootzWiki, and please donate to him if u can.
ICS and JB kernels are available.
v 4.0 is the newest version for TW JB 4.3 ML1 only.
Older versions are available (4.1.2)
Experimental builds are also posted on RW. I personally dont want to link them here since I cannot help if something goes wrong. So keep an eye on the RW thread if you can help in testing.
Link to OP/ICS kernel http://rootzwiki.com/topic/31329-ke...el-minimalistic-kernel-ics-v13-jb-v03-112512/
Link to JB kernel changelog https://github.com/imoseyon/leanKernel-d2vzw/wiki/TW-ChangeLog
Link to source https://github.com/imoseyon/leanKernel-d2vzw
All credit goes to Imoseyon
Please feel free to post results from Roms.
OK so running this on jelly beans b 4 and it is super fast. Works like a champ! Great work imoseyon. I tried ktoonsez and this way smoother on touchwiz. Like butter baby!
Sent telepathically
Are there any custom governors with this kernel?
Sent from my SCH-I535 using Tapatalk 2
No just three. Not as many options but already set out of the box so to speak. Changed my io scheduler to deadline and let her rip.
Sent telepathically
I hope to have interactiveX running on it before the 1.0 release.
Also, you can find the change logs here: http://revision.io/embeds/leanKernel-galaxys3-tw
Thanks for sharing.
Running fine on clean Rom 5
Sent from my SCH-I535 using Tapatalk 2
does not work with Taste of Beans 3.5k at all..
color flux
removed boot animation
reboots
battery gets SUPER HOT!
had to do a batt pull, boot into recovery, and go from there.
Ran fine when it first booted...benmark scores were very high...running very smooth...
Then after a reboot things got kinda wonky...
Seemed to be running rather hot...and I seemed to lose the ability to control clock speeds with system tuner...
I could sit in the app and watch the max/min speed change without any input from me...and setting it to 1512/384 manually would only last a matter of seconds...
...after the first reboot...i would set clock speeds...do something like run a quadrant test...go look at clock speeds and max would be at 1900 even though i set it at 1512...if i ran antutu at the end of the test it would come back as 1134mhz inn the system info even though I set it to 1512...
Based on my observations...it seems like the moment you put the CPU under any sort of stress...the clock speeds wig out and you lose the ability to control them...
Edit: I can repeat it every time I run a benchmark...quadrant, antutu, smart bench, whatever...the kernel completely loses the ability to control clock speeds..I noticed a similar problem with the Ziggy kernel that synergy uses...
The only non stock kernel that has worked right is 747...and in its ktweaker app there is a setting to "lock" clock speeds so that other apps can't change them...it specifically says "like benchmark apps." It may be something to look into...
Its a shame because on the initial boot up of this kernel my phone had never felt as smooth or performed as well...
sent from my VZW Galaxy S3 running Synergy Jelly Bean
Metfanant said:
Ran fine when it first booted...benmark scores were very high...running very smooth...
Then after a reboot things got kinda wonky...
Seemed to be running rather hot...and I seemed to lose the ability to control clock speeds with system tuner...
I could sit in the app and watch the max/min speed change without any input from me...and setting it to 1512/384 manually would only last a matter of seconds...
...after the first reboot...i would set clock speeds...do something like run a quadrant test...go look at clock speeds and max would be at 1900 even though i set it at 1512...if i ran antutu at the end of the test it would come back as 1134mhz inn the system info even though I set it to 1512...
Based on my observations...it seems like the moment you put the CPU under any sort of stress...the clock speeds wig out and you lose the ability to control them...
Edit: I can repeat it every time I run a benchmark...quadrant, antutu, smart bench, whatever...the kernel completely loses the ability to control clock speeds..I noticed a similar problem with the Ziggy kernel that synergy uses...
The only non stock kernel that has worked right is 747...and in its ktweaker app there is a setting to "lock" clock speeds so that other apps can't change them...it specifically says "like benchmark apps." It may be something to look into...
Its a shame because on the initial boot up of this kernel my phone had never felt as smooth or performed as well...
sent from my VZW Galaxy S3 running Synergy Jelly Bean
Click to expand...
Click to collapse
This is due to thermald and is normal behavior. I include a tweaked thermald in my ICS kernel but I don't really like the way i implemented it. I'm going to think of a different way to handle this for my JB kernel.
Imoseyon said:
This is due to thermald and is normal behavior. I include a tweaked thermald in my ICS kernel but I don't really like the way i implemented it. I'm going to think of a different way to handle this for my JB kernel.
Click to expand...
Click to collapse
So it would be "stress" related sorta...but more heat related specifically?...its a bummer because my phone does not like 1900mhz at all...and really starts to heat up/lag at that clock speed...
So if the kernel is going to "reset" all the time I'm gonna have to stick with 747 because its the only one (except stock vzw jb) that sticks no matter what I throw at it
Edit: I will however say...the kernel is completely compatible with Synergy 118...and like I said before...when it initially booted the phone was screaming...and performing better than ever...
So keep up the good work and I'll keep my eye on things...
I didn't run your kernel on ICS...wishing I had tried it out now lol
sent from my VZW Galaxy S3 running Synergy Jelly Bean
Despite what a previous user said I'm running this on tasteofbeans 3.5 with no issues. I've ran both 0.2 and now 0.3
Sent from my SCH-I535 using Tapatalk 2
Has anyone ran this kernel over CM10 nigthlies?
Sent from my SCH-I535 using Tapatalk 2
TheGman125 said:
Has anyone ran this kernel over CM10 nigthlies?
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
This is for TW roms not for aosp roms, imos has his aosp kernel in rootz
Sent from my SCH-I535 using xda app-developers app
Sorry to hear Met. My phone has never run so well. I'm not experiencing any heat ups or problems set at 1700mzh. When I I run Vellamo it lists the kernel max at 1900mhz but when I check setCPU its locked at 1700mzh. I ran LK on ICS and it was simply amazing. It was the only thing I missed moving to JB. Plz remember that this kernel is just days old and it will continue to get better with updates from Imo. Keep the reports coming guys, it's the best thing to do to help.
What I've noticed is that neither this kernel or ktoonsez like Android tuner or system tuner. They make the kernel go haywire if using either one. I don't know why. That will b why ur min max doesn't match in k tweaker when u open after reboot. I use set CPU for imoseyons kernel and it works great on EVERY tw new base rom and so far has been the best I've tried and i test extensively. Lol.
Sent telepathically
Any chance of Call Recorder kernel support Imo? I only ask becaues several of your kernels for other phones I have owned did support it.
jdub251 said:
What I've noticed is that neither this kernel or ktoonsez like Android tuner or system tuner. They make the kernel go haywire if using either one. I don't know why. That will b why ur min max doesn't match in k tweaker when u open after reboot. I use set CPU for imoseyons kernel and it works great on EVERY tw new base rom and so far has been the best I've tried and i test extensively. Lol.
Sent telepathically
Click to expand...
Click to collapse
I would not use KTweaker with this kernel. I remember reading some where its specific for KT kernel. I have had issues using Android Tuner and system tuner on previoulsy used Rom/Kernels as well. I use SetCPU and it works great, I know its a paid app but its so worth it especially if you plan on using custom kernels. Theres a free setCPU version floating around but that app isnt supported anymore.
V.3 locks my cpu to 1900mhz...so i reverted back to v.2 and all is well. 11180 antutu bench mark @ 1520mhz, 10080 @1900mhz
For the ppl not needing to OC try v.2, u might have better results.