Pipo M8 Pro Touch Problems

[PolarBear]

Same problem, specific circumstances

Greets to all! Since this is my first post here, let me just say how very useful I've found FreakTab to be and show my appreciation. Thanks to all here and a special hat tip to Riley whose 2.0A ROM I'm using now

Concerning the subject of this thread, I've always had trouble with the touchscreen in a certain meeting room which I often teach in. I always find the touchscreen difficult to control and often use my bluetooth keyboard to navigate around; this is especially annoying since I'm now using the tablet for teaching. Last night, the touchscreen went completely inoperative at the beginning of class (thank goodness I've gotten used to using the keyboard by now). Anyway, the room has three characteristics I believe may be at fault. The first: the low, florescent lights which dimly shine directly into the light-sensor near the front camera. The second is the old, static-saturated carpet. And the third is the clear, plastic table top which looks like a giant touchscreen itself. As I stated before, it's in this room only that I have the problem with the touchscreen of my Pipo M8 Pro. If you've any idea what the cause is, please reply to this post. If not, I guess this post may simply be used for future reference.

Thanks again and happy PCing to all,

pb

[pr0xZen]

Re: Pipo M8 Pro Touch Problems

Hi there! Sorry to hear you are having troubles with your tablet. As I do not know what you might have tried or not tried yet, to remedy the issue - so I'll just throw a few suggestions out there.

First off; Go ti Settings > Display ( > Brightness), and turn off Auto brightness. This should in effectively disable the workings of the light sensor to the right of the front camera. (You will have to adjust brightness manually afterwards, until you activate it again.

Secondly; put something between the tablet and the surface/table. If this part remedies the issue, you might want to get a cover for the tablet. As the back side is metal and in rare cases it could cause a short between the inner components and the outer case. Static electricity could cause issues, although - to be honest, It is much more likely to be the light sensor not coping with the surroundings.

Sent from my GT-I9305 using Tapatalk

[PolarBear]

Hi there! Sorry to hear you are having troubles with your tablet. As I do not know what you might have tried or not tried yet, to remedy the issue - so I'll just throw a few suggestions out there.

First off; Go ti Settings > Display ( > Brightness), and turn off Auto brightness. This should in effectively disable the workings of the light sensor to the right of the front camera. (You will have to adjust brightness manually afterwards, until you activate it again.

Secondly; put something between the tablet and the surface/table. If this part remedies the issue, you might want to get a cover for the tablet. As the back side is metal and in rare cases it could cause a short between the inner components and the outer case. Static electricity could cause issues, although - to be honest, It is much more likely to be the light sensor not coping with the surroundings.

Sent from my GT-I9305 using Tapatalk

Hi pr0xZen,

Thanks for the quick reply. I should have mentioned that I was not using auto-brightness. Also, I have a cover and a stand to separate the device. Also, I wasn't using the power adapter, and even when I hold it in my hands with my feet off the floor, the problem persists. Also, I use the HMDI output to a projector, and the problem still occurs whether connected or not. In the end, I figure I'm going to end up buying a TV Player. Btw, my phone is an Xperia Z Ultra (incompatible with the 50hz projector), and it sometimes has touch problems in that meeting room. Weird, huh?

[pr0xZen]

This could possibly be an issue with the HDMI connection - the cable itself or the socket. Does this happen if you do not connect the tablet to anything, including the hdmi cable?

Sent from my GT-I9305 using Tapatalk

[PolarBear]

This could possibly be an issue with the HDMI connection - the cable itself or the socket. Does this happen if you do not connect the tablet to anything, including the hdmi cable?

Sent from my GT-I9305 using Tapatalk

Indeed, it does.

Btw, I just finished teaching in another classroom, and I'm using my M8 right now, attached to a TV via the HDMI port (power adapter is also attached). I've had no trouble with it here, ever. Like I said, the problem ONLY occurs in that particular meeting room. Some odd mojo at play perhaps

[pr0xZen]

So this happens with tablet "in hand", /NOTHING/ connected to it (including any cables _not_ plugged into anything in the other end) - and only in this room?

Sent from my GT-I9305 using Tapatalk

[PolarBear]

So this happens with tablet "in hand", /NOTHING/ connected to it (including any cables _not_ plugged into anything in the other end) - and only in this room?

Sent from my GT-I9305 using Tapatalk

Yup, it's a weird situation. Will check it again when I go back Tuesday. Last thing, this meeting room is in a large IT manufacturer's main office building. Maybe there's some wicked electro-radio mojo there...

[pr0xZen]

...then I have no idea. Try putting a piece of black tape over both cameras and the light sensor in front. It might not be properly deactivated.

Sent from my GT-I9305 using Tapatalk

[diggerfinn]

If got this same very problem but my touchscreen doesnt work even after i've resetted my tablet! What should i do???

[ft1]

My touchscreen also stopped working suddenly. I tried flashing couple of different firmwares but it did not help. Currently i am on official unmodified kitkat rom.
dmesg | grep ts:

<4>[    0.000000] Built 1 zonelists in Zone order, mobility grouping on.  Total pages: 481280<5>[    0.000000] Kernel command line: console=ttyFIQ0 androidboot.console=ttyFIQ0 init=/init initrd=0x62000000,0x00150000 mtdparts=rk29xxnand:0x00002000@0x00002000(misc),0x00006000@0x00004000(kernel),0x00006000@0x0000a000(boot),0x00010000@0x00010000(recovery),0x00020000@0x00020000(backup),0x00040000@0x00040000(cache),0x00400000@0x00080000(userdata),0x00002000@0x00480000(metadata),0x00002000@0x00482000(kpanic),0x00180000@0x00484000(system),-@0x00604000(user) bootver=2013-12-27#2.10 firmware_ver=4.4.2
<6>[    0.000000] SLUB: Genslabs=13, HWalign=32, Order=0-3, MinObjects=0, CPUs=4, Nodes=1
<6>[    0.000000] sched_clock: 32 bits at 24MHz, resolution 41ns, wraps every 178956ms
<6>[    0.891860]       DBUFF-32x8bytes Num_Chans-6 Num_Peri-12 Num_Events-12
<6>[    0.892097]       DBUFF-64x8bytes Num_Chans-7 Num_Peri-20 Num_Events-14
<6>[    2.048464] input: lightsensor-level as /devices/virtual/input/input1
<4>[    2.048613] lightsensor us5151 driver created !
<6>[    3.126113] logger: created 256K log 'log_events'
<6>[    3.292504] nf_conntrack version 0.5.0 (16384 buckets, 65536 max)
<4>[    7.089971] tsk Enter, tsk = 0xeb441398
<4>[    7.294677] [<c07409b8>] (gpio_direction_output+0x98/0x20c) from [<c0870bc8>] (cy_ts_probe+0x34/0x300)
<4>[    7.294773] [<c0870bc8>] (cy_ts_probe+0x34/0x300) from [<c087c2e8>] (i2c_device_probe+0xac/0xe4)
<6>[    7.295946] input: cy_ts as /devices/virtual/input/input2
<7>[    7.325751] SELinux: 512 avtab hash slots, 1333 rules.
<7>[    7.327065] SELinux: 512 avtab hash slots, 1333 rules.
<7>[    7.327110] SELinux:  1 users, 2 roles, 288 types, 1 bools, 1 sens, 1024 cats
<7>[    7.329124] SELinux: initialized (dev sysfs, type sysfs), uses genfs_contexts
<7>[    7.329181] SELinux: initialized (dev rootfs, type rootfs), uses genfs_contexts
<7>[    7.329354] SELinux: initialized (dev proc, type proc), uses genfs_contexts
<7>[    7.330256] SELinux: initialized (dev debugfs, type debugfs), uses genfs_contexts
<7>[    7.332754] SELinux: initialized (dev devpts, type devpts), uses transition SIDs
<7>[    7.332822] SELinux: initialized (dev selinuxfs, type selinuxfs), uses genfs_contexts
<7>[    7.333138] SELinux: initialized (dev sysfs, type sysfs), uses genfs_contexts
<7>[   10.472404] SELinux: initialized (dev cgroup, type cgroup), uses genfs_contexts
<7>[   10.632533] SELinux: initialized (dev cgroup, type cgroup), uses genfs_contexts
<7>[   10.792400] SELinux: initialized (dev cgroup, type cgroup), uses genfs_contexts
<6>[   11.396416] EXT4-fs (mtdblock9): mounted filesystem with ordered data mode. Opts: noauto_da_alloc,discard
<6>[   11.400823] EXT4-fs (mtdblock5): mounted filesystem with ordered data mode. Opts: noauto_da_alloc,discard
<6>[   11.406571] EXT4-fs (mtdblock7): mounted filesystem without journal. Opts: noauto_da_alloc,discard
<6>[   11.431941] EXT4-fs (mtdblock6): mounted filesystem with ordered data mode. Opts: noauto_da_alloc,discard
<7>[   31.029201] SELinux: initialized (dev mtdblock10, type vfat), uses genfs_contexts

when tablet screen goes to sleep then dmesg says:

<4>[   46.508663] enter earlysuspend: cy_ts_suspend_hkw.

and when i press power button to wake up screen i get this:

<4>[   72.836445] enter laterresume: cy_ts_resume_hkw.

Any help is appreciated.

Thanks


Edit: if i connect tablet to PC with USB then only right side of touch screen registers touches but it is not accurate (i need to press it a little harder and touches are jumping all over the place).

[ft1]

Bought new digitizer but still not working. I can't find any schematics/wiring diagram of this LG display that is inside (LP094WX1-SLA1) so i could try to repair it myself.


Has anyone else had similar problem?


Any help is appreciated.

[Nordo]

Jumping Screen

Hi

My wife's M9 Max (RileyROM 2.5.3) is around 18 months old. Was working perfectly until yesterday when suddenly the screen starting randomly jumping from screen to screen. The unstable screen continues to randomly move or jump whether the battery re-charger is plugged in or not, and whether the tablet is lying down or is being held. Pulled the back off, but can't see anything obvious.
The touch sensitivity of the screen is also now very dodgy- sometimes it works, sometimes it doesn't.

When I try to turn it off, the "power-down" window flashes on for a split second, then a "reboot" window appears. So I can't turn it off.

I replaced the battery about 6 months ago. While I was doing that, I broke the micro SD socket, but that didn't appear to cause any problem back then.

Currently the latest glitch is that a window stating "Your connection was interrupted. Please refresh" keeps appearing regardless of what you do.

Using the Reset button will turn the tablet off, but when you turn it back on, all the problems reappear.

Does this sound like the same problem that others are getting? And has anyone found a solution?

[Klausl13]

Hello guys

I read this thread because I also need help.
My device is a Pipo M9, but I think that does not matter.
The tab ran very gold,suddenly the touch freezed without any cause.
So I flashed the newest Firmware because I thought that would help.
Then read somewhere that it would help to separate the battery for a while.
So I opened the tab and I noticed tab is working, as soon as I close it, the touch stops working.
I must mention that I destroyed the sd- socket and maybe the 3g-antenna because now the tab doesn't find a data connection.
Now it is worse, but before I also had problems with findung a net.
I controlled all cables, I put a sheets of paper in between to make no short cut, but it was no use.
The last thing I hoped to help was now to do the thing I wanted to do first, to separate the battery.
So i did this and till now the touch works very well, but I must watch it.
So maybe it helps to separate the battery.

Another question : does anyone know which 3g-antenna is compatible with Pipo tabs?

[Nordo]

Hello guys

I read this thread because I also need help.
My device is a Pipo M9, but I think that does not matter.
The tab ran very gold,suddenly the touch freezed without any cause.
So I flashed the newest Firmware because I thought that would help.
Then read somewhere that it would help to separate the battery for a while.
So I opened the tab and I noticed tab is working, as soon as I close it, the touch stops working.
I must mention that I destroyed the sd- socket and maybe the 3g-antenna because now the tab doesn't find a data connection.
Now it is worse, but before I also had problems with findung a net.
I controlled all cables, I put a sheets of paper in between to make no short cut, but it was no use.
The last thing I hoped to help was now to do the thing I wanted to do first, to separate the battery.
So i did this and till now the touch works very well, but I must watch it.
So maybe it helps to separate the battery.

Another question : does anyone know which 3g-antenna is compatible with Pipo tabs?

Hi
Your English is very good, but nor perfect.
What do you mean by "separate the battery"?
Did you unsolder the battery leads and then re-solder them? Or did you cover the battery with plastic or paper to isolate it from everything else?

Regarding the 3G antenna, have a search on FreakTabs. I know they are some articles on mods to the GPS antenna, so there may be something on the 3G antenna.

Currently my tablet is with Pipo, so hopefully they will repair it and send it back.

[Klausl13]

I think my English is not the problem, the content is not really clear.
I tried both, first with a sheets of paper which didn`t not help.
Then I unsoldered the battery leads and resoldered them again.

The tab ran good for a while but then the problem ermerged again.
Now it is better, the touch still freezes, but after some seconds I can go on.
It´s really frustrating, I have got no warranty any more.