Related
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
I'm noticing that during many of my calls, I apparently hit the HOLD button accidentally with my cheek. My proximity sensor seems to be working fine, and the screen does turn off appropriately when I hold the phone against my face. I'm assuming that at certain angles enough light gets through to the sensor to turn the screen on, and I accidentally hit the button in the corner. Anyone else have this issue? Is there any way to circumvent this? Thanks
Unfortunately i can't help but i am getting the same issue
Sent from my SM-G930F using Tapatalk
I tried applying different dialer apps and they only serve to change the dialer/contact screens, but the default calling screen containing the HOLD button remains unchanged. I found that using Skype as the default dialer fixes this issue since it uses its own dialing/calling screens, but obviously it's not practical to just rely on Skype. So the problem still remains unresolved.
As an update, someone on Reddit posted a download link to the Google dialer app here at: http://forum.xda-developers.com/galaxy-s6/themes-apps/app-google-dialer-t3323432
This installs a new dialer, which actually provides a new calling screen as well, fixing the main issue. The default dialer is better in my opinion since it opens up the dial pad immediately while this one doesn't, but this is a good option at this point
gomulkaaa said:
I'm noticing that during many of my calls, I apparently hit the HOLD button accidentally with my cheek. My proximity sensor seems to be working fine, and the screen does turn off appropriately when I hold the phone against my face. I'm assuming that at certain angles enough light gets through to the sensor to turn the screen on, and I accidentally hit the button in the corner. Anyone else have this issue? Is there any way to circumvent this? Thanks
Click to expand...
Click to collapse
even worst than calls is when you press it while watching youtube vids, i wish there was a lock of some sort cuz the music stops paying all the sudden
It's embarrassing when I put my clients on hold and don't realise until they don't respond to me. The cheek hold doesn't result in any audible sound so you can be talking for 20 seconds with the other end on hold. I love the S7 edge but I'm contemplating sending it back. I'll try the Google dialer mentioned above first though
Same issue here. I talk on the phone almost 2 hours a day and this is happening at least 1-2 times in every call! Checked my proximity sensor and it's working as it should.
Any workarounds? Maybe someone can edit the phone.apk and remove this stupid button or disable it? I am against rooting but I will definitely root my phone if there's a fix for this.
Damn, I suffer exactly the same issue! Found this googling for ideas...
Very old thread, but I just wanted to give a suggestion to others with the same issue. I really love the Google Phone dialer app, which actually replaces the calling screen during calls with this app's own screen, so you no longer have the Hold button at such an unfortunate location. If you do choose Google's app, I recommend this specific version: http://www.apkmirror.com/apk/google-inc/google-phone/google-phone-2-05-07_rc4-release/google-phone-2-05-07_rc4-android-apk-download/
The caller-ID function by Google actually works with this version, whereas the other .apk files floating around do not have this function working properly.
I'm having the same issue and I've installed the Google phone, however as soon as I place the call, the existing on-screen options pop up.
The option to disable the default phone app is greyed out in settings, so unsure on how to resolve.
robot1000 said:
I'm having the same issue and I've installed the Google phone, however as soon as I place the call, the existing on-screen options pop up.
The option to disable the default phone app is greyed out in settings, so unsure on how to resolve.
Click to expand...
Click to collapse
Finally searched for the answer to this today, after several accidental holds on work calls.
The solution above with Google Phone APK worked for me. I just went to SETTINGS - APPLICATIONS - DEFAULT APPLICATIONS and then under Calling App near the top, changed it from Contacts to Phone. . For some reason, I cannot open the phone app itself (gives an error message) but calls do use the phone app rather than Samsung stock dialer.
Turn off screen!! Most phones allow you to turn screen off without interrupting the call.
Same issue with a galaxy A5 2016
Can't understand why samsung doesn't fix it
Hello to the XDA Dev Community.
I'd like to start a threat with bugs after the Android Pie update on our devices.
1. Bug:
Camera App forgets the "volume down key" binding. Means, when double pressed in standby mode the cam is not started.
Solution: Sadly this works only temporary - start the cam app and exit or close. After that the above mentioned shortcut / quickstart works for a short time in standby mode.
2. Bug:
This one is still not repaired: when switching to black mode (to lower the battery consumption) one can not see in the apps overview which of the apps are deactivated - the letters are not visible. When you have the white menues, the term "deactivated" is quite readable. (This bug is existent from the beginning with Android 8 - i chatted on this topic with the customer service of Huawei last year but that guy had no blink of an idea, he sounded very unexperienced.)
My Device:
Unbranded, European version, yesterday received the update.
Wonder if anyone experienced same difficulties and perhaps if there are solutions to this.
Have a good day
Whenever you do a significant upgrade, do a factory reset. This cures most problems, people need to start doing this rather then moaning.
Quite a good idea - but I am long enough into the smartphone scene (since Windows CE and Mobile) to know well that "factory reset" is unfortunately not the magic solution to all problems as some would like it to be...
Of course factory reset is done. Problems are still there, and to be honest - we would have not awaited it as a solution to both bugs i mentioned above a priori, would we?
Well besides I recognized another bug or feature(?)
3. Bug (or feature?):
The native mail app no more shows contacts pictures left to the associated mails.
Does someone know if this is somehow configureable?
Thx in advance
Hi,
found next bug.
4. Bug:
Fast double tapping the "square button" works inconsistently.... It should switch between the two last apps in the tasklist..... May be it has to do with a little time delay / time lag in reaction of EMUI9/Pie... I have the slight feeling that the OS is not that fluent as before (under Android 8)
I hope that is it....
That AI thing in the left most corner in the camera APP is not working, it is the same button as the one you see next to the search bar when you swipe down for searching. I think it used to be some kind for scanner or products? Now the button just flicks and does nothing.
ppcppcppc said:
Hi,
found next bug.
4. Bug:
Fast double tapping the "square button" works inconsistently.... It should switch between the two last apps in the tasklist..... May be it has to do with a little time delay / time lag in reaction of EMUI9/Pie... I have the slight feeling that the OS is not that fluent as before (under Android 8)
I hope that is it....
Click to expand...
Click to collapse
Put High performance... I don't know where (probably battery settings?) As I haven't received yet OTA but seems that with that setting the double tap on square against slopes to switch between apps fluently
kotidoti said:
That AI thing in the left most corner in the camera APP is not working, it is the same button as the one you see next to the search bar when you swipe down for searching. I think it used to be some kind for scanner or products? Now the button just flicks and does nothing.
Click to expand...
Click to collapse
Working on my device, I had to confirm the consent before... Maybe u clicked it into the background?
Update:
I deactivated the corresponding Huawei app (HiVision), now it fully disappeared in the cam app and on the lock screen (formerly found at the bottom when you swiped from down to up... The list where the flashlight, calculator and so on appear)
Hey there,
Have you tried to go to battery optimisation (go to settings, hit the search bar on top and start writing "optim" and the first one), then search for "camera" and disable battery optimisation. It solved the problem for me.
I've found that the Pie is more aggresive overall with killing the background apps. I've had to add way more applications (than on droid 8) to the "disable battery optimizations" and to "app launch" (in settings, battery, app launch -> set applications that you want to survive on the background to "manage manually")
ppcppcppc said:
Hello to the XDA Dev Community.
I'd like to start a threat with bugs after the Android Pie update on our devices.
1. Bug:
Camera App forgets the "volume down key" binding. Means, when double pressed in standby mode the cam is not started.
Solution: Sadly this works only temporary - start the cam app and exit or close. After that the above mentioned shortcut / quickstart works for a short time in standby mode.
2. Bug:
This one is still not repaired: when switching to black mode (to lower the battery consumption) one can not see in the apps overview which of the apps are deactivated - the letters are not visible. When you have the white menues, the term "deactivated" is quite readable. (This bug is existent from the beginning with Android 8 - i chatted on this topic with the customer service of Huawei last year but that guy had no blink of an idea, he sounded very unexperienced.)
My Device:
Unbranded, European version, yesterday received the update.
Wonder if anyone experienced same difficulties and perhaps if there are solutions to this.
Have a good day
Click to expand...
Click to collapse
jcalderonv74 said:
Put High performance... I don't know where (probably battery settings?) As I haven't received yet OTA but seems that with that setting the double tap on square against slopes to switch between apps fluently
Click to expand...
Click to collapse
Thanks, will try your idea!
OTA Update: Against all info - the update was found by manual search in the standard system settings. As it was found I parallely checked HiCare App - NO updates were found, it was a joke!
So maybe also check this way, do not trust HiCare alone.
Update:
Found and activated the performance mode (as you said - battery settings). Sadly no change in performance of the app-switching.
Ereniemis said:
Hey there,
Have you tried to go to battery optimisation (go to settings, hit the search bar on top and start writing "optim" and the first one), then search for "camera" and disable battery optimisation. It solved the problem for me.
I've found that the Pie is more aggresive overall with killing the background apps. I've had to add way more applications (than on droid 8) to the "disable battery optimizations" and to "app launch" (in settings, battery, app launch -> set applications that you want to survive on the background to "manage manually")
Click to expand...
Click to collapse
You made my day, thx!
Disabling the battery optimization for the cam app is the solution. It works even after restart of the device without starting the cam app before!
Thx again!
jcalderonv74 said:
Put High performance... I don't know where (probably battery settings?) As I haven't received yet OTA but seems that with that setting the double tap on square against slopes to switch between apps fluently
Click to expand...
Click to collapse
Hi,
It helps a bit, but still inconsistently working, even after restart of the device. I also tried to put EMUI into the AppAssistant app to enforce it, but the app is not selectable (guess it should be HiStart, EMUI or something like that)...
Only solution atm is to SLOWLY double-tapping the square button.
ppcppcppc said:
Working on my device, I had to confirm the consent before... Maybe u clicked it into the background?
Update:
I deactivated the corresponding Huawei app (HiVision), now it fully disappeared in the cam app and on the lock screen (formerly found at the bottom when you swiped from down to up... The list where the flashlight, calculator and so on appear)
Click to expand...
Click to collapse
Update on this issue, I tried to clear data and cache which brought me back to give consent again and all but it still didn't work. What I did was disable it, which tuned it into factory default and then enabled it again and wolah, it works again. Thanks for informing me about the app name btw, would have been impossible without it. HiVision.
Calendar invites for office365 meetings cannot properly be accepted on the device. it sends the originator a 'not supported format.ics' file - rather than actually accepting the meeting.
Pretty stupid tbf. I'll look to move off the standard mail client i reckon
My P20 Pro (C782) finally prompted me to updated to Pie today, but having done so I'm experiencing choppy / clipping / stuttering audio when connected to my Sony WH-1000XM3's (using LDAC codec). This wasn't happening on Oreo at all.
I've done a factory reset, but the issue persists. Happens throughout whatever's playing (Spotify, Tidal, PocketCasts, YouTube) and is especially noticeable when pressing the power button to activate the screen.
Any ideas?
Anyone else having problems with the volume rocker?
I can't slide the volume to the left to get multiple profiles. Isn't it possible with the pie update?
zizzyboi said:
Anyone else having problems with the volume rocker?
I can't slide the volume to the left to get multiple profiles. Isn't it possible with the pie update?
Click to expand...
Click to collapse
Wonder if the volume rocker is not vertically orientated in Pie. Mine is working good, sliding down goes to silent. Above the slider is a button for vibration, sound and silence.
AWretchSavedByGrace said:
My P20 Pro (C782) finally prompted me to updated to Pie today, but having done so I'm experiencing choppy / clipping / stuttering audio when connected to my Sony WH-1000XM3's (using LDAC codec). This wasn't happening on Oreo at all.
I've done a factory reset, but the issue persists. Happens throughout whatever's playing (Spotify, Tidal, PocketCasts, YouTube) and is especially noticeable when pressing the power button to activate the screen.
Any ideas?
Click to expand...
Click to collapse
Hi, seems to be known and somehow a bug in Android 9 with Huawei components, let us hope for updates...
https://forum.xda-developers.com/huawei-p20-pro/help/bluetooth-issues-android-pie-clt-l29-t3889110
Naffets said:
Calendar invites for office365 meetings cannot properly be accepted on the device. it sends the originator a 'not supported format.ics' file - rather than actually accepting the meeting.
Pretty stupid tbf. I'll look to move off the standard mail client i reckon
Click to expand...
Click to collapse
Sounds to be a limitation by Huawei software...
I also recognized following bug (Android 8 & 9):
If I configure any mail account to "manually" in the native Huawei mail app, the app still looks for mails after a time when i only open the inbox....
Same situation when device goes into ultra power saving mode or automatically powers off because of low power....after return to normal state or reboot after charge the app now looks on all mail accounts for new messages itself/automatically. This happens when WIFI was on before powersaving mode or power off. As soon WIFI is available at startup or return to normal mode aforementioned situation occurs.... Can be avoided by canceling WIFI connection to the server/router....
That is indeed annoying!
ppcppcppc said:
Wonder if the volume rocker is not vertically orientated in Pie. Mine is working good, sliding down goes to silent. Above the slider is a button for vibration, sound and silence.
Click to expand...
Click to collapse
And what does sliding to the side do?
It should show all the profiles like media, alarm and phone volume? No?
I noticed that the homescreen shortcuts, that arised if you press and hold on the Phone Manager icon, were removed. Too bad, would link the power mode to homescreen. Even better would be a shortcut in the Quick Settings.
My new A32 5G on t-mobile comes with rtt call button set to "visible during the calls". The only other option is "always visible". As a result RTT call button is always on a call screen and I already accidntally activated it a couple of times during the call thus switching to RTT mode. I am never going to intentionally initiated RTT mode on my side and even though the intended user of this phone is hard of hearing, that person will in fact be completely lost if they do initiate it (and they will do so by accident). So I have a couple of questions.
First, since I have not seen this discussed yet I wonder whether other t-mobile users also have that "feature" or am I a rare exception? (Though I have two devices and both have RTT visible during all calls.)
The second question is -- is there a way to disable that button?
amelbeabk said:
For some reason real time text started showing up during my phone calls. There doesn't seem to be a way to turn it off. I don't need this feature, I don't like this feature and I want it gone.
Click to expand...
Click to collapse
Do you use the original dialer or a google phone dialer? In my case I realized that the problem only exists with google phone (which is the one I use). The original Samsung dialer has the RTT entry safely hidden in the three dot overflow menu. At least when RTT is set to "only visible during the calls" in the settings.
I still prefer using google phone and that would need "not shown" (or whatever the correct name) entry that Samsung removed from the settings.
amelbeabk said:
For some reason real time text started showing up during my phone calls. There doesn't seem to be a way to turn it off. I don't need this feature, I don't like this feature and I want it Kodi nox gone.
Click to expand...
Click to collapse
You can disable that feature on dialer menu, rtt was implemented by Android you could aslo disable said package
Implementing Real-Time Text | Android Open Source Project
source.android.com
Apparently, via other forums, if your caller has RTT on, you get it automatically (unconfirmed).
My Galaxy S10+ has NO off switch for RTT. The default dialer via Verizon/Samsung took a UI dive recently.
I installed the Google dialer and the UI was better, but RTT was on EVERY call.
I had to get RID of it, and finally, I found ACR Phone Dialer in the Google Play Store:
Highly recommend.
-Christian
Starting a thread to track Android 12 Bugs and issues similar to https://forum.xda-developers.com/t/android-11-bug-problems-original-firmware-xperia-5-ii.4225029/
In first few hours of use I found out that sometimes status bar vanishes and you need to scroll down settings panel to get the status bar again.
Observed this couple of times but not able to repro it consistently.
Anyone facing this? Any other issues to report?
Couple of another issues:
1) Dynamic vibration seems to be kicking off on first level and phone vibrates vigorously.
2) Multi window is having few issue like sometime one of the window is blank and when you try to see recently used apps the screenshot of the app shows zoomed in content.
IV updated not long ago I'm using nova launcher not noticed any bugs as yet just a boat load of blue everywhere lol
Dynamic vibration is working Continuously when I play YouTube video or something. That's the only bug I found. Even I tried to low ,mid or high it's not controlling properly. They need to fix this.
Small update. Dynamic vibration continuously work if I use my xm4 ear buds.
Connecting to headphones via tapping on the NFC doesn't work (wh-1000xm3)
I get a vibration, headphones turn on but I have to manually go to bluetooth tab and connect from there
disconnecting works fine
No new theme engine found in sony's android 12 update, is this a feature or bug?
k_basara said:
No new theme engine found in sony's android 12 update, is this a feature or bug?
Click to expand...
Click to collapse
i think they have not included the new theme-color-walls-feature like on Pixels for example, or other Brand. It's a very specific choice, i think, after all Xperia use Android Stock if i'm correct.
I'm no Android expert so my Xperia 5 II is stock. I do use the Nova Launcher. I'm in Mexico and got the update two days ago. I'm mostly deaf and don't use the phone and didn't notice until 3:30 this morning that I had no internet connection and when I checked in "Settings" I saw my provider, Telcel, and a not "Temporarily Inavailable". Since it was Sunday morning I thought maybe they took service down doing some sort of maintenance. At eight I took another look. I tried *133# to see my account status and got a message, "Temporarily Unavailable." Then I tried sending a text message to a friend and it went through.
I went to "Settings", deleted Telcel as my service provider, cancelled the instruction to automatically connect and shut down. Then I started the phone, reconnected to Telcel, reinitiated the order to connect automatically and all went well and it worked fine.
Other than that, I have had no glitches. I don't use vibrations or split screens. I did give the cameras a pretty good run and they worked fine.
Screenshot is no longer accessed from long press power button, but is now accessed through the square navigation button. Meaning i can no longer screenshot my apps list.
Ambient display, when phone is locked and idle, is dimmer than when in Andriod 11. Brightness cant be adjusted.
Turning wifi on/off requires more touches. You now have to press 'Internet' from the top pull-down menu and toggle the wifi on/off from a popup menu at the bottom of screen. I hope your fingers can reach if using one-handed.
Switching phone calls and notifications to Normal/Silent/Vibrate from pressing the Volume buttons on the side opens up a list of switches, rather than pressing same icon and cycling through modes.
The shortcuts in the top pull-down menu are larger. In Android 11 i had setup 6 most used shortcuts across the top, now in 12, 6 shortcuts take up half the screen.
Tapping the square navigation button twice to switch between open apps must be done slower. No more fast switching.
Swiping the top pull-down menu once covers the whole screen, whatever you were looking at is covered by the drop down.
You can probably tell i dont like A12, but i know, im probably whinging over nothing.
Screenshot is no longer accessed from long press power button, but is now accessed through the square navigation button. Meaning i can no longer screenshot my apps list.
PRofec said:
Screenshot is no longer accessed from long press power button, but is now accessed through the square navigation button. Meaning i can no longer screenshot my apps list.
Click to expand...
Click to collapse
I found that screenshot is done by holding the power button and volume down at the same time, which is the most clumsy and unnecessary thing to add. If there's a way to get this back by only long pressing the power button, I'd love to know.
I'm not a fan of this as well, mainly because they managed to break things that didn't need fixing, like turning on and off wifi. It is however better in that when I turn off wifi, it is automatically on my mobile network. Before this update, it would not automatically connect to the mobile network and I would have to toggle plane mode on and off several times or restart to get the mobile network connected. So that's working better at least.
Another issue I'm having is that when I delete an email from Gmail, it will sit in the notification bar showing deleted until I clear it, when before it would clear on its own after a few seconds. Also, the huge buttons look awful.
I don't want to go back to Android 11, but I would like the long press screenshot back, the buttons in the pulldown to look like they did before and accessing wifi simplified....I'm sure I'll find more things I hate with each passing day.
I don't know. I've never done a screenshot and my notifications for email go away when I delete the email whether I delete it on my phone or on my Chromebook. My old arthritic hands are cursed with stubby fingers and I rather like the large buttons.
Why do people turn WiFi off and on. My is just on. As I visit coffee shops, restaurants, and public places my phone automatically connects to other WiFi. I don't do anything requiring secuity while visiting other locations.
As usual, for me, Android 12 will be an irritating mess for a week or so and then it will miraculously improve.
patrickt said:
I don't know. I've never done a screenshot and my notifications for email go away when I delete the email whether I delete it on my phone or on my Chromebook. My old arthritic hands are cursed with stubby fingers and I rather like the large buttons.
Why do people turn WiFi off and on. My is just on. As I visit coffee shops, restaurants, and public places my phone automatically connects to other WiFi. I don't do anything requiring secuity while visiting other locations.
As usual, for me, Android 12 will be an irritating mess for a week or so and then it will miraculously improve.
Click to expand...
Click to collapse
I got in the habit of turning wifi on and off because on android 11, whenever I would get out of wifi range, it wouldn't automatically connect to mobile and so I would have no signal at all. I think it's a habit for me at this point, but it still shouldn't require 3-4 steps to turn on or off.
The longpress screenshot was really handy. Having to use a combination of buttons doesn't make much sense from a user standpoint...namely, mine
The big buttons, I've gotten used to and I do like that you can expand the size of the screenshot window to capture more of the image.
The biggest issue for me is the deleted messages not clearing. It will sit there all day showing deleted if I let it.
JS000 said:
I got in the habit of turning wifi on and off because on android 11, whenever I would get out of wifi range, it wouldn't automatically connect to mobile and so I would have no signal at all. I think it's a habit for me at this point, but it still shouldn't require 3-4 steps to turn on or off.
The longpress screenshot was really handy. Having to use a combination of buttons doesn't make much sense from a user standpoint...namely, mine
The big buttons, I've gotten used to and I do like that you can expand the size of the screenshot window to capture more of the image.
The biggest issue for me is the deleted messages not clearing. It will sit there all day showing deleted if I let it.
Click to expand...
Click to collapse
I never had that problem switching to my cell service when out of WiFi range. I think my 5II came with Android 11 and my Wifi and cell service are two different divisions of the same company. I don't know if that would matter.
I'll keep an eye on notifications but so far they're disappearing when the source is deleted..
Thanks for your responses.
The screenshot press vol down / power button doesn't work for me.
About the Gmail issue, i havent had that issue yet. I do use gmail, but its not my primary.
Im in the habit of turning wifi on/off when i use it. It defaults back to mobile network without issue, thats always on so I dont share that experience.
Ive just found another issue. Long press on the home screen and selecting 'Wallpaper'. When i select a wallpaper and set as home screen only, it applies to both home and lock screen.
Secret menù *#*#7378423#*#* has changed with android 12?! Somebody has tried it? Thanks
rez78 said:
Secret menù *#*#7378423#*#* has changed with android 12?! Somebody has tried it? Thanks
Click to expand...
Click to collapse
Yeah! a lot of options are missing there like Service tests and other Network related configs.
I've no issues with the update besides Android 12 user experience being garbage in some areas where it was perfectly fine in Android 11. This is mostly with the quick settings where I now need one more tap for almost everything I'm using.
As72 HK version .. in the Philippines... Incoming and outgoing calls not working after the upgrade. Phone restarts didn't help
Worked for a few days after doing a factory reset... But stopped working again...
Sms and LTE+ is working, no issues..
I found a workaround for dynamic vibration issue in 5II after Android 12 update (issue being dynamic vibration accidentally kicks in while playing video on YouTube or Facebook)
Go to settings>Sound > Disable Dynamic vibration.
Play a video in YouTube or Facebook.
Get back to settings > Sound > Enable Dynamic vibration.
Now, dynamic vibration won't kick in accidentally.