yashsingh1/xdaforums huggingface dataset:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] bjtheone:
I posted the script last week in the thread... :)

#!/system/bin/sh
# Configures iptables to allow tethering over LTE
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

Sounds like you might have a different issue if it works sometimes and then randomly drops the connection. Can you expand on anything that is happening when it stops, distance from your phone to your tethered device, are you stationary or moving, is the phone dropping from LTE to 3G, or going from 3G to LTE?

Or does it seem to drop after a set amount of time or amount of tethered data? If the later, you may have a carrier blocking issue. Is your data plan suppose to include tethering and if so have you called your carrier to verify that the appropriate features lines are set?

For me, on Rogers, using the "stock" tethering built into Slimbean, tethering never works over LTE (as far as I can tell data just does not get routed through from the wifi interface to the radio). Connectivity on the wifi side, between the tethered device and phone and between the phone and network is solid and I have no issues with things like DNS lookups. If I drop down to 3G everything just works.

With the iptable script, tethering is rock solid over LTE, using the built in tethering.

Doing some digging it seems that it has to do with Google now (after 4.1.1) setting a flag that reports data packets originating from a tethered device to the carrier, and the carrier blocking or dicking around with the APN. The end result is blocking data packets flagged as coming from a tethered device., which is exactly what I was experiencing.

Of course, my data plan is supposed to include & allow tethering but Rogers may have decided to interpret that as over 3G only, or they may have just messed up my account again (I have a rather odd plan, with a combination of corporate features, grandfathered data rights, and LTE additions). In that context, the iptables fix makes sense and I am perfectly happy not to spend hours arguing with various Rogers support folks to possibly get it changed.

See:

http://code.google.com/p/android/issues/detail?id=38563

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

from more background.

Some folks have reported that using a tweaked "Wifi Tether for Root Users" works with 4.2 based ROMs. I played with various version of that but could never get connected.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] :
Is this 3.0 or 3.4?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jproy12:
It's 3.0... they are working on the 3.4 version, and according to some earlier post, we should be seeing it as the next version.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] CZ Eddie:
edit
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Nautiliux:
You could get the 4.2.2 installed without problems .. end up doing full wipe installation in Gs3 i747m
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] joeyl:
is there a mod for the lockscreen handle? I flashed the zip file to revert to stock AOKP lockscreen icon handle but it did not do anything? I am using the nexus stock wallpaper and the black hole with slim logo in the middle clashes ;)

thanks
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] aaroncal:
Just flashed last night and running at 1026 MHz and get awesome battery life music player is wonky but overall this thing runs great...nice job!!!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Brooklynsour:
U can uninstall default music and install one u like
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] t3chn0s1s:
You might want to try downloading the latest one. It worked just fine for me. A few builds ago I had a problem where it wasn't converting to the stock handle and it turned out it was a bad download. I re-downloaded and it worked fine.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] joeyl:
thanks I redownloaded and flashed it is all good now!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] AznImport:
Freezing/locking up on Phone

Ive been using this Slim ROM as my daily driver for quite awhile now and everything has been working great. Since the last 2 updates my phone has been freezing while on call (it happens randomly, sometimes it freezes, sometimes it doesn't). I use my phone for calls quite often and this has happened for maybe half my calls. Again, this

ONLY

happens when I am on a phone call, ROM is flawless otherwise. I've tried a clean install and same thing happens. Hopefully this issue gets fixed soon =)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] momyc:
I concur with that . Actually it happened to me twice since I update to R3 and I noted that it happened at the end of the call when I press "End Call" on the screen . I believe once I press end call but it took a while to hang up as I can still hear the other side and then it freezes . Could be the modem ? I'm using the latest Bell MLL1 one.

Otherwise very happy with the ROM .

Thanks,
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] z34370z:
This has to do with a bug in the ROM. This will probably be fixed during the next release when the cm changes are merged. As I have been using a newer ROM with 3.4 kernel and don't have this issue anymore.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] voidstab:
maybe helpful, maybe not

I was experiencing this same issue while at work, at the time I had just flashed the latest BMS kernel and was blaming that. I flashed an older BMS kernel and later that day re-flashed the latest BMS kernel again and haven't experienced the issue since.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] blk_jack:
This is an upstream issue that affects all d2 4.2.2 ROMs regardless of if you're using the 3.0 or 3.4 kernel. It's completely random (I've only had it happen once ever) and is an upstream issue. Not only that, but it's specifically mentioned as a known issue in the build 3 Changelog.

Please read that changelog if you discover an issue since obviously it's pointless to report bugs here that we were aware of before the build was even released publicly. This goes for any Slim build.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] aaroncal:
Did just that been using rocket music player
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] bjtheone:
Firstly I want to make clear that I am very impressed with the Slimbean ROM. It is the best one I have found for my S3. I agree with the design philosophy, like the dark look and am impressed by the stability.

