[TOOL] Android Commander 0.7.9.11

Search This thread

slartyxxx

Member
Apr 18, 2010
29
5
Google Pixel 6 Pro
Problems on Win7

Heya,

I just changed my operating system from WinXP pro to Win7 pro 64bit. On WinXP all worked fine. But not on Win7, I don't get it properly working. Operating on my device works fine but when I try to access apk file functions on Windows for example "Show Android Applications" via Windows Explorer right-mouse-button-menu I get an error for every found app:

"Android Commander: Program could not extract APK file: filename.apk"

Any idea? Also icons of apk's on double click don't show up properly, only green android is showed as default icon. This worked well under WinXP. Btw, I remember I installed some Android Developer stuff additionally on my old WinXP system. But latest requirements for AndroidCommander only list Java JDK, which I installed successfully on the new Win7 system. Please Help.

Thanks.
 
Last edited:

slartyxxx

Member
Apr 18, 2010
29
5
Google Pixel 6 Pro
Heya,

I just changed my operating system from WinXP pro to Win7 pro 64bit. On WinXP all worked fine. But not on Win7, I don't get it properly working. Operating on my device works fine but when I try to access apk file functions on Windows for example "Show Android Applications" via Windows Explorer right-mouse-button-menu I get an error for every found app:

"Android Commander: Program could not extract APK file: filename.apk"

Any idea? Also icons of apk's on double click don't show up properly, only green android is showed as default icon. This worked well under WinXP. Btw, I remember I installed some Android Developer stuff additionally on my old WinXP system. But latest requirements for AndroidCommander only list Java JDK, which I installed successfully on the new Win7 system. Please Help.

Thanks.

Seems I found the solution:

Replace aapt.exe in "\Android Commander\bin\" with aapt.exe from latest Android SDK and tadadadad.... it works again :)
 

Attachments

  • aapt.rar
    1.3 MB · Views: 53

alentsa

Senior Member
Sep 26, 2007
66
3
Great application. Great idea. Thank you!! But the interface is not there yet. I can't do a search. The progress bar is not really a progress bar, just a blinker. Push/pull/copy concept is a little confusing. Since the idea is same as in Total Commander, maybe a plugin for the Total Commander would be the way to go, at least for simple copy/move/make directory operations?
 

kenzolo

Senior Member
Jun 14, 2012
1,474
3,052
Rome
I've problem to use android commander in the startup I've this error
" is not integer value
I've last omega 9 XXBLG1 on galaxy s3
someone can Help me?
 

zevele

Inactive Recognized Developer
Mar 8, 2010
279
89
Hi PanPiotr,

I love your application, but it seems download doesn't work on your temporary page (maybe it's me?)

Thanks,

Z.

Update: I used the facebook link... thanks...
 
  • Like
Reactions: PanPiotr

byrko

Senior Member
Aug 2, 2010
117
11
near Cologne
With CM9 and CMREX ROMs Android Commander shows "No root". Is there any chance to change this?
 
Last edited:

uppon2

Inactive Recognized Contributor
Oct 27, 2010
3,108
1,488
I seriously still can't believe how many people don't use this or know about it. It's ideal for slack people or if you are changing anything in framework etc. You only have 69 thanks. Man you deserve more credit
 

Top Liked Posts

  • There are no posts matching your filters.
  • 39
    logo.png


    My website is down, but download is still alive.


    Hi Guys!

    Android Commander is windows application to keep control on your android apps and files from PC. This is a small, very very fast and intuitive app.
    If someone want to try it, go a head. But remember, you doing this on your own risk! I'm not professional programmer, this is only my hobby :)

    Program Requirements
    Before you install the program you should read this:
    Phone Requirements:
    - ADB ROOT Access
    - BusyBox
    - „Settings->Applications->Development->USB debugging” must be enabled
    - USB Cable

    Computer Requirements:
    - Windows XP/Vista/7
    - ADB USB Driver
    - Java JDK
    - Minimum 800×600 screen resolution

    Android Commander should works for any android device, but here is list of devices confirmed by me or users.

    Before you report any problem to me, read program FAQ.

    Full list of program features.

    Screens:
    Android Commander screenshots gallery

    3.PNG




    If you like my program, conceder a donation please!


    Download is here
    mirror

    Program wasn't updated for a long time, but it still can work with any android device. The only think you have to do is update ADB binaries in program directory.


    Changelog:
    Version 0.7.9.11:
    Changelog:
    - updated adb and aapt binaries
    - better work with JB
    - better updates checking system (disabled as default)
    - files and partitions size display improvements
    - more fixes

    Full program changelog
    3
    Hi

    Imposible download your program, file corrupt.

    Thanks

    Here it is.... Enjoy..
    3
    Update!

    small update for you
    https://www.facebook.com/androidcommander/posts/10151031241149594

    i will update thread tomorrow, i'm going to sleep nowww......
    3
    Heya,

    I just changed my operating system from WinXP pro to Win7 pro 64bit. On WinXP all worked fine. But not on Win7, I don't get it properly working. Operating on my device works fine but when I try to access apk file functions on Windows for example "Show Android Applications" via Windows Explorer right-mouse-button-menu I get an error for every found app:

    "Android Commander: Program could not extract APK file: filename.apk"

    Any idea? Also icons of apk's on double click don't show up properly, only green android is showed as default icon. This worked well under WinXP. Btw, I remember I installed some Android Developer stuff additionally on my old WinXP system. But latest requirements for AndroidCommander only list Java JDK, which I installed successfully on the new Win7 system. Please Help.

    Thanks.

    Seems I found the solution:

    Replace aapt.exe in "\Android Commander\bin\" with aapt.exe from latest Android SDK and tadadadad.... it works again :)