Database Develop

Touch vs Diamond screen question

I have a Touch currently and I’m thinking of getting the Diamond. One of the many things I didn’t like about the Touch is how hard you have to press the screen. Does the Diamond screen have the same issue? Or is it more like the iPhone screen.
I have the 200mhz version of the Touch and I find it a bit sluggish sometimes. Although the Diamond has a 582mhz I’ve read a couple of reviews that state it’s sluggish at times, have you guys experienced this?
Thank you.

The screen is very responsive to my touch.
However, I have ran the application "Diamond Tweaks".
It allows you to change the sensitivity, and also has an option for TouchFlo3D speed.
Overall I barely notice any sluggishness unless I'm running many programs.
Either search the forum or google it, it's readily available.

intx said:
The screen is very responsive to my touch.
However, I have ran the application "Diamond Tweaks".
It allows you to change the sensitivity, and also has an option for TouchFlo3D speed.
Overall I barely notice any sluggishness unless I'm running many programs.
Either search the forum or google it, it's readily available.
Click to expand...
Click to collapse
Do you know if the Diamond screen is as hard to press as the Touch screen?

I have them both. Diamond is a little more responsive to the touch but nothing earth shattering. Speed is about the same if you're running 6.1 on your Touch.
The resolution is where the upgrade comes in. If you put the Diamond side by side with the Touch, it's like comparing a standard TV with rabbit ears to a High Definition LCD...
Now, if all you're looking for is a fast phone and don't care too much about the screen resolution, go for a Touch 3G as this has been described as one of the fastest and most responsive WM phones ever.

Jamolah said:
Do you know if the Diamond screen is as hard to press as the Touch screen?
Click to expand...
Click to collapse
Have them both too, and too answer your question: NO, you dont have to press at all on the diamond, screen is much better then the touch, hope it helps.

Jamolah said:
Do you know if the Diamond screen is as hard to press as the Touch screen?
Click to expand...
Click to collapse
I actually think the difference is quite noticecable between the two.
On the diamond I can actually press very very lightly using my finger while on the Touch I found myself having to poke at it sometimes with the finger nail - but as compared to the iphone it's definitely not as sensitive as they are two different beasts in that regards.

I feel I should mention I have the US 3G Diamond from sprint, and yes it is extremely responsive, quite amazing actually.

Jamolah said:
I have a Touch currently and I’m thinking of getting the Diamond. One of the many things I didn’t like about the Touch is how hard you have to press the screen. Does the Diamond screen have the same issue? Or is it more like the iPhone screen.
I have the 200mhz version of the Touch and I find it a bit sluggish sometimes. Although the Diamond has a 582mhz I’ve read a couple of reviews that state it’s sluggish at times, have you guys experienced this?
Thank you.
Click to expand...
Click to collapse
I played with the touch(for a month) and own the Diamond for almost 6 month now.
They are on a totally different level. Everything is better on the Diamond, except the batts.
The screen is double in resolution compared to most phones out there, once you go Diamond VGA screen you cant go back.
Screen is very responsive and I must say after some quick tweaks under da hood you are looking at a very responsive screen and device.
You wont regret it for a second if you switch.
Greets.

Sergio PC said:
The screen is double in resolution compared to most phones out there, once you go Diamond VGA screen you cant go back..
Click to expand...
Click to collapse
Not entirely true, I'd gladly turn in VGA for QVGA to speed things up really. And the new HTC Touch phones seem to be way more responsive than the first/older models.
That being said, I went from a HTC Touch (one of the first) to a HTC Diamond. The difference was indeed almost day and night (so to speak).
I've played with some newer Touch models, and it has improved quite a bit (or I just had a 'lucky' model which was very responsive). Still, the Diamond has a really nice Touchscreen.
Also the VGA is/was very nice (especially at the beginning), but now the lack of speed starts to annoy me.
Reason for me to start looking at the Touch 3G and the Asus P552w. Where the Asus is the preferred one at the moment since benchmarks (see here and here) show that little thing rocks.
And I've kinda lost faith in HTC and their Qualcomm drivers. That Asus phone really looks like it could be one of the fastest and smallest wm6.1 devices out there. But I can only tell you for sure once I've given it a testrun myself .
Edit:
To come back to the HTC Touch 3G speed compared to the Asus P552w, it could be nice to compare the following two benchmarks made by the same site:
HTC Touch 3G Benchmark (half way down)
Asus P552w Benchmark

