yashsingh1/xdaforums huggingface dataset:
[Verizon Samsung Galaxy S III] tvl76:
Just flashed latest BMS, same camera issues.
[Verizon Samsung Galaxy S III] beepea206:
He did. 12/15 fixed a previous break in the camera, caused by an ealier build. :)

CM is a damn mess... no way in Hell I'd flash that rom with so many solid AOSPs out there.
[Verizon Samsung Galaxy S III] gadgetguy08:
Now camera crashed my phone running 1.7 even with new BMS.
[Verizon Samsung Galaxy S III] ProtheusIRC:
Any way to use the TW messaging app with this ROM?
[Verizon Samsung Galaxy S III] SlimSnoopOS:
I'm sure this will get figured out quickly. It's commit related if I had to guess.

Out of curiosity, why would you want to do this?
[Verizon Samsung Galaxy S III] xdreaper15:
What's my best option for making JUST the GEL stock DPI. I love the phone being in the current DPI, but my icons look dumb. Even with custom icons some of them aren't themed and it just looks ridiculous.
[Verizon Samsung Galaxy S III] ProtheusIRC:
Because every AOSP/CM ROM I flash I can't send texts. I can receive texts and data and MMS work fine. Every time I send a message it says Message not sent. Touch to retry. Custom stock Roms work fine.
[Verizon Samsung Galaxy S III] nicklovell23:
Just to let you guys know I'm trying to pin down the cam issues. I'm experiencing it as well. I'll keep you all posted.
[Verizon Samsung Galaxy S III] SlimSnoopOS:
Hmm, is that so? Which firmware are you using in Settings/About Phone/Baseband?
[Verizon Samsung Galaxy S III] ProtheusIRC:
I'm on MF1.
[Verizon Samsung Galaxy S III] annoyingduck:
You've got something else going on, messaging is fine here... Tested on multiple platforms too..
[Verizon Samsung Galaxy S III] ProtheusIRC:
I never said it was a problem with this ROM. I specifically stated in my first reply that this happens on all AOSP/CM Roms.
[Verizon Samsung Galaxy S III] SlimSnoopOS:
No issues anywhere else either (calls or data)? That's just odd. Does the same go for JB and KitKat?

To answer your question, I don't believe there is an easy way to get TW mms on an AOSP rom. I know there was a ported AOSP mms mod for TW roms but I believe the person responsible for it decompiled/recompiled the app itself. There's no guarantee it would work and there's no quick and easy method at that. TW anything usually doesn't work on AOSP.
[Verizon Samsung Galaxy S III] ProtheusIRC:
Calls and data work fine. It's just outgoing SMS and MMS. KitKat and JB do the same thing. Idk what's wrong with it. Custom stock roms like jellybeans and bonestock work fine.
[Verizon Samsung Galaxy S III] carpdeeem:
As I always try to remember to start when posting, thanks so much to everybody working on this ROM. I really appreciate having such a solid OS that also satisfies my desire for the latest and greatest.

I've been running 4.4 beta 1.6 since last week and found two issues. For the first time, I'm having the Bluetooth trouble that others I believe were describing for older versions of the ROM. When I connect to my SmartMini Aux for the first time, the connection is smooth. Well after the car and Bluetooth receiver power off, the phone indicates that Bluetooth is still connected. Then when I power the device back on, the audio connection cuts in and out every second. Seems to be resolved each time with a combination of reboots, but becomes choppy again after disconnecting. Just turning Bluetooth off and on doesn't help.

Other thing I've noticed is that the stock camera seems to autofocus much more slowly than it did in SlimBean (last version I used was 2.1). Time from opening the camera app to taking a first picture seems much longer. I may be off on this one - anybody else notice the same thing?

Thanks again!
[Verizon Samsung Galaxy S III] beepea206:
You need to mention you're trying to do all this on a gsm connection. That kind of information is important to mention, since this phone, and rom/forum, is for Verizon and we're not gsm.

