Portable waterproof CarPlay units for your motorcycle - Page 4 - Portable waterproof CarPlay units for your motorcycle - Page 4 - Scenic App Forum: Browse 400+ Topics for Adventure Riders

Keep Moving@keep-moving

1 Post

Member

#61 · 14.04.2023, 17:43

I've been using the EarPeace Original for about two years now. They work great, stay in the ears and really do cut the noise. I can still hear Scenic directions on my Cardo unit. I have a Nolan full face but don't loose the Ear Peace taking the helmet on or off. The Pro ones Guido mentions may be even better. https://www.amazon.com/dp/B076VVV5WJ/ref=emc_b_5_t?th=1

2BTSquared@2btsquared

63 Posts

Member

#62 · 16.04.2023, 06:45

Quote from 2BTSquared on 16.04.2023, 06:45

Quote from Guido on 17.03.2023, 13:43

Second ride with the Maxca today. It was a ride of 1.5 hours. I did not experience any connection drops like on my first ride (see above).
I can only assume this is because I followed the recommendation of Maxca (to 'forget' my cardo in my phone's Bluetooth settings), see above as well. This is a bit of a nuisance because now I have to pair the Cardo to my phone temporarily every time I want to use it with the Cardo app and every time I want to use the Cardo with my phone, but without the Maxca (e.g. when I don't need navigation I don't need the Maxca for guidance, but I would like some music).

I did experience some very short audio drops just when I left my house. I'm not too worried about this though, because this also happens in my car (also wireless CarPlay) when I drive away. I'm guessing that's because my home Wifi is going out of range as I drive/ride away... or something related to that.

Before this ride, I updated the maxca firmware to the newest version. This firmware did not have any changes regarding the connection, but it did enable a customizable start-up screen and more detailed volume settings.

To get the latest firmware version you have to send Maxca a message through AliExpress. There's no link anywhere. They are pretty fast to respond though.

One small annoyance I found, but hopefully this was a one time thing. Because I installed the new firmware I had to reconnect my phone to get CarPlay. The first time it was pretty easy:... find the Maxca in your bluetooth settings on your iPhone, then connect. And rest went automatic. It wasn't automatic this time though. Not sure it was because I changed the default bluetooth name of the maxca, or if there was still some left-over bluetooth config on my phone. After about 5 tries I finally got it working. Not exactly sure why, but I turned off the Maxca. Then 'forgot' the maxca in my iPhone bluetooth settings. Turned off my phone, waited 2 minutes and turned it back on again. Then I turned on the maxca. Found it in my iPhone bluetooth settings and connected to it. That time everything went OK and iPhone asked me if I wanted to use the maxca for CarPlay...etc.

Hey @guidomm... My experience so far with the Binize unit/Motikom MPlus seems to has pretty much been the same as yours. I had to forget the Motikom pairing on my phone. I did have some confusion with the pairing process, as I noted in a support email to Binize...

...The Motikom has 3 pairing modes - 1) Intercom pairing, 2) Phone Pairing and 3) Remote Control Pairing. What profiles are used in all that is anybody's guess. It's not really documented anywhere.

Trying to pair with the Binize Unit (Settings/Bluetooth/Discover/Search) in any of the Motikoms MPlus pairing modes fails. Sometimes the Binize Unit will say that it is paired with the Motikom Mplus, but the Motikom MPlus will say that the pairing process failed. Sometimes the Motikcom MPlus will not do or say anything while attempting to pair with the Binize Unit. I do note the following in the Motikom MPlus documentation...

"MPlus is capable of pairing with a third-party Bluetooth device
(e.g. BT headphones, BT intercom device or BT speaker).
However, the proprietary software of the third party BT device must be compatible with MPlus and have HFP profile."

The Binzie Unit has the HFP profile, so I'm uncertain/curious as to why the above method for pairing fails.

Alternatively, I've tried getting the Binize Unit and the Motikcom MPlus to connect via the Bluetooth Emit icon (Bluetooth Search) on the main page. The Motikcom MPlus comes up in the list on that page and I'm able to connect to it (with the Motikom in the Intercom pairing mode). Everything seems to work as expected this way except the maximum audio volume is too low. When the Motikcom MPlus is connected directly to my Pixel 5a phone, audio volume is no problem. The Motikcom will get plenty loud enough.

I've reached out to Binize about the audio volume level being too low. I noted in your reply that the firmware update had some impact on volume. I wonder if this will fix my problem. I guess we'll find out. I've not seen anything in the documentation on how to do the firmware upgrade. What's the process?

Quote from Guido on 17.03.2023, 13:43

