yashsingh1/xdaforums huggingface dataset:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] bjtheone:
Just flashed build 3 (wipe cache, dalvic, and system) and have the same issue with tethering. Asus tf700 connects fine but does not actually get Internet connectivity. No browsing, speedtest or even ping. Dns resolves names to ip but not getting anything through the phone. I am on Rogers, with solid LTE network to the phone, rogers lte apn selected. Tablet works fine with normal wifi or tethered to an iPhone. Any suggestions or trouble shooting steps would be greatly appreciated. Confirmation from anither user on Rogers that tethering works on build 3 would also be great!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] oddspec:
Re: [ROM][4.2.2][March 29] Slim Bean-d2(att/bell/telus/rogers) [build 3]

Anyone know of an app or way to bind the widget view pager to a launcher gesture

sent from the samsung galaxy airplane (i747)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] busarov:
Re: [ROM][4.2.2][March 29] Slim Bean-d2(att/bell/telus/rogers) [build 3]

Not sure if I really understand your question but I know Nova Launcher supports gestures. You can set a specific gesture to open an app. I'm sure it could accomplish what you're trying to do as well.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] oddspec:
Re: [ROM][4.2.2][March 29] Slim Bean-d2(att/bell/telus/rogers) [build 3]

I know that what I am asking is the ROMs built in widget page veiwer that can be launcher from either the nav bar or bound to a hardware key I want to bind it to a gesture but it inaccessible threw any launcher I tried I was asking if anyone knew a way or an app that will make this happen

sent from the samsung galaxy airplane (i747)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] blk_jack:
Re: [ROM][4.2.2][March 29] Slim Bean-d2(att/bell/telus/rogers) [build 3]

Right now it's not accessible from a shortcut, but that's a good idea and something I'll look into implementing.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] phositadc:
Re: [ROM][4.2.2][March 29] Slim Bean-d2(att/bell/telus/rogers) [build 3]

Ignore
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] phositadc:
Re: [ROM][4.2.2][March 29] Slim Bean-d2(att/bell/telus/rogers) [build 3]

I posted this in BMS kernel thread too, but What kind of drain should I be seeing while phone is deep sleeping (WiFi on)? I've been losing nearly 1% per hour overnight even though better battery stats shows 98% deep sleep. For instance, last night I lost 7% in 8.5 hours. Too high?

Running slim build 2.5

Sent from my SAMSUNG-SGH-I747
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] 12packabs:
Re: [ROM][4.2.2][March 29] Slim Bean-d2(att/bell/telus/rogers) [build 3]

That is quite good. Every device and user setup is different.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] phositadc:
Re: [ROM][4.2.2][March 29] Slim Bean-d2(att/bell/telus/rogers) [build 3]

Yeah I agree the deep sleep % is outstanding. I guess I've gotten spoiled on nexus devices losing only like 2-3% battery overnight (ie, less than half a percent per hour).

Sent from my SAMSUNG-SGH-I747
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] droid_funktionz:
Email app time sync intervals...

One small request. I noticed that after the first version of aroma installer, the email app limited its sync options to being 1 hour at the longest interval. (Since noticing this) I have been previously installing the old version which has many more sync options but unfortunately with the latest build it does not work with TRDS. :confused:

It would be awesome if we can get those same sync time intervals on the next version of aroma. I don't have a need to sync my email every hour and this seems to help with battery life as well when not used like this.

Awesome latest build!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] anilrawal:
Build 3, Back Camera dont work, rest works

I experience the same issue on build 3, did a clean install and using default kernel.

One thing is strange, the video camera, panoramic camera, front camera works but the normal camera on back do not work. I get the same error.

Bug report is attached.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] rani9990:
Re: [ROM][4.2.2][March 29] Slim Bean-d2(att/bell/telus/rogers) [build 3]

That is too high for my device, but every device is made differently. I usually drain about 4% in 10 hours deep sleep.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] phositadc:
Re: [ROM][4.2.2][March 29] Slim Bean-d2(att/bell/telus/rogers) [build 3]

Thanks. What kernel do you use?

Sent from my SAMSUNG-SGH-I747
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] rani9990:
Re: [ROM][4.2.2][March 29] Slim Bean-d2(att/bell/telus/rogers) [build 3]

