On my z1 compact the powerkey is broken it is always pushed i've mapped the focus key as a power but the phone still have a input and it became hot because there is input boost on 2 core (1 and 4) at 1190 mhz
it is possible or disable input from key or disable this touchboost?
i've stock rom with root and looked bootloader
darix96 said:
On my z1 compact the powerkey is broken it is always pushed i've mapped the focus key as a power but the phone still have a input and it became hot because there is input boost on 2 core (1 and 4) at 1190 mhz
it is possible or disable input from key or disable this touchboost?
i've stock rom with root and looked bootloader
Click to expand...
Click to collapse
I'm not an expert on this stuff, but just wondering if you already tried kernel apps, (Kernel Adiutor, etc.). Besides that, I would say it sounds like a smali issue, maybe @venkat kamesh or @munjeni can help...
darix96 said:
On my z1 compact the powerkey is broken it is always pushed i've mapped the focus key as a power but the phone still have a input and it became hot because there is input boost on 2 core (1 and 4) at 1190 mhz
it is possible or disable input from key or disable this touchboost?
i've stock rom with root and looked bootloader
Click to expand...
Click to collapse
Maybe you can edit set_governor.sh,and change value to lower freq
Thanks!!! i'll try it! but i discovered another problem with this input always active, principally with chrome and youtube, in chrome the scroll semms stucked after i remove finger from the screen and in youtube the timebar is always present (sorry for my bad english)
Related
After I made my version of the GB keyboard do paging with volume +/-, I thought a little about what else one might want. I know some people here really like to have apps in fullscreen mode, without the soft buttons, but then there is the problem of how to get out of such apps (unless the developer thoughtfully provided an exit option). Well, one could modify the GB keyboard app to map something to HOME. Here are three options that come to mind:
- Volume down press. (But then you can't adjust volume.)
- Long volume down hold. (But then your volume gets unnecessarily adjusted.)
- Half-long power hold. (Assuming I can map power keys. I haven't tried.) The down side is that if you want to pop up the long power hold menu, you will be sent home before it shows up. Still, that's perhaps not so bad if you only enable this feature for selected apps.
And here's another option, which could even work together with other keyboards:
- Power button double tap.
You press the power button twice within a short interval (say, 1/2 second) and the current app is exited. Of course, this won't look so good: the screen will turn off and turn back on. But it should be pretty easy to implement.
Any other thoughts?
Hi,
you could simply press the power-button long until the menu pops up and then switch to button-mode which provides a home-button
Instead of getting rid of the softkeys completely, I just make them smaller (24px) using Buttons for RW Rooted Archos.
I you have a rooted device, you can use the button savior app which is available on the market. You can locate this button wherever you want.
ma-shell said:
Hi,
you could simply press the power-button long until the menu pops up and then switch to button-mode which provides a home-button
Click to expand...
Click to collapse
I think not. When you an application is forced into fullscreen mode by setting the FULLSCREEN.FULL option in the manifest, the button mode option isn't in the menu--or so I recall.
bach0405 said:
I you have a rooted device, you can use the button savior app which is available on the market. You can locate this button wherever you want.
Click to expand...
Click to collapse
Question: Has anybody benchmarked the device with and without button savior to see what it does to graphics performance?
arpruss said:
Question: Has anybody benchmarked the device with and without button savior to see what it does to graphics performance?
Click to expand...
Click to collapse
OK, now I did.
AnTuTu 2D without Button Savior: 295
AnTuTu 3D without Button Savior: 674
AnTuTu 2D with Button Savior: 289
AnTuTu 3D with Button Savior: 666
So, surprisingly little difference.
arpruss said:
I think not. When you an application is forced into fullscreen mode by setting the FULLSCREEN.FULL option in the manifest, the button mode option isn't in the menu--or so I recall.
Click to expand...
Click to collapse
Oh, what about e.g. the default clock-app or the gallery-app by archos? They don't have those Buttons but you can get them over the menu. Is this somehow "another kind of fullscreen"?
ma-shell said:
Oh, what about e.g. the default clock-app or the gallery-app by archos? They don't have those Buttons but you can get them over the menu. Is this somehow "another kind of fullscreen"?
Click to expand...
Click to collapse
I am thinking of apps forced into fullscreen mode either by modifying their manifest.xml file, or by editing the device's packages.xml. These are apps not designed to be used in fullscreen mode, but which can benefit from a fullscreen mode.
I'm on Madmack's 11/26/13, CM11 build and I'm trying to remap the extra quick launch button we have above the volume rocker on CM11 - basically I want it as my camera button.
I've been able to do this on other phones by manual editing the proper keyboard layout file.
The hardware keyboard layout file for the LGOP on CM11 appears to be: /system/user/gk-keypad-8064.kl
The quick launch button is Key 250 and by default its set to ASSIST (which launches the Search function oddly enough).
Normally just changing ASSIST to CAMERA and rebooting is sufficient to launch the CAMERA functions - doesn't work with my LGOP on CM11. However, once changing Key 250 to CAMERA, it does take pictures if you manually launch the camera app.
Switching it to Key 250 CAMERA WAKE oddly enough makes the quicklaunch button function exactly the same as when you press down on the screen for 2+ seconds and the home screens shrink to the center and Wallpapers/Widgets/Settings pop up.
I can tell you that changing Key 250 to POWER, VOLUME_UP, VOLUME_DOWN, HOME all work... just can't get the CAMERA function to work.
Any thoughts or ideas? Any help would be appreciated.
I have no idea but this is would be great. I hope someone can chime in to help you out.
Sent from my LG-E980 using xda app-developers app
hey, decompressed an old nandroid of the stock rom...
i'm pretty sure i had the quicklaunch button set to the default "press to launch camera/press again to snap a pic" action, and my gk-keypad-8064.kl had key 250 set to QUICK_CLIP
Can we set it to a particular app? particularly to display recent apps?
Isn't there a "buttons" section in the phone settings? I used that to switch search function to camera and tested, it works great. Only downside is its not a 2-step shutter button lol.
Hi have you tryed changing it to camera wake_dropped? ive remapped another LG phone and that was the code i used. ill try it now aswell
BraveDemon said:
I'm on Madmack's 11/26/13, CM11 build and I'm trying to remap the extra quick launch button we have above the volume rocker on CM11 - basically I want it as my camera button.
I've been able to do this on other phones by manual editing the proper keyboard layout file.
The hardware keyboard layout file for the LGOP on CM11 appears to be: /system/user/gk-keypad-8064.kl
The quick launch button is Key 250 and by default its set to ASSIST (which launches the Search function oddly enough).
Normally just changing ASSIST to CAMERA and rebooting is sufficient to launch the CAMERA functions - doesn't work with my LGOP on CM11. However, once changing Key 250 to CAMERA, it does take pictures if you manually launch the camera app.
Switching it to Key 250 CAMERA WAKE oddly enough makes the quicklaunch button function exactly the same as when you press down on the screen for 2+ seconds and the home screens shrink to the center and Wallpapers/Widgets/Settings pop up.
I can tell you that changing Key 250 to POWER, VOLUME_UP, VOLUME_DOWN, HOME all work... just can't get the CAMERA function to work.
Any thoughts or ideas? Any help would be appreciated.
Click to expand...
Click to collapse
A similar question
In looking through the forums, this thread seemed to be the closest to users having a similar situation to myself. I have an LGOP running the latest nightly of CM11 and I would also like to map the quick search button to a different function. While there are buttons options to set it to launch the camera app, it launches the default camera app and I would like it to launch the latest version of Google's camera app. Does anyone know how to do this?
Gravity box I think can pull it off
2SHAYNEZ
WEll I was searching for something similar, to remap our Quick button and assign anything to it! and I have found an xposed module which can do the job here you go: https://play.google.com/store/apps/details?id=com.spazedog.xposed.additionsgb
Hi
I previosuly had an Xperia S, and there was an easy mod to wake up the device using the camera button. I have been trying the same thing to work on my Z1 compact but so far I have only been able to break the button.
I did this:
With root exploring app, went to /system/usr/keylayout and opened file gpio-keys.kl
This has only four useful lines:
key 115 VOLUME_UP
key 114 VOLUME_DOWN
key 528 FOCUS
key 766 CAMERA
I modified to this:
key 528 FOCUS WAKE_DROPPED
Howevera after saving and rebooting, camera button becomes unresponsive (not even full press works). Any suggestions?
Thanks
If I remember correctly, there's an xposed module that let's you rebind hardware keys.
Sent from my D5503 using Tapatalk
Have solved my remapping problem below with the xposed module "XPOSED-EDGEPRO":
https://forum.xda-developers.com/xposed/modules/xposed-edgepro-v2-0-release-t3525566
easy going, works like a charm
---------------------------------------------------------------------------------------------------------------------------------------
The Power Button of my Z1 Compact is working very unreleiable since I dropped the device 2 weeks ago
So I wanted to remap the Power to the Camera Button. Therefore i have tried the Xposed Additions Module.
Unfortunately it seems that the Module isn't working on my phone. All remapping tryouts with the Xposed Additions module did not work.
So I wanted also to remap Buttons via "/system/usr/keylayout and opened file gpio-keys.kl"
Can anyone help me with information on how this file needs to be adjusted for switching these Buttons?
Thanks a lot in Advance!
Hi, I found you can activate softkeys on any stock rom by modify the build.prop value below
- Need root and use BuildProp Editor to edit
- Searh for words: qemu.hw.mainkeys=1 and change 1 to 0 it activates the softkeys.
- Save the changed and Reboot, your hardware key will still working as well
- The softkeys function is same to the hardware keys you can long press for screenshot, turn on camera etc
I don't know how to turn off the hardware key yet, if anyone know you can share it.
You can disable the hardware button in Settings/Accessibility/Virtual Button Control.
Just thought I'd add a little tidbit to this topic that I found after a dropped my LePro3 and lost home and back hardware key function. With the app Handy Soft Keys I now have (as the name suggests) really handy software keys. https://play.google.com/store/apps/details?id=ca.yesoft.handysoftkeys&hl=sv (There's an ad-free pro version available as well). No root required. I don't think it has the full functionality of the hardware buttons with long press, but I just needed the basic ones and if that's what someone else needs as well, well, it's there.
And by the way, if you don't want to go through settings etc hardware keys can be turned on/off easily by pressing power and volume up at at the same time.
Hi there. I love this phone but no matter what i use hardware key or software one i just hate those lights at the bottom of the phone.
I just like the mia1 as a blackbox so i made a simple magisk module to disable them with a simple echo cmd.
I made this for my personal use but before i searched on web if there was any other solution, and nothing was made recently.
The module is tested on a stock mia1.
It will work on other phones or mia1 rom if the kernel have the same path to the file i use. Testing won't bite as if it doesn't work nothing will break.
Many thanks to this thread and guys out there
https://forum.xda-developers.com/mi-a1/themes/root-navigation-light-control-t3712686
Nice! It worked for my Mi A1 with Pixel Experience 10, thank you so much!
Only turned off the light, how to disable the function as well?
afrizal87 said:
Only turned off the light, how to disable the function as well?
Click to expand...
Click to collapse
Using the gesture mode from android 9 will desactivate the button function.
Did you mean two buttons? I do activated that, but still working both physically and navbar aswell
afrizal87 said:
Did you mean two buttons? I do activated that, but still working both physically and navbar aswell
Click to expand...
Click to collapse
If you're on stock rom enabling the navbar will desactivate the button function but not the led light.
Did a modify from another module that disable capacitive navigation buttons completely and the backlight and enabling navigation bar (build prop edit) for stock. Because when I pick the phone and accidentally tap on recent button, the screen turns on.
File in attachments. (That can be counted as update of this module)
EDIT: installing any other magisk modules that include init.d (like Cloudflare Magisk module) will enable the button lights. (but still the buttons will be disabled)
Thanks for this, it works on my Le Max 2 . ?
Dısable charcing led mod please! Thanx you
Working in stock ROM android 9