yashsingh1/xdaforums huggingface dataset:
[Verizon Samsung Galaxy S III] OMG_VTEC:
saw something that cm10s 10/16 nightly has a working subway surfers...i know its silly but is there a way to see if that same fix can be applied here somehow?

other than that everything works great
[Verizon Samsung Galaxy S III] Obsession5:
Probably not the case but you might want to try re-downloading the ROM, maybe just a bad download.
[Verizon Samsung Galaxy S III] Juice3250:
I checked everything to make sure the rom was correct. A redownload likely wouldn't fix it. Anyhow, I installed cwm recovery using Rom Manager and my phone wouldn't boot up from it. I tried everything to get it to boot up. So I ended up reflashing the stock image from Odin. Now I think I'll stay on stock rooted debloated for a while and mess around with xposed framework mods.
[Verizon Samsung Galaxy S III] Blaiser47:
Did you format data too? If I have issues sometimes wiping won't fix it, I have to format as well to fix things.
[Verizon Samsung Galaxy S III] Juice3250:
Yes sir I did. I don't understand why they wouldn't reboot.
[Verizon Samsung Galaxy S III] Jayydude_SGP:
OK so I'm trying to get an LG G2 tomorrow... I need to disable audio completely so my stepmom will see this S3 is broken. The audio sometimes doesn't work unless I reboot the phone but when ever I want to show her it works. So I can I disable audio all together & drain the battery a lot?
[Verizon Samsung Galaxy S III] DerangedLoofah:
Just dunk it in water if you need it broken...
[Verizon Samsung Galaxy S III] dpeeps74:
So...apparently your parents can just buy you a phone and don't need to actually get it replaced through insurance? Go away. Get a job.

Sent from my Slim GS3
[Verizon Samsung Galaxy S III] Neverender326:
Lmao what a twit.
[Verizon Samsung Galaxy S III] Jayydude_SGP:
No, it's broken but oddly always acts flawless when I am around her. I'm not some spoiled brat, I lost my job & can't afford the insurance fee. You heartless prick. I am getting my own phone line she's just passing for the phone if I get it smh...
[Verizon Samsung Galaxy S III] dpeeps74:
Yes, I'm a heartless prick, and your step mom is the phone fairy.

Sent from my Slim GS3
[Verizon Samsung Galaxy S III] hexcorev2:
Lol you shouldn't come onto the forum asking for help to break your phone and then call someone a heartless prick. Also unless the problem relates directly to the ROM then no need to clutter the thread.
[Verizon Samsung Galaxy S III] omair2005:
Slim-d2vzw-4.3.build.1.9-WEEKLY-1271 is up!:good:
[Verizon Samsung Galaxy S III] SlimSnoopOS:
Appreciate that bruh! Looks like we have updated gapps too.

Edit: Hey all, do not flash a kernel dated from 10/19! Slim weekly 1.9 (as of this moment) does not have updated video drivers so its causing serious graphical tearing upon boot.
[Verizon Samsung Galaxy S III] griz.droidx:
I'm very sorry I don't understand. Maybe I should flash and see because I was going to anyway, but check here first. Do you mean not to flash a kernel from slim dated 10/19? I didn't know you guys posted kernels. Unless they were in the entire ROM file. So do you mean, don't flash 1.9 because of the video driver issue?

Sorry man, and thanks for the info I just don't understand.

Okay, the ROM on the slim site is date 10/20, I'm fairly sure this one is what I have since I got it about two hours ago, and it's what my filemanager says but I'm unsure of it's date and I never went to look at the actual properties of the file. Flashing Now....

Okay I must have the new driver. Yay. I'm looking for a replacement kernel, now that will be another trick, to see if any have been updated yet.. LOL

So the one that's up now should work. It's working on mine. So Far.

Saw this in the carbon thread.....

