Timeline of events leading up to the failure.
While connected to my home wireless router via WiFi on my Tilt, I was surfing Dutty's cab-page link but was unable to see any cabs; even after registering. So I then downloaded 2 cabs from these forums that were meant to aid in Bluetooth headset volume and installed them when I noticed my WiFi connection on the Tilt disconnected.
I've attempted to re-establish the connection with no success; even so much as to go through all the connection set-up steps and re-enter the router key.
The wireless router is operating fine and my Wife's Tilt is able to connect thru WiFi with no issues as usual; so not a router problem. I am still able to connect to the net thru the phone's basic internet eg. 3G etc. (I am typing this thread from the phone)
For months until now I've been able to connect with my wireless router on my Tilt; what could have happened?
Any suggestions for a fix?
Thanks in advance!
Christopher
Solution: I had to not only Remove the Programs but I had to delete the cabs in My Documents as well.
Guess I'll just suffer with low Jawbone volume
Ok, so 2 days ago my wifi started acting up, the cause of this was from:
I tried to send an app to my friends n1 over Bluetooth (transfer failed so cancelled); whilst I had my wifi on!!!, I turned on my Bluetooth.
I then turned off Bluetooth after cancelling transfer. Now the problem starts here, after turning off Bluetooth, my phone couldn't detect my wireless router, I tried turning on and off wifi and it still can't find it which it was perfectly connected to, 2 minutes ago...
After that I did a full wipe and reflashed my Rom and it seems to pick up my router again, however, after when it sleeps and disconnects wifi, it cannot detect my router yet again and I have to turn wifi on and off to let it detect it again... this didn't happen before the Bluetooth incident I descried above...
Is there a fix or is anyone else having the same problem???
Does anyone understand why Android Auto actually requires USB to be plugged in (at least in the Sonata)?
I am also interested in this. But I read somewhere (take it with a grain of salt) it will only use WiFi in the future. But here is my question - When I use WiFi, data connection goes off. So how would data requiring apps such as Maps or Google Music work?
WiFi tethering would be a battery killer.
Sent from my D5803 using Tapatalk
km8j said:
WiFi tethering would be a battery killer.
Click to expand...
Click to collapse
Your car doesn't have a power outlet?
mike.s said:
Your car doesn't have a power outlet?
Click to expand...
Click to collapse
Doing that puts you right back to the issue of needing the phone plugged in...
km8j said:
Doing that puts you right back to the issue of needing the phone plugged in...
Click to expand...
Click to collapse
Exactly, and that's the main reason why USB is the primary method for Android Auto <> HU connections.
Many HUs do not contain GPS, so the phone GPS is used, and that eats a lot of power, particularly for navigation, Waze or any app that uses regular GPS updates.
Bluetooth does not have the bandwidth needed for video, never mind adding high quality audio too.
Wifi Direct is the secondary method for Android Auto <> HU connections and it works right now using my HU app. Google may have issues to try and fix before they make it official; they haven't even announced it yet, and if there are too many problems they may never announce or ship it.
Apple Carplay is expected to add Wifi support in the coming iOS update. It was supposed to be out earlier but likely it had problems.
It remains to be seen how (un)reliable AA and CP are over Wifi, in noisy RF environments in traffic. If your phone is in your pocket while Wifi tethering and doing navigation, it may get uncomfortably hot while draining pretty fast.
I think that for many people, the "inconvenience" of plugging and unplugging will be outweighed by the inconveniences of hot pockets/purses and drained batteries.
The story would be different if most of the "smarts" were inside the HU and the phone simply shared/synced some info (though just Wifi tethering alone can create heat and battery drain issues). The current model is that most processing occurs inside of the phone. This helps keep "ecosystem advantages" in the hands of Google and Apple, instead of the car and HU OEMs.
km8j said:
Doing that puts you right back to the issue of needing the phone plugged in...
Click to expand...
Click to collapse
The comment was about what happens if AA only works with WiFi. And you wouldn't always need to plug in (e.g. drive to the corner store), just for extended use.
Even when plugging in it's far preferable to USB networking - when using a USB (2.x) data connection, the phone is limited to drawing 500 mA by the USB specification. For many (most?) phones, that means the battery will drain if doing tether/GPS/cell data, and even if a phone can keep up with all of that, it will charge slowly. If doing a WiFi data connection, the USB charging spec can be used, and the phone can draw up to 1.5 A, enough to do WiFi tether, GPS, cell data and charge simultaneously.
mike.s said:
The comment was about what happens if AA only works with WiFi. And you wouldn't always need to plug in (e.g. drive to the corner store), just for extended use.
Even when plugging in it's far preferable to USB networking - when using a USB (2.x) data connection, the phone is limited to drawing 500 mA by the USB specification. For many (most?) phones, that means the battery will drain if doing tether/GPS/cell data, and even if a phone can keep up with all of that, it will charge slowly. If doing a WiFi data connection, the USB charging spec can be used, and the phone can draw up to 1.5 A, enough to do WiFi tether, GPS, cell data and charge simultaneously.
Click to expand...
Click to collapse
If AA ever officially supports Wifi, it will be in addition to USB, as it is now. And other connection methods may be added in future, like Ethernet, but that will be more needed for "Android in the car" that runs Android on the HU.
You are correct.
The USB charging/powering limit also arises when people use USB Host mode or regular USB device mode for various reasons. Some devices have custom kernels that can bypass these limits, but that can create some issues as well.
Didn't see anyone mention the fact that media streaming is done digitally over USB - providing much higher audio fidelity than over Bluetooth. This could also be done over WiFi if/when that option comes to AA.
Pedrore said:
Didn't see anyone mention the fact that media streaming is done digitally over USB - providing much higher audio fidelity than over Bluetooth. This could also be done over WiFi if/when that option comes to AA.
Click to expand...
Click to collapse
Not always.
My Pioneer 4100NEX is VERY insistent on putting audio over Bluetooth, and it won't even fail over to USB when the maximum of 3 BT devices are paired; just endless error message popups.
And there are at least 2 possible ways to put audio over USB:
- One is via Androids audio for accessory mode protocol, which only supports output (not mic input) and only 44.1K, 16 bits, 2 channels.
- The other is Android Auto's method which tends to use 48K, or 16K for voice.
My 4100 only connects to voice over Bluetooth when android auto is active. Media goes through usb
The 2.4 GHZ ISM band is *so* overcrowded already and is getting worse each year. Bluetooth, wifi and now the MNO carriers want on on that spectrum. A wired connection has *got* to be better in long run.
USB C which has native support for video, seems like the answer.
Hi guys i have a nexus 7 2013 installed in the dash car as entertaiment system.
I would like to ask you some help to share the internet access of the phone with the tablet, that has a low data subscription.
I tought about a profile on the tablet trigged by screen on that turn on bt and some how tells to the phone to active the bt, pair with the tablet and share the internet access.
Can you please help me? I don't know where to start.
Thank you in advance.
I have something sort of similar set up, but the other way around (profile is on my phone, car head unit doesn't need tasker). It looks like:
Profile:
State=BT connected 'Car Kit'
Task=WiFi Tether set On
Exit task=WiFi set On
So...when the phone sees it is connected to the car via bluetooth, it turns on mobile hotspot. The phone is a known wifi network to the car, so the car connects automatically. When the connection is dropped (i.e.; the car turns off), the phone turns wifi on which also turns off the hotspot.
Not exactly what you're trying to do, but more or less the same effect.
I have wireless connected aftermarket Android Auto (IDCORE on a 2015 RRS), connected with my Galaxy s10 (android 10,stock, unrooted).
System works fine, but once in the while when firing up the system (starting engine) instead of the Android Auto start logo I got a blank screen. Putting the phone to airplane mode and taking it out again solves the issue, so I assume it has something to do with 'handshake' between car AA and my mobile - but I cannot find the culprit causing this glitch.
Anybody with similar experience, help how to solve it? My suspection is double BT connection, as car connects BT (for handsfree calling) and IDCORE also connects BT to set up wireless AA. When connected with USB wire, never seen this problem - but, of course, point of having AA is cutting wires in the car (mobile sits on a wireless charging pad when in the car)..