Hello i had this bug in one of my apps. I can't uninstall it if its marked as an auto start app in Blackberry descriptor. When i turn off this option i can delete it.
Someone has experimented this kind of problem?
i have tried going to apps administrator but the option isn't showing there either.
NOTE: i installed this application through eclipse as DEV.
I found someone having the same problem as me here : https://supportforums.blackberry.com/t5/Java-Development/Deleting-an-autostart-app/td-p/1436287
You can run this command to force-delete an app, if you know the module name:
javaloader -usb erase -f example.cod
You can find the Javaloader executable inside the bin folder in your Blackberry SDK folder. For the eclipse plugin, you can also find it inside the component packs:
<eclipse folder>\plugins\net.rim.ejde.componentpackX.X.X_X.X.X.X\components\bin
(the X are the versions numbers, that might be different in your case).
You might also be able to do it from the device settings, inside the installed apps screen, if you change the view to list the modules.
Related
I am new to Android Studio, and thanks to my dog knocking water on my Mac, I am using my PC with Windows 10 for the foreseeable future. Since I'm trying to learn Android Studio while also trying to pinpoint all the bs Windows is doing in the background, I have been beating my head against the wall for several days. To start, the PC I'm using has a 128GB SSD and a 1TB HDD, and since Windows is busy filling up my C: drive (the SSD), I am trying to keep everything else on the HDD. I originally installed Android Studio and went with the defaults, which put it on the C: drive, but when I realized what happened I uninstalled it and re-installed it on the D: drive. I also installed all the SDK tools and API versions on the D: drive.
The problem I am running into is every time I try to import a project from a tutorial, it says the project isn't synced with Gradle (these tutorials are all using older APIs and Gradle versions) and won't even give me the option to build. Originally, I set the GRADLE_HOME environment variable for the Gradle version installed on my D: drive to D:\Program Files\Gradle\gradle-4.8-bin\gradle-4.8\bin and then I could at least run the gradle command without getting "command not recognized...". At that point, the new projects I had created were running fine, but any project that used an older version would not sync. I guessed that I might need to install the older Gradle versions in order to be compatible with older projects, so I installed all of them and put them in the same D:\Program Files\Gradle directory, then set that to my environment variable. That broke everything since the variable was no longer pointing to a bin folder I assume. Now when I try to import a project using Gradle external model, it doesn't matter if I select the specific Gradle path to the /bin folder on the D: drive, or if I set it to C:\Users\brand.gradle, it says 'Gradle location is incorrect'. The only way I can make the gradle command work is if I go to the /bin folder for any one of the versions I have installed, and run it from inside the directory.
I know that when Android Studio installed it put the gradle configuration in C:Users\brand.gradle, part of the reason why I thought changing the GRADLE_HOME variable might fix it. Currently, the gradle command will not work if I am in the C:\Users\brand.gradle directory. I have researched a lot but can't seem to find clear answers, especially in regards to the newest versions of everything, so here are my primary questions:
Where does AS store and look for the gradle configuration on Windows by default (not for an individual project, but for Android Studio itself), and how can I get it to store and look for things on the correct drive?
Do I need every gradle version installed to be able to run projects that use older versions, and if so, is there a way that Android Studio can automatically find the appropriate version if they are in the right location?
In short, I want AS to do everything on my HDD, where all of the SDKs and gradle versions are installed, but I think it is looking in the wrong places by default, and perhaps even changing things back to default values after I change them. I want this to stop, but can't figure out what it's doing.
If you are running android Studio version 4.1.2 then go to Files -> Setting -> to
Build, Execution, Deployment, click on Gradle and it will show you the Gradle user home, it is here that you can change the directory. But make sure you copy over the Gradle files first to the external drive.
Yes, this question has been asked before. But the solutions on the internet are not working so that's why I am asking it here. I'm guessing the solutions aren't working because I am using newer versions but I'm not sure.
Bit of Background: So I am making a small game in Unity. I have to test it on Android so I can check if there are any problems or not. So I check around the internet on how I may be able to do that. Turns out, I need to change the build settings to android and I also need JDK installed on my computer along with Android SDK Manager so I download them both. I did not install the Android Studio but just the Command Line Tools because many tutorials say that I do not actually need the whole Android Studio because I'm gonna be making the app in Unity not in Android Studio. So I do that. I install JDK and Extract the command line tools.
I think the JDK installed fine because after installing JDK, I opened Internet Explorer (No, I don't use IE, I use Chrome but I opened it just for fun). And a little notification showed up at the bottom which basically said that I could now run Java on the browser so that's why I don't think there are any problems with the JDK installation.
Problem: I extracted Command Line tools of Android Studio and found that there was only a tools/ folder in it. I opened it and clicked on android.bat but the Android SDK manager doesn't work. A CMD screen just flashes for a moment but then nothing happens.
Solution I have Tried:
Change set java_exe to:
set java_exe="C:\Program Files\Java\jre7\bin\java.exe"
and delete the line:
call libjava_find.bat
But I can't find set java_exe code anywhere in the file. The file doesn't have it. How am I supposed to change it?
Alright, so I figured it out but I was still unable to pinpoint the problem. Here is what I did:
Installed a fresh copy of Windows 10. Note: It is highly unlikely that this will solve the problem. But where I live, it is very common to just install a fresh copy of windows whenever you get a problem. I really don't think you need to do this.
Follow all the instructions from: https://www.youtube.com/watch?v=yLFBu-VlBIw
If you get the following error:
Error building Player: CommandInvokationFailure: Unable to list target platforms. Then use this fix: not finding android sdk (Unity)
These steps solved the problem for me and I was able to run it properly.
I already had Eclipse (kepler) installed to create java programs.
Now I wanted to develop android apps, so I wanted to install the ADT plugin for Eclipse.
I read the following:
http://developer.android.com/sdk/installing/installing-adt.html#Download
I did those steps exactly.
Then, on that same page, I read this paragraph:
http://developer.android.com/sdk/installing/installing-adt.html#Configure
But I don't understand what I have to do.
When Eclipse restarts, I get a popup diolog which asks me to choose a path which has to lead to a folder. I can't find any folder. I don't see anything changed in my file system.
I don't see any folder which looks like Android SDK. I think I am missing something.
You need the SDK as well. You can find it here:
https://developer.android.com/sdk/installing/index.html?pkg=tools
When you install it you have to insert the path of your SDK in the Eclipse popup dialog
I encourage you to update the SDK on your first launch through SDK manager
I have been trying to install crashlytics for the passed 6 hours with no succes.
The first time it started downloading some libraries but something went wrong and I had to delete them all again. I'm talking about the ones that it places in the lib folder it creates (not sure of the exact name of that folder).
After that it simply refuses to redownload them and just sits there on the "build and launch the app" window so it can "verify" its configuration.
So here's the issue, because it doesn't download the stupid libraries i can't import them in any of my classes or use them.
Fabric.with(this, new Crashlytics());
gives errors ofcourse because it can't resolve "Fabric" or "Crashlytics". Why the people at crashlytics don't give you the simple option to download the jar file(s) yourself is beyond me...
In any case, here's what I've tried:
uninstalling the eclipse plugin
searching for EVERY reference to fabric and crashlytics and deleting them if relevant
deleting all contents and whatnot
deleting eclipse's artifacts.xml file
Since it's a git project I even deleted all the project files, created a new git folder and pulled them again there.
manually attempt to put some of the jars from the plugin folder in my libs folder and adding them to my build path
but nothing works... help?
Follow the steps to integrate Crashlytics to application.
If it is first time then fabric will support you in doing the setup.
https://fabric.io/onboard given option to select SDK.
Select SDK and started integrating.
Successfully able to add plugin.
After SDK restarts, clicked on the Fabric toolbar button to start using Fabric!
Logged in -> Selected project -> selected kit to install.
Follow all the steps initiated by tools.
change of android-manifest file.
add code in the java class.
add shown code to kits.properties (Eg: com.crashlytics.sdk.android:crashlytics:2.2.2)
Final step will show you the done. (If you haven't done the three steps properly in step 6 then you can't be proceed further).
I downloaded the most recent version of Android for Linux (android-sdk_r05-linux_86.tgz). I was trying to use the the Android Ant task(s) for packaging, building, and deploying my code. I should mention that I'm running AMD64, but I have the 32-bit libraries installed. The Android Ant tasks are all broken.
First, the start-emulator task never gets the emulator running. It does get past starting adb, but then it just sits there.
Second, the SDK is missing the AAPT binary in the tools directory. So, the example notepad sample application will not even package correctly.
java.lang.IllegalStateException: Can't find aapt inside the sdk at /home/user/bin/android-sdk-linux_86
at com.googlecode.autoandroid.lib.AndroidTools.locateTool(AndroidTools.java:116)
at com.googlecode.autoandroid.lib.AndroidTools.startTool(AndroidTools.java:103)
at com.googlecode.autoandroid.lib.AndroidTools.startTool(AndroidTools.java:91)
at com.googlecode.autoandroid.lib.UnixAndroidTools.aapt(UnixAndroidTools.java:9)
I have all the dependencies configured for Android. I can run it from the command line just fine.
I assume the Ant code is out of sync with the recent SDK updates. Can anyone shed some light on this problem? At this point, I'm considering writing my own Python scripts to interact with the Android SDK. Ugh.
For anyone running into this recently, aapt moved again. It's now in $ANDROID_SDK/build-tools/17.0.0.
I have written three books all using the Android Ant build scripts. Trust me, they work.
First, the start-emulator task never
gets the emulator running. It does get
past starting adb, but then just sits
there.
Run the android command and launch the emulator from AVD Manager window that appears. AFAIK, there is no start-emulator task in Ant -- in fact, I'm not aware that there ever has been one.
Second, the SDK is missing the aapt
binary in the tools directory.
If you are looking in $ANDROID_HOME/tools/ (where $ANDROID_HOME is where you unpacked the SDK), you aren't supposed to find aapt there. That directory is for tools that directly support all API levels. API-level-specific tools, like aapt, will reside in $ANDROID_HOME/platforms/$SDK/tools/ (where $SDK is the name of some Android version, like android-2.1).
If you do not have anything in $ANDROID_HOME/platforms/, please follow step 4 of the installation instructions.