yashsingh1/xdaforums huggingface dataset:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] RJQXCV:
Switched to Dalvik. Wiped cache and dalvik. Reflashed ROM and kernel. Ran for 30 min went back into recovery. same error. Will try without kt next time

Sent from my Samsung Galaxy S6 using your mother's preferred browser
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Lessaj:
I'm using Dalvik, so I don't think that's a factor. My only guess is that older bootloaders cause it. I don't mind because I go into recovery to flash cache anyway, and it doesn't rebuild the cache every time I reboot normally so it must be working.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Epikarus:
I'm on mk5 bootloader and I have this issue. Latest bootloader for i747
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] matrixzone:
Sorry for the delay, went to sleep. Downloading now, will share my findings shortly.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
Dont worry about it. Its been tested and works :D :good:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] matrixzone:
Just tested, working as expected.. You rock man!!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jukiewalsh:
How do you change the max GPU frequency? Is that the menu that comes up when you click on the "GPU section" header?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Epikarus:
You cannot change the GPU frequency
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jukiewalsh:
Actually you can and that is exactly how, you might need to be on a governor other than on demand. I verified it with trickster
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] berryman13:
Yes GPU Max Frequency is definitely in TRICKSTER, but I and I'm pretty sure 99% of all other kt users use ktweaker....however, I really like this idea and I'll pass it on to ktoon....GPU max frequency option in ktweaker....the levels in trickster are 128, 200, 300, 400. I use the GPU gov simple. Not ondemand or whatever, the default isn't that great on battery and simple is fantastic!

Really like that you pointed out the option was available through trickster, if it isn't in ktweaker then there's a real request that should be dealt with and it's functional, not aesthetic! Lets hope it happens.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Prufta:
Deleted
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] berryman13:
You're mixing up underVOLTING and underCLOCKING.... Currently you can select the gpu governor, change the voltages, but you can't select a max voltage. or minimum for that matter, but unlike the CPU, the gpu doesn't need it. so yeah, I'd like to the able to set the max frequency ad well as control the voltages of my device when it is on that frequency :) right now we can only do the latter, the first is chosen for us.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jukiewalsh:
I'm not just pointing out that it's in trickster I meant i verified that it works with kt too by using trickster. if you tap the gpu section header a menu pops up with either 128, 200, 320, 450, 477, and 504. This is for the max gpu frequency. It already is in ktweaker but it seems to be "hidden" haha.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] goodtimes50:
I'm using the 4.3 TW kernel and I've been getting constant reboots. For some reason a last_kmsg isn't getting produced, though. Any idea why that might be? Are there any other options for finding the source of the problem?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] matrixzone:
Everything working perfectly at my end, please try clean flash and report back
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jukiewalsh:
Did you under volt a lot?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] goodtimes50:
I've done a couple clean flashes. I was having this problem (no last_ksmg) on the prior rom I was running as well (TW 4.1.2).

I've tried undervolting a bit as well as running at the default values. I get the reboots either way.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Perseus:
After that last clean flash did you try running Ktweaker at stock Values ? Try wiping the data for KTweker.

Can you try grabbing a Logcat from inside KTweaker ?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] goodtimes50:
I did wipe data (although that didn't seem to reset all the settings for some reason) and running at stock values. I'll try grabbing a logcat...
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] lambgx02:
Hey ktoonsez,

Looks like my original compass/gyro integration patch had an issue in landscape mode; this fixes it:

diff --git a/arch/arm/mach-msm/board-m2.c b/arch/arm/mach-msm/board-m2.c
index 4765640..781fdb2 100644
--- a/arch/arm/mach-msm/board-m2.c
+++ b/arch/arm/mach-msm/board-m2.c
@@ -2094,7 +2094,7 @@ static struct platform_device opt_gp2a = {
static struct ext_slave_platform_data inv_mpu_ak8963_data = {
.bus = EXT_SLAVE_BUS_PRIMARY,
.orientation = {0, 1, 0,
- -1, 1, 0,
+ -1, 0, 0,
0, 0, 1},
};

Sorry bout that. :)

Should I ping the CM guys at some point, or do you push patches upstream?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] berryman13:
You're telling me there's settings for max gpu frequency of 118, 200, 320, 450, 477 and 507 Mhz (awfully high for a GS3) in the KTweaker app for the Galaxy S3 and not S4? I was in the GPU page tapping the header and everything I could think of that someone may call a header.... Nothing.

did you mean that you had ktweaker and trickster installed at the same time? trickster on top off ktoons kernel is easily done but I don't see why someone would :P
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Perseus:
I think you should have them commit it. I suspect [MENTION=4354056]KTOO[/MENTION]nservative has shared the device tree so he "could" commit himself too.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] RJQXCV:
Take notice of the orange "GPU Section." Click it.