Second ride with the Maxca today. It was a ride of 1.5 hours. I did not experience any connection drops like on my first ride (see above).
I can only assume this is because I followed the recommendation of Maxca (to 'forget' my cardo in my phone's Bluetooth settings), see above as well. This is a bit of a nuisance because now I have to pair the Cardo to my phone temporarily every time I want to use it with the Cardo app and every time I want to use the Cardo with my phone, but without the Maxca (e.g. when I don't need navigation I don't need the Maxca for guidance, but I would like some music).

I did experience some very short audio drops just when I left my house. I'm not too worried about this though, because this also happens in my car (also wireless CarPlay) when I drive away. I'm guessing that's because my home Wifi is going out of range as I drive/ride away... or something related to that.

Before this ride, I updated the maxca firmware to the newest version. This firmware did not have any changes regarding the connection, but it did enable a customizable start-up screen and more detailed volume settings.

To get the latest firmware version you have to send Maxca a message through AliExpress. There's no link anywhere. They are pretty fast to respond though.

One small annoyance I found, but hopefully this was a one time thing. Because I installed the new firmware I had to reconnect my phone to get CarPlay. The first time it was pretty easy:... find the Maxca in your bluetooth settings on your iPhone, then connect. And rest went automatic. It wasn't automatic this time though. Not sure it was because I changed the default bluetooth name of the maxca, or if there was still some left-over bluetooth config on my phone. After about 5 tries I finally got it working. Not exactly sure why, but I turned off the Maxca. Then 'forgot' the maxca in my iPhone bluetooth settings. Turned off my phone, waited 2 minutes and turned it back on again. Then I turned on the maxca. Found it in my iPhone bluetooth settings and connected to it. That time everything went OK and iPhone asked me if I wanted to use the maxca for CarPlay...etc.

Hey @guidomm... My experience so far with the Binize unit/Motikom MPlus seems to has pretty much been the same as yours. I had to forget the Motikom pairing on my phone. I did have some confusion with the pairing process, as I noted in a support email to Binize...

...The Motikom has 3 pairing modes - 1) Intercom pairing, 2) Phone Pairing and 3) Remote Control Pairing. What profiles are used in all that is anybody's guess. It's not really documented anywhere.

Trying to pair with the Binize Unit (Settings/Bluetooth/Discover/Search) in any of the Motikoms MPlus pairing modes fails. Sometimes the Binize Unit will say that it is paired with the Motikom Mplus, but the Motikom MPlus will say that the pairing process failed. Sometimes the Motikcom MPlus will not do or say anything while attempting to pair with the Binize Unit. I do note the following in the Motikom MPlus documentation...

"MPlus is capable of pairing with a third-party Bluetooth device
(e.g. BT headphones, BT intercom device or BT speaker).
However, the proprietary software of the third party BT device must be compatible with MPlus and have HFP profile."

The Binzie Unit has the HFP profile, so I'm uncertain/curious as to why the above method for pairing fails.

Alternatively, I've tried getting the Binize Unit and the Motikcom MPlus to connect via the Bluetooth Emit icon (Bluetooth Search) on the main page. The Motikcom MPlus comes up in the list on that page and I'm able to connect to it (with the Motikom in the Intercom pairing mode). Everything seems to work as expected this way except the maximum audio volume is too low. When the Motikcom MPlus is connected directly to my Pixel 5a phone, audio volume is no problem. The Motikcom will get plenty loud enough.

I've reached out to Binize about the audio volume level being too low. I noted in your reply that the firmware update had some impact on volume. I wonder if this will fix my problem. I guess we'll find out. I've not seen anything in the documentation on how to do the firmware upgrade. What's the process?

Guido@guidomm

2,153 Posts

Admin

#63 · 16.04.2023, 07:18

I messaged Maxca through AliExpress for the new firmware. They sent the new firmware file to me and I could update by putting that on a SSD card that I inserted into the Maxca. Through the settings menu on the unit you can then initiate the update.

From sound perspective this added some more volume settings if I remember correctly (I.e. now I can set separate volume levels for music and navigation instructions). Honestly not sure if/how that works if using CarPlay. The volume is OK though for my Cardo. Note that I didn’t have any volume issues before the update either. Even before the update, O could increase volume on the Maxca settings (which I did have to turn to almost max to get same volume as I would get directly from iPhone).

maxdamage00 has reacted to this post.

If you're enjoying Scenic and are happy with the support, please leave a nice rating in the App Store. It would mean a lot to me ❤️

2BTSquared@2btsquared

63 Posts

Member

#64 · 16.04.2023, 09:43

Quote from 2BTSquared on 16.04.2023, 09:43

Quote from Guido on 16.04.2023, 07:18

I messaged Maxca through AliExpress for the new firmware. They sent the new firmware file to me and I could update by putting that on a SSD card that I inserted into the Maxca. Through the settings menu on the unit you can then initiate the update.

From sound perspective this added some more volume settings if I remember correctly (I.e. now I can set separate volume levels for music and navigation instructions). Honestly not sure if/how that works if using CarPlay. The volume is OK though for my Cardo. Note that I didn’t have any volume issues before the update either. Even before the update, O could increase volume on the Maxca settings (which I did have to turn to almost max to get same volume as I would get directly from iPhone).

