Go to the /data/system folder, find & delete this files.
- gatekeeper.password.key
- gatekeeper.pattern.key
- locksettings.db
- locksettings.db-shm
- locksettings.db-wal
reboot system.
Now you have fingerprint enable and pin/password disabled.
Amazing thanks! Exactly what I needed with radon and double tap
Enviado desde mi Redmi Note 3 mediante Tapatalk
Good, why would u disable it? Sometimes the sensor cannot recognize my finger so i need to open it via other method like pattern which is my favorite.
But, else it is great. Appreciate ur effort.
Sent from my Redmi Note 3 using Tapatalk
scheccia said:
Go to the /data/system folder, find & delete this files.
- gatekeeper.password.key
- gatekeeper.pattern.key
- locksettings.db
- locksettings.db-shm
- locksettings.db-wal
reboot system.
Now you have fingerprint enable and pin/password disabled.
Click to expand...
Click to collapse
febry_valdy said:
Good, why would u disable it? Sometimes the sensor cannot recognize my finger so i need to open it via other method like pattern which is my favorite.
But, else it is great. Appreciate ur effort.
Sent from my Redmi Note 3 using Tapatalk
Click to expand...
Click to collapse
there's an option for this in NOS (one of the things that makes my life easier)
but it's good to know I can do it myself with other roms
Does it causing problem for a few rom? which is need to input the security code (pin/password/pattern) at every boot up?? Anyone tried with CAF AOSP?
febry_valdy said:
Good, why would u disable it? Sometimes the sensor cannot recognize my finger so i need to open it via other method like pattern which is my favorite.
But, else it is great. Appreciate ur effort.
Sent from my Redmi Note 3 using Tapatalk
Click to expand...
Click to collapse
I disable it, expecially for lockscreen, i dont use it, but if want use fingerprint, i must enable it... Wiith this mod no lockkk :silly:
I did exactly what u say , But lockscreen can even be unlocked by SWIPE , How to prevent this ? Or else any way to restore pattern nd pin , please consider I accidentally deleted "Gatekeeperd" too ????
scheccia said:
Go to the /data/system folder, find & delete this files.
- gatekeeper.password.key
- gatekeeper.pattern.key
- locksettings.db
- locksettings.db-shm
- locksettings.db-wal
reboot system.
Now you have fingerprint enable and pin/password disabled.
Click to expand...
Click to collapse
Is this safe? Fingerprint can disable itself once too many wrong fingerprint is provide.
Related
UPSM is good way to save some battery when needed, but only a very limited apps we can use under UPSM. With root access, we can add more apps support in UPSM.
Well, the whole idea of UPSM is to save battery, why on earth we want to add more apps to drain the battery? Because we can :victory:
For the start, our mod will add a few applications so you can test it out before customizing your own application list.
Apps added in our mod:
1) Camera
2) Gallery
3) Torch (included AOSP torch.apk for this feature)
4) Chrome
5) Hangout
Instruction to add more apps to UPSM
1) Download the UPSM_Add_More_Apps.zip from : http://electron-team.com/ADDONS/other/
2) Put zip file in sd card.
3) Boot in recovery and clear cache partition
4) Flash the zip file and reboot your phone
5) Boot into UPSM to test the added applications
How to add your own apps?
6) Go to system/csc and open up allowed_apps_upsm.xml with text editor
7) Add your desired applications. You need to know the application Package Name and the Main Class Name. Check the app's Android.Manifest.xml to find out.
8) Then go to phone data/data/com.sec.android.emergencylauncher/databases/ and delete EmergencyLauncherUPSM.db
9) Reboot your phone.
10) Done.
Note: Music app doesn't work in UPSM because some background services has been turn off.
Wish to have Xposed module or app to easily add more app to UPSM? Me too. Let's hope somebody could make one in future.:fingers-crossed:
Eteam
oh. big good new. big thank
thank you very much
in the other hand，can somebody make a apk or an easy way to find out own apk's className and packageName ........
as a Chinese , hope that can someone understand my poor English........
PS: can you make a new xml add a apk call " wechat " ? it is use often in china
Nic wu said:
thank you very much
in the other hand，can somebody make a apk or an easy way to find out own apk's className and packageName ........
as a Chinese , hope that can someone understand my poor English........
PS: can you make a new xml add a apk call " wechat " ? it is use often in china
Click to expand...
Click to collapse
Here : https://www.dropbox.com/s/n4wdk1r20qafdcd/allowed_apps_upsm.xml
Push it to system/csc and set permission rw-r--r--
Delete EmergencyLauncherUPSM.db at data/data/com.sec EmergencyLauncher/databases
Reboot
Sent from my GT-N7100 using Tapatalk
Nic wu said:
thank you very much
in the other hand，can somebody make a apk or an easy way to find out own apk's className and packageName ........
as a Chinese , hope that can someone understand my poor English........
PS: can you make a new xml add a apk call " wechat " ? it is use often in china
Click to expand...
Click to collapse
Hello
Here we go -> https://play.google.com/store/apps/details?id=jp.susatthi.ManifestViewer
Hope that can help you
Arsaw said:
Here : https://www.dropbox.com/s/n4wdk1r20qafdcd/allowed_apps_upsm.xml
Push it to system/csc and set permission rw-r--r--
Delete EmergencyLauncherUPSM.db at data/data/com.sec EmergencyLauncher/databases
Reboot
Sent from my GT-N7100 using Tapatalk
Click to expand...
Click to collapse
thank you very much :good::good::good:
---------- Post added at 07:36 PM ---------- Previous post was at 07:10 PM ----------
scumpicule said:
Hello
Here we go -> https://play.google.com/store/apps/details?id=jp.susatthi.ManifestViewer
Hope that can help you
Click to expand...
Click to collapse
thank you very much :good::good::good:
Will this work on s4
Sent from my GT-I9505 using XDA Free mobile app
Anson Alocious said:
Will this work on s4
Sent from my GT-I9505 using XDA Free mobile app
Click to expand...
Click to collapse
There is no ultra power saving mode on s4
Sent from my GT-N7100 using Tapatalk
I made a quick app to easily add more apps to the upsm list. I am still testing it to make sure it is writing the list right. I will share it soon enough.
Arsaw said:
UPSM is good way to save some battery when needed, but only a very limited apps we can use under UPSM. With root access, we can add more apps support in UPSM.
Well, the whole idea of UPSM is to save battery, why on earth we want to add more apps to drain the battery? Because we can :victory:
For the start, our mod will add a few applications so you can test it out before customizing your own application list.
Apps added in our mod:
1) Camera
2) Gallery
3) Torch (included AOSP torch.apk for this feature)
4) Chrome
5) Hangout
Instruction to add more apps to UPSM
1) Download the UPSM_Add_More_Apps.zip from : http://electron-team.com/ADDONS/other/
2) Put zip file in sd card.
3) Boot in recovery and clear cache partition
4) Flash the zip file and reboot your phone
5) Boot into UPSM to test the added applications
How to add your own apps?
6) Go to system/csc and open up allowed_apps_upsm.xml with text editor
7) Add your desired applications. You need to know the application Package Name and the Main Class Name. Check the app's Android.Manifest.xml to find out.
8) Then go to phone data/data/com.sec.android.emergencylauncher/databases/ and delete EmergencyLauncherUPSM.db
9) Reboot your phone.
10) Done.
Note: Music app doesn't work in UPSM because some background services has been turn off.
Wish to have Xposed module or app to easily add more app to UPSM? Me too. Let's hope somebody could make one in future.:fingers-crossed:
Eteam
Click to expand...
Click to collapse
My S5 does not have in system/csc a file named "allowed_apps_upsm.xml". It only has: contents.db, customer.xml, default_workspace.xml, feature.xml, others.xml, and sales_code.dat. Help?!
Also will this work on a Sprint Galaxy S5? (SM-G900P)
I hope that someone will turn on music files on upsm.
hello, is it possible to have gps turned on while screen is off.
I want to run Sports Tracker in this mode, but it stops working after turning off the screen
Joe0113 said:
My S5 does not have in system/csc a file named "allowed_apps_upsm.xml". It only has: contents.db, customer.xml, default_workspace.xml, feature.xml, others.xml, and sales_code.dat. Help?!
Also will this work on a Sprint Galaxy S5? (SM-G900P)
Click to expand...
Click to collapse
if it doesnt have that file you can add it. No problem. Take one of the files published ona previous page, copy it into system/csc and give rw-r-r permissions. then reboot. It should work on all devices, including sprint. Cheers!
daxgirl said:
if it doesnt have that file you can add it. No problem. Take one of the files published ona previous page, copy it into system/csc and give rw-r-r permissions. then reboot. It should work on all devices, including sprint. Cheers!
Click to expand...
Click to collapse
Please can u post '' allowed_apps_upsm.xml '' i would try on galaxy tab s ^^
Thanks
I don't have in com.android.sec.emergencylauncher this file.......db And upsm manager don't work on omega 7.1 why ?
Obviously if you run more apps, you'll use some more power when you're using those new apps in power save mode. But will adding more to the menu use any more power while you're not using these?
What I'm really trying to establish is if there's any negative point to adding more apps in power save mode.
h3x3d said:
Obviously if you run more apps, you'll use some more power when you're using those new apps in power save mode. But will adding more to the menu use any more power while you're not using these?
What I'm really trying to establish is if there's any negative point to adding more apps in power save mode.
Click to expand...
Click to collapse
Hey mate, I think I came across something today that may answer your question.
After adding settings with UPSM manager, I went into "manage apps" and discovered that whilst in this mode, all apps are marked as "disabled" except for those that work in upsm.
Based on this observation, it seems like UPSM actually disables all apps (and by consequence their background services) to save battery, not just hiding them.
So to answer your question, I'd guess that adding more apps will not in itself cause battery drain, unless the apps have battery/ram consuming background services. Therefore my approach is to enable as few apps as I need (whatsapp, music etc), whilst leaving off apps like facebook which has notifications etc.
Hope that helps you or someone
Work with NE5?
Does this work with NE5? I can't seem to get it to work. I am stock rooted without tripping KNOX.
I don't have either of the mentioned files:
system/csc/allowed_apps_upsm.xml
data/data/com.sec.android.emergencylauncher/databases/EmergencyLauncherUPSM.db
I don't even have the data/data/com.sec.android.emergencylauncher/databases directory.
Tried using the app and that adds the system/csc/allowed_apps_upsm.xml file but it doesn't affect the available applications list in UPM mode.
link doesn't work anymore (404). can somebody upload xml file I don't have it on my S5 . Will it work on lollipop?
+1
Sent from my SM-N910T using XDA Free mobile app
Any way to disable the zooming animation when entering the lock screen? I've looked in all the settings but can't seem to find it..
Info
RNK23 said:
Any way to disable the zooming animation when entering the lock screen? I've looked in all the settings but can't seem to find it..
Click to expand...
Click to collapse
no it s system animation and without root u cannot change it
u need to have root access to use module or something like this to change this system features
:good:
RNK23 said:
Any way to disable the zooming animation when entering the lock screen? I've looked in all the settings but can't seem to find it..
Click to expand...
Click to collapse
You can you an SQL editor( I prefer SQLite editor) and go into:
data/
data/
com.android.providers.settings/
databases/
settings.db/
system/
locksreen_ripple_effect:
change the value to something other than 13 (I use 12, lol )
and save
and now zoom effect should now be gone , no need to reboot
Hope this helps
tiboric said:
You can you an SQL editor( I prefer SQLite editor) and go into:
data/
data/
com.android.providers.settings/
databases/
settings.db/
system/
locksreen_ripple_effect:
change the value to something other than 13 (I use 12, lol )
and save
and now zoom effect should now be gone , no need to reboot
Hope this helps
Click to expand...
Click to collapse
This works without rooting?
RNK23 said:
This works without rooting?
Click to expand...
Click to collapse
nooo
this edits system files so needs rot
also if rooted and installed xposed framework, use instant lock module
I recently activated the Google Assistant on my OnePlus 2. Its a little different than installing on other devices.anyways, lets get started!
**I am not responsible for any problems in your device, This is just the method I used to activate Google Assistant for Myself(and my friends,worked every time!)**
Prerequisites:
1. Installed TWRP or CWM(in recovered)
2.Rooted OP2
3.Installed ES File Explorer!
4.Installed Android 7.x ROM.
How to get started:
Download the files from here : https://www.androidfilehost.com/?w=files&flid=121914
Put All files in same folder in your phone internal memory.
Thanks to @FaserF
Now...
1.Boot to Recovery.
2.Flash the Zip GoogleAssistantVelvet.zip
3.Flash the ZipGoogleAssistantBuildProp.zip (this will install the "tweak.prop" into your build.prop)
Now boot to your device.
4.Open ES file explorer and Activate "Root Explorer".
5.Mount R/W in memory , /system directory.
Here you will find the file "build.prop"
6.Remove these lines :
ro.product.brand=OnePlus
ro.product.name=OnePlus2
7.In the place of removed lines, add this-
ro.product.model=Pixel XL
Now save the changes.
Clear Data of your Google App.
Reboot your device.(not that important)
Tap the home Button and your Google Assistant will POP UP!
Tap on Thanks if I helped you!
Does OK GOOGLE works everytime?
sushant20 said:
I recently activated the Google Assistant on my OnePlus 2. Its a little different than installing on other devices.anyways, lets get started!
**I am not responsible for any problems in your device, This is just the method I used to activate Google Assistant for Myself(and my friends,worked every time!)**
Prerequisites:
1. Installed TWRP or CWM(in recovered)
2.Rooted OP2
3.Installed ES File Explorer!
4.Installed Android 7.x ROM.
How to get started:
Download the files from here : https://www.androidfilehost.com/?w=files&flid=121914
Put All files in same folder in your phone internal memory.
Thanks to @FaserF
Now...
1.Boot to Recovery.
2.Flash the Zip GoogleAssistantVelvet.zip
3.Flash the ZipGoogleAssistantBuildProp.zip (this will install the "tweak.prop" into your build.prop)
Now boot to your device.
4.Open ES file explorer and Activate "Root Explorer".
5.Mount R/W in memory , /system directory.
Here you will find the file "build.prop"
6.Remove these lines :
ro.product.brand=OnePlus
ro.product.name=OnePlus2
7.In the place of removed lines, add this-
ro.product.model=Pixel XL
Now save the changes.
Clear Data of your Google App.
Reboot your device.(not that important)
Tap the home Button and your Google Assistant will POP UP!
Tap on Thanks if I helped you!
Click to expand...
Click to collapse
Does your camera work? I tried an other method and it messed up my camera, because it only saved a green picture.
Akilesh Akil said:
Does OK GOOGLE works everytime?
Click to expand...
Click to collapse
yes it does!
trapistasajt said:
Does your camera work? I tried an other method and it messed up my camera, because it only saved a green picture.
Click to expand...
Click to collapse
I am using FireHound 7.0 and nothing seems broken to me because of Google Assistant!
Beware if you're on AICP, this locked up my phone, had to restore my backup again. If you're on AICP, just use the other Google Assistant thread and add the entries to build.prop yourself.
I've tried flashing these two files on 3 different ROMs with pico gapps--- Official RR 6.0.1, Graraks CM14, Firehound OS 7.0 but every time, the phone gets struck at 1+ bootlogo. I don't know what's going wrong. Please help.
1 more thing, while flashing the 2nd zip, some Error 1 appears in twrp.
Edit: its working good. I just didn't downloaded that tweak.prop. Now it works flawlessly!
Thanks!✌
Does it work on marshmallow ROMs?
amitgudwill said:
Does it work on marshmallow ROMs?
Click to expand...
Click to collapse
do you even read the requirements?
Just my two cents: there's no need to do any of that really to get Google assistant to work on Android N builds.
Just make sure that you have the latest version of the Google search app, then add these two lines to your build.prop file and reboot. After that, just clear Google search's data and then open the assistant using the same shortcut that you've used to open now on tap before(long press home by default), when asked about setting up "ok Google" select "I'll do it later"(to avoid crashes).
That's it
sar12330 said:
Just my two cents: there's no need to do any of that really to get Google assistant to work on Android N builds.
Just make sure that you have the latest version of the Google search app, then add these two lines to your build.prop file and reboot. After that, just clear Google search's data and then open the assistant using the same shortcut that you've used to open now on tap before(long press home by default), when asked about setting up "ok Google" select "I'll do it later"(to avoid crashes).
That's it
Click to expand...
Click to collapse
can u please explain which two lines to add? There is just one single line which is to be added in the build.prop.
The lines are:
ro.product.model=Pixel XL
ro.opa.eligible_device=true
After putting these in the build.prop and rebooting, clear Google search's data and the assistant should work
not working on Halogen OS 7.0
Just wanted to comment on the OP.
Adding the two lines works. No need to flash anything or delete any lines. It works just as on any other device.
At least on CM14/.1
Tried to activate assistant by put these two lines into build.prop... Seems to be OK but every time I finish voice recognition setup for "OK Google" and want to try it, it starts the setup again...
Any solution?
well can anyone try to help me ?
Resolved
vergilbt said:
Tried to activate assistant by put these two lines into build.prop... Seems to be OK but every time I finish voice recognition setup for "OK Google" and want to try it, it starts the setup again...
Any solution?
Click to expand...
Click to collapse
It's normal, voice recognition isn't working with this method.
@casual_kikoo
Thanks a lot for your information... Could you point me to the right way? The way from op?
vergilbt said:
@casual_kikoo
Thanks a lot for your information... Could you point me to the right way? The way from op?
Click to expand...
Click to collapse
In fact, no way for now.
sushant20 said:
I recently activated the Google Assistant on my OnePlus 2. Its a little different than installing on other devices.anyways, lets get started!
**I am not responsible for any problems in your device, This is just the method I used to activate Google Assistant for Myself(and my friends,worked every time!)**
Prerequisites:
1. Installed TWRP or CWM(in recovered)
2.Rooted OP2
3.Installed ES File Explorer!
4.Installed Android 7.x ROM.
How to get started:
Download the files from here : https://www.androidfilehost.com/?w=files&flid=121914
Put All files in same folder in your phone internal memory.
Thanks to @FaserF
Now...
1.Boot to Recovery.
2.Flash the Zip GoogleAssistantVelvet.zip
3.Flash the ZipGoogleAssistantBuildProp.zip (this will install the "tweak.prop" into your build.prop)
Now boot to your device.
4.Open ES file explorer and Activate "Root Explorer".
5.Mount R/W in memory , /system directory.
Here you will find the file "build.prop"
6.Remove these lines :
ro.product.brand=OnePlus
ro.product.name=OnePlus2
7.In the place of removed lines, add this-
ro.product.model=Pixel XL
Now save the changes.
Clear Data of your Google App.
Reboot your device.(not that important)
Tap the home Button and your Google Assistant will POP UP!
Tap on Thanks if I helped you!
Click to expand...
Click to collapse
The build.prop uses UNIX endlines. Does es even support those?
1. Go to /system/usr/keylayout
2. Rename the Generic.kl to Generic.txt
3. Open this file with an text editor*
4. Search for WINK and replace it with CAMERA
5. Rename it back to Generic.kl (otherwise you won't be able to press any hardware button after reboot
6. Restart your device
you can change Bixby Button to several things but i prefer CAMERA on this great note8 .
There's Root available?
Root is available via Magisk and Super SU. Exynos only though.
Magisk:
https://forum.xda-developers.com/galaxy-note-8/how-to/n950fd-root-via-magisk-t3673451
SuperSU:
https://forum.xda-developers.com/galaxy-note-8/how-to/guide-how-to-root-note8-efs-backup-t3677038
Quick question, the unlocked us version is exynos or snapdragon?
Sent from my iPhone using Tapatalk
tanquef said:
Quick question, the unlocked us version is exynos or snapdragon?
Click to expand...
Click to collapse
The US is a Snapdragon variant.
root is coming, it always does....
Sent from my SM-N950U1 using Tapatalk
Bofahad said:
1. Go to /system/usr/keylayout
2. Rename the Generic.kl to Generic.txt
3. Open this file with an text editor*
4. Search for WINK and replace it with CAMERA
5. Rename it back to Generic.kl (otherwise you won't be able to press any hardware button after reboot
6. Restart your device
you can change Bixby Button to several things but i prefer CAMERA on this great note8 .
Click to expand...
Click to collapse
Can't you just edit it with it's name as is?
Kalm_Traveler said:
Can't you just edit it with it's name as is?
Click to expand...
Click to collapse
What?
Bofahad said:
What?
Click to expand...
Click to collapse
I'm asking why it is necessary to change the file name before editing. Can't you just open it in a text editor and save it?
Kalm_Traveler said:
I'm asking why it is necessary to change the file name before editing. Can't you just open it in a text editor and save it?
Click to expand...
Click to collapse
Text editors can not open files with .kl extention
hello!
what else are options? camera, and?
second question is also an offscreen funtion available? all the bixby remappers work when screen is on.
thx
gepataki said:
hello!
what else are options? camera, and?
second question is also an offscreen funtion available? all the bixby remappers work when screen is on.
thx
Click to expand...
Click to collapse
Hi,
Take a look here: https://forum.xda-developers.com/galaxy-s8+/how-to/root-remap-bixby-button-o-app-t3601061.
Bofahad said:
1. Go to /system/usr/keylayout...
Click to expand...
Click to collapse
I've been looking how to apply theses steps o a Samsung Galaxy with Lineage OS.
You can follow the steps as described in the post, but you won't find button 703 on the "Generic.kl" file. You have to search for a file named "gpio_keys.kl" on the same folder:
/root/system/usr/keylayout/
Click to expand...
Click to collapse
Also, I've found other commands to try if you wish:
APP_SWITCH - Recent apps button
ASSIST - Google Assistant (with item display on the screen)
CALCULATOR - Open default calculator app
CALENDAR - Open default calendar
CALL - Open default call app
CAMERA - Open camera
CONTACTS - Open default contacts app
EXPLORER - Favorite internet browser
HOME - Homebutton
MEDIA_PLAY_PAUSE - Play pause media
MESSAGE - Default messenger
MUSIC - starts your favorite music player
POWER - Power menu
QPANEL_ON_OFF - Notification area
SYSRQ - Take a screenshot
VOICE_ASSIST - Google Assistant
VOLUME_DOWN - Sets volume down
VOLUME_MUTE - Volume media (set default media volume in phone setting)
VOLUME_UP - Sets volume up
All the steps described above have worked for me on a Galaxy S8 and a Galaxy S9+, with Lineage OS 15.1 and Lineage OS 16.
When I set password or PIN code, lock screen still unlocks by swiping and when I want to set new code it asks old one and when I enter old it says wrong code.
Ayano_+ said:
When I set password or PIN code, lock screen still unlocks by swiping and when I want to set new code it asks old one and when I enter old it says wrong code.
Click to expand...
Click to collapse
I have same problem, can't set face recognition, iris or fingerprint. Flashed new rom, restored stuff, can't set biometrics, reflashed without restoring system settings, only contacts and few apps, set new password, later when trying to set up fingerprints, it keep asking for password, and then tells me password is wrong.
opiumdance said:
I have same problem, can't set face recognition, iris or fingerprint. Flashed new rom, restored stuff, can't set biometrics, reflashed without restoring system settings, only contacts and few apps, set new password, later when trying to set up fingerprints, it keep asking for password, and then tells me password is wrong.
Click to expand...
Click to collapse
Hope, someone will find fix or maybe new security patch will help. When did your problem start? After what?
Fix
I fixed this issue.
1. Go to TWRP
2. Mount EFS
3. Go to advanced
3. Open file manager
4. Go to efs folder
5. Then to TEE folder
6. And delete all files from TEE folder
7. Restart
P.S. I am not sure if it will help everyone
Thanks!! You just saved my day.
I'm using s9+ with Andriod 10
Ayano_+ said:
I fixed this issue.
1. Go to TWRP
2. Mount EFS
3. Go to advanced
3. Open file manager
4. Go to efs folder
5. Then to TEE folder
6. And delete all files from TEE folder
7. Restart
P.S. I am not sure if it will help everyone
Click to expand...
Click to collapse
Nice
Deleted member 9896136 said:
Fix
I fixed this issue.
1. Go to TWRP
2. Mount EFS
3. Go to advanced
3. Open file manager
4. Go to efs folder
5. Then to TEE folder
6. And delete all files from TEE folder
7. Restart
P.S. I am not sure if it will help everyone
Click to expand...
Click to collapse
bro thank you so much you saved my day appreciate it.