Related
I am running CM
So I disabled the slider unlock, but it stopped recognizing my gesture for some reason and I cannot figure out how to login to my phone. Running stable build of CM7.1, not sure if I can change that setting somehow from ADP or do something from a terminal... Any ideas?
When I say gesture, I am not referring to the password based on the motion with the dots, I am saying the screen where the unlock / silent toggle was has been disabled and I cannot get passed there.
Your help is appreciated
Did u try unlock with menu button?
I remember that from cm7
Sent from my MB525 running 4.5.1-134 DFP 231 DEFY+ ROM...
using XDA App
No menu button doesn't do anything....
Do you know WHERE this "Slider Disabled" setting is stored? I could go in thru ADB and change it but I don't know where to look.
Here are the things I have tried already
----
Attempt 1:
$ ./adb -d shell
# cd data/data
# sqlite3 ./com.android.providers.settings/databases/settings.db
sqlite> update system set value=1 where name='lockscreen_disabled';
sqlite> .exit
# reboot
Attempt 2:
adb shell
input keyevent 82
---
Neither of these worked. I think the solution should be in the updating the settings.db, but maybe its a different row/record that contains "ENABLE slider"?
Help would be appreciated!
could deleting the the offending theme restore to normal?? Just thinking out loud here ^^
don't know much about adb
Okay. No help here, but I found a fix and I thought i would share it since I have seen that apparently other people have had this problem with no help as well other than "Wipe and reinstall rom"
This app fixed it!
https://market.android.com/details?id=se.curity.android.screenlockbypass
Just make sure you follow the instructions, you have to install the app, than install any other random app and BAM- unlocked phone! Sweet
Good morning. Can anyone tell me a way to unlock the screen without touching the display but simply pressing the unlock button?
I have USB debugging enabled, and root. Something with ADB ... My actually unlock mode is "drag" ... I'm looking for a way to set as a method of unlocking "nothing" so that you just press the button and you unlock ...
Some command-style ADB like this
Code:
adb shell
cd / data / data / com.android.providers.settings / databases
sqlite3 settings.db
update system set value = 0 where name = 'lock_pattern_autolock';
update system set value = 0 where name = 'lockscreen.lockedoutpermanently';
.quit
But this don't work
MrGioba said:
Good morning. Can anyone tell me a way to unlock the screen without touching the display but simply pressing the unlock button?
I have USB debugging enabled, and root. Something with ADB ... My actually unlock mode is "drag" ... I'm looking for a way to set as a method of unlocking "nothing" so that you just press the button and you unlock ...
Some command-style ADB like this
Code:
adb shell
cd / data / data / com.android.providers.settings / databases
sqlite3 settings.db
update system set value = 0 where name = 'lock_pattern_autolock';
update system set value = 0 where name = 'lockscreen.lockedoutpermanently';
.quit
But this don't work
Click to expand...
Click to collapse
Umm... maybe I'm not getting this, but why don't you just go to Settings/Security/Screen lock and set it to "None"?
Works for me, Screen unlocks with just the button...
danielms22 said:
Umm... maybe I'm not getting this, but why don't you just go to Settings/Security/Screen lock and set it to "None"?
Works for me, Screen unlocks with just the button...
Click to expand...
Click to collapse
I can't touch the screen
MrGioba said:
My screen is broken
Click to expand...
Click to collapse
Oh, got it.
Well, maybe this will help then:
http://www.youtube.com/watch?v=lIF7mym5EpU
Unless you already did that and are looking for a permanent solution to unlock your phone with just the button. In that case I have no idea.
danielms22 said:
Oh, got it.
Well, maybe this will help then:
http://www.youtube.com/watch?v=lIF7mym5EpU
Unless you already did that and are looking for a permanent solution to unlock your phone with just the button. In that case I have no idea.
Click to expand...
Click to collapse
Not helped but anyway i've solved my problem using
Code:
adb shell input swipe x1 y1 x2 y2
Hi everybody,
I work on a light Launcher (to replace Launcher2.apk).
One of my objectives is obviously to have a quick boot.
But when my app is ready to show something, the bootanimation is still visible until the Boot timeout (40s after the first log):
WindowManager: ***** BOOT TIMEOUT: forcing display enabled
If I reboot with my command line :
adb reboot && adb wait-for-device && adb shell setprop service.bootanim.exit 1
My boot time is around 15s but with a bad rotation display until I receive the first ConfigurationChanged event. Without this point, the app is ready so...
Question 1: Do you know a way to properly close the boot animation?
Question 2: If the Q1 don't solve the ConfigurationChanged event, do you know a method to receive the ConfigurationChanged event in my Launcher?
Best Regards,
Kikiwa
PS : I hope this topic is in the right section, sorry if it's not the case.
Same problem
kikiwa said:
Hi everybody,
I work on a light Launcher (to replace Launcher2.apk).
One of my objectives is obviously to have a quick boot.
But when my app is ready to show something, the bootanimation is still visible until the Boot timeout (40s after the first log):
WindowManager: ***** BOOT TIMEOUT: forcing display enabled
If I reboot with my command line :
adb reboot && adb wait-for-device && adb shell setprop service.bootanim.exit 1
My boot time is around 15s but with a bad rotation display until I receive the first ConfigurationChanged event. Without this point, the app is ready so...
Question 1: Do you know a way to properly close the boot animation?
Question 2: If the Q1 don't solve the ConfigurationChanged event, do you know a method to receive the ConfigurationChanged event in my Launcher?
Best Regards,
Kikiwa
PS : I hope this topic is in the right section, sorry if it's not the case.
Click to expand...
Click to collapse
I am having the same problem , have you found any solution?
Hello !
Sorry but no. I'm still interested by the solution BTW.
Good luck
Kikiwa
kikiwa said:
Hello !
Sorry but no. I'm still interested by the solution BTW.
Good luck
Kikiwa
Click to expand...
Click to collapse
In my case I pushed my custom launcher apk to system/app and deleted launcher2.apk
Could it be that the system is waiting for some special response from default launcher? That should be made in custom luancher?
Possible Solution
Hey guys,
I was having this same issue for a while now, and I finally found a solution that works for me, at least as of Android 4.4.4 on a Nexus 7 2013 (LTE)
What I did to find this was selectively disable system apps one by one, and then test a reboot.
In my case, disabling Launcher2 didn't affect the boot sequence, but SystemUI (com.android.systemui) did cause these delayed boot times.
I dug through the ASOP source code, and found that the WindowManagerService performs a few checks in performEnableScreen() before stopping boot animation / displaying normally:
- System services must all be ready (mSystemBooted)
- A keyguard or application must be attached to Window Manager (haveApp || haveKeyguard)
- The Wallpaper Service must be disabled or ready (!wallpaperEnabled || haveWallpaper)
Since monitoring logcat showed my replacement launcher was open, and the system services had no errors, I suspected #3 was the problem
In the source for SystemUI, I found a single reference for "wallpaper" - com.android.systemui.ImageWallpaper is an included class that extends WallpaperService but itself is never referenced from that package.
Checking logcat again, I found these lines:
Code:
Attempted wallpaper ComponentInfo{com.android.systemui/com.android.systemui.ImageWallpaper} is unavailable
Default wallpaper component not found!
It turns out that the system-level WallpaperManagerService has hard-coded that particular class.
As a test fix, I created a new project with package name "com.android.systemui" and a single class "ImageWallpaper" that extends WallpaperService, declared this as a service in my manifest, and installed this apk on a device.
I rebooted, and the boot times were back to normal (~20sec) instead of the previous ~50sec.
So in summary: SystemUI was the culprit in my case; creating a fake replacement package with that hardcoded class back in fixed the long boot times.
Thank you
dtyler7 said:
Hey guys,
I was having this same issue for a while now, and I finally found a solution that works for me, at least as of Android 4.4.4 on a Nexus 7 2013 (LTE)
What I did to find this was selectively disable system apps one by one, and then test a reboot.
In my case, disabling Launcher2 didn't affect the boot sequence, but SystemUI (com.android.systemui) did cause these delayed boot times.
I dug through the ASOP source code, and found that the WindowManagerService performs a few checks in performEnableScreen() before stopping boot animation / displaying normally:
- System services must all be ready (mSystemBooted)
- A keyguard or application must be attached to Window Manager (haveApp || haveKeyguard)
- The Wallpaper Service must be disabled or ready (!wallpaperEnabled || haveWallpaper)
Since monitoring logcat showed my replacement launcher was open, and the system services had no errors, I suspected #3 was the problem
In the source for SystemUI, I found a single reference for "wallpaper" - com.android.systemui.ImageWallpaper is an included class that extends WallpaperService but itself is never referenced from that package.
Checking logcat again, I found these lines:
Code:
Attempted wallpaper ComponentInfo{com.android.systemui/com.android.systemui.ImageWallpaper} is unavailable
Default wallpaper component not found!
It turns out that the system-level WallpaperManagerService has hard-coded that particular class.
As a test fix, I created a new project with package name "com.android.systemui" and a single class "ImageWallpaper" that extends WallpaperService, declared this as a service in my manifest, and installed this apk on a device.
I rebooted, and the boot times were back to normal (~20sec) instead of the previous ~50sec.
So in summary: SystemUI was the culprit in my case; creating a fake replacement package with that hardcoded class back in fixed the long boot times.
Click to expand...
Click to collapse
It is exactly my problem and your solution seems perfect
Thank you for your efforts
command "setprop ctl.start bootanim" to perform boot animation;
command "setprop ctl.stop bootanim" stop the boot animation.
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!
So the Lockscreen on my new HD 10 is pretty garbage, so far I've managed to get rid of the ads, but I can't change the Lockscreen wallpaper and I don't get any preview of a notification (e.g. the mail subject etc.)
Is there a workaround for those problems? Because simply isntalling a new lockscreen app, just makes me unlock my tablet twice, which isn't ideal.
Did you manually disable com.amazon.kindle.kso (special offers/lockscreen ads) over ADB in fire os 5.4.0.0 or lower using the method DragonFire1024 posted? If so, then yes, I found a fix that allows you to see notifications on the lockscreen without swiping down, more like the stock Android 5.x lockscreen.
lakitu47 said:
Did you manually disable com.amazon.kindle.kso (special offers/lockscreen ads) over ADB in fire os 5.4.0.0 or lower using the method DragonFire1024 posted? If so, then yes, I found a fix that allows you to see notifications on the lockscreen without swiping down, more like the stock Android 5.x lockscreen.
Click to expand...
Click to collapse
I did it over adb yes, but on the newest release of fire OS (5.6)
wieli99 said:
I did it over adb yes, but on the newest release of fire OS (5.6)
Click to expand...
Click to collapse
I thought Amazon broke the ability to disable apps over ADB with the release of 5.4.0.1. Did that not affect the new 2017 HD 10?
Sent from my Amazon KFGIWI using XDA Labs
lakitu47 said:
I thought Amazon broke the ability to disable apps over ADB with the release of 5.4.0.1. Did that not affect the new 2017 HD 10?
Click to expand...
Click to collapse
It works for me in adb shell with
pm clear --user 0 com.amazon.kindle.kso
Well, I don't know if this will work with your exact tablet, but try this:
1. If you haven't already, get the Google Play store/services on your tablet
2. Download this app without the quotes: "https://play.google.com/store/apps/details?id=by4a.setedit22&hl=en"
3. Follow on-screen instructions to grant tablet permission to edit secure settings (worked on 2 devices on 5.6)
BE CAREFUL WHAT YOU EDIT. If you change the wrong settings, your tablet can and probably bootloop or get bricked.
4. Go to the "secure" tab, scroll down to "limit_ad_tracking" and change value to 1
5. Go to "global" tab, scroll down to "LOCKSCREEN_AD_ENABLED" and change value to 0. Immediately reboot your device.
This was tested and worked on two HD 8 tablets on 5.6, with special offers manually disabled on 5.4. Since Amazon still thinks you are subscribed to special offers (ads), the notifications are hidden. This workaround actually makes the ads gone (hopefully), so the notifications will appear as soon as you turn on the screen, without a swipe down gesture.
Open up command prompt. Type in "adb shell", Then type in "su"
Then copy this into command prompt.
sqlite3 /data/system/locksettings.db "UPDATE locksettings SET value = '1' WHERE name = 'lockscreen.disabled'"
You will not get a confirmation, now type "exit", then type "reboot".
Let the device reboot and enjoy! Now install a new lockscreen.
Want it back?
sqlite3 /data/system/locksettings.db "UPDATE locksettings SET value = '0' WHERE name = 'lockscreen.disabled'"
*This is messing with the sqlite in the actual android system files, please becareful and don't go around changing values in system files.
source: Tips Tricks and the Root
Jned said:
Open up command prompt. Type in "adb shell", Then type in "su"
Then copy this into command prompt.
sqlite3 /data/system/locksettings.db "UPDATE locksettings SET value = '1' WHERE name = 'lockscreen.disabled'"
You will not get a confirmation, now type "exit", then type "reboot".
Let the device reboot and enjoy! Now install a new lockscreen.
Want it back?
sqlite3 /data/system/locksettings.db "UPDATE locksettings SET value = '0' WHERE name = 'lockscreen.disabled'"
*This is messing with the sqlite in the actual android system files, please becareful and don't go around changing values in system files.
source: Tips Tricks and the Root
Click to expand...
Click to collapse
do you have to have root for this? i did su and it said, " su not found."
Jned said:
Open up command prompt. Type in "adb shell", Then type in "su"
Then copy this into command prompt.
sqlite3 /data/system/locksettings.db "UPDATE locksettings SET value = '1' WHERE name = 'lockscreen.disabled'"
You will not get a confirmation, now type "exit", then type "reboot".
Let the device reboot and enjoy! Now install a new lockscreen.
Want it back?
sqlite3 /data/system/locksettings.db "UPDATE locksettings SET value = '0' WHERE name = 'lockscreen.disabled'"
*This is messing with the sqlite in the actual android system files, please becareful and don't go around changing values in system files.
source: Tips Tricks and the Root
Click to expand...
Click to collapse
Like that one eh? That was one of the first ones I found. Works without root too.
wieli99 said:
So the Lockscreen on my new HD 10 is pretty garbage, so far I've managed to get rid of the ads, but I can't change the Lockscreen wallpaper and I don't get any preview of a notification (e.g. the mail subject etc.)
Is there a workaround for those problems? Because simply isntalling a new lockscreen app, just makes me unlock my tablet twice, which isn't ideal.
Click to expand...
Click to collapse
Personally, I'd suggest just rooting it and disabling it. I did it a few months ago on my Dad's HD10 by following one of the guides here- I just can't remember which one, but it was simple. I also installed Gravity Screen Pro since I have his set up more like a laptop. The screen turns on/off when opened/ closed without ever having to see a lock screen. I might stop by my parents today (depending on the weather) and if i do, I'll try to trace my steps and link the guide I followed
dondraper23 said:
Personally, I'd suggest just rooting it and disabling it. I did it a few months ago on my Dad's HD10 by following one of the guides here- I just can't remember which one, but it was simple. I also installed Gravity Screen Pro since I have his set up more like a laptop. The screen turns on/off when opened/ closed without ever having to see a lock screen. I might stop by my parents today (depending on the weather) and if i do, I'll try to trace my steps and link the guide I followed
Click to expand...
Click to collapse
There are also a few Xposed modules that work too.
Sent from my Samsung Galaxy S4 using XDA Labs
wieli99 said:
So the Lockscreen on my new HD 10 is pretty garbage, so far I've managed to get rid of the ads, but I can't change the Lockscreen wallpaper and I don't get any preview of a notification (e.g. the mail subject etc.)
Is there a workaround for those problems? Because simply isntalling a new lockscreen app, just makes me unlock my tablet twice, which isn't ideal.
Click to expand...
Click to collapse
I followed this guide: https://forum.xda-developers.com/hd8-hd10/help/root-required-completely-disable-enable-t3739257
I just had to do it again today because attempted to use Xposed and wound up getting in over my head and got caught in a bootloop, but at least I can reaffirm that this guide works
---------- Post added at 07:56 AM ---------- Previous post was at 07:49 AM ----------
DragonFire1024 said:
There are also a few Xposed modules that work too.
Sent from my Samsung Galaxy S4 using XDA Labs
Click to expand...
Click to collapse
I love all your posts- it's your guide I followed to disable the lockscreen. Unfortunately, Xposed is a bit much for a "noob" like me. I attempted to install it and got caught in a bootloop and had to do a factory reset. Considering what my dad uses it for, the negatives far outway the positives for me to bother with Xposed ever again