yashsingh1/xdaforums huggingface dataset:
[Nexus 7 (2013) General] lomonic:
Installed KitKat and repatched supersu 1.69 earlier and unlocked sfhubs patches prior to install with a few reboots to be sure. So I should be on the new touch software that came with KitKat. Initial reboot does take a while on the preloading screen with Google on it, but once you see the new animation instead of the X, ur on your way.

Been playing around for about 20 to 30 mins and including typing this message entire in chrome! I have to say I'm very satisfied at the moment with the new touch software. I've not experienced a stucked key so far, Google maps works well with rotation and zooming. So far so good. Only thing I'm getting used to is the new location of the full stop and question mark key as per the new keyboard updates.

Gonna test it further with sone touch sensitive games and report back if things differ after extended usage. Fingers crossed. :angel:

---------- Post added at 01:09 PM ---------- Previous post was at 01:07 PM ----------

I tried YouTube after reading your post and it worked well for me! I skipped, and move forwards and backwards and all worked smoothy and well. Try rebooting?
[Nexus 7 (2013) General] Misledz:
Can't seem to get SuperSU to work it always force closes on 1.69
[Nexus 7 (2013) General] JassyNL:
How is GPS on this build ?
[Nexus 7 (2013) General] sfhub:
I assume others are running 1.69 without issues. Personally I am running 1.55 so I can say for sure it isn't FCing. Link to 1.55 is available in the first post.
[Nexus 7 (2013) General] lomonic:
No issues with gps that I've noticed so far. What were the old problems?

As for supersu 1.69 I hv no issues thou

Try installing again?

I just tried out some touch sensitive games and I'm so far happy with the results. Need more testing to be done.
[Nexus 7 (2013) General] sfhub:
I saw some dead patches in the unit I am testing with.

On previous releases I would see dead spots for both sliding and tapping. On this release, sliding is always fine, but tapping using the landscape keyboard will occasionally just not respond to touches in certain areas. It isn't the landscape keyboard per-se, but the top 1/3 of the screen, which happens to be the left side of the keyboard in one of the landscape orientations.

I think the touchscreen software included will behave differently for different screens just like previous releases. For some it will fix, for others there will still be lingering issues.
[Nexus 7 (2013) General] sfhub:
GPS works ok for me. It has been fixed for a while though, I believe in JSS15R (or it might have been JSS15Q).

They changed the icon in the status bar and I don't believe it blinks anymore to indicate searching. Also the icon is on the right side of the status bar whereas it used to be on the left.
[Nexus 7 (2013) General] lomonic:
sliding woks well, multi touch and typing works good for me. i'm gonna test a lil more on the top 1/3 of the screen but based on the game i tried (turbo racing) which requires left (top) and right (bottom) coordination for sliding around turns, it has worked perfectly.

i did notice some missed touches when the tablet is placed on the bed still. but i mostly use it holding up anyway so not a problem. love to see what others experience with it is too. like u said it could fix some but not all. hope at least "some" is majority of the users.
[Nexus 7 (2013) General] sfhub:
I've grown so used to the pattern I don't even mention it anymore, but the touches work fine when I hold the tablet or have it plugged in.

A lot of the touch issues start showing up when it is left on a table, which is the situation my experiences above were regarding.

On ts10 the touches are fine even on a table for this same unit.
[Nexus 7 (2013) General] littleromeo:
I flashed 1.69. It works fine here.
[Nexus 7 (2013) General] lomonic:
I was previously going between ts10 ts11 ts12 and ts16, all of which presented random freezing abt 5 to 10secs during typing in certain apps but mostly experienced in kik. Somehow typing now is more accurate than using the patches. Almost feels like they are better calibrated. I'm still not adjusting well to the new location of the fullstop though.

Other 4.4 matters

I noticed a problem wit quick office. It had an update after rebooting into 4.4 and now it's showing a green android icon instead of the quick office icon. Is anyone else having the same problem? It still works though.

