yashsingh1/xdaforums huggingface dataset:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] WaterMan!:
This ROM is working amazing. I have had issues on every other 4.3 ROM, such as random reboots, and randomly turning off and not being able to turn the device back on without a flash (bootloop)

However I am having a serious issue with my reception. I get around 30-40 network drops PER DAY, the internet just stops working or loses signal altogether, and it is extremely annoying. I dont want to revert back to earlier android versions because this one flies!

I have found a temporary solution that I think makes quite a difference, however it has to be done after every reboot. It is detailed here: http://www.androidpolice.com/2013/0...rops-on-some-nexus-4-handsets-fixes-in-sight/

Does anyone have a better solution? I am on Rogers, and this is really bugging the crap out of me! However flawless ROM other than this one issue
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] sdlopez83:
This may be a stupid question but where is the slim bean wallpaper located. I accidentally changed it while. I was changing the theme and want to revert back to the slim bean wallpaper but cannot find it.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SyNRGz:
Settings, Interface, Themes... (one way)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] dark_intel:
Awesome rom! Thanks Slim again, nothing but how Android should be. I feel sorry for those apple loving fks.

Xda I747
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Nishchhal:
Couldn't find the location of the wallpaper, but here's the wallpaper.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] fr3d0x:
Great rom

[YOUTUBE]APuiiPol8z8[/YOUTUBE]
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] basily:
I don't think it's the same issue. This was an old issue in Slim that was fixed way back in the 4.2.2 days. The difference is that the old issue would have bluetooth stuck on "turning off" which you would only actually see if you were in the bluetooth setup screen, meanwhile your battery would be taking a huge hit.

The current issue, that at the very least me and Level99 are having is that after you turn bluetooth off, it turns itself back on after 10-15 seconds.

As a follow-up, I have noticed that my phone does this consistently after connecting to certain devices, and not with others.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] RegBuckley:
Is it all your callers I heard people had problems with callers not on their contact list a few builds ago
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] bjtheone:
The way it works is that if the number sent down in the caller id info matches a number in your contacts, the name info from contacts is displayed. If there is no match the name field from the caller id info is displayed. The number info is always correct, so callers in my contact list are always correctly displayed. Something is messing up the character set so that unknown numbers get messed up name display.

I am also convinced it is an upstream issue. However, the fact that most carriers only provide number info for caller id and the fact that it seems to work for many/most people makes it a very low priority issue to address.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] hyewiz:
But how come only the LLE8 working correct, yes you are right its the contacts which are NOT in your list has the problem and not the one that listed.

I hope someone will come up with the fix soon.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] tbrummell:
I doubt a fix will see the light of day as the problem only affects Rogers users, and we are a small subset of people who use the ROM.

---------- Post added at 02:13 PM ---------- Previous post was at 01:21 PM ----------

Have any Rogers users had any luck getting WIFI tether to work? I for the life of me cannot...

---------- Post added at 02:41 PM ---------- Previous post was at 02:13 PM ----------

RE: WIFI Tether

I got it working.

Back story: Since 4.2, like alot of users, I've had to use GScript Lite to execute a script to get my tether to work. This solution was not working on 4.3.

The Solution:

I've need to add 1 more line to the script, courtesy of this thread: http://xdaforums.com/showpost.php?p=44419222&postcount=1

I needed to add the Flush command and it immediately started working, so here is my complete script I use in GScript Lite:

#!/system/bin/sh
iptables -F
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

Hopefully this helps other Rogers S3 users that want to tether...

---------- Post added at 02:43 PM ---------- Previous post was at 02:41 PM ----------

And my Speedtest when tethered:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] bjtheone:
Note: if you want to add the file to /etc/init.d, to get executed everytime the phone boots up, you need to do the following:

1) name it something starting with 99, like 99ltether, so it gets executed last

2) set the permissions to rwxr-xr-x

3) add the line "sleep 5" at the begining, right before "iptables -F", so that it gets executed after the interfaces finish coming up

4) Remember that /etc/init.d gets overwritten every time you flash a new ROM so that you have to redo this after flashing

Blk_jack, has the script, and it is likely going to be included into Slimbean soon.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] roadcarver1971:
I'm trying to add the 99tether script into etc/init.d but it reports that it's only a read only file system.

I have root access enabled, and in the developer options it has root for apps and adb. Am I missing something else?

