CarPlay CarPlay adapter to convert to wireless CarPlay?

[Gjwilly]

Found the manufacturer of the podofo unit, it seems to be rebranded cheerdriving https://www.cheerdriving.com/prod_view.aspx?TypeId=80&Id=220&FId=t3:80:3
on their website, they show the micro sd port as a firmware update port, probably for recovery in case of failure.

They have a few instructional videos on youtube https://www.youtube.com/playlist?list=PLTq6yB_xekfdhmzyIMcGZkPuf8aQ7_EXn

For anyone with issues with their car, I'd sugest contactim them directly.

I contacted them about my Podofo problems and they were very responsive but all they had to say was that their box doesn't support after-market stereos.

They also confirmed that they sold on AliExpress.

 

[Gjwilly]

Would someone with a v3.0 please check audio/video lag?
By that I mean play a video on your phone but let the audio come through the car stereo.
The v2.0 has horribly out of sync audio/video compared to the JoyeAuto.

 

[samabbott]

Would someone with a v3.0 please check audio/video lag?
By that I mean play a video on your phone but let the audio come through the car stereo.
The v2.0 has horribly out of sync audio/video compared to the JoyeAuto.

I believe this is normal. If you pull up the webpage 192.168.50.2, under the gear, you'll see a media delay section. I believe the default is 1000ms, a lot of people are dropping it to 500ms. Results may vary, but yes it's delayed on my 3.0, about the same as my 2.0...

With the very minimal testing I did, the v3.0 seems to connect a little bit faster that my 2.0... Haven't timed it at all, so I could be wrong, it's just my first impressions. Other than that, audio delay and screen responsiveness seems the same. I haven't been able to test a phone call yet to tell if there's any lag or delay when answering the call, etc... I know my 2.0 struggled at times to connect calls, and would sometimes freeze up completely; usually saw that once or twice a week.

 

[Gjwilly]

I believe this is normal. If you pull up the webpage 192.168.50.2, under the gear, you'll see a media delay section. I believe the default is 1000ms, a lot of people are dropping it to 500ms. Results may vary, but yes it's delayed on my 3.0, about the same as my 2.0...

With the very minimal testing I did, the v3.0 seems to connect a little bit faster that my 2.0... Haven't timed it at all, so I could be wrong, it's just my first impressions. Other than that, audio delay and screen responsiveness seems the same. I haven't been able to test a phone call yet to tell if there's any lag or delay when answering the call, etc... I know my 2.0 struggled at times to connect calls, and would sometimes freeze up completely; usually saw that once or twice a week.

Yeah I don’t care about UI lag.
I mean I do but I don’t have an issue with it.
But I like to watch videos at drive-ins or wherever I happen to be parked and the out of sync audio/video is super annoying.
That’s the one area where the JoyeAuto is miles ahead of the CarLinkit and I was thinking the difference must be in the hardware.
I was hoping the 3.0 hardware would improve things.

 

[MrMister111]

I contacted them about my Podofo problems and they were very responsive but all they had to say was that their box doesn't support after-market stereos.

They also confirmed that they sold on AliExpress.

Don’t support aftermarket stereos? So what do they support? They are all aftermarket in that fact that Podofo don’t make any inside a car?

Mine still on way so will see if is correct version ie not Android based, and works.

Anyone with the Podofo mini got caring to work ok?

 

[Arnau]

They might support non-car maker radios in the future, keep in mind that the firmware is at version 0.0.5 so it's clearly on it's infancy.

I already received it and it works like magic (posted a few pages back).Much better than my carlinkit v1 and does also not freeze/crash and it stays very cool to the touch. I also feel it boots-up and connect a bit more faster. Airplay casting also works but in my devices streams with artifacts, so it needs a bit more of development.

Today I did a more difficult test: 1 hour driving with GPS on, music and several calls. No issues at all.

I'm pretty satisfied, a very nice and cheap upgrade.

 

[Kurt871]

They might support non-car maker radios in the future, keep in mind that the firmware is at version 0.0.5 so it's clearly on it's infancy.

I already received it and it works like magic (posted a few pages back).Much better than my carlinkit v1 and does also not freeze/crash and it stays very cool to the touch. I also feel it boots-up and connect a bit more faster. Airplay casting also works but in my devices streams with artifacts, so it needs a bit more of development.

