Hi.@Emil Borconi, @mikereidis
Hi guys, I'm much interested in something opposite you obviously did - a custom companion application that will mirror whole android screen/sound/keys/touches into head unit already working with original Google AA. Are you working on something like this? (I did post a thread here: http://xdaforums.com/android-auto/a...ustom-apps-screen-cast-t3509788#post69884046)
Ouch, a pity... About Mike :/.Hi.
Mike is not between us for a while now, he sadly went to a better place.
As of myself, no I have no intention on working on anything like that, I think there is still loads to be done with the current app so when I have time I like to focus on this.
What you are trying to create is quite tricky, not sure if possible or not.... More probably not than yes, and it will need rooted phone for sure, this is just at a very quick run trough the idea.Ouch, a pity... About Mike :/.
Hmm. Can you at least help someone else to make such a thing? I guess your knowledge of protocol would be a key to do it.
What you are trying to create is quite tricky, not sure if possible or not.... More probably not than yes, and it will need rooted phone for sure, this is just at a very quick run trough the idea.
You need to create an app which respond to the headunit that same way android auto does, it needs to do an ssl handshake as well. This in theory can be achieved, it than needs to record and encode the screen and send it to the headunit, this again is possible. After that it needs to process the touch inputs from the headunit and inject them to the phone and this is not possible outside your own app unless you are root. Chinese headunits have a screen mirror solution but that uses adb to insert the touches, and that is allowed.
If you want screen mirroring than probably you should opt for a cheaper Android powered headunit which already offers that, trying to come up with a replacement for android auto on their protocol sounds wrong.... Not saying I won't help if somebody starts the project but o don't see the scope of it at all...
You can click anywhere in your own app, while the activity is on top, but when your activity is in background it's not possible any longer.Scope is simple - to get the factory built in head unit (ie Opel car) to work freely, not under Google restrictions. Making custom head unit was possible much before Google even invented AA. I even started to put a live notepad as my dash linux onboard, lol (way before tablets). I just want to use the hardware of original head unit to my needs.
I get the idea. You simply say that the hardest part is to force source android to listen to the HU. Point taken. But since apps like "Automate" can "click" anything on the screen gaining the "accessiblity" rights, it should still be possible even without root. I'm not sure what I'm talking about as I never digged this topic (as clicking know UI element may be easy, clicking the point on the screen can be a problem if there's no interface for that), but maybe there's hope.
I assure you, it's possible. I have flows made by myself in Automate which are clicking buttons, sections, menu items whenever other app appears on the screen. It would make no sense to make accessibility interface in android framework which can only click itself. Automate has a background service which operates thru accessibility interface.You can click anywhere in your own app, while the activity is on top, but when your activity is in background it's not possible any longer.
Yes accessibility does go e you some options... Never explored them to be honest.I assure you, it's possible. I have flows made by myself in Automate which are clicking buttons, sections, menu items whenever other app appears on the screen. It would make no sense to make accessibility interface in android framework which can only click itself. Automate has a background service which operates thru accessibility interface.
I wanted to do something similar with my OEM unit until someone smashed my window and made off with the radio.Scope is simple - to get the factory built in head unit (ie Opel car) to work freely, not under Google restrictions. Making custom head unit was possible much before Google even invented AA. I even started to put a live notepad as my dash linux onboard, lol (way before tablets). I just want to use the hardware of original head unit to my needs.
I get the idea. You simply say that the hardest part is to force source android to listen to the HU. Point taken. But since apps like "Automate" can "click" anything on the screen gaining the "accessiblity" rights, it should still be possible even without root. I'm not sure what I'm talking about as I never digged this topic (as clicking know UI element may be easy, clicking the point on the screen can be a problem if there's no interface for that), but maybe there's hope.
Do I get it right that mimics is mimicking android auto companion for the car head unit while making full mirroring with android without any need of hacking the protocol?I wanted to do something similar with my OEM unit until someone smashed my window and made off with the radio.
I was looking into this unit for touch and a lockpick device for video.
http://www.customgadz.com/
Do I get it right that mimics is mimicking android auto companion for the car head unit while making full mirroring with android without any need of hacking the protocol?
Ok, so this is no help to me. I want to do this without any interference into the car's hardware (especially it is a new one still on warranty). But thanks for trying .The mimics is a hardware solution to gain control of touchscreen inputs and relay them to phone via Bluetooth. It is achieved by physically opening the unit and connecting "in-line" to the screens ribbon cable. Video display requires another solution if full mirroring of phone display is not possible natively. In my case it would require another plug and play device for Chrysler/Jeep vehicles called a Lockpick Air to accomplish that.
http://www.coastaletech.com/mygigair.htm
So, I'm having a few issues getting this working... I have Nexus 7 wifi 2013. I'm running stock os 6.0.1, rooted. I've installed Timur's kernel as well. I installed AA from http://www.apkmirror.com/apk/google-inc/android-auto/ , 2.0.6423 and installed the attached HUR-T from the beginning of this post.
When I try to launch AA, it asks if I want to open HU, and I say yes. Then the option for wifi, wifi direct, usb and settings comes up. Both WIFI options give me a black screen and nothing else.
I try to see if there is a wifi network from my phone, but nothing is coming up.
Now, I don't have the create a wifi network option on my Nexus 7... Is that the issue? If so, how do I add that option back. I edited build.prop to add it, but nothing is showing up for creating a wifi hotspot. Not sure if I'm looking in the right area, or not, but end result, just a black screen when I try to launch HU. Also, can't open self mode, it just freezes.
Any help would be appreciated.
Will
Ok, so this is no help to me. I want to do this without any interference into the car's hardware (especially it is a new one still on warranty). But thanks for trying .
Hi.Emil,
Thanks, that worked perfect. I noticed I have the trial, where do I support and get the real deal?
I have a separate issue that is really annoying. Not sure if anyone else might be experienced in this....
I have an awkward medium pitched hum when the screen is actually on. If I turn the screen off, it goes away.
Equipment:
Pyle 300w mini amp
4 way USB
hard wired (soldered) 2A usb charger
Joy in Steering wheel adapter
USB DAC. (Second one, I thought this was the issue, but it wasn't)
OTG splitter
The DAC and the Joycon plug into the 4 way.
The 4 way into the OTG.
OTG plugs into the 2A USB charger and the other end of the OTG into the tablet.
Double insulated audio cable (dual headphones jack) to the Pyle amp and the DAC.
I have a ground lead off of the butt of the 2A USB charger and a ground lead off of the Pyle amp. They are joined and mounted on one of the bolt holes for the stock stereo.
Joycon is pinned to the wiring harness to read the steering wheel buttons and works great (but isn't grounded)
Not sure if there is a better way, bit like I said, when the screen is on, there is a horrible tone that doesn't go away until I turn the screen off.
Again, any help would be appreciated.
Connecting using WiFi : B3ITHi. I bought this from Play Store yesterday for an android T3L HU. Was able to make it work thru USB. But wireless seems to have a mind of its own. It suddenly started working after many attempts but stopped working suddenly as well. I tried everything, watched few YT videos but nothing seems to be working. I have a Samsung Galaxy S21 with Android 14. Any idea how to make wireless work?
You don't need to say, 'Hey Google' with AA. Rather you should be able to use either the mic button on your steeringwheel or the mic icon on the AA screen. Then simply say your instruction. If you have apps specified with AA on your phone, e.g. Spotify for music, then you don't even need to say play such and such on Spotify. Depending on the active navigation too, in my case Sygic, 'Navigate to...' without having to say also '...on Sygic', works also.Can You, guys give me some tips about making assistant work well on HUR installed on Chinese cars that does not support Android Auto out of the box.
It's on the headunit setting not HUR.Anyone know how to stop this changing teh volume while i drive, its driving me crazy, go fast volume jumps go slow or stop and i can hardly hear my music, it it just this app or does android auto do this too
There is also a speed sensitivity setting in HUR, Under Settings --> Audio, scroll down.Anyone know how to stop this changing teh volume while i drive, its driving me crazy, go fast volume jumps go slow or stop and i can hardly hear my music, it it just this app or does android auto do this too
Story of our life... I recommend to use with USB, the wireless is unstable, and you can't never know when it will work.Hi. I bought this from Play Store yesterday for an android T3L HU. Was able to make it work thru USB. But wireless seems to have a mind of its own. It suddenly started working after many attempts but stopped working suddenly as well. I tried everything, watched few YT videos but nothing seems to be working. I have a Samsung Galaxy S21 with Android 14. Any idea how to make wireless work?
Isn't that exactly what you just joined up to do?
You didn't join to ask a question. You could have started with telling us what device and Android version you are trying to connect with/to, and perhaps someone could help you constructively.
Sent from my ELE-L29 using Tapatalk