yashsingh1/xdaforums huggingface dataset:
[Verizon Samsung Galaxy S III] Perseus:
I don't use viper. So have no Idea.
[Verizon Samsung Galaxy S III] SlimSnoopOS:
Are you using the Slim gapps Gmail or Play Store Gmail? Cuz I just noticed this too with the Slim gapps Gmail. I haven't tried using the play store gmail cuz I like the Slim theme.
[Verizon Samsung Galaxy S III] SlimSnoopOS:
System apps are slightly more difficult to remove
[Verizon Samsung Galaxy S III] dodgem2012:
You can freeze system apps with TiBu.
[Verizon Samsung Galaxy S III] SlimSnoopOS:
I'm well aware, I've owned and used Titanium Backup for 3 years now. I was more so replying to the first half of their post about uninstalling what I would guess is the regular way.
[Verizon Samsung Galaxy S III] Perseus:
Do be kind and post on [GAPPS][4.4.x] Official Slim GApps TRDS (Slimkat) [2014-07-10] so they know about the issue.

Recent versions of TIBU have not been able to remove system apps for me. Is that your observation as well ? or is it just me ? I am guessing it does does look well with the changed directory priv-app.
[Verizon Samsung Galaxy S III] SlimSnoopOS:
I'll see about posting there sometime today. I'm headed into work right now.

I was having issues removing system apps (or rather failing to) with TiBu with the switch to native SU so I around 2 stables ago I started to flash SuperSU along with each weekly. TiBu has been behaving ever since.
[Verizon Samsung Galaxy S III] chiadrum:
So I have had probably a dozen calls without issue-not sure if installing Viper and it's driver was the fix or not but can't hurt to try.I can't actually activate the Viper drivers but if I have nornal call/speaker volume who cares right?

This thread is helpful to install Viper.Once the app is installed you have to go to settings in the app and choose which drivers to install based on your CPU.That is all that I did and no audio issues yet,fingers crossed.

http://www.droidviews.com/amazing-audio-quality-on-android-viper4android-audio-effects/
[Verizon Samsung Galaxy S III] deuce237bblock:
Whenever I am in a call and I have low volume I just press the volume down button once then the volume up button once and I have normal call volume for the rest of the phone call.
[Verizon Samsung Galaxy S III] Perseus:
You can make sure by posting in [GAPPS][4.4.x] Official Slim GApps TRDS (Slimkat) [2014-07-10]
[Verizon Samsung Galaxy S III] tlogank:
Sorry for the ignorant question...but where are the APN settings at in this ROM? I went to Settings>More>Mobile Networks, but don't see it anywhere. I am trying to figure out why my phone is being recognized as a Vodafone in the play store now.
[Verizon Samsung Galaxy S III] Perseus:
APN = Access Point name So visit.

Settings>More>Mobile Networks>Access Point Names

Request to all Rom users -

I can't post a poll as such. But would like to know your opinion.

What do you think of a change of the Screen Resolution from 245 (Current Default) to 320 ?

To those who don't know, the smaller the number, the smaller the text and icons on the screen and more space for you to play. The bigger the number, the bigger will be your icons and text.
[Verizon Samsung Galaxy S III] tlogank:
I don't see it?
[Verizon Samsung Galaxy S III] Perseus:
Which Rom version do you have ? Also do you have a Sim locked Device ?

I apologize, my device is the T-mo Variant not Verizon.
[Verizon Samsung Galaxy S III] tlogank:
The d2lte version, I'm on Verizon but my phone has been showing as Vodafone in the play store, and my picture messages have been bad about coming through, so I wanted to check APN.
[Verizon Samsung Galaxy S III] Perseus:
Its Showing Vodafone possibly because your device is a d2LTE and not D2VZW. You will need to make changes with Build.prop Editor app.

As to the Picture Messages, try using another app. See what happens.
[Verizon Samsung Galaxy S III] trol1374:
When I press the power button it reboots. If I press the settings-security I get a error saying it stopped working.

