I use Android Auto extensively in the car including streaming music via Spotify and my 12 month average data usage is 0.9 GB from a 12gb contract (Tesco) sim only. I would imagine that Spotify uses about 80% of what I actually use. I tend to leave the maps on even if I'm not navigating but google maps caches the area you spend most time in automatically anyway.
FWIW I have Android Auto on my Africa Twin and still tend to use my Zumo XT for navigation as there is a bit of messing about with some nav apps (MRA) making sure that the route has started before you connect the phone to AA. I've also tried OSMand+ on AA and it is currently better integrated to AA than MRA. The Honda also uses a wired connection which is good as it keeps the phone charged but bad as there is no provision for the phone. I use an old Lowpro camera belt bag strapped to the handlebars. The cable can disconnect intermittently on bumpy roads.
I can understand that folk like the big screen of AA/Carplay head units but to me it just introduces an extra level of complication and potential failure between the Bluetooth connection to the phone and from the unit to the headset. The likes of CARPE ITER PAD seems a better solution in that it runs the nav apps natively but it is darned expensive. If I was in the market, I think I would look at a ruggedised phone perhaps as a secondary device and run the apps that I wanted natively rather than through AA or Car play.
FWIW I have Android Auto on my Africa Twin and still tend to use my Zumo XT for navigation as there is a bit of messing about with some nav apps (MRA) making sure that the route has started before you connect the phone to AA. I've also tried OSMand+ on AA and it is currently better integrated to AA than MRA. The Honda also uses a wired connection which is good as it keeps the phone charged but bad as there is no provision for the phone. I use an old Lowpro camera belt bag strapped to the handlebars. The cable can disconnect intermittently on bumpy roads.
I can understand that folk like the big screen of AA/Carplay head units but to me it just introduces an extra level of complication and potential failure between the Bluetooth connection to the phone and from the unit to the headset. The likes of CARPE ITER PAD seems a better solution in that it runs the nav apps natively but it is darned expensive. If I was in the market, I think I would look at a ruggedised phone perhaps as a secondary device and run the apps that I wanted natively rather than through AA or Car play.
. Now that was a good little toy.
