yashsingh1/xdaforums huggingface dataset:
[T-Mobile, Samsung Galaxy SIII] stuff:
+1 on a ATT version of this rom
[T-Mobile, Samsung Galaxy SIII] Serious_Beans:
This is a kernel buddy lol
[T-Mobile, Samsung Galaxy SIII] stuff:
My apologies. Meant Kernel. Just been browsing way too many roms today so I just typed it up.
[T-Mobile, Samsung Galaxy SIII] ImARaptor:
What settings does everyone use in SetCPU? (if you actually even use it or use anything similar) I personally have the min set at 720 and max at 1890 :) that why my keyboard and launcher is perfectly smooth :)
[T-Mobile, Samsung Galaxy SIII] blacksheep242:
I am not running any task killer and I use the built in task manager to "clear memory" before running. Weird. Gonna try that redrum Rom with this kernel and try again. Will report back soon
[T-Mobile, Samsung Galaxy SIII] walliester:
I'm getting 6200 with out setcpu,I'm happy camper lol and battery will last me more than 10 +hours constantly using YouTube and FB and xda......thanks Roman...
[T-Mobile, Samsung Galaxy SIII] carrrnuttt:
Below is what I got on stock rooted with all bloat and background noise present and accounted for:
[T-Mobile, Samsung Galaxy SIII] ViralCipher:
Hey, I have a few questions about this kernel before I try it. I am currently on redrum's Lean Stock ROM version 3. Do I just need to do a backup, then flash this kernel in recovery and then wipe dalvik/cache? Also, I have busybox installed in system/xbin. I want to use the CPU1 Sleep script as well. Do I need to copy this to system/etc/init.d since this is a init.d supported kernel? What is the best root app to move this file there and set the correct permissions?

Thanks.
[T-Mobile, Samsung Galaxy SIII] Markdental:
Install busybox in bin as well, just in case. Nandroid, wipe dalvik and cache, flash kernel. Run script (follow directions from his post) for CPU sleep, reboot, you don't need to do anything else.
[T-Mobile, Samsung Galaxy SIII] zonly1:
Yes on the kernel. As far as the script, I did it the script manager way since the OP said it was preferred, but it looks like you could go either way. :) I used ROM Toolbox to move the file, but there are a ton out there like root explorer, etc.
[T-Mobile, Samsung Galaxy SIII] Imurdaddytoo:
Anyone have any luck installing this on sprint...

Just kept getting force closes when i tried
[T-Mobile, Samsung Galaxy SIII] blacksheep242:
It's me again! So, after installing this kernal with my stock installation I was not getting better quadrant scores. In fact, they actually dropped!

So I've installed the redrum rom along with this kernel and of course setcup. Now getting worst performance of all! Quadrant in the 4300 range!! restored my backup (stock) and now back in to the 5000 range.

So it is confirmed, at least for me, this kernal either does nothing (in any frequency above stock in setcpu) or worsens my scores.

Again though, this beast flies regardless so I'm happy. Someday I will get my beast to o/c hopefully
[T-Mobile, Samsung Galaxy SIII] MacTheRipperr:
Install busy box on xbin not bin. But doin both can't hurt
[T-Mobile, Samsung Galaxy SIII] carrrnuttt:
The processor is sensitive to being hot/overworked. You need to let it settle first, before running tests.

I got a 5300+ Quadrant score when I first installed this kernel, but noticed that it started getting lower and lower. I left the phone alone for a bit and let it cool down, and got a 5100+. I left it alone overnight, and got 5600+.

Now that I've set my phone's CPU profile to drop to a max of 810MHz when the screen is sleeping, I hit my high Quadrant scores practically every time I wake the phone up, since it will usually be even more nice and rested after each sleep session.
[T-Mobile, Samsung Galaxy SIII] blacksheep242:
Interesting tip, thanks. Might try that one and report back. Thank again!
[T-Mobile, Samsung Galaxy SIII] blacksheep242:
yet another interesting tip. May try this one as well... thanks
[T-Mobile, Samsung Galaxy SIII] Romanbb:
Some tips, since we're sharing:

