Related
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!
Hello,
i like the stock night mode of nougat. Is it possible to enable it in android 7.1.1. @Our Xc's?
Greetings Kullino
Hi, this has been discussed already in another thread.
Thanks.
@MOD, please delete tread.
Thanks, than my treadcan be deleted
Enabling Night Mode on Android Nougat
source: //michaelevans.org/blog/2016/08/23/enabling-night-mode-on-android-nougat
command: adb -d shell am start --ez show_night_mode true com. android.systemui/. tuner. TunerActivity
i have used this command to invoke but its failed stating that some extra parameters missing for activity...
the developer also stated with correct extras it should work but he has not revealed parameters for the activity..
OK, I don't think this thread will get any attention, but I want to document it anyway. All this should work on other devices with qcom WiFi drivers.
TL;DR:
Grab iwpriv binary somewhere (i've got my here: https://github.com/kriswebdev/android_wireless_tools/tree/master/bin)
adb push iwpriv /data/local/tmp/
adb shell su -c chmod +x /data/local/tmp/iwpriv
Code:
#!/system/bin/sh
ip link set wlan0 down
sleep 1
echo 4 > /sys/module/wlan/parameters/con_mode
sleep 2
ip link set wlan0 up
/data/local/tmp/iwpriv wlan0 monitor 1
/data/local/tmp/iwpriv wlan0 MonitorModeConf 9 40 1 111 0
And enjoy your airodump output
NO PACKET INJECTION! (stubbed out in driver, removed previously?)
If you don't receive any packets, issue "/data/local/tmp/iwpriv wlan0 monitor 1" again.
How does this all work?
Some time ago I discovered these strings in wlan_hal_msg.h: (they appeared in google):
Code:
...
/* Monitor Mode */
WLAN_HAL_ENABLE_MONITOR_MODE_REQ = 302,
WLAN_HAL_ENABLE_MONITOR_MODE_RSP = 303,
WLAN_HAL_DISABLE_MONITOR_MODE_REQ = 304,
WLAN_HAL_DISABLE_MONITOR_MODE_RSP = 305,
...
Then I unscrambled some indirections:
WLAN_HAL_ENABLE_MONITOR_MODE_REQ to WDI_MON_START_REQ in WDI_2_HAL_REQ_TYPE
WDI_MON_START_REQ sent in WDI_ProcessMonStartReq <— actual message sents here!
Called from "Request Processing Array" in function WDI_MonStartReq
Wrapped in WDA_ProcessMonStartReq, which is called in WDA_McProcessMsg by message WDA_MON_START_REQ
Which message is posted by wlan_hdd_mon_postMsg if (MON_MODE_START == pMonCtx->state)
Which is called in __iw_setint_getnone with sub_cmd = WE_SET_MONITOR_STATE
Which is set by iw_priv cmd "monitor"
And then figured out that driver works in different modes:
(vos_types.h)
Code:
/// Concurrency role. These are generic IDs that identify the various roles
/// in the software system.
typedef enum
{ /*ON linux maintain 1-1 corespondence with device_mode_t in hdd*/
VOS_STA_MODE=0,
VOS_STA_SAP_MODE=1, //to support softAp mode . This is misleading. It means AP MODE only.
//The constant name has historical reason
VOS_P2P_CLIENT_MODE,
VOS_P2P_GO_MODE,
VOS_MONITOR_MODE,
VOS_FTM_MODE = 5,
VOS_IBSS_MODE,
VOS_P2P_DEVICE,
VOS_MAX_NO_OF_MODE
} tVOS_CON_MODE;
Mode can be changed by "con_mode" module parameter.
(idk why they reinvented the wheel and not used the default "iw dev wlan0 set mode monitor")
Combined all this and... got a kernel panic. You may get it too. Main reasons are:
- You have not disabled WiFi before changing the mode
- The sleep time after disabling interface is short
- Driver is old. Yes, you can get crashes on some kernels. If you are, flash AGNi.
After successful switching you'll get a working monitor (check this with tcpdump -i wlan0), but with ethernet packets instead of radiotap, so airodump will not work. Luckily, this giant crappy driver can work with radiotap, but you need to configure it. This is done by another iwpriv call:
MonitorModeConf: <channel> <bandwidth> <crccheck> <filter> <conversion_required>
Filter: 3 decimal numbers
least to most: management packets, control packets, data packets
Conversion: 1 - ARPHRD_ETHER (802.3 packets), 0 - ARPHRD_IEEE80211_RADIOTAP (802.11 packets)
(again don't know why they implemented these calls instead of default ioctl's for channel switch, etc. This makes airodump unable to switch channels)
As a result you may get something like on a screenshot
Happy sniffing!
Who said it will not be an interesting , I my self appreciated your effort to bring this up. Kudos to you friend.
Crayvolt said:
Who said it will not be an interesting , I my self appreciated your effort to bring this up. Kudos to you friend.
Click to expand...
Click to collapse
Thanks. I wanted to say that kenzo development is almost dead, we've lost official LOS and keep losing devs.... So it's most likely we'll not see working packet injection (cuz devs who know driver's internals better than me are left), and, possibly, a wrapper library implementing the default ioctl's (like channel switch) used in most programs.
i understand, hopefully we can have new devs. who will continue
This is a perfect news. At least if this device became obsolete, it should still be useful to be a portable linux pen test device, if possible. Anyway, awesome job mate. Very much appreciated
Sent from my Note 3 using XDA Labs
you dont have permission to capture on that device sokect operation not permitted
aldhi said:
This is a perfect news. At least if this device became obsolete, it should still be useful to be a portable linux pen test device, if possible. Anyway, awesome job mate. Very much appreciated
Sent from my Note 3 using XDA Labs
Click to expand...
Click to collapse
Thank you. I forgot to say that monitor mode requiers support from firmware (there's some code in driver that checks for it). Kenzo guys are lucky because we have it enabled . There's also sta+monitor mode (so you can have working wifi connection while sniffing), but it also requiers support from firmware and kenzo's fw compiled without it. I forgot how to enable it, but i think you need to issue "iwpriv wlan0 monitor 1" in default con_mode and check dmesg - there will be a string that says it's not supported (if it is not).
And if someone is interested, our wireless chip is wcn3680b, simmilar one (or same, idk) can be found in nexus 4 (mako)
cerg2010cerg2010 said:
Thank you. I forgot to say that monitor mode requiers support from firmware (there's some code in driver that checks for it). Kenzo guys are lucky because we have it enabled . There's also sta+monitor mode (so you can have working wifi connection while sniffing), but it also requiers support from firmware and kenzo's fw compiled without it. I forgot how to enable it, but i think you need to issue "iwpriv wlan0 monitor 1" in default con_mode and check dmesg - there will be a string that says it's not supported (if it is not).
And if someone is interested, our wireless chip is wcn3680b, simmilar one (or same, idk) can be found in nexus 4 (mako)
Click to expand...
Click to collapse
Can you ziping code and flashable instal on twrp?
Khimin said:
Can you ziping code and flashable instal on twrp?
Click to expand...
Click to collapse
There's nothing to install except iwpriv binary... But OK, I'll try to create a magisk module with enable/disable scripts.
cerg2010cerg2010 said:
There's nothing to install except iwpriv binary... But OK, I'll try to create a magisk module with enable/disable scripts.
Click to expand...
Click to collapse
Thx, im waiting
Khimin said:
Thx, im waiting
Click to expand...
Click to collapse
Ok, I made it quickly!
Source: https://github.com/cerg2010cerg2010/qcmon
There's 2 scripts, run them from shell:
monen - enables monitor mode (you can specify configuration in the parameters, see system/xbin/monen)
mondis - disables monitor mode. You can use your wifi connection again.
cerg2010cerg2010 said:
Ok, I made it quickly!
Source: https://github.com/cerg2010cerg2010/qcmon
There's 2 scripts, run them from shell:
monen - enables monitor mode (you can specify configuration in the parameters, see system/xbin/monen)
mondis - disables monitor mode. You can use your wifi connection again.
Click to expand...
Click to collapse
Thx dude
thank you you are awsome +thumbsup
---------- Post added at 08:49 AM ---------- Previous post was at 08:03 AM ----------
filter expresion syntax error using command tcpdump -i wlan0
help please
---------- Post added at 09:05 AM ---------- Previous post was at 08:49 AM ----------
can you help me?
cerg2010cerg2010 said:
Ok, I made it quickly!
Source: https://github.com/cerg2010cerg2010/qcmon
There's 2 scripts, run them from shell:
monen - enables monitor mode (you can specify configuration in the parameters, see system/xbin/monen)
mondis - disables monitor mode. You can use your wifi connection again.
Click to expand...
Click to collapse
Is it safe to flash with magisk in note 5 pro ?
cerg2010cerg2010 said:
Ok, I made it quickly!
Source: https://github.com/cerg2010cerg2010/qcmon
There's 2 scripts, run them from shell:
monen - enables monitor mode (you can specify configuration in the parameters, see system/xbin/monen)
mondis - disables monitor mode. You can use your wifi connection again.
Click to expand...
Click to collapse
@cerg2010 Tried to flash with magisk in note 5 pro. System apps are not working after disabling the module from magisk it returned to normal. Any solution for this ?
Perinban Parameshwaran said:
@cerg2010 Tried to flash with magisk in note 5 pro. System apps are not working after disabling the module from magisk it returned to normal. Any solution for this ?
Click to expand...
Click to collapse
Please understand that I don't have any "note 5 pro". You can send me logcat and I can try to identify the problem or ask your ROM developer to take a look (if it's not MIUI lol). Anyway, that's just scripts, so you can copy them to /data/local/tmp or /system/bin manually.
Lol I'm a n00b what does this do? Is this a packet sniffer or something?
Op_Flashpoint said:
Lol I'm a n00b what does this do? Is this a packet sniffer or something?
Click to expand...
Click to collapse
Sort of. It makes your sniffer to work - you will be able to capture raw WiFi packets from your device without any dongles.
plis whats rom u use ¿
cerg2010cerg2010 said:
Ok, I made it quickly!
Source: https://github.com/cerg2010cerg2010/qcmon
There's 2 scripts, run them from shell:
monen - enables monitor mode (you can specify configuration in the parameters, see system/xbin/monen)
mondis - disables monitor mode. You can use your wifi connection again.
Click to expand...
Click to collapse
thank you man, monitor mode now working on my poco F1, using its module magisk + aircrack-ng
Every night from 11pm to 6am, my device screen turns itself into night mode(yellow tint). I have set Reading Mode off since the day I bought. Back in previous device(Redmi Note 4, mido) I had Pixel Experience ROM installed. In that I had turned on night mode with the same timing(11pm to 6am). Did Google restored this setting too? I want to turn it off in my K20 device.
Need help!
Redmi K20 Indian version.
I'm having the same issue on my k20. At sunset(~6:30), even though my reading mode settings are off, the display becomes warm/yellow. Can't seem to fix it. Have you managed to solve your issue?
This happens when all your old phone settings synced with your new mobile while setting it up. anyway you may not be aware of that while setting it up.
Here's the solution:-
Download system ui tuner from the playstore.
Give it the permissions it need using command prompt.
You can see some new options in your notification panel which is 'night mode' at click it when the yellow light turn's on.
Turn off the reading mode?
I have no problems here at night. Its only "warm" when its turned on. Maybe you could turn off the time settings also?
Vinay_sandy said:
This happens when all your old phone settings synced with your new mobile while setting it up. anyway you may not be aware of that while setting it up.
Here's the solution:-
Download system ui tuner from the playstore.
Give it the permissions it need using command prompt.
You can see some new options in your notification panel which is 'night mode' at click it when the yellow light turn's on.
Click to expand...
Click to collapse
Thank you a lot. It helps once, but tomorrow it still happens again. Maybe you know how disable this globally?
Prochkailo said:
Thank you a lot. It helps once, but tomorrow it still happens again. Maybe you know how disable this globally?
Click to expand...
Click to collapse
Run these commands in adb
Code:
adb shell 'settings list secure
You will see many device settings in which you need to modify Night display and then run these commands.
Code:
adb shell 'settings put secure night_display_activated 0'
adb shell 'settings put secure night_display_auto_mode 0'
That's it, it will turn off permanently.
Any update please
Are you fix this issue please feed me back?
I confirm this too, its warm but not like read mode. It's just more warm
Edit : try with stable xiaomi.eu ans turn yellow at 10pm without read mode activated...
Impossible for me, have :
Security exception: grantRuntimePermission: Neither user 2000 nor current process has android.permission.GRANT_RUNTIME_PERMISSIONS
EDIT : It's ok ! just dont have turn all 3 usb debugging options on for miui
Digital wellbeing under settings. Turn wind down off.
Is this issue fixed? I have this issue too. How can I fix this without using adb or pc? Thanks in advance!
Vinay_sandy said:
Run these commands in adb
Code:
adb shell 'settings list secure
You will see many device settings in which you need to modify Night display and then run these commands.
Code:
adb shell 'settings put secure night_display_activated 0'
adb shell 'settings put secure night_display_auto_mode 0'
That's it, it will turn off permanently.
Click to expand...
Click to collapse
Thanks a lot, finally I got the solution for this problem. After months thinking that was MIUI bug, I understand now what happened.
When I was on Pixel Experience and returned to MIUI, this yellow screen issue begin.
To run this commands, it's necessary to enable "USB debugging (Security settings)" in developer settings (as I saw on Stackoverflow).
:good:
---------- Post added at 19:44 ---------- Previous post was at 19:37 ----------
Tian_Valderev said:
Is this issue fixed? I have this issue too. How can I fix this without using adb or pc? Thanks in advance!
Click to expand...
Click to collapse
The only way I think it's use another phone with stock android or install Pixel Experience, and revogue the Night Mode from stock android. After a time, when Google account sync , when you return to MIUI this issue probably won't happen again.
Vinay_sandy said:
Run these commands in adb
Code:
adb shell 'settings list secure
You will see many device settings in which you need to modify Night display and then run these commands.
Code:
adb shell 'settings put secure night_display_activated 0'
adb shell 'settings put secure night_display_auto_mode 0'
That's it, it will turn off permanently.
Click to expand...
Click to collapse
Thanks bro. It fixes the problem!
Mkriiger said:
Thanks a lot, finally I got the solution for this problem. After months thinking that was MIUI bug, I understand now what happened.
When I was on Pixel Experience and returned to MIUI, this yellow screen issue begin.
To run this commands, it's necessary to enable "USB debugging (Security settings)" in developer settings (as I saw on Stackoverflow).
:good:
---------- Post added at 19:44 ---------- Previous post was at 19:37 ----------
The only way I think it's use another phone with stock android or install Pixel Experience, and revogue the Night Mode from stock android. After a time, when Google account sync , when you return to MIUI this issue probably won't happen again.
Click to expand...
Click to collapse
Yeah man. I came from an android one device and I can confirm your statement.
I am getting this error /system/bin/sh: settings list secure: inaccessible or not found. Kindly help me out. adb devices command return the device list
senthilanandhpv said:
I am getting this error /system/bin/sh: settings list secure: inaccessible or not found. Kindly help me out. adb devices command return the device list
Click to expand...
Click to collapse
Never mind I figured it out. (I had adb folder at two places and I was trying the commands from incorrect place)
Vinay_sandy said:
This happens when all your old phone settings synced with your new mobile while setting it up. anyway you may not be aware of that while setting it up.
Here's the solution:-
Download system ui tuner from the playstore.
Give it the permissions it need using command prompt.
You can see some new options in your notification panel which is 'night mode' at click it when the yellow light turn's on.
Click to expand...
Click to collapse
WTF bhai it actually works, but how to permanently disable yellow tint, even after using "ui tuner" it again goes to yellowish after some time, just what the hell is this thing? completely ruining my Amoled experience
Harshavarbm13 said:
WTF bhai it actually works, but how to permanently disable yellow tint, even after using "ui tuner" it again goes to yellowish after some time, just what the hell is this thing? completely ruining my Amoled experience
Click to expand...
Click to collapse
I have posted the ADB commands for permanent fix earlier in this thread....!
Run these commands in adb
Code:
adb shell 'settings list secure
You will see many device settings in which you need to modify Night display and then run these commands.
Code:
adb shell 'settings put secure night_display_activated 0'
adb shell 'settings put secure night_display_auto_mode 0'
That's it, it will turn off permanently.
Vinay_sandy said:
I have posted the ADB commands for permanent fix earlier in this thread....!
Run these commands in adb
Code:
adb shell 'settings list secure
You will see many device settings in which you need to modify Night display and then run these commands.
Code:
adb shell 'settings put secure night_display_activated 0'
adb shell 'settings put secure night_display_auto_mode 0'
That's it, it will turn off permanently.
Click to expand...
Click to collapse
Thanx successfully managed to run the command.
Harshavarbm13 said:
Thanx successfully managed to run the command.
Click to expand...
Click to collapse
You're welcome.
About yellow tint problem on Redmi k20 pro
Vinay_sandy said:
Run these commands in adb
Code:
adb shell 'settings list secure
You will see many device settings in which you need to modify Night display and then run these commands.
Code:
adb shell 'settings put secure night_display_activated 0'
adb shell 'settings put secure night_display_auto_mode 0'
That's it, it will turn off permanently.
Click to expand...
Click to collapse
I don't know what is adb command and where to type that please help me. do I need to root my device for this? do I need PC for this ?
Is there a method to getting the color filter camera working again on Android 11/oxygenos 11? I searched and found out it's possible via root and downgrading, but is there a way to on the new Android 11?
yikchandev said:
Is there a method to getting the color filter camera working again on Android 11/oxygenos 11? I searched and found out it's possible via root and downgrading, but is there a way to on the new Android 11?
Click to expand...
Click to collapse
Yes it's definitely possible, there's several threads for it.
In short you need to enable engineer mode
There's more than one way to do this, for me *#808# is the best option
[GUIDE] Access color-filter through command shell
I'm running on the 10.5.10.IN11BA build. Just get a command shell to your OnePlus 8 Pro through adb, no need for the device to be rooted or anything. Once you get there, just type: am start -n...
forum.xda-developers.com
The above is a command that can be run that invokes the option too