yashsingh1/xdaforums huggingface dataset:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] nicksmizzle:
yep! it worked awesome, other than the fact that i have one of the devices that pegs my voltages at 1150 :p
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] InstigatorX:
Same here on the voltage. You can lower after the initial boot, though. I've put mine down to 1100.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] blackwing182:
its the same phone, just that the att phone is LTE and the T-Mobile not.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] InstigatorX:
3.0alpha2 anyone?

http://tinyw.in/Pcgv

Lots of RCU updates and a fix for CPU1 not being set to CPU0 freq and governor.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] blackwing182:
as soon i finish to download the lastest aokp nightly, ill flash this little bad boy :) thanx bro!

i got some random reboots :(. any info i could bring?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] InstigatorX:
/proc/last_kmsg would be helpful.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] nklenchik:
Latest v2, 3.0 kernel is running smoothly with my phone. Battery life had been pretty good as well.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] blackwing182:
here it is, happened again,

[ 5778.618158] Hotplug: cpu1 is down - low load

[ 5778.710757] ---[ end trace 730f499766fddceb ]---

[ 5778.716769] Kernel panic - not syncing: Fatal exception

[ 5778.821241] Rebooting in 5 seconds..

[ 5783.825025] Going down for restart now

i think is this, but at the end it says no errors detected
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] InstigatorX:
Thanks. I would recommend upgrading to latest nightly. Retention mode has been flakey and is disabled in latest builds. You alternately disable in init.com.post_boot.sh
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] blackwing182:
im in the last nightly, 10.1-2013/04/27 nightly
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] InstigatorX:
Version 3.0 posted.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] nklenchik:
Sweet, thank you. Any changes since alpha 2?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] InstigatorX:
Yes, I removed some buggy cpufreq code and sync'd up with CAF JB_2.5. Check my github for all the changes...

https://github.com/InstigatorX/SGH-Krait/commits/cm-10.1_3.4-v3.0
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] blackwing182:
loving this kernel so far!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jsyl:
Absolutely fantastic kernel, best battery life and performance I'm getting all at once out of this phone. Thank you :)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] seshaz:
Solid on chameleon os
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Sepharite:
Great battery life and performance. But I can't access the lock screen widgets without it lagging to death on my RootBox ROM.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] InstigatorX:
I take it the problem doesn't exist with the kernel that comes with RootBox? Can you provide details on version and anything else you think might help troubleshoot? I don't have rootbox installed. I run the most up-to-date CM10.1 nightly.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Sepharite:
Odd. Problem went away after a while. Now I can't recreate it. Never mind. Best kernel I've used thanks :)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] nklenchik:
Can't stress how much I love this kernel. Seriously underrated in the popularity department
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] desichiko23:
Can i use this kernel on SLIM bean ROM 4.2.2 build 5????

thanks yall
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] nklenchik:
Certainly can.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Sepharite:
I'm using one of the latest root box ROMS and I've been getting reboots at least once a day, sometimes for no reason other than waking the phone. This is the only kernel with great battery life. Any ideas what I can do? (how do I find a reboot log?)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] InstigatorX:
Check to see if there is a /proc/last_kmsg file and send that. Can you also provide specifics on the carrier (ATT, TMO, VZW, etc), the radio firmware, kernel version, any specific apps that cause the reboot (music?), etc?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] InstigatorX:
Anyone up for testing...

http://tinyw.in/rNRq

Make sure you have 3.0.1 handy just in case. :)

All the latest CM10.1 goodies are there, I updated the WiFi firmware to a later release, merged some as yet to be merged WiFi drivers from CM10.1, power management merges from CAF 3.4, 3D GPU is OC'd 450MHz, hotplug tuning, wifi wakelock tuning, scheduler updates, and the list goes on.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] dhatch93:
I'll install it now... :D

------

only thing I've noticed so far is the GPU still only shows up to 400; otherwise working very well... =)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] InstigatorX:
Where did you check to see it running at 400MHz? Just saw that I made an error. Will upload a new version. Try some benchmarks and see if you notice anything different.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] dhatch93:
I use Trickster Mod to adjust kernel settings - in the "specific" tab it shows GPU Max Frequency and it only has 128/200/300/400 so figured 450 didn't stick ;)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] InstigatorX:
Try the latest build from...

http://goo.im/devs/InstigatorX/Kernel/D2-CM10.1

I uploaded, but its still mirroring and going offline for a bit. The /sys/class/kgsl/kgsl-3d0/gpuclk show 400MHz, but max show 450MHz. It's not settable via sysfs yet, but should jump up to 450MHz under load. Still figuring the code out. ;)

Thanks for testing!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] dhatch93:
downloading 3.1a2 and will see if i notice 450...

