yashsingh1/xdaforums huggingface dataset:
[Verizon Samsung Galaxy S III] SlimSnoopOS:
It's kinda hard to say in regards to SlimKat (4.4), its an alpha after all and is missing many features as detailed on the SlimBean website. That said, my biggest hurdle was getting past the "no root access" issue but as a few other users posted and confirmed (me as well) the latest KT747 kernel and LK 9.0 kernel both allow root access. I'm planning on going all in tonight and using my full load of apps including Xposed and I'll have some quality time tomorrow to use this so I can't say much until a full 24 hours at least.

Edit: without having tested calls and only using wifi (I live in a low signal area), I encourage you to flash this. Just don't be surprised that many of your favorite SlimBean 4.3 features are missing since that's intentional as an alpha.
[Verizon Samsung Galaxy S III] bigbear6708:
Thanks! I'm going to wait for your review (maybe.. Lol) I need my phone for work, etc!!
[Verizon Samsung Galaxy S III] SlimSnoopOS:
You're a better person than me lol Only reason I didn't have this flashed last night is cuz I fell asleep waiting on Nick to post back about the completed upload lmao
[Verizon Samsung Galaxy S III] bigbear6708:
Well, I might.. the web site has a hefty features list. I cannot assume much is missing!! Will I be able to dirty flash officials over this??? I'm over all the setting up!
[Verizon Samsung Galaxy S III] SlimSnoopOS:
If you're flashing SlimKat alpha (4.4) then there is A LOT that is not included yet. Trust me on that. I'm missing the custom shortcut for the Quick Tiles, sure it's obscure but I like setting that as my radio info. There's no Real Dark Slim toggle, display temperature, or DPI changes, for example.

If you're flashing SlimBean 4.3 then all the features are included. Its not suggested to dirty flash over SlimKat but that is entirely up to you. SlimBean (4.3) sure you can, but don't post bugs/logcats unless you did a clean flash.

Hey folks,

Just want to clarify on my earlier post: LK AOSP v9.0, KT747 12/3,

and

BMS 11/13 all grant root access on fresh flashes of SlimKat.
[Verizon Samsung Galaxy S III] kentedman:
Granted. But now that root is back, you can get alot of features back with xposed. Its still not full slim but its pretty dang sexy anyway.
[Verizon Samsung Galaxy S III] draexo:
can anyone confirm a working kernel for the 1.9 build??

Sent from my Lovely S3!! via Tap Talk
[Verizon Samsung Galaxy S III] SlimSnoopOS:
Agreed, I prefer to use Xposed for just a couple things though: Xhalo and Greenify. When it's ready, I'm betting SlimKat will be better than ever.

Flash a kernel dated BEFORE October 17. BMS 10/16 and LK 8.4 are two such kernels for SB 1.9. There were graphics driver updates in the kernel on Oct 19th so they require a rom built after that date.
[Verizon Samsung Galaxy S III] annoyingduck:
Oh my....

We love you Spence...
[Verizon Samsung Galaxy S III] draexo:
Downloading LK 8.4 now

Sent from my Lovely S3!! via Tap Talk
[Verizon Samsung Galaxy S III] liquidnails:
Hey guys, I'm having a issue with the camera force closing when I try to use it. Is this a issue everyone is experiencing or am I alone? Thanks in advance.
[Verizon Samsung Galaxy S III] draexo:
Which version you running? Rear or front camera?

Sent from my Lovely S3!! via Tap Talk

---------- Post added at 07:12 AM ---------- Previous post was at 06:59 AM ----------

1.9 Slim and LK 8.4 won't boot. Any ideas?

Sent from my Lovely S3!! via Tap Talk
[Verizon Samsung Galaxy S III] SlimSnoopOS:
Either try the previous version of LK, try BMS 10/16 (which I personally know works), or try another kernel from before that date.
[Verizon Samsung Galaxy S III] tvl76:
I prefer the stock kernel on 1.9, I failed to see any "improvement" with any of the customs (for me anyway)
[Verizon Samsung Galaxy S III] DjCalvin:
GPS gone haywire?