Like I said in the other thread, the RILs for this device are based off cm pulls, so all aosp and cm roms will give you the same issue, while stock will work.
[Verizon Samsung Galaxy S III] ProtheusIRC:
Here again is another person who assumes. I have a VERIZON GS3. Yes, I use it on a GSM connection but I'm fairly certain that would have no bearing on my problem. Thanks for trying to be an asshole though.
[Verizon Samsung Galaxy S III] SlimSnoopOS:
Huh? I had to look at the other users' recent post history to see what you meant by that.

Have you tried editing the APNs to match that of your GSM carrier?
[Verizon Samsung Galaxy S III] ProtheusIRC:
Yes of course.
[Verizon Samsung Galaxy S III] beepea206:
You're the one that came here and gave half the info, but said it didn't work. Gsm is VERY important to note, because the device the files were pulled from determine how it will work. If it's a cdma only device, Gsm won't work and vice versa. I'm not being an asshole, I'm speaking from experience with global phones and trying to get them to work with cm and aosp (the Droid 2 global). Gsm use of the s3 is not standard, so mention it when trouble shooting.
[Verizon Samsung Galaxy S III] Stranger_84:
Been awhile since I've been back to slimrom but hearing great things about the 4.4 betas ... Anyone recommend the best weekly or should I go for the most recent??? Thanks in advance
[Verizon Samsung Galaxy S III] shonalex:
Totally agree. And that guy has no ground to stand on to call you an ahole. CDMA and gsm are different and I believe that information would be important to know.
[Verizon Samsung Galaxy S III] tvl76:
I dropped back to 1.6. (Camera issue on 1.7)
[Verizon Samsung Galaxy S III] SlimSnoopOS:
Well [MENTION=3783550]kentedman[/MENTION] [MENTION=2681414]Rrrracer[/MENTION] [MENTION=5156561]Setco[/MENTION] [MENTION=3821588]beepea206[/MENTION] [MENTION=3716951]griz.droidx[/MENTION], y'all can consider me a convert to 280 DPI lol after taking y'all advice last week I noticed I actually prefer my DPI at this level.
[Verizon Samsung Galaxy S III] beepea206:
lol! I don't mind the lower DPI, but I kept having issues hitting the nav bar targets when it's that small. Making the nav bar larger to offset the lower DPI made it huge. ha.
[Verizon Samsung Galaxy S III] SlimSnoopOS:
Everything I utilize just seems unreasonably large on 320 now lol

Speaking of nav bar, do you notice any issues with yours? I don't think I have any issues but I notice some lag or spontaneous behavior when I press the multitasking or last app keys. It's mostly working fine and I don't think its any different or working less than in SlimBean.
[Verizon Samsung Galaxy S III] beepea206:
Just what you mentioned... a tiny bit of a lag pulling up last apps. I don't know that's related to the bar, though... possibly calling up the cache?
[Verizon Samsung Galaxy S III] SlimSnoopOS:
Yea, you're probably right. I use the last app soft key a lot and I don't really notice any issues consistently
[Verizon Samsung Galaxy S III] kentedman:
By the way. The slimkat 4.4 beta is the only ROM I've found that uses the "less intrusive" incoming call setting (I think its a pull from the N5?). I haven't seen it mentioned anywhere but its a great little feature.
[Verizon Samsung Galaxy S III] flyestAC:
I agree. It's included in [MENTION=3128576]notta[/MENTION]'s 12/15 build I'm playing around with right now and I thought my phone was tripping at first lol. Awesome new little tweak.
[Verizon Samsung Galaxy S III] TokedUp:
How do we go about using this less intrusive setting?
[Verizon Samsung Galaxy S III] SlimSnoopOS:
It's on by default and I'm glad someone else mentioned it's really cool too! I actually prefer it like this. When someone calls you, the call just pops up at the bottom to answer or decline instead of taking over your display. If it's somehow not on by default, go into Phone settings and turn it on.
[Verizon Samsung Galaxy S III] TokedUp:
I can't find the option in settings. Maybe its because Im using the Google dialer with search?
[Verizon Samsung Galaxy S III] Rrrracer:
OK now I am getting jealous :) I wish I could figure out how to fix tethering so I could join you guys!
[Verizon Samsung Galaxy S III] SlimSnoopOS:
Idk but I see the option and I'm using the included dialer and Slim minimal gapps FWIW.
[Verizon Samsung Galaxy S III] TokedUp:
Yeah that option is not in the Google Dialer. Oh well. I use the search feature to much to change. My friends are all jealous of that feature. I like to show it off lol
[Verizon Samsung Galaxy S III] SlimSnoopOS:
I keep seeing people mention this Google Dialer so maybe I need to see what it is haha does it come with KitKat? I wouldn't install it though cuz I don't use the dialer much.

