yashsingh1/xdaforums huggingface dataset:
[Nexus 7 Q&A, Help & Troubleshooting] FormerSlacker:
Did a full wipe and flash on my 32GB unit and I must say it's quite a bit faster than stock Kitkat on my unit. Can't wait for f2fs support.
[Nexus 7 Q&A, Help & Troubleshooting] joaopaulo_:
Well... All my game list is unplayable with 5.0. I don't know... Maybe laggy is caused by apps not optimized for art. When I uninstall Facebook and messenger I get a great performance.

I don't understand why google not upgrade the kernel to 3.4...
[Nexus 7 Q&A, Help & Troubleshooting] RocketOptics:
I flashed the image using NRT 1.9.3 and got a lot of lag ... 2-3 seconds to launch apps, screen transitions were very slow. I did a factory reset and things are better now, similar performance to prior to update.

Factory Reset worked for me.

Edit: 16GB, dirty flash official image LRX21P w/ NRT 1.9.3, rooted w/ NRT.
[Nexus 7 Q&A, Help & Troubleshooting] vo4LG:
Interesting; I might reflash and try a factory reset.

It would be cool if people could also post the model (8GB, 16GB, 32GB), what they flashed (i.e. official .img files or a custom build from here on XDA) and whether they did a full flash (i.e. ./flash-all.sh) or a dirty flash.

I did a full flash on a 32GB model using official images and the performance was terrible from the very beginning, whereas back on CM11 with F2FS the performance is really good.

I will try doing a full flash again and then a factory reset just in case that makes a difference.
[Nexus 7 Q&A, Help & Troubleshooting] tronmech:
Well, I'm seeing some improvements by letting it settle in. Maybe ART needs time to learn.

For the record:

Nexus 7 16gb

3 flash attempts

1) dirty flash of system, with wipe of cache & dalvik. (From Dirty Unicorn rom)

2) wiped cache and data in fastboot, then manually flashed data and system. Wound up with an 8gb tablet. (NO idea how that happened)

3) ran flash-all.bat
[Nexus 7 Q&A, Help & Troubleshooting] milkk:
Mine was laggy when I first installed it then I left it for a while and when I came back I rebooted it and since then no issues runs as smooth as a factory rom can work on old hardware with no custom roms/kernels. It actually runs better than I though it would but horsepower tells the tale because I also just upgraded our work test device Nexus 7 2013 to lollipop and wow that thing flies compared to this. I'm just glad a device this old gets the upgrade and even nexus 4 because I got a asus transformer and then never got past 4.2 and that was a top of the line device (tf700) now it's a freaking expensive picture views lol that's about all it's good for.
[Nexus 7 Q&A, Help & Troubleshooting] Mockingbird:
Yeah, I'm pretty dissapointed with it too. This time it took google to release an android version around 1 year...you'd think that with all the developer previews, apps would be more optimised for lollipop.
[Nexus 7 Q&A, Help & Troubleshooting] GtrCraft:
Do a factory reset in stock recovery, then you will get your whole storage. And it makes it faster
[Nexus 7 Q&A, Help & Troubleshooting] DoNuT_1985:
Mine goes from super-smooth (and remarkably better than KitKat ) to annoyingly unresponsive behavior just in a minute. It did a clean flash from factory image and the only thing I've changed is flashing a root kernel using NRT 1.9.4, even getting app freezes from time to time, even Google Search.

Are there some issues with rooting Android L so far? My Nexus 5 goes like hell with Lollipop and no issues whatsoever.