Today I did a more difficult test: 1 hour driving with GPS on, music and several calls. No issues at all.

I'm pretty satisfied, a very nice and cheap upgrade.

Do you feel like there's any difference between the Podofo and the CheerDriving units? My Carlinkit is fine but I'd really love to have track seeking via the steering wheel functionality restored. The CheerDriving looks slightly less.. janky? I wonder why it would be so much more expensive is my only question.

 

[Zombie Woof]

Just saw this new OTA update. Will update and see if things run smoothly

 

[live4ever]

Just updated my Carlinkit ver 1.0 (original USB-A with the 10MB rootFS) from vlud custom 2021.02.02_BASED
to 2021.08.24_BASED.

Good news the mic on my Sony XAV-AX5000 finally works wirelessly - 2021.02.02 (or any earlier ones) didn’t work at all for calls, messages or any Siri.

 

[Arnau]

Do you feel like there's any difference between the Podofo and the CheerDriving units? My Carlinkit is fine but I'd really love to have track seeking via the steering wheel functionality restored. The CheerDriving looks slightly less.. janky? I wonder why it would be so much more expensive is my only question.

Not really sure. To me I think they are exactly the same. Maybe podofo just wants to get more sales with less benefits, having the same price as the already known carlinkit would make people choose carlinkit... as de unit is new, you need to fet market share.

After all, I don't feel any of these units (neither carlinkit or cheerdriving) costs >70€ to make 😅

 

[samabbott]

Not really sure. To me I think they are exactly the same. Maybe podofo just wants to get more sales with less benefits, having the same price as the already known carlinkit would make people choose carlinkit... as de unit is new, you need to fet market share.

After all, I don't feel any of these units (neither carlinkit or cheerdriving) costs >70€ to make 😅

Just bought it. Maybe it’ll perform better than the v3.0, figured it wouldn’t hurt to try.

I wish Apple would create something. I’d easily pay their price for Apple-quality. Just dreaming.

 

[simps100]

Just bought it. Maybe it’ll perform better than the v3.0, figured it wouldn’t hurt to try.

I wish Apple would create something. I’d easily pay their price for Apple-quality. Just dreaming.

I would also love this - and I wonder if we do get a port-less iPhone we may get something like this? The ones we use have proven it’s possible - you’d think if apple wanted to they could probably quite easily built a perfected one.

I do think if they removed the port they would need something - it’s one thing making docks/ charger’s useless but cars are a much bigger investment!

 

[VLud]

Just saw this new OTA update. Will update and see if things run smoothly

Same as 2021.08.24 but for non-AUTOKIT units

Added to the repo

 

[Kurt871]

@VLud possible to get a custom firmware of 2021.07.05.2319 which has the 2x2MIMO settings? I bet we could set the channel too in the config.

Seconded; would love a custom firmware that includes the 2x2MIMO as well!

 

[Kurt871]

Not really sure. To me I think they are exactly the same. Maybe podofo just wants to get more sales with less benefits, having the same price as the already known carlinkit would make people choose carlinkit... as de unit is new, you need to fet market share.

After all, I don't feel any of these units (neither carlinkit or cheerdriving) costs >70€ to make 😅

I ordered both for testing and comparison so we'll find out soon

 

[VLud]

I don't know why you all want to get the maximum speed while Carplay feed is less than 25 Mbps. What really matters is the latency

2021.07.05.2319 added to the repo

 

[samabbott]

I don't know why you all want to get the maximum speed while Carplay feed is less than 25 Mbps. What really matters is the latency

2021.07.05.2319 added to the repo

Do you know if it's possible to change the radio settings in the config?


The 2x2 spatial streams would help with link reliability and overall link quality; aside from just throughput.. If CarPlay is low-bandwidth (25mbps) and latency sensitive... The 165 5GHz channel is hardly ever used, and is limited to 20Mhz: 2x2 @ 20MHz == 173mbps link speed and ~100mbps real-world throughput; it's likely MUCH cleaner of a signal in terms of interference than the lower 5GHz channels. Honestly, just being able to reduce/control channel width could benefit from the reduced interference. Running at 80MHz, your chance of interference increases substantially over 40Mhz, likewise 40Mhz to 20Mhz. It's really a balancing act, spatial streams NEVER hurt performance, but the wider-width you run (e.g. 20, 40, 80) also exponentially increases your interference in populated areas; and can increase your packet loss/error rate and latency. Having the AC radio is beneficial since even AC-wave1 introduced some better handling of interference and AP/Client delivery optimization compared to N.

