Default navigationbar_color values from adb shell global settings for Galaxy S10? - Samsung Galaxy S10 Guides, News, & Discussion

Hey,
I recently messed up with the navigationbar_color, navigationbar_current_color and navigationbar_use_theme_default values from adb shell settings.
Can anybody please tell me the output of these commands, which will return the default values:
Connect adb shell via:
Code:
adb shell
Then:
Code:
settings get global navigationbar_color
settings get global navigationbar_current_color
settings get global navigationbar_use_theme_default
Thanks.

settings get global navigationbar_color = -855310
beyond2q:/ $ settings get global navigationbar_current_color=-855310
beyond2q:/ $ settings get global navigationbar_use_theme_default=0
xmRipper said:
Hey,
I recently messed up with the navigationbar_color, navigationbar_current_color and navigationbar_use_theme_default values from adb shell settings.
Can anybody please tell me the output of these commands, which will return the default values:
Connect adb shell via:
Code:
adb shell
Then:
Code:
settings get global navigationbar_color
settings get global navigationbar_current_color
settings get global navigationbar_use_theme_default
Thanks.
Click to expand...
Click to collapse

Thanks that worked!

Related

[Q] Changing the emulator locale from the adb shell

-- Hello,
My goal is to change device language via ADB command , and for that i do the below:
1- Make my device language English.
2- Check persist.sys.language via this command / adb shell getprop persist.sys.language / , which gives me (en).
3- Check persist.sys.country via thia command / adb shell getprop persist.sys.country / , which gives me (US).
4- Now i have changed my device language to France (via device it self).
* Now the goal to change device language via ADB commands via the below commands:
Adb shell setprop persist.sys.language en;setprop persist.sys.country US;stop;sleep 5;start
The above command does not make any changes on my device, Also the device does not restart or do any thing as supposed.
I need your kindly help and support to change my device language (select one of the languages inside the device) via ADB command.

Amazfit Pace / Stratos Tweak and Info Summary

These are tweaks i tested myself and wanted to make sure, that they don't get lost. Some may only work on custom roms. Please leave a post here, if you have any further settings or interesting commands.
# time format 12/24
adb shell settings get system time_12_24
> 24
adb shell settings put system time_12_24 {12/24}
# screen timeout (14s and 61s seems to work, not sure why others aren't working)
adb shell settings get system screen_off_timeout
> 14000
adb shell settings put system screen_off_timeout 61000
# font size
adb shell settings get system font_scale
> 1.0
adb shell settings put system font_scale 0.8
# display size
adb shell getprop ro.sf.lcd_density
> 238
adb shell wm size
> Physical size: 320x300
adb shell wm size 440x600
adb shell wm density
> Physical density: 238
adb shell wm density 200
# charging screen
adb shell getprop prop.sys.show_chargingui
> true
adb shell setprop prop.sys.show_chargingui false
# language
adb shell setprop persist.sys.language en
adb shell setprop persist.sys.country {DE,GB,...}
# adb shell over wifi
adb connect <IP>:5555
adb -s <IP>:5555 shell
# control touchscreen by remote adb
adb shell input touchscreen swipe <x1> <y1> <x2> <y2> [duration(ms)]
adb shell input touchscreen tap <x> <y>
# keep screen on without changing screen off time
while [ true ]; do adb shell input touchscreen swipe 0 0 0 0; sleep 5; done
# restart launcher
adb shell am force-stop com.huami.watch.launcher
# get all system properties
adb shell getprop
# get android version
adb shell getprop ro.build.version.release
# get battery status information
adb shell dumpsys battery
# create screenshot
adb shell screencap -p /sdcard/screen.png
# enable installation from unknown sources
adb shell settings put secure install_non_market_apps 1
# install apk
adb install *.apk
# list installed packages
adb shell pm list packages
# list only installed 3rd party packages
adb shell pm list packages -3
# show installed package version
adb shell dumpsys package <package> | grep versionName
# uninstall package
adb uninstall <package>
# useful good working watch apps
Android Filemanager
Calendar Widget
Rearrange Widgets
AMF, Reply to Notifications
# roms
stratosfied

How to turn on and off the WiFi through ADB (no root)?

