Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • World
  • Users
  • Groups
Skins
  • Light
  • Cerulean
  • Cosmo
  • Flatly
  • Journal
  • Litera
  • Lumen
  • Lux
  • Materia
  • Minty
  • Morph
  • Pulse
  • Sandstone
  • Simplex
  • Sketchy
  • Spacelab
  • United
  • Yeti
  • Zephyr
  • Dark
  • Cyborg
  • Darkly
  • Quartz
  • Slate
  • Solar
  • Superhero
  • Vapor

  • Default (No Skin)
  • No Skin
Collapse
Code Project
  1. Home
  2. The Lounge
  3. Android Windows SDK installer woes [solved]

Android Windows SDK installer woes [solved]

Scheduled Pinned Locked Moved The Lounge
csharpjavahtmlandroiddatabase
21 Posts 8 Posters 0 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.
  • L l a u r e n

    *bzzzzzzt* wrong answer! works fine for me in glorious 64bit goodness ;)

    "mostly watching the human race is like watching dogs watch tv ... they see the pictures move but the meaning escapes them"

    V Offline
    V Offline
    Vark111
    wrote on last edited by
    #9

    Really? I could only get it to recognize the 32 bit JDK. Would never recognize the 64 bit version, even using the back/next "hack" in the StackOverflow link. :(

    1 Reply Last reply
    0
    • L l a u r e n

      *bzzzzzzt* wrong answer! works fine for me in glorious 64bit goodness ;)

      "mostly watching the human race is like watching dogs watch tv ... they see the pictures move but the meaning escapes them"

      R Offline
      R Offline
      Ravi Bhavnani
      wrote on last edited by
      #10

      Lauren, were you able to get a HelloWorld app running on the emulator in x64?  Also, are you able to stop at breakpoints set in your app's (not library) code?  Finally, did you have to hack the Android manifest file to set the target version to 11 (Android 3.0)? Thanks, /ravi

      My new year resolution: 2048 x 1536 Home | Articles | My .NET bits | Freeware ravib(at)ravib(dot)com

      L 1 Reply Last reply
      0
      • R Ravi Bhavnani

        Lauren, were you able to get a HelloWorld app running on the emulator in x64?  Also, are you able to stop at breakpoints set in your app's (not library) code?  Finally, did you have to hack the Android manifest file to set the target version to 11 (Android 3.0)? Thanks, /ravi

        My new year resolution: 2048 x 1536 Home | Articles | My .NET bits | Freeware ravib(at)ravib(dot)com

        L Offline
        L Offline
        l a u r e n
        wrote on last edited by
        #11

        ravi i use linux to develop most of my stuff ... only use windows to develop windows apps

        "mostly watching the human race is like watching dogs watch tv ... they see the pictures move but the meaning escapes them"

        R 1 Reply Last reply
        0
        • L l a u r e n

          ravi i use linux to develop most of my stuff ... only use windows to develop windows apps

          "mostly watching the human race is like watching dogs watch tv ... they see the pictures move but the meaning escapes them"

          R Offline
          R Offline
          Ravi Bhavnani
          wrote on last edited by
          #12

          Drat.  I knew there was a catch. :) /ravi

          My new year resolution: 2048 x 1536 Home | Articles | My .NET bits | Freeware ravib(at)ravib(dot)com

          1 Reply Last reply
          0
          • R Ravi Bhavnani

            The MonoDroid[^] installation procedure requires that I first install the Java 1.6 SDK (not just the JRE), followed by the Android SDK.  The JDK installed without a hitch, after which I rebooted my system.  The JDK shows up in my list of installed apps. When I run the Android SDK installer[^], I'm greeted with a warning saying the installer can't continue because I first need to install the JDK.  WTF, Google? :| Anyone else having this problem? /ravi

            My new year resolution: 2048 x 1536 Home | Articles | My .NET bits | Freeware ravib(at)ravib(dot)com

            C Offline
            C Offline
            carlospc1970
            wrote on last edited by
            #13

            Hi. I use Win7 x64 at my office and at home and in both systems I installed JDK x32 followed by the Android SDK with no problems and no need to reboot. I hope you have already solved your troubles. Cheers!

            R 1 Reply Last reply
            0
            • C carlospc1970

              Hi. I use Win7 x64 at my office and at home and in both systems I installed JDK x32 followed by the Android SDK with no problems and no need to reboot. I hope you have already solved your troubles. Cheers!

              R Offline
              R Offline
              Ravi Bhavnani
              wrote on last edited by
              #14

              Thanks.  Are you using MonoDroid or Java? I almost got MonoDroid to work.  Deployment to the emulator appears to be broken (version mismatch).  Hacking the Android manifest didn't get me very far. I decided to try the Eclipse route, and found running Eclipse.exe briefly displays the splash screen and nothing else.  The web has old references to Eclipse startup errors.  Unfortunately yet another reminder that despite flames against Microsoft, they provide the best (imho) tooling. I'll try installing the JDK and Eclipse on a fresh Win7-64 box and see if that gets me further.  Hopefully it will. :) /ravi

              My new year resolution: 2048 x 1536 Home | Articles | My .NET bits | Freeware ravib(at)ravib(dot)com

              G C 2 Replies Last reply
              0
              • R Ravi Bhavnani

                Thanks.  Are you using MonoDroid or Java? I almost got MonoDroid to work.  Deployment to the emulator appears to be broken (version mismatch).  Hacking the Android manifest didn't get me very far. I decided to try the Eclipse route, and found running Eclipse.exe briefly displays the splash screen and nothing else.  The web has old references to Eclipse startup errors.  Unfortunately yet another reminder that despite flames against Microsoft, they provide the best (imho) tooling. I'll try installing the JDK and Eclipse on a fresh Win7-64 box and see if that gets me further.  Hopefully it will. :) /ravi

                My new year resolution: 2048 x 1536 Home | Articles | My .NET bits | Freeware ravib(at)ravib(dot)com

                G Offline
                G Offline
                gavindon
                wrote on last edited by
                #15

                I've been running Eclipse for over a year now and have installed it 5 or 6 times all told on different machines with no troubles. I will say this however... When you run .exe with it it can take a couple of minutes to fire up but after that I have found it to be responsive. I have used it on XP, vista, win7 32 and 64 bit.

                Programming is a race between programmers trying to build bigger and better idiot proof programs, and the universe trying to build bigger and better idiots, so far... the universe is winning.

                1 Reply Last reply
                0
                • R Ravi Bhavnani

                  Thanks.  Are you using MonoDroid or Java? I almost got MonoDroid to work.  Deployment to the emulator appears to be broken (version mismatch).  Hacking the Android manifest didn't get me very far. I decided to try the Eclipse route, and found running Eclipse.exe briefly displays the splash screen and nothing else.  The web has old references to Eclipse startup errors.  Unfortunately yet another reminder that despite flames against Microsoft, they provide the best (imho) tooling. I'll try installing the JDK and Eclipse on a fresh Win7-64 box and see if that gets me further.  Hopefully it will. :) /ravi

                  My new year resolution: 2048 x 1536 Home | Articles | My .NET bits | Freeware ravib(at)ravib(dot)com

                  C Offline
                  C Offline
                  carlospc1970
                  wrote on last edited by
                  #16

                  Hello again! I am using Java. I followed this tutorial on setting up a computer for Android development: http://developer.android.com/sdk/index.html[^] I had never used Eclipse (I use Netbeans for Java development) but I have had no problems at all. Maybe it would help if you read the docs at android.com. We all are short on time but I have found that a good reading before starting to use a new tool always helps. Cheers!

                  R 1 Reply Last reply
                  0
                  • C carlospc1970

                    Hello again! I am using Java. I followed this tutorial on setting up a computer for Android development: http://developer.android.com/sdk/index.html[^] I had never used Eclipse (I use Netbeans for Java development) but I have had no problems at all. Maybe it would help if you read the docs at android.com. We all are short on time but I have found that a good reading before starting to use a new tool always helps. Cheers!

                    R Offline
                    R Offline
                    Ravi Bhavnani
                    wrote on last edited by
                    #17

                    carlospc1970 wrote:

                    I use Netbeans for Java development

                    I might give that a try.  I've used Eclipse for Java development before without problems - I'm surprised I'm running into these issues today.

                    carlospc1970 wrote:

                    Maybe it would help if you read the docs at android.com

                    Read and followed.  I actually like reading (and writing) docs. :) Thanks, /ravi

                    My new year resolution: 2048 x 1536 Home | Articles | My .NET bits | Freeware ravib(at)ravib(dot)com

                    1 Reply Last reply
                    0
                    • R Ravi Bhavnani

                      Clickety[^] /ravi

                      My new year resolution: 2048 x 1536 Home | Articles | My .NET bits | Freeware ravib(at)ravib(dot)com

                      D Offline
                      D Offline
                      DBND
                      wrote on last edited by
                      #18

                      This fixed the same problem for me the other day

                      R 1 Reply Last reply
                      0
                      • D DBND

                        This fixed the same problem for me the other day

                        R Offline
                        R Offline
                        Ravi Bhavnani
                        wrote on last edited by
                        #19

                        I still wan't able to get my MonoDroid app onto the emulator.  So I bit the bullet and decided to code it in Java (using Eclipse and ADT) and ran into a similar problem.  The emulator starts but my breakpoints don't seem to be reached. I'm sure I'm doing something stupid (I made sure I'm debugging, not just running) but don't know what. :) /ravi

                        My new year resolution: 2048 x 1536 Home | Articles | My .NET bits | Freeware ravib(at)ravib(dot)com

                        1 Reply Last reply
                        0
                        • R Ravi Bhavnani

                          I manually added C:\Program Files\Java\jdk1.6.0_24\bin\ (WinXP, 32bit) to the path, confirmed that it's all good (by invoking javac from the command line) and reran the Android installer - still no luck. [rant] You'd think Google - with all their might and muscle - would have the ability to create a (signed, please) installer that actually works.  Oh wait a minute - they haven't fixed the annoying IE combo dropdown bug for close to a year.  I suppose an installer's too much to expect. :thumbsdown: [/rant] /ravi

                          My new year resolution: 2048 x 1536 Home | Articles | My .NET bits | Freeware ravib(at)ravib(dot)com

                          J Offline
                          J Offline
                          jszczur
                          wrote on last edited by
                          #20

                          Hi. I had had the same problem but after I added the path I pressed the Back button (I guess it was Back :) then again Next\Ok or whatewer and then in a magical way the JDK has been found by the Installer. Yes, they did f..ked this up.

                          R 1 Reply Last reply
                          0
                          • J jszczur

                            Hi. I had had the same problem but after I added the path I pressed the Back button (I guess it was Back :) then again Next\Ok or whatewer and then in a magical way the JDK has been found by the Installer. Yes, they did f..ked this up.

                            R Offline
                            R Offline
                            Ravi Bhavnani
                            wrote on last edited by
                            #21

                            Yes, that ended up working for me too.  Now if I could only get Eclipse to stop at the breakpoints in my Android app... :) /ravi

                            My new year resolution: 2048 x 1536 Home | Articles | My .NET bits | Freeware ravib(at)ravib(dot)com

                            1 Reply Last reply
                            0
                            Reply
                            • Reply as topic
                            Log in to reply
                            • Oldest to Newest
                            • Newest to Oldest
                            • Most Votes


                            • Login

                            • Don't have an account? Register

                            • Login or register to search.
                            • First post
                              Last post
                            0
                            • Categories
                            • Recent
                            • Tags
                            • Popular
                            • World
                            • Users
                            • Groups