yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy S 4 Unified Development] Triscuit:
Ok you guys weren't kidding....I've used ART before on kitkang a while back but it was meh. ART on vanir?? Oh the humanity!!!! The only I have is ART doesn't seem to like modified apps, I have a YouTube app that forces HD playback and screen off playing and it instantly force closes when I boot and when I try to run it. Oh well speed is a winner right now since I have 4 days off and I don't need YouTube while I'm at home!
[Samsung Galaxy S 4 Unified Development] crossen0:
Where is this YouTube apk you speak of?
[Samsung Galaxy S 4 Unified Development] bkrickles:
I switched to art this morning and I'm only on 1/15 build and it definitely seems smoother. I only had one app (unpaid for) that won't work with it so I'm definitely pleased.

I just downloaded 1/17 build along with 1/17 pa gapps and I'm going to flash in 30 minutes when I get home and see how that is with art.

I read somewhere that starting with 1/16 build there were some changes to improve how art worked on this rom so we'll see how it goes.

Thanks to all for your comments and developers for a great rom!
[Samsung Galaxy S 4 Unified Development] ks3rv3rg:
Done! ;)
[Samsung Galaxy S 4 Unified Development] Nydalxy:
Can't wait to flash this later! Thanks for the support thread!!
[Samsung Galaxy S 4 Unified Development] Triscuit:
Just an FYI for anyone who uses viper4android, it's working flawlessly on vanir. Just have to edit one thing in the build.prop
[Samsung Galaxy S 4 Unified Development] :
ok i give up...what is it lol
[Samsung Galaxy S 4 Unified Development] Demiurge7:
Audio driver/mod. Takes the place of DSP. Advanced options, really nice eq, effects, etc.
[Samsung Galaxy S 4 Unified Development] ecsnead69:
where do you find it? And what build.prop change is needed?
[Samsung Galaxy S 4 Unified Development] Demiurge7:
http://xdaforums.com/showthread.php?t=2191223

I have only needed to change permissions in the past (put in sys/app and change to rw-r-r. Perhaps priv-app on 4.4). Not sure what is meant by changing build prop. Instructions on thread.
[Samsung Galaxy S 4 Unified Development] Triscuit:
I install it as a regular app, and the line in the build.prop is : lpa.decode=true change it to false and reboot.
[Samsung Galaxy S 4 Unified Development] Demiurge7:
Nice, TY. I haven't tried on KK yet, but will give it a shot. Old procedure was a bit easier.

IR does not work on latest, FYI. I tried with touchsquid and smartremote. I think the only 4.4 ROM I have seen with working IR is gummy. Hope that is integrated soon, as Vanir definitely has the most/best customizations. Thanks to OP for starting a thread here as well.
[Samsung Galaxy S 4 Unified Development] mcconvict:
I also add tunnel.decode=false and lpa.use-stagefright=false
[Samsung Galaxy S 4 Unified Development] :
i put it in the rom before flashing and delete dsp manager and works fine...may be more than one way to do it...thanks for the share...if i have problems ill do it your way
[Samsung Galaxy S 4 Unified Development] amosavitas:
it's about time that Vanir/Commotion gets the attention deserved by the s4 community, happy flashing.
[Samsung Galaxy S 4 Unified Development] Triscuit:
Hmm I've never added those lines, I was always under the impression that they only need to be changed if they are already in the build prop. I'm gonna have to try it out.
[Samsung Galaxy S 4 Unified Development] Draphix:
Viper is working ir is working. And really good battery also. Loving this rom. Thanks!
[Samsung Galaxy S 4 Unified Development] Crossoverdoc:
Has anyone run into 64GB exFat sdcard troubles? I asked elsewhere and didn't seem to find a definitive answer. Seems like some people experienced losing storage space when changing formats. Any insight would be appreciated.
[Samsung Galaxy S 4 Unified Development] ks3rv3rg:
Okay, so just to be clear;

People need to ADD or CHANGE these lines in the build.prop? I'll add this to the op if I can make it clear enough.

So CHANGE the line "lpa.decode=true" to false?

