Subject: Issue with mir on Ubuntu Touch and Samsung Galax S3 (i9300)

From: Florian Leeber <[email-masked]>
Date: Fri, 24 Mar 2017 22:35:44 +0100

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

---

From: Cemil Azizoglu <[email-masked]>
Date: Fri, 24 Mar 2017 23:28:02 -0500

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 <[email-masked]> wrote:

> --
> Mir-devel mailing list
> [email-masked]
> Modify settings or unsubscribe at: https://lists.ubuntu.com/
> mailman/listinfo/mir-devel
>

---

From: Cemil Azizoglu <[email-masked]>
Date: Fri, 24 Mar 2017 23:32:09 -0500

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
<[email-masked]> wrote:
>> Modify settings or unsubscribe at:
>> https://lists.ubuntu.com/mailman/listinfo/mir-devel
>
>

---

From: [email-masked]
Date: Sat, 25 Mar 2017 09:18:44 +0000

Hello,

yes I read the web page. Thanks for the tip with the display, now  
sometimes I can see some kind of result. Basically most of the tests  
are failing:

- mir_demo_standalone_render_to_fb: Shows the green background, with  
the bitmap, but no animation ongoing
- mir_demo_standalone_render_overlays: Black screen. If I remember  
right, maybe there was a mouse cursor visible one time?

I think we do not need to continue from here. Something is heavily  
bugged. Additional info:

- libhybris tests test_egl and test_glesv2 are both OK. test_glesv2  
shows animation correctly...

BR Florian

---

From: Daniel van Vugt <[email-masked]>
Date: Mon, 27 Mar 2017 09:38:15 +0800

I know device screens turn black/off during testing, and it can be a 
problem. I use a simple workaround for that when trying new Mir binaries:

$ sudo stop repowerd
$ mirbacklight    # (or mirbacklight 99)

---

From: [email-masked]
Date: Mon, 27 Mar 2017 08:57:18 +0000

Good Morning,

thanks for the tips. So far I used repowerd-cli display to keep it on,  
and that seems to work also.

For the second part I played a bit, but not much success: Is there a  
way to debug why mir tests are mostly stuck (have to kill them with  
ps), and in logcat I find the EGL_BAD_DISPLAY error from my first mail.

Are there basic conformity tests that dont start a server, where I can  
play with the parameters? So far I tried to follow the page on  
https://unity.ubuntu.com/mir/0.25/android_new_device_bringup.html.  
Results are:

mir_android_diagnostics  
--gtest_filter="AndroidMirDiagnostics.can_allocate_sw_buffer" => OK
mir_android_diagnostics  
--gtest_filter="AndroidMirDiagnostics.can_allocate_hw_buffer" => OK
mir_android_diagnostics  
--gtest_filter="AndroidMirDiagnostics.client_can_draw_with_cpu" =>  
Failed
mir_android_diagnostics  
--gtest_filter="AndroidMirDiagnostics.client_can_draw_with_gpu" =>  
Failed
mir_android_diagnostics  
--gtest_filter="AndroidMirDiagnostics.display_can_post" => Stuck  
(never finishes)
mir_android_diagnostics  
--gtest_filter="AndroidMirDiagnostics.display_can_post_overlay" =>  
Stuck (never finishes)

libhybris tests:

test_egl: OK
test_glesv2: OK
test_hwcomposer: Segmentation fault (core dumped)

Is there maybe some issue with libhybris? I am also currently on Mir  
0.24 since that is shipped with the vivid image on Ubuntu Touch.

BR Florian