Printable View
Hello errybody, I am running stock 4.1.1 VZW GN2, and every dang morning my stupid BAP tries to sync but fails, I have removed the feature from VZW.com, have tried to force stop and I can not disable the app, the option is grayed out in apps as shown in pictures below, any help would be great!
[Only registered and activated users can see links. Click Here To Register...]
[Only registered and activated users can see links. Click Here To Register...]
Thanks!
I feel your woes! :mad: It's never worked right on any of my devices.
When I got my N2, the salesperson activated before I could stop him. The only way that I found to stop it (stock), was to restore the phone & DO NOT let it activate & start up again. Even un-activated, it still can't be disabled.
Ugg, what a waste of resources.
Go into settings and app manager and then find the app that says sync service under all. it will have the same icon as back up assistance. Click on force stop and clear data in there and that will stop backup assistance for you
Sent from my Galaxy Note 2
Same here, I can't stand having co-mingled Google/Vzw contacts. On your Verizon account under Features you need to also remove the BAP feature. I was never sure if disabling the Sync Services app was enough.
Sent from my DROID RAZR HD
That doesnt do anything. Ive done that and disabled it vzw.com.
sent from my galaxy note 2
How are you certain that BAP is still syncing? Let's make sure of that first.
Quote:
Originally Posted by z71kris [Only registered and activated users can see links. Click Here To Register...]
Sent from my DROID RAZR HD
I had the failed notification again this morning, and I had to force stop it again, and its still in my synced accounts list in the settings screen. And its running as I speak, not backing up but in need of being force stopped again.
sent from my galaxy note 2
Unless you're rooted and can freeze things, your only option (as nlitenme alluded to) is a master (factory) reset then upon initial setup skip the Backup Assistant option. If I recall correctly, this was the exact same problem/resolution on the Thunderbolt. :(