yashsingh1/xdaforums huggingface dataset:
[Xposed Framework Modules] YK RAJ:
[MENTION=2675647]elesbb[/MENTION],it can correct by grammatically sentence ? Like Ginger keyboard on Ps

https://play.google.com/store/apps/details?id=com.gingersoftware.android.keyboard
[Xposed Framework Modules] elesbb:
It just tells whichever keyboard you are using to allow auto correct in whatever field you are currently typing in. Some fields have auto correct removed from them. This module adds it back. It is NOT a keyboard.
[Xposed Framework Modules] wrongway213:
Works perfectly on Lollipop. If this existed as a standalone app I'd pay good money for it, can hardly type when Xposed not enabled for one reason or another lol
[Xposed Framework Modules] elesbb:
You would have to modify the keyboard apk. I don't have xposed on lollipop yet for Samsung. So that is what i did for myself lol. Sadly this will always require either root or an xposed module. I could possibly make it stand alone.. I may look into that actually. Thanks for the idea. It will still require root though. PS: Even if its not a standalone app, you can always donate so I can get a coffee :)
[Xposed Framework Modules] wrongway213:
Oh man, if you did this I would be the happiest man on earth - always rooted. I like to run custom ROMs that often do not play nice with Xposed, and your module is the one Xposed module I can't live without - had some issues with motor skills when I was a little child that I got over with therapy when I was too young to remember thankfully, but still have very sloppy handwriting and I'm not proficient with tiny things like my phone keyboard.. I would stop running Xposed on ROMs that aren't meant for it if this was a standalone apk, that's for sure - I install Xposed only to run this now and never really face issues because this isn't a mod that messes with UI stuff or even can, but still when Xposed is not working, etc. it's a pain, and sometimes simply having Xposed installed can cause issues on a certain ROM + kernel combo. I really think this feature should be an option in all phones for clumsy people like me. P.S. very aware of donation in your profile, not sure if you're aware your in-module donation link is broken. Anyway, thanks for the awesome work - will be quite curious to see if you really make this a standalone app or keep it as a module, ether way I'm using it lol.
[Xposed Framework Modules] Goliath27:
Can anyone tell me if their instagram text field is still there? Specifically when you're uploading an image and you're writing a caption? Mine is missing on my google keyboard
[Xposed Framework Modules] wrongway213:
Anyone tried this on the alpha for 5.1 yet with any success? Wondering if it needs updating to work with 5.1 or if it's not compatible with theme or something, don't remember needing to update even from KK to LP so seems odd it would from 5.0 to 5.1.. anyone else tried yet?
[Xposed Framework Modules] elesbb:
I thought xposed didn't work on 5.1? Anyhow, it shouldn't need an update. I hook the keyboard service and tell it to enable auto correct. So if your old keyboards are still working, then the module should work too. Happy Easter everyone!
[Xposed Framework Modules] wrongway213:
I wouldn't think it would as it did not need an update on KK - but apparently this is not so. I confirmed with a user on stock rooted to make sure it's not an incompatible CM theme commit or something, Always Correct! causes keyboard FCs on 5.1 framework as of right now. Some other modules are working, many are not. http://xdaforums.com/showpost.php?p=59917145&postcount=106
[Xposed Framework Modules] elesbb:
Can you possibly provide a logcat? It might be something to do with xposed since there isn't a stable version yet. Especially since the guy said "its one of the few that does" for the other tinted module. My guess its something with xposed.

But anyhow, the logcat will definitely drill down the exact issue. I'm 99% confident it's not the module. I can't see them changing the keyboard code for 5.1. That would mean every developer out there would have to update their keyboards for 5.1. But it wouldn't be the first time an Android update broke something so necessary lol. So when you get a chance, grab that logcat. Btw a full logcat, not filtered. Thanks!
[Xposed Framework Modules] wrongway213:
Oh, I plan to. I would have gotten one last night but I was in an extended series of bootloops - I got intermittently booted for a few moments long enough to catch Fatal Errors coming from Youtube AdAway - bizzare because that module is confirmed working. The FCs are also so persistent that in order to catch them, I'd have to disable FC notifications in dev options - would that be a probem for logs? To give you an idea, I'll have to disable FCs, then load the module - I genuinely can't even use my phone to get into menus with your module installed for whatever reason. I've only narrowed down it was your module (other than obviously guessing it off the bat due to this being a keyboard module and the FCs being AOSP keyboard) was that uninstalling your module stopped the FCs. I still was going in and out of bootloops and getting Fatal Errors from YouTube AdAway after uninstalling your module, but it fixed keyboard FCs. Let me know whatever is pertinent to disabling FCs and taking logs. Also, to be clear, you want just a verbose logcat and a verbose Xposed log? Appreciate all the help.
[Xposed Framework Modules] elesbb:
A verbose logcat will included xposed log so just a verbose logcat will be great. Also, you can use ADB to get the logcat ;) So not being able to use the device shouldn't be an issue. I usually wait to see the force close, then grab the logcat using adb to ensure the crash was written to the logcat.
[Xposed Framework Modules] wrongway213:
OK, I'll have to stop being a noob for a minute and learn to get logs via ADB instead of just using Catlog :p and get back to you after I try the framework again
[Xposed Framework Modules] elesbb:
adb logcat -d > /some/directory/and/file/name.txt