Sent from my Samsung Galaxy S6 using your mother's preferred browser

---------- Post added at 06:43 AM ---------- Previous post was at 06:39 AM ----------

Bump.

Sent from my Samsung Galaxy S6 using your mother's preferred browser
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] berryman13:
oh that is interesting..... I talked to KT on hangouts he said it wasn't functioning when he tries to port it so I wouldn't think it's working and don't mess with it imo :) it's already there for the s4 but he is having trouble porting it is think
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] RJQXCV:
Now I just want to know why the awake time on my phone is less than my screen time.

Sent from my Samsung Galaxy S6 using your mother's preferred browser
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Perseus:
Post a BBS Text Dump on its thread please. That's really off-topic for here.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] RJQXCV:
Not really, considering the fact that it only happens with this kernel.

Sent from my Samsung Galaxy S6 using your mother's preferred browser
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] goodtimes50:
Here's a logcat from just after my last reboot.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] goodtimes50:
Just got another reboot. Here's the logcat. Can anyone see what the problem is?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jukiewalsh:
Oh okay well it seems to be working on my end for some reason. I tested with a few other kernel tweaking apps and a few system monitor apps and the settings look to be sticking. I've only tried 320, 200, and 128 though. I had a few reboots when I was on 128 and did a lot of switching between apps and games though. I'm just going to leave it at 320 and see what happens or just go into trickster to set on each boot
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] berryman13:
http://i62.tinypic.com/2zyefcy.jpg

indeed I was correct, any effects are placebo and it's just for testing
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Perseus:
Was this Logcat just after reboot or before it ?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] goodtimes50:
Just after. As soon as the phone booted I went into KTweaker and grabbed it. Am I doing it wrong?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] procco13:
It is probably more helpful to grab the last_kmsg, especially after a reboot.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] goodtimes50:
I'm not getting a last_kmsg after reboots and haven't for quite a while. I was told that many kernels are no longer producing last_kmsg's for some reason.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] PlayingPoise:
You can produce one in the KTweaker app, if I'm not mistaken?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] goodtimes50:
You can copy the file from the original location to the KTweaker folder, but there's no file to be copied.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] procco13:
I took a look and you are correct. Hmm. Don't know what to tell you.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] 65coupei6:
FauxSound is not working with the 1/18 4.3 TW version. Will there be an update?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Perseus:
Next time Read the Op. There's been updates. Use 02-01-14.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
Post #3 updated with volt table for people to experiment with:

http://xdaforums.com/showpost.php?p=28399842&postcount=3
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Kenneth.Torres:
Yes! Woooooo cm10 love <3 lol. So is it fine to under volt with system tuner? Or does it not stick?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
Give it a try and see, I use Voltage Control.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] manny05:
I can't under volt under 850.thats the lowest it can go. I'm using voltage control.

sent from my GALAXY SIII
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Kenneth.Torres:
Got mine to 825
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
Ya, someone needs to contact the maker of it and ask for him to lower it. Anyone have the pay version where they can ask?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] lordmorphous:
You're correct...fixed!

I even proofread that...twice
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] zanzee:
Would it be possible for you to add in fuse-3g for ntfs and exfat, usb audio and usb ethernet modules into the kernal? I would really appreciated this for usb otg support, thanks.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] BabyHuey:
No
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] gomisensei:
Out of curiosity, what kind of features are you planning on implementing as your kernel matures? I don't wanna put pressure on you, or be ungrateful, I'm just wondering about your priorities.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
Stability over all, awesome battery and still fast as hell :D
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] gomisensei:
Well, i noticed you've done some work with Siyah kernel, are any of the features in it in your gameplan? For example, the OndemandX governer, the ExTweaks app for configuration, the ability to set USB charging current, etc.

Not to mention the amazing Siyah recovery with dual boot/UMS . </fanboy>
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
No for all except ondemandx, extweaks is not open source and neither is dual boot.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] schwann:
I'm on AOKP and the lowest frequency is 384
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
Your not on my kernel then or you need to wipe, 192 is the lowest
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] justin860:
After flashing the latest jb kernel GPS navigation was a complete no go it would lock but something was wrong I tried 8 different gps applications and every single 1 kept saying I was in the same exact spot but I was actually driving I went back to the original kernel that is included in the cm 10. And the problem was fixed completely it showed that I was locked on to some satellites but like I said it thought I was not moving
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Kenneth.Torres:
I don't think this kernel likes volume+ because I had it installed and everytime I played a video/listen to music it would crackle up and eventually make a very high pitched noise.

Edit: seems to be the same thing with DSP. Must not like equalizers
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] schwann:
That's odd. I flashed 7/19c and its back to 192. When I flash 7/21 I get 384. I'm on aokp.

