I just updated to DK28 using the update.zip over stock software (no root) and on top of various new features and new bugs, I've noticed a strange new behavior.
At least several times per hour, my phone will give a quick vibration pulse, then maybe a second or two later will give two (or sometimes three) real quick pulses. I have no idea why it's doing this and whether it means something or not. Anyone know?
I can't seem to correlate the behavior to anything in particular the phone is doing at the time. It happens with the phone sleeping, and it does it while I'm using it. It happens when I'm on the home screen, when I'm reading web articles, when I'm playing with other apps, when it's on the charger, when it's off...
pilby said:
I just updated to DK28 using the update.zip over stock software (no root) and on top of various new features and new bugs, I've noticed a strange new behavior.
At least several times per hour, my phone will give a quick vibration pulse, then maybe a second or two later will give two (or sometimes three) real quick pulses. I have no idea why it's doing this and whether it means something or not. Anyone know?
I can't seem to correlate the behavior to anything in particular the phone is doing at the time. It happens with the phone sleeping, and it does it while I'm using it. It happens when I'm on the home screen, when I'm reading web articles, when I'm playing with other apps, when it's on the charger, when it's off...
Click to expand...
Click to collapse
I got that too, plus lag and other bugs when first went to 2.2 (rooted 2.1 and used update.zip). Did you wipe when you updated? I didn't so it was acting weird... Plus the GPS didn't work so I did the Odin thing and now it works fantastic.
Did you wipe when you updated?
Click to expand...
Click to collapse
No. I probably should.
I just wondered whether these little vibration pulses were meant to indicate something, or whether they're just a bug.
happens when an app crashes
My vibration was related to turning on the WIFI became very unstable. The DK28 I had came with clockwork mod so I did a recovery to Epic Experence 2.0.7 chosing the recover form a specific zip file I had copied to my SDcard. Fixed the vibration problem and my USB connection then agin worked on my Windows 7 laptop
This is really weird.
I know people have been having problems with Loss of Service, but so far, I've only had it happen once or twice. What's really bothering me, is that I've noticed an invisible service dropping problem that's actually way worse.
Twice now, my phone has full signal bars, and isn't roaming, but my wife will come home and say she sent me some texts. Sure enough, no texts. So I reboot, and suddenly I get a flood of text and voicemail alerts. So, not only was I not getting texts, but all calls were going straight to voicemail, as if the phone was powered off.
Has anyone noticed this?
I'm not rooted, no alternative kernel, nothing. I'm completely stock. If this keeps up, I have no alternative but to return the phone. I have a job where I have to be available for emergency alerts, and this is definitely a major problem.
I mean... why would the phone say it has a connection if it clearly doesn't?
Yeah can confirm the same. Its like the phone has los but doesnt realize it.
Sent from my SPH-D710 using XDA App
This is definitely a problem. It's usually referred to as "Stealth LOS". (or "POOS" but I have no idea what that stands for.)
If you decide to keep the phone, a workaround is to set Tasker to automatically reboot if it senses no signal. It should work even for the stealth cases. Obviously not everyone will feel that they should have to workaround the issue though.
Anyone noticing the location GPS is funky? I typically turn my GPS off when not in use and I am finding that when using the PullDown toggle, the annoying Location Icon/Notification gets stuck on, and other times won't come on after its been off.
The only way to fix it is to turn it off and reboot, or turn it on and reboot. But after it gets toggles, it gets screwy again.
I haven't done much testing yet to see if it is just the icon or actually the GPS failing to toggle. Also I am wondering if going through settings to toggle is a work around.
I am out of town for work but wanted to quickly throw it out there to see if anyone others experience this weird behavior. I don't have time this week to really sit down and play with it, so a quick fix (if available) is known.
+1 on this. Just noticed the other day when I had to navigate to a party. I arrived and turned off location and it was still stuck in notification tray. Think it went away eventually, but I didn't have time to reboot so not sure what happened. Will keep an eye on it next time though.
Also, noticed the phone has trouble switching from 1x back to 4g. Has to use airplane mode to cycle the radio.
Yea I noticed that too. Again I am traveling and normally have GPS off and only turn it on when I actually launch Google Maps.
I was listening to Pandora mostly with no issues on my 8hr drive but twice, I think, I had to toggle airplane mode to get back data.
The Location notification is ridiculous. I mean its stupidly annoying already but now its getting stuck.
player911 said:
Yea I noticed that too. Again I am traveling and normally have GPS off and only turn it on when I actually launch Google Maps.
I was listening to Pandora mostly with no issues on my 8hr drive but twice, I think, I had to toggle airplane mode to get back data.
The Location notification is ridiculous. I mean its stupidly annoying already but now its getting stuck.
Click to expand...
Click to collapse
Just chiming in. I haven't noticed these problems. Then again I've only been on MM for 5 days now.
I get the location icon stuck in the tray as well. Reboot is the only cure.
New Wifi lag is the biggest problem for me on MM.
phonepie said:
Just chiming in. I haven't noticed these problems. Then again I've only been on MM for 5 days now.
Click to expand...
Click to collapse
You really only notice it if you turn off Location, the little PIN notification gets stuck and doesn't go away on the status bar and notification that says Location on or something.
Pretty annoying.
Also my wifi just randomly stops working. I have to disconnect, reconnect and it starts again. Different topic though.
player911 said:
You really only notice it if you turn off Location, the little PIN notification gets stuck and doesn't go away on the status bar and notification that says Location on or something.
Pretty annoying.
Also my wifi just randomly stops working. I have to disconnect, reconnect and it starts again. Different topic though.
Click to expand...
Click to collapse
Ah ok, I hadn't had that problem. As of last night I downgraded and then rooted and removed bloatware. So doubt I'll see them problems. Though I am facing a few minor ones mainly with the all apps dual window mod. But like you said that's a different topic. Main reasons I downgraded was of course because I like full control over something I own. But wanted the 60fps video recording which I'm pretty sure we can all agree should have been included with the G4. I also finally found a nice work around for enabling silent mode with the actual volume button since the xposed module with true silent didn't work for the G4. Sorry I'm getting off topic here. But hope you find a fix.
Yea I was good with lollipop. Marshmallow hasn't included anything except bugs. I resisted the upgrade for a while but I was not rooted and the System Update popping up constantly was drivingme crazy.
A6 fixed a few annoying bugs for me but brought others.
The location notification getting stuck can happen even with location on, I never turn mine off.
Biggest problem for me WiFi disconnecting at 15%, and needing a reboot to reconnect.
Yea the location notification does get stuck regardless if turned off or not.
I ended up getting rid of the G4 because of the problems. (Qi Charging, wifi disconnects, etc).
Sometimes, not always, when I restart my phone, things get a little crazy and somehow they must be all related. It happens as often as approx once a week. What happens is the following things:
1- I get an email from Where's My Droid that my SIM card or phone number has changed
2- Network-provided time zone changes to Central European Summertime
3- Wifi calling is turned off (however this doesn't normally stay on for some reason)
4- Visual voicemail in the phone app is missing despite still being turned on
5 - APN is not selected (the circle next to Verizon is empty aka does not have the blue dot in it)
I am on 7.1.2 and rooted. Does this happen to anyone else and is there any fix? What could be the cause?
Edit: I doubt this is related, but since I am looking for general feedback for strange bugs with my phone...
Another thing that happens is sometimes while using my phone, apps randomly reload (lack of a better word)
By reload, what happens is the app does not fully close and reopen. What happens is the app remains open ("heading" bar at the top remains) but the rest of the page I am on goes completely blank and then returns with any previous changes undone.
So say I was writing an email in gmail, the red bar at the top with the back arrow and trash can, etc. stays while the rest goes blank and any text I wrote will be gone and I have to start from the beginning. Usually when this is happening, it continues to happen repetitively for a little while. Eventually it just stops on its own. It does not seem to be related to any specific app (since it happens with a bunch of apps) unless maybe it is related to something like Swype keyboard that is always on.
Does that happen to anyone else too? What is causing this??
If your phone is 128g your nand is bad and you need a replacement. Google is aware of the issue and should swap no problem.
DR3W5K1 said:
If your phone is 128g your nand is bad and you need a replacement. Google is aware of the issue and should swap no problem.
Click to expand...
Click to collapse
Thank you! I do have 128GB. I'm glad I finally asked!
NP glad to assist Buddy
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!