• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Help Pressing home button to wake up phone closes opened app. Need help.

D

demonflame5

Newbie
So when I updated to jelly bean, I noticed that whenever my screen turns black after waiting for 30 seconds, and I press the home button to wake it up, it closes the app that I currently had open.

It's really annoying when I'm reading something on the internet only to wake it up and it closes the browser, or when I'm thinking during a game of words with friends.

edit: I do not use a lock screen.
 
I did the same thing, you need to push the lock/power button to wake the device. I suppose it kind of makes sense it just takes a little bit to get used to it.
 
It is annoying. You can stop it happening of you get widget locker as a replacement lock screen which is what I've done
 
This is the first smart phone I've ever owned, and it seems like the developers half-ass everything hoping that 3rd party developers will correct any problems that the user may have. It's pathetic. The support and development for these phones is absolutely pathetic. I personally like using stock settings, but when it's so incredibly lacking and inferior it makes it hard for me to enjoy my experience on my smart phone.

Heavily considering to revert back to a flip phone. These smart phones are way too much maintenance for their own good. Lacking such simple features such as changing icon size, text, icon images, and just overall general customization, and forcing the user to seek out these features through 3rd party methods.

Also, do they even test their updates? I waited for this jelly bean update for 5 months, and what do I get? A keyboard that is incredibly laggy and a severe downgrade? How does this get through?
 
It actually makes sense as the idea is that you can turn your screen off but your phone is still active until it hits the lock time limit. just takes a bit of getting used to to use the power button instead.
 
i agree it is a bit annoying - keeps catching me out - and then im like, oh yeah, its the home key, doh! but that is because ive used widget locker for a long while and had that set to keep last app open
 
Go into s-voice and see if the box is checked next to "Open via the home key." If it isn't, check it and this should fix it. It's kind of annoying that I have a laggy home key now though. That's why I unchecked that box in the first place.
 
Here is your solution.

1) Go to your lock screen options
2) Change the lock screen to one that has security (like pattern)
3) Change the time out to immediately from 5 secs
4) Change back to any lock screen option you want.

Problem is, even though the screen is turning off, for that period of time, the home key still does what it is intended. Changing it to lock immediately will require you to unlock the device, but will not exit that app.

Of course, you can just use the power button as previously mentioned.
 
I think that if the screen is off, it still shouldn't close out of the app that is open. I'm pretty sure that's how it worked on ICS. On JB it looks like you have 3 options.

1. You can live with the laggy home key and have the home key only turn the screen on instead of closing the app too.
2. You can have the lock screen set to "immediately".
3. You can press the power button to turn the screen on.
 
demonflame5 said:
So when I updated to jelly bean, I noticed that whenever my screen turns black after waiting for 30 seconds, and I press the home button to wake it up, it closes the app that I currently had open.

It's really annoying when I'm reading something on the internet only to wake it up and it closes the browser, or when I'm thinking during a game of words with friends.

edit: I do not use a lock screen.
Click to expand...

I know exactly what you mean and I have the same problem, but the solution that worked for me is on this post:
http://androidforums.com/samsung-galaxy-s3/677954-fixed-home-button-closes-apps-wake-annoyance.html#post5731218


Hope it helps you.
 
indianaryan said:
Go into s-voice and see if the box is checked next to "Open via the home key." If it isn't, check it and this should fix it. It's kind of annoying that I have a laggy home key now though. That's why I unchecked that box in the first place.
Click to expand...


Thank you V much--tried all day to get this right,even refreshed software -finally only your suggestion worked-thx a tonn
 
You must log in or register to reply here.
Back
Top Bottom