Related
hi i have only just got the hero and was wondering how to close apps properly. i have noticed that when you hold the home key for a while a window pops up showing some apps ...is this how you close them? or is simply pressing the home key shutting them .
The long press on home just brings up a list of apps that have been recently run. It's almost a task switcher, but not quite!
Many apps will exit if you "back" out of them - i.e. when in the app keep pressing back until you get back to the home screen. However, this isn't the case for all applications. Some may have an explicit exit or close button, whereas others may have nothing at all.
However, Android is pretty good at managing its own applications, and will kill/exit them as necessary. In my experience, there's little to be gained from explicitly killing applications using a task killer, but some people swear by it.
Regards,
Dave
foxmeister said:
The long press on home just brings up a list of apps that have been recently run. It's almost a task switcher, but not quite!
Many apps will exit if you "back" out of them - i.e. when in the app keep pressing back until you get back to the home screen. However, this isn't the case for all applications. Some may have an explicit exit or close button, whereas others may have nothing at all.
However, Android is pretty good at managing its own applications, and will kill/exit them as necessary. In my experience, there's little to be gained from explicitly killing applications using a task killer, but some people swear by it.
Regards,
Dave
Click to expand...
Click to collapse
Most Task Killers free up memory thats used by background apps.
so basicly back out of the app and let android do the rest of the worring. thanks for advise
risterdid said:
Most Task Killers free up memory thats used by background apps.
Click to expand...
Click to collapse
Yes, but the point is that Android itself will start killing applications if it starts to run low on resources. (see http://developer.android.com/guide/topics/fundamentals.html)
Regards,
Dave
I'll attempt to sum it up once and for all, to try and set the record straight.
In Android's virtual machine, there is no functional differentiation between "closing" an app and "switching away from" an app. They are the same (the exception is things like music players which need to keep playing after you switch away from them, but even then only the 'service' part needs to keep running).
Whenever you switch away from an app, its current state is remembered so that even if it is effectively "killed" it can be returned to in just that state next time it's opened. Then Android either kills the process or it keeps it open, killing it when it needs the memory. You won't notice any difference between either scenario, except maybe that an app loads a little bit faster if it was kept in memory. At any rate, "closed" apps do not "run", and they do not take RAM or CPU cycles from other apps.
In terms of process/memory management, Android's VM has more in common with a web browser than a desktop OS - sure it can remember your state when you switch apps (like switching tabs, going back/forward/home in a browser) but whether behind the scenes it loads it all into and out of memory when you switch back and forth, or it all stays in memory is irrelevant to the user. Nobody worries that a long forum page on another tab or in their back button history is occupying 80 megs in the background or not, the browser takes care of loading/unloading it from RAM as needed, and that's just like how Android's VM works when switching between various pages of various apps.
Once you understand this you understand that all these 'task killer' apps are really unnecessary - all they'll do is make it slower to restart an app once closed. They don't reclaim RAM that was previously unavailable to other apps.
To cut a long story short, pressing "home" is a great way to close an app, whether you want to return to it later or not.
MercuryStar said:
Nobody worries that a long forum page on another tab or in their back button history is occupying 80 megs in the background or not, the browser takes care of loading/unloading it from RAM as needed, and that's just like how Android's VM works when switching between various pages of various apps.
Click to expand...
Click to collapse
that is not true for me, my firefox can eat a lot of resources as long as it is open. and i can see a performance difference when having a lot of apps open on my hero. not that it would be a problem, but you can see the menus scrolling more "fluid" after killing all bg apps, for example.
kendong2 said:
you can see the menus scrolling more "fluid" after killing all bg apps, for example.
Click to expand...
Click to collapse
I would wager that's the placebo effect. It feels faster because you believe it should. If you understand how the OS works you realise that apps you've switched away from do nothing to slow down or take memory from any other app (see my exception above about apps that launch background services such as music player).
kendong2 said:
that is not true for me, my firefox can eat a lot of resources as long as it is open. and i can see a performance difference when having a lot of apps open on my hero. not that it would be a problem, but you can see the menus scrolling more "fluid" after killing all bg apps, for example.
Click to expand...
Click to collapse
I do notice this too. There is a general 'sluggishness' with my Hero when there are lots of app sleeping/running/hibernating/whatever in the background. As soon as I kill off a few unwanted ones, all the menus scroll faster and home screens change quicker.
And this is not the placebo effect either. The menu's DO scroll more fluidly after I have killed a few apps, regardless of how you describe the RAM management...
Micksta said:
And this is not the placebo effect either. The menu's DO scroll more fluidly after I have killed a few apps, regardless of how you describe the RAM management...
Click to expand...
Click to collapse
exactly, you can tell easily if it is one motion or looks like it is "skipping frames". even it is only because it takes the device some cpu cycles to kill other apps, it does make a difference. like i said a rather cosmetic one, since it doesn't really effect the general usage. nevertheless i like to know what is running and what's not, and so far im running good with advanced task manager free.
WOW i didnt expect a massive response for my question but i thank you all for your responses
MercuryStar said:
I would wager that's the placebo effect. It feels faster because you believe it should. If you understand how the OS works you realise that apps you've switched away from do nothing to slow down or take memory from any other app (see my exception above about apps that launch background services such as music player).
Click to expand...
Click to collapse
that's not true, my phone gets so sluggish sometimes that i can't answer a phone call, the phone doesn't register that i press the answer button. and when that happends i usually have like 20 mb of free ram.
Daniehabazin said:
that's not true, my phone gets so sluggish sometimes that i can't answer a phone call, the phone doesn't register that i press the answer button. and when that happends i usually have like 20 mb of free ram.
Click to expand...
Click to collapse
Just as a matter of interest, do you use swapper or AppsToSD?
My phone never gets into the situation you've described, but even though I do have the full version of TasKiller, I almost never use it, and I don't see a need at present to use AppsToSD.
In addition, I'd imagine that having a swap partition would cause an issue with Androids own memory management, since I guess it can't distinguish between real and "virtual" memory. So where a "non-swap" device would start killing processes, a "swap" device would just continue on regardless because it thinks it still has physical memory available.
Regards,
Dave
Yesterday I downloaded "Advanced Task Killer Free"... anyone who has experiences with this? Is is better than just "Task Killer" or is it just an updated version of "Task Killer" ?
thanks!
have been using atk free for a while (lol 2 weeks since i got the hero) now, i really like it. its advantage over all other task managers IMHO: it has an ignore list, things you ignore are not shown in the running tasks list. in the list you have check boxes, where you can select the tasks that will be killed, and this list is remembered. for example "htc sense" is on my ignore list, but "music" is only checked, so i can uncheck it when i don't want to kill it while listening to music. next time i want to kill music i just have to tap the checkbox, no dealing with the ignore list here...
Daniehabazin said:
that's not true, my phone gets so sluggish sometimes that i can't answer a phone call, the phone doesn't register that i press the answer button. and when that happends i usually have like 20 mb of free ram.
Click to expand...
Click to collapse
I get this problem a lot, and in answer to fox meister, I don't have AppsToSD.
I don't know if the problem is RAM or CPU related, but the CPU often jumps to 100% when things are really slow.
Is the issue likely to be background apps, or widgets even?
Sausageman said:
I get this problem a lot, and in answer to fox meister, I don't have AppsToSD.
I don't know if the problem is RAM or CPU related, but the CPU often jumps to 100% when things are really slow.
Is the issue likely to be background apps, or widgets even?
Click to expand...
Click to collapse
Same for me with the processor.
When i reboot my phone i usually have 90 mb of free ram, after starting a few applications, like browser and phonebook, it plummets down to 20 mb.
I do have some extra applications that starts as services, like systray monitor and 3g watchdog.
when i open atk after a fresh reboot i see that some applications that i don't even use is started, like footprints, settings and calendar, even my webrowser is started, whats up with that, can it be disabled?
I think the issue is that we have some applications that autostart withous us using them, and also programs that we download that autostarts as services and maybe having memory leaks...
I came to chime in with my experiences of the CDMA hero and sluggishness.
I watch memory like a hawk (thanks Mogul) and I too have around 80-90mb free ram on start, but it can get down to around 30 rather quickly. Once it gets down here, I notice that screen transitions and random lag occurs in apps. If I go into Advanced Task Killer and kill many of the stragglers, my menus are as smooth as can be.
It is most certainly NOT a placebo effect.
One thing I really like about Advanced Task Killer (pay version) is that it has the "Auto End" feature, where it will kill all apps not chosen to be excluded at the interval that you choose. For example, I have determined the system applications that need to be on all the time, and I've excluded those. Every hour, ATK kills everything else. For the most part, my Hero hovers around 70MB now at all times, although it can get down there to around 30-40MB if I'm right around the 1 hour mark.
That feature alone makes it much better than Taskiller IMO. Totally worth 99 cents
This definition would imply that android works exactly like the iphone osx? I mean saving "screenshots" of the last state of an app. But NOT having real multitasking?
Because it's not possible to have multitasking and at the same time "inactive" background apps everytime you hit the home button...
MercuryStar said:
I'll attempt to sum it up once and for all, to try and set the record straight.
In Android's virtual machine, there is no functional differentiation between "closing" an app and "switching away from" an app. They are the same (the exception is things like music players which need to keep playing after you switch away from them, but even then only the 'service' part needs to keep running).
Whenever you switch away from an app, its current state is remembered so that even if it is effectively "killed" it can be returned to in just that state next time it's opened. Then Android either kills the process or it keeps it open, killing it when it needs the memory. You won't notice any difference between either scenario, except maybe that an app loads a little bit faster if it was kept in memory. At any rate, "closed" apps do not "run", and they do not take RAM or CPU cycles from other apps.
In terms of process/memory management, Android's VM has more in common with a web browser than a desktop OS - sure it can remember your state when you switch apps (like switching tabs, going back/forward/home in a browser) but whether behind the scenes it loads it all into and out of memory when you switch back and forth, or it all stays in memory is irrelevant to the user. Nobody worries that a long forum page on another tab or in their back button history is occupying 80 megs in the background or not, the browser takes care of loading/unloading it from RAM as needed, and that's just like how Android's VM works when switching between various pages of various apps.
Once you understand this you understand that all these 'task killer' apps are really unnecessary - all they'll do is make it slower to restart an app once closed. They don't reclaim RAM that was previously unavailable to other apps.
To cut a long story short, pressing "home" is a great way to close an app, whether you want to return to it later or not.
Click to expand...
Click to collapse
Shahpur.Azizpour said:
This definition would imply that android works exactly like the iphone osx? I mean saving "screenshots" of the last state of an app. But NOT having real multitasking?
Because it's not possible to have multitasking and at the same time "inactive" background apps everytime you hit the home button...
Click to expand...
Click to collapse
No, you've not understood the explanation.
The iPhone will always* terminate an application that isn't on its list of "approved" multi-tasking apps once it isn't active any more (i.e. you've switched tasks).
Android will try to keep whatever it can in memory, but eventually will start killing processes in order to keep the system running.
So, if you're on an iPhone listening to something on Spotify and you want to browse something on the web, the iPhone will "kill" Spotify when you switch to the web browser. On Android this won't occur except in the most critical of resource low situations, but then again, I'd imagine other apps would get killed before Spotify.
Read this article, specifically the section from "Component Lifecycles" onwards specifically "Activity Lifecycle", "Saving activity state" and "Processes and lifecycles".
Regards,
Dave
* Unless it has been jailbroken!
So I was told to only use the back button to leave an app when I'm done, which closes it so its not running all the time. I do that, but for some reason it doesn't quite work on some apps... for instance on the browser, if my wifi session dies while using my campus wifi, I have to force close the browser for it to automatically bring up the login page. And the app quickdesk also shows that the browser is always running. I shouldn't have to force close, and I hear bad things about other task killers... but it wont end itself. what to do?
Sent from my Motorola Atrix using the XDA App
So after a long browsing session you hit back back back back back back back until the browser closes.?. Or you force kill it. Do you have a particular reason why or your just following someone else's 'back out' preferences? I say there is no reason to end your browser, none. If you are playing a game, then yes there might be advantages to backing out opposed to hitting the "home" key. However, just this morning I was playing PvZ and hit the home key, no lag and two hours later I opened the game to the same spot and continued.
The Atrix manages tasks very well, much better than my Captivate for instance. For the most part it will background a task so its not burning up cpu/bat. I'm sure you may have noticed the task manager popup from time to time saying "the following app has been running 45 minutes, would you like to kill it?". If you are worried about what apps are burning up your cpu/bat, use Watchdog.
WiredPirate said:
So after a long browsing session you hit back back back back back back back until the browser closes.?. Or you force kill it. Do you have a particular reason why or your just following someone else's 'back out' preferences? I say there is no reason to end your browser, none. If you are playing a game, then yes there might be advantages to backing out opposed to hitting the "home" key. However, just this morning I was playing PvZ and hit the home key, no lag and two hours later I opened the game to the same spot and continued.
The Atrix manages tasks very well, much better than my Captivate for instance. For the most part it will background a task so its not burning up cpu/bat. I'm sure you may have noticed the task manager popup from time to time saying "the following app has been running 45 minutes, would you like to kill it?". If you are worried about what apps are burning up your cpu/bat, use Watchdog.
Click to expand...
Click to collapse
Yeah I usually don't have a problem. My problem is that I want the browser to end so that it can start up a new session next time. Like I said with the wifi login...Usually my browser is on the google homepage, so since it never ends it will always open up google again. Then when my wifi session dies, I open the browser so that the login page will show up, but just google tries to load because it's trying to 'remember' a previous session with the app. I realize what I'm trying to explain probably sounds really confusing lol sorry.
I am new to Android - just got a Droid 3.
How do I stop the system from auto-killing a certain app? When I play Angry Birds, if the phone goes to sleep on timeout, when I turn it back on, the App has to re-load from scratch (rather than opening to where I left off last time). I'm assuming the system decided to kill it for lack of memory, but how do I STOP it from doing that (like an ignore list)?
Will I need a third party app?
Any help is appreciated!
not really. the Android system does a pretty good job of reclaiming unused memory. ive been dealing with this for a while trying to keep a replacement lock screen in memory
Sounds like Verizon installed a task killer. I know their employees do that saying you need one. But you don't. Make sure you uninstall it. It is most likely set to kill apps off ever x minutes. Usually Android keeps foreground apps in memory for a long time unless the system needs it. But doesn't sound like it would. I wonder what the Droid 3 memory settings are for stock now. I have the Evo 3D and they are set at a higher threshold(as I'm kills unused apps sooner) compared to my older HTC phones(Evo and Hero). How long do you let the phone sit idle before coming back?
Sent from my iPhone with the bigger GeeBees.
notasimpleway said:
Sounds like Verizon installed a task killer. I know their employees do that saying you need one. But you don't. Make sure you uninstall it. It is most likely set to kill apps off ever x minutes. Usually Android keeps foreground apps in memory for a long time unless the system needs it. But doesn't sound like it would. I wonder what the Droid 3 memory settings are for stock now. I have the Evo 3D and they are set at a higher threshold(as I'm kills unused apps sooner) compared to my older HTC phones(Evo and Hero). How long do you let the phone sit idle before coming back?
Sent from my iPhone with the bigger GeeBees.
Click to expand...
Click to collapse
It's not obvious which program that would be - there's nothing called Task Killer. Plus, most of the VZW bloatware can't be uninstalled anyway. Apart from rooting (locked bootloader on Droid 3), what can I do to force it to stay open?
Also, it gets killed immediately on turning off the phone. As in, I start the game, hit sleep, hit wake a second later and the game reloads from scratch. Very irritating.
Any thoughts are appreciated, thanks!
jbroses said:
It's not obvious which program that would be - there's nothing called Task Killer. Plus, most of the VZW bloatware can't be uninstalled anyway. Apart from rooting (locked bootloader on Droid 3), what can I do to force it to stay open?
Also, it gets killed immediately on turning off the phone. As in, I start the game, hit sleep, hit wake a second later and the game reloads from scratch. Very irritating.
Any thoughts are appreciated, thanks!
Click to expand...
Click to collapse
I just tested this with Angry Birds from the time I posted till just now and it was right where I left the game. It may be called Advanced Task Manager. Or something like that. And you should be able to uninstall it. It would have been installed by the person selling the phone and not at the factory.
Sent from my iPhone with the bigger GeeBees.
Go to the Market, download Spare Parts. Open and scroll down to Activity/Process Management. Select normal. It may not have been the problem, but worth a shot. Are you hitting the home button before putting the phone to sleep? What do you see immediately upon turning the screen on and unlocking the phone? Angry Birds? The home screen?
Sent from my iPhone with the bigger GeeBees.
When you haven't used an app for a long time, Android automatically recycles all open activities from the app, except the root activity.
By default, every application runs in its own Linux process. Android starts the process when any of the application’s code needs to be executed, and shuts down the process when it’s no longer needed and system resources are required by other applications.
[...]
If the user leaves a task for a long time, the system clears the task of all activities except the root activity. When the user returns to the task again, it’s as the user left it, except that only the initial activity is present. The idea is that, after a time, users will likely have abandoned what they were doing before and are returning to the task to begin something new
Click to expand...
Click to collapse
From geekfor.me/faq/you-shouldnt-be-using-a-task-killer-with-android/ (sorry I can't make a link yet)
Shinigami20 said:
When you haven't used an app for a long time, Android automatically recycles all open activities from the app, except the root activity.
From geekfor.me/faq/you-shouldnt-be-using-a-task-killer-with-android/ (sorry I can't make a link yet)
Click to expand...
Click to collapse
it actually happens instantly. in other words - open angry birds, begin level. sleep phone, wake phone. angry birds reloads from the beginning. this is all within the span of 5 secs.
i thought it might be my lock screen - widgetlock, but i disabled that and it just happened again, this time with opera mini as i was writing this. I was writing this post, went to a text, came back to opera within 30 secs and it had shut down and reopened (no tab with my partially composed message).
is the droid 3 just shutting things down more aggressively? is there a way to tweak that? maybe too much other crap is running and I should get a task killer? thoughts?
jbroses said:
it actually happens instantly. in other words - open angry birds, begin level. sleep phone, wake phone. angry birds reloads from the beginning. this is all within the span of 5 secs.
i thought it might be my lock screen - widgetlock, but i disabled that and it just happened again, this time with opera mini as i was writing this. I was writing this post, went to a text, came back to opera within 30 secs and it had shut down and reopened (no tab with my partially composed message).
is the droid 3 just shutting things down more aggressively? is there a way to tweak that? maybe too much other crap is running and I should get a task killer? thoughts?
Click to expand...
Click to collapse
do not sleep your device, try entering level then return to home switch to other apps. Then open angry bird again and see what happen
On my desire Z, it kill the app every time i sleep the phone. Keep the phone alive then I have 3 apps running at same time without being killed. But it's not likely that I have RAM shortage. 3 apps is constant no matter what apps
Flipz explains that well. Autokiller is a great little app to adjust those settings. Used it for over two years now. I actually got to watch that app evolve. Great dev. Only works if you are rooted.
Shinigami20 said:
When you haven't used an app for a long time, Android automatically recycles all open activities from the app, except the root activity.
From geekfor.me/faq/you-shouldnt-be-using-a-task-killer-with-android/ (sorry I can't make a link yet)
Click to expand...
Click to collapse
Sent from my iPhone with the bigger GeeBees.
Thanks for all the responses. I've tried to address them all:
Spare Parts - I installed this and set the Activity to Normal (it WAS set on aggressive). Unfortunately, this didn't help.
Press the Home key - Pressing the Home key and then going back to Angry Birds DOES work. It picks up right where you left off. Unfortunately, when the phone goes to sleep, it restarts Angry Birds on waking.
What do I see when I wake the phone - It goes to my WidgetLocker lock screen. Once unlocked, the very first thing that shows up is the Angry Birds "Rovio" loading screen. No home screen in between.
Any other thoughts are much appreciated! Is there any way to simply exempt Angry Birds from being closed by the system automatically? It seems like this should be possible!
Can you try something out for me? I want to give evidence to my theory.
Download another 3d game, load a level, then sleep the device. See if there's a lot of stuttering/reloading when you wake the device back up.
Any news on this? I got the same problem with CM 9.1 on my Doubleshot (aka M4GS). When I have like 10 tabs or so opened in Opera, Android kills the task. But not when I put it into sleep, but right when I'm browsing! That's really annoying since after restarting Opera I have to reopen every single tab manually from the history.
Already tried Spare Parts, but it doesn't offer some kinda whitelist for apps that shouldn't be autokilled.
It's really frustrating, Android's autokilling feature was one of the few things, that I didn't like about that OS when I switched from Windows Mobile to Android a few years ago. And I still hate that feature. Why can't I decide by myself which apps to be closed and which ones not? Give back the power to the user I say!
At least there HAS to be a solution to force Anddroid, not to kill a specified app (e.g. Opera) and kill all the other running apps instead. Any 3rd Party task killer has some kinda ignore list, so how could Android be tweaked to do the same?
Shani Ace said:
Any news on this? I got the same problem with CM 9.1 on my Doubleshot (aka M4GS). When I have like 10 tabs or so opened in Opera, Android kills the task. But not when I put it into sleep, but right when I'm browsing! That's really annoying since after restarting Opera I have to reopen every single tab manually from the history.
Already tried Spare Parts, but it doesn't offer some kinda whitelist for apps that shouldn't be autokilled.
It's really frustrating, Android's autokilling feature was one of the few things, that I didn't like about that OS when I switched from Windows Mobile to Android a few years ago. And I still hate that feature. Why can't I decide by myself which apps to be closed and which ones not? Give back the power to the user I say!
At least there HAS to be a solution to force Anddroid, not to kill a specified app (e.g. Opera) and kill all the other running apps instead. Any 3rd Party task killer has some kinda ignore list, so how could Android be tweaked to do the same?
Click to expand...
Click to collapse
I agree. I was downloading a file in Opera, switched to other apps, then went back to opera and it reopened.. Needless to say the download failed. This really sucks.
Use titanium and freeze the stock task manager (if any).
Android, by default, keeps only 3 (correct me if I'm wrong) applications' sessions in memory, but that's obviously no reason for it to kill angry birds right after the display is closed.
Try installing Minfree (I think it's available on the Play Store) to understand when and why Android is killing the application. It'll give you the parameters on which the Android Auto killer operates, but you will need ROOT to be able to edit them.
And no, there isn't a way to earmark an application such that it isn't killed, at least, not that I know of.
Hope this helps.
Haters gonna hate
potatoes gonna potate.
Check out v6 supercharger and all ur questions will be answered.
http://forum.xda-developers.com/showthread.php?t=991276
sent from my DNA
jbroses said:
I am new to Android - just got a Droid 3.
How do I stop the system from auto-killing a certain app? When I play Angry Birds, if the phone goes to sleep on timeout, when I turn it back on, the App has to re-load from scratch (rather than opening to where I left off last time). I'm assuming the system decided to kill it for lack of memory, but how do I STOP it from doing that (like an ignore list)?
Will I need a third party app?
Any help is appreciated!
Click to expand...
Click to collapse
Hi, excuse me for not reading other posts and replying directly but wanted to share something that works for me and does not kill certain launched apps. Open any app, then come out of the app and tap on recent apps button and you will see the apps that are currently launched. Depending on your OS and model, are you able to lock an app (by slightly dragging the app icon down and then tapping on the lock icon). I did that for one of the games and surprisingly even after several minutes, I was able to continue from exactly where I left off. Hope this helps. Let me know.
Screenshot: http://1.bp.blogspot.com/-9Bs7dxj7t3o/VZHLFAF6fdI/AAAAAAABI0Q/WXFhUv1c2gw/s1600/IMG_0023.JPG
Hello to all!
I have been browsing the forums for quite some time and now i finally decided to create myself an account, though i don't have enough experience to help most people with android, i do believe that maybe the questions i make might help other people as well.
My first Post and Question would be because of the following problem:
My internet is actually very slow where i am now, and it takes quite some time to download heavy games such as Modern Combat 3, Need for Speed, Mass Effect, and many others around, being so, i usually leave them on background and try to do something as i don't want to just be sitting there staring to the screen, but if i do so, after some time i come back to the app and it simply had stopped downloading, usually gets back to the splash screen, and asks to download it all again, even some apps such as Modern Combat, that keeps an icon in the tray indicating that it is still active behaves like that, or even sometimes instead of stopping the download it rollbacks the progress, once while watching the downloadbar i saw it drop from 220+ mb to about 140mb for no apparent reason and no heavy applications on background.
Do any of you know the answer to this sort of problem?
I would like to add that the app is not sleeping, nor is my device, i have an asus transformer prime tf201 tablet, running ics 4.03, rooted, with the keyboard dock.
And checking from the asus task manager, the programs even on multitasking with games generally don't seem to consume more than half the available ram.
Sorry for the long post and thank you very much for reading!
Hey guys,
For me the Google Assistant is deteriorating in experience. In the early days of the phone it worked awesome, so well that I could actually use it with screen turned off with all of its functionality. But later more on MiUi 10 and pie updates it has gone to gutters.
1. Forget screen turned off or lock screen, now it doesn't even respond to 'ok Google' from home screen.
2. It doesn't respond even on the Google feed page.
3. I need to use GA from headphone as I ride bike sometimes. Everything used to work. Now when I tell it 'navigate to XYZ', it says I don't know how to help with that.
4. When I say 'send WhatsApp message to XYZ', it says I don't know how to help with that.
5. I ask 'play music' it says 'you need to unlock your device in order to do that.' but if I say 'play coldplay', it'll actually start playing songs on Google music
6. When I say 'what's this song' which is the feature we use to identify the song playing in the background, it says 'it's not capable of doing so yet.
7. Sometimes while saving reminders, it still keeps asking me what to save or when to remind even though I mentioned everything already.
Everything above used to work absolutely fine. It seems to me either Xiaomi or Google is restricting GA. And no I don't have any weird stereotypical accent. Have you guys observing what I'm observing?