yashsingh1/xdaforums huggingface dataset:
[Verizon Samsung Galaxy S III] carpdeeem:
Try fixing by plugging in then unplugging. Make sure you have the charging light enabled (even just temporarily).
[Verizon Samsung Galaxy S III] sweeds:
Same here. Blue pulsing LED. Goes away after 1 notification comes through. Comes back after reboot.

I even tried completely disabling the LED under the Display settings.

Anybody encounter and fix this problem before? I am a fan of KT but it was rather annoying so I switched to BMS but now getting reboots.
[Verizon Samsung Galaxy S III] sweeds:
Temp fix. Plugging in or getting a notification fixes it. Comes back at next reboot. Only happens with KT so I'll move this conversation to the kernels thread.
[Verizon Samsung Galaxy S III] BrUhNiGGs:
I encountered the same exact problem. It seems it only happens with KT kernel. Kinda the only thing keeping me away from using this ROM since I love kt kernel. Hope it gets fixed soon
[Verizon Samsung Galaxy S III] kidruk:
This rom and BMS Kernel is like a dream man .. running sioplus scheduler and badass governor is nice .. great battery life ..
[Verizon Samsung Galaxy S III] SlimSnoopOS:
I see the fact that I use Light Flow overrides this cuz I don't have a pulsating LED on boot for a minute or longer like y'all do. I did a quick test and with Light Flow, my LED pulses for about 15 seconds before its taken over by Light Flow as its granted SU. Without Light Flow, I have the same issue as y'all. I agree though, that's KT kernel related not rom related since its not like this on the SlimKat kernel.

Edit: With Light Flow installed, the LED pulses for about 23 seconds after pin unlock.
[Verizon Samsung Galaxy S III] helobubba88:
See posts 2813 and 2816.
[Verizon Samsung Galaxy S III] Rrrracer:
Wow nice screen on time!
[Verizon Samsung Galaxy S III] kidruk:
Seriously I was impressed .. BMS Kernel .. highly recommended!
[Verizon Samsung Galaxy S III] d1ez3:
Anyone having audio issues the past few builds? I get a staticy/lagging feedback sound when switching tracks in spotify sometimes. Last night it happened 2 times where the static/feedback sound didn't stop until I did a battery pull. Happens when DSP manager is being used more often, but still happens without. May need to fully factory reset my phone (back to stock, then back to a rom again) weird issue
[Verizon Samsung Galaxy S III] msternig:
I have had the same thing happen when starting a video call in Skype. It seems like it may be connected with the speakerphone audio, as I do not have the issue when making Skype voice (only) call. As the previous post mentioned, the only way to stop the crackling/static noise was to pull the battery.
[Verizon Samsung Galaxy S III] wolficus:
searching around for a 4.4 rom... how is this one as a daily? bugs?

sms/mms issues like cm?

thanks :)
[Verizon Samsung Galaxy S III] SlimSnoopOS:
If you're referring to the "1 sms sent" issue on CM, you'll experience it on every AOSP rom. It's an AOSP issue with Verizon atm.

And as of mid afternoon, I think I'm officially a member of this "1 sms sent" group. Great way to cap off my week. I may be moving away from AOSP for the time being so that I can actually send sms w/o issue. First time EVER this has happened for me too.
[Verizon Samsung Galaxy S III] wolficus:
dang... was afraid of that.

curious... are you in the Indiana area or is it spreading?
[Verizon Samsung Galaxy S III] Shakes The AssClown:
I haven't been having the SMS issue at all. SlimKat has been working well except for the sounds issue.
[Verizon Samsung Galaxy S III] SlimSnoopOS:
It's likely spreading.

I've been monitoring the sms Q/A thread cuz I knew it would spread beyond PA which is where it appears to have started in Feb. I live in Northern VA and my texts were working fine everyday I'd been on AOSP from late fall up until this afternoon when I left DC. I've been on this rom and the latest 3.8 weekly since release so I know its not a SlimKat issue. Pretty much sent 20ish texts and all failed but the moment I moved to TW, all good again.

