has anyone been able to find the solution to the problem of knock on double tap ?? since i upgrade from the kit kat I could not find a way to make my phone back to have that feature, someone else would still happening? has anyone been able to find the solution to this problem? and I have another problem. from that time I stopped working that feature, I have a problem with a certain part of the screen at the top does not detect touch, know someone that is? someone else will happen? or is it just me? .... please if anyone has a solution to these problems, I ask you to help me. thank you very much.
the problem with my screen
fanocampo2293 said:
has anyone been able to find the solution to the problem of knock on double tap ?? since i upgrade from the kit kat I could not find a way to make my phone back to have that feature, someone else would still happening? has anyone been able to find the solution to this problem? and I have another problem. from that time I stopped working that feature, I have a problem with a certain part of the screen at the top does not detect touch, know someone that is? someone else will happen? or is it just me? .... please if anyone has a solution to these problems, I ask you to help me. thank you very much.
Click to expand...
Click to collapse
thats the part of my screen not work the touch
Looks like a bad screen. Especially missing that whole section. If it was a corner or something, I would think something like a drop. But straight across, that's not good.
Sent from my LG-LS980 using Tapatalk
Related
Hi Guys,
I am currently using a Cell Pro Rom and I find that my it keeps flipping to landscape too often when I have my phone in portrait.
I always have to give it a shake to fix itself and it does get a bit annoying.
Does anyone know how to fix this?
(I remember I may have (not certain) that I might have changed the Sensor registry when I first got it, but I am not certain, does anyone know the default measurements?)
Any ideas are welcomed.
Many thanks in advance!
Did you ask in the Cell Pro ROM thread? Seems a more logical place to ask. I tried that one out and did not have the issue you are describing. Good ROM too.
There is a G-Sensor Calibration in Settings- System.
kimtyson said:
Did you ask in the Cell Pro ROM thread? Seems a more logical place to ask. I tried that one out and did not have the issue you are describing. Good ROM too.
There is a G-Sensor Calibration in Settings- System.
Click to expand...
Click to collapse
I'm fearing the fact that I may have changed something in the registery as I got all excited the day i got the phone and went through the tweaks in the wiki.
I am not certain if I made any changes regarding the g sensor so I was wondering if anyone knows the defaults or if there is a .cab or ROM to flash to system restore.
Any clues?
Many thanks in advance
To me the g-sensor is a gimmick. I find it annoying and totally useless so I've turned mine off altogether. If I want the screen to rotate I push the keyboard out. I really don't see any use for it.
I did think the only use I had for it was the face down hands free thing but have since decided that I'd be quite happy to push a button for that. Hardly a hassle.
every android rom i install on my tilt has a problem right after i reset the phone i can hear and talk to people but after a short while all sound quits working and the mic doesnt work. any help is apriciated. anyone else have this problem?
What radio are you using?
problem resolved your the best
I really hate this so bad.
When your problem is resolved, type how it was resolved.
I don't know how hard it is, but when you have a problem, someone else will have a problem, and your "problem solved' is useless.
That being said... I have the same problem, can someone help me out?
try changing your radio http://forum.xda-developers.com/showthread.php?t=393182
I've been using the "DK Custom Froyo V4.5.2" ROm for a while now, and it's been behaving quite well. But I just made a call and when it was over the display just stayed black, it has happened a few times before. It's quite annoying since the only solution seems to be to rip out the battery and put it in again.
I'm not sure it's the ROM that's causing this, in fact I don't think it is, but you never know. So wondering if anyone else have experienced this with the wildfire and have a solution for it. I'd rather stay with the current ROm but if a change to another one would fix this problem I'm willing to try it. But I rather stay with a "Older" ROM, just for thefact that wildfire isn't the most powerful mobile out there and I imagine it's more suited and can perform better with a little older ROM.
Greatful for any help.
EDIT: Just found this topic:
http://forum.xda-developers.com/showthread.php?t=921103
Can that be it? I do have a "rubber protection" on it.
http://forum.xda-developers.com/showthread.php?t=674847
Seems like it indeed is the cover that causes it.
Mods can remove this if they like, maybe I shouldn't post it when I have already found the answer but it's been bugging me for a while and maybe someone else will find it useful.
I have my Note 2 set up the same way I had my Note 1 set up (using Dialer One) to make calls.
When I finish a call and take the phone away from my ear, the screen takes much longer to come back on than my Note 1 did.
Anyone else seen this?
same problem here , any solution ?
mjrshark said:
same problem here , any solution ?
Click to expand...
Click to collapse
Do you have the same setup as me, or just the same problem (let's try to narrow it down)?
I don't know if it is the same issue, but my problem with proximity sensor is when using "quick glance" feature...it takes to much to wake up the screen (aprox. 3 sec). I don;t know if it-s the sensor or some other internal settings...
I never used #GNote so I can't tell which one much quicker...
Same problem
I have Galaxy Note 2 on AT&T. I backed up my S3 and restored to it but I don't know if that is the problem.
It takes 3 seconds if I am mid call but I pull my phone down to do something else. My S3 didn't have this problem, and I am NOT using Dialer One. What the hell is the problem, does anyone know?
I have the ATT version and have the same problem.
It is really anoying and hope there is solution soon
If anyone still have this problem, i have a solution. In google market there is an app ''softlocker''. for me solve the problem. And its good for lockscreen when you wake phone from sleep
palicnjak said:
If anyone still have this problem, i have a solution. In google market there is an app ''softlocker''. for me solve the problem. And its good for lockscreen when you wake phone from sleep
Click to expand...
Click to collapse
Can't find it. Anyone else find it?
Galaxea said:
Can't find it. Anyone else find it?
Click to expand...
Click to collapse
Can't find what????
palicnjak said:
Can't find what????
Click to expand...
Click to collapse
Softlocker in the play store. Not there for me.
Please help me with my nexus bad flickering screen... Been experiencing this for months... Anybody experiencing this? Do we have fix for this?
micqutiasol said:
Please help me with my nexus bad flickering screen... Been experiencing this for months... Anybody experiencing this? Do we have fix for this?
Click to expand...
Click to collapse
Looks like a hardware issue - you may need to have it physically repaired.
OrBy said:
Looks like a hardware issue - you may need to have it physically repaired.
Click to expand...
Click to collapse
but how??any video for that?is it in the video card or backlid?
Did you update to 4.4.4
micqutiasol said:
Please help me with my nexus bad flickering screen... Been experiencing this for months... Anybody experiencing this? Do we have fix for this?
Click to expand...
Click to collapse
I had the same problem recently. I thought my little cousin killed it or something.
I read up on the net to see how to fix it. There were stuff like auto brightness, Wi-Fi, etc. Doesn't work.
Then somebody said to disconnect the battery and reconnect which worked for him...no luck for me (tricky taking it apart w/o breaking it).
I tried factory default and nothing.
Then I realized the last time I used this was months ago...Google pushed out an update.
So, I decided to reflashed it back to 4.4.3.
IT WORKED!!!
I tell you, nobody does software testing like they should anymore.
I wasted a couple of days to figure this out and reflash the device.
Give it a try.