Currently Being ModeratedSep 1, 2012 3:38 AM (in response to ChangeAgent)
an auto-start process has been set to start HP's Device Monitor, presumably to keep an eye (so to speak) on that printer, but the startup process can't find the monitor to start.
Start Terminal and give the command
launchctl remove com.hp.devicemonitor
Currently Being ModeratedFeb 27, 2013 3:10 PM (in response to Austin Kinsella1)
That works, but after reboot it all starts again.
Currently Being ModeratedApr 2, 2013 12:37 PM (in response to scottinhawaii)
Hi - to keep the process from restarting after reboot, you'll have to track down the offending entry in one of:
Look in those directories for a .plist file that mentions "com.hp.devicemonitor" and remove it.
Currently Being ModeratedApr 3, 2013 12:00 AM (in response to ChangeAgent)
Mine has returned too. going to try Fearless fools solution.
Currently Being ModeratedJun 28, 2013 5:44 PM (in response to ChangeAgent)
I have similar problem, and have tried feerless fools action but that has not resolved the recurrence either.
All splashtom files in my MBP have been removed - Or so I thought.
6/29/13 8:35:35.988 AM KiesAgent: Enter detectWifiAgent
6/29/13 8:35:36.462 AM KiesViaWiFiAgent: CPU Usage = 0.0
6/29/13 8:35:37.582 AM KiesAgent: send msg to wifi agent
6/29/13 8:35:37.586 AM KiesAgent: receive msg from wifiagent!
6/29/13 8:35:37.777 AM com.apple.launchd.peruser.501: (com.splashtop.streamer.SRServiceAgent) posix_spawn("/Applications/Splashtop Streamer.app/Contents/MacOS/SRServiceAgent", ...): No such file or directory
6/29/13 8:35:37.778 AM com.apple.launchd.peruser.501: (com.splashtop.streamer.SRServiceAgent) Exited with code: 1
6/29/13 8:35:37.778 AM com.apple.launchd.peruser.501: (com.splashtop.streamer.SRServiceAgent) Throttling respawn: Will start in 10 seconds
6/29/13 8:35:37.993 AM KiesAgent: Enter detectWifiAgent
6/29/13 8:35:39.462 AM KiesViaWiFiAgent: CPU Usage = 0.0
6/29/13 8:35:39.998 AM KiesAgent: Enter detectWifiAgent
Is there a remedy for this?
From what I see maybe the solution lies in accessing 'com.apple.launchd.peruser.501'
Message was edited by: Coorabin
Currently Being ModeratedJul 27, 2013 7:23 PM (in response to ChangeAgent)
Here's what I did to nuke the HP Device Monitor app.... My post is buried somewhere in this thread link below, but copied for your convenience.
Hope this helps.
I've got an HP 8600 and noticed that the HP Device Manager process was always grabbing cpu (no more than 3%) more than what I think a simple monitor task should be. Reading other posts about this, it seems HP has not dealt with it - so here is what I did to remedy it.
You can't delete / rename the process because it is running, and killing the process in Activity Monitor doesn't work because it immediately respawns the process. so..... Boot in Safe Mode to do the work...
Reboot your system and immediately after the startup chime, press the SHIFT key to invoke SAFE MODE bootup. When the login screen appears, in the top right corner, in red, you should see "SAFE MODE". If not, redo this step.
Login. Then in Finder, select Go, Go to Folder and enter "/Library" without the quotes
Navigate to Printers / hp / hpio
In this folder you'll find an app called "HP Device Monitor.app". Drag this to your Desktop for now. This should now have removed the app from this folder. Don't worry about the other file(s) there - leave them.
Restart your system and log in. Test printing to your printer. All should be good - and the HP Device Monitor is history.
Your mileage may vary - but this is how I removed this seeminlgy low value add cpu time waster from my system.
Should you have issues with printing after performig this procedure, just drag the app from your Desktop back to the "hpio" folder and restart. All should be back as it was. Otherwise, after you are satisfied you haven't lost printing functionality, you can toss the file off your Desktop into the trash.