---------- Post added at 10:33 PM ---------- Previous post was at 10:31 PM ----------

Be happy you don't cuz it sucks. I'm going to revert back to SlimKat tomorrow to see if its just a one day thing but I know my issue is akin to the symptoms outlined in the sms Q/A thread now
[Verizon Samsung Galaxy S III] wolficus:
gl.

i think i will subscribe to that q/a thread.
[Verizon Samsung Galaxy S III] kidruk:
I'm not having any sms/mms issues. Clean flash with most recent slim gapps and I'm good.
[Verizon Samsung Galaxy S III] jcurley:
I am on stable 3.0 and I ran the nightlies before that, never has a problem using hangouts as my primary SMS/MMS app.
[Verizon Samsung Galaxy S III] yamaha_wins:
My phone randomly reboots all the time. But slimkat 3.0 runs great on my nexus 10. When I installed the Rom I did a clean install. Haven't did any type of mods or replaced the kernel.
[Verizon Samsung Galaxy S III] kidruk:
Try bms kernel.

My boOped s3!
[Verizon Samsung Galaxy S III] Droid316:
Is there a sound hack I can use on this Rom.Volume seems low and I have to lower the volume and up the volume to get my speakerphone to work
[Verizon Samsung Galaxy S III] draexo:
Interesting. I am on Bean's TW 4.3 and I had that issue for a few days about a week ago in Myrtle Beach and when I posted on it no one knew what it was about. My issue was incoming message flag always being set to 1 on the message ICON. After a few days it went away by itself and has not come back.Wonder if that was related.
[Verizon Samsung Galaxy S III] kidruk:
There is fauxsound. Some kernels are not compatible with it so you would need to check out if yours is. It works really well.

My boOped s3!
[Verizon Samsung Galaxy S III] Shakes The AssClown:
http://xdaforums.com/showthread.php?t=2400231
[Verizon Samsung Galaxy S III] jcurley:
Some phones work with some kernels some do not. I tried BMS kernel and my phone couldn't even make it thru the task of opening email without a reboot.

You may have to play around to find the right kernel for you. Lean kernel is my favorite, had always been stable for me.
[Verizon Samsung Galaxy S III] sweeds:
I agree with the thoughts in Kernels. You have to try for yourself. BMS with no OC rebooted for me every 30sec, while KT with OC runs great.

Question... Has anybody ever had problems with the phone/dialer having echo problems?

It's a hard thing to debug. I was going to Odin to stock and see if that fixes. Thought I'd ask yall first.

I've tried clearing data on dialer apk and changing Kernels. Could it be a firmware update?
[Verizon Samsung Galaxy S III] kidruk:
very true. I cant overclock my bms for anything, instant reboots but it seems to give me great battery life and stability. I may try ktoonz though and see what I get from it. I kind of miss ktweaker.

My boOped s3!
[Verizon Samsung Galaxy S III] AnTiDoWn3r:
How's the front camera for apps such as snapchat? I'm tempted to move away from Carbon to try this ROM + Xposed (if that will work). I heard they still hadn't fixed the stretched and pretty buggy/laggy camera with older builds. Can anyone help me out?
[Verizon Samsung Galaxy S III] kidruk:
Still choppy in my experience. The camera is still quite buggy for me overall.

My boOped s3!
[Verizon Samsung Galaxy S III] kerfex:
Not sure if this is the correct thread.....

I'm running the 3.8 weekly build and was wondering if you were going to add the Lockscreen notifications. I was running LS 3.0 and really liked that feature, but don't like the new running app manager/switcher they switched to. Love the one you guys have out in your rom on the side with collapsible app previews. really cool! The only thing I have noticed that doesn't work in this build is adding quick tiles and unlimited widgets on the lock screen. Not even with Xposed module gravity Box unlimited option checked. It worked on other Kit Kat roms I have tried. Other then that, super job. love this rom.
[Verizon Samsung Galaxy S III] gadgetguy08:
Weekly 3.9 is up. Mostly bug fixes.
[Verizon Samsung Galaxy S III] gadgetguy08:
It hasn't happened to me in a while. I haven't seen it since Stable build 3 came out.

