Database Info

Two weird problems

When I started using my Charge today, I discovered two odd problems with it.
Firstly, when I press the lock button (from a locked state), the screen starts dim and then brightens. When the screen is dim, it is completely unresponsive until it brightens about a second later. This isn't particularly horrible, but it is kind of annoying.
Second, I can't rotate my phone anymore. I've checked the settings and the notification tray and they both have auto rotate enabled. It isn't tied to any app as it happens accross the phone.
Both of these issues started today and I didn't make any big changes to my phone. I'm running GummyCharged 1.9.1 (flashed the full Odin) and I'm planning on just flashing it again if no one has any ideas to fix this. Thanks for any help!
Sent from my SCH-I510 using XDA App

The dim would appear to be normal as my phone does it as well although I wouldn't say it takes a full second before its responsive.
As for auto rotate, try deleting ms3c_yamaha.cfg from /data/system and reboot.
Sent from my SCH-I510 using Tapatalk

I added .bak to the end of the file, rebooted, and both problems are fixed. The screen is still dim and then brightens upon hitting the lock button, but it is now immediately responsive.
Thanks for the help!
Sent from my SCH-I510 using XDA App

Good to hear that it worked for you.
Sent from my SCH-I510 using Tapatalk

Random screen timeout........anyone else experiencing this?

Unrooted with latest ota and the screen just times out at random times. No matter what screen timeout is set on. Any help is appreciated.
Sent from my DROID2 GLOBAL using XDA App

Sometimes I've got a case when screen doesn't time out at all. Including on latest 4.5.608 update. Reboot fixes it for me. Have you tried rebooting (with taking battery out before powering it on again to make sure it is a true cold boot)?

No I haven't, my case, makes it hard to do a battery pull, guess im just lazy. Will let you know the results. Thanks for the quick response
Sent from my DROID2 GLOBAL using XDA App

Seems to have sufficed for now. Any idea what the cause might be?
Sent from my DROID2 GLOBAL using XDA App

BrImStOnE UnLeAsHeD said:
Seems to have sufficed for now. Any idea what the cause might be?
Sent from my DROID2 GLOBAL using XDA App
Click to expand...
Click to collapse
It's likely a bug of some sort. Hardware and software are so complex, it is impossible to make it perfect. But problems like this one aren't "turning the cart over" especially if they occur rather seldom and there is (somewhat) acceptable "workaround".
Sent from my DROID2 GLOBAL using Tapatalk

Could be simpler?
My wife recently switched from Iphone 2G to a blazing droid 2 G, she was all happiness, but recently she started to complain the same thing your talking about (random screen timeout), so I tried his phone but the problem do not happened when I was using the phone, so after some intriguing days, I found something...
When she uses the phone, sometimes inadvertently she was blocking the sensors (in the upper right frame) that are triggered when you are in a call, causing immediately lock screen.
So, after being more cautious about not to block this part of the screen the problem didn't happen again.
I hope every one else suffers this simple problem instead of having a real hardware issue.
Saludos.

Just disable in-pocket detection.

Download Screebl from the Market. It can detect when your phone I actively being used and prevents screen timeouts until you put the phone down. Great app, I think you'll find it useful.

Gonna try the screebl app out, sounds pretty useful
Sent from my PC36100 using Tapatalk pro

Touch screen stops working

Hi all
I'm having this issue where randomly the touch screen stops registering my touch, and the only way to get it to work is to turn the screen on and off.
Hardware buttons work fine, and I have tries different ROMS.
Anyone know anything about this issue? Thanks
Sent from my Nexus S using Tapatalk 2

bump

im not sure how much of an issue this is, i used have that problem sometimes but not since i started using a task killer again. its possible its just a lag issue
Sent from my Nexus S 4G

bringonblink said:
Hi all
I'm having this issue where randomly the touch screen stops registering my touch, and the only way to get it to work is to turn the screen on and off.
Hardware buttons work fine, and I have tries different ROMS.
Anyone know anything about this issue? Thanks
Sent from my Nexus S using Tapatalk 2
Click to expand...
Click to collapse
As you said randomly, try use clean stock ROM for days to see if it is jammed by applications or not, I have that problem as well sometimes, due to some apps fully occupied CPU and make everything else non responsive...
Sent from my Nexus S using xda premium

the UI might be lagging as well if youre using the noop i/o scheduler.
Sent from my Nexus S 4G

Phone Locking Up

