G'day all, I figured out how to detect when the device folds using tasker/macrodroid.
The built in Bixby Modes and Routines can do it but it has a long(ish) delay and can really only be used to create a custom notification for tasker/macrodroid to intercept, which then also has to be cleared and adds even more of a delay.
So you set up a task/macro to read the logcat as a trigger.
Trigger logcat details are as follows:
Component: lid_state_changed
Value: 0 or 1 (0=folded and 1=unfolded)
In macrodroid, the buffer is "Events", not sure in tasker as I don't use it.
So I have a macro set up to detect when the device is folded or unfolded and set a global variable to store the status for use by other macros.
This detection method is instant, simple and the best and easiest way to detect when a fold occurs.
Hope it helps everyone and ta-ta
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
lid_state_changed -- how did you find it? I'm on the latest FW, OneUI 5.1 and this doesn't come up in logcat on phone open or closed - so can't set it by it.
I've been identifying open/close state by a nasty workaround in tasker via reading the edge_panel_width variable - as it has different values on open/close - but for this have to have the edge panel enabled, and I'd like to disable it...
白い熊 said:
lid_state_changed -- how did you find it? I'm on the latest FW, OneUI 5.1 and this doesn't come up in logcat on phone open or closed - so can't set it by it.
I've been identifying open/close state by a nasty workaround in tasker via reading the edge_panel_width variable - as it has different values on open/close - but for this have to have the edge panel enabled, and I'd like to disable it...
Click to expand...
Click to collapse
That's strange. I'm on 5.0.... surely they didn't go through the effort of changing it :/
I found it by using macrodroid. When you select the logcat as the trigger, there's an option to identify the log entry by recording it then displaying it.
So when I did this, a floating button appeared on the screen. I tapped it and it starts recording the logcat. I quickly folded the phone shut then open again and hit the button to stop recording. It then displayed all logcat entries and I went through it until I found one that sounded like a fold event, then set it as the trigger and tested it. They must've changed the name of it in 5.1.
If you want, get an app that records the logcat, or even used macrodroid to do it the way I did, then quickly fold and unfold your phone and stop recording, then screenshot it and message it to me and I'll have a look
Is there a way to detect screen fold/unfold in Tasker or MacroDroid without using LogCat? My device has been updated to Android 13, which breaks LogCat functionality for this.
shdwphnx said:
Is there a way to detect screen fold/unfold in Tasker or MacroDroid without using LogCat? My device has been updated to Android 13, which breaks LogCat functionality for this.
Click to expand...
Click to collapse
I'm on 13 too and it works. LogCat needs either the abd hack or root to work. For abd, macrodroid will give you a command to enter which will let your phone read logcat without root.
shdwphnx said:
Is there a way to detect screen fold/unfold in Tasker or MacroDroid without using LogCat? My device has been updated to Android 13, which breaks LogCat functionality for this.
Click to expand...
Click to collapse
If you need help doing the abd hack, let me know. It doesn't really hack your phone or do anything to it... it literally just gives macrodroid permission to read the logcat and that's it.
Lovemtucken said:
If you need help doing the abd hack, let me know. It doesn't really hack your phone or do anything to it... it literally just gives macrodroid permission to read the logcat and that's it.
Click to expand...
Click to collapse
Is MacroDroid's ADB hack different from the one that Tasker does via the "Tasker Permissions" tool? That one causes Android to pop-up a prompt to allow once or deny whenever Tasker tries to read the log, and automatically revokes the permission as soon as I switch to another application.
shdwphnx said:
Is MacroDroid's ADB hack different from the one that Tasker does via the "Tasker Permissions" tool? That one causes Android to pop-up a prompt to allow once or deny whenever Tasker tries to read the log, and automatically revokes the permission as soon as I switch to another application.
Click to expand...
Click to collapse
I'm not too sure, I don't use tasker.
The macrodroid adb permanently gives macrodroid logcat read permission by entering a command in Windows command line.
You may even be able to do it with tasker.
adb shell pm grant com.arlosoft.macrodroid android.permission.READ_LOGS
You could try changing "com.arlosoft.macrodroid" to the tasker package name and see if it works?
Related
Please do NOT continue with this tutorial. This method has been improved, and has moved to another thread which you can visit by clicking here. Thank you for you're understanding!
I have finally found a highly effective solution to remove lockscreen ads from the Fire Tablets. If you want to COMPLETELY remove ads without them coming back randomly this is the post for you. So without further ado let's get started.
All you will need is:
Fire Tablet
USB Cable
USB Debugging enabled
And a computer
1. Next you will need to download Settings Database Editor by 4A from the Play Store.
https://play.google.com/store/apps/details?id=by4a.setedit22
Once the app is installed DO NOT open it. Proceed to the next step.
2. Enable USB debugging, if you need help refer to this website:
https://www.howtogeek.com/129728/how-to-access-the-developer-options-menu-and-enable-usb-debugging-on-android-4.2/
3. Once USB debugging is enabled plug your tablet into your PC.
Now you will need to open a Command Prompt (Windows) or a Terminal (Linux) session.
Now type the following commands EXACTLY as they appear on screen:
Code:
adb shell pm grant by4a.setedit22 android.permission.WRITE_SECURE_SETTINGS
You will know if the command has work successfully if it does not return an error after executing the command.
4. Now you can close the Terminal/Command Prompt and unplug your device from the PC.
5. Open Settings Database Editor. Once in the app look for a drop down menu that by default should say "System Table" tap on it and select "Global Table" from the drop down menu.
6. Find the following line of code:
Code:
"LOCKSCREEN_AD_ENABLED" "1"
Now to disable the lockscreen ads go ahead and tap on it. A box should pull up with a 1 already inserted, now delete the 1 and replace it with a 0. Now reboot your Fire Tablet! Once it reboots the Lockscreen ads should be no more. Thanks for taking the time to read this post and have a wonderful day!
Before:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
After:
Hey Monkeybomb, great work!
i'm experiencing an odd behavior though with this, apparently, if you let your tablet naturally go back to sleep (display times out) the ads will come back. any ideas on how to prevent that, other than disabling screen timeout?
hinxman said:
Hey Monkeybomb, great work!
i'm experiencing an odd behavior though with this, apparently, if you let your tablet naturally go back to sleep (display times out) the ads will come back. any ideas on how to prevent that, other than disabling screen timeout?
Click to expand...
Click to collapse
That would be the only way unless you are on 5.4.0.0 then you can disable system apps.
Just hitting the "thanks" button is not enough in this case. THANKS!
How did you figure that out? What did you do to get to this solution? And again, thanks!
GoodSoul said:
Just hitting the "thanks" button is not enough in this case. THANKS!
How did you figure that out? What did you do to get to this solution? And again, thanks!
Click to expand...
Click to collapse
Glad I could help you out! The Settings Database is where Android stores all of the values for each setting. By using the Settings Database Editor app we can manually change the values located in the settings.db file. Apparently, the only other known method to disable ads on the Fire Tablet is to removed the Amazon Offers app through ADB which sadly can no longer be done because Amazon has blocked the ADB command after the latest system update. The idea came to me when I was interested to see if Amazon was storing a value in the settings database governing the lockscreen ads and much to my surprise there it was! By using the Database Editor app we are able to change the value and thus removing the ads without the use of a PC (after you grant the app access to change system settings of course).
hinxman said:
Hey Monkeybomb, great work!
i'm experiencing an odd behavior though with this, apparently, if you let your tablet naturally go back to sleep (display times out) the ads will come back. any ideas on how to prevent that, other than disabling screen timeout?
Click to expand...
Click to collapse
Thank you for your kind words!
Unfortunately I don't know another way with this method. I'am however working on an app that can automatically perform the actions of disabling the lockscreen ads without user interaction. I will keep you all updated as I continue to make progress
hinxman said:
Hey Monkeybomb, great work!
i'm experiencing an odd behavior though with this, apparently, if you let your tablet naturally go back to sleep (display times out) the ads will come back. any ideas on how to prevent that, other than disabling screen timeout?
Click to expand...
Click to collapse
I have a method that will completely remove ads, even when the device sleeps, reboots, etc. I will share more information with you guys soon. Stay tuned
You can also try the amazon representative chat method. They removed mine very easily. I just said it blocks my notifications. Without any problem they removed my ads.
Alright guys I've successfully posted my new method. I PROMISE it will remove the ads for GOOD. Thanks guys!
Link: https://forum.xda-developers.com/hd8-hd10/development/remove-amazon-lockscreen-ads-adb-t3784848
I found simply disabling the kindle special offer will work.
Device must be rooted already.
adb shell
su
pm disable com.amazon.kindle.kso
Then change
LOCKSCREEN_AD_ENABLED
to 0.
Works on 2015 Fire 7. Thank you!
Many, many thanks, bro!!! I picked up a 7" 2017 Fire tablet and can attest that your fix works on 5.6.1, the latest OS. I use this tablet strictly as a touchscreen wifi universal remote control for Harmony, Nest, etc. No ads make it even better, now! :good:
spoofykid said:
Works on 2015 Fire 7. Thank you!
Click to expand...
Click to collapse
Hi Spoofy,
While this method does work and it will remove the ads it will only remove them temporarily. The ads sadly will return. However I have perfected this method by making a script that will remove the ads permeantly. Please check out the updated thread located here: https://forum.xda-developers.com/hd8-hd10/development/remove-amazon-lockscreen-ads-adb-t3784848 thanks for your understanding.
New thread on this method.
jswriter said:
Many, many thanks, bro!!! I picked up a 7" 2017 Fire tablet and can attest that your fix works on 5.6.1, the latest OS. I use this tablet strictly as a touchscreen wifi universal remote control for Harmony, Nest, etc. No ads make it even better, now! :good:
Click to expand...
Click to collapse
Hi jswriter,
I'm so happy that I could help you out with this method. I think it's very cool what you are using the tablet for! However I need to let you know that this method isn't perminant and the lockscreen ads will return. Fortunately, I have posted a new thread on this method that WILL prevent the lockscreen ads from returning and is a perminant solution. Please visit the thread for details. https://forum.xda-developers.com/hd8-hd10/development/remove-amazon-lockscreen-ads-adb-t3784848 thanks for your understanding. Have a great day!
Tested this with my new Fire HD 10 and Fire OS 7.3.1.1 and it works only for a few seconds/minutes.
killercorny said:
Tested this with my new Fire HD 10 and Fire OS 7.3.1.1 and it works only for a few seconds/minutes.
Click to expand...
Click to collapse
Read OP; method depreciated.
Worked like a charm in Fire HD 2018 Fire OS 6.3.1.5. Thank you!
Hello,
I have a small problem with black border around the display. Sometimes I dont have some black pixels in one line at the right bottom corner. It is ok after restart or after turn off (to always on) display.
Pixels aren't dead, they are correctly working so it's probably a SW bug. I know about one or two next devices with the same problem.
Do you know how to repair this? I tried factory reset and many display settings and it is the same but it doesn't work. A simple solution would be to set a frame 1px larger. Is it possible, for example, with ADB?
It is S20 5G (SM-981B/DS), here is the photo:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Look through your apps which need access to drawing on the display or something like that. I don't think that is a bug with one UI. Try disabling all "draw over screen" apps you have and look if the problem still persists.
honor701 said:
Look through your apps which need access to drawing on the display or something like that. I don't think that is a bug with one UI. Try disabling all "draw over screen" apps you have and look if the problem still persists.
Click to expand...
Click to collapse
I can see the bug after factory reset. The device has only default apps at this time. I tried to disable special permission for all apps and it is the same.
See if it happens in safe mode.
Anything show up with Screen Test?
Could even be a bug in that firmware version.
blackhawk said:
See if it happens in safe mode.
Anything show up with Screen Test?
Could even be a bug in that firmware version.
Click to expand...
Click to collapse
Yes, it´s in safe mode too. Problematic pixels are correctly changing color in the screen test.
skrlik said:
Yes, it´s in safe mode too. Problematic pixels are correctly changing color in the screen test.
Click to expand...
Click to collapse
Interesting. I would blow it off as it's on the firmware or the original software load.
-or-
If you look at the loaded app cache* after a reboot before it appears then wait until it appears then check the cache for newer apks; it's one of those.
Likewise when does it appear; a fixed amount of time or after a specific action?
It may be an apk on the autostart menu that's down on the priority list.
The app Autostarts might be helpful in giving clues.
* Developer options>running processes (or cache apps) may be helpful although it may not show up there. The cache processes is more likely to pigeon hole it.
Device Care>Memory is an easy way to see what apks are cached. If you clear it and it happens afterwards you can easily see what apks were just cached.
PD MDM package disabler can be used to block a suspect package or clear it's data or cache.
It can completely clear the data, App Settings can not.
Apparently the latter leaves behind nulls or something that can still corrupt the data.
PD MDM is powerful tool useful for cleaning up messes but use it carefully...
blackhawk said:
Interesting. I would blow it off as it's on the firmware or the original software load.
-or-
If you look at the loaded app cache* after a reboot before it appears then wait until it appears then check the cache for newer apks; it's one of those.
Likewise when does it appear; a fixed amount of time or after a specific action?
It may be an apk on the autostart menu that's down on the priority list.
The app Autostarts might be helpful in giving clues.
* Developer options>running processes (or cache apps) may be helpful although it may not show up there. The cache processes is more likely to pigeon hole it.
Device Care>Memory is an easy way to see what apks are cached. If you clear it and it happens afterwards you can easily see what apks were just cached.
PD MDM package disabler can be used to block a suspect package or clear it's data or cache.
It can completely clear the data, App Settings can not.
Apparently the latter leaves behind nulls or something that can still corrupt the data.
PD MDM is powerful tool useful for cleaning up messes but use it carefully...
Click to expand...
Click to collapse
Thanks for tips.
I haven't tried to stop all of the processes yet. There are a lot of them. I will finish it today.
If the bug isn´t shown, I can do anything or open all apps and it is still ok. Bug comes when I lock the screen and display goes to turn off. When I unlock the phone, one time it is ok, second not and still around...
Bug doesn´t show spontaneously during using phone - bug still precedes lock screen.
I received a new update of the system now and it looks like a fix of my problem. I tried all possibilities and bug doesn't show yet
https://photos.app.goo.gl/BinpgKL3U8sFzcy38
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
there's the screen im talking about, when you even touch the phone that screen seems to happen for you not to even touch the screen to input the fingerprint.
i've walked the whole config and found nothing.
it's deffinitely NOT the raise to wake, it's somethign else, but i dont know if its even workaroundable otherthan disaling the FPR which i dont want to.
Did a quick search and found there is an ADB command to disable it. I haven't tried it, so I am not sure if it works or if there are any issues that come up after running it, but if you want to check it out here you go
https://www.reddit.com/r/GooglePixel/comments/qvper2
robertbarber said:
Did a quick search and found there is an ADB command to disable it. I haven't tried it, so I am not sure if it works or if there are any issues that come up after running it, but if you want to check it out here you go
https://www.reddit.com/r/GooglePixel/comments/qvper2
Click to expand...
Click to collapse
Thanks robert !
found this one also will try that one out.
i really really appreciate it.
I think I am missing something....thats a setting in Lock Screen....
cmh714 said:
I think I am missing something....thats a setting in Lock Screen....
Click to expand...
Click to collapse
I'm confused also. That just looks like the aod. What's the problem here?
You mean that you have AOD off, and when you touch the screen you want to go directly to homescreen instead of the AOD, right?
The behavior on mine is exactly this one, I would like to have the AOD instead...
That "quick pickup" BUG has been really annoying me. It started with the december update -- did not exist before then. Glad to see a solution for it.
96carboard said:
That "quick pickup" BUG has been really annoying me. It started with the december update -- did not exist before then. Glad to see a solution for it.
Click to expand...
Click to collapse
the bug is from nov, or maybe from beginning.
Is this about the phone screen constantly waking up whenever you touch the phone, regardless of whether you have disabled things like Always On Display and all the gestures like "Lift to wake phone"? If so, there's a fix you can use through ADB. I found this solution on reddit, and it's worked perfectly for me. No downsides.
Code:
adb shell settings put secure doze_quick_pickup_gesture 0
Found the solution from this reddit thread:
https://www.reddit.com/r/GooglePixel/comments/qvg2nz/_/hkx0fiv
Perhaps I'm a little OT, but can you please help me which settings/adb commands should I use?
I have the AOD set to off, I would like that my phone shows the ambient display of first post when I lift the phone or touch the screen.
Thanks!
gpvecchi said:
Perhaps I'm a little OT, but can you please help me which settings/adb commands should I use?
I have the AOD set to off, I would like that my phone shows the ambient display of first post when I lift the phone or touch the screen.
Thanks!
Click to expand...
Click to collapse
Try going to Settings -> System -> Gestures. In there, toggle the Lift to Check and Tap to Check options.
vlubosh said:
the bug is from nov, or maybe from beginning.
Click to expand...
Click to collapse
No, didn't exist at the beginning. Started with December.
While the options are there to deactivate it I find it far too sensitive to the slightest touch sets it off
96carboard said:
No, didn't exist at the beginning. Started with December.
Click to expand...
Click to collapse
Existed since my phone arrived in October. Adb command fixed it.
btonetbone said:
Try going to Settings -> System -> Gestures. In there, toggle the Lift to Check and Tap to Check options.
Click to expand...
Click to collapse
Yes, thanks, I did this, and when lift to check is set OFF, I have the ambient display when I lift up the phone, and this is OK for me. But if I enable Tap to check, the phone goes to homescreen, if I disable it the screen remains dark.
The usual things (integrated solutions or the many ideas I found online) do not work. I don't want to permanently disable it but I am absolutely annoyed to constantly have to unlock it while i'm just at home.
I want Automate to have it off while home and on while outside. Such a simple task and yet so complicated :-(
(Smart-Lock doesn't work at all for me. Never had on any phone.)
Maybe someone has found a solution?
Set lock_screen_lock_after_timeout to any longer value. I have created a task that runs after every boot which sets this value. You phone will never be locked. Make sure you uncheck Settings -> Security -> Screen lock -> Power button instantly lock.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Kodijack said:
^^
Click to expand...
Click to collapse
ram4ufriends said:
Set lock_screen_lock_after_timeout to any longer value. I have created a task that runs after every boot which sets this value. You phone will never be locked. Make sure you uncheck Settings -> Security -> Screen lock -> Power button instantly lock.
Click to expand...
Click to collapse
Perfect! Damn, could've thought of that...I was so fixated on totally disabling it
Thanks man, helped a lot!
probably using this you can use your locations to enable or disable....
lockscreen.disabled=0
cmh714 said:
probably using this you can use your locations to enable or disable....
lockscreen.disabled=0
Click to expand...
Click to collapse
What does this setting do?
ram4ufriends said:
What does this setting do?
Click to expand...
Click to collapse
pretty sure it will enable or disable the lockscreen....
you can use this Task from TaskerNet to dump the contents of the 3 files where the settings are stored:
Tasker Share
taskernet.com
cmh714 said:
probably using this you can use your locations to enable or disable....
lockscreen.disabled=0
Click to expand...
Click to collapse
Sadly this was amongst the things I've already tried, but alas: Nope. Simply does nothing (for me).
Kodijack said:
Sadly this was amongst the things I've already tried, but alas: Nope. Simply does nothing (for me).
Click to expand...
Click to collapse
I just tried this and it didn't work for me either. But I have been using my solution for couple of years and it always works fine for me.
This is basically the one I use. Keeps your phone unlocked when connected to your WiFi at home and enables lockscreen when disconnected from your home Wifi when away from home.
Disable and enable your lock screen at will (No Root!)
Learn how you can make your phone lock when the screen turns off only when you're not at home
forum.joaoapps.com
Lughnasadh said:
This is basically the one I use. Keeps your phone unlocked when connected to your WiFi at home and enables lockscreen when disconnected from your home Wifi when away from home.
Disable and enable your lock screen at will (No Root!)
Learn how you can make your phone lock when the screen turns off only when you're not at home
forum.joaoapps.com
Click to expand...
Click to collapse
and its from Joao so you cant go wrong!
Lughnasadh said:
This is basically the one I use. Keeps your phone unlocked when connected to your WiFi at home and enables lockscreen when disconnected from your home Wifi when away from home.
Disable and enable your lock screen at will (No Root!)
Learn how you can make your phone lock when the screen turns off only when you're not at home
forum.joaoapps.com
Click to expand...
Click to collapse
Ah thank you, another option that will work. Thanks for sharing!
If you don't want to go down the tasker route,
Macrodroid with _Screen unlock at Home does the job.
Just change the SSID in the template. (Parts 1 and 2 needed)
What about on first boot? Don't you need to enter a password then? I want to bypass the password always, even after a reboot. Is there no way to have Tasker auto-login when the lock-screen is shown?
NOTE: I do have lockscreen set to Swipe, but that causes multiple issues which is what I am trying to fix... 1) No VPN without a lock, 2) No GPay without a lock, 3) Can't view Chrome saved passwords without creating a lock. Therefore disabling the lock at home is not a solution for me. I want it always disabled (swipe to unlock), but I want 1, 2, & 3 to work anyway.
PS: Here is how to do the timeout thing without Tasker... I will try that out for now, as it should solve everything except reboot (maybe I can live with that).
Code:
adb shell settings put secure lock_after_timeout_rollback 86400000
adb shell settings put secure lock_screen_lock_after_timeout 86400000
86400000 = 24 hours in miliseconds. You can change to a number that you find suitable.
This secure settings will survive after reboot so you only need to do once.
Kodijack said:
cmh714 said:
probably using this you can use your locations to enable or disable....
lockscreen.disabled=0
Click to expand...
Click to collapse
Sadly this was amongst the things I've already tried, but alas: Nope. Simply does nothing (for me).
Click to expand...
Click to collapse
Shouldn't it be
lockscreen.disabled=1
0 = false -lockscreen.disabled=0 =false =lockscreen.disabled=NO
1 = true -lockscreen.disabled=1 =true =lockscreen.disabled=YES
[RANT / Question]
I simply can't believe that there is no PERMANENT SETTING to disable bluetooth discovery in my TCL Android TV (with version 11 right now).
If there is already a solution in the forums, I didn't find it, so sorry in advance and point me to the thread, please.
Do anyone know a way to PERMANENTLY DISABLE bluetooth discovery? With ADB or something?
(for example on my grandma's TCL TV too, that she won't use any bluetooth device apart from the remote, so she doesn't need her TV to be available for pairing constantly and receiving requests from neighbors).
Bluetooth discovery "enables itself" from time to time no matter what you do. I already know "Bluetooth Discovery Disabler" app, but it's no permanent solution.
It's infuriating, at least for me.
Sorry for the rant. Thanks for any help.
Me too. Please help. I just had this very issue where some jackass kept trying to pair with my tv interrupting our movie. I am beginning to regret getting my Android TV.
xeradas said:
Me too. Please help. I just had this very issue where some jackass kept trying to pair with my tv interrupting our movie. I am beginning to regret getting my Android TV.
Click to expand...
Click to collapse
It's incredible! I can't believe there isn't a PERMANENT solution. What I do, that may be useful for you in the meantime, is EVERY TIME I turn on my TV, I use the app "Bluetooth Discovery Disabler", that I pinned on the Home in the TV to check if BT discovery is enabled or not.
Other thing to consider is that, if you use the optimization app that close unused apps for better performance, the setting of the BT discovery gets to default, so, you should "enable and disable" the setting again after using the optimization app to be sure that it is disabled.
I really hope that, AT LEAST, they should add the option in the "developer options" if they are unsure about "less tech savvy people", so you BET that I WANT THAT OPTION if I go there to use it...
Firmware V8-R51MT05-LF1V508........
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
i was about to remove the whole wifi/bt module from the tv to fix that but i'm unable to locate it, it's on the main circuit board? or maybe it's in the bottom part of the tv?
well i found out that you can simply force disable bluetooh apk with adb, rebooot the tv and then bt is fully off
adb shell cmd package disable-user com.android.bluetooth
stasiof said:
Firmware V8-R51MT05-LF1V508........
Click to expand...
Click to collapse
I don't have that firmware. In my country is different. Here you have always bluetooth enabled without the possibility of disabling, BUT you can disable "Bluetooth Discovery", but only temporarily, as my post explain.
Thank you anyway!
blinkycan said:
well i found out that you can simply force disable bluetooh apk with adb, rebooot the tv and then bt is fully off
adb shell cmd package disable-user com.android.bluetooth
Click to expand...
Click to collapse
I'm interested in trying this!
I would apply this in my grandmother's TV, that she won't be using Bluetooth whatsoever.
However I would like to check if the remote control keeps working well, because (if I'm not mistaken), it works with infrared as a classic remote and at the same time has Bluetooth capabilities, but I think them are for "Assistant" and that things that my grandmother doesn't use, of course. If she can still turn on the TV, change channel and volume (and if "home button", etc. still works for basic functionality), is enough.
Does your remote still work normally?
Thank you very much for your input. We may be getting somewhere with this!
they finally added a bluetooh toggle in the latest update of my TCL and no the bluetooh remote do not work with bluetooh off i just use the second remote that came with the tv this one use infrared and the other is bluetooh
blinkycan said:
they finally added a bluetooh toggle in the latest update of my TCL and no the bluetooh remote do not work with bluetooh off i just use the second remote that came with the tv this one use infrared and the other is bluetooh
Click to expand...
Click to collapse
Thanks for the answer!
In the infrared one, can you -for example- move with the pad, press OK, press "Home", "Setup", etc. with bluetooth disabled by ADB (if you tried before the update)?
Just to clarify, sorry for the insistence.
I will look however for the command to counter the disabling with ADB, just in case. And will try your solution in my TV before my grandma's.
Thank you very much!