PLEASE SEE BOTTOM OF OP FOR UPDATES
-----
Greetings all,
[Backstory]
I've been flashing ROMs for about a year now. I started off with Virtuous Team Gingerbread and the Sense 3.x ROMS. I had no issues.
Then I moved to CM7, and MIUI, also on Gingerbread. No problems.
I've been using the CM9/CM10 ROMs since they appeared for the Incredible 2, from AOKP and Aeroevan, respectively.
Here is where the problems start.
[Problem]
On ICS and JB ROMs, I get what I have dubbed (there is probably a better name for it) "Phantom Touch Input".
At first I thought this was caused by normal bugs and glitches in the ROM. I did my best to deal with it. Usually a simple lock/unlock would solve the issue, temporarily.
So what would happen? Without touching the screen, I would get the long press menu to show up, and then the screen and capacitive buttons would freeze. Or the screen would start to slowly half scroll to the side, and again, freeze.
The most annoying part is when I am typing on the phone. I have tried other keyboards, be it from the MIUIv4, or the default keyboards of 4.0.x, 4.1, or 4.2. All the sudden random keys are pressed, and continue to be pressed, even when my fingers are nowhere near the screen.
However, no one else seems to have this issue, so it looks like I am the lone wolf here with this problem.
Can anyone provide insight? A possible fix? Or am I forced to deal with this on all 4.x ROMs?
---
UPDATE 1: Issues also occurred on CM7.2, so I may be facing a hardware issue.
UPDATE 2: Issues occurred in 4ext Touch. Looking around on YouTube, others (Incredible S users) have similar issues.
Nearly confirmed as a hardware issue.
Check Page 2 for video links.
[::AP::] said:
Greetings all,
[Backstory]
I've been flashing ROMs for about a year now. I started off with Virtuous Team Gingerbread and the Sense 3.x ROMS. I had no issues.
Then I moved to CM7, and MIUI, also on Gingerbread. No problems.
I've been using the CM9/CM10 ROMs since they appeared for the Incredible 2, from AOKP and Aeroevan, respectively.
Here is where the problems start.
[Problem]
On ICS and JB ROMs, I get what I have dubbed (there is probably a better name for it) "Phantom Touch Input".
At first I thought this was caused by normal bugs and glitches in the ROM. I did my best to deal with it. Usually a simple lock/unlock would solve the issue, temporarily.
So what would happen? Without touching the screen, I would get the long press menu to show up, and then the screen and capacitive buttons would freeze. Or the screen would start to slowly half scroll to the side, and again, freeze.
The most annoying part is when I am typing on the phone. I have tried other keyboards, be it from the MIUIv4, or the default keyboards of 4.0.x, 4.1, or 4.2. All the sudden random keys are pressed, and continue to be pressed, even when my fingers are nowhere near the screen.
However, no one else seems to have this issue, so it looks like I am the lone wolf here with this problem.
Can anyone provide insight? A possible fix? Or am I forced to deal with this on all 4.x ROMs?
Click to expand...
Click to collapse
Not exactly sure, I would say its hardware if it happens on all the roms. Have you went back to CM7 or MIUI since this problem started? I would revert back to one of them and test for a couple of days to see if the problem continues. If the problem is only active in ICS or JB then someone else will have to give you a hand on a resolution.
ThePhantom97 said:
Not exactly sure, I would say its hardware if it happens on all the roms. Have you went back to CM7 or MIUI since this problem started? I would revert back to one of them and test for a couple of days to see if the problem continues. If the problem is only active in ICS or JB then someone else will have to give you a hand on a resolution.
Click to expand...
Click to collapse
Ok will do when I have the chance.
Thanks for the speedy reply.
But let's say it is a hardware issue...
Do I unroot/restore/whatever and bring it back to Verizon?
Thanks.
[::AP::] said:
Ok will do when I have the chance.
Thanks for the speedy reply.
But let's say it is a hardware issue...
Do I unroot/restore/whatever and bring it back to Verizon?
Thanks.
Click to expand...
Click to collapse
Yes if the phone is still under warranty
I'm so fresh you can suck my nits...
Flashed CM 7.2
My home button didn't work, but that doesn't really matter.
I still experienced the same issues.
On a side note, wow CM7.2/Gingerbread is smooth....damn kernel. But stock 2.3.x is so ugly
Anyways, it seems like I should just "start clean".
I'm not sure what that entails - not just a full wipe...something more...tips?
[::AP::] said:
Flashed CM 7.2
My home button didn't work, but that doesn't really matter.
I still experienced the same issues.
On a side note, wow CM7.2/Gingerbread is smooth....damn kernel. But stock 2.3.x is so ugly
Anyways, it seems like I should just "start clean".
I'm not sure what that entails - not just a full wipe...something more...tips?
Click to expand...
Click to collapse
I use 4ext recovery myself, and I do a "full wipe" by format all partitions/factory data reset, then I see a lot of people also say wipe cache and dalvik so I throw that in as well, it don't take long but just in case a factory reset don't get them I just do it...lol. Hope that helps, and that may clear up some bugs with ICS and JB roms if you weren't doing that before. Just make sure you do a backup before wiping everything. Wouldn't want you to be without a phone if some process hiccups.
Thanks for the info.
Should I do anything with my SD card? It shouldn't affect ROM performance, but a wipe wouldn't be a bad idea, yes?
[::AP::] said:
Thanks for the info.
Should I do anything with my SD card? It shouldn't affect ROM performance, but a wipe wouldn't be a bad idea, yes?
Click to expand...
Click to collapse
I doubt that the SD card would affect the performance, but as long as you have backups of everything you can do as you please, backup backup backup. You don't want to lose everything, trust me I have seen bad things happen to guys that don't backup, and I have learned from experience as well.
Right right I know.
I'll try 4ext on a fresh ROM and see how things go.
Not a good idea to flash the touch version of 4ext in light of my issues.
Did a Nandroid, hit back, then screen input froze. The on-screen time is updating, but are the capacitive buttons are lit up but do not respond/give haptic feedback, let alone the touch screen itself. Power button just moves to the power menu, where I again cannot select anything.
Pulling battery :/
This is why I will never (want to) purchase a phone without a removable battery.
So looks like my issue isn't software related. (This issue can in no way be software related [or even caused by], right?)
I've had the phone for over a year...but I guess I'll try with Verizon.
*sigh*
What a pain.
Looks like I am certainly not alone.
(Better video) http://www.youtube.com/watch?v=25CaiveQoQg
(Similar) http://www.youtube.com/watch?v=kANVkc-Sk74&feature=related
I'm just really pissed off. And there isn't a phone in the market that I want.
That looks like possibly a bad digitizer, you can replace that fairly cheaply if you are out of warranty. That would be my best guess, and keep in mind I am no expert. Here is a link so you can see the process:
http://www.youtube.com/watch?v=LQL9gakQyuI
ThePhantom97 said:
That looks like possibly a bad digitizer, you can replace that fairly cheaply if you are out of warranty. That would be my best guess, and keep in mind I am no expert. Here is a link so you can see the process:
http://www.youtube.com/watch?v=LQL9gakQyuI
Click to expand...
Click to collapse
That is what I was thinking.
I'll also see if I can milk anything out of Verizon. I'm already an unhappy customer, given the lack of ICS, especially when promised.
Yep, digitizer.
http://forum.xda-developers.com/showthread.php?t=1399085
Good luck with Big Red, and let us know if you get it resolved.
ThePhantom97 said:
Good luck with Big Red, and let us know if you get it resolved.
Click to expand...
Click to collapse
Thanks, I'll keep everyone updated.
I'm sure I'm not the only one who has had issues. Hopefully word spreads, especially to those still under warranty who are suffering from a faulty digitizer.
Related
My phone goes to sleep
and does NOT wake up, the bottom row of buttons and keyboard both light up if I open them or press them.
Help please!
rossle12 said:
My phone goes to sleep
and does NOT wake up, the bottom row of buttons and keyboard both light up if I open them or press them.
Help please!
Click to expand...
Click to collapse
Stock ROM or custom? Any overclocking?
The phone powers up if you soft reset, correct?
Well, I found out it was a small problem with the rom.
It was a custom rom, and I just installed a different one and it works flawlessly.
With the other one, the light sensor did not work either.
Also, I dropped my phone the other day, and a really small spring fell out.
And the back plain on my screen is loose and opens up easily..
Which ROM?
I hate to hijack this thread but i am having the exact same problem. Basically when i put my phone to sleep its hit or mess as to if it will wake. It seems to have started when i flashed Energy ROM. It was terrible after that, so I switched back to the stock ROM available from the HTC website and all seemed well at first. Now its back to hit or miss.
I cant really rule out a hardware issue such as a broken sensor or something because I'm not sure how the mechanics of it work. When i push the power button on top the phone wakes but not the screen I know this because the 4 lights on the bottom light up and the keyboard as well. I can hit the button repeatedly but it doesnt help. At other times it works flawlessly, but usually does not.
Can anyone give me a suggestion as to what it could be, or a way to rule out a hardware issue?
Exactly my problem!
It was perfectly fine for the first day or so before it started crapping out again..
Can someone please help us with this problem?
It's mind consuming and it's making me worry.
Until TP3 is out, I won't get a new phone ):
Well, the problem is discussed in great detail on the internet, but no one can give a definitive answer. ..
I've been a touch pro 2 user for exactly 3 days... My new HD2 from T-Mobile is in the mail... This is a un acceptable flaw with no real solutiion... Good Luck TP2 users....
Good luck to you.
I've had mine for over two years and it was flawless
Just one recent drop determined everything
Although I Must say, it was one hell of a durable phone
Yea, dont get me wrong. I really like the phone. Thats why I'm getting the HD2. Great OS and big beautiful screen. I'm gonna miss the slide out keyboard but I think thats what breaks these phones.
I'm excited that there's the possibility of running Windows Mobile 7 on it.
rossle12 said:
Can someone please help us with this problem?
Click to expand...
Click to collapse
I'd like to try to help. But you never answered my question of what ROM you are on (and which one you tried previously).
I've determined my problem is 100% hardware related. If I open my keyboard and then grab the screen and tweak it while pressing the power button it comes onn 100% of the time. Sux, but at least I know the cause now
djowen6565 said:
I've determined my problem is 100% hardware related. If I open my keyboard and then grab the screen and tweak it while pressing the power button it comes onn 100% of the time. Sux, but at least I know the cause now
Click to expand...
Click to collapse
Every once in a while my phone would turn on and I wouldn't know why
But yeah, I think it is hardware related.
I previously used Energy then went to Jacko's.
Both were perfectly fine, just the upsetting sleep function and light sensor would keep the phone off.
HELP: Same problem Phone not waking up
Hi saw this thread and was wondering if anyone can help me.
I have an HTC Touch Pro 2 for some month now...
Using the following details:
OS Version: 5.2.21887 (21887.5.0.86)
ROM Version: 2.07..401.1 (80303) WWE
ROM date: 02/04/10
Radio ver: 4.49.25.91
stock ROM basically...
THe issue is that the phone doesn't wake or when using it just freezes/hangs.
Not much software/apps installed... and memory is good as well.
I just don't know what's going on...
Help please.
Thanks
rossle12 said:
Every once in a while my phone would turn on and I wouldn't know why
But yeah, I think it is hardware related.
I previously used Energy then went to Jacko's.
Both were perfectly fine, just the upsetting sleep function and light sensor would keep the phone off.
Click to expand...
Click to collapse
I'd agree with the notion that its likely hardware related. I've flashed maybe 10 different builds of Energy over the last 7 months or so, and never once had and issue with the SOD (sleep of death) that I can recall. A bad flash can sometimes happen. But since you flashed another reputable ROM (Jackos), that somewhat eliminates the possibility that a bad flash is the culprit.
You can start from scratch, by running Task29 to format the ROM area of the phone's memory, and reflash the ROM. But this would be just to eliminate the possibility of a bad ROM flash. My gut says that you won't see any different results.
Running the phone "clean" for a while (to see if you still have the SOD) without any software installed or any other modifications will eliminate the possibility that any software or mods are responsible for the issue.
are you sure its hardware related? because my phone started doing this yesterday too...I had an energy rom from october, and it was really buggy. I am only able to keep my phone from sleeping when it is plugged in to some power, so i flashed the newest energy rom and still having the same problem...wont wake up from sleep
EDIT:
I dont see how this can be hardware related because everytime i soft-reset, the screen works again. this problem only happens when the device goes to sleep...
Any overclocking?
As I already mentioned, I never had any SODs on Energy that I can recall, except when using OCT (OverClocking Tool).
I have done no overclocking...I just flashed the newest energy rom like 15min ago...is there anything else I can do or check? it looks like the phone works still, just no backlight...
After flashing the ROM, maybe try running it "clean" for a day or two, don't install any software or do any mods, reg edits, etc. If you still have problems with the phone waking up with a new ROM, and no other software or other mods, than it may indicate a hardware problem.
And be sure to run Task29 before you flash the new ROM, if you don't already do that.
You guys should read the following thread:
http://forum.xda-developers.com/showthread.php?t=648134
You're not the only ones (by any means) with the SOD issue. But it isn't at all clear what causes the issue. Lots of different theories in that thread about various software or ROMs, with no clear solution.
Lots of conflicting info, but some comments on the thread suggest (as I mentioned) that Task29 may help (certainly can't hurt).
moto2000 said:
are you sure its hardware related?
Click to expand...
Click to collapse
Nope, definitely not sure, especially after reading the thread linked above. But as I suggested before, Task 29, try a different ROM, and run it clean with no software or mods, and start eliminating the variables.
This is my first time posting. I know how annoying reposts are, so I tried to find if anyone else had the same problems I have. Unable to find an answer, I seek a solution to my strange problem...
I flashed CM7 three days ago. Before flashing, I did a full factory reset, wiped cache, etc. I also performed a backup of rom, which was at the time CM6. Everything worked without a hitch for these past three days. I installed new programs, really enjoyed the new features. However, today, the screen suddenly became unresponsive.
It acts as though I am long-pressing something when I am not. It will not register even hard taps and when I try to hit the home key it brings up the most recent apps list as though I long-pressed. I have reset, but it keeps doing this. When I try to use an app where scrolling is required, it bounces back to the spot I started scrolling. Very frustrating. Any solutions?
At first I thought it was from installing swype beta, but after removing it completely, resetting, and reflashing, the screen continues to act up.
Flash your backup and see if you still have the same problem
Sent from my HTC Vision using XDA Premium App
Spastic909 said:
Flash your backup and see if you still have the same problem
Sent from my HTC Vision using XDA Premium App
Click to expand...
Click to collapse
Hey thanks for your suggestion. I've tried it but the screen problem continues. I even tried going back to the stock rom. Do you think it's a hardware issue?
Having the same problem using MexDroid for the G2...have to resort to the trackball half the time because the touchscreen doesn't work right or at all.
I reinstalled the ROM twice already and it keeps acting up at some random point after installing a few apps (none of which affect the touchscreen as far as I know). Tried clearing cache, dalvik cache, and fixing permissions...nothing. Happens regardless of overclock settings too.
magus57 said:
Having the same problem using MexDroid for the G2...have to resort to the trackball half the time because the touchscreen doesn't work right or at all.
I reinstalled the ROM twice already and it keeps acting up at some random point after installing a few apps (none of which affect the touchscreen as far as I know). Tried clearing cache, dalvik cache, and fixing permissions...nothing. Happens regardless of overclock settings too.
Click to expand...
Click to collapse
It's nice to know I'm not the only one with this problem... i.e. misery likes company... but I'm also sorry to hear that you have the problem, as well. There seems to be nothing that I can do at the moment. Since the phone is still under warranty, I guess I could just flash the original rom, factory reset, and send it back for a new one. I'd rather find a solution, though, in case it happens again.
wronskishin said:
It's nice to know I'm not the only one with this problem... i.e. misery likes company... but I'm also sorry to hear that you have the problem, as well. There seems to be nothing that I can do at the moment. Since the phone is still under warranty, I guess I could just flash the original rom, factory reset, and send it back for a new one. I'd rather find a solution, though, in case it happens again.
Click to expand...
Click to collapse
The weird thing is that it only happens sometimes...like, sometimes I'll get 100% accurate/responsive touchscreen use, while other times I can pinch all I want and never zoom in. I think it might have something to do with my lowering the screen density - right now I have it at 140, and earlier at 190, and it seems that when I have the stock 240 or the 190, I have better luck with the touchscreen than with at 140...but the usefulness of the lower screen density outweighs the better touchscreen for me.
magus57 said:
The weird thing is that it only happens sometimes...like, sometimes I'll get 100% accurate/responsive touchscreen use, while other times I can pinch all I want and never zoom in. I think it might have something to do with my lowering the screen density - right now I have it at 140, and earlier at 190, and it seems that when I have the stock 240 or the 190, I have better luck with the touchscreen than with at 140...but the usefulness of the lower screen density outweighs the better touchscreen for me.
Click to expand...
Click to collapse
How do you change the screen density?
I wanted to get the opinion of the devs who make all of the ROMS for this device. Below is my experience and my theory:
I have had the phantom soft key issue on every incarnation of the GSII software. I un rooted and went all the way back to the beginning. I used each rom version till the issue occurred, then I let the phone update to the next ROM version and repeated the process. Every single un rooted update had the same issue and then every single Rooted ROM all ROMS for the ET4G were tried and the issue occurred.
Strange part is it came out of nowhere. I have had and have been flashing for an entire year without issue and one day all of a sudden... BOOM. I don't think it is as simple as the signal issue. I think it has to do with flashing as well. Unless this is happening to someone who has never rooted their device, I think something in the roms we flash trigger the issue which is related to signal.
Has anyone known anyone who has never rooted their device and has had the issue? By the way, the store gave me a brand new factory OEM screen and the issue still occurs.
Gorguts said:
I wanted to get the opinion of the devs who make all of the ROMS for this device. Below is my experience and my theory:
I have had the phantom soft key issue on every incarnation of the GSII software. I un rooted and went all the way back to the beginning. I used each rom version till the issue occurred, then I let the phone update to the next ROM version and repeated the process. Every single un rooted update had the same issue and then every single Rooted ROM all ROMS for the ET4G were tried and the issue occurred.
Strange part is it came out of nowhere. I have had and have been flashing for an entire year without issue and one day all of a sudden... BOOM. I don't think it is as simple as the signal issue. I think it has to do with flashing as well. Unless this is happening to someone who has never rooted their device, I think something in the roms we flash trigger the issue which is related to signal.
Has anyone known anyone who has never rooted their device and has had the issue? By the way, the store gave me a brand new factory OEM screen and the issue still occurs.
Click to expand...
Click to collapse
I had the issue straight out of the box when we still had gingerbread. I hardly get it anymore besides on occasion
Sent from my SPH-D710 using Tapatalk 2
Elw00d said:
I had the issue straight out of the box when we still had gingerbread. I hardly get it anymore besides on occasion
Sent from my SPH-D710 using Tapatalk 2
Click to expand...
Click to collapse
Right outta the box before rooting it?
I personally think its hardware related with, either over time the screen moving and the heating up of the device causing phantom button presses... this only recently started happening to me and after i wipe screen with cloth while its turned off it goes away. for awhile... idk haha
I disabled the hardware capacitive keys and use the software on screen buttons. Problem solved
Sent from my SPH-D710 using xda premium
As said above, I had this issue on Gingerbread..out the box, no root. It'd press menu by itself lol, always gave me WTF moments. I'm on ICS now, and no problems at all.
Crazy, ok. Well I got the answers I was looking for. Thank you everyone for your info. Note 2, here I come.
Yup, happens here too. Menu key goes nuts when charging.
FYI just cause you want to get a developers opinion does not give you permission to ask a question in the development section.
Papa Smurf151 said:
FYI just cause you want to get a developers opinion does not give you permission to ask a question in the development section.
Click to expand...
Click to collapse
I will begin chastising myself at once....
Gorguts said:
I will begin chastising myself at once....
Click to expand...
Click to collapse
Picture please ^^^^^^^^^
I have this issue on out of box uprooted and other sget4g were okay for some time after rooting and flashing custom made roms... They too fell prey to the mysterious phantom presses... Ahhh the horror.
My fix was....... To
I have had this issue several months and now have a good solution. Use this info posted by elijahbrown on Page 464 in PA thread I believe. http://forum.xda-developers.com/showthread.php?p=34125394
" Disables menu key!
Ooookay..
Go to system/usr/keylayout
Select sec_touchkey. kl and edit as text. You'll see key 217 is search. Delete that line of code or put a "#" in front of it to turn it into a comment. Save the file.
Re boot and let meet know.
Just curious as to why you want to do this so bad? "
# comment out menu and search keys. Save file and Set permissions.
Then head over to the play store and get Button Savior. I paid for the advanced features and am very happy. Have to keep the phone until may 2013, sprint claims liquid damage so no replacement.
Button Savior on screen hidden pop up menu buttons works great and no more phantom presses menu or search pop ups ever again! 
So here's what I've discovered.
As of now, on stock 4.1.1, the phone runs smooth when audio is screwed up. The moment touch sounds work again (or the moment I install SoundAbout to fix it) it starts lagging like crazy. Is this a hardware thing? After switching roms, kernels, versions of Android, flashing stock and locking the bootloader nothing has worked.
_________________________________________________________________________________________________________
So I'm having this strange issue that I don't really see mentioned previously (based on my multiple searches)
My phone was running fine until I flashed Paranoid Android (The last Jellybean 4.1 Release). On this ROM i was getting some insane lag, sluggish performance. I'd swipe on the home screen and get a huge delay or the phone would read it as a long touch and bring up the wallpapers option. Opening folders and the app drawer had some serious slow downs. It was a real mess.
I assumed the phone just didn't play well with the ROM so I flashed over to Bugless Beast. The odd thing is that the problems persisted. I would get just as horrible performance and the same sluggish visual effects and stuff. Specifically I remember even the audio slowing down and being choppy (touch sounds) until they automatically disabled themselves and the ROM ran smooth for a bit but returned to the sluggishness again.
So last night I restored to stock flashing the stock image and relocking the bootloader. Rooted, unlocked, flashed recovery again and loaded up Bugless Beast and the issue is still happening. Even got my first random reboot on Bugless Beast today after it slowed down really bad. Now I've noticed that when touch sounds disable themselves so does media audio (while the ringer and notification sounds still work). This is pretty much why I'm convinced it's a software problem and not a hardware one.
Basically I just wanted to know if anyone's experienced something similar and found a way to fix it? Probably going to reflash to stock tonight
EDIT: Well it seems like the audio thing might be a hardware issue. SoundAbout fixed that but I don't see how my audio jack could have been damaged in between flashes.
EDIT 2: Current State:
- I tried flashing just the system img (multiple times) and the lag returned
- I just flashed a 4.2.1 ROM just to see what happened. Touch sounds are back which means my headphone jack fixed itself. Still EXTREMELY slow.
- And just like that headphone jack screwed AGAIN but no more lag? Any reason for these two things to be related?
Bump. Any help? Still happening, though not as common, when I flashed stock
Could it be a hardware problem? Though it would be odd for a hardware issue to show up after flashing a rom. How long have you had the phone before the issues started?
Have you tried the official 4.1.1 image?
If so, do problems go away?
If you are using ports you have to expect bugs.
Let us know
Sent from my Galaxy Nexus using xda premium
Try flashing just the system.img a few times in fast boot with a reboot boot loader between. I was having slow boot up and random performance issues on full stock until I flashed that partition with the stock image (3 Times to be precise). I no longer have the 5 minute wait for the Google logo to disappear, and overall much snappier. Apparently something was leftover from previous restores/downloaded OTA updates.
Sent from my Galaxy Nexus using xda premium
I'd suggest you stop messing around with multiple ROMs and start trying different kernels. Kernels will impact performance much more than any specific ROM will. Try either an updated version of leanKernel (assuming your sig is accurate) or a different kernel all together. Others have had luck with franco, trinity, etc, etc.
Had the same problem on my GSM GNex yesterday. Flashed a ROM combination (Xylon 4.2.1 + Lean Kernel 5.0) and had this lag.. everything would lag and FC.. tried a full wipe as well but didnt work..
Changed to another AOSP Rom (UDK 4.2.1 with linaro kernel) and its fine now..
Oh and i also changed recovery from 6.0.1.5 non-touch(that i flashed yesterday) to CWM 6.0.1.9 touch..
Not sure if this helps but thats what worked for me.. I suggest going back to a ROM that worked for you in the past.. and also try formatting your SD card and run the phone without putting back your data for a while..
@rlb81 - Starting to think it might be a hardware one but at this point I'm not sure of anything. Only had the device 3 months.
@tincbtrar - Yeah I flashed the official 4.1.1 image and the problems are still there. Ridiculously sluggish and the audio problems. In fact, on stock 4.1.1 I just had this issue where I'd turn the screen off, the animation would be really slow, and then I'd get a black screen and wouldn't be able to wake it up. Did a battery pull to boot it again and the same exact issue the second time it turned on.
@Winesnob - I'll be sure to give this a try. Thanks so much! This is a really odd issue and I've never experienced it on any of my previous android devices (Fascinate, Incredible, Thunderbolt, even the old HTC Vogue)
@Cilraaz - Currently just trying to get stock running properly so everything is locked right now. Can't remember but I'm pretty sure I tried the newer lean kernel when I flashed back to bugless.
@technogravy - Kinda the same response I have for Cilraaz here. Ideally I'd like to get stock running properly so that I can be sure there isn't something horribly messed up with my phone but I'll be sure to give both of your suggestions a try if things don't seem to work with stock.
Thanks so much to all of you guys. If you have any other input it'd be greatly appreciated.
+1 on try different kernels, my phone seems to love lean kernel. I switched to tiny kernel for a few days and every so often, a simple task like opening tapatalk would take up to 30 seconds, and everything would become unresponsive. Nothing but smoothness on lean, give some different kernels a try.
Sent from my Galaxy Nexus using Tapatalk 2
I tried Winesnob's method and I THOUGHT it worked. Was running smooth for a good amount of time and just now back to the really choppy mess it was before. In fact it just got frozen on the lock screen and went to a black screen again.
This is killing me. The headphone jack thing seems to be a hardware issue anyway so I emailed Wirefly about getting a replacement. I feel like they'll avoid that though and I'll be left with this.
Gonna try some other things tonight. Wish me luck
EDIT: The thing gets so choppy that notification sound get choppy and crackle. This is insane. I'm fully stock minus the unlocked bootloader right now
EDIT2: Flashed stock image and touch sounds came back. This is getting really weird. Lag is still here though. Really bad lag
Bumping again now that I've sort of pinpointed the issue. Lags with touch sounds enabled and headphone jack works / soundabout installed with touch sounds on.
Currently the phone's headphone jack is screwed up, I installed soundabout, disabled touch sound and no lag.
Over in the dinc2 forums a lot of people are having the same issue when going from vipers sense rom back to aosp. I know that's not the case here but they found it was due to a new lib partition that was introduced in jb. Again, not sure if I'm 100% on this, but it does sound like a bad wipe and something is getting left from previous roms
Sent from my Incredible 2 using xda app-developers app
Ahh thanks for the heads up
Would it be wise for me to try going back to the ROM that started the problem? Maybe that'll do *something?
Again, from what I saw, everyone had some luck going back to the rom that caused the problem.
There's a tool in the developer thread called "super duper wipe" that seems to have fixed the lag for ones having the issue. I'm not sure how it works, but If you can take it apart and look at the zip, it may point someone in the right direction.
Sent from my Incredible 2 using xda app-developers app
---------- Post added at 12:23 AM ---------- Previous post was at 12:22 AM ----------
The dev thread in the DROID incredible 2 forums.
Sent from my Incredible 2 using xda app-developers app
SkinnyT said:
Over in the dinc2 forums a lot of people are having the same issue when going from vipers sense rom back to aosp. I know that's not the case here but they found it was due to a new lib partition that was introduced in jb. Again, not sure if I'm 100% on this, but it does sound like a bad wipe and something is getting left from previous roms
Sent from my Incredible 2 using xda app-developers app
Click to expand...
Click to collapse
I took a look at that super duper wipe script...looks interesting but not necessary on our phone.
Im starting to think you may have a hardware issue if you cant flash stock images and get everything back to normal. Maybe a relock and then unlock?
i just did this cause I had a SIM card issue...and naturally it wiped my data completely.
solarpolitiks said:
...
@technogravy - Kinda the same response I have for Cilraaz here. Ideally I'd like to get stock running properly so that I can be sure there isn't something horribly messed up with my phone but I'll be sure to give both of your suggestions a try if things don't seem to work with stock.
...
Click to expand...
Click to collapse
turns out my lag problems weren't gone completely until i wiped /System before flash.. Alot of ROM's out there have a /system wipe script, but the one causing my FC's and lag didn't, so it was installing the new system files on top of the old ones and possibly causing a conflict.
it could the same for you
Yeah I've recently tried unlocking again, formatting system before a ROM flash and I still get lag. Now it's more that it will last a day without the lag and just magically come back the next day. Headphone/speaker issues still exist. Wirefly completely ignored my first email so I sent them another one. Hoping for the best.
Completely lost on what this could be
anyone see this thread?
http://forum.xda-developers.com/showthread.php?t=2029246
I have random lag on my vzw nexus and i think its io related and nothing to do with the kernel.
Sent from my Galaxy Nexus using Tapatalk 2
I'll check out that app but like I've mentioned. Lag seems to be coming from sound. After installing soundabout to get the speaker working again I get some nasty lag. Disable touch sounds and I have no lag. Disable the sound effects on twitter - no issues with the app. WireFly said I'm still under manufacturer warranty through my carrier and it sounds like I should be covered. If Verizon tries anything to get around that they'll be willing to do a three way call to make sure I get the replacement. I'll probably end up with a refurb but hopefully it'll beat this stupid issue.
Just stopping in to say thanks to everyone that tried to fix the issue but Verizon is sending out my replacement device today and I'll be sending this one with the faulty headphone jack back.
Problem solved!
Hi everyone,
TL;DR: I have an issue with the touchscreen of my Find 7 qhd (x9076), while on any other ROM than stock it my touchscreen glitches or something.
After installing a custom Rom, like PA, Dirty unicorns, CM, Nameless or any other available for this device (I believe I've tried all of them). The device works just like it should, nothing wrong with the touchscreen. But after like half a day, it starts to 'glitch'. Sensitivity is very low, when I press here it detects a press somewhere else.
I've got a temporary solution which is wiping the cache in recovery, then it works for a short period of time, but then it starts gliching again..
On stock rom the issue doesn't exists, but I realy do want to use a custom one.
Is anyone experiencing the same issue? Or maybe someone who has a solution?
Thanks in advance!
P.s every install is a full wipe, tried multiple recoveries, non-unified
I've read that the touchscreen fixes implemented by Oppo only work on ColorOS even though ROM makers have already implemented the fixes into the Roms. I'm not sure why, though
farenteria said:
I've read that the touchscreen fixes implemented by Oppo only work on ColorOS even though ROM makers have already implemented the fixes into the Roms. I'm not sure why, though
Click to expand...
Click to collapse
Hmm that's unfortunate, but it seems to me that I am one of a few people having trouble with this? Why don't other x9076 users have this problem?
B-vb said:
Hmm that's unfortunate, but it seems to me that I am one of a few people having trouble with this? Why don't other x9076 users have this problem?
Click to expand...
Click to collapse
Not sure. I personally have never had that problem
I want to bump this thread, i have this problem aswell and still it isnt fixed. anyone has a idea what to do about it ?
B-vb said:
Hi everyone,
TL;DR: I have an issue with the touchscreen of my Find 7 qhd (x9076), while on any other ROM than stock it my touchscreen glitches or something.
After installing a custom Rom, like PA, Dirty unicorns, CM, Nameless or any other available for this device (I believe I've tried all of them). The device works just like it should, nothing wrong with the touchscreen. But after like half a day, it starts to 'glitch'. Sensitivity is very low, when I press here it detects a press somewhere else.
I've got a temporary solution which is wiping the cache in recovery, then it works for a short period of time, but then it starts gliching again..
On stock rom the issue doesn't exists, but I realy do want to use a custom one.
Is anyone experiencing the same issue? Or maybe someone who has a solution?
Thanks in advance!
P.s every install is a full wipe, tried multiple recoveries, non-unified
Click to expand...
Click to collapse
Try to flash back stock recovery then flash COS 1.20 in systembase, then upgrade to COS 1.25, Then upgrade to 2.0 or above. Then flash custom recovery and rom again. This is the step you will not have problem in custom Rom. I am 100% sure.
Sent from my X9070 using XDA Free mobile app
I have the same problem, and I'm running Stock OS.
v2.1.4i Beta
This is how I bought the phone, interesting that it reads Beta...
I've updated to the latest firmware and still having touch screen sensitivity issues.
Someone has got too have some advise.... Oppoooooo.....
TouchScreen Auto Test - FAIL
I did the TouchScreen Auto Test and showed FAIL. Has anyone else shown this error?
Hi, I am having exactly same touch screen problem with custom roms, have tried both Omni and crDroid.
Is there a solution for this? I didn't have this problem in COS before.
What's the auto test?
I‘m on COS 2.1.5I and sensitivity works ok so far. I did have auto brightness problems but xposed and gravitybox has helped me adjust a lot of that out. Now it doesn‘t over dim in low light.
Auto test in COS is ok, I only had this problem in custom Roms, COS worked smoothly,so I reckon it's could be driver issue in custom Rom, maybe there are new fix for some panels are not included in custom Rom.
I never had any problems with touchscreen on find 7 until now. I have been extremely satisfied with this device until now. I have the find 7 9076.
There is a lengthy discussion of this touchscreen problem on the oppo forums.
My opinion is, it has nothing to do with the rom or firmware. It is a physical problem caused by heat. Once overheated, the digitizer gets somehow damaged.
I left my phone on a table in direct sunlight for hours while working on my lawnmower. I noticed it got very hot to touch. Ever since then my touchscreen has problems where there were no problems for 2 years prior. Dead spots, phantom touches and behaves sluggish in certain spots. Upper screen in portrait.
I tried wiping and reinstalling. Nothing works to fix this.
I even tried sealing it in a ziplock bag and freezing it. This actually works but its only temporary. The digitizer got damaged from heat. There is no "software" fix.
The only solution I can see is to physically replace the digitizer. This is a difficult thing to do but can be done.
I am considering replacing replacing the entire screen along with the digitizer as this is much easier but the problem is getting the high res replacement. Most after market screens are not equal to oppo's. The cost of OEM is too high.
Shame because this problem makes me now shy away from oppo devices.
Okay,
I opened up the phone.
Set to try and pry off/seperate the digitizer and replace with new one.
Decided to try something first.
Unplugged the digitizer and held power button (to release any stored up energy in the phone). Resnapped in digitizer cable to connector.
Reassembled the phone.
Put battery back in. Rebooted.
Sure enough, its all working. The full touchscreen is working with no dead spots or glitches.
For how long? Who knows?
Keeping this thing out of the heat.