Why are the volume buttons the wrong way round? - Galaxy Tab 2 Q&A, Help & Troubleshooting

Was this tablet made for never using in portrait mode or something?
Up to lower volume, down to increase? wtf?
Also, people say press volume down and power to boot into the bootloader (and I need to use the button on the right, even though this is technically up) and then on that screen it says press volume down again, but I need to press the button on the left this time
anyone know why they did this?

I don't really understand your issues with the bootloader sequences but I will agree that it seems ass backwards when you are holding the tablet in landscape with the buttons on top.
I would love to see Samsung (or some gifted XDA user )add the option to have the volume keys follow the UI.

You should be able to remap the volume keys to be reversed if you use the device predominantly in portrait mode.
But like Caldair said, I'd love to see them auto remap based on orientation.

I think basically what it boils down to is on the 7" its viewed more as an E-reader type device and so they assume portrait orientation so the button furthest from the power button is volume down as it points down but on the 10.1 it's more like a computer screen so they are in landscape mode so left in down and right is up, this is also seen in there positioning of the USB 30-pin connector (which denotes the "bottom" side of the device).
I just find it weird that you have 2 versions of basically the same device just different screen sizes and the volume buttons are ass backward from each other, makes things really screwy when you try to tell people how to get into download mode or recovery.
Frankly the 10.1 volume buttons is far less an issue then the decision on the 7 to put the speakers on the "bottom" which when your watching a movie or doing about 90% of things in android that are in Landscape all your sound comes from ONE side.

It is badly designed, compared to the previous version, I think they just didn't care.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Related

[BUG] Hardware Buttons not changable

I have following Problem:
I would like to change the Hardwarebuttons of my Leo but in the "Keys" screen there are none -.-
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Also I have the Problem that it I cannot turn off the Windows Lock completely. I managed it to disable it when the device wakes up, but the lock activates when I turn off my phne with my HangOn button
you can use AEbutton plus
is working like a charm in leo
http://ae.inc.ru/aebplus.php
I wouldn't call it a bug. The buttons on the HD2 are already assigned to specific tasks already.
They wouldn't really want anyone assigning them to anything else. It's not like there are spare buttons (like on the X1) that aren't already assigned to specific functions.
So, like I said, not exactly worth calling a bug.
I cannot override the the hangOn button so the problem with the Windows Mobile Lock stays....
I've posted a reg for the send key in the hints and tips thread first page
no go
Looks like Aebutton and the reg key breaks existing button assignment.
I just installed AEBUttonPlus [because I had used it before on my HD - and I HATE not being able to scroll up/down a list of items WITHOUT triggering/opening one (EG spam email) ] - Stupid Windows/HTC AGAIN!
So I was trying to setup the HD2 the same way as I had it on my HD - that is;
'volume up HARDWARE button' has TWO functions = *one press = scroll up* : *Long press = Volume up* (same design for down of course)
But....I think I've possibly become less intelligent over the past year or something because I cant figure out how to do it in AEButtonPlus (and the website isn't much help) The prog itself isn't very intuitive, that much I do recall, but somehow I did manage it last year, to sort the HD - but can't replicate it now
If anyone knows what I mean and can help I'd be very much obliged - thanks!

Safe Mode?

I was using the Music player. After an MP3 file ended I looked at my phone and it was in Safe Mode (the text "safe mode" was in the block in the lower left-hand corner of the screen.
My live wallpaper was replaced the default Nexus wallpaper. I rebooted and it came back to normal. Any idea why this happened? I don't believe my phone rebooted into Safe Mode. It seemed to just enter into that state.
Any ideas?
all android phones have a SAFE MODE
each phone has a different combination of keys, or screen wipe, or combination of both to enter into the SAFE MODE
as the name implies it is just like your PC machine, it lets you go into SAFE MODE to fix whatever problem might be preventing it from working normally
rebooting the phone will go back to Normal Mode
My Nexus S did something similar just now. Screen off, screen on in safe mode.
Does anyone know why I would nearly instantly switch to safe mode?
I'm on ASOP 2.3. I rebooted and everything was normal.
To boot into safe mode, you hold the 'menu' key while booting
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I'm sorry if my post was unclear.
I did not hold down the menu key on boot. I did nothing special to enter safe mode.
My phone was on, I blanked the screen with browser and LauncherPro running, and when I unblanked my screen 5sec later it was in safe mode with the default launcher.
Has anyone else seen this specificity?
Supermighty said:
I'm sorry if my post was unclear.
I did not hold down the menu key on boot. I did nothing special to enter safe mode.
My phone was on, I blanked the screen with browser and LauncherPro running, and when I unblanked my screen 5sec later it was in safe mode with the default launcher.
Has anyone else seen this specificity?
Click to expand...
Click to collapse
Are you sure your phone didn't reboot on its own you just happened to hold the menu button? xD
That would be a slim chance. The time from me blanking the screen and putting it in my pocket to pulling it out again was maybe 5 seconds. I didn't see the nexus boot screen, so I don't think it did. But I guess it's possible.
I haven't had it happen since then.

Hardware buttons backlit?

Are the hardware buttons of the G-tab backlit (eg, does the writing glow in the dark)? (home, settings, etc)
My wife thinks they look like they should be backlit, but they aren't lighting up. I'm not sure if this not-lit by design, or if the lights on our unit are broken.
Can anyone confirm if their G-tab buttons are backlit?
Not backlit.
ml_boston said:
Are the hardware buttons of the G-tab backlit (eg, does the writing glow in the dark)? (home, settings, etc)
My wife thinks they look like they should be backlit, but they aren't lighting up. I'm not sure if this not-lit by design, or if the lights on our unit are broken.
Can anyone confirm if their G-tab buttons are backlit?
Click to expand...
Click to collapse
If you're talking about the touch buttons next to the screen (search, home, menu, back) they are not backlit. There are some modders here that have tried diy projects to add LEDs or drops of glue to add a bead next to them so that you can either see them or feel them in the dark. ROMs like VEGAn have them as soft buttons on the status bar on the screen for you to use as well.
If you're talking about the hardware buttons like power and volume they are also not backlit.
Here is a simple mod to locate the buttons in the dark.
Simply cut a tiny groove in the plastic bevel next to the buttons. They should have been there from the beginning if you ask me.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
magqccom said:
Here is a simple mod to locate the buttons in the dark.
Simply cut a tiny groove in the plastic bevel next to the buttons. They should have been there from the beginning if you ask me.
View attachment 552987
Click to expand...
Click to collapse
What does that do? Allow you to "feel" where they are, or does this illuminate them in some way? If it is a feel thing, there are many ways to "mark" them with some tactile application for "feel".
insight3fl said:
What does that do? Allow you to "feel" where they are, or does this illuminate them in some way? If it is a feel thing, there are many ways to "mark" them with some tactile application for "feel".
Click to expand...
Click to collapse
Indeed, it just allows to feel, but away from the buttons themselfs who are touch sensitive (so you don't have a problem when you feel the wrong one and it feels you right back). It also cannot be rubbed off or become sticky with use (like glue beads, for example).
Button Savior located in the market is a nice solution for those not wanting to modify the exterior. It allows you to access the same commands on screen that the touch sensitive one do.
Wow, thx for that tip Mike - just what I was looking for!

[Q] Remapping BT Headset Buttons (Change Call Button function)

I recently bought a Nokia BH-503 Bluetooth headset, and it has 4 buttons, 3 for media, that work flawlessly, and a Call button. Here's an image:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Since the Xoom doesn't have phone functions, this button is unusable for me, so I thought about remapping it, but couldn't find any app that could do it. Most apps would work with headsets with 3 buttons.
If possible, I want to remap it for voice commands/action, I'm not sure what is supported on the Xoom (I had some problems with one of my tests, saying Voice Commands are unsupported), so, anything that I could touch the button, speak a function, and receive it by sound.
I searched and couldn't find, in fact, when searching for headsets and Android, usually I would find that calls works, and media not.
Xoom Wifi - Stock ICS 4.0.3 - Rooted
//////////////////////////////////////////////////
My tries [None worked]
//////////////////////////////////////////////////
I tried Headset Button ControllerTrial, but not only the Debug mode didn't work, there were no options related to a "fourth button".
I also tried Button Remapper, and it found the buttons, but...
It shows me the buttons (If I disconnect the headset, it crashes, so I believe they are all from it) (I don't know shy it won't show the 3 hardware buttons...), but there are buttons that just don't exist.
I tried changing the only button not directly specified on the phone controls, the Stop button, to Search, but nothing changed and the buttons are doing the exact same thing.
Thoughts
I have started researching this subject but have made little progress.
I believe how the remapping software you are using just modifies the Keyboard layout files in order to remap the functions (just an assumption). I tried doing this myself and it failed.
I think the reason is because bluetooth commands are handled separately from the keylayout mapping. It is built into the android system itself so it needs a custom program to intercept the command and set another function.
For reference, I would suggest you read this: stackoverflow.()com/questions/6287116/android-registering-a-headset-button-click-with-broadcastreceiver
The only solution I can come up with is writing a custom app. It is doable, but will take some time.

In Call Volume Issue

I posted this in the Pixel XL forum as well.
So I just recently noticed that I cannot adjust the volume while on a phone call. The volume buttons trigger the slider, and the slider moves, but the volume does not change. Also, the volume slider doesn't go all the way down. It stops at about the 15-20% mark. Here's a screenshot of the volume slider as low as it will go:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
After some searching, I found a PIxel User Community post on the same topic, and posted there as well: https://productforums.google.com/forum/#!topic/phone-by-google/P0Lc5nX-Huk
I also found a news item from last summer, describing a similar problem with the Nexus 5: http://www.phonearena.com/news/Goog...l-bug-brought-on-by-the-latest-update_id83468
The following description from back then is far too much like what is going on with my phone to be a coincidence:
"Some of the issues that users are complaining about include the inability to adjust the volume during a call, even though the slider does move. Another complaint found on the AOSP Issue Tracker includes one from a Nexus 5 user who is unable to move the volume slider under the second lowest position."
Click to expand...
Click to collapse
So, is anyone else here having the same issue? Any ideas on a fix?
Have my phone since 15th of Dec and haven't yet seen this issue. Were you just talking on the phone normally by holding it to your ear?
Yes. It was too loud, so I tried lowering the volume, and nothing happened. Pulled the phone away from my ear, and watched the volume slider go down, but no volume change happened.
Now that I'm aware of it, I check all the time, and this happens on every call now.
Mine definitely adjusts the actual volume. Are there any apps or mods you have installed that could interfere with this?
farfromovin said:
Mine definitely adjusts the actual volume. Are there any apps or mods you have installed that could interfere with this?
Click to expand...
Click to collapse
Not that I know of. My bootloader is unlocked, but I have not flashed a custom recovery or rooted. I'm just running stock, with BL unlocked. Not sure what app or apps would cause this issue.

Categories

Resources