Game save transfer from one playbook to another
Hi fellow CrackBerry Meisters,
I have a 16GB PlayBook and have recently purchased a 64GB version. I want to give the 16GB to my son and keep the 64GB version for myself. I have used the 16GB version for over a year and now use the same BBID on both devices. I am aware of the limitations of this setup e.g. video calling and various apps that will not run on multiple devices running the same ID. What I would like to do is move my bookmarks created on the 16GB to the 64 GB, how would I do this whilst keeping all purchased apps (using the same BBID) on both devices? This also goes for game saves i.e Angry Birds; how do I move the save data for Angry Birds from one device to another?
An couple of extra points I have; one relating to this, the other is not:
I am fully aware of the limitations of running the same BBID on multiple PlayBooks as RIM generally require a separate PIN associated with separate BBID when using a similar hardware platform, to me this is a hangover from an ageing infrastructure that is very reliant on its PIN system (won't be surprised if this whole architecture is changed with the introduction of BB10; and have already seen their work around to this by moving to active sync for business email delivery). Apple currently supports up to 5 devices running on the same ID which generally avoids the scenario I am faced with.
My second gripe is (and I can't really find any other posts regarding this on the internet) why haven't RIM thought about browser bookmark synchronisation across devices? I currently have loads of bookmarks on my BB handset that are not synced with my PlayBook. This means I now have loads of bookmarks on my handset and loads of bookmarks on my PlayBooks which are all out of sync, or have had to create the same bookmark on the different platforms; a real oversite from RIM from my point of view.
Can any of you fellow CrackBerry fans provide any advice on the problems I am experiencing in the above scenarios. I am also aware that there are completely different concerns raised in the same post which should perhaps be broken out into separate topics.
I look forward to hearing you responses.