Develop Bugs

[Q] No haptic feedback ("vibrate on touch") in Galaxy Nexus

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...

Phone turns on my flash light whenever i hit the power button !

There's this strange problem my phone has where the flashlight is turned on whenever i hit the power button to turn off my screen It has been working fine on android revolution rom for the past 3 months then this problem started occurring just this morning. Going to the official htc flashlight app to adjust the brightness works but it cannot turn off the flashlight unless i initiate a shutdown. anyone has any idea how i can solve this problem ? is this a hardware or software issue ?

24inchsub said:
...is this a hardware or software issue ?
Click to expand...
Click to collapse
If it worked before you tried a new ROM it's bound to be s/w. Is Tasker baked in to the ROM or did you install it? Some third party app is triggering Flashlight to launch when you press the power button. You might want to check the dev who built the ROM's thread or ping him or her.

In aokp there's a turn flash light on by hitting power option in the settings have a look at your roms settings.
Sent from my Xperia Play using xda premium

this rom isn't exactly new its a 3 month old build and has nv given me any sort of problems before till this strange problem started occurring. Is there any way to disable the flashlight for good so it doesn't keep turning on and draining my battery ?

24inchsub said:
this rom isn't exactly new its a 3 month old build and has nv given me any sort of problems before till this strange problem started occurring. Is there any way to disable the flashlight for good so it doesn't keep turning on and draining my battery ?
Click to expand...
Click to collapse
If it were me, I'd want to figure the problem out as what's causing it may not be limited to Flashlight (EG: other things are being turned off or on and you just don't know it). I you want to disable it, go in to Apps>All>flashlight and clear data, force stop, and then hit disable.

Do you have EQS? If so, try to turn flashlight on then off again from the EQS tab itself.

BarryH_GEG said:
If it were me, I'd want to figure the problem out as what's causing it may not be limited to Flashlight (EG: other things are being turned off or on and you just don't know it). I you want to disable it, go in to Apps>All>flashlight and clear data, force stop, and then hit disable.
Click to expand...
Click to collapse
Already tried disabling flash light it doesn't work
omar302 said:
Do you have EQS? If so, try to turn flashlight on then off again from the EQS tab itself.
Click to expand...
Click to collapse
What is a EQS ?

Extended Quick Shortcuts. The ones that show up in a seperate tab in the notifications panel.

omar302 said:
Extended Quick Shortcuts. The ones that show up in a seperate tab in the notifications panel.
Click to expand...
Click to collapse
i do have more quickly panel installed i aready uninstalled it and problem still persists. Ima try to flash a new rom and kernel over the phone see if it helps

Have you solved this? I am having the same problem. Wondering if it is a little virus or something.

Try freezing the flashlight app
Sent from my HTC One X powered by ARHD

its software related.
i m using viper rom and it has the option to trigger flashlight when power button is pressed (while screen off) . ive enabled it. so yea, you can disable it as well.
so check that.

Well if you're on viper it's an option for flashlight.. You can change in venom tweaks...
Sent from my HTC One X using xda app-developers app

Cashreedhar said:
Well if you're on viper it's an option for flashlight.. You can change in venom tweaks...
Sent from my HTC One X using xda app-developers app
Click to expand...
Click to collapse
:thumbup:
Sent from my HTC One X using xda premium

[Q] Random Reboot

Hi,
History:
I have a problem with my Nexus. It randomly reboots. Nothing seems to help.
It started after a few months after I was rooted on CyanogenMod 10.0. In 3 days, it quickly escalated to a reboot every 10 minutes on average.
A factory reset (without user apps installed on it) on CynogenMod reduced the frequency (every hour?), but didn't eliminate it.
Unrooting to stock Jellybean 4.1.2 seemed fine only in the first week. The problem came back afterwards, and updating to JB 4.2.1 didn't help.
Now, 2 months on stock ROM, I get even more random times. Sometimes it is 2 times a day, sometimes once a week.
Just before it:
I get a metallic screeching noise for 1-2 seconds, and immediately following that, device turns off with a "pang". Although these days I HAVE had situations that the sound came for up to 3 seconds (and the screen freezes), but the phone worked normally afterwards.
What happens:
It randomly reboots. The rebooting is at irregular intervals, whatever i was doing on it (even when not using it).
What happens after:
It takes much, much longer to startup again. It can get stuck at the "Google" logo screen for up to 5min. It doesn't take this long to reboot if I shut it down myself.
Any ideas? What causes this? Is it software or hardware?
Can I even send it for warranty if I cannot reproduce the problem?
I don't want to send it to warranty if I don't have to. I don't want to loose my phone for I don't know how long.

Hi, what's your eMMC version? Maybe buggy memory, try looking at other threads.
Отправлено с моего Galaxy Nexus через Tapatalk

Have you tried different batteries?
GeeNex | Carbon nightlies | Rubiks

I'm new to this eMMC thing, but according to an app my eMMC Type is V3U00M. To check whether it is buggy or not it needs root, which I don't currently have. If it IS buggy, I don't have a choice but to bring it for warranty right?
No, I have not tried to changed batteries. I don't have other batteries. But can the problem really lie with the battery? Btw, my phone is less than 8 months old.

Djalaal said:
I'm new to this eMMC thing, but according to an app my eMMC Type is V3U00M. To check whether it is buggy or not it needs root, which I don't currently have. If it IS buggy, I don't have a choice but to bring it for warranty right?
No, I have not tried to changed batteries. I don't have other batteries. But can the problem really lie with the battery? Btw, my phone is less than 8 months old.
Click to expand...
Click to collapse
Well, try waranty, that chip is buggy. Mine too )) but I just live with it using lagfix app and discard mount options, but things requires root. Good luck.

