[Q] Did I get a virus ??? - Nook Color General

The video tells everything :
youtube . c o m/watch?v=Ay_eV9ycRZE
( Please modify the youtube . c o m to youtube.com , I cannot post url currently based on my forum level , sorry)
The thing is :
This is my second nook. My first one got the same bad thing just after I bought it in 2days, then I exchanged it to this second one.
I really don't know if this is a virus or something else :
It will not active always, it will active even I format system and data ( yes, rooted), it will active even I restore back to 1.0 or 1.01 stock rom, it will active even when I use the latest Ad 3.0 honey OS in my SD !!
Let me know if you have any clue on this please ~

Turn off the screen and wipe it for fingerprints and it should work normally. This has been a well documented flaw from the capacitive screen's design. The 1.1 update has seemed to help but it still happens occasionally.

Thank you man.
Do you mean this is just because of fingerprint??????

Not entirely from the fingerprints, what I believe is happening is when you long press on the screen the device starts thinking that its multiple touches in the same area and will temporarily remember those touches and tries to keep up with you by these so called phantom touches. It happens a lot to me when I would play a game where you constantly were touching the screen and it then would eventually start to go crazy. I could then recreate it every time doing this and turning off the screen and doing a wipe for fingerprints would correct the problem.

surferfl7 said:
Not entirely from the fingerprints, what I believe is happening is when you long press on the screen the device starts thinking that its multiple touches in the same area and will temporarily remember those touches and tries to keep up with you by these so called phantom touches. It happens a lot to me when I would play a game where you constantly were touching the screen and it then would eventually start to go crazy. I could then recreate it every time doing this and turning off the screen and doing a wipe for fingerprints would correct the problem.
Click to expand...
Click to collapse
appreciate , sir.
Hope it will fix this frustrating problem.

franklicd said:
Thank you man.
Do you mean this is just because of fingerprint??????
Click to expand...
Click to collapse
I also experienced the same issue early on. It happened when my NC was plugged in. I unplugged and the problem immediately disappeared....never to return.
Good luck.

I had a really bad phantom touch problem, focusing on the wifi/quick options menu in the stock eclair rom. Ever since I flashed my emmc with the custom nookie froyo rom, the phantom touches have completely gone away. I wish I knew personaly what could have changed in order to get that result, but I'll take it.

Related

Touchscreen broke, way to bypass welcome screen?