Most of my skips//drops are due to interference. Running a constant ping to 192.168.50.2, I can watch as I drive through certain areas and see latency/packet loss.

 

[P1xellat3d]

APPLE CAR PLAY UI THEME

EXCLUSIVELY FOR U2W AUTOKIT (RED INTERFACE)​

Notes:

You MUST be on 'CUSTOM AUTOKIT' FIRMWARE. This was developed on Feb 2021 software but is most likely compatible on older versions.

Questions?

*yes* it must be custom firmware* - you cannot access the file system on stock FW

*yes* it must be AUTOKIT version - blue version uses different code, if anyone wants to test and find out, be my guest. However I am pretty sure it wont work and you may brick your device.

*it MUST be a U2W Device* (As far as I know AUTOKIT is only U2W devices)


Any bug fixes or element adjustments *MUST* be opened on Github, if you have questions, open them on GITHUB discussion. This thread moves to fast to help.

For further information regarding installation check github in the /install or uninstall directories and read the README.TXT file for further instructions.

You will require 3 things:

1) USB Stick
2) U2W Dongle running Custom AUTOKIT FW
3) Brain.

I am not responsible for mistakes.

Thankyou @dca78 for helping with the 1280x720 version, without him it wouldn't exist.

Enjoy:

th1efx/AutoKit-CarPlay

CarPlay Theme for AutoKit U2W Dongle. Contribute to th1efx/AutoKit-CarPlay development by creating an account on GitHub.

github.com

Theme fully supports 3 resolutions:

1) 800x480
2) 1920x720
3) 1280x720

If you don't have a compatible resolution you will see everything out of place and it will look like the current ugly interface. It will still work and you can either revert. There is one file not updated called "1024" version in the code but the file doesn't seem to be maintained well, so its possible that this is not a very popular/universal resolution for displays.

*** IF YOU NEED YO CHANGE TO CUSOM FIRMWARE ITS SUGGESTED TO STAY AT 02.02.2021 and not March update as they have made changes abs specifically changed wifi drivers and some devices are failing after moving to this firmware! ***

If you downloaded and like the theme, all i ask if that you like this post to show your appreciation!

Hi there! Is it possible at all to assist with adjusting elements to suit a 1280x640 resolution display? This is to suit the 9.2" screen as found on Volkswagen Golfs.

Thanks in advance.

 

[VLud]

Do you know if it's possible to change the radio settings in the config?


The 2x2 spatial streams would help with link reliability and overall link quality; aside from just throughput.. If CarPlay is low-bandwidth (25mbps) and latency sensitive... The 165 5GHz channel is hardly ever used, and is limited to 20Mhz: 2x2 @ 20MHz == 173mbps link speed and ~100mbps real-world throughput; it's likely MUCH cleaner of a signal in terms of interference than the lower 5GHz channels. Honestly, just being able to reduce/control channel width could benefit from the reduced interference. Running at 80MHz, your chance of interference increases substantially over 40Mhz, likewise 40Mhz to 20Mhz. It's really a balancing act, spatial streams NEVER hurt performance, but the wider-width you run (e.g. 20, 40, 80) also exponentially increases your interference in populated areas; and can increase your packet loss/error rate and latency. Having the AC radio is beneficial since even AC-wave1 introduced some better handling of interference and AP/Client delivery optimization compared to N.

Most of my skips//drops are due to interference. Running a constant ping to 192.168.50.2, I can watch as I drive through certain areas and see latency/packet loss.

Broadcom chip changes:

/lib/firmware/bcm/nvram_bcm4354_m.txt

First window: 2021.07.05.2319

Full file:

