Looking at the softkeys, where is the Menu key? I see Home, Back, and the new Multitasking key, but no Menu. How can this be? The iOS method of integrating all menu options into the application UI is terrible, and what about apps made before ICS? Lack of a Menu key would make them unusable. I must be missing something here, but I can't see what it might be.
A virtual menu button appears in the form of 3 dots. It can be seen in this photo.
Tung_meister said:
A virtual menu button appears in the form of 3 dots. It can be seen in this photo.
Click to expand...
Click to collapse
Nice catch. Was wondering about that.
Menu items are represented by the 3 vertical dots at the top right corner of apps.
The indication is that new apps should no longer hide their menus, but rather make them intuitive to access in the app's UI.
For legacy apps, we'll probably see a menu button of some type appear along with the 3 softkeys at the bottom.
On my Honeycomb tablet either a button is in the top right corner or another is added to the bottom when menu is needed... I'm guessing HC is a good example of what we'll be getting, and if so I look forward to it
Thanks so much for a useful thread. I was actually wondering about that myself. Glad to know its non-obtrusive and clean
Sent from my GT-I9100 using xda premium
You have lost the search button though. Not all apps will handle this well... I had to tweak an app I was writing because of this (luckily found fairly early during testing on Honeycomb).
Of course for most apps search isn't useful - probably why they removed the dedicated key.
TonyHoyle said:
You have lost the search button though. Not all apps will handle this well... I had to tweak an app I was writing because of this (luckily found fairly early during testing on Honeycomb).
Of course for most apps search isn't useful - probably why they removed the dedicated key.
Click to expand...
Click to collapse
The idea is if the app needs search in order to function properly, you just put the search button up in the menu bar, just like they're doing with settings buttons.
Otherwise, the google search button is at the top of every homescreen now.
martonikaj said:
The idea is if the app needs search in order to function properly, you just put the search button up in the menu bar, just like they're doing with settings buttons.
Otherwise, the google search button is at the top of every homescreen now.
Click to expand...
Click to collapse
The menu button happens automatically (technically, since 2.3 android has called onCreateOptionsMenu at activity startup so it knows you need it already).
There simply is no search button in Honeycomb/ICS - you have to stick it on the options menu, the action bar*.. somewhere the user can reach it. That needs code (not much.. respond to 'search' in the options menu by calling onSearchRequested()).. existing apps will simply lose that function if they run on ICS assuming a button exists.
We're not talking about a lot of apps here.. Not much point in a search function in 'Angry Birds' for example. Just something to bear in mind when developing a new app or trying to work out if your favourite app will work without issue on ICS.
Home screen search is totally different.. that searches the global search (emails, contacts, etc.). Different class of app entirely.
* The honeycomb search widgets are really flexible, but of course not available unless you break compatibility with <3.0.
TonyHoyle said:
You have lost the search button though. Not all apps will handle this well... I had to tweak an app I was writing because of this (luckily found fairly early during testing on Honeycomb).
Of course for most apps search isn't useful - probably why they removed the dedicated key.
Click to expand...
Click to collapse
There are already quite a few phones out there without a search button. My almost 2 years old X10 doesn't have a dedicated search button and i never missed it. The search function is bound to long-press menu at the x10. Given the fact that ICS has a dedicated task switcher button, they could bind the search to long-press home for example. Just an idea though
Sent from my X10i using XDA App
qwer23 said:
There are already quite a few phones out there without a search button. My almost 2 years old X10 doesn't have a dedicated search button and i never missed it. The search function is bound to long-press menu at the x10. Given the fact that ICS has a dedicated task switcher button, they could bind the search to long-press home for example.
Click to expand...
Click to collapse
Hmm.. news to me - I've never seen an android phone without one. Lucky I was doing tablet compatibility testing then
There will probably also be custom roms that put it back (since a custom rom can do anything it likes with the buttons.. change their apparence, colour, hide them completely, make them dance up and down..).
TonyHoyle said:
Hmm.. news to me - I've never seen an android phone without one. Lucky I was doing tablet compatibility testing then
There will probably also be custom roms that put it back (since a custom rom can do anything it likes with the buttons.. change their apparence, colour, hide them completely, make them dance up and down..).
Click to expand...
Click to collapse
The Galaxy series in general (SGS1, SGS2) do not have a dedicated search button. They have just the menu, home and back buttons. However search is bound as a long press to the menu button which I guess won't be possible anymore. Haven't really found search to be that vital (maybe because I don't want to long press the menu button just to bring it up when I can search in other ways)
Since it's purely software, I know for a fact someone will mod in a search key.
Sent from my Samsung Galaxy S3 using XDA Ultimate App
That would be pointless. When search is available, the search box will appear in the menu bar of the app.
Sent from my Nexus S using XDA App
Related
Where would you rather have the "search" bar/icon?
Honestly, the search bar at the top of the home-screen is pretty ridiculous. Yes, I know, I know, they wanted to put the search bar on every homescreen, so you can search easily, and from a business standpoint, it would result in a lot more mobile searches. this way people don't have to go hunting for a search box.... But, is that really the best they can do? It intrudes the screen real-estate, and you still have to exit an app, and go to the homescreen to search for something. since searching is googles #1 priority, it should be easier than that.
what they should have done is put a search icon at the bottom, next to the 'back', 'multitask', and 'home' keys. the US carriers did this the right way. With it being down there, we would free some screen real-estate, and we would be able to search something with just one tap. Another benefit would be the "voice" search. I know a lot of people don't use this feature (as i have to tell and remind all of my friends about voice actions), but this is a huge feature, whether people realize it or not. we would be able to use 'voice actions' simply by holding down the search key. ANYWHERE we are in the OS. if we're playing a game, and we want to send a quick text message, just use voice actions and send a text message without even leaving the game! Also, with the button at the bottom, we can search within apps without having to hunt for the "search" key within the app.... some apps don't even have a "search" key visible! For example, if i want to search for a previous text message about a party in Austin, i can simply tap the "search" key at the bottom and search.... The button would be in a universal spot throughout the whole OS, and we wouldn't have to go hunting around finding it.
tl;dr version:
Search key should be on the bottom, next to the home, menu, multitasking buttons.
Pros
search anywhere in the OS
Search within apps (songs, files, text messages, etc)
saves homescreen real-estate
easier to search on the web
can conveniently do voice searches anywhere in the OS, even when in a game.
Cons
adds a fourth button at the bottom?
???
there is really no reason to disagree. I really hope someone figures out a way to add that button at the bottom. It's extremely useful.
bump.
&10char
I think you need a 3rd option, neither. If I want to search the web, I can click on the icon for it. Should be a users choice, what goes on their screens.
i voted at the bottom, as i use the "press and hold the search button" a lot in the car for navigating. what i'm sure i'll end up doing is dragging the voice search shortcut from the app drawer to the launch dock to mimic the way i'm used to using it on my nexus s and nexus one.
eric b
I never really used the actual button that often. I know it's there but I always find myself going to the search widget. The only times I really hit the button was when I was in an app like the music app and searching for a song or artist. I assume that's just going to be done with the press of the app menu button and the hitting search (making it now two button presses) but I don't really mind that. They are software buttons after all so they can totally be patched in with an update if the demand for them is large enough.
I wouldn't have minded the google search bar, if it were a "true widget", i.e. when you tap on it, the cursor would appear whilst you are still in the homescreen. But, correct me if I'm wrong, but the search bar simply takes you to a google search page, so it's not even a widget!! I felt the same way when using it in Gingerbread.
What they should have done, is to create a proper active widget and given us the choice to install it on the homescreen. I probably would install the widget on each homescreen.
Alas, we have to wait to a developer to release a ROM that takes the bugger off.
The fun thing about this is that it's all software; a custom lanucher can be used, and an adventurous (Depends on the way it was written; it could be very easy or very hard) dev could add a search button. Hell, El Goog themselves could even change this if they see it fit and there's enough community support for such a change.
Bmerz said:
I think you need a 3rd option, neither. If I want to search the web, I can click on the icon for it. Should be a users choice, what goes on their screens.
Click to expand...
Click to collapse
that's the thing. the "search" button isn't just for searching. the same button doubles as a "voice actions" button. it's like an extremely convenient way to text, set reminders, notes, call "walmart" or "pizza hut", or even search where the nearest olive garden is, and navigate to it. all these options from the touch of one button. I personally use voice actions A LOT. they're extremely useful if you remember the feature is there.
Lieu10ant said:
that's the thing. the "search" button isn't just for searching. the same button doubles as a "voice actions" button. it's like an extremely convenient way to text, set reminders, notes, call "walmart" or "pizza hut", or even search where the nearest olive garden is, and navigate to it. all these options from the touch of one button. I personally use voice actions A LOT. they're extremely useful if you remember the feature is there.
Click to expand...
Click to collapse
True, I wasn't thinking about that. I was more thinking it would be nice to have a choice if it's at the top - as it's my understanding that it's at the top of all 5 screens fixed.
No biggie, and certainly not a deal breaker for me - just thought it would be nice to remove it of one wanted to.
Bmerz said:
True, I wasn't thinking about that. I was more thinking it would be nice to have a choice if it's at the top - as it's my understanding that it's at the top of all 5 screens fixed.
No biggie, and certainly not a deal breaker for me - just thought it would be nice to remove it of one wanted to.
Click to expand...
Click to collapse
agreed. i would have thought the main reason of having "virtual" buttons was so we could be able to modify them. it only makes sense.
MoDaco moved the location of the menu bottons and forced them always on so I don't see why it would be impossible to put a search button down there and a long-press couldn't simulate what we have now with capacitive buttons.
This is the best part of Android -- everything can and will be fixed by a Dev to make it work.
http://android.modaco.com/topic/348762-21-nov-legacy-menu-patches-lhs-rhs-both-normal-always-on/
I might be a minority but I abuse the search feature on android so having it on the top is actually much better for me, i use it for even find apps that are already on my phone, I can't remember when was the last time i've seen my app drawer.
Didn't have a search button for almost two years (Galaxy S), never missed it. But the positioning on every homescreen is not ideal either.
Voted option one since I'm not a fan of the search button and don't need it as a software button.
Stigy said:
MoDaco moved the location of the menu bottons and forced them always on so I don't see why it would be impossible to put a search button down there and a long-press couldn't simulate what we have now with capacitive buttons.
This is the best part of Android -- everything can and will be fixed by a Dev to make it work.
http://android.modaco.com/topic/348762-21-nov-legacy-menu-patches-lhs-rhs-both-normal-always-on/
Click to expand...
Click to collapse
wow! that's amazing. that shows a 'search/voice' key is definitely plausible.
Does anyone think that there could be great potential in the Galaxy Nexus' soft key area at the bottom of the screen? As soon as they announced that the GN would have on-screen buttons, customization came to mind right away.
We've already seen Paul O'Brien's begin with his UI patches here, but I feel like we are only scratching the surface of what can be done.
For example, with my limited pondering, I was hoping that a dev or maybe CM could soon allow us to put shortcuts on that bottom bar for quick access to the certain apps that you always use. For me, I would love for Google Talk to have a permanent shortcut on that bar that I can access from anywhere as I use it almost religiously. Also, a shortcut that emulates the power button would be highly convenient as well so that I don't have to reach up to the side button as often. I can also foresee some themeing or button rearrangement and so forth.
Do you guys have any other ideas? As I'm not a dev of any sort, maybe I'm out of line in thinking that the bottom bar is flexible enough to customize. However, if it could be done (and Paul O'Brien already has demonstrated that maybe it could), the possibilities could be endless.
As a webOS user, I'd love some swipe gestures implemented for 'back' and a swipe up to open the app drawer
a swipe up for the drawer would really nice
Damn, I didn't even think of swipe gestures at all. Now my mind is really running wild.
bump for more ideas!
swype gestures are already available on go launcher
subxero123 said:
swype gestures are already available on go launcher
Click to expand...
Click to collapse
But we're not talking about the launcher. Didn't read the post huh?
I wish we could swipe down to make the thing disappear, which allows us to take advantage of the full 4.65 inch screen.
Swipe down - disappear
Swipe up - appear again
I think would be awesome if we could swipe the regular buttons to the side, showing new options (like we do with dock bar in almost every popular launcher). There, we could use app shortcuts, power widgets and other stuff, like the search and the option buttons.
I agree, I hope this is just a tip of the iceberg, it seems pointless to have all this potential and not utilize it.
how about instead of the soft keys have it scroll:
"wwwwwaaaaaasssssssssssuuuuuuuuuuuuppppppppppppp!!!!!!!!" w/ flashing text.
seriously though, being able to make them appear/disappear anytime would be a big plus in my book.
or say if you're playing a game/watching a movie, and someone calls you... rather then having the call notification pop up & take over, have the notification just appear in the soft key area.(i guess same for texts)
I think instead of putting toggles with the notification bar, a scrolling dock with these would be even better.
Like you guys said, swipe on the dock to the left or right to reveal Wifi/BT/GPS/etc. This seems easier than swiping down on the notification bar to bring it down.
On honeycomb we could hide them and theme them. Change animations and icons.
They didn't figure out how to add more or change up the order or add functionality because honeycomb wasn't open source like gingerbread and ICS.
So yea. Expect lots of cool stuff.
-Galaxy Nexus
-Asus Transformer
Since Android came out, I was hoping we would switch to soft-keys. Now we can fully customize the buttons, select preferred positions, preferred icon style, and which icons you actually have...
I'd be pretty content to just Swap the Menu and task manager buttons... I dont need a permanent task manager button that takes as much time to operate as it does to just navigate to the apps icon itself.. the menu button on the other hand I use in just about every app I launch.
sodequis said:
I'd be pretty content to just Swap the Menu and task manager buttons... I dont need a permanent task manager button that takes as much time to operate as it does to just navigate to the apps icon itself.. the menu button on the other hand I use in just about every app I launch.
Click to expand...
Click to collapse
I thought this too until I actually got down to using it on the GN.
I never used the task switcher on my other Android devices as it seemed too difficult and took too long for it to be worth it. However, having been using the GN for a couple of days now, I find its implementation (just a single tap) to be much more friendly and useful. I find myself using it all the time now to switch between what I am doing and can't imagine not having it.
player911 said:
On honeycomb we could hide them and theme them. Change animations and icons.
They didn't figure out how to add more or change up the order or add functionality because honeycomb wasn't open source like gingerbread and ICS.
So yea. Expect lots of cool stuff.
-Galaxy Nexus
-Asus Transformer
Click to expand...
Click to collapse
I'd just like to know what devs to talk to in order to make it happen
I was hoping for some app specific keys. For instance in the browser have a Forward, Back, Stop/Reload, Home, etc.
id love to see the buttons replaced with like gif animations. so cool
Enhanced said:
I thought this too until I actually got down to using it on the GN.
I never used the task switcher on my other Android devices as it seemed too difficult and took too long for it to be worth it. However, having been using the GN for a couple of days now, I find its implementation (just a single tap) to be much more friendly and useful. I find myself using it all the time now to switch between what I am doing and can't imagine not having it.
Click to expand...
Click to collapse
But, why not just allow the "Home" button to be the task-switching button via long-press like before? Is that extra pause for the long-press what you're referring to when you say it took too long?
Anyway, I, too, would like the Menu button back, but more importantly I want the Search button back. I can't wait for the ability to get rid of the G Search widget, put a dedicated Search button back in the soft touch area, and have the Home button as the task-switcher.
Brandon
Hi,
I use the menu key a whole lot more than multi task. How hard would it be to remap the multi task key to act like a menu key? Is it even possible?
Sent from my GT-I9100 using Tapatalk
If the apps is according to the new ICS look, Holo I think the theme is called, then the menu button is on the top right of the screen.
Seems to me it would be a hassle to press a button on the bottom right and then move youre finger to the top right to actually use the menu.
On apps not yet fitted for ICS I can understand what u mean, however this problem should hopefully be almost gone within not too long.
Would love to remap the useless.most recent programs button to act as a google search button, much like a long press on menu on my s2 does...
There are several threads about this. Here is one: http://forum.xda-developers.com/showthread.php?t=1480130
I just got my One X, so haven't tried anything myself.
But being able switch songs with the volume buttons while locked is what I'm looking for.
A must when you're outside in heavy rain or snow.
I'm hoping the discussion in this thread can inspire devs to really tweak Android.
An article I read a while back through Daring Fireball really got me thinking on how to fix the back button. This quote in particular:
They’ve replaced dumb hardware buttons with equally dumb software buttons.
Click to expand...
Click to collapse
http://daringfireball.net/linked/2012/01/16/android-buttons
This is also a good discussion on the topic:
http://www.theverge.com/2012/4/10/2...uidelines-update-settings-navigation#98209921
This is what I've come up with:
The back button should be dimmed or not visible at all when looking at the home screen.
This should also be the case for looking at the home/main scene of an app, for this reason:
The back button should never take you out of an app to the home screen, that is what the home button is for.
Instead of using the back button to close apps, use the task switcher to swipe away and actually close unwanted apps.
I know all this is possible, I just don't know how feasible it would be. I would love to see these changes in Android, what do you think?
I actually use the back button to exit out of applications, this way the app get's a chance to save any information to files. if it's forced closed, these writes can sometimes get missed and cause inconsistencies in the app (or lost time if game progress is not saved).
Having it on the home screen maintains a consistent look that many people appreciate. What i find is fantastic now is how the button rotate to the right place regardless of orientation, I KNOW that if I'm in landscape, the buttons will always be on the right hand side.
The buttons also dim down to dots in some applications (not sure if it's a new API) look at the camera app to see this in action. This removes the aesthetics of the bright buttons while leaving the functionality.
I guess you can argue about anything these days. The software keys will work better as apps are updated to 4.0 API, but to get full use out of them use AOKP, or just remove them altogether and use LMT's Pie menu. Problem fixed.
If the user accidentally opens an app, it wants to go back to where he was before. If the user opens Maps from the Gmail app, and the user wants to go back, the only way to do so is by pressing the back key.
If the user is in the App Drawer, accidentally opens an app, it wants to go back to the app drawer, and not back to the home screens.
The home button doesn't close the app, but tells the app that it's moved to the background.
The back button closes the app, tells the app it is being destroyed and lots of memory will be given back to the system.
With Android, it's possible to open app X within app Y(if the developer of app Y wants the user to do so). It wouldn't make any sense if the user had no way to undo that operation.
In my opinion, the navigation buttons are used properly.
EDIT:
Matridom said:
I actually use the back button to exit out of applications, this way the app get's a chance to save any information to files. if it's forced closed, these writes can sometimes get missed and cause inconsistencies in the app (or lost time if game progress is not saved).
Click to expand...
Click to collapse
The Android Documentation states that developers should save their data when onStop is called. onStop will be called both when user presses the home button, and when users presses the back button. So in theory, both buttons should work fine.
The buttons also dim down to dots in some applications (not sure if it's a new API) look at the camera app to see this in action. This removes the aesthetics of the bright buttons while leaving the functionality.
Click to expand...
Click to collapse
Yes, that's an API. It's possible to dim those buttons in some apps(like gallery/camera), and it's also possible to hide those buttons. The buttons will re-appear as soon as the user touches the screen. Look at the YouTube app if you want to see the buttons disappear and re-appear.
fifarunnerr said:
If the user accidentally opens an app, it wants to go back to where he was before. If the user opens Maps from the Gmail app, and the user wants to go back, the only way to do so is by pressing the back key.
If the user is in the App Drawer, accidentally opens an app, it wants to go back to the app drawer, and not back to the home screens.
The home button doesn't close the app, but tells the app that it's moved to the background.
The back button closes the app, tells the app it is being destroyed and lots of memory will be given back to the system.
With Android, it's possible to open app X within app Y(if the developer of app Y wants the user to do so). It wouldn't make any sense if the user had no way to undo that operation.
In my opinion, the navigation buttons are used properly.
Click to expand...
Click to collapse
I agree. I dont think it is "broken". It works well for me and I hate using my friend iPhone because it doesnt have a back button and I have to find it on screen.
Matridom said:
I actually use the back button to exit out of applications, this way the app get's a chance to save any information to files. if it's forced closed, these writes can sometimes get missed and cause inconsistencies in the app (or lost time if game progress is not saved).
Click to expand...
Click to collapse
I'm not talking about force closing apps, just regularly exiting apps only when they are swiped away from the multitask menu. I agree with everything else.
miketoasty said:
I guess you can argue about anything these days. The software keys will work better as apps are updated to 4.0 API, but to get full use out of them use AOKP, or just remove them altogether and use LMT's Pie menu. Problem fixed.
Click to expand...
Click to collapse
I'm not talking about removing the icons altogether, just make them contextually aware.
fifarunnerr said:
If the user accidentally opens an app, it wants to go back to where he was before. If the user opens Maps from the Gmail app, and the user wants to go back, the only way to do so is by pressing the back key.
Click to expand...
Click to collapse
This isn't the case anymore with ICS. I think the multitask button should be utilized instead. Granted, it's one extra tap, but I think it's more consistent.
fifarunnerr said:
If the user is in the App Drawer, accidentally opens an app, it wants to go back to the app drawer, and not back to the home screens.
Click to expand...
Click to collapse
I don't think that should happen. I realize that I'm arguing against actions Android has done since it's inception, but I believe that they are wrong now.
fifarunnerr said:
The home button doesn't close the app, but tells the app that it's moved to the background.
Click to expand...
Click to collapse
The home button shouldn't close an app, they should never have to unless the system decide when it needs to close an app, or the user does by swiping it away.
juliano_q said:
I hate using my friend iPhone because it doesnt have a back button and I have to find it on screen.
Click to expand...
Click to collapse
The same is for me as well, muscle memory is much faster. I just think the potential of the virtual back button is not even being scratched at yet.
thereddog said:
This isn't the case anymore with ICS. I think the multitask button should be utilized instead. Granted, it's one extra tap, but I think it's more consistent.
Click to expand...
Click to collapse
In Android, there are 2 ways of launching an app:
- As a new Task, this will add the app to the multitask interface
- As the same task, the new app won't be added to the multitask interface.
If you would like to see the second one, go to the Play Store, and click on the Email button. The Gmail apps opens. Now press the home button and open the multitask interface. You won't see the Gmail app, only the Play Store. If you open the Play Store, it'll open the gmail app, since it's the same task.
Press the home button again, and open the Gmail app(from the app drawer). The draft of the Play Store email won't show up, but it'll open the Gmail task that you opened before(for example, your latest received mail).
So, the multitask button won't work properly when the second way of launching an app is used.
The home button shouldn't close an app, they should never have to unless the system decide when it needs to close an app, or the user does by swiping it away.
Click to expand...
Click to collapse
In some cases, the back button would fit better. When you're in the Paypal app and want to close it, it's much easier to press the back button(then the user logs out), instead of pressing home, multitask button, and swipe away(thats 3 times as much time/energy).
In Android, there are 2 ways of launching an app:
- As a new Task, this will add the app to the multitask interface
- As the same task, the new app won't be added to the multitask interface.
If you would like to see the second one, go to the Play Store, and click on the Email button. The Gmail apps opens. Now press the home button and open the multitask interface. You won't see the Gmail app, only the Play Store. If you open the Play Store, it'll open the gmail app, since it's the same task.
Press the home button again, and open the Gmail app(from the app drawer). The draft of the Play Store email won't show up, but it'll open the Gmail task that you opened before(for example, your latest received mail).
So, the multitask button won't work properly when the second way of launching an app is used.
Click to expand...
Click to collapse
I actually agree with this. The back button would be used to to back into the store. GMail was never really opened though so it wouldn't have to be closed.
When you're in the Paypal app and want to close it, it's much easier to press the back button(then the user logs out), instead of pressing home, multitask button, and swipe away(thats 3 times as much time/energy).
Click to expand...
Click to collapse
In this case, I believe it is up to PayPal to have a Log Off button on the main scene of their app, and possibly in a context menu in other scenes.
although I get your main premise, I think it might be extra confusing when you have buttons just "randomly" disappearing and reappearing.
martonikaj said:
although I get your main premise, I think it might be extra confusing when you have buttons just "randomly" disappearing and reappearing.
Click to expand...
Click to collapse
Maybe not disappear, dim would work
thereddog said:
Maybe not disappear, dim would work
Click to expand...
Click to collapse
Possibly. But I think what you're looking for is a fundamental reworking of the OS here. The "Back" button is meant to work a certain way (completely at the OS level), and changing that changes everything.
What you're really looking for is the iPhone setup, where all you have is a "Home" and "Multitasking" (just double tap home, could be a separate button). All "Back" functions are handled at the app level, not the OS level. Back buttons are placed at the discretion of the developer.
The consistency provided by the Android way of handling "Back" at the OS level has many advantages I think.
The software keys actually work great. I've never had a problem with them. The menu key always comes up when its needed and I'm not finding myself missing the search key either.
Sent from my Galaxy Nexus using XDA
the whole back button talk has got me thinking. do you guys think the back virtual button will go away any time soon since the new style guides want a back button in the top left corner.?
The way the android back button works is simply brilliant and I hope it never changes. The application stack is very thoroughly thought out and designed for a specific reason. As already mentioned there are many examples/situations that wouldn't be possible if there was no activity stack history with the back button function. You just have to learn how the activity stack works.
And yes you should ALWAYS use the back button to leave an app, never home. It clears that activity stack. Only time to use home is when you want to background said app to come back to later, ie multitasking.
I pray to god they don't change the way the back button functions. I like having all my keys lit up whenever I'm not using a full screen application. I like that the back button goes through different apps/pages when you close out of it. This just integrates multi-tasking soooo much better. I don't want to have to wade through different clicks and apps just to get to a place I was before (i.e. backing into a different application). I'm not sure I understand the premise of this... please elaborate?
It is entirely possible to implement this in the OS, it's just a question if Google wants to do this. I personally am well adapted to Android's back button, and find it much better for multitasking than Apple's iOS design. Example:
1. Open Twitter, click on link from Tweet
2. Android opens the browser, I read whatever was posted, then hit back
3. I return to my Twitter feed, ready to move onto the next Tweet
This works in a multitude of apps, from Reader to Google Music to anything that wants to keep the previous app alive in the background. Can you imagine having a back button in the Browser that could both take you back a page and also take you back to the app you used to launch it? Apple's iOS solves this by eliminating any form of efficient multitasking in my opinion, as you have to double press home and select the previous app. The iPad does it better with gestures, but a soft back-key would easily suffice.
Additionally, Apple's iOS also has a varying design for the back-key, it's in different places for different apps. I personally love the static back-key on Android, and I've used both on a daily basis. You could dim the back button when on the home screen, but that would leave a gaping hole in the Navigation bar, in addition of wasting RAM/Processing power continuously disappearing and reappearing the key when you move from home-screen to app.
Got my G3 today and have been spending a good amount of time setting it up.
I am rooted and have Xposed w/G3 Tweaksbox.
I have a couple of things that still annoy me.
Is there a way to swap the behavior of the recent apps button? I want short press to be menu and long press to be recent apps. I figured out I can add a menu button using G3 Tweaksbox that does exactly that, but I can't remove the stock recent apps button, so I have 4 buttons there and I don't really like that.
When I drag up the recent apps button, I get a little semi circle selector with voicemate, search and quickmemo+ options. I have no intention of ever using voicemail or quickmemo+. Is there a place to change the 3 things that come up there?
lexluthor said:
Got my G3 today and have been spending a good amount of time setting it up.
I am rooted and have Xposed w/G3 Tweaksbox.
I have a couple of things that still annoy me.
Is there a way to swap the behavior of the recent apps button? I want short press to be menu and long press to be recent apps. I figured out I can add a menu button using G3 Tweaksbox that does exactly that, but I can't remove the stock recent apps button, so I have 4 buttons there and I don't really like that.
When I drag up the recent apps button, I get a little semi circle selector with voicemate, search and quickmemo+ options. I have no intention of ever using voicemail or quickmemo+. Is there a place to change the 3 things that come up there?
Click to expand...
Click to collapse
Most modern apps use the 3 dot menu button in the app interface and that is why most modern phones tablets do away with dedicated menu button so why would you want to do this?
rkirmeier said:
Most modern apps use the 3 dot menu button in the app interface and that is why most modern phones tablets do away with dedicated menu button so why would you want to do this?
Click to expand...
Click to collapse
Probably because I'm used to it coming from the Galaxy S3.
lexluthor said:
Probably because I'm used to it coming from the Galaxy S3.
Click to expand...
Click to collapse
You'll get used to the new buttons in no time. Just give it a little time and you'll look back at the S3 thinking the button layout was dumb.i had an S3 and S4. Love the G3 and the on screen buttons!
rkirmeier said:
You'll get used to the new buttons in no time. Just give it a little time and you'll look back at the S3 thinking the button layout was dumb.i had an S3 and S4. Love the G3 and the on screen buttons!
Click to expand...
Click to collapse
We'll see.
Anyone have a solution to my other issue?
When I drag up the recent apps button, I get a little semi circle selector with voicemate, search and quickmemo+ options. I have no intention of ever using voicemail or quickmemo+. Is there a place to change the 3 things that come up there?
I have the exact thing you want; but I don't want it. I'm rooted with Xposed framework and I randomly rebooted my phone earlier to have it turn back on with a functioning menu button. I looked through all the modules I had downloaded and even booted into safe mode but to no avail. I desperately need help with this.
Sorry that's not what you want, but if anyone knows how to get that, that's why I want.
I'm rooted with Xposed framework and I randomly rebooted my phone earlier to have it turn back on with a functioning menu button. I looked through all the modules I had downloaded and even booted into safe mode but to no avail. I desperately need help with this.
Sorry for reposting this... Thought I posted in a different thread but I guess I'm wrong. Please don't crucify me
As a long time samsung user, I'd say try without the menu button and see how you get on first.
But you can change the swipe up (and thats a swipe up from anywhere on the navigation bar btw, try it out), using tweaksbo, it's under:
theme > ring pad
And you can either turn it off, or add up to 5 custom apps.
The recent apps button is kinda key to android, it's like asking to remove the home button. Maybe instead of adding a menu button, make double tap on home be the menu button instead? Then you'd still have your three icons, and wouldn't lost out on recent apps, which you should end up using more now it's easier to reach (as opposed to a long press on the home button on samsung).
As noted most apps should use the 3 dot menu button so unless you have an outdated app you use regularly you really shouldn't even want a dedicated menu button. Ask the developer to update the app. It's the way forward and most all modern phones don't have a dedicated menu button, even the S5 replaced the menu button with the multitask button. It you really can't adapt ask the G3 Tweaks xposed developer if he can add a menu button option as the G3 already has the framework to change nav buttons.
How can you change them?
steviewunderr said:
How can you change them?
Click to expand...
Click to collapse
Just use the LG Display menu in settings to remove that button and xposed to add other button options. I'd like to know what people use, I'm on a 4 button system. I'll post pics when I get a chance
I somehow managed to change them on a system level if that's even possible. I disabled all modules and even booted into safe mode and they were still there. I'd like to change it back on whatever level it got modified. And the settings app crashes when I try to change the button combination.
The OP did not want to replace the resents button with menu, but only change its behavior: short press - menu, long press- resents. I am very interested in the same setup.
lexluthor said:
When I drag up the recent apps button, I get a little semi circle selector with voicemate, search and quickmemo+ options. I have no intention of ever using voicemail or quickmemo+. Is there a place to change the 3 things that come up there?
Click to expand...
Click to collapse
In TweaksBox under theme tweaks, then ring pad. It let's you select one in the free version. In the donate version you can select up to 5 shortcuts in the ring pad or disable it altogether.
settings / display / home touch buttons / button combination
I think they are standard options and not something I've added in. let's you add/remove a button such as the menu button or recent apps. screen is wide so I use 5 buttons.
Sent from my LG-D855 using XDA Premium 4 mobile app
personally don't use program #1 the ring selector as it is accidentally opening all the time with use of the back button.
Sent from my LG-D855 using XDA Premium 4 mobile app
Hold the recents and thats your menu button. Thats a default setting i believe. No need for g3 tweakbox unless a longpress isnt what you want. Idk which model you have but the tmobile version doesnt let you add the menu button on the nav bar.
Sent from my LG-D851 using XDA Free mobile app
lexluthor said:
We'll see.
Anyone have a solution to my other issue?
When I drag up the recent apps button, I get a little semi circle selector with voicemate, search and quickmemo+ options. I have no intention of ever using voicemail or quickmemo+. Is there a place to change the 3 things that come up there?
Click to expand...
Click to collapse
Did you ever find an answer that I'd love to able stick a few more bits on there seems like the only thing lg have forgotten let customise! Lol
jonny_blagwind said:
Did you ever find an answer that I'd love to able stick a few more bits on there seems like the only thing lg have forgotten let customise! Lol
Click to expand...
Click to collapse
G3 Tweaksbox,theme, ring pad, disable ring pad.