[android-developers] Re: Bluetooth devices is pairing but not connecting

2012-04-29 Thread hüseyin toplu
i found my problem problem  have server code
  tmp = mAdapter.listenUsingRfcommWithServiceRecord(NAME_SECURE,
MY_UUID_SECURE);
} else {
tmp = mAdapter.listenUsingRfcommWithServiceRecord(
NAME_INSECURE, MY_UUID_INSECURE);
}
} catch (IOException e) {}

Problem is uuid because I dont know other device uuid.i dont send file
to my application i wanna just send file over bluettooth to any device

i chanced this code with this
m = mAdapter.getClass().getMethod("listenUsingRfcommOn", new Class[]
{ int.class });
tmp = (BluetoothServerSocket) 
m.invoke(mAdapter, 1);
} catch (SecurityException e) {

e.printStackTrace();
} catch (Exception e) {
e.printStackTrace();
}
it send java.lang.reflect.invocationtargetexception erorr please
help :S

-- 
You received this message because you are subscribed to the Google
Groups "Android Developers" group.
To post to this group, send email to android-developers@googlegroups.com
To unsubscribe from this group, send email to
android-developers+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/android-developers?hl=en


[android-developers] Re: Strange force close on Froyo phone, works fine on ICS tablet

2012-04-29 Thread Alger Lin
I release a tool to help developer to dump API from Android device. This 
tool may help you to check if class, method, or field existed at target 
device.

You can get it from Google Play by URL below.
http://market.android.com/details?id=com.twrd.yulin.classminer

-- 
You received this message because you are subscribed to the Google
Groups "Android Developers" group.
To post to this group, send email to android-developers@googlegroups.com
To unsubscribe from this group, send email to
android-developers+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/android-developers?hl=en

Re: [android-developers] play sound file

2012-04-29 Thread asheesh arya
try to install apk accurately in your mobile device then test it

-- 
You received this message because you are subscribed to the Google
Groups "Android Developers" group.
To post to this group, send email to android-developers@googlegroups.com
To unsubscribe from this group, send email to
android-developers+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/android-developers?hl=en

Re: [android-developers] How to force quit a Thread

2012-04-29 Thread Kristopher Micinski
read this:

http://docs.oracle.com/javase/1.5.0/docs/guide/misc/threadPrimitiveDeprecation.html

On Mon, Apr 30, 2012 at 12:33 AM, Matt Clark  wrote:
> What do you mean use flags?
> The app hangs on lines that wait for an HTTP response, so i want to be able
> to just cut them off mid execution if I have to, i cant call check
> statements before and after.
> Sorry, I do not know a whole lot about Threading.
>
>
> On Monday, April 30, 2012 12:09:25 AM UTC-4, Ankita wrote:
>>
>> stop(),destroy() etc. methods were deprecated by JDK versions, so must
>> have not got support now. To stop thread, you should try to use flags,
>> AFAIK.
>>
>> On Mon, Apr 30, 2012 at 9:34 AM, Matt Clark 
>> wrote:
>>>
>>> I am creating an app that sends various HTTP requests in seperate
>>> threads, while doing so brings up a loading screen. If the network request
>>> is taking longer then the user expects, I want them to be able to press the
>>> back button to force quit the thread, and dismiss the loading screen.
>>> I have my thread set up as:
>>>
>>> dataThread = new Thread(new Runnable() {
>>> public void run() {
>>> //...
>>> //Networking Data and Handlers
>>> //...
>>> }
>>> });
>>> dataThread.start();
>>>
>>> and where I want to force quit at onBackPressed() I have tried:
>>>
>>> dataThread.stop();
>>> dataThread.destroy();
>>> dataThread.interrupt();
>>>
>>> And none of them work, Android does not support stop(), or destroy(), and
>>> interrupt() does nothing to stop the thread. I do not care about exceptions
>>> as everything will be caught, I just want it to allow the user to resume
>>> doing what they want, if it hangs on requests, or even retry the request..
>>>
>>> Any and all help is greatly appreciated.
>>> ~Matt
>>>
>>> --
>>> You received this message because you are subscribed to the Google
>>> Groups "Android Developers" group.
>>> To post to this group, send email to android-developers@googlegroups.com
>>> To unsubscribe from this group, send email to
>>> android-developers+unsubscr...@googlegroups.com
>>> For more options, visit this group at
>>> http://groups.google.com/group/android-developers?hl=en
>>
>>
> --
> You received this message because you are subscribed to the Google
> Groups "Android Developers" group.
> To post to this group, send email to android-developers@googlegroups.com
> To unsubscribe from this group, send email to
> android-developers+unsubscr...@googlegroups.com
> For more options, visit this group at
> http://groups.google.com/group/android-developers?hl=en

-- 
You received this message because you are subscribed to the Google
Groups "Android Developers" group.
To post to this group, send email to android-developers@googlegroups.com
To unsubscribe from this group, send email to
android-developers+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/android-developers?hl=en


Re: [android-developers] How to force quit a Thread

2012-04-29 Thread Matt Clark
What do you mean use flags?
The app hangs on lines that wait for an HTTP response, so i want to be able 
to just cut them off mid execution if I have to, i cant call check 
statements before and after.
Sorry, I do not know a whole lot about Threading.

On Monday, April 30, 2012 12:09:25 AM UTC-4, Ankita wrote:
>
> stop(),destroy() etc. methods were deprecated by JDK versions, so must 
> have not got support now. To stop thread, you should try to use flags, 
> AFAIK.
>
> On Mon, Apr 30, 2012 at 9:34 AM, Matt Clark wrote:
>
>> I am creating an app that sends various HTTP requests in seperate 
>> threads, while doing so brings up a loading screen. If the network request 
>> is taking longer then the user expects, I want them to be able to press the 
>> back button to force quit the thread, and dismiss the loading screen.
>> I have my thread set up as:
>>
>> dataThread = new Thread(new Runnable() {
>> public void run() {
>> //...
>>  //Networking Data and Handlers
>> //...
>> }
>> });
>> dataThread.start();
>>
>> and where I want to force quit at onBackPressed() I have tried:
>>
>> dataThread.stop();
>> dataThread.destroy();
>> dataThread.interrupt();
>>
>> And none of them work, Android does not support stop(), or destroy(), and 
>> interrupt() does nothing to stop the thread. I do not care about exceptions 
>> as everything will be caught, I just want it to allow the user to resume 
>> doing what they want, if it hangs on requests, or even retry the request..
>>
>> Any and all help is greatly appreciated.
>> ~Matt
>>
>> -- 
>> You received this message because you are subscribed to the Google
>> Groups "Android Developers" group.
>> To post to this group, send email to android-developers@googlegroups.com
>> To unsubscribe from this group, send email to
>> android-developers+unsubscr...@googlegroups.com
>> For more options, visit this group at
>> http://groups.google.com/group/android-developers?hl=en
>
>
>

-- 
You received this message because you are subscribed to the Google
Groups "Android Developers" group.
To post to this group, send email to android-developers@googlegroups.com
To unsubscribe from this group, send email to
android-developers+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/android-developers?hl=en

Re: [android-developers] How to force quit a Thread

2012-04-29 Thread Kristopher Micinski
That's right, use the flags and catch the interrupted exception..

don't use stop().

This is a huge antipattern..

kris

On Mon, Apr 30, 2012 at 12:09 AM, Ankita Kashyap
 wrote:
