yashsingh1/xdaforums huggingface dataset:
[Sprint Samsung Galaxy S III] amiblindyet:
If you miss a call from a number not saved to your contacts and try to text from the drop down notification the messaging app will drop the area code.
[Sprint Samsung Galaxy S III] sixgunmojo:
I guess since I blacklist everyone not in my contacts list I have no worries. :D
[Sprint Samsung Galaxy S III] rambleon84:
I had an issue this morning where my alarm clock did not ring, just vibrated. I took a log after my initial alarm, I snoozed, and waited for the alarm again. Still no audio,just vibration. It worked fine all week too.https://www.dropbox.com/s/uwlg5ppttso9fal/bugreport.zip
[Sprint Samsung Galaxy S III] Perseus:
Did you have the phone on vibrate when you set the alarm ? Since its a repeating alarm, did you have it set to vibrate only the day before ?

According to the Logcat the Sound did start. Can you look at volume level you have set for such alarms ? Also turn off "increasing Volume" for testing to make sure it does work.

What happens when you use a different clock ?
[Sprint Samsung Galaxy S III] rambleon84:
I only ever have the phone set to on volume or silent, never just vibrate (btw love the programmable hardware button, use double tap home to toggle volume on/silent.) The alarm volume is set to about 50% and I always have it set to that, on a repeating basis. I am not sure what happened, increasing volume was fine all previous days this week and i cant think of me changing anything. I normally dont mess with the volume on my phone, use my nexus7 for most media when at home. This has happened on previous versions of slim for me but not since 4.4.4 that I can remember but it is the reason i have set to vibrate as that sound is usually enough to wake me up on its own.

I reset the phone and tested setting an alarm and everything was back to normal. Fluke? I dont know, if the log cat said the volume was normal, maybe its just something local on my end. I always clean flash when going to a new stable but only only wipe cache and format system when flashing weekly's, not sure if that matters in this case. Thanks for looking into it though, everything else is going well
[Sprint Samsung Galaxy S III] Perseus:
May be it was the Cosmic Rays or something. :) Glad its all working fine. you process for flash is pretty good. Don't think that'd matter unless you had a problem like the BT issue few releases back.

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.
[Sprint Samsung Galaxy S III] thearch1tect:
I prefer the smaller DPI to take advantage of more screen space
[Sprint Samsung Galaxy S III] sixgunmojo:
I would say leave it. Until I first tried Slim changing dpi was one of those things I had heard about but didn't care to look into as I didn't know what it really was. Once I tried Slim I was all "wtf? this is awesome", unfortunately my old man eyes couldn't take it but at the time Slim included the dpi changer. Now I change the dpi to either 280 or 300 depending on my mood when I install. This applies to any rom. I now think any rom defaulting to 320 looks childish/cartoony, for lack of a better way to describe it.

If you want to change it, I would say change the default to 280 because when SlimKat first came out (w/o the dpi changer) there were a lot of posts about how to manually change the dpi. It seemed that most people who changed the dpi were changing to 280.
[Sprint Samsung Galaxy S III] wallythander:
I would say that you should go back to 320. I think that most people go to 320 rather than something more unique, it is just the default for the device. You should definitely include a DPI changer in the ROM or put instructions into the OP for changing it manually. I have two comments or so in which I explained to confused new users how to change the DPI manually. Which is really pretty easy, I don't mind doing it, so I can't say I am all that firmly in favor of changing the default DPI. I would guess that a lower DPI is off putting to the newer potential users of Slim though. It seems to me like people who prefer a lower DPI are more adventurous and experienced users who would be less phased by changing their DPI. That is simply my impression from reading this thread and the SlimBean thread for a long time, I could be wrong.
[Sprint Samsung Galaxy S III] nostrings:
+1
[Sprint Samsung Galaxy S III] sixgunmojo:
I'll second placing an explanation in the OP, unless you change it to 320. AFAIK Slim is the only S3 rom with a non-standard dpi and new users may be confused or turned off. A short how-to on how to manually change the dpi should also be included. I know there are apps that can do it but i fear that if you mention them in the OP we will probably see a lot of requests for support/how do I use app X.
[Sprint Samsung Galaxy S III] hayzooos:
I say leave it or change it to something in the middle. One of the cool things about Slim is that feature and to have everything working with a non-320 DPI. I agree with the guys who say 320 looks cartoonish and childish. So much wasted space with icons and such that big on a screen this size.
[Sprint Samsung Galaxy S III] mremale:
I love this ROM but hate hangouts for the stock SMS! Also is there a fix for the exchange 4.4 email bug?
[Sprint Samsung Galaxy S III] sixgunmojo:
I'm mostly sure that you have to choose hangouts to be your stock messaging app. If you have already done so there are 2 ways to change back to the stock messaging app. One is in the settings of the messaging app (easiest), first choice when you go into the settings. The second (slightly less easy) is in Settings > Wireless & Networks > More > Default SMS App. Maybe even a 3rd way from the Settings > Apps > Hangouts > remove default, but you'll have to try that one on your own.

