Android auto process explorer/killer? - Android Auto General

Greetings,
Is there an app that I can use while in Android Auto to view and kill processes from the head unit?
I'm tired of having to disconnect my phone, kill the app on my phone and then reconnecting.
Thanks!

same here, having to kill off Waze the odd time, getting annoying.
One thing I noticed with AnyAutoStream installed, i can now access the phone and any app without having to unplug the phone from the headunit. At least this allows me to force stop the app.
https://www.xda-developers.com/play-music-from-any-app-on-android-auto-with-anyautoaudio/

Related

[Q] Car mode and Google maps since last update

Good morning. I have been having a particular, repeated issue since the last google maps update (7.0.2). Whenever I get into my truck I put my One in the OEM dock and it goes into "car" mode. Overall I love this app and find it incredibly efficient at doing its job.
However, since the last update from Google maps (which is also pretty indredible) I have been having a very specific error, that I believe is related to HTC's car mode. If I start navigation though the car dashboard and some event happens that pulls it from navi to the dashboard (i.e. a call comes in or a message) then when I return to navigation it again asks me to select the destination and I have to hit start. This will cause a "maps stopped working" error about 75% of the time.
What I believe is happening is that maps is already navigating but when in car mode you have to click on the "navigation" icon to get back to it, and it tries to launch another instance or over itself. This will also happen if I start navigation while not docked (i.e. walking to my truck) and docking, then launching the app. Also, maps is the one app that actually leaves car mode (you can see the system tray and then navigate to other non car mode apps) and I believe this is the root of the issue.
Since the car mode is (I believe) part of Sense, this would seem to be something specific to this. I thought there would be lots of inquiries into this but could find none. Thoughts?
I'm getting this too. It's deeply annoying and quite dangerous when going down the motorway. Considering going back to previous version.
Sent from my HTC One using xda app-developers app
It's an issue with the new Maps app. It sucks balls. I have those issues and I don't have the car dock.
Take a call or something else then when you try to go back to nav by selecting it from the notification panel, it does nothing or crashes or takes you to regular map and have to restart your route.
I hate it. It's pretty but so buggy. I reloaded the old version.
Sent from my HTC One
HTC car mode and Google maps
I am also having same problem. UN installed update and gone back to the much better old version

Google Play Music on 5.1.1

Since upgrading to 5.1.1, Google Play Music keeps mobile radio active even after I stop listening to streaming music. About an hour after I stop the music and exit from the app, I get a warning from Stamina Mode indicating that GPM is preventing the phone from sleeping. When I check the usage statistics, it shows that GPM is the biggest drain on my battery. The only way to stop this is to force close the app from the app manager, but then it starts again the moment I try to use it (which is daily).
Does anyone else have this issue, or at least know how to prevent GPM from keeping mobile radio active when not in use?
Problem solved. There was a bug preventing the phone from sleeping when WiFi was enabled. Changed the advanced WiFi setting to stay active only when plugged in and now the phone sleeps properly and Google music behaves as it should.
Sent from my D5803 using XDA Free mobile app

Android stops sending Notifications to Pebble Watch after time.

