Related
HTC Sensation: Possible solution of "phone doesn't sleep" and "power button" problem
Hi every body,
I was getting irritated and extremely fed up of basically two problems of my htc sensation:
1- The phone didn't automatically turn the screen off. The screen would remain ON and wouldn't automatically lock itself. For example, i use the phone and then i will place it at a side expecting that first screen will be dimmed and then phone will automatically lock itself. It wasn't happening since a very long time (I don't remember the beginning of problem), even when screen timeout setting was enabled. I also observed that if at one time i set the brightness level of display to be automatic, next time i check it and brightness level was always set to be at maximum level.
2- When i pressed the power button to lock the phone, the phone often doesn't go dark. It went dark for a second and then became ON again. I had to press it a number of times until it goes dark. Similarly when i wanted to unlock the phone, i had to press the power button multiple number of times, until it gets unlocked.
Basically i was trying to solve the 1st problem. I went into settings -> applications -> manage application. I checked for each installed application whether it has following in the permissions:
System tools: prevent phone from sleeping
Following applications had above mentioned permission, so i removed them:
xda
ebay
mobile voip
daily motion
sports tracker
Calorie Counter - MyFitnessPal
imdb
Photo Editor
speedtest.net
whatsapp
yahoo messenger
Surprisingly after removing those apps, both issues 1 & 2 were totally gone. The phone was automatically locking it self (it still is). So for me problem number 1 is totally gone now.
However, regarding second problem, i tested it like 100 times locking and unlocking the screen by pressing power button. The behavior was absolutely normal. Then i checked the brightness level of phone, it was set to maximum, i set it to automatic. As soon as i set the brightness level to be automatic, the 2nd problem somehow reappeared.
Now if i set the brightness level manually, the 2nd issue doesnt reappear, but when i set the brightness level to be automatic, power button issues reappears.
Sorry for such a long post but I hope may be this post helps someone, also i would like to ask the experts the justification of such behavior of phone.
I am using stock rom and android version 2.3.4, sense version 3.0 and software number 1.50.206.1
This definitely needs a bump!
I was thinking of possible solutions as well, but this one makes sense. Maybe it is a flaw in how that permission is handled? I don't know how to program, but if any of you clever rom hackers are around, maybe you can try tweaking this? I was thinking that it was maybe something to do with the hardware button itself, sending off multiple signals to the phone telling it to lock and unlock right after due to the shoddy power button design.
My main issue with the fix in the original post is that I use a lot of apps that require this permission, and apps are kinda what define how useful your phone is (aside from making phone calls, that is). If there was a way to fix this issue by either tweaking the "prevent phone from sleeping" permission, or maybe just trying to add an input delay that doesn't register any power button presses until half a second has passed or something.
Like I said, I don't know what is possible to tweak with android since I don't know how to program so I might just be talking out of my butt, however, I do like this phone, it just has this one major power button flaw that really annoys me!
#2 doesn't occur in ICS Roms. I'm always on auto brightness.
Some ROMS added some apps may let your phone awake automatically when you close the screen,so it is the right way to move some apps. Using ARHD ICS and Insection ICS ROMS ,#1#2problems never happend.
Basically i would like to stick to original stock rom. I know i can avoid these problems if i use custom roms.
@Tekuno
Let me tell you, i didn't delete all of those apps which were using that permission "prevent system from sleeping". I only deleted those which i mentioned in my 1st post. Among those, i installed "yahoo messenger" again and 1st problem started happening again. I removed that app, problem gone. For me it's the case of hit and trial. I can't definitely point out one specific app which cause the problems.
I think there is really a flaw in the way this permission is handled by operating system of the phone.
I would also like to keep with the stock rom if possible. I figured it would only be a few apps that would be causing the lock screen issues, I am currently too lazy to go through all of the apps and figure out which ones are causing it.
I'll wait patiently for the ICS and Sense 3.6 update and see if that helps.
i have both problems too. About no 2, i always tot it happens after using the stock camera app which forces the brightness to go maximum and sometimes after exiting, there is some bug that doesnt return setting to automatic. Just a hunch but not sure :s
Do you have "Extended quick settings" installed ? and on a custom ROM, if so then i guess you need to check the "Screen On" option in the extended quick settings dropdown window.
You must have accidentally pressed it and activated it instead.
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
Hi,
I just purchased an x96 box and was looking through the features when I saw the security feature for setting up a resticted profile. Since I have kids I thought it would be good to set one up, so created my password and then clicked "enter restricted profile". Not only did it restrict the apps that were availible to me, but now in the sttings tab all the buttons are gone (except for network) so I can't change any settings. As well there isn't anything for me to toggle back to normal profile. I basically am stuck in restricted profile and cant change it. When I turn on and off the box it comes back on in regular mode (all the apps), but then 5 seconds in it says "switching to restricted profile" and I cant make any changes to settings.
Anyone who can help would be a lifesaver.
Cheers
Android
Archiero said:
Hi,
I just purchased an x96 box and was looking through the features when I saw the security feature for setting up a resticted profile. Since I have kids I thought it would be good to set one up, so created my password and then clicked "enter restricted profile". Not only did it restrict the apps that were availible to me, but now in the sttings tab all the buttons are gone (except for network) so I can't change any settings. As well there isn't anything for me to toggle back to normal profile. I basically am stuck in restricted profile and cant change it. When I turn on and off the box it comes back on in regular mode (all the apps), but then 5 seconds in it says "switching to restricted profile" and I cant make any changes to settings.
Anyone who can help would be a lifesaver.
Cheers
Click to expand...
Click to collapse
I am having the same exact issue. Can you please let me know when you get some resolve
Thanks
I ended up doing a factory reset. Click on the apps button on the home page. Near the bottom is a button that says "backup......". Clicked on that and checked off delete data and delete "something" then hit restore. Good to go.
Hope that helps.
Let sera...
Ok so I got a x96 foolishly done the same thing. Here's how to set it again. While the power is off in the av point on the rear of the box poke a match stick in and there is a button insode. Hold it down. It will come up with options like a boot sort of setup options. I went to clear data or something along those lines and boom back to factory settings. I looked everywhere for a reset button it was only because company I purchased from advised me it was there.
Ditto! Is ther e any other option than reseting factory settings? How can i apply the original passcode I entered?
Did you get it fix?
Archiero said:
Hi,
I just purchased an x96 box and was looking through the features when I saw the security feature for setting up a resticted profile. Since I have kids I thought it would be good to set one up, so created my password and then clicked "enter restricted profile". Not only did it restrict the apps that were availible to me, but now in the sttings tab all the buttons are gone (except for network) so I can't change any settings. As well there isn't anything for me to toggle back to normal profile. I basically am stuck in restricted profile and cant change it. When I turn on and off the box it comes back on in regular mode (all the apps), but then 5 seconds in it says "switching to restricted profile" and I cant make any changes to settings.
Anyone who can help would be a lifesaver.
Cheers
Click to expand...
Click to collapse
I know I'm a 'lil late to ask u if u got by the restricted profile... if not... I found out by looking with my phone flash light there's a reset button through the speaker...
Did you get it
mightyjoe123 said:
I am having the same exact issue. Can you please let me know when you get some resolve
Thanks
Click to expand...
Click to collapse
I know I'm a 'lil late to ask u if u got by the restricted profile... if not... I found out by looking with my phone flash light there's a reset button through the speaker...
X96 restricted profile problem
Now any new solution? When I set PIN code and apply restricted profile after that I cannot reverse normal mode, can't apply PIN code
With a factory reset ?
So did anyone work out how to get back removing restricted profile without a factory reset. It seems so counter productive...
Thanks.
Hope it works for you too.
Okay. So, I didn't see a reset button hidden anywhere, but I didn't wanna have to do that anyways. What I've found is that when you turn it off and back on, you can go back out of restricted mode. You just need to be really fast before it re-enters restricted mode again. You have about ten seconds. It's best to connect a mouse because it takes longer to scroll to the apps and options using the remote. But I did everything in time because my password was 0000. As soon as it turns back on, as quickly as possible, go to settings, >security & restrictions, then go to turn off restricted profile. Quickly enter your passcode and you're home free! After that, I'd highly recommend deleting restricted profile. Hope this works for you too!
---------- Post added at 06:26 PM ---------- Previous post was at 06:23 PM ----------
sammyDC said:
So did anyone work out how to get back removing restricted profile without a factory reset. It seems so counter productive...
Thanks.
Click to expand...
Click to collapse
Okay. So, I didn't see a reset button hidden anywhere, but I didn't wanna have to do that anyways. What I've found is that when you turn it off and back on, you can go back out of restricted mode. You just need to be really fast before it re-enters restricted mode again. You have about ten seconds. It's best to connect a mouse because it takes longer to scroll to the apps and options using the remote. But I did everything in time because my password was 0000. As soon as it turns back on, as quickly as possible, go to settings, >security & restrictions, then go to turn off restricted profile. Quickly enter your passcode and you're home free! After that, I'd highly recommend deleting restricted profile. Hope this works for you too!
Yours is the best idea to solve the issue. Unfortunately my GT1 is so fast, that gives me only 1 second. The same is with wired mouse. Is there any experience, if after master (pinhole) reset the Google account should get back all (Kodi reppositories, YouTube account,...) settings ?
I have exactly the same problem with my Philips 49PUS7502/12 Android TV. I even didn't set up a PIN CODE for it. I can't get out of this profile. Any solution rather than factory reset? I have many apps and customization.
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.
I can successfully run widgetupdatet and musicproxy on my uis7862 unit.
But I think i need to make it start at boot/wakeup and also make it not battery optimized
So for start at boot/wake up, i turn it on with User - application. But this make widgetupdater app show up everytime when unit boot up, which i prefer it to hidden
For battery optimized setting, I don't have battery option from my setting menu.
May I have your advice on this?
@KёniG
Thanks
Hello.
The newest firmware doesn't have battery settings. Install this https://play.google.com/store/apps/details?id=com.sika524.android.quickshortcut and find "Settings suggestions". Launch it and type in the search field "Battery".
KёniG said:
Hello.
The newest firmware doesn't have battery settings. Install this https://play.google.com/store/apps/details?id=com.sika524.android.quickshortcut and find "Settings suggestions". Launch it and type in the search field "Battery".
Click to expand...
Click to collapse
cool, thanks. Let me try this app on my unit for battery setup part
May I know how about the startup part, anyway I can make the app screen do not popup and make a more silent startup?
(for my firmware, I can make app startup automatically in settings -> user -> application settings
Thanks again
@KёniG
I've switched to paid version and turn on "silent start" seems it will just flash then go away which is good now.
However I don't find the way to open the app to change settings anymore (don't see the icon at notification menu) . need to wipe out the app data to get back to setting screen
jasonwong28 said:
May I know how about the startup part
Click to expand...
Click to collapse
My answer above is about silent start up.
If you have the restricted notification bar it is required to reinstall the app to enter settings. Silent mode is not appropriate way for you.
KёniG said:
My answer above is about silent start up.
If you have the restricted notification bar it is required to reinstall the app to enter settings. Silent mode is not appropriate way for you.
Click to expand...
Click to collapse
Thanks, so either I can still choose silent startup but need to reinstall app if i need to change settings
Or
I dont make it silent startup but i will see the setting screen everytime the unit starts?
and one last thing
After I use musicproxy+widgetupdater. When I use my wheel button - "mode" to change the source, it will go through radio, Phone, Bluetooth music, then my specified music player, then stopped if i press "mode" again. Originally, the next app is the map and then loop back to radio. Is it normal behaviour?
Thank you so much
Played a bit more, seems AIMP is working fine to loop the button cycle.
Your problem got solved?
SamWarner01 said:
Your problem got solved?
Click to expand...
Click to collapse
silent startup still make the app no longer configurable but is ok as I don't think need to always configure that often.
For wheel button issue, I find out is my specific app (KKBox) issue. If I change to AIMP or another music app then is working fine to cycle the sources.
And i think a setting which is quite useful for me is "Multiple music app" which will show current playing app info in that widget area