Live data from Hacker News

GM Backed "Open Source Protocol" for Connecting Vehicle Apps and Services

projects.eclipse.org

21–30 of 43 posts

Re: GM Backed "Open Source Protocol" for Connecting Vehicle Apps and Services

#21
post #15

Earlier quoted context omitted.

That hasn't been my experience with a 2021 RAV4. The Toyota system is much more reliable then Carplay. Which I've heard is itself more reliable than android auto. I imagine partly because it uses the physical buttons located around the screen, partly because automakers have much more stringent requirements for software validation. e.g. Maybe 1 out of 1000 times the built in maps app crashes, gives an error, or doesn'…

I've never experienced a "crash" in Maps or Google Maps, whether on carplay or on the phone. Maybe there is something wrong with your car/phone? Carplay & android auto do have issues connecting at first but the apps themselves never seem to crash.

I said 'crashes, gives an error, or doesn't respond to an input'?

Have you never had an unresponsive screen before?

Re: GM Backed "Open Source Protocol" for Connecting Vehicle Apps and Services

#22

Earlier quoted context omitted.

At this point the horse is out of the barn. People want a connected center screen. Figure out how to do it in an open way if you must, but telling people not to want it doesn't work.

People want tactile hard buttons, not a "connected center screen". Who started this myth?

Marketing, of course. People are being told what they should want, which conveniently lines up with cost savings from the companies themselves..

Re: GM Backed "Open Source Protocol" for Connecting Vehicle Apps and Services

#23

After the failure of pretty much all embedded automobile platforms like microsoft sync that people really don't want yet another crappy middleware platform, the automotive industry is trying this shit again removing android auto and apple carplay after people actually got what they want. Why? Auto vendors realized they lost control through their ineptitude of the user interface, and want it back. Problem is no one wa…

That hasn't been my experience with a 2021 RAV4. The Toyota system is much more reliable then Carplay. Which I've heard is itself more reliable than android auto. I imagine partly because it uses the physical buttons located around the screen, partly because automakers have much more stringent requirements for software validation. e.g. Maybe 1 out of 1000 times the built in maps app crashes, gives an error, or doesn'…

If Toyota integrated CarPlay correctly, it wouldn’t be crashing. Instead, they prioritize their inferior system, which only leads to better experience because the other one is gimped.

Re: GM Backed "Open Source Protocol" for Connecting Vehicle Apps and Services

#24
There's some previous submissions ~6 mo ago but not much traction. https://hn.algolia.com/?q=%22uprotocol%22

Since it's not named in the title it's: Eclipse UProtocol. Protobuf & CloudEvents. Url-based, with different devices ("UDevice") each getting their own dns name ("UDomain"). Somewhat transport agnostic. Http2, amqp, mqtt, dds (used some in ROS robotics os).

Re: GM Backed "Open Source Protocol" for Connecting Vehicle Apps and Services

#25
There's some previous submissions ~6 mo ago but not much traction.

Since it's not named in the title it's: Eclipse UProtocol. Protobuf & CloudEvents. Url-based, with different devices ("UDevice") each getting their own dns name ("UDomain"). Somewhat transport agnostic. Http2, amqp, mqtt, dds (used some in ROS robotics os).

This makes me rather miss Webinos, which was a connected is with pretty interesting end user privacy systems kind of built in that let the device kr car talk to a cloud, but a user defined cloud.

Re: GM Backed "Open Source Protocol" for Connecting Vehicle Apps and Services

#26
post #23

Earlier quoted context omitted.

That hasn't been my experience with a 2021 RAV4. The Toyota system is much more reliable then Carplay. Which I've heard is itself more reliable than android auto. I imagine partly because it uses the physical buttons located around the screen, partly because automakers have much more stringent requirements for software validation. e.g. Maybe 1 out of 1000 times the built in maps app crashes, gives an error, or doesn'…

If Toyota integrated CarPlay correctly, it wouldn’t be crashing. Instead, they prioritize their inferior system, which only leads to better experience because the other one is gimped.

That's possible, but I haven't seen any evidence that Toyota's integration is notably worse then other automakers.

Re: GM Backed "Open Source Protocol" for Connecting Vehicle Apps and Services

#27
post #15

Earlier quoted context omitted.

I've never experienced a "crash" in Maps or Google Maps, whether on carplay or on the phone. Maybe there is something wrong with your car/phone? Carplay & android auto do have issues connecting at first but the apps themselves never seem to crash.

I said 'crashes, gives an error, or doesn't respond to an input'? Have you never had an unresponsive screen before?

I’ve used carplay with a iphone 12 nearly every day for 2 years and never had issues with it crashing or becoming unresponsive. Stability issues definitely makes me think it’s a problem with your setup.

Re: GM Backed "Open Source Protocol" for Connecting Vehicle Apps and Services

#28
post #15

Earlier quoted context omitted.

That hasn't been my experience with a 2021 RAV4. The Toyota system is much more reliable then Carplay. Which I've heard is itself more reliable than android auto. I imagine partly because it uses the physical buttons located around the screen, partly because automakers have much more stringent requirements for software validation. e.g. Maybe 1 out of 1000 times the built in maps app crashes, gives an error, or doesn'…

I've never experienced a "crash" in Maps or Google Maps, whether on carplay or on the phone. Maybe there is something wrong with your car/phone? Carplay & android auto do have issues connecting at first but the apps themselves never seem to crash.

Google Maps crashes all the time on my Pixel phone, and I hear similar complaints from friends of mine on Samsung and Motorola phones. Note that this is without using Android Auto.

Count yourself lucky if you have a stable, crash free Google Maps experience!

Re: GM Backed "Open Source Protocol" for Connecting Vehicle Apps and Services

#29
post #16

Earlier quoted context omitted.

It doesn't have to be Bluetooth. We had local wireless remote start and control solutions long before "cloud" or even BT or WiFi was a thing.

Add LoRA support to phones and you could have it miles away. But that would not require a subscription.

Heck, put LoRA and Bluetooth Low Energy in the remote, then your phone can send this message through BLE and the remote will relay it to the car seamlessly from significant distance.

Re: GM Backed "Open Source Protocol" for Connecting Vehicle Apps and Services

#30

Earlier quoted context omitted.

I said 'crashes, gives an error, or doesn't respond to an input'? Have you never had an unresponsive screen before?

I’ve used carplay with a iphone 12 nearly every day for 2 years and never had issues with it crashing or becoming unresponsive. Stability issues definitely makes me think it’s a problem with your setup.

It sounds like you are an outlier then, there are many many videos on youtube showing Carplay to not respond 100% of the time.
Post reply on HN