I also appreciate the effort the dev team puts into it and the support provided.

However I do disagree with your comments about this bug. I did not perceive that folks were just *****ing, whining, or blaming the dev team for the bug but rather commenting on it and how it impacted them. I absolutely agree that it is both upstream, and documented in the changelog. However it has a serious impact on folks that absolutely need calling to work. I run a small contracting business and use my cell as my main client interaction tool, especially in the initial states of quoting jobs. To date I have had 9 call related crashes, 6 at end of call (which are annoying but just require a forced reboot) and 3 during the call. For me the impact and risk is large enough that I am seriously comtemplating going back to a 4.0.4 based rom to get rid of the bug. For me, the comments and experiences of others that help me judge the severity of the bug are both relevant and helpful.

Any insight you could share on any things that could be done to minimize the call bug would be appreciated, since it does seem to impact some folks more than others. More importantly any information you could provide about hte likelyhood of this getting fixed upstream and then pushed out by the Slimbean team would be greatly appreciated.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] HiKsFiles:
If you rely that much on your phone, then you shouldn't temper with it in the first place.

Custom ROMs will never be as stable as official releases from the OEM.

In my mind, if you so desperately need stability, stick to the official thing and maybe just root it for backup purposes (TiBU, CWM, etc...).
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] bjtheone:
Actually my experience, going back 25 plus years with Unix workstations & PCs and 15 with PDAs & smartphones is exactly the opposite...

The entire process with open source, and small dev team software has been much better. Bugs are fixed faster, more options available, often able to interact directly with the dev team, can pick and chose the features I want or need.

The fact that I may be able to get a reply from the dev team on the call bug is light years better than what I would get from Samsung. Plus after Samsung fixes a bug I would have to wait months, years or never actually get the fixes pushed by the carrier.

For exampe: the 911 bug on the HTC magic was initially denied, and then took over 6 months for the first fix (which did not work). I had a fix within a week on a custom rom. My Dell streak took almost a year to get an update from the carrier and never got the second promised update. Was rocking current android releases the entire time. Same expereinces with my S2 and S3.... custom rom are MUCH better than stock for support, flexibility, features, and if you are selective about what you flash, stability.

Like I said, I find Slimbean way better than stock. In my experience it has 2 bugs... the call related one, and tethering over LTE (which seems to be due to the new "tethered" flag Google implemented and how my carrier interacts with it). I have a fix for tethering. The call bug is an issue for me if it is going to impact calls in progress. At first I only saw it at call end, but I have since had three instances where the phone freezes mid call.

I have never had a freeze or reboot other than the call related one. Other than this one bug the rom is rock stolid and stable. Howver, given that I need calling to work (especially to not drop calls) I may go back to another custom rom based off 4.0.4 that was less feature rich, with other issues , that did not have any call bugs.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] blk_jack:
That is not entirely true. Almost all the issues that come from upstream are related to closed source libraries. The reason why custom ROMs for a non-nexus device are going to be less stable than their official counterparts is because we have to deal with closed source blobs.

So while some other bugs may be fixed quicker, those bugs are usually aesthetic or superficial in nature. The S3's history with AOSP/CM and such has never been bug free. 4.1 AOSP/CM based ROMs for the d2 had numerous bugs of their own that in most cases didn't get fixed before 4.2 came out and support was dialed down or dropped.

Also consider that very few ROMs have original code/features. I'm not trying to be insulting or particularly single any ROMs out, but ones such as Carbon & Liquid are based entirely off other ROM's features/fixes and the teams of those ROMs have few, if any, actual developers involved. There is this illusion amongst XDA users that all ROM chefs are actual developers. That is not true at all. Most ROM "devs" simply combine and kang commits from other repositories and mash them together. This means that most ROMs and most ROM devs are simply not capable whatsoever of fixing larger issues that relate to hardware.

Most of the fixes (and new issues introduced) that you'll see actually come upstream from Qualcomm themselves.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] bjtheone:
Not disputing what you are saying. However the rate of bug fixing, interactions, and accessiblity is much better in my experience than with a large coprorate process further muddled by carrier rules and requirements. Due to nothing else, that as soon as a closed source releases a fix visible to the community, it will get pushed out in a good custom rom without waiting for lengthy integration/stability testing by the oem/carrier or the oem/carrier making the business decision to never release it.

