I’ve been using the realdash CAN data source over TCP for years, today it stopped working on my Pixel 7 Pro, can’t connect. Another android device still works fine, my server is fine.
I don’t have auto updates turned on, nothing should have changed.
After a lot of AI help testing different settings and clearing all app data, uninstall, reset, reboot, etc. nothing worked.
I finally found using PCAPdroid (TCP logger) fixed it as it ports all the RD comms through a VPN within my phone. But this has to be running for it to work.
It seems the Android system is specifically blocking RD or the raw TCP frames.
Any help appreciated!
Thanks Darren, and sorry for the trouble! Your PCAPdroid finding was a really useful clue, and I’m fairly sure I know what’s going on.
Android 17 added a new “local network” permission. Apps built for Android 17 need it before they can connect to devices on your own network, like your CAN server, and RealDash doesn’t ask for it yet. If your Pixel got the Android 17 update recently, the system would start quietly blocking RealDash’s connection to your server, even though nothing changed in RealDash itself.
I was able to reproduce this on an Android 17 emulator: the current RealDash couldn’t connect to a CAN-over-TCP server on the local network at all, it just kept timing out, exactly like you describe. With a fix that makes RealDash ask for the new permission, it connected and CAN data came through right away once the permission was allowed.
That would also explain the rest:
- Your other phone still works because it isn’t on Android 17 yet.
- PCAPdroid fixes it because Android doesn’t treat traffic going through a VPN as local network traffic.
- Reinstalling and clearing app data didn’t help because the block comes from the system, not from RealDash’s settings.
The fix should be included in an upcoming update. When it arrives, RealDash will ask for “Nearby devices” access when it starts. Please allow it, because that’s what lets RealDash reach your CAN server. Until then, keeping PCAPdroid running is a fine workaround.
Thanks very much!
My AI searching suggested this was likely the case and that’s great you were able to reproduce and fix the issue.
Yes Android 17, security update 5th of Sept. It was definetely working after that date though.
I did go into the app permissions and set nearby devices which didn’t help. I assume there’s something deeper to go anlong with that.
I’ll wait for the next update!