License deactivating after turning off device

[Steve70]

Hi, I bought an android license for launchbox for my GPD XP, running Android 11.

Added licence to launchbox by using the browsing method to my download folder on my GPD and launchbox reloaded to remove 100 game restriction. 

It reloads and my name appears as registered, spent a few hours setting things up adding my games and Retroach etc.. and played for a while no issues. 

Switched off my GPD. Upon next switch on I had lost everything I'd set up and it showed it wasn't licensed.

I again browsed and attached the license and it did the reboot of launchbox all good, showing my name again, but sadly nothing else I'd spent a few hours earlier doing. 

So I added just one system as a test, all good. 

Then I switched my GPD off and on again and launchbox has gone back to unlicensed. 

It doesn't become unlicensed if I close and reopen launchbox, but everytime I switch off my GPD it loses the license and anything I've set up. 

Any help appreciated.

 

[Steve70]

Hi again.

Hopefully I have rectified this.

I move the Launchbox folder to the internal storage and put the license key in the Launchbox folder and also in the data folder (not sure if the license key needs to be in either of those places).

Then, I went into the options menu and used the data folder option, to browse and point it to the new location of the data folder, within the Launchbox folder.

[Jason Carr]

On 2/11/2022 at 1:25 PM, Steve70 said:

Hi again.

Hopefully I have rectified this.

I move the Launchbox folder to the internal storage and put the license key in the Launchbox folder and also in the data folder (not sure if the license key needs to be in either of those places).

Then, I went into the options menu and used the data folder option, to browse and point it to the new location of the data folder, within the Launchbox folder.

@Steve70 I'm sorry to hear about this. I think what happened is the device updated to Android 11 or 12 on reboot, which ultimately caused this issue, because Android changed file system permissions with that upgrade. All the emulators and frontends have been dealing with pain points like this due to these updates.

For what it's worth, we just put out LaunchBox for Android 1.0, which should resolve this and related issues.

[Steve70]

On 2/16/2022 at 12:49 AM, Jason Carr said:

@Steve70 I'm sorry to hear about this. I think what happened is the device updated to Android 11 or 12 on reboot, which ultimately caused this issue, because Android changed file system permissions with that upgrade. All the emulators and frontends have been dealing with pain points like this due to these updates.

For what it's worth, we just put out LaunchBox for Android 1.0, which should resolve this and related issues.

Thanks for the reply. 

I'm on Android 11.

No further issues for me, after I did what I did above. 

Updated to 1.0, without any issues.