yashsingh1/xdaforums huggingface dataset:
[Verizon Samsung Galaxy S III] buggerritt:
That's interesting. I don't like that it relies on downloading files from a server during install, though. I think I'll stick with the current method I'm using. Thanks for the link.
[Verizon Samsung Galaxy S III] Josolanes:
The 4/11 nightly has been awesome, most stable 3.4 kernel ROM I've tried and I went through several. No more inability to activate even through restarts and I was able to up my KT747 over clock a hair to 1.89Ghz without stability issues.

I need to look through the ROM some as maybe I missed it but, something I'll try to find is the hold back button to force quit an app.
[Verizon Samsung Galaxy S III] WettbackMartyr:
Look under settings > CarbonRom > navigation > hardware keys, for the hold back to kill function
[Verizon Samsung Galaxy S III] david_hume:
Holy crap! 68 hours without a reboot or freeze! First Carbon ROM that hasn't rebooted after 5 hours! Now this ranks up evenly with Liquid's Stable version and AOKP MR1 build 5 on my list as the most stable AOSP ROMs.

Sent from my Carbonized GS3
[Verizon Samsung Galaxy S III] jamesino:
Which version of Carbon are you running? I'm running the 4/8 nightly with 4/11 KT kernel. It's been about 2-3 days now and I havent had a single freezing/SOD problem.
[Verizon Samsung Galaxy S III] keynith:
So whats the other vzw download with a carbon 12 in it?

http://goo.im/devs/carbon/dg4prez
[Verizon Samsung Galaxy S III] ckelly33:
I don't even know what the one with the 11 in it is. Open it and see!
[Verizon Samsung Galaxy S III] BlazingGlory53:
I am really enjoying this ROM, but I have a nagging question. For this, when you pull down the notification bar, when there are no notifications, it will always go to the Quick Tiles by default. There a way to turn that off?
[Verizon Samsung Galaxy S III] ckelly33:
1 finger vs two pull down?
[Verizon Samsung Galaxy S III] WettbackMartyr:
Yes there is. Got to settings > CarbonRom > Statusbar Toggles > Enable Fast toggle (check) > Set toggle side (left or right). Now when you slide down the notification shade from the center or opposite side you will get just the notification shade and not the toggles! Hope this helps.
[Verizon Samsung Galaxy S III] BlazingGlory53:
Thanks. I'm used to CM's method which was a setting not depending on which side you pull down.
[Verizon Samsung Galaxy S III] Josolanes:
@Wettbackmartyr

Thanks! Yep this will be my ROM for quite a while now, extremely fast and stable and has all the options I could want

(Forgot to quote in the xda app -_-)
[Verizon Samsung Galaxy S III] keynith:
So that other vzw download is for us. Idk the differences but i hope whoever runs it posts about it as far as a changelog for it. I might flash, but i like this nightly and don't see a reason to without a dev response.
[Verizon Samsung Galaxy S III] cobija:
Great ROM, I was on TW since I have had my phone and slowly dipped my feet into the AOSP pool with Beans but decided to throw myself in :p

Crazy the amount of customization you can do with this. I had a request, can you put a toggle for the keyboard input notification? Some people change it often but I personally don't. Thanks :)
[Verizon Samsung Galaxy S III] dg4prez:
I swear you guys will flash anything I post.

That was to test goo.im's incremental updates. It didn't work so well, though. The incremental file was as big as the original.
[Verizon Samsung Galaxy S III] WhiteAssBrent:
Maybe one of you can help me out. I've used Handcent as my text messenger forever and never had this problem.

When receiving a text sometimes the sound works fine and other times it loops and keeps going till I turn it off. Is it a known bug or something on my end?
[Verizon Samsung Galaxy S III] PeakyBoo:
First off, I don't know what set up you are on but, I am on Carbon 4-11 KT 4-11 running ktoonserv/zen with TKMod1.0.2 and some other stuff. I have no issues with Handcent!

That being said, have you, 1, set Handcent as default SMS/MMS?

2 frozen stock mesanger app with TiBu?

Try if not. Hope this helps

