Here's an app that does the same thing: https://play.google.com/store/apps/details?id=com.notquiteinsane.galaxybuttonlights
Credit goes to Sander761, just putting it here so everyone can see it. I did this to my regular S 6 and it worked.
sander761 said:
Hi, using my Note 3 and adb I figured out the fix for this. On the Note 3 these settings were under Settings/Display/Touch Key Light. Assuming you have ADB installed and the phone put into developer mode (root is not required, this is 'standard' stuff) + usb debugging to on, take the following steps (tested on an S6 Edge):
* on the PC running adb, connect it to the device and use the command 'adb usb'. Perform the requested action to allow the PC access to the S6 (Edge)
* next, use the following commands to change the light-out period:
"adb shell settings put system button_key_light 0" -> always disable the capacitive button lights
"adb shell settings put system button_key_light -1" -> always enable the capacitive button lights
"adb shell settings put system button_key_light 1500" -> always disable the capacitive button lights after 1.5 seconds
"adb shell settings put system button_key_light 6000" -> always disable the capacitive button lights after 6.0 seconds
"adb shell settings get system button_key_light" -> get the current setting (standard: 1500, ie. 1.5 seconds)
Good luck,
Sander761 (I posted this same instruction on Tweakers.net in Dutch btw)
Click to expand...
Click to collapse
I can't for love nor money get the ADB connection working. I've installed and reinstalled them through Samsung's driver installer and KIES. Any tips?
I've tried running the commands through a terminal emulator session but there are permissions errors.
Also I found out you can shut off the lights by using in SQL editor. I was going in settings provider.db to change my notification toggles when I noticed the option I changed 1500 to 0 and the lights shutoff. will take screencap
qpop said:
I can't for love nor money get the ADB connection working. I've installed and reinstalled them through Samsung's driver installer and KIES. Any tips?
I've tried running the commands through a terminal emulator session but there are permissions errors.
Click to expand...
Click to collapse
Do you have Android Debugging checked in the development settings and did you trust the computer?
ktetreault14 said:
Also I found out you can shut off the lights by using in SQL editor. I was going in settings provider.db to change my notification toggles when I noticed the option I changed 1500 to 0 and the lights shutoff. will take screencap
Click to expand...
Click to collapse
I'm assuming this is if you have root, right?
SmiLey497 said:
Do you have Android Debugging checked in the development settings and did you trust the computer?
Click to expand...
Click to collapse
I wasn't offered the option to trust the computer, but debugging is enabled.
Never mind, I needed to manually select ADB driver for the "Samsung_Android" device in device manager. Got it working now.
This is a brilliant tweak and makes the phone far less annoying!
SmiLey497 said:
I'm assuming this is if you have root, right?
Click to expand...
Click to collapse
Correct
Any other ADB commands?!
I wonder if leaving these on will kill the battery
s6 made me do it
You don't need root for this to work
donnybright said:
You don't need root for this to work
Click to expand...
Click to collapse
And, even without root, the setting sticks between reboots.
Are there other hidden system settings that have been discovered that can be altered this way?
[EDIT] So exported the whole list of properties. 468 including public, global and secure ones on my Verizon S6 Edge. Looking through the public ones now.
Thannk yooouuu!!! Was looking for this!
Is there any way to control the light intensity? I'm fine with the backlight being on at night, etc., but it's just too bright in general. When I had my S3 2 years ago I don't remember having the option to control brightness, so maybe not...?
Is this possible on Redmi 1S? Btw I don't think its possible.
How do I get into ADB trough cmd? I don't understand that..
musti20 said:
How do I get into ADB trough cmd? I don't understand that..
Click to expand...
Click to collapse
I wrote a quick app wrapper around doing this so those that aren't ADB proficient can set their values whenever they want.
Galaxy Button Lights
Averix said:
And, even without root, the setting sticks between reboots.
Are there other hidden system settings that have been discovered that can be altered this way?
[EDIT] So exported the whole list of properties. 468 including public, global and secure ones on my Verizon S6 Edge. Looking through the public ones now.
Click to expand...
Click to collapse
Anything in there about safe volume limit?
dpwhitty11 said:
Anything in there about safe volume limit?
Click to expand...
Click to collapse
Yep, it's a Global rather than Public value. Not sure what the different states are.
global::audio_safe_volume_state::3
[EDIT] Found the constants.
private final int SAFE_MEDIA_VOLUME_NOT_CONFIGURED = 0;
private final int SAFE_MEDIA_VOLUME_DISABLED = 1;
private final int SAFE_MEDIA_VOLUME_INACTIVE = 2;
private final int SAFE_MEDIA_VOLUME_ACTIVE = 3;
You can set it using the ADB method, just have to do global rather than system. It doesn't stick on reboot and doesn't seem to actually do anything. I've never quite figured out how the audio thing pops up or doesn't. Do you know a good method to trigger it?
Averix said:
I wrote a quick app wrapper around doing this so those that aren't ADB proficient can set their values whenever they want.
Galaxy Button Lights
Click to expand...
Click to collapse
Thanks alot, works fine :good:
Averix said:
I wrote a quick app wrapper around doing this so those that aren't ADB proficient can set their values whenever they want.
Galaxy Button Lights
Click to expand...
Click to collapse
It requires permission to write system settings so the changes can be saved.
Do you mean you have to be root?
Related
THIS IS FOR INFORMATIONAL PURPOSES ONLY. BY USING SUCH A SERVICE COULD BE AGAINST YOUR CARRIER'S TERMS OF SERVICE.
Ok, I have been playing around with the Wireless Tether for Root User and got it to work on the Droid Eris!
For those who don't know what this is useful for, it allows your phone to be a gateway/router and broadcast your 3G/Edge network to other devices such as a laptop.
To get this to work, you must have 2.1 with root and flashed custom rom "Rooted 2.1 v0.3"
To get to this point, follow this guide: http://forum.xda-developers.com/showthread.php?t=647707
Once you are to this point, grab "wireless_tether_1_70-pre2_htc.apk" from http://code.google.com/p/android-wifi-tether/downloads/list?can=2&q=HTC+Donut
Make sure you allow Apps from unknown sources to be installed. (Menu > Settings > Applications > Unknown sources).
Install the app. Depending on how you acquired the download, use the browser download list, Astro Browser, Android Mate ect.
When launching the app, Superuser Whitelist will pop-up. Click always allow.
Congratulations! Now you can use your phone as a router for other devices.
THIS IS FOR INFORMATIONAL PURPOSES ONLY. BY USING SUCH A SERVICE COULD BE AGAINST YOUR CARRIER'S TERMS OF SERVICE.
I had success using "wireless_tether_1_70-pre2_htc.apk", but other versions might work also. You might get this to work without flashing the custom rom but you will have to have Superuser Whitelist, which I had trouble doing.
awesome tutorial for people that weren't sure. I added it to photex-media with working links and all =) thanks again.
any reason you went the 1.7 version as opposed to wireless_tether-2_0-pre8? I've been runnning 2.0.8 for a day or two now on and its been great.
scottdot2008 said:
any reason you went the 1.7 version as opposed to wireless_tether-2_0-pre8? I've been running 2.0.8 for a day or two now on and its been great.
Click to expand...
Click to collapse
Oh I was having problems, and after I flashed the rom, that was the 1st one I tried and it worked. I will try other versions too.
Fair enough, just wasn't sure if you knew something that I didn't about the wifi chip or something. Sorry to be a stickler.
Ive got it installed and when i load it, a panel pops up saying "SU request" but it either doesn't show anything or Force closes. Is my recovery messed up?
I don't know that it would directly be a result of your recovery, generally that's not what is running the SU program. It would be helpful to know what ROM you're currently running, as well as what version of the tether you're trying to run.
im running ivans 2.1 v0.3 and i tried the 1.7pre2 apk and the 2.0pre8. With the 1.7pre2 it force closed at the SU request and 2.0pre8 it just doesn't show anything at SU request and somewhat freezes.
EDIT!!::: i have no idea why but my usb debugger setting got switched off so i switched it back on and i can start the program and it looks like it is working, but no wireless device ive tried can see the phone as a accesspoint. BTW now i am using the 1.7pre2 version
ch4sethe5un said:
im running ivans 2.1 v0.3 and i tried the 1.7pre2 apk and the 2.0pre8. With the 1.7pre2 it force closed at the SU request and 2.0pre8 it just doesn't show anything at SU request and somewhat freezes.
EDIT!!::: i have no idea why but my usb debugger setting got switched off so i switched it back on and i can start the program and it looks like it is working, but no wireless device ive tried can see the phone as a accesspoint. BTW now i am using the 1.7pre2 version
Click to expand...
Click to collapse
Make sure to check the settings in the app (menu). My laptop is able to the the access point and I connected to it.
This may be stupid question. But can verizon detect that your using this on your phone???
903tex said:
This may be stupid question. But can verizon detect that your using this on your phone???
Click to expand...
Click to collapse
no. the only thing verizon knows is how much data you use
Thanks. So may just go ahead and try this!!!
Im not sure what i have to change in the settings, but it looks like all the correct settings are on. Is there anything else i should check out?
ch4sethe5un said:
Im not sure what i have to change in the settings, but it looks like all the correct settings are on. Is there anything else i should check out?
Click to expand...
Click to collapse
Once in a while my laptop can't find it either so I do a combo of restarting the latop/phone/service until I get it all working together. If I am correct, the set up is a point to point network so how you are configured might effect it but I might be wrong. Another app that works pretty well for wifi tethering is aNetShare. One last thing, make sure that the app has SU permissions. If you can't get it to work, try figuring out variables, like do you have wifi/bluetooth/gps on? I have no clue if this effects anything, just tossing out ideas.
I can not download superuser whitelist from the market does anyone have a link to the apk? I get an error saying it is unsigned.
FireSokar said:
I can not download superuser whitelist from the market does anyone have a link to the apk? I get an error saying it is unsigned.
Click to expand...
Click to collapse
Go to home screen > menu > settings > applications > Check Unknown sources. Accept the prompt that comes up. Try the superuser whitelist again.
is there a limit to how much data i can use.. like with this tethering app.. will verizon charge me extra if i use alot of data with this program
If you aren't on a rom with ifconfig in /system/bin/ifconfig:
go to adb shell
get root (su)
type ln -s "/system/xbin/busybox ifconfig" /system/bin/ifconfig
That should clear it up.
ashertheplague said:
is there a limit to how much data i can use.. like with this tethering app.. will verizon charge me extra if i use alot of data with this program[/QUOTE
If you have an unlimited data plan on your phone, then no there is no limit to how much data your phone could use. Call Verizon and ask if you wanna be sure. BUT, you arent supposed to be using this data connection on your pc without adding the feature to your plan which is more money. So if you hook this up and start downloading/uploading large amounts of data (bittorent, video streaming, ect) then is POSSIBLE to get yourself into trouble as it would unusual for a phone to use gigs in gigs of bandwidth in a week.
Click to expand...
Click to collapse
zifnab06 said:
If you aren't on a rom with ifconfig in /system/bin/ifconfig:
go to adb shell
get root (su)
type ln -s "/system/xbin/busybox ifconfig" /system/bin/ifconfig
That should clear it up.
Click to expand...
Click to collapse
will this clear up my date usage??
The stock DPI of 640 on this phone is totally wrong and needs to be changed immediately. I recommend the stock Nexus 6p DPI of 560 to avoid any playstore or graphical problems. Here are the steps:
1.) Settings
2.) About phone
3.) Tap build number 7 times
4.) Settings > Developer options
5.) Enable USB debugging
6.) Connect phone to computer
7.) Open command prompt and type the following hitting enter after each entry
8.) adb devices (look for prompt on phone. Check the box and hit okay)
9.) adb shell wm density 560
10.) adb reboot
Done.
To setup adb the easy way, follow this guide: http://forum.xda-developers.com/showthread.php?t=2317790
I need a USB Type C cable for the computer.... Because yes, I agree, the DPI is way off. On the 2015 X Pure it was perfect at 560.
RyanTX said:
I need a USB Type C cable for the computer.... Because yes, I agree, the DPI is way off. On the 2015 X Pure it was perfect at 560.
Click to expand...
Click to collapse
Make sure you get one of the approved cables so you don't blow anything up.
seh6183 said:
Make sure you get one of the approved cables so you don't blow anything up.
Click to expand...
Click to collapse
Thanks for the reminder, I wouldn't have even thought about it. :good:
Changing DPI to anything besides stock causes Moto Display alignment to be off. Sometimes way off. I found 534 to be the closest but went back to stock.
fr4nk1yn said:
Changing DPI to anything besides stock causes Moto Display alignment to be off. Sometimes way off. I found 534 to be the closest but went back to stock.
Click to expand...
Click to collapse
I don't know, mines at 560 and works fine ( I can see that it is slightly off though). Luckily in android N changing the DPI is right there in the settings menu. Almost there...
seh6183 said:
I don't know, mines at 560 and works fine ( I can see that it is slightly off though). Luckily in android N changing the DPI is right there in the settings menu. Almost there...
Click to expand...
Click to collapse
When you try press a "notification" button you don't need to press below or to the side of the actual button?
fr4nk1yn said:
When you try press a "notification" button you don't need to press below or to the side of the actual button?
Click to expand...
Click to collapse
It's a very tiny bit off, almost not noticeable on my phone. Sometimes I will go to press and miss, but rarely.
I changed the DPI and some of the images in the twitter app look very odd.
Also the stuff in the play store under "my apps" looks weird. The app rating and some other stuff are off.
Is this able to be fixed without going back to stock? The proportions are so much better at 560.
RyanTX said:
I changed the DPI and some of the images in the twitter app look very odd.
Also the stuff in the play store under "my apps" looks weird. The app rating and some other stuff are off.
Is this able to be fixed without going back to stock? The proportions are so much better at 560.
Click to expand...
Click to collapse
There is no way to fix it without root or Android N. We will have one or the other very soon. With that said I think the positives out weigh the negatives.
seh6183 said:
There is no way to fix it without root or Android N. We will have one or the other very soon. With that said I think the positives out weigh the negatives.
Click to expand...
Click to collapse
Agreed. It's way better. So how long before N I wonder. The way Moto and Verizon are, it could be a year.
Moto is fantastic with updates, Verizon sucks. Hopefully since Verizon is so fascinated with it's "Droid" brand, it pushes through the update as soon as Moto has it ready. N is dropping next month, which means Moto can have it ready before Christmas, or already does.
seh6183 said:
Moto is fantastic with updates, Verizon sucks. Hopefully since Verizon is so fascinated with it's "Droid" brand, it pushes through the update as soon as Moto has it ready. N is dropping next month, which means Moto can have it ready before Christmas, or already does.
Click to expand...
Click to collapse
Moto was fantastic with updates when Google owned them...they have been horrible since Lenovo took over...
VZW doesn't care if it's a Droid or not...they take their time
Sent from my XT1650 using Tapatalk
this does look better thanks. now if we could get columns and rows on stock
Thank you very much
seh6183 said:
The stock DPI of 640 on this phone is totally wrong and needs to be changed immediately. I recommend the stock Nexus 6p DPI of 560 to avoid any playstore or graphical problems. Here are the steps:
1.) Settings
2.) About phone
3.) Tap build number 7 times
4.) Settings > Developer options
5.) Enable USB debugging
6.) Connect phone to computer
7.) Open command prompt and type the following hitting enter after each entry
8.) adb devices (look for prompt on phone. Check the box and hit okay)
9.) adb shell wm density 560
10.) adb reboot
Done.
To setup adb the easy way, follow this guide: http://forum.xda-developers.com/showthread.php?t=2317790
Click to expand...
Click to collapse
Thank you very much,I am very glad to see it.I am very happy
Never mind. So used to root I forget terminal emulator where best with rooted phones.
Sent from my XT1650 using XDA-Developers mobile app
Can I ask why you would change the DPI of need to?
Now you can do it in developer options.
LeeMullinsII said:
Now you can do it in developer options.
Click to expand...
Click to collapse
Here?
Droidgreg30 said:
Here?
Click to expand...
Click to collapse
There and/or Settings - Display - Display size
Note that in developer options, bigger numbers means smaller icons etc. 560 is about as big of a number you probably want to go.
Sent from my XT1650 using Tapatalk
I want to use tasker to turn the screen off. Secure Settings > Lock Device forces me to use pin, which is not what I want, as I use a finger print scanner to wake my device. Shell > Input keyevent 26 does not work either, as I am not rooted (Huawei Mate 9 pro, doesn't seem to have a reliable root yet).
I have tried doing it with System > Send intent, but that seems to have no effect. I dont know if I am doing it wrong. I have also tried
Code:
terminal task
, with a code like this (and some variants of it), without success:
Code:
am start --user 0 -a android.intent.extra.KEY_EVENT --es KEYCODE_POWER ACTION_DOWN
I have also tinkered with
Code:
android.intent.action.SCREEN_OFF
...but with even less success.
Any ideas as how how I can get this to work? Either with terminal emulator or tasker send intent task?
I think you can't do that cause you're using your Fingerprint. That is a security future and Tasker can't bypass it. Don't nail me on it cause I am not sure. Maybe someone else can prove me wrong.
Sent from my ONEPLUS A3003 using Tapatalk
Maybe you could setup a workaround for this. For example, you could lower the display timeout value to one second so your device locks itself.
(Don't forget to change the timeout back to your preferred value after another second!)
digitalpig82 said:
Maybe you could setup a workaround for this. For example, you could lower the display timeout value to one second so your device locks itself.
(Don't forget to change the timeout back to your preferred value after another second!)
Click to expand...
Click to collapse
Good idea. But the minimum is 7 seconds, which is too long to wait, for the solution to be worthwhile.
I found a way to do it:
1: Create a task:
display > display timeout: 8 seconds
scene: Show scene: popup - display as overlay, blocking, full screen2: create a profile for screen on, create task:
hide scene: popup
display > display timeout: 30 seconds
So you're hiding the ui with a black screen until the screen is really switched off after 8 seconds, right? But what happens when you press the back or home button within the 8 seconds? Does the scene disappear?
This is what I do. Just make a task with Run shell, no need for security settings app. In the command line type input keyevent 26. You then can add a short cut when you double tap the homescreen to turn off the screen.
@snorrski you might want to have a look at this:
https://forum.xda-developers.com/u/...-adb-shell-t3562013/post72212441#post72212441
It seems to be exactly what you wanted. It works without root and on my (unrooted) S7 Edge, I can still use the fingerprint sensor to unlock my device after locking it this way (input keyevent POWER).
digitalpig82 said:
So you're hiding the ui with a black screen until the screen is really switched off after 8 seconds, right? But what happens when you press the back or home button within the 8 seconds? Does the scene disappear?
Click to expand...
Click to collapse
Yes, exactly. That's the way it is program.med for now.
digitalpig82 said:
@snorrski you might want to have a look at this:
https://forum.xda-developers.com/u/...-adb-shell-t3562013/post72212441#post72212441
It seems to be exactly what you wanted. It works without root and on my (unrooted) S7 Edge, I can still use the fingerprint sensor to unlock my device after locking it this way (input keyevent POWER).
Click to expand...
Click to collapse
Thank you! That does indeed look like what I need!
digitalpig82 said:
@snorrski you might want to have a look at this:
https://forum.xda-developers.com/u/...-adb-shell-t3562013/post72212441#post72212441
It seems to be exactly what you wanted. It works without root and on my (unrooted) S7 Edge, I can still use the fingerprint sensor to unlock my device after locking it this way (input keyevent POWER).
Click to expand...
Click to collapse
@snorrski
I know it's been over 2 years since y'all had this discussion, but I hope this still reaches you.
The power button on my Mi A1 stopped working recently and I can't seem to find it's replacement flex cable anywhere. I'm entirely new to Tasker but I have been reading for hours now to find ways to use a screen based interaction (say a double tap on the screen) to simulate the Power button to turn the screen off while still being able to unlock my phone with my fingerprint scanner.
So far, I've understood that it is doable (with an article refering to input keyevent 26), even more so on Android Pie (with another article refering to using Global_Actions) than it was previously possible, but am entirely clueless on how. I also couldn't quite understand the process of using the remote ADB shell plugin you mention here.
Could either of the two of you please share a step-by-step how-to on how to achieve the same? It would really help a lot. Thank you
Note: I'm using unrooted Mi A1 running stock Android Pie with July 1st security patch.
deepesh_p said:
@snorrski
I know it's been over 2 years since y'all had this discussion, but I hope this still reaches you.
The power button on my Mi A1 stopped working recently and I can't seem to find it's replacement flex cable anywhere. I'm entirely new to Tasker but I have been reading for hours now to find ways to use a screen based interaction (say a double tap on the screen) to simulate the Power button to turn the screen off while still being able to unlock my phone with my fingerprint scanner.
So far, I've understood that it is doable (with an article refering to input keyevent 26), even more so on Android Pie (with another article refering to using Global_Actions) than it was previously possible, but am entirely clueless on how. I also couldn't quite understand the process of using the remote ADB shell plugin you mention here.
Could either of the two of you please share a step-by-step how-to on how to achieve the same? It would really help a lot. Thank you
Note: I'm using unrooted Mi A1 running stock Android Pie with July 1st security patch.
Click to expand...
Click to collapse
Your post is getting long in the tooth. Are you still looking for help?
There are button remapping apps and apps that do double tap for off in the play store. Also, launchers can do this. Nova launcher for sure, but others I believe as well.
ktmom said:
Your post is getting long in the tooth. Are you still looking for help?
There are button remapping apps and apps that do double tap for off in the play store. Also, launchers can do this. Nova launcher for sure, but others I believe as well.
Click to expand...
Click to collapse
Hey, thanks for the suggestions. Gravity Screen, Nova Launcher as well as finally being able to understand Tasker, did help solve this issue, as I still look for a flex cable to fix the physical button issue as well.
deepesh_p said:
Hey, thanks for the suggestions. Gravity Screen, Nova Launcher as well as finally being able to understand Tasker, did help solve this issue, as I still look for a flex cable to fix the physical button issue as well.
Click to expand...
Click to collapse
Any chance this is what you're looking for?
https://www.cellspare.com/mi-a1-parts/xiaomi-mi-a1-side-key-flex-cable-module
ktmom said:
Any chance this is what you're looking for?
https://www.cellspare.com/mi-a1-parts/xiaomi-mi-a1-side-key-flex-cable-module
Click to expand...
Click to collapse
It is. Although, the price is 3.5x the price if I got it from an authorised Xiaomi service centre (except the one in my locality doesn't have it) and about 14x than what is available at local mobile spare parts shops (again not available). Hopefully, I'll find it soon.
deepesh_p said:
It is. Although, the price is 3.5x the price if I got it from an authorised Xiaomi service centre (except the one in my locality doesn't have it) and about 14x than what is available at local mobile spare parts shops (again not available). Hopefully, I'll find it soon.
Click to expand...
Click to collapse
https://www.ebay.com/itm/For-Xiaomi...851299?hash=item33fb43b7e3:g:BHEAAOSwfNpbM2Pn
https://www.parts4repair.com/side-key-flex-cable-for-xiaomi-mi-a1-5x/
If you're like me you're bummed that we have no root and are missing the abilities of root. Namely having the ability to use Xposed to turn off the annoying high volume warning. The following information aims to restore that functionality without root but requires some work but when you're done it's "set it and forget it.". You will never have to do it again. (Unless you wipe your phone)
I have this running on my phone and it works perfectly. I've attached a screenshot showing that the high volume warning is disabled on my phone. Note there is no popup on my volume slider when it's at max, so it's working. This mod uses Tasker and AutoTools. If you're not familiar with them it's OK, the article I'm linking has a step by step process for creating events and tasks.
Once again this isn't my work. I'm just bringing the information to the masses.
All set? Click here to go to the article. Enjoy!
P.S. You will need to open AutoTools and activate the 30 day trial if you don't have the full version. Then grant it permission, If not this won't work. To get the full version just open AutoTools and clock "Get full version".
***********UPDATE 09/15***********
I have confirmed that you will have to manually "test" this procedure first before it survives a reboot.
To do this:
Open tasker.
Click on the Monitor Start event.
Click on the 30 second task.
Click the "play" button in the lower left corner.
The task will begin manually.
If all is well both of the actions will turn green.
If anything turns red something isn't configured correctly.
***********UPDATE 09/17***********
For those that either don't want to or are having difficulty setting up the profiles I have attached them to this post in XML form, Then all you have to do is give the apps permission in ADB as stated in the article and import the profiles.
To import them into Tasker:
Download the file called "Tasker Profiles.zip" from the link below.
Unzip it and save it anywhere on your internal storage. Open up Tasker and disable Beginner Mode in Preferences.
Then, go back to the main screen and long-press on the “Profile” tab up top. You should see a pop-up with one of the options being “Import.”
Tap on that and browse to where you saved the .prf.xml files and select that file to import.
Repeat for the second profile.
Screenshots for this are attached to this OP.
I have also attached a quick demo video to show that this process works perfectly. No popup.
Credit:
Mishaal Rahman
reboot and see if it still works.
I already tried this and after reboot it still prompts the first time.
I've rebooted several times. It works for me. There is a 30 second delay before the task is executed. That is by design.
Compusmurf said:
reboot and see if it still works.
I already tried this and after reboot it still prompts the first time.
Click to expand...
Click to collapse
Try this to see if everything is set up correctly:
Open tasker.
Click on the Monitor Start event.
Click on the 30 second task.
Click the "play" button in the lower left corner.
The task will begin manually.
If all is well both of the actions will turn green.
If anything turns red something isn't configured correctly.
I've attached screenshots of this procedure.
Also something to consider is that if you have any task killers installed or anything that kills tasks on startup you should add tasker to the ignore list of that app.
Hope this helps.
It's configured correctly. Here is the thing. If you pull the value before without using, then pull the value after clicking ok manually, it is NOT 2, it's 0. This was discussed on the s7 and s8 forums. Odd that yours works and dozens of other folks doesn't.
Sent from my SM-N950U using Tapatalk
I dont know what to tell you. It does work for me just fine as my screen shots show. Sorry it's not working for you.
Can you screenshot your configuration screen? Is the value your sending "int" for integer? It shouldn't matter but what Carrier are you using? I'm Sprint.
One other thing to check is under app permissions ensure that AutoTool has the ability to change system settings. Just running the adb shell pm command isn't enough.
Compusmurf said:
It's configured correctly. Here is the thing. If you pull the value before without using, then pull the value after clicking ok manually, it is NOT 2, it's 0. This was discussed on the s7 and s8 forums. Odd that yours works and dozens of other folks doesn't.
Sent from my SM-N950U using Tapatalk
Click to expand...
Click to collapse
According to the article 0 is 'not configured' 1 is 'disabled' which is what the value would be when you click ok. 2 is 'inactive'.(How this differs from 'not configured' or 'disabled' I do not know). and 3 is 'enabled'. All depending on your mobile country code. Perhaps changing it to 1 will work for you?
Specifically, we will be modifying the System.Global property audio_safe_volume_state both on boot and periodically so Android will always think you have consented to bypass the warning. This property is defined in AOSP, which we’re reproducing below. There are several states this property can take, ranging from 0-3. 30 seconds after boot or after every 20 hours of continuous music playback, the state is set to ‘0’ or ‘not configured.’ It is then set to ‘1’ for ‘disabled’ or ‘3’ for ‘enabled’ depending on your Mobile Country Code. If you live in the E.U., this property is set to ‘3’ by default but is changed to ‘2’ for ‘inactive’ whenever the user manually bypasses the volume warning. We will be changing the value of this property to the ‘inactive’ state (changing it to ‘disabled’ never worked for me, in case you’re wondering).
Click to expand...
Click to collapse
Hope this helps.
This is already built in...Vibration>Volume>3 dots menu in upper right hand corner> Media Volume Limiter> Turn it off.
Namuh said:
This is already built in...Vibration>Volume>3 dots menu in upper right hand corner> Media Volume Limiter> Turn it off.
Click to expand...
Click to collapse
Confirmed.
Going to Settings -> Sound and Vibration -> Volume -> hit the 3 dot menu -> Media Volume Limiter -> Off works.
I came from a Note 4 with Android 5.1.1 that didn't have this feature. I had no idea Samsung finally caved and added it.
Thank you.
Or not. I rebooted again and it does NOT work anymore. I'm really not trusting Samsung with this. The tasker method works every time. Every reboot. See attached screenshots showing it's turned on (and set to max) and still showing this message. I rebooted several times just in case I had a weird reboot. I'm still getting the popup even with it turned on and the max adjusted to the maximum or even with it turned off completely.
I only wish I was wrong. Thanks for the try though.
Yeah will reset after a boot
https://forum.xda-developers.com/showpost.php?p=73802232&postcount=4
marctronixx said:
https://forum.xda-developers.com/showpost.php?p=73802232&postcount=4
Click to expand...
Click to collapse
Yup...so with tasker I don't have to do any of that. I never have to touch it again. It never comes back.
Thanks again though.
I did learn something from this process. When I re-enabled the tasker even it didn't work when I rebooted. So I hit the "play" button that I mentioned earlier to retest the task and once everything turned green I rebooted and it now works again...after every reboot. So I'll add this to the OP that the task must be "tested" after it's set up in order to get it to work.
Even more interesting is who posted it. Compusmurf was the guy who stated in this thread that this did not work for him. Interesting.
I did get it to work finally. I had another tasker/app that was stepping on it.
Compusmurf said:
I did get it to work finally. I had another tasker/app that was stepping on it.
Click to expand...
Click to collapse
Well I also confirmed that when I disabled it and allowed the popup to come back by rebooting simply re-enabling the tasker even then rebooting did not make it work again. I had to "test" it with the play button to get it to work again. So I'm updating the OP to reflect this.
rawintellect said:
Yup...so with tasker I don't have to do any of that. I never have to touch it again. It never comes back.
Thanks again though.
Click to expand...
Click to collapse
Yeah my point of my post was to show the reason why the built in way doesn't work long term. The tasker way is preferred for those who find the nanny thing an annoyance. :good:
System ui tuněr app should be able to do it
Techvir said:
System ui tuněr app should be able to do it
Click to expand...
Click to collapse
I looked at every single screenshot of System UI Tuner in the play store. I saw no option to disable the high volume warning. Only an option to remove the volume icon which isn't the same thing.
Can you show me a screenshot of it working?
I know this process I linked is a long one and I would really love to be shown a better way but until I am this works for non rooted devices every time.
Hello
I recently got a Realme X2 Pro and I am very happy with it.
However, I have an issue with the screen 90Hz setting. I use Samsung internet browser and I can't get it to use the 90Hz setting, with the UFO test I get 60Hz, I tried other browsers (Brave, Chrome beta, etc) and all of them are in 60Hz mode. Only Chrome gets the 90Hz mode correctly.
I checked the 90Hz setting and they are enabled in the app list.
I am wondering if there is a way to force enable 90Hz as it's possible on the OnePlus 7 Pro (via ADB command)
Many thanks for any support
I don't think so, as despite it being a 90Hz panel Realme have put a severe limit on it; they do not enable it on any game which was a bit of a disappointment
Aidey68 said:
I don't think so, as despite it being a 90Hz panel Realme have put a severe limit on it; they do not enable it on any game which was a bit of a disappointment
Click to expand...
Click to collapse
Thank you. I hope realme adds a option to force enable 90Hz in all cases or some hack like the one on OnePlus is found.
I enjoy 90Hz but it not working on one of the most used apps (browser) is a bummer.
Derek100 said:
Thank you. I hope realme adds a option to force enable 90Hz in all cases or some hack like the one on OnePlus is found.
I enjoy 90Hz but it not working on one of the most used apps (browser) is a bummer.
Click to expand...
Click to collapse
There are a few browsers that support 90hz like Chrome and Opera, sadly my most used one Kiwi doesn't.
wilpang said:
There are a few browsers that support 90hz like Chrome and Opera, sadly my most used one Kiwi doesn't.
Click to expand...
Click to collapse
Yeah I knew that! I hope there is or will be a way to always enable 90Hz as it's possible on OnePlus
Minecraft and the Chinese pubgm work in 90hz so it's not all games... I don't think this is Realme blocking them but the game developers.
ngagephone said:
Minecraft and the Chinese pubgm work in 90hz so it's not all games... I don't think this is Realme blocking them but the game developers.
Click to expand...
Click to collapse
With the Samsung browser, 90Hz only works on the settings screen :laugh: but not on webpages, in which it switches back to 60Hz. Opera does indeed use it on webpages, but its scrolling is so laggy that it's difficult to notice it LOL, while the Samsung browser has the smoothest scrolling and it would benefit the most.
Any other app also seems to use 90Hz, but it seems Asphalt 9 doesn't.
I am curious if the Android 10 update will change something, as I can't try the betas.
Derek100 said:
With the Samsung browser, 90Hz only works on the settings screen :laugh: but not on webpages, in which it switches back to 60Hz. Opera does indeed use it on webpages, but its scrolling is so laggy that it's difficult to notice it LOL, while the Samsung browser has the smoothest scrolling and it would benefit the most.
Any other app also seems to use 90Hz, but it seems Asphalt 9 doesn't.
I am curious if the Android 10 update will change something, as I can't try the betas.
Click to expand...
Click to collapse
I'm on beta and nothing has changed.
JackSparrow17 said:
I'm on beta and nothing has changed.
Click to expand...
Click to collapse
Then I hope some command or hack to always enable 90Hz as it's possible on OnePlus, surfaces (I tried it for the lulz but it returns an error)
It's a shame that one of the apps I use most can't benefit from 90Hz
I have a trick.
1) Use any app that runs at 90Hz
2) Launch It in split Windows Mode
3) Now launch Samsung Browser in the botton of the splitwindow (as the second app)
4) Now move the split line up yo asign more space to Samsung Browser.
5) Now move totally Up the split line, making Samsung Browser the only app visible...and voila!!! It is running at 90Hz.
The process is quick as soon you make rutine...but the problem is you need to do several time (each time you change the application).
Can't somebody develop a hack (similar to OnePlus) on the basis of that workaround?
Tetraeder said:
Can't somebody develop a hack (similar to OnePlus) on the basis of that workaround?
Click to expand...
Click to collapse
OnePlus has a hidden option to force 90hz and that's how the hack enables... Not sure our device will have any hidden settings to enable this.
---------- Post added at 03:58 PM ---------- Previous post was at 03:20 PM ----------
Tetraeder said:
Can't somebody develop a hack (similar to OnePlus) on the basis of that workaround?
Click to expand...
Click to collapse
Ok this might be a start
https://www.reddit.com/r/samsung/comments/fqk5he/made_the_s20_display_run_at_96hz_so_much_better/
This uses pretty much the same method the OnePlus 7t but for the S20 ultra... I don't have access to ADB at the minute.
If anyone with ADB would like to test and use these commands?
adb shell settings put secure refresh_rate_mode 0
adb shell settings put secure refresh_rate_mode 1
adb shell settings put secure refresh_rate_mode 2
Might need the global tag
adb shell settings put global screen_refresh_rate 0
adb shell settings put global screen_refresh_rate 1
adb shell settings put global screen_refresh_rate 2
anfederin said:
I have a trick.
1) Use any app that runs at 90Hz
2) Launch It in split Windows Mode
3) Now launch Samsung Browser in the botton of the splitwindow (as the second app)
4) Now move the split line up yo asign more space to Samsung Browser.
5) Now move totally Up the split line, making Samsung Browser the only app visible...and voila!!! It is running at 90Hz.
The process is quick as soon you make rutine...but the problem is you need to do several time (each time you change the application).
Click to expand...
Click to collapse
It works! the only problem is what you say, when you exit the app or switch apps you have to do it every time
ngagephone said:
OnePlus has a hidden option to force 90hz and that's how the hack enables... Not sure our device will have any hidden settings to enable this.
---------- Post added at 03:58 PM ---------- Previous post was at 03:20 PM ----------
Ok this might be a start
https://www.reddit.com/r/samsung/comments/fqk5he/made_the_s20_display_run_at_96hz_so_much_better/
This uses pretty much the same method the OnePlus 7t but for the S20 ultra... I don't have access to ADB at the minute.
If anyone with ADB would like to test and use these commands?
adb shell settings put secure refresh_rate_mode 0
adb shell settings put secure refresh_rate_mode 1
adb shell settings put secure refresh_rate_mode 2
Click to expand...
Click to collapse
I get this
Security exception: Permission denial: writing to settings requires:android.permission.WRITE_SECURE_SETTINGS
java.lang.SecurityException: Permission denial: writing to settings requires:android.permission.WRITE_SECURE_SETTINGS
at com.android.providers.settings.SettingsProvider.enforceWritePermission(SettingsProvider.java:2295)
at com.android.providers.settings.SettingsProvider.mutateSecureSetting(SettingsProvider.java:1720)
at com.android.providers.settings.SettingsProvider.insertSecureSetting(SettingsProvider.java:1680)
at com.android.providers.settings.SettingsProvider.call(SettingsProvider.java:543)
at android.content.ContentProvider.call(ContentProvider.java:2162)
at android.content.ContentProvider$Transport.call(ContentProvider.java:481)
at com.android.providers.settings.SettingsService$MyShellCommand.putForUser(SettingsService.java:375)
at com.android.providers.settings.SettingsService$MyShellCommand.onCommand(SettingsService.java:277)
at android.os.ShellCommand.exec(ShellCommand.java:104)
at com.android.providers.settings.SettingsService.onShellCommand(SettingsService.java:49)
at android.os.Binder.shellCommand(Binder.java:881)
at android.os.Binder.onTransact(Binder.java:765)
at android.os.Binder.execTransactInternal(Binder.java:1021)
at android.os.Binder.execTransact(Binder.java:994)
Do you have usb debugging on in the developer settings? I'm going to setup ADB and have a play around later today and I'll post back if I get anywhere.
ngagephone said:
Do you have usb debugging on in the developer settings? I'm going to setup ADB and have a play around later today and I'll post back if I get anywhere.
Click to expand...
Click to collapse
Yeah I have it enabled, I don't know why I can't change system settings, I search that permission and it's for APKs and not for the entire ADB command prompt
ngagephone said:
Do you have usb debugging on in the developer settings? I'm going to setup ADB and have a play around later today and I'll post back if I get anywhere.
Click to expand...
Click to collapse
I had to enable "Disable permission monitoring" at bottom LOL
Now I don't get any error but none of these commands do anything (the screen still doesn't force to 90 Hz
Derek100 said:
I had to enable "Disable permission monitoring" at bottom LOL
Now I don't get any error but none of these commands do anything (the screen still doesn't force to 90 Hz
Click to expand...
Click to collapse
Just leave it then I'll test later because actually I don't want anyone needing to do a master reset if something goes wrong. I'll update.
ngagephone said:
Just leave it then I'll test later because actually I don't want anyone needing to do a master reset if something goes wrong. I'll update.
Click to expand...
Click to collapse
No problem, I have tried many other commands or variants like the oneplus one
adb shell settings put global oneplus_screen_refresh_rate 0
Even tried changing "oneplus_screen_refresh_rate" to "realme_screen_refresh_rate" or "oppo_screen_refresh_rate" but it's still hopeless!
Still the phone works without any difference (I've rebooted just in case)
Derek100 said:
No problem, I have tried many other commands or variants like the oneplus one
adb shell settings put global oneplus_screen_refresh_rate 0
Even tried changing "oneplus_screen_refresh_rate" to "realme_screen_refresh_rate" or "oppo_screen_refresh_rate" but it's still hopeless!
Still the phone works without any difference (I've rebooted just in case)
Click to expand...
Click to collapse
Not looking hopeful then as the last 2 commands was the first thing I was going to try.
ngagephone said:
Not looking hopeful then as the last 2 commands was the first thing I was going to try.
Click to expand...
Click to collapse
I tried the command
adb shell settings list global
but I can't find anything with refresh or screen or Hz or something similar ... only the tried commands settings