edit- sorry, just noticed the '13682...' kernel has a newer upload time so i'll try that one.

edit #2- installed ...16214 kernel & it shows 450 as max GPU now :good:

---------- Post added at 02:10 PM ---------- Previous post was at 01:10 PM ----------

just to check - did you remove Fast Charge in the test kernel? i don't see it as an option anymore...
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] InstigatorX:
Check goo.im again. :) Added fast charge back in. Also, fixed some GPU settings.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] dhatch93:
Thanks for the update- giving the newest one a try...
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ilanderek:
Will this kernel work with pac-man rom???
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] nklenchik:
Any aosp rom that uses the 3.4 kernel, yes
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] InstigatorX:
Another 3.1 beta posted to goo.im.

http://goo.im/devs/InstigatorX/Kernel/D2-CM10.1

Look for file with latest date.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] dhatch93:
GPU to 480...hope my phone doesn't catch on fire... ;) :p :eek:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] gvsukids:
I'm using this kernel in an aokp rom and having muffled call quality; not garbled but unable to discern everything in a call and on speaker. Is that an issue with the kernel or ROM?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] CYRAXDroid:
Anything more up to date that's tw cause I'm on sr3x rom.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] InstigatorX:
Probably not. I don't run TW and can't be sure anything would work with all the newest 3.4 stuff. What is there so far should work no problems since ATT hasn't updated anything significantly.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] InstigatorX:
Version 3.1a4

Latest beta uploaded for your consumption. Would appreciate feedback on this.

1. Remove 162MHz (caused weird freq oscillations)

2. Using Showp1984s MPDecision with touchbooster

3. Disable CM's PowerHAL (so as to not interfere with #2)

4. A bunch of stuff under the hood and will post to my git shortly.

5. GPU is OC'd to 480MHz

6. Battery polling intervals increased

http://tinyw.in/AEVo
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] dhatch93:
installed...running great so far :good:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] rani9990:
Is the gpu overclock optional? It gave me severe lag when I tried it...weird right.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] InstigatorX:
Where did you get the lag? You can reduce to 400MHz or lower using Trickstermod. However, you shouldn't be getting lag.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] JJRules:
Frequencies not sticking?

Does anyone else have an issue where the CPU frequency sticks way below the max set in kernel preferences? I can usually reboot to take care of it, but it's an intermittent bug.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] dhatch93:
Only time i've seen this is when more than one app is installed that can tweak settings (SetCPU, AnTuTu, System Tuner Pro, Trickster Mod, ROM Toolbox, etc). Only use one, have it set on boot and also lock frequencies. I haven't seen it in a long time since doing this :D
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] JJRules:
Yeah, that's what I was thinking as well. Maybe I haven't removed something, I will check it again.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] InstigatorX:
What governor r u using?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] rani9990:
Candy crush saga. Lol. Not that big of a deal though.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] drivel2787:
Going to try this out. Haven't been happy with any kernels I've used so far. Will report back on findings.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] InstigatorX:
I'll give it a try and see what happens on my end. I don't play any games typically, but have Beach Buggy Blitz (I think its free). Can you try that one and let me know if there's lag there, too?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] JJRules:
Intellidemand.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] InstigatorX:
I've noticed Intellidemand does this sometimes. Not sure why (and I've looked). Interactive works best, IMO.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] drivel2787:
Anyone undervolting with this kernel? If so, what are your settings?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] InstigatorX:
Every device is different. Do all your voltages start at 1150mV? Some devices are part of a batch that is "flawed" and requires 1150mV. You can go lower, but again every device behaves differently. If you're one of those 1150 devices, you can still go pretty low (900-ish on lower freqs), but you'll get little graphics glitches and bluetooth might have some static (mine did). Start uV'ing 25 at a time and run something like Stability Test to see how it behaves.

I know it's not a simple "Here are my settings".
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] drivel2787:
1.89 is at 1325
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] JJRules:
I'll give it a shot. I have had poor battery life on other kernels with interactive.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] drivel2787:
Not too bad. Just ordered an extended battery zero lemon 7000 mah. Still plan on using this kernel though everything is stable, smooth, and great battery life so far.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] InstigatorX:
Should be better IMO. Your Android system seems high. Can u send me your BBS logs?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] InstigatorX:
Version 3.1a6

a6 uploaded. I'm liking this one a lot more. Try disabling ZRAM. I've noticed a bump in performance and battery life personally. It's under PERFORMANCE section in SETTINGS.

Build number is 1369417346 on http://goo.im/devs/InstigatorX/Kernel/D2-CM10.1
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] drivel2787:
Logs from Better Battery Stats? Do I just let it run and do a save logcat?