I use KTs kernel. No UV just ktoonservative tweaks and row. 486 MHz screen off speed.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] blk_jack:
I was mistaken when I previously said you couldn't toggle this from an activity. You can, it's under System UI -> Widgets -Toggle. Beware though that the widget disappears when you touch anywhere on the screen that's not the widgetlayer (when it's exposed), so setting up a swipe gesture to "toggle" the widget will only really show you the widget, rather than toggle it.

To better explain.. say you bind the toggle WidgetLayer activity to swipe up with nova launcher.

1) Swipe up -> Shows WidgetLayer

2) Swipe up again -> as soon as you touch the screen it hides the widget layer -> the swipe up shows it again instead of hiding it since it was already hidden by the first touch.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] oddspec:
Re: [ROM][4.2.2][March 29] Slim Bean-d2(att/bell/telus/rogers) [build 3]

Thx sir I'll figure it out to work with my setup I use a strange launcher mosy don't ( stoic )

sent from the samsung galaxy airplane (i747)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] GigDroid:
Re: [ROM][4.2.2][March 29] Slim Bean-d2(att/bell/telus/rogers) [build 3]

Just did a clean install of build 3 (wiped caches, data, and system). Anyone notice that the subject line in trds slim gmail after you select/open a message is dark grey on black? Kinda low contrast and hard to read. It used to be white on black on build 2.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] kswa1987:
it looks like the slim_gapps download is broken on the slim website... does anybody have the slim_gapps from 3-29? Thanks!

edit its working again... that was weird
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Brooklynsour:
Re: [ROM][4.2.2][March 29] Slim Bean-d2(att/bell/telus/rogers) [build 3]

Maybe bad download

BTW build 3 is the best one great job haven't had any problems thanks
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] 1weener:
Why don't you toggle sync and just run it when you want to check?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mfc719:
Re: [ROM][4.2.2][March 29] Slim Bean-d2(att/bell/telus/rogers) [build 3]

Suffering! Using my old captivate while my S3 is being fixed.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Brooklynsour:
Re: [ROM][4.2.2][March 29] Slim Bean-d2(att/bell/telus/rogers) [build 3]

Where r u fixing it? Mine fell in toilet on 4th day.... No speaker sound since
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] baconatorXVI:
Re: [ROM][4.2.2][March 29] Slim Bean-d2(att/bell/telus/rogers) [build 3]

This release isn't Linux 3.4 right? 3.4 kernels haven't booted. Also no PIE, any hope for that in the future?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] busarov:
Re: [ROM][4.2.2][March 29] Slim Bean-d2(att/bell/telus/rogers) [build 3]

To the question about the 3.4 kernel...

http://xdaforums.com/showpost.php?p=39691744&postcount=1354
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] CZ Eddie:
Love this ROM. Thanks guys!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mfc719:
Re: [ROM][4.2.2][March 29] Slim Bean-d2(att/bell/telus/rogers) [build 3]

Cracked glass. Insured with a company called gocare.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] baconatorXVI:
Re: [ROM][4.2.2][March 29] Slim Bean-d2(att/bell/telus/rogers) [build 3]

Well dammit, during my flash between Pac man Rom and this my imei got wiped out :/
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] AtoZ0to9:
Try rebooting, sometimes it just disappears until a reboot...
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] GigDroid:
Re: [ROM][4.2.2][March 29] Slim Bean-d2(att/bell/telus/rogers) [build 3]

Anyone else seeing this? Anyone? Anyone? Bueller? Bueller?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] busarov:
Re: [ROM][4.2.2][March 29] Slim Bean-d2(att/bell/telus/rogers) [build 3]

It's present on mine too.

Not an issue for me though, as I don't use my phone to email. Just confirming.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] baconatorXVI:
Oh i had rebooted many times through kernel flashing and stuff. I wonder, could me flashing the incorrect 3.4 kernel be the cause? I came back to SLIM while i wait for Pacman rom to get a bit more stable.

I got my IMEI back, thankfully i had mad a .qcn backup when i lost it once before. restoring it wasn't too bad.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] J M L:
snd_soc_msm_2x

I've been having a problem on Slim 2.5 and 3 streaming podcasts from Doggcatcher to a mono bluetooth headset. I use either Mono Bluetooth Router or BTmono to route the sound. This has worked fine on all roms I've tried except Slim. The headset works fine for phone calls, and it also works fine using mono-routing with the music player. So far, it's just Doggcatcher which gives me a problem.