Thanks for the firmware update tips @guidomm.

Your mention of CarPlay jostled loose a few brain cells. I had been testing/setting things up with my Android Pixel 5a. Other than making sure all the interfaces/pairing worked the same (they do), I didn't dig too far into it with my iPhone. But then I remembered that along with the Binize Unit's System and Navi volume controls, it also had a CarPlay volume control. Naturally the CarPlay volume control did nothing when I was using my Android phone. Then I recalled your previous post about the added volume controls via the firmware update - Android Auto volume being amongst them. Hmmm - wheels turned between the ears and I decided to look a little closer at things when using my iPhone and CarPlay. Sure enough the CarPlay volume control on the Binize unit controls/solves the volume problem. In fact CarPlay volume can be turned up too high on the Binize unit - causing it to produce distortion (regardless of the volume setting on the Motikom). Had to back it down a bit to clear that up. So... All in all... Problem solve-ed.

As to Android Auto. The Binize unit's System volume is the only thing that impacts the volume for Android Auto. Seeing that the new firmware adds an Android Auto volume control suggests that the firmware update may fix the problem with Android Auto.

So thanks Guido for getting the wheels turning.

Quote from Guido on 16.04.2023, 07:18

I messaged Maxca through AliExpress for the new firmware. They sent the new firmware file to me and I could update by putting that on a SSD card that I inserted into the Maxca. Through the settings menu on the unit you can then initiate the update.

From sound perspective this added some more volume settings if I remember correctly (I.e. now I can set separate volume levels for music and navigation instructions). Honestly not sure if/how that works if using CarPlay. The volume is OK though for my Cardo. Note that I didn’t have any volume issues before the update either. Even before the update, O could increase volume on the Maxca settings (which I did have to turn to almost max to get same volume as I would get directly from iPhone).

Thanks for the firmware update tips @guidomm.

Your mention of CarPlay jostled loose a few brain cells. I had been testing/setting things up with my Android Pixel 5a. Other than making sure all the interfaces/pairing worked the same (they do), I didn't dig too far into it with my iPhone. But then I remembered that along with the Binize Unit's System and Navi volume controls, it also had a CarPlay volume control. Naturally the CarPlay volume control did nothing when I was using my Android phone. Then I recalled your previous post about the added volume controls via the firmware update - Android Auto volume being amongst them. Hmmm - wheels turned between the ears and I decided to look a little closer at things when using my iPhone and CarPlay. Sure enough the CarPlay volume control on the Binize unit controls/solves the volume problem. In fact CarPlay volume can be turned up too high on the Binize unit - causing it to produce distortion (regardless of the volume setting on the Motikom). Had to back it down a bit to clear that up. So... All in all... Problem solve-ed.

As to Android Auto. The Binize unit's System volume is the only thing that impacts the volume for Android Auto. Seeing that the new firmware adds an Android Auto volume control suggests that the firmware update may fix the problem with Android Auto.

So thanks Guido for getting the wheels turning.

Guido has reacted to this post.

maxdamage00@maxdamage00

2 Posts

Member

#65 · 16.04.2023, 09:49

Dear @guidomm
Is it possible for you to share the newest firmware for Maxca ?
I need version 202302281613 MAXCA C5 PRO 202302281613.Zip

There are lot of people who bought same device but from other sellers who dont provide relevant FW.
Also, in file Factory.ini you can tweak a lot of stuffs (customize device)

Many thanks

2BTSquared@2btsquared

63 Posts

Member

#66 · 18.04.2023, 07:22

Quote from 2BTSquared on 18.04.2023, 07:22
So I've had a couple of interactions with Binize support on my Android Auto volume problem. Binize support response to me...

Hello
Thanks for your reply and sorry for my late response. After checking
with our tech support team and factory, I regret to inform you that
your headset may not be very compatible with our product. The lower
maximum volume after a successful connection should be due to the
multiple modes of the headset itself. You can try to connect your
phone or other devices in different modes to experiment with the
difference between the maximum volume. Actually, we recommend you use
AirPods to listen to music.

My reply back to them...

Fortunately, I also have an iPhone. I've been able to get all devices - the Binize Unit, the Motikom Mplus and the iPhone - to work/play well together. They all pair and function as expected. So, no I don't believe there is a compatibility issue with the Motikom MPlus (re. headset) and the Binize Unit.

