yashsingh1/xdaforums huggingface dataset:
[Verizon Samsung Galaxy S III] t1n0m3n:
Still having Bluetooth issues with the new stable version. When I connect to my car, audio cuts out a lot, and the Bluetooth share app force closes. Same issue with most of the recent weeklies. I do a clean install every upgrade.

Eat at Joe's
[Verizon Samsung Galaxy S III] eksoccer99:
I used textdroider on co-workers s3. Worked just fine. [MENTION=2539186]320[/MENTION] default
[Verizon Samsung Galaxy S III] gadgetguy08:
With the stable build 3, my Bluetooth issues have vanished from what I can tell. I haven't had a long stint in the car yet, but driving to work I used to get the Bluetooth share app FC and haven't had that all week.

I did start having problems yesterday when I tried some other kernels, but with stock it was good.
[Verizon Samsung Galaxy S III] t1n0m3n:
Bah, camera bug is still there too. Oh well, off to try a different ROM. FYI Bluetooth in the car is the only place that the Bluetooth issue pops up for me. My BT heart monitor (Zephyr HxM) works fine on any previous version and the stable version.

Eat at Joe's
[Verizon Samsung Galaxy S III] KevinGee:
What issues did you have with the camera?
[Verizon Samsung Galaxy S III] S52Stu:
I have same issue. All cm bases ROMs. Kinda just waiting in hope its fixed or at least acknowledged.
[Verizon Samsung Galaxy S III] Bamdroid:
I just had to reply/thumbs up your Busta Rhymes quote! Lol
[Verizon Samsung Galaxy S III] jsmitty90:
Is this good?
[Verizon Samsung Galaxy S III] deuce237bblock:
Looks good! Stock kernel? Stock battery?
[Verizon Samsung Galaxy S III] jsmitty90:
Yes stock battery. But using the 2/6 BMS test kernal. And the battery is 2 years old
[Verizon Samsung Galaxy S III] deuce237bblock:
I would say that's pretty good battery life.

