[BluesBoy]

Are you using the device with the keyboard attached or detached? Is WiFi enabled or disabled? What about bluetooth? If you turn those things off and test with the keyboard detached, does the problem still occur?

Mike

Keyboard is detached, bluetooth and wifi are both on. I can try with wifi off but without bluetooth I have no way to turn pages (bluetooth page turn pedal). I can try leaving it on with both turned off when not practicing and see if it's on the recents page after a while.

If you want to share a library backup file (.msb) with mike@zubersoft.com, I'll be happy to test it on my Chromebook to see if I can reproduce the issue, although it will be difficult if it seems to be unpredictable. I'll need to have some way of reproducing the issue.

Mike

Well, I left it on when I went out for dinner tonight and it was on the recents pages when I returned. Wifi and bluetooth were off and, as usual, there was no keyboard attached. I'll get that file to you probably tomorrow.

[BluesBoy]

you mean an SD card? That may be your problem. SD cards made for consumer use are known to have severe quality problems which may manifest in infinite and unpredictable ways. Been there, done that. You may want to switch to industrial grade SD cards,

Thanks for your suggestion. I won't rule it out of hand but it is a decent SD card (Samsung EVO plus), has been fine for the two years that the Chromebook has been in use, and isn't used for storing MobileSheets data or any apps.

A brand name or type is no gurantee for or against anything, it may be conterfeit or mooned:  On MicroSD Problems « bunnie's blog (bunniestudios.com) . Again, I have seen examples of SD cards that looked like (and cost the same as) highly reputed ones but were trash. I do not even want to estimate how many work hours went into trying to debug seeming file system software issues that were in reality storage bugs.

At the very least you should try running a checker over the drive. May save you a lot of head scratching.

Thanks again. I appreciate the concern but I understand the issue of (mostly) Chinese SD card forgeries. I'm pretty fastidious about these sorts of things and this card along with any others that I have bought in the past have all been checked at purchase time.

[jdp72]

Hello,

I am also having the same issue. 

• Chromebook Asus with the latest Chrome OS version.
  
• Bleutooth is enabled --> Pageturner BleuTurn
  
• Wifi is enabled --> Have tried without wifi but had the same problem
  
• No SD Card in the system
  
• I do use it to send midi patch changes to GigPerformer on a Windows OS PC. USB is connected to a midi port. It is really difficult to test without because Mobilesheets does al the patch selecting.
  

 
If i don't touch it for a while, it sometimes stays in setlist mode, but sometime i come back from a pause and it is out of setlist mode. It's really strange since i can't find anything which could do it. So i came to the forum with the hope i could find a solution here or at least a few other options to explore. I was thinking that maybe a midi signal comming from the PC was a problem, but it shouldn't happen since i have nothing programmed to send anything out. But how knows... 

It is really random, sometimes it goes for for more than a hour of rehearsel and then it drops out of the setlist, or sometime after a few minutes.

I really hope someone can point me to a solution. I have a really big musical performance comming up and really on Mobilesheets for all patch changes.

[Zubersoft]

I'm going to do all I can to investigate this, but I need to have a way of reproducing it, as it's never happened to me during testing. So I'm at a loss to explain what is happening. It seems to be mostly happening to ChromeOS users, which makes me think it must be related to ChromeOS, but I have had one or two users mention it happening on standard Android tablets, so I'm not 100% confident about that.

Mike

[Lawrie]

Hi Mike,
FWIW I've had it happen a few times - Boox TabX here.

[aspiers]

Hi Mike,
FWIW I've had it happen a few times - Boox TabX here.

After several years of using MobileSheetsPro on a Google Pixel Slate Chromebook with zero issues, I have seen this problem suddenly appear recently.  It's happened maybe 5-10 times over the last few weeks.  I haven't been able to spot any pattern to it.  Unfortunately the possibility of this happening during an upcoming gig which involves difficult and nonstop music absolutely terrifies me, to the point that I'm seriously considering buying another Chromebook.

I'm telling myself I can justify the purchase not just for this reason, but also because the Pixel Slate is old and has always been horribly sluggish, plus if I have two tablets then presumably I can link them together, which gives me two pages at a time and a backup in case anything goes wrong with one.

