yashsingh1/xdaforums huggingface dataset:
[T-Mobile, Samsung Galaxy SIII] blk_jack:
This isn't me being rude :) If I was rude you'd know it. I'm being matter of fact in letting you (and other new users) know the general protocol for narrowing down issues and doing some legwork before you make a post in any XDA thread.

You have to understand that on a daily basis, in the 6 Slim Bean threads I run/maintain, I get asked many questions. A large majority of those questions fall into the realm I covered in my previous posts.

That said, the problem isn't instagram or the ROM, since there are many d2tmo/d2att users who run it without any issues whatsoever.
[T-Mobile, Samsung Galaxy SIII] corlissak:
No worries. Like I said, Instagram isn't that big of a deal. I can just uninstall it. I was just curious. Thanks
[T-Mobile, Samsung Galaxy SIII] edit28:
Google Navigation will FC on me after about 5 minutes. Sometimes after it FCs the navigation icon will remain in the status bar and will even re-connect on occasion, however usually it just kills the process. This has been a recurring issue for me throughout the last few SLIM builds :(

Steps taken to (attempt to) solve:

Tried clearing dalvik/cache (still FCs)

Tried to ODIN back to stock then reflash (still FCs),

Tried various other modems (still FCs)

I also get a strange popup when starting Navigation that states, "For voice-guided navigation, you need to install text-to-speech support from the Android Market" even though the voice projects just fine without the addon (have to skip this prompt every time Navigation is started). Directions work fine from GMaps, it's only when the active GPS navigation is running that I get the FC. Any ideas on a fix?
[T-Mobile, Samsung Galaxy SIII] imilleson:
Go to "manage apps" and click Maps. Click "wipe data", then force stop. Now restart and see if that has helped. If not I would clear the google services framework as well... If that still doesn't work do a factory reset. When you Odin to stock it can still leave crap behind, so in cwm format /system and wipe data before reflashing this ROM
[T-Mobile, Samsung Galaxy SIII] abc123pro:
Yep.. And if that doesn't work for you I think there was a discussion on the navigation issue a page back or two. Think they were able to get it fixed
[T-Mobile, Samsung Galaxy SIII] corlissak:
I'm almost afraid to post this for fear of being jumped on but whatever. I just want to know is there a reason why I'm always showing 3g and never 4g? Also, in case anyone was wondering, I figured out the Instagram issue I was having (phine reboots when trying to post a pic) only occurs when I use the front facing camera. Any suggestions to either? If not, just scroll on passed me. No need to be rude. Thanks
[T-Mobile, Samsung Galaxy SIII] imilleson:
Our phone gets 3G and HSPA+ but not LTE. So the H you see is the same as the 4G you see in stock ROMs . As for the front facing camera issue I have no idea
[T-Mobile, Samsung Galaxy SIII] richardlibeau:
Occasionally I get h+ when i used to always be on hspa network not utms all the time on my s2. Now i am mostly on 3g and utms don't get it. People were trying to say that the phone was lying. In mobile network it clearly said hspa, hspa+, hspa 10, or dc. You can't change that it comes from the company. So i figure if the S3 is supposed to be better than how come I never stay at hspa. Seems like S2 got better signal.
[T-Mobile, Samsung Galaxy SIII] MV10:
In some parts of town I get H+ pretty steadily. In other places it kind of flips back and forth from 3G to H+.

Unfortunately, nearly everywhere I spend a lot of time, I get EDGE more than anything else.

But I've seen H+ for very long periods of time. In fact, when I was out in Austin on business, I had H+ for about four straight days downtown.

In fact, I've been meaning to research how to complain to T-Mo, since I get weak EDGE at my home and office.

Oh, and don't bother with their signal booster. The booster has to see 3G -- if it could see 3G, my phone would, too...
[T-Mobile, Samsung Galaxy SIII] corlissak:
That's the thing, I NEVER see the H.
[T-Mobile, Samsung Galaxy SIII] jdidtht:
So when u are using the web or etc it doesn't display the h? Most ROMs will display the h only when data is actually being used or sent but if it never displays it i would try flashing a different modem that works vest in your area. Especially if you came fro. A clean wipe

Absolutely Infected SGH-T999
[T-Mobile, Samsung Galaxy SIII] jpcdeux:
It drops to save data use, etc. If you pay attention soon as it uses data it kicks up to H/H+ and then back down when no data is being sent/received

Unlike some carriers that label everything "4G" as a gimmick.
[T-Mobile, Samsung Galaxy SIII] corlissak:
Nope. It never displays the H. Flashing a different modem? What do u suggest?
[T-Mobile, Samsung Galaxy SIII] jzun223:
You should try a speed test of the Internet connection. Like that it can help you determine if you really are getting 4g speeds or if it's something visual that's not being displayed properly.
[T-Mobile, Samsung Galaxy SIII] corlissak:
I did the test. Attached is a screenshot of it. What does it mean?
[T-Mobile, Samsung Galaxy SIII] jzun223:
That is definitely 4g speeds. That's 15 Mbps. Not bad at all if you ask me.

So that means it's just not properly displaying the 4g or H+ icon.
[T-Mobile, Samsung Galaxy SIII] corlissak:
Oh ok well that's good to know lol. Is there a fix to make the 4g or H icon show up? Just curious
[T-Mobile, Samsung Galaxy SIII] jzun223:
Not that I know of. I haven't experienced that. When I was running the ROM it would display H+. I guess a place to start would be a re-download and flashing again, but that may be a little bit of a pain if you have set up everything already.

Idk if someone who has experienced that can say what they did.
[T-Mobile, Samsung Galaxy SIII] corlissak:
Front Camera

I've noticed that any time I try to use the front facing camera with any apps, the phone reboots. The only time I can use the front facing camera without the phone rebooting is when I use the regular camera. Anyone else experiencing this? Suggestions?
[T-Mobile, Samsung Galaxy SIII] Naturesretard:
The way the ROM works is when you're not using data it's 3g. Once you use anything that requires data it kicks up to h+ which basically means 4g. Its to save battery.

As far as FFC not working try doing a clean flash. I've had no problems with my front camera and I dirty flashed build 6 over build 5, but that was a clean install
[T-Mobile, Samsung Galaxy SIII] ace2153:
Gtalk

How can I get gtalk on this ROM I don't like hangout?
[T-Mobile, Samsung Galaxy SIII] garymachete:
Flash an old gapps?

SlimBean
[T-Mobile, Samsung Galaxy SIII] ace2153:
So the old gappswill work with build 6? What build should I use as far as the gapps
[T-Mobile, Samsung Galaxy SIII] garymachete:
Just download the latest official gapps from goo.im - 20130301

http://goo.im/gapps/gapps-jb-20130301-signed.zip

SlimBean & Ktoonz
[T-Mobile, Samsung Galaxy SIII] sc2ascend:
Great ROM, very fast and stable. Every now and then I get some minor flickering but its very minimal and not as bad as some of the other 4.2.2 ROMs. Thanks for this great release!
[T-Mobile, Samsung Galaxy SIII] tsunami2312:
is this rom getting Halo? just curious! :confused:
[T-Mobile, Samsung Galaxy SIII] garymachete:
Halo is aokp based and slim is aosp based so idk I wouldn't think so.

SlimBean & Ktoonz
[T-Mobile, Samsung Galaxy SIII] tsunami2312:
aopk based? i was almost pretty sure it was aosp based, because PA is aosp based,same as SLim Bean.. and since halo is PA feature..
[T-Mobile, Samsung Galaxy SIII] garymachete:
Oh that's right, well then, damn, maybe we will get halo

SlimBean & Ktoonz
[T-Mobile, Samsung Galaxy SIII] Shawn:
All of the custom ROMS here are AOSP based except for the ones that are stock firmware (Sammy)
[T-Mobile, Samsung Galaxy SIII] jpcdeux:
Search this thread. That was mentioned a few pages back by the dev
[T-Mobile, Samsung Galaxy SIII] theBunkinator:
It's amazing how quiet this thread is ... If you're considering this ROM, take this lack of traffic as a sign of how mature and solid Slim Bean is. Go ahead and install it already!

(This is my first post on this thread after 6 weeks of using it. About time to say thanks.)

THANKS!
[T-Mobile, Samsung Galaxy SIII] LuigiBull23:
Got that right buddy. One of the most stable AOSP ROMS out there.
[T-Mobile, Samsung Galaxy SIII] DylanTheVillian:
they pushed a new weekly and i want to flash it but noooooo, the d2tmo build isnt ready yet :p

Oh well, i guess i have to be patient :p
[T-Mobile, Samsung Galaxy SIII] garymachete:
R u sure about that? Not showing up in my search. But I don't really care about halo so nbd. Link to his post?

SlimBean & Ktoonz

---------- Post added at 09:00 AM ---------- Previous post was at 08:57 AM ----------

Its up now

http://www.slimroms.net/index.php/d...mo/3285-slim-d2att-4-2-2-build-6-8-weekly-286

SlimBean & Ktoonz
[T-Mobile, Samsung Galaxy SIII] abc123pro:
Anyone else getting this issue / knows a fix for the camera? There is nothing wrong with the pictures taken themselves but the screen looks stretched out when looking at something. Took a screenshot to explain it better.

(my hands aren't supposed to be that long :p)
[T-Mobile, Samsung Galaxy SIII] DylanTheVillian:
Turn off true view....
[T-Mobile, Samsung Galaxy SIII] abc123pro:
Tried that. When alternating between front and back cameras it gets narrowed again.
[T-Mobile, Samsung Galaxy SIII] Meanrogue:
gapps crashing after adding any account

Gapps gives the "Not responding" and force closes after any account is added (email, drive, facebook, etc). Seems like most of the stuff still works after it crashes, except for facebook, which will not sync contacts. Minor annoyance as I was trying to get all my contact pictures back, but not the end of the world.

Full wipe coming from Darth Stalker ROM. Tried re-installing the gapps addon and wiped dalvik. No joy. Everything else seems to be working smoothly.

Am I missing something obvious?
[T-Mobile, Samsung Galaxy SIII] LuigiBull23:
By full wipe I assume you also formatted the system partition?
[T-Mobile, Samsung Galaxy SIII] Meanrogue:
Yeah. That threw me for a second since I've never had to do that for the touch wiz ROMs.
[T-Mobile, Samsung Galaxy SIII] LuigiBull23:
You don't but if you're gonna jump from TW to AOSP formatting the system is required along with Data, Cache, and Dalvik Cache.
[T-Mobile, Samsung Galaxy SIII] Meanrogue:
No magic order to that right? I did the system format last. Also used CWM if that matters.

I was trying to see if anyone else had this issue before I went through a second complete reinstall.
[T-Mobile, Samsung Galaxy SIII] LuigiBull23:
Nope there is no specific order unless stated otherwise by the dev. Like I said just make sure you do wipe System, data, Cache, and Dalvik Cache before flashing the ROM and gapps. This is completely optional but I would also suggest wiping your internal storage as it can collect leftover junk from previous ROMS and potentially cause issues as well.
[T-Mobile, Samsung Galaxy SIII] jpcdeux:
Yeah, I get that too. I just deal with it lol
[T-Mobile, Samsung Galaxy SIII] trofmoc:
would appreciate

If someone has copy of 6/08 nightly would be very thankful
[T-Mobile, Samsung Galaxy SIII] LuigiBull23:
There are no nghtlies. There are only weekly builds. Here's the 6.8 weekly build if that's what you were referring to.

http://www.slimroms.net/index.php/d...mo/3285-slim-d2att-4-2-2-build-6-8-weekly-286
[T-Mobile, Samsung Galaxy SIII] trofmoc:
thanks alot

this is the one. only one that works bt stereo headsets faithfully.
[T-Mobile, Samsung Galaxy SIII] 2pac4life:
I have a the S3 T-Mobile but it is unlocked for ATT? if i flash this rom will i still be able to use ATT Service? My Phone is International....
[T-Mobile, Samsung Galaxy SIII] garymachete:
You should be fine

SlimBean & Ktoonz
[T-Mobile, Samsung Galaxy SIII] rani9990:
Do you have a GT-I9300? Because you say your phone is "international". Then don't flash this.
[T-Mobile, Samsung Galaxy SIII] mentisimperium:
This rom has been so smooth and stable, I am ashamed i haven't tried it earlier.

Also, I downloaded setcpu and changed the governor to powersave, INSANE BATTERY LIFE!
[T-Mobile, Samsung Galaxy SIII] garymachete:
Yea if you have the GTi9300 then dont flash this. If you have the t999 unlocked to work with att you will be OK.

SlimBean & Ktoonz
[T-Mobile, Samsung Galaxy SIII] popimp315:
With build 6 do you have to use a 3.4 kernel or can you use a 3.0?
[T-Mobile, Samsung Galaxy SIII] LuigiBull23:
3. 4
[T-Mobile, Samsung Galaxy SIII] bouzouki:
New nightly running great as usual. Any chance halo or the sidebar launcher will be in any future releases?
[T-Mobile, Samsung Galaxy SIII] blk_jack:
Halo is still under code review. There are a few bugs and issues with it that we're not completely comfortable having in the rom. These issues apply to all ROMs with halo mind you, but we're looking into them and can hopefully address them in the near future and include halo in slim.
[T-Mobile, Samsung Galaxy SIII] popimp315:
What version was the last 3.0 kernel version

Sent from Planet Vegeta
[T-Mobile, Samsung Galaxy SIII] oddspec:
I wanna say build 3 but I could be wrong
[T-Mobile, Samsung Galaxy SIII] karmendc:
I've started to get FC/random crashes saying, "unfortunately Google.location.process has ended"

Any ideas on what could be happening? Everything has been running fine for weeks until now. The only thing ive done was install Google maps and then promptly uninstall it..

Oh i should mention I'm running the latest weekly release but it was also doing it on the previous weekly.
[T-Mobile, Samsung Galaxy SIII] oddspec:
Maybe fix permissions in recovery if it keeps.doing redownload the ROM and clean flash full wipe
[T-Mobile, Samsung Galaxy SIII] karmendc:
Yeah I've already fixed permissions and it's still doing it. Worst case, I'll wipe it like you suggested but i was really hoping I could work around that lol
[T-Mobile, Samsung Galaxy SIII] abc123pro:
I had this error too but only after restoring maps/street view from titanium backup.

Maybe clear the data for both those apps and then uninstall, restart and reinstall. I did something along those lines but yeah if you can't get that to work you could try just reflashing the slim gapps. Hope this helps man

Oh! And also under Google accounts in settings make sure everything you want to sync is checked. If there's a sync error keep rebooting and manual syncing til it goes away
[T-Mobile, Samsung Galaxy SIII] LuigiBull23:
Build 7 is out the oven!

http://www.slimroms.net/index.php/d...-d2tmo/3564-slim-d2att-4-2-2-build-7-official

Changelog

http://www.slimroms.net/index.php/changelog/343-build-7-changelog
[T-Mobile, Samsung Galaxy SIII] getrdy:
How much screen on time do you have ? Anything around 3h of screen on is good. (3h with 10-15% battery left)
[T-Mobile, Samsung Galaxy SIII] flykeyz:
Anyone having problems sending MMS while WiFi is on?
[T-Mobile, Samsung Galaxy SIII] blk_jack:
Build 7!

SlimBean 4.2.2 build 7

Ok guys stable Build 7 is out!. Tons of changes since build 6. Read carefully changelog and install instructions.

Small hint: If google now may get an FC on starting due to old data from the previous version. If you run into this problem...uninstall google now, reboot and install it/flash our gapps package again.

You do not need to wipe between releases. buuut if you do have problems full wipe, reproduce & report appropriately ;)

Changes, Features & Fixes:

d2

d2: Enable stereo mic

6.2+

Improve LPM support

Add sysinit

Add Fido Canada APN

Add Samsung Qcom RIL

Add Samsung Exynos RIL

Fix MAP SDP record generation

Update bcm43241 firmware to version 6.10.170.4

Fix sms sending and reciever declarations

Fix wrong log information in DevicePolicyManagerService

Fix Expanded Mode

Camera button rebinding and lockscreen action additions

Slim Center fix delete dialog string behavior

Fix cursor leak

DashClock updates

6.5+

Seperate multipart sms settings from size

Add Personal Argentina APN

Fix 0% battery QS tile

Fix MMS possible NPE

Filter picasa specific options

Add an AlertDialog before deleting APN

Fix for several touch key duration bugs

6.8+

Update DashClock

Update MAP code from upstream

Fix possible loss of custom ring tones

CM optimizations for skia

Expand profiles

Fix Mms FC in low memory devices

Add Statusbar Quick Peek

LCD density backup

6.9+

Add gps indicator to camera

Fix profiles BT on or of when in a intermediate state

Add BT triggers to profiles

add triggers to change profiles based on AP

Fix aapt warnings

Fix quick peek

Add 2G/3G to profiles

Add Solvaei APN

Reduce observer footprint on many Slim features

7.0+

Add QS and Notifications to navrings

Add Privacy Guard

Add Privacy Guard Manager (Settings->Security->Privacy Guard)

Add SMS Middleware layer

Add option for subtle vibration notification during calls

Make contacts apps aware of blacklisting being disabled

Removed all init.d scripts

Many translations updates

Many other optimizations and fixes

Add support for m7att and m7tmo

Privacy Guard

​
[T-Mobile, Samsung Galaxy SIII] abc123pro:
This has been my favorite ROM for a while and I've been waiting on build 7. Thanks for such a flawless build
[T-Mobile, Samsung Galaxy SIII] droidsung:
Everything works perfect on the new build 7. Very stable and the battery life seems to have gone up atleast by 10%.

However, I might be missing something here but I somehow am not able to change my volume from the lockscreen. Any idea how do I go about doing that?
[T-Mobile, Samsung Galaxy SIII] abc123pro:
I've never been able to do that, phone always has to be unlocked to do so, no? at least if its password protected
[T-Mobile, Samsung Galaxy SIII] droidsung:
Actually, I think I figured out what the problem was. I was using the Halo HD launcher up until Build 6. Only this time around I switched to Apex Pro.

I am thinking the Halo launcher has a built in feature that allows volume adjustment from lockscreen - Apex doesn't.

I am on the default "Swipe to Unlock" so can't really say if volume adjustment from lockscreen works when the Password protected option is selected but I can assume it would work.

Close to 4 hours screen time for the new build 7. I'm impressed!
[T-Mobile, Samsung Galaxy SIII] blk_jack:
If you're getting FCs, you can get logs and it will tell you exactly why it's crashing. Get a log!
[T-Mobile, Samsung Galaxy SIII] kpizzle:
Just switched over to SlimBean from CM, and I'm loving it so far. Thanks to the team for all of your hard work. I'm looking forward to the better battery life.
[T-Mobile, Samsung Galaxy SIII] abc123pro:
4 hours?! What kernel are you using?
[T-Mobile, Samsung Galaxy SIII] kpizzle:
Also curious, is everyone running MD5 baseband? Or the LJC?

I ask because over on the CM thread, there was talk about some sort of issue with the MD5 and compability with AOSP ROMS where it causes a battery drain?
[T-Mobile, Samsung Galaxy SIII] LuigiBull23:
This is true along with overheating. It's happened to a lot of users overall running the MD5 bootloader. I'm on MD5 but running the LJC baseband. All is well on my end.
[T-Mobile, Samsung Galaxy SIII] kpizzle:
Good to know. I'll revert to LJC.
[T-Mobile, Samsung Galaxy SIII] TheSleezkIng:
Is thier a way to change the battery icon in build 7? Cuz if thier is I can't seem to find it and I like having the percentage available when I look at it lol
[T-Mobile, Samsung Galaxy SIII] LuigiBull23:
Settings > Interface > Statusbar > Battery Icon and bar style
[T-Mobile, Samsung Galaxy SIII] droidsung:
Stock.

Wheatley governor + Row scheduler

Min 192 / Max 1512
[T-Mobile, Samsung Galaxy SIII] MV10:
On build 6 and now on build 7, if I'm talking on the phone and try to pull down the notification area (for example, if a text message comes in), the screen turns off. I think this only happens once the screen automatically turns off the first time due to triggering the proximity sensor. In other words, if I'm on a call in speakerphone mode, so that the screen doesn't turn off due to the proximity sensor, then the screen and notification pull-down works normally throughout the call.

Just kept forgetting to mention it until now.

My biz partner is still on build 6 and he gets the same thing.
[T-Mobile, Samsung Galaxy SIII] LuigiBull23:
Sorry to hear this man. How soon after receiving a notification do you attempt to pull down the notification bar? Once you receive a notification and you pull your ear away from the phone you should give it a good 10-15 seconds before touching any part of the screen so your phone can have that little bit of time to respond to the touch sensors accordingly rather than responding to the in-call proximity sensors. Just a suggestion.
[T-Mobile, Samsung Galaxy SIII] MV10:
Heck, nothing to be sorry about, Slim rocks! I've been using it almost from the very beginning, and I'm amazed at the progress that has been made.

I do tend to go straight to the notification. I'll try waiting the next time and see whether that makes any difference, and report back.
[T-Mobile, Samsung Galaxy SIII] DesignGrits:
Just wondering, I am about to flash this on my wifes phone...but when I download all of the files from the slim bean site, while the files sizes do match the md5 listed under each build 7 files always fails. I have downloaded the build 7, gapps, aroma, and addons multiple times and they keep failing. Should I assume that the md5 numbers have not been updated since the files are the right size? Thanks.
[T-Mobile, Samsung Galaxy SIII] kpizzle:
Having some issues with my Facebook Messenger. It's not popping up the chatheads when people message me, and I'm finding missed messages when I log onto Facebook on my computer. I never had this problem before when I was running Cyanogenmod. I have my notifications turned on, I double checked all the settings within the app. Anyone else have this issue?
[T-Mobile, Samsung Galaxy SIII] LuigiBull23:
There was an update to the app just yesterday so it's likely due to that and not the ROM. Only way to be sure is by reverting back to the previous version and see if you have similar issues.
[T-Mobile, Samsung Galaxy SIII] o193746285:
The checksums listed on the slim site are sha1. You can either convert those to md5 or use a sha1 verifier.
[T-Mobile, Samsung Galaxy SIII] DesignGrits:
Oh, never heard of sha1, only ever used md5...got to Google it. ;D Thanks
[T-Mobile, Samsung Galaxy SIII] abc123pro:
The one time I had this problem installing a rom on a friend's phone, it turned out to be a corrupt SD card. Try installing from internal storage or a different SD. Assuming you're not already attempting to install from internal, in that case idk.
[T-Mobile, Samsung Galaxy SIII] DesignGrits:
Thank you, but I am just on the computer right now, haven't even touched her phone yet.
[T-Mobile, Samsung Galaxy SIII] abc123pro:
So sorry I misread your post. Thought you meant the installation was failing from recovery :P
[T-Mobile, Samsung Galaxy SIII] nirogu325:
I have just one question: is the low volume video recording bug still present? I read it was an AOSP issue with the GS3, but I'd like to know if it is there or not. I have this ROM installed in my old Samsung Vibrant and I'd love to install it on my GS3 without that bug. Thanks!
[T-Mobile, Samsung Galaxy SIII] LuigiBull23:
It is AOSP specific. Best thing you can do is flash a 3rd party kernel in which supports Fauxsound and use that app to improve video recording audio quality.
[T-Mobile, Samsung Galaxy SIII] oddspec:
I thought the stock kernel supported faux sound I know the att does

Edit : att/tmo share the same kernel from slim try it out on stock kernel ( I only say this cuz stock kernel is so battery effective and stable
[T-Mobile, Samsung Galaxy SIII] LuigiBull23:
True but that never exactly helped in my case. Using Fauxsound on KT747 is what made all the difference for me. Based solely on my results, I can only assume that the Fauxsound app will work to it's full potential depending on the kernel it's running on top of. So if no luck on stock kernel I would still suggest trying the same app but with a different kernel.