Conversation
Notices
-
So flashing Cyanogenmod onto my GTab seems to have solved all my issues with the device, including, absolutely bizzarely, my inability to purchase paid content from google play.
Monday, 17-Sep-12 18:40:18 UTC from web-
@ceruleanspark I think Cyanogenmod uses a very generic build.prop, whereas if Samsung had screwed about with the build.prop on your stock install, then it might've shown up as some obscure build the market wasn't willing to support. (I'm just guessing here, but build.prop is _usually_ the root of rom-specific Play Store weirdness.)
Monday, 17-Sep-12 18:48:19 UTC from web-
@bitshift Weirdly it wasn't device identification or anything like that, it just wouldn't authorize payment, ever. It'd just error out instantly.
Monday, 17-Sep-12 18:49:11 UTC from web-
@ceruleanspark Huh, now that is odd. I'm gonna go ahead and blame Samsung though, considering how much stuff they ****ed up on their stock rom on my S2. :P
Monday, 17-Sep-12 18:54:01 UTC from web-
@bitshift Yeah. Samsung are definitely at fault on that one. My Odin counter is at 9 now though
Monday, 17-Sep-12 18:58:40 UTC from web-
@ceruleanspark Protip: Samsung do not give any hoots about Odin counter, as long as you haven't pretty much literally exploded your device by flashing a rom.
Monday, 17-Sep-12 18:59:54 UTC from web-
@bitshift Is there a known way I can set it to some stupidly high number
Monday, 17-Sep-12 19:01:29 UTC from web-
@ceruleanspark Other than actually flashing it that many times, none that I know.
Monday, 17-Sep-12 19:02:13 UTC from web-
@bitshift 6.7 millon flashes it is then!
Monday, 17-Sep-12 19:03:06 UTC from web
-
-
-
-
-
-
-
-