Also some widgets needed to be removed and readded. The my library widget actually works good now without blank covers.
[Nexus 7 (2013) General] Elting:
So will I have to flash the fix again after the OTA or even after flashing the Factory Image (when it is public)?
[Nexus 7 (2013) General] sfhub:
If you are talking about the touchscreen ts10, ts20, etc. unless you run the ts-unlock, you will still be using whichever touchscreen software you previously were running, regardless of ota or factory image.

If you want to run the touchscreen software that comes with KRT16O, then run ts-unlock before or after you install kit kat, doesn't matter. Upon first reboot, you'll be back to using the touchscreen software that came from the manufacturer.

If you find the kit kat touchscreen software is not to your liking, you can run ts10, ts20, whichever again.

I should point out that 4.3 kernels will not boot a 4.4 ROM, so when you run ts10, ts20, etc. after installing kit kat, it will not get past the bouncing balls. It doesn't matter though, because by the time you get there, the touchscreen software is already installed.

Just press and hold the Power button until the tablet reboots and you'll be back to using the onboard 4.4 kernel, but with the ts10, ts20, etc. touchscreen software.
[Nexus 7 (2013) General] bokagavrilov:
tried it ...and the UI its smooth..i think its something wrong with the GPU because its the vid that lags its like that the gpu isnt working as it should i just tested again with stock 4.3 and i dont see those drops ( ps same vids and i also tried others)
[Nexus 7 (2013) General] Hilbe:
I was running a custom kernel. I put it back to stock and tried to flash the OTA. I get "/system/bin/thermald" has unexpected contents and the install fails. Any idea how to fix that?
[Nexus 7 (2013) General] AarSyl:
Anyone tried running benchmarks yet? I got 7710 running ART, while I'm used to seeing 6500ish on JB 4.3. Nice!

I know that Quadrant isn't the most reliable, but I don't use it to compare devices, but to compare different roms on the same device. That provides somewhat consistent results, since it is device specific.
[Nexus 7 (2013) General] stfudude:
I've got a different error :

"/system/bin/debuggerd" has unexpected contents.

Error in /tmp/update . zip (Status 7)

Installation aborted

Previous kernel: faux m v7

Previous recovery: twrp
[Nexus 7 (2013) General] mandrsn1:
I had the same error. I just flashed the system.img from 4.3 in fastboot. the install worked fine after that.
[Nexus 7 (2013) General] sfhub:
You need to get the stock JSS15R or KRT16O /system/bin/thermald

You can either get the one file if you are sure that is all you need or if you have a lot of changes, you can consider reflashing stock JSS15R with the flash-all-nowipe option.

http://xdaforums.com/showthread.php?p=45671279#post45671279
[Nexus 7 (2013) General] Hilbe:
Does that wipe data?
[Nexus 7 (2013) General] Spyr0s:
There is a thermad.bak in \system\bin, rename it to thermald
[Nexus 7 (2013) General] sfhub:
Are you using stickmount?

That is the most likely cause of this error.

Stickmount modifies this file after backing it up, then restores it when it is done.

Sometimes that gets out of sync.

You can get a copy of the original stock JSS15R debuggerd in this post:

http://xdaforums.com/showthread.php?p=46240453#post46240453
[Nexus 7 (2013) General] mandrsn1:
Not if you just flash system.img
[Nexus 7 (2013) General] Hilbe:
Disregard. Flashing system now :)
[Nexus 7 (2013) General] stfudude:
Thanks a lot, man! Will try now
[Nexus 7 (2013) General] someotherguy:
Just installed using Scott's 4.4 Odex .zip. On 4.4 missing Ok Google, and wallpaper doesn't strech under buttons and notification area.

