Phonopolis: How to Solve Scenes 1–48 – Felix Puzzle Hub

If you searched for a walkthrough hub for “Felix’s loudspeaker puzzles” across Scenes 1-48, the game you want is Phonopolis. The practical answer is that the full run is best treated as three blocks: Scenes 1-10, Scenes 11-29, and Scenes 30–48. That is also how the most recent public walkthrough coverage is organized, and it matches how the game escalates its puzzle language: first object interaction, then layered loudspeaker logic and escapes, then multi-step endgame setups.

One point is worth clearing up immediately: Felix the Reaper is a different puzzle game built around shadows and rotating light. Phonopolis is the cardboard-city adventure with Felix, loudspeakers, the Leader’s broadcasts, and a scene-based progression. If a search result keeps sending you toward shadow puzzles, you are in the wrong game.

How to use this Scenes 1–48 hub

The easiest way to avoid getting lost is to stop looking for one giant scene index and instead use the game’s natural chapter flow. Recent coverage of Phonopolis follows that structure, and there is no strong sign that later updates have changed the core solutions. In other words, if a room feels impossible, you usually do not need a newer patch-specific answer. You usually need to identify which object, speaker, or route the scene expects you to test next.

• Scenes 1–10: opening tutorial puzzles, object handling, first loudspeaker resistance, and the early escape path.
• Scenes 11–29: the longest and messiest middle section, including ventilation, apartment loudspeaker setups, and urban escape sequences.
• Scenes 30–48: the final chapter, where environmental setups become larger and you start chaining multiple mechanics in a single solution.

If you get stuck, read the scene by function instead of by story beat. Ask three questions: what can Felix move, what can the environment react to, and what state change opens the next route? That mindset is more reliable in Phonopolis than treating every scene like a hidden-item puzzle.

Scenes 1–10: learn the game’s interaction rules early

The opening ten scenes do more than introduce the story. They quietly teach the rules that the rest of the walkthrough depends on. If you miss those rules here, the midgame feels much harder than it actually is.

Portrait, record player, and headphones puzzles

Early rooms use small domestic objects to tell you what kind of puzzle adventure Phonopolis is. A portrait, a record player, and a pair of headphones are not there as decoration. They are there to teach you that important objects often look ordinary, and the answer is usually about changing a room’s state rather than “using” an item on every hotspot you can find.

The reliable method in these scenes is simple: interact with every object that is clearly distinct from the background, then check what changed in the room. Did a sound source turn on or off? Did a path open? Did Felix gain cover from a broadcast? That feedback matters more than the object itself. Players lose time here when they assume the first successful interaction is the full solution. Usually it is only the first trigger in a short chain.

When the game gives you headphones or another sound-related item, think in terms of control and interference. Phonopolis uses audio as a pressure system. A scene is often solved by weakening the Leader’s influence, isolating a sound source, or redirecting attention long enough to move safely. If an early room seems static, you probably have not changed the audio state enough yet.

Opera house, crusher, and vehicle controls

This stretch is where the game starts expecting you to notice sequence. The opera house and crusher-style scenes are not about speed. They are about setting the stage before you commit Felix to the route. If you move too early, you end up resetting your own work or forcing an unnecessary loop through the room.

The best habit here is to stand still for a few seconds and identify the room’s moving parts. Which object changes the environment permanently, and which one only helps temporarily? Permanent changes should almost always come first. Temporary changes are what you use to cross the final gap.

The same logic applies to vehicle controls. Do not treat those scenes like a driving minigame. Treat them like a lever puzzle with a vehicle skin on top. The correct approach is to understand what position or access point the vehicle needs to create, then work backward from there. If you move it just because the control is available, you can easily put it somewhere that looks useful but does not actually solve the room.

Police pressure and rooftop cable traversal

By the end of this opening block, the game starts adding tension through police presence and exposed traversal. That can make the puzzles feel more action-heavy than they are. In practice, these scenes still reward calm routing. If a broadcast or a patrol is pushing Felix where you do not want to go, check whether the puzzle wants disruption first and movement second.

The rooftop cable sequence is a good example of this design. Players often fail it by committing before the route is visually clear. Because the game’s handcrafted angles can hide the obvious path, rotate your view if possible, confirm both landing points, and only then send Felix across. Most failed attempts here come from misreading the destination, not from difficult timing.

Scenes 11–29: the midgame section where most players slow down

The middle third is where Phonopolis stops teaching one mechanic at a time. Scenes begin to mix movement, sound, escape pressure, and multi-room logic. If you were comfortable in the opening, this is the part that still tests whether you actually understood why those early solutions worked.

Ventilation escape scenes

Ventilation puzzles are easy to overthink because the camera can make the space feel larger than it is. The clean approach is to reduce them to route confirmation. A vent scene is usually asking one of two questions: which opening is actually usable, and what action outside the vent changes the internal route? If you are crawling around without learning anything new, back out and look for the external switch, obstruction, or object interaction you missed.

These scenes also punish blind backtracking. Before retreating, check whether the vent network created a one-way reveal. Adventure games like this often use vents to show you a future exit before they let you use it. When that happens, the useful information is not “I cannot pass.” The useful information is “I now know which room I need to affect from outside.”

Apartment loudspeaker puzzles

The apartment section is where the search phrase “Felix’s loudspeaker puzzles” makes the most sense. These scenes revolve around how sound influences movement, safety, and access. The mistake here is treating every speaker like a simple on/off switch. What matters is the speaker’s role in the scene. Is it drawing Felix, controlling an NPC, blocking a route, or creating a safe window?

