Hello all, I'm trying to resolve my Bluetooth issues, but when I change the Bluetooth settings in developer settings, they do not stick. They just revert to the previous settings. Does anyone know how to fix this?
I really like this phone, but if I can't resolve the Bluetooth issue, it's not worth keeping.
The device doesn't support the setting change is the most likely cause.
Try toggling Developer options off and then enabling it again. Also try a reboot, clear system cache if you have that option.
Related
Hi guys,
I own a Blackview Crown with the latest SW released (20141015).
I noticed that randomly during the day the audio profiles and the data settings for the dual SIM management are reset to the default values.
For example: I set "screen lock sound" and "vibrate on touch" to OFF and they are set to ON automatically by the system.
In contemporary the bug affects also the data connection settings on the DUAL SIM management menu... it is switched from one SIM card to the other one (and this is the most annoying problem...).
Do you know whether this can be a known problem? Or maybe this is an Android bug?
I already tried to write to Blackview.hk but received no answers so far...
Thanks a lot for your help!!
PS you know whether there is a LOG that can be activated to understand what is happening? this issue does not happen during system reboot... it happens really randomly, every 1-2 days
I found that the settings reset is caused by the Android "POWER SAVING MANAGEMENT" function.
When the "POWER SAVING MANAGEMENT" function is enabled many services are stopped to save power (like data connection or ringtone volume for example). When the "POWER SAVING MANAGEMENT" function is disabled, the settings are set at the default values (such as "high precision" GPS or "vibrate on touch"). The customized settings are lost.
I do not know whether this is a Crown-related issue or it's common to all the Android 4.4.2 users.
hi everyone, in developer options, 'do not keep activities' wont turn off!, everytime i untick it, when i close the developer options, it then enables it again, and its causing app crashes and slow touchwiz, so has anyone got any ideas how to turn it off please?
Searching around isn't tuning up anything useful, but I cannot change any administrator settings. I can't activate or deactivate any apps on that screen. Am i missing something simple? So frustrating....
I figured it out....spent half the day trying to figure this out.....if you add another user it fixes this issue. Now I am able to activate and deactivate on the owner profile as well as the dummy profile I created.
Hi all,
apparently this seems to be a known bug (feature) of the S9, at least I found several reports on different forums, however without any solution so far.
The problem: It is not possible to activate both, the accessibility option for an app (e.g. for Nova Launcher, Tasker or BixBye) and the secure start / secure boot option (official name might be different - I'm talking about the option that requires you to enter your PIN / passphrase before your phone boots).
Whenever I try to enable one of the accessibility options, secure start is switched off.
Is there any workaround for that?
Thanks and cheers!
hunchi
/edit: I forgot to mention that I never experienced this problem on my S7.
On my AT&T S7 Edge, and my AT&T S9+, I just go into the Security Settings and turn Secure Startup back on. It warns that the accessibility services won't be available until the phone fully boots.
I just found an interesting solution to prevent wifi getting disabled on a device without root. I am just beginning to test this now, so this may have battery consequences, but it seems to work as desired on my fossil sport. If there is the key "cw_disable_wifimediator=1" in global settings, then the wifi will never turn off. The user can change the setting to disable wifi, but this will have no effect on wifi connectivity. Same with airplane mode. Interesting. This change also survives device restarts.
To add this setting, you can do
adb shell settings put global cw_disable_wifimediator 1
I don't know if you can do it from an app (maybe with write_system_settings), but I'll keep testing this in the future.
Yep, can be done at least with granted permission WRITE_SECURE_SETTINGS.
Settings.Global.putInt(contentResolver, DISABLE_WIFI_MEDIATOR_KEY, 1)
I did it accidentally... I moved my watch from one phone to another (guide online). But it stuffed up Bluetooth so it only connected via wifi. Battery was worse so I just reset the watch like you're supposed to.
so good
I just found this thread searching for a solution to this problem...
Android 12 Developer options adb "Wireless debugging" option keeps turning off
The question I'd like to ask those who tried this ... is...
Q: Is there any way to KNOW (after the fact) that you've permanently turned off the ability to turn off the Wi-FI?
How do you turn it back on if you need to?
GalaxyA325G said:
I just found this thread searching for a solution to this problem...
Android 12 Developer options adb "Wireless debugging" option keeps turning off
The question I'd like to ask those who tried this ... is...
Q: Is there any way to KNOW (after the fact) that you've permanently turned off the ability to turn off the Wi-FI?
How do you turn it back on if you need to?
Click to expand...
Click to collapse
Code:
adb shell settings get global cw_disable_wifimediator
to get the status. Whether or not the feature works as intended, I don't know - I'm going to test it myself.
Code:
adb shell settings get global cw_disable_wifimediator 0
to disable this feature and re-enable the auto setting.
GalaxyA325G said:
I just found this thread searching for a solution to this problem...
Android 12 Developer options adb "Wireless debugging" option keeps turning off
The question I'd like to ask those who tried this ... is...
Q: Is there any way to KNOW (after the fact) that you've permanently turned off the ability to turn off the Wi-FI?
How do you turn it back on if you need to?
Click to expand...
Click to collapse
I have the same issue you have, have you got it to work yet as intended?