[Nexus 4 Original Android Development] sga999:
lock screen goes dark

I was not going to post anything else about this problem since no one else seemed to encounter it. But in a PM, obsanity asked me to post my findings, so here goes. I'll show the sequence of posts/PM's yesterday.

YESTERDAY'S POSTS....

sga999:

Gosh, I have no idea how this happened. I was on r82. I updated Franco's app and was looking at Gamma values, etc. Then I saw there was r83, so I flashed it through Franco's app. Now, after boot, the lock screen stays lit only for a few seconds, then goes dark...not completely black. If I hit power, it will go completely black, just as it normally would when when sleeping. I can hit power, and the lock screen will show for a fraction of a second, then go dark again.

I tried flashing an earlier kernel, but the result is the same.

Does this behavior seem familiar to anyone?

obsanity:

I think your previous gamma settings now make the screen way dark.

Go into a dark closet and see if you can tell where stuff is. Navigate to Franco's app and bump brightness.

Edit: I just lowered RBG values about half way and got gamma all the way to dark and sure enough... black screen LOL

Also, try putting your phone to a light source. I'm thinking the auto brightness might show more details so you can navigate.

me:

Once it goes dark, I can't see anything, closet or bright light or anywhere. When the lock screen comes on for the very brief moment that I hit power, I can see that it says Jan. 1. So something has messed up the date.

If the RGB values are the problem, does it make sense that I can see the lock screen briefly and then it goes dark? If so, any other ideas on how to get these RGB values changed? I flashed the stock kernel, and it's the same problem. Does that indicate it's something other than RGB values?

Thanks for your help.

PM from me to obsanity. (Since no one else was having this problem, I didn't want to clutter the thread).

I kept hitting power over and over, lockscreen showing ever so quickly, and then it managed to stay on. I have no idea why it will stay on once every few hundred tries!

So I was able to change the RGB values from 0 to 255. I had tried to use his app, and somehow the slider wasn't working, and I guess that's why it got left at 0. But it caused no issues until I used Franco's app to install r83 and let it reboot.

Thanks for your ideas about what caused this. I guess that was it because I haven't fixed anything else. One last question....are you saying it does make sense to you that the lockscreen will come up but then go dark? I don't know enough about when the RGB values are used. Somehow hitting power does allow the lockscreen to show, but then something kicks in to make it go dark. So the RGB values are being changed then?

Thanks again.

PM from obsanity to me:

First. I'm glad it worked and you were able to bump them up. Do me a favor and post your findings in the thread.

I think Franco's app actually works that way. It adjusts colors once the screen is on and they get reset once its off. I'm not sure but you can ask him.

END OF YESTERDAY'S POSTS....

TODAY...

So...Franco, here are my questions.

1. When are the RGB and gamma values set/reset by the kernel?

2. Does it make sense that setting RGB to 0/0/0 (accidentally) would cause the lock screen to display, then go dark within a fraction of a second?

3. After hitting power MANY times, why would the lock screen finally stay on so that I could proceed to change the RGB values in Franco's app?

4. Does it make sense that after flashing the stock kernel (or any "early" Franco kernel), this "dark screen problem" persisted?

EDIT: RIght as I was posting this, I now see stuff on the previous page about another person with the same issue. I guess I'd still be interested in answers to my questions.