I have a question to the right bottom button "back". Now I use rom officiální CyanogenMod 7 dated August 19, 2012. When the phone rings, then picks him for the bottom right button "back" and call off (like I did not want to accept). Previously I was using some other rom and it also made, such as when I used rom apocalypse of June 17, 2012, so I did not do it and when I put the latest apocalypse from 9.7.2012 so I did. Is it somewhere on a fix? or where is the problem? Thanks for the reply. Excuse me for my English
It should not happen.
Some bug.
Sent from my GT-S5830 using Tapatalk 2
Related
I have an off-warranty SGS that has the back/menu soft-keys not working. I tried updating OS to 2.3 and then flashing to Darky's 10.2.2 to no avail. I have heard vague rumours of "hacking the softkey firmware" to fix this issue, but no one can elaborate on that.
Does anyone know how to do this and what is required?
If they don't work, I doubt you'll get them to work with software—unless you flashed software on their which caused the initial problem. If, for example, you dropped your phone and your capacitive buttons stopped working... well, good luck.
I had the same problem too.
Try to put froyo the with type this code *#*#2664#*#* then it will give you 2 options choose the first then the second.
It should take around 5 to 10 minutes then it's should be dine.
Sent from my GT-I9000 using XDA Premium App
Thanks KFlexx I'll try that tonight.
Hi guys, my first post here on XDA.
The Note is my first Android phone, I previously had an iPhone. I really like the Note, but the most annoying thing about it is that it will always wake up after a call is ended.
I always call using the headset cable, and I both answer and hang up calls using the headset button. The phone is in my pocket. After hanging up the call (using the button) I happily go on doing whatever I was doing before. Meanwhile, in my pocket, my Note happily continues making pocket calls and clicks around at random!
It's driving me absolutely crazy. How can I fix it? Is there a mod I don't know about? An app? I've tried downloading another dialer (DialerEx) but no luck. It's obviously an OS "feature".
I first noticed this on stock ROM, so I tried RocketROM v21 in hope that it was fixed there. No luck.
Can someone please point me to a fix? I'm even willing to hack kernel code to get rid of this!
Thanks
---------
Edit: I of course posted this thread in the wrong forum just to show my noobieness. Can't find a way to move it to Q&A so I leave that to the moderators... Sorry!
Moved To Q&A
No Problem, its moved
I'm curious about this as well. I use a headset 95% of the time and this drives me crazy. It's got to be TouchWiz I think since my AOSP phones never did/do this.
Sent from my GT-N7000 using xda premium
I just compared this to my friend's HTC (Sense UI), and he also does not have this problem. I find it problematic if this is part of the TouchWiz UI, because we don't have access to the source code for that, right? So, no way of fixing it beside throwing out TW completely?
How about the ICS TW? I'm still waiting for a stable CM9 release before jumping on the ICS bandwagon, so can someone with the ICS leak confirm that this is till an issue?
Thanks in advance!
Ok
Ive tried to experiment extensively with this issue I am having;
1) When I press the stand by button, If there is no lock screen then I sometimes need to press/touch the screen once randomly, after which the second touch is responsive. So basically if I click on the home icon, the first touch will highlight it, but no action will be performed. Second touch will do the action I programmed home button.
2) If I use the 3rd Party app for the lockscreen, and I have the same issue,when powered on, I have to tap the screen first, then after that the second action (swipe or pattern) works. First touch doesn't respond.
3) Rarely the touch does responds in the first go, after 20 times not working on the first touch maybe. This eliminates suspected faulty hardware.
Ive reinstalled my rom (fuklag1.4) and it made no difference. Ive reset to stock kernel, made no difference, Ive tried a lot of things, a different launcher,no luck. Does anyone notice this ? or have the same issue?
Im using ;
Unlocked Bootloader
Doom Kernel 6
Ful Lag 1.4
Dodexed it myself
Pure X Audio 11
Shrunken Touch Buttons
Any pointers would be helpful.
Do you have some script in init.d?
Did you tried stock rom?
Sent from my C6602 using xda premium
gm007 said:
Do you have some script in init.d?
Did you tried stock rom?
Sent from my C6602 using xda premium
Click to expand...
Click to collapse
how do I get the script?
No. Ive departed from the stock rom, on the stock rom, I dont recall these issues to be honest but I cant remember. I dont even have it saved to revert to.
The script should be in system/etc/init.d folder if there is any.
You can revert to stock rom by using flashtool.
Sent from my C6602 using xda premium
Hi, for a month now my droid 4 has had a problem where the screen will not rotate when the phone does. I have done a full wipe/reset, upgraded to jelly, and shook it a little yet the screen still will not rotate.
Is there any way to see if the accelerometer is working so i can tell if its a hardware problem or software problem? Is there anything i can do to fix it if it is a hardware problem, because i dont think verizon will accept a return or exchange
Do you have auto rotate enabled?
Most likely this is your problem. Disabling auto rotate will force your phone to portrait mode.
Auto rotate can be found on settings>display
Make sure there is a checkmark in auto rotate.
Please hit the thanks button if i this helped. :thumbup:
Sent from my Motorola Droid 4 using xda app-developers app
Are u on stock ROM or cm/aokp?
Sent from my XT894 using xda app-developers app
I'm not OP, but I'm using Cyanogenmod 10, nightly build 4/28 or so. I kept updating to see if it got fixed and hasn't for as long as I've had the phone, month. I just saw in the dev forum that using build 1904 with a replacement kernel file it would work, but my phone won't boot into cyanogen anymore. I'm currently trying to fix that issue now.
Anyone know how to fix the accelerometers in cyanogen 10 correctly?
tribalman said:
I'm not OP, but I'm using Cyanogenmod 10, nightly build 4/28 or so. I kept updating to see if it got fixed and hasn't for as long as I've had the phone, month. I just saw in the dev forum that using build 1904 with a replacement kernel file it would work, but my phone won't boot into cyanogen anymore. I'm currently trying to fix that issue now.
Anyone know how to fix the accelerometers in cyanogen 10 correctly?
Click to expand...
Click to collapse
I tried the replacement kernel, and it didn't fix the problem for me on Liquid-JB-v2.2 .
Fix for CM10 rom is scheduled for tonight.
Many roms on this forum are based on the CM10 rom so should slowly solve all of these issues. Keep an eye on the CM10 thread
Just recently had this issue pop up. Everything else seems to be running smooth aside from the virtual home button. When pressed, it makes a glow, but doesn't take me to the home screen. Setting a home button on LMT Launcher doesn't work either. Basically, I just have to keep hitting the back button to get Home. Not sure what info one would need about my device to tackle the issue. KFHD7 running the latest CM11 nightly(5/31), Nova launcher with Maromi's 5/19 kernel installed. The issue has come up with two recent nightlies as well as the May 5th Snapshot. I've done a fresh install twice since yesterday and the button will work for a bit, then will stop. I should also mention that I wiped everything possible aside from the bootloader two days ago, reinstalled and same thing, not working! Does downgrading from a newer Nightly to the Snapshot cause problems because I did just that. Anyone can help with this please?
Braves1995 said:
Just recently had this issue pop up. Everything else seems to be running smooth aside from the virtual home button. When pressed, it makes a glow, but doesn't take me to the home screen. Setting a home button on LMT Launcher doesn't work either. Basically, I just have to keep hitting the back button to get Home. Not sure what info one would need about my device to tackle the issue. KFHD7 running the latest CM11 nightly(5/31), Nova launcher with Maromi's 5/19 kernel installed. The issue has come up with two recent nightlies as well as the May 5th Snapshot. I've done a fresh install twice since yesterday and the button will work for a bit, then will stop. I should also mention that I wiped everything possible aside from the bootloader two days ago, reinstalled and same thing, not working! Does downgrading from a newer Nightly to the Snapshot cause problems because I did just that. Anyone can help with this please?
Click to expand...
Click to collapse
The 5/19 kernel does not have the committs from 5/31. You may want to reflash the ROM and wait for a kernel update to flash it.
Sent from my Nexus 7 Flo running CM 11 4.4.2 with ElementalX Kernel using XDA Premium 4 mobile app