yashsingh1/xdaforums huggingface dataset:
[Verizon Samsung Galaxy S III] edwards311:
Just came back to Slim Bean after trying pretty much every other ROM for the SGS3 and just as I expected Slim is still rock solid!!!! I do have a question though, when I turn the power shutter off in the camera settings it still makes a sound when I take a pic. Is there a simple edit I can do through root explorer? Any help would be appreciated
[Verizon Samsung Galaxy S III] snoop5:
is there anyway to get a different messaging icon than the ugly green one
[Verizon Samsung Galaxy S III] SoCalSpecialist:
u didnt read my friend

---------- Post added at 12:27 PM ---------- Previous post was at 12:26 PM ----------

a bunch of ways, here's two

1 - install a theme

2 - find the messaging apk and change the icon

---------- Post added at 12:28 PM ---------- Previous post was at 12:27 PM ----------

sorry i cant replicate that.

very weird tho. did you do that then reboot? try to do it, then reboot and see if it sticks.
[Verizon Samsung Galaxy S III] edwards311:
---------- Post added at 12:28 PM ---------- Previous post was at 12:27 PM ----------

[/COLOR]

sorry i cant replicate that.

very weird tho. did you do that then reboot? try to do it, then reboot and see if it sticks.[/QUOTE]

Tried a reboot, flashed the ROM again(clean install both times) and nothing is working. It worked when I was on previous versions of Slim. It also worked on CleanROM just before I flashed back to Slim.:confused:
[Verizon Samsung Galaxy S III] spacepirates:
Coming from slim 3.0 and as far as I know doing the steps for a clean install. Nandroid backup, wipe data/factory reset, flash 3.1
[Verizon Samsung Galaxy S III] infinit22:
Does this have group messaging?
[Verizon Samsung Galaxy S III] b1g.p0ppa:
Remove these two files:

/system/media/audio/ui/camera_click.ogg

/system/media/audio/ui/camera_focus.ogg

---------- Post added at 04:57 PM ---------- Previous post was at 04:54 PM ----------

Yes. Enable it in Settings in Messaging.
[Verizon Samsung Galaxy S III] dtowngs4g:
I just came from liquid smooth rc9. ROM ran fine til I upgraded to rc9 then I kept getting Ui force closes. Just flashed this ROM today, so far so good. Will give another day to mk sure.
[Verizon Samsung Galaxy S III] cordell12:
I have tethered both WiFi and USB, mainly USB though. For the past 3 days or so my comcast connection was cutting in and out. I finally ran a new coax cable to fix it, but while down it was 4G tethered via USB.
[Verizon Samsung Galaxy S III] cordell12:
Not sure if you all know this but stop by the website from time to time and see whats cooking!

http://slimroms.net/
[Verizon Samsung Galaxy S III] sudermatt:
Won't we get OTA's on new stuff?:cool:
[Verizon Samsung Galaxy S III] Colomonster:
Would not install without WiFi... and also made it so my restore won't work..... please help!!! This is the only ROM that will flash and start ATM... please let me know by pm how to strip everything and start fresh in adB... thanks...

Edit: OK so the internet works... I guess this will be my daily driver for a few days. Please if anyone feels like helping me fix my cwm issues I am all ears.. it will not restore any of my backups, including a backup of slim... I am not opposed to making this my dd.... I would just like to be able to backup. I am working until midnight but will be able to check this semi frequently
[Verizon Samsung Galaxy S III] jmill75:
Can someone point me to the download, i see the download page but not the VZW version. Thanks
[Verizon Samsung Galaxy S III] Masa6GCS:
I think a new build is coming as all the other roms have been updated to 2.3. Please let it be true, love this rom :fingers-crossed:

Edit: A new update is coming out today.

---------- Post added at 06:50 PM ---------- Previous post was at 06:38 PM ----------

Is the slimgapps the new name for common?
[Verizon Samsung Galaxy S III] cordell12:
2.3 is UP on website and you should have a OTA Notice!!!