krugdenis said:
Well, try waranty, that chip is buggy. Mine too )) but I just live with it using lagfix app and discard mount options, but things requires root. Good luck.
Click to expand...
Click to collapse
Well, I am planning to root again. I want to switch back to CyanogenMod 10.1. Lagfix app isn't needed if you can use -discard mount option right? How to use either, if let's say I'm on CyanogenMod. This is also the first time I hear of lagfix and discard mount... :/
Btw, the app i used to check my eMMC Type said that my chip is ok. No brickbug. Are you sure it's buggy?

http://code.google.com/p/android/issues/detail?id=39154
Отправлено с моего Galaxy Nexus через Tapatalk

I might be wrong here, but from what I've read at the link and other xda posts (http://forum.xda-developers.com/showthread.php?t=2029246), the V3U00M chip is not buggy (in the sense that it's stable for rooting and using the -discard command), but it does give slowdowns. I do have horrible slowdowns, so thanks for that solution I didn't know existed. However, this doesn't solve my random reboot problem at all...

No one else got any solid way to find out the source of the problem?

BUMP

Djalaal said:
Hi,
History:
I have a problem with my Nexus. It randomly reboots. Nothing seems to help.
It started after a few months after I was rooted on CyanogenMod 10.0. In 3 days, it quickly escalated to a reboot every 10 minutes on average.
A factory reset (without user apps installed on it) on CynogenMod reduced the frequency (every hour?), but didn't eliminate it.
Unrooting to stock Jellybean 4.1.2 seemed fine only in the first week. The problem came back afterwards, and updating to JB 4.2.1 didn't help.
Now, 2 months on stock ROM, I get even more random times. Sometimes it is 2 times a day, sometimes once a week.
Just before it:
I get a metallic screeching noise for 1-2 seconds, and immediately following that, device turns off with a "pang". Although these days I HAVE had situations that the sound came for up to 3 seconds (and the screen freezes), but the phone worked normally afterwards.
What happens:
It randomly reboots. The rebooting is at irregular intervals, whatever i was doing on it (even when not using it).
What happens after:
It takes much, much longer to startup again. It can get stuck at the "Google" logo screen for up to 5min. It doesn't take this long to reboot if I shut it down myself.
Any ideas? What causes this? Is it software or hardware?
Can I even send it for warranty if I cannot reproduce the problem?
I don't want to send it to warranty if I don't have to. I don't want to loose my phone for I don't know how long.
Click to expand...
Click to collapse
Same as you man...
I'm seriously considering throwing my phone to the garbage. I don't like iPhones, but google is really pushing me into it with this crappy piece of phone. Is so frustrating to have these rebooting issues, I've tried everything, from wipe to factory reset, back to stock, flash custom ROMS and KERNELS, turning location access off, uninstalling all apps/widgets that might interfere, and every single "solution" it's out there, and STILL I'M HAVING THESE DAMN REBOOTS!
Now it's even worse, I can't even transfer files to my phone anymore because, guess what... IT REBOOTS! everytime I transfer ANY KIND of file.
The only thing that seems to work for a while is reformatting and start from scratch. I've done that like 3 times already. But still after a few weeks the issue reapears... i'm really mad about this, and no one seems to care. Not Google and not even Samsung.
The only interesting thing that i found around the internet is this guy's findings
plus.google.com/113601948978986762347/posts/2ALASEC1dG2
I read the log on my phone and matches to his... but now the thing is, what do i do with this information? I'm not a programmer o something like that.
Any ideas?

I think your board is faulty. Even so, have you tried disabling SR and raising voltages across the board? Trimming eMMC? Omapflash?
a manta wrote this.

