Anyone else experiencing an issue with the Google Phone app refusing to close after a call is hung up? I've been having this problem for about a month, so I decided to factory reset and start from scratch with PD and the June update.
After a call, no matter how many times I press the Hang Up button, that screen will not disappear even though the person on the other end has already hung up. I can swipe the screen away and use other apps, but the Google Phone app will remain in the notifications and if I press on it, it opens as if the call was still active. The only way to make it go away is if I restart the phone.
Any ideas? This happens almost every time I end a call and it's pretty frustrating since the phone itself thinks that there's an active call and I can't use Bluetooth audio in my car or record a video with sound.
I've been experiencing this issue. It's quite a weird one because it's not an every single call thing, but seems like every 2-3 calls it'll pop up.
Yesterday, I hung out while making food and noticed the call kept going about 8 minutes later thinking my father forgot to hang up, but really, the call was ended and it was just stuck on the process of it.
I think it's the reason I've been getting weird audio issues as well. Been noticing my volume buttons only controlling the phone call volume or strictly coming out the earpiece as well.
YES! I never noticed this before because I normally make and receive calls through the Google voice app. I accidentally picked up a call from the native phone app and after I hung up, the call wouldn't close and kept showing up as ongoing call. I had to reboot to clear it because foreclosing it didn't close it.
I too have this issue. It's awful.YES! I never noticed this before because I normally make and receive calls through the Google voice app. I accidentally picked up a call from the native phone app and after I hung up, the call wouldn't close and kept showing up as ongoing call. I had to reboot to clear it because foreclosing it didn't close it.
It happens on other ROMs as well, I am on Bliss and it happens, the common denominator is Google framework and Google phone.
And i tried this and still not working, getting same error on ADB SIDELOADHere try this:
From Google with my notes:
You need ADB and ADB drivers (SDK) installed and available for CMD to find it. You will also need the matching ROM / firmware FACTORY image downloaded to your PC. Unzip the factory firmware zip you downloaded. In there contains the images needed to factory restore the device, along with the flash-all batch file to do the work.
Factory Images for Nexus and Pixel Devices
This page contains binary image files that allow you to restore your Nexus or Pixel device's original factory firmware. You will find these files useful if you have flashed custom builds on your device, and wish to return your device to its factory state.
Warning: To flash a device using one of the system images below (or one of your own), you also need the latest fastboot tool. You can get it from the Android SDK Platform-Tools package, which you can download here.
Once you have the fastboot tool, add it to your PATH environment variable (the flash-all script below must be able to find it).
Go here, download the March firmware to your local PC/MAC/Linux:
Unzip the firmware you just downloaded to disk, make sure ADB is installed with drivers and in the same folder or in your environment path
Open a terminal (command or bash) and navigate to the unzipped system image directory (which also has ADB and fastboot or make sure it’s in the environment variables so the entire system can find it).
SET ACTIVE SLOT to A then to B when A completes (more info below)
Execute the flash-all script. This script installs the necessary bootloader, baseband firmware(s), and operating system. This is first done on SLOT A, then SLOT B (on SLOT A because we forced slot A, then when done, SLOT B, so we can get BOTH slots prepared for the A12 removal and restore BACK to factory 11).
WATCH the process on the initial A slot, when it gets to the VERY LAST STEP, erase userdata, it is almost done. The very second it reboots (but NOT before it completes), let it finish then reboot on its own (its part of the flash-all batch), hold POWER+VOLUME DOWN to catch the boot process BEFORE entering the OS for setup. Switch to SLOT B, execute step 3 (same flash-all) on SLOT B, this time, hands off and let it boot into the OS setup. Skip everything, no G account, no pin, nothing, once its done, reboot to BL and follow ROM steps.
Now its prepared and ready for the ROM install. I will also send this to you in a word doc over PM so it keeps my formatted notes.
What version of Android are you coming from? If it's the July security patch version of stock or something else with the July security patch, that error will happen every time, you'll need to use the June factory image zip, then flash this rom.I have an error in the ADB SIDELOAD PART, and i cant install the ROM.
Pixel 4XL from Best Buy ( From Google ), UNLOCKED, bootloader unlocked
ADB SIDELOAD IS STUCK ON 47% WITH THE ERROR:
adb sideload PixelDust-Eleven-aosp-coral-user-20210616-0759.zip
serving: 'PixelDust-Eleven-aosp-coral-user-20210616-0759.zip' (~47%) adb: failed to read command: No error
In my Pixel im getting this error:
E: Update package is older than the current build, expected a build newer than timestap 1627025144 but package hastimestap 1623822927 and downgrade not allowed.
Install from ADB completed with status 1.
And yes, i tried to do a local Factory Flashwith June Image with FlashAll.bat file on my pc. I do first flash on A SLOT and then in B SLOT.
But i still having this problem.
I read the instructions, first flash boot, then wipe data, and then ADB sideload
Im using JUNE factory image.
Im using JUNE factory image.
fastboot flash boot boot.img
fastboot erase userdata
fastboot reboot fastboot
adb sideload PixelDust-Eleven-aosp-coral-***.zip