I've recently faced a terrible and annoying situation and as I found also the solution I've wanted to share it with you.
After coming on and off from Custom ROMS I was in front of the situation that the Blue Light Filter was automatically coming ON even with reading mode completely de-activated from its submenu.
Usually got itself activated on white pages when scrolling web pages without any action from my side. Temporary solution was to manually activate and de-activate the Reading Mode and for a short period the the Blue Filter was de-activated until the first wihte page opened.
I can tell you that this yellow light it's very annoying in the middle of the day.
Tried several solution presented like:
- Factory Reset - no success. It works only if you don't set-up your previous back-ups on your phone, but this is no viable solution for me;
- tried also the solution with Google Play Books - no success;
I remembered that I came from an Realme device (that I regret selling TBH) that had a similar issue inherited from an Oneplus devices, and the solution to fixing the issue was using ADB commands. therefore I am sharing with you this solution in case you are facing same situation.
Sorry if the solution was posted before, but looked everywhere and harldy found it, therefore I save your efforts!
First of all you must have installed ADB Fastboot tools and execute the following commands (no root required, only USB debugging activated).
Open Command Prompt and starting typing:
- type "adb shell" -> ENTER
- type down " settings put secure night_display_activated 0" (without the " character) -> ENTER;
- type again " settings put secure night_display_auto_mode 0 " -> ENTER;
- Restart your phone, either manually or type "abd reboot".
This solves the problem permanently, therefore enjoy freedom!
It doesn't work for me.
{
"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"
}
Try this again after activating the Security Settings USB debugging mode+ USB installation under the USB debugging in Developer Settings!
it didn't work for me , no errors ; but the problem persists .
if there is anything else to try let me know .
Related
Hello everybody,
want to ask your advice in re: following issue
I am going to use nextbook NX868QW8G tablet as an embedded advertisement solution ie it should start when external power gets plugged in. I can find a normal tech desc of this model in the internet even on the official site.
It have almost the same look&hardware as NX785QC8G availabe at wallmart but have slightly another cpu mtk8382 and embedded 3g modem which was the decisive factor since we need tablets to be updated remotely.
Here are system settings:
{
"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"
}
I have done the following:
1) rooted device via cydia impactor - root check apps from gplay are saying its rooted now + it has auto instaled chainfire SU to the tablet. For some reasons cydia impactor thinks its HTC ONE X. I have installed a PdaNetA4150 and it also considers it as HTC phone. I have tried to install drivers for nextbook8 I have found in internet but window doesnt recognize them as appropriate. At the moment device is recognized as unknown MT65XX Android phone
2) run adb reboot-bootloader
3) run fastboot oem unlock
4) run fastboot oem off-mode-charge 0
I have tried doing it manually and through cydia impactor but in both cases the command thread for #3 and #4 seems to be in an infinite sleep - just displays "..." in command line shell and cydia impactor simply gets frozen for a couple of minutes then throws timeout exception.
I think its waiting my input after #3 however the screen remains black and it does nothing when I press on vol up/down/power buttons. Fastboot prints "OK [X sec]" when I call fastboot reboot from another shell window.
In regards to the adb drivers and etc - device is visible through both 'adb devices' and 'fastboot devices' commands. For some reasons
Please advice in which direction to seach and digg.
Any help will be highly appreciated,
Max
Hi,
a cousin came to me with a problem about a trojan and now I have some questions to you:
All I know:
Some weeks ago I installed on this smartphone an app from F-Droid (Ghost-Commander) and to do so I had to tick >unknown sources<. After that I forgot to untick it again. About a week after that my cousin came to me with the smartphone and the 'trojan' on it (as you can see on the picture). She said that she only installed apps from the appstore.
{
"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"
}
What the 'trojan' does:
A program is forced to foreground (as you can see on the picture) - it can't be exited. No key works. The status bar can be expanded but also clicking on the icons doesn't do anything. If the device is rebooted the lock-screen is shown first and when the device is unlocked then after about one to two seconds later the 'trojan' is executed.
What I did:
After some research I rebooted the device into safe-mode. The 'trojan' wasn't executed there and so I enabled android debugging. I couldn't remove any malicious app because due to safe-mode no suspicious app was loaded. After rebooting to normal-mode again the 'trojan' was back. I connected to the android shell with $adb shell and executed $top there. Then I started to force-stop suspicious apps with $am force-stop <package> and after some tries the 'trojan' was gone. I unchecked >unknown sources< und returned the smartphone to my cousin.
The problem now is that after some days the 'trojan' showed up again but now with a different package-name! (it was called edu.fluster this time)
View attachment commands.txt
Do you know
1) how this 'trojan' got onto the smartphone?
2) how it can be totally removed or if it was another infection how to prevented more infections?
3) how it is possible to write such a harmful program? I did some simple android programming and the sandbox that is built seemed pretty secure to me (as a novice) but how are such vulnerabilitiesfound? With much time? luck? knowledge? or all together?
I would be glad if you helped me!
piqJZu
EDIT:
I finally found the apps that start this trojan:
- 2 apps with the same name both are malicious - both show up as "Browser Update" in the menu
|-- one package is called: de.record.gauge
|-- the other: edu.fluster
Answers to the other questions are still appreciated
Hi, I have a problem, I keep receiving subscription ads requests, it seems that it is from my cellphone company, since you can see the sim image in there but I am not sure. This are some examples:
{
"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"
}
Background info: (running Android 6.01, 26.3.B.0.131)
So I used to be on a cell phone company which had this subcription ads request (Movistar), but I changed to another one which they say they do not have any of that (Tuenti), with the same number, and they are both owned by the same company (Otecel), so maybe some settings from the old operator were kept in the new ones, I have talk and talk and talk with them, and i just keep receiving this ads.
Is Root the solution?
Maybe if root my device, I can disable the sim services app, or I do not know something else, and I would not receive this ads again, or what do you guys recommend me.
Hello, have you tried to 'adb hide' or 'adb disable' the STK apk? No root required AFAIK
Pixelado said:
Hello, have you tried to 'adb hide' or 'adb disable' the STK apk? No root required AFAIK
Click to expand...
Click to collapse
No, I have not tried not, because I do not know how to do it, could you please teach me , please noob steps
Sorry for being so late haha.
I'll assume you're using Windows 7 or newer.
Steps:
- Get ADB and proper drivers for your devices (Flashtool ships with all of this)
- Enable dev settings on your phone
- Enable USB debugging. Disregard all warnings
- Connect your Xperia to your PC via USB cable
- Wait for drivers to install
- Open a terminal/command prompt on your PC, point it to a directory where you have an ADB executable (adb.exe) (you can do this by opening the flashtool libs folder, eg: c:\flashtool\x10flasherlib, and right-clicking anywhere on the window while keeping the SHIFT key pressed)
- Issue the following command:
-- adb devices
Your phone should ask for authorization now. Grant it
- Issue the following command(s):
-- adb shell (this gives you access to your device's terminal from your PC)
-- pm disable com.android.stk
If the above command fails, try:
-- pm hide com.android.stk
- You're done
You can avoid using a PC by using a terminal emulator on your device AFAIK. I might be wrong though.
Good evening,
So I wasn't aware of this DPI bootlooping issue until it happened to me today. I tried changing my DPI to 1000, since it worked to me before (not yet MIUI 11)
Here are some points to consider:
> USB debugging OFF
> bootloader LOCKED
>basically just stock pocophone f1 without any trace of modding.
>Mi Flash Unlock might unlock my bootloader, but I dont want to lose personal data. I tried logging in and my account has permissions to unlock. I only consider this as a last resort. (Is this feasible by the way?)
Here are some things I discovered
1. Using command prompt:
> fastboot devices - detects my phone
> adb devices - detects my phone if I select "Connect with MIAssistant" on stock recovery
> adb shell wm density -doesn't work (I think because bootloader is locked)
> fastboot flash recovery - doesn't work either(bootloader locked)
"adb devices" did not work at first. I tried doing it on fastboot to no avail.
But after some time exploring, "adb devices" worked when selecting "Connect to MIAssistant" on stock recovery
2. It actually is not "not booting", because I tried connecting a mouse using OTG when the loading circle appeared, then a very small mouse cursor appeared.
Here is a picture
{
"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"
}
3. What I can tell is, it actually boots but encounters a problem when trying to display with that DPI setting. Correct me if I am wrong with #2 and #3.
Is there any solution to this without wiping my personal data?
Edit1: My solution here: https://forum.xda-developers.com/poco-f1/how-to/pocophone-f1-flash-stock-rom-locked-t4084979
Issue Solved with flashing stock rom. I will edit the post with a link on a new thread on how I did it even with a locked bootrom and USB debugging OFF. I hope that new thread will help others in this same problem.
hii please help fast
i have same problem i also have bootloader unlocked
i tried command in adb "adb shell density reset"
but it shows error closed
please replay soon
Kunalkp123 said:
hii please help fast
i have same problem i also have bootloader unlocked
i tried command in adb "adb shell density reset"
but it shows error closed
please replay soon
Click to expand...
Click to collapse
you need to time it correctly, or use adb's wait for device command
Can I copy somehow the files from my dead phone to PC, using fastboot command? Maybe by EDL mode
Rase to wake not working.
Phone waking up even Rase to wake in off position
{
"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"
}
It may be a bug. You can try to upgrade the system
红豆生南瓜 said:
It may be a bug. You can try to upgrade the system
Click to expand...
Click to collapse
Hi
It is up to date
Fixed.
Follow these steps:
1- Activate developers options on your phone.
For this you have to open Settings>About phone and tap on MIUI Version for about 7-10 time.
Now you go back to settings>adittional settings > Developer Options. Make sure you have USB Debugging and
USB Debugging(Security settings) are activated. For this last one i think you have to be logged in your MI account.
2- Install ADB(Android Debug Bridge) on your computer.
If you are on Windows, install ADB Universal drivers first.
Then download the ADB files.
3- Excecute commands.
Open a Command prompt (or shell) on the directory where you have the adb files.
Connect your phone with a USB cable. Change the USB mode to “file transfer".
In the Command Prompt window, enter the following command to launch the ADB daemon: adb devices.
You should get a prompt on your phone to allow (or deny) USB Debugging. Allow it and re enter on command prompt the "adb devices" command.
Now you should see your phone serial number. And you just have to enter the mentioned commands.
adb shell
settings put secure wake_gesture_enabled 0
exit (to exit adb shell)
And that`s all.
Screen turning on by itself.
When moving the redmi Note 9 the screen turns on by itself. I have disabled the "lift to activate" option, but the screen keeps turning on when moving. Someone can help me please? When the winds of change blow, some build walls, others build...
forum.xda-developers.com