yashsingh1/xdaforums huggingface dataset:
[Verizon Samsung Galaxy S III] SlimSnoopOS:
Gotcha. I switched from Minimal to AIO a few weeks back so that I could have TRDS on more apps and I just like to keep things consistent. I typically keep one set of gapps saved to my phone at a time, and that's where the confusion came up. I've since gone with the Full gapps whether its beta or stable and debloat from there.
[Verizon Samsung Galaxy S III] damnhao:
i'm having a location issue. i just did a clean install of 6.0 and location services was working. as i start re-downloading all of my apps, my location switch on/off no longer works. i had this issue with the previous slimkat 5.0 as well but i put off fixing it(it was working and mysteriously broke). i'm not sure what app is causing the issue but some apps i might suspect is xposed framework, gravitybox or waze, which were the last few apps i installed. anyone else having the same issue?

my last resort would be to do another clean install.
[Verizon Samsung Galaxy S III] Perseus:
You can use Settings >Apps > App Details >Modify to revoke the permission of the app to use Location Service. If that does not work, try wiping dalvik + Cache. If that too fails you will have to re-flash.

TO ALL - May I please Ask a Favor ?

On this page, you have an opportunity to Review this Rom. Can you take some time to Review it please ?
[Verizon Samsung Galaxy S III] damnhao:
i just did a fresh install and everything was working till realized what caused my location issue. if i switch location modes from "device only" or "battery saving" it's fine. i can turn off location and turn it back on. once i switch to "high accuracy," the location on/off switch is then stuck and doesnt work anymore. because of this, i do not have the option to change the mode back to "battery saving" or "device only."

just tried to wipe dalvik + cache did not fix it
[Verizon Samsung Galaxy S III] Perseus:
Wipe data to Google maps and Google Settings. Also check

https://www.google.com/settings/accounthistory?hl=en

I just checked and this did not happen to me. Are you using a specific Non-Google app that needs location ?
[Verizon Samsung Galaxy S III] damnhao:
i tried wiping data for those two items, then wiping data for every google item along with a reboot, still not working. since i cannot turn on the locations at all, it does not tell me which recent app has requested location services. the only ones i see that may want to use locations is: instagram, snapchat, hangouts, and facebook messenger.
[Verizon Samsung Galaxy S III] Perseus:
After the most recent Factory Reset, did you restore any apps by titanium Backup or any other method ? Particularly the data of any of the apps ?

What about the other suggestion I had before ?
[Verizon Samsung Galaxy S III] damnhao:
no, i manually reinstalled all my apps, which is very tedious. as for revoking location services per app, i just tried going through my apps and doing so, still will not turn on.
[Verizon Samsung Galaxy S III] Perseus:
When you said Not Turning On, you mean Location Service won't set to Low Power mode right ? Last you had said, it turns on but won't switch back to battery saver mode.
[Verizon Samsung Galaxy S III] damnhao:
originally i did a fresh install and locations was working. i can turn the switch on and off. i can choose between "device only" and "battery saving" and it'll work just fine. however, if i switch to "high accuracy," locations stops working completely. the on/off switch does nothing. here's a video:

https://www.youtube.com/watch?v=gKk3h_jiZmk&feature=youtube_gdata_player
[Verizon Samsung Galaxy S III] Perseus:
Did you try my other suggestions ?
[Verizon Samsung Galaxy S III] Jdelta9889:
That is weird, I dirty flashed over 5.8 and do not have that issue. Running 6.0 now..
[Verizon Samsung Galaxy S III] damnhao:
i tried all the suggestions you specifically told me. was there something else that you suggested to others?
[Verizon Samsung Galaxy S III] Perseus:
Did you visit https://www.google.com/settings/accounthistory?hl=en ? does it report your location correctly ? What does it say in "Google Settings" app for Location Reporting and Location history ?

Before you proceed, take a copy of Google Maps apk from /data/app to your sd card.