and ADD the two lines tunnel.decode=false and lpa.use-stagefright=false

Correct?
[Samsung Galaxy S 4 Unified Development] ks3rv3rg:
What exact issue are you experiencing? There have been issues reported but there may be solution.

Here's one solution that works:

Plug your phone into your PC

Copy all SDCARD data to backup folder on your PC

Format SDCARD in recovery

Copy files back to SDCARD

Should be good to go on KK ROMS
[Samsung Galaxy S 4 Unified Development] ks3rv3rg:
Did you need to change anything in your build.prop for viper to work?
[Samsung Galaxy S 4 Unified Development] Crossoverdoc:
It just hasn't been reading the card.. It's been showing as 0.00 Bytes in the settings. I'll try this solution in the morning.
[Samsung Galaxy S 4 Unified Development] Triscuit:
Mine is working with just changing lpa.decode, I haven't tried adding the other lines yet so I'm not going to say yes or no on that.
[Samsung Galaxy S 4 Unified Development] Triscuit:
http://xdaforums.com/showthread.php?t=1529715
[Samsung Galaxy S 4 Unified Development] Efrenjr15:
And from the looks of it KT is updating here shortly pretty sure it has some stuff to do with the ART changes that were made around. But seriously don't think it can get any smoother then this and +1 on the YouTube app fcs
[Samsung Galaxy S 4 Unified Development] dougmod:
does this rom have the quick settings tiles? if so, can you access them by swiping side to side on the notification drop down (like on liquidsmooth), or do you have to tap the quick tile button?
[Samsung Galaxy S 4 Unified Development] Triscuit:
Yes and slide
[Samsung Galaxy S 4 Unified Development] dougmod:
awesome because this rom looks pretty solid. looks like everything pretty much works. as long as bluetooth works and i have those sliders, it should be golden!!

oh and is one of the tile options torch?

I have been a liquidsmooth guy for over a year and I am thinking of making a change..
[Samsung Galaxy S 4 Unified Development] Triscuit:
Yep! You won't be disappointed with this ROM.
[Samsung Galaxy S 4 Unified Development] dougmod:
im really excited. i mean my big 3 features are bluetooth, swping to tiles and notification LED control. if i have that, im a happy man hahah. backing up now...
[Samsung Galaxy S 4 Unified Development] Triscuit:
You might want to check out ktoons kernel, he just updated his ktweaker app with LED control!
[Samsung Galaxy S 4 Unified Development] icon123:
Does this have "vibrator intensity" control yet? It's a little bit high for me.
[Samsung Galaxy S 4 Unified Development] dougmod:
rom is running really well. i do notice on my launcher and nova launcher, there is a black gap at the bottom of the screen. do you know how to get things to align properly to the bottom of the screen?

