Question android 13 bluetooth issues fix - Samsung Galaxy Z Fold3

Hey all,
I have had issues with my smartwatch since updating to android 13, and I have seen others having simmer issues. I have found a fix!
Go to
Settings > Apps> turn on Show system apps
Scroll to Bluetooth
Tap Battery
Set it to Unrestricted
That's it, my bluetooth devices work as intended now

Thanks! I was also going through the same problem and the above solution helped me fix it.

Related

Noob [Q] Help choose ROM that fixes Bluetooth problem (and is close to stock)

Hi all,
I'm having problems keeping my Galaxy Note 2 (GT-N7100) in contact with my Pebble Time Steel and other Bluetooth devices. It appears to be related to the Bluetooth LE function in Android 4.3, as discussed at androidpolice.com/2014/05/20/bug-watch-bluetooth-will-begin-crashing-after-encountering-too-many-ble-devices-affects-kitkat-4-4-and-jelly-bean-4-3/ (sorry, can't post link because I'm new here).
Basically the Note keeps a list of all the Bluetooth IDs that have ever connected to it, and that list has a limited size. Once it's full, the Bluetooth program keeps crashing (and disconnecting my Bluetooth devices), with the message "Unfortunately Bluetooth Share has stopped." until I reboot the phone. That helps for a few hours, but then it starts again. Lately I've just kept Bluetooth off.
I've tried the Bluetooth Crash Resolver app by Radius Networks, but it doesn't seem to make a difference. I understand that the latest official Android firmware released by Samsung for the Note 2 (4.4.2) still has this bug. According to the page I linked, the bug was fixed in Cyanogen 10.2 and its descendants.
So I guess I get to dip my toe into the exciting world of Note 2 mods. In the first instance, I'd like to get something pretty much the same as the Samsung Touchwiz experience I'm using now, just with the Bluetooth bug fixed. But even with mods that include Touchwiz stuff, how do I know whether they have fixed the Bluetooth bug?
Thanks in advance,
Buzko

Enable / disable bluetooth turns off bluetooth tethering?

Hello,
First: All apologies for the lack of english skills.
My device is a stock HTC 10 in grey. No branding.
Android Version: 6.0.1
Patchlevel: 1. August 2016
Software number: 1.95.401.4
Description:
In order to use my TomTom go500 navigation system in the car properly i have to enable a bluetooth network connection for it. I am getting traffic data through this. And the device connects to some other sort of online services also.
Issue with the HTC10:
- I enable Bluetooth.
- I go to settings and enable bluetooth tethering.
- (At this point my navigation system can communicate fine).
- Now i drove like 160 kilometres to Bodensee and left the car.
- Turned off bluetooth.
- Went around Bodensee and took many pictures and did some other crazy stuff.
- Got in the car again.
- Turned on bluetooth.
- Ran into heavy traffic on my way home until i noticed i got no traffic data.
- Blamed my TomTom
- Found out the Issue was that Bluetooth tethering got turned off automatically.
- Decided to not blame my HTC10 but ask if others had the same issue or a possible fix?
Do you?
In short the title says it. Do you have the same issue? A fix? Do you know if that is reported to HTC already and if it is maybe being worked on?
Many thanks!
Greetings,
R
revealed said:
Hello,
First: All apologies for the lack of english skills.
My device is a stock HTC 10 in grey. No branding.
Android Version: 6.0.1
Patchlevel: 1. August 2016
Software number: 1.95.401.4
Description:
In order to use my TomTom go500 navigation system in the car properly i have to enable a bluetooth network connection for it. I am getting traffic data through this. And the device connects to some other sort of online services also.
Issue with the HTC10:
- I enable Bluetooth.
- I go to settings and enable bluetooth tethering.
- (At this point my navigation system can communicate fine).
- Now i drove like 160 kilometres to Bodensee and left the car.
- Turned off bluetooth.
- Went around Bodensee and took many pictures and did some other crazy stuff.
- Got in the car again.
- Turned on bluetooth.
- Ran into heavy traffic on my way home until i noticed i got no traffic data.
- Blamed my TomTom
- Found out the Issue was that Bluetooth tethering got turned off automatically.
- Decided to not blame my HTC10 but ask if others had the same issue or a possible fix?
Do you?
In short the title says it. Do you have the same issue? A fix? Do you know if that is reported to HTC already and if it is maybe being worked on?
Many thanks!
Greetings,
R
Click to expand...
Click to collapse
I did not encounter this since i did not use bluetooth tethering. Just tested it, activated bluetooth, then activated tethering and deactivated bluetooth which in turn deactivated tethering. Wouldn't call this a bug, seems more like common sense to me that deactivating bluetooth also deactivates bluetooth tethering.
If i'd stop watering my plants until they are dried out, then start watering them again i do not think "man, why won't they grow"
*sorry for the non-technical example, it's late and this was the best i could come up with
Hi there
Sure, turning BT back on the tethering still keeps turned off. It worked with my HTC One S. It just remembered my setting. This is the fourth HTC smartphone i own. And i'm just used to this until now.
I would have expected it to behave like remembering my settings. What i understand already is that the visibility option happens automatically.
It is a bit annoying that i have to walk through several menus to reactivate Bluetooth-Tethering. Ehm in the meantime i found a bugreport on via online research. (All my excuses for the external link):
https://code.google.com/p/android/issues/detail?id=161031
Some mentionings are no resolution there until now. I guess this is up to the devs. And i think many ppl have this issue. Not just HTC10. I hope they make this work again.
Also i will try the there mentioned workaround with a tool from the market.
Many thanks for your help!
Greetings,
R
I just wanted to popp in and say that i chatted with the support at HTC website. They let me boot the HTC10 in safe mode and asked me to reproduce the issue.
I reproduced it instantly. Further we sorted the steps to reproduce to full understanding.
The HTC employee forwarded the issue to the dev team.
Further i was informed that i will receive information on this issue in future.
Greetings,
R