> stop(),destroy() etc. methods were deprecated by JDK versions, so must have
> not got support now. To stop thread, you should try to use flags, AFAIK.
>
>
> On Mon, Apr 30, 2012 at 9:34 AM, Matt Clark  wrote:
>>
>> I am creating an app that sends various HTTP requests in seperate threads,
>> while doing so brings up a loading screen. If the network request is taking
>> longer then the user expects, I want them to be able to press the back
>> button to force quit the thread, and dismiss the loading screen.
>> I have my thread set up as:
>>
>> dataThread = new Thread(new Runnable() {
>> public void run() {
>> //...
>> //Networking Data and Handlers
>> //...
>> }
>> });
>> dataThread.start();
>>
>> and where I want to force quit at onBackPressed() I have tried:
>>
>> dataThread.stop();
>> dataThread.destroy();
>> dataThread.interrupt();
>>
>> And none of them work, Android does not support stop(), or destroy(), and
>> interrupt() does nothing to stop the thread. I do not care about exceptions
>> as everything will be caught, I just want it to allow the user to resume
>> doing what they want, if it hangs on requests, or even retry the request..
>>
>> Any and all help is greatly appreciated.
>> ~Matt
>>
>> --
>> You received this message because you are subscribed to the Google
>> Groups "Android Developers" group.
>> To post to this group, send email to android-developers@googlegroups.com
>> To unsubscribe from this group, send email to
>> android-developers+unsubscr...@googlegroups.com
>> For more options, visit this group at
>> http://groups.google.com/group/android-developers?hl=en
>
>
> --
> You received this message because you are subscribed to the Google
> Groups "Android Developers" group.
> To post to this group, send email to android-developers@googlegroups.com
> To unsubscribe from this group, send email to
> android-developers+unsubscr...@googlegroups.com
> For more options, visit this group at
> http://groups.google.com/group/android-developers?hl=en

-- 
You received this message because you are subscribed to the Google
Groups "Android Developers" group.
To post to this group, send email to android-developers@googlegroups.com
To unsubscribe from this group, send email to
android-developers+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/android-developers?hl=en


Re: [android-developers] How to force quit a Thread

2012-04-29 Thread Ankita Kashyap
stop(),destroy() etc. methods were deprecated by JDK versions, so must have
not got support now. To stop thread, you should try to use flags, AFAIK.

On Mon, Apr 30, 2012 at 9:34 AM, Matt Clark  wrote:

> I am creating an app that sends various HTTP requests in seperate threads,
> while doing so brings up a loading screen. If the network request is taking
> longer then the user expects, I want them to be able to press the back
> button to force quit the thread, and dismiss the loading screen.
> I have my thread set up as:
>
> dataThread = new Thread(new Runnable() {
> public void run() {
> //...
> //Networking Data and Handlers
> //...
> }
> });
> dataThread.start();
>
> and where I want to force quit at onBackPressed() I have tried:
>
> dataThread.stop();
> dataThread.destroy();
> dataThread.interrupt();
>
> And none of them work, Android does not support stop(), or destroy(), and
> interrupt() does nothing to stop the thread. I do not care about exceptions
> as everything will be caught, I just want it to allow the user to resume
> doing what they want, if it hangs on requests, or even retry the request..
>
> Any and all help is greatly appreciated.
> ~Matt
>
> --
> You received this message because you are subscribed to the Google
> Groups "Android Developers" group.
> To post to this group, send email to android-developers@googlegroups.com
> To unsubscribe from this group, send email to
> android-developers+unsubscr...@googlegroups.com
> For more options, visit this group at
> http://groups.google.com/group/android-developers?hl=en

-- 
You received this message because you are subscribed to the Google
Groups "Android Developers" group.
To post to this group, send email to android-developers@googlegroups.com
To unsubscribe from this group, send email to
android-developers+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/android-developers?hl=en

[android-developers] How to force quit a Thread

2012-04-29 Thread Matt Clark
I am creating an app that sends various HTTP requests in seperate threads, 
while doing so brings up a loading screen. If the network request is taking 
longer then the user expects, I want them to be able to press the back 
button to force quit the thread, and dismiss the loading screen.
I have my thread set up as:

dataThread = new Thread(new Runnable() {
public void run() {
//...
//Networking Data and Handlers
//...
}
});
dataThread.start();

and where I want to force quit at onBackPressed() I have tried:

dataThread.stop();
dataThread.destroy();
dataThread.interrupt();

And none of them work, Android does not support stop(), or destroy(), and 
interrupt() does nothing to stop the thread. I do not care about exceptions 
as everything will be caught, I just want it to allow the user to resume 
doing what they want, if it hangs on requests, or even retry the request..

Any and all help is greatly appreciated.
~Matt

-- 
You received this message because you are subscribed to the Google
Groups "Android Developers" group.
To post to this group, send email to android-developers@googlegroups.com
To unsubscribe from this group, send email to
android-developers+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/android-developers?hl=en

[android-developers] Re: Android application StartUp Internals

2012-04-29 Thread Mansoor


Thanks Nadeem I Understood.

When i checked setContentView() API i found that a new instance of
Window is getting created so if there is already a default window then
why new instance of window getting created on call this method?

Regards
Mansoor V.M

-- 
You received this message because you are subscribed to the Google
Groups "Android Developers" group.
To post to this group, send email to android-developers@googlegroups.com
To unsubscribe from this group, send email to
android-developers+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/android-developers?hl=en


[android-developers] Re: Strange force close on Froyo phone, works fine on ICS tablet

2012-04-29 Thread Jim Graham
I was wrong about one point here, so this post is to correct that error.
Sorry.  But now, the plot thickens (maybe)

On Sun, Apr 29, 2012 at 11:45:34AM -0500, Jim Graham wrote:
> The following code (which works fine earlier in the app on both devices)

I was WRONG about this point!  It does NOT work earlier in the code on my
MB520 phone (Froyo).  I wasn't thinking about the fact that the
PorterDuff merge is in the method that blends filters ... but ONLY if
MORE THAN ONE filter is used.  I re-did that test, using TWO filters,
and it gave me the same force close.  Now I have to wonder if I did the
test the right way before, or did I just apply one filter.

Just to be sure, I re-did the test on my Acer A500 (ICS), as well.  It,
as it has done all along, worked fine with multiple filters.

I just thought of something:  could this have anything to do with
Eclipse's claim that android.graphics.PorterDuff and a.g.P.Modes are
never used?

> causes a force close (logcat below) on my Froyo phone (Motorola Bravo
> MB520), and works fine on my ICS tablet (Acer Iconia A500):
> 
> ---  CUT HERE  ---
> Canvas canvas = new Canvas(saveme);
> Paint paint = new Paint();
> 
> canvas = new Canvas(saveme);
> paint = new Paint();
> canvas.drawBitmap(image, 0, 0, paint);
> // the following is line 1071...the source of the exception/error
> paint.setXfermode(new 
> PorterDuffXfermode(android.graphics.PorterDuff.Mode.ADD));
> canvas.drawBitmap(filter, 0, 0, paint);
> ---  CUT HERE  ---
> 
> And here's the error in logcat:
> 
> ---  CUT HERE  ---
> D/AndroidRuntime(3550): Shutting down VM
> W/dalvikvm(3550): threadid=1: thread exiting with uncaught exception 
> (group=0x400208b0)
> E/AndroidRuntime(3550): FATAL EXCEPTION: main
> E/AndroidRuntime(3550): java.lang.NoSuchFieldError: 
> android.graphics.PorterDuff$Mode.ADD
> E/AndroidRuntime(3550):at 
> com.jdgapps.UltraCamPro.UltraCamPro$1.onPictureTaken(UltraCamPro.java:1071)
> E/AndroidRuntime(3550):at 
> android.hardware.Camera$EventHandler.handleMessage(Camera.java:330)
> E/AndroidRuntime(3550):at 
> android.os.Handler.dispatchMessage(Handler.java:99)
> E/AndroidRuntime(3550):at android.os.Looper.loop(Looper.java:143)
> E/AndroidRuntime(3550):at 
> android.app.ActivityThread.main(ActivityThread.java:4717)
> E/AndroidRuntime(3550):at java.lang.reflect.Method.invokeNative(Native 
> Method)
> E/AndroidRuntime(3550):at java.lang.reflect.Method.invoke(Method.java:521)
> E/AndroidRuntime(3550):at 
> com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:860)
> E/AndroidRuntime(3550):at 
> com.android.internal.os.ZygoteInit.main(ZygoteInit.java:618)
> E/AndroidRuntime(3550):at dalvik.system.NativeStart.main(Native Method)
> W/ActivityManager(1321):   Force finishing activity 
> com.jdgapps.UltraCamPro/.UltraCamPro
>  ---  CUT HERE  ---
>  
> On my tablet, it doesn't throw an error, and continues on to create the
> final image, save it, and return to the camera preview.  Note that this
> very same Porterduff code works fine earlier in the app (also blending
> two bitmaps---different variable names...only difference), and also WAS
> working at this point previously (before a name change, some unused
> imports removed, two[1] that Eclipse said were unused replaced because
> Eclipse complained when they weren't there after I removed them because
> Eclipse said they weren't used).  Oh, one more change:  Target SDK
> stepped up from Android 3.2.1 to Android 4.0.3, min SDK stayed at Android
> 2.2.1.  Tablet also changed from Android 3.2.1 to 4.0.3.
> 
> Can anyone help explain this mystery?
> 
> Thanks,
>--jim
> 
> 
> [1] android.graphics.PorterDuff and android.graphics.PorterDuff.Mode
> 
> -- 
> THE SCORE:  ME:  2  CANCER:  0
> 73 DE N5IAL (/4)| Peter da Silva:  No, try "rm -rf /"
> spooky1...@gmail.com| Dave Aronson:As your life flashes before
> < Running FreeBSD 7.0 > |  your eyes, in the unit of time known as an
> ICBM / Hurricane:   |  ohnosecond (alt.sysadmin.recovery)
>30.44406N 86.59909W  |
> 
> Android Apps Listing at http://www.jstrack.org/barcodes.html

-- 
THE SCORE:  ME:  2  CANCER:  0
73 DE N5IAL (/4)MiSTie #49997  < Running FreeBSD 7.0 >
spooky1...@gmail.comICBM/Hurr.: 30.44406N 86.59909W

   Saw something on TV about Psych-os.
 H, Psych OS.  Perhaps the next freeware OS   --me

Android Apps Listing at http://www.jstrack.org/barcodes.html

-- 
You received this message because you are subscribed to the Google
Groups "Android Developers" group.
To post to this group, send email to android-developers@googlegroups.com
To unsubscribe from this group, send email to
android-developers+unsubscr...@googlegroups.com
For 

[android-developers] Preserving Compound Control View State Across Configuration Changes

2012-04-29 Thread Casvah
I have a compound control containing an AutoCompleteTextView, a CheckBox, 
and an ImageButton. The layout is inflated from xml. The control is added 
added at runtime to a linearlayout when a user clicks an 'Add' button.

I need to preserve the values of the textview and the checkbox across 
configuration changes, so I implement the following INSIDE the compound 
control class.

@Override
protected Parcelable onSaveInstanceState() {
// Create a bundle to save our state in
Bundle b = new Bundle();
// Save the superclass' instanceState
b.putParcelable("instanceState", super.onSaveInstanceState());

// Save the AutoCompleteTextView
AutoCompleteTextView acTextView = (AutoCompleteTextView) 
findViewById(R.id.houseEditFragmentProConView_autoCompleteTextView1);
b.putString("acTextView", acTextView.getText().toString());

// Save the CheckBox
CheckBox cb = (CheckBox) 
findViewById(R.id.houseEditFragmentProConView_checkBox1);
b.putBoolean("cb", cb.isChecked());

// Return the saved state
return b;
}

@Override
protected void onRestoreInstanceState(Parcelable state) {
if (state instanceof Bundle) {
Bundle b = (Bundle) state;
AutoCompleteTextView acTextView = (AutoCompleteTextView) 
findViewById(R.id.houseEditFragmentProConView_autoCompleteTextView1);
acTextView.setText(b.getString("acTextView"));
CheckBox cb = (CheckBox) 
findViewById(R.id.houseEditFragmentProConView_checkBox1);
cb.setChecked(b.getBoolean("cb"));
super.onRestoreInstanceState(b.getParcelable("instanceState"));
return;
}
super.onRestoreInstanceState(state);
}

When I change the orientation of the screen, ALL of these controls are 
lost. So I overrode the fragment's onSaveInstanceState method with a loop 
to store all of the control.getid()'s in an ArrayList. Then in the 
fragment's onViewCreated method, I loop through that arrayList (extracted 
from the bundle), and create a control for each id in the arraylist, and 
set that id on it before adding it to the containing view.

As I understand it, if you recreate a control and give it the same ID as a 
control that was destroyed in an orientation change, Android will refill 
the data it had. My problem is that even though all the controls show back 
up and have data in them, they all have the SAME data as the LAST control 
that was stored, instead of having their individual unique datas.

How can I fix this? Relevant portions from the fragment posted below:

@Override
public void onViewCreated(View view, Bundle savedInstanceState) {

super.onViewCreated(view, savedInstanceState);

LinearLayout prosConsView = (LinearLayout) getSherlockActivity()
.findViewById(R.id.houseEditFragment_linearLayout_Pros);
if (savedInstanceState == null) {
buttonAdd.performClick();

EditText editTextAddress = (EditText) getSherlockActivity()
.findViewById(R.id.houseEditFragment_editText_Address);
editTextAddress.requestFocus();
} else {
// TODO: Restore fragment from savedInstanceState in case of
// orientation
// change or if this gets killed
ArrayList recoveredProsConsIds = savedInstanceState
.getIntegerArrayList("prosConsIds");
Log.d(LocalApplication.DEBUG_TAG, "RECOVERED ARRAY: "
+ recoveredProsConsIds);

HouseEditFragmentProConView workingProConView;
for (Integer id : recoveredProsConsIds) {
workingProConView = new HouseEditFragmentProConView(
getSherlockActivity(), null);
workingProConView.setId(id);
Log.d(LocalApplication.DEBUG_TAG, "Restore: "
+ workingProConView.getId() + " " + workingProConView.getText().toString());
prosConsView.addView(workingProConView);
}

for (int i = 0; i < prosConsView.getChildCount(); i++) {
workingProConView = (HouseEditFragmentProConView) prosConsView
.getChildAt(i);
Log.d(LocalApplication.DEBUG_TAG,
"Check: " + workingProConView.getId() + " " + 
workingProConView.getText().toString());
}
}

}

@Override
public void onSaveInstanceState(Bundle outState) {
// TODO Save the form in case of configuration change or if the user
// changes apps and this gets killed
// EditText address = (EditText)
// 
getSherlockActivity().findViewById(R.id.houseEditFragment_editText_Address);
// outState.putString("address", address.getText().toString());

LinearLayout prosCons = (LinearLayout) getSherlockActivity()
.findViewById(R.id.houseEditFragment_linearLayout_Pros);
ArrayList storedProsConsIds = new ArrayList();
for (int i = 0; i < prosCons.getChildCount(); i++) {

HouseEditFragmentProConView current = (HouseEditFragmentProConView) prosCons
.getChildAt(i);
storedProsConsIds.add(current.getId());
Log.d(LocalApplication.DEBUG_TAG, "Save: " + current.getId() + " " + 
current.getText().toString());
}
outState.putIntegerArrayList("prosConsIds", storedProsConsIds);
super.onSaveInstanceState(outState);
}

-- 
You received this message because you are subscribed to the Google
Groups "Android Developers" group.
To post to this group, send email to android-developers@googlegroups.com
To unsubscribe from this group, send email to
android-developers+unsubscr...@googlegroups.com
For more options, visit this group at
ht

[android-developers] Import Project form excisting source

2012-04-29 Thread Marcus Maximus
Hey guys,

