Hi All,
I have been experiencing for the last 2 weeks problems with my Huawei Watch ver 1. The upper part of the screen (2-3 mm from top) is not accepting thouches most of the time (97%). I have AW2 (2.8.0.182823779) installed. Not sure did the problems start after some automatic updates. No new programs installed. No physical damage has occured for the watch.
Has any one experienced similar. Is this a physical or software problem ?
All help & Comments much appriciated.
This has happened to me too I have to use the swipe down gesture to access the top bar. No idea what happened watch was great till this happened.
I have also thread under google.plus / Watchmaker , look under questions and discussions with my name (sorry that I can not post here the link as my profile does not allow it yet)
Please try also the "Show Taps" hint that Scott almond suggested. For me it show upper panel part does not register anything. Next I will try to re-flash the whole wathc with original stock rom ( Need to do some googling 1st here
Scott Almond
If it is happening with stock faces as you advised above then this is a watch problem. possibly try re-flashing the stock firmware if a factory reset doesn't work. other than that, the hardware (screen) may be faulty.
Scott Almond
You can turn on "Show taps" in the watches developer options (Need to click on the build version multiple times in the "system/about" section of the watch settings). This will at least show you if the device is even detecting your finger in the top area of the screen
so tried to Re-Flahsing with adb after wipe out still same issue so watch physically damaged and goes to box as spare parts.
Related
Hey there.. I just installed the Energy ROM after having received this phone as a gift from a friend (with an unknown other ROM installed). I haven't had any problems with it for several weeks until just earlier today when the Quick List has decided to randomly start appearing on my screen. I don't even know how to trigger that screen to appear myself, but I can leave my phone unlocked on my desk and it'll randomly show the Quick List for a little while, then it'll vanish, sometimes extremely quickly. But I can't do anything on the phone anymore since it's constantly appearing and interrupting whatever I'm trying to do.
Like I said, I attempted to install an Energy ROM (Energy.RHODIUM.21916.Sense2.5.Cookie.2.0.Mar.08.7z, according to the file I downloaded from the Energy website) and it just finished no more than 30 minutes ago. As soon as I turned the phone back on from a reboot, that dang Quick List screen appeared.
Does anyone know why it keeps popping up and how I can get it to quit? Or is there some way I can just disable the Quick List altogether (as the options on it aren't really useful anyway..)? Thanks for any help ya'll can provide!
Started having this problem a few weeks ago. Did some hardresets, some task29 and tried different roms. But this quick list keeps appearing outof nowhere. Starts to get frustrating.
It's happening again...
So, for no reason that I could tell, it magically started working again (same rom as listed above) and I never saw the Quick List window again until today.
Today, I was using that same ROM as before, but the Quick List window started appearing. I thought that perhaps it was just something to do with that build, so I upgraded to the English build available at (well, tried giving the link but apparently I haven't posted enough, so never mind). It's at "http : // Energy Roms dot com forward slash www forward slash flavors forward slash sencity.html" for the HTC Touch Pro 2 Cookie (April 8, 2011 version). The ROM installs without a problem (absent the annoying attempts to get the phone to not constantly display the Quick List) but as soon as I power the phone on, the Quick List starts blinking on again.
I searched around as before for a solution and thought I could just disable the setting so that when I hold the end call button, it displays the Quick List, but after 10+ attempts to get to the settings window without the Quick List appearing and interrupting me (then closing itself automatically and displaying the Home screen), I finally got the setting saved and it didn't change anything.
Is it possible to just turn the Quick List feature off? Is there some known reason why it has possessed my phone? Thanks for any help ya'll can give.
Is there still no solution for self appearing Quick List? because I have the same problem :/
EDIT:
I've solved it The front keys flex need to be reconnected to main flex because "endkey" was self pushed what in energy rom is configured to turn on Quick List.
Hello guys,
My G3's touch screen has been acting up for a week now and I am seeking help to pin point if it is a hardware issue or a software issue that can be fixed.
Whilst typing (have used different keyboards) I cannot seem to press the letter 'k' and the letter 'r' or any keys directly above or below those keys. I wondered what the problem was and started swiping my screen to see if I can flow through the UI of the phone smoothly. Suffice to say that it didn't which then prompted me to turn on the "Show touch" & "Show touch data" within the developer settings of the phone.
After turning on those two options, I could clearly see that the screen does not recognise any input on two parts of the screen. This can be seen in the screenshots I have posted.. As it shows when swiping on the screen it skips an entire column of the screen on both left and right sides of the screen .
I was hoping someone could shed some light in this issue since I have been trying to troubleshoot this problem with no avail for the past week. If this is hardware related then what would be the best course of action?
Additional Info:
* Have tried different firmware and roms
* Have tried other keyboards like google keyboard and swiftkey
* Have tried to clear cache and factory reset
* Have taken it to phone repair store and they said they would have to replace the LCD.. Thought I'd post here before I go that route.
Any help would be greatly appreciated.
You're gonna have to replace the digitizer. Unfortunately I had the same issue with my nexus 4. That's why I have the g3 now.
StatusUnknown? said:
You're gonna have to replace the digitizer. Unfortunately I had the same issue with my nexus 4. That's why I have the g3 now.
Click to expand...
Click to collapse
Thank you for your reply.
Was hoping I would not have to go through that route but it seems inevitable .
Is the G3's digitizer and LCD stuck together? If so it'll be a costly replacement :crying:
That I do not know. I know the frustration though. It might be a big charge
My headunit (MTCB KLD6 with latest MCU 2.98 ) touchscreen is not more working properly, some upper and bottom part of the screeen is not responding to my finger touch, even tough I have managed to enter the factory settings to reset some setting such as the radio band (because I dont hear enything) it doesnt accept the "enter" comand when I press the OK button.
Also the "space" button and numbers/letter on the left bottom corner is not working when pressing the screen.
Is there anyway to make it work again??
I have also reinstalled another rom, resintalled it twice, maybe I should revert to an older MCU version?Currently I am running an MCC mcu version (kld6 2.98).
Is there any way to re-calibrate the screen??
I am so frustated.
Yes, it's really frustrating. I have the same problem with my Eunavi (MCU MTCD_LM_2.55_1, px5). Bottom of the screen (20%) doesn't respond. I also made factory reset of device, installed another ROM and changed MCU (from 2.55_1 to 2.52_1). All that things doesn't help. Because seller is not interested in helping me, in weekend i'm going to disassembly device and check connections between display and mainboard, eventually try to buy another display (digitizer ?) to replace it.
Has anyone ever suffered this problem?? Is there a way to re-calibrate the Head-Unit??
if I enter the code httouch into factory settings to check the unit resolution it says "1024*768" but my unit is a 800x480 native resolution.
I've never installed a wrong rom with incorrect resolution, I've changed serveral roms, reinstalled original MCU, but some part of the screen does not respond to finger touch...
Goaz said:
if I enter the code httouch into factory settings to check the unit resolution it says "1024*768" but my unit is a 800x480 native resolution.
I've never installed a wrong rom with incorrect resolution, I've changed serveral roms, reinstalled original MCU, but some part of the screen does not respond to finger touch...
Click to expand...
Click to collapse
If you want I have a MTCB 1024*600 touchscreen left. BTW I am from Italy too
Touchscreen change is great idea. I changed my digitizer after one month (1,5 week conversation witch seller and 2,5 week waiting on package). Now device working like new - I'm absolutely sure that was hardware failure. Changing is simple in my issue - 18 screws and 7 wiring tapes.
How did you know which to buy ?
Sent from my SM-N975F using Tapatalk
I just got mine installed and the top band of my screen is unresponsive as well.
I cannot touch My Apps in the play store or search in the play store due to the dead area being on that top portion.
I cannot even search in maps as that search bubble is at the top where the screen seems to be dead.
Time to contact Aliexpress.
I'm having multi-touch issues on my new S20. It works just fine with up to 5 touch points, but as soon as you start adding more points (using more fingers), touch panel starts to glitch, with touches quickly "flickering" in and out, as if I'm quickly tapping screen, sometimes working fine, other times glitching moderately or severely, use up to 5 points, and works flawlessly.
I noticed it while using Piano/Synth apps (such as Perfect Piano, ORG 2020), trying to play simple chords, for example every other white key, using as many fingers as I can, playing chords repeatedly. To make sure it's not app specific, I downloaded "Display Tester" app and used its "multi-touch test", same problem, panel registers 5 fingers flawlessly, but using more fingers, problems start to manifest themselves, sometimes immediately, other times not. To completely rule out downloaded apps, I enabled "pointer location" through Android's "developer options", and yep, testing on solid backgrounds (better visibility) reveals touches not registering properly. Removed factory screen protector, tried restarting phone, safe mode, enabling/disabling touch sensitivity, accidental touch detection, changing resolution, updating phone (all the latest updates as of July 3 2020).
The only thing I haven't tried is "TSP FW Update", through secret dialer code *#2663#, hearing horror stories of update failing (even seemingly succeeding) , and people losing touch panel functionality entirely, with no obvious way to flash older firmware since touch panels firmware lives separately from device's main firmware.
● So my question is, problems that I'm experiencing, are unique to my device, or is this widespread/normal?
I doubt many people would notice these problems since panel works flawlessly with up to 5 fingers, no glitches whatsoever.
● Can you, fellow S20 owners perform above described tests, and report back your results?
● Dialing secret dialer code *#2663#, what touch panel firmware version your phone displays? Maybe mine is old and needs updating, but I'm afraid of clicking that button, which leads me to my final question to experts
● Is there a way to backup touch panel firmware, and somehow reflash it, in case something goes wrong. Or once update fails, there's no way for a phone to communicate with panels controller?
Thanks
Just tried and yep, same thing
Also the thing you gave to update touch panel firmware tells me I'm already on latest so there is no point to use it
EDIT: I tried doing the display update thing for you, it didn't solve the problem
replying to jojos38; sharing more thoughts
:good: Thanks, jojos38, especially for your bravery regarding TSP FW update! (I read you still can control your phone using mouse and keyboard if update fails, but it's very challenging to reflash panel's firmware if something goes wrong, if it's even possible, because reflashing phone will not fix bricked touch controller).
I feel a little relieved I'm not the only one. I wonder just how widespread this is, I also wonder if Samsung uses same touch screen controller on all S20 devices. Seems like it's either panels limitation, or a software thing, I doubt it's a defect, because of how well it performs otherwise, but of course, who knows..
If this will get enough attention, maybe Samsung can release an update, or at least chime in.
Let's wait for more replies, and see what others have to say.
Hi everyone.
I have a note 10 + 256 go exynos from france.
SInce about last update one ui2.5, I have seen 3 issues which I think are related.
- AOD tap to show not working
- Double tap to wake not working
- When I remove the phone from the ear during a call the screen does not light up anymore whereas before yes.
I almost returned the phone in warranty a short time ago because my screen only registered two fingers,a few days later I received an update that fixed this problem.
For these 3 problems I tried 3 things :
- Update touch screen firmware via *#2663#
- Factory reset
- Reflash the stock firmware with odin and frija
I also have another problem a few times a day the screen freezes, I have to lock unlock the screen and it works again..
Do you think it's a software problem or a hardware problem (damaged screen, damaged sensor or other)?
Please help me thanks.
Lol, firmware and/or software; maybe a settings or permissions issue as there are many. Hardware rarely fails unless it receives severe abuse. You can perform some of the builtin hardware tests just to be sure.
Try using the factory load if the apk in question has been updated or wait for an update that fixes it. Be sure to check the Gallaxy Store for updates.
I'm still running on Pie because it's fast, stable and functional. No scope storage that I don't want or need.
Once you get an OS optimized and running well there's little advantage to upgrading many times unless the new OS is really worth it.
Many times it's not... I'm still running W7 too.
You invariably end up with new issues, hunting down all new glitches and worse, since it's new there not many online solutions.
Thank you for your help.
I mentioned the 3 main methods of fix but of course before that I had already tried the basic things like clearing the system cache, checking the permissions of the AOD application as well as deleting this data.
I also checked the sensors with * # 0 * # but I did not find anything problematic
I even tried to flash the november update with odin and frija and I got a soft brick, so I don't even dare to try a downgrade firmware, I don't have the knowledge, I read that I had to keep the same bootloader and I get lost in the different firmwares
Those are all system apks that run in the background.
Is Android System configured correctly?
Try clearing it's data and of course the system cache.
A hard reboot as well.
It's interesting you lost the proximity sensor.
Thanks.
Yes I have cleared the system cache several times, android system too. I even did a hard reset. I think more and more of a hardware problem, because all these functions are linked to the fact that the screen does not wake up by touch when it is turned off.
the proximity sensor still works at least partially because it flashes well during a call and turns off the screen when I put the phone to my ear, but no wake up when I take it off my ear.
cyroko said:
Thank you for your help.
I mentioned the 3 main methods of fix but of course before that I had already tried the basic things like clearing the system cache, checking the permissions of the AOD application as well as deleting this data.
I also checked the sensors with * # 0 * # but I did not find anything problematic
I even tried to flash the november update with odin and frija and I got a soft brick, so I don't even dare to try a downgrade firmware, I don't have the knowledge, I read that I had to keep the same bootloader and I get lost in the different firmwares
Click to expand...
Click to collapse
cyroko said:
Thanks.
Yes I have cleared the system cache several times, android system too. I even did a hard reset. I think more and more of a hardware problem, because all these functions are linked to the fact that the screen does not wake up by touch when it is turned off.
the proximity sensor still works at least partially because it flashes well during a call and turns off the screen when I put the phone to my ear, but no wake up when I take it off my ear.
Click to expand...
Click to collapse
If it happened after the firmware update... it's in the firmware or software.
Bad firmware can sometimes blowout a cpu but doubt it damaged the hardware controlling just that one feature of the touchscreen.
If that was the case the touchscreen wouldn't work at all.
Maybe the firmware is ok but got corrupted during the download or flash.
A defective memory module could corrupt the load but again that rarely happens.
So back to the firmware/software/settings...
Maybe someone here has seen this before or has a better idea to sort it out.
Honestly I'm not sure it's exactly after an update.
It's just that it's not functions that I use very often. I don't call a lot of people and most of the time I use very little Aod and double tap2wake.
Usually when I grab my phone to use it I unlock it directly with the fingerprint.
when i mentioned the problem where my screen only recognized two fingers at this time , aod and dt2w were already weird as it only worked on the top half of the screen not on the bottom half ..the update solved the problem for the 2 fingers but not for the fact that aod and dt2w only works on the upper half.
Now for some time aod and dt2w no longer work at all no matter where I touch the screen.
I want to clarify that I use a screen protector with loca glue but that it is from the beginning and that it has never been a problem before.
I know this is a weird problem thanks for your patience
I never use a lock screen or the fingerprint sensor.
There may be a conflict because that... disable and see if that helps.
The screen could goof up the proximity sensor. Probably not but next time it's off, check it out.
No worries; these devices fascinate me.
Hope you sort it out; eventually one usually does
I never use a lock screen or the fingerprint sensor.
There may be a conflict because that... disable and see if that helps.
The screen could goof up the proximity sensor. Probably not but next time it's off, check it out.
No worries; these devices fascinate me.
Hope you sort it out; eventually one usually does
2x post
when i did the factory reset it was the first thing i tried before even resetting a password but it didn't work anyway.
For the screen protector I use the same brand from the beginning and it has never caused me a problem of this kind, but maybe this one is defective ..
I would have to remove it to try but I have lazy to change it again because I had to change it twice in a little while.
Hoping that by dint of applying the loca glue I haven't damaged anything.
Thanks
Nah the glue didn't hurt anything; it's well sealed.
The tap on AOD I never use but I double tap to turn the screen on/off. If I lost that I be witch hunting.
Try increasing the touch sensitivity if you haven't already... and make sure no other apps have accessibility permissions that could conflict. Same for device administrator permissions.
Try it in safe mode as well.