yashsingh1/xdaforums huggingface dataset:
[Verizon Samsung Galaxy S III] slvfox:
Searched but didn't see any reference. I tried flashing another 4.3 rom using TWRP and upon reboot it got stuck on the splash screen. Do you have to use CWM flashing this? Also using latest TWRP
[Verizon Samsung Galaxy S III] Dearborn1977:
Did you wipe data/factory reset first? Did you verify good download? If yes to both you should ask in the other ROM's forum for help. Twrp should work fine.
[Verizon Samsung Galaxy S III] slvfox:
Thanks for the reply. Yes, when flashing the other rom it required you to be on CWM. I want to flash this one but I don't want to switch from TWRP. Can you flash this rom with TWRP?
[Verizon Samsung Galaxy S III] Dearborn1977:
Yes absolutely. Twrp has always worked for me with Slim. About to flash 4.3b2
[Verizon Samsung Galaxy S III] samsgun357:
I renamed the gallery2.apk to .bak and pushed this apk to system fix permissions and reboot. FFC works now.

http://db.tt/uzoNu0qa

What you don't know could fill a book.
[Verizon Samsung Galaxy S III] TokedUp:
Hey man thanks for this camera apk! Not only in FFC working but this also has a working HDR mode and save to SD card! Thank u so much

Edit: this also has a built in photo editor and the gallery is much nicer. Thanks again!
[Verizon Samsung Galaxy S III] tvl76:
I'm kinda dumb about this.

Exactly how is this done?

I can't rename the file.
[Verizon Samsung Galaxy S III] ddurandSGS3:
not too great with this stuff either but you should be able to navigate to the file with a file explorer, then lon press to rename
[Verizon Samsung Galaxy S III] dbornack:
Does anyone have BT headaches? I've had BT issues since the 4.2.2 train started, and 4.3 isn't any different. It takes forever to connect to a bluetooth device (Jawbone Jambox). THings work fine for awhile when it eventually DOES connect, but after 5 or 6 hours I get a clicking sound that plays over my music.

Half the time I need to turn BT Off/On a few times, maybe unpair the device and go through the pairing process again, etc.

Everyone else that connects to my Jambox (various phones, iPhones, GS4 stock, etc.) connect right away, and have no issues.

These issues follow me to my car as well.

Would it be beneficial to upload a logcat of the process?
[Verizon Samsung Galaxy S III] amaury48:
Downloaded the latest weekly on phone and on pc, but not getting a match on the md5s
[Verizon Samsung Galaxy S III] SlimSnoopOS:
What md5 are you seeing? I've been on this since last night and this is the md5 of the zip I flashed:

efe085c121b16e8bd2e374144f1c7ed4
[Verizon Samsung Galaxy S III] Dearborn1977:
I think they post the SHA1 value on the Slimroms site, not md5. Android File Verifier from market can generate those. However on two downloads, I've gotten a SHA1 checksum of 34a7a57492198da474d9f0773c550f929665a57c, not the one posted on Slimroms.
[Verizon Samsung Galaxy S III] RayMcGrath:
yea yea! started with another clean install and then used this camera apk and BAM! it's all working \... nothing broke! Blue tooth is perfect too! No problems at all :good:

THANKS! :cool:
[Verizon Samsung Galaxy S III] flyestAC:
I've had problems with purchased apps on anything besides 245 or 320.
[Verizon Samsung Galaxy S III] SlimSnoopOS:
Do you mean in terms of using them or the act of purchasing them? I don't have many paid apps installed yet cuz I tend to keep a low app count when running alphas/betas of roms. My two icon packs and TiBu are working fine though.
[Verizon Samsung Galaxy S III] flyestAC:
Apps that I purchased didn't show up as purchased on some DPIs. I think I remember GMail having compatibility issues too. I would get a not compatible with your device error.
[Verizon Samsung Galaxy S III] SlimSnoopOS:
Gotcha, I'll keep an eye out but unfortunately my use case involves mostly free apps. So far, stuff is working but I like to give it the work test as well.

