Android page says..You newer can handle Home button..it is easy to understant..
if you can handle home button you can newer close program..You always
start intent..That is bad for users..
For that you cant handle home button press...
2011/9/22, kaciula :
> What you are experiencing is a known bug
What you are experiencing is a known bug (at least known by me for
over a year now). Check out my answer here
http://stackoverflow.com/questions/3042420/home-key-press-behaviour/4782423#4782423
I've also filed an issue a couple of months ago. The idea is that in
some situations, after you press HO
I assume that your activities have the default launch-mode. I.e. when
started, they will be newly created.
Press app-icon: Activity is started and onCreate is called.
Press Home-button long time: Your task, that contains your activity, is
brought to the foreground. If your process was still runn
The only thing I changed in the manifest was the versionCode and
versionName. I had made a copy of the project, the renamed it (using
Android tools through Eclipse) and discovered this problem. So I
exported the original project, signed it, zip aligned it, put it on my
phone and it too was doing i
On Tue, Sep 20, 2011 at 12:38 PM, GregAZ wrote:
> #3 is calling onCreate again. If instead of doing step 3 I hold home
> down and switch to the app it just resumes, onCreate isn't called
> again.
>
Weirdballs. I'd do a full clean / rebuild, delete your shortcut (if that's
what you're using) and
On Tue, Sep 20, 2011 at 12:21 PM, GregAZ wrote:
> But the problem still remains, the bundle is always null even though it is
> saved.
>
Then a new instance of the Activity is being created. You can verify this by
printing out the value of the Activity object itself in onSaveInstanceState
and onC
I'm finally getting some where. I need to read up on the life cycle
cuz I'm getting myself screwed up.
Here's what's happening:
Debug mode:
1. Tap app icon to open app, onCreate is called
2. Hit home button, state is saved
3. Tap app icon to open app, it resumes, onCreate is not called
In debug
I think I misunderstood when onRestoreInstanceState is called so
ignore that part. But the problem still remains, the bundle is always
null even though it is saved. I have logging showing me
onSaveInstanceState is called.
On Sep 20, 12:11 pm, GregAZ wrote:
> savedInstanceState is always null. F
onSaveInstanceState() is used to save per instance state while
SharedPreferences is used to save persistent data across sessions.
Whenever you start the app the SharedPreferences are there, data saved
in onSaveInstanceState() is gone once the app has been shut down.
onSaveInstanceState() can be us
OH obviously, I don't know why I was so set on using the
savedInstance... Anyway SharedPreferences works great.
Chris
On Jan 20, 3:03 pm, TreKing wrote:
> On Thu, Jan 20, 2011 at 1:48 PM, Chris wrote:
> > I'm trying to save the state of my app while I shut it down but every
> > time I bring
Thanks, i will approach it that way.
On 28 July, 11:28, Mark Murphy wrote:
> Ne0 wrote:
> > My activity displays a text view where the text is constantly changed
> > with updates from a LocationListener. When returning to the activity
> > after navigating away, the text view comes back with the
Ne0 wrote:
> My activity displays a text view where the text is constantly changed
> with updates from a LocationListener. When returning to the activity
> after navigating away, the text view comes back with the
> savedInstanceState state but any changes to the text in the text view
> dont. How d
You can't, your object must be a Parcelable and implement the protocol for
marsalling/unmarshalling itself.
On Thu, Mar 12, 2009 at 6:21 AM, Mr.No wrote:
>
> Hello,
>
> how do i put a Obect(or a HashMap) into the Bundle?
> rgds F.Hildt
> >
>
--
Dianne Hackborn
Android framework engineer
hack.
13 matches
Mail list logo
