TL;DR: I have a hunch that the SAR sensor is related to touch issues, which I observed by experimentation. Is there a way to tell the system I am holding my phone regardless of SAR sensor readings? (always set SAR value above threshold)
SAR - Specific Absorption Rate
Hello everyone, I posted this since i can't seem to find solutions or maybe I have just overlooked it.
As we know, Pocophone is well known to have touch screen issues, in which I have observed in my unit that it shows the issues whenever I am not holding my phone. Later I have discovered that this phone has a SAR sensor, which I think might be the cause for this touch problem since I tried holding the phone while not triggering the SAR sensor and my touches where not registered most of the time, and only registering if I press it hard. When I held my phone while triggering the SAR sensor, the touches worked properly again.
Is there a way to always send data that I am holding my phone? (i.e.: always send a "held state" regardless of SAR reading?)
SAR readings are accessible on : Settings > About Phone > Kernel Version tap 3× to enter CIT > scroll to the bottom #35
aztigin009 said:
SAR readings are accessible on : Settings > About Phone > Kernel Version tap 3× to enter CIT > scroll to the bottom #35
Click to expand...
Click to collapse
I did the SAR test. CS0 ranges between 2900 to 3400 when holding with one hand on the top. When I approached the other hand to the bottom of the phone CS0 ranges from 12000 to 14000.
CS2 is always at 22000.
I never had any touch screen issues on my Poco. Not with Android 8.1 nor Android 9 none of the miui 10 updates had touch issues, I am currently on 10.3.6
Most of the time I am wearing rather thick rubber gloves and I'm not holding the phone, it's just laying over a metal or plastic surface.
I hope it helps shedding some light into your suspicions
Cheers
Thank you so much for yur response!
Maybe this is not a more general issue as I had initially thought, since I considered this when I read about other people having touch issues when they don't touch their units.
TheBlackening said:
I did the SAR test. CS0 ranges between 2900 to 3400 when holding with one hand on the top. When I approached the other hand to the bottom of the phone CS0 ranges from 12000 to 14000.
CS2 is always at 22000.
I never had any touch screen issues on my Poco. Not with Android 8.1 nor Android 9 none of the miui 10 updates had touch issues, I am currently on 10.3.6
Most of the time I am wearing rather thick rubber gloves and I'm not holding the phone, it's just laying over a metal or plastic surface.
I hope it helps shedding some light into your suspicions
Cheers
Click to expand...
Click to collapse
RESOLVED
The root cause has not been found but the latest update (MIUI Global 11.0.5. 0) fixed this touch issue.
My SAR reading are a bit different from before, which maintains a higher value than before even without physical contact(high value means there is a presence of tissue nearby) , but I am not entirely sure if it is related.
Thank you for your kind responses!
Whenever my hands are little wet with water or sweat My touch doesn't respond and Ghost touches appears. Then i just wipe up my hands and everything works well . Hope that helps.
Related
So I figured I would post this up just in case people are going crazy about turning on their display, and then having it turn right back off on them lol. There are sensors at the top of the device by the ear speaker. When turning on the device make sure your fingers remain clear of those sensors for 1 second, if those sensors do not pick up light source by being blocked off (try it, press the power button while covering the sensors), the display will turn back off. Same thing goes for Knock on, the display wont even turn on at all. Keep your fingers clear of those sensors!
I dont think this is a design flaw I think LG inadvertently did this to keep from the device from turning on in your pocket by accidentally hitting power on knocking on while in your pocket. it might also attribute to poor knock on feature in low light areas or night time.
Walter21026 said:
So I figured I would post this up just in case people are going crazy about turning on their display, and then having it turn right back off on them lol. There are sensors at the top of the device by the ear speaker. When turning on the device make sure your fingers remain clear of those sensors for 1 second, if those sensors do not pick up light source by being blocked off (try it, press the power button while covering the sensors), the display will turn back off. Same thing goes for Knock on, the display wont even turn on at all. Keep your fingers clear of those sensors!
I dont think this is a design flaw I think LG inadvertently did this to keep from the device from turning on in your pocket by accidentally hitting power on knocking on while in your pocket. it might also attribute to poor knock on feature in low light areas or night time.
Click to expand...
Click to collapse
There's also a bug which emulates the same symptoms,while the sensor is not blocked. Changing the screen-off effect to different effect, is a work around for those caught with the issue.
timsterzzz said:
There's also a bug which emulates the same symptoms,while the sensor is not blocked. Changing the screen-off effect to different effect, is a work around for those caught with the issue.
Click to expand...
Click to collapse
Its interesting that LG went with this sensor design. This sensor thing is kinda weird seeing as people will no doubt block this sensor and trigger this effect without even realizing what they are doing, making people think their device is broken. LOL im sure this is talked about in the instruction guide but who the heck reads those things now?
Hello all and please forgive my poor english
I really love this tablet (thickness, battery, weight, screen) BUT i have a major problem with it : i often need to tap 2 or 3 times on something in order to launch/select it and it ruins my global experience with the tablet :crying:
Do you guys have this problem and is there a way to alter the sensivity of the screen ?
Thanks
yanouch said:
Hello all and please forgive my poor english
I really love this tablet (thickness, battery, weight, screen) BUT i have a major problem with it : i often need to tap 2 or 3 times on something in order to launch/select it and it ruins my global experience with the tablet :crying:
Do you guys have this problem and is there a way to alter the sensivity of the screen ?
Thanks
Click to expand...
Click to collapse
Yes, I have the same problem. Some say, it's software issue, and suggest to wait until tab gets updated.
xbad1 said:
Yes, I have the same problem. Some say, it's software issue, and suggest to wait until tab gets updated.
Click to expand...
Click to collapse
Yeah that's what i expected but wanted just to know if others had the same problem and if there was already a workaround for this
Many people have this problem, including a number of reviewers.
Nevertheless Sony refuses to acknowledge the existence of the issue. When I called them, the guy said "You are the first to report such a problem". (Probably he lied and was advised "from above" to say so...)
The customer is left in the cold!
Some people have a return policy - what if one waits for a software update, the return period expires, the update comes, but it doesn't fix the problem and it turns out to be a hardware problem??
The information politics of Sony and other companies (yes, Google, you too!) is an absolute PILE OF S**T!!
Yup, me too. The annoying thing it is difficult to document. Yesterday my tablet was charging and I turned the screen on using power button - lock screen didn't react at all to my inputs. Tried switching screen on/off a few times but it didn't help. Also tried double-tap to wake with no success. Went to get my camera to document, then of course it started working...
I've written this elsewhere, but this is how I notice the touch screen problems:
For me the tablet randomly doesn't recognize touches during the below instances. In all cases either going to the home screen and relaunching the app or turning the screen off/on will solve the problem. The problems occur several times per day but not constantly.
Sometimes opening apps will cause everything but the bottom android-buttons to be non-responsive. This can happen in any app it seems, including native ones such as Google Play.
Sometimes the lockscreen doesn't recognize touches at all.
While charging I've had issues getting the touchscreen to recognize touches, disconnecting the charger has helped.
Double-tap to wake seems to be very moody, sometimes working sometimes not. Sometimes it turns the screen on even by me just holding the tablet with my palm resting against the screen.
While not a bug per se, also the android-buttons seem very picky that you have to hit them right on the spot to work.
Other threads on same topic:
http://talk.sonymobile.com/t5/Xperia-Z2-Tablet/Touch-screen-problem/m-p/620325
http://community.sony.fi/t5/Tablets/Xperia-Z2-tablet-touch-screen-issue/td-p/1582051
http://www.android-hilfe.de/sony-xp...screen-reagiert-nicht-immer-zuverlaessig.html
Damn ! i'm not alone....
One forumer said he thinks that switching OFF Stamina mode helped a little bit...
I don't have my tablet with me, can someone test this ?
"A little bit" help is NOT enough.
The touchscreen MUST work perfectly, whether with Stamina Mode on or off or whether with Mode XY on or off. No discussion.
Sony HAS to fix this.
Already solved in .55 firmware
hasenbein1966 said:
Nevertheless Sony refuses to acknowledge the existence of the issue. When I called them, the guy said "You are the first to report such a problem". (Probably he lied and was advised "from above" to say so...)
Click to expand...
Click to collapse
The same experience with Z1 compact and support. Told them the camera is really broken - they told me there is absolutely nothing wrong with the camera and I'm the first one who got this problem. That was some weeks before, now they officialy added that maybe some devices are defect.
But that´s Sony, they give a **** about u, don't even try to contact the support.
I'm also having this issue, if I'm using the Sony sleve it's impossible to use the touchscreen as it will tip over when I press hard enoug for the screen to actually register it.
No problem here.
Only early days yet. The only prob I've got atm is Dropbox isn't showing up in the Album.
Edit: Fixed the Dropbox problem by using the Dropsync app.
I also seem to get this. The tablet works fine when tilted at an angle but for some reason can be completely unresponsive when it's laid flat. Would this suggest a hardware issue or a software bug?
I also get this, sometimes it's like I just need to press harder (so hard the tablet falls over when using the cover as a stand), but other times it seems that no matter how hard I press or how many fingers I apply it doesn't register a thing for periods at a time.
I'm lead to believe that this is either software or firmware considering the intermittent nature. Are there any custom ROMs out yet that we could flash to eliminate the software aspect?
I have same problem, most noticeable in Chrome, switching tabs fails to register 10% of time. I can only think Sony have a hardware quality control issue with the digitizer as if it was firmware related, surely everyone would be suffering. Strange none of the reviews have picked this up, but I'm going to have to return mine.
No, no, no.
It's most surely a firmware problem!
The electric current threshold for registering a touch is set too high. So if the tablet lies on a non-conducting surface, and especially if it was not touched for a longer time, there will be touch problems. Also touching the tablet with a fingernail will not suffice because nails conduct current worse than skin. Other tablets which have a lower current threshold also accept fingernail touches.
I'm very sure: If you hold the tablet with one hand and touch with the other (and don't accidentally use fingernails), touch will be OK! Right? This is because more current will flow.
The .55 firmware which is out for LTE devices already and will follow for WiFi devices lowers the threshold and thus fixes the problem.
Up to then always take the tablet in your hands when operating it.
Interesting theory, just gave it a go, inclusive, but does seem worse in case. However if Sony aware, why have they not rushed out firmware as otherwise initial user experience is ruined.
QUOTE=hasenbein1966;52005720]No, no, no.
It's most surely a firmware problem!
The electric current threshold for registering a touch is set too high. So if the tablet lies on a non-conducting surface, and especially if it was not touched for a longer time, there will be touch problems. Also touching the tablet with a fingernail will not suffice because nails conduct current worse than skin. Other tablets which have a lower current threshold also accept fingernail touches.
I'm very sure: If you hold the tablet with one hand and touch with the other (and don't accidentally use fingernails), touch will be OK! Right? This is because more current will flow.
The .55 firmware which is out for LTE devices already and will follow for WiFi devices lowers the threshold and thus fixes the problem.
Up to then always take the tablet in your hands when operating it.[/QUOTE]
POTENTIAL FIX FOUND (ROOTED ONLY)!
Rooted users can try this fix, works for me! Touch seems to work perfectly now, also when tablet not in hands and lying on non-conducting surface!
Edit the file
/system/usr/idc/clearpad.idc
and alter these two lines:
Code:
touch.pressure.scale = 0.0001
(original value: 0.1)
and
Code:
touch.filter.level = 1
(original value: 2)
Don't forget a nandroid before
Please report whether it helped! :good:
P.S.: just for the curious - on the first Tablet Z, the two values are also lower: touch.pressure.scale is 0.0074, and touch.filter.level is also only 1.
Thanks for suggestion but dont wish to root (I use it to watch Sky which wont work if rooted) - seems there is more assistance on this forum to the issue than from Sony. I'll give it another week for a firmware fix before returning it.
elaborate...
nos1609 said:
Already solved in .55 firmware
Click to expand...
Click to collapse
If this is fixed in the 55 firmware then how do you get it?
I haven't had a firmware update?
I'm using 16GB Wi-Fi only in the UK
---------- Post added at 09:17 PM ---------- Previous post was at 09:11 PM ----------
homme_fromage said:
If this is fixed in the 55 firmware then how do you get it?
I haven't had a firmware update?
I'm using 16GB Wi-Fi only in the UK
Click to expand...
Click to collapse
My bad, didn't read all the way through, ignore me.
Now after a few days I can say:
With the root fix described above, my tablet works like butter. Simply perfect. :good:
Only instance where I have still problems is when the tablet was lying around for a while and I try to operate the touchscreen without taking it in my hands. Then sometimes (not always) the screen doesn't react, but only for a short time.
The problem seems to be related to static electricity.
hallo everybody
i've bought a BV6000 (firm ver 20160713 chip MT6755 (Helio P10)) but the proximity sensor is very weak, i've asked on official forum for calibrating\change threshold, but no one have published my question.
now my idea:
on engineering mode i've found ps calibrating tool but nothing happens after calibration and reboot; the default threshold is set to 40 (less than 1cm) and if i could set to 5 or less the range arrive to about 3 cm.
is some days that i try all solutions founded on the web but no one works...
now someone have some skills in calibrating the sensonsor manually? i've also tried with DHD Proximity Recalibrator but give me a kernel error.
maybe edit some files in /sys/devices/als/subsystem/drivers/als_ps is the solution?
any other idea?
thank you!!!
xposed and the module: http://repo.xposed.info/module/com.mrchandler.disableprox
I have an MTK and it kept hanging up when I brought the phone close to my face, so I had to disable it completely.
yeah i've tried this module but is a bit too invasive and need a tasker profile to turn off screen on call, i would remap the threshold (if is possible!)
/sys/devices/als/subsystem/drivers/als_ps there are many files:
a "config" file with
(3 200 0 0 50)
a "status" file with
CUST: 1, (-1 0)
REGS: DF C1 00 06 00
MISC: 0 0
what makes me angry is the farest PS sensibility from engineering mode! (hardware testing>sensor>light/proximity> PS calibration) if only is possible to manually reduce threshold!!
engineering mode ps calibration...
UP! i attach two photos of the engineering mode that show the lower threshold.. but after calibration nothing happens...
I put 4 times complete analysis of proximity sensor issue on Blackview forum. Every time, they delete my post.
None of the calibration would help.
The only solution is to replace one rubber part from phone. More details here:
thank you
at now i have do a tasker scene that block upper buttons and an "immersive mode" shell during call (show up when call+phone app is on screen and hide if not).
is a patchy solution but it works
maybe if i have some other hardware problem i'll try to open the phone
bye!
Could you upload a video of your solution? How did you reach the rubber part?
Thank you!
I could not upload video, because I did not recorded the process, but I will try to describe this process.
Video comparing working BV6000 and broken BV6000 proximity sensors:
https://www.youtube.com/watch?v=s8NYcs-Yo5E
Go to service mode *#9646633* and select
Hardware-->Sensor-->Light/Priximity Sensor-->PS Calibration
If your BV6000 acts like the right yellow model, then you are affected with this issue.
Root cause:
Proximity sensor is good. Rubber part covering sensor is really poor quality and it has a gap just above sensor causing light leaks.
PS reading 0-80 are considered as "far". Phone cannot get proximity readings >100 which are considered as "near", so the phone does not dim the screen at all. This is causing a lot of unwanted touch screens while making a call. If the proximity readings were possible in full range 0-255, then the threshold settings 40-100 would be perfect. This issue cannot be fixed by any calibration.
On my working, green BV6000, this rubber part has a bit different shape and it is made with much softer rubber. The edge which is covering sensor is also much tighter than on the yellow one.
Workaround:
Disassemble the phone, like on video here:
https://www.youtube.com/watch?v=9yLEemeXFnY
You do not need to disassemble the whole phone. Just get to the part, when you can detach main board.
Then turn upside down this rubber part covering proximity sensor. It is not meant to be mounted this way, but it will fit. Basically the part which was close to the screen should go close to sensor. This will make gap between rubber and PS sensor smaller and there will be just tiny light leak. It will not make full proximity range 0-255, but it will improve a lot.
On my phone proximity range expanded from 0-80 to 0-200 after this mod. Phone will dim the screen while making a call, if you head is 1cm above sensor. On working phone 0-255 it dims screen in 2-3cm range.
The only 100% solution:
New working rubber part to be sent to all affected users.
Shame on Blackview, that they not only deleting my posts about this issue on their forum, but also reporting my posts, when I put this analysis somewhere on well known Android forums. This is like they want to cover a problem and not resolve it like they did with faulty OTG boards.
thanks for the brilliant hardware workaround, but if i want to change the values showed in this app
i've seen many phones with different resolution\max range (higher than 1cm!)
how i can edit this values without MTK engineer tool (tried but dont do nothing for this issue)?
thanks to all
PS. BV6000 is a good phone for the price, but this issue is really annoing!
PPS. BV6000 have adups fota search online and be paranoized!
I have tried it by placing the rubber above the sensor both ways but it still doesn't work. Whenever I make a call the screen remains responsive and many apps open up or settings mess up every time. There is no end to it.
Please help. I'm really annoyed with this issue.
Sent from my BV6000 using XDA Free mobile app
Another thread about this stupid sensor.
My screen goes black when I call or answer a call. If I use a headset sometimes randomly the screen comes on or stays on when I answer a call.
The proximity sensor is working. Looking in *#*#7378423#*#* > Service tests > Ambient Light Sensor.
Putting it to a lamp gives a value of 10.0 and putting my finger over the sensor gives 0.0 .
So its working.
This seems to not be rom related if not for the change after Android 4.4. I flashed roms from cm-12.1-20161016-NIGHTLY-togari.zip, AOSP_N_161207_togari.zip and now I am on hybrid_concept_edition_2.0.zip.
I do have a screen protector on. But with a hole for the sensor. Its not dirty in that area. And the sensor worked fine way before I installed it.
This started happening during the last two months or so.
I tried numerus of apps from play store. None did anything. Of course I could force the screen to be on. But with the risk of pushing some buttons when I'm in a call.
My temporary fix so far has been to enable end call with power button
Do you have any idea what to do?
Thank you
I'm facing this same problem, I'm on stock.
hypergp said:
I'm facing this same problem, I'm on stock.
Click to expand...
Click to collapse
yup.. I had mine apart today. But you need to remove the battery in order to flip the motherboard around to get to the connector.
I don't have time for that. Perhaps the battery will explode if I try to remove it..
So I cut a piece of foam plastic to fit around the usb connector so there is a constant pressure applied to the motherboard when screwed down the NFC antenna because there is a screw just around this area that sets the NFC antenna in place.
Hang on. I just made a call just for the sake of it that you answered to my thread and it freakin works!!!!!!!!!!!
I got the idea from this guy/gal: https://forum.xda-developers.com/xp...olution-proximity-sensor-fix-z-ultra-t3595525
Just got a new Tab S7+, and I found that I was getting a heck of lot of repeating keys from the Samsung keyboard and the Gboard keyboard. Hadn't noticed any problems elsewhere.
I finally got fed up with it and get Touch Screen Test, and I can see clearly there that the screen is registering a touch with my finger maybe 0.5mm away from it. That fits with what I see on the keyboard, where I can get keys to fire with tiny finger movements just away from the screen.
I can't find any settings in Android 10 to adjust this. It's surprising for a table that's been out of the box a couple of weeks, and possibly it's worsening.
I had an idea after I'd posted this - I often use the tablet connected to the 25W charger that came with it. If I use it on battery, the problem is much diminished , and possibly gone. Electrical interference, then???
Is it a return-as-faulty, would you say? Any test options I can use to help with this?
Thanks
Alan
Latest update fix that issues
bicubic said:
Latest update fix that issues
Click to expand...
Click to collapse
Many thanks for that. My tablet has T970XXU1AT12 / T9700XM1AT12, no update showing as of a moment ago. I expect it will reach the UK soon and I will be able type!!
I think the touchscreen of this tablet does have some interesting behaviors, as I've also observed some touches being registered when my finger was a still a short distance away. I suspect this might have something to do with palm-related gestures (like palm swipe from right to left for screenshooting).
I play rhythm games on this tablet mostly, and I'm seeing some cases of taps not being registered properly (unexpected misses), which happened less often, when I was playing those same games on my phone (before migrating them to the tablet).
I don't constantly put the tablet on the charger, as I've lessons learned from my previous tablet, Pixel C, whose battery went swollen after having placed it constantly on the charger for quite a long while that I ended up replacing the swollen battery with a new one by myself. While it was a lot of effort in overall, but the swollen battery had made the glues between the screen and the chassis mostly visible, that removing the screen became much easier.
I couldn't confirm this issue.
I've installed a safety glas on top of the screen. Fingerprint and S Pen is working but I've no issue's with a to sensitive Display
Update came yesterday. Still not fixed
I'm also using a tempered glass screen protector and my personal experience with such protectors on different devices has always been positive, with few issues directly related to such protectors as long as the quality appears to be good enough. I don't connect the charger while gaming, but I do attach a Type-c audio cable for connecting the tablet to desktop speakers.
On the other hand, some lower quality charging cables would certainly cause issues with touchscreens regardless of device. Usually with stock chargers and cables (or those from very reputable vendors) you can mostly rule out this possibility.
EDIT 6: Moved the rest of the issues I'm having to a separate thread.