So On 2.2 stable, stock kernel.

For some reason my phone thinks I am in Buenos Aires. Im up in the northeast US.

never had this issue till going to 2.2 (was on 2.x stable prior) Both google maps and aviate.

Anyone have this issue?
[Verizon Samsung Galaxy S III] samsgun357:
I'm not seeing the 4.4 builds on goo???

Remember, its only weird if it doesn't work!
[Verizon Samsung Galaxy S III] SlimSnoopOS:
Have to copy/paste the URL from Nick's post (emphasis mine):
[Verizon Samsung Galaxy S III] samsgun357:
Awesome brutha, thank you!!

Remember, its only weird if it doesn't work!
[Verizon Samsung Galaxy S III] beepea206:
I'm on the latest TWRP and still received a binary error when I tried to flash the 4.4 build.
[Verizon Samsung Galaxy S III] SlimSnoopOS:
TWRP 2.6.3.1?
[Verizon Samsung Galaxy S III] beepea206:
Yessir. I've been running 4.4 roms since they came out (so I know about the binary error in TWRP) and flashed 2.6.3.1 the day it was available, because I prefer TWRP. I thought it was a tad odd that I'd get a binary error with the new TWRP.
[Verizon Samsung Galaxy S III] SlimSnoopOS:
Hmm, definitely weird. I've flashed this rom about eight times the last two days to test different things. You tried reflashing TWRP? If so, might as well temp flash CWM.
[Verizon Samsung Galaxy S III] beepea206:
Yea, I was thinking about temp flashing with CWM to see if I had the issue still, but I'm at work and was just testing the rom. I'll try it again tonight, because I'd love to see what it looks like!

BTW, are there new 4.4 slim gapps up? I don't see any, so I assume the PA GAPPS are ok?
[Verizon Samsung Galaxy S III] SlimSnoopOS:
Yes, there are SlimKat gapps on the site. You'll have to ask [MENTION=4408910]nicklovell23[/MENTION] about compatibility with other roms' gapps.
[Verizon Samsung Galaxy S III] kentedman:
The slim gapps are on their site. No dark slim yet. But, I'm running this Rom with the PA kanged gapps (with the updated dialer search) with no issues at all
[Verizon Samsung Galaxy S III] gadgetguy08:
Running 4.4 and had two instances today where Blue Tooth suddenly stopped for no apparent reason. Was running Beyond pod connected to my car's BT and got a message that BT Share failed. After restarting BT it reconnected and continued.

I have a Logcat if anyone is interested.
[Verizon Samsung Galaxy S III] beepea206:
Nice one... Got it flashed. I think K the binary issue was because I used the PA gapps.

Is there a way to adjust the screen dpi? It looks like it's higher than usual, but I don't see where it can be adjusted.
[Verizon Samsung Galaxy S III] beepea206:
Has anyone else lost root access? I've flashed and wiped a few times, but every time, I don't t have the access.
[Verizon Samsung Galaxy S III] SlimSnoopOS:
We all did. If you read back a bit (or search) you'll notice we had to use a custom kernel to get root access :laugh:
[Verizon Samsung Galaxy S III] countryfolk07:
You can look in the build.prop to see what it is. And if you want it different just change it and save it. Clear market data, then reboot. You'll have your new DPI. :)
[Verizon Samsung Galaxy S III] beepea206:
Haha seriously? That's the complete opposite of Gummy. Sorry, I totally missed that post, but I prefer kt, so I'll flash it. :)
[Verizon Samsung Galaxy S III] draexo:
Any chance for a build 2.3 that fixes the need to "Disable Hardware Overlays"?

Sent from my Lovely S3!! via Tap Talk
[Verizon Samsung Galaxy S III] SlimSnoopOS:
I have to ask, were you able to succesfully change your DPI? I'm using the older version of ES File Explorer, Simple Explorer, and even QuickOffice and none of these are writing to /System in any way on SlimKat alpha. I even copied the build.prop over to my downloads folder, changed the lcd density to 320, saved it, verified it was changed, then tried copying and even moving it over. I had to settle for increasing the font cuz the default DPI of 245 is WAY to small for my eyes.

