com.sec.app.MIPErrorNotifier running after restart

Search This thread

stereo386

Senior Member
Jun 22, 2012
213
71
Has anybody been able to come up with a solution for this annoying thing. Its happening randomly throughout the day no matter if on WiFi or on 3g or 4g. It just happens. It doesn't mess wit anything except sometimes people have to call me twice to get thru. Like it will ring on their end but not show on my end. Other than that its ok just very annoying. Any help is appreciated and no I'm not rooted so I can't freeze the app w titanium backup app. :) tx in advance.

Sent from my SPH-L720 using XDA Premium 4 mobile app
 

slixzen

Senior Member
Jan 9, 2010
382
17
Can I +1 to this?

If people call me, I tend to not receive a call.

This also happens all the time after a reboot or cold boot. This application shows up in my recent activity list.

A fix would be much appreciated.
 

ROMANTiC KiD

Senior Member
Mar 2, 2011
690
226
Can I +1 to this?

If people call me, I tend to not receive a call.

This also happens all the time after a reboot or cold boot. This application shows up in my recent activity list.

A fix would be much appreciated.

There hasnt been a fix for this yet cause we dont whats actually causing that but you can delete it from system apps and that will take off the app from recent activities.

Sent from my SPH-L720 using xda app-developers app
 

myamex

Senior Member
Mar 4, 2011
88
18
So I'm running everything stock. Already replaced my phone once yesterday. This is what happened:
Did the system update over wi-fi at home. Went out and suddenly it restarted. Then a few seconds restarted again. And again.
It basically went into boot loop in a sense. I went back to the store where I got it from (within 14days still) and they couldn't do anything with it and gave me a new one. So come today. I get the update, download it. SAME thing. It stays on for about 3-6 seconds and restarts.

BUT I was able to turn off my "Mobile Data" and it stays on. No restart. But it shows up with MIPERRActivity which is com.sec.app.MIPErrorNotifier. I can use wi-fi just fine. But the second I turn Mobile Data back on, it freezes my phone and restarts. And then restarts after a few second of being turned on. :mad:

When looking at the Permissions, it looks as if it essentially has permission to do everything and anything on my phone. Could this be some sort of viral file that got attached to the update somehow? Or just a monitoring app that runs in the background? :eek:

---------- Post added at 04:56 PM ---------- Previous post was at 04:44 PM ----------




Also, I'm on Sprint and I can turn the wifi on/off so long as the mobile data is turned off. :rolleyes:

I have the exact problem. Have you figured out how to fix it?
 

Vajamie

New member
Mar 4, 2013
2
0
Kansas City
My husband has had his s4 since July and the same error thing popped up today in his recent apps too. Everyone keeps asking but I'll ask again, has anyone found an answer to this yet?? I agree, it kinda creeps me out with all the permissions.
 

ROMANTiC KiD

Senior Member
Mar 2, 2011
690
226
My husband has had his s4 since July and the same error thing popped up today in his recent apps too. Everyone keeps asking but I'll ask again, has anyone found an answer to this yet?? I agree, it kinda creeps me out with all the permissions.

You can use delete the app in system/apps or just freeze it with titanium backup. There isnt really a fix since I believe its samsungs and sprint bug maybe idk could be fixed in the next release or not.

Sent from my SPH-L720 using xda app-developers app
 

sainthooligan