I have a Pebble Classic smartwatch (I know, old, unsupported, and discontinued) and a Huawei Honor 6X. My Pebble watch is able to pair and receive notifications fine. After some time, it stops receiving notifications. Sometimes after 5 minutes or even an hour. It doesn't re-sync till I disconnect it via the Pebble app (or settings on the watch) and then reconnect it. After that, it begins the process over by staying in sync after some time then stops receiving notifications.
Also, a strange thing I notice is it syncs in the morning when I wake up just fine without having to do anything.
When it stops receiving notifications both devices say they're still paired.
I have tried forgetting the device and then reconnecting. I have checked that my Pebble app isn't in the lock-screen cleanup list for the Huawei management. The Pebble app has Permissions to notifications. I do have the persistent notification within the Pebble app enabled. This happened before the Pebble servers went down and even after switching to Rebble. I do have Google Wear OS installed. Should I try using GadgetBridge?
My brother has the exact same watch with his iOS device and it works flawlessly.
Phone: Huawei Honor 6x Android 7.0
Pebble: v3.12.3
Is there something happening with the phones Bluetooth connection? Is it the Android operating system putting the app into sleep or something. Is it going into power save mode or something? If rooting my phone will provide a fix I am willing to do so.
phcreery said:
I have a Pebble Classic smartwatch (I know, old, unsupported, and discontinued) and a Huawei Honor 6X. My Pebble watch is able to pair and receive notifications fine. After some time, it stops receiving notifications. Sometimes after 5 minutes or even an hour. It doesn't re-sync till I disconnect it via the Pebble app (or settings on the watch) and then reconnect it. After that, it begins the process over by staying in sync after some time then stops receiving notifications.
Also, a strange thing I notice is it syncs in the morning when I wake up just fine without having to do anything.
When it stops receiving notifications both devices say they're still paired.
I have tried forgetting the device and then reconnecting. I have checked that my Pebble app isn't in the lock-screen cleanup list for the Huawei management. The Pebble app has Permissions to notifications. I do have the persistent notification within the Pebble app enabled. This happened before the Pebble servers went down and even after switching to Rebble. I do have Google Wear OS installed. Should I try using GadgetBridge?
My brother has the exact same watch with his iOS device and it works flawlessly.
Phone: Huawei Honor 6x Android 7.0
Pebble: v3.12.3
Is there something happening with the phones Bluetooth connection? Is it the Android operating system putting the app into sleep or something. Is it going into power save mode or something? If rooting my phone will provide a fix I am willing to do so.
Click to expand...
Click to collapse
You can try to exclude the app from androids Power saving. Also gadgetbridge can be tested(I'm using it with my PTS).
I tried gadget bridge and that does the same thing. Also I have it removed from my power management, nothing. I downloaded an app that supposedly keeps the Bluetooth alive. I'll give that a go.
I found a workaround.
I installed an app called BluetoothKeepActive and that seemed to fix the problem. It seems that my presumption was correct. The Bluetooth is going into standby mode or power management mode or something.
phcreery said:
I found a workaround.
I installed an app called BluetoothKeepActive and that seemed to fix the problem. It seems that my presumption was correct. The Bluetooth is going into standby mode or power management mode or something.
Click to expand...
Click to collapse
Seems to be an kernel issue of your phone imo.

Possible fix for constant AA crash

I recently started getting a lot of AA disconnects from my Samsung phone and my AA stereos - I have an Android Chinese unit as well as a Kenwood Excelon in my second car. Thought the cable might be the issue but that didn't seem like it.
I went in to the apps menu and found that under system apps, there are 2 more AA related apps. Proceeded to turn off battery optimizations for all 3 and now it seems to be running stable.
The apps are:
Android Auto (DUH!)
android.auto_generated_rro_product__
android.auto_generated_rro_vendor__
You're the f'ing man! I could kiss you.
Didn't work for me.. only fix I have found is tap the usb options [while plugged in] on phone and tell the phone that the plugged in device manages connection.. unfortunately this setting does not remain set after use.

Question Android auto heating up the device

Whenever i plugin my s21 ultra to my kia seltos for android auto ,
Even on idle without the music playing / navigation the phone heats up like crazy .
I have tried resetting the infotainment on my car as well as the android auto app on my s21 ultra but nothing gets better .
Anyone can help out ?
It heats for me FWIW...I was initially fascinated by android auto but considering the damage it does to the battery I seldom use it...
I don't find mine heating up more when using AA, but I use it wirelessly. Now, my headunit is an Android powered one, so we're comparing apples to oranges, but on on the phone it should be the same.
What I don't like is that lately AA started to control the headunit beyond what it used to : turns on BT and WiFi all the time, because the headunit stays in low power mode for a while after turning off the engine, I find myself at home getting calls and audio gets routed to the car despite me being inside.
I gave up on it....
aj7400 said:
Whenever i plugin my s21 ultra to my kia seltos for android auto ,
Even on idle without the music playing / navigation the phone heats up like crazy .
I have tried resetting the infotainment on my car as well as the android auto app on my s21 ultra but nothing gets better .
Anyone can help out ?
Click to expand...
Click to collapse
I have yet to test it out however will do so . I did check on play and they have a beta programme which is currently full. Maybe use a service like APKMirror to try the beta? See if that fixes your issues
Try clearing system cache.
Disable all power management... destroyer of worlds.
Try using the factory load version of the apps causing trouble.
Parent apks, dependencies... the apk causing the trouble may not be the obvious one
Check memory and individual battery usage to help isolate the apks causing trouble.

Categories

Resources