# 4354_M turning 2020/07/15 by AIDEN.
NVRAMRev=$Rev: 373428 $
sromrev=11
boardrev=0x1101
boardtype=0x070c
boardflags=0x12401001
boardflags2=0x00802000
boardflags3=0x40000109
macaddr=00:90:4c:16:70:01
ccode=CN
regrev=38
antswitch=0
pdgain5g=4
pdgain2g=4
tworangetssi2g=0
tworangetssi5g=0
femctrl=10
vendid=0x14e4
devid=0x43df
manfid=0x2d0
nocrc=1
otpimagesize=502
xtalfreq=37400
rxgains2gelnagaina0=3
rxgains2gtrisoa0=5
rxgains2gtrelnabypa0=1
rxgains5gelnagaina0=3
rxgains5gtrisoa0=5
rxgains5gtrelnabypa0=1
rxgains5gmelnagaina0=3
rxgains5gmtrisoa0=5
rxgains5gmtrelnabypa0=1
rxgains5ghelnagaina0=3
rxgains5ghtrisoa0=5
rxgains5ghtrelnabypa0=1
rxgains2gelnagaina1=3
rxgains2gtrisoa1=5
rxgains2gtrelnabypa1=1
rxgains5gelnagaina1=3
rxgains5gtrisoa1=5
rxgains5gtrelnabypa1=1
rxgains5gmelnagaina1=3
rxgains5gmtrisoa1=5
rxgains5gmtrelnabypa1=1
rxgains5ghelnagaina1=3
rxgains5ghtrisoa1=5
rxgains5ghtrelnabypa1=1
rxchain=3
txchain=3
aa2g=3
aa5g=3
agbg0=63
agbg1=63
aga0=2
aga1=2
tssipos2g=1
extpagain2g=2
tssipos5g=1
extpagain5g=2
tempthresh=120
tempoffset=255
rawtempsense=0x1ff
pa2ga0=65405,6046,64854
pa2ga1=65408,6127,64843
pa5ga0=65358,6053,64807,65354,6020,64808,65364,6040,64813,65359,5987,64817
pa5ga1=65357,6084,64806,65356,6018,64810,65362,5936,64821,65368,5935,64828
pa2ga0.fab.4=-161,5896,-688
pa2ga1.fab.4=-161,6005,-702
pa5ga0.fab.4=-181,6051,-727,-183,6055,-730,-177,6030,-722,-177,6049,-723
pa5ga1.fab.4=-185,6080,-733,-180,6078,-729,-178,5928,-714,-174,5963,-713
maxp2ga0=76
maxp5ga0=76,76,76,76
maxp2ga1=74
maxp5ga1=74,74,74,74
subband5gver=0x4
pdoffsetcckma0=0x4
pdoffsetcckma1=0x4
pdoffsetcckma0.fab.4=0x0
pdoffsetcckma1.fab.4=0x0
pdoffset40ma0=0x0000
pdoffset80ma0=0x0000
pdoffset40ma1=0x0000
pdoffset80ma1=0x0000
cckbw202gpo=0x0000
cckbw20ul2gpo=0x0000
mcsbw202gpo=0x88866662
dot11agofdmhrbw202gpo=0x6542
ofdmlrbw202gpo=0x0122
mcsbw205glpo=0x88866662
mcsbw405glpo=0xa9a66663
mcsbw805glpo=0xbb866665
mcsbw205gmpo=0x88866662
mcsbw405gmpo=0xa9a66663
mcsbw805gmpo=0xbb866665
mcsbw205ghpo=0x88866662
mcsbw405ghpo=0xa9966663
mcsbw805ghpo=0xbb866665
mcslr5glpo=0x0000
mcslr5gmpo=0x0000
mcslr5ghpo=0x0000
sb20in40hrpo=0x0
sb20in80and160hr5glpo=0x0
sb40and80hr5glpo=0x0
sb20in80and160hr5gmpo=0x0
sb40and80hr5gmpo=0x0
sb20in80and160hr5ghpo=0x0
sb40and80hr5ghpo=0x0
sb20in40lrpo=0x0
sb20in80and160lr5glpo=0x0
sb40and80lr5glpo=0x0
sb20in80and160lr5gmpo=0x0
sb40and80lr5gmpo=0x0
sb20in80and160lr5ghpo=0x0
sb40and80lr5ghpo=0x0
dot11agduphrpo=0x0
dot11agduplrpo=0x0
phycal_tempdelta=25
temps_period=15
temps_hysteresis=15
AvVmid_c0=2,140,2,145,2,145,2,145,2,145
AvVmid_c1=2,140,2,145,2,145,2,145,2,145
rssicorrnorm_c0=20,20
rssicorrnorm_c1=20,20
rssicorrnorm5g_c0=4,6,6,4,6,6,3,5,6,4,6,6
rssicorrnorm5g_c1=4,5,7,4,5,7,3,5,7,3,5,6
swctrlmap_5g=0x02020202,0x05050404,0x04040000,0x000000,0x047
swctrlmap_2g=0x10081008,0x28300820,0x08200000,0x803020,0x0ff
muxenab=0x10
btc_mode=1
btc_params84=7000
btc_params10=20000
btc_params8=45000
cckdigfilttype=1
paprdis=0
epsdelta2g0=0
epsdelta2g1=0
rpcal2g=0x9
rpcal5gb0=0x33
rpcal5gb1=0x29
rpcal5gb2=0x36
rpcal5gb3=0x2E

