This is with the 1.6 & 1.5 SDKs, not tried earlier ones. When you switch from portrait to landscape the onSaveInstanceState()/ onRestoreInstanceState() pair are called once, but when going back from landscape to portrait they are called twice, unless I've missed something. To test, see the log after creating a default Hello World app and change the main class like this: code...
View 4 Replies
I have a problem with the activity lifecycle specifically on Nexus One (2.1 running on emulator works fine). If I just create a simple empty Activity with no special launchModes that logs the calls on the onStart and onStop methods, this is what I see: - launch app: onStart called; - home button: onStop NOT called; - launch app: onStart NOT called; - home button: onStop NOT called: and so on. Sometimes if I press the back button then the onStop is not called, but the when i launch the activity again the onStart is called and right after the onStop is called. Similar results with different launchModes. What is going on? Can anyone confirm this?
i found an android issue for the problem here: http://code.google.com/p/android/issues/detail?id=6094 and a similar thread here http://groups.google.com/group/android-developers/browse_thread/threa.
My app is made of two activities, A and B. I'm considering this sequence of steps: Activity A is started. A launches B [A is paused, B is running]. B launches a map intent [A and B are both paused now]. Now the user is using the maps application and the system decides it needs more memory. Can the system kill only one of my activities for memory, or will it always kill all activities in a "process" in this situation?
Both activities share some static data like:
class Data {
public static String mName;
public void save() {
// write to file: mName;...................
A question for all the frequent ROM-switchers. I've got the premium edition of Titanium, and up 'till now, every time I try out a new ROM, I have to re-load all my apps/data. It's not terribly inconvenient - I just do the batch 'restore apps/data' option - but I still have to 'confirm' the re-loading of each app, and it takes forever. It give me an 'install' prompt for each app which I have to press. Is there a faster way of restoring all my apps/data?
View 3 Replies View RelatedThis is probably a pretty easy to answer question, but I can't find the solution myself after a couple hours of searching the documentation and Google.I set the orientation of my Android app to landscape in the AndroidManifest.xml file: android:screenOrientation="landscape"
However, when I run the app in the simulator, it appears sideways and in portrait mode. How can I switch the emulator to landscape mode on a mac? It's running the 1.6 SDK.
Can any one help with how to test sensor events like shake on Android Emulator.I have found some posts pointing to openintents but can anyone explain how to use it in android 2.0 avd.
View 1 Replies View RelatedCan multitouch events be tested on Android Emulator ? Or is there any way to test this without actual device ? I am using 2.0 sdk and want to test zoom-in zoom-out on by two fingers.
Is there a way out ?
We are currently working on an instrumentation test suite which runs on our build server, but while the tests pass on a dev machine using a normal Android emulator, the builds fail on the build server since there we only run a headless emulator with the -no-window flag.The failure occurs when trying to invoke the InstrumentationTestCase.sendKeys() method to programatically open the options menu.We also tried to let the instrumentation test app and the app under test share the same Linux user ID using android:sharedUserId and run in the same process (android:process -- we weren't sure if that was already the case), but still no luck. Does this mean it's currently impossible to run instrumentations which contain key events on a headless emulator, or are we missing something?
View 2 Replies View RelatedI have a MapActivity that contains a MapView with some custom controls, state information, and an ItemizedOverlay composed by some locations that I draw using the default approach (using populate(), super.draw() and createItem()) and by some lines that I draw in the overrided draw() method.
So, when the activity is paused, I have to save:
Some state information
The ItemizedOverlay
[Maybe more Overlays in the future.]
I'm saving the state information as usual, putting them in the bundle. I'm thinking in doing the same with the Overlays, implementing Parcelablein each one of the OverlayItems and so, but I don't know if there is a better way to store the complete state of the MapViews.
The information depends on remote requests that I don't want to repeat each time the activity is paused. Any recommendation?
I have an application which uses a cookie to tie a user to a session on my server.
Is there a simple way to save and restore this cookie to a SQLiteDatabase so that the user does not have to reacquire the cookie every time the app starts?
I have several hundred contacts and tons of calendar events on my Incredible. I have all of these on my gmail account which syncs with my INcredible. What is the best way to ensure that I never lose this information? I would imagine that it will always be on my gmail account??? If my phone were ever lost or stolen wouldn't it just be a matter of getting another phone and uploading from gmail to the phone? So, what is the best backup method out there for me? I am coming from a Palm Treo which I was able to sync with my desktop program.
View 3 Replies View RelatedI've downloaded Launcher Pro, I currently still have ADW installed as well. When I use LauncherPro my home screen (and other screens) are not set up the way I currently have them. I spent a lot of time setting my current screens so they are exactly the way I want them. Any way to save that config when switching to LauncherPro? It does seem faster so I want to give it a shot, but I'm dreadig setting everything up again- widgets, apps, etc.
As usual in android, each time the screen is flipped to portrait/landscape mode an Activity runs through life-cycle from onSaveInstanceState to onDestroy and then is recreated.In my Activity there's a ButtonText which can be changed by the user. It's reseted to the initial state, but I have to save the last state somehow. How can I achieve that, will I have to override onSaveInstanceState? Can someone show an example?
View 1 Replies View RelatedIn Android, you need to implement the following Activity methods so your application can be restored to its previous state if the OS decides to destroy then recreate your activity:
public void onSaveInstanceState(Bundle savedInstanceState)
public void onRestoreInstanceState(Bundle savedInstanceState)
The examples I've seen of implementing these methods is to use put/getBoolean, put/getInt etc. on the Bundle object (i.e. primitive objects only) to save the application state. This seems hugely error prone way to save your state for a start and I cannot see how this scales to storing complex objects without writing lots of code.
What options do I have for storing/restoring state in a robust and easy to implement fashion?
In case it's important, my application (a game) needs to store about 50 objects, which each store maybe 5 float variables and some store references to other objects. I don't particularly want to have to write save/restore methods for every class and subclass (maybe about 15 of these) I use. It would be ideal if I could just stick all my state relevant objects in an object called "state" and then just call save/load on "state" to handle everything.
Is using Java serialization an option? I've heard it's very slow, but is that a problem for save/restoring? Could I just write my data to the SD card? To a database?
I just download a cupcake branch of source code and build it. I configured Eclipse for a new SDK, and appear the things is works great, EXCEPT emulator. 1. I configured a new AVD as parameter i pointed my old sdcard.img then loaded and do not see my sdcard 2. then I back and configure another AVD with a parameter to create a new sdcard.img, when the emulator loaded I still not seen sdcard in emulator. 3. then I try to something like: emulator -avd myavd -sdcard mysdcard.img and there is still no sd card.
How can I restore my sd card in emulator.
How do i reinstall saved apps and settings when i have flashed a new rom .Iassume it is possible .
View 2 Replies View RelatedI'm considering trying one of the ROMs available here for my behold 2.Will I lose all the apps and other user data I have?If so, is there a way to save the apps/information and then restore it after the flash ?I have a few paid apps in particular that I'd prefer not to lose.
View 3 Replies View RelatedHow do I load snesoid save files from my phone so I can play them on my pc? Can someone walk me through this cause I tried just copying the file to pc but it didn't load with snes9x.
View 1 Replies View Relatedi am trying to recording on button click.
mycode is following::
HTML Code:
HTML Code:
private void StartAudioRecording() {
[Code].....
when i was running application in debug mode application getting crash. i am not getting sdcard path .
I have installed PC Companion but every 2-3 days it announce me a new update for my phone X10mini.Is it possible to know which bugs are fixed in each update before proceeding ?Is there a way to save all data before upgrading and restore after upgrading ? (sms, sounds, accounts, software, note, alert, phonebook etc)
View 1 Replies View RelatedI 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?
In my application I have several activities, the main screen has 4 buttons that each start a different activity. So one of them is a search activity, once it searches it shows you a result activity. This result activity can be reached from other activities, so in general something like this:
Main activity -> Search activity -> Result activity
Main acitivty -> someother activity -> Result activity
Now, if I have reached this result activity and press back once or twice, and after that press the Home key it will show the Home screen. But if I want to get back to my application by holding the Home button and clicking on my app it will always go back to the Result activity, no matter which activity was the last one I was using. And if I press again back it will take me back to the Home screen.
If I try it again it will take me again to the Result activity. The only way to avoid this is to start the application by clicking on the app's icon. And this takes me to the last activity I was using and it remembers the state so if I press back again it doesn't take me to the Home screen, instead to the activity before it. To illustrate this:
Main activity -> Search activity -> result activity --back--> Search activity --Home Button--> Home Screen --Hold Home and select the app --> Result activity --back--> Home Screen
--Click application icon--> Search activity --back--> Main activity
Another thing that happens is that if I press the Home button while on the Result activity, and start the app by clicking the icon, it will take me to the activity prior the the Result one.
There's a decent amount of information out there on the Activity lifecycle. But I'm surprised how difficult it is to find a comprehensive description of the rendering lifecycle. By that I mean the order and rules by which a tree of nested activities, views, and drawables get to be sized and drawn to the screen, and the points at which a developer can modify rendering behavior.
View 1 Replies View RelatedIn the Android Application Fundamentals it says that after the call to the onStart()-method of the activity lifecycle either the callback method Resume() or onStop() is called. In case of an "normal" Start of an activity the system calls onCreate(), onStart(), onResume().But does somebody know an example where onStart() - onStop() are executed one after another?
View 2 Replies View RelatedI am having difficulties with the lifecycle of the opengl context. While rendering my scene and the user hits the back button, home button or another application opens in front of my application, my app is still running in the background.
So when my application comes to the foreground later on (user relaunches it or the app that was opened on top of it finishes), my application crashes and leaves me nothing but a GL stack trace which i can't properly decipher.
For rendering i use the GLSurfaceView and therefore delegate the onPause and onResume. The crash happens on the first call to glDrawElements(..).
I have tried to reload my resource (geometry/textures etc.) on onSurfaceChanged but with or without reloading... The problem persists.
This behavior can be observed on all AVD versions of the emulator as well as on the G1.
Here is the gl stacktrace i get.
CODE:.............
I just ran into a situation where it looks like a static variable reference is persisted across activity sessions. I didn't expect that because I thought that when an activity exits, it's de-referenced and garbage collected. I am wondering if anyone can shed some (more) light on when the VM eliminates object references for Activities and Services and in particular when static variables get reset to default values?
View 7 Replies View RelatedI am trying to create a Servicefor my application which will negotiate Bluetooth connections and data. I want this service's lifecycle to start and end with the Application, but still be able to have specific Activities listen for events that occur within this service (in addition an Activty should be able to call specific methods of the Service to write data or query connection state).
I started by creating AIDL interfaces for my callbacks and service, but I can't figure out exactly what I'm doing.
How is the best way to go about this? EDIT: To be clear, I do not specifically need (or want) more than one process for my application. Right now I don't have more than one; I'm just using AIDL because it is the only way I know of for a Service to communicate with an Activity.
I have creating application with 3 activities, where A - list of categories, B - list of items, C - single item. Data displayed in B and C is parsed from online XML. But, if I go trough A -> B1 -> C, then back to A and then back to B1 I would like to have it's data cached somewhere so I wouldn't have to request XML again.I'm new to Android and Java programming, I've googled a lot and still can't find (or simply do not have an idea where to look) a way to do what I want.Would storing all received data in main activity A (HashMaps? ContentProviders?) and then passing to B and C (if they get same request that was before) be a good idea?
View 3 Replies View RelatedI slapped together a simple test application that has a button, and makes a noise when the user clicks on it.
Here are it's method:
CODE:..................
My question is, why is onCreate acting like it's in a while loop? I can click on the button whenever, and it makes the sound. I might think it was just a property of listeners, but the Button object wasn't a member variable. I thought that Android would just go through onCreate onse, and proceed onto the next lifecycle method. Also, I know that my current way of seeing if the sound is playing is crap...I'll get to that later.
http://developer.android.com/reference/android/app/Activity.html
The Activity Lifecycle could have implementation and or design bug: One case is to initialize a big image in onCreate(), try to reuse the image during the whole lifecycle, and then recycle the image in onDestroy(). Test showed that onCreate() is called every time one navigate away from the activity and back again, but onDestroy() is not called at all. This behavour causes memory leaking for the big image (size 960*1920). After 6+ times away and back to activity, the system runs out of memory and has to kill the process.
One workaround is to initialize the big image in onResume() and recycle in onPause(), but that's not so good reuse.
Could it be better to change the process (as shown in the diagram) a little bit such as: Call onDestroy() first when a process is killed?