[android-developers] Re: Concurrency: Do you use Loaders? AsyncTask? or Runnables?
There are differences - Loader managed by fragment/activity, if you feel trouble managing task between configuration changes, other interruption (phone ring) or any other, use Loader and let Fragment/activity will mange pause/restart/reattach . Where ever possible try to use Loader - AsyncTask- Simply queuing of thread, Android internally manage execution based on available resource, A global executor Service which does not block current UI thread and keep reference of UI thread to display data when execution finish. In most of situation it is easy to implement and avoid UI blocking. - Runnable - non control threads, good to use when you know what you are doing for ex: a socket listing on a port -- -- 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 unsubscribe from this group and stop receiving emails from it, send an email to android-developers+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
Re: [android-developers] Getting the problem while fetching the current location...?
Hi, I have tested in Samsung Galaxy Grand. In this device I have tried but not getting the current location details. Same code is working in ICS device. What might be the problem. On Tuesday, March 19, 2013 7:22:40 PM UTC+5:30, Kristopher Micinski wrote: what's the exact device? Kris On Tue, Mar 19, 2013 at 5:44 AM, abhay_401 abhilash.and...@gmail.com javascript: wrote: Hi, I am having an application in which we can get the latitude and longitude of the current location. Which is working fine in ICS device, but the same app if i test in Jellybean(4.1.2) its not giving the latitude and longitude. Do we need to add any new functionality or permission to test in Android version 4.1.? Regarding, Abhilash Baddam -- -- You received this message because you are subscribed to the Google Groups Android Developers group. To post to this group, send email to android-d...@googlegroups.comjavascript: To unsubscribe from this group, send email to android-developers+unsubscr...@googlegroups.com javascript: 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 unsubscribe from this group and stop receiving emails from it, send an email to android-developers+unsubscr...@googlegroups.com javascript:. For more options, visit https://groups.google.com/groups/opt_out. -- -- 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 unsubscribe from this group and stop receiving emails from it, send an email to android-developers+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[android-developers] App works on Samsung Galaxy Note ONLY when I debug it with eclipse
Hello, I have written an Android app that uses fusesource stompjms client. The app connect to a server with stompjms. I am using AsyncTask for network related operations. The app: - works on all 2.3 devices; - works on 2.3 emulator; - works on 4.0 emulator; - works on HTC 4.0 phone; - hangs on connect to server on Motorola RAZR 4.0; - hangs on connect to server on Samsung Galaxy Note 4.0; - WORKS ON GALAXY NOTE WHEN I AM DEBUGGING IT WITH ECLIPSE AND USB CABLE! I can see that stomp jms is an asynchronous framework that uses CountDownLatch java class. When it hangs I am pretty sure that it waits forever on latch.await() Please help me, it is a very strange behaviour! Thanks, Mario -- -- 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 unsubscribe from this group and stop receiving emails from it, send an email to android-developers+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[android-developers] Re: Deadlock running app on Nexus 10, Android 4.2.2
Are you able to repeatedly reproduce the issue? Is the suspended thread always stuck in the same place? If it does, have you considered removing the call to validate the key (which calls into, apparently native, regular expression code)? -- K On Wednesday, March 20, 2013 2:25:35 AM UTC+4, bergstr wrote: Hello, I have an app that displays images in a ListView and in a larger ImageView in a separate fragment. The images are downloaded dynamically from a server into a LRU cache using a threaded backend. I am experiencing random deadlocks on my Nexus 10 when I put load onto the app by scrolling through the list. I have attached the traces.txt file, which shows the thread sates at the time of the deadlock. As far as I can tell from the file and from analyzing my code, there are 3 threads waiting for a lock on a DiskLruCache object while the lock is held by another thread (held by tid=40). So far there would be nothing unusual - if it wasn't for the fact that thread tid=40 is in state SUSPENDED!! All locks are from synchronized methods on the DiskLruCache object. One of the locked threads is obviously the main UI thread, which causes the app to lock up. What I dont understand is how thread 40 (which is a background cache maintenance thread) got into the SUSPENDED state. It is certainly not because the Thread.suspend() method is called anywhere in my code (the method is deprecated, the javadoc clearly warns against the deadlock potential it introduces, and I can read). The traces.txt file clearly shows that there are no other locks involved, so there is no circular dependency. It seems someone is suspending a thread - which is an obvious deadlock trap - and it is NOT ME. I am coming close to the point of assuming it is a nasty feature of the Android VM.. Can anybody help me solve this riddle? If this was a VM error, it would be an extremely heavy one - I'd really prefer to find it on my side.. thanks, Christian -- -- 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 unsubscribe from this group and stop receiving emails from it, send an email to android-developers+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[android-developers] Re: Concurrency: Do you use Loaders? AsyncTask? or Runnables?
I use...java.util.concurrent.* classes. AsyncTask is just a specific usage of these classes. Avoid creating and managing threads yourself. Use Executors instead. -- -- 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 unsubscribe from this group and stop receiving emails from it, send an email to android-developers+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[android-developers] Re: Making my app the only one that can run.
Hi, You should build your own home activity ( a real one that handles all the events needed to be handled by a home) then at each key methods of your activity (onResume, onCreate) you just launch your apllication using the intent (startActivity(intent)). If building a home is a too huge work, a home is already available (under apache licence) in the sdk, to be exact in the sample of the sdk. Then, as you did, just set this home as the default one on the devices you want to manage. I have the project to make such application for my kid allowing him to use only some applications (the ones I decided). Hope it helps. Mathias Seguy Founder of Android2EE Le mardi 19 mars 2013 22:35:56 UTC+1, Tobiah a écrit : I'm not being unfriendly to users. I need to hand out devices at an event so that people can walk around and use my app. I don't want them to use other apps on the phone. So I put this in my AndroidManifest.xml: intent-filter action android:name=android.intent.action.MAIN / category android:name=android.intent.category.LAUNCHER / category android:name=android.intent.category.HOME / category android:name=android.intent.category.DEFAULT / /intent-filter Then I get a choice of launchers from the home button. I choose my app 'Always' and everything is great. The only problem is that if I reboot the device, my app indeed comes up as the home screen, but it immediately crashes. Is there some event or Intent I need to handle to do this? I can't figure out how to debug this, because there are no logcat events, and when I restart my app it works fine. Also if there are any other thoughts on how to make a one app device, I'd love to have suggestions. Thanks! Tobiah -- -- 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 unsubscribe from this group and stop receiving emails from it, send an email to android-developers+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[android-developers] Android Games SDK?
Hey, Are there any game development SDK's by google, or some other established developers? I'm programming in JAVA. -- -- 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 unsubscribe from this group and stop receiving emails from it, send an email to android-developers+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
Re: [android-developers] Android Games SDK?
On Wed, Mar 20, 2013 at 05:42:58AM -0700, Taylor Ringo wrote: Are there any game development SDK's by google, or some other established developers? I'm programming in JAVA. As to SDKs, I don't know. However, there are at least two popular game engine libs, libgdx and andengine, which is (or at least, used to be, and probably still is) based on libgdx. Later, --jim -- THE SCORE: ME: 2 CANCER: 0 73 DE N5IAL (/4)MiSTie #49997 Running Mac OS X Lion spooky1...@gmail.com ICBM/Hurricane: 30.44406N 86.59909W In light of DHS's recommendation to defend yourself against armed intruders with scissors, I'm giving my deer rifle a new nickname: Scissors. -- -- 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 unsubscribe from this group and stop receiving emails from it, send an email to android-developers+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[android-developers] Re: Deadlock running app on Nexus 10, Android 4.2.2
Hello Kostya, havent tried to reproduce yet, so I cannot say whether its always in the same place. Will try that next. However, you will agree that even seeing it once is enough reason for an emergency call. I am considering all options, really. But before I delve into speculative approaches, I would like to understand what is happening. My hope was/is that someone will look at the file and say something like aah, here's what you have overlooked or maybe, you should read chapter X in the developer docs. Or maybe been there, done that Anyway, thanks for looking at the file, and for your comments Christian -- -- 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 unsubscribe from this group and stop receiving emails from it, send an email to android-developers+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[android-developers] Re: Concurrency: Do you use Loaders? AsyncTask? or Runnables?
There are even more ways of doing stuff in the background: IntentService :-) - Runnable If you mean a Thread (running itself or a Runnable): Generally, avoid using them. But there are good use cases: When you want to setup something that runs in the background for a long time (possible during the entire lifetime of your app's process), simple Threads are very useful, e.g. set up a rendering thread for an openGL game. - AsyncTasks If you want to run something in the background, that is a one-shot operation, relatively short duration and you want your UI (main UI-thread) to be notified about updates/results. If you are not worried about screen rotations/config-changes, etc., AsyncTasks work well. AsyncTasks in these situations are relatively simple to implement. - Loaders, AsyncTaskLoaders Like AsyncTasks, but they are well suited to easily handle screen rotations/config-changes/etc, especially when used in conjunction with Fragments. - IntentService Also good for one-shot operations with relatively short duration. Best used when you want to share these operations among other components of your or other people's applications and/or want to have Android manage its life-cycle (e.g. if an (Intent)Service is killed, Android could restart it for you automatically and re-issue the Intent that started it before). On Tuesday, March 19, 2013 8:33:50 PM UTC-4, littledot wrote: Android concurrency has always bugged me... These are all methods to achieve essentially the same thing: mutli-threading *I honestly don't see much difference between them*, except the amount of code you need to write.. Which methods do you use? Are there certain situations where you prefer one method over the other? Or do you stick to one method and use it as a rule-of-thumb? Thanks for reading. -- -- 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 unsubscribe from this group and stop receiving emails from it, send an email to android-developers+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[android-developers] Re: How to determine application's method count?
Well, what 3rd party JARs are you using? Thanks. On Tuesday, March 19, 2013 4:02:54 PM UTC-5, Ab wrote: I'm encountering issues with my application having to many methods. In the last post in the below link, a poster posts the method count for his application (broken down by package). I unable to find how I can get this information for my application, any suggestions? https://code.google.com/p/android/issues/detail?id=20814 -- -- 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 unsubscribe from this group and stop receiving emails from it, send an email to android-developers+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[android-developers] Re: Making my app the only one that can run.
I used an app in Google Play called *SureLock Kiosk Lockdown*. On Tuesday, March 19, 2013 4:35:56 PM UTC-5, Tobiah wrote: I'm not being unfriendly to users. I need to hand out devices at an event so that people can walk around and use my app. I don't want them to use other apps on the phone. So I put this in my AndroidManifest.xml: intent-filter action android:name=android.intent.action.MAIN / category android:name=android.intent.category.LAUNCHER / category android:name=android.intent.category.HOME / category android:name=android.intent.category.DEFAULT / /intent-filter Then I get a choice of launchers from the home button. I choose my app 'Always' and everything is great. The only problem is that if I reboot the device, my app indeed comes up as the home screen, but it immediately crashes. Is there some event or Intent I need to handle to do this? I can't figure out how to debug this, because there are no logcat events, and when I restart my app it works fine. Also if there are any other thoughts on how to make a one app device, I'd love to have suggestions. Thanks! Tobiah -- -- 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 unsubscribe from this group and stop receiving emails from it, send an email to android-developers+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
Re: [android-developers] Re: Making my app the only one that can run.
Thanks Envoyé de mon Android Excusez la brieveté. Mathias Seguy - Android2EE Le 20 mars 2013 15:55, bob b...@coolfone.comze.com a écrit : I used an app in Google Play called *SureLock Kiosk Lockdown*. On Tuesday, March 19, 2013 4:35:56 PM UTC-5, Tobiah wrote: I'm not being unfriendly to users. I need to hand out devices at an event so that people can walk around and use my app. I don't want them to use other apps on the phone. So I put this in my AndroidManifest.xml: intent-filter action android:name=android.intent.**action.MAIN / category android:name=android.intent.**category.LAUNCHER / category android:name=android.intent.**category.HOME / category android:name=android.intent.**category.DEFAULT / /intent-filter Then I get a choice of launchers from the home button. I choose my app 'Always' and everything is great. The only problem is that if I reboot the device, my app indeed comes up as the home screen, but it immediately crashes. Is there some event or Intent I need to handle to do this? I can't figure out how to debug this, because there are no logcat events, and when I restart my app it works fine. Also if there are any other thoughts on how to make a one app device, I'd love to have suggestions. Thanks! Tobiah -- -- 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 a topic in the Google Groups Android Developers group. To unsubscribe from this topic, visit https://groups.google.com/d/topic/android-developers/h7t1vjkoF0w/unsubscribe?hl=en . To unsubscribe from this group and all its topics, send an email to android-developers+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out. -- -- 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 unsubscribe from this group and stop receiving emails from it, send an email to android-developers+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
Re: [android-developers] Re: Concurrency: Do you use Loaders? AsyncTask? or Runnables?
Though it's worth noting that since an `IntentService` doesn't run in a background thread context. (Probably one of the biggest things beginners screw up..) Kris On Wed, Mar 20, 2013 at 9:49 AM, Streets Of Boston flyingdutc...@gmail.com wrote: There are even more ways of doing stuff in the background: IntentService :-) Runnable If you mean a Thread (running itself or a Runnable): Generally, avoid using them. But there are good use cases: When you want to setup something that runs in the background for a long time (possible during the entire lifetime of your app's process), simple Threads are very useful, e.g. set up a rendering thread for an openGL game. AsyncTasks If you want to run something in the background, that is a one-shot operation, relatively short duration and you want your UI (main UI-thread) to be notified about updates/results. If you are not worried about screen rotations/config-changes, etc., AsyncTasks work well. AsyncTasks in these situations are relatively simple to implement. Loaders, AsyncTaskLoaders Like AsyncTasks, but they are well suited to easily handle screen rotations/config-changes/etc, especially when used in conjunction with Fragments. IntentService Also good for one-shot operations with relatively short duration. Best used when you want to share these operations among other components of your or other people's applications and/or want to have Android manage its life-cycle (e.g. if an (Intent)Service is killed, Android could restart it for you automatically and re-issue the Intent that started it before). On Tuesday, March 19, 2013 8:33:50 PM UTC-4, littledot wrote: Android concurrency has always bugged me... These are all methods to achieve essentially the same thing: mutli-threading I honestly don't see much difference between them, except the amount of code you need to write.. Which methods do you use? Are there certain situations where you prefer one method over the other? Or do you stick to one method and use it as a rule-of-thumb? Thanks for reading. -- -- 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 unsubscribe from this group and stop receiving emails from it, send an email to android-developers+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out. -- -- 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 unsubscribe from this group and stop receiving emails from it, send an email to android-developers+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
Re: [android-developers] Getting the problem while fetching the current location...?
Some Galaxy devices (especially the Spica) require an alternative way of starting up the location listener. Ping me if you want the code. -- -- 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 unsubscribe from this group and stop receiving emails from it, send an email to android-developers+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
Re: [android-developers] Getting the problem while fetching the current location...?
I'm interested as to why their implementation would differ from the standard API, do you have any specific reason for not putting an example on github, or would you care to share the trick..? (I'm just interested because it seems like a stupid decision on the vendor's part to break things..) Kris On Wed, Mar 20, 2013 at 11:09 AM, lbendlin l...@bendlin.us wrote: Some Galaxy devices (especially the Spica) require an alternative way of starting up the location listener. Ping me if you want the code. -- -- 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 unsubscribe from this group and stop receiving emails from it, send an email to android-developers+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out. -- -- 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 unsubscribe from this group and stop receiving emails from it, send an email to android-developers+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[android-developers] I'm missing something dumb here...
I'm making a grid of items that has an image and two text elements under it. I want all three elements centered horizontally, and the image to be right above the text. For some reason, the image is centered vertically and the text is at the bottom. Here's a screen shot to make that clearer: https://www.evernote.com/shard/s138/sh/6cdb585f-d523-47a5-a3a3-184124719e01/ed424d6929bdbf4abd9c36e2ce4a4390 I've tried everything I can think of... This is the grid view: GridView android:id=@+id/content_list_grid_view android:columnWidth=90dp android:numColumns=4 android:verticalSpacing=5dp android:horizontalSpacing=10dp android:stretchMode=columnWidth android:layout_height=wrap_content android:layout_width=fill_parent android:padding=5dp / This is my item: ?xml version=1.0 encoding=utf-8? LinearLayout xmlns:android=http://schemas.android.com/apk/res/android; android:layout_width=fill_parent android:layout_height=140dp android:orientation=vertical android:gravity=bottom|center_horizontal ImageView android:id=@+id/thumbnail_image android:background=#40ff8080 android:layout_width=wrap_content android:layout_height=110dp android:layout_gravity=center_horizontal|bottom android:src=@drawable/image_not_available_large android:contentDescription=@string/thumbnail_image / TextView android:id=@+id/title_name android:textColor=@color/white_color android:layout_width=wrap_content android:layout_height=wrap_content android:singleLine=true android:gravity=center_horizontal style=@style/normal_label / TextView android:id=@+id/title_author android:textColor=@color/light_gray_color android:layout_width=wrap_content android:layout_height=wrap_content android:singleLine=true android:gravity=center_horizontal style=@style/normal_label / /LinearLayout -- -- 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 unsubscribe from this group and stop receiving emails from it, send an email to android-developers+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[android-developers] Re: I'm missing something dumb here...
I think android:layout_below is only for relative layout...but I may try that instead. :-/ Nothing else seems to be working here... Larry On Wed, Mar 20, 2013 at 10:11 AM, John Masseria jpmasse...@gmail.comwrote: Have you considered trying to explicitly force the order of the items in the LinearLayout by using android:layout_below to specify the order of the items? Please forgive the newbie answer my part if there's an obvious reason to not do this. John On Wednesday, March 20, 2013 11:53:03 AM UTC-4, Larry Meadors wrote: I'm making a grid of items that has an image and two text elements under it. I want all three elements centered horizontally, and the image to be right above the text. For some reason, the image is centered vertically and the text is at the bottom. Here's a screen shot to make that clearer: https://www.evernote.com/**shard/s138/sh/6cdb585f-d523-** 47a5-a3a3-184124719e01/**ed424d6929bdbf4abd9c36e2ce4a43**90https://www.evernote.com/shard/s138/sh/6cdb585f-d523-47a5-a3a3-184124719e01/ed424d6929bdbf4abd9c36e2ce4a4390 I've tried everything I can think of... This is the grid view: GridView android:id=@+id/content_list_**grid_view android:columnWidth=90dp android:numColumns=4 android:verticalSpacing=5dp android:horizontalSpacing=**10dp android:stretchMode=**columnWidth android:layout_height=wrap_**content android:layout_width=fill_**parent android:padding=5dp / This is my item: ?xml version=1.0 encoding=utf-8? LinearLayout xmlns:android=http://schemas.**android.com/apk/res/androidhttp://schemas.android.com/apk/res/android android:layout_width=fill_**parent android:layout_height=140dp android:orientation=vertical android:gravity=bottom|**center_horizontal ImageView android:id=@+id/thumbnail_**image android:background=#40ff8080 android:layout_width=wrap_**content android:layout_height=110dp android:layout_gravity=**center_horizontal|bottom android:src=@drawable/image_**not_available_large android:contentDescription=@**string/thumbnail_image / TextView android:id=@+id/title_name android:textColor=@color/**white_color android:layout_width=wrap_**content android:layout_height=wrap_**content android:singleLine=true android:gravity=center_**horizontal style=@style/normal_label / TextView android:id=@+id/title_author android:textColor=@color/**light_gray_color android:layout_width=wrap_**content android:layout_height=wrap_**content android:singleLine=true android:gravity=center_**horizontal style=@style/normal_label / /LinearLayout -- -- 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 unsubscribe from this group and stop receiving emails from it, send an email to android-developers+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
Re: [android-developers] Re: Concurrency: Do you use Loaders? AsyncTask? or Runnables?
The onStart/onStartCommand methods of a *Service *run in the main UI thread, not a background thread, But an *IntentService*'s onHandleIntent method does run in a pooled background thread (pool has only one thread, and subsequent Intents are handled sequentially). On Wednesday, March 20, 2013 11:06:05 AM UTC-4, Kristopher Micinski wrote: Though it's worth noting that since an `IntentService` doesn't run in a background thread context. (Probably one of the biggest things beginners screw up..) Kris On Wed, Mar 20, 2013 at 9:49 AM, Streets Of Boston flying...@gmail.com javascript: wrote: There are even more ways of doing stuff in the background: IntentService :-) Runnable If you mean a Thread (running itself or a Runnable): Generally, avoid using them. But there are good use cases: When you want to setup something that runs in the background for a long time (possible during the entire lifetime of your app's process), simple Threads are very useful, e.g. set up a rendering thread for an openGL game. AsyncTasks If you want to run something in the background, that is a one-shot operation, relatively short duration and you want your UI (main UI-thread) to be notified about updates/results. If you are not worried about screen rotations/config-changes, etc., AsyncTasks work well. AsyncTasks in these situations are relatively simple to implement. Loaders, AsyncTaskLoaders Like AsyncTasks, but they are well suited to easily handle screen rotations/config-changes/etc, especially when used in conjunction with Fragments. IntentService Also good for one-shot operations with relatively short duration. Best used when you want to share these operations among other components of your or other people's applications and/or want to have Android manage its life-cycle (e.g. if an (Intent)Service is killed, Android could restart it for you automatically and re-issue the Intent that started it before). On Tuesday, March 19, 2013 8:33:50 PM UTC-4, littledot wrote: Android concurrency has always bugged me... These are all methods to achieve essentially the same thing: mutli-threading I honestly don't see much difference between them, except the amount of code you need to write.. Which methods do you use? Are there certain situations where you prefer one method over the other? Or do you stick to one method and use it as a rule-of-thumb? Thanks for reading. -- -- You received this message because you are subscribed to the Google Groups Android Developers group. To post to this group, send email to android-d...@googlegroups.comjavascript: To unsubscribe from this group, send email to android-developers+unsubscr...@googlegroups.com javascript: 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 unsubscribe from this group and stop receiving emails from it, send an email to android-developers+unsubscr...@googlegroups.com javascript:. For more options, visit https://groups.google.com/groups/opt_out. -- -- 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 unsubscribe from this group and stop receiving emails from it, send an email to android-developers+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
Re: [android-developers] Re: Concurrency: Do you use Loaders? AsyncTask? or Runnables?
Ah that's right, forgive my comment. On Mar 20, 2013 12:03 PM, Streets Of Boston flyingdutc...@gmail.com wrote: The onStart/onStartCommand methods of a *Service *run in the main UI thread, not a background thread, But an *IntentService*'s onHandleIntent method does run in a pooled background thread (pool has only one thread, and subsequent Intents are handled sequentially). On Wednesday, March 20, 2013 11:06:05 AM UTC-4, Kristopher Micinski wrote: Though it's worth noting that since an `IntentService` doesn't run in a background thread context. (Probably one of the biggest things beginners screw up..) Kris On Wed, Mar 20, 2013 at 9:49 AM, Streets Of Boston flying...@gmail.com wrote: There are even more ways of doing stuff in the background: IntentService :-) Runnable If you mean a Thread (running itself or a Runnable): Generally, avoid using them. But there are good use cases: When you want to setup something that runs in the background for a long time (possible during the entire lifetime of your app's process), simple Threads are very useful, e.g. set up a rendering thread for an openGL game. AsyncTasks If you want to run something in the background, that is a one-shot operation, relatively short duration and you want your UI (main UI-thread) to be notified about updates/results. If you are not worried about screen rotations/config-changes, etc., AsyncTasks work well. AsyncTasks in these situations are relatively simple to implement. Loaders, AsyncTaskLoaders Like AsyncTasks, but they are well suited to easily handle screen rotations/config-changes/etc, especially when used in conjunction with Fragments. IntentService Also good for one-shot operations with relatively short duration. Best used when you want to share these operations among other components of your or other people's applications and/or want to have Android manage its life-cycle (e.g. if an (Intent)Service is killed, Android could restart it for you automatically and re-issue the Intent that started it before). On Tuesday, March 19, 2013 8:33:50 PM UTC-4, littledot wrote: Android concurrency has always bugged me... These are all methods to achieve essentially the same thing: mutli-threading I honestly don't see much difference between them, except the amount of code you need to write.. Which methods do you use? Are there certain situations where you prefer one method over the other? Or do you stick to one method and use it as a rule-of-thumb? Thanks for reading. -- -- You received this message because you are subscribed to the Google Groups Android Developers group. To post to this group, send email to android-d...@**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=enhttp://groups.google.com/group/android-developers?hl=en --- You received this message because you are subscribed to the Google Groups Android Developers group. To unsubscribe from this group and stop receiving emails from it, send an email to android-developers+**unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/**groups/opt_outhttps://groups.google.com/groups/opt_out. -- -- 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 unsubscribe from this group and stop receiving emails from it, send an email to android-developers+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out. -- -- 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 unsubscribe from this group and stop receiving emails from it, send an email to android-developers+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
Re: [android-developers] Re: Concurrency: Do you use Loaders? AsyncTask? or Runnables?
That's what I get for not reading the documentation before speaking. :-) On Mar 20, 2013 12:59 PM, Kristopher Micinski krismicin...@gmail.com wrote: Ah that's right, forgive my comment. On Mar 20, 2013 12:03 PM, Streets Of Boston flyingdutc...@gmail.com wrote: The onStart/onStartCommand methods of a *Service *run in the main UI thread, not a background thread, But an *IntentService*'s onHandleIntent method does run in a pooled background thread (pool has only one thread, and subsequent Intents are handled sequentially). On Wednesday, March 20, 2013 11:06:05 AM UTC-4, Kristopher Micinski wrote: Though it's worth noting that since an `IntentService` doesn't run in a background thread context. (Probably one of the biggest things beginners screw up..) Kris On Wed, Mar 20, 2013 at 9:49 AM, Streets Of Boston flying...@gmail.com wrote: There are even more ways of doing stuff in the background: IntentService :-) Runnable If you mean a Thread (running itself or a Runnable): Generally, avoid using them. But there are good use cases: When you want to setup something that runs in the background for a long time (possible during the entire lifetime of your app's process), simple Threads are very useful, e.g. set up a rendering thread for an openGL game. AsyncTasks If you want to run something in the background, that is a one-shot operation, relatively short duration and you want your UI (main UI-thread) to be notified about updates/results. If you are not worried about screen rotations/config-changes, etc., AsyncTasks work well. AsyncTasks in these situations are relatively simple to implement. Loaders, AsyncTaskLoaders Like AsyncTasks, but they are well suited to easily handle screen rotations/config-changes/etc, especially when used in conjunction with Fragments. IntentService Also good for one-shot operations with relatively short duration. Best used when you want to share these operations among other components of your or other people's applications and/or want to have Android manage its life-cycle (e.g. if an (Intent)Service is killed, Android could restart it for you automatically and re-issue the Intent that started it before). On Tuesday, March 19, 2013 8:33:50 PM UTC-4, littledot wrote: Android concurrency has always bugged me... These are all methods to achieve essentially the same thing: mutli-threading I honestly don't see much difference between them, except the amount of code you need to write.. Which methods do you use? Are there certain situations where you prefer one method over the other? Or do you stick to one method and use it as a rule-of-thumb? Thanks for reading. -- -- You received this message because you are subscribed to the Google Groups Android Developers group. To post to this group, send email to android-d...@**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=enhttp://groups.google.com/group/android-developers?hl=en --- You received this message because you are subscribed to the Google Groups Android Developers group. To unsubscribe from this group and stop receiving emails from it, send an email to android-developers+**unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/**groups/opt_outhttps://groups.google.com/groups/opt_out. -- -- 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 unsubscribe from this group and stop receiving emails from it, send an email to android-developers+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out. -- -- 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 unsubscribe from this group and stop receiving emails from it, send an email to android-developers+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
Re: [android-developers] Re: Making my app the only one that can run.
On 03/20/2013 07:50 AM, bob wrote: I used an app in Google Play called */SureLock Kiosk Lockdown/*. Wow, that is perfect! Unfortunately the license is too expensive. We are going to have hundreds of units, and and at $50 a pop, that adds up quickly. It's a shame. We'd probably pay $10 without blinking. Tobiah On Tuesday, March 19, 2013 4:35:56 PM UTC-5, Tobiah wrote: I'm not being unfriendly to users. I need to hand out devices at an event so that people can walk around and use my app. I don't want them to use other apps on the phone. So I put this in my AndroidManifest.xml: intent-filter action android:name=android.intent.action.MAIN / category android:name=android.intent.category.LAUNCHER / category android:name=android.intent.category.HOME / category android:name=android.intent.category.DEFAULT / /intent-filter Then I get a choice of launchers from the home button. I choose my app 'Always' and everything is great. The only problem is that if I reboot the device, my app indeed comes up as the home screen, but it immediately crashes. Is there some event or Intent I need to handle to do this? I can't figure out how to debug this, because there are no logcat events, and when I restart my app it works fine. Also if there are any other thoughts on how to make a one app device, I'd love to have suggestions. Thanks! Tobiah -- -- 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 unsubscribe from this group and stop receiving emails from it, send an email to android-developers+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out. -- -- 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 unsubscribe from this group and stop receiving emails from it, send an email to android-developers+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
Re: [android-developers] Re: Making my app the only one that can run.
On 03/20/2013 05:38 AM, Android2ee wrote: Hi, You should build your own home activity ( a real one that handles all the events needed to be handled by a home) then at each key methods of your activity (onResume, onCreate) you just launch your apllication using the intent (startActivity(intent)). If building a home is a too huge work, a home is already available (under apache licence) in the sdk, to be exact in the sample of the sdk. Then, as you did, just set this home as the default one on the devices you want to manage. I have the project to make such application for my kid allowing him to use only some applications (the ones I decided). Hope it helps. Mathias Seguy Founder of Android2EE Hey thanks for the advice. This looks like the way to go. I'll check out the sample launcher. Are there docs somewhere outlining which methods must be handled? Tobiah Le mardi 19 mars 2013 22:35:56 UTC+1, Tobiah a écrit : I'm not being unfriendly to users. I need to hand out devices at an event so that people can walk around and use my app. I don't want them to use other apps on the phone. So I put this in my AndroidManifest.xml: intent-filter action android:name=android.intent.action.MAIN / category android:name=android.intent.category.LAUNCHER / category android:name=android.intent.category.HOME / category android:name=android.intent.category.DEFAULT / /intent-filter Then I get a choice of launchers from the home button. I choose my app 'Always' and everything is great. The only problem is that if I reboot the device, my app indeed comes up as the home screen, but it immediately crashes. Is there some event or Intent I need to handle to do this? I can't figure out how to debug this, because there are no logcat events, and when I restart my app it works fine. Also if there are any other thoughts on how to make a one app device, I'd love to have suggestions. Thanks! Tobiah -- -- 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 unsubscribe from this group and stop receiving emails from it, send an email to android-developers+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out. -- -- 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 unsubscribe from this group and stop receiving emails from it, send an email to android-developers+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
Re: [android-developers] Re: Concurrency: Do you use Loaders? AsyncTask? or Runnables?
Thank you all for the kind and enthusiastic responses; they were all very insightful to help my understanding of Android concurrency =D In many of these responses, many spoke of threads being *managed* for you. This term is very vague to me because in the Ref pages for AsyncTask and Loaders, there are no mentions of how Android manages worker threads during different app lifecycles. http://developer.android.com/reference/android/os/AsyncTask.html http://developer.android.com/reference/android/content/Loader.html (Ctrl-F manag *nothing*) In the Loaders API Guide page, it says it helps manage during a configuration change, but what kind of change constitutes a config change? (Maybe after resuming, coming back from a screen lock, change in orientation, etc?) http://developer.android.com/guide/components/loaders.html *Can you tell me what kind of management support AsyncTasks and Loaders have that are different from Runnables (or that Runnables lack) ?* Thank you for reading. On Wed, Mar 20, 2013 at 2:15 PM, Kristopher Micinski krismicin...@gmail.com wrote: That's what I get for not reading the documentation before speaking. :-) On Mar 20, 2013 12:59 PM, Kristopher Micinski krismicin...@gmail.com wrote: Ah that's right, forgive my comment. On Mar 20, 2013 12:03 PM, Streets Of Boston flyingdutc...@gmail.com wrote: The onStart/onStartCommand methods of a *Service *run in the main UI thread, not a background thread, But an *IntentService*'s onHandleIntent method does run in a pooled background thread (pool has only one thread, and subsequent Intents are handled sequentially). On Wednesday, March 20, 2013 11:06:05 AM UTC-4, Kristopher Micinski wrote: Though it's worth noting that since an `IntentService` doesn't run in a background thread context. (Probably one of the biggest things beginners screw up..) Kris On Wed, Mar 20, 2013 at 9:49 AM, Streets Of Boston flying...@gmail.com wrote: There are even more ways of doing stuff in the background: IntentService :-) Runnable If you mean a Thread (running itself or a Runnable): Generally, avoid using them. But there are good use cases: When you want to setup something that runs in the background for a long time (possible during the entire lifetime of your app's process), simple Threads are very useful, e.g. set up a rendering thread for an openGL game. AsyncTasks If you want to run something in the background, that is a one-shot operation, relatively short duration and you want your UI (main UI-thread) to be notified about updates/results. If you are not worried about screen rotations/config-changes, etc., AsyncTasks work well. AsyncTasks in these situations are relatively simple to implement. Loaders, AsyncTaskLoaders Like AsyncTasks, but they are well suited to easily handle screen rotations/config-changes/etc, especially when used in conjunction with Fragments. IntentService Also good for one-shot operations with relatively short duration. Best used when you want to share these operations among other components of your or other people's applications and/or want to have Android manage its life-cycle (e.g. if an (Intent)Service is killed, Android could restart it for you automatically and re-issue the Intent that started it before). On Tuesday, March 19, 2013 8:33:50 PM UTC-4, littledot wrote: Android concurrency has always bugged me... These are all methods to achieve essentially the same thing: mutli-threading I honestly don't see much difference between them, except the amount of code you need to write.. Which methods do you use? Are there certain situations where you prefer one method over the other? Or do you stick to one method and use it as a rule-of-thumb? Thanks for reading. -- -- You received this message because you are subscribed to the Google Groups Android Developers group. To post to this group, send email to android-d...@**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=enhttp://groups.google.com/group/android-developers?hl=en --- You received this message because you are subscribed to the Google Groups Android Developers group. To unsubscribe from this group and stop receiving emails from it, send an email to android-developers+**unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/**groups/opt_outhttps://groups.google.com/groups/opt_out. -- -- 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
Re: [android-developers] Re: Concurrency: Do you use Loaders? AsyncTask? or Runnables?
Loafers are built on top of asynctasks. They manage the gui vs. background threads for you. If you just *read* the reference page to which you link, it should describe the procedure. The main idea is that you can publish results on UI elements and still do background work, with coordination between the background thread and gui. Kris On Mar 20, 2013 1:37 PM, Chang Sheng-Dean 章聖典 littledot5...@gmail.com wrote: Thank you all for the kind and enthusiastic responses; they were all very insightful to help my understanding of Android concurrency =D In many of these responses, many spoke of threads being *managed* for you. This term is very vague to me because in the Ref pages for AsyncTask and Loaders, there are no mentions of how Android manages worker threads during different app lifecycles. http://developer.android.com/reference/android/os/AsyncTask.html http://developer.android.com/reference/android/content/Loader.html (Ctrl-F manag *nothing*) In the Loaders API Guide page, it says it helps manage during a configuration change, but what kind of change constitutes a config change? (Maybe after resuming, coming back from a screen lock, change in orientation, etc?) http://developer.android.com/guide/components/loaders.html *Can you tell me what kind of management support AsyncTasks and Loaders have that are different from Runnables (or that Runnables lack) ?* Thank you for reading. On Wed, Mar 20, 2013 at 2:15 PM, Kristopher Micinski krismicin...@gmail.com wrote: That's what I get for not reading the documentation before speaking. :-) On Mar 20, 2013 12:59 PM, Kristopher Micinski krismicin...@gmail.com wrote: Ah that's right, forgive my comment. On Mar 20, 2013 12:03 PM, Streets Of Boston flyingdutc...@gmail.com wrote: The onStart/onStartCommand methods of a *Service *run in the main UI thread, not a background thread, But an *IntentService*'s onHandleIntent method does run in a pooled background thread (pool has only one thread, and subsequent Intents are handled sequentially). On Wednesday, March 20, 2013 11:06:05 AM UTC-4, Kristopher Micinski wrote: Though it's worth noting that since an `IntentService` doesn't run in a background thread context. (Probably one of the biggest things beginners screw up..) Kris On Wed, Mar 20, 2013 at 9:49 AM, Streets Of Boston flying...@gmail.com wrote: There are even more ways of doing stuff in the background: IntentService :-) Runnable If you mean a Thread (running itself or a Runnable): Generally, avoid using them. But there are good use cases: When you want to setup something that runs in the background for a long time (possible during the entire lifetime of your app's process), simple Threads are very useful, e.g. set up a rendering thread for an openGL game. AsyncTasks If you want to run something in the background, that is a one-shot operation, relatively short duration and you want your UI (main UI-thread) to be notified about updates/results. If you are not worried about screen rotations/config-changes, etc., AsyncTasks work well. AsyncTasks in these situations are relatively simple to implement. Loaders, AsyncTaskLoaders Like AsyncTasks, but they are well suited to easily handle screen rotations/config-changes/etc, especially when used in conjunction with Fragments. IntentService Also good for one-shot operations with relatively short duration. Best used when you want to share these operations among other components of your or other people's applications and/or want to have Android manage its life-cycle (e.g. if an (Intent)Service is killed, Android could restart it for you automatically and re-issue the Intent that started it before). On Tuesday, March 19, 2013 8:33:50 PM UTC-4, littledot wrote: Android concurrency has always bugged me... These are all methods to achieve essentially the same thing: mutli-threading I honestly don't see much difference between them, except the amount of code you need to write.. Which methods do you use? Are there certain situations where you prefer one method over the other? Or do you stick to one method and use it as a rule-of-thumb? Thanks for reading. -- -- You received this message because you are subscribed to the Google Groups Android Developers group. To post to this group, send email to android-d...@**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=enhttp://groups.google.com/group/android-developers?hl=en --- You received this message because you are subscribed to the Google Groups Android Developers group. To unsubscribe from this group and stop receiving emails from it, send an email to android-developers+**unsubscr...@googlegroups.com. For more options,
Re: [android-developers] Android Games SDK?
Try corona or starling sdk, with they you can develop to any kind of plataforms On Wed, Mar 20, 2013 at 10:09 AM, Jim Graham spooky1...@gmail.com wrote: On Wed, Mar 20, 2013 at 05:42:58AM -0700, Taylor Ringo wrote: Are there any game development SDK's by google, or some other established developers? I'm programming in JAVA. As to SDKs, I don't know. However, there are at least two popular game engine libs, libgdx and andengine, which is (or at least, used to be, and probably still is) based on libgdx. Later, --jim -- THE SCORE: ME: 2 CANCER: 0 73 DE N5IAL (/4)MiSTie #49997 Running Mac OS X Lion spooky1...@gmail.com ICBM/Hurricane: 30.44406N 86.59909W In light of DHS's recommendation to defend yourself against armed intruders with scissors, I'm giving my deer rifle a new nickname: Scissors. -- -- 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 unsubscribe from this group and stop receiving emails from it, send an email to android-developers+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out. -- att, Pedro Cortez -- -- 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 unsubscribe from this group and stop receiving emails from it, send an email to android-developers+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[android-developers]
hi all , I am working on getting google adsense adds to work on my test android mobile application.Can someone please help me get it working ? I always get an error and it stops working even before the launch. -- ThanksRegards Kaushik Pendurthi http://kaushikpendurthi.blogspot.com/ -- -- 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 unsubscribe from this group and stop receiving emails from it, send an email to android-developers+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[android-developers] Re: I'm missing something dumb here...
I would say just make each one of those squares an image. Just draw both text items onto the image. Then it will just be a grid of images. Thanks. On Wednesday, March 20, 2013 10:53:03 AM UTC-5, Larry Meadors wrote: I'm making a grid of items that has an image and two text elements under it. I want all three elements centered horizontally, and the image to be right above the text. For some reason, the image is centered vertically and the text is at the bottom. Here's a screen shot to make that clearer: https://www.evernote.com/shard/s138/sh/6cdb585f-d523-47a5-a3a3-184124719e01/ed424d6929bdbf4abd9c36e2ce4a4390 I've tried everything I can think of... This is the grid view: GridView android:id=@+id/content_list_grid_view android:columnWidth=90dp android:numColumns=4 android:verticalSpacing=5dp android:horizontalSpacing=10dp android:stretchMode=columnWidth android:layout_height=wrap_content android:layout_width=fill_parent android:padding=5dp / This is my item: ?xml version=1.0 encoding=utf-8? LinearLayout xmlns:android=http://schemas.android.com/apk/res/android; android:layout_width=fill_parent android:layout_height=140dp android:orientation=vertical android:gravity=bottom|center_horizontal ImageView android:id=@+id/thumbnail_image android:background=#40ff8080 android:layout_width=wrap_content android:layout_height=110dp android:layout_gravity=center_horizontal|bottom android:src=@drawable/image_not_available_large android:contentDescription=@string/thumbnail_image / TextView android:id=@+id/title_name android:textColor=@color/white_color android:layout_width=wrap_content android:layout_height=wrap_content android:singleLine=true android:gravity=center_horizontal style=@style/normal_label / TextView android:id=@+id/title_author android:textColor=@color/light_gray_color android:layout_width=wrap_content android:layout_height=wrap_content android:singleLine=true android:gravity=center_horizontal style=@style/normal_label / /LinearLayout -- -- 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 unsubscribe from this group and stop receiving emails from it, send an email to android-developers+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
Re: [android-developers] Re: Making my app the only one that can run.
The pricing page is right here: http://www.42gears.com/surelock/androidpurchase.html Please note this: SureLock Android 100 License Pack $1299 Thus, if it is hundreds of units you have, you should not have to pay more than *12.99* a pop. On Wednesday, March 20, 2013 1:24:36 PM UTC-5, Tobiah wrote: On 03/20/2013 07:50 AM, bob wrote: I used an app in Google Play called */SureLock Kiosk Lockdown/*. Wow, that is perfect! Unfortunately the license is too expensive. We are going to have hundreds of units, and and at $50 a pop, that adds up quickly. It's a shame. We'd probably pay $10 without blinking. Tobiah On Tuesday, March 19, 2013 4:35:56 PM UTC-5, Tobiah wrote: I'm not being unfriendly to users. I need to hand out devices at an event so that people can walk around and use my app. I don't want them to use other apps on the phone. So I put this in my AndroidManifest.xml: intent-filter action android:name=android.intent.action.MAIN / category android:name=android.intent.category.LAUNCHER / category android:name=android.intent.category.HOME / category android:name=android.intent.category.DEFAULT / /intent-filter Then I get a choice of launchers from the home button. I choose my app 'Always' and everything is great. The only problem is that if I reboot the device, my app indeed comes up as the home screen, but it immediately crashes. Is there some event or Intent I need to handle to do this? I can't figure out how to debug this, because there are no logcat events, and when I restart my app it works fine. Also if there are any other thoughts on how to make a one app device, I'd love to have suggestions. Thanks! Tobiah -- -- You received this message because you are subscribed to the Google Groups Android Developers group. To post to this group, send email to android-d...@googlegroups.comjavascript: To unsubscribe from this group, send email to android-developers+unsubscr...@googlegroups.com javascript: 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 unsubscribe from this group and stop receiving emails from it, send an email to android-developers+unsubscr...@googlegroups.com javascript:. For more options, visit https://groups.google.com/groups/opt_out. -- -- 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 unsubscribe from this group and stop receiving emails from it, send an email to android-developers+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[android-developers] Re: New SDK release for Egnos
Hello again, the EGNOS SDK is being increasingly adopted by the developers community to create apps based on superior positioning. It was successfully implemented the EGNOS SDK within the application GeoPointer™ M3 for Mobile Logistics. You can find out more in the Test Testimonials section of the EGNOS SDK webpages: http://www.egnos-portal.eu/developer-platform/egnos-toolkits/egnos-sdk/tests-and-testimonials Cheers, Leonardo On Wednesday, 13 March 2013 11:51:47 UTC+1, Leonardo Costa wrote: Hello! The European Commission wanted me to remind you that the EGNOS SDK v3 is fully available for different OS: access the EGNOS portal for downloading your version of the toolkit (Download the EGNOS SDK). You can also check the compatibility of your OS version. If you encounter any problem in your development or just want to discuss some issues about the EGNOS SDK, using the Demo App or the SDK Core, refer to the supporting documentation. If you do not find an answer to your questions, directly write us at: egnos.toolk...@gsa.europa.eu. More simply, you can just ask by replying to this post :-). I will be glad to help! On Tuesday, 31 July 2012 23:20:39 UTC+2, Leonardo Costa wrote: Hello, I'm posting this info on behalf of the European Commission, the new release of the EGNOS SDK for app developers is now available. This EGNOS SDK allows taking advantage of the European system that provides enhanced positioning accuracy and other features (e.g. information on the reliability of the position itself) directly towards the smartphones. It is available for free on the EGNOS Portal at http://egnos-portal.gsa.europa.eu/developer-platform/egnos-toolkits/egnos-sdk I am available for any further info, request, questions, you may have on this topic and will post reply here. I will also post further details in the next weeks, following up directly at this thread. Thanks and regards, Leonardo -- -- 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 unsubscribe from this group and stop receiving emails from it, send an email to android-developers+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[android-developers] Re: How to determine application's method count?
Adding Google Drive adds things like: google-api-client-android-1.12.0-beta.jar google-api-services-drive-v2-rev59-1.12.0-beta.jar google-http-client-1.12.0-beta.jar google-http-client-android-1.12.0-beta.jar google-http-client-gson-1.12.0-beta.jar google-http-client-jackson-1.12.0-beta.jar google-http-client-jackson2-1.12.0-beta.jar google-oauth-client-1.12.0-beta.jar Dropbox requires: commons-logging.jar httpclient-4.0.3.jar http-core-4.0.3.jar httmpmime-4.0.3.jar json_simple-1.1.jar Box requirues: gson-renamed-2.2.2.jar On Wednesday, 20 March 2013 10:33:00 UTC-4, bob wrote: Well, what 3rd party JARs are you using? Thanks. On Tuesday, March 19, 2013 4:02:54 PM UTC-5, Ab wrote: I'm encountering issues with my application having to many methods. In the last post in the below link, a poster posts the method count for his application (broken down by package). I unable to find how I can get this information for my application, any suggestions? https://code.google.com/p/android/issues/detail?id=20814 -- -- 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 unsubscribe from this group and stop receiving emails from it, send an email to android-developers+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[android-developers] Re:
Make sure you add that *Provider* line to your AndroidManifest.xml. On Wednesday, March 20, 2013 3:06:34 PM UTC-5, kaushikpendurthi wrote: hi all , I am working on getting google adsense adds to work on my test android mobile application.Can someone please help me get it working ? I always get an error and it stops working even before the launch. -- ThanksRegards Kaushik Pendurthi http://kaushikpendurthi.blogspot.com/ -- -- 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 unsubscribe from this group and stop receiving emails from it, send an email to android-developers+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
Re: [android-developers] Android Games SDK?
A member of this forum works on http://www.batterytechsdk.com/ Haven't used it yet. The person, Robert Green, is doing a Hackathon at AnDevCon that I plan to be at. http://www.andevcon.com/AnDevCon_Boston/tutorials.html You can save $200 on Andevcon by using the discount code 'Mellor' at registration. 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 --- You received this message because you are subscribed to the Google Groups Android Developers group. To unsubscribe from this group and stop receiving emails from it, send an email to android-developers+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
Re: [android-developers] Re: Making my app the only one that can run.
On 03/20/2013 02:22 PM, bob wrote: The pricing page is right here: http://www.42gears.com/surelock/androidpurchase.html Please note this: SureLock Android 100 License Pack $1299 Better, but it seems that the program has to 'Phone Home' to verify the license against the phone's id# or wifi mac address. My devices will go for long periods without internet access. There are some far cheaper alternatives that do the same thing anyway. LOCKiosk works fine for $8. I'm trying to find out if that's a one time fee or a per device fee. Tobiah Thus, if it is hundreds of units you have, you should not have to pay more than *12.99* a pop. On Wednesday, March 20, 2013 1:24:36 PM UTC-5, Tobiah wrote: On 03/20/2013 07:50 AM, bob wrote: I used an app in Google Play called */SureLock Kiosk Lockdown/*. Wow, that is perfect! Unfortunately the license is too expensive. We are going to have hundreds of units, and and at $50 a pop, that adds up quickly. It's a shame. We'd probably pay $10 without blinking. Tobiah On Tuesday, March 19, 2013 4:35:56 PM UTC-5, Tobiah wrote: I'm not being unfriendly to users. I need to hand out devices at an event so that people can walk around and use my app. I don't want them to use other apps on the phone. So I put this in my AndroidManifest.xml: intent-filter action android:name=android.intent.action.MAIN / category android:name=android.intent.category.LAUNCHER / category android:name=android.intent.category.HOME / category android:name=android.intent.category.DEFAULT / /intent-filter Then I get a choice of launchers from the home button. I choose my app 'Always' and everything is great. The only problem is that if I reboot the device, my app indeed comes up as the home screen, but it immediately crashes. Is there some event or Intent I need to handle to do this? I can't figure out how to debug this, because there are no logcat events, and when I restart my app it works fine. Also if there are any other thoughts on how to make a one app device, I'd love to have suggestions. Thanks! Tobiah -- -- You received this message because you are subscribed to the Google Groups Android Developers group. To post to this group, send email to android-d...@googlegroups.com javascript: To unsubscribe from this group, send email to android-developers+unsubscr...@googlegroups.com javascript: For more options, visit this group at http://groups.google.com/group/android-developers?hl=en 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 unsubscribe from this group and stop receiving emails from it, send an email to android-developers+unsubscr...@googlegroups.com javascript:. For more options, visit https://groups.google.com/groups/opt_out https://groups.google.com/groups/opt_out. -- -- 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 unsubscribe from this group and stop receiving emails from it, send an email to android-developers+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out. -- -- 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 unsubscribe from this group and stop receiving emails from it, send an email to android-developers+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
Re: [android-developers] Getting the problem while fetching the current location...?
I am currently traveling with no access to the code. I also need to make sure I get the attribution right as the hack was developed by someone else. As for the why - my guess it is a botched attempt by Samsung to mess with the GPS radio power management. On Wednesday, March 20, 2013 10:42:18 AM UTC-5, Kristopher Micinski wrote: I'm interested as to why their implementation would differ from the standard API, do you have any specific reason for not putting an example on github, or would you care to share the trick..? (I'm just interested because it seems like a stupid decision on the vendor's part to break things..) Kris On Wed, Mar 20, 2013 at 11:09 AM, lbendlin lu...@bendlin.us javascript: wrote: Some Galaxy devices (especially the Spica) require an alternative way of starting up the location listener. Ping me if you want the code. -- -- You received this message because you are subscribed to the Google Groups Android Developers group. To post to this group, send email to android-d...@googlegroups.comjavascript: To unsubscribe from this group, send email to android-developers+unsubscr...@googlegroups.com javascript: 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 unsubscribe from this group and stop receiving emails from it, send an email to android-developers+unsubscr...@googlegroups.com javascript:. For more options, visit https://groups.google.com/groups/opt_out. -- -- 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 unsubscribe from this group and stop receiving emails from it, send an email to android-developers+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
Re: [android-developers] Re: Concurrency: Do you use Loaders? AsyncTask? or Runnables?
On Thu, Mar 21, 2013 at 3:48 AM, Kristopher Micinski krismicin...@gmail.com wrote: Loafers are built on top of asynctasks. +1 for 'loafers' :) -- -- 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 unsubscribe from this group and stop receiving emails from it, send an email to android-developers+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
Re: [android-developers]
On Wed, Mar 20, 2013 at 3:06 PM, Kaushik Pendurthi kaushiks...@gmail.comwrote: I am working on getting google adsense adds to work on my test android mobile application. OK. Can someone please help me get it working ? Help you how? You've provided nearly zero information about your problem. I always get an error and it stops working even before the launch. What error? What does stops working mean? We're not mind readers. Read this: http://www.catb.org/esr/faqs/smart-questions.html, provide more information, and try again. - TreKing http://sites.google.com/site/rezmobileapps/treking - Chicago transit tracking app for Android-powered devices -- -- 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 unsubscribe from this group and stop receiving emails from it, send an email to android-developers+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[android-developers] What is the data usage warning issue
Hi friends, There is a message prompt called *Data usage warning *in my android mobile.(xperia arc s) *how can i fix it. What is this...?* * * *Please give me a suitable answers for this.* https://lh4.googleusercontent.com/-uCh38Nac1MM/UUp9hzvuv3I/EWI/KW8Gfe9yCqM/s1600/Screenshot_2013-03-19-07-08-09.png * * -- -- 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 unsubscribe from this group and stop receiving emails from it, send an email to android-developers+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[android-developers] Language Translator
*Hello friends, * * * *is there any way to translate language in android app. Help me ,how to do that.?* * * *thnkx.* -- -- 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 unsubscribe from this group and stop receiving emails from it, send an email to android-developers+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[android-developers] Having common code for both phone and tablet Android
Hi All, For our project we our supporting from android 2.3 onward on phone and as well as for tablets 3.0 onward. I would like to have common code base and UI for both. But found that from 3.0 onward. some classes like fragments, loaders are support where as below this version its not. So which would be the best practice to keep the code common (or maximize the common code). Thanks 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 --- You received this message because you are subscribed to the Google Groups Android Developers group. To unsubscribe from this group and stop receiving emails from it, send an email to android-developers+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
Re: [android-developers] Having common code for both phone and tablet Android
On Wed, Mar 20, 2013 at 11:47 PM, Mamatha K mamatha...@gmail.com wrote: For our project we our supporting from android 2.3 onward on phone and as well as for tablets 3.0 onward. I would like to have common code base and UI for both. But found that from 3.0 onward. some classes like fragments, loaders are support where as below this version its not. So which would be the best practice to keep the code common (or maximize the common code). http://developer.android.com/tools/extras/support-library.html - TreKing http://sites.google.com/site/rezmobileapps/treking - Chicago transit tracking app for Android-powered devices -- -- 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 unsubscribe from this group and stop receiving emails from it, send an email to android-developers+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[android-developers] why cannot we play local videos from SD card using Iframe inside webview?
I have googled a lot. I read about Stagewebview Bridge and Adobe Air... In some articles they have said , 1) can enable Browser plugins 2) Can play via Flash player (So have to Install it) Now, i am getting a Question. Cant we play local videos from SD card inside webview using Iframe tag on Android 2.2 version ? Please anyone suggest me about this ! I am struggling for this ! Any help or suggestions is highly appreciated, thanks ! -- -- 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 unsubscribe from this group and stop receiving emails from it, send an email to android-developers+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