Android Auto not working on Android 10

After the android 10 ota update, i can't open android auto on my pixel. it shows in my apps but there is no icon installed on my phone(I am not rooted).
Any work around solution?
You'll find it under Settings, Google, Android Auto
If you're coming from a fresh 10 install, set it to auto start when connecting to a bluetooth device - either via what bullfinch110 said or go to Nova Launcher and create a shortcut to Android Auto Settings. But it has to be connected to that Bluetooth device otherwise it won't run. Otherwise take OTAs from Pie and it will remain as a launchable app.
So I had a issue with Android Auto on Android 10... My vehicle has the head unit JVC KW-M845BW and I couldn't get the android auto interface to pop up after installing Android 10. In Pie, I could just go into the app and turn on the bluetooth auto start up setting when the car started. Now that the app is not available to open, you have to hope starting the head unit will pull up Android Auto... In my car, I have to set the parking break to get Android auto app to pop up on Android 10 for the first time installation. After that, the app pops up on my head unit every time.
I've come across the same issue today - relocked my bootloader and on reboot and setup I can't locate the app. Play store says it's installed but it's not listed as installed on the phone. Sideloading the APK doesn't change this. I'm not using an AAuto headunit, gut using the phone as the display for my BT headunit.
Have force stopped the launcher, flashed the latest image, rooted, unrooted... I'm about to move to a Pie rom to see if it carries on
Someone has managed to use android auto on a Toyota C-hr?
Android Auto is now an integrated app in Android 10. You can trigger it either with a Tasker task or when connecting to a bluetooth device:
Go to settings > apps > android auto > additional settings > autolaunch with bluetooth, and set the app to autolaunch whenever it connects to your car's bluetooth.
Same issue here, but there is no "Autolaunch" option in settings for Android Auto version 5.0.500214. Any idea?
Trottel said:
Same issue here, but there is no "Autolaunch" option in settings for Android Auto version 5.0.500214. Any idea?
Click to expand...
Click to collapse
My phone is on 4.9.594934 and it still has autolaunch. Playstore doesn't show a new DL for the app. I would uninstall the version and install an early version.
jlokos said:
My phone is on 4.9.594934 and it still has autolaunch. Playstore doesn't show a new DL for the app. I would uninstall the version and install an early version.
Click to expand...
Click to collapse
Even in 4.9.594934 I have no autolaunch option
Trottel said:
Even in 4.9.594934 I have no autolaunch option
Click to expand...
Click to collapse
Do you have the AA app on the phone? If not try this, go into settings>apps & notifications>AA>advanced>additional settings in the app; this will open up AA settings. Go o phone screen settings>autolaunch.
jlokos said:
Do you have the AA app on the phone? If not try this, go into settings>apps & notifications>AA>advanced>additional settings in the app; this will open up AA settings. Go o phone screen settings>autolaunch.
Click to expand...
Click to collapse
It looks like AA is installed, but in the Settings>Apps & Notifications I can only deactivate the application or uninstall updates. I assume this is because AA is preinstalled on Nokia 7 plus with A10. However, I do not see the icon in the installed applications. There isn't even a choice of Phone screen settings in Additional Settings in the App. Is it possible that this is due to the fact that AA is not officially supported in the Czech Republic?
Sorry, Android auto for phone screens solved it.