Hey all, I've been looking around the past few days and didn't see anything on this particular issue.
Basically, I washed my G1 and had to get a new one. The one that got washed has been starting up (slowly, and not always), but the touchscreen no longer works. I reflashed the software to hopefully alleviate any of the problems when it was starting up. My initial thought was to use fastboot to flash the backup I made on my new phone with nandroid, but the bootloader isn't working properly (I'll try a reflash of that too).
So, do any of you guys know of any other ways to bypass the startup welcome touchscreen?
Try placing your finger on the Android, press the trackball, then lift the finger and press the trackball again
Tommy
IzzeLing said:
Hey all, I've been looking around the past few days and didn't see anything on this particular issue.
Basically, I washed my G1 and had to get a new one. The one that got washed has been starting up (slowly, and not always), but the touchscreen no longer works. I reflashed the software to hopefully alleviate any of the problems when it was starting up. My initial thought was to use fastboot to flash the backup I made on my new phone with nandroid, but the bootloader isn't working properly (I'll try a reflash of that too).
So, do any of you guys know of any other ways to bypass the startup welcome touchscreen?
Click to expand...
Click to collapse
Flash the ADP1 software.
Edit: You'd still need touch for that, sorry.
The driver was all wonky, uninstalled, reinstalled, fastboot works now Flashed over to my new G1's state, but forgot to take off the lock screen... Flashing yet again. Everything should be good from here.
Edit: Alright, washing the G1 makes it wacky. The touchscreen works now after restoring it to the new G1's state. Weeeirrrdd.
Edit 2: Anddd now the touchscreen doesn't work :S
well.. when my touchscreen broke i used remote control software to control my ppc from pc .. thats one way to bypass welcome screen, but won't get you much further. I used it for making a backup from my phone.
just leave it off for a while and keep it someplace dry and warm so it can dry out.
You may try to modify build.prop in the rom you flash
ro.setupwizard.mode=DISABLED
I think it will skip the setup
Sorry can't help myself. In the laundry?
I guess I'm wondering what exactly you did. I'm assuming it didn't make it into the dryer....
If you need the data off it, you might be able to ADB pull what you want to keep. If I'm not mistaken, ADB is as close as we have to remote controlling for Android at the moment.
There may be some places around, like PPC Techs, that can do hardware repair. I'm guessing what will happen is you'll occaisionally get it to work for brief stints after reflashing or whatever, but it'll keep conking out until the hardware issue goes away/gets fixed. Hardware issues do that, printers, routers, sometimes PCs.
Not to be a naysayer, but I don't think changing out the software is going to help.
I washed my G1 (was in pocket of jeans under the water for about 90 seconds), and after that I disassembled it to let it dry. It was running fine up to the day I SPL bricked it.
Hey.. i split water on my phone.. it couldnt have been that much but the touch screen wasnt working.. thought if i factory reset it, it may started working..
I dont actually understand all the lingo you guys use.. but any ideas on how i can fix it?
J x
oh the main issue is i cant get past the touch android to continue set up... please i just want my android to work!!! J x
I'm having a similar issue... My phone randomly stopped loading android.process.acore and it's messing with my heart. The touch screen doesn't respond but I can use the trackball to navigate, and every acore process force closes instantly upon activation, such as dialer, contacts, music, etc. The wonderfully helpful people at T-Mobile instructed me to do a factory reset on my G1, and it should fix the problem.
New problem: I can't get past the "Touch me, I'm an Android logo" screen. When I click Emergency Dial, it force closes because the acore processes are still messing up. The intention today was to reload the Cupcake SPL and Radios onto the phone. The issue there is that I can't touch the screen to start the USB connection with my computer.
Anyone have any suggestions aside from paying another $130 bucks??
This will do the trick
google androidscreencast it will allow you to contol your G1 via your PC
...let me know if you have resolved android.process.acore im on the same boat and a wipe and flash has yet to solve it...
same boat for me too! wow, this is three, maybe 4 of us currently experiencing same problem!
I love screen cast. Droid explorer is great too, basically a GUI for adb, and has a plugin for screen cast. Too bad you have to be online though, I'd love to use screencast offline!
I'll update if I figure out the error problem!
Well it looks like a complete wipe and a flash back to non root status is whats gonna take to fix the android.process.acore issue. BUT now w/o root, I cant access the G1 via android screen cast...so im totally stuck on the "Touch Android to begin" screen... sucks to be me lol
I think I'm in the same boat. I didn't know about the screencast application before I did a complete wipe to stock. So I'm stuck at the "touch android" as well. This phones pretty much junk to me right now.
I wonder if any of you have tried restoring your latest back up?
Yes, no help, either on the touchscreen, or the incessant errors. I think there must be some code that checks whether the touchscreen works, and sends back an error if it doesn't. I've tried almost every combination of radios and spls mixed with several different cyanogen roms going back to 4.1, both fresh installs and nand restores.
Currently I'm running the latest cyanogen, radio and hard spl. I get errors often, and can't use the phone / dialer at all without force closing. For now texts and google voice work so I have at least some communication. Ironically, I can't even unroot because none of the spls will flash dreaimg.nbh, but that probelm is in my unresponsive bootloader thread.
Sorry to hear about your predicaments allthrottle and r1ch. Strangely you are right where I'm trying to get, I have warranty coverage to fall back on.

Rooted NC is possessed, need exorcism.

