Before *Android OS 16*'s last update (to build # BP3A.250905.014), it was possible to use programs such as *Google Messages* to send or receive **SMS** messages. But as of BP3A.250905.014, **SMS** messages sent to you (which are required to login to your government accounts, or to use social services, or bank apps such as *Well's Fargo*, or to login to your *Google* account if you are stuck with 2-factor-authentication) are not shown, and you can not send **SMS** messages:  . If you click "More ways to veridy", Google's 2-factor-authentication has an option to enter a code for account access, but [build BP3A.250905.014 breaks the input box (the text input which you enter the code into)](https://android.stackexchange.com/questions/262261/after-system-update-to-bp3a-250905-014-you-cannot-use-bluetooth-keyboard-to) . If you can disable 2-factor-authentication, that is a possible solution, but do not know how to. How to restore **SMS**? - Do you have to undo the update (roll back to the old version) to restore this ("Alt + Tab" switches)? Have the stock *Android OS* (not [**AOSP**](https://source.android.com/) , which includes sudo); is it possible to go back to the old version on devices without sudo? - Do you have to purchase a new phone (and remember to disable all processes related to "updates" / "provisioning" (and *Google* still asks, refuse those))? - If you can not refuse those: use without the **SIM** card (so *Google* can not force those), or [switch to a new **OS** (such as *Ubuntu Phone*) which allows you to use your phone](https://android.stackexchange.com/questions/57674/ubuntu-for-android) ?

After *Android OS*'s last system "update" (to build # BP3A.250905.014) you cannot use *Bluetooth* keyboards to enter 2-factor-authentication codes to access your Google accounts. If you focus the input box, all keypresses cause the input box to lose focus, so that you can not enter your code. How to restore *Google* access? - Do you have to undo the update (roll back to the old version) to restore this ("Alt + Tab" switches)? Have the stock *Android OS* (not [**AOSP**](https://source.android.com/) , which includes sudo); is it possible to go back to the old version on devices without sudo? - Do you have to purchase a new phone (and remember to disable all processes related to "updates" / "provisioning" (and *Google* still asks, refuse those))? - If you can not refuse those: use without the **SIM** card (so *Google* can not force those), or [switch to a new **OS** (such as *Ubuntu Phone*) which allows you to use your phone](https://android.stackexchange.com/questions/57674/ubuntu-for-android) ? If you press "More ways to veridy", there is a option to use **SMS**, but build # BP3A.250905.014 also [breaks **SMS**](https://android.stackexchange.com/questions/262245/build-bp3a-250905-014-prevents-you-from-sending-or-receiving-sms-messages-which) .

Before *Android OS 16*'s last update (to build # BP3A.250905.014), Home settings had Allow home screen rotation (if enabled, this uses the accelerometer so that home is vertical if the phone is vertical, or horizontal if the phone is horizontal. - This was the sole option that allowed you to hide the *Google* search bar; if you disabled the *Google* app and enabled this option, then when your phone is horizontal, the *Google* search bar does not show.  But BP3A.250905.014 replaces this option with Landscape mode (which is a permanent on/off switch). - It is now not possible to hide the *Google* search bar unless you replace the stock launcher (such as with *Nova Launcher*, which is not recommended). With the new Landscape mode, even with the *Google* app disabled and the phone horizontal, the *Google* search bar shows.  How to restore the old home view? - Do you have to undo the update (roll back to the old version) to restore this ("Alt + Tab" switches)? Have the stock *Android OS* (not [**AOSP**](https://source.android.com/) , which includes sudo); is it possible to go back to the old version on devices without sudo? - Do you have to purchase a new phone (and remember to disable all processes related to "updates" / "provisioning" (and *Google* still asks, refuse those))? - If you can not refuse those: use without the **SIM** card (so *Google* can not force those), or [switch to a new **OS** (such as *Ubuntu Phone*) which allows you to use your phone](https://android.stackexchange.com/questions/57674/ubuntu-for-android) ?

System updates is **forcing** update to be performed over WIFI. Is there a download from Motorola for APK for upgrading to Android 15? Is there a setting I am missing that will download system update OTA?

I bought a refurbished Chromebook on Amazon and didn't know it couldn't be updated. That part isn't mentioned anywhere in the sellers description. I cannot install any chrome extensions because Chrome is out of date. (It wont even update chrome browser let alone the system) My Chromebook is useless to me if I cannot get some of the extensions I need. I read somewhere that Chrome extensions can be installed without the chrome web store. I've tried figuring something out on my own, but I'm so computer illiterate it's not even funny. **Can install Chrome extensions from somewhere other than Chrome Store?**

Some apps implement logic that requires a query every time data is activated on the smartphone. This consists of a conditional block such as: if a new version is available, then force the update or automatically block. This prevents the user from continuing to use the app unless they comply with the request. I noticed that the auto-block and the caption that refers the user to the update are standardized (comparison between different apps); this raises a question: is this code due to Google, meaning it's generated by the APK package installer created, for example, with Android Studio?

My Motorola stylus won't call out. I can text and receive calls but I can't make a phone call . What can I do to make it work

I went ahead and let my phone update itself and since then it's been really SLOW. Phone calls take 5-45 seconds to connect, which is beyond aggravating. Apps don't run as fast as they use to. And I am constantly reconnecting the Mobile network because it keeps losing it. Anyone have similar and get around it??

I often receive the following error message when attempting to perform Android security updates: > There was a network error while downloading the update. Please try again later or connect to a different network. In researching this error message, it is apparent that many other people have been reporting the same issue for years: - Update cannot be downloaded on specific networks : GooglePixel https://old.reddit.com/r/GooglePixel/comments/10whijh/update_cannot_be_downloaded_on_specific_networks/ - Not able to update to android 15. Shows error in network while downloading although connected to WiFi - Google Pixel Community https://support.google.com/pixelphone/thread/322921191/not-able-to-update-to-android-15-shows-error-in-network-while-downloading-although-connected-towifi - Pixel 7 System Update Fails : GooglePixel https://old.reddit.com/r/GooglePixel/comments/ycejcz/pixel_7_system_update_fails/ - There was a network error while downloading the update. Please try again later or connect to a diffe - Google Pixel Community https://support.google.com/pixelphone/thread/205161477/there-was-a-network-error-while-downloading-the-update-please-try-again-later-or-connect-to-a-diffe Over the years, people have offered "magical" solutions, such as toggling WiFi on and off, which likely has nothing to do with the real issue. Yet some do claim that such actions have temporarily fixed the issue (not myself, though). What's even more odd is that those reporters have not indicated they made any additional changes. In Google's latest Android version, Android 16, this issue is still present. Ironically, the issue seems to be most prevalent on Google's own Pixel devices. Does anyone know what is causing this bug and how to actually fix it? Update --- A couple of our community members asked some good questions... here are the answers: - The issue occurs regardless of whether WiFi or carrier data is used. - I've seen the issue occur on many Google Pixel devices, starting with the Pixel 4. Online reports indicate it was present going back to at least the Pixel 2. I've seen this issue on several Samsung devices as well, although online reports of this issue tend to mention the Pixel devices more often than Samsung devices. - Regarding proxies, VPNs, or blocked ports/servers, I need to investigate further. It definitely happens on a wide range of devices and on a wide range of networks, but perhaps there is a common element that I can discover.

I have a Nokia G42 5G with Android 13. A week ago, a notification popped up, asking me to download the latest update (and also that that update was a week behind). Since the size was 2.67 GB, I decided to close the notification at the time; I would install it later. A quick search afterwards revealed that it was an upgrade to Android 14 . When I went to download it later (from Settings → System → System update, then Check for update), it keeps showing “Your system is up to date”. This is how it has been since. Now, I know that that is not the case because - there was that notification, - someone I know uses this very device (model) and they have already upgraded (means, it has been released in our location/market), and - one could check from Nokia’s Website that that update has been released. **My question is: how can I get that update?** I have installed Google Play system updates and what not. I have also cleared the ‘System cache’ app (don’t know what this app does) from Settings → Memory. I have tried using both WiFi and 5G data while the device was charged to full. **What else can I do?** May be allow unrestricted data access to some app? May be clear some cache to force fetch that update? I won’t flash a custom ROM but I am willing to reboot to safe mode or connect to a computer to clear some hidden cache or run some code. Technically, it seems to be possible to postpone updates ; the system will fetch them later . **Is it possible to reset that waiting period instead of waiting it out?** (If that has been the case; my device is my own, not managed.) ---------- On a related note: I recently had a run-in while installing the 2024-02 Cumulative Update for Windows 11 Version 23H2 for x64-based Systems (KB5034765) update on Windows 11. It downloaded, started installing, computer restarted, it installed all the way to 100%, and then rolled back with a . This happened quite a few times. I tried all kinds of solutions from all around. At the end, it turned out that all I had to do was rename/remove the

:\$WinREAgent

folder . And it worked in a snap! So, I know that software work in mysterious ways!

How does Google Play store decide to indicate that an application has a major update?

