yashsingh1/xdaforums huggingface dataset:
[Xposed Framework Modules] n0j0e:
mhh, perfect if it can tweaked with Exi! :laugh:
[Xposed Framework Modules] danbest82:
SwiftKey 7.5.3.4 seems to work with latest Exi. Will report back if I find discrepancies.
[Xposed Framework Modules] n0j0e:
i get a weird "icon_IMEGoKey" if i try to delete a suggestion from suggestion bar with a long touch.

SwiftKey 7.5.2.7

Exi 2.6.8
[Xposed Framework Modules] Gruber008:
Same thing here, it displays that text but it removes the suggestion, so just a small bug I guess.
[Xposed Framework Modules] rolear8:
[MENTION=6797900]Roughy[/MENTION] please provide your PayPal address to buy you a vegan juice
[Xposed Framework Modules] Tchania:
It's on the main page/post (towards the bottom).
[Xposed Framework Modules] Roughy:
Exi accepts intents to control the theme, incognito, and vibrations.

You can use these intents with something like Tasker or Automate to enable/disable them when any given app is open/closed.

See this release post for more info: https://xdaforums.com/showpost.php?p=78892109&postcount=796
[Xposed Framework Modules] guillermorojaz:
Hi [MENTION=6797900]Roughy[/MENTION]

Small request for a next update.

- Add direct access to native clipboard in Space Up-Swipe Mode :cool:

- Add more editing options or the option remove completely from the top bar of the keyboard ;)
[Xposed Framework Modules] Ice Bear:
Ice Bear would like to make a request. Ice Bear would like the ability to change the font size of the predictions. Changing the keyboard size also changes the font size depending if one makes it bigger or smaller but Ice Bear would like a smaller predictions font size on a bigger SwiftKey size.
[Xposed Framework Modules] patrickneil:
Prediction size is controlled by the theme, and it is something you can edit. The themes are written in JSON and live in data/data/com.touchtype.swiftkey/files on the system partition. If you create a custom theme, then replace it with the files from a downloaded one you like, you can change a lot of the appearance in the style.json file. The predictions (which SwiftKey calls "candidates") can be made smaller by increasing the padding around them. One easy trick is also to change "should_brand" to false to get rid of the SwiftKey logo on the space bar.

This brings me to a question I've wondered about, whether Exi should look into theming at all. Certainly what first got me into SwiftKey were DJDarkKnight96 and his library of custom themes.
[Xposed Framework Modules] Ice Bear:
Ah, Ice Bear had no idea. Ice Bear gives his thanks for helping him discover this useful trick.
[Xposed Framework Modules] Redn2000:
Is it possible to backup the clipboard with Exi's Backup and Restore function? And if not, I'd like to make this a feature request since SwiftKey themselves don't seem to have any intention.
[Xposed Framework Modules] pratyush28:
The spacebar functions are regularly breaking for me. I need to force stop swiftkey to make them work again. Anyone else have the same issue?

Using canary edxposed 5.0.0 Yahfa (same issue on sadhook)

latest exi and swiftkey beta

Edit : Not just spacebar functions but all swipe gestures randomly stop working :eek:
[Xposed Framework Modules] dedq:
Guys, how can me open the file containing suggestions to edit manually maybe deleting some?
[Xposed Framework Modules] whitehollow:
I would like to change the comma key with the ? Key. Is it possible ?
[Xposed Framework Modules] XtraWater:
The last update on SwiftKey and beta version broke the space bar functions. Like, swipe up for copy, paste....
[Xposed Framework Modules] n0j0e:
SwiftKey 7.5.4.4 + Exi 2.6.9 = no problems. Space up menu works and all things which i'm using.
[Xposed Framework Modules] XtraWater:
Interesting. I rebooted the phone. It didn't help. Something else I can do?
[Xposed Framework Modules] pratyush28:
Try reinstalling swiftkey this used to happen to me earlier.
[Xposed Framework Modules] n0j0e:
me too, reinstall SwiftKey.
[Xposed Framework Modules] :
[MENTION=6797900]Roughy[/MENTION] the latest SwiftKey Beta uses an updated emoji set finally adding most of the ones you had trouble finding before.

