yashsingh1/xdaforums huggingface dataset:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] javamaniac:
Yea the bootloader shows UCDLK3… I also have uconnect in my RAM and the 4.3 build 2.2 broke the Bluetooth connection to my messages. I guess I will check out 4.4 and see how it is.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] tallsilver:
4.4 has been broken the whole time for the Uconnect.....this latest version seems to be working so far. Fingers crossed and good luck.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Swiftks:
Nevermimd. :)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] nsmith4:
I just flashed the new 4.4 beta and everything seems to be working except the camera lockscreen widget. When I try to enter the camera from the lockscreen widget the camera app freezes and I have to reboot my phone. The camera app on it's own seems to work fine though. Does this work for anyone else?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] sbs8331:
It doesn't work, and I eventually get the message that the camera is not responding. I haven't had to reboot. I press the back button a few times or the power button quickly, and I'm able to exit. I have CyanFox backed up on my phone. I may try that one to see if the problem is there as well.

Update: Must be something to do with SlimKat in particular. The Lockscreen camera works okay with CyanFox.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Chr0nicDreamz:
Anyone else notice the advanced power menu is no longer there? No more reboot, recovery, download mode options.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] NJD316:
Its under "Security" now, you have to reactivate it.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Chr0nicDreamz:
Much appreciated.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] tbird57:
I can't seem to find where you can change the lock screen wallpaper...did they not implement it on 4.4?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] sbs8331:
Not generally available in Kat. I installed Xposed Installer / Xblast Tools to get that feature.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] lambgx02:
Anyone tried cSipSimple, Zoiper or the built-in SIP client on slimkat 4.4.2 beta 2.4? It seems to be selecting the wrong microphone across the board (rear, instead of call mic).

I checked through /etc/audio_policy.conf and there's a dedicated voip_tx definition, set to use AUDIO_DEVICE_IN_COMMUNICATION, but I'm not sure where that itself is defined.

I've tried changing the device list to AUDIO_DEVICE_IN_BUILTIN_MIC, but it didn't seem to help. Is this working for anyone else?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] sbs8331:
I haven't used my camera much until today, but I'm now having an issue with 4.4.2 beta 2.4. After the first camera shot, the camera app freezes. If I close it and try to go back in, it's either still blank, or I get the connection message referenced above.

Update: It appears that this issue occurs only with the OpenAir app (used for my time and expenses). That app integrates with the camera to allow pictures of receipts to be taken and uploaded to an expense report. It worked with 4.3 but gets hung when taking more than one picture with 4.4 (and freezes the camera app afterwards as well). The issues does not occur when using just the camera app apart from OpenAir. It must be an issue with OpenAir and KitKat. No, in the famous words of the esteemed Emily Litella:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ronedogg:
How do I disable the capacitive key backlights? I had it disabled and I had to re install. After I can't find the damn option, and I feel stupid for having to ask..... Thanks I'm on 4.3.1 stable 2.2
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] 12packabs:
I think in Settings > Display you can make the timeout 0 seconds which might do the trick.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ronedogg:
Victory!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] zeusakatkm:
Is there a way to enable killing an app by long pressing the back button?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] lambgx02:
RC1 (4.4.2 v2.5) is in the build queue for our devices and should be available soon; it implements hardware button remapping to enable long-press back-to-kill.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Threezees:
Build broke. Damn the bad luck.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] 12packabs:
Xposed with GravityBox.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] powerserge1:
or settings > navigation > hardware keys then enable kill app with long press of back key
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] lambgx02:
Sorry to bump, but has anyone tried using a VOIP client (cSipSimple, the native SIP dialer, Skype, Zoiper, etc) on 4.4.2, native Slim kernel?

On my device, it never uses the handset microphone, but rather the rear while on a call (unless on bluetooth/headset, which works fine).

It works fine for regular GSM phone calls; I saw some scattered reports on this around the web, but some claims of it being a hardware bug in some devices. But, I was hoping to rule out it being a d2att/kitkat/cm11 issue before I gave up.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] matrixzone:
RC1 is out for our device, go get it!!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] tallsilver:
So far so good!!

Thanks Slim Team
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] lambgx02:
Can anyone check if their compass is bound to the wrong gyro axis? Launch a compass app and see if the compass always points the right direction as you pitch and rotate the phone.

---------- Post added at 05:03 PM ---------- Previous post was at 04:08 PM ----------

I've confirmed that the compass is broken in 2.5 (at least for me), assisted by the wrong gyro; all is well in 2.4.

Looking through the changelogs, this is suspicious:

