hi all, is anyone finding that the soft keys arent as responsive over time. takes a few presses at times for an action to register and perform. anyone else noticed this? wonder if its a hardware or software problem.
for the record im using duttys v1.5.
thanks
Its not a hardware problem, I had a same problem with tlr3 rom. I fixed it by flashing an other rom.
You can try swiftblade latest rom. Its pretty neat and stable.
Related
Hey guys, haven't really seen much Telus rom representation on these forums, just curious if anyone can verify it's not just me having these problems with my handset.
Basically, landscape mode for SMS/Email is ****ered. It'll work fine the first time after a soft reset, but anytime after that the screen orientation will change, then the app will minimize to manilla (or the phone app sometimes) and revert back to portrait on it's own. This happens both with the hold-call-key method AND gyrator2. I'm fairly certain it's a rom issue (that's unlikely to get fixed, sadly, because it's outside of "normal use") but I figured I'd throw it out there and see if anyone else with a Telus HTC Diamond can tell me if theirs does the same thing.
Cheers
I've got a Telus Diamond as well, and yes, using landscape orientation is buggy at best. Gyrator 2 kinda works, but as you've mentioned in some apps when I change the orientation it'll kick me back to manilla.
Unless Telus/HTC issue some sort of official software or ROM upgrade - which seems unlikely - your best option is to flash the phone with a custom ROM like this one. I'm planning to do it myself once I work up the nerve and once I find the time I'll need to reinstall a bazillion programs.
hey yea i have a telus diamond as well, its started with my opera not wanting to rotate, and after trying Gsen and the rotatescreen app, same thing keeps happening. that juicy rom does look good.
hell yeah! didn't know 2.7 came out, i'm all over this. thanks
Update: Juicy 2.7 rocks, fixed my landscape problems and seems to be quicker for GPS locking.
I just got the HTC Touch pro, and I almost get it to perform at his best. I love it, but I have an issue than I've never been able to get fixed
Using the virtual keyboard or the sliding hardware keyboard to enter a URL in Opera Mobile is extremely slow, about 1 to 2 sec for each letter and if I type normally most of the letter will be missing, so I have no other choice than take 30 seconds to enter any URL.
I would be really happy to find an way to fix that issue, and I'm curious to know if anyone is experiencing the same problem
Thanks
Are you using a custom ROM?
Have you tried a hard reset?
No I have the default ROM who came with my HTC touch Pro ( from sprint by the way)
I'm a little bit reticent to do a hard reset, but if that's the only way I should probably try.
Hey guys, lately i've been really annoyed because i can't use any ICS rom properly, mainly because my MENU button is not working.
I got this app "ButtnRemapper" which reassigned my hardware keys to the one i wanted.
So i switched the home button to menu and it worked great on the Gingerbread ones, but on the ICS roms it would not work!
That's why i'm asking if there is any possibilites of porting software button as the Galaxy Nexus has.
bump le bump
Not meaning to be captain obvious, but why not consider getting your home button fixed? Flash your phone back to original state and no warranty problems there - and after some time you'll finally be able to fully enjoy your phone.
hi!
i'm using CM 7.2 nightlies on my cappy. from a while back, the search button started triggering by itself. at first very sporadically, and as time passes the problem happens with increasing frequency. all buttons work well when actually used. so,
1) is there a thread discussing this? i couldn't find it.
2) is there a way to fix this? maybe fine tuning sensitivity through software?
3) i'm planning to move to CM9 ICS soon. ICS doesn't need the physical search button, but it does respond to it anyway. is there a way to make CM9 ignore the search button? maybe a button remapper app or editing some config file?
thank you very much for your help!
3. Yes in cm9 just use root explorer and go to system/usr/keylayout/cypress-touchkey.kl. and open that file with text editor and delete the line that says search then save and exit and reboot. The search key will no longer fuction, I suffered from the same issue.
2. It is a hardware issue. It is caused when just small amounts of water get under the capactive button strip causing the buttons to activate randomly.
1. Yes there are multiple threads disscusing this issue lol.
Sent from my SGH-I897 using xda premium
hey, thank you!!! excellent answer with everything i needed! i'm embarrassed for not finding the thread though... :-S now i'll search for "cypress-touchkey.kl" and i'm sure i'll find the posts.
i won't work on this for some days or even weeks since i don't have the cappy with me, but now i can disable the button and fix the issue. thanks again!
That is excellent information, I was not aware of that. My search button used to energize itself all of the time but now that the phone is older it seems to have ceased.
My phone used to do that also. After I changed roms the problem went away for good.
Sent using XDA App
@jboneiii,
do you remember which rom had the problem and which fixed it?
i know that capacitive touch sensors require calibration, but most implementations self-calibrate. however it might be the case that in the cappy some form of calibration is programmed into the sensor IC during boot and then adjusting sensitivity manually by editing a config file might be an option. however this is entirely speculation on my part, i don't know how the cappy sensors work. on the other hand, if there is no IC calibration programming during boot i can't imagine how swapping roms could have any impact on the issue.
Capacitive buttons sensitivity can be tweaked in latest ICS ROMs/kernels. I disabled it on my phone after buttons becoming too sensitive.
So I started noticing lag on games with a virtual pad. As in, jump works fine if im standing in game for example, but im running and I try to jump, either it doesnt do it at all, or it does it with some lag.
So I downloaded a multitouch tester and pretty much confirmed that there's an issue there.
If I just touch with one finger at a time, it works fine. If I press with two fingers and keep them there moving them around and whatnot, it also works fine.
BUT, if I keep pressing with one finger and use the other one to do a fast light tap, half of the time it doesnt register it.
Im using the ROM posted here: http://forum.xda-developers.com/showthread.php?t=1583871
wich im finding to be great, but I thought of originally posting my issue there since I gather it is more likely to be caused by software and not hardware.. right? considering simple touch works completely fine.
Any ideas?
Ace supports only 2 fingers at a time. But i did not find any types of lags while using 2 fingers. But it wont work if u use 3 or more fingers at once.
REPLY
Hey I got 100% same issue too. On original cm7 nightly.
But I found out sometimes it works and sometime it doesn't seems to work. I think it's similar to the rounding bug.
Maybe it's the kernel problem. Just don't overclock and it will work well. Or, reboot your phone and wait for a night without touching it, and the problem is gone. However, the bug will occur again after you install an app or launch an app. This multi-touch bug always occur on cm7. If you don't want this problem you can use stock roms. But if you say touch making it lags, it doesn't make our phone lags or the game you play using this phone is a bit slow. Just the second finger is responding slowly if the first finger is pressed/touched on the screen.
And I've tested this bug using the dev tools in the cm7 rom. dev tools/pointer location. All of the stock rom doesn't have this bug except cm7. CM7 will not have this problem on the first few weeks since the first boot. hope it helps
It's a Ace Hardware issue. Nothing to do about it.
King of the mashed potatoes©
Getting a faster device is the only solution
I got transformed into a potato while writing this post..