CarPlay and Android Auto device
-
I have quadlock with wireless charging. Neither samsung or iphone couldnt keep up the whole day
-
I have quadlock with wireless charging. Neither samsung or iphone couldnt keep up the whole day
@Jure-Sirena-0 My exact same setup too
Without charging I get about 4 to 5 hours of battery life while constantly using the app. -
@Con-Hennekens said in CarPlay and Android Auto device:
@Tim-Thompson, If your phone can't handle a days ride in your pocket with the screen off, buy a new one... CarPlay and Android Auto are wireless (nowadays at least), so no cabling needed. The headunit itself of course needs power from the bike.
Have you tried running a navigation app and Android Auto or CarPlay on a phone not plugged into a power source? My experience suggests that a phone consumes a fair amount of power - even with the screen off - in such a scenario. New phone/fresh battery or not, it's likely that a significant power draw will be experienced on anything other than a fairly short trip. I personally don't fancy arriving at my destination - or worse an intermediate stop with potentially no opportunity to recharge - only to find that my phone has been significantly drained. Additionally, I prefer the phone to maintain a fairly healthy state of charge in case it's needed in an emergency while traveling.
@Tim-Thompson said in CarPlay and Android Auto device:
Have you tried running a navigation app and Android Auto or CarPlay on a phone not plugged into a power source?
To be honest: I have not tried that, no. But I think we can agree that the screen on it's brightest setting will always be the highest powerdrain possible. Both my phones will have absolutely no problem surviving more than a day without charging in my pocket. The CAT S52 can even handle at least 4 to 5 hours of navigating on it's brightest setting. My P30 Pro has less battery capacity, but with it's screen off, no youtubing, tiktocking and apping (hey, we are riding...!
) I am sure it will survive a whole day. The trick is not to charge when needed, but to charge to full before leaving EDIT:
Completely unrelated, but triggered from a post in a forum elsewhere:
Many people seem to be desperate to have their USB chargers connected behind the ignition of their bikes, to prevent power leak. I am advocate for connecting it (fused!) directly to the battery. Buy a charger with integrated switch, or buy a separate switch. I use this sometimes to charge my bluetooth headset while having a coffee break. That is otherwise impossible without the engine running. You can easily charge a phone this way too of course.I am just an enthusiastic MRA user, and hope you will be one too!
Most motorcycle problems are caused by the nut that connects the handlebar to the saddle.
Streetpilot 2610/Zumo 660/Zumo 395/ CAT S52 + MRA app -
@Tim-Thompson said in CarPlay and Android Auto device:
Have you tried running a navigation app and Android Auto or CarPlay on a phone not plugged into a power source?
To be honest: I have not tried that, no. But I think we can agree that the screen on it's brightest setting will always be the highest powerdrain possible. Both my phones will have absolutely no problem surviving more than a day without charging in my pocket. The CAT S52 can even handle at least 4 to 5 hours of navigating on it's brightest setting. My P30 Pro has less battery capacity, but with it's screen off, no youtubing, tiktocking and apping (hey, we are riding...!
) I am sure it will survive a whole day. The trick is not to charge when needed, but to charge to full before leaving EDIT:
Completely unrelated, but triggered from a post in a forum elsewhere:
Many people seem to be desperate to have their USB chargers connected behind the ignition of their bikes, to prevent power leak. I am advocate for connecting it (fused!) directly to the battery. Buy a charger with integrated switch, or buy a separate switch. I use this sometimes to charge my bluetooth headset while having a coffee break. That is otherwise impossible without the engine running. You can easily charge a phone this way too of course.@Con-Hennekens said in CarPlay and Android Auto device:
@Tim-Thompson said in CarPlay and Android Auto device:
Have you tried running a navigation app and Android Auto or CarPlay on a phone not plugged into a power source?
To be honest: I have not tried that, no. But I think we can agree that the screen on it's brightest setting will always be the highest powerdrain possible. Both my phones will have absolutely no problem surviving more than a day without charging in my pocket. The CAT S52 can even handle at least 4 to 5 hours of navigating on it's brightest setting. My P30 Pro has less battery capacity, but with it's screen off, no youtubing, tiktocking and apping (hey, we are riding...!
) I am sure it will survive a whole day. The trick is not to charge when needed, but to charge to full before leaving EDIT:
Completely unrelated, but triggered from a post in a forum elsewhere:
Many people seem to be desperate to have their USB chargers connected behind the ignition of their bikes, to prevent power leak. I am advocate for connecting it (fused!) directly to the battery. Buy a charger with integrated switch, or buy a separate switch. I use this sometimes to charge my bluetooth headset while having a coffee break. That is otherwise impossible without the engine running. You can easily charge a phone this way too of course.Yes... Certainly the screen on fully bright (typical during day time riding/navigating) is going to be a significant power drain. If memory serves, the drain from running with the screen off, Android Auto on and using a Navigation app still consumes a non-trivial amount of power. This is with a USB connection. I can't say for sure what the impact would be if using WiFi for the data connection. Could it be worse? Maybe.
One thing I do to protect the phone battery is to manage charging and battery temperature. Theory has it that one can extend Lithium battery life by keeping charge cycles limited to between 20% and 80%. You can manage battery charging on an Android device via software or hardware/software combination. The software only option requires rooting the phone (I would need a more compelling reason than this one application to root the phone). The other option is use something like a Chargie (hardware/software solution).
Chargie allows you to manage charging, rate of charge, and battery temperature. One feature it has is called Android Auto mode. If this is not set to "on" when using it in the car, then the phone will not recharge (go back into charging mode ) after hitting the low threshold (in my case - generally set to 77%) to reinitiate charging.
So why am I telling you all this? Well, this is how I know that the battery drain impact of running Android Auto and a Navigation app without external power to the phone is non-trivial. I've missed the Chargie's Android Auto mode not being set to "on" a couple of times on my way to work and saw the results when I got there.
I understand the appeal of such a device as this Elebest unit. It appears to be designed for the harsher conditions (rain, temperature, etc.) that is experienced when riding. So that's a plus - perhaps a solution to common problems. Certainly might reduce wear and tear on the phone in these respects. However, the power issue with the associated/still needed phone is an issue in my mind. Like I said, maintaining the phone in a healthy state of charge while riding is a requirement for me. Anything that will significantly drain it during a day long outing/while traveling is a unacceptable problem in my book. A practical solution would be required here. In the end, the hassle of such a solution might not be worth it. Instead I'd just use the phone as I currently do now.
As to the Chargie... They came out with a smaller, inline Chargie C unit that makes installation on the bike viable. I should also note that Chargie supports both Android and iOS. However, it doesn't not have an equivalent to the Android Auto mode for CarPlay.
-
@Con-Hennekens said in CarPlay and Android Auto device:
@Tim-Thompson said in CarPlay and Android Auto device:
Have you tried running a navigation app and Android Auto or CarPlay on a phone not plugged into a power source?
To be honest: I have not tried that, no. But I think we can agree that the screen on it's brightest setting will always be the highest powerdrain possible. Both my phones will have absolutely no problem surviving more than a day without charging in my pocket. The CAT S52 can even handle at least 4 to 5 hours of navigating on it's brightest setting. My P30 Pro has less battery capacity, but with it's screen off, no youtubing, tiktocking and apping (hey, we are riding...!
) I am sure it will survive a whole day. The trick is not to charge when needed, but to charge to full before leaving EDIT:
Completely unrelated, but triggered from a post in a forum elsewhere:
Many people seem to be desperate to have their USB chargers connected behind the ignition of their bikes, to prevent power leak. I am advocate for connecting it (fused!) directly to the battery. Buy a charger with integrated switch, or buy a separate switch. I use this sometimes to charge my bluetooth headset while having a coffee break. That is otherwise impossible without the engine running. You can easily charge a phone this way too of course.Yes... Certainly the screen on fully bright (typical during day time riding/navigating) is going to be a significant power drain. If memory serves, the drain from running with the screen off, Android Auto on and using a Navigation app still consumes a non-trivial amount of power. This is with a USB connection. I can't say for sure what the impact would be if using WiFi for the data connection. Could it be worse? Maybe.
One thing I do to protect the phone battery is to manage charging and battery temperature. Theory has it that one can extend Lithium battery life by keeping charge cycles limited to between 20% and 80%. You can manage battery charging on an Android device via software or hardware/software combination. The software only option requires rooting the phone (I would need a more compelling reason than this one application to root the phone). The other option is use something like a Chargie (hardware/software solution).
Chargie allows you to manage charging, rate of charge, and battery temperature. One feature it has is called Android Auto mode. If this is not set to "on" when using it in the car, then the phone will not recharge (go back into charging mode ) after hitting the low threshold (in my case - generally set to 77%) to reinitiate charging.
So why am I telling you all this? Well, this is how I know that the battery drain impact of running Android Auto and a Navigation app without external power to the phone is non-trivial. I've missed the Chargie's Android Auto mode not being set to "on" a couple of times on my way to work and saw the results when I got there.
I understand the appeal of such a device as this Elebest unit. It appears to be designed for the harsher conditions (rain, temperature, etc.) that is experienced when riding. So that's a plus - perhaps a solution to common problems. Certainly might reduce wear and tear on the phone in these respects. However, the power issue with the associated/still needed phone is an issue in my mind. Like I said, maintaining the phone in a healthy state of charge while riding is a requirement for me. Anything that will significantly drain it during a day long outing/while traveling is a unacceptable problem in my book. A practical solution would be required here. In the end, the hassle of such a solution might not be worth it. Instead I'd just use the phone as I currently do now.
As to the Chargie... They came out with a smaller, inline Chargie C unit that makes installation on the bike viable. I should also note that Chargie supports both Android and iOS. However, it doesn't not have an equivalent to the Android Auto mode for CarPlay.
@Tim-Thompson said in CarPlay and Android Auto device:
I can't say for sure what the impact would be if using WiFi for the data connection. Could it be worse? Maybe.
I don't think so, because most people work on wifi the whole day also when NOT riding their bike. The navigation software will of course consume power, but so does spotify and youtube and ticktock what people listen to or watch almost continuously. And following my earlier tip about charging while having a break will most likely prevent a to high drain. But yes, it wil have it's cons and pros.
I am just an enthusiastic MRA user, and hope you will be one too!
Most motorcycle problems are caused by the nut that connects the handlebar to the saddle.
Streetpilot 2610/Zumo 660/Zumo 395/ CAT S52 + MRA app -
@Tim-Thompson said in CarPlay and Android Auto device:
I can't say for sure what the impact would be if using WiFi for the data connection. Could it be worse? Maybe.
I don't think so, because most people work on wifi the whole day also when NOT riding their bike. The navigation software will of course consume power, but so does spotify and youtube and ticktock what people listen to or watch almost continuously. And following my earlier tip about charging while having a break will most likely prevent a to high drain. But yes, it wil have it's cons and pros.
So anybody tried one of these out yet?
Seen another variant under various names...
-
Morning,
no I haven´t tryed yet, because the Elebest device is not available at the moment. (maybe end of Feb.)
I have contacted Elebest and they are willing to provide a test sample for some weeks. 1. When they can ship 2. When Navigation Next is CarPlay capable.
I will provide a test report, then.I prefer the Elebest device, because it has a 7inch display and a German/Europeen contact.
I am not sure what support will be provided for the other devices, may be none.Hardware
iPhone 12 pro (iOS 17.0.2)
Oukitel RT3 (Andr. 12)
Samsung Galaxy XCover 4 (Andr. 9 Pie)
Wireless CarPlay mit (Elebest C650)
Wired CarPlay (SEAT Arona - 2021)
For more information, click here -
@Corjan-Meijerink
When do you think is Carplay ready to test? (approx.)Hardware
iPhone 12 pro (iOS 17.0.2)
Oukitel RT3 (Andr. 12)
Samsung Galaxy XCover 4 (Andr. 9 Pie)
Wireless CarPlay mit (Elebest C650)
Wired CarPlay (SEAT Arona - 2021)
For more information, click here -
@Corjan-Meijerink
When do you think is Carplay ready to test? (approx.)@Jörgen We're still aiming for a first Beta version at the end of this month / beginning next
-
Thanks.
What a work spirit, working on Sunday.
Hardware
iPhone 12 pro (iOS 17.0.2)
Oukitel RT3 (Andr. 12)
Samsung Galaxy XCover 4 (Andr. 9 Pie)
Wireless CarPlay mit (Elebest C650)
Wired CarPlay (SEAT Arona - 2021)
For more information, click here -
@Jörgen Drinking coffee and updating the forum
Nice and calm Sunday! -
So I've been digging into these things a little more...
Noted on the Maxca site that the OS is Linux. Also, found out that they support both wired and wireless Android Auto and CarPlay.
Searching around, I've found reports of roughly 10%/hour (some more, some less) phone battery drain using wireless Android Auto. I might find that unacceptable. They say on a charger, the phone will run hot while running wireless AA.
The wired option may be important. I did a quick test running Android Auto with no power (using my Chargie to facilitate this test). It consumed about 1% in roughly 1/2 hour. If this is indeed representative, then 2 to 3 percent battery usage in an hour wouldn't be bad. I might do some longer runs to confirm this.
So... You'd have to wire the provided power supply harness into the bike's accessory power (might also be able to use the bike's USB port). Then you'd need to run a USB cable to where the phone is. Hmmm... What would make for a good setup here? Perhaps I could mount a windshield bag on my Heritage and toss the phone in it. The USB cable run from the windshield bag to a device like this might not be too bad. A little kludgy, but perhaps acceptable.
One potential important use case... Cold weather riding. They say not to charge your phone when it's cold, which is generally not a problem. In times past, I haven't used my phone on the bike during the winter. However, I've done a couple of rides beta testing MRA this year. I've noted that charging performance appears to be poor when it gets cold enough. So, one of these things might be useful here.
Hot weather riding might also see a benefit for obvious reasons.
-
So I've been digging into these things a little more...
Noted on the Maxca site that the OS is Linux. Also, found out that they support both wired and wireless Android Auto and CarPlay.
Searching around, I've found reports of roughly 10%/hour (some more, some less) phone battery drain using wireless Android Auto. I might find that unacceptable. They say on a charger, the phone will run hot while running wireless AA.
The wired option may be important. I did a quick test running Android Auto with no power (using my Chargie to facilitate this test). It consumed about 1% in roughly 1/2 hour. If this is indeed representative, then 2 to 3 percent battery usage in an hour wouldn't be bad. I might do some longer runs to confirm this.
So... You'd have to wire the provided power supply harness into the bike's accessory power (might also be able to use the bike's USB port). Then you'd need to run a USB cable to where the phone is. Hmmm... What would make for a good setup here? Perhaps I could mount a windshield bag on my Heritage and toss the phone in it. The USB cable run from the windshield bag to a device like this might not be too bad. A little kludgy, but perhaps acceptable.
One potential important use case... Cold weather riding. They say not to charge your phone when it's cold, which is generally not a problem. In times past, I haven't used my phone on the bike during the winter. However, I've done a couple of rides beta testing MRA this year. I've noted that charging performance appears to be poor when it gets cold enough. So, one of these things might be useful here.
Hot weather riding might also see a benefit for obvious reasons.
@Tim-Thompson I rode in the freezing cold this year - battery charging was terrible. On the quadlock wireless charger, my iPhone was dead within approx 20 minutes.
As soon as it was inside again and I connected a normal charger it indicated a level of around 70% - leading to the simple conclusion that the phone cannot handle such temps and the battery indication goes bananas
leading to a shutdown 
Riding in hot / cold weather with a phone on your handlebar can be very challenging regardless of the apps you use. To benchmark MRA, we always test in cars as the weather (especially current season) impacts tests too much.
-
Did a 1 hour test run with my Pixel 5a. It was connected to Android Auto via USB cable, but with no power (battery only). Waze was used for navigation. Car temperature was 70 degrees F. Battery dropped from 76% to 69% - 7%/hour.
Not great in my opinion. Could imagine worse results in extreme temperatures. Road trips with long days might put a significant hit on the phone's battery. Not sure I'd want to do this too often (wear and tear on battery).
I'd be curious to see what wireless Android Auto would do to the phone while plugged in. Probably have the phone setup not to quick charge for this experiment (~1.5 to 2 amps max). Would the phone get hot?
Of course, similar experiment with an iPhone, CarPlay and MRA/Scenic would be interesting. How would the iPhone fair here? Heat?
-
Morning,
no I haven´t tryed yet, because the Elebest device is not available at the moment. (maybe end of Feb.)
I have contacted Elebest and they are willing to provide a test sample for some weeks. 1. When they can ship 2. When Navigation Next is CarPlay capable.
I will provide a test report, then.I prefer the Elebest device, because it has a 7inch display and a German/Europeen contact.
I am not sure what support will be provided for the other devices, may be none.Garmin Zumo XT2/XT/BMW Connected Ride Navigator/MyRouteapp (The App)
Een dag niet gelachen is een dag niet geleefd / Een route is net zo goed als deze uitgezet is. -
Pondering...
I probably wouldn't want to typically run wireless Android Auto or CarPlay on a phone without power, assuming a battery discharge rate of ~ 10%/hour. This is particularly so traveling all day.
So, what about with the phone powered? Suppose that battery heat generated while running wireless AA or CP isn't much more than is currently experienced with wired AA/CP in the car (which isn't much). Currently my setup in the car (or the bike) doesn't do any kind of fast charging. Charging current is currently limited to ~1.5 amps. If demand/heat isn't much of a factor in this scenario, then it might be feasible.
I guess the question is, what am I gaining with such a device? I don't listen to music or take phone calls while riding. I currently just use my phone for navigation.
I suppose that heat and direct sun exposure could be minimized if the phone was tucked away. You wouldn't be using the phone's screen. I have to wonder if the battery temperature experienced would be significantly different (direct use of the phone vs. driving wireless AA/CP). My phone gets plenty of wind when riding/navigating. But I have to admit, I'm not sure how hot it is running. I can't recall it ever being warm to the touch. However, my memory may not be worth much in this case.
In the cold, I suppose I would need to use my phone without charging/being plugged in. In this case, it might prevent a significant hit on the battery if it was just driving wireless AA/CP etc. Otherwise just using the phone directly for navigation might put a whammy on the battery pretty quickly. However, how much do I really ever need navigation during cold weather riding? Not often. I generally ride fairly local during the winter months. But it would be nice to have it if needed.
So I guess the benefits would be...
- Minimizing phone's exposure to heat and the elements during the summer. Maybe a reduction in battery temps experienced.
- Getting more time/range during cold weather riding with phone unpowered.
I can sort of see some value... Maybe.
Did I miss something?
-
Pondering...
I probably wouldn't want to typically run wireless Android Auto or CarPlay on a phone without power, assuming a battery discharge rate of ~ 10%/hour. This is particularly so traveling all day.
So, what about with the phone powered? Suppose that battery heat generated while running wireless AA or CP isn't much more than is currently experienced with wired AA/CP in the car (which isn't much). Currently my setup in the car (or the bike) doesn't do any kind of fast charging. Charging current is currently limited to ~1.5 amps. If demand/heat isn't much of a factor in this scenario, then it might be feasible.
I guess the question is, what am I gaining with such a device? I don't listen to music or take phone calls while riding. I currently just use my phone for navigation.
I suppose that heat and direct sun exposure could be minimized if the phone was tucked away. You wouldn't be using the phone's screen. I have to wonder if the battery temperature experienced would be significantly different (direct use of the phone vs. driving wireless AA/CP). My phone gets plenty of wind when riding/navigating. But I have to admit, I'm not sure how hot it is running. I can't recall it ever being warm to the touch. However, my memory may not be worth much in this case.
In the cold, I suppose I would need to use my phone without charging/being plugged in. In this case, it might prevent a significant hit on the battery if it was just driving wireless AA/CP etc. Otherwise just using the phone directly for navigation might put a whammy on the battery pretty quickly. However, how much do I really ever need navigation during cold weather riding? Not often. I generally ride fairly local during the winter months. But it would be nice to have it if needed.
So I guess the benefits would be...
- Minimizing phone's exposure to heat and the elements during the summer. Maybe a reduction in battery temps experienced.
- Getting more time/range during cold weather riding with phone unpowered.
I can sort of see some value... Maybe.
Did I miss something?
@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
-
Morning,
no I haven´t tryed yet, because the Elebest device is not available at the moment. (maybe end of Feb.)
I have contacted Elebest and they are willing to provide a test sample for some weeks. 1. When they can ship 2. When Navigation Next is CarPlay capable.
I will provide a test report, then.I prefer the Elebest device, because it has a 7inch display and a German/Europeen contact.
I am not sure what support will be provided for the other devices, may be none.@Jörgen I would be really interested to know how you get on with the device.
Kind Regards. Help where I can.
Ducati Multistrada V4 Rally
iPhone 15 Pro
Chigee AIO-5 Play
Google Pixel 6 Pro - mounted on SP Connect Plus
Ex Garmin XT2 and XT1 as well as Ex TomTom Rider User -
@Dave-J-0 as soon as MRA Next is CarPlay ready, I will contact Elebest again.
-
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.