Question Is %UIMODE in Tasker broken for anyone else?

I had a profile triggered by %UIMODE when I connected to Android Auto. It was working fine on my S21 Ultra but it doesn't seem to work on the 6 Pro. Is it a Pixel, Android 12, or me issue?
I have the same problem... Google Pixel 6
RockManX77777 said:
I had a profile triggered by %UIMODE when I connected to Android Auto. It was working fine on my S21 Ultra but it doesn't seem to work on the 6 Pro. Is it a Pixel, Android 12, or me issue?
Click to expand...
Click to collapse
I have a Pixel 5 and it happened after the Android 12 upgrade, so it's probably that. I couldn't find a way to report a bug, tried the Google group but don't have permission to post.
I had the same issue. Been using uimode for my tasker profile forever. This obviously no longer works in Android 12. But after spending a bit of time, I found a workaround! Not pretty, and it requires a third party app, but hey it works. I have always had a start and exit task. When Android Auto runs, Bluetooth, location, etc enable. When I unplug, all of those things turn off. Of course, the trigger for this profile was uimode=car. Anyways, I was able to change the trigger to use autonotification instead. This tool must be purchased. It's from the autoapps developer. Replaced my trigger with a State (do not use Event, even if the app tells you otherwise) --> Plugins --> Autonotification --> Intercept. Then hit the configuration button. Scroll down to Apps. Then choose Android Auto. That's it. Works like a charm. I originally had the notification text in there, but changed to the app only. Important: the reason to use a State rather than an Event is due to the fact that tasker cannot have an exit task with an Event.
contact the author of Tasker... pretty responsive to fixes
Here's a workaround that works until João Dias fixes it for Android 12 in his next release of Tasker Beta
Simple profile to react to notification from Android Auto connecting.
Tasker Share
taskernet.com

Question The new Android 12