Looking to find anyone with the same issues I am having. My NC is rooted using Auto-nooter for 101. Everything went smoothly no issues at all. A day later my NC has been possessed. When reading a book NC would start to skip pages sometimes as much and 5 pages in fast progression, I would then have to swipe back to my page. Then there are times when the quick nave bar of the NC would start flashing multiple times then click a random book from the home screen or from the daily shelf and open it, when I close it it would do it again this would happen about 3 or 4 times till the screen freezes for about 7 minutes. But its not over, then the NC would automatically go into settings then back to home screen then back to settings again really fast, then again freeze. The only way (and this does work) is to "light boot" it by holding down the power button for 5 seconds (the option to shut down will pop up) then let go then press the power button once quickly on then off. The home screen will come back and the "possession" will have stopped, for awhile. This is getting really annoying, especially the reader skipping multiple pages forward on its own as I do like reading with my NC. So has anyone else have this happening? Any ideas as to what this could be? Thanks for any help or ideas. I have read the forums but it seems I am the only "lucky" one to have this issue. Again thanks.
yes, this happened to me. I went and bought a screen cover and cloth. Cleaned the screen VERY thoroughly and applied to cover. Has not happened since.
Phyllip J FRy said:
yes, this happened to me. I went and bought a screen cover and cloth. Cleaned the screen VERY thoroughly and applied to cover. Has not happened since.
Click to expand...
Click to collapse
Do you mean like an anti glare/non scratch screen protector? I have a great gadget cloth that I use all the time.
brie987 said:
Looking to find anyone with the same issues I am having. My NC is rooted using Auto-nooter for 101. Everything went smoothly no issues at all. A day later my NC has been possessed. When reading a book NC would start to skip pages sometimes as much and 5 pages in fast progression, I would then have to swipe back to my page. Then there are times when the quick nave bar of the NC would start flashing multiple times then click a random book from the home screen or from the daily shelf and open it, when I close it it would do it again this would happen about 3 or 4 times till the screen freezes for about 7 minutes. But its not over, then the NC would automatically go into settings then back to home screen then back to settings again really fast, then again freeze. The only way (and this does work) is to "light boot" it by holding down the power button for 5 seconds (the option to shut down will pop up) then let go then press the power button once quickly on then off. The home screen will come back and the "possession" will have stopped, for awhile. This is getting really annoying, especially the reader skipping multiple pages forward on its own as I do like reading with my NC. So has anyone else have this happening? Any ideas as to what this could be? Thanks for any help or ideas. I have read the forums but it seems I am the only "lucky" one to have this issue. Again thanks.
Click to expand...
Click to collapse
No, you're by far not the only one, seems to be related to bad chargers, bad cables, or bad luck... I've had it happen one time while plugged in, but some people have said they couldn't use their NC at all while plugged in.
There are several threads here already on this subject...
I had some eratic stuff going on...buttons clicking, menus popping up, etc. Cleared up after i cleaned the screen really well and stopped breating so heavily (have a cold and coughing & breath was making the screen moist).
something similar happened to me early on... My K key kept pressing itself, and random key strokes while trying to enter a password... here I think.
Is your screen dirty? I happened to be using mine with sweaty hands right then, lots of finger cheese on the screen was causing false contacts. cleaned it and was good to go.
I have had the "dirty screen" issues as well. But there was one time about a week ago when this was happening even after I cleaned the screen. I completely powered off and rebooted and all has been well since. . .
Thanks for the replies I never thought that my greasy marks would make false positive clicks on my screen. come to think of it it does happen when I am reading for a bit before it starts and eating chips while reading just conjures up those spirits, thanks.
EDIT: Alright I am now convinced that this issue is technical. Its happening again now and my screen is clean and I just reboot it. NC was just sitting and charging I started it to read and it just started jumping to settings again and the Nav bar keeps flashing on and off. This time I just let it go and it went on for 5 min even after the screen turned off. I did the old "soft boot" (check first post) and it stoped. HHHHHHHHMMMMMMMMMM. I think I have a conflict with an app. I did the "save battery by changing the phone.apk and telephony.apk, has anyone also changed this and have this problem?
I had the problem before I did the cell standby battery thing.
In another thread people were solving it by recalibrating the screen. I tried it and it worked for a while before they phantom presses started again, though I might have done it wrong to begin with.
*can't post the link but its in the nookdev wiki.
Sunrisemix said:
I had the problem before I did the cell standby battery thing.
In another thread people were solving it by recalibrating the screen. I tried it and it worked for a while before they phantom presses started again, though I might have done it wrong to begin with.
*can't post the link but its in the nookdev wiki.
Click to expand...
Click to collapse
Thank you so much for this, I did not even know of this site, happy I do now. To anyone that needs this the link is here. Again thanks.
http://nookdevs.com/Recalibrate_the_NookColor_touch_screen
Happened to me when i first got my NC while charging it. Has not happened since.
brie987 said:
Looking to find anyone with the same issues I am having. My NC is rooted using Auto-nooter for 101. Everything went smoothly no issues at all. A day later my NC has been possessed. When reading a book NC would start to skip pages sometimes as much and 5 pages in fast progression, I would then have to swipe back to my page. Then there are times when the quick nave bar of the NC would start flashing multiple times then click a random book from the home screen or from the daily shelf and open it, when I close it it would do it again this would happen about 3 or 4 times till the screen freezes for about 7 minutes. But its not over, then the NC would automatically go into settings then back to home screen then back to settings again really fast, then again freeze. The only way (and this does work) is to "light boot" it by holding down the power button for 5 seconds (the option to shut down will pop up) then let go then press the power button once quickly on then off. The home screen will come back and the "possession" will have stopped, for awhile. This is getting really annoying, especially the reader skipping multiple pages forward on its own as I do like reading with my NC. So has anyone else have this happening? Any ideas as to what this could be? Thanks for any help or ideas. I have read the forums but it seems I am the only "lucky" one to have this issue. Again thanks.
Click to expand...
Click to collapse
I had it happen one time recently while the NC was charging. I was attempting to type a FB reply and the keyboard went all wacky. For every character I hit it entered 3-4 random characters. I switched to Gmail and it did the same thing. I unplugged the NC to plug into the computer to calibrate the screen and immediately after unplugging (before calibrating) it worked perfectly. No problems since.
My God! I thought I was the only one this was happening to. It drives me CRAZY. It happens all the time.
I have hands that sweat almost nonstop, and I think they're what causes this for me. Funny thing is, I never noticed it till I rooted. Does AutoNooter install a custom kernel? That may explain it. Also, it mostly seems to happen when plugged in, which makes me think it may be an issue like on the Evo in it's early days where the screen isn't properly grounded. It was fixed by a sensitivity tweak in a software update, and that should be possible here, I'll look into it.
Someone said a screen protector helps, and I just ordered one to try it. They've helped on past devices, and may here too.
While I have not personally had these problems on either of the NCs in the family it seems pretty conclusive that two things contribute to the problem ... a) 'dirty screen' .. getting a screen protector helps ... b) using while charging .. the #1 'quality' problem reported in the forums seems to be the port/plug on the NC and circumstantial evidence points to the cable .. I don't use the NC while it's charging so don't see the behavior and do use it connected to the PC rarely and do not use the B&N cable to connect so those with the problem may want to try another cable/charger. One of my cables works fine, the other is problematic.