great job on this rom
[Samsung Galaxy S 4 Unified Development] brizey:
re-apply your wallpaper?
[Samsung Galaxy S 4 Unified Development] usmcamgrimm:
I've noticed today that when I select a notification in the notification drawer it hangs for a good 20 seconds before it opens the notification. Still on 1/16...didn't have the lag until today
[Samsung Galaxy S 4 Unified Development] 808phoneaddict:
Everything with this rom seems to be working awesomely! Only prob I've had is my scramble with friends hasn't been working thru data connection... It works thru wifi but not regular Verizon data connection... Really minor compared to how awesome everything else is!
[Samsung Galaxy S 4 Unified Development] dougmod:
do you guys think its a good idea to turn on art? i flashed the latest KT
[Samsung Galaxy S 4 Unified Development] 808phoneaddict:
Read the last couple pages of comments on art
[Samsung Galaxy S 4 Unified Development] mcconvict:
Yes. Do it immediately
[Samsung Galaxy S 4 Unified Development] usmcamgrimm:
Go for it...ART works great...it's smooth and fast
[Samsung Galaxy S 4 Unified Development] Triscuit:
Just be warned, first boot after enabling ART will take a LONG time. And your phone will get hot. I usually put the phone in the fridge for about 10mins during first boot.
[Samsung Galaxy S 4 Unified Development] 808phoneaddict:
Yup, and clearing cache and dalvik will do the same,
[Samsung Galaxy S 4 Unified Development] namedkwon:
Anybody having issue with the Quick Unlock not working on the 1/17 build?
[Samsung Galaxy S 4 Unified Development] ks3rv3rg:
Our phones have a temp safety switch that will cause shutdown if the processor/phone gets to hot. Even this level of heat is well below what will cause problems. Of course keeping it cooler tends to be helpful and promote longevity in your device but the 5/10/15 min it takes on startup for that time isn't enough to damage your phone in any way. Although I do like the mental image of your phone in the fridge! ;P
[Samsung Galaxy S 4 Unified Development] ks3rv3rg:
Don't wipe davlik with ART enabled.
[Samsung Galaxy S 4 Unified Development] 808phoneaddict:
I only did it because I was flashing a new kernel, as i# typical protocol if I'm not mistaken.. Should I not now that I'm using art?
[Samsung Galaxy S 4 Unified Development] mcconvict:
Hell, I've quit wiping anything on a kernel flash. I just flash and reboot
[Samsung Galaxy S 4 Unified Development] ks3rv3rg:
Do not wipe davlik while using ART. That is protocol for normal everyday flashing. This is not the case using ART.
[Samsung Galaxy S 4 Unified Development] dougmod:
is there any way to adjust the volume of the phone just after waking it, but not unlocking?
[Samsung Galaxy S 4 Unified Development] asf1187:
I find that when I reboot my phone it won't work more often than not. It'll freeze or just won't pass the boot animation. I have to reboot several times.
[Samsung Galaxy S 4 Unified Development] 808phoneaddict:
After choosing ART? first boot takes a really long time when selecting ART
[Samsung Galaxy S 4 Unified Development] ks3rv3rg:
Did you clean flash? What build?
[Samsung Galaxy S 4 Unified Development] asf1187:
yes. clean flash on 1/16
[Samsung Galaxy S 4 Unified Development] ks3rv3rg:
Try the newer nightlies.
[Samsung Galaxy S 4 Unified Development] mcconvict:
No build today
[Samsung Galaxy S 4 Unified Development] ahoslc:
I believe I read that the build script broke.
[Samsung Galaxy S 4 Unified Development] usmcamgrimm:
Mjolnir unlocks my Vanir :D
[Samsung Galaxy S 4 Unified Development] brizey:
I could not get 1/19 to boot. I was using KT 1/17, but I was using that on 1/18, too. Anyone booting 1/19 OK using the stock kernel? Don't have time to test, just had to get my phone back up and running.

Edit: oops, didn't mean to quote usmcamgrimm

Edit #2: But that bad ass paper does deserve another view, lol
[Samsung Galaxy S 4 Unified Development] ks3rv3rg:
There were some complaints like this on the sprint side too. Do you flash the ROM then the kernel immediately without rebooting? This can cause problems. Dirty flash? Clean flash?
[Samsung Galaxy S 4 Unified Development] brizey:
Dirty flash...no boot.

So I wiped and tried again--with KT immediately as well as the optimized dalvik stuff...no boot.

Realized I needed to get it together and restored my backup.

So Yes, Yes, and Yes.

