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...
hello i recently flashed this version of cyanogen-mod on my Samsung s2 and am having an issue. First of all, i used a non-touch CWM but it was confirmed to work as long as you use super swipe, so i did that and it worked no problem. However the back-lighting on my buttons will not come on. It is not broken because it sometimes works but mostly does not. i am wondering if there is a fix or a setting i need to use to get it to work.
Thank you
heatpro said:
hello i recently flashed this version of cyanogen-mod on my Samsung s2 and am having an issue. First of all, i used a non-touch CWM but it was confirmed to work as long as you use super swipe, so i did that and it worked no problem. However the back-lighting on my buttons will not come on. It is not broken because it sometimes works but mostly does not. i am wondering if there is a fix or a setting i need to use to get it to work.
Thank you
Click to expand...
Click to collapse
have you tried "settings > advanced > sensors" and checking the backlight and notification settings?
yes I have tried it, it fixes the issue but once I lock the phone and then unlock it it does not work anymore.
heatpro said:
yes I have tried it, it fixes the issue but once I lock the phone and then unlock it it does not work anymore.
Click to expand...
Click to collapse
It's a known issue with any aosp builds such as cm or aokp. No one has gotten it to work consistently yet with ics or jb
Sent from my SAMSUNG-SGH-T989 using xda premium
yoft1 said:
It's a known issue with any aosp builds such as cm or aokp. No one has gotten it to work consistently yet with ics or jb
Sent from my SAMSUNG-SGH-T989 using xda premium
Click to expand...
Click to collapse
i think ill just re-flash to dark-side evolution. can you please explain to me what the MD5 keys mean since there are like a few download mirrors and i an not sure which one to get.
i am having this problem on every version or CM9 past RC2 and CM10 i really would like a fix
i looked into this a little and it seems that it's a problem from the moment you turn off the screen until the first hard light timeout afte the screen is turned back on
Apparently the bug is also in Miui and AOKP
NOOB HERE
Hi, I am using eugene373's newest PLANE JANE ICS ROM, the whole system seems to me is perfect, except the one issue about the touch keys backlight. Sometimes those four keys do not light up even I already unlock the screen, may have to wait for 15-30 seconds, then the backlight comes up. But sometime it works good. So I am just wondering is there any other this ROM users have same problem about this?
Its a little bug, everyone's got it. It'll probably be fixed soon.
Sent from my SGH-T989 using xda app-developers app
whatiznt said:
Its a little bug, everyone's got it. It'll probably be fixed soon.
Click to expand...
Click to collapse
Thanks for telling me that. I already had flashed the rom more than five times!! I thought that only because I installed something affect the lights.
PlainJane
Installed Rom.Everything seemed to work fine.But i could not get Talkatone working that what i use mostly.
Anyone else having this issue?
Ok so I've been using a few different versions of the CM10 ROM and I've noticed a new problem. On occasion, when I go to wake the device, it will not wake. The keys light up, but thats it, the screen doesn't come on. The only way to get it working again is to hold down the power button and wait till it restarts. It's happened twice so far, not too frequently but annoying none-the-less.
Is there something I can do to fix this?
screwregi said:
Ok so I've been using a few different versions of the CM10 ROM and I've noticed a new problem. On occasion, when I go to wake the device, it will not wake. The keys light up, but thats it, the screen doesn't come on. The only way to get it working again is to hold down the power button and wait till it restarts. It's happened twice so far, not too frequently but annoying none-the-less.
Is there something I can do to fix this?
Click to expand...
Click to collapse
I thought you said you noticed a new problem...
Sent from my LG-P930 using xda premium
lordcheeto03 said:
I thought you said you noticed a new problem...
Sent from my LG-P930 using xda premium
Click to expand...
Click to collapse
I meant new to me! Though I looked around like crazy, cant find anything on this problem so I figured it was unique to my device.
screwregi said:
I meant new to me! Though I looked around like crazy, cant find anything on this problem so I figured it was unique to my device.
Click to expand...
Click to collapse
Nah, I'm mostly just giving you a hard time The CM10 nightly thread has gotten to be a beast to look through; seriously though... that problem is pretty old, and like you said; the only way to get around it is to hold power or do a battery pull. Just wait until you have an alarm go off in the morning and you can't turn it off!
Try the 2013 nightly, it does not appear to have this issue
Nz
notzippy said:
Try the 2013 nightly, it does not appear to have this issue
Nz
Click to expand...
Click to collapse
Maybe not, but it probably has other issues instead!
I can confirm that these issues still exist in the NIGHTLY (1/20) version. Just had it happen. Doesn't appear to be quite as frequent, but definitely still happening. I think it MAY have something to do with notifications, not sure though. Seems to often happen when I get a notification, I'll go turn it on and it wont wake from sleep.
screwregi said:
I can confirm that these issues still exist in the NIGHTLY (1/20) version. Just had it happen. Doesn't appear to be quite as frequent, but definitely still happening. I think it MAY have something to do with notifications, not sure though. Seems to often happen when I get a notification, I'll go turn it on and it wont wake from sleep.
Click to expand...
Click to collapse
Just saying; but there's already a thread for discussing CM10...
OK, I have Odin'ed twice, and wiped the poor little phone so many times I'm gonna need to use Desitin. It does not matter, I have pretty much tried every 4.2.2 ROM out there, and although I have had one or two that I could initially get bluetooth to turn on, even those would fail to do so after a few hours. I've tried rebooting with it on, rebooting with it off, does not matter. The last few AOKP and CM nightlies as well as Jedi, it will not even turn on. I have seen a few folks state somewhat similar issues, but I am getting that it is not pervasive for the community. Does anybody have any ideas as to a fix, or, even any ideas as to what causes it, so maybe I can play around with whatever and try myself? Or, best case-scenario, did anybody have the issue on ROM ABC and discover that by switching to ROM XYZ it was fixed? I'm not updating my sig because it changes multiple times a day anyway, but I am back to CWM 6.0.2.7 from TWRP if that variable matters at all. Same situation whether on stock, Cerux or ASD kernel.TIA...
wbexpress said:
OK, I have Odin'ed twice, and wiped the poor little phone so many times I'm gonna need to use Desitin. It does not matter, I have pretty much tried every 4.2.2 ROM out there, and although I have had one or two that I could initially get bluetooth to turn on, even those would fail to do so after a few hours. I've tried rebooting with it on, rebooting with it off, does not matter. The last few AOKP and CM nightlies as well as Jedi, it will not even turn on. I have seen a few folks state somewhat similar issues, but I am getting that it is not pervasive for the community. Does anybody have any ideas as to a fix, or, even any ideas as to what causes it, so maybe I can play around with whatever and try myself? Or, best case-scenario, did anybody have the issue on ROM ABC and discover that by switching to ROM XYZ it was fixed? I'm not updating my sig because it changes multiple times a day anyway, but I am back to CWM 6.0.2.7 from TWRP if that variable matters at all. Same situation whether on stock, Cerux or ASD kernel.TIA...
Click to expand...
Click to collapse
it turns on with pac 20.0 not sure if it stays on though. I'm on the latest twrp. full wiped, adsk and nos script. give that a try?
wbexpress said:
OK, I have Odin'ed twice, and wiped the poor little phone so many times I'm gonna need to use Desitin. It does not matter, I have pretty much tried every 4.2.2 ROM out there, and although I have had one or two that I could initially get bluetooth to turn on, even those would fail to do so after a few hours. I've tried rebooting with it on, rebooting with it off, does not matter. The last few AOKP and CM nightlies as well as Jedi, it will not even turn on. I have seen a few folks state somewhat similar issues, but I am getting that it is not pervasive for the community. Does anybody have any ideas as to a fix, or, even any ideas as to what causes it, so maybe I can play around with whatever and try myself? Or, best case-scenario, did anybody have the issue on ROM ABC and discover that by switching to ROM XYZ it was fixed? I'm not updating my sig because it changes multiple times a day anyway, but I am back to CWM 6.0.2.7 from TWRP if that variable matters at all. Same situation whether on stock, Cerux or ASD kernel.TIA...
Click to expand...
Click to collapse
I works on the 2/26/13 Nightly of CM10.1. You wanna try and clean flash it? If it doesn't work then it's just a problem with your phone hardware instead of the software. Might be a buddy bluetooth adapter or such.
zxstyle07 said:
it turns on with pac 20.0 not sure if it stays on though. I'm on the latest twrp. full wiped, adsk and nos script. give that a try?
Click to expand...
Click to collapse
Fingers crossed, so far so good. I reinstalled Rootbox which is awesome. I changed from CWM back to TWRP and also installed Cerux 1.42 which in the thread made mention of the bluetooth issue being fixed, and being kernel, not ROM related. I am using crossbreeder which makes things crazy fast. I saw the "nos script" in some thread but couldn't find it with a Google search. Do you have a link for it and what exactly does it do?
Edit: Crap. it went away. Oh well, back to 4.1. Hellybean it is. I just don't get it. BT works fine on any 4.1 or ICS ROM. Only thing with 4.1 is music skips in my music player but I can live with that, I can't live with no BT. Thanks for your help. Maybe when source drops it will be all good.
Does ithe bt button turn on then instantly off when you press it? This happened to me and i went into recovery and wipe dalv n cache.. Worked perfectly after
Or i saw this post. Not sure if itll help
http://forum.xda-developers.com/showthread.php?t=2174100
Sent from my SGH-T989 using xda premium
joeyrey said:
Does ithe bt button turn on then instantly off when you press it? This happened to me and i went into recovery and wipe dalv n cache.. Worked perfectly after
Or i saw this post. Not sure if itll help
http://forum.xda-developers.com/showthread.php?t=2174100
Sent from my SGH-T989 using xda premium
Click to expand...
Click to collapse
Yup, this helped for my JB-MR build 4!
no more having to reboot to enable bluetooth
wbexpress said:
Fingers crossed, so far so good. I reinstalled Rootbox which is awesome. I changed from CWM back to TWRP and also installed Cerux 1.42 which in the thread made mention of the bluetooth issue being fixed, and being kernel, not ROM related. I am using crossbreeder which makes things crazy fast. I saw the "nos script" in some thread but couldn't find it with a Google search. Do you have a link for it and what exactly does it do?
Edit: Crap. it went away. Oh well, back to 4.1. Hellybean it is. I just don't get it. BT works fine on any 4.1 or ICS ROM. Only thing with 4.1 is music skips in my music player but I can live with that, I can't live with no BT. Thanks for your help. Maybe when source drops it will be all good.
Click to expand...
Click to collapse
http:// http://forum.xda-developers.com/showthread.php?t=2158329
joeyrey said:
Does ithe bt button turn on then instantly off when you press it? This happened to me and i went into recovery and wipe dalv n cache.. Worked perfectly after
Or i saw this post. Not sure if itll help
http://forum.xda-developers.com/showthread.php?t=2174100
Sent from my SGH-T989 using xda premium
Click to expand...
Click to collapse
Well, what seems to happen is it is fine for 15-30 minutes after I've freshly installed the ROM, then it just turns off. When I then try to turn it back on it hangs at "turning on" and then goes back to off. At that point when I click "turn on", it doesn't even move. I'm a gonna try the fix, nothing to lose at this point...
Nuts. It fast moves to on and immediately goes back to off. White flag, thanks to all.
Apply the fix and delete all you devices then try turning it on and off with nothing on it...if it works then add devices one by one...if you have devices married to it the patch might not work also I think my computer dongle was the culprit
Sent from my SAMSUNG-SGH-T989 using xda premium
After a reboot I'm back to the same problem
Sent from my SAMSUNG-SGH-T989 using xda premium
djtheraven said:
After a reboot I'm back to the same problem
Sent from my SAMSUNG-SGH-T989 using xda premium
Click to expand...
Click to collapse
Yeah, how about that. I can't see that it's hardware-related, it's perfect on 4.1.
wbexpress said:
Yeah, how about that. I can't see that it's hardware-related, it's perfect on 4.1.
Click to expand...
Click to collapse
Your exactly right...
Sent from my SAMSUNG-SGH-T989 using xda premium
djtheraven said:
After a reboot I'm back to the same problem
Sent from my SAMSUNG-SGH-T989 using xda premium
Click to expand...
Click to collapse
If you ever figure it out, please put something here. I keep looking every so often, I have to believe enough folks are having the issue that eventually someone is gonna fix it. Thanks...
wbexpress said:
If you ever figure it out, please put something here. I keep looking every so often, I have to believe enough folks are having the issue that eventually someone is gonna fix it. Thanks...
Click to expand...
Click to collapse
I'm posting to a couple of devs hope they can get it...the problem was people were commenting that it worked when they had no Bluetooth device hooked up...if you uninstall all devices then bt will toggle on and off...so they thought it was working when it wasn't...
Sent from my SAMSUNG-SGH-T989 using xda premium
bluetooth issues
djtheraven said:
I'm posting to a couple of devs hope they can get it...the problem was people were commenting that it worked when they had no Bluetooth device hooked up...if you uninstall all devices then bt will toggle on and off...so they thought it was working when it wasn't...
Sent from my SAMSUNG-SGH-T989 using xda premium
Click to expand...
Click to collapse
Has anyone had any luck with this? I've tried various combinations of different 4.2.2 roms and kernels and have the same issues described in this thread with all of them.
Not a perfect answer...
RandyToe said:
Has anyone had any luck with this? I've tried various combinations of different 4.2.2 roms and kernels and have the same issues described in this thread with all of them.
Click to expand...
Click to collapse
I found one thing that at least gets it working again without rebooting is to activate airplane mode. Its faster than rebooting. Wish I had a better answer...