http://slimroms.net/

Slim-Gapps is the new common, also should not need camera fix. See second post for flashing instructions

if for some reason data does not appear on first boot, pull battery and reboot. i think its my device that needed the battery pull and reboot, but not sure...
[Verizon Samsung Galaxy S III] got556:
Hmm....really wanting to put some slimness on an already slim device.
[Verizon Samsung Galaxy S III] jgrimberg1979:
I am not sure if it has been mentioned already or not but the when you select ota in options it fc.
[Verizon Samsung Galaxy S III] got556:
Tried native tethering option, WiFi tether, and foxfi....nothing will allow my computer to connect. :confused:
[Verizon Samsung Galaxy S III] cordell12:
Will check in morning. Build was delayed due to a camera/gallery issue all other devices were having. Once fixed I compiled and got it out as quick as I could ;)
[Verizon Samsung Galaxy S III] got556:
Thanks. I tried everything.

Wipe, re flash everything, fix permissions, uninstall all non native wifi tether apps, so on and so forth. Nothing would work. I could see my hotspot on my laptop but it would never connect. Other than that, loved the build so far. Had to switch ROMS though as I need my hotspot for work. Will keep an eye on this though.
[Verizon Samsung Galaxy S III] cordell12:
Anybody having issues with WiFi Tether, if so under your settings select "Open" rather than either of the secure channels. I will try to get a fix out this afternoon :)

Thanks for pointing it out, "Open" does connect, so that will work for you until I get a fix pushed out.
[Verizon Samsung Galaxy S III] pie944:
Great ROM. Came from CM10.
[Verizon Samsung Galaxy S III] tamar88:
great rom so far. The camera/gallery fix on the site didn't correct my issue though. It still freezes after a photo is taken.
[Verizon Samsung Galaxy S III] hopesrequiem:
You weren't supposed to flash that. Wasn't for our version. That fix was posted a day before our 2.3 build was posted
[Verizon Samsung Galaxy S III] jclendineng:
Anyone know why phone info force closes? And why updates me force closes sometimes? Thanks.
[Verizon Samsung Galaxy S III] got556:
Are you using the app phone info? B/C I think phone info is baked in to the ROM.
[Verizon Samsung Galaxy S III] mkintop:
Has anyone else had trouble Activating with this ROM? This is my first time trying and and it won't get past the Activation screen.

Edit: I just waited for about 5 minutes, it said it could not activate and gave an option to retry or skip and I selected skip. Seems to be working ok but I'm not sure why it didn't work.
[Verizon Samsung Galaxy S III] iSpyder:
The thread is TL;DR. Lol. sorry.

A few things that i noticed.

So far, Im experiencing the camera menu in Landscape force closes. (Permission fix doesnt help.)

And i toggle the LED lamp thru the the Custom notification crashes the SystemUI. (Permission fix doesnt help.)

Sometimes when the screen times out and i press the home key or the power button it doesnt light up and freezes. I have to do a battery pull and reboot.

Again sorry if someone has mentioned this already.

Im on Slim 2.3. upgraded from 2.2.

Same issues were on the 2.2.
[Verizon Samsung Galaxy S III] droidxxxxx:
For some reason my google mail is not working it says it's not compatible.. And also no bass when I play Slacker Radio or Pandora over Bluetooth in my vehicle.

---------- Post added at 07:05 PM ---------- Previous post was at 06:49 PM ----------

And also no Facebook contact picture sync..very smooth ROM though..looks really good..
[Verizon Samsung Galaxy S III] infinit22:
Is there anyway to get this MMS app to work on a tw rom?
[Verizon Samsung Galaxy S III] prototype7:
Didn't try it on 3.0 so not sure if it was a problem there too, but 3.1 has the no bass over BT bug.
[Verizon Samsung Galaxy S III] danstar:
my facebook contact's picture shows up in my contact list....
[Verizon Samsung Galaxy S III] snael:
I had this problem on 3.0 as well... haven't tried on 3.1 yet.

