[Q] modify "developer options" through adb to deactivate "slide to unlock"
Hello,
I am trying to modify "developer options" through adb, in order to remove "slide to unlock", so the phone wakes directly into "main desktop".
What database should I aim for? what should I modify/add to the database in order to achieve this?
--
I am trying to do this because my phone digitizer is broken. I am using AndroidScreencast to control it BUT I cannot get past the "slide to unlock"; AndroidScreencast does not seem to allow "swipe".
So I want to deactivate "slide to unlock".
--
Another solution would be being able to emulate a swipe through adb, and unlock this way. I've seen some people using "adb shell input swipe" but I do NOT have that possibility :silly:
I am trying this on a Wildfire S with MIUIv4 by Henry_01
--
THANK YOU very much for your help.
EXTRA, a list of all databases I can find in the system:
/system/etc/yellowpage.db
/system/etc/weather_city.db
/system/etc/telocation.db
/data/data/com.android.providers.userdictionary/databases/user_dict.db-journal
/data/data/com.android.providers.userdictionary/databases/user_dict.db
/data/data/com.android.deskclock/databases/alarms.db-journal
/data/data/com.android.deskclock/databases/alarms.db
/data/data/com.lbe.security.miui/databases/lbe_security.db-journal
/data/data/com.lbe.security.miui/databases/lbe_security.db
/data/data/com.google.android.gsf/databases/subscribedfeeds.db-journal
/data/data/com.google.android.gsf/databases/gservices.db-journal
/data/data/com.google.android.gsf/databases/talk.db-journal
/data/data/com.google.android.gsf/databases/talk.db
/data/data/com.google.android.gsf/databases/gservices.db
/data/data/com.google.android.gsf/databases/subscribedfeeds.db
/data/data/com.google.android.gsf/databases/googlesettings.db-journal
/data/data/com.google.android.gsf/databases/googlesettings.db
/data/data/com.android.inputmethod.latin/databases/userbigram_dict.db-journal
/data/data/com.android.inputmethod.latin/databases/userbigram_dict.db
/data/data/com.android.vending/databases/suggestions.db
/data/data/com.android.vending/databases/library.db-journal
/data/data/com.android.vending/databases/localappstate.db-journal
/data/data/com.android.vending/databases/suggestions.db-journal
/data/data/com.android.vending/databases/localappstate.db
/data/data/com.android.vending/databases/library.db
/data/data/com.android.providers.media/databases/external.db-shm
/data/data/com.android.providers.media/databases/external.db-wal
/data/data/com.android.providers.media/databases/internal.db-shm
/data/data/com.android.providers.media/databases/internal.db-wal
/data/data/com.android.providers.media/databases/internal.db
/data/data/com.android.providers.media/databases/external.db
/data/data/com.google.android.partnersetup/databases/rlz_data.db-journal
/data/data/com.google.android.partnersetup/databases/rlz_data.db
/data/data/com.android.mms/files/festival_sms.db
/data/data/com.android.browser/app_databases/Databases.db
/data/data/com.android.browser/app_databases/https_mail.google.com_0/0000000000000001.db
/data/data/com.android.browser/app_geolocation/CachedGeoposition.db
/data/data/com.android.browser/app_geolocation/GeolocationPermissions.db
/data/data/com.android.browser/app_icons/WebpageIcons.db
/data/data/com.android.browser/app_appcache/ApplicationCache.db
/data/data/com.android.browser/databases/webviewCookiesChromiumPrivate.db
/data/data/com.android.browser/databases/webview.db-shm
/data/data/com.android.browser/databases/webview.db
/data/data/com.android.browser/databases/browser2.db-journal
/data/data/com.android.browser/databases/browser2.db
/data/data/com.android.browser/databases/autofill.db-journal
/data/data/com.android.browser/databases/autofill.db
/data/data/com.android.browser/databases/webview.db-wal
/data/data/com.android.browser/databases/webviewCookiesChromium.db
/data/data/com.miui.providers.telocation/databases/customtelocation.db
/data/data/com.miui.providers.telocation/databases/customtelocation.db-journal
/data/data/com.android.providers.downloads/databases/downloads.db-journal
/data/data/com.android.providers.downloads/databases/downloads.db
/data/data/com.android.fileexplorer/databases/kuaipan.db-journal
/data/data/com.android.fileexplorer/databases/kuaipan.db
/data/data/com.miui.home/databases/launcher.db-journal
/data/data/com.miui.home/databases/launcher.db
/data/data/com.airbnb.android/databases/webview.db-shm
/data/data/com.airbnb.android/databases/suggestions.db-journal
/data/data/com.airbnb.android/databases/suggestions.db
/data/data/com.airbnb.android/databases/webview.db-wal
/data/data/com.airbnb.android/databases/webview.db
/data/data/com.airbnb.android/databases/google_analytics_v2.db
/data/data/com.airbnb.android/databases/google_analytics_v2.db-journal
/data/data/com.airbnb.android/databases/webviewCookiesChromium.db
/data/data/com.airbnb.android/databases/webviewCookiesChromiumPrivate.db
/data/data/com.android.providers.settings/databases/settings.db-shm
/data/data/com.android.providers.settings/databases/settings.db-wal
/data/data/com.android.providers.settings/databases/settings.db
/data/data/com.android.providers.telephony/databases/mmssms.db-journal
/data/data/com.android.providers.telephony/databases/firewall.db-journal
/data/data/com.android.providers.telephony/databases/telephony.db
/data/data/com.android.providers.telephony/databases/telephony.db-journal
/data/data/com.android.providers.telephony/databases/mmssms.db
/data/data/com.android.providers.telephony/databases/firewall.db
/data/data/com.whatsapp/databases/wa.db-shm
/data/data/com.whatsapp/databases/wa.db-wal
/data/data/com.whatsapp/databases/msgstore.db-journal
/data/data/com.whatsapp/databases/msgstore.db
/data/data/com.whatsapp/databases/wa.db
/data/data/com.google.android.googlequicksearchbox/databases/qsb-log.db-journal
/data/data/com.google.android.googlequicksearchbox/databases/qsb-log.db
/data/data/com.google.android.googlequicksearchbox/databases/qsb-history.db-journal
/data/data/com.google.android.googlequicksearchbox/databases/qsb-history.db
/data/data/com.miui.notes/databases/note.db-journal
/data/data/com.miui.notes/databases/note.db
/data/data/com.android.keychain/databases/grants.db
/data/data/com.android.keychain/databases/grants.db-journal
/data/data/com.android.settings/databases/webviewCookiesChromium.db
/data/data/com.android.settings/databases/webviewCookiesChromiumPrivate.db
/data/data/com.android.settings/databases/miui_settings.db-journal
/data/data/com.android.settings/databases/webview.db-wal
/data/data/com.android.settings/databases/webview.db
/data/data/com.android.settings/databases/webview.db-shm
/data/data/com.android.settings/databases/miui_settings.db
/data/data/com.android.providers.calendar/databases/calendar.db-journal
/data/data/com.android.providers.calendar/databases/calendar.db
/data/data/com.android.providers.contacts/databases/contacts2.db-journal
/data/data/com.android.providers.contacts/databases/profile.db-journal
/data/data/com.android.providers.contacts/databases/profile.db
/data/data/com.android.providers.contacts/databases/contacts2.db
/data/data/com.ijinshan.mguard.provider/files/firewall_sys_rules.db
/data/data/com.ijinshan.mguard.provider/files/antivirus.db
/data/data/com.android.email/databases/EmailProviderBody.db-journal
/data/data/com.android.email/databases/EmailProvider.db-journal
/data/data/com.android.email/databases/EmailProviderBackup.db-journal
/data/data/com.android.email/databases/EmailProviderBody.db
/data/data/com.android.email/databases/EmailProviderBackup.db
/data/data/com.android.email/databases/EmailProvider.db
/data/data/com.google.android.gsf.login/databases/webviewCookiesChromiumPrivate.db
/data/data/com.google.android.gsf.login/databases/webview.db-wal
/data/data/com.google.android.gsf.login/databases/webview.db
/data/data/com.google.android.gsf.login/databases/webview.db-shm
/data/data/com.google.android.gsf.login/databases/webviewCookiesChromium.db
/data/data/com.google.android.gms/databases/app_state.db-journal
/data/data/com.google.android.gms/databases/app_state.db
/data/data/com.google.android.gms/databases/rmq.db-journal
/data/data/com.google.android.gms/databases/games_51caa370.db
/data/data/com.google.android.gms/databases/plus.db-journal
/data/data/com.google.android.gms/databases/gcore_ulr_ActivityDetection.db-journal
/data/data/com.google.android.gms/databases/gcore_ulr_UlrLocation.db-journal
/data/data/com.google.android.gms/databases/pluscontacts.db-journal
/data/data/com.google.android.gms/databases/peoplelog.db
/data/data/com.google.android.gms/databases/pluscontacts.db
/data/data/com.google.android.gms/databases/plus.db
/data/data/com.google.android.gms/databases/rmq.db
/data/data/com.google.android.gms/databases/gcore_ulr_UlrLocation.db
/data/data/com.google.android.gms/databases/gcore_ulr_ActivityDetection.db
/data/data/com.google.android.gms/databases/games_51caa370.db-journal
/data/system/accounts.db-journal
/data/system/accounts.db
Click to expand...
Click to collapse
Related
I bought a Chinese Android 4.2.2 smartwatch (SWatch / Kingelon K2) and discover it does not have any virtual keyboard. There is also no "input" option in Settings (there is "language" only).
I installed a third party keyboard (Anysoftkeyboard) and another app called Quick Keyboard Switch that can change keyboards with going through Settings.
When I run Quick Keyboard Switch and tried to enable the downloaded keyboard, the app force closed.
I found a post in Stackexchange describing how to use ADB shell to enable and set the default keyboard:
how to change input method with ime command
The instruction from the above post describes how to enable the keyboard using "ime enable com.etc.etc" command before setting the keyboard as default using "ime set com.etc.etc"
Unfortunately, when I use the "ime enable" command in ADB shell ("su" applied, the watch has been rooted), it gives me an error message:
Error: Unknown ID: null
When I use "ime set" command, it returns a similar error message ("com.etc.etc" (name of keyboard) instead of "null") - I gather this is because I have not enabled the keyboard yet.
I am worried that I don't even see "keyboard" option in Settings - does that mean the input module has been removed by the firmware maker of this smartwatch?
If so, where should I look in the Android firmware (I guess somewhere inside /system) that I can copy and paste to restore the keyboard input function?
I am NOT a developer nor a computer engineer. I google and try to find solutions to my problems. Thank you for your help and being patient.
What does this actually do to tell the bootloader that it is ok to unlock.
Write a 1 byte file to the system partition?
Write one byte of the bootloader?
Searching google just gave "How to Enable OEM Unlock to unlock your bootloader" articles nothing on how it actually works.
Finally found out how it works.
While trying to find my screen resolution while offline I checked getprop with terminal and sys.oem_unlock_allowed [1] came up.
I then checked /dev/__properties__ and it was there so it is enable by writing sys.oem_unlock_allowed = 1 to /dev/__properties__
Guicrith said:
Finally found out how it works.
While trying to find my screen resolution while offline I checked getprop with terminal and sys.oem_unlock_allowed [1] came up.
I then checked /dev/__properties__ and it was there so it is enable by writing sys.oem_unlock_allowed = 1 to /dev/__properties__
Click to expand...
Click to collapse
Is there any way to prevent a user from accidentally disabling this option in Developer options?
I am asking because if you disable "OEM unlock" after installing a custom ROM in eg. a Samsung phone, the device refuses to boot with a FRP "Custom binary blocked by FRP lock" message.
timba123 said:
I'm on samsung a102u . The galaxy a10e. I added sys.oem_unlock_allowed 1 but now both sys.oem_unlock_allowed 0 and sys.oem_unlock_allowed 1 both are showing up. Is there a command to remove the sys.oem_unlock_allowed 0
Click to expand...
Click to collapse
Well actually the first one is indeed sys.oem_unlock_allowed but the second one is sys.oem_unlocl_allowed so those are not the same: probably you made a typo when adding it and thus it didn't just change the original prop's value but added a new, mistyped prop with the desired value? The K and L buttons on a QWERTY or similar keyboard are next to each other (and the Levenshtein distance between the names of the two props is only 1).
This is an excellent resource for information on bootloader unlock ability.
There are several components at play here:
ro.oem_unlock_supported is set at ROM build time; if 1, the OEM Unlocking toggle should be available. This property is not visible without root.
sys.oem_unlock_allowed is used by some "permissive" devices such as the Google Pixel to determine whether OEM unlocking should be allowed; in the case of the Pixel, this is done by checking an online whitelist of serial numbers
get_unlock_ability is controlled by the OEM Unlocking toggle. Off is 0, on is 1. If 0, the bootloader will reject fastboot flashing unlock. Can be checked in bootloader mode using ADB: fastboot flashing get_unlock_ability
To fit the status bar with notch, it is necessary to change the density of the device screen
See the attached image.
Steps.
Enable "USB debugging" in "Develop options".
Enable "USB security setting" (bellow "USB debugging") (tap on yes to all).
Setup ADB on your computer with this tool
Open the ADB installation folder
Right click + shift and click on open command window here (on windows 10, type "CMD" in the upper bar and enter)
Type this and accept all permissions on the device screen:
ADB Devices
adb shell wm density 470
adb reboot
Click to expand...
Click to collapse
Done!
It is likely that the screen aspect looks a bit different, you can fix that by adjusting the size of the font in screen options.
Thanks
or change it in developer settings ...
there is no difference
Wow u change resolution from ADB! Mama's hacker!
andrecuellar said:
To fit the status bar with notch, it is necessary to change the density of the device screen
See the attached image.
Steps.
Enable "USB debugging" in "Develop options".
Enable "USB security setting" (bellow "USB debugging") (tap on yes to all).
Setup ADB on your computer with this tool
Open the ADB installation folder
Right click + shift and click on open command window here (on windows 10, type "CMD" in the upper bar and enter)
Type this and accept all permissions on the device screen:
Done!
It is likely that the screen aspect looks a bit different, you can fix that by adjusting the size of the font in screen options.
Thanks
Click to expand...
Click to collapse
This is not solution, already have it on forum, changing resolution it's not what all we want! Stop repost this sh!t.
Thank you. I didn't know these. Is there a way to only fit the status bar , because when I change this, all the icons and text shrink. I have a theme with the icons very big, and I would like to keep it that way.
Nope
Okey so. Doesn't work.
How can I go back?
I get (bootloader) unlock_abilty = 16777216
I also have to do ./ before any commands
I'm really struggling and could use some advice on how to make my unlock ability 1
The value of "unlock_ability" gets set to 1 if you in Android's Settings -> Developer option enable option "Allow OEM unlocking".
jwoegerbauer said:
The value of "unlock_ability" gets set to 1 if you in Android's Settings -> Developer option enable option "Allow OEM unlocking".
Click to expand...
Click to collapse
I have done that, the issue is that its a wierd high number
I need an app that every Friday at 4PM will turn on (=Allday) the "Always On" display and turn off the "Wake on Wrist Raise". And on Saturday at 8PM will reverse the 2 settings.
crontab with correct shell commands should do. will probably need root and busybox.
(google crontab android)
or maybe without root according to this (lower half of the page)
How to use crontab in Android?
I can't find answer to my question: Is it possible to run crontab to reboot Android using busybox (or other means) Tried to run crontab, and it complain about unknown uid 0. Tried to run reboot, ...
stackoverflow.com
then google adb commands for things you need to do "always on display" etc..
test with adb to make sure your commands work .
then implement without adb shell in crontab, since it will be executed from within android not adb.
If you are talking about zeppos based watch then only first condition (AOD) is reachable.