It is possible, your GPS Sensor firmware got corrupted. Please go back to stock. Make sure to use the same Google ID you have now. No Mods or anything. Then follow [*gps fix] alternate gps fix] (Yes I know its not your device.). After that is done, check to make sure Google Maps does report your position pretty accurately. If it does then go into Google Settings app and turn off Location Reporting and Location History. Goto the URL above and delete all your history.

Once that's done, take a nandroid, do a factory reset then flash just this Rom and GApps. When you boot, and it prompts you to enter your Google ID, Choose I don't have one. Proceed with the rest. When that's done, install google maps alone from the copy you had grabbed earlier. See if it can see you on the map. If it does, Log on to your Google account (Settings > Account). It will probably start downloading apps you had before all this. Let that complete. Don't even think about restoring any data. Just go back and check for position on the map. It shouldn't be able to if you followed so far. Let me know when you reach there.
[Verizon Samsung Galaxy S III] BattsNotIncld:
I know it sounds stupid but the first thing I do whenever I have gps issues is to tighten all the screws on the back. Your problem sounds more software/firmware related so this probably won't help but it's worth a shot.

It's not out of the realm of possibility that you got a bad download. Try to re-download the ROM zip and flash again.

Have you tried a different ROM? Maybe it's just an issue with your phone and Slim?

Tried a different kernel? I don't think that would have anything to do with it but you never know. Leankernel runs great for me with 6.0.

If none of those work I would definitely try and go back to stock like Perseus71 suggested. Just make sure you ODIN a 4.1.2 firmware like MF1 or earlier. Also under no circumstances take an OTA otherwise you risk the chance of locking your bootloader up.

If none of that works I guess it could be a hardware issue.
[Verizon Samsung Galaxy S III] Perseus:
To Those interested in Theming -

Xtheme Engine - [MOD][XPOSED][4.0+] XThemeEngine beta5 - Theme engine for any rooted phone

It will want Xposed Framework - Xposed - General info, versions & changelog

You will be interested in #10 of the XTheme Thread. It has a mini Guide on applying themes.

Please Visit #2212 for some Screenshots by [MENTION=3698016]jorv976[/MENTION]
[Verizon Samsung Galaxy S III] draexo:
Clean flashed the new stable to get rid of the Google + issues I was having. I was unable to download anything from Play Store. Kept getting PRC-3 error??? Had to restore back to my old nandroid.
[Verizon Samsung Galaxy S III] tlogank:
For clarity, what is the ideal modem to be on with the ROM? And can anyone share said modem?
[Verizon Samsung Galaxy S III] BattsNotIncld:
This happened to me as well but a reboot fixed it.
[Verizon Samsung Galaxy S III] draexo:
Wish I had thought of that. Wonder why it happened.
[Verizon Samsung Galaxy S III] Perseus:
Modem Choice depends on your location and signal strength. Assuming you have the right APN going, I'd try to pick up most recent modem for your device. EXCEPT THE 4.4.2 UPDATE MODEM UNLESS YOU HAVE ACCEPTED THE 4.4.2 UPDATE.

The very latest 4.4.2 modem has been known to cause bricks.
[Verizon Samsung Galaxy S III] Perseus:
OP Updated with Theming Engine related Links.
[Verizon Samsung Galaxy S III] NMEAGENT:
So i downloaded the normal beta gapps but i dont want certain apps in the /system/app folder in the zip. Can I just delete the apk files in the zip and then flash it?
[Verizon Samsung Galaxy S III] Perseus:
Yes you may. But if you run into signature errors then you'd have to flash as is and then remove the ones you don't want.

If you past the com.google.xxxxx name of the APK into Google, it will tell you what exact app it is. Some of these names are confusing.
[Verizon Samsung Galaxy S III] t1n0m3n:
I don't expect this to be fixed, but are the Bluetooth A2DP streaming crashes (skipping, BT APP crashes, etc) fixed in 4.4.4? Anyone try it yet?