Thanks.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] KuRuPtIoN:
The past few hours I been getting a message saying Messages has stopped, it happens every time I get a new text message. I don't ever use it, I use ChompSMS, anyone else having this problem?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] roadcarver1971:
I got script to work. I had to use ant tek file explorer to remount the file system as rw. Thx.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] bjtheone:
I think ChompSMS has some issues with 4.3. It would not send MMS messages for me, failed every time. Try Handsent SMS.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] atrix4nag:
It works perfectly. Thanks once again for the great rom.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] x10user2011:
wow it didn't boot up AGAIN. one reboot and it won't work again... I then went on to clean flash the newest release and the same error occurred.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] CrackerTeg:
blk_jack, a heads up on the bluetooth. This morning I got into my car like I usually do and went to pair with my car. It paired initially and then dropped the connection nearly 30 seconds later. No amount of reconnecting from my car or the phone will get the connection back. I'd literally have to unpair and re-pair only to have the same results. I hit the generate bug report in the slim center but don't know where it went. Its not on my SD card so I have no idea if it actually generated. I almost want to go back to my nandroid of build 8 to have a functioning bluetooth but I don't really talk to people while I'm driving anyway so its nbd.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jonnyjb:
I have 2.6 and it is working great so far.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Sajoeee:
how stable is this rom for you guys?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] CrackerTeg:
Extremely. IMO, it shouldn't be called a beta. That's how stable it is.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Azure1203:
Outside of the the 'cannot connect to camera' error that I had which seems to have been fixed with a flashing of beta2, it seems to be very stable and has better battery life than 4.2.2.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] blk_jack:
I've seen some reports of wonky bluetooth in other roms too. I haven't had issues myself, but it looks like it may be an upstream issue.

I'll keep my eye on it. Also, the bug report feature in developer options is broken. It's on our todo list.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] JayRolla:
I'm loving this rom. Always ran aokp and never could stick with anything else. Finally found something I'll stick with. Was looking for 4.3 goodness till task released his but think I'm staying put for awhile.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Swiftks:
Can you also post the .rle file and any other files needed for the splash screen image. I love the Slim ROM splash screen, but every time I flash a different kernel, the splash screen changes. I know it's in the boot.img, but I can't decompile it without Linux, etc.

Thanks
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] MercilessLTD:
I use Smart WiFi Toggler (because I'm lazy and ADH...squirrel!). I let it run in persistent mode, but to defeat the constant notification, I go to System Settings > Apps > Smart WiFi Toggler > uncheck "Show notifications". This, while remaining unchecked, does not stay over reboot. I have to go back into the App Manager, check and uncheck (and tap OK to the message). Then the persistent notification goes away again.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jpcdeux:
Does the stock lock screen handle work on 4.3?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] CrackerTeg:
Funny you mention this. Bluetooth decided to behave properly the last couple times I got in my car. I didn't make any calls but it was connected. Weird.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Chr0nicDreamz:
I have had similar issues with other roms. It turned out to be one of my devices going bad. Had it swapped out and have not had a single issue since
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Jep56:
Lost Root

Wiped, flashed and lost root! Any ideas?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jasvncnt1:
Read OP
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] LuigiBull23:
Really..? lol
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Jep56:
Jeeeeeeeeeez...I'm really sorry...I should know better by now! :p
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] StraightUpT:
I don't think so. I flashed it and nothing happened. I can't stand the Slim Bean lock screen handle.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] CrackerTeg:
True but no issues on build 8. This is a beta after all.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] roadcarver1971:
I am using Handscent and it works with this stable build of Slim ROM.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] matrixzone:
No love this week?

Any user noticing the smsdispatcher wakelock on the latest build?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] roadcarver1971:
Anyone noticing that the LTE signal bar is very low (1 bar) but the performance is it still good anybody noticed this?

By the way I'm on the Rogers LTE network.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] datoneazn:
I think Textra is the best messaging app imo

No bloatware AT ALL, interface and everything looks like it should be the stock messaging app.

It's amazing, everything you need and all you need.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] brttwilliams:
I've noticed this, but like you've mentioned it's still working well... I was tempted to try a different modem, but since there's been no noticeable decrease in performance I left it be....

Also, just noticing there's not been an announcement for a 1.1 beta... Are we staying on stable build 1 for this week?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] roadcarver1971:
Thanks for confirming.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jproy12:
If I'm not mistaking, the lead developer is on vacation, so we might not see an update this week...
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] brttwilliams:
Right on... Can't hate on him for needing some R&R... All the people involved with Slim work hard
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Brooklynsour:
Official 1 was like just released take it e.z were done with beta, op hasn't been updated since update....

