05-20-2016, 01:01 AM
As far as I can tell, the problem only occurs on that tablet when running the stock 4.1.2, so I don't think there is anything you can do to help. Thank you for the offer though. I changed very little that could cause this kind of problem between 1.4.6 and 1.4.7, so I'm rolling back one feature at a time, and a user is helping me test each build to see if it has any impact. Hopefully soon I'll be able to figure out what change is responsible.
Mike
Mike