you can resize and mount the image on the device, you just need to install e2fsprogs…
also the sha256sum of the image will most probably change, when you change some content in it
Thanks, yes, rinigus had suggested some corrections to the README which mentions about resizing on the device itself and it has been updated.
Regarding sha256sum, that is right. Intend is to check it before and after transferring the modified/unmodified image over network, not before and after modification.
1 Like
running commands 8 and 9 cause waydroid folder to be deleted…
Great to see that this issue is reproducible! As for me, in Xperia Tama port: 4.2.0.21 release - #38 by rinigus. We will have to report it to Waydroid devs
For me, it was “session start”. As a workaround, if you change owner to root and then the files will stay intact.
2 Likes
thanks - nvm about the alien conf … I think I just got it.
When looking into https://github.com/waydroid/waydroid/commit/f966cbf22b81960656a2f5694cf28af9171e49a1 - seems like we should not clone into home dir with into waydroid subfolder. As that commit is newer than 1.1.1 used by @lal, it makes sense that only those cloning current state would get the issue
using 1.1.0 fixes issue of folder deletion, but hangs on
“[08:12:47] XDG Session is not “wayland”
[08:12:47] Failed to start Clipboard m
anager service, check logs
[08:12:47] Failed to add service waydr
oidusermonitor: -1”
Not sure how long it’s supposed to take to get “Android ready” message…
As for your workaround about 1.1.1 above - are you saying it will boot Android by doung that, or just that it won’t delete?
It will “boot to Android”
1 Like
or whatever you want to call it 
1 Like
Looks like with KDE Connect installed in both Sailfish and Waydroid, some level of integration can be achieved. Clipboard sharing, file transfer and media control is working pretty well.
Unfortunately Sailfish KDE Connect implementation cannot receive notifications from a connected device yet. That would have been really convenient in this particular use case.
I get notifications from Debian Linux container via KDEconnect using SailConnect app, (ping, pairing request…)
I meant the system and app notifications. If you were running Telegram in Waydroid and someone messaged you, the notification within Waydroid doesn’t get transferred to Sailfish through SailConnect app. That plugin isn’t implemented yet, as described on the app’s page.
1 Like
Question for you about Waydroid on Tama - I get successful start container and start service, (and “puddlejumper has appeared” message), and Android icons show up in launcher, but I never get “Android container ready” message, so full-ui command shows “unable to… trying again …”
Any idea where to start looking for issue ?
Thanks
There is a video on youtube xz2 sailfish os 4.2.0.21 - YouTube
XZ2 with sailfish os 4.2.0.21 looks like with alien dalvik on board
Maybe we can ask Jolla to sell us alien dalvik files for a Tama devices?
It’s been on the tablle for months. We’ve heard that Jolla is “considering it”.
1 Like
hi rinigus, i have serious problems with my xz2c dual sim touchscreen since aarch64. reflashing to android didn’t solve the problem: input lags or processes twice, when i hold my finger on delete it vibrates randomly… update seems to solve it mostly, but i was really irritated again after clean install!
Do you mean that you have the same issue in Android as well? Which Android? AOSP or Stock? Versions of them.
no, in android touchscreen is working fine. i used xperifirm, like you advised in your aosp9->aosp10 guide. then i returned to your newest sailfish and ran immediately in this problem again, which is present for me since aosp10, but it seems to be better after an update of sailfish. btw, waydroid is working and really cool!