So all kinds of crappy flashing techniques that work 95% of the time...I guess this may be that 5% where you need to do things right...OR...somethings broken in the build. That's why I was asking to see if it was worth trying again with a real basic clean flash...'cause I was getting the "are you still f%$#in' with your phone" glare from the wifey.
[Samsung Galaxy S 4 Unified Development] Ironclad Lou:
Completely clean flash, stock kernel. Haven't been on this ROM in a long time. Reading through the last few pages decided to try ART. Crazy fast. Everything seems to be working well, just noticing some weird stuttering with haptic feedback when typing. Hard to describe, almost like the vibration strength is going up and down at random every few key strokes.
[Samsung Galaxy S 4 Unified Development] Triscuit:
I also had issues with with 1/19 build, clean flash. Wouldn't even get past the boot screen! I'm back on 1/18 for now
[Samsung Galaxy S 4 Unified Development] ahoslc:
Were you also trying to install custom kernel?
[Samsung Galaxy S 4 Unified Development] Triscuit:
I tried with and without. I always go to stock kernel if I experience issues.
[Samsung Galaxy S 4 Unified Development] ahoslc:
Good to know I guess I won't flash then .
[Samsung Galaxy S 4 Unified Development] Addiso:
Mine is working flawlessly.
[Samsung Galaxy S 4 Unified Development] Triscuit:
Dirty? Clean?
[Samsung Galaxy S 4 Unified Development] TMYINC:
I wonder if some of the kernel commits are messing with it booting. Thought I read they were merging some in recently.
[Samsung Galaxy S 4 Unified Development] Addiso:
Dirty flash from 1/16 I believe. Phone is working fine no force closes or anything.
[Samsung Galaxy S 4 Unified Development] btvolta:
Ok, everyone who says running fine, are you using the 1/17 KT kernel or stock. We already have confirmed that it boots with the stock kernel, so please confirm kernel.
[Samsung Galaxy S 4 Unified Development] bkrickles:
Not working with custom kernel
[Samsung Galaxy S 4 Unified Development] amosavitas:
thanks B you saved me a restore
[Samsung Galaxy S 4 Unified Development] cryogenic666:
So is there an easy way to get this ROM to boot the kernel at stock speeds? It boots up on mine overclocked to 2.322Ghz and my phone locks up in approximately 15 seconds if it tries to boot at that speed. If I'm SUPER fast, I can get into performance settings and set it to a more sane speed, but even that doesn't always work. Who in their right mind would want their phone to boot overclocked by default to that ridiculous speed?

This is after a CLEAN flash with the PA GAPPS.
[Samsung Galaxy S 4 Unified Development] ks3rv3rg:
Better to be safe than sorry, just go back to the 1/18 build. Its running great. To many reported issues to mess with it in my opinion.
[Samsung Galaxy S 4 Unified Development] ks3rv3rg:
Also, have any of you tried letting the phone boot after flashing, THEN rebooting and flashing the custom kernel? This method can generally solve this kind of issue.
[Samsung Galaxy S 4 Unified Development] bkrickles:
That's what I did and it didn't work
[Samsung Galaxy S 4 Unified Development] btvolta:
That was one of the procedures I tried.

Sent from my SGH-L720 using Xparent BlueTapatalk 2
[Samsung Galaxy S 4 Unified Development] cryogenic666:
I just flashed to a different ROM, actually. No problems with that one, so that 1/19 build is apparently busted all to hell and back. I might come back and try this one out at a later date.
[Samsung Galaxy S 4 Unified Development] bkrickles:
The rom is fine. Just can't flash custom kernels today
[Samsung Galaxy S 4 Unified Development] ks3rv3rg:
Well that's what can happen when you are flashing nightlies of a ROM that is being constantly updated.
[Samsung Galaxy S 4 Unified Development] cryogenic666:
Yup. They're called Nightlies for a reason. I generally will flash between several different ROM's, so I'll likely try this one out again another time. It's not a big deal. Stuff happens and things break.
[Samsung Galaxy S 4 Unified Development] ahoslc:
I never bothered to look at clock speed till today wonder if 2.3ghz is there default for stock kernel.
[Samsung Galaxy S 4 Unified Development] Addiso:
I'm running kt kernel on 1/19 tho, here's a screenshot
[Samsung Galaxy S 4 Unified Development] brizey:
Odd how it works for some.

What recovery and version and how did you flash (clean, dirty, kernel right away, kernel after a first boot, optimized dalvik, etc.).
[Samsung Galaxy S 4 Unified Development] Addiso:
Twrp latest forgot what version it is but I know it's the latest one out. Dirty flash from 1/16, kernel right after it, and also optimized dalvik after that.
[Samsung Galaxy S 4 Unified Development] brizey:
The only thing I did differently was flash from 1/18.

