BertL
Active Member
Yes, at least one owner upthread (it's a long thread already!) has already reported the apparent missing Slacker & TuneIn Credentials screen to Tesla.
-
Want to remove ads? Register an account and login to see fewer ads, and become a Supporting Member to remove almost all ads.
Yes. It was not working at all in 7.1 for the past few months. Working well - so far - in 8
Ulmo
Active Member
This is great news. Those are sensible things that I used to complain about and expected to be fixed.
So, in other words, the Israeli Mobile Eye was screwing up Tesla, and killed that Florida driver. Yeah, I said it. I said a long time ago that the Tesla + Mobile Eye partnership was a bad idea. I am entirely happy that Tesla has made progress on this situation. If Tesla keeps their attention on it, they can lead from ahead and not behind, and show NHSTA the right way to do it rather than have NHSTA lead them around by the nose (like Mobile Eye was setting them up to do).
We can expect Tesla to get steadily better now with AP. These are major improvements. In all honesty, most of us AI aware programmers expected this level of function a few years ago shortly after AP first came out, but like I've said in the past, now that Tesla is on its way, it's all progress now. We can look forward to incremental steady improvements every 6 to 18 months for a while now, and I suspect we'll see it going much faster than that during many jump periods, like this next couple of months, when I suspect it will be phenomenal improvement, COMPARED to what we had. AP improvements will be fun to watch.
IT IS NOT AUTONOMOUS YET. WITH EVERY STEP FORWARD, IT MIGHT DO SOMETHING OLD WORSE. YOU HAVE TO BE THE MAIN DRIVER AND TAKE CONTROL AT A NANOSECOND'S NOTICE. Ok, that's out of the way. Seriously, some "advancements" will be steps backward sometimes, so watch out.
rickrickrick
Member
I finally found it. You have to scroll the panel up, the login area is at the bottom of the music streaming panel.
BertL
Active Member
I don't have 8.0 yet, but try changing the name of the root directory of your USB stick, insert again and let it be scanned. If 8.0 is like 7.x, that will cause any tracks that may have Gracenotes album art to be ignored and pulled back down the next time you play the track. Rebooting the CID may help, but my past experience is to resolve the problem takes Media Player to think your tracks are all new to get the art (as strange as it is sometimes) flowing again...
Not even close. As far as I can tell, not one single X has been upgraded yet.
Everyone got the latest 7.1 in the last few days - the security update - so that shouldn't be a factor.
BertL
Active Member
You're not alone. Welcome to the left-in-the-dust club.
Check the tracker and you'll find 8.0 is being much more slowly released than some others have been. As my grandmother used to say, "patience is a virtue". Ah ha ha.
Ulmo
Active Member
According to ev-fw.com, it is around 10% (53 of 529 reported) so far that have it. This is just a sampling, but I consider it a fairly moderate sample size.
53 is the number of cars which reported having 2.36.108, which is the first widespread* release level 8.0.
529 is the number of cars which reported having 2.36.31, which was supposed to be 100% spread to every car to fix a security hole. Since this was only a few days ago, and it was to plug a security hole, I use it as an extremely easy and accurate approximation of the number of live FW reporters that would be likely to report 8.0 FW at this time. We are relatively lucky that a security hole got patched so few days before the release of an intensely interesting FW release, for this reason.
ev-fw.com only represents those who wish to report, so, participants from TMC, mostly.
-------------
* 2.36.106 was the first 8.0 released, but it was pulled so fast they "hammered"** it, and didn't even use proper English in writing the note about that they were so hurried; they very effectively halted its release before it became "widespread", even disabling it in cars that had downloaded it successfully and were ready to install it (but hadn't yet done so because owner hadn't given consent), with only 3% getting it installed, and reportedly only 1.7% still not since upgraded to 2.36.108, if ev-fw.com reports are to be believed.
There is a bad precedent, which I got from reading eyewitness reports on TMC and analyzing ev-fw.com: Analysis shows that Tesla quickly sent the fix to .106 to those that installed it, 8 of the 17 on ev-fw.com getting .108 installed within a day. That is good. What is bad is that analysis also showed that many who were offered .106 but did not install it and got it "hammered" out of their car, have not subsequently been offered .108, introducing a "damned if you do damned if you don't" dilemma of what do you do if you have the option to install a known dangerous firmware in order to "lock your place in to get the fixed upgrade sooner" (some people had this option and knew they had this option --- they had the files staged while in good network range (wifi) but parked in a parking garage in bad network range (1 bar or less LTE) when it got pulled, so they could have been able to install without the pulling --- and in any case, a "rush to install" might be a statistically significant hurt level from this kind of behavior). In my humble opinion, Tesla should have circumvented this dilemma by simply pushing .108 forcefully to EVERYONE who had .106 staged or a reasonable approximation of almost done staging (some people know when their car is getting ready to metamorphose), WHETHER OR NOT they tried installing it. (Simply pushing .108 to everyone who had .106 pushed would have neatly solved that.)
** I presume "hammered" means they went after the release and pulled it back out by doing something similar to zero'ing out the upgrade files in place so it wouldn't signature verify. It might not mean that: it may mean that the MCU had a bug that made it freeze because some piece of it got "hammered" in software causing the hang bug. Doesn't really matter here to my point about the releases.
Last edited:
I got 8.0 today, and I'm not sure it adds much for me (non ap). Maybe a little more slick overall.
Unfortunately I seem to have lost album cover art on regular fm stations. Anyone else notice this? I still get them on slacker, but on fm I just get generic station logos. I hope this isn't permanent because it's a big downgrade in terms of polish imo.
Unfortunately I seem to have lost album cover art on regular fm stations. Anyone else notice this? I still get them on slacker, but on fm I just get generic station logos.
I hope this isn't permanent because it's a big downgrade in terms of polish imo.I for one I'm glad that it will be in a future release because I don't want automatic emergency braking to suddenly switch what it uses to activate until a certain amount of time has been given for fleet learning. I also like knowing exactly when it does get switched. So I can hold off on that update for a few weeks.
jchag
Member
I'm hopping for better Nav pics. Currently when an exit appears on dash screen it shows a pretty grassy freeway exit. I'm hoping for a more realilistic California picture ( dead dry weeds with litter)
Even if they do it in a future update, there is no way they can switch it for all roads at the same time unless they are going to wait years. So even once it uses the new improved AEB it will act differently on different roads. (I wonder if Tesla will publish any details on witelisted roads, or make some indication on the IC that lets you know which type of AEB is enabled.)
Click on media. Go full screen. Click on stream or TuneIn. Scroll to the very bottom is the login screen.
TuneIn login works. Slackers login hangs at the moment