I tried reflashing and no change. I did a clean install by wiping everything.

Went into settings-navigation-hardware buttons. Tried changing one to pull up the power menu and exit out. go to button and trigger it causes a reboot.
[Verizon Samsung Galaxy S III] NMEAGENT:
I prefer it as 245 because i can fit a lot more on the screen. I also think that 320 looks a little too big but that may be because I am used to 245.

Edit: You can go to strawpoll.me to set up a poll and just post the link to it here.
[Verizon Samsung Galaxy S III] trol1374:
It certainly needed to be bumped up. I used the app and moved it up to 310. Which works fine for my tired eyes.
[Verizon Samsung Galaxy S III] Perseus:
Thanks. But not supposed to post external links. The rules are pretty black and white.

I had this posted on 4 of the 5 threads. We'll see consensus. I will post it beforehand.
[Verizon Samsung Galaxy S III] dodgem2012:
I tried this when I'm in a call and press the speaker button and I still do not get the speaker to come on, I do not have the volume in call problem but when I turn it on speaker the volume in the call goes lower and when I turn the speaker off the volume in the call goes back to normal.
[Verizon Samsung Galaxy S III] deuce237bblock:
If our options are between 245 and 320 then it doesn't matter to me as I use 280 DPI.

You have to do the same steps when you switch to speaker, it works for me but that doesn't mean it will work for everyone.
[Verizon Samsung Galaxy S III] SkinnyT:
Are any of you guys able to get print share working?
[Verizon Samsung Galaxy S III] gadgetguy08:
I prefer 320 dpi, but it is easy enough to change with Textdroider.
[Verizon Samsung Galaxy S III] lvgdgts:
My preference is 320, unless it breaks functions of this ROM.
[Verizon Samsung Galaxy S III] SlimSnoopOS:
I am indifferent. I set my DPI to 280.
[Verizon Samsung Galaxy S III] tvl76:
Love the default of 245.

In the future, Can the ROM include a step during the install, to choose DPI?
[Verizon Samsung Galaxy S III] NMEAGENT:
Its easy enough to change the DPI. All you have to do is edit build.prop
[Verizon Samsung Galaxy S III] SlimSnoopOS:
It was included in SlimBean and I thought it would be reintroduced for SlimKat but that has yet to be the case.
[Verizon Samsung Galaxy S III] Perseus:
I know eventually we are going to have built-in DPI Change mechanism.

Thank you all for sharing your thoughts. I will change to 320 until that time.
[Verizon Samsung Galaxy S III] timothydonohue:
well, crap. i flashed this using twrp, now i've lost root, and it won't boot into recovery for me to flash superuser in ...can't use tibu, because it needs root access. eff.

edit: damnit. my mistake. i kept booting into odin mode, not recovery. i just needed to be holding vol up + home, not vol down + home during boot. superuser flashed and working. why isn't this added natively?
[Verizon Samsung Galaxy S III] SlimSnoopOS:
Enable developer options by tapping your build number multiple times. Then go to Settings/Developer Options/Root Access and set it for "Apps & ADB."
[Verizon Samsung Galaxy S III] timothydonohue:
thanks bud. hours ahead of you. just been so long since i've updated, i totally forgot, lol
[Verizon Samsung Galaxy S III] deuce237bblock:
This and being able to control ringtone volume while on lockscreen and this ROM will be complete.

I remember back when I was on SlimBean and being able to just wake up my screen and hold down the volume button to turn down the ringtone level when I go to school. I miss this because now I have to unlock the device then turn down the ringtone volume and then lock the device.

Sent by me.
[Verizon Samsung Galaxy S III] SlimSnoopOS:
Does anyone have any information on how to tweak the gamma control colors? I greatly dislike the move to remove display temperature from Advanced Options as I set my display to "cold." Everything looks off with the stock colors, given that I have been setting my display to "cold" for so long.
[Verizon Samsung Galaxy S III] Perseus:
Do you have a pattern or pin lock for screen ? If so that could be one of the reasons. I just tested, and Ringer control worked on Lock screen for me. I have basic slide lock.

