Device is a PX5 fitted for an MB SLK (with extra hardware Buttons, CAN-BUS, etc), Android 9.
I think someone posted something similar before, I'm also in contact with the producer (Witson):
First the tl;dr - Touchscreen didnt work temporarily, then permanently, now not in some areas.
Now the details:
~2 Weeks ago: Touchscreen suddenly didn't respond, I rebooted the device, worked fine again
~1 Week ago: Touchscreen was acting "on its own" sometimes making presses I didnt make, so songs switched etc. maybe was also only dirt, but didn't seem like it, only reboot helped
~2 days ago: Drive to supermarket, everything works fine, come back, screen doesn't react anymore. AT ALL. Tried to reboot, still doesn't work. Tried to boot into recovery, even there the screen doesn't work(tapping gestures, long press).
So I wrote Witson and simultaneously googled for issues like that with Android Head Units, read sth about calibrating the screen or holding reset+power button... last thing didnt work.
Smarta** that I am, I connected a mouse to the device, system was working fine with that, so I could still somehow use everything, so definatley sth with the touchpanel
Then came the answer from Witson, they sent a video on how the recalibrate, so I did:
Go into Factory Settings > Enter 126 > Touch Panel Calibration (or sth like that) .... 2 crosses in the corners of the screen, no reaction .. i think i also tried to use "Reset Touch" but also didn't work.. BUT I didn't reboot afterwards.
Now the fun begins: After work, go to the car, Head Unit starts, I dont even try touching until after 3 minutes and as I try suddenly the screen reacts! But after some time of driving, it stopped working again.
Back home, reboot, touch works for ~1min then stops again.
Boot into recovery, Wipe/Factory reset, Screen reacts PARTLY after that, like around the middle it doesn't seem to react... Factory Settings for Calibration again, want to enter the 126, but that row on the keyboard doesn't react. All the others do (even though sometimes laggy), Mouse again, enter code, go to calibration, touch works this time! Calibrate, apply, reboot. But still sometimes the Settings itself don't react all the time, when I wnat to enter WiFi Password, again, upper row of the keyboard doesn't react, rest of the keyboard does.
WHAT is going on!? Faulty Hardware? Software? "Driver"?
I also have a video of me trying to enter stuff on the keyboard, if someone needs it.
Suggest to send it back or demand warranty replacement for these poor lack of Quality Control knock off head units.
All you will get posting here are guesses.
Related
Hi, to all!
I have a problem with the touchscreen of my hermes alias O2 trion.
When starting from cold state the touchscreen works normal. After some time the screen reacts not allways and shortly after that it does not react at all. Reset does not change anything.
Is it a upgrading problem or is it a hardware problem?
Here the hole story:
I bought a used device with Win Mobile 5 on it. At the first try out it worked, but afer some time the screen did not react to my stylus at all. After a reset it worked again so i dit not pay much attention to this and upgraded to official Windows mobile 6 (which was downloaded from O2). Update worked fine.
Then i ran a rom update on the computer to change the start screen. The tion disconnected (update stopped at 0%). Little shock, but the trion still worked. The program and radio versions did not change.
First thought: this was no official update, so trion did not accept it. Was something installed or was everything blocked?
Could this make problems?
What do you think?
Thanks
i think this problem:
http://forum.xda-developers.com/showthread.php?t=285062
Alienax said:
After some time the screen reacts not allways and shortly after that it does not react at all. Reset does not change anything.
Click to expand...
Click to collapse
Did you try to re-calibrate your screen? It could be a question of the screen loosing calibration so bad that when you press it, it works but you are not HITTING any buttons, because the calibration is off...
I have that problem with my Hermes, I need to recalibrate several times every day, especially after sliding out the keyboard (since the screen flips then) .
There's a very nifty short-cut to the calibration app: press the middle button on the D-pad while pressing the messaging button to go to the calibration screen, then press the middle D-pad button to launch the calibration (same as pressing "calibrate" with your stylus).
There seems to be a lot of Herms that have serious calibration issues. I'm personally so tired of it I am thinking of buying something else.
Good luck,
Laz
It's KNOWN hardware issue where the processor heats up and *somehow* transfer heat to the digitizer which make it unresponsive. I got a Hermes just like that laying around. Can't fix it.
http://wiki.xda-developers.com/index.php?pagename=Hermes_Problems
Thanks!
Today the touchscreen worked good. Even playing spider solitair was possible. Then i pluged it into power supply and the device got slightly warm. The touchscreen did not work any more.
Could be a heating problem of the prozessor like Mikro_ Tech described. Thanks by the way
How can i be sure it is this problem and not something else?
@LazPL: That was one of my first thoughts as well and i did.
When the Touchscreen works, it works just fine and accurate. Then it behaves strange (sometimes not corresponding to touches, programms close all of a sudden) and shortly after that it doesn not work at all.
@the_passenger: The Hermes Version is HT 626... Anything special to this, because the link just lists screen allignment issues for this modell?
What do you think of the solution from the link LazPL posted?
The other day I was sitting on the couch watching TV when I felt a vibration on my wrist. I looked at my watch and it was flipping out on it's own. At the time, I had Wear 2.0 DP installed (in which, you just swipe left/right to change watch faces) and my watch was switching between watch faces on its own, acting as if someone was holding their finger on the screen and rapidly moving it back and forth.
Using the hardware button, I pulled up the apps list and attempted to scroll down to Settings (so that I could try simply restarting the watch). It was like the watch was fighting against me, and each time I would scroll down on the list it would scroll back up on its own a little bit. After a brief struggle I was able to get it to restart, but the touch issues persisted. I opened the app on my phone and unpaired with the watch so that it would reset itself. I got through the Wear 2.0 first time setup screen, tho with enough touch input weirdness that I suspected the issue was still present... and I was right.
I managed to navigate to the Settings and got developer options re-enabled and then proceeded to flash the stock factory image. Hopeful that this was somehow just DP weirdness, I started the first time setup on the watch and could not proceed past the Language Selection screen. No matter how much I tapped, I could not select any of the languages. I noticed that the bottom 1/4 of the screen seemed to be the only part that seemed to be responding to touch input.
I pushed and held the button and got into the Settings and used gestures to get into developer options, re-enabled ADB (so that I could relock bootloader, since at this point it seemed likely that I'd need to send it in and didnt want that to be an issue) and also turned on the options to show touches and show cursor. I backed out to the language selection screen and confirmed what I had been noticing, only the very bottom of the screen was responding to touch input.
At this point, I am just looking for any additional ideas for things to try before giving up and sending it in for repairs. My watch has never been immersed in water or damaged in any way, I've always babied it. I do use Cape Cod's polishing wipes (which are lightly moistened with a polishing solution) periodically to remove minor, unavoidable scuffs and scratches from the body of the watch. I'm careful to avoid getting anything on the screen and always wipe things dry immediately after finishing, but I'm wondering if somehow a small amount of it got in around the screen somehow?
I'm a repair technician and am regularly taking apart and repairing phones, tablets and laptops, but I've never worked on a watch before. Since my watch is still under warranty (purchased in march 2016), I know the smart options is probably just to send it to Huawei, but I've heard numerous negative things about how slow their turnaround is and how they've tried to get out of providing warranty repairs for other customers. I've become quite dependent on my watch in my daily life, and hate the thought of being without it for weeks on end!
Thanks in advance to those who take the time to read this and give input!
I also having almost the same problem. Did u found any solution?
Yesterday suddenly my phone just deny to work with touch screen. I try hard reset with update.zip. I try clear data with button combination. I wonder what can be the cause? Is there anyone with the same problem? I wonder if i change the touch screen what will happen? Because the screen is not broken, i didnt hit the phone. The touch stopped just when it was with screen off. I hit the power button to wake it up, and then cant swipe.
Yes unfotunately mine as well. It happened 1 year ago, touchscreen used to work randomly. So I sent it back to China, but it was working perfectly.
After getting it back it worked for 1 month, and since impossible to do anything. Without touchscreen no TWRP, no backup possible, no flash.
It's a brick now and it is no guaranteed anymore. I lost my money my time and my nerves.
So sorry for you but I don't think you'll manage to fix it. I think it's an hardware issue.
You can try use OTG cable and a mouse.
Mine touchscreen have an row in the middle, with about 1 centimeter that don't recognize the touch, all the rest work perfect. With a mouse, work all.
Mine stopped working one morning. I left the phone on the bedside table and the next morning the touch screen didn’t work..that’s all…the screen is fine, I didn’t have any accident with it...
It was 4 months ago.. I tried everything I could to revive the phone, but I couldn’t.. so I bought a new phone, from different brand obviously
Good luck with yours!
Hi,
I recently updated my rk3188 MTCB-YM from 4.4.4 to dsa’s 5.1.1 ROM. All went well with the update. After a couple of weeks, I found the ROM was starting to run quite slow and was almost unusable - except if you kept the unit on for a long time. It was like it was loading a lot of things for a long time and once that was done, it became responsive immediately instead of being delayed to button presses etc.
So I decided to boot into recovery and do a wipe all/factory reset. My unit does not have physical buttons or a gps sd card slot. None of the usual boot into recovery options work so I use an app to reboot into recovery. I started this app and chose the correct option. At the time I did this, the radio was playing. The screen went black and the stayed like that with the radio still playing. The lights on the unit are still on but nothing works - no response at all. I have turned the car off and left it off overnight. When I turn the car back on, the radio starts playing again immediately. (This would normally take a little time while it boots up, so the unit is obviously stuck). As I cannot do any of the reset/recovery options - is there anything I can do? I haven’t removed the unit to see if it is possible to short the pins as I don’t have access to a bench power supply and have limited skills. But I will try this if there are no other options. I also haven’t removed the battery terminal to cut power yet. That was going to be my next test. But wanted to see if there was any advice before I do this.
EDIT: I took the plunge and disconnected the battery, and the unit started back up again.
(UPDATED)
Hi, when i try the code *#2663# only said DeviceKeystring has stopped.
Yes, my note only works with the SPen, but i want to try with that menu to see if it can made that the touchscreen works again or not, but i have the problem that i said.
I'm in the N920AUCU5ERB5 system.
I tried with the Binary System 5 and it made the same error.
Could it be that the touchscreen it's really broken?
New Information
Hello, this morning when I woke up I took my cell phone and I did not take it well and it fell to the floor, nothing was broken, so I decided to restart it to see what happened, when I did the touch screen was working.
I'm not saying that if the touch screen does not work, drop your cell phone NO, but it is likely that if this is failing have to open the cell phone disconnect and reconnect the cable that connects to the screen, maybe work as in my case although it was unexpected.
And yes, the *#2663# is working now, but how the touchscreen is working i don't going to update that.