Related
How do I use the optimized dalvik binaries? In developer mode I only see option for Dalvik or ART
http://forum.xda-developers.com/showpost.php?p=52353481&postcount=21
It is one or the other. Art also has what seems to be a compatibility mode. But as many report, not for Xposed.
Summarized Standard Disclaimer: use at your own risk. I use it at mine.
*Full wipe recommended if coming from another kitkat rom*
MAKE SURE TO HAVE A BROWSER APK. THERE IS NO MORE STOCK BROWSER. For firefox see below.
My personal build "Diamond Rom 4.4" is based on omnirom with the following additions:
CM Calculator (the newly redone one they're proud of)
CM File Manager
CM Wallpapers
Bash shell
Nano text editor
Powertop
Koush's full featured open source superuser (and it's INTEGRATED into settings :cyclops: )
Carbon rom blue balls wallpaper
Cyanogenmod port of 2 column settings adapted to Omni rom.
Omni floating window
I've added a few of my personal touches which include
Batter circle color changing: green 100%-51% yellow 50%-16% red 15%-0% This was my favorite I9000M framework-res mod that I've missed since switching to CM7.2 way back.
Killed lock screen music full screen (personal privacy thing when riding public transportation)
Disable android external storage management: messes with ext4 formatted hard drives or multi partitioned hard drives. Use the unix style mount command
Disable hardware keyboard on boot: disabled but not removed. You'll have to manually turn it on
Removed camera sounds
Disable SELinux at the kernel level. It's even disabled on my laptop/desktop at the kernel because it seems like it's more trouble than it's worth.
Put the dalvik cache in the cache partition. Don't waste the data partition for it. :cyclops:
And of course, comes bundled with my A1 kernel :cyclops:
Every thing I've tested: camera, youtube hd, sound, gps, usb otg(use manual mount command) etc work.
*Instructions*
First time flashing omni:
-Read second post FAQ and other important information.
-Flash TWRP (you can flash twrp over cwm from cwm if you're in that situation)
-Reboot into new recovery
-Make recovery backup (optional)
-Run Titanium Backup (highly recommended)
-Full wipe
-Format system partition
-Install ROM
-Install gapps
-Reboot :cyclops:
Subsequent flashes:
-Install ROM
Downloads
Mediafire Wifi download folder with md5sum file
Mediafire 3G download folder with md5sum file
Mediafire TMobile download folder with md5sum file
*Authorization to download is just a captcha. Simply enter the text in the picture or name the item being advertised in the picture.* Mediafire sure beats sh***y sites like uploaded.net or rapidgator
A1 Kernel (as its own download)
V1.9.2: Security fix made aware by cyanogenmod, specifically this. The commit message on my github has a copy and paste mistake. It should list both of those security flaws as patched instead of the same one twice. Oops :cyclops: Security fix comes with ALL roms June 28 and onwards.
3G/Wifi 6ff199d6c9037d222a70ec0c561c8028
TMobile a675fd353ad3ad7dbf8e6bf2109fa360
TWRP Recovery
2.7.1.0 Wifi 6c995325e749e7561893e398847b09a0
2.7.1.0 3G 8fa04be69d0faf3d9a134e829ddff680
2.7.1.0 Wifi July 8 a8d12c13aac7430a319369069d814e72
2.7.1.0 3G July 8 dc1c50622c29c621f29b95f4c53734ea
2.7.1.0 Wifi August 11 b2c21e8fd58dc38a9c8b7669031b84b1
2.7.1.0 3G August 11 9f48defe78391e63a9053cbd281f738f
2.7.1.0 TMobile August 11 87fb29c803a2e3a56d98a1475c5fce8f
2.8.0.0 Wifi cfdac70d0ccac34cf220887eab72f8b0
2.8.0.0 3G d7918eb397f54c484e04a6d5cb07945c
2.8.0.0 TMobile aaf7c6d2455ca32178ec846f5186c774
Newer versions of firefox explicitly disable flash on tegra2. Use my firefox mod which is just normal firefox with a hacked tegra2 blacklisting mechanism. Don't use the old firefox apk. It has unpatched security holes.
Changelog: omnirom gerrit
Sources: https://github.com/AAccount?tab=repositories Has my device trees as well as all the omni repos I forked with my additions.
Credits:
Kasper_h: helping to make 4.4 possible
pershoot: original device tree from CM10.1
Omni team: providing great starter rom and keeping it TF101 compatible
fred6681: original gapps package. I just removed the 4.4.2 check
Cyanogenmod team: rom extras like calculator, superuser, to fill in Omni's missing holes and 2 panel settings template.
XDA:DevDB Information
Omnirom+ 4.4 for Galaxy Tab 10.1, ROM for the Samsung Galaxy Tab 10.1
Contributors
AAccount
ROM OS Version: 4.4.x KitKat
ROM Kernel: Linux 3.1.x
Based On: Omni
Version Information
Status: Stable
Created 2014-10-12
Last Updated 2014-10-11
Known Issues:
Wifi signal indicator and speed indicator don't show up
No list of 3G APN. Write down your settings first
Bluetooth audio issues
Recovery adb doesn't start automatically. In recovery, go to Advanced --> ADB Sideload and start it. You can then cancel it if you don't want to use that. It just starts the recovery adb and will continue to run until you reboot. fixed thanks to twa_priv
Use another recovery for TMobile. Apparently the twrps I make can't boot on TMobile hardware even though it boots on my Wifi only.
FAQ
How do I get multi window: Settings-->(second) More --> App circle bar (check box) && --> Included apps (choose what you want available in multi window)
Yes you can flash TWRP over CWM
Random flickering: Try Settings-->Developer options -->Disable HW Overlays.
Can't install a very large quantity of apps: fix
Can't mount ext4 media: kill the e2fsck process assuming you safely removed the media before sticking into the tablet.
(Below this is optional)
(Android device manager does have legitimate uses. However, please read and consider the following paranoid but realistic fantasy:)
Completely disable android device manager: By only going to Settings->Security->Device administrators and un checking "Android Device Manager" this doesn't completely remove the ability for google to send in commands to your device. Go to the google play store through a web browser, choose android device manager, and try "ringing" your device. To my horror, my tablet started to ring as if it got a phone call. I don't find it acceptable that gapps gives google a way to setup a remote command and control operation. In any other operating system this is considered a back door or virus.
To close this back door install Xprivacy. Enable system apps to be modified. Look for the entry (should be highlghted in red to indicate a system app) "Google Account Manager, Google Backup Transport... (lots of items here) ...Google Services Framework". Check mark Notifications and open its menu. Check mark the items in red. These are cloud to device (c2d) permissions which do exactly what you think. While not necessary, disable identification too for good measure. This disabled the ring feature on my tablet which means android device manager should no longer be able to send in commands. I don't have the guts to try the device wipe feature but it should work too. Do not disable location otherwise google maps won't be able to find you which means no gps car navigation.
See this post about building from source. I use a different, simpler trick for prebuilt chromium binaries. Fear not, they are source built but only when there are real source changes. They're just recycled in between to save 90mins/build of time.
Downloading now!! Thanks for your work!!
Enviado desde mi GT-I9195 mediante Tapatalk
Another 4.4.3 for the tab?
Thank you very much!
Hi AAccount,
thanks for your 4.4.3 ROM, sounds promising ... however, what about the graphical glitches on that vesion? I always went back to ROM version CM10.2/SGT7 as this seems to be the latest one without those glitches (last version I tried was Nameless ROM version 4.4.2 where they were still visible ... and annoying).
Thanks in advance,
mistersixt.
Great job!! Runs fast without bugs and glitches, only youtube HD...
The best kitkat rom!! Thanks !
Enviado desde mi GT-P7510 mediante Tapatalk
Best kitkat rom. I have some glitches. It is not as smooth as cm10.2 so i am going back to cm10.2.
What graphical glitches do you mean? I think ever since omni fixed the screenshot way back most graphical bugs have been ironed out. By youtube hd do you mean it doesn't play or can be laggy? If you mean laggy I read on wikipedia the GPU video decoding on the tegra2 sucks. That's a hardware problem.
3G build and new recovery coming later today. I cheated the chrome renderer build process by copying all the freshly done ones from the wifi only output folder.
My github is now fully up to date with all the appropriate omni repos forked with my personal touches whether it be the audio blob fixes or little things I like.
Sent from my GT-P7510
What are the flashing instructions? Is there a preferred gapps package?
Sent from my GT-P7510 using Tapatalk
AAccount said:
What graphical glitches do you mean?
Click to expand...
Click to collapse
With all ROMs starting with 4.3 it looks like if a flash of lightning goes from one corner to the other (my wife is saying it looks more like a scratch) for maybe 100 ms, this happens quite constantly though, every minute or something. Also, in some games like flappy bird the application gets stuck for maybe 100 to 200 ms completely (every 5 to 10 seconds maybe) before it continues, this makes playing games unpossible (temple run is another good example).
With 10.2/SGT7 this does not happen ... for whatever reason.
Regards, mistersixt.
lancem71 said:
What are the flashing instructions? Is there a preferred gapps package?
Sent from my GT-P7510 using Tapatalk
Click to expand...
Click to collapse
I added instructions. There's no really preferred gapps package. I just like that one because it's the smallest one that gets the job done. There are some gapps packages that are bigger than the rom which I consider bloated.
mistersixt said:
With all ROMs starting with 4.3 it looks like if a flash of lightning goes from one corner to the other (my wife is saying it looks more like a scratch) for maybe 100 ms, this happens quite constantly though, every minute or something. Also, in some games like flappy bird the application gets stuck for maybe 100 to 200 ms completely (every 5 to 10 seconds maybe) before it continues, this makes playing games unpossible (temple run is another good example).
With 10.2/SGT7 this does not happen ... for whatever reason.
Regards, mistersixt.
Click to expand...
Click to collapse
I get these randomly sometimes but not often enough that I would consider it an issue. In angry birds it's an issue but if you go to Settings-->Developer Options check mark "Force GPU rendering" and "Disable HW overlays". Then you can play angry birds at least without the lightning.
And now for an important question
I have a script that puts /data/dalvik-cache on /cache/dalvik-cache as it was way back in android 2.2 froyo. Even though our tablet shipped with android 3.0 and my I9300 S3 shipped with android 4.0, Samsung seems to have been very sloppy and left the /cache partition huge to accomodate the froyo standard. This is a waste of space that will never be used. The cache paritition is 0.5GB. Is it OK if I include this script as a boot script? Is 0.5GB/500MB enough for most peoples' dalvik-cache? This will free up that space and add it to the internal sd card.
Great room, thanks! Everything working OK during the first hour of use
Sent from my GT-P7500 using XDA Free mobile app
Thanks for posting this! Great ROM. Only problem I'm having is the APN settings are blank for my 3G tablet (P7500). I input them manually and everything works, but normally they are preset.
AAccount said:
I get these randomly sometimes but not often enough that I would consider it an issue. In angry birds it's an issue but if you go to Settings-->Developer Options check mark "Force GPU rendering" and "Disable HW overlays". Then you can play angry birds at least without the lightning.
And now for an important question
I have a script that puts /data/dalvik-cache on /cache/dalvik-cache as it was way back in android 2.2 froyo. Even though our tablet shipped with android 3.0 and my I9300 S3 shipped with android 4.0, Samsung seems to have been very sloppy and left the /cache partition huge to accomodate the froyo standard. This is a waste of space that will never be used. The cache paritition is 0.5GB. Is it OK if I include this script as a boot script? Is 0.5GB/500MB enough for most peoples' dalvik-cache? This will free up that space and add it to the internal sd card.
Click to expand...
Click to collapse
Many thanks for this!
"Disable HW overlays"- for some reason this setting does not stick between reboots (not your ROM problem- it happens in all devices that I've ever seen). Is there a way to apply it automatically during or after boot? Such as in a script, or init settings etc?
Regarding the Dalvik cache, is there a way to know how much space all my installed apps + system are currently using?
jaibar said:
Regarding the Dalvik cache, is there a way to know how much space all my installed apps + system are currently using?
Click to expand...
Click to collapse
Go to the CM File Manager --> Settings --> General Settings -> Compute folder statistics and check mark that box. Also in the same area be sure to set access mode to prompt user mode or root access mode. Then, go to /data and hold dalvik-cache folder until get a menu and choose properties. The size will show up under "Size: ". Mine is 208mb.
AAccount said:
Go to the CM File Manager --> Settings --> General Settings -> Compute folder statistics and check mark that box. Also in the same area be sure to set access mode to prompt user mode or root access mode. Then, go to /data and hold dalvik-cache folder until get a menu and choose properties. The size will show up under "Size: ". Mine is 208mb.
Click to expand...
Click to collapse
238MB here. Maybe a quick poll can help gather info on how much allocation must users are using?
Sent from my GT-P7510 using Tapatalk
jaibar said:
238MB here. Maybe a quick poll can help gather info on how much allocation must users are using?
Sent from my GT-P7510 using Tapatalk
Click to expand...
Click to collapse
Same around 2xx mb. I'm fine with it, since the 400mb in /cache is wasted anyway.
Sent from my GT-P7500 using Tapatalk
223MB here
Is Netflix working on this ROM. Asking because there is problems on the Nameless ROM.
Sendt fra min GT-I9305 med Tapatalk
thra1982 said:
Is Netflix working on this ROM. Asking because there is problems on the Nameless ROM.
Click to expand...
Click to collapse
Every time somebody asks about Netflix... I fell I'm missing something big...
NEW EASY INSTALLER, RECOVERY ZIP
Total overhaul of code.
*HELP WANTED, PM FOR RELEVANT DETAILS*
This software package was originally just made for my personal use to rectify the issue of my phone not entering deep sleep when idle and me not having access to a charger for the majority of the day while also improving multitasking because being my phone is also my build environment/office environment, I am frequently jumping around various apps that I'd prefer to keep open.
Things this package accomplishes on your phone (very simple and brief summary):
*Forces entry into deep sleep as soon as the screen is off (if enabled, on by default). It also has audio detection so you can listen to music with the screen off without unwanted deep sleep entry.
*Improves multitasking, no more apps having to reload/redraw when you switch back to them.
*Automatic odexing of all apps, including new installs (if enabled, pre-lollipop ROM's).
*Easy management of swap.
*CPU management. You can set your own values to be locked (no other app can change them) or let its device manager automatically set CPU frequencies and the governor you specify.
*Dynamic Max CPU Freq: When enabled (on by default) it will automatically scale the max CPU frequency value depending on the CPU load. This can help with governors that favor the high end of the frequency table too much by allowing you to save battery but have the CPU power available when needed, without having to adjust anything manually whenever you go from doing something processor demanding to having your phone sit idle.
*Fixes issues with several kernels where the touch screen is unresponsive after waking the device. No more inconvenient force reboots.
*Enables all idle and suspend states available (they are disabled by default quite often) and can help get your device into the lower C-States.
*Fixes broken links to firmware files caused by buggy init scripts on some ROM's.
New/Other features:
*New recovery flashable installer
*Force system wide GPU rendering and faster framerate.
*Fixes Dt2w and Sw2w lock screen freeze bug.
*Now compatible with KSM.
*Faster app loading and responsiveness. Key android services are given priority status for I/O and CPU resources.
*Multitask over 20+ apps simultaneously without any redraws and low-latency app switching (provided you have the swap space)
Tip: I use the large amount of unused space on /system to increase the size of that MaxOpt managed swapfile.
*Fixed the crash on boot issue between MaxOpt and some kernels.
Default MaxOpt config:
•Swap on, default MaxOpt generated swapfile size is 64 MB, with one made on /data, one on /cache, and one on /system if mounted rw.
•Auto-odexing off.
•Hotplugging compatibility on.
•User CPU settings off, auto-device manager on.
•Deep Sleep immediately on screen off enabled.
•KSM off (you must have a kernel that supports it to enable this option and have it work).
•Kernel settings on.
•Everything is forced to be drawn by the GPU.
All of the above listed features are user optional/tuneable.
For those who wish to only use MaxOpt for fixing the lock screen freeze bug associated with some kernels/DT2W/S2W use the following link: http://forum.xda-developers.com/showthread.php?t=3061589
If you would like to just use individual components or adjust program settings from a terminal app, here is an example usage and description of their individual functions as well as other useful documentation (VERY OLD DOC, NEEDS LOTS OF UPDATES):https://docs.google.com/file/d/0B_hgNZE_j5sVbEN4ZUtkS2p0bW8/edit?usp=docslist_api
Terminal Emulator is what I would recommend for use with managing MaxOpts' settings.
System Requirements (not entirely sure due to lack of public testing):
Busybox
A terminal app
A kernel that can best be utilized by these programs.
Please make a nandroid backup before using.
And here is the MaxOpt installer ( R2 1.0.6 ):
* https://drive.google.com/file/d/0B_hgNZE_j5sVaGdxV0FfODdxbVU/view?usp=docslist_api
Changelog:
R2 v1.0.6- Adjustments to write buffering and multitasking memory performance.
R2 v1.0.5a- Fixed a bug present in both this project and MaxLife where data wasn't validated thoroughly enough before using it.
R2 v1.0.5- Added a new completely experimental new user tuneable (on/off, default off) that changes runtime memory allocation values. Only activate it if you have a large amount of swap.
R2 v1.0.0- Totally rebuilt the project, installable with a recovery flashable zip now, kernel image installer is no longer compatible and is scrapped.
For those still getting crashes:
The issue still appears to be related to the device radio when it happens, so, after a crash could you please force reboot your device and try to disable mobile data when it boots before it crashes again and please post a copy of /proc/last_kmesg. Thank you.
Screenshots of battery screen showing time spent in sleep:
https://docs.google.com/file/d/0B_hgNZE_j5sVSjRUU0ZlX0UwUWc/edit?usp=docslist_api
https://docs.google.com/file/d/0B_hgNZE_j5sVSmNjYThkUzAtNGM/edit?usp=docslist_api
https://docs.google.com/file/d/0B_hgNZE_j5sVcWxJd0JyV09nMDA/edit?usp=docslist_api
Please thank if my software has helped you and please leave logs and descriptions of problems if my software did not work for you.
Wow, this looks amazing. Very nice work.
I Will be playing with this for the next few days.
Sent from my Moto G using Tapatalk
Damn this looks complicated as hell haha. Good job OP
Very nice job
Thank you very much everyone. Glad for the positive feedback, this is my first public software release. I daylight in a machine shop, so this was far from my field of expertise and a long learning experience for me
I tried it on faux kernel 014m.
But my phone bootlooped
I have faux clock app.
Is it causing the problem?
Thanks
One possible problem could be the boot image it made was over 10 MB depending on the size of the input one. If that wasn't the issue, did you disable signature checking? Also this is currently not ART compatible. It is also important that you run the installer from a partition that supports octal permissions, so the emulated sdcard is a no go.
Edit: it may be worth trying disabling the faux clock app too. I don't have that kernel or app to try for myself but this mod does affect CPU settings so it could be a conflict. If none of those work, I may have to look into updating my installer with an alternate method for incompatible kernels.
elrod16 said:
One possible problem could be the boot image it made was over 10 MB depending on the size of the input one. If that wasn't the issue, did you disable signature checking? Also this is currently not ART compatible. It is also important that you run the installer from a partition that supports octal permissions, so the emulated sdcard is a no go.
Edit: it may be worth trying disabling the faux clock app too. I don't have that kernel or app to try for myself but this mod does affect CPU settings so it could be a conflict. If none of those work, I may have to look into updating my installer with an alternate method for incompatible kernels.
Click to expand...
Click to collapse
I followed steps as below:
I put that 2 files in the data partition.
Then boot.img of faux.
I set permission 755 for both files and boot.img
Then from terminal I executed the command.
I got new_image.img
I repack the zip using this new boot image and flashed it in recovery.
Then I reboot.
Phone booted and stuck on "optimizing apps 1 of 98"
Then again same.
Also I had 700mb of free memory when I tried this.
When I again booted using faux kernel I had 450mb of free memory.
Can you guess what's going wrong?
Did you disable APK signature checking?
elrod16 said:
Did you disable APK signature checking?
Click to expand...
Click to collapse
Sorry I forgot that.
Where exactly should I put those 2 files.
Was I doing right to put them in data partition?
And after first boot can I enable signature verification?
Do I need to disable it before every boot?
Unfortunately for now it needs to be off whenever an app is upgraded or added, but can be enabled after the reboot that that happens on, and yeah, /data works
Even after disabling signature verification it doesn't work on faux boot.img
Am I doing right?
For whatever reason it sounds like the dexy binary isn't playing well with your phone, I'll make a new installer with the option of disabling it for incompatible setups for the time being, but the other ones should still work. I'll keep ya posted.
My rom is stock 4.4.4
I will try again with disabled optimization.
kedar512 said:
My rom is stock 4.4.4
I will try again with disabled optimization.
Click to expand...
Click to collapse
OK, hopefully that should be the only part of this package not working for ya. Keep me posted, I'll continue trying to figure this out if it persists.
elrod16 said:
OK, hopefully that should be the only part of this package not working for ya. Keep me posted, I'll continue trying to figure this out if it persists.
Click to expand...
Click to collapse
No luck bro
Same problem.Stuck at optimization.
Should I try it on Xperience kernel?
Its not working with faux.
kedar512 said:
No luck bro
Same problem.Stuck at optimization.
Should I try it on Xperience kernel?
Its not working with faux.
Click to expand...
Click to collapse
I would say yeah, try it with it and see if it makes a difference
Also did you try the new build with a clean restore? (Before any of the failed install attempts) Try not wiping the cache/dalvik-cache after install and flash.
I tried again but this time booted upto lock screen and rebooted.
I tried with new build.
after placing ./maxopt boot.img appears running with dexy enabled.
That means it's already working? If yes, have to do anything else?
Every time you turn the meter will have to repeat the procedure?
Sorry my bad english
Just a heads up for all of those who get the dreaded "Incompatible Aliyun OS" message:
I just bought an Elephone P6000 which runs on the new Mediatek 6732 with Mali T760 GPU and comes with Android 4.4.4 (Update to Lollipop via OTA announced). This baby runs incredibly smooth, but that's not the purpose of this post.
I downloaded Xposed Installer 2.7 beta and got the Aliyun notification. Since the programmer was nice enough to include some safety features to save overzealous noobs from rash decisions, I decided to test this for the heck of it. I switched to ART and let the installer run its course, fully expecting to have to use the emergency exit from a bootloop.
But, waddayaknow, the phone started up and everything seems to be working. Ok, Xposed switched back to DALVIK but that was expected, too. GravityBox is working, everything cool. So MAYBE the bloody Aliyun problem only applies to JellyBean?
Does ART stick?
Poppeye0 said:
I downloaded Xposed Installer 2.7 beta and got the Aliyun notification. Since the programmer was nice enough to include some safety features to save overzealous noobs from rash decisions, I decided to test this for the heck of it. I switched to ART and let the installer run its course, fully expecting to have to use the emergency exit from a bootloop.
Click to expand...
Click to collapse
@Poppeye0 - I too have a P6000 but when I switch to ART and reboot, the phone has switched back to Dalvik - did you check whether your ART-iness had stuck? I have read elsewhere that de-odexing can help with Aliyun problems, but the procedure seems to be quite a pain. I have de-odexed using Tibu Pro, but the system/framework directory is not deodexed by Tibu.
I am tempted to just give it a try - I have TWRP installed and have backups of my ROM, so recovery should not be too hard.
Reading the OP on the 2.7 beta, it says this:
I have just uploaded a test version of Xposed Installer.
It doesn't have anything to do with ART!!!
Click to expand...
Click to collapse
Just tried it out
And it works on my P6000 too. Didn't try to switch to ART, but did de-odex with TiBu Pro first. Gravity Box KK works perfectly (apart from reordering of Quck Setting tiles - that's a problem I have on another KK device anyway).
Hoorah!
If you just delete the .jex files the "Incompatible Aliyun OS" will go away.
The switch to art isn't working for me either but Xposed doesn't 100% work well with art anyway.
Xposed itself switches back to DALVIK. Xposed 2.7 should install without deodexing on the P6000.
Renaming all the .jex files worked for me on my Android/Aliyun 4.2.2 MT6592 system. No deodexing. The current XPosed and Amplify are now running OK. I have the little microcpu app running in the top corner of the display and it was the first time I've seen all 8 cores banging away when Amplify did its initial sorting out of the machine. Mind you, I've only had the phone for a day....
i got that message too and im kinda scared to push it though
I have owned the Moto G 2014 since January. I like the phone but get very frustrated at how it slows down excessively. I am running Lollipop 5.0.2 which I received OTA bere in the USA. After I downloaded Lollipop, I did a full factory reset on the phone to make sure everything was cleared out. One of the major problems I am having is downloading apps and updating apps from the Play Store. The download time takes WAY longer than on any of my devices that are attached to the same network. Once the app or update downloads, it again take three or four times as long to install as on my other devices (including a Nexus 7 running Lollipop. Any ideas out there. I like the phone but it gets SO LAGGY and SLOW.
Clearing the dalvik cache may help.
Go to Settings > Apps > All > Download Manager > Clear Data and Cache and restart the phone. Then go to Playstore and download the apps.
Lollipop uses ART as compared to Kitkat which uses Dalvik VM. Google for the differences
ART (Ahead of Time) compiles the bytecode before execution as compared to Dalvik (Just In Time) which compiles it during run-time.
So at the time of installation apps take a bit to install as compared to Kitkat.