So were good I supppose. As I mentioned I must have one build from 10/20 because I downloaded today, and never even checked yesterday so I may not have see the 10/19 build.
[Verizon Samsung Galaxy S III] SlimSnoopOS:
Oh, no! I'm saying that nobody should try flashing a custom kernel (KT747, BMS, etc) dated 10/19 or newer. The rom itself is fine, I'm on SB 1.9 with 10/16 BMS Kernel. I don't believe SB has a separate custom kernel aside from what's included but someone from the SB team can correct me if I'm mistaken. I just know quite a few of us Slim Bean users (myself included) are using custom kernels and the warning is for those that do use custom kernels. Just want to avoid anyone posting in this thread that the rom is "broken" when that's not the case. It's missing commits that will cause immediate screen tearing that I guess were pushed yesterday (10/19).
[Verizon Samsung Galaxy S III] GideonX:
Slim has not pulled in the new CM video drivers. So for the weekly that just came out, do not flash any recently updated kernels (BMS, DKP, KT, etc.). These kernels have all been updated with the latest commits, which will cause video issues with Slim.

For the time being, flash an older build of the kernel of your choice. Do not use the latest one until Slim updates with the new commits.
[Verizon Samsung Galaxy S III] griz.droidx:
Thanks fellows I just figured it or thanks to you guys and me flashing the updated kernels. :). Thanks for the clarification. I'll flash one of the older ones. I flashed dkp and ktoonez. Neither would boot so CWM and a reflash fixed it right up. Thanks again. I understand now. Hope the updated drivers help on this device once we get them.

sent from a slim'd sgs3
[Verizon Samsung Galaxy S III] nicklovell23:
Sorry bout the issue guys I'll throw up a test build in a bit with our kernel swapped out and compiled with cm's. I didn't have time to get the kernel up to date before we ran weeklies my fault. Should be up in a few hours on my goo account nicklovell23.
[Verizon Samsung Galaxy S III] SlimSnoopOS:
Hey Nick, no need to apologize! Nothing you did is wrong cuz SB 1.9 by itself is great. Hope you didn't get that vibe from my post. Just wanted to post that, for others, to prevent your thread from getting cluttered. I, for one, absolutely love how stable this rom has been for me. You've been doing fantastic with these builds man.
[Verizon Samsung Galaxy S III] nicklovell23:
I appreciate that. I didn't take anything you said as bad lol just want to make sure you guys can take advantage of the updated kernels ;)
[Verizon Samsung Galaxy S III] Danvdh:
Have you been in contact with blk_jack nick for d2att-d2tmo? we are also experiencing this and I'm not quite sure if you can help us because he seems to be MIA :( is he ever in IRC because I can't ever catch him in there?
[Verizon Samsung Galaxy S III] nicklovell23:
Ok I compiled with CMs and still having some issues. I dont have any more time to play tonight so it may be a few days sorry.

[MENTION=4830253]Danvdh[/MENTION] I havent talked to him for awhile but you use the same kernel as we do so once its resolved it will be resolved for you as well...
[Verizon Samsung Galaxy S III] griz.droidx:
Me too man. Thanks for trying to put up a new one. But I'm in no hurry and as the other person said I hope I didn't come across bad or *****y. I know this stuff takes up your time and I don't expect you to drop everything just to tend to us sheep. That said thanks again for trying to get a new build up.

sent from a slim'd sgs3
[Verizon Samsung Galaxy S III] OMG_VTEC:
is there any way to fix mms? or does it only work from the factory mms? i tried with handcent and it would never send

it would kick data on for a minute but then kicks it back off and never sends
[Verizon Samsung Galaxy S III] tvl76:
I have been running custom kernels with slim for several months.

Out of curiosity, I decided to run with the stock kernal beginning with 1.8 and now 1.9.

I must say, the battery and performance for my use, are as good as with any of the customs I ran. (I mean NO disrespect to the kernel devs.)

Asswax / row.

