April 2021 Security Patch
Update as of April 6: Google usually releases Android security patches on the first Monday of every month. Apparently, the first Monday of April was on April 5 and that’s where Samsung took the lead releasing the April 2021 security patch days before Google could do it. Now that the Android April 2021 security patch is available, here’s what it carries.
The April Android Security Bulletin points out many vulnerabilities with the system ranging from high to critical statuses. The incoming April 2021 tends to plug some of these issues that Google Pixel smartphones face.
According to the bug fixes detailed by Google, it has fixed the missing home screen grid setting on some devices including Pixel 3/XL, 3a/XL, 4/XL, and Pixel 4a. The update also brings about some performance optimizations for certain intensive games and apps on Pixel 4a 5G and Pixel 5. The update also includes improvements to the camera quality on Pixel 4a 5G and Pixel 5 whilst using some of the third-party camera apps.
The update also brings about bug fixes to some of the issues triggering the device to appear offline even when connected to a VPN. Lastly, Pixel 4/XL, Pixel 4a/4a 5G, and Pixel 5 have also faced issues whereby the devices tend to freeze when the Google logo pops up on the screen when booting up, certainly it has been dealt with as well. [Source]
March 2021 Security Patch
Google has finally released the March 2021 security patch as it does every month. It fixes a myriad of issues on Pixel devices and issues affecting other smartphones that have been patched up in the March 2021 security patch.
The March 2021 security patch fixes issues related to Android Auto disconnect in certain scenarios in Pixel 3/XL, Pixel 3a/XL, Pixel 4/XL, Pixel 4a/4a (5G), and Pixel 5. Proceeding further, the issue causing full-screen display to appear chopped in some cases has been Pixel 4a, Pixel 4a (5G), and Pixel 5.
Next up, Pixel 4a (5G) and Pixel 5 users have received a fix on auto-rotate response as well. Next up, you get a fix to the stuck battery indicator percentage as the issue has been fixed on Pixel 4a (5G) and Pixel 5. Then there’s kernel update to 4.9.237 on Pixel 3/XL and 3a/XL; kernel update to 4.14.199 on Pixel 4/XL and 4a, and finally, kernel update to 4.19.135 on Pixel 4a (5G) and Pixel 5.
The March 2021 security patch also shows that Google has resolved issues leading to heads-up notification for starred contacts in DND mode that was spotted on a bunch of devices. The update has fixed the issue on Pixel 3/XL, 3a/XL, 4/XL, 4a, 4a (5G), and Pixel 5. Finally, there’s an issue causing missed call notifications in some cases on Pixel 4a (5G) and Pixel 5 as well. [Source ]
February 2021 Security Patch
Update as of February 2: Google has released the February 2021 security patch on Pixel devices that will soon arrive on other Android devices as well. This brings a number of fixes including tuning and improvements on the touch experience on Pixel 4a 5G and Pixel 5. There’s also a bug fix on issues that prevents certain sensor detection when starting up the device. This fix is available for Pixel 3/XL, Pixel 3a/XL, Pixel 4/XL, Pixel 4a, Pixel 4 (5G), and Pixel 5. [Source]
January 2021 Security Patch
Google is now rolling out a January 2021 security patch on its Pixel devices and it carries a bucketload of bug fixes and more. Apparently, the Galaxy S20 series and S9 series are getting the same SPL too.
According to the changelog, the January 2021 security patch offers bug fix to the issue causing speaker noise in certain scenarios on Pixel 4a 5G. Further, it fine-tunes the volume level of system sounds on Pixel 5. Proceeding further, we have bug fixes for the issue preventing calls on certain MVNO networks as it was reported on Pixel 3/XL, 3a/XL, 4/XL,4a, 4a 5G, and Pixel 5. Further, the issue causing intermittent restarts in certain apps as reported on Pixel 3/XL, 3a/XL, 4/XL, 4a, 4a 5G, and Pixel 5.
The January 2021 security patch also brings improvements to auto-brightness response in certain lighting conditions as it was reported on Pixel 4a, Pixel 4a 5G, and Pixel 5. Finally, we have improvements on the device’s response to auto-rotation when subjected to Pixel 3/XL, 3a/XL, 4/XL, 4a, 4a 5G, and Pixel 5.
December 2020 Security Patch
Google recently released the December 2020 security patch that supports all Pixel devices running on Android 11 and includes global, Verizon, and AT&T variants. Google detailed the list of bug fixes that December 2020 arrives with including the screen flickering bug in certain media apps as reported on Pixel 4a and 4a 5G. Another bug as reported on Pixel 4a 5G and 5 is the grip detection and suppression. Apart from that, the Pixel 5 gets fix for its poor network reception in certain regions.
Google has also provided bug fixes for issues preventing auto-rotation in certain conditions on Pixel 4a 5G and Pixel 5 as well as improvements on auto-brightness on the same devices. Next up, the Pixel 4a has a bug fix to curb issues preventing AOD mode in some conditions. The Pixel 3/XL, 3a/XL, 4/XL, 4a, 4a 5G, and 5 have intercepted graphics driver updates and performance enhancements for some of the apps. Next up, the Pixel 5, 4a 5G, 4a, 3/XL, 4/XL, and 3a XL has received bug fix for issue causing intermittent boots as well as inconsistent FOV between captured and preview image. Finally, the Pixel 3/XL, 3a/XL, 4/XL, and 4a have received Kernel updates. [Source]
November 2020 Security Patch
Update as of November 3: It usually takes Google just a few days in the first leg of every month to rollout its monthly updates and this month isn’t an exception. Google has now released the November 2020 security patch on Pixel devices from 3 and above. This fixes a plethora of issues related to inadvertent playlist removal on the YT Music, but preventing calls in Android Auto mode and audio routing in Android Audio as well.
Other fixes include a dark screen during phone calls, bug causing audio stutter during playback in some apps, hidden navigation during media playback on fullscreen and so on. The November 2020 security patch fixes bugs and issues on Pixel 3, 3a, 3 XL, 3a XL, 4, 4 XL, 4a, 4a (5G) and Pixel 5. Although the patch carries bug fixes to a number of issues, it is also market dependent given the fact that not all devices are available worldwide and neither do all bugs. [Source]
Issue: Android devices failing to save photos/videos after 10,000 clicks
Update as of April 10: Sony devices that upgraded to Android 11 had faced issues causing the device to fail to save photos and videos after the user has taken 10,000 photos/videos using their phones post the update. Well, Sony confirmed the issue and also pushed a confirmation as well as provided a way around.
Cut to now, Samsung devices have ran into a similar problem after upgrading to OneUI 3.1 update. According to the issue, the Camera app and Gallery app tends to fail to load images after OneUI 3.1 upgrade when the user has captured an excessive number of media files. Note that this might not be a case with all the Samsung devices and thus, it could be a probabilistic issue. Here’s a quick fix until the developers at Samsung don’t find a way to fix it via a software update.
Step 01: Firstly, go to the Settings on your device and proceed to Apps. Tap on the Filter and sort icon and then, tap on “Show system apps”. Next up, scroll through the list of apps and search and tap on “Sec Media Storage”.
Step 02: Now you need to go to its Storage and then, click on the “Clear Data” button. When a prompt appears on the screen, simply tap on “OK” and it is done.
Step 03: Restart the device once you have done this method and check if the Gallery and/or the Camera app show the problem or not.
Users are required to send all the reports via the bug report on their devices so that Samsung could analyze it and process a fix via upcoming software updates.
Issue: Wi-Fi disconnects when connected to WifiNetworkSpecifier
Updates: Google assigned an engineering team towards this issue in February 11, 2021, and since then, users have been posting about intercepting this issue on the way.
Update as of March 23: In a recent update coming from Google Issue Tracker, the issue causing Wi-Fi to disconnect automatically when connected to WifiNetworkSpecifier has been assigned to a developer as per the information supplied by Google Issue Tracker. Here’s more about it.
Issue: Apps aren’t launching after swiping away from Recents screen
Update as of March 20: This comes from Google’s Issue Tracker according to which, some of the Pixel 3 users who are upgraded to Android 11 are facing issues whereby some of the apps aren’t launching after swiping them away from the Recents menu. Those who are facing this issue can see a set of instructions on how to reproduce the issue and that is when a Google employee acknowledged the issue. They are working on fixing the issue permanently. [Source]
Issue: Google Photos “Device is too hot” issue
Update as of February 12: Google recently pushed a new update on Google Photos app on Android devices. This includes a new video editor with an improved set of editing tools. The update is arriving in batch manner over the air and thus, users will have to wait for it to arrive. With Google Photos, you get the ability to make granular edits, change perspective, crop, and add filters among others. There’s a newly added Portrait Blue that as mentioned, blurs the background post snapping the photos. Portrait Light adds lighting in the shots although these two features are only available for Google One users.
However, this doesn’t mean everything is going as planned. Apparently, the newly added Google Photos app is not fully optimized to work on Google’s latest Android 11 devices. Apparently, using the new Google Photos app to backup photos is causing it to get hot. The users are also unable to backup photos due to this issue as well.
Many users have claimed that this issue has been triggered right after the new update was installed. Many users tried uninstalling and reinstalling the app as well as force stop it, toggle off and on data and Wi-Fi and a bunch of other activities but to now avail. The issue is widespread as we have seen it in action on Realme X2 Pro, Samsung Galaxy Note 10+ and a bunch of other models running on Android 11 and not other OSes and thus, it is limited to Android 11 at the moment.
When users reported the same on various forums including Google’s community forum, a Gold Product Expert at Google commented that he has passed the bug report to Google. This means we will have to wait for some more time to get our hands on a fixed up Google Photos app. [Source 1, 2]
Update as of March 26: According to the latest update on the Pixel’s “device is too hot” issue, Google has fixed the issue to quite a degree with Google Photos v5.32. Users are some optimizations that the developers have affixed with Google Photos app. Thus, users who are facing the issue are advised to upgrade to v5.32 from the Google Play Store to get the issue straightened. [Source]
Issue: Scoped Storage on Android 11 adds 2 prompts to delete files
Update as of February 2: Android 11 comes with what is known as scoped storage and not everyone is liking it. If you are an Android 11 user and you also use Google Photos, you might have discovered that you get prompts twice before you can delete photos. According to the reports, when a user tries to delete the photos and videos and moves it to trash, they get a prompt before deleting or restoring the files.
Although this isn’t a problem for many, it is a problem for those who take a lot of photos and videos and it is an extra step towards deleting/restoring those files and it is annoying. As said, the going by an extra mile method wasn’t accessible on Android 10 and only arrived with Android 11’s Scoped Storage which limits an app’s access to any sensitive files without requiring user consent.
Apparently, this is a problem because Google Photos sources photos from various sources such as stock camera apps that are different for each OEM. Since the said stock camera app is out of Google Photos’ jurisdiction to make changes, it is having issues deleting or restoring files without seeking permission. One way to make this problem go away is to change Google Photos as a system app. You can read more about it here.
Issue: Google Pixel 4/4XL experiencing battery indicator stuck glitch
Update as of December 24, 2019: Android 10 is one of the best operating systems hands down and yet, it has a few issues. The battery indicator stuck glitch has made its way to Android 10. According to the users, the battery percentage stuck at any given percentage such as 50 or 18 as per users. Here, the percentage won’t go down or up no matter if the user is plugged the charger or streaming movies. Upon dying, the phone’s screen simply turns black.
Some of them reported that their Pixel 4 XL battery indicator stuck at 100 percent. It seems like restarted the phone has little to no impact on this particular issue. If that’s not all, even Pixel 3 users are reporting the same issue on their devices. [Source 1, 2, 3, 4, 5]
Update as of November 23: Almost a year after it was first reported, the battery indicator stuck glitch is still affecting some of the users if not all. Apparently, this has continued even after upgrading to Android 11 recently. The problem is still not acknowledged by the search engine giant. [Source 1, 2, 3, 4]
Update as of November 27: The said battery indicator stuck glitch has appeared on Pixel 5 as well as per the users. Apparently, a Product Expert at the Google support page said that the team is aware of the issue and they are working towards fixing the issue in an incoming update on Pixel 5. Note that it is mentioned that Google will provide a fix for Pixel 5 which means the fate of this issue on Pixel 3/4/4A and other Pixel devices facing the same is still hanging at large. [Source]
Issue: Google Pixel 3a facing battery charging issues after Android 11 update
Update as of November 27: It has been months since Android 11 has been available on Pixel devices with the official update arriving on September 8. Cut to now, it has already attracted a trove of issues and we are currently adding one m ore to it. Apparently, Pixel 3a users are facing issues charging their devices after upgrading to Android 11. One of the users said that the phone ain’t charging or if it does, it turns on for a second and disconnects. Another user said that no matter which charger he/she used, the battery percentage won’t go higher than 30 percent.
A different user pointed out that his/her Pixel 3a won’t charge until put into safe mode or turned off for charging purposes. However, at least one of the users found solace afterthe issue actually was fixed after a week of troubled charging attempts.According to the report, this issue has been reported on Pixel 2 XL when it upgraded to Android 10. Keep a tab on this section if you are facing this issue and we will keep you updated with the latest information coming on. [Source 1, 2, 3]
Issue: Google Pixel Wi-Fi connectivity issue
Update as of November 27: Android 11 is still new and fresh and still coping up with bugs that are constantly being fixed only to find out new ones. One such issue that users reported recently is the Wi-Fi connectivity issue after upgrading to Android 11. Apparently, a Pixel 4 user said that the Wi-Fi and cellular data speeds took a toll. He/she had to reboot the device to get it working which is often a workaround to fix temporary bugs on Android devices.
Another user reported it on Pixel 3XL where the Wi-Fi stopped working entirely. Here, the user suggested a few possible workarounds that include renaming network, forget and connect to the network, restart, restart in safe mode, update router firmware, reset router, or finally, perform a factory reset to fix the issue. As of now, reports of the WiFi connectivity issues have been reported on Pixel 4 and 4a, Pixel 3 and 3XL and might have inflicted upon other Pixel devices running on Android 11 too.
We did a bit of digging around the Pixel WI-Fi connectivity issue only to find out the issue was tagged as fixed on Google’s issue tracker. However, it still stays untreated to some of the users. Going through the possible workarounds can fix the issue for sure. Here are some of the possible fixes that could bypass the issue once and for all. [Source 1, 2, 3]
Issue: Fling Velocity Issue
Update as of November 26: The Fling Velocity issue was discovered on Google Pixel 4a and other devices just after the Android 11 was launched i.e. on September 11. Apparently, users had to take more effort to swipe on the screen to get the things done compared to earlier when it had less efforts to make. Google was quick to acknowledge the issue. Cut to now, the issue has been fixed as per Google’s Issue Tracker. Apparently, the build carrying this bug fix will arrive soon although there’s no ETA available at this moment. [Source]
Issue: Google Pixel 4a & Pixel 3a blurry photos/videos with the front facing camera
Update as of November 26: No doubt Google Pixel devices are something you should for when checking out mobile photography thanks to Google’s exceptional computational prowess. Pixel uses Google Camera which is set by default and offers a lot more and no doubt why it is modded for non-Google devices too.
However, the road isn’t always smooth here. Apparently, reports of blurry front cameras have popped up on the internet and Pixel 3a and 4a seems to be widely affected. Most of the images clicked with the front camera are blurry and visible to naked eye as per the reports. Pixel 3a and Pixel 4a are taking the most hits as of now although other devices might be affected too. Further, the screen protectors and facial retouching doesn;t seem to be the culprit. Perhaps, the issue is likely on the Pixel’s end. It seems like the minimum focusing distance (focal length) is bit too far causing the blurry images. Well, this was for photos.
Talking about blurry video calls via the front camera, the Pixel 3a and 3a XL are facing this issue with several reports already up on Google’s Community forum. Interestingly, some of the reports date back a year. Apparently, they are facing blurry video calls issues only on third-party apos and not stock apps. It remains to be seen when we will get Google’s attention towards it and get it fixed. [Source 1, 2, 3, 4]
Issue: Google Pixel 5 fluctuating volume and poor audio quality issues
Update as of October 26: Google Pixel 5 is the latest addition to the Pixel family. It did arrive with top-tier specifications. With the latest Android 11, it did make an impact with a tonne of upgrades, features, and whatnot. Turns out Android 11 has its issues too. One such issue is the poor audio quality when watching videos on Netflix or YouTube where the bottom-firing speaker looks too low.
Note that once you connect a headphone, you’ll get the usual sound quality but it reduces when listening to the sound emanating from the speakers. It is a random issue and isn’t restricted to these two apps only but rather it has engulfed many such apps like YouTube, Spotify among others. The same issue was reported on Google Pixel 4 which means it is not restricted to Pixel 5 either. It is probably an OS thing since Android 11 already has a long list of bugs that needs to be ironed out.
For now, users can try a few fixes to improve speaker audio quality. One such fix is to download an app called Flat Equalizer from the Play Store. Once you download and install it, the app will probably improve the sound quality as said by several users. You can also try an app called Wavelet that has shown positive results with it as well. [Source 1, 2, 3, 4]
Update as of November 23: If you are facing volume fluctuating problems on your Pixel 5 or other Pixels, note that the issue has been reported on Pixel 2 and Pixel 4a as well. This means it is surely an Android 11 bug since all these Pixel devices run on Android 11. Luckily, Google is aware of the issue and has acknowledged it as well. A Platinum Product Expert said that Google will fix it in the future update. Google released monthly updates which mean, users probably won’t have to wait longer to get their hands on this bug fix. [Source 1, 2]
Update as of November 18: What if you buy a smartphone with a hefty price tag and can’t play music on Spotify or videos on YouTube? Well, turns out Pixel users have started encountering media playback issues on their devices after locking the screens. The problem is primitively affecting Spotify, YouTube Music, and several podcast apps and others. According to the reports, the issue is dominant on Google Pixel 3a series although it has affected users across the Pixel 3/XL and Pixel 4a series as well.
According to the users, he encountered that YouTube Music stopped working when the screen went to sleep. One of the fix that could work on a short term is to change battery settings to keep the display lit up for a longer duration to get the media playback running. It goes without saying that the issue has come to light only after Pixel devices upgraded to Android 11.
Apparently, one of the suspects causing this issue on Pixels is reportedly the aggressive doze system which is apparently killing media playback apps from running in the background. On the flip side, it doesn’t explain why the audio on Pixel devices turns choppy, hinting at a totally different issue causing the problem.
According to the workarounds available, users can try to turn off Google Assistant on Pixel devices that reportedly fixes the issue. Google’s Twitter handle responded that setting the apps you don’t want to be killed to “Don’t Optimize” will likely work in this case. For it to work, you need to go through Settings >> Apps and Notifications >> Advanced >> Special App Access >> Battery Optimization >> All Apps. Scroll through the list, select the apps you want the battery to optimize on and tap on “Don’t Optimize”. [Source 1, 2, 3]
Issue: No response, timed out error on Pixel 3/3XL
Update as of November 17: Google Pixel devices are already up and running Android 11 after a series of developer previews and beta updates only to receive stable updates in September. However, even after going through several updates, there are a few issues with it. One of the latest issues that has come to light is the “No response, timed out” error message that users are getting on their Pixel 3 and 3 XL devices primarily. Apparently, the devices keep showing the error message just after 30 seconds int the call on Verizon.
It doesn’t take a rocket science degree to decipher that the issue has primarily affected Pixel devices on Verizon network. The issue doesn’t trigger on all calls but it is limited to outgoing calls only.
There are a few workarounds that could help find a way around the bug until Google/Verizon fixes the issue. Users can reset app preferences as this reportedly works. Another workaround is to turn off advanced calling via Settings >> Network & Internet >> Mobile Network >> Advanced Calling to fix the issue. The third workaround is to reset network settings via System >> Reset Options >> Reset Wi-Fi, mobile & Bluetooth and hopefully, it works in your favor.
Update as of November 19: Users are facing the “No response, timed out” issue on their Pixel devices. As per the latest update, a user claimed that he spoke to Verizon tech support about the issue and was told that it is a known network issue from the carrier’s end. Verizon is working on fixing it although there was no ETA available around when the fix will arrive. Also, take it with a pinch of salt at the moment. [Source]
Issue: Pixel Low call volume
Update as of November 18: Apparently, there are a tonne of reports where users have claimed that they are facing low call volume. This makes it difficult to hear what the recipient is saying. The issue has been reported on Pixel 5 where the volume is pretty low even when cranked all the way up. Note that the issue can be mitigated indoors but when it comes to calling when in outdoors, the problem is affecting users.
There are a few workarounds that users have found to be instrumental. Lowering speaker volume improves sound quality when listening to the person on the other side of the call. Another workaround is to get rid of screen protectors as some types of protectors may cause distortion as it adds a layer on top of the display possibly posing as an obstacle from the speaker in the earpiece.
Other workarounds include positioning the phone correctly, finding the sweet spot of the speaker where the volume is higher than other spots. [Source 1, 2, 3, 4, 5]
Issue: Notification Volume & Ring Volume is together
Update as of November 16: Android 11 is the latest edition of the Android operating system that was released in early September after months of being in beta. But there are bugs that still need to be ironed. Apparently, Google removed Notification Volume settings from the Android 11 and squashed the notification’s volume with the ring’s volume. There are a tonne of reports of users seeking out to Google to separate both the notifications and ring volume. Users have started sending out feedback via “Settings >> About Phone >> Send feedback about this device”. Google hasn’t responded to it as of now, however, the code for the feature is still present in the Android source code which raises chances of revival. [Source 1, 2, 3, 4]
Update as of January 11: According to the Google Issue Tracker, there’s some progress with the request to separate the notification volume controls from the ring volume. According to the tracker, search engine giant Google has actually assigned a developer who will be working towards the issue and hopefully, the notification and ring volume on Android 11 on-board Pixel devices will be separated for soon. [Source]
Issue: Calls & SMS aren’t going through on Pixel 5
Update as of November 10: Apparently, all’s not well for Pixel 5 Android 11 users. Some of the users have reported that they are facing call drop and SMS issues on their devices. As per the report, the issue has hit Mint Mobile users majority although it is widespread. Some users aren’t able to make calls on their Pixel devices and yes, that includes both Pixel and Pixel 3 XL as well. Mint is a MVNOs based on the existing infrastructure of the U.S.’ T-Mobile, however, the latter doesn’t seem to have any issue at the moment.
There could be many reasons behind why Mint users are majorly facing the calls and sms not going through issue. Of the many workarounds available, users can try disabling Wi-Fi calling and rebooting the device works too. Switching to LTE (4G) from 5G acts as a potential workaround as well. For the actual fix, users will have to wait until any party declares what went wrong. [Source 1, 2]
Update as of November 18: If you are a Mint user facing issues connecting calls and sending SMSes on your Pixel devices, Mint has responded that they are in communication with the carrier and Google and they are working on the issue. It is perhaps not limited to Mint only. They seem to have a clear sight of the issue although the fix will take some time until then, users will have to wait for it. [Source]
Update as of November 25: According to the latest update coming from Mint Mobile’s co-founder, Google has finally released the bug fix for the calls and SMS issue on their Pixel 5 devices. The users must upgrade to the latest firmware to get the bug fixed and as it is an OTA rollout, this could take some time. The statement posted on Reddit points out that the update should arrive within 12 hours. If it doesn;t arrives, dial 6#6CHECKIN#6#6 and the phone should intercept the update. Some of the users got the hold of this update and reported that this hasn’t fixed the SMS and call not going through issue on Pixel 5. [Source]
Issue: Google Pixel screen freezing issue after Android 11
Update as of November 5: If battery draining, performance issues, and others weren’t enough, Google Pixel devices are facing screen freezing issues after upgrading to Android 11 as well. Users have reported the issue on Pixel 2, Pixel 3a XL and turns out this issue has been spotted across the Pixel lineup right after users upgraded to Android 11.
It is yet to be seen if the issue is with Android 11 OS or the apps that might not be optimized to run on Android 11 as it has been a few months after it was released. For now, factory resetting is one of the viable options although try to disable or clear cache an app before pulling off the life support with factory reset to fix the issue. [Source 1, 2]
Update as of November 7: The Android 11 is one of the most advanced Android firmware available and yet it has some issues. It is likely because it has been just a few weeks since it was launched officially. Coming back to Android 11, plenty of users on Pixel devices have reported that their phones crashed abruptly when upgraded to Android 11. Apparently, it his a widespread issue and not limited to certain apps. As per the reports, it has targeted issues with the Facebook app, Messenger, Camera, Instagram, Gboard, Settings, Chrome and a way long list of assorted apps.
Also, the Android 11 crashing problem has been spotted across the whole Pixel lineup. We already mentioned that uninstalling and reinstalling the affected app might help or simply a factory reset would do but these are just temporary fixes. The problem is still at large and users will have to wait until a permanent solution for the same isn’t provided in the further updates although the ETA is not available either. [Source]
Issue: Android 11 update broke default launcher setting
Update as of November 5: Apparently, there’s another issue as reported on Pixel devices and now it is related to the default launcher. According to the users, when they set up a custom launcher like Nova, they get prompts to select the default launcher. Even after selecting a launcher other than the default launch, the prompts keep on repeating them. The issue has been reported on Pixels and some of the OnePlus devices running on Android 11 as well.
Before Google could fix the issue which will of course take some time, here are a few recommended workarounds. Apparently, if you set Pixel Launcher as default and then change it to another preferred launcher, the problem seems to disappear. Allowing motifying of system settings fixes the problem in some senses as well. [Source 1, 2, 3, 4]
Issue: Pixel 3a/XL audio problems
Update as of November 3: Pixels devices have been getting Android 11 as beta since February. In September, Google released a stable version but the ride hasn’t been smooth lately. Android 11 is still relatively new and has a lot of bugs and issues to be fixed. One such issue that Pixel 3a/3a XL users pointed out on official Pixel forums is about the audio playback issue after upgrading to Android 11.
Apparently, ever since they upgraded, they are facing sound issues. Some users aren’t able to hear when calling someone, they can’t play music on their units and so on. A user did mention that rebooting fixes the problem but on a temporary basis. It is yet to be acknowledged by Google and hopefully, a fix will be provided soon. [Source]
Issue: Pixel 3/XL motherboard failing issue
Update as of November 3: Another issue that is boiling in front of some Pixel 3/XL users is the motherboard failing issue. Apparently, users have claimed that their units undergo bootloop state or fail to boot. A user said that his Pixel 3a XL started randomly rebooting. Although it isn’t clear, he said that the problem is the motherboard as it is failing to boot up or the other possible reason could be a faulty battery.
As of now, it is unclear what is triggering the bootloop state on pixel devices but this is after Android 11 upgrade so you know who to blame. A user mentioned a similar issue but said he used 99% IPA to spray on the power button, blew it with compressed air and it worked. If itis a hardware issue, your possible options are to replace it or wait as the Pixel 3 series goes out of warranty after which, you will have to pay no matter what unless Google has something in it for its users but the chances are slim. [Source 1, 2, 3]
Issue: Pixel 5 5G not working
Update as of November 3: Google launched its much-decorated flagship 5G smartphone aka Pixel5 just a few weeks ago. It supports 5G, however, some users have taken it to Pixel forums to discuss that they are facing issues connecting to 5G. Users have posted that they aren’t able to connect to the 5G network even when 5G is available in the area. Users with various U.S. based carriers are facing a similar issue as well.
Apparently, this is a widespread issue affecting a lot of users in various regions. It is yet to be known what is triggering the issue. It is possible that Google may argue that it doesn’t sell Pixel 5 in many regions but even the users in the U.S. aren’t able to connect to 5G which hints at the device’s issue. A user asked his carrier and in-turn, the carrier said that have requested a certification at Google. There’s no ETA available on any of the matters mentioned above and neither Google has acknowledged it at the time of writing this. [Source 1, 2, 3, 4]
Issue: Android Auto broken after Android 11 upgrade
Update as of November 2, 2020: It has been a few weeks since Android 11 released on Pixel devices as a stable version. Note that developer previews and beta versions have been releasing on Pixel devices for a few months now. Talking about the Android 11 update, it has brought a number of new features, UI changes, and more on-board. However, it also comes with some issues.
The latest to arrive on the scene is a broken Android Auto app on Android 11. Apparently, users are facing issues related to the Android Auto app such as no notification sounds, music cutting in and out, no Calendar app working and so on. Also, users are facing a varied range of issues including calls not routed through the car stereo as well as Waze not working, some users even reported that their Pixel devices (especially Pixel 3 XL) is triggering soft-bricking thereby users are required to perform a factory reset to fix the issue.
Redditors have come up with fixes as a workaround such as apparently, turning off Bluetooth device scanning on your Pixel device running on Android 11 tends to give the issue a pass. Google hasn’t acknowledged the issue and hasn’t provided any ETA yet but the impending Calendar app issue that we mentioned earlier has been fixed.
Update: November 2020 security patch was recently released and apparently, this has potentially fixed many issues related to Android Auto on Android 11. The changelog released by Google states that the issue triggering incorrect audio routing and a bug preventing users from making phone calls while on Android Auto mode has been fixed on Pixel 4 / XL, Pixel 4a and Pixel 4a (5G), Pixel 5 respectively. [Source]
Update as of February 20, 2021: If you are an Android 11, facing issues with Android Auto is not a new thing. Apparently, the pending bugs have caused a series of issues including no calls are routed via car stereo, general connectivity problems, choppy music playback, no notification sounds, and so on. Back when Android 11 wasn’t that widely available, the Android Auto issue was limited to a handful of devices.
Cut to now, the problem has been spotted on devices from Pixels, Oppo, Xiaomi, Samsung and other OEMs as well. For those who have been in touch with us w.r.t the Android Auto problem or if you can read the previous update on this issue, you’d know that the November 2020 security patch did resolve a few issues related to Android Auto. But the issues are still strong and compounding as the days fast and Google hasn’t plugged the holes yet.
According to the latest updates, Pixel devices aren’t the only affected devices but even Samsung Galaxy S21 Ultra and a few others have been affected. A user reported earlier that the Waze speedometer reportedly stopped showing on the car’s display.
Users pointed out a possible workaround wherein clearing the app data in Android Auto overturns the issue although it reverts to an older version which isn’t facing similar bugs.
An update was supplied recently stating that Google acknowledged the Waze speedometer issue and it has escalated and a fix is awaited soon. You can still use a workaround mentioned above or somewhere to fix the issue temporarily until a permanent fix is not rolled out. Another issue that has been escalated is the Android Auto restart bug and a team is working on the same along with the app not working issue.
Update as of February 24, 2021: Android Auto app on Android 11 has been problematic ever since it arrived with tens of issues occuring on Android 11 devices although not all at times but to a varying degree. Many of the issues were escalated to Google and it already had a concerned team looking after fixing the issues. The Android Auto V6.1 is here and it does bring a lot to offer with bug fixes.
Talking about the Android Auto v6.1, here’s a few issues that are no longer there. The first is Android Auto not working on Samsung Galaxy S21 devices. Another issue that has been fixed is with Pixel 3 series immediately rebooting after turning on Android Auto. Next up, issues related to Android Auto not working on Ford F150 wirelessly has been fixed too. For those who want to upgrade to the V6.1, they will have to download the app via APKMirror as the update isn’t available on Google Play Store for some reasons. Also, upgrade Google Chrome to 88.0.4324.181 or higher to be able to download the package on your device.
Update as of October 9: Android 11 is the latest operating system and has already gone through a tonne of beta updates on Pixel and other devices. All is well but some bugs need to be ironed out. Users have reportedly had battery draining issues with Android 11. This one is happening across all Pixels. Google hasn’t responded with an acknowledgment yet but an expert suggests that booting into safe mode does. According to the reports, the Pixel’s battery is dropping to 25% after a few hours of use.
If that’s not enough, reports suggest that Pixel devices are performing slower than they should with the update. Accordingly, the October 2020 security patch didn’t help as well. Downgrading to Android 10 does the trick.
Update as of October 12: According to the latest development, the battery draining and performance issues have plagued Pixel 3 and 3a series after the Android 11 upgrade. Users have reported the issue with the Pixel 3/3a series.
Update as of October 14: The battery draining issues on Pixel devices after the Android 11 upgrade is still dominant. Turns out users might have found the culprit. It’s the TuneIn Radio that is causing the battery to aggressively drain and uninstalling the same resolves the issue. However, some users are still encountering the same battery draining issues even after uprooting the TuneIn Radio app on their respective devices.
Update as of November 5: As per the latest update, it isn’t just the Pixel 3 and 3a series, Pixel 5 is hogging the battery aggressively. Apparently, users have reported battery draining issues on Pixel 5 wherein they are noticing ~25% drop in battery even after the phone remained idle during the night. A user pointed out that where Pixel 4 XL recorded ~8-10% decrease in the battery, Pixel 5 saw ~25% which is substantial as we are literally talking about a quarter of the battery. In fact, some users even reported that their battery drained around 40% overnight which is insane.
Just like any other issues, there are a few workarounds. Apparently, the 5G network support can be changed via the Settings >> Network and Internet >> Preferred Network Type”. Another workarounds include disabling ‘Mobile data always active’, using Naptime, disable Pixel Ambient Services among others. [Source 1, 2]
Issue: Bluetooth controllers not working
Update as of October 12: The Android 11 seems to be facing a lot of bugs on its Pixel lineup. Another issue that was recently brought to light is with the Bluetooth game controllers like Nvidia GeForce Now and Google Stadia among others. Users are unable to control their Bluetooth controllers after upgrading to Android 11. Reports have arrived from users on Pixel 2, 3, and 4 users who have taken it to Google Issue Tracker to discuss the same.
Users have come up with their workarounds to fix the issue. One user claimed that switching off magnification gestures on Android 11 does the trick while another user said tweaking the Accessibility settings fixes the issue at least temporarily. Users are still waiting for a permanent solution from Google on this matter. [Source 1, 2, 3]
Update as of January 6: Looks like the Android 11’s Bluetooth controllers like Stadia not working have swamped other devices too. Apparently, OnePlus and Samsung (8T & Note20 users) have reported that Bluetooth controllers on their devices aren’t working properly. One of the users said that when the BT controllers connected to the OnePlus 8T, it didn’t recognize any input.
Another user said that he isn’t able to connect to the PS4 controller on his Samsung Galaxy Note 20 soon after upgrading to Android 11. Google Pixel devices already had this issue after it was reported a few weeks ago. Seems like the search engine giant hasn’t yet rolled out any fix for the issue so users will have to find a workaround or they will have to wait until Google fixes this issue with Android 11 builds. [Source 1, 2]
Update as of January 21: Remember how Pixel devices had issues with game controllers after upgrading to Android 11? Well, the issue was acknowledged by the search engine giant even before it rolled out the stable Android 11 build and still, the issue hasn’t been fixed yet.[Source]
Update: Users have been posting updates on the Bluetooth controllers not working issue on Android 11 post updating on their respective devices. The Google Issue Tracker details all these posts made by users. According to one such user, he upgraded to Android 11 on Samsung Galaxy Note 10+ to find out that no controllers are working post the update. Some of the users have also mentioned that one side of the controllers works while another doesn’t.
A user quoted a workaround that could potentially fix the issue at least on Samsung devices if not others. Users will have to go towards Settings >> Accessibility >> Installed Services >> Control Center and disable it and check if it works or not.
Another workaround that has potentially fixed the Xbox One controller over Pixel 4XL is to enable Developer Mode and then, turn on Debugging Over Wi-Fi and then, forget all Bluetooth controllers. Try reconnecting the controller again to check if it works or not. Note that the bug is yet to be fixed with the latest reports coming in the first week of February stating that the bug still exists. [Source]
Issue: Bluetooth (in-car) issues
Update as of October 11: Recently, a new issue has come to notice on Android 11. Some of the users are facing trouble with Bluetooth issues while playing music in their cars. The reports are pretty vivid such as some have reported that the audio stops playing while some say it cuts off while playing for several seconds. Other users have stated that the audio pauses when the screen is locked while some hear a crackling and hissing sound when playing music via Bluetooth. The only major similarity that users have found is that the problem arose after they upgraded to Android 11 on Pixel devices. Some users are facing issues with Android Auto as well. When asked, Google ruled out the possibility of a ‘product feature issue’ and also, there’s no ‘developer issue’ either. Perhaps the problem is still intact and users are trying to find a fix to it.
Update as of October 19: According to the various reports, Pixel 4a appears to be more affected by the Bluetooth issues as per the reports posted by several users. But there are a few workarounds that seem to be working to some degree. A user stated that the Music app is causing the problem as the battery optimization feature is turning off the app. The easy fix to this issue is to simply render out the music app from the ‘Restricted Apps’ list. They can remove the music by going via Settings >> Adaptive Battery >> Restricted Apps. Check if it works.
On the other hand, a user found out that turning off the location on Pixel devices does the trick as well. Try one of these workarounds to check whether it works or not.
Update as of March 26: After a few months, there’s a new update on the Bluetooth connectivity issue faced by Pixel users in-car on units running Android 11. Apparently, the problem was earlier termed as a product feature issue and not a developer issue where the latter is resolved by a concerned team of developers. Apparently, the Google Issue Tracker has updated the status whereby it has been assigned to a concerned Google team and now, it will be further investigated, analyzed, and hopefully, a fix will be provided soon. Note that we still don’t have any timeline so it could be weeks and we will still have to wait for any update. [Source]
Issue: Navigation & status bar occasionally getting stuck
Update as of October 12: This is particularly a straightforward bug that has been frustrating users ever since Android 11 was in beta. The navigation or status bar as some people call it reportedly sticks on top of the screen in landscape mode when playing a game or watching videos. Ideally, it should retract and only become visible once the user swipes down on top of the display but it ain’t the case with some Pixel devices running Android 11.
Users have plagued forums regarding the issue. A user said that he got this bug when playing Call of Duty but it doesn’t restrain any particular app or demographic parse. It remains to be seen if this issue is with Android 11 as it is probably an outcome of early adoption. On the other hand, it could be due to apps not optimized for Android 11. [Source 1, 2, 3]
Update as of October 15: Android 11 brought a string of cosmetic changes to the overall UI. One of the changes that it brought was the new Power Menu which has ‘Emergency’, ‘Restart’, ‘ Power’ but not ‘Screenshot’. Google Pay, Home actions, and other features are added in the Power Menu. The screenshot has been shifted to the ‘Recents’ screen. Although this isn’t a bug, users have taken it to various forums asking Google to bring back the Screenshot button to the Power Menu. Some users have quote workarounds but no avail. Google hasn’t made any announcement or statement about this change. The users will have to stick to Power + Volume Up (or Down) to get the screenshot rather than finding ways to get the previous screenshot button on the power menu back. [Source]
Update as of November 16: As per the latest update, the November 2020 security patch on Pixel devices have recently added a screenshot menu on the power button after it was unavailable previously. However, it is still a 2 button navigation so you can’t use gesture navigation or other methods at the moment. [Source]
Issue: DND Exceptions not working/broken
Update as of October 15: Google recently upgraded its Do Not Disturb (DND) interface on the new Android 11. Now the DND menu has its own space along with other options. According to the bug that has been brought up several times on Google support forums and bug trackers and Twitter, the DND is working but the Exceptions created with it seem to be broken.
According to the users, the phone works well when DND is off. When DND is on with exceptions like starred contacts and callers, the recipient seems to not get any ringtone when the said exception calls. This issue has plagued the entire Pixel lineup. One of the workarounds that users have found is that enabling ‘Allow repeat callers’ does the trick. It lets starred contacts call users even if the DND is on. On the other hand, it cannot fix the message notifications. However, a Google Support staff said that the latter issue has been acknowledged and the developers are working on it to fix it. [Source 1, 2]
Update as of December 16: Based on the latest info w.r.t the DND exceptions error, users have been reportedly facing the issues ever after the November 2020 security patch stating that a bug fix has been released. Anyways, Anyways, December 2020 was intended to fix the problem as well. Apparently, one of the user reports suggests that the DND exceptions error is nowhere after upgrading to the December 2020 security patch. More user reports are awaited. [Source]
Update: One of the users who actually posted the DND exception issue on Google Support page has mentioned that upgrading to the December 2020 security patch seems to fix the issue. It is yet to be confirmed if the issue is fixed on all affected units or not. [Source]
Issue: Android 11 reportedly broke proximity sensor
Update as of December 8: Proximity sensor is what detects your presence and turns off the screen when on a call. Apparently, Android 11 on Pixel 4a has reportedly broken its functioning. There are tonnes of reports on Pixel Phone Help and other community forums including Reddit where users have updated about the incoming issue after upgrading to Android 11.
According to the user, the screen doesn’t light up after finishing a call which it must since the user is away from the proximity sensor. The user is not able to hang up the call or do anything without the screen lighting up again. The reports state both the scenarios where the proximity sensor doesn’t function properly as the screen either doesn’t light up after a call or the screen display lights down when making/receiving a call. The standard practice of rebooting the issue has proven to fix the problem but only on a temporary basis.
When a user checked if the proximity sensor as a hardware is working properly or not, they found out that it is working as intended, however, malfunctions when the user gets or makes a call. Google is yet to acknowledge the issue. Also, the issue has affected many other Pixel devices including Pixel 2, 3, 3a, 4, and 4 XL as well. [Source 1, 2, 3]
Issue: Persistent “Charging connected device via USB” notification
Update as of December 05: When you connect your phone to your computer via USB cable, you see a notification in the notification panel saying “Charging connected device via USB” if you have set it to ‘charging’ or else, it would show ‘file transfer’ if you have set it as such. Apparently, some users have claimed that after upgrading to Android 11, they are seeing the charging connected device via USB notification persistent on the notification panel. This isn’t going anywhere even if there’s nothing connected to the phone.
The original poster on Google Support stated that when the user tried connecting the charger to the phone, the notification went away. However, it returns almost immediately after unplugging the charger. Apparently, this issue has been around since November 2019 when it was originally posted.
There are a few workarounds that kind of works although in a varying degree of effect on the issue. One such method is to reboot the device that should fix the bug. Another is to boot into the Safe Mode on your device and if the issue still persists, a factory reset could help. Similarly, clearly up cache files both from memory and apps can do wonders in many cases so try on this bug as well.
This issue isn’t limited to Pixel devices only as a user on Nokia 3.1 Plus said the same thing. Note that the issue has affected devices on Android 10 as well. [Source]
Issue: Wi-Fi hotspot/tethering issues
Update as of December 02: You just got upgraded to Android 11 and it works fine. However, it has issues with Wi-Fi hotspot/tethering connectivity. What would you do? It’s annoying without any doubt and that is what Pixel users have been complaining about on Pixel Phone forums. Apparently, the Wi-Fi hotspot on their Pixel devices is behaving abnormally although it is not a widespread issue but it exists. Users are saying that there are various issues under Wi-Fi hotspots such as networks not available while some are saying that the hotspot gets disconnected when they lock and unlock their phones.
Many users have reported that the hotspot when once turned on, remains turned on until the screen is on. Once they turn off the screen, the hotspot switches off immediately. This issue has been spotted on all Pixel devices in different multitudes although Pixel 2 and 2 XL are targeted as the ones most affected with it.
There are many workarounds that possibly fix the issue although have a different multitude of impact on the bug. One such workaround is to disable Bluetooth as one of the users found out Bluetooth is somehow interfering with the hotspot feature on the device.
Another possible workaround is to reset the APN settings if any user is able to connect to your hotspot but cannot use your internet for some reason. For this to work, you will have to go to Settings >> Network & Internet >> Mobile Network >> Advanced >> Access Point Names. Here, you need to tap on the three-dot menu and select “Reset to default” from the dropdown menu.
Next up, battery saver on your device might be hindering the hotspot/tethering on the device and thus, turning off battery saver on your device seems to be working in your favor enabling users to connect to the internet on a hotspot without any hassle. [Source 1, 2, 3, 4, 5]
Issue: Buggy gesture navigation, recents app & third-party launcher
Update as of October 16: Gestures on Android OS are integral and indelible part of design and accessibility. But Android 11 isn’t a smooth ride even now. As per the slew of reports posted on Google Pixel forums and other places, the Android 11 are not working properly. Apparently, a reboot does the trick in most cases so you can do it. Ensure you are swiping up from the search bar and not the gesture pill. [Source]
On the other hand, the Android 11 users on Pixel devices are encountering that the recents app is broken. But if that’s your problem, rest assured as Google has already fixed the issue with the latest October 2020 security patch. Upgrade to the latest update to ensure smooth functioning of the recents app interface on your device. [Source, Source 2]
According to the latest update w.r.t. to a different issue on Android 11, users are facing it difficult to use recent apps and other interfaces on third-party launchers (Nova). A simple fix for this issue is to simply avoid using third-party launchers and instead cling to the default Pixel launcher to get things done. Hope this resolves the problem in case you are facing it. [Source]
Update as of November 26: Android 11 on Pixel devices already has a trove of bugs to tackle. Although Google has actively participated in fixing many issues, many still lie at close sight. One of the issues that has been present on Android 11 as reported in September 2020 when Android 11 was launched is the one when the user is unable to force close apps from the ‘recent apps’ section. Apparently, the Reddit thread gives on a probable fix to the issue.
Apparently, a user pointed out that instead of restarting the phone, turning off the phone, wait for a few seconds and turn on the device. Now tweak the accessibility settings on the Pixel devices and bingo, the issue is gone. This has actually worked for some users although it may not work for all users but what’s in trying it out. One of the users said that instead of force stopping an app from the recent apps list, leave it idle and use the touch gesture to switch between apps and access the list accordingly. [Source]
Issue: SBI YONO app not working on Android 11
Update as of October 21: Android 11 is still rolling out and there are tens of thousands of apps that haven’t adapted to Android 11 yet. One such app is SBI’s YONO app on the Google Play Store. Users have taken it to various forums stating that the app isn’t working on Android 11. This comes as a blow given the fact that no other banking app is facing the same fate which has left users frustrated.
When asked, SBI said that the YONO app is not compatible with Android 11 as of now. The technical team is working to optimize it for the new Android OS. For now, using the SBI website is a possible workaround while using YONO Lite SBI seems to be working on Android 11 as well. [Source 1, 2, 3, 4, 5]
Issue: Google Photos Nearby Share option missing
Update as of October 26: Google Photos keeps all the photos you click on the cloud. It’s Nearby Share option is similar to Apple’s AirDrop. It allows users to share photos and videos with others who are ‘nearby’. However, as the Pixel series and a few other devices have upgraded to Android 11, the Nearby Share option is gone in some of ‘em. Users have posted about this missing feature on Pixel 4a among other Pixel devices.
The issue is already reported to Google and a fix is expected to arrive soon. But there’s a workaround available at your disposal. You can still use the Files by Google app to share content via your local storage. It doesn’t allows sharing content stored on Google Photos or cloud and that’s the only catch. You can use the Files by Google app to create a link, ask the recipient to join and share it without any hassle. Tap here to download the app. [Source 1, 2]
Issue: Screen fliickering
Update as of October 28: The Android 11 is a pleasing and one of the best operating systems but it has its flaws and most of ‘em plague Pixel devices as these phones get a stock Android while other OEMs deliver custom UIs with it. Talking about another issue with Android 11, users have begun to face screen flickering issues on their Pixel 4a when viewing Instagram stories. Although it was earlier expected to be isolated on Instagram but rather it has plagued other apps too and it is related to the brightness levels. [Source]]
On Instagram, the issue of extreme flickering is happening at random. One such user said that the issue kicked in when the phone was under 20% battery. When asked, a Product Expert on Google Pixel Community Forum said if the issue is isolated to affecting Instagram only, contacting Instagram is a viable option. [Source]
One of the workaround that appears to be fixing the Pixel 4a screen flickering issue is to simply disable adaptive brightness. You can do so simply by going to the Settings >> Click on Display >> Advanced >> Colours >> Select Natural (it will be Adpative) and there you have it. [Source]
Update as of December 21: According to the latest update, if you are facing screen flickering issues on your Google Pixel 4/4a devices or any other Pixel devices, be sure to upgrade to the December 2020 security patch as it will fix the impending screen flickering issue for good. [Source]
