i got a little problem with installing my app on my smartphone. Its works normal when i am using the standart icon, but after changing the icon, Android studio starts the app on my smartphone normally, but i cant find the app in the app list.
What i am trying to say is that, I cant manually start the App, because its not showing on my Smartphone. Starting throuch Android studio works perfectly fine. I assume its because of my new icon, because the other work fine. I changed the Logo in the different Sizes and just exchanged the old icon with the new one.
Please post a snapshot of your code(xml,java and manifest), without which the forum is unable to help you.
You'll have to first update your icon in the drawable folder only then will you be able to use it in your app.
Related
I have only just started android programming, but I have a few basics programs working. Normally when I click run in Android Studio and choose my galaxy nexus as a running device, the app I'm running opens and is saved onto my device, so that I can open my program when I am not plugged into my computer.
However, now when I hit run, my program opens, but it is not saved onto my device.
This happened almost immediately after I changed my application label in my manifest file, but I'm not sure if that's related. Any help is appreciated!
Make sure that "deploy the APK" is selected in Run-> Edit Configurations
You have to set it at the new project screen. Its greyed out but theres a link next to it. Just click it. Its next to the Package name and that is the only .app extension you need to execute the apk.
I had the same issue. For me the problem was that the icon was not appearing on the screen but I found the app was actually stored on the device. I have installed NovaLauncher on a Meizu U20. I went to see the "Applications List" (tr. it. "Menu delle app"), I found my app icon there and I drag/dropped it on the screen.
Doing a routine update to an app and decided to update the launcher icon as I have done many times before. However, I'm getting a very strange bug which I had once before but can't remember how I resolved.
I have the right sized icons in each drawable folder and in the manifest the name is correct:
android:icon="#drawable/ic_launcher"
When I try to update the app the old icon remains, on a fresh installation the default launcher icon shows.
I've tried:
Cleaning the project
Restarting Eclipse
Restarting my computer
Restarting the device
A different device
Adding a new set of icons using the Android Icon Set function
Adding a new set using a different filename and changing the name in the manifest
One stange thing that is worth pointing out, if I delete the file ic_launcher.png from a drawable folder, then rename another file to that filename I get this error:
This shouldn't show as the file doesn't exist. This error then shows if I click continue:
Any ideas?
EDIT:
It appears this issue is even more complex than I thought. If I install an app on the emulator the icon appears just fine, on a device it doesn't. If I install the app onto physical devices from the apk, on one device the icon appears and on the other the Package installer crashes!
It seem this is caused by a bug in newer versions of Android. The icons are indeed included in the apk and upload just fine to Play, however it takes a reboot to get them to be shown on my devices (I was wrong above where I said a reboot doesn't work). This means I need to reboot the devices each time I try and new icon, not the end of the world but certainly frustrating.
This problem exists on two different apps I have been working on and two different Nexus devices, I think since they were updated to 5.0.
I've created a sample application (just a textview, nothing else), and I noticed a bug.
After installing it from the SDCard, it displays the "Application installed" screen, with the done and open buttons.
If I click the open button, a strange thing occurs:
Whenever I put the application in background and reopen it from the application icon, it doesn't reopen it, it creates a new instance.
I can confirm that it is creating a new instance, because after putting it on background and reopening a few times, when I click the back button, it opens the previous instance, instead of returning to the home screen.
Now the strange thing is that it only happens after installing from the SDCard and clicking on the open button.
If I click the done button (or installing via ADB) and open the application via icon, it doesn't happen.
Also, if I click the open button (and the bug occurs), after the application is ended for the first time, the bug doesn't occurs anymore.
I've tested it in different devices and in different Android versions (GB, HC and ICS), and the bug is reproducing in them all.
Does someone know if this is an known issue from Android and if so, does someone have an official reference that I can refer?
Thanks in advance
Yep, it is a nasty, well-known Android bug that has been around since the very beginning. See the following:
Android issue 26658
Android issue 2373
Android app acts differently installed from adb vs sdcard
I am trying to write an application with Mono for Android. In an attempt to do this, I'm using the default template in monodevelop. I can successfully compile and run the application. When I run the application, it looks similar to the one shown here: http://docs.xamarin.com/android/getting_started/hello_world
There are two oddities in my version though:
The button is red
I can't seem to actually click the button. When I use my computers mouse, it acts like it won't click the button. This is not limited to the application either. If I try to click the home or search button in the emulator itself, I noticed that nothing happens either. Its like the emulator is not responding to my mouse.
As someone new to working with Android, can someone please tell me what I'm doing wrong? I'm using MAC OS X with Lion installed. I'm assuming that I have the SDK and Java SDK installed properly considering the app compiles and when I press "play" I can load the app in the emulator. I just can't figure out why I can't actually click the button. So bizarre.
Any ideas?
The title of this question is pretty misleading, since you're saying that the emulator is not very responsive even outside the Mono for Android application. The problem here is with the emulator itself. The one thing I would recommend trying with respect to Mono for Android is to try starting the application without debugging, as debugging will add extra overhead to running the app.
The Android emulator is notoriously slow, since it is fully emulating the ARM instruction set in software. That said, there are certain things you can do in order to squeeze some more speed out of it. One thing that I've seen make a big difference is to decrease the screen size of the emulator image. Setting this to a small screen size (such as QVGA) can make a big difference. You can manage these settings through Android's AVD Manager.
So I've searched for an answer but found nothing. Basically, whenever I run a simple little menu app for android tablets using the eclipse android emulator 3.0, only about 1/6th of the app is shown (the top center piece, if the tablet is held landscape.) I've done tutorials using the 2.2 emulator and they work just fine, but whenever I launch the 3.0, the app (and only the app - the android home runs fine) just doesn't appear. When I look at it in the main.xml layout folder, the graphical layout shows it exactly the way I want it to appear.
Is this a problem with the emulator? This can't be a common problem, otherwise I'm sure I would have found a solution by now, but there must be some switch or something that I'm not seeing that's making the app appear as if it were running on a phone and not a tablet.
Do you have a low resolution set for your 3.0 AVD? If you run the AVD Manager, what resolution does it show?