As discussed in a specific thread, ICS is not managing the car mount supply power that, by activating the "car mode" (basically voice commands and phone calls in horizontal), causes ICS phone application to crash and the system crashes completely!!!
I tryed closing the voice commands interface (opened authomatically when connecting the power supply in the car mount) but that is not enough and the phone crashes at the first phone call or bluetooth stereo audio interaction
While waiting for a fix in ICS, I was wondering if the community here knows how to avoid that the "car mode" is activated, as a temporary turn around
The issue, you can imagine, is that we cannot charge the battery in the car mount, critical for instance while using the navigation app that drains battery!
dengi_it said:
As discussed in a specific thread, ICS is not managing the car mount supply power that, by activating the "car mode" (basically voice commands and phone calls in horizontal), causes ICS phone application to crash and the system crashes completely!!!
I tryed closing the voice commands interface (opened authomatically when connecting the power supply in the car mount) but that is not enough and the phone crashes at the first phone call or bluetooth stereo audio interaction
While waiting for a fix in ICS, I was wondering if the community here knows how to avoid that the "car mode" is activated, as a temporary turn around
The issue, you can imagine, is that we cannot charge the battery in the car mount, critical for instance while using the navigation app that drains battery!
Click to expand...
Click to collapse
Though have never used the car mode/mount but you can freeze it using Titanium Backup if you have root.
abhisahara said:
Though have never used the car mode/mount but you can freeze it using Titanium Backup if you have root.
Click to expand...
Click to collapse
I see, thanks. My doubt is if indeed "car mode" is managed by an app that we can kill/freeze or instead is just a sort of "system configuration" activated by the car mount chip
Well as i told earlier haven't used it so never looked into it. But the car mount gives the system a signal (yeah the pin connectors position should be different...look inside your normal usb connector and the the car dock connector...they should have the pins placed differently...) that the phone has been docked to the car and hence the CarHomeGoogle.apk gets activated. So if you freeze this app the system will still give the command to activate the app but since its freezed it wont run.
I might be total wrong.....but just what i thought!! Never experienced it so learning it
Your advice makes a lot of sense. I didn't know the name of that apk, it might be the one to be freezed!
I just asked in the specific thread here if somebody else can give a try, as at the moment I have not got root rights on my ICS... let's see!!
Thank you very much for your advice!
Try this:
Install this app
https://play.google.com/store/apps/details?id=com.megagram.docknoop
and set as default when you insert in car dock.
Related
Hello Guys,
before Froyo it was possible do "disable" the Car mode by deleting the CarHome.apk.
But since Froyo, if you delete this apk, the Phone still switches to CarMode in the CarDock....
And maybe thats a reason for the loudness problem in the Cardock...
Does anyone know how i can disable the Carmode Completely?
thanks a lot
Install "dock nothingness" from market.
Also you have posted in the wrong forum. If it is a question, it goes to Q&A forum.
ive noticed as well, since 2.2 i havent been able to adjust the audio when it is docked in the car, is that just me? I use audiomanagerpro but i also tried to adjust the media volume from the settings menu as well
I'm so happy to KILLED the evil Car Mode - here's how
Car Mode would pop up constantly on my HTC Incredible 2. It had nothing to do with the usb. Most times, the phone wasn't even plugged it and Car Mode would still pop up and Yes, I could click on it and disable it. For about 5 secs, then it was back. The worst part was that it would force-close the program that I was in to launch. It took me about 8 hours of research. Car Mode is a system app, and therefore can not be removed like other applications. You have to root your phone then delete, freeze or rename. Ok by me, but rooting apparently isn't stable yet for the Incredible 2 if you have a later os version than 2.2. Guess what? I have 2.3. No problem, how do i revert. Oh, i find out, you can't without resetting the phone to factory, which by the way is what verizon support suggested. I thought not before I back up, but lo and behold you can't back up more than contacts and pics without rooting. Arrrrgh! Next, I looked for an app to help me battle this devil Car Mode, so I tried apps from Amazon and market:
Advanced task killer Free
Astro
Gemini App Manager
Dock Nothingness
Dock no-op
Disable car home
and NONE of them worked, at least not for the Incredible 2.
I had a new idea, if you can't beat them, join them so I installed the latest version of Car Dock Home, hoping that at least it would give the option to not launch. Nope, didn't work. Luckily, I'm good at my job just because I don't give me 'easily'. Anyway, finally on my 14th try, I used 'DockNothing Free' from Amazon. At first, I didn't think this worked either. There was no input screen or settings but that's because the app doesn't initiate until the Car Mode launches, then it allows you to choose to select DockNothing as the default program. I had to do that 3 times: 1) Car Panel 2)Car Dock 3)Home Dock. Now I actually see a little popup that says 3 tasks killed. YEA!
Sorry for the long post, but I'll bet if you're here, you are going crazy because of Car Mode. And I read a lot more than just this much to get mine fixed.
ps. Car Mode actually looks pretty neat and seems useful IN THE CAR. But I have been too afraid to release the monster to check it out. I might at the next update. Might....
interesting, i love car mode in the car, no idea why yours is coming up while not in one lol
patience, htcdev website just released the unlock bootloader over the web for the uk sensation today, should probably hit for the other htc phones soon
Im having the same issue here on a desire z.. The Dock nothingness and simmilar applications doesn't help with the "car mode" at all
it just replaces the "Car Home" App
It's the "Car Mode" that is the problem for me atleast.
when the phone enters/exits car mode the phone always returns to the homescreen.
Any progress on disabling this?
I got rid of it on my Desire by adding a shortcut to the homescreen and choosing Settings > Car Dock and then unticking Auto Launch. I never saw car mode again so it either fixed it or it was a coincidence.
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
This is sort of a dumb questions but is there any preferred order when using Android Auto to turn the car radio off? What I mean is should I unplug the USB from my phone first when Android Auto is active, or should I shut the car down (radio turns off), then unplug my phone, or does it not matter?
It took a while to get my Android Auto to work, I just kept trying and it looks pretty cool. I'm using a AVIC-8100NEX with a Sony Xperia Z3 compact unlocked running 5.0.2. The only bug I've had is for some reason, my phone lost the bluetooth pairing with my radio after the 3rd time I used Android Auto. I never had this problem before with this phone or radio during normal use. I was curious if it was the way I shut it off.
Thanks for any help
Jason
For me, it seems best to turn off the car then unplug the phone.
But here, it is much more important how you connect than disconnect. If I turn on bluetooth on the phone, start the car and wait for bluetooth to connect, and then plug it in, everything works fine. But if the phone is plugged in before the NEX is on, it will create a new pairing in favor of the old one. And sometimes it will delete the pairing entirely.
Weird.
Solutions Etcetera said:
For me, it seems best to turn off the car then unplug the phone.
Click to expand...
Click to collapse
You didn't mention a reason, but I think safety is a valid reason to turn car off first.
Once the car is safely parked, and the engine (or hybrid or EV ECU) is safely off, THEN you can pick up the phone and unplug it.
This order should also be the most provably legal method in the many locales where phone use/distracted driving laws are active.
This order could also be advantageous for minimizing power spikes and tiny little sparks on the power connectors.
Logically, with all software working as it should, there should be no software preference. It's a disconnection to the still running phone either way. I've noted no difference except that Android Auto might run a little longer before it crashes itself to sleep or otherwise terminates.
Android Auto supports a "Byebye" request packet and a response packet. Shutting the headunit down gives it an extra second to do cleanups like this.
All of this seems to support "Power off car or HU, then unplug" as a good habit.
But if something crashes (HU or AA software), or you want to switch phones while "hot" (which nobody has ever mentioned that I've read) it might be less distracting to yank and replug, which of course should only be done when it's safe to do so.
Solutions Etcetera said:
For me, it seems best to turn off the car then unplug the phone.
But here, it is much more important how you connect than disconnect. If I turn on bluetooth on the phone, start the car and wait for bluetooth to connect, and then plug it in, everything works fine. But if the phone is plugged in before the NEX is on, it will create a new pairing in favor of the old one. And sometimes it will delete the pairing entirely.
Weird.
Click to expand...
Click to collapse
Wow, I've been searching everywhere for someone with the same issue as me and tried figuring out why my phone keeps (intermittently) forgetting my car as a bluetooth device after I've connected it to Android Auto. I will be testing out your suggestion, thanks beforehand though, I never would've guessed it had to do with the order you connect it in, rather than disconnect.
mrnmukkas said:
Wow, I've been searching everywhere for someone with the same issue as me and tried figuring out why my phone keeps (intermittently) forgetting my car as a bluetooth device after I've connected it to Android Auto. I will be testing out your suggestion, thanks beforehand though, I never would've guessed it had to do with the order you connect it in, rather than disconnect.
Click to expand...
Click to collapse
My comments were based on using AA with a Moto X. Now that a Nexus 6P is my daily driver, I just plug it in, make sure it is unlocked, and start the engine. I don't even turn BT on anymore as AA does that automatically.
No issues this way in over a week. Nice to be Nexusing again!
Solutions Etcetera said:
My comments were based on using AA with a Moto X. Now that a Nexus 6P is my daily driver, I just plug it in, make sure it is unlocked, and start the engine. I don't even turn BT on anymore as AA does that automatically.
No issues this way in over a week. Nice to be Nexusing again!
Click to expand...
Click to collapse
Odd, I've been having these issues first with my Nexus 6 and now Nexus 6P. It just sometimes removes my car from the saved bluetooth devices list and the next time I get in the car it demands to be paired again. Anyway, I'll try your solution and report back.
Alright, so I tried letting the bluetooth connect and then plugged in the cable, unfortunately that still made my phone forget about the car as soon as I disconnected it.
However, your last message got me thinking, maybe I'm overcomplicating this. I've noticed that the phone indeed does get connected to bluetooth, regardless of whether I pair it if/when it prompts me or not, Android Auto does seem to handle the pairing by itself.
I've only once noticed that the phone actually failed connecting and that was with my Nexus 6 which always felt like it had a wonky bluetooth. That time I couldn't place a call with the car handsfree, or even start the "phone app" on the Auto screen. So far the phone app has never refused to work on my Nexus 6P, regardless of if I skipped the pairing request.
So the best method I've found is to plug the phone to the USB before starting the car, this way it doesn't even prompt me to make a bluetooth connection, it just starts Android Auto right away and does the pairing automatically.
The only nuisance with this solution is that I get a new Smart Lock notification every time the phone connects, but I guess I can live with that (though it's not very elegant).
mrnmukkas said:
The only nuisance with this solution is that I get a new Smart Lock notification every time the phone connects, but I guess I can live with that (though it's not very elegant).
Click to expand...
Click to collapse
Yeah, I've seen that with all my phones. Be nice to turn that off but haven't found a way short of completely turning off smartlock.
Would this imply that you are alone? Here is the reason for my question:
Pull into the train station, Wife will be driving the rest of the way to work. I unplug my phone because i take it with me. HU goes back to Main Menu, she plugs her phone in and says "Play Music" ,she then drives to work listening to her own music. I dont think using AA should force us to power off the car before unplugging. We do this scenario everyday and have never had an issue. Just wanted to throw that into the conversation.
mikereidis said:
You didn't mention a reason, but I think safety is a valid reason to turn car off first.
Once the car is safely parked, and the engine (or hybrid or EV ECU) is safely off, THEN you can pick up the phone and unplug it.
This order should also be the most provably legal method in the many locales where phone use/distracted driving laws are active.
This order could also be advantageous for minimizing power spikes and tiny little sparks on the power connectors.
Logically, with all software working as it should, there should be no software preference. It's a disconnection to the still running phone either way. I've noted no difference except that Android Auto might run a little longer before it crashes itself to sleep or otherwise terminates.
Android Auto supports a "Byebye" request packet and a response packet. Shutting the headunit down gives it an extra second to do cleanups like this.
All of this seems to support "Power off car or HU, then unplug" as a good habit.
But if something crashes (HU or AA software), or you want to switch phones while "hot" (which nobody has ever mentioned that I've read) it might be less distracting to yank and replug, which of course should only be done when it's safe to do so.
Click to expand...
Click to collapse
BPryde said:
Would this imply that you are alone? Here is the reason for my question:
Pull into the train station, Wife will be driving the rest of the way to work. I unplug my phone because i take it with me. HU goes back to Main Menu, she plugs her phone in and says "Play Music" ,she then drives to work listening to her own music. I dont think using AA should force us to power off the car before unplugging. We do this scenario everyday and have never had an issue. Just wanted to throw that into the conversation.
Click to expand...
Click to collapse
In the end, I don't think it's a big deal to worry about order, unless one method crashes or has other bad results.
The reasonings I gave are IMO rather tiny, and "split some hairs", just to come down in slight favor of one order over another.
Do whatever works for you and save your worry for the bigger issues in life...
New hybrid or electric drivers may ask "How do I drive it". Answer: just like any other car or however suits you.
mikereidis said:
You didn't mention a reason, but I think safety is a valid reason to turn car off first.
Once the car is safely parked, and the engine (or hybrid or EV ECU) is safely off, THEN you can pick up the phone and unplug it.
This order should also be the most provably legal method in the many locales where phone use/distracted driving laws are active.
This order could also be advantageous for minimizing power spikes and tiny little sparks on the power connectors.
Logically, with all software working as it should, there should be no software preference. It's a disconnection to the still running phone either way. I've noted no difference except that Android Auto might run a little longer before it crashes itself to sleep or otherwise terminates.
Android Auto supports a "Byebye" request packet and a response packet. Shutting the headunit down gives it an extra second to do cleanups like this.
All of this seems to support "Power off car or HU, then unplug" as a good habit.
But if something crashes (HU or AA software), or you want to switch phones while "hot" (which nobody has ever mentioned that I've read) it might be less distracting to yank and replug, which of course should only be done when it's safe to do so.
Click to expand...
Click to collapse
I have had the opposite experience in my 2016 VW gti. I have to unplug before shutting the car off.
With 3 different HTC(m9, a9, 10) phones, and the galaxy s7, if I turn the car off before unplugging I will have to pair the phone again. AA will auto pair it, but I still have to give the car message access and dismiss the new smart lock notification.
Old but relevant thread
I am using a Samsung A8 with a 2019 Subaru HU. I too have been having success with unplugging the USB cable first before turning off the radio/engine. Without power to the USB port as on turning off the engine, it seems to mess with the handshake randomly. For now, every time I stop and park I pull the cord first. Seems to better handle the disconnect better, but time will tell.
Wilbour said:
I am using a Samsung A8 with a 2019 Subaru HU. I too have been having success with unplugging the USB cable first before turning off the radio/engine. Without power to the USB port as on turning off the engine, it seems to mess with the handshake randomly. For now, every time I stop and park I pull the cord first. Seems to better handle the disconnect better, but time will tell.
Click to expand...
Click to collapse
I rarely do this because I am lazy. But for me the best way to disconnect is to pull the notification that is telling me that android auto is connect to my phone and then touching the option to disconnect it. Sometimes when i simply disconnect the USB the android auto app on my phone complains about a connection error code xxx (I forgot the exact code)
Hey! I haven't figured this out yet but, when you attach your moto to the Incipio Car Moto Mod Dock, it automatically puts it in Android Auto mode. Personally, I hate Android Auto, but I can't figure out a way to stop it from automatically launching. I've tried just deleting Android Auto, but it makes it so you have to click multiple notifications every single time you dock it to turn it off. Has anyone had any luck disabling this?
I don't think you can do it through any built-in means. I personally like that it goes into Android Auto when attached, and immediately exits when disconnected, but I do wish there was more control - specifically to start playing Google Play Music automatically when connected too.
It would be really sweet of Motorola made a suite of controls for Moto mods, that would allow more customization. Like when a certain mod is attached I get to choose what, if anything, is launched automatically.
That said, I'm totally happy with the car-dock, even considering how stupid-expensive it was to get it here in Canada.
Caldair said:
I don't think you can do it through any built-in means. I personally like that it goes into Android Auto when attached, and immediately exits when disconnected, but I do wish there was more control - specifically to start playing Google Play Music automatically when connected too.
It would be really sweet of Motorola made a suite of controls for Moto mods, that would allow more customization. Like when a certain mod is attached I get to choose what, if anything, is launched automatically.
That said, I'm totally happy with the car-dock, even considering how stupid-expensive it was to get it here in Canada.
Click to expand...
Click to collapse
I definitely agree, I LOVE the dock, I just am not a fan of Android Auto, so as a result, I have to exit out of it every time I dock my phone which gets annoying :/
holabola said:
I definitely agree, I LOVE the dock, I just am not a fan of Android Auto, so as a result, I have to exit out of it every time I dock my phone which gets annoying :/
Click to expand...
Click to collapse
What about to uninstall or disable Android Auto if you don´t use it at all.
A YouTube video this week said that the latest MZP Nougat upgrade added the ability to turn Car Mode off. You have to go into the settings while the Car Dock mod is attached. I haven't tried it yet as I like Android Auto auto-launching.
Search Youtube for "Incipio Car Dock Mod update.."
sonex293 said:
A YouTube video this week said that the latest MZP Nougat upgrade added the ability to turn Car Mode off. You have to go into the settings while the Car Dock mod is attached. I haven't tried it yet as I like Android Auto auto-launching.
Search Youtube for "Incipio Car Dock Mod update.."
Click to expand...
Click to collapse
I confirm that. I'm on Nougat and when attached to Moto dock I see option to uncheck auto launch Android auto when attached to dock. As it doesn't work in Poland where I live it was useless future for me.
I can confirm now as well. I'm beyond happy. This was pretty much my only gripe I had with my phone and it's fixed. This is the best.
One strange problem I am having with the Incipio Dock is with audio. I am connecting to my car stereo via Bluetooth and my car is not Android Auto compatible. If I plug into the dock, Android Auto launches and Google Play starts playing MP3 but I have to hit a volume button to hear the audio. Just a single tap is all it takes. If I leave the phone in my pocket, the file starts just fine. Haven't found a fix yet.
Sent from my XT1635-02 using Tapatalk
Pioneer Android Auto head unit
Does anyone know if this will work the same as plugging in the USB cable to launch on compatible head unit? I know it's not much more seamless than plugging in a cable but would save wear and tear on the phone port over the life of the device...and look cooler.
aia832003 said:
Does anyone know if this will work the same as plugging in the USB cable to launch on compatible head unit? I know it's not much more seamless than plugging in a cable but would save wear and tear on the phone port over the life of the device...and look cooler.
Click to expand...
Click to collapse
That's exactly what I'm trying to do: dock my Z3 Play to the Incipio Car Dock, which is plugged into my Andriod Auto compatible head unit so I can use Android Auto on my head unit.
Despite all my efforts, whenever I dock my phone, it either launches the Android Auto interface on the phone, or optionally doesn't automatically launch the Android Auto interface on the phone - but in either case, my head unit doesn't detect that an Android device has been connected via USB.
#frustrating
- www.JoeLevi.com
The USB-C port on the dock is for charging only. No data transfer. Does it work if you connect using the USB-C port on the phone instead of the dock?
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.