haha I'm just happy there's a workaround, post back with your results. I'm sure Nick would appreciate it!

Aight so I'm posting back to say....SlimKat definitely is solid enough for a daily driver. I had no issues with calls, texts, or mobile data where I work at even when I went to lower levels of the building. I had to use a custom kernel to get root and after that I've been all set. I'm using about 60 apps, Xposed with 3 modules, and everything is working or as close to bugless with my apps as far as I can tell. No random reboots, graphical glitches, nor force closes with what I have installed. GPS seemed to work well although I did not test navigation. I only used GPS test to verify it turned on and Maps to see if it tracked me. I want to reiterate, this is not a review, and also that any feature you use in SlimBean most likely is not included yet in SlimKat alpha but that's very clearly stated on the SlimRoms homepage.

There are some bugs that are annoying but are consistent with an alpha release. One of the bugs I noticed is that pressing the home button when the screen times out causes the phone to back out to the homescreen regardless of the app you're in OR if you're already on the homescreen then it displays all of your homescreens (whether its 2 or 7). Another is that the power menu is hidden behind your notification drawer if you have that open before long pressing the power button. Things like this, in my opinion, are obvious bugs so I'm sure they'll be fixed in the next few releases. Overall, a solid experience and one that can only get better. Take my anecdotal experience however you want and if anyone has a different or similar experience then please do share :D
[Verizon Samsung Galaxy S III] tvl76:
I'm on 1.9 now. But I changed the animation scaling in the developer options and that did the trick for me on 2.0 and 2.2.

Window animation to off, the other two to. 25.

1.9 still the most stable, imo
[Verizon Samsung Galaxy S III] gadgetguy08:
I had the same issue and was finally able to modify build.prop with ES Explorer by opening Root Explorer and selecting Mount R/W of system. This is version 3.
[Verizon Samsung Galaxy S III] SlimSnoopOS:
No more squinting for me! lol 320 DPI is in effect :good:

Edit: if the above doesn't work, try updating ES File then trying it again.
[Verizon Samsung Galaxy S III] countryfolk07:
This is what i was going to suggest. Make sure you have a current file explorer and make sure you make the system folder r/w. Lol. I bought Solid Explorer, I love it's features, and it's not to heavy on resources. But I can't say anything about this ROM, I'm not on it. Slim was my first experience on the lower DPI. I loved it! Sadly though, I haven't much luck on Slim since like version 6 of 4.2. So I've been running Carbon. I always had location issues, network issues, or GPS issues. :(
[Verizon Samsung Galaxy S III] bigbear6708:
The 4.4 worked surprisingly well for me. Almost as (or more stable) than bld 2.2.. it's just missing a few key features I have grown use to.. That's why I am back on 4.3. If u are thinking about it.. Give it a go!
[Verizon Samsung Galaxy S III] xdreaper15:
Any workaround for changing icons in GEL? In on the high squinty DPI and I want good looking icons :/ mine seem a little off at this high of a DPI.
[Verizon Samsung Galaxy S III] nicklovell23:
Ok guys Another build is up if you guys want to go at it. Camera should work please test and report back on BT and anything else you find. Root needs enabled in developer options just like in 4.3. To enable developer options go to about phone and tap build# 8million times. Other than that enjoy. "Rom http://d-h.st/fWB Gapps http://slimroms.net/index.php/downloads/dlsearch/viewcategory/978-addons4-4/downloads
[Verizon Samsung Galaxy S III] bigbear6708:
Hey Nick.. If I start flashing 4.4 now... Can I maintain a dirty flash with each update.. Including once it goes stable?
[Verizon Samsung Galaxy S III] beepea206:
So I'll try the new build, but with the first 4.4 build, I flashed 3 different kernels and lost root every time. Anyone else encounter that issue?

Edit... Actually, that's the build I have... 12/5. Can't seem to keep root access.
[Verizon Samsung Galaxy S III] dpeeps74:
I'm pretty sure that the new build isn't there yet.

Sent from my Slim GS3
[Verizon Samsung Galaxy S III] nicklovell23:
I will never recommend dirty flashing. Its like wearing dirty underwear.
[Verizon Samsung Galaxy S III] nicklovell23:
Did u enable developer options and enable root?
[Verizon Samsung Galaxy S III] nicklovell23:
Switching to dev-host will put links up when they r done.
[Verizon Samsung Galaxy S III] flyestAC:
Anyone else getting a 404 trying to download the 12/5 build via the link Nick posted
[Verizon Samsung Galaxy S III] nicklovell23:
Goo.I'm is being a pia will get new links in a bit.
[Verizon Samsung Galaxy S III] flyestAC:
Thanks! Appreciate your work.
[Verizon Samsung Galaxy S III] nicklovell23:
Ok here it is http://d-h.st/fWB
[Verizon Samsung Galaxy S III] Rrrracer:
Alright I can't resist any longer... taking this for a test drive :)
[Verizon Samsung Galaxy S III] beepea206:
Well s**t... In all my years with cm, I didn't know you could enable root access in dev options. I'll give that a try. Other than root access, it'll be my daily driver, for sure. Super smooth and fast.
[Verizon Samsung Galaxy S III] Rrrracer:
So far so good. It's surprisingly fast, smooth and stable.

Make sure you have the latest recovery and firmware installed; I was on old firmware and got an Error 7 until I updated it.

I can't seem to get tethering to work; the switch turns on and it shows enabled but none of my other devices or laptop see it. Tried both with and without security. Any suggestions?

I need it to run my business (unlimited data FTW lol) so if it's borked I'll have to restore my 1.9 nandroid, which would be unfortunate because so far I am loving SlimKat. Thanks Nick!
[Verizon Samsung Galaxy S III] SlimSnoopOS:
I can't get it to work either although this is the first time I've ever tried using it. My ipod and MBP don't see my S3 after setting it up.

Hey all, I see in Settings/Display we have an option for Cast screen but what do you cast the screen to? I have a Google Chromecast that definitely works with Netflix and youtube and I know Google blocked device streaming in a recent update for the Chromecast.
[Verizon Samsung Galaxy S III] Rrrracer:
Good to know. It's unfortunately a deal breaker for me but I know they'll get it fixed. Otherwise I'm not seeing a whole lot that would prevent this from being a daily driver for most. Restoring my nandroid but really looking forward to subsequent releases!

Cheers to Nick and the amazing devs behind Slim Rom.
[Verizon Samsung Galaxy S III] trips555:
I know the majority had eagerly moved on to kitkat, but I'm so happy with 4.3.1, I just need some help! Hangouts runs semi-normally but just crashes on some sending or receiving of messages. It's VERY annoying and the ONLY problem I've come across! Can anyone lend a hand? Here's a logcat if it helps!
[Verizon Samsung Galaxy S III] flyestAC:
Can someone share the default wallpaper from Slim 4.4? In back on 1.9 but that wallpaper is super nice.
[Verizon Samsung Galaxy S III] Rrrracer:
What build are you on? I had no problems whatsoever with Hangouts on 1.9 but didn't try 2.0+
[Verizon Samsung Galaxy S III] trips555:
on the newest... I thought about going back, but I wanted to be sure before I did a whole reflash. (First time with this rom so I wasn't sure if it worked on any version)
[Verizon Samsung Galaxy S III] Rrrracer:
Its a great ROM. I would recommend flashing 1.9 if you're wanting the most stable 4.3 Slim.
[Verizon Samsung Galaxy S III] trips555:
Got a link? Or upload? Can't seem to find it?
[Verizon Samsung Galaxy S III] Rrrracer:
Here ya go buddy:

http://slimroms.net/index.php/downloads/dlsearch/viewcategory/630-d2vzw
[Verizon Samsung Galaxy S III] Setco:
Having issues getting 4.4 to load. Gets to the bootloader screen and then reboots to the recovery..I am using the latest CWM recovery. Any suggestions?? Would appreciate any help! Thanks in advance my friends..
[Verizon Samsung Galaxy S III] Rrrracer:
Did you get any errors while flashing?
[Verizon Samsung Galaxy S III] Setco:
No errors everything appeared to go smooth
[Verizon Samsung Galaxy S III] Rrrracer:
Weirdness. The only other thing I can think of is to make sure you're running the latest firmware; mine wouldn't boot until I upgraded, but it gave me an Error 7 on installation on the latest CWM.
[Verizon Samsung Galaxy S III] Setco:
How can I make sure i'm running the latest firmware (don't mean to be a noob). And how would I get the latest?
[Verizon Samsung Galaxy S III] griz.droidx:
Go into about phone and look at baseband. The latest is i535VRBMF1. Where to find it... I'd try goo.im. or android file host. I'm sure you can find it linked somewhere in development, not original development, here on xda. I know several people have it shared.

Supposed to be an edit...

http://invisiblek.org/sch-i535/firmware/

I hope invisiblek doesn't mind me linking. I can't figure out how to link to his original post with tapatalk.
[Verizon Samsung Galaxy S III] Setco:
I'm running the latest firmware. Can't figure this one out and I really want to try the new 4.4. I am doing a clean flash. However, I am afraid if I do a formatting of the system I will lose important data I needed either on my internal and or external. So I am not doing a formatting of the system. This may be the problem but can someone tell me if I am safe in doing this (and wont lose any stored data) sorry, I feel like an idiot....but I don't want to take a chance. Any help would really be appreciated.
[Verizon Samsung Galaxy S III] SlimSnoopOS:
[MENTION=4408910]nicklovell23[/MENTION]

Yooooooo......

Bluetooth stays off when I turn it off while still connected to my headset on SlimKat beta 1.2. No more of that auto-toggling back and forth bug. Just got off an hour long call with no hiccups as expected, all on BT. I have to give the SlimKat team and all the AOSP devs big ups for that. Idk if it was like this on SlimBean 2.x cuz I had a few other bugs on their that caused me to drop back down to 1.9.

Formatting /System

does not

touch your internal or external storage. It is essentially wiping the /System partition of your phone and a new one is installed when you flash SlimBean (or any rom). Some roms even wipe /System as part of the install process. If you notice when you do nandroid restores in CWM or TWRP, one of the first lines is "Wiping /System..." for the old rom then it eventually says "restoring /System..." for the backup you're restoring. You've been doing this all along with no impact on your storage. Wipe /system, my friend and see if this helps in any way!

I'm on desktop so I'll link it for ya.
[Verizon Samsung Galaxy S III] beepea206:
Working great with kt... It seems like my modem turns off on its own and I have to reboot 2 times to get it back in... It's random and I think it's related to my use of llama.
[Verizon Samsung Galaxy S III] Rrrracer:
You could always offload that important stuff to your pc, start fresh and then load it back on. If you have really important stuff on your device you should probably be in the habit of backing it up anyway. Worst case, restore your nandroid backup...which you copied over to your PC, right? :)
[Verizon Samsung Galaxy S III] Setco:
Got SlimKat up and running... Incredibly smooth...although some features are missing ..I'm really loving it. Can anyone tell me how to install KTweeker...I have the apk but it won't install. Also, is there any way to adjust the dpi? Appreciate any help. A major thanks to the developer...all your efforts are appreciated. Awesome job:good