As to the exchange bug, can't help you there as I don't have an exchange email and that is one of the many, many apps I remove from my system. For the clarity of someone else who may be using it, which exchange bug do you have? A brief search leads me to believe there are a couple.
[Sprint Samsung Galaxy S III] rambleon84:
I'd like to see the DPI bumped up
[Sprint Samsung Galaxy S III] nimaim:
I'm with hayzooos and sixgunmojo here. I would absolutely not go straight from 245 to 320. 320 is cartoonishly large. Plus, it would be a HUGE change for most users. I for one LOVE 245 DPI with our current native 720p resolution; it's just a perfect match and rivals some native 1080p screens. I love that I'm the only one able to see what's on my screen with a group of people around me (who are used to super large text). If you feel that you must change it, it should be a fair compromise at ~280. I've been on Slim so long that even when I went to 280, it was too big for me, so I'm more than content with the current 245.
[Sprint Samsung Galaxy S III] Perseus:
Ok on the DPI front, we seem to have run into an unexpected wall. Yesterday I created 2 separate builds and tried on my phone. The challenge I see is that Sqisher is the last one to touch Build.prop during the build process. Unfortunately it being coded uniformly across all the devices Slim supports, it is set to change DPI to 245 if the stock is 320. Can't change that for it will affect a host of other devices that do have 320 Stock. This does not include just Samsung alone.

So that seems like a bummer to me. The usually resilient system.prop too does not survive this either. On the bright side (if one can call it that), we can expected baked in DPI changer in future. I know this is a let down and I apologize for getting the hopes up.

EDIT - Heads Up coming to a SlimKat near you in next weekly.

https://plus.google.com/107859134357373490612/posts/bJABHs1aNMj
[Sprint Samsung Galaxy S III] sixgunmojo:
Jesus dude I think you may be slightly over-estimating the skill set/intelligence level of us poor schmucks. :D

I understand it in a very, very broad sense but if that sh!ts on the test I'll take my F now and go day drinking! :laugh::laugh:
[Sprint Samsung Galaxy S III] Perseus:
Sorry I was taking out my frustrations. Long story short, no DPI change until we get built in DPI Changer. :(
[Sprint Samsung Galaxy S III] sixgunmojo:
No apology needed. I didn't read it as you venting. I read it as you giving us an explanation of what the problem was. I was just busting your balls because it was probably a little more "technical" than most of us needed.

I'll wait until you post something that sounds like a Joe Pesci soliloquy in a Scorsese mob flick before I get offended. :)
[Sprint Samsung Galaxy S III] Perseus:
Quoting Tommy D.

No, really not trying to Tick you off. :D
[Sprint Samsung Galaxy S III] zhiwlin:
2 6.4 versions?

There are 2 versions of 6.4. Are they the same? Any issues with using the earlier one?
[Sprint Samsung Galaxy S III] sixgunmojo:
From the Slim home page:

Update!: Due to possible sync issues, jenkins has been

restarted​

I would assume that we just got lucky and got two builds with no difference between the two.

My general rule of thumb in this situation is to always go with the newest unless specifically told otherwise. I'm fixing to download it now. No news is good news
[Sprint Samsung Galaxy S III] Perseus:
Nick won't let the rom be uploaded unless he knew it was all Good.
[Sprint Samsung Galaxy S III] sixgunmojo:
I just assumed that was a given. Its been awhile since I've seen a rom released and then a couple of hours later getting yanked because of serious issues. Seems most dev teams have really gotten on top of that.

On a semi-side note. If you don't mind me asking, who are you? (in relation to SK) I thought you had taken over maintenance for our phone. You obviously have the skill and inclination to build/compile and tweak (or try;)) a rom. Are you a co-maintaner, a maintainer-in-training, a super-secret-don't-let-the-plebes-know-get-roms-two-weeks-in-advance alpha tester, or something else that I can't think of right now? Lord knows I've seen you posting all over the d2 SK forums.
[Sprint Samsung Galaxy S III] Perseus:
All of the Above! Plus the secret spy of the SK team to check out the users. LOL. No Seriously speaking, I am co-maintaner for all the D2LTE SK Threads. I am a maintainer-in-training for the Rom.
[Sprint Samsung Galaxy S III] thanatos_evo:
Hello,

Switched from CM11 and I'm loving this ROM so far. A few questions (I searched here but didn't find answers)

