[QUESTION]: How can I restore my backup from 30.43 into the new stable?

[rpgdev]

Checklist

• [x] I made sure that there are no existing issues - open or closed - which I could contribute my information to.
• [x] I have read the FAQ and my problem isn't listed.
• [x] I have taken the time to fill in all the required details. I understand that the bug report will be dismissed otherwise.
• [x] This issue contains only one bug.

Affected version

30.56

Device Type

Smart TV/Box

Affected Android

Android TV 14

Steps to reproduce the bug

1. export a backup from 30.43
2. import backup into 30.56

Actual behavior

Backups from version 30.43 are not being imported. I see the file structure of the zip file has changed between versions but not the actual shared_prefs (at least didn't seem to from a cursory look). I modified the exported backup to fit the new structure, but that didn’t work. How can I import my backup from a .dot version that happened right before?

Changing the backup process right after a major break from the app that forces people to install a new one because of the compromised developer keys wasn’t a good call. Can we get an update pushed to the app that also recognizes the previous backup format? I don’t want to go through all those settings again man 😭😭

Additional information

No response

[count0x30]

I just went through the backup->update->restore process, and it works, but the folder structure probably got messed up.

Up until 30.48, the shared_prefs folder was in /storage/emulated/0/data/com.teamsmart.videomanager.tv/Backup/

Now, in 30.56, it has to go in /storage/emulated/0/Android/media/org.smarttube.stable/data/org.smarttube.stable/Backup/

That double org.smarttube.stable in the path is NOT a typo. Put your shared_prefs in that folder, do a restore within the app, and everything should be just as it was!

[CaptainBlagbird]

I have never made a backup, didn't even know that this option was added... Am I SooL now that the old one can't be started, or is there a way?

[count0x30]

If the app was blocked by Play Protect, then it should be possible to get it running again. Check out this thread: #5127 .

[eisbaer274]

I saved settings on google drive and could restore backup settings from google drive in new 30.56 version...

[CaptainBlagbird]

If the app was blocked by Play Protect, then it should be possible to get it running again. Check out this thread: #5127 .

Thanks for the hint. This worked for me:

1. Re-enable the old version via adb: adb shell pm enable <package name of the disabled app>
2. Start the old app
3. Create a local backup via the menu in the settings
4. Move the backup to the location of the new app (as shown in the local backup menu in the settings of the new app), making sure the folder structure is correct
5. Restore local backup in the new app
6. Then I uninstalled the old app for the obvious security reason

Disabling Play Protect was not necessary for any of this.

[rpgdev]

I saved settings on google drive and could restore backup settings from google drive in new 30.56 version...

I ended up doing this and it worked. I had not connected a a gdrive accnt to smarttube but the most painful thing is dealing with the fs on my TV so I gladly set it up just to avoid it. I messed with it long enough already. Thank you!

[rpgdev]

If the app was blocked by Play Protect, then it should be possible to get it running again. Check out this thread: #5127 .

Thanks for the hint. This worked for me:

1. Re-enable the old version via adb:
   `adb shell pm enable <package name of the disabled app>`

don't you need root for this though?

[CaptainBlagbird]

don't you need root for this though?

No, root access is not needed for that, I don't have root access on my device.

Actually for that reason, pm disable <pkg> or pm disable-user --user 0 <pkg> is also a nice way to get rid of bloatware apps on devices that you don't want to unlock.

[rpgdev]

don't you need root for this though?

No, root access is not needed for that, I don't have root access on my device.

Actually for that reason, pm disable <pkg> or pm disable-user --user 0 <pkg> is also a nice way to get rid of bloatware apps on devices that you don't want to unlock.

but did you get to adb on the device itself? Which tool do you use for that?

[zopieux]

Can we please pin https://github.com/yuliskov/SmartTube/issues/5160#issuecomment-3610463212 to the top of the issues list? This saved me 30' of trying to incorrectly port all of the tweaks I made over the years which I can't live without. Thanks for sharing this workaround pending a better solution.

[SimpleCreations]

The Google Drive method didn't work for me, however I've managed to fully migrate all settings via the file system. Here are the steps, hope this helps someone.

1. Open the old SmartTube Beta
2. Create a local backup from settings
3. Connect via adb
4. Pull the backup: adb pull /storage/emulated/0/data/com.liskovsoft.smarttubetv.beta ./
5. On your computer, open the the ./com.liskovsoft.smarttubetv.beta/Backups/shared_prefs directory and rename com.liskovsoft.smarttubetv.beta_preferences.xml to org.smarttube.beta_preferences.xml
6. Create the backup directory for the new app: adb shell mkdir -p /storage/emulated/0/Android/media/org.smarttube.beta/data/org.smarttube.beta
7. Push the backup into the new location: adb push ./com.liskovsoft.smarttubetv.beta/* /storage/emulated/0/Android/media/org.smarttube.beta/data/org.smarttube.beta/
8. Open the new app
9. Restore the local backup from settings

Notes:

• This is for SmartTube beta; if you use the stable version, adjust the package names.
• You can probably do the above with a file manager instead of adb if that's easier for you.

[CaptainBlagbird]

but did you get to adb on the device itself? Which tool do you use for that?

I used adb on my PC, and connected to the device via WiFi. Needs enabling in the developer setting of the device. I'm sure you'll find videos or other guides for this.

[GollyJer]

The Google Drive method didn't work for me, however I've managed to fully migrate all settings via the file system. Here are the steps, hope this helps someone.

1. Open the old SmartTube Beta
2. Create a local backup from settings
3. Connect via adb
4. Pull the backup: adb pull /storage/emulated/0/data/com.liskovsoft.smarttubetv.beta ./
5. On your computer, open the the ./com.liskovsoft.smarttubetv.beta/Backups/shared_prefs directory and rename com.liskovsoft.smarttubetv.beta_preferences.xml to org.smarttube.beta_preferences.xml
6. Create the backup directory for the new app: adb shell mkdir -p /storage/emulated/0/Android/media/org.smarttube.beta/data/org.smarttube.beta
7. Push the backup into the new location: adb push ./com.liskovsoft.smarttubetv.beta/* /storage/emulated/0/Android/media/org.smarttube.beta/data/org.smarttube.beta/
8. Open the new app
9. Restore the local backup from settings

Notes:

• This is for SmartTube beta; if you use the stable version, adjust the package names.
• You can probably do the above with a file manager instead of adb if that's easier for you.

What device did you do this on? I have a Google 4K streamer and it won't allow me to access the data folder.

[gitttt54]

I made a local backup in smart tube and smart tube beta to the default folders. installed the new apps via adblink (both 30.64) and restored the local backup just as easy as it should be from the started apps. great!