Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
Cheerdriving just told me they don’t recognize my podofo device and that the WiFi isn’t the WiFi they have on their box. Is “ConnectBox WiFi” not the same as Cheerdriving?
Bummer but that was to be expected I guess. Podofo seems to be a generic rebadge/reseller which was also to be expected at that price point
 
I was hoping maybe Podofo had something similar. Anyone else a bit worried that CheerDriving locks down their firmware, or worse builds in some device-check that bricks the Podofo?

I guess for $50ish it’s not a huge loss. But now I’m wishing I just spent the $25 more and ordered the CheerDriving device. SMH Hahahahaha

side note, the Podofo was running a bit hot on my 30 minute drive. Using GPS, streaming music, and a brief phone call… compared to the v3.0 Carlinkit.
 
  • Like
Reactions: dvuon
I was hoping maybe Podofo had something similar. Anyone else a bit worried that CheerDriving locks down their firmware, or worse builds in some device-check that bricks the Podofo?

I guess for $50ish it’s not a huge loss. But now I’m wishing I just spent the $25 more and ordered the CheerDriving device. SMH Hahahahaha

side note, the Podofo was running a bit hot on my 30 minute drive. Using GPS, streaming music, and a brief phone call… compared to the v3.0 Carlinkit.
I bet Cheerdriving is also just a reseller and not developper of the box
 
  • Like
Reactions: samabbott
Just tried the podofo on my gf’s Honda Civic 2018. It recognizes device as carplay but the interface never pops up and we get an error loading carplay message on her screen. Will try to update with a 16gb sd card now.

edit1: loaded .09v onto a 16gb sd card and inserted into the podofo. Plugged the podofo into my laptop and it instantly lit up and flashed for about 15 seconds. Solid green light now. Time to try it in the Honda and Mazda cars.

edit 2: the device works in the Honda Civic. Airplay casting does not work though. The audio plays, but no video. It is sometimes black screen or it’ll have the airplay interface. Will try again on my Mazda CX-5 in a bit.

Edit 3: Mazda recognized as carplay. I clicked enable on the message screen for Mazda but it won’t connect or show the interface. Looking at my connections, the apple carplay keeps flashing from available to being greyed out (unavailable). The device also blinks on and off. Looks like v09 doesn’t work with Mazdas yet.

Edit 4: spoke with CheerDriving and the rep said to look out for future updates for Mazda compatibility. The Podofo rep on AliExpress has not replied to a single message of mine. I think I’m going to have PayPal refund me at this point.
 
Last edited:
can anyone help with this please we’ve tried the latest firmware and the previous version it is a red ui CarPlay adapter v2 and it won’t let us even check for updates or send logs.

we only get this white screen, any help would be greatly appreciated.
B0CC5C2F-1A55-4C5C-A768-B3BE08100B04.png
 
Version 4306 is ok I dit OTA to 4309 no connection to head unit again
I will stay on 4306 for now
Btw podofo support really is non existent
 