I also completely understand the differences between orginal material devs, tweaker devs and chefs... and factor that into the custom roms I choose to run... :)

That all begin said, do you have any idea of the likelyhood and timeline for a fix on this issue, given that random bugs are a ***** to reproduce and fix, and how far upstream it is? Is it believed to be in google or qualcomm code or is that even known?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] blk_jack:
Honestly I know very little about the phone call lockup issue. I've done zero debugging and haven't looked into it beyond knowing that it's an issue affecting multiple devices across a whole variety of ROMs. You're right in that it's a more difficult issue to debug due to its random occurrence, but in general I simply haven't suffered from it myself (except once), so I'm concentrating on other issues I'm able to reproduce more reliably, like the bluetooth hang bug when turning off.

Also the development I typically do for slim involves feature additions rather than debugging obscure hardware issues, so I'm probably not best suited to look into it.

Maybe it's affected by kernel frequency or voltage tables though. I mostly use interactive governor with my addon kernel and keep stock voltages. More information on your kernel setup could help, though this issue also occurs on CM but maybe different setups reduce the frequency in which it happens.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] bjtheone:
Sigh... never a magic wand when you need one.

Unfortunately I am running the stock kernel that comes with Slimbean, with what I believe are the stock settings for scheduler (interactive) and min/max (384/1512) frequencies. I also tend to have very little background stuff and widgets running as I want stabilityand battery life, not bleeding edge perfromance.

That being said could folks chime it with what kernel setups they are running, ESPECIALLY if they make a reasonable amount of phone calls and never or rarely see the call freeze bug.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] HiKsFiles:
That's precisely my point, altough I totally agree with you that support from devs here is usually far better than the one from OEMs.

But I still think that people whose professional life depends on a perfectly functionning phone should refrain from using custom ROMs, especially AOSP based ones on non-Nexus devices, due to the inherent limitations the devs are facing with the integration of closed source libs.

With that being said, I can understand your frustration. :)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] wcoast:
I respect your view but 110% disagreed, custom ROM in all shape/form is uncountably better than stock
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] toonwar:
Have you tried ZPlayer? Its a nice music player that runs similar to the Microsoft Zune device.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Grillrd:
It was mentioned here at the beginning of the thread but haven't seen a fix for the capacitive buttons not lighting up. Went through all pages of the thread. Is there a fix?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] gmillz:
The fix will be in the next release.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jproy12:
When using this ROM, when unlocking the phone, i get somewhat small rectangle, the size of the screen on the left side of the screen, is this normal? Am I the only one?

Really looking forward to the BT fix as well!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] CrackerTeg:
That is to create lock screen widgets. Perfectly normal.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] finneginsfast:
I can't change the i/o scheduler in performance. It just defaults back to cfq every time.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Software Guy:
I have to say this rom is great. I have not tried to set up my blue tooth to either car (my pioneer stereo is very picky.) but it's fast and sleek. Battery life is awesome.

Thanks!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jpride:
FYI. Bluetooth people.

Depending on the app, my Bluetooth Audio streaming seems to be working. I just tested with Subsonic Streamer, both streaming online and local music sitting on my phone. Neither of those worked, i.e. erratic pacing, static clips, etc. I also used Audible to play an audiobook and it worked fine for about 5 minutes. I even turned the screen off to trigger the effect. Nothing. Maybe its not the best quality ever, yet. But its something. *shrug*
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] roman5566:
I know im probably late with this but its funny as hell to me, he's gonna check under his bed....
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] tonorice:
Exhange not resolving

I'm trying to get exchange working. I installed the extra's package which I read had exchange in it. When setting up the account it resolves the domain and all account info however when finalizing it comes back with a edit details message. I have double checked every setting and port they're correct. Is there something I'm missing or is it just not working in this build?

P.S. BEST rom I've ever used.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] grotz497:
Edit: I'll preface this with awesome ROM and definitely appreciate your work!

I don't believe I saw this mentioned before but is anyone having issues with google navigation on this ROM? GPS locates me just fine but can't get it's act together to actually navigate.

Wiped everything when I flashed, no other (new) issues, flashed latest modem this morning but still no improvement. Any ideas?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jpride:
GMillz,

I dont know if you are still working on this ROM, in particular, the Bluetooth stack issues. But I have recently had some luck with the A2DP issues using the Official 4.2.1 beta 2 release. I had Audible streaming good stereo audio (bass intact) for about 30 minutes last night.