Give it a try. (One or two or three less threads to occupy my time at work)
[Verizon Samsung Galaxy S III] griz.droidx:
I haven't sent any pics, but I have sent some extra long texts today on the 10/20 build without issue. Maybe someone else can chime in. Also, My app isn't set to convert from mms to sms as far as I know. The check box that says messages over 160 char. will be sent as multipart sms, Is this the same thing as mms? I've always wondered about that anyway. But just sending texts is working for me on the stock app, and again, they are usually extremely long.

Which build are you on? Did you wipe cache/data before you flashed?
[Verizon Samsung Galaxy S III] OMG_VTEC:
the zip says build 1 official 888. yes i did the wipe beforehand. im not playing in the nightlies cause the slim site is blocked at work.
[Verizon Samsung Galaxy S III] kentedman:
I dont use Handcent, but I've been using Sliding Messenger, Hello, and stock. All send MMS without issue for me. Have you monkeyed around with your APN settings ?
[Verizon Samsung Galaxy S III] bass0324:
I am trying to upgrade from 1.6 to 1.9 but I can't get passed the finishing boot message, am I missing something? The same thing happened when going from 1.6 to 1.8 last week.

Edit: seems as though I just needed to flash the rom first and then everything else
[Verizon Samsung Galaxy S III] Juice3250:
It took me a while to get this running but I have to say this ROM is pretty good. Not experiencing some of the signal or call quality issues that plagues other 4.3 Roms.

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

Had to use cwm touch recovery for it to work right.

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

Umm. Dialer keeps force closing. I installed the aroma gapps package. Should I flash the aio gapps and see if that fixes it?
[Verizon Samsung Galaxy S III] SlimSnoopOS:
Either reflash your gapps or clear data for the dialer. I prefer the minimal Slim gapps and have no FCs. I haven't had any FCs with the dialer after or during calls.
[Verizon Samsung Galaxy S III] d1ez3:
Only issue that I still have is bluetooth skipping, is everyone else experiencing this as well?
[Verizon Samsung Galaxy S III] Juice3250:
I clean flashed the ROM and slim aio gapps. No more dialer FC's. I think last time when I changed the LCD density that's when it started force closing. I followed all the steps to change it. I really don't like the 245 DPI. I'd rather change it to 320 but don't want to have the same fc issues. I hate clean flashing the same ROM over and over.

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

Okay. I think I know what I did wrong. I forgot to go to the last step to change the density to whatever you like and reboot. I changed it to 320 and now dialer works. :)
[Verizon Samsung Galaxy S III] Juice3250:
Frustrating.....dialer issues showed up after calling voicemail. Immediately when I hung up, it force closed. I cleared data and cache, rebooted. And still fc.

---------- Post added at 09:54 AM ---------- Previous post was at 09:45 AM ----------

Forgot to mention. I'm on the latest weekly build. 1.9. I'm switching to the official.
[Verizon Samsung Galaxy S III] SlimSnoopOS:
Hmm, that's unfortunate. Are you having any errors syncing contacts? I'm drawing a blank on why your dialer is FCing.

I'm not sure what you mean by "switching to the official"? Cuz this is as official as it gets. Do you mean the 4.2.2 builds?
[Verizon Samsung Galaxy S III] Juice3250:
Contacts sync fine. I flashed official build 1 instead of the weekly build 1.9. Still had issues so I went to another rom. Too frustrating and a waste of my time trying to get it to work.
[Verizon Samsung Galaxy S III] SlimSnoopOS:
Ahh, that's too bad.
[Verizon Samsung Galaxy S III] rbellis:
I'm trying to find a proper kernal to use with slim. I tried one but was in a bootloop butni can't remember the one I tried
[Verizon Samsung Galaxy S III] SlimSnoopOS:
Make sure your kernel is dated from October 16th or older. Say within the two weeks leading up to then.
[Verizon Samsung Galaxy S III] draexo:
Wow... I use Opendns and Slim is not blocked there.
[Verizon Samsung Galaxy S III] gadgetguy08:
I haven't had BT skipping with 1.9 or really any of the 4.3 versions. Used it today in car and a standalone BT speaker.

Could something be running in the background that is interrupting BT comm?

I did have BT connection issues twice yesterday with car audio, but it was fine today.
[Verizon Samsung Galaxy S III] nicklovell23:
I need someone who can thoroughly test BT.
[Verizon Samsung Galaxy S III] indyssee:
I use BT everyday through Ford Sync in my Escape and have no issues when it comes to streaming or phone calls. The only issue I have is that no system sounds will work until I reboot the phone. Its like its not being switched over to the headset speaker and still attempts to send to car speakers.

I'm sorry I wouldn't be a good one to test because I'll have no time today but hopefully that will help a little. The only other issue is that the signal seems to be getting progressively worse... Data and dBm info is basically the same from TW to AOSP but the call quality has dropped to where I can barely talk at my house now. I've seen that they have been working on this qcril stuff so hopefully it will improve.

Otherwise Slim is running great, as always. Thanks for being the Slim maintainer, Nick!
[Verizon Samsung Galaxy S III] Juice3250:
http://xdaforums.com/showthread.php?p=46734089
[Verizon Samsung Galaxy S III] Interflop:
I also use BT daily in my car's audio system. I'd be glad to test as well.
[Verizon Samsung Galaxy S III] Rrrracer:
Wow man that is the strangest thing. I don't dial into VM though, I use Google Voice instead and have no trouble whatsoever.

Don't know why it would make a difference but I flashed with regular old CWM non-touch; you mentioned you used Touch and TWRP. I couldn't get the rom to load with TWRP so I switched and voila, it worked. Might be worth a shot.

---------- Post added at 05:24 PM ---------- Previous post was at 05:21 PM ----------

I'm pleased to report that the issue I was having with BT on earlier iterations of Slim has finally been rectified! (screen off, streaming music would stop after a song was done playing; had to wake device to get it to start playing again).

I'm not having any skipping issues with my home system or car head unit, connects quickly and works great so far. I am getting text notification sounds over BT as well.

For me, it is near perfect now. After trying just about every other 4.3 rom out there, it's good to finally be home again.

Slim is fast, smooth, clean, feature-laden and yet lightweight, mature and stable.

Thank you Nick.
[Verizon Samsung Galaxy S III] Interflop:
I just flashed 1.9 and I'm not getting any push notifications. What's causing this?
[Verizon Samsung Galaxy S III] Juice3250:
Don't remember, but does this ROM have the music skipping bug on SD card music, not streaming? Also on LS I couldn't install drivers for viper. Does viper audio work on this ROM? Right now I'm on root box 4.2.2 but if I have any signal or call issues I will go back to a 4.3 ROM. For some reason the call quality was better on them than a couple of 4.2.2 ROMs I was on.
[Verizon Samsung Galaxy S III] Neverender326:
The new viper works on build 1.6 for me. It won't work on 4.3.1 builds
[Verizon Samsung Galaxy S III] Juice3250:
Wow! That was easier than I thought. I was using Super Backup and restoring my call logs across different ROMs. This is what was causing my dialer app to crash. All I did was go into the dialer app settings and looked at the permissions for the app and it just came to me. Maybe if I clear my call log it will work. So I did and immediately it worked. Didn't even have to reboot. Such a relief to know that the problems weren't with the ROM.
[Verizon Samsung Galaxy S III] SlimSnoopOS:
Man, I could yell at you lol
[Verizon Samsung Galaxy S III] Juice3250:
I'm doing enough yelling at myself for not figuring it out sooner. I spent a day and a half switching to three different AOSP ROMS and still didn't figure it out.
[Verizon Samsung Galaxy S III] SlimSnoopOS:
I'm glad you've got this all worked out though haha now's the time to dive head first into AOSP 4.3
[Verizon Samsung Galaxy S III] Juice3250:
Exactly what I'm gonna do.
[Verizon Samsung Galaxy S III] SlimSnoopOS:
Hey, if anyone is having trouble with Google sync today, its on Google's end according to a few articles here and here.
[Verizon Samsung Galaxy S III] SomeGuyDude:
Well that would explain why my apps didn't restore. Ah well!
[Verizon Samsung Galaxy S III] Stolly08:
Working flawlessly! Just installed the latest... Super quick and snappy! Love it!
[Verizon Samsung Galaxy S III] draexo:
How is Bluetooth?
[Verizon Samsung Galaxy S III] SlimSnoopOS:
I have only done a few BT calls and they were fine. Turning off BT is the same as other AOSP roms where it only turns off immediately if you turn off the BT device first. Idk about BT audio streaming.
[Verizon Samsung Galaxy S III] WettbackMartyr:
Bluetooth audio streaming is.... Well as good as can be expected on any AOSP ROM right now (Carbon at one point was the best for me, but I prefer Slim better overall) I do use bluetooth audio in my car and the skipping is intermittent. Hoping for the next stable release to fix it.
[Verizon Samsung Galaxy S III] griz.droidx:
The site says the new build should be r rolling out soon. I decided to try aTW rom to test signal strength. I'm in a low signal area and I can tell a difference. Anyone else in this predicament with signal issues. Again I know our ril isn't perfect but I really need the best signal possible. I prefer aosp roms preferably slim. Nut may Jane too stay with TW just for signal issues. I imagine the new build shield be in the stable section but I haven't seen it there or weekly yet. I'm sure it'll get there eventually.