You may want to delete the device from the car and re-add it. I did that about the same time I went to Stable build 3, so I wasn't sure if that played a part or not.
[Verizon Samsung Galaxy S III] flyestAC:
I'm getting this blue led flash with lean kernel 9.5.1 as well. This is on a clean install of 3.9. Sent myself a text to get it to stop.

---------- Post added at 11:01 AM ---------- Previous post was at 10:40 AM ----------

Also I know this horse is dead but I'm still getting the camera issue when trying to use camera while in the messaging app. Still no auto focus either. I'm not getting the freeze ups or distortions that others are seeing on other 4.4 roms. No issue with video or FFC.
[Verizon Samsung Galaxy S III] kerfex:
No Super User

OK, Did a full factory wipe and reinstalled all including the Slim Kat Gapps full. and went to start Titanium back up pro and it said could not acquire root privileges. SU is installed. Anyone else experience this?
[Verizon Samsung Galaxy S III] flyestAC:
You have to enable root in developer options
[Verizon Samsung Galaxy S III] kerfex:
DOH!

OK, Slim is a little different in the settings then other ROMS I have tried.. I did not notice that in the developers options. My bad. Thanks for the help!
[Verizon Samsung Galaxy S III] 996:
Love the ROM, but I just have one question. Does anyone else experience big time lag in general?
[Verizon Samsung Galaxy S III] flyestAC:
No lag whatsoever. I like flashing ROMs but I always come back to Slim. Easily the snappiest, smoothest, most stable AOSP based ROM for me.

Did you do a clean flash? I use TWRP and always format data, wipe internal SD, cache, system, dalvik and data. No problems here. I also set transitions to .75, but no lag on 1 either.
[Verizon Samsung Galaxy S III] lvgdgts:
3.10 build is up. Apparently Github was having sync problems leading to build errors.
[Verizon Samsung Galaxy S III] 996:
didn't wipe my internal. I will try doing that and get back to ya.

Thanks dude
[Verizon Samsung Galaxy S III] DADER:
Pls someone guide me how to disable blinking blue boot led, it keeps blinking for very long time...

Another thing, anyone knows how to add APNs in global mode because apn options appear grey on settings (not adjustables)

Thanks in advance
[Verizon Samsung Galaxy S III] duarian:
Blue led is a kernel that took a certain CM commit. Only way to stop it is to plug your phone in and unplug it on every boot. Quantum kernel does not have this issue
[Verizon Samsung Galaxy S III] DADER:
Thanks duarian,

Now the only one thing left is how to add APNs in globlal mode if anyone knows?
[Verizon Samsung Galaxy S III] kerfex:
Quesion on 3.10

Does 3.10 have the lock screen notifications? Not Active notifications, but lock-screen. I am back on an older version of Liquid (2.10) that doesn't have their new task manager/switcher just the stock AOSP one but I really like the one in the new Slim builds but I need the lock-screen notifications and will be switching back to slim if they add that., Both are great and both are smooth but there is something abut that new Slim task manager that I just love. Thanks
[Verizon Samsung Galaxy S III] Magicman500:
There's always NiLS Notifictions.
[Verizon Samsung Galaxy S III] kerfex:
NilS

Thanks I give those a whirl.
[Verizon Samsung Galaxy S III] Magicman500:
Just flashed the 3.10 weekly. It's not recognizing my External SD Card. It can tell that there's one in there, but when I click "Mount," it fails instantly. I really want to use this ROM, but I need my SD Card!

