Google released Android 2.3.7 Gingerbread in September 2011.
What you need to know
- Google will begin blocking logins on devices running Android 2.3.7 or lower starting September 27.
- Google says the move is part of its ongoing efforts to keep its users safe.
- Users will receive a username or password error when trying to sign in on older Android versions.
Google has announced that it will no longer allow sign-in on Android devices running version 2.3.7 or lower starting September 27 (via Bleeping Computer).
If you try to sign in with your Google account on Android 2.3.7 Gingerbread or below after September 27, you will get username or password errors when accessing Google services such as Gmail, YouTube, and Maps.
The following actions will also be no longer possible on devices running Android 2.3.7 or older versions:
- Perform a factory reset and try to sign in.
- Change the Google account password on the device or on another device, which signs you out everywhere else. You will receive an error message when you try to sign in again.
- Remove your Google account from the device and re-add it.
- Create a new Google account on the device.
The change will only affect a small number of users, since Google's Android distribution numbers claim there are less than 1% active devices running Android versions older than Jelly Bean.
Google recommends users update to Android 3.0 or a newer version to maintain access to its apps and services. While users with devices running Android version 2.3.7 or lower will no longer be able to sign in to their account to use most Google products and services, they can continue to access some Google services when logged in using the best Android browsers.
Google Pixel 4a
$349 at Amazon $350 at Best Buy $349 at B&H
If you're looking for a new budget Android phone, Google's Pixel 4a is still your best bet. The phone has a fantastic camera, zippy performance, great battery life, and a headphone jack.
from Android Central - Android Forums, News, Reviews, Help and Android Wallpapers https://ift.tt/3fmmkkX
via IFTTT
No comments:
Post a Comment