Related
hey guys,
my green answer call button doesnt seem to work. i'm wondering if its the rom or the phone. it still lights up but doesnt respond when i push the button.
any suggestions like a button tester program?
kind regards,
jason
Are you having any problems with any other keys?
If its just the one you can break your phone down and check your connections and see if anythings loose or damaged. Make sure to go to the Wiki and check out the guide on how to properly take your phone apart.
everything works except for that the green phone button
Starting to wonder about malfunctioning buttons posts
I myself posted a thread on my malfunctioning power button . I am getting the feeling that certain apps and tweaks are causing some of these malfunctioning hardware buttons to happen. Not exactly a scientific point of view, but I think lots of this button malfunctioning (no matter which one), can eventually be resolved by HR or as mentioned in another post, Clear Storage. I myself, within a minute, pulled out my SDMicro card out for 15 seconds, took off Quickmark application (last app or cab put on my system), and my power button turns on/off as it should. I had to resort to SR's when I had my problem..........................
Latest: Found out that my main problem was NOT any of the above,, it all seemed to occur because of a buildup of Notification Queue's,, so check that out... I think that those queue's can be a source of a lot of problems
cheers for that suggestion.
softreset doest fix it so i will have to resort to hard reseting.
lucky the vodaphone version has the 3G phone button and i can use that to get to the dial pad but it then assumes my calls are 3G which are annoying
has anyone got any suggestions then?
i flashed K's new rom and still my 'Green Answer Phone' button doesnt work.
thanks in advance for any help
jason
jasonchiu said:
has anyone got any suggestions then?
i flashed K's new rom and still my 'Green Answer Phone' button doesnt work.
thanks in advance for any help
jason
Click to expand...
Click to collapse
i had a similiar problem when installing a different dialer via cab.
i would suggest to either install a naked rom (like pandora naked) or one of the older roms (like schaps v3.x).
do not install any other cabs and see if the green button is working.
i flashed pandora naked rom and it still doesnt work.
any one have any other suggestions?
if not will i have to take the phone apart :S?
the Irda doesn't work at all, when i install a program to use my tytn as a remote for my tv, and i try to clone my remote i get an error saying "Irda port being used by another application"
and it wont communicate with over devices via Irda. other than that it works great...does anybody know a way to fix this problem?
p.s. tried other roms, Irda works fine, so it's not the phone.
please help this lost soul!!
thanks!
sorry, posted in wrong area! rookie mistake! forget about it!
A general rule I follow is not to use too many .cabs as certain apps and tweaks can cause some of these malfunctionings to happen.
You cant be installing cabs for everything on your phone. Do you really have so much space in your phone?
hey guys i thought this was a thread about getting my green answer call button working again!
seem like more of a hardware problem to me. you can still try checking for bad blocks, flashing another radio, but that all may be futile. look up the disassembly guides in the wiki. mikechannon also has some stuff on that, if u click on his sig
every other time my phone rings I cant answer it. The accept button just wont move?? is it just me or have anyone else had this error I have a dezire z
Do you have set CPU set to 245MHz @ screen off?
no i dont, why?
Well that could be one cause, maybe it's a bad app causing your phone to temporarily freeze? Can you slide it the other way and ignore the call?
Did you try flashing a different kernel?
Sent from my CyanogenMod powered G2.
Utorrent76 said:
Did you try flashing a different kernel?
Sent from my CyanogenMod powered G2.
Click to expand...
Click to collapse
why do you suggest this? how do you know hes using kernels? im just trying to see what your connection to the solution is -its quite a specific answer to a problem that hasnt really been examined. what rom is he on, etc before you can start talking about kernels -- so can you clarify?
accept button - do you mean the slider? if you have cmod - just activate settings to disable lock menu/trackball/ whatever --also you could try the no-lock unless you have security issues.
if no cmod -- theres apps to reduce the lockage -- that may help you get your phone calls but still doesnt fix the problem? you could try enomther's and his awesome extra ssettings app has all those options
Thanks for your help, well it is my wifes phone and it is fresh from the store, just a bunch of apps installed.
I will try some things and see if i can figure it out. And yes it is the slide button, can that be switched for a push button, Is it theme based or in the dialer?? hope you understand what i say.
jaypeg123 said:
Thanks for your help, well it is my wifes phone and it is fresh from the store, just a bunch of apps installed.
I will try some things and see if i can figure it out. And yes it is the slide button, can that be switched for a push button, Is it theme based or in the dialer?? hope you understand what i say.
Click to expand...
Click to collapse
If its a stock DESIRE Z and not a G2 then I think it's safe to assume its got sense on it and not AOSP. Did you try hard resetting it? (power down and pulling the battery for at least 30 sec) other than that id check for any OTA updates in the settings menu. OR if you're willing/know how, you can root it and run CM or virtuous. Both ROMs are excellent. If you do that and the problem persists, it could very well be a faulty unit. You have a lot of options!
I found I had problems answering calls when I had a specific make of screen protector on the phone. As soon as I took that off and went back to a previous one I'd used then it was fine again ! It's a long shot, but I thought I'd throw it in there.
Problem solved, An update did the trick, thanks for helping out my friends,
same problem , cannot answer with swipe keys
I have the same problem, which update did you use
same problem , cannot answer with swipe keys
I have the same problem, which update did you use
so i'd like to collect the issues (and solutions) for the captivate glide's new official android upgrade (ice cream sandwich).
we all know about the keyboard backlight issue,but its already solved (thanks for it to the devs), moreover we have an opportunity for rooting, as well.
Apart from that I experienced that after a few seconds of black screen, "com.android.phone stops" after I receive or make phone calls. That is also can be solved by making a factory reset.
But I have a problem I couldnt solve yet: screenshot/screencapture. On gingerbread you had to hold home button while pressing the lock key. On ICS it doesnt work. I read that on ICS you should press volume down and lock key at the same time, but that doesnt work for me either. Do you know a solution for this?
I've got one more problem, but I'm not sure if its a fault of the ROM: on the stock web browser,everything works fine, but on google chrome, I cannot use virtual keyboard,nor copy/paste functions.
Thanks for your help
soadzoor said:
so i'd like to collect the issues (and solutions) for the captivate glide's new official android upgrade (ice cream sandwich).
we all know about the keyboard backlight issue,but its already solved (thanks for it to the devs), moreover we have an opportunity for rooting, as well.
Apart from that I experienced that after a few seconds of black screen, "com.android.phone stops" after I receive or make phone calls. That is also can be solved by making a factory reset.
But I have a problem I couldnt solve yet: screenshot/screencapture. On gingerbread you had to hold home button while pressing the lock key. On ICS it doesnt work. I read that on ICS you should press volume down and lock key at the same time, but that doesnt work for me either. Do you know a solution for this?
I've got one more problem, but I'm not sure if its a fault of the ROM: on the stock web browser,everything works fine, but on google chrome, I cannot use virtual keyboard,nor copy/paste functions.
Thanks for your help
Click to expand...
Click to collapse
Press and hold Power + Home button together for a screenshot.
Keyboard works fine for me on Chrome, as well as copy/paste. But mine can be a different scenario as i'm running NardROM with the LH2 kernel.
ninthsense said:
Press and hold Power + Home button together for a screenshot.
Keyboard works fine for me on Chrome, as well as copy/paste. But mine can be a different scenario as i'm running NardROM with the LH2 kernel.
Click to expand...
Click to collapse
Thanks a bunch! if i press them at the same time and hold them, it just works as a charm! Im wondering why I didnt figure that out by myself.
The chrome with virtual keyboard is still no better.. anyone has a tip?
If anybody knows how to get past KIES because it never recognizes my phone, I'd love to get ICS to load.
just use this: http://forum.xda-developers.com/showthread.php?t=1841502 It's what I am using and most people were using before the Official came out. No diffidence between the 2 version practically. Make sure you have CWM then flash. Oh and as always do a nandroid backup before. It is the only way back as well.
I'll admit it... I'm a n00b that this and don't want to brick my phone. Dare I wait till Samsung / AT&T get their stuff together and get the KIES & ICS issues fixed or do I try the link dudejb suggested? A clear step by step would be appreciated (no offense intended). I'm just not too technically savvy.
If you're new to android flashing and not comfortable with something like that, I wrote up a nice newb-friendly guide here that walks you through installing the 4.0.4 leak, as well as installing ClockworkMod Recovery, fixing the keyboard backlight issue, and rooting.
I'd say go for it, you'll be waiting quite some time just to see Samsung fix the keyboard light, let alone address your issue of kies not seeing the phone.
I'd like to chime in with another problem I've noticed. With Gingerbread, the physical keyboard worked just like the on-screen one: tap shift or alt to modify the next keystroke, tap twice to lock the modifier. With ICS (the official firmware installed via Kies), however, a single tap on the physical keyboard keeps modifying keystrokes until tapped again. Has anyone else experienced this? Since I have the force-closing problem with the phone, I'm planning on doing a factory reset. Maybe that will solve my keyboard problems.
Also, I can also confirm problems with the on-screen keyboard in Chrome. All the other browsers work fine, but the keyboard just won't show up in Chrome. Combine that with the physical keyboard problems I've been having and Chrome becomes essentially unusable.
On the plus side, my battery life seems better. It used to be that I couldn't go more than eight hours without the phone dying on me, but now it's still going strong at 20-30% after eight hours.
clpo13 said:
With Gingerbread, the physical keyboard worked just like the on-screen one: tap shift or alt to modify the next keystroke, tap twice to lock the modifier. With ICS (the official firmware installed via Kies), however, a single tap on the physical keyboard keeps modifying keystrokes until tapped again. Has anyone else experienced this?
Click to expand...
Click to collapse
I'm not having that problem with the LH2 update (checked in the stock browser and text messages).
Here's my list of bugs/complaints with the LH2 official update:
1. no keyboard backlight (I know there's a fix.)
2. occasionally getting "com.android.phone has stopped" after ending a call. (I've seen at least 4 people report this problem on this forum.)
3. email app display is blank after adding a email account (solved by changing font size, then it's fixed)
4. email app doesn't remember which view you selected after closing (i.e. standard/conversation view, always defaults back to standard view)
clpo13 said:
I'd like to chime in with another problem I've noticed. With Gingerbread, the physical keyboard worked just like the on-screen one: tap shift or alt to modify the next keystroke, tap twice to lock the modifier. With ICS (the official firmware installed via Kies), however, a single tap on the physical keyboard keeps modifying keystrokes until tapped again. Has anyone else experienced this? Since I have the force-closing problem with the phone, I'm planning on doing a factory reset. Maybe that will solve my keyboard problems.
Click to expand...
Click to collapse
I can confirm the problems with the keyboard's alt and shift keys. It's a pain
My physical keyboard works just like before. I haven't looked, but I imagine this is something you can set in the Input tab in Settings?
EDIT: It's not there, sorry. I also have the CRT-Off, Custom Boot Anim and Backlight fix mods installed. Perhaps that makes a difference?
Sent from my SGH-I927 using xda app-developers app
Evil Alex said:
My physical keyboard works just like before. I haven't looked, but I imagine this is something you can set in the Input tab in Settings?
EDIT: It's not there, sorry. I also have the CRT-Off, Custom Boot Anim and Backlight fix mods installed. Perhaps that makes a difference?
Sent from my SGH-I927 using xda app-developers app
Click to expand...
Click to collapse
I too had the keyboard problem. I traced it back to the keyboard app "Swiftkey3." If I use any other keyboard app (stock or not), the physical keyboard works as it should. If Swiftkey is enabled, the caps or alt keys lock on with one press. VERY annoying.
Other than that, I've experienced some txt messages coming in multiple times. Like sometimes more than 15 copies of one txt. Seems to have calmed down some since I moved from the official leak to NardROM 0.4, but I did have a txt last night come in twice. Maybe that one was on my friend's end and he actually sent it twice.
Right now, my main concern is battery consumption on NardROM 0.4. Seems a bit worse than when I was running the stock leak (rooted). Battery profile attached. I've barely used my phone today since unplugging it, yet plenty of drain. I have no idea why the phone is "awake" so much when the screen is off.
bakageta said:
If you're new to android flashing and not comfortable with something like that, I wrote up a nice newb-friendly guide here that walks you through installing the 4.0.4 leak, as well as installing ClockworkMod Recovery, fixing the keyboard backlight issue, and rooting.
I'd say go for it, you'll be waiting quite some time just to see Samsung fix the keyboard light, let alone address your issue of kies not seeing the phone.
Click to expand...
Click to collapse
I haven't tried to do anything yet because the link you supplied has in it this phrase which concerns me.... "First, make sure you have Kies installed, so that you have the correct USB drivers." I cannot connect to the phone using the latest KIES installed on my PC. Is there supposed to be KIES on my phone, because if there is, it's missing. Again, please be patient with me and thank you all for everybody's help.
clpo13 said:
With Gingerbread, the physical keyboard worked just like the on-screen one: tap shift or alt to modify the next keystroke, tap twice to lock the modifier. With ICS (the official firmware installed via Kies), however, a single tap on the physical keyboard keeps modifying keystrokes until tapped again
Click to expand...
Click to collapse
I experienced the same but I realised that it depends on the program you use. At some browsers it is the way you just described it, but with texting, and with the stock browser, everything is fine to me
bakerb316 said:
I haven't tried to do anything yet because the link you supplied has in it this phrase which concerns me.... "First, make sure you have Kies installed, so that you have the correct USB drivers." I cannot connect to the phone using the latest KIES installed on my PC. Is there supposed to be KIES on my phone, because if there is, it's missing. Again, please be patient with me and thank you all for everybody's help.
Click to expand...
Click to collapse
i have a difficult time connecting to my phone with Kies as well. Here are some steps to take that have helped me:
download the latest version of kies.
remove battery from phone for 30 seconds, then let it boot back up fully before plugging to computer (this was from samsung tech support)
uninstall kies, run ccleaner registry cleaner, reboot, reinstall kies.
download the 1.5.xx version of samsung USB drivers.
I've had to do all of those things to get Kies to see my phone.
and on a couple of computers, it just won't read it, at all.
euro1990 said:
Right now, my main concern is battery consumption on NardROM 0.4. Seems a bit worse than when I was running the stock leak (rooted). Battery profile attached. I've barely used my phone today since unplugging it, yet plenty of drain. I have no idea why the phone is "awake" so much when the screen is off.
Click to expand...
Click to collapse
Toggle off wi-fi and bluetooth, ya dingbat! :silly: Your phone is likely trying to re-sync BT connection and/or sending a wifi heartbeat, and/or searching for wifi network.
euro1990 said:
I too had the keyboard problem. I traced it back to the keyboard app "Swiftkey3." If I use any other keyboard app (stock or not), the physical keyboard works as it should. If Swiftkey is enabled, the caps or alt keys lock on with one press. VERY annoying.
Click to expand...
Click to collapse
How about that. I did have SwiftKey installed and enabled. I switched to another keyboard and it's working fine now. Strange that it would affect the physical keyboard like that.
bakerb316 said:
I haven't tried to do anything yet because the link you supplied has in it this phrase which concerns me.... "First, make sure you have Kies installed, so that you have the correct USB drivers." I cannot connect to the phone using the latest KIES installed on my PC. Is there supposed to be KIES on my phone, because if there is, it's missing. Again, please be patient with me and thank you all for everybody's help.
Click to expand...
Click to collapse
Simply having Kies installed on your PC should make sure you have the drivers you need, you don't actually need to run Kies. Follow the instructions for download mode, and see if you get a green OK in the 4.0.4 exe. If so, you'll be fine.
Apparently Samsung has heard enough complaints about the issues with ICS and the Glide, so they made this 'announcement' on their website.
AT&T Cell Phones: How do I update my Samsung Captivate Glide to Android 4.0 Ice Cream Sandwich?
The update for the Samsung Captivate Glide has been put on hold while Samsung works to optimize the update for our users.
Here's would be the link if I would be able to attach it.
Not too sure what those 'optimizations' entail (Keyboard back light I'd assume to be one of them), or if Kies connectivity is one as well because I had a chat with one of their online support agents and he said this...
"As there is huge demand on the Kies server and that is why the update is put on hold. As the Kies server is busy the phone would not be detected."
Sounds fishy to me, but plausible.
a new update for chrome has been out today! now the onscreen keyboard is visible and works well!
Ive searched everywhere and can't seem to find anyone with a solution. Ive found a post with the same problem but no solution.
So yesterday my s3 started having problems waking up. Meaning when I lock it usually you bring up the lock screen by pressing the power button or home button. Problem is when I press either one, screen doesnt come on. The buttons do. If I tap the screen I can hear the ripple effect but the screen doesnt light up. I have to keep locking and unlocking till it finally works. Averege of about 6 tries. When I get a call most of the time the screen doesnt come on either. I can still answer since I know where the slider is. When I do turn it on everything works perfect. No flickering or any other issues. When it boots it works perfect...never fails. Just when I lock it.
I tried restoring already, thinking its a software issue...still does it. What piece of hardware could cause this? I'm stumped. Please any advice would be great.
I'm not rooted and running 4.1.1 oem rogers software.
Sent from my SGH-I747M using xda app-developers app
felcom said:
Ive searched everywhere and can't seem to find anyone with a solution. Ive found a post with the same problem but no solution.
So yesterday my s3 started having problems waking up. Meaning when I lock it usually you bring up the lock screen by pressing the power button or home button. Problem is when I press either one, screen doesnt come on. The buttons do. If I tap the screen I can hear the ripple effect but the screen doesnt light up. I have to keep locking and unlocking till it finally works. Averege of about 6 tries. When I get a call most of the time the screen doesnt come on either. I can still answer since I know where the slider is. When I do turn it on everything works perfect. No flickering or any other issues. When it boots it works perfect...never fails. Just when I lock it.
I tried restoring already, thinking its a software issue...still does it. What piece of hardware could cause this? I'm stumped. Please any advice would be great.
I'm not rooted and running 4.1.1 oem rogers software.
Sent from my SGH-I747M using xda app-developers app
Click to expand...
Click to collapse
My guess is that you have something draining all your RAM or being hard on your CPU. When you restored, did you factory reset?
You might have to backup your stuff, factory reset. Test it, if it still does it, bring it up with Rogers for a replacement. If it doesn't, reinstall your stuff until you find the culprit.
You could troubleshoot it also by uninstalling the latest apps you installed.
BWolf56 said:
My guess is that you have something draining all your RAM or being hard on your CPU. When you restored, did you factory reset?
You might have to backup your stuff, factory reset. Test it, if it still does it, bring it up with Rogers for a replacement. If it doesn't, reinstall your stuff until you find the culprit.
You could troubleshoot it also by uninstalling the latest apps you installed.
Click to expand...
Click to collapse
Like I said...Already did a factory reset. Meaning All apps were gone. Started fresh. Even without going through the first setup (setting up google account etc etc) if I lock the phone its hard to wakeup.
Phone is out of warranty so no go there....
I'm just not understanding what is causing it. I know the screen is fine...buttons are fine...everything points at a software problem. I found a post from a while back where someone was having the same problem....no solution was posted though. I even took the phone apart last night thinking a bad connection or something...disconnected the screen and reconnected it...didn't do anything.
If the screen was going bad wouldn't I have issues all the time? Once I wakeup the phone it works perfect...no flickering or anything. When it boots (which I've done like 30 times between today and yesterday) the screen has come on every single time perfectly fine. Everything tells me it's software related...but after doing a factory reset and running original firmware it seems as though it must be a hardware issue...but which component.
I know the phone wakes up when I press the buttons...I can see the menu and back buttons light up...and if I tap the screen the ripple sound is there...just the screen doesn't wake up....till I try a few more times....very frustrating.
Thanks Again for trying...if anyone has any ideas....greatly appreciated. I'll try and find original Rogers firmware and install with odin...see if that works....
felcom said:
Like I said...Already did a factory reset. Meaning All apps were gone. Started fresh. Even without going through the first setup (setting up google account etc etc) if I lock the phone its hard to wakeup.
Phone is out of warranty so no go there....
I'm just not understanding what is causing it. I know the screen is fine...buttons are fine...everything points at a software problem. I found a post from a while back where someone was having the same problem....no solution was posted though. I even took the phone apart last night thinking a bad connection or something...disconnected the screen and reconnected it...didn't do anything.
If the screen was going bad wouldn't I have issues all the time? Once I wakeup the phone it works perfect...no flickering or anything. When it boots (which I've done like 30 times between today and yesterday) the screen has come on every single time perfectly fine. Everything tells me it's software related...but after doing a factory reset and running original firmware it seems as though it must be a hardware issue...but which component.
I know the phone wakes up when I press the buttons...I can see the menu and back buttons light up...and if I tap the screen the ripple sound is there...just the screen doesn't wake up....till I try a few more times....very frustrating.
Thanks Again for trying...if anyone has any ideas....greatly appreciated. I'll try and find original Rogers firmware and install with odin...see if that works....
Click to expand...
Click to collapse
Sounds indeed like software issue. I'm not so sure what would cause it on stock rogers though.
Either way, you can find the stock ROM on sammobile.com or on this thread: http://forum.xda-developers.com/showthread.php?t=1822308
You'll need Odin to flash it. (It doesn't trigger the flash counter)
felcom said:
Phone is out of warranty so no go there....
Click to expand...
Click to collapse
Did you buy your phone with a credit card? Some cc's have warranty built in. Mine doubles what the manufacturer offers.
Thanks for the link. I will try it tonight and post the results. Really hoping it works.
Sent from my SGH-I747M using xda app-developers app
I downloaded the newest firmware. 4.1.2 official rogers. Problem persists. Must be a hardware issue. Thing is what could cause this? Is it the screen...is it the gpu? I imagine if its gpu the phone is only good for parts as I imagine its part of the motherboard. Oh well...might be getting the s4 sooner then planned.
Sent from my SGH-I747M using xda app-developers app
felcom said:
I downloaded the newest firmware. 4.1.2 official rogers. Problem persists. Must be a hardware issue. Thing is what could cause this? Is it the screen...is it the gpu? I imagine if its gpu the phone is only good for parts as I imagine its part of the motherboard. Oh well...might be getting the s4 sooner then planned.
Sent from my SGH-I747M using xda app-developers app
Click to expand...
Click to collapse
If you're down for a little test, you could try with a custom ROM.
Use the link I gave you and flash pre-rooted Rogers' ROM. From there, install TWRP (or cwm) using goomanager (from the Play Store) and flash a custom ROM as per their instructions (Don't forget the Gapps).
Before anything though, make a backup
Never know, might save you some time on that S4.
BWolf56 said:
If you're down for a little test, you could try with a custom ROM.
Use the link I gave you and flash pre-rooted Rogers' ROM. From there, install TWRP (or cwm) using goomanager (from the Play Store) and flash a custom ROM as per their instructions (Don't forget the Gapps).
Before anything though, make a backup
Never know, might save you some time on that S4.
Click to expand...
Click to collapse
Thanks. I might try it. Dont think I have too much to lose at this point. I always try and keep my phones nice so that when I get a new one I can sell the old one for good money to help offset the cost. This really messes with that system as the phone isn't worth much now...just bought an extended battery too...was planning to keep it for at least another 6 months.
Sent from my SGH-I747M using xda app-developers app
So just a quick update. For no apparent reason the phone started working fine again. It now turns on and off just fine. I'm not going to mess around with it anymore. That's really bizzare. I'll give it a couple days and will report back if it continuous to work fine or if the problem comes back. Thanks for the input.
Sent from my SGH-I747M using xda app-developers app
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. -.-