Sliding won't work anymore

Hey guys,
I could need a bit of help! It's now the third time I'm having this problem, don't ask me why. I've got the feeling that I read the whole forum here, but didn't find anything similiar.
The 1st time I didn't change anything (ok, rooted it, but nothing else)
The 2nd time I overclocked it slightly (~850-900 MHz)
Now I'm using MIUI.
But back to the problem:
I'm unable to use the keyboard, every time I'm sliding open the keyboard (even when it's turned off), it "crashes". The screen stops working or it freezes, the only way to turn it off is taking out the battery.
However, the bigger problem comes now: I'm barely able to restart it. It tries booting, but is restarting all the time or the screen is just turning on (in some angles you see that it is turned on but it's black). After many retries, it starts working, sometimes the bootloop is running 15min or i have to manually restart it 10 times or more. The strange thing is that the keyboard works fine, nevertheless I have to choose between using it opened (taking it with me becomes difficult ) or closed...
...the main problem now is flashing a new Rom, I'm currently trying it through the android sdk and adb, but using the power-button + x is easier
I don't think that I can solve the problem, I sent the device two times back (warranty till may 2012), but maybe someone here knows a bit more. My guess is that one of the sensors is broken, or some parts of the display that should manage the sliding process...
Anyway, thanks for your attention!
Web
If you already have Rom Manager, just click Reboot into Recovery..
inches0 said:
If you already have Rom Manager, just click Reboot into Recovery..
Click to expand...
Click to collapse
Tried to use one a time ago, but it wasn't working right....
However, now I'm not even able to boot it, the screen just flashes and turns off itself before trying to restart a few moments later....guess I lost my Milestone
Sbf back to stock?
taptaptouch said:
Sbf back to stock?
Click to expand...
Click to collapse
the computer isn't finding it anymore...I'll back up the data and try use my warranty... I hope that they don't complain about MIUI...
But I'm still not getting the point, why my mobile had these issues three times, although they "repaired" it twice...and nobody else is having the same problem

