yashsingh1/xdaforums huggingface dataset:
[T-Mobile, Samsung Galaxy SIII] mikoal:
Thanks for your reply. I'm running 4.1.1 with the kernel I listed above.

1) Would I have any troubles swapping back and forth and to other new kernels?

2) Can you go into a bit more detail or refer me to a link about reflashing roms with correct modules and comparing the directory with Rom zip file?

3)Reflashing roms:

So I'm guess reloading a nandroid wont work and I need to flash a rom with the older drivers (or correct modules)? Where would I find these correct modules?

4) Comparing directory and rom zip

Where in the ROM zip do I compare? and what im I looking for?

Do they have to match? what if they dont?

Thanks!
[T-Mobile, Samsung Galaxy SIII] LuigiBull23:
can't promise anything but you're less likely to face issues so long as you follow proper instructions. Like I said, you don't have to worry unless the kernel is outdated in some shape or form towards the ROM you're flashing or vice versa,. The worst that can happen is it just wouldn't fully boot. The easiest way to avoid conflicts is to acknowledge the ROM's default kernel information under settings > About Phone and match up a similar build to that. Refer to this to gain a better understanding on modules.
[T-Mobile, Samsung Galaxy SIII] KunoMochi:
Thanks for that. :) As castle_bravo noted, though, the main reason I undervolt is because of heat issues. When running at default on KT747, it would get my phone's bottom screen so hot that it almost felt like it would burn my fingers sometimes (CPU running ~53-55C). Undervolting it kept it at a cooler ~51C. Granted, it is also the combination of using the temperature throttling and switching to another governor.

The offset is finding the right amount without having the phone auto-reset, pixel artifacts appearing, and drag the CPU down when it doesn't get quite enough voltage to do some processes. I still some draw glitches now and then, but I'm thinking that might be due to something else besides the voltage tweak.

Whether or not it gives better battery life, I haven't seen much of a difference yet.
[T-Mobile, Samsung Galaxy SIII] krntehknik303:
Can some explain to me what the very first one means? Com.Google.android.gsf
[T-Mobile, Samsung Galaxy SIII] LuigiBull23:
I believe that relates to your Google calendar and apps syncing with it using the accounts stored on your phone.
[T-Mobile, Samsung Galaxy SIII] Aerowinder:
Just to add, it is Google Services Framework.
[T-Mobile, Samsung Galaxy SIII] LuigiBull23:
Yes. Thank you kind sir. just wanted to provide a more elaborate response to that.
[T-Mobile, Samsung Galaxy SIII] krntehknik303:
Why does it activate when I don't have anything snycing or have the data connection on? I'm a little confused..
[T-Mobile, Samsung Galaxy SIII] LuigiBull23:
So you may think.. Google services includes various services such as

Google Services Framework

Google Play Services

Google Account Manager

Google Contacts Sync

Google Bookmarks Sync

Network Location
[T-Mobile, Samsung Galaxy SIII] krntehknik303:
Alright, so I disabled the sync for google calender and the google services framework. I've only disabled stuff for like "After Start-Up"

Will this be safe or make my phone buggy?
[T-Mobile, Samsung Galaxy SIII] LuigiBull23:
Don't disable Google Services framework. It allows the phone to connect to google for all intents and purposes, including upgrading firmware or accepting updates through the Play Store. You are likely to encounter FC as well. Just leave that alone. Disabling calendar sync is completely fine though.
[T-Mobile, Samsung Galaxy SIII] jdidtht:
Why is this thread in original development for? Cant the end user just get these builds from the source creator? I just don't understand why its here and not in general

Absolutely Infected SGH-T999
[T-Mobile, Samsung Galaxy SIII] LuigiBull23:
Let me start by saying you are not wrong bro.. This could have definitely been placed under General or even Android Dev. I completely understand where you're coming from but the OP speaks for itself in terms of the thread's purpose. The point here is this thread was intended to help both the developer and users alike in simplifying things. In addition, these builds have not been modified in any way. They are OFFICIAL, which I'm sure you're aware of as everyone else should be, and although I can be wrong it was for these reasons why I felt this thread should be placed under the OG Development forum, to work side by side with the original thread.

