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
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
Are there any important difference between NOF26V and NDE63P updates? Any advantages or disadvantages between the two?
I have a Verizon Pixel XL that arrived about a week ago. It came with NDE63P. I immediately enabled developer options and disabled automatic system updates. I have not yet decided if I am going to unlock the bootloader, and I am not asking for advice on whether or not I should. I am trying to keep my options open. I like to keep things simple, which is why I like the Nexus and Pixel phones. Taking an OTA is much easier than sideloading an update. But there are still good reasons to unlock/root.
I am still weighing my options. I don't feel any need to rush right now.
I've read of people having bluetooth or battery issues, none of which I am experiencing right now on NDE63P. Until I make a decision, is there anything other than current security updates that NOF26V fixes or breaks?
Thanks!
Here is a great big disadvantage to taking it as your device sits now. Any ota you take before unlocking the bootloader renders it un-unlockable. So, theres your choice. Unlock and take any otas you want and maintain the ability to customize or not, or, leave it locked, take an ota, and no more choices. You decide.
Sent from my VK810 4G using Tapatalk
wyrdtrtle said:
Here is a great big disadvantage to taking it as your device sits now. Any ota you take before unlocking the bootloader renders it un-unlockable. So, theres your choice. Unlock and take any otas you want and maintain the ability to customize or not, or, leave it locked, take an ota, and no more choices. You decide.
Sent from my VK810 4G using Tapatalk
Click to expand...
Click to collapse
I am completely aware of that. That is why I disabled automatic system updates, so I can make this decision after I have had a chance to use the device and decide what changes, if any, I want to make. I am just trying to make an informed decision on my own.
Are there any key differences, pros or cons, between NDE63P and the current NOF26V?
stm8 said:
I am completely aware of that. That is why I disabled automatic system updates, so I can make this decision after I have had a chance to use the device and decide what changes, if any, I want to make. I am just trying to make an informed decision on my own.
Are there any key differences, pros or cons, between NDE63P and the current NOF26V?
Click to expand...
Click to collapse
Many people have disabled the updates but then it mysteriously updates itself and then cry for an unlock, so we are warning you is all. The difference between the 2 is mainly security updates but they did add a few features, like waking the phone can't remember exactly what. Some small tweaks and fixes too. There's change logs somewhere.
jjayzx said:
Many people have disabled the updates but then it mysteriously updates itself and then cry for an unlock, so we are warning you is all. The difference between the 2 is mainly security updates but they did add a few features, like waking the phone can't remember exactly what. Some small tweaks and fixes too. There's change logs somewhere.
Click to expand...
Click to collapse
Thanks. I have read about the mystery updates happening despite disabling automatic updates.
I'll review the change logs, but Google doesn't usually list their "bugs" in the change logs...
The Bluetooth issues seem the typical phantom Android issues that come and go. There are the emoji and long press shortcuts that come with 7.1.1. That is about it, not much has changed.
So I don't think you need to update any time soon.
stm8 said:
I am still weighing my options. I don't feel any need to rush right now.
Click to expand...
Click to collapse
Weighing your options? You have 2 options, unlock or don't unlock. What's the dilemma? Ok, so here ya go. 50% say unlock and the other 50% say stay locked. Solved?
bobby janow said:
Weighing your options? You have 2 options, unlock or don't unlock. What's the dilemma? Ok, so here ya go. 50% say unlock and the other 50% say stay locked. Solved?
Click to expand...
Click to collapse
I am not asking advice about whether or not to unlock, just the differences/bugs/upgrades between these updates.
TonikJDK said:
The Bluetooth issues seem the typical phantom Android issues that come and go. There are the emoji and long press shortcuts that come with 7.1.1. That is about it, not much has changed.
So I don't think you need to update any time soon.
Click to expand...
Click to collapse
Thanks, I appreciate it. That's the kind of info I am looking for!
stm8 said:
I am not asking advice about whether or not to unlock, just the differences/bugs/upgrades between these updates.
Click to expand...
Click to collapse
I understand that but you first need to decide if you're going to unlock or keep the bootloader locked. Because, at some point you "will" upgrade whether or not you are in a rush. I'm just not getting your dilemma. Google has resources which you can search that outline what has changed besides the security updates which you obviously should get. And as you know if you stay locked and update then you're stuck. So once again, your options are to lock or unlock not whether to update or not.
TonikJDK said:
The Bluetooth issues seem the typical phantom Android issues that come and go. There are the emoji and long press shortcuts that come with 7.1.1. That is about it, not much has changed.
So I don't think you need to update any time soon.
Click to expand...
Click to collapse
Are you certain?
https://www.google.com/amp/www.gott...ruary-android-nougat-update-what-to-know/amp/
Sent from my Pixel using XDA-Developers Legacy app
bobby janow said:
Are you certain?
https://www.google.com/amp/www.gott...ruary-android-nougat-update-what-to-know/amp/
Sent from my Pixel using XDA-Developers Legacy app
Click to expand...
Click to collapse
I wasn't 100 percent sure until your link, thanks. From the article:
"From what we’re seeing and hearing the February Android 7.1.1 Nougat update doesn’t actually have any other changes. There are no new features, bug fixes, or performance tweaks. This is simply a security update, like we can expect to see at the beginning of each month."
TonikJDK said:
I wasn't 100 percent sure until your link, thanks. From the article:
"From what we’re seeing and hearing the February Android 7.1.1 Nougat update doesn’t actually have any other changes. There are no new features, bug fixes, or performance tweaks. This is simply a security update, like we can expect to see at the beginning of each month."
Click to expand...
Click to collapse
The problem is that Google doesn't exactly advertise or even admit to any bugs introduced in their updates, whether it's firmware or applications.
stm8 said:
The problem is that Google doesn't exactly advertise or even admit to any bugs introduced in their updates, whether it's firmware or applications.
Click to expand...
Click to collapse
Very true, and Google doesn't disclose fixes much either. So all we can do is give the OP our opinion and experience. I have not seen any bugs fixed, or seen any introduced on my phone. So if he wants to wait while he decides on unlocking i dont think he is missing much. I stand by my advice.
TonikJDK said:
Very true, and Google doesn't disclose fixes much either. So all we can do is give the OP our opinion and experience. I have not seen any bugs fixed, or seen any introduced on my phone. So if he wants to wait while he decides on unlocking i dont think he is missing much. I stand by my advice.
Click to expand...
Click to collapse
But you selectively left out the important part.
Overall we spotted 35 changes to the February Nougat release. At least according to Google’s security blog and change log. That said, eight of them were considered “critical” and needed to be addressed right away.
It's ridiculous to wait. There are bug fixes, You just need to search for them. Personally I don't care what he does, but then he is taking a security chance. I think your advice is wrong. His choice.
Sent from my Pixel using XDA-Developers Legacy app
Just curious if anyone has side loaded and is running Android P beta. And what's broken, etc.
I am.
letrain02 said:
Just curious if anyone has side loaded and is running Android P beta. And what's broken, etc.
Click to expand...
Click to collapse
yes.
https://developer.android.com/preview/release-notes.html
uicnren said:
yes.
https://developer.android.com/preview/release-notes.html
Click to expand...
Click to collapse
Thanks for that. Figured since it was released through the beta program as an OTA there still might be early issues... "Slow and janky" clarified that. Doesn't seem there is anything too horrible that doesn't work.
In your opinion could this still be a daily driver? Of course that always depends on what your doing with your phone.
letrain02 said:
Thanks for that. Figured since it was released through the beta program as an OTA there still might be early issues... "Slow and janky" clarified that. Doesn't seem there is anything too horrible that doesn't work.
In your opinion could this still be a daily driver? Of course that always depends on what your doing with your phone.
Click to expand...
Click to collapse
Just flash it and try it, if you don't like it flash back to O
dobbs3x said:
Just flash it and try it, if you don't like it flash back to O
Click to expand...
Click to collapse
Wouldn't I lose all my data? And past experience had showed me going backwards after major updates means restore doesn't work right...
letrain02 said:
Wouldn't I lose all my data? And past experience had showed me going backwards after major updates means restore doesn't work right...
Click to expand...
Click to collapse
Than don't even worry about the "developer" release and keep on Oreo.
letrain02 said:
Wouldn't I lose all my data? And past experience had showed me going backwards after major updates means restore doesn't work right...
Click to expand...
Click to collapse
It's not an official release. You'd be fine going back to O. You'd have to clean flash O more than likely. So back up stuff for sure :good:
Badger50 said:
It's not an official release. You'd be fine going back to O. You'd have to clean flash O more than likely. So back up stuff for sure :good:
Click to expand...
Click to collapse
Just remembering my Nexus 6p and beta testing and trying to restore from Google backup wouldn't work..
Has anyone running it noticed the slow and janky-ness?
letrain02 said:
Just remembering my Nexus 6p and beta testing and trying to restore from Google backup wouldn't work..
Click to expand...
Click to collapse
I understand bruh. Was just reading on another thread where a user apparently did just that though :good:
Badger50 said:
I understand bruh. Was just reading on another thread where a user apparently did just that though :good:
Click to expand...
Click to collapse
Sweet. Thanks for help everyone.
letrain02 said:
Sweet. Thanks for help everyone.
Click to expand...
Click to collapse
I'd still hold off for a little while until it's been done a couple times just to make sure though. Although, I can't think of why it can't be done since it's not an official release yet.
letrain02 said:
Thanks for that. Figured since it was released through the beta program as an OTA there still might be early issues... "Slow and janky" clarified that. Doesn't seem there is anything too horrible that doesn't work.
In your opinion could this still be a daily driver? Of course that always depends on what your doing with your phone.
Click to expand...
Click to collapse
So far havent found any show-stoppers. A few apps dont work. Google Pay is being weird about adding cards, though I have some added.
If you dont mind running into some bugs, then so far, it seems stable enough, but wont really know til after using it for a day.
uicnren said:
So far havent found any show-stoppers. A few apps dont work. Google Pay is being weird about adding cards, though I have some added.
If you dont mind running into some bugs, then so far, it seems stable enough, but wont really know til after using it for a day.
Click to expand...
Click to collapse
you mind saying which apps? might not even apply to me. did you do the OTA or Factory image? i can't seem to find the OTA Android P, only the factory images on their site..i found a link from the XDA article for the OTA.
letrain02 said:
you mind saying which apps? might not even apply to me. did you do the OTA or Factory image? i can't seem to find the OTA Android P, only the factory images on their site..i found a link from the XDA article for the OTA.
Click to expand...
Click to collapse
so far the MyATT app crashes every open.
FiSwitch app, widget doesnt seem to work at all.
CustomNavigation bar app opens, but cannot be enabled due to Android version issue (also possible because Google seems to have gotten rid of system ui tuner altogether, or there is a new way you have to enable it that I havent found).
SolidExplorer gives a toast about API compatibility issue, but so far seems to work fine. I did have to delete and re-add cloud storage providers.
Off-hand, those are all I can think of, still have more to go through.
I installed factory images, did full wipe. In the past, when I have installed new OS with images, and deleted the -w (wipe user data flag) there were always issues, so I did clean install.
So far apps such as LightFlow, KWGT, CallFlash, things of that nature seem to be fine.
uicnren said:
So far havent found any show-stoppers. A few apps dont work. Google Pay is being weird about adding cards, though I have some added.
If you dont mind running into some bugs, then so far, it seems stable enough, but wont really know til after using it for a day.
Click to expand...
Click to collapse
uicnren said:
so far the MyATT app crashes every open.
FiSwitch app, widget doesnt seem to work at all.
CustomNavigation bar app opens, but cannot be enabled due to Android version issue (also possible because Google seems to have gotten rid of system ui tuner altogether, or there is a new way you have to enable it that I havent found).
SolidExplorer gives a toast about API compatibility issue, but so far seems to work fine. I did have to delete and re-add cloud storage providers.
Off-hand, those are all I can think of, still have more to go through.
I installed factory images, did full wipe. In the past, when I have installed new OS with images, and deleted the -w (wipe user data flag) there were always issues, so I did clean install.
So far apps such as LightFlow, KWGT, CallFlash, things of that nature seem to be fine.
Click to expand...
Click to collapse
https://www.xda-developers.com/android-p-blocks-custom-overlays-substratum-themes/
Delete.
dobbs3x said:
Than don't even worry about the "developer" release and keep on Oreo.
Click to expand...
Click to collapse
Why are people here so helpful?
here we go! did the OTA from the xda thread. article... whats the worst thing to happen? clean install and stability? thanks for the help anyone. hope this helped some others as well.. https://www.xda-developers.com/android-p-developer-preview-1-google-pixel-xl-pixel-2-xl/
https://source.android.com/security/bulletin/pixel/2018-10-01
Announcements
There are no Pixel or Nexus security patches in the October 2018 Pixel / Nexus Security Bulletin.
Click to expand...
Click to collapse
:angel: :cyclops:
Seems like we're back to not being able to push the updates through
murso74 said:
Seems like we're back to not being able to push the updates through
Click to expand...
Click to collapse
I don't understand. I downloaded and adb sideloaded the October OTA minutes after it posted. I had no problem whatsoever.
My comment was about the "security update" having no security updates / patches.
Still September Patch Level?
Pkt_Lnt said:
I don't understand. I downloaded and adb sideloaded the October OTA minutes after it posted. I had no problem whatsoever.
My comment was about the "security update" having no security updates / patches.
Click to expand...
Click to collapse
After upgrading to the October image, does you system show though that the system security patch level is still September, 2018?
cmexec said:
After upgrading to the October image, does you system show though that the system security patch level is still September, 2018?
Click to expand...
Click to collapse
No, shows October 5 2018 which is crazy, because I got the update on October 1, and did not know the P2XL was a time machine to take me into the future! :cyclops:
Pkt_Lnt said:
https://source.android.com/security/bulletin/pixel/2018-10-01
:angel: :cyclops:
Click to expand...
Click to collapse
Update took ages for me. The download and the install was sooooo slow... . After the update (one full day) I have about 25-30% less battery with the same usage.
(This is not a real measure, just a feeling)
Charged faster over 90% (sometimes it says @95% : 18 mint to max. Now It was faster.
It was not on the change log list but I have less display flickering during the environmental light changes...
And Now the notification led alerts are sometimes not working with some apps. (example Gmail.)
Maybe I'm going to reset my phone.
And yes I'm on Oct 5. security update
still no update for me. Shouldnt we all have access to the update ?
Relayers said:
still no update for me. Shouldnt we all have access to the update ?
Click to expand...
Click to collapse
You do too have access.
https://developers.google.com/android/ota#instructions
You have a Pixel phone and you are an XDA member, nothing stopping you.
It was posted yesterday morning and I had my phone update within 15 minutes. :good:
Pkt_Lnt said:
You do too have access.
https://developers.google.com/android/ota#instructions
You have a Pixel phone and you are an XDA member, nothing stopping you.
Click to expand...
Click to collapse
useless comment, well done !
Relayers said:
useless comment, well done !
Click to expand...
Click to collapse
XDA Developers gives you the knowledge and tools to do it yourself instead of sitting around waiting for someone else to do it for you. Use that knowledge and tools to take control of your phone! :good:
Pkt_Lnt said:
XDA Developers gives you the knowledge and tools to do it yourself instead of sitting around waiting for someone else to do it for you. Use that knowledge and tools to take control of your phone! :good:
Click to expand...
Click to collapse
I know more than you, wake up kiddo.
I asked about pushed OTA, you replied about XDA and sideloading. Do you understand what you did ? Probably not. I blame your parents (and Trump).
Relayers said:
I know more than you, wake up kiddo.
I asked about pushed OTA, you replied about XDA and sideloading. Do you understand what you did ? Probably not. I blame your parents (and Trump).
Click to expand...
Click to collapse
Seems not.....you obviously dont understand how the push happens....short answer is no, not everyone has access to it at the same time. android 101.
Pkt_Lnt said:
No, shows October 5 2018 which is crazy, because I got the update on October 1, and did not know the P2XL was a time machine to take me into the future! :cyclops:
Click to expand...
Click to collapse
Same for me, also Oct. 5 security level
cmh714 said:
Seems not.....you obviously dont understand how the push happens....short answer is no, not everyone has access to it at the same time. android 101.
Click to expand...
Click to collapse
Yet he "knows more than you do"... and probably more than anyone else on xda
Relayers said:
I know more than you, wake up kiddo.
I asked about pushed OTA, you replied about XDA and sideloading. Do you understand what you did ? Probably not. I blame your parents (and Trump).
Click to expand...
Click to collapse
@Pkt_Lnt fully understands what he did, but you apparently missed his point. Then again, you claim to know more than he does. And yet you still have so much to learn.
Regards,
Someone who has forgotten more than what you've learned.
reporting back: finally got the OTA, I guess I should have remembered its always around the 5th of the month.
Relayers said:
reporting back: finally got the OTA, I guess I should have remembered its always around the 5th of the month.
Click to expand...
Click to collapse
Well good. Guess you can't blame the parents or (Trump) anymore! :laugh:
I still haven't gotten the update.
t2jbird said:
I still haven't gotten the update.
Click to expand...
Click to collapse
Updates are staged and not everyone will receive one the first day. Download the update from Google's servers and sideload it if you don't want to wait.
t2jbird said:
I still haven't gotten the update.
Click to expand...
Click to collapse
Are you enrolled in the Android Beta Program? Try un-enrolling. Then, check for updates again. The OTA should be pulled to your device this time round.
Hi, I'm still on OS11, and I would like to know if there are any commands via adb to block future updates. I'd appreciate any help!
Adelino80 said:
Hi, I'm still on OS11, and I would like to know if there are any commands via adb to block future updates. I'd appreciate any help!
Click to expand...
Click to collapse
Turn off auto updates in developer settings
https://www.hardreset.info/devices/oneplus/oneplus-9-pro/developer-options/#:~:text=Developer%20Options%20OnePlus%209%20Pro%201%20Firstly%2C%20turn,option%20and%20find%20Developer%20options.%207%20Good%20job%21
can you use app inspector to search "update" in app list and post me the results
TheGhost1951 said:
https://www.hardreset.info/devices/oneplus/oneplus-9-pro/developer-options/#:~:text=Developer%20Options%20OnePlus%209%20Pro%201%20Firstly%2C%20turn,option%20and%20find%20Developer%20options.%207%20Good%20job%21
Click to expand...
Click to collapse
Thanks! Turned the option off!
do you like insecure system with 2Y old security patch? gg.
Hildanew said:
do you like insecure system with 2Y old security patch? gg.
Click to expand...
Click to collapse
Unfortunately, the Kennel is never updated by the manufacturers and therefore remains a security risk
ChrisFeiveel84 said:
Unfortunately, the Kennel is never updated by the manufacturers and therefore remains a security risk
Click to expand...
Click to collapse
Kernel is majority updated with ever major Android. btw, every Kernel is patched by regular Google updates like different supported builds Windows..
Good question, I am also still on A11 oxygen OS. It is smooth and stable. Why would I be crazy enough to update?
We also need instructions on how to prevent google play services annoying nag messages about old firmware updates. Anyone know how to stop google play from annoying us?
Mandy $ingh said:
can you use app inspector to search "update" in app list and post me the results
Click to expand...
Click to collapse
Update for what?
Hildanew said:
do you like insecure system with 2Y old security patch? gg.
Click to expand...
Click to collapse
Who you referring to?
immortalwon said:
Good question, I am also still on A11 oxygen OS. It is smooth and stable. Why would I be crazy enough to update?
We also need instructions on how to prevent google play services annoying nag messages about old firmware updates. Anyone know how to stop google play from annoying us?
Click to expand...
Click to collapse
Try turning off notifications....maybe?
on oos 13 use pm uninstall -k --user 0 com.oplus.ota using adb if you want to do the hard disable system update
TheGhost1951 said:
Who you referring to?
Click to expand...
Click to collapse
for someone who want stay on OOS11 now with "2y" old security patch.
Hildanew said:
for someone who want stay on OOS11 now with "2y" old security patch.
Click to expand...
Click to collapse
if you mean slowing down your phone, then yes, security patches are great!
An example: On windows 10, the original 1607 ltsb 2016 is probably the fastest and most smooth OS I ever used on win 10 series. Unfortunately if you install the "security patches", it becomes slow and high latency.
Same goes for android devices.
If you know what you are doing, then you don't need patches.
TheGhost1951 said:
Update for what?
Who you referring to?
Try turning off notifications....maybe?
Click to expand...
Click to collapse
I did, but I was wondering if there is a specific component u can disable from play services instead of turning off notification?
immortalwon said:
if you mean slowing down your phone, then yes, security patches are great!
An example: On windows 10, the original 1607 ltsb 2016 is probably the fastest and most smooth OS I ever used on win 10 series. Unfortunately if you install the "security patches", it becomes slow and high latency.
Same goes for android devices.
If you know what you are doing, then you don't need patches.
Click to expand...
Click to collapse
No man. If even, I'd rather be safe than fail. As with Meltdown and Spectre. Safety is safety and there is no other option for my good..
Hildanew said:
No man. If even, I'd rather be safe than fail. As with Meltdown and Spectre. Safety is safety and there is no other option for my good..
Click to expand...
Click to collapse
Propaganda, but you do you buddy. Sounding like a Google / security researcher shill. The average person doesn't need all these security patches. Unless you work in a high level government or military field, security is pointless. I don't need nanny updates from google to tell me how to use my device.
immortalwon said:
Propaganda, but you do you buddy. Sounding like a Google / security researcher shill. The average person doesn't need all these security patches. Unless you work in a high level government or military field, security is pointless. I don't need nanny updates from google to tell me how to use my device.
Click to expand...
Click to collapse
Have heard in the news about a rampant problem of androids being hacked.
No but sounds interesting. I would like to reiterate I am not fully against patching and updating a device / firmware to latest for security reasons. All I am saying is that a person should have the ability to block updates on an android or any other electronic device for that matter, not to be forced by Google or another megalithic corporation to move to the latest.
1) I fully agree that a user should have the right to not update
2) why a user would subject himself at a constant security risk is beyond me, but I strongly support his right to do whatever he wants
Freewill, freedom of choice be it good or bad. In that it is a matter of opinion, but it is still their choice! God gave us freewill, do we choose Him or choose the world? That is the single biggest choice one has to make!