Related
I have a weird bug/problem. On my nexus 5, whenever i hangup a phone call the end button and screen do not go away. The back button does not work but the home and recent apps does. Any help would be appreciated. I can upload a video of the problem. MODS: sorry if this is the wrong area. please move if necessary.
thepoetlives89 said:
I have a weird bug/problem. On my nexus 5, whenever i hangup a phone call the end button and screen do not go away. The back button does not work but the home and recent apps does. Any help would be appreciated. I can upload a video of the problem. MODS: sorry if this is the wrong area. please move if necessary.
Click to expand...
Click to collapse
Having the same problem! really annoying!!! Was not how Nexus 4 was or any other phone I have used. There have been settings on some dialers of what to do after hanging up, like return to dialer, return to call log or home screen. None on this built apparently.
bjjere said:
Having the same problem! really annoying!!! Was not how Nexus 4 was or any other phone I have used. There have been settings on some dialers of what to do after hanging up, like return to dialer, return to call log or home screen. None on this built apparently.
Click to expand...
Click to collapse
I don't know what happened but mine seemed to either fix itself or was fixed when i erased play store app data.
I have that problem too (see attached photo). It's getting pretty annoying. Any ideas?
thepoetlives89 said:
I don't know what happened but mine seemed to either fix itself or was fixed when i erased play store app data.
Click to expand...
Click to collapse
Had the same issue. This fixed it. Thank you.
Sent from my Nexus 5 using Tapatalk
oldmanwinter said:
I have that problem too (see attached photo). It's getting pretty annoying. Any ideas?
Click to expand...
Click to collapse
Try wiping play store app data.
I tried wiping the just the general play store data before and it didn't fix the issue. Just wiped all play related data: magazine, books, etc and it solved the issue. Thanks
Sent from my Nexus 5 using xda app-developers app
My problem is eve weirder when I call someone it takes me to the homescreen and still makes the call but I can't access the dialer thing where you can hangup and stuff and when I get a call I can't answer it because it doesn't show up it just rings
Sent from my Nexus 5 using XDA Premium 4 mobile app
I have this screen issue too from time to time, exactly like the screenie above...button is just black.
I will try this fix...
Sent from my Nexus 5 using XDA Premium 4 mobile app
3's&7's said:
I have this screen issue too from time to time, exactly like the screenie above...button is just black.
I will try this fix...
Sent from my Nexus 5 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Mine helped clearing the Google Dialer data.
randomnoob83 said:
My problem is eve weirder when I call someone it takes me to the homescreen and still makes the call but I can't access the dialer thing where you can hangup and stuff and when I get a call I can't answer it because it doesn't show up it just rings
Sent from my Nexus 5 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
i had the exact same issue, or more precisely :
I receive or pass a call. then, instead of going to the "in call" screen with the big red "hang up" button, i'm back to the home screen...
now this can happen, if i press the home button, but i don't. And if that was that, then first i would have the small "phone" logo in the upper left notification telling me i'm currently in call, and the "in call" screen would be accessible from the task manager, however the task manager displays absolutely nothing.... just like i wasn't making any call at all, except i can hear the person on the other side in my speaker.
Then i click on the big blue phone logo to get to the dialer screen, but i then get a screen which i never had before, with a black transparent background, proposing me to either use the default keyboard (if i click it i get the keyboard), either to "return to current call", and when i click it, i'm back to the homescreen... so the only way to hang up is to shut the phone down...
it's happened to me twice yesterday, but never before....
PS: just so we might find a common app that would cause the issue, i have installed on my N5 these apps :
dashclock
file manager
prochain bus
ridiculous fishing
sygic
today calendar
vlc
and thats all. Any of you have some apps in common ?
I also had the same issue during the first week or so...but with tym and aftr update the issue vanished!! Since 2014 i nvr faced this issue again!!
Sent from my Nexus 5 using Tapatalk
Different Dialer problem
Hi,
I am rooted running beanstalk. But before flashing had stock rom then Purity.
This problem happened after flashing Purity ROM.
When I make or receive a call, my screen goes blank and I cannot do,anything to wake the phone, unless the other party ends the call and then the screen may wake up if I touch the screen?!
Anyone else, please help.
bagou01 said:
i had the exact same issue, or more precisely :
I receive or pass a call. then, instead of going to the "in call" screen with the big red "hang up" button, i'm back to the home screen...
now this can happen, if i press the home button, but i don't. And if that was that, then first i would have the small "phone" logo in the upper left notification telling me i'm currently in call, and the "in call" screen would be accessible from the task manager, however the task manager displays absolutely nothing.... just like i wasn't making any call at all, except i can hear the person on the other side in my speaker.
Then i click on the big blue phone logo to get to the dialer screen, but i then get a screen which i never had before, with a black transparent background, proposing me to either use the default keyboard (if i click it i get the keyboard), either to "return to current call", and when i click it, i'm back to the homescreen... so the only way to hang up is to shut the phone down...
it's happened to me twice yesterday, but never before....
PS: just so we might find a common app that would cause the issue, i have installed on my N5 these apps :
dashclock
file manager
prochain bus
ridiculous fishing
sygic
today calendar
vlc
and thats all. Any of you have some apps in common ?
Click to expand...
Click to collapse
Exact same issue here. No app in common... Did you manage to fix it ?
Fixed mine by turning off developer options and then rebooting
Hello,
Anybody see this issue? My Google Now is not listening to the hot word anymore. See the listening icon is paused. A reboot or cache clear of Google Search app resolves it but it is really annoying. Trying to figure out what's causing the pause.
Here is the screenshot of my home screen. Notice the listening icon looks different.
Thanks.
danlo said:
Hello,
Anybody see this issue? My Google Now is not listening to the hot word anymore. See the listening icon is paused. A reboot or cache clear of Google Search app resolves it but it is really annoying. Trying to figure out what's causing the pause.
Here is the screenshot of my home screen. Notice the listening icon looks different.
Thanks.
Click to expand...
Click to collapse
Were you using headphones that day? I've seen this issue, and I think it's an audio issue (software). When I had this issue, the speakers didn't work either.
Sent from my Nexus 5 using Tapatalk
I was using my Bluetooth headset but I've been using this pair since day 1. This just started happening yesterday.
Workaround I mentioned in another thread this morning:
With any music or sound playing apps paused, tap the Google logo (not the mic icon) in the Google search tool. Once in the search screen, just swipe back out to the home screen. The mic icon should now be "filled in" instead of hollow, and should respond to "Ok Google".
Sent from my Nexus 5 using Tapatalk
TJCacher said:
Workaround I mentioned in another thread this morning:
With any music or sound playing apps paused, tap the Google logo (not the mic icon) in the Google search tool. Once in the search screen, just swipe back out to the home screen. The mic icon should now be "filled in" instead of hollow, and should respond to "Ok Google".
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Thanks for the tip!
man sadly nothing in this thread is working for me
I toggled the hotword option, toggled it with reboots in between, cleared Google Search data and cache, removed device administrators, toggled english styles, toggled wifi... I've done everything I can think of, and it's still not working.
I've scoured the web and nothing. It was working when I first got the phone, but today I noticed it had stopped. Ugh.
bengrulz said:
man sadly nothing in this thread is working for me
I toggled the hotword option, toggled it with reboots in between, cleared Google Search data and cache, removed device administrators, toggled english styles, toggled wifi... I've done everything I can think of, and it's still not working.
I've scoured the web and nothing. It was working when I first got the phone, but today I noticed it had stopped. Ugh.
Click to expand...
Click to collapse
Same with me. I'm not sure why nobody else is having this issue. I've tried everything to get it back to always listening, and it doesn't work. I have to hit the microphone. The only "workaround" I've found is to swipe up from the center bottom of the lock screen, which takes me to the google now page and it's listening for "ok google". I can't get the widget on the left pane back though.
bengrulz said:
man sadly nothing in this thread is working for me
I toggled the hotword option, toggled it with reboots in between, cleared Google Search data and cache, removed device administrators, toggled english styles, toggled wifi... I've done everything I can think of, and it's still not working.
I've scoured the web and nothing. It was working when I first got the phone, but today I noticed it had stopped. Ugh.
Click to expand...
Click to collapse
Ok, I've done a lot more testing with this issue, and have come up with the following working theory. If any of you notice behavior inconsistent with this theory, post it up here. Maybe we can pin the exact cause down enough to let Google know the exact parameters of this glitch.
Here's my theory:
I'm going to call the situation where the Google search mic icon is hollow and the search won't respond to "Ok Google" the HM (hollow mic) mode, and the normal, full mic icon, indicating the search will properly respond to "Ok Google" the FM (full mic) mode. (HM=hollow mic is not listening, FM=full mic is listening)
The problem seems to be that the control is designed to enter HM mode whenever the system is aware that the device is playing sound and to return to FM mode when the system detects that sound has been paused or stopped, but that sometimes the system gets "stuck" in HM mode and remains there even when sound has been paused or stopped. Furthermore, in some cases HM mode is not activated when sound is started,
My theory is that the HM/FM switching only occurs correctly when the sound app itself is used to *directly* start and stop sound. If you use an alternate method to start and/or stop sound (like a linked set of media controls in the notification shade, or a set of media controls in a linked home-screen widget), then there is a near certainty that either HM mode will not be activated when sound starts and/or FM mode will not be reset when sound stops.
When the system becomes "stuck" in HM mode, even when no sound is playing, I have found two ways to reliably get it to reset to FM mode:
Method 1:
1) Stop any sound being played by the device via any means (directly from a sound app, or indirectly from a set of media controls in the notification shade or a home-screen widget)
2) Tap the word "Google" in the Google search bar at the top of any home screen
3) Once inside the search screen, cancel it by swiping right-to-left once or twice to return to the home screen.
Method 2
1) Go into the sound app which either is or was being used to play sound
2) Start the app playing sound from directly in the app itself
3) Stop or pause the sound from directly in the app itself
On my device, using Google Play as the sound app, I have had 100% success, with both of these methods, at getting HM mode "unstuck" and getting the device back into FM mode.
I can also reliably produce the "stuck" HM mode by starting music from within a music app, but stopping or pausing it from outside the app by using a widget.
On my device, if starting from FM mode, starting music playing from a widget instead of from within a music app will result in the device never entering HM mode in the first place.
If others can verify this, I think we may be able to say with some confidence that the problem is that the method being used to detect when sound starts and stops is not properly looking for sound to be started or stopped using an externally-linked set of media controls (as from a notification shade or widget), and that it only reliably works when sound is started or stopped *directly from inside the app itself, using app's built-in media controls*.
Thanks for any additional data anyone is willing to provide to prove or disprove this theory.
I've had the same issue, but I can add that this is happening with games as well. Specifically, asphalt 8 causes this problem. Obviously, when I'm switching between apps, I wouldn't want to kill an ongoing game or song just to make the hotword work. The HC issue is annoying and I hope there's a fix to always keep it live no matter which apps are in the background...
shaklee3 said:
Same with me. I'm not sure why nobody else is having this issue. I've tried everything to get it back to always listening, and it doesn't work. I have to hit the microphone. The only "workaround" I've found is to swipe up from the center bottom of the lock screen, which takes me to the google now page and it's listening for "ok google". I can't get the widget on the left pane back though.
Click to expand...
Click to collapse
bengrulz said:
man sadly nothing in this thread is working for me
I toggled the hotword option, toggled it with reboots in between, cleared Google Search data and cache, removed device administrators, toggled english styles, toggled wifi... I've done everything I can think of, and it's still not working.
I've scoured the web and nothing. It was working when I first got the phone, but today I noticed it had stopped. Ugh.
Click to expand...
Click to collapse
My hotword detection also suddenly doesn't work. I've toggled the option in google now settings, rebooted, cleared cache, turned off google music... nothing turns it back on.
TJCacher said:
Ok, I've done a lot more testing with this issue, and have come up with the following working theory. If any of you notice behavior inconsistent with this theory, post it up here. Maybe we can pin the exact cause down enough to let Google know the exact parameters of this glitch.
Here's my theory:
I'm going to call the situation where the Google search mic icon is hollow and the search won't respond to "Ok Google" the HM (hollow mic) mode, and the normal, full mic icon, indicating the search will properly respond to "Ok Google" the FM (full mic) mode. (HM=hollow mic is not listening, FM=full mic is listening)
The problem seems to be that the control is designed to enter HM mode whenever the system is aware that the device is playing sound and to return to FM mode when the system detects that sound has been paused or stopped, but that sometimes the system gets "stuck" in HM mode and remains there even when sound has been paused or stopped. Furthermore, in some cases HM mode is not activated when sound is started,
My theory is that the HM/FM switching only occurs correctly when the sound app itself is used to *directly* start and stop sound. If you use an alternate method to start and/or stop sound (like a linked set of media controls in the notification shade, or a set of media controls in a linked home-screen widget), then there is a near certainty that either HM mode will not be activated when sound starts and/or FM mode will not be reset when sound stops.
When the system becomes "stuck" in HM mode, even when no sound is playing, I have found two ways to reliably get it to reset to FM mode:
Method 1:
1) Stop any sound being played by the device via any means (directly from a sound app, or indirectly from a set of media controls in the notification shade or a home-screen widget)
2) Tap the word "Google" in the Google search bar at the top of any home screen
3) Once inside the search screen, cancel it by swiping right-to-left once or twice to return to the home screen.
Method 2
1) Go into the sound app which either is or was being used to play sound
2) Start the app playing sound from directly in the app itself
3) Stop or pause the sound from directly in the app itself
On my device, using Google Play as the sound app, I have had 100% success, with both of these methods, at getting HM mode "unstuck" and getting the device back into FM mode.
I can also reliably produce the "stuck" HM mode by starting music from within a music app, but stopping or pausing it from outside the app by using a widget.
On my device, if starting from FM mode, starting music playing from a widget instead of from within a music app will result in the device never entering HM mode in the first place.
If others can verify this, I think we may be able to say with some confidence that the problem is that the method being used to detect when sound starts and stops is not properly looking for sound to be started or stopped using an externally-linked set of media controls (as from a notification shade or widget), and that it only reliably works when sound is started or stopped *directly from inside the app itself, using app's built-in media controls*.
Thanks for any additional data anyone is willing to provide to prove or disprove this theory.
Click to expand...
Click to collapse
didn't help me. can't figure out what is going on. so frustrating.
---------- Post added at 11:12 PM ---------- Previous post was at 10:26 PM ----------
For me, turning off Push Bullet Notification Listener in Accessibility in Settings made Google Now hot word work again.
gaetawoo said:
For me, turning off Push Bullet Notification Listener in Accessibility in Settings made Google Now hot word work again.
Click to expand...
Click to collapse
I'm replying to clarify this info for others who, like me, may not have been aware that Push Bullet is a third-party app that is installed from the Google Play store.
After reading through the app's description and reviews on the Play Store site, it sounds like a very useful app which has recently added a new feature which mirrors your notifications to a PC via a PC-side browser add-on.
According to a number of the user reviews on the Play Store, which have been confirmed by the app's author, this feature is causing problems with the "always listening" feature of OK Google.
Sounds like they're actively working on a solution for the conflict.
Thanks for posting this - it may very well be the reason some others have had no luck getting the listening feature to work.
Sent from my Nexus 5 using Tapatalk
TJCacher said:
I'm replying to clarify this info for others who, like me, may not have been aware that Push Bullet is a third-party app that is installed from the Google Play store.
After reading through the app's description and reviews on the Play Store site, it sounds like a very useful app which has recently added a new feature which mirrors your notifications to a PC via a PC-side browser add-on.
According to a number of the user reviews on the Play Store, which have been confirmed by the app's author, this feature is causing problems with the "always listening" feature of OK Google.
Sounds like they're actively working on a solution for the conflict.
Thanks for posting this - it may very well be the reason some others have had no luck getting the listening feature to work.
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Yes I've talked to them, they know about it and are working on it, but that say it could be an OS issue.. that are trying to figure it out.
This happens to me at least couple times a day. Either Wi-Fi disconnect or a OK Google three I n a row consecutive search. Solution: kill the g search app it will automatically restart and you'll be gtg
Pebble whatsapp notifier causes this same problem. Unchecked it in accessibility and viola! Always listening again..
Easiest solution I found on the internet was to go into settings and install the US English language pack. Even though it says it is installed, reinstall it and set it as the default. After a reboot, it worked perfectly.
phandroid.com/2013/11/14/how-to-install-google-experience-launcher-with-ok-google-command/
Once in Google Now, scroll all the way to the bottom and press the 3 dot menu to select Settings. From there, select “voice” > “offline speech recognition” (manage downloaded languages). Now, we’re going to work our way from the right tab, all the way to the left.
Select the Auto-Update tab from the top and choose one of the auto-update options (we recommend leaving it on “over WiFi-only”). After that, scoot over to the All tab and find English (US). You’ll notice it already says “pre-installed”. Don’t listen to it. Select English (US) anyway. From there, jump to the Installed tab and press “English (US)” where you’ll be asked to download the latest version (version 28 at the time of writing). Hit “Download” and the updated version will be downloaded and installed.
TJCacher said:
Ok, I've done a lot more testing with this issue, and have come up with the following working theory. If any of you notice behavior inconsistent with this theory, post it up here. Maybe we can pin the exact cause down enough to let Google know the exact parameters of this glitch.
Here's my theory:
I'm going to call the situation where the Google search mic icon is hollow and the search won't respond to "Ok Google" the HM (hollow mic) mode, and the normal, full mic icon, indicating the search will properly respond to "Ok Google" the FM (full mic) mode. (HM=hollow mic is not listening, FM=full mic is listening)
The problem seems to be that the control is designed to enter HM mode whenever the system is aware that the device is playing sound and to return to FM mode when the system detects that sound has been paused or stopped, but that sometimes the system gets "stuck" in HM mode and remains there even when sound has been paused or stopped. Furthermore, in some cases HM mode is not activated when sound is started,
My theory is that the HM/FM switching only occurs correctly when the sound app itself is used to *directly* start and stop sound. If you use an alternate method to start and/or stop sound (like a linked set of media controls in the notification shade, or a set of media controls in a linked home-screen widget), then there is a near certainty that either HM mode will not be activated when sound starts and/or FM mode will not be reset when sound stops.
When the system becomes "stuck" in HM mode, even when no sound is playing, I have found two ways to reliably get it to reset to FM mode:
Method 1:
1) Stop any sound being played by the device via any means (directly from a sound app, or indirectly from a set of media controls in the notification shade or a home-screen widget)
2) Tap the word "Google" in the Google search bar at the top of any home screen
3) Once inside the search screen, cancel it by swiping right-to-left once or twice to return to the home screen.
Method 2
1) Go into the sound app which either is or was being used to play sound
2) Start the app playing sound from directly in the app itself
3) Stop or pause the sound from directly in the app itself
On my device, using Google Play as the sound app, I have had 100% success, with both of these methods, at getting HM mode "unstuck" and getting the device back into FM mode.
I can also reliably produce the "stuck" HM mode by starting music from within a music app, but stopping or pausing it from outside the app by using a widget.
On my device, if starting from FM mode, starting music playing from a widget instead of from within a music app will result in the device never entering HM mode in the first place.
If others can verify this, I think we may be able to say with some confidence that the problem is that the method being used to detect when sound starts and stops is not properly looking for sound to be started or stopped using an externally-linked set of media controls (as from a notification shade or widget), and that it only reliably works when sound is started or stopped *directly from inside the app itself, using app's built-in media controls*.
Thanks for any additional data anyone is willing to provide to prove or disprove this theory.
Click to expand...
Click to collapse
I have the same issue and none of that work for me, it gets stuck with real racing, i force the stop once and it started to work again but minutes later it was hallow again, please help
shaklee3 said:
Same with me. I'm not sure why nobody else is having this issue. I've tried everything to get it back to always listening, and it doesn't work. I have to hit the microphone. The only "workaround" I've found is to swipe up from the center bottom of the lock screen, which takes me to the google now page and it's listening for "ok google". I can't get the widget on the left pane back though.
Click to expand...
Click to collapse
Are you on stock? I thought this was a result of the new launcher in today's version of cm.
Sent from my Nexus 5 using XDA Premium 4 mobile app
xdapro said:
Easiest solution I found on the internet was to go into settings and install the US English language pack. Even though it says it is installed, reinstall it and set it as the default. After a reboot, it worked perfectly.
phandroid.com/2013/11/14/how-to-install-google-experience-launcher-with-ok-google-command/
Once in Google Now, scroll all the way to the bottom and press the 3 dot menu to select Settings. From there, select “voice” > “offline speech recognition” (manage downloaded languages). Now, we’re going to work our way from the right tab, all the way to the left.
Select the Auto-Update tab from the top and choose one of the auto-update options (we recommend leaving it on “over WiFi-only”). After that, scoot over to the All tab and find English (US). You’ll notice it already says “pre-installed”. Don’t listen to it. Select English (US) anyway. From there, jump to the Installed tab and press “English (US)” where you’ll be asked to download the latest version (version 28 at the time of writing). Hit “Download” and the updated version will be downloaded and installed.
Click to expand...
Click to collapse
I love you dude or dudette I was going balled trying to figure this out, thanks a lot!
I found out that the hot word detection only works on the default launcher. If I add the google search widget on apex launcher, I get the search bar with a hollow mic, and hot word detection does not work.
If I use default launcher I got the full mic and hot word detection works.
Sent from my Nexus 5 using xda app-developers app
So I'm just on the basic stock rom rooted on the sprint version. I've noticed every 30 sec when im doing something on it, it will freeze and then respond 3 seconds later, as well as songs on blue tooth lag as well. Any suggestions. Oh and my ok google available everywhere is greyed out and im on English and i believe svoice is enabled. My favorites wont display on the edge bar either when i add them and press done.
cbwhat said:
So I'm just on the basic stock rom rooted on the sprint version. I've noticed every 30 sec when im doing something on it, it will freeze and then respond 3 seconds later, as well as songs on blue tooth lag as well. Any suggestions. Oh and my ok google available everywhere is greyed out and im on English and i believe svoice is enabled. My favorites wont display on the edge bar either when i add them and press done.
Click to expand...
Click to collapse
Have you installed xposed framework & wanam?
unFKNreal said:
Have you installed xposed framework & wanam?
Click to expand...
Click to collapse
xposed yes
I had the same problem, as after i installed xposed S Health stopped working.
This suggestion that's posted on forums everywhere should fix the problem:
Uninstall Xposed framework
Open build.prop in with ES File Explorer or something similar
Find: ro.securestorage.support=true & change to false
Reinstall xposed framework
If S Health isnt working clear app data for S-Health and HealthService
Restart your phone
Source: https://www.google.co.uk/webhp?sour..._th=1&ie=UTF-8#q=xposed+framework+lag&spell=1
I am having real lag issues sending and receiving text messages, some will send but will hang in sending for up to 10 minutes or so, others will simply say failed after a while... I don't have Xposed installed, but I've done the build prop edit just in case it would help... still having the lag in my messages.... anyone with an idea please offer your assistance. Most of my communication would be via text, it almost defeats the purpose of my phone not being able to send or know if I'm receiving a text...
Sad face
Edit:
Just did another reboot after my build prop edit and it appears that did the trick, however I'll wait another day to conform.
Smiles
Sent from my SM-N915P using Tapatalk 2
Mine also randomly freezes while browsing. I believe it's ram related as its almost maxed out straight out the box (thanks Samsung!). And what do u mean by Google now being greyed out? Like won't record when you talk? I also have that issue if that's what you mean. It's bluetooth related for me, as soon as I disconnect my Gear S it works fine.
Sent from my SPH-L900 using XDA Free mobile app
RayTrue04 said:
Mine also randomly freezes while browsing. I believe it's ram related as its almost maxed out straight out the box (thanks Samsung!). And what do u mean by Google now being greyed out? Like won't record when you talk? I also have that issue if that's what you mean. It's bluetooth related for me, as soon as I disconnect my Gear S it works fine.
Sent from my SPH-L900 using XDA Free mobile app
Click to expand...
Click to collapse
Is your device rooted? Try installing Seeder from the android store: https://play.google.com/store/apps/details?id=com.lcis.seeder&hl=en_GB
It costs a couple of dollars but your should definitely see a massive improvement in performance
In terms of high ram usage, this can actually be a good thing as android manages the ram differently. By having applications loaded into the ram allows for instant access & increased performance. Have a read of the following URL or search for some articles on google about this topic, makes interesting reading.
http://www.makeuseof.com/tag/ram-boosters-task-killers-bad-android/
Not rooted
Sent from my SPH-L900 using XDA Free mobile app
Is there any alternatives ? I've been trying to find something that allows me to game without getting interrupted by notifications and phone calls.
Does the new 5.1.1 update includes interruption mode?
austinjklim said:
Is there any alternatives ? I've been trying to find something that allows me to game without getting interrupted by notifications and phone calls.
Does the new 5.1.1 update includes interruption mode?
Click to expand...
Click to collapse
I stumbled upon Omni Swipe earlier today. I haven't actually used the Samsung version but I'm guessing that it's every bit as piss poor as the rest of their bloatware.
TBH it's turning out to be just the right side of just turning the ringer off. Alerts for banned apps still one though, buy in the form of tiny red dots in the bottom corner. Definitely a good one for gamers and for getting actual work done on the phone as well.
Sent from my SM-G920F using Tapatalk
It's just a normal launcher. And it doesn't fix my problem.......
I reckon you're doing it wrong. I'm using it like an insecure Knox so that I don't get distracted when I am working.
It's also got some nice simple tools like a RAM cleaner and torch built in.
Surely anything more would involve muting phone calls and notifications?
Sent from my SM-G920F using Tapatalk
---------- Post added at 05:55 PM ---------- Previous post was at 05:35 PM ----------
Also a built in NSFW photograph filter that's enabled by default and easy to override. And dice...
Sent from my SM-G920F using Tapatalk
Could you give instructions? I kinda dont understand you
I just set it up normally. Think you're right and it is just a launcher. I'd you turn offence notification sounds and include apps for notifications the red dot at the bottom notifies you.
Why don't you just turn off the sounds?
Sent from my SM-G920F using Tapatalk
Go to Settings-Applications -Applications Manager. Choose your conflicting app. Uncheck Show Notifications.
Once you've enabled Omni Swipe, the first time after that you open your game or whatever there's a pop-up at the bottom of the screen that offers to enable no interruption mode for that app.
Sent from my SM-G920F using Tapatalk
Hey these are just a few things that i have found that are not completely broken but annoying enough to talk about.
First one is on some apps I am getting double notifications. Not that there are 2 of the same notifications in the tray but i get 2 sound alerts and too vibrate alerts. Not every app is doing this though which leads me to believe it may be an app optimization issue. This also get translated to android wear btw.
Second is voice dictation in the Stock google keyboard. Sometimes it will fail and other times it will be fine. random issue so no really way to lock down the cause.
Third is camera sluggishness all around. Double tapping the power button is slower than it has been and in the app changing modes or viewing pictures is also a slight issue.
Anyone else have these issues?
Having the same issue with the voice dictation in Gboard. It turns on and shuts off immediately.
Sent from my Pixel using Tapatalk
jerflash said:
Hey these are just a few things that i have found that are not completely broken but annoying enough to talk about.
First one is on some apps I am getting double notifications. Not that there are 2 of the same notifications in the tray but i get 2 sound alerts and too vibrate alerts. Not every app is doing this though which leads me to believe it may be an app optimization issue. This also get translated to android wear btw.
Second is voice dictation in the Stock google keyboard. Sometimes it will fail and other times it will be fine. random issue so no really way to lock down the cause.
Third is camera sluggishness all around. Double tapping the power button is slower than it has been and in the app changing modes or viewing pictures is also a slight issue.
Anyone else have these issues?
Click to expand...
Click to collapse
I'm not seeing any of this
I used ./flash-all.sh to both slots with the -w intact
Sent from my Pixel using XDA-Developers Legacy app
piperx said:
I'm not seeing any of this
I used ./flash-all.sh to both slots with the -w intact
Sent from my Pixel using XDA-Developers Legacy app
Click to expand...
Click to collapse
I updated straight from the August 7.1.2 to August 8.0.0 oreo.
Thinking about doing a wipe but not at that point yet...
Sent from my Pixel using Tapatalk
Well, I never do ota's, always clean flash, it avoids future problems, up and running in 10 - 15 minutes, easy as pie. ?
Sent from my Pixel using XDA-Developers Legacy app
Sign up for GBoard beta. A new version released today. I've read that it resolves the issue.
---------- Post added at 19:31 ---------- Previous post was at 19:24 ----------
snovvman said:
Sign up for GBoard beta. A new version released today. I've read that it resolves the issue.
Click to expand...
Click to collapse
By the way, to sign up for beta, just go to Playstore, GBoard, scroll down, and tap the button.
I'm on Gboard beta and it works better. I have had no camera sluggishness and I flashed from O DP4. I've never had that double notification issue, what apps give you double notifications??
Sent from my Pixel using XDA Labs
Nick80835 said:
I'm on Gboard beta and it works better. I have had no camera sluggishness and I flashed from O DP4. I've never had that double notification issue, what apps give you double notifications??
Sent from my Pixel using XDA Labs
Click to expand...
Click to collapse
Twitter, Tapatalk and a few others. It is a strange thing but maybe I will wait until the September OTA to see what happens
Sent from my Pixel using Tapatalk
jerflash said:
First one is on some apps I am getting double notifications. Not that there are 2 of the same notifications in the tray but i get 2 sound alerts and too vibrate alerts. Not every app is doing this though which leads me to believe it may be an app optimization issue. This also get translated to android wear btw.
Click to expand...
Click to collapse
Have you tried 1) deleting cache, 2) toggling notification on/off in app, 3) clearing app data, and/or 4) uninstalling/reinstalling app? I would try these things in the stated order and observe the app behavior each time. Let us know how things turn out. Thanks.
jerflash said:
Twitter, Tapatalk and a few others.
Click to expand...
Click to collapse
snovvman said:
Have you tried 1) deleting cache, 2) toggling notification on/off in app, 3) clearing app data, and/or 4) uninstalling/reinstalling app? I would try these things in the stated order and observe the app behavior each time. Let us know how things turn out. Thanks.
Click to expand...
Click to collapse
I'm seeing the same on my Px and Px XL. Twitter and Slack. Clearly, the issue is app-specific. I tried all of the above but no joy. I have noticed that if the phone is not asleep, then there is no double sound. This may support your theory of app optimization. I will next try uninstalling/reinstalling the app to see if it makes a difference.
Hmm I may check this myself about the sleep issue
Sent from my Pixel using Tapatalk
I am having the same double notification issues as well. Same apps, Twitter particularly. I also used the OTA directly from the August 7.1.2. In addition my battery drain has been ridiculous today. I attempted to clear cache for all apps only to find that Google has removed that control from both the OS settings as well as via stock Recovery. That's right, you can no longer format the /cache partition. I wish they'd at least moved it into Developer options instead of removing it entirely.
I've manually cleared Google Play services data and cache for several apps showing high battery usage in the new battery settings. I've also limited background usage for apps like Facebook, Snapchat, etc.
I've uninstalled/reinstalled Twitter with the hope that the app will register under O [perhaps properly] and resolve the issue. No joy. I would seem that the app devs for Twitter, Slack, Tapatalk, etc. will need to fix the code to work under O. I recently saw another app updated with "Fixed Android O notifications" in the change log.
Relatedly, I have a custom ringtone set with Twitter, but the double tone I hear is the phone's default tone. I have not been able to get the custom-selected tone to play. Something else for Twitter to fix.
---------- Post added at 16:55 ---------- Previous post was at 16:51 ----------
tiberian said:
I am having the same double notification issues as well. Same apps, Twitter particularly. I also used the OTA directly from the August 7.1.2. In addition my battery drain has been ridiculous today. I attempted to clear cache for all apps only to find that Google has removed that control from both the OS settings as well as via stock Recovery. That's right, you can no longer format the /cache partition. I wish they'd at least moved it into Developer options instead of removing it entirely.
I've manually cleared Google Play services data and cache for several apps showing high battery usage in the new battery settings. I've also limited background usage for apps like Facebook, Snapchat, etc.
Click to expand...
Click to collapse
For wiping cache, if you are rooted or bootloader unlocked, you can use Flashfire or boot to TWRP.
My battery life on O (observed on two Pixels) is definitely not as good as N.
Weird. Battery life for me is incredibly better. I mean like.. Is there a reporting problem? How can this be so much better? Only one day in but I'm liking what I see.
Sent from my Pixel using XDA-Developers Legacy app
For the double notification sound, my workaround is to use Lightflow. I already had it for other purposes, so I set the native app [e.g., Twitter] for no sound and set LF to make the sound. All is good.
---------- Post added at 07:02 ---------- Previous post was at 07:01 ----------
bobby janow said:
Weird. Battery life for me is incredibly better. I mean like.. Is there a reporting problem?[/URL]
Click to expand...
Click to collapse
What do you mean by "reporting problem"?
snovvman said:
For the double notification sound, my workaround is to use Lightflow. I already had it for other purposes, so I set the native app [e.g., Twitter] for no sound and set LF to make the sound. All is good.
---------- Post added at 07:02 ---------- Previous post was at 07:01 ----------
What do you mean by "reporting problem"?
Click to expand...
Click to collapse
I meant is the battery indicator reporting it wrong. I was being facetious but I have not noticed any unusual battery drain. On N when I used Strava and gps for 3 hours or so I'd end up with about 55% left and then plug in for a quick charge. On O I wound up with 67% left which was pretty good. After a few days I think there are some things that are better but overall about the same as N.
I've had it today where the screen on time in the battery stats is stuck. So it's been reading 1hr 15min screen on time regardless of how much I use it... Something is a bit off with battery reporting it seems
Regarding the double sound, this is what I have discovered:
1) Go to Twitter app and set the notification for no sound
2) Go to settings/apps/Twitter, select notifications. You will see a bunch of granular notification settings. Once I made the desired setting there, no more double sounds and the tone is what I desired.
piperx said:
Well, I never do ota's, always clean flash, it avoids future problems, up and running in 10 - 15 minutes, easy as pie.
Click to expand...
Click to collapse
If you do not mind sharing, how you restore all your apps data and phone settings in 10-15 mins?
I have had several issues with the final O release. I updated OTA straight from beta and even factory reset without restoring data and apps.
Definitely having the Gboard microphone issue.
Was also having a lot of wifi connectivity issues. The phone would randomly not connect to several wifi networks and started dropping wifi once connected alot.
Battery life is also atrocious especially when navigating. I used maps for 20 minutes with the screen off and had nearly a 20% drain.
I contacted project fi and received a replacement device which I'm going to keep at 7.1.2 for the time being.
Incidentally the beta worked perfectly nearly for months. All this started after the final OTA to the production release.