I want to import the soultion Projects from that source:
developer.android.com/resources/tutorials/notepad/codelab/
NotepadCodeLab.zip

into my eclipse. So I am doing:

File-> New-> Android Project and then create project from existing
source and then I just pick the for example notepads2 BUT I do not get
the hole import!

For example the source is missing and the AndroidManifest file...

What am I doing wrong and how can I import an existing project in
eclipse that it works?

greetings and thx in advance

-- 
You received this message because you are subscribed to the Google
Groups "Android Developers" group.
To post to this group, send email to android-developers@googlegroups.com
To unsubscribe from this group, send email to
android-developers+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/android-developers?hl=en


[android-developers] Forced Close for Googles Notepad Exercise 2

2012-04-29 Thread Marcus Maximus
Hey guys,

i am doing that 
http://developer.android.com/resources/tutorials/notepad/notepad-ex2.html.
But when I want to run it on Android 2.2 emulator I get an error:

Here is the log file:
04-29 19:58:24.561: I/Process(336): Sending signal. PID: 336 SIG: 9
04-29 19:58:28.651: W/KeyCharacterMap(344): No keyboard for id 0
04-29 19:58:28.651: W/KeyCharacterMap(344): Using default keymap: /
system/usr/keychars/qwerty.kcm.bin
04-29 19:58:29.791: D/AndroidRuntime(344): Shutting down VM
04-29 19:58:29.791: W/dalvikvm(344): threadid=1: thread exiting with
uncaught exception (group=0x4001d800)
04-29 19:58:29.821: E/AndroidRuntime(344): FATAL EXCEPTION: main
04-29 19:58:29.821: E/AndroidRuntime(344):
android.content.ActivityNotFoundException: Unable to find explicit
activity class {com.notepad2/com.notepad2.NoteEdit}; have you declared
this activity in your AndroidManifest.xml?
04-29 19:58:29.821: E/AndroidRuntime(344): at
android.app.Instrumentation.checkStartActivityResult(Instrumentation.java:
1404)
04-29 19:58:29.821: E/AndroidRuntime(344): at
android.app.Instrumentation.execStartActivity(Instrumentation.java:
1378)
04-29 19:58:29.821: E/AndroidRuntime(344): at
android.app.Activity.startActivityForResult(Activity.java:2817)
04-29 19:58:29.821: E/AndroidRuntime(344): at
com.notepad2.Notepad2Activity.createNote(Notepad2Activity.java:111)
04-29 19:58:29.821: E/AndroidRuntime(344): at
com.notepad2.Notepad2Activity.onMenuItemSelected(Notepad2Activity.java:
83)
04-29 19:58:29.821: E/AndroidRuntime(344): at
com.android.internal.policy.impl.PhoneWindow.onMenuItemSelected(PhoneWindow.java:
730)
04-29 19:58:29.821: E/AndroidRuntime(344): at
com.android.internal.view.menu.MenuItemImpl.invoke(MenuItemImpl.java:
143)
04-29 19:58:29.821: E/AndroidRuntime(344): at
com.android.internal.view.menu.MenuBuilder.performItemAction(MenuBuilder.java:
855)
04-29 19:58:29.821: E/AndroidRuntime(344): at
com.android.internal.view.menu.IconMenuView.invokeItem(IconMenuView.java:
532)
04-29 19:58:29.821: E/AndroidRuntime(344): at
com.android.internal.view.menu.IconMenuItemView.performClick(IconMenuItemView.java:
122)
04-29 19:58:29.821: E/AndroidRuntime(344): at android.view.View
$PerformClick.run(View.java:8816)
04-29 19:58:29.821: E/AndroidRuntime(344): at
android.os.Handler.handleCallback(Handler.java:587)
04-29 19:58:29.821: E/AndroidRuntime(344): at
android.os.Handler.dispatchMessage(Handler.java:92)
04-29 19:58:29.821: E/AndroidRuntime(344): at
android.os.Looper.loop(Looper.java:123)
04-29 19:58:29.821: E/AndroidRuntime(344): at
android.app.ActivityThread.main(ActivityThread.java:4627)
04-29 19:58:29.821: E/AndroidRuntime(344): at
java.lang.reflect.Method.invokeNative(Native Method)
04-29 19:58:29.821: E/AndroidRuntime(344): at
java.lang.reflect.Method.invoke(Method.java:521)
04-29 19:58:29.821: E/AndroidRuntime(344): at
com.android.internal.os.ZygoteInit
$MethodAndArgsCaller.run(ZygoteInit.java:868)
04-29 19:58:29.821: E/AndroidRuntime(344): at
com.android.internal.os.ZygoteInit.main(ZygoteInit.java:626)
04-29 19:58:29.821: E/AndroidRuntime(344): at
dalvik.system.NativeStart.main(Native Method)

What am I doing wrong ?

greetings and thx in advance

-- 
You received this message because you are subscribed to the Google
Groups "Android Developers" group.
To post to this group, send email to android-developers@googlegroups.com
To unsubscribe from this group, send email to
android-developers+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/android-developers?hl=en


Re: [android-developers] Reading ROM version through code

2012-04-29 Thread JP
Hey guys... 

This code works... although I'm not that keen on it, since it is definitely 
not part of the jars available. But it works:

@Override
public void onCreate(Bundle savedInstanceState)
{
super.onCreate(savedInstanceState);
setContentView(R.layout.main);
TextView arch = (TextView)findViewById(R.id.arch);
TextView name = (TextView)findViewById(R.id.name);
TextView version = (TextView)findViewById(R.id.version);
TextView roversion = (TextView)findViewById(R.id.roversion);
TextView rofingerprint = (TextView)findViewById(R.id.rofingerprint);
arch.setText("os.arch: " + System.getProperty("os.arch"));
name.setText("os.name: " + System.getProperty("os.name"));
version.setText("os.version: " + System.getProperty("os.version"));
roversion.setText("ro.product.version: " + 
getProp("ro.product.version", "Not found"));
rofingerprint.setText("ro.build.fingerprint: " + 
getProp("ro.build.fingerprint", "Not found"));

}

private String getProp(String prop, String defaultVal)
{
String line = defaultVal;
try {
Process ifc = Runtime.getRuntime().exec("getprop " + prop);
BufferedReader bis = new BufferedReader(new 
InputStreamReader(ifc.getInputStream()));
line = bis.readLine();
ifc.destroy();
} catch (java.io.IOException e) {
}

return line;
}

This returns:

TextView arch = (TextView)findViewById(R.id.arch);
TextView name = (TextView)findViewById(R.id.name);
TextView version = (TextView)findViewById(R.id.version);
TextView roversion = (TextView)findViewById(R.id.roversion);
TextView rofingerprint = (TextView)findViewById(R.id.rofingerprint);
arch.setText("os.arch: " + System.getProperty("os.arch"));
name.setText("os.name: " + System.getProperty("os.name"));
version.setText("os.version: " + System.getProperty("os.version"));
roversion.setText("ro.product.version: " + 
System.getProperty("ro.product.version"));
rofingerprint.setText("ro.build.fingerprint: " + 
System.getProperty("ro.build.fingerprint"));

Which gave me this output on my HTC Legend:
os.arch : armv6l
os.name: Linux
os.version: 2.6.32.17-g30929af
ro.product.version: 3.15.405.3
ro.build.fingerprint: 
htc_wwe/htc_legend/legend/legend:2.2/FRF91/291292:user/release-keys