2014-01-18 | d2: use sprint final board revision to fix up sensor [Shareef Ali]

It was a commit to the CM11 kernel:

http://review.cyanogenmod.org/#/c/57674/2/arch/arm/mach-msm/board-m2_vzw.c

Does anyone know how to check board revision number? And, can anyone else test the compass in 2.5?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] JaY_III:
Seeing the same thing as you on my end.

Just heading out now and was planning to rest the GPS to see if that's fixed. But I am now having my doubts.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] lambgx02:
Actually, that's good; I suspect we've found the culprit. :) This patch made it into various other kernels I've tried (lite, kt747) as well, and caused the same issue on 4.4.2-2.4. I'm pulling the repo and will attempt to build with this patch reverted (assuming my little i7 960 doesn't melt down first). :fingers-crossed:

Thanks a lot for the confirmation!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] lambgx02:
More confirmation of the theory - in 4.4.2-2.5, running with kt747 01/18 solves the compass issue. This kernel does not have the Shareef's sensor commit.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] tallsilver:
Also BT is dropping and not reconnecting with uconnect. 2.4 worked. 2.5 does work with BMS 12/09 kernel!!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] JaY_III:
I am getting the same results you are seeing.

01/ 18 works and the change at 01/24 causes the compass fail.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] LeeC:
camera still crashed:crying:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] k29er:
Just my view but I have tried most kitkat ROMs for the s3 plus stock kitkat for my nexus 7 and find lots of problems and bad battery life. I have gone back to slimbean 4.3-2.2 on the s3 and n7 to regain speed,super stability and excellent battery life. It just works so well.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] lambgx02:
So, looks like in merging board-m2_(vzw|att|spr) together, they changed the compass gyro orientation around. This seems to fix it:

diff --git a/arch/arm/mach-msm/board-m2.c b/arch/arm/mach-msm/board-m2.c
index e9ed246..14ef618 100644
--- a/arch/arm/mach-msm/board-m2.c
+++ b/arch/arm/mach-msm/board-m2.c
@@ -2093,9 +2093,9 @@ static struct platform_device opt_gp2a = {
/* compass */
static struct ext_slave_platform_data inv_mpu_ak8963_data = {
.bus = EXT_SLAVE_BUS_PRIMARY,
- .orientation = {-1, 0, 0,
- 0, 1, 0,
- 0, 0, -1},
+ .orientation = {0, 1, 0,
+ -1, 1, 0,
+ 0, 0, 1},
};

struct mpu_platform_data mpu6050_data_spr = {

I built a kernel based on KT747-JB HEAD with this change, and the compass is working properly again. If anyone wants to test it, let me know.

Otherwise, should I submit a patch to the CM guys? Or is anyone else here already connected with them? :)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] JaY_III:
If you need a tester, send me a link.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] tallsilver:
I agree. Keep a current nandroid of SlimHalo to go back to. Everything looks like I want and just works. On it now......will try next one.

Thanks Dev for your hard work.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Wond3r:
After the latest update, my text notification sounds no longer work. Anyone else experience this?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Threezees:
Mine are working. Tried a dirty flash and a clean flash, no problems here. Try clearing media storage and reboot.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] LeeC:
Tried almost all the 4.4 ROMs and everyone has the camera problem:( Went back to slim 2.2 and everything just works:good:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Jep56:
What camera problem? I have not had a problem with any Slim Rom 4.4 camera!!:fingers-crossed:

---------- Post added at 07:23 AM ---------- Previous post was at 07:19 AM ----------

I flashed the 01/18 kernel and still have the compass problem
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] LeeC:
Try to change camera settings, picture size, front/back mode, picture/video mode etc, and the camera will be frozen then FC. Without a reboot you cannot connect to the camera again.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] JaY_III:
KT kernel was patched last night with the fix.

Tested it thus morning on the drive to work. GPS and compass both work now.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Wond3r:
That was a good suggestion, thank you. It did not work though :confused:

Maybe I'll try another dirty flash or something
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] dima470:
I can't help but notice that everything on this ROM feels smaller. Can I make everything bigger? I'm sure you guys know what I mean.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] sbs8331:
Grab "resolution change / Density" from play store and use it to set the density back to standard 320.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] nsmith4:
Download a build prop editor from the playstore (there are a bunch). Then find the line ro.sf.lcd_density and change the value to 320 (which is the normal density on most roms).Then reboot.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] dima470:
Thanks guys. Also I'm noticing that my 64GB exFat SDcard isn't supported. Is there a fix for this? I know KToonsez new kernel fixes this. Are there any fixes for the stock kernel? Thanks In advance.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] LeeC:
I might be wrong but I don't think the kernel fixed the camera issue.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] nsmith4:
I'm not on slimkat now but the 4.4 rom I'm on also had these Camera issues. To solve it I uninstalled the gallery and camera apk from my rom. Then I grabbed the Gallery2.apk from Slimbean 4.3 and installed it. Now the camera seems to be working fine. Of coarse make a backup of the apks before uninstalling.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Threezees:
Correct, the fix he (or she) is speaking of involves axis problems, not the camera. However, I haven't had any camera issues since 2.2, but I always clean flash Slim (even though it doesn't state it's required). Maybe I'm one of the lucky ones?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] LeeC:
The camera also requires some lib files .so files. That would be cool if just install the 4.3 camera on 4.4. I'll probably try it out when have time.

Thanks for the tips.

I always do a clean flash as well. Out of box, the camera worked fine and most of time it's just working. The froze problem does not always happen but if you try to change settings, picture size, front/back, video/picture mode etc it will crash at some point.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] dima470:
I'm not to sure if this is a problem with just this ROM or AOSP in general, but when on YouTube and watching a video in landscape, if I tap the screen and the status bar appears, the video studders like crazy. Any fix for this?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] amf66:
Still having some obnoxious camera lockups on the latest weekly (2.5). I hope they find the issue that's causing this on all recent d2 ROMs soon. :rolleyes:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Threezees:
Try Snap camera. No lockups, better than stock.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Conekiller2:
Just tried slimkat. When I go to the play store it says that candycrush is not compatible with my device
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Snow.Goose:
Is there anyway to set the volume up and volume down to not change with screen orientation?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ronedogg:
I thought I lost my mind hahahahah.

+1 if someone can answer this!

Driving me nuts on my tab and phone
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Conekiller2:
New release 2.6 is up
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] tallsilver:
2.6 running very smooth. Still has BT re-connect problem with Uconnect in my truck. Had to use my standby kernel, BMS 12/09......but everything else I use seems to be good.

Thanks Slim team!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] sailzfast:
Could you please post a link to this kernel?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] tallsilver:
It's in the BMS thread...........http://goo.gl/5sk6Jh

Have to dig to find it but the above should take you to the download.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] amf66:
Let's hope they're right about this.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] sailzfast:
Huh. Getting install error with that version. Thanks tho.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] tallsilver:
Make sure it's the one dated 12/09......works for me with all the 4.4 ROMs I've tried so far????
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] fr3d0x:
Rom is working good now,no more camera problems..
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Brokeddid It:
This is the 4.3.1 SlimBean thread not 4.4 SlimKat
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] sbs8331:
Actually it's both and has been for quite some time.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] xmetalfan99:
I can't find the 4.4.2 gapps on slims site. Anyone have direct links?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] sbs8331:
Under Downloads => Misc => Addons 4.4 (beta): Slimroms 4.4 Addons
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] brGabriel:
Does anyone else think 4.4.2 and 4.3.1 SlimRoms need separate threads?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] lqdcat:
I think the title needs changed. 4.3 is unsupported now.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Conekiller2:
Battery life with leankernel has been super and no hickups at all.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] sbs8331:
Am I reading that wrong, or has your device been on for just over two hours and with only six percent battery life left? That doesn't appear to be super to me, though I figure there's an explanation.

The Rom works well for me as well. I'll test drive other KitKat Roms for a day or two but, just like the prodigal son, always seem to make my way back to this one.

A new thread is probably a good idea. The Slim developers don't seem to focus on this forum, and, not being a developer, I'd be wary about starting a new thread. I wonder if one of the Slim guys could rename this one or start one for SlimKat. It might get some more attention from the casual observer who may not realize that this thread has focused largely on SlimKat (vs. Slimbean) for some time now.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Conekiller2:
Phone has been of charge for 28 hours with slightly over 2 hrs screen on time. Averaging just below 1.0 percent in sleep and about 3.3 percent on
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jasvncnt1:


Your reading it correctly but the phone has also been up for little over a full 24 hours
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ronedogg:
Lord 2 hours and 1 day up time. I'm getting 3 days and 4 hours screen time. And I thought I wasn't doing that well.

KT 747 kernel. About to flash 4.4 rc2.

---------- Post added at 10:36 PM ---------- Previous post was at 10:09 PM ----------

I'm getting installed failed. I recently updated my bootloader and modem. Could this be the issue?

I downloaded twice and checked md5.

I'm using twrp

---------- Post added at 11:18 PM ---------- Previous post was at 10:36 PM ----------