I have a few questions regarding the new update.
1. Does region matter?
I have a RETEU device, is there a reason why flashing the RETBR wouldnt work?
2. Is it worh it? Are the features (mostly design and privacy interest me) Android 12 promised there and functional?
3. How is the battery life on it?
I would love if you guys could help me out since i am very exited about the new features!
Also is there a Third Party Android 12 ROM, or GSI or something, any of you guys have used and recommend that is somewhat functional as a daily driver?
Thanks and much love!
No harm in waiting... 12 is a mess across all devices.
I bailed with Adroid 10 and don't regret spurning 11 and up one bit. CPU cycle sucking scoped storage became mandatory with 11; 12 is likely worse. I would research this first.
KAN7A said:
I have a few questions regarding the new update.
1. Does region matter?
I have a RETEU device, is there a reason why flashing the RETBR wouldnt work?
2. Is it worh it? Are the features (mostly design and privacy interest me) Android 12 promised there and functional?
3. How is the battery life on it?
I would love if you guys could help me out since i am very exited about the new features!
Also is there a Third Party Android 12 ROM, or GSI or something, any of you guys have used and recommend that is somewhat functional as a daily driver?
Thanks and much love!
Click to expand...
Click to collapse
Hey,
short feedback from my experiences since upgrading to Android 12 in Germany.
1. Sorry, no idea.
2. Privacy features seam to work fine. Only problems I experienced are the following.
- You can now deny new / formerly hidden permissions. Denying them can brick apps. (example denying the "alarm / reminder" permission bricks the app "Notebook" until permission is granted again).
- All quick access setting have to be sorted again.
- new "deny all microphone access" in quick setting does what it should. For me it did it's job too literally. My interpretation "deny all apps except calling" but all MEANS all (yeah I know obvious... duh....).
3. Haven't performed any special comparisons but it feels same or maybe even a bit longer.
blackhawk said:
No harm in waiting... 12 is a mess across all devices.
I bailed with Adroid 10 and don't regret spurning 11 and up one bit. CPU cycle sucking scoped storage became mandatory with 11; 12 is likely worse. I would research this first.
Click to expand...
Click to collapse
Hi,
to be honest, I have no idea what you mean. I guess I'm too much of a noob regarding Android internals. I mean no offense. Would you be so kind to briefly explain this? Thanks
--------
Some of my own experiences / questions.
Background:
I'm using my device with the work profile to keep annoying apps at bay.
Using "Shelter" app.
Using "Aurora Store" in work profile to install apps.
No factory reset was performed since upgrade.
Not rooted.
Problem:
Since the upgrade to Android 12 I'm experiencing an quite annoying bug. Using the "phone" app (private profile) I have no sound and microphone sometimes. So I can't hear and can't be heard. If I'm activating the work profile and use the "phone" app (again from private profile) I suddenly have sound and microphone.
Fix / workaround:
Another way to "fix" this problem is to reboot the phone. After reboot it works for an undefined time. I haven't tested if the problem starts after using work profile and deactivating it again. I'm testing it and I'll try to not forget to post an update for others.
FYI:
BTW if sound from other apps does work, wasn't tested until now. If you need to call you normally have no time for testing, so reboot it was for me.
Tested solutions:
Tested some general "solutions" from REDDIT & Co.
Editing settings in "Sound & vibration" -> "Audio effects": recommended "activate Dolby ATMOS". Phone doesn't have that so i resetted the setting (after tapping "Audio effects" tap "Settings" at the bottom then tap 3 dot menu and tap "Reset")
- DIDN'T WORK
Suggestion it's a carrier problem
Set network selection to manual and select your corresponding network.
- DIDN'T WORK
Deactivate or activate "Wi-Fi calling". (mine was activated so I deactivated it)
- DIDN'T WORK
Enable or disable "VoLTE". (mine was activated so I deactivated it)
- DIDN'T WORK
My questions:
Is anyone else experiencing this problem?
Has anyone found a solution?
The_Naudiz said:
Hey,
short feedback from my experiences since upgrading to Android 12 in Germany.
1. Sorry, no idea.
2. Privacy features seam to work fine. Only problems I experienced are the following.
- You can now deny new / formerly hidden permissions. Denying them can brick apps. (example denying the "alarm / reminder" permission bricks the app "Notebook" until permission is granted again).
- All quick access setting have to be sorted again.
- new "deny all microphone access" in quick setting does what it should. For me it did it's job too literally. My interpretation "deny all apps except calling" but all MEANS all (yeah I know obvious... duh....).
3. Haven't performed any special comparisons but it feels same or maybe even a bit longer.
Hi,
to be honest, I have no idea what you mean. I guess I'm too much of a noob regarding Android internals. I mean no offense. Would you be so kind to briefly explain this? Thanks
--------
Some of my own experiences / questions.
Background:
I'm using my device with the work profile to keep annoying apps at bay.
Using "Shelter" app.
Using "Aurora Store" in work profile to install apps.
No factory reset was performed since upgrade.
Not rooted.
Problem:
Since the upgrade to Android 12 I'm experiencing an quite annoying bug. Using the "phone" app (private profile) I have no sound and microphone sometimes. So I can't hear and can't be heard. If I'm activating the work profile and use the "phone" app (again from private profile) I suddenly have sound and microphone.
Fix / workaround:
Another way to "fix" this problem is to reboot the phone. After reboot it works for an undefined time. I haven't tested if the problem starts after using work profile and deactivating it again. I'm testing it and I'll try to not forget to post an update for others.
FYI:
BTW if sound from other apps does work, wasn't tested until now. If you need to call you normally have no time for testing, so reboot it was for me.
Tested solutions:
Tested some general "solutions" from REDDIT & Co.
Editing settings in "Sound & vibration" -> "Audio effects": recommended "activate Dolby ATMOS". Phone doesn't have that so i resetted the setting (after tapping "Audio effects" tap "Settings" at the bottom then tap 3 dot menu and tap "Reset")
- DIDN'T WORK
Suggestion it's a carrier problem
Set network selection to manual and select your corresponding network.
- DIDN'T WORK
Deactivate or activate "Wi-Fi calling". (mine was activated so I deactivated it)
- DIDN'T WORK
Enable or disable "VoLTE". (mine was activated so I deactivated it)
- DIDN'T WORK
My questions:
Is anyone else experiencing this problem?
Has anyone found a solution?
Click to expand...
Click to collapse
Great formating and great feedback! Thanks so much!
The first point seems irrelevant anyways since the update is now for RETEU too.
I might try to upgrade tonight but i might wait a bit since i try and degoogle my phone as much as i can so i will probably soft brick it once or twice.
If I run into any of the issues you have i will come back with more feedback!
Regarding what BlackHawk said, from my understanding somehow the new scoped storage feature ( that allows apps to have access to only selected files and folders instead of device wide storage access) somehow messes with the CPU.
He most likely knows more but thats just my basic understanding and interpretation of what he said.
Thanks again and have a great day!

Categories

Resources