Related
hi
I,ve just replaced a nexus7 2013 after i hit the multitouch problem,everything was fine with it whilst it was running build JWR66N,but then i got a notification to update to the latest version.
I was reluctant to do so,but eventually decided to take the plunge,so i updated,it put build JSS15Q on my nexus...result was terrible multitouch issues,basically the update had inflicted my "working perfectly tablet" with the dreaded multitouch issue,needless to say i was gutted.
My new nexus again comes with the JWR66N build,my question is,can i stop the tablet auto downloading the new update(JSS15Q),i know i don't actually have to install it,but i was told that if i power of my nexus,it will automatically install the update when i reboot,is this true?
Don't want to go anywhere near that JSS15Q update,or any future updates at all if possible.
To be honest,i'm not that interested in having bleeding edge versions,if my nexus works flawlessly on the JWR66N build then i could'nt care less if i never updated ever again,if it ain't broke,don't fix it.
You should look at the two posts in my signature. They will cover everything you need.
BTW the update won't automatically install when you reboot. You can also turn off the notification in the framework services configuration.
sfhub said:
You should look at the two posts in my signature. They will cover everything you need.
BTW the update won't automatically install when you reboot. You can also turn off the notification in the framework services configuration.
Click to expand...
Click to collapse
Okay,thanks Sfhub,can I just ask though,I have the jss15q update sitting in my notification panel,until I specifically allow it,will it just stay there,I mean,will it at some point install itself without any action by me.
What happens if I reboot,will that instigate the update process.
As long as I'M in control of when it gets installed I'm happy,I know it fixes the GPS issue,but I literally never use GPS,so I'm not bothered about fixing that.
Would really really appreciate some help on this,cheers pal
wildcat777 said:
I have the jss15q update sitting in my notification panel,until I specifically allow it,will it just stay there,
Click to expand...
Click to collapse
Correct
settings->apps->all->google services framework
uncheck show notifications
if you get tired of the notification (it'll probably get rid of other Google notifications also)
wildcat777 said:
I mean,will it at some point install itself without any action by me.
Click to expand...
Click to collapse
This shouldn't happen, though you might hit the notification by accident then panic and ask it to continue.
wildcat777 said:
What happens if I reboot,will that instigate the update process.
Click to expand...
Click to collapse
This won't happen.
wildcat777 said:
As long as I'M in control of when it gets installed I'm happy,I know it fixes the GPS issue,but I literally never use GPS,so I'm not bothered about fixing that.
Would really really appreciate some help on this,cheers pal
Click to expand...
Click to collapse
If you ever just want the GPS fix by itself with no other changes, the link is in my signature.
http://forum.xda-developers.com/showthread.php?t=2421373
Thanks Sfhub,really appreciate your quick reply and the info,that's really set my mind at rest.
Once again,cheers pal
Just received this update. Installing now.
Edit: I guess it's only security patch, got December 1st, 2016.
.....
Pkt_Lnt said:
http://forum.xda-developers.com/huawei-watch/help/november-update-m9e41v-t3507154
Click to expand...
Click to collapse
Why are you giving this url with no explanation? This is different update
NeedleGames said:
Why are you giving this url with no explanation? This is different update
Click to expand...
Click to collapse
I missed that the V became a Y, I have poor eyesite, ok? I made a simple mistake as noted in another thread, happy now?
Here is the link to the update for anyone who wants it. You can adb sideload it in watch recovery.
https://android.googleapis.com/pack.../7edfb860768f03482c8c7c95bb346db2af678337.zip
Pkt_Lnt said:
I missed that the V became a Y, I have poor eyesite, ok? I made a simple mistake as noted in another thread, happy now?
Click to expand...
Click to collapse
You are very aggressive mate, calm down.
Hmm, after this update missing Wifi setting at hwatch and i can't turn it off sad with battery drain
I'm on Android P and today I noticed an update for Google photos app. So I downloaded it and it turns out to have broke something. When u roll up or down the screen flickers now. I have since then went back before the update. Is it just mines or anyone else on P can comfirm.
same here.
3.19.0.194452507
Must be an Android P issue. I don't notice a flicker when scrolling. I even changed from days, months, etc.
Sent from my Pixel 2 XL using Tapatalk
EeZeEpEe said:
Must be an Android P issue. I don't notice a flicker when scrolling. I even changed from days, months, etc.
Click to expand...
Click to collapse
That's what I was thinking. Hopefully in DP2 it will be fixed
Same here, I made a bug report linked below. Please add your comments.
https://issuetracker.google.com/issues/78905843
TonikJDK said:
Same here, I made a bug report linked below. Please add your comments.
https://issuetracker.google.com/issues/78905843
Click to expand...
Click to collapse
Done
Me too
Yup, me too. Total display corruption when scrolling in Google Photos 3.19 . Android P dp1. Pixel 2 XL. DP2 should be days away!
I expect the fix will come from photos no P. And I hope I'm wrong.
---------- Post added at 01:16 AM ---------- Previous post was at 01:12 AM ----------
TonikJDK said:
I expect the fix will come from photos no P. And I hope I'm wrong.
Click to expand...
Click to collapse
Changing my answer. I now see several app compatibility issues as closed pending next update. So maybe it's will too.
Good job gang. They noticed our issue and asked me for more info, which I have provided.
TonikJDK said:
Good job gang. They noticed our issue and asked me for more info, which I have provided.
Click to expand...
Click to collapse
Hell yea that's good to hear
holla420 said:
I'm on Android P and today I noticed an update for Google photos app. So I downloaded it and it turns out to have broke something. When u roll up or down the screen flickers now. I have since then went back before the update. Is it just mines or anyone else on P can comfirm.
Click to expand...
Click to collapse
Came here to check if anyone else had this issue. I deleted the data/cache. That didn't fix it, like you, I deleted the update, and it did fix it.
dratsablive said:
Came here to check if anyone else had this issue. I deleted the data/cache. That didn't fix it, like you, I deleted the update, and it did fix it.
Click to expand...
Click to collapse
I'll give that a try. Thanks for sharing
holla420 said:
I'll give that a try. Thanks for sharing
Click to expand...
Click to collapse
I had to rollback to version 3.18.0.192689168 to get it working.
uicnren said:
I had to rollback to version 3.18.0.192689168 to get it working.
Click to expand...
Click to collapse
Yup that's what I did. The above method didn't work for me.
have the same problem
but i deleted the update apk and it works again.. the last update broke the app.. i hope they will fix the issue soon
i starred the issue
I loaded up DP2(Beta Update) and let the Google Photos update, problem is gone.
dratsablive said:
I loaded up DP2(Beta Update) and let the Google Photos update, problem is gone.
Click to expand...
Click to collapse
Hmm. I had this same issue with DP2 yesterday. I actually use the camera frequently, it was bothersome enough for me to revert to Oreo.
dratsablive said:
I loaded up DP2(Beta Update) and let the Google Photos update, problem is gone.
Click to expand...
Click to collapse
Same here, it is working fine now.
Very nice and the ambient service is now fully downloading. I'm enjoying dp2 how about u guys?
Hi Friends,
I Would Like To Inform You That, The February Update Has Been Rolled Out.
The Patch Is 240.5 MB
Thanks,
MUHAMMAD asif Qasim
I updated it and it seems useless!!
Patch notes?
The Only One Thing I Have Noticed i.e Sim Color Name. Now It Is In English...
Did anyone test if the "mark as read" option on Whatsapp/Telegram notifications works after this update?
aasiaasi said:
The Only One Thing I Have Noticed i.e Sim Color Name. Now It Is In English...
Click to expand...
Click to collapse
And that, my friend, is a major improvement. I was wondering when it will be in English.
Sent from my Mi A2 Lite using Tapatalk
Just updated, now i can't even connect to unsecured wifi...even release is getting worse, i'm regretting that i haven't buyed the note 5 instead.
Flashed stock 10.0.3 with fastboot but OTA not work.
Gcam works well again with hass31 version until now since the february Update, also the blinking un youtube and chrome seems solved
Camera 2 and WiFi calling enabled by any chance?
It would be a miracle if they did but doubt it, wishful thinking.
Aside from the SIM color bug, the Wi-Fi MAC Address bug was also fixed with this update. The phone's MAC Address is back to what it was on Oreo.
Strider Nemesis said:
Aside from the SIM color bug, the Wi-Fi MAC Address bug was also fixed with this update. The phone's MAC Address is back to what it was on Oreo.
Click to expand...
Click to collapse
Yes You are Right.
I Can Also Confirm That, The Mentioned Bugs Have Also Been Fixed In February Update.
Thanks,
MUHAMMAD Asif Qasim
Has anyone already updated from 10.0.3.0 having Magisk?
What steps did work?
krzygaj said:
Has anyone already updated from 10.0.3.0 having Magisk?
What steps did work?
Click to expand...
Click to collapse
This method worked for me:
https://forum.xda-developers.com/mi-a2-lite/how-to/guide-install-magisk-proper-support-ota-t3836952
BJumperBR said:
This method worked for me:
https://forum.xda-developers.com/mi-a2-lite/how-to/guide-install-magisk-proper-support-ota-t3836952
Click to expand...
Click to collapse
Thanks - will try after making backup preventively
yaco96 said:
Gcam works well again with hass31 version until now since the february Update, also the blinking un youtube and chrome seems solved
Click to expand...
Click to collapse
Focus issue persists.
Slow 2.4ghz Wifi when Bluetooth ON seems to be fixed for me? Other impressions?
edit: not fixed. my mistake. With BT ON I'm downloading with 2-3 mb/s, if it's turned off 4-5 mb/s (full speed).
Can't believe they couldn't fix this issue yet.
No update for big regular A2 this ? I'm getting less and less patient with this [email protected] very soon I'm going to sell this pos cheap and return to Nokia. Only thing innit that stands alright is the camera and even that's bugged with bad focus on close up objects and gets black flickering on the view finder
To be honest, Android one sucks!
Medo22 said:
To be honest, Android one sucks!
Click to expand...
Click to collapse
To be honest, it doesn't. You just don't like it as much as other ROMs.
I just got notified that my pixel 6 pro will update to A13 in two days, and there seems to be nothing I can do about it.
Does anyone know how to block it and stop any future updates? I've already got 'automatic updates' turned off, but that isn't stopping it.
What do I need to freeze, or what command line do i need to run, to clean this up and stop updates, especially A13?
I assume if your phone rooted, automatically updating will fail
It doesn't, and I lose root, that's what I thought last security update— which is why i'm concerned
christiebunny said:
I just got notified that my pixel 6 pro will update to A13 in two days, and there seems to be nothing I can do about it.
Does anyone know how to block it and stop any future updates? I've already got 'automatic updates' turned off, but that isn't stopping it.
What do I need to freeze, or what command line do i need to run, to clean this up and stop updates, especially A13?
Click to expand...
Click to collapse
Yes tap build 7 times for Developer Settings and disable automatic updatea
You could unlock the bootloader (which would require a device wipe) and then reinstall your current build of Android manually. That would be one of the only ways to officially disable automatic updates as well as update notifications.
I don't think that there's any way you'll be able to permanently avoid it. At least one other person who was rooted on Android 12 got the OTA to 13 even though they had automatic updates already disabled and it actually installed successfully - they lost root until they manually re-rooted it, but it was a surprise it updated successfully via OTA.
You may be able to delay it some buy factory resetting and some other things, but it's a big "maybe", and ultimately I don't think there's any way for you to avoid it.
biggiesmalls657 said:
Yes tap build 7 times for Developer Settings and disable automatic updatea
Click to expand...
Click to collapse
The OP you quoted says:
christiebunny said:
I've already got 'automatic updates' turned off, but that isn't stopping it.
Click to expand...
Click to collapse
roirraW edor ehT said:
I don't think that there's any way you'll be able to permanently avoid it. At least one other person who was rooted on Android 12 got the OTA to 13 even though they had automatic updates already disabled and it actually installed successfully - they lost root until they manually re-rooted it, but it was a surprise it updated successfully via OTA.
Click to expand...
Click to collapse
I "think" I've seen 3 instances of where someone was rooted but successfully completed the OTA, although 2 may have been from the same person. Maybe it was even the same person mentioning it 3 times, lol. Not really sure.
Makes me wonder if they removed the pre-OTA block verifications when going from A12 to A13 or just a fluke situation.
Lughnasadh said:
I "think" I've seen 3 instances of where someone was rooted but successfully completed the OTA, although 2 may have been from the same person. Didn't go back to check the posts.
Click to expand...
Click to collapse
I think I've seen more than one person report this too, but wasn't sure, and as I always say, I keep forgetting the old stuff. What was I talking about?
Lughnasadh said:
Makes me wonder if they removed the pre-OTA block verifications when going from A12 to A13 or something else is going on.
Click to expand...
Click to collapse
I suspect (but pretty obvious) that they have ways of force-pushing updates through despite the automatic update setting (or it's broken in typical Google fashion), but I think it's the former.
Then I believe they made a command decision that the vulnerability is too bad and that they felt they must force it on everyone. Again, given Google's reputation, this could've easily been an accident as well - "who pushed the red button!?!?!?"
And then the further command decision to push over top of modded, or at least simply rooted, devices as much as possible. I wonder what happens in the case someone has truly modified their software more aggressively at the root level. It wouldn't surprise me if it would've still overridden in those cases.
While, of course, those would be questionable actions for them to take (if these are actually true in the first place), I either partially or mostly agree with them, but just on principle, I can't wholeheartedly agree with them. Somewhere in the 40%-99% range.
If true, hopefully this is a very rare occurrence and not going to be how it is from now on. I will wait patiently to observe how things go.
What's the reason for avoiding the update? A13 is a pretty minor update from A12.1. In fact, I'd go so far as to say they should have called it A12.2.
96carboard said:
What's the reason for avoiding the update? A13 is a pretty minor update from A12.1. In fact, I'd go so far as to say they should have called it A12.2.
Click to expand...
Click to collapse
this exactly I also want to know, is there any reason for not upgrading to A13 when coming from A12?
Only thing I could think of is some apps which might not yet work on A13...but thats about it?!
Annil said:
this exactly I also want to know, is there any reason for not upgrading to A13 when coming from A12?
Only thing I could think of is some apps which might not yet work on A13...but thats about it?!
Click to expand...
Click to collapse
V4A, at least in my case. I'm not updating until its compatible, or I find a better alternative.
96carboard said:
What's the reason for avoiding the update? A13 is a pretty minor update from A12.1. In fact, I'd go so far as to say they should have called it A12.2.
Click to expand...
Click to collapse
Android 13 cannot be modified is one reason...
Tulsadiver said:
Android 13 cannot be modified is one reason...
Click to expand...
Click to collapse
I'm concerned about app compatibility, magisk, and how much control I'll lose.
As it is, even on 12, I can't change anything in /system, it's locked RO. I'm tired of not having control over a phone I paid for that's supposedly 'unlocked', but isn't
Tulsadiver said:
Android 13 cannot be modified is one reason...
Click to expand...
Click to collapse
Could you explain your theory on this?
christiebunny said:
I'm concerned about app compatibility, magisk, and how much control I'll lose.
As it is, even on 12, I can't change anything in /system, it's locked RO. I'm tired of not having control over a phone I paid for that's supposedly 'unlocked', but isn't
Click to expand...
Click to collapse
Compatibility seems remarkably intact, magisk works as intended, and there is no evidence of any change in what control you have.
96carboard said:
Could you explain your theory on this?
Click to expand...
Click to collapse
Modified SystemUI bootloops.
Tulsadiver said:
Modified SystemUI bootloops.
Click to expand...
Click to collapse
Ok? How are you modifying it?
96carboard said:
Ok? How are you modifying it?
Click to expand...
Click to collapse
Same way I always have.
Tulsadiver said:
Same way I always have.
Click to expand...
Click to collapse
That answer really doesn't help anyone.
96carboard said:
That answer really doesn't help anyone.
Click to expand...
Click to collapse
Any like these:
Stand alone Clock, Navbargone, Battery Icon Gone, etc. Mods
For stock rooted only. For most part, these cannot be flashed together. These mods use the SystemUI Patcher Module Template by @Jai_08 By @cool_modules on telegram. After Installing this module, your screen will relock after every reboot of...
forum.xda-developers.com