In this guide, we will be discussing a potential workaround to fix the dual SIM color bug in Google Phone App. The devices from the Silicon Valley giant aren’t free from their fair share of issues. while some issues such as the green lines on the screen are of astronomical proportions and require a return and exchange of the device, others such as the Bluetooth bug are usually software side and are rectified with the next software update. Fortunately, the bug that we are about to discuss is related to software, but it still doesn’t fall short on the inconvenience and infuriation scale.
Dual SIM Color Bug in Google Phone App on Pixel
In this regard, numerous Pixel users have voiced their concern about the dual SIM color bug in the Google Phone app. According to the affected users, the Phone app displays the wrong colors for the SIM cards. When they select green [from Settings > Network and internet > SIMs > Select SIM > Edit > select Colour], then it ends up displaying the blue color in the Phone app, and on selecting the blue color, it tends to display green.
This issue is only affecting the phone app, the colors are being displayed correctly across all the other sections of the device. while on paper it might not look like a grave issue, but it definitely giving a tough time to the users who usually just glance at the SIM color for its identification before placing a call.
A similar issue was observed last year as well with the cyan and orange colors. That time around, the culprit was the February 2022 update and it was rectified with the June update. So this begs the all-important question-
How to Fix Dual SIM Color Bug in Google Phone App
As of now, the only workaround that is spelling out success for some users involves downgrading the Phone app to an older version [between July 2022 and January 2022]. So grab hold of the older APK version from here and then check out our guide on How to Downgrade a System/User App on Android [Video].
As far as the official stance on this matter is concerned, the developers are yet to acknowledge this issue, let alone give out any ETA for the rollout of a fix. As and when any of these two things happen, we will update this guide accordingly. In the meantime, the aforementioned downgrade workaround is your best bet.