How do I turn off screen rotation for the lock screen?

Is there any way to launch a music app when the headphone jack is connected? Not a problem if it isn't, just something I used to find really useful in CM

Any way I can have separate wallpaper for the lockscreen?
[Sprint Samsung Galaxy S III] sixgunmojo:
Cool. :good:

---------- Post added at 02:58 PM ---------- Previous post was at 02:52 PM ----------

1) Settings > Security > Lockscreen Rotation > Portrait only. I thought it was odd that enable/disable had no apparent effect but portrait only does what I want.

2) For me it is a setting in my music player (Poweramp)

3) Unfortunately no (not yet? hint, hint devs). Right now I used an Xposed module - Xposed Lockscreen Wallpaper
[Sprint Samsung Galaxy S III] JaylanPHNX:
These are good answers, and I'll add to 2) and 3).

2) Not native, but I believe there are a few apps in the Play Store that do this.

3) Xposed is an option, as mentioned, but as far as native support, I wouldn't hold my breath. It's been a back burner item for a while, something they've not said no to, but haven't gotten around to doing either. I doubt they'll get to it anything soon, since L is going to come along in a matter of months and completely change the lock screen.

From my Tab Pro 8.4
[Sprint Samsung Galaxy S III] thanatos_evo:
Is anyone else having trouble with ok Google everywhere? I had this on CM but I don't have it anymore. Tried the "trick" by searching for ok Google everywhere, but no dice.
[Sprint Samsung Galaxy S III] Perseus:
Are you talking about Google Now ? You have to install Google Search.
[Sprint Samsung Galaxy S III] thanatos_evo:
Yeah, Google now. And I have Google search 3.5.xxx which is higher than what's needed for Google now everywhere.
[Sprint Samsung Galaxy S III] nostrings:
Are you using Nova or Google launcher? If the former, you need to enable that on the Nova configuration.
[Sprint Samsung Galaxy S III] thanatos_evo:
I'm using Aviate. I don't see how that has anything to with the option being available in Google search?
[Sprint Samsung Galaxy S III] nostrings:
Ah, my apologies. I thought you had an issue with "OK Google" hotword not working for you. I had to re-read your original and follow up post to see your actual issue. I got nothing useful, unfortunately.
[Sprint Samsung Galaxy S III] sixgunmojo:
I don't normally use Google search but since I'm getting ready to wipe and do a new install I figured I'd give it a whirl. Unfortunately I was also unable to get the everywhere function to work. I tried about 3-4 times with different settings changed ( enabled in Nova, Privacy Guard on/off, re-boot w/ cache and dalvik cleared, etc ). I'll poke around a little more before I give up completely but I'm kinda bumfuzzled.

EDIT: Ok I've officially given up. I should however point out that If there are some (unknown?) Google dependencies needed my phone is not the best to test on as I use mini gapps and strip out everything I don't use or need.
[Sprint Samsung Galaxy S III] JaylanPHNX:
The OK Google everywhere thing is completely dependant on Google's backend (and the latest Search and Play Services). The keyword search suggested above seems to sometimes work (placebo?), but in the end you can only wait for Google to give it to you.

From my Tab Pro 8.4
[Sprint Samsung Galaxy S III] zhiwlin:
For those using ktoons kernel, what governor and scheduler is best combo for skimkat, for better battery? I was thinking of using smartassv2 and bfq. Is this good combo?
[Sprint Samsung Galaxy S III] Perseus:
Use Ktoonservative +Bfq. In addition, I'd undervolt by deducting 25 mv from all steps.