Sent from my unlocked Motorola Atrix.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
You probably shouldnt be loading this kernel since you have a "Motorola Atrix", lol. You are loading the wrong kernel (I.E. Jellybean or sammy version maybe) or soemthing or you arent clearing cache, dalvik and fix permissions AFTER installing kernel.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] gomisensei:
Well, I didn't mean ExTweaks specifically, I just meant a way to configure options, etc, even a text .conf file or something.

I understand the dual boot thing is probably way too much work to implement, especially in the early days of a kernels development when stability is a priority.

thx for the answers
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] 65coupei6:
I must be blind. I read the OP which was last edited 1/28 and do not see updates for a 02-01-14.

EDIT:

Forget it. I found it here : http://xdaforums.com/showpost.php?p=49960968&postcount=14132&nocache=1&z=2034014947540499
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Perseus:
For Next Time, bookmark this link.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Reechings:
Is there some trick I am missing with the swipe to wake feature in ktweaker? I have tried using it with various versions of the KT kernel on multiple phones/ROMs over the years and every time it just makes my phone reboot.

Tapped it!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] berryman13:
Very rarely used option so there isn' much upport to be foudn regarding it,
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] sdlopez83:
Any new major commits?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Perseus:
Check on CM's Device Tree on their website. You can find for yourself.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] buildnoob:
What's so custom about the WiFi driver? Can you add monitor mode support?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] RJQXCV:
Why would you quote the whole OP?

Sent from my Samsung Galaxy S6 using your mother's preferred browser
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] berryman13:
Seriously.... Pick out what is pertinent and don't be lazy.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] JoshReuben:
Word. That was enough to cause my whole world to wobble for one vetiginous moment ;)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] chowhoundb:
Anyone running cm11 snapshot m3 with the 1/28 ktkernel?

Just curious if any of the kernel commits made since 1/28 break anything?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mrsubway:
Just updated. No sounds.

Update. Made a phone call and system sounds returned. Rebooted. Still working. ROM glitch perhaps. Kernel is fine. :D
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] RJQXCV:
Didn't have sound either. Called, still no sound. Rolled back to last night's nightly.

Sent from my Samsung Galaxy S6 using your mother's preferred browser
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] sdlopez83:
This was the real reason I asked if there were any updates. Lol being an ingrate.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] RJQXCV:
What?

Edit: Why don't you do us a favor, flash it, and tell us if it happens to you too. ☺

Sent from my Samsung Galaxy S6 using your mother's preferred browser
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Epikarus:
I don't have any issue with sound cm11 M3 with this kernel.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] RJQXCV:
Downloading the 2/11 nightly now. Anybody have sound issues with it?

Sent from my Samsung Galaxy S6 using your mother's preferred browser
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mrsubway:
I'm still on m3 and the sound is still working. Just a note. Cleared dalvik and cache, flashed m3, then flashed kt. So, I dirty flashed. Sound issue was only the first boot.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] RJQXCV:
2/11 nightly sound works fine on first boot. Hopefully yesterday was just a fluke.

Sent from my Samsung Galaxy S6 using your mother's preferred browser
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mrsubway:
Confirmed. Just updated to 2/11. Sound fine on first boot. :D
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] chowhoundb:
Updated to 2/12 nightly with kt 1/28 and all seems fine. I did run into some camera FC's but they seem to be fixed after a reboot.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] RJQXCV:
Last night's update was a good one, and I can confirm sound works.

Sent from my Samsung Galaxy S6 using your mother's preferred browser
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] matrixzone:
Eagerly waiting for the next AOSP kernel update, currently enjoying the TW Kernel :good:. Think the following updates have been added since last AOSP kernel update:

disable CONFIG_SECURITY_SELINUX_DEVELOP (android_kernel_samsung_d2)

d2: pulse the led (android_kernel_samsung_d2)

Revert "usb: hsic: suspend hsic until really activated by the gadget driver" (android_kernel_samsung_d2)

Revert "HACK: usb: gadget: Fix enumeration on boot" (android_kernel_samsung_d2)

remove Bayer sensor (android_kernel_samsung_d2)

Apexq: import touchscreen driver change from d2 ML1 (android_kernel_samsung_d2)

Bump nom voltage for MSM8260A (android_kernel_samsung_d2)

board-mms-tsp: fix derped ifdefs (android_kernel_samsung_d2)

HACK: usb: gadget: Fix enumeration on boot (android_kernel_samsung_d2)

usb: hsic: suspend hsic until really activated by the gadget driver (android_kernel_samsung_d2)

Stop the kernel complaining about rild. (android_hardware_ril)

add fading led (android_kernel_samsung_d2)