EDIT: Thread has now been moved to Android Dev :)
[T-Mobile, Samsung Galaxy SIII] jdidtht:
Well that's cool but your not developing anything therefore it should be in general discussion

Absolutely Infected SGH-T999
[T-Mobile, Samsung Galaxy SIII] LuigiBull23:
Taken care of now bro
[T-Mobile, Samsung Galaxy SIII] Aerowinder:
Actually, it should be in Q&A. Because it's a huge Q&A thread. A huge Q&A thread with mirrors. However, I don't care enough about it's placement to request a move. It just doesn't matter that much. Kind of made sense to have them together.
[T-Mobile, Samsung Galaxy SIII] hectormcesar:
Hello people. Some one suggested this Kernel for Stock TW JB 4.1.1 ...I heard gives a great battery life to the GS3 my question is can I flash this kernel on my i747M which was bought on Mexico using a Telcel mexican phone company???

Thanks in advance!! Cheers!!
[T-Mobile, Samsung Galaxy SIII] LuigiBull23:
Yes you can. Post #2 is the one for you :)
[T-Mobile, Samsung Galaxy SIII] LuigiBull23:
OP Updated!

Here's a small AOSP (3.4) update for you guys courtesy of [MENTION=4325945]ktoonsez[/MENTION]. ENJOY!!
[T-Mobile, Samsung Galaxy SIII] shenry1307:
Yeah, I know... But I'm @ work and they block mediafire! :mad: I'll get it at home... I don't like flashing while "on the road". ;)
[T-Mobile, Samsung Galaxy SIII] LuigiBull23:
Check out the links. The mirrors I provide are from Dropbox lol. Unless they block that too you're free to download it here
[T-Mobile, Samsung Galaxy SIII] shenry1307:
Ironically, Dropbox and GDrive are allowed... Go figure! It's because the "C " class made a big stink after they were blocked! Lol! :laugh:

EDIT: To which links are you referring?
[T-Mobile, Samsung Galaxy SIII] LuigiBull23:
Every single one in the OP? lol Though you're gonna wanna look at post #2.
[T-Mobile, Samsung Galaxy SIII] shenry1307:
Oh yeah... I knew that... DUH moment! :eek:

Thanks, bud!
[T-Mobile, Samsung Galaxy SIII] clothednblack:
Thanks for making this thread
[T-Mobile, Samsung Galaxy SIII] hectormcesar:
Thanks and I'm guessing the KT747-Kernel-TW-JB-ATT-12-11-2012.zip is 4.1.1 ?? and/or if I flash 4.1.2 on TW JB 4.1.1 will brick the phone??
[T-Mobile, Samsung Galaxy SIII] LuigiBull23:
That is correct and no, flashing a 4.1.2 version over 4.1.1 won't brick your phone. They are compatible with eachother. If you choose to flash a 4.1.2 build then I recommend starting with the most recent one (5/31) and see how that works out for you. If you experience any issues on that build then you may work your way down or simply revert to one of the 4.1.1 versions.
[T-Mobile, Samsung Galaxy SIII] shenry1307:
Just to clarify, is [MENTION=4545247]hectormcesar[/MENTION] asking if it's ok to flash a version 4.1.2 kernel while using a 4.1.1 rom... Or does he want to upgrade

both

to 4.1.2?
[T-Mobile, Samsung Galaxy SIII] LuigiBull23:
He's currently running a stock 4.1.1 ROM and was curious as to whether or not he can flash a 4.1.2 version over that without bricking his phone. They are indeed compatible with eachother.

EDIT: Don't ask me why he doesn't just upgrade his ROM lol. I have no idea why but there must be a reason why he chose to stick with 4.1.1
[T-Mobile, Samsung Galaxy SIII] shenry1307:
Lol! Right? "Luke, come to the Smooth side!" :D I know when I first got my S3, most other carriers pushed 4.1.2 to customers, 2 months later, except TMO... I rooted just to get off of 4.1.1, but was glad I could go above and beyond with 4.2.2. :cool:
[T-Mobile, Samsung Galaxy SIII] hectormcesar:
hehehe yeah I know right!!