I suspect that it is not, but since search seems to be non-functional on this thread, I figured I would make sure.
[Verizon Samsung Galaxy S III] SlimSnoopOS:
I always uninstall, with Titanium Backup, about 5 of the apps after installing the rom and gapps. Usually G+, Hangouts, and a couple others in /system.
[Verizon Samsung Galaxy S III] Fivecent:
Anyone else running into issues with 2-step verificaton? I run into an error that says "There was a problem communicating with Google server. Try again later" whenever it tries to open the browser sign-in. This is not a problem on other devices / ROMs.
[Verizon Samsung Galaxy S III] gadgetguy08:
I have seen that previously and think it is related to the issues with the Stock Browser and Google sites. If you try to go to Google News and such with the Stock Browser do you have issues? For me it isn't consistent, but it is frequent.
[Verizon Samsung Galaxy S III] Fivecent:
[/COLOR]

Oh, bizarre. I just tried to go to vanilla Google.com and it kicked back an error saying "net::ERR_EMPTY_RESPONSE" Same thing with other subdomains.

Other sites work just fine.

I remember hearing that the stock browser was screwy, so I tried to freeze it with TiBU, but it wouldn't re-associate with a new browser.

Any workaround?

Edit: not a hosts problem
[Verizon Samsung Galaxy S III] Magicman500:
Just worked fine for me. Clean flashed to 6.0 stable.
[Verizon Samsung Galaxy S III] Fivecent:
I also clean flashed.
[Verizon Samsung Galaxy S III] draexo:
My second clean flash of six didn't go well either. Seemed fine until I did two things: Install Nova Launcher 3 beta and change that silly DPI so I can read it. I rebooted for DPI change and it hung on SlimKat screen. Rebooted cleaning cache and dalvik and same. Since DPI change shouldn't have made a difference....

Any one else survive a reboot after installing Nova Launcher 3 beta?
[Verizon Samsung Galaxy S III] Fivecent:
Haven't been able to find a single solution anywhere as to why the stock browser won't go to Google sites. Rolling back to 4.4.2 until this gets figured out as it completely breaks 2 step authentication.
[Verizon Samsung Galaxy S III] Magicman500:
SlimKat seems to be randomly rebooting when I use the keyboard. Is anyone else having this problem? It's very sporadic. Most days it doesn't happen, some days it'll happen multiple times. I was hoping a clean flash to the latest stable would fix it, but it's already happened twice in a few hours. I use SwiftKey, I don't know if that makes a difference.
[Verizon Samsung Galaxy S III] draexo:
I get random reboots once or twice a day with "stable" build 6 and can't seem to get a clean install to take.
[Verizon Samsung Galaxy S III] Magicman500:
Random reboots while using the keyboard are particularly bad, because I'm usually trying to respond to some sort of message. It'd be great if anyone knew of a solution.

Did you try flashing and then not installing Nova Launcher?
[Verizon Samsung Galaxy S III] draexo:
I've between running 6 since it came out. Dirty flashed. Tried to clean flash after all the problems with Google Plus and Google Photo and the random reboots. I rebooted twice. I had super user issues that asked me to reboot and then again after I restored my text messages with TiBu. I was using the phone and decided to try the Nova 3 beta. I installed it and was using the phone. Finally decided to fix the DPI using textdroid and rebooted and that was it. Had to nandroid.
[Verizon Samsung Galaxy S III] SlimSnoopOS:
I flashed SlimKat stable 6 a few days ago and aside from my initial boot lacking any ringtones, fixed after a reboot, I have been running smoothly ever since. I have not been putting my phone through its normal paces though cuz of independence day and working night shifts this week but stable 6 is running fine for me. I've even been using ART for a few days, yes I greatly miss Xposed + XHalo, but ART isn't so bad. I'll switch back to Dalvik soon enough. I have no comment on battery life because of work and such but its running fine. All of this with BMS 7/01 kernel now installed but I ran with stock kernel for a day and it was smooth too. Appreciate the continued support Nick!
[Verizon Samsung Galaxy S III] BattsNotIncld:
I'm in the same boat as SlimSnoop. I've got 100+ hours uptime on build 6 without a single reboot. Using Leankernel 9.7.
[Verizon Samsung Galaxy S III] SwaySwayJoy:
This doesn't feel right...

