Navigation

    UBports Robot Logo

    UBports Forum

    • Register
    • Login
    • Search
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Groups
    • Search

    [HowTo][Convergence]Use a simulated miracast sink for testing convergence

    Support
    flo hacks
    8
    26
    4387
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • D
      doniks last edited by doniks

      what can I expect to happen if it works? I don't have a UT device around just now, so I tried with Android. I get:

      $ sudo miracle-sinkctl 
      [ADD] Link: 3
      [miraclectl] # run 3
      now running on link 3
      [ADD] Peer: b2:72:bf:3b:28:c8@3
      [PROV] Peer: b2:72:bf:3b:28:c8@3 Type: pbc PIN: 
      [GO NEG] Peer: b2:72:bf:3b:28:c8@3 Type: pbc PIN: 
      [CONNECT] Peer: b2:72:bf:3b:28:c8@3
      now running on peer b2:72:bf:3b:28:c8@3
      NOTICE: SINK connected
      SINK set resolution 1920x1080
      

      but other than the console output I never see anything. I was expecting to see the screen of my Android.

      Edit: Ah found something:

      On Laptop:

      • git clone https://github.com/albfan/miraclecast
      • follow the "How - Linux" steps in @Flohack's post above

      On Android:

      • install "Miracast Shorcut" (from fdroid)
      • run it
      • see your laptop show up

      On Laptop:

      • see "SINK connected"
      • open new terminal
      • cd miraclecast/res
      • ./gstplayer
      • see a live stream playing from your Android

      Of course it misses some of the miracle of convergence .... it's just a video, you can't interact with it

      Flohack 1 Reply Last reply Reply Quote 0
      • Flohack
        Flohack @doniks last edited by

        @doniks Cool at least partially this is working. Now we need a proof with UT 😉

        BR

        1 Reply Last reply Reply Quote 0
        • jonius
          jonius last edited by

          I have a FP2 with UT 16.04. But there are no external displays shown in that menu. But how would the phone find the notebook anyways? The stopping the network manager that wifi connections gets lost.

          jonius Flohack 2 Replies Last reply Reply Quote 0
          • jonius
            jonius @jonius last edited by

            @jonius said in [HowTo][Convergence]Use a simulated miracast sink for testing convergence:

            I have a FP2 with UT 16.04. But there are no external displays shown in that menu. But how would the phone find the notebook anyways? When stopping the network manager the wifi connections gets lost.

            In the miraclectl shell I got the print "[ADD] Peer: <some Mac address>@2" and later a "[REMOVE] ..." message.

            1 Reply Last reply Reply Quote 0
            • Flohack
              Flohack @jonius last edited by

              @jonius Hello,

              yes the loss of network connections is intentional. Miracast needs P2P mode on the WiFi card which means its not allowed to be associated with any other network. This is why you need to check first if your card even supports that.

              I did not try this myself as I do not own a PC which has such a card. Therefore I am waiting for people who are able to follow the instructions. Seems you were not able, meh. Sounded too good to be true 😉

              BR

              1 Reply Last reply Reply Quote 0
              • jonius
                jonius last edited by

                I have checked that and it shows the three modes you named above. But how is my FP2 supposed to find the computer, if it is not connected to my local network anymore? Do I need to search for some kind of miraclecast wifi opened by the netbook?

                Flohack 1 Reply Last reply Reply Quote 0
                • Flohack
                  Flohack @jonius last edited by

                  @jonius Hello,

                  P2P mode should be configured so that FP2 finds any display device announcing itself. Its a special form of AdHoc mode. So nothing needs to be done, in theory. Seems in practice its not so easy...

                  BR

                  1 Reply Last reply Reply Quote 0
                  • D
                    doniks last edited by

                    @Flohack Ok, now I have UT running on my Nexus 7 and my laptop has this required mode, but I can't figure it out still.

                    Firstly, on UT, the "External display" is greyed out and I can't toggle the switch. The switch is on the left.

                    However, in the terminal I can enter aethercastctl [1] and do enable, which actually changes the switch in the settings to on-the-right. Also in aethercastctl I get a confirmation that it is Enabled: true, I can also scan which gives me a Scanning: true. After a while this times out and noting else happens.

                    But, in general, I'm not getting how this is supposed to go together. aethercast seems to be happily scanning while connected to regular wifi. I can repeat my test with the Android, trying to cast UT to Android. In that case aethercast actually finds the android when after a scan I can also progress a few steps with connect - the android phone bleeps and shows some kind of connection dialog, aethercast tells me it is now in State: connected. Well, I don't actually see the UT display on the android phone, so something is failing after all. But what this tells me is that aethercast (UT) might actually want to connect (and stream?) via regular wifi and not via some special "direct" mode. Is it the difference between a) what we transport, ie, the display, versus b) how we transport it, ie, either wlan or wifi direct? And maybe miraclecast expects a) display data over b) wifi direct, and while UT happily sends a) display data, it sends it over b) regular wifi ....

                    [1] https://wiki.ubuntu.com/Touch/DisplayCasting

                    1 Reply Last reply Reply Quote 1
                    • Flohack
                      Flohack last edited by

                      Thanks for your findings. It seems we need much more here, too sad it does not work out of box.

                      BR

                      D 1 Reply Last reply Reply Quote 0
                      • D
                        doniks @Flohack last edited by

                        modules:composer.user_said_in, @flohack, &#91;HowTo&#93;&#91;Convergence&#93;Use a simulated miracast sink for testing convergence

                        Thanks for your findings. It seems we need much more here, too sad it does not work out of box.

                        BR

                        Maybe it's not "much more", but just a way to convince miraclecast into talking on regular wifi

                        Flohack 1 Reply Last reply Reply Quote 0
                        • Flohack
                          Flohack @doniks last edited by

                          @doniks Miracast is per definition not possible over "normal" WiFi, thats why most people had only success with the Microsoft Miracast stick. That seems to be still the most compatible one...

                          BR

                          D 1 Reply Last reply Reply Quote 0
                          • L
                            Luksus last edited by

                            It seems that the wireless display mode is broken on 16.04 for FP2.
                            I reflashed it with 15.04 and there my "display" shows up.
                            By the way, you can add the LG 1500pf/g/Largo projectors to the confirmed working devices :-).

                            D 1 Reply Last reply Reply Quote 1
                            • D
                              doniks @Luksus last edited by

                              modules:composer.user_said_in, @luksus, &#91;HowTo&#93;&#91;Convergence&#93;Use a simulated miracast sink for testing convergence

                              It seems that the wireless display mode is broken on 16.04 for FP2.
                              I reflashed it with 15.04 and there my "display" shows up.

                              Sounds like it justifies a bug report

                              By the way, you can add the LG 1500pf/g/Largo projectors to the confirmed working devices :-).

                              Sounds like worth documenting, maybe in a new page about wireless displays here: https://docs.ubports.com/en/latest/userguide/dailyuse/index.html

                              hint, hint 😉

                              1 Reply Last reply Reply Quote 0
                              • ierihon
                                ierihon @Flohack last edited by

                                Nexus 5 with SlimPort: on 16.04 RC icons are wery big 😞

                                I back to 15.04 to try Convergence mode.

                                1 Reply Last reply Reply Quote 0
                                • ierihon
                                  ierihon last edited by

                                  How to enable desktop mode like on 15.04?

                                  M 1 Reply Last reply Reply Quote 0
                                  • M
                                    malditobastardo @ierihon last edited by

                                    @ierihon Use the UT Tweak Tool. Or plug a slimport cable to the tv.

                                    https://open-store.io/app/ut-tweak-tool.sverzegnassi

                                    ierihon 1 Reply Last reply Reply Quote 0
                                    • ierihon
                                      ierihon @malditobastardo last edited by ierihon

                                      @malditobastardo said in [HowTo][Convergence]Use a simulated miracast sink for testing convergence:

                                      @ierihon Use the UT Tweak Tool. Or plug a slimport cable to the tv.

                                      https://open-store.io/app/ut-tweak-tool.sverzegnassi

                                      Thanks. I know these app, but is not suitable: DPI not changed 😞

                                      On 15.04 when i connect SlimPort on external screen icons looks good.

                                      On 16.04 RC - icons are big, like on phone:

                                      (0_1533362910939_screenshot20180804_074924163.png

                                      P.S. With these app i can change icon size, but it also not suitable. On 15.04 stable convergence mode work better.

                                      M 1 Reply Last reply Reply Quote 0
                                      • M
                                        malditobastardo @ierihon last edited by

                                        @ierihon In Desktop mode?

                                        ierihon 1 Reply Last reply Reply Quote 0
                                        • ierihon
                                          ierihon @malditobastardo last edited by ierihon

                                          @malditobastardo said in [HowTo][Convergence]Use a simulated miracast sink for testing convergence:

                                          @ierihon In Desktop mode?

                                          Yes, in Desktop mode (Screenshot of 15.04 Stable).

                                          0_1531117659490_IMG_20180706_190917_542.jpg

                                          1 Reply Last reply Reply Quote 1
                                          • K
                                            killerbee last edited by killerbee

                                            Just out of curiosity I ordered a HAMA (German company) Miracast stick to play around with my M10FHD

                                            Good thing: Display is detected
                                            Bad Thing: On connecting it fails after some time its going through connecting, preparing for display, ready to display and then fails / disconnects on the tablet...

                                            Using dev114

                                            Any directions to extend testing or provide more logs/traces?

                                            FWIW:
                                            iw phy does NOT report P2P-device for my M10
                                            HAMA device is HAMA83210-ADFC46

                                            br
                                            Thomas

                                            1 Reply Last reply Reply Quote 0
                                            • First post
                                              Last post