I'm hoping that this isn't a unique problem just for me but this is literally the first time I've had this problem. Depending on the use of my Note 5 will determine if I can even unlock my phone the next time I turn it on. I'll go about my usual use of any phone should be able to accomplish (browsing Instagram/Facebook/Chrome/Email/Pinterest/etc.). After a little while it become noticeable that the phone is starting to slow down considerably if I continue to use it. However, the one that really grinds my gears is I'll do my typical browsing and then lock my phone, put it back in my pocket. Something we all do, however, the next time I go to pull out my phone I can't even get the screen to come on for sometimes five minutes. I can hear it thinking with random sounds of the lock screen either responding to my fingers touching the screen or the un/lock sound but nothing happens. Sometimes, I can see the screen and all the notifications that I want to check on but nothing is happening. Sometimes, I'll double tap the home button to get to the camera shortcut programmed to it and sometimes the camera app comes up like it should but it is completely unresponsive.
So the steps I've tried to resolve the issue:
Restore to Stock ROM
Different ROMs
Even leaving the Stock ROM alone and just seeing if it still occurs
I'm just not sure what to try next. There's a chance the problem could be a memory error that's occurring physically but I'm not 100% sure.
Attached is my Note 5's current state of customization. Any help with this would be very very much appreciated.
Thank you

Giving a slight bump here. Does no one else have an idea of what c could be wrong?
Sent from my SM-N920T using XDA Free mobile app

CharlieBoy808 said:
Giving a slight bump here. Does no one else have an idea of what c could be wrong?
Sent from my SM-N920T using XDA Free mobile app
Click to expand...
Click to collapse
Have you removed or disabled any system files? Also have you tweaked the kernel in any way?
I will say that I've had issue with v11 of that kernel you are using. I bounce between v4.1 and Sky-high v4.5 depending on what I need my phone for that day.
Sent from my SM-N920T using Tapatalk

I will give those a try. Thank you!
Sent from my SM-N920T using XDA Free mobile app

Screen burn in

View attachment 4024381
Woke up to this just now and can't figure out why as one Facebook wasn't on and 2 s teen timeout is set at 1 min. Guess this phone is going back in. Never had a screen get ghosting on it before
Sent from my LG-H910 using Tapatalk

OK what's going on with this phone. Now the burn in on the screen is gone. Anyone have a clue what happened ?
Sent from my LG-H910 using Tapatalk

Dark Jedi said:
OK what's going on with this phone. Now the burn in on the screen is gone. Anyone have a clue what happened ?
Click to expand...
Click to collapse
Try a factory reset, there is no screen burn in on LCDs

i can confirm that this is true while it looks like burn in once you turn the screen off for a while it will disappear its, more of a ghost image. use amoled Burn in fixer form the play store or an all grey image and you'll be able to see it where the status bar is located.

This was really bad on some v10s but I haven't experienced it yet on my v20. It's not permanent like led burn in. It's a ghost image.
On my v10 it showed up when I used an app like my Word text game which kept the same image on the screen for a while. It was also worse/showed up faster the brighter I had the screen.
Glad I haven't seen it on the v20!

You also can't screen capture screen burn as that is hardware, this looks like a software bug. Tho not completely understanding your first post.
Sent from my LG-H990 using XDA-Developers Legacy app

i recently got this as well.. Sad that it has happened so quickly for me... Rebooting and shutting down didnt help at all. Nor do I thing factory reseting would either. It showed up before I was going to sleep so I locked it and went to bed. It went away the next morning. It freaked me out and made me think I was going to need to get a replacement but all is good.

Yeah I realized afer I finally woke up that you can't screen cap that lol.
It did it again last night at work. It was Facebook yet again. I played a few YouTube vids and made it go away.
Sent from my LG-H910 using Tapatalk

I haven't had the luck to experience that. But with IPS panels it is bound to disappear at some point. Now, you are only missing to find the way to generate the ghost image once again. IF it only happens with specific apps, or if it happens with everything in general.

So far it only been with Facebook in landscape mode
Sent from my LG-H910 using Tapatalk

Dark Jedi said:
So far it only been with Facebook in landscape mode
Sent from my LG-H910 using Tapatalk
Click to expand...
Click to collapse
have you tried with another version of facebook? try to find a beta version . or a previous version and see how it goes.

I just updated Facebook app so I'll see how it goes.
Sent from my LG-H910 using Tapatalk

Dark Jedi said:
I just updated Facebook app so I'll see how it goes.
Sent from my LG-H910 using Tapatalk
Click to expand...
Click to collapse
im on version 111.0.0.0.28 of facebook:good: