yashsingh1/xdaforums huggingface dataset:
[Xposed Framework Modules] oroboros74:
Not sure if others are having the same problem, but when I finger type there's a greater lag every since this latest update (not as much if I'm flow typing). It's as if it's taking longer for key presses to register. Any help or suggestions would heartedly be appreciated! Thanks

Edit : I just saw i have 7.3.2.19 of the app. I guess the mods aren't backward compatible and that's why I have this issue?
[Xposed Framework Modules] Tchania:
All working well here after the update.

Thanks [MENTION=6797900]Roughy[/MENTION]
[Xposed Framework Modules] Roughy:
This has been discussed a number of times in the past.

The short answer is that it would be possible for me to do this myself, but it would be a rather significant undertaking.

In the meanwhile, there are solutions such as Tai-Chi ( Linked in the top post ) that allow you to patch xposed /into/ an app, allowing you to utilize the module without installing xposed on your system.

Tai-Chi does, unfortunately, have a few problems:

A: It only works on some devices and versions of android

B: It whitelists specific versions of this module, meaning you have to use an older version of this module and swiftkey, and that I can't attempt to find workarounds for any of the Tai-Chi specific issues that exist.

But hey, I used it in Nougat at some point and it ran fine, albeit painfully slow.

Nothing has changed in the hooks that should impact performance.

Feels the same to me.

The update aside, Xposed hooks probably do have some performance impact, though pretty much every time I've suspected the module was causing something, the performance issues would persist with the module removed.

If you can document a specific difference in performance with and without the module I'll look into it though. ... Not that I have any idea how to profile it short of just.. commenting stuff out until it runs faster.
[Xposed Framework Modules] Roughy:
There haven't been any breaking changes, so the module should be compatible all the way back to 7.2.6.28 at the moment.

7.3.2.19 is definitely fine.
[Xposed Framework Modules] oroboros74:
Odd. The lag was so bad (with finger typing) I had to downgrade to the previous Exi. It doesn't change a thing in my end, but just thought I'd report it. Thanks!
[Xposed Framework Modules] oroboros74:
Does SwiftKey backup just the user profile or also the app settings on the device? Because of it doesn't this might be something to add to the requested feature list.
[Xposed Framework Modules] JerryGoyal:
so the back key swipe is not working which is used to select words towards left.
[Xposed Framework Modules] Roughy:
I honestly have no idea what Swiftkey backs up. I've never used it.

Swipe from delete?

Does the swipe-from-**** function work?

Are you sure it is disabled in config app?

Failing that, what layout, language, and other non-default options are you using?

Also, what version of Swiftkey and the Exi module are you using?

Anything in the xposed logs?
[Xposed Framework Modules] JerryGoyal:
this is strange but i think swipe to delete issue is from swiftkey keyboard side. i was using the latest beta version but then i installed the stable version and disabled the exi module restarted the phone and set the option in swiftkey setting to swipe to delete but still it's not deleting the word. don't know how can it be possible. though swipe down to close keyboard is working fine. i know u can't help much in this.
[Xposed Framework Modules] oroboros74:
It seems like SwiftKey backs up the user account only. Per device settings are not backed up.

Would it be possible for Exi to include a backup function of the app settings? Just an idea. Would be useful rather than having to set everything up manually.
[Xposed Framework Modules] BaschtlWaschtl:
So like titanium backup? ?
[Xposed Framework Modules] Tchania:
To anyone nervous to update SwiftKey, the module is working well with version 7.3.4.17.
[Xposed Framework Modules] Roughy:
Almost! Emoji panel now has issues.

You will likely be greeted with a completely empty emoji panel.

After returning to the keyboard, you should be greeted with the stock emoji panels the next time you open the emoji panel.

I had to do do some nasty things to get the support library android components working inside Swiftkey to begin with, and this appears to be a resource problem related to that.

Swiftkey probably migrated from appcompat to androidx or something.

If that's the case it probably can't be fixed without breaking backwards compatibility. Wish they would break both stable and beta at the same time when they do things like this.

Fffffffffffuuuu

Edit: Looks like its only a single resource. Fixed, will push update in the morning.

