yashsingh1/xdaforums huggingface dataset:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] bjtheone:
Did a bunch of GPS testing today enroute to quoting a job, and I cannot replicate your issue. With Nav running I can switch to another app, to the home launcher screen, let to auto time out, turn the screen off via the power button, and when I come back to the Nav screen I am current on position and everythig is up and running as expected. Thus I think you have something funky with your install/settings.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] waiters:
Can we dirty flash beta 3 over beta 2?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] 12packabs:
You can, but in case of issues try a clean flash before reporting issues. Don't forget the new gapps. I had to clear the camera cache, but other than that was fine.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] CrackerTeg:
I did. Been just fine. I didn't experience the camera issues previously reported but I'm happy that save to sd is now in the camera.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] stevenca:
Wondering if someone can help with a battery charging issue? I never experienced it before installing this rom and I am sure its an easy fix, I read a few foolish things online as well as downloaded the battery calibration app from play store....but my phone still only charges to 91% and stops charging....anyone else run into this? In the meantime , i will keep searching google thanks

EDIT :

I shut the phone off , unplugged charger and plugged it back in until it said it was charging...let it go until it came back as full....booted into the os and it said 100% and i ran the battery calibration ..... not sure why it was messed but f*#$in' with stuff can help sometimes!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] GreenMean:
Anyone having issues with play store?? It giving me the no connection error even though I've got full bars on wifi.

Clean flash beta 3
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] waiters:
You need to make sure to flash the beta3 gapps also
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] MercilessLTD:
I can also confirm this works. Thanks!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] dcoulombe:
Turning bluetooth off ?

I'm running on beta 3. This morning, I streamed music from Slacker Radio to my car using bluetooth.

Then I turned bluetooth off with AutomateIt Pro (NFC rule). A few minutes later, I saw that bluetooth was running, so I manually turned it off. Then it came back on...

I had to reboot the phone so my bluetooth stayed off.

Anybody else had that problem ?

Pretty solid build overall. Impressive. :good:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] GreenMean:
Yeah I did. All other gapps worked.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ARchamps:
My favorite ROM so far! Any plans on getting the photo-sphere working on other devices? Thanks again!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] bjtheone:
Having caller id issues with 4.3 beta 3. Did not happen with beta2. Running the latest gapps. Beta 3 was flashed over 2 with only cache clearing.

Callers listed in contacts work fine. Unknown callers have the name portion completely messed up, with odd non English characters in name. Number portion remains correct.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] nsmith4:
Have you tried clearing the data for play store? I've had a similar issue before and that solved it.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] GreenMean:
Yeah that's the first thing I did. I'm on a different ROM now but will try another clean flash. I think that will solve the issue.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] T_D_H:
did full wipe multiple times, using TWRP 2.5.0.0, install went fine, gapps AIO used, worked fine after a cache clear and reboot....but wifi was almost unusable to the point I couldnt download more than 1 app before it cut out, and I'm 6 feet from the router, along with some other issues, I'm going to have to go back to 4.2 for now, but from how long I used it, it was nice, I did notice faster charging times via USB as well which was nice.

Best of luck with this project, I will be back to try it out at a later date when it's not so buggy;)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] atrix4nag:
Try switching off bluetooth receiving device, before switching off bluetooth on your device.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jpcdeux:
Had same issue. Go into DPI settings and hit clear app data again and reboot. You have to do it once when you change DPI then do it again. Always worked for me
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] k29er:
I'm running on beta 3. This morning, I streamed music from Slacker Radio to my car using bluetooth.

Then I turned bluetooth off with AutomateIt Pro (NFC rule). A few minutes later, I saw that bluetooth was running, so I manually turned it off. Then it came back on...

I had to reboot the phone so my bluetooth stayed off.

Anybody else had that problem ?

Pretty solid build overall. Impressive. :good:

On beta3, I have a problem every time I use BT. Won't play the next track without a restart, won't pause without a soft reset, was the same with beta2. Also battery life is half of what it was in beta2 and charging is back yo normal speed.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] dbornack:
Is anyone seeing the LTE issues a lot of people (including myself) experienced with the 4.2.2 version, or CM 10.1?

I'm on 4.2.2 and having these issues and wonder if 4.3 will fix it.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] CrackerTeg:
I saw no LTE issues on build 8 nor on current beta.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] dbornack:
Hmmm. I just rooted my friend's phone and put him on Slim 4.2.2 Build 8. All sorts of LTE issues. Went through most fixes I could find (IMEI, APNs, etc).

Anyways, that's not for this thred to discuss. Just curious what others have seen with 4.3.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] dcoulombe:
In facts, I always turn off the car before turning off bluetooth on my phone.