---------- Post added at 12:59 AM ---------- Previous post was at 12:54 AM ----------

It was a lousy d/l of the ROM. I did a second d/l and flashed it again and everything went smooth. Thanks for the help!
[Verizon Samsung Galaxy S III] SlimSnoopOS:
Did you flash KT747's latest kernel? It installed for me when I flashed it.

To change the DPI, you'll have to modify it the old fashioned way....via a build.prop edit. Download your favorite file Explorer (ES File, Root Explorer, etc) and do the following:

Edit: You'll be changing the lcd-density which is currently defaulted to 245. Stock for S3 is 320. Your eyes will thank you :cyclops:
[Verizon Samsung Galaxy S III] Setco:
Thanks SlimSnoop... you have made things extremely easy! good: highfive
[Verizon Samsung Galaxy S III] beepea206:
Your eyes and your fingers, since smaller DPI makes for harder target sensing with things like nav bar.

DPI on every phone I've owned since the Droid 1 has been 320... any idea why the default is 245?
[Verizon Samsung Galaxy S III] kentedman:
To each their own... I prefer smaller dpi. With xposed framework and per app settings I can run gmail and mail app with dual panes so folders are always visible.

I quite enjoy having alot more screen real estate on lower dpi's
[Verizon Samsung Galaxy S III] Rrrracer:
Probably because they were going for more screen real estate. The extra room makes a noticeable difference on gmail, text messages, etc. Slim has defaulted to 245 as long as I can remember.