I have a 64 GB SD card, if that matters. It shouldn't, though. I've never had a problem with it before.
[Verizon Samsung Galaxy S III] lvgdgts:
If you touch the clock on the lockscreen and pull down, it will show the notifications you have set up to display.
[Verizon Samsung Galaxy S III] flyestAC:
You don't even have to drag down. Go to security in settings and select widgets maximized and the will display for desk clock. Just choose which notifications you want in settings.
[Verizon Samsung Galaxy S III] kidruk:
no lag bro .. I do have a question though; I have been updating dirty and I don't have the kill all option in my recents. In my previous experience flashing dirty would bring any updates along with it. Am I going to have to do a clean flash here?

Edit: nevermind ;) ..
[Verizon Samsung Galaxy S III] SlimSnoopOS:
Pinch to zoom in/out to kill all recent with the SlimRecents open.
[Verizon Samsung Galaxy S III] gadgetguy08:
Bluetooth share hasn't crashed on me since the Build 3 release. Before that it was frequent.

I did remove the entry from the car side and re-paired at about the same time as Build 3 so that may have helped. Also did a clean install on Build 3.
[Verizon Samsung Galaxy S III] cstone1991:
Your S3 likely corrupted your SD card. It is a very common problem on many Samsung phones. Some have been able to recover the contents of the SD card, but most are forced to just do a low level reformat and lose everything that was on there. [rant]It will happen again eventually so don't bother storing anything important on your SD card going forward. I have 5 corrupted SD cards from this phone, all of which were used regularly in other phones without problems, I haven't even bothered attempting to recover them because it isn't worth it to put them in my phone again. From what I understand, this is a hardware issue that causes the SD card to unmount and then mount over and over and is not ROM related. This is the reason I will not buy another Samsung phone.[/rant]

Sent from my SCH-I535
[Verizon Samsung Galaxy S III] EatonZ:
So do we have any workaround for the SMS issue?

When I clean flash, it lets me send 1 before the rest fail with error code -1, same as CM 11.

If I flash CleanROM, everything works great, but I want to be on 4.4.:crying:
[Verizon Samsung Galaxy S III] SlimSnoopOS:
Seems like the only "confirmed but potentially still not 100% fix" is to follow these steps that are outlined in the CM11 unofficial thread OP. I have yet to try this cuz I've had a busy week with work. Been using Alliance rom for the last week. I may try this in a few days just not today.
[Verizon Samsung Galaxy S III] Magicman500:
Forgot to update my post, sorry! For some reason, Slim (and only Slim) doesn't like whatever file system my SD Card was formatted in (I honestly can't remember anymore). I backed up the contents and wiped it with TWRP, then it worked fine. Thanks for your help, though!
[Verizon Samsung Galaxy S III] Magicman500:
Would it be possible to disable the requirement to have SliePIE or the Navigation Bar on on the d2 version? I use my hardware buttons, but when I toggeld auto rotation on, it turned on the navigation bar, and now I can't turn both of them off.

Edit: Found the dimensions setting, sorry. I wish you could delete your own posts on here.
[Verizon Samsung Galaxy S III] GatorsUF:
I too am having issues with Bluetooth in my car, it crashes constantly. I remember this issue was common in all 4.4 ROMS when they first came out. It has been fixed in most of them somehow.
[Verizon Samsung Galaxy S III] kidruk:
Are you not running weeklies? I did do a clean install of 3.0 but now I'm on 3.10

Yea im on 3.10 as well. Dirty flashing and its all good. Just learned that the pinch in gesture kills all in recents.

My boOped s3!
[Verizon Samsung Galaxy S III] FastEddie422:
I am on 3.0 and I have crazy lag, too. Phone works great after a reboot but that only lasts for a little while before it starts to slow down heavily. This is with location off, app ops x controlling rogue permissions, and greenify stopping most apps that run in the background.

Before 3.0 I had 2.3 or around there and it wasn't nearly as bad but it definitely wasn't smooth. Thinking about switching ROMs because its getting unbearable at times.
[Verizon Samsung Galaxy S III] tvl76:
I recommend you flash 3.10, before you switch.
[Verizon Samsung Galaxy S III] kidruk:
I agree.. Your way behind lol.

