yashsingh1/xdaforums huggingface dataset:
[Xposed Framework Modules] Roughy:
If it crashes while creating the app the problem is purely with Tai-Chi, seeing as Exi doesn't come into play until the modified app is installed and the Exi module enabled. However, it seems pretty clear what it's unhappy about.

Abort message: 'thread.cc:2165] No pending exception expected: me.weishu.exp.core.CreateFailedException: do not support 64bit now.'

Are you on an ARMv8 device?

Tai-Chi's apk only seems to be compiled for armv7; I'm not seeing any armv8 libs in there. Not sure if this means you need to use the armv7 variant of Swiftkey even if your device is armv8. Maybe try if you run into trouble.
[Xposed Framework Modules] fijasko:
Yes, my device is armv8, so just now, I tried with armv7 variant of SwiftKey and TaiChi was able to create the new app, but the actual keyboard won't start.

See attached screenshot.

Edit: Modified SwiftKey starts normally only with Exi module uninstalled.
[Xposed Framework Modules] Roughy:
That's progress at least.

The dra class mentioned in the error is one of the classes we hook to insert popupkeys.

That is neither the first hook we create, nor the first one that is triggered, which suggests that most of the hooks are at working okay.

I'll probably have to make some Pie-specific adjustments.

I'll get everything set up in an emulator, but given the performance penalty it'll probably take me a couple of hours, so that will have to wait until tomorrow.

Stayed tuned for updates.
[Xposed Framework Modules] Kglim:
That shouldn't be happening.

I know it doesn't work at all on some Chinese layouts, but this is the first I've heard of it only working if done really fast.

Could you tell me your version of Android, Swiftkey, and the module? Also what keyboard language/layout and any options that may be changing the layout.

///

Im using android 8.0.0 with alexis rom 6.0.1 with nx r19 kernel. (+systemless xposed 90.2 api 26)

Also using latest version of swift key.

Perfectly works fine on english but with my korean language only works if i swipe up the space bar really fast.

The special thing is im using swipe space bar to change my language. (the stuff that samsung support)

Btw huge thanks for your work!!!ʘ‿ʘ
[Xposed Framework Modules] Zordak7:
Hi!

There is a weird bar on the rigth edge of the keyboard, which dessapears on landscape mode. How can I get ríe of it? I've been looking in the module options, with no luck. Screenshots attached.

Saludos!
[Xposed Framework Modules] Uraniam9:
[MENTION=6797900]Roughy[/MENTION] I try to create swiftkey in taichi but the taichi crashed in middle
[Xposed Framework Modules] Roughy:
I'm not able to make the default (single-vowel?) keyboard layout do anything weird, though some of the alternative layouts are broken because they don't actually have space bars.

Swiping the space bar to change the language is a standard Swiftkey feature. Is it different from that?

Could you give me a very detailed rundown of the exact layout settings and languages you have installed in Swiftkey, and the settings you are using in Exi?

A screenshot and possibly video of the quick-menu failing would also be helpful.

There is some logic in place to block certain actions when we detect a popup with multiple keys. The language popup that appears above the space bar is technically a popup, but it should be a "single key" one and thus not cause any problems. That shouldn't actually block the quick menu though, only swiping.

I can't reproduce your exact issue on the normal layout, but the compact layout is foobar'd in a similar way. No idea when that started happening. Will fix.

Have a look at my previous post. Tai-Chi seems to work in Nougat, but I will probably have to make some special adjustments for pie. Which I will do.
[Xposed Framework Modules] Roughy:
Says it is being force closed. As I explained in my first Tai-Chi post the one-time setup takes a very, very long time when using Tai-Chi. Expect it to freeze at the splashscreen for 5-10 minutes.

See my earlier post for details.

also, 7.2.1.17 with Exi 1.8.1 means the emoji panel will be broken.
[Xposed Framework Modules] Roughy:
@Addicted-Adnan @fijasko @Techvir

Bad news.

I was hoping Tai-Chi had a relatively simple form of checking if the module was approved so I could test newer versions, but alas it appears to be using a hardcoded hash or something, stored somewhere in the native libraries. That means it's impossible for me to test or debug.

I'm reasonably sure this is a problem with Tai-Chi/Exposed itself, rather than Exi, so there probably isn't anything I can do to fix it anyway.