At least, if I turn off bluetooth and it come back, I know that I need to reboot the phone...

---------- Post added at 08:05 PM ---------- Previous post was at 07:54 PM ----------

Another problem I have is that I sometimes loose audio... Notifications, ring tones and about any sound output.

Funny thing is that when I started slacker radio to test music output, everything came back to normal...

Oh and when that happens, every action that normally output sounds lags (like typing on the keyboard or navigating in menus).

Don't know if it is rom or app related...

EDIT: Maybe a logcat might help... I copy-pasted from the moment I received a call to when I turned off my screen. Somewhere in there, I start slacker radio. And sound came back at that moment.

http://pastebin.com/my9Kqi3u
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jpcdeux:
After moderate camera use, this starts. Have to reboot
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Brooklynsour:
Beta 2 still kicking ass no issues A++. hope the 2.6 twrp ify issues clear up not taking chances
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] waiters:
Guys the bluetooth problem affects every d2att phone with any and all 4.2.2 and 4.3 roms.. U turn it off and it sits the acting like it's turning off just to turn back on.....

It doesn't always happen... But usually does.

It's not rom specific
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SlothlyDX:
Actually I have had no bluetooth issues in PAC rom 4.3 soooo I dunno?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] smithisize:
Could anyone create a zip for the modem in this ROM? I flashed a different one, and now my battery won't last the day.

Thanks

Smith
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Testman08:
I don't believe ROMs have modems included....but I could be wrong. There is a modem thread on xda though.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] matrixzone:
This ROM does not have model bundled. You need to flash modem separately..
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] blk_jack:
PAC is definitely affected too (after all, it's just a giant kang). The bluetooth on/off issue is completely random and definitely upstream. It's still open on CM's tracker and has been for more than half a year with comments on it every milestone.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] android_4life:
Every device is different, Just because we all have S3's doesn't mean that they are all going to take the flashing of this Rom the same. I been repairing PC's for a long time and these phone are like mini PC's. You could put the same hardware in 20 different computers and they all won't act the same. That's why it would be impossible for everyone to not have an issue. These Dev. like blk_jack know this and they work very hard to try to accommodate as many phones as possible.

Currently I have no Bluetooth issues it connects and disconnects properly on two devices, but the next beta it might not who knows, its the luck of the draw for everyone.

Remember I was having the splash screen freezes until I Odin to stock and started from scratch now I reboot once or twice a day with no issues. People need to try different things and see what works on their phone. What works on one persons may not work on another.

By the way when I went to stock it really made me appreciate this rom even more, because touch wiz sucks and is so laggy.

Thank you for your hard work Blk_Jack
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] dlockhart:
On Beta 3, still have same problem as I had in Beat 2, seemingly random close/reboot of all apps. No errors etc.. just all processes and apps restart. Once it happens once, it seems persistent until a reboot.

I am on fully clean install.

If there is a way to grab you more information on this I would be happy to.

Other than this and the already known BT thing I have had no issues.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] bjtheone:
Update: Banging my head against the wall on a caller id issue. Getting corrupted name info, for unknown callers. Callers in contacts are displayed correctly. Given that no one else is reporting it, I suspect I am special.

Did a clean flash to beta 2 (did not see the problem) and then dirty flashed beta 3 over it. Currently doing a full wipe, and clean flash of beta 3. Would love any suggestions of anything else to do to try and resolve this.

Only other issue I have is that Chomp SMS will not send long messages. Suspect that is internal to Chomp since the stock SMS app and Handsent SMS work properly.

Update: With a clean install, no extra apps loaded, I still have the caller id name corruption... (argh!)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] waiters:
What are u using for caller ID? Normally your phone just displays the name unless it's in your contacts. I don't know any USA carriers at least that offer caller ID?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] bjtheone:
I am on Rogers in the frozen north. They offer full callerid. When working I get name and number for callers not in my contacts. It was working before .
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] nsmith4:
What modem are you using. This post in the Canadian thread says it maybe Modem related.

http://xdaforums.com/showpost.php?p=40631929&postcount=195

Though that is with cm10.1 it may be an issue with 10.2 as well
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] bjtheone:
Using I747MUMLL1 which is fairly current. I am very aware of the CallerID issues with cm10.1. I actually was running an older modem, without any caller id issues but switched to a new one to try and improve LTE perfromance.

That modem (LL1) worked fine with SlimBean for a long time, up through 4.2 build 8. I only started having issues with the switch to 4.3 builds, though I thought it worked with Beta 2. However when I clean flashed beta 2, to retest I still had the issue. I suspect it is something that the cm lads broke upstream in 10.2.

Update: Flashed old old original modem that came with my S3 (I747MVLLE8) and Caller ID works. Thus I would conclude the cm lads rebroke something in the move to 4.3.