Anyone notice any difference in camera performance on 4.4.1? I don't take many pics so I can't tell much.
[Verizon Samsung Galaxy S III] kentedman:
Easiest way for me to change DPI is an app called "textdroider DPI". Its as simple as punching in the DPI and rebooting.

If you're having trouble with the play store, make sure you clear app data from the play store in the running apps list every time you change DPI. There's also an xposed module that's supposed to force all apps to show in the play store regardless of DPI setting, but I haven't had a need to try it yet.
[Verizon Samsung Galaxy S III] beepea206:
If you have an app with a build.prop editor like Rom Toolbox, you can easily do it too... just look for 'density'; there are drop downs for standard settings, like 280 and 320. After a quick reboot, you're golden.
[Verizon Samsung Galaxy S III] gadgetguy08:
Finally got in the car and used Blue Tooth. The BT crashed again after a period of time (minutes) twice -- I didn't get a LogCat. I found that it continued to play on the BT link until I clicked on the pop-up acknowledging the error. I will say that it was much easier to recover from than previously. Earlier versions require using a Task Manager to kill the Blue Tooth app and restart it. Now I can click the BT off and back on with the tile drop down.

I will attempt to get a logcat next time.
[Verizon Samsung Galaxy S III] indyssee:
Hopefully someone can give me some insight. I was having issues with my Sandisk 64 gb sdcard so I got a Transcend 64 gb class 10 card and formatted it to fat32.

I flashed 4.4 using the newest twrp and it failed saying unable to unzip. Tried redownloading and checking md5 and it matched but still failed.

I remember reading the CM and twrp would support exfat so I copied everything over to pc and reformatted to that since it was the cards default. This time no issues with flashing but then the os doesn't seem to read card because slim explorer couldn't see it and it just says mount sd card in settings/storage but never does anything. Anybody have any advice or experience with a similar situation? Thanks.
[Verizon Samsung Galaxy S III] SkinnyT:
Can I mirror my screen on this phone using this rom on my Samsung TV or is that a tw feature only?
[Verizon Samsung Galaxy S III] kude87:
Does 4.3 version 2.2 have the qrill commits added in? Looking for a stable, faster than tw rom with good signal.
[Verizon Samsung Galaxy S III] nicklovell23:
Link me the commits and I can check.
[Verizon Samsung Galaxy S III] kude87:
The app isn't letting me quote you, Nick. Getting an invalid thread id. Anyways, I'm not exactly sure where to find them, but here is a guess:

https://github.com/CyanogenMod/android_device_samsung_d2vzw/blob/cm-10.2/system.prop
[Verizon Samsung Galaxy S III] SlimSnoopOS:
Hey [MENTION=4408910]nicklovell23[/MENTION], do you guys have any input on this Qualcomm dalvik and bionic patch that seems to be receiving a bit of attention from users?
[Verizon Samsung Galaxy S III] sbattosai:
For some bizarre reasons, slim never supported exfat in 4.3.x roms. I am hoping they will in kit kat though...
[Verizon Samsung Galaxy S III] TokedUp:
I flashed it on PA beta and it seemed to install fine. I can't say I notice any difference but it didnt break anything either. Im hoping Nick, Invisiblek or Notta chime in on this subject.
[Verizon Samsung Galaxy S III] indyssee:
Well now its different issues that may be related to the actual SD card. Reformatted again to fat32 and flashed successfully using newest cwm. Once again os couldn't do anything with card. It did freak out a few times saying card unexpectedly removed and then tried to mount it a bunch of times with no success. But then again I'm back on Beans 20 and it works without issue. I haven't tried any other 4.4 ROM to see if it might be an issue with Slim, though. Anybody successfully using a 64gb class 10 SD card, in any format, with Slim?
[Verizon Samsung Galaxy S III] SlimSnoopOS:
Same here but just for SlimKat alpha. I probably would notice something if I took benchmarks pre and post flash but I'm not one for those. Maybe I'll try that tonight.
[Verizon Samsung Galaxy S III] dpeeps74:
This is driving me crazy. Tried a Google search but all I find is changelogs for slim or 3rd party apps. I changed a setting that changes my volume controls when in landscape and want to change it back to normal and have no idea where I changed the setting. I'm not certain but I think that after I changed that I can't get my phone to stay in vibrate/silent. Anyone have any idea?

