Related
Though I have done forum searches and google searches for this issue and not found solution yet, if anyone has seen the same issue addressed somewhere else, I apologize for making this redundant thread.
I have experienced this problem ever since the 4.2 update, I have tried wiping everything and reflashing factory image again but still it persists.
When I open the JB stock browser, not the chrome, the holo-blue loading bar on the top hangs and remains even after the page has finished loading. There is also a gap below the loading bar that does not go away when I scroll down.
This happens in either full screen mode on/off or quick control on/off.
Rebooting the phone seems to fix this for little bit but soon it comes back.
Has anyone else experience this issue and has anyone got around to fix this?
Thanks
Hi,
I have the same issue, in order to "fix" it (it's not really a fix but it's the only solution I've found) I have disabled the "quick controls" option (Maybe my translation isn't good, it's the first option in the labs parameter of the stock browser).
I've lost the quick controls and the address bar isn't hiding anymore, but the display is ok
GeorgesAbitbol said:
Hi,
I have the same issue, in order to "fix" it (it's not really a fix but it's the only solution I've found) I have disabled the "quick controls" option (Maybe my translation isn't good, it's the first option in the labs parameter of the stock browser).
I've lost the quick controls and the address bar isn't hiding anymore, but the display is ok
Click to expand...
Click to collapse
i have used Cyanogen, XenonHD and stock and have not seen this issue. try formatting /system and re flashing
I have tried formatting, reflashing, full screen on and off, quick control on &off. Still the same...
Sent from my Galaxy Nexus using xda premium
I have been having the same issue. Also when I type the screen runs upwards. Just a bad flash eh?
I have had this problem no matter which 4.2 rom I tried. It's very annoying as stock browser is the best for me (love Quick controls)
Same problem here, didn't happened before 2day
Sent from my GNexus
I hope there is no similar thread on this yet and I request to all to add bugs here
my device: GSM international yakju-rooted
bugs:
1. clear recent apps in landscape mode, then switch to portrait mode and the cleared recent apps are BACK!!....and vice versa!!
2. Did OTA update with Bluetooth on and cannot switch off Bluetooth now with devices paired. Bluetooth switches back on automatically as soon as I try to switch it off. Correct me if this is a change in 4.2.1 or if this is indeed a bug.
Other complaints
1. apps on lockscreen widgets starting up randomly
2. 3 sec lag to start daydream and camera app
3. butter gone
4. laggy
luckily no random reboots and broken Bluetooth as others have reported on my device yet. I am not happy Google.
1. doesn't happen with me
2. can't test that (no bluetooth accessories)
Others:
1. lockscreen needs improvement (like clock widget auto resizing itself to full screen when swiping through screens)
2. my camera app starts in less than 2 seconds
3. 4.2 is a little heavier than 4.1.2 but still buttery compared to other high end phones
4. not on my phone
Something which happens to me when creating events on calendar... If i manually type in the end time of the event and the minutes are 59 (e.g. setting the end time to 22:59) when i press okay the time goes back one hour (e.g. 22:59 becomes 21:59). Anyone else?
I have none of the issues any of you have specified.
Sent from my Galaxy Nexus
I got the same Recent App bug, which I didn't notice before!
But overall it is running smoothly. Did you try factory reset or flashing stock image?
jam_27 said:
I hope there is no similar thread on this yet and I request to all to add bugs here
my device: GSM international yakju
bugs:
1. clear recent apps in landscape mode, then switch to portrait mode and the cleared recent apps are BACK!!....and vice versa!!
2. Did OTA update with Bluetooth on and cannot switch off Bluetooth now with devices paired. Bluetooth switches back on automatically as soon as I try to switch it off. Correct me if this is a change in 4.2.1 or if this is indeed a bug.
Other complaints
1. apps on lockscreen widgets starting up randomly
2. 3 sec lag to start daydream and camera app
3. butter gone
4. laggy
luckily no random reboots and broken Bluetooth as others have reported on my device yet. I am not happy Google.
Click to expand...
Click to collapse
* I listen to podcasts via Bluetooth car audio during my drive to and from work. Ever since 4.2, I get frequent Bluetooth disconnects while I am listening to audio. This never happened before 4.2. Unfortunately, 4.2.1 did not fix it.
* When third party apps such as Locale or Tasker turn WiFi on, it will not connect to any access points in range. However if I turn WiFi on via the WiFi settings, it connects immediately.
* Car mode is broken in 4.2 and 4.2.1. A "car home" app used to be able to invoke a mode where the home button would return you to the car app instead of the desktop. Now, the home button drops you to the desktop and crashes the launcher (Android's desktop process).
* Overall, much more lag and delays. Looks like 4.2.x is optimized for the Nexus 4 and its 2GB of RAM. 4.1.2 seemed perfect -- too bad we only had it for less than a month.
Well, my screen shuts off at random.. I can still press stuff, but it's totally black!! I have to put the battery and restart
bugs
I cannot use my BT headset, it disconnects when screen is off.
Camera is very very laggy.
Wipe phone and flash complete stock image!
I have none of these bugs! Bluetooth works like a charm.
Stock browser omnibox issue. When I open bookmarks and links from 3rd party appss, it's all good.
But when I try to type a search or url, the adress bar freezes and stays frozen on the screen. Rotate the screen and it becomes a black empty wasted space.
Is it a bug in in 4.2/4.2.1 or is it my phone?
Sent from my Galaxy Nexus using xda app-developers app
i find it takes a couple of swipes of the security pattern at times, screen doesnt always respond as quick if ive not used my phone for a few hours.
didnt happen on 4.1.2 , not a massive issue but i do notice it
FrankNS said:
Wipe phone and flash complete stock image!
I have none of these bugs! Bluetooth works like a charm.
Click to expand...
Click to collapse
Firstly, It sounds bit too much to do a complete wipe and re-flash or a factory reset for just a dot.dot update.
Also, I have been reading that for some wipe and re-flash did not fix the Bluetooth issue. Also, a just a factory reset after OTA hasn't worked for all.
Can we please have confirmation here that a the factory reset thingy works so that all of us having issues can give it a shot?
In case we should wipe and re-flash, can it be done in the following way?
1. full backup system (in my case using titanium backup)
2. factory reset
3. copy the relevant image , yakju 4.2 in my case, into memory and flash zip using cwm recovery (6.0.1.5 in my case). then flash 4.2.1 similarly.
4. restore root.
5. system data/apps restore
please let us know.
International Yakju here and I've get the most annoying out of the problems. Random soft restarts. I've done a soft reset and it didn't help. I'm getting really pissed at this. Thinking of rolling back to 4.1.x
I havent tested bluetooth but I have random errors, sometimes when phone is locked It vibrates, I unlock it and it is asking with wich program I want to open, I choose gmail and it attaches a bug report, a .txt file with 4mb and a screenshot tottaly black.
weird. 4.2.1 yakju
jam_27 said:
I hope there is no similar thread on this yet and I request to all to add bugs here
my device: GSM international yakju-rooted
bugs:
1. clear recent apps in landscape mode, then switch to portrait mode and the cleared recent apps are BACK!!....and vice versa!!
2. Did OTA update with Bluetooth on and cannot switch off Bluetooth now with devices paired. Bluetooth switches back on automatically as soon as I try to switch it off. Correct me if this is a change in 4.2.1 or if this is indeed a bug.
Other complaints
1. apps on lockscreen widgets starting up randomly
2. 3 sec lag to start daydream and camera app
3. butter gone
4. laggy
luckily no random reboots and broken Bluetooth as others have reported on my device yet. I am not happy Google.
Click to expand...
Click to collapse
I agree with the 3rd and 4th points. Camera app is quite different from ISC 4.0 and Jelly Bean 4.1, both icons are rotating while the phone is rotated. However, Jelly Bean 4.2's icon, instead of rotating, they shift the position while the phone is put as horizontally. I hope these will be fixed in the near update.
jam_27 said:
I hope there is no similar thread on this yet and I request to all to add bugs here
my device: GSM international yakju-rooted
bugs:
1. clear recent apps in landscape mode, then switch to portrait mode and the cleared recent apps are BACK!!....and vice versa!!
Click to expand...
Click to collapse
I got the same bug on both my galaxy nexus and nexus 7. For those who said that they don't have this bug, did you leave at least one app on and rotate the screen while having the recent apps menu open? Try again.
NexusDro said:
I got the same bug on both my galaxy nexus and nexus 7. For those who said that they don't have this bug, did you leave at least one app on and rotate the screen while having the recent apps menu open? Try again.
Click to expand...
Click to collapse
Just tryed that, no bug.
Can I turn off updates
OTA update to 4.2, totally stuffed my setup, flashed 4.2.1, no difference, have now flashed stock 4.1.2. to make the phone work as it should do.
Problem 1: The signal strength meter vanished on my car screen, no indication that bluetooth had connected.
Problem 2: The speaker, as I am sure we are all aware, is rubbish. I am using the pucker car mount and have a small speaker system set up and hooked into this so that I can hear warnings from CamerAlert. The phone connects over bluetooth but the CamerAlert warnings are directed out of the device speaker and go via the car mount to the speaker system - works a treat. With 4.2 this totally disappears and I get half a warning from the device speaker itself.
Having gone to 4.2 and back I can vouch for the fact that it is the update that is wrong.It will take me another day to get the 'phone back as I want it and I will then do a full backup. Thanks a bunch Google for, really professional update.
All I want now is for the 'phone to stop nagging me to update, anyone know how to turn off updates ??
my phone freeze after taking a picture today, so weird it didn't happen before and i need to pull out the battery in order to restart the device because the power button not give a respond.. so sad.. in 4.1.x everything is good.. for the first time on my gnex i need to pull out the battery twice today.. huh!!
Wow. I was very pissed of with the overall lagginess of 4.2/4.2.1 update, but I thought I might wait and hopefully Google will fix that. But then I noticed just how ofter the stock launcher crashes (leaks from RAM anyways). 5-10 times in an hour after using heavy apps like Chrome, Pocket, Facebook etc I press home button and I get and empty wallpaper. WTF? How is this even possible for a stock app?. And then there are things I've mentioned in other similar 4.2-reated threads like camera animation that lags and music widget that stops responding and keeps playing after headphones are unplugged...Gosh, that's the worst update (for me at least) ever. And now I noticed that recent apps bug. It does exist. Awesome.
*Originally I posted this in the Help section of the G3 forums but got no help, so I am posting this here*
Hey all,
So I'm posting this thread regarding a couple pretty weird glitches and bugs occurring on my G3, 3 specific ones.
The first: (Probably the least serious but still REALLY annoying) At EXACTLY 12:00AM every night no matter what timezone I set the phone to (I'm in AU on the AEST GMT+10 timezone but it does this at the same time on any timezone) the phone will switch it's WiFi off automatically without warning, reason or explanation. It just goes off and then I have to manually turn it back on. Sure I could use an app such as Tasker or AutomateIt to turn it back on but I don't see why this is occurring in the first place?
The second issue (Most recent): Lately after updating to the V20E firmware for my D855 I've noticed that a graphical glitch (Specifically related to the colour Blue) occurs when there are fast moving elements on my phone's screen (Such as when I move a chat head around on my phone from Messenger, or when I'm scrolling Facebook or my App Drawer fast, there's just a blue box around whatever object/s appear to be moving on my phone's screen. I've not dropped the phone at all, and it has only been present since updating from the V20D ROM. Not sure what could be causing it.
The third and by far the MOST ANNOYING of the issues I'm having, is that for no apparent reason, whenever I am listening to Music with the stock Music player, and I lock the screen (The screen goes off) about 5 seconds later weird stuff starts to happen..
The song will pause, play or even stop completely, seemingly on its own. The "phone" will change songs, artists and sometimes complete albums and playlists completely by itself, with me doing nothing but staring at the lock screen (It keeps doing it until I re-enter the Music app, then when I lock the phone the whole cycle just repeats itself.)
I've done some looking around and careful observations on the phone itself, and it seems that before the weird stuff starts happening to my music, the phone opens Voice Mate by itself, and then if I'm not present, it apparently closes it and then that's when the stuff happens. I've tried everything I can on a non-rooted phone to stop this. I've tried re-installing the Music app, Uninstalling all updates to the Voice Mate and it's packages to the factory version, force-stopping Voice Mate, everything and no matter what I do the phone still opens Voice Mate and the weird stuff starts happening (It's like it's taking commands from Voice Mate to do something but I'm not even doing anything ) It's been doing this since I got my phone when it came with Android KitKat 4.4 (I was on the D10M ROM until I moved to the D20D Android L ROM) and I moved ROMs doing a completely fresh start ( I factory wiped the phone and then upgraded via a CSE flash and put all my stuff back on it manually) and I would've thought a completely fresh start would have fixed it but apparently not... Either it's a bug that's been present for a while, or it's something deeper than the ROM.
So yeah some pretty weird issues, if someone knows what could be causing them, please let me know, especially if you know a way to solve them.
Cheers guys.
I'd do a factory reset for bugs 1 and 2. If that doesn't fix it, then do a clean flash from LG's Flash Tool. Regarding the first one, I think that it may be due to Quiet Mode on your phone? Or possibly even Battery Saver automagically kicking in at 12.
But yeah, backup your data and do a reset. It fixes around 80% of bugs after an update (As a rule of thumb I reset just before and right after an update to avoid any issues.
GuyInTheCorner said:
I'd do a factory reset for bugs 1 and 2. If that doesn't fix it, then do a clean flash from LG's Flash Tool. Regarding the first one, I think that it may be due to Quiet Mode on your phone? Or possibly even Battery Saver automagically kicking in at 12.
But yeah, backup your data and do a reset. It fixes around 80% of bugs after an update (As a rule of thumb I reset just before and right after an update to avoid any issues.
Click to expand...
Click to collapse
As I said before I've done a factory reset and complete re-flash via CSE, and nothing has fixed it it's been the same since I updated :/
iDefalt said:
As I said before I've done a factory reset and complete re-flash via CSE, and nothing has fixed it it's been the same since I updated :/
Click to expand...
Click to collapse
whoops, sorry didn't read the full post (newb mistake, had a teacher looking over my shoulder). Contact LG support?
Sounds like your phone is superstitious
Sent from my LG-D855 using XDA Free mobile app
GuyInTheCorner said:
whoops, sorry didn't read the full post (newb mistake, had a teacher looking over my shoulder). Contact LG support?
Click to expand...
Click to collapse
Yeah I thought that but I wanted to know if anyone here has had the same issues.
iDefalt said:
Yeah I thought that but I wanted to know if anyone here has had the same issues.
Click to expand...
Click to collapse
the WiFi issue seems like its something to do with battery saver/quiet mode (to me anyway). Unless your router is kicking the phone off at that time?
EDIT:
oh and regarding the Voice Mate issue it could be either the jack or your headphones?
Please do not double post. It is a violation of Forum Rules.
5. Create a thread or post a message only once.
As a large forum, we don't need unnecessary clutter. You're free to edit your message as you like, so if you do not receive an answer, revisit your message and see if you can describe your problem better. Not everyone is online at the same time so it might take a while before you receive an answer
Click to expand...
Click to collapse
This thread is closed. Your original will remain open here: http://forum.xda-developers.com/lg-g3/help/couple-weird-glitches-occuring-help-t2974077
Hi everyone,
I have 2 Galaxy S8+ from Verizon and here are my issues:
Past issues:
One of them did not come with the Galaxy Apps store (Not the plays store), and that phone also experienced the DQA issue
Current issues:
If I turn on Fingerprint gestures, the fingerprint sensor will stop working, this was an issue I had from the day I got the phone and has continued even through the updates. Here's a thread I made about it a while ago : https://forum.xda-developers.com/galaxy-s8+/help/fingerprint-sensor-t3595614
My internal speaker has detached, or at least I think that is the issue, as sometimes when I am in a phone call and shake the phone just a little bit, it will either start making a weird buzz sound or completely cut off the sound. Shaking it again will fix it, that's why I think it's a physical issue. I haven't dropped my phone and just in case I ever do, I have a case and a screen protector on it, and neither of them (phone, case, screen protector) have any damage marks on them.
The Biggest Issue: Currently this is the most annoying bug I am experiencing is that whenever I go to lock screen and security in the setting app, it crashes the settings app. I also can't use the search function in the settings app, as it crashes the app withing a few seconds. The lock screen and security is the only menu in which I experience this, I am 99% sure this is due to me turning on Secure startup. I had it turned on a few days after I got the phone and it worked great, I had to turn it off once, about a month ago in order to get a quicker boot. After that I was experiencing issues turning it back on (meaning I turned it on, rebooted the phone and it would not work) , after some persistence, I was able to get it to work and it has worked and still works.
One thing to mention is that I had done the most recent system update, I am not sure this issue was caused by at, since the inability so search in the setting menu has happened prior to the latest update.
I have tried everything other than a full factory reset (wiping all cache, wiping apps cache, reset setting, reset network settings), which I refuse to do, It is absolutely unacceptable for me to pay this much for this phone and have so many issues with it, I have factory resetted my phone (Samsung's recommendation) in order to fix the first issue listed above, multiple times and it did not work.
At this point I really don't know what to do, Samsung support has been useless in this, I don't wish to replace my phone right now as I need it to much to even give up for one day, If anyone has any advice/fix other than factory resetting, I'll happily try it.
Thank you,
GGgamer16
Sounds like a factory reset is needed. I just tried all you mentioned with zero problems on the newest update w/ navbar options and experienced none of that. Speaker problem is most likely hardware related.
Anyone had any luck getting rid of the wifi disconnect? The issue where wifi disconnects showing a ! next to the wifi symbol on the status bar?
*Hooligan* said:
Anyone had any luck getting rid of the wifi disconnect? The issue where wifi disconnects showing a ! next to the wifi symbol on the status bar?
Click to expand...
Click to collapse
You try changing your WiFi channel? Using 5ghz or 2.5ghz? I use Wifi 100% of the time I'm home and never have any issues with disconnects.
brandonc0526 said:
You try changing your WiFi channel? Using 5ghz or 2.5ghz? I use Wifi 100% of the time I'm home and never have any issues with disconnects.
Click to expand...
Click to collapse
Yeah I have tried changing channels. It didn't matter. I'm on 2.4 GHz.
I found a possible fix from another forum. I changed my wifi encryption from wpa2 AES/tkip to wpa2 tkip only last night and was rock solid after that point. I didn't have any more wifi issues... Just wanted to mention this change for other people. I usually got 5+disconnects every night. I'm gonna try just the AES option tonight and see how it acts.
Really strange issue just started occurring today as far as I can tell. I am on a Google Pixel XL, unlocked, rooted (with Magisk), running latest 8.1 with Feb security patch. This morning I have started experiencing a very strange issue with making phone calls with my phone. Regardless if I use a home screen direct dial shortcut, attempt to dial from within contacts, from call log, etc...I experience a VERY long delay between attempting to place the call and the call actually being made. Upwards of 30 sec or even much longer. I just used the stopwatch app to time a 3 min 10 sec. delay between the time I attempted to make a call by pressing the phone icon next to a recent call in the call log and when the phone actually "dialed" the call. Between the pressing of the button and the actual making of the call - there was no indication the phone had even accepted the input. I have never seen this behavior and it just started today. I have frozen my Call Control app (spam call filtering), Cleared cache and data for the "Phone" app. Disabled Advanced LTE Calling. I'm at a loss...the last app update on the "Phone" app was Feb 7, 2018
Anyone else experienced this or any suggestions? I have searched the forums and reddit and there appear to be some similar issues being reported - but nothing widespread. Any suggestions welcomed.
EDIT: The issue does not occur when booted into safe mode. So now I am hunting for which most recent app update is causing the issue. Good times.
Thanks!
S
sb1893 said:
Really strange issue just started occurring today as far as I can tell. I am on a Google Pixel XL, unlocked, rooted (with Magisk), running latest 8.1 with Feb security patch. This morning I have started experiencing a very strange issue with making phone calls with my phone. Regardless if I use a home screen direct dial shortcut, attempt to dial from within contacts, from call log, etc...I experience a VERY long delay between attempting to place the call and the call actually being made. Upwards of 30 sec or even much longer. I just used the stopwatch app to time a 3 min 10 sec. delay between the time I attempted to make a call by pressing the phone icon next to a recent call in the call log and when the phone actually "dialed" the call. Between the pressing of the button and the actual making of the call - there was no indication the phone had even accepted the input. I have never seen this behavior and it just started today. I have frozen my Call Control app (spam call filtering), Cleared cache and data for the "Phone" app. Disabled Advanced LTE Calling. I'm at a loss...the last app update on the "Phone" app was Feb 7, 2018
Anyone else experienced this or any suggestions? I have searched the forums and reddit and there appear to be some similar issues being reported - but nothing widespread. Any suggestions welcomed.
EDIT: The issue does not occur when booted into safe mode. So now I am hunting for which most recent app update is causing the issue. Good times.
Thanks!
S
Click to expand...
Click to collapse
Update: No idea what is going on - but I think I resolved the issue accidentally. I connected my Pixel XL to my computer to try to capture a logcat while the issue was occurring to see if I could find a clue as to the offending app. However, I was unable to reproduce the issue while running the logcat. I disconnected from my computer and now the issue is resolved. Phone calls can be made and respond immediately. This is after multiple reboots, clearing cache, data on phone app, etc did not resolve the issue and it could be readily reproduced.....not sure why the simple act of connecting to computer and running a logcat could have resolved. But oh well.
sb1893 said:
Update: No idea what is going on - but I think I resolved the issue accidentally. I connected my Pixel XL to my computer to try to capture a logcat while the issue was occurring to see if I could find a clue as to the offending app. However, I was unable to reproduce the issue while running the logcat. I disconnected from my computer and now the issue is resolved. Phone calls can be made and respond immediately. This is after multiple reboots, clearing cache, data on phone app, etc did not resolve the issue and it could be readily reproduced.....not sure why the simple act of connecting to computer and running a logcat could have resolved. But oh well.
Click to expand...
Click to collapse
And....issue has recurred. This time after making successfully making call over lunch while connected to Bluetooth system in my car. After that first call...all other calls were impacted by the 30 sec to 2 min delay before going thru. I've tried installing older version of Google Connectivity Services and that did not resolve the issue as well as using the Pixel Launcher (I normally use Nova). Once again, I was able to clear up the issue by simply connecting my phone to my computer via USB. (Didn't even run any commands within ADB this time - just connected phone and was able to make immediate calls again.) So now I think something related to connecting to my car bluetooth system is the culprit. But that car bluetooth version hasn't changed in a long time. And this has never happened before this morning. (I did use bluetooth in the car to make a call this morning when I first noticed the issue.) I'm at a loss. I'll keep playing with it I guess. Hopefully whatever got messed up gets corrected with another update soon.
sb1893 said:
And....issue has recurred. This time after making successfully making call over lunch while connected to Bluetooth system in my car. After that first call...all other calls were impacted by the 30 sec to 2 min delay before going thru. I've tried installing older version of Google Connectivity Services and that did not resolve the issue as well as using the Pixel Launcher (I normally use Nova). Once again, I was able to clear up the issue by simply connecting my phone to my computer via USB. (Didn't even run any commands within ADB this time - just connected phone and was able to make immediate calls again.) So now I think something related to connecting to my car bluetooth system is the culprit. But that car bluetooth version hasn't changed in a long time. And this has never happened before this morning. (I did use bluetooth in the car to make a call this morning when I first noticed the issue.) I'm at a loss. I'll keep playing with it I guess. Hopefully whatever got messed up gets corrected with another update soon.
Click to expand...
Click to collapse
The saga continues. The issue occurs immediately after the first call I attempt when connected to my BMW bluetooth system. From that point on, I experience a 30 sec to 3 min delay between attempting to make a call and the Pixel XL actually initiating the call. The quickest way I have found to resolve the issue is to plug the phone into a charger for a few seconds and I am then again able to place calls. I have verified that the BMW bluetooth software is up to date and has not been updated in over a year. (Again - this issue just started happening yesterday...and I've been on Feb security patch for several weeks). I just cleared cache from within Titanium Backup. Will see if that improves the situation. Very weird. I also was just able to recreate the issue using just a simple Plantronics headset. So I continue to think it is something related to the Bluetooth stack on the phone. But I am not sure how to check to see if any of that has been updated via app update since I upgraded to Feb security patches. (I reproduced the issue at my desk using the headset after clearing cache.)
S
Any news on this? This is absolutely killing me. Sometimes a hard reset stops fixes it, sometimes now. I bought this phone for almost $1,000 in April last year and it can't make phone calls. Pretty bad bug to say the least.
Racermanz said:
Any news on this? This is absolutely killing me. Sometimes a hard reset stops fixes it, sometimes now. I bought this phone for almost $1,000 in April last year and it can't make phone calls. Pretty bad bug to say the least.
Click to expand...
Click to collapse
No - but I'm at least somewhat encouraged to know I am not the only one dealing with the issue. Today I flashed factory images (but preserved my data by removing the -w from the flash-all.bat)...that did not resolve. I've tried the reset app preferences, reboot suggestion I found elsewhere - no dice. Google pushed a new Phone app yesterday - that also did not resolve. I've even tried uninstalling Magisk completely and dropping back to 15.4 - also no help. I'm running out of ideas. I've taken to carrying a charging cable in my car...so if I absolutely need to make a call when the phone isn't behaving, I can just quickly plug it in...which does clear up the issue temporarily. Also keep a charging cable at my desk now...so I'm limping along..but for an issue that just appeared out of nowhere this week...it's been pretty frustating to deal with. Also - I no longer believe being currently connected to Bluetooth is related to the issue. I've been able to get the issue to occur today while not connected to any bluetooth devices.
Try
settings>system>developer options>media>disable USB audio routing
DR3W5K1 said:
Try
settings>system>developer options>media>disable USB audio routing
Click to expand...
Click to collapse
Thanks bros. This is such a strange bug. Right now it works before I have turned off USB audio routing. I have turned off USB audio routing. I will report back if this DOESNT work. If I don't post again we can assume this works.
Thanks DR3W5K1, great name bro.
DR3W5K1 said:
Try
settings>system>developer options>media>disable USB audio routing
Click to expand...
Click to collapse
Just tried to toggle on, which looks to mean Disable. Then rebooted. No luck. Issue still occurs. Thanks for the suggestion. Willing to try anything even to just eliminate as possibility at this point.
Well - I have found a better workaround. When you attempt a call, if you get no response, you can toggle Airplane mode "ON"....You will then see the call you attempted fail. When you turn Airplane mode back "Off" you can can successfully make calls again. Better than having to plug into a charger cable to get the attempted call "unstuck"....still no idea what is going on....but this workaround at least is more palatable, portable, and take a few seconds...hope someone can figure out root cause soon and a proper fix becomes available.
EDIT: Even better workaround. Toggling Mobile Data OFF and ON has the same effect of clearing the issue. And works better when connected to Bluetooth in car as those connections will be maintained vs. using Airplane mode toggle. So - issue seems to be related to Mobile Data somehow - but I have already had Advanced Calling / LTE, etc...turned off as one of my first steps in troubleshooting this issue.
Has OP been down the road of looking at any and all apps installed that are interacting with the Phone permission? I remember snapchat was causing weird beeps for people when making calls until the permission was manually revoked.
Maybe some app is having a bad interaction?
Try changing the network mode in the secret menu dial *#*#4636#*#* to get there
The.Yield said:
Has OP been down the road of looking at any and all apps installed that are interacting with the Phone permission? I remember snapchat was causing weird beeps for people when making calls until the permission was manually revoked.
Maybe some app is having a bad interaction?
Click to expand...
Click to collapse
I have tried that. Sorry for not mentioning it in this thread. At one point I revoked "Phone" permission from all apps other than Phone, Carrier Services, and Contacts. Rebooted. Issue still occurred.
DR3W5K1 said:
Try changing the network mode in the secret menu dial *#*#4636#*#* to get there
Click to expand...
Click to collapse
Ahhh...I had forgotten about this secret menu. Looks like I could permanently toggle off VoLTE, WifiCalling, etc...here. But - not sure I want to go that route...I'm OK at present with Toggling Mobile Data via Quick Settings tile. And hopefully this issue eventually gets solved as mysteriously as it was introduced via some update.
Having the same problems on OG Pixel XL 8.1 with February security patches. All apps latest up to date.
Have tried uninstalling latest Phone app update. Clearing Phone app cache, etc nothing works. Network mode change, SIM reinstall, Network type change.
Only airplane mode toggle will fix it.
FYI mobile data toggle does NOT fix it for me, only airplane toggle. I wonder if network data toggle will only fix it if you are on a network provider currently doing calling over mobile data. Im on TMobile with great LTE coverage, but the mobile data toggle doesn't work for me.
tesla45 said:
Having the same problems on OG Pixel XL 8.1 with February security patches. All apps latest up to date.
Have tried uninstalling latest Phone app update. Clearing Phone app cache, etc nothing works. Network mode change, SIM reinstall, Network type change.
Only airplane mode toggle will fix it.
FYI mobile data toggle does NOT fix it for me, only airplane toggle. I wonder if network data toggle will only fix it if you are on a network provider currently doing calling over mobile data. Im on TMobile with great LTE coverage, but the mobile data toggle doesn't work for me.
Click to expand...
Click to collapse
Interesting....I'm on Verizon and I do believe that they route calls over Mobile data at times. I'm going to stay tuned, but likely done with much more deep investigation at the moment. I've spent enough time down this particular rabbit hole and the Mobile Data toggle is workable for me (not ideal, obviously)...hopefully a permanent fix materializes soon. Thanks to all for their suggestions and moral support. Much appreciated.
OK WORKAROUND FOR ANSWERING CALLS UPDATE:
Found this floating on some other forum, not sure where after this mad dash of a search I did this morning, but original credit to them...
When you receive a call and the phone is active and unlocked, press the power button to lock the phone and bring up the blue call management screen. Now you can swipe to answer.
This seems to work for more than one test call as I've tried this multiple times in a row.
NO REAL WORKAROUND FOR MAKING CALLS YET (outside of airplane mode toggle, or using Google voice/hangouts to place calls).
GOOGLE SUPPORT - THIS IS CLEARLY A SOFTWARE ISSUE, not a 3rd party app issue either since the problem goes away for answering calls when you press the lock screen or toggle airplane mode for placing calls. Please STOP ASKING CUSTOMERS TO invest hours of time (or money) FACTORY RESETTING PHONES, or REPLACING/BUYING NEW PHONES.
MY HUNCH is there is some core google service that isn't being used in SAFE MODE, but starts being used on NORMAL BOOT that is causing all these issues. I really DOUBT its a 3rd party app.
Install the stock again clearing all the data. Don't restore anything with titanium or install any extra apps. Then make a call.
tesla45 said:
OK WORKAROUND FOR ANSWERING CALLS UPDATE:
Found this floating on some other forum, not sure where after this mad dash of a search I did this morning, but original credit to them...
When you receive a call and the phone is active and unlocked, press the power button to lock the phone and bring up the blue call management screen. Now you can swipe to answer.
This seems to work for more than one test call as I've tried this multiple times in a row.
NO REAL WORKAROUND FOR MAKING CALLS YET (outside of airplane mode toggle, or using Google voice/hangouts to place calls).
GOOGLE SUPPORT - THIS IS CLEARLY A SOFTWARE ISSUE, not a 3rd party app issue either since the problem goes away for answering calls when you press the lock screen or toggle airplane mode for placing calls. Please STOP ASKING CUSTOMERS TO invest hours of time (or money) FACTORY RESETTING PHONES, or REPLACING/BUYING NEW PHONES.
MY HUNCH is there is some core google service that isn't being used in SAFE MODE, but starts being used on NORMAL BOOT that is causing all these issues. I really DOUBT its a 3rd party app.
Click to expand...
Click to collapse
And all this time, I thought my problem was only on the delay in placing calls. I just tested and confirmed that I am also having the same issue of being unable to answer calls. I also verified that the workaround you describe above works perfectly for me for answering calls. Also - I appreciate the suggestion to restore to fully factory reset, wiping data, and test prior to installing any apps....BUT I am not willing to invest that amount of time when I have viable workarounds. I agree that this is almost certainly a Google software issue in some core app or service and I'm hoping that we will see a resolution shortly...(maybe in March Security patches? - but I'm not holding out hope as I haven't seen that much widespread concern about this issue elsewhere.)
sb1893 said:
And all this time, I thought my problem was only on the delay in placing calls. I just tested and confirmed that I am also having the same issue of being unable to answer calls. I also verified that the workaround you describe above works perfectly for me for answering calls. Also - I appreciate the suggestion to restore to fully factory reset, wiping data, and test prior to installing any apps....BUT I am not willing to invest that amount of time when I have viable workarounds. I agree that this is almost certainly a Google software issue in some core app or service and I'm hoping that we will see a resolution shortly...(maybe in March Security patches? - but I'm not holding out hope as I haven't seen that much widespread concern about this issue elsewhere.)
Click to expand...
Click to collapse
Glad the workaround helps you too. My emphasis CAPS in my last post was clearly misleading, I was actually suggesting NOT to reinstall/factory reset because I don't believe that solves the problem long term and its a huge ask for a customer (when really Google should be solving this problem for us).
Based on this little workaround its clearly a software problem that Google needs to address, I've raised the issues on many threads in their product forums ... hope it gets to the right people ASAP because I believe lots of Pixel users are running into the problem (both Pixel 2 and 1st gen, another indication its NOT a HW problem).
Keep the workarounds coming folks!