Hi everyone,
I recently noticed the green indicator lighting up when I use my phone, indicating that the microphone or camera is being accessed.
How can I disable that function, it is a bit irriating as it keeps popping on when I use the phone?
Many thanks
Andy
and_novice said:
Hi everyone,
I recently noticed the green indicator lighting up when I use my phone, indicating that the microphone or camera is being accessed.
How can I disable that function, it is a bit irriating as it keeps popping on when I use the phone?
Many thanks
Andy
Click to expand...
Click to collapse
It's an integral privacy feature of Android 12. It may be possible to disable it using a Magisk module, but I don't know of a specific module that might do it, nor would I ever want to in the interests of privacy.
I have the solution!
Activate the developer option on the phone. Enable USB debugging.
Install platform tools on the PC.
Connect cell phone to PC.
Start command prompt with platform-tools. E.g. C:\platform-tools>
then type in ADB DEVICES and confirm on the phone.
The phone should now appear in the list.
Now copy and paste the following line
Code:
adb shell cmd device_config put privacy camera_mic_icons_enabled false default
and confirm with Enter.
From now on there is no longer a green dot when using the camera and microphone.
Restore the green dot with
Code:
adb shell cmd device_config put privacy camera_mic_icons_enabled true default
Dennis9 said:
I have the solution!
Activate the developer option on the phone. Enable USB debugging.
Install platform tools on the PC.
Connect cell phone to PC.
Start command prompt with platform-tools. E.g. C:\platform-tools>
then type in ADB DEVICES and confirm on the phone.
The phone should now appear in the list.
Now copy and paste the following line
Code:
adb shell cmd device_config put privacy camera_mic_icons_enabled false default
and confirm with Enter.
From now on there is no longer a green dot when using the camera and microphone.
Restore the green dot with
Code:
adb shell cmd device_config put privacy camera_mic_icons_enabled true default
Click to expand...
Click to collapse
This works great. However, if you reboot the device, the annoying icon is back. Do you know of a more permanent solution? Thanks!
+1 want/search a permanent solution for the location icon
I would like to know how to make those changes persistent, too.
I tried the method, worked once, but next time when I tried to use the front camera to record a video, although it showed no green dot, the video wasnt catched! only voices.... anyone knows how to resolve it? thx
Hummm... doesn't work for me.
adb shell
cmd device_config put privacy camera_mic_icons_enabled false default
I still see annoying green dot when opening camera (not horrible, but prefer not to have it).
I still see annoying green dot flashing on and off randomly all the time due to some background location (ie: sharing my GMaps location with my wife).
That drives me frickin insane to be trying to use my phone and have that damn green thing keep showing a location bubble, then a green dot, then nothing, then the location bubble again and so on all the frickin time. Who wants that? You can't even click it to see what is getting your location and disable it. It is totally useless.
Has anyone found a fix (that both works and survives reboots)?
rpmccormick said:
Hummm... doesn't work for me.
adb shell
cmd device_config put privacy camera_mic_icons_enabled false default
I still see annoying green dot when opening camera (not horrible, but prefer not to have it).
I still see annoying green dot flashing on and off randomly all the time due to some background location (ie: sharing my GMaps location with my wife).
That drives me frickin insane to be trying to use my phone and have that damn green thing keep showing a location bubble, then a green dot, then nothing, then the location bubble again and so on all the frickin time. Who wants that? You can't even click it to see what is getting your location and disable it. It is totally useless.
Has anyone found a fix (that both works and survives reboots)?
Click to expand...
Click to collapse
I found a solution. But it needs Tasker and root. If interested let me know. I'm using it on custom rom
I found that I have a slider in Developer Options to turn on/off the location one which is the one that is truly annoying. The issue is that even if I turn it off, it comes back on by itself (always after a reboot, but randomly when I have not rebooted in a few days as well).
I have root and Tasker, though I never use Tasker and find it a bit annoying in my notifications area. I would be interested in your solution though. I wish the dev-opts switch just held so I didn't get the location one all the time. The camera/mic is not so bad (though completely unnecessary useless feature that has never helped anyone identify a bad-actor app and never will)
Task: Disable Green Dot
A1: Run Shell [
Command: cmd device_config put privacy location_indicators_enabled false default
Timeout (Seconds): 0
Use Root: On
Use Global Namespace: On ]
This is the task.
Create a profile with Event - Device Boot and assign this task. I only use it since a few days, but it works so far.
After a reboot the green indicator will appear for s few seconds until Tasker sets in.
Using Tasker as XtraWater suggested and the following command:
cmd device_config put privacy camera_mic_icons_enabled false default
I was able to create a task to disable the camera's green dot. But, it only works 1/2 the time after a reboot. And when it does not work after boot up then running the task manually also does not get rid of the green dot. I'm using a rooted Pixel 6 on Android 13. I copied the other settings as well: timeout: 0, root: on, global namespace: on.
This is the first time I've ever used Tasker and I'm fairly new to rooting phones but what gets me is that it works about 1/2 of the time. Maybe a timing issue during boot up?
Any ideas??? This is driving me crazy.
It appears the Tasker job isn't doing anything actually. I disabled it and rebooted the phone a few times and it seems sometimes it shows the dot and sometimes it doesn't.
Hello, I created a Magisk module for this. This module will execute commands for disabling the green dot after boot. (
"cmd device_config put privacy location_indicators_enabled false default" and "cmd device_config put privacy camera_mic_icons_enabled false default")
The green dot may still show up for a few seconds after boot, that's because I set a delay before executing commands. Without the delay, the module may not work, probably because some system program enabled the green dot again after commands are executed.
Tested on POCO X4 Pro with ArrowOS (Android 13).
anenasa said:
Hello, I created a Magisk module for this. This module will execute commands for disabling the green dot after boot. (
"cmd device_config put privacy location_indicators_enabled false default" and "cmd device_config put privacy camera_mic_icons_enabled false default")
The green dot may still show up for a few seconds after boot, that's because I set a delay before executing commands. Without the delay, the module may not work, probably because some system program enabled the green dot again after commands are executed.
Tested on POCO X4 Pro with ArrowOS (Android 13).
Click to expand...
Click to collapse
Thank you, the module just worked fine...
Jackson Karloff said:
Thank you, the module just worked fine...
Click to expand...
Click to collapse
Not working for me on
anenasa said:
Hello, I created a Magisk module for this. This module will execute commands for disabling the green dot after boot. (
"cmd device_config put privacy location_indicators_enabled false default" and "cmd device_config put privacy camera_mic_icons_enabled false default")
The green dot may still show up for a few seconds after boot, that's because I set a delay before executing commands. Without the delay, the module may not work, probably because some system program enabled the green dot again after commands are executed.
Tested on POCO X4 Pro with ArrowOS (Android 13).
Click to expand...
Click to collapse
Not working for me on S20 with latest magisk on Android 13. Is there an updated version for this?
Hi.
Please help me.
I didn't understand how to make the command final. I tried to enter the command "cmd device_config put privacy location_indicators_enabled false default" and "cmd device_config put privacy camera_mic_icons_enabled false default"
but it gives me error. how can I do? thank you
Hey, really thanks man. It worked for me fine.
anenasa said:
Hello, I created a Magisk module for this. This module will execute commands for disabling the green dot after boot. (
"cmd device_config put privacy location_indicators_enabled false default" and "cmd device_config put privacy camera_mic_icons_enabled false default")
The green dot may still show up for a few seconds after boot, that's because I set a delay before executing commands. Without the delay, the module may not work, probably because some system program enabled the green dot again after commands are executed.
Tested on POCO X4 Pro with ArrowOS (Android 13).
Click to expand...
Click to collapse
Hello.
This work but after some times again show green dot can you please check this ?
Redmi 10 note ver 12
Hello, I found an XPosed module called Location Indicator Whitelist. Despite the name, it can disable indicator for microphone and camera in addition to location. Instead of totally disabling indicator, it disables indicator for selected application.
Related
I've complained about the OP6 DND settings, and after switching from my Essential the settings I had on there for work and sleep were still taking effect on my phone. Digging around a bit, it looks like the stock options are still there but OnePlus just hid them.
Proof - https://imgur.com/a/grHAY5V
They can be accessed with a little app from XDA Labs which just opens the window from within Settings.
https://play.google.com/store/apps/details?id=com.aiuspaktyn.nodisturb&rdid=com.aiuspaktyn.nodisturb
1+ added back DND scheduling in 5.1.6 (if I recall correctly)
maddler said:
1+ added back DND scheduling in 5.1.6 (if I recall correctly)
Click to expand...
Click to collapse
They did, but it's not as good as the stock ones with weekday, weekend..
mgear356 said:
They did, but it's not as good as the stock ones with weekday, weekend..
Click to expand...
Click to collapse
fair enough.
It works fine but, be careful : there is no icon in status bar to show when DND mode is on.
I actually created a thread about an issue i was having where a DND rule from my previous phone got carried over and was activating it on my OP6. Up until now there was nothing i could do to remove it because there were no settings for it. This has allowed me to delete that rule! Thank you.
I use tiles from playstore
Enviado desde mi ONEPLUS A6003 mediante Tapatalk
Tasker does this best, with no limitations or missing status bar icons.
Action used is 'Custom Setting'
Type: System
Name: dnd_mode_enabled
Value: 0 or 1
Use 1 to switch DND on, 0 to switch off.
heywtf said:
Tasker does this best, with no limitations or missing status bar icons.
Action used is 'Custom Setting'
Type: System
Name: dnd_mode_enabled
Value: 0 or 1
Use 1 to switch DND on, 0 to switch off.
Click to expand...
Click to collapse
Hi there, thanks for the tip;
However i get an error while running it as it needs extra permission; I have grant AutoTools the Secure Settings permissions; Is there anything else i need to tweak?
EDIT: Got it. You need to run adb shell pm grant net.dinglisch.android.taskerm android.permission.WRITE_SECURE_SETTINGS as well for tasker to get permission;
EDIT 2: its not working... Under custom settings type is "Global", "Secure" or "System" ?
@geovass type is system. Make sure that you've got https://play.google.com/store/apps/details?id=com.joaomgcd.taskersettings installed
hash87 said:
@geovass type is system. Make sure that you've got https://play.google.com/store/apps/details?id=com.joaomgcd.taskersettings installed
Click to expand...
Click to collapse
Yeah, i have this already installed; Still wont work... strange...
EDIT: I missed your note that it needs to be set as "System". Now it works!
@hash87 - do you have a list for all the different custom setting for Tasker?
heywtf said:
Tasker does this best, with no limitations or missing status bar icons.
Action used is 'Custom Setting'
Type: System
Name: dnd_mode_enabled
Value: 0 or 1
Use 1 to switch DND on, 0 to switch off.
Click to expand...
Click to collapse
I tried this with the new Android Pie update for OP6 and it seems that it doesn't work anymore.
Anyone knows another solution to get this working again?
What does Tasker's auto-detect mode say when you toggle DND manually while it's listening for changes?
It detects zen_mode from 0 to 1.
But I realised that native tasker Do Not Disturb action works as expected now.
This is my biggest gripe on Android, it almost pushes me over the edge at times. :silly: Pardon me, as this is my first Samsung device in more than a year, I just got rid of my Pixel 3 XL due to my dislike for the screen not recognizing gestures as good as Samsung.
I've tried ADB with the command prompt adb shell settings put global heads_up_notifications_enabled 0, which is what I used on my S8+ and even my P3XL, both successfully. It didn't work on my S10+. I also successfully installed SystemUI Tuner, followed the complete instructions and all of the ADB commands for that. The toggle appeared, didn't work.
This is the last thing I need to resolve to be comfortable in my new device besides the stupid GMail syncing notification. Any advice is much appreciated! :good:
Figured it out, I'm an idiot. I didn't see an option to delete the thread.....
Bro were u able to turn off the headsup notifications as i tried both of them the adb method and system tuner but neither works for me.
tariq_devil said:
Bro were u able to turn off the headsup notifications as i tried both of them the adb method and system tuner but neither works for me.
Click to expand...
Click to collapse
Its easy, you can choose it in the notification settings, you can choose for each app, choose only 'sound' if you don't want the heads up notifications.
This is new in UI 2.1 as before we had to disable with the adb method.
Cool!
So, i recently got this device and i found it pretty annoying how the clock and battery icons were too close to the rounded corner of the screen, and since my device is still in warranty i can't use advanced root tools to fix this, but fortunately i found a solution that works in unrooted stock rom and i wanted to share in case anyone wants to fix their device too.
All you need is to have access to Developer Settings and enable Device Debugging, and ADB installed in your computer.
With your device connected, open CMD in the folder you installed ADB or just open Terminal if you're in linux, then enter this commmand:
Code:
adb shell settings put secure sysui_rounded_content_padding 8
And done! You should see the difference right away.
This setting is kept after a reboot, but i doubt you'll ever want to change it back to it's default, but if you want you can change the value to 0.
You can change the value at the end of the command to your liking, i just found 8 to be my prefered setting.
I hope this helps!
EDIT: Actually, there's a problem. The padding changes to the default everytime you change the screen orientation which is very annoying. I couldn't find a fix for this but if you know of any please let me know!
Hey, do You know how to make a similar adjuctment but with padding-top (i dunno, that's how it is in html )
Bartoshevsky said:
Hey, do You know how to make a similar adjuctment but with padding-top (i dunno, that's how it is in html )
Click to expand...
Click to collapse
I'm not sure if you can change the vertical padding, but if you did it the notch would probably cover the apps on screen so i think it wouldn't be a good idea
Hi,
I have found a little workaround for the padding setting reset after screen orientation change. It is possible to get the padding back without using ADB again.
Set the padding using the ADB method
Now if you change screen orientation the padding will disappear
Go to Settings -> Display -> Advanced -> Device Theme
Switch to the theme that is not currently used and back (Note: If you have an automatic theme selected, try to select both light and dark theme, it should change after selecting one or another)
The desired padding should be back again.
I have made "Moto_LED_Blinker.prj.xml" file. See attached file.
This is a simple LED Blinker for the rooted Motorola Edge 20 Lite(Fusion)
"Moto_LED_Blinker.prj.xml" is a project file of "Tasker" for the blinking LED notification.
It is require "Tasker" for the running it.
The LED starts to blink by:
a phone calling.
a message of some messenger applications(Eg, WhatsApp, Signal, Telegram and so on).
a charging battery.
And the LED stops to blink when open an anpplicable application.
Moto_LED_Blinker.prj.xml is not a perfect.
However, it is so nice.
Please customize it for your device.
Regards!
this sounds great!
i've never used tasker before, can it be exported as a stand alone app so people without tasker can use it?
trevtdogg said:
this sounds great!
i've never used tasker before, can it be exported as a stand alone app so people without tasker can use it?
Click to expand...
Click to collapse
Techinical Iinformation:
Moto_LED_Blinker.prj.xml makes LED on and off by writting data to /sys/class/leds/charging/brightness.
This writing operation require the ROOT permission.
It is possible to export as a standalone application and people can execute the application without Tasker.
In this case, the standalone application have to be ran with the ROOT permission.
We need ROOTED device for the running the standalone application.
I have no plan to export the standalone application.
Because:
(1) There is no easy way to verify that the standalone application is secure by another person. This is a great chance to mix malicious code into the standalone application.
(2) The standalone application can not change a triggering application for the LED blinking.
(3) After all, the standalone application needs ROOT permission.
Regards,
TakaSZK said:
Techinical Iinformation:
Moto_LED_Blinker.prj.xml makes LED on and off by writting data to /sys/class/leds/charging/brightness.
This writing operation require the ROOT permission.
It is possible to export as a standalone application and people can execute the application without Tasker.
In this case, the standalone application have to be ran with the ROOT permission.
We need ROOTED device for the running the standalone application.
I have no plan to export the standalone application.
Because:
(1) There is no easy way to verify that the standalone application is secure by another person. This is a great chance to mix malicious code into the standalone application.
(2) The standalone application can not change a triggering application for the LED blinking.
(3) After all, the standalone application needs ROOT permission.
Regards,
Click to expand...
Click to collapse
Nice work
This reminds me.. I need to fix the flashlight toggle on pbrp.
Do you know which dir is for flash / torch?
I assume it'll be one of these 3.. Not had a chance to test
Code:
/sys/class/flashlight/mt-flash-led1
/sys/class/flashlight/mt-flash-led2
/sys/class/flashlight_core/flashlight
CFKod said:
Nice work
This reminds me.. I need to fix the flashlight toggle on pbrp.
Do you know which dir is for flash / torch?
I assume it'll be one of these 3.. Not had a chance to test
Code:
/sys/class/flashlight/mt-flash-led1
/sys/class/flashlight/mt-flash-led2
/sys/class/flashlight_core/flashlight
Click to expand...
Click to collapse
@CFKod
Hi,
I had confirmed in my Edge 20 Fusion.
I think that the torch is depend in /sys/class/flashlight/mt-flash-led1/ directory.
Because:
When the torch is OFF then follwing results.
:/ #
:/ # cat /sys/class/flashlight/mt-flash-led1/torch_brightness
12
:/ # cat /sys/class/flashlight/mt-flash-led1/mode
Off
:/ # cat /sys/class/flashlight/mt-flash-led2/torch_brightness
0
:/ # cat /sys/class/flashlight/mt-flash-led2/mode
Off
:/ #
When the torch is ON then follwing results.
the mode file of mt-flash-led1 says "Torch".
:/ #
:/ # cat /sys/class/flashlight/mt-flash-led1/torch_brightness
12
:/ # cat /sys/class/flashlight/mt-flash-led1/mode
Torch
:/ # cat /sys/class/flashlight/mt-flash-led2/torch_brightness
0
:/ # cat /sys/class/flashlight/mt-flash-led2/mode
Off
:/ #
I had tried to write "Off" and "Torch" into mode file.
It was failed. It so regrettable.
:/ #
:/ # echo Off > /sys/class/flashlight/mt-flash-led1/mode
: can't create /sys/class/flashlight/mt-flash-led1/mode: Permission denied
1|:/ #
1|:/ # echo Torch > /sys/class/flashlight/mt-flash-led1/mode
: can't create /sys/class/flashlight/mt-flash-led1/mode: Permission denied
1|:/ #
1|:/ #
Regards,
Does this mod use the white led over the top of the screen that lights up on the boot sequence?
xvivo said:
Does this mod use the white led over the top of the screen that lights up on the boot sequence?
Click to expand...
Click to collapse
Let's try below if you have rooted Edge 20 fusion. You can find which LED going ON ;-)
# echo 1 > /sys/class/leds/charging/brightness
# echo 0 > /sys/class/leds/charging/brightness
For anyone still wondering, it indeed uses the Led near the top grill.
It works well. Thanks.
I found my way around and customized it for my applications using the original application slots.
How to add more such slots?
Second question is that some apps pop up a temporary notification when they are checking for new messages (for example gmail, whatsapp). This notification triggers the script, but since it goes away, I check the phone and there is nothing there. I thought it was a bug until I found out what is happening from the "monitoring" option in tasker. Any way to stop these false alarms?
To answer my second question, I just added that it will trigger the led only if the display is off.
I also changed most off triggers to happen when the notification is cleared instead of needing to open the app.
In my case, I find a false alarm(false notifaction) in the history of notification and disable the false alarm.
> How to add more such slots?
I am very sorry. I have no answer because I don't know slot.
Good morning. Where can I find the procedure to import the file on tasker in my Edge 30 fusion? Thank you
Is it possible to detect fold/unfold using tasker? And then execute some tasks as a result?
lombrozo said:
Is it possible to detect fold/unfold using tasker? And then execute some tasks as a result?
Click to expand...
Click to collapse
Apparently it is by looking at the log; kaledh44 has worked it out.
see this thread;
Nova Launcher lock rotation brave toggle desktop-mode (Using Tasker)
Using Tasker to change the default launcher for OPPO FIND N, by canceling Oppo's method to enforce their launcher. -- Requirements 1- Tasker (paid ~3$). --- Autoinput (2$), for Brave desktop/phone mode auto switiching. 2- Launcher of your...
forum.xda-developers.com
In Tasker create a new profile choose Event and search for logcat entry.
>>>Fold
Component
OplusFoldingAngleManager
Filter
notifyFaceHallEventChanged status:3
>>>Unfold
Component
OplusFoldingAngleManager
Filter
notifyFaceHallEventChanged status:0
And create a task for it
Done
kaledh44 said:
In Tasker create a new profile choose Event and search for logcat entry.
>>>Fold
Component
OplusFoldingAngleManager
Filter
notifyFaceHallEventChanged status:3
>>>Unfold
Component
OplusFoldingAngleManager
Filter
notifyFaceHallEventChanged status:0
And create a task for it
Done
Click to expand...
Click to collapse
Amazing! Thanks!
@kaledh44 do you know if is possible to have Gmail and GMaps in phone mode also in the internal display?
Thank you
danilos2k said:
@kaledh44 do you know if is possible to have Gmail and GMaps in phone mode also in the internal display?
Thank you
Click to expand...
Click to collapse
by using shell command
(adb shell wm density 300)
The only problem that we dont have root access which is needed to run this command in tasker
This appears to have been changed since.
The above solutions no longer worked for me consistently on Galaxy Fold 4.
I managed to get it working with this: ( Tested only on Galaxy Fold 4 )
Folded / Closed: Logcat Entry
Component: DeviceStateProviderImpl
Filter: notifyDeviceStateChangedIfNeeded, newState=0
Unfolded / Opened: Logcat Entry
Component: DeviceStateProviderImpl
Filter: notifyDeviceStateChangedIfNeeded, newState=1
These events are executed once, as/when the inside screen turns on/off.