Last edited:
Just received my Carlinkit V3 mini.
I received it with the 2021.08.24 FW. First test shows a faster start. I could set 300ms of delay… have to check on a long run if it’s ok.
Now I lost the customFW with “Carplay like” interface… :(

I remember @zerozoneice mentions it has a new BT chip. So not sure I can test the script from @VLud to restore the 2x2MIMO.

Anyone else bought the mini?
 
Version 4306 is ok I dit OTA to 4309 no connection to head unit again
I will stay on 4306 for now
Btw podofo support really is non existent
Good deal. Went for a drive today and felt the latency was too high with the Podofo, especially when Carlinkit can now reliably do 300ms on 2021.08.30 firmware
 
Audio delay has indeed come down quite a bit. 300ms are reliable now. Audio and UI are more in sync than before. Hopefully Carlinkit will allow setting it even lower.

Call latency however stays the same. It still measures in at a round-trip time of about 1s.
 
  • Like
Reactions: dca78
Just sharing some wireless detais/comparison TOYOTAEB==CarLinkit v3.0 & ConnectBoxWiFi==Podofo.
Podofo seems to be running fine on my test drive. Just a bit warm as mentioned earlier compared to the Carlinkit devices. The Carlinkit devices do appear to have better hardware internals as far as I can tell... But obviously both meet the requirements for CarPlay.

1631887544657.png

1631887579696.png

1631887595576.png
 
Another update on the rollback... my coffee is finally kicking in a bit.

Here's the play-by-play...
I was able to upgrade using your stock firmware repository to "Firmware/U2W_AUTOKIT_Update_2021.08.24.1817.img" (confirmed as spatial stream reduced to 1, interesting enough, throughout this entire process, the spatial streams remained "1" even after rolling back to the 2020.11.10.2139 firmware).

1631892440231.png


Per all of the online readme, I tried to use the "Firmware/U2W_Update_2020.11.10.2138_ROLLBACK.img"... No dice. Does absolutely nothing while running the "U2W_AUTOKIT_Update_2021.08.24.1817.img".

Tried your post above @VLud , "VLud said:
Try U2W_AUTOKIT_Update_2020.12.25.1732_ROLLBACK.img instead then. You can't install CFW straight away due to new encryption, nothing new."

-- This sort of works. I loaded it to the flash drive, inserted it... and no blinking red/green... however, the web interface does how the firmware version changed from 2021.08.24 to...

1631892632618.png

That said, it did this all within maybe 5-10 seconds? No flashing, no reboot... and it also shows the update available:

1631892675817.png


Disconnecting the USB flash drive after ~5 minutes of sitting, it did reboot.
Post-reboot, it still shows v2020.12.25.1733...
Cleaned off the flash drive and downloaded the "Firmware/U2W_Update_2020.11.10.2138_ROLLBACK.img".
This time, after about 5-10 seconds, the version changed to v2020.11.10.2139... No flashing, no reboot, etc...
I waited about 5 minutes (to give it time to finish any processing/flashing) before disconnecting the USB flash drive.
It rebooted after the flash drive was removed, and shows:

1631893160550.png

Checking for updates does nothing at this point... No rollback option within the settings...
I tried jumping over to the custom firmware "Custom_Firmware/2021.08.24_BASED/AUTOKIT/U2W_AUTOKIT_Update.img". Does nothing, still shows the 2020.11.20 version...
Power-cycled the device and tried loading custom firmware: "Custom_Firmware/2021.04.26_BASED/AUTOKIT/U2W_AUTOKIT_Update.img"
Tried renaming it to "U2W_Update"and power-cycled the device again.
Did nothing, still shows v2020.11.10.2139...
Downloaded "Custom_Firmware/2021.03.06_BASED/AUTOKIT/U2W_AUTOKIT_Update.img"
Kept the filename as the same... (did not remove AUTOKIT).
Did nothing. Renamed to "U2W_Update.img" and again no dice.
This time I thought I'd try doing the latest file again, including the two script files...
Downloaded: "Custom_Firmware/2021.08.24_BASED/AUTOKIT/U2W_AUTOKIT_Update.img"
as well as the two script files:
"Custom_Firmware/Scripts/Downgrade_2021.03.06/ARMimg_maker"
"Custom_Firmware/Scripts/Downgrade_2021.03.06/U2W.sh"
placed all three files on the root of the flash drive... and no luck, no change. Power-cycled the device and still nothing.

I'm a bit out of steps to try. I'm open to testing more if anyone has any input... but I cannot get it to switch over to the custom firmware. Maybe I am missing something (hopefully not obvious)?

I tried to keep it on the OEM firmware, but update again to something later... and now it appears to be stuck on the 2020.11.10 version. It won't take any of the newer auto kit files within /Firmware/ and the OTA update appears to be broken. hahaha <curse word/> -- I'll update if I figure out how to shake it loose.

Rebooting with the USB flash drive inserted, w/ the 2020.12.25.1732_rollback image resolved the issue (oddly enough, seems to have remembered the TOYOTAEB SSID as well, no more AUTOBOX wifi). It's now running that version... Spatial Streams still show "1" instead of "2"... Once the interface showed the newer version, I unplugged the flash drive and it rebooted. Performed OTA update to 2021.03.06.1356 (no typo).... It did its thing and rebooted by itself. It's now running version 2021.03.06.1355 post-reboot... Spatial streams are now showing "2".

I'm planning on keeping it at the 2021.03.06.1355, rollback shows 2020.12.25.1732... unless it's not stable in my truck. Then I'll plan on updating it to something later. Time to go mess with the Podofo...

** all of these tests were performed outside of my car, with the Carlinkit connected to my MBP PD Apple charger.
 
Last edited:
(confirmed as spatial stream reduced to 1, interesting enough, throughout this entire process, the spatial streams remained "1" even after rolling back to the 2020.11.10.2139 firmware)
I am not sure whether rollbacks work properly in any case. Carlinkit updates are pretty flaky indeed. They are delta updates. So if the newer update writes some file but the rollback FW does not, you will be stuck with the newer file.
 
  • Like
Reactions: samabbott
I am not sure whether rollbacks work properly in any case. Carlinkit updates are pretty flaky indeed. They are delta updates. So if the newer update writes some file but the rollback FW does not, you will be stuck with the newer file.
Seems to be the case. Part of me is tempted to try again, coming from an older update this time instead of the latest... but I need to get some work done. hahaha

If I get more free time I'll mess with it some more. I'm hoping @VLud can provide some input or direction. It would be very much appreciated!
 
I'm hoping somebody can figure out why the Carlinkit freezes when audio or sound is introduced.......
 
Seems to be the case. Part of me is tempted to try again, coming from an older update this time instead of the latest... but I need to get some work done. hahaha
I think you can easily and badly mess up that the device if you jump wildly between versions. If one update writes one application and another one writes another and the two are incompatible with each other... boom!
 
  • Like
Reactions: samabbott
I believe mine took this version. It now shows 1733 (not 1732). Not sure if that matters?
View attachment 1834202

What are the steps to load the custom firmware after rollback?

when the interface boots up — do you have the gre
Another update on the rollback... my coffee is finally kicking in a bit.

Here's the play-by-play...
I was able to upgrade using your stock firmware repository to "Firmware/U2W_AUTOKIT_Update_2021.08.24.1817.img" (confirmed as spatial stream reduced to 1, interesting enough, throughout this entire process, the spatial streams remained "1" even after rolling back to the 2020.11.10.2139 firmware).

View attachment 1834215

Per all of the online readme, I tried to use the "Firmware/U2W_Update_2020.11.10.2138_ROLLBACK.img"... No dice. Does absolutely nothing while running the "U2W_AUTOKIT_Update_2021.08.24.1817.img".

Tried your post above @VLud , "VLud said:
Try U2W_AUTOKIT_Update_2020.12.25.1732_ROLLBACK.img instead then. You can't install CFW straight away due to new encryption, nothing new."

-- This sort of works. I loaded it to the flash drive, inserted it... and no blinking red/green... however, the web interface does how the firmware version changed from 2021.08.24 to...

View attachment 1834221
That said, it did this all within maybe 5-10 seconds? No flashing, no reboot... and it also shows the update available:

View attachment 1834223

Disconnecting the USB flash drive after ~5 minutes of sitting, it did reboot.
Post-reboot, it still shows v2020.12.25.1733...
Cleaned off the flash drive and downloaded the "Firmware/U2W_Update_2020.11.10.2138_ROLLBACK.img".
This time, after about 5-10 seconds, the version changed to v2020.11.10.2139... No flashing, no reboot, etc...
I waited about 5 minutes (to give it time to finish any processing/flashing) before disconnecting the USB flash drive.
It rebooted after the flash drive was removed, and shows:

View attachment 1834233
Checking for updates does nothing at this point... No rollback option within the settings...
I tried jumping over to the custom firmware "Custom_Firmware/2021.08.24_BASED/AUTOKIT/U2W_AUTOKIT_Update.img". Does nothing, still shows the 2020.11.20 version...
Power-cycled the device and tried loading custom firmware: "Custom_Firmware/2021.04.26_BASED/AUTOKIT/U2W_AUTOKIT_Update.img"
Tried renaming it to "U2W_Update"and power-cycled the device again.
Did nothing, still shows v2020.11.10.2139...
Downloaded "Custom_Firmware/2021.03.06_BASED/AUTOKIT/U2W_AUTOKIT_Update.img"
Kept the filename as the same... (did not remove AUTOKIT).
Did nothing. Renamed to "U2W_Update.img" and again no dice.
This time I thought I'd try doing the latest file again, including the two script files...
Downloaded: "Custom_Firmware/2021.08.24_BASED/AUTOKIT/U2W_AUTOKIT_Update.img"
as well as the two script files:
"Custom_Firmware/Scripts/Downgrade_2021.03.06/ARMimg_maker"
"Custom_Firmware/Scripts/Downgrade_2021.03.06/U2W.sh"
placed all three files on the root of the flash drive... and no luck, no change. Power-cycled the device and still nothing.

I'm a bit out of steps to try. I'm open to testing more if anyone has any input... but I cannot get it to switch over to the custom firmware. Maybe I am missing something (hopefully not obvious)?

I tried to keep it on the OEM firmware, but update again to something later... and now it appears to be stuck on the 2020.11.10 version. It won't take any of the newer auto kit files within /Firmware/ and the OTA update appears to be broken. hahaha <curse word/> -- I'll update if I figure out how to shake it loose.

Rebooting with the USB flash drive inserted, w/ the 2020.12.25.1732_rollback image resolved the issue (oddly enough, seems to have remembered the TOYOTAEB SSID as well, no more AUTOBOX wifi). It's now running that version... Spatial Streams still show "1" instead of "2"... Once the interface showed the newer version, I unplugged the flash drive and it rebooted. Performed OTA update to 2021.03.06.1356 (no typo).... It did its thing and rebooted by itself. It's now running version 2021.03.06.1355 post-reboot... Spatial streams are now showing "2".

I'm planning on keeping it at the 2021.03.06.1355, rollback shows 2020.12.25.1732... unless it's not stable in my truck. Then I'll plan on updating it to something later. Time to go mess with the Podofo...

** all of these tests were performed outside of my car, with the Carlinkit connected to my MBP PD Apple charger.

This is exactly the same with my (2 different) v3.0 devices and trying to install @VLud Custom Firmware.

It's impossible.

So anyone that wants a CFW dongle -- get a V2.0.

@VLud is this enough data for you? I'm more than happy to help provide more where I can... I don't believe this is user error anymore.
 
  • Like
Reactions: samabbott
when the interface boots up — do you have the gre


This is exactly the same with my (2 different) v3.0 devices and trying to install @VLud Custom Firmware.

It's impossible.

So anyone that wants a CFW dongle -- get a V2.0.

@VLud is this enough data for you? I'm more than happy to help provide more where I can... I don't believe this is user error anymore.

The v3.0 I purchased has the red interface. My original v2.0 had a Green interface (that unit got bricked about a month ago doing an OTA update)... I know I have the v3.0 as opposed to a v2.0 device since the new unit is now wireless AC/WiFi5. My previous v2.0 as well as my original replacement order (which arrived with the Red UI same appearance as the v3.0-WiFi5) both had Wireless N/WiFi4.

I did all steps being powered off my MacBook Pro charger. I was messing around for so long, I didn't want to keep my truck idling for that long, not to mention, I wanted to keep my WiFi Explorer open so I could watch that status of the SSID as it changed, disconnected, rebooted, etc. Because it wasn't powered/connected to my head unit, I couldn't actually see what the device was doing... Just relied on the LED/status light, and some courage... hahaha

If there's a certain step or update between two versions where it would be beneficial to watch the head unit display, let me know. I'd be more than happy to get some screenshots of the updates from the head unit. I just want to stage it before doing all the steps. Likewise, if it would help -- I can crack open the case to verify chip components, etc..

My simple definition of the two devices:
v2.0 == WiFi 4/Wireless N w/ 40MHz, RealTek chip. v2.0 can be upgraded to run the same Red UI, although my original unit never switch UI, always had green even with the 2021 OTA updates.
v3.0 == WiFi 5/Wireless AC w/ 80MHz, Per @VLud it's a Broadcom chip. I also believe these units are shipping with the Red UI only.
1631914258372.png
 
Last edited:
  • Like
Reactions: Mavro
My motivation for switching to CFW w/ my v3.0 (Broadcom chip, Wireless AC/5) is simply to mess with the script files @VLud posted previously. I really would enjoy tinkering with them, and figuring out how to switch the radio width to 20MHz, channel to 165... Just to see if it resolves any of my perceived 'interference' issues. During my commute into the office, I can perfectly predict when my music will start stuttering, sometimes dropping to the point that my phone disconnects from the Carlinkit all together... It happens in the exact same spots on the freeway. Likewise, it happens out in the parking lot of my work (we have some outdoor Cisco Enterprise Mesh APs, so I know the 5GHz band is pretty busy). Using "Network Analyzer" on my iPhone, I can run a constant ping to 192.168.50.2, and watch as the latency increases and packet loss in these specific areas.
 
  • Like
Reactions: Mavro
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.