Database Info

No sound on touch screen

Have the Thunderbolt set up for making sound when touching screen. The screen will work as it should and then without reason it will get very soft and sometimes completely stop making any sound. Checked all my settings and they are as they should be. I also have the Sensation and the screen is set up the same way and it works properly. Is there something I'm overlooking or is this another bug?? Any help would be welcomed. Running stock Thunderbolt.
Thanks,

restart phone and go from there
Sent from my ADR6400L using XDA App

vinnyjr said:
Have the Thunderbolt set up for making sound when touching screen. The screen will work as it should and then without reason it will get very soft and sometimes completely stop making any sound. Checked all my settings and they are as they should be. I also have the Sensation and the screen is set up the same way and it works properly. Is there something I'm overlooking or is this another bug?? Any help would be welcomed. Running stock Thunderbolt.
Thanks,
Click to expand...
Click to collapse
It's a bug of some kind. I've had it since the day I bought my TBolt(Launch Day). I think the reason its not heard about much is because most users don't use the screen sound option and also because a lot of users here and at AC root and flash custom roms.
I'm still running launch day software because it just works for me for the way i use my device.... this being the only bug that affects me. I rooted and flashed this rom:
http://forum.xda-developers.com/showthread.php?t=1013577
and the issue went away so if it really bothers you I would go that direction. I assume other custom roms fix it as well but I cannot comment as the above is the only rom I flashed before going back stock and un-rooting.

Thanks for your input, checked other sites and found other people with same issue. Going to root this thing anyways and I'm sure the new Rom will fix the issue. Might check out the one you downloaded, looks pretty fast.
Thanks again.

Android Revolution Q&A

As some of you have come from the captivate know what I did there with Rom Q&A threads. I am doing the same here. In an effort to clean up the site. All Rom related question shall from now on be posted in the proper Q&A or will be deleted on sight.

Just saying it should be Android Revolution HD
Thanks for your effort!

mike1986. said:
Just saying it should be Android Revolution HD
Thanks for your effort!
Click to expand...
Click to collapse
We'll shall change that
Sent from my HTC Inspire 4G using XDA Premium App

WiFi not working?
I just installed this Rom and now wireless is not working any suggestions?
EDIT: It was my router config all is well.

Gps Issues
I love this Rom but I can't get my gps to work very well. I tried Lee's and cyno just didn't like them but the GPS worked. I really don't want to have to switch away from it just because I can't use apps that use my gps ( mapmyrun, google latitude)
Sometimes, it will work with an accuracy of like 800-2000 ft after fixing for 10-15 minutes. I have tried every solution on the Android Revolution F.A.Q section Q.14. It worked fine before and if I switch to a different ROM. Also, I have tried apps like GPS FIX, Faster fix, and Gps essentials. My radio is the suggested one for the ROM.
Any ideas I'm desperate?

Also I have noticed when trying this fix.
http://forum.xda-developers.com/showpost.php?p=12185980&postcount=20784
Under my
gps.conf file (inside system\etc):
I have no gps.conf file at all.
Any ideas?

So my question.. By far ARHD is my favorite rom, the only issue I'm having is that every once in awhile when i try to unlock the phone it won't respond the anything. The only way to get it to turn on again is a battery pull. I remember when I had my captivated I had similar issues but muuuuch worse. I followed the flashing directions line by line and did a full wipe. The last time it happened was today right before I updated to 5.2.4 so ill see if this makes it any better. Any ideas why this is happening, does my processor not like OC and I need to scale it down? Other than that I love everything about the rom thanks in advance for any help.

Does anybody have any idea why I can't set a permanent screen lock? It's like everytime I set a pattern lock or PIN lock, it works once then no longer requires a pattern or PIN to unlock my phone depending on which one I chose to use. Any help would be appreciated.
Sent from my Inspire 4G using XDA App

ryan09266 said:
So my question.. By far ARHD is my favorite rom, the only issue I'm having is that every once in awhile when i try to unlock the phone it won't respond the anything. The only way to get it to turn on again is a battery pull. I remember when I had my captivated I had similar issues but muuuuch worse. I followed the flashing directions line by line and did a full wipe. The last time it happened was today right before I updated to 5.2.4 so ill see if this makes it any better. Any ideas why this is happening, does my processor not like OC and I need to scale it down? Other than that I love everything about the rom thanks in advance for any help.
Click to expand...
Click to collapse
That is a good guess. Test it out by scaling it down and monitoring what the behavior is. Mike's rom should be set at 1.152gHz out of the box. That is not high at all but every phone is different and if you have yours set higher your particular phone may not like it.

XPLiiCiiT said:
Does anybody have any idea why I can't set a permanent screen lock? It's like everytime I set a pattern lock or PIN lock, it works once then no longer requires a pattern or PIN to unlock my phone depending on which one I chose to use. Any help would be appreciated.
Sent from my Inspire 4G using XDA App
Click to expand...
Click to collapse
That is a strange one. Mine works with no problems on AR. Sorry I could not give you a better clue as to why this is happening. Possibly try flashing again to see if that solves it. Either that or do you have any lock switch type apps that may be causing some kind of problem?

Wolf_2 said:
That is a strange one. Mine works with no problems on AR. Sorry I could not give you a better clue as to why this is happening. Possibly try flashing again to see if that solves it. Either that or do you have any lock switch type apps that may be causing some kind of problem?
Click to expand...
Click to collapse
Hmm. I don't have any type of apps that could cause this and I've already tried flashing it again but the problem still persists. Oh well, no biggie. Thanks for the reply.
Sent from my Inspire 4G using XDA App

XPLiiCiiT said:
Hmm. I don't have any type of apps that could cause this and I've already tried flashing it again but the problem still persists. Oh well, no biggie. Thanks for the reply.
Sent from my Inspire 4G using XDA App
Click to expand...
Click to collapse
After you set the pattern or pin did you change the inactivity setting? I believe default is it will only lock after 5 minutes of inactivity. After you set the pattern/pin the second setting down is "Lock phone after" then gives you the selections immediately, 3 mins, 5 mins and so on. Make sure its set to immediately. That would be my best guess from the info you provided.

cbronson41 said:
After you set the pattern or pin did you change the inactivity setting? I believe default is it will only lock after 5 minutes of inactivity. After you set the pattern/pin the second setting down is "Lock phone after" then gives you the selections immediately, 3 mins, 5 mins and so on. Make sure its set to immediately. That would be my best guess from the info you provided.
Click to expand...
Click to collapse
Yeah, it's set to immediately but still does the same thing. Thanks for the help.
Sent from my Inspire 4G using XDA Premium App

I am currently using this rom and I think its great. The only problem I've had was downloading from the Android market. But it started to work all of a sudden a few days ago.
Thanks for the ROM. Great work.

Well, I just upgraded from 5.2.5 (which I installed this morning) to 5.2.6... very smooth upgrade.

Well, mostly smooth anyway. I have the sense 3.0 lockscreen installed and although it works in terms of pulling the ring up to unlock, there are no icons (and yes, I have configured the ones I want there) and no matter which lockscreen I choose under personalizations, I just get the same background I have on my home screen with no icons, no clock, no weather, no nothin'. I did so a SuperWipe when I installed 5.2.5 this morning, but the dev's notes say you don't have to SuperWipe if you are installing over another 5.2 release.
Incidentally, I saw the exact same misbehavior under 5.2.5 and was hoping it might get fixed.
Other than that it seems to run real well though. Is the 3.0 lockscreen working for others?

Installed the "Restore HTC Lock-Screen for Android Revolution HD 5.2.x " mod to revert to the non sense 3.0 lockscreen, and it works, but I notice that under "personalize -> lockscreen" it still shows the sense 3.0 ones, and lets you modify and select one, but it doesn't work.

Although I normally use an external bluetooth GPS, I just tested the internal one with 5.2.6 and it locked on quickly and gave about 16' accuracy.

I've been using this ROM for the past few days and I think its great.
However, I didn't flash a new radio (the one suggested on the thread). Is that alright? Will I see a huge difference flashing a new radio over the stock one?

does the new APN trick work with AR HD for the wifi tethering?

Touchscreen doesn't work for first few seconds

This was one of the similar threads found, but it didn't give me a solution. I messed around with the different CPU governor's but none of them solve my problem. When I unlock the phone, it doesn't respond well to my touch for a few seconds. I'm using CM10 and I've never had this problem before. It only came up recently when I replaced my lcd and digitizer because I was having touchscreen problems. Now the problems are mostly gone except at the lock screen. I've tried 3 different roms (one was a Sense 3.6 rom) and they all had this problem. Outside of the lock screen, it mostly worked well except inside the "phone app" in the sense rom. I called someone and they didn't hear it ringing, so it went to voicemail. I didn't want to record a message so I pressed end call like 30 times but it didn't work until i took out the battery. It happens in CM10 too, but its not as bad, usually ends the call after the 3rd or 4th time.
To troubleshoot the problem, I turned on "Show touches-show visual feedback for touches" under Developer options. I also made this video so you guys can see what it looks like.

