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
This will work for the S7 and S7 Edge. In fact it will work for all Android Devices on Jellybean and higher.
This will NOT trip Knox.
You can change DPI without root but will need to use adb on a computer.
As some of you may be aware, changing dpi in build.prop does not work, therefore I have also now included a method to change DPI with root, without the need of a computer. Scroll down to see how to do this.
Since the April update, Samsung have included a menu in the settings screen which allows you to change between 'Standard' (640 DPI) and 'Condensed' (560 DPI). If you have not had this update, you can still access this menu using this app.
(AT&T users have confirmed that this menu is not available in the display menu but still available via the the app route.)
If you would like a different DPI other than 640 or 560, please follow the instructions below:
Change DPI without root (Requires Computer):
To do this, follow the steps below.
The first thing you need to do is to install adb. The quickest way to do this is using the adb installer. You can download it from Here. If you follow the steps correctly in that thread, you should have no issues installing adb.
Now you will need to enable USB Debugging. [If you have 'My Knox' installed, you will not be able to do this so you will need to uninstall 'My Knox' First otherwise USB debuggin will be greyed out.]. Go into Settings > About Device > Software Info and keep tapping Build Number until Developer Options is enabled. Then go back into the Settings screen and go into Developer Options (located just above 'About Device'). You should see USB Debugging, turn the slider to on.
Connect your S7E to your computer. You will see a notification asking for you to Allow USB degugging for that computer, select 'OK'.
Now open Command Prompt (CMD) on your computer. (If you're not sure how to do this, Click Here to find out how).
First thing to check is if adb can detect the device, so type the following command in CMD and press enter...
Code:
adb devices
If this command shows the device (a line of random letters and numbers), then it has successfully detected your device. If nothing shows, then it cannot detect the device and you have either not enabled USB debugging, not allowed USB Debugging for this computer (as per the prompt when plugging it in)or the drivers have not been installed. (Most recent Windows will automatically install the Drivers, but if you are having Driver issues, then install Kies, connect the device to Kies to allow the drivers to install, then remove device from the computer, disable Kies then start again from Step 3).
If the device is detected in adb, go ahead and enter the following command to change your DPI. 560 is the most commen used but you can change this to anything you like (I find 520 to be the best).
Code:
adb shell wm density 560 && adb reboot
Your S7E should now reboot and the new DPI will be applied. To confirm this, install DPI Checker from the Play store. The prop file will still show the default DPI of 640 so ignore this.
If you want to revert back to the default DPI, enter the following command:
Code:
adb shell wm density 640 && adb reboot
Change DPI with root (No computer required):
1. Download a Terminal app (such as this one) and open the app.
2: Type the following:
Code:
su
Then tap enter. This will prompt root permission, make sure you allow permission
Code:
wm density 560 && reboot
Change 560 to your prefered DPI.
Then tap enter.
3. Your phone will reboot and when booted it will have the new set DPI.
4. To change back to stock DPI, use the following in Terminal:
Code:
wm density 640 && reboot
FAQ:
Will this affect Samsung Pay?
No. But I recommend you make sure the initial Samsung Pay set up is complete before changing DPI as some people have reported that the initial set up does not work after changing DPI. After that it works fine.
Will this affect Android Pay?
Yes. You will not be able to use Android Pay after changing DPI
Will this affect the scaling of Samsung apps?
The camera shifts slightly to the left.
Using the stock wallpaper will leave a blue gap at the bottom of the lock/home screen.
The Edge screen will have a small gap at the bottom.
Other than this, I have not noticed any other scaling issues (see screenshots below).
Screenshots:
Camera:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Other Samsung Apps
If you have any issues or questions feel free to ask me and I will be happy to help.
If you notice any mistakes or know any ways this can be improved, please let me know and I will update the guide.
Thanks!! Wonder though why it breaks Android pay.
If you switch the dpi back does it fix android pay?
Nice! Thank you!
Does this change resolution to?
People who lowered the dpi and res in their s6 got faster benchmarks and cooler phones while playing 3D games. And potentially gaining battery life.
Will it effect S7 in the same way? What would be an optimal DPI if you want 1080 resolution?
It wont work with apps like Swiftkey though since it doesn't support multi dpi.. for that root is needed.
Mr Sliff said:
If you switch the dpi back does it fix android pay?
Click to expand...
Click to collapse
I've switched mine back and AP still does not work for me, and my camera app is still shifted. I think I may need to reset.
Edit: It would not reset the DPI using the adb reset command. I had to specifically rewrite it back to 640 to get everything back to normal.
Mr Sliff said:
If you switch the dpi back does it fix android pay?
Click to expand...
Click to collapse
I've never used it myself but other users have advised me that when they reset the DPI, it worked as Normal.
varun.gid said:
It wont work with apps like Swiftkey though since it doesn't support multi dpi.. for that root is needed.
Click to expand...
Click to collapse
Not true. I use SwiftKey and it works perfectly after changing DPI.
ImSoHungry said:
I've switched mine back and AP still does not work for me, and my camera app is still shifted. I think I may need to reset.
Click to expand...
Click to collapse
Weird. Did you reset the DPI as per the guide? Sounds like it hasn't actually gone back to default. Try again.
Sent from my SM-G935F using Tapatalk
CuBz90 said:
Weird. Did you reset the DPI as per the guide? Sounds like it hasn't actually gone back to default. Try again.
Click to expand...
Click to collapse
Yea, I went back and had to rewrite it back to 640. The
Code:
adb shell size reset && adb reboot
command does not stick.
ImSoHungry said:
Yea, I went back and had to rewrite it back to 640. The
Code:
adb shell size reset && adb reboot
command does not stick.
Click to expand...
Click to collapse
Are you sure you used
Code:
adb shell wm size reset && adb reboot
Looks like you missed the 'wm' part.
If it still doesn't work, try this one...
Code:
adb shell wm density reset && adb reboot
Sent from my SM-G935F using Tapatalk
Samsung pay does NOT work after changing DPI on GS7 Edge
i set up Samsung pay on both a S7 Edge and S6 Edge+. It worked prior to the changing the DPI using the method below. I changed my DPI using the method below on BOTH a S7 Edge and S6 Edge +. In both cases the Samsung Pay does not work with reduced DPI. I tried 480, 500, 520. The problem is the "radiating" bar above the credit card in Samsung pay never activates.... ever. I factory reset the device back to normal resolution (640) and voila', Samsung pay worked... I'm not sure why the reduced DPI would impact SamsungPay operation - any advice?
Ereeser said:
i set up Samsung pay on both a S7 Edge and S6 Edge+. It worked prior to the changing the DPI using the method below. I changed my DPI using the method below on BOTH a S7 Edge and S6 Edge +. In both cases the Samsung Pay does not work with reduced DPI. I tried 480, 500, 520. The problem is the "radiating" bar above the credit card in Samsung pay never activates.... ever. I factory reset the device back to normal resolution (640) and voila', Samsung pay worked... I'm not sure why the reduced DPI would impact SamsungPay operation - any advice?
Click to expand...
Click to collapse
Same here, SP working prior to DPI change now at 520 and it's greyed out where it says to enter the PIN or use finger print. Thoughts?
Vexamus said:
Same here, SP working prior to DPI change now at 520 and it's greyed out where it says to enter the PIN or use finger print. Thoughts?
Click to expand...
Click to collapse
Strange. This seems to only me the case on the S7. Everyone reported it working fine on the S7E
Sent from my SM-G935F using Tapatalk
what does changing DPI give you?
Heads up, if you do a DPI that's under 560 it will prevent samsung pay from working.
Check this out!
Fixed all of my (minimal) scaling issues.
NATIVE scaling.
A_N_D_R_E said:
Check this out!
Fixed all of my (minimal) scaling issues.
NATIVE scaling.
Click to expand...
Click to collapse
very cool that it's native. anyone find a fix for the samsung weather widget being a bit cut off by this? also will changing DPI affect battery?
A_N_D_R_E said:
Check this out!
Fixed all of my (minimal) scaling issues.
NATIVE scaling.
Click to expand...
Click to collapse
I seen this earlier. It's very promising. Hopefully Samsung are going to eventually give us this option via settings.
Sent from my SM-G935F using Tapatalk
A_N_D_R_E said:
Check this out!
Fixed all of my (minimal) scaling issues.
NATIVE scaling.
Click to expand...
Click to collapse
yea but this only works when you're in nova launcher, when you switch to your regular launcher everything's back to default
konoplya said:
yea but this only works when you're in nova launcher, when you switch to your regular launcher everything's back to default
Click to expand...
Click to collapse
Not correct. Nova is just used to get into this menu. The scaling is across the whole device.
Sent from my SM-G935F using Tapatalk
CuBz90 said:
Not correct. Nova is just used to get into this menu. The scaling is across the whole device.
Sent from my SM-G935F using Tapatalk
Click to expand...
Click to collapse
not on my device it isn't
Hi,
my problem is - I have installed ScreenShift, then changed resolution and overscale and after reboot I can;t use my screen because of overscan. Tried steps provided by the author of the app, tried adb over twrp recovery (after typing command adb shell wm overscan reset I receive this error "CANNOT LINK EXECUTABLE: cannot locate symbol "stderr" referenced by "app_process"... page record for 0xb6f0404c was not found (block_size=32)"). Tried changing density inside build.prop and nothing has changed. I tried to figure out where the overscan settings are stored but with no luck.
My phone is Galaxy S4 Value Edition with Unofficial CM13 (latest from 11.09.2016) and TWRP 3.0.0.
Hi all,
I had previously used an ADB command to remove my navigation and use swipe gestures instead.
I remember typing this following command into terminal on Mac:
adb shell wm overscan 0,0,0,-168
Now I've updated my phone to One UI, and my phone is no longer functioning correctly. My keyboard is not showing the spacebar, and I have no idea how to reverse the above command.
I really need help with this, preferably explained simply as I'm not tech savvy at all.
Thank you all!
Try the command:
adb shell wm overscan 0,0,0,0
Alternatively you can try:
adb shell wm overscan reset
Should restore you back to default
I assume you were reading from this thread here?:
https://forum.xda-developers.com/galaxy-s8/how-to/remove-oreo-navbar-completely-t3772217
You can also just use the XDA navigation gesture app or gesture control app from the play store to accomplish what you wish to do.
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 ?