As you can see in my profile my ROM version, so I don't know if I have one of the good HTC touch or not.
The screen on my Touch has weird colors on it and I'm wondering to get it fixed (my warranty runs out on Jan 7, 2009 so in 1 week) or should I do a hardware upgrade to the Diamond.

Why not get it fixed in warranty ánd perhaps get a Diamond? That way you at least have a good Touch you could sell or something.
Unless they give you a Diamond in exchange, but I very much doubt that.

Moving on to the Tilt2/TP2

Well, just my my Tilt 2 2 days ago. Just wanted to thank everyone here for all their help in making my Tilt the best it could be.
So far I love the Tilt 2. At time I do miss the D-pad, but everything else more than makes up for it.
Some of the things I like over the Tilt.
1. The Screen
The Screen is beautiful! Bigger & WVGA make for a better internet experience as well as overall usage. The extra room make it easier to use with your finger.
2. Speed and performance
It overall performance was a nice surprise, better than I expected. Faster and smoother than my original Tilt. GPS lock is much better for me. It has it moments of slowness, but over all much better than I was used to. Start up is also quicker than what I had become used to. I'm still running the stock ROM so maybe it can get better.
3. Size
Yes it a large device, but is thinner and feels smaller and more comfortable in the hand than the Tilt. Did I mention that large WVGA screen is AWESOME!
4. Opera Mobile
Yes I had Opera Mobile on my Tilt, but never could find a version that ran quite as fast and smooth as the one that come stock with the Tilt2.
5. Features
I like some of the added little features.
- Proximity sensor turns off screen when hold to you ear.
- Speaker phone then placed face down. Speaker woeks well too.
- If stylus removed while in call notes is automatically opened.
- Remove stylus and phone wake up (as abviously your about to use it).
- FM radio. It sounds good too.
- TouchFlo 3D is really nice and keep you from having to see WM for the most part.

One of the things that I have been wondering is about the keyboard. Although I like it, sometimes I find it hard to type fast on the Tilt because you have to press the keys so hard to activate them. How is the typing on the TP2? I am sure bigger keys and gaps between keys helps, but I am more interested in the action of the keys compared to the Tilt.

myriad46 said:
One of the things that I have been wondering is about the keyboard. Although I like it, sometimes I find it hard to type fast on the Tilt because you have to press the keys so hard to activate them. How is the typing on the TP2? I am sure bigger keys and gaps between keys helps, but I am more interested in the action of the keys compared to the Tilt.
Click to expand...
Click to collapse
I find the key work very well, better than the Original Tilt in my view. It does take a little while to adjust to the different layout and spacing, so I'm probably a little slower at this point. In a week or two I'm sure I have it down.
Over all I'm glad I skipped the Fuze and waited for the Tilt2.

..I have a question: how is the program responsivesness compare between the two? Is there a signifigant difference in speed when multi-tasking?

I have both devices but have moved the other way. Native android and windows mobile option in the tytn 2 is brilliant. And most things are tried and tested and working on the tytn2. I use Androkidd as an interface over 6.5 for both devices.
It must be said that the keyboard is the best I have used on a mobile device on the TP2 and the screen is very nice too.

Capacitive Button Responsiveness?

Recently, I've been considering getting a Nexus One, however, most of the reviews I read say that the N1's capacitive buttons are a little unresponsive. You must tap the upper half of the button as opposed to the bottom half of the button.
I've also read that some of the cyanogen roms have fixed this problem. Can anyone give me more insight on this issue?

I've never had a problem with mine.
I saw a review saying that they got in the way when typing w/ the onscreen keyboard, but I haven't even had that, and I'd like to think that I have pretty normal-sized fingers.

Some people have problems, others don't i personally haven't. I wouldn't consider it to be something important enough to sway me from a sale though.

Stock Rom had this issue. If you unlock your bootloader, all the kernels (and mods) available now have a fix for this, as well as a few other things.
Im sure when 2.2 update comes out this fix will be passed on to the stock version too (at least as far as im aware it hasnt already!?). So tbh this isnt an issue for you not to get a nexus one...also, there's no point getting a nexus one if ur too scared to unlock the bootloader!!

adam18488 said:
Stock Rom had this issue. If you unlock your bootloader, all the kernels (and mods) available now have a fix for this, as well as a few other things.
Im sure when 2.2 update comes out this fix will be passed on to the stock version too (at least as far as im aware it hasnt already!?). So tbh this isnt an issue for you not to get a nexus one...also, there's no point getting a nexus one if ur too scared to unlock the bootloader!!
Click to expand...
Click to collapse
Definitely! That's one of the biggest reasons why I want an N1. It has a good root and dev community and gets android updates first.
I just thought it'd be annoying to have to use a phone with crappy capacitive buttons, but I'm glad to hear that the problem has been fixed.
The only other thing I'm worried about is the dualtouch but it's most definitely going to get fixed in the next update.
Thanks to everyone for their input. I'll definitely be picking up an N1 soon

I have rooted and custom roms etc and I still hate the capacitive buttons with a passion. They are not nearly enough to topple the overall awesome that is the N1 but man I hate those things.

I only hate those buttons, when Nex is in my car mount!

adam18488 said:
Stock Rom had this issue. If you unlock your bootloader, all the kernels (and mods) available now have a fix for this, as well as a few other things.
Click to expand...
Click to collapse
Is this true? I've tried plenty of ROMs and kernels and I don't remember any of them changing the button sensitivity.
The best way to show off how frustrating the buttons can be is to give the phone to someone that's never played with it before and watch as they struggle to register touches on the buttons. The people that use the phone daily have recognized that the touchpad is above the button and never think about it any more.
It's very apparent as soon as you rotate the phone into a different position though.

PrawnPoBoy said:
Is this true? I've tried plenty of ROMs and kernels and I don't remember any of them changing the button sensitivity.
The best way to show off how frustrating the buttons can be is to give the phone to someone that's never played with it before and watch as they struggle to register touches on the buttons. The people that use the phone daily have recognized that the touchpad is above the button and never think about it any more.
It's very apparent as soon as you rotate the phone into a different position though.
Click to expand...
Click to collapse
I also haven't noticed any change in the sensitivity with different ROMs or kernels. For me though, sometimes if I hit right on top of the button it won't register. I am used to just tapping it a little above and it works everytime.
As others have said, this is definitely not a deal breaker for me or shouldn't be for any person IMO. This phone's pros far outweigh the cons.

The best way to show off how frustrating the buttons can be is to give the phone to someone that's never played with it before and watch as they struggle to register touches on the buttons. The people that use the phone daily have recognized that the touchpad is above the button and never think about it any more.
Click to expand...
Click to collapse
When someone is doing that you should just say that it has Finger print authentication technology

absolutely true and this was my discovery today (day 4 with n1). the buttons work fine if you cheat towards the top of the button area and overlap into the screen area.
that solved it for me.
resolved for me for now...

xboomer55 said:
absolutely true and this was my discovery today (day 4 with n1). the buttons work fine if you cheat towards the top of the button area and overlap into the screen area.
that solved it for me.
resolved for me for now...
Click to expand...
Click to collapse
Did you just buy your N1 from Google brand new?

Those buttons are a pain in the bum, but you get used to them, the bigger problem is if the phone gets too cold it starts mis-registering the touchscreen necessitating a reboot or a bunch of mucking around to fix it. This is the biggest annoyance with the phone for me, hopefully they fix the screen calibration in 2.2!
Almost swapped mine for a Desire, thinking less of doing so now, unless anyone can offer a good reason

