Hey all,
Have my phone on Vibrate and when I receive a Google mail the phone isn't vibrating and the LED isn't flashing. As far as I can see all options in Google mail and the phone settings suggest I should be getting both.
Any ideas?
Thanks
Russ
Hmmmmm a reboot seems to have fixed this, lets hope it doesn't get into a habit of it
didn't work for me, rebooted, but still no vibrate on new SMS, light flashing, tho
Apologize for cross-posting, but I'm getting frustrated with this. A reboot didn't help me either.
Everything was working before, but just today I noticed it refused to vibrate on email notifications. WinMo used to have a similar annoying bug, but it was related to replies. This bug is affecting all messaging notifications, i.e. Exchange, pop3, Gmail and SMS.
I've gone in to general settings and put vibrate on. I've gone into each account and turned vibrate on. I've gone into Messaging (SMS) and turned vibrate on. Vibrate is basically turned on throughout the system, but it's still not vibrating except for phone calls.
I've uninstalled all of the last apps I had installed to no avail.
Anyone with any advice?
Last resort could be hard reset
EddyOS said:
Last resort could be hard reset
Click to expand...
Click to collapse
Not really keen on hard reseting, but will try that as a last resort.
I ended up fixing it with a hard reset.
First time around, I chose to reinstall the settings from the auto backup that was on the SD card, but I experienced the same behaviour.
Redid the hard reset and opted for cancel when asked about reinstalling the backup settings and all seems well so far.
Suspect it was a dodgy app or could have been that running the battery down flips a software switch to turn off vibrations, but the switch has a hard time flipping back. Will wait and see how long I can keep the vibrating notifications, but now I know how to solve it.
On another note, talk about a waste with that auto backup function. I mean, to really be useful you should be able to choose when it backs up and which backup you want to reinstall. Having it constantly backup settings like it does is bound to backup whatever went wrong in the first place. Oh well.
Starting last night, my phone's BT won't stay enabled. If I turn it on, it turns itself back off a second or two later. Restarting the phone fixed it for a few hours, but the problem soon returned and now restarting does not even temporarily relieve it.
I've seen some reports that factory-reset has solved this problem on other phones, so I'll try that later. I'm inclined to suspect a hardware problem, though. The phone has worked great since I got it last year, and I sideloaded BPE6 as soon as it was available in May, with no difficulties until yesterday. I don't use any power-optimizing apps.
UPDATE: Before resorting to factory-reset, I used the Application Manager to clear cache and data for Bluetooth Share and Bluetooth Test. That seems to have fixed it, at least for now.
Further update: the above fix was only temporary. Bluetooth stopped working again a few hours later. Clearing recovery cache doesn't help. However, the problem does not seem to occur in Safe Mode. So maybe some third-party app keeps turning BT off somehow.
Sounds like factory reset time!
Sent from my SAMSUNG-SM-N920A using XDA-Developers mobile app
whmgreen said:
Sounds like factory reset time!
Click to expand...
Click to collapse
Yup. I resorted to that last night. Back to normal so far.
I've been experiencing several issues with my Pixel XL recently, and I'm not sure how they might be related to one another or how to resolve them. Before I resort to possibly resetting the device entirely, I was wondering if anyone might have any bright ideas.
1. I was having issues reconnecting to the Project Fi network after the connection was lost without resetting the device. This appears to have been resolved after a call to the Project Fi team, but toggling airplane mode did nothing.
2. Play Store app updates seem to take forever now. They get to 100% downloaded and just sit there for minutes or longer before installing.
3. Notifications for apps are just broken a lot of the time. They arrive hours late if they arrive at all.
Rebooting and/or clearing the cache do not seem to help with the above issues.
Does this all point to anything? I've never bother rooting the device, so I'm not sure what could possibly have messed things up this badly.
Sounds like a factory reset is needed. Sucks but it'll fix all your issues.
My wife has a G7 Thinq that has been having this problem for a while now. She gets the debris/moisture error when the phone has had no exposure to water at all. There is nothing in the port at all. No amount of drying/cleaning makes any difference. When the error occurs, she gets frequent notifications and can only charge the phone wirelessly. The only fix is to factory reset the phone. Then, it's fine for a while (it was 2-3 months this last time), as long as she does not restart the phone. It often, but not always, recurs after a restart. Once the error occurs, it persists until a factory reset.
Because it goes away after a factory reset, I'm inclined to think it's a software issue, but I've had no luck in identifying an app responsible for it. Has anyone else seen this behavior, or know how to solve it? It has the stock ROM on it, and I've wondered if a custom ROM would fix the problem. However, she likes the stock ROM, so I'm not exactly eager to change that.
Try a hard reboot (not reset).
Clear system cache.
It could be an update causing it. Disable all auto updates. Try rolling the updated ones back to factory loads especially system apks.
Does it do it in safe mode? If so it's likely a system apk, firmware or a hardware failure.
blackhawk said:
Try a hard reboot (not reset).
Clear system cache.
It could be an update causing it. Disable all auto updates. Try rolling the updated ones back to factory loads especially system apks.
Does it do it in safe mode? If so it's likely a system apk, firmware or a hardware failure.
Click to expand...
Click to collapse
When I've done the factory reset before, I've just done it through the system settings menu and assumed that would also clear the cache. Is that not so?
When you say "hard reboot (not reset)", do you mean to do the factory reset with the hardware buttons, rather than through the settings menu? Does that do something different?
As for updates, auto updates are off. I'll try rolling back updates and see if that makes any difference.
I vaguely remember booting into safe mode back when this first manifested many months ago. I think the error was still there in safe mode, but it was so long ago I can't remember for sure. I'll check that, too.
drfarmkid said:
When I've done the factory reset before, I've just done it through the system settings menu and assumed that would also clear the cache. Is that not so?
When you say "hard reboot (not reset)", do you mean to do the factory reset with the hardware buttons, rather than through the settings menu? Does that do something different?
As for updates, auto updates are off. I'll try rolling back updates and see if that makes any difference.
I vaguely remember booting into safe mode back when this first manifested many months ago. I think the error was still there in safe mode, but it was so long ago I can't remember for sure. I'll check that, too.
Click to expand...
Click to collapse
If it didn't crop up right after the reload it indicates something that was added or a changed setting.
Clearing the system cache can only be done off the boot menu. This can cure many types of erratic behaviors.
For individual apks clearing their data can do the trick when clearing the cache doesn't.
A hard reboot simulates pulling the battery or pull the battery if it's removable.
I run many of my system apks as the factory loaded versions because of issues with their updated versions.
Next reload pay close attention to any updates.
If it's software caused it may prove a challenge to track down.
Could be an internal hardware failure. Try a known good cable and charger. Google the issue, others may have had the same problem and have a solution.
Clearing the cache, factory resetting the phone, etc. didn't work this time around. I was going to try putting a custom ROM on it, until I started looking into it and found out the bootloader can't be unlocked (it's the T-mobile version).
In the service menu (dial *#546368#*710#) there is a setting to shut off moisture detection. That also didn't fix it. However, I did find something in there that I don't understand that might be informative. My daughter has the same phone, so I looked through some things in there comparing the two. Under a menu called "Type-C checker" there is a table where the two phones differ. My wife's phone says:
Supported ModeUFP DFPMODEFAULTPOWER ROLEFAULTDATA ROLEFAULTVCONNN
My daughter's phone says "NONE" where my wife's says "FAULT". Does that mean anything?
I'm now suspecting some sort of hardware fault, perhaps a short in the charging port. I can buy that daughter board with the USB port for ~$15. What are the odds replacing that will fix it?
Hmmm... That's interesting. After several days of the notification never going away, even after trying every fix for the problem, it went away on it's own about an hour after posting that last message. Out of curiosity, I looked in the service menu, and those three things that said "FAULT" now say "NONE", just like my daughter's phone without the problem. I have no idea what those things mean, but apparently it has something to do with the error. I don't know what fixed it either, but it wasn't anything I did.
drfarmkid said:
Hmmm... That's interesting. After several days of the notification never going away, even after trying every fix for the problem, it went away on it's own about an hour after posting that last message. Out of curiosity, I looked in the service menu, and those three things that said "FAULT" now say "NONE", just like my daughter's phone without the problem. I have no idea what those things mean, but apparently it has something to do with the error. I don't know what fixed it either, but it wasn't anything I did.
Click to expand...
Click to collapse
Hopefully it's a permanent change.
Androids wuv attention...
drfarmkid said:
Hmmm... That's interesting. After several days of the notification never going away, even after trying every fix for the problem, it went away on it's own about an hour after posting that last message. Out of curiosity, I looked in the service menu, and those three things that said "FAULT" now say "NONE", just like my daughter's phone without the problem. I have no idea what those things mean, but apparently it has something to do with the error. I don't know what fixed it either, but it wasn't anything I did.
Click to expand...
Click to collapse
hey, can you have found what was the issue because I have exactly same issue like your phone.
After upgrading to the latest update, my DPI is affected on both screen. They are almost identical when folded and unfolded. I can't reset it. I've tried turning it off and on, reset all settings, factory reset, as well as Odin. I cannot seem to figure this out. I've Google this and no luck. Has anyone experienced this??