IMS Framework draining my Battery on Galaxy S4

[Steve 4]

Since Updating to 4.4.2 on the S4 recently I've had a major issue with my phone.

They battery has been draining at an alarming rate.

Currently I'm down to 20% of which 50% has been used by IMS Framework in the space of 11 hours.

CPU Total - 1h 48m 48s
Stay awake - 10h 51m 15s

Any suggestions on how to remedy this problem or remove IMS Framework.

 

[Ablissland]

I would like to know too. Any solutions?

Posted via the Android Central App

 

[Ablissland]

I force stopped the app which seemed to have had a huge effect! Try it and see if you get the same results.

Posted via the Android Central App

 

[Cassipip]

I have the same problem. My battery was almost entirely drained from full after 4-5hrs today and I'd barely used any apps! I tried to force stop ims but dont think it stays stopped. Does it stand for 'instant messaging service'? I don't even use that I use whatsapp.
How do we rectify this? SO many people saying they are having battery issues since the 4.4.2 update. Is the only way to backup and then factory reset?

 

[Ablissland]

Force stopping IMS framework worked for me. I think I had to force stop it every time the phone was restarted.

Yeah I believe it stands for instant messaging service.

Posted via the Android Central App

 

[cooky69er]

Force stopping IMS framework worked for me. I think I had to force stop it every time the phone was restarted.

Yeah I believe it stands for instant messaging service.

Posted via the Android Central App

 

[cooky69er]

Force stopping IMS framework worked for me. I think I had to force stop it every time the phone was restarted.

Yeah I believe it stands for instant messaging service.

Posted via the Android Central App

Just wanted to say everytime i use messeages it turns ims back on any help pls.

 

[cs02mf]

I'm getttng the same problem. Running Android 4.4.2, my battery has lost 55% in 6 hours and IMS has sucked up 40%.

 

[Ablissland]

I'm on Vodafone using an s4 with 4.4.2.

Is it network specific? Only started happening when Vodafone did some updates.

Posted via the Android Central App

 

[Ablissland]

Disabling rich communication resolved my issue.

Posted via the Android Central App