yashsingh1/xdaforums huggingface dataset:
[T-Mobile, Samsung Galaxy SIII] lextex:
Two big issues so far...

1 -- I can't find the developer options to turn on root.

2 -- I'm getting constant 'package file invalid' errors from the Play store.
[T-Mobile, Samsung Galaxy SIII] blk_jack:
Like all 4.2+ ROMs you need to enable developer options. Those play store errors are common across android.

Use Google for both, they're not strictly ROM related.
[T-Mobile, Samsung Galaxy SIII] lextex:
I hadn't run into the developer options bit with any other 4.3 rom I've used so far. Good to know.

The play store, though, seems to be related to this rom. Can't seem to get it to work with any of the fixes listed in the FAQ, either.

Also, after my latest reboot I no longer have network access. "Emergency calls only" ...

**EDIT**

...And, now my IMEI is gone. Brick.
[T-Mobile, Samsung Galaxy SIII] MV10:
No AV software, I generally keep app downloading to a minimum. I'm more about working than playing games etc.

I'll go look for the MMS APK, thanks for the tip.

This mms.apk from LuigiBull23 did the trick. The two third-party SMS/MMS apps I have still don't work but I can live with stock-style messaging for now. Thanks again.
[T-Mobile, Samsung Galaxy SIII] jdatb:
Hi, I have this ROM, and it's working beautifully so far. Thumbs Up to the Dev.

One Question: How do I use HDR Mode with the Camera?
[T-Mobile, Samsung Galaxy SIII] Perseus:
I do not believe the Camera that comes with this rom actually has HDR Mode. I always thought that's a Touchwiz feature. I'd love to be proven wrong.
[T-Mobile, Samsung Galaxy SIII] abc123pro:
I'm still on the JLC modem. Anyone recommends updating to the latest? I seem to have random drops but I'm not sure if that's due to the modem or my vpn that stays connected both on data and wifi
[T-Mobile, Samsung Galaxy SIII] Perseus:
Your signature indicates you are using AT&T Version of Galaxy SIII. This is a T-Mobile forum. I don't think flashing a T-Mo modem to an AT&T phone is a good idea. Here's the AT&T Forum.

Still, to answer your question, there's no particular reason to upgrade unless you experience low signal consistantly or have call drop. Do please note, with the latest MD5 modem, a lot of people have reported that the phone gets warm, particularly during and after long calls. Lastly, on Doc Holliday's thread, you will see a map link in Post 2. This map will help you identify what modem may perform better in your area. Do note, that thread has SGH-T999 modems as well as Canadian Sgh-T999V modems. So read and pick carefully. By the way your question actually belongs there.
[T-Mobile, Samsung Galaxy SIII] abc123pro:
Lol thanks, but that's just the tapatalk signature doing its thing because as you know slim bean has an AT&T build. I know enough to understand that my phone is T-Mobile though, a t999.

I guess I just wanted an input on those who are on 4.3 and the latest radio. I've looked at the signal before and that's why I flashed the JLC radio to begin with, just been having recent signal drops and wanted to narrow down the reason
[T-Mobile, Samsung Galaxy SIII] Perseus:
Oops Sorry, fergot TapaTalk doing its thing. I had MD5 until recently. But I just now switched back to LJC modem to see if that brings down the RILJ partial Wakelock. It did.

You may want to explore the map to see in general what modem has better results in your area. That modem will less likely to have RILJ issues.
[T-Mobile, Samsung Galaxy SIII] Danvdh:
New weekly is out :)

quite a big changelog http://www.slimroms.net/index.php/d...lim-d2att-4-3-build-1-6-weekly-1214-changelog
[T-Mobile, Samsung Galaxy SIII] Volc7:
woop woooop. new weekly, any chance of a new luigibull23 tmobile update?
[T-Mobile, Samsung Galaxy SIII] Perseus:
Thanks for posting. As I see there's a bunch of camera code fixes. So hopefully I can get the Google Edition Camera to work. Right now it freezes after taking a shot. Kernel code has improved on CPU Control. Gotta pass this to my favourite

Well well well, I see some Q Employee names in there. We are truly blessed indeed!.
[T-Mobile, Samsung Galaxy SIII] LuigiBull23:
Here you go bud.

