I have an app that works only in portrait mode, and I have made the changes in my manifest file for every activity the orientation to be portrait. But when I rotate the device, the activity recreates again.
How to not destroy the activity?
View 2 Replies
I have an activity defined as below:
CODE:............
A strange thing is that, when running on emulator, and the back key is pressed, the activity was destroyed (I saw onDestroy() called in log). But when running on my Nexus One phone, and the back key is pressed, the activity is not destroyed (I didn't see onDestroy() called in log).
I would like to know as to what will happen to the thread which has been created by an activity and the device is rotated. I have observed that the onDestroy method is called when this happens. Will the thread be killed too?If the thread is not killed, how can I reassociate the thread with the activity as a new instance of the activity is created on rotation.
View 1 Replies View Relatedwhat puzzle me so much is that i can't destroy a GLSurfaceView while i don't want to exit the activity.
the fact is when i destroy a GLSurfaceView which had show in the screen (that means it has binded to the activity's SurfaceHolder), the activity exits without any prompting. Perhaps ,the Context which provided in the Construction of GLSurfaceView joins the two things together. so my conclusion is that a GLSurfaceView can only be destroyed when exit the activity. is there anyway to destroy a GLSurfaceView without exit activity? is there someone can provide a clue?
I have an Activity with an inner Handler. The problem is that after the activity is destroyed, the Handler is receiving messages for the destroyed activity. This breaks things because the activity is in an inconsistent state. I'm thinking this might be a bug in Android - it should probably delete all the messages in the queue when the activity is destroyed. There doesn't appear to be any way I can manually delete all messages in the queue (except by calling removeMessage(int what) with every possible variation of what, which seems a bit ridiculous). The only other solution I can think of is to create my own is_destroyed instance variable and check it in handleMessage(), but again that seems like a ridiculous hack. Has anyone come across this problem before?
View 5 Replies View RelatedI have a activity MyActivity, which "kills" yourself using the finish () method. The problem is: after the kill operation, method onDestroy is called, but the object of type MyActivity is never garbage-collected (I forced the GC run). It is causing a memory leak, because MyActivity is launched many times, by other activities. Does anyone know when the Activity object is supposed to be garbage- collected, and what can be done to avoid the issue I mentioned?
View 2 Replies View RelatedI would like to pausing or putting the application on background when pressing the back button, I don't want the application to go through the destroy state. Things are when I override onKeyDown and when I force to pause or stop the application by using onPause, I have some issuees with the wakelock and application crash, but when I press home button I go through onPause method and I have no exception, it's weird!
View 1 Replies View RelatedI frequently run into the problem that I have to preserve state between several invocations of an activity (i.e. going through several onCreate()/onDelete() cycles). Unfortunately, Android's support for doing that is really poor. As an easy way to preserve state, I thought that since the class is only loaded once by the class loader, that it would be safe to store temporary data that's shared between several instances of an activity in a static Bundle field. However, occasionally, when instance A creates the static bundle and stores data in it, then gets destroyed, and instance B tries to read from it, the static field is suddenly NULL. Doesn't that mean that the class had been removed and reloaded by the classloader while the activity was going through a create/destroy cycle? How else could a static field suddenly become NULL when it was referencing an object before?
View 2 Replies View RelatedI am getting error when I rotate the device (it was HTC with Verizon):
The application My App (process com.mycompany.android) has
stopped unexpectadly. Please try again.
So, I think I need to code for this issue. In order words, when rotate the device from landscape to portable or from portable to landscape, application needs to catch this event.
Is it right ?
How to make it ? What is wrong here ?
Is it possible to test on the emulator ?
what i wont for example my g1 is Orentation enable and when my app start with screen rotate 90 then should be no rotating you know help me exam code pls.
View 2 Replies View RelatedI have developed simple application of progress bar in that when I hit the button then it will do some work in background and one progress bar is visible on foreground. afte completing back ground work it display the same screen. It works fine if I don't rotate mobile but when I rotate mobile then it throws java.lang.IllegalArgumentException: View not attached to window manager
I know when we rotate the device or open keypad it starts activity restarted. But How to avoid this error. My code is.
CODE:..........................
I have implemented rotation of a custom view which runs perfectly on Emulator,but the screen goes blank without any error. When i disable the animation in code[commenting the lines] the view appears on device.
Please help me out. if there is any fox for this.
today i bought Point of View ProTab 25 Tablet. last night i read this thread "[ROM] Point Of View Protab 25 with root" and today i brought it home and every thing were working just fine. so i decided to root it by following the steps in the previous thread, so i flash it with the uploaded firmware, and after it finished, the device become very slow and the "auto rotate" didn't work.. so i flash it back with a firmware that i installed from: Point of View official website and now camera stop working..
View 3 Replies View RelatedAs we know, we can rotate a bitmap through 2 ways. The 1st way is: Matrix mt = new Matrix(); mt. postRotate (degree);Bitmap bitmap = CreateBitmap(src, 0, 0, w, h, mt, true); canvs.drawBitmap(bitmap, 0, 0, paint); In this way, we always need create new bitmap for every rotation, it is not good way for high performance game or app.The 2nd way is: canvas.save(); canvas.rotate(degree); canvas.drawBitmap(bitmap, 0, 0, paint); canvas.restore();In this way, we avoid creating new bitmap frequently, but the rotation bitmap is distortion, the bitmap quality is worse than first way.So, Is there 3rd way to rotate bitmap with high performance and good quality? Your any comments are really appreciated!
View 3 Replies View RelatedI just bought the Nexus One unlocked for AT&T and really like it. 1 wierd thing is that when I rotate the phone counter clockwise, the screen goes to landscape just fine; but when I rotate it clockwise it does not go to landscape "the other way". And, if I'm holding the phone 'normally' and rotate it 180 degrees ('upside down') it doesn't follow.My youngest daughter delights in telling me that her iPhone does this with no problem. What's up with that?
View 7 Replies View RelatedI have a HTC Magic (Rogers Canada).And, I see how the Dream (G1) rotates the home screen. can the Magic do that as well? Also, anybody know if it's possible to rotate the screen to the right and not just to the left? Shouldn't the acceleromater detect all the different rotated modes (even upside down?). that'd be cool
View 1 Replies View RelatedHow does my android activity know (is there a callback) when there is a change in screen orientation?
View 1 Replies View RelatedI have developed an application which is working fine.
In that i have used some static variables and also set Application level variables.
My problem is that even after setting finish() on each activity, application is showing in Running mode.
After closing the application, when i start the application after sometime, it will set the last changes.
How can i destroy my application?
Is it possible to programmatically create and/or destroy AppWidgets?
View 7 Replies View RelatedI have one doubt about back button. If one activity is running on foreground and if I press back button then it will destroy the activity. Now my question is is destroy and kill a process is different? cause if I open DDMS I can see same process is running..Only if I stop that process in DDMS then only it disappear. Is that process will take any memory space after pressing back button..
View 6 Replies View Related"It's not limited to Android devices, but it seems that increasingly Android more than other platforms is shipping with the worst mobile bloatware. It's a bad trend that's going to lead to consumer backlash and it's destroying the credibility of Google's Android vision."
Entelligence: Will carriers destroy the Android vision? - Engadget
I am unable to completely destroy my app. My app is thread based app. Once i exit the app by calling on Destroy method, it is exiting properly. If i try to relaunch the application is says "The application stooped unexpectedly, try again". If i again select my app it is launching. It means in a alternative attempt its launching. as i am guessing, its not making Null for few static objects. once it shows the exception has explained above it is making all the objects null, so that i am able to relaunch. Pls can some one suggest how to overcome this issue. How to completely destroy the application?
View 10 Replies View RelatedAnyone using this? Sure it has a price, but this thing isnt using ANY battery life on my phone... I thought these apps running in the background (chat apps) were supposed to destroy battery? I leave this thing on nearly 8 hours a day, and hardly see any battery drain. The UI could use a few tweaks and themes, but for reliability its awesome!
View 4 Replies View RelatedI want my Activity to be always in portrait mode and I do NOT want the onDestroy() method to be called. There are some interesting articles about that at: http://www.androidguys.com/2008/11/24/rotational-forces-part-four/
The solution seems to be: In AndroidManifest.xml:
CODE:...............
I've tried it and it seems to work. Is there any other alternative or is it the correct solution?
I am working on an app that beeps every second. When I hit the home button I want it to close the program and stop beeping. Right now it closes the program but continues to beep.
What am I doing wrong?
if ((keyCode == KeyEvent.KEYCODE_HOME)) {
isdone = true;
mp.release();
counter.cancel();
finish();
}
Here is a thread example in Android SDK sample (BluetoothChat).code...
In order to destroy this thread, first to close the socket. But this thread is still running at the blocked call mmInStream.read() even mSocket.close is successfully run.
Question: How to properly destroy a thread stuck in blocked call?
Edit / Update:
As an update to the below problem, I found the exact action which causes it to happen.
Download an apk from a url through the android browser
Install the app.
After install, the app gives you two choices: "Open" or "Done".
If you choose "Open", the quirky behavior described below starts.
If you choose "Done", then launch the app from the app tray, it works fine.
So it seems like this problem is caused by using the "Open" button the browser provides you after installing the APK.
I'm experiencing an error in the history stack of applications upon first install. I made a test app to demonstrate this.
The test app is simply two activities, A and B. Activity A launches B. That's all it does. Rest is wizard generated template code from eclipse.
When the user installs the app (via web url apk), and runs it for the first time, I get an out-of-order activity stack:
-User starts the app, A is on top.
-They make A launch B by clicking a button. B is on top of the stack.
-User hits the home screen button.
-User returns to the app, A is displayed, instead of B.
-User hits the back key, B is shown!
-User hits the back key again, A is shown!
-User hits the back key again, home screen shown.
-Now the stack is clean, and app behaves "normally" from now on!
Is any one else seeing this? This is almost exactly like this known bug, however my users are not installing from eclipse:
http://code.google.com/p/android/issues/detail?id=2373&q=first%20%20i...
I can provide the test app/source if anyone wants to try. This is the manifest, which does not have any special customizations made to it. code...
as far as I know, this should definitely not be happening, and works fine after you clear the history stack the first time.
I have created a threaded service the following way. code...
After I close the application the phone works really slow and I guess it is due to thread termination failure.
Does anyone know what is the best way to terminate all threads before terminating the application?
I've noticed that changing the background color of an android widget (f.ex. Button or TextView) by program:
myButton.setBackgroundColor(Color.BLUE);
makes it to loose its 3D shape, border, and shadows effects, and then appears like a ugly flat square. What am I missing?
Sorry for the very naive question but I couldn't get it right although tried for a time.
Like me, many of you are switching to the Incredible from another, older, less awesome phone. Some of you may even be moving to the Inc because you've had it with your current phone. But before you consider taking out your frustrations on your old phone by answering the age-old question, "Will it blend?", consider donating your phone. There are many organizations that will put your old phone to good use. Here in Raleigh, NC, an organization called Interact helps victims of domestic violence and will accept donations of used cell phones. You can also donate your phone to be used by troops overseas. So before you think of just throwing away a piece of technology, consider how it may benefit someone else.
View 17 Replies View Related