ENTRYnav2 F45 installation- connection refused

[skha-max]

Hi,

We were in touch in sqooky form. I have working wireless carplay. Now I am trying to install it in my 2 series. I got SSH access as from feature installer. I started it and then moved to CMD but i am still getting connection refused and connection closed. Could you help me with toubleshooting the installation steps which i am missing.

[Gsonz04]

Make sure you have diagnosis mode enabled. I once forgot this and encountered the same problem.

[skha-max]

@Gsonz04 sorry. I am a newbie. Could you explain where i should enable diagnosis mode?
Thanks

[Gsonz04]

Not sure how it works on your 2 series, in my G21 you do it by quickly pressing the engine start button 3 times.

[Jiraiya43]

Hi, thanks for the photos, they show what is going on.

1. The address. Use 169.254.1.0. It is the head unit's default address on the ENET cable, and the cars reported so far answered there (my G20, an X3 G01, an i3). Your 169.254.86.122 answers ping but refuses SSH, so it is probably not the head unit: more likely another control unit of the car, or your PC's own address.

To check, with the ENET cable between the OBD socket and the PC, the network card left on automatic addressing, and the car kept awake the whole time (Gsonz04's point above):

ipconfig
ping 169.254.1.0
ssh root@169.254.1.0

• ipconfig: if 169.254.86.122 is listed under your Ethernet adapter, it is your own PC.
• If ping 169.254.1.0 gets no reply, run arp -a and post the lines under that adapter.
• ssh needs a space after it: ssh-p was read as one unknown command.

2. The messages.

• Connection refused: a machine answered at that address, but nothing listens on port 22 there. My head unit never answers that way: it either asks for the password or stays silent.
• Connection closed: only scp saying its SSH connection failed. It follows from the line above, it is not a second problem.
• If ssh root@169.254.1.0 ends with Connection timed out while ping answers, you are on the head unit but SSH is not open on it at that moment.

3. The version. The commands at the bottom of your second photo are the 0.12.0-rc.1 ones, and you downloaded the rc.2 archive, so the names will not match. For rc.2, from the PC:

scp entry-aad-0.12.0-rc.2-armhf.tar root@169.254.1.0:/tmp/
ssh root@169.254.1.0

then, in the SSH session:

V=0.12.0-rc.2
cd /tmp && rm -rf entry-aad-$V && tar -xf entry-aad-$V-armhf.tar && cd entry-aad-$V

The rest is on the install page of that release. The later commands use $V: retype the V= line if you reconnect.

4. Wi-Fi. Your second photo shows the fault 0xB7F81A: Connection between head unit and WLAN antenna: Line break. Wireless Android Auto uses the head unit's own Wi-Fi, the one wireless CarPlay uses. If that fault is current, wireless will probably not work on your car, and the USB cable is most likely the way to go: in the Android Auto menu of iDrive, tick USB cable instead of wireless (it is in 0.12.0-rc.2), then plug the phone into a USB socket of the car with a data cable.

The limits: this mode is experimental. Picture, controls, microphone and GPS go through the cable, but the sound still goes through the car's Bluetooth, so the phone has to stay paired with the car. It has run on my G20 and on an i3 (#19); nobody has reported an F45 yet. Details in docs/USB.md (in French). You wrote that wireless CarPlay works: if it really connects without a cable today, the fault may be an old one, and wireless is worth one try first.

Step 2 of the install page changes nothing on the car. Its output (the first line of /etc/version and the @ok / @warn / @block lines) would be useful here, since yours would be the first F45.

One more thing: your second photo shows your VIN in full. You may want to replace it with a cropped one.

[skha-max]

Thanks for the detailed analysis. I will recheck the IP again. That IP was shown in the feature installer after connecting, so I thought it was correct.

Regarding the version, I downloaded all versions, and they are in the same folder. I noticed that line break error in the antenna before, but wireless Apple CarPlay works fine without any disconnections.

One more thing, do I need to start the feature installer app every time and keep it open during the whole process?
Also I am not sure about the diagnosis mode option in my car, and I cannot find any guidance online. Is three short clicks on the start button fine? I have not done that during remote CarPlay activation.

Since I am the first one, I would like to be a bit more careful, so I will update you on the status of step 2 before writing anything to the HU. Also, is there any need to back up any codes in case something goes wrong?

I really apreciate your support

[skha-max]

@Jiraiya43
It worked... i used rc.6 version

I think i have a good new with compatibility. But i want to confirm it before start writing. Please see brief log below and further in screenshot.

/etc/version: 202402191339
md5sum -c MD5SUMS: all OK
df -k /: 504892 KB available (92% used)
Compat check: all @ok, no @warn/@block
@ok|abi|
@ok|vmost|
@ok|mic|
@ok|video|1280x480
@ok|alps|
@ok|uuid|0300000000decafadedecadeafdecacaff0300000000decafadedecadeafdecacafe
@ok|spp|
@ok|hotspot|
@ok|gps|
Car: BMW 225xe (F45), EntryNav2/EntryEvo, hostname xse-j6-apn-entryevo

Please let me know so i can proceed.

[skha-max]

Thanks for the quick fix. I will install it tonight. Wifi AA screen freeze issue came back after driving 15 minutes. Since i am away from home. Cannot capture logs

[skha-max]

The wireless connection worked fine for the first 15 minutes and then started to buffer.

Today, I updated to the latest version, RC4. Please see the new logs with 12.1 RC4.

The first attempt is with wireless; I tried touch and drag, then two-finger touch on Google Maps, but there was no response on the screen. It was frozen and then disconnected.

A second log was captured with wired AA. I made a few touch and scroll attempts, but there was no response. The media and map buttons work fine.

Yesterday, I made an interesting observation: touch and drag and two-finger zoom work fine on AA when my wife uses the screen, but not when I or our daughters use it. At the same time, our fingers are perfectly detected on the normal iDrive screen. I checked with my daughter's fingers, and hers are not working either on AA. It registers a touch, but touch and scroll or two-finger gestures do not work with our fingers. Strange.. but i tested it more than 10 times.

Idrive buttons Such as MEDIA works fine.
Another noticed glitch is that the display briefly shows the iDrive call disconnection screen while I disconnect a call.

wireless app 12.1 rc4.log
wired app 12.1 rc4.log
wired entry-aa-service 12.1 rc4.log
wireless entry-aa-service 12.1 rc4.log

[Jiraiya43]

Thanks for the logs and the careful testing, the observation about different fingers is useful.

Touch (wired and wireless): in your wired log, each attempt to drag reaches Android Auto as a press and a release 0 to 10 ms apart, at the first point, and the rest of the movement is dropped. So the first frame of your touch is read, and then the head unit's frames stop matching what the service expects for a finger that stays down. Why this happens with some fingers and not others is not visible in this log: it only records the raw frames of the first few touches after start. I'm looking into it.

Wireless: the log shows the same pattern as on the G21 in #26: the head unit is waiting while the phone goes silent for 1 to 4.7 s at a time, until it stops answering for 5 s and the session ends. On that car the cause was the phone: it went away after updating Android Auto (18.0.664274) and Google Play services. Please update both on your S25 Ultra and try wireless again.

Call screen: the iDrive's own call screens are drawn above Android Auto, so the "call ended" screen showing briefly is expected.

[skha-max]

Thanks for your input. I confirm that Play Services and Android Auto are already updated. I also checked the Wi-Fi and Bluetooth scanning settings; it is not making any difference.

Regarding the touch screen issue, the provided log does not have inputs taken from my wife.

I again tried using my fingers with moisturizing, different fingers, different pressure, etc. No changes in AA other than registering first touch. At the same time i can scroll, pinch to zoom on idrive interface.

Wireless AA still lags a lot and I am using it wired.

Also, were you able to confirm that my HUD does not have the feature to capture and display map arrows other than from native BMW maps?

Thanks again for your dedication on this project

[Jiraiya43]

Thanks for checking all of that.

Touch: understood, the log only had your touches. The log shows the first frame of each touch arriving and the following ones not being taken as the same finger, so a drag ends as a tap. I'm looking into it; the current logs only keep the raw frames of the first touches after start, which is why the reason is not visible yet.

HUD: for the F45, the guidance does not reach the cluster today because the project sends it over Ethernet, as on the G-series. Another owner has just found, on an F48, how BMW's own navigation sends the arrows on F-series cars, and that it can be driven from outside (#79). The F45 is very likely the same, but nothing is ready for it yet.

[skha-max]

Hi again, please see the logs. Wireless AA worked without lag for the first two minutes after connecting. Then it started to slow down and then lagged horribly. It also disconnected in between. My BMW app and AAIdrive were in a forced-close state.

Wired AA worked without any new events, but the touch issue persists. I also tried physical buttons and steering buttons. Finally, I did a few reverse and drive maneuvers.

I will update to latest version tomorrow.

wireless app.log
wireless entry-aa-service.log
wired app.log
wired entry-aa-service.log