Sent from my Slim GS3
[Verizon Samsung Galaxy S III] SlimSnoopOS:
Are you referring to SlimBean or SlimKat beta? I'm on SlimKat and I don't notice a landscape only setting.
[Verizon Samsung Galaxy S III] dpeeps74:
I'm still on bean, sorry.

Sent from my Slim GS3
[Verizon Samsung Galaxy S III] SlimSnoopOS:
Hmm, try looking in Advanced Options but I'm pretty sure what you need is in Settings/Navigation/Hardware Keys
[Verizon Samsung Galaxy S III] bigbear6708:
Just tossing it out that slimkat beta 1.5 is up on the site!!!!
[Verizon Samsung Galaxy S III] SlimSnoopOS:
Ooo yea, looks like new gapps are up too!

Btw lol I love the first line (newest) of the changelog.

Edit: thank you for building another beta release for us Nick! I, for one, am very grateful for your continued support!
[Verizon Samsung Galaxy S III] dpeeps74:
Thanks, found it in auto rotate settings. It's apparently not the cause of my issue so don't know if poweramp introduced a bug in an update or what. I'll just live with it for now. People at work will just have to deal with it. Apparently if I do the volume key to skip a track or anything it takes it off silent. Also tried setting it so volume only controls media and tried the lock volume controls. Oh well. Thanks again for replying.

Sent from my Slim GS3
[Verizon Samsung Galaxy S III] FastEddie422:
Just installed beta 1.5 and it seems to be working good so far, thanks. Am I just not finding the option to turn off the hardware key backlights or has it not been added yet to 4.4? Also, the option to add custom actions to the hardware keys?
[Verizon Samsung Galaxy S III] annoyingduck:
Mikey likey new build!

Nick, please tell me the samsung hardware key lockscreen options are going to return....
[Verizon Samsung Galaxy S III] deuce237bblock:
Just noticed SlimKat 4.4.2 beta 1.6 has been uploaded. http://slimroms.net/index.php/downloads/dlsearch/viewcategory/630-d2vzw
[Verizon Samsung Galaxy S III] SlimSnoopOS:
Hmm, downloading this too. I was five minutes away from flashing beta 1.5. Guess I'll compare the changelogs between the two betas.
[Verizon Samsung Galaxy S III] o0BlacknesS0o:
Hey guys... I've never ran slim... Does it have profiles?
[Verizon Samsung Galaxy S III] deuce237bblock:
I've never used profiles but I'm pretty sure SlimBean has it. I'm on SlimKat and I can't find profiles so I'm guessing no.
[Verizon Samsung Galaxy S III] o0BlacknesS0o:
Nevermind... Flashed it... No profiles... Bummer... everything else is great though... So smooth and it's actually the only 4.4+ rom that auto downloaded my apps from the play store after setup
[Verizon Samsung Galaxy S III] deuce237bblock:
Yeah, that actually annoys me. Did you flash beta 1.6? What gapps did you use?
[Verizon Samsung Galaxy S III] o0BlacknesS0o:
Clean flashed 1.6 and used the slim gapps
[Verizon Samsung Galaxy S III] deuce237bblock:
I used the 1.5 gapps. I haven't had any problems yet but I also remove a lot of stuff I don't use.
[Verizon Samsung Galaxy S III] kinnerful:
How do I change dpi in SlimKat 1.6 beta?
[Verizon Samsung Galaxy S III] flyestAC:
I had been holding off on running Slim because of some of the features that I have grown so used used to being left out of the the first alpha. Well I flashed 1.6 last night and I'm so happy to be back lol. So fast and clean. Easily the snappiest 4.4 I've run and I've tried most of not all. I disabled keys backlight using Keyboard Backlight Controller from the market. For the DPI I used Texdroider (thanks [MENTION=3783550]kentedman[/MENTION]). Still missing some of the options like TRDS, profiles, and some settings tweaks, but this is such a rock solid ROM I'm just gonna stick it out and wait for the goodies. I fell kind of bad I wasn't running the alphas already lol.