Hey! Thanks for the reply but I'm just a regular user with just a little bit of computer knowledge... so the things you mentioned are basically Chinese to me
Sent from my Galaxy Nexus using xda app-developers app

elcampeondelrodeo said:
Hey! Thanks for the reply but I'm just a regular user with just a little bit of computer knowledge... so the things you mentioned are basically Chinese to me
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
He is saying that you have root you need to install trickster mod from the play store. Open the app and go to specific. Then disable the smart reflex toggles and click the oké button in the upper right corner see if that works. If it doesnt re enable smart reflex and go tot MPU voltages. Next to the words MPU voltages there is a blue plus/minus button. Click that and click the plus one time. Accept it and push again the oke button. The other two things I dont exactly know..
Sent from my Galaxy Nexus using XDA Premium HD app

Honestly, if you are getting reboots on a clean stock (including stock kernel) , it's probably a hardware issue.
Sent from my Galaxy Nexus using Tapatalk 2

Thanks for the reply guys!
mrgnex said:
He is saying that you have root you need to install trickster mod from the play store. Open the app and go to specific. Then disable the smart reflex toggles and click the oké button in the upper right corner see if that works. If it doesnt re enable smart reflex and go tot MPU voltages. Next to the words MPU voltages there is a blue plus/minus button. Click that and click the plus one time. Accept it and push again the oke button. The other two things I dont exactly know..
Sent from my Galaxy Nexus using XDA Premium HD app
Click to expand...
Click to collapse
I tried both things you mentioned with no luck
I'm still searching around for those other things beekay201 mentioned earlier. I found that Omap Flash is a tool for flash roms in binary mode, so that way you can unbrick some phones. Still trying to find out how that can be useful for my case (forum.xda-developers.com/showthread.php?t=1242330)
bpyazel said:
Honestly, if you are getting reboots on a clean stock (including stock kernel) , it's probably a hardware issue.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
The thing is that after a clean stock install everything works fine for a week or two, that means no random reboots, and i can transfer any kind of file of any size with no problem. Then for some estrange reason (even with no crazy apps installed) starts with a random reboot, after that first reboot i know is time and that i wont be able to transfer files anymore, because it WILL reboot while i'm transfering files. Other thing i have noticed is that around where the camera lens is, get really hot. So I think that the reason it reboots is kernel panic caused by overheating, or the other thing is that my sdcard have some issues when writing files.
Right now i'm using CyanogenMod 10.0.0-maguro with jelly bean 4.1.2 and franco.kernel 3.0.51-nightly-512GPU and i have already tried going back to stock.
how can a I check if my hardware is fine? Is there any app out there?
Thanks!

elcampeondelrodeo said:
Thanks for the reply guys!
I tried both things you mentioned with no luck
I'm still searching around for those other things beekay201 mentioned earlier. I found that Omap Flash is a tool for flash roms in binary mode, so that way you can unbrick some phones. Still trying to find out how that can be useful for my case (forum.xda-developers.com/showthread.php?t=1242330)
The thing is that after a clean stock install everything works fine for a week or two, that means no random reboots, and i can transfer any kind of file of any size with no problem. Then for some estrange reason (even with no crazy apps installed) starts with a random reboot, after that first reboot i know is time and that i wont be able to transfer files anymore, because it WILL reboot while i'm transfering files. Other thing i have noticed is that around where the camera lens is, get really hot. So I think that the reason it reboots is kernel panic caused by overheating, or the other thing is that my sdcard have some issues when writing files.
Right now i'm using CyanogenMod 10.0.0-maguro with jelly bean 4.1.2 and franco.kernel 3.0.51-nightly-512GPU and i have already tried going back to stock.
how can a I check if my hardware is fine? Is there any app out there?
Thanks!
Click to expand...
Click to collapse
512GPU? You mean your GPU is overclocked? Maybe try to set your GPU to stock. And if it gets really hot and you have random reboots you can try to over volt with trickster mod.
Sent from my Galaxy Nexus using XDA Premium HD app

mrgnex said:
512GPU? You mean your GPU is overclocked? Maybe try to set your GPU to stock. And if it gets really hot and you have random reboots you can try to over volt with trickster mod.
Sent from my Galaxy Nexus using XDA Premium HD app
Click to expand...
Click to collapse
No, I don't think my GPU is overclocked, that's the full name of the kernel, you say that the kernel automatically puts my GPU to 512?. Anyways i just installed that kernel two days ago just because i thought it might make the reboots go away. I'm having rebooting problems since february (just after upgrading to 4.2.1), so i don't think that the GPU is causing the reboots.