Senior Member
Apr 28, 2010
141
39
Not too sure there's a call for being nervous about what it is...it appears to just be "listening" for changes in data (as also mentioned earlier in this thread) here's a snippet of what logcat says about it:
Code:
09-26 08:32:08.108: I/MIPErrorReceiver(4741): onReceive intent : android.intent.action.ANY_DATA_STATE
09-26 08:32:08.108: I/MIPErrorReceiver(4741): getMobileDataState
09-26 08:32:08.108: I/MIPErrorReceiver(4741): onReceive intent : android.intent.action.ANY_DATA_STATE
09-26 08:32:08.108: I/MIPErrorReceiver(4741): getMobileDataState
09-26 08:32:08.118: I/MIPErrorReceiver(4741): onReceive intent : android.intent.action.ANY_DATA_STATE
09-26 08:32:08.118: I/MIPErrorReceiver(4741): getMobileDataState
09-26 08:32:08.128: I/MIPErrorReceiver(4741): onReceive intent : android.intent.action.ANY_DATA_STATE
09-26 08:32:08.128: I/MIPErrorReceiver(4741): getMobileDataState
09-26 08:32:08.138: I/MIPErrorReceiver(4741): onReceive intent : android.intent.action.ANY_DATA_STATE
09-26 08:32:08.138: I/MIPErrorReceiver(4741): getMobileDataState
09-26 08:32:08.148: I/MIPErrorReceiver(4741): onReceive intent : android.intent.action.ANY_DATA_STATE
09-26 08:32:08.148: I/MIPErrorReceiver(4741): getMobileDataState
09-26 08:32:08.148: I/MIPErrorReceiver(4741): onReceive intent : android.intent.action.ANY_DATA_STATE
09-26 08:32:08.148: I/MIPErrorReceiver(4741): getMobileDataState
09-26 08:32:08.158: I/MIPErrorReceiver(4741): onReceive intent : android.intent.action.ANY_DATA_STATE
09-26 08:32:08.158: I/MIPErrorReceiver(4741): getMobileDataState
09-26 08:32:08.168: I/MIPErrorReceiver(4741): onReceive intent : android.intent.action.ANY_DATA_STATE
09-26 08:32:08.168: I/MIPErrorReceiver(4741): getMobileDataState
09-26 08:32:08.168: I/MIPErrorReceiver(4741): onReceive intent : android.intent.action.ANY_DATA_STATE
09-26 08:32:08.168: I/MIPErrorReceiver(4741): getMobileDataState
09-26 08:32:08.178: W/SignalStrength(779): Size of signalstrength parcel:172
09-26 08:32:08.178: W/SignalStrength(1121): Size of signalstrength parcel:176
09-26 08:32:08.178: W/SignalStrength(1359): Size of signalstrength parcel:176
09-26 08:32:08.178: W/SignalStrength(779): getCdmaLevel=5
09-26 08:32:08.178: W/SignalStrength(1359): Size of signalstrength parcel:176
09-26 08:32:08.178: W/SignalStrength(3990): Size of signalstrength parcel:176
09-26 08:32:08.178: W/SignalStrength(1121): getCdmaLevel=5
09-26 08:32:08.178: W/SignalStrength(1121): getCdmaLevel=5
09-26 08:32:08.178: W/SignalStrength(779): getCdmaAsuLevel=8
09-26 08:32:08.178: I/MIPErrorReceiver(4741): onReceive intent : android.intent.action.ANY_DATA_STATE
09-26 08:32:08.178: I/MIPErrorReceiver(4741): getMobileDataState
09-26 08:32:08.178: D/STATUSBAR-NetworkController(1121): onSignalStrengthsChanged signalStrength=SignalStrength: 99 0 -77 -20 -74 -20 7 99 2147483647 2147483647 2147483647 2147483647 2147483647 cdma 0x500 level=5
09-26 08:32:08.188: I/MIPErrorReceiver(4741): onReceive intent : android.intent.action.ANY_DATA_STATE
09-26 08:32:08.188: I/MIPErrorReceiver(4741): getMobileDataState
09-26 08:32:08.198: I/MIPErrorReceiver(4741): onReceive intent : android.intent.action.ANY_DATA_STATE
09-26 08:32:08.198: I/MIPErrorReceiver(4741): getMobileDataState
09-26 08:32:08.198: I/MIPErrorReceiver(4741): onReceive intent : android.intent.action.ANY_DATA_STATE
09-26 08:32:08.198: I/MIPErrorReceiver(4741): getMobileDataState
09-26 08:32:08.208: D/StatusChecker(1951): onReceive : android.intent.action.SERVICE_STATE
09-26 08:32:08.208: D/StatusChecker(1951): Service state changed : 0

I think you're only going have true peace of mind about its permissions if you follow one of the previous "work-arounds"- since it doesn't seem to have a general fix for it.
 

RogueSly

Senior Member
May 21, 2013
71
19
I deleted this out of /system/app, after making a backup of it locally of course. I've been running for days without any problem with data or wifi. Just looks like more bloat from what I've seen.
 

stereo386

Senior Member
Jun 22, 2012
213
71
I deleted this out of /system/app, after making a backup of it locally of course. I've been running for days without any problem with data or wifi. Just looks like more bloat from what I've seen.

How can I do something about it if not rooted. U have to be rooted to delete the apps rite.

Sent from my SPH-L720 using XDA Premium 4 mobile app
 

