Anyone here running the battle.net mobile authenticator on rooted Android device? Rooted other device? Curious if you've had any issues. I realize I'd have to remove the authenticator between flashing roms / restoring applications.
Printable View
Anyone here running the battle.net mobile authenticator on rooted Android device? Rooted other device? Curious if you've had any issues. I realize I'd have to remove the authenticator between flashing roms / restoring applications.
You don't even have to remove it if you use titanium backup to backup/restore it. Its probably still a good idea to write down the original code it gives you though, just in case.
I use to... but you should know that because i posted about it.
have to remove it if you are flashing bios etc etc and re-dl and re-apply.
I used it on a jailbroken iphone, it gave me a warning on the first startup that running on a jailbroken phone was less secure or something to that nature. It worked as advertised. I had to remove the authenticator from my account when i upgraded as you mentioned, but no issues.
I recently went from an RC 6 of Cyanogen to 6.1.1 and the app code changed even when restored from Titanium. Thanks for the replies.
That's interesting. I specifically tested for this and my code stayed the same. I'm certain CM was one of the (many) roms I used to switch between.Quote:
Originally Posted by Svpernova09
I use the dial-in authenticator now and am happier with that. Plus, my rom flashing days are on hold until/if Samsung Fascinate development picks up.