I have an APK of [Unlimited Call Log 3.1.1](https://apkhome.io/unlimited-call-log-3-1-1/) , but I am unable to install it on Samsung Galaxy S24+ running Android 14. When I tried to install it, an error comes: > App not installed as app isn't compatible with your phone. Can anyone help to solve this issue or upgrade to new Android level?

I want to dial *#*#2432546#*#* so aka *#*#checkin#*#* to check updates http://lifehacker.com/5719657/force-your-android-phone-to-check-for-a-system-update but when I press # in this place *#*#2432546# <- this place it clears and can't type all code Make: Goclever Model: Quantum 350 android version: jelly bean 4.2.2

On my Pixel phone, apps will download on Play Store, but once the download completes, it doesn't install. After some time, there's a notification from the Play Store that says > Google Play isn't responding. Try again in a few minutes, and if the problem continues, get help troubleshooting. (Error code: 927) Usually, if I restart the phone, the apps can be installed, but if I wait a few hours, I have to repeat the process. Does anyone know of a way to fix the issue permanently?

The Google app on my Pixel 6a just updated, and now ALL of my Google things I added to my home screen are GONE. I had SO MANY important things. Is there any way to get them all back?

My RCA Voyager Pro (Android 8.1.0) recently got a firmware update. Since the update, I have not been able to set a wallpaper without it "zooming in." Take these screenshots for example. When I select the image I want to use as my wallpaper, it allows me to choose the orientation and zoom before clicking "✓ Set Wallpaper." Before the update, the wallpaper would be set exactly as it looks in the preview. However, after the update, the wallpaper will become enlarged and will scroll as I swipe from right to left: Here is a side-by-side comparison of how the wallpaper is the in preview (before the wallpaper is set), and how it is on home screen (after the wallpaper is set): Is there a way I can disable this "auto-zooming?" I miss the way it used to be, where my wallpaper was the same on the home screen as it was in the preview, and did not "scroll" as I browsed my apps.

Is there a technical reason why Android phones general lag a lot behind the stable released version of Android? This applies to both new phones, for example a recent trip to the phone shop everything was 4.0 to 4.2.1, KitKat could not be seen. And also old phones, my girlfriend's iPhone 4 had an OTA update to the latest OS, this is a July 2010 phone, whilst a July 2010 Android is basically a paperweight. Presumably Android itself doesn't concern itself with the actual hardware, and thus talks to the OS via abstractions? I guess then the handset maker just provides the drivers for the specific hardware, thus I can't see the issue with pushing OTA updates if the ABI remains stable (my phone doesn't grow new hardware features).

Imagine the following situation: - The vendor of my phone has stopped providing security patches for the stock OS. - The HW is perfectly fine and powerful enough for years to come, so I'm definitely not willing to replace it just to get access to security patches. - Running a phone OS with unfixed security vulnerabilities makes me uneasy. (It feels insane enough to run a computer at home with an OS that's a year behind on security patches. It's twice as insane to do the same with a device that I routinely take to all kinds of hostile environments and untrusted networks.) - Authors of all kinds of random apps have grown a habit of requiring SafetyNet attestation. - I don't need root access to my phone, and I can live with losing some of the proprietary vendor-provided features. I also don't care too much about running the latest Android version, as long as it's receiving security fixes and is compatible with most apps. I know I have the following two options: - Stick to the stock vendor OS, which is gradually going to become full of security holes. However, SafetyNet passes and I can run all kinds of apps because they feel safe on my device. - Install a custom OS. This will fail SafetyNet, unless I use a tool to hack around it and try to pretend the phone is not rooted. This approach is likely to stop working at some point, leaving me with a device that fails SafetyNet. Thus although my device may have up-to-date security patches, apps will refuse to run because they deem the device insecure. **Is there a third way, which would let me stay up-to-date on security patches while not breaking SafetyNet?** I can imagine something like a pure AOSP system, perhaps built and signed by Google or another vendor, that I could run unrooted and unmodified (relying on vendor drivers through the Treble thing).

I have an Android tablet that I rooted to attempt to install a different OS. After I failed and restored my tablet to a backup that I had made earlier (it's still rooted), I tried to update Android. It checked for updates, and promptly displayed a box that said "Your device has been modified. Software updates are not available." Is there any way that I can update my tablet while it's rooted?

I recently was playing on my PC while I noticed an update on my Oneplus One. As every other update I just downloaded it and let it flash automatically. The next thing I noticed was that it just kept rebooting. I made a backup to my usb_otg in the TWRP recovery and clean-flashed CM13. My question now is, is there a way I can use the backup as a working backup? I tried to flash the new GApps and Xposed framework, which didn't work.