Database Users

Wifi Stuck w/Certain Roms.

Hi. I'm having wifi issues with my Nexus. It started after flashing MIUI. I was using TWRP to flash, it took a while for the google logo to disappear and to get to the Xiaomi bootlogo. After it finally booted, the wifi was stuck to "turning on", but never ultimately firing up(couldn't get it to turn on nor off, even having turning it off). I've also noticed that I have the same EXACT issue with CyanogenMod. I completely returned to stock, i've relocked the bootloader and everything. I tried CM installer today and i'm rooted again with CM, but still I have the same exact issues as before. I don't have these issues with some other roms such as stock, official Omnirom and such, i wouldn't think it would be exactly a hardware issue, since it works just fine with certain roms. Would anyone have an idea why my phone is having this issue? It wasn't always this way. Specifically, I haven't been having issues with 4.4 roms. Does anyone think it could be something related to bootloader, or something?

Juanito216 said:
Hi. I'm having wifi issues with my Nexus. It started after flashing MIUI. I was using TWRP to flash, it took a while for the google logo to disappear and to get to the Xiaomi bootlogo. After it finally booted, the wifi was stuck to "turning on", but never ultimately firing up(couldn't get it to turn on nor off, even having turning it off). I've also noticed that I have the same EXACT issue with CyanogenMod. I completely returned to stock, i've relocked the bootloader and everything. I tried CM installer today and i'm rooted again with CM, but still I have the same exact issues as before. I don't have these issues with some other roms such as stock, official Omnirom and such, i wouldn't think it would be exactly a hardware issue, since it works just fine with certain roms. Would anyone have an idea why my phone is having this issue? It wasn't always this way. Specifically, I haven't been having issues with 4.4 roms. Does anyone think it could be something related to bootloader, or something?
Click to expand...
Click to collapse
i have a similar problem... i rooted my nexus and flashed a custom rom (PACman) when it boots wifi is disabled, also bluetooth doesnt work neither any sounds, no music, no speaker, nothing, so i flashed Paranoid android (both based on 4.3) and i had the same problem
so then i flashed stock, everything ok, then CrDroid (based en 4.4) everything ok, then OmniRom (Based on 4.4) everything ok too...
i posted it here and got no replies, hope someone could help

Yes, right now I'm running an unofficial CM 11, and no issues. I wonder if something needs to be downgraded, in order for things to be okay again. I would still like the option to be able to run 4.2/4.3 based roms. Maybe I could try flashing to stock 4.2 or 4.3, then reroot, and test my results
Sent from my Nexus 4 using Tapatalk

What radio/baseband version are you using?

Hi, I'm using AOKP last nightly builds and since 2013-10-18 Wi-Fi started to stuck, settings ui errors and other problems. So I just tried franko kernel with official AOKP releases and Wi-Fi now is working fine. But i've faced skype problems). After 4 minutes it hangs and i need to restart my phone.

[Q] SM-G900F (Date & Time problem with [klte] 4.4.4 ROMS)

Hi all,
I've recently upgraded from a Samsung Galaxy S3 (i9300) to a Samsung Galaxy S5 (SM-G900F). Phone seemed to be working as desired so decided to go ahead, root, and install a custom ROM for enhanced functionality and customisation. Root process went smoothly, just running a simple CF-AutoRoot with Odin3 (voids KNOX, but no other problems), then installing PhilZ Advanced CWM Recovery.
From there I decided to install an unofficial build of CyanogenMod 11; found information on this forum. Flashing worked perfectly (and took rather little time!), but upon installation I noticed a strange problem. If I hard reboot (power off, power on) the device, with Wifi & Mobile Data off, the time and date are reset to incorrect values. Usually 01/01/xxxx and the time around 00:00. Same problem occurs even if when I turned off Network-allocated time and tried and set time manually.
The same problem occurred with other similar CyanogenMod based builds such as [AICP] and [AOSB]. I decided to restore back to the stock ROM and noticed that the clock and date were set correctly on reboot (and also on custom versions of 4.4.2 such as SpeedROMv7).
I checked with the terminal the value of the 'hwclock' (from BusyBox) and it reported an odd date somewhere in 1970, but different to the ones in found on CyanogenMod etc.
Does anyone have any idea what could cause this kind of problem and how to fix such an issue? If anyone wants any additional information about my device, please don't hesitate on commenting in this post. Would be grateful for any feedback. Thanks! :good:
PS: Also seem to be experiencing a problem with WiFi randomly disconnecting after a period of time. Not seen many threads with this said explicitly however. Problem with no voice in phone calls with headphones still persists but I've acknowledged that this is a known bug at the moment.
A.

