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
Hey folks!
I just bought 10.1 Android screen with GPS running Android version 7.1.2, processor type: Ultra Octa-T8
my question is:
How to split the screen (running two apps simultaneously )? Is there any app can do the split?
Thanks in advance,
Android7 supports split screen by default, so no special application is needed.
BUT Since T8's firmware has freeform mode enabled, you can not use split screen unless it is invalidated.
If you can use ADB, you can override freeform mode with the following syntax
adb shell delete global enable_freeform_support
But stock firmware will not be able to use ADB.
I would like to know if there is a good way...
warata said:
Android7 supports split screen by default, so no special application is needed.
BUT Since T8's firmware has freeform mode enabled, you can not use split screen unless it is invalidated.
If you can use ADB, you can override freeform mode with the following syntax
adb shell delete global enable_freeform_support
But stock firmware will not be able to use ADB.
I would like to know if there is a good way...
Click to expand...
Click to collapse
thanks for the reply,
How can I override freeform mode with the following syntax
adb shell delete global enable_freeform_support
Do you mean I have to root the screen?
would you please give more details I am new this world
MoMo131 said:
thanks for the reply,
How can I override freeform mode with the following syntax
adb shell delete global enable_freeform_support
Do you mean I have to root the screen?
would you please give more details I am new this world
Click to expand...
Click to collapse
Is this what you mean??:
https://www.youtube.com/watch?v=MRHyH9anr4c
MoMo131 said:
Is this what you mean??:
https://www.youtube.com/watch?v=MRHyH9anr4c
Click to expand...
Click to collapse
That's right buddy.In freeform mode you can use it immediately in stock ROM.
But its function is not quite useful in car stereos.
If you can disable free form mode it should be possible to use split mode.
But I am not a developer, nor is it familiar to Android.
I think that it is better for you to come to this thread for better advice.
https://forum.xda-developers.com/an...ecity-vw-allwinner-t8-2gb-32gb-7-1-2-t3704290
OK, I don't think this thread will get any attention, but I want to document it anyway. All this should work on other devices with qcom WiFi drivers.
TL;DR:
Grab iwpriv binary somewhere (i've got my here: https://github.com/kriswebdev/android_wireless_tools/tree/master/bin)
adb push iwpriv /data/local/tmp/
adb shell su -c chmod +x /data/local/tmp/iwpriv
Code:
#!/system/bin/sh
ip link set wlan0 down
sleep 1
echo 4 > /sys/module/wlan/parameters/con_mode
sleep 2
ip link set wlan0 up
/data/local/tmp/iwpriv wlan0 monitor 1
/data/local/tmp/iwpriv wlan0 MonitorModeConf 9 40 1 111 0
And enjoy your airodump output
NO PACKET INJECTION! (stubbed out in driver, removed previously?)
If you don't receive any packets, issue "/data/local/tmp/iwpriv wlan0 monitor 1" again.
How does this all work?
Some time ago I discovered these strings in wlan_hal_msg.h: (they appeared in google):
Code:
...
/* Monitor Mode */
WLAN_HAL_ENABLE_MONITOR_MODE_REQ = 302,
WLAN_HAL_ENABLE_MONITOR_MODE_RSP = 303,
WLAN_HAL_DISABLE_MONITOR_MODE_REQ = 304,
WLAN_HAL_DISABLE_MONITOR_MODE_RSP = 305,
...
Then I unscrambled some indirections:
WLAN_HAL_ENABLE_MONITOR_MODE_REQ to WDI_MON_START_REQ in WDI_2_HAL_REQ_TYPE
WDI_MON_START_REQ sent in WDI_ProcessMonStartReq <— actual message sents here!
Called from "Request Processing Array" in function WDI_MonStartReq
Wrapped in WDA_ProcessMonStartReq, which is called in WDA_McProcessMsg by message WDA_MON_START_REQ
Which message is posted by wlan_hdd_mon_postMsg if (MON_MODE_START == pMonCtx->state)
Which is called in __iw_setint_getnone with sub_cmd = WE_SET_MONITOR_STATE
Which is set by iw_priv cmd "monitor"
And then figured out that driver works in different modes:
(vos_types.h)
Code:
/// Concurrency role. These are generic IDs that identify the various roles
/// in the software system.
typedef enum
{ /*ON linux maintain 1-1 corespondence with device_mode_t in hdd*/
VOS_STA_MODE=0,
VOS_STA_SAP_MODE=1, //to support softAp mode . This is misleading. It means AP MODE only.
//The constant name has historical reason
VOS_P2P_CLIENT_MODE,
VOS_P2P_GO_MODE,
VOS_MONITOR_MODE,
VOS_FTM_MODE = 5,
VOS_IBSS_MODE,
VOS_P2P_DEVICE,
VOS_MAX_NO_OF_MODE
} tVOS_CON_MODE;
Mode can be changed by "con_mode" module parameter.
(idk why they reinvented the wheel and not used the default "iw dev wlan0 set mode monitor")
Combined all this and... got a kernel panic. You may get it too. Main reasons are:
- You have not disabled WiFi before changing the mode
- The sleep time after disabling interface is short
- Driver is old. Yes, you can get crashes on some kernels. If you are, flash AGNi.
After successful switching you'll get a working monitor (check this with tcpdump -i wlan0), but with ethernet packets instead of radiotap, so airodump will not work. Luckily, this giant crappy driver can work with radiotap, but you need to configure it. This is done by another iwpriv call:
MonitorModeConf: <channel> <bandwidth> <crccheck> <filter> <conversion_required>
Filter: 3 decimal numbers
least to most: management packets, control packets, data packets
Conversion: 1 - ARPHRD_ETHER (802.3 packets), 0 - ARPHRD_IEEE80211_RADIOTAP (802.11 packets)
(again don't know why they implemented these calls instead of default ioctl's for channel switch, etc. This makes airodump unable to switch channels)
As a result you may get something like on a screenshot
Happy sniffing!
Who said it will not be an interesting , I my self appreciated your effort to bring this up. Kudos to you friend.
Crayvolt said:
Who said it will not be an interesting , I my self appreciated your effort to bring this up. Kudos to you friend.
Click to expand...
Click to collapse
Thanks. I wanted to say that kenzo development is almost dead, we've lost official LOS and keep losing devs.... So it's most likely we'll not see working packet injection (cuz devs who know driver's internals better than me are left), and, possibly, a wrapper library implementing the default ioctl's (like channel switch) used in most programs.
i understand, hopefully we can have new devs. who will continue
This is a perfect news. At least if this device became obsolete, it should still be useful to be a portable linux pen test device, if possible. Anyway, awesome job mate. Very much appreciated
Sent from my Note 3 using XDA Labs
you dont have permission to capture on that device sokect operation not permitted
aldhi said:
This is a perfect news. At least if this device became obsolete, it should still be useful to be a portable linux pen test device, if possible. Anyway, awesome job mate. Very much appreciated
Sent from my Note 3 using XDA Labs
Click to expand...
Click to collapse
Thank you. I forgot to say that monitor mode requiers support from firmware (there's some code in driver that checks for it). Kenzo guys are lucky because we have it enabled . There's also sta+monitor mode (so you can have working wifi connection while sniffing), but it also requiers support from firmware and kenzo's fw compiled without it. I forgot how to enable it, but i think you need to issue "iwpriv wlan0 monitor 1" in default con_mode and check dmesg - there will be a string that says it's not supported (if it is not).
And if someone is interested, our wireless chip is wcn3680b, simmilar one (or same, idk) can be found in nexus 4 (mako)
cerg2010cerg2010 said:
Thank you. I forgot to say that monitor mode requiers support from firmware (there's some code in driver that checks for it). Kenzo guys are lucky because we have it enabled . There's also sta+monitor mode (so you can have working wifi connection while sniffing), but it also requiers support from firmware and kenzo's fw compiled without it. I forgot how to enable it, but i think you need to issue "iwpriv wlan0 monitor 1" in default con_mode and check dmesg - there will be a string that says it's not supported (if it is not).
And if someone is interested, our wireless chip is wcn3680b, simmilar one (or same, idk) can be found in nexus 4 (mako)
Click to expand...
Click to collapse
Can you ziping code and flashable instal on twrp?
Khimin said:
Can you ziping code and flashable instal on twrp?
Click to expand...
Click to collapse
There's nothing to install except iwpriv binary... But OK, I'll try to create a magisk module with enable/disable scripts.
cerg2010cerg2010 said:
There's nothing to install except iwpriv binary... But OK, I'll try to create a magisk module with enable/disable scripts.
Click to expand...
Click to collapse
Thx, im waiting
Khimin said:
Thx, im waiting
Click to expand...
Click to collapse
Ok, I made it quickly!
Source: https://github.com/cerg2010cerg2010/qcmon
There's 2 scripts, run them from shell:
monen - enables monitor mode (you can specify configuration in the parameters, see system/xbin/monen)
mondis - disables monitor mode. You can use your wifi connection again.
cerg2010cerg2010 said:
Ok, I made it quickly!
Source: https://github.com/cerg2010cerg2010/qcmon
There's 2 scripts, run them from shell:
monen - enables monitor mode (you can specify configuration in the parameters, see system/xbin/monen)
mondis - disables monitor mode. You can use your wifi connection again.
Click to expand...
Click to collapse
Thx dude
thank you you are awsome +thumbsup
---------- Post added at 08:49 AM ---------- Previous post was at 08:03 AM ----------
filter expresion syntax error using command tcpdump -i wlan0
help please
---------- Post added at 09:05 AM ---------- Previous post was at 08:49 AM ----------
can you help me?
cerg2010cerg2010 said:
Ok, I made it quickly!
Source: https://github.com/cerg2010cerg2010/qcmon
There's 2 scripts, run them from shell:
monen - enables monitor mode (you can specify configuration in the parameters, see system/xbin/monen)
mondis - disables monitor mode. You can use your wifi connection again.
Click to expand...
Click to collapse
Is it safe to flash with magisk in note 5 pro ?
cerg2010cerg2010 said:
Ok, I made it quickly!
Source: https://github.com/cerg2010cerg2010/qcmon
There's 2 scripts, run them from shell:
monen - enables monitor mode (you can specify configuration in the parameters, see system/xbin/monen)
mondis - disables monitor mode. You can use your wifi connection again.
Click to expand...
Click to collapse
@cerg2010 Tried to flash with magisk in note 5 pro. System apps are not working after disabling the module from magisk it returned to normal. Any solution for this ?
Perinban Parameshwaran said:
@cerg2010 Tried to flash with magisk in note 5 pro. System apps are not working after disabling the module from magisk it returned to normal. Any solution for this ?
Click to expand...
Click to collapse
Please understand that I don't have any "note 5 pro". You can send me logcat and I can try to identify the problem or ask your ROM developer to take a look (if it's not MIUI lol). Anyway, that's just scripts, so you can copy them to /data/local/tmp or /system/bin manually.
Lol I'm a n00b what does this do? Is this a packet sniffer or something?
Op_Flashpoint said:
Lol I'm a n00b what does this do? Is this a packet sniffer or something?
Click to expand...
Click to collapse
Sort of. It makes your sniffer to work - you will be able to capture raw WiFi packets from your device without any dongles.
plis whats rom u use ¿
cerg2010cerg2010 said:
Ok, I made it quickly!
Source: https://github.com/cerg2010cerg2010/qcmon
There's 2 scripts, run them from shell:
monen - enables monitor mode (you can specify configuration in the parameters, see system/xbin/monen)
mondis - disables monitor mode. You can use your wifi connection again.
Click to expand...
Click to collapse
thank you man, monitor mode now working on my poco F1, using its module magisk + aircrack-ng
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 ?
Is there a method to getting the color filter camera working again on Android 11/oxygenos 11? I searched and found out it's possible via root and downgrading, but is there a way to on the new Android 11?
yikchandev said:
Is there a method to getting the color filter camera working again on Android 11/oxygenos 11? I searched and found out it's possible via root and downgrading, but is there a way to on the new Android 11?
Click to expand...
Click to collapse
Yes it's definitely possible, there's several threads for it.
In short you need to enable engineer mode
There's more than one way to do this, for me *#808# is the best option
[GUIDE] Access color-filter through command shell
I'm running on the 10.5.10.IN11BA build. Just get a command shell to your OnePlus 8 Pro through adb, no need for the device to be rooted or anything. Once you get there, just type: am start -n...
forum.xda-developers.com
The above is a command that can be run that invokes the option too