Maybe a good idea to use that set as a basis again? It includes stuff like skin tones and new variants that emoji version 12.0 added.
[Xposed Framework Modules] Roughy:
Exi for Swiftkey 2.7.0 release

2.7.0 [15.05.2020 ] - Compatibility ( Stable: 7.5.4.4 Beta: 7.5.5.15 )

Changes in 2.7.0

Fixed

- Compatibility targeting 7.5.5.15 ( keys, quick menu, shortcuts

- Long preferences getting cut off in some languages

The Xposed Installer app does not appear to be refreshing properly and may not list the latest version.

Please download it directly from the Xposed Repository below using a browser.

Download:

Exi for Swiftkey on Xposed module repository

My own mirror of all versions

Notes:

Compatibility [MENTION=9076664]XtraWater[/MENTION]

Methods were removed and moved around. Affected us getting a reference to the root view of the keyboard ( keys, quick menu ), and inserting shortcuts. Quick fix once you figure out what's broken.

[MENTION=8536001]alex_long[/MENTION] also pointed out that one of the Russian translations in the settings was cut off. Turns out Android's stock checkbox preferences have a max number of lines, and require some magic to override it. Why are the Russian translations so long you ask? Because I never update the documentation and alex_long's description provide a much better explanation of how features work ¯\_(ツ)_/¯。

I also added that period.
[Xposed Framework Modules] Tchania:
Big thank you
[Xposed Framework Modules] Yoannjap:
Thanks a lot for your fixing!

Also, keyboard shortcut with space bar don't work in Firefox Preview / Firefox Preview Nightly and Firefox Focus.

I hope there's a way it can work.

Thanks whatever
[Xposed Framework Modules] Roughy:
7.5.5.17! It's only been a day since 7.5.5.15! What did you break!?

We currently include all the Emoji listed in 13.0 of the standard, so there isn't really much point in downgrading to their older list.

Now that I know what to do it's a lot easier to pull the data directly from the official source rather than digging through Swiftkey's sources to find theirs, not to mention they are most certainly always going to be super out of date in the future too.

Unfortunately this is a bug on Firefox's end that seems to affect all their textboxes ( in actual sites, rest of the interface is fine ).

In the past they've broken swipe selection too.

Copy seems to work, but paste is a bit wonky. Sometimes adds the text, sometimes replaces it.

Select-all does not work at all.

Exi calls performContextMenuAction() on the InputConnection to perform most of these actions here.

Since it current is responding to selection changes correctly I could perform the same action by messing with the cursor positions, but this is really a Firefox bug that Mozilla should be fixing on their end.

I use Firefox myself and am somewhat miffed by this so I /might/ do a workaround, but the issue really should be reported to Mozilla instead.
[Xposed Framework Modules] :
Okay that's great I didn't realise you managed to implement it that way. ?

In that case could you look into the missing skin tones and variants in the Exi Panels? Because quite a few of the gesture (like ??) and people (like???) Emoji are limited to the default yellow tint.

In 12.x and definitely from 13.0 onwards those (and a few more) should support a whole range of choices.
[Xposed Framework Modules] flexoduss:
Thank you so much :) for doing this!!!

This made my day :D!!!
[Xposed Framework Modules] grotesque02:
Just ask!

Is possible with this module change the "real time" microsoft translator with google translator?

Thanks!
[Xposed Framework Modules] m8980:
Hello,

I'm using Samsung Galaxy S20 Ultra and tried Exi for Switkey 2.6.9 and 2.7.0 with xpatch, Taichi and VirtualExposed but no luck. Doesn't work for me.

Swiftkey Versions I've tried:

Beta: 7.5.5.17

Stable: 7.5.4.4

Any ideas?

Thanks
[Xposed Framework Modules] Tchania:
With beta 7.5.6.3 seems to be working fine.
[Xposed Framework Modules] oroboros74:
DeepL Translator would also be nice (better at conversational translations I find). But Google would also be nice!

Ugh! Just auto updated to the new Microsoft for SwiftKey! Darn it!
[Xposed Framework Modules] oroboros74:
That's odd. Exi wasn't working with the new version till after I rebooted. Dunno if something broke but I see some functionality.