Also, I'm using the link off the first page which shows version 1.1 for Touchwiz. Is there a different one I should be downloading and running for touchwiz?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] nklenchik:
Which CM 10.1 rom are you on, or is it a nightly?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] InstigatorX:
I'm on the latest nightly.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ckisgen:
this one's been a winner for me all day.

nice job, man.

does this build have Francos hotplug incorporated?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] bobloadmire:
What app do we use to configure this kernel?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] InstigatorX:
In bbs there is an option to share the logs at the top. Check xda for latest versions if not. You should be using 1.1 for TW
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] InstigatorX:
Thx. I'm using showp1984s mpdecision in this build.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] InstigatorX:
I use system tuner but trickster works.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] drivel2787:
Sorry should have specified I was referring to this kernel for that version
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] gvsukids:
Page times out trying to load
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] drivel2787:
Here are the stats I got from the last 2 times I saved them.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] rani9990:
Goo's been wonky the last couple of weeks, try again.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] nklenchik:
I concur that the last build is indeed, butter. Flashed it on task's 05/21 rom yesterday, cm10.1 05/24 nightly before that
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] InstigatorX:
TW had high android system for me previously. I've never liked all the background stuff Samsung adds. Its a pain to troubleshoot.

However, it looks like you have Lattitude turned on or some other automatic checkin service. That will cause additional drain. If you want those services, then no worries. Otherwise, go into maps settings and turn off any of the extraneous location reporting options you don't want. Also see something called "Cleaner". Not sure what that is.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] drivel2787:
I froze all map related services. Only thing I do have is Google contacts and Gmail synced
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] InstigatorX:
Freezing them could be causing side effects elsewhere since a lot of apps rely upon them. I'd just disable a lot of the automatic stuff buried in the settings. Disabling wifi/mobile-based location is something to consider as well if you don't need it. I've got a crapload of wakelocks and consumption coming from that. Its under SETTINGS...LOCATION on CM10.1
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] drivel2787:
Ok I'll play around with it. I think I'm getting ready to flash a new Rom today.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] JJRules:
The latest build kernel is running great on my phone. Any thoughts of adding additional governors?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] InstigatorX:
Seems like most misbehave on multi-core devices. Interactive works best, IMO. Which one would you like to see added?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
Quite a few have been modded to hotplug just fine on multi-core devices, if you look around hard enough. :cyclops:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] InstigatorX:
Tried 'em all dude. They all act funny. Best way to explain it. The ones that support hotplug are of no interest to me given I use kernel-based hotplug.

Let me know specifically which ones u r referring to since I haven't looked hard enough. ;) I'd be willing to check it out.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
I'm just saying. I'm all about interactiveX myself. :)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] PwnCakes193:
InteractiveX is amazing. Hotplugging actually works like it should on LeanKernel
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ckisgen:
not for me, it doesn't.

both cores get stuck on for me every single time no matter what I do.

and I can't afford to restart mpdecision every 15 minutes.. it's why I haven't been able to run LK for months now..
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] InstigatorX:
InteractiveX in LK essentially has screenoff max freq support on top of stock CM10.1 Interactive. Is it the max screenoff part you guys like so much?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
You have an underlying issue somewhere. Clean install everything, and it works just fine.

Don't mind me too much InstigatorX, I run whatever I feel like running, no matter what my signature says. Usually settle for Interactive or one of its siblings/offsprings because I feel it gives decent performance for what battery it takes.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] PwnCakes193:
That's an aspect, but for some reason it runs differently than regular interactive.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] InstigatorX:
No worries. Thought I might be missing something. I always end up back on Interactive myself. I like BadAss, too, but it acts weird at time. I'm trying to keep things simple on my end. I'm going to add max screenoff stuff to hotplugging code in next release.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] InstigatorX:
Have you tried it recently? In CM10 there is a PowerHAL that works with Ondemand and Interactive to boost freq and some finetuning. Other governors don't get the benefit of this. If you're using LK, then InteractiveX replaces Interactive and gets the PowerHAL benefit. You'd have to run another kernel to compare stock Interactive to InteractiveX, though.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] pberge:
I have tried LK with a clean install using a few different ROMs and hotplugging works at first but the 2nd core will always stick on after a period of time. I know quite a few people with this same problem. There are also a few ROMs that no longer include mpdecision that will never hotplug on LK. Kernels that use the Thalamus hotplug driver have been much more reliable for me.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ckisgen:
dude. seriously. I appreciate that you think you know what you're talking about... buuut you don't :D why do you think Imoseyon added a 'restart mpdecision' sysfs to his lkconfig script several versions ago?

I'm not the only one with this issue.