elcampeondelrodeo said:
No, I don't think my GPU is overclocked, that's the full name of the kernel, you say that the kernel automatically puts my GPU to 512?. Anyways i just installed that kernel two days ago just because i thought it might make the reboots go away. I'm having rebooting problems since february (just after upgrading to 4.2.1), so i don't think that the GPU is causing the reboots.
Click to expand...
Click to collapse
Well if it keeps rebooting you can try to over volt. Maybe that helps.
Sent from my Galaxy Nexus using XDA Premium HD app

OK I'll try that! Thanks for your help man!
Sent from my Galaxy Nexus using xda app-developers app

Strange wifi problem after kitkat upgrade?

After upgraded to kitkat, I noticed wifi icon at status bar will be missing after many days. Wifi will indicates as off and it couldn't be turned on. YET wifi is working fine. The only way to clear is to reboot. Anyone seen this?
Sent from my SM-P600 using Tapatalk

double07 said:
After upgraded to kitkat, I noticed wifi icon at status bar will be missing after many days. Wifi will indicates as off and it couldn't be turned on. YET wifi is working fine. The only way to clear is to reboot. Anyone seen this?
Sent from my SM-P600 using Tapatalk
Click to expand...
Click to collapse
I have had the same issue a few times.
Sent from my SAMSUNG-SGH-I317 using XDA Premium 4 mobile app

ProFresh4 said:
I have had the same issue a few times.
Sent from my SAMSUNG-SGH-I317 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I have the issue too. Anyone have any idea how to fix? Thanks.

I noticed the same thing too. Turning airplane mode on and off fixes it for me. I just got the tablet a few days ago, so I havent done much testing, but do you guys have " turn wifi off during sleep" setting on in the advanced wifi menu? I was suspecting that to be the culprit.

I realized this thread is nearly a year old, but I just bought this (used) Note tablet, and experienced the exact symptoms as described by the other posters. The wifi issue happens almost every time my tablet sleeps for more than a hour. Toggling airplane mode on/off fixes the issue, only temporarily, until the next sleep. I am wondering if there are any clues to what causes the issue.
Is it a bug in the factory rom, or something that I installed?
Here is the info of my tablet:
- US model SM-P600 (XAR), with latest stock rom UEUCOB1
- Rooted by TWRP 2.8.5.1
- Xposed installed with these modules:
Wanam
No Wake of Charge for S5, and
App Settings (only change rotation setting for one 3rd party app).
I am considering do a factory reset and setting it up again from scratch. But I want to hear if others are experiencing this issue even with 100% stock (non-rooted) rom. By the way, the issue only happens when you set Keep Wi-Fi on during sleep to either "Never" or "Only when plugged in". I would really appreciate someone with non-rooted rom letting me know if this happens to them when they set their tablets to allow Wifi to sleep with tablet.

Volume keys not responding during call?

My volume keys don't work at all when in a call when the phone is held to my ear. To change the in call volume I have to take the phone off my ear so that the screen can come on, and then press the volume rocker.
Is this by design or is there something wrong with my device?

Update: this seems to be working intermittently for me. What could be the issue? I'm so stumped.

Same here. It's pissing me off. Anyone else have this issue?
Sent from my HTC_0P6B6 using XDA Free mobile app

No problem on At&t stock
Sent from my HTC One_M8 using XDA Premium 4 mobile app

I have the same problem. Stock international + ROOT and Xposed. It's really really annoying.

Hey,
Exactly the same configuration as above. Same issue as you all guys. I think this is intentional though

I don't believe it is, it would be the first phone I see with this "feature".

Ok, now I am really getting confused. Reading of @angadreme also having Xposed, I thought it must be some Xposed module. I disabled all of them and rebooted -> volume buttons working with screen off during call. I thought it could be one of the options about volume buttons with screen off of Sense 6 toolbox, so I re-enabled all modules except S6TB and rebooted. Volume buttons still working. Then I enabled S6TB again, rebooted and... volume buttons still working.

Still not responsive in call
Black Antitoon said:
I don't believe it is, it would be the first phone I see with this "feature".
Click to expand...
Click to collapse
Hey,
Am now wondering if my phone has an issue...I had this 'feature' (you're true, this should not happen at all...) since the very first day I bought it...all stock and so on.
Now that I'm running ARHD 8.0 with or withouht ElementalX, with or without Sense Toolbox, still the same issue...not TOO annoying, but still.
What do you suggest ? Shall I go for a replacement ?

No, it's clearly a software issue, I don't think it would make sense to ask for a replacement which would most likely have the same problem (assuming that they accept to replace the phone). If it's a firmware bug, it will sooner or later be fixed. If you had this problem even before rooting, it might be related to some app we have both installed. In case you find out more, please let me know, I am also going crazy for this little annoying issue!
By the way, after my last post, the volume buttons kept working without problems until I next rebooted the phone, which was several days later. Now they are again not working. -.-