Peakyz ° S lll °
[Verizon Samsung Galaxy S III] kryptik06:
Great job, going to test the latest nightly with ktoon's latest kernel
[Verizon Samsung Galaxy S III] bitemeoftn:
That was smart on your part. I tried the installer a. it doesn't work. Actually tried twice, once without restoring the build.prop and once restoring it. Both times it says my device isn't initialized even though I have full 4g. It was worth a shot though I suppose.

Edit: After the fourth attempt it finally worked. Guess I spoke too soon lol.
[Verizon Samsung Galaxy S III] keynith:
Haha i didnt flash it, just was curious about it.
[Verizon Samsung Galaxy S III] Mikecolorama:
i'm on 1.6.1 and had my screen freeze during a call for the first time today. i don't know if it's related, but now under Mobile Network State, it says Disconnected. not sure what to do to get it back.
[Verizon Samsung Galaxy S III] bamaredwingsfan:
I've been having the same trouble, what kernel are you using? I'm using the stock carbon kernel. Get 1 to 2 freeze ups a day.

Sent from my rOot3d Samsung Galaxy S3
[Verizon Samsung Galaxy S III] Mikecolorama:
i'm on the stock kernal. are you having problems with the screen freezing or mobile network state?
[Verizon Samsung Galaxy S III] bamaredwingsfan:
Screen freeze, an sometimes sdcard errors too

Sent from my rOot3d Samsung Galaxy S3
[Verizon Samsung Galaxy S III] khaoskosmos:
I've had this issue on stock kernel and kt747.
[Verizon Samsung Galaxy S III] bamaredwingsfan:
Guess I'll try the 3.0BMS kernel then

Sent from my rOot3d Samsung Galaxy S3
[Verizon Samsung Galaxy S III] ckelly33:
Under settings> data usage...are you "on"?
[Verizon Samsung Galaxy S III] Mikecolorama:
ya, i figured it out. not rom related. my 4 year old went into setting and turned off the automatic time and date
[Verizon Samsung Galaxy S III] WhiteAssBrent:
I'm running 1.6.1 with stock 3.0 kernel. Yes Handcent was set as default and I did end up freezing the stock messenger and tested again and the notification sound still loops until I click the text message.

I remember like a month or two ago there might of been something sorta similar to this with ring tones, except the ring tones would not loop and only play one the sound once. I'll do some searching deep into Handcents settings... Maybe I clicked some loop option by mistake, but then again that wouldn't explain why it only plays the sound once sometimes.

EDIT: I played around and selected a new sound and then went back to the original sound giving me problems and it has now stopped looping on incoming messages.

Sent from my Verizon SGS3 Carbon 1.6.1
[Verizon Samsung Galaxy S III] hsomnus:
Decimalman' 3.4 kernel is da ****...happens to be the only 3.4 kernel that plays nice with my phone!
[Verizon Samsung Galaxy S III] BrUhNiGGs:
I don't get how people manage to get no freezing at all with ktk kernel 4/11 on the latest nightlies or Stable liquid 2.2. I tried a clean a flash with the kernel and immediately it freezes up out of nowhere after about 5 mins of use.
[Verizon Samsung Galaxy S III] TheBurgh:
Agreed........It has been spot on perfect for me.
[Verizon Samsung Galaxy S III] SpyroDazee:
Edit: wrong forum, please delete
[Verizon Samsung Galaxy S III] WhiteAssBrent:
I haven't used any kernel other then the stock kernel provided, that being said... Do the freezes come when everything is brand new out of the box to say, not installing any apps yet or after you do some type of restore with TiBu?

For me, I had a bunch of freezing problems and gapps quitting on me from trying to restore "All apps + system + data" to get everything as close to back to what I had before installed. From playing around with TiBu I've learned I can still do most, I just have to make sure to uncheck everything RED before hitting the restore button.

Not sure if that's the case for you, but if it is, I hope it helps. This is a nice ROM when it works! Good Luck

Sent from my Verizon SGS3 Carbon 1.6.1
[Verizon Samsung Galaxy S III] OMG_VTEC:
i had my first freeze yesterday during a phone call, updated kt kernel to the 4-11 build and never went past 00.00 on call time. back to the 3-27 build and everything is great again...
[Verizon Samsung Galaxy S III] PeakyBoo:
Glad you got it. BTW was having issues with KT747-4-11 kernel so I went back to LK 4-10 2.9 build with Carbon 4-11 nightly. My phone seems to like LK and not KT.hmmm. Oh well, what ever works i guess.lol