Had the 4.4.4 factory image running before (clean flash with full wipe) and it wasn't perfect either, especially in Chrome browser...
[Nexus 7 Q&A, Help & Troubleshooting] YellowMango:
just switched to the default launcher and found it to be much smoother
[Nexus 7 Q&A, Help & Troubleshooting] toastido:
I had serious lagging issues with it when I first installed. I then wiped all the partitions (except bootloader) and re-flashed and set up device as a new device, and it has performed flawlessly since, even with the Google Now Launcher.
[Nexus 7 Q&A, Help & Troubleshooting] anastatow:
Lollipop has breathed new life into this old tablet. Just running stock at the moment and haven't experienced any lag. Games feel smoother at higher settings and haven't encountered any problems yet. Hopefully this holds up!
[Nexus 7 Q&A, Help & Troubleshooting] dgattenb:
It took mine when it I went to 4.4.4 about a week to "calm" down. After the lag had gone and it was perfect ....
[Nexus 7 Q&A, Help & Troubleshooting] C0derbear:
Full wipe and flash all on my 32gb WiFi model, seems fine. Definitely on par with how CM11 was running.

I don't game though, kindle, zinio, Facebook, chrome, Tapatalk, and mapping apps are my primary use.

Lag will happen big time on first startup though, or if too memory loaded. Feels just like Windows 7 on a 2 GB ram system if you get my meaning ... So long as you stay in memory limits is OK, but swapping to disk hurts big time.

If the N7 had more ram it would probably be hugely better. Later gen devices benefit big time from bigger ram and hugely faster flash ram.
[Nexus 7 Q&A, Help & Troubleshooting] funtomi:
Updated via OTA (sideload) 265aps and speed is +/- like 4.4.4
[Nexus 7 Q&A, Help & Troubleshooting] philippecr:
hem.... anybody notice that Nexus 7 2012 is not using the ART runtime? I used the "ART Checker" app and it's written Dalvik.....
[Nexus 7 Q&A, Help & Troubleshooting] KevinouILG:
I've done the same, and for me it don't use my local DNS server... and it's very annoying because I use it to resolve service inside our private network, so they are unreachable right now.

I've opened an issue on the android tracker : https://code.google.com/p/android/issues/detail?id=79504
[Nexus 7 Q&A, Help & Troubleshooting] gizzmoffm:
It definitely runs on ART, because:

- Apps installation takes much longer