Is wallpaper stretching for anyone else?
[Nexus 7 (2013) General] biggiestuff:
I flashed it successfully using TWRP but when i try to go to sixxaxxiss it says my root is not working. Any suggestions? :(
[Nexus 7 (2013) General] jmdearras:
set_metadata_recursive: some changes failed

I fail near the end with set_metadata_recursive: some changes failed. Will not boot, now, loops into recovery (TWRP). Any ideas?
[Nexus 7 (2013) General] someotherguy:
Also, is google now on the left like it is on the Nexus 5?
[Nexus 7 (2013) General] stfudude:
Now I got another problem... thermald

Can someone please give me the JSS15R stock thermald (in /system/bin) ? My Internet is very expensive so downloading a 4xx mb factory image is out of the question. Please help.
[Nexus 7 (2013) General] hanzotutu:
Tried ART for a while.....turned back to Dalvik
[Nexus 7 (2013) General] fzammetti:
I'm getting the same thing. Was stock before but rooted... I went out of my way to NOT hack anything in fact, just let it be, other than root... ARGH.
[Nexus 7 (2013) General] lespaulman67:
Hey Everyone

I installed the Kit Kat by side loading it. My device wasn't even unlocked.

With my touch issue I had seems to be gone right now.

This Kit Kat doesn't look any different then what I had. It does have all the extra little things like Office and printing in the cloud and pay here by touch crap.

I don't have any new wall papers. I thought Kit kat had some new wall papers in the videos I seen.

There is still a line above my icons . I thought it was supposed to be without dividers.

I did not have one error at all loading this and its running good.

Let me know if there is anything I need to check make sure I have the full version of the release. And not the pre release files.

This is the one I loaded. 3a3951e8243c82bc01a620ab858f4454c8ebd65c.signed-razor-KRT16O-from-JSS15R.3a3951e8.zip
[Nexus 7 (2013) General] dimako83:
why?
[Nexus 7 (2013) General] sfhub:
Either install in TWRP/CWM or unzip and grab the thermald file an place in /system/bin

update-JSS15R-thermald.zip
[Nexus 7 (2013) General] sfhub:
You have the full release.

I believe they are only providing the new launcher to N5 for now but you can probably install a 3rd-party launcher to get the UI feel.
[Nexus 7 (2013) General] sfhub:
If you ever run into the problem again, I added the JSS15R thermald to the "Stock missing/modified JSS15R" section of the first post.
[Nexus 7 (2013) General] Vanillalite:
YMMV

Some quick initial benches running stock ROM with stock kernel and dalvick. Hate me if these are terrible. I have warned you in advance!
[Nexus 7 (2013) General] Muikkuman:
I have the same problem. Why is this happening? I'm completely stock, stock recovery, except root.
[Nexus 7 (2013) General] hanzotutu:
I didn't feel the difference, and there are compatible issues.
[Nexus 7 (2013) General] sfhub:
You probably have an older version (v1.51 or earlier) of SuperSU.

If that is the case try installing UPDATE-SuperSU-ota.zip from this post:

http://xdaforums.com/showthread.php?p=44597339#post44597339

then reinstall the OTA.
[Nexus 7 (2013) General] sfhub:
Are you using SuperSU v1.51 or earlier? If so see above post.
[Nexus 7 (2013) General] hatyrei:
Wallet not supported

I mean after flashing 4.4 it has tap to pay feature...but when I log in to my Gwallet app >settings>about>Tap to pay :device not supported

:(
[Nexus 7 (2013) General] fzammetti:
I actually updated SuperSU to 1.69 right before trying the update, so while you may be correct in saying this, it's clearly not the answer for everyone, unfortunately - I'm still sitting here with a soft-bricked N7 :(
[Nexus 7 (2013) General] jmdearras:
It was the latest.
[Nexus 7 (2013) General] dmeadows013:
Does flashing TWRP or Clockworkmod bring back the touchscreen issues? I read somewhere that they used the old drivers and caused the problem in the first place.
[Nexus 7 (2013) General] Muikkuman:
The problem was SuperSU Thanks.
[Nexus 7 (2013) General] oTeMpLo:
Probably you have thermald.bak in that folder.. just rename it. it worked for me. (elemntalx?)
[Nexus 7 (2013) General] Vanillalite:
More benchmarks.

Still Dalvick, stock ROM and stock kernel.

Browser is Chrome Beta
[Nexus 7 (2013) General] sfhub:
I'm curious, how did you do the update. Was it through the update.zip from chainfire's download?

I went back and examined his install file and it suffers from the same problems as previous ones, it has an empty "dummy" placeholder install script/binary.

The last one that actually worked was v1.55. Earlier today, I did a factory restore of JSS15R, then installed SuperSU v1.55, then sideloaded the KRT16O update.zip so I can personally say that combination works.

So basically I believe if you had a version v1.51 or earlier, then used the v1.69 update.zip, it wouldn't have done anything since the install script is just a placeholder. You should probably assume you were on whichever version of SuperSU you had prior to updating.
[Nexus 7 (2013) General] sfhub:
See if above applies.
[Nexus 7 (2013) General] fzammetti:
Nope, I updated it from the store... updated SuperSU app to 1.69, then launched the app and it updated the su binary itself (not sure what version that is).
[Nexus 7 (2013) General] sfhub:
I can work with you to figure out what went wrong or you can just flash the JSS15R system.img and rerun the OTA.

There is likely some remnant of an earlier SuperSU installation that is causing the OTA to fail while setting permissions. That is the most common error for the failure in the recursive operation.
[Nexus 7 (2013) General] fzammetti:
I'd definitely be grateful for any ideas you have short of a wipe/restore at this point :) I've had to rebuild my tablets too much over the years, if there's a way to avoid it here I'd like to do so. Fire ideas away, I'll try 'em all at this point! :)
[Nexus 7 (2013) General] sfhub:
Thanks, I added a link to your two benchmark posts in the first post.
[Nexus 7 (2013) General] sfhub:
Can you still boot into recovery?

I suggest you install SuperSU v1.55 from the first post using TWRP.

If you can't boot your rom, you can still place the SuperSU update.zip on the virtual sdcard using adb push or you can sideload it.

In addition to installing SuperSU, it will reset all sorts of old permissions SuperSU might have left around.

Also, did you sideload the KRT16O update.zip or is it sitting on your virtual sdcard still?
[Nexus 7 (2013) General] jmdearras:
I reflashed JSS15R, and it took, but I cannot get ADB to see the device in the bootloader mode, now. :(
[Nexus 7 (2013) General] sfhub:
adb is not supposed to see the device in bootloader. Only fastboot sees the device in bootloader. adb can see the device in recovery if you have the proper drivers installed.
[Nexus 7 (2013) General] jmdearras:
OK so how do I side load the OTA?

:laugh:
[Nexus 7 (2013) General] blackroseMD1:
Edit: Nevermind
[Nexus 7 (2013) General] jmdearras:
Does the new bootloader need different usb drivers?
[Nexus 7 (2013) General] sfhub:
I am using my previous drivers and it works fine.

fastboot works with bootloader

adb works with recovery
[Nexus 7 (2013) General] sfhub:
Covered in this post:

http://xdaforums.com/showthread.php?p=44882205#post44882205

To sideload, you use Recovery, not bootloader.
[Nexus 7 (2013) General] Vanillalite:
Once you get to the boot loader toggle to boot to recovery. When the android guy comes up hold down power, press and release up volume, and then release power.

Then click the option to adb the update in recovery and use the adb sideload filename.zip command.
[Nexus 7 (2013) General] sonnydroid:
After flashing JSS15R->KRT16O OTA, do I still need to flash stock KRT160 kernel and bootloader v3.15?
[Nexus 7 (2013) General] sfhub:
No.

After the OTA you will have everything you need

v4.01 bootloader

KRT16O kernel

KRT16O recovery

KRT16O rom

The kernel and recovery are there in case you need to go back after flashing custom kernels, custom recoveries, etc.
[Nexus 7 (2013) General] sfhub:
Mini guide for flashing stock factory image:

You must have your bootloader unlocked to flash the factory images released so far.

You have the OPTION to wipe your data but it is best to back up anything important AND copy off the phone

Download the factory image from Google's servers:

(2013/11/18 Google updated factory images to correct filename mistakes, no need to reflash, v2 addon reflects new filenames)

flo/WiFi

deb/LTE

Unpack using 7-zip or winrar.

You may need to unpack twice

once to get the .tar file from .tgz

another to get the actual razor-krt16o/razorg-krt16o directory from the .tar

unzip the addon to the appropriate directory

flo/WiFi - razor-krt16o-addon-v2.zip into the razor-krt16o directory (from previous step)

deb/LTE - razorg-krt16o-addon-v2.zip into the razorg-krt16o directory (from previous step)

boot your tablet to the bootloader using Power+VolDown

connect via usb cable to pc

If you have problems with drivers, use the adb_driver.zip from this post or naked drivers from this post

in command prompt in the razor-krt16o/razorg-krt16o directory type EITHER

flash-all

(this WILL perform factory reset and wipe your data, including virtual sdcard, starting completely fresh)

OR

flash-all-nowipe

(this WILL NOT wipe your data, nor your virtual sdcard, allowing you to preserve your setup)

You can ignore the warning about the 3 missing .sig files in the status.

Google didn't sign these factory restore images, which is incidentally why you need to be unlocked to flash.

If you have issues after upgrading, the first thing you should try is factory reset (backup your apps and sdcard if needed)

Whenever you preserve your data whether it be factory image or natural OTA, there will always be a

small percentage

of users who will encounter instability, depending on what apps they are using
[Nexus 7 (2013) General] fzammetti:
I sideloaded.

Ok, so I went with the option of just flashing system.img and then applying the OTA again since that seemed most expedient to me, and that worked fine... yes, I lost root naturally, so had to re-root, but all seems right with the world now, up on 4.4 and rooted.

Is there anything special to look for with regard to old su versions that you suspect was the culprit? Is it literally just some older versions (something like su.bak in /system or some such?) that I can look for? Especially given that I just updated SuperSU and it updated su after the upgrade again, so in theory I'd have the same problem with the *next* OTA if I don't get things "cleaned up".

Thanks for your help!
[Nexus 7 (2013) General] jmdearras:
I just flashed TWRP and loaded the OTA with that. Went fine. Then rooted.

:)
[Nexus 7 (2013) General] sfhub:
su

cd /system/etc

busybox lsattr install-recovery.sh

If you see an "i" in the attributes, then that will prevent an OTA from installing.

The solution is simple, just flash the v1.55 SuperSU in the first post, it will reset the attributes so that an OTA can install.
[Nexus 7 (2013) General] airmaxx23:
Using ART causes quite a few faves to not work at all, including Dead Trigger 2.
[Nexus 7 (2013) General] ITenson:
Successfully sideloaded to Kitkat!

Thank you so much for all the information you have collected for us! Very useful!
[Nexus 7 (2013) General] fzammetti:
Ok cool, thanks... I see an A only now, so looks good :)
[Nexus 7 (2013) General] CrazyPeter:
Had the problems mentioned in this thread. Occurred with both TeamWin and ClocworkMod recoveries, I got the set_metadata_recursive: some changes failed error.

I downloaded the 4.3 factory image unzipped to the IMG files and booted into fastboot, and JUST flashed the system.img, I then rebooted recovery and cleared cache and davlik cache, the tablet did not boot, I tried to load the OTA in recovery and it complained about not enough space on /system for the patch files.

I then formatted system partition in recovery, then loaded the system.img again (from fastboot), and then tried the OTA patch ZIP from recovery, and it patched perfectly.

I now back up and running 4.4 , no data lost at all.

Hope this helps someone (+Thanks if it did).
[Nexus 7 (2013) General] aa_chow:
Had the same problem. SuperSU 1.69 would not show up in app drawer but does show up in Settings > Apps.

When I clicked Uninstall Updates, it shows up in the app drawer but would force close.

What solved it in the end was reinstalled it, and wipe cache and dalvik cache.
[Nexus 7 (2013) General] sfhub:
It seems magnetic smart wake for cases is fixed in KRT16O.

Been able to wake the tablet w/o needing to have Bluetooth turned on.

Can anybody confirm?
[Nexus 7 (2013) General] LoopDoGG79:
I have a completly stock N7 (stock system, kernel, recovery, locked bootloader) Ive installed latest android SDK. My device is recognized when running. But, when i go to recovery, adb sideload option, my device is not recognized by my Windows 8.1 machine. I looked up the hardware IDs and changed them in the android_winsuf file. Rebooted windows 8 into "Dont enforce driver signatures" mode, installed the android_winsuf file. Still will not recognize my device, hence adb did not recognize my device when in recovery, adb sideload. Is there a step im missing? If someone has the correct android_winsuf file or drivers so windows will see my device correctly in recovery, please share! :)