Feel free to try on latest CFW (reboot the device once done):
https://github.com/ludwig-v/wireles.../Custom_Firmware/Scripts/Restore_Broadcom_2x2

Documentation for all nvram parameters (From 6.1):
002-14808_BCM4354_BCM4356_BCM4358_-_OTP_Programming_and_NVRAM_Development_in_SDIO_Mode.pdf

aa2g, aa5g Number of antennas available for the 2.4 GHz and 5 GHz bands, respectively, in bit-mapped binary format:
• 1 = 01b for one antenna
• 3 = 11b for two antennas (applies to CYW4356)

rxchain This specifies the number of RX paths (bit mask). Set this to 3.
txchain This specifies the number of TX paths (bit mask). Set this to 3.

 

[samabbott]

Broadcom chip changes:

/lib/firmware/bcm/nvram_bcm4354_m.txt

First window: 2021.07.05.2319

Full file:

# 4354_M turning 2020/07/15 by AIDEN.
NVRAMRev=$Rev: 373428 $
sromrev=11
boardrev=0x1101
boardtype=0x070c
boardflags=0x12401001
boardflags2=0x00802000
boardflags3=0x40000109
macaddr=00:90:4c:16:70:01
ccode=CN
regrev=38
antswitch=0
pdgain5g=4
pdgain2g=4
tworangetssi2g=0
tworangetssi5g=0
femctrl=10
vendid=0x14e4
devid=0x43df
manfid=0x2d0
nocrc=1
otpimagesize=502
xtalfreq=37400
rxgains2gelnagaina0=3
rxgains2gtrisoa0=5
rxgains2gtrelnabypa0=1
rxgains5gelnagaina0=3
rxgains5gtrisoa0=5
rxgains5gtrelnabypa0=1
rxgains5gmelnagaina0=3
rxgains5gmtrisoa0=5
rxgains5gmtrelnabypa0=1
rxgains5ghelnagaina0=3
rxgains5ghtrisoa0=5
rxgains5ghtrelnabypa0=1
rxgains2gelnagaina1=3
rxgains2gtrisoa1=5
rxgains2gtrelnabypa1=1
rxgains5gelnagaina1=3
rxgains5gtrisoa1=5
rxgains5gtrelnabypa1=1
rxgains5gmelnagaina1=3
rxgains5gmtrisoa1=5
rxgains5gmtrelnabypa1=1
rxgains5ghelnagaina1=3
rxgains5ghtrisoa1=5
rxgains5ghtrelnabypa1=1
rxchain=3
txchain=3
aa2g=3
aa5g=3
agbg0=63
agbg1=63
aga0=2
aga1=2
tssipos2g=1
extpagain2g=2
tssipos5g=1
extpagain5g=2
tempthresh=120
tempoffset=255
rawtempsense=0x1ff
pa2ga0=65405,6046,64854
pa2ga1=65408,6127,64843
pa5ga0=65358,6053,64807,65354,6020,64808,65364,6040,64813,65359,5987,64817
pa5ga1=65357,6084,64806,65356,6018,64810,65362,5936,64821,65368,5935,64828
pa2ga0.fab.4=-161,5896,-688
pa2ga1.fab.4=-161,6005,-702
pa5ga0.fab.4=-181,6051,-727,-183,6055,-730,-177,6030,-722,-177,6049,-723
pa5ga1.fab.4=-185,6080,-733,-180,6078,-729,-178,5928,-714,-174,5963,-713
maxp2ga0=76
maxp5ga0=76,76,76,76
maxp2ga1=74
maxp5ga1=74,74,74,74
subband5gver=0x4
pdoffsetcckma0=0x4
pdoffsetcckma1=0x4
pdoffsetcckma0.fab.4=0x0
pdoffsetcckma1.fab.4=0x0
pdoffset40ma0=0x0000
pdoffset80ma0=0x0000
pdoffset40ma1=0x0000
pdoffset80ma1=0x0000
cckbw202gpo=0x0000
cckbw20ul2gpo=0x0000
mcsbw202gpo=0x88866662
dot11agofdmhrbw202gpo=0x6542
ofdmlrbw202gpo=0x0122
mcsbw205glpo=0x88866662
mcsbw405glpo=0xa9a66663
mcsbw805glpo=0xbb866665
mcsbw205gmpo=0x88866662
mcsbw405gmpo=0xa9a66663
mcsbw805gmpo=0xbb866665
mcsbw205ghpo=0x88866662
mcsbw405ghpo=0xa9966663
mcsbw805ghpo=0xbb866665
mcslr5glpo=0x0000
mcslr5gmpo=0x0000
mcslr5ghpo=0x0000
sb20in40hrpo=0x0
sb20in80and160hr5glpo=0x0
sb40and80hr5glpo=0x0
sb20in80and160hr5gmpo=0x0
sb40and80hr5gmpo=0x0
sb20in80and160hr5ghpo=0x0
sb40and80hr5ghpo=0x0
sb20in40lrpo=0x0
sb20in80and160lr5glpo=0x0
sb40and80lr5glpo=0x0
sb20in80and160lr5gmpo=0x0
sb40and80lr5gmpo=0x0
sb20in80and160lr5ghpo=0x0
sb40and80lr5ghpo=0x0
dot11agduphrpo=0x0
dot11agduplrpo=0x0
phycal_tempdelta=25
temps_period=15
temps_hysteresis=15
AvVmid_c0=2,140,2,145,2,145,2,145,2,145
AvVmid_c1=2,140,2,145,2,145,2,145,2,145
rssicorrnorm_c0=20,20
rssicorrnorm_c1=20,20
rssicorrnorm5g_c0=4,6,6,4,6,6,3,5,6,4,6,6
rssicorrnorm5g_c1=4,5,7,4,5,7,3,5,7,3,5,6
swctrlmap_5g=0x02020202,0x05050404,0x04040000,0x000000,0x047
swctrlmap_2g=0x10081008,0x28300820,0x08200000,0x803020,0x0ff
muxenab=0x10
btc_mode=1
btc_params84=7000
btc_params10=20000
btc_params8=45000
cckdigfilttype=1
paprdis=0
epsdelta2g0=0
epsdelta2g1=0
rpcal2g=0x9
rpcal5gb0=0x33
rpcal5gb1=0x29
rpcal5gb2=0x36
rpcal5gb3=0x2E