Busy box installation only needed in xbin. Most kernels (like this one) call it to run init.d scripts on boot directly from there. Putting it in both places just doesn't make sense :D

You can disable the thermal daemon that will clock your phone down once it hits X temp. "adb shell stop thermald" will stop it. I recommend a reboot after you're done feeling good about benchmark scores so it will start back up.
[T-Mobile, Samsung Galaxy SIII] TheJesus:
Any chance to get a port for AT&T and Sprint or should it work as-is?

Good work!
[T-Mobile, Samsung Galaxy SIII] immunityx:
Im using whitehawkx deox and rooted rom and if i want to use the the cpu1 sleep stript with this kernal, i just need to dump the script in the /system/etc/init.d folder and reboot? or am im missing something ? busybox is installed in system/xbin
[T-Mobile, Samsung Galaxy SIII] es7241:
It should work, just make sure permissions are set.
[T-Mobile, Samsung Galaxy SIII] saywhat4118:
This!!
[T-Mobile, Samsung Galaxy SIII] Romanbb:
I tried compiling a version for the AT&T version but my tests said they kept getting those FCs. I'm completely lost as to why it's not working for them
[T-Mobile, Samsung Galaxy SIII] skyhigh2004:
I'm not one to care to much for benchmarks but this java score is pimp. This is a great start roman can't wait to see where this goes. :D

Edit: a little better run after I let it cool down.

Sent from one of my Galaxies
[T-Mobile, Samsung Galaxy SIII] blacksheep242:
And I'm back! Soo, back on stock, I ran some quadrants and getting in the high 4900s to low 5000s range.

I decided to flash this kernal once again per the instructions in the OP. Setcpu set at 384/1512 (set to stay after boot) and let the phone settle (following a tip from carrrnuttt) for 15 minutes.

Rebooted. I let the phone settle for 10 more min. Then ran Quadrant 2x (at stock speed): 5283! Impressive. Getting over 200 points HIGHER with this kernel at STOCK (1.5ghz) speeds. Interesting... Moving on.

rebooted and let the phone sit for 5 more minutes.

Put SetCPU to 1728Mhz and ran quadrant 2x: 5143 highest. Hmm.

Rebooted and let phone sit again for 15 minutes at 1728Mhz....

Ran quadrant 3x in a row:

1st run: 5420 nice!

2nd run: 5238 very good

3rd run: 4300 What?

Let phone sit again for 10 more minutes (still at 1728Mhz):

Ran quadrant 3x in a row:

1st run: 5087

2nd run: 4783

3rd run: 4588

Ok, so this kernal works wonderfully!! My phone, on the other hand, seems to be getting to the "too hot" limit and slows itself down rather quickly. I've considered using the command to disable the thermal limiter, but I figure if this beast won't consistently run those super nice numbers due to heat...prolly better I stay at stock.

You've all been a great help with all your tips/tricks. Thanks so much!!!
[T-Mobile, Samsung Galaxy SIII] benefit14snake:
Have we found out if we can manipulate it? Maybe still use the thermal control but push the temps up a bit?
[T-Mobile, Samsung Galaxy SIII] stuff:
Dang that is odd and unfortunate. I don't see how it could be so much different
[T-Mobile, Samsung Galaxy SIII] Abhi97:
Sweet!

I Flashed it on stock and I got a blazing 5802!
[T-Mobile, Samsung Galaxy SIII] jr71x:
Can I has this kernel too? Lol... Great work on this, Roman...
[T-Mobile, Samsung Galaxy SIII] Advantageous:
I'm not sure what happened but when I flashed 003 from 002 my phone got a lot slower and dropped about 1000 points in quadrant. Should I flash from the stock rom?
[T-Mobile, Samsung Galaxy SIII] benefit14snake:
Did you wipe? I would wipe cache and dalvik cache and re flash. 03 works way better than 02 for me.
[T-Mobile, Samsung Galaxy SIII] MacTheRipperr:
You guys seriously need to drop the quadrant scores crap. It means nothing. Quadrant scores don't mean ****. They don't represent practical uses. But he already noted what you needed to do to get your rocks off for score sake. Go ahead and flash the thing that disables thermald

Sent from my SGH-T999
[T-Mobile, Samsung Galaxy SIII] Markdental:
agree about the overuse of benchmarks. I don't know how I feel about overclocking AND removing the heat protection of the CPU. I think you are asking for trouble long term. My $.02
[T-Mobile, Samsung Galaxy SIII] sswb27:
Having a bad day or what, no sense in getting pissed off about what other people are talking about.
[T-Mobile, Samsung Galaxy SIII] kobos311:
If you are willing to request things for ATT, you gotta be willing to work too! lol, anyway ive sent roman a message, and im downloading the kernel currently to see what I can do. I know a few of the issues after working with redruM on figuring out those differences so we could make a compatibility zip possibly? just throwing around ideas..ill check into it.. NO PROMISES SO PLEASE DONT START HOUNDING ME FFS...I've been known to knife people in the back of the face, yes, the back of it. I'm that good. Lol
[T-Mobile, Samsung Galaxy SIII] Romanbb:
If someone wants to do some experimentation on their AT&T SGS3 for me, the following would be helpful:

Split my boot.img and the stock insecure boot.img. Try using it's ramdisk and my zImage, and vice versa. See if you get FCs
[T-Mobile, Samsung Galaxy SIII] Advantageous:
Lol someones getting hostile. Go to sleep brotha! Its been a long day :]

I just used the quadrant as a reference point for myself. The phone was running slower, even though i wiped both caches. I am going to keep the kernel at 002 for a little while.

Nevertheless, its an amazing kernel. Just because im having problems doesnt mean everyone is. SO many variables :good:

Thanks again Roman
[T-Mobile, Samsung Galaxy SIII] kobos311:
Hey I think Ill have a ATT version of my own kernel Im stuck here fixing some idiot 18 yr olds comp for now. he's trying to tell me what to do to fix it I told him to STFU you broke it, now go away so i can Fix it. Umm, Roman: send me a dropbox on twitter or something:

Theres alot of differences from:

case "$target" in

"msm7627_ffa" | "msm7627_surf" | "msm7627a" | "msm7627_6x")

echo 25000 > /sys/devices/system/cpu/cpufreq/ondemand/sampling_rate

;;

esac

case "$target" in

"qsd8250_surf" | "qsd8250_ffa" | "qsd8650a_st1x")

echo 50000 > /sys/devices/system/cpu/cpufreq/ondemand/sampling_rate

and wouldn't your post setup be blah blah blah

you'd have to have a

case "$target" in

"msm8660")

start thermald

;;

esac

therm or am I just completely looking at this wrong? did you happen to do something dealing with jelly bean or something or another? Cause Errr, it just seems off... :/ at least to me.. just asking get at me on twitter

I gotta get back to work so i can get home and play with my galaxy. lol
[T-Mobile, Samsung Galaxy SIII] sam_1421:
Im pretty new to this, and I'M kind of lost in it... first, what is a nandroid backup, and how can i do that?

Also, how can I wipe cache and delvik? Finally, with which utility do i flash the kernel, with odin?