2019-07-05 03:42:12.770 17427-17427/? E/Xposed: android.content.res.Resources$NotFoundException: Resource ID #0x7f120217
at android.content.res.ResourcesImpl.getValue(ResourcesImpl.java:190)
at android.content.res.Resources.getColorStateList(Resources.java:992)
at android.content.Context.getColorStateList(Context.java:542)
at android.support.v7.content.res.AppCompatResources.getColorStateList(AppCompatResources.java:65)
at android.support.v7.widget.TintTypedArray.getColorStateList(TintTypedArray.java:171)
at android.support.v7.widget.AppCompatBackgroundHelper.loadFromAttributes(AppCompatBackgroundHelper.java:60)
at android.support.v7.widget.AppCompatTextView.<init>(AppCompatTextView.java:78)
at android.support.v7.widget.AppCompatTextView.<init>(AppCompatTextView.java:71)
at android.support.v7.widget.AppCompatTextView.<init>(AppCompatTextView.java:67)
at com.mayulive.swiftkeyexi.EmojiCache.NormalEmojiItem.<init>(NormalEmojiItem.java:26)
at com.mayulive.swiftkeyexi.main.emoji.EmojiPanelPagerAdapter$3.onTabAdded(EmojiPanelPagerAdapter.java:210)
at com.mayulive.swiftkeyexi.util.view.FixedTabLayout.addTab(FixedTabLayout.java:172)
at com.mayulive.swiftkeyexi.main.emoji.EmojiPanelTabLayout.addTab(EmojiPanelTabLayout.java:72)
at android.support.design.widget.TabLayout.addTab(TabLayout.java:465)
at android.support.design.widget.TabLayout.populateFromPagerAdapter(TabLayout.java:910)
at android.support.design.widget.TabLayout.setPagerAdapter(TabLayout.java:901)
at android.support.design.widget.TabLayout.setupWithViewPager(TabLayout.java:814)
at android.support.design.widget.TabLayout.setupWithViewPager(TabLayout.java:775)
at android.support.design.widget.TabLayout.setupWithViewPager(TabLayout.java:753)
[Xposed Framework Modules] Tchania:
You are right.

My bad, I only checked the swipe to move curser and slide space bar up for shortcuts, as they are the most used features by me. Didn't check emojies but just did and it was empty in the first try as you described.
[Xposed Framework Modules] Roughy:
Exi for Swiftkey 2.3.2 release

2.3.2 [06.07.2019 ] - Compatibility ( 7.3.2.19 Beta: 7.3.4.17 )

Changes in 2.3.2

Fixed

- Compatibility targeting 7.3.4.17 ( Emoji panel )

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=7420144]Tchania[/MENTION]

Resources! What are they?

In Android apps, resources such as strings, pixel dimensions, colors, and images are bundled alongside the code that will run the app.

Each resource is assigned an ID: A number the code can use to access the resource.

You basically ask the system for the resource represented by the given ID, taking into account the language, size, and type of the device.

AppCompat! What is it?

AppCompat is a library of features that exist on newer versions of android, that have been ported to older versions of android.

Usually, the android device itself will provide a lot of the ... code? necessary to run an app, but when the stuff available on the device is too old to support certain features, we use the AppCompat support library instead.

The problem here is that the AppCompat components ship with a number of resources that will not be available on the device. This is fine if you're just using them in your own app, as they will be bundled in, but we're running them inside of Swiftkey where they are not available. I have several hooks in place to deal with this, and none of Exi's own components utilize the resource system at all.

However, I can only really track down these problems when they occur. Up until now Swiftkey has either been using AppCompat themselves, or just happened to ship with compatible resources that were assigned IDs that matched what we were looking for.

Today it was looking for a list of background tint colors for image views. A resource with the corresponding ID does appear to exist, but it is apparently of the wrong type, and Android throws a fit.

The solution is to hook the android.support.v7.content.res.AppCompatResources.getColorStateList() method that attempts to look up this resource, and return an empty list instead.

Since the class in question ships with Exi, rather than belonging to Swiftkey or Android itself, we can hook it without worrying about causing problems elsewhere in Swiftkey.

With any luck this will be the end of it, but we may run into similar problems in the future. It's a ticking time-bomb, but at least the solution is fairly simple.
[Xposed Framework Modules] iamMG:
[MENTION=6797900]Roughy[/MENTION] please implement this.