I didn't really want to go into details of why I'm still sticking with TW 4.1.1 But honestly the GS3 works just fine with TW. Of course i like pure android over all those branded skins. But having the experience of a preview device "LG O2X" replacing lg's for cm's, and even though I was running CM 10.1 when the LG only released 4.0.4 the device had many issues such as bad radio quality. So now that my GS3 is running smoothly with TW (i know i know) and don't have now much time to flash rom and kernels (cause as you guys know once you start with one you just keep flashing and flashing!!)... But I'm sure one day I will replace the rom and move to the "dark side" ...again.
[T-Mobile, Samsung Galaxy SIII] shenry1307:
Ain't that the truth!! :cyclops: Well, when you're ready to return home, my Prodigal Son, we will be here with open arms, cooking the fatted ROM! :D
[T-Mobile, Samsung Galaxy SIII] yanikd:
I'm a bit in the same boat. I need to recover, I've been flashing pretty much every CM nightly since the beginning, I think it was in august or september. I spend way too much time looking at changelog and whatnot.

That being said, I feel like a noob in TW, how does the Power Saving mode affect this kernel? I usually just use settings like in the OP with a few variants, but I'm wondering how does that play with TW Power saving mode.

Thanks.
[T-Mobile, Samsung Galaxy SIII] shenry1307:
No idea there, buddy... I'm not a TW fan. But stick around... Someone will assist you! :)
[T-Mobile, Samsung Galaxy SIII] Aerowinder:
Careful with this kernel on TW. Was too unstable to use for me.
[T-Mobile, Samsung Galaxy SIII] shenry1307:
Not me, [MENTION=4788211]Aerowinder[/MENTION]... I'm straight AOSP... Don't really like TW personally. :cowboy:
[T-Mobile, Samsung Galaxy SIII] krntehknik303:
Looks like boost cpu and battery control is not in the TW version 5/31... I was following your settings.. its okay if I don't have those two minor things, correct? Just trying to figure out what works for me... so far nothing seems to work in my favor, so I thought I try out these settings.
[T-Mobile, Samsung Galaxy SIII] LuigiBull23:
Haven't been on TW for quite a while now but if memory serves me right I don't believe enabling power saving mode overrides your kernel tunings. It will only affect that of the screen and background colors.

My settings are AOSP specific so yes, it is ok to skip anything not included in TW versions. For boost_cpu, you're gonna want to use the touch boosters instead and battery control settings are located in "Governor Adjustments". So you may wanna check there.
[T-Mobile, Samsung Galaxy SIII] prboy1969:
Correct :)

TEAM MiK

MikROMs Since 3/13/11

---------- Post added at 05:35 AM ---------- Previous post was at 05:29 AM ----------

How so ? I run TW daily. UV'd 50 -75 across the board. Also OC'd . I'm curious as to what kind of issues you ran into ?

TEAM MiK

MikROMs Since 3/13/11
[T-Mobile, Samsung Galaxy SIII] Aerowinder:
Reboots and bad stutters (default settings). It's my favorite AOSP kernel, but not playing nice on TW for me.
[T-Mobile, Samsung Galaxy SIII] LuigiBull23:
OP updated!

All posts updated to latest 3.4 builds!!
[T-Mobile, Samsung Galaxy SIII] Danvdh:
This kernel run's very well on TW if you're phone can handle it. KT's TW kernel is incredible work but some phones perform awful or refuse to boot.
[T-Mobile, Samsung Galaxy SIII] Perseus:
You do know right that even though same model, each phone is

Pretty much unique right?

What works for one may not work for other.

For example I have unstable issues with current ROM version and this kernel at -50 undervolting. No one can reproduce it. I am not worried ask know the above