U don't happen to know where they moved it to in 4.4? **** why do they keep moving **** around.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Conekiller2:
Stock battery?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ronedogg:
Yup. I've seen 5 hours screen on time. And have hear of 6 to 7
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Conekiller2:
Never had that kind of battery life. Most was about 4hrs with about 14 hrs total time and that was on 4.3 rom
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Snow.Goose:
Bump. Would really like to get it solved. Really annoying because some apps force orientation but the volume keys won't change with it
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ronedogg:
After flashing rc2 I decided to go back. Its missing too many key features I need.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] lambgx02:
Could try the Xposed framework here:

http://repo.xposed.info/module/de.robv.android.xposed.installer

.. and use the Swap Volume Keys module. Might work. Great framework to have installed even if it doesn't.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Snow.Goose:
Tried it out, but it didn't work. I appreciate the suggestion though. Other than this, the rom is pretty much perfect haha.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] peach007:
I just switched to this after trying every other ROM and I love it too. Going to stay on it for a while longer
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] hwy28spur:
Which Kernel for SlimKat 4.4.2 RC2

Finally made the jump from SlimBean 4.3.1 stable 2.2 to SlimKat 4.4.2 RC2.

I have read some comments concerning better performance with either the KT747 or BMS Kernel. Just wondering about some thoughts of which would be the better one to use with SlimKat 4.4.2 RC2 on AT&T Galaxy S III. Advantages and Disadvantages.

Thanks
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] akyboy:
Hi

Have rc2,all good except volumes, too low I think

I have stock kernel,.

Wonder if there is a way to adjust volumes little higher, even if I have to install some new kernel?

Thanks
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] 12packabs:
Both are very good. I'm running the latest BMS with excellent results and it is my preferred kernel.

Asking for advantages and disadvantages is subjective as everyone's phone is different.

Read their OPs and changelogs and then try them both to see which works best for your usage patterns on your phone.

---------- Post added at 09:13 PM ---------- Previous post was at 09:11 PM ----------

Plenty of mods to boost sound here on XDA. You could also flash a kernel like BMS which supports Faux Sound.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] sailzfast:
Hey...is Slim 4.4.2 based on Linux 3.4.y or 3.0.y?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] JamFan05:
3.4
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] paluinfusion:
IS there custom DPI settings in 4.4 ? Default 240 is too small for me. thanx in advance.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] sbs8331:
It's how Slim is delivered. Per post #648: "Go into system settings, then choose interface, follow that up with LCD density and follow the steps there. 320 is the default for the gs3." What I've done is to grab "resolution change / Density" from play store and use it to set the density back to standard 320. I believe I saw where the developers plan to incorporate an easy density setting into a future release. I haven't understood the lower density default, maybe a differentiating factor, but the reliability of this Rom has made the minor workaround worthwhile.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] paluinfusion:
I dont see any option related to DPI in Interface. Do I get that only after that play store app ? Anyway, downloaded that app and changed to 300, rebooting
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] sbs8331:
I guess I should have looked more closely. My bad. That setting was for 4.2/4.3, and I don't see it in 4.4 (though it may be there). I had installed this app prior to SlimKat, so I haven't used the setting since. Give the app a try. It's a snap. It's titled "resolution change / Density" in the play store. Upon installation, you'll see it in your list of apps as "Density Changer". Just execute it, press "Accept", set the density to 320, click the check mark at the bottom, and click "Reboot". Apologies for the confusion.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Swiftks:
Just open build.prop @ /system and change ro.sf.lcd_density to 320, save & reboot.

Clear app data for play store & Google services framework, and reboot again. Grant acess to everything upon reboot.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ronedogg:
Maybe someone here can help me. I'm trying to switch back from super su to the built in superuser.

I installed supersu to update the binary as I've done 100 times on other ROMs on my nexus 7. Then I went in supersu clicked change super user app. Rebooted.

Now built superuser works. But I get no prompts or toasts . and in the superuser log there is nothing.

Anyone know what I'm talking about?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] unknownyello:
I've done the same thing and got the same results as you. Not knowing if some of the apps work correctly or not without any logging or notifications, I just ended up installing supersu.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] 12packabs:
The binary is installed to the system partition. Try wiping system, then reinstalling the ROM and gapps. I think that will do it.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ronedogg:
Hey another person from Halifax. I live there too.

Thanks for the tip, was trying to figure out a way to fix this without reinstalling totally. This should do the trick!

Cheers
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Danny 0311:
I've never used a "Slim" rom. Can someone give me a quick rundown on the differences between Slim and Quantum? Thanks.:)