Search results

Looks like the browser will get some love and much needed bug fixes.

Looks like the browser will get some love and much needed bug fixes.

Yes, they fixed the browser issues around using GPS, but this is the buggiest version of the browser to date. It hangs and crashes a lot.

I will contact someone from Tesla. I suspect that they already know.

I have not changed code on the website for at least 6 months. Did you recently have a Tesla update? Normally you would see a tesla browser message to allow website location access. This is something that is not controlled by the website. Does other websites have this issue like ABRP? I'm...

So Browsers by default block access to GPS location and will prompt you for consent. In the old MCUv1 and MCUv2, they would show you a dialog. If that dialog does not display they are blocking access to your location from a web page. I do not have access to a MCUv3 so I can't really debug this...

This should be working now. Let me know if it is not working for you

Waze stores the average speed cameras info on their map road segments. Our maps does not come from Waze. It is from MapBox Average Speed Zones - Wazeopedia

I have MCU1 with 219.12.1.1, and it's still the old browser, with the same old issues

Nope, I don't have 2019.12

I do not have this update, only on 2018.50

No there is no way to play sound thru the browser.

Right now it's a proximity thing based on speed and is computed every 4 seconds. What version MCU do you have? I'm thinking on updating it to every second on MCU v2. Do you feel that the warning is too late?

Ha ha, game on!

If you know how to do that, please let me know.

In the settings menu

No the Tesla App

Yes, it's a separate database. You can send a report thru the app of the camera was removed.

No, the Tesla browser does not support WebGL.

The style for the setting bar is "bottom: 0" so if it's getting cut off, it's a Tesla browser bug. I don't have v9 yet.....don't really want it.

The issue has nothing to do with moving off of Google maps. It just coincided with the Tesla update of the browser to HTML5, which is very buggy and the JavaScript VM crashes all the time for no apparent reasons.

The weather radar issue has been fix.

Yes, it's currently broken. :(

yea, saw that. The newest webapp version is out there and it's pretty fast. There are two options, upgrade the MCU to v2.5 and Tesla needs to fix the java script VM so that it stops crashing all the time. It's not a server backend issue. I can throw as much iron as possible and it will make no...

Yes, that is currently by design. Processing the weather map is kind of expensive, for MCU 2.5, that should not be an issue. I can make that persistent in a future release

Nope. Moving the map API from OpenLayer to Leaflet seamed to solve the issue. Everything works fine under Chrome :(

I'm finishing another rewrite (yet again) of the teslawaze app, and I think the new version address all the current problems. You should see a noticeable speed improvement and it looks like the browser crashes are gone, so hang in there a little longer. Moved the MAP apis from OpenLayer to...

I'm finishing another rewrite (yet again) of the teslawaze app, and I think the new version address all the current problems. You should see a noticeable speed improvement and it looks like the browser crashes are gone, so hang in there a little longer. Moved the MAP apis from OpenLayer to...

So I stopped by the Tesla store in the mall yesterday, and I got to play around with the new MCU, holly cow it's fast! This website is much more usable and responsive.

Well, running the website in Chrome for a day, shows max memory usage of the JavaScript VM instance is 16 MB.

Forgot to add, that we are now at 2 million reported police locations in western Europe. The new police trap areas has also been updated.

Well, we have been living with mapbox maps for a month now, and I was not really happy with their traffic layer. I just pushed out an update that now pulls traffic data from the waze feed. Traffic is now fully render on the server side, so there should be some improvements in the car browser...

Known issue. The Tesla browser ignores the "user-scalable=no" header meta-tag (tesla browser bug?), so the body can only fill 99.9% of the browser window height. I can fix this by painting the body background black in dark mode, just did not have the time yet it fix it. Yes...it bugs me too

I'm P85D with 3G..so you LTE people are spoiled :)

I had this issue and it ended up being because my Android phone was plugged in to the cars USB port, only to charge it. It seamed that the cars USB drives was crashing the MCU because it tried to talk to the phone storage system. Went to a cigarette lighter USB charger and had no issues since.

Street level traffic currently does not auto update...you need to refreash the browser :(

Made reddit.. r/teslamotors - TeslaWaze is back and it's way better.

This that don't work yet: Panning the map Tesla browser bug, Browser does not respect the "user-scalable=no" header meta property Tesla browser bug. Browser does not handle the element.pointerEvents = "none" property Traffic camera alerts doe not work Traffic Jam paths do not render Alert...

Correct, with the ,12 update the browser now continues running even if it is in sleep mode. It was hammerings my server up a million requests a day until I figured out what was going on. I updated the app that if your car has not moved in 10 mins, then I stop polling/updating. I also had MCU...

Because: I don't have the time or want to spend the time to turn this into a business. II don't want to give ANY money to Google. Period. I feel that they are trying to hold you hostage by extorting high fees and only give you 30 days’ notice before they start charging. I can't believe how...

So to be clear, at this point I'm not giving any money to Google, after this fiasco.So I looked at other options, and of course Open Street Maps is the best option right now. I have setup my own OSM tile server, and there is definitely more work involved here (mostly styling issues). To...

Also, before this happened, I "was" working on Waze routing now that we are not restricted to 30 second GPS updates.

Yes, I plan on moving this to OpenStreetsMaps. I'm looking at different self hosting tile server options. It's a PITA, I wish they would have told us sooner. :( It's going to be down for a while.

There is no way they don't know about this site as it drives 33 GB of data thru their cell network per week.

They are moving to MapBox, which is based on Open Street Maps. Their hope is to have large companies fund open source maps. Tesla’s highly-anticipated new navigation and maps engine is coming this weekend, says Elon Musk They already are. Tesla releases new Waze-like crowdsourced traffic...

Google owns Waze. I suspect it won't be free much longer.

Edit -> View Source Seriously, it in a local git repository.

I think the whole point now is NOT to pay Google.

It's an option. I'm not the only one getting screwed by Google and I'm following the forms to see that other people are doing. There are other options: Bing maps: (cost fee is to complicated to understand without actually switching over to see what you get billed). Mapbox: Seams like the...

This is the end.... As you may not know, but Google has decided to charge for all access to their mapping service. At my current usage, I'm looking in an excess of $800 a month to continue running this service. Even if I remove the elevation usage, I'm still looking at $500 a month in charges...