When you enter an apartment or similar interior puzzle, test each audio-related interaction and watch for the exact result. Do not chain several actions at once. If you move an object, trigger a speaker, and then reposition Felix, you lose track of what actually solved the problem. The best way through this section is to isolate cause and effect: one change, observe the room, then commit to the next step.

If a loudspeaker puzzle feels unfair, it is usually because you are solving the wrong layer. The surface layer is “how do I get past this broadcast?” The deeper layer is “what in this room allows me to break, block, redirect, or outlast that broadcast?” Phonopolis regularly hides the real answer in the environment, not in a direct speaker interaction.

Lobby routes, house puzzles, and chained objectives

By the time you reach lobby-like spaces and the plumber-house style puzzle chain, the game expects you to remember earlier lessons about everyday objects. A route can depend on something that looked purely narrative ten minutes ago. This is where you should start mentally grouping interactables by purpose: mobility, distraction, cover, and access. If you do that, larger spaces become much easier to parse.

These scenes are also where players most often create their own confusion by solving steps in the wrong order. If a house puzzle gives you three possible interactions, start with the one that changes the environment for the whole room. Leave local or personal actions for the end. That keeps you from doing the fiddly part before the room is actually ready for it.

• Check whether a newly acquired object is meant to be used immediately or simply carried forward.
• If a chase or broadcast starts, pause long enough to identify the intended safe space instead of running in circles.
• When a scene spans more than one room, assume the clue is in the relationship between those rooms, not in a single isolated hotspot.
• If the puzzle feels abstract, return to the basics: what changed, what opened, and what is still obstructing Felix?

Scenes 30–48: final chapter solutions and endgame flow

The last block takes the same mechanics and stretches them across larger environments, including the Avant-Garde Quarter and the Phonnobureau. This is where a lot of walkthroughs become harder to follow if they are too literal, because a single missed setup step can invalidate everything that follows. Think of these scenes as staged construction puzzles: you are building the answer piece by piece.

Crane puzzles and movable-object setups

Crane sequences are the clearest example of endgame thinking. A crane is rarely there to place one object in one obvious spot. It is there to let the game test whether you understand spatial planning. Before touching it, identify the final destination you need Felix to reach. Then ask what intermediate position each movable object needs to occupy so that route becomes possible.

The common mistake is to use the crane reactively: move something because it looks helpful now, then discover it blocks the actual finish path later. The better method is to treat empty floor space as future routing space. If a crate, platform, or barrier might be needed later, park it where it opens options rather than where it solves the immediate visual problem.

Multi-step environmental puzzles in the final chapter

The endgame raises difficulty by asking you to remember a room’s whole logic tree. A speaker, switch, or object placement might not matter until several interactions later. That means you should stop expecting instant feedback from every step. Some actions in Scenes 30–48 are preparation, not payoff.

If you are using a scene-by-scene reference and something seems wrong, verify that the setup state matches. In final chapter puzzles, being one object-position off is enough to make a correct later step look incorrect. This is one reason consolidated text hubs are helpful here: they remind you what the room is trying to accomplish, not just which interaction to press next.

Reaching the ending cleanly

The final run toward the Leader is less about twitch execution and more about reading what the game considers progress. If a room contains both dramatic set dressing and one or two suspiciously movable or reactive elements, trust the reactive elements first. Phonopolis likes theatrical spaces, but its solutions stay mechanically grounded. You advance by changing control systems, access routes, and room states, not by hunting for tiny hidden pixels.

That makes the endgame surprisingly fair once you slow down. Most failed attempts late in the story come from trying to finish a puzzle the moment its theme becomes obvious. Wait until you can explain the room’s logic in plain terms: what is blocking Felix, what changes that blockage, and what path opens after the change. Once you can answer those three points, the scene usually collapses quickly.

Common mistakes that make the Scenes 1–48 run harder

• Mixing up games: if a guide starts talking about rotating sunlight and walking only in shadows, it is for Felix the Reaper, not Phonopolis.
• Assuming a decorative object is irrelevant: in this game, ordinary props often carry the puzzle.
• Triggering multiple changes at once: that makes it harder to learn what actually helped.
• Treating loudspeakers as identical: some create pressure, some redirect behavior, and some are just part of a larger setup.
• Moving before planning: this is especially costly in chase scenes, crane puzzles, and rooftop traversal.
• Using the wrong scene range: public walkthrough coverage is split into three large parts, so it is easy to read a later solution and think your current scene is bugged.

If a scene solution seems off

Because current walkthrough coverage is organized by scene range rather than one universal text index, the first check is always whether you are in the correct block. A player stuck in Scene 18 can waste a lot of time reading a Scene 31 fix and assuming the game has changed. As of the latest public guidance, the bigger change is better organization of the walkthrough material, not a rewrite of the puzzles themselves.

• Confirm your current scene range: 1–10, 11–29, or 30–48.
• Reset your understanding of the room state: what has already been moved, powered, opened, or silenced?
• Check whether the puzzle wants a permanent environment change before a temporary movement step.
• If audio is involved, identify what the speaker is actually affecting.
• If the space is vertical or multi-room, look for how one area changes another rather than searching for a single final interaction.

Use this hub as a map of the game’s logic: opening object lessons in Scenes 1–10, layered sound-and-escape puzzles in Scenes 11–29, and larger staged setups in Scenes 30–48. That is the cleanest way to move through Phonopolis without getting sidetracked by the wrong Felix game or by a scene description that belongs to a different chapter.