Please hit thanks if you find this useful.
[T-Mobile, Samsung Galaxy SIII] tiger013:
After jumping from several threads to find the tw kernel I'm a little lost. Is 5-13-2013 the current tw build?
[T-Mobile, Samsung Galaxy SIII] tiger013:
Wow, that was a fast response. Thank you. I'm going back to tw to see if I can get Carrier billing to work for Verizon. I'm going to miss aokp
[T-Mobile, Samsung Galaxy SIII] Perseus:
Mind telling what issues you have with AOKP ?
[T-Mobile, Samsung Galaxy SIII] tiger013:
Very weak signal/wifi and carrier billing in the market wouldnt work. Tried different kernels everything. wierd being on tw again but nice to have carrier billing again
[T-Mobile, Samsung Galaxy SIII] Perseus:
What modem do you have"?

If Carrier Billing is vital to you then you are better off with stock as it will never work on aokp.

Please hit thanks if you find this useful.
[T-Mobile, Samsung Galaxy SIII] Indian9990:
Hi guys,

Total newb question but I did try searching the thread.

I'm running Illusion 2.1 and it's great but I heard this kernel helps with battery life and has rather good performance for it.

Am I using the right link?

https://www.dropbox.com/sh/ivwuxkhrc45ddqt/UTGAT_Rfip

It's the ASOP 3.4 version. They all say AT&T on it though so I wasn't sure.

I also tried flashing it the other day and I just got a black screen. It wouldn't start up for me which is why I'm asking and double checking that I had the right version.

Thanks,

Indian :)
[T-Mobile, Samsung Galaxy SIII] Perseus:
I believe you are using the Correct version. I assume your Illusion is on JB 4.2 Don't worry about ATT. When you say won't start, do you mean Bootloop ?
[T-Mobile, Samsung Galaxy SIII] Indian9990:
Yeah but I downloaded the ASOP kernel is that the wrong one? When I meant won't start I mean that I get a blank black screen.

My steps when I install is..flash kernel..wipe cache.

Sent from my Samsung Galaxy S III
[T-Mobile, Samsung Galaxy SIII] Perseus:
Yes that's the right version for you. Given that's not a TW rom. I'd want to do Clean Dalvik & Cache before and after flash.

Does the blank screen appear before or after Illusion Boot Animation ?
[T-Mobile, Samsung Galaxy SIII] Indian9990:
I see "Samsung galaxy S IIII" then it just goes black. The menu and the back arrow light up for a bit but that's about it. Its not a TW ROM.

I don't even get the illusion boot logo.

Sent from my Samsung Galaxy S III
[T-Mobile, Samsung Galaxy SIII] Perseus:
Then that means its a bad flash. I'd do a ultra clean flash of everything.
[T-Mobile, Samsung Galaxy SIII] Indian9990:
I've experienced it three times already though. Define this "ultra clean"?

Sent from my Samsung Galaxy S III
[T-Mobile, Samsung Galaxy SIII] Tunasty:
What a great thread! Thanks for this bro, definitely bookmarked! :highfive:
[T-Mobile, Samsung Galaxy SIII] Perseus:
1. Backup any needed Non-App Data from Internal SD.

2. Do a TiBU.

3. Go to recovery.

4. Factory Reset, Format /System (Redundant but still) & /data

5. Without rebooting, flash just the rom by itself & Gapps.

6. Reboot finish initial wizard. DO Not restore or install anything. Reboot back to recovery.

7. Clear Cache & Dalvik. Flash the Kernel and then Clear Cache and Dalvik again.

8. Reboot and post results.

Do not use most recent version of the kernel. Just flash 6-8 for now. Once you find everything is fine after reboot, go ahead and flash latest version in normal manner. Sometimes Rom does not have the needed CM code but latest kernel does. So that might cause incompatibility.
[T-Mobile, Samsung Galaxy SIII] Indian9990:
Newb question..what is TiBu?

EDIT: I'm like completely retarded..I downloaded the version that was like 4 months old..not the latest version..Dropbox sorted them by oldest first rather than newest..I guess I should read more. Still trying your method and will report back though :)

Thanks for all the help!

Sent from my Samsung Galaxy S III
[T-Mobile, Samsung Galaxy SIII] Perseus:
TiBU = Titanium Backup. Not sure what you mean by second to top,you should download this version here.