Is there a kernel which works best with this ROM?
[Verizon Samsung Galaxy S III] Magicman500:
I got a random reboot today. I had just gotten a text message, and my phone was doing the standard two vibration pulses. On the second pulse, the screen went dark (But the hardware button back lights stayed on) and my phone continued to vibrate for ten to fifteen seconds, before it crashed and rebooted. I think this is the first non-IME related reboot I've had.
[Verizon Samsung Galaxy S III] jcurley:
With those with random reboots what kernel are you using?

Do you have that kernel under volted? I had some problems with build .10, but I cranked up the voltage and it seems a lot more responsive and stable.
[Verizon Samsung Galaxy S III] Magicman500:
Completely stock. Stock kernel untouched. I've had bad experiences with custom kernels and tweaking with them, so I tend to just trust that the Slim team knows what they're doing with their kernel.
[Verizon Samsung Galaxy S III] draexo:
Stock kernel. Still random reboots once or twice a day.

Dirty flash. Have not had time for clean flash.
[Verizon Samsung Galaxy S III] SlimSnoopOS:
Have either of you taken a look into the last_kmsg file to see if it was a kernel panic? The folder is in /proc. There would be errors or warnings in the line. If you want to attach the file, I won't be able to take a look until tonight. I'm not a dev so all I can do is just see what may have caused the reboot. Random reboots often generate a last-kmsg, which I believe is something the kernel produces once the phone boots back up.
[Verizon Samsung Galaxy S III] Magicman500:
Mine doesn't show any errors, probably because it's been awhile since it last crashed. I'll try to remember to pull the file after a crash, though.
[Verizon Samsung Galaxy S III] SlimSnoopOS:
Cool. If you can't attach the file, upload it to Pastebin then paste the link from the output.
[Verizon Samsung Galaxy S III] draexo:
http://pastebin.com/r31APkCk
[Verizon Samsung Galaxy S III] SlimSnoopOS:
I'm not seeing anything of note when I look at that log. That's from moments after a random reboot, right? I see that the system restarted but there's nothing that I can put the cause on.
[Verizon Samsung Galaxy S III] draexo:
No idea. It's the only file in that directory with that name. Last reboot was 45 hours ago.
[Verizon Samsung Galaxy S III] SlimSnoopOS:
Oh ok. If it happens again, then catch the last_kmsg right after it boots up. Maybe it'll be more informative.
[Verizon Samsung Galaxy S III] Magicman500:
[ 721.262047] INFO: task dbs_sync/1:136 blocked for more than 120 seconds.
[ 721.267816] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
[ 722.254448] SysRq : Emergency Remount R/O

I'm not overly knowledgeable with the contents of last_kmsg. Is this not a bad thing?
[Verizon Samsung Galaxy S III] droidxxxxx:
No option to theme changer?

---------- Post added at 11:01 PM ---------- Previous post was at 10:10 PM ----------

Nevermind I figured it out lol had to read a little further.
[Verizon Samsung Galaxy S III] SlimSnoopOS:
I guess so, but idk what any of that means in the log
[Verizon Samsung Galaxy S III] Perseus:
I guess you are referring to the Emergency Remonut and not the Sync task that was waiting. My guess is Kernel realized that after the phone woke from sleep, there were disk I/O Pending. So the Scheduler requested for mounting of the Flash Memory in order to read something or execute some app. It depends on which scheduler was in effect at the time.

