I am wanting to create a simple app which will show some information on the Samsung S6s edge panel, and so I am starting to try to get the samsung exmaple running.
I've developed android application before (some time ago), but looking through the Samsung documentation I am lost, i'm sure i'm not the only one.
What I have tried so far
I have downloaded the samsung look sdk here: http://developer.samsung.com/galaxy#look
I can then import a project into eclipse from the samples called "EdgeScreenSampleApplication", and using android 19 I am able to compile it. However, I cannot run it on any emulator. I assume I need some special emulator to show the 'edge', but I cannot find one. When I run it on a Nexus emulator, I get:
[2015-03-21 21:01:33 - EdgeScreenSampleApplication] Installation error: Unknown failure
[2015-03-21 21:01:33 - EdgeScreenSampleApplication] Please check logcat output for more details.
[2015-03-21 21:01:33 - EdgeScreenSampleApplication] Launch canceled!
Now I am stuck, do I need a particular emulator? How can I get this thing running? I'd like to run it, then I can dig in to look at the code and see how it is working. Of course I do not have a Samsung S6 to test on as they are not yet released.
Related
Let me start by saying that i'm new to Xamarin/Cocossharp and game development in general.
I did a very basic game/application starting from the Cocossharp template for Shared application in VS2015. Now my app works well on WP (Emulator & Device) but wont start up on android.
After the emulator laoded this is what i get:
android 4.4 emulator
No Exception has been generated. I only get those errors in the output window, but they don't actually crash the application:
debug output
it looks like the Android version of the app doesn't go further than the class MainActivity.cs, which is generated by the template and should not be necessarily modified. Btw I have the same problem while trying to execute the examples from Xamarin.com
strugling with this issue since two days, help would be very appreciated!
This issue was already answered.
It was only necessary to set GPU emulation to true in Hardware properties of the virtual device.
The story is that I developed an Android program with Android 4.4.2. But some problems was found after installing the program to a device with Android 5.1.1. So I tried to download Android 5.1.1 for my SDK to debug the problem. Then the AVD I kept on using becomes like a mess no matter I changed to different configuration (see picture 1). My AVD configuration is as picture 2.
Hope someone could help... Thank you so much!
Picture 1
Picture 2
Got a temporary way to solve it and don't know if it is correct.
Set the skin to "no skin".
There is another problem happened now. The control bar of that window shows out of the screen. It makes the window cannot be moved. Anyway, I can continue my development job in this way...
I am using Eclipse to develop android applications. Initially the AVD used to run fine but when I launched it today, it just did not load. It just kept showing the blank screen with the word ANDROID glowing. I waited for quite a couple of minutes but it did not start. I even reinstalled my sdk but still no progress.
I am using Windows 7(32 bit) with 4 GB RAM.
Check virtual devices characteristics of your device created, sometimes if you choose a big resolution it doesn´t wokrs. check this.
also, I recommend you to use Android studio because eclipse is no longer used
I am using ubuntu 12.04,and Eclipse Platform Version: 3.7.2, I have one issue which i observed occasionally on my system I dont know whether this issue is common and did't find any related question so asked.. problem is - "when I tried to launch android application using emulator(API level 17 Nexus 4),it runs fine no problem and emulator is in front of me, But the moment i open other window like browser,editor it hides and i am not able to see it.." Log says that emulator is ruuning but dont know where it hide.
If someone else is facing this problem, it could be due to memory overwhelming. To solve, in Ubuntu, go to Home/.android/avd/Pixel_X_API_XX.avd
and delete the *lock files, then Run the emulator as usually.
Where I wrote Pixel_X_API_XX.avd it means, for example : Pixel_2_API_32.avd
Bye bye
I am trying to test my app on android emulator. So as soon as, i am choosing run the application, a new window pops up on the screen and after taking 1-2 minutes, it goes not responding.
I also tried running the emulator separately using AVD manager. Using this, i am able to start the emulator; but after 3-4 minutes - it goes "not responding".
OS- Windows 7 32 bit [ intel pentium 3.00 GHZ + 2GB RAM]
Java - 1.6
Android SDK - i have the latest SDK with 3.0 OS
IDE - eclipse Helios Service Release 2.
Plz help, i am unable to do anything.
Update: can you guys point me towards other 3rd party emulators which i can use?
Update2: My emulator is taking too much time in launching now. Can this be a cause? If yes, then how do i decrease the boot time?
(This isn't so much of an answer, but might go some way to figuring out the source of the problem; I'd comment on the original question instead but don't have enough rep to do so)
I keep having this problem too. I have an app with a few activities, one of which contains a layout with a Canvas which runs its own thread to do drawing processing. All of the activities run fine except for this Canvas activity which seems to crash the emulator in the way the OP described (the emulator .exe itself crashes rather than the application within the emulator) if left to run for a few minutes. As far as I can tell I'm not doing anything unusual with the thread - I copied the Lunar Landar example in the SDK and worked from that so I'm doing everything "by the book". The app runs fine on real devices.
So, while I realise the OP may be long gone, could anyone else with a similar problem confirm that the affected Activity is using a Canvas, drawing Thread, or anything like that? This problem is a real pain and I can't find any other discussions/solutions for the matter.
EDIT: I recently did a complete, clean re-install of the most recent versions of Eclipse and the Android SDK with all the updates and that seemed to solve the problem. Guess there was a bug in an older version of the emulator that was fixed in a more recent release.
Have you enabled snapshots. If you enabled it then you can be trying to open a incorrectly saved snapshot. If so, while starting the emulator with launch options, uncheck launch from startup
#mudit:remember Android 3.0(Honeycomb) is dedicated entirely to only tablets and not the mobile phones..
Does the emulator prompts you "not responding" in your app or when you just start the emulator without launching an app, too?
A strong advice: you don't need to restart the emulator for every app launch, just keep him running (maybe you already do that).
Does the logcat show some errors prior to the "not responding"? Have you tried creating another AVD?