ContextService has stopped NE9 rerooted

[wrongway213]

I just followed the guide to flash back to NCG kernel, reroot and flash NE9 kernel. So far everything is lovely except for after a phone call I always get an error: "Unfortunately, Context Service has stopped." Any idea what this is and how to fix it?

 

[GuestK00143]

I just followed the guide to flash back to NCG kernel, reroot and flash NE9 kernel. So far everything is lovely except for after a phone call I always get an error: "Unfortunately, Context Service has stopped." Any idea what this is and how to fix it?

Are you on a custom ROM, if so witch one?

 

[wrongway213]

Are you on a custom ROM, if so witch one?

No, stock ROM. Never flashed a ROM, Knox 0x0.

 

[wrongway213]

I believe I found a solution. I have installed Greenify, but it was disabled under my accessibility services. Apparently that's how it is set by default after downloading it, even when rooted. I turned Greenify on under Settings < Accessibility < Greenify and rebooted my phone. I made a few calls and received one and no more Context Service Errors for me. I am quite curious as to what Context Services are and why Greenify would cause those errors as I do not see any information on it relating to the S5, so if anyone has any idea why this happens, feel free to shed some light on it.I wonder also if Context Services are safe to freeze..

 

[wrongway213]

Problem returned with a vengeance after several reboots. Now I boot the phone sometimes and there are no errors, other times and constant FCs. Could I have somehow gotten a corrupt Context Service apk when I flashed to Stock Odin, or the NCG or NE9 kernels? Anyone know what Context Services actually is and if it's safe to freeze if there isn't a fix? I found a similar thread for someone having this issue on the At&T variant and someone replied that his Context Service apk was possibly corrupt and that he PM'd him a new one. http://forum.xda-developers.com/att-galaxy-s5/help/context-services-stopped-t2837895/post54614539 If this is something that is possible to do, I would greatly appreciate it.. I've looked both on Google and here and there seems to be very little info on Context Services, so I do not wanna freeze something that's unsafe to freeze, but these errors are killing me. Any help will be greatly appreciated.

Edit: Totally removed Greenify and the problem is gone. I would love to use Greenify, but I would like to know I can do so without causing issues. Does anyone know how Greenify would cause ContextService FCs?

 

[wrongway213]

Logcat

i have a logcat of the issue occurring, both by itself and induced via having my girlfriend call my phone. i took this to the xposed forum first and was told it appears not to be module related. if anyone can give me any input on this, i would really appreciate it

 

[elliwigy]

i thought it was just me.. however stock rom works fine for me its my custom build i get the fc on.. i dont have greenify in my rom so not sure if thats the root cause or not.. i will try something and report back

Sent from my SM-G900V using XDA Free mobile app

---------- Post added at 03:46 PM ---------- Previous post was at 03:29 PM ----------

ok so clearing data/cache doesnt help.. i also deleted it and pulled one from stock base pushed and set perms with no luck either.. ill keep searching but were not the only ones with this issue..

mines a deal breaker cuz it fcs after every call as well as i cant send sms lol

Sent from my SM-G900V using XDA Free mobile app

 

[wrongway213]

i thought it was just me.. however stock rom works fine for me its my custom build i get the fc on.. i dont have greenify in my rom so not sure if thats the root cause or not.. i will try something and report back

Sent from my SM-G900V using XDA Free mobile app

---------- Post added at 03:46 PM ---------- Previous post was at 03:29 PM ----------

ok so clearing data/cache doesnt help.. i also deleted it and pulled one from stock base pushed and set perms with no luck either.. ill keep searching but were not the only ones with this issue..

mines a deal breaker cuz it fcs after every call as well as i cant send sms lol

Sent from my SM-G900V using XDA Free mobile app

i've figured out if i try to install ANY modules by wanam, the issue occurs. greenify isn't the problem, i know that much. let me know if you find any progress and i''ll do the same for you.

 

[elliwigy]

i've figured out if i try to install ANY modules by wanam, the issue occurs. greenify isn't the problem, i know that much. let me know if you find any progress and i''ll do the same for you.

i flashed back but can you by chance go to a rom it was working on? ive read somewhere that if you have it working then back it up with tibu then on new rom restore its data and it might fix it.. it doesnt work pullin from rom for some reason