Edit: Nevermind, accomplished what I wanted using Popups tab.
[Xposed Framework Modules] kos25k:
hello dev.i asked this feature some months ago...is it possible to add punctuations while voice recording but also voice recording dont stop when we press symbols?it is very annoying to have to stop voice recording,then choose the symbol and then re-enter the voice recording to continue our message.
[Xposed Framework Modules] Roughy:
It is certainly possible. Probably.

Changing the text while it is kinda-inputting-kinda-editing might upset it, but that could certainly be worked around.

Unfortunately, as with most feature requests that require me to do more than make some quick tweaks though, I probably won't be adding this (or any of the other things asked for ) anytime soon.

I have to eat and stuff, and just doing compatibility updates on existing features occasionally ends up taking up quite a bit of time.

Sorry.

You can add it to the github as an issue/feature request though, so that at least it won't be forgotten, and I may give it a go when I have more time on my hands.
[Xposed Framework Modules] Alexey71:
After rebooting 5 out of 10, the clathure does not work, you have to forcibly kill the SwiftKey process. Who had it?. I not see error xposed logs...
[Xposed Framework Modules] Roughy:
I don't know what "clathure" is.

You logs seem to indicate that the Swiftkey hooking process is starting and finishing several times in a very short timespan. This would normally indicate that Swiftkey is crashing immediately, but you mentioned that you have to force kill it, which suggests otherwise.

It is normal for Swiftkey to freeze for a while after updating the module or Swiftkey, but this should be a one-time thing. Logs indicate that it finishes loading in about 2 seconds, so that shouldn't be the cause.

Most likely Swiftkey itself is crashing, and then immediately restarting again. I am probably going to need LOGCAT output to track down the issue.

If you are using EdXposed, there was an issue a while back where garbage collection occurring during the hooking process would cause Swiftkey to randomly crash multiple times like this.

