Related
Is there anything that will take care of that sudden jerk when you start to scroll in the browser? It's very annoying. It's been improved over the stock ROM using other ROMs, but it's still there. When you start to scroll...it snaps/jerks before getting smooth. Yeah, yeah...I know...we have a SNAPdragon processor... LOL...but hope you know what I mean. Seems to only be happening in the browser, stock/dolphin.
Mine seems very smooth in Dolphin, Im not sure what youre refering to exactly. Is there a video or anything that shows what you mean?
mines smooth as can be as well.
Mines smooth with no snap at first...
Agree with the above people. Can you post a video? Mine's just fine.
Only video camera I currently have is on the Nexus. Sorry. But, you really only notice it, I guess, when you do a slight scroll. It's very minute, but...ah...must just be an OCD of mine.
I think I know what you mean. You scroll and its late to react so it jumps ahead. This is something I only noticed after using another device ( that I wont address by name because it hurts peoples feelings around here )which scrolls a lot smoother. And its not just the browser its all scrolling. But again, if I hadn't used the "other" phone first I wouldn't even notice it.
If you are comparing to the iPhone, this is just because the Android browser isn't optimized as much. It has the GPU power to do it, but you can have a computer chiptset in there and it won't run smooth unless the software is further optimized which I'm sure Android is working on...or hope...
DMaverick50 said:
I think I know what you mean. You scroll and its late to react so it jumps ahead.
Click to expand...
Click to collapse
Bingo!
Ruben1123 said:
If you are comparing to the iPhone, this is just because the Android browser isn't optimized as much. It has the GPU power to do it, but you can have a computer chiptset in there and it won't run smooth unless the software is further optimized which I'm sure Android is working on...or hope...
Click to expand...
Click to collapse
Man...hope they get it done soon! Or, hope a dev is working on something to get it to 100% perfection...or at least 99%....I think it's at about 96-97 right now. LoL
Yep, the iPhone has much smoother scrolling(there, i said it.), i did a direct comparison in google maps between the n1 and my dad's old ipod touch. The touch movement is far smoother and feels more real, as real as a scrolling image on a screen can be i suppose.
M
Ruben1123 said:
If you are comparing to the iPhone, this is just because the Android browser isn't optimized as much. It has the GPU power to do it, but you can have a computer chiptset in there and it won't run smooth unless the software is further optimized which I'm sure Android is working on...or hope...
Click to expand...
Click to collapse
Yeah I agree, android is young but google will take care of the shortcomings. Just have to be patient
I can't believe anyone even noticed this!
I've had my nexus one for near 2 months now (and an iphone before that), and I've never noticed this 'problem' until I looked carefully after reading this thread!
GlenH said:
I can't believe anyone even noticed this!
I've had my nexus one for near 2 months now (and an iphone before that), and I've never noticed this 'problem' until I looked carefully after reading this thread!
Click to expand...
Click to collapse
Oops...Sorry!
I suppose the rumors weren't true, then?
halorin said:
I suppose the rumors weren't true, then?
Click to expand...
Click to collapse
I saw someone on here posting a quote about the multi-touch fix... lemme find it
by Paul22000:
Also "A scale gesture detector API provides improved definition of multi-touch events."
I wonder if that means the N1's multitouch axes will be fixed for gaming!
halorin said:
I suppose the rumors weren't true, then?
Click to expand...
Click to collapse
since nobody has froyo yet, we dont know if it was fixed or not. i really hope they did though.
Thanks for the responses, guys. I guess in hindsight it might have been good to leave out any negative things in such a positive conference.
But still, some mention would have been comforting.
halorin said:
Thanks for the responses, guys. I guess in hindsight it might have been good to leave out any negative things in such a positive conference.
But still, some mention would have been comforting.
Click to expand...
Click to collapse
I feel the same way halorin. It's natural to voice displeasure over something important missed in an update (I would have loved 360* rotation, colored trackball, fm radio, etc) but I know your happy about the update when it does occur and a great guy to have on the forum
All progress is still progress toward perfection, no matter how small.
Thing is, they were just demoing the OS, not device specific things like the N1's trackball & whether it has working FM etc.
Very valid point, Rusty.
Yup, each device will have their own seperate updates with device exclusive things.
Rusty! said:
Thing is, they were just demoing the OS, not device specific things like the N1's trackball & whether it has working FM etc.
Click to expand...
Click to collapse
*in Kramer voice* ........ you just blew my mind...
ap3604 said:
I saw someone on here posting a quote about the multi-touch fix... lemme find it
by Paul22000:
Also "A scale gesture detector API provides improved definition of multi-touch events."
I wonder if that means the N1's multitouch axes will be fixed for gaming!
Click to expand...
Click to collapse
That quote is from the highlights web page:
http://developer.android.com/sdk/android-2.2-highlights.html
The axis problem can never be fixed 100% because the hardware doesn't report enough info to do it for all cases, but currently it is pretty bad and I think better drivers/software could get it close. I believe that Cyanogen's ROMs have had some tweaks that have greatly improved its responsiveness for some time now so perhaps the Android engineers adopted similar fixes. It will hopefully get good enough over time that you'd have to know exactly how the sensors work and deliberately try to fool the drivers in order to get it confused.
I tested a nexus one on froyo today at google i/o, some things that were absent, colored track ball, touch screen wise they didn't have any multi touch analysis program installed, but just pinching around I don't detect any notable differences, so i'm guessing no to those 2 features on nexus, at least on their current build
I was also at I/O and while I did play with a few different Nexus Ones that were loaded with FroYo, I was unable to determine if any screen fixes were applied.
I asked a few times and each time I was politely told that they could not talk about anything that was not already made public (fair enough btw).
However, pinching and zooming on maps seemed to be smoother (not sure if it just my impression or some actual change) and it seemed to respond overall to my finger movements more smoothly.
Also, some games that I demoed on a few different Nexus Ones did employ finger gestures and those games functioned flawlessly from the touch perspective.
I am not sure that translates into any real fix or just my biases, but I am putting it out here for whatever it is worth.
Dan
dan1431 said:
I was also at I/O and while I did play with a few different Nexus Ones that were loaded with FroYo...
Click to expand...
Click to collapse
Did you notice if there was 360 rotation? ie could you flip it from 12 to 3 O'Clock clockwise and get it to rotate to landscape when in a rotating app like Maps?
logger said:
Did you notice if there was 360 rotation? ie could you flip it from 12 to 3 O'Clock clockwise and get it to rotate to landscape when in a rotating app like Maps?
Click to expand...
Click to collapse
I hate to admit this, but I did not even think about testing that feature.
Dan
Dorick said:
I tested a nexus one on froyo today at google i/o, some things that were absent, colored track ball, touch screen wise they didn't have any multi touch analysis program installed, but just pinching around I don't detect any notable differences, so i'm guessing no to those 2 features on nexus, at least on their current build
Click to expand...
Click to collapse
Dorick, by any chance have you noticed wifi-n connection?
I'm almost certain from the API improvement and UI modifications listed on the Android SDK site that we have a software fix for the crazy multitouch issue.
Having said that, it means the screen won't go crazy when the paths "swap". But, it's still limited to two touchpoints and not 10 like the 3000 series screen.
A fix is a fix though. =)
Personally if the have fixed up pinch zooming somewhat and made it smoother that will cover me 99% of the way as I use the device so that will be pretty much a fix assuming we actually see it in the official N1 rom.
Hey guys, I tested the evo 4g multitouch input with the multitouch visualizer yesterday and found that though it does have much better tracking than the nexus one(no crossing and stuff) it does seem to have significant input lag, I do not have it on me to take a video, but download the multitouch visualizer and try moving around, the dot lags behind your finger significantly, anyone know if this is a hardware issue or just not tuned right?
Dorick said:
Hey guys, I tested the evo 4g multitouch input with the multitouch visualizer yesterday and found that though it does have much better tracking than the nexus one(no crossing and stuff) it does seem to have significant input lag, I do not have it on me to take a video, but download the multitouch visualizer and try moving around, the dot lags behind your finger significantly, anyone know if this is a hardware issue or just not tuned right?
Click to expand...
Click to collapse
Yea I'm noticing some lag too :/ bummer
I seriously hope this is a software/work in progress issue. I'd be severely disappointed to see HTC make such a mistake that they've avoided with past phones like the Incredible. I mean, why would they make the Evo's screen worse than the Incredible's?
This might be a deal killer for me. It is one of the reasons I've avoided Android up until now.
If there is not a software patch then I am sure FROYO will remove the problems.
I have a sneaking feeling that the camera, video and lag will be addressed at the update of Froyo 2.2
BadBoyNDSU said:
This might be a deal killer for me. It is one of the reasons I've avoided Android up until now.
Click to expand...
Click to collapse
The Droid has a more responsive screen and no axis-crossing issues like the Nexus One.
Personally I wouldn't have noticed the Evo's input lag if I hadn't downloaded the Multitouch Visualization Test from the Market.
wow, thats retarded, it may be a deal breaker for me.
Possible to turn off Sense UI and test again?
I would love to see a comparison side by side with the Evo & the Incredible. All of the comparison I've seen are either the Evo vs. N1 or Incredible vs. N1. None of which the two are side by side. From the comparison I've seen with Evo vs. N1, the Evo is still far superior to the N1 as far as multitouch goes. In that case I'm not to worried.
deal breaker? no lag in the UI, but lag on one program that tests multi-touch and it's a deal breaker?
at least test out actual multitouch functions, if there is lag there than maybe a deal breaker, otherwise I fail to see how this is definitely an evo problem; maybe it is a problem of the program on the phone. I'll take real use over test program for my deal breaker.
tatnai said:
deal breaker? no lag in the UI, but lag on one program that tests multi-touch and it's a deal breaker?
at least test out actual multitouch functions, if there is lag there than maybe a deal breaker, otherwise I fail to see how this is definitely an evo problem; maybe it is a problem of the program on the phone. I'll take real use over test program for my deal breaker.
Click to expand...
Click to collapse
As much as I'd like to believe otherwise, the same program running on my Droid is a bit more responsive.
But this is just a perceived problem running this test program, correct? I have read no negative issues regarding screen response in any of the reviews...
chazglenn3 said:
But this is just a perceived problem running this test program, correct? I have read no negative issues regarding screen response in any of the reviews...
Click to expand...
Click to collapse
Whether or not people notice the lag while doing everyday tasks, that's a different problem. I already stated that I DON'T notice the lag doing other stuff.
But the multitouch visualization test running on both Droid and Evo shows that the Evo does indeed have some bit of input lag.
i wont call it a deal breaker but its definitely there.
tatnai said:
deal breaker? no lag in the UI, but lag on one program that tests multi-touch and it's a deal breaker?
at least test out actual multitouch functions, if there is lag there than maybe a deal breaker, otherwise I fail to see how this is definitely an evo problem; maybe it is a problem of the program on the phone. I'll take real use over test program for my deal breaker.
Click to expand...
Click to collapse
+1
Is the Multi-Touch test app using OpenGL to render those dots? It may just be that the EVO is slower at rendering using the specific graphics API and nothing to do with the touch screen.
Overall it would appear that the current EVO is slightly slower than the Incredible (at least the benchmarks that I have seen on the web). I have also been reading that the firmware on the EVO is likely not the release version of software so for all we know these Google I/O and Advocate devices have been compiled in DEBUG / TEST code.
i tried this too, and it does appear to be true.
if you run the visualizer and try single-touch and double-touch response, and then go into google maps or a webpage on the browser, then try the same test, the response seems about the same. that's why i tend to believe the visualizer. i'll bet htc simply needs to optimize their touch input handling code to eliminate the lag
i also tried this killing every other running application besides the multi-touch visualizer and got the same result. it's the same whether running the htc sense launcher or the nexus one launcher. definitely not a deal breaker though
I have E-mail HTC about this and also give them my S/N of my EVO lets see what will they respond, I will let you guys know.
Thanks
fazzy said:
I have E-mail HTC about this and also give them my S/N of my EVO lets see what will they respond, I will let you guys know.
Thanks
Click to expand...
Click to collapse
Should be an interesting response, hopefully you don't get some auto-generated response based on keywords.
I agree with other posters, unless I see issues with actual use, I don't see this very specific application as anything near a deal-breaker. All other reports confirm that the UI experience is amazingly fast.
I'm not a developer, but my intuition says the observed lag compared to other devices has root in code that isn't optimized for this specific application.
Even if Froyo doesn't clear this up, it won't make a difference to me.
Its definitely not a deal breaker, but can be annoying for things like gaming and stuff.. on normal usage, you probably won't notice it.
It's most likely an input setting they put in for the phone for gesture recognition. I'm willing to bet is enough people complain about it they'll tweak it.
the cam in the 1.6 version is really horrible and very slow. ist that better in the 2.1 version? Thanx
stalker1981 said:
the cam in the 1.6 version is really horrible and very slow. ist that better in the 2.1 version? Thanx
Click to expand...
Click to collapse
I am running the 1.6 and i would say the camera is very good better than any camera i ever had on any HTC device. But the camera is a lot better in 2.1 i have read
lufc said:
I am running the 1.6 and i would say the camera is very good better than any camera i ever had on any HTC device. But the camera is a lot better in 2.1 i have read
Click to expand...
Click to collapse
well I have HD2 also, and the cam is pretty good. but on the 1.6 of my Streak is the shutter lag really terrible. much slower as of the HD2...and the flash is very poor... If the quality doesnt get better in 2.1 i will have to send the Streak back
Does anyone know if the dell streak will allow you to keep the flash on while recording video? Any difference in this from 1.6 vs 2.1 or if it makes a difference?
Also, I know it's off topic but can you watch youtube videos in HQ in the youtube app?
The camera has been improved, but not by much. At least it's usable now though.
The 720p filming is pretty damn good though
and yes, you can watch HQ videos in the youtube app.
Meltus said:
The camera has been improved, but not by much. At least it's usable now though.
The 720p filming is pretty damn good though
and yes, you can watch HQ videos in the youtube app.
Click to expand...
Click to collapse
Thanks Meltus, How about having the flash on while recording video. I know that is mainly a froyo thing but some devices with 2.1 have implimented it so though it may be possible on a new device. One can dream..
Also, was the 720p only added with the 2.1 update?
I have also heard horror stories about the keyboard on 2.1. That is probably the only thing keeping me from forcing this update. How do you like the keyboard with the 2.1 update?
The camera is slightly better, but the app is now hideous. It really is ugly and far less usable. However we should remember the leaked ROM is beta at best, its not an official release.
Raspster said:
Thanks Meltus, How about having the flash on while recording video. I know that is mainly a froyo thing but some devices with 2.1 have implimented it so though it may be possible on a new device. One can dream..
Also, was the 720p only added with the 2.1 update?
I have also heard horror stories about the keyboard on 2.1. That is probably the only thing keeping me from forcing this update. How do you like the keyboard with the 2.1 update?
Click to expand...
Click to collapse
No, there's no flash (will probably come with 2.2) and they've also got rid of the zoom-before-you-film, which is annoying.
Yes, 720p was only added with the 2.1 beta leak.
They keyboard isn't as bad as everyone says, whilst it is a HUGE step backwards it is still usable (i use swype anyway, so it doesn't bother me).
But the camera layout is now dreadful, because when you go into the settings menu and select something, you cannot then go back to change something else, you have to close the settings menu then re-open it, which is VERY annoying.
Softkeyboard or dock, the delay is killing me.
Its a bug i tried stock and prime v1.4 are the same, still cant type in browser, maxthon...
Opera mobile is normal.
The Samsung 10.1 has the same problem (actually worse IMO). Seems to be a Honeycomb issue.
MisterEdF said:
The Samsung 10.1 has the same problem (actually worse IMO). Seems to be a Honeycomb issue.
Click to expand...
Click to collapse
Aw, so they need to do a lot to make everything go smoothly.
Now too many unsupported issue.
MisterEdF said:
The Samsung 10.1 has the same problem (actually worse IMO). Seems to be a Honeycomb issue.
Click to expand...
Click to collapse
Seems to be a stock browser issue, actually. As others have reported, Opera works fine because it was built from a completely different browser engine.
I found that the lag in the stock browser is minimal if you disable plugins.
Typing lag and potrait frame rate drop; are the biggest reasons why iPad is winning tablet race. U might not think those 2 things are huge issue but have someone who plays with the iPad and give android tab a try will be turned off by this. I know because my brother put down my xformer noticing so much lag and went back to his fluid iPad. Sucks I hope it gets resolved soon
the keyboard lag while typing in the browser is from the browser autocomplete / autosearch. This doesn't make it OK I know. But if you can turn it off (or a rom can turn it off) it should help.
What people are saying about portrait fps I don't know. Scrolling and zooming in the browser and gallery for example go butter smooth whatever my orientation is.
dipje said:
the keyboard lag while typing in the browser is from the browser autocomplete / autosearch. This doesn't make it OK I know. But if you can turn it off (or a rom can turn it off) it should help.
What people are saying about portrait fps I don't know. Scrolling and zooming in the browser and gallery for example go butter smooth whatever my orientation is.
Click to expand...
Click to collapse
not to make fun or anything, but u might not have the eyes to notice a frame drop in portate mode, but its def no where near as smooth as landscape
Since this is (was?) The dev forum I was only giving facts, to help find the source. It's not apparent in every app and or every device. Bb
cowballz69 said:
Typing lag and potrait frame rate drop; are the biggest reasons why iPad is winning tablet race.
Click to expand...
Click to collapse
Well, that and Apple has been in the market almost 2 years. And they advertise at least once on every prime time show I watch.
Anyway, really happy with my Transformer. I'm impressed with how well the apps. work. EVERYTHING WORKS. It may even be better than my Vibrant. Skype and Netflix are my only two issues? Where are you?
I have another tablet (Elocity A7). Same CPU (Froyo), no browser lag. Incredibly snappy. Anyway, the transformer is a huge setup in quality. 3.1 is awesome so far (after a little getting used to).
Generally the browser freakin' awesome. Everything works (except the click lag issue). Something is definitely up with that. I also miss the click highlighting from Froyo.
O wow I've spent a while trying to sort out this issue, glad its not only me!
The lag is pathetic, this is the only thing left letting me down now. I cant believe this is happening with this great tablet!! Google need to sort this out with up-most priority!!
NOW!
Maybe some1 should try to downgrade it to 2.3.3 to reduce the bug in 3.1 )
dragonthl said:
Maybe some1 should try to downgrade it to 2.3.3 to reduce the bug in 3.1 )
Click to expand...
Click to collapse
Does this happen on the Xoom? If not then maybe someone could port over the apk?