yashsingh1/xdaforums huggingface dataset:
[Xposed Framework Modules] WicCaesar:
In the Settings I've configured it to perform a MORE command, I don't know if it's supposed to be invisible but it never performs anything and it doesn't give me any keys either. When I try to input my own commands (COMPLEX or MORE), many times it does not recognise and the hack result is always imperfect.
[Xposed Framework Modules] _firewall_:
MORE command is invisible. You shouldn't see it, but module will do it.

Reboot is required after module installation.

Please take a look at attached screenshot and check all settings once again.

[IMG="Required settings for module"]http://rghost.ru/7QW8bfvCJ/image.png[/IMG]
[Xposed Framework Modules] Genericxx:
Xglyph doesn't work for me anymore after updated to latest android release r24 and latest ingress version 1.97.1. Tried different approaches to resolve my issue (clean flash, multiple times deactivate+reactivate module and multiple times deactivate and reactivate in-app-function, ofc both with device reboot) but nothing helps. logcat and xposed log doesn't tell anything related to xposed or xglyph, so i'm a little bit out of ideas. Because [MENTION=6407867]_firewall_[/MENTION] said that it works for him, i guess it's either related to the new android codebase in r24, or related to the rom i'm using (Resurrection Remix for OnePlus One).
[Xposed Framework Modules] _firewall_:
I'm still on Android 4.4.4. It's currently satisfying all my requirements and its battery time is the best on my Nexus 7 2013.

Seems, that your issue is related with work of some Xposed modules under newest OS version.
[Xposed Framework Modules] Genericxx:
I'm using Android Marshmallow since December last year and being satisfied so far with it. Strange thing is, that even with the latest Xposed (v81) Xglyph worked until yesterday. After i've updated to latest version (monthly security update) it stopped working. Maybe [MENTION=4960233]Cypher_01[/MENTION] can look into it and release an updated version.
[Xposed Framework Modules] Genericxx:
Have to revert my last Information. It's not dependant on latest Android 6.01_r24 nor Xposed v81. It just was the ROM i've used. Seems like Resurrection Remix fooked too much up because of their optimisations. With Omni Based ROM everything works as intended.
[Xposed Framework Modules] xfunforx:
[MENTION=4960233]Cypher_01[/MENTION]

hi, your account add to the admins at xposed.info. you can update the ingressXglyph.

http://repo.xposed.info/module/com.xingress.xglyph
[Xposed Framework Modules] srinagar:
ran into same issue like [MENTION=5369313]Genericxx[/MENTION]

Did some testing - looks like it's related to any newer release of Cyanogenmod or CM-based ROMs. CM13 March release works fine, any newer version (as of April 2016) seem to cause issues with xglyhp. Rolled back to CM13 30.3.2016, working fine now. Not related to ROM (Oneplus Two, inofficial CM13, tested Grarak and Seraph version - same issue). Going forward I guess the APK needs an update.
[Xposed Framework Modules] Wayd:
i run under CM 13 - stock kernel (latest version) with my G3 and N7 2013 .. without any serious reason (one at a time, it is necessary to restart the glyph)
[Xposed Framework Modules] Cypher_01:
Great! Thanks! :) I will upload future versions to the Xposed repository.

Quick status update:

SIMPLE/COMPLEX glyphs aren't working yet. I'm very busy atm, but I'll do what I can. Stay tuned.
[Xposed Framework Modules] Genericxx:
Anyone tried if the new xposed v82 fixes the issues with xglyph on cm13 based roms?
[Xposed Framework Modules] Wayd:
CM13 + v82 (N7 2013 & G3 855) no problem
[Xposed Framework Modules] namandistro:
This is a great piece of module... I just hope that there should be a function to put commands like more keyz and etc...
[Xposed Framework Modules] Bence98007:
Is there any new update about simple/complex glyphs?
[Xposed Framework Modules] Genericxx:
Nope
[Xposed Framework Modules] euphemismus:
Hi all. I can confirm xglyph(12.01) not working with op2 cm13 unofficial (04-27 build), xposed 80,81 and 83. xposed itself works with others modules. Tried a lot of version combinations now. Log shows no errors.

Anyone else having the same Problem?
[Xposed Framework Modules] Genericxx:
I'm currently using an unofficial cm13 also and can confirm that the latest version of xglyph is working with xposed v83. It turned out that custom unofficial cm13 builds with huge optimizations to art, ramdisk or other stuff are fooking up xposed. Usually the devs of those roms warn their users of installing xposed. Personally i can confirm that xposed/xglyph won't work on Resurrection Remix, at least on OPO. If you rely on xposed or desire to run xglyph, simply switch to official cm nightlies, as they should probably work.
[Xposed Framework Modules] pki101:
Anyone tested latest official cm13 signed version to Oneplus One?
[Xposed Framework Modules] rgawenda:
It does work with CyanogenOS13, xposed v83, v12.1 of the module.
[Xposed Framework Modules] Aghartay:
Please update...

Manual input key\no key does't not override settings...
[Xposed Framework Modules] _firewall_:
Xglyph settings should override key/no key commands in game. And it works like a charm.

If you want to enter them manually, then just turn off these options in module settings.
[Xposed Framework Modules] euphemismus:
I can confirm: Switched to latest OxygenOs 3, although it has some downsides. But at least now xglyph is working again (and by the way: GREAT).
[Xposed Framework Modules] sirivanhoe:
Hi guys

Anyone has it working with Samsung Galaxy S7 edge?, I can't make it work, I've tried toggling everything toggable in Xposed and directly on Xglyph, restarting after disabling, restarting after enabling, I've tried launchin it with samsung's game launcher enabled and disabled.. just it doesn't work... also even if the checkbox for log is ticked, no log is written into Xposed.

Funny thing, I have also a Galaxy S6 edge and everything works perfectly there, including the latest v1.99.1 :eek:

I'm running:

Xposed framework version 83.0 (custom build by wanam 20160423)

Xglyph v12

SuperSU Free v2.71

TWRP 3.0.2-0

Could you please advice me what to do/check/change? :fingers-crossed:

Thanks!

---------- Post added at 05:28 PM ---------- Previous post was at 05:02 PM ----------

I apologize, I've realised what was the mistake.

I was running v12, while v12.1 was the latest

Link to latest version (click the small 'play' button to go directly to Cypher_01 's post):
[Xposed Framework Modules] _firewall_:
I have tested with Ingress v1.100.0 too.

Works like a charm.

COMPLEX command works correctly.
[Xposed Framework Modules] Cypher_01:
Xglyph v12.2

Hi@all,

strange, that nobody complained about the imperfect glyph not working, even I didn't notice til now. v10 worked with the imperfect glyph, but since v11, I accidently removed the code taking care of this.

I've fixed the bug, I simply re-added the old code. But I couldn't test it, because I didn't get a glyph sequence including the imperfect glyph. Please tell me, if it works for you.

You can find the new version at the Xposed repository. I will also upload future versions to the repo, which makes updating more comfortable.

As always, the source code is on GitHub.

I didn't have time to take care about COMPLEX/SIMPLE glyphs so far.

Have fun and play fair! ;)
[Xposed Framework Modules] xfunforx:
report bug:D

keytool -printcert -file META-INF/CERT.RSA

Cypher_01:

所有者: CN=Android Debug, O=Android, C=US

发布者: CN=Android Debug, O=Android, C=US

序列号: 6a51ace5

有效期开始日期: Sat Mar 19 20:04:22 CST 2016, 截止日期: Mon Mar 12 20:04:22 CST 2046

xfunforx:

所有者: CN=yi, OU=v, O=v, L=v, ST=v, C=123456

发布者: CN=yi, OU=v, O=v, L=v, ST=v, C=123456

序列号: 2fa2950e

有效期开始日期: Thu Jul 16 21:31:30 CST 2015, 截止日期: Mon Jul 09 21:31:30 CST 2040

need sign the apk with my .jks file.:D:D:D

xposed can't no see the new update.
[Xposed Framework Modules] Cypher_01:
Oh, I didn't think about that. So that means, my access to the repository is no use anyway? :p
[Xposed Framework Modules] xfunforx:
xposed cannot find the last update. you can resign the apk used my jks file.

i had sent jks file to you.
[Xposed Framework Modules] shubhamkulkarni02:
How to use COMPLEX command.

MORE is working.

What about complex?
[Xposed Framework Modules] Cypher_01:
SIMPLE/COMPLEX glyphs aren't implemented yet. For more information: Post 186 and Post 190
[Xposed Framework Modules] Bqsnotoponi:
Guys i am with JellyBean OS and i cant start the app... i am opening it, starting ingress, going to glyph and...nothing ...an you help me a lil bit?
[Xposed Framework Modules] shubhamkulkarni02:
Ohk..

Thanks for the reply..

Can u tell when will complex gonna available?
[Xposed Framework Modules] Cypher_01:
I've been working on it, but I didn't have time recently. I still can't give an ETA.

Meanwhile I suggest to deactivate command glyph key hack, if you want to use the SIMPLE/COMPLEX command glyphs. It could interfere with it.

Stay tuned.
[Xposed Framework Modules] shubhamkulkarni02:
Cypher_01 thank you..... I'll... But Plz try to update as soon as possible.

I'm trying to devwlop app by using ur source from github but I know java programming very little. So it's as good as not possible.
[Xposed Framework Modules] Cypher_01:
Xglyph v13

Hi@all,

COMPLEX/SIMPLE glyphs are finally here! :) I finally found the right spot in the Ingress source code. ;)

There are a few things you need to know:

First, the code, that's hooked additionally now, is part of the obfuscated classes of the Ingress client. That means, that the automatic COMPLEX/SIMPLE input most probably won't work for new versions of Ingress. I did my best to design the code as compatible as possible. The worst thing that could happen is, that automatic COMPLEX/SIMPLE glyphs don't work anymore after an update. But it doesn't cause crashes and manual input of command glyphs always works. I may only need to update Xglyph for every new version of Ingress.

Second, a short tutorial:

You have to touch the command glyph interface, otherwise the glyph speed hooking won't be triggered.

As with the MORE/LESS glyphs, it's also for the COMPLEX/SIMPLE glyphs possible to override the configuration by drawing a correct COMPLEX/SIMPLE glyph.

Key and speed overriding are also combinable.

If you don't touch the command glyph interface, the glyph speed is at normal, independent of your configuration.

That also means, that if you want to override just the key hack config, it will always trigger the glyph speed. I couldn't avoid that.

I now also signed the APK, so that you can update it via Xposed Installer. If you have problems updating from a former (unsigned) version, simply uninstall it, reboot, install the new version, activate it in the Xposed Installer and reboot again.

Have fun and play fair! :)
[Xposed Framework Modules] _firewall_:
I've just tested it. Works like a charm with Ingress v1.100.0 :good:
[Xposed Framework Modules] namandistro:
Loved it... Its working fine in CM 12.1 (Android 5.1)
[Xposed Framework Modules] RedFungi:
New features

Hello there!

Is it possible to add two features?

Auto tapping and holding "Hack" button (to start glyph hack)

Auto tapping on screen to pass glyph

If it's possible, can you add this?

Thanks for this soft! :)
[Xposed Framework Modules] Cypher_01:
I already thought about this myself, but this is even more cheaty than the module already is. At least I won't add these features.

But the module is open source. Every developer can play around with it and add/change things.

I repeat it again. I suggest, the best way to use Xglyph is as I do. I do my best to draw the glyphs correct. Xglyph only saves me in case of a mistake.
[Xposed Framework Modules] _firewall_:
You're right. Niantic may ban user for such "features". They shouldn't be implemented into the module.
[Xposed Framework Modules] Genericxx:
If Users want total automatisation they should get their self one of the bots available and pay for it
[Xposed Framework Modules] pki101:
Found this from facebook