On Sunday, April 29, 2012 12:30:36 PM UTC+2, JP wrote:
>
> I tried using this code:
>
> TextView arch = (TextView)findViewById(R.id.arch);
> TextView name = (TextView)findViewById(R.id.name);
> TextView version = (TextView)findViewById(R.id.version);
> TextView roversion = (TextView)findViewById(R.id.roversion);
> TextView rofingerprint = (TextView)findViewById(R.id.rofingerprint);
> arch.setText("os.arch: " + System.getProperty("os.arch"));
> name.setText("os.name: " + System.getProperty("os.name"));
> version.setText("os.version: " + System.getProperty("os.version"));
> roversion.setText("ro.product.version: " + 
> System.getProperty("ro.product.version"));
> rofingerprint.setText("ro.build.fingerprint: " + 
> System.getProperty("ro.build.fingerprint"));
>
> Which gave me this output on my HTC Legend:
> os.arch : armv6l
> os.name: Linux
> os.version: 2.6.32.17-g30929af
> ro.product.version: null
> ro.build.fingerprint: null
>
> So this didn't work either unfortunately... I'll keep looking!
>
> JP
>
>
>
> On Monday, April 23, 2012 4:53:25 PM UTC+2, Chris Stratton wrote:
>>
>> On Monday, April 23, 2012 7:54:50 AM UTC-4, JP wrote:
>>>
>>> Didn't find anything unfortunately. Is this really impossible to do?
>>
>>
>> Open an adb shell, type "getprop" and look at the result.
>>
>> Some entries which may be of interest:
>> ro.build.fingerprint
>> ro.build.version.*
>> ro.product.version
>>  
>> These should be readable by apps; what I don't know off the top of my 
>> head is which (if any) are "stable API's" and which are private and thus 
>> subject to change without notice.
>>
>

-- 
You received this message because you are subscribed to the Google
Groups "Android Developers" group.
To post to this group, send email to android-developers@googlegroups.com
To unsubscribe from this group, send email to
android-developers+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/android-developers?hl=en

Re: [android-developers] Re: Strange force close on Froyo phone, works fine on ICS tablet

2012-04-29 Thread Jim Graham
On Sun, Apr 29, 2012 at 12:04:01PM -0700, Jonathan S wrote:
> java.lang.NoSuchFieldError: android.graphics.PorterDuff$Mode.ADD
> 
> it is telling Mode.ADD is not exists in 2.2

Hm, according to the developers guide, it's existed since API
Level 1  2.2 is API Level 8  Yeah, it exists in 2.2.