Peakyz ° S lll °
[Verizon Samsung Galaxy S III] ECrispy:
Not sure what is the point of 3.4 when it doesn't have any benefits and seems to be causing problems in every rom its used. It is the latest and newest but obviously not stable enough for all users on the GS3.
[Verizon Samsung Galaxy S III] pocii29:
No problem on 3.4 with 4/7 everything is smooth and no reboots. Y'all are missing out
[Verizon Samsung Galaxy S III] aj8600:
The problem isn't the kernel, it's how it's made that's messing people up. Find the right dev and it'll be fine
[Verizon Samsung Galaxy S III] draexo:
There's no choice anymore as all theses AOSP roms are CM-based and CM switched.

Sent from my Carbonized S3 via Taptalk
[Verizon Samsung Galaxy S III] Josolanes:
fwiw I'm running KT747 4/11 with Carbon 4/13 nightly and it runs very well. OC at 1.89Ghz with upped voltage from 1726 and above and lowered voltage elsewhere

I just tried the 4/14 nightly and got nothing but system ui crashes. Dirty flashing back to 4/13 fixed it so staying with 4/13 for now
[Verizon Samsung Galaxy S III] draexo:
What does the GCC 4.7/03 in thread title mean???

Sent from my Carbonized S3 via Taptalk
[Verizon Samsung Galaxy S III] Wi1son:
Anybody running 4-14 and having no issues?

Sent from my SCH-I535
[Verizon Samsung Galaxy S III] PeakyBoo:
+1 ^ I also just tryed with LK latest and got the same thing. "System stop" bat pull re flashed my BU.

Peakyz ° S lll °
[Verizon Samsung Galaxy S III] TheBurgh:
No go for me as well. System ui crash
[Verizon Samsung Galaxy S III] david_hume:
Basically speed tweaks. :)
[Verizon Samsung Galaxy S III] Josolanes:
Sent a small donation, very happy with this ROM :)
[Verizon Samsung Galaxy S III] ckelly33:
I have a weird issue. I have, on a couple of occasions, noticed that when I go to battery under settings it lists the time on battery WAY off. Today for instance it lists it as 43 minutes but I've been on battery for over 4 hours.

Is thus a known issue or is there a fix? Not a very big deal but it is surprising that it can't time it even close!
[Verizon Samsung Galaxy S III] bigee1212:
Waiting for someone else to try because the system ui memory leak fix is really appealing to me. My phone always lags after a few and have to restart systemui to smooth it out again.

Maybe I'll give it a row night lies before I flash 4_13 with lean kernel no issues besides the systemui leak... (Takes just a second to restart it anyway)
[Verizon Samsung Galaxy S III] david_hume:
You might've had a reboot. Check the up time in the status section of the settings (located in the about phone section). I don't have any issue at all as far as battery representation goes.

sent from my Hard Carbon S3
[Verizon Samsung Galaxy S III] ckelly33:
No. I checked my running apps and some were running that I last used last night. Anyway, a reboot fixed it and now it is dismaying almost 5 hours. Strange.
[Verizon Samsung Galaxy S III] pocii29:
Did you press the refresh button at the top?
[Verizon Samsung Galaxy S III] sinman02:
Can someone please advise which latest version of lean kernel works with carbon 1.6.1 release? It's kinda confusing. I can only use a 3.0 kernel, right? I've tried the 3.0 kt kernel and it kept giving me random reboots. I'm currently on the stock kernel. Thanks.
[Verizon Samsung Galaxy S III] fcardona86:
Great rom. Very stable.
[Verizon Samsung Galaxy S III] bamaredwingsfan:
I've been running the 3.0BMS kernel for close to 24 hrs an have yet to freeze up

Sent from my rOot3d Samsung Galaxy S3
[Verizon Samsung Galaxy S III] PeakyBoo:
I believe (someone correct me if I am wrong)

its the v-2.9 that is for 3.0 just look for your phones VERSION here . the ones that end with 2.9.