msm_serial_hs: borrow m7 version. (android_kernel_samsung_d2)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Perseus:
3, 6, 10 & 11 seems to be important ones. May be 7 too at a stretch. I guess you guys are rooting for 12 :)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Helloworld294:
Fading LED is the shizne. I love it 120%
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Lessaj:
Actually yea it's pretty cool. :P

I love this kernel but unfortunately I need to move away from it for a while... Whenever I flash it with CM11 my bluetooth no longer works properly. It'll work for a couple minutes (albeit the speed seems to be very slow) and then it just doesn't work anymore until a reboot. I need my bluetooth connection to work properly for my Pebble. I'll keep my eye out for any updates though. :)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Helloworld294:
You should flash the latest cm11 13022014 version and then flash this kernel, see if it works gurlll :P

If it doesn't, then I guess cm11 commits break due to incompatibility with the outdated kernel (ktoonz).
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Lessaj:
Actually I'm running 02/13. :)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Naddict:
Thread cleaned of off topic material...

Contribute with respect, leave the off topic banter for the appropriate threads, or better yet, go somewhere else for that stuff.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Prufta:
Ktweaker would be unified (d2lte), to be able to use it on all S3 variants??
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
Building up an updated AOSP 4.4 right now guys, the merge, merge, merge commits are driving freaking bonkers, been at it for 4 hours now
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
OP Updated

Change Log 02.20.2014

1. CM sync

2. Added the CM LED kang from decimalman

3. Linux all up to date

ENJOY!!!!!!!!!!!!!!!!!!!!!!!!

Let me know ASAP how things go so I can update the Sprint and Verizon guys :D :good:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] chowhoundb:
So are the kt747 builds going to be unified across the d2 lineup? Or will you continue to support a separate build for each device?

I am backing up now and will flash shortly, and let you know how things run.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] culson_35:
Download to test :)

Carbon 4.4.2 (sgh-t999l)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
I have searched many times when I have seen this but no idea how/what they are doing it since all the phones have a different network and modded hardware. So answer is I have no idea, lol.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] culson_35:
I don't no but say (error) when flashing

Carbon 4.4.2 (sgh-t999l)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
In recovery it gives you an error or it doesnt boot after a successful flash. Sounds like you are saying it wont flash in which case is a recovery issue or bad download. The file is:

8,542,773 bytes
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] chowhoundb:
ktoonsez, any changes to KTweaker this time around?

So far, so good. Flashed cleanly. Booted normally. All my kernel settings seems to be working. Will keep an eye on betterbatterystats to make sure there aren't any crazy wakelocks. I will provide another update if any issues come up.

P.S. The pulsing LED looks soooooo much nicer!

Thanks for your hard work and for still supporting us GS3 users, ktoonsez!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
Coooool man. Thanks for the update :D. :good:. No updates to ktweaker.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] chowhoundb:
May have spoke to soon. Looks like I am not getting LTE, only H+. This is in a spot in the building that I normally have 3-4 bars of LTE. Ive rebooted, airplane mode on/off, and changed the mobile network mode. No luck.

Would this be a rom issue or kernel? I flashed both new just now. CM11 2/20 nightly.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
A service in the ROM for cell service. Did you check your APN's? And just a heads up, the newest real CM is 02.17, no 02.20 so that could be your issue.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] chowhoundb:
Thats probably it. I am using the 2/20 nightly for new unified d2lte. I will try the 2/17 d2att nightly.

APNs are correct.

UPDATE: just booted into recovery and realized I did not have the 2/17 nightly. Rebooted back into the 2/20 d2lte nightly and I now have 1 bar of LTE. I think I will still flash the 2/17 d2att nightly if that is what you synched for your kernel build.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Steuartl:
Hmm running PA4 Beta 4 and Wifi is broken after update, likely from it being a couple weeks old. Anyways heads up
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] culson_35:
True.... Bad download....I download again,flash and work.....thanks :thumbup:

Carbon 4.4.2 (sgh-t999l)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] chowhoundb:
Strange, looks like I am having the same issue on 2/17 d2att nightly.

If I go into Mobile Network settings, It keeps resetting my preferred network type to: GSM/WCDMA

I don't understand this much but I wonder if this has something to with it:

http://review.cyanogenmod.org/#/c/59846/

This is a commit in the 2/18 d2lte build.

ktoonsez, can you grab this commit and add it to your 2/20 kernel build?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] tasteslikechicken:
I'm running the 2/20 d2tle nightly and neither the 1/28 nor the 2/20 kernel will install. Status 7 and some warning about the last_install file in /cache/recovery
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] chowhoundb:
Flash rom, then GAPPS, then wipe cache, and then flash kernel.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
My kernel is up to date even with the commit from today, so I guess 2/17 is too old but there is no nightly so not sure what you should do, 3g/4g stuff is definetely not kernel related though.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Greycloak42:
Working great with quantum v3.4.