Waze is INTENTIONALLY not supporting one of the most important stereo tie-in protocols around.

From the WAZE support team:

So who actually uses SmartDeviceLink? Is it cars nobody uses?

I would say Ford and Toyota count as important. The rest of them are certainly worth paying attention to.

If I had the time I would start up Waze, find who was advertising through them and write every one of their advertisers asking why they pay to advertise on a platform that intentionally excludes are large portion of their potential advertising targets. I've tried using Waze on my Titanium level Ford with my up to date flagship Pixel 7 Pro - I'm not using shitty stuff here but Waze doesn't work right on it. I've literally had Waze on my head unit showing where I was 20 minutes ago with Google Maps doing fine on the phone itself.

I can only explain this as some sort of political punishment, especially since I found an old announcement where the teams were announcing with glee the Waze / SmartDeviceLink partnership. My guess is it went sour so their shitting all over the group they used to work with.

Way to go Google! Shit all over your customers AND your users because you're mad at a former vendor partnership.

DUH!

Of course not.

Everyone knows it was Al Gore!

This is what I came here to look for....

It was my go-to social media site for real world interaction.

Now I'm on Minds.

I did catch a bunch of glowies on Google+, and they seemed to cater to glowies, but that's most platforms.

They also happen to be the most used versions of their crap.

That soundbar ESPECIALLY should have the port built in.

When you are in charge of developing for the public you cater to the least intelligent denominator, and the cheapest denominator. I am very happy using my NVIDIA Shield.

Seriously - the cable Internet comes into the house where the cable is - under the TV.
The Ethernet ports are on the cable modem, under the TV.
The Roku is plugged into the TV 3 ft from the cable modem. Under the TV.

It's a high rise apartment building and WiFi sucks because multiple that by the number of Roku's on your floor with the same setup plus the floors above and below yours. The spectrum is saturated because everyone is at home watching and bitching about Velma at the same time.

But, if there was an Ethernet port, people would use it because wired DHCP is so much simpler than logging the damned thing into their WiFi - three feet away under the TV.

However I've never bothered digging into the the specific chips on a modern mobile phone. I have assumptions made based on modems, DACs, RAM, CPU, etc...

I honestly didn't know an e-sim wasn't already an i-sim, or vice/versa. Not sure this article is that big of a deal to the public at large outside of very phonecentric people. Just another "miniaturization and chip combining continues" story. E-sim was a big story - that involved the user and needing to keep track of something physical, past that, the user doesn't care.

I started a project and backed off of it for a bit.

I actually bought an Nvidia Tesla K60 specifically to give the GPUs to VMs for casting Moonlight (possibly the Nvidia streamer it's based on) from Windows VMs, the thought being both my boys could theoretically play off of a single install base at the same time, each from a different VM playing from the same game library on the Shield/something else.

Turns out I can't fit the K60 in my case while my main video card is in (I have a new case in mind) and I was having trouble getting hardware diversion to VMs to work properly. Some of the kernel updates I've gotten recently may fix that, but I haven't put any time into it. Still, I think it was a great idea.

Yeah, I'm totally not putting my family onto a VLC library browser. I've got over 1,700 movies ripped - with a disk for each - I'm not putting them on VLC. I have kids that can't read well yet. My only problem with using Kodi was when I left my server off for too long and it came up with a different DHCP address - guess I need to make that static. Had a reservation on the old equipment, but I'm using the ISP router now and they've Nerfed the ever loving shit out of the interface.

As for me - a place for everything and everything in its place. I have places to set my remotes so that doesn't happen to me - unless the kids are all over everything then all bets are off.

The Shield is awesome.

My kids were playing Stadia on it regularly for a while. I'm now working on replacing that with Moonlight. We've also used it as a Steam Link.

It does Kodi from my Linux system just fine, sadly it only supports SMB, not NFS or SFTP, but that's fine, it works anyways. I suppose I probably could hook up a big-ass USB drive for Kodi, but that's more of a pain to manage.

The remote is incredibly intuitive and easy to use, and it has a locator, which gets used often with the kids around.

It natively plays some of the video games I already had for my phone.

I Chromecast stuff to it occasionally. In fact I've had to tell the kids NOT to cast to it and just use the native apps due to the occasional WiFi traffic issue.

I use Roku's on occasion as well, those work fine for playback only people, but if you're going to go full nerd-shit on it, Nvidia is the way to go.

I've used USB, Bluetooth, and when Stadia was still a thing WiFi game controls on it, they all worked fine.

My Wii quickly got to where it would only work horizontally - yes, optical drive reasons.

I actually changed the optical drive about a year ago.

The lack of Ethernet ports on most Roku shit puzzles and astounds me.

I drew a representation of 27 apartments in a 3 story x3 deep with another next door with a narrow walkway in the middle apartment complex and what it means to be the butthole in the middle where Roku is involved. All 27 apartments have identical setups, a cable jack under the TV, the cable modem/WiFi router combo plugged into that jack in the living room and a Roku 3 feet from it. Because Roku only has WiFi and they didn't bother to use a 6ft cheap flat roll-up Ethernet cable like the one that came with my Steam Link the entire spectrum is completely saturated from everyone deciding to watch the latest Mandalorian show as soon as it airs at the same time. Everything grinds to a halt because half of the apartments are not only doing that but have kids watching Minecraft videos in the bedroom and the other half has has mom doing FaceTime with Grandma in the other room.

Everyones video feed on everything starts to suck simultaneously because Roku didn't bother to put a port on the device and a cable in the box.

BTW - Google had the best idea EVER with the Chromecast Ultra PSU:

https://www.ebay.com/sch/i.htm...

I FAR prefer Waze to Maps, but I can't friggin use Waze in my car.

I sent them a message detailing WTF was going on - similar to this one that was a reply on a discussion. I just reworded the one I sent them I don't have a copy of to remove the "Me Too" stuff:

This was their reply:

I looked up "Smart Link Device" - the consortium consist of:
Ford
Mazda
Subaru
Suzuki
Toyota

I did a little more research, outside of the core consortium:

Bosch
Isuzu
JVCKenwood
Daihatsu
Panasonic
Yamaha

Basically they straight up told me "We no longer support one of the most common standards in existence just-because."

This reminds me of Internet Explorer not support PNG for so long and Apple - well being Apple.

HOPEFULLY with both teams banging their heads together they'll come up with something more usable than Maps - like Waze is - but not completely stupid with not supporting the most common interface in existence - like Waze.

I just don't like the Gnome file managers and default interface. In KDE if I save a file to a directory, the next time I click on a file to save it will go back to the last one I saved in. Gnome stuff goes to ~ EVERY SINGLE TIME. Gnome file navigation feels like early Windows 95 to me. With the KDE stuff it feels powerful.

Yes I know I can replace one thing with another whatever - default QT just feels better to me that default GTK.

It is ABSOLUTELY what I was doing.

The text I didn't expect was something along the lines of 32x32 Font not found.

Turns out the apt-mirror command is lacking. It is known that is lacking. No one is actually bothering to fix it.

I have a system I am prohibited from putting online by management, but I still have to update it with APT. I did massive amounts of troubleshooting trying to get a working offline APT, and I did eventually do it, but it requires running wget AFTER running apt-mirror.