[Q] Streak 7 keeps powering off and rebooting (even at full charge and after reset)

Hello
I've got a used Streak 7 with the official Dell Honeycomb update. I made a master reset while driving home, then connected it to my WIFI network and worked very well! until it suddenly rebooted while browsing the web. After turning it on again and using the youtube app, the same thing happened even at full charge with the cable still plugged. Annoyed as hell, did another master reset... seemed to work well but after an hour it rebooted again... and does it every 10 minutes or so.
I am pretty sure it is software related because seconds before each reboot, the screen goes black and I am able to read: "Android System" with a weird icon on the top left corner... then It displays the Power Off/Shutting Down dialog (like when you power it off the right way pressing the power button) but then instead of pwering off it reboots itself.
I have noticed that if I leave it alone without opening any applications, it stays on. So far I have done 6 master resets and the issue is still there.
Any help please!!?
anyone?
I'm no expert on this but it seems about all you can do is to NVflash some other ROM since that will wipe your internal memory and repartition it. Then go back to HC again. If you have anything important on your device, back it up somehow as all data will be erased. There are lots of Guides and How To's here, some are good but some aren't! You'll have to read, read and reread till you go blind.
domenicostorino said:
Hello
I've got a used Streak 7 with the official Dell Honeycomb update. I made a master reset while driving home, then connected it to my WIFI network and worked very well! until it suddenly rebooted while browsing the web. After turning it on again and using the youtube app, the same thing happened even at full charge with the cable still plugged. Annoyed as hell, did another master reset... seemed to work well but after an hour it rebooted again... and does it every 10 minutes or so.
I am pretty sure it is software related because seconds before each reboot, the screen goes black and I am able to read: "Android System" with a weird icon on the top left corner... then It displays the Power Off/Shutting Down dialog (like when you power it off the right way pressing the power button) but then instead of pwering off it reboots itself.
I have noticed that if I leave it alone without opening any applications, it stays on. So far I have done 6 master resets and the issue is still there.
Any help please!!?
Click to expand...
Click to collapse
Though you are running Dell's official rom, I'm not sure which rom it is. Anyway, I suggest you follow the instructions here and update it to the newest 514 rom. This will wipe your ds7 and give you a clean start.
http://streakblog.blogspot.com/2012/01/new-patch-to-fix-docking-bug.html
domenicostorino said:
Hello
I've got a used Streak 7 with the official Dell Honeycomb update. I made a master reset while driving home, then connected it to my WIFI network and worked very well! until it suddenly rebooted while browsing the web. After turning it on again and using the youtube app, the same thing happened even at full charge with the cable still plugged. Annoyed as hell, did another master reset... seemed to work well but after an hour it rebooted again... and does it every 10 minutes or so.
I am pretty sure it is software related because seconds before each reboot, the screen goes black and I am able to read: "Android System" with a weird icon on the top left corner... then It displays the Power Off/Shutting Down dialog (like when you power it off the right way pressing the power button) but then instead of pwering off it reboots itself.
I have noticed that if I leave it alone without opening any applications, it stays on. So far I have done 6 master resets and the issue is still there.
Any help please!!?
Click to expand...
Click to collapse
I'm gonna go out on a limb here and say it's a known bug that hasn't been been able to be repaired and/or addressed. The only version that didn't have this problem was the stock Froyo and DJSteve's custom Froyo builds.
The Honeycomb builds, even the stock ones on my Streak did the same thing, and once in a while the ICS beta I'm currently using will randomly reboot if I'm using the browser.
NOW if I remember correctly, DJ Steve's Honeycomb builds R2 through R6 weren't plagued with this that I can remember. I used them all and don't recall random reboots of any kind.
Hope this helps. I know it's frustrating and I used to pull my hair out thinking it was something I installed. It may be my Streak, but down here in Costa Rica there are a group of about 20 of us that have one and I service them all and they were all plagued with the random reboots in the Honeycomb builds
cdzo72 said:
I'm gonna go out on a limb here and say it's a known bug that hasn't been been able to be repaired and/or addressed. The only version that didn't have this problem was the stock Froyo and DJSteve's custom Froyo builds.
The Honeycomb builds, even the stock ones on my Streak did the same thing, and once in a while the ICS beta I'm currently using will randomly reboot if I'm using the browser.
NOW if I remember correctly, DJ Steve's Honeycomb builds R2 through R6 weren't plagued with this that I can remember. I used them all and don't recall random reboots of any kind.
Hope this helps. I know it's frustrating and I used to pull my hair out thinking it was something I installed. It may be my Streak, but down here in Costa Rica there are a group of about 20 of us that have one and I service them all and they were all plagued with the random reboots in the Honeycomb builds
Click to expand...
Click to collapse
I am running stock 514 rom and found it to be less prone to the reboot. Before this update my ds7 would reboot at least 2-3 times a week. Now it would be 2-3 times a month. I noticed that some apps do trigger the reboot, specially poor written apps and non-honeycomb apps. So don't go installling every apps under the sun.
But back to the OP problem, you seem to have an excessive amount of reboot. I would update to the 514 rom first because it is simple and easily done before you nvflash to other roms.
After upgrading to 514, I cant say I've ever gotten a reboot on it since it came out.
Had a fair amount of them on 506 though.
Cant speak for HS as I dont use them.
TheManii said:
After upgrading to 514, I cant say I've ever gotten a reboot on it since it came out.
Had a fair amount of them on 506 though.
Cant speak for HS as I dont use them.
Click to expand...
Click to collapse
I wish I had your luck... On all HC roms... Stock or Steven's I had reboots so bad that my 7 was almost unusable... Not much without root but after root it got real bad... I even quit using it for a while... But mine is the 4G version so that may have had something to do with the instability
SGS II I9100 from TapaTalk
ok, this sucks
thanks... I have been playing with it for more than a week and I've discovered that if I tap on the back of it lightly, it immediately reboots!
The reboot also occurs if I hold it horizontally twisting it a bit (being gentle of course).
So, even if it seems like a software issue (because it reboots instead of suddenly loosing power completely)... it is actually a hardware issue.
I've been reading a lot regarding this problem and learned this also happens on the Dell Streak 5. Some users say that when Android detects an unstable voltage it auto reboots... and the problem with those ds5 is the battery not sitting completely still and it can be solved just by putting a piece of paper under the battery, great for them with a detachable battery! but not for us with a sealed system.
Do any of you have a service manual? I am willing to take it apart to try to solve this problem. My streak is unusable.
domenicostorino said:
thanks... I have been playing with it for more than a week and I've discovered that if I tap on the back of it lightly, it immediately reboots!
The reboot also occurs if I hold it horizontally twisting it a bit (being gentle of course).
So, even if it seems like a software issue (because it reboots instead of suddenly loosing power completely)... it is actually a hardware issue.
I've been reading a lot regarding this problem and learned this also happens on the Dell Streak 5. Some users say that when Android detects an unstable voltage it auto reboots... and the problem with those ds5 is the battery not sitting completely still and it can be solved just by putting a piece of paper under the battery, great for them with a detachable battery! but not for us with a sealed system.
Do any of you have a service manual? I am willing to take it apart to try to solve this problem. My streak is unusable.
Click to expand...
Click to collapse
Our friend TheManii wrote a thread on how to take apart the ds7. Link below.
http://forum.xda-developers.com/showthread.php?t=1441139
Oh wow this sucks... I mean cool guide but it is so extremely difficult to take it apart without damaging it! It is basically being held together with glue :S

