AAWireless - General discussion and support

Search This thread

Dragoshiz

Member
Mar 24, 2021
9
2
Something interesting I noticed with the App. I moved my wife's AAW box from her Mitsubishi my GTI as I had moved my unit to our Polo, that is back on the road for a bit.

After a rocky start of taking a long time to bring up the AA screen it's now quite fast in the Polo. I was trying to enable the audio timestamp adjustment, which I hadn't tried yet but it wouldn't save the config.

When I setup the box from my wife's car I enabled the timestamp successfully and then I noticed that the same settings were applied when I was connecting to the other box in the Polo.

This is not a big issue, as they are both VAG cars and the same setup is probably fine, but what if you have another car that doesn't like a certain setup, like when I get my third box and put it back in the Mitsubishi?

Until I saw this I did assume that each individual box had it's own settings, but it seems the app applies the one setup to all the boxes it has in it's list. Could it be made that each box has unique settings? It would also be cool to rename the units.
we will have a look at it.
 
  • Like
Reactions: osm0sis

Snirpo

Member
Jan 23, 2007
25
28
Hmm, that is odd. Each device has it's own settings stored on the device. It should not apply the same config to all devices. Actually when in the settings screen it loads the current config from the device. Might have been a been bug in the app. I'll look into it.
 
  • Like
Reactions: osm0sis

-Loom-

Senior Member
Nov 5, 2010
333
66
Düsseldorf
For all users who have frequent headunit reboots with their VW MIB headunit:

I noticed that the supplied usb cable was quite loose in the car usb port. A slight touch would disable the connection.

