Skip to content

CanZE for R-Link #144

@yoh-there

Description

@yoh-there

it is often suggested CanZE should be implemented on R-Link. Here is an early (and if I may say rather blunt) example from the German forum:

In the light of the recent "stagefright" vulnerability of Android (and also R-Link), wouldn't it
be easier to hack the OS itself, so one can directly use the CAN processor on the mainboard
and the internal display? Up to now, I haven't found any sign of hacking attempts of the
R-Link system itself. There must be lots of other open doors, given that it is based on the
ancient Android 2.3.

On the face of it, the argument is not unreasonable:

  • The display and processing power are there;
  • It is at least connected to the MM CANbus;
  • No additional devices needed, no mounting brackets for an additional tablet or phone.

Then, there are also strong arguments and uncertainties against:

  • R-Link is, as said, based on a totally outdated Android version (2.3);
  • We would probably be forced to use R-Link UI design elements and rules (not entirely illogical BTW), requiring new learning and cutting flexibility options;
  • We don't know if R-Link is not connected to the main CANbus, which is needed;
  • There is no publicly available tool chain to develop apps for R-Link;
  • If there is a closed tool chain and if we could get our hands on it, it is probably a step back in productivity (Eclipse instead of IntelliJ based);
  • We would most probably have to deal with the whims of both Renault and TomTom;
  • We would have to be much more careful not to break the host platform;
  • Testing would most probably totally car-bound.

My opinion is that I am not (yet) willing to either risk breaking R-Link or buying / learning / maintaining a specific tool chain and emulator / hardware for solely this project.

I can't see this happening really, unless there is explicit demand from Renault. I doubt they are interested and given the effort needed we'd have to even talk some sort of compensation. Given the free-beer nature of this project, I see us opening up a nasty can of worms between the team members.

This this will not happen. IMHO.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions