yashsingh1/xdaforums huggingface dataset:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] flroots:
I've started to experience FC of the Dialer whenever I click on the clock icon in lower left corner that's used to view call history. I've tried reboots, clearing cache, clearing call log data, uninstalling/reinstalling, etc, but so far nothing helps. I'm running the latest stable 9 version and latest gapps. Any suggestions much appreciated.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] sjamie:
Hmm... no problems here! Try also clearing Dalvik cache.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] flroots:
Thanks. I did clean both caches with no effect.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] sjamie:
In that case, since I have not encountered that problem and no one else has reported it, you may need to do a full wipe and reflash ROM.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mp3deviant721:
Did you try it on a clean install, with none of your user apps installed?

GS³: SlimKat + leanKernel Edition™

ギミチョコ！！
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] flroots:
Thanks. I just a full clean flash and it's now behaving. Wonder what could have caused it? It didn't start out misbehaving.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mp3deviant721:
It can happen. Just out of the blue like that. If a weird or sudden bug pops up after its been working for a while like that, remember to try a clean flash first. A lot of the time it can fix the issue.

GS³: SlimKat + leanKernel Edition™

ギミチョコ！！
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] sjamie:
Did you install any new apps recently? If so, one of them may have caused the problem.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] flroots:
Yes, probably several.

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

Thanks. I did a clean instal after wiping cache, Dalvik, system, and data and then used TB to install each app one by one. It takes several hours that way. Is there a faster, more efficient way?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] sjamie:
In TB, tap MENU then tap BATCH ACTIONS. Explore the possibilities! :)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mp3deviant721:
This works great if you have the Pro edition which allows for auto app install meaning it doesn't ask you to confirm the install of every app.

GS³: SlimKat + leanKernel Edition™

ギミチョコ！！
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] sjamie:
Yes and it's SO worth it!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] flroots:
Thanks everyone. Yes, I've used that feature; guess I'll try it next time
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] diakonos:
Anyone else having issues with the screen not turning itself off after the specified timeout? I know some apps keep the screen on but this is at the home screen...not in an app. Seems to be happening off and on for me. Dirty flash of 9.0. Thought I'd ask first before considering clean flash.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mp3deviant721:
Works fine for me. Try the clean flash. Remember, when in doubt, try a clean flash...

GS³: SlimKat + leanKernel Edition™

ギミチョコ！！
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] sjamie:
I agree!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] diakonos:
I went into Settings > Display, changed to 15 seconds and it works fine. Changed it back to a minute, again, works fine. I'll see it it repeats. I'm wondering if some other app is "active" somehow, not the visible active app, but somehow keeping the screen alive. I play "Classic Words Free" which I know keeps the screen on. If I'm in the app and get a text notification, view the text (maybe even reply) then exit the messaging app back to the home screen, would CWF still be considered "active"? I didn't exit the CWF app back to home screen but instead went straight to messaging from the notification. I've often seen when selecting a floating notification, going to the app of the notification, then pressing "back" button will often take me back to the app I was in when the notification arrived. Maybe some weird scenario like that is keeping the screen alive.

I have to watch it because it can drain my battery pretty good with the screen never shutting off after I place the phone back on my belt holder with the screen facing in.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Invalid1021:
Do you have Better Battery Stats (available here on xda)? Have you looked under wake locks?

Would have put this in the Q&A, but the q is here.. Sorry...
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Perseus:
Oh So polite nudge to the *Track*. (Hint Hint). ;) All this talk is good. Let's not allow ourselves go OT.:)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Perseus:
"We are currently experiencing technical difficulties with our infrastructure, due to which we cannot verify anything from our sites since the date of 22th February 2015. Please do not flash any builds downloaded until further notice.

We are working hard to resolve this issue, and are extremely sorry for the inconvenience."

Josue Rivera
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] shortstuffpb:
I have that issue, too. I think that they probably function on the lockscreen in the total opposite way that my brain does. What makes it a real problem is that I can't unlock the phone or decrease the volume until it stops ringing.

Beyond that, I am having issues with settings not sticking or behaving in the way that they should. I get notifications from apps where I set them for no notifications. I get tones for ones that I set for no sound. The lockscreen rotates in spite of the fact that it's set not to. I get FCs for Hangouts even though I have it disabled.

I did do a clean flash using the latest stable build. I'm a long way from being a noob. I just wanted to point out that 99.9% of users not experiencing an issue translates into 1 in every 1000 who does...
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Perseus:
Apps are known to ignore their own Settings. Facebook is a Prime Example. Nothing Anyone can do about that except the App Dev.Hangouts is deeply embedded in Play Services, so no wonder there. If you have it disabled/frozen, wipe dalvik. As to Lock Screen, Set it to Portrait only. Then see if it rotates.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] sjamie:
Is it possible to lower the volume of GMaps voice navigation while on a phone call? It is a bit loud to me. Touchwiz lowered the volume perfectly.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Ryou_Concord:
This also worked for me, and I also have the NJ1 baseband. I dont' know how you figured this out, but it DID fix my long-standing GPS issue. Oddly enough, it does take a bit longer for my GPS to get a good lock, which has been troublesome when driving through Detroit on some of the more unfamiliar roads. :eek:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jason2678:
Glad it helped. This issue took a while to figure out., I've had to repeat this procedure once since posting this.

I have an app called GPS Status intalled. It seems to get a fix a lot faster and more reliably than other apps that use GPS. I normally leave location off, but when I need it, I get a fix with GPS Status before Maps or whatever app needs it; it seems to greatly speed up the process of Maps getting a GPS fix for navigation.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] weedy2887:
Everything past 8.0 has had this slow lock thing going. My phone locks in 5 to 10 seconds on 8.0, 30+ on anything after that.

Also the compass is useless, but that seems to be a CM bug that's getting ignored over there.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jason2678:
Ditto on the compass thing, but I flashed something last week that had a working compass. It was either the official SlimLP or Cyanide L, can't remember. I'm not quite ready to use LP as a daily driver on this phone, but there does appear to be hope for a working compass again.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] heathroi:
You don't have to update the firmware just flash a TW rom go through the *#197328640# menu steps then reflash the Aosp rom and Gapps, and GPS will be good.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jason2678:
I've since realized that. I originally thought being on MJB and flashing a newer ROM had something to do with how GPS got borked, but it has happened to me again since then while on NJ1 firmware. I see now updating the firmware wasn't part of the fix, just something I happened to do before I stumbled onto the real fix.

Anyone know why flashing AOSP ROMs messes up GPS from time to time?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] heathroi:
probably because that rebuild menu is a script that a tw rom will run when it updates and aosp doesn't have it, would be my wild stab in the dark.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mp3deviant721:
If I remember correctly, it has something to do with NVRAM... TW has the ability to reset it as an AOSP ROM on a device like the S3 does not...

GS³: SlimKat + leanKernel Edition™

ギミチョコ！！
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Perseus:
Not a Script. Its a piece of Code in the TW Dialer. But yeah. For all purpose, it is I guess.

For the expedient Reason, the code for this isn't GPL. Its propitiatory so AOSP can never use it.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] adroidgalaxy:
Hey everyone, so I'm noticing some people having GPS issues, mostly related to issues just locking to them? (Which I know how to fix)

Now I'm running an older rom and during navigation my phone hard reboots. Is anyone running this rom experiencing this issue?

Also looks like 9 is the latest build but is that from July of 2014 or did the date just not get updated on op? :eek: haha

Thanks everyone? :thumbup:

Sent from my Carbon-i747 running 4.4.4 with custom mods
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mp3deviant721:
Build 9 has a build date of Dec. 21 according to my build.prop. Looks like OP hasn't been updated to match current. But build 9 works great (has some minor quirks that you can work around though), I'd recommend that if you are looking to run SlimKat.

GS³: SlimKat + leanKernel Edition™

ギミチョコ！！
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Perseus:
Thanks guys. OP Updated.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] eric512:
Need to do the GPS fix by flashing to a stock rom as previously posted.

I did a nandroid backup first.

Now i want to flash to stock. I have NE4 base and stable 9 running.

Is this ROM ok ? http://xdaforums.com/galaxy-s3-att/general/ucufne4-to-ucufnj1-update-t2941792
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jason2678:
It would be better if you used this one. This is an NE4 based rom.

You don't need to do steps 1 or 2 in the linked thread; in fact, since I assume you're already on NE4 bootloader make sure you don't do step 1 or you'll brick. Just grab one of the roms from step 3, flash it, and do the nvram rebuild.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Perseus:
Try [*gps fix] alternate gps fix]
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] hellenicboy:
google wallet

Is tap and pay working with this version? Google wallet is installed and set up but nothing happens when i use it at the store. Does anyone have any luck?

Thanks
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] cnergy_14:
a lot of bugs....

google app, camera, browser, rom manager is not working anymore.. how can I fix this??
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] sjamie:
Never mind...
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] machhho:
Can anyone please guide me on how to install this Rom coming from stock 4.1.1 ( UCDLK3 ) .

thanks in advance
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jason2678:
I think you'll need an updated modem to have working data with this rom. Is taking OTA updates to get your phone more up to date an option for you? That would be a nice safe way to get the firmware up to date before proceeding.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] machhho:
thanks for replying , but here in lebanon no ota updates further than 4.1.1 firmware which I have ,
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] d00m178:
Hello

Can't install SuperSU and get root rights with this ROM.

