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 ?
Related
Hi
I've made the update Android Wear 2.0 on my LG G Watch R (through the Play Store).
However, i really do not like the new interface and how notifications are now displayed.
Is it possible de downgrade Android Wear to old version 1.5? How should I do that?
Thanks for your help, have a nice day.
nicodvt said:
Hi
I've made the update Android Wear 2.0 on my LG G Watch R (through the Play Store).
However, i really do not like the new interface and how notifications are now displayed.
Is it possible de downgrade Android Wear to old version 1.5? How should I do that?
Thanks for your help, have a nice day.
Click to expand...
Click to collapse
you can flash stock image via fastboot https://forum.xda-developers.com/g-watch-r/development/fastboot-zip-factory-images-t3405311
Thanks @ingbrzy for the advise, I have not found any other easiest solution to downgrade Android Wear 2.0 to Android Wear 1.5.
If it can help others, thi is how I flashed a stock image with Android Wear 1.5 on my LG G Watch R:
Enabled "Developer tools" on my watch
Connected my watch to my computer
Unlocked my bootloader with WinDroid Toolkit
After selected my device, on first screen: "Unlock Bootloader"
Downloaded and installed ADB Installer (v1.4.2)
Downloaded stock images of build "M1D65H" from this topic
Inspirated by this guide, opened a command line prompt and entered the following commands
Code:
fastboot -w
Code:
fastboot flash boot M1D65H_boot.img
Code:
fastboot flash recovery M1D65H_recovery.img
Code:
fastboot flash system M1D65H_system.img
Rebooted my watch with command
Code:
fastboot reboot
That's finished, my watch was again on Android Wear 1.5 <3
After having downgraded, has anyone managed to get rid of the update message?
midafaya said:
After having downgraded, has anyone managed to get rid of the update message?
Click to expand...
Click to collapse
Yeap, I rebooted my watch and had no more the update message.
nicodvt said:
[*] That's finished, my watch was again on Android Wear 1.5 <3
[/LIST]
Click to expand...
Click to collapse
Hi Nicodvt. Thank you for this good summary.
Unfortunatly, our friends from Google have perhaps not performed a lot for the Android Wear 2.0 new features implementation but they are really good in the development of their OTA procedure!
After the downgrade to AW1.5, even after the installation of the Android Wear 1.5 apk smartphone application and settings in Playstore not to automatically update the applications, the "always on" notification on the watch to install the new version of Android Wear 2.0 appeared one day after the downgrade....
See post below to remove the notification.
I have done tried this, not really sure what I am disabling though, but those services look like thay could bring trouble ... We'll see :silly:
Code:
laptop$ adb shell
[email protected]:/ $ su
[email protected]:/ # pm disable com.google.android.gms/.update.SystemUpdateService
Component {com.google.android.gms/com.google.android.gms.update.SystemUpdateService} new state: disabled
[email protected]:/ # pm disable com.google.android.gsf/.update.SystemUpdateService
Component {com.google.android.gsf/com.google.android.gsf.update.SystemUpdateService} new state: disabled
adlx.xda said:
I have done tried this, not really sure what I am disabling though, but those services look like thay could bring trouble ... We'll see :silly:
Code:
laptop$ adb shell
[email protected]:/ $ su
[email protected]:/ # pm disable com.google.android.gms/.update.SystemUpdateService
Component {com.google.android.gms/com.google.android.gms.update.SystemUpdateService} new state: disabled
[email protected]:/ # pm disable com.google.android.gsf/.update.SystemUpdateService
Component {com.google.android.gsf/com.google.android.gsf.update.SystemUpdateService} new state: disabled
Click to expand...
Click to collapse
Ah, that seems to work (for now)!
It removed the notification (after applying and rebooting) and has not reappeared for 45 minutes even after a few reboots.
I confirm these 2 commands seem to remove the upgrade notification.
For information, the creation of an empty update.zip file in the /cache/ folder was not enough and the upgrade notification appeared spontaneously one day later.
Thanks
It's great, I also want to come back the ver 1.5, but i dont have an experience in this field. I have problem in step 2 and try to install the ADT,... but it doesnt work very well. Can I contact to you via facebook or skype? Thank you.
nicodvt said:
Thanks @ingbrzy for the advise, I have not found any other easiest solution to downgrade Android Wear 2.0 to Android Wear 1.5.
If it can help others, thi is how I flashed a stock image with Android Wear 1.5 on my LG G Watch R:
Enabled "Developer tools" on my watch
Connected my watch to my computer
Unlocked my bootloader with WinDroid Toolkit
After selected my device, on first screen: "Unlock Bootloader"
Downloaded and installed ADB Installer (v1.4.2)
Downloaded stock images of build "M1D65H" from this topic
Inspirated by this guide, opened a command line prompt and entered the following commands
Code:
fastboot -w
Code:
fastboot flash boot M1D65H_boot.img
Code:
fastboot flash recovery M1D65H_recovery.img
Code:
fastboot flash system M1D65H_system.img
Rebooted my watch with command
Code:
fastboot reboot
That's finished, my watch was again on Android Wear 1.5 <3
Click to expand...
Click to collapse
dungkr89 said:
It's great, I also want to come back the ver 1.5, but i dont have an experience in this field. I have problem in step 2 and try to install the ADT,... but it doesnt work very well. Can I contact to you via facebook or skype? Thank you.
Click to expand...
Click to collapse
Check your private message @dungkr89 if you want to reach me.
Hi,
If you have some difficulties, I made this memo for me.
Downgrade LG G Watch R and block OTA upgrades
---------------------------------------------
Prepare the PC
--------------
Install adb-setup-1.4.3.exe on the PC
Place in folder (C:/wear for example) all the necessary files :
- M1D65H_boot.img
- M1D65H_recovery.img
- M1D65H_boot_system.img
- SuperSU-v2.78_Lg-G-Watch-R.zip
- twrp-3.0.0-0-Lg-G-Watch-R.img
Prepare the watch and smartphone
--------------------------------
On the smartphone, dissociate and restore factory settings on the watch.
Remove ALL applications on the smartphone in relation with the wear watch (excepted Android wear). This is usefull to avoid a long installation with risk of applications not compatible with the Android Wear version which will be installed on the watch.
Reassociate the watch with the smartphone
On the watch :
Activate developper mode (click 7 times on the build number in version menu)
Then in the developper menu, activate adb degug
Connect the watch to the pc via usb
On the PC :
DOS commands invite
Change directory (cd) to point he folfer where are located the .img files.
Type:
adb devices
// The watch device is present and ready
// Switch the watch in fastboot mode
adb reboot bootloader
adb devices
// If the watch is seen oem locked you have to type:
fastboot oem unlock
// If the watch has not been restored (I recommend to do it before via the smartphone)
//fastboot format userdata
//fastboot format cache
//fastboot format system
Send the firmware to the watch
------------------------------------
fastboot flash boot M1D65H_boot.img
fastboot flash recovery M1D65H_recovery.img
fastboot flash system M1D65H_system.img
Restart the watch via the screen menu
ROOT the watch
--------------
adb reboot bootloader
fastboot flash recovery twrp_xxx.img
//fastboot boot twrp_xxx.img (if command below is rejected)
adb push SuperSU_xxx.zip /sdcard/
// From the watch screen, by typing on the screen and following instructions, move to sdcard folder and install from zip the SuperSU_xxx.zip application
Then, when the patch has been installed (quite long), the watch has restarted. Reconnect to the watch via the PC and adb commands
Deactivate OTA
--------------
adb reboot bootloader
adb devices //to make sure your watch is connected
adb shell
> su
> pm disable com.google.android.gms/.update.SystemUpdateService
> pm disable com.google.android.gsf/.update.SystemUpdateService
> exit
Before to reassociate the watch with the smartphone, eventually, remove the Android Wear application on the smartphone and reinstall the Android Wear V1.5.apk on the smartphone.
Reassociate the watch with the smartphone.
Thanks for this thread! I am having issue getting SU in cmd. I have installed 3 different TWRP and 3 different SuperSU.zip trying to get it to work. I can't seem to get any of them to execute su commands. When trying I get a FC on SuperSU on watch, and adb does nothing after
- adb shell
- su
- then nothing happens, and I eventually get SuperSU FC on watch.
Thanks in advance for the help.
Thanks both for the re-flash guide and the commands for disabling the update service. Had a problem not finding appropriate SU and TWRP images, but after finding them I'm finally free of the damn 2.0 and the update notification too.
SU: SuperSU-2.78-wear.zip
TWRP: twrp-3.0.0-0-lenok+squashfs.img
I did not check any other root-needing apps, and as far as I'm concerned, I'm done with updates for the lifetime of this watch...
nagi603 said:
Thanks both for the re-flash guide and the commands for disabling the update service. Had a problem not finding appropriate SU and TWRP images, but after finding them I'm finally free of the damn 2.0 and the update notification too.
SU: SuperSU-2.78-wear.zip
TWRP: twrp-3.0.0-0-lenok+squashfs.img
I did not check any other root-needing apps, and as far as I'm concerned, I'm done with updates for the lifetime of this watch...
Click to expand...
Click to collapse
That's the su and twrp I have installed on my watch at this time, I am not able to get su commands to execute. Is there something else that needs to be done after installing these? Thanks.
I want to get rid of the automatic upgrade to AW 2.0, so I want to apply the recipe you have kindly shared, but I don´t know how to do it because it is my first time with ADB commands.
I have already ADB installed and USB debugging enabled. I can type "adb devices" and my watch is listed.
The question is how to apply the (two?) commands you suggest.
- Should I type "laptop$ adb shell" ??
- At the $ prompt I have tryed to type "su" but get an error.
- Also: the two commands are "one single line" each, like "...systemUpdateService Component ....", or they are two lines each command?
- Should the watch be rooted to do this ?
Thank you very much.
PD: I have flashed my watch back to AW 1.5 with no problems, using the instructions given in this link:
https://forum.xda-developers.com/g-watch-r/general/andorid-wear-2-0-t3382032/page23
adlx.xda said:
I have done tried this, not really sure what I am disabling though, but those services look like thay could bring trouble ... We'll see :silly:
Code:
laptop$ adb shell
[email protected]:/ $ su
[email protected]:/ # pm disable com.google.android.gms/.update.SystemUpdateService
Component {com.google.android.gms/com.google.android.gms.update.SystemUpdateService} new state: disabled
[email protected]:/ # pm disable com.google.android.gsf/.update.SystemUpdateService
Component {com.google.android.gsf/com.google.android.gsf.update.SystemUpdateService} new state: disabled
Click to expand...
Click to collapse
[/COLOR]
paggps said:
I want to get rid of the automatic upgrade to AW 2.0, so I want to apply the recipe you have kindly shared, but I don´t know how to do it because it is my first time with ADB commands.
I have already ADB installed and USB debugging enabled. I can type "adb devices" and my watch is listed.
The question is how to apply the (two?) commands you suggest.
- Should I type "laptop$ adb shell" ??
- At the $ prompt I have tryed to type "su" but get an error.
- Also: the two commands are "one single line" each, like "...systemUpdateService Component ....", or they are two lines each command?
- Should the watch be rooted to do this ?
Thank you very much.
PD: I have flashed my watch back to AW 1.5 with no problems, using the instructions given in this link:
https://forum.xda-developers.com/g-watch-r/general/andorid-wear-2-0-t3382032/page23
I have done tried this, not really sure what I am disabling though, but those services look like thay could bring trouble ... We'll see :silly:
Click to expand...
Click to collapse
The commands are single lines, and it will require root. Make sure you use twrp listed above, and super su 2.78 for wear, also listed above.
It's clear that the downgrade to AW1.5 is quite easy. However, it's less obvious to block the OTA!
For that, it's mandatory to root the Watch and I didn't find a clear notice to do it. After many atempts, I did it without clearly understand how I made it!!!! But it's done, and the upgrade notification has disappeared.
I wrote my onwn notice (in case I want to try again in few months a new attempt to test for instance the next AW2.1...) here.
Somebody in this forum could write a full clean procedure for newbie with all the links to do the downgrade and OTA disabling in one shot with a 100% success.
nicodvt said:
Thanks @ingbrzy for the advise, I have not found any other easiest solution to downgrade Android Wear 2.0 to Android Wear 1.5.
If it can help others, thi is how I flashed a stock image with Android Wear 1.5 on my LG G Watch R:
Enabled "Developer tools" on my watch
Connected my watch to my computer
Unlocked my bootloader with WinDroid Toolkit
After selected my device, on first screen: "Unlock Bootloader"
Downloaded and installed ADB Installer (v1.4.2)
Downloaded stock images of build "M1D65H" from this topic
Inspirated by this guide, opened a command line prompt and entered the following commands
Code:
fastboot -w
Code:
fastboot flash boot M1D65H_boot.img
Code:
fastboot flash recovery M1D65H_recovery.img
Code:
fastboot flash system M1D65H_system.img
Rebooted my watch with command
Code:
fastboot reboot
That's finished, my watch was again on Android Wear 1.5 <3
Click to expand...
Click to collapse
Hi,
Using you guide to go back to 1.5 on g watch r but im stuck on step 6......
Only thing i can do in adb i type Y and nothing else?
Hi,
I try follow your steps, everything seems to be fine. But after last command 'fastboot reboot' I am still booting to fastboot. Please do you know what can be wrong here?
Thanks
Dear Sirs
It has been almost 2 years since I got my Nexus 6P, and I always disable the navigation bar for a better usage. Before Oreo I added 'qemu.hw.mainkeys = 1' on Build Pro file via root file explorer. But it no longer worked, If I did, the system will collapse and I have to reflash the system. So is there any new way to disable the navigation entirely on Oreo.
Many thanks.
Best Regards
ChaoChao
I am interested in auto hiding the nav keys. I had a method that worked, but had phone replaced last week, and the upgrade to OREO. I had tried using the adb command:
adb shell settings put global policy_control immersive.navigation=*
But this command returns an error about Failed executing settings. ''
I have tried Tiles, but that has some annoying lag.
dratsablive said:
I am interested in auto hiding the nav keys. I had a method that worked, but had phone replaced last week, and the upgrade to OREO. I had tried using the adb command:
adb shell settings put global policy_control immersive.navigation=*
But this command returns an error about Failed executing settings. ''
I have tried Tiles, but that has some annoying lag.
Click to expand...
Click to collapse
So sad. thanks for your help though.
dratsablive said:
I am interested in auto hiding the nav keys. I had a method that worked, but had phone replaced last week, and the upgrade to OREO. I had tried using the adb command:
adb shell settings put global policy_control immersive.navigation=*
But this command returns an error about Failed executing settings. ''
I have tried Tiles, but that has some annoying lag.
Click to expand...
Click to collapse
Try issuing the command
adb shell settings list global
to see if that setting still exists.
stevemw said:
Try issuing the command
adb shell settings list global
to see if that setting still exists.
Click to expand...
Click to collapse
I was trying to execute the command
adb shell settings put global policy_control immersive.navigation=*
from a terminal on the phone, but executing this command on my laptop while connected to phone worked
Anyone can please help..!!!!
In android 8.0 (oreo),i am unable to hide soft keys using "qemu.hw.mainkeys=1".since after this my phone starts doing data factory reset,next time it boots.
I tried immersive mode but soft keys alwayas pops up while using keyboard.
Also tried themer.zip from some xda link,it does hide the soft keys but swipe at bottom where softkeys are seems laggy while performing swipe action in LMT launcher.
There's an app called custom navigation bar, you can try it out, after you did your setup you can even uninstall it.
i install custom navigation bar app,but it failed compatibilty test,what to do now???
I dont want to hide the nav bar. I want to completely disable it so it wont pop up at all anywhere. I'll be using swipe navigation.
lemonspeakers said:
I dont want to hide the nav bar. I want to completely disable it so it wont pop up at all anywhere. I'll be using swipe navigation.
Click to expand...
Click to collapse
I want to disable it as well. Pie Control is great.
Any solution yet to disable the navigation bar on Oreo 8.x?
phedoreanu said:
I want to disable it as well. Pie Control is great.
Any solution yet to disable the navigation bar on Oreo 8.x?
Click to expand...
Click to collapse
If you are rooted stock Feb update you can flash this. A restore zip should be created in a folder called ozop on your sdcard.
Hey there guys,
i was implementing the full screen apps ADB cmd and all was good, got a little to confident and went to the swapping nav buttons around and put in this code
adb shell settings secure sysui_nav_bar "space,recent;home;back,space"
instantly get a message saying "system Ui has stopped"
now screen is just blank.
Please help get my launcher....to launcher again
Thank you in advance!
Droidsaurusrex said:
Hey there guys,
i was implementing the full screen apps ADB cmd and all was good, got a little to confident and went to the swapping nav buttons around and put in this code
adb shell settings secure sysui_nav_bar "space,recent;home;back,space"
instantly get a message saying "system Ui has stopped"
now screen is just blank.
Please help get my launcher....to launcher again
Thank you in advance!
Click to expand...
Click to collapse
This works:
adb shell settings put secure sysui_nav_bar "space,recent;home;back,space”
You did not add the "put".
After many sleepless nights, I found solution.
As we don't have in our stock ROMs System UI tuner, we can do this even without root.
First, you'll need ADB, USB debugging ON and Samsung Drivers.
ADB:
- https://dl.google.com/android/repository/platform-tools-latest-windows.zip
- https://forum.xda-developers.com/showthread.php?p=48915118#post48915118
Turn on usb debugging from developer menu (tap build number 7 times to show developer settings menu)
Samsung Drivers
- http://www.devfiles.co/download/AbRa7wHc/SAMSUNG_USB_Driver_for_Mobile_Phones.exe
Connect your device via USB.
Open terminal (command prompt) inside ADB folder (hold shift and mouse right click on blank space)
write :
Code:
adb devices
You should see your phone listed as numbers. After that write:
Code:
adb shell settings put global heads_up_notifications_enabled 0
Restart your phone. Now your heads up notification nightmare has gone.
I FOUND A SOLUTION WITHOUT HAVING TO INSTALL ANY EXTRA APPS!
So we have all been getting the annoying heads up notifications that we don't want appearing on our phone when it's unlocked right?! Well I found a solution after playing round with my phone. First I changed the notification settings in my apps for example WhatsApp, Facebook messenger etc by going to settings > notifications > select each app you want to stop heads up from > allow notifications > show silently. Toggle this to on.
Now wait I've not finished, the go back into settings > accessibility > notification reminder and turn this on. Then turn sound on and vibrate on and select the apps you wish to receive notifications from. Then there you have it , this stops the heads up but then reminds you 1 minute later that you have a notification! I'm sure a 1 minute wait won't hurt to stop those heads up!
Yesterday I was searching a solution for my Note 5 and I didn't notice that it was the S7 edge forum.
I follow the tutorial step by step and it works very well too on my Note 5 SM-N920C NRD90M.N920CXXS4CRD1 (April 2018 release).
However, I do not know how to use this: https://dl.google.com/android/repository/platform-tools-latest-windows.zip , what is it?
In my case I use the other link for ADB installation.
P.D.: may someone put this tutorial in Note 5 forum too? I think it will be useful.
Great, except your phone then beebs ever minute until you review the notification - which can be incredibly annoying.
Thank you for this!
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