My boOped s3!
[Verizon Samsung Galaxy S III] Flowah:
IS there a way to unreverse the hardware volume buttons?
[Verizon Samsung Galaxy S III] BattsNotIncld:
I was having a few lag/reboot issues during heavy use from recent weekly's, but 3.10 is running great. Buttery smooth and stable so far!

Have you tried running it without App Ops or Greenify? From my experience those kinds of apps tend to cause issues rather than solve them.
[Verizon Samsung Galaxy S III] draexo:
I'd question the source of the SD card. There is a huge counterfeit market especially on EBAY.

Sent from my Beanified S3!
[Verizon Samsung Galaxy S III] dpeeps74:
If you're referring to them being reversed in landscape, no. Just takes a little getting used to since side by side, right would be up.
[Verizon Samsung Galaxy S III] Flowah:
I used Slimkat for a couple months before I just grew tired of the volume buttons and went to CM11. I prefer Slimkat overall, but the hardware buttons are super annoying.

It's a little weird that it's not even an option.
[Verizon Samsung Galaxy S III] dpeeps74:
It was an option on JB. Can't say why it's not now or if it will be at some point.
[Verizon Samsung Galaxy S III] SwaySwayJoy:
Quick Question was the front facing camera issue fixed? I remember there being an issue where the imaged would be zoomed in up until the photo was taken.
[Verizon Samsung Galaxy S III] Magicman500:
I used the front facing camera the other day on 3.10. I didn't notice any problems.
[Verizon Samsung Galaxy S III] sweeds:
I just confirmed this happened on 3.10. Not a big deal in my books.

On the front facing camera, the view finder seems slightly zoomed in compared to the actual picture taken.

BTW, 3.10+Ktoonz running buttery smooth.
[Verizon Samsung Galaxy S III] draexo:
Any suggestions on which version to run? My main concerns are camera and blue tooth. 3.9 seemed to run fine for the few hours I had it running. 3.11 should be out today?

Sent from my Beanified S3!
[Verizon Samsung Galaxy S III] sweeds:
I've been on SK from 3.0 Stable -> 3.10 nightly. Current latest, but most weeklys drop in Monday so keep your eye on it.

I can highly recommend the latest weekly release. I run BT in my car, with home speakers, and pebble smartwatch all day. No problemo. The camera is stable and works as well as any AOSP ROM I've used.

I use it in conjunction with Ktoonz Kernel and it performances really well, zero lag.

My 2 cents.
[Verizon Samsung Galaxy S III] SlimSnoopOS:
Looks like Stable Build 4 was released today!

Edit: Gapps were posted too! I'll try running this but I'm already dreading the 1sms issue that's afflicted myself as well as others running AOSP roms.
[Verizon Samsung Galaxy S III] draexo:
I've had great luck using Philz recovery with is clean install option

Sent from my Beanified S3!
[Verizon Samsung Galaxy S III] Blaiser47:
Same here, couldnt install newest build 4, just stuck forever at kernel boot screen. Bummer, oh well back to 3.10
[Verizon Samsung Galaxy S III] draexo:
187 downloads. Someone have it working??

Sent from my Beanified S3!
[Verizon Samsung Galaxy S III] daturkel:
working for me just fine. only problem is dropbox won't work, here's my logcat http://pastebin.com/rqbkPqAa

already tried uninstalling and reinstalling, clearing data and cache, restoring from titanium, and rebooting. don't know what it is
[Verizon Samsung Galaxy S III] Magicman500:
Works great over here. I haven't had a single problem (Other than Slim coming with Superser instead of SuperSU, but that's just personal preference).
[Verizon Samsung Galaxy S III] draexo:
Oh man. I use drop box a lot.

Sent from my Beanified S3!
[Verizon Samsung Galaxy S III] Magicman500:
Dropbox working fine here.
[Verizon Samsung Galaxy S III] wizzardeel:
I got it to boot on clean install, but I have no touch functionality. Stuck at Welcome screen, can't touch anything.
[Verizon Samsung Galaxy S III] monkeyhihi:
Hey guys, I've got an issue that's probably a bit different from all of yours...