:)

Very simple. :)

Thanks dood.
[Xposed Framework Modules] gitchrodd:
Could it be a stock kernel thing? Was going to try and get myself a log cat just for trying to figure out how to do a log cat.... So i reactivated module turned on aosp keyboard rebooted and its working now? No F.C's

Running Temesek V10 for 5.1L rom

hydra kernel v2.0

Always correct v1.0.2
[Xposed Framework Modules] wrongway213:
I'm not sure.. I do not have the framework even installed as I have not had time to do logs and all the things a super alpha needs, and since this module was confirmed not working I have not found it important enough to make time. Did you happen to use the Make ~99% of modules work fix, or just do everything normally? Also, I would really appreciate it if you could please submit this to the Xposed 5.1 module thread, as it would help narrow things down I am sure. Link attached: http://xdaforums.com/xposed/modules/discussion-xposed-modules-5-1-lolipop-t3075257 Thanks for looking into the issue - my personal life has been pretty insane lately and so I have had no time for a super alpha, but I would be a very happy man to have this module back in my life.
[Xposed Framework Modules] gitchrodd:
Done posted in other forum...

i have not tried the 99% fix. just did all normal
[Xposed Framework Modules] beardymarrow:
Always Correct working fine for me on Temasek 12.1 for i9300. Worked fine from first install, then had a crash of my phone and then SwiftKey and AOSP keyboard started FCing afterwards. Uninstalled Always Correct and reinstall and rebooted and now working again fine.
[Xposed Framework Modules] elesbb:
Just an fyi I can't debug or do any patches for lollipop. I need to wait till xposed comes to Samsung. I may even port it myself.
[Xposed Framework Modules] dyurdz:
hi. is there a way to enable/disable the "ignore passwords field" through tasker?
[Xposed Framework Modules] maxpayne4:
Not working for me using note 3 sm n900 on cm 12.1. 1.0.2. Tried rebooting several times, used aosp, swift and Google keyboards. Still nothing.
[Xposed Framework Modules] only1hammy:
Just confirming that this works for me. OPO with COS12.1 and stock AOSP keyboard.

I actually don't use autocorrect, but this module restores suggestions in Chrome, Play Store, et all. Perfect.
[Xposed Framework Modules] marco2012:
Confirmed working on OnePlus One running Android 6.0.1 Marshmallow.

Sent from my OnePlus One.
[Xposed Framework Modules] Ricardo_Is:
Working on Samsung Galaxy S4 Note 5 Port by [MENTION=5403589]Albe95[/MENTION]

When I try to make a search using Google in web browser, auto-correct don't work.

Sent from Samsung Galaxy S4 GT-I9505 - Note 5 Port Astra v2 - Xposed Framework v75
[Xposed Framework Modules] SCrid2000:
Thanks for the app, would love it if the app would let you exclude email fields as well.
[Xposed Framework Modules] Raijin:
[MENTION=2675647]elesbb[/MENTION] Is it possible for you to add a button in the blacklist to select and deselect all? Or a change on the behavior of the app, making it work with a white list instead (Always Correct disabled by default).

I think it's better this way, because some apps give problems when using Always Correct.

Also, a setting to exclude e-mail fields, like SCrid2000 said, would be nice.

I think these are relatively easy things that can improve a lot the module. Thank you.
[Xposed Framework Modules] wrongway213:
I have had this thought myself about Gmail... would definitely be convient to blacklist certain fields and things instead of whole apps and I imagine that may not be a lot more work as a blacklist is already working - but a whitelist sounds a bit backwards given the point of this module. I am definitely echoing the sentiment as a daily user of this module that blacklisting gmail password fields and Chomrium URL fields in particular would be super useful, though. Allowing for a toggle (accessible thru QS maybe - since all apps can now do that with Custom QS app) could be a very cool way to achieve that disabling you wanted in a whitelist that sounds a bit less contrary to the purpose of this module.
[Xposed Framework Modules] elesbb:
The reason I haven't thought of any specific "whitelist", which yea seems redundant, is because my keyboard has the option to turn off autocorrect at will. I assumed all keyboards had this, guess not.