I investigated as to what might be different between the sound setup for Slim and Task650's 3/13 rom (his last 3.0 based one, I think). I just used that one because I happened to have it on my hard drive, not for any special reason. What I discovered was differences in system/etc/snd_soc_msm/snd_soc_msm_2x A representative diff is:

***************
*** 876,886 ****
Name "HiFi Low PowerBT SCO Rx"

EnableSequence
! '"AUX_PCM_RX Audio Mixer MultiMedia3':1:1
EndSequence

DisableSequence
! '"AUX_PCM_RX Audio Mixer MultiMedia3':1:0
EndSequence

# ALSA PCMs
--- 876,886 ----
Name "HiFi Low PowerBT SCO Rx"

EnableSequence
! 'AUX_PCM_RX Audio Mixer MultiMedia3':1:1
EndSequence

DisableSequence
! 'AUX_PCM_RX Audio Mixer MultiMedia3':1:0
EndSequence

# ALSA PCMs

From what I can see, on Slim the string is '"AUX_PCM_RX Audio Mixer MultiMedia3':1:1, but from the other rom it is 'AUX_PCM_RX Audio Mixer MultiMedia3':1:1, with an extra ". I don't actually know what that extra quote is doing, but removing them from snd_soc_msm_2x and rebooting has restored the ability to play podcasts from Doggcatcher to a mono-headset. I've not done extensive testing, but the headset seems to still work with the phone as well.

After making the change, I did have my first instance on Slim of bluetooth getting stuck at "Turning bluetooth off...". After rebooting I was able to connect the headset and turn bluetooth on and off without issue, so it's either an intermittent problem, or something specific triggers it.

Anyway, hopefully somebody knows if the extra quotes are typos, or if they're supposed to be there and the playback problem is due to a bug (or incompatibility) someplace else.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jproy12:
What kernel is best used with the latest v3.0? I've tried ktoon's and been having problems... Tried BMS as well, just wondering what everyone else uses?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] LeeC:
I'm using BMS on Telus and dont see much of trouble. What problems you have?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jproy12:
What settings have you done to BMS? And I'm assuming its with SetCPU?

I'm trying to find the best performance/battery setup for now...
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] bjtheone:
Does anyone on Rogers tether, and if so what are the relevant settings?

Also, it seems the freezing after a call happens more often if the other party hangs up first. Have not yet had a freeze when I terminate the call. Only had 4 freezes, but they all followed that scenario.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] phositadc:
Re: [ROM][4.2.2][March 29] Slim Bean-d2(att/bell/telus/rogers) [build 3]

Tried BMS first and liked it fine, but was losing nearly 1% per hour while idling (98% deep sleep), which seemed high to me. So now I'm trying blck Jack's add-on kernel to see if it improves on that idle drain at all.

Both kernels seem to work fine. Haven't been using black Jack's kernel long enough to get a feel for idle drain.

Sent from my SAMSUNG-SGH-I747
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] brttwilliams:
Re: [ROM][4.2.2][March 29] Slim Bean-d2(att/bell/telus/rogers) [build 3]

I've only used ktoonz, but I haven't had any issues, I enabled the OC steps without OC'ing, and run the row scheduler with the ktoonzservative gov.... I also keep BBS handy to check on anything I may need to look into.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] voidstab:
With build3 i've decided to give BMS a whirl and so far I like it. I like the "control panel" that comes with kt747 but I'm in an anti-tinker mode now. A few builds ago I spent hours messing with governor and scheduler settings, and on the last build(2.5) I just stuck the governor on performance and left it there, and really if you put your phone on the charger at night anyways I couldn't see much difference. For me I'm seeing some pretty good battery numbers with BMS and I don't plan on putting any time in changing settings.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jproy12:
Which version of ktnooz kernel are you using? I know its vers 3.0.x, but what date is it from? Also, what settings have you done to the gov? Also roughly what's your battery drainage while in deep sleep? I am hoping to get about 1% every 2hours or so.

Thanks
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] LeeC:
I'm just using interactive and row. about 2-3% battery drain every hour with WifI, data, sync on all the time. I am happy whit that but the total screen time is about 3 hours or little bit more. I wish could get more screen time rather than the deep sleep time.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] brttwilliams:
Re: [ROM][4.2.2][March 29] Slim Bean-d2(att/bell/telus/rogers) [build 3]

