Related
Found this via google groups.
You can unlock your phone via an adb shell command
Code:
adb shell
input keyevent 82
or on one line:
adb shell input keyevent 82
key event 82:
public static final int KEYCODE_MENU
Since: API Level 1
Key code constant: Menu key.
Constant Value: 82 (0x00000052)
Click to expand...
Click to collapse
Background: I flashed a kernel and rebooted and when the phone was fully booted I could not unlock the lock screen!
Had disabled the slider and had the menu key set to unlock (cm7). Unfortunately the kernel must have had a bug or something and all my soft buttons were not working.
Neat! It never occured to me that ADB might support sending key events.
Any updates to this? I locked myself with gesture. LOL
mh do you know what it is for the Desire??
I tryed this, but it doesn't worked. had a simular problem. I worked on the lockscreen and than i removed the ring, and i could push it XD
Thanks a lot man for sharing this.
Working awesome with Nexus 5.
Thank you!!!
Thank you for good information . :good::good::good::good:
Doesn't work with Samsung S6
Hi, it doesn't work with Samsung S6. Any generic solution for all the mobile devices ?
Hey
If your rom has a problem with the rom lagging on pressing both volume keys, it is likely to be this problem.
The symptoms are that on presing both volume keys together, the phone slows to a crawl and after a certain amount of time, it vibrates a couple of times and comes right again.
To confirm, check sdcard, there will be a folder called bugreport with bugreports generated every time that key combo is pressed.
It is described in this thread:
http://forum.xda-developers.com/showthread.php?t=1566742
Fix is to open boot.img and change this line in init.huawei.rc:
Original:
# bugreport is triggered by the KEY_VOLUMEUP and KEY_VOLUMEDOWN keycodes or triggered by projectmenu
service bugreport /system/bin/dumpstate -d -v -o /sdcard/bugreports/bugreport
user root
disabled
oneshot
keycodes 115 114
Modded:
# bugreport is triggered by projectmenu
service bugreport /system/bin/dumpstate -d -v -o /sdcard/bugreports/bugreport
user root
disabled
oneshot
It occurs because huawei probably include it for testing and run as root, but it does not work on a standard rom which has no root access. When we root, it comes back. Just deleting the keycode line allows the bugreports to be generated if necessary, but just not by the volume keys.
Sbasils miui r5g currently has this problem according to the thread listed. Here is the fixed boot.img for testing:
http://www.mediafire.com/?zyv5cqe5yema7xi
Paul
Thank You, Paul. It works likes it is supposed to.
This thing is driving me nuts, especially because on my Xperia Play you don't even have to press both buttons, you just press volume up and be unlucky (sometimes this happens, sometimes it doesn't).
It's actually supposed to be triggered by volume up and right trigger (keycodes 115 311), and it is (it always happens if you do that), but sometimes just pressing volume up is enough and I have never noticed the right trigger getting stuck.
Anyway, on this phone the file is init.semc.rc, but I don't know how to get to boot.img. Where is it? Is it even on the phone? As far as I know boot.img is used for flashing custom ROMs, but I'm using the stock one. Can I do anything to fix this on a locked bootloader?
For now I've renamed /system/bin/dumpstate. I hope it isn't used for anything else.
Thanks Paul. Can we use this any ROM?
if the rom has this particular problem as described, then the boot.img just needs to be edited with this one line change and the problem will be fixed. Then you just need a way to apply the boot.img. In our phone this is easy with CWM or a root capable file browser, sorry, I can't speak for any other phones. This has been a problem on both Huawei phones I have had so far!
Also to the guy with the experia play, I'm sorry mate, this may give a guide to fixing the problem, but you will need root and some experience with linux based tools at a minimum to fix it. If it is a stock rom, there may be a different problem.
Can somebody give me an overview of the nook filesystem? There are some files I would like to change but I'm not sure what to change it to.
NMGxda said:
Can somebody give me an overview of the nook filesystem? There are some files I would like to change but I'm not sure what to change it to.
Click to expand...
Click to collapse
Your question is way too general to be answered. The Nook Color has an Android file system, dependent on whether it's stock or the various versions of Android that can be loaded on it. What files do you want to change? What are you trying to accomplish? Maybe then help and advice.
Sorry about that
I think my file://sys/power files may be messed up because it always says "Not Charging" in the quick settings when plugged in. It could also be because I used the wrong cord once. It could also be both. Could you maybe give me the default values in the files (if you have a Nook)? You can use the OpenExplorer app and open the files with a browser.
NMGxda said:
I think my file://sys/power files may be messed up because it always says "Not Charging" in the quick settings when plugged in. It could also be because I used the wrong cord once. It could also be both. Could you maybe give me the default values in the files (if you have a Nook)? You can use the OpenExplorer app and open the files with a browser.
Click to expand...
Click to collapse
What ROM are you using? Stock, rooted, CM7, CM9? I'll upload the file once I know.
OK
It's running stock v1.4.3
I had trouble copying my files values last post so I backspaced them all. I'm going to try again.
Filename/data
file:///sys/power/sr_vdd2_autocomp
1
file:///sys/power/sr_vdd1_autocomp
1
file:///sys/power/sr_steps
37500
file:///sys/power/sr_steps_1g
62500
file:///sys/power/sr_vnom_steps
50000
file:///sys/power/sr_adjust_vsel
oppid: [nominal v] [dynamic Vnom] [calib v] [calib step v] mpu 1: 0x20 0x1b 0x14 0x17 mpu 2: 0x2d 0x26 0x1f 0x22 mpu 3: 0x38 0x2f 0x28 0x2b l3 1: 0x1e 0x18 0x18 0x18 l3 2: 0x2d 0x20 0x20 0x20
file:///sys/power/vdd2_lock
0
file:///sys/power/vdd1_lock
0
file:///sys/power/vdd2_opp
2
file:///sys/power/vdd1_opp
2
file:///sys/power/dsp_freq
520000000
file:///sys/power/tick
I get this error
Web page not available
The Web page at file:///sys/power/tick could not be loaded as: Invalid argument
file:///sys/power/fb_state
awake
file:///sys/power/wait_for_fb_wake
awake
file:///sys/power/wait_for_fb_sleep
It would not load.
file:///sys/power/wake_unlock
It would not load.
file:///sys/power/wake_lock
It would not load.
file:///sys/power/pm_test
It would not load.
file:///sys/power/state
It would not load.
Mine always says "not charging" when plugged into my computer.
turdferguson92 said:
Mine always says "not charging" when plugged into my computer.
Click to expand...
Click to collapse
It happens when I plug it into the wall.
NMGxda said:
It's running stock v1.4.3
I had trouble copying my files values last post so I backspaced them all. I'm going to try again.
--SNIP--
Click to expand...
Click to collapse
Based on the number of files, the fact that it's not rooted, and other things, I think your best option is to go the 8 boot route and reinstall the software.
Is there a way to disable touch to wake on my LG G Watch R?
I like to cross my arms and when wearing a t-shirt it constantly wakes the screen.
I want to avoid Theatre Mode as I want to be able to glance at the screen and see the time.
Any suggestion will be greatly appreciated.
Thanks in advance
mark3180 said:
Is there a way to disable touch to wake on my LG G Watch R?
I like to cross my arms and when wearing a t-shirt it constantly wakes the screen.
I want to avoid Theatre Mode as I want to be able to glance at the screen and see the time.
Any suggestion will be greatly appreciated.
Thanks in advance
Click to expand...
Click to collapse
+1 intrested to this. I have a lg g watch r.
In Cinema Mode i have Touch2Wake disabled but watch dont show anything and does not vibrate. It becomes really useless if it does not vibrate In Cinema Mode.
mark3180 said:
Is there a way to disable touch to wake on my LG G Watch R?
I like to cross my arms and when wearing a t-shirt it constantly wakes the screen.
I want to avoid Theatre Mode as I want to be able to glance at the screen and see the time.
Any suggestion will be greatly appreciated.
Thanks in advance
Click to expand...
Click to collapse
I am also searching for this:good:
I've been looking everywhere for a solution to this. I hasn't even considered it as an issue, but just a couple of days is enough to make me realise this is a requirement. I can't believe it didn't come up in development! Aside from your own accidental touches, there's also the issue of inquisitive fingers from children touching that nice shiny screen... Tapping the side button to wake the screen would be perfect (whilst retaining the monochrome screen and notifications).
Cinema mode is really dumb. Just very poorly thought out. There has got to be a way to disable touch to wake. Or even enable vibrating notifications in cinema mode.
Yes there is a way
First you have to install twrp on your watch. Because you need the acces to some files. When you have installed, start in recovery mode, and go to mount and press system. Connect your watch to your computer and open adb,
adb root
adb push /system/usr/idc/sec_touchscreen.idc <choose where you want to have the file in your pc>
Click to expand...
Click to collapse
Make a copy of the file, and open it with notepad++ or other file editor. YOU will se a think like this
# Copyright 2014 The Android Open Source Project
#
# Licensed under the Apache License, Version 2.0 (the "License");
# you may not use this file except in compliance with the License.
# You may obtain a copy of the License at
#
# http://www.apache.org/licenses/LICENSE-2.0
#
# Unless required by applicable law or agreed to in writing, software
# distributed under the License is distributed on an "AS IS" BASIS,
# WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
# See the License for the specific language governing permissions and
# limitations under the License.
#
# Input Device Calibration File for the Dory touch screen.
#
device.internal = 1
touch.deviceType = touchScreen
touch.orientationAware = 1
touch.wake = 1
Click to expand...
Click to collapse
So remove the part of ( touch.wake = 1 ) and save (make first a copy of the file), Go to adb
adb pull <where you have the file> /system/usr/idc/
Click to expand...
Click to collapse
Restat the watch and you will se that the screen is not goin to turn off, pressing the button of your watch. Restart other time the watch and go to recovery.
With the copy of the file, mount other time system on twrp and go to adb
adb pull <where you have the copy> /system/usr/idc/
Click to expand...
Click to collapse
Restart the watch other time. This work for my, but i am using an alpha for gear 2 neo with android, so probably this might be a bug.
dataonlycod said:
First you have to install twrp on your watch. Because you need the acces to some files. When you have installed, start in recovery mode, and go to mount and press system. Connect your watch to your computer and open adb,
Make a copy of the file, and open it with notepad++ or other file editor. YOU will se a think like this
So remove the part of ( touch.wake = 1 ) and save (make first a copy of the file), Go to adb
Restat the watch and you will se that the screen is not goin to turn off, pressing the button of your watch. Restart other time the watch and go to recovery.
With the copy of the file, mount other time system on twrp and go to adb
Restart the watch other time. This work for my, but i am using an alpha for gear 2 neo with android, so probably this might be a bug.
Click to expand...
Click to collapse
After you restart the second time you can use the button to wake and not the touch screen?? I will try this then thank you.
-RioT- said:
After you restart the second time you can use the button to wake and not the touch screen?? I will try this then thank you.
Click to expand...
Click to collapse
Yep you can use it to wake up the device. But as I say, make a backup because this happen with my alpha of the gear 2 neo, so probably this is not going to work with other devices. Just in case xD
Works for me on LG G Watch R
The file name is different "synaptics_rmi4_i2c.idc"
Same edit, copied to sdcard and moved in recovery to /system/usr/idc/ as mentioned above.
I have swipe menu still available and I can swipe down for the quick toggles.
Button is used to wake (and I use screen always on)
Going to be interesting how this performs in the shower and in general. Thanks to the suggestion posted.
Any update on this after using it for a while? Looking to apply this to my LG G watch R running the Urbane port.
Ok well i tried it any ways and i still have the problem when my arms are crossed my arm starts doing things on my watch...
Starting from version 1.6 this app supports wake on touch changing - https://play.google.com/store/apps/details?id=com.sssemil.advancedsettings (here is apk - View attachment AdvancedSettings-v1.6-11.apk)
I downloaded the advanced settings app tried the disable touch wake... it doesn't wake but you can still scroll notifications and long press to change the face.
Any chance of completely turning off the touch screen while in sleep...
..
castructuraleng said:
I tried the Advanced Settings app on my LG Watch Urbane 2nd Edition with Android 6.0.1, which is not rooted. It has an option for "Touch to wake screen" that I tried to set to "off"; however, when I go back to look at it, it is always set to "on". Do I need to root to have this stay, or is the app just not compatible with 6.0.1?
Update... just answered my own question. It appears you need to be rooted to do this.
Click to expand...
Click to collapse
Yep, it works on Marshmallow 6.0.1 when Rooted. Just tested it on my Huawei Watch.
..
I installed "Showear". You can set a simple touch pattern to unlock the watch. Crossing your arms will no longer trigger any action on your watch (except making the screen on).
..
..
Hi m8. I've done this on my LG urbane and works just fine ty a lot... but i modified a little your steps...
1) My lg urbane is rooted
2) I went to the ADB folder in my PC (using windows explorer) then using shift+right click i select "open command window here"
3) in this command window i did:
adb reboot bootloader
fastboot flash recovery (starts twrp)
in the TWRP:
Go to "Mount"
tick the "system" box
In the command window :
adb pull /system/usr/idc/synaptics_rmi4_i2c.idc (Dont need to select the folder, will appear in the ADB folder used to open the command window)***
*** When i tried to write the destination folder have not worked so i strongly advise not to fill this part, the command in the beginning is PULL not PUSH to take from the device and the file to be taken from the device had a different name as someone have stated before ***
4) In the notepad i did
I opened the file with the notepad and edit "touch.wake = 1" to "touch.wake = 0" (I did not delete this part just change the value)
5) in the command window:
adb pull <where you have the file> /system/usr/idc/
6) Reset my phone and works great!
Hi everyone,
I looked so much for a way to do this, and rooted my tab and installed Prism™ Barebone V3.5 ROM just so I find a way to disable waking the tab with the home button. The way I found most used on the internet is to modify the key layout file "generic.kl" in "/system/usr/keylayout/". I also tried modifying "gpio-keys.kl" but to no avail. I removed the WAKE keyword next to the HOME key, didn't make any change.
I have no idea how to do this, although it seems simple to remap a hardware key for everyone, what am I doing wrong?! :/ Or is there a trick samsung has done with their tabs to prevent custom remapping of keys?
Thank you in advance
ILIA_93 said:
Hi everyone,
I looked so much for a way to do this, and rooted my tab and installed Prism™ Barebone V3.5 ROM just so I find a way to disable waking the tab with the home button. The way I found most used on the internet is to modify the key layout file "generic.kl" in "/system/usr/keylayout/". I also tried modifying "gpio-keys.kl" but to no avail. I removed the WAKE keyword next to the HOME key, didn't make any change.
I have no idea how to do this, although it seems simple to remap a hardware key for everyone, what am I doing wrong?! :/ Or is there a trick samsung has done with their tabs to prevent custom remapping of keys?
Thank you in advance
Click to expand...
Click to collapse
I got this from this thread (they deserve the credit), I've been using their tricks on my Tab 4 for a while. You need to do a tiny smali edit to android.policy.jar. Decompile it with apktool 2.0, open smali/com/android/interal/policy/impl/PhoneWindowManager.smali and find the method called .method private isWakeKeyWhenScreenOff(I)Z and add the lines in blue:
Code:
:sswitch_1
move v0, v1
goto :goto_0
[COLOR="Blue"]:sswitch_4
return v1
nop[/COLOR]
:sswitch_data_0
.sparse-switch
[COLOR="blue"]0x3 -> :sswitch_4[/COLOR]
0x18 -> :sswitch_0
0x19 -> :sswitch_0
thisisapoorusernamechoice said:
I got this from this thread (they deserve the credit), I've been using their tricks on my Tab 4 for a while.
Click to expand...
Click to collapse
Thank you so much!!! REALLY THANK YOU!!!! :victory: