[Android 4.1+] Headunit for Android Auto - 160117 - Self Mode+ other fixes, x86, 720p

Marecki_

Senior Member
Jul 16, 2012
153
37
0
Ok thanks for reply, I get it now. It IS laggy on the video side. So what do you recommend, how to switch it to the right dpi? Do you think this has sth to do for ex with gpu rendering available to turn on indeveloper options?
 

Emil Borconi

Recognized Developer
Feb 18, 2008
3,191
2,859
243
Tg. Secuiesc / Kezdivasarhely

Marecki_

Senior Member
Jul 16, 2012
153
37
0
I've already tested cm13 by Andi and I was getting this (attachement) when launched AA. On CM12.1 I at least got it running.
 
Last edited:

mkomana

New member
Sep 4, 2010
4
1
0
Is anyone using Nexus 7 2012? My setup was working fine, but now none of the releases work, including the latest paid app. When my phone is connected via USB Headunit recognises the phone but does not launch. On the phone, AA says it is connected to the car (headunit). I do not use self mode as I use the data on my phone.

I'm running rooted stock lollipop 5.1 with oxydo revamp kernel
 

fma965

Senior Member
Nov 20, 2011
3,728
1,654
0
cyanlabs.net
does any one know any other way of port forwarding? that sysctl command doesn't work for me on all roms i have tried


I can use the FWD Port forward app but it doens't start on startup, does any one know any other command line / shell binary i can use to port forward?

Also when i start self mode i have to press home then open HU again, is this normal? otherwise i get a black screen.
 

Emil Borconi

Recognized Developer
Feb 18, 2008
3,191
2,859
243
Tg. Secuiesc / Kezdivasarhely
does any one know any other way of port forwarding? that sysctl command doesn't work for me on all roms i have tried


I can use the FWD Port forward app but it doens't start on startup, does any one know any other command line / shell binary i can use to port forward?

Also when i start self mode i have to press home then open HU again, is this normal? otherwise i get a black screen.
I'm afraid I'm not aware of any other way to forward the port. You can try to use the ADB approach but in my case it wasn't stable (aka it kept disconnecting).

As of pressing home and HU again, you can try to just swipe from left to right (bring up the HU list menu) and you should see the screen come up.
 

Marecki_

Senior Member
Jul 16, 2012
153
37
0
Ok I tried a different approach. Phone A3, stock 5.0.2 rooted - AA/ SGT2 7.0 Slimkat 4.4.4 - HeadUinit. Because Kitkat on GT2 is far more stable and faster. Will it work? I've already tried to connect phone to the tab but didn't get it running, phone can't get connected to the car.
 

fma965

Senior Member
Nov 20, 2011
3,728
1,654
0
cyanlabs.net
Is any one else having to press HOME then go back to HeadUnit after starting self mode (Tether or Local) ? i tested the ROM's above and all roms with working TCP HU required me to do that. even if i set tasker to wait 5 seconds, go home then go back to HU it doesn't work.
 

ikerg

Senior Member
Dec 19, 2007
2,393
691
0
Gents.Apart from this fantastic app from which we can talk during months... Do we know anything from mike? He was on hospital and do we know if he has recovered?


Enviado desde mi D6603 mediante Tapatalk
 

Christopher Price

Senior Member
Jul 24, 2014
122
60
48
console.com.co
Unfortunately I don't have any good news to share. I spoke to him as he was going to hospital, and he was in bad shape. I personally was urging him to go to hospital for about a week prior.

My attempts to reach him since have gone unresponded.
 

champikasam

Member
Sep 28, 2011
22
2
0
Hi,

I downloaded January 17 release through XDA Labs app and installed it in my RK3188 Android 4.4.4 head unit. I am using a Nexus 6P running the latest version of android to connect to it. When i connect, i can see that my phone detects the HU and shifts to android auto screen, but the head unit shows a black screen (with the side bar appearing sometimes). I am unable to see android auto view on the head unit.

Also when i exit headunit app by either using the exit entry in the sidebar or the back button, it keeps on starting back without closing. Only way to exit is to click on exit drive mode option on the notification drawer in the head unit.

I haven't tried using a different OTG cable yet, but will try that soon. Meanwhile, any idea what could be wrong here ?

Thanks in advance
 
  • Like
Reactions: erfanoabdi

rock187

Senior Member
Jul 29, 2008
61
4
0
padoa
Hi,

I downloaded January 17 release through XDA Labs app and installed it in my RK3188 Android 4.4.4 head unit. I am using a Nexus 6P running the latest version of android to connect to it. When i connect, i can see that my phone detects the HU and shifts to android auto screen, but the head unit shows a black screen (with the side bar appearing sometimes). I am unable to see android auto view on the head unit.

Also when i exit headunit app by either using the exit entry in the sidebar or the back button, it keeps on starting back without closing. Only way to exit is to click on exit drive mode option on the notification drawer in the head unit.