As a reminder, I asked about firmware updates in my original email. The version that I have is EW_YFM_01-202211291221. An updated version is EW_YFM_01-202301311027 (I don't know if this is the latest or not).

As to Android Auto and my Android phone... Everything also works with it - the Binize Unit, the Motikom Mplus and the Pixel 5a. They all pair and function as expected - with one exception. That exception being that there is no way currently to adjust the Android Auto volume (which is currently set too low to be useful). The current firmware version on the Binize Unit provides System volume, Navi volume and CarPlay volume. It doesn't provide Android Auto volume control. The new version of the firmware does...

As can be seen in the attached image... The new firmware version provides Master, Navigation, CarPlay Media, CarPlay Telephone and Android Auto volume controls.

When using my iPhone, I'm able to adjust CarPlay volume and everything works fine (all 3 devices - the Binize Unit, Motilkom MPlus and the iPhone - work nicely together). When using my Android phone, all devices work together as well - except that I can't adjust Android Auto volume (which is set too low). I believe the new firmware might solve this problem. You might be able to confirm this with your tech support team.

Can you provide the updated firmware and procedure for installing it?

Binize support response...

Hello

Thanks for your reply and sorry for the late response due to the big time difference. And Thank you for your detailed email content and logical and clear expression of the problem. After we double-confirmed with the factory, version EW_YFM_01-202211291221 is the latest stable version. Newer beta versions may cause unpredictable problems, so it is not recommended to upgrade. Regarding the Android Auto volume prob, their reply is, “We also received feedback from other customers before, and there is currently no way to solve this problem”. As for the picture you attached, after confirmation, it is not our product. Maybe the UI looks the same, but it is not the same thing.

I've seen this hardware being sold under different brand names Binize, Maxca, Wizcar, Ottocast, and Iorigin to name a few. This screen shot was from a no name brand being sold on Ebay...

Interestingly, that settings page is identical (same versions etc.) to the one on my unit - which is a Binize. It's been an assumption that this is exactly the same product being sold under different brand names. However, perhaps the hardware is the same but there are different flavors of firmware/software depending on the brand. Or perhaps the hardware is different as well (I doubt it). They all look the same, right down to the box they come in appearing to be identical.

So @guidomm do you recall the firmware version that you upgraded from? What did the GUI look like on your unit? Did it look like this?...

So I've had a couple of interactions with Binize support on my Android Auto volume problem. Binize support response to me...

Hello
Thanks for your reply and sorry for my late response. After checking
with our tech support team and factory, I regret to inform you that
your headset may not be very compatible with our product. The lower
maximum volume after a successful connection should be due to the
multiple modes of the headset itself. You can try to connect your
phone or other devices in different modes to experiment with the
difference between the maximum volume. Actually, we recommend you use
AirPods to listen to music.

My reply back to them...

Fortunately, I also have an iPhone. I've been able to get all devices - the Binize Unit, the Motikom Mplus and the iPhone - to work/play well together. They all pair and function as expected. So, no I don't believe there is a compatibility issue with the Motikom MPlus (re. headset) and the Binize Unit.

As a reminder, I asked about firmware updates in my original email. The version that I have is EW_YFM_01-202211291221. An updated version is EW_YFM_01-202301311027 (I don't know if this is the latest or not).

As to Android Auto and my Android phone... Everything also works with it - the Binize Unit, the Motikom Mplus and the Pixel 5a. They all pair and function as expected - with one exception. That exception being that there is no way currently to adjust the Android Auto volume (which is currently set too low to be useful). The current firmware version on the Binize Unit provides System volume, Navi volume and CarPlay volume. It doesn't provide Android Auto volume control. The new version of the firmware does...

As can be seen in the attached image... The new firmware version provides Master, Navigation, CarPlay Media, CarPlay Telephone and Android Auto volume controls.

When using my iPhone, I'm able to adjust CarPlay volume and everything works fine (all 3 devices - the Binize Unit, Motilkom MPlus and the iPhone - work nicely together). When using my Android phone, all devices work together as well - except that I can't adjust Android Auto volume (which is set too low). I believe the new firmware might solve this problem. You might be able to confirm this with your tech support team.

Can you provide the updated firmware and procedure for installing it?

Binize support response...

Hello

Thanks for your reply and sorry for the late response due to the big time difference. And Thank you for your detailed email content and logical and clear expression of the problem. After we double-confirmed with the factory, version EW_YFM_01-202211291221 is the latest stable version. Newer beta versions may cause unpredictable problems, so it is not recommended to upgrade. Regarding the Android Auto volume prob, their reply is, “We also received feedback from other customers before, and there is currently no way to solve this problem”. As for the picture you attached, after confirmation, it is not our product. Maybe the UI looks the same, but it is not the same thing.

I've seen this hardware being sold under different brand names Binize, Maxca, Wizcar, Ottocast, and Iorigin to name a few. This screen shot was from a no name brand being sold on Ebay...

Interestingly, that settings page is identical (same versions etc.) to the one on my unit - which is a Binize. It's been an assumption that this is exactly the same product being sold under different brand names. However, perhaps the hardware is the same but there are different flavors of firmware/software depending on the brand. Or perhaps the hardware is different as well (I doubt it). They all look the same, right down to the box they come in appearing to be identical.

So @guidomm do you recall the firmware version that you upgraded from? What did the GUI look like on your unit? Did it look like this?...

Guido@guidomm

2,153 Posts

Admin

#67 · 18.04.2023, 08:27

My GUI looks different, but the top bar looks the same, and the maxca has 3 different GUIs to choose from. One of them might be the one you have here, but not sure.

Here is the firmware version I received from Maxca... and the instructions to go with it.

IMPORTANT: This is for the Maxca C5. I have only used this to update my Maxca. It might not work on other brands. It might even BRICK YOUR UNIT, so use it at your own risk!

MAXCA C5 PRO 202302281613

INSTRUCTIONS RECEIVED FROM MAXCA:

Here are the change logs:

1,Volume settings ( CarPlay Navigation, CarPlay media, CarPlay Phonecall, Android auto volume)

2, Logo preset ( Settings--Factory--123456--Settings--Logo--123456/000000)

If you dont find these 2 update useful for you, please ignore that.

You may follow the instruction video to do the upgrade:

https://youtu.be/1cVTY9Z28Hk

Tool : USB flash drive or SD card (FAT32, Maximum 32GB)

Upgrade instructions:
1, Unzip "MAXCA C5 PRO 202302281613.Zip", you will get "ISPBOOOT.bin" file, Put it into USB drive /SD Card root directory (Dont put it into any folder)
2, Plug USB drive /SD card into C5 mini USB port or SD card slot
3, Go Settings-system-update-upgrade firmware, click it to start upgrading
4, The system will reboot automatically after upgrade finishes (Around 40s later), or you can reboot it by the power button

If unfortunately your upgrade was failed (power cut, bad quality USB flash drive/SD card-needs to be changed ), and C5 pro became a brick, no worry, please follow this video to do the upgrade again

https://youtu.be/blyduNsPIw0

If you dont find your favor logo inside, you may follow this video to customize the boot logo.
https://youtu.be/SL7ajIhSTS8

Use SD card instead of USB flash drive (FAT32, max 32GB)

maxdamage00 has reacted to this post.

If you're enjoying Scenic and are happy with the support, please leave a nice rating in the App Store. It would mean a lot to me ❤️

Guido@guidomm

2,153 Posts

Admin

#68 · 18.04.2023, 08:31

I'm not 100% sure, but I believe my firmware when I got the Maxca was from December 2022 (so not November as in the screenshot).

If you're enjoying Scenic and are happy with the support, please leave a nice rating in the App Store. It would mean a lot to me ❤️

2BTSquared@2btsquared

63 Posts

Member

#69 · 18.04.2023, 10:03

Quote from 2BTSquared on 18.04.2023, 10:03

Quote from Guido on 18.04.2023, 08:27

My GUI looks different, but the top bar looks the same, and the maxca has 3 different GUIs to choose from. One of them might be the one you have here, but not sure.

Here is the firmware version I received from Maxca... and the instructions to go with it.

IMPORTANT: This is for the Maxca C5. I have only used this to update my Maxca. It might not work on other brands. It might even BRICK YOUR UNIT, so use it at your own risk!

MAXCA C5 PRO 202302281613

INSTRUCTIONS RECEIVED FROM MAXCA:

Here are the change logs:

1,Volume settings ( CarPlay Navigation, CarPlay media, CarPlay Phonecall, Android auto volume)

2, Logo preset ( Settings--Factory--123456--Settings--Logo--123456/000000)

If you dont find these 2 update useful for you, please ignore that.

You may follow the instruction video to do the upgrade:

https://youtu.be/1cVTY9Z28Hk

Tool : USB flash drive or SD card (FAT32, Maximum 32GB)

Upgrade instructions:
1, Unzip "MAXCA C5 PRO 202302281613.Zip", you will get "ISPBOOOT.bin" file, Put it into USB drive /SD Card root directory (Dont put it into any folder)
2, Plug USB drive /SD card into C5 mini USB port or SD card slot
3, Go Settings-system-update-upgrade firmware, click it to start upgrading
4, The system will reboot automatically after upgrade finishes (Around 40s later), or you can reboot it by the power button

If unfortunately your upgrade was failed (power cut, bad quality USB flash drive/SD card-needs to be changed ), and C5 pro became a brick, no worry, please follow this video to do the upgrade again

https://youtu.be/blyduNsPIw0

If you dont find your favor logo inside, you may follow this video to customize the boot logo.
https://youtu.be/SL7ajIhSTS8

Use SD card instead of USB flash drive (FAT32, max 32GB)

Curious... Does your box look the same?

This is probably a long shot... But have your tried yours with Android Auto? If so, can you control Android Auto volume? Doubtful I know. You're probably pretty much iPhone and that's it.

Quote from Guido on 18.04.2023, 08:27

My GUI looks different, but the top bar looks the same, and the maxca has 3 different GUIs to choose from. One of them might be the one you have here, but not sure.

Here is the firmware version I received from Maxca... and the instructions to go with it.

IMPORTANT: This is for the Maxca C5. I have only used this to update my Maxca. It might not work on other brands. It might even BRICK YOUR UNIT, so use it at your own risk!

MAXCA C5 PRO 202302281613

INSTRUCTIONS RECEIVED FROM MAXCA:

Here are the change logs:

1,Volume settings ( CarPlay Navigation, CarPlay media, CarPlay Phonecall, Android auto volume)

2, Logo preset ( Settings--Factory--123456--Settings--Logo--123456/000000)

If you dont find these 2 update useful for you, please ignore that.

You may follow the instruction video to do the upgrade:

https://youtu.be/1cVTY9Z28Hk

Tool : USB flash drive or SD card (FAT32, Maximum 32GB)

Upgrade instructions:
1, Unzip "MAXCA C5 PRO 202302281613.Zip", you will get "ISPBOOOT.bin" file, Put it into USB drive /SD Card root directory (Dont put it into any folder)
2, Plug USB drive /SD card into C5 mini USB port or SD card slot
3, Go Settings-system-update-upgrade firmware, click it to start upgrading
4, The system will reboot automatically after upgrade finishes (Around 40s later), or you can reboot it by the power button

If unfortunately your upgrade was failed (power cut, bad quality USB flash drive/SD card-needs to be changed ), and C5 pro became a brick, no worry, please follow this video to do the upgrade again

https://youtu.be/blyduNsPIw0

If you dont find your favor logo inside, you may follow this video to customize the boot logo.
https://youtu.be/SL7ajIhSTS8

Use SD card instead of USB flash drive (FAT32, max 32GB)

Curious... Does your box look the same?

This is probably a long shot... But have your tried yours with Android Auto? If so, can you control Android Auto volume? Doubtful I know. You're probably pretty much iPhone and that's it.

2BTSquared@2btsquared

63 Posts

Member

#70 · 18.04.2023, 11:32

Right now, I can get by using my work iPhone. So - as to the question about attempting the firmware from Maxca (see @guidomm reply) - I may hold that possibility in my back pocket for a bit. If the need for Android Auto becomes more critical - I may attempt the experiment. It's a gamble that the hardware is exactly the same (appears so - but maybe not). But what the hell? These units are pretty cheap and if I were to brick it with the Maxca firmware... Meh. Buy another one.

I'm going to keep trying to resolve the issue with Binize support. But if I haven't already hit a brick wall with them (likely), I'm guessing I'm about to do so soon.

In the interim... Anybody that comes along this thread... Posterity's sake and all... If Android Auto is a concern, one might want to consider the Maxca over the Binize. It appears Maxca's updated firmware provides the Android Auto volume control where the current firmware on the Binize (at least what they are willing to offer) does not. The updated firmware may solve the Android Auto volume problem - but I have no way of confirming.

Guido@guidomm

2,153 Posts

Admin

#71 · 18.04.2023, 11:39

I have an android phone lying around. I’ll give it a try once I have a bit more time.

If you're enjoying Scenic and are happy with the support, please leave a nice rating in the App Store. It would mean a lot to me ❤️

2BTSquared@2btsquared

63 Posts

Member

#72 · 18.04.2023, 11:42

Quote from Guido on 18.04.2023, 11:39

I have an android phone lying around. I’ll give it a try once I have a bit more time.

Thanks. I'll be interested to see what you find out.

massi@massi

85 Posts

Member

#73 · 19.04.2023, 07:21

The devices are all the same and so is the firmware. I got an Ottocast Lite C5, the box is the same as the box shown above. On my Ottocast was installed a version from January 2023. Unfortunately I flashed an old firmware from november 22 when fiddling around with the Factory.ini (be careful by setting the "SupportQuickUpgrade=" setting, leave it on true).

Installing the firmware, that Guido posted here, on my Ottocast was installing fine, no problems so far.

maxdamage00 has reacted to this post.

2BTSquared@2btsquared

63 Posts

Member

#74 · 19.04.2023, 10:04

Quote from 2BTSquared on 19.04.2023, 10:04

Quote from massi on 19.04.2023, 07:21

The devices are all the same and so is the firmware. I got an Ottocast Lite C5, the box is the same as the box shown above. On my Ottocast was installed a version from January 2023. Unfortunately I flashed an old firmware from november 22 when fiddling around with the Factory.ini (be careful by setting the "SupportQuickUpgrade=" setting, leave it on true).

Installing the firmware, that Guido posted here, on my Ottocast was installing fine, no problems so far.

I suspect that is probably right. However, this is the most recent email I got from Binize support...

Hello
Thanks for your reply and sorry for my late response.

My friend, first of all, sorry for all the inconvenience caused by our
product, and please give me a chance to explain:

Thank you very much for your feedback. We have noticed this problem
according to your feedback, and we have sent your problems to the
software development company already. I understand the lack of Android
auto-tuning is a real headache. Now we only have the latest firmware
file on November 29, 2022. EW_YFM_01-202211291221 like what we
mentioned before. Our suggestion is to wait until the software side
gives us the latest reply before we proceed to the next step. But if
you insist on trying an upgrade first, you can also try a refresh with
the same version.

As you can see, there are many similar versions of the machines we
sell on the market. Although the appearance and some features look the
same, the reality is different. To tell you the truth, making the same
type of product must be a combination of many corresponding parts
developers, and not all the sellers of goods are the same developer.
It's like the phone is made by both Apple and Android.

Sorry again for the inconvenience caused by our products, I will let
you know as soon as the factory has the latest updated documents.

Thanks again.

Binize

There appears to be some language barrier issues etc. but they seem to be trying to imply that there may be differences under the hood... so-to-speak. I'm dubious about that and more inclined to bet that you are right.

Regardless, I'm in no hurry either way. They do seem to imply they are working on getting updated firmware. Right now, my work iPhone will suffice for my needs at the moment. Eventually, I do want to end up using my personal Android phone for these things, so I'll be looking for a solution somewhere down the road. I do have to say though, just satisfying my curiosity is almost enough to get me to risk it and try the firmware Guido provided.

Quote from massi on 19.04.2023, 07:21

The devices are all the same and so is the firmware. I got an Ottocast Lite C5, the box is the same as the box shown above. On my Ottocast was installed a version from January 2023. Unfortunately I flashed an old firmware from november 22 when fiddling around with the Factory.ini (be careful by setting the "SupportQuickUpgrade=" setting, leave it on true).

Installing the firmware, that Guido posted here, on my Ottocast was installing fine, no problems so far.

I suspect that is probably right. However, this is the most recent email I got from Binize support...

Hello
Thanks for your reply and sorry for my late response.

My friend, first of all, sorry for all the inconvenience caused by our
product, and please give me a chance to explain:

Thank you very much for your feedback. We have noticed this problem
according to your feedback, and we have sent your problems to the
software development company already. I understand the lack of Android
auto-tuning is a real headache. Now we only have the latest firmware
file on November 29, 2022. EW_YFM_01-202211291221 like what we
mentioned before. Our suggestion is to wait until the software side
gives us the latest reply before we proceed to the next step. But if
you insist on trying an upgrade first, you can also try a refresh with
the same version.

As you can see, there are many similar versions of the machines we
sell on the market. Although the appearance and some features look the
same, the reality is different. To tell you the truth, making the same
type of product must be a combination of many corresponding parts
developers, and not all the sellers of goods are the same developer.
It's like the phone is made by both Apple and Android.

Sorry again for the inconvenience caused by our products, I will let
you know as soon as the factory has the latest updated documents.

Thanks again.

Binize

There appears to be some language barrier issues etc. but they seem to be trying to imply that there may be differences under the hood... so-to-speak. I'm dubious about that and more inclined to bet that you are right.

Regardless, I'm in no hurry either way. They do seem to imply they are working on getting updated firmware. Right now, my work iPhone will suffice for my needs at the moment. Eventually, I do want to end up using my personal Android phone for these things, so I'll be looking for a solution somewhere down the road. I do have to say though, just satisfying my curiosity is almost enough to get me to risk it and try the firmware Guido provided.

maxdamage00@maxdamage00

2 Posts

Member

#75 · 19.04.2023, 12:24

Quote from Guido on 18.04.2023, 08:27

My GUI looks different, but the top bar looks the same, and the maxca has 3 different GUIs to choose from. One of them might be the one you have here, but not sure.

Here is the firmware version I received from Maxca... and the instructions to go with it.

IMPORTANT: This is for the Maxca C5. I have only used this to update my Maxca. It might not work on other brands. It might even BRICK YOUR UNIT, so use it at your own risk!

MAXCA C5 PRO 202302281613

INSTRUCTIONS RECEIVED FROM MAXCA:

Here are the change logs:

1,Volume settings ( CarPlay Navigation, CarPlay media, CarPlay Phonecall, Android auto volume)

2, Logo preset ( Settings--Factory--123456--Settings--Logo--123456/000000)

If you dont find these 2 update useful for you, please ignore that.

You may follow the instruction video to do the upgrade:

https://youtu.be/1cVTY9Z28Hk

Tool : USB flash drive or SD card (FAT32, Maximum 32GB)

Upgrade instructions:
1, Unzip "MAXCA C5 PRO 202302281613.Zip", you will get "ISPBOOOT.bin" file, Put it into USB drive /SD Card root directory (Dont put it into any folder)
2, Plug USB drive /SD card into C5 mini USB port or SD card slot
3, Go Settings-system-update-upgrade firmware, click it to start upgrading
4, The system will reboot automatically after upgrade finishes (Around 40s later), or you can reboot it by the power button

If unfortunately your upgrade was failed (power cut, bad quality USB flash drive/SD card-needs to be changed ), and C5 pro became a brick, no worry, please follow this video to do the upgrade again

https://youtu.be/blyduNsPIw0

If you dont find your favor logo inside, you may follow this video to customize the boot logo.
https://youtu.be/SL7ajIhSTS8

Use SD card instead of USB flash drive (FAT32, max 32GB)

Thank you very much for sharing this !

jmossfeld@jmossfeld

2 Posts

Member

#76 · 23.04.2023, 09:19

Hi all! I now have one of these generic units (the box says “Road Top”) from eBay. I can get Scenic to show up in CarPlay just fine, but the navigation voice only plays through the screen’s speaker, not through my Cardo headset. I did pair the Cardo unit, and it even shows up on the “paired” list of the screen’s Bluetooth settings, but there doesn’t seem to be an active connection. Anyone else have this issue and a possible solution? I’ve messaged the seller through eBay, but I do not have high hopes of a legible response.

FYI, although the included RAM-style mount looks solid, I already had a QuadLock mount on my bike (and one on my bicycle, for my phone), so I stuck one of QuadLock’s universal plates on the back of the screen bracket, and it seems to work fine. I can still easily swap out the screen for my phone if needed.

Guido@guidomm

2,153 Posts

Admin

#77 · 23.04.2023, 09:26

I have the Maxca C5 pro, and a Cardo Freecom 4x. It works fine for me. Check that your Cardo is not also paired with your phone (caused connection dropouts with the Maxca for me). Also check common reasons for not having voice in Scenic: https://scenic.app/help/no-voice-guidance-instructions/

If you're enjoying Scenic and are happy with the support, please leave a nice rating in the App Store. It would mean a lot to me ❤️

mbirth@mbirth

36 PostsTopic Author

Member

#78 · 23.04.2023, 12:41

Quote from jmossfeld on 23.04.2023, 09:19

I did pair the Cardo unit, and it even shows up on the “paired” list of the screen’s Bluetooth settings, but there doesn’t seem to be an active connection.

Make sure you have a motorcycle unit with 2 Bluetooth modules. The Cardo has to be paired in the "Transmit BT", "Bluetooth Emit" or "BT Helmet" menu, NOT in the normal system settings.

2BTSquared@2btsquared

63 Posts

Member

#79 · 23.04.2023, 14:20

Quote from mbirth on 23.04.2023, 12:41

Quote from jmossfeld on 23.04.2023, 09:19

I did pair the Cardo unit, and it even shows up on the “paired” list of the screen’s Bluetooth settings, but there doesn’t seem to be an active connection.

Make sure you have a motorcycle unit with 2 Bluetooth modules. The Cardo has to be paired in the "Transmit BT", "Bluetooth Emit" or "BT Helmet" menu, NOT in the normal system settings.

I was just getting ready to say this. If I paired mine via Settings/Bluetooth/Discover/Search it wouldn't work. I had to pair the Motikom (similar to Cardo) via the Bluetooth Emit icon (Bluetooth Search) on the main page.

Plus I was going to say, don't have the Cardo paired with your smartphone - but Guido already beat me to it.

jmossfeld@jmossfeld

2 Posts

Member

#80 · 23.04.2023, 15:10

Thanks, using the “BT Emit” thing worked! I had tried it previously, but I gave up too soon —it took about a minute to find my com unit to make a connection. All is good now and I’m looking forward to riding the routes that I made in Scenic for the BMW MOA Grand Coddiwomple (even though I’m on a Versys instead of a Beemer).

I’ll try the same thing with a Bluetooth receiver that I have for my wired noise-cancelling earbuds. I like to switch between the Cardo helmet speakers and the earbuds just to mix things up for my ears.

maxdamage00 has reacted to this post.

Cookie	Duration	Description
cookielawinfo-checkbox-analytics	11 months	This cookie is set by GDPR Cookie Consent plugin. The cookie is used to store the user consent for the cookies in the category "Analytics".
cookielawinfo-checkbox-functional	11 months	The cookie is set by GDPR cookie consent to record the user consent for the cookies in the category "Functional".
cookielawinfo-checkbox-necessary	11 months	This cookie is set by GDPR Cookie Consent plugin. The cookies is used to store the user consent for the cookies in the category "Necessary".
cookielawinfo-checkbox-others	11 months	This cookie is set by GDPR Cookie Consent plugin. The cookie is used to store the user consent for the cookies in the category "Other.
cookielawinfo-checkbox-performance	11 months	This cookie is set by GDPR Cookie Consent plugin. The cookie is used to store the user consent for the cookies in the category "Performance".
viewed_cookie_policy	11 months	The cookie is set by the GDPR Cookie Consent plugin and is used to store whether or not user has consented to the use of cookies. It does not store any personal data.