Besides, like I said, it's working perfectly happily in another part
of the code.  The mystery continues  :-(

Later,
   --jim

-- 
THE SCORE:  ME:  2  CANCER:  0
73 DE N5IAL (/4)| DMR: So fsck was originally called
spooky1...@gmail.com|  something else.
< Running FreeBSD 7.0 > | Q:   What was it called?
ICBM / Hurricane:   | DMR: Well, the second letter was different.
   30.44406N 86.59909W  |-- Dennis M. Ritchie, Usenix, June 1998.

Android Apps Listing at http://www.jstrack.org/barcodes.html

-- 
You received this message because you are subscribed to the Google
Groups "Android Developers" group.
To post to this group, send email to android-developers@googlegroups.com
To unsubscribe from this group, send email to
android-developers+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/android-developers?hl=en


[android-developers] Re: Strange force close on Froyo phone, works fine on ICS tablet

2012-04-29 Thread Jonathan S
java.lang.NoSuchFieldError: android.graphics.PorterDuff$Mode.ADD

it is telling Mode.ADD is not exists in 2.2
On Sunday, April 29, 2012 12:45:34 PM UTC-4, Spooky wrote:
>
> The following code (which works fine earlier in the app on both devices) 
> causes a force close (logcat below) on my Froyo phone (Motorola Bravo 
> MB520), and works fine on my ICS tablet (Acer Iconia A500): 
>
> ---  CUT HERE  --- 
> Canvas canvas = new Canvas(saveme); 
> Paint paint = new Paint(); 
>
> canvas = new Canvas(saveme); 
> paint = new Paint(); 
> canvas.drawBitmap(image, 0, 0, paint); 
> // the following is line 1071...the source of the exception/error 
> paint.setXfermode(new 
> PorterDuffXfermode(android.graphics.PorterDuff.Mode.ADD)); 
> canvas.drawBitmap(filter, 0, 0, paint); 
> ---  CUT HERE  --- 
>
> And here's the error in logcat: 
>
> ---  CUT HERE  --- 
> D/AndroidRuntime(3550): Shutting down VM 
> W/dalvikvm(3550): threadid=1: thread exiting with uncaught exception 
> (group=0x400208b0) 
> E/AndroidRuntime(3550): FATAL EXCEPTION: main 
> E/AndroidRuntime(3550): java.lang.NoSuchFieldError: 
> android.graphics.PorterDuff$Mode.ADD 
> E/AndroidRuntime(3550):at 
> com.jdgapps.UltraCamPro.UltraCamPro$1.onPictureTaken(UltraCamPro.java:1071) 
> E/AndroidRuntime(3550):at 
> android.hardware.Camera$EventHandler.handleMessage(Camera.java:330) 
> E/AndroidRuntime(3550):at 
> android.os.Handler.dispatchMessage(Handler.java:99) 
> E/AndroidRuntime(3550):at android.os.Looper.loop(Looper.java:143) 
> E/AndroidRuntime(3550):at 
> android.app.ActivityThread.main(ActivityThread.java:4717) 
> E/AndroidRuntime(3550):at java.lang.reflect.Method.invokeNative(Native 
> Method) 
> E/AndroidRuntime(3550):at 
> java.lang.reflect.Method.invoke(Method.java:521) 
> E/AndroidRuntime(3550):at 
> com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:860)
>  
>
> E/AndroidRuntime(3550):at 
> com.android.internal.os.ZygoteInit.main(ZygoteInit.java:618) 
> E/AndroidRuntime(3550):at dalvik.system.NativeStart.main(Native 
> Method) 
> W/ActivityManager(1321):   Force finishing activity 
> com.jdgapps.UltraCamPro/.UltraCamPro 
>  ---  CUT HERE  --- 
>   
> On my tablet, it doesn't throw an error, and continues on to create the 
> final image, save it, and return to the camera preview.  Note that this 
> very same Porterduff code works fine earlier in the app (also blending 
> two bitmaps---different variable names...only difference), and also WAS 
> working at this point previously (before a name change, some unused 
> imports removed, two[1] that Eclipse said were unused replaced because 
> Eclipse complained when they weren't there after I removed them because 
> Eclipse said they weren't used).  Oh, one more change:  Target SDK 
> stepped up from Android 3.2.1 to Android 4.0.3, min SDK stayed at Android 
> 2.2.1.  Tablet also changed from Android 3.2.1 to 4.0.3. 
>
> Can anyone help explain this mystery? 
>
> Thanks, 
>--jim 
>
>
> [1] android.graphics.PorterDuff and android.graphics.PorterDuff.Mode 
>
> -- 
> THE SCORE:  ME:  2  CANCER:  0 
> 73 DE N5IAL (/4)| Peter da Silva:  No, try "rm -rf /" 
> spooky1...@gmail.com| Dave Aronson:As your life flashes before 
> < Running FreeBSD 7.0 > |  your eyes, in the unit of time known as an 
> ICBM / Hurricane:   |  ohnosecond (alt.sysadmin.recovery) 
>30.44406N 86.59909W  | 
>
> Android Apps Listing at http://www.jstrack.org/barcodes.html 
>
>

-- 
You received this message because you are subscribed to the Google
Groups "Android Developers" group.
To post to this group, send email to android-developers@googlegroups.com
To unsubscribe from this group, send email to
android-developers+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/android-developers?hl=en

Re: [android-developers] how to detect difference between 5 and 7 inch screen

2012-04-29 Thread Mark Murphy
On Sun, Apr 29, 2012 at 2:10 PM, Faust Nijhuis  wrote:
> The strange thing is that a 5.3 inch and a 10 inch screen  with the
> same screen density (800x1250)

Those are not the same density. They are the same *resolution*.
Density is resolution divided by size.

> I have a layout with a lot of 77x160dp icons.
> On the 5.3 inch screen is see 2.5 icons and on the 10 inch screen i see 5
> icons next to each other (portrait mode)
>
>  Why i do see only 2.5 icons on the 5.3 inch screen?

Perhaps because 160dp will use more pixels on the 5" than on the 10",
because the density of the 5" is significantly higher.

-- 
Mark Murphy (a Commons Guy)
http://commonsware.com | http://github.com/commonsguy
http://commonsware.com/blog | http://twitter.com/commonsguy

Android Training...At Your Office: http://commonsware.com/training

-- 
You received this message because you are subscribed to the Google
Groups "Android Developers" group.
To post to this group, send email to android-developers@googlegroups.com
To unsubscribe from this group, send email to
android-developers+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/android-developers?hl=en


[android-developers] Re: Bluetooth devices is pairing but not connecting

2012-04-29 Thread hüseyin toplu
i dont need to server code because i wanna just connect and then send
a file to a bluetooth device

-- 
You received this message because you are subscribed to the Google
Groups "Android Developers" group.
To post to this group, send email to android-developers@googlegroups.com
To unsubscribe from this group, send email to
android-developers+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/android-developers?hl=en


Re: [android-developers] how to detect difference between 5 and 7 inch screen

2012-04-29 Thread Faust Nijhuis
The strange thing is that a 5.3 inch and a 10 inch screen  with the
same screen density (800x1250) have a compete different view of the layout.

I have a layout with a lot of 77x160dp icons.
On the 5.3 inch screen is see 2.5 icons and on the 10 inch screen i see 5
icons next to each other (portrait mode)

 Why i do see only 2.5 icons on the 5.3 inch screen?

Faust

2012/4/29 Mark Murphy 

> On Sun, Apr 29, 2012 at 11:11 AM, Faust Nijhuis 
> wrote:
> > How can i detect the difference between 5 and 7 inch screen.
> > Sinds 5.3 (Galaxy note) and 7 inch screen are both large screens and we
> > can only use layout, layout-large and layout-xlarge.
>
> On Android 3.2 and higher, you can use resource set qualifiers like
> -sw600dp to help create your own size-dependent buckets.
>
> Prior to Android 3.2, at runtime, you can probably attempt to use
> screen density and resolution to try to derive the physical size and
> choose different resources (by name) based on that calculation.
> Accuracy of this approach is far from guaranteed, though.
>
> Personally, I would recommend you try to come up with a UI design that
> works OK on both 5" and 7" -large tablets.
>
> --
> Mark Murphy (a Commons Guy)
> http://commonsware.com | http://github.com/commonsguy
> http://commonsware.com/blog | http://twitter.com/commonsguy
>
> Android Training...At Your Office: http://commonsware.com/training
>
> --
> You received this message because you are subscribed to the Google
> Groups "Android Developers" group.
> To post to this group, send email to android-developers@googlegroups.com
> To unsubscribe from this group, send email to
> android-developers+unsubscr...@googlegroups.com
> For more options, visit this group at
> http://groups.google.com/group/android-developers?hl=en

-- 
You received this message because you are subscribed to the Google
Groups "Android Developers" group.
To post to this group, send email to android-developers@googlegroups.com
To unsubscribe from this group, send email to
android-developers+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/android-developers?hl=en

[android-developers] Re: Google I/O device in reboot loop.

2012-04-29 Thread Nathan


On Sunday, April 29, 2012 8:58:39 AM UTC-7, Streets Of Boston wrote:
>
> The same happened to mine. I was hoping a firmware update by me would fix 
> it. However, the GoogleIO version of the tablet seemed to have a different 
> boot-loader than the standard ones.
> I contacted Samsung and they told me the only way to flash it with a 
> proper firmware and fix it was to send it in to get it fixed.
>
> I did and within a week I had mine back fixed, for free. Mine was still in 
> its warranty. The warranty is for one year, if i'm not mistaken. This means 
> that yours can be fixed for free as well.
> Register your tablet at www.samsung.com and go from there to get it fixed.
>
> Thanks. I'm hoping for the same turnaround. I'm cutting it close for 
AnDevCon. Doing presentations with a laptop is so last decade. 

Nathan 

-- 
You received this message because you are subscribed to the Google
Groups "Android Developers" group.
To post to this group, send email to android-developers@googlegroups.com
To unsubscribe from this group, send email to
android-developers+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/android-developers?hl=en

Re: [android-developers] Re: Bluetooth devices is pairing but not connecting

2012-04-29 Thread Kristopher Micinski
Chill out,

you posted this four hours ago, and expect people to get back to you
within a few hours on a free list?  If you want that kind of
responsiveness you'll need to hire a consultant :-)...

You show the client code, but I didn't see the server code.  Most
likely you're doing something like using the wrong key or something
like that...

kris

On Sun, Apr 29, 2012 at 12:38 PM, hüseyin toplu  wrote:
> nobody is not know anything about that :S
>
> --
> You received this message because you are subscribed to the Google
> Groups "Android Developers" group.
> To post to this group, send email to android-developers@googlegroups.com
> To unsubscribe from this group, send email to
> android-developers+unsubscr...@googlegroups.com
> For more options, visit this group at
> http://groups.google.com/group/android-developers?hl=en

-- 
You received this message because you are subscribed to the Google
Groups "Android Developers" group.
To post to this group, send email to android-developers@googlegroups.com
To unsubscribe from this group, send email to
android-developers+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/android-developers?hl=en


[android-developers] Strange force close on Froyo phone, works fine on ICS tablet

2012-04-29 Thread Jim Graham
The following code (which works fine earlier in the app on both devices)
causes a force close (logcat below) on my Froyo phone (Motorola Bravo
MB520), and works fine on my ICS tablet (Acer Iconia A500):

---  CUT HERE  ---
Canvas canvas = new Canvas(saveme);
Paint paint = new Paint();

canvas = new Canvas(saveme);
paint = new Paint();
canvas.drawBitmap(image, 0, 0, paint);
// the following is line 1071...the source of the exception/error
paint.setXfermode(new PorterDuffXfermode(android.graphics.PorterDuff.Mode.ADD));
canvas.drawBitmap(filter, 0, 0, paint);
---  CUT HERE  ---

And here's the error in logcat:

---  CUT HERE  ---
D/AndroidRuntime(3550): Shutting down VM
W/dalvikvm(3550): threadid=1: thread exiting with uncaught exception 
(group=0x400208b0)
E/AndroidRuntime(3550): FATAL EXCEPTION: main
E/AndroidRuntime(3550): java.lang.NoSuchFieldError: 
android.graphics.PorterDuff$Mode.ADD
E/AndroidRuntime(3550):at 
com.jdgapps.UltraCamPro.UltraCamPro$1.onPictureTaken(UltraCamPro.java:1071)
E/AndroidRuntime(3550):at 
android.hardware.Camera$EventHandler.handleMessage(Camera.java:330)
E/AndroidRuntime(3550):at 
android.os.Handler.dispatchMessage(Handler.java:99)
E/AndroidRuntime(3550):at android.os.Looper.loop(Looper.java:143)
E/AndroidRuntime(3550):at 
android.app.ActivityThread.main(ActivityThread.java:4717)
E/AndroidRuntime(3550):at java.lang.reflect.Method.invokeNative(Native 
Method)
E/AndroidRuntime(3550):at java.lang.reflect.Method.invoke(Method.java:521)
E/AndroidRuntime(3550):at 
com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:860)
E/AndroidRuntime(3550):at 
com.android.internal.os.ZygoteInit.main(ZygoteInit.java:618)
E/AndroidRuntime(3550):at dalvik.system.NativeStart.main(Native Method)
W/ActivityManager(1321):   Force finishing activity 
com.jdgapps.UltraCamPro/.UltraCamPro
 ---  CUT HERE  ---
 