[C6903] Persistent problems with full screen and home bar, detailed info.

I updated my C6903 to Android 5.1.1 around... say a month ago? Or around there. It was giving me so much trouble, I couldn't stand to use my phone anymore.
Therefore, I read up on what I could, and attempted my first downgrade to 4.4 KitKat (Central European 01 version 108, unbranded). I didn't wipe the data and that turned into a bit of a mess, but I successfully flashed it and wiped the data properly during the second time around.
But I was still getting some problems, ones that had been occuring since my phone was upgraded to Lollipop. First, that my phone can not enter full screen at all, on any app. The home bar flickers on and off all the time, during Youtube, during any videos, during visualiser, or any app that will make use of fullscreen.
The second issue is that my home keys become unresponsive the vast majority of the time. Restarting does not fix this, and locking my screen then unlocking it again works for roughly 1 minute, then it's back to freezing and no response.
So, considering my main issues were persistent since the update of 5.1.1, I tried a factory reset. I wiped everything and flashed it properly again with Flashtool, to 4.4 KitKat.
It has not worked. Using the developer options/diagnostics I have tested my display and my entire screen has no dead pixels and reacts to the movement or touch of my finger with no issue. So if my screen is fine otherwise, why has 5.1.1 completely ****ed my phone over? It does not make any sense.
At this point I cannot even watch videos or do basic things on my phone as the above issues are preventing me from doing anything. I'm willing to provide as much information as I can, so I would appreciate some help and insight into this. Thank you!
EDIT: Additional information - Trying to view pictures in full screen (Album) ends up with it zooming in and out constantly, even when nothing on the screen is being touched.
When my phone is on landscape/full screen android keyboard, it will intermittently go crazy and start vibrating. I believe it is the symbol key being pressed on it's own, off/on constantly. Nothing on my phone is being touched or moved at this time, it just does this by itself.
it looks like some dirt got on the edges of the screen and it's messing with the touch detection.give that phone a nice bath(one of the best advantages it of being waterproof ) and clean that screen.that should fix it!
masterofnocrack said:
it looks like some dirt got on the edges of the screen and it's messing with the touch detection.give that phone a nice bath(one of the best advantages it of being waterproof ) and clean that screen.that should fix it!
Click to expand...
Click to collapse
The cover for the charger port is broken and just fell off one day a long time ago (it never closed properly, though) so unfortunately, I won't be able to go through with that suggestion.
Added new information. I hope I can get some insight into this soon.

Categories

Resources