Bump
*bump* // Problem still not resolved. Anyone know if it's device chain related?

Anyone?
AlfieJPalmer said:
*bump* // Problem still not resolved. Anyone know if it's device chain related?
Click to expand...
Click to collapse
Same Issue.

I have been encountering this very same problem for a while now, in fact, I am expriencing the same issue with my Galaxy S4 (i9505). So this must really be an issue of the CM code I guess.
Any ideas on how to solve this would be welcome since it is a really annoying issue

remove me

[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.

[Q] KitKat to Lollipop - the phone is unusable (huge battery drain and sys errors)

Hi everyone,
Until recently I've been using a KitKat based ROM and I was pretty OK with how my NOTE 3 SM-9005 was performing. However, a few days ago I decided to try a Lollipop based ROM and the problems started. I had similar problems with 3 different ROMs with great reviews. My battery went, for example, from 100% to 15% in ONE HOUR while streaming from YouTube. It never did that before. Also, It sometimes gives a "system stopped responding" error or something like that (it's like the equivalent of explorer.exe crashing on Windows) and after a few seconds it starts working again. Other system apps crash as well every now and then and sometimes the phone just decides to restart by itself.
I initially used Philz recovery and after the initial errors I switched to TWRP and started from scratch. I completely wiped my system internal space before flashing and, of course, I wiped dalvik cache and cache before and after flashing the ROM. I only used recommended gapps. Also, I did not restore any system apps. I started from scratch after the installation and the problem is the same.
To be more exact, I tries flashing so far the following ROMS, experiencing more or less the same problems on each:
temasek's UNOFFICIAL CM12.1
AryaMod V5.4 TW Lollipop Official BOB6
BlissPop 3.5 Unofficial
I also tried the Dirty Unicorns v9.4 ROM from the Original Android Development section but this one went on a reboot loop initially after the first restart so it never really even installed.
At this point I believe I might have done something that I should't have, but it seems strange because this is not the first time I am flashing a new ROM and I never had problems in the past. Also, my NOTE 3 SM-9500 did not have any problem on my previous KitKat ROM. Did I miss something? Should I have used another kernel? If I understood correctly, the ROMs come with a recommended kernel already. If this is not the problem, what could it be? Should I have done any additional thing before flashing a Lolipop ROM after using a KitKat ROM?
I now installed an app for trying to find out what exactly drains my battery but this is not the only problem. The system itself is really unstable.
I would really appreciate some help, suggestions, or opinions. I really don't know what else should I be doing at this point.
Thanks a lot!

Apparently is the media server eating all that battery (currently 68%).
I will format the SD card hoping this fixes the issue.....but could this have something to do with the system error and, sometimes, restarts?

Well I really don't know what to say! A lot of people report battery problems on 5.0 just because they didn't wipe the phone while coming from KK! But you did, so that's no go. Battery life on LP is much better than KK for me, at least 20% better if not more. And I didn't face any system crashing issues either! Don't really know what's going on with you mate.

Someone suggested that maybe I shoud update the bootloader and modem to a Lollipop version but I really couldn't find any info on how to do that.
Formatting the SD card just slightly reduced the battery drain. The phone is still discharging like crazy. Any suggestion on how to update the bootloader and modem?
Thank you.

LG G2 D02 CM 13 Problems

My boss rooted his LG G2-D02 and installing CM 12.1 in the process. Now, after knowing that CM 13 was already released, he downloaded a copy of it and immediately flashed it onto his phone. He got a problem with Gapps and DL-ed a problematic version which caused the notification,"Unfortunately, Setup Wizard has stopped" to pop up repeatedly. We had tried following a few advices from this website but to no avail.
1.) We already tried using Force Stop and Disable under Apps->(Show system apps)->Setup Wizard (CM). I had also tried giving it app permissions, but all app permissions were already available.
2.) The only option is to flash CM 12.1 back again but it can't be done. My boss set the default recovery app to Cyanogenmod's own recovery program, which had limited functions, so I can't
also use TWRP ATM.
3.) My boss also tried something on ADB but to no avail
4.) Factory reset didn't also solve the problems.
I'm almost running out of solutions... Perhaps, I can use a helping hand from brighter minds in this community.
TIA

I'm using cloudyg2 v3.3 because cm13 has got a lot of bug for example
-I can't proceeded to music
-systtem has stopped once a hour
-I can't close touching vibration
I can't remember now but cm13 has got really much bug (yeah my english is very bad,I know this)

Now system is stable and battery is very very good but still İ can't scretch to music