I've seen these simple USB GPS receiver antennas that hook to a laptop for GPS duties so naturally I'm thinking why can't this be done for the nook. Ideally we would have a dual/split port so power could still be supplied at the same time.
I'd rather have this config since I don't like the idea of tethering to a GPS capable cell for privacy reasons and it ties up the cell too.
Why couldn't this be possible? Is it just a matter of the Nook recognizing the GPS antenna and being able to get a software package to recognize it?
Any ideas?
With CM7, and a bluetooth GPS reciever, this is no problem. We will never be able to build a GPS into the device, but we can get close enough...
Yes, my intention would be to leave the GPS antenna in the vehicle and just hook up when I get in. Along with MP3 duties of course. It shouldn't be hard to find or make a USB gender changer with dual connections.
KDOG2020 said:
Yes, my intention would be to leave the GPS antenna in the vehicle and just hook up when I get in. Along with MP3 duties of course. It shouldn't be hard to find or make a USB gender changer with dual connections.
Click to expand...
Click to collapse
Im not following, sorry.
I just ordered a "kit" for my NC actually - a car window mount, and a stand-alone BT GPS. I plan on attaching the the GPS to the window mount via velcro, and leave it in the car. You don't need USB at all (nor would it work, since our nook does not currently support usb host). Just get a BT module, and leave it in the car; connect it to the nook when you need it. done.
Ok I see what your saying. But Im not familiar with Bluetooth recievers. Are we talking about just a regular GPS with a screen and all? Then why hook it up to the nook? Or are we talking about a little box that just sits on the dash or tucked away somewhere?
KDOG2020 said:
Ok I see what your saying. But Im not familiar with Bluetooth recievers. Are we talking about just a regular GPS with a screen and all? Then why hook it up to the nook? Or are we talking about a little box that just sits on the dash or tucked away somewhere?
Click to expand...
Click to collapse
Ah, let me fill ya in then.
What i am talking about are standalone recievers - nothing more than a GPS and BT transmitter. No screen, no frills. Most have batteries that will last for weeks, and are small enough to store anywhere in the car when not in use. YOu can see a good selection here:
http://www.amazon.com/s/ref=nb_sb_n...eiver&keywords=bluetooth+gps+receiver&ie=UTF8
Hope that may give you some new ideas.
Aaaahhhh..... yes I see now. So it would be just a matter of finding one thats compatible with our NC's and the software for it... cool. Anyway to know which one works the best for the Nook?
KDOG2020 said:
Aaaahhhh..... yes I see now. So it would be just a matter of finding one thats compatible with our NC's and the software for it... cool. Anyway to know which one works the best for the Nook?
Click to expand...
Click to collapse
Now, i guess i cannot guarantee, but in theory, ANY BT gps should work with our system, since all GPS's transmit in the same standard. All you should need for software on the nook will be:
https://market.android.com/details?id=de.mobilej.btgps&feature=search_result
or
https://market.android.com/details?id=googoo.android.btgps&feature=related_apps
Assuming my GPS arrives sometime soon, i will be able to give ya some first hand advice.
You will still need a data connection if you intend to use Google Maps for your GPS software.
If you want to use it without a data connection, you will need something like this:
https://market.android.com/details?id=com.alk.copilot.market.usa&feature=search_result
"maps stored on your phone, not downloaded"
Also note, Bluetooth range is very limited on the NC. My BT GPS has to be within 2 feet of the NC to connect.
That is true, a stand alone program is the best, but google will cache the maps if you pre-plan the route.
As for distance - with a car mounted GPS< you really don't need to worry about that - the GPS should be by the windshield anyway, so keeping it close to the nook isn't an issue..
What about this Google "Navigation" program that is on the nook? (the blue arrow)
KDOG2020 said:
What about this Google "Navigation" program that is on the nook? (the blue arrow)
Click to expand...
Click to collapse
You'd still need a data connection. The best probable solution would be to tether to a smartphone that has GPS - so the Nook has a data connection for the Google Maps and Navigation, and GPS data from the phone's GPS.
I was interested in the same thing and went so far as to successfully pair my Garmin bluetooth gps unit with my CM7 nook, but I was not able to actually read any gps data. (This unit was successfully used with a linux laptop and car computer, so it works in linux.)
While looking for a way (hack or software) to read the gps data I found the TetherGPS app, which meets my needs- and yes, I have received phone calls and browsed the web on the phone while using nav on the nook without problems.
The biggest issue I have found in the past and NOW is that I do not think much of the other gps nav options available on Android (or linux!) and caching a limited tileset with Google maps is not enough for my needs. My routes often change.
I do have another bluetooth puck around, if I can find it... I will test to see if that one is easier for the Nook to read data from.
rogerdugans said:
I was interested in the same thing and went so far as to successfully pair my Garmin bluetooth gps unit with my CM7 nook, but I was not able to actually read any gps data. (This unit was successfully used with a linux laptop and car computer, so it works in linux.)
While looking for a way (hack or software) to read the gps data I found the TetherGPS app, which meets my needs- and yes, I have received phone calls and browsed the web on the phone while using nav on the nook without problems.
The biggest issue I have found in the past and NOW is that I do not think much of the other gps nav options available on Android (or linux!) and caching a limited tileset with Google maps is not enough for my needs. My routes often change.
I do have another bluetooth puck around, if I can find it... I will test to see if that one is easier for the Nook to read data from.
Click to expand...
Click to collapse
It will pair, but you need to use an intermediary program to access the GPS, like this one:
https://market.android.com/details?id=googoo.android.btgps&feature=related_apps
or this one:
https://market.android.com/details?id=de.mobilej.btgps&feature=search_result
or this:
https://market.android.com/details?...oid.addon.bluetooth.GPS&feature=search_result
I had trouble with some GPS apps.
I was able to use the GPS and data access on my Motorola Cliq to have GPS voice guided navigation.
http://forum.xda-developers.com/showthread.php?p=12076390
That is how I accomplished it.
If you have a hardware GPS, then you only need the 1 app, which is even easier, but I still recommend wifitether or barnicle for data access (you can download the maps for offline use if you plan ahead.)
colorado_al said:
It will pair, but you need to use an intermediary program to access the GPS, like this one:
https://market.android.com/details?id=googoo.android.btgps&feature=related_apps
or this one:
https://market.android.com/details?id=de.mobilej.btgps&feature=search_result
or this:
https://market.android.com/details?...oid.addon.bluetooth.GPS&feature=search_result
Click to expand...
Click to collapse
I actually tried those apps to no avail, which is why I started looking for the other puck (not as accurate but easier to connect) and alternative solutions.
I actually had looked at all of the other (non- Google) nav apps for Android before to use with a now unused Droid (original) but found them all to be ... less than desirable for various reasons.
Note that I am NOT trying to discourage this project- it is possible, I am certain, but much like linux navigation software... lacking a certain "polish" if not functionality.
Googling shows mixed results over whether this will be possible.
When my phone connects to the car Bluetooth, can mobile hotspot also turn on so my car sat nav can use the phone data?
Currently I have to turn it on manually each time.
Thanks
candell77 said:
Googling shows mixed results over whether this will be possible.
When my phone connects to the car Bluetooth, can mobile hotspot also turn on so my car sat nav can use the phone data?
Currently I have to turn it on manually each time.
Thanks
Click to expand...
Click to collapse
I do it with secure setting plugin... but you need to be rooted.
Regards,
Sorry for a possibly dumb question, I am new to android. Does Tasker provide additional functionality when rooted?
candell77 said:
Googling shows mixed results over whether this will be possible.
When my phone connects to the car Bluetooth, can mobile hotspot also turn on so my car sat nav can use the phone data?
Currently I have to turn it on manually each time.
Thanks
Click to expand...
Click to collapse
Can be done:
State: BT near (select BT from Nav device) -> task wifi set off, wait 2 seconds, wifi tether set on.
On android 6 I used secure settings for also switching bluetooth tether on. This doesn't work for me in android 7.0.
I now use the app Blue Car tethering. This checks for a bluetooth network and then forces bluetooth tethering.
This is unrooted for both phones.
From what I gather, YMMV depending on the phone, head unit, or even carrier. This works to turn on the hotspot and re-enable wifi/turn off hotspot when the bluetooth connection drops for my current setup (rooted Honor 6X/Android 6, Cricket Wireless, Android 4.4 head unit):
Profile state=BT Connected CAR KIT,*
Action=WiFi Tether Set On
Exit=WiFi Set On
I don't need secure settings for that to work on my Honor 6X, but I have two other phones that profile doesn't work on, so you might have to play around to get something that works for your particular setup
I've got it working, thanks for the help folks
candell77 said:
I've got it working, thanks for the help folks
Click to expand...
Click to collapse
Would you mind sharing how? It would be very useful to me. Thanks :good:
Sure, create a new profile based on State
In the filter type 'BT'
Then click BT Connected
Then select or type the exact name of the bluetooth connection of your car
Then create a new task for Tether On (instead of trying to find the options, I find it much easier to search)
Job done, works every time for me. As tether automatically turns off itself after xx minutes of not being used, I didn't bother setting an exit task to turn it back off.
Is this related to Bluetooth tether or wifi mobile hotspot?
I'm looking for an automated solution for my car android 2din device.
After Google announced almost a full year ago that Android Auto would support phone connections without needing to rely on a USB cable, I have yet to find any news on this.
Is this still happening in the aftermarket HU's? Hoping this doesn't turn into another Android Wear situation where it lacks the attention it needs to make it a market hit.
Hi,
This is called "WIFI Projection", and it's included (hidden) in the last release. No one knows how to enable AND use it. Still in alpha!
I hope current HU with wired AA support can be upgraded to wireless with a simple USB dongle (not a Wifi dongle, but with an AA wireless adapter).
Just to make sure I understood correctly: the option is there in the OS, but it doesn't work on any device as of yet? As if the software support is there, but the hardware support is not?
I'm a bit disappointed that Android Auto wasn't discussed at the I/O keynote... I think there's lots of usability updates required to improve it...
Relevant:
https://arstechnica.com/cars/2017/0...finally-ready-to-talk-about-its-car-os/?amp=1
What gets me: is it really necessary to use a a different name for this? Chromecast comes in audio-only and video forms, Pixel comes in "XL" and "C" forms also, can't they just name it something like "Android Auto Standalone" and call it a day? It serves the same end goal of getting Android into your car's radio/head unit.
Still no news of the phone-based Android Auto and wireless that I can find. That said, if everything will be integrated into the radio to begin with, I'd welcome the lack of tethering. Might even get back to developing Android apps for myself now that I have a use for them, but for my car this time! Hopefully the aftermarket guys will be smart enough to bypass Android for the sound processing though. Would hate for a resource-hogging app to kill my radio!
Background
- Couple of years ago Google have launched Android Auto, but up till recently the only way to connect your device to the car/head unit was to plug in a USB cable. As of 2018 this starts to change, BUT it looks like you will need to get new hardware for this and older cars/head units won't be upgraded to support this, neither phones with older OS.
Concept
- Since many of us will like to have this wire free but not ready / willing or have the possibility to upgrade the units/cars/phones I have thought of a way to achieve this, by using a small auxiliary device, like for example a very cheap and basic Android TV stick, which can be plugged in/mounted in the car and which can fulfil the roll of a Wifi antenna for your car.
This app should allow you to transform any android powered device into a Wifi receiver for your Android Auto compatible Car/Headunit. Please do not confuse Android Auto, with Android powered headunit (usually Chinese, like MTCB, MTCD, Joying, etc).
AAGateWay Documentation.
Beta released (04.01.2020)
What is it?
AAGateWay is a an app which should allow you to use an auxiliary (slave) device to connect your existing Android Auto compatible car to your phone (master) using a hotspot created on your phone.
How to use it?
SLAVE SETUP
1) Install the app using XDA Labs (Only on SLAVE) : https://www.b3itlabs.com/prod.php?id=3
2) Configure
FOR BOTH ROOTED AND NOT-ROOTED SLAVES
CASE 1: Master is running Pie or higher
Pair Master and Slave over BT (do this from the normal BT settings)
Open app
If slave is ROOTED and ONLY if you are using a TV STICK convert the app to system app. (if app not visible after conversion, reboot device)
Enable the start tethering option (If asked make sure you manually configure the hotspot, to have the name HUR and the password AndroidAutoConnect)
Select the masters phone BT MAC
Exit
CASE 2: Master is running Android 8 or lower
Create a Wifi hotspot from the master
Connect slave to it
Reopen AAGateWay and select the masters hotspot from the "Phone Wifi SSID" list
Slave is ROOTED - This will give a much bigger compatibility with cars, it should work with any car/unit (but depends a lot on the slave used, read below)
Slave is NOT ROOTED - This mode won't work on all cars and it has caveats.
MASTER SETUP
CASE 1: Master is running Pie or higher
Install WiFi Launcher for HUR (https://play.google.com/store/apps/details?id=com.borconi.emil.wifilauncherforhur)
Make sure WiFi Launcher is version 2.1 or higher!!!
Open WiFi Launcher
FOR Android 10, set permission location to ALWAYS!!!!!!
Select slaves BT from the BT list and exit
DO NOT ENABLE ANY OF THE OTHER OPTIONS!!!!
If you do not want to use WiFi Launcher you can use the following Tasker task to launch AA on any condition you want: https://drive.google.com/file/d/1UO-Z5P0oQpHEdrQjYqvSM48L1TI-K5g8/view?usp=sharing
CASE 2: Master is running Android 8 or lower
Open Android Auto, go to Settings, scroll down tap the version 10 times, then from the 3 dotted top right corner select start headunti server.
Exit Android Auto
Leave the Headunit Server running
When you get into the car turn on the hotspot on the master (or use Tasker, automate or anything else do that for you)
CONNECTING
Go to the car, plug in the slave to the car's USB and start the car
Slave is ROOTED
Nothing should happen, car should NOT detect the phone (SLAVE) at this stage. If the car does detect the slave being connected, it means your slave doesn't allow a proper USB toggle, in which case you should try enabling non-root mode.
Master is Pie and above
If you selected to tether from the slave, at this point you should see the slave turning on the hotspot, otherwise you might see the slave trying to connect to a Wifi network.
Slave will notify master
Master will automatically start WiFi Launcher
Master will connect to slaves hotspot
Master will start AA on the phone and notifies slave
Slave will enable USB
If you are using a phone as slave you will get a prompt if you want to use AAGW as the default app for this action, make sure you select ALWAYS ans yes. (TV stick should work automatically)
Projection should start
Slave is NOT-ROOTED (or running in non-root mode)
You will get a prompt to use AAGateWay for this action, make sure you select always.
Car should display a splah-screen saying waiting for master. (on some car's screen you might see a scrambled image)
After splash-screen is displayed, the slave will start tethering, or will try to connect to the masters hotspot depending on the setting.
Once a network connection is established between the 2 devices, you will see the AA icon turning on on the master and Android Auto should be displayed on the car's screen. It is possible that the screen will stay /turn black, if that happens, you can try to press the home button on the infotainment system, then re-open Android Auto on it.
Troubleshoot and getting help
As the thread has so much information it will be really nice if we can try to stick to one format of troubleshooting, by using one of this 2 templates:
Master is running Pie or above and slave is tethering:
Running in root mode: (Yes/No)
If running in non-root mode, is the splashscreen visible on the car: (Yes/No)
If running in non-root mode, did you set the masters BT inside AAGW app?: (Yes/No)
Did the slave actually turned on the hotspot on the slave: (Yes/No)
On the master did you select the slaves BT in the Wifi Launcher app?: (Yes/No)
When the master connected to the car's BT did the Wifi launcher app started up?: (Yes/No)
Did the master connected to the slaves hotspot?: (Yes/No)
Did the AA icon appeared on the master at all (in the notification bar)?: (Yes/No)
Master is running Oreo or below and master is tethering:
Running in root mode: (Yes/No)
If running in non-root mode, is the splashscreen visible on the car: (Yes/No)
If running in non-root mode, did you set the masters BT inside AAGW app?: (Yes/No)
Did you select the masters hotspot name in AAGW?: (Yes/No)
Have you started the Headunit server on the master?: (Yes/No)
On the master did you select the cars BT in the Wifi Launcher app?: (Yes/No)
When the master connected to the car's BT did the Wifi launcher app started up (notification bar)?: (Yes/No)
Did the master turned on the hotspot?: (Yes/No)
Did the slave connected to the masters hotspot?: (Yes/No)
Getting rid of all automation and manually starting it all (regardless of Android version on master and slave):
Uninstall AAGW on the master
Start the headunit server from within Android Auto on the master
Create a hotspot on the master
Open AAGW on the slave and make sure it's not set to tether
in AAGW make sure you select the masters hotspot
If AAGW is set to non-root mode make sure you select the masters BT (just press the button AAGW will do a BT scan of nearby devices and you can pick it from the list)
Go to the car and plug the slave in
Start the car
If slave is running in ROOT mode, slave will first try to connect to the masters Wifi and you will see a notification on the master that AA is running, only then the car should recognise a plugged in device.
If the slave is running in non-root mode, first you will see a splash screen on the car, then you will see slave connects to masters Wifi (if not already connected), then you will see AA starting on the master.
How do I collect a bug report / logcat
Open Settings > About phone.
Scroll down to the Build number.
Tap the Build number 7 times in quick succession until "You're now a developer" appears.
Return to the Settings menu and select Developer options.
At the top of the screen, make sure 'Developer options' is set to On (green).
Scroll down to Debugging and enable both USB debugging and Bug Report Shortcut on (green).
Tab on Logger buffer sizes: Default setting is 256K. Select 16M to help capture more information for debugging. Of note, it can affect the apps performance especially with lower spec phone, so change it back after you have finished submitting bug reports.
On slave make sure you enable debugging inside AAGW, on master open Android Auto go to developer settings and make sure force logging is enabled.
Reproduce the problem
Hold the Power button down until the menu appears.
Select Take bug report. and wait for the device to capture the bug report.
Tap the 'Bug report captured' notification when it appears.
Send the bug report by email to [email protected]
Know problems, workaround:
- Latency & lag. This will be really down to the devices you are using. I have tested it with a MK808B Plus, it work’s ok most of the time but occasionally you will get the odd lag. I’ve also tested it with a Nexus 7 tablet, and there was no lag at all, so device does matter, as well as probably ROM.
- I get random disconnection. There can be 2 causes for this, one the USB connection fails between the car and the auxiliary device, or the Wifi fails between the phone and the auxiliary device. In my tests I saw a few Wifi disconnections without any reason on the MK808, but non on the Nexus. Changing the tethering option from WPA2 to Open did help with this.
- App is closed without error or reason. The app runs in a background process, with a minimal interaction with the foreground, some devices/OS will kill background apps. I saw this happening on Nokia and I saw this happening on OnePlus as well. Try disabling battery optimisation for AAGateWay, that might help.
- I just cannot get it to work… Try using a phone, that will at least give you some visual guidance. Make sure that your device connects to the phone Wifi hotspot, make sure that AA Headunit server is running on the phone (try to force stop Goolge Play Services, stop and restart the headunit server)… All fails contact me
- Nothing happens on the master, using Wifi Launcher for HUR app. In this case, try to manually start the headunit server on the master, and manually turn on a hotspot, then reconfigure you're slave to connect to the masters hotspot (even if the master is running Pie or higher).
Device compatibility:
Master:
Any phone which normally works with Android Auto
Slave with ROOT:
- Tested and know to work: - MK809V, Nexus 7 (depending on rom), Sony X Compact (depending on rom)
-Tested and not working as expected: Pixel 2, MK808B
- While root is necessary, not all phones can toggle USB port on and off by software. And there can be other problems, for example on some devices when you turn off the USB the phone loses the ability to detect the power connection as well, which is use as trigger to start the whole process. It is almost impossible to predict if a phone will be a good slave candidate or not.
Other things
- Xiaomi phones (MIUI makes a mess), try not to use it for Slave
- Generally older phones (pre oreo) are more likely to work fine as a slave device.
Any suggested slave?
- Yes, use an MK809V TV stick, as the experience with it, is pretty slick and it should work out of the box. If you get a MK809IV try to get the one with Android 5.1.1 as the one with Android 7.1 has problems with the tethering.
FAQ.
Q: Can I use this with any car and phone combination?
A: Assuming your car is already Android Auto compatible, then YES.
Q: Can I also automate the start of the Headunit server?
A: Only with a rooted phone, using the following shell command: am startservice -W com.google.android.projection.gearhead/com.google.android.projection.gearhead.companion.DeveloperHeadUnitNetworkService
Q: Can I use Wifi-Direct to connect instead of WIfi?
A: No.
Q: Does the traffic come out from my monthly data allowance?
A: NO, traffic between auxiliary device and phone hotspot does NOT count as internet traffic, HOWEVER if you do have other apps on the auxiliary device which download updates, etc in the background that WILL be counted as internet traffic. So I suggest double check the apps on the aux device and disable all those which aren’t needed.
Q: Will the car/head unit provide enough power?
A: It should provide at least 500mA that’s the standard USB current, while I cannot guarantee that will be enough in all cases, it should do, assuming you do turn off all unneeded services on the TV stick.
Q. What about start up time?
A. It will depend a lot on the device you are using. A low-entry TV stick boot time is about 1 minute, which can be a bit too much for an initial car setup. As mentioned earlier, these devices usually have 2 USB ports, you can for example connect the power USB port to a continues power supply in the car, in which case the boot time will be non-existent since the device is always running. If you are using a phone, the phone battery will probably hold the charge just fine for a couple of days, if you disable all apps on it and you set up a profile to go into aeroplane mode when it’s not charging. Tasker or Automate are your friends for that. If you cannot connect the TV stick to a continues power source, you might consider using a small portable power pack which powers the tv stick (should hold power for a few days) and the power pack can be charged while the car is running.
Q. Can I decrease boot time for TV Sticks/Phones by removing all unrelated software.
A. Yes, actually quite a lot. Once you have your configuration ready and everything is working as expected, you can uninstall/disable all packages beside this ones:
package:android
package:com.android.apkinstaller
package:com.android.providers.settings
package:com.android.packageinstaller
package:com.notriddle.null_launcer (or any other launcher, but NULL launcher has no memory consumption, no app drawer no nothing, perfect for headless - see: https://github.com/notriddle/null-launcher )
package:com.android.inputmethod.latin
package:com.android.settings
package:uk.co.borconi.emil.aagateway
package:com.android.shell
package:com.android.systemui
Easy way to list / disable all apps will be using a computer and following commands
Code:
adb shell pm list packages
This will list all installed packages
Code:
adb shell pm disable xxxx
where you replace xxxx with the package name (Ex: com.android.shell )
Q. Will using Wifi 5Ghz give me better performance?
A. Well if both of your devices support it, SURE!
Q. Is the source code available?
A. Sort-of, please see: https://github.com/borconi/AAGateWay this is only for the sketch, however new version does contain code which lift restrictions on 3rd party apps in Android Auto. To prevent the abuse of this by some, further code won't be updated to GitHub, however if you want to build your own version, please do contact me for details.
Guarantee or Warranty
- Due to the fact that there are so many possibilities and combinations of cars, head units, slave and master devices, there is no way for me to test all of them, however if you did purchase the software and you are not able to get it to work for any reason, please email me on [email protected] and I'm more then happy to refund the purchase.
Teaser:
VERY interested in the progress on this, Emil. For one, this would allow me to charge my Samsung using the Quick Charge adapter in my cigarette lighter, rather than relying on the anemic power output of my truck's USB port. Or if I want to get fancy, I could install a wireless charger and use that.
Thanks for all of your hard work.
Sent from my SM-G935V using Tapatalk
Hi Emil,
What about original headunits that have integrated Wifi, but do not have Wireless Android Auto enabled? Is this something that you could enable to work as well?
Another great idea.
Definitely interested..
thanks.
Sent from my iPad using Tapatalk
I thought of you instantly when I saw this thread on Reddit, but didn't imagine that you were the creator.
Congratulations and thanks again!
Jackos said:
Hi Emil,
What about original headunits that have integrated Wifi, but do not have Wireless Android Auto enabled? Is this something that you could enable to work as well?
Click to expand...
Click to collapse
Sadly no, that will require altering the firmware on the car and each unit is different. It is possible that those unit might get an official update for Wifi support, but although I'm not 100% certain, I think it will only work with 5Ghz Wifi network, so if you're unit is 2.4Ghz only probably it won't get the update.
If I will ever have times (something which I never have ) I might look into adding this to some units out there, but that is so far down the line, that realistically speaking probably will never happen.
Very interesting idea. I have a couple of these android sticks here and maybe even a modern mediabox that might offfer a bit more performance. I guess you want to power it from the USB socket from the car. Not sure how much current you can draw from these ports.
What is the pc below the radio doing?
This is awesome news! looking forward to progress!
lukesan said:
Very interesting idea. I have a couple of these android sticks here and maybe even a modern mediabox that might offfer a bit more performance. I guess you want to power it from the USB socket from the car. Not sure how much current you can draw from these ports.
What is the pc below the radio doing?
Click to expand...
Click to collapse
Performance is not really needed the slowest device should work just fine. You can theoretically disable all processes and apps, so even a device with 512Mb ram will do.
Indeed I'm taking power directly from the headunit/car in the demo I use an MK808B powered directly from the Sony XAV-100 which only provides like 500mA, so should do (especially if you kill all apps which can use CPU and turn of everything but Wifi on the stick).
The PC is the power source , to lazy to make a separate power switch so I powered the Sony from my PSU directly
Emil Borconi said:
Performance is not really needed the slowest device should work just fine. You can theoretically disable all processes and apps, so even a device with 512Mb ram will do.
Indeed I'm taking power directly from the headunit/car in the demo I use an MK808B powered directly from the Sony XAV-100 which only provides like 500mA, so should do (especially if you kill all apps which can use CPU and turn of everything but Wifi on the stick).
The PC is the power source , to lazy to make a separate power switch so I powered the Sony from my PSU directly
Click to expand...
Click to collapse
Ok, got the Mk802, 808 etc etc so I might finally have a good destination for those. Lazy and working is a combo that also works. :good:
Wondering if there is like a beta test thing, or is it complex to get it up and running? I'm pretty sure a lot of people are seriously interested in this. It would offer the freedom of charging your phone the proper way.
lukesan said:
Ok, got the Mk802, 808 etc etc so I might finally have a good destination for those. Lazy and working is a combo that also works. :good:
Wondering if there is like a beta test thing, or is it complex to get it up and running? I'm pretty sure a lot of people are seriously interested in this. It would offer the freedom of charging your phone the proper way.
Click to expand...
Click to collapse
Not that far away, the only problem this will be braking my fix for obd2aa, so I need to make the 2 things compatible. I also need to do find a way to set the defaults without plugging into the car, you won't really be able to plug in a HDMI screen when you plug it in the car.
I've started fully rewriting my HUR app moving all the code from C to Java, once that is done and I fix other issues with obd2aa I will be pushing this forward
Ideally I will like to have a release available before I go on holiday on the 17th of July but not sure I will manage to do it all by that time.
Emil Borconi said:
Not that far away, the only problem this will be braking my fix for obd2aa, so I need to make the 2 things compatible. I also need to do find a way to set the defaults without plugging into the car, you won't really be able to plug in a HDMI screen when you plug it in the car.
I've started fully rewriting my HUR app moving all the code from C to Java, once that is done and I fix other issues with obd2aa I will be pushing this forward
Ideally I will like to have a release available before I go on holiday on the 17th of July but not sure I will manage to do it all by that time.
Click to expand...
Click to collapse
Yup, sounds like a bit of an issue that you can't really test since we'll have no screen. Well maybe a sort of a config txt file. Most of us will have to clear the thing on a tv screen or monitor anyway because a lot of crap is installed on these devices. I guess it makes sense to have something that can show if the stick is getting data from the phone. There is always a way.
Emil Borconi said:
Not that far away, the only problem this will be braking my fix for obd2aa, so I need to make the 2 things compatible...
Click to expand...
Click to collapse
No offense to obd2aa, I use it daily, but I'd be interested in this even without it
Where is the APK to give it a try ?
Emil Borconi said:
Currently only a placeholder for those interested in the project while working on development.
Background
- Couple of years ago Google have launched Android Auto, but up till recently the only way to connect your device to the car/head unit was to plug in a USB cable. As of 2018 this starts to change, BUT it looks like you will need to get new hardware for this and older cars/head units won't be upgraded to support this, neither phones with older OS.
Concept
- Since many of us will like to have this wire free but not ready / willing or have the possibility to upgrade the units/cars/phones I have thought of a way to achieve this, by using a small auxiliary device, like for example a very cheap and basic Android TV stick, which can be plugged in/mounted in the car and which can fulfil the roll of a Wifi antenna for your car.
This app should allow you to transform any android powered device into a Wifi receiver for your Android Auto compatible Car/Headunit. Please do not confuse Android Auto, with Android powered headunit (usually Chinese, like MTCB, MTCD, Joying, etc).
If you are interested in this project please simply subscribe to this thread and follow the updates.
Teaser:
Click to expand...
Click to collapse
I'm interested, I have a Tahoe with AA and an Android stick. Your project sounds great, can't wait!!
You should have it by the 17th of July, I'm just in the middle of rewriting another app, once I completed that I will focus on this one. I'm going away on a holiday on the 17th of July so I'm really pushing to have it out there by then.
Having the same XAV-AX100, and I was pissed off when I heard that in order to use wireless android auto it needs to be replaced.
Great idea, can`t wait to test it.
Do you think it can works also with windows stick.? Or only android?
Sent from my iPad using Tapatalk
jeromeo01 said:
Do you think it can works also with windows stick.? Or only android?
Sent from my iPad using Tapatalk
Click to expand...
Click to collapse
Never heard of a windows stick... Any link/reference? In theory it can work with almost anything but since Android Auto need Open Accessory, Android device will be the preferred option, having all the classes already available.
Emil Borconi said:
Never heard of a windows stick... Any link/reference? In theory it can work with almost anything but since Android Auto need Open Accessory, Android device will be the preferred option, having all the classes already available.
Click to expand...
Click to collapse
Its exactly the same.
Mini PC stick, but using windows 10 as OS.
Just a little bit more expensive. But I already have one to try. [emoji6]
https://www.windowscentral.com/best-stick-pcs
Sent from my SM-G965F using Tapatalk