We Keep Coding

Read-only file system in android studio

i try to open the camera with th opencv library using android studio but it is not opened and the message appeared was " it seems that your device does not support camera( or it is locked) application will be closed" on the emulator screen
this is my logcat
09-09 19:39:17.436 11223-11223/? E/libprocessgroup: failed to make and chown /acct/uid_10058: Read-only file system

Unfortunately, if you are using emulator, it will not allow writing a file to its file system, unless you use API ver 21 or below. (That's what I tried once and it works probably.)
AVD does support camera, try edit AVD -> Advanced parameters.

no show UI content for android after launching inspector in appium

I use the eclipse mars2 and appium 1.5.3 in mac 10.12 .
I have already configured in appium (android settings,iOS setting,general setting,developer setting).
I have configured app path,waith fo package,package,launch activity,platform nam,device name,platform version,automation name in adroid setting.
I have already changed server address(127.0.0.1) and port 4723 in general setting.
I have already checked enabled and custom server flag and enter input : --native-instuments-lib.
I use the emulator (CPU/ABI) ARM(armeabi-v7a).
I use the device Nexus5.
For my app,that emulator ARM can be run.
I have also configured in eclipse (install sdk,add ADT plugin,create emulator).
I use the android API Level 23 and android 6.0.
I can launch the inspector in appium.
But when I launch the inspector,application can run in emulator but not show UI in appium.

Try to update your appium version.
In some cases, the outdated version of appium could be the problem.

Android studio does not launch first try sometimes

When I change the code and try to lauch the app sometimes this happends:
Installing ...
Success
Launching application: ...
DEVICE SHELL COMMAND: ...
java.lang.UnsatisfiedLinkError: No implementation found for java.lang.String android.os.SystemProperties.native_get(java.lang.String) (tried Java_android_os_SystemProperties_native_1get and Java_android_os_SystemProperties_native_1get__Ljava_lang_String_2)
at android.os.SystemProperties.native_get(Native Method)
at android.os.SystemProperties.get(SystemProperties.java:52)
at com.htc.customization.HtcCustomizationManager.<init>(HtcCustomizationManager.java:65)
at com.htc.customization.HtcCustomizationManager.<clinit>(HtcCustomizationManager.java:60)
at android.os.Environment$UserEnvironment.getCustomizationReader(Environment.java:523)
at android.os.Environment$UserEnvironment.isDynamicSwitchSupported(Environment.java:534)
at android.os.Environment$UserEnvironment.<init>(Environment.java:222)
at android.os.Environment.initForCurrentUser(Environment.java:142)
at android.os.Environment.<clinit>(Environment.java:136)
at android.os.Environment.getLegacyExternalStorageDirectory(Environment.java:726)
at android.os.Debug.<clinit>(Debug.java:96)
at android.ddm.DdmHandleHello.handleHELO(DdmHandleHello.java:164)
at android.ddm.DdmHandleHello.handleChunk(DdmHandleHello.java:91)
at org.apache.harmony.dalvik.ddmc.DdmServer.dispatch(DdmServer.java:171)
java.lang.UnsatisfiedLinkError: android.os.Debug
at android.ddm.DdmHandleHello.handleFEAT(DdmHandleHello.java:176)
at android.ddm.DdmHandleHello.handleChunk(DdmHandleHello.java:93)
at org.apache.harmony.dalvik.ddmc.DdmServer.dispatch(DdmServer.java:171)
java.lang.UnsatisfiedLinkError: android.os.Debug
at android.ddm.DdmHandleProfiling.handleMPRQ(DdmHandleProfiling.java:215)
at android.ddm.DdmHandleProfiling.handleChunk(DdmHandleProfiling.java:106)
at org.apache.harmony.dalvik.ddmc.DdmServer.dispatch(DdmServer.java:171)
Aborted
And the app does not lauch unless I rebuild the solution - then it launches fine
This is not that serious but very annoying as it happens once every 3-4 builds
What is wrong?

You probably have and HTC phone (M8 I'd guess) with HTC Sense. There is a bug in their code which prevents you from installing the app sometimes. Here's relevant question and answer from HTCdev FAQ:
Why does my debug APK sometimes fail to install or run on my device
and how to recover?
HTC devices with Lollipop 5.0.0 or 5.0.1 may experience this issue and
we suggest retrying the installation step for workaround. HTC will
prepare the solution to address the issue on Lollipop MR1.
So, nothing you can do but to wait for Android update. Since HTC backed off from pushing Lollipop MR1, you will have to wait for Marshmallow update.

Running applicatiom from eclipse causing phone restart

im using eclipse to develop android app.
Im debugging my app on real device, htc desire hd.
When i start my app from eclipse its allways restart my phone.
This behavior wasnt allways like this and suddenly happaned.
I tried 3 different ROMs all 4.2.2 and its happing in all of them.
In my log cat i dont see any errors except this in my console:
[2013-09-05 21:25:33 - WorkoutLog2] Failed to install WorkoutLog2.apk on device 'HT0BRRX047774!
[2013-09-05 21:25:33 - WorkoutLog2] (null)
[2013-09-05 21:25:33 - WorkoutLog2] Launch failed on device: HT0BRRX047774
Why this is happening?

Android Emulator is not responding to program

Ok Folks I decided to try this developer thing, and after about a dozen tutorials, ended up with the following Hello World type program:
package com.example.helloandroid;
import android.app.Activity;
import android.os.Bundle;
import android.widget.TextView;
public class HelloAndroid extends Activity {
/** Called when the activity is first created. */
#Override
public void onCreate(Bundle savedInstanceState) {
super.onCreate(savedInstanceState);
TextView tv = new TextView(this);
tv.setText("Hello, Android");
setContentView(tv);}
}
Simple enough, So I go to compile it and I get this
[2011-03-14 00:11:25 - HelloAndroid] Android Launch!
[2011-03-14 00:11:25 - HelloAndroid] adb is running normally.
[2011-03-14 00:11:25 - HelloAndroid] Performing com.example.helloandroid.HelloAndroid activity launch
[2011-03-14 00:11:25 - HelloAndroid] Automatic Target Mode: launching new emulator with compatible AVD 'my_avd'
[2011-03-14 00:11:25 - HelloAndroid] Launching a new emulator with Virtual Device 'my_avd'
[2011-03-14 00:11:30 - HelloAndroid] New emulator found: emulator-5554
[2011-03-14 00:11:30 - HelloAndroid] Waiting for HOME ('android.process.acore') to be launched...
Or if I have the emulator already up, I get this
[2011-03-14 08:23:09 - HelloAndroid] Android Launch!
[2011-03-14 08:23:09 - HelloAndroid] adb is running normally.
[2011-03-14 08:23:09 - HelloAndroid] Performing com.example.helloandroid.HelloAndroid activity launch
[2011-03-14 08:23:09 - HelloAndroid] Automatic Target Mode: using existing emulator 'emulator-5554' running compatible AVD 'my_avd'
[2011-03-14 08:23:09 - HelloAndroid] WARNING: Application does not specify an API level requirement!
[2011-03-14 08:23:09 - HelloAndroid] Device API version is 7 (Android 2.1-update1)
[2011-03-14 08:23:09 - HelloAndroid] Uploading HelloAndroid.apk onto device 'emulator-5554'
[2011-03-14 08:23:09 - HelloAndroid] Installing HelloAndroid.apk...
[2011-03-14 08:23:26 - HelloAndroid] Success!
[2011-03-14 08:23:27 - HelloAndroid] Starting activity com.example.helloandroid.HelloAndroid on device emulator-5554
And then the emulator comes up everytime with just this blank screen, with the text "android" on it. And it sits there for about 3 minutes until it goes to another blank black screen with "android" except its animated. I have looked around and can't seem to find anyone who has the same problem. Its like the emulator does not even recognize anything I am doing. Here is a nice screenshot of the blank nothingness:
So, any ideas what I did wrong?

Try waiting for the emulator to load everything before lunching your app.

That's the startup screen for the emulator... It takes a while to boot the emulator, but once it is up and running, it should fire up your application.
The first typed font is the bootstrapping stage, and then the animated version is when it is loading the OS. The next screen should be your Android platform with a GUI.

I too had the same issue.
The program should be executed only after the emulator is ready to run it. So wen u open eclipse press the run button and wait for some time. This will indirectly start the emulator. Once it is loaded press the run button again, this time to run the program.

I had this issue too. My problem was the SDK version. I installed versions 3.1, 3.2 and 2.2 on my Eclipse and I created 3 different target machines. SDK versions 3.1 and 3.2 did not work whereas version 2.2 did go through. I guess there is no stable emulator for SDK 3.*. If you really need to use such a SDK version you might consider using an actual device. My system: Ubuntu 10.04 running Eclipse 3.5.2.
Hope this helps.

when you open the eclipse then go the run tab and run the emulator and appears the GUI screens in emulator then run the application.and then here after use the same emulator dont close.it take a more time to run the emulator. if your system slow.

Try using Genymotion. You can download a version for Windows/Mac OS X/Linux after registering. A plugin for Eclipse is also avaliable.
i give you link Genymotion Emulator please download and setup.
as per my experience Genymotion Vertual device is faster then android emulator.

after you get result
HelloAndroid] Starting activity com.example.helloandroid.HelloAndroid on device emulator-5554
on you console
click on menu button and try to see output