stopcrazypp
Well-Known Member
Doing all the work on the UI thread is the default practice for Android developers so they don't have to deal with concurrency or creating a worker thread. Usually this is not a huge deal in terms of response time especially on something like the Tegra 3 in the Model S (except for the network case you mention, in which case it's recommended to have a different thread handle it).TMore than likely it means the developer took a lock on a UI thread (waiting for e.g. something from the network). That shouldn't ever be done in theory, but it commonly is since it's simpler. Async programming is not for sissies.
But looking at the video, it seems the issue is not really UI responsiveness, but rather the AC cutting off with many button presses. That's probably a bug unrelated to what has been discussed so far.
Last edited: