Can't remember if the image you're working on uses powerd or repowerd. You can also try :
adb shell powerd-cli display on bright -Cemil On Fri, Mar 24, 2017 at 11:28 PM, Cemil Azizoglu <cemil.azizo...@canonical.com> wrote: > Have you read through the android_new_device_bringup document? > > http://bazaar.launchpad.net/~mir-team/mir/development-branch/view/head:/doc/android_new_device_bringup.md > > IIRC, you can force the display to stay on by running > > adb shell sudo repowerd-cli display on > > You can also get help at #ubuntu-mir channel on freenode. > > Best of luck > -Cemil > > > On Fri, Mar 24, 2017 at 4:35 PM, Florian Leeber <fl...@bin.org.in> wrote: >> >> Hello All, >> >> I am faithfully trying to port the current Ubuntu Touch vivid image to >> the Samsung Galaxy S3 (i9300). Basically I have a good progress, the >> phone is booting, kernel is fine, lxc container started etc... >> >> But, again as already seen on a previous porting with an even older >> device, I am stuck with graphics: >> >> - regardless of the test I try (mir tests) I always get >> libEGLvalidate_display:262 3008 (EGL_BAD_DISPLAY) >> - screen stays dark (actually who is turning on and off the screen, and >> where is the timer for the default screen blanking, can I disable that) >> >> Can you help me to find out why this is happening? Basic test_egl and >> test_glesv2 seem to be fine (though I cant tell for sure w/o a screen) >> >> BR Florian >> >> >> -- >> Mir-devel mailing list >> Mir-devel@lists.ubuntu.com >> Modify settings or unsubscribe at: >> https://lists.ubuntu.com/mailman/listinfo/mir-devel > > -- Mir-devel mailing list Mir-devel@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/mir-devel
