Related
It happens to me quite a bit when i open up the keyboard..sometimes i'll get just a "t", lots of times "ty." I don't think it's a coincidence that they happen to be the 2 top most centered keys, but I don't think the casing is rubbing and pressing the buttons. Is anyone else experiencing this? It is pretty annoying cause you always have to delete them before you type anything
i get them as well since i last updated (CRC r11.0)
same rom as me...
hmmm....better check in that thread
Mine does it as well using TNT's Rom. I don't think it's rom related, as every ROM I've used has done this.
It may not look like it, but I'm betting your casing it rubbing. I know mine is by using dry erase marker and seeing the transfer on the T and Y keys.
Good luck
lol.. i get them also.. but it only happens sometimes...
im using FARIA-R32-XDA2 rom
Yea, sitting here playing with mine, you're right, only sometimes. Seems it depends how I open the slide, how it torques, etc.
TY
No... It never hppened to me, actually... No matter what ROM I use...
I wish I could help.
Iim sorry...
Cheers.
Your phone is thanking you for installing a new rom! TY!
TY
Hello Together,
I think it is a hardware problem. When push with your thumbs on the bottom of the screen while you slide out the keyboard (this is my normal methode to slide it out) you push the characters T and Y because they are in the middle of the upper row.
I wonder if it is possible to lock the buttons (in software) till the slider is out completely (when the screen rotates). Does anyone know a register or software solution?
Greetings Pudl
yes its a hardware problem...your keyboard cable is a bit loose probably...
you have to take your phone apart to fix that
its the bottom left ribbon cable with a flat silver plate that u need to unplug when u seperate the motherboard
and the screen rotation is activated by some magnetic thingy if i remember correctly
hehe,i also think it's the hardware problem
We finally got Apps2SD, we've got 720p video recording and we have wifi tethering. So just out of curiosity - why people still want to root their phones?
(I think we should leave the custom ROMs case)
Two important things to me are: Market Access/Enabler (I'd be seriously pissed if I couldn't buy apps) and slight modifications to the system like menu button to unlock, ...
Becase even witg froyo app2sd i only have 15mb left.
martintzvetomirov said:
We finally got Apps2SD, we've got 720p video recording and we have wifi tethering. So just out of curiosity - why people still want to root their phones?
(I think we should leave the custom ROMs case)
Click to expand...
Click to collapse
Because using AdamG's OpenDesire 3.0.2 ROM, I have loads of large meg apps installed, like Google Earth, and still have about 138 meg of phone memory left
Dont forget overclocking and underclocking.
Sent from my HTC Desire
The Froyo app2sd is rubbish at the moment, only three apps I have installed at the moment can be moved to the SD card... there for rooting is essential.
Well, you can kinda hack FroYo's Apps2SD Moving ANY app to SD on FroYo (or how to Enable all grayed out 'Move to SD' buttons)
But I agree about the market...
The ability to do full backups and restore them is my main reason
Adblock...?
Because it's fun! Hacking devices to see how far you can take them. I have tons of old phones (mostly winmo) I keep around for hacking.
Why root?
To get rid of the STUPID HTC lock screen and replace it with the standard FroYo.
Piece of sh*t is constantly unlocking itself in my pocket, and you only have to do a slight downwards slide to open it! USELESS!
Adding OpenVPN
Buetooth Wireless Tether (Uses WAY less battery than wifi tether)
Unless of course,someone knows better??
cheers
CQU
So yeah, that's the thrill of it - to hack stuff. I totally agree with that but also I don't want to loose the warranty on my expensive phone and now there are way fewer reasons to root it. So I think HTC did their job well with FroYo.
All of the above for me
ix9 said:
Piece of sh*t is constantly unlocking itself in my pocket, and you only have to do a slight downwards slide to open it! USELESS!
Click to expand...
Click to collapse
Put your phone in your pocket with the power button at the top so that it doesn't get accidentally pressed. Sorted.
Nickedynick said:
Put your phone in your pocket with the power button at the top so that it doesn't get accidentally pressed. Sorted.
Click to expand...
Click to collapse
I always do. My jeans STILL manage to lightly tap the power button then my leg rubbing on the screen still unlocks it!
(before stating the obvious "face the screen to the outside" so your leg doesnt rub, I just can't do it. Lean over a desk and the screen cops the pressure and could crack. No thanks!)
(sidenote: my iphone never unlocked itself, EVER, the power button needed more force, and the slide motion of unlocking could never be done by legrubbing)
For me the number one reason is Gingerbread. I'm happy with the stock ROM and adding customizations is not that necessary (if thou I like it).
But when Gingerbread arrives (Android 3.0) I don't think that HTC will offer it to desire users and then, if I'm rooted, I hope that there will be custom ROMs taking Gingerbread to my Desire.
ix9 said:
Why root?
To get rid of the STUPID HTC lock screen and replace it with the standard FroYo.
Piece of sh*t is constantly unlocking itself in my pocket, and you only have to do a slight downwards slide to open it! USELESS!
Click to expand...
Click to collapse
How do you do this? I also think it's stupid and have the same problem answering calls as I take it out of my jeans (people who wear loose pants might not have this issue).
How is it possible for a capacitive touch screen to get rubbed by jeans and pick up a touch motion?? Arent capacitive screens made only to register contacts from our fingers only? No matter how hard i tried i could never answer a call with something other than my hands.. i just cant understand those discussions.. unless im mistaken ofcourse and a capacitive screen can register touches from other things aswell.. someone enlighten me please?
Sent from my HTC Desire using XDA App
Objects which leads electricity can be used on the screens. I can use my jeans to navigate on my Desire
Sent from my HTC Desire using XDA App
I've started noticing recently that my Incredible 2 touchscreen occasionally goes berserk. All of a sudden it will stop properly responding to my finger and instead whatever is on the screen will start flailing about e.g. a webpage will move around more or less uncontrollably or a list will move up and down in short spurts and sporadically. I almost feel like the movement can be influenced by hovering a finger over the screen without actually touching, almost as if the capacitive screen can sense the electricity from that far. The four capacitive buttons stop doing anything and produce no haptic feedback when touched.
I've found that the surefire way to resolve this is to press the power button to turn off the screen, and then press it back to get to the lockscreen. At that point, everything starts working normally again.
I have been messing around with ROMs, but this problem has occurred on CM7, Mikrunny, and a newly flashed stock.
Any ideas?
Do you happen to be charging the phone when this happens?
I am not. I've read up a bit about that, but my touchscreen craziness starts when it is in my hand, not connected to the charger.
Do you have a custom rom running? If so which one? Did you do a full wipe before flashing?
Currently, Mikrunny. Before flashing a Rom, I would always wipe data, wipe cache, and wipe dalvik cache.
Maybe static electricity? It would explain the hypersensitivity but not really the capacitive buttons not responding.
Sent from my Incredible 2 using XDA App
Do you all think this has to do with flashing different ROMs, or was this type of problem gonna come up regardless of that?
LeoBloom. said:
Do you all think this has to do with flashing different ROMs, or was this type of problem gonna come up regardless of that?
Click to expand...
Click to collapse
Based on the fact that it is happening with different roms it seems to me like it is not related to flashing roms.
Sent from my Incredible 2 using XDA App
Good news. I figured that since most of these issues regarding crazy touchscreens was due to a 3rd party charger being used, then it was likely that it had something to do with the power the phone was receiving, specifically from my battery. For the last 2 or 3 days, I've tried using my phone with the old standard battery (as opposed to my extended), and I haven't run into the problem since. Eventually, I will move back to the extended, but I'm liking the thinness of my phone way too much to switch
Hi, does anyone else experience problems with the screen turning on and off randomly?
I have had this ever since I was out hiking and the phone got wet during a heavy rainfall.
I have tried different ROMs, among Cyanogenmod 10.1 and Android Revolution 31.0, and it sometimes looks like it has been fixed, but the problem always come back. I am worried that it is a hardware fault.
Also I wonder if the on/off switch has got dirt inside that makes it turn on/off by itself.. Any tip on how to clean this button?
Have also installed an app called WakeLock Detector. The "Screen wakelock" doesnt seem to give me any information about why the screen is turned on.. Not many apps that causes screen wakelock..
Any help is much appreciated.
petwussy said:
Hi, does anyone else experience problems with the screen turning on and off randomly?
I have had this ever since I was out hiking and the phone got wet during a heavy rainfall.
I have tried different ROMs, among Cyanogenmod 10.1 and Android Revolution 31.0, and it sometimes looks like it has been fixed, but the problem always come back. I am worried that it is a hardware fault.
Also I wonder if the on/off switch has got dirt inside that makes it turn on/off by itself.. Any tip on how to clean this button?
Have also installed an app called WakeLock Detector. The "Screen wakelock" doesnt seem to give me any information about why the screen is turned on.. Not many apps that causes screen wakelock..
Any help is much appreciated.
Click to expand...
Click to collapse
First of all, this is not something that belongs in the General section, but rather in the Q&A Section...
Now to the problem...
No this is not normal, and shouldn't be happening...
It's very unlikely to be a software problem, and since it got wet, that is what probably caused the damage...
The only way to find out what really is happening is to open the phone...
Since it is a uni-body phone this proves to be quite the challenge but it is possible...
If you are Brave enough you can try it yourself, there are some videos on YT on how to do it, and when you open it check for corrosion on the mainborad, and the cable connections...
IF they seem to be OK, try removing the power button, cleaning it and the actual button below the plastic covering...
If that doesn't solve it ether, well than, it's time to bring it to Repair
Be warned... Taking the phone apart by yourself probably voids the warranty.
OK, guess Ill have to deliver it to service... thx!
Is there any way on kitkat 4.4 to disable my proximity sensor, it acts up when I'm in a call. Its only on this certain ROM and its driving me nuts. If I call someone and they don't pick up, I get a voicemail, but I can't hang up because screen won't come back on. Help plz.
Edit: its not dusty
Sent from my SGH-M919 using xda app-developers app
fateownzyou3 said:
Is there any way on kitkat 4.4 to disable my proximity sensor, it acts up when I'm in a call. Its only on this certain ROM and its driving me nuts. If I call someone and they don't pick up, I get a voicemail, but I can't hang up because screen won't come back on. Help plz.
Edit: its not dusty
Sent from my SGH-M919 using xda app-developers app
Click to expand...
Click to collapse
You can disabled it in TouchWiz. I'm not sure you can in an AOSP rom, which your 4.4 rom is.
It could also just be a ROM bug that hasn't been worked out yet. I'd check the development thread for this rom and see if it's a known issue.
If it is, help the developers by posting a logcat of the problem in the develoment threads. (Because odds are no one else has)
Well iv went thru the threads of the development section, and didn't find anyone else having same problems. So I posted there, and nobody responds to me as usual
Sent from my SGH-M919 using xda app-developers app
fateownzyou3 said:
Well iv went thru the threads of the development section, and didn't find anyone else having same problems. So I posted there, and nobody responds to me as usual
Sent from my SGH-M919 using xda app-developers app
Click to expand...
Click to collapse
You didn't get a response in a development thread because development threads are not for tech support. They are for discussing development. Tech support questions (which this is) do not belong in development threads.
The rest of XDA isn't even for tech support. We are just happy to try and assist if you get stumped. And don't get me wrong, we are legitimately happy to try and assist you. But complaining that it's "usual that no one responds to you" is pretty rude. No one promised you tech support here. If you get help, it's because someone was trying to be nice, not because you are owed an answer.
If you are using an alpha release ROM it's YOU who should be providing tech support to the developers by giving them logcats of your error so they can review them and find out what is causing the conflict. That's how you can help add to XDA and assist the developers who are building cutting edge software for you and giving it away free as a gift.
If you aren't willing to put up with the proximity sensor errors, or to help the developers fix it by providing them with the logs of the error, then your best bet is to move back to a stable build of a 4.3 or 4.2 ROM for another month or two until the major issues with 4.4 are hammered out.
As for asking for help here, what else have you tried? Have you verified that the bug doesn't exist if you revert to a different ROM?
Have you done a full wipe and clean install of the 4.4 rom and tested for the bug immediately, before installing any other apps or user data? Since you are the only one having the issue this could easily be a conflict with some other app that you have installed. The full wipe and test is the best way to confirm that or rule it out.
fateownzyou3 said:
Well iv went thru the threads of the development section, and didn't find anyone else having same problems. So I posted there, and nobody responds to me as usual
Sent from my SGH-M919 using xda app-developers app
Click to expand...
Click to collapse
Same scrap happening with me. The problem is the proximity sensor is always detecting something is in its proximity (most likely dust that got in through the ear piece grill). As a result, the screen turns off immediately when a call is answered, and in Android 4.4 the power or home button can not override this. Interestingly, in 4.3 the power or home button does in fact override the proximity sensor. Why the difference between 4.4 and 4.3 I'm not sure. As Skip Jack alluded to, in Touchwiz roms under settings>my device>call> "turn off screen during calls" can be toggled off to shut down the proximity sensor. If I could find a setting like this in stock 4.4, that would solve this issue.
I need to reflash a 4.4 rom and look for this setting, although I do not think it exists.
I've tried the "pressurized air into the ear piece grill" fix, but it didn't work for me.
Any other suggestions?
https://www.youtube.com/watch?v=zm4f2XjQLAM&feature=youtube_gdata_player
QUOTE=fateownzyou3;47870242]Well iv went thru the threads of the developme, section, and didn't find anyone else having same problems. So I posted there, and nobody responds to me as usual
Sent I rom my SGH-M919 using xda app-developers app[/QUOTE]
Canned air didn't work. So I took my phone apart as demonstrated on YouTube , and when I peeled back the proximity sensor and gesture sensor assembly (they're one piece, attached to the earpiece) i found little bits of sand and dust. A lot. I enjoy the beach in the summer. I cleaned the sensors and the screen area that they are housed in (the part of the screen they "look" out of) with a dry q tip. after putting it all back together its as good as new. *#0*# confirms all sensors now working. The vid above is what I used. You only have to remove sim, sd card, little screws, back speaker, side housing, and a small bracket (in that order) before disconnecting and peeling back the proximity/gesture sensors in order to clean.
You don't have to remove all that other stuff.
I am having the same issue since puttin on CM 11. In 4.1 there was a setting to turn the proximity sensor off but in 4.4 there isn't. I keep looking for an app or something else to trigger it but it is also driving me crazy.
It only happens when my protective case is on my phone, but I am the type of person that NEEDs a case on their phone otherwise itll crack or drown within a couple of days. Any help would be appreciative.
I am having the same issue. Just installed CM 10.2.0-jfltetmo
How do I get a logcat to post? Also, what other information would be helpful for development?
I don't think my issue is sand in the sensor... but I will post back after I open it up and check it out.
If anyone knows of a fix or way to access settings for the proxy sensor, that would be awesome! Also, isn't there a way to use the terminal session to read data from the sensor?
Thanks for any help provided!
Another idea for those who are stuck. I didn't find a way to disable the proximity sensor, but there is another way to hang up a call. If you go into Accessibility options, there is an option to hang up call with Power button. This way you at least have a way to hang up the phone call without having to pull the battery, etc. But it doesn't help if you need to enter additional numbers on the keypad unfortunately. But at least we can hang up now!
I've been having this issue as well which seems to be an aosp bug, but for the mean time, has anyone come up with a solution? Ive tried tasker actions to turn screen on during calls but it seems to be blocked due to the proximity sensor. I know that downgrading to 4.3 is an option but a workaround must be possible. If you find it, Post it.:good:
Edit: Came across this post. Haven't tested yet but it seems promising
Edit2: Wasnt able to get the app to solve the issue as others stated
Hardware fix for proximity sensor
The apps mentioned in this forum and others did not worked for me. My phone is not rooted; perhaps this is required. Apps that I tried are:
Proximity Screen Off Lite
Caffene
I did find the Phone Tester app very useful during the surgery.
I was able to desensitize the proximity sensor as follows. The sensor is made of an IR emitter and an IR detector. It is very sensitive. Small reflections from one side to the other will cause the sensors to show "near" instead of "far."
0. When you look at the Nexus 4 straight on (front camera on top right), of the two elements on the top left, the one more to the right is the IR emitter.
1. Open the phone and gently peel back the proximity sensor/headphone jack (2 + 9 screws; pry plastic and one flex).
2. On the hole corresponding to the IR emitter, apply two small squares of masking tape cut to 1.5 mm x 1.5 mm. Only cover that hole; you do not want to cover the ambient light sensor. The masking tape blocks enough IR to desensitize the system, but won't deactivate it.
3. Gently pry up the digitizer from the phone near the corner when the sensor is. Using a toothpick, apply a drop of superglue just inside the top left corner. Apply pressure and ensure that the digitizer sits firmly on the frame. This is necessary because a slightly separated digitizer will reflect the output of the IR emitter back to the sensor (think about standing behind a window about a foot versus having your nose up to it; you don't see your reflection when you are close).
All this assumes that you know your way around opening the phone and have the correct tools. Sharp objects, execessive force along any step can break your screen or the phone in a split second. If you are not comfortable with it, don't do this.
-PD
i9100 proximity sensor doesn't work
Hi to all!
I have the issue with proximity sensor and didn't manage to find a solution in other similar threads!
The matter is that it is always stay as Released.
In the same time in test screen (*#0*#) there are changing reading for PROXIMITY parameter from 2 up to 240 with no ADC parameter at all. Please look for screenshots. PROXIMITY parameter changes its value when I move my finger in front of the sensor, but as I can understand Android doesn't recognize it because of ADC absence.
Moreover I tried to change proximity sensor for working one (from another phone), but it shows the same as mine (with no ADC readings).
After all I think it is software problem, but I don't know how to solve it. I flashed different firmwares (now it is XWMSE NeatROM v.6.4), but nothing helped.
Please assist! Thanks!
You only need to post your question once. You have it in a more appropriate thread already. Please don't dig up 5 month old threads to multi post your questions.