Good afternoon, Agents and Investigators! My name is Mustafa Said and welcome back to This Week in Niantic History.
So let’s begin with what was revealed on August 25th, 2013:
This page was from a mysterious comic being penned by the equally mysterious ghost artist Tycho…..It showcases the escape from the Niantic Project facilities.
How it ties into the story: The details of Epiphany Night hadn’t ever been really explored until this comic emerged..it revealed tons of interesting secrets of what went down that night.
On August 26th, 2013, a statement from P.A Chapeau was released:
Cassandra is over. Carrie is missing. Something is very wrong. I don’t know what it is. Does anybody?
-H. Richard Loeb.
How it ties into the story: It’s obvious that Cassandra has ended but Carrie’s disappearance was unexpected…
On August 27th, another statement from Chapeau was released:
Still no word from Carrie. Had a photographer with me in Chicago. He sent me these images, said his camera was malfunctioning. I don’t think that was the case. -H. Richard Loeb.
How it ties into the story: Shaper Glyphs discovered at the site of the final Anomaly in Chicago….it only deepened the mystery of what occurred with Cassandra.
On August 28th, 2013, a document was leaked on the Niantic Project Investigator Board:
It was a conversation between Avirl Lorazon and Zeke Calvin. Calvin wanted to find Lynton-Wolfe alive. Lorazon didn’t really care. What was known between them both: Lynton-Wolfe’s escape caused chaos to ensue in his leave.
How it ties into the story: Lynton-Wolfe is on the move, perhaps in danger, perhaps dead. No one knew where he was or what he was up to anymore…..
And finally, two videos emerged on August 25th, 2013. The first one being the twenty-third installment of the Ingress Report:
In the episode, Susanna Moyer recaps the end of the Cassandra Anomalies and interviews Agents on site in New York as well as Devra Bogdanovitch and Hank Johnson. What they have to say on Cassandra is quite interesting (as well as the end of the video….)
And the second…It’s a conversation between ADA and Klue. I’ll leave it at that:
Cassandra is over. The world is different now…somehow….and the Anomalies are coming.
Tune into DeCode Ingress next week to find out what happened next in Niantic History!
Welcome back to our 9th teardown of Ingress APKs. This version only lists “bug fixes” as the official changelog on Google Play, but we can dig beneath the surface and see what’s really different.
In APK since 1.55.0
We saw two changes in the expected responses of various mission functions. The passphrase mission parameter clue was renamed to question, and the MissionStats response (the information you get when clicking on a mission) gained the numUniqueCompletedPlayers integer. So now we can see how many unique agents completed a certain mission.
There were only two changes to the server -> client functionality. The bulk of mission changes happened in the design and layout of them. We saw the addition of many strings which are related from passphrases to field trip cards.
ERROR_WHILE_VIEWING_FIELD_TRIP_CARD = “Failed to complete Field Trip card objective: %s”
TEXT_PASSPHRASE_DEFAULT_QUESTION = “PASSPHRASE:”
TEXT_PASSPHRASE_INCORRECT = “Incorrect.”
TEXT_PASSPHRASE_WAYPOINT_NULL = “Unavailable.”
TEXT_ONLY_ONE_MISSION_IN_PROGRESS = “Mission already in progress”
TEXT_HIDDEN_WAYPOINT_TITLE = “???”
As we’ve discovered this feature almost 6 versions ago the functionality is quite known. We can only sit and watch as the feature nears completion.
First noticed in the Handshake and Intel map around August 18, this change was expected to be hidden in this APK and sure enough made an appearance. Ornaments appear to be directly related to Anomalies. These ornaments attach to certain specified portals with one of the following four types (anomaly_cluster, anomaly_end, anomaly_start, anomaly_volatile). However, our perception of an ornament doesn’t help with understanding this feature’s look. Below are the images for each type of ornament as it would be laid over a portal.
Various types of ornaments
As you can see, this feature has now been located in both the APK and Intel Map. This might help provide agents quick access to identify cluster / volatile portals in the middle of an anomaly instead of cross referencing Google Plus. When an ornament is attached to a portal, additional attributes are attached to it. These are listed below.
These attributes are quite broad and not hardcoded to anomalies directly which looks like they might play into future use where certain portals need to stand out from others.
Jailbreaking / Rooting
On our previous teardown of 1.58.2, we noticed a few new changes that may have locked out jailbroken/rooted devices. I’m proud to announce that as of 1.59.1 the below checks have been removed.
These boolean values were added in 1.58.2 and sent to Niantic as part of the Device handshake. It appears they got the data they wanted and didn’t want to lock out this percentage of agent user base. This code has been removed.
Everyone has come across an agent who still doesn’t know what Glyph Hacking is. It happens to everyone. It appears that a new addition may help new agents discover this feature.
This feature references a DoubleSidedProgressBar which increases in value depending on how long the HACK button has been held.
As you can see above, whenever this feature is released new agents should discover Glyph hacking much quicker.
Direct Recharge Flow
Our Handshake and APK has now hinted at a “enableDirectRechargeFlow” change. In 1.59.1, the progression for recharging is now: find a Portal Key -> Recharge -> Recharge All / Pick a resonator to recharge. This method is now less button clicks after the jarring change in 1.58.2.
Build August 26
Leaked August 28
Ornaments have caught my eye and I’m hoping they are live in time for Tulsa (Helios secondary site), as I’d like to see this feature live there. Lots of activity now with missions, direct recharge, and ornaments. This version is probably just a stepping stone for a bigger feature release of 1.60.0! Hack on agents, I’ll see some of you at Tulsa.
The post is linked to a SoundCloud track titled 45-8-N-1 and upon opening it you will hear annoying tones. The first type of noise you will hear will be the sound of a touch tone phone. You will also hear some morse code intermixed with those touch tones. At the end of the sound clip, you will hear the sound of a dial-up modem.
We’ll be focusing on the morse code sound and leave the other two codes for you to solve. The touch tone has a difficulty of 3/5 and the dial-up modem has a difficulty of 4/5.
Unfortunately, when the code was valid, the code above was not valid. Listening to the morse code again, there is a slight gap between the -.- and the . near the beginning. It could either be -.- (k) being -.– (y) or -.-. (c); or the . (e) becoming -. (n) or .. (i).
The last code is hiding in the channel’s description:
/chanserv info #niantic
<ChanServ>: Information for channel #niantic:
<ChanServ>: Founder: Theresa_Chic
<ChanServ>: Description: welcome to the Niantic/Ingress channel - 9dr7ghevate0e4d
<ChanServ>: Registered: Jul 29 21:03:44 2014 CEST
<ChanServ>: Last used: Aug 15 17:21:09 2014 CEST
Trying atbash or Caesar cipher does us no good here. We have to make an assumption: this is a substitution cipher.
This will be covered in an upcoming article (spoiler: we’ll be using regular expressions), but taking a look the longest chunk of text:
In a substitution cipher, each character you swap will change all similar characters. For example, in the word above, if you change s’s to be t’s and i’s to be a’s (we’ll show the substititions with uppercase characters to distinguish the changes):
So we have to look for a word that has matching characters in:
the 1st and 4th positions
the 2nd and 8th positions
the 5th, 7th, and 9th positions
the 6th and 10th positions
There is only one keyword that matches that description: substitution. What a coincidence!
But the numbers aren’t quite right (0 is not a valid number in the passcode format). Normally with a code like this, one would add (or substract) 13 from the numbers and modulus the result with 10.
Assuming the numbers will all increment by the same amount, the set of numbers in the passcode can be:
Trying all 3, the passcode is:
In the last post of this series, we’ll go back to the Verum Inveniri post and investigate the SoundCloud link attached to the post. We’ll also look into a code found on a reddit comment made by Verum Inveniri.
I am proud to release Part 3 of the Ingress How To Play series. This video shows some more of advanced aspects of Ingress that you wouldn’t necessarily tell a young Agent just picking up the scanner. However, new and veteran Agents alike should be able to take something away from the Ingress How To Play series. Thank you for your time, enjoy!