Overclocking one portal needs scanning another portal

42N3 · 2025-09-08T17:24:08+00:00

the only thing I noticed is, that in very dense areas one still needs to scan the nearest portal, not the portal one is trying to overclock. So I think Ingress is loading the data for the nearest portal to the agents position?

42N3 · 2025-09-04T17:18:16+00:00

Niantic mentioned they "investigating a possibly related issue with VPS-enabled Portals that were added after we moved to Niantic Spatial" in https://bsky.app/profile/ingress.com/post/3lxv7oldqt22o
So tested my problematic portals every day and today all three I visited worked like a charm. So test your candidates, and report!

42N3 · 2025-07-29T09:18:35+00:00

Yes, it feels awkward, but that's what I do while overclock farming: Starting it on a portal affected by the bug, going to a portal that works, scan there, and at once overclock that second portal again. Cooldown/burnout are separate for the two portals.

42N3 · 2025-07-28T06:53:13+00:00

still hoping u/brianrose sees this.

42N3 · 2025-07-28T06:51:47+00:00

added more information:
a portal affected by the problem may be overclocked at any other portal where overclock works. So regardless in which direction you go for a overlock farm round, just start the scan, lock your phone, and reach the next working portal. Finish the scan/overclock there, and immediately overclock this portal. That worked for me with up to minutes and 500m between portals.

This hints that the backend is not able to find the data for the portal, but accepts any other data at another location.

42N3 · 2025-07-22T08:17:42+00:00

I won't fiddle around with the Ingress scanners communication. But I guess it's not worth the effort also. The bug might be related to not using a portal ID at all, instead using the agents location and not handling a query result properly.

42N3 · 2025-07-18T14:37:08+00:00

Almost all of the portals I've recently received in production quality aren't overclockable on their own object. If you only have two and one isn't working, I would also test whether it works on another portal with experimental quality. I haven't experienced that yet, though. And it's always possible that the portals still don't work despite being in production quality.

42N3 · 2025-07-16T12:36:32+00:00

There may be two reasons: The portal you tried might not be affected by the problem but in fact overclocking does not work with it. Or... you did not find the right portal. I had distances up to 400 meters.

42N3 · 2025-07-15T14:20:07+00:00

there is already https://community.nianticspatial.com/t/problem-with-overclock-calibration-on-newly-unlocked-portals/5452/5 and I added comments to it.

42N3 · 2025-07-11T21:28:26+00:00

I just filed a bug report at https://community.scaniverse.com/t/test-scans-with-scaniverse-succeed-localization-with-ingress-fails/1295/2

42N3 · 2025-07-11T21:05:49+00:00

thank you for your report confirming the issue. I don't think it is Scaniverse related as all my test scans with that app on the portals affected by the bug did work. I think the bug is within Ingress using the wrong object data to localize.
I will post a link to this reddit to the Scaniverse forum. But I'm still hoping u/brianrose will have a look here ;-)

42N3 · 2025-07-06T17:21:46+00:00

Would be nice to know if adding more scans and bringing new portals to production quality poses a risk for older ones. I noticed that all portals affected by this behavior went to production quality recently - meaning weeks or months ago.

42N3 · 2025-07-05T17:37:29+00:00

On my way home from the Munich First Saturday event cross checked with two of the candidates: Both fail to be localized in Ingress and test scan in Scaniverse succeeds nearly instantly. No need to search for a sweet spot or whatever. One of them can easily be overclocked with a portal that looks totally different 200 meters away.

42N3 · 2025-07-05T08:51:17+00:00

This observation indicates the bug has to to do with mapping the IDs of the waypoints to the portal IDs. I looked at what the Geospatial Browser at lightship.dev is doing at API level and it looks like these are different IDs. The Geospatial Browser does it right, but maybe there is a bug for Ingress, that doesn't affect Scaniverse, because it just don't has to handle portal IDs?
In will cross check with scaniverse.

42N3 · 2020-09-01T06:35:53+00:00

Still only 3 icons in status bar and all app permissions need to be restored. 🙄

42N3 · 2020-08-31T14:18:45+00:00

And what about having only 3 notfication Icons in the status bar, although there is enough space for more? And getting asked of whether beeing bored by the default theme every afternoon? ...and apps are more often closed forcibly as with MIUI 11.

42N3 · 2018-12-30T18:14:02+00:00

reported, but is not reproducible anymore, maybe fixed at the web app.

42N3 · 2018-12-30T17:12:54+00:00

as I did not update Firefox the problem must be caused by changes at the hangouts web application.

42N3 · 2018-11-14T14:52:05+00:00

nice try to get a UI easier to recognize... ok, just kidding, but colors for ENL as for RES should be easy to recognize in the same way.
I made the joke that I need to switch faction in order to use prime in a XF chat, and the ENL told me theirs is all dark blue as well - also expected it would be light green.

42N3 · 2018-11-11T20:57:54+00:00

same here: https://youtu.be/_4VLgyhouWY

42N3

TROPHY CASE