and as an RD, I promise I know how to flash a kernel properly :cool:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
With all due respect, ignoring the fact you're having a blast using sarcasm, it's not because someone added a workaround that there's no issue with something you're using (probably proves the contrary actually). I'm sure there's plenty other people that have 0 issues with hotplugging, albeit that mpdecision can be finicky.

Now, if the rom or other parts of your current setup stop hotplugging from working properly, can't really help you with that. ;)

But I don't think InstigatorX kernel thread is the right section to discuss that either way.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ckisgen:
is that why you've continued to have this 'off topic' conversation in the thread?

it's exactly this kind of stuff that usually keeps me from posting anything on xda anymore and why most threads just turn into noobs asking the same questions over and over.

your logic is weak. (just because you don't have this issue doesn't mean there's something wrong with the several other people who do have this issue or something is 'off' in their setup/ROM) once again, you don't know what you're talking about. I have looked thru the dmesgs, kmsgs, and logs to see if I could identify anything that is causing both cores to get stuck on. I guess the fact that I have compiled / modified / hacked / and released my own kernels means I have no authority to speak on this stuff, right?

sarcasm, fun, or not - my posts have been relevant to this thread because InstigatorX asked for feedback on various govs and even made the comment that hotplugging doesn't seem to work quite right all the time these days on most govs.. others (you) made the post that a certain gov worked perfectly... when in fact, though it may work well for YOU, it doesn't for me, and several others I've seen in both the official LK thread and others. that's relevant to a devs decision as to whether or not to include them in future builds.

I currently have a PM convo going with Imoseyon about this very issue and have for several days.

so, feel free to post your own personal experiences with whatever govs work well for YOU, but don't imply that my input isn't valid or state that I must be doing something wrong (or am incapable of basic or even advanced troubleshooting) just because I post my issues with this or that gov. especially when the person you are dismissing has the creds to back up what they're saying.

props to InstigatorX for soliciting input from users on this stuff and for hacking together a pretty mean kernel. it's been my dd for a couple of weeks now.

peace
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
Don't need to boast your achievements to try and undermine someone's opinion either. Last thing XDA needs is a show off contest.

Never did I imply your input wasn't valid.

So nothing is wrong with your setup, yet hotplugging doesn't work? We'd have to discuss this sort of logic over a beer.

Does it hotplug for me, as well as many others? Sure does. So instead of having this discussion, what are we waiting for to eliminate the causes one by one until we get to the cause?!

I wholeheartedly agreed with iX that indeed, hotplugging is broken on a lot of governors, that are unsurprisingly half-assed hacks of govs that were thought out for single core devices. Ain't surprising.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] InstigatorX:
New version on goo.im posted.

iX-CM10.1-I747-Kernel-1369970732.zip
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] InstigatorX:
Another update posted with the IOMMU patches that enable more RAM. This version also has a heavily modified hotplugger based on Thalamus' original. I think the only thing that resembles the original code is the copyright and credits. :) Works well for me and sips the battery. Would appreciate feedback. Also, added some new freq steppings to take advantage of AVS.

EDIT: Oh yeah...and I added FIOPS I/O scheduler, tweaked Intellidemand a bit, added screen off max freq limiter (702MHz), some scheduler tweaks, and a bunch of under-the-hood stuff.

http://goo.im/devs/InstigatorX/Kernel/D2-CM10.1

File is iX-CM10.1-I747-Kernel-1370028974.zip
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] JJRules:
Am I goof? I'm not seeing the link.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] InstigatorX:
Sorry, should've added that it'll take a few moments to mirror. I uploaded, but goo takes its sweet time.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
Does FIOPS show any tangible advantage over ROW?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] InstigatorX:
Not sure. Seems about the same from a benchmark perspective, but I'm hoping you guys can give it a try.

Here's a link with some additional info...

http://xdaforums.com/showthread.php?p=23885668
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] dhatch93:
running well so far... did you get rid of westwood TCP Congestion Control for any reason? seemed to make my wi-fi work a little better... no worries if it's not worth keeping in - just checking :cyclops:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] InstigatorX:
Crap... Was doing a compare against stock cm10 and my config and forgot to switch back. Will update tomorrow.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] matrixzone:
Just wanted to check if that fix is included in the latest release

Edit: Which is the latest version for cm 10.1? Bit confused

Is it iX-CM10.1-I747-Kernel-1370143140.zip?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] bstylz911:
Will This work with tmobiles tw roms or only atnt?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] InstigatorX:
3140 is the latest for cm10.1.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] matrixzone:
Thanks for your response. How do I found out the exact kernel version of your kernel releases? I am using ROM which is based on 3.4.45 kernel, so looking for the compatible kernel