Ir0nMa1deN said:
This was one of the similar threads found, but it didn't give me a solution. I messed around with the different CPU governor's but none of them solve my problem. When I unlock the phone, it doesn't respond well to my touch for a few seconds. I'm using CM10 and I've never had this problem before. It only came up recently when I replaced my lcd and digitizer because I was having touchscreen problems. Now the problems are mostly gone except at the lock screen. I've tried 3 different roms (one was a Sense 3.6 rom) and they all had this problem. Outside of the lock screen, it mostly worked well except inside the "phone app" in the sense rom. I called someone and they didn't hear it ringing, so it went to voicemail. I didn't want to record a message so I pressed end call like 30 times but it didn't work until i took out the battery. It happens in CM10 too, but its not as bad, usually ends the call after the 3rd or 4th time.
To troubleshoot the problem, I turned on "Show touches-show visual feedback for touches" under Developer options. I also made this video so you guys can see what it looks like.
Click to expand...
Click to collapse
Take a look at this thread, maybe it helps. I would say update your firmware to 3.33, and try cleaning and pulling out the gray pin on the back of the phone. Hope it helps

Did you replace the digitizer yourself? If yes, I'd go back and make sure nothing is wrong. Make sure everything is properly put back together. Hope this helps. best wishes.
Sent from my HTC Sensation using xda premium

realsis said:
Did you replace the digitizer yourself? If yes, I'd go back and make sure nothing is wrong. Make sure everything is properly put back together. Hope this helps. best wishes.
Sent from my HTC Sensation using xda premium
Click to expand...
Click to collapse
I did replace it myself and I think that's probably the problem but my dad is refusing to help me take it apart again. We're going to go to a cell phone repair store to see if they can give us some advice, then he'll probably agree to open it up again and see what's going on.

Ir0nMa1deN said:
I did replace it myself and I think that's probably the problem but my dad is refusing to help me take it apart again. We're going to go to a cell phone repair store to see if they can give us some advice, then he'll probably agree to open it up again and see what's going on.
Click to expand...
Click to collapse
It looks like you've opened 2 treads for the same problem, so here's what I answered you earlier - http://forum.xda-developers.com/showpost.php?p=34955821&postcount=3

Ah yes, I made some new discoveries since then and I forgot to check on that thread so I ended up making a new one. The digitizer/lcd I bought is supposedly new, and it's the one that says HTC in the middle (no T-Mobile logo on the side) I'm updating Cyanogen Mod to the newest version and flashing new firmware, so if that doesn't fix it then that'll rule out software issues. After that, I'll re-install the lcd/digitizer and see if I can get it to work.
Also, you said "when you change displays it's never the same as the original" I've been looking through hundreds of forums and many people have successfully replaced their screen only for the problem to come back again a few weeks later. I'm thinking it has something to do with static buildup caused by third-party batteries or chargers, as seen in this thread that i forgot to mention. I've changed my charger so all that remains is taking apart the screen again.

Thanks to dennis8, my screen is now fixed. He linked me to this thread and it worked right away after that. Finally my freaking phone works :laugh::laugh::laugh::laugh::laugh::laugh::laugh:

Ir0nMa1deN said:
Thanks to dennis8, my screen is now fixed. He linked me to this thread and it worked right away after that. Finally my freaking phone works :laugh::laugh::laugh::laugh::laugh::laugh::laugh:
Click to expand...
Click to collapse
glad for you man:good:

[Q] New Google Maps flickers on CM10.1

Some of you may have noticed that the new maps app flickers on MT4GS running CM10.1. I reflashed gapps with the old maps, turned off auto-updates and it still updated itself. It is just useless.
Does anyone have a solution? I doubt google cares.