Flashed with full wipe all partitions..

Please advice.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] sjamie:
This ROM is rooted by default. You must turn on root access in developer options.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] d00m178:
thank you, it works )

would you advice about once more thing - when I open camera and then choosing video and after that again switching to photo mode - camera hung.

and only reboot can fix it.. it is really annoying.

Also it would be good to know how to make all fonts a bit bigger )
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mp3deviant721:
Camera issue is a known issue. Only way around it is to reboot. You can also try a different kernel, may or may not help with camera issues.

As for the small fonts, you'll have to change the DPI via the build.prop file. The default for this ROM is 245, but the default for TW and most other AOSP style ROMs are 320... You can do this either through a file explorer or an app that makes the DPI change for you.

GS³: SlimKat + leanKernel Edition™

ギミチョコ！！
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] sjamie:
I've switched to using Camera ZOOM FX and it works perfectly on this ROM.

I used Texdroider to change the DPI to 345 which looks great to me.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] d00m178:
I switched to this KK ROM after a long time being on the several LP ROM from here.

The main reason of this switching is the camera issue in LP - it doesn't work. And I also check Camera ZOOM FX and this app works not good - time to time it hangs and I need to reboot phone.

So i decided to go to more stable ROM and choose this ROM.

But again I have troubles with camera )) it is strange but Camera ZOOM FX works worse then on LP .

I tried Google Camera and it is hang after couple of switches between photo and video..
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] horga_83:
Try this:

https://play.google.com/store/apps/details?id=com.billgbennett.camerafix&hl=en
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] wrenhal:
I use Open Camera on all the roms I flash. Works great in this one. I haven't tried any lp roms yet though.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mp3deviant721:
I found a possible solution to the switching problem. Install Camcorder (https://play.google.com/store/apps/details?id=com.bryanowens.Camcorder). This just gives you a shortcut to the camcorder so you don't need to switch back and forth causing a no connection error. I'm still testing it out, but I have successfully switched back and forth dozens of times so far with out an issue.

GS³: SlimKat + leanKernel Edition™

ギミチョコ！！
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] hellenicboy:
I guess no-one knows.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] unibombz:
Hello,

I am still running SlimKat 7.0 Official on my SGS3 (d2LTE) I have recently purchased a new car that seems to use BT 4.4 protocol. My old car had no issues with BT and my device on SlimKat Official 7 (4.4.4) now when I pair my device it pairs, but every 10-20 seconds it says "unfortunately bluetooth share has stopped" and then resyncs and does the process over and over again.

I saw this link >> http://www.yoonhuh.com/blog/a-fix-for-the-bluetooth-share-has-stopped-error/

but that is only a temp fix for the issue. I was curious if there was any "fix" for this, maybe a patch.zip for the issue I can install with CWM?

If anyone could assist me with this that would be wonderful. Thank you.

I was thinking about upgrading to version 9.0, however I don't have the detailed instructions for updating the bootloader etc as I am on MUMUEND3 Baseband (It has been a while since I have flashed a new bootloader on the phone) -- Also I have read there is a few other issues with 9.0 (GPS and LTE) that don't work...

not sure if this would be a proper fix for the issue either ....

http://www.modaco.com/topic/368306-rom444all-slimkat-90-unofficial-29122014/page-52

http://d-h.st/i0C
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mp3deviant721:
I wouldn't recommend that fix, it's for a different device...

To update the bootloader I believe the best method is to Odin to what ever version you want that's newer than what you currently have. I think there isn't a flashable zip that you can use to update the bootloader on the i747... I'm not 100% sure though as I have a T999 and I know you can update the bootloader via flashable zip.

GS³: SlimKat + leanKernel Edition™

ギミチョコ！！
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] unibombz:
Yah, there might be a flashable zip for bootloader, surprised there isn't a patch fix for this bluetooth issue. Version 7 runs really well, just this new issue I've encountered with it that was hoping there was a quick flashable zip for.... maybe someone else knows some more regarding this issue :-/
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] dhack21:
I haven't tried this ROM but tap to pay is a known issue on CM 11 which I assume this ROM is based on.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] JaylanPHNX:
Essentially what you say is correct. Just one pedantic correction: the ROM is based on AOSP, but it does use device trees from CM (drivers, kernel stuff). It's only a technical difference, but some people get worked up about that sort of thing. I don't, but I figured I'd say something before someone who did was rude about it.

From my SlimTab Pro 8.4
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] dhack21:
Thanks for the clarification!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Perseus:
KK Version has been improved on prior detail. I had only tried once since I hate Google Wallet. You are welcome to try and let me know the feedback.

+1 There's a Geeky explaination to it. Short Answer its not pure CM.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] unibombz:
And the bluetooth issue remains unknown ?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jason2678:
I had zero problems with bluetooth, LTE, or GPS on stable 9.0. The only thing I know of that wouldn't work was the compass.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mp3deviant721:
AOSP ROMs have always had issues with BT not working properly with cars... Its a hit or miss kinda thing. I've heard not allowing phone book access may help in some cases...

GS³: SlimKat + leanKernel Edition™

ギミチョコ！！
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] hellenicboy:
Thank you. At least it is not something I was doing wrong.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] unibombz:
OK so coming from version 7 to version 9, can you just flash and go, or does it need a bootloader update, and if so which?

Maybe going to try version 9 and see if it fixes the BT issue, and doesn't give new issues (I hope)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mp3deviant721:
You can without a bootloader upgrade. Just as long as your bootloader is JB (4.1.2) or higher. I'm not familiar with the AT&T bootloaders, but you should be able to figure that out.

GS³: SlimKat + leanKernel Edition™

ギミチョコ！！
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] neavissa:
Hi,

I just installed this ROM and I really like it. The only issue I have is, that the taskbar on top is too small! How can I make the symbols on top bigger?!

thanks,

G
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] JaylanPHNX:
Slim uses a lower DPI. You can increase it by either editing the build.prop or using an app like textdroider_dpi from the Play Store. I can't remember what the default DPI for the S3 is, but a search will probably find that.

It's baconnn!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] dhack21:
I want to say stock dpi is 240 on the SGS3.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] neavissa:
Thanks for the reply guys. I tried it with the app you suggested, didn't work. I also tried it manually, didn't work either... I did this:

"in /system/ find build.prop

open in text editor

find this

ro.sf.lcd_density = ''

and change the digits to any of u like"

I did that and made sure I saved the file before closing. Did not work. Maybe having that app installed first screwed things up?! I have to run now, but what I am going to do later is, flash the ROM again and then try the manual method first...

thanks,

G
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] JaylanPHNX:
Dumb question, but did you reboot after? Also check and make sure root is working properly. I think 320 is Samsung default.

From my SlimTab Pro 8.4
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] neavissa:
There are no dumb questions, only dumb people. People like me, ha ha. You hit the nail on the head. I just checked and my phone is not rooted. What a dumba$$ I am! I never get that?! I thought that a phone has to be rooted in order or you to install a custom ROM?! Anyhow, let me find out how to root the Galaxy 3...

thanks,

G

---------- Post added at 11:04 PM ---------- Previous post was at 10:15 PM ----------

Update: it is working now. Problem was - device was not rooted.

Thanks everyone,

G
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] JaylanPHNX:
Technically, the phone doesn't need to be rooted so long as you can get a custom recovery installed. Slim comes with root turned off, but you can enable it under developer options in settings. You can also just flash the SuperSU zip.

It's baconnn!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Alexandre-P:
Yep, I confirm what you said: the default DPI on the stock ROM is 320.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Rhetorical:
restoring slimkat settings

I had to factory reset my phone and am currently restoring evthing via titanium. I need to know where slim ROM settings might be saved for recovery. looking to restore setting like recent apps panel and quick settings to the way they were before automatically but don't know where the data has been stored. Anyone able to help?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] sjamie:
Anyone getting complaints from callers about it being hard to hear you on this ROM especially over Bluetooth?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] neavissa:
I didn't know that. A bit late, but thanks for pointing that out!!!

Copy that!

thanks,

G
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] sjamie:
I have dialpad tones activated in call settings but no tones are heard during phone calls (e.g. entering conference call pins, selecting options with automated answering machines, etc.). Is this a known bug or do I need to activate another setting?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Perseus:
Need to check Volume Settings too.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] sjamie:
Ahh... that was the problem. I always keep my phone on vibrate. All other ROMs I've tried still emit the dialpad tones when the phone is set to vibrate. On SlimKat, setting the phone to vibrate also mutes the dialpad tones. Argh!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] sjamie:
Is there an option to add the brightness slider to the notification dropdown?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] loosemoose613:
Has anyone else had an issue with the aspect ratio in the front facing camera getting stretched vertically when using Snapchat?

It seems like Snapchat can't access a 16:9 setting on the FFC, so it uses 4:3 and stretches it to fill the whole screen. Looking in the settings for the camera app and some third party ones, I can't change any of them to 16:9 for the FFC either.

The rear facing camera works fine in Snapchat, and I can set it to 16:9 on other camera apps as well.

I've heard about others having this problem on on Slimkat on other devices, and even other ROMs. Apparently some other ROMs fixed the issue but it's still present in build 9 on d2att/d2lte. :(
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] wrenhal:
Don't know about how it was fixed but it's fixed in the cm12 lollipop builds.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Perseus:
You can add it to QS Tiles. Nothing Like Stock unless you add Power Widgets or something like that.