Every time that I wipe and install a new ROM, I have to redownload all of the music I chose to keep on my device from Google Play Music. Even when I choose in Play Music to download the music to my SD card, I still have the same issue. Does anybody know a way to preserve all of the music I download from Play Music so that I don't have to redownload it all after I update?

Thanks :D
[Verizon Samsung Galaxy S III] Blaiser47:
those of you that were able to get build 4 running, what did you flash with twrp or cwm? Any custom kernels or just stock? I ask because a re-downloaded and clean flashed again with twrp and still stuck at boot screen. I get stuck at first but screen, the one that doesn't fade in and out and is set by the kernel.
[Verizon Samsung Galaxy S III] kidruk:
Everything is fine on my end. Dirty flashed from 3.10 with no problems what so ever.

---------- Post added at 07:32 AM ---------- Previous post was at 07:27 AM ----------

I've been using CWM since my motorola droid X bro. I just can't make the switch... I'm old fashion. I am rocking the stock kernel for my first battery run but my plan to flash a kernel afterwards, either ktoonz or BMS.

Did you backup any previous builds?
[Verizon Samsung Galaxy S III] Blaiser47:
Yeah of course, I nandroided back. I'll try cwm now.
[Verizon Samsung Galaxy S III] kidruk:
Dirty flash right over that bad boy! I'm on a dirty.... no complaints here.
[Verizon Samsung Galaxy S III] Blaiser47:
Cwm still a no go for a clean flash, just get stuck at boot screen. So weird. Anyone get a CLEAN install to work with build 4? If so, recovery? Installed from SD, internal?

Edit: just tried to "dirty" flash but still manual wipe system per website directions and still just got stuck at book logo. So no matter what recovery, clean or dirty-ish, i can't get build 4 to boot. 3.10 for me for a while I guess but would love to know if others are able to get it booted with a clean or system wipe install.
[Verizon Samsung Galaxy S III] Magicman500:
I use TWRP. Make sure you're using the version right under the latest (2.6.3.1, I think). The latest version (2.7.0.0) has some problems. I dirty flashed from 3.10, with the recommended manual system wipe.
[Verizon Samsung Galaxy S III] AdMire:
I clean flashed Slim 4 this morning with TWRP 2.7.0.0 with no issues at all thus far.
[Verizon Samsung Galaxy S III] dbus08:
The first time I clean flashed and put lean kernel as well, had no wifi. Tried another two times and got boot looped. Just did regular clean install no new kernel and everything is working.

Flashed build 4 with twrp
[Verizon Samsung Galaxy S III] Blaiser47:
Weird, OK I'll mess around and try again
[Verizon Samsung Galaxy S III] draexo:
I installed v4 twice. First time I did a clean install with PhilZ recovery. First thing I noticed was my custom wallpaper had not changed, so I knew something had not been entirely cleaned. I proceeded anyways and started having issues pretty quick.

I did a SECOND clean install with PhilZ and it looks good so far. Got to love SLIM!

---------- Post added at 11:23 AM ---------- Previous post was at 11:23 AM ----------

Now that I am fairly confident the ROM is working, do we know which kernel works with the v4 release?
[Verizon Samsung Galaxy S III] Blaiser47:
Wow finally got it to boot, took forever at boot animation, and now this thing happened to me, can't touch screen just sits at welcome screen and nothing responds... wizzardeel, did you solve this?

Edit: definitely kernel related. Flashed BMS when I couldn't get touch functionality to work and boot time was fast, and could touch. Seems like there is something with the stock kernel that doesn't like my phone and possibly a few other peoples phones. up and running on build 4 now, thanks for those who confirmed it was working.
[Verizon Samsung Galaxy S III] wizzardeel:
Didnt try another kernel, but definitely will. Did it last night while watching Dexter and wife was complaining. Will clean flash today with dkp and see what happens. Thanks for trying out diff kernel.