..
[Xposed Framework Modules] n0j0e:
Yeah, DeepL is the best translation service!
[Xposed Framework Modules] pratyush28:
Guyz if anyone is having a problem like this one please use the inbuilt backup and restore feature of exi! I have been switching multiple roms lately and I always restored exi using either TiBU or Migrate app.

Today I clean installed exi and restored the features using the import zip file option and now everything works perfectly. 2 days have passed and swipe actions haven't broken even once. Earlier It used to break every 10-20 mins and had to force stop swiftkey to make it work again.
[Xposed Framework Modules] mario0318:
Hello world. I can confirm the latest Microsoft SwiftKey 7.5.5.19 seems to work with Exi 2.7.0.

But I'll give it a bit longer and a couple more reboots to check for potential wonk.
[Xposed Framework Modules] oroboros74:
It comes and goes for me, in the sense that erratically things stop to work (swiping on space bar to move cursor or for the quick actions), then later it's fine... something that I never had to deal with before.
[Xposed Framework Modules] mario0318:
Yes. After a few hours of regular use and rebooting the device, I'm experiencing a similar situation with Exi seemingly stopping to function though it's still active and running and no force close errors have popped up.

But it did seem to at least fix the issue with the previous SwiftKey version where it would Force close randomly but usually after gesture swiping several sentences in a single session, sorta like I'm doing right now.
[Xposed Framework Modules] pratyush28:
Everything works perfectly for me on swiftkey version 7.5.5.19 been 2 days and no problems so far. Try reinstalling exi and use the inbuilt restore function to restore data this fixed my swipe gesture problem which I had earlier.
[Xposed Framework Modules] bocaum:
All working in version 7.5.6.3

thanks ;)
[Xposed Framework Modules] Roughy:
Possible, but complicated and would probably required paying for the service.

Probably won't be doing that anytime soon, but you can chuck it on the github issues tracker.

Force-close as in ANR ( freeze ) is normal crashes?

In either case I wouldn't mind the logcat output to see if it's something the module is doing or if Swiftkey screwed something up.

I don't think there has been many ( any ? ) other users experiencing crashes though. Granted, just because they're not being reported doesn't meant they're not happening.

There are a few potential causes of swipe-selection/the quick menu coming and going, alas it's somewhat difficult to track down the exact cause.

Swiftkey will recreate the keyboard and keyboard layouts a lot.

In some situations we only keep track of the last couple of objects created, discarding the oldest instances as Swiftkey creates new ones.

This has causes problems in the past where we didn't keep track of enough keyboard key objects, which might be what's happening again here.

After reading the code though, we are apparently keeping a separate list for each layout type, storing the last 1000 keys created there, so that... really shouldn't be the case.

If you are experiencing crashes then something more sinister might be going on, so logcat of anything interesting would be appreciated.

Serious problems causing hooks to deactive themselves should also be logged to xposed log.
[Xposed Framework Modules] Yoannjap:
Hello,

Thanks again for your great work on this module.

Would it be possible to add the symbol sign like @, €, &, #, etc. to set text shortcut.

As far as I tried, only numbers and letters work.

Thanks whatsoever,

Yoannjap
[Xposed Framework Modules] mario0318:
I'll try to get a logcat as soon as the next keyboard crash happens. But I might as well mention that I've been tinkering with the phone quite a bit in my long search for the best optimal kernel parameters and other memory related settings that may be the true cause for the keyboard crashing out of nowhere. It was pretty stable at one point not too long ago so I don't think it's your mod. With that said, the issue really began to crop up more after the Microsoft redesign for Swiftkey and the crashing seems to happen when my device is visibly struggling to keep up with gesture typing with several hungry apps running in the back, and then occasionally it does a three second freeze followed by a crash, and sometimes without the FC dialog. It takes about 15 to 20 seconds after that crash for the keyboard to pop up when tapping on a text input field. Many times it seems to happen within certain apps only when gesture typing for too long in a single session makes these crashes kick in at least once, possibly because it's keeping track of a lot of words to keep in memory for undo/redo, but that's only a guess....it was only a guess. It was only a guess.

