Related
Is there a way to disable the autolock or auto screen blank for specific programs?
The reason I want this is because I would like to be able to change and see my music without having to hit the power button and/or unlock the phone every time.
Setting the registry key:
HKLM/Software/HTC/AudioManager_Eng/Config/enter_suspend to 0 doesn't help
Any ideas?
I'm sorry if this has already been asked before, but I couldn't find it with the search function.
yeah i'll second that. I was actually going to ask if there was a way you could skip songs without unlocking the screen. its a real pain
I use G-Trigger to skip songs and play/pause. But you still can't see what's playing on the screen.
http://forum.xda-developers.com/showthread.php?t=494267
I just received my phone today.I know that there is "Voice Search" and "Google Now" built in, but I cannot seem to launch them from the lock screen using a headset.
I have also tested the headset (3 button), and it does work; I can play and stop music both locked and unlocked screen and Google Now activates when I hold middle button unlocked, but nothing happens when the phone is on lock screen.
As far as I am concerned, "Google Now" & "Voice Search" are useless unless I can activate them while they are in my pocket, for driving and walking. Furthermore, when I ask it to send a message to someone, it simply displays the message, not repeating it to me, or asking me if I would like to send. I see lots of reviews, claiming "Google Now" is far superior to S-voice and Siri (iPhone) but in my opinion, they should not be categorized together, "Google Now" simply does not do the things I need it to do. If at any point, I need to look at the screen, or press something on the screen, the whole purpose of Voice activation is rendered useless. I cannot be the only one out there with this problem. I am open to any suggestions to solve this issue, or else I must go back to iPhone for the sake of the voice dialing that is headset activated, as well as the ability to read out my messages and send them.
I have tried 3rd party apps like Headset Button, with no luck and it still does not allow Google Now to run in the background with screen off, and requires another third party app, Screen Off & Lock to do just turn off the screen with a different combination of presses on the headset. The lack of any sort of physical button on the N4 is also another problem.
I am open to any suggestions or comments if I am simply just missing something from the features. Please excuse me if I sound rude or a hater, all I am trying to do is find out the problem to my issue, and potentially inform others if they have the same needs as me.
Cheers. :good:
So because it doesn't do the things YOU need it to do, they shouldn't be categorized together?
If you want to access Now with your headset then turn off the screen lock function.
AFAIK, I don't think Google Now will do the things you want it to do out of the box. If you're willing to use third-party apps, though, I think you may be able to get the behavior you need by using Tasker (https://play.google.com/store/apps/details?id=net.dinglisch.android.taskerm). A quick search also turned up this app (https://play.google.com/store/apps/details?id=com.sonalight&hl=en), which supposedly can read/send text messages by voice alone.
As far as physical buttons go, well .. that's something you're just going to have to get used to, sorry
tengen said:
AFAIK, I don't think Google Now will do the things you want it to do out of the box. If you're willing to use third-party apps, though, I think you may be able to get the behavior you need by using Tasker
Click to expand...
Click to collapse
How would Tasker accomplish this?
thanks for all the responses
is there itleast a way i can activate voice dialing from my headset button, i feel like that must be a feature for driving
i now have no lock screen, and when holding down the middle button of my headset, still get nothing
please help.
vicson88 said:
thanks for all the responses
is there itleast a way i can activate voice dialing from my headset button, i feel like that must be a feature for driving
i now have no lock screen, and when holding down the middle button of my headset, still get nothing
please help.
Click to expand...
Click to collapse
I have the same issue , headset button doesn't start voice while screen is off even if there is no screen lock ... Bit daft
Sent from my Nexus 4 using xda premium
Hi all,
I recently picked up the 2.0MHL to HDMI cable along with a Bluetooth mouse and Bluetooth (what appears to be Apples style) keyboard to use with my S4. So far I'm enjoying the experience in terms of uses and navigating relatively easily through the phone. Currently using NOVA as my launcher. Volume, home button, back buttons were easy to figure out. Accessing the multi-window, recent apps/task killer is not a problem. I can't however, for the life of me figure out how to access the MENU button via. the keyboard or mouse. I've done various searches and YouTube videos online and people mention how the right click doesn't access the menu but neglect to mention how to ACTUALLY access the menu. I did see 1 video where it mentioned Control P but when I had tried that, it was a shortcut to select either music player or Google play. Has anyone else had this problem? Any luck with finding the right short key? Thanks in advance for your time and consideration.
Moosterly said:
Hi all,
I recently picked up the 2.0MHL to HDMI cable along with a Bluetooth mouse and Bluetooth (what appears to be Apples style) keyboard to use with my S4. So far I'm enjoying the experience in terms of uses and navigating relatively easily through the phone. Currently using NOVA as my launcher. Volume, home button, back buttons were easy to figure out. Accessing the multi-window, recent apps/task killer is not a problem. I can't however, for the life of me figure out how to access the MENU button via. the keyboard or mouse. I've done various searches and YouTube videos online and people mention how the right click doesn't access the menu but neglect to mention how to ACTUALLY access the menu. I did see 1 video where it mentioned Control P but when I had tried that, it was a shortcut to select either music player or Google play. Has anyone else had this problem? Any luck with finding the right short key? Thanks in advance for your time and consideration.
Click to expand...
Click to collapse
I know this is a late reply to your question, but maybe I can help. I bought a mini bluetooth keyboard designed to use with windows, and for a while I had the same problem. I. could access everything on my S3 except the menu. I searched, found your post, then started randomly trying different buttons. I'm not sure if your board has this key, but it's between the right Alt and Ctrl keys, it looks like a square with an arrow pointing inside it. That`s the menu button on mine. Hope this help, and sorry for the long reply.
I'm not sure this is the right subforum for this, but I was coming here to ask how to do this before I figured it out for myself. So I figured I should post about it in case I forget what I did.
I just switched to a shiny new G2, and I'm using the one-button earphones that came with my Nexus S 4G. This is actually the third set of such headphones (I keep breaking and replacing them), so I refuse to have them not work on my rooted but otherwise stock G2.
When I first plugged them in to the G2, it was configured so that the button would control the phone function: one press would open my call history, a double press would redial, and a hold would start up voice dialer. On the Nexus S 4G, the buttons controlled my media player, so that's what I want them to do here.
I tried various button remapping tools like the JAYS Headset Control app, but none of them would take precedence over the default LG actions.
Instead, I modified this approach from the Nexus 4, and changed the key code for the button from the one that the voice dialer controls were intercepting (HEADSETHOOK) to something else (MEDIA_NEXT).
What I did:
1. Have root and install Busybox (for vi).
2. Get a root shell on the device.
Code:
$ adb shell
[email protected]:/ $ su
[email protected]:/ #
3. Mount /system as read-write:
Code:
[email protected]:/ # mount -o rw,remount /system
4. Edit the default Android keyboard layout to swap the HEADSETHOOK and MEDIA_NEXT keys.
Code:
[email protected]:/ # vi /system/usr/keylayout/Generic.kl
Press "i" to enter insert mode. Move around with the arrow keys.
Change:
Code:
key 163 MEDIA_NEXT
to:
Code:
key 163 HEADSETHOOK
And also change:
Code:
key 226 HEADSETHOOK
to:
Code:
key 226 MEDIA_NEXT
Press Escape, and then press Shift + Z twice to save and quit.
5. Reboot your device for the changes to take effect.
6. Now the button on your single-button headset is the equivalent of the "down" or "next" button on a three-button headset. To configure it, install JAYS Headset Control or a similar application. Chose the three-button headset instead of the one-button headset, and configure the third button to do everything you want your button to do.
7. Enjoy your customizable button!
Sweet! Not having my headset button work for audio was my biggest issue with the G2.
I followed the instructions above, but instead of swapping "key 163 MEDIA_NEXT" I swapped "key 164 MEDIA_PLAY_PAUSE". This caused the default behavior to be "Play/Pause".
I tried using JAYS Headset Control and it works great. Thanks for the find!
Oh my gosh! I've been looking everywhere for this solution. Thank you so much!
My dilemma was that I want to be able to use the headset buttons because I listen to music and switch tracks frequently while walking around the university. Only the Android KitKat ROMs worked for me, but the problem with those ROMs is that GPS has locking problems and/or doesn't work at all.
Thanks for this, it was helpful for me also. Like Myzur I've also used MEDIA_PLAY_PAUSE instead of MEDIA_NEXT.
I had a quick go with the "Headset Button ControllerTrial" app for some extended functionality, but it kept switching from Rhapsody to LG's music app. This was before I saw the comment about configuring things as if it were a 3 button headset, so I'll play around with this some more (and will probably also try the JAYS app). But even as-is, just the ability to play/pause is a very nice improvement over stock behavior (honestly, who uses their phone more for making calls than listening to music.. ).
doesnt work
For some reason this doesnt work with the LG G2 Sprint version, is there any other solution?
pabel101 said:
For some reason this doesnt work with the LG G2 Sprint version, is there any other solution?
Click to expand...
Click to collapse
My phone is LG G2 on Sprint (LS980), and it actually does work for me.
Since my above post, I have actually changed the mapping again to MEDIA_NEXT, and I'm using the Headset Button Controller app (https://play.google.com/store/apps/details?id=com.kober.headsetbutton). The actions in the controller app are all set under "Right button actions" (so exactly according to step 6 in the OP..).
I think any app that will let you configure things for a 3rd/right button should work. The JAYS one is free, but as I recall it asked for a permission I wasn't comfortable with, and I ended up with Kober's app instead, which I think was $2 and to me well worth it (you can barely get a coffee for that these days..). There is a free trial.
This setup works great for music controls (play/pause, next/previous, volume control), but it doesn't seem call control (answer/hangup, mute etc.) is totally working. For me this is mostly about music controls, so I'm not too worried about the call controls and haven't looked into fixing that so far.
By the way, I found out a modified Generic.kl file is enough to cause updates to fail (for ZVC anyway), so you'll want to keep a copy of the original to restore for cases like that.
If you still can't get it to work, what exactly is happening for you, and what app are you using? Did you map MEDIA_NEXT, or MEDIA_PLAY_PAUSE? The Headset Button Controller app I'm using (free trial also) has a troubleshooting feature where it displays the button presses it sees on screen, whether it takes action on it or not, which could be useful to figure things out.
doesnt work
ChoppedLiver said:
My phone is LG G2 on Sprint (LS980), and it actually does work for me.
Since my above post, I have actually changed the mapping again to MEDIA_NEXT, and I'm using the Headset Button Controller app (https://play.google.com/store/apps/details?id=com.kober.headsetbutton). The actions in the controller app are all set under "Right button actions" (so exactly according to step 6 in the OP..).
I think any app that will let you configure things for a 3rd/right button should work. The JAYS one is free, but as I recall it asked for a permission I wasn't comfortable with, and I ended up with Kober's app instead, which I think was $2 and to me well worth it (you can barely get a coffee for that these days..). There is a free trial.
This setup works great for music controls (play/pause, next/previous, volume control), but it doesn't seem call control (answer/hangup, mute etc.) is totally working. For me this is mostly about music controls, so I'm not too worried about the call controls and haven't looked into fixing that so far.
By the way, I found out a modified Generic.kl file is enough to cause updates to fail (for ZVC anyway), so you'll want to keep a copy of the original to restore for cases like that.
If you still can't get it to work, what exactly is happening for you, and what app are you using? Did you map MEDIA_NEXT, or MEDIA_PLAY_PAUSE? The Headset Button Controller app I'm using (free trial also) has a troubleshooting feature where it displays the button presses it sees on screen, whether it takes action on it or not, which could be useful to figure things out.
Click to expand...
Click to collapse
Im sooooo confused by this but is it possible for you to screen shot your settings for Generic.kl? im sorry for the late reply
pabel101 said:
Im sooooo confused by this but is it possible for you to screen shot your settings for Generic.kl? im sorry for the late reply
Click to expand...
Click to collapse
The whole file is over 400 lines long, so a bit too long to fit in a screenshot. There are only 2 lines that you will need to touch however, and they will look like this when you are done with them:
Code:
key 163 HEADSETHOOK
key 226 MEDIA_NEXT
Note that these lines are not next to each other, but they are easy enough to find as they are pretty much ordered by key "number" as you can see.
Sorry if I made things sound confusing.. the steps in the OP are maybe more clear, and exactly what you need to do to get Generic.kl modified the way mine is. Feel free to ask if you need more help/clarification though.
playpause
ChoppedLiver said:
The whole file is over 400 lines long, so a bit too long to fit in a screenshot. There are only 2 lines that you will need to touch however, and they will look like this when you are done with them:
Code:
key 163 HEADSETHOOK
key 226 MEDIA_NEXT
Note that these lines are not next to each other, but they are easy enough to find as they are pretty much ordered by key "number" as you can see.
Sorry if I made things sound confusing.. the steps in the OP are maybe more clear, and exactly what you need to do to get Generic.kl modified the way mine is. Feel free to ask if you need more help/clarification though.
Click to expand...
Click to collapse
ok i did what you said and now my middle button Just skips to next track is that alright?
pabel101 said:
ok i did what you said and now my middle button Just skips to next track is that alright?
Click to expand...
Click to collapse
Yes, this means the re-mapping of the button worked. Now you can use one of the headset control apps to program the button as you please (remember this button is now acting as the "next" or right button, so program as such).
But, you say "middle button" - do you have a 3 button headset? If yes, I think you could have left the mapping alone, and programmed either of the left/right buttons, or both. Not really sure of the best and most functional approach in this case, I've never had anything other than a single button headset. I would think with 3 buttons, if all 3 are supported, you can have some more flexibility.
If you do have a 3 button headset, but only the middle button is supported by Android at all (apparently YMMV depending on the make/model among other things), then ignore everything I just said, keep the mapping as-is, and just program the one working button as you like - still as if it were the right button.
headset
ChoppedLiver said:
Yes, this means the re-mapping of the button worked. Now you can use one of the headset control apps to program the button as you please (remember this button is now acting as the "next" or right button, so program as such).
But, you say "middle button" - do you have a 3 button headset? If yes, I think you could have left the mapping alone, and programmed either of the left/right buttons, or both. Not really sure of the best and most functional approach in this case, I've never had anything other than a single button headset. I would think with 3 buttons, if all 3 are supported, you can have some more flexibility.
If you do have a 3 button headset, but only the middle button is supported by Android at all (apparently YMMV depending on the make/model among other things), then ignore everything I just said, keep the mapping as-is, and just program the one working button as you like - still as if it were the right button.
Click to expand...
Click to collapse
Just to be more specific these are the headphones im using http://www.amazon.com/Samsung-Repla...m-Headset/dp/B007C5S3AU/ref=pd_bxgy_cps_img_y
Help
I really want to do this but I am clueless on what to do. Where do I input this code? The build prop? I don't usually mess with stuff to much but his has been bugging me for a while. Thanks in advance
Ghost_Killer811 said:
I really want to do this but I am clueless on what to do. Where do I input this code? The build prop? I don't usually mess with stuff to much but his has been bugging me for a while. Thanks in advance
Click to expand...
Click to collapse
The file to edit is /system/usr/keylayout/Generic.kl. Of course you need a rooted device to be able to edit it; also you need to mount the system partition read/write (it is mounted read-only during normal operation).
The first post of this thread has the exact instructions on how to do this. Have you tried to follow those steps?
One thing I might add - you will want to keep a copy of the un-edited, original Generic.kl file, because you will typically need to restore it to the original before applying firmware updates. Make a new copy of the original file after every firmware update, since the firmware update sometimes modifies it.
ChoppedLiver said:
The file to edit is /system/usr/keylayout/Generic.kl. Of course you need a rooted device to be able to edit it; also you need to mount the system partition read/write (it is mounted read-only during normal operation).
The first post of this thread has the exact instructions on how to do this. Have you tried to follow those steps?
One thing I might add - you will want to keep a copy of the un-edited, original Generic.kl file, because you will typically need to restore it to the original before applying firmware updates. Make a new copy of the original file after every firmware update, since the firmware update sometimes modifies it.
Click to expand...
Click to collapse
Thanks for the help. I tried reading the instructions, but I got confused. When it says to make a root shell and then gives the code, do I put it somewhere specific in the file or just anywhere.
Hi,
I bought this remote:
http://g03.s.alicdn.com/kf/HTB1clsdIXXXXXXlXVXXq6xXFXXXn/2-4GHz-Fly-Air-Mouse-Wireless-Keyboard.jpg
but I'm having trouble with the "back" key. It's not really acts as back. Instead it acts as right click.
Has anyone been able to fix this problem?
I xposed module would be nice
I did some research and found this:
https://github.com/timduru/platform-frameworks-base/commit/bae953c0063dc1afb9e8c43381f3894329abe115
Think this is exactly what we need to fix this.
Is it possible via xposed module? Maybe any Devs are interested in that one?
Use esc button for back key
ilkerates said:
Use esc button for back key
Click to expand...
Click to collapse
Yes, I'm sure he's already aware of that.
Speaking personally, it would be nice if my back button on my air mouse (the same one as the OP has which, despite being marked as a back button, is effectively seen by Android as a right mouse click) actually worked as a back button. To stop having to turn my air mouse over to access the esc key every time I wanted to go back, given that the QWERTY doesn't work when pointing downwards. I had to remap my Menu button as the back button isn't seen by any key mapping apps.
So yes, a big thumbs up from me too if this can happen in Xposed. I'm rooted and running it already.
Beefheart said:
Yes, I'm sure he's already aware of that.
Speaking personally, it would be nice if my back button on my air mouse (the same one as the OP has which, despite being marked as a back button, is effectively seen by Android as a right mouse click) actually worked as a back button. To stop having to turn my air mouse over to access the esc key every time I wanted to go back, given that the QWERTY doesn't work when pointing downwards. I had to remap my Menu button as the back button isn't seen by any key mapping apps.
So yes, a big thumbs up from me too if this can happen in Xposed. I'm rooted and running it already.
Click to expand...
Click to collapse
Yes this is what I am also trying to do, so if anyone has figured out how to make the right mouse button into the back button that would be amazing!!
Xposed Additions may work for you.
ErAzOr2k said:
I did some research and found this:
https://github.com/timduru/platform-frameworks-base/commit/bae953c0063dc1afb9e8c43381f3894329abe115
Think this is exactly what we need to fix this.
Is it possible via xposed module? Maybe any Devs are interested in that one?
Click to expand...
Click to collapse
what exactly is this? thanks
[email protected] said:
Yes this is what I am also trying to do, so if anyone has figured out how to make the right mouse button into the back button that would be amazing!!
Click to expand...
Click to collapse
It's impossible as far as I'm aware to map the back button on my air mouse to a specific activity. Like I said, I ended up mapping the menu button instead. I've gotten used to it now.
Mogster2K said:
Xposed Additions may work for you.
Click to expand...
Click to collapse
Unfortunately not. In fact, not only did it not work, it caused delay issues in button presses on my NVidia controller. This only stopped when it was deactivated within Xposed.
Only other thing I can think of would be to create a custom profile in /system/usr/keylayout/, however I don't know the details of how to do it.
Sent from my LG-H811 using Tapatalk
nice !
nice !
Any updates with this issue? I was actually coming here to post about a similar problem.
Just picked up my Shield TV and tried using this same remote. The center button (select button; left click button) doesn't function at all. I can scroll up and down, left and right, air mouse cursor works fine. But I can't actually make a selection.
I also find that with either the controller or nvidia remote, I can't navigate in app file structures. So when I side load ES Explorer for instance, I can't get into the center of the screen and navigate the file list, only the top and bottom border menus. Or when I sideloaded ShowBox and other similar apps, I can't navigate the movie lists, only the top or bottom menus.
At this point I'm starting to think I'm either better off taking this thing back and using my old droid tv box. OR flashing this thing to make it act like a droid tablet and lose all the added functionality that the shield uses to set itself apart.
So, I bought this remote from amazon:
https://www.amazon.com/dp/B00UYCLV8Y/ref=cm_sw_r_other_awd_CTeTwbRCVNCP1
Which is pretty awesome so far. Everything works except the back button of course. I've been digging and digging and unfortunately I don't think we can change the behavior as it just doesn't seem to be recognized as a typical key scancode. I'm confident of this because I made a custom key layout file for this device, and literally edited 999 key entries, ranging from "key 0" all the way up to "key 999". I gave every keycode the back button tag. What this essentially did was turn every single button on the remote into a back button (lol), and as you may expect, even STILL the back button on the remote only registered as a mouse click.
After searching, it seems the only way to bypass this would to be to change the behavior of the mouse button itself, which according to resources online, is hard coded into the kernel itself. You would have to actually know how to code and compile a new kernel for your media device.
http://stackoverflow.com/questions/...ped-to-work-for-traversing-back-in-jelly-bean
I have created a simple keylayout that anyone can use if interested. It's pretty much just a rip of the generic.kl file, with the zoom in and out buttons on the remote configured as back buttons. If you use a proper keycode scanner, you can study this keylayout file and eventually customize any button (except the back button of course) to do almost anything you want.
It's a temporary workaround until someone figures it out. If it doesn't work for you, you may need to change the filename to reflect the proper vid and pid of your device. I did this by plugging my device into windows and checking the hardware id for the new mouse and keyboard input that popped up.
I'm not sure which directory the file needs to be in, so I just copied it to both known directories:
Root: data>system>devices>keylayout
Root: system>usr>keylayout
I hope this helps.
Edit: Also, a couple of things to note, in case anyone was curious. If your having any issues trying to program the infrared side for a remote, consider that the source remote may be blasting too much for this remote to learn. I discovered this issue because my Samsung tv would send tons of ir data and causing my remote to have troubles learning. If you have a similar issue, try quickly/lightly tapping the button on the source remote when teaching this remote to learn it. Had no issues teaching my remote once I figured this out.
Finally, an oddity I noticed is that the issue seems specific to Android TV boxes. Connecting the USB to my galaxy note 5 via USB otg cable, the back button works fine on its own on this remote. Oddly though, while it registers as a key using the key test app (Google it), it reports back as having a scancode of 0.
Tried adding key 0 as a button in the keylayout config. Still no go. :/
I've made a custom kernel based on stock kernel to (hopefully) change the rightclick event to back event.
Is anyone brave enough to check this out as I don't give a guarantee to anything?!
ErAzOr2k said:
I've made a custom kernel based on stock kernel to (hopefully) change the rightclick event to back event.
Is anyone brave enough to check this out as I don't give a guarantee to anything?!
Click to expand...
Click to collapse
tried your boot.img, and as far as i can tell, nothing.
my shield tv is already unlocked and rooted, so i just used "fastboot flash boot boot.img" in adb to flash the boot image to my device. booted up fine, just i dont see any changes regarding right mouse click.... :/
has anyone figure this out yet. I really need to change the right click to function as "back"
Has anyone been able to fix this meanwhile? With Xposed Module maybe?
I'd love a Magisk (or Xposed) module that fixes that, but I don't think any module like that exists right now...
There are work-arounds to use apps that create fullscreen overlay which intercepts right clicks and emulates a Back button, but those don't work on Shield (or Android TV in general) because creating Overlay / requesting "draw over other apps" permission causes a crash
For now, the most convenient (more than editing *.kl files) work-around I've found is to use an app called Button Mapper (packagename: flar2.homebutton, can't post a link cause I'm a newbie) and emulate Back button on some other button...