If it is a real issue, versus someing I have mucked up in my phone, it likely is only an issue for Canadian users on Rogers and Fido. I think CallerId is slightly different on Bell and Telus. Rogers does have full Name/Number display when it is working correctly. Things get funky for calls from other countries and cell numbers, but even then I usally get where the caller is calling from, plus the number. The totally corrupt name, with non standard charcters is new to 4.3.

I seem to get the same corruption each time (for calls from the same number) which might mean it has something to do with character sets getting messed up.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Brooklynsour:
I think u need to change modem/apn I may be wrong tho
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] bjtheone:
Reverting the modem all the way back to LE8 solved the problem. However LL1 worked fine with many many version of SlimBean based on 4.1 and 4.2.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] blk_jack:
Never heard of this before. I would check some of the apps/mods you may have installed.

Obviously logs would also help, but I've kinda given up reminding people that without them I typically can't help and have mostly stopped responding to these types of "phantom issue" posts.

TLDR; works for me!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] dlockhart:
Not too sure how to do logs, but here it's an attempt

http://db.tt/bCm2HxL6
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] bjtheone:
Back on Beta 3 (don't think I have ever flashed so many versions and nandroids in one day before) ... other than my weird caller id issues both beta 2 & 3 have been rock solid. No FCs, app issues, or OS crashes. Of course given that this is just a beta I am looking forward to amazing things when the official version drops... :)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] dlockhart:
here is another one

https://dl.dropboxusercontent.com/u/12127949/S3appcrash.txt
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] waiters:
I'm officially jealous :)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ARchamps:
What is the icon theme in the screenshots?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] GreenMean:
Beta 3 is pretty solid after using it for a few days now. :thumbup:

Looking forward to the stable release!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] blk_jack:
It looks like SELinux is going bonkers and enforcing aggressive permission blocking. Did you / are you enabling it somehow?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] dlockhart:
Not going to lie, don't even know what that is...

I have no idea if this will do anything but I'm going to freeze secure settings app(tasker plug in, uses root) and see if this is causing the permission issue.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] waiters:
What is the default dpi for this ROM? I changed it but want to go back to the default now. Thanks!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] dcoulombe:
245

...at least, that's what I have and I haven't messed with it :)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] waiters:
240?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] MercilessLTD:
It's 245. You can see that by looking at the /system/build.prop, the line that says ro.sf.lcd_density = 245.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Jep56:
Been running beta 3 with Lean Kernel...no problems, smooth as silk. 11 hours off charger with 42% remaining. (4) pushed emails, 10 screen widgets.

Thanks Slim Bean:laugh::good:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ARchamps:
Hi there.

Love this ROM! One issue though. I have WiFi off but it looks like it is still draining the battery. It shows as in use in androidbattery stats and in better battery stats (app). See screenshots.

Any ideas?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] CrackerTeg:
Go into the Wi-Fi advanced settings and uncheck the always scan option.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] dlockhart:
do you think that there could be an incompatibility issue with SElinux and particular apps causing this? it seems i can make it happen almost every time if I am in candy crush or dolphin browser.

uninstalling secure settings didn't work.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] bvsbutthd101:
I'm on beta 2, can I just do a dirty flash to beta 3 and do I have to flash gapps again?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] android_4life:
Yes you can, they are both 4.3 so you will be fine, as always clean flash before reporting.

---------- Post added at 06:34 PM ---------- Previous post was at 06:31 PM ----------

You don't have to re-flash Gapps if your dirty flashing, only on a clean flash is Gapps necessary.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] 12packabs:
Check the date on the gapps you have installed as there was an update with beta 3. While technically you don't need to install gapps every time, in this case I think there was an update to the gapps so you have to.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] bvsbutthd101:
Thanks everyone, there is an update to the gapps so I'm just gonna flash them as well.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] 12packabs:
You could, but by doing that you lose the ability for Dark Slim. The team also sometimes tweaks or makes improvements to the packages.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] android_4life:
I never lose dark ui, but I see your point.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ARchamps:
Thanks!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] xmetalfan99:
I can't wait for an official release even though it seems the beta is pretty stable. Just have never been a beta guy. Thank you for all of your hard work.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] android_4life:
I agree this release is more stable than the 4.2.2

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

I know the dev. Only recommends TWRP 2.5, but 2.6.1.0 is out with big fixes and possible 4.3 compatibility issues. Has anyone tried it?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] sdlopez83:
Yeah. Been on it. Not one problem with beta2 or 3 twrp 6.1 works fine for me
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] android_4life:
Should i use Odin to install Twrp 6.1, I heard bad things about GooMgr
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Galaen:
I used the .img file from their website and terminal emulator since goo wasn't working for me.