Sent by me.
[Verizon Samsung Galaxy S III] jsmitty90:
I thought so too. But I wanted to know if anyone agrees. I don't know other peoples averages. Thank you
[Verizon Samsung Galaxy S III] deuce237bblock:
No prob. I use a ZeroLemon battery with stock kernel (usually on BMS but that hasn't been updated to latest kernel version) and I can squeeze about 5-6 days on one battery cycle. I'm loving my Lemon Juice. :silly:
[Verizon Samsung Galaxy S III] PsiPhiDan:
Are we expecting a build tonight? Or no now that we've got the stable build?
[Verizon Samsung Galaxy S III] annoyingduck:
Don't delete the file, just move it from the downloads folder (I place my zips directly on the root of my sd after their downloaded) using a file manager, and see if that works. Also try clearing data from the downloads app. I'm sure a lot of people dirtied from beta 1 to 2 and this is the first I've heard of this. Obviously you can try a full clean install too...
[Verizon Samsung Galaxy S III] dbornack:
I'll try this for the sake of seeing if that works, and I'm sure it will, as it seems to just be the Download folder, but it's not a viable solution :)

I'll try this first, then download a file, move it, and report back.
[Verizon Samsung Galaxy S III] Dearborn1977:
Yup I think you're right. I'm running a custom kernel and it's been absolutely flawless and smoother than 4.2.2 ever was.
[Verizon Samsung Galaxy S III] Setco:
Hey I'm loving this ROM. I have the AIO gapps installed and I did a NAN Backup. I installed another ROM then did a clean recovery to Slim again. Now I have no Play Store. Tried to reinstall the gapps but no luck... Can anyone help? Looked through the threads but couldn't find anything pertaining to this problem. Thanks in advance!
[Verizon Samsung Galaxy S III] SlimSnoopOS:
I'd suggest dirty flashing the rom and 8/20 Slim gapps again. Then clean flashing if that fails.
[Verizon Samsung Galaxy S III] Rrrracer:
I figured I would hang out with the stock kernel for a couple of days to see how it worked, and so far I am impressed to say the least.

4.2.2 was pretty good for me, but 4.3 sure seems to be at least as smooth on a much more consistent basis. I was skeptical but the "underhood" changes to 4.3 are noticeable on the exterior. The thing is damn fast, all the time.

I'm also quite amazed at how stable it is. Much kudos to the Slim team and turbocharged thanks to Nicklovell23!
[Verizon Samsung Galaxy S III] samsgun357:
Beta 2 ran good with stock kernel but with BMS its freaking amazing!! If your good now on stock kernel a custom is gonna rock your rig!

Eat Play Google
[Verizon Samsung Galaxy S III] droidxxxxx:
How so just what does it do? Brush my teeth and comb my hair and all that.. an make me dinner? Lol
[Verizon Samsung Galaxy S III] KnappyRoot:
Loaded Slim Bean on my Gnex and it looked good so I tried loading it on my GS3. First flash the play store was not in my apps. Tried dirty flashing over original and still no play store. Did a clean flash and still no play store.

Possible bad download or any other idea as to why the play store not showing up?

Not device related as I'm running latest CM 10.2 nightly as I type this.
[Verizon Samsung Galaxy S III] uberbdon:
I did a quick search of the thread and didn't find a definitive answer so I'll go ahead and ask. I'm using the MB1 radio right now. Is this compatible with this version of Slim Rom or should I flash something else?
[Verizon Samsung Galaxy S III] idreamer24:
Did you flash the gapps?
[Verizon Samsung Galaxy S III] samsgun357:
For me it completely removed screen flicker. Plus you have the option to overclock the cpu, more governor and scheduler choices, gpu oc, sdcard read ahead (might be able to in stock), undervolting, init.d support etc.

MB1 should be fine, you can use any radio you'd like. If you get better signal on it than you do on MF1 than stay with it.

Eat Play Google
[Verizon Samsung Galaxy S III] KnappyRoot:
Yes. The AIO gapps each time.
[Verizon Samsung Galaxy S III] samsgun357:
Look in the zips, do you see vending.apk?

Also double check md5

Eat Play Google
[Verizon Samsung Galaxy S III] KnappyRoot:
I re-downloaded the ROM and both the gapps file. AIO and min gapps file have the vending.apk and the sha1 (md5) matches.

Does it matter if I flash from my SD card as opposed to my internal storage? Last time I tried from SD card so I will try internal this time.

Going to try flashing the ROM and AIO gapps file on lunch break. If that does not work, going to try ROM and min gapps.
[Verizon Samsung Galaxy S III] KnappyRoot:
Installed ROM and AIO gapps from internal storage and all is good. Maybe I had a bad download before. Thanks everyone for the suggestions.
[Verizon Samsung Galaxy S III] samsgun357:
I always put the zips on phone internal SD, that shouldn't make a difference though.

Question, are you manually formatting system before flashing by going to mounts and storage, format /system?

Here's another suggestion, if the playstore doesn't show up, use a root file app, I use root browser, extract the vending.apk from the zip. Then copy and paste it to /system/app, long press it and fix permissions to rw-r--r-- (644) and reboot.

Eat Play Google
[Verizon Samsung Galaxy S III] KnappyRoot:
I use TWRP and when I go to the advanced wipe, I select both cach, system, and data. I have never gone through mounts and storage.

Thanks for the suggestion. I was able to get it up and running by flashing the ROM and AIO gapps this afternoon.
[Verizon Samsung Galaxy S III] bsdesign0000:
i am running this rom and I am trying to change the LCD Density. But when I do, it keeps barking at me saying

"An Error Occurred.

Please check for root access. To activate go into superuser settings and enable root access"

I am confused... dont I have to be rooted to even install these custom roms? I am 99.99% sure my phone is rooted. I looked into my apps list, I dont see any superuser app for me to ajust anything?

The Slim Bean rom is super fast and smooth but i just dont like the tiny LCD Density.

Please advise
[Verizon Samsung Galaxy S III] annoyingduck:
Go into developer options/root access and change it to apps+adb
[Verizon Samsung Galaxy S III] SlimSnoopOS:
Not a clue. Regardless, I'm happy if nothing releases cuz I can finish a sitting of Walking Dead and True Detective without setting up my phone for once lol
[Verizon Samsung Galaxy S III] PsiPhiDan:
Ha ha true. I'm an avid Walking Dead follower but don't have HBO to try out True Detective. How is it?

I may need that show to replace Breaking Bad now that I'm fine catching up on that show. I hear True Detective is a good replacement, which says a lot!
[Verizon Samsung Galaxy S III] SlimSnoopOS:
I'll answer in the general section. Keep this thread devoid of off-topicness.
[Verizon Samsung Galaxy S III] dpeeps74:
Has double tapping the status bar always locked the phone in kk or is this new? I'm doing it on accident a lot!
[Verizon Samsung Galaxy S III] SlimSnoopOS:
Wooooow that's dope! Lol I never knew that was included!
[Verizon Samsung Galaxy S III] dpeeps74:
I've never noticed it til yesterday or the day before and since have accidentally locked the phone a handful of times. I do think it's a good feature just hate that I keep doing it on accident lol
[Verizon Samsung Galaxy S III] SlimSnoopOS:
I'm going to use the heck out of it now. Less wear and tear on the power button!
[Verizon Samsung Galaxy S III] d1ez3:
That's a cool feature. I actually turned my menu button into a screen off button (the hw power button wasn't working correctly) and I love the convenience of that only needing one finger to lock the screen. Of course this confuses anyone else trying to use my phone.. lol
[Verizon Samsung Galaxy S III] KevinGee:
Yeah that's something new that was added to aosp. It's a nice little feature that's sort of hidden.