sent from a slim'd sgs3
[Verizon Samsung Galaxy S III] SlimSnoopOS:
It's weird, I don't feel like I have noticeably worse signal on AOSP. I won't dispute that TW has better reception but for most, it just makes sense. I have always checked DBm on TW and AOSP and my signal is equally terrible on both lol I think I drop calls at about the same rate when I'm home on TW as I do AOSP which rarely makes me feel like I'm on VZW these days. For me, the tradeoff is insignificant but I imagine for others its more pronounced.
[Verizon Samsung Galaxy S III] indyssee:
I actually just tested this too. On TW and Slim the dBm and speed tests were almost identical. However, on AOSP, I have a lot of places in my house where I can't talk where I can on TW. Call me vain but its not enough to go back to TW, though.
[Verizon Samsung Galaxy S III] kenbrownstone:
The new fixes in masta builds seem to help signal as far as asop . But Tw have always had better signal on my phone
[Verizon Samsung Galaxy S III] SlimSnoopOS:
Those would be the qcril commits right? I keep up with Mastamoon's thread cuz I like reading the day to day comments about nightlies and commits posted. As someone who hasn't flashed that rom, some of these early comments by users about the qcril commits are promising.
[Verizon Samsung Galaxy S III] SlimSnoopOS:
Looks like stable build 2 official is UP! Thank you in advance [MENTION=4408910]nicklovell23[/MENTION]!

Edit: Gapps are posted simultaneously as well. Downloaded just in time for The Walking Dead, ha!
[Verizon Samsung Galaxy S III] shonalex:
Grabbing it. Doing a clean install this time. LOVE SLIM. excited for this one.

sent from my Galaxy S3 with Slim Bean Android
[Verizon Samsung Galaxy S III] griz.droidx:
I was going to let you guys know. But as many say on here. I got ninjered. Downloading now yay. Thanks Nick and all the slim team

sent from a slim'd sgs3
[Verizon Samsung Galaxy S III] TokedUp:
Thanks for build 2 can't wait to try it! Exciting news about Kit Kat! Thanks for all the hard work Nick!

