Droid Explorer is the #1 Open Source Android device manager for Rooted devices.
Device Requirements
Rooted Android Device with busybox
Guide to installing busybox on the Droid
PC Requirements
Windows (looking for a developer to help create UI for mono)
.NET Framework 3.5 SP1
Some plugins require Java Runtime Environment and Java Web Start
Confirmed Devices
All Devices have been rooted and busybox installed
HTC Dream / G1 / ADP1
HTC Sapphire / Magic / MyTouch 3G / ADP2 / Ion
HTC Hero / G2 / CDMA Hero
Google Nexus One
Motorola DROID
Samsung Galaxy / i7500
Acer Liquid
HTC EVO
Samsung Galaxy S Line
Features
Includes the required windows USB drivers - you will be prompted to install the drivers during installation if running vista/7
Auto setup of Android SDK tools and drivers during install
Use an existing Android SDK if you already have one set up
Multiple Device Support
No need to mount SD card to access files
Copy any file on the device to PC
Copy files to clipboard
Copy update to device and auto-apply
Drag & Drop copying from Explorer to Droid Explorer
Auto detection of connected/disconnected device
Open files on PC
Plugin Framework
Application Manager
Right Click APK to install/uninstall
Take screen shots of device (landscape & portrait)
Open right from "My Computer" (a lot like how WinMobile is with active sync)
SQLite Manager Plugin
Uses System Icons for files displayed in explorer
Familiar Explorer like UI, including an Explorer like location bar
Android Screencast plugin
Install/Uninstall APK files right from explorer
Standalone plugin runner
Window 7 JumpLists for plugins
DesktopSMS plugin - Send SMS messages from your desktop
Service can be controlled now from the options dialog (can create the service if you do not use the installer)
Backup plugin for the "Bare Bones" Roms
Run shell scripts on the device by double clicking them
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I'd like any thoughts you may have for other features to add to Droid Explorer. Report bugs or request features here or on the project issue tracker.
Web Installer (x86)
Requires internet connection to download android sdk tools
x86 Serivce will not work on x64 OS
Web Installer (x64)
Requires internet connection to download android sdk tools
Use this install if running a 64 bit OS
Older Releases
Source Code Available at CodePlex
Change log 0.8.8.2
New Device selection dialog
all assemblies are now signed again
fixed the "runner" so apk's can now be installed from the machine (along with the other plugins)
when upgrading, and using an existing SDK, the value will now be pulled from the registry, if it exists.
fixed bug in uninstall that would remove the sdk, even if you used an existing sdk
removed anda.pk plugin since the site is dead.
added a link in the bootstrapper (installer) to download the sdk.
refactored some strings to the external resources files in the bootstrapper (installer)
changed the reboot commands to use the adb commands, not the shell commands
fixed rm command to now use busybox as it was passing args that are not supported on the "stock" rm command.
added the sph-p100 device icon
Change log 0.8.8.1
fixed issue that some people experience error durring install about an droidexplorer shell extension.
added sph-m910, htc desire hd (ace), nexus s, and the c8600 icon support
use existing android SDK is now the default and recommended.
added htc vision (Tmobile G2) and the s5830
Change log 0.8.8.0
fixed the issue with latest android-sdk using "platform-tools" directory for adb
fixed screen shot capture to now support 32bpp raw image as well as 16bpp
added other device icons, like the Galaxy S variants
fixed other bugs
Change log 0.8.7.2
fixed issue with the service
minor bug fixes
updated the bread crumb bar
fixed the dragging the window so it doesn't fly off screen
Change log 0.8.7.1
Some refactoring of the settings to keep the Core libraries non-windows dependant.
APK information is now cached for faster loading
Attempting a fix for vista 64 bit and xp 64 bit
fixed the .net 3.5 check
added icon for the EVO (supersonic) - thanks to sanjsrik for identifying the device
added some debugging info to the shell console plugin to see if I can get it working for droid/milestone
Change log 0.8.7.0
Can now use existing SDK instead of the "trimmed" version
Settings stored in the registry now check both Local Machine and Current User
Lots of other little fixes
Change log 0.8.6.0
fixed missing file in the standalone installer
added check for minimum .net framework version in to bootstrapper (v3.5sp1)
increased the service start/stop timeout in the bootstrapper from 30 seconds to 60 seconds
removed initial strings from download panel labels of bootstrapper
htc desire / bravo icon added for attached devices - thanks to beadza for identifying the device
added ability to only install the SDK Tools by running install with /sdk switch
sdk install mode checks if DE is installed, if not, it switches to full install mode
bart plugin now also checks the sd-ext mount point for the license.
added the sd-ext app paths as valid application paths
added sd-ext app paths to the application backup plugin
removed anda.pk plugin as the site is dead.
screencast plugin changed to pull the jnlp file directly from the trunk of the project. If there
is an error, it falls back to a "local" file
fixed issues with spaces in folder names
motorola backflip icon added for attached devices - thanks to zibiza for identifying the device
new screenshot app that handles all resolutions. Uses new methods to get the framebuffer data
adjusted the RGB565 class to better handle other devices for screenshots
started to implement communicating with adb over TCP like ddms does.
acer liquid icon added for attached devices - thanks to fyodor0218 for identifying the device
started working on the ability to use existing sdk (not yet an option, but soon)
Change log 0.8.5.1
Fixed typo in the final step when uninstalling
Fixed x64 issues for windows 7 x64 - still broke on Vista x64 & XP x64 (sorry people, i'm still working on it!)
Default button for bootstrapper changed to the "next" button instead of cancel
added incredible icon for attached devices
added nexus one icon for attached devices
added galaxy S (gt-i9000) icon for attached devices
added acer liquid icon for attached devices
updated the samsung moment icon
added a new "open" version of the moment - rename in the assets directory to "moment.ico" to use.
Change log 0.8.5.0
android screen cast updated to load the lastest build from the trunk
changed publish to use skydrive share instead of the api from the msbuild tasks
added platform tools 2.2
added sdk tools r6
updated repository.xml
added help video link when the device cannot be found
attempting to fix the registry read issues with XP SP3 x64 and Vista x64
removed the "fade out" of the expandos from the treeview to remove the flicker
fixed the issue with opening offscreen
fixed workitem:10275, changed "Close" to "Finish" in the description of the final step of installer
fixed the "hanging" of trying to delete a file. added the '-f' switch to never prompt.
Change log 0.8.4.3
Fixed the install / start up issues caused by the platform tools having a typo in the file name
Change log 0.8.4.0
Fixed issue with cyanogen 4.2.14.x
fixed issue with bart manager plugin license (sorry for the delay)
added 2.1 r1 platform tools
added usb drivers r3 - adds support for nexus one
fixed issue with install plugin crashing if application is already installed.
Change log 0.8.3.0
Fixed bug with device not identifying recovery mode
Display QR code to purchase bart manager if license not found.
mount partitions in recovery mode to find bart manager license
bart manager now attaches to process to output the info
another attempt to set as root when starting for non-adp devices
There is a known bug with droid explorer detecting a device already "connected" going in to recovery mode.
Flash recovery now works in any mode, not just recovery
bart manager license now available for purchase on market.
Change log 0.8.2.3
Drivers removed for windows XP until XP issue with the drivers can be resolved.
added device icon for the nexus one / passion
Code setup to allow some plugins to be purchased.
The .net 3.5 check has been removed for the time being until a better solution can be implemented.
build published via [url:MSBuild Deployment Tasks|http://mdt.codeplex.com]
some bugs fixed here and there
What happened to 0.8.2.2? - Windows locked the directory when I was building that version so it failed and I couldn't delete it to rebuild so I skipped it.
Change log 0.8.2.1
Fixed install issues with 0.8.2.0 - should install for x86 and x64
Change log 0.8.2.0
created a WiX custom action library for checking for the android usb drivers
install logging is now merged in to one file and off by default. use /l[og] to turn on logging
tools will always be downloaded/extracted during install. This lets the tool update to newer tools if needed
fixed delete file when the file name has a space in the file name.
sdk tools upgraded to r4
fixed bug in uninstall if the service did not exist on the machine
should now successfully check for the android usb drivers and install them if revision 2 is not installed.
remember location of "open file dialog"
added code that should check for .net 3.5 sp1 before "crashing" for not having it installed.
added check that the user is installing the correct version (x86 or x64) for their system
Change log 0.8.1.0
added a splash screen so the user is aware that the app is running right away
.NET Framework 3.5 SP1 check added to installer.
apk shell extension now uses the path stored in the registry for the tools.
added logging to the install process
kill all adb processes before attempting to cleanup the sdk path during install.
apk seems to not be working, still debuging the issues. it will be back.
defined a platform constant to the project scripts, x86: PLATFORMX86, x64: PLATFORMX64, ia64: PLATFORMIA64
fixed bug with reading / writing to the registry in x64. now looks in HKLM\Software\WOW6432Node\
fatal errors are now caught and user given option to restart app, close app, or report bug
there is still a bug with installing the driver, the check isnt working so the driver still needs to be installed manually.
Change log 0.8.0.1
fixed installer issue where it crashed if you do not have a proxy set up
x64 installer has issues. - Tempory Fix - Will fixed in next release
Change log 0.8.0.0
added the r2 windows usb drivers, which add support for droid and other devices
added new checks for the drivers. Checks for dream/magic/sholes - these are the devices that google defines in the .inf file.
images moved to external resources library
changed the installer images to be more "custom"
removed need for droid explorer to require "run as administrator" - Yay!
the bootstrapper now handles starting the service. This makes sure the sdk is setup before it starts.
bootstrapper is self contained, the msi is an embedded resource and all referenced assemblies are ILMerged
repository file is hosed on the droid explorer google code site, it is based on the same one that google uses for the android sdk setup
the tools are also hosted on the google code site, this is so the download size is smaller, since all unused bits are removed.
A fully standalone version of install is also available. No need for internet access to install.
boot strapper support uninstall - setup.exe /uninstall
removed reference to the "common.shared" assembly.
added a properites dialog for folders/files
properties dialog shows security settings as well.
fixed icons in context menu for new folder/file
Change log 0.7.12.0
fixed the error that anda.pk plugin logs when it starts because it did not implement "Runnable"
shell extension for apk files so the apk icon displays in explorer - based on http://code.google.com/p/apkshellext/
seems there is a bug in some APKs that dont display their icon, nor do they display the default icon.
registers and unregisters the shell extension on install/uninstall
driver check now works better in the installer
removed some tools menu items that have been replaced by plugins
Installer now gives "options" on what features to install
changed default apk icon to be the "android package" icon
fixed bug with launching ddms and hierarchy viewer
fixed bug launching the google applications backup plugin
added methods to the core command runner to make a mount point read/write and readonly
added icon for the motorola droid
added icon for the samsung moment
added icon for the htc droid eris
Change log 0.7.11.0
USB Drivers installed - This is still in "alpha", should only install them if you need them. please report any issues. It doesn't actually install the drivers, it places them in the driver store, when the device is attached, and the new hardware wizard displays, selecting "automatically install (recommended)" should find the drivers automatically. This installs the 1.6 drivers.
fixed logcat not starting
created a new logcat console that colorizes the log entries
save the logcat output (minus the log level indicator (W/I/D/E/))
support for android screencast 0.2
Change log 0.7.10.1
Fixed crash on device going from connected to disconnected state
Change log 0.7.10.0
Sign Package plugin (signs zip file with test keys)
modified IPlugin to now have methods for creating the toolstrip button and menu items
DroidExplorer.Core.Plugin.PluginHeler added. Contain default static methods for creating the toolstrip button and menu
and.apk now a plugin instead part of "core"
started a contacts manager
started a tool to export facebook contacts from official application to android contacts
added "recovery" as device state.
now "attaches" while in recovery mode.
screenshot now works in recovery mode.
screenshot rotates the current image before refreshing when switching between landscape & portrait
flash recovery image now a plugin - only active when in recovery mode
some bug fixes that I don't remember the exact details on
Change log 0.7.9.0
new shell console enhanced
getprop wrapped to get device properties
explorer icon now attempts to load an icon of the device
- Known devices:
- Bahamas (Tattoo)
- GT-I7500 (Galaxy)
- Hero (G2/Hero)
- Sprint Hero (do not yet know what it identifies itself as in ro.product.device may just show normal hero)
- cliq (need to verify what ro.product.device returns)
- Saphire (MyTouch3G/ION/Magic)
- Dream (G1/ADP1)
- Pulse (need to verify what ro.product.device returns)
- Zii Egg (need to verify what ro.product.device returns)
Device properties viewable in options->environment->known devices->[device-serial]->properties (only when device is connected)
fixed bug with screenshot image being landscape but window portrait.
fixed bug with large icons not always showing the right icon
Change log 0.7.8.0
Desktop SMS now launched from officially signed jar file
Plugin tool strip disabled / enabled when device disconnected / connected
SymLinks and Directories can now also be renamed
F2 starts file/link/directory rename
Executable files now run if double clicked (open from context menu)
Shell Console (could still be buggy so the normal shell window is still available)
double clicking sh scripts run them
plugins that are registered as a file type handler will show up in the right click menu for the file
Change log 0.7.7.0
Renaming of files (folders and links coming)
Google Application Backup (GAB) plugin added
GAB supports HTC's ADB1 update packages (containing system.img), pulling from the device or from normal update.zip
Screen shot plugin supports portrait & landscape modes (use button or right click image)
Screen shot threaded so it doesn't "hang"
Change log 0.7.6.0
Fixed screen shot plugin from opening off screen if droid explorer is maximized or positioned on the right of the screen.
Check for the USB Driver version and download the tool set based on that. If you select the sdk yourself, you must select the correct tools yourself.
USB Driver Version info available in Options->Environment->Android SDK
Speed up of navigating to different directory. Reduced the number of LS calls that are made to build the tree and listview
Change log 0.7.5.0
Fixed plugins executing when loading within Runner
Fixed bug with additional plugin getting the same changed values as other plugin.
Change the SDK path from the Options dialog (requires restart of application)
Fixed bug with apk's not displaying.
Fixed Batch Installer not "showing"
provided a way to manually install, start and stop the droid explorer service - for non-installer users
added ability to save debug output to a file
moved debug window filter buttons to the right
debug window will display below DE if there is room, otherwise, it will display at the top of the screen
added plugin to launch DesktopSMS. Requires the DesktopSMS Server APK be installed on the device - Currently usinging a signed jar by me, hopefully the developer will sign his version.
can now copy symlinks files to clipboard
Change log 0.7.4.0
Changed the SdkInstallDialog to use a WebRequest instead of the WebClient. Hopefully this will help some peoples issues...
Window settings are now saved and reloaded.
Remembers the folder view state (large icon, details, etc)
added --color=never to directory listing command. this should fix the issue people with Heros are having
moved the options dialog tree config to its own file, as it really isnt configured by the user.
added batch installer plugin (alpha) that can install/uninstall multiple apk's at one time.
added logging info for droid explorer. (saved in %USERAPPDATA%\DroidExplorer\logs)
it should also handle "unhandled" errors better
wired up Tools menu items
Added property to indicate if a plugin can be ran by the Runner
Jumplist items added for runnable plugins
Change log 0.7.3.0
app.manifest added to projects. requestedExecutionLevel = requireAdministrator. This means in Vista/Win7 it will prompt w/ UAC. I can not get around this at this time.
this is because in order for the service to use the same settings as the application, i need to save them in the install directory.
The sdk tools, if downloaded, is no longer stored in the user directory, it is stored in the install directory, see above for the reason.
Known devices moved back to HKLM for the same reasons above.
New Options form added.
Device manager now part of options dialog
plugins can now reside in any directory as long as it is added to the plugins settings
plugins can now be enabled or disabled from the options dialog
Service is now working because of the requireAdministrator change.
DroidExplorer.Runner added - a tool that can execute a plugin; usage: DroidExplorer.Runner.exe /type=Full.Plugin.Class.Name,Plugin.Assembly.Nam/any /additional /args
if the type argument is not specified, then it will display a plugin selection dialog.
Installer plugin. This is launched by the runner when an APK file is opened in Explorer.
Registry settings to register .apk files to open with DroidExplorer.Runner /Installer (create with MSI installer)
.apk files can be installed by double clicking them or by right clicking and selecting "Install"
.apk files can be uninstalled by right clicking and selecting "Uninstall"
the initial device selection dialog is only required if more then 1 device is connected.
If you have set up to use the SDK tools by downloading the tools and put them in your user application data directory, when launched, it will prompt you to re-setup the tools. They are not stored in the user directory because the Service can not access that directory.
Just realized the bug with the device name not showing in the titlebar/addressbar. This is already fixed and will be in the next release.
dude nice stuff !!! ... cant wait to look through the source to learn some more C# tricks
Errors pulling up list of APK
Code:
[CommandRunner] adb.exe -s HT840GZ23223 pull "/system/sd/app/com.shazam.android.apk" "C:\Documents and Settings\Administrator\Local Settings\Temp\DroidExplorer\com.shazam.android.apk"
[CommandRunner] C:\WINDOWS\platforms\android-1.5\tools\aapt.exe dump badging "C:\Documents and Settings\Administrator\Local Settings\Temp\DroidExplorer\com.shazam.android.apk"
[MainForm] The system cannot find the path specified - System.ComponentModel.Win32Exception: The system cannot find the path specified
at System.Diagnostics.Process.StartWithCreateProcess(ProcessStartInfo startInfo)
at System.Diagnostics.Process.Start()
at DroidExplorer.Core.CommandRunner.RunAaptCommand(AaptCommand command, String args) in g:\Projects\Csharp\DroidExplorer\DroidExplorer.Core\CommandRunner.cs:line 1057
at DroidExplorer.Core.CommandRunner.AaptCommandRun(AaptCommand command, String args) in g:\Projects\Csharp\DroidExplorer\DroidExplorer.Core\CommandRunner.cs:line 944
at DroidExplorer.Core.CommandRunner.GetLocalApkInformation(String apkFile) in g:\Projects\Csharp\DroidExplorer\DroidExplorer.Core\CommandRunner.cs:line 634
at DroidExplorer.Core.CommandRunner.GetApkInformation(String apkFile) in g:\Projects\Csharp\DroidExplorer\DroidExplorer.Core\CommandRunner.cs:line 626
at DroidExplorer.UI.MainForm.BuildListViewItems(List`1 fsiList)
I basically get the above errors in debug for all the apk's, when I try to display them when clicking on the folder hierarchy of /system/app, system/app-private, /system/sd/app/, system/sd/app-private.
currently running CM 4.1.2.1
andonnguyen said:
Code:
[CommandRunner] adb.exe -s HT840GZ23223 pull "/system/sd/app/com.shazam.android.apk" "C:\Documents and Settings\Administrator\Local Settings\Temp\DroidExplorer\com.shazam.android.apk"
[CommandRunner] C:\WINDOWS\platforms\android-1.5\tools\aapt.exe dump badging "C:\Documents and Settings\Administrator\Local Settings\Temp\DroidExplorer\com.shazam.android.apk"
[MainForm] The system cannot find the path specified - System.ComponentModel.Win32Exception: The system cannot find the path specified
at System.Diagnostics.Process.StartWithCreateProcess(ProcessStartInfo startInfo)
at System.Diagnostics.Process.Start()
at DroidExplorer.Core.CommandRunner.RunAaptCommand(AaptCommand command, String args) in g:\Projects\Csharp\DroidExplorer\DroidExplorer.Core\CommandRunner.cs:line 1057
at DroidExplorer.Core.CommandRunner.AaptCommandRun(AaptCommand command, String args) in g:\Projects\Csharp\DroidExplorer\DroidExplorer.Core\CommandRunner.cs:line 944
at DroidExplorer.Core.CommandRunner.GetLocalApkInformation(String apkFile) in g:\Projects\Csharp\DroidExplorer\DroidExplorer.Core\CommandRunner.cs:line 634
at DroidExplorer.Core.CommandRunner.GetApkInformation(String apkFile) in g:\Projects\Csharp\DroidExplorer\DroidExplorer.Core\CommandRunner.cs:line 626
at DroidExplorer.UI.MainForm.BuildListViewItems(List`1 fsiList)
I basically get the above errors in debug for all the apk's, when I try to display them when clicking on the folder hierarchy of /system/app, system/app-private, /system/sd/app/, system/sd/app-private.
currently running CM 4.1.2.1
Click to expand...
Click to collapse
that's because it uses more then just the ADB, it makes use of a lot of the tools within the SDK. It looks like you have ADB setup in your c:\windows\ directory. Currently you have to manually set up the tools path in the environment variables, but in the next release (hopefully tonight) I will have a utility built in that will download, extract and set up the path environment variable with the SDK tools.
camalot said:
that's because it uses more then just the ADB, it makes use of a lot of the tools within the SDK. It looks like you have ADB setup in your c:\windows\ directory. Currently you have to manually set up the tools path in the environment variables, but in the next release (hopefully tonight) I will have a utility built in that will download, extract and set up the path environment variable with the SDK tools.
Click to expand...
Click to collapse
Weird, I've had the environment variables set up just fine for the past 8 months for adb and the sdk. In SYSTEM PROPERTIES > ADVANCED > ENVIRONMENT VARIABLES
Edit: wth they got erased somehow haha. Looks like ill set them up again. Probably good to include them in your next release as a lot of people aren't willing to set up the SDK.
Code:
Descrizione:
Stopped working
Firma problema:
Nome evento problema: CLR20r3
Firma problema 01: droidexplorer.exe
Firma problema 02: 0.5.0.0
Firma problema 03: 4a9d2e95
Firma problema 04: System
Firma problema 05: 2.0.0.0
Firma problema 06: 49d44bf7
Firma problema 07: 3a97
Firma problema 08: 395
Firma problema 09: System.ComponentModel.Win32
Versione SO: 6.1.7100.2.0.0.256.1
ID impostazioni locali: 1040
Win 7 64bit RC1
IronFly said:
Win 7 64bit RC1
Click to expand...
Click to collapse
Did you install the x64 version? The x86 service will not work on an x64 machine. you have to install the x64 version.
just what i was looking for!
thanks for posting
camalot said:
Did you install the x64 version? The x86 service will not work on an x64 machine. you have to install the x64 version.
Click to expand...
Click to collapse
i downloaded this:
DroidExplorer.0.6.0.0.x64.msi
http://de.codeplex.com/Release/ProjectReleases.aspx?ReleaseId=32271#DownloadId=81513
IronFly said:
i downloaded this:
DroidExplorer.0.6.0.0.x64.msi
http://de.codeplex.com/Release/ProjectReleases.aspx?ReleaseId=32271#DownloadId=81513
Click to expand...
Click to collapse
I will dig in to this when I have access to my laptop that is running Windows 7 64bit.
Thanks Camalot!
In windows seven 32bit this same
0.7.0.0 posted, should now start in window 7 x86 & 64bit.
Windows 7 64 bit here
I manually added the SDK and everything and had .6 working
(at least the basics where)
However .7 gets to the screen saying its going to download whats needed, then stops responding
Did a uninstall and re-installed however, same thing
LinkinX said:
Windows 7 64 bit here
I manually added the SDK and everything and had .6 working
(at least the basics where)
However .7 gets to the screen saying its going to download whats needed, then stops responding
Did a uninstall and re-installed however, same thing
Click to expand...
Click to collapse
I'm having this same problem. I can use adb to access my phone but your app simply freezes up.
Jumping back to .6 for now since its working for me
Main thing I love it just viewing me SD without forceing the cell 2 reboot on unmont
that and I connect with Droid Explorer so android screen cast connects easily lol
LinkinX said:
Windows 7 64 bit here
I manually added the SDK and everything and had .6 working
(at least the basics where)
However .7 gets to the screen saying its going to download whats needed, then stops responding
Did a uninstall and re-installed however, same thing
Click to expand...
Click to collapse
same problem.
hmmm. honest, i tested the setup like 90 times. I'll look in to it when i get off work this afternoon. Sorry if it broke your original setup.
There is a manual work around if you want the latest version and bypass the setup.
Create DroidExplorer\sdk\ Directory in User application data directory
- c:\documents and settings\<username>\applicationdata\ on pre-vista
- c:\users\<username>\appdata\roaming\ vista & 7
download http://droidexplorer.googlecode.com/files/android-sdk-tools-1.5r3.zip and extract to that directory
OR copy the platforms and tools directories from the root of your SDK directory to the above path.
The DroidExplorer\SDK directory should now have 2 directories in side, platforms and tools
Restart Droid Explorer
I will change the installer later today to contain this zip file, I just tried to keep the initial installer as small as possible.
it works with the work around.
HTC G1 Dream JF v1.51
trying to start learning to dev, however I need help setting up usb access for the Bionic. Anyone care to help a newb?
ROB281 said:
trying to start learning to dev, however I need help setting up usb access for the Bionic. Anyone care to help a newb?
Click to expand...
Click to collapse
these should help you out
http://forum.xda-developers.com/showthread.php?p=19446284#post19446284
how-to-get-adb-to-work-on-ubuntu
1. Make sure you have the Android SDK for Linux installed with the package for Platform Tools. Take your SDK folder and move it to your home folder, so that for example to navigate to my SDK folder I type: cd /home/miles/android-sdk-linux/
2. Edit your environment path variable. Everyone uses a more complicated way but I change my Linux distribution quite regularly, almost all based off of Ubuntu, and this is a very easy way that I figured out how to do it. Open up a Terminal and type:
sudo gedit /etc/environment
you will be prompted for your password, then a document will open. you can at the end of the text, inside the last quotation mark, type :/home/username/android-sdk-linux/platform-tools:/home/username/android-sdk-linux/tools mine looks like this::
PATH="/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/home/brandon/android-sdk-linux/platform-tools:/home/brandon/android-sdk-linux/tools" then save it and exit the word processor
3. Now you have to set up your computer so that it recognizes the Android device through ADB. To do this, type this exactly: sudo gedit /etc/udev/rules.d/51-android.rules
A blank file should open up for you. Assuming you are using a Bionic, copy and paste this, SUBSYSTEM=="usb", ATTR{idVendor}=="22B8", MODE="0666", GROUP="plugdev"
if you are using or will be using any other device go to the link below this text for developer.android.com and scroll down to the manufacturer of your device and take the 4 characters and put them where 22B8 is above. I have various devices and my girl has a droid and my dad so I go ahead and set it up to work with all. All you have to do to set up the file for multiple devices is copy and paste the text above on separate lines for each manufacturer you will be developing for, and replace the value following {idVendor} with the respective value for that Manufacturer. For example HTC would be "0BB4". After you have this file setup, you don't need to type anything else, just save it and exit. Then in the terminal type: sudo restart udev
Link for ADB vendor ID's
http://developer.android.com/guide/developing/device.html
4. Make sure your android device has Debugging enabled. To do this go to Settings > Applications > Development and make sure the box for debugging is checked. After this, plug your phone up to the computer and type: adb devices
If you get an error with the command, just restart your computer and it should then work, that just means that your path environment hadn't taken its new effect. and if it still doesn't recognize adb as a command from the terminal, open up that /etc/environment file and make sure the pathname to your android-sdk platform tools is entered correctly.
This is what I do every time I have to set my computer up for development on my device. Also you should check out the Android Source pages at http://source.android.com/
Simple step by step tutorial for installing the Tizen SDK for Wearables
1) Go to http://developer.samsung.com/
2) Select Development Tools for Samsung Gear.
3) Under the SDK portion of the table, select Tizen SDK for Wearable.
4) Before downloading the files, choose a target location. This will make locating the files easier later on.
5) Under Tizen SDK for Wearable 1.0.0b2, in the Install Manager column, select and download the install bin or exe file for your development environment. This file is approximately 4 MB.
6) Under SDK Image, select and download the matching SDK Image. This file is approximately 560MB.
7) Double-click the Install Manager (the 4MB file). The Tizen Window for SDK appears, saying “Cannot start Tizen SDK for the Wearable Install Manager” and “Cannot find repository. Please check your repository (http://)”
8) Click on the Advanced button.
9) Select the SDK Image radio button (bottom half of the screen), and click on the open folder icon to the right.
10) Locate the SDK Image (~560MB), select it, and click Open. This is where having a predetermined download target can be very helpful. The file unzips and takes you back to the previous screen. Click OK.
11) This takes you back to the Tizen Window for SDK, except now you have no warning, and a Next button. Click the Next button.
12) The EULA appears, read and accept the EULA by clicking Next.
13) Install type is Typical. Click Next.
14) Accept the default install location or choose your own, and click Next.
15) The Intel Hardware Accelerated Execution Manager (HAXM) Setup Wizard appears. Click Next for the next three screens, and then click Finish.
16) Reboot if asked to.
Installation is now complete. Next is to start working with some of the Sample Projects, like Making a Custom Watch Face
.
.
Tyzen SDK: cannot execute java even if it was istalled, check environment variables or Java version (1.06 or superior)
Changing or introducing java path variable doesnt work sofar. You get stuck at start. The same problem occurs when installing the wearables SDK version, 32 or 64 bits in W7.
First question, I suppose I could have added more relevant data. Thank You.
Other cases are adb and fastboot problems after Android SDK and Eclipse.
I am learning how to develop android apps. So to debug, I need a device. I tried Genymotion, but it is not working on my PC. So instead, I set up a virtual device on virtualbox and that is running pretty good, but I don't know how to connect it to Android Studio for debugging and testing purposes. Please help me out. If irrelevant, delete the post. Thank you in advance.
shagunc96 said:
I am learning how to develop android apps. So to debug, I need a device. I tried Genymotion, but it is not working on my PC. So instead, I set up a virtual device on virtualbox and that is running pretty good, but I don't know how to connect it to Android Studio for debugging and testing purposes. Please help me out. If irrelevant, delete the post. Thank you in advance.
Click to expand...
Click to collapse
Why don't you use the virtual device already present in Android Studio?
Go to Tools --> android --> AVD manager
you can view the devices that are present in android studio. If you want create a new virtual device you can do so by clicking on "+ create virtual device".
in order to run your code on this device, Run your app by clicking on the play button, you will then get a pop up window. Click on Launch Emulator. Then in the "Android virtual device" drop down menu, select the device you want then press OK.
Dreamerz Studio said:
Why don't you use the virtual device already present in Android Studio?
Go to Tools --> android --> AVD manager
you can view the devices that are present in android studio. If you want create a new virtual device you can do so by clicking on "+ create virtual device".
in order to run your code on this device, Run your app by clicking on the play button, you will then get a pop up window. Click on Launch Emulator. Then in the "Android virtual device" drop down menu, select the device you want then press OK.
Click to expand...
Click to collapse
It's too slow and is not working properly.... idk why, but virtualbox runs good
Hi everyone,
Today I'd like to dust an old subject that was quite discussed: emulating a custom Android ROM.
There are in threads arround here or in some Stack Overflow subjects (for instance) peoples talking about this, providing ideas or even complete tutorials.
These tutorials show how to use the SDK tools to create an Android Virtual Device to run the desired ROM.
But all these informations are purely deprecated and can't be applied exactly for new touch phones (higher than Jellybean you can't do that!)
Didn't realizing it yet and wanting to try it out I personnally downloaded the latest Android Studio software with the basic SDK tools.
I tried to run commands specified in the tutorials to test some things out (like creating an avd) and actually creating an avd this way is purely deprecated. Well.
What a good start.
So instead I used the avd tool of the Studio software and I successfully created one.
Got into the C:\Users\%USERNAME%\.android\avd\avdname.avd folder to check components of the avd. I even read .2cow things files to know the location of the missing components (like system.img)
So I am almost done. I prepared my .img files to replace avd img basic components to test my emulated firmware out. But...
I have no idea where to start!!
I am missing some img files that would be necessary to run the avd correctly, like the kernel.img or userdata thing...
I just don't know what to replace or not, how to obtain necessary files without breaking something, I need help...
Here is finally the question of the subject:
Can somebody post out a complete updated tutorial on how to emulate a full custom rom using the AVD tool provided by Android Studio, please? (If possible of course)
This would be really nice and pretty useful for ROM development. I'm still experiencing things, trying to modify the close-to-my-devive avd I generated but this is just messing arround with things, I am pretty inexperienced so I don't think I could help...
Ok, no contribution as expected...
Fortunately I started reasearches despite the fact that I'm not a dev so I have a really really little idea of what I'm doing...
So here are what my researches led to (report with my memory, I will re-edit my post soon to add what I missed) :
Note: I used my SM-G361F pre-rooted ROM to test emulation.
==========*#1*==========
Operations:
•Created a close-to-device AVD (Same API Level etc.)
•Found out AVD dependencies folders: [C:\Users\%USERNAME%\.android \avd\x86 (I guess?)\(devicemodel).avd then another location containing kernel, system.img etc. thanks to .qcow2 files in the previously presented folder ("link" were in.)
•Made a backup of these folders **obvious**
•Edited some configurations (config.ini etc.) to make the final emulated system as close to the real device as possible to avoid incoherences
•Replaced some components of the AVD (build.prop, cache.img, userdata-qemu.img, etc.)
•Replaced the system image in the second folder
•After an hard struggle to get boot.img file of my device, decompiled it to get the ramdisk.img and kernel.img I used to replace kernel-qemu
Test:
•Starting the AVD from Android Studio
=> Outputs option "repair device"
•Attempted a repair: selected... My device SM-G361F to repair.
(=> Weird...)
•Repair seemed to work well according to the fact I could run the AVD
•Statut of the AVD: Black screen. Using power button and all doesn't make anything working: the AVD doesn't react.
=> Quiting made the emulator crash
Initial reason: see troubleshooting section
Result: FAIL
Troubleshooting:
•I shouldn't had to replace kernel-qemu by the stock extracted kernel: it has nothing to do with the actual system because it isn't purely system but device related. Will fix that next time
•ramdisk was badly recompiled: after extracting it from boot.img using Android Image Kitchen I recompiled it with the recompile.bat that ouputs two files: img-new.img (cannot figure what's its utility...) and new-ramdisk.cpio.gz that I simply renamed ramdisk.img. This could be the main reason why the AVD isn't working.
Will look up how to deal with ramdisk soon.
==========**2**==========
Operation:
•Restored the original kernel-qemu from backup
Test:
•The AVD still not show anything but quiting the emulator doesn't trigger any crash now.
Result: FAIL
Troubleshooting:
•As mentionned before will look up ramdisk.img file that seems problematic
Thread closed. But the project of emulating a custom rom is not abandoned.
Actually I didn't find a way to use the new AVD tool provided by Google to reach this goal. Instead I am heading over the new idea of creating a software generating an environment for Android emulation with given components (kernel, system, data etc. prealably extracted or, better, from a backup)
I hope I'll get help in the future because I'm pretty sure I won't be able to do such enormous task alone...
New thread here: https://forum.xda-developers.com/android/development/help-environment-builder-custom-rom-t3758360