Following is the example of tabs with intent data.
While debugging i found that always when first tab we add in tab host in our case following tab
CODE:................
oncreate method of "List1" intent get called regardless it is our current tab or not even if if i define tab2 as a current tab how to fix this ?
CODE:..........................
View 1 Replies
I have a TabActivity with 3 tabs, each tab started an activity and I realise when a tab is clicked onResume is call. If I have onCreate, when app start it will launch onCreate and then onResume immediately.So, I can just get ride of onCreate in this case?
View 2 Replies View RelatedI make 'hello world' app :-) and wrote a Log code in onCreate. and then give "android.intent.category.DEFAULT" and "android.intent.category.HOME"
This situation appears emulator(1.5, 2.0, 2.1). but HTC hero(1.5, original htc rom) didn't! it just call one time! Which is normal? and If calling twice is normal, why are they call twice?
I launch my TestWebView activity. After my web page is loaded, I put the app in the background by pressing the Home key. Then I bring the TestWebActivity back to the foreground. Unexpectedly, TestWebView's onCreate() is called when I bring the activity to the foreground. But onDestroy is never called. This same thing happens every time I tested. It appears the old TestWebView was not completely killed so there are possibly duplicate web clients running.
My code: .....
I have some code in the onCreate method an Activity and noticed that it is being called three times. Is it normal behaviour?
View 1 Replies View RelatedThe order is:
A: startActivityForResult( B ) B: <dostuff>, call finish() A: onCreate <---- what's this all about A: onActivityResult
This happens for a tiny minority of users. I havn't been able to reproduce or find any common elements. A is the launch activity.
CODE:..............
I got my hands on Android which is really fun. But at some point I don't seem to understand the concept. I've got a Main class which reads like this:
CODE:....
In the onCreate(...) I set the layout to setContentView(R.layout.main); and add an OnTouchEvent Listener to the sole View in main.xml: myView.setOnTouchListener(new OnTouchListener() {@Override public boolean onTouch(View v, MotionEvent event){...
As you can see I also implemented a SensorEventListener which is used if required. All works fine so far.
But my problem is this (at this point my misunderstanding kicks in): whenever I rotate the device the onCreate(), onStart() etc. methods are called, causing my app to act as if it just started. Furthermore, I feel unable to implement an onSizeChanged(int w, int h, int oldw, int oldh) { ... } Listener.
Can anyone please explain where my error in reasoning is? I am working on a tiny app which is more or less done, except for the just mentioned bug(s). Maybe I got it all wrong but it does what it is supposed to do (i.e. sending touch positions and accelerometer data over the network via UDP).
In my android app I call the voice recognition in my onCreate method of my startup activity. I have made it a preference to start up with the voice control or not. However, the app takes about 5-7 seconds to load when voice recognition is on. When it is off, the app starts almost instantly. Below is sample code, I have added Free_Form, max_results 1, and a custom prompt to mine.Why would calling the normal android speech recognition take sooo long to load in my OnCreate method?
View 1 Replies View RelatedAndroid will call onCreate() of my activity whenever it is launched.
In the onCreate() of my activity can I tell what intent launches my activity?
Maybe my question might seem a bit weird, but I have an activity in which, in one case , I have to move to another activity before it finishes loading the screen. My condition is in the onCreate method, which means when I encounter it, i get a "startActivity called from outside an activity context" error and the app just crashes. But then, is there an easy way like a flag for the intent to make it work without having the activity context resolved?
View 1 Replies View RelatedI start an IMAGE_CAPTURE Intent like this, and my activity's onActivityResult() get called: Intent i = new Intent (android.provider.MediaStore.ACTION_IMAGE_CAPTURE, null); i.putExtra("return-data", true);
startActivityForResult(i, PICK_ICON_FROM_CAMERA_ID);
But, if I start my Intent like this, the Capture Image Intent did get called, but my activity's onActivityResult() never get called:
Intent i = new Intent (android.provider.MediaStore.ACTION_IMAGE_CAPTURE, null); i.putExtra(MediaStore.EXTRA_OUTPUT, Uri.parse("file:/" + "MyTestFile")); i.putExtra("outputFormat", Bitmap.CompressFormat.PNG.name());
startActivityForResult(i, PICK_ICON_FROM_CAMERA_ID);
I'm using Eclipse and have an emulator running Android 2.1 and my IntentService. I'd like to step through my onHandleIntent() overridden function. I've put in a breakpoint on the first statement of the function, which is Context context = getBaseContext();. When the intent is called the program just fails and does not go to debug view in Eclipse.
View 1 Replies View RelatedI have the following issue. I am starting a recognizer intent activity in order to detect speech using the "startActivityForResult" method. I have also an "onActivityResult" method listening for results from the recognizer activity. It works and it detects my speech. The problem is that it is only called when everything is ok or when i cancel the operation, but it is not called if it doesn't find a matching text "RecognizerIntent.RESULT_NO_MATCH" or in the rest of wrong cases "RecognizerIntent.RESULT_........" What is happening? Application is Android 2.1 and I have tested on a Android 2.2 device.
View 1 Replies View RelatedI have an application where i have a TabHost with 3 tabs.I have a ScrollView in tab2 and also another ScrollView in tab1. The problem is my ScrollView in tab2 shows up in tab1 too (the scroll bar is showing up).
My main.xml is given below. Name of tab1 scrollview : @+id/ScrollViewOuputText Name of tab2 scrollview :
CODE:................
I have application in landscape orientation, I set it as <android:screen Orientation="landscape"> in Android Manifest.xml. But when my app starts another activity - default internet browser - it starts in portrait orientation.
View 9 Replies View RelatedTrying to grok intents and actions in android and looking through the documentation. But one thing I keep seeing is an intent filter with multiple actions defined.
Like this, from the above link:
CODE:...........
But, if you call that activity, how does it choose which action is chosen?
For that matter, that linked to example has multiple activities that all contain the same actions, "android.intent.action.VIEW" for example. When calling this with something like content://com.google.provider.NotePad/notes how does it even know which activity to use?
I'm posting this to share the lessons I learned while working with IntentService. IntentService has a single constructor that takes a string argument "name". The documentation has no description of what name is used for. In looking at the sources, I found that its only use is in naming the worker thread for the IntentService. This thread is named IntentService [name].
I initially implemented the constructor of the derived class to also take a String argument and passed it along to the derived class. This is wrong. This will cause the startService() call to generated a java.lang.InstantiationException in the application containing the service i.e. you don't get the exception in the application calling startService(). A clue to the actual problem is a little further up in the logs:"newInstance failed: no <init>()"
The derived class must have a Default constructor and that constructor must call super() passing a string for the name component of the worker thread name.
public class MyIntentService extends IntentService {
public MyIntentService() { super("MyIntentService");
} @Override
protected void onHandleIntent(Intent intent) {
// Handle events on worker thread here }
I am customizing native phonebook application as a third party application which can be launched by the same intent as the native application. I have installed that application in my G1 phone. When I have clicked on Contacts icon in launcher menu it a menu pops out and asks me to select which app to lauch i.e., native contacts or my customized contact application. I have selected my application and I have also selected to use this selection as my default choice. After that system never put a pop-up and whenever I clicked on contacts it launches my customized application.
Now my problem is, I do not know how do I change this setting i.e., tell the phone to put the pop-up again so that I can select native app or my app?
Does anyone has any idea?
I need to push an intent to default camera application to make it take a photo, save it and return an URI. Is there any way to do this?
View 2 Replies View RelatedI have the Samsung Galaxy Tab2 10.1 and was today notified that an update was ready. I installed this which was the upgrade to 4.2.2
However since then, none of my apps will work. There is a short pause before I get:
"Unfortunately Coin Dozer has stopped"
"Unfortunately Lookout has stopped"
"Unfortunately Tiny Castle has stopped"
"Unfortunately Candy Crush Saga has stopped"
etc.
I tried a reboot a couple of times but that didn't work. Checked to see if Upgrades were available for all affected apps but there are none.
I am running into an issue with the way my asynctasks are executed. Here's the problem code:
firstTask = new background().new FirstTask(context);
if(firstTask.execute().get().toString().equals("1"))
secondTask = new background().new SecondTask(context);
What I'm doing here is creating a new asynctask object, assigning it to firstTask and then executing it. I then want to fire off a separate asynctask when the first one is done and making sure it returns a success value (1 in this case). This works perfectly on Android 2.0 and up. However, I am testing with Android 1.5 and problems start popping up. The code above will run the first asynctask but doInBackground() is never called despite onPreExecute() being called. If I am to execute the first task without the get() method, doInBackground() is called and everything works as expected. Except now I do not have a way to determine if the first task completed successfully so that I can tell the second task to execute. Is it safe to assume that this is a bug with asynctask on Android 1.5? Especially since the API says that the get method has been implemented since API 3. Is there any way to fix this? Or another way to determine that the first task has finished?
My prob is the following: My android application has the class TestActivity (entrypoint) -my app uses "library.jar" wich contains J2ME classes, used as library -library.jar also includes "UIActivity" [can spawn several dialogs] wich is called by a (j2me) class of library.jar -I only have the .class files of the j2me-lib stuff, so I cant modify them, but I can do so on Android-classes
so... the short form:
CODE:.............
finally I get the error:
CODE:.............
Do I have to use Services instead of Activities? But afaik I have to give a reference of an activity to spawn dialogs.
Leaving aside the lamentable wording of the documentation for this method, it's not really acting as I hoped for an ImageView. I call toggle() from the onClick method of the view but the view system does not redraw my drawable with the checked state. However, if I initialize CHECKED_STATE_SET with android.R.attr.state_checked then the view is draw with the checked state.
So apparently my call to setImageState is not updating the state of the ImageView. The documentation for setImageState is totally blank in the case of an ImageView. What does this mean?
Here's my code:................................
I have been looking it up and I just cant seem to wrap myself around the onCreate and Bundles. I understand that the onCreate is called when the program starts but its how the Bundles get passed around and how they are pertinent. Can anyone try to put this into plain english because I cant seem to find it well described.
View 1 Replies View RelatedI have an activity that checks stuffs online when it's created (is the GPS on and if not it asks if the user wants to turn it on).
The problem I'm having is that it is also doing it everytime I change the orientation of the screen.
I've read some comments on onConfigurationChanged() but is there a better way to be sure I'm checking the GPS only when the activity is first created?
I try to call inside onCreate() it is ok but not onClick(). How to make it work?
View 3 Replies View RelatedI'm having a hard time resolving a crash report. It's an OutOfMemory exception that occurs during the setContentView in the onCreate of my main activity.
I just want to be sure I understood Android LifeCycle well :
1) The onCreate of my main activity is called once and only once during the life time of my application ? Is that correct ?
2) Just like for the big bang, before the oncreate of my activity, nothing exists for that activity, so memory consumption is zero, no objects exists right ?
So what can cause that sometimes, with random framework and devices, I get an OOM exception ? I mean if say my background image is causing this, it should blow up everytime, on every device, shouldn't it ? I mean the result should be reliable.
The background image is a standard jpg : 360*480 weighing 37kb, nothing fancy really :s
The crash report below :
CODE:.....................
I'm opening an Activity using this:
startActivity(new Intent(Parent.this, Child.class)); And on the child, I have this code on the onCreate function (the if contains more than just true, of course): public void onCreate(Bundle savedInstanceState) {super.onCreate(savedInstanceState); if (true) { AlertDialog.Builder builder = new AlertDialog.Builder(this); builder.setPositiveButton("OK", null); builder.setTitle("Error"); builder.setMessage("Connection error, please try later.") .show(); finishActivity(0); return;}}
Why is the activity not closing? I get the alert box, but then I have to tap the "back" button to go back.
CODE:.......
Phone was an HTC My Touch. I got the prompt to choose what activity, browser or youtube, chose youtube.
I understand that Android Activities have specific lifecycles and that onCreate should be overridden and used for initialization, but what exactly happens in the constructor? Are there any cases when you could/should override the Activity constructor as well, or should you never touch it?
I'm assuming that the constructor should never be used because references to Activities aren't cleaned up entirely (thus hampering the garbage collector) and that onDestroy is there for that purpose. Is this correct?