Edit: btw, if y'all are in the Christmas spirit open up google now and say "OK Google...let's go caroling." Courtesy of every android blog that published this.
[Verizon Samsung Galaxy S III] deuce237bblock:
I love Christmas music! :)
[Verizon Samsung Galaxy S III] SlimSnoopOS:
It's subtle, yet cool!
[Verizon Samsung Galaxy S III] Neverender326:
Anyone having probs with WiFi on 1.7 slimkat? It seems to not pick up on a new network after I scan. Its a work network so should be available

---------- Post added at 02:57 PM ---------- Previous post was at 02:51 PM ----------

Grrr won't let me edit...the above was a clean flash it picked up my network at home just fine but not the work network. Tried to manually enter the said but no luck. The ssid will not show up in WiFi settings
[Verizon Samsung Galaxy S III] d1ez3:
My wifi didn't work at all on 1.7, had to go back to 2.2 stable for now
[Verizon Samsung Galaxy S III] tvl76:
My only prob with 1.7 was the camera. I'm back on 1.6, runs flawless.
[Verizon Samsung Galaxy S III] SlimSnoopOS:
Is anyone else's call volume extremely low on SlimKat beta 1.7? Mine seems to alternate between normal and very low on different calls. This includes the speakerphone, when the call sound is low then the speakerphone sounds extremely low as well. I rebooted and call volume sounded fine while turned up then the next call it dropped down. Also, I can listen to a podcast (via Antennapod) which plays from the speakerphone and it sounds perfectly fine so its not my speakerphone. Even noticed that while listening to my podcast, I received a call and the call volume was very low and then when the call ended my podcast app resumed playing and that was loud as it should be.
[Verizon Samsung Galaxy S III] deuce237bblock:
I have noticed this too, I use the xposed module xvolume. It helps a little bit but sometimes the sound gets really low.
[Verizon Samsung Galaxy S III] FastEddie422:
I feel like the call volume in 1.6 is even lower than I'm used to in 4.3 and before but I haven't tried 1.7 yet.
[Verizon Samsung Galaxy S III] SlimSnoopOS:
This wasn't happening on older builds for me. Its a very obvious difference in sound quality. This was a surprise to me cuz I had replaced my speakerphone about a month ago so I had thought it was messing up already but its only phone calls. Even managed to eek out a 30 minute phone call earlier where it seemed like switching to speakerphone made the sound volume get lower. I've started, stopped, and resumed my podcast app and there's no issue with that.

I'm wondering if this has anything to do with the purported Verizon data outage today? I hadn't noticed this before today and I have had build 1.7 installed since release.
[Verizon Samsung Galaxy S III] annoyingduck:
I restored my slim 1.7 nandroid after being on cm11 for a few days... It's amazing how the battery life is on slim, it's like 2 different world's.

If you don't already have it, I highly recommend kroz's custom slim kk wallpaper...

https://plus.google.com/105240510340160263809/posts/5M9WsRR7Gn2
[Verizon Samsung Galaxy S III] SlimSnoopOS:
You always have the inside scoop on really dope SlimKat wallpapers lol where is the blue SlimKat wallpaper stored? I might install this one you linked but want to keep the SlimKat blue in my downloads.
[Verizon Samsung Galaxy S III] annoyingduck:
I can't find it... It's usually data/system/users/0/wallpaper..., but on my n7 running 1.7 the default blue slim is included in the wallpaper chooser...