Oh and one other thing. Under sound or someplace, (too tired now to scratch my head.) there is a control that defines weather Volume control buttons control media seek. (Next track/previous track). Make sure to turn that off.

Sorry bud. I use KT747 and it has its own color control. :p

Speaking of which I have been toying with the idea of making a build with that kernel baked in.
[Verizon Samsung Galaxy S III] deuce237bblock:
I have never used anything other than basic slider lock screen, I have been on SlimRoms for over a year and ever since SlimKat I have not had volume controls on lock screen. I do not have the media seek option enabled either.

Sent by me.
[Verizon Samsung Galaxy S III] Magicman500:
My set up is the same, and I, too, do not have the ability to change the volume on my lock screen. I see this as a good thing, though. I don't want to be accidentally turning up my phone in my pocket, or while I'm holding it with the screen off.
[Verizon Samsung Galaxy S III] infsoul:
How can I get battery life back have done clean wipes factories dirty flashes everything far as proper and varied rom installation processes
[Verizon Samsung Galaxy S III] deuce237bblock:
Back in the SlimBean days when we had the ability to change ringtone volume while on lockscreen it wouldn't do anything while screen was off. Unless you had skip track while screen off enabled.

Sent by me.
[Verizon Samsung Galaxy S III] SlimSnoopOS:
Darn haha I alternate between KT and BMS every other build or so. I'm using BMS so I always relied on the option in Advanced Options.
[Verizon Samsung Galaxy S III] Perseus:
Heads Up coming to a SlimKat near you in next weekly.

https://plus.google.com/107859134357373490612/posts/bJABHs1aNMj
[Verizon Samsung Galaxy S III] deuce237bblock:
I thought this was already introduced in 6.2?

I remember reading about it last week.

Sent by me.
[Verizon Samsung Galaxy S III] dpeeps74:
Yeah I'm already using heads up
[Verizon Samsung Galaxy S III] Perseus:
I was given to understand that there will be more changes/integration (theaming ??) this time.
[Verizon Samsung Galaxy S III] chayesfss:
Amazing, I installed this on my old gs3, had some serious issues because of my old version of clockworkmod but wow!

Once I got it installed and running and figured out how to enable root this phone was blazing fast, mega kudos devs!
[Verizon Samsung Galaxy S III] Perseus:
Post a log from BetterBatteryStats on that apps's thread.
[Verizon Samsung Galaxy S III] Bramton1:
Coming from a 4.4.3 weekly, do I need to clean flash for the 4.4.4?
[Verizon Samsung Galaxy S III] SlimSnoopOS:
Clean flash is always recommended. Otherwise, do not post about any bugs that you have found.
[Verizon Samsung Galaxy S III] NMEAGENT:
Anyone having problems with AutoVoice tasked plugin? I've already tried clearing data to no avail. The voice recognize dialogue fails to show up
[Verizon Samsung Galaxy S III] jweavis:
I prefer the stock 245. One of the many reasons I've not tried another ROM since installing SLIM a year ago.
[Verizon Samsung Galaxy S III] swolfe2:
Bad LTE Speeds

Hello all!

Here are some screenshots of my current download/upload speeds with the newest nightly version and stock kernel. Obviously, these speeds are a tad bit low, especially since I had full bars of LTE. I did a full wipe of the previous CM that was on the phone, and am also using the SK full GApps. Mobile networks is set to LTE, which is the recommended setting.

Any ideas on why this is so slow? Could my SIM be bad?

[IMG="Speedtest"]http://i.imgur.com/HPGZ4Kk.png[/IMG]

[IMG="PhoneInfo"]http://i.imgur.com/IrCN6b1.png[/IMG]
[Verizon Samsung Galaxy S III] Farabomb:
Clean install, I wasn't having issues until today. Gallery seems to be having issues. Not all the pictures are showing, maybe 50% of them. Then media starts FCing. Cleared cache in apps and davlik.