Dab
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] JoshReuben:
This week's beta is posted. Here's the direct link though gapps isn't yet up.

EDIT to remove link as build pulled back
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] matrixzone:
Yes build without gapps is unusable
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Subsonic44:
Just flashed with last week's gapps. Working fine here.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] CrackerTeg:
Any differences between build 1? The changelog is Greek to me.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] bjtheone:
Not sure if 4.3 tweaked the signal strength meter, but the number of bars is pretty irrelevant. It certainly varies, modem file to modem file, and I find that the latest gives better performance (MF1 for Rogers however it breaks caller id for me).

Best way to check signal strength is Settings -> About phone -> Status and look at the actual signal strength in dBm.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] basily:
Is there no Fast Charge available on this ROM? I have the toggle in my Quick Settings panel, but it doesn't turn on when I touch it. Do I need to enable this somewhere or is it simply not available yet?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] LuigiBull23:
Flash a kernel in which supports fast charge and then it will turn on.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] matrixzone:
They have pulled back this week build because of critical bug.... Don't flash if you have downloaded the build..
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] basily:
Thanks but I hate to stray from stock. It used to (back in 4.2.2) work with stock kernel - I'll just wait till it's included again.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Swiftks:
Lean Kernel or bust! :D
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Brooklynsour:
The phone already charges faster than it did on 4.2.2.

I don't see any new breakthroughs for a reason to flash a beta about 1 week after official was released...just ridiculous

Dab
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Nic2112:
I lost root after flashing this row (first row install after rooting via odin) and I don't know what I missed. I tried the root from recovery file but it didn't work.

I know I had root before, I used root checker to be sure.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] brttwilliams:
I see that posted, but I think I DL'd and flashed before that was put out... I haven't had any problems with it...

---------- Post added at 03:55 PM ---------- Previous post was at 03:51 PM ----------

This may have been why they pulled it back... They reposted a new build... 1.2 is that the one you have?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Nic2112:
I have version 1 official, I'll try the new 1.2 weekly

---------- Post added at 01:08 PM ---------- Previous post was at 01:01 PM ----------

Flashed 1.2 and I still don't have root
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] galakanokis:
Did you activate in the developer settings? You have to turn it on if you are coming from a full wipe.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Nic2112:
I didn't do that, in fact I'm having a hard time finding the developer options in this rom
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Sajoeee:
I can't find the build 1.2 weekly gapps? Guess we use the regular official/stable ones from last week.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] bigfoot.kom:
JJ
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] gutlessmerc:
The developer options are not under Settings like it used to. Its actually under another app in the app drawer called: dev tools. There you'll find developer options.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] LuigiBull23:
That is true but you need to tap on build number under settings > About Phone to enable Developer Options. That's the way it's been since 4.2.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] gutlessmerc:
Weird! Somehow my developer actions still worked without having to enable it.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] dubjdub:
I have been reading and I keep see ppl using TWRP. Can I use CWM? Will it not flash correctly with CWM?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] m1batt1:
I use CWM without problem.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] dubjdub:
Thanks!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Chr0nicDreamz:
Only issue I have come up with for the latest build is that after around 24 hours of my device being up. I see a mass amount of RAM being used but no apps running or suspended. A reboot usually fixes the issue. Just curious to see if anyone else is having this issue.

Sent from my SAMSUNG-SGH-I747 using Xparent Skyblue Tapatalk 2
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] matrixzone:
Betterbatterystats seems to be having problem with latest weekly build. BBS after couple of restarts show inconsistent data on the up time of the device i.e. my device was up and running for the past 1 hour, but BBS shows 10 seconds.:silly:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] dubjdub:
So I love the ROM top to bottom. Two small issues. Photosphere isn't working and Google now is not working either. Any ideas?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] CrackerTeg:
I know nothing of photosphere as my phone isn't a nexus but as for Google now, clear data for search and you should be good.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Prufta:
I'm experiencing an issue when for some reason I have to reboot the phone, the mobile signal comes up but mobile data last few minutes (more than 5 minutes) to show. I have Bell modem + Slim Rom Official Build 4.3 + Ktweaker 08/31. When using the nightly version this doesn't happen.

