[One (M8) Android Development] _moelle:
i dont know there is a special feature a kernel needs to run viper?! ...of course viper will work on this kernel just as on every other kernel. different sound mods installed in combination with viper could break it.

---------- Post added at 09:31 PM ---------- Previous post was at 09:07 PM ----------

so back to the maintopic ...NV12 black screen problem.

I did take a logcat ...dunno if its enaugh to post this lines, otherwise i will provide the full file.

D/CwMcuSensor( 948): CwMcuSensor::setEnable: debug.sensorhal.fill.block= 0

D/CwMcuSensor( 948): CwMcuSensor::setEnable: [v09-Add debug logs when open inputs], handle = 0, en = 0, what = 0

D/CwMcuSensor( 948): CwMcuSensor::setEnable: debug.sensorhal.fill.block= 0

D/CwMcuSensor( 948): CwMcuSensor::setEnable: [v09-Add debug logs when open inputs], handle = 3, en = 1, what = 3

D/CwMcuSensor( 948): CwMcuSensor::setInitialState

D/CwMcuSensor( 948): LightSensor::setInitialState: Reporting mPendingEvent.light = 45.000000

D/CwMcuSensor( 948): CwMcuSensor::setDelay: handle = 3, delay_ns = 1000000000

D/CwMcuSensor( 948): CwMcuSensor::readEvents: Init light

D/CwMcuSensor( 948): CwMcuSensor::readEvents: returning light, mEnabled = 0x40000008

D/CwMcuSensor( 948): CwMcuSensor::setDelay: handle = 3, delay_ns = 1000000000

I/PowerManagerService( 948): Waking up from sleep...

I/QCOM PowerHAL( 948): Got set_interactive hint

E/QCOM PowerHAL( 948): Invalid hint ID.

D/SurfaceFlinger( 267): Screen acquired, type=0 flinger=0xb89484e0

D/qdhwcomposer( 267): hwc_blank: Unblanking display: 0

D/EasyAccessService( 1148): > onScreenOn()

D/EasyAccessService( 1148): setTmpTargerLintener(MotionHidi)

D/CwMcuSensor( 948): CwMcuSensor::setEnable: debug.sensorhal.fill.block= 0

D/CwMcuSensor( 948): CwMcuSensor::setEnable: [v09-Add debug logs when open inputs], handle = 25, en = 0, what = 30

D/EasyAccessService( 1148): > onScreenOnDebugBuffer

D/EasyAccessService( 1148): < onScreenOnDebugBuffer

D/EasyAccessService( 1148): unregisterListener(hTC Gesture Motion HIDI):Done

D/EasyAccessService( 1148): < onScreenOn()

I/WindowManager( 948): Lock screen displayed!

D/DisplayPowerController( 948): Unblocked screen on after 62938 ms

W/GAV4 ( 2442): Thread[GAThread,5,main]: Service unavailable (code=1), will retry.

I/GAV4 ( 2442): Thread[GAThread,5,main]: No campaign data found.

W/GAV4 ( 2442): Thread[GAThread,5,main]: Unknown exception. Could not get the ad Id.

I/qdhwcomposer( 267): handle_blank_event: dpy:0 panel power state: 1

E/qdexternal( 267): writeHPDOption: file write failed '/sys/devices/virtual/graphics/fb1/hpd'

D/qdhwcomposer( 267): hwc_blank: Done unblanking display: 0

D/SurfaceControl( 948): Excessive delay in unblankDisplay() while turning screen on: 240ms

D/audio_hw_primary( 270): adev_set_parameters: enter: screen_state=on

W/InputMethodManagerService( 948): Got RemoteException sending setActive(false) notification to pid 1315 uid 10096

D/AlertService( 1990): Beginning updateAlertNotification

D/AlertService( 1990): No fired or scheduled alerts

D/AlertService( 1990): Scheduling next alarm with AlarmScheduler. sEventReminderReceived: null

D/AlarmScheduler( 1990): Query result count for events starting within 1 week: 1

I/Choreographer( 1148): Skipped 31 frames! The application may be doing too much work on its main thread.

I/GAV2 ( 2763): Thread[GAThread,5,main]: No campaign data found.

It looks like the device is booting up but doesn t "enables" the screen cause of the "unknown something" that happens on boot^^

after a few moments, staying on the blank screen, you could start for example the screen record (by using hardware buttons) and just hear the start sound. (but screen ofcourse keeps blank)

noticed it by accidently not triggering the right hardwarekey-combination, to reboot ..... hope it helps to find out whats wrong.