Feel free to try on latest CFW (reboot the device once done):
https://github.com/ludwig-v/wireles.../Custom_Firmware/Scripts/Restore_Broadcom_2x2

Documentation for all nvram parameters (From 6.1):
002-14808_BCM4354_BCM4356_BCM4358_-_OTP_Programming_and_NVRAM_Development_in_SDIO_Mode.pdf

thank you! I’ll give it a shot once my other unit arrives. Looks like it shipped yesterday from AliExpress.

 

[zerozoneice]

Do you know if it's possible to change the radio settings in the config?


The 2x2 spatial streams would help with link reliability and overall link quality; aside from just throughput.. If CarPlay is low-bandwidth (25mbps) and latency sensitive... The 165 5GHz channel is hardly ever used, and is limited to 20Mhz: 2x2 @ 20MHz == 173mbps link speed and ~100mbps real-world throughput; it's likely MUCH cleaner of a signal in terms of interference than the lower 5GHz channels. Honestly, just being able to reduce/control channel width could benefit from the reduced interference. Running at 80MHz, your chance of interference increases substantially over 40Mhz, likewise 40Mhz to 20Mhz. It's really a balancing act, spatial streams NEVER hurt performance, but the wider-width you run (e.g. 20, 40, 80) also exponentially increases your interference in populated areas; and can increase your packet loss/error rate and latency. Having the AC radio is beneficial since even AC-wave1 introduced some better handling of interference and AP/Client delivery optimization compared to N.