"Agents,

This week we enabled a new component of our anti-cheat system - specifically focused on agents trying to falsify their location and automate gameplay. We consider any technical mechanism that does these things to be cheating, including applications that inject false locations or techniques to maintain a stale location. This new component resulted in the termination of accounts that showed clear signs of cheating and we have verified these results are highly accurate.

Our goal is to provide a fair, fun and legitimate game experience for everyone. We will continue to work with all of you to improve the quality of the gameplay, including ongoing optimization and fine tuning of our anti-cheat system. If you believe your account has been terminated incorrectly, you should report it to the Ingress Help Center.

Thank you for your understanding and continued support, Agents.

JH"
[Xposed Framework Modules] selemine:
so this means tuning of server-side checks they already have,so what? Mock locations was already checked, modified apks get you banned today and the server checks if you are travelling too fast. This module auto corrects your glyphs so there should be enough timing variation.
[Xposed Framework Modules] nick_stokes:
need update for new version...
[Xposed Framework Modules] _firewall_:
Module works correctly with latest Ingress v1.101.2.

Update is not required.
[Xposed Framework Modules] _firewall_:
What version of module you are currently using?

Xglyph v13 works like a charm with latest version of Ingress.
[Xposed Framework Modules] sebzanga:
Awesome Mod, I'm going to give a try once I reach home....

I was trying to figure it out how it works.... But got stuck in the part that the glyphSequence got parsed into a float.... The method "g" is external right?

Sorry, i'm a c# developer :(
[Xposed Framework Modules] halliba:
So based on the latest comments I assume the mod does not trigger the 'new' anti cheat systems?

What about a setting that only a random but high percentage of glyph are getting corrected? No one can glyph for month without a fault[emoji14]
[Xposed Framework Modules] tanparin:
Great tool!

Using this for quite some time now - I agree that it should sometime on a non-L8 Portal do a faulty glyph so it appears to be legit!

Keep up the good work!
[Xposed Framework Modules] Genericxx:
There are reports in our community that people have been hit by the ban hammer for using auto glyph mods. Ingress checks for root and xposed and submits a flag for each, regardless of mods like xglyph being installed. General rule: If you don't want get banned, simply don't use this, as chances are always given that you will get caught.
[Xposed Framework Modules] Cypher_01:
Risk for getting banned

Hi@all,

some thoughts about the risk of getting banned.

First of all, you're only on the safe side if you don't use Xglyph. But there is more to think about.

Lately I realized, that the Ingress client calls Androids API method 'getInstalledApplications'. That is for sure part of the new anti cheat system. But I'm not sure what they're looking for. I don't think, that it is particularly Xglyph, and if, doesn't matter, the module hides itself by hooking also this method. I think Niantic checks for the Xposed Installer, as Genericxx already mentioned (the Xposed Framework itself cannot be detected by an app). But, apart from Xglyph, does it matter? No, it doesn't. Using Xposed isn't against the TOS, neither is root. Anyway I'll also add hiding the Xposed Installer.

Root can only be detected by an app by requesting root access, which leads to a SuperSU popup dialog. The Ingress client doesn't do this, and if, you could deny the request, an app cannot distinguish between a deny or an unrooted rom.

There are more possibilities for detecting hooked code, e.g. analyzing the stack trace of a method, which can be done by an app. But I don't believe, that the Ingress client is doing this, because the code is obfuscated automatically. It would be way too much afford to adjust the stack trace analysis for every code change during development. Anyway, we cannot be sure.

We already had the idea of random false glyphs. I don't think, that this would help. It's legit, you cannot get banned just for being a perfect glypher. But you have to play the glyph game reasonable! If you tap the screen very quickly just to get a high speed bonus, your behaviour can be analized, because it's not possible to draw five correct glyphs in half a second. Let's see, maybe I'll add this feature, although I think it won't make a difference.

I personally stopped using Xglyph for a few weeks now, because I don't need it anymore. I won't give it up, it was always fun to improve it. But it's your choice, if you want to take the risk. I still think, it's pretty low.