What is "QS" though?

I could make like pressing the space bar three times turn off the auto correct, or something along those lines. I some how managed to be a douche and delete my source code. But reverse engineering it shouldn't be too hard. But will just take some time. Lets collaborate some more ideas of toggling it then when I get time I shall work on it. But like I said, my keyboard has the option to, while typing, turn off the auto correct. Maybe I could implement something like that for all keyboards.
[Xposed Framework Modules] wrongway213:
Awesome, thanks dude! QS is quick settings tiles.
[Xposed Framework Modules] fijasko:
This module should have more visibility.

I came upon it accidentally in some Google group discussion, after looking for a solution for a long time.

Thanks, [MENTION=2675647]elesbb[/MENTION], fantastic job.
[Xposed Framework Modules] elesbb:
I finally had time to update this. Let me know if you have any issues, but first read the OP. I have some information in there about it not working on OEM keyboards. Thanks all.
[Xposed Framework Modules] twistednl:
Yes, same issue here on my HTC one m8
[Xposed Framework Modules] wrongway213:
1.3 does not produce any functionality for me - I was able to install via XDA labs and module loads up, has ignore password field option available. Whether enabled or disabled, no notification when typing anywhere. Reverted to 1.2 and all works as normal. Let me know what kind of logs or info you could use and I'll get them for you after work. 1.2 still working flawlessly for me and I like blacklist so I'll likely stay on 1.2 - just wanna help you get 1.3 working as I love your work. Let me know if I can be of assistance.

You guys can get around this by downloading through XDA Labs instead of Xposed installer.
[Xposed Framework Modules] elesbb:
I had to rename the package. I'm guessing something didn't get renamed somewhere. I have homework so once that's finished I'll take a look.
[Xposed Framework Modules] ssrij:
Doesn't work for me. I'm on 1.0.3 and using Google Keyboard on my S7 edge running 6.0.1
[Xposed Framework Modules] Snah:
Sideloading 1.03 still shows the upgrade notification in Xposed. Du to that the app has a new name?

Discovered one error in 1.03 which made me switch back to 1.02. In Swiftkey, there's a setting for one automatic capital letter after a period. With 1.03 it doesn't work. I'm on a LG G4, running MM 20D.

[Written by my thumbs on a state-of-the-art Nokia 3110.]
[Xposed Framework Modules] elesbb:
Okay guys. Re-download if you previously downloaded it. I keep forgetting Android Studio uses gradle, so I had to change the package name in there and in the xposed_init file too. So if you check your xposed log, you probably see that it says "file doesn't exist" for my module.

You should also be able to install via xposed module now.

Just re-download and it should work. You may need to fully uninstall previous version. Actually, you MUST uninstall old version. Also, ensure module is enabled inside xposed installer app. I have no idea how many times I kept rebooting wondering why my logs weren't showing up in adb :)
[Xposed Framework Modules] adomm420:
1.0.3 file not found:

1.0.2 installing as it should:
[Xposed Framework Modules] elesbb:
Click the "reload" button at the top right.
[Xposed Framework Modules] Realz4747:
Version 1.0.2 is working, but 1.0.3 isn't (I've already uninstalled previous version)

Device: Moto G 2014 stock 6.0
[Xposed Framework Modules] elesbb:
Did you reinstall since today? Meaning, when did you download the app? If it was before today, download again.

Are you using your stock keyboard? Can you please tell me what kind of logs are generated in xposed installer app?

I can't help you if you don't help yourself.
[Xposed Framework Modules] Realz4747:
Yes, I reinstalled today. I had downloaded yesterday, but I redownloaded today.

I'm using Google Keyboard (the stock of Moto G). I can't tell you the logs because I've installed version 1.0.2 again :p

Sorry my bad english :)
[Xposed Framework Modules] elesbb:
Well I can't do anything without logs or debug info. So you need to get me some logs or something to have me help you. If version 1.0.2 is working, I wouldn't see why 1.0.3 isn't, unless there is something wrong with the xposed package again.

Can anyone else confirm 1.0.3 working or not?
[Xposed Framework Modules] fijasko:
Not working for me.

I can download 1.0.3 (yesterday I couldn't) and install it, but only if I uninstall 1.0.2 first.

The name of the module is changed and is now XposedAutoCorrect (it used to be Always Correct!).

No suggestion bar pops up, even when I toggle it on and off.

I'm using the latest Google Keyboard on stock Sony 5.1.1 LP.

1.0.2 worked without a glitch.

I mistakenly cleard the log, so it's now empty. I don't have the time now to uninstall/install again, but if no one else posts a log, I will do it tomorrow.
[Xposed Framework Modules] fjdifede:
It is not working forma me reverted back to 1.2 and works perfect
[Xposed Framework Modules] alichiddy:
Well, I stuffed up this app trying to install the latest version using XInstaller to disable "Checking Signature" so it restarted the phone while installing the latest version, now I can't "fully" uninstall the old version (everytime I uninstall the old version and try to install the new one it says there's an app with the same name but different signature already installed) to install the new one with XInstaller disabled, so I can't confirm if the new version works, sorry
[Xposed Framework Modules] elesbb:
I need logs if anyone wants help. I literally completely uninstalled it, rebooted, reinstalled, enabled, rebooted, and it works for me.. I can't fix it if it works perfectly for me, simply stating its not working doesn't help me one bit.

Try using a root explorer to completely remove the apk. otherwise, try installing the old one and then use settings to uninstall it.
[Xposed Framework Modules] alichiddy:
Thanks a lot

I uninstalled the old version using "SD Maid" app and was able to install the new version, and it works in the password field in a Bank app I use, thanks a lot.

There's a new "System UI" gets fc on a restart but I'm not sure if it will go away by time, and even if it doesn't, I feel the mobile boots quicker this way, so even better from my beside [emoji4]
[Xposed Framework Modules] fijasko:
This is after I couldn't install over 1.0.2, uninstalled 1.0.2 completely, rebooted, installed 1.03, enabled it and rebooted.
[Xposed Framework Modules] pirasalbe:
Can't make ignore password fields works

If you need it I can send you a log
[Xposed Framework Modules] elesbb:
Thank you for the log. Nothing is in it though, signifying everything should be hooked properly and everything was found. A little later, I will release a version to this thread that has extreme debug logs in it. I will append them to a file so you can just share the file that will end up on your SD card.

Does it not work globally or for a single app? Is it working fine for you otherwise?

For those who its not working for, just to organize my thoughts, it is working perfectly fine for you when using 1.0.2? Cause I literally copied the code xD
[Xposed Framework Modules] pirasalbe:
Always correct is working, I have suggestions for every app and I see the notification and the previous version was working perfectly.

I've tried with PayPal and Instagram and in both applications I have suggestions in password fields
[Xposed Framework Modules] alichiddy:
System UI started to close more often so reverted back to the old one for the time being, love the old version, the only reason I updated was because I didn't want to see the green text in Xposed notifying me that I have an update for a specific module
[Xposed Framework Modules] elesbb:
You're right. It's not working. I probably made a stupid error, that's what happens when you rush ?

This has nothing to do with system ui, so I have no idea why it would cause force closes. Unless it's my notification option. I used notification builder but that shouldn't affect any devices on kitkat and above.
[Xposed Framework Modules] pirasalbe:
Thanks, waiting for a fix [emoji23]
[Xposed Framework Modules] alichiddy:
No wonder, I'm on Jellybean 4.3 [emoji4]
[Xposed Framework Modules] elesbb:
YOu should be fine then. Its API 11 and up that is supported. I just couldn't remember off the top of my head what the last version was that was supported. I really don't know why it is force closing. Could you get me a log cat? It only happens with v1.0.3 installed and NOT 1.0.2?
[Xposed Framework Modules] alichiddy:
Yes, it only happens with 1.03, I'm fine with v.1.02, I guess it has something to do with other modules interfering your latest version, cause I have other problems with other modules that I couldn't find what the culprit was so I'm not using those modules.

After the first reboot Logs:

https://drive.google.com/file/d/0B-G7bKnjWgwXUmlydVRJbFpzWTA/view?usp=drivesdk

After the 2nd Reboot Logs:

https://drive.google.com/file/d/0B-G7bKnjWgwXZEFuekdDWFBwX1k/view?usp=drivesdk
[Xposed Framework Modules] Realz4747:
Won't you fix it?
[Xposed Framework Modules] plazzmex:
Hey.. Amazing module.. Can we disable the notification somehow?

Thanks
[Xposed Framework Modules] elesbb:
So I fixed passwords not being ignored when checked. I forgot to switch the package names lol.

Yeah, I already said I would, once I have the time to do it.

