Database Users

Bluetooth wont turn on

Hello
I am on stock 4.2.2 non rooted
Bluetooth doesnot turns on for me..but after doing a reboot it starts
Edited (Possible Cause
I had Snapdragon Battery Guru installed and i uninstalled it and now bluetooth is fine..does not require a reboot anymore..

Same here...
Google and you will see your not the only one.
Reboot is the only solution at the moment.

Had the same issue, but only once. Also solved that by doing a reboot. It didn't happen again (until now).
If anybody knows the reason, would be great.
Schm1dt
Edit: Android 4.2.2 - built JDQ39

this happened to me as well on wednesday. i had to reboot my phone and it seemed to fix the problem.

[Q] Cant turn on NFC

Hello everybody,
month ago i tried this mod for NFC Lockscreen (http://forum.xda-developers.com/show....php?t=2285978). I flashed it to my phone and clicked on turn on NFC, but just slider changed to NFC ON, but this icon on panel on top wasnt there and NFC doesnt work. I dont know how to repair it, because i have no backup...
Thank you for you help!

Solved in service...

*Thread hijacked*
Hey guys. I'm from the S4 mini forums and came here to help solve our problem as we are only a small community.
Basically a kernel was made for stock rom enabling BLN and other mods but since flashing that, it has disabled our NFC (tries to turn on).
Even after flashing/factory resetting and changing firmware doesn't solve the problem.
I have managed to come up with a temporary fix by replacing "nfc_nci.msm8960.so" located in system/lib/hw from CM rom. Soon as we flash a fresh firmware via Odin, the problem comes back.
Does anyone have a rough idea what this kernel may have caused for this to happen?
Hope to hear some feedback soon as we are all getting rather frustrated over this matter.
Thanks people and Merry Christmas!

[Q] system crashing Omega21&22

hi,
yesterday i thought it is Tasker wifi issue or something but after flashing Omega21 and Omega v22 (without tasker) a couple of times I noticed when i installed Xposed instaler and activate Youtube adaway, Wanam, Greenify system just crashes after few minutes or even bootloops for some time. :crying:
So i hardly managed to get catlog from my phone filtered only for errors and from PC logcattool a loooong log. restored my original EFS still having this issue. been using leankernel 3.6 some time with omega rom and recently upgraded it to 3.7 so maybe some connection i dont know...now I am stuck....
any help much appreciated

WiFi Bluetooth not working after Xposed Update

Hi guys,
I've been stuck with this problem for a month. PLEASE HELP otherwise I have to get rid of the phone...:crying:
I was on IMPERIUM 10 with XPOSED Framework active. One day it asked for an update of one of the standard module (I cant remember which one). After the process completed, I wasnt able anymore to use Wifi and BT. Even after reverting the module to the previous version or disabling XPOSED. Sometimes I could use WiFi and BT after a reset for a while, but again they turned off.
I've tried to reinstall IMPERIUM with full wipe, other SAMSUNG ROMs with XPOSED and CM11 (w/o XPOSED) but nothing. Besides, I've tried several modems (with ODIN) and NO SUCCESS as well.
Do you have any suggestion PLEASE?

[Q] "Dream Manager Service" keeps waking the screen up, how do I disable it?

[Q] "Dream Manager Service" keeps waking the screen up, how do I disable it?
I've looked for other posts on this issue, but none helped me very much. I have a Samsung S5 (international, sim-free), I recently flashed Phoenix Rom, version 6.3, build BOC7. Was on Omega Rom BOB7 previously. I'm also on BOB7 bootloader and modem. Don't know if it's relevant, but I'll mention it anyway. I don't have a PC, so it's difficult for me to use Odin, it's something I have to arrange days in advance. That's why I haven't updated bootloader or modem to BOC7 yet. And before anyone tells me to just go back to Omega Rom, Phoenix Rom is my absolute favourite Rom, it was my daily driver on KitKat, and I just discovered today that it had been updated to Lollipop, so I flashed it immediately.
Using Wakelock Detector immediately after booting, I find Android System, specifically "Dream Manager Service" the only thing which has woken the screen. So that seems to be the culprit, but I don't know how to kill it. It was never an issue before. Basic Daydreams (a Samsung process) is frozen via Titanium Backup. I don't use any other sort of daydream app or service.
It is clearly an issue with Phoenix Rom, but it didn't start until a few hours after I'd flashed it. So in the meantime something has happened, but I don't know what, and before I go through the hassle of reflashing it, I'd like to see how I could disable it. Things I've tried:
- Turning off ambient display - was not on when the problem started, I've tried turning it on and off, but doesn't help. I don't use it or want it, so I don't mind killing it somehow.
- Booting into safe mode. This helped, the problem did not appear when in safe mode. As far as I know though, it just doesn't allow "Dream Manager Service" to run. Not so helpful for finding out how to disable it.
- Revoking permission to "keep screen on" in App Ops for Android System. It seems to just ignore this, which seems to make the whole permission management thing a bit pointless.
When the screen does turn on, it looks different. The wallpaper is not displayed, and it's all in black and white.
Does anyone know why "Dream Manager Service" is doing this? And more importantly, how I can stop it? If you need any more information from me, just ask.
EDIT: Found reason: Ambient Display in Phoenix v6.3 was causing this bug, even after I turned it off. Downgraded back to 6.0, will skip 6.3 and wait for fix, hope it will be an option in the Aroma Installer next time.

Thank you! I found this information useful 2 years later in my Galaxy S7 running Ambasadii Nougat 7.0.