PS I installed the latest Google USB drivers. When system is up and running, these are my hardware IDs

USB\VID_18D1&PID_4EE2&REV_0228&MI_00

USB\VID_18D1&PID_4EE2&MI_00
[Nexus 7 (2013) General] molo88:
It took a little bit too long [around 20 minutes] to rebuild for first ART reboot
[Nexus 7 (2013) General] mhca:
4.4 fixed USB OTG

I had issues using Nexus Media Importer (or any OTG app for that sake) before 4.4.

Now with KitKat it works :)

That was the mean reason for me to hurry to update, so I'm a happy person now :)
[Nexus 7 (2013) General] codahq:
It's weird that GEL isn't included. With all of the talk about fragmentation you'd think they'd want to include that.
[Nexus 7 (2013) General] wd5gnr:
I will be very happy if this makes bluetooth keyboards work.

Sadly I am on the road this week and too chicken to upgrade it without a real computer near by in case I brick it.
[Nexus 7 (2013) General] LoopDoGG79:
Solved the issue. I downloaded and exctracted the latest Google USB files. I looked up the hardware ID windows was seeing when in recovery/adb sideload. I edit the android_winsuf file by adding those lines under "%CompositeAdbInterface%" Rebooted my windows machine to "Do not enforce signitures mode" Uninstalled the driver. Installed the modified android_winsuf file ( file must be in theUSB folder) Unplugged, re-plugged in my device while in recovery/adb sideload. Wha-la!! Windows saw my device correctly, as an ADB interface. Ive attached the modified android_winsuf file for those having the same issues as me.

https://www.dropbox.com/s/povbzd15kkbks03/android_winusb.inf
[Nexus 7 (2013) General] JassyNL:
Oh really? My Smartcase always works on 4.3, even with Bluetooth turned off. With 4.4 it's working as expected, case open and screen turns on.
[Nexus 7 (2013) General] hawkye:
I never had an issue with my Portenzo case turning on/off the screen in 4.3 either. Works the same in 4.4. I have never had the Bluetooth on.
[Nexus 7 (2013) General] thetechaddict10:
I'm having the same experience. I was under the impression that KitKat would bring Tap & Pay to my Nexus 7! If anybody has Tap & Pay working on their tablet, let me know! I installed the update.zip through CWM and retained root by installing the SuperSU .zip before rebooting, so I am curious if there are any side effects from using that process to update the tablet.
[Nexus 7 (2013) General] Zinc64:
Breaks Xposed Framework

Rooted with TWRP....Flashed successfully with the "KRT16O repackaged TWRP/CWM-flashable".

Kit Kat is purring,

Unfortunately...XPrivacy now broken...doesn't recognize 4.4 as being "4.0+".

Apparently Xposed Framework not compatible with Kit Kat yet...developer says he's waiting on delivery of Nexus 5...Nov 22 or later.