- App size is much bigger (Facebook generates about 150MB of App Data during first start which also takes quite a long time, on Dalvik that's just about 50MB)

- There is no libdvm.so, but a libart.so

- logcat shows many "art" entries

So your tool is wrong.
[Nexus 7 Q&A, Help & Troubleshooting] bftb0:
F this release.

Seizes up frequently, or gets so slow that screen touches are delayed by 4 or 5 seconds. Twice this morning it froze & rebooted, claiming to be out of memory and even more mind-blowing: that the OOM killer ran but could find absolutely nothing to harvest.

The 2nd time was in the middle of a detailed post here about the care I took in erasing (boot, recovery, cache, system, userdata), formatting (cache/system/user data), and flashing the Google LRX21P images. (Skip flash of userdata.img as this causes the "6 GB data partition bug").

The CM 10.2 nightly I was on for the last year would get choppy, but nothing like this. Same set of (market) apps.

I had the most recent KK stock release on the tablet for a couple of days ... in about the same amount of time it experienced none of these behaviors.

Uh-oh... slowing down, I better post *now*.
[Nexus 7 Q&A, Help & Troubleshooting] suchavibrantthang:
This release is is pretty laggy so far. Should've stayed on cm11 till the bugs get worked put. Just gotta be patient. We've always been beta testers for google and this release is no different from any other. Stop complaining so much, you're fueling crapple fanboys! I've noticed a huge battery life and standby performance. Before I would never get 2-3days of standby. It would drain while sleeping and have issues recharging from dead battery state.

Will wait for CM to cook up some performance tweaks and give that a run.
[Nexus 7 Q&A, Help & Troubleshooting] 19dragon98:
This is why Grouper is so laggy, watch system free memory...
[Nexus 7 Q&A, Help & Troubleshooting] bftb0:
Ummmm ... what that app/picture is showing is that the /system mount point (file system) is full. (Note the "MMC" designation)

That would be a huge problem if anything was trying to WRITE to that filesystem, but it's a read-only filesystem. Unrelated; the Android /system filesystem is usually quite full on most stock ROMs.

(Note your image shows 420+ MB of "free" RAM.)

.
[Nexus 7 Q&A, Help & Troubleshooting] Monfro:
HTC ONE M8 users that are running GPE leak think there is some sort of memory leak: after you run some memory intensive apps, ram is not correctly freed, so this means slow down and lag.
[Nexus 7 Q&A, Help & Troubleshooting] TXKSSnapper:
I'm pretty sure that "ART Checker" isn't compatible with 5.0 and will always report not ART.
[Nexus 7 Q&A, Help & Troubleshooting] tedkunich:
Yep... Two clean installs later and I'm back on 4.4.4. The lag/unresponsiveness was infuriating at best. I like the look and feel of the OS, but IMHO it is not usable with the slowdowns.

T
[Nexus 7 Q&A, Help & Troubleshooting] bftb0:
[MENTION=3395887]suchavibrantthang[/MENTION]

LOL. I was responding to your post (on the tablet w/5.0, using Chrome) and touched the del key to backspace. The tablet made a noise like a machine gun - as if I had pressed "del" 10,000 times. Since the cursor was about halfway through the post, I thought "well, there goes half my post".

But I was wrong - three seconds later the tablet rebooted, so I lost the whole post. :( Three reboots in one day - enough is enough, this poor POS is gone. (Mind you this is on a well-taken care of tablet, never OC'ed, never even a whiff of hardware trouble even once)

Now I'm on a different computer while I restore back to KTU84P (rooted) Stock.

Do you have a favorite CM11 release? I care mostly about stability and predictability of performance, not tweaking or theming (e.g. I don't OC or fool with governors). It would be nice if USB OTG was well supported, and the ability to use the tablet as an NDIS client would also be nice. I stayed on CM10.2 for nearly a year, mostly because ad-hoc WiFi got dropped from CM10.2 -> CM11 & my old Android phone could only do ad-hoc Wifi Hotspot. But that's ancient history now - newer Android phablet.

I don't really care what other people use. I just want releases to improve my experience, not go back to the days of Eclair and Froyo.

Call me a realist - the Linux kernel is quite mature & new kernels will at best have essentially identical performance (using the same clocking scheme & rate governors), so at best I expect some functional improvement in the middleware stack - not a degradation of past reliability. Unfortunately the OOM paradigm is central to the Android application life-cycle management, so if it doesn't work, then someone needs to be the squeaky wheel.

I suppose a kernel memory leak (mentioned above) could be behind the "nothing available to OOM harvest" kernel death penalty. I've never seen this before on any Android device - including the Eris, which had a tiny amount of RAM (192 MB iirc). If you got the OOM parameters wrong on that thing, the device would thrash continuously (harvest/re-start/harvest) - but the kernel wouldn't panic out.

cheers
[Nexus 7 Q&A, Help & Troubleshooting] KiljoyMcCoy:
I'm finding it to be much better than kk.

I did do a factory reset and manually wiped and repaired partitions in recovery.

Only problem I'm having is the WiFi range \strength is weak.
[Nexus 7 Q&A, Help & Troubleshooting] ZEII:
How you wipe and repair partition?

Do you use TWRP to wipe?

thank.
[Nexus 7 Q&A, Help & Troubleshooting] Shivam Kuchhal:
Just had a failed attempt to use F2FS on lollipop.

My steps-

Format all partitions to F2FS

Replace stock lollipop zImage with oxydo kernel zImage and changed fstab accordingly.

Flashed new boot.img and system.img accordingly.

Rebooted into recovery to find out that flashing system.img changed system partition back to ext4.

Changed system mount point back to ext4 in fstab and flashed boot.img(cache and data still F2FS).

Infinite bootloop.

Any help or points? Or should we all wait for flashable ROMs. I really want to stick to factory images with F2FS because of studies. :(

[MENTION=2687601]Metallice[/MENTION] [MENTION=2743057]legolas93[/MENTION] [MENTION=5501864]USBhost[/MENTION] [MENTION=4693882]HTCDreamOn[/MENTION] [MENTION=4394172]sgt. meow[/MENTION] I think you guys can help maybe?
[Nexus 7 Q&A, Help & Troubleshooting] USBhost:
Did doxydo kernel support f2fs? Was it updated to L

Did you get a boot animation?

Also dont know if this is of any relevance

But lollipop won't boot with SELinux set to disabled on the Nexus 9

Don't know if its the same with the Nexus 7
[Nexus 7 Q&A, Help & Troubleshooting] RaphiAoC:
I installed the factory image two times. The first time according to a wild "how to install a factory image guide" I found on google... The result was annoying. The whole system was very slow... it was unusable.

So I decided to try it again with the simple guide from Google.

Now without the manual wiping of partitions an separate flashing of the zip parts my Nexus 7 is usable! I have no clue why because at the end of the day both ways delivered a clean installed OS but now it is significant faster.
[Nexus 7 Q&A, Help & Troubleshooting] Shivam Kuchhal:
Oxydo has F2FS support. It isn't updated to latest branch but it boots just fine. Also lollipop boots with selinux disabled. And yes I got a bootanimation.
[Nexus 7 Q&A, Help & Troubleshooting] USBhost:
Ok so system is being read thats good

Do you get adb
[Nexus 7 Q&A, Help & Troubleshooting] HTCDreamOn:
I take it you're using the new ramdisk from the new L boot.img? I'll be syncing Google's updated tegra kernel source soon to update my nv-3.1 kernel but I can compile Google's branch with no modifications other than F2FS for you to try.
[Nexus 7 Q&A, Help & Troubleshooting] Shivam Kuchhal:
Yes, I did use ramdisk from lollipop. Also I used oxydo because I knew that it works with lollipop(I tried it earlier). Still I'll wait for your boot.img. There aren't much changes in lollipop from kitkat branch though.
[Nexus 7 Q&A, Help & Troubleshooting] Gaheris:
I'm very disappointed by Lollipop. The N7 has become very sluggsish, noticeably slower than KK. Besides, I do not understand all the rage about 5.0. The few features which are new are neglectable. I hope that Custom Roms will be able to make me happier about 5.0
[Nexus 7 Q&A, Help & Troubleshooting] Bl4ckX:
So actually Lollipop on my Nexus 7 is the worst. Its always laggy, freezes almost everytime when opening an app etc. Its basically unusable.

Did a complete wipe using the flash-all.bat and the device is not rooted.
[Nexus 7 Q&A, Help & Troubleshooting] gogol:
I think the problem might be ART runtime.

I switched back to SlimKat f2fs and the performance is like night and day. No lag, no janky compare to Lollipop.

Then I switched to ART, and it was also a bit laggy and janky on opening / switching apps. But, not as laggy as Lollipop.

So, now back to Slimkat f2fs and Dalvik.

Happy, I don't miss any new feature of Lollipop!~
[Nexus 7 Q&A, Help & Troubleshooting] greensheep:
lollipop on nexus 7 has a beautiful UI, but it is too slow.... laggy.... google what are you doing?!?!?! I am very very very disappointed .....
[Nexus 7 Q&A, Help & Troubleshooting] Tmzdroid:
Im seeing a lot of people are disappointed with 5.0 Lollipop on here. I did a fresh clean install using the wugfresh NRT and have had none of the performance issues mentioned. My Nexus 7 is running better than ever, just hoping it will stay like this once the memory starts filling up. Big Thumbup to Google for supporting the Nexus 7 for 2+ years:good:
[Nexus 7 Q&A, Help & Troubleshooting] everesee:
I think performance is very good. The only problem is stock kernel, so i'm using nvidia 3.1 kernel alpha 0.5 now. This fixed all of stupid lags. The only problem of art; when installing an app on google play, rom starts lagging like a crazy! I know this is not our hardware's problem, it's source is ART :o
[Nexus 7 Q&A, Help & Troubleshooting] abobobilly:
[MENTION=5008705]Gaheris[/MENTION]! The reason for sluggish performance is the crappy NAND of our Nexus 7. However, i have observed (and experimented) that if you Erase System (using ADB) and (CLEAN) Flash the Factory Image (basically do a CLEAN flash overall) ... the device performs beautifully well.

If you keep your data coming from Kit Kat, thats when you face the most problems.
[Nexus 7 Q&A, Help & Troubleshooting] Skyrocketing:
My performance is absolutely terrible. About half of the time, there will be a 3-5 second delay opening apps, and at its worst, much much longer. Most of the system is laggy, though there are times when it works fine, probably 40% of the time. This is a clean flash then factory reset all stock.
[Nexus 7 Q&A, Help & Troubleshooting] dpdurst:
I couldn't be happier with Lollipop on both of mine, the 2012 and 2013 version. 5.0 runs like a champ and IMO much better than KitKat did. I'm not using any kernel but the one that came with it and not overclocked at all.
[Nexus 7 Q&A, Help & Troubleshooting] Tomaxda:
Wow, I think your experience is not the norm.

I did a fresh install of lollipop on my Nexus 7 (2012 wifi) and it became even slower then before - pretty much unusable now.

I think its finally time for me to give up on stock and try slimbean with f2fs (which seems to be the recommended option for slow N7's now).
[Nexus 7 Q&A, Help & Troubleshooting] xQuestx:
I was having very bad lag problems till I used nexus root toolkit 1.9.6 with the flash stock and selected 5.0. So far it seems fast now, and not exhibiting the problems from before.
[Nexus 7 Q&A, Help & Troubleshooting] KiljoyMcCoy:
Yes I used twrp to wipe and repair before doing a full install. I did install twice since first time was showing 6gig free. I also did not restore anything.
[Nexus 7 Q&A, Help & Troubleshooting] Shivam Kuchhal:
Okay, had another failed attempt to boot lollipop with F2FS

Here are the steps this time-

Changed updater script of this ROM to work with F2FS.

Compiled a kernel using lollipop branch by Google with added F2FS and kexec support and edited F2FS accordingly. Here's what my edited fstab looks like-

Flashed ROM zip(with new kernel) in TWRP.

Stuck at Google logo for a while and then it rebooted into recovery.

Tried compiling my kernel with Linaro 4.9 and GCC 4.7 both and tried flashing oxydo too.

I think I am missing onto some small thing. :/

Tried flashing my kernel with stock ramdisk on ext4 and it booted just fine!

[MENTION=4693882]HTCDreamOn[/MENTION] [MENTION=5501864]USBhost[/MENTION] [MENTION=2687658]bshiznit[/MENTION] any ideas guys?
[Nexus 7 Q&A, Help & Troubleshooting] steviemch:
Clean flash of the official image on my 32gb grouper and I don't have the lag others are describing. After flashing I booted into the stock recovery and wiped cache and performed a factory reset (I always get the decreased storage bug so it's something I do each time I flash the factory images.) All in all the performance is better than kk. My problem is regarding root, I rooted manually with the modified boot img and SuperSU 2.19, flashed with latest TWRP. Root works but certain apps show the pie error in su logs and obviously don't work as expected. I tried the pie patch that's kicking about XDA, with no joy. TWRP is also behaving strangely, failing to restore backups, or if it does restore, somehow erasing the SD card or changing default storage to /emulated/0. TLDR, lollipop for me is an improvement in terms of responsiveness and also battery life, but a pain in the ass for recovery and root. And there seems to be no fix.

Sent by Borg neural subspace transceiver node.
[Nexus 7 Q&A, Help & Troubleshooting] HTCDreamOn:
Those wanting F2FS, I've merged the latest lollipop updates into my nv-3.1 kernel and it's working fine on EXT4 but it has F2FS support too so you might wanna give that a go. If it doesn't work then it's most likely a problem in the ROM rather than the kernel.
[Nexus 7 Q&A, Help & Troubleshooting] KiljoyMcCoy:
F2FS all?
[Nexus 7 Q&A, Help & Troubleshooting] HTCDreamOn:
Yeah, although I don't think this has anything to do with the kernel. The f2fs patches for the kernel simply add support for the f2fs filesystem, it doesn't care where your using f2fs. I use agnostic flasher anyway which detects which partitions are what so I'll work with ext4, f2fs data and f2fs all (assuming it works with f2fs on lollipop at all that is)
[Nexus 7 Q&A, Help & Troubleshooting] scotth324:
I had the lag everyone was reporting when I first flashed the system image with NRT it wiped everything but was still very slow. So I went into recovery and wiped cache then did factory reset from recovery and started from scratch and now everything is working almost as good as when it was on 4.1.2. Works really well now. All the same apps installed using it the same. So there is something to try for those of you with unbearable lag. And I had the unbearable lag before I wiped cache and factory reset again.
[Nexus 7 Q&A, Help & Troubleshooting] ZEII:
Excuse me.

How to wipe cache in Stock recovery?

Thanks for advice.
[Nexus 7 Q&A, Help & Troubleshooting] treefrog20012003:
Lollipop Performance

I have to say that I have had a really bad experience with the update to 5.0. I did a clean install, did not back anything up or restore anything, installed all of the apps fresh, did a factory reset to clear the storage issue, wiped cache after reboot and once I started to use my apps the lag started. It finally came to the point that I force rebooted it cause it stopped working and then went into a boot loop. Force restarted it and got into the recovery wiped cache and dalvik and let it reboot and it upgraded apps again. I think I will go back to KitKat until the apps get updated to fix the problems because I think that there are memory leaks from some of them. I like the way 5.0 looks and runs but the apps may be updated to work but I don't think all of the kinks are worked out yet.:(
[Nexus 7 Q&A, Help & Troubleshooting] DroidOnRoids:
It's such a shame. If this tablet had higher performing nand storage speeds, this tablet would still be a joy to use in 2014.

Animations are smooth at times but 60 frames throughout is just not going to happen on this tablet :crying:
[Nexus 7 Q&A, Help & Troubleshooting] naoentrar:
I wah hoping my tablet would have a "new life" with lollipop update but it is the same as kitkat. It blows my mind how slow it is sometimes. I can get almost 10 seconds delay between pressing a button and actually doing something.

The solution is go back to 4.1.2 or even 4.2.2 and the tablet feels snappy again. I though updates were supposted to increase user experience, not in this case.

Shame
[Nexus 7 Q&A, Help & Troubleshooting] Shivam Kuchhal:
In case anyone wants a kernel compatible with F2FS and lollipop having useful stuff, go here- http://xdaforums.com/showpost.php?p=56818558&postcount=510
[Nexus 7 Q&A, Help & Troubleshooting] KiljoyMcCoy:
I assume you did something wrong. Did you do a complete wipe? If coming from F2FS do a repair on each partition? Try doing a complete new install with out restoring apps. ( I found even on Nexus 5 restoring apps from non ART backups seems to cause problems.Install google now launcher from the store? Use adb for installing not NRT.

I still use grouper for everything I run on my Nexus 5. do run adaway and seeder. Nothing else non stock.

Lollipop is smooth, no lag at all on my 2 groupers. Way better than KK. KK with all F2FS is slightly snmoother but not worth going back to..
[Nexus 7 Q&A, Help & Troubleshooting] nikatapi:
Well for me performance was a mixed bag, sometimes it was snappy, but other times lag was unbearable. Back to KitKat at least for now, i hope some kerners or f2fs custom roms will improve the performance, but for now it is not very usable.
[Nexus 7 Q&A, Help & Troubleshooting] naoentrar:
I used f2fs some time ago but I did not feel it improved the performance that much so I went back to stock kitkat. I never did that repair partitions thing, didn't know it was needed. But I restored a backup from 4.2.2 and my nexus is as smooth as the first day I used it so I don't think the lag on lollipop and kitkat is due to repair partitions.

Thank you