Sent from my SCH-I535
[Verizon Samsung Galaxy S III] indyssee:
I listened to power amp earlier through BT and it had bass for me
[Verizon Samsung Galaxy S III] hsomnus:
I have bass too but alot of static...tried multiple bluetooth devices and music app combos
[Verizon Samsung Galaxy S III] edwards311:
Worked great!!!!! I just moved the files to another folder in case I screwed something up....thanx again!!!
[Verizon Samsung Galaxy S III] sivarticus85:
Does this build have the low cam volume bug? At work and can't test...
[Verizon Samsung Galaxy S III] infinit22:
Is there any way to invert the MMS and contacts app?
[Verizon Samsung Galaxy S III] b1g.p0ppa:
I can hear comfortably on a call. Have to pull the phone away from my ear to adjust volume tho.
[Verizon Samsung Galaxy S III] SoCalSpecialist:
i use Noozxoide EIZO found here...works flawlessly.

give it a go, you wont be disappointed.
[Verizon Samsung Galaxy S III] TabletConnect:
This question probably does not belong here but it is an easy one for probably all of you. What exactly is "inverted" apps? What is the difference between that and regular ones? Thanks.
[Verizon Samsung Galaxy S III] funnyperson1:
So using Noozxoide you don't have any issues with bass when connecting via Bluetooth? If that's the case then maybe the bug is in the MusicFX app.
[Verizon Samsung Galaxy S III] zeus33:
White text on black background instead of black text on white background.
[Verizon Samsung Galaxy S III] sivarticus85:
That's not what I said. I'm talking about the low recording volume on the camcorder. It's been a bug for a while. I'm home now so I'll check it out.
[Verizon Samsung Galaxy S III] Thadrow:
Id like to know this as well if you find out .
[Verizon Samsung Galaxy S III] SoCalSpecialist:
none.

i use the bluetooth in my car and via my headset with no issues quality wise.
[Verizon Samsung Galaxy S III] b1g.p0ppa:
Sorry, I read that as low call volume bug, not cam. Tested and sound does seem lower in videos I record.
[Verizon Samsung Galaxy S III] SoCalSpecialist:
its all in the kernel i guess.

i dont have any issues with cam record.

im using KT's latest.
[Verizon Samsung Galaxy S III] b1g.p0ppa:
Interesting thought. Here in a bit I'll re-flash and try the ROM's built-in as well as latest ktoonsez.
[Verizon Samsung Galaxy S III] hsomnus:
Didn't help with the static
[Verizon Samsung Galaxy S III] SoCalSpecialist:
weird. very weird.

sorry cant help there.
[Verizon Samsung Galaxy S III] Marcismo55:
Disappointed I didn't try this ROM out sooner. Light and very responsive.

Bluetooth audio through my TV sounds good but can't comment on anything else.
[Verizon Samsung Galaxy S III] bond32:
Never would I thought to give AOSP any thought... I was pretty happy with stock. This is a very nice change. I really like it so far.

Edit: do you guys use on screen keys? I figured with the extra space it might be nice. I'm not really a fan of the home button (hardware).
[Verizon Samsung Galaxy S III] b1g.p0ppa:
I tested diff kernels (ROM default and ktoonsez) and had the same experience as with Lean exp1.1 where a2dp has no bass unless you pause music, make a phone call and hang up, then resume playing. I also recorded video when on both they're not any louder than others I recorded on LKexp1.1.

My procedure was to wipe cache+dalvik then format system prior to flashing the ROM and the Real Dark Slim gapps. To test the koonz kernel I did the same procedure + flash that kernel and the boot fix from cordell.

Not extremely scientific I'll agree, but seems to indicate the kernel is not the root culprit.