emi.bu said:
Some of you may have noticed that the new maps app flickers on MT4GS running CM10.1. I reflashed gapps with the old maps, turned off auto-updates and it still updated itself. It is just useless.
Does anyone have a solution? I doubt google cares.
Click to expand...
Click to collapse
Saw you mention this in one of the dev threads as well. I'm running SilverL's Unofficial CM 10.1 and haven't personally noticed this issue, while I saw someone else back you up with similar problems.
Maybe you pulled a map update I haven't seen yet? I'm showing version 6.14.4(#6140400) Web
Are you higher? Do you have a lot of layers on maybe?

PsychoPhreak said:
Saw you mention this in one of the dev threads as well. I'm running SilverL's Unofficial CM 10.1 and haven't personally noticed this issue, while I saw someone else back you up with similar problems.
Maybe you pulled a map update I haven't seen yet? I'm showing version 6.14.4(#6140400) Web
Are you higher? Do you have a lot of layers on maybe?
Click to expand...
Click to collapse
Yes, version 7 is out. auto-updated earlier week on my phone. dev threads? i don't recall, posting anything, I don't think I have permission to post there.
Anyway, I figured it out. I reflashed gapps, but it doesn't contain the maps app, and that's why it was ineffective. I uninstalled version 7, and pulled the version 6 apk from a friend's phone and installed it.
I also turned off auto-update in play.

emi.bu said:
Yes, version 7 is out. auto-updated earlier week on my phone. dev threads? i don't recall, posting anything, I don't think I have permission to post there.
Anyway, I figured it out. I reflashed gapps, but it doesn't contain the maps app, and that's why it was ineffective. I uninstalled version 7, and pulled the version 6 apk from a friend's phone and installed it.
I also turned off auto-update in play.
Click to expand...
Click to collapse
Sorry, saw someone mention it, thought it was you! Glad to hear it was sorted, I'll be sure to avoid a map update if I see one pop, but I haven't yet. Maybe it was causing issues outside of custom roms and google stopped pushing it until they got it sorted.

interesting, i was also having this issue.i was on the jellykang rom 1.8 and changed to silverL's 10.1 unofficial cm and im seeing a version 7.0.1 and it look like its working fine. ill report back if i see anything messing up again. but looking at android polices coverage of this update release reported that there were several versions getting pushed all over the place so maybe some work better than others..

Tampoon said:
interesting, i was also having this issue.i was on the jellykang rom 1.8 and changed to silverL's 10.1 unofficial cm and im seeing a version 7.0.1 and it look like its working fine. ill report back if i see anything messing up again. but looking at android polices coverage of this update release reported that there were several versions getting pushed all over the place so maybe some work better than others..
Click to expand...
Click to collapse
Interesting. I finally popped for the map update yesterday, and after reading this I figured I'll give it a shot. I like everyone else definitely had issues with the map, the jitteryness, the menu icon on bottom left slightly off screen. I uninstalled and reverted to 6.14.4 from my backup and it's just fine again. Hope this does get fixed, the new map looks nice if it was working. Wondering if you really are issue free or just didn't notice anything real quick.
It did seem like as I was playing with location options (use network for location, gps radio on or off, let google always allow access, having a gps lock or not) sometimes it seemed like it would smooth out for a second or two, then get all glitchy again. Wonder if any official JB handsets are getting the issue, I think I know what I'll google next.

PsychoPhreak said:
Interesting. I finally popped for the map update yesterday, and after reading this I figured I'll give it a shot. I like everyone else definitely had issues with the map, the jitteryness, the menu icon on bottom left slightly off screen. I uninstalled and reverted to 6.14.4 from my backup and it's just fine again. Hope this does get fixed, the new map looks nice if it was working. Wondering if you really are issue free or just didn't notice anything real quick.
It did seem like as I was playing with location options (use network for location, gps radio on or off, let google always allow access, having a gps lock or not) sometimes it seemed like it would smooth out for a second or two, then get all glitchy again. Wonder if any official JB handsets are getting the issue, I think I know what I'll google next.
Click to expand...
Click to collapse
yea you were right, i just did a glance look at it and didint really dive into it that far. i checked it out again and it is still all messed up so nevermind ..
are there any custom roms that dont have the issue i wonder. maybe this can help narrow down the root cause. unless its just an inherent problem with the app as it stands today. it almost reminds me of this issues i was having with ingress when i was on stock.

Tampoon said:
yea you were right, i just did a glance look at it and didint really dive into it that far. i checked it out again and it is still all messed up so nevermind ..
are there any custom roms that dont have the issue i wonder. maybe this can help narrow down the root cause. unless its just an inherent problem with the app as it stands today. it almost reminds me of this issues i was having with ingress when i was on stock.
Click to expand...
Click to collapse
Unfortunately it seems to me to be an issue with all of the 10.1's at least, and from my googling before, it seems likely specific to our device, just not sure why
Anywho, I'm pretty OK with maps 6, it works, and still has separate navi app, and is what anyone with earlier than android 4.0 is stuck with anyway.
UPDATE: So I tried the 7/22 update that I got hit with, and it's weird. Initially it seemed OK, aside from the menu button still being half off screen. After fooling around for a bit with menus and settings, it got all flickery again. It seems like it heavily had to do with overlays/prompt dialogues showing up. The box would kind of disappear aside from the outline, but still respond. After fooling around quite a bit and disabling boxes from asking again, eventually everything seems to have evened out. Now I haven't actually done any kind of navigation or heavy use, but I've been using v 7.0.2 now on and off for a few days, and the stutter hasn't come back. Wish I had a more definitive way of what I did to get rid of it, or if it eventually just smoothes out on it's own, but for now it seems like I'm good with the new maps on a CM10.1 rom.

Bump for update, anyone else experiences with new maps?

PsychoPhreak said:
Bump for update, anyone else experiences with new maps?
Click to expand...
Click to collapse
Yes, I'm having the exact same issues as you. Screen flickers and overlay menus keep blanking out so you can't read them. I have an HTC Inspire 4G running CM 10.1. Came across this thread searching for "Maps 7 screen flicker". I had to revert back to Maps 6 as 7 was unusable!

greiland said:
Yes, I'm having the exact same issues as you. Screen flickers and overlay menus keep blanking out so you can't read them. I have an HTC Inspire 4G running CM 10.1. Came across this thread searching for "Maps 7 screen flicker". I had to revert back to Maps 6 as 7 was unusable!
Click to expand...
Click to collapse
I am having same issue with HTC Evo 4g 3d buil 7-17 of CM Flicker maddness . . . it seems to be the CM build or something within CM Rom. Other phones or devices do not have the issue . . <---- my story

j1232 said:
I am having same issue with HTC Evo 4g 3d buil 7-17 of CM Flicker maddness . . . it seems to be the CM build or something within CM Rom. Other phones or devices do not have the issue . . <---- my story
Click to expand...
Click to collapse
Im running PACman ROM v22.4.0, same issue as you guys with the new maps, and navigation is a stutterfest.

I'm on jellykang 1.8 and that's definitely happening to me. especially in the navigation app

Since others are now finding this thread outside of just us DS users, I figure I'll share this idea from a dev thread:
Originally Posted by pyro9219
"Have you tried Settings > Developer Options > Disable HW Overlays?
I had to do that for several games that were causing screen tearing / artifacts."
I hadn't, but that's a wonderful suggestion, wonder if anyone else has?
Edit: So after learning how to re-enable dev options, I just tried this, and it definitely seems to WAY help. Is there any downside to leaving this checked all the time?
So something for others to try/chime in on?

Guys, can you try disabling android debugging AND USB debugging in developer options?
I saw it on a sensation ROM forum and it seems to be working for me.

anitgandhi said:
Guys, can you try disabling android debugging AND USB debugging in developer options?
I saw it on a sensation ROM forum and it seems to be working for me.
Click to expand...
Click to collapse
Hrm, I'll try it. Just loaded maps now, it was sketchy, disabled and seemed fine. Turned back on, and it was still fine, this one seems to be crazy inconsistent.

It wotk fine on my device
Gesendet von meinem GT-I9505 mit Tapatalk 2

possible workaround?
I found another workaround that seems to work for me:
Turn on the "Extended Desktop" (or "Expanded"? I'm on German here). And it's gone. Strangely the flickers don't return when I turn it off again.
Extended Desktop Option has to be activated in the settings, if it's not available in the power switch menu.

Counter perspective
I've just been working with the newest CM builds for the MT4GS, and I don't encounter any flickering. This is with a complete wipe prior to installing however.

same issue with HTC G2 on CM10.1
Hello,
I experienced the same issue on my HTC G2 with CM10.1. I had to revert to Maps v6...the v7 would sometime work fine, but most of the time I had some part of the screen flickering and the navigation feature was not usable at all (the animation would not work). I first thought it might be because of the overclocking. but I tried with stock frequency and the issue persisted.
My wife's Sony Ericsson Mk16a also has the same issue but on a custom stock rom..

[Q] Touch sensor randomly stops working

Hi!
For past two-three days I am experiencing this problem. Touch sensor just randomly stops working. Top side of the screen is very very difficult to control, sometimes even impossible. Sometimes it feels like sensor recognizes multiple touches at the same time which results random pages or menus opening and closing.
After short usage with screen up or after long downtime (like when I go to sleep) I'm not able to use sensor at all. I cannot shut down the alarm clock, I cannot answer the calls. I still can use the power button tho.
Now what is the most retarded is that nearly all that vanishes after phone reboot. The only thing that remains is that top side of the screen is still quite difficult to control. For example I cannot open that top slide-bar comfortably. I have to slowly move my finger over the screen in order to do so.
Phone specifications:
Custom ROM: Cyanogen 11-20140702-nightly
sdcard partition type: FAT32
bootloader version: 2.14
Security-OFF
CID: 11111
Custom recovery: TWRP 2.7.0.8
P.S.: tried to re-insall ROM did not help. Phone havent been damaged by any means recently.

Did u over or under clock..flash a mod to control kernel? That's what it sounds like

I'm assuming you're using the stock kernel? What you're describing is an ongoing issue with the CM kernel, flash a custom kernel (Torched or Bubba) and your problem should cease.
Sent from my Evita

Wow. I never knew there was an issue with stock kernel...what's causing that anyways?

Damn it..
I'm a newbie with all that kernel flashes. Any How-To for noobs? Guide or something? I have found Tourched Kernel for KK thread (I suppose it stands for Kit-Kat?), but it's quite puzzling for me with all that voltages.
P.S.: What caused such random issue all of the sudden? Have been using CM for quite a bit of time already. Got that issue just 2-3 days ago

Look under Tims sig

marknoll said:
Wow. I never knew there was an issue with stock kernel...what's causing that anyways?
Click to expand...
Click to collapse
I have no idea what's causing it, I do know that using a custom kernel always fixes it for me though.
SoulSurvivors said:
Damn it..
I'm a newbie with all that kernel flashes. Any How-To for noobs? Guide or something? I have found Tourched Kernel for KK thread (I suppose it stands for Kit-Kat?), but it's quite puzzling for me with all that voltages.
P.S.: What caused such random issue all of the sudden? Have been using CM for quite a bit of time already. Got that issue just 2-3 days ago
Click to expand...
Click to collapse
Flashing a kernel is similar to flashing a ROM, if you want instructions just check the How-To Guide For Beginners thread in my signature.
Sent from my Evita

timmaaa said:
I have no idea what's causing it, I do know that using a custom kernel always fixes it for me though.
Flashing a kernel is similar to flashing a ROM, if you want instructions just check the How-To Guide For Beginners thread in my signature.
Sent from my Evita
Click to expand...
Click to collapse
Meh, I have updated kernel to 3.4.86-Torched-KK.B4.3+
Problem is still here.
Still cant open top slide menu properly. It is just weird, it really seems like some sort of damage to very top side of the screen. But i didnt hit it or anything like that. Screen itself without any visible damage or even scratches, cuz im using screen protector. Gonna see if I can at least answer the calls properly without sensor goin full nuts.
update:
That's definitely a software issue. If i turn the phone around so screen would get rotated that "damaged" area works just fine. What the **** is going on? It started so randomly

You can try flashing a different ROM, or rolling back to the last build of CM that you remember being ok.
Sent from my Evita

SoulSurvivors said:
Meh, I have updated kernel to 3.4.86-Torched-KK.B4.3+
Problem is still here.
Still cant open top slide menu properly. It is just weird, it really seems like some sort of damage to very top side of the screen. But i didnt hit it or anything like that. Screen itself without any visible damage or even scratches, cuz im using screen protector. Gonna see if I can at least answer the calls properly without sensor goin full nuts.
update:
That's definitely a software issue. If i turn the phone around so screen would get rotated that "damaged" area works just fine. What the **** is going on? It started so randomly
Click to expand...
Click to collapse
Maybe reflashing the ROM and the kernel would be a good idea. I've had to do that too. Its annoying,but sometimes I had to do that. Good luck.

Nop..
I've done the factory reset. Installer fresh ROM, Gapps and kernel.
Same ****. I Guess That is indeed hardware damage to sensor.
/sadpanda

There's a way to diagnose it. Download an app called sensor on play store