I've tried a lot of android builds whilst the development has been going on and found that Bangster's 1.4 coupled with Michy's R11 was the best for me with regard to screen sensitivity and keyboard accuracy.
I recently had a dabble with m-deejay's next-gen builds Desire HD/Z etc (which are excellent by the way, credit to him), and found that I was getting a lot of screen bounce, missed button presses and a very frustating keyboard experience (Hastarin R7.1). Pressing and holding the delete key for example would result in keypresses bouncing all over the place, sometimes several keys removed from the delete key. I tried a plain Froyo Sense build and found the same thing, although not quite as bad.
So, I decided to try the bare kernel from Michyprima's R11 (AXI, Desire, OC) on my current Froyo Desire build just to see if it was down to the kernal 100%. Instant bounce removal... keyboard is accurate and now when I press & hold on the home screen, I don't get the screen wobbling from side to side as the software thinks that I'm moving my finger around rapidly.
To recap; it seems like I was getting more bounce with Hastarin's R7.1 than any other, but certainly Michy's R11 (Desire based) is making my phone usable again. It really was bad before.
More messing required methinks... I may re-load the Desire Z build on to my SD card and try R11 to see what it's like. One thing I remember is whilst trying m-deejay's Desire HD 3.1 (which had an Evo kernel IIRC), keyboard bounce was almost non-existant. It wasn't until I changed to D-HD 3.3 that the keyboard became a pain to use (Hastarin R7.1).
Hastarin if you read this, please note this is by no means a dig, I have the greatest respect for all the guys posting builds here, these are just my obvservations.
As with all things Android/HD2 related, YMMV. Your thoughts are welcome.
---------------------------------------------------------------------
---------------------------------------------------------------------
Edit: I've taken a couple of quick videos of m-deejay's brand new 3.4 Desire HD build showing this phenomenon (kernal is huanyu's #21). Replacing the zImage with Michy's R11 virtually eliminates it.
Video 1 - homescreen
Video 2 - keyboard
Could this be Windows ROM related? Might flash another WinMo ROM to see if it's any different.
Edit 2 Sent my HD2 back to HTC today, hopefully for TS replacement... see relevant post here.
Edit 3 Received my HD2 back from HTC's repair department. Problem fixed. No more bouncing Relevant post here.
No-one else with similar experiences?
Me too!
previously was using M-deejay's froyo sense 2.2 and the keyboard was a great improvement from my old stock HD2 Windows keyboard, which was oversensitive and jumps alot, making typing a hassle. I did not have any problems with the froyo sense 2.2 keyboard, it was accurate and sufficiently responsive, and even have my essential chinese input.
However, after the 2.4 version was released, i updated it, and noted that the browser's bookmark crashes. So i though, why not give EVO Sense 1.6 a try?
Btw, i did not realise any problems with the 2.4 keyboard, so it's probably as good as the 2.2 version.
Then i ran EVO sense 1.6, and i feel that the keyboard is different. Firstly it's the additional arrow buttons below, which is useful, and more like the original HD2's keyboard. Then it also has chinese input.
BUT i experience alot of the "bouncing" problems, if not more than my original HD2 windows rom. tried calibrating a few times, and deleting the calibration, but it doesn't help.
i want to emphasize again i am very grateful to all the developers like M-deejay, Hastarin, for developing all these builds that are effectively working. this is likewise, just my observation.
Anyone else? I can't believe it's just us two!
Videos added to 1st post.
I tried to replicate your problem (m-deejay's Desire HD 3.4) but I coulnd't. I also thinkg that the keyboarad its not as accurate as some of the builds but its not that bad as yours.
I'm sorry to say but the lag with the keyboard kinda looks funny
My keyboard isn't very accurate too. Sometimes it just takes the wrong key. I mean when I press the backslash it takes "m" or something although i was pressing backslash. This was on Hastarin 4.1.
But it really seems to be kernel related. With the r11 my keyboard is okay.
I don't think is caused by the WM ROM, but which one do you use?
have the same prob!
yep...and I get phantom touches also.
jaka.erc said:
I tried to replicate your problem (m-deejay's Desire HD 3.4) but I coulnd't. I also thinkg that the keyboarad its not as accurate as some of the builds but its not that bad as yours.
Click to expand...
Click to collapse
What WinMo ROM are you running?
JanssoN said:
I'm sorry to say but the lag with the keyboard kinda looks funny
My keyboard isn't very accurate too. Sometimes it just takes the wrong key. I mean when I press the backslash it takes "m" or something although i was pressing backslash. This was on Hastarin 4.1.
But it really seems to be kernel related. With the r11 my keyboard is okay.
I don't think is caused by the WM ROM, but which one do you use?
Click to expand...
Click to collapse
CleanEx DsE GTX 6.5.x
anoschka666 said:
have the same prob!
Click to expand...
Click to collapse
muzicman0 said:
yep...and I get phantom touches also.
Click to expand...
Click to collapse
Try changing your zImage to Michyprima's R11 and post your findings
Major_Sarcasm said:
No-one else with similar experiences?
Click to expand...
Click to collapse
OK ! very common HD2 touchscreen failure! ...ur touchscreen is defective ....there are many threads already on xda regarding this ...but could not be solved because this is a hardware problem ...this even happens in winmo ! here are the youtube videos having same problem
http://www.youtube.com/watch?v=DhhrA3u4rcI
http://www.youtube.com/watch?v=3rJJ1eyM9FM&feature=related
http://www.youtube.com/watch?v=QEHn9CaHFpk&feature=related
http://www.youtube.com/watch?v=hY60I9Z0RU0&feature=related
http://www.youtube.com/watch?v=TSvAlqw6HJw&feature=more_related
http://www.youtube.com/watch?v=6hIE_wV4djs&feature=more_related
and here is my thread about this in detail - http://forum.xda-developers.com/showthread.php?t=745255
so , the conclusion is ...u have to get ur screen replaced under warranty ....i had the same problem with my hd2 ...and i got so pissed ...so get ur screen changed and that is the only solution !
hope that helps -
cheers
coolbeer1990
Got it to but not in my homescreen. When I am typing with swype ... When I try to delete a word it will write 10 :X nice feature but its really anoying. But lets wait I thing dev know about it let wait for nand and the bother them with this. I heard It is a long way to nand
coolbeer1990 said:
so , the conclusion is ...u have to get ur screen replaced under warranty ....i had the same problem with my hd2 ...and i got so pissed ...so get ur screen changed and that is the only solution !
hope that helps -
cheers
coolbeer1990
Click to expand...
Click to collapse
Thanks for your reply. However, my screen isn't defective as I don't have this problem in Windows and using a different kernel fixes it.
major_sarcasm said:
thanks for your reply. However, my screen isn't defective as i don't have this problem in windows and using a different kernel fixes it.
Click to expand...
Click to collapse
that's great my friend
Well.. i have the same thing in hastarins latest kernel
I dont have this on DesireZ out the box.
I have MDeejay's latest Desire HD build and have this problem, how do I fix it? If I need to replace the Kernel how do I do it? What side effects will it have?
Thanks in advance
keyboard bounce also experienced by me when i am trying to type fast, using hastrin r7.1 as well, maybe is caused by the touchscreen delay?
have you tried keyboard calibration?
in the setting menu ..
it ask you to type that ..lazy brown fox jumps..
it helps me alot.. well some of it i guess
and also try the schrub bartome build. the keyboard is perfect-iphone like. im using this build for day use
I experience the same issue with the new kernel releases. But with hastarin #3 the touchscreen works normally.
Sent from my HTC Vision using XDA App
Related
Well this is basically a pointless thread other than to say I've read about bugs people are experiencing and all the threads about it.
Well this is the no bug thread. I have zero issues and think this is the best stock rom I've tried (besides trackball wake) and honestly even better than every custom I've tried. This will only make the new custom roms better.
Anyways please don't post if ya have bugs. This is the I got not a single bug thread.
FROYO ROCKS, even this isn't the real final release ( even though I don't see final any different)..
Like yourself, I'm probably one of the lucky ones that has not had any issues with Froyo.
I can't really comment too much on reception, I've noticed that the bars tend of fluctuate a bit more now, but the overall signal seems to have gotten slightly stronger.
I conducted a full wipe before I installed Froyo, so maybe that's a contributing factor to our overall positive experience with Froyo opposed to those who may have simply installed Froyo over their previous ROM.
I also have no issues with froyo. I'm very pleased with it. I just hope I get an update to the official build since i'm not rooted.
none for me that I know of.
very, very complete wipe before install.
I'm extremely pleased with the wifi performance, it's very fast, connects no problem to my usual spots without the hassle. And the better sound on phone calls.
No bugs for me! I'm completely stock, coming from ERE27. I didn't even wipe.
I can easily say this is the fastest android I've ever experienced!
Yeah there may be bugs on some of you mugs... but there ain't no bugs on me. =)
http://www.youtube.com/watch?v=nNlt0D_xba4
temperbad said:
FROYO ROCKS, even this isn't the real final release ( even though I don't see final any different)..
Click to expand...
Click to collapse
Im using Paul's froyo kitchen ROM + CM Kernel + Setcpu.apk + spareparts.apk
I got No "ROM" or internal apps problems ...
pvillasuso said:
Im using Paul's froyo kitchen ROM + CM Kernel + Setcpu.apk + spareparts.apk
I got No "ROM" or internal apps problems ...
Click to expand...
Click to collapse
Is that spare parts from the market or a special moddified one?
temperbad said:
Well this is basically a pointless thread other than to say I've read about bugs people are experiencing and all the threads about it.
Well this is the no bug thread. I have zero issues and think this is the best stock rom I've tried (besides trackball wake) and honestly even better than every custom I've tried. This will only make the new custom roms better.
Anyways please don't post if ya have bugs. This is the I got not a single bug thread.
FROYO ROCKS, even this isn't the real final release ( even though I don't see final any different)..
Click to expand...
Click to collapse
Zero complaints here. It's solid and I am getting good battery life. If you want trackball wake, you can add the Market app "No lock". The display will sleep but will wake on any hardware button push - vol up/down/trackball. No unlock required.
attn1 said:
Zero complaints here. It's solid and I am getting good battery life. If you want trackball wake, you can add the Market app "No lock". The display will sleep but will wake on any hardware button push - vol up/down/trackball. No unlock required.
Click to expand...
Click to collapse
lol, your killing me bro. All this N1 talk is getting to me. =) I really can't wake for trackball wake because that way I can avoid the power button issue that some people are having.
ChillRays said:
lol, your killing me bro. All this N1 talk is getting to me. =) I really can't wake for trackball wake because that way I can avoid the power button issue that some people are having.
Click to expand...
Click to collapse
Go take a cold shower and stop that or you'll go blind.
I've had no bugs at all, except with apps and that has nothing to do with the build itself, I just can't wait for it to be a full Rom and themed with all of the goodies lol
-------------------------------------
Sent via the XDA Tapatalk App
I too have no bugs. I used the pre-rooted rom, running set cpu and a modded swype as well, no issues, I love this rom! I can't wait to see what cyanogen cooks up with this.
No problemo.
I have had no bugs either. Once there was a soft reset when I used an unstable hack to implement Apps2Sd, but that's all.
ChillRays said:
Yeah there may be bugs on some of you mugs... but there ain't no bugs on me. =)
http://www.youtube.com/watch?v=nNlt0D_xba4
Click to expand...
Click to collapse
LOL!
temperbad said:
Is that spare parts from the market or a special moddified one?
Click to expand...
Click to collapse
From market !
pvillasuso said:
From market !
Click to expand...
Click to collapse
Thanks!!!!!!
no problems here...awesome, but i need a bit more (see signature)
no bugs here...just waiting for the devs to update their apps for 2.2 and sd install
missing about 10 paid apps.......ta ta ta today junior
Hey guys.
After trying dozens of ROMs for a week, I can't find a good sense rom. Nothing fancy. As close as stock 2.1 sense as I can get. I have a 1024 Tmous HD2. Preferably something like the DFT NAND ROM that I'm sure everyone is familiar with, but without any bugs.
Please?
Thankss
Sense of eclipse ...is to be recommended
Really great work from daekin !!!
Belp said:
Sense of eclipse ...is to be recommended
Really great work from daekin !!!
Click to expand...
Click to collapse
I don't think a ROM where you need to use an app to turn off the dang thing is great. As a matter of fact, the only thing I see in NAND development these days are these buggy Sense 3 ROMS, Sense 2.1 ROMs themed to the point of retina destruction and that MIUI crap.
Why has nobody made a stock Desire HD ROM for cLK.
To the OP: If you're a fan of MAGLDR, try this: http://forum.xda-developers.com/showthread.php?t=915159
Only thing wrong is the camcorder doesn't work with the stock HTCCamera.apk. (and another thing wrong with it is that it's for MAGLDR )
there are stock like hd with sense 2.0 which can be used with clk
rr5678 said:
I don't think a ROM where you need to use an app to turn off the dang thing is great.
Click to expand...
Click to collapse
I don't need any app to turn off the "dang thing" like you said....
Anyway, the issues i knew after 2 weeks of use:
Camcorder with higher resolutian than 320x240 does not work (i'm not a cameraman so it does not affect me...)
Graphical glitches (much less then in other NAND-roms. Really: not disturbing)
Thats it and all what i've noticed in 2 weeks use. ^^
After testing these two weeks, i only can say that the rom is fast, stable and (that's important i think) suitable for everyday use...
Greetz
Belp
Belp said:
I don't need any app to turn off the "dang thing" like you said....
Click to expand...
Click to collapse
So you're telling me that this list is lying?
Known Issues
Camcorder (Records well up to 320x240 resolution)
Tethering (Workaround: third party app can be used)
Graphical glitches (horizontal stripes)
[*]Power menu (Works one time, QuickBoot application included)
Click to expand...
Click to collapse
rr5678 said:
So you're telling me that this list is lying?
Click to expand...
Click to collapse
Hi,
I'm not sure why you are laying so much importance on such a minor aspect of a great ROM.
Have you actually tried it?
As it happens my power off (stock) button is still working.
But what's the difference between pressing the power button and pressing an app button.
Same result...
@[OP] Try it.You may like it.
rr5678 said:
So you're telling me that this list is lying?
Click to expand...
Click to collapse
No, of course not. I'm just telling you my experiences. And if i want to turn it off i just turn it off^^ button is working for me...
Anyway, it's just like malybru said: not a important thing. Test it, you may like it too^^
malybru said:
@[OP] Try it.You may like it.
Click to expand...
Click to collapse
can only agree with that
enough is enough
its starting to get really annoying seeing people constantly asking
about when the gfx glitches will be fixed ,even though 2 or 3 posts
above theres someone has already said when they will be fixed
i can probably count 30 or more posts in differnt threads in the last 12
hours asking that same question
so here it is in a nut shell and read it really slow
the gfx glitches on GB Sense roms will be fixed when HTC releases the Kernel Source Code, untill that happens we will have those small glitches
so please out of common courtesy for the Devs of the sense roms
stop asking when the gfx glitches will be fixed every other post
Unfortunately I say let trolls roll. I just ignore moronic posts that have been asked before whenever I search the forums anyways
Sent from my HTC HD2 using XDA App
Kameirus said:
the gfx glitches on sense roms will be fixed when the source code
is released, untill that happens we will have those small glitches
Click to expand...
Click to collapse
When you say "source code," do you mean the HTC Sense source code or the source code of the custom ROMs from which Sense was ported? Either way, it seems likely that it'll be a while before either will be released
EDIT: You edited it with more description. Thanks!
When the gfx glitches will be fixed?
it's bug not in videos drivers in the kernel, it's bug gralloc library
Does anyone know if these same issues are effecting any other phones?
Sent from my HD2 using XDA App
Thanks for the information. Now i can stop asking when the gfx glitches will be fixed
Greetz
Belp
What do the glitches actually look like? I have a Sense rom installed but a Froyo. So, not sure what they look like. Can you post a screen shot or direct me to a post that shows?
I rarely notice the glitches on the Sense 3 ROM I'm using. But I figure when a Sense 3 ROM is released that is closer to the HD2 in hardware specs...like HTC releasing a Sense 3 ROM for the Inspire 4G/DesireHD, the glitches and bugs will continue to be an issue. Although they are a monor issue in my current ROM.
Egrier said:
What do the glitches actually look like? I have a Sense rom installed but a Froyo. So, not sure what they look like. Can you post a screen shot or direct me to a post that shows?
Click to expand...
Click to collapse
They are in GB sense not froyo, If you want to see what they look like flash a GB rom.
Egrier said:
What do the glitches actually look like? I have a Sense rom installed but a Froyo. So, not sure what they look like. Can you post a screen shot or direct me to a post that shows?
Click to expand...
Click to collapse
I also didn't know what glitches where, but....
Yesterday I tried the Pyramid port from dungphp and there they where, the nasty little buggers!
As I don't have a screen-shot from any glitches I'll try to describe it for you.
Here we go...
They seem to appear when there's graphical activity (i think).
Like for instance in scrolling text (like in the app Quick System Info) and in the text under the scene (loading preview) in the scene picker in Sense 2.1 and 3.
So the glitches are mostly seen around and through text.
It's no more than little white lines completely running through your white text, making it hard(er) to read.
It's there, sometimes annoying, sometimes not.
For me it was one of the reasons not to stay on the Pyramid port or use any other GB Sense rom.
Luckily we have many roms to choose from here
Here you go mate, hope this clarifies it somewhat.
Thanks for the explanation. That helps out alot. I think I will just stay with Froyo. It's been working great for me so far.
Egrier said:
Thanks for the explanation. That helps out alot. I think I will just stay with Froyo. It's been working great for me so far.
Click to expand...
Click to collapse
which froyo build are you using?
By the way, I'm not sure if you are aware of this or not but there is a flashable fix for the Graphics, However it will kill your camera .
Link to fix.
kawazaki said:
By the way, I'm not sure if you are aware of this or not but there is a flashable fix for the Graphics, However it will kill your camera .
Link to fix.
Click to expand...
Click to collapse
and messes up your dialer
boysha8 said:
which froyo build are you using?
Click to expand...
Click to collapse
I've been running the MAGLDR version of Frankinstine DROID HD v1.2. It has sense and works pretty good.
In this thread we will do the discussion of this ROM so we don't bother the developers anymore!
Sorry for this question, I am in good faith, but I want to understand if Drewis is developing this kernel alone or collaborating with the team CyanogenMod (or other). I guess the first hypotesis, but maybe they are sharing progress. Repeat, I am gratefully, it's only a curiosity
paolo-red1 said:
Sorry for this question, I am in good faith, but I want to understand if Drewis is developing this kernel alone or collaborating with the team CyanogenMod (or other). I guess the first hypotesis, but maybe they are sharing progress. Repeat, I am gratefully, it's only a curiosity
Click to expand...
Click to collapse
This is the discussion thread of the evervolv ROM and you're free to ask whatever you want. It's only a question and can't hur
If I'm not mistaken, texasice, drewis and the rest of the evervolv crew are working on the new kernel alone.
Theshawty said:
In this thread we will do the discussion of this ROM so we don't bother the developers anymore!
Click to expand...
Click to collapse
which part of evevolv do you want discuss?
j00m said:
which part of evevolv do you want discuss?
Click to expand...
Click to collapse
Anything mate. Abt ur experience, what you like,what you dont like, what features u want and miss, etc.
This way it will be better for devs and also it will be good for us too
Sent from my Nexus One using Tapatalk
j00m said:
which part of evevolv do you want discuss?
Click to expand...
Click to collapse
Anything, really. Better to discuss here than to bother texasice.
Sent from my Nexus One using Tapatalk
Can anyone post a youtube of the newest version running with HWA to see how it compares with MIUI?
I am curious to see if it's worth installing...
Really appreciate it!!
Markdental said:
Can anyone post a youtube of the newest version running with HWA to see how it compares with MIUI?
I am curious to see if it's worth installing...
Really appreciate it!!
Click to expand...
Click to collapse
I can tell you that the latest version is running pretty smooth for me, the UI just seems faster and I can run the Chrome Beta which I couldn't even load up using MeDroid. HWA even at this early stage is giving my N1 a whole new life.
Very promising ROM but far too buggy for me to leave MIUI for it. :/
Sent from my Nexus One using Tapatalk
I flashed the P9 release yesterday (my first ICS release)... pretty smooth in general, Quadrant scores are not far behind the scores I had with CM7.1 (998 with evervolv P9 VS 1039 with CM 7.1)...
Got the same issues as stated in the "not working" section, plus the clock crashes (to set alarms) but that could be just a question of wiping cache/dalvik again.
Coming from CM, I miss all the customizations options in this ROM. Dont get me wrong, texasice did a fantastic job with the ROM and kernel development, especially in figuring out the HWA part...
But I will surely try MeDroid Remix (as soon as it's new release with HWA comes out this weekend) to see what it offers... looking at samuaz's thread, it looks a lot more customizable and coming from CM, it might be just what I'm looking for.
I will surely donate to both texasice and samuaz as well for a fantastic job done on their part, otherwise, we'd be probably stuck with Gingerbread forever.
I know plenty of much newer phones than ours that don't have a mod that can run chrome properly.
That said, if people are playing around with older (more stable?) versions and want to give some of the reboot fixes a try, look up market id com.jrummy.sysctl.config to set the memory without the new kernel or messing with scripts.
A lot of the CM stuff you might be used to is available from other programs. I mostly miss the brightness hacking and night mode filters, but I found a separate program that can make my screen dimmer to use as a night mode. The way the notification toolbar works is slightly different too. And Trebuchet is nice, but not that much different that I can tell.
I have an issue with p4 through p9.
I used trackball wake on build p3 it worked like a charm, but now when I press the trackball, pwr or vol buttons, the soft buttons are lighting but the screen remains black, I have loaded p4, p6, p7, and p9. All Roms work fine initially and appear trouble free up until the phone goes to sleep. After the phone goes to sleep the screen won't wake no matter what I do.
I have tried several SD cards, tried to turn off wifi, tried to change swap sizes from none to 256.... Not sure what else could be causing this???
Any ideas anyone?
ezoliver said:
I have an issue with p4 through p9.
I used trackball wake on build p3 it worked like a charm, but now when I press the trackball, pwr or vol buttons, the soft buttons are lighting but the screen remains black, I have loaded p4, p6, p7, and p9. All Roms work fine initially and appear trouble free up until the phone goes to sleep. After the phone goes to sleep the screen won't wake no matter what I do.
I have tried several SD cards, tried to turn off wifi, tried to change swap sizes from none to 256.... Not sure what else could be causing this???
Any ideas anyone?
Click to expand...
Click to collapse
So I got my phone running on the latest p11 finally. It works great, has been running for days, no reboots, pretty fast and seems stable so far... AND battery life has been awesome!
What I found was the CWM recovery was jacking my sd card when I partitioned it. I tried 4EXT recovery and all has been well after that.
No obvious issues other than camera preview...
Sometimes while on call the mic stops responding.. People calling me are not able to hear me..
I'm running p11 and not facing any other issues except the known one like camera preview etc ...
Anybody else facing similar issue?
*le bump*
Please do not let this topic die.
New rom is out. I had problems with wifi. No work around seem to work. I wait till the next version which I believe or hope to be stable one. Have to thank texasice, the rom is super smooth. ;-)
Sent from my Nexus One using XDA
i think he posted a rebuilt p12 in the thread. it might be on the op page by now.
I just installed p13 today, it seems to work fine. The interface is a bit sluggish in places, for example Google Play is quite slow, and buttons don't always respond immediately. Is that normal for this rom?
Jacotb said:
I just installed p13 today, it seems to work fine. The interface is a bit sluggish in places, for example Google Play is quite slow, and buttons don't always respond immediately. Is that normal for this rom?
Click to expand...
Click to collapse
Try to flash a standalone Tiamat ICS kernel and see if that helps. Download it here: http://tiamat-dev.com/mahimahi/
taodan said:
Try to flash a standalone Tiamat ICS kernel and see if that helps. Download it here: http://tiamat-dev.com/mahimahi/
Click to expand...
Click to collapse
Thanks, I tried the 0314-kernel and got slightly better results in the Quadrant benchmark (1004 as opposed to 937). But it didn't make a noticable difference in interface responsiveness.
It's not dreadful, but just not nearly as good as FroYo. But I'm not gonna expect any better since this is just a community work-in-progress rather than an official release.
Hey
I installed this rom yesterday, my applications are much smoother, but i have a huge problem, which makes almost every game unplayable. When i try to play the game with 2 fingers, it doesnt respond well. Is there any way to fix this?
Rucsok said:
Hey
I installed this rom yesterday, my applications are much smoother, but i have a huge problem, which makes almost every game unplayable. When i try to play the game with 2 fingers, it doesnt respond well. Is there any way to fix this?
Click to expand...
Click to collapse
That's not a problem with the ROM as much as it is a general problem with the HD2 unfortunately. It only supports 2 points on the screen, and I've found it does that terribly as well.
Nigeldg said:
That's not a problem with the ROM as much as it is a general problem with the HD2 unfortunately. It only supports 2 points on the screen, and I've found it does that terribly as well.
Click to expand...
Click to collapse
I dont think so, in my previous rom (Typhoon CM7) multitouch worked flawlessly in the games. After all these updates, how isnt it a priority to fix this?
Rucsok said:
I dont think so, in my previous rom (Typhoon CM7) multitouch worked flawlessly in the games. After all these updates, how isnt it a priority to fix this?
Click to expand...
Click to collapse
Because it's working for almost everyone, so it isn't really a 'known problem' as such. What version of the ROM are you on? If you're on 2.1 it'll be a bit shady, but multitouch works as well as it did on Typhoon for me on v2.2 (haven't got round to the 2.3 update yet).
Nigeldg said:
Because it's working for almost everyone, so it isn't really a 'known problem' as such. What version of the ROM are you on? If you're on 2.1 it'll be a bit shady, but multitouch works as well as it did on Typhoon for me on v2.2 (haven't got round to the 2.3 update yet).
Click to expand...
Click to collapse
2.2
I'll reinstall the rom (now the 2.3 version) hopefully this will fix the problem.
Rucsok said:
2.2
I'll reinstall the rom (now the 2.3 version) hopefully this will fix the problem.
Click to expand...
Click to collapse
Hmm, try going into the settings>developer options and enabling 'pointer location', then see if both the points are detected. Don't worry if the two points sometimes 'lock together', this is normal for the HD2's outdated screen
Nigeldg said:
Hmm, try going into the settings>developer options and enabling 'pointer location', then see if both the points are detected. Don't worry if the two points sometimes 'lock together', this is normal for the HD2's outdated screen
Click to expand...
Click to collapse
I tried this, i can certainly feel the "lock together"-effect. Is that supposed to be normal? If thats a HD2 related problem, how come i havent experienced this before?
Rucsok said:
I tried this, i can certainly feel the "lock together"-effect. Is that supposed to be normal? If thats a HD2 related problem, how come i havent experienced this before?
Click to expand...
Click to collapse
As far as I know that's a HD2 problem, yes. You probably have experienced it before, but haven't noticed it because you don't have the visual feedback to show you that it's happening. It doesn't have much of an effect during gaming (surprisingly)
omethek
it is a problem, because any game with a joystick is unplayable.
edit: besides the 'lock together', sometimes when the touch points are close to eachother, they are detected "inversed". is that normal too?
I agree that our device is outdated, but I've never experienced such issues.
I played multitouch games on WP7, Android GB & (Currently) ICS .. Even GTA 3, the movements are precise.
Not sure what you two are facing, but it's definitely not "too-old" related.
The only thing that the HD2 can't do is handling more than two finger points, other than that, everything seems to be fine for me.
There are lockups, but they are rare.
Rucsok said:
it is a problem, because any game with a joystick is unplayable.
Click to expand...
Click to collapse
Rucsok said:
edit: besides the 'lock together', sometimes when the touch points are close to eachother, they are detected "inversed". is that normal too?
Click to expand...
Click to collapse
I'm beginning to agree with Marvlesz here, these issues aren't that normal. I've never had the points becoming inversed and I can play games with onscreen 'joysticks' (i.e. GTA3) fine, so I think you might need to take a look at some of those threads with the digitizer issue and check if others are experiencing the same issues.