Weekly 1.6 d2tmo Build Prop

https://copy.com/ptpzW
[T-Mobile, Samsung Galaxy SIII] Volc7:
Thanks a lot, so far every build prop has worked perfectly.
[T-Mobile, Samsung Galaxy SIII] Markdental:
Any fixes yet for BT issues? It's a must that BT connect and remain connected consistently.

I am waiting on that for this to become my Daily driver...
[T-Mobile, Samsung Galaxy SIII] Perseus:
I will test this evening and let you know later. Do kindly note, the bluetooth issue has been plaguing all roms sharing CM Codebase. Some are more affected than others.This one seems one of the less affected ones.

EDIT - False Hope I guess. I tried and my bluetooth still has that NFC Wakelock. Even if I turn off Bluetooth, it turns on again. Not necessarily a stuck connection as before. But me I'd like it to respect what I want to do.
[T-Mobile, Samsung Galaxy SIII] Volc7:
I dirty flashed 1.6 over my 1.4 dirty flash which had the BT bug. I just tried my bt with my car twice. Worked perfectly, i can tur off bluetooth afterwards no problem. i dont know if it was just a fluke. Will report if i get the bug. Everything is working as it shuold for now
[T-Mobile, Samsung Galaxy SIII] galahadUSA:
Can't believe I'm gonna ask this but here goes...where did the option go to stop wallpaper scrolling?

Doh!!!........dumb ass, it's in my launcher settings.
[T-Mobile, Samsung Galaxy SIII] mike.r.olson:
Follow up on the SpeedTest.net app. I contacted Ookla on Twitter and they hinted that the problem might be caused by running a custom DPI. Dunno if they're gonna fix it or not. Just wanted to pass that along.
[T-Mobile, Samsung Galaxy SIII] Perseus:
Thanks for letting us know. I will see if I can run the new version on the Stock Galaxy S3.
[T-Mobile, Samsung Galaxy SIII] MV10:
I think this is the first report of issues keeping a BT connection up, isn't it? FWIW, I'm on the official build (not a weekly/beta) but I haven't noticed any issues staying connected, and at times I've driven long distances (hours) uninterrupted. It doesn't even lose the BT connection when my data signal gets bad in the middle of nowhere. (My issues are making/breaking the connection, which takes forever, and the well-known problem turning off BT.)

The delays answering calls are making me consider stepping back to 4.2, but based on the enormous changelogs it "feels" like a new stable 4.3 is probably around the corner so I'm trying to wait it out...
[T-Mobile, Samsung Galaxy SIII] Perseus:
Here's another funny thing I noticed on Bluetooth. This morning I connected to the Car and had an audiobook going for about half an hour. When I exited, I turned off Bluetooth after turning the car off. It obeyed me immediately. So maybe the other device should be turned off before turning the phone BT off ? I will test more.

Also now makes me Suspect if Torque too makes the Partial wakelock go ape. I will test that as well.
[T-Mobile, Samsung Galaxy SIII] MV10:
I've often shut down BT when it hasn't been connected to anything for a long time (for example, in the airport the other day I noticed my battery was almost dead and so I shut down everything I could to save juice) and still had the problem where it wouldn't turn on again later.
[T-Mobile, Samsung Galaxy SIII] Perseus:
So it turned itself on even under that case ? I'd suspect that partial wakelock. I tired the IRC Channel from OP and their Reporting Bugs page on the website. Neither worked.
[T-Mobile, Samsung Galaxy SIII] MV10:
No, it's off, and when I try to turn it back on, it sort of hangs and never turns on (if I use a widget, the widget stays in the turning-on mode (many use a red/yellow/green indicator, and they get stuck at yellow). As I understand it, this was the big BT on/off problem from AOSP in 4.2.x.

