Related
Something very strange happened yesterday.
I got the latest OTA and installed it, after this the touch screen is not responding at all.
I managed to control the tablet with an usb mouse, so I have been able to do a factory reset, but to no avail.
Just now I'm clueless on what to do.
I actually did on more thing in the same process; the initial reason for why I took up the tablet yesterday, was to put on a screen protector film.
So while it was updating I put on the screen protector, after all this was done the touch screen was not responding. I don't think this issue has nothing to do with the screen protector, and I have also now removed the film. But still the screen does not react to touch.
But what to do from here?
Is it possible to revert to a previous version of the firmware?
I doubt reversion is the best option.
If this was common this forum would be flooded with complaints.
It might have been something to do with putting on the screen protector DURING an update.
Factory reset may help. Did you try the pinhole reset switch?
Sent from my HTC One X using Tapatalk 2
I can use the tablet with a usb mouse, and have been able to do a factory reset. But this did not difference.
I have also tried the pinhole reset, no luck...
I have the same issue.
I tried back to ICS stock rom. Touch screen is not responding too. :crying:
imtheyoyo said:
I have the same issue.
I tried back to ICS stock rom. Touch screen is not responding too. :crying:
Click to expand...
Click to collapse
Interesting.
Was it after the latest OTA the touch screen stopped working? Or was it something else that started this?
My tablet is stock in every way, never been rooted or had other roms installed.
I could of course send it in to service, but since I bought the tablet while on holiday in Washington DC and I reside in Norway, it's a little unpractical.
owangen said:
Interesting.
Was it after the latest OTA the touch screen stopped working? Or was it something else that started this?
My tablet is stock in every way, never been rooted or had other roms installed.
I could of course send it in to service, but since I bought the tablet while on holiday in Washington DC and I reside in Norway, it's a little unpractical.
Click to expand...
Click to collapse
what is your image version and touch FW version? my A700 touch function is normal after OTA update.
my image is Acer_AV051_A700_RV19RC01_TWN_GEN1
touch FW version:AT0-22F40-F6935B
My touch screen work again.
I back to ICS stock rom (Acer_AV043_A700_RV07RC06_EMEA_FR), then I apply the update (Acer_A700_AV043.RV07RC06_AV043.RV23RC04_EMEA_FR).
Now I'm on JB (Acer_A700_AV043.RV23RC04_AV051.RV10RC01_EMEA_FR). All Work fine.
jacksonkuo said:
what is your image version and touch FW version? my A700 touch function is normal after OTA update.
my image is Acer_AV051_A700_RV19RC01_TWN_GEN1
touch FW version:AT0-22F40-F6935B
Click to expand...
Click to collapse
Thanks. Compared to yours I see that there is some problem with my touch FW version. On my tablet it says AT0-0-0.
Image version reads Acer_AV051_A700_1.052.00_PA_CUS1
Is it a way for me to fix this? Could I perhaps reapply some of the patches?
Sent from my U8860 using Tapatalk 2
owangen said:
Thanks. Compared to yours I see that there is some problem with my touch FW version. On my tablet it says AT0-0-0.
Image version reads Acer_AV051_A700_1.052.00_PA_CUS1
Is it a way for me to fix this? Could I perhaps reapply some of the patches?
Sent from my U8860 using Tapatalk 2
Click to expand...
Click to collapse
Seems the touch FW is incorrect.Maybe you can download the OS upgrade image from Acer website and reflash OS. I checked the image and it should packed touch FW. If still failed, maybe contact Acer service is good way to solve your problem.
Good luck.
I had the same problem this week, bought the Tablet on monday, made the OTA Update and boom, no Touch input.
I resolved it by unlock my device, flash CWM and then flashed a older full rom.
After that i made the OTA Update again and this time it worked well.
I can upload the ROM i used for this if it's needed.
MfG Frank
via Acer Iconia Tab A700 mit Tapatalk 2.0
Thanks. I have fixed my tablet now.
I managed to reflash an older rom, taken from Acer site. And then upgraded via ota to the latest version.
I did not need to use cwm. Just started the tablet the power + volume - combination
Sent from my A700 using Tapatalk 2
Problem: Screen touches are bugged..
Hi,
I need some urgent help..
I upgraded my A700 (was shipped with 4.0.4) to JB but the screen touches are completely off track. I did the following:
1) unlocked the bootloader
2) flashed CWM Rom 6.0.1.5
3) installed cm-10
Don't know what to do next..
I have an Acer A700 and I'm having the same problem as others here.
Once I upgarded my ROM, the A700 touch-screen did not work.
I found a post that explained a fix. Here's what I did:
* Flashed the non-touch CWM v6.0.1.5
* Wiped everything (system, data, cache, dalvik)
* Installed the IconiaN ROM (by Vorbeth) and choose the option to have IconiaN upgrade my "Touch Firmware"
* The A700 is now booting with version JB-653b3d3 (Unlocked)
* The ROM loads just fine
However, in the ROM, the touchscreen does not work. Clicking in one place on the screen will trigger a click in an entirely different area of the screen.
I then tried installing one of the stock Acer ROMs from their website through CWM. None of them would load, not sure why?
Other people here seem to have solved the problem by flashing an "older ROM" from Acer. I could not find any trace of this older ROM.
I'm running an American version (PA1_CUS) if that makes any difference? I've also tried installing CM 10.1 with the same problems in the touchscreen.
Thank you in advance for any suggestions!
RKM
Where can i get the acer software to update? i've tried to find it on the acer website but i cant find it.
please help. i just got the device and i updated it and now a portion of the screen becomes unresponsive to touch input.
toggling the screen on and off will fix it temporarily but that only lasts for 5 minutes max before it stops being responsive again.
Every thing on it is stock so i want to keep it that way
pyrochance said:
Where can i get the acer software to update? i've tried to find it on the acer website but i cant find it.
please help. i just got the device and i updated it and now a portion of the screen becomes unresponsive to touch input.
toggling the screen on and off will fix it temporarily but that only lasts for 5 minutes max before it stops being responsive again.
Every thing on it is stock so i want to keep it that way
Click to expand...
Click to collapse
Try Google and search for your Rom Build number. Should be able to find the update file. You can also try some of the Acer support sites. I remember they have some ICS full roms for the 700.
Next of course, you're going to ask how to install it?
1. Decrypt the original update file (tool is in the themes and apps forum)
2. Using 7zip, OPEN the decrypted file (DO NOT UNZIP IT)
3. Pull the "update.zip" (NO NOT UNZIP IT)
4. Copy the update.zip to your ext sd card
5. Start tablet holding PWR & Vol- or + (can't remember which) until you see the text in upper left corner then release. Now, JB may have a different stock recovery which offers a small menu. I believe you can select the install update from there.
If the update doesn't install, it may be the wrong update file, so you'll have to search for another.
Anyhow, should work for you. But you may have to roll back to the original ICS rom (full version) then OTA update again.
Remember though, you do this at your own risk, so if things get messed up, don't blame anybody
Moscow Desire said:
Try Google and search for your Rom Build number. Should be able to find the update file. You can also try some of the Acer support sites. I remember they have some ICS full roms for the 700.
Next of course, you're going to ask how to install it?
1. Decrypt the original update file (tool is in the themes and apps forum)
2. Using 7zip, OPEN the decrypted file (DO NOT UNZIP IT)
3. Pull the "update.zip" (NO NOT UNZIP IT)
4. Copy the update.zip to your ext sd card
5. Start tablet holding PWR & Vol- or + (can't remember which) until you see the text in upper left corner then release. Now, JB may have a different stock recovery which offers a small menu. I believe you can select the install update from there.
If the update doesn't install, it may be the wrong update file, so you'll have to search for another.
Anyhow, should work for you. But you may have to roll back to the original ICS rom (full version) then OTA update again.
Remember though, you do this at your own risk, so if things get messed up, don't blame anybody
Click to expand...
Click to collapse
Thank you for the detailed help!
after many google searches i finally found the update files on the acer website!
i managed to go back to ics then re update to jb
and for a while my screen had no issues but they came back again. Im begining to think that its a hardware related issue because it comes and goes. I am going to see if my warranty with square trade will get it fixed.
I have a Pixel 2 with the bluetooth connection issues. When I go look for the Google Security Updates, it says that I am up-to-date. I did a factory reset and tried to get the update afterwards, but it has the same issue where it is not finding the update.
Has anyone successfully been able to find a way to get the phone to find the updates, or should I get a hold of Google to return the phone?
Thanks,
Mark
I have also not received the November security update, every time I check it says it is up to date. I bought the unlocked version from the Google Store and am using Verizon.
This reddit thread shows a way to potentially force it, i have not tried it yet -- https://www.reddit.com/r/GooglePixe..._on_september_security_patch_regular_pixel_2/
UPDATE: I have tried it, and it did not work
I also tried it and it didn't work. I would be more patient, but the Bluetooth issue is quite frustrating. I'll give it a few more days then will contact Google again for a replacement device.
Despite they say that the check for updates button now always bring the latest update. There's a lot of people that doesn't get it when pressed and have to wait a few days or weeks to get them like always.
Things that could affect the check for update button:
- Not being 100% stock un-rooted
- Being subscribed to the Android Beta
- and sometimes if you start executing an OTA update and it fails you might need to wait a few days for a second chance.
None of these reasons apply to you obviously but just giving my experience.
The best 100% official workaround to get now the update is to install the update manually using the stock recovery:
https://developers.google.com/android/ota
Sent from my Pixel 2
thesebastian said:
Despite they say that the check for updates button now always bring the latest update. There's a lot of people that doesn't get it when pressed and have to wait a few days or weeks to get them like always.
Things that could affect the check for update button:
- Not being 100% stock un-rooted
- Being subscribed to the Android Beta
- and sometimes if you start executing an OTA update and it fails you might need to wait a few days for a second chance.
None of these reasons apply to you obviously but just giving my experience.
The best 100% official workaround to get now the update is to install the update manually using the stock recovery:
https://developers.google.com/android/ota
Sent from my Pixel 2
Click to expand...
Click to collapse
Are the ones marked Verizon for the Verizon version, or also for people who bought the unlocked version and are using Verizon? My current version is OPD1.170816.010, which is not a Verizon version, so I guess I would want OPD1.170816.025 since the version I currently have is not the Verizon version? Still find it crazy that an update would come this late, never got them this late on my 5X. I never understood the point of if I manually check I cant just auto get the OTA (I know there was that article somewhat recently that they are moving to that though).
I got 023 over the air automatically on my Pixel 2. Haven't downloaded the OTA from the developer site some I got this phone.
OPD3.170816.023, Nov 2017, Verizon
I too bought unlocked from Google but using on Verizon. I was on .10 and waited weeks after release for a push, but it never came. So I manually flashed the .25 update. No issues, working perfectly, with the Nov security update.
I am still on september security update. Got a Pixel 2 (Verizon). Hope they hurry up. Its almost december
Sorry to bring up an old thread, but I have the same problem ever since I cleared the Google Play Services' data through the app's interface. The OTAs just stopped coming. I have been flashing full OTA images since August, but it is getting really annoying. I still didn't get the November's patch, nor the December's one. It always says my system is up to date. I didn't try clearing the Play Services Framework's data, as it isn't effective and only causes trouble. I tried clearing the Play Services' data though many times, but it doesn't help.
I am rooted with Magisk. Everything else is fully stock (rom, kernel, recovery) and I do pass the Safety Net test.
If anyone has a solution to this problem, please share it with the world. I don't believe that I am the only one with this problem.
Same here, rooted pixel 2, currently away from pc so would love to update from phone
Sent from my Pixel 2 using Tapatalk
I've had the same problem with my P2XL for the last couple of month. I have just been downloading the full updated firmware and flashing from my computer, but it would be nice to be able to update while travelling with no computer.
Details:
-Magisk rooted, everything else stock, including recovery.
-Google edition - I used to get updates, not sure what changed.
-Not on beta. I even tried signing up and then unsubscribing. No help.
-"Check for update" button does nothing.
-Clearing data on Google Services Framework doesn't help.
-I'm in Mexico on Telcel, but updates have worked in the past.
Haven't been receiving OTA updates since flashing the Pie factory image in August.
Device is stock apart from being rooted with Magisk.
Update button always says system is up to date, so I eventually sideloaded the latest OTA image at the end of November but still didn't receive any update notification in December.
I'm starting to suspect the update manager in Pie is detecting root or something, because I used to receive updates just fine on Oreo, and everyone else who has this problem also seems to be rooted.
I've done a lot of searching but can't seem to find anyone posting about the issue I'm having with DP3 on my 7 Pro. I'm stock on 9.5.10. the flash using local update works fine. Upon reboot, the phone will work for a few seconds, once a while it works for a couple of minutes. Then the screen goes black. If I hit the power button twice, I get a reboot dialog box. I restart and the process starts all over. I went back to 9.5.9 and everything is fine. I tried again going from 9.5.9 to DP3 after a full format. Same thing happens. I suspect the UI is stopping but it just goes black.
Anyone have any ideas?
Just wanted to chime in to say the same thing is happening to me.
Mike02z said:
I've done a lot of searching but can't seem to find anyone posting about the issue I'm having with DP3 on my 7 Pro. I'm stock on 9.5.10. the flash using local update works fine. Upon reboot, the phone will work for a few seconds, once a while it works for a couple of minutes. Then the screen goes black. If I hit the power button twice, I get a reboot dialog box. I restart and the process starts all over. I went back to 9.5.9 and everything is fine. I tried again going from 9.5.9 to DP3 after a full format. Same thing happens. I suspect the UI is stopping but it just goes black.
Anyone have any ideas?
Click to expand...
Click to collapse
You need to downgrade in twrp to 9.5.7 then update your phone to dp3 and everything will be grate. I was on dp 3 till I wanted to try out omni ROM witch is grate but there is more customization on dp3 then any ROM for this phone so go ahead and downgrade and then update to dp3. The region it will not update to dp3 is because its build number is lower then 9.5.10 ok
The challenge is downgrading. Can't install TWRP because I get the error when I try to boot it via fasboot. I can't get to the local upgrade option in settings to install the downgrade zip that OnePlus provides, and I can't fastboot an old version because I get a var error. Any suggestions?
NickMidd91 said:
You need to downgrade in twrp to 9.5.7 then update your phone to dp3 and everything will be grate. I was on dp 3 till I wanted to try out omni ROM witch is grate but there is more customization on dp3 then any ROM for this phone so go ahead and downgrade and then update to dp3. The region it will not update to dp3 is because its build number is lower then 9.5.10 ok
Click to expand...
Click to collapse
Thanks. I tried this and while not as frequent, system UI crashes continue. When I went to bed it was fine. After 5 minutes use this AM, it started going black again. I'm going to wait for the next release before testing again.
Odd that only 2 have reported this here. If it helps, I have 2 SIMS both on Verizon Wireless.
Apparently this is a known issue. Bug has been reported to OnePlus.
Dear all,
Hope you are doing great, I was downloading and installing automatic updates just fine and the other week got a notification about a new update of over 1.4 gbs and the automatic installer was not possible to do and requested me to download it and installing it manually. I downloaded the Rar and everything was going smooth and when I enter TWRP I installed at first shoot without doing any wipe or clear cache or data.
All was installed and it told me to restart the phone, I did that and vroom a vibrating sound happen and got me back to the main screen of Poco and then to TWRP and show me 3 workarounds to clear data and cache and the last resort do a clean flash rom.
I had to end with the last option since I was unable to install the update. What could be gone wrong here? I am back at stock now and I am very sad that this fricking update break all the custom firmware and got me bootlooped
I look for your inputs and maybe I can try again.
Thank you!
You must install Android 11 firmware for newer versions of Arrow as it has switched to OSS vendor.
I was on arrow os 11 so Android 11 was on there, the issue was when I was installing the new update from surija I believe si called the developer.
Do you guys have an idea what did I did wrong? Should You recommend staying vainilla stock miui 12 with root privileges or arrow 11?
Thank you!
I was able to flash the latest version update but I am having a System UI is not responding and got WIFI broken so if anyone is installing this update be careful, does anyone installed the last arrow OS update?
I am currently having issues with the last update, I think I will stick with no updates on the firmware
Sorry I am posting multiple updates on my thread, but I tested it and definetly the last update from Surya break the OS when you login you do not have WIFI and is showing the error I mentioned UI system unresponsive. I installed the version from April from Arrow OS and all works like a charm.
So if anyone reads this be careful with latest release from Surya 5/14 version
Yes, i can confirm. The version I used initially was from april 30. The update from may caused bootloop. I'll be turning off updates when I restore it with miflash.
The main reason I went with arrow is that it is selinux enforcing and supports safety net. But this really makes me think..
@SebixWolf The problem may have been that you flashed arrowos from the wrong miui version. I just miflashed back to the original regional version, flashed twrp again and flashed the R firmware. See https://forum.xda-developers.com/t/...ng-flashing-custom-rom.4274891/#post-85002889
had this device all of a week (barely), seemed to work great out of the box, have left it stock intentionally.
take the April security update, reboot.
Have completely lost pinch zoom / multitouch and it seems as though the screen's settings, software or combination are completely misaligned / out of whack regarding touch input.
It's the kind of behavior you get when you have a droplet on your screen and the phone screen is getting erratic input... like it's compromised or fragmented somehow.... I've increased sensitivity which made the phone more usable, but I can barely use the bottom row of my home screeen. If I switch to left hand and try my L thumb, it better detects the input (if I aim WAY LOW). Almost like the calibration for the screen touch has been completely FUBAR.
Hoping custom software and lack of OTA updates fixes this? Has this community seen this issue and are custom ROMs a way out of the mess, or is this a hardware issue that absolutely requires the device to be returned and replaced? Seems odd the change happened with no physical change to the phone.
Same issue here when updating. Complete factory reset fixed mine
@beflythis hey did you figure the fix out? I have a similar issue. Factory reset didn't help me
Got a screen replacement from B2X and updated it to Android 13 subsequently. Since the update or repair, multi-touch has been ruined, cannot pinch-to-zoom, and the keyboard is very buggy since screen responsiveness seems to have been compromised. I flashed android 12 on it again using flash.android but the issue still persisted. I am unable to figure out a solution. Is it a hardware or software issue? Once in a while after a restart the pinch-to-zoom will work and keyboard will work fine before it gets ruined again. Please tell me what to do
Update: Downgrading the phone to Android 10 fixes everything. I. DONT. KNOW. HOW. THO
@anshuuu03 so after downgrading the phone to Android 10, can you update it to Android 12 back? Or should you always use Android 10 now to have sensors working correctly?
anshuuu03 said:
Update: Downgrading the phone to Android 10 fixes everything. I. DONT. KNOW. HOW. THO
Click to expand...
Click to collapse
Same thing for me created a post just about this: https://forum.xda-developers.com/t/wanted-to-get-a-survery-multitouch-on-google-pixel-4a.4452169/ I think this might be releated in the different touch drivers in android 10 kernel and the android 11 kernel and up kernel. I was going to try and fix this by bringing the kernel touchscreen drivers from android 10 and just pasting them into a newer kernel and hoping that works. But have been really busy.
This is definetly an issue with what seems to be the software, not sure exactly what is wrong though (I dont know too much about kernel driver code),
anshuuu03 said:
Got a screen replacement from B2X and updated it to Android 13 subsequently. Since the update or repair, multi-touch has been ruined, cannot pinch-to-zoom, and the keyboard is very buggy since screen responsiveness seems to have been compromised. I flashed android 12 on it again using flash.android but the issue still persisted. I am unable to figure out a solution. Is it a hardware or software issue? Once in a while after a restart the pinch-to-zoom will work and keyboard will work fine before it gets ruined again. Please tell me what to do
Click to expand...
Click to collapse
Exacty same issue, got a screen replacement from UbreakiFix, wonder if it might be a batch of screens that are bad on specific kernel drivers? I honestly dont know.
fbievan said:
Same thing for me created a post just about this: https://forum.xda-developers.com/t/wanted-to-get-a-survery-multitouch-on-google-pixel-4a.4452169/ I think this might be releated in the different touch drivers in android 10 kernel and the android 11 kernel and up kernel. I was going to try and fix this by bringing the kernel touchscreen drivers from android 10 and just pasting them into a newer kernel and hoping that works. But have been really busy.
Click to expand...
Click to collapse
Do let me know if it works. It would be a life saver
fbievan said:
Exacty same issue, got a screen replacement from UbreakiFix, wonder if it might be a batch of screens that are bad on specific kernel drivers? I honestly dont know.
Click to expand...
Click to collapse
I think downgrading to Android 10 has worked for almost everyone facing this problem
vovapolischuk said:
@anshuuu03 so after downgrading the phone to Android 10, can you update it to Android 12 back? Or should you always use Android 10 now to have sensors working correctly?
Click to expand...
Click to collapse
I haven't tried doing that but I guess I'll just wait for other people to come up with a better solution since I have none
fbievan said:
Same thing for me created a post just about this: https://forum.xda-developers.com/t/wanted-to-get-a-survery-multitouch-on-google-pixel-4a.4452169/ I think this might be releated in the different touch drivers in android 10 kernel and the android 11 kernel and up kernel. I was going to try and fix this by bringing the kernel touchscreen drivers from android 10 and just pasting them into a newer kernel and hoping that works. But have been really busy.
Click to expand...
Click to collapse
Now that i know that im now going crazy, and atleast one other person has very very similar story to mine, there needs to be a proper fix. I do know that android 10 and android 11 do have different touchscreen drivers. Downgrading then upgrading back wont work, atleast to my knowledge. I've done plenty of looking, and just don't know whats wrong. If any kernel devs that know their way around touchscreen drivers, and pixel 4as. Would be a life saver. But I have little idea of whats actaully going wrong.
anshuuu03 said:
I haven't tried doing that but I guess I'll just wait for other people to come up with a better solution since I have none
Click to expand...
Click to collapse
Yep, downgrading again to Android 10 alllows multittouch to work
anshuuu03 said:
I haven't tried doing that but I guess I'll just wait for other people to come up with a better solution since I have none
Click to expand...
Click to collapse
Update: I actually got it working on Android 12L. So, I downgraded to Android 10, from googles flash tool. Then upgraded one by one. And for some reason that seemingly worked. Can u confirm?
fbievan said:
Update: I actually got it working on Android 12L. So, I downgraded to Android 10, from googles flash tool. Then upgraded one by one. And for some reason that seemingly worked. Can u confirm?
Click to expand...
Click to collapse
So you went flashed Android 10 > Android 11 > Android 12 using the flash.android tool or did you use the update drops that appear on phone? Also, did you trying going all the way upto Android 13?
anshuuu03 said:
So you went flashed Android 10 > Android 11 > Android 12 using the flash.android tool or did you use the update drops that appear on phone? Also, did you trying going all the way upto Android 13?
Click to expand...
Click to collapse
I flashed from android 10 to 11 t0 12 to 12L. Didnt try 13 because i use lineageOS. Also another note is that i did flash a build of the holy dragon kernel on Android 10. But that should influence it.
fbievan said:
I flashed from android 10 to 11 t0 12 to 12L. Didnt try 13 because i use lineageOS. Also another note is that i did flash a build of the holy dragon kernel on Android 10. But that should influence it.
Click to expand...
Click to collapse
Make sure to test, test, and test
anshuuu03 said:
So you went flashed Android 10 > Android 11 > Android 12 using the flash.android tool or did you use the update drops that appear on phone? Also, did you trying going all the way upto Android 13?
Click to expand...
Click to collapse
Can I ask: has that worked for you?
fbievan said:
Can I ask: has that worked for you?
Click to expand...
Click to collapse
I think I will try and do the 10 > 11 > 12 > 13 in a few days. I am stuck with some work and cannot afford to keep resetting my phone atm. But I will update here whatever is the update on that