search

showp1984 / bricked-flo

Nexus 7 2013
Other
3 stars 10 forks source link

Screen unresponsive #1

Open dark2099 opened 10 years ago

dark2099 commented 10 years ago

After enabling doubletap2wake and setting that option to boot, when I restarted the tablet to verify boot settings, screen would turn on with the power button, but was unresponsive to physical touches.

showp1984 commented 10 years ago

Is there a possibility that the doubletap2wake option was applied while the screen was offline? Asked differently: was the screen off at the end of that bootup? (screen timeout) Kernel log?

dark2099 commented 10 years ago

Oddly it isn't happening now, dirty flashed ROM to go back to stock, flashed bricked (latest master), booted, set options, rebooted, and all was good. Would undervolting possibly create this issue?

showp1984 commented 10 years ago

Could be, though unlikely. Then again, undervolting produces all sorts of unlikely issues. I guess you either let the timeout disable the screen upon bootup or closed the magnetic lid though. The current implementation of the touchscreen driver sleep prevention is not meant to be enabled with the screen off. This issue would also be reproduce-able.

dark2099 commented 10 years ago

Just redid my UV settings, left the magnetic lid closed while rebooting, I'll try closing it as it boots, if I am able to recreate the issue, I'm assuming you want a last_kmsg?

showp1984 commented 10 years ago

Yeah that's the issue I was already aware of. Preventing touchscreen sleep while screen is off triggers this behavior. Don't need a kmgs for that as I already have a fix for the hammerhead :)

dark2099 commented 10 years ago

Would leaving doubletap2wake off help prevent that from happening, or is it nothing related to that? Missed closing the lid at the end of boot, but happened again, while I had the lid flipped around to the back of the tablet. Also, I remember on the old N7, deadline was the default/preferred I/O scheduler, is it with this or should I leave it on cfq? Thanks!

showp1984 commented 10 years ago

If both, s2w and dt2w, are off then neither can be safely enabled when the screen is off. Is one of them active there will be no issue. When writing it I just didn't think about that people are going to change this while the screen is off. My bad.

to schedulers: Try it. I found cfq to perform the best across the board.

dark2099 commented 10 years ago

To better understand you saying people changing this while the screen is off, what I will do is go into k-control, enable the option, then either exit the app via the back button or home button then let the screen time out or manually turn it off via the power button. How is the setting changed when then screen is off?

showp1984 commented 10 years ago

On boot, as you mentioned. Android signals that the boot completed quite late, which causes kcontrol to apply settings late too. The screen may be off then.

jaredmorgs commented 10 years ago

This has happened twice now for me with DT2W enabled in as many days. It happens on boot using k-control, and requires a reboot to correct the issue. When I reboot, the live wallpaper I selected resets to the default wallpaper (not sure if this is relevant).

Just adding weight to the issue.

Apart from this issue, the kernel is awesome. Thanks for providing us with this kernel.