I'm using 3/27... Haven't had problems really with any of them
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jproy12:
I'll give it another shot! Did you make any adjustment to the governor? Or just left it as is?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] brttwilliams:
Re: [ROM][4.2.2][March 29] Slim Bean-d2(att/bell/telus/rogers) [build 3]

I left as is other than switching on the OC steps
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] t3chn0s1s:
Re: [ROM][4.2.2][March 29] Slim Bean-d2(att/bell/telus/rogers) [build 3]

Experienced my first SOD last night. Running completely stock Slim (build 3) - kernel and all.

Sent from my Galaxy S III
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] brttwilliams:
Re: [ROM][4.2.2][March 29] Slim Bean-d2(att/bell/telus/rogers) [build 3]

Do you have better battery stats installed?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ooklathemok:
I had problems on 2.5 with tethering. I found a thread somewhere that mentioned changing the APN for Rogers. That didn't seem to help, but switching the network off of LTE does work. I'm not sure if there's another APN for Rogers LTE tethering or if you cannot tether on LTE. Try switching off LTE and tethering.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] phositadc:
Re: [ROM][4.2.2][March 29] Slim Bean-d2(att/bell/telus/rogers) [build 3]

Does better battery stats cause sods?

Sent from my SAMSUNG-SGH-I747
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jasvncnt1:
No..
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] rmead01:
You should NEVER leave your phone on performance govnr. It sets your phone to max freq and keeps it there which is not good for your phone.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] t3chn0s1s:
Re: [ROM][4.2.2][March 29] Slim Bean-d2(att/bell/telus/rogers) [build 3]

Yes. Why do you ask?

Sent from my Galaxy S III
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] olo567:
Is it just me, or is the dark theme option for QuickReply gone?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] voidstab:
Alright, I'm curious why performance should NEVER be used? I noticed no issues, battery life wasn't even effected as much as you'd think.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] bjtheone:
Don't see why tethering would not work on lte but you are absolutely right, dropping down to 3g makes it work. Thanks for the tip!

Changing the apn does not work for me (at least not between the predefined ones).

So the next question, how to get tethering working over lte?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Judman:
Dirty flash of build 3 here with the new slim_gapps.

I cannot download any apps out of the play store. Getting "Error retrieving information from server. [RPC:S-5:AEC-0]"

Anyone else getting this error? I have cleared the play store cache and data, but no bueno!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] J M L:
Looks like this problem was fixed by cordell probably a few hours before I noticed it. I hope the commit means that the fix will be in the next release. Until then, if anybody else is a having a similar problem with bluetooth, you can download the fixed file and put it into system/etc/snd_soc_msm/.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] baconatorXVI:
Re: [ROM][4.2.2][March 29] Slim Bean-d2(att/bell/telus/rogers) [build 3]

How often do you drive your car everywhere with the gas pedal completely to the floor? Never right?

It's a waste of battery it generates a LOT more heat and running higher frequencies for longer duration puts more wear and tear on your phone.

Why would you want to run performance governor?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] 12packabs:
Trying re-installing with a full wipe - data factory reset, wipe cache, wipe dalvik, format system, install ROM, install gapps, then reboot.

You might get away with dirty flashes for a while, but if you eventually have problems, you need to start from a known clean state for the devs to be able to help you. Chances are it will resolve your problem.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] cytherean:
I've had this a couple times, you will have to remove/delete your google account from the phone then log back in and you are good to go.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ooklathemok:
I'd be interested in purchasing a Slim Bean Rom Backup settings app. Similar to the AOKP one. It would just be nice to not have to change my LCD density settings, lock handle with each update.

Actually, it would be great if I could figure out how to keep SuperSU through updates as well. Disappeared this time, but I swear it survived when I went to 2.5.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Judman:
This worked!! Thanks.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] blk_jack:
Re: [ROM][4.2.2][March 29] Slim Bean-d2(att/bell/telus/rogers) [build 3]

There are changes and improvements coming to Slim Center with some of that functionality. Also, SuperSU is gone now, replaced by koush's new su client.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] LeeC:
Noticed that koush's su has been integrated into the ROM:good:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ameanl:
Hi, I just wanted point out that I had a problem, I am not sure if it's a bug or not.