I haven't tried using a different OTG cable yet, but will try that soon. Meanwhile, any idea what could be wrong here ?

Thanks in advance
it's require android 5.0+
 
  • Like
Reactions: champikasam

champikasam

Member
Sep 28, 2011
22
2
0
it's require android 5.0+
Thanks for the reply. Android 5+ requirement is for the Google Android Auto app isn't it ? For that i'm using a Nexus 6P phone with android 6 running on it. It is the head unit which runs the server (headunit app) that has android 4.4.4. Should this be a problem ?
 

Emil Borconi

Recognized Developer
Feb 18, 2008
3,191
2,859
243
Tg. Secuiesc / Kezdivasarhely
Thanks for the reply. Android 5+ requirement is for the Google Android Auto app isn't it ? For that i'm using a Nexus 6P phone with android 6 running on it. It is the head unit which runs the server (headunit app) that has android 4.4.4. Should this be a problem ?
Hi,
You are right, the phone need to be 5+ and the device running the head unit need to be 4.1+. However as it was mentioned quite a few times, till now we didn't saw any chinese head unit which was able to run the app properly. It looks like all of them have some ind of problem with the Hardware decoding part.

If I recall correctly there was 1 person who got it working on an android powered head unit, but that was a custom build rather than a chinese product.

Also I think your unit is able to do a so called "screen-mirroring" called EasyConnect or similar, so you might want to try to run a headunit app on your phone in SelfMode and mirror the screen to your car stereo.

Alternatively I have posted a convoluted way on how you can mirror the screen from your phone to your car by wifi (assuming the phone is rooted). Besides not being the most practical/easiest way to get it running, it does require a strong charger for the phone (it will use Wifi+GPS+Screen always on) so the power consumption and heat up will be significant. For details see: http://forum.xda-developers.com/showpost.php?p=64881737&postcount=1015
 
  • Like
Reactions: champikasam

kris4956

New member
Jun 8, 2016
3
0
0
I have this working using a SG7 Edge and a Nexus 7. I'm using a micro USB to micro USB cable, and am thrilled it worked. Now I'm wondering if there is a way to provide a charge to both devices while in use.
 

erfanoabdi

Recognized Developer
Jan 3, 2015
1,007
3,133
153
Tehran
erfanoabdi.github.io
Hi,

I downloaded January 17 release through XDA Labs app and installed it in my RK3188 Android 4.4.4 head unit. I am using a Nexus 6P running the latest version of android to connect to it. When i connect, i can see that my phone detects the HU and shifts to android auto screen, but the head unit shows a black screen (with the side bar appearing sometimes). I am unable to see android auto view on the head unit.

Also when i exit headunit app by either using the exit entry in the sidebar or the back button, it keeps on starting back without closing. Only way to exit is to click on exit drive mode option on the notification drawer in the head unit.

I haven't tried using a different OTG cable yet, but will try that soon. Meanwhile, any idea what could be wrong here ?

Thanks in advance
My head unit is 5.1.1 and I have same problem
Have you succeed to run Android auto?
Or self mode!? (If yes, How?)

Thanks
 
Last edited:

champikasam

Member
Sep 28, 2011
22
2
0
Hi,
You are right, the phone need to be 5+ and the device running the head unit need to be 4.1+. However as it was mentioned quite a few times, till now we didn't saw any chinese head unit which was able to run the app properly. It looks like all of them have some ind of problem with the Hardware decoding part.

If I recall correctly there was 1 person who got it working on an android powered head unit, but that was a custom build rather than a chinese product.

Also I think your unit is able to do a so called "screen-mirroring" called EasyConnect or similar, so you might want to try to run a headunit app on your phone in SelfMode and mirror the screen to your car stereo.

Alternatively I have posted a convoluted way on how you can mirror the screen from your phone to your car by wifi (assuming the phone is rooted). Besides not being the most practical/easiest way to get it running, it does require a strong charger for the phone (it will use Wifi+GPS+Screen always on) so the power consumption and heat up will be significant. For details see: http://forum.xda-developers.com/showpost.php?p=64881737&postcount=1015
Thanks for the reply. this should be the issue. I also read elsewhere in this forum that the h264 decoding capabilities of Chinese head units are not good enough for the headunit app. The one unit which got it to work had an 8 core CPU (hopefully with better hardware decoding of h264). Mine is just a quad code RK3188.

I'll try EasyConnect and your screen mirroring solution. Thanks again !

---------- Post added at 04:47 PM ---------- Previous post was at 04:41 PM ----------

My head unit is 5.1.1 and I have same problem
Have you succeed to run Android auto?
Or self mode!? (If yes, How?)

Thanks
Hi,
Sadly I couldn't get the headunit app to work on my head unit. Probably it's a limitation in the hardware decoding capabilities in the CPU. I'm still experimenting with the screen mirroring solutions as well.