I got my N1 straight from Google on day one, and I'm currently running CM 5.06
I find the capacitive buttons to be _awful_ if I tap directly on them it takes 2-5 attempts to get it to register.
However, I have found that if I swipe from the button down off the bottom of the button it registers ever single time.
I'm pretty convinced that the problem isn't the digitiser itself but in the driver that splits that section of the digitiser off. I believe it checks to see if there is upward movement before registering a button tap and if it does detect upward motion it cancels the tap event and forwards the event as a touch screen event. I also thing that because I have pretty big fingers any time I press the flattening of my finger registers as a slight upward motion.
If I could find the button "sub"-driver I'd be hacking at it right now.
Still, I wouldn't give up my N1.

SilentMobius said:
I got my N1 straight from Google on day one, and I'm currently running CM 5.06
I find the capacitive buttons to be _awful_ if I tap directly on them it takes 2-5 attempts to get it to register.
However, I have found that if I swipe from the button down off the bottom of the button it registers ever single time.
I'm pretty convinced that the problem isn't the digitiser itself but in the driver that splits that section of the digitiser off. I believe it checks to see if there is upward movement before registering a button tap and if it does detect upward motion it cancels the tap event and forwards the event as a touch screen event. I also thing that because I have pretty big fingers any time I press the flattening of my finger registers as a slight upward motion.
If I could find the button "sub"-driver I'd be hacking at it right now.
Still, I wouldn't give up my N1.
Click to expand...
Click to collapse
Just realized that!!
It does not get the upward movement
It gets: right, left & down
So this means, one could set different options for different directions...

hacker01 said:
Recently, I've been considering getting a Nexus One, however, most of the reviews I read say that the N1's capacitive buttons are a little unresponsive. You must tap the upper half of the button as opposed to the bottom half of the button.
I've also read that some of the cyanogen roms have fixed this problem. Can anyone give me more insight on this issue?
Click to expand...
Click to collapse
I have noticed no issues when holding the phone in my hands but the responsiveness is not that great if the phone is flat on a desk or a similar surface. I wonder what if anything the accelerometer may play a factor.

PrawnPoBoy said:
Is this true? I've tried plenty of ROMs and kernels and I don't remember any of them changing the button sensitivity.
The best way to show off how frustrating the buttons can be is to give the phone to someone that's never played with it before and watch as they struggle to register touches on the buttons. The people that use the phone daily have recognized that the touchpad is above the button and never think about it any more.
It's very apparent as soon as you rotate the phone into a different position though.
Click to expand...
Click to collapse
I dunna man, my 3-year-old daughter figured it out within a minute of getting my phone. I set her up in a game and she decided she wanted something else, so she messed with the capacitive buttons until she got out of the game. Once she had it once or twice (~5-10 seconds for her to figure out each time) it was pretty much instant after that. If a 3-yo can figure it out, I'm pretty sure it's not THAT difficult. Annoying, sure....but not difficult.

hacker01 said:
Did you just buy your N1 from Google brand new?
Click to expand...
Click to collapse
Yes. Direct from Google.

Wow there's definitely a good mix of answers. I thought that the newer batches of N1's fixed the capacitive button problem, but apparently not.
I guess there's not a definite answer. It seems the only conclusion you can make is that some N1's may still have the problem, some may not. Some can be fixed with custom roms and unlocking the bootloader and some cannot. Your results may very.
EDIT: After rereading some of the previous posts (more carefully. excuse my sleep deprived state lol), the capacitive button issue might actually be more of a feature than an issue. I've read similar posts about the capacitive buttons having that sort of "motion detection" thing to prevent accident presses. Hopefully for anyone still having the problem, you can reread some of the posts on this page and give their methods a try

I haven't had a problem with mine but I haven't had the problems most people say they have with the phone so I would recommend this phone to anyone that wants an android phone
-------------------------------------
Sent from my Nexus One

Nexus One screen accuracy?

I've had Nexus one for a week so and I am very happy with it (so much better than my old touch pro2 except the keyboard). However, one thing really bugs me is the screen accuracy. A lot of times say when I press on a link in the browser the press actually registered to something below. So in order to hit the link l want I need to press a little bit higher. For example if there's 3 links
Link0
Link1
Link2
When I press on link1 the screen showed I pressed on link2. And press Link0 takes me to Link1. It's not a deal breaker but it's quite annoying. Same thing happens for the home/back buttons. So is this a common problem with Nexus one or just my device? TIA

what is your firmware version.
some say this problem was fixed for 2.1-u1
was for me.

You can always use the trackball to select links if they're stuck really close to each other

zachthemaster said:
what is your firmware version.
some say this problem was fixed for 2.1-u1
was for me.
Click to expand...
Click to collapse
This is a well-known issue and was not fixed for 2.1-u1. It does occasionally happen and is quite annoying but I've learned to live with it.
The awesome things about the device outweigh the little annoying things for me

Bryce2010 said:
This is a well-known issue and was not fixed for 2.1-u1. It does occasionally happen and is quite annoying but I've learned to live with it.
The awesome things about the device outweigh the little annoying things for me
Click to expand...
Click to collapse
Thanks for everyone's reply. I think mine has the latest firmware but I guess this is a common issue that cannot be addressed through software......

no it cannot be fixed so far, and it still exists with the newest froyo. the only solution is to lcok the screen, then unlock. that resets it and fixes the problem for a good while. only takes a few seconds. its one of the nexus one's little dirty secrets!

RogerPodacter said:
no it cannot be fixed so far, and it still exists with the newest froyo. the only solution is to lcok the screen, then unlock. that resets it and fixes the problem for a good while. only takes a few seconds. its one of the nexus one's little dirty secrets!
Click to expand...
Click to collapse
Lock and unlock screen..you mean press the power button to turn off the screen and then turn the screen on and slide to unlock?

codesplice said:
You can always use the trackball to select links if they're stuck really close to each other
Click to expand...
Click to collapse
+1 thats what I do when you cannot click on something no matter how much you zoom in. trackball+click

[Q] Touch Screen Responsiveness

Device: Nook Color rooted to 1.1
I had my Nook Color in the car today (40 degrees or so), pulled it out to show her what it looked like rooted. While standing in the driveway showing her different things, I found the touch screen was overly sensitive. As I was scrolling through different things (the app list, twitter, facebook), the slightest touch would select/open an item. It normally doesn't do this. It was incredibly frustrating and almost unusable. I pulled it out later and it seems to be behaving like it normally does.
Does temperature affect the NC screen? Where they any touch screen changes in 1.1? Is there a setting to calibrate the touch screen? I can't seem to find one. Any other suggestions?
I tried doing a search on the forum, but the search crashed.
Thanks.

horsemom said:
Is there a setting to calibrate the touch screen? I can't seem to find one.
Click to expand...
Click to collapse
I was wondering this myself. My input doesn't seem to register as I get towards the edge of the screen.

tactfulcactus said:
I was wondering this myself. My input doesn't seem to register as I get towards the edge of the screen.
Click to expand...
Click to collapse
I don't know if it's placebo or not, but I feel like this app improved my screen response.
http://forum.xda-developers.com/showthread.php?t=934500
As for the other question, I would expect the screen to be less responsive in cold weather, but I don't have anything to base that on.

Guessing what you experienced was due to condensation on the screen. Doesn't take much and can be 'invisible' to you but the screen is sensitive to 'stuff' on the screen and will become overly sensitive if there is anything on it, like moisture, skin oils, etc .. a screen protector may help but unless it continues that is probably the cause.

tactfulcactus said:
I was wondering this myself. My input doesn't seem to register as I get towards the edge of the screen.
Click to expand...
Click to collapse
What you experience is probably temperature related, but another thing to try is to increase the LCD screen density to around 190, 200, or a little more. For me, I get improved sensitivity, especially near the corners.

My daughter accidentally got a little water on the screen and it was a little erratic. I put it in a ziplock with a handful of rice for about 6 hours and it was like new.

I have owned 3 nook colors, the first one I owned freaked out when I used a damp cloth to wipe the screen. It exhibited some strange behavior and emitted some loud static from the speaker. It would not power down or anything... finally it just went back to normal, so I took it back to B&N and then went and bought one at walmart. I took it back because I thought I wanted the Viewsonic G Tablet. But after trying it I finally bought a Nook Color at Best Buy, bought a screen protector too so that I don't have a repeat of my first NC. The screens on these things are, I believe, rather sensitive and the cold or the moisture may have played a part in your unit's behavior.
migrax

tactfulcactus said:
I was wondering this myself. My input doesn't seem to register as I get towards the edge of the screen.
Click to expand...
Click to collapse
Same here. My screen also seems very inaccurate.
Have you found a fix?
Sent from a NookColor using the xda app

I'd be interested in a solution for this as well, since the edges of my NC screen seems to be a lot less sensitive. For instance, when the Market is launched, it takes 4-5 tries to hit the search button at the right top corner (I know that I can hit menu and select search from there, but I am trying to illustrate my point).

tenderidol said:
I'd be interested in a solution for this as well, since the edges of my NC screen seems to be a lot less sensitive. For instance, when the Market is launched, it takes 4-5 tries to hit the search button at the right top corner (I know that I can hit menu and select search from there, but I am trying to illustrate my point).
Click to expand...
Click to collapse
this modified kernel solves that
http://forum.xda-developers.com/showthread.php?t=925451
and you'll also get a speedier nook

It's funny, actually... The cold makes your skin less detectable because of vasoconstriction in your fingers as a physiological response to the cold temperature, but a hint of moisture by means of condensation has the opposite effect.
For me, condensation is rarely a problem, but the decreased capillary blood flow effect is quite noticeable.
Sent from my Nexus S using XDA Premium App

One thing that's been mentioned before (and the B&N salesman told me while buying a screenprotector) is that if the screen has a lot of fingerprints, it'll make the nook act weird.
Try wiping the screen of fingerprints.

don_ernesto said:
this modified kernel solves that
http://forum.xda-developers.com/showthread.php?t=925451
and you'll also get a speedier nook
Click to expand...
Click to collapse
Thanks for the reply. Is it safe to assume that the screen sensitivity would not be an issue in Honeycomb since it is designed for tablets? If so, I may just wait for the final release of HC before fiddling with different kernels,etc. Thanks!

tenderidol said:
Is it safe to assume that the screen sensitivity would not be an issue in Honeycomb since it is designed for tablets? If so, I may just wait for the final release of HC before fiddling with different kernels,etc. Thanks!
Click to expand...
Click to collapse
final realease of HC? no one knows if we will ever have one...... anyhow, it seems to be a fix at kernel level (had to be fixed in eclair, froyo and HC), and it fact, it was discovered by deeper (the guy who ported our HC version)
my suggestion? go for it now. the sensitivity problem is way too bothersome, and it is very easy to apply

don_ernesto said:
final realease of HC? no one knows if we will ever have one...... anyhow, it seems to be a fix at kernel level (had to be fixed in eclair, froyo and HC), and it fact, it was discovered by deeper (the guy who ported our HC version)
my suggestion? go for it now. the sensitivity problem is way too bothersome, and it is very easy to apply
Click to expand...
Click to collapse
Thanks again for the reply.
Yes, I'd love to take care of it ASAP, since I'm sick of trying to hit a small button on the screen and going somewhere else instead.
My NC was rooted with B&N 1.1 + Autonooter 3.0. Will I still be able to "apply" the changes that you mentioned on top of that or do I have to start from scratch?
Thanks!

tenderidol said:
My NC was rooted with B&N 1.1 + Autonooter 3.0. Will I still be able to "apply" the changes that you mentioned on top of that or do I have to start from scratch?
Thanks!
Click to expand...
Click to collapse
go ahead! you won't loose any app or any data (not even your progress in Angry Birds)
Of course, before applying this changes i always make a backup. good to have a way back in case something goes wrong

Good test tool
I ran GoJimi's tool, and since then my screen has been flipping out. Typing anything is a good test...I enter one key like "z", and get 2 - "zm". Utterly maddening.
A good tool to see what's going on is "Mutitouch Test" from JerryW in the market.
When I press with one finger, I see a "phantom" 2nd point jumping around. Very quick way to see 1) how good tracking is and 2) if there's any random inintended multitouch action happening.