Related
Both the on-screen keyboard and the menu keep annoyingly popping up on my Viewpad7. It is driving me crazy.
At some point I thought it had to do with how I moved the device around, but I still think it's a random thing. It was/is a problem before and after loading it with a custom rom.
Is this a known hardware (or software?) bug ? If so, is there a cure for this? I have looked for settings, but was unable to find them. Thank.
SWVer=3.16K
MODEL=FM6-0001
HWVer:103
Android 2.2.2
Hi
Have the same problem and some other users here too.
Seems the Touchscreen/Softkeys are faulty and have to be replaced.
I bought mine 1 week ago and day by day it went worser. I didn't upload a custom rom so far, so it's a stock problem.
Now every 2nd time I take the device it vibrates and menu/keyboard keeps popping up/down. Looks like, the "menu" softkey does his own business, right?
Also the G-Sensor/Compass seems to be defective for me - after a few hours I have to calibrate always.
I made some videos, look at this thread:
http://forum.xda-developers.com/showthread.php?t=1258052
Where have you bought yours?
Regards
With my device it was when I held it in landscape mode and touched the bottom part of the right side or the rightmost part of the bottom of the device itself. It was also HWVer 103. You will most likely have to get the screen and soft keys replaced like I did.
Sent from my ViewPad7 using XDA App
Or, it could be just be a "normal" thing with Froyo OS itself, I've noticed it on 2 newer build - both ITE enabled - in U.S. market.
SWVer=3.41
MODEL=FM6-0001
HWVer:107
Android 2.2.2
This happened only on certain Apps - even when Auto Rotation under Settings are turned off, it will switch to the "opposing" mode and won't go back once it make that orientation change, i.e. YouTube whereas Angry Birds will stay landscape all the time. Device has been calibrated & sensors working, as I had no issues with GPS status & Maps, etc.
Should be a simple fix or patch on the OS or custom ROM .... BTW, I'm running the stock, rooted 2.2.2 ROM while waiting for an OC one with the ITE kernel working to boost the Quadrant scores, LOL.
Ours seems to be more a hardware problem since it happens anywhere, with autorotation on or off, after a complete hard reset (without any additional apps installed) and simply by touching the case itself (not the screen)...
astuermer said:
Ours seems to be more a hardware problem since it happens anywhere, with autorotation on or off, after a complete hard reset (without any additional apps installed) and simply by touching the case itself (not the screen)...
Click to expand...
Click to collapse
Hmmm, interesting after I checked out a few YouTube videos & it sounded like it's all HWVer 103 yet running Froyo 2.2.2. Is the device ITE enabled as I noticed that the pop-up keyboard is "standard" whereas mine has Swype style keybaord with ITE.
It's a pain to get it returned, exchanged & repaired at the authorized factory service center and be without the use for 2+ weeks, unless one's within a 30 days period & can send it back to the place of purchase for a new one (could take just as long)
Another post mentioned a new stock ROM just being released, it might be worth an effort or try to flash it (FM6-3350-0-1008-A01.nb0) upon downloading & using the SUTL3 app to do it - would need to root it again - if one is brave enough (since it's going back for repair/exchange anyway?)
BUT, I'm guessing whether this newly released stock ROM is for ITE devices vs. non-ITE ones with HWVer 103, 106 and 107's ???
The button clicking by itself or when under vibration is an HW fault.
pulling the back off and wedging some paper near the touch IC to keep pressure on it has fixed mine.
Brought it back to the store for repair. I think they put a new screen and cover (back) on it. Works like a charm.
flez1966 said:
The button clicking by itself or when under vibration is an HW fault.
pulling the back off and wedging some paper near the touch IC to keep pressure on it has fixed mine.
Click to expand...
Click to collapse
Can you describe more precisely how and what did you do or can you (better) do some photos?
Did you pulled off a back cover and inserted a piece of paper somewhere?
Need to experiment
Software solution
This is a solution from a user 'retrochip' from 4pda.ru forum
(Link to original post in Russian and i'm not able to post is here)
1. Root your device (can be done with Gingerbreak)
2. Find out codes for Menu button and Search button (229 and 217)
3. Edit configuration file /system/usr/keylayout/qwerty.kl (you can use RootExplorer)
In qwerty.kl:
Find text:
key 217 SEARCH WAKE_DROPPED
and change to:
key 217 MENU WAKE_DROPPED
Find text:
key 229 MENU WAKE_DROPPED
and change to (just comment it with #):
#key 229 MENU WAKE_DROPPED
Save and reboot.
Now Menu button isn't active and Search button works as a Menu button.
No annoying random popping keyboard anymore.
This has killed my all soft buttons, now the only option is to fix it in adb, because screen keyboard doesn't appear in terminal, I need to touch menu then screen keyboard.
So I'm using the CM11 4.4 Kitkat on my Galaxy S4 and recently found out that my proximity sensor isn't working (when I dial the screen goes black and won't turn on until the call is over). I've read many threads about fixing it but I think it's broken. So all I want now is to disable it but there isn't such option in the Cyanogenmod. Is there anyway to disable it, like with a terminal or something?
bump
bump!
with root explorer go to system/lib/hw and go all the way to the bottom to the last sensors file. its an so file. long press on it and open in text editor. somewhere in the page almost at the bottom you will see where it says ProximitySensor then on one of those line it should say mEnabled. just rename it to mDisabled, then reboot and the proximity sensor is fixed.
qman66 said:
with root explorer go to system/lib/hw and go all the way to the bottom to the last sensors file. its an so file. long press on it and open in text editor. somewhere in the page almost at the bottom you will see where it says ProximitySensor then on one of those line it should say mEnabled. just rename it to mDisabled, then reboot and the proximity sensor is fixed.
Click to expand...
Click to collapse
I know this is an old thread but qman66 you are AWESOME! Was going nuts trying to fix the proximity sensor problem. Ran the commands in terminal emulator that recalibrates the sensor, didn't work for me. Blasted the speaker with compressed air, also didn't work for me. But this method allowed me to disable the proximity sensor while still using an AOSP rom. I will send the phone in for warranty eventually, but I thought I was going to have to use a touchwiz rom until then (touchwiz has the option of disabling the proximity sensor in the call menu).
And I read like 5 or 6 different threads dealing with the Galaxy S4 proximity sensor issue and no one else posted this method before.
kg2128 said:
I know this is an old thread but qman66 you are AWESOME! Was going nuts trying to fix the proximity sensor problem. Ran the commands in terminal emulator that recalibrates the sensor, didn't work for me. Blasted the speaker with compressed air, also didn't work for me. But this method allowed me to disable the proximity sensor while still using an AOSP rom. I will send the phone in for warranty eventually, but I thought I was going to have to use a touchwiz rom until then (touchwiz has the option of disabling the proximity sensor in the call menu).
And I read like 5 or 6 different threads dealing with the Galaxy S4 proximity sensor issue and no one else posted this method before.
Click to expand...
Click to collapse
glad someone found this useful.
While this fixed the call locking problem, it also disables a lot of other hardware sensors. The only one I'd care about is the gyroscope for rotating the camera and watching videos full screen. Any solutions?
sjschoo said:
While this fixed the call locking problem, it also disables a lot of other hardware sensors. The only one I'd care about is the gyroscope for rotating the camera and watching videos full screen. Any solutions?
Click to expand...
Click to collapse
Yeah I noticed that, the best solution is to get the proximity sensor fixed in the end. Then you don't have to disable anything. If your lucky it doesn't even need to be replaced, just cleaned. For me I can live with no rotation, because the screen off during calls is a ridiculous PITA by comparison. Also apps can force landscape mode even with the gyroscope not working. I use force landscape for videos through mx player, and mango reader for manga.
I finally broke down and took the phone apart. There were no warranty stickers to break so assuming you don't mess up royally, it shouldn't effect your resale value. All it took was an eye glass screw driver and a q-tip. Once I was inside I tried the can of air first, but didn't help. Swabbed the back of the glass with the q-tip and that finally provided lasting relief.
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!
khudko83 said:
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!
Click to expand...
Click to collapse
Changing the rom isn't going to do anything, even factory roms (I've tried it). If a replacement sensor doesn't fix it for you, then it's going to be hard to fix it yourself. All the posts I've seen so far have cleaned the sensor or replaced the sensor and fixed the problem. Otherwise people like me just turn the sensor off.
You were right, proximity software fix didn't help! But how is it possible to work in this (the same wrong) way with changed sensor? Can it be some main board hardware problem? But it doesn't look like this...
Sent from my GT-I9500 using XDA Premium 4 mobile app
Maybe somebody knows how to fix the issue???
Finally fixed
Thanks so much qman66 I have had problems with my proximity sensor on my JFLTEXX pretty much since I got it. Had been using the xposed disable proximity sensor module but xposed doesn't work with CM12. Your simple system tweak has given me use of my phone know call options again
qman66 said:
with root explorer go to system/lib/hw and go all the way to the bottom to the last sensors file. its an so file. long press on it and open in text editor. somewhere in the page almost at the bottom you will see where it says ProximitySensor then on one of those line it should say mEnabled. just rename it to mDisabled, then reboot and the proximity sensor is fixed.
Click to expand...
Click to collapse
Hi, I tied to do this but it says I can't save the changed so file... Can you let me know which root explorer and text editor you are using?
Thanks massively
Not a text file
qman66 said:
with root explorer go to system/lib/hw and go all the way to the bottom to the last sensors file. its an so file. long press on it and open in text editor. somewhere in the page almost at the bottom you will see where it says ProximitySensor then on one of those line it should say mEnabled. just rename it to mDisabled, then reboot and the proximity sensor is fixed.
Click to expand...
Click to collapse
I found sensors.msm8960.so with many references to proximity sensor but it is not a text file!!
Samsung S4 Active w LOS 15.1 (a&Droid 8.1) - how to disable HW sensor(s).
Hi All
Hope some here will help me stay afloat long enough to learn to surf by myself; bit of a noob in this wild ocean here (more of a 'fresh water/indoor pool' kinda dude I guess) - but trying to break out of tis little pond and learn to 'surf'. Anyway, to the point:
1. HW spec
Samsung Galaxy S4 Active
GT - i9295
TWRP 3.3.0-0
Lineage 15.1 20180227 jactivelte
(sometimes with opengapps pico and addonsu15.1 but mostly just LOS and addonsu nothing else)
2. Have the sensors on phone covered up with black electrical tape - all but the notification light are covered and it's gonna stay that way - NOT negotiable!
Obvious Issue: Have the blank screen during phone call problem. Can end calls using power button but I need to use the keypad quite often so need the screen to stay on. How? Ideally want to (SW) disable most if not all hardware sensors - how?
Tried a few fixes but no luck, e.g.:
(a) adding 'the' fix/control many sensors apk no good as not suported under 8.1 (plus want to find out how to do manually myself not use 'hand outs').
(b) edit selected sensor etc ".so" (eg in system hw) files - so far not resulting in the disabled ProximitySensor.
So, I really want to hack this myself at cmd line level, am ok with that (many years IT ops/admin experience in 'fresh water commercial space'). Can mount system using TWRP then adb shell to connect and find and grep for stuff in files but cannot find setttings I need to change to disable sensors for good. Where to look/find more info?
What do I want to achive:
Make calls and have keypad stay on all the time or give me manual option to turn screen on/off with a hw button during call.
How:
I am happy to disable pretty much all sensors (proximity, gyro, compass etc) in system or firmware memory so that I am free from the overlords and really want to be able to use the keypad during calls - and have option to manually turn screen off/on during call would be cool.
Constraint:
Really want to do this from (a) cmd line or (b) edit code/recompile (learning curve) the LOS 15.1 or whatever to disable sensors for good. I will be using this old thing mostly for just call and txt not much else - and cannot be asked to buy an old Nokia handset.
Thanks,
iHAL8999.999... (hi dave...)
(Pretty much a crosspost from /r/Xiaomi cause I got no answer there):
Per the title: Once I had finally gotten past that Error 86006 stuff with bootloader unlocking and such, I immediately went to flash some custom ROMs on my Vince (since that was honestly what I had bought it for). One of the things I enjoy about those custom ROMs is that they often have the "Hold volume key to change tracks" function while the screen is off. Unfortunately, with any ROM I've tried so far (AOSPEX Official [7.1.1], LOS 15.1Unofficial [8.1.0, Non-Treble], RR 6.0.0 Unofficial [8.1.0 Non-Treble]), I've had an issue of my headset's buttons not functioning properly.
(Using CTIA/Android-compatible headsets [that also worked fine on my Kenzo]), whenever I press the top button, it acts identical to a middle button press, something I confirmed through the use of a KeyTest app I found on GitHub, showing a scancode 226 [HEADSETHOOK] for both top and middle buttons, while the bottom button was reporting as scancode 257 [BUTTON_2]. Not gonna lie; I don't really know the implications of that besides the fact that my top/middle buttons are essentially clones.
What this results in is: my top (and middle) button does the standard pause/play/skip track thing while my bottom button does weird stuff - sometimes acting like a "Tab" key would on Windows, selecting various boxes and then clicking on them. (Still not sure what it's doing.) This has been the same across 4 different headsets and it's becoming a bit irritating. I found some people with the same(?) issue with the Mi 2 and Mi Max 2, but the Mi 2's solution included some kernel tweaking for headset button electrical resistance (and I compared the values between the vince kernel dump and the ROM kernels and they seemed to be the same, so I dunno) while the Mi Max 2's solution involved some editing of the Generic.kl file in /system/usr/keylayout but that didn't work for me either. Has anyone else come across this issue/found a fix?
tl;dr: headset buttons aren't doing what they're supposed to in every single non-MIUI ROM I've flashed - some 7.1.x/8.1.0. Does anyone have a fix/the same issue?
I has same problem with 3 different headset. Non of them were working and no solution.
Same here. Any workarounds?
So as all you may know, most of the new custom ROMs come with fingerprint navigation gestures, which sometimes don't make sense because the soft keys are already enabled.
Sometimes this is annoying because we touch the fingerprint sensor accidentally, or want to set up another gestures, like turning screen off by long-pressing the sensor.
I noticed this annoying thing on LineageOS, Pixel Experience, AOKP and RessurectionRemix.
So how can we set another gestures? If it's by generic.kl (which i tried unsuccesfully), what do we have to do?
Is there an app that can control it?
Thank you all
maathps said:
So as all you may know, most of the new custom ROMs come with fingerprint navigation gestures, which sometimes don't make sense because the soft keys are already enabled.
Sometimes this is annoying because we touch the fingerprint sensor accidentally, or want to set up another gestures, like turning screen off by long-pressing the sensor.
I noticed this annoying thing on LineageOS, Pixel Experience, AOKP and RessurectionRemix.
So how can we set another gestures? If it's by generic.kl (which i tried unsuccesfully), what do we have to do?
Is there an app that can control it?
Thank you all
Click to expand...
Click to collapse
Hey,
maathps said:
So as all you may know, most of the new custom ROMs come with fingerprint navigation gestures, which sometimes don't make sense because the soft keys are already enabled.
Sometimes this is annoying because we touch the fingerprint sensor accidentally, or want to set up another gestures, like turning screen off by long-pressing the sensor.
I noticed this annoying thing on LineageOS, Pixel Experience, AOKP and RessurectionRemix.
So how can we set another gestures? If it's by generic.kl (which i tried unsuccesfully), what do we have to do?
Is there an app that can control it?
Thank you all
Click to expand...
Click to collapse
maathps said:
So as all you may know, most of the new custom ROMs come with fingerprint navigation gestures, which sometimes don't make sense because the soft keys are already enabled.
Sometimes this is annoying because we touch the fingerprint sensor accidentally, or want to set up another gestures, like turning screen off by long-pressing the sensor.
I noticed this annoying thing on LineageOS, Pixel Experience, AOKP and RessurectionRemix.
So how can we set another gestures? If it's by generic.kl (which i tried unsuccesfully), what do we have to do?
Is there an app that can control it?
Thank you all
Click to expand...
Click to collapse
Hey, i saw your this comment today and i hope you have somehow fixed this issue, i am facing the same one, kindly tell me if there is any way yo totally stop those fingerprint gestures, and only use fingerprint to unlock the device.
Hello guys,
on the Redmi Note 10 Pro I saw the double tap fingerprint sensor option in the settings.
Why isn't this available on the Mi 11 Lite?
The sensor should be the same....
I'm only having the first 4 options, the last one is missing completely.
Thanks in advance!
Well ask xiaomi, it's their decision what features each device gets.
Is there some way for use gestures in the fingerprint sensor for doing things?