MobileSheets Forums

Full Version: Android update killed data
You're currently viewing a stripped down version of our content. View the full version with proper formatting.
This morning my Galaxyou Tab S2 pushed an update to 6.01.  Now I can't see any of my song data. I was storing all data on external SD card.  Can't locate any.  Has anyone else experienced this mess and if so what is the solution?

Thanks in advance.
Yes, please read about my troubles and their solution in

http://zubersoft.com/mobilesheets/forum/...p?tid=3320

I assume you have the same problem with the new naming/handling of the SD card with Marshmallow.
Bliz,

Send an email to mike@zubersoft.com and I can help you fix your database. This problem is coming up a lot, but I don't have a good way of fixing it without making some major changes that I've described in other posts (relative paths versus absolute paths).

Mike
(07-04-2016, 11:50 PM)Bliz Wrote: [ -> ]This morning my Galaxyou Tab S2 pushed an update to 6.01.  Now I can't see any of my song data.

As and old (too old, maybe) IT specialist I can't stress enough: If you have a production system do not upgrade anything unless it has been tested extensively, for your environment and your purposes. This was true for a financial department 30 years ago, and it is still true today. If you need a tablet for MobileSheetsPro and you have frequent rehearsals and gigs, the tablet is a production system, don't play with it. Do not upgrade. Never.

My MSPro tablet is running 4.4.4 for a reason.

Mike, maybe it is (slightly) helpful to include a message to that extent in the initial tour information?
(07-05-2016, 02:13 AM)Zuberman Wrote: [ -> ]Bliz,

Send an email to mike@zubersoft.com and I can help you fix your database.  This problem is coming up a lot, but I don't have a good way of fixing it without making some major changes that I've described in other posts (relative paths versus absolute paths).

Mike

What am doing is editing each song in database and pointing to the correct files on the SD card. This seels to work but is cumbersome since each file has to be done separately.
That is one way to do it... I could fix your database in about 10 seconds using a SQL query though. I would just replace all paths containing the bad path at the start with the newer correct path.