If you know one good tutorial for that I would appreciate if you could share it with those who, like me, are pretty lost in the process!
[T-Mobile, Samsung Galaxy SIII] drawde40599:
No disrespect to u ( and ur probably gunna yell at me, but I won't care/ reply; ) ) but without knowing all the basics ( everything u asked how to do, u should not be flashing anything on a 600$ phone .... your questions have been asked and answered 100000000 x on xda try searching a lil .....
[T-Mobile, Samsung Galaxy SIII] benefit14snake:
Nandroid backup is done from within clockwork mod recovery. It creates a safety net by backing up your system files so if things go wrong you can restore it.

Both caches are wiped in clockwork mod recovery (CWM)

Kernels are also flashed in cwm.
[T-Mobile, Samsung Galaxy SIII] benefit14snake:
Here is a tutorial. Mods take this down if it's against the rules....

http://androidforums.com/android-lounge/485535-video-tutorial-how-flash-rom-using-cwm.html

Next time use Google as it tends to irritate the tenured people here. (for good reason... Repetition sucks lol)
[T-Mobile, Samsung Galaxy SIII] jdlorinser:
Anyone here on 003 that hasn't overclocked. How's battery life been compared to stock kernel?
[T-Mobile, Samsung Galaxy SIII] es7241:
Your on the SGH-T999V which is a different phone, than the SGH-T999 that this is for , I'm assuming your phone is Canadian? So I'm not sure if it will work properly..

You might want to read up on that before flashing anything here.
[T-Mobile, Samsung Galaxy SIII] carrrnuttt:
Although I have/am overclocked, battery life has actually been better for me, since this kernel allows me to severely underclock when my screen is off. The stock kernel, even if you're rooted running SetCPU or something similar, won't allow profiles to stick.
[T-Mobile, Samsung Galaxy SIII] notxel21:
I'm trying to underclock to 1.6 but it reverts to 1.8 and won't stick.. anyone else noticing this? :confused:
[T-Mobile, Samsung Galaxy SIII] cwalker0906:
is anyone using system tuner with this? does it work?
[T-Mobile, Samsung Galaxy SIII] Chilled26:
Yea I noticed that it won't stick to anything under 1.8.
[T-Mobile, Samsung Galaxy SIII] afbengochea:
No problems here at 1.5. Using set cpu on protekk debloated Rom
[T-Mobile, Samsung Galaxy SIII] Romanbb:
try changing the /system/etc/init.qcom.post_boot.sh file and setting the clock in there for whatever you want to clock to (and don't use SetCPU to set anything). It should be the last two lines you need to change
[T-Mobile, Samsung Galaxy SIII] cwalker0906:
I have used both setcpu and system tuner and settings do stick... have to use on boot completed.... Roman great job... been enjoying your work since the vibrant... can't wait for aokp.... Thank you
[T-Mobile, Samsung Galaxy SIII] TheJesus:
Well Samsung released Sprint's open source today if that would help on that side.
[T-Mobile, Samsung Galaxy SIII] swa2k4:
been using it on 1.89 for some bouts of wifi time and it stays relatively cool. but when I take it out and use HSPA+ boy gets so hot! lol gonna stick with 1.5ghz, I am also having issues with SetCPU sticking the set on boot frequency to 1.5ghz keeps wanting to go up to 1.89 ...busybox on xbin and everything, havent tried systemtuner but must I?
[T-Mobile, Samsung Galaxy SIII] sam_1421:
Yeah that's the only thing that bugs me right now, I know the T-mobile root worked like a charm on it... does it mean it should be good or it doesn't mean anything?
[T-Mobile, Samsung Galaxy SIII] carrrnuttt:
I had issues with SetCPU, but everything seems to be settling down using ROM Toolbox. Both pro versions.
[T-Mobile, Samsung Galaxy SIII] kobos311:
haha, I think i missed the word ' simple ' in your original post. I'm used to all the complex editions and long tedious processes to compile one haha, anyway, glad everyone is enjoying it, Im guessing you're AOSP/AOKP base could be the force close issues, but thank you for this! it's a great start for all of our US users.
[T-Mobile, Samsung Galaxy SIII] lferrin:
Can confirm set cpu wouldn't stay set. Installed Rom toolbox pro and has worked ever since. Been using cpu spy to confirm this.
[T-Mobile, Samsung Galaxy SIII] swa2k4:
Still no luck for me using Rom toolbox pro either. Keeps on booting to 1.89ghz probably something to do with using free gs3 Rom 1.5. May just go back to a stock Rom? Any suggestions
[T-Mobile, Samsung Galaxy SIII] PanamaPaul:
Me as well....

Just cant get the settings to stick at 1512 no matter whether I am using Rom Toolbox or SetCPU.

I can set the settings to "set on boot" in both and set max to 1512 with ondemand gov and still after I reboot it is sitting at a max of 1890...

Any ideas guys?

I am using stock Rom....

Can everyone else confirm they are getting this setting to stick after a reboot?

TIA....
[T-Mobile, Samsung Galaxy SIII] murdermonkey9000:
Tried several different apps as well and it won't stick on reboot, won't stick period for long.
[T-Mobile, Samsung Galaxy SIII] skyhigh2004:
Yeah that is kinda weird. No matter where i have it set for a high frequency I always get 20-40 sec of 1890mhz at boot up.

Sent from one of my Galaxies
[T-Mobile, Samsung Galaxy SIII] Lakeshow423:
It's letting you know it there when you wanna push it :cyclops::good:
[T-Mobile, Samsung Galaxy SIII] cwalker0906:
that because most appropriate set at boot meaning after boot... during boot it runs at max
[T-Mobile, Samsung Galaxy SIII] MacTheRipperr:
Mine works just fine with set cpu

Sent from my SGH-T999
[T-Mobile, Samsung Galaxy SIII] techrider77:
I don't seem to have any troubles with this kernel and I am running SetCPU, it hits 1890 when it needs to but likes 1134-1512 mostly. All in all it runs very smooth and battery life is great, especially once appropriate profiles are setup.

For those having issues getting alternate speeds set, make sure your BusyBox install is in /system/xbin like mentioned earlier.

Not sure on this one...but someone mentioned trying this on a stock ROM, stock ROM's don't have init.d support and this kernel needs it to work properly with the UV/OC settings maybe? :confused:

Also for those having issues with with trying to run at less than 1890 max, do you have any profiles setup that may be over-ruling the min/max settings?
[T-Mobile, Samsung Galaxy SIII] sic3230:
Flashed this kernel earlier today, and my phone has lost all haptic feedback/vibration. Strange, huh? Anyone else experience this or know what would cause this? Going to Nandroid back to stock and flash again and see what happens.

edit: Restore worked.
[T-Mobile, Samsung Galaxy SIII] notxel21:
Could someone please tell me what could be causing this wakelock? :confused:

Running version 003 of this kernel.

Freegs3 1.5 Rom. Thanks! :)
[T-Mobile, Samsung Galaxy SIII] skyhigh2004:
Why does this kernel boot higher than stock? Just curious as almost every kernel I have ever ran boots up at stock speed to reduce the amount of people who have issues booting at a higher frequency. My phone handles 1.89 fine its just not needed if you ask me lol. Anything above 1728 doesn't seem to make much of a difference performance wise that I can tell both in real world usage and benchmarks and turns this phones heater on. Either way it gives me great battery life.

Sent from one of my Galaxies
[T-Mobile, Samsung Galaxy SIII] cwalker0906:
that just the frequency roman set as normal operation. its a oc kernal so to have it boot at factory stock you have to underclock it
[T-Mobile, Samsung Galaxy SIII] skyhigh2004:
I know what an OC kernel is but this is the only one other then some pre release stuff I tested for morfic back in December that boots up OC'd. The funny thing is it only jumps to that high frequency just at boot up and goes right back down for operation. Its not a problem just an observation.

Sent from one of my Galaxies
[T-Mobile, Samsung Galaxy SIII] jwwolfe77:
I don't know **** about kernals except how to flash them. Lol. That being said.... will this work for a sprint ssgs3?
[T-Mobile, Samsung Galaxy SIII] sswb27:
Sorry man t-mobile only.
[T-Mobile, Samsung Galaxy SIII] uoY_redruM:
Morfic is the ****! I hope he eventually gets a S3 as well and starts doing kernels here. I swore by his kernels while I had my GNexus.
[T-Mobile, Samsung Galaxy SIII] ViralCipher:
Hey, all. I am sure this isn't an issue with the kernel or eugene's CPU sleeper script, but ever since I flashed this kernel and used the CPU sleeper script the battery seems to drain much more quickly with the phone screen on even if I am just sitting on the home screen not doing anything and even at stock frequency 1512mhz. The battery seems to go down 1% every 1.5-2mins or so (not sure if this is normal). The CPU Sleep app works great when the screen is off saving battery life though.

I decided to see if nandroiding back to before I flashed the kernel and just using the CPU sleep app on stock kernel would work, but I am still seeing the same battery drain. I decided to use neither the CPU Script app nor the kernel, but I am still seeing the battery drain. I even tried a factory reset and a battery calibration to no effect. I am using redrum's lean stock ROM release 3 which didn't have this issue before. Does anyone know what could be the cause of this battery drain that I never had before and what could be a solution? Should I format system and then nandroid back to stock? Thanks! Note: I have installed busybox on system/xbin and system/bin
[T-Mobile, Samsung Galaxy SIII] orthopak:
I am having the same problem. I had great battery life with Redrum lean stock and ever since FreeGS3 v1.5 w/ adama and cpu sleeper my battery life hasn't been great. In 4 hours of cell standby I lost 30% with 2 minutes of screen time. I was told it might be the CPU sleeper so I'll disable that and try again tonight with just the rom and adama kernel. Any suggestions would be great!
[T-Mobile, Samsung Galaxy SIII] Armani G:
Will this work with the AT&T version?
[T-Mobile, Samsung Galaxy SIII] sswb27:
This it tmobile only, but roman is working on getting a kernel for at&t.
[T-Mobile, Samsung Galaxy SIII] ViralCipher:
Thanks, I would like some suggestions as well. I originally just used redrum's rom with the stock kernel and battery life was fine. I did a nandroid backup then flashed this kernel and right after that I applied the CPU sleeper script using Script Manager method. I did get a significant increase in overall battery life when the screen is off, but it started to drain quickly with the screen on. I removed the script then used the App version, same thing happened. I did as you said and removed the CPU sleep mod and just used the kernel and ROM, but that didn't seem to fix the issue either. I am now just using the ROM without the kernel and without the CPU sleep like I had originally and it is still doing it. Its strange.
[T-Mobile, Samsung Galaxy SIII] moonfire711:
Looks like a new CPU sleeper app is coming today. Should resolve some of your problems according to the changelog preview.

http://xdaforums.com/showthread.php?p=28466880#post28466880
[T-Mobile, Samsung Galaxy SIII] murdermonkey9000:
Turn on the thing in developer options that shows active cpu processes, see if gsiff_daemon is running like crazy.
[T-Mobile, Samsung Galaxy SIII] eddylee09:
Pardon the silly question but, what exactly does this kernel do?
[T-Mobile, Samsung Galaxy SIII] moonfire711:
Silly rabbit, tricks are for kids. Read the OP.
[T-Mobile, Samsung Galaxy SIII] eddylee09:
But tricks are so good...

No, I did but I still don't really understand the benefits of it. I guess a more simpler or "Explain Like Im 5" description if you mind helping me out. Just switched over to android/GS3 and trying to learn as much as I can.

Thanks!
[T-Mobile, Samsung Galaxy SIII] cwalker0906:
Google what kernels. are and it will probably help you understand. a little more
[T-Mobile, Samsung Galaxy SIII] Serious_Beans:
Well the kernel is overclocked so your processor can run at faster speeds but you are sacrificing battery life and the phone will get hotter. Roman also decreased the voltages which saves some but not very noticeable battery. Right now this to me this is just a test kernel and proof of concept in a sense. The kernels for this phone will get crazy and your battery life and speed will only get better as more devs get GS3s and they start working on kernels. Also some roms will come with custom kernels. I'm sure when roman releases AOKP he will also release a custom kernel with it.
[T-Mobile, Samsung Galaxy SIII] moonfire711:
Yeah, I used this Kernel for testing and playing a bit, but went back to the stock kernel as I wasn't seeing enough benefit in real life application to warrant the extra (however small) battery drain and wear and tear on my CPU. As long as you have a nandroid backup from before you flash this kernel, you can use clockworks recovery to do an advanced restore of the boot.img only to restore your stock kernel without clearing your whole rom or raising your flash counter.
[T-Mobile, Samsung Galaxy SIII] Serious_Beans:
I raised my flash counter already :/ does T-Mobile check that stuff? Lol
[T-Mobile, Samsung Galaxy SIII] moonfire711:
I don't know. They could I guess. Hope someone figures out how to reset that some day.
[T-Mobile, Samsung Galaxy SIII] sam_1421:
After 3 days of testing I can confirm that this kernel works flawlessly on my SGH-T999V! Thank man, good work!
[T-Mobile, Samsung Galaxy SIII] KingOfThaJungle:
This looks pretty sick, anyway you could make a Sprint version?