I then bought a short 30cm USB-IF cable which sits in the USB A port a little bit more snuggly. (My former official VW cable didn't work at all with AAWireless).

Then I also enabled "Enable Audio Latency Dump" in the Android Auto developer settings.

Didn't have a single headunit reboot in two weeks now where before it was usually at least once per drive.

I don't know if it was the cable or the AA setting - or both. But it's surely worth a try if you have frequent headunit reboots.
 
Last edited:

vizzze

Senior Member
Jan 16, 2011
108
23
For all users who have frequent headunit reboots with their VW MIB headunit:

I noticed that the supplied usb cable was quite loose in the car usb port. A slight touch would disable the connection.

I then bought a short 30cm USB-IF cable which sits in the USB A port a little bit more snuggly. (My former official VW cable didn't work at all with AAWireless).

Then I also enabled "Enable Audio Latency Dump" in the Android Auto developer settings.

Didn't have a single headunit reboot in two weeks now where before it was usually at least once per drive.

I don't know if it was the cable or the AA setting - or both. But it's surely worth a try if you have frequent headunit reboots.
Did you also enable "Adjust audio timestamp" option?
 

AeneasAquinas

New member
Mar 22, 2021
2
0
Pretty much the same experience here. It worked great the first night I got it with no fiddle required. Then it worked for about 20 km on another trip and died. It has not worked since.

I have tried different cables and two different phones. I am really frustrated that there's no logical explanation for why it should stop working.

I saw a remark that the first OTA update will address the issues we have with Mazda not working. No word on when that OTA is happening tho.

Mazda CX-5 2018 with the latest firmware updates. Google Pixel 5 and One Plus 6.
For me, it was the cable in the end. Only 1 cable out of 15 varieties worked. Seriously. High data one, specifically the Anker black high speed cable
 

andreiav

Senior Member
Jun 4, 2014
218
115
Brasov
For all users who have frequent headunit reboots with their VW MIB headunit:

I noticed that the supplied usb cable was quite loose in the car usb port. A slight touch would disable the connection.

I then bought a short 30cm USB-IF cable which sits in the USB A port a little bit more snuggly. (My former official VW cable didn't work at all with AAWireless).

Then I also enabled "Enable Audio Latency Dump" in the Android Auto developer settings.

Didn't have a single headunit reboot in two weeks now where before it was usually at least once per drive.

I don't know if it was the cable or the AA setting - or both. But it's surely worth a try if you have frequent headunit reboots.
I can't wait to try this! Thanks!

Update: sadly, it did nothing for me.
After a lot of testing, I have found that very rarely, everything can work perfectly. In other words, sometimes, no matter how many songs I change and how long I am connected, everything works perfectly. Most of the times it takes less than 10 song changes to trigger a restart of my head unit.
I couldn't identify why. Maybe it's down to luck.
 
Last edited:
  • Like
Reactions: Nudnik_de

Genebaby

Senior Member
Dec 11, 2013
597
71
Here was the Tasker task I used to disable BT and WiFI scanning:

Code:
HUR
A1: Custom Setting [ Type:Global Name:ble_scan_always_enabled Value:0 Use Root:Off Read Setting To: ]
A2: Custom Setting [ Type:Global Name:wifi_scan_always_enabled Value:0 Use Root:Off Read Setting To: ]
A3: WiFi Net [ Action:Disconnect Force:Off Report Failure:Off ]

The exit task to re-enable is pretty much the same with just the value changed:

Code:
HUR Restore
A1: Custom Setting [ Type:Global Name:ble_scan_always_enabled Value:1 Use Root:Off Read Setting To: ]
A2: Custom Setting [ Type:Global Name:wifi_scan_always_enabled Value:1 Use Root:Off Read Setting To: ]
Hi, I have been trying to do this in Tasker, an app I have never had any success with.

I have a BT profile for when I connect to the car but I don't know which Code option to paste this information in for the task?
 

HofaTheRipper

Senior Member
Apr 26, 2014
104
150
St. Veit an der Glan
For all users who have frequent headunit reboots with their VW MIB headunit:

I noticed that the supplied usb cable was quite loose in the car usb port. A slight touch would disable the connection.

I then bought a short 30cm USB-IF cable which sits in the USB A port a little bit more snuggly. (My former official VW cable didn't work at all with AAWireless).

Then I also enabled "Enable Audio Latency Dump" in the Android Auto developer settings.

Didn't have a single headunit reboot in two weeks now where before it was usually at least once per drive.

I don't know if it was the cable or the AA setting - or both. But it's surely worth a try if you have frequent headunit reboots.
Thank you! This setting did something... at least its more stable now (didnt have any reeboot of the hu since thursday).

I only changed the setting in AA developer menu... cable is the delivered one 👍
 

Nudnik_de

Senior Member
Feb 22, 2011
96
18
Zurich
For all users who have frequent headunit reboots with their VW MIB headunit:

I noticed that the supplied usb cable was quite loose in the car usb port. A slight touch would disable the connection.

I then bought a short 30cm USB-IF cable which sits in the USB A port a little bit more snuggly. (My former official VW cable didn't work at all with AAWireless).

Then I also enabled "Enable Audio Latency Dump" in the Android Auto developer settings.

Didn't have a single headunit reboot in two weeks now where before it was usually at least once per drive.

I don't know if it was the cable or the AA setting - or both. But it's surely worth a try if you have frequent headunit reboots.
Unfortunately doesn't work for me. Neither Latency dump nor different cable. Just niticed that the reboot only happens when I change songs in spotify. When only navigating the headunit never reboots. This sounds to me to be a software problem but not related to contact issues with the cable...
 

-Loom-

Senior Member
Nov 5, 2010
333
66
Düsseldorf
Unfortunately doesn't work for me. Neither Latency dump nor different cable. Just niticed that the reboot only happens when I change songs in spotify. When only navigating the headunit never reboots. This sounds to me to be a software problem but not related to contact issues with the cable...

Yes, my headunit (MIB 2.5) did also reboot only when changing songs before.

But with the "Latency Dump" setting and the new USB-IF cable it's been 3 weeks without a single reboot now.

With this setting and the original AAWireless cable I drove about a week without a reboot. Then an additional 2 weeks now with the new cable.

What cable did you buy? USB-IF certified?
 

Nudnik_de

Senior Member
Feb 22, 2011
96
18
Zurich
Yes, my headunit (MIB 2.5) did also reboot only when changing songs before.

But with the "Latency Dump" setting and the new USB-IF cable it's been 3 weeks without a single reboot now.

With this setting and the original AAWireless cable I drove about a week without a reboot. Then an additional 2 weeks now with the new cable.

What cable did you buy? USB-IF certified?
I have not bought a different cable yet, just tried the ones I have. I have ordered a USB-IF certified one now. Let's see if this changes anything.
 
  • Like
Reactions: andreiav

Killmeplsok

New member
Mar 28, 2019
1
0
Just got my new unit, having a hard time setting it up because it wouldn't start. (Galaxy Note 10+ and JVC KW-V940BW). Keeps telling me to engage my parking brake, which is already permanently grounded. Different USB modes didn't help.

It worked with passthrough mode in the end but it was still a bummer because the ability to change dpi was the most excited feature for me and it's not available in passthrough mode.

Looks like I have to give resetting the device a try which I really don't want to due to how troublesome it is for me. But if I couldn't solve this after the the next OTA, I'll give it a try.
 

joshuaz5

New member
Apr 1, 2020
1
0
Received the AA wireless device, I've had a few bumps & bruises, but think it is due to my vehicle powering the USB port every time I unlock car door or open door!

First time I used it, started the app, plugged in the device - I waited on the AA wireless app to do something, and eventually just connected it to car bluetooth - worked like a champ. However... when I walked away from car for the night, it kept trying to grab my incoming calls & push through the aawireless dongle, for at least 15 minutes after I walked away - I am fortunate/unfortunate enough that it is only 15-20 feet from the house, so every call I would have to change my input to be "phone" or "phone speaker".

I then started disabling bluetooth when I walked away from car, to avoid the aggravation, and when I get back into car, turn it back on. But then AA wireless doesn't connect. So I forget the wireless, forget the bluetooth connection, and then reconnect, everything works again.

So I think my issue is due to the vehicle providing power to the USB port for a while after the ignition is off - any suggestions? I think the rest of it is self inflicted pain - the aa wireless dongle didn't expect the sequence of events I'm creating.

2018 ram 2500 - I have the 8 inch uconnect screen, I set it to power off after 30 seconds, but that didn't seem to do the trick? Any ideas? I love the concept but get very aggravated that I have to keep redirecting my calls - even in call a few times (cut out midsentence!).
Thanks,
Josh
 

jwedda

Senior Member
Jul 12, 2010
172
47
Received the AA wireless device, I've had a few bumps & bruises, but think it is due to my vehicle powering the USB port every time I unlock car door or open door!

First time I used it, started the app, plugged in the device - I waited on the AA wireless app to do something, and eventually just connected it to car bluetooth - worked like a champ. However... when I walked away from car for the night, it kept trying to grab my incoming calls & push through the aawireless dongle, for at least 15 minutes after I walked away - I am fortunate/unfortunate enough that it is only 15-20 feet from the house, so every call I would have to change my input to be "phone" or "phone speaker".

I then started disabling bluetooth when I walked away from car, to avoid the aggravation, and when I get back into car, turn it back on. But then AA wireless doesn't connect. So I forget the wireless, forget the bluetooth connection, and then reconnect, everything works again.

So I think my issue is due to the vehicle providing power to the USB port for a while after the ignition is off - any suggestions? I think the rest of it is self inflicted pain - the aa wireless dongle didn't expect the sequence of events I'm creating.

2018 ram 2500 - I have the 8 inch uconnect screen, I set it to power off after 30 seconds, but that didn't seem to do the trick? Any ideas? I love the concept but get very aggravated that I have to keep redirecting my calls - even in call a few times (cut out midsentence!).
Thanks,
Josh

This is known to the devs and will be picked up. One of them found it aggravating as well. So do expect some kind of fix in the future. When? I dunno...
 

mapinkerton

Senior Member
  • Jul 28, 2010
    56
    10
    This is known to the devs and will be picked up. One of them found it aggravating as well. So do expect some kind of fix in the future. When? I dunno...
    Looks like "when" is coming soon per the latest indiegogo update! At least the initial version of the workaround for always-on USB ports is in the first OTA and will be enabled through an app update sometime next week.
     

    Genebaby

    Senior Member
    Dec 11, 2013
    597
    71
    So I'm wondering what the definition of working is for everybody. For me it does work but I get the audio skipping issue in music when driving around, and after testing with the cable it didn't occur like this.

    For those that have it "working", does your music play pretty flawlessly, without stops and starts now and then?
     

    Top Liked Posts

    • 1
      AAWireless-aLScWcr6

      My issue is more with constant disconnections, and not the rebooting. But happy to test and see if this fixes the problem.
      I'm not sure that's the same issue. You mean like the device going back to blinking green? Might also just be a defective device. Have you tried it on other cars?
      AAWireless-63c9zZik
      Done
      1
      @PaulyTally you might turn off the feature named 'Reduce tap restriction'. Sometimes the head unit thinks you are stationary when that feature is on, so it does not update as fast.
      1
      Anyone???

      Have you tried changing the USB Mode from MTP to Direct?

      I was having the same problems and I tried many settings, the ones below worked best for me:

      I also have a VW Polo (2020, with MIB2.5) and I managed to get AAWireless after a few mods (in the beginnig, it was not working, or taking very long to connect). I will have they listed here, maybe they can help you out:

      If you have a Samsung phone:
      1. Added AAWireless and AndroidAuto to the list of apps that do not sleep (preveting battery saving features from Samsung phones)
      2. Added a Bixby Routine to press the Home button to wake the Wireless connection as soon as the Bluetooth is connected.
      3. Enabled "show network quality info" in Wi-Fi settings

      On AndroidAuto app
      4. Enabled developer settings
      5. Enabled Wifi projection
      6. Enabled request focus on start

      On AAWireless
      7. Enabled Auto video focus
      8. Changed the USB Mode from MTP to Direct.

      The killer change was number 8 for me.
    • 6
      OTA will be rolled out to second batch devices from next week. This will be version 1.2.2 with some specific WiFi related fixes for the second batch devices. We were planning to release this earlier, but that went all a bit sideways...
      All first batch devices should be able to update to 1.2.0. I fixed a bug in the backend few days ago which caused the 1.2.0 not being shown for some. If the update still does not show, please create a support ticket and provide your device name so we can investigate :)
      5
      Are there guys who would like to test a possible VW/VAG crash fix? Please pass me your device name (AAWireless-xxxxx).
      5
      For all users who have frequent headunit reboots with their VW MIB headunit:

      I noticed that the supplied usb cable was quite loose in the car usb port. A slight touch would disable the connection.

      I then bought a short 30cm USB-IF cable which sits in the USB A port a little bit more snuggly. (My former official VW cable didn't work at all with AAWireless).

      Then I also enabled "Enable Audio Latency Dump" in the Android Auto developer settings.

      Didn't have a single headunit reboot in two weeks now where before it was usually at least once per drive.

      I don't know if it was the cable or the AA setting - or both. But it's surely worth a try if you have frequent headunit reboots.
      5
      Some edited thoughts on my settings with AAWireless Connect 1.7.0 that may help someone.

      I have a 10.25 Hyundai head unit. I think that the Wireless Projection function of this unit is the same for KIA and Genesis 10.25 inch head units. This head unit first appeared in 2019 Korean model years and is very flexible when used with with AAWireless.

      Here are the settings in the AAWireless Connect app version 1.7.0 that I use and what also works with my head unit.

      USB Mode I use MTP, but Direct works as well. The head unit responds a bit faster with MTP.

      Passthrough I have it turned off. The head unit works with Passthrough turned on, but DPI, Remove tap restriction, Disable Audio Sink, AutoVideo Focus and Developer mode cannot be processed by AAWireless when on. When on the exact encrypted data conversation is transmitted between your phone and the head unit. When off, AAWireless joins the conversation to inject those Experimental Features.

      Force 2.4Ghz I have it turned off. The 5Ghz channel used is 40. This feature will turn off 5Ghz Wi-Fi in favor of 2.4Ghz Wi-Fi on channel 1.

      WiFi connect timeout I now leave this at the default 20 seconds. For a couple of months after the initial conversion to Android 11, my Samsung Galaxy S20 FE 5G phone would not connect to AAWireless on the first try. It would always connect on the second try. Samsung fixed their problem with a subsequent update. But while this was a problem, reducing the WiFi connect timeout to 5 seconds really helped.

      Adjust audio timestamp I have it turned off. The head unit also works with it turned on. Turn this on if you notice things out of sync.

      Change DPI I use 130 to see more of the map. Lower numbers make the area of the map shown larger but the text will be smaller. The number 0 will restore the default used by your phone, head unit combination.

      On my head unit, using the number 103 will put Android Auto into wide mode with map and media side by side. But it is still only displayed in the left portion of the screen, and much of the text is too small for me to read.

      Remove tap restriction I turn this on, it helps me with my on phone music collection. The head unit works with this off. Some other head units will not update your GPS map position properly with this option on.

      Disable Audio Sink I have this turned off. Turning this on will make your phone use something else for audio. In my case it is the phone's speaker.

      Auto video focus I have this turned on. This option tells my Infotainment system to switch to Android Auto when AAWireless connects. I don't have to navigate through the screens to get Android Auto up where I can see it.

      Developer Mode I have this turned off. The head unit works with this turned on. An app update will be needed to correct the text. Frankly, I am not sure what is enabled by setting this on, but Emil is sure some of you will know.

      I often use the app with the AAWireless device plugged into a USB A power source, like a power supply or a charging port in your vehicle. The Android Auto traffic going through the device can make app less responsive.

      When an OTA is available, it is better to download the OTA with the AAWireless device powered off and your phone on WiFi. Once the download has completed, turn on AAWireless, link to it again and upload the OTA to the device.

      I use a large microSD card in my phone (Samsung Galaxy S20 FE 5G) to store my music collection. I play the music with Rocket Music Player. Works very well under Android Auto.

      LeRoy
      4
      Hi All! First of all big thank you for the product, it brings my android auto experience to another level.

      Just one question
      One of the last indiegogo update mentioned upcoming "Connect/disconnect with car" function to prevent connection when car ignition is off, but car usb still has power.

      This is basically my only issue with the device, but can be annoying when I am on the phone and trying to get out of the car.

      I just installed the updated app, but I can't seem to find it. Is it me being lame, or it not implemented yet.

      Thanks a lot, and keep up the great work you are doing!

      Gabor
      We removed it for now, it's not stable enough for the general public. Will be there in version 1.8 of the app.
      We needed to push an new app version with support for OTA updating second batch devices ASAP, so we decided to push an intermediate version. This was all planned two weeks ago, but yeah... That went a bit sideways.
      There will be an Indiegogo update soon with more information.
    • 20
      This thread is dedicated for AAWireless users.

      AAWireless is a device which allows you to transform your existing wired Android Auto compatible unit into a Wireless Android Auto unit.

      General chat, experience sharing and community support should be expected as well as support from the developers of the product: @Snirpo and myself.
      8
      @jahandy

      Here are the LED codes.

      Solid Green, the device is booting, should complete in under 12 seconds. Both the Bluetooth and WiFi are not active until after the boot is completed.

      Blinking Green, the device has activated Bluetooth and is waiting for a WiFi connection from your phone. You will only be able to pair while under blinking green.

      Blinking Blue, the device has fully connected with your phone and is attempting to connect with your head unit via USB.

      Solid Blue, the device is full connected with your phone and the head unit. The first time you connect you may need to set some Android Auto permissions and some head units may also produce prompts for you to answer.

      Red, an error has occurred, the device will attempt recovery after a timeout.

      LeRoy
      6
      Hey all, and thanks so much to the developers for bringing this great product to life!

      I just wanted to share my experience with the setup process because I had a rocky start and maybe someone with similar issues finds it useful. Please don't yell at me if most of it has already been posted! ;-)

      Car: Nissan Leaf MY19 / Phone: Samsung Galaxy S9 (One UI 2.5, Android 10)

      Open Android Auto for phones and activate wireless mode:
      The basic prerequisite is to enable wireless projection in the Android Auto for phones app. So if there's no Android Auto app in your app drawer, first download the app, and enable wireless projection in its settings. If that setting isn't there, activate developer mode by tapping the version number at the bottom of the settings several times. In the menu on the upper right enter developer settings and activate the setting for enabling wireless projection. Return to the main settings, find the new wireless setting and activate it, too.

      Connect to AAWireless via Bluetooth and starting of Android Auto:
      First of, I would have liked a little more insight on how to connect to what exactly.

      The AAWireless config app is actually not necessary but provides some troubleshooting options in case the setup is unsuccessful and offers some tweaks for advanced users.

      The regular process as I understand is the following:
      1) Turn ignition on and connect AAWireless via cable to the car's USB port. Nothing happens on the car's head unit just yet.
      2) Connect the phone to AAWireless via Bluetooth.
      3) The phone should receive WiFi-Settings from AAWireless via Bluetooth and then connect to AAWireless' WiFi without any user input.
      4) Android Auto starts automatically on the phone and becomes available on the car's head unit.
      Now the phone stays connected via both Bluetooth and WiFi.
      From now on whenever the phone is near the AAWireless device it will connect to it automatically and thus activate Android Auto on the phone and the car's head unit.

      Throughout my whole setup process I encountered all kinds of LED states: green, red, blue, blinking steadily, constantly lit and whatnot. Frankly I just ignored the LED because without an official legend I find if futile to try and decipher the meanings.

      No Android Auto after successful Bluetooth connection:
      My first problem arose right after initiating the Bluetooth connection to AAWireless on my phone. Nothing would happen afterwards.
      So I followed the steps outlined in the FAQ:
      When connected via Bluetooth to AAWireless I opened the AAWireless config app which would take a while to read the settings from the device and sometimes nothing would happen. I unplugged, replugged, disconnected, unpaired and re-paired A LOT.

      Finally, I got a working connection by selecting Direct for USB mode and enabling Passthrough mode. After saving and re-plugging the device Android Auto would magically appear on my phone and car.
      But - just once.

      Stops working:

      Now, after having had one successful connection I wanted to test if it works reliably. Thus I unplugged AAWireless for a minute and plugged it back in. The result: again my phone connected via Bluetooth and nothing else happened.
      I tried all kinds of stuff, like deleting the app caches, uninstalling Android Auto, unpairing etc. I got it working again from time to time but not reliably.
      To add insult to injury my husband's OnePlus 3T started Android Auto effortlessly right. away. without. any. hassles. whatsoever. over. and. over.

      So I factory reset my phone!
      I know, no one wants to hear this but it actually helped. I've never done a reset in the 2.5 years I've had my phone and I dreaded it. But after all this time, 200 apps, 2 major Android updates and a lot of general tinkering I didn't have to coerce myself too hard. After resetting the S9 I could easily initiate the connection via Bluetooth, it would connect to WiFi and start Android Auto. Over and over.

      No internet

      Then I ran into the next major problem: the dreaded no internet because WiFi problem. My phone is set to connect to the internet via the cell network in case WiFi is unstable. I also tried the setting in the phone's developer options which keeps the phone connected to mobile data all the time. Both settings didn't change the fact that even though the status bar showed a 4G icon, Google couldn't be reached in Android Auto.

      The solution is another brain melter for me. When the phone informed me that WiFi data was unstable I must instinctively have tapped 'Keep WiFi'. This actually kills mobile data and forces all data requests through the non working WiFi connection! As stupid as it sounds: just ignoring the popup keeps both mobile data and WiFi active while choosing an option will sabotage wireless Android Auto. This is clearly Google's fault because they obviously forgot to code an exception for Android Auto to keep it from throwing this error.

      Now AAWireless seems to work as it should.

      One more thing I had to learn even before going wireless: Samsung's power saving settings can mess up your phone's GPS in Android Auto. It took me a while to figure out that one thing power saver does is it stops the GPS when the phone screen is off. It makes no exception for Android Auto. Thus I could use Maps and Waze on the phone but as soon as I was on Android Auto it would just show me an approximate location and 'jump' from street to street as it only used cell tower data for positioning.

      So, good luck to those who face issues, enjoy your wireless Android Auto to those who got it and got it working and a huge thanks to the team who made AAWireless!
      6
      OTA will be rolled out to second batch devices from next week. This will be version 1.2.2 with some specific WiFi related fixes for the second batch devices. We were planning to release this earlier, but that went all a bit sideways...
      All first batch devices should be able to update to 1.2.0. I fixed a bug in the backend few days ago which caused the 1.2.0 not being shown for some. If the update still does not show, please create a support ticket and provide your device name so we can investigate :)
      6
      I tried again later and still have the same issue with the same settings. Not sure why this happens.
      @DevAuto @vizzze

      I solved my problem !!! Hope it helps you vizzze, and others who experience bad location accuracy / zoom behaviour with Waze.

      Do not activate the tap limit bypass in the experimental features !

      I figured out it is not really just deactivating the limit, but makes the system think the car is stopped. Then GPS location is not accurate, and moreover, Waze doesn't work really well. Google maps seems to handle it better but still, GPS location is still approximative.

      Once this option is deactivated, the experience is actually flawless. Waze is showing acutal speed, GPS location is accurate, zoom behaves normally.

      @DevAuto , IMHO it would be useful to add a disclaimer about this when activating this feature, even if is an experimental one. What I understand here is 100% of the users using the tap limit bypass will experience a bad GPS behaviour, so I'm pretty sure you are going to receive new requests regurlarly.
    Our Apps
    Get our official app!
    The best way to access XDA on your phone
    Nav Gestures
    Add swipe gestures to any Android
    One Handed Mode
    Eases uses one hand with your phone