But, if the stock performance settings have some crazy high default speed, then it is likely the culprit. Even if you flash KT, his control app doesn't take over until after boot (I think). I'm guessing you have rock star binning on your SOC.

Edit: Looks like 1/20 is up with some governor fixes in from the last 24 hours. Gonna give it a shot during one of my morning conference calls.

Edit: Was only able to boot 1/20 on the stock kernel. No go with 1/17 KT. Dirty flash, too.

Edit: WTF? I installed trickstermod to play around with the stock kernel and koontzsservativeq is one of the governor options, and the kernel name has KT in it. Is the stock kernel a version of koontz's kernel?
[Samsung Galaxy S 4 Unified Development] dougmod:
im on 1/17 and notice I do not always get notifications for my apps. Whats app, gmail and google voice seem to give notifications if I go into the app, but if i am not in it, they will not push. any ideas?
[Samsung Galaxy S 4 Unified Development] ahoslc:
Yes stock Kernel is based off of Ktoonz
[Samsung Galaxy S 4 Unified Development] Atheron121:
ART question

I've been noticing that while running ART, installing nightlies seems to take a very long time when updating all the apps (no clearing of cache or dalvik). Is that process normally supposed to take just as long (or longer sometimes) as the first time ART is activated? Or am I just doing / not doing something?

Usually just do the normal nightly updates, but the phone still takes a good 15 - 20 minutes to update apps, and get somewhat warm in the process.
[Samsung Galaxy S 4 Unified Development] bkrickles:
I've had the same experience, so I'll say it's normal.

When finished, it's been terrific.

I'll add that after a week on vanir w/art, I've been on nameless the past couple of days and installing nightly's has been the same
[Samsung Galaxy S 4 Unified Development] Atheron121:
ART question

OK, thanks. Thought it was me doing something wrong (again...).
[Samsung Galaxy S 4 Unified Development] bkrickles:
getting ready to throw this on again after a couple of days on another rom.

I'm bored and tired from shoveling.

Anyway, was wondering what peoples experiences have been with commotio vs. plain vanir

A couple of weeks ago I ran commotio and then I went to the plain vanir and thought the plain ran better.

It was probably just in my mind (There's very little there, by the way) but I figured I'd ask anyway.
[Samsung Galaxy S 4 Unified Development] Triscuit:
I personally haven't run commotio yet.

---------- Post added at 04:55 PM ---------- Previous post was at 04:55 PM ----------

Just FYI peeps. 12/22 build still won't boot with custom kernel. Boots fine with stock.
[Samsung Galaxy S 4 Unified Development] amosavitas:
thanks for the heads up Triscuit, [MENTION=2965986]bkrickles[/MENTION] I share your sentiment, it's probably psychological but I think Vanir has better performance.
[Samsung Galaxy S 4 Unified Development] ks3rv3rg:
This is completely normal/typical when using ART. No worries. :)
[Samsung Galaxy S 4 Unified Development] TMYINC:
There was some changes to init.d so I'm wondering if that doesn't have something to do with it not booting with a custom kernel. One file I found in the init.d folder was 00kernelcompat. Not sure if this has anything to do with it but I haven't looked at the file yet.
[Samsung Galaxy S 4 Unified Development] ks3rv3rg:
I run Vanir myself. Commotio tends to be a bit more of a testing ground for new scripts/ideas and I prefer to have a solid DD.

Also everyone, the solution to flashing the custom kernel does work. The script 00kernelcompact was included in all builds after 1/18. If you navigate to system/etc/init.d/ and delete this file you can flash custom kernel. Its always good practice to read through the files in this folder as they are mostly ROM specific and give you a better understanding of what's going on behind the scenes.
[Samsung Galaxy S 4 Unified Development] Triscuit:
I happened to see this on the Google+ page. Was about to quote it but you beat me to it.
[Samsung Galaxy S 4 Unified Development] ks3rv3rg:
That was me that posted it. :)