I can't find it on my n7 either to extract it, need some time to dig
[Verizon Samsung Galaxy S III] SlimSnoopOS:
Yea it's hidden pretty well. That one you posted is slick as well man. Almost makes me want to switch my softkeys away from blue to match.
[Verizon Samsung Galaxy S III] annoyingduck:
I'm addicted to the black/white kk look - (that looks weird to write!!)

I flashed a 4.3 build the other day and cringed when I saw the status bar.

This wallpaper is driving me nuts, I'm looking everywhere... I'm assuming kk has changed the old hiding spots around?
[Verizon Samsung Galaxy S III] SlimSnoopOS:
lmao...I'm warming up to the move to a white theme but I'm still partial towards holo blue particularly for QuickSettings. Either KitKat changed up the spots or the Slim team has become very crafty.
[Verizon Samsung Galaxy S III] annoyingduck:
I'm having issues... After digging around, in root Explorer my default internal storage (just called storage) now has a 0 folder that has some of my missing items in it that would usually just be in the root storage... Wtf? How did a 0 folder just get magically created, and why is only some stuff there?
[Verizon Samsung Galaxy S III] TokedUp:
I had to extract a wallpaper the other day from framework/Framework-res.apk. Might be in there? I used APKTool
[Verizon Samsung Galaxy S III] countryfolk07:
This is where it should be for system default backgrounds.
[Verizon Samsung Galaxy S III] SlimSnoopOS:
Hmm, guess I'll check that out. Off the top, do you know if it works on Mac? It's a command line like tool, right? I've seen a thread for it before but didn't give it any attention. I'll find it later today.
[Verizon Samsung Galaxy S III] annoyingduck:
If it's there, it's buried... I can't find it. You can use root Explorer to examine it. System/framework/framework res.apk. Tap it and choose view (not install!)
[Verizon Samsung Galaxy S III] deuce237bblock:
I miss dark slim. :(
[Verizon Samsung Galaxy S III] david_hume:
You do realize that every AOSP ROM is based off of CM.... Right? LOL!
[Verizon Samsung Galaxy S III] annoyingduck:
Before you get completely destroyed here, I'll be kind.

That's a big no. Cm is based on aosp, not the other way around. And no on every aosp being based on cm. Original development is built from scratch from aosp. When a base is used like cm, slim, or aokp (the 3 popular bases), it becomes classified under development, not original. A true(er) statement would be that all roms are based on aosp...
[Verizon Samsung Galaxy S III] o0BlacknesS0o:
The absurdity of this statement makes me wanna Lol and cry at the same time...
[Verizon Samsung Galaxy S III] TokedUp:
Yeah it's not the first crazy post I've seen from that guy
[Verizon Samsung Galaxy S III] liquidnails:
Wow...lmao!
[Verizon Samsung Galaxy S III] beepea206:
You've got that backwards, man. Cm is a modified version of aosp. All the aosp builds out use the cm device a day hardware repos, but they have no cm-modified framework. The most pure aosp rom right now is gummy, because it uses a custom kernel, whereas the other aosp-based builds use the cm kernel.
[Verizon Samsung Galaxy S III] david_hume:
I should've corrected that post. *facepalm.

I meant to say most AOSP ROMs here, but in my stupidity, I said all. Lol
[Verizon Samsung Galaxy S III] shonalex:
1.8 posted. Trying it out now.
[Verizon Samsung Galaxy S III] d1ez3:
When you get it installed please let me know if there is hardware key modifying and if the cameras are stable.
[Verizon Samsung Galaxy S III] carpdeeem:
Wondering if there have been any Bluetooth fixes? Looked in the changelog for 1.8 and saw nothing specific about Bluetooth. I've had trouble with 1.6 & 1.7 where I can connect to my Bluetooth device (SmartMini Aux) successfully the first time, but then can't reconnect without serious messing around (and haven't been able to identify the correct recipe). Anybody else having trouble and / or have a fix?
[Verizon Samsung Galaxy S III] countryfolk07:
Stock messaging app doesn't seem to send MMS. Seems doing a compass calibration in maps, force closes it. That's all I got so far. Otherwise smooth. I've been missing Slim. Thanks devs!
[Verizon Samsung Galaxy S III] annoyingduck:
Guys, they are pushing rebuilds now to 1.9...missing merges. Our device should be up shortly
[Verizon Samsung Galaxy S III] shonalex:
Well I did a dirty flash from 1.6 to 1.8, and the camera doesn't work. U can get one pic out of it then freezes up.

They added TRDS to the slim settings. Nice! Appears to be working.

There isn't an option to change the hardware keys that I could find. Hope that helped you.

Maybe it needs a clean flash, but I just dirtied back to 1.6 and all seems well again. 1.6 is really good. I've enjoyed the heck out of it.

---------- Post added at 02:32 PM ---------- Previous post was at 02:28 PM ----------

Oh, cool. I was wondering what was up with 1.8. Must've been a mistake.
[Verizon Samsung Galaxy S III] annoyingduck:
Clean flash required!!
[Verizon Samsung Galaxy S III] ryanstfl:
You can modify the hardware keys go to

/system/usr/keylayout/sec_touchkey.kl

Swap the back and menu button or whatever you want. Done.
[Verizon Samsung Galaxy S III] shonalex:
OK. I thought we were ok to dirty between slim builds. As long as they are all 4.4.
[Verizon Samsung Galaxy S III] countryfolk07:
Ugh. Really? I literally JUST flashed 1.8. Looks like I need to charge the battery. LOL.
[Verizon Samsung Galaxy S III] :
Most of the time you would be but they are saying clean this time because there were so many changes.
[Verizon Samsung Galaxy S III] SlimSnoopOS:
I took a look at the 1.8 changelog, can any tell if they Slim is up to date on the cm kernel? I didn't see any commits that stood out to me about in-call volume either.
[Verizon Samsung Galaxy S III] :
Could be it was part of the merge problem? 1.9 just showed up, maybe it's in that changelog?
[Verizon Samsung Galaxy S III] nicklovell23:
We use CM kernel so its synced as of today.
[Verizon Samsung Galaxy S III] SlimSnoopOS:
I'll try it in a couple hours. Did y'all get the camera fixed as well? On 1.7 it would only take a single photo then instantly freeze.
[Verizon Samsung Galaxy S III] annoyingduck:
Bad news on that front, camera seems to be worse. It gets all graphically pixilated and eventually freezes up...so sad, I just got finished setting everything up...

Other than that it's fantastic.... Clearly stronger than 1.7. Trds is not theming any Google Apps though, just some system ones.
[Verizon Samsung Galaxy S III] TokedUp:
Try the modded AOSP camera until it's fixed. Also I have a thread for a dark theme MMS file in the apps section. And if ur using the Google dialer there's a link to a dark theme for that as well. Hangouts and contacts dark theme apps r on the way.
[Verizon Samsung Galaxy S III] annoyingduck:
Dark google dialer theme?...

Please link
[Verizon Samsung Galaxy S III] tvl76:
Link to the camera?
[Verizon Samsung Galaxy S III] annoyingduck:
OK, found it...

That modded dialer is f+++ing awesome!
[Verizon Samsung Galaxy S III] SlimSnoopOS:
Appreciate the input man. Maybe it's cuz this is the holiday season but I haven't had much reason to use my camera until the last few weeks lol I'll still run 1.9 in a few. Waiting on the charge as I type this.
[Verizon Samsung Galaxy S III] ryanstfl:
What's the status on voice+ integration? I can send you the apk if you don't feel like downloading cyanogen just for the apk. I need voice+ or else I can't install...
[Verizon Samsung Galaxy S III] TokedUp:
Yeah that dark themed google dialer is the shiznit! Im loving the MMS too. It can hold us over until we get Dark Slim. When Hangouts and Contacts are done I'll make sure to let you guys know, that is unless Dark Slim isnt out by then.

Themed Google Dialer (must have Google Dialer installed before flashing the theme):

http://xdaforums.com/show....php?t=2576791

Modded AOSP Camera:

http://xdaforums.com/showthread.php?t=2408345

If you like, please hit the thanks button! Happy Holidays guys!
[Verizon Samsung Galaxy S III] samsgun357:
Does 4.4 have the slim dark ui?

Its only weird if it doesn't work!
[Verizon Samsung Galaxy S III] SlimSnoopOS:
Absolutely! :good: AND SlimKat 1.9 has many more features back! I'm personally glad to see Advanced Options/Device/Color Temperature is back among other things.
[Verizon Samsung Galaxy S III] deuce237bblock:
I finally have power again after 2 days without power because of the ice storm. So excited for 1.9, don't really use the camera so I'm not worried about that.
[Verizon Samsung Galaxy S III] SlimSnoopOS:
That's tough, hope you had an external battery charger just for emergencies such as that.
[Verizon Samsung Galaxy S III] indyssee:
Any word on when WiFi tethering might work? I can't wait to make Slim my daily but I rely on tethering too much. It works on CyanFox and Gummy so hopefully it make it here soon.

Anyway, nice work on 1.9 Nick. Slim is coming along nicely.
[Verizon Samsung Galaxy S III] Stranger_84:
Anyone else having connectivity issues with WiFi on 1.9?
[Verizon Samsung Galaxy S III] SlimSnoopOS:
I don't use it normally so idk if I'm doing something wrong but neither my iPod or MBP can find my S3. I tried no security, WPA-PSK, and WPA2-PSK to no avail. None can find my network regardless of the name I set. Can anyone else confirm?

Edit: I'll try again with 4.4.2 gapps and clean install to be thorough.

Wifi seems fine to me. Are you on VRBMF1 firmware?

Btw, looks like 4.4.2 Slim Gapps were posted today!

Edit: I already have the 4.4.1 beta 1.5 gapps installed, so do I wipe cache then install newer gapps? I'm used to flashing clean each time. Gonna flash and see either way.
[Verizon Samsung Galaxy S III] tvl76:
This camera didn't work for me.

I'm afraid I need to drop back to 1.6 again...Need the camera, especially this time of year !!
[Verizon Samsung Galaxy S III] Beeko:
Am I the only one that can't find the performance settings on the ROM? I have the developer setting enabled but no performance settings.
[Verizon Samsung Galaxy S III] dpeeps74:
Don't think they're added back yet. I'm using rom toolbox to set the cpu.
[Verizon Samsung Galaxy S III] TokedUp:
That's the first time hearing it didn't work. Did u follow instructions completely? Did u delete the original camera and gallery? What exactly didn't work?
[Verizon Samsung Galaxy S III] beepea206:
I forget who it was, but the data/wifi handoff issue... anyone know if it's resolved from previous builds?
[Verizon Samsung Galaxy S III] tvl76:
Did not delete original, renamed gallery2.apk to gallery2.apk.bak.

Copied the 3d apk to system and installed.

What I did not do was reboot, before trying it out.

I'll try it again and reboot this time and let you know
[Verizon Samsung Galaxy S III] tvl76:
Well..trouble in river city.

I restored my 1.9 backup and now the phone will not boot. Gets to the breathing slimkat logo and goes no further.

After battery pull at the recovery menu, If I try to wipe, it reboots before finishing the wipe.

I tried flashing the rom over top again and I get the same reboot - boot loop.

I got started up again by restoring my 1.6 backup over what ever was still there. Runs fine

I'll have to wipe and try a clean install again when I'm not at work.
[Verizon Samsung Galaxy S III] TokedUp:
Don't install the apk just follow the directions. Push it to system/app fix perms and reboot

If u have more problems please post in the camera thread so we don't clog up this thread with off topic talk.
[Verizon Samsung Galaxy S III] deuce237bblock:
Actually this ROM gets such good battery life mine lasted on one charge through the whole storm. I did shut WiFi, GPS, etc. off to make it last longer but yeah.
[Verizon Samsung Galaxy S III] newbie4ever:
Is there a way to change the DPI? Love the rom... Hate the low visibility
[Verizon Samsung Galaxy S III] countryfolk07:
Don't know how familiar you are with root explorer, build. prop modification, but go into the build.prop in system and find a line near the bottom that days something about LCD density. It should say 245. Change to whatever you like. 320 is stock. 268 and 280 are nice also. Save changes. Clear market data. Then reboot.