Jump to: navigation, search

Difference between revisions of "OpenHU Builds"

(Play Store notes)
Line 7: Line 7:
 
'''Important:''' Only you are responsible for how you drive, and for how use this app. This app may contain bugs and glitches. It is offered without warranty. Focus on driving at all times, and don't allow any infotainment device to distract you.
 
'''Important:''' Only you are responsible for how you drive, and for how use this app. This app may contain bugs and glitches. It is offered without warranty. Focus on driving at all times, and don't allow any infotainment device to distract you.
  
== Requirements ==
+
== Installing ==
 +
 
 +
You must enable unsigned sources, which is typically inside the Security tab of the Android Settings app. Google repeatedly removed Mike Reid's submissions of his predecessor app to the Google Play Store, routinely giving intentionally vague reasons for removal. As such, we have no immediate plans to submit the app to the Google Play Store, and we discourage you to attempt doing so either.
 +
 
 +
If you are running Lollipop, KitKat, or Jelly Bean, you will need to activate USB Debugging. This should not be necessary on Marshmallow.
 +
 
 +
Once done, simple sideload the APK to your device and install it, as you would any other APK file obtained from the internet.
 +
 
 +
For best results, launch OpenHU once, then reboot the device. This loads the proper USB ID associations with the ADB system.
 +
 
 +
== Requirements & Important Notes ==
  
 
OpenHU requires an Android device running Android 4.1 "Jelly Bean" or later. Android 4.4 "KitKat" or higher is strongly recommended. We are only focused on developing for Android 5.1 "Lollipop" and above, so we encourage you to at least use that version.
 
OpenHU requires an Android device running Android 4.1 "Jelly Bean" or later. Android 4.4 "KitKat" or higher is strongly recommended. We are only focused on developing for Android 5.1 "Lollipop" and above, so we encourage you to at least use that version.
  
You must enable unsigned sources, which is typically inside the Security tab of the Android Settings app. Google repeatedly removed Mike Reid's submissions of his predecessor app to the Google Play Store, routinely giving intentionally vague reasons for removal. As such, we have no plans to submit the app to the Google Play Store, and we discourage you to attempt doing so either.
+
Currently Android N (Developer Preview) devices cannot run OpenHU. Android N adds additional security layers to ADB networking that will require reworking the app, routing USB networking calls through JNI instead of NDK. This is something we hope to incentivize the developer community to help us do. It may also change as Android N is in an active state of development - so we aren't going to treat this as a priority, until Android N ships.
 +
 
 +
* It is important to note that phones running Android Auto as a client app, and the Android N Developer Preview, from our testing can communicate with an OpenHU tablet running Android versions prior to Android N. In other words, if your phone has Android N installed, you should be fine... just don't update the tablet you want to run OpenHU on to Android N Developer Preview. ''Currently the only tablets that this is an issue on, are the Nexus 9 and Google Pixel C.''
  
 
It is a project goal to resolve any lingering concerns about the app with the Google Play team, but we ask that you aid this process by not flooding Google Play with your own APK builds of OpenHU. It may, in fact, endanger your developer credentials with Google Play to attempt submitting this app to the Google Play Store (''though we are not aware of any Play Store rule that it inherently violates'').
 
It is a project goal to resolve any lingering concerns about the app with the Google Play team, but we ask that you aid this process by not flooding Google Play with your own APK builds of OpenHU. It may, in fact, endanger your developer credentials with Google Play to attempt submitting this app to the Google Play Store (''though we are not aware of any Play Store rule that it inherently violates'').

Revision as of 04:09, 24 June 2016

Console OS > Wiki > OpenHU > OpenHU Builds

Downloading Builds of OpenHU

OpenHU is very much a work in progress. When we're ready, builds of OpenHU will be pubished here. Until then, you can download the source code from GitHub and build it yourself!

Important: Only you are responsible for how you drive, and for how use this app. This app may contain bugs and glitches. It is offered without warranty. Focus on driving at all times, and don't allow any infotainment device to distract you.

Installing

You must enable unsigned sources, which is typically inside the Security tab of the Android Settings app. Google repeatedly removed Mike Reid's submissions of his predecessor app to the Google Play Store, routinely giving intentionally vague reasons for removal. As such, we have no immediate plans to submit the app to the Google Play Store, and we discourage you to attempt doing so either.

If you are running Lollipop, KitKat, or Jelly Bean, you will need to activate USB Debugging. This should not be necessary on Marshmallow.

Once done, simple sideload the APK to your device and install it, as you would any other APK file obtained from the internet.

For best results, launch OpenHU once, then reboot the device. This loads the proper USB ID associations with the ADB system.

Requirements & Important Notes

OpenHU requires an Android device running Android 4.1 "Jelly Bean" or later. Android 4.4 "KitKat" or higher is strongly recommended. We are only focused on developing for Android 5.1 "Lollipop" and above, so we encourage you to at least use that version.

Currently Android N (Developer Preview) devices cannot run OpenHU. Android N adds additional security layers to ADB networking that will require reworking the app, routing USB networking calls through JNI instead of NDK. This is something we hope to incentivize the developer community to help us do. It may also change as Android N is in an active state of development - so we aren't going to treat this as a priority, until Android N ships.

  • It is important to note that phones running Android Auto as a client app, and the Android N Developer Preview, from our testing can communicate with an OpenHU tablet running Android versions prior to Android N. In other words, if your phone has Android N installed, you should be fine... just don't update the tablet you want to run OpenHU on to Android N Developer Preview. Currently the only tablets that this is an issue on, are the Nexus 9 and Google Pixel C.

It is a project goal to resolve any lingering concerns about the app with the Google Play team, but we ask that you aid this process by not flooding Google Play with your own APK builds of OpenHU. It may, in fact, endanger your developer credentials with Google Play to attempt submitting this app to the Google Play Store (though we are not aware of any Play Store rule that it inherently violates).

In terms of hardware, your device must support USB On The Go (OTG) mode, and your build of the Android operating system must support it as well.

Your device also needs to be able to decode H.264, which is an Android compatibility requirement - but some low-end uncertified devices lack.

Currently x86 device support requires Intel's ARM translator "Houdini" - which all production Intel-based Android devices have. Still, this is a high priority to resolve, as it will improve power consumption and performance on x86, and there are no major roadblocks to making the app cross-architecture. While Mike Reid had crafted a fix for this, he passed away before uploading these changes to GitHub.

Finally, the phone or device you wish to connect - must be running the Android Auto app, obtained from Google Play. Unlike the OpenHU app, which is not a Google-endorsed app, the Android Auto client app must be obtained from Google Play - and the phone in question must have Google Play Services installed. In the very, very long term, the OpenHU project may pivot to developing a client-side app, but this is not a priority right now.