Motorola Droid X : Back Button Functionality - Cannot Simply Go Back One Menu Using The Back Key
Jul 15, 2010
This is my first android device and i'm loving it... but one thing that irks me is the use, or lack thereof, of the back button.
As I am navigating menus and options in the Settings, I cannot simply go back one menu using the back key. For example, if I go to Settings->Battery Manager->Battery Profile Options and want to go back to the Settings screen, I cannot.
Pushing the back button does nothing and I can only go back to the Settings menu by going Home, then re-entering.
Another quirk regarding the back button is when reading emails. Using a regular email account such as Hotmail, I cannot simply read an email and go back to the inbox using the button.
I'm finding that I'm using the back button A LOT whether browsing the web or just navigating the OS. It kind of sucks because the buttons on the droid x are well, really small, and sometimes hard to press because they are so narrow and flimsy feeling. And depending on how you are holding the phone, it could be a good bit of distance for your thumb to travel or I'm finding myself having to reposition the phone in my hands just to reach the back button, which you seem to need very frequently.
Anyone know of any kind of back 'swipe' implementation ? Like some software you can install that makes it if you swipe left to right on maybe the top bar it goes back?
Any way that you can make the back button in the browser retain the same function that it normally would - IE taking you back to the last program you were in. I hate how it takes you back a page instead - I mean the Browser's back button is there for a reason, right?
I call WebView.clearHistory(), but I am still able to go back after doing so. I want to reuse a WebView, but I don't want the back button to allow the user to go back further than the current "session" of using the WebView. Anybody know what is the best way to handle this? I thought for sure that clearHistory() would do it.
In my android application i have a video list screen,a buffering screen and a videoplayer screen. As soon as the user clicks an item from videolist screen ,he is navigated to buffering screen and then to videoplayer. In the buffering screen i am using Async task and doing the loading process in on background process.
Now my issue is like the user if has selested a video then gets navigated to buffering screen.But if the user clicks back when he is in buffering screen then initially he is getting navigated to videolist screen but immediately after that again he is navigated to videoplayer screen.
What i would like to have is either the back button should be made disable in buffering or should prevent the player tostart if back is clicked.
I'm roooted. I downloaded bootstrap and the first thing i did was create a nandroid back up for my x. then i proceeded to try and install tranquility rom. it got stuck in a bootloop. so when i rebooted into recovery it now goes for some reason to the droid stock recovery and i can't revert back to my back up. what do i do?!
Kind of new to Android, and definitely don't know too much about the devices. I was wondering whether every android device out there has a menu and back button? I just wanna make sure we could assume this as a fact...
I am working on a device that does not have a hardware Home, Back or Menu button. I am trying to create a soft keyboard with only these three keys but I have not been able to get it working. Does anyone have any insight into my problem?
I first looked into injecting keypresses into a WindowManager but this functionality seems to have been removed.
I then looked at creating a custom soft keyboard but that will not work either. Custom soft keyboards only inject their input into the text fields they are attached to. I can't send a Home, Back or Menu keypress to the Android system.
I finally got the Home button working by using this intent to tell Android to go to the Home screen: Intent HomeIntent = new Intent(); HomeIntent.setAction(Intent.ACTION_MAIN); HomeIntent.addCategory(Intent.CATEGORY_HOME);
Unfortunately, I have not found an Intent to send for Menu and Back.
Does anyone have a problem with the backlight on the Home/Menu/Back/seach buttons. On my Incredible sometimes they come on when I bring it out of sleep and stay on. Other times they don't come on at all. Sometimes they just come on in the middle of doing something on the phone.
Have added some apps from the market but can't remember if it was like this from the start. Did a reboot and battery pull but it's still occuring.
I have also had a couple phantom reboots when in sleep mode so not sure if it's related.
Is it possible to get the old functionality of the Gmail app back? I can't stand this new way of doing things.I don't *want* "Primary", "Social", "Promotions", "Updates", etc. I want all of my messages together.
Sometimes with the home or back button not responding at times? Kind of like a freeze where u have to press the buttons a couple of times then they will respond. Also, have you noticed that sometimes that pressing the power button will not wake the phone up? And when my phone call ends, it takes a while for the screen to come back from black so I can end the call. Should I get an exchange for my phone or are these issues supposed to be resolved with the update coming?
So I'm new to Android OS and the Droid X. I'm on the $54.99 plan that's just data/text, so I don't pay for any minutes. So I was wondering if it's possible to change out the capacitive phone button on the main screen to something more useful for me, or would I need something a little beefier than root access, like a whole new rom?
Also, would it be possible to create a capacitive back button on the screen to replace the mechanical back button?
I'd just like to know if anybody else finds their home row (home,menu,back) to be very picky about registering. I have to firmly plant my finger slightly above these keys to get them to work. I can never get away with pecking at them.
I was under the impression that the "back button" closes applications.
Apparently this is not true. I always use the "bb" however, I've checked and found that many apps were still open.
For instance: I open messages. Don't actually create one. Press "bb". Check apps and find that it is still running. So what is happening is that after a while there are a bunch of apps still running in the background.
Is there a way to force close? What is the proper way to close an application then?
I'm thinking about using a ViewFlipper for an Wizard like Activity. But I see one problem with this approach. The back button. Will the back button go back to the last shown activity or will the the Viewflipper somehow catch the back button event and only change to the last shown activity?
I have an onKeyDown event which is only needed for handling the Up and Down hardware keys in my app. For these it returns true, as they are handled. For anything else it returns false which I understand means that the OS should handle them. However, when I press the Back button, my onKeyDown is called and returns false, but there is no other effect. I want/would expect the OS to finish the current Activity and resume the previous one.
I notice on my eris that when i am on a menu with a black background that if i hit my back (bottom button) a little firmly, right above the button on the lcd kind of changes colors. Like if you press your laptop screen, its only a little bit though. If you could, please try this and report back.
Lurked for short time. Good site. Wife and I got Eris each. hers does not 'buzz' when tapping the 'home, menu, back and search' touch keys. Could not figure it out. Any suggestions? (Love the phones by the way!) OH!!! And, bought the Seido 3500 mah battery. it really is not that big, fits in my hand nicely. I will let you know how it lasts. charged last night and still strong today. But I will keep updated.
I have noticed while working in the emulator that whenever i get out of my app via any method other than pressing the back button, my toggle button (if pressed) will have its state saved and return to that state when i return to the app. im guessing its because its value gets saved in a bundle and reloaded when i return. when i leave the app via the back button, this does not happen and the toggle is always off when i return. is there any way to get the value of the toggle back if the user leaves via the back button, without having to save the value in a db table? alternatively, if my apps notification is in the status bar, i can be confident that the toggle should always be selected, so if there is no way to save the state, is there a way to find out if my apps notification is currently being displayed? then it would be easy to just set the toggle each time via a quick check of the status bar.