So the consensus is to skip this update.
Is there a way to permanently get rid of the nag screen, though?
edit: ok...I see that the OTA fix is for stock. Somehow I misread and though it was for one of the ROMs.
Follow along with the video below to see how to install our site as a web app on your home screen.
Note: This feature may not be available in some browsers.
So the consensus is to skip this update.
flash this ota fix if ur getting prompt for the new ota update and let me know if it goes away
Will only work with custom recovery!!
If u have root download the fix, extract the build.prop and replace yours in system, set perms rw-r-r and rebootNo custom recovery here so I guess I have to figure out how to add TWRP.
Say, I just saw a reference to an app called "Flash Gordon," for flashing zips without needing a custom recovery:
[APK] Flash Zip Files, NO NEED FOR CWM OR TW… | Xperia Miro | XDA Forum
Does anyone have experience with this? Would it work for the nag fix zip?
I would like to avoid installing TWRP if I can, simply to save time. I only use a couple of root apps and don't tinker daily. All I ever do with my phone is toggle the wifi hot spot and use the stock web browser.
If u have root download the fix, extract the build.prop and replace yours in system, set perms rw-r-r and reboot
Just compare...the one i posted has ums and 100% jpg quality... And will say awe inspiredCool. What's the difference between the two (the stock one and the "fix")? If it is minor, can I just backup my build.prop and edit the current one?
And that's it? That's all the editing that's required to stop the nag screen? Change UMS to true and tack on jpeg.quality=100 at the end? Or are those just examples to enable us to identify which build.prop you're referring to?Just compare...the one i posted has ums and 100% jpg quality... And will say awe inspired
Thats just what i added over stock... Use winmerge and compareAnd that's it? That's all the editing that's required to stop the nag screen? Change UMS to true and tack on jpeg.quality=100 at the end? Or are those just examples to enable us to identify which build.prop you're referring to?
And that's it? That's all the editing that's required to stop the nag screen? Change UMS to true and tack on jpeg.quality=100 at the end? Or are those just examples to enable us to identify which build.prop you're referring to?
Followed your lead and edited the dates and lines you suggested. Nag screen is gone, I'm "up to date" and all seems well. JDubTrey, thanks for sticking your neck out and taking a chance....and thanks to brittnearl as well.I backed up my original build.prop, and changed the following props to match the one in the fix.zip:
ro.build.display.date
ro.build.version.incremental
ro.build.date
ro.build.date.utc
ro.build.description
ro.build.fingerprint
ro.build.sw_internal_version
The phone did say that I needed an update on reboot (it appeared to just give a background notification and not a popup). I selected the notification for "..more info" and the update tool said "up to date". I didn't get any more popups or updates after that.
I did a root check and fired up tethering as a quick test and both were fine.
Many thanks to brittnearl.
Not sure what u mean by chance?? @jdubtrey i know its the dates not what i added... I was just letting u know what i changed above stock... Glad it helped u guys outFollowed your lead and edited the dates and lines you suggested. Nag screen is gone, I'm "up to date" and all seems well. JDubTrey, thanks for sticking your neck out and taking a chance....and thanks to brittnearl as well.
I had deleted the ota file. Stopped the notifications and was still getting the nagging popup.
This morning I overslept because the nag interfered with my alarm. Got p@@@ed and finally touched "install now". Watched the countdown and then..... Nuthin happened... No reboot... Nuthin! I assume that's because the gota file was deleted.
Haven't seen the nag screen since.
Yes it will come bk unless u either install it or use my build.prop fix... As far as it not installing u must have modified the stock file system in someway eg: removing bloat apps, modifying apps, etc... Root should b ok as the update only checks for stock files not added filesJust wait a couple days it will come back i promise you that I've tried to install mine three separate times and it will never go through.if i get again I'm calling virgin mobile and b/+ching
Yes it will come bk unless u either install it or use my build.prop fix... As far as it not installing u must have modified the stock file system in someway eg: removing bloat apps, modifying apps, etc... Root should b ok as the update only checks for stock files not added files
Yes it will come bk unless u either install it or use my build.prop fix... As far as it not installing u must have modified the stock file system in someway eg: removing bloat apps, modifying apps, etc... Root should b ok as the update only checks for stock files not added files
Since u removed system apps ur only options are my fix or to flash back to stock and take all updates Then remove the bloat appsI'll be sure to do an update if it does return. I have removed some bloatware tho. Most recently VM's "my account". Wish I could remember what I unchecked to stop the notifications tho.
If u have root download the fix, extract the build.prop and replace yours in system, set perms rw-r-r and reboot