Related
Is anybody getting this weird issue when they're typing: The keyboard all of a sudden just goes away on it's own after 2 or 3 keystrokes. It happens a lot when I use the Bing Search function. I'll get two or three letters down then the keyboard abruptly goes away. So I have to get two or three key presses in each time I restart the process.
Anybody know what could be causing this? It's not just limited to my Bing Search, I literally got so frustrated trying to start this thread through my phone's browser that I had to dig out the laptop instead.
And this is happening on a Lumia 900?
Sent from my Lumia 900 using Board Express
sorry not I
iiDeadSeriousii said:
Is anybody getting this weird issue when they're typing: The keyboard all of a sudden just goes away on it's own after 2 or 3 keystrokes. It happens a lot when I use the Bing Search function. I'll get two or three letters down then the keyboard abruptly goes away. So I have to get two or three key presses in each time I restart the process.
Anybody know what could be causing this? It's not just limited to my Bing Search, I literally got so frustrated trying to start this thread through my phone's browser that I had to dig out the laptop instead.
Click to expand...
Click to collapse
the symptoms are those of the disappearing keyboard issue with mango. Its supposedly fixed in this release of mango. However several people have reported seeing it.
I suggest you report it to Nokia at the web site. You won't be able to fix it on your own.
alodar1 said:
the symptoms are those of the disappearing keyboard issue with mango. Its supposedly fixed in this release of mango. However several people have reported seeing it.
I suggest you report it to Nokia at the web site. You won't be able to fix it on your own.
Click to expand...
Click to collapse
This still happens to me occasionally on both my original Focus, and my Lumia 900. Both are updated.
alodar1 said:
the symptoms are those of the disappearing keyboard issue with mango. Its supposedly fixed in this release of mango. However several people have reported seeing it.
I suggest you report it to Nokia at the web site. You won't be able to fix it on your own.
Click to expand...
Click to collapse
Ok, I didn't know if it was a symptom of Mango or the Lumia. It's just so weird when it happens, I notice it when I'm low on battery more often, but idk what sort of relevance that would have. Thanks for the tip though.
Yeah, I get it quite often on my Lumia 900. Also my Radar still has it happen occasionally, my girlfriends Radar has it happen more than mine. All updated as well.
Sent from my Lumia 900 using XDA Windows Phone 7 App
Are you sure you're not accidently rubbing you hand/finger on the back button? The back button, since it's universal, will remove the keyboard if it's on screen. And because Back, Home and Search button all use capative touch instead of having to push them, simply rubbing or bumping them will cause them to activate.
I had this problem when I first got my Lumia, but I've adjusted and adapted.
SwimSwim said:
Are you sure you're not accidently rubbing you hand/finger on the back button? The back button, since it's universal, will remove the keyboard if it's on screen. And because Back, Home and Search button all use capative touch instead of having to push them, simply rubbing or bumping them will cause them to activate.
I had this problem when I first got my Lumia, but I've adjusted and adapted.
Click to expand...
Click to collapse
For me, definitely not. I've tested it many times on my Lumia and my Focus. It's definitely something to do with the keyboard deactivating itself. It happens to me a lot if I try to share an article I read in WP7 News app and go to email. When I try to type my name in the TO: field, I get one or two letters, then it goes away and I end up clicking/typing in the message body.
It seems like if I give it a moment to rest, then start typing, it's less likely to do it, but that's a little annoying, since I want to check my stuff and get on with things. Not a huge issue, mind you, but annoying none the less.
No, im not accidentally touching the back buttons.I'll ask my girlfriend if she's having the same problem, but it's gotta be a software issue from what I'm hearing now.
SuperSport said:
For me, definitely not. I've tested it many times on my Lumia and my Focus. It's definitely something to do with the keyboard deactivating itself. It happens to me a lot if I try to share an article I read in WP7 News app and go to email. When I try to type my name in the TO: field, I get one or two letters, then it goes away and I end up clicking/typing in the message body.
It seems like if I give it a moment to rest, then start typing, it's less likely to do it, but that's a little annoying, since I want to check my stuff and get on with things. Not a huge issue, mind you, but annoying none the less.
Click to expand...
Click to collapse
Huh, this doesn't happen to me though. Guess it's only effecting certian modles... Nonetheless, this kind of defeats their whole add campaign (Smartphone beta test is over)
iiDeadSeriousii said:
Ok, I didn't know if it was a symptom of Mango or the Lumia. It's just so weird when it happens, I notice it when I'm low on battery more often, but idk what sort of relevance that would have. Thanks for the tip though.
Click to expand...
Click to collapse
at&t has not rolled the fix out yet, but the lumia supposedly has it. Other carriers that rolled out the fix, still report some problems, though not nearly as widespread. AT&T says they will roll out the fix around the tango release timeframe..i think it needs more work.
Mine is doing it now after updating to the latest software, this sucks! I hope they fix it asap, very annoying when composing text and the keyboard disappear!
humblehyper said:
Mine is doing it now after updating to the latest software, this sucks! I hope they fix it asap, very annoying when composing text and the keyboard disappear!
Click to expand...
Click to collapse
I have actually noticed this problem less and less as the weeks have gone on. It's not so much that I'm getting used to it, cause I notice when it does happen, I think it was just a weird thing. I haven't had a problem personally since the update either.
Hi,
I don't have this issue on my 900 nor does my wife see it on hers. That said, let me offer what I know about the keyboard disappearing from previous hardware/builds.
When I had this issue on earlier hardware (Focus/Focus S) it was caused by apps set to run in the background. When an app is set to run in the background, the app would shift focus away from the current user task for a split second, and if you have the keyboard out the keyboard thinks you've switched to a different task and it closes. The way I worked around it was to disable background tasking for all my apps (settings -> applications -> background tasks. Note that when an app updates itself, it will reset this background task setting so you have to reset it. I never saw this problem again after I updated my Focus S to 8107. Still, it might not hurt as a troubleshooting step to disable background tasks and see if the problem reappears.
Michael
so far, i've not encounter this issue with my phone yet, but seems to be affecting mango version only, coz mine is already on tango....
So the other day the app Widgetsoid releases a "Completely rewritten" update for their sweet app. I was obviously excited to play with this and set about recreating all of my toggles. One toggle I have is to toggle the camera flash on/off which is very handy to have a widget for on the homescreen. Another one I use toggles the screen always on/off which is handy when reading long articles. So I was using the screen always on toggle as a reading light (as the camera LED can be overly bright) when, after some time, my phone locked up. Following my natural instinct I pulled the battery and powered it back on. When it came back on I noticed that the screen always on toggle was still in the "on" position though I believe (honestly can't remember for sure) that the screen was timing out as if it were off. Anyways I put this out of my mind and decided to use the flashlight toggle as the screen hadn't been quite as bright as I wanted. However, upon toggling the flashlight to "on" The toggle froze in mid activation. I could see that I had clicked it but the animation never finished and the flashlight never turned on. I gave it several minutes to sort itself out and when it didn't I did another battery pull thinking that would clear it up. Well it didn't. Upon the phone restarting I was greeted by "Tango has stopped responding". Then when I tried the flashlight toggle again I got "Gallery has stopped responding" which flashed up and disappeared too quickly for me to click on it. I tried opening the camera to no avail. "Gallery has stopped responding". So one bug led to another to another to another as bugs so often do. No biggie, I was planning on doing a factory reset soon anyways so I backed up my data and went ahead with that. Unfortunately, when I finished the setup and went back to the camera app it gave me the same error. (please note that I did not restore anything after the reset.) So I did another just for sanity's sake but no change. I went into the bootloader and into recovery, cleared the cache and then did another factory reset. Nada. I downloaded a flashlight app to see if it could tell me anything new, which it sort of did. "Cannot connect to camera", it said when I turned it on. In my search on this forum for a similar issue I came across a post to a different issue talking about how when an app uses the camera it might not have let go when it was finished which causes problems for other apps. This makes enough sense except that I figured the reset would have resolved that issue. Unless, of course, the problem lies in the hardware which I am desperately hoping someone will tell me is foolish.
I'm not really sure what to try next in my troubleshooting short of unlocking the bootloader and flashing either the stock back over it or another ROM. I would prefer to try other possible solutions before this. Correct me if I'm wrong but shouldn't the factory reset restore the system and stock apps to their default state? Almost literally bit for bit? If that is the case then that means the issue isn't with the system or the camera app and must fall to the camera hardware itself? I feel it is worth noting that on about the third factory reset, during the initial setup (quite literally on the first screen) a popup popped saying "Talk has stopped responding". Why the Talk app would stop responding due to some issue with the camera seems out of place. Though as I said and we all know, bugs have a way of spreading to the places you least expect.
Anyways any help, suggestions or questions would be greatly appreciated. This really has me stumped.
I guess the question it boils down to (besides the three I've already asked) is how can I do a full wipe/reset that will actually reset everything? Or is it that the camera is really hung and if so any possible fixes for that? Anyone see any bright red flags waving violently in the storm?
Thanks in advance for any help you can provide
patrioticparadox
I am running 4.1.1 on a Verizon Galaxy Nexus build JRO03O
patrioticparadox said:
So the other day the app Widgetsoid releases a "Completely rewritten" update for their sweet app. I was obviously excited to play with this and set about recreating all of my toggles. One toggle I have is to toggle the camera flash on/off which is very handy to have a widget for on the homescreen. Another one I use toggles the screen always on/off which is handy when reading long articles. So I was using the screen always on toggle as a reading light (as the camera LED can be overly bright) when, after some time, my phone locked up. Following my natural instinct I pulled the battery and powered it back on. When it came back on I noticed that the screen always on toggle was still in the "on" position though I believe (honestly can't remember for sure) that the screen was timing out as if it were off. Anyways I put this out of my mind and decided to use the flashlight toggle as the screen hadn't been quite as bright as I wanted. However, upon toggling the flashlight to "on" The toggle froze in mid activation. I could see that I had clicked it but the animation never finished and the flashlight never turned on. I gave it several minutes to sort itself out and when it didn't I did another battery pull thinking that would clear it up. Well it didn't. Upon the phone restarting I was greeted by "Tango has stopped responding". Then when I tried the flashlight toggle again I got "Gallery has stopped responding" which flashed up and disappeared too quickly for me to click on it. I tried opening the camera to no avail. "Gallery has stopped responding". So one bug led to another to another to another as bugs so often do. No biggie, I was planning on doing a factory reset soon anyways so I backed up my data and went ahead with that. Unfortunately, when I finished the setup and went back to the camera app it gave me the same error. (please note that I did not restore anything after the reset.) So I did another just for sanity's sake but no change. I went into the bootloader and into recovery, cleared the cache and then did another factory reset. Nada. I downloaded a flashlight app to see if it could tell me anything new, which it sort of did. "Cannot connect to camera", it said when I turned it on. In my search on this forum for a similar issue I came across a post to a different issue talking about how when an app uses the camera it might not have let go when it was finished which causes problems for other apps. This makes enough sense except that I figured the reset would have resolved that issue. Unless, of course, the problem lies in the hardware which I am desperately hoping someone will tell me is foolish.
I'm not really sure what to try next in my troubleshooting short of unlocking the bootloader and flashing either the stock back over it or another ROM. I would prefer to try other possible solutions before this. Correct me if I'm wrong but shouldn't the factory reset restore the system and stock apps to their default state? Almost literally bit for bit? If that is the case then that means the issue isn't with the system or the camera app and must fall to the camera hardware itself? I feel it is worth noting that on about the third factory reset, during the initial setup (quite literally on the first screen) a popup popped saying "Talk has stopped responding". Why the Talk app would stop responding due to some issue with the camera seems out of place. Though as I said and we all know, bugs have a way of spreading to the places you least expect.
Anyways any help, suggestions or questions would be greatly appreciated. This really has me stumped.
I guess the question it boils down to (besides the three I've already asked) is how can I do a full wipe/reset that will actually reset everything? Or is it that the camera is really hung and if so any possible fixes for that? Anyone see any bright red flags waving violently in the storm?
Thanks in advance for any help you can provide
patrioticparadox
I am running 4.1.1 on a Verizon Galaxy Nexus build JRO03O
Click to expand...
Click to collapse
I would honestly try to flash another ROM. its hard to tell what is exactly causing this prob but I highly highly highly doubt its hardware. Make sure you wipe data and dalvik a couple times and go to mounts and storage and wipe system too. Do those a couple times, I always do just to be sure it works. Then after that try to flash another ROM stock or custom doesnt matter. This will help a lot.
Just a recommendation, I use and LOVE Codename Android Rom. Very very fast and stable with a lot of features.
Anyways, post back when you wipe everything out and flash a new ROM on there and let me know the outcome.
nothing yet...
myboyblake said:
I would honestly try to flash another ROM. its hard to tell what is exactly causing this prob but I highly highly highly doubt its hardware.
Click to expand...
Click to collapse
Just finished flashing the 4.1.1 back and still the same issue (did all of the data wiping). I'll try a custom ROM now though I doubt its going to make any difference.
What in the world has got a hold of my camera?
No dice
"Unfortunately Talk has stopped responding" on the first screen. "Gallery has stopped responding" when trying to open Camera app.
So despite several wipes and two distinct ROM flashes (used PARANOIDANDROID the second time) my device is still acting up.
Please help me out people. What is causing this error that is lasting across ROM flashes? What can I try to resolve this issue?
Rewiped everything and reflashed PARANOIDANDROID (2.23) just to be sure and still the camera doesn't work
seems like perhaps the registers ended up in an odd state.. know this is for a different phone, but you might give it a shot..
http://www.droidforums.net/forum/dr...amera-app-stoped-working-wont-initialize.html
---------- Post added at 05:03 PM ---------- Previous post was at 04:46 PM ----------
Looks like OMAPFlash can do a full reset on all the camera registers from looking at:
./Targets/Definitions/definitions_omap4.txt
in the OMAPFlash zipfile..
It might be worth a shot..
Slide opultl
No dice... I assume you were referring to clearing the cache and data. I had tried this before but gave it another shot anyways. In case you meant the screenshot part, I did that too and the screenshot captures fine but still the camera does not function. Also holding down the volume down and power keys never shuts the phone off I assume that is device specific (though several seconds after the screenshot captured the screen did flash off then on very quickly). I have tried disabling Gallery and rebooting in the hopes that would free up the hardware. Failed.
I am uber stuck on this.
Why is this persisting across flashes and what can I try to resolve it?
edit: just noticed that the bottom of your post was more info and not a signature. I'll look into that. Ran out of "thanks" for today but I'll get you yours
Since it won't delete....
As an update: I have tried contacting both Verizon and Samsung about the issue. Both recommend returning the device under warranty (as was expected). This would be fine except that I LEARN NOTHING! If the Samsung techies have a protocol/enumeration/anything to discover and resolve the issue then so can I (potentially), which means the general public should have this knowledge too, right? WHAT IS MY NEXT STEP?
(still have not yet OMAP_Flash'ed as I haven't found SOLID documentation on this yet.) (Google searching led me somewhere but left me confused. Please post documentation or the correct link if you have it and thank you) I am open to trying anything. Understand that my bottom line is giving Asurion $50 USD. "I LOST my phone, send me a [new] one". Phone gets replaced and I get to trash the old one. Sweet for everyone right? Wrong.
I don't give two runny, stinky butt creams about the phone itself. Which is not entirely, or honestly, even close to true. I'd hate to see a Nexus that can be saved be completely obliterated. If its totally bricked (which its very hard to do to a Nexus) then go for it. Smash that ***** up! But if, like mine, its recoverable then you owe it to the developer to try to save it. This Galaxy Nexus SCH-I515 reminds me of my SCH-a950. I loved that phone and literally (because of a now EX girlfriend) BEAT THE LIVING SNOT OUT OF IT. I literally threw it at my front porch as hard as I could from a good 30 yards away and yet it survived. Not only did it survive, it thrived. Never failing me (even until I finally upgraded) despite the "wear and F'ing tear" I had inflicted upon it.
I have actually dropped my Nexus several times. I have a massively cracked screen that I would love to show you all, yet the screen still functions as if there were no crack. I can click on the "options" toggle that is in the bottom right corner of many apps as if there were not a MASSIVE chunk of screen missing there. The phone is quite amazing. And before anyone says "oh you dropped it, that could have to do with the errors in the camera", NO. The camera worked just fine until what I described above. Samsung has done quite a magnificent job with this device (and all of their hardware, {I own a 26" computer monitor that kicks ass too}) making it resilient to adversity.
Now please, help me out....
I am hesitant to try the OMAP_flash as I haven't found decent documentation. PLEASE PLEASE post a link.
As I said I can always "lose" the phone and get a new one through insurance. So I'm not worried about screwing the phone, I just want to LEARN about the issue at hand.
What do YOU think is causing this issue?
If someone could post a link to the relevant info about the OMAP_flash then I will be happy to go forward with it.
Aside from all this I am shocked at the relative dismissal of this thread. I am seeking information from experienced members who have expertise on this device and while many are available I have gotten no replies as of yet. (this is not to discount those who have replied as I am very grateful for those suggestions as well) Please take two minutes and give me your thoughts. I don't believe this issue is similar to any other posts here and if you do believe it, kindly point me in that direction.
http://forum.gsmhosting.com/vbb/f63...-i9100g-via-usb-cable-freeeeeeeeeeee-1465412/
Here's a link, sorry I didn't post soon - I don't check back here often..
patrioticparadox said:
(still have not yet OMAP_Flash'ed as I haven't found SOLID documentation on this yet.) (Google searching led me somewhere but left me confused. Please post documentation or the correct link if you have it and thank you) I am open to trying anything. Understand that my bottom line is giving Asurion $50 USD. "I LOST my phone, send me a [new] one". Phone gets replaced and I get to trash the old one. Sweet for everyone right? Wrong.
I don't give two runny, stinky butt creams about the phone itself. Which is not entirely, or honestly, even close to true. I'd hate to see a Nexus that can be saved be completely obliterated. If its totally bricked (which its very hard to do to a Nexus) then go for it. Smash that ***** up! But if, like mine, its recoverable then you owe it to the developer to try to save it. This Galaxy Nexus SCH-I515 reminds me of my SCH-a950. I loved that phone and literally (because of a now EX girlfriend) BEAT THE LIVING SNOT OUT OF IT. I literally threw it at my front porch as hard as I could from a good 30 yards away and yet it survived. Not only did it survive, it thrived. Never failing me (even until I finally upgraded) despite the "wear and F'ing tear" I had inflicted upon it.
I have actually dropped my Nexus several times. I have a massively cracked screen that I would love to show you all, yet the screen still functions as if there were no crack. I can click on the "options" toggle that is in the bottom right corner of many apps as if there were not a MASSIVE chunk of screen missing there. The phone is quite amazing. And before anyone says "oh you dropped it, that could have to do with the errors in the camera", NO. The camera worked just fine until what I described above. Samsung has done quite a magnificent job with this device (and all of their hardware, {I own a 26" computer monitor that kicks ass too}) making it resilient to adversity.
Now please, help me out....
I am hesitant to try the OMAP_flash as I haven't found decent documentation. PLEASE PLEASE post a link.
As I said I can always "lose" the phone and get a new one through insurance. So I'm not worried about screwing the phone, I just want to LEARN about the issue at hand.
What do YOU think is causing this issue?
If someone could post a link to the relevant info about the OMAP_flash then I will be happy to go forward with it.
Aside from all this I am shocked at the relative dismissal of this thread. I am seeking information from experienced members who have expertise on this device and while many are available I have gotten no replies as of yet. (this is not to discount those who have replied as I am very grateful for those suggestions as well) Please take two minutes and give me your thoughts. I don't believe this issue is similar to any other posts here and if you do believe it, kindly point me in that direction.
Click to expand...
Click to collapse
Jesus, will people stop talking about insurance fraud........
It's these kind of people that people in your country have to suffer higher insurance premiums, and the very same group of fraudsters are complaining about high insurance premiums..
Regarding OMAP flash:
1) Remove battery
2) Open device manager
3) Plug your phone to your PC/laptop
4) Right click on OMAP4460, go to properties
5) Drivers tab
6) Update drivers, direct to the OMAP flash folder
7) Run the .bat
8) Reflash a ROM just in case.
I don't think it going to do a reg reset for the camera by default..
This is from: Targets/Definitions/definitions_omap4.txt
CONTROL_CORE_PAD_CAM_GLOBALRESET 0x4A1000C0
It is pulled in and used by:
Targets/Configurations/configuration_omap4460_tuna_8g.txt
CONTROL_CORE_PAD_CAM_GLOBALRESET needs to set for the correct location -- I have not done any digging, so I don't know what the location is..
Just Found this -- https://github.com/omapconf/omapconf/wiki
omapconf can be used to read/write/modify any register from within Android..
Mach3.2 said:
Jesus, will people stop talking about insurance fraud........
It's these kind of people that people in your country have to suffer higher insurance premiums, and the very same group of fraudsters are complaining about high insurance premiums..
Regarding OMAP flash:
1) Remove battery
2) Open device manager
3) Plug your phone to your PC/laptop
4) Right click on OMAP4460, go to properties
5) Drivers tab
6) Update drivers, direct to the OMAP flash folder
7) Run the .bat
8) Reflash a ROM just in case.
Click to expand...
Click to collapse
Insurance fraud? Um get a life! That's not why their premiums are high you ass! They do it to make more money you jack knob. My company charges $65/yr with a $25 deductible with up to 5 claims a year! That's so much better than asurion. And they give you a piece of **** replacement. Is all about money not the customer...now please me nice. Great ideas come from working together not from being an asshat!
First off, I disabled adaptive battery in Android P. Ever since the upgrade from 8 to 9, I noticed that notifications are right around 5 minutes late. I have a couple time-sensitive apps that I need notifications right away. Gmail and another app for my home automation. In Android 8, the were flawless. However, ever since going to 9, not so much.
I also noticed that when I delete messages in the gmail app for gmail and an IMAP email server I have it does nothing with the messages on the server. I login to webmail from a computer and the messages are still in the Inbox.
Anyone have any ideas? I am going to try a wipe again to see if it resolves the issues, but I am out of ideas. I had the above issues in Android 9 beta as well. I would downgrade and it fixed them.
I have the same thing and it turns out it is a common issue with Pie. I have not found a solution yet. I have read all kinds of things people have tried and nothing seems to help. Sorry that I can't be more positive. Hopefully Google will figure something out and fix in an update.
Here is a two page post I started about the issue but there are also many others online describing the same thing:
https://forums.androidcentral.com/android-pie/904647-notifications-delayed-stopped.html
My thought is that the delayed notifications are due to Android Pies implementation of adaptive battery. Maybe try excluding the apps you want to receive notifications from in a timely manner?
Sent from my Pixel 2 XL using XDA Labs
You don't happen to have data saver in the quick tiles turned on by accident do you? That does prevent notifications from getting pushed. Both my parents had this on and a bunch of notifications came through after turning it off. I made sure to remove it from even being an available option.
Sent from my Pixel 2 XL using Tapatalk
been fighting with this issue as well, but it only seems to be gmail, and a couple other apps, my sms notifications seem to come through fine, at least as far as I can tell. I've turned off adaptive battery etc, nothing seems to make a difference. sometimes i can turn my screen on and all the notifications will come flooding in, other times they come through 10ish min later.
yes i have also these issue
and i opened thread on these https://forum.xda-developers.com/pixel-2-xl/help/gmail-sync-problems-pie-t3839357
also i tried many apps, but instead of gmail but yet i didn't find any solution
Triscuit said:
My thought is that the delayed notifications are due to Android Pies implementation of adaptive battery. Maybe try excluding the apps you want to receive notifications from in a timely manner?
Sent from my Pixel 2 XL using XDA Labs
Click to expand...
Click to collapse
Thanks for the suggestion but that is one of the first things I tried. No difference.
EeZeEpEe said:
You don't happen to have data saver in the quick tiles turned on by accident do you? That does prevent notifications from getting pushed.
Sent from my Pixel 2 XL using Tapatalk
Click to expand...
Click to collapse
Made sure it was off early on. No change.
The best way to describe my issue is that once the screen times out and has been off for at least about 5 minutes, notification sounds are delayed. It is sort of like the phone goes into a deeper sleep or something and then the problem arises. As soon as I use my fingerprint to wake the phone, all notifications blast through.
The delay can vary. Sometimes it is only 15 minutes or so, but often it is much longer. It is almost like once in a while an app wants to call home or something and to do so wakes up the phone just enough to allow some notifications through.
There also seem to be some issues with individual apps and notifications that may be fixed when a developer updates their app for Pie. For example, most apps notify immediately when the screen is on or within that first 5 minutes or so after the screen goes off. But since installing Pie, Kuna always has a delay of 5 to 10 minutes before notifying. Kuna does this 100% of the time. In fact if I have the phone awake, looking at the screen when walking out the front door, when the motion sensor is triggered, immediately there is a notification icon. But the sound notification is always delayed. This seems like an issue with Kuna and they are well know for being very slow with updates and fixes but eventually they do fix things. But the notification sound delays described in this thread do indeed seem like a system issue with Pie. Hopefully enough people will have the issue that Google will figure it out and fix.
I am having same issues after updating to Android P. At first, notifications came late about 5 min, but then they started to vary some coming in 15-30 minutes later. Can't figure out what is causing the time difference but either way I can't find a fix. I spoke with Google support and they had no fix as well.
sammys8 said:
I spoke with Google support and they had no fix as well.
Click to expand...
Click to collapse
Did Google give you any indication they were aware of the issue and trying to fix?
Will_T said:
Did Google give you any indication they were aware of the issue and trying to fix?
Click to expand...
Click to collapse
Nope, they didn't mention anything about existing issues or being aware of the issue.
Any one found any solutions or fixes? I feel like my notifications are becoming even more delayed now and have also realized I'm not getting a lot of various notifications at all (through many different apps).
I am guessing you all are aware of this, and have tried, however I just found this recently and thought I would share for anyone that doesn't know.... Settings > Apps and Notifications > Advanced > Special App Access ..... Lots of options here with one of them being battery optimization for individual apps. After I upgraded to P, hardly any of my frequently used apps were given full battery use. Haven't played with all the other options there, however just granting apps full battery seemed to help me out.
3yoders said:
I am guessing you all are aware of this, and have tried, however I just found this recently and thought I would share for anyone that doesn't know.... Settings > Apps and Notifications > Advanced > Special App Access ..... Lots of options here with one of them being battery optimization for individual apps. After I upgraded to P, hardly any of my frequently used apps were given full battery use. Haven't played with all the other options there, however just granting apps full battery seemed to help me out.
Click to expand...
Click to collapse
Just updated some settings, now we wait and see if these buried settings fix my delays.. here's to hoping! :good:
3yoders said:
I am guessing you all are aware of this, and have tried, however I just found this recently and thought I would share for anyone that doesn't know.... Settings > Apps and Notifications > Advanced > Special App Access ..... Lots of options here with one of them being battery optimization for individual apps. After I upgraded to P, hardly any of my frequently used apps were given full battery use. Haven't played with all the other options there, however just granting apps full battery seemed to help me out.
Click to expand...
Click to collapse
One of the first things I tried was giving full useage, (no battery optimization) for all apps that I want notifications from. Did not help. Many other apps are still being optimized. I thought I had previously found a way to turn off all battery optimization but because I do have many apps in that list that are being optimized, I obviously did not. Right now I can't find a global setting to turn off battery optimization even though I thought I did before?
So I noticed this morning, that the main app/notification that's super delayed (5-10min after the event should have triggered) it doesn't happen when my phone is plugged in or i have the screen on in my hand. Even after going through all the battery save features and making sure this app is exempt from them, it still happens if the screen is off, or my phone is off the charger. super annoying. wish there was a fix for this already!
pvtjoker42 said:
So I noticed this morning, that the main app/notification that's super delayed (5-10min after the event should have triggered) it doesn't happen when my phone is plugged in or i have the screen on in my hand. Even after going through all the battery save features and making sure this app is exempt from them, it still happens if the screen is off, or my phone is off the charger. super annoying. wish there was a fix for this already!
Click to expand...
Click to collapse
Verizon sent me a replacement because of this problem. I was apprehensive, but got a very nice re-furb. Still have the same problem, but I got a phone that is indicated as Verizon on the LG site. In developer mode, the bootloader unlock button works. I guess everything isn't bad. I sure hope Google straightens this out soon.
pvtjoker42 said:
So I noticed this morning, that the main app/notification that's super delayed (5-10min after the event should have triggered) it doesn't happen when my phone is plugged in or i have the screen on in my hand.
Click to expand...
Click to collapse
This happens only with Gmail on my phone - WhatsApp and Messages send instant notifications. Messages isn't optimized, the other apps are.
I can live with that, no big deal. Perhaps disabling battery optimization for Gmail would fix this, though.
Interesting note: I was talking to YouMail support today about something else but I asked about an issue where I get an email and transcript of a new voicemail but when I go to the YouMail app that voicemail is not shown until I drag down from the top of the screen to refresh the list. Support told me they are aware of this but can not do anything because it is a problem with the "latest Android version causing delay". So it is becoming a more widely known issue and hopefully Google will fix soon.
Thanks for all the feedback. Speaking of delay, I think I have tried just about every fix here and then some and still no luck. Wiping the phone did nothing as well. At this point, I would almost like to revert back to v8 to get this fixed.
I tried this supposed fix, (reply #51). https://forums.androidcentral.com/a...ifications-delayed-stopped-3.html#post6355714
No idea if it worked for me as when you restart the phone you need to do it again and less than 30 minutes after I went through the steps, my Pixel2 got the October update for Pie and required a restart!
Almost every Samsung android phone I've own has this problem after using it for a period of time. I've had the note 10+ since launch and the dreaded issue has return.
For some apps, I would tap the notification for the app. It would take a few minutes before the app will open.
Anyone has this issue?
I've had it on my note8, Note9 and now the note10+.
Hard reset will fix it but I don't want to reset and start again..
Continuation from note 8 thread: https://forum.xda-developers.com/galaxy-note-8/help/app-lag-clicking-notification-t3781356/page2
I don't have this issue.
Some people prefer to perform an hard reset as soon as they got the phone, before starting using it for the first time ; maybe they had some issues like yours at first, then wanted to avoid them.
Personally I didn't got any at first run.
That's odd, I have not experienced what you say in any of my samsung devices dating from my beloved S3 to this note10+
Yes..i am so confuse why it happens.. When the phone is new or just had a hard reset.. I don't have the issue.. Over time I always get it.
I also have this issue and it's incredibly annoying. Apps will take a full minute to open after being tapped on from the notifications banner. I too have had all but one Note product since the original (skipped the 2nd gen), but this is the first I can recall this issue happening. I'm also experiencing the issue of Google Play store apps getting stuck at 99% or 100% and not installing for 10 minutes or longer.
Is it all apps or certain apps only? Are you running stock or rooted? Exynos or Snapdragon? I haven't seen this issue shown up in a while, but have had it happen on Android devices in general in the past.
aarick said:
Almost every Samsung android phone I've own has this problem after using it for a period of time. I've had the note 10+ since launch and the dreaded issue has return.
For some apps, I would tap the notification for the app. It would take a few minutes before the app will open.
Anyone has this issue?
I've had it on my note8, Note9 and now the note10+.
Hard reset will fix it but I don't want to reset and start again..
Continuation from note 8 thread: https://forum.xda-developers.com/galaxy-note-8/help/app-lag-clicking-notification-t3781356/page2
Click to expand...
Click to collapse
Aaron J said:
I also have this issue and it's incredibly annoying. Apps will take a full minute to open after being tapped on from the notifications banner. I too have had all but one Note product since the original (skipped the 2nd gen), but this is the first I can recall this issue happening. I'm also experiencing the issue of Google Play store apps getting stuck at 99% or 100% and not installing for 10 minutes or longer.
Click to expand...
Click to collapse
I don't have this issue, but as @dhorgas, more info would be helpful if it's a problem that can easily be fixed.
Two have the issue here, It could be a common app both of you are running.
lennie said:
I don't have this issue, but as @dhorgas, more info would be helpful if it's a problem that can easily be fixed.
Two have the issue here, It could be a common app both of you are running.
Click to expand...
Click to collapse
It seems to be related to pendingIntent type notifications as if I tap a notifications that is a collapsed version of all the notifications, the app will load instantly. Have a look at this video I created:
(I didn’t include the tap showing on screen unfortunately, will attempt to do another video next time)
Initial tap was when the notification is collapsed for reolink and that will just open up the app. Happens instantly.
I close the app, expanded the notification and click on specific notification
The app doesn’t open until 8 minutes + later towards the end of the video.
Issue is happening across a fair few apps so I doubt it's common app..
I also have the issue of delayed notifications as discussed here:
https://eu.community.samsung.com/t5...ue-affecting-all-range-of-Samsung/td-p/738070
dhorgas said:
Is it all apps or certain apps only? Are you running stock or rooted? Exynos or Snapdragon? I haven't seen this issue shown up in a while, but have had it happen on Android devices in general in the past.
Click to expand...
Click to collapse
Stock on exynos
Aaron J said:
I also have this issue and it's incredibly annoying. Apps will take a full minute to open after being tapped on from the notifications banner. I too have had all but one Note product since the original (skipped the 2nd gen), but this is the first I can recall this issue happening. I'm also experiencing the issue of Google Play store apps getting stuck at 99% or 100% and not installing for 10 minutes or longer.
Click to expand...
Click to collapse
Have the same issue with the play store. One way to speed it up is to force close play store... Then reopen it..
The app will redownload and should install this time.. Not always..
Quick update: Got fed up and did a factory reset and restored everything. Everything's working fine now. Obviously that's a last resort, but so far it's the only solution I've seen.
aarick said:
It seems to be related to pendingIntent type notifications as if I tap a notifications that is a collapsed version of all the notifications, the app will load instantly. Have a look at this video I created:
(I didn’t include the tap showing on screen unfortunately, will attempt to do another video next time)
Initial tap was when the notification is collapsed for reolink and that will just open up the app. Happens instantly.
I close the app, expanded the notification and click on specific notification
The app doesn’t open until 8 minutes + later towards the end of the video.
Issue is happening across a fair few apps so I doubt it's common app..
I also have the issue of delayed notifications as discussed here:
https://eu.community.samsung.com/t5...ue-affecting-all-range-of-Samsung/td-p/738070
Click to expand...
Click to collapse
Wow. That would drive me crazy. Try backup, hard reset and restore like @Aaron J did and see if that fixes the issue.
lennie said:
Wow. That would drive me crazy. Try backup, hard reset and restore like @Aaron J did and see if that fixes the issue.
Click to expand...
Click to collapse
Yes.. It will fix it.. But it's temporary..
The issue won't happen straight away.. It takes a few weeks/months and will return.. It has happened to me from the note 8, note 9 and now note 10+.
Initially everything will be good and fast.. Then eventually issue will return..
So need to try to get to the root of it..
Aaron J said:
Quick update: Got fed up and did a factory reset and restored everything. Everything's working fine now. Obviously that's a last resort, but so far it's the only solution I've seen.
Click to expand...
Click to collapse
Hope the issue doesn't return for you.. It always returns for me..
I have been dealing with 3 issues in my phone:
-delayed notifications
-slow app opening when tapping notifications
-apps installation through play store delayed after download
So recent development, I have been following this thread on Samsung forums regarding delayed notifications
https://eu.community.samsung.com/t5...ting-all-range-of-Samsung/td-p/738070/page/28
Have tried all the fixes which has given minor relief..
But the last suggestion to disable dynamic lock on windows 10 seems to have fixed the issue for me. Early days but all 3 issues have not reoccured yet today.. Usually my Samsung reminders will not show until I reboot. But today been good so far.
Apps install instantly and apps open from notifications straight away..
Will report back in a few days if anything changes..
aarick said:
I have been dealing with 3 issues in my phone:
-delayed notifications
-slow app opening when tapping notifications
-apps installation through play store delayed after download
So recent development, I have been following this thread on Samsung forums regarding delayed notifications
https://eu.community.samsung.com/t5...ting-all-range-of-Samsung/td-p/738070/page/28
Have tried all the fixes which has given minor relief..
But the last suggestion to disable dynamic lock on windows 10 seems to have fixed the issue for me. Early days but all 3 issues have not reoccured yet today.. Usually my Samsung reminders will not show until I reboot. But today been good so far.
Apps install instantly and apps open from notifications straight away..
Will report back in a few days if anything changes..
Click to expand...
Click to collapse
So ... did this do it? I've been dealing with this for a LONG time. My Note 8 started this crap after the 9 'upgrade', motivated me to get a new Note 10. A few months later, the SAME exact problem is cropping up.
Slow notification reactions, stuck installs, notifications coming in repeatedly, notifications coming in late all at once.
If this isn't resolved soon, my next phone will definitely not be a Samsung.
nokster said:
So ... did this do it? I've been dealing with this for a LONG time. My Note 8 started this crap after the 9 'upgrade', motivated me to get a new Note 10. A few months later, the SAME exact problem is cropping up.
Slow notification reactions, stuck installs, notifications coming in repeatedly, notifications coming in late all at once.
If this isn't resolved soon, my next phone will definitely not be a Samsung.
Click to expand...
Click to collapse
Yes, my issue is gone now. Try removing windows dynamic lock and unpair your phone from your laptop if you have this setup.
If not, try slowly removing other Bluetooth devices.
For me, a Bluetooth yeelock also caused the delay to return..I have to reboot each time after using the lock to get it back to normal.
I also think a plantronics desktop headset was also causing the issue as I was getting the lag everytime I reach home since removing windows dynamic lock. I have since unplugged it and unpaired. So far been good for a few weeks now.
I heard this issue wasn't specific to Samsung but might be an Android issue..i think it started with Android 9.0 as you have mentioned as I never had this issue when I was using the note 8 before one ui.. But note 9 and 10+ both had issues..
Similar issue mentioned on pixel phone support:
https://support.google.com/pixelphone/thread/5024453?hl=en
aarick said:
Yes, my issue is gone now. Try removing windows dynamic lock and unpair your phone from your laptop if you have this setup.
If not, try slowly removing other Bluetooth devices.
For me, a Bluetooth yeelock also caused the delay to return..I have to reboot each time after using the lock to get it back to normal.
I also think a plantronics desktop headset was also causing the issue as I was getting the lag everytime I reach home since removing windows dynamic lock. I have since unplugged it and unpaired. So far been good for a few weeks now.
I heard this issue wasn't specific to Samsung but might be an Android issue..i think it started with Android 9.0 as you have mentioned as I never had this issue when I was using the note 8 before one ui.. But note 9 and 10+ both had issues..
Similar issue mentioned on pixel phone support:
https://support.google.com/pixelphone/thread/5024453?hl=en
Click to expand...
Click to collapse
I don't have Dynamic Lock set up, nor do any of my computers have bluetooth enabled. BUT I do have this cursed Plantronics PLT W8200 series headset that has been nothing but buggy since I got it. Not surprised if this is the cause. I just unpaired it - fingers crossed.
I hope that's it because otherwise, it's just 2 other pretty crucial devices I have paired.
nokster said:
I don't have Dynamic Lock set up, nor do any of my computers have bluetooth enabled. BUT I do have this cursed Plantronics PLT W8200 series headset that has been nothing but buggy since I got it. Not surprised if this is the cause. I just unpaired it - fingers crossed.
I hope that's it because otherwise, it's just 2 other pretty crucial devices I have paired.
Click to expand...
Click to collapse
Would be good to hear if this fixes your issue. Please make sure you reboot after unpairing too and if possible completely unplug the plantronics as I think it might try to connect to your phone still (but fail) and potentially still bring the issue back as my yeelock doesn't even show up as a paired device, the app just sends msg to it via bluetooth and I still have delays after using it.
Keep us updated...
aarick said:
Would be good to hear if this fixes your issue. Please make sure you reboot after unpairing too and if possible completely unplug the plantronics as I think it might try to connect to your phone still (but fail) and potentially still bring the issue back as my yeelock doesn't even show up as a paired device, the app just sends msg to it via bluetooth and I still have delays after using it.
Keep us updated...
Click to expand...
Click to collapse
So after the weekend of having the Plantronics headset un-paired, it *seems* better. Hopefully it stays that way.
I've been having an issue with my Z2 Force that I've never had with any of my other phones. For some reason, it acts like I'm hitting the home button, even when I'm not touching it. I could be using a web browser, the XBox app, or any other app and it will go back to whatever launcher I have set as default. It doesn't close the app, it just minimizes it. I've tried disabling the home button for navigating & use the touch buttons instead, and when that didn't work I tried doing a factory reset. Well, it's still doing it, and I'm to the point where I'm very tempted to try to use one of the rooting methods I was able to find online, one of which does mention the specific model of my Verizon variant (XT1789-01). I can live without root if needed, but this 'phantom home button pressing' thing is driving me nuts. Any help is appreciated, and thanks.
I have 4 Moto Z2 Force in my house, 2 of them (Android 9, Verizon version) have this same issue.
Eco0901 said:
I have 4 Moto Z2 Force in my house, 2 of them (Android 9, Verizon version) have this same issue.
Click to expand...
Click to collapse
I'm still working on getting myself to go through with trying the root method I found. I think it'd work, but my main issue would be with making sure I can find a rooted ROM for the phone. Assuming the method works and I don't bork my phone, I'd still need a different ROM to install in order to determine if it's a hardware issue or software based. By the way, on the chance you're thinking of trying to remove the screen protector, be aware it is realllllllly stuck on there. I almost pulled my screen off, but I was able to remove it & was rewarded with a bunch of left over residue.
At any rate, if I do actually get myself to do the root thing, I'll be sure to post my results here.
will4958 said:
I'm still working on getting myself to go through with trying the root method I found. I think it'd work, but my main issue would be with making sure I can find a rooted ROM for the phone. Assuming the method works and I don't bork my phone, I'd still need a different ROM to install in order to determine if it's a hardware issue or software based. By the way, on the chance you're thinking of trying to remove the screen protector, be aware it is realllllllly stuck on there. I almost pulled my screen off, but I was able to remove it & was rewarded with a bunch of left over residue.
At any rate, if I do actually get myself to do the root thing, I'll be sure to post my results here.
Click to expand...
Click to collapse
I use the ROM stock so isn't the root that cause the problem, but I hope you find the way, my only hope is on you, actually ):
Eco0901 said:
I use the ROM stock so isn't the root that cause the problem, but I hope you find the way, my only hope is on you, actually ):
Click to expand...
Click to collapse
My concern is whether the root method I found is legit or not. The only reason why I want to attempt it is because the description mentions the specific model of my phone. All variants of the Z2 Force start with XT789-, but it's the number after the '-' you have to look for, and for Verizon users is '01'. Rooting the phone will let me install a different version of Android that should help me narrow down the cause of the glitch. Since your phone is doing the same thing mine is, it's more-than-likely not due to an app, so it has to be either the OS or a hardware thing.
Maybe a downgrade to 8.0 will make it, this bug is so annoying
Eco0901 said:
Maybe a downgrade to 8.0 will make it, this bug is so annoying
Click to expand...
Click to collapse
It's possible that might work, but either way I still need to be able to root the thing and find a ROM made for the Verizon model. My phone has only been doing this for a couple weeks or so, but before that it would actually fully close certain apps (gsam Battery Monitor, RadioU, Taskbar, and some others). However, I more than less fixed that by setting the timers for those apps to 23 hrs.
How did you set the timers? That fixed the problem of minimizing the apps?
Eco0901 said:
How did you set the timers? That fixed the problem of minimizing the apps?
Click to expand...
Click to collapse
The reason why I tried setting timers on certain apps was because they were being killed automatically, this was before the 'phantom' home button thing. The following steps may/may not resolve your current issue, but you can try them if you'd like:
1. Go to Settings
2. Apps & notifications
3. Screen time
4. At the bottom, you'll see a few apps listed, and a an option to show all of your apps. Select 'Show all apps', then the app you want to set the timer for.
5. Next to each app you'll see a little hour glass. If it's empty, then there is currently not timer set. If you'd like to set a timer, tap the hour glass, then set your desired time.
Again, I did all this well before my phone started acting like I was hitting the home button in an effort to get it to stop closing my favorite apps. For the most part, it worked, but the automatic closing thing only started after the upgrade to Android 9. I did find a site where I could download a previous stock ROM, but without root it may/will re-update again. There's an app that let's you prevent updates, but the phone has to be rooted in order for the app to work. I can't really remember the name app right now, but I used to use it on my Note 4. I think there was also a way to do it through the command line in Windows (might've worked in Linux, too), or it might've been a combination of an app and the command line.
In any case, the root method I thought I'd found wasn't really all that instructive, and I need to make sure I can actually fully unlock the boot loader before attempting root. If I can't unlock it, then whatever root method I try won't stick. The auto home button thing, at least on my phone, seems to be random, though. Sometimes it'll be fairly soon after opening an app, other times the app will stay open for a good while before going back to the home screen.
Well, like I said, I have other 2 Moto Z2 Force but they are Sprint or whatever the carrier are. They don't have the phantom home button problem. But they are in Android 8. I actually don't have a problem on click the multitasking button to go back to the app but the problem is on the games and that stuff. So if I go back to Android 8 the system will update automatically to 9? I didn't know that, I thought that it was volunteer hahaha. Btw I don't even know how to downgrade since I'm not a moto user of all life. This is my first experience with a moto phone and it sucks. . Hahaha actually the home button problem happen.
Eco0901 said:
Well, like I said, I have other 2 Moto Z2 Force but they are Sprint or whatever the carrier are. They don't have the phantom home button problem. But they are in Android 8. I actually don't have a problem on click the multitasking button to go back to the app but the problem is on the games and that stuff. So if I go back to Android 8 the system will update automatically to 9? I didn't know that, I thought that it was volunteer hahaha. Btw I don't even know how to downgrade since I'm not a moto user of all life. This is my first experience with a moto phone and it sucks. . Hahaha actually the home button problem happen.
Click to expand...
Click to collapse
It may not immediately update the OS after a downgrade, but you would get a notice there's an update available, even on a rooted phone. Since root only removes the barriers that're usually there to keep the less knowledgeable from hurting their phones, you'd still get any update notices a non-rooted phone would usually get. There is an app called NoBloat Free, and with it there are two files you'd be able to block that'd keep your phone from updating when you don't want it to. I'm not sure if the app is still in the Play Store or not, but I did use it on my Note 4, and it worked pretty well.
On a side note, I've had Opera open on my phone for a while now, and so far it hasn't gone back to the home screen yet. As for the phone itself, Moto phones are pretty good phones, my Z2 Force is my fourth phone from Moto (the other three being the RAZOR smartphone, Bionic, and the original RAZOR, which I sometimes miss). For all we know, our issue could be caused by a software glitch, hence my desire to root and test a different ROM.
Do you know how to downgrade to 8.0? I'll try it, it's a good phone and I didn't pay so much por this, that's why I'm not that angry. I won't root the phone since the games I play would kick me from the game. So just for make me sure I understand, do you reestablished the phone with a computer or from the same phone?
will4958 said:
My concern is whether the root method I found is legit or not. The only reason why I want to attempt it is because the description mentions the specific model of my phone. All variants of the Z2 Force start with XT789-, but it's the number after the '-' you have to look for, and for Verizon users is '01'. Rooting the phone will let me install a different version of Android that should help me narrow down the cause of the glitch. Since your phone is doing the same thing mine is, it's more-than-likely not due to an app, so it has to be either the OS or a hardware thing.
Click to expand...
Click to collapse
My man, I found something, I think it's a Verizon app's problem, there is a post in Reddit with more people having this problem, one of them leading to the conclusion that two apps of Verizon update recently. I don't know if that work. Btw I leave the link to that post. https://www.reddit.com/r/Moto_Z/com..._source=amp&utm_medium=&utm_content=post_body
Eco0901 said:
My man, I found something, I think it's a Verizon app's problem, there is a post in Reddit with more people having this problem, one of them leading to the conclusion that two apps of Verizon update recently. I don't know if that work. Btw I leave the link to that post. https://www.reddit.com/r/Moto_Z/com..._source=amp&utm_medium=&utm_content=post_body
Click to expand...
Click to collapse
I think I may have finally given my phone the smack in the pants it needed to start behaving itself again. I followed the link you provided, and one of the comments suggested installing any updates for a couple Verizon apps and disabling them. Not sure if this would work on a non-Verizon phone or not, but I've had the XBox app open on my phone for over 20 minutes now, and so far it hasn't minimized yet. To be accurate, I even closed & reopened the app. The apps mentioned were Verizon App Manager & My Verizon Services. I was able to disable the first app, but not the second, and rebooted my phone after doing so.
If your phone isn't from Verizon, there may be a similar pair of apps you could try disabling, though I'd probably look it up first to be on the safe side.
Update: It's been almost two hours now and the app still hasn't closed. Now, to get the screen protector residue off my phone.