I'm still relatively new to rooting, so please forgive my lack of knowledge of terminology and such. I decided to give MIUI a try and flashed it on my phone. It was buggy, but not anything too crazy. Two nights ago, I flashed the newest update for it and ever since, the vibration when I touched the soft keys and when I entered my unlock pattern has gotten significantly weak. I went into the settings and changed the vibration level to strong but it did nothing. It was really bothering me, so I did a data wipe and flashed the latest build of AOKP. The vibration is still weak when I touch the soft keys and unlock pattern. I also have the stock ICS lock screen set up too, but when I slide the ring to unlock the phone, the vibration is normal again. I went into the device settings and changed the vibrations settings, but that didn't do anything either. I did a data wipe, wiped the dalvik cache, formatted the system and reinstalled the ROM, yet it's still the same. Is there a way to fix this? Sorry for being so long winded, I hope it made sense lol Thank you for any help
Did you drop the phone or cause any other physical damage to the phone? Because any control over the vibration would be reset after installing a new rom/wiping data.
Sent from my Galaxy Nexus using Tapatalk 2
AyyEmBee said:
I'm still relatively new to rooting, so please forgive my lack of knowledge of terminology and such. I decided to give MIUI a try and flashed it on my phone. It was buggy, but not anything too crazy. Two nights ago, I flashed the newest update for it and ever since, the vibration when I touched the soft keys and when I entered my unlock pattern has gotten significantly weak. I went into the settings and changed the vibration level to strong but it did nothing. It was really bothering me, so I did a data wipe and flashed the latest build of AOKP. The vibration is still weak when I touch the soft keys and unlock pattern. I also have the stock ICS lock screen set up too, but when I slide the ring to unlock the phone, the vibration is normal again. I went into the device settings and changed the vibrations settings, but that didn't do anything either. I did a data wipe, wiped the dalvik cache, formatted the system and reinstalled the ROM, yet it's still the same. Is there a way to fix this? Sorry for being so long winded, I hope it made sense lol Thank you for any help
Click to expand...
Click to collapse
Probably because of the kernel. That's my best guess. Flash trinity kernel and see how the vibration is for that one.
did you flash miui.us or miuiandroid? have you tried to flash any different roms since this issue started to see if its a rom issue or hardware issue?
theking_13 said:
Did you drop the phone or cause any other physical damage to the phone? Because any control over the vibration would be reset after installing a new rom/wiping data.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
No I didn't drop the phone. Held it in my hand the whole time I flashed MIUI
sd0070 said:
did you flash miui.us or miuiandroid? have you tried to flash any different roms since this issue started to see if its a rom issue or hardware issue?
Click to expand...
Click to collapse
I flashed miui.us, but I thought the faint vibration was a result of the miui update so I wiped and flashed AOKP 39. I still have the faint vibration when I touch the soft keys or enter my unlock pattern. However, for everything else it vibrates normal.
If you haven't dropped your phone, then probably it's the kernel. Haptic Feedback sometimes lessens on certain kernels. Try flashing another one.
I flashed Trinity kernel with 1536MHz CPU And 512MHz GPU clock. I wasn't sure which one to pick so I just chose the one at the top of the list. Anyway, since doing so I can't change any settings under the device options, except for 'color hack presets' Everything else is grayed out and I can't select them. Is there something I missed or should've done? I didn't wipe data or the dalvik cache, because I read that it wasn't necessary.
I think Trinity is not compatible with MIUI, which follows CM team very closely.
Sent from my i9250
bk201doesntexist said:
I think Trinity is not compatible with MIUI, which follows CM team very closely.
Sent from my i9250
Click to expand...
Click to collapse
I couldn't deal with MIUI anymore, so I flashed aokp b39.
Related
This is my first time posting. I know how annoying reposts are, so I tried to find if anyone else had the same problems I have. Unable to find an answer, I seek a solution to my strange problem...
I flashed CM7 three days ago. Before flashing, I did a full factory reset, wiped cache, etc. I also performed a backup of rom, which was at the time CM6. Everything worked without a hitch for these past three days. I installed new programs, really enjoyed the new features. However, today, the screen suddenly became unresponsive.
It acts as though I am long-pressing something when I am not. It will not register even hard taps and when I try to hit the home key it brings up the most recent apps list as though I long-pressed. I have reset, but it keeps doing this. When I try to use an app where scrolling is required, it bounces back to the spot I started scrolling. Very frustrating. Any solutions?
At first I thought it was from installing swype beta, but after removing it completely, resetting, and reflashing, the screen continues to act up.
Flash your backup and see if you still have the same problem
Sent from my HTC Vision using XDA Premium App
Spastic909 said:
Flash your backup and see if you still have the same problem
Sent from my HTC Vision using XDA Premium App
Click to expand...
Click to collapse
Hey thanks for your suggestion. I've tried it but the screen problem continues. I even tried going back to the stock rom. Do you think it's a hardware issue?
Having the same problem using MexDroid for the G2...have to resort to the trackball half the time because the touchscreen doesn't work right or at all.
I reinstalled the ROM twice already and it keeps acting up at some random point after installing a few apps (none of which affect the touchscreen as far as I know). Tried clearing cache, dalvik cache, and fixing permissions...nothing. Happens regardless of overclock settings too.
magus57 said:
Having the same problem using MexDroid for the G2...have to resort to the trackball half the time because the touchscreen doesn't work right or at all.
I reinstalled the ROM twice already and it keeps acting up at some random point after installing a few apps (none of which affect the touchscreen as far as I know). Tried clearing cache, dalvik cache, and fixing permissions...nothing. Happens regardless of overclock settings too.
Click to expand...
Click to collapse
It's nice to know I'm not the only one with this problem... i.e. misery likes company... but I'm also sorry to hear that you have the problem, as well. There seems to be nothing that I can do at the moment. Since the phone is still under warranty, I guess I could just flash the original rom, factory reset, and send it back for a new one. I'd rather find a solution, though, in case it happens again.
wronskishin said:
It's nice to know I'm not the only one with this problem... i.e. misery likes company... but I'm also sorry to hear that you have the problem, as well. There seems to be nothing that I can do at the moment. Since the phone is still under warranty, I guess I could just flash the original rom, factory reset, and send it back for a new one. I'd rather find a solution, though, in case it happens again.
Click to expand...
Click to collapse
The weird thing is that it only happens sometimes...like, sometimes I'll get 100% accurate/responsive touchscreen use, while other times I can pinch all I want and never zoom in. I think it might have something to do with my lowering the screen density - right now I have it at 140, and earlier at 190, and it seems that when I have the stock 240 or the 190, I have better luck with the touchscreen than with at 140...but the usefulness of the lower screen density outweighs the better touchscreen for me.
magus57 said:
The weird thing is that it only happens sometimes...like, sometimes I'll get 100% accurate/responsive touchscreen use, while other times I can pinch all I want and never zoom in. I think it might have something to do with my lowering the screen density - right now I have it at 140, and earlier at 190, and it seems that when I have the stock 240 or the 190, I have better luck with the touchscreen than with at 140...but the usefulness of the lower screen density outweighs the better touchscreen for me.
Click to expand...
Click to collapse
How do you change the screen density?
I apologize if there is any easy fix for this or if there's already a thread, but I just recently started having this issue for about a week. Sometimes, when I turn on the screen it will quickly light up to the lock screen, but then turn blank right after; before I even get a chance to unlock the phone. The capacative buttons will completely stay light up and when I press them they vibrate so I assume the screen is still active.
Is this a common issue and is there an easy fix? I'm running the latest CM7 nightly build 258. I don't think that's the issue though because I just upgraded it today and before I hadn't upgraded the Nighly Build ROM in a couple weeks. I upgraded it today just to see if there was something wrong with that build.
Has anyone else experienced this?
Restore your previous ROM save
graymonkey44 said:
I apologize if there is any easy fix for this or if there's already a thread, but I just recently started having this issue for about a week. Sometimes, when I turn on the screen it will quickly light up to the lock screen, but then turn blank right after; before I even get a chance to unlock the phone. The capacative buttons will completely stay light up and when I press them they vibrate so I assume the screen is still active.
Is this a common issue and is there an easy fix? I'm running the latest CM7 nightly build 258. I don't think that's the issue though because I just upgraded it today and before I hadn't upgraded the Nighly Build ROM in a couple weeks. I upgraded it today just to see if there was something wrong with that build.
Has anyone else experienced this?
Click to expand...
Click to collapse
Are you using a custom kernel. If so are you under / overclocking or over / undervolting?
Nope. I'm running whatever kernel comes with the ROM and no undervolting or overclocking either.
Anyone....?
Have you done a restore?
I would try wiping dalvik-cache and the cache partition. If that dosent work i would wipe everything and do a fresh install of a different rom to determine weather it is rom related or hardware related.
Hi everyone,
I've looked for a solution all over the net, but seems like no one had this problem before (guess i'm a special girl...):
The vibrate feedback when touching the screen just stopped working, in spite of the settings under "settings -> sounds -> vibrate on touch".
It started after an update to AOKP rom - milestone 5 (based on ICS 4.0.4) + Franco kernel nightly r151, but effects all the other roms. Maybe one untouched system file damaged.
I've tried everything: restore from previous nandroid backup, another rom (CM9), another kernel, another launcher, I even wiped everything and flashed new and clean rom-stock from google developers' page. And yet - no vibrate feedback.
The wired thing is that the haptic feedback is working in few specific applications, like the build-in ICS keyboard and the dialer Dialer-One, so it probably not some hardware failure.
All this time there are five softkeys that still have haptic feedback: the buttons of the nav-bar, the button that opens the applications drawer and the google-search widget.
I've tried using "KickBack" instead, but it's too aggressive and very uncomfortable.
PLEASE, PLEASE - Help me!
Same thing happened to me. I had the exact same setup and the haptic feedback went away after I flashed the kernel. Since I've had lots of issues when trying custom kernels, I just restored a nandroid and went back to the kernel included with aokp.
Sent from my Galaxy Nexus using XDA
Restore fixed my issue, so I'm not sure exactly what to tell you.
Sent from my Galaxy Nexus using XDA
taappel said:
Restore fixed my issue, so I'm not sure exactly what to tell you.
Click to expand...
Click to collapse
I've seen some ppl's msgs that even simple reboot fixed their vibrate problem.
Didn't work for me, unfortunately
Some kernels have haptic adjustment, see pic for kernel does.
I'm running Franco 152 and mines fine.
I know trinity kernels lower it
Sent from my Galaxy Nexus using XDA
Sveke said:
Some kernels have haptic adjustment, see pic for kernel does.
I'm running Franco 152 and mines fine.
I know trinity kernels lower it
Sent from my Galaxy Nexus using XDA
Click to expand...
Click to collapse
I'm also using Franco kernel, but I don't think this is the problem because i've tried some other kernels and none of them fixed my haptic.
Hi TaliKa
I've just had this problem myself but it happens long after I flashed aokp m5 + franco r152 (too) so I'm not exactly sure what caused it. However after I went to clear my cache and dalvik cache, everything seems fine again.
nich0145 said:
Hi TaliKa
I've just had this problem myself but it happens long after I flashed aokp m5 + franco r152 (too) so I'm not exactly sure what caused it. However after I went to clear my cache and dalvik cache, everything seems fine again.
Click to expand...
Click to collapse
Thanks guys, but as I wrote in the first msg, those actions didn't help.
Is there any pro here who can offer a profound solution that I didn't tried before?
Which system file responsible for the haptic feedback?
Guess I'll have to stuck without haptic feedback...
Sveke said:
Some kernels have haptic adjustment, see pic for kernel does.
I'm running Franco 152 and mines fine.
I know trinity kernels lower it
Click to expand...
Click to collapse
How can I adjust the haptic feedback feature in Trinity kernel?
+1
just wanted to say...exactly the same thing happened to me (started with aokp milestone 5 and vibration gone afterwards...)
im trying several things to get it back...i use it alot (at work and most of the time..its on vibrate)
hopefully we'll find a solution
Yeah this just happened to me too. It was working fine for awhile on AOKP and then all of a sudden it stopped. No idea what happened exactly. I tried whiping everything and restoring CM9 but that didn't work either. I thought maybe hardware but the phone vibrated on boot so it isn't that. Hopefully we find a fix...
takomar said:
+1
just wanted to say...exactly the same thing happened to me (started with aokp milestone 5 and vibration gone afterwards...)
im trying several things to get it back...i use it alot (at work and most of the time..its on vibrate)
hopefully we'll find a solution
Click to expand...
Click to collapse
Dacian said:
Yeah this just happened to me too. It was working fine for awhile on AOKP and then all of a sudden it stopped. No idea what happened exactly. I tried whiping everything and restoring CM9 but that didn't work either. I thought maybe hardware but the phone vibrated on boot so it isn't that. Hopefully we find a fix...
Click to expand...
Click to collapse
unfortunately I didn't get any solution yet. Realy depressing.
I promise to update about any progress, and hope you'll both do the same...
Just don't give up! it isn't hardware thing, so there must be solution somewhere.
TaliKa said:
unfortunately I didn't get any solution yet. Realy depressing.
I promise to update about any progress, and hope you'll both do the same...
Just don't give up! it isn't hardware thing, so there must be solution somewhere.
Click to expand...
Click to collapse
im starting to believe its a hardware issue (well at least for me) i mean i dont even get a vibration upon booting or turning off the phone...and i even went back to full stock...same thing
maybe it might have been some software issue that led to the overburning of the motor(doubt that though)
what is weird though is that the same scenario happened to us so im lost...
maybe i should start talking to samsung for my replacement
meanwhile...im very open to suggestions that might help my case
hope we find something soon...u guys, does it vibrate at all?when u turn on ur phone?turn off? unlock ?
takomar said:
hope we find something soon...u guys, does it vibrate at all?when u turn on ur phone?turn off? unlock ?
Click to expand...
Click to collapse
Yes, it vibrates at boot and also when using application with it's own vibrate settings, like "dialer one" for example.
Did you try using KickBack just to check the hardware?
if it's some hardware issue, maybe you can apply to your warranty supplier about that, just flash stock rom and relock your device before.
TaliKa said:
Yes, it vibrates at boot and also when using application with it's own vibrate settings, like "dialer one" for example.
Did you try using KickBack just to check the hardware?
if it's some hardware issue, maybe you can apply to your warranty supplier about that, just flash stock rom and relock your device before.
Click to expand...
Click to collapse
thats what im gonna do i guess...such a sad day...
i couldnt find KickBack, its not available in my accessibility menu nor in my market (i live in France)
i tried googling an apk but nothing for android 4.0
do you have a link for it?
takomar said:
thats what im gonna do i guess...such a sad day...
i couldnt find KickBack, its not available in my accessibility menu nor in my market (i live in France)
i tried googling an apk but nothing for android 4.0
do you have a link for it?
Click to expand...
Click to collapse
I couldn't find it in play store either, but i download it from here:
http://code.google.com/p/eyes-free/downloads/detail?name=kickback-v1.1.1.apk
works fine for me.
TaliKa said:
unfortunately I didn't get any solution yet. Realy depressing.
I promise to update about any progress, and hope you'll both do the same...
Just don't give up! it isn't hardware thing, so there must be solution somewhere.
Click to expand...
Click to collapse
Good to know. I went ahead and flashed the base image and it restored vibration, then I rooted and flashed AOKP again. It worked for about that day and then this morning when I woke up the vibration is gone again. I'm almost positive it's AOKP's software. I'll test another ROM (Android Revolution) for a day and see if it happens again.
Dacian said:
I'm almost positive it's AOKP's software. I'll test another ROM (Android Revolution) for a day and see if it happens again.
Click to expand...
Click to collapse
Which kernel do you use? and did you set the quite hours on?
If you succeed to restore the vibrate, i'd like to hear exact instructions how to do that, including links to download the boot image, if you plesae...
I have a problem. Yesterday, my phone started rebooting randomly. It's been happening almost every time I use the phone. I rooted and flashed the Calk E4GT 2 4.0.4 ROM about a month or so ago and have had no issues to speak of with it at all. I disabled the facial unlock because I noticed that the reboot would routinely happen with either I was trying to unlock or put the phone in standby or while I was trying to use it in some way.
In the past I had noticed similar behaviors randomly, but never became a persistent issue. Anyone have any ideas as to what the culprit could be?
If I need to reload...how do I go about doing that? Just pick a new ROM and flash from CM to start from scratch? If so, what's a good ROM that is 4.0.4 based to run with....Cyanogenmod?
willjr0k5 said:
I have a problem. Yesterday, my phone started rebooting randomly. It's been happening almost every time I use the phone. I rooted and flashed the Calk E4GT 2 4.0.4 ROM about a month or so ago and have had no issues to speak of with it at all. I disabled the facial unlock because I noticed that the reboot would routinely happen with either I was trying to unlock or put the phone in standby or while I was trying to use it in some way.
In the past I had noticed similar behaviors randomly, but never became a persistent issue. Anyone have any ideas as to what the culprit could be?
If I need to reload...how do I go about doing that? Just pick a new ROM and flash from CM to start from scratch? If so, what's a good ROM that is 4.0.4 based to run with....Cyanogenmod?
Click to expand...
Click to collapse
I'm having the same problem with the stock ff18 rooted...started out of the clear blue, can't place my finger on a consistent pattern. I'm gonna try installing a new kernel and see if that helps. If it works I'll let you know.
I disabled facial recognition security and cleared dalvik and normal cache with clockworkmod. My phone hasn't rebooted basically all day so far.
Something must have been stuck in the cache possibly that was causing issues.
Sent from my SPH-D710 using xda app-developers app
I rooted my galaxy s3 when I got it. sometimes the screen turns on and it is unresponsive to touch. As soon as I turn the screen off and back on with the lock button then it works fine. It does it randomly, for instance when somebody calls I can't answer it sometimes I have to hurry up and turn the screen off and back on so I can swipe to answer. Also when I'm playing a game like hill climb racing it works then after a minute it stops responding completely until I lock and unlock the screen. Everything was working fine until I rooted it. That is my only issue. Any suggestions? Thanks
Are you using a custom recovery? Wipe cache / dalvik cache? Are you using a custom rom that modifies the touch responsiveness / better accuracy when
pressing? Or better yet using a utility that changes governor settings of your phones CPU?
I have the same issue but it was only linked with governor CPU settings and UV OV / OC'ing the device.
Spark91 said:
Are you using a custom recovery? Wipe cache / dalvik cache? Are you using a custom rom that modifies the touch responsiveness / better accuracy when
pressing? Or better yet using a utility that changes governor settings of your phones CPU?
I have the same issue but it was only linked with governor CPU settings and UV OV / OC'ing the device.
Click to expand...
Click to collapse
No i am rooted only no rom or custom recovery just went back to stock and updated to 4.1.2 and re rooted and it still does the same thing.
It does it on stock rooted? Sounds like a hardware issue, especially since you unrooted and then rerooted and it still persists
Get an app that traces screen touch points to verify that the phone isnt detecting it at all
bump
CNexus said:
It does it on stock rooted? Sounds like a hardware issue, especially since you unrooted and then rerooted and it still persists
Get an app that traces screen touch points to verify that the phone isnt detecting it at all
Click to expand...
Click to collapse
Ok I turned the developer option on to track touchs and sure enough when the screen touch "freezes" it is still responsive to touch it's just way off. And even though it is way off I can get it right about where I originally am trying to touch, and it still does respond. Also when it freezes, there are two touch spots and they are way off of where I am touching..! Any Ideas???
I am having an issue on 4.1.2 TW; has happened on both TPR and JellyBomb... when phone boots or I wake it up with home or power button, lockscreen is in landscape mode and unresponsive to touch. Have to pull battery and wipe cache/Dalvik. Is this just from multiview?
Using CWM with KT Kernel (it has happened on various KT builds, including 14MAR, 27MAR and 11APR).
Anyone know what's causing this?
EDIT: well, as usual, a quick PM to Kennyglass123 has solved the issue! I forgot to uncheck the "ripple effect" and I'm using AOSP lockscreen. Nothing like feeling like a schmuck to start your weekend!
Mucho thanks to Kenny, as per usual...