---------- Post added at 07:21 PM ---------- Previous post was at 07:10 PM ----------

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
[Sprint Samsung Galaxy S III] sixgunmojo:
Alrighty then, saw this just as I was going off line to flash 6.4. Looks like I'll hold off until tomorrow in case I have any issues. Plus I'm gonna have to translate those instruction to my linux box. Pretty sure I already have ADB installed but I've never had to pull a boot logcat . I'd like to know what I'm doing before I need it.
[Sprint Samsung Galaxy S III] Perseus:
[Translation Begin /]

# sudo add-apt-repository ppa:nilarimogard/webupd8
# sudo apt-get update
# sudo apt-get install android-tools-adb android-tools-fastboot

[/End Translation]
[Sprint Samsung Galaxy S III] sixgunmojo:
LOL. Thanks, completely unnecessary as I had ADB installed from the SDK, but thanks. Plus I'm pretty good at translating. :)

Quick question. Is the problem occurring on clean installs, dirty installs, or both? If its just dirty, I will override every instinct i have (shudder) and see if I can replicate (if you need).

PS Good thing I run Debian based or I'd still have to translate :D
[Sprint Samsung Galaxy S III] Perseus:
I KNEW it was unnecessary for any person running a linux box. :good: But was trying to save a bit of time. :laugh:

Problem occurs on Dirty installs. Especially when the Xposed was installed and up and running before the dirty flash.
[Sprint Samsung Galaxy S III] sixgunmojo:
Did this before I saw this post. I don't know if it will help but I just finished a dirty flash (wiped cache, dalvik only) with Xposed running, flashed 6.4 over 6.2 and have no apparent problems. Booted fine, have no fc's on the couple of apps I've opened. I did grab the boot logcat (from boot to my lockscreen widgets settling down) in case I had any problems, so if you need a logcat for a successful boot under those conditions I have it if you need it.

Getting ready to do a clean install, 'cause dirty ones make my skin crawl. I'll hold off for about an hour in case you need anything else
[Sprint Samsung Galaxy S III] Perseus:
Thanks. Did you have any of the Xposed Modules installed such as Xtheme or HKTheme ? Do please post that logcat someplace and give me the link.
[Sprint Samsung Galaxy S III] nostrings:
Is there an idea on fixing the problem, where if you turn the device off, and have it plugged in, the kernel splash backgrounb+screen stay on? It has been going on for a while (I am not sure if this is Slim specific) - just wondering...
[Sprint Samsung Galaxy S III] Perseus:
That's specific to the Kernel. You'd have to ask on its thread. Slim does have just the battery animation.
[Sprint Samsung Galaxy S III] sixgunmojo:
Here is the logcat. The only Xposed modules I had activated were AppOps, Xposed Lockscreen Wallpaper, and PlayPermissionsExpossed. I was not using HKTheme or Xtheme.
[Sprint Samsung Galaxy S III] nostrings:
I have been using Leankernel & QuantumKernel and get that from both. It's been ages since I have used the default slim kernel...
[Sprint Samsung Galaxy S III] sixgunmojo:
It's not Slim specific. I've seen a discussion about it on the CM threads. It also happens on Slim stock kernel. It's not one of those things I run into often since I rarely shut my phone completely off but when I do it, I look at my phone and go f****************k because it seems to be 50/50 time wise between opening the cover and yanking the battery or holding down the power button long enough for it to power up.
[Sprint Samsung Galaxy S III] Perseus:
Two things.

1. It is a known suggestion that the phone is likely to charge faster when on as Kernel controls the charge.

2. Recently there has been a spate of borked or intermittently borked Power Buttons. So you want to care for it. It gets stuck.
[Sprint Samsung Galaxy S III] sevenpioverthree:
So, i broke my gps somehow and my location won't turn on at all. I did a quick search and found a fix from perseus71 but am unable to do it because i have no computer access for the moment. However i always keep nandroids handy and tried restoring my last nandroid of slimkat 6.0. Upon doing so my gps was working again!

Now I'm wondering if there are any files i can pull off of my nandroid and place them in my most recent version? As in restore my nandroid to get the necessary files and put them on an sd card, nandroid back and place them accordingly?