Thanks [MENTION=4408910]nicklovell23[/MENTION] and the Slim team for the best d2vzw ROM. Excited to watch this beast progress!

---------- Post added at 09:56 AM ---------- Previous post was at 09:45 AM ----------

Oh yeah one thing I noticed and I noticed this on another 4.4, when I go in the play store and tap on the search line to bring up the keyboard, two lines extend up vertically at each end of the search line. It's only there while I'm typing, then it goes away after I search. Doesn't hurt any functionality, just a cosmetic thing that wasnt there before.
[Verizon Samsung Galaxy S III] Relentless D:
You read back a few pages :D

You need to either do a manual build.prop edit or use an app like Textdroider for now.
[Verizon Samsung Galaxy S III] Rrrracer:
Can you guys on 1.5/1.6 please check tethering to see if it's working? It was borked in the initial release and I had to revert back to 4.3. Thanks!
[Verizon Samsung Galaxy S III] flyestAC:
I don't use tethering but I just tried for you and I couldn't get my hotspot to show up on my old Bionic. I enabled on my S3 and it showed I had it on but the Bionic didn't pick it up. Not sure if there are some other steps I missed because like I said I don't use it but that was my experience.
[Verizon Samsung Galaxy S III] Rrrracer:
Much appreciated. That's what it was doing before.
[Verizon Samsung Galaxy S III] beepea206:
Really? I've flashed 4 different KK roms and they've all auto-downloaded apps from the play store.
[Verizon Samsung Galaxy S III] jlokos:
On occasions, playstore has not auto-downloaded my apps. I have noted that under settings> backup and reset>backup account, there was no backup account and I couldn't add one because it was grayed out.
[Verizon Samsung Galaxy S III] beepea206:
Ya know what, that's true; I didn't think about it until now, but I noticed 'Restore' wasn't an option when I flashed Gummy. For some reason, the apps auto-downloaded (I left the backup box checked). Odd. Hell, with as much as I flash and go between roms, I'm surprised the Play Store can keep up with me...
[Verizon Samsung Galaxy S III] o0BlacknesS0o:
You could also used Xposed and the App Settings module.... it will give you control just like pa

---------- Post added at 05:01 PM ---------- Previous post was at 04:53 PM ----------

You've been luckier than me lol... This is the only one that worked for me... I've flashed cm11, hellfire, gummy, beanstalk, pa, bam
[Verizon Samsung Galaxy S III] bigbear6708:
So what features are still out? Hardware button re map?
[Verizon Samsung Galaxy S III] SlimSnoopOS:
Just about the same things in the first SlimKat beta release
[Verizon Samsung Galaxy S III] flyestAC:
Little bug in getting.... When I back out of browser I'm getting funky lines on the screen for a sec
[Verizon Samsung Galaxy S III] kinnerful:
Same here, with Firefox though.
[Verizon Samsung Galaxy S III] FastEddie422:
Edit: Ignore this. I must have been doing something wrong because it is working and now I can't delete this post.

Not sure if it's a bug, a missing feature, or an option I'm missing somewhere but double tap to zoom isn't working in browser and other in-app browsers. I was pretty sure slim bean had it but I was on PACman for a little while before switching back to slim for 4.4 so I am not be remembering correctly.
[Verizon Samsung Galaxy S III] beepea206:
You might be able to resolve that by disabling HW Overlay in developer settings. Flickering/black lines is a common issue in 4.4 that can be resolved by altering this line in the build.prop:

persist.hwc.mdpcomp.enable=false

I haven't tested on Slim, so it may not do anything, but it won't hurt anything to try.
[Verizon Samsung Galaxy S III] annoyingduck:
Man this 4.4.2 build is friggen amazing....

