I am starting this thread so all issues related to SlimKat Rom can be documented in one single place. Please post your Questions & Answers in here instead of in the SlimKat Rom Thread, lets try and keep that thread clean.
SlimKat ROM Thread: http://forum.xda-developers.com/showthread.php?t=2511512
All Credit goes to the developers, Please support them for continued development
I will try my best to keep the thread updated and have questions and solutions posted in the first three posts of this Thread:
How to Install SlimKat ROM
Assuming you have already rooted, unlocked boot loader and installed custom recovery. If not there are multitude guides to do so, search in the forum.
Step 1:
Download the following:
Current SlimKat ROM: http://slimroms.net/index.php/downloads/dlsearch/viewcategory/979-hammerhead
Note SlimKat Rom is in beta currently
Current SlimGapps: http://slimroms.net/index.php/downloads/dlsearch/viewcategory/978-addons4-4/downloads/dlsearch
Note Slim Gapps are also in Beta, You can choose to download the full Slimgapps or the minimalgapps thats your choice. You can also download the photosphere addon.
Current SuperSu: http://forum.xda-developers.com/showthread.php?t=1538053
Step 2:
Place the downloaded file onto your nexus 5 using the provided cable, alternatively you can also download the files directly onto your phone using the browser.
Reboot into Recovery
Wipe data/factory reset (required)
Wipe Cache Partition (required)
I also always do the following (optional)
In mounts/ Storage
Format /system (optional)
Format /data (optional)
Format/cache (optional)
These are not necessary but I have made it a habit to do so.
Once you have performed the required resets, select Flash Zip file and flash in the following sequence
Flash SlimKat Rom
Flash SlimGapps
Flash SlimPhotoSphere (optional) Note: Does cause audio lag in recorded video with some kernels also videos are darker after photosphere flash. See Q&A section
Flash Kernel ( optional: only if you want to use a custom kernel)
Flash SuperSu ( I prefer SuperSu, SuperUser does not work properly for Me)
Reboot
Now your good to go and setup your phone.
Step 3: (optional)
~ Note for ART I follow this procedure:
After Flashing, once the phone starts I skip through the setup screen
Go to Settings-> About-> tap on build 7 times to enable developer options
Go to Settings-> Developer Options -> Select Runtime --> Art
Reboot and let it finish what its doing takes 10-15 mins.
Once done setup your phone how you like.
Reserved : Guide To SlimKat Features
Features And Guide
Once I have time I will break down all the slim settings and what they do
Features Not Included
PIE - Can be installed using Xposed Framework
HALO - Can be installed using Xposed Framework
NOTE: Xposed Framework does not play nice with ART, You will need to stick with Dalvik to use Xposed.
Feature Request
I will update this as users request features but please dont request features that can be added via addons such as xposed. There is no point adding those features to the ROM, those who want them can always install via Xposed
Keyboard Automatically Switching to Numeric Keypad when a field requires numbers only
Questions and Answers
Frequently Asked Question
http://slimroms.net/index.php/faq
These Are for SlimKat 4.4.2 beta 1.95 + Slim_AIO_gapps_4.4.2 beta1.x
These will be updated/removed as SlimKat updates
DPI/ Screen Issues
[Q] What are the default DPI's
Stock Kitkat = 480
Stock SlimKat = 361
Lowest DPI working for me = 370
[Q] Water in the Google Maps app is distorted, streaked or all over the place when zoomed out
Its a DPI issue, this is how i resolved it:
Download: Rom Toolbox lite ( Free) from PlayStore
Run app -> Swipe left to switch tab to performance --> click build.prop Editor button
on this new screen-> swipe right to bring out menu on the left side of the screen
First option is LCD density Click that-->change Value to whatever you want --> click ok and reboot
once Rebooted do the following :
Settings-> Apps-> Maps-->clear data, also clear Cache--> Force Close
Open Maps and confirm everything is working.
Some users have been able to get the maps to work properly at 361 DPI, but the lowest value at which it will work for me is 370. Default Stock Kitkat DPI is 480. Default Stock SlimKat DPI is 361
[Q] Everything is too small on default SlimKat, how can i fix that
two solutions:
go into settings-->display-->font-->change font size to make it bigger
change DPI:
Download: Rom Toolbox lite ( Free) from PlayStore
Run app -> Swipe left to switch tab to performance --> click build.prop Editor button
on this new screen-> swipe right to bring out menu on the left side of the screen
First option is LCD density Click that-->change Value to whatever you want --> click ok and reboot
Default Stock Kitkat DPI is 480, stock SlimKat DPI is 361, 400 ~ 420 DPI works best for me
Recovery
[Q] TWRP asking for a password, even though user never setup a password
When TWRP asks for a password, hit cancel.
Then go to Wipe and Factory Reset.
If that doesn't work, then restart your recovery.
If that still doesn't work then try reflashing TWRP again.
Camera
[Q] What is True View in the Camera App
True view is a camera feature to show the whole field of view of the camera.
By default the field of view is stretched and cut on the sides to fit fullscreen.
http://slimroms.net/index.php/faq/slimbean/323-what-is-true-view
[Q] Why is the Camer app Missing HDR+
HDR+ and Photosphere are closed-source. AKA no way to be built from source and must be distributed as an add-on.
Flash photosphere camera if you want HDR+.
http://forum.xda-developers.com/showpost.php?p=48832042&postcount=27
Note: PhotoSphere Addon currently adds a audio lag in recorded videos and recorded Videos are much darker, Read Q&A below about audio lag when photosphere is installed, link for photosphere is in the first post ( Slim gapps/addons)
[Q] Audio Lag in recorded video after Installing Slim PhotoSphere
Flash a different kernel, that will fix the issue
confirmed fixed with trinity.
in Recovery, without wiping:
Flash ROM
Flash Gapps
Flash PhotoSphere
Flash Kernel of choice
Flash SuperSu
Reboot
NOTE: Videos are much darker when Photosphere addon has been installed
Misc
[Q] How do I access the chamber of secrets on SlimKat
http://forum.xda-developers.com/showpost.php?p=48830608&postcount=25
[Q] Where are the QuickRecord recordings stored, are they cleared at boot and are they overwritten
/data/data/com.android.systemui/files/
It's never cleared from a reboot, but yes, rewritten each time you record.
http://forum.xda-developers.com/showpost.php?p=48832011&postcount=2577
[Q] Where is the clear all in the recent apps list
Clear all is not there as it is not needed, the list just shows the recently ran apps and provides the means of switching between apps quickly. Android will kill apps when needed there is no need to kill apps
[Q] I have no Mobile Network ( not data but no coverage at all)
This applies to only those who have no mobile network i.e they do not have a signal at all on their device and it does not say no service.
You somehow wiped the radio firmware, That needs to be restored.
http://forum.xda-developers.com/showthread.php?t=2514095
[Q] What is ART and what does it do
If you really need to know what ART is then you should not be using ART.
ART stands for Android Run Time, it is an experimental run time which is being developed by google to replace the current dalvik run time. Once released users would be able to get better performance and better battery life.
Currently, as ART is in experimental stage ( I would say Alpha, not even beta) the benefits of switching to ART are minimal. Not all apps are compatible with ART and most users will not see any performance or battery life improvements.
Thats why google buried it deep into the settings. Use at your own discretion. I suggest staying with Dalvik run time till further progress has been made on ART.
Un-Answered Questions
reserved
Regarding the last Q: Modem and EFS restoration is explained here: http://forum.xda-developers.com/showthread.php?t=2514095
Sent from my Nexus 5 using Tapatalk
lyrois said:
Regarding the last Q: Modem and EFS restoration is explained here: http://forum.xda-developers.com/showthread.php?t=2514095
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Thanks, updated the Q&A
One last question...screen recording how do I get that again...?
Sent from my Nexus 5 using Tapatalk
Galaxysm said:
One last question...screen recording how do I get that again...?
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
I'm not sure how to get that, I think you have to connect the device to the computer and use something in the SDK to be able to record screen, I could be wrong. Try searching for it. If I find a solution I'll let you know.
Sent from my Nexus 5 using Tapatalk
just a suggestion what do you think to move this thread to here
http://forum.xda-developers.com/custom-roms
would be more centralized and maybe more ppl would see the q&a thread
kufikugel said:
just a suggestion what do you think to move this thread to here
http://forum.xda-developers.com/custom-roms
would be more centralized and maybe more ppl would see the q&a thread
Click to expand...
Click to collapse
Yes, i think that would be better. My Apologize for starting the thread in Q&A section. Could a Moderator please move the thread to the custom rom Q&A section or if someone knows how to move it let me know and ill move it.
Thanks
Nice work.
maybe add LMT to the "Features Not Included: PIE" section
shawnbon206 said:
Nice work.
maybe add LMT to the "Features Not Included: PIE" section
Click to expand...
Click to collapse
Thanks.
I am not sure if and when PIE is implemented if it would include LMT with it therefore i left it out. I believe the xposed framework PIE does have LMT support.
Hope there are enough people here to help me out. I've been using Slim ROMs for a couple years on G-Nex and now Nexus 5. On the last couple releases I've been having issues with Google Maps not getting a GPS fix, or when it does get a fix it's off by nearly a mile. GPS Data, Waze, Gas Buddy, etc. all work fine. After spending nearly a day re-flashing the ROM, app, clearing data, etc., I finally tried another ROM (Purity) and discovered that Google Maps gets a fix in less than 10 seconds and is within 20' accuracy. I used the latest Slim Gapps on Slim 1.95 and the CM Gapps on the Purity ROM. Has anyone had similar problems?
From my Nexus 5
AquilaDroid said:
Hope there are enough people here to help me out. I've been using Slim ROMs for a couple years on G-Nex and now Nexus 5. On the last couple releases I've been having issues with Google Maps not getting a GPS fix, or when it does get a fix it's off by nearly a mile. GPS Data, Waze, Gas Buddy, etc. all work fine. After spending nearly a day re-flashing the ROM, app, clearing data, etc., I finally tried another ROM (Purity) and discovered that Google Maps gets a fix in less than 10 seconds and is within 20' accuracy. I used the latest Slim Gapps on Slim 1.95 and the CM Gapps on the Purity ROM. Has anyone had similar problems?
From my Nexus 5
Click to expand...
Click to collapse
I just reflashed slimkat on my phone, took less then 5 seconds for it to get a GPS lock. Check the following:
Settings-> locations -> mode
Make sure high accuracy is selected
Also are you using a custom kernel ?
Flash sequence for ROMs is
Slimkat ROM
Slimgapps
Kernel ( if using custom kernel)
Supersu ( supersu always comes last)
Reboot.
Sent from my Nexus 5 using Tapatalk
Anyone have any issues with the stock Slim Explorer app. I've never really used it before as I've always been an ES Explorer user but want to switch having the auto toggle TRDS modes. The app loads up but as soon as I scroll the screen the app closes and I get a "Slim Explorer has stopped" message. I've seen it in the past a handful of times I went to change DPI with it before installing ES. I did a complete clean install(ie. manually wiped everything and re-downloaded and re-setup all my apps instead of restoring them with Titanium), sha matches, so I can't think of anything else that could be the issue. Maybe it doesn't agree with Super SU???
Yep, did all that except for the SuperSU bit. I did use SuperSU on the Purity install though but haven't had any problems with the built in Superuser before. I'll nandroid back to the Slim ROM to give it a try. It was with the stock kernel.
From my Nexus 5
AndrasLOHF said:
Anyone have any issues with the stock Slim Explorer app. I've never really used it before as I've always been an ES Explorer user but want to switch having the auto toggle TRDS modes. The app loads up but as soon as I scroll the screen the app closes and I get a "Slim Explorer has stopped" message. I've seen it in the past a handful of times I went to change DPI with it before installing ES. I did a complete clean install(ie. manually wiped everything and re-downloaded and re-setup all my apps instead of restoring them with Titanium), sha matches, so I can't think of anything else that could be the issue. Maybe it doesn't agree with Super SU???
Click to expand...
Click to collapse
U mean simple explorer ?
Its working for me.
It could be super user, I've had issues with it
First post on this forum has link to supersu, download zip file flash in recovery. C if that solves the issue
Sent from my Nexus 5 using Tapatalk
AquilaDroid said:
Yep, did all that except for the SuperSU bit. I did use SuperSU on the Purity install though but haven't had any problems with the built in Superuser before. I'll nandroid back to the Slim ROM to give it a try. It was with the stock kernel.
From my Nexus 5
Click to expand...
Click to collapse
I've had issues with super user so always use supersu, but maps has nothing to do with either.
Did u check the settings?
Also sometimes you have to be outside to get a GPS lock,
Also try this:
Settings -> apps-> maps.
Clear data clear cache force close.
Reboot
Go outside and open maps c if that fixes it
Sent from my Nexus 5 using Tapatalk
OK, but it will be a while - when I went into recovery (TWRP) it asked for a password (which I haven't set) then failed to backup the existing ROM.
Sent from my Nexus 5 using Tapatalk 2
fruitsalt said:
U mean simple explorer ?
Its working for me.
It could be super user, I've had issues with it
First post on this forum has link to supersu, download zip file flash in recovery. C if that solves the issue
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
I have Super SU installed and working already seeing as I use Faux kernel as well as I've always had issues(even on a SlimBean port on Evo LTE)with Superuser unmounting the system as RW. It's weird. It only happens when I scroll from within the emulated/legacy/0 storage. I can scroll within the device partition and change settings just fine.
Do you use ART??? Only other thing I can think of.
Edit: Added a screenshot to the post as well as a bug report
Hello,
So i've been having a bit of a hard time getting viper to stick. This usually happens when I do a reboot or change from headset to bluetooth and vice versa.
I've converted viper to a system app through titanium, and although that solves the recent app problem, the driver seems to not process automatically after a reboot or a sleep period. In order to get it to stick, I would have to do another reboot and then enable/disable a couple of times.
Anyone know of any other suggestions? Help would be greatly appreciated! Thanks!
good luck, i still havent got it to work properly. im assuming we need to wait for an update for full compatibility
works fine here. after reboot as well. i installed the 4.X apk. opened it, installed the drivers, rebooted, and everything works as should, even afyer a reboot. but i dont install it into /syatem/app/, i keep it in /data/app/ with all my other apps http://vipersaudio.com/swupdate/viper4android/ViPER4Android_FX_A4.x.apk
Thanks for the replies. I managed to get it to stick using combo of converting to system app and changing fx compatible mode to compatible.
Hi guys,
i got a problem. From this morning, when i try to open the camera, it FC with the error in the log i have attached.
I've done those steps:
1) I have terminated and cleared data of both apps (gallery & camera) being the cause of the problems > NOTHING HAS CHANGED
2) Flashed stock 4.4.2 camera via TWRP > NOTHING HAS CHANGED.
Reading the log, seems a problem of my AndroidManifest? an activity not declared? How could it be a google app not declared in AndroidManifest?
The only thing i can remember that can be the cause of this problem is this: yesterday i tryed to migrate from franco to faux kernel. I did those steps
Franco > stock > faux.
I booted the phone, opened faux app..i forgot to close FKU app, and seems like there was a conflict between 2 app, i saw the max frequency jumping from 1.7 Ghz ( setted in FKU) to 2.25 ghz ( setted in faux123) many times fastly. After few seconds, everything freezed and phone reboot. So i decided to come back to franco.
Do you think that this can have ****ed up the AndroidManifest?
thanks in advance
federikk90 said:
Hi guys,
i got a problem. From this morning, when i try to open the camera, it FC with the error in the log i have attached.
I've done those steps:
1) I have terminated and cleared data of both apps (gallery & camera) being the cause of the problems > NOTHING HAS CHANGED
2) Flashed stock 4.4.2 camera via TWRP > NOTHING HAS CHANGED.
Reading the log, seems a problem of my AndroidManifest? an activity not declared? How could it be a google app not declared in AndroidManifest?
The only thing i can remember that can be the cause of this problem is this: yesterday i tryed to migrate from franco to faux kernel. I did those steps
Franco > stock > faux.
I booted the phone, opened faux app..i forgot to close FKU app, and seems like there was a conflict between 2 app, i saw the max frequency jumping from 1.7 Ghz ( setted in FKU) to 2.25 ghz ( setted in faux123) many times fastly. After few seconds, everything freezed and phone reboot. So i decided to come back to franco.
Do you think that this can have ****ed up the AndroidManifest?
thanks in advance
Click to expand...
Click to collapse
Dirty flash the rom you are on, maybe something gets messed up.
If that doesn´t help either - full wipe and start fresh
Regards
Im running a stock rooted rom with Franco Kernel installed. For some reason when I select a performance profile it will not stay. It will select it but when I close the app and reopen it, it is no longer selected. I do have the CPU voltage control set below the defaults. Is it possible that manually selecting a setting will override the performance profile and unselect it? Thanks for the help.
Why not ask in its thread? lol
Do you use any other app which controls the kernel? Like Trickster MOD or something?