+- HP Forums (https://www.hpmuseum.org/forum)
+-- Forum: HP Calculators (and very old HP Computers) (/forum-3.html)
+--- Forum: HP Prime (/forum-5.html)
+--- Thread: Android emulator won't list - reset (/thread-5339.html)
Android emulator won't list - reset - StephenG1CMZ - 12-15-2015 10:01 PM
Having recently updated to the latest emulator (about a week ago) I was hoping it would be more reliable - and for the first week it did seem to crash less often. and I was pleased to see that the update did not erase my programme.
But then I discovered that Shift LIST would crash instead of opening the list editor -:something I don't use often, but very useful when I do. and attempting to open my ZIPP program for editing crashed the emulator too.
I have just done a reset, so hopefully that will help...I did a backup first.
Here's hoping that Santa will make the next release much better.
RE: Android emulator won't list - reset - Tim Wessman - 12-19-2015 01:17 PM
(12-15-2015 10:01 PM)StephenG1CMZ Wrote: But then I discovered that Shift LIST would crash instead of opening the list editor -:something I don't use often, but very useful when I do.
I'm unable to reproduce this on our end with many different systems. Could you please send an email with more details about your device/android version? Thanks.
RE: Android emulator won't list - reset - Fortin - 12-19-2015 03:19 PM
I've had something similar happen with the HW when I had a program that didn't 'check' and then warmstarted on exit due to the syntax error resulting from duplicate/modified 'export's. Until that was resolved, the list editor, memory manager, editing in the program editor and sometimes even cold starts would cause a crash.
I was unable to use the CK to obtain a backup or browse to the program from the tree control. This would always result in a crash of the CK. I ended up 'send'ing the program from the HW to the VC, then saving the program from the VC using the CK. I formatted the HW and restored my backups and everything has been fine since.
I also experienced a similar situation on the previous Android release, but just cleared the app data to resolve it.