On my tablet, it doesn't throw an error, and continues on to create the
final image, save it, and return to the camera preview.  Note that this
very same Porterduff code works fine earlier in the app (also blending
two bitmaps---different variable names...only difference), and also WAS
working at this point previously (before a name change, some unused
imports removed, two[1] that Eclipse said were unused replaced because
Eclipse complained when they weren't there after I removed them because
Eclipse said they weren't used).  Oh, one more change:  Target SDK
stepped up from Android 3.2.1 to Android 4.0.3, min SDK stayed at Android
2.2.1.  Tablet also changed from Android 3.2.1 to 4.0.3.

Can anyone help explain this mystery?

Thanks,
   --jim


[1] android.graphics.PorterDuff and android.graphics.PorterDuff.Mode

-- 
THE SCORE:  ME:  2  CANCER:  0
73 DE N5IAL (/4)| Peter da Silva:  No, try "rm -rf /"
spooky1...@gmail.com| Dave Aronson:As your life flashes before
< Running FreeBSD 7.0 > |  your eyes, in the unit of time known as an
ICBM / Hurricane:   |  ohnosecond (alt.sysadmin.recovery)
   30.44406N 86.59909W  |

Android Apps Listing at http://www.jstrack.org/barcodes.html

-- 
You received this message because you are subscribed to the Google
Groups "Android Developers" group.
To post to this group, send email to android-developers@googlegroups.com
To unsubscribe from this group, send email to
android-developers+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/android-developers?hl=en


[android-developers] Re: Bluetooth devices is pairing but not connecting

2012-04-29 Thread hüseyin toplu
nobody is not know anything about that :S

-- 
You received this message because you are subscribed to the Google
Groups "Android Developers" group.
To post to this group, send email to android-developers@googlegroups.com
To unsubscribe from this group, send email to
android-developers+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/android-developers?hl=en


[android-developers] Re: Google I/O device in reboot loop.

2012-04-29 Thread Streets Of Boston
The same happened to mine. I was hoping a firmware update by me would fix 
it. However, the GoogleIO version of the tablet seemed to have a different 
boot-loader than the standard ones.
I contacted Samsung and they told me the only way to flash it with a proper 
firmware and fix it was to send it in to get it fixed.

I did and within a week I had mine back fixed, for free. Mine was still in 
its warranty. The warranty is for one year, if i'm not mistaken. This means 
that yours can be fixed for free as well.
Register your tablet at www.samsung.com and go from there to get it fixed.

On Sunday, April 29, 2012 1:10:02 AM UTC-4, Nathan wrote:
>
> Without any provocation, my Galaxy Tab 10.1 began to be stuck in a reboot 
> loop this morning. Since this is a common device among Android developers, 
> perhaps some of you have already dealt with this problem. 
>
> It displays the Samsung name, then the swirly logo, then the Samsung name, 
> then the swirly logo . . .  
>
> adb says the device is complaining about, among other things,  a Read Only 
> file system. 
>
> I haven't rooted, changed bootloaders, installed custom roms or anything 
> of the sort. The last over the air update was last August, I believe. 
>
> Thinking I may need to flash firmware any way, I followed the instructions 
> at this page:
>
> http://www.theandroidsoul.com/android-3-2-1-update-for-galaxy-tab-10-1-is-out/
>
> All appeared to go well. 
> After that, the tablet boots as follows:
> Shows Samsung Galaxy Tab 10.1 label. 
> Shows a think bar of static and stays there for a few minutes  
> It displays the Samsung name, then the swirly logo, then the Samsung name, 
> then the swirly logo . . .  
>
> I don't know how to make the file system be not Read Only. 
>
> Has the device bricked itself? Have I bricked it? This sure seems like a 
> hardware problem if it survived a firmware update. 
>
> Alas, my Tab 10.1, it was fun while it lasted. But at just a year old, it 
> didn't last long. 
>
> Nathan
>
>

-- 
You received this message because you are subscribed to the Google
Groups "Android Developers" group.
To post to this group, send email to android-developers@googlegroups.com
To unsubscribe from this group, send email to
android-developers+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/android-developers?hl=en

[android-developers] Using SIP for IP Telephony over wifi

2012-04-29 Thread ikimatsu noob
Hello.

I'm hoping you could help me with two questions.
I took a look at SIPDroid and saw that a person had to register, make
an account before communicating over the app.

My question is, is it possible to make a videocall, via wifi, just
like SIPDroid, but without having to make an account, especially that
both devices are on the same network.?

Second, can anyone tell me the use and importance of a
WebcamBroadcaster class given what I would like to achieve?

Thank you.

-- 
You received this message because you are subscribed to the Google
Groups "Android Developers" group.
To post to this group, send email to android-developers@googlegroups.com
To unsubscribe from this group, send email to
android-developers+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/android-developers?hl=en


Re: [android-developers] how to detect difference between 5 and 7 inch screen

2012-04-29 Thread Mark Murphy
On Sun, Apr 29, 2012 at 11:11 AM, Faust Nijhuis  wrote:
> How can i detect the difference between 5 and 7 inch screen.
> Sinds 5.3 (Galaxy note) and 7 inch screen are both large screens and we
> can only use layout, layout-large and layout-xlarge.

On Android 3.2 and higher, you can use resource set qualifiers like
-sw600dp to help create your own size-dependent buckets.

Prior to Android 3.2, at runtime, you can probably attempt to use
screen density and resolution to try to derive the physical size and
choose different resources (by name) based on that calculation.
Accuracy of this approach is far from guaranteed, though.

Personally, I would recommend you try to come up with a UI design that
works OK on both 5" and 7" -large tablets.

-- 
Mark Murphy (a Commons Guy)
http://commonsware.com | http://github.com/commonsguy
http://commonsware.com/blog | http://twitter.com/commonsguy

Android Training...At Your Office: http://commonsware.com/training

-- 
You received this message because you are subscribed to the Google
Groups "Android Developers" group.
To post to this group, send email to android-developers@googlegroups.com
To unsubscribe from this group, send email to
android-developers+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/android-developers?hl=en


[android-developers] how to detect difference between 5 and 7 inch screen

2012-04-29 Thread Faust Nijhuis
Hello all,

How can i detect the difference between 5 and 7 inch screen.
Sinds 5.3 (Galaxy note) and 7 inch screen are both large screens and we
can only use layout, layout-large and layout-xlarge.

Faust

-- 
You received this message because you are subscribed to the Google
Groups "Android Developers" group.
To post to this group, send email to android-developers@googlegroups.com
To unsubscribe from this group, send email to
android-developers+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/android-developers?hl=en

[android-developers] Re: How to change default HIPRI connection expiry?

2012-04-29 Thread Med Chakib
Hello,
I have tried your method to use 3G and WIFI simultaneously, however data is 
still routed through WIFI even though HIPRI connection is successfully 
initiated and traffic to ipAddress is routed through it.

   connMan = (ConnectivityManager) 
> getSystemService(Context.CONNECTIVITY_SERVICE);
>int res = 
> connMan.startUsingNetworkFeature(ConnectivityManager.TYPE_MOBILE, 
> "enableHIPRI");
>boolean reqRes = 
> connMan.requestRouteToHost(ConnectivityManager.TYPE_MOBILE_HIPRI, 
> ipAddress); 

Socket soc = new Socket(ipAddress,port);

... 


Any help through this problem ? 

-- 
You received this message because you are subscribed to the Google
Groups "Android Developers" group.
To post to this group, send email to android-developers@googlegroups.com
To unsubscribe from this group, send email to
android-developers+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/android-developers?hl=en

[android-developers] Re: Bluetooth devices is pairing but not connecting

2012-04-29 Thread hüseyin toplu
nobody is not know anything about that :S

-- 
You received this message because you are subscribed to the Google
Groups "Android Developers" group.
To post to this group, send email to android-developers@googlegroups.com
To unsubscribe from this group, send email to
android-developers+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/android-developers?hl=en


[android-developers] Bluetooth devices is pairing but not connecting

2012-04-29 Thread hüseyin toplu
E/BluetoothChatService( 8403): Hata
E/BluetoothChatService( 8403): java.io.IOException: Connection refused

E/BluetoothChatService( 8403):  at
android.bluetooth.BluetoothSocket.connectNative(Native Method)

E/BluetoothChatService( 8403):  at
android.bluetooth.BluetoothSocket.connect(BluetoothSocket.java:206)

E/BluetoothChatService( 8403):  at com.androproject.picture.iletisim
$ConnectThread.run(iletisim.java:370)


public ConnectThread(BluetoothDevice device, boolean secure) {
   mmDevice = device;
BluetoothSocket tmp = null;
mSocketType = secure ? "Secure" : "Insecure";
int port=1;

try
{
  Method m =
device.getClass().getMethod("createRfcommSocket", new
  Class[] { int.class });
  tmp = 
(BluetoothSocket)m.invoke(device,
port);
}catch (Exception e)
{
Log.e(TAG, "Failed to connect", e);}


mmSocket = tmp;
 }

public void run() {

setName("ConnectThread" + mSocketType);
mAdapter.cancelDiscovery();

try {
mmSocket.connect();
Thread.sleep(6000);
} catch (InterruptedException e) {
// TODO Auto-generated catch block
 Log.e(TAG, "", e);
e.printStackTrace();
}
 catch (IOException e) {
 Log.e(TAG, "Hata Buradaaaadadadadadh", e);
// Close the socket
try {
mmSocket.close();
} catch (IOException e2) {
Log.e(TAG, "unable to close() " + mSocketType +
" socket during connection failure", e2);
}
connectionFailed();
return;
}

-- 
You received this message because you are subscribed to the Google
Groups "Android Developers" group.
To post to this group, send email to android-developers@googlegroups.com
To unsubscribe from this group, send email to
android-developers+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/android-developers?hl=en


[android-developers] Bluetooth devices is pairing but not connecting

2012-04-29 Thread hüseyin toplu
E/BluetoothChatService( 8403): Hata
E/BluetoothChatService( 8403): java.io.IOException: Connection refused

E/BluetoothChatService( 8403):  at
android.bluetooth.BluetoothSocket.connectNative(Native Method)

E/BluetoothChatService( 8403):  at
android.bluetooth.BluetoothSocket.connect(BluetoothSocket.java:206)

E/BluetoothChatService( 8403):  at com.androproject.picture.iletisim
$ConnectThread.run(iletisim.java:370)


public ConnectThread(BluetoothDevice device, boolean secure) {
   mmDevice = device;
BluetoothSocket tmp = null;
mSocketType = secure ? "Secure" : "Insecure";
int port=1;

try
{
  Method m =
device.getClass().getMethod("createRfcommSocket", new
  Class[] { int.class });
  tmp = 
(BluetoothSocket)m.invoke(device,
port);
}catch (Exception e)
{
Log.e(TAG, "Failed to connect", e);}


mmSocket = tmp;
 }

public void run() {

setName("ConnectThread" + mSocketType);
mAdapter.cancelDiscovery();

try {
mmSocket.connect();
Thread.sleep(6000);
} catch (InterruptedException e) {
// TODO Auto-generated catch block
 Log.e(TAG, "", e);
e.printStackTrace();
}
 catch (IOException e) {
 Log.e(TAG, "Hata Buradaaaadadadadadh", e);
// Close the socket
try {
mmSocket.close();
} catch (IOException e2) {
Log.e(TAG, "unable to close() " + mSocketType +
" socket during connection failure", e2);
}
connectionFailed();
return;
}

-- 
You received this message because you are subscribed to the Google
Groups "Android Developers" group.
To post to this group, send email to android-developers@googlegroups.com
To unsubscribe from this group, send email to
android-developers+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/android-developers?hl=en


Re: [android-developers] play sound file

2012-04-29 Thread Jonas Petersson

On 2012-04-28 17:51, Mai Al-Ammar wrote:

I install the new program every time but it still the old file.


This my be related to what I have noted:
Apparently there is some kind of "optimization" going on when deploying 
iteratively from Eclipse - adding files will work as expected, but 
removing will just "not add" the file, but may still keep it around - 
presumably the APK zip file is just UPDATED with new stuff and hence 
removed files may hang around until the next project cleanup.


Note: I've not really dug into this, just deduced that something like 
this will occasionally cause confusion - I examined the APK file once 
just after a major refactoring and found a mix of old and new files.


Best / Jonas



On Sat, Apr 28, 2012 at 5:55 PM, Mark Murphy mailto:mmur...@commonsware.com>> wrote:

On Sat, Apr 28, 2012 at 10:49 AM, Mai Al-Ammar
mailto:mai.alam...@gmail.com>> wrote:
 > I did not delete it at run time, I delete the file before I
compile the
 > project and replace it with other file. but the program still
play the old
 > one

Then you did not install the modified app on the device.


--
You received this message because you are subscribed to the Google
Groups "Android Developers" group.
To post to this group, send email to android-developers@googlegroups.com
To unsubscribe from this group, send email to
android-developers+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/android-developers?hl=en


Re: [android-developers] Reading ROM version through code

2012-04-29 Thread JP
I tried using this code:

TextView arch = (TextView)findViewById(R.id.arch);
TextView name = (TextView)findViewById(R.id.name);
TextView version = (TextView)findViewById(R.id.version);
TextView roversion = (TextView)findViewById(R.id.roversion);
TextView rofingerprint = (TextView)findViewById(R.id.rofingerprint);
arch.setText("os.arch: " + System.getProperty("os.arch"));
name.setText("os.name: " + System.getProperty("os.name"));
version.setText("os.version: " + System.getProperty("os.version"));
roversion.setText("ro.product.version: " + 
System.getProperty("ro.product.version"));
rofingerprint.setText("ro.build.fingerprint: " + 
System.getProperty("ro.build.fingerprint"));

Which gave me this output on my HTC Legend:
os.arch : armv6l
os.name: Linux
os.version: 2.6.32.17-g30929af
ro.product.version: null
ro.build.fingerprint: null

So this didn't work either unfortunately... I'll keep looking!

JP



On Monday, April 23, 2012 4:53:25 PM UTC+2, Chris Stratton wrote:
>
> On Monday, April 23, 2012 7:54:50 AM UTC-4, JP wrote:
>>
>> Didn't find anything unfortunately. Is this really impossible to do?
>
>
> Open an adb shell, type "getprop" and look at the result.
>
> Some entries which may be of interest:
> ro.build.fingerprint
> ro.build.version.*
> ro.product.version
>  
> These should be readable by apps; what I don't know off the top of my head 
> is which (if any) are "stable API's" and which are private and thus subject 
> to change without notice.
>

-- 
You received this message because you are subscribed to the Google
Groups "Android Developers" group.
To post to this group, send email to android-developers@googlegroups.com
To unsubscribe from this group, send email to
android-developers+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/android-developers?hl=en

[android-developers] About Default debug.keystore

2012-04-29 Thread Soyer
Hello everybody,




I recently moved .android folder from C drive to D drive, and now
eclipe is taking the default debug.keystore in D:/
so when i go to run it
first i cant see the old AVDs
and when i create a new one and press run , i get this error
C:\Users\USER\.android/avd/Avd1.ini
i googled this i they said
just move it back...
but the issue
is that once i create a new one (AVD)
.android folder gets created automotically
in the D drive
i should change the default path for the debug.keystore
but it wouldnt change :S


Any help please, would be very appreciated.


-- 
You received this message because you are subscribed to the Google
Groups "Android Developers" group.
To post to this group, send email to android-developers@googlegroups.com
To unsubscribe from this group, send email to
android-developers+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/android-developers?hl=en