Related
So I`m new here and if my thread is not on the right place - sorry. And here it is my problem:
I`m using Widgetsoid Switcher Widget and have this very annoying problem that when i turn on something it not works (For example: I turn on my data service, widget indicates that it`s turned on but actually it's not. If I turned it on from the Settings menu the widget indicates it`s turned on and when I stop it from the widget it doesn`t stop). Same with WiFi and GPS... This thing is freaking me out so if somebody can help me it would be great or if you can tell me other app like that one with options for customization. Thanks in advance
Can`t somebody help me?
podmatrix said:
Can`t somebody help me?
Click to expand...
Click to collapse
Hi,
Try to uninstall, install and reboot directly after install (it's important!).
After go to global preferences and check "Disable all apn"
Create your widgets and it will be ok.
Now everythings is fine but Data Service still doesnt't work... Any ideas?
data toggle help
i had the same problem with the data/3g toggle on my htc evo. what you have to do is go to "settings->wireless & networks->then scroll down and make sure there is a check mark in the "mobile network" setting" in order for the widget to control it the setting must first be enabled. it took me and the dev 3 days to find this out.
also if that doesn't work go into the app itself and as soon as it opens it you should see something at the top that says data toggle mode. make sure that setting is set to "APN toggle" and not "APN rename"
hope this helps. remember to rep if it did
Thanks man
No problem
Sent from my PC36100 using XDA App
I had a similar problem today, it looks like the data switch in Widgetsoid places a dash in front of your AccessPoint name in order to block data transfer and removes that dash when you click switch again.
After messing with Widget I was not able to connect to net, I installed, uninstalled, etc, and then I noticed that APN list was empty, I had to add the APN again and restart it, I think (as said above) that you need the data to be ON then do a restart in order for Widgetsoid to properly read the status.
If you're rooted, use the new "root method" to toggle data. It doesn't mess with your APN & it works flawlessly for me. It's the first time I've had a data toggle that actually works.
A simple method
FIX = Settings>Location & Security>Select Device Administrators> *Uncheck Widgetsoid
Uninstalled
Thanks to: mr.noobsalot
I know this is an old thread, but where is the global preferences on version 3.4.1 it doesnt appear when I click apply.
Im using a HTC sensation and ICS.
Thanks
bump
euqiddis said:
bump
Click to expand...
Click to collapse
Stay FAR away from Widgetsoid. It can slow a Galaxy S5 down to a Crawl. Your Dialer will not function, Your phone will not respond. Its trying to load your phone with Ads or something and keeps your CPU busy, whether its a dual core or quad doesn't matter. Developer does not respond and does not seem to care. After uninstalling this App, the phone feels "new" again.
I believe this app is some type of Spyware/Malware combo. Why does it need access to my Contacts? Something very fishy and the developer never responds. It's a great Widget when it works but certain things about it don't seem right. Uninstalled!
i keep being asked which app i would like to perform actions - i make a selection & all is fine until the phone is rebooted, then off it goes again.
i've trawled the general system settings looking for a toggle but failed to find anything related to default settings storage.
any help appreciated
my set-up is in my sig.
gascomm said:
i keep being asked which app i would like to perform actions - i make a selection & all is fine until the phone is rebooted, then off it goes again.
i've trawled the general system settings looking for a toggle but failed to find anything related to default settings storage.
any help appreciated
my set-up is in my sig.
Click to expand...
Click to collapse
Probably another program overriding your selections. Try try going to Menu button on your phone and select Settings option, scroll down to the Applications section and tap it. On the next screen, tap Manage Applications and then the All tab on the subsequent screen, scroll down the list of apps until you see the App in question listed and tap that entry. On the next screen look for the "Launch by default" section and hit the Clear defaults button. Reboot and select the default program you want and see if it sticks on the next reboot. Let me know if this helps.
Omnichron said:
Let me know if this helps.
Click to expand...
Click to collapse
good logical advice, which you would assume would do the trick.
unfortunately, it doesn't fix the problem
i was wondering if there's a file somewhere whch can be edited & locked?
im not 100% sure where those things are saved, maybe in settings.db file of the android settings app.
Check your phones app directory, there should be something like
com.android.providers.settings and com.android.settings
I could imagine that the filepermissions are wrong on certain files and thus your new selection are not saved.
i've searched for hours with no success for a db file. i do believe you are on the right trac but it'll take a smarter mind than my own to highlight where the setting is hiding.
there is a lockscreen toggle option on the redux2 rom, so i've asked over there.
thank you both for your thoughts
Anyone know how to change which apps are listed on the main screen in car mode? Long pressing on the app doesn't do anything. I've disabled tune in radio and would like to replace it with a pandora shortcut.
nvillamob said:
Anyone know how to change which apps are listed on the main screen in car mode? Long pressing on the app doesn't do anything. I've disabled tune in radio and would like to replace it with a pandora shortcut.
Click to expand...
Click to collapse
Don't think you can, apart from Navigation. Reason being is that the shortcuts don't open the App itself, it opens up a custom UI tailored for Car Mode, which I'm guessing is why you can't change them.
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
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.