Sure? Could you please try to watch any video of this page http://www.ndr.de/mediathek/. Let it just run for at least 5 minutes and do something else, then take a look if the screen is black.Factory reset also seems to fix black screen problem.
I Just watched a video on that page for about ten minutes and paused and played several times without any problems. I used Firefox.Sure? Could you please try to watch any video of this page http://www.ndr.de/mediathek/. Let it just run for at least 5 minutes and do something else, then take a look if the screen is black.
what is this ricks kernel ?I also can confirm that there are no issues at all with ricks kernel v15.
No black screens/lags or whatsoever.
Yes, sorry, thats itwhat is this ricks kernel ?
http://forum.xda-developers.com/lg-g-pad-83/development/kernel-redkernel-t2856297
Probably this one by Rick Roll ?
Haven't used any custom kernel on this device so far
Thanks
Thanks for testing. I think you are right about disabling hw overlays not solving the black screen problem. Although, since upgrading to the latest nightly build,I have not had a black screen so far (it was happening twice a day before that even after a factory reset).Sorry, I tried this and just had a black screen whilst using type mail.
The other camera module isn't working yet for aosp.Can anybody say if the back camera works or not? The "ov5693" one.
The only problem is that my sdcard unmounts with latest red kernel.For last week i tested new versions nightly with RedKernel # 15. I had no problems at this time with black screen issue. Yesterday i did a clean install version 20150521. Within two hours i had three times the black screen issue. I was using at that time Pocket. Today installed RedKernel again. So far, no error occurred. Sorry for my bad english...![]()
Does pure aosp have this problem?Just tried the latest nightly with a clean install for three hours. Had three SODs. As much as I hate to say but this ROM and all his derivates are pretty useless in their current condition.
Isn't there an official maintainer for our device? Isn't it possible to log anything which could help? I would like to help to get this working.
Sadly this problem exists on my mako too. But the issue occurs a lot less often.
Going back to the latest cm12 nightly for now. This works flawless and the differences between 5.0.2 and 5.1.1 are zero for my uses.