Hello everyone,
Pretty new here, 1st post
I recently updated my N4 to 4.3 (flashed the stock image from google). I'm rooted with CF's autoroot (and have an unlocked bootloader), but the rest is stock....
I seem to have an issue: when I unlock the screen, the screen turns black and then turns on again (in less-than-a-second maybe...), so there's a screen flicker, just one time when I unlock the screen... I thought the problem was N4 Display Contol app, but the issue remains after I removed it...
4.2.2. didn't do this as far as I remember....
Anyone else have this problem? (I'm set to auto-brightness btw..)
I am having the exact same issue after I updated last night.
HowlinMadMurdoc said:
I am having the exact same issue after I updated last night.
Click to expand...
Click to collapse
Well.... I went into (stock) recovery and wiped cache. Then I manually deleted my dalvik cache with Tcmd...
..aaand (after reboot) the issue seems to be gone. It unlocks without flickering :good:
Please try this (if you are rooted) and write back if it helped.
dSERiES said:
Well.... I went into (stock) recovery and wiped cache. Then I manually deleted my dalvik cache with Tcmd...
..aaand (after reboot) the issue seems to be gone. It unlocks without flickering :good:
Please try this (if you are rooted) and write back if it helped.
Click to expand...
Click to collapse
you are lucky you can get into recovery! i cant even get there, just says "no command" when i do so.
---------- Post added at 11:29 AM ---------- Previous post was at 11:15 AM ----------
Ok was able to fix the recovery error by using the Nexus 4 Toolkit to install one of the custom recovery tools. now wiping cache and dalvik to see if that fixes it.
---------- Post added at 11:46 AM ---------- Previous post was at 11:29 AM ----------
that didnt work, flashing back to stock recovery brings that error back as well. might have to just wipe everything and start from scratch :/
dSERiES said:
Well.... I went into (stock) recovery and wiped cache. Then I manually deleted my dalvik cache with Tcmd...
..aaand (after reboot) the issue seems to be gone. It unlocks without flickering :good:
Please try this (if you are rooted) and write back if it helped.
Click to expand...
Click to collapse
Unfortunately this works for a little while (even just rebooting when you get flickering), but the problem keeps coming back after a few days of use (without restart)
patsmike said:
Unfortunately this works for a little while (even just rebooting when you get flickering), but the problem keeps coming back after a few days of use (without restart)
Click to expand...
Click to collapse
Reboot didn't help me at all. The issue did come back however. I updated SuperSU and it updated some binaries for me, after it was complete and phone rebooted, the flickering came back. I deleted dalvik-cache again and wiped cache partition through stock recovery and it's gone again....
You aren't talking about the CRT on off animation like TV set old school are you??? Lol if not its common for many flickers on these devices. I get them off and on. Usually in the ROM hw overlays. Sometimes in settings you can revert by clicking or get to stop. Just hoping its CRT as those unfamiliar have asked bfore
Sent from my Nexus 4 using xda premium
Droid2drummer said:
You aren't talking about the CRT on off animation like TV set old school are you??? Lol if not its common for many flickers on these devices. I get them off and on. Usually in the ROM hw overlays. Sometimes in settings you can revert by clicking or get to stop. Just hoping its CRT as those unfamiliar have asked bfore
Sent from my Nexus 4 using xda premium
Click to expand...
Click to collapse
"screen UNLOCK flicker"
CRT off animation? :laugh::laugh::laugh::laugh:
seriously no, we are talking about the flickering when you Un-lock your device
Same problem here. But mine does not go to the black screen. Just straight cut off the animation. From lockscreen to homesreen without any animation. Restart is a temporary fix. Any suggestions?
Hello,
I own a note 4 N910F for over a year now. I've played around with a few roms but currently I'm on stock rom (no root). Lately I've been having problems with my battery. When below 50% the phone can restart at any time. Usually when opening a game. Not every time but any time.
A few days ago while on 25% I tried to enable the Ultra power saving mode. The screen turned gray and then..... the phone restarted.
Now when I turn on the phone it powers up normally and a few seconds after I get a message "Disabling powers saving". That fails and I get a message saying that "EmergencyManagerService Stopped". That happens 2 times. After that the phone functions normally but..... the screen is gray.
When I try to enable the ultra power saving mode now I get the screen with the estimated battery life but nothing happens after that.
I've tried flashing the rom with odin, so that I don't loose any apps/settings but the problem remains.
I have backed up my data with Helium but..... it would be best not to do a reset for now, due to tight work schedule.
Thanks
I rooted my phone, installed titanium backup, found the EmergencyManagerService, reset its data and the pr;oblem was solved.
Just for the record
安卓手机提示“EmergencyManagerService已停止”的解决办法
手机：三星Samsung Note4 N9100
安卓：4.4版
线刷包：是“三星N9100_{380750}_TGY（香港）N9100ZHU1ANL1_4.4.4_20160830194905.rar”
大家都知道这个官方的包内置软件比较多，需要做精简处理，然后一轮精简后，重启提示“EmergencyManagerService已停止”，Google一下，百度一下，Bing一下，都没有解决办法。
过程分析：
后来在钛备份中发现有个程序的名称就是叫“EmergencyManagerService”，对应的是在 \system\app 目录下的“EmergencyModeService.apk”的apk文件，这个包名称是“com.sec.android.emergencymode.service”的。于是搜索了一下“EmergencyModeService.apk”的情况，发现“EmergencyLauncher.apk 启动器.不能删除”，“EmergencyModeService.apk 启动器相关,不能删除”，“EmergencyProvider.apk 启动器相关联的服务”，三个带有“Emergency”开头的相关APK不能删除的问题。于是上 Root Explorer 看了一下，EmergencyModeService.apk 和 EmergencyProvider.apk 都在，就是 EmergencyLauncher.apk 被删除了，而这个 EmergencyLauncher.apk 就是“启动器 1.0”就是默认桌面系统嘛，想了一下，估计是因为后期改为使用Nove做桌面，想着这个没用，就删除掉EmergencyLauncher.apk，把这个文件复制回去，会不会就不提示呢？于是复制回去，改了权限，重启后，就没有再提示“EmergencyManagerSevice已停止”，看来就是因为删除了EmergencyLauncher.apk引起的。
解决办法：
所以我们要做的很简单，把EmergencyLauncher.apk复制到\system\app下，权限修改为跟同目录的其他APK的权限一样，然后重启手机即可。
Hi, my problem is exactly the same. You said "found the EmergencyManagerService, reset its data" and this solved the problem, but what do you mean here exactly? What files or data was reset? My phone is also rooted so probably can do the same, but please be a little more specific.
---------- Post added at 01:53 PM ---------- Previous post was at 01:22 PM ----------
Okay, I got it, needed to clear data and clear cache for the EmergencyManagerService and it indeed solved the problem.
On a related note: did you ever find a solution to the phone turning off or restarting when the battery is around 40-50%? My note 4 does the same
I'm running a Galaxy S5 with CM14.1. All was good for many weeks until today, when suddenly the phone started freezing irrecoverably. It occurs about 1 minute after the phone boots. Before that, between starting up and freezing, the phone is a little laggy but works fine.
I've tried a factory reset and also tried reinstalling CM14 but it still occurs.
Nothing was changed on the phone between when it was working fine and when it started freezing consistently.
Anyone have this experience?
[Update] Downgrading to CM13 (or even restoring a backup of a CM13 install) solves the problem. But no amount of reinstalling CM14, or even reverting to a backup of a CM14 install that was entirely functional (no freezing) solves the problem - all installs of CM14 now freeze.
Similar experience from another user....
Literally could have written your post word for word (S5, 14.1, same symptoms) and created an account to tell you so, but it won't let me. Still a n00b in many respects but I've backed my way out of enough soft bricks to not feel totally out of my depth when I say "This is weird, but probably not unique." So, thanks.
Additional info, in case it helps in any way:
- T-Mobile network
- was working fine until about 8:45pm when it died while I was making a call. Plugged it in, turned it on, freeze.
- Recently installed a new SD card because my old one was unreadable, discovered by "too little storage, delete some apps." 128GB Samsung brand (just because I was bitter about it). Promptly made a full backup Jan 20. Tried to restore it but it was giving me a LOT of **** about making the SD internal, and I got so frustrated that I gave in. Result: "Cannot restore modem -- mounted read only." Restoring everything but the modem now.
Moved to Galaxy s5 Q&A
same same
same problem here, all in a sudden 14.1 started freezing. i can factory reset, wipe, dalvik, cache, etc. even went so far to format system and everything, and reinstalled, it boots, and as soon as i should be select language etc. it freezes. no way to do anything. i will go back to a 13/6.0.1 based rom, and see if this works.
Update: i formated everything, system, cache, data, you name it after going back to a 6.0.1 based rom, in my case Resurrection Remix, it worked like a charm, as expected. it offered me an update to 7.1.1 or so, i downloaded it, factory resettet it, installed it, as soon as it booted, it froze, again. so there is, indeed, something with the 7.1.1 roms, which my phone does not like. i feel at a loss, since i never before experienced such a problem, since i started putting custom roms on my first galaxy S, and my S3.
any pointers would be helpful. not sure if i can provide any logs, since it freezes anyway, as soon as the setup-wizard comes up, before i can enter anything.
at least 6.0.1 works, which means, unless i feel like wasting an afternoon again, or some pointers on what goes wrong will come up, i will stay on it, for a month or so at least.
novae_lithic said:
I'm running a Galaxy S5 with CM14.1. All was good for many weeks until today, when suddenly the phone started freezing irrecoverably. It occurs about 1 minute after the phone boots. Before that, between starting up and freezing, the phone is a little laggy but works fine.
I've tried a factory reset and also tried reinstalling CM14 but it still occurs.
Nothing was changed on the phone between when it was working fine and when it started freezing consistently.
Anyone have this experience?
[Update] Downgrading to CM13 (or even restoring a backup of a CM13 install) solves the problem. But no amount of reinstalling CM14, or even reverting to a backup of a CM14 install that was entirely functional (no freezing) solves the problem - all installs of CM14 now freeze.
Click to expand...
Click to collapse
Was there ever a resolution to this. I am having freezing issues with all versions of Nougat on my Verizon S5.
---------- Post added at 09:49 PM ---------- Previous post was at 09:46 PM ----------
novae_lithic said:
I'm running a Galaxy S5 with CM14.1. All was good for many weeks until today, when suddenly the phone started freezing irrecoverably. It occurs about 1 minute after the phone boots. Before that, between starting up and freezing, the phone is a little laggy but works fine.
I've tried a factory reset and also tried reinstalling CM14 but it still occurs.
Nothing was changed on the phone between when it was working fine and when it started freezing consistently.
Anyone have this experience?
[Update] Downgrading to CM13 (or even restoring a backup of a CM13 install) solves the problem. But no amount of reinstalling CM14, or even reverting to a backup of a CM14 install that was entirely functional (no freezing) solves the problem - all installs of CM14 now freeze.
Click to expand...
Click to collapse
tron65 said:
same problem here, all in a sudden 14.1 started freezing. i can factory reset, wipe, dalvik, cache, etc. even went so far to format system and everything, and reinstalled, it boots, and as soon as i should be select language etc. it freezes. no way to do anything. i will go back to a 13/6.0.1 based rom, and see if this works.
Update: i formated everything, system, cache, data, you name it after going back to a 6.0.1 based rom, in my case Resurrection Remix, it worked like a charm, as expected. it offered me an update to 7.1.1 or so, i downloaded it, factory resettet it, installed it, as soon as it booted, it froze, again. so there is, indeed, something with the 7.1.1 roms, which my phone does not like. i feel at a loss, since i never before experienced such a problem, since i started putting custom roms on my first galaxy S, and my S3.
any pointers would be helpful. not sure if i can provide any logs, since it freezes anyway, as soon as the setup-wizard comes up, before i can enter anything.
at least 6.0.1 works, which means, unless i feel like wasting an afternoon again, or some pointers on what goes wrong will come up, i will stay on it, for a month or so at least.
Click to expand...
Click to collapse
Were you "tron65" ever able to use Nougat on your S5 without freezing? Thanks.
martytoo said:
Was there ever a resolution to this. I am having freezing issues with all versions of Nougat on my Verizon S5.
---------- Post added at 09:49 PM ---------- Previous post was at 09:46 PM ----------
Were you "tron65" ever able to use Nougat on your S5 without freezing? Thanks.
Click to expand...
Click to collapse
i am now again using nougat, the latest nightly fixed all problems, i suppose it was a bug in the specific version, then. now i am at 7.1.2
cheers
martytoo said:
Was there ever a resolution to this. I am having freezing issues with all versions of Nougat on my Verizon S5.
---------- Post added at 09:49 PM ---------- Previous post was at 09:46 PM ----------
Were you "tron65" ever able to use Nougat on your S5 without freezing? Thanks.
Click to expand...
Click to collapse
I only found a solution doing a full install and going back to 6.0.1. The latest (last) CyanogenMod build didn't work for me, and now they're defunct anyhow.
Hey all! I was stoked to see nougat coming out today, but now am having issues with the installation. It downloads without a problem (tried both WiFi and cellular), starts the installation, then stalls at 32%, reboots, and gives error code 402.
I have been rooted in the past but have flashed back to stock using Odin previously. This is the first time I have tried to take an OTA since that process. I have already wiped the cache partition but have not done a full reset yet. Any ideas on how to fix this? Thank you!
I'm working on making a new thread for this now. Check the forum in just a few.
---------- Post added at 05:09 PM ---------- Previous post was at 05:01 PM ----------
Here you go!!! https://forum.xda-developers.com/verizon-galaxy-s7/how-to/update-pi3-to-official-nougat-t3568613
Thefireballkid said:
Hey all! I was stoked to see nougat coming out today, but now am having issues with the installation. It downloads without a problem (tried both WiFi and cellular), starts the installation, then stalls at 32%, reboots, and gives error code 402.
I have been rooted in the past but have flashed back to stock using Odin previously. This is the first time I have tried to take an OTA since that process. I have already wiped the cache partition but have not done a full reset yet. Any ideas on how to fix this? Thank you!
Click to expand...
Click to collapse
Are you you package disabler pro? If so make sure all apps are turned back on before attempting.
Crsdr37 said:
Are you you package disabler pro? If so make sure all apps are turned back on before attempting.
Click to expand...
Click to collapse
I was not. But in your thread I posted my solution.
Hi, I have an S5 prime SM-G906L that has been working great for the last 2 years. I installed blue light filter pro a few months back for reading in low light and it was working great. When I didn't need the filter e.g. during the day I would turn it off, then a week ago whilst off the right hand side of the screen started to jump up and down but only in apps with text not games. Anyway I have so far uninstalled the filter app and also cleared the cache and even did a hard reset and upgraded from 5.1 to 6.01 but the flickering is still there. It does go away when I use the blue light filter app on green at 20% or more which is a handy temporary fix for now.
My question is would a complete wipe and a fresh install of android fix it or does it sound like the hardware is on its way out?
Many thanks in advance
I don't think the hardware would work with some apps and not others if it was dying... If you have custom recovery get a ROM and wipe the phone 100%, I mean put your music n photos on your SD card and go to advanced and wipe data, system and internal storage. Do not wipe modem or anything else there or you hurt your device. If you are on stock... Flash twrp recovery using Odin and still do the above. You can reflash stock too but I suspect something in your system is buggy or altered and as the upgrade kept your files the issue still persists. That's why I want you to delete everything and start fresh.
---------- Post added at 09:35 PM ---------- Previous post was at 09:34 PM ----------
Make sure the rom being installed is on the SD also