slixzen

Senior Member
Jan 9, 2010
382
17
So is the above method of just freezing the application the resolution to this problem? Because this pops up all the time.
 

emod0705

Senior Member
Oct 12, 2011
216
34
San Antonio, TX
Just now wiped the apk. Just solved a month worth of the same thing.:)

From a Modded SPRINT Galaxy S4 on XDA PREMIUM

---------- Post added at 01:48 AM ---------- Previous post was at 01:47 AM ----------

31 down and 8.5 up YES!!

From a Modded SPRINT Galaxy S4 on XDA PREMIUM
 

o6o3

New member
Mar 30, 2015
1
0
Apologies in advance if a redundant Q:

"Force Stop" doesn't seem to eliminate the issue. In a step by step format, how can this app be removed? I'm able to see it on the app list through settings, but there's no option to completely get it off the device (or at least I'm not aware of the way to do it).

Thank you!
 

Top Liked Posts

  • There are no posts matching your filters.
  • 2
    After a bit of review

    Ok, so I've been doing a little testing this AM to see if I could get to the bottom of this error.

    After rebooting, locking and unlocking a ton of times I've decided its related to wifi connecting on the initial boot.

    After a while I started noticing a pattern in relation to the toast message that pops up when it initially connects to wifi and the error showing up.

    To confirm my theory, I removed the local wifi at my office, and on reboot, no error.

    I have zero clue on how to fix the issue, but just wanted to point any devs looking into this in the right direction. :D

    Additional notes, I'm stock, not rooted, and updated via the sdcard method.
    2
    I'm getting this error too... glad it's not just me. this may just be a bug in the MF9 f/w.

    I'm thinking the phone is checking for a MIP(Mobile IP) connection... not getting one(due to wifi being used) and triggers the error. Mobile IP is related to 1x/EVDO/eHRPD(and I'll assume LTE)... but "MIP" is not used when wifi is on. The data profiles(usernames and passwords for data authentication) are technically called "MIP Profiles"... which is why I'm tying the MIP name to 1x/EVDO etc but not wifi.

    As to why this is being triggered like this... I do not know. At first I thought maybe one of the system apks I deleted caused this... but those of you reporting that this happens on pure stock have confirmed that's not the case. As long as this isnt draining the battery or something... it seems like just a cosmetic nuisance.

    I can't think of a way for non-rooted people to fix this... removing/freezing the apk would seem to be the only way. If your mobile data works after togging off wifi... as I said... just seems to be a cosmetic issue. At least that seems to be the case for just about everyone besides Chimodo(post #31).


    [EDIT - continue reading below for some updates]



    Hmmm... after a bit more poking... ##DEBUG# hidden menu(password = sprint) if you go to the EVDO ENG RF menu.. I noticed that when "Rx PER" gets an "invalid error".. I see the "MIPERRActivity" in Recent Apps list. If I disable wifi.. reboot the phone and start off with evdo/ehrpd/lte... no "invalid" error under ##DEBUG# > EVDO RF > Rx PER(and no MIPERRActivity). Turn on wifi... the "invalid error" comes back(not always) as does "MIPERRActivity" in recent history. Basically... if you see the "MIPERRActivity" in recent apps... check in ##DEBUG# menu for the "Rx PER invalid error". If this happens on more phones than just mine.. I think we've found the culprit.

    Why this happens... I do not know... doesn't seem to me that the data profiles are failing in any way... I get evdo/ehrpd/lte just fine... and wifi is fine when enabled as well. Again.. this makes me think it's some kind of bug. Perhaps we can contact Sprint... and maybe in the next update things will be fixed.



    blah... another update. after more testing... seems "MIPERRActivity" and "Rx PER" invalid error aren't always linked. :( there goes that theory.
    1
    Same here. Not sure what this is, and if I should just freeze it using Titanium backup. Searched google and the first hit was this post :)
    One of the subsequent posts indicates that this app existed on the S3 late last year too - http://forums.androidcentral.com/sp...ng-galaxy-s3-sprint-version-stock-rooted.html
    1
    Same here! I'm wondering if we rename it to .bak at the end if that will affect anything... anyone willing to test that lol?

    I froze it using Titanium backup. No ill effects so far
    1
    Has anyone totally deleted it (not freeze it, but DELETE IT) from system/apps ??

    I did. Uninstalled via TB and havent seen anything weird.