Transaction crashes

[Chest_Rockfield]

That's okay, for a year and a half, my home computer was a Heroes of Might & Magic III Complete machine by choice.

It really is funny that we are the only two that had transaction crashes and no one can reproduce it.

[Black Wind]

I have an older computer (as in it's never had a hard drive) that I don't recall the last time it contained any disk that's not either for boot or Wasteland.

What I really don't get is we have different phone types and different OS builds. Yet this (apparently very rare) bug affects both of us. I'd expect a bug that rare to be specific to a phone model or an OS build (or a certain combination of the two).

[Chest_Rockfield]

I was surprised when no one else had a FC upon opening x1 every time it opened. I tried everything they suggested, and no ideas from anyone that panned out...

[nyktos]

I have reported similar situatons in past threads,
And it was fixed on the very next update.

Oskar needs to know your phone, provider & RAM
If there is a bug, The Team will find it!

[Black Wind]

This was patched or I might have a fix! For me (on all saves: tests @ Loneford Inn, Foaming Flask, Fallhaven Tailor) this is cleared up.

If it wasn't patched (I downloaded nothing to my knowledge, but AT is set for updating automatically), last thing with my phone - my cat bit it near the on/off button. That says to me I have a magic cat or he clamped/reclamped something by biting.

[Chest_Rockfield]

Droid X, Android 2.3, however much RAM comes in a Driod X

I love cats!

What exactly got fixed for you? The crash when you try to sell?

[Black Wind]

Yeah, it was the crash I'd get trying to sell that left.

The FC on opening still happens sometimes but makes no sense - I get it less than you do even though you have the better phone.

[Chest_Rockfield]

Mine only crashed at the place by my home and I haven't been back there yet...

[Black Wind]

Interesting, makes me wonder if it's a different problem than what I had since for me location never made a difference. I think I had it happen at every location possible before it resolved.

I'm not sure how/why the problem resolved (if it was hardware related it probably should've killed critical system processes sometimes, but never did), so even if it is the same thing I have no clue what might help.

[Chest_Rockfield]

That's the worst part for computertards like me; we don't know enough to even offer help to help them help us.