yashsingh1/xdaforums huggingface dataset:
[T-Mobile, Samsung Galaxy SIII] MV10:
That thread still says 4.2.x ... at some point somebody posted the Verizon link as the 4.3 stable (I didn't think to check at the time and only noticed it was Verizon yesterday).

This BT issue (losing audio completely) is new to 4.3, didn't happen under 4.2.x ... under 4.2.x I had the well-known AOSP problem turning BT off and then it would hang turning it on again. 4.3 has other new BT issues, too -- connects much, much more slowly; sometimes SPP (serial) won't connect even if A2DP does (my truck stereo uses both A2DP and SPP to control Pandora); and SPP seems much slower to disconnect (which has the odd behavior of my phone suddenly blaring Pandora for a few seconds after A2DP disconnects but before SPP disconnects, which is Pandora's trigger to pause).

Thinking of downgrading back to 4.2 build 8 for awhile. First time on Slim that I've ever downgraded. In fact -- can I just flash build 8 ROM & apps over 4.3? Does going backwards work as smoothly as going forward?

With all these BT issues, I've been wondering -- is the BT stack accessible to AOSP devs, or is it a locked-up black-box library sort of deal?
[T-Mobile, Samsung Galaxy SIII] EXV:
I reverted back to build 8 after having minor annoyances from 4.3. I did a full wipe (including internal) and system format and I am happy to say there are zero issues as of yet. I honestly don't see much of a difference between 4.2 and 4.3 so I'd rather go with the most stable which was 4.2.

From my SGH-T999 S3 running Slim Bean 4.3 AND BMS Kernel
[T-Mobile, Samsung Galaxy SIII] scifan:
I noticed with the 1st stable, that Pandora would launch and interface with my deck as expected.

What I've noticed a couple bluetooth related issues... whenever I change songs, there's a minor pop... (doesn't matter which music player I'm using... even does it on google's own on-line player)... sometimes there's a significant delay when I change songs (this is listening to music on my local sandisc 10x 64gb card...) at first I thought the player I was using had hung...

I've also noticed a weird speed anomaly... the BEST speed I could achieve on a speed test under 4.3 was ~ 8m down... with the older rom I'm getting ~ 15m down in the same location... (need to re-test the spot I've been able to hit 25mb at...)

I stepped back to a nandroid from a prior rom for now.
[T-Mobile, Samsung Galaxy SIII] MV10:
Does your head unit have specific Pandora support, or just generic Bluetooth Audio? Mine has both. When I set it up for generic BT Audio (A2DP) everything is a lot smoother.

Bluetooth Serial Port Profile (SPP) is used on top of A2DP to retrieve Pandora artist/album/track info, the album cover art, to implement the like/dislike feature, and to retrieve and select playlists.

Based on what I'm seeing, I'm guessing the SPP implementation has gone a bit sideways in 4.3, somehow.
[T-Mobile, Samsung Galaxy SIII] scifan:
My deck has well integrated support - I'm using a Kenwood kdc-x996... (Pandora no longer responds to/nor shows on screen controls...)
[T-Mobile, Samsung Galaxy SIII] MV10:
I'm running a Pioneer AVH-X2500BT. You're right, if your phone shows Pandora <> Accessory (or Pioneer, or whatever), you're connecting over both A2DP and SPP.

The 4.3 issue I mentioned about losing audio completely is very intermittent, as it turns out. Sometimes after I disconnect, all phone audio is dead. Other times it works normally. But when it goes away, it's always immediately after disconnecting from A2DP and SPP.
[T-Mobile, Samsung Galaxy SIII] Perseus:
Well for what its worth, this version has just migrated from Beta to full release. So its your call.

The Op isn't updated. But if you check the website, you will see the update. Here's the link.
[T-Mobile, Samsung Galaxy SIII] Volc7:
im using build 1 and i get the same audio disconnect thingy after using bluetooth audio with my car, also mail app doesnt show the little number of unread mails
[T-Mobile, Samsung Galaxy SIII] Perseus:
Ok I will test the Bluetooth in the morning and report back the results.

You do know that Due to known CM bug, it is best to turn off phone Bluetooth before turning off the car engine.
[T-Mobile, Samsung Galaxy SIII] MV10:
That wasn't the case with 4.2.x ... I'm in and out of my truck several times a day. As long as I didn't turn off BT at all, there was no problem. However, if I turned off BT (which I used to do before I realized BT is no longer a massive battery drain in 4.x), something like 75% of the time I couldn't turn BT on again successfully without rebooting first.

And in fact, that behavior is still present in 4.3, it just looks like we have more new BT behaviors that go sideways. But if you turn off BT, you're almost guaranteed to have to reboot to use it again.
[T-Mobile, Samsung Galaxy SIII] Perseus:
I did some extensive testing this morning. It turns out, there's a Partial wakelock called NfcService:mRoutingWakelock. It is created every time you successfully connect to another Bluetooth device. In this case your truck. Once you turn off the connection and turn off the Bluetooth Radio, the wakelock should have gone.

Unfortunately it does not. On the contrary it tries to re-establish the connection. In a sense that's good as you are automatically paired when you are close to your truck. However, it also does not let Bluetooth to be turned off. Hence you have to Reboot to kill that background process.

Speaking of Process, its actually the NFC App that continues to do this. In this thread, there's another NFC.APK posted. You could try that route. But it does sound like NFL Apk is not letting go of the Wakelock. By the way you are right things were better with 4.2

[MENTION=2637227]blk_jack[/MENTION] - I can go back through the commits of Slim 4.3 to see CM Codebase of NFC. Let me know if you want me to pinpont the location of code.
[T-Mobile, Samsung Galaxy SIII] Volc7:
thanks for checking that, so if i install that nfc.apk posted the troubles might go away? hopefully with this dicovery they can patch it up

one more thing, there is a red little light next to the camera hole on the front, if i reboot its off until used i guess, but it has been on for the entire night, this is the third time it happened, dont know why (im not talking about the LED that lets you know its charging, its a very faint red light im assuming the proximity sensor)
[T-Mobile, Samsung Galaxy SIII] Perseus:
Remember the thread I posted is SGS II. So take a nandroid before you replace the APKs. Proceed with caution.

Yes that's Proximity Sensor and Light sensor.Dunno why they'd light up. could be difficult to say. If it continues wipe data for Gallery.
[T-Mobile, Samsung Galaxy SIII] momulah:
Beta 5 has bug with Bluetooth where when in settings you can't turn it off. When you slide it to off it tries but stays on.
[T-Mobile, Samsung Galaxy SIII] MV10:
Interesting. I have no use for NFC and had it turned off in 4.2 but forgot to disable it after moving to 4.3... maybe disabling it will improve things.

Sure wish I had the spare time to contribute to the dev effort on this.
[T-Mobile, Samsung Galaxy SIII] Perseus:
Are you saying this bug was reported already against Beta 5 Codebase ?
[T-Mobile, Samsung Galaxy SIII] momulah:
No just something I noticed today. It doesnt happen every time but I managed to get it to happen a few times pairing with my sony stero unit.
[T-Mobile, Samsung Galaxy SIII] Perseus:
I hope [MENTION=2637227]blk_jack[/MENTION] is listening.:silly:
[T-Mobile, Samsung Galaxy SIII] EXV:
Thank you, but I was on the stable version and decided to go back. Once the 4.3 has gone through a few stable releases, I'll give it another go. Slim Bean 8 has been too reliable to move away from.

From my SGH-T999 S3 running Slim Bean
[T-Mobile, Samsung Galaxy SIII] MV10:
Has anyone noticed the phone being slower to answer in 4.3 vs 4.2?

I usually have to say Hello (or my name or whatever) two or sometimes three times before it connects through to the caller and they hear me. Previously it would connect just as soon as I hit the button to answer.

I use Dialer One which is normally pretty good, but I should probably go back to the stock Phone app just to be sure (although if I understand it correctly, I don't think the dialer would interfere with that).

Just wondering if anyone else has experienced this.
[T-Mobile, Samsung Galaxy SIII] Perseus:
Not really, With the Stock dialer, I didn't particularly see any different. But then I was not paying attention either. I will watch out next time and see.

Is DialerOne updated for 4.3 ?
[T-Mobile, Samsung Galaxy SIII] MV10:
DialerOne hasn't changed in awhile.

I switched back to the stock phone app and it does also answer very slowly sometimes, but not other times. Seems to be about a 50/50 chance. I want to say DialerOne was slow every time but I should probably watch it more carefully before I make that assertion.

With the stock app, when I slide the icon to answer, the icon just locks up at the right side, sometimes for four or five seconds, before I connect. Other times it's instantaneous, as it used to be.

I try to avoid any background stuff (no Facebook notifications active, no email polling, etc) -- my battery tends to last a good 20 or 25 hours depending on call volume, if I let it run that long without charging -- so I don't think it's likely to be another app at fault.
[T-Mobile, Samsung Galaxy SIII] Perseus:
Do you have any tweaks of the CPU Frequency ?
[T-Mobile, Samsung Galaxy SIII] MV10:
No, I run as bone-stock as I can get.
[T-Mobile, Samsung Galaxy SIII] Perseus:
By bone stock I assume you kept stock kernel. Did you dirty flash the rom by chance ?

Also I assume you have no apps running when the delay in stock phone app occurs ?
[T-Mobile, Samsung Galaxy SIII] MV10:
Stock kernel and stock settings as far as "tweak" type stuff goes, including DPI and so on. Just don't have the time to mess with things the way I used to. When I flash a new SB, I always wipe the cache partition and dalvik cache but not a full reset.

Usually nothing else running. Sometimes Kindle might be up in the background, but it has happened plenty of times right off a fresh reboot (which I'm doing right now from time to time because of the Bluetooth issue).
[T-Mobile, Samsung Galaxy SIII] Perseus:
Get Auto Memory Manager and set it on medium setting. If that does not help, put it on aggressive.
[T-Mobile, Samsung Galaxy SIII] MV10:
What do you expect that to do? I haven't had to run anything like that since the days of my G1.

Nothing else "lags" -- it's strictly answering an incoming call.
[T-Mobile, Samsung Galaxy SIII] Volc7:
well there is something definitely wrong with Bluetooth, today i was unable to turn it off unless i rebooted
[T-Mobile, Samsung Galaxy SIII] Perseus:
Auto Memory Manager tightens up Android LMK. Since we have ruled out there is no CPU tampering of any kind going on, Memory is the only other viable choice left to try.

Today, I had bluetooth connected with the car but forget to turn it off after getting out. When I turned off after 30 minutes, it turned off just fine.
[T-Mobile, Samsung Galaxy SIII] tlopez1973:
hey guys is the d2att for the t-mobile s3 also because i can't find the one for d2tmo one on slimbean website
[T-Mobile, Samsung Galaxy SIII] :
Yes. I'm running that ROM with no issues. Just change the build prop to say d2tmo instead of d2att or you won't get data signal.
[T-Mobile, Samsung Galaxy SIII] LuigiBull23:
Yes it is but you're phone will be recognized as a d2att device. I assume you plan on flashing build 1.2? I have a flashable zip that will replace your current build prop with my modified one and identify the Phone as d2tmo if you would like that.
[T-Mobile, Samsung Galaxy SIII] Perseus:
Luigi Please request Blk_Jack to include that zip in the OP.
[T-Mobile, Samsung Galaxy SIII] scott7175:
1.4 needs to hurry I don't wanna set up 1.2 and have 1.4 in a couple hours
[T-Mobile, Samsung Galaxy SIII] RedJack117:
Would appreciate that
[T-Mobile, Samsung Galaxy SIII] :
Noob question: I noticed that there's a 1.4 release on the SlimROM website. Is that available for downloading or should we wait for the OP? Thanks.
[T-Mobile, Samsung Galaxy SIII] EXV:
OP hasn't been updated and doesn't reflect any of the stable builds. Go right ahead.

From my SGH-T999 S3 running Slim Bean
[T-Mobile, Samsung Galaxy SIII] Perseus:
With a stable build being released, I think this thread has served its purpose. So possibly not being updated anymore ? Who know. But then the Original thread should have been updated....:confused:

Ok anyway this 1.4 version has code fixes for International S3 and VZW version. The only thing worthwhile for this device is potentially the Snapdragon Optimizations, IPV6 Stable code, Updated Wireless driver and some code tightening. If anything I'd say the updated wireless location fix might save you some battery if any.

So those who have to have latest code can go for it. I on the other hand am going to pass this time.
[T-Mobile, Samsung Galaxy SIII] Volc7:
2 questions.

1) im on build 1. can i just flash 1.4 over it?

2) and luigibull23 is the tmobile zip u gave me the same for 1.4?

EDIT: quesiton 3, i dont seem able to plug a usb flash drive to my phone anymore, anyone have that problem?

tahnks a lot, hope this fixes bluetooth although nothing says so on changelog
[T-Mobile, Samsung Galaxy SIII] :
I downloaded 1.4, flashed gaaps, use the play store to get My Backup Pro (that's my backup tool) and restored all my apps. However, when I reboot, a number of apps (such as AFWall+ and Apex Launcher) disappeared - I had to restore them again. Anybody else experience this?
[T-Mobile, Samsung Galaxy SIII] Perseus:
Yes dirty flash should be ok. Do a nandroid before just to be safe. Luigi's zip will do fine.

I didn't see much hope for BT issues. Do post back if you see improvement.

EDIT - You edited on me. :( No never tried USB Plugin.
[T-Mobile, Samsung Galaxy SIII] LuigiBull23:
Updated build prop

https://copy.com/bitXD
[T-Mobile, Samsung Galaxy SIII] mike.r.olson:
Can anybody run a speed test using the updated SpeedTest.net app on any build newer than 1.1?
[T-Mobile, Samsung Galaxy SIII] Perseus:
I am not considering updating. Any particular problem ?
[T-Mobile, Samsung Galaxy SIII] momulah:
GPS navigation with maps is terrible on beta5.
[T-Mobile, Samsung Galaxy SIII] mike.r.olson:
When you press the "Begin Test" button, nothing happens. It's almost like it's not registering keypresses. I've cleared the app's data and cache, uninstalled and reinstalled and the problem persists. I'm on the latest 1.4 weekly on my T999 and my N7 (2013) and both suffer the issue, so I'm not really sure what the deal is.
[T-Mobile, Samsung Galaxy SIII] dynas7y:
So what exactly needs to be done with the ROM and updated build prop for tmo in order to be able to flash it? Thanks for any help!
[T-Mobile, Samsung Galaxy SIII] Babydollll:
That statement is so wrong.

I have a d2tmo but I've been running d2att ROMs and kernels for over a year. I've NEVER had data issues on slim (or any other d2att ROM)

The only thing he might have to do after a full wipe is select (or add) the correct apn for T-Mobile.

The build prop change is more of a preference thing. The only issue I can really see having a d2att build prop is:

If your carrier is T-Mobile but your build prop states you have an Att device, you can't say....buy apps in the play store and charge them to your T-Mobile account.
[T-Mobile, Samsung Galaxy SIII] :
That's strange, because while I had the right APN and could see the network icon in the status bar, it wouldn't allow me to access the network or even download apps from the Play Store until I changed my build.prop.
[T-Mobile, Samsung Galaxy SIII] Perseus:
Do oyu have the latest version of the Speed Test app ? It recently got updated for 4.3

You go to Recovery and then flash both from there. If you didn't know that, or don't know what a recovery is, you probably should not mess with it.

Depends on if you did Dirty Flash. The APN Settings sometimes mess up.
[T-Mobile, Samsung Galaxy SIII] mike.r.olson:
It didn't happen until they updated it with the new UI. The old one works.
[T-Mobile, Samsung Galaxy SIII] #1n00b:
I can verify I have the same issue. All other buttons work, but "begin test"
[T-Mobile, Samsung Galaxy SIII] Negativezeroxxxx:
When certain apps try to request su access (in my case cpu control light, rescan media root, and goomanager) the dialogue to select allow shows up for about 1/2 a second then disappears and immediately denies, even if I have the settings always set to allow su access. But other apps it will work fine for. Any ideas?
[T-Mobile, Samsung Galaxy SIII] Perseus:
I do believe, you should then raise it to the developer. I don't think they have a thread here.

I updated my rom just so I could reproduce this issue. You are right it does not work.

You will have to go into SU log under Settings. Remove everyone and then explicitly change under Developer options to allow Apps and ADB. If its already set then set it to something else and then set again.

Also turn off the alternate UI for SU option temporarily. Once done, reboot and try. If the problem persists, then uninstall the problem app and then re-install only after reboot.
[T-Mobile, Samsung Galaxy SIII] Volc7:
welp 1.4, dirty flashed. so far works as good as 1.0

however:

- bluetooth still broken, in fact it froze my phone after turning off my car.

- connects fine as a media device (sadly no mass storage option) but fails to read any usb stick with 3 different cables and 5 different usb sticks

-this happened even in stock: compass in 90 degrees wrong at all times. i think i read it might be because it is set for tablet and not phone (you hold the tablet horizontally (90 degrees more or less)

the third is really not important, but the first two bugs are bad, with those 2 fixed it would make this rom great
[T-Mobile, Samsung Galaxy SIII] nirogu325:
In the short time I had a clean install of weekly 1.4, I noticed the ROM sometimes has issues opening the camera (opening camera failure) and Torch (LED flashlight).

Sent from my SGH-T999
[T-Mobile, Samsung Galaxy SIII] Perseus:
I too tested yesterday and yes Bluetooth is still borked. Try another compass app and also go through the Sensor recalibration on a flat surface.

Doesn't sound clean flash. Please go to recovery and then wipe Dalvik +Cache. If that does not help then need to do really clean flash.
[T-Mobile, Samsung Galaxy SIII] Volc7:
i have tried numerous compass apps, recalibrators and all types of spinning rotating fixes XD, none of them worked.

camera works perfect for me
[T-Mobile, Samsung Galaxy SIII] nirogu325:
Lol, nice one.
[T-Mobile, Samsung Galaxy SIII] RedJack117:
Does Viper audio worm for anyone on 1.4? cant seem to get the drivers to install
[T-Mobile, Samsung Galaxy SIII] nirogu325:
It did work for me in weekly 1.4 as long as I downloaded SuperSU from the market and used it. Try that. It sounds better than the previous V4A, but it's clear that one seems to have issues with root.
[T-Mobile, Samsung Galaxy SIII] RedJack117:
Even when I try to install the drivers it fails... Not sure why. Also when I go to download su pro it says it's already installed
[T-Mobile, Samsung Galaxy SIII] nirogu325:
I don't know. It works for some...it didn't work for me in TouchWiz, but it did on weekly 1.4. Their dev says to wait for next release (bugfixes).
[T-Mobile, Samsung Galaxy SIII] Perseus:
Installing SuperSU and making it work requires SuperSU overriding the CM Root Manager. Follow the op instruction to grant SU rights to SuperSU app first and then install some Rooted App to test if SuperSU is able to do its job.
[T-Mobile, Samsung Galaxy SIII] nirogu325:
Obvious. It has been repeatedly reported the integrated root sometimes causes issues. This is a weekly we're talking about. Hence my suggestion to RedJack117.
[T-Mobile, Samsung Galaxy SIII] derride8:
My problem please help. For example, the stuff I downloaded on internal sdcard while on 4.1.2 rom, does not show on 4.3 rom. But when I go into recovery only rhen it shows up.
[T-Mobile, Samsung Galaxy SIII] Aerowinder:
Move it from /data/media into the /data/media/0 folder.
[T-Mobile, Samsung Galaxy SIII] derride8:
If I transfer the files over to the new location, how do I get it to shiw up in recovery?
[T-Mobile, Samsung Galaxy SIII] Perseus:
In Recovery, it will show up under /sdcard. If not then /mnt/sdcard. If all else fails, manually traverse to the new location.
[T-Mobile, Samsung Galaxy SIII] MV10:
Ran with this for about a week. No real difference seen no matter which group of settings I use -- still a roughly five second delay answering incoming calls most of the time, regardless of whether I use the AOSP dialer or Dialer One (although I still suspect the active dialer isn't related to the call answering process).

Also sending and receiving MMS doesn't seem to work at all for me when WiFi is on, and is highly unreliable with WiFi turned off. (I tried the steps suggested in the 4.2 thread -- delete Messaging data, reboot, MMS yourself with WiFi on -- and it had no effect.)
[T-Mobile, Samsung Galaxy SIII] Perseus:
Do you have any kind of Antivirus software ? Anything that would scan whatever you install or try to run ? One Example is Lookout, but there are plenty more. If you do, try freezing them.

As to MMS, on the 4.2 thread [MENTION=5082757]LuigiBull23[/MENTION] had posted an APK. You need to replace your MMS apk with that one.
[T-Mobile, Samsung Galaxy SIII] saytj1:
Does anyone have Google wallet running on slim bean beta 2 for the d2tmo GS3
[T-Mobile, Samsung Galaxy SIII] sp1zz:
So I noticed Bluetooth Streaming music is choppy and not clear. Anyone else having that issue?
[T-Mobile, Samsung Galaxy SIII] merk_maniak:
small?

Is everything supposed to be small? Like the whole layout. My icons only go 4x4 but there's a huge gap between the sides, bottom and the top. Is this normal?
[T-Mobile, Samsung Galaxy SIII] LuigiBull23:
Change your dpi
[T-Mobile, Samsung Galaxy SIII] blk_jack:
This guy gets 90% of my daily thanks.

SlimRoms MVP, sir.
[T-Mobile, Samsung Galaxy SIII] Markdental:
Anyone using this as your daily driver?? Issues?

So ready to try 4.3......

My main thing is camera, wifi, bluetooth, and battery life.
[T-Mobile, Samsung Galaxy SIII] abc123pro:
Anyone know how to change the camera's storage location to external? I don't see it in the 4.3 camera options
[T-Mobile, Samsung Galaxy SIII] garymachete:
Been using as a DD since release. SlimRoms are always the most stable. Give it a go.

Slim 4.3
[T-Mobile, Samsung Galaxy SIII] blk_jack:
Not available yet in 4.3
[T-Mobile, Samsung Galaxy SIII] sp1zz:
Been using it myself since yesterday and been using it constantly since. Only issue I've had is streaming via Bluetooth in my car, everything has been working great with heavy usage.
[T-Mobile, Samsung Galaxy SIII] RedJack117:
Still can't figure out this reboot problem... Re flashed a new recovery and everything but still get stuck at Samsung logo
[T-Mobile, Samsung Galaxy SIII] chrisokaly:
love the new builds. everything is running smoothly, except the known issues like focal. one thing that i have noticed is recording audio, whether in sound recorder or on camcorder is very low... and if i remember correctly was the same on 4.2....... Stock ROMs record at a much higher volume, almost an HD level. Is this a known issue? Is it a software or hardware thing??
[T-Mobile, Samsung Galaxy SIII] lextex:
First rom I've used in a looooong time that didn't reboot my phone when I tried to take a FFC pic. :)

Now... how do I get rid of the logo on the lock screen?

***Also -- Apex is force closing on me.
[T-Mobile, Samsung Galaxy SIII] blk_jack:
Switch to a working (better) recovery.

Flash the new beta 2 build on the website. Check the filenames, the new one doesn't have a -### in the weekly filename.

Read the FAQ. There's a flashable zip.
[T-Mobile, Samsung Galaxy SIII] lextex:
The lockscreen zip link in the FAQ is dead. I found it by searching the downloads tab, though.
[T-Mobile, Samsung Galaxy SIII] chrisokaly:
So audio recording is good? stereo recording?
[T-Mobile, Samsung Galaxy SIII] blk_jack:
That's what they tell me. The next build will have even more improvements to the recording, but the newest beta 2 build has improved audio volume.