My Nexus 7 just got the new 4.4.2 OTA update. Can't see any differences yet.
Anyone seen an OTA link?
wilde68 said:
My Nexus 7 just got the new 4.4.2 OTA update. Can't see any differences yet.
Click to expand...
Click to collapse
There's now cast screen option in the display settings!
http://android.clients.google.com/p...signed-nakasi-KOT49H-from-KRT16S.d72d1413.zip
Wifi, of course.
Appears to be a new kernel, remot display stuff, patching a bunch of things. Sorry, not very useful
So, as always kids, if you modified your ROM, you can't OTA. This time that includes the kernel.
chnages:
1. transparent lockscreen, nice! but launcher is not transparent
2. in app drawer apps and widgets text is now in white colour.
this is for now, i need to take a look more
I think Chrome feels a lot smoother, still got the boot animation glitch and the jumping back to another app when hitting the back key out of an app.
Sent from my Nexus 7 using Tapatalk
There's any link to download the stock kernel from the 4.4? I don't have any PC now and I can't extract it from the Google image.. Sorry for my English
Este mensaje se autodestruirá desde tapatalk
Anyone having issues with their screen on time?
Sent from my Nexus 7 using XDA Premium 4 mobile app
khaytsus said:
http://android.clients.google.com/p...signed-nakasi-KOT49H-from-KRT16S.d72d1413.zip
Wifi, of course.
Appears to be a new kernel, remot display stuff, patching a bunch of things. Sorry, not very useful
So, as always kids, if you modified your ROM, you can't OTA. This time that includes the kernel.
Click to expand...
Click to collapse
I received the update and i have mkernel.
Sent from my Nexus 7 using Tapatalk
khaytsus said:
http://android.clients.google.com/p...signed-nakasi-KOT49H-from-KRT16S.d72d1413.zip
Wifi, of course.
Appears to be a new kernel, remot display stuff, patching a bunch of things. Sorry, not very useful
So, as always kids, if you modified your ROM, you can't OTA. This time that includes the kernel.
Click to expand...
Click to collapse
Whats the kernel version is it finally 3.4??
chand9336 said:
Whats the kernel version is it finally 3.4??
Click to expand...
Click to collapse
Yup....Its version 3.4 :good:
jithumon said:
Yup....Its version 3.4 :good:
Click to expand...
Click to collapse
Are you talking about grouper/nexus 7 2012?
nikola1970 said:
chnages:
1. transparent lockscreen, nice! but launcher is not transparent
2. in app drawer apps and widgets text is now in white colour.
this is for now, i need to take a look more
Click to expand...
Click to collapse
transparent lockscreen was also there in 4.4.1 :silly:
khaytsus said:
http://android.clients.google.com/p...signed-nakasi-KOT49H-from-KRT16S.d72d1413.zip
Wifi, of course.
Appears to be a new kernel, remot display stuff, patching a bunch of things. Sorry, not very useful
So, as always kids, if you modified your ROM, you can't OTA. This time that includes the kernel.
Click to expand...
Click to collapse
I'm back on the google kernel but still the ota or sideload doesn't work.
Sent from my Nexus 7 using XDA Premium 4 mobile app
chand9336 said:
Whats the kernel version is it finally 3.4??
Click to expand...
Click to collapse
Kernel on my device is 3.1.10-g4776c68 after up date to 4.4.2 dated 20 Nov 2013 on grouper
quincyquinn said:
Kernel on my device is 3.1.10-g4776c68 after up date to 4.4.2 dated 20 Nov 2013 on grouper
Click to expand...
Click to collapse
Same here
On my N4 it is 3.4 though
Rob
redmonke255 said:
I received the update and i have mkernel.
Click to expand...
Click to collapse
It installed? I'd be quite surprised It'd fail for both boot.img and power grouper library. I just removed both from my OTA zip and left m-kernel in place
ev!denz said:
I'm back on the google kernel but still the ota or sideload doesn't work.
Click to expand...
Click to collapse
Can't just restore kernel if you're using a kernel which replaces any files, such as m-kernel replaces the power grouper. You could restore the full system image, the power grouper lib, or remove it from the OTA. I opted for the latter.
I took the ota and it caused me to bootloop. Anyone know how to fix this?
fyi not rooted and hardly anything even installed on it. My mother used it to play solitaire basically.
I cant for the life of me get this OTA installed. Running stocked rooted 4.4.1, installed and set up yesterday. No custom kernel. Have tried flashing in latest TWRP, as well as sideloading via adb and same result.
It states:
Not enough free space on /system to apply patches
E:Error executing updater binary in zip '/sdcard/update.zip'
Error flashing zip '/sdcard/update.zip'
Just applied the 4.2.2 OTA to my WiFi N7 2012 and noticed that the System ROM size is 670MB. Was this the default System ROM size for previous ROM versions? I never paid attention to the System ROM size before, but I was about to integrate a couple apps using Titanium Backup and got a message saying that I did not have enough room to integrate the app. I had integrated some of these apps before without running into a storage room problem. Also, how can I determine the version of the bootloader that's currently being used?
Related
According to this IBT Blog, restoring to stock ROM is mandatory for receiving the upcoming OTA update to 4.2.
Does any one know if this is true, as the last OTA update to 4.1.2 automatically launched and completed just fine on my N7 in its rooted state?
digixmax said:
According to this IBT Blog, restoring to stock ROM is mandatory for receiving the upcoming OTA update to 4.2.
Does any one know if this is true, as the last OTA update to 4.1.2 automatically launched and completed just fine on my N7 in its rooted state?
Click to expand...
Click to collapse
I think you're confusing running the stock rom and being rooted. One can be rooted while still running the stock rom. If this is the case, you should have no problem receiving the OTA update. On the other hand, if you loaded a custom rom (e.g., CyanogenMOD), you won't get the OTA update.
nyijedi said:
I think you're confusing running the stock rom and being rooted. One can be rooted while still running the stock rom. If this is the case, you should have no problem receiving the OTA update. On the other hand, if you loaded a custom rom (e.g., CyanogenMOD), you won't get the OTA update.
Click to expand...
Click to collapse
Am I still able to get the OTA update, if I'm on Stock rooted, but modify the system to have tablet UI?
If not, what will be my option, to update the tablet? I guess manually pushing the Rom might work, but a reassuring would be good
Sent from my Nexus 7 using xda app-developers app
Bcroc said:
Am I still able to get the OTA update, if I'm on Stock rooted, but modify the system to have tablet UI?
If not, what will be my option, to update the tablet? I guess manually pushing the Rom might work, but a reassuring would be good
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
I haven't messed around with modifying the UI, but I have replaced and disabled system apps in the past, and that stops the OTA from installing (it will download the OTA, but the install will fail). I suspect it's possible that the same thing will happen with a modified UI, but I'm not 100% sure. What is the process for modifying the UI? Did you replace certain files? If so, hopefully you saved the original versions and can revert back to the originals.
Bcroc said:
Am I still able to get the OTA update, if I'm on Stock rooted, but modify the system to have tablet UI?
If not, what will be my option, to update the tablet? I guess manually pushing the Rom might work, but a reassuring would be good
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
Can you keep us updated here if you decide to try and install the OTA update while in tablet UI? i would be interested as well if it will update
Bcroc said:
Am I still able to get the OTA update, if I'm on Stock rooted, but modify the system to have tablet UI?
If not, what will be my option, to update the tablet? I guess manually pushing the Rom might work, but a reassuring would be good
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
If all you did was change the dpi then yes it wont matter your build.prop is going to be overwritten anyways
ontoptherock said:
Can you keep us updated here if you decide to try and install the OTA update while in tablet UI? i would be interested as well if it will update
Click to expand...
Click to collapse
Of course, but I think I will wait the update before doing anything, that's just more convenient
Sent from my Nexus 7 using xda app-developers app
---------- Post added at 07:16 AM ---------- Previous post was at 07:15 AM ----------
nyijedi said:
I haven't messed around with modifying the UI, but I have replaced and disabled system apps in the past, and that stops the OTA from installing (it will download the OTA, but the install will fail). I suspect it's possible that the same thing will happen with a modified UI, but I'm not 100% sure. What is the process for modifying the UI? Did you replace certain files? If so, hopefully you saved the original versions and can revert back to the originals.
Click to expand...
Click to collapse
No, I don't wan to replace anything, only modify the build.prop to have a different density setting.
Sent from my Nexus 7 using xda app-developers app
nyijedi said:
I think you're confusing running the stock rom and being rooted. One can be rooted while still running the stock rom. If this is the case, you should have no problem receiving the OTA update. On the other hand, if you loaded a custom rom (e.g., CyanogenMOD), you won't get the OTA update.
Click to expand...
Click to collapse
I do know the difference between Stock ROM vs. Stock ROM + Rooted -- but I had just read the IBT blog too fast and plus I implicitly assume that folks who use custom ROM would just wait until their particular custom ROM rolls onto 4.2 base, to realize that folks with custom ROM is the target audience of the IBT blog.
So its safe to update via ota if your on stock rooted? Ive seen people saying its fine but on my old atrix I was warned it would brick my device.
jefferson9 said:
So its safe to update via ota if your on stock rooted? Ive seen people saying its fine but on my old atrix I was warned it would brick my device.
Click to expand...
Click to collapse
My N7 went through the last update just fine (other than getting un-rooted).
UPDATE: don't need anyone testing this anymore as it is not fixing most reboots
Can someone who is running custom recovery and has bad/frequent reboots install the attached file and see if it alleviates your reboots?
Please let me know what version of the OS you are running and if you are on JSS15J or JSS15Q, whether you updated via factory image or OTA.
I am 99.99% sure nothing bad will happen to your system. This will not disable your ability to get OTAs, nor change any system files, nor affect touchscreen, nor affect GPS, ...
I'm running a version of cm which has worked better than stock but still a daily reboot. What is this file going to alter / Will it work on cm?
Sent from my Nexus 7
joeshmoo said:
I'm running a version of cm which has worked better than stock but still a daily reboot. What is this file going to alter / Will it work on cm?
Click to expand...
Click to collapse
If it works, it should work ok with CM as long as you run it in TWRP.
It doesn't actually touch the ROM. It uses the kernel to reset the DDR3 memory timings and allows the system to retrain.
Thanks, I like to know what I'm flashing. Just flashed, will report back.
Sent from my Nexus 7
getting desperate and flashing this to try..
Didn't work. Just had my first reboot.
Sent from my Nexus 7 using Tapatalk 2
fkfs9 said:
Didn't work. Just had my first reboot.
Click to expand...
Click to collapse
Could you tell me what OS you are running and whether you've run an OTA before?
sfhub said:
Could you tell me what OS you are running and whether you've run an OTA before?
Click to expand...
Click to collapse
I'm on 15Q odex stock ROM. I never had an ota before.
I rooted and unlocked the boot loader and flash this ROM yesterday.
Just had a reboot on mine as well.
Running build 8 of this:
http://forum.xda-developers.com/showthread.php?t=2391779
[ROM][CM10.2][4.3][CyanogenMod FLO Kangs][DJL10.2][LINARO][Build 8][2013/08/25]
Ok, then it looks like this won't fix the random reboots.
Sorry, back to your regularly schedule program.
sfhub said:
Ok, then it looks like this won't fix the random reboots.
Sorry, back to your regularly schedule program.
Click to expand...
Click to collapse
Thanks for trying
Sent from my Nexus 7 using Tapatalk 4
joeshmoo said:
Thanks, I like to know what I'm flashing. Just flashed, will report back.
Sent from my Nexus 7
Click to expand...
Click to collapse
Don't you mean you like to know who you are flashing?
Sent from my Nexus 7 using xda app-developers app
im on clean rom with elemental x 1.2 and i have never had a reboot or anything bad happen since. i did have issues on stock 4.3 with small tweaks but since clean rom i have had no issues whatsoever
Edit also was on slim bean flo and had same issues so it's something messed up in the rom i would assume and not the software version it self
KiaraTheDragon said:
im on clean rom with elemental x 1.2 and i have never had a reboot or anything bad happen since. i did have issues on stock 4.3 with small tweaks but since clean rom i have had no issues whatsoever
Edit also was on slim bean flo and had same issues so it's something messed up in the rom i would assume and not the software version it self
Click to expand...
Click to collapse
can i flash clean rom without losing data or apps? im on modded stock rom + elementalX
I haven't had a reboot since the newest update.
Sent from my Nexus 7 using xda app-developers app
Just threw together a video showing how to manually update your Nexus 7 to 4.4 KitKat.
Hopefully this cuts down the questions. You must be on the 4.3 JSS15R build to update.
Video:
http://youtu.be/bgjH2E5oi0Y
qbking77 said:
Just threw together a video showing how to manually update your Nexus 7 to 4.4 KitKat.
Hopefully this cuts down the questions. You must be on the 4.3 JSS15R build to update.
Video:
http://youtu.be/bgjH2E5oi0Y
Click to expand...
Click to collapse
Can you rename the ota.zip to just ota.zip?
godutch said:
Can you rename the ota.zip to just ota.zip?
Click to expand...
Click to collapse
Yes.
sfhub said:
Yes.
Click to expand...
Click to collapse
Thanks, easier than copying these filenames with hashes
Any specific reason that it only works with the 4.3 JSS15R build instead of the 4.3.1 JLS36I build? Is one just the WiFi version?
Craysh said:
Any specific reason that it only works with the 4.3 JSS15R build instead of the 4.3.1 JLS36I build? Is one just the WiFi version?
Click to expand...
Click to collapse
Yes right now there is no update zip for the LTE N7. I will update my site once that zip comes available
I just upgraded. It seems that the ota package doesn't contain the new launcher that the Nexus 5 uses. There is no Google Now home screen as the far left screen and the app drawer still contains a tab for widgets. Is there a separate app to install now from the store?
codahq said:
I just upgraded. It seems that the ota package doesn't contain the new launcher that the Nexus 5 uses. There is no Google Now home screen as the far left screen and the app drawer still contains a tab for widgets. Is there a separate app to install now from the store?
Click to expand...
Click to collapse
Those features are for the N5 only.
Craysh said:
Any specific reason that it only works with the 4.3 JSS15R build instead of the 4.3.1 JLS36I build? Is one just the WiFi version?
Click to expand...
Click to collapse
Yeah it does a signature check of your system files and the ota file, if one does not check out the update won't apply
I get an error when it tries to install the update - something to do with the BasicDreams.apk not being valid (or something along those lines). It then aborts the installation. Not sure if anyone else is running into this problem, or if there's something I can do to fix it. I'm running stock, but rooted, and I've switched back to the standard recovery image from TWRP to try the install.
Thanks!
Thanks man, I've never used the stock recovery before, so had no clue how to get past the broken robot screen. Your video helped a lot!
Does anyone know the way to do this on a Mac?
Question?
Hello,
I can't get the side load to work because it no longer recognizes my nexus 7 when i enter recovery mode? is there a quick fix for this?
im rooted,using cuatom.kernel and recovery
if i flash the stock kernel and recovery and do what u did on the video,will i lose root or lose any data??
Sent from my Nexus 7 using xda app-developers app
Ignore plz
Sent from my Nexus 7 using xda app-developers app
Just as a note, adb sideload method works with twrp installed. Same steps as the guide but the sideload option is located under the advanced tab.
Sent from my Nexus 7 using XDA Premium 4 mobile app
konradsa said:
Watch the video, the answer is right there.
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
Thanks!! :good:
Sorry goober, I answered to the wrong post by accident. I intended to answer to the guy asking about the recovery mode.
But I think the Mac procedure should be pretty similar, the archive download from Google contains the same tools for Mac. Just not sure how driver installer works on Mac.
Sent from my Nexus 7 using xda app-developers app
Still not having any luck. I can sideload the file onto the tablet fine, but when it gets to the "Verifying current system" stage I get an error saying:
"/system/app/BasicDreams.apk" has unexpected contents
E:Error in /tmp/update.zip
(Status 7)
Installation aborted
I've tried this several times and keep getting the same result. I'm rooted, but running the stock kernel and rom, and using the stock recovery. Any help on this would be greatly appreciated.
Will this work on a stock rooted N7?
Just receive message of OTA. It is a small update and file size is 3.4MB. Since I have flashed the latest TWRP that support the OTA update.
I can not see any different version change.
taitony said:
Just receive message of OTA. It is a small update and file size is 3.4MB. Since I have flashed the latest TWRP that support the OTA update.
I can not see any different version change.
Click to expand...
Click to collapse
i just recieved it myself on my Android 4.4, it says "fixes bugs" which i haven't felt there was, but i guess it's not everyone that finds the bugs they fix, and maybe the performance will go up a little more, i will bench a little later, depending on how much i have to do at work
Yeah it's mostly under the hood bug fixes. There's no change log but one new 'feature' they found is that it will remind you to set up a backup account if you have multiple Google accounts on the device.
Sent from my Nexus 7 using XDA Premium 4 mobile app
puma99dk| said:
i just recieved it myself on my Android 4.4, it says "fixes bugs" which i haven't felt there was, but i guess it's not everyone that finds the bugs they fix, and maybe the performance will go up a little more, i will bench a little later, depending on how much i have to do at work
Click to expand...
Click to collapse
Great to see your investgation what will be updated. But my Nexus 4 has no such update, so it is not for all KitKat devices.
Yeah I checked if it was also up for Nexus 4, sadly its just the N7 up for grabs, Just got the OTA notification, 3MB file.
Also there's this, new build, KRT16S
Sorry is this a jelly bean update or kit kat?
Sent from my SM-N9005 using XDA Premium HD app
protoism said:
Sorry is this a jelly bean update or kit kat?
Sent from my SM-N9005 using XDA Premium HD app
Click to expand...
Click to collapse
we talk about "Kitty kat"
but so far Benchmarks haven't improved to me, but it don't get as hot as with JB rom around the cam when it's in use so that's fine with me
puma99dk| said:
we talk about "Kitty kat"
but so far Benchmarks haven't improved to me, but it don't get as hot as with JB rom around the cam when it's in use so that's fine with me
Click to expand...
Click to collapse
Maybe I have missed something, but are people receiving a small kitty kat bug fix OTA, even though 4.4 has not actually gone out over the air, but is just being sideloaded?
Sent from my SM-N9005 using XDA Premium HD app
protoism said:
Maybe I have missed something, but are people receiving a small kitty kat bug fix OTA, even though 4.4 has not actually gone out over the air, but is just being sideloaded?
Sent from my SM-N9005 using XDA Premium HD app
Click to expand...
Click to collapse
i read some has gotten OTA but not everyone, i used adb yesterday at work to "sideload" 4.4 on to my Nexus 7 2013 16gb tablet and it just is nice running smooth, no heat around my cam anymore in use.
i normally game a little and use it for Teamviewer. I brought my tablet bcs i was tired of dragging a laptop with me around, bcs i drag it to work everyday.
I basicly when at family, or friends house use my tablet for surfing, teamviewer and all what i used the laptop for it's nice
puma99dk| said:
i read some has gotten OTA but not everyone, i used adb yesterday at work to "sideload" 4.4 on to my Nexus 7 2013 16gb tablet and it just is nice running smooth, no heat around my cam anymore in use.
i normally game a little and use it for Teamviewer. I brought my tablet bcs i was tired of dragging a laptop with me around, bcs i drag it to work everyday.
I basicly when at family, or friends house use my tablet for surfing, teamviewer and all what i used the laptop for it's nice
Click to expand...
Click to collapse
Nice, just in this forum only one person claims to have received 4.4 OTA. It does seem they are sending out a patch for something that is only available as a factory image that is being sideloaded. Curious.
Sent from my SM-N9005 using XDA Premium HD app
protoism said:
Nice, just in this forum only one person claims to have received 4.4 OTA. It does seem they are sending out a patch for something that is only available as a factory image that is being sideloaded. Curious.
Sent from my SM-N9005 using XDA Premium HD app
Click to expand...
Click to collapse
the factory image and the one that comes on OTA should be the same as far as i know.
but it was pretty easy to flash my tablet, it took a little bcs i had a problem but when i fixed that one it went smoothly and no issues at all.
anyone else's touchscreen get ridiculous after this small OTA? I never had issues, then we got that jellybean OTA to "fix" touch screen issues for certain people, which then proceeded to break my touch screen. then I got kitkat, and it's perfect again, no touch issues anymore.. now I got this OTA and this morning I had to press everything 5 times before it registered! I did a reboot and it went away, but seriously, if they broke touch again, I'm giving up on this tablet.
Sent from my Verizon LG G2 using Tapatalk Pro
Where is the update located once it is downloaded, I'm trying to install it with TWRP.
Just got it via OTA (had side loaded KitKat before that). Made me lose root but that should be easily fixed.
I had side loaded 4.4, unlocked and rooted. I got the OTA notification and there was an error installing and now I'm stuck in a bootloop. When it comes up it has dead android with red exclamation point and says "No command."
embhorn said:
I had side loaded 4.4, unlocked and rooted. I got the OTA notification and there was an error installing and now I'm stuck in a bootloop. When it comes up it has dead android with red exclamation point and says "No command."
Click to expand...
Click to collapse
Same thing happened to me. I got the OTA notification but stoopidly I had SuperSU in OTA survival mode. The update failed and I ended up at the 'No Command' recovery thing you are talking about.
I was able to fix it by manually flashing the /boot, /recovery, and /system partitions (NOT /userdata ) in fastboot using the KRT16S system image that can be found here (https://developers.google.com/android/nexus/images#razorkrt16s). Everything was okay after that - all of my user data was intact and I was updated to KRT16S :good:
paddycr said:
Same thing happened to me. I got the OTA notification but stoopidly I had SuperSU in OTA survival mode. The update failed and I ended up at the 'No Command' recovery thing you are talking about.
I was able to fix it by manually flashing the /boot, /recovery, and /system partitions (NOT /userdata ) in fastboot using the KRT16S system image that can be found here (https://developers.google.com/android/nexus/images#razorkrt16s). Everything was okay after that - all of my user data was intact and I was updated to KRT16S :good:
Click to expand...
Click to collapse
Ah well. I win the noob award. I panicked and re-flashed stock. But my saving grace is that I have a backup from not too long ago.
airmaxx23 said:
Where is the update located once it is downloaded, I'm trying to install it with TWRP.
Click to expand...
Click to collapse
I was on stock, unlocked, rooted with TWRP. I ran the KRT16S OTA normally. TWRP installed it. I lost root and TWRP. Easy enough fix.
Sent from my Nexus 7 using Tapatalk 4
Lost root, tried reflashing the SU 1.43 binary in TWRP and still don't have root. Any advice?
nchopp said:
Lost root, tried reflashing the SU 1.43 binary in TWRP and still don't have root. Any advice?
Click to expand...
Click to collapse
This: http://autoroot.chainfire.eu/
You need to do this in fastboot. The instructions are at the bottom of the page
if YES, is there a way to install it manually to our N7.2?
Someone will probably post it in this thread once the link gets discovered :fingers-crossed:
After that, just flash back the original boot.img and system.img from KRT16S if you are on a custom kernel or have modified any system files, and then flash the OTA, either from a custom recovery or sideload it from the stock recovery
giank30 said:
if YES, is there a way to install it manually to our N7.2?
Click to expand...
Click to collapse
Check here for the factory image.
https://developers.google.com/android/nexus/images
I use the WugFresh tool kit for easy flashing of stock images.
Android 4.1.1 KitKat is rolling out in stages available for N5, N7LTE, N4 but not yet for N7WiFi also factory images for 4.1.1 won't be available till next week. So we have to wait for somebody to get the OTA and grab the link.
it is out. below the llink
http://plus.url.google.com/url?sa=z....90745e15.zip&usg=mrEFavEhbtdgK5R5ZeUD2qSQuyM.
use the THANKS button!
giuvilas said:
it is out. below the llink
http://plus.url.google.com/url?sa=z....90745e15.zip&usg=mrEFavEhbtdgK5R5ZeUD2qSQuyM.
use the THANKS button!
Click to expand...
Click to collapse
Isn't this for the Nexus 7 2013 LTE Version??
http://www.androidpolice.com/2013/12/06/download-android-4-4-1-kot49e-for-the-2013-wifi-nexus-7/
Is there a changeog anywhere?
This feels so weird, i had HTC Desire for like 3 years, and the last OTA i have seen was like 2 years ago.
Now with N7 it's OTA's overload. :laugh:
Aizukaori said:
Is there a changeog anywhere?
Click to expand...
Click to collapse
Don't know. I've heard it's focused on Nexus 5 camera issues. I'm not getting my panties in a wad to install it.
Summit1 said:
Don't know. I've heard it's focused on Nexus 5 camera issues. I'm not getting my panties in a wad to install it.
Click to expand...
Click to collapse
That's pretty much my feel on it. I just installed those dalvik patches yesterday, I don't want to have to flash the stock libraries, wipe cache, and then flash 4.4.1 just for an extremely minor incremental update that isn't even focused on our device.
Summit1 said:
Don't know. I've heard it's focused on Nexus 5 camera issues. I'm not getting my panties in a wad to install it.
Click to expand...
Click to collapse
I believe that there's more to it. 50MB is not that small for a patch, perhaps they ironed out some bugs(there's a hidden wifi bug in 4.4 that I would like to see fixed).
Stability and optimization improvements are always welcome too...
im on Nexus 7 v2 LTE rom 4.4.0 rooted. any body that can help me go to 4.4.1, i tryed adb sideload but gives me error i use wugfresh toolkit
Please continue in this dedicated thread for your updates.
Thank you and thread closed.