Threema: Restore on Jolla C fails

Question

0

Threema: Restore on Jolla C fails

bug
jollac

asked 2016-07-23 14:36:07 +0300

lenggi

1162 ●18 ●19 ●29

updated 2016-07-23 15:28:40 +0300

When I try to restore a data backup of threema on the Jolla C, the app crashes with a segfault (as it seems):

I/DEBUG   (21736): Build fingerprint: 'Jolla/alien_jolla_l500d/alien_jolla_l500d:4.4.4/KTU84Q/eng.erin.20160505.154502:user/dev-keys'
I/DEBUG   (21736): Revision: 'unknown'
I/DEBUG   (21736): pid: 21870, tid: 21883, name: system_server  >>> system_server <<<
I/DEBUG   (21736): AM write failure (32 / Broken pipe)
I/DEBUG   (21736): signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr 00000000

The backtrace is as follows

I/DEBUG   (21736): backtrace:
I/DEBUG   (21736):     #00  pc 00003308  /system/lib/libwayland_client.so (wl_proxy_marshal+7)

I/DEBUG   (21736):     #01  pc 0000ca33  /system/lib/libalien_glue.so (WLAlienRuntime::data_device_selection(void*, wl_data_device*, wl_data_offer*)+70)
I/DEBUG   (21736):     #02  pc 00000a74  /system/lib/libffi.so (ffi_call_SYSV+56)
I/DEBUG   (21736):     #03  pc 00000c89  /system/lib/libffi.so (ffi_call+112)
I/DEBUG   (21736):     #04  pc 000045f1  /system/lib/libwayland_client.so (wl_closure_invoke+284)
I/DEBUG   (21736):     #05  pc 00002d61  /system/lib/libwayland_client.so
I/DEBUG   (21736):     #06  pc 00002daf  /system/lib/libwayland_client.so
I/DEBUG   (21736):     #07  pc 00003751  /system/lib/libwayland_client.so (wl_display_dispatch_queue+138)
I/DEBUG   (21736):     #08  pc 0000cef3  /system/lib/libalien_glue.so (WLAlienRuntime::runDisplay()+6)
I/DEBUG   (21736):     #09  pc 0000d355  /system/lib/libalien_glue.so (WLAlienRuntime::nativeWindowEventLoop()+164)
I/DEBUG   (21736):     #10  pc 0000fea9  /system/lib/libalien_glue.so
I/DEBUG   (21736):     #11  pc 0000d180  /system/lib/libc.so (__thread_entry+72)
I/DEBUG   (21736):     #12  pc 0000d318  /system/lib/libc.so (pthread_create+240)

Note: a restore of the ID works, but I would rather not miss all the media and chat protocols

Has anyone succeeded to restore? Any help is appreciated to solve the problem.

edit retag flag offensive close delete

Answer 1

2

answered 2016-07-23 15:27:26 +0300

lenggi

1162 ●18 ●19 ●29

updated 2016-07-23 16:30:56 +0300

Okay, to answer my question, I succeeded as follows

Install threema on Jolla C, start it, enter your license code, and close it again
Copy folder /home/nemo/android_storage/Android/data/ch.threema.app to Jolla C (same location)
Stop Android Support on Jolla 1 and Jolla C
Login as root on Jolla 1
Go to folder /opt/alien/data/data/ch.threema.app
Create a tar archive as follows

tar czvf threema-manual-bck.tar.gz cache/ databases/ files/ no_backup/ shared_prefs/

It's important that android support is stopped!
Determine the uid/gid of threema in your system by having a look at the files in /opt/alien/data/data/ch.threema.app, I'll refer to it as $THREEMAID below
Copy the above tar archive to Jolla C and extract it when in folder /opt/alien/data/data/ch.threema.app
Fix ownerships by executing the following in /opt/alien/data/data/ch.threema.app

chown -R $THREEMAID:$THREEMAID cache/ databases/ files/ no_backup/ shared_prefs/
Start Threema on Jolla C

Some notes on this

Threema can only run on one device, so once it is active on Jolla C, the app on Jolla 1 will become inactive
My contact avatars were totally mixed up and I had to manually relink them to fix this
If you require a more detailed walkthrough, let me know in the comments
I could successfully restore a backup made on the Jolla C

edit flag offensive delete publish link

Comments

Dear lenggi, thanks a lot for excellent instructions! Even if they are quite old by now, they still worked for me (back from defect XA2 to Jolla 1 with Threema version 4.2). The main difference is that Alien Dalvik uses /home/.android instead of /opt/alien on the XA2. Further, I had to restore Threema ID via "ID export" and set up Threema preliminarily before Step 8.

mke ( 2019-11-24 21:51:41 +0300 )edit

Answer 2

0

answered 2016-08-07 22:59:45 +0300

FloR707
2025 ●52 ●71 ●76

Hi,

I had no issue transferring my Threema account to the Jolla C. I followed the instruction on the Threema webpage.

Make a full backup as stated in the FAQ. Then copy the backup from /home/nemo/android_storage/Threema/Backups to your new phone, I used my SD card.
Turned off Threema background activity (Setting/Apps/Threema) and power off your Jolla to get the SD card.
On the Jolla C go to the Threema homepage to download the app again. To be able to download the app you need you activation key you received during purchasing the app.
After downloading and installing the app copy the backup from the SD card to the backup folder.
Start Threema and choose restore from backup. In the next dialog window the backup you just copied should show up. Select it and your account should be fully restored.
After restoring Threema will point out that push cannot be enabled because some Google service could not be found. As work arround Threema will offer you to activate polling.
Go the Setting->Apps->Threema to enable the background activity.
To get notifications you have to follow this thread.

edit flag offensive delete publish link

Comments

Migrating Threema from Jolla1 (JP1301) to Xperia X Sailfish OS X (Both 2.1.3.7) worked for me just as described above, except the paths where different for me: /opt/alien/home/nemo/android_storage/Threema/Backups

fl ( 2018-01-03 07:13:46 +0300 )edit

Threema: Restore on Jolla C fails

2 Answers

Comments

Comments

Question tools

Stats

Related questions

Threema: Restore on Jolla C fails

2 Answers

Comments

Comments

Question tools

Public thread

Stats

Related questions