CarPlay and Android Auto device

[Con Hennekens]

@Tim-Thompson, I think these devices are really nice, if they work well. I use a dedicated rugged phone (CAT S52) as a navigation device. If I could do that as easily with one of those headunits, and they work great, I don't see why I would not use one of those. Having already fixed a mount and charger, I don't see a benefit in changing to one of those, but when my CAT needs replacement, I might try one. So keep us posted

[Dave J 0]

@Jörgen I would be really interested to know how you get on with the device.

[Jörgen]

@Dave-J-0 as soon as MRA Next is CarPlay ready, I will contact Elebest again.

[Jure Sirena 0]

I am using iphone 13 and Carplay all the time in my car with Quadlock wireless charger. Absolutely no drain or high temperature (car's original Carplay connected wirelessly with iphone, no cables)

I am using also quadlock wireless charger on motorcycle (same charger behind quadlock wireless head) and never had issues with heat/battery except now in Tunisia for which I reported very high battery drain despite charging in paralel only when using MRA navigation (before the last update)

I use TomtomGO on iphone with carplay support and also tomtom rider 550 on bike

The Carplay will never drain your battery (it is just transfer of image and small data) The app on phone itself shall be the focus of battery consumption, because there it uses gps, bigger data, maps etc

But biggest advantage on this topic is when you use Carplay (or AA) is that phone screen can be locked! This helps phone battery by long way.
It also means that app itself is not accessable, usage of CP/AA intention is for guidance only with very limited functionality, not like on phone where you can 'touch and manage' all.

[Jörgen]

Hi, a short update.
Today I received a Elebest C650 for testing, thanks to Daniel from Elebest.
I did a short test, based on the information from another thread, that these kinds of devices don't have a battery, and do make problems with reconnection.
I concentrate on the reconnect time after power loss.
First, the pairing with the iPhone worked without any issues.
The device will boot and reboot after power loss in about 21sec. in standard mode. In CarPlay it takes 33sec.
So if the devices is connected to your bike, and you start your bike, there will be normally a short power loss, but it takes only 33sec to get the CarPlay App running again. I tested it with TomTom Go App in the car during a short trip and navigation is working fine.
I have not yet tested more, e.g. with Bluetooth headset etc.
Furthermore, I am locking forward to get MRA Next working with Carplay:
I believe there is something coming really great for motorcyclist.
To be continue...

[Jörgen]

@Hans-van-de-Ven-MRA-Master

Which model Hans?

[RetiredWingMan]

I personally don't understand why you would want a Carplay / Android auto device on a bike. The GPS is distracting enough. The phone still needs to run MRA Next. Currently the power draw is excessive meaning it has to be plugged in all the time which causes excess heat. The phone would need to be somewhere allowing it to be cooled. Personally I just use an older phone with no cell service ... just GPS and WiFi. I download routes via Wifi as required and with downloaded maps basically run off line. I'm considering getting a slightly more recent phone that is at least water resistant if not water proof. Older phones can be purchased quite cheaply. My Cardo headset connects to both my GPS phone as well as my primary phone.

[Tim Thompson]

This post is deleted!

[Tim Thompson]

@Doug-Robinson said in CarPlay and Android Auto device:

I personally don't understand why you would want a Carplay / Android auto device on a bike. The GPS is distracting enough. The phone still needs to run MRA Next. Currently the power draw is excessive meaning it has to be plugged in all the time which causes excess heat. The phone would need to be somewhere allowing it to be cooled. Personally I just use an older phone with no cell service ... just GPS and WiFi. I download routes via Wifi as required and with downloaded maps basically run off line. I'm considering getting a slightly more recent phone that is at least water resistant if not water proof. Older phones can be purchased quite cheaply. My Cardo headset connects to both my GPS phone as well as my primary phone.

I've asked that question as well. I can see both sides of the argument.

I suppose one could use an old phone. But you are stuck I suppose with an old/no longer supported operating system. Eventually, have to wonder about future compatibility issues. Then of course the old phone - just as a new phone - is likely going to suffer battery/heat issues in the summer. In the winter, the phone's charging system likely won't keep up with the power demand and will have cold temp charging issues (damage).

If... Let me say that again... If... the wireless CP/AA power demand on the phone is similar to what's experienced running wired CP/AA in a car, then it might be something to take note of. Plug the phone in, toss it into the windshield bag and off you go. Phone is protected, out of the elements, and power demand (and generated heat) is as minimal as experienced running CP/AA in a car.

Plus... CP/AA provide a nice interface to use on a bike. Big buttons that make wearing gloves less of an issue. I know Scenic works very well on CP. I suspect MRA will also (and AA too). This pretty much gives bikes without HD's Boom Box (or pick your brand/poison) the possibility to have the same experience.

Plus... These devices are cheap (~ $125.00). They are supposedly IPX7 rated. I've not seen any environmental testing standards claimed. But assuming they do in fact hold up over time. Meh... Why not let a device like this take the beating?

I don't listen to music or talk on phones while riding. So, any advantage CP/AA would bring to the table in this arena would be lost on me.

I'm also intrigued with the Beeline Moto... Have to wonder... at the end of the day which will win out. An AA/CP front end or a super simple, diminutive device like the Beeline? Testing/time will tell.

[Hans van de Ven MR.MRA]

@Jörgen

Elebest Motorrad Wireless CarPlay Navigator - 7-Zoll-Display - Apple CarPlay & Android Navigation

Received it yesterday

[Tim Thompson]

Well... Got a delivery notice that my unit has arrived. I got the BINIZE (Does the brand name even matter? It's the same unit sold under multiple brand names.) 5" unit.

I'll be attempting to do a less permanent install on the Heritage so that I can give it a whirl. I'll be testing the Beeline at the same time. It should be interesting.

One of the first curiosities to satisfy will be to determine what kind of hit that wireless AA/CP puts on my unpowered phone. We'll see.

As an aside... Did a test run with the Beeline and phone unpowered. It drained the phone battery 3% in 45 minutes. Maybe extrapolate 4% to 5% per hour. Not too shabby. One's mileage may vary - depending on the phone's battery capacity, battery health, etc. More testing to do.

[Tim Thompson]

Ok... Got to play with the toy today. Set it up in the car.

Quick summary - Overall it worked well. So far, nothing to complain about.

I did the testing today using an iPhone 12. Phone was unpowered for all testing. Navigation app used in CP - Scenic. Power drain on the phone was 9% in an hour. About what I expected. The phone never warmed up - remained cool the entire time. Overall I would say this is satisfactory. However, I would provide power to the phone on long days or when traveling.

I also tested my Beeline at the same time. It was driven by my unpowered Pixel 5a. Phone battery drain was 4% in an hour. I was pretty pleased with that. I've got an app on this phone that monitors battery temps. Temp was 76 degree after 1 hour. So very little phone battery stress. I would be more free/inclined to ride without powering the phone with the Beeline. However, I'd probably still power the phone on really long days.

One thing mentioned in another thread is the fact that these CP/AA devices don't have an internal battery. Some don't like the notion that the unit restarts/power cycles when you start the engine. Personally I don't see a battery as necessary. The navigation app and route can be queued up on the phone before stepping to the bike. Once this CP/AA device boots up and loads CP/nav app (30 seconds), you're off to the races. Ready to navigate.

I've had no pairing issues. No need to repeat the pair process. Each time I've powered on the device it has automatically connected to my phone and started CP/nav app with no issues.

As to the Beeline... I'm actually kind of torn between the CP/AA device and the Beeline. Both work well and have their advantages and disadvantage. So far, I would say the Beeline is a viable navigation device. It will be the sole navigation device used on my Nightster. The Heritage - IDK. I did have one instance today where uncertainty may have led me to not take a correct turn. However, the Beeline rerouted no problem and I was back on track in no time. Eventually, even if something like this occurs, the thing won't leave you lost.

[Jure Sirena 0]

Myself as I mentioned I lost patience on bike because of this….

I tried again today on 400km trip (on bike again). Just cant accept it without battery. Sorry the restart is so anoying. Again my personal oppinion - and I spent 30-40.000km per year on bike

I am interested to see you try on bike

No issue when I tested in car, there is a different environment….no gear, hands available….

[Tim Thompson]

@Jure-Sirena-0 said in CarPlay and Android Auto device:

Myself as I mentioned I lost patience on bike because of this….

I tried again today on 400km trip (on bike again). Just cant accept it without battery. Sorry the restart is so anoying. Again my personal oppinion - and I spent 30-40.000km per year on bike

I am interested to see you try on bike

No issue when I tested in car, there is a different environment….no gear, hands available….

Yes. I understand the distinction between a bike and a car. However, I generally see no issue with queuing the route up on the phone in advance before donning gear and hoping on the bike. In such a case, the thing would power on after engine start and be ready to go (in 30 seconds) without any further interaction needed from me. Once setup... I expect to have to interact with the device very little during the ride/navigating the route. If I have to make a stop... Well the route's still queued up/running on the phone. It will be there on the CP/AA device in 30 seconds after I start the bike. So... for me at least... I don't see an issue here.

To be fair... testing on the bike is yet to be done. Right now though, I'm not expecting this to be an issue... At least for me.

[Dae 0]

Tried my device for the first time. Obviously I had to use the current version of MRA as Next doesn’t yet have CarPlay.

Overall I’m very impressed. The screen is bright enough and easy to see. No problems with disconnections etc.

Yes, the device reboots when cranking the engine as the GS cuts accessory power during crank. However, it didn’t bother me in the slightest. I’d already started the route on the phone so when the device came back on everything was good to go. It took no longer than about 30s. That’s less time than is necessary to get to the car park exit etc so not an issue. Yes, it would be better if the device had a capacitor or something to bridge the few seconds of power cut while cranking but it’s no big deal.

It will take some time coming from the BMW nav as I can no longer control it using the BMW wonderwheel. However, since the Nav died from the dreaded ghost touches issue and is out of warranty it kind of forced the issue.

[Jure Sirena 0]

@Dae-0
I will play with the device a bit more, I will try to add small powerbank. The shop that I wanted to return the device admitted their description did not have anywhere description it had no battery so instead of return they offered 50€ refund. i ll take it and play a bit.
New tiger has a powerbank space under seat with the usb port so its easy to connect it in between usb port and device

[RetiredWingMan]

@Jure-Sirena-0 why not just power the unit from the battery directly (fused) rather than using a switched power source?

[Jure Sirena 0]

@Doug-Robinson
Then you need to power on off manualy everytime, plus question of short….battery consumption. Ok you can remove the device from cradle but power is still there on pins.

The device should work with based on contact, like many devices do, but they can go also to standby or have a ‘countdown’ choice when they detect power loss. And thats possible only with battery.

There is also question of connectivity when you move away with phone….again needing fuzzling with phone.

I might be a particular person but I want to start the bike and GO.
Currently tomtom rider 550 is doing that for me, because it has standby feature. Goes to sleep with contact off (15 sec option to stay on by clisking cancel) and goes back on from standby with route running after 1 sec when power back on. but its bloody small device (getting old)
Because of 15 sec to standby option even start of of engine when the loss of power happens is compensated

[Jure Sirena 0]

So I already played on table with powerbank on table - and it does the job. BUT I am able to reproduce the connectivity error several times

After 6,7,8 OK reboots connection is lost and it wont come back even if i restart several times, but it will com back if i manually confirm BT:

https://youtu.be/Ab-PKc4LsqQ

recorded issues between ok starts:

• 2 x lost connectivity asking for bt connectivity
• BT on device was OFF, even after 2 restarts, and I could not activate it
• after third attempt BT was back and it asked for reconnectivity
• cleared all and repaired....

Randomly this happens.....

What is your FW version?

[Jörgen]

1. I would not recommend direct connection of the device to the battery. The 12 to 5 Volt converter needs power even in idle mode (without a device).

It looks like my version is newer. May be depends on supplier.