I recently purchased a Samsung Galaxy Note 2 (yes, that ‘gigantic’ phone!), and been having a good time playing with its features and using its stylus to the fullest. The phone works well except for a nagging error that had started showing up now and then, right from the first day of using the device. The error said ‘Unfortunately CloudAgent Has Stopped’ and usually took down whatever app I was working on when I clicked on OK.
It usually popped up when I was in the Photo Gallery, browsing photos, but that wasn’t the only time when it occurred. As you see in the screenshot below, it may also show up on the shutdown screen.
The error isn’t difficult to understand. One can conclude that CloudAgent is a service running in the background that has stopped suddenly. I am not sure if this is a Google service that runs in all Androids or a service specific to Samsung. I can’t tell you what causes this error either. It appears that it has something to do with the auto-upload of Gallery pictures to Dropbox.
Whatever the reasons that cause this error, the good news is that I managed to fix it. Disabling the service altogether is an option and should help you get rid of the error, but I didn’t want to do that. I wanted to solve the problem, not dodge it.
Here’s the solution:
Step 1: Go to Settings on your Galaxy Note 2, and from there to Application Manager.
Step 2: In the Application Manager, you should find a service named CloudAgent either under Running or under All.
Step 3: Here’s what I did in this step, and you might as well follow the same order:
Force stop the service.
Step 4: The simplest step of all: Restart the device.
I went through the above steps once, and haven’t seen that error since then, irrespective of the app or the way I have used the phone.
I would, however, stop short of calling this a perfect solution or the only solution. It worked for me, and I hope it works for you too. But you shouldn’t be surprised if it doesn’t; Android’s flexibility means that it comes with its own quirks and you might need to try different things.
If you are a Galaxy Note 2 owner who has encountered this error, or maybe you own some other device that showed the same error, and fixed it by following a different set of steps then I urge you to share them in the comments below. It’ll help readers for whom the above steps don’t work out.