My phone quite regularly thinks the search button has been pressed and Google now opens up waiting for a search query.
Before Jellybean the old Search dialog would pop up. This happens quite often, Usually 5 - 10 times per day. Every ROM I have tried - this issue occurs in, from Stock to NexusMV and more recently Codename Android.
The issue was around back in Gingerbread days but I seem to remember a fix and it went away for awhile (Has been back Since ICS for me)
Does any one know if there is something that can be done to resolve the phone wanting to search? I have even tried disabling the hardware search button in advanced settings of Codename Android.
Seems an hardware issue to me. If that, you can try to remap the search button to nothing with "Button remapper" http://forum.xda-developers.com/showthread.php?t=850464.
I don't have CNA so I can't say if disabling it in hardware settings is working or not.
Flash cna ROM, and change search key press and longpress to nothing in settings.
Sent from SpeedMachine i9023
Yes, it's a hardware issue and has been discussed intensively elsewhere. For me it was the Home-button, but most had issues with Search. Easiest is to remap by editing /system/usr/keylayout/cypress-touchkey.kl, just use a text editor with root access. More info here: http://source.android.com/tech/input/key-layout-files.html.
Alternatively, check this thread (haven't tried myself since JB solved the problem for me): http://forum.xda-developers.com/showthread.php?t=1815071
Back when I 1st bought the phone there were a lot of i9020As that did this and it was NOT a hardware problem but a baseband issue. A root and radio flash fixed it for me. Since then I gave the phone to the daughter and put it back on stock which was by then ICS so no more Search popup bug.
on the other hand after rereading the OP has been to other ROMs so maybe this time it is hardware but I'd take a close look at the flashed radio.
Thanks for the replies,
I tried loosening some screws on the back of the device as well as flashing a new Radio. I remember when I first got the phone well over a year ago I had flashed the radio to I920xxKD1, and never touched the baseband again.
Today I flashed Radio UCKJ1, and have not seen the issue happen yet.
Related
I occasionally get into a mode where the hardware keyboard is non-responsive. Nothing on it works. I'm not sure if this is a defect on my particular phone, or if I've accidentally enabled some "feature" that causes the keyboard to be locked out. A soft reset will fix the issue, but that can be very annoying...
Has anyone else seen this?
Ken98045 said:
I occasionally get into a mode where the hardware keyboard is non-responsive. Nothing on it works. I'm not sure if this is a defect on my particular phone, or if I've accidentally enabled some "feature" that causes the keyboard to be locked out. A soft reset will fix the issue, but that can be very annoying...
Has anyone else seen this?
Click to expand...
Click to collapse
I have experienced this before, where the backlight wont even activate from pressing a button, and the keyboard certainly isnt typing anything on the screen either. Although usually i can fix this by sliding the keyboard back in, and then out again.... annoying yes, but its only happened twice in the month i have had my ATT Fuze, and i havent had to reboot like you mentioned.
When running my stock AT&T rom, I had this happen almost daily. Now that I flashed a new rom, I have yet to experience it again. I had to turn off/on my device in order for it to go away before.
Same problem here.
Sliding in and out does not work any more.
Resetting doesn't work anymore either...
Time to flash to original Roms?
Keyboard lock up
This happens to me too. I noticed that it happens more frequently when I set my wifi to best performance, and then try to type something. Keyboard becomes completely unresponsive. I usually have to soft reset.
I had the problem with stock ATT rom, NATF rom, and now with RRE 4.5SE Rom. I have tried the T9 dissabler, but it also did not work. My Fuze is only a few days old...
I notice this seems to be a common problem... No one seems to have answered this in any of the posts I've read. Is there a cab or patch or reg tweak that some one has come up with to deal with this? Can some one look into this???
Thanks so much in advance!
Mitch
*Edit*
Forgot to mention that this my second Fuze, sent the other one back because it was doing the same thing...
same unsolved issue here (wants me to crack my fuze)
Ive noticed this too... but what I do to correct the problem is hit the window key. It then activates the start menu. Then press it again to exit the start menu and the keyboard magiclly works again. At least for me anyway.
I have this problem occasionally, maybe twice with the ATT stock ROM, an once with the RRE 4.5SE ROM, mine rights itself after the application is closed and re-opened after a minute or so, so Im not that bothered, it is annoying though.
Nice, I'll try that..
Try the NATF ROM
Since I've switched over to the NATF ROM I haven't had a single problem with the keyboard.
tried NAFT v4 already with the same hq keyboard lock/die/shut down issue
Ken98045 said:
Since I've switched over to the NATF ROM I haven't had a single problem with the keyboard.
Click to expand...
Click to collapse
Same issue here, happened with both stock rom and NATF 4.1
It goes away after doing some random things like others have mentioned, but still annoying.
My keyboard was working fine all this while until about 2 weeks ago it starts to act up. When I press the spacebar, sometimes it will create double spaces (instead of the usual one), and sometimes, it wouldn't work at all (meaning no space is created).
Does anyone else have this problem?
And just wondering, I have flashed my TP to ROMeOS, so if I were to claim warranty, does that mean I'll have to re-flash my TP back to the original firmware?
Bump - I really need some help.
Bump again! Mine is doing this at the moment. Stock ROM. UK Vodafone.
As far as going back to get it fixed by someone, yes, you would have to go back to stock SPL and stock ROM. It sounds like a pretty strange problem. The only thing I could think of is that you have some particles stuck underneath the space key since it's acting s erratically.
same problem here. I don't think that it is particles under the keyboard as that would not explain the double spacing issue.
I only noticed it on the R2A rom, don't remember it being there on the R1 so prob a rom issue.
I have this problem too
Figured I'd give this a good Ole Bump, because it seems that, although not widespread, it's still an issue. I'm running the Latest 6.5 ROMeOS on my Fuze and am having the SAME problems mentioned in the first post. I remember reading in Da_G's thread that there was something corrected in his ROM by using a custom xT9 dictionary? Anyone have any input? I'm (almost) positive this is not hardware related. It seems to be tied to the OS. Thanks in advance.
me too having the problem as well, i've it for more than 1.5 months i think, and no one having this in the earlier day which no one can help me out with it, but this few days i think i manage to solve this problem already, which i think it actually is a hardware issue, i used to use my right thumb to press spacebar and the problem occur, but since few days ago i try changing it to use my left thumb to press spacebar, who knows, the problem did not come to me since then... maybe you can try this, if not, i think you might gonna sent it back for warranty... hopes this helps...
I'm almost positive it has something to do with xT9. I just used a cab from my tilt days to disable xT9, and its happening FAR less than it was. But its still happening lol. Even with the regular stock non-finger-friendly keyboard set as the SIP. Back to the drawing board.
Well, I'm not sure if everyone else has read and figured out the problem, but it is now known what causes the spacing issue.
Apparently the newest builds have changes to the compime.dll file. These changes are what is causing the spacing problems, and (so far) can only be resolved by using the compime.dll from build 21731 or earlier. So how do we fix this
I know that Da_G has a package in his kitchen to change the dll back to an earlier one, but for the people that are using already cooked roms, what do we do?
djcaston said:
Well, I'm not sure if everyone else has read and figured out the problem, but it is now known what causes the spacing issue.
Apparently the newest builds have changes to the compime.dll file. These changes are what is causing the spacing problems, and (so far) can only be resolved by using the compime.dll from build 21731 or earlier. So how do we fix this
I know that Da_G has a package in his kitchen to change the dll back to an earlier one, but for the people that are using already cooked roms, what do we do?
Click to expand...
Click to collapse
If that's the problem, then this post might help you.
EDIT: But someone noted this problem with their stock ROM, which suggests a hardware issue, not a ROM problem.
I thought I'd post this since clearly I'm not the only one who suffers from this problem. After 6 months of living with this problem, I've decided to flash back to stock SPL and stock ROM and sent it to SiS for repair. They replaced the keyboard, and in just 2 days, I got my phone back (talk about a speedy repair!).
I don't know about you guys, but I'm almost positive mine is a hardware problem. I'm now using a WM6.5 TF3D2 ROM by shep211 and the keyboard seems to be working perfectly.
-accidentally double posted-
i got the same problem.
spacebar sometime can press sometime cant.
i think is hardware problem
anyone can guild me how to open n repair it?
my touch pro is not under sis. too bad.
Mine's been doing the same thing recently. I'm *hoping* this is an os issue, but I'm using stock original bloat free rom.
My has also been acting up tho (goofiness with Opera, rare and seemingly random shut offs and freezing) so I was hoping that a flash to a cooked rom would fix it.
I'm planning on doing it this weekend, if I get around to it I'll post here on my results.
I had the same problem. Went to the AT&T store and got a new phone
I too have been having this problem. I have been using NRG's roms for the past month (no blame on them) and the problem started to occur. Whenever I texted i would hardly ever get any spaces and it would double space when i did get it to work. I found that if i went slower and pressed harder it would work fine, however this is not a good solution. So i figured it was a hardware problem so i put everything back to default for ATT warranty purposes.
This is where it gets weird, the dumb thing starts to work again. I thought it was pure hardware failure because i had to press harder, but now that problem was gone.
So now I am running stock ATT rom but it is starting to double space ALOT. However this only occurs in the text message box. If i open word and type it is flawless. So is there a glitch in the text messaging program?
same problem here... happens when texting in my browser, in forums, in sms msging, all over...
I have a Samsung Omnia with a WM 6.5 build, and I noticed a similar problem, regardless of which onscreen keyboard I use. Basically whenever I type a dot (.) or press the spacebar, the previous letter would get selected (underlined) for a second, before the caret returns to the intended position. Typing the spacebar in a browser would indeed produce 2 spaces.
I assume it's related to the input/dictionary suggest feature, yet dis-/enabling this feature in the settings doesn't fix the problem. My guess is that the dictionary somehow thinks that a single spacebar press is a correct word, which is automatically expanded to the full word (1 space), followed by another space to put the following word.
This issue surfaced at some point (the rom initially worked fine after a hardreset).
same issue on my phone
Okay, so shortly after flashing CM7, every five minutes or so a key on my (Gingerbread) keyboard stops working. After trying some things (like pushing a little harder, clicking other things) it works again. But then it happens to another key! I think I read one thread somewhere on the internet with some people saying using a different fixes the problem.. But I don't think it does :/ And I can't find any other threads about this problem. I can't even find that one again! Has anyone else been experiencing issues like this? Is this a problem with the ROM maybe? Things worked fine on all of my other ROMs, and the stock ROM. I'm really worried, and I hope this isn't a permanent issue. Sending my device back to get replaced would be really screwy for my schedules. I'm using an Inspire 4G btw, if that matters to any of you.
Anyone? Any tips? I can't tell if it really is a hardware issue or software
Sent from my HTC Inspire 4G running Cyanogenmod 7
I have this issue with my stock inspire along with several others. Every now and then a key gets stuck and will not respond. I have to re-boot my phone. Right now I am using swype and so for it has not locked up any keys as of yet for about a week. It was happening to me approx once every 7 to 10 days. No fix that I know of. Hope they correct this issue with 2.3
I second the Swype keyboard - can't live without it!
:side note:
I'm using the latest version (I think) and the only issue that I've had is when I reboot the phone, sometimes the keyboard will work but the swiping feature will not (blue border flashes around the keyboard instead of posting the word I spelled). The fix is easy - go to Language and Keyboard, uncheck the box for Swype, run the Swype installer, click Enable swype, select it as the keyboard when the installer pops up the box for Input Type, and you're good to go (if it ever happens).
My search button is flickering, firing itself off in bursts, and I want to completely deactivate it. The flickering was/is apparent in Clockwork recovery --> Key test as well.
It first happened using a 2.3.4 deodexed rom (been using it for a month or so, but all of a sudden it started firing off), then I flashed a CM7 based rom which completely killed the button. I figured it was a hardware issue, but to be sure I flashed an ASOP rom (ZuluZulu) and after a couple of hours of use the search button button started firing off again. Between the periods of bursts, the button is as dead as ever, meaning it's lit, but does not respond (haptic feedback, opening the search app) at all.
Since I don't use the button at all, deactivating it completely would not only resolve the issue but save me the trouble of accidentally hitting it once in a while as well
I've searched a bit and found this answered thread over at Google: http://www.google.com/support/forum/p/Google+Mobile/thread?tid=49e8ca84071d51a4&hl=en
TS 4/21 said:
I have a nexus s running 2.3.3 and I will be using it normally and all of a sudden it will start a voice search without reason but, it opens and closes it really fast for as long as it wants. It only stops when I lock the phone and it does it in all my apps. I don't want to have wasted my money on a p.o.s phone just cause i can't stop it from wanting to search. Help it happens all day and more than ten times a day.
Click to expand...
Click to collapse
Google 6/3 said:
Hello again everyone,
Good news -- we've identified the source of this problem which is entirely software based. We're developing a fix which we can deploy with an over-the-air update. I don't have a timeline for when that'll happen yet, but when it's ready I'll let you know.
Click to expand...
Click to collapse
I don't know if it has anything to do with anything as not even wipe + re/flash different roms changes it though.
Does anyone else have the problem where the recent apps/task switcher doesn't actually show the latest app? It usually does if I back out and then hold the back button again. For example, if I'm in Internet and switch to Messaging then hold Back, Internet doesn't show up in the switcher. If I tap back and then hold back again, it does.
Also, most of the apps don't show actual screenshots. They just show a black square.
This has happened with a couple of different ROMs, but I don't remember if it did it while stock. Is there a fix?
Anyone?
I also had this issue when I was on 4.1, but not on 4.2. I have 3 people in my family who have stock rom and also have this issue. I have been trying to search for a fix, but your post is the only thing that showed up. Have you found a fix yet?
nonnarb said:
I also had this issue when I was on 4.1, but not on 4.2. I have 3 people in my family who have stock rom and also have this issue. I have been trying to search for a fix, but your post is the only thing that showed up. Have you found a fix yet?
Click to expand...
Click to collapse
Nothing. Seems to happen on all TW ROMs that I try. I switched to an AOSP 4.2 ROM for a bit, but realized it wouldn't work with my Fitbit and switched back to TW before I noticed whether it was affected.
It has to be a problem with 4.1 because I've always had this problem, even on my gnex when I was running 4.1. When I was on 4.2, it didn't happen once. It's quite annoying, but must have been fixed with 4.2.
Sent from my SCH-I535 using Tapatalk 4 Beta