But I remember having an option in PA to enable it but now it's pretty much enabled forever. Lol it's all good
[Verizon Samsung Galaxy S III] wizzardeel:
I am experiencing low volume when making calls in headset and on speaker. Like really low volume. I do have boost volume setting checked in Advanced-Device.
[Verizon Samsung Galaxy S III] d1ez3:
New 3.2 build is up for anyone who hasn't looked yet
[Verizon Samsung Galaxy S III] eksoccer99:
49 Downloads, must be that good w/ no reports yet. haha :D
[Verizon Samsung Galaxy S III] d1ez3:
Everything seems the same so far for me. I can't get the notification reminder to work, once I clear the current one I can't get a new one, it just disappears.
[Verizon Samsung Galaxy S III] gadgetguy08:
Under Settings / Wireless and Networks / More / Mobile Networks works now. It FC'ed in 3.0. Woo hoo.
[Verizon Samsung Galaxy S III] wizzardeel:
After taking a picture and swiping left to see the pic, the picture shows a little blurry but looks fine when zoomed and it also looks fine when opened in Gallery app by itself.
[Verizon Samsung Galaxy S III] SlimSnoopOS:
Are you referring to "Carrier Settings"? Cuz I'm still on a stable 3.0 and /Mobile Networks doesn't FC for me.
[Verizon Samsung Galaxy S III] deuce237bblock:
When your on a call and your experiencing low volume just press the volume down button then the volume up button. Fixes it for me.

Sent by me.
[Verizon Samsung Galaxy S III] gadgetguy08:
OK. Carrier Settings still FC's.

Too much flashing, I suppose. :silly:
[Verizon Samsung Galaxy S III] rmg88888888:
I know this has been asked before, but any chance this rom gets exfat support?
[Verizon Samsung Galaxy S III] ryanstfl:
I don't think that carrier settings will ever work for a Verizon phone, the ROM is AOSP based and I'm sure only a few GSM carriers would support that feature.
[Verizon Samsung Galaxy S III] Bamdroid:
Latest weekly build is a lot snappier than 3.0..(new kernel). Just my two cents.
[Verizon Samsung Galaxy S III] thorrules:
Can I dirty flash the new 3.2 build on the 3.0 build?