Suggestions?
[Verizon Samsung Galaxy S III] foxnutz:
Had/Have the same issue here… I just flashed the latest nightly so I'm hoping i don't run into it again. Anywhoozle, To fix this i cleared the data for Gallery and Media storage and rebooted. once phone scans SD card all is well again. i posted about it awhile ago and attempted some troubleshooting for this issue, thought it was a corrupt file or poor folder naming structure on my end… sadly i never found out why i kept experiencing this. Hope that fixes ya up.
[Verizon Samsung Galaxy S III] jonny30bass:
Thank you! Best ROM for S3.

Thank you for this ROM! My S3 is perfect now. I have tried many other ROMs, but this is the best. I haven't really had any serious bugs with the latest weekly either. It's very solid. The only thing that bugged me when I first installed the ROM was the low dpi and that the mobile data tile in quicksettings said "Roaming Indicator Off". Once I figured out how to fix both of those, this ROM became my favorite. It is a very smooth ROM with just the right amount of customizations. The heads up almost works flawlessly, and I love using it with expanded mode. Right now I'm using BMS kernel(smartmax gov/deadline io) and Faux123 Kernel Enhancement Pro tool with this ROM, and it is almost flawless. No other ROM that I have used has came close to the quality of this ROM. Thank you, and keep up the good work devs!
[Verizon Samsung Galaxy S III] Perseus:
None Reported. Try a factory Reset.

Oh Wait. what is the last System update you accepted from Verizon ?
[Verizon Samsung Galaxy S III] SlimSnoopOS:
It took me two downloads and multiple flashes to get past first boot. My first two times, I was stuck on that screen for like 10 minutes before clean flashing again. I always factory reset and format system so I know it wasn't my process. Once it booted, it took a few hours before I even had normal reboots. They initially took forever to reboot too.
[Verizon Samsung Galaxy S III] jhoutz:
I also flashed multiple times before I got this to boot.
[Verizon Samsung Galaxy S III] nicklovell23:
Users having boot issues are you using twrp? If so its been reported using cwm clears this up. Not sure why if someone using tarp can grab a logcat that would be great.
[Verizon Samsung Galaxy S III] SlimSnoopOS:
I actually thought I had a corrupt download so I downloaded it again on wifi, then again on LTE and it worked somewhat better after a few flashes. As for my long reboots, I think it may have been due to my having restored apps from when I was running ART on slimkat 6.2 although I was using dalvik on 6.4 and had not yet switched to ART. Just a theory, idk if that makes sense or would cause an issue.

Yea, I have been using TWRP 2.7.0.0 ever since it was released. I'll see about getting a log from TWRP when I find time.
[Verizon Samsung Galaxy S III] Perseus:
I was wondering if its your bootloader. Please read bellow.

Request to Those who may have Boot Issue -

If you can't boot after flashing latest 6.4 update, please see if you have got Xposed framework installed. If yes, remove it and then re-flash the Rom. It will boot. Also, if you have TWRP, update it to most recent version 2.7.1.0 if you did not have most recent version.

If you still can't boot. Please PLEASE do me a favor and follow the steps bellow to get a logcat.

I do know with the phone not booted, you can't get a logcat. However there is another way.

1. Turn off the phone and connect it to a PC.

2. Install ADB if not installed already. This thread is of great help. [TOOL] [WINDOWS] ADB, Fastboot and Drivers - 15 seconds ADB Installer v1.3

3. That thread will also install correct drivers if need be. Once you know ADB is successfully installed, run the command

adb -d logcat >mylogfile.txt

4. Now power on the phone. It may get stuck at the Slim Boot Screen. That's ok. Give it a few minutes. See if the mylogfile.txt is getting filled up. Power off the phone then attach that log file to a post here.

