Related
Hi!
Was wondering if we could somehow override the home button long press to run a custom application instead of showing the recent apps list? This way, we could develop a custom application which shows more stuff rather than just 6 recent apps.
Some ideas are - integrating a task manager which shows running apps, favorite apps shortcuts, shortcut to app drawer etc.
I could develop the application but I wouldn't know how to override the home button long press! Any ideas anyone?
Cheers,
San
Well, there is at least one (paid) app that already does this (could be more but i don't know of them) - "MultiTasking Pro" http://www.cyrket.com/p/android/com.tkdtnek23.app.multitaskingpro
It would be nice to have extra functionality though, such as a clock (say, if you're in the middle of a game and want to check the time).
As for how it works, just from testing it out, it appears to act as a launcher (given that single home button press takes you to home launcher). I gather this as I had to set it as the default app when i pressed home button for the first time, aswell asthe fact that you have to select the home launcher in the app settings.
The way the app works is, press home button once brings up the menu (overlaying existing app). press it a second time and it takes you to the "default" home launcher as selected in settings. If you hold down home, the original app menu pops up, reinforcing the fact that this isn't a replacement per se.
Of course, overriding the original home button hold function menu would appear to be a much cleaner solution, and I welcome any info on that... whether its integrated into touchwiz or what not... One things for sure, is that samsung modified it to include a link to their "task manager" app.
TaskSwitcher is better, faster, uses less memory and it's completely free.
However no app can replace the long press. It needs kernel/system file modding.
Bec07 said:
TaskSwitcher is better, faster, uses less memory and it's completely free.
However no app can replace the long press. It needs kernel/system file modding.
Click to expand...
Click to collapse
Indeed, not possible. Does anyone know if it was implemented in other android phones?
PS. Power strip is better =) Very very fast and you can see 12 recent apps + widgets. Itching thumb is very promising, but its a plain beta for now.
Yeah but itching thumb uses a LOT of memory.
Bec07 said:
Yeah but itching thumb uses a LOT of memory.
Click to expand...
Click to collapse
For me Itching Thumb is currently the only task switcher style thing I find good enough (interface, functionality) to run next to Launcher Pro... I uninstalled all others I tried before.
But if I could have Launcher Pro on short press home, and Itching Thumb on long press home, that would be exactly how I would want that . Because I think optimizations such as memory use will come in time anyway.
I hope for the visual style to be integrated in android and have a real preview, live of the app.
Bec07 said:
However no app can replace the long press. It needs kernel/system file modding.
Click to expand...
Click to collapse
Any idea on what would need to be modified?
[Info]:
My only gripe about the trackpad wake mod (while it is awesome), is that we do it in order to avoid reaching for the awkwardly placed power button, but then we still have to reach for it anyway when we want to shut the screen back off. So it only helps us for half of the task.
After trying to find a way to directly map the search soft-key (or any of the soft-keys) to a power button, and failing, I've decided to come at it from a different angle. Attached you'll find a very simple app, that simply turns off the screen when clicked, along with instructions on how to map it to the search soft-key or the rosie button for sense users.
[Options]:
1. Search key short press. This is the method I use, as it is both the fastest and accessible from within any app. It will completely replace the search key. Single-tap it at anytime to turn off the screen. You'll need to install the app, and push the keyboard remapping file that I have also attached. Note that there are 2 different key mapping files, one for Sense ROMs and another for Vanilla. They will make the following changes:
Sense version:
-Search soft-key is now mapped to the user programmable key #2. Set it to open the Kill Screen app.
-www/com key is now TAB.
-USER 3 key, which didn't work anyway, is now BACK.
-USER 2 key, which is now not needed, is HOME.
-USER 1 key (left of the space bar) is left as normal.
Vanilla version:
-Search soft-key is now mapped to the user programmable key #3. Set it to open the Kill Screen app.
-USER 3 key, which is now not needed, is now BACK.
-USER 1 and USER 2 are left as normal.
2. Rosie's right button. This is for those who want to keep the search key as normal. See my rosie remap thread here for the option to have it launch when you press the right dock button. Keep in mind you still need to install the app, and you'll (obviously) have to be viewing one of the home screens to press it.
NOTICE: Do not post asking me to adapt this key layout to your needs, as we will end up with 500 different files before long. Instead, change it yourself! Editing this file is about as easy as it gets. You don't need anything special installed, or any programing experience whatsoever. Simply open the attached (or your own) vision-keypad.kl in any text editor (Notepad, Notepad++, etc) and change your desired key to your desired function. If you want to know what key corresponds to what number, you can boot to clockworkmod recovery --> advanced --> key test. Touch any key on the phone, and it spits out the number.
NOTICE #2: As with any app that is given administrator permissions, you will need to remove the app from the admin list in order to uninstall it. Menu --> Settings --> Security --> Select Device Administrators --> Uncheck Kill Screen. Then uninstall as normal. You will be reminded to do this when you first give the app the admin permissions.
[How To]:
Method 1 - Install the app, then grab a copy of the modified key layout and then reboot to recovery and enter this code:
adb shell mount /system
adb shell rm /system/usr/keylayout/vision-keypad.kl
adb push [your saved file location]\keypad_owamod_xxxxx.kl.zip /system/usr/keylayout/vision-keypad.kl
Reboot and enjoy.Method 2 - Install the app first, then see the linked thread for how to get the modified rosie.apk
That's pretty awesome Will definatley try out when I get a Z
Great news but something like that exists already for a few monts:
http://forum.xda-developers.com/showthread.php?t=795811
I used it on the Nexus One and now on the Desire Z.
Works great! Thanks a lot!!
g4rb4g3 said:
Great news but something like that exists already for a few monts:
http://forum.xda-developers.com/showthread.php?t=795811
I used it on the Nexus One and now on the Desire Z.
Click to expand...
Click to collapse
Not quite.
You should read the whole post, people fail to do so far too often on this forum. Of course the app exists, there are multiple versions, both pay and free, on the android market and floating around the forums.
What does not exist, is the remapped key file to make the app launch with a short press of the search key (method #1) and the remapped rosie buttons to launch the app from the right dock button (method #2).
The only method I really cared about is the short-press search button (method #1), which completely replaces the search button, so that it functions to turn off the screen (like it should have been from the factory) like the G1. This also allows it to work while the screen is still locked, so you can single press the trackpad, check the time/messages/missed call, then turn the screen back off without ever unlocking it! But I made this mod and guide, so that you have THREE options: the long-press method (like the one that you linked to) AND two NEW ways.
Using all of the default files while running CM 6.1.1 Colourized, I can get my DZ to sleep only by long-pressing the Search button, not a short-press.
I checked the .kl file and confirmed the USER2 key is 217 and that matches my Key Test number in Recovery.
A short-press of my Search button doesn't do anything.
I've set KillScreen as the default app for the long-press and it works as it should, but I'd like to leave that as a Search (Vlingo) button and have a short-press go directly to KillScreen.
Suggestions?
I tried the Rosie_killscreen.apk , it installs ok i get the little power icon on my Rosie launcher bar but when I press it, it doesn't do anything, I tried to re-download the file in case it was corrupt and re-install it but the same thing happens, nothing. I installed the Rosie_contacts.apk and it work fine but can get the Rosie_killscreen.apk to work. Has anyone gotten the Rosie_killscreen.apk to work?
EDIT- My fault forgot to install the main app..... Sorry, let me try this again.
Update: The app works great on the Rosie_launcher, Just a reminder to install the KillScreen.apk first, then follow the process for pushing the app to the Rosie launcher.
I like this very much!! I have Launcher Pro Paid and I have set it up as one of my swipe options on the dock.
I use cm6.1.1 lockscreen gestures and the "screen off and lock" app. I setup a gesture of "L" and link the gesture to the "screen off and lock" app so when I am on the lockscreen and do a "L" gesture and it shuts off the screen. I also have it set as a shortcut in the dock for adw launcher too so I can lock/screen off just by pressing it. So far it works great.
B73C said:
Using all of the default files while running CM 6.1.1 Colourized, I can get my DZ to sleep only by long-pressing the Search button, not a short-press.
I checked the .kl file and confirmed the USER2 key is 217 and that matches my Key Test number in Recovery.
A short-press of my Search button doesn't do anything.
I've set KillScreen as the default app for the long-press and it works as it should, but I'd like to leave that as a Search (Vlingo) button and have a short-press go directly to KillScreen.
Suggestions?
Click to expand...
Click to collapse
I'm not really sure what the issue is. If you choose the method where Kill Screen acts as the short-press search, you will not have a long press function anymore.
I'm experiencing a problem with the long press method where the screen turns off for a second but immediately turns back on to the lock screen. Manually launching the app shuts off the screen properly. Anyone else getting this?
I am having problems downloading the 2 .zip files
I use the one called "Lock Screen Button" in the market. It's simple and the icon is very clean.
cyricc said:
I'm experiencing a problem with the long press method where the screen turns off for a second but immediately turns back on to the lock screen. Manually launching the app shuts off the screen properly. Anyone else getting this?
Click to expand...
Click to collapse
After a bit of testing I'm pretty sure this has something to do with the capacitive buttons remaining active for a very brief time after the screen shuts off: since the search button is held while the kill screen action runs, it immediately triggers wake. Pressing the power button while holding down any of the capacitive buttons has the same effect (screen turns off then back on to lock screen).
I'm guessing this can be fixed by adding a delay to turning the screen off. Or by setting the capacitive buttons to not wake the screen somehow.
Can't uninstall kill screen app
I installed the KillScreen.apk, however if I try to uninstall the app via the manage applications I get "Uninstall not succesful" and app is still in my applications list.
How can i permanently remove the KillScreen.apk?
As for the app not working properly with the long-press method, you are right, it seems to be bugging. I will take a look and hopefully get a new version up soon. The other two methods work ok, but I don't use that method, so I didn't do enough testing
LQT said:
I installed the KillScreen.apk, however if I try to uninstall the app via the manage applications I get "Uninstall not succesful" and app is still in my applications list.
How can i permanently remove the KillScreen.apk?
Click to expand...
Click to collapse
This is the second time in one thread I've had to quote someone and tell them to READ. Do they not teach you kids to read in school anymore? READ PEOPLE. You are working with rooted phones in a programming development forums, you SHOULD have some smarts to you.
Since you missed the "--WARNING!!!!---:READ:---WARNING!!!!--" text in all caps across the whole screen when you first gave the app permission, allow me to take my time to type it again for you: You need to remove ANY app that has been given administrator permissions from the admin permissions list in order to uninstall it. Since you gave this app administrator permissions, you need to do so. Menu, Settings, Security, Select Device Administrators. Uncheck kill screen. There will be a pop up box. Do not just hit the ok blindly, READ that too. Then uninstall.
the1wingedangel said:
Since you missed the "--WARNING!!!!---:READ:---WARNING!!!!--" text in all caps across the whole screen when you first gave the app permission, allow me to take my time to type it again for you: You need to remove ANY app that has been given administrator permissions from the admin permissions list in order to uninstall it. Since you gave this app administrator permissions, you need to do so. Menu, Settings, Security, Select Device Administrators. Uncheck kill screen. There will be a pop up box. Do not just hit the ok blindly, READ that too. Then uninstall.
Click to expand...
Click to collapse
Dude relax, no reason to get so agitated!
I actually did press the ok blindly, the reason for that was that the phone didn't do anything after the installation. So i tried to tap the screen to make it work and by accident tapped the ok button before reading the warning post.
If you do tell people to read, please give them the information to read. Either put it in first post or put it somewhere inside the app so people can re-read it.
I managed to uninstall the app, thanks for the info.
Relax, cheers
LQT said:
Dude relax, no reason to get so agitated!
I actually did press the ok blindly, the reason for that was that the phone didn't do anything after the installation. So i tried to tap the screen to make it work and by accident tapped the ok button before reading the warning post.
If you do tell people to read, please give them the information to read. Either put it in first post or put it somewhere inside the app so people can re-read it.
I managed to uninstall the app, thanks for the info.
Relax, cheers
Click to expand...
Click to collapse
Actually I do have reason to get agitated! (Even though I wasn't that upset at the time, my posts often just come across that way) Because after 2 years of seeing stuff like this with android users, it gets very tiring! For example: the countless comments on the market for an app that says in the description "ONLY works on Nexus 1" and the commenter says "Does not work on Droid" and rates it 1 star. But I can forgive those, because its the general public. On a development forum, however, I expect nothing less than every member to have their wits about them. Though, realistically, it's probably just wishful thinking.
the1wingedangel said:
Actually I do have reason to get agitated! (Even though I wasn't that upset at the time, my posts often just come across that way) Because after 2 years of seeing stuff like this with android users, it gets very tiring! For example: the countless comments on the market for an app that says in the description "ONLY works on Nexus 1" and the commenter says "Does not work on Droid" and rates it 1 star. But I can forgive those, because its the general public. On a development forum, however, I expect nothing less than every member to have their wits about them. Though, realistically, it's probably just wishful thinking.
Click to expand...
Click to collapse
Lol! I do that same thing in my thread. It's hard to not snap on some people lots of times. I have come to the conclusion that a lot of people just don't have the brain power to read/comprehend certain things. I've had to learn to relax a bit... It's quite useless to argue with them because it just rolls off them with no worries while people like us simply struggle to understand why and end up getting pissed off. It's tough being cynical sometimes
Thanks for the little app! Just some feedback. Wanted to install method 1. Followed the steps. However, it still acts as method 3, long press on search, instead of just the short press. Running Virtuous 0.8.1.
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
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.
I've resorted to this because...
1. Modifying "kl" files doesn't work for me.
2. I don't like using softkeys
*PROCEED AT YOUR OWN RISK. I AM NOT LIABLE IF YOU SOMEHOW DAMAGED YOUR PHONE.
*EVERYTHING IS REVERSIBLE by just removing the apps listed below.
Hi everyone,
If you are just like me, wanting to mitigate from accidentally clicking home button while supposedly trying to click space bar while typing, here is my suggestion.
1. You need root
2. Install xposed app
3. Install xposed gravityboxLp module (NO NEED FOR THIS - EVERYTHING CAN BE DONE ON Xposed Addition Module)
4. Install xposed additions module
Xposed additions: you need to remap each button to your preference.
My current setup:
BACK button:
click = go back
click+hold = forcekill foreground app
HOME button:
click = disabled
click+hold = go home (this may not work, so you might need to call your launcher activity instead)
RECENT button:
click = show recent apps
click+hold = screenshot
Don't forget to click thanks and, if not so burdensome, reply here if this has helped you. thanks
BTW, if you guys have simpler/better solution that this, please do share. thanks.
xgneilx said:
BTW, if you guys have simpler/better solution that this, please do share. thanks.
Click to expand...
Click to collapse
Change keyboard to Google keyboard...
Oh, and stop eating all those sweets and lollies that are making your fingers pudgy...
ultramag69 said:
Change keyboard to Google keyboard...
Oh, and stop eating all those sweets and lollies that are making your fingers pudgy...
Click to expand...
Click to collapse
thanks for this suggestion. however, it didn't get the job done
One way to temporary disable the home and task switch key is to use screen pinning:
http://www.howtogeek.com/202841/how-to-pin-screens-in-android-5.0-for-more-security-and-privacy/
Back key still work, and it last until you quit the app. I only use it for running Asphalt 8, since my left thumb tends to hit those keys when playing.
cf18 said:
One way to temporary disable the home and task switch key is to use screen pinning:
http://www.howtogeek.com/202841/how-to-pin-screens-in-android-5.0-for-more-security-and-privacy/
Back key still work, and it last until you quit the app. I only use it for running Asphalt 8, since my left thumb tends to hit those keys when playing.
Click to expand...
Click to collapse
I tried this one too. But pinning foreground apps just just to mitigate from accidentally clicking the home won't work for me. thanks for this though.
xgneilx said:
In gravitybox, manage the behavior of your capacitive buttons by appropriating each purpose to meet your requirements
In xposed additions, you need to remap your home button and set a condition that will disable it's click functionality.
Click to expand...
Click to collapse
It works. I only installed the xposed additions, and set the home button to respond to long click on screen-on.
"RECENT button:
click = show recent apps
click+hold = screenshot "
I am sure that there are some applications where the default "click+hold" function of recent apps button, i.e. calling up the app menu, may come handy as those apps don't have the three dots in upper right corner or that hype design....yes, "material" they call it
How would you proceed to call up the menu in such cases?
Just my observation/warning for users, otherwise your solution is a good one, I used to have similar settings through Gravity Box.
Heh, my thumb still keeps hitting a "." key on my favourite keyboard instead of spacebar due to ZF2 having a slightly larger screen than my previous device )
mp3comanche said:
"RECENT button:
click = show recent apps
click+hold = screenshot "
I am sure that there are some applications where the default "click+hold" function of recent apps button, i.e. calling up the app menu, may come handy as those apps don't have the three dots in upper right corner or that hype design....yes, "material" they call it
How would you proceed to call up the menu in such cases?
Just my observation/warning for users, otherwise your solution is a good one, I used to have similar settings through Gravity Box.
Heh, my thumb still keeps hitting a "." key on my favourite keyboard instead of spacebar due to ZF2 having a slightly larger screen than my previous device )
Click to expand...
Click to collapse
Good that you've mentioned the possible issue with app menu. I honestly haven't experienced the issue with any app that i use to call upon app menu, but i think we can still add double tap in gravity box on recent key to do that.
So far, i am still mistyping due to big hands, but at least I no longer experience being brought back to home accidentally.
great one
does anybody here have better solution than this?