I have to reboot before it works again. (If it's off when I reboot, it turns on just fine the first time.)
[T-Mobile, Samsung Galaxy SIII] Perseus:
You understand correct. Yes you need to reboot to fix it. I traced part of the reason for this to that wakelock.NFC APK Code hasn't changed much since 4.2 or 4.3
[T-Mobile, Samsung Galaxy SIII] MV10:
I leave NFC off, I guess it must set a wakelock regardless?
[T-Mobile, Samsung Galaxy SIII] Perseus:
NFC APK controls Bluetooth. Yes the partial wakelock is related.
[T-Mobile, Samsung Galaxy SIII] ayeitschris:
I tried your build prop and I cannot change the DPI back to stock. When I change back to 240, its too small. But when I change it to 320, its close to stock but slightly larger.

Edit: lol nvm, 320 is stock not 240
[T-Mobile, Samsung Galaxy SIII] LuigiBull23:
Lol I was about to say.. Glad you figured it out though.

I left dpi alone to allow the end user to adjust it to their personal liking within the interface settings. This is why upon flashing this your dpi is reverted back to default 240.
[T-Mobile, Samsung Galaxy SIII] IXChicharitoXI:
I've never tried slim before. Just to be sure, I would do a full wipe, flash ROM, flash gapps, then flash this file?
[T-Mobile, Samsung Galaxy SIII] LuigiBull23:
Correct. It's as simple as that.

EDIT: Oh and welcome aboard!
[T-Mobile, Samsung Galaxy SIII] Volc7:
been using 1.6 for a few days now. feels rock solid and very fast. somehow my bluetooth got fixed lol.

i think the only thing missing for this rom is mass storage mode. other than that i love how slim it is
[T-Mobile, Samsung Galaxy SIII] Perseus:
Care to elaborate ? I can access as mass storage in car usb or on pc. its just that previous MTP & PTP are gone
[T-Mobile, Samsung Galaxy SIII] Volc7:
hmm so you dont have those choices?, well i can either choose MTP or PTP, no option for UMS
[T-Mobile, Samsung Galaxy SIII] ayeitschris:
Anyone have the themeable aosp messaging app that works with this ROM?
[T-Mobile, Samsung Galaxy SIII] Vyrus69:
Got an interesting issue, I installed the build 1 version and when I get an incoming call, the caller ID shows a bunch of random characters instead of a name. Any ideas?
[T-Mobile, Samsung Galaxy SIII] Perseus:
Search for Luigi's MMS apk few pages back or get AIO Gapps addons from slim Website.

Did you dirty flash? If yes do a clean one. If you didn't' then wipe data and cache for phone app.
[T-Mobile, Samsung Galaxy SIII] Danvdh:
Weekly builds are rolling out now. Looks like this is the last weekly until we get a stable. This weeks build is also 4.3.1 and we can now customize where the close all apps button appears in the recents screen.
[T-Mobile, Samsung Galaxy SIII] LuigiBull23:
Weekly Build 1.8 AOSP 4.3.1

The final Weekly Build is up before the next Stable Build.

Weekly 1.8

http://www.slimroms.net/index.php/d...tmo/6075-slim-d2att-4-3-build-1-8-weekly-1260

Gapps are the same. No changes from Google so no new Gapps :)

http://slimroms.net/index.php/downloads/dlsearch/viewcategory/383-addons/downloads/dlsearch

d2tmo Build Prop

https://copy.com/4U7Kw76UouD6

Changelog:

http://slimroms.net/index.php/news/385-weekly-1-8-changelog

Update to aosp 4.3.1

major overhaul of Privacy Guard. See this link for further information about the changes

frameworks: adjustable clear all button location

frameworks: PIN unlock random shuffle mode to avoid ppl can see your unlock move - thanks helicopter88

Torch: complete overhaul of torch app - thanks CM

Settings: improve AppOps detail layout

When wifi/dalvik wants ASCII lowercasing, it needs to ask for it

add otela web APN

fix VIPNet Croatia APN

fix dalvik logcat spam

fix superuser wrong assigment of legacy folder

update busybox

KeyguardViewMediator: Play lock screen sound sooner

Correcting NULL pointer when callerApp is not set

fix up CDMA APNs

audioflinger: Fix pops in LPA while effects are applied

audioflinger: Fix delay in enabling effect for LPA

Enable Tunnel Playback for msm8974

Enable LPA/Tunnel audio for QCOM B-Family

frameworks/av: Fixed framecount in AudioRecord

audio policy: Avoid unintended update of a command's timestamp

slimatalk app for new forum was removed due that tapatalk is now for free

several device specific upstreams

mako kernel update to 3.4.65

Privacy Guard Changes

https://github.com/SlimRoms/frameworks_base/commit/97ccae06cd0ad1aa366c3a70e8e744277c409b06

Details

Short before the next stable release we are rolling out step by step new weekly SlimBean 1.8....as usual read changelog and install instructions carefully and have fun. Gapps are not updated due that google did not update any apps this week. Gmail still remains the same till google fixed it finally up.

Beside rom development we are always working to improve our environmente. Not far away and we will start openening our gerrit code review system which we are using over a year now to the public so that everyone can see what we are doing and that every developer who want to work with us can jump in and support us....develop with us....get part of the slim community.

That said community is one of the most important things without we never could exist. So we decided to open our own Forum....where you will find in future news, announcement, developing status, device threads and places for just talking about android. Let's grow the Slim eco system :)

You will find the new forum here....register and have fun

http://forum.slimroms.net/
[T-Mobile, Samsung Galaxy SIII] galahadUSA:
Think I'll stick with stock kernel
[T-Mobile, Samsung Galaxy SIII] LuigiBull23:
If it ain't broken, don't fix it. :)
[T-Mobile, Samsung Galaxy SIII] Volc7:
just flashed 1.8, everything as smooth as ever. good job
[T-Mobile, Samsung Galaxy SIII] galahadUSA:
It's going to be the most recently updated, so yeah. Unless of course KT it's still updating his.
[T-Mobile, Samsung Galaxy SIII] Markdental:
Can anyone do a little testing on the new build and see if BT issues have been resolved?
[T-Mobile, Samsung Galaxy SIII] Perseus:
I know for a fact KT will be updating for this device in few weeks time. Until then, sad as it may seem, I am going to stick with the stock. My experiments with 1.6 version's Kernel were satisfactory.

Me. I will be doing quiet some testing with varied platforms as you saw in my last few comments.
[T-Mobile, Samsung Galaxy SIII] Volc7:
hmmmm, so my phone just went black. it is still on i can unlock it and all. reboot and it boots normally but still black lcd.. can taht happen from the flash even though it was working? cause i repaired a crack it had yesterday with LOCA . so i cant tell if it was the fix from yesterday or the flash from today O.o

guess ill start by reloading my dandroid, is there a way i can do it without being able to look at the screen? adb? odin?
[T-Mobile, Samsung Galaxy SIII] MV10:
For what it's worth, MMS still fails nearly every time even after updating to that other APK recommended earlier.

I haven't yet sat down to try to figure out if it appears to be related to having WiFi on or not.
[T-Mobile, Samsung Galaxy SIII] Perseus:
Yes PC Odin Back to Stock.
[T-Mobile, Samsung Galaxy SIII] Volc7:
bah i did odin back to stock, it wasnt the rom but apparently my lcd got messed up form the day before. im doing some last tests to see if i can revive it if not i guess its replacement for me lol
[T-Mobile, Samsung Galaxy SIII] Perseus:
If you go in for replacement, cross all your fingers and watch carefully. You may get T999L instead of T999. If so you have a bonanza. Some "unlucky" folks got S4 instead of their S3 as the s3 was out of stock. According to the Insurance fine print, if your model is not available, next compatible/equivalant model should be used as replacement.
[T-Mobile, Samsung Galaxy SIII] freak69ize:
Im not getting any transparency on the statusbar.. just the lock screen. I have it set for both. Am i missing something?? thanks
[T-Mobile, Samsung Galaxy SIII] Volc7:
heh i wish it was warranty, sadly i bought it off ebay so the repair is on me. is the T999L compatible with this rom? i hope so, fingers crossed XD
[T-Mobile, Samsung Galaxy SIII] Perseus:
Yes it is. Just there might be Asserts in the rom's updater script that prohibit from flashing. If you ran into that error, you will have to comment them out or delete them before flashing. Post if you do.
[T-Mobile, Samsung Galaxy SIII] MV10:
It has never worked that way for me. I have several other BT audio devices (one in the garage, another in the bathroom, etc). BT doesn't turn off when they disconnect and I have never seen the "Tuning off Bluetooth" message. As long as I don't manually turn off BT, they are able to connect again later on.