What I'm wondering, as an experiment, is if there's a way to adjust the oom value for the keyboard app and maybe the mod as well in case the crashing is instigated by it and spilling into the keyboard process, so that they can be prioritized high enough for Android's LMK to not consider killing the keyboard in out of memory events.
[Xposed Framework Modules] Tchania:
Seems to be working fine with beta 7.5.7.3
[Xposed Framework Modules] Preformerr:
[MENTION=6797900]Roughy[/MENTION] I have four suggestions, I think they would perfect this app which is a piece of art and I'm very thankful that you made it! I'm physically disabled and this app helps me a lot in typing :D

One: Selective Autocorrect. IMHO autocorrect gets in the way more often than not and you have to proofread your messages and see that you won't accidentally embarrass yourself. What if instead of expanding everything, it only expands some specific to letters into whole words? Basically an advanced version of the shortcuts we already have. So I can add individual words, for example - expand nmste to namaste, etc. One good side effect this feature will have is that it will be transliteration on steroids - for the people who type in more than one language it'll speed up their typing a lot. There is also an opposite way this feature can be implemented - in addition to selectively enabling autocorrect, we can also selectively disable autocorrect! So the people who use autocorrect primarily can identify common mistakes and add them as exceptions.

Two: Better Voice Typing. I just checked out GBoard yesterday and it has a really cool voice typing; mostly because it doesn't have the google mic pop-up. We can have some other nifty things to speed up voice typing like when you say "cross" (word should be customizable), it would delete the last spoken word instead of typing cross. Voice shortcuts, isn't that cool?

Three: Add customizable key pop-ups to the symbols page too. I use this feature quite a lot, and I noticed that it doesn't work if you try it on the individual keys in the two pages (first after clicking 123, second of {&=). Would really appreciate this.

Four: Like we have hot-keys or the pull-up pie menu (from space bar) to execute some much needed actions like Start, End, New Line, I would like to suggest you to please add the shortcut of "Next Field" also! Usually when we're filling up forms it automatically gives you that action, but sometimes it doesn't so it would be very nice to have it in the pie menu.

Thank you very much!
[Xposed Framework Modules] Roughy:
That is indeed strange. We partially rely on Swiftkey's prediction mechanism, and they must completely ignore special characters like that.

It may be an easy fix, but if a special character results in Swiftkey not generating any of its usual prediction events then it... might not be.

One:

We already have mechanism in place for selectively promoting the literal prediction candidate ( i.e exactly-what-the-user-wrote ) to the primary slot. This is used for the "no auto-correct after swiping" option.

Simplest implementation would be adding an option that does this for all predictions other than the ones inserted by us. You lose Swiftkey's best-guess-based-on-sloppy-input functionality, but it seems like that is what you would want.

tl;dr add option that disables auto-correct for anything but the shortcuts added by Exi.

Two:

Messing with voice typing is not very straight forward; improving it would require reimplementing it from a scratch which I am not particularly keen on doing. Ditto for voice commands. All possible, but not something I intend to do.

Three:

Looks like the keys generating in those layouts are not being parsed correctly. Even if we're not adding any popups to a key we still need to keep track of whether or not they have existing popups for swipe-selection to function correctly ( do not trigger if popup with multiple options has been triggered ), but that is apparently failing for the symbols layouts.

Will have a look and fix if feasible.

Four:

Will look into it and add if feasible.
[Xposed Framework Modules] Preformerr:
Can you please make the voice input into a separate key like we have an option for an emoji key?

Remembered one more thing; can you please give us an easy way to move the shortcut placements in the key pop-ups?
[Xposed Framework Modules] Tchania:
Seems to be working fine with beta 7.5.8.5.

What I tested:

-Space bar shortcuts working.

-Emojies showing.

-Number row swipe to move cursor works.

-Shift+swipe to select working.
[Xposed Framework Modules] Roughy:
Don't really intend to anything but fix bugs; new features will mostly be limited to stuff that's very easy implement.

A voice input key is unfortunately not very straight forward, but you can add an issue on the repo and I may remember it at some point.

Popup key configuration is the way it is out of necessity. Exactly where Swiftkey will display a popup will depend on the specific layout, so nothing we can really predict.

