Related
We all know that there is a random issue with the keyboard letters being unresponsive randomly (and on random handsets). Sometimes its a delete (backspace) button, sometimes its a letter A or P. The only way to fix it would be putting the phone to sleep and waking it up.
I tried to search for the solution and did not find an answer. I tried different keyboards - the issue persists.
I am running RoyalGinger 3.0
Does anyone know how to fix it? I really love Royal Ginger, but this issue is quite annoying.
I've experienced it too. I made a thread about it, don't know if you've seen it.
But you may wanna take a look as dozens of other people have reported it. Some have found temporary fixes and such.
But here it is.
mackster248 said:
I've experienced it too. I made a thread about it, don't know if you've seen it.
But you may wanna take a look as dozens of other people have reported it. Some have found temporary fixes and such.
But here it is.
Click to expand...
Click to collapse
If you could post your input there as well as to which ROM it has happened to you and anything else would be nice. That way we can kinda have a consensus on what ROM's it's occurring.
I've had this issue since the update to ED01 (or maybe before, I can't remember). Anyway it's darn annoying. I froze the screenshot apk to keep the screenshots from happening but there is still the issue with random back/return button presses. Sometimes it's the home key. Sometimes the search key will long-press and cause voice search to come up. It's mostly the return/back key.
I've had this problem on two Fascinates (the modem died on my first one and was replaced about a month ago). It happened with ED05 and it is now happening (although less frequently) with PWGB EH09 ROM v2.0b3 running ED05 modem. My daughters fascinate was having the same problem on stock ED05.
I've searched through several forums and it seems that lots of people have the same or similar symptoms with the fascinate/captivate as well as with the Nexus S.
I see that google tracked it as a problem earlier in the year and claimed to be working the issue and had a fix that was supposed to be rolled out. Never happened.
I think I've narrowed it down to only happening when the phone is using 3G data.
I'd like to locate and fix the problem but I could use some help getting started. For starters, I'd like to get a development environment set up and running so that I can build and test kernels. I can do this on my own but if someone could guide me so that I don't have to go through that learning curve, it would be appreciated.
My first thought is that it's a driver issue. In the source code there's a folder under src/kernel/drivers named "input" that has a bunch of drivers. Does anyone know which driver is used for this phone?
Thanks,
Dale
UPDATE: 15 Mar 2012:
I added a 100pf capacitor to the interrupt line on the cypress touchkey chip today. Everything works fine now. dmesg shows that I'm no longer getting any false interrupts. I downloaded a 6meg file over 3G and had zero false interrupts. Without the cap there would have been at least a couple of hundred (I use dmesg to check for false interrupts since I have printk statements in my code). I'll keep testing but I think this is it. I'll try to get some pics of the tack on showing where I added the cap. It's some tiny sh-t to work on. I had to do the soldering under a microscope. It was not easy. The cap I put on is a 100pf 50v X7R I bought from Digikey. Digikey part number 445-6856-1-ND. I got a 100 of them for <$6 with shipping.
I'll go back to the driver and remove the software fixes to see if the hardware fix takes care of the problem completely.
The parts are $0.028 each if you buy a hundred. They're less than a penny if you buy thousands. Seems a shame that Samsung couldn't pony up an extra penny to keep this problem from happening in the first place.
For those of you who don't want to crack your phone open, there's still the software (read: duct tape) fix.
Here's a link to the thread showing the hardware mod http://forum.xda-developers.com/showthread.php?p=23725671#post23725671
Yeah a lot of people have tried to fix this but nothing has ever worked. It's a well-known issue.
sageDieu said:
Yeah a lot of people have tried to fix this but nothing has ever worked. It's a well-known issue.
Click to expand...
Click to collapse
Yeah, that's why I'd like to try to fix the problem. Not to dismiss the skills of the other people who have tried, but I'm pretty good at finding bugs in hardware.
Well more power to ya, if you fix it then you will make a LOT of people very happy. You should absolutely get in contact with some developers of kernels (jt1134, sixstringsg, Tk-Glitch, sswek2, etc) if you have any ideas or get anything fixed. I'm sure they will be glad to help you out with the issue and use any of your changes in their kernels.
i have a SGS I9000. my problem is phantom presses of menu and back button. tried flashing to stock firmware etr (original was xeu). installed ics. all with no result. FINALLY found that it occurs only when using packet data (edge) we dont have 3g yet. i ve tried disabling packet data and using wi-fi and there is no preblem.
the diagnosis finally comes to this - problem related with packet data and may be (most probably be) related to software bug in the touch button firmware.
It only seems to happen to me at my house, which is in a low signal area. I'm betting it is buried somewhere in the tower switching code, as my phone switches towers constantly at home.
Sent from my SCH-I500
Yes the problem only seems to occur for me when on 3g and not wifi. I've verified this with the three other fascinates in my house. I'm digging through the interrupt routines now using the kgb kernel source.
Does anyone know which interrupt line on the processor the cypress touchkey device is connected to?
I'm almost ready to break open the phone and start probing with an o'scope.
electric bill said:
Yes the problem only seems to occur for me when on 3g and not wifi. I've verified this with the three other fascinates in my house. I'm digging through the interrupt routines now using the kgb kernel source.
Does anyone know which interrupt line on the processor the cypress touchkey device is connected to?
I'm almost ready to break open the phone and start probing with an o'scope.
Click to expand...
Click to collapse
Hey Bill (I'm also a Bill, heh) :
You'll probably want to check out the changes I did for the V13.1 Glitch kernel. They seem to have at least severely limited the phantom keypresses. I did find some GPIO pins that were configured differently by the dpram driver and the mach-aries.c gpio (and gpio while sleeping) settings, and making those match up seemed to help a lot.
I'm an embedded guy, but more on the software side. I don't particularly want to tear my phone apart and hit it with a scope, but hey .. if you do that and find anything, go for it!
FYI, I was able to determine that the IRQ number used for the cypress-touchkey driver, and the one that's firing during the phantom key events, is IRQ 334 (0x14E). Without having a schematic to look at, though, I wasn't able to figure out what might be causing it to fire, nor even begin to guess why it has something to do with poor signal strength.
Anyway .. I've been beating my head against this problem for a long time .. so if there's anything else you'd like to pick my brain about, let me know.
Downgrade
I have found that the only thing that works is to downgrade. I am however through uscellular so my phone is the mesmerize. I tried talking to a representative about my problem but all they would say is to upgrade. After multiple tries and different methods I downgraded to DI14 from EH09 and I have not had one problem since. Besides one with random menu flashes but it turned out to be the application Zedge. Hope this helps. If not at least I can say I tried.
ssewk2x said:
Hey Bill (I'm also a Bill, heh) :
You'll probably want to check out the changes I did for the V13.1 Glitch kernel. They seem to have at least severely limited the phantom keypresses. I did find some GPIO pins that were configured differently by the dpram driver and the mach-aries.c gpio (and gpio while sleeping) settings, and making those match up seemed to help a lot.
I'm an embedded guy, but more on the software side. I don't particularly want to tear my phone apart and hit it with a scope, but hey .. if you do that and find anything, go for it!
FYI, I was able to determine that the IRQ number used for the cypress-touchkey driver, and the one that's firing during the phantom key events, is IRQ 334 (0x14E). Without having a schematic to look at, though, I wasn't able to figure out what might be causing it to fire, nor even begin to guess why it has something to do with poor signal strength.
Anyway .. I've been beating my head against this problem for a long time .. so if there's anything else you'd like to pick my brain about, let me know.
Click to expand...
Click to collapse
What? _I_ found out that it is interrupt 334! )
Sent from my SCH-I500 using Tapatalk
electric bill said:
What? _I_ found out that it is interrupt 334! )
Sent from my SCH-I500 using Tapatalk
Click to expand...
Click to collapse
Yes, yes you did, lol. And you're probably going to end up fixing the whole thing before i get a chance to look at it again, lol.
ssewk2x said:
Yes, yes you did, lol. And you're probably going to end up fixing the whole thing before i get a chance to look at it again, lol.
Click to expand...
Click to collapse
I've been testing the code for about a day. I added the int test to the interrupt handler just now and I'll test for awhile. I'll prob also put it on my daughters phone since she uses hers about 10x what I do.
Excellent. You're welcome to drop by the glitch kernel thread, btw. I've got some folks testing there with good results so far.
Superclean Rom has screenshot removed. Also Geewiz 2.4.2 has a mod to remove the screenshot, just flash this in recovery:
http://db.tt/xERensX3
It happens when you have a low signal. It's was so annoying but no longer have that issue.
Keep me Fascinated.
It's not just the screenshot that's annoying. When using navigation, the phone will keep saying "this will end the navigation" as if the back button keeps getting pressed. Sometimes the menu comes up as well. Really annoying and kind of dangerous to have to keep hitting cancel while driving. Removing the screenshot app will not fix this. I'm really hoping someone finds a true fix for this. Otherwise I'm getting a new phone soon.
Sent from my SCH-I500 using XDA App
SnrSuave said:
It's not just the screenshot that's annoying. When using navigation, the phone will keep saying "this will end the navigation" as if the back button keeps getting pressed. Sometimes the menu comes up as well. Really annoying and kind of dangerous to have to keep hitting cancel while driving. Removing the screenshot app will not fix this. I'm really hoping someone finds a true fix for this. Otherwise I'm getting a new phone soon.
Sent from my SCH-I500 using XDA App
Click to expand...
Click to collapse
I actually just re-enabled screenshot on my phone. The glitch kernel ( http://forum.xda-developers.com/showthread.php?t=1252871 ) has a fix that they're testing that seems to work pretty good. I'm not sure if it's in their release or just in testing. I think comradesven is putting the code into the kgb kernel too http://forum.xda-developers.com/showthread.php?t=1364912
I've been running my own butchered up kgb kernel for a few days with the fix and it seems to help quite a bit.
electric bill said:
I've had this issue since the update to ED01 (or maybe before, I can't remember). Anyway it's darn annoying. I froze the screenshot apk to keep the screenshots from happening but there is still the issue with random back/return button presses. Sometimes it's the home key. Sometimes the search key will long-press and cause voice search to come up. It's mostly the return/back key.
I've had this problem on two Fascinates (the modem died on my first one and was replaced about a month ago). It happened with ED05 and it is now happening (although less frequently) with PWGB EH09 ROM v2.0b3 running ED05 modem. My daughters fascinate was having the same problem on stock ED05.
I've searched through several forums and it seems that lots of people have the same or similar symptoms with the fascinate/captivate as well as with the Nexus S.
I see that google tracked it as a problem earlier in the year and claimed to be working the issue and had a fix that was supposed to be rolled out. Never happened.
I think I've narrowed it down to only happening when the phone is using 3G data.
I'd like to locate and fix the problem but I could use some help getting started. For starters, I'd like to get a development environment set up and running so that I can build and test kernels. I can do this on my own but if someone could guide me so that I don't have to go through that learning curve, it would be appreciated.
My first thought is that it's a driver issue. In the source code there's a folder under src/kernel/drivers named "input" that has a bunch of drivers. Does anyone know which driver is used for this phone?
Thanks,
Dale
Click to expand...
Click to collapse
Sent from my SCH-I500 using XDA App
I had the same problem...I went to big red and exchanged my phone...well they actually sent me a refurb... this was last week
electric bill said:
I actually just re-enabled screenshot on my phone. The glitch kernel ( http://forum.xda-developers.com/showthread.php?t=1252871 ) has a fix that they're testing that seems to work pretty good. I'm not sure if it's in their release or just in testing. I think comradesven is putting the code into the kgb kernel too http://forum.xda-developers.com/showthread.php?t=1364912
I've been running my own butchered up kgb kernel for a few days with the fix and it seems to help quite a bit.
Click to expand...
Click to collapse
Thanks all u guys. I 'd really appreciate if u could find a standalone fix for this issue i.e. no modded kernel only the touchkey fix. Thanks again.
th3b3 said:
Sent from my SCH-I500 using XDA App
I had the same problem...I went to big red and exchanged my phone...well they actually sent me a refurb... this was last week
Click to expand...
Click to collapse
yeah, I'm on my third phone. there's been some speculation that phones built early (ie when they just started making them) don't have the problem. the data code on mine is 08/05/2011.
dff_jx said:
Thanks all u guys. I 'd really appreciate if u could find a standalone fix for this issue i.e. no modded kernel only the touchkey fix. Thanks again.
Click to expand...
Click to collapse
technically if we change the driver code, which is in the kernel then it's been modded...
If you want to run fully stock ROM and see this problem go away then I think you can add a 120pf cap from the interrupt pin on the cypress chip to ground. I haven't tried it yet but I'm going to as soon as I get done testing the s/w fixes.
Not everyone flashes their phone, but all of us suffer from bugs.
I thought of starting an exclusive thread just for discussing the bugs present on the official SGS2 Firmware.
With the experts here, hopefully they can be clarified, resolved and become history
So, i'll start with the bugs i found.
My firmware version is I9100GDDKL1
First issue
When i get a call and answer it, the screen times out, as the proximity sensor signals it to. But often AFTER the call, and after i take the phone away from my ear to hang up, the screen does not come back again, instead it goes blank black. The call is still on as i am not able to press the end call soft button.
Pressing the home key OR the power key have no affect, it last for 10-20 seconds maybe and then it comes back on its own AFTER the person on the other side hangs up.
Any ideas? This is a sensor, or a software glitch?
Second Issue
Sometimes the phone just loses connectivity. Alot of times its within the city. Its odd, because normally others using the same network do not face this issue.
I have to then manually re-connect to the network.
What issues can these be?
Third Issue
I have noticed this twice now. Phone starts acting funny, as in no signal and does not restore it. I restart it, but when i do, the entire home screen and app drawer is gone. Its blank. All other phone functions work just fine.
I restart again a couple of times, but no luck. So i finally open the back cover, take out the battery, sim and SD Card and put them back again. After that when i switch it on again, it works just fine.
Software or Hardware problem?
This thread is a great idea i think.
My firmware version is I9100XWLP4.
I have only one issue, the same as the first issue in the op, been using this firmware for about a week now, and thats the only problem i have come accross so far.
Any insight would be appreciated.
Thanks
Jesse
My PDA is i9100XWKI4 and GB on it.
First two issues are happening with my SGS2 also, but twice in a week or thrice in a week only. I think proximity sensor have some HW issue.
For calls, even phone shows good signal, but calls are dropped, before I thought it was the problem with other end party, but realized that it is SGS2 problem.
My firmware is i9100xxlpq and I have none of these issues. Maybe you could try flashing the rom I'm using.
Sent from my GT-I9100 using xda premium
Azax said:
My firmware is i9100xxlpq and I have none of these issues. Maybe you could try flashing the rom I'm using.
Click to expand...
Click to collapse
We can solve alot of issues by simply flashing it, but i wanted to know if there is some way that we can solve them with simpler adjustments/enhancements?
Also if we conclude that something is an hardware issue, then we should just go to a service center and get it corrected, shouldn't we?
There isn't a great deal you can do about most 'problems' if you stick to stock & don't root or run custom firmware.
Short of sending it back to Samsung. Who will probably only flash the latest firmware (if there is any) if the problem isn't hardware related. Which you could easily do yourself.
Rooting/running custom firmware gives you the ability to solve problems that otherwise wouldn't be fixable (and definitely produces problems that otherwise wouldn't happen as well sometimes obviously).
I don't disagree with you that rooting/ flashing custom roms will solve most software issues or atleast lead a way to solving them.
All i am saying is, that is there a way to solve some of these problems otherwise.
Also we can find out if our phone has an hardware issue, because if some problem is too uncommon, then it probably IS isolated and can be a hardware fault.
I think all do update their firmware. I Infact changed to the latest one recently, but it didn't do any good.
I am not against flashing man .
Just keeping it as a last resort.
sk1989 said:
I don't disagree with you that rooting/ flashing custom roms will solve most software issues or atleast lead a way to solving them.
All i am saying is, that is there a way to solve some of these problems otherwise.
Also we can find out if our phone has an hardware issue, because if some problem is too uncommon, then it probably IS isolated and can be a hardware fault.
ICS BUGS thread search please we dont need another one .
Hardware is relatively simple if you do not have a problem on GB firmware then it is not hardware .
jje
Click to expand...
Click to collapse
This is not for ICS alone.
You mean to say there can be NO hardware fault at all?
I have a Nexus 4 and I am on Android 4.4. I recently encountered the issue of my soft touch buttons (back, home, recent apps) being unresponsive, the rest of the screen works but my buttons don't respond to touch. I can still slide ip for Google now though.
I tried restarting my device and even upgraded to a newer build of 4.4, no luck.
R u on stock or custom rom? Try to flash stock rom from developer google site.. If nt solved thn go to lg service centr it seems touch problm
Sent from my Nexus 4 using XDA Premium 4 mobile app
parveen75 said:
R u on stock or custom rom? Try to flash stock rom from developer google site.. If nt solved thn go to lg service centr it seems touch problm
Sent from my Nexus 4 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
After some digging, there's a whole Google products forum post on this issue. It's disgusting that Google won't acknowledge it, looks like it's a hardware issue associated with overheating and the 4.4.2 update.
Temporary solution is to use another soft keys app, but I'll have to ditch this phone ASAP, I'm out of warranty and Google will not fix something they caused.
soulcedric said:
After some digging, there's a whole Google products forum post on this issue. It's disgusting that Google won't acknowledge it, looks like it's a hardware issue associated with overheating and the 4.4.2 update.
Temporary solution is to use another soft keys app, but I'll have to ditch this phone ASAP, I'm out of warranty and Google will not fix something they caused.
Click to expand...
Click to collapse
That heat thing sounds odd to me. Do the home buttons work in landscape (With the earpiece to your right)?
lopezk38 said:
That heat thing sounds odd to me. Do the home buttons work in landscape (With the earpiece to your right)?
Click to expand...
Click to collapse
Yes, it does, but the touch input isn't recognized in the developer options. It's all documented here:
https://productforums.google.com/forum/m/#!topic/nexus/7SNIT8xPYzc
soulcedric said:
Yes, it does, but the touch input isn't recognized in the developer options. It's all documented here:
https://productforums.google.com/forum/m/#!topic/nexus/7SNIT8xPYzc
Click to expand...
Click to collapse
As said by many peolple in the thread you posted, it clearly seems to be a software issue :
- problem appeared after an update
- screen zone is fully functionnal with touch input (immersive mode or landscape tests proves it)
as said by parveen75, try to flash stock rom from developer google site (with a version on wich you know didn't have the problem, ie 4.2 ?)
popinterfaces said:
As said by many peolple in the thread you posted, it clearly seems to be a software issue :
- problem appeared after an update
- screen zone is fully functionnal with touch input (immersive mode or landscape tests proves it)
as said by parveen75, try to flash stock rom from developer google site (with a version on wich you know didn't have the problem, ie 4.2 ?)
Click to expand...
Click to collapse
I will try that, but it seems odd that other people would have the problem fixed after a screen replacement, which would identify it as a hardware issue.
maybe the screen replacement method (used by repair services/centers) came with a reset/flash of the rom.
What is even more strange is that some people seem to encounter the same bug again even after a screen replacement.
Please, keep us informed if the flash method solved the bug.
I'm currently still on 4.4.2 (for development needs) and i'm worried i could face the same problem !
I've confirmed that it's a hardware issue and has affected a lot of users who updated. I cannot touch the area of the screen in full screen apps.
Google should be warned and issue a statement about this, this is very bad news for us users.
The fact that it works after a screen replacement with no software modifications is proof enough. Time to vow to never buy a Google product again...
Temporary solution
any one has this problem should download any soft key app
BUTTON SAVIOR IS A good APP
it solved my problem
i advice you to try it
you can try any other app it's not advertisement you can use any soft key app i wrote this name just because i have tried it
good luck every one
I guess many of us have been stuck up with issues where during calls people are not able to hear voice from either side in last couple of days.
Reading playstore reviews of "HTC lock screen" it looks like its HTC who goofed up, lot of people have reported this regression issue.
BTW uninstalling this update did not even solve the issue.
This is just FYI to help folks who are not yet affected.
https://play.google.com/store/apps/details?id=com.htc.lockscreen&hl=en
i called HTC after reading this and they told me that there was no reports of this. I suggested checking out the reviews on the play store. No resolution offered though
Hello
My wife has exactly the same problem with her HTC One !
Any workaround someone ??
I asked her to uninstall the HTC lockscreen update but she says it did not help.
Will we have to re-install ROM ?
Hope HTC will correct this really ugly bug.
LeGrosMario said:
Hello
My wife has exactly the same problem with her HTC One !
Any workaround someone ??
I asked her to uninstall the HTC lockscreen update but she says it did not help.
Will we have to re-install ROM ?
Hope HTC will correct this really ugly bug.
Click to expand...
Click to collapse
Well when I posted it , it looked to me a lockscreen bug(may be its not , i am really not sure).. Some people on play store also said that its a problem with HTC service pack (check out its reviews)
Annoyed and reading more figured out that lot of people said that freezing google play services helped them.
Would suggest you check this thread
http://forum.xda-developers.com/htc-one/help/wip-sound-block-auto-update-play-t2969715
Hope this helps.
LeGrosMario said:
Hello
My wife has exactly the same problem with her HTC One !
Any workaround someone ??
I asked her to uninstall the HTC lockscreen update but she says it did not help.
Will we have to re-install ROM ?
Hope HTC will correct this really ugly bug.
Click to expand...
Click to collapse
Update to the latest Google play services with this version, released yesterday https://play.google.com/store/apps/details?id=com.google.android.gms. Or download apk from here http://www.apkmirror.com/apk/google.../google-play-services-6-5-99-1642632-038-apk/ Problem is solved for me. Also clear cache and data for Google Play Services and Google Play Services Framework.
Every time I get this issue,I used to put the phone on Airplane mode and restart it once or twice
Problem got solved for me
The audio bug from installing an update is new to me but I've uninstalled all new updates weather service pack clock etc due to weather not updating and battery drain issues. As far as audio bug where no one can hear you properly this has been a known issue from the phone being launched and relates to noise cancelling microphone on back of phone. My phone is like this all the time but will try anything to get it working again instead of covering mic on back.
Sent from my Nexus 7 using xda premium
The issue is not just on HTC. It is affecting people with Xiaomi and Nexus phones, at least.
This thread on Nexus 4 seems to be the most up-to-date.
http://forum.xda-developers.com/nexus-4/help/audio-call-nexus-4-cm11-t2924589/page3
For everybody who is experiencing no audio/voice during calls HTC is sending OTA's. I'm not experiencing any problem because I've already updated to 6.09.401.11. And the fix was included in it. <br />
For more info, see this venom rom thread. http://venomroms.com/venomhub-fix-no-sound-calls-htc-one-m7/<br/>
abdulwakil said:
For everybody who is experiencing no audio/voice during calls HTC is sending OTA's. I'm not experiencing any problem because I've already updated to 6.09.401.11. And the fix was included in it. <br />
For more info, see this venom rom thread. http://venomroms.com/venomhub-fix-no-sound-calls-htc-one-m7/<br/>
Click to expand...
Click to collapse
Your lucky I've got this update and its still broke tested the microphones and there working. Having been looking around it seems to be affecting m8 and m8 mini 2 as well. I think this problem has something to do with Qualcomm as its there tech that's used for noise cancellation or whatever it is that's not working properly anyway won't be getting another HTC until this has been fixed I think a known problem that was addressed on m7 then continued on too two other handsets just isn't on.
Sent from my Nexus 7 using xda premium
cokey77 said:
Your lucky I've got this update and its still broke tested the microphones and there working. Having been looking around it seems to be affecting m8 and m8 mini 2 as well. I think this problem has something to do with Qualcomm as its there tech that's used for noise cancellation or whatever it is that's not working properly anyway won't be getting another HTC until this has been fixed I think a known problem that was addressed on m7 then continued on too two other handsets just isn't on.
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
The 6.09.401.11 update must fix this issue. If your phone is stock/non rooted, update your phone, if problem still occurs go into bootloader, select recovery, wait until a red warning sign or triangle appears on the screen (takes a while) then press volume up and the power button. That will take you to the recovery menu. There select wipe cache partition. That might fix your problem.
Yes I am fully stock but this problem has been there since i have had the phone and this is the third handset it has done this on so wiping cache isn't going to do it even though I have done this already I am just unlucky. However there should be more information on this from HTC but there isn't and there isn't any real fix which is annoying will just have to wait until my next phone so I can be heard properly
Sent from my Nexus 7 using xda prem