I have a Samsung Galaxy 3, around a year old. Recently it started spontaneously rebooting all the time (like every ten minutes). I also find that when I plug it in to charge, it rapidly blinks on and off - charging, not charging, charging, not charging. Sometimes does that, not always.
I looked on line for possible explanations for the reboot problem, and found sites telling me to delete unnecessary apps that could cause it.
So I looked at what apps I'm running, found lots of things that I didn't know what they are, and turned some of them off. And now - no surprise - things don't work right.
Symptoms:
BadgeProvider
Best face
Blurb Checkout
Bubbles
CapabilityManagerService
ChatON
com.android.providers.partnerboo...
DirectConnectManager
DirectShareManager
Drive (google drive)
Dropbox
Dual Clock (digital)
Favorite Contacts
Flipboard
Google Backup Transport
Google Calendar Sync
Google Contacts Sync
Google Play Games
Google Text-to-speech Engine
Group Play
InteractiveKeyguardTutorial
LogsProvider (that sounded likely, I just turned it back on)
Market Feedback Agent
MobilePrintSvc_CUPS
MobilePrintSvc_CUPS_Backend
Multimedia UI Service Layer
S Memo
Samsung Link
Samsung Print Service Plugin
Samsung Push Service
Software Update
Story Album Widget
TalkBack
Trim
Weather (that's accuweather, which I thought I'd uninstalled - though it shows 0 bytes, so maybe it's just an icon?)
Can anyone tell me what else I should turn back on to solve these problems? it looks like logs might work again now that I turned it on. I now have the logs predating when I started turning things off, though not those from the past week. Progress, maybe?
Thank you!
catteau
p.s. In the interim I put in a different battery, and I don't think I'm having the spontaneous reboot problem any more. That may have addressed the charge-not charge problem as well.
I looked on line for possible explanations for the reboot problem, and found sites telling me to delete unnecessary apps that could cause it.
So I looked at what apps I'm running, found lots of things that I didn't know what they are, and turned some of them off. And now - no surprise - things don't work right.
Symptoms:
- When I try to send or read messages, it (message app) immediately shuts down as soon as I open it. It will do this repeatedly - then stop, and behave normally for a while.
- I no longer have phone call logs - old logs are gone, new ones not created.
- I keep getting messages saying Touch Wiz Home is not working. What is Touch Wiz Home? It is on my list of "all apps" but not in the Running list, nor in the Turned Off list. Same for TouchWiz easy home. What is the difference between them?
- Almost ever time I get a call, it rings maybe once and then I get a message saying I missed the call. (This may have been happening before as well - I don't get many calls, so I'm not sure.
- All of my widget links disappeared - I put some back, but what would I have done that wiped them out?
BadgeProvider
Best face
Blurb Checkout
Bubbles
CapabilityManagerService
ChatON
com.android.providers.partnerboo...
DirectConnectManager
DirectShareManager
Drive (google drive)
Dropbox
Dual Clock (digital)
Favorite Contacts
Google Backup Transport
Google Calendar Sync
Google Contacts Sync
Google Play Games
Google Text-to-speech Engine
Group Play
InteractiveKeyguardTutorial
LogsProvider (that sounded likely, I just turned it back on)
Market Feedback Agent
MobilePrintSvc_CUPS
MobilePrintSvc_CUPS_Backend
Multimedia UI Service Layer
S Memo
Samsung Link
Samsung Print Service Plugin
Samsung Push Service
Software Update
Story Album Widget
TalkBack
Trim
Weather (that's accuweather, which I thought I'd uninstalled - though it shows 0 bytes, so maybe it's just an icon?)
Can anyone tell me what else I should turn back on to solve these problems? it looks like logs might work again now that I turned it on. I now have the logs predating when I started turning things off, though not those from the past week. Progress, maybe?
Thank you!
catteau
p.s. In the interim I put in a different battery, and I don't think I'm having the spontaneous reboot problem any more. That may have addressed the charge-not charge problem as well.