http://imoseyon.host4droid.com/s3/aosp/#!/view=details/lang=en/sort=na

Edit;think its this one if your Verizon.:thumbup:

lk_s3vzw_aosp_jb42-v2.9.zip

Peakyz ° S lll °
[Verizon Samsung Galaxy S III] david_hume:
Yeah, you're right. Anything after 2.9 is designed for the 3.4 kernel.

sent from my Hard Carbon S3
[Verizon Samsung Galaxy S III] ckelly33:
Nope, ha! I've never noticed that before. Its happened twice, if it happens again I will try that. On all other occasions it is accurate upon opening.
[Verizon Samsung Galaxy S III] jamesino:
I know this set up is outdated, but I thought I'd chime in here just in case anyone is having problems with the new builds and wants to fall back on a stable old build.

Been running 4/8 Carbon nightly and 4/11 KT747 for about 4-5 days now. Not a single SOD, freeze or lock up. Been very table and very fast (with governor tweaks) so far.

On another note, are the new Carbon nightlies merged with CM10.1 M3?
[Verizon Samsung Galaxy S III] uberbdon:
Have the issues with M3 been smoothed out regarding our phones?
[Verizon Samsung Galaxy S III] khaoskosmos:
Do you get random screen glitches like scrolling back etc...?
[Verizon Samsung Galaxy S III] ckelly33:
The only glitches I seem to have with the screen are times that it responds all by itself by reverting back to my previous view. Difficult to explain but it is as if I hit the back button (without actually touching anything on the screen)
[Verizon Samsung Galaxy S III] jamesino:
I do get the grey static lines from time to time. It is app and brightness dependent. Usually it's not a problem. Only on rare circumstances do they appear. But I've had these with every ROM I've tried including Stock (however, on stock, the flickering lines disappeared right away when I turned off and back on the screen).

Now that you mention it, sometimes in the Feedly app, when I just opened an article to read, it would back out (like as if I hit the back button) for a half second and go back to the correct view.

This is the only app where I have observed this phenomenon and only happens like once or twice in a sitting if it does happen.
[Verizon Samsung Galaxy S III] ckelly33:
36 hours in and I just had my first random reboot. 4/8 and KT 4/11 (ktoonservative)
[Verizon Samsung Galaxy S III] Trumps:
I had to switch back to 4/7 to eliminate the screen glitches.
[Verizon Samsung Galaxy S III] system6:
This is a known issue but was reported as being fixed by CM on Saturday. I was excited for yesterdays nightly for this reason, but it was reported that it didn't boot.

I'm hoping someone will report back on the latest nightly.
[Verizon Samsung Galaxy S III] mapatton82:
I flashed the latest nightly 4/15 and it booted but my phone was very sluggish after flashing it. I needed my phone so i flashed back to 4/13. It is possible it may have needed a clean flash, but I just didn't have time.