Most of my skips//drops are due to interference. Running a constant ping to 192.168.50.2, I can watch as I drive through certain areas and see latency/packet loss.

you can always rollback to the june FW which had 2x2 MIMO. Possibly the one before-last as well, where i saw 867mbps. Basically just stop updating when you see 2021.08.24 as next update.

 

[samabbott]

you can always rollback to the june FW which had 2x2 MIMO. Possibly the one before-last as well, where i saw 867mbps. Basically just stop updating when you see 2021.08.24 as next update.

That’s what I’ve done.

That said, VLud actually answered perfectly! I really want to try doing his custom firmware (always wanted to try it, but never got around to piecing how-to do it together).

However, looking at all that he sent. It motivates me to do it. I want to apply his 2x2 MIMO script ++ also tweak the channel and channel width so it’s 165 @ 20MHz.

But I also ordered the Podofo mentioned a few pages ago to test it out… figured I’d wait for it to arrive, so if I brick my v3.0 in the process of messing with it; I won’t be completely screwed. Hahaha

 

[emarcin]

The script only replace the binary responsible for .img decryption (new encryption > old one), you can't brick your unit doing this.

I updated directly from CFW 2021.02.02 to CFW 2021.08.24 on my end, without any issue:

The real update is done by a proprietary binary made by Carlinkit (binary that can rewrite flash with raw data, raw data that can brick your unit)

I currently have version 2021.04.26 AUTOKIT_AppleLike can I upload 2021.08.24 AUTOKIT_AppleLike without any additional scripts?

 

[jbn858273]

Update on Podofo:

But first... a mention that my CarLinkIt 2.0 running AutoKit 07.05.2021 keeps rebooting after an hour or so, and although the web interface keeps telling me there is an update that I download and try to apply, nothing ever changes. This despite emptying the browser cache etcetera as I always counsel others. So I was happy to return from a lengthy road trip on Friday to find the Podofo had arrived.

Plugged it in and it was straight up and running, firmware version 43.0.7... and connected to CarPlay. A short test and a drive later, it seemed to work only every second time of starting up. When working correctly the Wi-Fi network was ConnectBoxWifi... and when not connecting the Wi-Fi network had a suffix of Debug or Dbg. I am vague on these points because I did not have time to take proper notes. The car is a 2021 Mercedes C-Class (W205) with NTG5.5, and it may be total coincidence but the multimedia (COMAND) also locked up in CarPlay at one point, the first time this has ever happened. Not totally encouraging.

Next step therefore was to upgrade the firmware. I could not at this point remember the IP address for the device in order to try an Over The Air update. By the time I could look it up it was just as easy to register on the cheerrdriving.com website (it's free) and download the update image 43.0.9.0.0.4.2.0-2.8.6. The Cheerdriving / Podofo image file is named ISPBOOOT.BIN (this is not a typo). I copied the file onto a blank microSD card and inserted into the Podofo then powered it on from a USB charger. I waited a couple of minutes after the flashing green light turned solid then powered off and tested in the car. All good. Repeated testing out of the car with an Android tablet using the CarLinkIt AutoKit adapter also seemed fine.

I made one short drive today with a brief stop, and the unit connected fine both times. I will make some longer journeys tomorrow (Monday) and update further.

EDIT: I have not yet had time to try unpacking the ISPBOOOT.BIN file

 

[Gjwilly]

When working correctly the Wi-Fi network was ConnectBoxWifi... and when not connecting the Wi-Fi network had a suffix of Debug or Dbg. I am vague on these points because I did not have time to take proper notes.

According to the tech I was working with this is normal operation.
My unit never connects so the Debug network is the only one I ever see.