Still, the a2dp workaround isn't bad at all and I don't really record video so that's moot for me. It would take much more than those to sour me against this ROM. I seriously can't say enough about how great it is!
[Verizon Samsung Galaxy S III] dcowboys2184:
Do lte work? Mine don't seem to connect
[Verizon Samsung Galaxy S III] SoCalSpecialist:
well of course you should do a complete wipe. its not a work around, its the way it should be. from the way you were speaking of your issue i was under the assumption you went thru the proper steps.

ive always been an advocate of a COMPLETE WIPE..not a half assed or a dirty flash.

does for all of us, bad flash possibly?
[Verizon Samsung Galaxy S III] b1g.p0ppa:
Sorry, didn't mean to sound like I was complaining. I'm totally happy with the way this ROM is running for me. I didn't have enough time to do proper testing last night and was interested in comparing my current setup's behavior in with the two other scenarios. I do dig that the proper way to test is from a full wipe, I just get lazy.
[Verizon Samsung Galaxy S III] fz798:
I did a full wipe today to test the bass issue as described above, and got the same result :(

Soon as you make a call, bass is restored to a2dp streaming, but if you reboot or disconnect/reconnect Bluetooth, bass is gone.
[Verizon Samsung Galaxy S III] foreverinpanama:
I noticed this last week. Thought I had goofed up something on my head unit. St least there's a work around.
[Verizon Samsung Galaxy S III] Marcismo55:
Works for me. Make sure you have LTE/CDMA selected under mobile networks. If you already do try toggling airplane mode.
[Verizon Samsung Galaxy S III] FastEddie422:
Is there any way to get just the Exchange mail app by itself (preferably inverted)? Can I just pull the apk from the Extras zip and sideload that? I'm not sure if the package installs any other system level files in recovery that the Exchange app would rely on.
[Verizon Samsung Galaxy S III] spacepirates:
I've done 3-4 full wipes with different combinations of kernels/add-ons and 2 dirty flashes over slim 3.0 and I can't even get the phone to stay on longer than a few seconds before it bootloops after a lot of FC's (launchers, systemui). checked the sha1 checksums to what was posted on the website and they match. I'm not really sure what my next steps should be.

Anyone have any helpful hints?
[Verizon Samsung Galaxy S III] fz798:
Maybe stating the obvious, but did you take the full gapps/addons and not the update ones?
[Verizon Samsung Galaxy S III] foreverinpanama:
Try doing the obvious cache wipes and all but also fix permissions. Just a thought
[Verizon Samsung Galaxy S III] spacepirates:
Yeah, I've tried the full gapps, inverted gapps (both all-in-one) and no gapps. None of those worked for me.

---------- Post added at 02:35 PM ---------- Previous post was at 02:26 PM ----------

I did factory reset, wipe cache, wipe dalvik, fix permissions, flash 3.1 & kt kernel, fix permission again with no luck in that order.
[Verizon Samsung Galaxy S III] b1g.p0ppa:
Did you flash cordell's patch to boot with non-stock kernels? http://xdaforums.com/showpost.php?p=34877850&postcount=808

Might also try formatting /system in recovery. Also, avoid restoring any data until it's stable (if you're trying to restore).
[Verizon Samsung Galaxy S III] foreverinpanama:
Geez sorry to hear. I'm out of ideas. Good luck. I did a dirty flash to 3.1 and had no issues myself.

You might be getting close to the point of going back to stock and doing the entire process from the very beginning.
[Verizon Samsung Galaxy S III] spacepirates:
I did not, though I did try flashing 3.1 without a separate kernel and it had the FCs/bootloops.

Regardless, I am quite pleased that it did finally work.

Nandroid backup, factory reset, wipe cache, fix permissions, mount and wipe system, flash 3.1, flash the patch, flash KT kernel, flash inv gapps, fix permissions, reboot