Edit: I made a backup and clean flashed the latest nightly (4/15). It booted and seems to be running great, I restored data from my backup and everything appears to be running just fine.
[Verizon Samsung Galaxy S III] bigee1212:
dirty flashed 4/15 nightly with newest LK stable. for me it fixed the systemui getty laggy (hasnt lagged since i booted) and no screen glitching (was getting frequent glitching while in some apps such as messaging or even my wallpaper on my home screen would look like the gpu was busted until i long pressed....) anyway seems good to me.
[Verizon Samsung Galaxy S III] rfranken:
I seem to need to wipe cache and d cache and fix permissions every couple days to keep things running smooth and to stop the random reboots. (I'm not sure which of the above helps my issues but they are a very minor work around to keep me running smoothly)
[Verizon Samsung Galaxy S III] fcardona86:
You can always disable hardware overlays in developers options whenever u get that weird red/gray pixel glitching. The only thing that sucks is it resets after a reboot so you'll have to do it again. I can't honestly say I know what hardware overlays do, but I found that fix in a thread and saved me a rom of headaches.
[Verizon Samsung Galaxy S III] jamesino:
Disabling hardway overlay shifts offloads more work from the GPU to the CPU, which may slow down your phone under certain situations. Do you notice any slowdowns when you disable hardware overlay?
[Verizon Samsung Galaxy S III] draexo:
I haven't and I use this all the time.

Sent from my Carbonized S3 via Taptalk
[Verizon Samsung Galaxy S III] harosxcomp170:
I'm running the latest nightly. It's running beautiful with Imo's kernel!
[Verizon Samsung Galaxy S III] cr4ck3r4lif3:
Which lean kernel are you using?
[Verizon Samsung Galaxy S III] fcardona86:
I haven't but I'm going to watch out for it now. Thanks
[Verizon Samsung Galaxy S III] harosxcomp170:
I'm running this. lk_s3vzw_aosp_43-v5.3.4.zip
[Verizon Samsung Galaxy S III] ckelly33:
How are the latest night lies running? I'm on 4/8 now and thinking of 4/16 (since its my birthday!) but haven't seen any feedback for a while.
[Verizon Samsung Galaxy S III] PeakyBoo:
With a CLEAN flash I have been running great on the below setup.

Have had no issues with BT, SMS/MMS no reboots, glitches or scroll jumps etc...Nada:good

Edit: Deleted..opps :what:

Edit; I also switched to the latest TWRP from CWM:cool:

Peakyz ° S lll °
[Verizon Samsung Galaxy S III] mapatton82:
The 4/16 nightly is running great, no issues yet.
[Verizon Samsung Galaxy S III] PeakyBoo:
thumbup:

Clean or dirty flash?

Peakyz ° S lll °
[Verizon Samsung Galaxy S III] tprophit:
Been running 4/11 nightly and 4/11 kt747 with no issues, til today ...lost 3 calls...

Suggestions?

Thank you.
[Verizon Samsung Galaxy S III] mapatton82:
Dirty flash, just wiped cache and dalvik.
[Verizon Samsung Galaxy S III] PeakyBoo:
Make a backup. Then Clean flash Crbn4/15 nightly with stock, or your choice of Kernel. Then you can update by way Mapatton82(see above post) said, to 4/16. JMO:)

Peakyz ° S lll °
[Verizon Samsung Galaxy S III] WhiteAssBrent:
Is there any benefit to using TWRP over CWM? In the last 3 years between my HTC Dinc. & this phone I've only used CWM, and Odin once just to obtain root.

Sent from my Verizon SGS3 Carbon 1.6.1
[Verizon Samsung Galaxy S III] david_hume:
Certain ROMs work better with TWRP (Touchwiz based ROMs anyways). It really comes down to preference. A majority of ROMs work with either recovery. :)

sent from my Hard Carbon S3
[Verizon Samsung Galaxy S III] PeakyBoo:
+1^ also I like the way you can load, order then flash multiple zips at once. Makes Clean Flashing ... ie ..Rom, Gapps -n- Kernel easier.

Tnx Matt.lol

Peakyz ° S lll °
[Verizon Samsung Galaxy S III] mapatton82:
Yeah +1 to what PeakyBoo said!! When I flash a new nightly I setup (through Goo Manager) to backup my current rom, clear cache/dalvik, flash new nightly, and flash kernel. I set the phone down and it will boot into TWRP perform everything and reboot the phone. Works pretty slick!!
[Verizon Samsung Galaxy S III] austin1227:
Mms is only working through sliding messaging and wifi off. I'm running the 4/7 nightly. It also happened on liquid. I changed the APN file. Is this fixed in the later nightlies?
[Verizon Samsung Galaxy S III] 760hacker:
On 4/16 with a clean flash and having my status bar randomly disappear, anyone else?
[Verizon Samsung Galaxy S III] Wi1son:
Not happening here........

Sent by i535 with CarbonROM & KT747
[Verizon Samsung Galaxy S III] khaoskosmos:
At boot, my status bar says -1

If I slide the tray down and back up, all my status icons show up and stay there until I reboot.
[Verizon Samsung Galaxy S III] rruready:
So I flashed Carbon tonight and love every aspect of it, except for some reason the camera freezes after I snap a picture and I have to pull the battery. I'm hoping there is something easy that I'm missing that someone can point out so that I can enjoy this fantastic rom. Thanks!
[Verizon Samsung Galaxy S III] 760hacker:
Same here, bet you are on 4/16
[Verizon Samsung Galaxy S III] khaoskosmos:
Yes, I am. I quoted the other 4/16 post but it didn't show for whatever reason. So far 4/16 is running well. Maps has started using lots of battery so I disabled location settings.

