yashsingh1/xdaforums huggingface dataset:
[T-Mobile, Samsung Galaxy SIII] EXV:
Having an issue where, I believe, after disconnecting from Bluetooth, I lose all speaker audio (notifications, video audio, music audio, etc). A reboot fixes it but curious if this happened to anyone else?
[T-Mobile, Samsung Galaxy SIII] MV10:
Yeah if you check my posts in this thread I've been having it ever since I moved to 4.3. Perseus71 has been looking into it.

Something interesting to try, which I noticed a few days ago -- after audio is dead, place a call and put it on speakerphone and see if audio starts working again after a few seconds.
[T-Mobile, Samsung Galaxy SIII] Perseus:
Attention [MENTION=4830253]Danvdh[/MENTION] as well.

I believe, this may be due to the Stock Kernel that ships with the Rom. Are you [MENTION=2751810]MV10[/MENTION] & [MENTION=3341435]EXV[/MENTION] game enough to try another Kernel ?

I have exclusively and exhaustively tested 2.0 Release with recent releases of KT747 (10-27 also 11-04). I am unable to re-produce the issue you are experiencing. Do note, just because I can't reproduce it, doesn't mean it doesn't exist. I had seen the issue before on 4.2 release of Liquidsmooth. Even more recently on 1.9 Release of Slim, after making video recording, I kept loosing sound on playback. I know KT and BMS have includes all the recent BT driver & firmware changes. However after 1.8, I am yet to see major changes to Slim Kernel. Could that be an issue ?

If you guys can think of a way for me to test, I am game. Before I forget, I should remind you that I freeze Music app that comes with slim. (I hate it with some fervor.) I did toy with freezing Bluetooth Share app. That made impossible to turn on Bluetooth.
[T-Mobile, Samsung Galaxy SIII] MV10:
I wish I could, but I have a major data center re-location to babysit this weekend and I can't risk borking my phone.

Maybe next week though.

I just remembered I have a Xantech A2DP receiver in the master bathroom at home. I'll give that a try and see if I lose audio through that, too. I never use it, it's there for my wife, I forgot all about it. Can't hurt to have more tests.
[T-Mobile, Samsung Galaxy SIII] Perseus:
Good Luck with the Data Center move and A2DP. I can't say which is more perilous. :p Always remember Murphy's Law.

So If no one has any cases for me to test on Bluetooth, I may start paying attention to why we can't get PhotoSphere, unless anyone has it working on Build 2.
[T-Mobile, Samsung Galaxy SIII] itsLYNDZ:
Can someone link to where the newest stable version of this in 4.2.2? I dont think im up for 4.3 yet, ha! But I would like to try this with 4.2.2 since im still using a TW rom. Also, anything I should know as far as bugs or what doesnt work?

