I have an activity that starts with an AsyncTask to check the connection to my servers api.
Since this should not run in the UI thread i have made a AsyncTask for this.
The problem is that is get an runtime exception when i start the background process of the Asynctask.
How can i avoid this?
From log:
code:.........................
View 1 Replies
I use an AlarmManager to run a Service which tries to download a file from the web. If it fails I'd like to retry that Service in 5 minutes.
Inside the Service I run an AsyncTask to run my code. As far as I know the only way I can tell if it failed or not is from the onPostExecute().
What is the best way of implementing a retry of that Service again?
I am using an AsyncTask to fetch the ring tone for a contact when my application starts, it works fine until after my Activity closes a couple of times during the AsyncTask, after this happens the AsyncTask will only ever get to onPreExecute() and never doInBackground, so I can never fetch the ringtone then until either a force stop or device restart.
Why this might be happening? Why the AsyncTask would get to onPreExecute but then never run doInBackground()?
Here is my code: (Following the Shelves source code)
CODE:.....................
And onAddRingtone() is used in onCreate and onCancelRingTone() is used in onDestroy() as well as where you can see if in the code above. I have spent 3 days on this and I haven't been able to find a solution? Am I taking the wrong approach? Using cancel wrong? Is there a bug?
I'm writing some JUnit tests for my Android Activity.They run fine and report proper results.However, when i automate the test and start the emulator, the emulator starts with an unlock screen. This prevents the test from running correctly.How do I start an emulator without the unlock screen so that it's ready to run a test immediately? Are there commands in the emulator.exe or adb.exe that can close/ remove the unlock screen?
View 5 Replies View RelatedI'm trying to figure out the correct way to create an AsyncTask to retrieve some data from the internet and then to take that data and bundle it up in an Intent and pass it to a new activity(A list display). So in the first activity I just have an EditText and Button. In the event of an OnClick the task should be called and when it is finished the data should be bundled inside an Intent and passed to the next Activity. The problem is when I take the results from onPostExecute and set them to an instance variable of the main activity, that instance variable is still null when the task is complete. Here is the barebones version of the code:
CODE:...........
When I debug the application I see onPostExecute does contain a valid PlacesList full of results, so why is the instance variable places set to null after the task is executed? I am going about "returning data" from an AsyncTask incorrectly?
1) I am developing my app in Eclipse 3.4.1 with Android (ver 1.1_r1) plugin. My app compiles and executes without errors when using the Eclipse IDE.
However, when I export my app (unsigned) using Eclipse (via {select project} >right-click>Android tools>export unsigned application package), sign it, and try to run it on the Emulator, it throws a runtime error when I try to update my sqlite database, at which time the specific error created is: SQLite error#14, unable to open database. It is able to read from the database without problems. (I have also verified that the database is: open, is not readonly, is not locked by another thread, is not in the middle of a transaction.)
I have limited experience, but this seems more like a "system" problem given that the app works OK in Eclipse IDE but then fails as an exported/signed apk. Some googling of SQLite resources revealed a similar error on a non-Android platform which was fixed by: "Set your permissions correctly on /var/tmp, or whatever directory you are using to hold temporary files".
Does Android have temporary files, and if so how does it handle permissions on temporary files? Is there a way to check or set these permissions to see if this fixes my problem here?
2) Not sure if it is related, but after I have run the exported/signed app which causes the runtime error, if I reboot the Emulator, and try to run the program using the Eclipse IDE , the program fails with the same exact error. PLUS I also noticed the following error message while the program is installing/running: 03-01 22:22:29.282: ERROR/PackageManager(53): Package com.northwestradiology has mismatched uid: 0 on disk, 10019 in settings; read messages:
I can restore the Eclipse version of my program to be able to execute without runtime errors by utilizing the -wipe-data option for the emulator. But note that if I run my signed APK using an emulator created with the -wipe-data option, it still throws the runtime error listed above...
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?
I am making twitter application in which i open browser for user authentication and i pass call_back URL when launching authentication browser.
Problem is after authenticating it is calling again oncreate of TWitterShare class instead calling onNewIntent method, why is that ? my another class working fine i am unable to find difference any idea by looking at the following ocde why it is calling oncreate again ?
CODE:...................
I got this class, and nothing inside the onCreate is happening? Does it not automatically get called upon initialization?
Code is below.
CODE:......................
Doing this results in a "application has stopped unexpectedly. Please try again". If I initialize the string to some set of characters instead of null, it'll just stay that way. Should it not do what is inside the onCreate() and make that change?
I know that network activity and expensive operations should not be done on the ui thread, but what about database activity?
I have an activity that, when started, I query an sqlite database and dynamically populate rows in a tablelayout with an inflator. I do this all in the oncreate() method. Should this be done in a separate thread?
What is the lifetime of a ContentProvider in Android? After onCreate() is invoked, will the ContentProvider persist unconditionally for the lifetime of the process?
My ContentProvider manages a list of records, but only 1 is designated "active" and will be accessed by different applications a lot. I was wondering if it's safe to cache the index of this active record in memory as a member of my ContentProvider to speed up lookup.
Why if I start the MPlayer from the onCreate it doesn't start?
I tried also from onStart(), but the only working way was from onTouch or on key press.
Any idea how to start it without any additional user input needed?
I have a main activity and a sub activity.The main activity starts the sub activity using startActivity, and passes an object in the intent.The sub activity reads the object out of the intent in its onCreate action.The sub activity updates the object, then returns to the main activity using startActivity, again passing the updated object back.However, the main activities onCreate function is not called, so the code it contains to read the passed object does not run.Further investigation indicated that the main activity onPause event is firing, i.e. it is only paused when the sub activity runs, so when the sub activity starts the main activity again, it just on Resumes.Does anyone know if there would be any disadvantages if I moved my data restore/store activities to the onResume and onPause events?I'm not using the onCreate saved Instance State, should I be?
View 4 Replies View Relatedwhen writing a ContentProvider I have to implement the onCreate()-method, in which I establish my database connection. But to write the changes I made to the database I have to close the database on some point. Does something like a onDestroy()-method exist for ContentProviders or is there some intent I have to listen to, which is fired before killing my process?
View 5 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?
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 RelatedMaybe 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 want to have a configurable language settings in my app. So, in onCreate of my activity, I call Resources.updateConfiguration with the new locale. However, after onCreate (at some time, I can't find it when), the locale is set back to the default locale.
On the code example below, the strings shown in the main layout (as inflated by setContentView) shows the "in" language version, BUT when I press the menu button, on which onCreateMenu is called, the strings is taken from the "en" (default) locale.
The log shows this:
CODE:...............
Between "oncreate" and "onmenu", the locale magically changes.
Code snippet:
CODE:.................
My app launches the camera to allow the user to capture a picture. Sometimes this causes the OS will kill my App to free up memory for the camera. Once the picture is taken, my app starts back up where it left off using the Bundle I saved in onSaveInstanceState(). My app had a bug where in the code that restores the state. Is there anyway that I can simulate or test this case to make sure I am restoring correctly now? It seems I am having trouble making this happen when I want to test it.
View 4 Replies View RelatedAs you can see, I first create a webview. Then, I want it to immediately disappear. Then, I want the Listview to come up. But the problem is, I can't do Listview if I don't do ListActivity but then I can't do Activity. Code...
View 2 Replies View RelatedI have a parent activity, and a child activity that extends the parent activity. When the parent starts the child activity,
Which onCreate gets executed first? The child's or parent's?
There is a particular variable I am setting in the Child activity's onCreate method, and right now, it looks like it takes a while to get to the Child activity's onCreate, and so the methods in the Parent are reporting an empty variable. Whereas when I make the Parent sleep for a while, it reports the correct variable.
CODE:............
So, basically, even after the Parent starts the Child, it still returns "Parent Value", but when I have the thread sleep, it return "Child Value".
My application after an update needs to fill its ContentProvider with some data found on the server.
I found that starting a service from the ContentProvider.onCreate() method works but I'm not sure if it is a good idea or if it works randomly.
I don't know the initialization of an application in android. Are the services always already available before the content provider is created?