Sent from my Galaxy S3 (d2vzw) running Kitkat
[Verizon Samsung Galaxy S III] SlimSnoopOS:
You probably can. Just don't bother reporting any issues unless you did a clean flash first.
[Verizon Samsung Galaxy S III] robfromga:
Call volume is all messed up. Super low. Yes I checked the settings. Speaker is also not loud. Flashed back to a back up and its good...forward to 3.0 and its back low. Also I can't get my Bluetooth to link to my car.

Ideas ?
[Verizon Samsung Galaxy S III] EvoNotion:
So I did Safe Mode and that didn't fix it.

Here's what I've done since:

Gone to 4.4 Beta 3.2 update from last night - SMS Problem exists

Gone back to 4.4 Beat 2.1 - SMS Problem exists

Gone back to 4.3 Stable 2.2 -- SMS Problem exists

Gone to a Wicked Sensations 4.3 - Problem does not exist.

I did this all after a complete DATA FORMAT as well each time.

I am on ML1 Modem/base

Searching the interwebs, it appears that SMS in 4.4 is a major problem with many phones. Most use Hang-outs, but that doesn't seem to work for me either.

I can't be the only one having this issue on Slim.

Either way, thanks for looking out, I love Slim, but it gives me no love.
[Verizon Samsung Galaxy S III] eksoccer99:
Might have to do a factory Odin from scratch and reroot, etc. Start allll over.??
[Verizon Samsung Galaxy S III] Shakes The AssClown:
I performed a clean flash as per the instructions. Installed the newest weekly 3.2. It's working great with no issues so far. Great job team.
[Verizon Samsung Galaxy S III] EvoNotion:
What Firmware would you recommend going back to? MF1? or earlier?
[Verizon Samsung Galaxy S III] S52Stu:
Response

I am having the same problem.. I tried odin, but I also immediatly flashed the problem .zip that started the sms issue. I have been looking for a fix for a while. Apparently if you change to just cdma you have a work around, but the part that concerns me the most is the fact that old builds don't work now either...
[Verizon Samsung Galaxy S III] samsgun357:
When you guys have this issue are you using WiFi or is it when connected to data only or both? I'm curious if its some WiFi data handoff issue. I'm really baffled by this issue fellas but now I'm gonna put my sig into play and see what I can come up with.

Watch, as I combine all the juice from my mind...
[Verizon Samsung Galaxy S III] annoyingduck:
Yes, mf1 as it'll update all your partitions correctly without additional zips. Just do Not take the ota! Ask [MENTION=471697]slims[/MENTION]noop where the full .tar can be obtained as it's not directly linked in the Odin thread op's. I have it too if needed, but I can't upload it until later tonight. Before the 4.3 update we just odin flashed the b1 and took the mf1 update then re rooted + unlocked. Can't do that anymore!

-VZW LG G2 VS980
[Verizon Samsung Galaxy S III] EvoNotion:
For me, it's both on WiFi and LTE/CDMA
[Verizon Samsung Galaxy S III] SlimSnoopOS:
This VRBMF1 formats /sdcard. Backup your data to an external sdcard or computer then Odin flash. Like [MENTION=4795150]annoyingduck[/MENTION] says, don't accept the OTA after doing so.
[Verizon Samsung Galaxy S III] gadgetguy08:
My Bluetooth is working better than it has since 4.3.

You may want to delete the BT definition on the car and device and rebuild them.
[Verizon Samsung Galaxy S III] S52Stu:
Wifi or just data. If you reboot you can send one text . If you use airplane mode on off sometimes it let's you send one text.
[Verizon Samsung Galaxy S III] jsmitty90:
Any noticeable benefits updating to 3.2? My ROM and kernel finally settled in and battery is good
[Verizon Samsung Galaxy S III] deuce237bblock:
The only thing I noticed is seems to be more responsive and faster running ART. If 3.0 is running good for you I don't really see any need to update to 3.2.

Sent by me.
[Verizon Samsung Galaxy S III] wizzardeel:
Is ART the new kernel in 3.2?
[Verizon Samsung Galaxy S III] eksoccer99:
ART, is run-time. Or did you miss *in* the new kernel. ^^^
[Verizon Samsung Galaxy S III] thorrules:
Just google "ART vs Dalvik"

