Overclock hack with thin glyph pattern lines, difficult to decipher
Moodsville
✭✭
in Report a Bug
Symptom
When I try to solve a problem in the Overclock hack, the glyph pattern lines are too thin and difficult to decipher. When I restart Ingress, the lines temporarily become thicker but soon become thinner. The screenshot is attached.
Occurrence conditions
Model: Pixel 7
OS: Android 14
Note 1: Some users have reported similar symptoms on Pixel 7pro and Pixel 8pro.
Appendix 2: Pixel 3a (Android 12) has no problem.
Tip 3: No problem on iPhone (iPhone 12 pro)
Please
This is during the Overclock hack event, and we ask for an immediate fix.
9
Comments
Try moving around the Tesseract (or whatever the box is called). It is meant to glow brighter the closer you are to the correct orientation.
Keep in mind that some Glyphs are symmetrical so even if you have it lined up 'correctly' the actual orientation might be from the opposite side.
This does not work.
The only temporary work around is to periodically restart ingress
It is meant to, but I've never once seen that happen.
The thin lines are clearly a bug, since they reliably go away when you restart Ingress.
I have the exacg same issue.
Having watch other agent on their phone, their line are realy realy thicker.
It's almost impossible for us to read any glyph other than "strong"
Please act very fast !
Have you tried turning Prime off and on again?
Really, this solved the issue for me: reboot. The problem might reoccur when overclocking a lot, but then one just have to reboot again. Frustrating, but might do the trick.
I see the issue with the Pixel 7.
Walking around the object and not tripping, or walking into traffic or such is problematic. Also, most things that are overclock portals around me, are bench plaques, or sculptures or other things that are hard to get a good background for the cube to show the glyphs against.
Seems like i've potentially discovered, something regarding this bug.
<code>[FMOD] Please add an 'FMOD Studio Listener' component to your a camera in the scene for correct 3D positioning of sounds.
[FMOD] Event not found: {58439137-e8d7-4046-8179-17b182aea041}
Parent of RectTransform is being set with parent property. Consider using the SetParent method instead, with the worldPositionStays argument set to false. This will retain local orientation and scale rather than world orientation and scale, which can prevent common UI </code>
Is roughly the same bug we've seen with the likes of lag and such
Which appears too be stemming from the comm layer. particular the protocol used.
I have similar problem on Huawei P30 Pro - lines are almost always very thing, sometimes invisible, recognizing glkyphs is hard or impossible. Soimetimes, rewraly, at random, glypohs are shown ok. It does not depend oin the orientation of the cube.
reboot does not help in my case
Line are very thin on the Pixel 7. Which makes it really hard to figure out the glyph if you can even see it. usually its just a guessing game, and its not a winning combination.
Another Pixel 7 owner with the same problem. Restarting the app fixes it for a time.
Once it switched from thick lines to thin in the middle of a hack, after the first glyph.
I've had the issue on my Pixel 6a
Usually force closing the app helps the thin lines from no longer appearing. I'm trying to see if this is due to data being spotty (5G switching to 4G/LTE) but can't confirm.
I've have the same issue on my Pixel 8 pro. And NIA please unlock the Pixel 8 pro for portal scanning - sorry, it's a shame for an ex-Google startup.
Fix it! soon(TM)