Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • Users
  • Groups
  • Search
  • Get Qt Extensions
  • Unsolved
Collapse
Brand Logo
  1. Home
  2. General talk
  3. The Lounge
  4. AVDs and general Android discussion [solved]
Forum Updated to NodeBB v4.3 + New Features

AVDs and general Android discussion [solved]

Scheduled Pinned Locked Moved The Lounge
5 Posts 2 Posters 2.0k Views 1 Watching
  • 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.
  • T Offline
    T Offline
    thready
    wrote on last edited by
    #1

    I can’t seem to get an AVD going. I see I’m always on target API of 19 (which seems high, but that’s something to look into). And ABI has 4 choices [armeabi-v7a, armeabi, x86, and mips]. What exactly do these settings do and do these matter when targeting AVDs? Also I'm getting the error message, “Qt version for architecture mips is missing”. Which one I should choose and why? Is it because Qt is compiled to each one and packaged in some mega zip that allows whichever device to get appropriate files?

    I’m running on Windows 7 pro, I’ve got an S4… Can someone give some tips to direct my focus to develop well on Windows (debug) and what ratio of debugging would you feel reasonably safe with testing on AVDs and actual devices? With audio recording, should I try all devices possible or are they generally all very equally supported the same way?

    Thanks for any other tips in general as well in getting an app onto the play store - any gotchas you experienced, etc...

    [solution was to downgrade the tools version of the android SDK since Qt was not recognizing the device because of a way device names are output with "default/" prepended]

    1 Reply Last reply
    0
    • T Offline
      T Offline
      thready
      wrote on last edited by
      #2

      Yep... I always get device is incompatible error. I'm choosing the same architectures, I even added the environment variable into the system to no avail: ANDROID_NDK_ROOT=C:\android-ndk-r9d

      I'm sure it's some dumb newbie error. This is always the toughest part... Getting used to new things. All you can do is rely on the really smart, really nice people to help... <blink> <blink>... I guess that might work if I were a good looking blond...

      1 Reply Last reply
      0
      • T Offline
        T Offline
        thready
        wrote on last edited by
        #3

        [solution was to downgrade the tools version of the android SDK since Qt was not recognizing the device because of a way device names are output with “default/” prepended]

        1 Reply Last reply
        0
        • O Offline
          O Offline
          overtime
          wrote on last edited by
          #4

          What did you downgrade to?

          1 Reply Last reply
          0
          • T Offline
            T Offline
            thready
            wrote on last edited by
            #5

            r22.3

            Cheers,
            Mike

            1 Reply Last reply
            0

            • Login

            • Login or register to search.
            • First post
              Last post
            0
            • Categories
            • Recent
            • Tags
            • Popular
            • Users
            • Groups
            • Search
            • Get Qt Extensions
            • Unsolved