Hi, first thing, this is my first Android phone and I understand I should press the back button to close out of apps rather than press the home button. So this means if I have been surfing for a while, I have to press back, say 20 times, going backward through all the pages I've visited, until I reach the first page opened and the browser will close.
I know I can press home to close, then press the right menu button to bring up the recent apps and swipe the browser away, but isn't there a better way to close out of programs? I thought maybe holding the 'back' button would force close it but it just brings up the browsing history.
2nd: I'm finding that some programs do not go into certain 'folders' while it goes into other folders, what is causing this?
Thanks.
On cm10 or any custom rom actually has the option in developers options to "long press back to kill app" if you don't have that option the only way is it press the home button hit the recent apps button not the menu button and swipe it away. How is that hard? Its much harder to do the same task on iOS.
Also I'm not too sure what you mean by the folder deal can you take a screenshot and upload it here. ( hold power + volume down.)
Sent From My Toro+ via RED Tapatalk
The browser is a unique case where you don't have to back out. The best way is just close the current tab, or all tabs you have open, to close the browser. You don't go 20 pages back for browser closing. But for all apps yes back button is the best way to close apps when you're done.
Lol wow... I do that all the time and completely forgot thanks.
Sent From My Toro+ via RED Tapatalk
Related
don't know you guys, but imho,
back should just be back.
multitasking should use long press home (instead of long press back)
and voice search should use long press search (instead of long press home)
reason for this is (in my case) search is kinda under-utilized and back gets used all the time. i'd rather leave back key to back function alone.
what's your thought on this?
edit: oh, i'd also rather have back key to go back within the same app and not to desktop or some other app.
I agree with the long press on the search button for tellme search. But back button is a better choice for multitasking menu because your finger is going to drift there to switch back an app.
Btw don't call it the home button... Its the start button =)
hardcoreplur said:
I agree with the long press on the search button for tellme search. But back button is a better choice for multitasking menu because your finger is going to drift there to switch back an app.
Click to expand...
Click to collapse
my rationale is to separate in-app navigation (use back) and between-app navigation (use home).
right now there's no indication of where you are in the "back queue". e.g. you don't know that you are already backed to root navigation inside an app and another back would bring you outside the app. coupled with lag in certain apps, it can be very frustrating.
I think I like things the way they are. I use the search button (hardware) a ton.
In the stock browser, I have enabled the Quick Controls and Full Screen options. The results are brilliant.
However, it is a bit of a chore to get to my Bookmarks. Anyone have any shortcuts?
I usually press the quick control for the tabs a little longer than normal before letting go which shows all the tabs. The bookmark button appears on the top right. Don't know if there's a faster way.
If you press and hold the "back" screen button, for a couple of seconds -- the bookmarks / history / saved pages will be there.
One issue I have always had with Android is knowing whether or not pressing the back key will take you to a previous menu or close the program. Now that the back button is dynamic, would it be possible to create a mod where the back button turns into an "x" when it will close the program? I think this is something that should be part of ICS, but I also know that modders can do some incredible things.
I wouldn't get your hopes up. Every application is coded differently and it depends on the developer to what function the back button does. I think for this to work, hypothetically, you would need specially designed applications to include this feature.
You could have the button linked to environmental variable that always takes you back home, bypassing any specific app uses, however that would be redundant since you already have a home button. Other than that, I don't think there's another way to do it, definitely not dynamic since its up to the specific App. However, I remember on CM7, there was an option for SMS so that the back button always took you to the inbox, and not just quit, which I miss.
The application controls whether the back button moves you to a previous screen, home screen, or even exits the program.
Edit: Just noticed I repeated what everyone else said
If it were possible to mod Android so that the back button was unable to close apps, I would be very happy. Could this be done?
thereddog said:
If it were possible to mod Android so that the back button was unable to close apps, I would be very happy. Could this be done?
Click to expand...
Click to collapse
Don't think of the back button as closing the applications. Think of it more like the button triggering the app to close itself. It's an app specific issue, but not really an issue... Just use the home key!
RTContent said:
Don't think of the back button as closing the applications. Think of it more like the button triggering the app to close itself. It's an app specific issue, but not really an issue... Just use the home key!
Click to expand...
Click to collapse
Just an example using Google Music:
Listening to music, I want to go into the app using the widget or icon on a home screen. Sometimes it goes to the Now Playing screen, other times it will go to the Recent/Artist/Albums view. (Which is a whole 'nother issue I have with Android)
I don't wan't the back button to go back to the home screen, I want the back button to back within the app. If the system can be modded so that the back button never navigates to home, I think that would work for me.
thereddog said:
Just an example using Google Music:
Listening to music, I want to go into the app using the widget or icon on a home screen. Sometimes it goes to the Now Playing screen, other times it will go to the Recent/Artist/Albums view. (Which is a whole 'nother issue I have with Android)
I don't wan't the back button to go back to the home screen, I want the back button to back within the app. If the system can be modded so that the back button never navigates to home, I think that would work for me.
Click to expand...
Click to collapse
Yeah I have noticed this with Google music. Hopefully Google will update this with a fix but understand it's not an 'android' issue its a apk issue.
Sent from my Galaxy Nexus using Tapatalk
I don't use any lock screen and I always use the home button to wake my phone up.
Since official JB, the home button not only wakes the phone up but it closes the app I'm in. Example : I'm browsing something on chrome, the screen turns off bc of timeout, I wake the phone using the home button and I see chrome back but immediatly it closes down like if I had pressed the home button again (but I didn't). The same behavior does not happen when a lock screen is enabled.
I tried searching for an answer and tried the solution of editing the .kl files in system/usr/keylayout by adding WAKE_DROPPED or replacing WAKE with WAKE_DROPPED for every occurence of the home key (key 172) without luck. I tried fixing the permissions in CWM and I made sure the permissions are rw-r-r.
Running stock rooted with CWM.
Any other ideas? Thx!
I'm also curious about this. My temporary fix was to unfreeze S Voice in Titanium and then enable the double press of the home button to start S Voice.
I'd rather keep S Voice frozen and still keep the same behaviour of the home button in ICS.
pappcam said:
I'm also curious about this. My temporary fix was to unfreeze S Voice in Titanium and then enable the double press of the home button to start S Voice.
I'd rather keep S Voice frozen and still keep the same behaviour of the home button in ICS.
Click to expand...
Click to collapse
Yes that does work indeed. However, it brings back the lag when pressing the home button. I'm also using home2 shortcut for some shortcuts and it completely breaks them!
The same problem arises also when you long press the home button to get to recent apps, if you have an app open in the background at that moment and you press the home button to get out of the recent app screen, it closes the app!
Hi all,
I'm trying to figure out if there's a way to lock an app in memory even if I push the back button?
I am locking 2-3 most frequently used apps from the "Recents" menu but that gets washed away when I press the "Back" button after being done with the respective app.
I know the best option would be to start pushing the "Home" button but over the years I developed a habit of pushing the "Back" button several times to go to home or once to close the app and it's very hard to change behavior now.
I'm on NitrogenOS (8.1) if it matters - stock kernel.
Cheers.
DonnyR said:
Hi all,
I'm trying to figure out if there's a way to lock an app in memory even if I push the back button?
I am locking 2-3 most frequently used apps from the "Recents" menu but that gets washed away when I press the "Back" button after being done with the respective app.
I know the best option would be to start pushing the "Home" button but over the years I developed a habit of pushing the "Back" button several times to go to home or once to close the app and it's very hard to change behavior now.
I'm on NitrogenOS (8.1) if it matters - stock kernel.
Cheers.
Click to expand...
Click to collapse
Unless the back button is programmed to kill an app, the app should stay in memory. So check the options for the back button and change it.
It is set to close app. Long press for kill. But still does not work.
If I assign to something else, then basic acknowledge functionality does not work...
DonnyR said:
It is set to close app. Long press for kill. But still does not work.
If I assign to something else, then basic acknowledge functionality does not work...
Click to expand...
Click to collapse
Check the long press duration and if possible lengthen it. Or assign double tap for kill and none for long press as an experiment and check.