Sure, I will create an option to disable it. As of now, you cannot though.
[Xposed Framework Modules] Realz4747:
I've installed SwiftKey and I've noticed that it's working, but it's not working with Google Keyboard, I don't know why. I can use SwiftKey with no problem, but it would be great if you fixed it :)
[8125, K-JAM, P4300, MDA Vario General] Tall_Man:
Hi all,

I got an unlocked T-Mobile MDA VARIO from the states, which is working fine in my country (UAE), but I can't find an arabic rom for it.

I tried the arabic rom for the imate k-jam, but I came to know it's a different rom which can not be installed on my phone.

I tried the imaginet arabizer, but it's not a rom, it's just an application which eats up the memory, and wipes out if the device is hard-resetted.

I contacted T-Mobile, but they said that they don't have an arabic rom!

What to do?

(I'm an I.T. guy)
[8125, K-JAM, P4300, MDA Vario General] GerooTech:
the solution is to coock your own extended rom
[8125, K-JAM, P4300, MDA Vario General] Tall_Man:
Thanks,

but :

1) how will I link the arabizer into the coocked rom?

2) I don't know how to cook a rom, but I used to cook them a few years back when I had my qtek 1010 !

Thanks again
[8125, K-JAM, P4300, MDA Vario General] GerooTech:
1 ) you will extract the arabizer cab files from the imate kjam extended rom and try to mixthem with your tmobile extended rom.

2) this link may help in how to coock.

http://xdaforums.com/viewtopic.php?t=56088&highlight=
[8125, K-JAM, P4300, MDA Vario General] Tall_Man:
that's very risky & dangerous.

I'd prefer to do it with someone who tried it earlier.

You know, my pda could be ruined.

Thanks for your help.
[8125, K-JAM, P4300, MDA Vario General] nadp:
hala 7ajji,

ana ga3ed asta5dem barnamaj y3arrib iltelephone, ana 3ndi CINGULAR 8125, madri etha nfs iltmobile illi 3ndk, bs ana illi ast5dma 3adi, agdar aktb 3rbi, asolef 3l msn bl3arabi, agra 3arabi, no problems.

ism ilbarnamaj في جيبي عين tgdar it79la 3l montadayat il3arabya

(to every1 else in the forum, this is arab-ish =P a new net language =D)
[8125, K-JAM, P4300, MDA Vario General] Tall_Man:
mashkoor ya ameer,

bus aby ism al barnamij biddabt law sama7t, aw kallimny .

050-6454332
[Verizon Samsung Galaxy Note II] cmraymond:
Well, it wasn't Kitkat , still on 4.3, but maybe there's hope!! Anyone else get it?
[Verizon Samsung Galaxy Note II] wuestsider:
I also recieved the update (ND3), but still on 4.3. I can't find anything stating what the update actually is.

WUESTSIDER X!

Sent from my Mighty Galaxy Note 2
[Verizon Samsung Galaxy Note II] jpatt:
Damn it that Knox crap. What's the point, I am stock. I can't even flash a Mod. Because I am root they knife me in the back.

Tell me there's no way back except ODIN back.
[Verizon Samsung Galaxy Note II] nbock01:
Added ability to roam on telus network. Got it last night. Also freaking patches the kernel so the saferoot method no longer works :(
[Verizon Samsung Galaxy Note II] swdude987:
Good I rooted and installed another rom before this update!!
[Verizon Samsung Galaxy Note II] z71kris:
New radio?
[Verizon Samsung Galaxy Note II] PuffJr2:
it's probably just a way for them to try and lock the phone back down before the 4.4 release.
[Verizon Samsung Galaxy Note II] monkeyass408:
http://www.sammobile.com/firmwares/3/?download=29193

looks like 4.4.2 is released to those nordic countries for the n7105. the people on the att note2 forums are playing with it. Hoping for a port if everything goes well for them.
[Verizon Samsung Galaxy Note II] TonikJDK:
This update its very telling. A simple roaming fix that also kills root. Looking like my last samsung phone and maybe the end of VZ for me.
[Verizon Samsung Galaxy Note II] mattymo:
There's a pdf you can view before you download the update. it lists an update for Galaxy Gear, improvements for wifi, maps, voicemail notifications, bunch of other crap. comes with amazon appstore preloaded. im not rooted so i guess i'll go ahead and download it lol.
[Verizon Samsung Galaxy Note II] PuffJr2:
theyve been killing root with every update. id be more surprised if they allowed root to stay.
[Verizon Samsung Galaxy Note II] thebat1:
not going to take it

I keep getting bugged to do the OTA..

I don't want it...

I guess I need to start a new thread and find out how to stop the OTA if I am not rooted.

So the numbers did not change? I am on 4.3 now...