Hey, guys. Quick question.
Is there any way AT ALL that reverse portrait and reverse landscape could be achieved on the NST?
Let me know. Thanks,
ThirdNookie
Android 2.1 only supported two orientations.
Heck, B&N only really supported one!
I've looked at this. You'd need some system patches to get that working.
Right now, my system has so many patches on it already.
You could also arrange this on a per-application basis.
I've thought about throwing it on my reader app.
The question of buttons makes it a sticky question.
The original orientation key remapping remaps all the arrow keycodes.
We'd want to remap the scancodes, but only on the hard keys and not external keyboards.
Renate NST said:
Android 2.1 only supported two orientations.
Heck, B&N only really supported one!
I've looked at this. You'd need some system patches to get that working.
Right now, my system has so many patches on it already.
You could also arrange this on a per-application basis.
I've thought about throwing it on my reader app.
The question of buttons makes it a sticky question.
The original orientation key remapping remaps all the arrow keycodes.
We'd want to remap the scancodes, but only on the hard keys and not external keyboards.
Click to expand...
Click to collapse
Well, first thing would be getting the screen itself to rotate properly. Then we can worry about key remappings.
I'm here, but I'm not on my regular development system right now.
I'll take a peek at the rotation stuff when I am.
Related
is there a way to have the Keyboard Light come on when the device is opened?
I find it aggrevating that I must press a key first!
I second that
I third it.
I fourth it....
yeah thats pretty god damn true actualyl when your in cinema and trying to txt when u open it you have to press two buttons, (a letter to lite it up) then another to delete that letter before u can start to reply, gay !
who is the one!
does anyone have ideas heres a thought
it should be triggered with the screen rotation
Haha, this is one of the most annoying things about the wizard.
I hate that "feature" and I also hate that the backlight goes out after a second or two on the keyboard if you don't push a key.
Lol, I second that one too!
I'm sure it would be possible to make an application that simulated keypresses on the slide out keyboard, but only whilst it was open (could be detected by looking is the screen was in landscape mode or portrait mode)
Should be simple enough to make, but i've not learnt enough at university yet to tackle such a problem, maybe next summer
it should not be triggered by app simulating keypress with screen rotation or upon opening it should be executed in same manner as screen rotation.
brins0: have you tried simulating a keypress by using the onscreen keyboard? Doesn't work.
The keyboard backlight is not stimulated by non hardware keypresses (at least on the Hermes)
V
jeffbar1 said:
it should not be triggered by app simulating keypress with screen rotation or upon opening it should be executed in same manner as screen rotation.
Click to expand...
Click to collapse
Actually, looking into it further, there arn't actually any keys you could "press" that wouldn't result in an action on-screen. You may be able to trick the hardware into thinking you pressed a key (by possibly creating a virtual hardware key (if that is even possible)), which would make the keys light up.
Are the keyboard lights controlled by the hardware itself, or does Windows have some mention in the lighting status?
The keyboard backlight timer is all hardware controlled.
This means there is no way to change it's crappy 5 second time out, and no way to control it from within software.
Yes, it sucks. That is one of my few complaints about this device. The backlight on the keyboard DEFINATELY needs to be configurable.
vijay555 said:
brins0: have you tried simulating a keypress by using the onscreen keyboard? Doesn't work.
The keyboard backlight is not stimulated by non hardware keypresses (at least on the Hermes)
V
Click to expand...
Click to collapse
I understand what you mean, but I think you mis-understand what i'm suggesting. The drivers for the keyboard should have something similar to a key status. If you make the status for a peticular key "pressed" or whatever, it's effectively fooling the driver into thinking the key has been pressed, hence the keys would illuminate. (I don't fully understand how the hardware works, not being an expert in this feild, and considering each new model differs (sometimes quite heavilly))
GldRush98 said:
The keyboard backlight timer is all hardware controlled.
This means there is no way to change it's crappy 5 second time out, and no way to control it from within software.
Yes, it sucks. That is one of my few complaints about this device. The backlight on the keyboard DEFINATELY needs to be configurable.
Click to expand...
Click to collapse
Yeah, I gathered this was the case...
I wonder if a physical modification of the hardware would allow it to be changed... Any volunteers
Elsewise, it is impossible...
brins0 said:
Yeah, I gathered this was the case...
I wonder if a physical modification of the hardware would allow it to be changed... Any volunteers
Elsewise, it is impossible...
Click to expand...
Click to collapse
Any electrical diagrams of the keyboards interface? lol
Why not just have it trigger upon landscape activation?
I too would like to see the keyboard light come on when landscape is activated, and stay on until landscape is de-activated
h00ligan said:
Why not just have it trigger upon landscape activation?
Click to expand...
Click to collapse
This is what we are suggesting, but this is not possible as the keyboard lights are controlled by the hardware, not by windows, so we can't really trigger them in such a way.
Unless you are willing to physically modify your hardware, it is NOT possible to make the keyboard lights activate upon sliding the keyboard open, and most likely never will be with this device, and most likely others too...
Hmm.
I know it's a stretch, but hit the delete key?
Or hit a menu key twice.
The right-click function mentioned in the topic would be an amazing feature to have in any android build. Being able to hold down on the screen for a second to bring up the menu is invaluable. Not to mention the amount of stress it would save on the Windows button..
Now this is only a request for the development of an idea I had for the current android builds. I do not expect anything to be done about it, only taken into consideration. If the work involved is too heavy and difficult to manage, then it doesn't have to be done. There are already MIUI builds that somewhat incorporate this idea.
whats wrong with pressing the windows button?
Some people have it in theur minds that pressing the keys too much will break them. Don't see why, if that happens you can't just buy a new set of keys from eBay to replace them...
Sent from my HTC HD2 using Tapatalk
Personally, I'd like to see someone develop a way of using the hardware keys to control the touchscreen. I'm really worried that, because of Android, I'm using my touchscreen more than it was designed for and I'm going to break it.
lol, yeah these people who break the hardware keys are obviously pressing them to hard or something. My HD2 is second hand, ive used it very often with the keys and they still work fine.
The keys are there to be pressed, its as simple as that.
have you seen software key panel app;http://forum.xda-developers.com/showthread.php?t=865525
it brings in the screen 4 software button that emulate the hardware button
no need to press anymore the hardware button
if you search in the thread you will find some very good skins for this great app
Stom said:
Personally, I'd like to see someone develop a way of using the hardware keys to control the touchscreen. I'm really worried that, because of Android, I'm using my touchscreen more than it was designed for and I'm going to break it.
Click to expand...
Click to collapse
it is easier to break hardware buttons by too many times pressing them instead of break touchscreen from pressing
many people like me have broke their buttons because of the need that android have of them
clio94 said:
have you seen software key panel app;http://forum.xda-developers.com/showthread.php?t=865525
it brings in the screen 4 software button that emulate the hardware button
no need to press anymore the hardware button
if you search in the thread you will find some very good skins for this great app
it is easier to break hardware buttons by too many times pressing them instead of break touchscreen from pressing
many people like me have broke their buttons because of the need that android have of them
Click to expand...
Click to collapse
I think that was dripping sarcasm from his part.
maff1989 said:
The right-click function mentioned in the topic would be an amazing feature to have in any android build. Being able to hold down on the screen for a second to bring up the menu is invaluable. Not to mention the amount of stress it would save on the Windows button..
Now this is only a request for the development of an idea I had for the current android builds. I do not expect anything to be done about it, only taken into consideration. If the work involved is too heavy and difficult to manage, then it doesn't have to be done. There are already MIUI builds that somewhat incorporate this idea.
Click to expand...
Click to collapse
Android already uses long-click in a lot of situations, I'm not sure how your idea would be able to co-exist with that.
StephanV said:
Android already uses long-click in a lot of situations, I'm not sure how your idea would be able to co-exist with that.
Click to expand...
Click to collapse
That's true. Although, my idea was to ADD a long-click/right-click function to, say, the Browser app. Instead of long-clicking a link, picture, etc, you could long-click the page and bring up the options menu for the Browser app, not necessarily just links, pictures, etc.
maff1989 said:
my idea was to ADD a long-click/right-click function to, say, the Browser app. Instead of long-clicking a link, picture, etc, you could long-click the page and bring up the options menu for the Browser app, not necessarily just links, pictures, etc.
Click to expand...
Click to collapse
That could not be done on a system-wide basis. Every single app would have to specifiy what part of each screen brings up the "right-click menu" and what should be on that menu.
If they were going to do that, they'd have done it already. And that is what the menu button is for.
No doubt most users are happy using the standard capacitive and home keys to navigate their tablet but there are definitely more ways than one to get around and I thought it would be interesting to share our ideas and preferences that make using this (and other) tablet quick and easy.
I read and edit documents a lot so most of the time I prefer to have the tablet in portrait mode. I find the capacitive keys annoying as they are always get touched unintentionally by myself and especially when handing the tablet to someone else when trying to show them something.
So I decided to disable them by editing the generic.kl file in system/user/keylayout and putting an # before keys 139 & 158 then rebooting.
To the replace those keys I use GMD gesture control with some simple and easy to use gestures.
Pretty difficult to show exactly how well this works but first a screenshot showing the gestures paths and action. Dots are the fingers and lines the path they take.
And a video..... I put this together in a hurry so it looks pretty clunky. Recording video over ADB makes it look pretty slow too.
https://www.youtube.com/watch?v=kKCZ7LjAFBE
Quick Search and Lux are two other apps that I can highly recommend........ Rotation Lock is just a simple tasker task that uses the Ultimate Rotation app/plugin. Swiping rotation lock simply toggles between auto 0, 90, 180, 270 and swiping again locks in the desired orientation.
marxses said:
No doubt most users are happy using the standard capacitive and home keys to navigate their tablet but there are definitely more ways than one to get around and I thought it would be interesting to share our ideas and preferences that make using this (and other) tablet quick and easy.
I read and edit documents a lot so most of the time I prefer to have the tablet in portrait mode. I find the capacitive keys annoying as they are always get touched unintentionally by myself and especially when handing the tablet to someone else when trying to show them something.
So I decided to disable them by editing the generic.kl file in system/user/keylayout and putting an # before keys 139 & 158 then rebooting.
To the replace those keys I use GMD gesture control with some simple and easy to use gestures.
Pretty difficult to show exactly how well this works but first a screenshot showing the gestures paths and action. Dots are the fingers and lines the path they take.
And a video..... I put this together in a hurry so it looks pretty clunky. Recording video over ADB makes it look pretty slow too.
Click to expand...
Click to collapse
Thanks for this! I LOVE GMD - very snappy and hitting the capacitive buttons while reading was driving me nuts.
bdneuman said:
Thanks for this! I LOVE GMD - very snappy and hitting the capacitive buttons while reading was driving me nuts.
Click to expand...
Click to collapse
No probs and yeh GMD is definitely handy.
If anyone is having trouble with the way GMD functions with certain apps or in general tweak some of the advanced and touch consumption settings and you should be able to get it working flawlessly.
marxses said:
No probs and yeh GMD is definitely handy.
If anyone is having trouble with the way GMD functions with certain apps or in general tweak some of the advanced and touch consumption settings and you should be able to get it working flawlessly.
Click to expand...
Click to collapse
Good point - I had to do the screen calibration (super easy) in order to get the swipe from borders to work.
I agree though - I am surprised at how responsive this app is. How have I not been using this!?!
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...
Hello, oh great wise ones of the android modding community. I come to you with some questions and a desire to learn.
I have just recently rooted my pixel 4 and installed crDroid, and have realized that i want to make some changes to the navigation buttons when the keyboard is in landscape mode.
Notice in these two pictures how the back button is either on top or bottom, depending on which way the phone is rotated. How can I switch the order for just one of the orientations?
Also, while we're at it, how would I make it so that the nav buttons only show up on the right-hand or left-hand, no matter which way the device is turned?
In case it is relevant, I will say that I am fairly experienced with rooting and am proficient with Java, Linux, & C++.
Thank you