Android emulator does not emit a signal












0















I'm currently on a test project and I'm using the KVM Android Emulator.



BEHAVIOUR: when I run the code, the app gets correctly opened in the phone emulator but then it no longer responds.



PREAMBLE: I checked if all Qt connects are correctly performed by declaring them as bool, and then I had the value printed



const bool connected = connect(myObject, SIGNAL(mySignal()), myClass, SLOT(mySlot());
qDebug("connection is %i", connected);


In all cases the connects were OK.



HINT: by using the breakpoints I noticed the debugger never entered one particular slot. This slot should be called every time the signal readingChanged() is emitted by an object of type QGyroscope(), which belongs to the Android emulator.



HYPOTHESIS: it is likely that the Android emulator does not emit one or more signals related to the Gyroscope. If you simply want to have the values measured by the Android emulator printed on the emulator itself, you will find out you can. However, the signals associated with these values are never emitted.



QUESTIONS:



1) How can I check if a signal with a void argument is actually emitted?



2) Is there a fix for a signal not emitted by the Android emulator?



Thanks in advance. Any hint is welcome










share|improve this question



























    0















    I'm currently on a test project and I'm using the KVM Android Emulator.



    BEHAVIOUR: when I run the code, the app gets correctly opened in the phone emulator but then it no longer responds.



    PREAMBLE: I checked if all Qt connects are correctly performed by declaring them as bool, and then I had the value printed



    const bool connected = connect(myObject, SIGNAL(mySignal()), myClass, SLOT(mySlot());
    qDebug("connection is %i", connected);


    In all cases the connects were OK.



    HINT: by using the breakpoints I noticed the debugger never entered one particular slot. This slot should be called every time the signal readingChanged() is emitted by an object of type QGyroscope(), which belongs to the Android emulator.



    HYPOTHESIS: it is likely that the Android emulator does not emit one or more signals related to the Gyroscope. If you simply want to have the values measured by the Android emulator printed on the emulator itself, you will find out you can. However, the signals associated with these values are never emitted.



    QUESTIONS:



    1) How can I check if a signal with a void argument is actually emitted?



    2) Is there a fix for a signal not emitted by the Android emulator?



    Thanks in advance. Any hint is welcome










    share|improve this question

























      0












      0








      0








      I'm currently on a test project and I'm using the KVM Android Emulator.



      BEHAVIOUR: when I run the code, the app gets correctly opened in the phone emulator but then it no longer responds.



      PREAMBLE: I checked if all Qt connects are correctly performed by declaring them as bool, and then I had the value printed



      const bool connected = connect(myObject, SIGNAL(mySignal()), myClass, SLOT(mySlot());
      qDebug("connection is %i", connected);


      In all cases the connects were OK.



      HINT: by using the breakpoints I noticed the debugger never entered one particular slot. This slot should be called every time the signal readingChanged() is emitted by an object of type QGyroscope(), which belongs to the Android emulator.



      HYPOTHESIS: it is likely that the Android emulator does not emit one or more signals related to the Gyroscope. If you simply want to have the values measured by the Android emulator printed on the emulator itself, you will find out you can. However, the signals associated with these values are never emitted.



      QUESTIONS:



      1) How can I check if a signal with a void argument is actually emitted?



      2) Is there a fix for a signal not emitted by the Android emulator?



      Thanks in advance. Any hint is welcome










      share|improve this question














      I'm currently on a test project and I'm using the KVM Android Emulator.



      BEHAVIOUR: when I run the code, the app gets correctly opened in the phone emulator but then it no longer responds.



      PREAMBLE: I checked if all Qt connects are correctly performed by declaring them as bool, and then I had the value printed



      const bool connected = connect(myObject, SIGNAL(mySignal()), myClass, SLOT(mySlot());
      qDebug("connection is %i", connected);


      In all cases the connects were OK.



      HINT: by using the breakpoints I noticed the debugger never entered one particular slot. This slot should be called every time the signal readingChanged() is emitted by an object of type QGyroscope(), which belongs to the Android emulator.



      HYPOTHESIS: it is likely that the Android emulator does not emit one or more signals related to the Gyroscope. If you simply want to have the values measured by the Android emulator printed on the emulator itself, you will find out you can. However, the signals associated with these values are never emitted.



      QUESTIONS:



      1) How can I check if a signal with a void argument is actually emitted?



      2) Is there a fix for a signal not emitted by the Android emulator?



      Thanks in advance. Any hint is welcome







      android qt emulation qt-signals






      share|improve this question













      share|improve this question











      share|improve this question




      share|improve this question










      asked Nov 22 '18 at 10:34









      ragnarragnar

      221410




      221410
























          0






          active

          oldest

          votes











          Your Answer






          StackExchange.ifUsing("editor", function () {
          StackExchange.using("externalEditor", function () {
          StackExchange.using("snippets", function () {
          StackExchange.snippets.init();
          });
          });
          }, "code-snippets");

          StackExchange.ready(function() {
          var channelOptions = {
          tags: "".split(" "),
          id: "1"
          };
          initTagRenderer("".split(" "), "".split(" "), channelOptions);

          StackExchange.using("externalEditor", function() {
          // Have to fire editor after snippets, if snippets enabled
          if (StackExchange.settings.snippets.snippetsEnabled) {
          StackExchange.using("snippets", function() {
          createEditor();
          });
          }
          else {
          createEditor();
          }
          });

          function createEditor() {
          StackExchange.prepareEditor({
          heartbeatType: 'answer',
          autoActivateHeartbeat: false,
          convertImagesToLinks: true,
          noModals: true,
          showLowRepImageUploadWarning: true,
          reputationToPostImages: 10,
          bindNavPrevention: true,
          postfix: "",
          imageUploader: {
          brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
          contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
          allowUrls: true
          },
          onDemand: true,
          discardSelector: ".discard-answer"
          ,immediatelyShowMarkdownHelp:true
          });


          }
          });














          draft saved

          draft discarded


















          StackExchange.ready(
          function () {
          StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53428988%2fandroid-emulator-does-not-emit-a-signal%23new-answer', 'question_page');
          }
          );

          Post as a guest















          Required, but never shown

























          0






          active

          oldest

          votes








          0






          active

          oldest

          votes









          active

          oldest

          votes






          active

          oldest

          votes
















          draft saved

          draft discarded




















































          Thanks for contributing an answer to Stack Overflow!


          • Please be sure to answer the question. Provide details and share your research!

          But avoid



          • Asking for help, clarification, or responding to other answers.

          • Making statements based on opinion; back them up with references or personal experience.


          To learn more, see our tips on writing great answers.




          draft saved


          draft discarded














          StackExchange.ready(
          function () {
          StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53428988%2fandroid-emulator-does-not-emit-a-signal%23new-answer', 'question_page');
          }
          );

          Post as a guest















          Required, but never shown





















































          Required, but never shown














          Required, but never shown












          Required, but never shown







          Required, but never shown

































          Required, but never shown














          Required, but never shown












          Required, but never shown







          Required, but never shown







          Popular posts from this blog

          MongoDB - Not Authorized To Execute Command

          How to fix TextFormField cause rebuild widget in Flutter

          Npm cannot find a required file even through it is in the searched directory