When we hook a method, Xposed basically replaces it with a native implementation, which then calls the original method in addition to our hooks. What appears to be happening is that the Android runtime decides this replacement is not allowed to access a certain other class, which in this case is a subclass of the class the original method belongs to.

java.lang.IllegalAccessError: Illegal class access: 'dro.x2892999108' attempting to access 'dro$a' (declaration of 'dro.x2892999108' appears in Anonymous-DexFile@0xb0b8e000-0xb0b8e438)
at dro.x2892999108.a(Unknown Source:55)
at dro.a(s:150)

This does not occur in the body of the hook (i.e. the stuff we're doing ), but in the body of the original method we are hooking, I think.

Most likely the problem would persist even if we added an empty hook there, so basically we cannot hook that particular method.

I believe the author did mention that Pie may be somewhat unstable.

Assuming this only occurs in certain relatively rare scenarios it probably would be possible for me to work around the problem, but this would require a lot of trial and error, which is not going to be possible as long as Tai-Chi limits the version of Exi it will run.

Soooooo we're screwed for the time being.
[Xposed Framework Modules] Gbrl95:
I don't know but somehow it is already fixed. I flash via odin the latest stock rom that is available for my phone, flash xXx no limits, debloat, then restore data, viola. Thanks!
[Xposed Framework Modules] Uraniam9:
[MENTION=6797900]Roughy[/MENTION] thank you bro for your hard work on exi and for dedication you did to make it work on pie. Sorry if you don't like this qs but it's always in my mind

Isn't it possible to implement exi classes and methods directly into swiftkey rather than hooking and its ok if we ignore next updates like there is a famous module gravity box now most feature are already there in native custom roms also does accebility services has anything to do with non xposed framework like max lock xposed module has acc/xposed implementation
[Xposed Framework Modules] Roughy:
It isn't impossible, but the effort required makes it unfeasible.

Injecting a bit of code and using to to Epic to do what we are already doing ( like Tai-Chi ) does would be more feasible, but would still require a ton of work and research.

I would really like to look into doing something like that, but I also have a bunch of other projects that I want to work on.
[Xposed Framework Modules] ZellZoy:
Aw man, I thought I had finally found the perfect keyboard to replace Swype as this was gonna address everything from Swiftkey that's missing to me. Thing is, I can't seem to get it to work. I'm on a Huawei Honor 8 on Android 6.0. I just downloaded the lastest Swiftkey (not beta) and latest version of this module. After I enabled it and rebooted, it still doesn't seem to be affecting swiftkey at all. Feature I am most interested in the the modifier key shortcuts, but even transparency isn't working either. Do I need to grant permission somewhere? Like root permission or something? Or do I need to change a setting in Swiftkey?

edit: Apparently I was on 1.5.2 (that was the latest version in xposed repo). When I updated to 1.8.2 in this thread, it now seems the keyboard doesn't popup at all.
[Xposed Framework Modules] Roughy:
The Xposed Installer doesn't update its list properly anymore, so you have to go to the xposed repository in a browser to get the latest version.

The first time you open the keyboard after activating the module, it will go through a one-time setup that can take some time to complete.

The keyboard won't open until it has finished. It should only take 20 seconds or so, but may take longer on slower devices.

I would recommend opening the Swiftkey app directly ( not the keyboard ) and waiting for it to fully open. It will be stuck on the splashscreen while the module does its thing. If you get a "Swiftkey has stopped responding" dialog, just click "wait".

This process is performed every time Swiftkey or this module is updated, as it needs to search for the classes and methods it is going to hook. The results are cached and subsequent launches are not affected.

If anything goes horribly wrong with the module it will leave messages in the xposed log.

You can also monitor the progress of the hooking process via logcat.
[Xposed Framework Modules] ZellZoy:
Thanks for the quick response. Opening Swiftkey app directly fixed it.

Now I am just trying to figure out the modifier key option. Shortcuts with space work just fine, but any other key I add does, and I don't even see an option to use they 123 key (unless that's the symbol key).
[Xposed Framework Modules] Roughy:
123 key is indeed the symbols key, and what it is set to be default.

The quick-menu is ultimately a lot more useful than the modifier key + key combo though.
[Xposed Framework Modules] KaMyKaSii:
There is a Chinese developer trying to port Xposed to Magisk. Resource hooking is still not supported so modules like Exi for SwiftKey (which modify the target app's interface) will not work correctly, only those that modify functions under the hood. Maybe you can contribute to the project, [MENTION=6797900]Roughy[/MENTION]? Of course only if you have time and are willing ;)

https://github.com/solohsu/EdXposed

https://drive.google.com/drive/u/0/...5qFFjVHoXyomOPwVxhnNawjdO?sort=13&direction=a
[Xposed Framework Modules] Roughy:
I imagine you are talking about the Tai-Chi Magisk module, that allows you to hook system components as well.

We don't really need to hook any system components, so there wouldn't be any advtange over normal Tai-Chi.

We've discussed and tested Tai-Chi over the past couple of pages of this thread. There are problems with running Exi for Swiftkey in it on pie ( works fine on Nougat ). I can probably work around those issues, but since Tai-chi whitelists specific versions of the module, I can't test any changes I make.

Edit: Oh hey, you linked to something. I'll have a look at that.

Exi actually doesn't have any resource hooks. It relies entirely on method hooks and reflection.
[Xposed Framework Modules] KaMyKaSii:
It's not TaiChi, it's a similar project from another developer. But this time without a new app to manage the modules, only the Xposed Installer (but the version modified by DVDandroid, for having support to Xposed systemless). As I said, this new framework is still premature and does not yet have resource hooking but is a promising project. But I just tested Exi for SwiftKey here and it really worked but a bit buggy (I had to disable the ways of sliding in Exi to be able to slide correctly in SwiftKey). But basic functions such as vibration when touching emojis and allowing improper GIFs worked. I'm on Oreo but I believe it will also work on Android Pie
[Xposed Framework Modules] Roughy:
Just installed it on pie. Everything works! And from what I can tell flawlessly too, at least one my Oneplus One.

All the swipe selection modes seem to work fine, and the quick menu too.

Unlike Tai-Chi there is no performance impact, everything runs just as fast as Xposed.

Thanks for letting us know about this!

If by "I had to disable the ways of sliding in Exi to be able to slide correctly in SwiftKey" you mean you had to disable swipe-selection to use flow input, then that's intended. They both use the same gesture, so you can't use flow when you've got swipe-selection mode set to "everywhere".

[MENTION=9380335]Addicted-Adnan[/MENTION] [MENTION=4549435]fijasko[/MENTION] [MENTION=537184]Techvir[/MENTION] yo check this out
[Xposed Framework Modules] drjat:
I am very excited to hear this. I am keen to learn how this is installed and does it cause safetynet fail on your Oneplus?
[Xposed Framework Modules] Techvir:
Can you help me with the steps that you took to install this ?

Thanks... Will try it out today...

This is great news
[Xposed Framework Modules] Roughy:
The process is as follows:

Have a phone with Magisk installed.

Apparently works with both AMv8 and ARMv7 now, but try ARMv7 if you run into trouble.

Download the follow files from the link @KaMyKaSii provided:

Edit: Also available via the instructions on EdXposed's github page: https://github.com/solohsu/EdXposed

magisk-riru-core-arm-arm64-vXX.zip

magisk-EdXposed-arm-arm64-vXX.X.X_beta-release.zip

XposedInstaller_by_dvdandroid_XX_XX_XX.apk

Download the latest version of each.

The first two are Magisk modules. EdXposed is a wrapper for Riru.

Install them via Magisk, and then the custom XposedInstaller by dvdandroid apk normally.

Install Exi for Swiftkey, and the ARMv7 ( ARMv8 maybe fine now) variant of Swiftkey / Swiftkey Beta from [ ApkMirror ]

Active the module in the custom XposedInstaller and reboot. You should be good to go.
[Xposed Framework Modules] fijasko:
[MENTION=6797900]Roughy[/MENTION]

There's more about EdXposed in this thread: https://xdaforums.com/xposed/android-9-0-xposed-solutions-t3889513

I'm a bit worried because it's closed source. Some devs are advising against using it for now.
[Xposed Framework Modules] KaMyKaSii:
You're welcome!

I think I misinterpreted the purpose of this feature because of the Brazilian Portuguese translation, maybe I'll make some corrections later. By the way, in github, why the name of the Brazilian Portuguese translation is "values-pt-rbr" instead of "values-pt-br"? And in the next update, could you add an option to select the language of the app? Thank you!

Here on Oreo I can still pass safetynet, but this may only be a matter of time until safetynet developers find out about EDXposed. And if the developer of EDXposed does not take this issue seriously to keep as few traces as possible from now on at the beginning of development, in the future it will probably be too late (because it would require full rebuilding of the project base, which no developer wants)

It is also necessary to install the latest version of magisk-EdXposed-arm-arm64-vX.Y.Z_beta-release.zip in Magisk, at the moment that I am writing is v0.2.8.5

Edit: And if you find the error "Xposed is installed but not active", go to TWRP, wipe dalvik cache and restart

In my first post it contains a link from the EDXposed page in github so I think it's open-source
[Xposed Framework Modules] Techvir:
Unfortunately Edxposed does not work on Note 9 or may be even any Samsung devices yet... Wait Continues
[Xposed Framework Modules] KaMyKaSii:
Did you wiped dalvik cache on TWRP as I suggested earlier? I was having the same problem on my Zenfone 4 and Xposed got active after doing this
[Xposed Framework Modules] ZellZoy:
So it seems that no matter what modifier key I choose, and if I choose quick menu or key combo, only spacebar works.
[Xposed Framework Modules] fijasko:
[MENTION=6797900]Roughy[/MENTION]

With EdXposed, Exi only showed changes I made in popup keys, nothing else seemed to be working. Also I had a couple of crashes.

Didn't have much time last night to test it properly and had to uninstall, but as soon as I find time, I'll post here.

Thanks everyone, especially Roughy.
[Xposed Framework Modules] Roughy:
Failed hooks should show up in the xposed log, and both them and Swiftkey crashing outright should appear in logcat.

I wonder if one might have more luck with the ARMv7 build of Swiftkey, if you are on an ARMv8 device.

I may not be able to fix anything, but it would be interesting to see what is going wrong.

The Pie rom I tested on had SELinux running in permissive mode because it is super broken, which may also have affected my results.
[Xposed Framework Modules] Roughy:
I think you may have gotten a bit mixed up here. Admittedly the instructions I wrote are terrible.

The modifier key is for hotkey combos, configured in the hotkeys tab. You hold one key and press another, like you would with ctrl + c for instance on a keyboard.

By default the modifier key is configured to the Symbols (123) key, so press that with one finger, and press c with the other to copy text.

The space up-swipe mode ( this is a terrible name ) on the other hand is hardcoded to the spacebar. It is not at all affected by what the modifier key is set to. You can either use it with the quick-menu, or in hotkey mode where you swipe up to the corresponding key configured in the hotkeys tab.
[Xposed Framework Modules] ZellZoy:
Ah ok, that makes sense (and works). I was trying to set it up to work like Swype does, dragging from the corner to the hotkey. Holding them both is kind of uncomfortable, but dragging from space instead is easy enough.
[Xposed Framework Modules] fijasko:
You were right as usual. I installed armv7 variant of Swiftkey and everything's fine. Thanks again!

Now I use EdXposed for Exi and TaiChi for XInsta. A bit complicated, but it works.
[Xposed Framework Modules] Uraniam9:
[MENTION=4549435]fijasko[/MENTION] hey man are you on Android pie with exi working with Ed Xposed?

I tried earlier but swiftkey crashed and I also posted stepwise logcats in this thread
[Xposed Framework Modules] fijasko:
Yes, I'm on MIUI 10 which is Android 9.

EdXposed has been updated since you tried to install Exi. Follow Roughy's instructions here: https://xdaforums.com/showthread.php?p=78729290 but instead of v2.8.5 use the latest 2.9.0 from the link in the same post. Also, use the latest Exi version 1.8.2, not 1.8.1.

Also, if your device is armv8, use armv7 variant of Swiftkey. All info thanks to Roughy.
[Xposed Framework Modules] Uraniam9:
I think Core 11 is not working with arm64
[Xposed Framework Modules] oroboros74:
Just lurking atm, but wow! what a time to be alive! Lol
[Xposed Framework Modules] Uraniam9:
P. S exi working smoothly with core 11, finally our dream came true thanks to ED Xposed developer and our fav [MENTION=6797900]Roughy[/MENTION]

Cheers!
[Xposed Framework Modules] Medicineguy:
Could you please delete this reply?

The module started working for me.

Thank you.
[Xposed Framework Modules] Indranil0:
Keyboard not opening after installed :(

xposed log attached

Os- lollipop
[Xposed Framework Modules] Roughy:
Log doesn't contain any information pertaining to this module other than the Xposed Framework loading the module itself.

It does not contain any error messages, or even the message we print when Xposed executes the hook entry point.

I have an inkling the xposed bridge doesn't process log entries while we're hogging the main thread, so logcat output is generally more useful.

Having said that ...

Most likely you are not waiting long enough for it to complete its one-time setup, searching for the classes and methods it will be hooking.

On a semi-recent device this should take something like 20 seconds, but may take longer on older devices.

If you are on a slower device it is advisable to open the Swiftkey app directly and waiting for it to fully open. It will freeze on the splash screen until it is done.

Subsequent launches will be instantaneous, but this process needs to be repeated when Swiftkey or this module is updated.

I did implement a proper progress meter and such at one point, but due to a bug in the Xposed framework we are forced to prevent the app from doing any other work until we have finished the hooking process.
[Xposed Framework Modules] Indranil0:
waited more than 15 min. And my device getting freezed between some times so i uninstalled. Will upload full logcat soon after installed.

EDIT: sorry, it worked like a charm. I stopped the keyboard when not responding dialog appears. Thanks, now working.
[Xposed Framework Modules] Indranil0:
Could we expect these features :D

1. Keyboard change toogle

2. Different size of keyboard for portrait and landscape.

Thanks
[Xposed Framework Modules] andrizmitnick:
somehow, my shift key isn't working, how do i fix this? my language is english (us), on edxposed pie. thanks before.

update:

i finally found the issue, it seems to be caused by "From Shift/Delete" option of Selection Mode section, disabling that option makes my shift key work again. is it a bug?
[Xposed Framework Modules] Roughy:
Not sure what keyboard change toggle would be.

The keyboard size multiplier thing could have a separate setting for each orientation... maybe.

There is a fairly complicated system set up to handle the shift key, as we /sometimes/ need to prevent it from firing. We accomplish that by keeping track of when it was hit, blocking it, and then maybe triggering it manually depending on whether the user completes a tap action or starts swiping.

As a result of this I was aware that long-pressing it to make the keyboard enter permanent upper-case mode doesn't work, but if tapping it normally doesn't do anything either then we may have an EdXposed-specific issue on our hands.

Logcat please!
[Xposed Framework Modules] Indranil0:
Thanks, what's about the undo/redo for lollipop? I have seen you said for marshmallow, is this functionality is impossible for lollipop?
[Xposed Framework Modules] Roughy:
It's available on Marshmallow and later because it's built into Android itself, and all I need to do is tell it to ... do the the thing.

For Lollipop I would have to hook into all input fields and manually keep track of all this stuff.

There is an existing module that adds undo/redo to lollipop, but it only adds them as clickable options in the text menu. If the developer were to make it react to the same text action codes that are used in Marshmallow and later, all I would have to do is check is the module is installed and enable them in Exi.

That's up to them though. I believe it's open source so anyone can implement the feature there and make a pull request.
[Xposed Framework Modules] Indranil0:
Like Gboard, long press spacebar( or any customizable key) will popup list of all installed keyboards.
[Xposed Framework Modules] oroboros74:
I was actually going to suggest this feature! This would be very useful for those of us that constantly switch between orientations, like on tablets.
[Xposed Framework Modules] Uraniam9:
[MENTION=6797900]Roughy[/MENTION] Feature requests

Is it possible to close keyboard on swipe down

(in case of flow)

Can you add button tint like kt2 module did

---------- Post added at 11:30 AM ---------- Previous post was at 11:20 AM ----------

P.s

Can someone confirm about the custom search working on swiftkey 7.2.2.32,not working for me
[Xposed Framework Modules] Roughy:
Working in stable, broken in beta. Guess it's time for some maintenance.

Button tint is possible, but I'm going to play the feature-bloat card.
[Xposed Framework Modules] Uraniam9:
Oh my bad :), OK got it dude