Clicking the thanks button is much easier but this helps too.
[T-Mobile, Samsung Galaxy SIII] Indian9990:
I do hit the thanks button and it seems like you quoted me before my edits :)
[T-Mobile, Samsung Galaxy SIII] LuigiBull23:
That's because he was quick to respond so he got to you before the edits were made lol

I figured you downloaded an earlier build but luckily [MENTION=3639717]Perseus71[/MENTION] was here to guide you in the right direction and help you acknowledge your own mistake. Just understand that this happens to everyone at one point or another. Sometimes it has absolutely nothing to do with being a "noob". So don't ever label yourself as a "retard'' or anything of the sorts..
[T-Mobile, Samsung Galaxy SIII] Indian9990:
Oh lol. It didn't show up on my phone for a while I guess. Yeah I figured I downloaded a later build too but not all off the dropbox text shows up on my phone so it only was clear to me what happened when I went to the link on my computer :) I'm glad he was here to help though. It makes these forums 10x better :0

Okay sounds good. I won't, but sometimes I just feel dumb asking such simple questions lol.

Another question while you're around. I got the kernel installed and I'm adjusting everything to your settings but how did you get the voltage to -25. The lowest I can get is 700.

Thanks :)
[T-Mobile, Samsung Galaxy SIII] LuigiBull23:
Lol the -25mV just means I subtracted 25mV across the board and it appears you're trying to undervolt by 200!. I HIGHLY suggest you don't do that. Some phones can handle it but I still would not recommend it to anyone. You will likely suffer an incredible amount of instability as well as random reboots, especially if you use my settings. I recommend just applying my settings as they are and observe how well they run for a few hours before adjusting them to your liking.
[T-Mobile, Samsung Galaxy SIII] Perseus:
+1 to what Luigi said. Believe me, I do it all the time!

Never ever feel bad asking simple questions. People on XDA have this awful tendancy to make Acronyms on the fly. Makes it terrible to follow through for someone else. I think I have been infected with the same.

[MENTION=2557878]Indian9990[/MENTION];43870056 Actually some people do tend to undervolt by 200 mv. But I definitely do not recommend it. Your phone is not meant to do that. Do take a look at my Guide to see if it helps. Link in my signature.
[T-Mobile, Samsung Galaxy SIII] tiger013:
Carrier billing works on AOKP m2 :)
[T-Mobile, Samsung Galaxy SIII] LuigiBull23:
I used to be able to undervolt by 200 til I began noticing an increasing number of artifacts in my settings, apps, etc.. So I jumped off that bandwagon.

Those specific phones that can handle such extreme undervolting are VERY substantial. The end users have been blessed lol
[T-Mobile, Samsung Galaxy SIII] prboy1969:
+1 to what you and Perseus71 have posted. Yes it can be done. But in almost all cases, it's not a good idea. In fact too much UV ( Under Volting ) can have the reverse of the desired effect. Instead of consuming less battery, it will use more. In some cases I've actually had the device heat up because of acting erratically from being undervolted far to much. Not to mention the Random Reboots that in most cases accompany being undervolted to low.

TEAM MiK

MikROMs Since 3/13/11
[T-Mobile, Samsung Galaxy SIII] LuigiBull23:
Story of my darkest days lol. Agreed on battery life as well. Mine was just dreadful then.. but ever since I jumped off that bandwagon my phone's been incredibly stable and does what I want it to about 95% of the time. As you can clearly tell, after managing unnecessary wakelocks and such, my battery life has improved drastically. I'm prepared for my next full run and expecting nothing but better results than my last... :)
[T-Mobile, Samsung Galaxy SIII] Indian9990:
I tried your settings and I got wake locks and such. I would hit unlock and the screen was black for like 30 seconds before coming on. The menu and back button was lit though. I didn't adjust the voltages but followed your other settings this time around and things seem to be better.

I also wasn't getting notifications from google voice unless I manually refreshed the app. This morning its working fine thiughm strange.
[T-Mobile, Samsung Galaxy SIII] mw86:
Castle Bravo and I echo the same thoughts Prboy and Luigi have on this subject.

Here are two links of posted theories and explanations of why the voltage is less a factor to battery savings than a good tuned governor and scheduler with frugal use of systems of the phone that drain power fast and good control over how apps can use or effect phone.

http://xdaforums.com/showthread.php?p=42258652

Castle Bravo has a wonderful post there and I posted a bit farther down that page endorsing Castles post.

Here is another post of mine that Eddyfunkycold said was a good post too.

http://xdaforums.com/showthread.php?p=42612300
[T-Mobile, Samsung Galaxy SIII] Perseus:
http://xdaforums.com/showpost.php?p=42612300&postcount=5500

This is why I quoted Castle_Bravo in the OP of my KT747 Guide. May I Quote this post of your as well ?
[T-Mobile, Samsung Galaxy SIII] LuigiBull23:
Agreed. Can never forget Castles intake on it. I believe I had linked to it on post 81? I will always link to his as well as your post in case anyone wants a more elaborate approach on this matter. Thanks again for the links!
[T-Mobile, Samsung Galaxy SIII] mw86:
My posts are free to share for sure. It's an honor when anyone refers to our posts so I would be honored if you do place the link in your guide.

---------- Post added at 02:41 PM ---------- Previous post was at 02:41 PM ----------

You are very welcome Luigi and same above goes to you... Thank you guys kindly.
[T-Mobile, Samsung Galaxy SIII] Indian9990:
Running the settings you posted on main page now. Will let ya know how it goes.
[T-Mobile, Samsung Galaxy SIII] chazel3:
Sorry to sound like a noon, but Tmo & att download are the same, right? I'm having trouble installing this on my tmo s3. Running monocerous v0.3. Phone starts to boot, gets to s3 splash then goes black and unresponsive. Any thoughts?
[T-Mobile, Samsung Galaxy SIII] Indian9990:
Yeah make sure you grab the latest version. You should be fine as long as you grab the latest version.
[T-Mobile, Samsung Galaxy SIII] LuigiBull23:
Yes, they are compatible with eachother. Which build version did you download?
[T-Mobile, Samsung Galaxy SIII] prboy1969:
Did you follow the instructions in the OP for flashing ? Did you verify the MD5 before flashing ? Try this : wipe Cache, Wipe Dalvik, Fix Permissions, and Reboot.

TEAM MiK

MikROMs Since 3/13/11
[T-Mobile, Samsung Galaxy SIII] nxoxe:
I like keep going bro.
[T-Mobile, Samsung Galaxy SIII] t1gartist:
is yur kernel updated to run on vrbmf1 stock firmware?
[T-Mobile, Samsung Galaxy SIII] LuigiBull23:
Not my kernel but yes. It should run just fine on MF1.
[T-Mobile, Samsung Galaxy SIII] Kingr070:
Noob Need helpp

Okay excuse me for being a noob. Im new to downloading kernels and such. I have a T-999 and im running Liquid Smooth 2.8 (unsure if I wanna update to 2.9 at all)

I dont know which one I should be downloading. Would I be downloading the AOSP Linux 3.0 version? Or the 3.4 Version? Thanks in advance
[T-Mobile, Samsung Galaxy SIII] LuigiBull23:
3.4

Make sure you grab the very latest one.
[T-Mobile, Samsung Galaxy SIII] Kingr070:
Thanks a lot

Flashing it right now, Thanks a lot man will let you know how it goes.
[T-Mobile, Samsung Galaxy SIII] Kingr070:
Reverse Tilt controls?

So i successfully flashed the kernel to my phone, but now my tilt controls are reversed! Like orientation wise if I turn the screen landscape, itll go landscape but itll be upside down. I tried calibrating the screen but that didnt work either. Any ideas?

[Edit] Lol I also just lost all of my text messages out of nowhere. Not liking where this is going x_x
[T-Mobile, Samsung Galaxy SIII] LuigiBull23:
You're on the T999 but it sounds like you downloaded the kernel from the wrong post. Normally when one experiences orientation issues like that it's due to flashing another model's kernel.
[T-Mobile, Samsung Galaxy SIII] Kingr070:
Remove current Kernel?

So is there a way to remove this kernel? Or should I just flash over it to put the new one on it