I modified some of the parameters in the main.conf and input.conf files located in /System/Etc/Bluetooth. If you are interested in pursuing a solution to the issue, let me know, I will try to catch the onset of the static/pacing issues in a logcat.

Here is the 10,000 foot view from a novice (read: Saluton Mondo!) Java/Android programmer: since the phone can consistently pair to my vehicle and stream audio just fine for a limited amount of time, it would seem something is going lopsided in the buffering scheme only after a significant amount of data has accumulated. This might indicate a mismatch between the two devices' streaming parameters, i.e. IdleTimeout, DeviceID, PageTimeout, or DefaultLinkPolicy. (Yes, those are all Config variables easy accessible in the "main.conf" and "input.conf" files.) Or it could just be a CODEC issue. meh.

I am a programmer (C#, other more esoteric proprietary langs) by occupation, and from my experience, when I run code that works at first but gradually falls apart, it points to a tweaking of the initial conditions, generally.

Ignore this post if you have no interest. We can all just wait for Google to fix it, I suppose.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] prbassplayer:
I can't speak specifically for this issue but I can say the whole team is working really hard on the next release ;)

Sent from my Slim Bean powered Mako
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jpride:
Thanks. And awesome.

DEVS --> Logcat attached, if interested.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Gandalf:
Google fixed the A2DP issues with 4.2.2. So hopefully that fix can be brought down to 4.2.1 and therefore brought to us. :good:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jpride:
Yeah, I saw that. I officially give up trying and await the fix.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] nae10135:
Giving thanks

As a modder / jailbreaker since my HTC Hermes back in the day, the xda community has come a long way since 2006.

Slim Bean 3.1 is my Daily driver, and I am absolutely thrilled with it. Many thanks to all the Devs spending their free time on a solid 4.2 release. I'm looking forward to the improvements.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] oriveradel:
Apparently 4.2.2 its specific to LG phone not go for samsung phones, devs not bothering with it
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Haighter:
BT Issues

Bluetooth works fine in 4.2.1, it's not Google's fault because nothing is wrong with it. When it got brought into our device, something that had to be done to get it to work in our G3s kicked Bluetooth in the teeth. That is what the devs are trying to work out. There is no guarantee that the same thing would not happen with 4.2.2.

But I am sure that soon they will get the kinks worked out. I know they are working hard on it.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Gandalf:
Well madmack just compiled a working 1/16 nightly of CM10.1 earlier today with working A2DP. we established that it wasn't Google or AOSP source, but something that was caused by the device. However we DO have a build with working A2DP from 1/16 now in the CM10 thread.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SeanHacker:
True. But other things aren't working now. That's exactly why CM is not reverting considering its not the proper way. All madmack did was revert a couple common repos in order to have working A2DP. Yes it works. I've done it myself. But it breaks things. I'm sure the culprit will be found soon. I'm pretty sure the audio-caf repo is one of the major causes.

P.S- Technically thats not the 1/16 build. That is a build from December now. ;)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] baconatorXVI:
I'm on one if the latest 3.0 kt747 kernel releases, I haven't had any of the call reboots that you mentioned.

I aggressively undervolt my min is 81mhz and I use ktoonservative(modified conservative governor) with my thresholds very high tuned for battery life. As well as aggressive hot plugging

I have some of the farthest from stock settings and I have yet to experience a call reboot.

I'm doubting it's a kernel settings related issue. You could always flash his kernel and try it out...

Sent from a Galaxy far far away...
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] aaroncal:
Opinions belong somewhere other than the development thread
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] bjtheone:
Given the lag in my carrier pushing out updates and my utter dislike of touchwiz stock is not an option. :) Plus look at the disaster that is the latest stock update to the Galaxy Note 2. Unfortunately stock does not mean stable.

I have run stripped down stock based roms with alternate launchers but honestly I find aosp based, without the samsung framework to be better performing and more stable.

One of my sons has a bone stock S, another a bone stock S3. They both have more issues than I do and I have way more apps loaded and spend way more time actually using my phone.

Also find the code size difference rather staggering:

Slimbean 4.2.2 - approx 168 Mb, GApps - another 24 Mb

Stock - approx 1.2 Gb

Like I have said, my experience with custom roms has been fabulous, both from the perspective of access to the latest Android versions and from support and stability.

Case in point, one of the Slimbean devs took it offline with me and gave me access to a beta build that might assist in addressing my issue. I had trouble getting that level of access and support when I was spending millions of dollars on support for ASIC cad tools in a former career.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Brooklynsour:
Yea the freeze has been happening at least about twice a day... Is there something I can do while its frozen to help understand why it happens or what can be done to not freeze?