Database Info

S100 > S200 Worth the upgrade ?

Well this is what I have been deciding for sometime now.
And here is my verdict:
http://forum.xda-developers.com/viewtopic.php?t=48608

I think it's worth it. Orange now have upgrade stock and I've ordered my M600 today. My M500 will probably appear on eBay in the next few days.
Someone else in our office has just got an M600 having upgraded from the M500 and he really likes it - and so do I. Since I'm due for a free upgrade I thought - what the heck...go for it. 8)

I never had S100 but I still have my old 9090. I think you should go for it. The new WM5 is faster, cleaner and more stable (no more soft reset). And not being worried about losing everything when the battery dies. As for the processor, it is right, the S200 is a bit slower, you’ll feel it while playing movies with tcpmp. But using an overclocking app. Will fix it.

if you encode your video correctly, eg in 320x240 res, video playback is no problem whatsoever without overclocking

Indeed!
The gadget it nice, small, stylish black (at least are the XDA Neos), definitely better than the Wizard, and has no problems playing movies without overclocking if encoded with PocketDVDStudio.
It is THE phone!
P.S. The Start and OK/Close buttons are life-savers 8)

I've now upgraded and it was definitely worth it. 8)

When playing movies shot with my Canon Ixus @ 320x240 the Charmer stutters and the S100 does not.
Why would I want to 'upgrade' to something that I need to 'overclock' to get to the same speed that I have already ?
I think I will wait till the next version !
Hopefully they will have sorted it by then.

I would just upgrade again when the next model is out :lol:

gregory_marsh said:
Why would I want to 'upgrade' to something that I need to 'overclock' to get to the same speed that I have already ?
Click to expand...
Click to collapse
I think it is something like this... Let's say I have a Pentiun III (256MB) with Windows 98SE(WM2003SE Device) and I upgrade it to WinXP (WM2005 Device) .... I believe I WILL have to overclock to have same performance speed when let's say opening a document, or starting a game.
I don't know but i believe it is WM5 that is slowing the device down. I guess that's why even if were in 2006 there are still computers running Windows 98. So i guess you are right. If you don't need (yet)the advantages that WM5 brings then you could wait for the next generation Processors so that it will run "at par" as the S200.
I came from a h6340 (OMAP 200Mhz WM2003) to the Universal (Intel 520Mhz WM5) and no matter how you look at it, the Universal is so much faster than the HP h6340.
Oh, BTW... out from the box, the universal was "kinda" slow and I would classify it as a little non-responsive when opening a lot of programs at same time. Now though after a few ROM updates, everything is running quite quick.

First of all, no need to overclock. The processors arent from the same vendor, so dont look too much at the "Mhz".
I had a S100, and now got a 200, the 200s processor is definetely Not worse than the S100.
In my opinion, its worth it! The one thing I miss on my S200, is Project VCABT, I really hope these talented guys will fix it asap

