Forums

Join The Community
RegisterLogin

Poor UI performance

Is it just me or is the performance pretty bad for the UI (the browser in particular). I understand that the 3G connection is slow and that may be upgraded to 4G in the future, but just loading up a web page and scrolling is painfully slow. The delay and refresh when scrolling or clicking on links/etc is so noticeable that I'm concerned that in a few years it'll be so outdated with what we are used to from mobile devices, that it'll be painful to use (it almost is now). Is it due to a slow CPU or graphics processor used for the display OS? Could that be upgraded in the future?

Anyone sharing the same concerns?

-Joe

Yes, mine is slow as well, however, I get the feeling it will get faster when Tesla chooses a final service provider, and upgrades the software to accept 4G connectivity.

I recently logged into my Facebook page via my S, and I have my FB security set to send me an e-mail anytime a new device is used. The e-mail said I was logging in from a device that was located in Chicago, IL (and I am in So California), so that also might be a factor as to why it's so slow.

With that slow speed, does it play flash, youtube, netflix, videos from the web?

The Tesla browser doesn't appear to support audio or video at all, nor does it appear to support Flash.

TikiMan - Try going to an IP look-up Web page and see where it says the provider is located. Until TM activates the WiFi and we can get on a faster router, we won't know if the slowness is a function of 3G speed or the UI software.

If the UI was the problem (as opposed to the internet connection speed), then other functions that are not connection dependent would also be slow. Since other menu and UI functions are not, it's a pretty safe bet that it's the connection speed.

I hope they get LTE eventually. Blazing fast.

I would chalk it up to 3G too, but when I have a page fully loaded, just scrolling up/down has a visible lag and trying to click on a HTML form (like a remember login checkbox) takes 3-5 seconds for the click to actually register on the page. That makes me thing it's more of a CPU thing. The rest of the UI is most likely native code developed while the browser is a custom app they built from webkit. That could explain why the browser is slow but the rest of the UI isn't as much.

A faster connection will definitely make the page render faster, but it won't do anything to speed up the app on a fully rendered page (unless the page is doing some AJAX calls of some sort).

Anyway, not a big deal right now, but I know it's going to be one when the download speed increases but the UI is still slow to respond.

I agree that this looks like a CPU bottleneck.

I only played with the touchscreen for a few minutes at a Tesla store, and I found that most of the UI on the native apps is pretty snappy, but two of them were significantly choppier: the maps app (especially when panning and zooming) and the web browser.

The hardware is a Tegra 3 - essentially a quad-core ARM processor with a beefy GPU - which should be more than enough to drive the screen and the apps that Tesla has shipped so far. The web browser is also WebKit, which on other platforms with significantly less powerful CPUs is able to run much more smoothly. So my hope is that Tesla just hasn't gotten around to optimizing WebKit and that there's a ton of improvement to be had from a potential future update. For instance, maybe their WebKit implementation isn't currenly using hardware acceleration for rendering websites; using a software renderer is incredibly slow and would easily bring the ARM CPU to its knees. Same for the maps app.

Another option is that the screen is just too high resolution for the Tegra (too many pixels to drive). Does anyone know the screen resolution? Maybe someone with the car can go to a website like http://www.screenresolution.org/ both in full screen and half-screen modes and report back?

Is the slowness intermittent? If it is not happening all the time, I wonder if the problem could be that the factory is downloading or uploading data in the background.

On the other topic of videos, it seems like they could make video accessible as long as the car is in park. That might appease the safety activists.

It would be nice to access the latest animated weather graphics or a live highway video during a charging stop before your voyage over a mountain pass.

1920 x 1200. And it does not change from half to full screen. I did the pinch resizing and it is quite slow repainting. That was not a reload from the web.

Another thing I saw: I got my ip address. It indicates AT&T. But when I went back out later, I had a different address and hostname. The hostname indicates also dmz. The new ip means it is getting ip from DHCP I guess, and doing that after it wakes up. I do not have the new power saving download yet. I might also guess from this that the mother ship does not call, instead the car checks in periodically. Probably no way to get it from outside, it just checks in and takes instructions for downloads, pushing logs, crying for help, etc.

I tried SpeedTest.net but it does not work without Flash.

Thanks for testing the screen resolution bfranks273.

In half-screen mode the web browser will be using a resolution of at most 960x1200. That's something the Tegra 3 GPU should be able to handle easily.

Here's hoping there's indeed tons of room for optimization in future updates.

Try this: http://www.tracert.org/bandwidth_meter/ no Flash needed.

OK tried that but highly variable. Here are a series of readings: .55mbps, 2.5, 1.0, .89, .90, 1.1, 1.4, 1.4

I think if Tesla uses the same system as IPhone 5, Internet will work much better

If there's only a lag when a page is loaded it could be a memory/swap file problem IMHO.

ylyubarsky, they use the same browser engine as iOS: WebKit. There are other optimizations I'm sure they can make in the UI.

@Vawlkus, it's not just the loading, it's mainly after the page is fully loaded and rendered. Scrolling down on a long browser page is painfully slow. There's a 2-3 second delay between swiping and the page moving. Same thing for clicking on UI elements (form buttons, checkboxes, etc). I hope this is something they can optimize...

@joe
That's a function of available memory, not the CPU. They can probably patch that to use the internal HD for swap file memory.

Lemme put it this way: the CPU processes the web page into memory, and memory displays it on the screen for you to interact with. If the page is slow AFTER it has been loaded, then it's a memory problem. That's a little simplistic, but it'll do for an explaination.


X Deutschland Site Besuchen