WOW this new build 2 is awesome!
[Verizon Samsung Galaxy S III] Rrrracer:
On their changelog for D2 devices, it lists "Switch back to CM kernel". Does that mean it has the updated video drivers we need to run the latest BMS?
[Verizon Samsung Galaxy S III] Stolly08:
Ya I'm not gonna lie... DBMS blah blah I travel through the same areas every day on a 100 mile stretch and I get way better service on tw than aosp I don't care what anyone says, aosp only measures or reads lower that's how its made.... Bullsh#$... I'm an aosp guru I love the **** but going on and off between carbon, this, revolt and PAC vs moar... Moar kicks hard azz in comparison... Things load quicker and I get service in the aosp no service areas in the boonies.. So from an actually usability test over two months between tw an aosp, tw is stronger for signal... I don't care what anyone says...
[Verizon Samsung Galaxy S III] Danvdh:
You're quite wrong ;)

Check the smali in systemUI and compare with AOSP (STOCK FROM GOOGLE)

The carriers and touchwiz LIE ;)

yep :)
[Verizon Samsung Galaxy S III] Rrrracer:
If you were referring to my post, I was talking about the latest BMS kernel, not signal decibels...
[Verizon Samsung Galaxy S III] griz.droidx:
I haven't flashed this rom yet, but on every rom I've been on for the s3 it's been volume down and power button simultaneously. Or you could add it to the power menu in slim. I've been on the CM 4.3 for a while, and haven't had issues with themes. But it could be that I'm on the "right" themes. LOL. I'm usually on a mixer or cobalt theme. Haven't had the issue with either however.

Can't wait to flash slim. I was going to flash the orig release but read about camera and theme issues so I remained on CM. Really missing slim's customizations though.
[Verizon Samsung Galaxy S III] Thank Me Later:
Does this have "TRIM" implemented into it? Just like how 4.3 is on the Nexus devices?
[Verizon Samsung Galaxy S III] dunlap92:
I'm on this ROM...didn't flash extras....did flash gapps for cm 10.2 and had issues so I flashed slim gapps....running lean kernel 8 and have installed betterbeans theme from play store....also flashed temp camera fix from op...did have occasional phone.com popup at first....apply airplane mode and back off. Good to go.....running smotth

Sent from my SCH-I535
[Verizon Samsung Galaxy S III] dunlap92:
Sent from my SCH-I535
[Verizon Samsung Galaxy S III] m_s_ifland:
I gave you one back :good:
[Verizon Samsung Galaxy S III] ddurandSGS3:
easiest way is to enable it in the power menu if that option is availabe in this build
[Verizon Samsung Galaxy S III] griz.droidx:
Finally flashed the test build from the link provided some pages back. I'm getting the com.android.phone error that pops up every few seconds when the phone loses signal. This happened in CM on Mastamoon's 08-09 build, but not on 08-08 or 08-07. Haven't tried the newest CM nightly to see if it does it as well.

I'm going to try the newest unofficial CM nightly to see if it's doing the same thing. Thanks to Slim again, and to our new maintainer.
[Verizon Samsung Galaxy S III] annoyingduck:
Power+down at the same time. Instant screen shot of whatever is on the screen. Other ways you can't take a picture of say the notification bar expanded.... Simple and effective
[Verizon Samsung Galaxy S III] dunlap92:
Try turning airplane mode on for a minute or so...then off....I too experience this and its caused from low signal.....helps me.....goes away after a few minutes

Sent from my SCH-I535
[Verizon Samsung Galaxy S III] dbornack:
Why do people do this crap?
[Verizon Samsung Galaxy S III] MrBrady:
Running the 8/11 build. Its fantastic! But twice now the Phone keeps getting stuck at "Android is upgrading... starting apps" after making a change in one of the two Slim settings menus. Just wish I knew what setting is causing it so I don't have to keep doing a factory reset.

Edit: after doing a factory reset and going through the settings one by one with a reboot in between, I can't replicate the issue. It's happened twice already but I have no idea why.
[Verizon Samsung Galaxy S III] uberbdon:
The same reason people beg you to press the "thanks" button.
[Verizon Samsung Galaxy S III] Castanoff:
Thanked