Make sure to say @Perseus71 in your post to attract my attention. :D
[Verizon Samsung Galaxy S III] jonny30bass:
Same for me. After a clean flash it probably took 15 minutes for initial boot, and then around 10 minutes for the next 3 or 4 times I rebooted. Then all of the sudden it started booting up really fast lol. I also restored backups of apps that were using the ART runtime...so maybe that's why? After that though, everything works great.
[Verizon Samsung Galaxy S III] SlimSnoopOS:
Xposed. Since you're asking about it, you do not have it installed.
[Verizon Samsung Galaxy S III] markapowell:
Yah my phone has been doing stupid things. I never clean flashed until 6.2 and am going to do it again in the morning. But my boot time is anywhere between 2-5 minutes. Bootlooping is crazy when it happens. My phone reboots constantly. Not *****ing. I love the ease of install on this ROM and love the ease of use. Just giving my experience. I also don't have xposed.
[Verizon Samsung Galaxy S III] Perseus:
Do you have custom Kernels or any modder apps such as SetCPU or Trickster Mod ? How about heat ?
[Verizon Samsung Galaxy S III] markapowell:
Nope. Plain Jane. Some actions take a bit to complete too. I clicked the link in the email screen goes black for 10 seconds and then opened here. Like I said I am going to clean install this morning and see what happens.
[Verizon Samsung Galaxy S III] markapowell:
Okay, so I am having a hard time with something. I went to see what version of TWRP I have and I have the 2.6.x I am trying to go in and install the latest, but under goo manager it says it can't find a recovery for my device. Okay no problem I have the TWRP app. I go there to install and a notice comes up saying that it can't find what I'm looking for.

Any thoughts?
[Verizon Samsung Galaxy S III] Perseus:
That's primarily because your device is identified as D2LTE and not as D2VZW. Not an issue. From This page please download openrecovery-twrp-2.7.1.0-d2vzw.tar. Flash it with Odin. You can do it with Mobile Odin as well.
[Verizon Samsung Galaxy S III] Prack:
I was able to use ROM Toolbox Pro to install TWRP 2.7.1.0, you can also install it with the free version from the same dev, jrummy.
[Verizon Samsung Galaxy S III] AdMire:
I believe I read in here that the new ROM flashes using ART now and not Dalvik by default which is probably why you all are seeing long boot times. My phone took/takes forever to boot anymore.

Edit: Disregard.
[Verizon Samsung Galaxy S III] SlimSnoopOS:
I clean flashed Slimkat 6.4 multiple times and it was Dalvik in developer options when the few times that it finally booted. I manually changed it to ART and rebooted when my rom settled down. Unless you saw this on the Slim Gerrit, nobody mentioned that ART is default in any Slimkat build.
[Verizon Samsung Galaxy S III] Farabomb:
Well good news is that worked to get Gallery playing nice again. Thanks.

Bad news is now it seems I've lost all notifications. Alarm didn't work this morning and notifications don't seem to work. I can change the sounds and hear them but when a TXT or something comes in I get nothing.

I did dirty flash 6.4 over 6 stable. Maybe I'll do another clean flash and see if that sorts it. Sucks I can't do it at home, my connection is far too slow and updating everything takes forever.

As for long boot times I am seeing it as well but it will eventually boot. I did have the xposed framework but I uninstalled it. Could there be some lingering code from that?
[Verizon Samsung Galaxy S III] AdMire:
I stand corrected, sorry about that. I could of sworn one of the updates I saw "ART selected by default" or something similar.

I checked mine and it goes say Dalvik.
[Verizon Samsung Galaxy S III] markapowell:
I got pissy with it so I just put clockwork mod on there. So far just one reboot for no reason. Everything else is running smooth.

Thanks again for the help.
[Verizon Samsung Galaxy S III] deuce237bblock:
I have a request, we have the ability to customize our hardware buttons and backlight, but we can't turn off haptic feedback of the hardware buttons.

