[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.
Related
I have created this thread to clean up the forums a bit and to fix one confusion that most people in the forums which are saying which can mislead people to think that user means that when they don't mean that.
Q: What is the different between brick and soft-brick?
A: This is the issue I was talking about above.
A soft-brick is where you cannot access the kernel or/and rom and a brick is where you cannot access the bootloader so you cannot turn on your device unless you JTag it.
Q: Since I flashed a kernel I got stuck on the splash screen (Google logo bootloader screen), I attempted to reflash but it did not help.
A: Make sure the kernel is supported by the Rom's build number and Android version, to fix this you have to flash a supported kernel, remember that not all kernels are supported.
Q: Since I upgraded to Android 4.3 via OTA I noticed a large battery drain, WHAT IS GOING ON?!?!
A: On day 1 after the upgrade Google Backup will be using your battery for restoring your data so you will have to wait until it is done BUT then it will backup your settings such has brightness and app data but you can switch off "App Data" from the sync settings to stop Google Backup.
Q: A while/day later the issue is gone but Google Services is draining my battery.
A: That is actually Google Maps doing the draining, it is using the internet to locate you, to stop the battery drain go to Settings, Location settings, and disable WiFi & Mobile network location.
Q: Titanium Backup is not restoring my backups, what can I do?
A: Flash SuperSU v1.51 via recovery, this will fix the root issues and the Titanium Backup restore issues.
Q: Root is not working on Android 4.3, I'm panicking!!!!!!!!!!!!
A: Don't worry, flash SuperSU v1.51 has mentioned above to fix root since it now uses the SU Deamon due to the new security.
Q: The stock recovery says "No command.", what can I do?
A: Either keep pressing or hold volume up and power to unlock the menu.
This does not always work for certain users so I would try volume down and power so see if that does anything.
Q: How do I disable the OTA updater?
A: You will need root and an application, thanks to @joshuab227 for the information, the following is from joshuab227's post:
Here's how to disable the auto OTA download on any ROM
Install Autorun Manager from the Play store.
Then enter its recommended advanced mode.
Go into the settings and enable the following : system entries and system app disable.
Disable com.android.gsf.update.SystemUpdateService$Reciever under Google Service Framework
Click to expand...
Click to collapse
Q: The Play Store app and web store will not recognise my device!
A: @ColdEmbrace has got this issue and found the solution so that should explain why the start of the post starts how it starts:
After trying all of the above options my device was still not showing in the store. I went to this link.
play.google.com/settings
I clicked on one of my devices and clicked the update option this loaded my Nexus 4 onto the list it is now available on the web store.
Thanks everyone for the advice and I hope this helps people who are still having issues.
Click to expand...
Click to collapse
Q: My device says that I have no internet connection with a empty signal bar with or without a sim card.
A: The user @matt0401 was one of the victims with this issue and managed to fix this issue with a interesting solution:
Wow, I'm up and running! Weird fix though...
I installed the toolkit and downloaded the ROM, and was attempting to get into fast boot manually because trying to do it during the unlocking process in the toolkit wouldn't work. I thought I remembered the buttons for getting into fast boot from my old Gnex as being "hold power and volume up at same time". I tried this, and the phone went to the white "Google" logo and then vibrated, and then screen went black and the LED notifier at the bottom of the phone glowed red for about 2 seconds. The phone then rebooted, about 10x faster than before might I add, and when I was booted up I saw "No SIM detected... emergency calls only". This would infer my SIM slot was finally being detected, whereas before even with no SIM inserted I just got "No Internet Connection".
I popped my SIM in, rebooted, and the network is connected. Time to review 5 days of missed texts. Thanks for the hand!
tl;dr --> Anybody having this problem, try turning it off, and then turning it back on with the SIM inserted, holding POWER + VOL UP til it does this hard reset type fucntion. When rebooted, the problem should be resolved.
Click to expand...
Click to collapse
Q: I have to reenter my pin code for my sim every time, what do I do?
A: @lucker#1 you guessed it has the same issue has well but he wasn't the OP of the thread that the issue was discussed in but he did sure find a fix, the following is a quote from his post:
i've also had that issue the second day after receiving the phone. I removed the sim, put it back in but that didn't help - i looked at my sim card tray and i realized that a one side of the sim card chip was close to one metal side of the tray and i figured that could be the issue - so what i did is i took a stripe of adhesive tape and made sure they wouldn't touch - I haven't had the issue again and it's been more than 2 weeks.
Click to expand...
Click to collapse
Q: Since I installed Android 4.3 a few of my apps are force closing, what should I do?
A: You have to reinstall that application to fix the issue.
Q: I am getting screen flickering.
A: Flash the correct kernel which supports your Android build and version.
Q: Got a kernel panic, HALP!!!
A: That is pretty rare for the kernel to panic but you can actually easily trigger it, to fix it you must reflash the kernel (make sure it is the correct one!).
Q: Since Android 4.3 on YouTube using Slimport there is a blue graphical glitch, why is it doing that and how to fix it?
A: Since Android 4.3 there is some major bugs, improvements and fixes and the graphical glitch (I got this myself) is due to the new Software Encoder, there is no fix yet but you can go around it by using VPlayer as it apparently supports YouTube videos and it has Hardware Encoding.
If you have any questions and answers please post them here.
Bump!, Not much people are reading this...
Sent from my Nexus 4 using xda app-developers app
Bump once again and the last time.
Sent from my Nexus 4 using Tapatalk 4
I received the OTA for 4.4.2 yesterday after I had installed 4.4.1 manually. I noticed with both that the screen began to flash black quickly, and then went back to normal, every now and again. I noticed it the most in Hangouts, and for some reason the Play Store keeps opening at random...very annoying because it doesn't even load to show me all the new things, it just stays white. Is anybody else having this issue? I assumed 4.4.2 was to fix the screen flash but nope. Also I noticed GPS doesn't lock on unless High Accuracy is selected under the GPS settings, haven't gotten it to work otherwise with Mobile Data or Wi-Fi
Hi, I had a very similar problem in the past, while updating my Nexus 4 from 4.2 to 4.3. The solution is to clear cache.
1. Put the phone in airplane mode.
2. Go to Settings -> Storage
3. Find the second bottom most item, "Cached data," and touch it. It will ask if you want to clear cache. OK it and power down the phone.
4. Reboot and get out of the airplane mode.
This should fix it. You can alternatively clear cache from the stock recovery. If this doesn't solve it and the screen flickering persists, give Google a call.
GPS-Fix
Wink GPS-Fix
Hi there guys,
I have had the same problem updating from 4.4.1 to 4.4.2 and was looking for this fix,
here are the files that I used but I don't know for sure if it will work for you but for me it did the trick.
You have to try each one of them, for me the second one worked out, the first one didn't even flash on my phone.
So I guess you guys can give it a try.
After flashing and clearing (((Cache and Delvik/Cache)))) please reboot.
When I did the GPS fix worked right away, so it was a very quick fix based on a Galaxy S3 script and the best part was that
I didn't need to go back to a stock room or anything.
PLEASE IF THIS WORKS FOR YOU JUST HIT THANKS.
I'm not good at this guys so here are the two links the website give me if you like let me know if anything is wrong
I will send you guys the file directly.
(((((((((((( I DO NOT CLAIM ANY PROPERTY ON THIS FILES. THEY WERE ENTIRELY CREATED BY SOMEONE ELSE. )))))))))))))
https://anonfiles.com/file/0ec77a872...98258e69e265a9
https://anonfiles.com/file/0ec77a872...98258e69e265a9
Hello.
I posted the question in the Q & A thread but I fear my question got lost in between the many that are asked.
I own a rooted S4 from Rogers Canada, which used to be on Alpha Infamous rom, an old version like the 5.0 from at least 6 months ago. Everything runned fine until recently. The phone started giving me some trouble. After missing a phone call while I didn't had the phone on me, the screen stayed on showing missed call until I happened to see the phone and pressing power to close it. The same started happening with message at about the same time.
Since I thought I might have installed a dumb apk on gplay that messed something in the settings, I went to get a new Rom. Alpha having no development for a long time, I thought I'd try something else.
I have tried both omega v25 and [23/03][4.4.2][XXUFNBH]< Echoe v18 > [07/02][4.3][NA4]< Echoe v12.1 "The Final Bean">, the latest which I run at the moment. Both gave me the same trouble with the screen staying powered after missing a msg or a phone call.
Since I don't know how to fix it, I was wondering if anyone could help me out ?
I'm no pro at rooting/flashing but I did the wipe dalvik, cache and everything before flashing both of the new rom. I didn't update the bootloader as I didn't remember clearly how or if it was necessary but the rom in general runs great so I figured out it was ok this way. The only trouble I have is with the screen as previously stated. I didn't flashed the modem either as I seem to have great download speed (without testing, simply feeling it).
So as of now, I'm running Echoe V18 with most of the bloatware disabled in aroma installer.
What can I do to fix this? I've tried googling but nothing close to my trouble came as result. Neither could I find an answer here, there's so many result I might have simply missed it.
Thanks for the help!
Laethageal
Anyone's able to help out ? My question is getting phased out but still has no answer. Please ?
Deleted
SirOxyGems said:
Good day, This is my first time ever posting a thread on this site and new to custom ROMs on Android devices. I currently have Samsung Galaxy Note 4 (T-Mobile) and a friend suggest I flash it with some custom ROMs. I did, indeed, tried all the compatible ROMs for this phone and they all boot up find (despite the long hang time after finishing the boot setup), but I ran into some problems after doing everything, step-by-step, correctly. I've done light research on how to fix these issues but was afraid if my phone may brick again and do another Emergency Recovery using Samsung Smart Switch. To get to the point, the following issues that are occurring are these below,
- WiFi continuously says "Wifi turning on" and never stops
- Settings will sometimes crash when entering "Security" and then backing out of it
- Camera quality remains blur and can't find any settings to get the camera to focus properly
- LTE/Mobile Data does not apply on boot (when restarting or turning it on) and it requires to fully reboot again
- Uninstalling a application forces the phone to do a soft reboot
- Sometimes multiple background apps will pop-up a error message stating, "Unfortunately, (App) has stopped"
I currently have the Resurrection Remix v5.7.1 (which is the latest I've found) build on the phone, but at the moment using Stock Marshmallow as I'm witting this. If there is anyone on the forums that can help me resolve these issue so i can have a stable flashed ROM, I would greatly appreciated the help. Thanks for your time and have a bless day.
Click to expand...
Click to collapse
Did you have all of these issues on every ROM that you flashed or just a specific ROM?
Sent from my Nexus 6 using XDA-Developers mobile app
Deleted
Hello,
Long story short, I flashed a stock firmware and I had two problems faced me, and thank God I got the solution by luck and decided to share them with anyone who might find them useful.
First problem that my device is 32gb and after flashing it showed storage capacity of 16 GB only.
Solution: just wiped data in recovery and then flashed another stock firmware of another country.
Second problem which gave me aloooooooot of headache is an annoying message on the always on display says
"double tap here to learn how to use always on display"
And it I tapped over every pixel of the screen and wiped data/cache of aod app over and over again and did factory reset and even flashed another stock firmware and still IT DIDN'T GO AWAY!!!!!!!!!!
Solution which worked for me:
The current version of aod app available for my device is 4.2.xx or something like that.
So I downloaded from internet aod app -still by Samsung- but higher version 5.x.x and installed it but the aod screen stopped working at all.
Then I uninstalled this update and installed the next higher version of my current version 4.3.xx and once I installed it just vanished the message thank God!!
Anyway, I'm an amateur and sure these problems are nothing to you, but I felt I had to share that with you.
Stay safe ?