How Do I Disable The Navigation Bar on Oreo? - Nexus 6P Q&A, Help & Troubleshooting

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.

Related

Is it possible to deinstall the Lockscreen on HD 10?

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

Navigation bar disappeared

Navigation bar is always on immersive mode , i have to swipe up to get it
eventhought i double clicked the dot to keep it always on , but that seems to have no effect
i was using navigation gestures and when i disabled it the issue occurred , any idea ?
Use this adb command: adb shell wm overscan reset
NeophyteGS2 said:
Use this adb command: adb shell wm overscan reset
Click to expand...
Click to collapse
used it , no difference .
A factory reset fixed the issue .

Updating to One UI mistake - please help

Hi all,
I had previously used an ADB command to remove my navigation and use swipe gestures instead.
I remember typing this following command into terminal on Mac:
adb shell wm overscan 0,0,0,-168
Now I've updated my phone to One UI, and my phone is no longer functioning correctly. My keyboard is not showing the spacebar, and I have no idea how to reverse the above command.
I really need help with this, preferably explained simply as I'm not tech savvy at all.
Thank you all!
Try the command:
adb shell wm overscan 0,0,0,0
Alternatively you can try:
adb shell wm overscan reset
Should restore you back to default
I assume you were reading from this thread here?:
https://forum.xda-developers.com/galaxy-s8/how-to/remove-oreo-navbar-completely-t3772217
You can also just use the XDA navigation gesture app or gesture control app from the play store to accomplish what you wish to do.

Display automatically turns yellow at fixed timing.

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 ?

[Guide][nonroot] Fix AndroidQ no UI sound bugs