I use the nav bar and have all the actions for my hardware buttons set to none and backlight turned off but I still get haptic feedback when I touch the hardware keys. Its kind of annoying cause I sometimes touch the hardware keys on accident, it would be nice if we could turn haptic feedback off for the hardware buttons.

Sent by me.
[Verizon Samsung Galaxy S III] AlexR666:
Xposed

So we cannot use xposed on 6.4 at all or just for the initial boot?
[Verizon Samsung Galaxy S III] Perseus:
Settings > Language & Input > Uncheck vibrate on Keypress. Seems to control it for me. Now if you were talking about intensity of the haptic feedback, then that's different matter.

Other users expressly tested for this when updating from 6.2 to 6.4. If you do a clean install with factory reset before flashing then you are not likely to have issue. Anything else will cause issues.
[Verizon Samsung Galaxy S III] NMEAGENT:
Is there a way to change the color of notifications in the notif drawer? I know you can change the color of the quick setting toggles but would it also be possible to change the colors of the notifications and also the bar with the time and such above them?
[Verizon Samsung Galaxy S III] Magicman500:
Forgot to post this yesterday when it happened. Got a random reboot while using the keyboard (SwiftKey).

http://pastebin.com/raw.php?i=BF6Pub9u

I copied this out of the /proc/ folder right after it booted up and put it on my external SD. I'm not sure if it worked correctly, though.
[Verizon Samsung Galaxy S III] GuitarrassDeAmor:
Okay so I just upgraded to this Rom. My phone was soft bricked? Maybe from CM 11 so I moved to this. I went back to a stock pre-rooted rom with Odin, then flashed recovery, then flashed this and gapps + reset data. Apparently I do not have root access now though? When I use Super Su it tries to install binaries and says it fails and to try again.

Any suggestions?
[Verizon Samsung Galaxy S III] nicklovell23:
About phone tap build 7x go to developer options enable root
[Verizon Samsung Galaxy S III] trol1374:
Go to settings-about phone- then click on "build number" about 7 times. You should see the count down. Then go to developer options and see "root access" click on that and chose your option.
[Verizon Samsung Galaxy S III] deuce237bblock:
All this does is turn vibration off on the keyboard. I'm talking about the hardware buttons (the menu, and back buttons).

Sent by me.
[Verizon Samsung Galaxy S III] misterx51:
settings, sound, vibrate on touch
[Verizon Samsung Galaxy S III] savagebunny:
So I abandoned AOSP roms for the last 6 months due to Bluetooth not being fixed, or crashing every time it connects to any of my devices. Came from a plagued crashing TW rom, and wanting to use 4.4.4

I haven't seen any solid CM commits at all fixing this issue of Bluetooth crashing. Any fixes on this or do I gotta use a different rom?
[Verizon Samsung Galaxy S III] NMEAGENT:
Bluetooth has been working flawlessly for many builds now. I'm running the latest weekly right now and I don't have any problems with Bluetooth.
[Verizon Samsung Galaxy S III] savagebunny:
Weird, you running the Slim-d2lte-4.4.4.build.6.4-WEEKLY-5639 I take it? I just flashed this last night, and my phone was going crazy of crashing, re-enabling bluetooth, and just going haywire, almost threw my phone at the wall cause I was getting so impatient

Also, what kernel you running, ROM baked, BMS, KT, DKP?

EDIT: Kernel change didn't work, went from DKP to KT and no change. Still crashes constantly

EDIT 2: I hate Samsung, and car manufactures and other various companies who won't agree on one protocol. My problem was due to rSAP issues, and giving HFL Access to my Phonebook, even though I kept hitting yes to give HFL phonebook access, it would constantly crash. Tried to get a rSAP fix and didn't work. Re-synced to the car, denied access to phonebook, messages, contacts etc and everything is working now.
[Verizon Samsung Galaxy S III] dodgem2012:
I use bluetooth on this ROM every weekday and I do not have any problems with connecting, works every time I get in the car, with various system types I rent and they are Ford, Chevy and Nissan, and Hyundai, usually, and all work. I do not use media tho just phone.