Using KT747 4/11 also.
[Verizon Samsung Galaxy S III] ckelly33:
Not sure what this means. I have 4/16 running. Is the status bar missing or does a -1 actually show on the status bar?
[Verizon Samsung Galaxy S III] tpayne2345:
Same thing happened to me when I was on 4/11 for an hour, it showed my battery status as -1% in status bar for a little bit and then went back to normal

back on 4/8 now and loving it, not flashing again until the next release
[Verizon Samsung Galaxy S III] ckelly33:
Yeah, I'm going back to 4/8 too. When you went back, did you do a full clean flash or did you just dirty flash it?

---------- Post added at 07:09 AM ---------- Previous post was at 06:20 AM ----------

Wow. I just noticed that when I post (and under settings -> about phone) my phone is listed as a galaxy nexus despite flashing the 4/16 d2vzw carbon.
[Verizon Samsung Galaxy S III] kinnerful:
Seeing the "go back in time" bug mentioned somewhere above in 4/7 nightly. Is it fixed in recent builds?
[Verizon Samsung Galaxy S III] tpayne2345:
I clean flashed just to be safe
[Verizon Samsung Galaxy S III] mapatton82:
Did you flash any other zips like zip to install Google Wallet? It sounds like somewhere your build.prop got changed. I flashed the latest nightly and I haven't had any issues and my phone model is still SCH-i535 in About-Phone.
[Verizon Samsung Galaxy S III] Setco:
Just installed Carbon 4/17 with latest 4/11 KT kernel. Did clean flash. Seems to be running smooth and pretty quick too. Will check it throughout the day and post my findings.
[Verizon Samsung Galaxy S III] ckelly33:
Yeah. I did flash wallet. Maybe I got mixed up and flashed the wrong one. I was having screen glitches and sluggishness too with 4/16 with both Lean and KT. I clean flashed back to 4/8 and all is well.
[Verizon Samsung Galaxy S III] lucky13:
Essentially all the wallet installer does is modify your build.prop to show a nexus. It's changing three lines inside that to get it back to showing a s3.

Sent from my S3...like a BOSS.
[Verizon Samsung Galaxy S III] hsomnus:
The installer also has an option to change your build prop back to the correct one.
[Verizon Samsung Galaxy S III] ckelly33:
Yeah but I've re-run installer to rebuild the build.prop and it always goes back. Maybe I didn't do the second step yesterday.
[Verizon Samsung Galaxy S III] system6:
Has the screen jumping around stopped? I was hoping it would have been fixed in 4/16.
[Verizon Samsung Galaxy S III] lucky13:
Instead of relying on the installer, a simple search will give you the proper build.prop edit, do it yourself and be a 100% sure it's done right. Editing the build.prop manually is a good thing to know how to do.

Sent from my S3...like a BOSS.
[Verizon Samsung Galaxy S III] david_hume:
Does anyone know if the soft rebooting still occurs in 1.6.1? :o

sent from my Hard Carbon S3
[Verizon Samsung Galaxy S III] SpyroDazee:
3.4 kernel is a work in progress, it'll be smooth in time. Best & only one i've tried is the forbidden 3.4 aosp kernel. Never tried any other, & I don't get ANY of the problems everyone else is getting. Those who have tried it would agree.

Makes carbon nightlies work perfectly :cool:
[Verizon Samsung Galaxy S III] draexo:
Not assure as I'm 1.6 , but disabling hardware overlays in developer options seems to fix it until the next reboot.

Sent from my Carbonized S3 via Taptalk
[Verizon Samsung Galaxy S III] ckelly33:
I had it once. Haven't seen it since. Not disabling anything.
[Verizon Samsung Galaxy S III] bamaredwingsfan:
I keep getting a notification disabled popup pretty often. But I'm not sure how to fix it. I'm using insets latest experimental kernel on the 417 nightly

Sent from my rOot3d Samsung Galaxy S3
[Verizon Samsung Galaxy S III] bigee1212:
Lost data.... WiFi only works for me atm not sure what's going on.