seems stable, thanks for your help, i missed that patch and mounting/wiping system separately.
[Verizon Samsung Galaxy S III] roose00:
anyone experiencing slightly less life out of the battery on 3.1? 3.0 was settling in beautifully and giving me a solid 24 hours. This build is down to less to about 16.
[Verizon Samsung Galaxy S III] born1690:
Try downloading a app called battery calibration and charge your phone to 100% then open the app and follow the instructions nothing to it really
[Verizon Samsung Galaxy S III] snael:
Thanks a ton for posting this workaround it worked for me and allows me to use my BT headphones again at work. Love the ROM just wish I could figure the no bass issue out. Fully unrooted to stock and formatted internal and ext sd, re rooted clean install 3.1 with default kernel and still have no bass over Bluetooth.

Not a deal breaker especially with this workaround.. love the ROM!

Sent from my SCH-I535
[Verizon Samsung Galaxy S III] :
I've tried redownloading and reflashing a d everything I could and I still get the stock 241 DPI which I can change no problem, but rebotting my phone makes my home WiFi "not in range" unless I disable for a minute and reenable it. Anyone have any idea what to do? That's the only issue I have with this rom
[Verizon Samsung Galaxy S III] Marcismo55:
I don't know what's up but even with the same usage I have never had battery life like this on any AOSP rom.

Default clock speeds/kernel, on demand & sio is working well for me. Just a hair under 2 hrs of screen on time.

Thanks for such a fantastic rom Cordell!
[Verizon Samsung Galaxy S III] FastEddie422:
Sorry for asking the same question again but I never got an answer from a few days ago.

I want to install JUST the inverted Email and Exchange apps from the Extras package. I know I can install everything and freeze the apps I don't use but I'd rather keep my phone clean.

I tried to pull the apks out of the zip file and install them (both normally and by mounting the system r/w and changing the permissions) but I couldn't get Email.apk to work with me.

Could someone either point me to inverted Email/Exchange apps on their own that will work with this rom or at least tell me another way to go about it? Thanks in advance.
[Verizon Samsung Galaxy S III] cordell12:
This should take care of you, Flash in recovery. Choose InvertedExchangeEmail.zip, or ExchangeEmail.zip, ExchangeEmail.zip is NON Inverted...

What kind of Router do you have? I know (cant remember brand/type) there is a router that AOSP ROMs and the drivers used have trouble connecting to after rebooting. The user must "toggle" in order for router to be seen by the device.

I really wish I had some 4.2 to offer up, but at this time I dont :( I know everyone (myself included) for some 4.2 goodness on our VZW S III, as SOON as something happens I will either post a update, or if the build is solid, Ill post the build, stay tuned!
[Verizon Samsung Galaxy S III] FastEddie422:
That worked perfectly. Thank you so much!

This is the first AOSP rom I've tried that does exactly what I want it to now. Cheers.
[Verizon Samsung Galaxy S III] danstar:
Take your time on the 4.2 stuff. 3.1 is running perfectly for me. I'd rather wait and have a rock solid 4.2, than to have something sooner that isn't stable. You do great work, thank you!
[Verizon Samsung Galaxy S III] fz798:
For sure, 3.1 is the best yet.

I am seeing two "new" issues, that I never had before 3,1:

The first, is that the Bluetooth phone connection is constantly disconnecting from my car. It stays paired, just undocks constantly. I've tried deleting the pairing countless times (from both the phone and the car), as well as changing the device name, wiping the phone and flashing 3.1 from scratch, all to no avail. Interestingly, the A2DP device connection never breaks, that stays connected even when the phone connection breaks (then of course too there's still the bass issue, but that was in earlier Slim versions too). Simply hitting "reconnect" on the car's infotainment system does not work, I have to turn Bluetooth off on the phone, then back on, and then the reconnect works. the disconnect doesn't happen while I am in a call, but if just connected (with or without the A2DP connection), the disconnect happens constantly, every few minutes. Sometimes it will stay for longer than other times, but usually no longer than 15 minutes or so, sometimes, much less. Also, the other BT devices I use never disconnect, just the car phone, but this too only began with v3.1

