Glowworm or OS 1.15? bad mount/unmount and sdcard mount/stay umounted behavior?

[keriflur]

---

roustabout wrote:

" If it happens with a charged battery and units that were never rooted the possibility of finding the problem is even harder"

If it repeats itself, I know that it may not be rooting related and because I am able to run the debugging tools, I can collect information that should be valuable if it starts to happen again.

---

No offense, but I really hope this problem happens to you again.    I'd love to have a fix for it. 

[roustabout]

None taken - I'd love to be able to get it to happen again, since we have access to Alex, et al. pretty directly here, and the BN folks who watch these boards will work with us on well-documented trouble reports, and mine would be pretty well-documented : )

[BN_AlexG Administrator]

Hey roustabout,

I'd like to help out if I can in anyway. Anything reproducible, that you've noticed?

- Alex

[roustabout]

Not yet, no.   

I think Keri actually has the most reproducible version of this we've seen to date, and some really intereting thoughts on how to make it happen -

- low battery

- fight between the OS and the reader app over who owns a book being displayed.

She might be open to letting you ship her a replacement and doing a call with your tech team as they reproduce the error on hers?  Now that mine is cleared, I haven't seen it again.   

[keriflur]

---

roustabout wrote:

Not yet, no.   

I think Keri actually has the most reproducible version of this we've seen to date, and some really intereting thoughts on how to make it happen -

- low battery

- fight between the OS and the reader app over who owns a book being displayed.

She might be open to letting you ship her a replacement and doing a call with your tech team as they reproduce the error on hers?  Now that mine is cleared, I haven't seen it again.   

---

I'll be sideloading a book tonight.  I'll see if the issue occurs again.

[keriflur]

---

keriflur wrote:

---

roustabout wrote:

Not yet, no.   

I think Keri actually has the most reproducible version of this we've seen to date, and some really intereting thoughts on how to make it happen -

- low battery

- fight between the OS and the reader app over who owns a book being displayed.

She might be open to letting you ship her a replacement and doing a call with your tech team as they reproduce the error on hers?  Now that mine is cleared, I haven't seen it again.   

---

I'll be sideloading a book tonight.  I'll see if the issue occurs again.

---

So I finally sideloaded those books tonight and I didn't have any issues this time around.  I had 55% battery, and the nook was open to the library.

[fjrichman]

I've actually noticed this problem after transfering books too my Glowworm, it seems to recognize the card, but sometimes it doesn't appear to check for files on the SD and I'm forced to remove and insert my card again. I believe this to be a bug in the OS version running on the Glowworm itself and related to the mounting/unmounting of the sdcard not running the library update check for the card.