What we can do is decide which one will be in the center ( the slot that's raised during configuration ). The rest are inserted in the slot you specify, counting from the left.

There should be a more in-depth explanation in the second post of this thread.
[Xposed Framework Modules] Black Platypus:
Shortcuts ignore uppercase of first letter

Hi!

It seems like no matter what I do, I can't seem to get shortcuts to respect the casing of the first letter.

They always turn out lowercase.

Can that be addressed, please?

Not having to tap the shift key is one of the main reasons one might want to use shortcuts in the first place.

(a checkbox "force case" might be nice if you want to preserve default behavior)
[Xposed Framework Modules] pratyush28:
Yes this is very annoying indeed which is why I have been using a workaround for this. I'm using an invisible character just before my shortcut content so that I can deceive swiftkey into thinking that the first letter has been made lowercase.

What you need to do in order to use this is, copy the invisible character from method 1 in this link http://emptycharacter.com/

and paste it before all of your shortcuts that start with an uppercase letter and hit done. (You won't see anything being pasted as it is invisible and doesn't event take space on the text field)

Hope this workaround helps until [MENTION=6797900]Roughy[/MENTION] can implement a fix for this.
[Xposed Framework Modules] Black Platypus:
Ha! Neato, sly idea!

I just hope that this doesn't cause any weird behavior anywhere (a site/service might flag a message as spam when non-printable non-control chars are found because of a possible obfuscation attempt?) - might also keep a phrase from being found if the char is not stripped ("my search Phrase" not found. All we have here is "my search [0-width invisible char]Phrase" - and you didn't ask for that, sir ^^)

Thank you for your tip, and may the great creator hear our request :)
[Xposed Framework Modules] pratyush28:
Oh yes you're right it wont work everywhere. I only used shortcuts on social media apps so didn't think of using it this way.
[Xposed Framework Modules] Devildire:
On SwiftKey 7.5.7.4 most features don't work for me. Only thing that's working is hotkeys. Did already reinstall both SwiftKey and exi. Any clue why most features won't work?

Edit: I am using exi 2.70 on Android 10
[Xposed Framework Modules] Preformerr:
Nothing is working for me out of sudden, I even went from Taichi to EdXposed to see if that was the problem to no avail.

Edit: Working again, using a different Custom ROM with EdeXposed.
[Xposed Framework Modules] pratyush28:
I have a feeling that ART optimization which occurs after overnight charging is somehow breaking swipe gestures. I had charged my device overnight for 2 days in the past week and both the times swipe gestures were broken in the morning.

People having issues with broken exi features can you try going into edxposed manager >> top left menu >> applications >> search for SwiftKey keyboard (Not Exi) >> Tap and select De-optimize and check if the features start working for you.
[Xposed Framework Modules] Preformerr:
[MENTION=6797900]Roughy[/MENTION] Can you add the Tab key? Can help while coding or typing in excel. Also, would it be possible to have a single separate key for arrow keys? I feel that enabling the arrow keys from the main app settings takes too much unnecessary space; maybe it can be just one key and we can get our required arrow after swiping on it through key pop-ups (at the four directions).
[Xposed Framework Modules] Tchania:
Seems to be working fine with beta 7.5.9.2.

Tested what I use daily:

-Space bar shortcuts, working.

-Emojies, showing.

-Number row swipe to move cursor, working.

-Shift+swipe to select, working.
[Xposed Framework Modules] oroboros74:
Same with me. I was hoping today's update would have fixed it with targeting the newer v.6.6.8.33, but it didn't.

I'm wondering if there's not a way for Exi to disable itself when it isn't compatible with the targeting Swiftkey version, rather than manually having to disable it from Xposed and reboot. (?)
[Xposed Framework Modules] Roughy:
As soon as I identify an issue in the beta branch, I roll out a fix so that anyone using stable won't run into trouble by the time it hits the same version.

The hooks disable themselves if they run into trouble, but if something they do causes a problem outside of the method they are hooking, it will have no idea what caused it.

I am fairly meticulous about testing compatibility before releasing, and haven't encountered any issues on my end.

I also haven't received any reports about crashes before this (Unless I missed a post), so I'm hoping the problem isn't too wide spread.

If you feel like ruling out my worst fear, you could try deleting EXI_CLASS_CAHCE_*packaname*.json in Swiftkey's data/files folder, then rebooting.

It's possible that the class-cacher isn't ditching old results properly, resulting in the module trying to hook the wrong classes.

Would explain why only some users are affected, and why I haven't encountered it on my end, since I'm likely to reset it manually a few times while testing.