I'm guessing that if the Pixel Slate was the secondary device and it suddenly returned to the library screen, there's no way it could cause the primary device to do the same?

[aspiers]

I found this other thread which suggests that Google Play updates can cause MSP to exit.  I realise that's a different issue to it returning to the library screen, but I wonder if it's possible that Play updates could cause both?

[Zubersoft]

Anything is possible, and I haven't had time to really dig into this further yet to see if there's any hope of me reproducing it. If you used the connect tablets feature and had the same song up on both, if one did return to the library screen, it would have no impact on the other.

Mike

[aspiers]

Thanks, that's good to know.

It happened again this afternoon - notably, this time after I'd deliberately disabled Google Play updates and quit every single other app which was running.  So at least we can rule out that kind of interference.

But this is pretty concerning and unfortunately means there's no way I can trust it on this upcoming gig without a backup, as it would totally derail the performance if it spontaneously exited to the library screen while I was in the middle of playing.

It's been a long time since I tinkered with Android stuff, but I remember it used to be possible to do things like adb logcat in developer mode to view logs and see what was going on when something odd happened.  Would that not be possible or helpful in this case?

[Zubersoft]

You could certainly do that to see if the OS itself is reporting anything. I don't think you'll see any information from MobileSheets itself because I don't log any information when returning to the library screen (as that wouldn't normally be useful for anything). While I'd be happy to work with you to run test builds on the Chromebook to try to gather information, it's definitely going to be a shot in the dark, as I have no clue what the source of the issue is, and if it was an application crash, I would get crash reports, and I'm not receiving any that would explain this. The other problem is you can only sideload apps on a Chromebook if the device is in developer mode (which requires powerwashing the device and an annoying warning screen each time the device is booted up).

I just haven't had time yet to sit and focus on this issue. The last time I tried to reproduce it, I ran an automated test for around 6-7 hours and the problem never occurred, so that makes it very difficult to try to run any meaningful tests to track down information.

Mike

[aspiers]

I've already had Linux installed on this device for a long time.  It seems to be allowing me to enable adb with only a restart, and the powerwash is only required if disabling it again.  I guess enabling it might break apps like Netflix which rely on DRM, but not sure if that's the case and willing to risk it anyway.

Wild guess - doesn't the Play Store let you release beta versions which are opt-in?  That might be an alternative to sideloading versions with extra debug.

In any case, I'm up for trying anything to see if we can pin it down.

[Zubersoft]

Alright, I'm running tests today with my Chromebook to see if it returns to the library screen at any point, but if I'm not able to reproduce anything, I'll produce an apk with some logging for you so we can try to gather information. 

Thanks,
Mike

[Zubersoft]

I just wanted to follow up to say that I've been running MobileSheets on my Chromebook on and off for the last 2+ days, and I still have not see this problem occur. I did see an issue where, if the Chromebook fully went to sleep for 10+ minutes, that it would restart MobileSheets completely when I turned the screen back on. The OS itself seems to be doing this, so there isn't much I can do to prevent that. The app has never jumped back to the library screen though, so I still don't have any more information. Aspiers - if it's easy for you to reproduce the issue, we can pursue having a build that logs some information (I'll start with basic information though, just printing stacktraces to understand what is triggering the return to the library screen). 

Mike

[BluesBoy]

I'd be willing to run a special build as well if you want. I continue to have it happen. I was just practicing earlier using MobileSheets and saw it switch. This is the second time that I was looking directly at the screen when it happened and it looked again like some message box of some kind popped up before it switched to the "Recents" screen. It was super quick and I couldn't see any text other than a dark rectangle popping up and disappearing.

[Zubersoft]

That means that the app was completely restarted, because that popup is the "Loading database" progress dialog. It didn't switch back to the library screen - the OS restarted the app, similar to what I saw when the screen was turned off. That's a horribly bad sign, because if the OS is just restarting the app out of nowhere, it's not like I can stop that in my code... With a test build, we can definitely confirm this theory though. Bluesboy - if you have a Chromebook as well, you'll have to use adb to sideload the app (https://www.howtogeek.com/752759/how-to-...oper-mode/). I just want to confirm that you are okay with this though, because it's a little technical. ChromeOS normally requires all installations to go through Google Play.

Thanks,
Mike