It's like getting a new phone! Running with art, and can't be any happier with the performance. Now the wait for themes, trds, and button remapping (including lockscreen)... Nice work as always, puts the official cm to shame!
[Verizon Samsung Galaxy S III] daturkel:
Can someone point me to the right KT version for 2.2 of slim? The 4.3 one I flashed gave me a bootloop and I had to reflash the rom to get back the slim kernel
[Verizon Samsung Galaxy S III] beepea206:
If that's the case, then you most likely want the KT version BEFORE 11/8/13. There was a huge update to the CM kernel on 11/8 and it affected all roms and kernels.

If your rom build is after 11/8, most kernels after 11/8 should work... if it is before 11/8, you'll need a kernel released before 11/8.
[Verizon Samsung Galaxy S III] dbornack:
Anyone running a new kernel for the 4.4 ASAP train?

---------- Post added at 06:34 PM ---------- Previous post was at 06:34 PM ----------
[Verizon Samsung Galaxy S III] SlimSnoopOS:
Yup, using KT747 12/03 right now cuz I can change my display temperature to "Cold" with the KTweaker app. I can't stand the stock colors. I had been using BMS on SlimBean and I'll return to it that temperature option is back in Advanced Options. Can't say I notice improvement but that's cuz I just like changing stuff for the fun of it.
[Verizon Samsung Galaxy S III] griz.droidx:
My apologies if this has already been asked. I've kept up with the thread but haven't been able to check things this week.

Does the recent slim 1.6 beta include the ability to remap hardware buttons. I miss back to kill. I've tried a couple versions including the latest and I must say things are moving along well. Thanks for that.

If anyone knows how or if it's possible in the build prop or elsewhere please let me know. If you know it's possible but can't remember the details don't worry. I can search for that on my own. I don't want to do that though if the function is already in slim.

Thanks everyone
[Verizon Samsung Galaxy S III] annoyingduck:
Not yet, but you can use dalvik + xposed + gravity box for the time being. You must use the new kk gravity box though..
[Verizon Samsung Galaxy S III] griz.droidx:
Thanks duck. I tried that in Spencer's build a while back but didn't want to use exposed. Thanks though. Does xposed affect battery or performance? I know it's good. But how good compared to baked in. Or are there no differences. I've read a lot of good things about xposed but not many details. I'll do some research. Thanks
[Verizon Samsung Galaxy S III] annoyingduck:
You won't notice any difference... Just be careful with some of the settings, they will conflict with what slim already has in.
[Verizon Samsung Galaxy S III] d1ez3:
Is there any way to get black sms before trds is released into the builds?
[Verizon Samsung Galaxy S III] TokedUp:
You can use the one in the Nexus 5 app forum. I'm using it now.
[Verizon Samsung Galaxy S III] annoyingduck:
Use 8sms

https://play.google.com/store/apps/details?id=com.thinkleft.eightyeightsms.mms

It's a modified aosp messaging app with a dark mode. It's great, and your settings will remain on ti restores.
[Verizon Samsung Galaxy S III] d1ez3:
Does anyone else have the issue where pressing the home key when the screen is off sends you to the home the launcher and the previous app you on?
[Verizon Samsung Galaxy S III] SlimSnoopOS:
Everyone does on SlimKat. It's annoying but I do see this as well.

Bug report Sunday for SlimKat build 1.6!

1) Screenshot previews are distorted although the actual screenshot is fine when viewed in Gallery apps.

2) The "Sound profile" tile on the Quick Settings page doesn't show the Vibrate icon. The icon displayed is "No Sound" however it does sometimes show the Vibrate icon in certain circumstances.

3) Home button to wake the phone takes you to homescreen when you were in an app.

4) Advanced Power menu doesn't show over the notification drawer. It appears hidden behind it until you pull up the drawer which makes notification bar screenshots difficult if you're into that sorta thing.

5) I'm finding it INCREDIBLY difficult to find bugs! Lol My other issues would be considered feature requests and that's not useful since they'll be re-added in time.