You can also just open the zip of the ROM and delete that file before flash. This is way easy.
[Samsung Galaxy S 4 Unified Development] mcconvict:
Tried this. It booted. But it doesn't run right. Screen would lock when trying to pull down notification shade. Just went back to stock kernel
[Samsung Galaxy S 4 Unified Development] ks3rv3rg:
Weird. I haven't had any issues.
[Samsung Galaxy S 4 Unified Development] mcconvict:
Its just that one file to delete?
[Samsung Galaxy S 4 Unified Development] bkrickles:
I deleted the one file but haven't flashed kernel yet. I will check it in a bit
[Samsung Galaxy S 4 Unified Development] ks3rv3rg:
Yep just one file.

So just to make sure I just tried it.

I booted to recovery and dirty flashed 1/22 over 1/18, booted the ROM, moved the file to a temp folder, booted back to recovery, flashed KT 1/17. Because I'm using ART I only wiped cache and rebooted. ART did its thing for 10 min or so then I was back up with no issue.
[Samsung Galaxy S 4 Unified Development] mcconvict:
Honestly, it seems to be something with the 1-22 build that doesn't agree with my phone. It did the same thing on stock kernel.
[Samsung Galaxy S 4 Unified Development] asf1187:
Things are currently running great for me! Getting 3hrs+ on screen time. What do you suggest we do about the display not turning on sometimes. is that just relating to the cpu governor? Other than that, the rom is running perfectly.
[Samsung Galaxy S 4 Unified Development] dogg94:
I came here looking for this, same results running art, it's very smooth and seems to hold up over multiple days quite well (better in my experience than normal dalvik did with other aosp based Roms on the s4) but Haptic feedback is all over the map sometimes strong, sometimes weak, sometimes none. Overall I am impressed enough to keep this as my dd though thanks :thumbup:
[Samsung Galaxy S 4 Unified Development] bkrickles:
I deleted the one file mentioned previously before flashing vanir 1/22 nightly last night.

This morning, while running w/art, I flashed kt kernel 1/17 and restored one of the profiles I use (ktoonsifiedv4)

Everything seems to be fine so far, so I'll assume the fix works for those interested in custom kernels.

If anything changes, I'll report back.

Rom is great. I'm using lockscreen notifications, which I really like, and the rom is speedy.

Between this and Nameless, I could not be happier.

Also, I mentioned yesterday I was interested in commotio, so I flashed it first and for some reason I just feel the plain vanir is better, although I like the way commotio looks better.

Just my 2 cents.

Thanks
[Samsung Galaxy S 4 Unified Development] mrbigdrawsz:
I'm currently on the 1/22 build and previously ran the 1/19 build and I don't get any of my defaults saved. Every time I do something I have to choose a default application and when I chools "Always", it still makes me do it the next time.

Anybody else getting this or is there a setting on this Rom that I'm missing?
[Samsung Galaxy S 4 Unified Development] ahoslc:
Dark dialer and contacts that seem to run well this Rom here http://xdaforums.com/showthread.php?t=2526844
[Samsung Galaxy S 4 Unified Development] ks3rv3rg:
I haven't experienced this at all.
[Samsung Galaxy S 4 Unified Development] Efrenjr15:
kT updated his kernel don't seem like much changed but has anyone been able to flash on latest builds? Seen a bunch of ppl were having to do some things to get it to boot
[Samsung Galaxy S 4 Unified Development] bkrickles:
Yep. You have to remove 1 file. Easiest to do before flashing a nightly. Instruction is within last day of posts here
[Samsung Galaxy S 4 Unified Development] Efrenjr15:
Even with the update KT did today?
[Samsung Galaxy S 4 Unified Development] Triscuit:
Yes, file that gets deleted is on the ROM side.
[Samsung Galaxy S 4 Unified Development] bkrickles:
I removed the file on my computer before moving the ROM download onto my phone. I found it to be easier that way. Then I flashed ROM and then the kernel.
[Samsung Galaxy S 4 Unified Development] Triscuit:
Actually guys.....I stand corrected, just for the hell of it I flashed KT latest kernel on 1/22 vanir build without deleting the file and it booted fine.
[Samsung Galaxy S 4 Unified Development] bkrickles:
That's excellent news. I love easy