Any idea to fix this issue.:confused:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Judman:
Photosphere has never worked in slimrom on the S3 and search -- Google Now Fix
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] dubjdub:
Thanks Teg it works!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Differentiation:
Hey, I flashed this rom perfectly fine except that when I restart the phone, the phone is stuck at the boot screen. I've followed up the instructions in the first few posts and the FAQ, did clean wipe, used TWRP 2.5, no luck.

Any other suggestions? Thanks!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] JoshReuben:
+1! Photoshpere on my slim S3!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] njpnc:
Lot of people had this issue with 4.3 ROM. It is not related to SlimBean. Read some earlier posts in this thread.

ODIN rooted stock ROM then flash 4.3 ROM
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] sdlopez83:
Are you saying that photo sphere now works? Or are you just requesting it?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] JoshReuben:
Not sure if it's Photosphere, but after following the linked procedure and deleting the APK, I was able to flash the Photosphere zip on my S3 and, upon rebooting, I now have a new panoramic photo option in the menu of my stock photo app, and I was able to create a panoramic photo with it. I see now that it's different from photosphere in that it doesn't provide the top and bottom grid, but it does allow me to click once and slowly more the camera from left to right to create a single panoramic photo. No new request - just happy that it works.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Raul77:
Hi Guys,

a strange problem i am having recently, the phone screen stays on! for example if i am sending a text or browsing, leave the phone on the table, it does NOT turn OFF the screen after 1 min. anyone experienced this?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] shaker2k:
Update your recovery. Twrp 2.5 had problems.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] stuff:
My sound often stops working. I only notice it when I see my notification light blinking and I realize I didn't hear anything. I test the volume rocker, and there's no audible "beep" when changing the volume. Also going into settings and playing the ringtone or notifications do not work. But if I play audio from my music player (For example, Google Play Music) the audio works. Then I go into the settings and mess with the ringtone, and I can hear it and everything appears normal again.

Would I need a logcat or anything to better figure out what's going on?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] 12packabs:
And if that doesn't work, use slim center to delete quicksearchbox, reboot, then flash gapps again or reinstall Google search from the store.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Differentiation:
But the FAQ says use 2.5. Should I still use 2.6? Thanks.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] 12packabs:
Some people had issues and some didn't. I never had problems. Using the latest 2.6.3.0. If you have issues, I'd use the version blk_jack specified first before reporting problems.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] datoneazn:
I also have that problem, I have to reboot my phone for the sound to come back.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Brooklynsour:
Wow so many of you do not read op or even few pages back with all the same bs.....

Dab
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] arcticrobot:
Just switched to this rom from CM and really loving combination of Slim and Lean. Just for some reason Hangouts dont sync. I send fine but dont receive replies and notifications. Is this a documented behaviour of supplied Gapps or just me? Removed them with slim center and reinstalled with play store. Didnt have chance yet to test.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] J M L:
I have the same problem, I think. For me it occasionally happens when I disconnect from a Bluetooth headset. I'm in the habit now of testing notification sounds after using Bluetooth, and if they don't work, I reboot.

It's intermittent, and the times I've setup to capture a log, I've not had the error.

This happens on all the 4.3 weeklies, and the 1.0 and 1.2 releases.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] stuff:
I don't use Bluetooth though. The only thing I have done is listened through my headphones via headphone jack.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] J M L:
And I don't use headphones, just the bluetooth...
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] dcoulombe:
I have the same with Slacker Radio since I flash the first 4.3 beta. When I start Slacker and resume the playback, audio starts to work again.

I attached a logcat to one of my post a while back :

http://xdaforums.com/show...&postcount=227

Great ROM with very few problems (for me at least).

Thanks
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] shaker2k:
And I use both! :p:sly:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] shaker2k:
Is anyone having trouble with gps? I'm not getting any satellites and before I Odin to stock I wanted to see if anyone else has this problem.

Thanks!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] m1batt1:
Compiling Slim

I tried my hand at compiling Slim today. It seems to have compiled correctly though I haven't had a chance to flash it yet. My question is during the build I noticed this and several similar errors/warnings that were like this or similar. Is this normal or is there something I need to do to correct it?

Note: Some input files use or override a deprecated API.
Note: Recompile with -Xlint:deprecation for details.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SyNRGz:
Do a google search on GPS FIX for Galaxy S3. Someone recommended tightening the 10 small screws under the back cover. I had immediate improvement. This is just one easy effective step to elminate. NOT TOO TIGHT!

I meant to add... my GPS was working but not reliably as it is now after tightening the screws.