Overclock Glyph is almost never highlighted, very difficult to see
DizzyBum
✭✭✭
in Report a Bug
Whenever I begin an Overclock hack session on a portal, the glyph is almost always very thin, dark, and barely readable for me. I am expecting the glyph to be properly highlighted so I can easily read it in all conditions, but this almost never happens.
Screenshot of the initial tesseract deployment. The first glyph is WAR:
It took me several seconds to find the correct position to confirm the WAR glyph, and it remained unhighlighted the entire time, with the glyph lines basically blending in and looking like the tesseract borders to me:
This essentially makes Overclock unplayable for me in certain lighting conditions.
Phone: Pixel 7
Android version: 13
Scanner version: 2.128.1
8
Comments
As described in the original announcement, the glyph will glow brighter the closer you are to the correct orientation. Even if its a symmetrical glyph, you may need to look at the glyph from 180⁰ around the glyph cube.
The issue I'm having is that, no matter what orientation I take around the cube, it never highlights, even if I'm in the correct orientation. Either all of the glyphs are always highlighted in every orientation, or none of them are. And it's almost always the latter case.
On the rare occasions the glyphs are highlighted, they stay highlighted at every orientation I take around the cube.
I also have reports from other fellow players that always see the glyphs highlighted no matter what their orientation is.
I also have reports from other fellow players that always see the glyphs highlighted no matter what their orientation is.
✋ I've never seen the lines not highlighted, I always assumed it was a feature they planned but didn't implement yet just like the cube redeployment that wasn't part of the initial release either.
Restart Ingress just before you start overclocking. The lines will probably be highlighted then. Just one of many weird memory-corruption bugs that they seem to have.
Thanks! I'll give this a try in a bit and report what happens.
I found this article when encountering the same problem with the glyphs never being highlighted during an entire week of overclocking a portal.
The orientation of where I'm standing does not appear to matter.
I will also try restarting Ingress prior to my next attempt to see if that changes the behavior.
My phone is a Pixel 7 Pro, Android 14, Ingress version 2.130.1.
I can confirm that rebooting Ingress before initiating the overclock, at least in my case, solved the issue.
After restarting Ingress the lines were properly highlighted, also regardless of the vertex angle.
Same issue
Device: Galaxy S21 ultra Exynos 2100
OS: Android 13
Get through around 6 good glyphs, then the scanner draws faint unreadable lines.
If I switch apps And return to Ingress to Overclock, same deal.
Ram usage is ~50%
and with an excellent cellular connection.
Should we need to post a log of the bug to help?
The only work around is to periodically restart ingress after a few Overclocks
As I've worked through the Chronos challenge, I have discovered that the glowing lines of the glyphs turn off quite unpredictably, even while running Ingress the entire time and not swapping between apps. In one occasion today of a five-glyph overclock, the first four were normal and the last one was missing the glowing lines, making it unreadable.
I have not yet determined any specific cause or behavior that causes it to break, but it definitely does fail after a period of time.
The only method I have found to correct the problem is to force-close and restart Ingress.
Hey for everyone, how was data service at the time? Of course if it was Wifi then nothing to add but what if using 5G? One portal I OC has spotty 5G and it takes a while for it to switch to 4G (ATT loves to state 5GE but you know it's BS)
I have had great 5G signal,
4G signal too, and it is just not working.
Looking at the logs it is clear the common layer bug appears to be the root of the problems.
Latest version of ARDK uses a much more robust and faster communication layer. Not sure if it will solve the problems but it is better than what we have now.
I'm not lucky enough to have a portal within Wifi range. ;)
But I had good 5G service at every location I encountered this issue.
That the highlight feature failed in a single Overclock hack, where four symbols rendered correctly and the fifth did not, definitely suggests more of a rendering problem than a data service problem.
This is still an issue in version 2.135.1, but per a previous suggestion in this thread, I am able to restart the app as a workaround. Luckily, force-closing the app in the middle of an overclock does not waste the hacks.
Yes I've done the same sometimes. Bit irritating that you have to waste time doing this, but good that you can rescue the hack and get the thick lines back.