I downloaded the Android SDK tools from https://developer.android.com/studio/index.html which gave me a zip file called tools_r25.2.3-linux.zip. Unziped, it produced a folder called tools, containing the sdkmanager, android. When I tried to run it, it failed with the error message above.
I set ANDROID_HOME to the tools directory, but it still failed.
It turns out that ANDROID_HOME needs to be set to the parent directory, with the contents of the zip file (a single directory named tools) contained within it. Once I did that, it worked fine. This seemed confusing enough to be worth adding to stackoverflow.
The zip file can be opened anywhere. The important thing is to leave the name "tools" and it's files intact.
Run the android program from the tools parent directory as:
$ ./tools/android
This will update the tools parent directory (the one from where you are running ./tools/android) with a number of folders and tools.
I name this parent directory sdk. I also place the whole directory (named sdk) in a folder by the name of the downloaded version.
Now for consistency of my programming environment I bind mount this sdk to a folder in the /opt directory so that it'll be available system-wide.
The hierarchy becomes:
/home/userid/android_r25.2.3/sdk
Now I make a folder in the /opt/ directory called /opt/android/sdk.
My /etc/fstab entry for this becomes:
/home/userid/android_r25.2.3/sdk /opt/android/sdk none bind
It's mounted with:
$ sudo mount /opt/android/sdk
The only thing that changes with new versions or new installs is the location of where the zip file is opened. replace the /home/userid/android_r25.2.3/sdk with where you extract the zipfile and nothing else would ever have to be changed.
The PATH variable will consistently become:
$ export PATH=$PATH:/opt/android/sdk/tools:/opt/android/sdk/platform-tools
And, of course, the eclipse android configuration becomes:
/opt/android/sdk
Using this as a consistent procedure makes reinstalls and installs on new machines very seamless... having only one variable that might change, and that is where the package is extracted.
One more issue is that one has to leave the name of the unzip result tools untouched and move it into a to be created directory in order to allow any version management (or leave it in your home directory if a information-free directory name like "tools" doesn't distrub you). Then set ANDROID_HOME like #JesseW explained.
unzip tools into e.g. ~/android-sdk, so it will live at ~/android-sdk/tools
then in ~/.bashrc
export ANDROID_HOME="$HOME/android-sdk"
ANDROID_TOOLS="$ANDROID_HOME/tools"
ANDROID_PLATFORM_TOOLS="$ANDROID_HOME/platform-tools"
export PATH=${PATH}:$ANDROID_TOOLS:$ANDROID_PLATFORM_TOOLS;
then run sdkmanager
Related
I have download the android-studio android-studio-ide-202.7351085-linux.tar.gz file from develop.android.com and I have extracted this file to /opt/android-studio folder so that the android studio software should be installed on root directory. I don't want to install it in /home/Downloads directory. but I have not shown any software icon on my app bar and search bar. I want to know why and I also want to set path environment variable for run/start the android studio from any directory.
as it mentioned in install_linux.tar the instruction is 3 and 4.
3. [OPTIONAL] Add "{installation home}/bin" to your PATH environment variable so that you can start Android Studio from any directory.
4. [OPTIONAL] To adjust the value of the JVM heap size, create a file studio.vmoptions (or studio64.vmoptions if using a 64-bit JDK) in the configuration directory and set the -Xms and -Xmx parameters. To see how to do this, you can reference the vmoptions file under "{installation home}/bin" as a model but do not modify it, add your options to the new file.
my purpose of installing android-studio is for learning app development in flutter.
Short answer:
Go to your home directory.
Type ls -a
You should see file named .bashrc (perhaps you will see file named .zshrc insead - then replace .bashrc with .zshrc)
Type nano .bashrc
Add this line to the end of file: export PATH=/path/to/your/instalation/directory/android-studio/bin:$PATH
Press CTRL+s, then CTRL+x
Reload with source ~/.bashrc
Long answer:
I had the same problem and I found this site https://linuxhint.com/add-directory-to-path-linux/, where is everything explained to details. I would recommend reading it.
Quick Tip:
For Kali linux add file (export PATH=/path/to/your/instalation/directory/android-studio/bin:$PATH) to .zshrc instead of .bashrc
Now that Xamarin supports creating App Bundles in the .aab format, is there any way to use Visual Studio to add downloadable Asset Packs to the bundles?
Here's a guide for creating install-time asset packs on Windows 11 manually using Windows Subsystem for Linux:
Install Windows Subsystem for Linux (WSL)
Download aapt2 (Linux version) from Google Maven (download the jar file and then extract its contents with "jar xf"), e.g. https://dl.google.com/android/maven2/com/android/tools/build/aapt2/7.2.0-alpha06-7909850/aapt2-7.2.0-alpha06-7909850-linux.jar or get it right here: https://drive.google.com/file/d/1sb9KevVgRA9PTAGqc74rWorWBtXWYnWq/view?usp=sharing
(You can download Java from https://www.java.com/en/download/ to get the jar utility.)
Create an appropriate AndroidManifest.xml (example here: https://drive.google.com/file/d/1sb0BeyWcs7edz_qL9aTqkt55pGmhhJ4e/view?usp=sharing); Change the package attribute to match your app id, such as com.company.yourgame. Make sure to that the file uses Linux line endings (it might work with Windows line endings, too).
Create a directory for the asset pack (let's say C:\assetpack) on Windows.
Put aapt2 and AndroidManifest.xml to that directory.
Create Assets directory under the assetpack directory. Put all assets there.
Download this bash script file: https://drive.google.com/file/d/1saOfj5a3wHIrB5nTJsDqv0GhMnaP3m_n/view?usp=sharing and put it into the assetpack directory. Make sure that it has Linux line endings. It will not work with Windows line endings.
Start WSL and navigate to the assetpack directory by "cd /mnt/c/assetpack"
Run "./createassetpack.sh assets.zip com.company.yourgame", where com.company.yourgame is the id of your app. assets.zip is the name of the final zip file.
assets.zip will now appear in the assetpack directory. Copy this file to your solution, let's say to assetpack\assets.zip under your Xamarin.Android project.
Go to your Xamarin.Android project and edit its project file with a text editor. Add the following code after all ItemGroups in XML:
<ItemGroup>
<AndroidAppBundleModules Include="assetpack\assets.zip" />
</ItemGroup>
Now, you can access your assets through AssetManager. For example, in your MainActivity.cs, you can write:
using(var stream = Assets.Open("myasset.png"))
{
//Code goes here
}
They are working on it:
https://developercommunity.visualstudio.com/t/xamarinandroid-asset-delivery/1527043
https://github.com/xamarin/xamarin-android/issues/4810#issuecomment-902235355
So, we need to wait a bit more.
Will it cause any problem if I delete the "Android\sdk" [Size: 2 GB] folder from an old directory path "C:\User\AppData\Local\Android\Sdk" ?
I actually do have another "Android\sdk" folder [Size: 23 GB] on a different location [Local Disk D] since previously I faced WHITESPACE NAMING ISSUES while using Android Studio. So I think the folder is lying idle on my Local Disk C. Should I delete the folder on the path "C:\User\AppData\Local\Android\Sdk" ? Or, will it harm the IDE in the future ?
No it will not harm your development and IDE, but make sure that before deleting this sdk folder, the Android Studio SDK path has been set to the other targeting SDK. You can completely delete the one which you are not using.
You can simply make a link folder to your main android sdk folder (23gb). you can put that link in place of your first folder (2gb). even you can have your main folder in a path with spaces, but you've to create a link folder for some where like c:\android\sdk and in your favorite IDE sets the path to that. It's a OS level abstraction and everything works like a charm on top of that
For example:
mklink /j C:\android-sdk "C:\Program Files (x86)\Android\android-sdk"
Yes. You can remove your older Android SDK Folder (2 GB). There is no longer a need for it as the Android studio is targetting the new location PATH ("D" Directory) so, Feel free to remove the older one.
I'm trying to use FastCV, https://developer.qualcomm.com/mobile-development/mobile-technologies/computer-vision-fastcv/setting-developer-environment. It tells me that I need to install Android NDK. I did that and put it in the place that it told me to.
I then try: cd /cygdrive/c/Development/Android/android-ndk-r6/samples/san-angeles
And it tells me that there is no file or folder by that name.
I then try the command ndk-build and it tells me that there is no command by that name.
Note: there is a cygwin section in the "How to get started" section, but it says that it is not relevant for mac users.
Here is another part that I don't understand:
MAC: Update $path variable to point to the ndk directory. Modify the /Users/<login-name>/.tcshrcfile to set the path by adding /Users/<login-name>/Development/Android/android-ndk-r6. Along with the changes applied in the section 'Android SDK Downloader' you will have:
set path = ( $path /Developer/usr/bin /Users//Development/Android/android-sdk-mac_x86/tools /Users//Development/Android/android-ndk-r6 )
I have NO idea what is being asked of me here.
I just want to solve this, so I can actually start doing things.
Edit: I think (emphasis on I think) that I misread the instructions about cygwin. So I don't need to do the ndk-build commands. However, I still don't know what the instructions mean about the path stuff
You should download NDK for Mac OS, the 64-bit version can be found here. Note that today we don't use r6 anymore, the current version is r9.
NDK is distributed as a plain compressed archive. Mac will open it for you and extract all files. Copy this whole tree wherever you like, and add the top directory to ${path} environment variable.
Let's say you decided to copy extracted NDK into /Users/user678392/ndk. Then you should try
cd /Users/user678392/ndk/samples/san-angeles
ndk-build
I have created an AIR app that is currently on the market. To update the app, obviously I must keep the same package name. My first version's were packaged using Eclipse with the ADT plugin.
Now to use AIR 3.0 Native Extensions (ANE) which were not available when I first developed the app, I currently must create my APK using AIR's command line tools. Unfortunately, these command line tools force you to have a package name that starts with the word "air". For example, I need the package name "com.example". AIR creates the package name as "air.com.example".
So now, I cannot update my app in the market since the package name has changed. Adobe has this horrific article to help you rename and remove the "air" in the package. I'm not a great programmer so this has really stumped me.
http://kb2.adobe.com/cps/875/cpsid_87562.html
Apparently this info is out of date or incorrect in a few areas.
I have completely stumbled at step 12 which uses apkbuilder:
apkbuilder final.apk -u -z resources.arsc -f classes.dex
I am getting this error message:
THIS TOOL IS DEPRECATED. See --help for more information.
java.io.FileNotFoundException: resources.arsc does not exist
I have used step 10 to create the new resources.arsc file. It clearly DOES exist and in the correct location. I tried using apkbuilder with other resources.arsc files taken from other projects. I still get the same error message.
Is there a chance in hell of this working? If anyone is interested in this, I have a zip file with a sample AIR apk, windows bat files for all the command line work, and all the needed utilities so they don't need to be downloaded. To get started you just need to change my path.bat to fit your system. And you need notepad++ (or an equivalent) to batch automate renaming the package name across several files.
bradwallacedesign.com/dktimer/renameApkProject.zip
Thanks so much!
this was done on a pc. i have no idea how to do this on a mac.
i don't recommend using this to remove the "air." from an air package name. If you do so, the user will not be prompted to download air on their device. the user will get an error message instead with no clue to the problem. of course you can use air captive runtime to solve this issue.
http://bradwallacedesign.com/share/renameAPK.zip
download and unzip my file (renameAPK.zip) to c:\renameAPK.
required files:
my file (renameAPK.zip) which contains the apkTool
java jdk/jre
android SDK
notepad++ (or an equivalent text editor that can rename across multiple files)
i made many bat files since i'm not sure how to combine them into one file. you will need to edit each one to change your path names and file names to work with your computer and your apk file.
i numbered all the bats in the order that i use them. once a command line is open, i type the number of the bat file i want then hit the tab key to automatically finish the name of the bat file then hit enter to run that bat file.
instructions:
double click `openCmd.bat to open a command line pointing to the directory with all your files.
0. run 0path.bat to set your path. (i can't remember now if the adobe air sdk is needed for this but i have it in my path. obviously, the JDK is needed and the android sdk for the jarsigner and zip align i think.)
1. run 1decompileAPK.bat to have apkTool decompile your app into a folder called UNZIPPEDapk
2. follow the instructions in 2editManifest & PackageName - Instructions (not a bat).txt to edit the manifest and package name using Notepad++ inside UNZIPPEDapk:
edit AndroidManifest.xml:
a. change package name from air.oldPackageName to newPackageName
b. edit other needed entries:
c. rename folder system inside "smali" folder so that it works with your new package name
for example:
if the old package name was: air/oldName then change the folders to match the new package name: air/newName
use notepad++ (or any editor that can find and replace text over many files)
d. ctrl+shift+f --- "Find in files"
find:
air/oldPackageName
replace with:
newPackageName
where:
all files in UNZIPPEDapk/smali
(i think there were over 200 replacements)
3. run 3buildDistFolder.bat to have apkTool build the new apk in the UNZIPPEDapk\Dist folder
4. follow the instructions in 4getMissingFiles - instructions.txt to reinstate the 2 missing files in the new build:
a. Two files were not built during 3buildDistFolder:
3buildDistFolder.bat built the new apk in the \UNZIPPEDapk\dist folder but it failed to copy 2 files:
(skipping hidden file 'C:\Users\computer\apkTool\UNZIPPEDapk\assets\META-INF
\AIR\extensions\com.adobe.mobile\META-INF\ANE\Android-ARM.classpath')
(skipping hidden file 'C:\Users\computer\apkTool\UNZIPPEDapk\assets\META-INF
\AIR\extensions\com.adobe.mobile\META-INF\ANE\Android-ARM.project')
grab these 2 files from your original apk and drop them into your new apk in the correct folder
b. copy yourApp.apk from DKTimer/Dist/ to root directory where your bat files are.
5. run 5signAPK.bat to sign the apk.
developer.android.com/guide/publishing/app-signing.html
6. run 6verifySigned.bat to verify the signing worked properly
7. run 7zipAlign.bat to align the apk file.
developer.android.com/guide/developing/tools/zipalign.html
You are finished at this point. Continue on if you want to test it on a device.
8. run 8installAPK.bat to install the apk on a usb connected device.
9. run 9remoteDebugger.bat if you want to use remote debugging.
i hope this helps someone. let me know if i forgot to include something.
also, if you know a better way to do this, please comment (such as how to combine this into 1 long pausing bat file...)
There is a simple environment variable you can set to disable the air. prefix easily. The following code exists in the Adobe AIR packager:
String optOut = System.getenv("AIR_NOANDROIDFLAIR");
if ((optOut == null) || (optOut.indexOf("true") == -1)) {
packageName = "air." + packageName;
}
So, simply set the AIR_NOANDROIDFLAIR environment variable to true, repackage your application, and it won't have the air. prefix. Google how to set environment variables in windows or mac for your particular OS version.
For example, I use the command-line compiler on Mac/Linux, so I run:
> export AIR_NOANDROIDFLAIR=true
> java -jar $AIR_HOME/lib/adt.jar -package -target apk-captive-runtime -storetype pkcs12 -keystore cert.p12 -storepass *** Main.apk Main-app.xml Main.swf
Warning: I don't know what implications this has. Per someone's note above, this may only be a good idea with captive runtime (but that's the default going forward from AIR 3.8).
Update: Renaun Erickson said it shouldn't cause problems.
Cross-posted here (slightly different question, same answer).
Having tried several apkRename tools, I found that they all failed for some app, such as com.android.browser on HTC device.
The reason is in apktool which does not correctly unpack apk file sometimes.
So, i create my own tool: https://github.com/sjitech/ApkRename
No need apktool, no need aapt, just java and jar utilities.
This utility directly modify AndroidManifest.xml so without recompile whole resource by apktool,
so it's clean.
Tested devices: 11 kinds (both android 4+, but 2.2+ should be no OK)
Tested OS: Mac OS X 10.9 and CentOS 6. (Cygwin with bash 4+ should be OK, but not tested yet)
I actually tried brad's approach and couldn't imagine having to go through the process EVERY TIME i compiled a release. so i did something else...i modified ADT so it doesn't insert "air." at the start and replaces it with a more useful extension like "com."
Here's a summary of the approach:
use:
jar xf adt.jar
to extract the adt.jar file to a directory on your desktop. you'll find it in {adobe SDK}/lib/
look for the file APKOutputStream.class
com/adobe/air/apk/APKOutputStream.class
Open it in a hex editor (eg, HxD is what i used). Search for "air." (without the quotes but including the dot).
Don't delete the entry. i tried, you can't, it corrupts the class and it won't run. What you can do, however, is replace "air." with "com." because it has the same number of characters and doesn't mess with the length of the file. The com prefix is a lot more useful to most of us.
save the modified APKOutputStream.class file and repackage with JAR. something like this:
jar cfm ..\patchedadt.jar ..\MANIFEST.MF *
you'll want to copy that MANIFEST.MF file from the subdirectory of the package called META-INF
Rename your patchedadt.jar to adt.jar and put it back in the lib directory. Works with the Flash Builder and all that garb.
Needless to say, when you're in there, you'll want to produce your package without a "com." prefix so you don't end up with com.com.your.package.name.
maybe there was an easier way, but i didn't know any better and no one else had an answer except to decompile the apk, modify it, and recompile and that didn't even work. so i figured i'll share what i did in case someone else stumbles on it later :)
jim