Since I originally wrote this I have found an even easier way that works 100% without root using Setting database editor so I've updated this guide to the better method.
as a few of us 2XL owners will know Google derped sounds on the factory image of Q and our nice charging sound has been replaced with a horrible Error sound (Google Bug tracker.)
after a few weeks of waiting & trying to fix the issue myself I have finally managed to figure it out...
turns out they're trying to access sounds from the WRONG location
UI sounds on factory Q image seem to trigger from /product/media/audio/ui but this directory only has boot animations, no audio as these files are actually located in /system/media/audio/ui
it's probably why upgrading from 9 to 10 keeps the audio settings but factory flashing doesn't.
https://play.google.com/store/apps/details?id=by4a.setedit22
Install the settings database editor (link above)
Code:
open a terminal app and type(or copy paste) the line below;
pm grant by4a.setedit22 android.permission.WRITE_SECURE_SETTINGS
or using adb:
Code:
adb shell
pm grant by4a.setedit22 android.permission.WRITE_SECURE_SETTINGS
using setedit go to the global tab and look for each of the UI audio settings, switch /product/media/audio*.* to /system/media/audio/*.*
Restart your phone to apply the settings.
car_dock_sound /system/media/audio/ui/Dock.ogg
car_undock_sound /system/media/audio/ui/Undock.ogg
desk_dock_sound /system/media/audio/ui/Dock.ogg
desk_undock_sound /system/media/audio/ui/Undock.ogg
lock_sound /system/media/audio/ui/Lock.ogg
low_battery_sound /system/media/audio/ui/LowBattery.ogg
trusted_sound /system/media/audio/ui/Trusted.ogg
unlock_sound /system/media/audio/ui/Unlock.ogg
wireless_charging_started_sound /system/media/audio/ui/ChargingStarted.ogg
Minor notes:
I'm unsure why the charging sound is dictated by wireless_charging setting.
I've had a report that settings revert after a few reboots, I've not had this myself and I've rebooted a lot but if it happens just reapply the changes in setedit.
You can also change the sounds to files on your system, I've not had luck pinpointing my sdcard folder but I have been able to change Lock.ogg to Dock.ogg as a test.
(/Sdcard/download didn't work)
_________( Old method )_________
This is my first write up so please bear with me
please note I'm not responsible for any messups you make doing this
it can be done on a terminal emulator, I prefer ADB shell
in order to sucessfully do this you will need HiddenSettings magisk module
Thank you skittles9823
I'm unsure if you need busybox but the module certainly looks for it
Code:
[B][COLOR="red"]adb shell[/COLOR][/B] or launch your [I]TerminalApp[/I]
taimen:/ $[B][COLOR="red"]su[/COLOR][/B]
taimen:/ [I]#[/I] [B][COLOR="red"]hidden[/COLOR][/B]
4 - All settings
[CHOICE]:[B][COLOR="red"]4[/COLOR][/B]
3 - Modify settings
[CHOICE]:[B][COLOR="red"]3[/COLOR][/B]
===== Modify Settings =====
[Search?]:[B][COLOR="Red"]wireless_charging_started_sound /system/media/audio/ui/ChargingStarted.ogg[/COLOR][/B]
press enter & reboot your phone.
That is pretty much it, hopfully the android team fix this next patch.
I'll add some notes from what I have found through tinkering
you must reboot after modifying EACH setting.
you can see the "=" is not added when changing the settings wireless_charging_started_sound=/system/media/audio/ui/ChargingStarted.ogg (wrong)
wireless_charging_started_sound /system/media/audio/ui/ChargingStarted.ogg (Right)
Here are all the settings i can find
car_dock_sound /system/media/audio/ui/Dock.ogg
car_undock_sound /system/media/audio/ui/Undock.ogg
desk_dock_sound /system/media/audio/ui/Dock.ogg
desk_undock_sound /system/media/audio/ui/Undock.ogg
lock_sound /system/media/audio/ui/Lock.ogg (this causes an error on my phone)
low_battery_sound /system/media/audio/ui/LowBattery.ogg
trusted_sound /system/media/audio/ui/Trusted.ogg
unlock_sound /system/media/audio/ui/Unlock.ogg
wireless_charging_started_sound /system/media/audio/ui/ChargingStarted.ogg
Awesome job figuring this out. Hopefully Google will fix this in the November system images since You've done all the work for them.
Great job and thanks for it, so this works with the charging sound issue but not the locking/unlocking sound?, As for the charging sound i already have a workaround for it as i have gravitybox and edxposed installed and gravitybox have a option to change charging sound, hoepfully google will fix both in upcoming noember update
Nightf0x_007 said:
Great job and thanks for it, so this works with the charging sound issue but not the locking/unlocking sound?, As for the charging sound i already have a workaround for it as i have gravitybox and edxposed installed and gravitybox have a option to change charging sound, hoepfully google will fix both in upcoming noember update
Click to expand...
Click to collapse
I have found an even easier way that works 100% using setedit:
https://play.google.com/store/apps/details?id=by4a.setedit22
Install the app open a terminal app
pm grant by4a.setedit22 android.permission.WRITE_SECURE_SETTINGS
Job done easier to edit
Out of habit I typed su to enable root before granting write permissions so if it doesn't work without enabling su try that
co4 said:
I have found an even easier way that works 100% using setedit:
https://play.google.com/store/apps/details?id=by4a.setedit22
Install the app open a terminal app
pm grant by4a.setedit22 android.permission.WRITE_SECURE_SETTINGS
Job done easier to edit
Out of habit I typed su to enable root before granting write permissions so if it doesn't work without enabling su try that
Click to expand...
Click to collapse
Does settings revert back after multiple reboots ? Cause this happened to me
Nightf0x_007 said:
Does settings revert back after multiple reboots ? Cause this happened to me
Click to expand...
Click to collapse
I've yet to have anything revert yet if it does happen I'll post, I guess you can reapply the settings? Or once they revert can they be re changed?
Awesome it worked I have all my sounds back!!!!
krolla03 said:
Awesome it worked I have all my sounds back!!!!
Click to expand...
Click to collapse
I'll add that it's been reported that setting may revert and reapplying will fix it again
co4 said:
I'll add that it's been reported that setting may revert and reapplying will fix it again
Click to expand...
Click to collapse
so far so good
Thank you SOOO much! :highfive: It works on my Pixel 2. Had to reset it to factory after the December update killed my Pixel launcher app. After the reset I faced this horrible charging sound and the lack of lock sounds, too.
God this was driving me crazy on a warranty replacement Pixel 2. 3rd replacement and finally it boots and the battery is decent.
I don't know if I would have noticed but for having 2 phones side by side. After that, I couldn't un-hear it.
What about Effect_tick.ogg? Is there any way to set this custom sound?
Hi,
I've tried the first method, but I couldn't grant permissions in the Terminal app, it fails!
I don't have root.
Can anyone help?
Thank you so much
All these sounds work on my Pixel 1, but I get the error sound whenever I get a notification while in call. Does anybody know where I can find that sound? It's not in SetEdit.
Mandrutz said:
All these sounds work on my Pixel 1, but I get the error sound whenever I get a notification while in call. Does anybody know where I can find that sound? It's not in SetEdit.
Click to expand...
Click to collapse
I have this also on my pixel 2 does anyone know the ADB script for that?

Categories

Resources