I found I can use these ADB commands to turn on and of the WiFi of a rooted phone:
Code:
adb shell su -c 'svc wifi enable'
adb shell su -c 'svc wifi disable'
However, I'm interested in doing it without having to root the phone for an automatic testing I'm doing. Do you guys know if this is possible?
I found this project which allows me to connect to a WiFi through ADB commands not being a root user. I was wondering if anyone knows how to disconnect also from ADB and not being a root user.
UPDATE:
I've been recently trying:
Code:
C:\adb>adb shell am start -a android.intent.action.MAIN -n com.android.settings/.wifi.WifiSettings
adb server is out of date. killing...
* daemon started successfully *
Starting: Intent { act=android.intent.action.MAIN cmp=com.android.settings/.wifi.WifiSettings }
Warning: Activity not started, its current task has been brought to the front
and
Code:
C:\adb>adb -s serial_number shell am start -a android.intent.action.MAIN -n com.android.settings/.wifi.WifiSettings
Starting: Intent { act=android.intent.action.MAIN cmp=com.android.settings/.wifi.WifiSettings }
Warning: Activity not started, its current task has been brought to the front
I also found doing this type of command:
Code:
adb shell input keyevent 20 & adb shell input keyevent 23
I can navigate and click. The problem seems to be that I always finish in a different state so the next time I input the command
Code:
adb -s serial_number shell am start -a android.intent.action.MAIN -n com.android.settings/.wifi.WifiSettings
I start in a different place and start clicking elsewhere. I've tried returning home, but that doesn't fix the issue. Is there any way to start always from the same point inside the WiFi settings?
Thanks!
natiya said:
I found I can use these ADB commands to turn on and of the WiFi of a rooted phone:
Code:
adb shell su -c 'svc wifi enable'
adb shell su -c 'svc wifi disable'
However, I'm interested in doing it without having to root the phone for an automatic testing I'm doing. Do you guys know if this is possible?
Click to expand...
Click to collapse
Turn WiFi off
Code:
adb shell settings put global airplane_mode_on 1
adb shell settings put global wifi_on 0
adb shell settings put global wifi_scan_always_enabled 0
Afterwards you've to re-boot the device.
Turn WiFi on
Code:
adb shell settings put global airplane_mode 0
adb shell settings put global wifi_on 1
adb shell settings put global wifi_scan_always_enabled 1
jwoegerbauer said:
Turn WiFi off
Code:
adb shell settings put global airplane_mode_on 1
adb shell settings put global wifi_on 0
adb shell settings put global wifi_scan_always_enabled 0
Afterwards you've to re-boot the device.
Turn WiFi on
Code:
adb shell settings put global airplane_mode 0
adb shell settings put global wifi_on 1
adb shell settings put global wifi_scan_always_enabled 1
Click to expand...
Click to collapse
Thank you, but those don't produce any change on my device. Actually, if I put the first two commands without doing "adb kill-server" in between, I get this message:
error: more than one device/emulator
Click to expand...
Click to collapse
But the output when they work is:
adb server is out of date. killing...
* daemon started successfully *
Click to expand...
Click to collapse
and nothing happens.
I've been recently trying:
Code:
C:\adb>adb shell am start -a android.intent.action.MAIN -n com.android.settings/.wifi.WifiSettings
adb server is out of date. killing...
* daemon started successfully *
Starting: Intent { act=android.intent.action.MAIN cmp=com.android.settings/.wifi.WifiSettings }
Warning: Activity not started, its current task has been brought to the front
and
Code:
C:\adb>adb -s serial_number shell am start -a android.intent.action.MAIN -n com.android.settings/.wifi.WifiSettings
Starting: Intent { act=android.intent.action.MAIN cmp=com.android.settings/.wifi.WifiSettings }
Warning: Activity not started, its current task has been brought to the front
This opens the screen where you can turn on and off the WiFi but it doesn't do it...not sure if I'm missing something!
Just to be shure, make shure your using the latest version of ADB offered by google here:
https://developer.android.com/studio/releases/platform-tools
You could use adb wifi
After activating when using usb it and connecting through the same wifi:
svc wifi enable
works without root
I'm a little late to this thread, but if it still helps the OP, non-rooted Android 10 and below allowed wireless adb connections AFTER a USB connection was first established (adb start-server && adb tcpip 5555 && adb connect [IP]:5555), but that changed (for the better) in Android 11 and above with the new new Developer options Wireless debugging random port assignments (adb connect [IP]:[PORT] or adb pair [IP]:[PORT] [PIN]) such that the adb wireless connection never needs USB cable ever again.
Given Android 11 allows Developer options Wireless debugging via a random port, and Android 12 new Developer options Wireless debugging allows that to be accessed even easier with a new Developer options Wireless debugging tile, the only thing missing is a way to turn the non-rooted Android Wi-Fi on or off via adb (which was the OP's original question after all).
Maybe this will work if we can figure out how to tap the buttons?
adb shell "am start -a android.settings.WIFI_SETTINGS"
Click to expand...
Click to collapse
For swiping on the phone from adb this works...
C:\> adb shell input swipe 500 1000 500 100
This will instantly swipe from center to the top of the screen.
You can add a time period, e.g., take 3 seconds to swipe that.
C:\> adb shell input swipe 500 1000 500 100 3000
Click to expand...
Click to collapse
But you want to tap the buttons, right?
If we can figure out the positions, maybe this would work?
C:\> adb shell am start -n com.google.android.gms/.ads.settings.AdsSettingsActivity
That should pop up an Android "Reset Advertising ID" settings page.
C:\> adb shell input tap 500 400
If run after the command above, that will tap the button to
asking to "Opt out of Ads Personalization" in that Activity
if that button is like mine, at the X=500 & Y=400 location.
On my phone, this is the "Reset advertising ID" button location:
adb shell input tap 500 200
On my phone, this is the "OK" button on that GUI above.
adb shell input tap 700 1000
C:\> adb shell am force-stop com.google.android.gms
If run after bringing up the advertising-id reset Activity,
it will close the activity without doing anything else.
Click to expand...
Click to collapse
Here is a somewhat related post...
[adb,scrcpy,vysor] What ports does Android 12 randomly set when Wi-Fi connecting via Wireless debugging adb "pair" or "connect" commands?
Type adb tcpip 5555 in the command line or Terminal and press Enter.
Find your phone's IP address in Settings > About Phone > Status > IP Address.
Back in the command line or Terminal, type adb connect [your Android's IP address].
Finally, press Enter again.
Regards,
J Wick

[Guidance] Enable SIM hot-plug support without root

Run this with adb-tools
Code:
adb shell pm disable-user com.sonymobile.uiccdetection
Restore:
Code:
adb shell pm enable com.sonymobile.uiccdetection
Remenber to restore it if you plan to change your SIM card.
Thanks! I really appreciate this command! I always hated the reboot procedure after the sim card change.
Also, I have another adb command for the heads up notifications as stock ROM doesn't have a general heads up disable option as Lineage OS.
adb shell settings put global heads_up_notifications_enabled 0

Question Problem with 5G and volte Calls

Hi,
I read some information from users who do not have 5G available and Volte on calls.
Is this a problem that phone operators can fix or will a OnePlus fix be needed?
Thanks
5G compatibility with missing carriers/ISP can only be fixed by OTA from OnePlus
VoLTE + WifiCalling can be fixed by OTA too or once we gain root in the future and we can modify radio system files ourselves
Pouic said:
5G compatibility with missing carriers/ISP can only be fixed by OTA from OnePlus
VoLTE + WifiCalling can be fixed by OTA too or once we gain root in the future and we can modify radio system files ourselves
Click to expand...
Click to collapse
Any idea when it is going to happen?
Pouic said:
5G compatibility with missing carriers/ISP can only be fixed by OTA from OnePlus
VoLTE + WifiCalling can be fixed by OTA too or once we gain root in the future and we can modify radio system files ourselves
Click to expand...
Click to collapse
Is there a way to fix this now?
VoLTE activation procedure on OnePlus Nord 2 5G:
If NoRoot:
1. Get ready to use the adb command
2. adb reboot recovery And reboot to recovery
3. When the language selection screen appears, you will be able to connect to adb, so wait until the driver setup is completed.
* If ⚠ is displayed in the device manager, the driver cannot be loaded, so right-click and see Update Driver → Computer. Search for the driver → Available on your computer ~ → Android Device → Load the Android Composite ADB Interface.
If that doesn't work, try plugging and unplugging the cable or using the USB 2.0 port.
4. Execute the following command line by line
adb root
adb shell setprop persist.dbg.ims_volte_enable 1
adb shell setprop persist.dbg.volte_avail_ovr 1
adb shell setprop persist.dbg.vt_avail_ovr 1
adb shell setprop persist.radio.VT_ENABLE 1
adb reboot
After restarting, "VoLTE call" will appear in the SIM settings, so turn it on.
If Rooted:
1. Install Termux from GP
2. Enter "su"
3.
setprop persist.dbg.ims_volte_enable 1
setprop persist.dbg.volte_avail_ovr 1
setprop persist.dbg.vt_avail_ovr 1
setprop persist.radio.VT_ENABLE 1
setprop persist.dbg.wfc_avail_ovr 1
reboot
I have volte calls enabled by default but still doesnt work. Probably you also need support from your carrier and one plus will never exist for my carrier.

Categories

Resources