I wouldn't worry unless the phone lags like hell when you try to turn it on and unlock after sitting idle.
[Verizon Samsung Galaxy S III] Magicman500:
Well, the Sync task was waiting for for 20+ minutes. I thought maybe it got bogged down with not being able to run the task and crashed, but like I said, I'm just guessing, I don't know much about this. Are there any guides/tutorials on last_kmsg?
[Verizon Samsung Galaxy S III] Perseus:
Not to my knowledge.
[Verizon Samsung Galaxy S III] draexo:
I was responding to a message when it happened
[Verizon Samsung Galaxy S III] Perseus:
If anyone is curious about the kind of battery possible on Release 6, please see #145
[Verizon Samsung Galaxy S III] SlimSnoopOS:
You didn't have the screen on! lol
[Verizon Samsung Galaxy S III] Perseus:
On Purpose! I was trying to squash the Discussions that the Roms are responsible for Battery Drain or "Battery on this Rom is bad"
[Verizon Samsung Galaxy S III] droidxxxxx:
Any way to enable the Clear All button for the recents.?
[Verizon Samsung Galaxy S III] Perseus:
It was taken out for a reason. We all need to understand that Windows "Kill all" Strategy is actually Counter Productive on Android.
[Verizon Samsung Galaxy S III] carpdeeem:
Just getting back to this as I'm about to flash stable build 6. Do you know if it's an issue specifically with Slim Gapps? If so, could I avoid this issue by flashing the Gapps package from elsewhere (e.g. one of the packages from here: http://xdaforums.com/showthread.php?t=2397942) since I don't use TRDS?
[Verizon Samsung Galaxy S III] preusstang:
Bluetooth metadata is working! w00t!!1
[Verizon Samsung Galaxy S III] lepa71:
Sorry to ask. Does the camera/camcorder fully work(front and back)?

Thanks
[Verizon Samsung Galaxy S III] markapowell:
I thanked you. I don't like it! And am a bit jealous, but thanked you none the less.
[Verizon Samsung Galaxy S III] lepa71:
May I ask why you don't like it?
[Verizon Samsung Galaxy S III] markapowell:
I get 12 hours with moderate use
[Verizon Samsung Galaxy S III] draexo:
Last few weeks on Slim had bad battery experience. Always was "display". Just seemed disproportionate to use.
[Verizon Samsung Galaxy S III] Shakes The AssClown:
The new recents is cleared by doing the pinch method like if you were shrinking a picture.
[Verizon Samsung Galaxy S III] Perseus:
OP UPDATE - Weekly Release 6.2 is Out.
[Verizon Samsung Galaxy S III] NMEAGENT:
Is there a way to make the notification drawer background fully transparent? I found the setting for it but it still isn't fully transparent. I'm trying to make my phone look like android L and I want to make the notification drawer fully transparent.
[Verizon Samsung Galaxy S III] SlimSnoopOS:
Hmm, seems like the option to change display temperature in Settings/Advanced Options has been moved. I'm a little confused about what it means in the 6.2 changelog in terms of "gamma control single tunable knob using presets." Any one notice where it's relocated too? I always set my display temperature to cold" cuz I prefer that display temperature for its displaying of white.

I did remove a few system apps, like Keep, Hangouts, IRC, news & weather, and Setup Wizard if that matters.
[Verizon Samsung Galaxy S III] dpeeps74:
Mine is still showing it in the same spot there under device, but I also have no lte since the stable so maybe it's bad that I can still set the color temp?
[Verizon Samsung Galaxy S III] SlimSnoopOS:
Yea, it very well could be on my end then. I'll try reflashing after work tonight and check before uninstalling system apps.
[Verizon Samsung Galaxy S III] AdMire:
I delete the same apps you do (except Keep, I don't even see that in TiBu) and I don't see that option either under the Device setting, either.
[Verizon Samsung Galaxy S III] Kreeker:
I'm loving Slim Heads Up. I got a phone call today and it looked so nice. Unless that's something different.
[Verizon Samsung Galaxy S III] NMEAGENT:
Would I be able to flash the SlimKat Gapps on CM11? I want to try out their themes but the gapps they use have many apps that I don't need
[Verizon Samsung Galaxy S III] tlogank:
I'm currently on Build 5.10 Weekly, using modem ML1, but it's been terrible lately reception wise. I love this ROM in general, but wondering what modem you guys have had best luck with so far, and if you could tell me how to find said modem. Thanks.
[Verizon Samsung Galaxy S III] SlimSnoopOS:
I have tracked it down to CM and I think they are doing something different. Here are some of the commits that are in the Slim changelog.

Yup, it does look good. I just tried this with a test call and it looks cool. I still prefer Floatifications for my heads up notifications however.

You should. Or you could flash any of the the PA gapps. There is no "TRDS" with these apps.
[Verizon Samsung Galaxy S III] chiadrum:
Viper Audio settings,recommended Modem?

Hi all-I am running the 4.4.4 6-Official stable build Baseband I535VRLG1 and I was having pretty serious low volume issues so I installed Viper.

The funny thing is that the low volume isn't happening today anyway but the question is in the Viper setup instructions it says to go to Sound-Effects and select Viper.Where is this setting found in the Slim Rom if at all?I can't find it anywhere and my Viper driver status shows not processing.

Is there a different modem I should be running?ML1?

I just realized that I just recently did a flash back to stock to get a clean slate and maybe the VRLG1 isn't the best choice?

Much appreciated
[Verizon Samsung Galaxy S III] tlogank:
I posted about having the exact same problem a few days ago here, but I didn't receive any help really. I believe I was on the same ROM as you as well. It did seem to be intermittent (but the problem happened much more than not). I flashed the lastest weekly (6.2) and the issue hasn't happened yet, but I've only received 2-3 phone calls since flashing it.
[Verizon Samsung Galaxy S III] chiadrum:
Ok thanks good to know-so you did a dirty flash and no other issues?

Any idea about the Viper settings?Is that just not included in this oh so Slim rom?

Let's keep each other posted about call quality-Thx
[Verizon Samsung Galaxy S III] tlogank:
I was on the ML1 baseband, so seemed to be more of a ROM issue since we're on different modems. To be honest, I'm not at all familiar with Viper or what it does. And yes, I did a dirty flash. I was initially getting a lot of pop-up errors, but if you go in and clear the data from Contacts and Contacts storage and reboot, it will resolve the errors. And don't worry, assuming your contacts are synced with Google already, they will restore after the reboot.

---------- Post added at 02:05 PM ---------- Previous post was at 01:57 PM ----------

Bad news, just made a call and the low volume issue was back...so frustrating.
[Verizon Samsung Galaxy S III] chiadrum:
Oh crap-yeah that sucks and if you search that has been going on with this ROM for a long time-someone must have an answer.this is one of the most respected ROMS out there,has to be a solution.I'll let you know how mine works-installing Viper is easy enough if that somehow fixes the problem but I highly doubt it.Seems like I have just gotten lucky so far today.Other threads have mentioned using Volume control apps but the first 1 that I tried did nothing FYI.
[Verizon Samsung Galaxy S III] tlogank:
It's so low I have to put it on speaker and use the phone backwards sometimes, because it even brings the speaker volume down. A few minutes ago on a call, the volume was low and I toggled speaker a couple of times and it came back to normal...so I am mystified. Let me know how it goes for you trying Viper.
[Verizon Samsung Galaxy S III] Perseus:
For both of you, in the Phone App > Settings , what do you see under Supress Noise ? Also try Boeffla sound app app from store.
[Verizon Samsung Galaxy S III] chiadrum:
I am using EX Dialer but the stock app had Noise Suppression enabled.I unchecked it.

Do you know if/where there is a place to set Viper for Audio control or is that not an option in Slim?

Thanks for the tips!