Sent from my Galaxy S3 (d2vzw) running Kitkat
[Verizon Samsung Galaxy S III] Droid316:
So any one had luck with a dirty flash on 3.2?

™Sent From My ™GUMMY™ KITKAT 4.42 Rom Running With ™Killjoy™ Script Powered By 7000MAH Of LEMON JUICE Power™
[Verizon Samsung Galaxy S III] countryfolk07:
I haven't noticed any to speak of. All you can do is backup, try it. If you do, do over with a clean flash.
[Verizon Samsung Galaxy S III] xbiker321:
Coming from LiquidSmooth.

Performed a clean install of SlimKat 3.2 Weekly, Slim_AIO_gapps.4.4.2.build.3

Everything smooth so far. Made a phone call, sounds fine. LTE data, SMS/MMS work.

Both front and rear camera / video recording works. Same with Instagram. Snapchat still has a warped from camera unfortunately (This has to be a problem on their side, I've had this issue with every 4.4.2 ROM and SnapChat).

I'll post if I find anything else wrong.

Netflix doesn't like this ROM
[Verizon Samsung Galaxy S III] tvl76:
I dirtied over 3.0. No problems. Find as good as ever.
[Verizon Samsung Galaxy S III] SlimSnoopOS:
Does anyone use a pin lock or secured lock? If so, do you also have the Messaging app as a slider target? Have you been prompted to enter your pin twice when dragging the target to unlock into the Messaging app? Once after dragging the Messaging target, it sits, then you have to drag it again and are prompted again for the pin?
[Verizon Samsung Galaxy S III] Obaterista93:
There is a thread in the Q&A section about this exact problem. Out of curiousity, are you two from Central PA? Everyone else affected by this seems to be in or around the 570 area code, myself included.
[Verizon Samsung Galaxy S III] EvoNotion:
Yes, actually the 717 area code. I'll check it out
[Verizon Samsung Galaxy S III] dpeeps74:
I am using pattern lock but I don't see this behavior when unlocking to messaging.
[Verizon Samsung Galaxy S III] SlimSnoopOS:
Hmm. I'll see if I can figure this out tonight with another clean flash and nothing installed.
[Verizon Samsung Galaxy S III] bass0324:
Do you happen to have a 570 area code?

Seems as though this was covered above :)
[Verizon Samsung Galaxy S III] samsgun357:
Very weird issue, I checked out that thread, I believe dex is from PA somewhere as is everyone, it seems, with this text issue. There must be a problem with vzw in that area and because aosp ROMs for our device are not official (the RIL is generic I think), something with that and the service is causing a problem. The thread said going to CDMA fixes the problem so that tells me its LTE specific. IIRC the band number that used to show in settings>about phone>status on aosp ROMs was 13 vs showing as 14 on TW ROMs. I'll continue to follow this as it has really peaked my interest.

Watch, as I combine all the juice from my mind...
[Verizon Samsung Galaxy S III] msternig:
I am having the same issue with MMS and Email notifications. I have tried to unlink the volumes as suggested as a fix, but when I use the Quick Toggles to switch between Sound and Vibrate Only modes, the notifications are still playing when in vibrate. I am using BMS since it seemed to fix an issue I had with Skype video recording. Can anyone else confirm that this is working for them and which version/kernel you are on? Thanks!

UPDATE: On previous ROMS back in 4.2(JB), there was an option on the volumes dialog to silence notifications, or treat notifications the same as the ringer (or something like that). It was different from the "link the ringer and notification" option. I no longer see this in KitKat.
[Verizon Samsung Galaxy S III] wizzardeel:
So is art runtime only on 3.2 weekly or does 3.0 has it also? From what i read art replaced dalvik in kitkat

---------- Post added at 06:39 PM ---------- Previous post was at 06:36 PM ----------

Well what I mean by fixed is that now I can manually silence notifications and it works. When I had them linked, I would put it on silent, bar all the way down, ringer would be silent but notifications still on. Quick Toggles only puts the ringer volume on vibrate or silent while the rest are whatever levels they were left last. You have to manually turn the levels down on notifications, alarm, media.
[Verizon Samsung Galaxy S III] msternig:
So is this really how KitKat is supposed to work? It seems odd that you can no longer hit a quick toggle that would change the ringer and notifications from being on (making noise so you can hear it), to being vibrate only (not making noise so I don't get in trouble in a business meeting). If this is indeed the case, I may be forced to switch back to JB or try to find an app that might help. Darn...
[Verizon Samsung Galaxy S III] eksoccer99:
ART hasn't quiet replaced dalvik cache. its there for you to try.

hasn't been updated in awhile not sure if it still works, see an app called, "real silent". or some thing similar??

https://play.google.com/store/apps/details?id=net.geekherd.realsilent&hl=en
[Verizon Samsung Galaxy S III] msternig:
Thanks for the recommendation on the silent app. I am still hoping that I am just missing something really stupid in the settings someplace. Other than this little issue, I find this ROM to be perfect.
[Verizon Samsung Galaxy S III] SlimSnoopOS:
My QuickSettings toggle works fine for vibrate. Just got a text which vibrated just before typing this. I only hear sounds when on Sound & vibrate. My QS Sound tile modes are: silent, sound and vibrate, vibrate. No issues yesterday with this specific sound inquiry while I was at work yesterday. I have not attempted to unlink sound, it's not something I have a need to do.
[Verizon Samsung Galaxy S III] msternig:
Just to clarify, on the Settings > Sound > Volumes dialog, you have the box checked next to "Link ringtone & notification volumes", correct? What do you have your volume panel style set to in Settings > Sound? I have mine at "expanded", but am still seeing (or rather hearing) the issue when toggling to "vibrate".
[Verizon Samsung Galaxy S III] SlimSnoopOS:
Yes, "link ringtone & notification volumes" is enabled. My Settings/Sound is set to the default of "Expandable," idk know what it does honestly. I only receive texts and emails, haven't heard any notifications for either of those when on vibrate. I keep my phone in vibrate often cuz I'm usually in a library.
[Verizon Samsung Galaxy S III] msternig:
I have mine set the same as you described, and still am hearing notification sounds despite being on vibrate. When I expand the volumes panel, I can see that my notifications are set to vibrate (according to the icon next to it), but the volume level is still half way up. My ringer on the other hand shows the vibrate icon and the volume all the way down. At a loss...
[Verizon Samsung Galaxy S III] iballen93:
I've been running the 3.0 stable for a few hours and just can't seem to get root access. I've tried Superuser and SuperSU. Both have failed. I'm trying to use my titanium backup but it can't get root access.

Does anyone have some ideas to fix this problem?
[Verizon Samsung Galaxy S III] SlimSnoopOS:
Have you enabled "root and adb" in Developer Options? I make it a point to flash SlimKat build xyz, gapps, then SuperSU in one session them boot up.

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

This is off a clean flash (data and system wipe)? Mine has always worked properly, regardless of stock, BMS, or KT kernel being installed as well. I only change my ringtone sound, notification ringtone, and deselect Touch Sounds and Screen lock sounds in fresh boot. Everything else is stock.

Edit: Anyone get the newly released Google Now Launcher to install for them and work? It installs but says I need a newer Search app which doesn't change after a reinstall of that specific app. My search is v3.2.17.1009776.arm. Just curious to test it out.

Edit x2: per [MENTION=4959456]thesoldier[/MENTION], GNL does in fact work if you install or convert the GNL app to a system app!
[Verizon Samsung Galaxy S III] iballen93:
Thank you so much Snoop. It's been awhile since I've flashed a new ROM and totally forgot about developer option. Thank you now my phone is complete

BTW do you know if there is a way to change grid size on the google now launcher? The launcher doesn't seem to have many tweaks. Last thing is when holding down home and looking at recent there is no clear all button. Is it just not incorporated in this build?
[Verizon Samsung Galaxy S III] Blaiser47:
I just got the new launcher from the play store, asked to update the current one included with the rom and seems to still work fine.