Sent from my SM-G900V using XDA Free mobile app

 

[wrongway213]

A rom it was working on? I've only ever been on stock rom in slot 1, not sure what you mean.

Sent from my SM-G900V using XDA Free mobile app

 

[elliwigy]

A rom it was working on? I've only ever been on stock rom in slot 1, not sure what you mean.

Sent from my SM-G900V using XDA Free mobile app

so its always fcd since youve got the device?

Sent from my SM-G900V using XDA Free mobile app

---------- Post added at 05:42 PM ---------- Previous post was at 05:41 PM ----------

A rom it was working on? I've only ever been on stock rom in slot 1, not sure what you mean.

Sent from my SM-G900V using XDA Free mobile app

also theres a dif between stock slot and rom slot 1.. im on stock slot

Sent from my SM-G900V using XDA Free mobile app

 

[wrongway213]

No, since I flashed back to NCG, rerooted and flashed NE9 it's been happening. I've never flashed a rom, just rooted on stock slot in safestrap

Sent from my SM-G900V using XDA Free mobile app

 

[bad bone]

A rom it was working on? I've only ever been on stock rom in slot 1, not sure what you mean.

Sent from my SM-G900V using XDA Free mobile app

I'm not sure if this will help but from what I've read ss has a problem when using a rom slot instead of the stock slot I've seen a lot of the rom devs change the procedure from using a rom slot to using the stock slot.

http://bit.ly/1brshoa

 

[wrongway213]

I'm not sure if this will help but from what I've read ss has a problem when using a rom slot instead of the stock slot I've seen a lot of the rom devs change the procedure from using a rom slot to using the stock slot.

http://bit.ly/1brshoa

yeah i'm in stock slot, not rom slot. didn't mean to post that, but thank you anyways

 

[wrongway213]

Anyone know if a Nandroid backup from before I ever originally took the OTA, stock rooted NCG, would fix my problems, and more importantly, if it would trip Knox or not if I restored it via Safestrap?

 

[bad bone]

I haven't read anywhere of someone trying it yet. I was wondering too good question

http://bit.ly/1brshoa

 

[elliwigy]

Anyone know if a Nandroid backup from before I ever originally took the OTA, stock rooted NCG, would fix my problems, and more importantly, if it would trip Knox or not if I restored it via Safestrap?

lol read the many posts about it floating around.. i restored my ne9 rom just fine many times.. nothing we can do with the vzw s5 will trip knox at this time so dont know why you even mention it lol we cant flash bootloaders

Sent from my SM-G900V using XDA Free mobile app

 

[wrongway213]

lol read the many posts about it floating around.. i restored my ne9 rom just fine many times.. nothing we can do with the vzw s5 will trip knox at this time so dont know why you even mention it lol we cant flash bootloaders

Sent from my SM-G900V using XDA Free mobile app

plenty of posts saying safestrap won't trip knox, had not heard from anyone as to what restoring a nano would do until i specifically asked this question yesterday though... you referring to a certain thread containing these many posts? because until i asked, the safestrap thread even made NO mention of nano backups as they relate to knox...

 

[KaM1KaZ3]

Never had that but I did get documents have stop once an it never did it again not sure what was up with that ?

 

[MWFD]

Is there an actual fix for the "Unfortunately, Context Service has stopped" error? I really made a stupid mistake yesterday and froze some system apps in Titanium Backup. At first I was getting a bootloop when the OS tried to load the apps and thought I was going to have to wipe data, but I used adb push to send the entire system/app folder to my phone (got the files/folder from my wife's phone who has the same phone on same ROM - I'm 90% sure it is the rooted KOT49K/ANCG build of Verizon GS5). This adb push allowed my phone to boot entirely, but now everytime I boot the phone up, I get the Contest Service error message. So I just backed up Contest Service 2.0.3 using Titanium Backup on her phone, then put the 3 files it created onto my phone and tried using Titanium to restore Context Service 2.0.3 to my phone but to no avail. I tried restoring app only and also restoring app+ data but the restore never completes in TB (ive changed TB to INDIRECT mode too) but it doesn't fix the problem. When I start the restore, it does stop the error message from constantly appearing but only until the next reboot.

So does anyone know how I can stop from getting this error message? I have another working Verizon GS5 on the same ROM at my disposal.