I did a search of "location" on the root of my phone and it yielded 21 results and i am not sure which files i need. Any help would be much appreciated!
[Sprint Samsung Galaxy S III] rambleon84:
My GPS will not work in maps but does works in my tracks. No icon GPS in maps but works normal in my tracks.
[Sprint Samsung Galaxy S III] sevenpioverthree:
Let me rephrase, when i go to settings->location, it is turned off entirely, and when i try to move the slider to "on" it just slides back to "off" (it doesn't even stay on for even a fraction of a second)

Edit: I've confirmed it was just my own data causing this issue, a clean flash of slimkat had location working. But for reference would anyone happen to know which data file would cause this?
[Sprint Samsung Galaxy S III] jorv976:
Dirty Flashed 6.4 over 6.2 with No Problems.
[Sprint Samsung Galaxy S III] nimaim:
6.6 is out but no 6.6 for our device on the site to download just yet ...
[Sprint Samsung Galaxy S III] Perseus:
This past week there haven't been any Rom related commits on CM. So we could be on lower priority. Besides, Nick was swamped as well.
[Sprint Samsung Galaxy S III] nicklovell23:
d2lte is next in queue.
[Sprint Samsung Galaxy S III] nimaim:
Great, thanks guys! :good:
[Sprint Samsung Galaxy S III] amiblindyet:
6.6 be takin' forever to boot up.
[Sprint Samsung Galaxy S III] nostrings:
Did it boot up for you, yet?
[Sprint Samsung Galaxy S III] Perseus:
Is it this bad ? I have been flashing my unofficial builds so didn't flash this one.

I will try 6.6 now.
[Sprint Samsung Galaxy S III] phaseL:
I'd say it took about 10-15 minutes, but it got there eventually.

--------------

I searched and read, but didn't see anything. Apologies in advance for my oversight if this has been covered to death...

Is there an issue with screen casting through Chromecast? I keep getting a Google Play Services error.
[Sprint Samsung Galaxy S III] amiblindyet:
Yes, it boots. Just took a few minutes. Nothing unreasonable. Just thought it was worth mentioning.
[Sprint Samsung Galaxy S III] zhiwlin:
Any plans or is it even possible to port the ultra power saver mode similar to g5?
[Sprint Samsung Galaxy S III] nicklovell23:
Can someone using TWRP thats having slow boot times flash and test this build and shoot me an email with the results.

Email is: nicklovell23@gmail.com

rom download:http://d-h.st/L26
[Sprint Samsung Galaxy S III] Perseus:
Last night I expressely updated with a Dirty flash as well as Clean flash. On both occasions, the boot time has been normal. Of course the first time there is added lag as Dalvik Rebuilds the app cache.

If you never wiped Dalvik and Cache after flashing the rom, it will obviously take forever to boot.
[Sprint Samsung Galaxy S III] nostrings:
And if you're using ART instead of Dalvik, it will take much longer, still!

--

Edit: I made a clean install (ROM+lean kernel 9.8exp kernel ONLY!), over 30 minutes of waiting to get past the boot splash screen, I just yanked the battery and after a few minutes, put it back in and let it boot. It worked this time around.

Not sure what the problem was/is...
[Sprint Samsung Galaxy S III] mholloway:
Just curious if anyone tested.I will test it this week end if no one has.
[Sprint Samsung Galaxy S III] Perseus:
THOSE WITH ISSUE OF LONG BOOT TIMES -

I had been deeply investigating this issue for today and yesterday. I went through quiet a chore and laundry list of Scenarios. I formatted to different File System Combos, tried several versions of the Recoveries as well. I even formatted to F2FS even though I haven't converted the Rom Zip on my SD Card.

It turns out, in the end, that this could possibly be related to recovery. Also possibly related to DPI as mentioned by others.

Will you be kind to post What Recovery and which version have you got there ? Is it possible that you have Philz or CWM ?
[Sprint Samsung Galaxy S III] amiblindyet:
Philz.
[Sprint Samsung Galaxy S III] htb723:
Am I able to use the 4.4.4 gapps on the 4.4.2 version of the rom? I can't seem to find the gapps for 4.4.2
[Sprint Samsung Galaxy S III] zhiwlin:
Philz, has long boot time. In fact, kt kernel never boot up even with clean flash
[Sprint Samsung Galaxy S III] thearch1tect:
I'm running CWM and can confirm it takes forever to load when restarting