The menu button long press starts up google search... I like google voice command so I have it installed.

When I go into interface setttings to change hard key assignment, and go to menu and change it to "none" (what I am hoping for is that it does nothing), but it still starts the search. I can change it screen close or whatever else, but not to "do nothing."

If it's not a bug and is intended, can you look into a "do nothing" command.

Thanks.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] 12packabs:
Some launchers, like Nova, also allow you to map buttons. Could it be in your launcher settings?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jasvncnt1:
Hi all. Just flashed ROM to try it out. Only thing Im trying to install a different mms.apk. As soon as I go into type the message it force closes. Is there no way to swap out the mms.apk?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] t3chn0s1s:
Re: [ROM][4.2.2][March 29] Slim Bean-d2(att/bell/telus/rogers) [build 3]

Essentially you should be able to copy/paste the MMS.apk into system/app, reboot and it should work. I've never had a problem swapping them out. Keep in mind the breathing effect won't work nor will TRDS theme your MMS app. Did you try a different apk or just the one?

Sent from my Galaxy S III
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] bjtheone:
Tethering over LTE

Happy day... found how to get tethering to work over LTE. Basically need to tweak the iptables... details found in:

http://www.androidcoliseum.com/2013/03/how-to-enable-nexus-4-lte-tethering-on.html

You do this by creating a script containing the following:

#!/system/bin/sh
# Configures iptables to allow tethering over LTE
# Works for Samsung Galaxy SIII running on Rogers
iptables -A bw_FORWARD -i !lo+
iptables -A natctrl_FORWARD -j RETURN -i rmnet+ -o wlan0 -m state --state RELATED,ESTABLISHED
iptables -A natctrl_FORWARD -j DROP -i wlan0 -o rmnet+ -m state --state INVALID
iptables -A natctrl_FORWARD -j RETURN -i wlan0 -o rmnet+
iptables -A natctrl_FORWARD -j DROP
iptables -A natctrl_nat_POSTROUTING -t nat -o rmnet+ -j MASQUERADE

set it to run as root on every reboot and voila, it allows tethering over LTE at civilized speeds.

An easy way to do this is to use the scripter tool in ROM Toolbox or create a script in /system/etc/init.d that executes the commands above (don't forget to set the permissions to executable!).
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jasvncnt1:
Re: [ROM][4.2.2][March 29] Slim Bean-d2(att/bell/telus/rogers) [build 3]

Thanks. That's exactly what I did. Opened up fine and let me pick my contact. But as soon as I tab the field to type if FC's. Actually I haven't been able to get it to work on any ROM. Its just the MMS from root box. I'm stumped.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] t3chn0s1s:
Re: [ROM][4.2.2][March 29] Slim Bean-d2(att/bell/telus/rogers) [build 3]

That's bizarre. I've mixed and matched diff ones from diff ROM's and never had an issue before. Just for the hell of it did you try clearing app cache/data and/or cleared Dalvik/Cache and fixed permissions?

Sent from my Galaxy S III
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] blaze0303:
So I flashed this last night coming from CM10 and it bricked my phone. Thread is here if anyone cares to help :)

http://xdaforums.com/showthread.php?t=2218431
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] AtoZ0to9:
This ROM doesn't brick phones, so don't say that it did, you've done something wrong...
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jasvncnt1:
Re: [ROM][4.2.2][March 29] Slim Bean-d2(att/bell/telus/rogers) [build 3]

I know. I've done this in the past and no issues Lol. I did all that except I didn't run fix permissions. I might as well give that a shot.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] y0yerrj0sh:
Did you flash the d2att image?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] stevehkim:
Looks like you flashed the wrong version of the rom. Do you have an international version SGS3? Or a US Variant S3? Ain't no slimbean rom or any rom posted here gonna brick a device. 100% user error. I think you should edit your post because your giving people the wrong idea of a highly tested, researched rom from an awesome team of devs.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] 1weener:
You might consider not doing a long press, which effectively would be adding the do nothing command. ;)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] t3chn0s1s:
Re: [ROM][4.2.2][March 29] Slim Bean-d2(att/bell/telus/rogers) [build 3]

Is there another similar MMS.apk you can try? Or maybe its a bad download?

Sent from my Galaxy S III