I looked on the OP and the link where it says download here has many different official versions. Im not sure which I should use or which gapps...
[T-Mobile, Samsung Galaxy SIII] Gungrave223:
Wait so the rom label d2att will work on tmoible?
[T-Mobile, Samsung Galaxy SIII] Gungrave223:
cool thanks.
[T-Mobile, Samsung Galaxy SIII] EXV:
This issue has existed since the initial release of 4.3 for me. That, along with a few other minor bugs, led me back to the last 4.2.2 stable. But this latest stable is unbelievably amazing, I don't ever want to switch to anything else. My phone feels faster than ever, more responsive, and battery life has been the best it's ever been (with the Zerolemon, I'm getting 14 hours So, 3 full days on a single charge).

I would definitely love to help but ktoonz has never played well with my phone. I had awful battery life and random reboots galore. BMS has given me good battery life at the expense of even more random reboots and scratchy audio. The current stock kernel has been the best I've ever seen and I don't want to jynx it by switching out. A little paranoid since this is the best it's ever been.

The issue may also arise from putting the phone on silent. I know in the past I have noticed my phone losing audio when I restore sound/vibration from silent mode. I recently took off the silent mode from my notification toggles and I haven't had an issue since. Maybe that's causing an issue?
[T-Mobile, Samsung Galaxy SIII] Perseus:
Quiet possible. Sometimes the Quick Toggles don't effectively restore volumes. So I guess it didn't have anything to Bluetooth ?
[T-Mobile, Samsung Galaxy SIII] Perseus:
Wrong ROM Thread.
[T-Mobile, Samsung Galaxy SIII] MV10:
FWIW, I'm in and out of meetings all day and turn silent on and off all the time. I typically use the power menu to do this, but I've never lost audio from that. (I always run the stock kernel, haven't really had time to play with anything else.)
[T-Mobile, Samsung Galaxy SIII] SiNJiN76:
Wondering if anybody is familiar with the phone randomly selecting 15 seconds for display to sleep...also for it turn on the Auto Brightness at random.
[T-Mobile, Samsung Galaxy SIII] EXV:
Not 100% sure but I'm beginning to notice that it may just be the silent toggle on my end. I'll continue testing it. Btw I've never been so pleased with a ROM before. This is exactly how the S3 should have came out.
[T-Mobile, Samsung Galaxy SIII] Perseus:
I always have those 2 set that way. Whats your questionn?
[T-Mobile, Samsung Galaxy SIII] SiNJiN76:
I don't use auto brightness and I have my screen timeout @ 5 minutes. But this past couple weeks...I noticed that it had somehow made itself at home, turned auto brightness on AND screen timeout to 15 seconds.

Doesn't happen too often, so I'm not freaking out about it, yet. Ha ha ha
[T-Mobile, Samsung Galaxy SIII] MV10:
lol... I think that every time I see the garish TouchWiz interface on my wife's S4.

She's a mobile app developer so she believes she should keep the stock system so she knows what most people use.

*shrug* Her loss!
[T-Mobile, Samsung Galaxy SIII] Perseus:
Could be some "Battery Saver" app turning it down ?

Do you remember the "IE" mentality of web develoeprs ? If it works in IE its good for us all ? :rolleyes:

Sorry about OT.
[T-Mobile, Samsung Galaxy SIII] Danvdh:
https://github.com/SlimRoms/vendor_slim/commit/500377c55455326be8015e26ea9ca8abf05e50ce

build 2.1 should be here this weekend, this will be the final 4.3.1 stable from Slim
[T-Mobile, Samsung Galaxy SIII] itsLYNDZ:
Flashed this coming from a 4.2 rom and it looks like I lost root. How do I get it back without having to reflash the rom?

Does this rom not have Power Save Mode like 4.2 did? What can I do to save battery as far as adjustments? (kernel, cpu, governors...)

Could anyone post the wallpaper that is in the screenshots on the first post? Also, is there another 4.3 messaging apk I can flash that gets rid of the contact icons? I see you can remove them from the conversation list, but thats not what I mean. Thanks.
[T-Mobile, Samsung Galaxy SIII] SiNJiN76:
Try going into developer settings and allow root to apps.
[T-Mobile, Samsung Galaxy SIII] Perseus:
For Root, you need to go to Settings > About and then click on Build Number 7 times. Then back into settings you will see Developer options. Under it, you will see Root Access option. In it, choose ADB & Apps.

For Power Save, there's performance settings under Settings > Advanced. If you want to tune Governer and Scheduler, see the reference thread on undervolting in my signature.

If you use Aroma Gapps from Slim, there's a Message apk that you can use. The wallpaper in OP is the same one you get upon fresh install of this Rom.
[T-Mobile, Samsung Galaxy SIII] itsLYNDZ:
In did a fresh install and didnt get the wallpaper. Just the blank with blue slim rom circle. Can you link to the messaging apk you mentioned? Could you also suggest a governor/ I/O scheduler and cpu ranges for this rom? I have tried so many different combinations for each rom ive used, just would like to hear what works best with this rom.
[T-Mobile, Samsung Galaxy SIII] Perseus:
Isn't that what the Wallpaper is in the OP Screens ? That Skyline must be some City somewhere. Difficult to predict it.

The Aroma Gapps are here.
[T-Mobile, Samsung Galaxy SIII] blk_jack:
Obviously you're experiencing abnormal behavior. Do some troubleshooting, get some logs, reflash the ROM with a different recovery, etc.

You're reporting issues other users don't have, and this is a development thread, so you should assume the issue is on your end and not only debug your issues, but also report them in the appropriate manner with logs and detailed information.
[T-Mobile, Samsung Galaxy SIII] blk_jack:
Are you using TWRP 2.6?
[T-Mobile, Samsung Galaxy SIII] nicky9door:
Developer options are found in the dev tools app
[T-Mobile, Samsung Galaxy SIII] garymachete:
Oh its "bricked" then? You can give it to me, I'll take that "brick". I think this ROM may be a bit above your understanding. Its easy to fix an imei error. You gotta read buddy. The problems u r having are definitely some sort of user error. This ROM is rock solid, and there's almost no way to brick your phone if you know what u r doing. Don't let this deter you, just do your homework before posting non dev feedback. Happy flashing!

Slim 4.3
[T-Mobile, Samsung Galaxy SIII] PhrostB:
What is this, an OS for ants?!?!

Please use the default dpi in the future! Otherwise, the rom looks pretty good!
[T-Mobile, Samsung Galaxy SIII] garymachete:
No way, 245 is perfect. 320 is huge. It is a 4.8 screen. Use that real estate!

Slim 4.3
[T-Mobile, Samsung Galaxy SIII] PhrostB:
320 is fine and there's no reason to change the default value. Make it optional, sure, but don't force it by default. 245 makes it hard to read things, you have to hold the phone really close.
[T-Mobile, Samsung Galaxy SIII] chrisokaly:
nah, audio recording is still borked. I think its a CM/AOSP base issue as im remembering its been a problem since CM10. CM9 was good, but since then any audio recording sounds like its 100 feet away. Easiest way to test is by recording while watching TV; Stock rom and CM9 recording sounds like youd hear it while sitting in the room. CM10 you can barely hear it. I know Faux has a sound mod to increase the gain but its not compatible with all kernels, and it still doesn't sound right.
[T-Mobile, Samsung Galaxy SIII] blk_jack:
I realize this, however, in the second beta 2 build (sans number at the end of the filename) it includes this patch: https://github.com/SlimRoms/device_samsung_d2-common/commit/9d242ff22cbe8810945187bed3583d5d3e896296

Edit: to make myself more clear, two beta 2 builds were made available. The second one was posted a full day after the first one and has a different filename and sha1sum hash. Check either of those to make sure you're on the second posted beta 2 build.
[T-Mobile, Samsung Galaxy SIII] jdidtht:
So then Odin back to stock and leave it.

infected sgh-t999
[T-Mobile, Samsung Galaxy SIII] nirogu325:
I'm using the second beta 2 and am noticing a bit of distortion in my audio recordings. At least with the patch things are slowly getting there. Apart from that and the root issue I encountered (which I fixed by installing SuperSU from the play store), the ROM is perfectly smooth and stable for a beta. You guys are doing an excellent job.

---------- Post added at 01:28 AM ---------- Previous post was at 01:24 AM ----------

It's actually easy to use 7Zip to find and edit the DPI value inside the build.prop so you can flash and start with your desired DPI. I do it all the time to customize before flashing.
[T-Mobile, Samsung Galaxy SIII] blk_jack:
The next build will have another fix for the recording volume which should further smooth things out.

You also under no circumstances need to use SuperSU if you're activating root first (within Developer options or Superuser). I've never used SuperSU and root has always worked perfectly fine for me (as well for my testers & many other users).

Slim retains any DPI modifications you choose when you flash new builds of the ROM. The only time it will wipe your DPI to the "Slim stock" value is if you do a full wipe or manually wipe /system first.

Anyway, don't want this post to seem ungrateful for your kind words, there's just a lot of misinformation going around right now based on the changes 4.3 introduces and there's a lot of "install SuperSU" as this magical solution when really the problem is with root not being activated properly when first installing the ROM.

TLDR; You must explicitly grant Superuser root access in 4.3. It is not inherently activated when you install the ROM, you need to manually set it in Developer options or Superuser.
[T-Mobile, Samsung Galaxy SIII] nirogu325:
I see, thanks a lot for the new information. Well, I did use the FAQ you posted (read it twice actually) about how to properly activate root. The two specific apps which gave me issues with root even after following the FAQ is the V4A Audio Mod app when trying to install the driver. Also, Root Explorer 3.1 reported lack of space in /system/ whenever I tried to move anything there. The errors on that app also stopped when I installed SuperSU, so I dunno. I always do a full wipe twice before flashing any ROM, any build.
[T-Mobile, Samsung Galaxy SIII] blk_jack:
I haven't done enough testing, but what I think might be happening is if Superuser gets a request for root before its been given permission by Android itself, it will silently deny that app's future root requests even after it is given access (and possibly mangle the app's request response, so the app gets confused & doesn't realize it is being denied).

As far as I'm concerned we need to enable root on all new installs by default since Superuser is still required to ultimately grant/deny access on a per-app basis, and all this confusion is creating a ton of headaches for quite a few users.

If 95% of users are activating root then the most logical course of action is to enable root by default (a la 4.2.2) and let the other 5% change the settings to disable Superuser, rather than what is happening right now which is of course the opposite.

I'll petition for it to the rest of the team & hopefully put an end to this madness!
[T-Mobile, Samsung Galaxy SIII] jdidtht:
Root explorer just had an update to day to make it more compatable with 4.3 internal storage mounting issue.

infected sgh-t999
[T-Mobile, Samsung Galaxy SIII] zeusakatkm:
Has anyone seen this yet?
[T-Mobile, Samsung Galaxy SIII] jdidtht:
I just googled it and its an error that appears to happen even back in late 2010 and 2011. I read some responses and everyone just said to rewipe. I also read some people that clicked I'm feeling lucky experienced a million reboots. Of just factory reset and give it another go..

infected sgh-t999
[T-Mobile, Samsung Galaxy SIII] blk_jack:
Before wiping try to fix permissions from recovery.
[T-Mobile, Samsung Galaxy SIII] PhrostB:
For some reason it's not remembering the password on my home wifi network.
[T-Mobile, Samsung Galaxy SIII] jdidtht:
Your a patient man.

infected sgh-t999

---------- Post added at 11:29 PM ---------- Previous post was at 11:29 PM ----------

So what did you try to remedy this? Mines fine

infected sgh-t999
[T-Mobile, Samsung Galaxy SIII] itsLYNDZ:
Oh I really wanted the city lights one. does anyone still have it that they could post? And I used another gapps I guess when I flashed the rom. Would I have to reflash to use the aroma gapps? Or can I just extract or drop the messaging apk into /system/apps like when replacing the messaging app normally?

Im also noticing that Titanium Backup wont let me make Google Services Framework int oa user app, and greenify donation doesnt show it. So im not sure how to hibernate that. I did make google play services into a user app, but everything keeps force closing now. So much for trying to save battery my Greenifying those...

Can you suggest a governor and io combination
[T-Mobile, Samsung Galaxy SIII] itsLYNDZ:
I also wanted to see how to adjust the screen resolution. Currently everything is so small and I have space for 7 icons across my home screen instead of the normal 5. How do I get it back so only 5 fit? Everything is so tiny, even with font size set to huge. I think the DPI or something needs to be made smaller, but not sure what size to make it so I get 5 rows of icons across rather than 7. And is there a place to get the black and white circle icons shown in the screen shots in the original post?
[T-Mobile, Samsung Galaxy SIII] SiNJiN76:
Follow instructions in Setting... Interface... Lcd density
[T-Mobile, Samsung Galaxy SIII] Perseus:
You should use these gapps as they have been tested to work with the Rom. Expect possible issues if you used other Gapps.You can't extact from Aroma I believe. You could get the AIO app from that link and try to extract from it. GSF is unlikely to be user Apps. If you still want to Greenify, take it on Greenify's thread.

For Governer, I have already given suggested combinations in the post 8 of the thread linked before. If you don't want to read then there's not likely to be much help.
[T-Mobile, Samsung Galaxy SIII] itsLYNDZ:
I have read the thread on governors and i/o schedulers. I just dont understand all that stuff... Im using Slim AIO gapps.

I changed the LCD density to 320, followed all the instructions and now everytime I open the Play store I get No internet connection. What should I do?
[T-Mobile, Samsung Galaxy SIII] damngood98:
only when you're using the play store? try clearing the data on the app and see if that works
[T-Mobile, Samsung Galaxy SIII] itsLYNDZ:
It looks like it wasnt clearing everything in the Interface-LCD steps where you have to click clear google data.
[T-Mobile, Samsung Galaxy SIII] damngood98:
so did you get it working now? what gapps do you use btw? slim gapps include the multi dpi playstore app...if you're using something else it could be why you're having issues
[T-Mobile, Samsung Galaxy SIII] itsLYNDZ:
Im using Slim AIO gapps. Its working now. Just need to change the governor and i/o now... Do you know of another messaging apk I can either flash or drop into /system/apps that gets rid of the contact user icons on every line of the conversation?
[T-Mobile, Samsung Galaxy SIII] damngood98:
sory, not off hand...never really bothered me, lol
[T-Mobile, Samsung Galaxy SIII] itsLYNDZ:
does anyone have the city skyline background from the OP screenshots?
[T-Mobile, Samsung Galaxy SIII] Perseus:
Change the Governor to Conservative and Scheduler to either ROW or SIO. For Battery, Lock the Max Frequency to 1350 MHZ.

Do Note, playing with Governor and Schedulers is inherently risky. There is a very serious possibility of hardbricking your device if you did wrong change. Follow any advice with care.
[T-Mobile, Samsung Galaxy SIII] Perseus:
Thanks [MENTION=4830253]Danvdh[/MENTION]. Based on the the change log, I am hoping they do get Bluetooth right. Finally after much fits and starts the BT had stabilized in 2.0 version.

General Question. Has anyone with the 2.0 Rom ever used a Photosphere Camera successfully without crashing ? Typically all 4.3 Camera apps I have seen, will freeze after taking a Picture.
[T-Mobile, Samsung Galaxy SIII] Danvdh:
We will see

I'm syncing now and I will get a build out soon
[T-Mobile, Samsung Galaxy SIII] thepa:
quick question n/m
[T-Mobile, Samsung Galaxy SIII] Markdental:
If we are coming from 2.0 do we need to wipe before upgrading?

Also, I don't see the links up for either 2.1 or 2.2 on slims website.

Anyone know where I can find them?
[T-Mobile, Samsung Galaxy SIII] RedJack117:
Does anyone know how to get viper to work? I've heard talk of a build prop edit but I've had no luck finding it
[T-Mobile, Samsung Galaxy SIII] galahadUSA:
Couldn't get it to work on any SLim Rom after 1.6 nightly. So that's where I stay if I want to use viper.

I'm now on 4.4 unofficial and viper works like a charm. Go figure.

---------- Post added at 10:16 AM ---------- Previous post was at 10:14 AM ----------

Hasn't been released for us yet.
[T-Mobile, Samsung Galaxy SIII] Unythios:
Why does it say T-mo yet all the files are d2att?
[T-Mobile, Samsung Galaxy SIII] Perseus:
Developed for the ATT S3, works great on the T-Mo S3.
[T-Mobile, Samsung Galaxy SIII] scott7175:
Cause the devices are almost identical other then carrier modem and garbage
[T-Mobile, Samsung Galaxy SIII] Unythios:
Ok because SlimBean 4.2.2 changed my device to an i747 and that caused me issues when flashing a few other test ROMs. Will this one do the same thing?
[T-Mobile, Samsung Galaxy SIII] itsLYNDZ:
Does anything need to be done to revert that back to Tmobile when flashing a different non slimbean att rom? Will I have problems if i try to flash another Tmobile rom?

Im excited for the RC. Just got a random reboot. the first one ive had since flashing this a week ago.
[T-Mobile, Samsung Galaxy SIII] Unythios:
I had to Nandroid Restore back to a previous T-mo ROM that I had and then redownload the CWM for T-MO devices instead of ATT devices.
[T-Mobile, Samsung Galaxy SIII] galahadUSA:
Because T Mobile and AT&T S3 are pretty much the same phone...some folks say we can run AT&T roms. But always use aT Mobile kernel.

---------- Post added at 04:14 PM ---------- Previous post was at 04:10 PM ----------

Never use another carries recovery. That's where your issue was I bet.

I've run slim for months with zero issue.
[T-Mobile, Samsung Galaxy SIII] Unythios:
CWM auto found the one that matched my build number since Slim changed it in the build.prop......so CWM is the one that installed the d2att recovery not me.

also......I just flashed Build 2 of this ROM and for some reason my connection is always grey and not blue indicating that I'm not synced or connected to Google's servers and even though I have 3G and H+ it tells me I have no connection in the Play Store and I'm not able to view the store. Anyone know about this?
[T-Mobile, Samsung Galaxy SIII] Perseus:
First flash [MENTION=5082757]LuigiBull23[/MENTION] 's Revert zip. This will make your device to report as T999. Next try CWM Auto, it should give T999 Recovery.

As to the Grey icons, have you flashed any mods ? If not, then please Factory Reset in the Recovery.
[T-Mobile, Samsung Galaxy SIII] Unythios:
I just went into recovery and wiped data factory reset and wiped cache. It sat in a boot loop for 20 mins.....I pulled battery same thing. Then I pulled the battery again now it's finally at the Welcome screen.....
[T-Mobile, Samsung Galaxy SIII] Perseus:
Given T-Mo bloat, it will take nearly an hour after Wiping Cache. You need to be patient.
[T-Mobile, Samsung Galaxy SIII] itsLYNDZ:
So will I have to do that same? I can revert to a Nandroid saved rom used previously, but do i have to re-download CWM? Even tho ive previously used all Tmobile roms on my Tmobile S3?
[T-Mobile, Samsung Galaxy SIII] SiNJiN76:
So, I played around with my build.prop file just a little bit. I made a backup to my external first. Something went wrong...so I thought simply replacing the corrupt file with the back up I made would be fine, but I got stuck in a bootloop. Wiped both caches and still nothing. (It's fixed) Just wondering...if there is a 'proper' way to replace the build.prop or did I just have bad luck?
[T-Mobile, Samsung Galaxy SIII] Perseus:
You are supposed to Grant Permissions RW-R-R to the file after replacing it back.
[T-Mobile, Samsung Galaxy SIII] SiNJiN76:
Man. I kept looking at that too. Thanks. Hope I Remember next time.
[T-Mobile, Samsung Galaxy SIII] Perseus:
Modifying Build.prop raw is a pain in the what. Best either make a quick flash file or use build.prop editor.
[T-Mobile, Samsung Galaxy SIII] itsLYNDZ:
I cant seem to get the battery drain with this rom under control. Its been sitting all morning on my desk and its drained 14%. Im definitely not having great battery life like on a 4.2 rom.
[T-Mobile, Samsung Galaxy SIII] Perseus:
Please Install Better Battery Stats app and post your Text dump from it. Post on the Apps thread not here.
[T-Mobile, Samsung Galaxy SIII] itsLYNDZ:
i have been posting over there...
[T-Mobile, Samsung Galaxy SIII] Perseus:
Yes I am aware, I am just trying to save time of others who might be drawing wrong conclusions from your incomplete post.