[Xposed Framework Modules] K0media:
Exi for SwiftKey and TaiChi - Latest Reports

Okay, so I came here to compose this intermediate thread and reply, such this is a very complicated and tiresome task.

Let's separate into parts:

1. Facts

2. Exi for SK details

3. Grabbing the right versions of each app

4. The troublesome task

5. Testing...

6. Final word

7. Sources and links

Facts

Well, as a matter of fact, after a long while weishu, who's the head dev of TaiChi itself, did some changes to the core of the engine and so it was reported that it was fixed in the latest build.

Now what's left for me to do is testing. (I'm doing this as I compose this, let's see if it works! )

As you all should know, dealing with non-root TaiChi and other stuff is a very tiring task. That is, I could simply root my device right away, flash Xposed, Magisk and (almost) done. That would save me a lot of time (or not). I just didn't decide to go deeper into this because I'm avoiding to root the device for security reasons, as I've mentioned some time ago in this thread already.

Exi for SK details

Now that I've grabbed the latest version of TaiChi, it's time to do something amazing! (Or not just yet.)

The latest TaiChi supports Exi for SK v2.3.1. I told weishu to support the latest version available, but I guess he just left it the way it is.

Grabbing the right versions of each app

Here's what's needed for the tests:

1. TaiChi v5.2.0

2. Exi for SK v2.3.1 (which is the latest supported by TaiChi. There's an older, but I'll explain later)

3. SwiftKey app: Stable - 7.3.2.19 or Beta - 7.3.3.10 or older. (These are the latest builds compatible with this version of the mod.)

The troublesome task

So my choice at this time was this sequence: TaiChi v5.2.0 + Exi for SK v2.3.1 + SK Keyboard v7.3.2.19. I had to access a lot of sites on the web to get the right versions, so don't expect this will be easy. With this sum, I've started the tests.

Testing...

So, after updating TaiChi to the mentioned version, grabbing the right version of Exi in the Xposed Repo and that version of SK that was supported, I went through a tiring task of installing everything over and over. So I could see the results.

Installing TaiChi went fine. But for the part that it was showing me strange Chinese characters prompting me to update the embedded engine. (I had to throw the images on Google Translate to understand what was happening.)

I thought it wasn't updating as I had Blokada enabled. But then, after disabling it, it didn't work either. We'll see if it works or not...

Then, after browsing on mobile to the right place, I've managed to get Exi v2.3.1, as suggested in TaiChi. It's not Kosher, but anyway...

And fml I realized that v7.3.2.19 of official SK wasn't working at all. So after all this frustration, I had to grab it from other source. I thought about APK Mirror at 1st, but I wanted a newer version, such it was possible to.

After a while, I got the version listed in APK Mirror, selecting what was possible. 1st got the arm64 version, but after attempting to install over TaiChi, when I read the logcat, I realized TaiChi doesn't support 64 bit versions yet.

Back to APK Mirror, got the arm (32 bit) version to try it over. Installed it, and asked to TaiChi to prepare the app to be ready for injected emulated Xposed. And then the long process started.

After a while again, it worked fine. But, when I finally came to the keyboard testing screen, the same error it was showing before popped up in a toast again. Seriously I'm really frustrated as it came to this point and didn't work again. Now I'm going to report to the dev again, but first

I need your help to test this out.

Yes, this is the only way to tell if it works or not. As I don't have spare devices to test here, it's better for you to do it for me.

Don't worry, I've got time for this. This is a long process and it's probably going to take a while to deal with the final results.

If the issue is confirmed on several devices, I'll report again to the dev and we'll see again if he'll take care of the issues.

Final word

So, in the end, this test, once again, was a big frustration. At least I used my knowledge to try to get something working. But in the end, I'll only have this done if you guys help me to know whether it's only my device or not. If it has issues specifically with MIUI, I guess I'll have to skip it and try something else. Or wait for the good will of the dev to see if he takes time to solve it one year or so.

Also, as suggested by TaiChi itself, if you have patience for this, try testing Exi v2.0.4 as well. It will support older versions of SK, but it's my last chance before waiting longer.

Additionally, keep in mind that TaiChi breaks the Google OAuth support. With that said, you'll have to sync with other service, such as Microsoft or Facebook accounts. Currently, it's not possible to sync across multiple and simultaneous accounts, so no big deal for this. I tried exporting my data, but they don't allow me to import back into other service or OAuth.

Sources and links

1. https://github.com/taichi-framework/TaiChi

2. https://repo.xposed.info/module/com.mayulive.swiftkeyexi

3. This thread, ofc

4. https://www.apklinker.com/apk/swift...ftkey-keyboard-7-3-2-19-android-apk-download/ (Tested on MIUI 10, failed attempt)

5. https://www.apk4fun.com/history/10910/ - SwiftKey changelogs (unofficial source, but it keeps track of them)

6. https://www.apkmirror.com/apk/swiftkey/swiftkey-keyboard/swiftkey-keyboard-7-2-3-24-release/ (SwiftKey Keyboard 7.2.3.24 on APK Mirror. 3 variants)

I don't have much time to do this perfectly, so this is the end result I came at for some quick tests. I hope it helps you guys if you want to try to use Exi in a non-root way. If you'd prefer, you can even do a video showing this about how to get it done on your devices, if it ever works. Just let me know. I'll be glad to see it.

[MENTION=6797900]Roughy[/MENTION], if you have enough time and some spare devices to test this on, I'll be glad if you can do so. All the help is highly appreciated. I want to see this working somehow, but I really need to do further tests before telling out if it's only on my device or not. ?