AT&T Galaxy S3
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] android_4life:
I tried Too also and it did nothing. I will just use Odin with the .tar file from their site.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] sdlopez83:
Just used goomanager like always... Never a problem 1 year so far.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] matrixzone:
Beta4 could land today, changelog is updated on slim site. Enjoy!!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Sajoeee:
Can't wait. :good:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] matrixzone:
Most of the build for other devices are completed. Sprint S3 build is also up, expect the att version any time as build server are up and running..
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Sajoeee:
+1. I've been monitoring the site.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] CrackerTeg:
I'm feverishly hitting the f5 button.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mfc719:
I use the min. G-APPS. Just wondering if I can use face unlock from build 8? On beta 3 right now.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Sajoeee:
It's weird how were always mostly last to get the new updates. But the test of d2 got it.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] blk_jack:
SlimBean 4.3 beta 4

SlimBean 4.3 beta 4

Beta 4 is live! Please read the Changelog for more details including proper upgrade/installation methods, as well as notes on activating root and restoring with Titanium Backup.

Changes, Features & Fixes:

Changelog from beta 3 to beta 4

d2: Lower [fixed] camcorder audio volume

d2: Match MMS to jf-common

d2: Support Samsung extended AGPS

d2: Kernel updates

d2: Clean/update startup scripts

d2: Bluetooth fixes

Frameworks: Clean up trigger code

Frameworks: Fix lockscreen bottom trigger on expanded desktop

Frameworks: Completely revamp and fix transparency mode for navbar/statusbar

Frameworks: Rework navbar/status bar color handling

Frameworks: Simply custom lockscreen background code

Frameworks: Move complete KeyEvents into SlimActions

Frameworks: Bring navring/pie/navbar vibrate/sound inline with AOSP

Frameworks: Add accessibility events to navbar/pie/navring

Frameworks: Add expanded desktop to SlimActions

Frameworks: Add power menu to SlimActions

Frameworks: Add torch to SlimActions

Frameworks: Add DeviceSupportUtils helper class

Frameworks: Fix framework reboot on format of SD card

Frameworks: Hide new non-standard APIs and permissions

Frameworks: Add filter method for supported phone features

Frameworks: Center keyguard shortcuts when only 1 or 2 set

Frameworks/Native: Forward port surface dithering from CM10.1

Frameworks/AV: Audio flinger/LPAPlayer fixes

Frameworks/AV: Featurize QCOM's VOIP feature

Frameworks/AV: Camera fixes

Frameworks/Opt/Telephony: Fix MMS auto-retrieval

Frameworks/Opt/Telephony: Various fixes

Bluetooth: HID: Add support for set idle/get idle commands

Bluetooth: Add trust device feature

Bluedroid: USB: Abort writes if device is absent

Bionic: Merge in CM's bionic

Bionic: Add NEON optiomized memmove

Settings: Fix USB settings tile

Settings: Correct wallpaper custom image size toe new keyguard size

Settings: Add development animation transition mode 0.75

DashClock: Collapsed mode conditions

QCOM: display/audio/media updates and fixes

Major device branch bring-ups and fixes

Add T-Mobile IPV6 APN

Correct Tele2 APN

Add Eastlink Wireless APN

Gapps: Fix Hangouts video call FC

Gapps: Google+ update

Dashclock collapsed mode conditions

​

Please note these builds are under heavy development!

4.3 mini-FAQ

Q) I'm stuck at the boot logo and/or a boot loop!

A) Make sure you use TWRP 2.5.0.0. TWRP 2.6 and other recoveries can cause boot loops & hangups

Q) Root doesn't work!

A) From a clean build you need to enable root access for Superuser itself. This is different from 4.2.2 in which Superuser by default had root access on a new install. To do this, go to Settings -> Developer options -> Root access. If an app attempts to request root access before Superuser itself has access, it may cause problems with that app in the future where root requests are silently denied.

Q) Titanium Backup isn't restoring apps!

A) Change the backups folder to storage/emulated/legacy.

Download SlimBean 4.3 beta 4

Download 4.3 beta 4 GAPPS
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] CrackerTeg:
That weird lock screen bug I posted a few pages back is still there.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Sajoeee:
A few pages? I haven't seen that you posted a lock screen bug?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] CrackerTeg:
Look for the screen shots I posted.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Sajoeee:
Found it, okay. I recommend just not rotating and turning off lock screen rotation. Or turning off rotation.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jpcdeux:
Anyone else have camera connection issues after moderate camera use? Just suddenly doesn't want to start again. Have to reboot.

Data seems slower as well over tw. Haven't run a test to prove