Related
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
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...
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.
Hi everyone,
I'm new to Samsungs tablets, I have HTC HD2 so i have a little knowledge about firmwares, kernels, roms, flashing and etc. and now i have problem with galaxy tab 2 p5100.
The facts that i know correct me if i am wrong:
1-custom kernels for overclocking doesn't work on stock firmware (ICS,JB)
2-you need to have either AOKP 4.1.1 or CM(CyanogenMod) 9,10,10.1 for overclocking
after flashing CM 10 on my TAB, i tried to flash AOKP_p51xx_1-52GHz_v2-2.zip using CWR but phone stuck on "Samsung Galaxy Tab 2 10.1" logo then i flashed CMOC10-Kernel the same way and it worked so the questions are:
1-why AOKP kernel didnt work i saw posts indicating that it is working, is there anyhing that i have to do before or after flashing this kernel?
2-i have succeeded to flash CMOC10-Kernel, i went to the settings - performance and i change my max frequency to 1380 and set it on boot, so is it enough? or i have to use special program to overclock GPU?
3-what governor is the best for this tablet?
and final question, it is about auto brightness setting, it seems CM 10 can't detect room's light level correctly is there anyway to solve this or change sensitivity of light sensor?
1. The aokp kernel did work, because if it didn't your phone would have never booted!
2. That's enough, but a word of advice, over clocking reduces batter life and increases heat.
3. The governor you want to use totally depends on you and your usage!
4. Try a different auto brightness app like lux auto brightness
prince147 said:
1. The aokp kernel did work, because if it didn't your phone would have never booted!
2. That's enough, but a word of advice, over clocking reduces batter life and increases heat.
3. The governor you want to use totally depends on you and your usage!
4. Try a different auto brightness app like lux auto brightness
Click to expand...
Click to collapse
1. Phone(tablet) didn't boot after flashing aokp kernel! it stuck on Samsung logo (not cyanogenmod logo) as i mentioned in my post the kernel that worked is CMOC10-Kernel produced by johnsel ... wonder why aokp kernel didnt work!
2. i know the consequences of overclocking, reducing battery life(sometimes hardware life) more heat it is predictable, i was just asking is there any program apart from default cyanogenmod settings to see GPU clock also because all programs that i tried they just show me cpu clock not gpu! of course it is not so important ... just interesting!
3.i am using smartass v2 on my htc hd2 it is recommended governor for my htc, but i don't see that option in cm10 is there any place (some website) that i can get information about governors?
4.thanks for your suggestion i will try that :good:
Finally thank you so much for helping me, i appreciate that :good::good::good:
1.I'm not so sure about your problem, report it to the dev for it to be solved
2.this post contains info about how to on gpu over clocking http://forum.xda-developers.com/showthread.php?p=31683246
3.these two articles explain clearly about governors http://www.xda-developers.com/android/your-guide-to-governors/
http://androidforums.com/xperia-mini-all-things-root/513426-android-cpu-governors-explained.html
Sent from my GT-P3100 using Tapatalk 2
Hey, I've been under the impression that keeping force GPU rendering was typically a good idea, but after upgrading from 4.3 I feel like it has become more of a burden, or something.
When I under volt pretty drastically, I notice I get reboots way more commonly and frequently with it on, all else equal.
Anyone have any input? Am I just crazy?
Sent from my SCH-I535
:thumbup:
One shameless bump...
ur crazy..lol jp
need more info what rom are u on and kenel stock or custom
im on liquidsmooth kitka-t nightly i use BMS kenel undervolt -50 acros the board runs fine but if i undervolt to much i get reboots for ex -125 i would have reboots kenels are fone dependent also notice with settings u gotta play around with them.i did notice on kitkat bat or bat stats are not as good as 4.3 roms