Related
I open up WMP, go to the Library, Menu->Open File, and I select a music file from a directory full of music files. Normally if I leave it when it finishes playing the song it will move on to play another song in the same directory with shuffle.
However if I turn off the screen when it's in the middle of a song, it will continue playing the song but when it finishes it will not move on to another. It will only continue when I turn on the screen again.
Is this some weird default behavior, should it be happening? Can I override this?
There is a place where you can change hot key settings, there is a key setting for the screen. Hope that solves your problem.
Thanks! That worked.
One more thing though, I am using a 6.5ROM and Titanium has a lovely WMP plugin. I find it quite convenient to control the playing song from there - so is there a way to turn off the screen the same way when viewing the Today screen so that when I turn it on again I see Titanium?
noidtluom said:
Thanks! That worked.
One more thing though, I am using a 6.5ROM and Titanium has a lovely WMP plugin. I find it quite convenient to control the playing song from there - so is there a way to turn off the screen the same way when viewing the Today screen so that when I turn it on again I see Titanium?
Click to expand...
Click to collapse
The best I can come up with is use a hardware button to launch a "Screen Off" app. You should just be able to Bing or Google "Screen Off .cab" and find something free. Have you tried Locking then waiting for the screen to Time-Out? maybe the screen will just dim, my guess.
erickbryce said:
... Have you tried Locking then waiting for the screen to Time-Out? maybe the screen will just dim, my guess.
Click to expand...
Click to collapse
Thats what I do with Sat Nav, works a treat. No point having the screen on when its in my pocket (im on a motorbike using handsfree to listen to instructions).
Nifty, I guess locking then waiting for the screen to time out is good enough for me. No sense in getting some extra program and binding it to another key.
Thanks
Just picked up a Radar, moving from two years of Android. Hoping I could get some help on the following questions:
1) Does WiFi turn off when the phone sleeps? If so, is this a changeable setting?
2) I'm having trouble getting GoVoice to notify me. I've gone through all the setup numerous times. I leave myself a voicemail and I don't get notified. If I click the app, it refreshes, vibrates and gives me the new message.
3) Is there a way to bypass the initial lockscreen when using password lock?
4) Is there a way to have the Maps app voice direct me automatically, or I have to touch the screen?
5) Can the maps app navigate if it isn't in the foreground?
6) How do I truly close an app? Like when I run Slacker and stop using it, it still displays on the lock screen.
7) Is there really a difference in the find my phone functionality turning off push vs sms?
THANKS
bump..........
1) Does WiFi turn off when the phone sleeps? If so, is this a changeable setting?
Yes it turns off. Not changeable.
2) I'm having trouble getting GoVoice to notify me. I've gone through all the setup numerous times. I leave myself a voicemail and I don't get notified. If I click the app, it refreshes, vibrates and gives me the new message.
Dont use it, but did you contact the app developer?
3) Is there a way to bypass the initial lockscreen when using password lock?
No, it's more secure than Android bypasses.
4) Is there a way to have the Maps app voice direct me automatically, or I have to touch the screen?
Not bing maps. There are alternatives.
5) Can the maps app navigate if it isn't in the foreground?
Not sure it can. It will refresh to your current position when you go back to it.
6) How do I truly close an app? Like when I run Slacker and stop using it, it still displays on the lock screen.
Back, back, back, back till you go to home screen.
7) Is there really a difference in the find my phone functionality turning off push vs sms?
I would leave all of those settings as 'on' as that maximizes my chances of finding my phone.
hah2110 said:
Just picked up a Radar, moving from two years of Android. Hoping I could get some help on the following questions:
1) Does WiFi turn off when the phone sleeps? If so, is this a changeable setting?
2) I'm having trouble getting GoVoice to notify me. I've gone through all the setup numerous times. I leave myself a voicemail and I don't get notified. If I click the app, it refreshes, vibrates and gives me the new message.
3) Is there a way to bypass the initial lockscreen when using password lock?
4) Is there a way to have the Maps app voice direct me automatically, or I have to touch the screen?
5) Can the maps app navigate if it isn't in the foreground?
6) How do I truly close an app? Like when I run Slacker and stop using it, it still displays on the lock screen.
7) Is there really a difference in the find my phone functionality turning off push vs sms?
THANKS
Click to expand...
Click to collapse
For WiFi, if you are streaming music with one of the Pandora apps (MetroRadio or RemoteConrolled), it will continue to play using WiFi.
Try pinning the GoVoice app. Not sure if it will help or if you already did this. If you are in an area with no coverage when the notification is sent, you might miss it. Then you will need to launch the app and refresh. GoVoice could be modified to check this with a background process that would run every 30 minutes. It may already do that.
As far as closing apps. For music, I usually just pause it. It will eventually be inactive. Unlike Android, apps are actually suspended when put in the background. If music is paused it isn't streaming, so it isn't doing any work.
If you really want the processes cleaned up. Back, Back, Back, ...
Maps don't update in the background. In fact GPS can't be accessed in the background. But, the GPS works fast in the foreground.
Faster way to close the app out it hold the back button, select the window that has the app like slacker, when app comes up, hit back.
Not to say you can't do it, but I wouldn't worry about closing apps. On Android you needed to as they would suck your phone dry with unruly processes and poor management. With windows phone its a suspended action unless streaming something. So in the case of slacker, or any other music player, once you hit "pause" its a stopped process. It isn't using resources, and will eventually be kicked out.
The WP system will manage it on its own and boot out old processes to make room for things if its finding that it needs to.
Bump........
hah2110 said:
Bump........
Click to expand...
Click to collapse
It looks like all of your questions have been answered.
Is there a specific question that still needs answering?
If not, there is no point in bumping.
If so, please state the specific question / questions that you still need answered.
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
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.
I am so used to my OnePlus 9's AOD that I'm kind of surprised how terribly it seems to be implemented here and I'm hoping it's just being buggy...
First off, the AOD doesn't seem to work at all if I don't choose to have it displayed all the time (which is the first hint that this may be a bug as even the preview for tap or lift seems to suggest that the AOD should be popping up, not the lock screen as is happening right now).
Second, if I do have it displayed all the time, incoming notifications bring up the lock screen. My OnePlus shows a preview of that one specific notification while still on the AOD screen and it seems silly that Google isn't utilizing something similar. It is extremely handy to have a text come in, say with a 2FA code, and have the entire screen black besides a large preview that shows you that code. The way that it is working now, it wakes the lock screen, which is fine, except the message gets truncated so it often requires me to interact with the device even further to be able to see the full message.
I also tried turning off wake the screen for notifications to see if that triggers the AOD and... it just adds an icon to the AOD...
This is a huge downgrade in user experience if this is the normal expected behavior. I could have sworn my 3 XL handled it better than this but I haven't used it for awhile and I'm not at home where I could check it. Maybe I'll have to look into third party options.
Im not quite sure and your whole post. I as well had the Oneplus 9 pro. My Pixel 7 pro AOD works just fine. I double tap screen and goes directly to the AOD, which displays the Date(top left corner), the time that is big, the fingerprint icon and battery percentage. a tap of the screen brings up the lock screen. Face unlock and pin works directly to the home screen. Now I do have to say im using Nova Launcher as i can't stand that the dat and google search bar can't be removed.
schmeggy929 said:
Im not quite sure and your whole post. I as well had the Oneplus 9 pro. My Pixel 7 pro AOD works just fine. I double tap screen and goes directly to the AOD, which displays the Date(top left corner), the time that is big, the fingerprint icon and battery percentage. a tap of the screen brings up the lock screen. Face unlock and pin works directly to the home screen. Now I do have to say im using Nova Launcher as i can't stand that the dat and google search bar can't be removed.
Click to expand...
Click to collapse
Thanks. Sounds like I have a bug after all right now.
When you get a text or something, does it show an AOD notification with a preview like the OnePlus did or does it just show the lock screen?
I turned off screen on with new notification, I will have to check
Without screen on with new notification, I still get the notification and AOD stays on. Lock screen does not come on. So in other words, AOD works as it should.
EtherealRemnant said:
Second, if I do have it displayed all the time, incoming notifications bring up the lock screen. My OnePlus shows a preview of that one specific notification while still on the AOD screen and it seems silly that Google isn't utilizing something similar. It is extremely handy to have a text come in, say with a 2FA code, and have the entire screen black besides a large preview that shows you that code. The way that it is working now, it wakes the lock screen, which is fine, except the message gets truncated so it often requires me to interact with the device even further to be able to see the full message.
Click to expand...
Click to collapse
The AOD on my Pixel 4a works just like you describe the OnePlus AOD, it stays on the AOD but displays the message at the center for a few seconds, sounds like a bug (unless this changed on the 7 and 7 pro for some reason).
Interesting. Thanks to both of you. Hopefully it gets resolved at some point. I'm in no mood to factory reset and set everything up again so I'll just deal with it for now.
EtherealRemnant said:
Interesting. Thanks to both of you. Hopefully it gets resolved at some point. I'm in no mood to factory reset and set everything up again so I'll just deal with it for now.
Click to expand...
Click to collapse
Yeah Im trying to adjust to not having Recent Apps, home and Back buttons on the screen! lol
schmeggy929 said:
Yeah Im trying to adjust to not having Recent Apps, home and Back buttons on the screen! lol
Click to expand...
Click to collapse
You can get those back if you want. Settings > System > Gestures > System navigation and change back to 3-button.
Do you have the wake screen setting toggled? It's possible that's why
EtherealRemnant said:
You can get those back if you want. Settings > System > Gestures > System navigation and change back to 3-button.
Click to expand...
Click to collapse
Thanks, I literally just found it as I was getting your reply notification!
bosox284 said:
Do you have the wake screen setting toggled? It's possible that's why
Click to expand...
Click to collapse
I have tried messing with all four settings in all sorts of configurations to see if I can get it to work properly and have been totally unsuccessful. It seems I have just stumbled on some kind of bug.
EtherealRemnant said:
I have tried messing with all four settings in all sorts of configurations to see if I can get it to work properly and have been totally unsuccessful. It seems I have just stumbled on some kind of bug.
Click to expand...
Click to collapse
Hey, I do have the same bug. Did you manage to fix it ?
I am rooted + I use Kirisakura kernel
I don't think this would be the cause but we never know ...
Repear88 said:
Hey, I do have the same bug. Did you manage to fix it ?
I am rooted + I use Kirisakura kernel
I don't think this would be the cause but we never know ...
Click to expand...
Click to collapse
It was resolved after I did a factory reset and restored only SMS and apps (but not settings) from my Google backup.
EtherealRemnant said:
It was resolved after I did a factory reset and restored only SMS and apps (but not settings) from my Google backup.
Click to expand...
Click to collapse
Thx ! Damn it ...
I didn't restore anything ... I'll try before resetting (it's been only 2 days I have it ready XD)
schmeggy929 said:
Im not quite sure and your whole post. I as well had the Oneplus 9 pro. My Pixel 7 pro AOD works just fine. I double tap screen and goes directly to the AOD, which displays the Date(top left corner), the time that is big, the fingerprint icon and battery percentage. a tap of the screen brings up the lock screen. Face unlock and pin works directly to the home screen. Now I do have to say im using Nova Launcher as i can't stand that the dat and google search bar can't be removed.
Click to expand...
Click to collapse
Don't know if I understand you correctly. Do you have enabled AOD all the time (always show time and info)? If not, you double tap to show AOD and it's working fine? Do you have any other settings enabled (tap to check phone, etc)?
I have disabled AOD (always show time and info) and when I tap, it goes straight to lockscreen. Not sure but that change may have been introduced in one of the latest updates.
@EtherealRemnant same question to you
In my case as it works right now:
When I enable AOD (always show time and info), it is showing all the time. When I disable that, it's not. When I tap on the screen (when AOD is disabled), it goes straight into lockscreen. When I receive a notification, AOD shows for a short moment.
What I would like to achieve (dunno if that's possible) would be to have tap to show AOD instead of lockscreen (with AOD not showing all the time).
I understand what you would like to do( tap the screen to have AOD appear first. I cannot find anything like( temp AOD) in settings. The show time and info toggle is basically the master AOD switch. Either AOD all the time or disabled completely, nothing in between.
Same for me, after reading topics on reddit, I was thinking I wasn't a bug and I might misunderstood what op was saying.
@trawel to add to your statement, if you move slightly your phone, like lifting one side, the AOD should come, most of the time (sometimes screen stays black)
But yeah I also would like to be able to "tap to show AOD" so it won't unnecessarily unlock when it sees my face.
AOD = Always On Display...it's in the name...ALWAYS ON. I understand what you're looking for but then it would NOT be called AOD, but SOD = sometimes on display.
jaseman said:
AOD = Always On Display...it's in the name...ALWAYS ON. I understand what you're looking for but then it would NOT be called AOD, but SOD = sometimes on display.
Click to expand...
Click to collapse
We get the semantics but the point is that the AOD used to function differently. You used to be able to tap to get the AOD to come on and lifting the device used to always go to AOD FIRST. When I made this thread, I was not seeing the AOD at all most of the time. A factory reset has set it to such that if the phone gets barely moved, the AOD comes up, but tapping or picking it up quickly will almost always go to the lock screen (but then sometimes it will go to the AOD too when picking it up quickly) so it's clearly bugged somehow as the behavior is inconsistent, whichever way that Google intended for it to actually be.
Going beyond that, the AOD is pretty useless anyway. Any incoming notifications light up the lock screen. Why can't they just make it like my OnePlus where the notification shows up on a black screen with a full preview when AOD is enabled? This is so much more useful, not to mention battery friendly.