montana said:
First of all, no need to overclock. The processors arent from the same vendor, so dont look too much at the "Mhz".
I had a S100, and now got a 200, the 200s processor is definetely Not worse than the S100.
In my opinion, its worth it! The one thing I miss on my S200, is Project VCABT, I really hope these talented guys will fix it asap
Click to expand...
Click to collapse
Some items might be a matter of taste, but some are critical.
- The machine IS slower than an JAM
- It hangs, at least so often as the JAM, or more frequently should I say.
- I had to hard reset the first day of usage: A clock alarm remained somehow turned on and sounding every few minutes. No way to disconnect the thing..... even after a Soft Reset
- Battery life is shorter.... (It may be my unit, but it's way shorter than my JAM one year old one....)
- BT worries remain the same as in older models (JAM, etc)
- Lots of Apps simply don't load or don't work
- It's a more radical change than XP was, and less documented and user-conscious than it should.
- Phone caller ID is worse. Pictures are unreadable on screen. No options.
- Phone directional keys don't work as expected.
- ¡Notes on contacts are limited in size!
- flimsy pen
Really, very disappointed.... :evil:
On the plus side: WIFI, look, screen, more ergonomics for one hand use... not enough

montana said:
First of all, no need to overclock. The processors arent from the same vendor, so dont look too much at the "Mhz".
I had a S100, and now got a 200, the 200s processor is definetely Not worse than the S100.
In my opinion, its worth it! The one thing I miss on my S200, is Project VCABT, I really hope these talented guys will fix it asap
Click to expand...
Click to collapse
Some items might be a matter of taste, but some are critical.
- The machine IS slower than an JAM
- It hangs, at least so often as the JAM, or more frequently should I say.
- I had to hard reset the first day of usage: A clock alarm remained somehow turned on and sounding every few minutes. No way to disconnect the thing..... even after a Soft Reset
- Battery life is shorter.... (It may be my unit, but it's way shorter than my JAM one year old one....)
- BT worries remain the same as in older models (JAM, etc)
- Lots of Apps simply don't load or don't work
- It's a more radical change than XP was, and less documented and user-conscious than it should.
- Phone caller ID is worse. Pictures are unreadable on screen. No options.
- Phone directional keys don't work as expected.
- ¡Notes on contacts are limited in size!
- flimsy pen
Really, very disappointed.... :evil:
On the plus side: WIFI, look, screen, more ergonomics for one hand use... not enough

Looking Glass said:
Some items might be a matter of taste, but some are critical.
- The machine IS slower than an JAM
- It hangs, at least so often as the JAM, or more frequently should I say.
- I had to hard reset the first day of usage: A clock alarm remained somehow turned on and sounding every few minutes. No way to disconnect the thing..... even after a Soft Reset
- Battery life is shorter.... (It may be my unit, but it's way shorter than my JAM one year old one....)
- BT worries remain the same as in older models (JAM, etc)
- Lots of Apps simply don't load or don't work
.....
- flimsy pen
Really, very disappointed.... :evil:
On the plus side: WIFI, look, screen, more ergonomics for one hand use... not enough
Click to expand...
Click to collapse
I think you might need to return your unit and get a replacement. Something must be wrong with your unit, or might because of some programs you installed on it?
I had a XDA Neo (same as S200) with JAMin WWE ROM for more than 2 month. The XDA Neo runs very fast and smooth. I never got any problem with it. I normally run multiple programs (2-5) at the same time. For example, media player to listen to mp3s and watch ebooks, and also have the dictionary (Lexisgoo 2.0) running. I never had complaints about the speed. The OMAP CPU is defferent than Xscale, you can not compare them by MHz.
I did not reset the unit in more than one week. The unit never (or at least rarely) hangs. Extremely stable. So, I guess you must installed some program not very compatible with your unit. I have installed more than 20 programs on it, but of course, I tested more than probably 40 programs in my first month after I got this unit, and deleted all the other programs which I believed it made the unit unstable.
I am also pretty satisfied with the battery life. It can last about one week (or at least 4-5 days) for regular use, if I do not use it for long time (more than 30-60 minutes talk) chat on the phone.
The BT is very stable. I use it to connect to my car (I have blue tooth system in my Prius), and it worked beautifully. But to save the battery, I normally turn the BT off when I get off the car.
Sometimes, I guess, you really need to test all the programs you installed. A lot of programs may not work right for WM5, and I also found that some programs it actually may work for WM5 (according to online info or reviews), but it did cause problems on my unit, and made the unit not very stable. You have to spend sometime to figure out. After you done this, you can always use the same programs on it, just keep updating when new version coming out. That is what I did for all my PDA phones.
Hope it helps.
By the way, I am using the overlocking now (252 MHz), and the unit runs even more faster and stable.

Hi!
I agree that no comparison is good based on Mhz, I know about it, but things are slower. Example: after a soft reset, (Several times a day) just accesing a contact whose name begins with "Z" in a 3000+ contact list, takes .... almost 20 seconds!
Loading TomTom 5? some 30 seconds before getting back the control of the thing. Never mind of using the TT5 if you receive an incoming call while tt5 loads..... it will be gone! An I have more than 39 Mb free memory!
Screens redraws that you can "see" almost by the pixel, etc. And I have just 6 apps loaded, tt5, Check Point, Pocket Earth, and a couple of games, none of then running altogether, but for the tt5-check point combo.
I know I can not return my unit for servicing just based on those problems.
:evil: :evil: :evil:
Or could I?

Optimal Video Settings for High Quality Playback Using Core Player?

I have Core Player and love it's steaming capabilities. Doesn't skip and has plenty of feature to customize. The problem I'm running into is playing videos from my SD card. I have two TV show episodes loaded onto my microSD, 640x480. For some reason, Core Player skips a frame or two, sometimes, and freezes/lags for a solid 5-7 seconds other times.
I'm wondering if there are any fixes for this? What settings work best for the Core Player for the smoothest possible feedback?

Unfortunately...
This is not the answer that you want to hear (and I hope someone can prove me wrong) but you will probably will have to reencode those videos to a more CorePlayer friendly format if you want to use CorePlayer on your Raphael to play those files.
CorePlayer doesn't play nicely with H264 files yet on our Qualcomm chips. You can reencode to something like divx/xvid or wait until CorePlayer 2.0 to release sometime in 2009. They claim better hardware support will come with that version. Or you can reencode for WMP. Yeah, I know, kind of a bummer. =/
More info can be found on xda and fuzemobility. I think there is an xda thread started by k9tim regarding this issue if you want to read up on it.
One thing that helped for non H264 files was to increase the buffer size tenfold and decrease video quality to Medium or Low for better framerates. Didn't help me for H264 files but it did help me with some mpegs. I hope someone can prove me wrong.
Posted from my Fuze

I watch movies and tv shows in xvid and divx with 1.25, default settings, high quality, with absolutey no slow downs at all. What exactly are you trying to play?

dogyo01 said:
This is not the answer that you want to hear (and I hope someone can prove me wrong) but you will probably will have to reencode those videos to a more CorePlayer friendly format if you want to use CorePlayer on your Raphael to play those files.
CorePlayer doesn't play nicely with H264 files yet on our Qualcomm chips. You can reencode to something like divx/xvid or wait until CorePlayer 2.0 to release sometime in 2009. They claim better hardware support will come with that version. Or you can reencode for WMP. Yeah, I know, kind of a bummer. =/
More info can be found on xda and fuzemobility. I think there is an xda thread started by k9tim regarding this issue if you want to read up on it.
One thing that helped for non H264 files was to increase the buffer size tenfold and decrease video quality to Medium or Low for better framerates. Didn't help me for H264 files but it did help me with some mpegs. I hope someone can prove me wrong.
Posted from my Fuze
Click to expand...
Click to collapse
Well, you're right - It's certainly not good news. But the bold'd part made it that much better, so it evens out
As far as the info goes, I really appreciate it. It's really no problem for me to leave my computer on overnight with a whole queue of files to re-encode. It'd suck if I was trying to get other things done too, but a fan on high and a few solid hours overnight should (hopefully) take care of these issues. Thanks again.

joeh4x said:
I watch movies and tv shows in xvid and divx with 1.25, default settings, high quality, with absolutey no slow downs at all. What exactly are you trying to play?
Click to expand...
Click to collapse
You, or anyone else who reads this and has zero issues with playback, wouldn't happen to have drivers from this post installed, would you?
http://forum.xda-developers.com/showpost.php?p=2892184&postcount=357
I'm wondering if that's the issue - different drivers on different phones. I have a stock ROM Alltel HTC Touch Pro, with no real desire to upgrade/flash/change the PRL. I ***LOVE*** it the way it is and probably won't be getting a different phone for 3-4 years. 99.8% perfect in my book (with potential factored in, too)

I have a stock Fuze and can get good playback.
Again it all depends on the source files your trying to play. Some of my trilinear and high quality audio encoded files chop / lag every 60th frame or so but at high quality its worth it. Medium quality it does not slow down too much. Most play smoothly till high action in which case they will slow a little.
Increasing the buffer and playing with the method of drawing can increase your quality. If I was not half asleep and my phone in the other room (wife asleep) I would check my settings. If I remember I will post them in the morning. Most of them have not been changed though.

sovrce said:
You, or anyone else who reads this and has zero issues with playback, wouldn't happen to have drivers from this post installed, would you?
http://forum.xda-developers.com/showpost.php?p=2892184&postcount=357
I'm wondering if that's the issue - different drivers on different phones. I have a stock ROM Alltel HTC Touch Pro, with no real desire to upgrade/flash/change the PRL. I ***LOVE*** it the way it is and probably won't be getting a different phone for 3-4 years. 99.8% perfect in my book (with potential factored in, too)
Click to expand...
Click to collapse
I have those drivers installed AND playback issues. But you should install them anyway.
I'm working out some methods of encoding at the moment and will get back to you. I tried to fight the transcoding, but am starting to give in. The device just doesn't have a lot of headroom as far as playing videos, with currently available players.

Any other thoughts on this or are we all just waiting on the next Core Player update?

Did installing the drivers help you at all?

very poor Internal flash memory performance on new HTC devices

it is very surprising that file transfer performance hasnt improved a bit in the last years. i mean it takes my xperia the same time to install a cab or to launch the same app from my 6-year-old Magican
is there something that is preventing HTC from using these crazy SLC-based 100+MB/sec flash chips found in new SSD drives. really appriciate any insite on this

fatso485 said:
it is very surprising that file transfer performance hasnt improved a bit in the last years. i mean it takes my xperia the same time to install a cab or to launch an app from my 6-year-old Magican
is there something that is preventing HTC from using these crazy SLC-based 100+MB/sec flash chips found in new SSD drives. really appriciate any insite on this
Click to expand...
Click to collapse
Those chips aren't really that fast, they are just being run massively parallel in raid like arrays. Even still though, a setup as fast as what they use in compact flash cards would be nice.

- there are some major improvments in flash performance just take any normal flash drive (no RAID-like voodoo going on here) these days and compare it to the ones you used to have 3-4 years ago. the difference is MASSIVE even on low 1GB flash drives.
-what's wrong with running parallel flash chips in a raid-like fashion on a mobile device. it seems like one way to gain massive performance increases only

fatso485 said:
it is very surprising that file transfer performance hasnt improved a bit in the last years. i mean it takes my xperia the same time to install a cab or to launch the same app from my 6-year-old Magican
is there something that is preventing HTC from using these crazy SLC-based 100+MB/sec flash chips found in new SSD drives. really appriciate any insite on this
Click to expand...
Click to collapse
I really don't think it is the chips, it is the CRAPPY Qualcomm processors HTC uses for our expensive phones.

With the size of the chips, the price, the controller, etc... would get sort of expensive. For example, an Intel SSD looks like this. http://blog.wired.com/photos/uncategorized/2008/12/02/inside_an_ssd.jpg and costs a fortune. Their controller is the only one sofar that doesn't suck horribly at small file writes.
Look at this little glimmer of hope though
http://www.pretec.com/epages/Store....re.Pretec/Products/"news-March 03, 2009.no.2"
Too bad the a phone would probably make horrible use of it. My class 6 card might as well be a class 1 for how well my phone makes use of it.

oic0 said:
Look at this little glimmer of hope though
http://www.pretec.com/epages/Store....re.Pretec/Products/"news-March 03, 2009.no.2"
Too bad the a phone would probably make horrible use of it. My class 6 card might as well be a class 1 for how well my phone makes use of it.
Click to expand...
Click to collapse
thats exatly my point. why are $800+ 2009 devices perform identically (internal flash memory) to 2003 devices. people seem to only care about obvious things like CPU speed when hey talk about performance.

[Q] Couple noob questions

I'm not necessarily a noob to android. I've flashed a few phones, dabbled with rooting and custom roms, but nothing too serious.
My first question about these Tegra 2 processors is fairly simple. I want to know if overclocking them makes them more media capable? I have a Droid Charge and had a Galaxy S before it, and both phones were perfectly capable of playing a 720p mkv with nary a stutter. It boggles my mind that I have to convert every video file before I drop it onto the Xoom. It's not a huge hassle but it's rather interesting a single core hummingbird can handle it with ease and a dual core clocked at the same speed has so much trouble.
Second question is this. Is there any development going on for the Xoom Family Edition? I haven't noticed much other than news posted regarding this version on this forum, so I'm not sure. It's obviously not the hit they were hoping it would be, there's a whole 3-4 cases made to fit it, and virtually no accessories for it like there is for the Xoom (docks and whatnot). If overclocking helps without nuking battery life, I'd be interested. I wouldn't know where to start developing, I'm definitely not a skilled programmer, but I would be happy to help any way I could (minus a potential brick, I can't afford a new tab)!

Bump. Any opinions?

Regarding the overclocking the tegra 2 , yes it will be more powerful therefore increasing media playback performance. Although battery usually drops faster you can install set CPU to set profiles for when the screen is off etc...
As for the Xoom I myself am not very knowledgeable about that device so I cannot effectivily answer your question.
Hope this helps!
Sent from my PG86100 using XDA App

Remember that the Xoom screen is so much bigger, so takes a lot more juice to playback at same resolution, but overclocked cpu does make a difference for sure. Also, if on ICS, go into developers settings menu and turn off animation or set to .5. Makes a big difference.
The Xoom FE (like the Xoom2 and the Xyboard) don't have unlockable bootloaders and noone yet has found the exploit to gain root access. Hence no development...so far. If you find the way, you will be popular among the owners of those devices.

If you overclock the Xoom it will of course consume the battery faster, as with anything that requires voltage tweaking. The main thing to remember is research the governors that will adjust what clock you're running at and when you're running it. Interactive usually gives the best performance speedwise while Ondemand gives you a mix of performance and battery life.
Your media playback issue could possibly be due to several factors. Processor, RAM, SD read rate, and the media player are the main culprits that come to mind.
If it is the processor then overclocking will most likely help. There is a minor off chance that the Tegra2 does not contain certain instruction sets included on the other devices processor that allow it to decode the Matroskiva, mkv, format as readily.
If it is the RAM, your best bet is to get a task killer and use it to kill everything before you try to play the video. You can also go into settings and go to individual apps to force kill them which tends to work better than most task killers.
If it is the SD card rate, research fairly deeply into the subject because I personally have heard many mixed reviews in regards to the Xoom and higher "class" or access rate SD cards. Eventually I plan on getting a collection of them to run some testing myself for a unified chart, but until then your best bet would be to ask experienced Xoom users, and browse these forums.
If it is the app then try looking around to see what other players are out there. Some people use different decoding codecs than others, and some tend to work better on mobile devices with limited instruction sets.
Mind you, if i remember correctly, the other two devices also display at a lower resolution, which would take less power, and the app used to play the file might not support the larger resolutions as well.
And if you have not already toyed around with your Xoom and hacking it, just as a warning, like all other devices it can be easy to brick. Make sure you have read at least 2 different tutorials on how to do it beforehand as some are much more clearly stated than others.
Hope this helps you some

I hadn't thought about the memory card being the issue. I'm not sure how fast the internal memory card is, but my external is only a class 2, so that could have an effect on load times and everything. I know the RAM isn't really a problem, I don't do much on my tablet, and I've tried killing apps and fresh boots and nothing seems to work. It only seems to use about 450mb out of 1024mb for apps, and out of that only 124 was in use last time I checked.
I have tried many other media players though, including Dice Player which seems to be unanimously the best, and nothing I've tried is able to play an mkv on the Xoom. I typically try downloaded tv shows before movies, which include 500mb Big Bang Theory mkv files and 1gb Top Gear mkv files at 720p. Neither play at all in the stock player and play very badly in Dice or other players.
I can't wait until ICS on the Xoom FE, I'm betting it fixes a lot of my issues. Such as the browser constantly force closing and my wifi slowing down the longer the tablet is on.

[Q] Touchscreen Input Lag aka Touch Lag, Kernel Hack Possible?

Despite all apps/menus being fast, the Sensation 4G still feels sluggish due to a significant touchscreen input lag, also known as "touch lag" or "touchscreen latency". I see the same amount of lag with clean installs of stock GB 2.3.4 and ICS ARHD 6.6.1 /w overclock to 1.6Ghz.
This video/article (of a Galaxy SII) illustrates the problem.
Here is another video showing the effect that I'm talking about.
I've tried increasing/decreasing the "windowsmgr.max_events_per_sec" in build.props but that only affect smoothness, not overall lag or latency in following my finger. I've been using the free "Touch Test" app to compare different phones. The iPhone 4 and Galaxy S Blaze have MUCH less lag, and hence feel more responsive overall. The Blaze is an Android phone, so all of Android is not to blame (as the first video suggests).
Is there a hidden setting somewhere to help fix this or is the touch sensor in the Sensation just too slow? A fix for ARHD ICS would be ideal since I plan on running that.
UPDATE
I am a programmer but new to Android and mobile platforms. Assuming the touch screen is implemented as a polling input device, is a kernel hack that increases the polling rate possible? I am looking at the Sensation ICS kernel driver code, but I have no idea what I'm doing... Not even sure which driver's are applicable to the touchscreen yet...
Nvm, we need to decrease the touchscreen latency, polling rate won't affect that...
UPDATE
The following seem to have no effect on the touch lag:
Upgrading to ICS with ARHD 6.6.1 or Virtuos 4.0.1
Using Sebastian or faux123 kernels for ARHD
Overclocking up to 1.7Ghz
Using SuperCharger /w or w/o Nitro Lag Nullifier
Increasing/decreasing windowsmgr.max_events_per_sec in build.props

I have never experienced any lag at all with my phone running ARHD...
I cant recall seeing any threads regarding this either ??? Maybe its a hardware fault ?? If it is a really noticeable severe lag

azzledazzle said:
I cant recall seeing any threads regarding this either ???
Click to expand...
Click to collapse
This (old) thread mentions the Sensation. There are a couple threads around in other phone forums (SGS2 and DROIDX)
azzledazzle said:
Maybe its a hardware fault ?? If it is a really noticeable severe lag
Click to expand...
Click to collapse
It is not "severe". I have 2 Sensations and both behave similarly. I'm new to Android so maybe its just something I'm not used to, but seeing as how the Galaxy Blaze 4G hardly has any, the Sensation seems slow by comparison.
Really it seems like there should be a (hidden) setting somewhere because the CPU isn't struggling in the slightest. If the touch digitizer is just slow though, then there is no hope...

Well certain kernels and tweak apps have lots of hidden features. GPU rendering and such.... I dont really understand what they all are because i dont have any issues, so i dont bother to learn about things that dont affect me lol
maybe you could try a custom kernel and install leedroid tweaks. ??

azzledazzle said:
maybe you could try a custom kernel and install leedroid tweaks. ??
Click to expand...
Click to collapse
Yeah, I'm in the process of just trying everything. I was hoping maybe someone knew something about it so that I could avoid the shotgun approach
Ideally the fix would be a setting at the firmware level. The lag is even apparent in 4EXT and CWM Touch for example. But I would gladly settle for a kernel level hack so I have fast touch when actually using my phone...

demonsavatar said:
Despite all apps/menus being fast, the Sensation 4G still feels sluggish due to a significant touchscreen input lag, also known as "touch lag" or "touchscreen latency". I see the same amount of lag with clean installs of stock GB 2.3.4 and ICS ARHD 6.6.1 /w overclock to 1.6Ghz.
This video/article (of a Galaxy SII) illustrates the problem.
I've tried increasing/decreasing the "windowsmgr.max_events_per_sec" in build.props but that only affect smoothness, not overall lag or latency in following my finger. I've been using the free "Touch Test" app to compare different phones. The iPhone 4 and Galaxy S Blaze have MUCH less lag, and hence feel more responsive overall.
Is there a hidden setting somewhere to help fix this or is the touch sensor in the Sensation just too slow? A fix for ARHD ICS would be ideal since I plan on running that.
Click to expand...
Click to collapse
i have the same lag i had the lag from gb rom and now on ics arhd i really hate it when you touch somewhere and it shows the touch later rather than picking it up straight away

Recommend v6 supercharger and nitro lag nullifier. Makes my 1.5GHz sensation feel like 1.8GHz!
http://forum.xda-developers.com/showthread.php?t=991276
sent from HTC Pyramid using Tapatalk

The easiest way to see the lag if you have an ICS rom installed is enable Settings->Developer Options->Show touches. Move your finger around on the screen and see how far back the dot trails your finger.
Shery4life said:
i have the same lag
Click to expand...
Click to collapse
Good to know I'm not the only one. I think more people may have it, but they are used to it?!? If this could be fixed it would make the phone feel much faster. I actually played with a single-core lumia 710 windows phone and the touchscreen responds quite fast. Same thing with Iphone 4. This is part of how Microsoft/Nokia/Apple make their slow hardware feel fast.
stringer7 said:
Recommend v6 supercharger and nitro lag nullifier.
Click to expand...
Click to collapse
Tried these. Supercharger is also an option when installing ARHD, which I did choose. Nitro Lag Nullifier is a bunch of build.prop settings which didn't make a difference in the touch lag.

here watch this video
http://research.microsoft.com/apps/video/default.aspx?id=160670
and tell me in which latency htrc senastion falls
and also with you experience can you also tell which one iphhone 4 falls under
here what i think about all the andriod that they have latenc of 100 millisecond
and for iphone, ipad, and ipod have latency of 50 millisecond
and since i have used alot of andriod devices i think that some andriod devices have latency of 200 millisecond or more
but for iphone i think that there latency are 50millisecond

Shery4life said:
here watch this video
http://research.microsoft.com/apps/video/default.aspx?id=160670
and tell me in which latency htrc senastion falls
and also with you experience can you also tell which one iphhone 4 falls under
here what i think about all the andriod that they have latenc of 100 millisecond
and for iphone, ipad, and ipod have latency of 50 millisecond
Click to expand...
Click to collapse
Yeah I saw that video. Not sure how fast they are moving their finger, but if we are talking in relative terms, the Sensation is definitely in the 100ms range, the Windows phone is somewhere between 100ms and 50ms. The iPhone and the Galaxy Blaze are around 50ms. Again, these are relative comparisons, the numbers dont mean much unless we know how fast he is moving his finger in the video.
The limit is clearly not the entire Android platform as the Galaxy S Blaze responds quickly.
I am looking through the kernel driver code to see if anything makes sense. I am a programmer but I've never touched Android or mobile platforms before, so I have no idea what I'm doing...
Any DEVs with kernel and driver experience care to join the discussion? I'm guessing the touch screen is implemented as a polling input device. If we can increase the polling rate, it may go faster. Of course, the hardware may impose some limit on that...
UPDATE: I just realized polling rate has nothing to do with it. It is just input latency. Harder problem to fix...might just be hardware limitation.

demonsavatar said:
Yeah I saw that video. Not sure how fast they are moving their finger, but if we are talking in relative terms, the Sensation is definitely in the 100ms range, the Windows phone is somewhere between 100ms and 50ms. The iPhone and the Galaxy Blaze are around 50ms. Again, these are relative comparisons, the numbers dont mean much unless we know how fast he is moving his finger in the video.
The limit is clearly not the entire Android platform as the Galaxy S Blaze responds quickly.
I am looking through the kernel driver code to see if anything makes sense. I am a programmer but I've never touched Android or mobile platforms before, so I have no idea what I'm doing...
Any DEVs with kernel and driver experience care to join the discussion? I'm guessing the touch screen is implemented as a polling input device. If we can increase the polling rate, it may go faster. Of course, the hardware may impose some limit on that...
UPDATE: I just realized polling rate has nothing to do with it. It is just input latency. Harder problem to fix...might just be hardware limitation.
Click to expand...
Click to collapse
I live in UK and I don't think we have galaxy blaze in UK but then again I can be wrong
But like I said I have used iPhones iPod and iPad and the experience I had from these devices made me think that the latency is around 50 and my phone like sensation have 100 and I'm not sure if galaxy s2 have 100 or 50 latency but one thing I can say is that s2 is much more responsive than any other android I have used. But compare to iPhone I would say it is a bit laggy and I would put it around 75 and even 75 latency touch experience is still better than 100 I would love it manufacturer stay making new devices with 1 latency. But even if they bring out 10 latency I wouldn't mind but to keep the devices with 100 latency I think is bull**** and as a customer I will love a device with good touch experience.
Sent from my HTC Sensation using xda premium

demonsavatar said:
Yeah I saw that video. Not sure how fast they are moving their finger, but if we are talking in relative terms, the Sensation is definitely in the 100ms range, the Windows phone is somewhere between 100ms and 50ms. The iPhone and the Galaxy Blaze are around 50ms. Again, these are relative comparisons, the numbers dont mean much unless we know how fast he is moving his finger in the video.
The limit is clearly not the entire Android platform as the Galaxy S Blaze responds quickly.
I am looking through the kernel driver code to see if anything makes sense. I am a programmer but I've never touched Android or mobile platforms before, so I have no idea what I'm doing...
Any DEVs with kernel and driver experience care to join the discussion? I'm guessing the touch screen is implemented as a polling input device. If we can increase the polling rate, it may go faster. Of course, the hardware may impose some limit on that...
UPDATE: I just realized polling rate has nothing to do with it. It is just input latency. Harder problem to fix...might just be hardware limitation.
Click to expand...
Click to collapse
Sorry to resurrect an old thread, but there isn't much discussion on the internet going on regarding this issue. I used to own a HTC Desire (Oxygen Rom 2.3) and recently upgraded to a Galaxy S3 (LTE) and the input latency is no different. I have also tested using hardware controllers via bluetooth such as Wiimotes and PS3 gamepads, same results on 2 very different devices.
I was planning on using my device for some emulation (SNES, etc) but the input latency makes platforming games unplayable. I've read that AMOLED screens are supposed to be as responsive (in both pixel reponse and input delay) as plasma screens, so I'm pretty sure that the screen hardware isn't at fault here. From the little information I have scrounged together from the internet, it is the Android OS and the way it is written. All devices, all applications.
When my HDMI adapter for my S3 arrives, I'm going to test using both the touch screen and a hardware gamepad on a screen I know to have negligible input lag.
Some people aren't sensitive to noticing input latency, but its very frustrating for people like me that do. I have a quad core in my pocket with 2GB ram and I'm dealing with 100ms+ input latency in everything I do, despite getting awesome buttery smooth frame rates.
iOS has Android beat in this area, and I'm yet to use one yet, but the Microsoft Surface is said to boast a 1-2ms delay on their touch input.
Knowing that my hardware is more than capable of great response makes me sad. But I have a feeling that rom nor kernel alone can fix this issue.