Happy Sunday folks!
[Verizon Samsung Galaxy S III] d1ez3:
Ah thanks, I should read the whole bug report..
[Verizon Samsung Galaxy S III] SlimSnoopOS:
Lol I hope you don't think I'm affiliated with the SlimRom team. I'm a regular user just like yourself. That's my personal bug report since using SlimKat. I've thrown a lot at this rom between Xposed and two modules, KT747 kernel, restored apps via Titanium, and just using stuff.
[Verizon Samsung Galaxy S III] griz.droidx:
I noticed the screenshot issue in oce as well. I'm guessing it's across most builds unless someone has fixed it recently.

Correction. I'm on oce 12-13 now from 12-08ish and slim 1.6. The screen shot issue is fixed.
[Verizon Samsung Galaxy S III] Rrrracer:
Also, WiFi tether doesn't work.
[Verizon Samsung Galaxy S III] FastEddie422:
I'm not sure if you'd consider it a bug but if I turn the screen on, pull down the notification shade on the lockscreen, then turn the screen off while the shade is still down, the shade will still be down whenever I turn the screen on next...even hours later. Previously, the shade would hide itself after turning the screen off. It might just be normal kitkat behavior because I haven't seen it before.

Other than that I am not seeing any other bugs that haven't been reported. With Xposed and Gravitybox I have hardware keys mapped and backlit buttons turned off. With KT I'm getting better battery life than I have in a long time. Thanks again!

Also, I feel like I should throw it out there for people who may be new to Xposed like me. Apparently Xposed does NOT work with ART yet and switching to ART while running Xposed might give you a boot loop.
[Verizon Samsung Galaxy S III] d1ez3:
How do you change the key mapping with kk gravity box? I see options to change the hardware keys for long press and double tap, but I don't see how to change for single clicks. Is that option there somewhere?
[Verizon Samsung Galaxy S III] FastEddie422:
I was referring to the long press and double tap actions. I usually change my long press back button to switch to the last used app but the options are missing from slimkat at the moment. I just looked and couldn't find anything about changing the default single key press either, sorry.
[Verizon Samsung Galaxy S III] d1ez3:
thanks, I'll just use the navigation bar for now. I need a power button remapped as a hardware key since my power button on the phone doesn't work for me anymore most of the time.
[Verizon Samsung Galaxy S III] gadgetguy08:
Slimkat build 1.7 is up!
[Verizon Samsung Galaxy S III] bigbear6708:
Is it time I plunge into slimkat? Every time i dl one.. I talk myself out of flash... Lol
[Verizon Samsung Galaxy S III] gadgetguy08:
Well, it is still in beta and has some rough edges and pieces missing, so it depends on what you can accept.
[Verizon Samsung Galaxy S III] deuce237bblock:
Also the volume rocker doesn't change volume while on lockscreen.
[Verizon Samsung Galaxy S III] annoyingduck:
New thread time....?
[Verizon Samsung Galaxy S III] SlimSnoopOS:
Does anyone else have a non-functional camera on SlimKat beta 1.7? I can effectively take one photo and it freezes. Clearing data and force stopping the camera causes it to give the "Can't connect to camera" message that should not be occurring on VRBMF1 firmware. This wasn't an issue on prior versions of SlimKat and I am using this on a fresh flash.
[Verizon Samsung Galaxy S III] gadgetguy08:
Yes. Seeing same thing occur on my phone on beta 1.7.

EDIT:

I just installed the latest (12/15) BMS kernel and rebooted and the camera is working OK now. Not sure if it is the new kernel or the reboot that helped.
[Verizon Samsung Galaxy S III] kentedman:
Anyone had any luck with wifi tether on 1.6 or 1.7?
[Verizon Samsung Galaxy S III] SlimSnoopOS:
Reboot alone does not help. Off a fresh flash of the rom and minimal gapps, its just not working. Probably a commit or three that were updated recently that caused this. I'm seeing on the CM threads they had the same issue as well. With 12/03 KT747 the camera has the same issue so GideonX must have reverted or fixed the camera issue in his 12/15 build if what you're saying is true.