Verified VCDS User
- Feb 10, 2014
- Reaction score
- VCDS Serial number
Not certain - I'm a developer and we do things differently.Correct me if I'm wrong, but weren't OTA updates introduced with iOS 5?
The vision we've heard so far is this: you should be able to pick up HEX-NET and $RANDOM_HTTP_CLIENT, and just go. It's a good vision.Well... I view the utility as training wheels for the folks who aren't as adept at configuring things as guys like Jason and I and likely others.
The idea that we have to be shackled to it regardless doesn't make sense to me.
I can't disagree. I rather suspect it's the main reason, if not the only reason Uwe hasn't taken off the Beta label. It's been more than two months since I could make Desktop/HN break in any meaningful way once HN is online. I only have older and simpler vehicles, but I haven't seen much of any vehicle-related grumbling in the Beta forum. It's all been about the process of getting online.At some point I'd like to be able to just leave the HEX-NET in the vehicle instead of bringing it back to my desk after every trip
I realize it's still Beta, but.... poke poke.... poke poke...
Jake, I think it's all embedded, or intended to be. WiFi config and OTA software updates can be done in the Mobile UI. It's just sometimes that part is NFG.What would be cool is if the WhyFi assisted setup could be done from the apps if all that java garbage [garbage = java sucks donkey sphincter in all ways] was embedded on the HN.
Allegedly they are, and got updated in the last major fixpack when we had to check for updates 6 or 7 times. [Remind you of Windoze XP with 47 reboots on patch Tuesdays?]I may be missing something re: those ROD updates you mentioned, but I thought those were included in OTA dataset updates.
With Beta programs come frequent updates. That one big push with the WiFi radio firmware update was probably a major outlier though.Allegedly they are, and got updated in the last major fixpack when we had to check for updates 6 or 7 times. [Remind you of Windoze XP with 47 reboots on patch Tuesdays?]
From a network perspective, I think it chitchats with the same back-end servers using the same protocols to discover and obtain updates. From a device perspective, I imagine it uses the same dev/test and manufacturing load interfaces that have to exist anyway. I doubt there was a total re-invention of the wheel. From a UX perspective, I stipulate that training on two different methods isn't ideal, but once the Mobile UI config and OTA update mechanisms are smoothed out, I don't see why people would use the USB utility except as a fallback or rescue mechanism.It's forking update methodologies and is a bad idea IMHO, but then again I've only been programming for 37 years....
Now I'm an Architect so the programmers, implementation guys, and everyone in development hates me equally for understanding the end user process
And I should probably stop putting words in Uwe's mouth so I'll let him carry on/correct the record from here if he wishes.Am just trying to add my 2 inflation adjusted cent input to make a better product.
That's what I'm hoping foronce the Mobile UI config and OTA update mechanisms are smoothed out, I don't see why people would use the USB utility except as a fallback or rescue mechanism.