I'm having trouble with haptic feedback lately. It comes and goes on everything eg., keyboard, home, menu, etc. buttons, lock screen (the feedback on unlock), etc. Anybody else experiencing these problems or have a possible solution for them?
I'm running CM 7.0.2 not overclocked or anything with this started happening.
Yea I noticed that too. Every so often my keyboard sporadically had no haptic. It drove me nuts cause it felt like I wasn't pressing the button. I just turned haptic off because of that issue and I actually prefer it this way now.
Sent from my cm7 Aria.
CallMeAria said:
Yea I noticed that too. Every so often my keyboard sporadically had no haptic. It drove me nuts cause it felt like I wasn't pressing the button. I just turned haptic off because of that issue and I actually prefer it this way now.
Sent from my cm7 Aria.
Click to expand...
Click to collapse
I might try that, does it help battery any, too?
okachowwa said:
I might try that, does it help battery any, too?
Click to expand...
Click to collapse
I'm sure in some very small way it does. But nothing I've been able to notice.
What i have noticed is I've found I can type faster now because I don't find myself waiting for that feedback. It may be a slight effect, but when typing long emails or text its noticeably faster for me having feedback off.
Sent from my cm7 Aria.
Related
OK this is freakin getting me mad! I was tolerating it for a while now, but every since I rooted my 3D Ive noticed huge keyboard lag / buggyness. Ill be typing then it starts freaking out, cant push certain letters, and other weird things.. Its not the ROM, I flashed wiped did everything I could possibly think of...I think?
You guys have any ideas? Hardware malfunction? Anyone else have this problem?
Update:: ok I think I noticed that it's happening when my Handcent pop ups a text when my screen is off. When typing normally, after unlocking the screen it seems to be working normal.... Could be a Handcent problem?
I am having issues also. I am stock but did temp root a couple times in the beginning. Mostly having issues in landscape. If swiping left past d it starts a new word. Also pressing a adds an e right after. Think mine might be screen related though.
Sent from my PG86100 using Tapatalk
Try turning off pop up on key press in settings. That might help a little.
Locked & Loaded
" Shooter on Deck "
I'm also having the same problem. I'm currently on SteelH's latest 2.1 using Smart Keyboard Pro, but I have tried several other roms/keyboards. It only does it when I'm typing in portrait mode with both thumbs. I think it may be my palm pressing on the capacitive buttons. Never happened on my EVO 4G because it was wider due to the aspect ratio of the screen. I guess I'll just have to start wearing finger-less gloves all day.
i love the htc keyboard, its auto correct is amazing and very rarely makes mistakes.
Yeah something is going on with mine too. Mainly my backup button and the letter P gives me problems. Not sure what I is but its starting to piss me off. When I try to delete I have to press the back button several times. It's annoying me.
Edit: so recalibrating did the trick. Now everything works great.
Sent from my Beastly EVO.. And did I mention it has 3D?
Just bought one but the haptic feedback vibrate when I press the touch key like home button is too weak and keyboard as well.
Any1 have the same issue? Any solution?
dragonthl said:
Just bought one but the haptic feedback vibrate when I press the touch key like home button is too weak and keyboard as well.
Any1 have the same issue? Any solution?
Click to expand...
Click to collapse
Mines exactly the same, prefer it to be softer
Sent from my XT910 using xda premium
As a usar of CM7 on the Atrix, I know it (and some other ROMs for other phones) have the setting of how long the haptic feedback lasts. Take note, what you are experiencing isn't a "week", feedback, it's a short one, as phones don't really have the possibility of calibration in it's strenght.
Maybe future ROMs for the razr will enable this configuration...
My vibrate is weak too, was going to go to Verizon today to see if it is defective.
When a text or call come in it seems more like a fast jiggle than a hard vibrate...also when typing I can barely feel a vibrate at all (it is turned on)
Is this normal?
I see lots complaining about this. Remember the more vibrations it's going to drain battery faster. Personally I never used haptic feedback till now, the softer vibration is nice to me.
Sent from my DROID RAZR using Tapatalk
I have a feeling thats just how it is cause mine is too. Keep in mind it's a skinny phone!
Mine vibrates well but is a fairly loud noise when vibrating.
Sent from my DROID RAZR using Tapatalk
Mine seems to have enough vibration feedback, but what doesn't work is the "screen press sound" I called Verizon tech support for the heck of it just to hear what they would say, and told me I could exchange it. Anyone else having this issue?
A lot of this thread has pertained to haptic feedback, but what about regular vibrate notifications when the phone is in silent mode. My phone barely does anything at all. Even when I'm holding it in my hand it barely vibrates compared to the GSII or iPhone.
Is this just the way it is, or is mine defective?
I've literally missed every single call, text, and email that have come in. This is the only thing keeping me from loving this phone, but I have to say, it's a dealbreaker if I can't have the phone in silent mode and still know when something comes in.
I actually prefer the amount of haptic feedback the RAZR provides. I didn't much care for the keyboard feedback, but that was fixed with SwiftKey. Like Bond32 said, less vibration, less battery usage!
\\Carved into this thread by my RAZR//
http://android-gz.com
Hey guys,
I've been having an issue with AOSP roms where my display will just stop updating, Previously on one of Neo's ROM, and currently on CounterShrike 2.1. The screen doesn't turn itself off; it stays on, but freezes and doesn't change. I have to hit the power button to turn the display off and on again and it will work normally again for awhile.
It actually still accepts input when the display freezes. If I press the home button while it's frozen, it will be back on the home screen when I hit the power button off and on. If I'm in a list and scroll with my finger while it's frozen, it will be further down in the list when I hit the power button off and on.
I thought this was related to the proximity sensor bug but when I follow shrike's guide in the FAQ for setting up Chad's proximity sensor calibration, it already is showing 'FAR' when I first load the app and I don't need to adjust the high threshold. I think the sensor is fine.
Anyone have any other tips I can try? Everything works fine under CleanROM DE but AOSP is so much faster I'd really like to try and nail the issue down.
Thanks!
EDIT: I've attached a logcat. Two times I recorded the timestamp when it frozen, around 00:45 and 01:11. But I don't really know what to be looking for in the log cat.
thank god I'm not alone with this! I get this crap with any aosp based rom. I sent logcats to a few and nobody can't figure it out yet. sometimes it freezes but the display bleeds and fades itself off simultaneously
This is just an accepted problem with any AOSP ROM.
If you read the OPs they all mention graphics issues.
If you have been following the JellyBean stuff, they can't get any graphics to work at all.
GrayTheWolf said:
This is just an accepted problem with any AOSP ROM.
If you read the OPs they all mention graphics issues.
If you have been following the JellyBean stuff, they can't get any graphics to work at all.
Click to expand...
Click to collapse
really? the OP's for rage and aokp mention nothing about freezing or graphics being glitchy
Maybe unrelated, but I have recently discovered that if my fingers are even the tiniest bit wet or sweaty, my touch screen completely freaks out and becomes impossible to use. The only way to fix it is to turn the screen off, and turn it back on.
a.mcdear said:
Maybe unrelated, but I have recently discovered that if my fingers are even the tiniest bit wet or sweaty, my touch screen completely freaks out and becomes impossible to use. The only way to fix it is to turn the screen off, and turn it back on.
Click to expand...
Click to collapse
That is probably not an AOSP issue.
GrayTheWolf said:
That is probably not an AOSP issue.
Click to expand...
Click to collapse
Yeah, I sorta agree.. but I never had noticed it until I started using CM9 ROMS.
Actually though, ever since the ICS leaks something has been a little off about the Rezound touch screen, even on Sense ROMs..
Sometimes when you swipe horizontally one direction quickly, it starts to go and then jerks back and actually scrolls the other way. Worked fine in GB for the 2 months I ever used it on this device....
a.mcdear said:
Maybe unrelated, but I have recently discovered that if my fingers are even the tiniest bit wet or sweaty, my touch screen completely freaks out and becomes impossible to use. The only way to fix it is to turn the screen off, and turn it back on.
Click to expand...
Click to collapse
This is true. I've stated this issue months back, sweat or a drop of liquid makes our screen act funny.
Sent from my ADR6425LVW using xda app-developers app
freezing occurs regardless, no moisture involved
What cpu governor and i/o scheduler are you using, do you know?
I've noticed freezes/slow response with either noop or deadline i/o scheduler. The powersave governor or turning cpu speed down too far can also cause freezing.
Occasional Graphical flickering in GUI elements does seem to be an issue with cm roms on multiple devices. I've had success turning on settings - developer - force gpu rendering to reduce flickering, YMMV.
Sent from my Rezound using Tapatalk 2
brenuga said:
What cpu governor and i/o scheduler are you using, do you know?
I've noticed freezes/slow response with either noop or deadline i/o scheduler. The powersave governor or turning cpu speed down too far can also cause freezing.
Occasional Graphical flickering in GUI elements does seem to be an issue with cm roms on multiple devices. I've had success turning on settings - developer - force gpu rendering to reduce flickering, YMMV.
Sent from my Rezound using Tapatalk 2
Click to expand...
Click to collapse
I forget exacts but it's with whatever is default when first flashed. the logcats at the time didn't mention anything about the CPU itself but graphics and HDMI errors with different invalid sound outputs as well
I experience this on multiple AOSP rom's! My phone was fine with sense based rom's but AOSP freezes. Sometimes it doesn't freeze at all, sometimes it's multiple intervals close together. This leads me to believe that it's something in the AOSP rom's themselves and not bad hardware, too many people have it with the same symptoms. Yet sense works fine.
Head scratcher (to put it very lightly).
least I'm not alone on this one. can't be hardware otherwise same issues on sense. anything that's not custom like the kernel or aosp works fine
I agree that I don't think it's necessarily the hardware itself. I think it could be some sort of threshold parameter HTC sets that differs just slightly from CM9 (threshold in what exactly I don't know), but that some of us have hardware that gets tripped up on it and others don't.
I initially thought it was an issue with the CPU (I've always been using the stock speed and governor after the initial flash) but it doesn't matter if I'm doing something really light or really intensive. It also doesn't seem to matter if I'm using stock apps vs. apps I've downloaded either.
I have 2 days off from work so I'm going to flash back to the latest CounterShrike and grab a log cat every single time it freezes up. At the end of the two days, I'll compare every single instance and try to find some correlating event.
Hopefully I'll find something!
God Damn this is really annoying!
Just had to get that of my chest. I'm reading threads and scrolling every few seconds and I just had a few lockups in a row. It's so frustrating because every other aspect of the Rom works perfectly! I don't understand. No amount of kernels I try fixes the issue. Volts don't affect it, cpu speed doesn't affect it. It's enough to make me want to go back to sense just to not have to deal with it. I don't want to
winston856 said:
God Damn this is really annoying!
Just had to get that of my chest. I'm reading threads and scrolling every few seconds and I just had a few lockups in a row. It's so frustrating because every other aspect of the Rom works perfectly! I don't understand. No amount of kernels I try fixes the issue. Volts don't affect it, cpu speed doesn't affect it. It's enough to make me want to go back to sense just to not have to deal with it. I don't want to
Click to expand...
Click to collapse
yeah sadly I went back to sense. dark tranquility gives me phenomenal battery until the mean time with functional video chat. it's not often but I would like to give up video calls for aosp. even with everything I want removed from sense it's still bloated memory wise.
good luck with getting logs. I sent to most devs here and they were stumped
Got a replacement phone coming in the morning, we'll see if I experience the same issue or not.
I tried all sorts of things, and it happens to me.
Went back to Sense with included dsb kernel.
Funky kernel has the issue on sense for me though.
Sent from my ADR6425LVW using Tapatalk 2
I didn't have much luck identifying something in the logs winston856 I'm considering getting a replacement as well. Let me know how you make out.
Hi, I used the search but I couldn't find anyone else having a problem like this so I'm asking right now!
I just got my HTC One 3 days ago and I absolutely love it! With that being said, I have noticed a strange click that seems to happen inside of the phone everyone and a while. I have tried turning off all the "button noises" in the settings and it still happens, it seems to happen often when I am typing but also happens at other times too. It's not terrible but it is a little annoying as I want my phone to be perfect
Oh and just to clarify it sometimes happen when I tough the screen and sometimes when I don't. So it nothing like a response noise.
Sorry for the block of text!
Thanks!
it is probably just the camera or autofocus sensor had the same problem on my old iphone and all the ones that i've had while changing out for a good one had the same sound
Danno27 said:
Hi, I used the search but I couldn't find anyone else having a problem like this so I'm asking right now!
I just got my HTC One 3 days ago and I absolutely love it! With that being said, I have noticed a strange click that seems to happen inside of the phone everyone and a while. I have tried turning off all the "button noises" in the settings and it still happens, it seems to happen often when I am typing but also happens at other times too. It's not terrible but it is a little annoying as I want my phone to be perfect
Oh and just to clarify it sometimes happen when I tough the screen and sometimes when I don't. So it nothing like a response noise.
Sorry for the block of text!
Thanks!
Click to expand...
Click to collapse
Under sound there is a option to enable touch sounds when making screen selection, it is a clicking type sound, do you have this enabled, drove me crazy for about the first 3 days
Sent from my HTC One using XDA Premium HD app
Mine has no clicking sound, but my autofocus is broken, going for a replacement today.
Mine has a weird click when the haptic feedback hits sometimes. I think it's just the vibrate motor kicking on.
Sent from my HTC One using xda premium
^^ I think it is the the vibration kicking in or something. I have turned off all screen tough sounds and everything but it still happens. Like I said, it's not a huge deal but just slightly annoying. I'm going to try turning the vibration on touch off.
hey all
loving the 1 year+ with the atrix, but a few problems still affecting me. On neutrino 3.02 is anyone is wondering.
1)most of the time, when i take calls, the screen turns off as normal due to the proximity sensor, but refuses to turn back on after i take the phone away from my ear. no amount of pressing any buttons, physical or capacitive, will turn it on, and a battery pull is required.
2) im pretty sure i've read that this is a manufacturing defect with the atrix, so please correct me if i'm wrong. sometimes the screen will randomly press buttons, even when my hands and the screen itself is dry.
any solutions to the above?
thanks in advance
AFAIK, no to both
andresrivas said:
AFAIK, no to both
Click to expand...
Click to collapse
so basically, the sensor is dead? hmm. will be a pain to replace, one because the warranty is out, and two because motorola no longer serves asia.
sidewinder_x5 said:
so basically, the sensor is dead? hmm. will be a pain to replace, one because the warranty is out, and two because motorola no longer serves asia.
Click to expand...
Click to collapse
I should have explayed a little longer..
As is stated in the forums, screen off after a call is a known bug of several roms (neutrino, cm9, cm10, atrics, etc, etc) I had it on cm7 stable and have it on cm7 latest nightly (pure cm7 both of them). In fact, the only rom I hadn't experienced this was on stock 2.3.6 with stock kernel.
As for the random press, I think it's hardware problem (the hardware is garbage) I experience it mostly on multitouch emulators, where you need to quickly press several spots... most of the time, a couple of second without touching the screen solves it
andresrivas said:
I should have explayed a little longer..
As is stated in the forums, screen off after a call is a known bug of several roms (neutrino, cm9, cm10, atrics, etc, etc) I had it on cm7 stable and have it on cm7 latest nightly (pure cm7 both of them). In fact, the only rom I hadn't experienced this was on stock 2.3.6 with stock kernel.
As for the random press, I think it's hardware problem (the hardware is garbage) I experience it mostly on multitouch emulators, where you need to quickly press several spots... most of the time, a couple of second without touching the screen solves it
Click to expand...
Click to collapse
Ah okay, i see. thanks for the clarification. its a shame the stock rom isn't any good for me then, otherwise i wouldn't be having this problem!
as for the screen, my experience is that it happens when the screen first turns on, no matter what app i'm using. doesn't happen when the screen is already on, which is interesting. i remember reading a thread which said that the digitizer wasn't properly attached for this phone, meaning that it's destined to go bad at some point. i'll have to see if i can find the thread again.
once again, thanks for the clarification!