If you are using EdXposed, you should be able to resolve the problem by updating to a newer version of it.
[Xposed Framework Modules] Alexey71:
EdXposed does not work well with your module. During the day, the module stops working :(. I would love to use edXposed...

Therefore, I use https://xdaforums.com/xposed/unofficial-systemless-xposed-t3388268

Logcat View attachment LogCat.zip
[Xposed Framework Modules] alex_long:
Thaks. I have found it in Swiftkey options but I never use it and I was really surpised to see it in this keyboard. I used Swipe keyboard long before and swipe technology is a key feature of Swipe keyboard. It's funny Swiftkey uses it as Flow technology.

Anyway thank you. Now it's clear.

By the way do you mind to add a localized Exi version? I could offer you a good Russian translation.

---------- Post added at 09:04 PM ---------- Previous post was at 08:23 PM ----------

Pardon me — Swype + Dragon keyboard
[Xposed Framework Modules] Roughy:
Exi 1.0.3 Release

Update - V 1.0.3 - Compatibility update

Change log:

Fixed

- Compatibility targeting Beta 6.6.7.28

Download:

Exi for Swiftkey on the Xposed Module Repository

Notes:

Nothing new in terms of features, just fixing stuff that broke with the latest beta version.

The module should still work fine with older (Which at this point in time means the stable branch) versions of Swiftkey.

Thanks for the offer. Localization really is something I need to get around to doing.
[Xposed Framework Modules] bkkzak:
Unfortunately, since upgrading Exi module and SwiftKey, most features aren't working (I was using Exi 1.0.2 and the mainstream SwiftKey that was working at the time of that modules release):

-swipe on spacebar

-swipe from delete/shift buttons

-hold control button (123) for copy/paste /etc

Working:

-more predictions
[Xposed Framework Modules] _labello:
Very nice work.

I hope you can add the abilitty to make the keyboard bigger than the orignal values\sizes

When I edit my phone dpi to 290\300 everything looks good , but the keyboard looks small
[Xposed Framework Modules] Roughy:
What specific version of Swiftkey?

1.0.3 necessitated a rework of key definitions, and if that breaks ... anything that needs to know what key you're pressing will break too.

Having said that, I have 6.6.7.28 and 6.6.6.21 working fine on my end. If you are using >=6.6.6.21 then we have a problem.

Swiftkey/Exi Version, language, android version, logcat filtered by tag "Exi/" should help in figuring out what's going on.

There is also the potential that the class search caching system is causing problems, in which case you may want to try deleting EXI_CLASS_CACHE_com.touchtype.swiftkey.json from the swiftkey/files directory.

It shouldn't be causing any trouble, but it's one of the few things that might differ between users.
[Xposed Framework Modules] bkkzak:
Swiftkey/Exi Version -6.6.21/1.0.3, language-english, android version-7.1, logcat filtered by tag "Exi/"- I downgraded back to 6.6.5.31/1.0.2 because of the problems..

I have one of my busiest weeks of the semester this week so I couldn't help troubleshoot until next weekend at the soonest. Sorry.

I just wanted to throw this out there so it's on your radar. Heck, it could be because I'm using the unofficial Xposed, but I haven't had any problems with other modules or that much with the previous versions of Exi (only problems were force closes when I was swiping fast). Sorry again that I can't be more help. Love the work you do
[Xposed Framework Modules] Roughy:
I'm hoping this is the cause.

Last I tried the Unofficial Xposed Frameworks just fail to hook things sometimes, without providing any errors or warnings.

Sometimes restarting the app would get one hook working, only for another to fail. Completely random.

I'll gladly track down any problems on <=Marshmallow, but in my experience the unofficial frameworks are far too unstable to even consider supporting.

Thanks for the heads up though.
[Xposed Framework Modules] el_easy:
The last time I used your app ''Flow'' wasn't working and for me is the main feature of Swiftkey and I uninstalled it. Did you fix it already? Thanks
[Xposed Framework Modules] alex_long:
Hi and thanks for this module.

I've already made the Russian version of it. After I test it on my device I will share it (strings.xml with Russian translation)

By the way don't you think there is some mistake in app strings?

You:

<string name="settings_name">Settings</string>

<string name="settings_title">Sensitivity</string>

I think it should be:

<string name="settings_name">Settings</string>

<string name="settings_title">Settings</string>

i.e when you press Settings you should see <— Settings but not <— Sensitivity in the upper left corner.

Anyway in my Russian translation version I substituted it for Settings so it looks like above Settintgs-Settings but in Russian.
[Xposed Framework Modules] Roughy:
I have had no reports of flow not working.

If you have swipe selection set to swipe-anywhere you will not be able to flow (see docs in second post).

If you wish to have flow and swipe selection at the same time, you need to use one of the other swipe-selection modes (hold and swipe, swipe on spacebar etc)

Yuuuuuuuuup. I am evidently reusing the same string resource in two locations ("Sensitivity" in the Swipe tab used to be named "Settings"). Hadn't noticed that. Will sort it out in the next release.
[Xposed Framework Modules] alex_long:
Please make it more clear (highlighted):

Suggestion shortcuts: If enabled, shortcuts will trigger on the primary suggestion, instead of only on verbatim input

It's important for me to make the correct and easy to understand russian translation.

Thanks.
[Xposed Framework Modules] Roughy:
A shortcut is essentially a word to word mapping, so "hello" might map to "peanuts"

Verbatim means literally, as-written. In other words, you have to type in "hello" perfectly for the shortcut to be inserted. This is also how Swiftkey's clipboard shortcuts work.

This obviously means that the shortcut will not be inserted if you instead type "hellp", as "hellp" does not equal "hello"

However, swiftkey will likely provide the correct spelling "hello" as the primary suggestion, and with trigger-on-primary-suggestion enabled, we will use this as a trigger to insert the shortcuts.
[Xposed Framework Modules] alex_long:
Fine. I did not know how to insert images here so I will try to explain how I do it step by step

I use the latest English version of Exi for Swiftkey, 1.0.3

The Swiftey version is 6.6.6.21 MOD from www.4pda.ru

I do not think there will be a big difference between official and MOD versions.

So...

In Shotcuts section I create a shortcut hallo with the text peanuts

Now I make Suggestion shortcuts on in Settings (have it checked) and try to type hallo. I see the words: hallo - peanuts - Halloween and Swiftey highlights peanuts. If I press Space key I have "peanuts" typed in (inserted).

Now I make Suggestion shortcuts off in Settings (have it unchecked) and try to type hallo. I see the same words hallo - peanuts - Halloween and Swiftey highlights peanuts. If I press Space key I have "peanuts" typed in (inserted), as above.

I can not see any difference between Suggestion shortcuts on and off (checked and unchecked). Am I doing anything wrong? Maybe I did not understand the meaning of Suggestion shortcuts on/off (checked/unchecked)?

---------- Post added at 02:42 PM ---------- Previous post was at 02:18 PM ----------

Hi again

There are strings in values —> strings.xml

(this is for Settings section)

<string name="category_pref_emoji_panel">Emoji Panel</string>

<string name="category_pref_flow_suggestions">Flow & Suggestions</string>

<string name="category_pref_misc">Misc</string>

I can easily translate it into Russain because the strings are present.

In Exi for Swiftkey Settings I can find another categories as KEYS and APP but I could not find any string for it.

Is is logical to have some more strings?

<string name="category_pref_keys">Keys</string> and <string name="category_pref_app">App</string>

I may be wrong because I am not a programmer.
[Xposed Framework Modules] Roughy:
I create the following shortcut:

Shortcut: hello Text: peanuts

Suggestion Shortcuts: DISABLED

I type in hellp.

Since I input hellp instead of hello, peanuts is not inserted

Swiftkey correctly predicts that this is a typo of hello, and offers hello as the primary prediction.

Suggestion Shortcuts: ENABLED

I type in hellp, which swiftkey will attempt to auto-correct to hello

The module will detect that this prediction matches the shortcut trigger hello, and peanuts is inserted
[Xposed Framework Modules] Roughy:
Welp, looks like I forgot to move some text to string resources.

They are not present there because they are still hardcoded in xml/preferences.xml

<PreferenceCategory
android:title="Keys">

<PreferenceCategory
android:title="App">

Bad me.
[Xposed Framework Modules] godlesplay:
[MENTION=6797900]Roughy[/MENTION] Polish translations here, I didn't translate first 4 strings because I don't know that I should, if yes then tell me so I will update them. And I'm not using this module, so if I translated something incorrectly than correct me
[Xposed Framework Modules] alex_long:
I translated it into Russian and so far I do not find any problem on my device. But let's wait the author's resume.
[Xposed Framework Modules] K0media:
[MENTION=6797900]Roughy[/MENTION], don't forget about this:
[Xposed Framework Modules] alex_long:
I will share here my Russian strings.xml tonight.

---------- Post added at 03:44 PM ---------- Previous post was at 03:34 PM ----------

Thanks, now it's clear with this item.
[Xposed Framework Modules] alex_long:
Hi.

1. There should be <string name="category_pref_keys">Keys</string> in Settings section. That's OK. Please pay attention that it's impossible to translate the phase Define Key because I can not find a proper string.

[IMG="Define Key preview"]https://img.xda-cdn.com/pWBUD4IoQ4hyRfm9JryFtTxare0=/http%3A%2F%2Fi.imgur.com%2FrSQeIvR.png[/IMG]

You may forgot to add it to strings.xml?

2. Please find attached my Russian strings.xml

View attachment strings.zip

I am ready to make chages in case I find some better translation variants or in case of your changes and adding some new into the module. Anyway my current translation is checked by myself dozens of times in search of the perfect word match and word meaning.

Sometimes I appied more descriptive phrases in "summaries" to make people understand the meaning without referring to Detailed Instructions

N.B.

I have downloaded the Polish translation just to have a look and it seems to be not full IMHO. godlesplay, could you please check it?
[Xposed Framework Modules] Roughy:
Your logcat does not contain any information or events related to the module

07-15 21:35:44.152 1552 8447 I ActivityManager: Start proc 9099:com.mayulive.swiftkeyexi/u0a227 for content provider com.mayulive.swiftkeyexi/.providers.SharedPreferencesProvider

07-15 21:35:44.242 9099 9111 I Exi/ProviderSecurity: Allowing com.touchtype.swiftkey:10066

The content provider ( Hook uses this to read module settings from the config app ) is accessed at some point, but unlike your earlier xposed log none of the output expected during the initialization process is present.

If the above log covers the Swiftkey process being launched, then your xposed variant simply isn't doing its job.
[Xposed Framework Modules] Alexey71:
I try EdXposed again, module dead again. And errors do not appear, the keyboard works without a module. After a reboot, some time normally works again ...
[Xposed Framework Modules] Primokorn:
Just to say that your module works better with YAHFA instead of SandHook.

Several features din't work fine with SandHook (already reported months ago) but everything works out of box with YAHFA.