Unless by "turn off" you mean disconnect (gray icon), rather than disabling it completely (no icon).

And then, of course, I still have all those newer problems I mentioned which are specific to 4.3 -- slower connection, and what appears to be a big change in the disconnect sequence when A2DP and SPP are both connected.
[T-Mobile, Samsung Galaxy SIII] SiNJiN76:
I have this problem, but it's that the Bluetooth will disconnect on its own. Sucks when it happens while working out! :( Anyway, since you say that it may be a problem with the BT and NFC sharing the same antenna...could just deleting anything associated with NFC solve it? Although you mention that it happens with NFC turned off.
[T-Mobile, Samsung Galaxy SIII] Perseus:
Yes to clear the terminology,

Disconnect = explicitly disconnecting that specific connection.

Turn Off = What you referred to as Disabling Bluetooth.

Since you don't have this specific problem, it does not apply in your case. The speed issue may be raised on the Slim Rom's forum for hopefully more attention.
[T-Mobile, Samsung Galaxy SIII] MV10:
He wrote that the NFC program (APK) controls BT, so you certainly don't want to delete that.
[T-Mobile, Samsung Galaxy SIII] Perseus:
Do not delete the NFC Programs. Please mention your custom kernel if any. I do assume you are on Op's latest weekly version 1.8 ?

A bit while back, particularly earlier 4.3 versions, there was another CM bug on bluetooth. Unrelated to this one but nonetheless. It could be that you might be affected by that. It is also possible the bluetooth headset you are using has a limited range ?

I'd ideally wipe clean and reflash your rom. Practically speaking, start with wiping all the existing pairings and then wipe data for bluetooth share and media storage. Do the same for the media player you are using. After that reboot to recovery and wipe dalvik + Cache. Once done, reboot and then re-pair your headphone in BT-interferance free area. Once done, first turn off the headphone, then reboot the phone. That's it.

Thanks. Yes that's good advice.
[T-Mobile, Samsung Galaxy SIII] SiNJiN76:
Doh! It controls BT, got it. Thanks.

Cool. Yes, I'm on the stock kernel that comes with the latest nightly. I'll give your method a try, although I just flashed 4.3 yesterday. I use a bluetooth dongle clipped to my shirt and have my phone in my pocket.
[T-Mobile, Samsung Galaxy SIII] Perseus:
That sucks but better bite the bullet now rather than do it after the Rom had settled in.
[T-Mobile, Samsung Galaxy SIII] Danvdh:
Perseus have you tried updating to a kernel with more upstream

Linux version 3.4.66 is a LTS release much like 3.4.62 that slim uses and it just came out 2 days ago, bluetooth could very well have improvements

try BMS kernel, the dev uses slim specifically and I'm running it fine with no hiccups
[T-Mobile, Samsung Galaxy SIII] Perseus:
I used to use KT747. But with Ktoonsez away, that one will get updated after he comes back. Anyway the point is, with both, the latest Stock Kernel as well as KT747, the problem kept repeating. Yes the A2DP protocol profiles are part of Kernel. But the code for the Bluetooth Share Service is part of the Rom.

I have not tried BMS kernel as I had seen some posts regarding instability on Undervolting. I will however try it now to see if it makes any difference.
[T-Mobile, Samsung Galaxy SIII] LuigiBull23:
Not that this will guarantee repair of bluetooth share issues because as you said, the code for such services are within the ROM itself but Ktoonsez has already made his illustrious return to the forums in case you do plan on updating.

http://ktoonsez.jonathanjsimon.com/sgs3/aosp/KT747-AOSP-JB-MR2-3.4-ATT-10-16-2013.zip
[T-Mobile, Samsung Galaxy SIII] SiNJiN76:
No hiccups with BT?
[T-Mobile, Samsung Galaxy SIII] Perseus:
He did ? Durn it how come the thread aien't updated ?

Double Darn. Just flashed BMS.