I ran it that way for a while but it was no good for when I docked the phone in the car and used it on trips. Plus my eyes are getting old and crotchety just like the rest of me...

I changed mine to 280 and found that seems to be a happy medium and after using it, 320 looks just huge, but to each their own... choice is a good thing!
[Verizon Samsung Galaxy S III] Setco:
I have to say that typically, I do like my font/dpi small... I agree, it gives you more screen real estate. But lately my eyes have gotten to where I am really having to squint to see anything... so I am happy there are options for all!
[Verizon Samsung Galaxy S III] beepea206:
You and I are on the same page. 280 with 'normal' size font and I'm happy as a clam. I started using 280 when I got my LG Spectrum, which was bigger than the Droids I had previously... the S3 is about the same size, so it's perfect for me.
[Verizon Samsung Galaxy S III] griz.droidx:
That's exactily what I do. 245 is tiny for my bad and now aging eyes. But between 268 and 300 are great for me depending on what I'm doing. Everyone needs too try different settings to see what they like. A wise slim Dev once said try it for a week and you'll never notice it. If I could make the status bar bigger with the 245 that's what I'd keep mine at.

---------- Post added at 05:44 PM ---------- Previous post was at 05:42 PM ----------

Are most of you on the kt kernel? Anyone using dkp or bms?
[Verizon Samsung Galaxy S III] beepea206:
KT here. I like both and may flash the new BMS tonight to try it out; KT seemed to work better with more roms, but there's a BMS update, so it's time to give it a whirl.

There aren't many differences between the two, other than BMS defaults to undervolting (which I like) and KT has a proprietary app, but I use Trickster Mod, so I don't really need it.
[Verizon Samsung Galaxy S III] SlimSnoopOS:
Aight y'all convinced me to drop down my DPI to 290 :good: lol I'll use it over the next couple days and see how I like it. I haven't ever messed with DPI settings aside from changing from 245 to 320 on each fresh flash of SlimBean.
[Verizon Samsung Galaxy S III] tat2me2:
Don't know how this happened but I just did a clean install, wiped everything just like it says to flashed latest 4.3 Slim Bean Rom then Gapps everything booted up fine but when I tried to delete the Gallery2.apk it said phone was not rooted. I also tried Rom Toolbox just for the heck of it and it too failed to detect root - I'm restoring from backup now. any ideas as to what went wrong? I'd like to check this Rom out -

Thanks - tat
[Verizon Samsung Galaxy S III] m_s_ifland:
Damn! I thought I looked there :eek:

Thank you.

---------- Post added at 05:23 PM ---------- Previous post was at 05:20 PM ----------

No need to restore, just go into Settings>Developer Options and enable root.
[Verizon Samsung Galaxy S III] icon123:
Is rear facing cam working on beta 2?
[Verizon Samsung Galaxy S III] m_s_ifland:
Rear facing - Yes

Front facing - No(at least on mine)
[Verizon Samsung Galaxy S III] tat2me2:
Thanks for the info, it's much appreciated.
[Verizon Samsung Galaxy S III] RayMcGrath:
Great! All seems well except front camera.
[Verizon Samsung Galaxy S III] tat2me2:
I'm not seeing "Developer Options"where is it ?

NEVER MIND - I FOUND IT :)