Question Cellular signal drops after December OTA update
- Thread starter ePearl
- Start date
you get the radio from previous build...
for me I'm in the U.S I use this build
12.0.0 (SD1A.210817.037, Nov 2021
yours might be
12.0.0 (SD1A.210817.036, Nov 2021)
I am not 100% sure...but you can try both, if one doesnt work try the other....Flash at your own risk...
I think my bootloader is locked? Says device locked when I boot the phone into fastboot?
yeah device wipe lock bootloader and one more i think force flash something is down if i remember wll from device wipe
That works fine but not everybody has an unlocked bootloader already. They don't want to do that now because it would mean wipe/loss of data
follow this ALL THE STEPS is here : https://www.droidwin.com/how-to-fla...ware_on_Pixel_Devices_via_Android_Flash_Tool) step by step and dont foget to instal adb drivers to ur laptop/pc , (have chapter how to unlock bootloader
i thin
i think that u dont have install adb drivers for windows mate .just follow every step on guide its easy
Fixes for Januard Update.
Does Google really address this Problem?
Framework
Does Google really address this Problem?
Framework
- Fix for issue causing screen to unlock after missed call when no screen lock is set.
- General fixes & improvements for network
- Fix for issue preventing emergency calls in certain conditions while some third-party apps are installed.
- Fix for issue preventing Pixel Stand setup to start after updating apps in certain conditions.
- Fix for issue causing incorrect data usage accounting in Network menu on some networks.
- Fix for issue causing a black frame to appear when dismissing the Assistant overlay on the lock screen.
- Fix for issue causing memory leak in system UI under certain conditions.
- Fix for issue causing navigation bar to be hidden when switching device orientation in certain conditions.
- Fix for issue causing PIP window to render incorrectly for certain apps.
- Fix for issue causing Wi-Fi network to drop connection in certain conditions.
The cell reception problems will be encompassed in this line. Whether we get a full explanation afterwards is a different story.
Google is a joke in this regard, if basic function of the phone isn't working, what is the point of having it?
The December update has been withdrawn by Google.
You can rollback to the November version.
For this you first have to enable "OEM unlocking" in the develeper options, after which you can perform the actions in the bootloader to flash the factory image, which can be found here: https://developers.google.com/android/images
Don't forget to make a backup first, after flashing a factory image you get a factory reset.
You can rollback to the November version.
For this you first have to enable "OEM unlocking" in the develeper options, after which you can perform the actions in the bootloader to flash the factory image, which can be found here: https://developers.google.com/android/images
Don't forget to make a backup first, after flashing a factory image you get a factory reset.
I don't think that the modem in pixel 6 is so bad. After all same modem was used in the exynos versions of Samsung galaxy s20 series. Main problem most probably is that google need time to properly support anything different than qualcomm with which they worked till now. I hope that with january update they will manage to fix the problems.
OK, i was so crazy to Install it. Could not wait 
It seems that the Signal problem is fixed and i have not found any other issues so far.
It seems that the Signal problem is fixed and i have not found any other issues so far.
Similar threads
Top Liked Posts
-
There are no posts matching your filters.
-
94@djoka60 @m-j-s I agree, this is not a solution long term nor is it acceptable that Google didn't fix this immediately. I was merely commenting on the blanket statement confirming this is not a solution. It does work for some and for some it did not. Thing is it is worth a try and "confirming" it doesn't work would preclude some from doing that. That point is now moot since they pulled the beta signup but you can download it on apkmirror last I heard. Not sure about that now. Even if, and I'm sure you're right, the majority of users are not experiencing increased signal it means that some are. I can confirm that. ;-)
Semantics aside this December update was a total disaster including some now deprecated (or disabled) major features of the Pixel phone service. It's almost 2 weeks now and not a real fix in sight. I'm not sure what they are thinking at this point. I almost wish I'd held onto my Pixel 5 now so I can wipe the smile off my wife's face as she twirls her P5.4Of course she has no clue.. she's the lowest person on the totem pole, trained to answer questions like "where does my SIM card go in?"
If people want to get Google's attention go to the link @pemz82 provided https://issuetracker.google.com/u/1/issues/210484323 and star the issue.4
If your bootloader is unlocked you can simply flash the radio image from your previous version. If you're not unlocked then don't do it now since unlocking will wipe all your data!
Download the November factory image from here.
Open it, unpack the radio-some.long.number.img and rename it to something shorter like radioNov.img
Copy it to your adb/platform tools folder and flash it with fastboot flash radio radioNov.img
That's it - my P6 went from 0-1 bars with the December A1 update (and A4 was just as bad) back to 3-4 bars with the mid November 037 radio.img4Frankly i don't understand why google are doing this. Ok it is new custom chipset and new software - bugs happen. It is normal. The way this should be handled though is much different than what we are seeing and it is pretty simple to do:
1. Stop the OTA update rollout immediately. Google did that more than week later and they also acknowledged the bug around the same time which for me was unsuccessful attempt to hide the problem.
2. Publish news acknowledging the problem and remove the link to the OTA files so that people do not sideload the problematic update not knowing about the problem.
3. Push update for the affected devices reverting the radio firmware to the november version till the problem is fixed.
If they did that people would be ok and give them needed time for proper fix in the january update. Instead of that thousands of their customers (looking at the issuetracker comments alone) are left for almost two weeks now during the hoilday season with flagship devices that can't even make phone calls properly and without any information when problem will be resolved. I myself was on vacation when december update was pushed and this saved me. I did not get OTA but i would have sideloaded it if i had access to pc and may have been in the same situation. I like to be early adopter and can wait for some bugs to be fixed as soon as at least the basic functions are working. This is why i was so excited to switch to google phone. Well it looks that i will think twice and research before updating in future.