Ask me tomorrow.
[T-Mobile, Samsung Galaxy SIII] SiNJiN76:
Hope I don't jinx myself...but BT usually craps out on me at ~20 - 30 minutes into listening. Using the latest KT and so far so good. [over an hour] :good: :victory:

Thanks for sharing the link to the latest build LuigiBull23.
[T-Mobile, Samsung Galaxy SIII] Perseus:
Guess Same day delivery. No joy. If I follow my own advice and properly end the connection, all is well. But otherwise the bug's still there. I needed to kill BT Share to bring it back. Strangely I didn't see the PWL though.

Ok Off I go and try my luck like Sinjin.

Yes crossing my fingers for you as well. Sorry Luigi I have reached my Quota of 8 for Day of Thanks. I am not allowed to press until tomorrow.
[T-Mobile, Samsung Galaxy SIII] SiNJiN76:
So, KT fixed the one problem that's been annoying the hell out of me (BT cutting out)...but disabling BT is the same.

Perseus71, is there a widget that can be used to kill that process with one click?
[T-Mobile, Samsung Galaxy SIII] LuigiBull23:
It's cool bro. I hit it for you :D
[T-Mobile, Samsung Galaxy SIII] Perseus:
Since this is a process, it does not appear under Recents list. You could potentially the Tasker plugin that kills specific processes or get

More Details in this other bug.
[T-Mobile, Samsung Galaxy SIII] SiNJiN76:
Just tried Automateit workarond...Works good. (only tried it once, but it worked). Just don't see the need for the second RULE to turn BT back on. Cause after the first RULE. It stays off.
[T-Mobile, Samsung Galaxy SIII] Perseus:
Also in the linked bug, someone tweaked the code a bit of the rule. You may want to take a look.

The second rule is for someone who'd want to re-establish stuck connection. Glad it worked for you. I thought since you had the problem at workout, vehicle based solution of automate it won't help.
[T-Mobile, Samsung Galaxy SIII] MV10:
For what it's worth, last week I took a three-hour drive (each way) running Pandora over BT and had no problems the whole time.
[T-Mobile, Samsung Galaxy SIII] SiNJiN76:
With this bluetooth workaround...I can comfortably stay on 4.3. :highfive::cool::D [Shoot, shouldn't have said that...probably jinxed myself]
[T-Mobile, Samsung Galaxy SIII] Perseus:
LOL I am on 4.3 Despite this irritant. I do know 4.3 is not the cause of this. I flashed 4.2 last night just to spite and the Durned thing is there too.
[T-Mobile, Samsung Galaxy SIII] xxqbnxx:
How is battery with the latest build I was having bad life earlier builds
[T-Mobile, Samsung Galaxy SIII] Perseus:
I am averaging 2 days under moderate use. But then I have had some Partial Wakelocks that drained my battery. Otherwise I am sure I'd have met my previous record of 3 days.
[T-Mobile, Samsung Galaxy SIII] xxqbnxx:
OK that sounds good did you use greenify or anything extra
[T-Mobile, Samsung Galaxy SIII] Perseus:
No Greenify. I did however use

1. KT747 Kernel - 10-14-13 Version.

2. The Google Shared Framework Mod from Galaxy S4 forum - (works just as fine here)

Needless to say I turn off Location related everything off unless I am navigating.
[T-Mobile, Samsung Galaxy SIII] :
Can you provide a link for the Google shared framework mod? I couldn't find it when searching.
[T-Mobile, Samsung Galaxy SIII] :
I think this is the one: http://xdaforums.com/showthread.php?t=2357417
[T-Mobile, Samsung Galaxy SIII] Perseus:
Yup that's the one!!
[T-Mobile, Samsung Galaxy SIII] abc123pro:
Interesting! Sadly I do use hangouts and calendar frequently so I think they may be effected :(
[T-Mobile, Samsung Galaxy SIII] zeusakatkm:
I have the latest slim rom weekly and gasps, abs it won't let me say my phone to connect to 2g networks only. Any ideas?
[T-Mobile, Samsung Galaxy SIII] scott7175:
To the that can only get 2 g check your IMei and make sure you didn't lose it
[T-Mobile, Samsung Galaxy SIII] abc123pro:
For what? Lol I'm not even having any issues right now