Have fun and play fair! :)
[Xposed Framework Modules] _firewall_:
[MENTION=4960233]Cypher_01[/MENTION] told me that:

"the package already hides itself from the Ingress client. This is based on xfunforx's module HideX. It filters the package name from Android's getInstalledApplications and getInstalledPackages methods. I didn't find such method calls in the Ingress source code anyway, but you can never be sure."

So, this module could not be the reason of people's ban.

I have too many friends with Xposed, root devices and Ingress installed. Non of them were banned.

But one of your thoughts is correct: if someone aware to be banned, then just play fair and don't use a third-party software for Ingress according to Terms of Services. ;)
[Xposed Framework Modules] Cypher_01:
Exactly :)

[MENTION=5369313]Genericxx[/MENTION]: Just out of curiosity, do you know, what mods/apps your banned colleges were using?
[Xposed Framework Modules] infected321:
xglyph wont work on OP3

Hi,

I have a problem with my Oneplus 3 with OxygenOS 3.1.2, as xglyph is not working.

Installed xposed framework from twrp, then the app, and then xglyph.

Xposed showing in green, that framework installed, xglyph activate is on, Correct glyph checked.

Even no complex hack feedback, when I tap on command screen, even no glyphs corrected.

I have a Oneplus One with CM13, the install method is the same, and works perfectly, so as far as I know, I'm not doing anything wrong.

Tried with xposed framewrork 85,80,82 the result is same

Here is the xposed debug log (checked in xglyph of course) of framework 82, from boot till hack try:

06-24 20:24:10.995 I/Xposed ( 3013): -----------------

06-24 20:24:10.995 I/Xposed ( 3013): Starting Xposed version 82, compiled for SDK 23

06-24 20:24:10.995 I/Xposed ( 3013): Device: ONEPLUS A3003 (OnePlus), Android version 6.0.1 (SDK 23)

06-24 20:24:10.995 I/Xposed ( 3013): ROM: ONEPLUS A3003_16_160606

06-24 20:24:10.995 I/Xposed ( 3013): Build fingerprint: OnePlus/OnePlus3/OnePlus3:6.0.1/MMB29M/213690:user/release-keys

06-24 20:24:10.995 I/Xposed ( 3013): Platform: arm64-v8a, 64-bit binary, system server: yes

06-24 20:24:10.995 I/Xposed ( 3013): SELinux enabled: yes, enforcing: yes

06-24 20:24:11.041 I/Xposed ( 3013): -----------------

06-24 20:24:11.041 I/Xposed ( 3013): Added Xposed (/system/framework/XposedBridge.jar) to CLASSPATH

06-24 20:24:21.170 I/Xposed ( 3014): -----------------

06-24 20:24:21.170 I/Xposed ( 3014): Starting Xposed version 82, compiled for SDK 23

06-24 20:24:21.170 I/Xposed ( 3014): Device: ONEPLUS A3003 (OnePlus), Android version 6.0.1 (SDK 23)

06-24 20:24:21.170 I/Xposed ( 3014): ROM: ONEPLUS A3003_16_160606

06-24 20:24:21.170 I/Xposed ( 3014): Build fingerprint: OnePlus/OnePlus3/OnePlus3:6.0.1/MMB29M/213690:user/release-keys

06-24 20:24:21.170 I/Xposed ( 3014): Platform: arm64-v8a, 32-bit binary, system server: no

06-24 20:24:21.170 I/Xposed ( 3014): SELinux enabled: yes, enforcing: yes

06-24 20:24:21.174 I/Xposed ( 3014): -----------------

06-24 20:24:21.174 I/Xposed ( 3014): Added Xposed (/system/framework/XposedBridge.jar) to CLASSPATH

06-24 20:24:34.392 I/Xposed ( 3013): Detected ART runtime

06-24 20:24:34.394 I/Xposed ( 3013): Found Xposed class de/robv/android/xposed/XposedBridge, now initializing

06-24 20:24:34.513 I/Xposed ( 3013): Loading modules from /data/app/com.xingress.xglyph-1/base.apk