The other issue that's really weird, relates to Google Voice (regardless of Bluetooth state). If I make a call directly using GV, it works fine. If I dial my GV number first, then make a call from GV, that works fine too. However, if I use Voice Choice to automatically dial the GV number first, I get a busy signal on every outgoing call. I've tried wiping and uninstalling both apps. I've tinkered with every setting I could find in both apps, and still the same result. This only began happening with 3.1.

If anybody has any ideas on either of these issues, I would be most appreciative!
[Verizon Samsung Galaxy S III] foreverinpanama:
I can only comment on the BT issues since I don't use Google voice for calls but I use BT to stream Pandora and local flac files every day on my hour + commute. Never disconnects in the way you explained.

Bass issue is there but I quickly call and hang up to fix that and sticks.

Btw my head unit is a Clarion cx501 which is blue tooth 2.0. Not the new stuff.
[Verizon Samsung Galaxy S III] bajasur:
Did anyone else lose link to all their threads this morning in the XDA app... ???
[Verizon Samsung Galaxy S III] roose00:
Have been on a fringe area and I keep switching between 3g and 4g. No problem switching, but the hand off its slow enough that I will lose data for a couple seconds. Long enough that a data application will lose connection. Any remedies? Using HE radio. No issues on stock roms

Sent
[Verizon Samsung Galaxy S III] indyssee:
I'm always on fringe of sh**ty service and 3g and the new JB radios have, by far, been the best for me.
[Verizon Samsung Galaxy S III] rich33389:
How is the data connection with this Rom, on slim rom 3.0 and eclipse Rom I was getting constant data drops that I do not get on tw roms. If this is not an issue with this one I will gladly stitch to it.
[Verizon Samsung Galaxy S III] Marcismo55:
It has been fine for me except in those fringe areas which I am really in. Never had data drop out of nowhere though.

If yo want an extremely stable AOSP rom with all the right customization options...this is it. Its worth flashing for sure.
[Verizon Samsung Galaxy S III] mkintop:
I'm new to Slim and have to say I'm very impressed! Very smooth and just the right customization available.

One question, why on all AOSP ROMs when connecting to a dock (iBolt) does the ability to use Bluetooth for calls stop working. It's like turning on the "Dock USB Audio" automatically turns off Bluetooth. Anyone have a solution to this (other than going back to a TW ROM...)?
[Verizon Samsung Galaxy S III] ross8425:
View attachment 1541275

View attachment 1541276

I went to sleep last night with my phone at 100% any idea why it did this?
[Verizon Samsung Galaxy S III] ross8425:
Ps the brostache was pretty funny.
[Verizon Samsung Galaxy S III] brando7010:
Anyone else having problems with 3.1?

I can't get the ROM to boot with the stock kernel or with KT (boot loop and eventually hangs). Finally got it to boot with LK1.8.1.

I guess I will find out what other issues I might have.
[Verizon Samsung Galaxy S III] ross8425:
I did a total wipe on my phone after using Liquid for a while. Just wanted to see what this was all about; its as stable as Liquid was. I think it did boot loop once on the initial install, but after that its been smooth as can be. I really see no reason to use anything on your phone other than this or liquid. :good:
[Verizon Samsung Galaxy S III] dawiseguy77:
This is my first time using this rom, and i must say i am pleasantly surprised at how well everything works. Dpi is a little small for me, but i can get used to it and gps isnt as fast to lock ad a touchwiz rom, but as long as it connects I'm on with that. Great work dev
[Verizon Samsung Galaxy S III] brando7010:
I did a full wipe also. I even went as far as flashing a "full wipe" stock image with Odin and I still couldn't get it to boot correctly.

It is running now, seems kind of flaky but it's running.
[Verizon Samsung Galaxy S III] Marcismo55:
I agree and changing the DPI back to stock was the first thing I did. I'll be running this until 4.2 rolls out