06-24 20:24:34.771 I/Xposed ( 3013): Loading class com.xingress.xglyph.Xglyph

06-24 20:24:46.751 I/Xposed ( 3014): Detected ART runtime

06-24 20:24:46.756 I/Xposed ( 3014): Found Xposed class de/robv/android/xposed/XposedBridge, now initializing

06-24 20:24:46.845 I/Xposed ( 3014): Loading modules from /data/app/com.xingress.xglyph-1/base.apk

06-24 20:24:46.990 I/Xposed ( 3014): Loading class com.xingress.xglyph.Xglyph

Any idea, or advice what else can I try?

Thanks
[Xposed Framework Modules] Cypher_01:
Did you activate the module in the Xposed Installer? Do other modules work?

Check the Debug Log (Xposed) in Xglyph and post your log again.
[Xposed Framework Modules] infected321:
Yes, I've activated, of course, and the time of the attached log "Debug log (xposed)" was activated too. Will try with other xposed modules, because it is very strange, and suspiciously xposed fails.
[Xposed Framework Modules] infected321:
Looks like other module working. Screenshots and log are here https:// mega.nz/#!Q48D1QyJ!6WGsYCsrdS_w_VgyiscHs8vgMwCP9cbEyGs6vBDrOHA
[Xposed Framework Modules] infected321:
UPDATE: 12.1 works perfectly, only 13 is faulty
[Xposed Framework Modules] edward34:
V13 can't work too

V12.2 do work

my device next bit robin

it was work on V13 but device after June OTA

it can't work
[Xposed Framework Modules] Cypher_01:
Strange. Maybe this has something to do with the Xposed version I used to build the project. Since v13 I'm using the new API method, not the jar library anymore.

But I can't undo that, because rovo89, the creator of Xposed, announced, that support for the jar library will be removed from Xposed sooner or later. Old modules will then no longer work.
[Xposed Framework Modules] kshitij84:
non rooted

can you please go back to the non rooted method ?
[Xposed Framework Modules] Cypher_01:
I'm not sure what you mean "go back". This is an Xposed module. It doesn't use root directly, but to install Xposed, you need root.

If you're not rooted, you could use Glyph predictor, which uses a different approach, but for Xglyph, you need Xposed and therefore you need root.
[Xposed Framework Modules] larswars:
It's working perfectly all the time. Must be your fault.
[Xposed Framework Modules] ingresspokogo:
I had an account banned over the weekend, havent worked out if it was Xglyph or a spoofing app I was trying. But I am currently seeing in the Xposed Debug log the following:

Xglyph: [DEBUG] Ingress loaded

Xglyph: [DEBUG] o.mq':NoSuchMethodError
[Xposed Framework Modules] larswars:
Spoofers are getting banned and that is the right way. F*ck Spoofers!So it wasn't Xglyph!
[Xposed Framework Modules] selemine:
well the game seems to be calling logcat -t 100 -v time so it looks a bit fishy
[Xposed Framework Modules] nopenopenopenope:
Where did you seen that?

I tried to logcat ingress launch with xglyph and i havent seen that
[Xposed Framework Modules] selemine:
Xprivacy asks if an app requests acess to functions that do not match current rules. It seems that Ingress wanted to call logcat but it may also be a wrong attribution ,not sure how precise xprivacy is there.
[Xposed Framework Modules] larswars:
Complex Hack isn't working since latest Update! ?
[Xposed Framework Modules] Cypher_01:
Ingress 1.105.1

Hi@all,

I see what's the problem with COMPLEX/SIMPLE glyphs. As I wrote in my post about Xglyph v13, the hooked code is part of the obfuscated classes of the Ingress client. I'm happy that it even worked for so many further Ingress versions, but now we are at the point where the obfuscation broke it.

I already found the new spot in Ingress source code, I just have to implement and test it. Stay tuned.
[Xposed Framework Modules] KDL037:
Appreciate your continued efforts and for reviving the project :svetius: