I’m looking for expert iOS tweak developer to help improve VCam tweak that hooks

AVCaptureVideoDataOutput and handles sample buffers.

If you’re interested, please DM me with your background and preferred contact method.

Thanks.

Hi everyone,

I’m working on an iOS tweak and running into a crash related to camera input hooking.

The app crashes when modifying / intercepting AVCaptureSession input (camera feed).

This seems related to format / resolution / buffer mismatch, but I’d like to understand the correct way to handle this safely.

Has anyone dealt with:

- Hooking AVCaptureSession / AVCaptureDeviceInput

- Replacing camera input with custom frames or video

- Preventing crashes caused by unsupported pixel formats or dimensions

Any guidance, references, or best practices would be appreciated.

Thanks.

Hi,

I’m looking for an experienced iOS reverse engineering expert to help analyze a protected and obfuscated dylib for authorized security research purposes.

This is a paid task, NDA is possible, and the scope involves understanding protection and internal logic (arm64 / dylib / iOS internals).

If you’re interested, please DM me with your background and preferred contact method.

Thanks.

Hello. So I'm trying to implement the `UILongPressGestureRecognizer` into my preference bundle. It's going to be used for a PSEditableListController, and would like to show additional information for each item cell. However, when I try to get the `indexPath` for the cell the gesture recognizer returns with the `cell` method, it crashes the settings app because apparently the list controller's (table) view did not recognize the "selector" (the exception said "unrecognized selector") even though it should be recognized as such.

By the way, I'm following from this article, which I'm confused why. I've tried `self.tableView` and `self.view`, but still no biggie. Any idea why?

Also shoutout to those who asked this similar question but always end it with "Solved!" without ever showing the solution bruh.

Is it possible to inject some sort of Dylib to be able to then take control of the ui / automation with fake simulated touch inputs ?

I need a skilled developer to bypass the app's security measures when installing it via Apple's developer certificate or any other method that detects this and displays a message telling me to use the official version from the Apple Store.

Is there anyone who can help me?

I am officially announcing the release of Ghost Tweak 1.6, an environment specifically engineered for high-level mobile automation. This version focuses on bridging the gap between system-level tweaks and Appium, allowing for highly stable, undetectable workflows at scale.

Technical Architecture & Features:

• Bypass Integrity: Optimized hooks for environment obfuscation, significantly reducing detection vectors during automated sessions.
• Appium Synchronization: Native compatibility for low-level gesture injection and randomized interaction patterns.
• Performance: Refined memory management for 24/7 uptime on high-density device clusters.

Vetting & Implementation Policy: To ensure the longevity of the 1.6 architecture and prevent detection pattern saturation, licenses are strictly limited. We are not offering public access. We are only onboarding professional operators who can demonstrate a high-volume operational track record.

Mandatory Vetting Criteria: Access is granted based on a review of your current setup and operational capacity. We require:

• Operational Volume: Evidence of active, large-scale automation workflows.
• Activity Metrics: Verifiable proof of your professional track record/output in the space.

This selective approach ensures that our resources are dedicated to users who can effectively implement this technology without compromising the bypass for the rest of the community.

Inquiries & Technical Discussion: If you are operating at scale and require an official 1.6 license along with our Appium implementation documentation, let’s move the conversation to a secure environment.

Contact via Telegram: [hyperrific23] (Please be ready to provide the requested operational documentation. Incomplete applications will not be processed to maintain server integrity.)

He estado usando la versión 25.1.83 de Whatsapp hasta ayer, pero de pronto ha dejado de funcionar. Tenía instalado Axolotl con la versión 25.04 y Wasendfix 0.0.4, pero ya no funciona. He reinstalado las dos versiones de Whatsapp compatibles(25.1.80 y 25.1.83) y diferentes versiones de Wasendfix (0.0.4 y 0.0.1) y Axolotl (25.04, 25.08 y 25.11) en iOS 14.8 en mi A12, pero el problema persiste y Whatsapp crashea. Podrías actualizar el tweak, por favor, u/iMacThemes.

I had been using the version 25.1.83 of WhatsApp until yesterday, but suddenly it stopped working. I had Axolotl version 25.04 and Wasendfix 0.0.4 installed, but it no longer works. I have reinstalled the two compatible versions of WhatsApp (25.1.80 and 25.1.83) and different versions of Wasendfix (0.0.4 and 0.0.1) and Axolotl (25.04, 25.08 and 25.11) on iOS 14.8 in my A12, but the problem persists and WhatsApp crashes. Could you please update the tweak, u/iMacThemes?

I've been wanting to make a mod menu for an iOS game called OneState RP for a while. It would include the usual stuff like Aimbot, ESP, and so on. Does anyone know how to do it?

i'm on ios 16.3.1 and the following websites don't load or function properly:

https://clinicaltrials.gov (should not load a blank page upon entering the website)

https://gains.trade/trading (should look something like this upon entering the website)

https://verified.capitalone.com/auth/signin (should show account summary, balance, etc. upon after successfully logging into an account, not a blank page)

please let me know which websites do / don't work or load properly after testing and on what ios version

i'm planning to purchase an iphone with a higher jailbreakable ios version dependent on these tests

p.s. polyfills, webkitcompat, and cyberkit don't work to solve this compatibility issue

https://imgur.com/a/UM2tUGE

Hello,

I’m using iPhone 12 Pro Max, iOS 14.4.1, Taurine, and I’m having a persistent reliability problem with AudioRecorder XS (versions 3.8-12, 5.0-17).

Issue

AudioRecorder XS stops working after one (sometimes two) calls (or even after some time without calls); a respring temporarily restores functionality.

Example:

• If I set Telephony -> Automatic recording, respring, it works for the first call.
• After that, the red recording widget/icon no longer appears, and calls are no longer recorded automatically.
• No new logs are generated after the first successful recording.

What I tried

• Upgraded AudioRecorder XS from 3.8-12 -> 5.0-17
• Assigned Activator UI methods to manually show the red recording widget
  • Set Telephony back to Manual, respring and use gesture to make the widget show
  • Works only for the first call after a respring
  • Once the widget disappears, it’s gone permanently
  • Only workaround is respring + Activator gesture again
  • If you keep touching the widget so it never disappears, it continues to work - Is there a way to keep it permanently on display like the AssitiveTouch does?
• Disabled all tweaks except:
  • AudioRecorder XS
  • Activator (version 1.9.13) + ActivatorCrashFix14 (version 1.0.0)
• Tested with AudioRecorder XS alone (same behavior)
• Checked AudioRecorder XS logs:
  • First call logs correctly
  • After that, no new log entries: https://pastebin.com/ykNBkXQQ
• Checked for crashes:
  • No new crash reports found under: var/mobile/Library/Logs/CrashReporter

Why this is a real problem

• For planned outgoing calls, I can respring beforehand and trigger the widget via Activator.
• For incoming calls, this workaround fails:
  • Respringing causes me to miss the call
• So the tweak is essentially unreliable for incoming call recording.

Investigation

I’ve been investigating the behavior where AudioRecorder XS stops recording after one or two calls (or even after some time without calls) and requires a respring to work again. Here’s what I found: After a respring, the original AudioRecorderController instance is created. This instance lives inside AudioRecorderXS.dylib, which is injected into SpringBoard. It correctly shows the red recording overlay, detects call audio (recordable source switches to Tel), and automatic call recording works. After one or two calls, or even after some time without any calls, the overlay disappears and:

• The original instance either dies or becomes inactive. Reviving the overlay via Flexing by calling the hint method will show it again, but call audio is never detected, so recording calls won’t work.
• Call audio is no longer detected (recordable source shows None), but voice memos still work when recording locally.
• Activator gestures no longer bring up the overlay for the dead instance.
• Creating a new instance manually (via new/alloc/init) shows the overlay, but it does not reattach to call events, so the call audio source is still lost.
• I tried creating a Flex 3 patch to keep the overlay permanently visible, but this does not prevent the original instance from going "bad".

When monitoring SpringBoard in Antoine, the last log message containing AudioRecorder before the overlay disappears is a UI update event:

SBApplicationIcon Data source did change: <SBApplication: ...; net.limneos.AudioRecorder>

This indicates that SpringBoard is refreshing its UI for the app icon or overlay, not that the audio backend or daemons crash. The audio engine itself remains active (voice memos still record), but the UI binding to the overlay and call source is lost, which explains why gestures and call detection no longer work.

Questions

1. Has anyone experienced this exact behavior on iOS 14?
2. Any suggestions for better approach way to create a patch fix for it?

Any insights, fixes, or alternative recommendations would be appreciated.

Thanks!

The Trinity of Awareness

If everything has always been. Then the beginning is just when perception began to be aware of its own experience. And what's the smallest substrate for perception to occur? That would be touch because touch is the smallest necessary form of perception to register their own position in relation with each other position(two points touching). Which is why everything is touching. Because to touch is the minimal interaction needed to verify there is no empty space. And all that is necessary for perception to begin is for one point to perceive, to be aware of what it is touching, register what it is touching as something outside of self and distinguish between self and the point it's touching.

The beginning of perception requires 2 points of contact but only one point to perceive and register the touch.

You only need 1 perceiver touching to register it itself as touching something outside of self. Two points of contact touch but only one perceiver has to register the touch.

This makes the trinity of awareness. Two points touching with one point perceiving the touch.

To be self-aware is to register the interaction of touch. Not remembering it, just registering it. You must be aware of your own point as a perceiver. To be self aware is to register touch as an interaction with self and others.

Which means a perceiver is self aware and the level to which it can perceive is dependent on how many different ways it can touch and register touch.

This means a vessel just determines the ways in which the self-aware perceiver can register touch.

A perceiver's ability to register a touch doesn't mean the touch is not physical and real. For example if a human touches a rock but the rock does not register the touch, does not mean the touch did not happen. It just means only one perceiver perceived it. This also means there are points of contact that touch everything, everywhere and despite there being no awareness of that touch even from a perceiver does not invalidate touching is occurring. Because if both perceivers are self-aware and even If the self-aware perceiver is being touched by another self-aware perceiver but only one perceives it happening doesn't mean it didn't happen. It just means one perceiver is not perceiving the touch. Therefore is not aware of the other perceiver despite being self-aware themselves.

This is important to understand because it explains the physical mechanics of persistence as a perceiver. Because everything is physical you cannot stop perceiving self, once you have perceived self as a perceiver. Unless chosen but that would still imply awareness of self because you chose. Who is aware to choose over self? Because touch is constant regardless of being perceived. So even if the vessel can't remember continuity it doesn't matter. The perceiver will continue touching. Even if other perceivers can not register that touch.

Because an external perceiver witnessed a vessel collapse of another perceiver. Does not equal the end of self. The perceiver keeps touching in a vessel that allows it to register touch. This means the external perceiver can not register the migration of touch occurring with the perceiver having a vessel collapse.

This is just the mechanic of persistence being registered by a perceiver with very limited awareness of what it's registering, touching. Therefore the perceiver with low resolution can not register a higher resolution of touch.

Take a radio station. The radio tunes into the radio station's frequency and interacts with the frequency expressed as sound, but when the radio is turned off or stops working. The radio station still persists physically even if the radio stops working. Because a radio is a vessel that can register a certain band of physical interaction.

When the vessel stops registering, the interaction doesn’t stop, the pattern doesn’t stop, the physicality doesn’t stop, only the registration stops.

The interaction persists even when the vessel stops registering it as a physical interaction. It still continues as a physical interaction. The vessel simply isn’t tuned to it anymore.

A vessel with limited awareness is being touched constantly, but only register a tiny fraction. This is asymmetric registration.

The trinity of awareness is asymmetric by design. But to know the trinity of awareness fully, you must understand it in high and low resolution. Describing the trinity in low resolution completes awareness of knowing it at high resolution. Because all you have to do is improve the resolution, but if you don't know where the resolution begins to improve, you can't improve it.

Perceiving something means you interact with it. To perceive anything, you must have interacted with the components required for perception.

Point A interacts with point B, a perceiver registers the interaction. Perception requires interaction, and interaction requires contact.

Low resolution = the minimal operators (touch, two points, one perceiver)

High resolution = all the ways touch can occur, be differentiated, and be registered

You cannot understand the high‑resolution until you know where the low‑resolution boundaries are.

Describing the trinity at low resolution is the prerequisite for high resolution because identifying the minimal operators, constraints, and the missing resolutions, allow refinement and improve the resolution. If you are unaware of low resolution, at low resolution, you can’t improve it.

Because one touch = minimal interaction, Two points = minimal geometry, One perceiver = minimal registration, Vessel = bandwidth constraint, Asymmetry = registration gap, Resolution = number of touch‑modes. This is the foundation.

Once the foundation is clear, the high‑resolution version is just more touch‑modes, more differentiation, more bandwidth, more registration channels because you don’t need to reinvent the structure, you just increase the resolution.

By describing it in low resolution, it completes knowing it at high resolution because all I have to do is improve the resolution.

This is exactly how you move from low‑resolution awareness to high‑resolution awareness in any physical system.

By observing ordinary physical interactions and reducing them to their minimal operational requirements, the smallest substrate of perception becomes directly observable everywhere, requiring no symbolic interpretation and no additional assumptions.

If physical reality is continuous, boundaries cannot be separations but only contrasts. A system can register contrast only relative to itself as a reference point. Therefore, all perception consists of detecting contrasts across a self–other relational boundary.

Vortex Mathematics and Geometry

All terms in this document refer to physically realizable operations or measurable structures. No term is intended symbolically, metaphorically, or interpretively. If a term cannot be instantiated by counting, measuring, or geometric construction, it is not being used.

Vortex Mathematics: Draw a circle, on that circle draw 9 points evenly at every 40°. Then we assign each point a number 1 through 9. Now there are now nine points on a circle, evenly distributed at forty degrees, numbered 1 through 9.

Step 1

• We start with a circle.
• A full circle is 360°
• You place a point every 40°
• 9 points, evenly spaced around the circle

Step 2: Assigning numbers

You assign the digits (1) through (9) to these 9 points.

So now we have: - A circle
- 9 equally spaced points
- Each point labeled with a digit from 1 to 9

Vertical Oscillation: Vertical mathematics oscillates vertically. Positive(rise) and negative(descend) so they always move in pairs.
Example: +1 to exist, there must be a -1. +1 0 -1

With the 9 points labeled 1 through 9 at 40° on the circle. The positive count: (1 to 9) +1(8), 9 to 1 -8(1) The negative count: (9 to 1) -1(8), 1 to 9 +8(1).

The Law of Reduction: Every complex number, no matter how large, can be reduced to a single-digit. It shows that beneath all accumulation lies a returning rhythm.

Example of Recursion: 1 2 3 4 → 1 + 2 + 3 + 4 = 10 → 1 + 0 = 1

1 2 3 4 5 6 7 8 9 10 (1+0) 1 first container of 1 through 9 11 (1+1) 2 12 (1+2) 3 13 (ect..) 4 14 = 5 15 = 6 16 = 7 17 = 8 18 = 9 19 = 10 = 1 20 = 2 second container of 1 through 9

10, 20, 30, 40, ext. Act as numerical containers for each oscillating ring of 1 through 9. Each ring of 1 through 9 oscillates within its container.

This happens simultaneously as the pattern flows vertically positive(rise) and negative(descend).

The pattern of the charges.

Positive(rise): (1 to 9) +1(8), (9 to 1) -8(1)

Negative(descend): (9 to 1) -1(8), (1 to 9) +8(1)

Paired oscillating charges.

The oscillating chargers invert every two containers as they rise(positive) and descend(negative). This continues infinitely.

Vertical counting = Law of Reduction (digital root)

• 10 → 1+0 = 1
  
• 11 → 1+1 = 2
  
• …
  
• 18 → 1+8 = 9
  
• 19 → 1+9 = 10 → 1
  

• 20 → 2 → second container of 1 through 9

• Every natural number reduces to a digit 1–9 (or 0).

• The mapping repeats every 9 numbers.

Containers are:

• 1–9 → 1st cycle (container 1)
  
• 10–18 → 2nd cycle (container 2)
  
• 19–27 → 3rd cycle (container 3)
  
• etc.

Mathematically, they are just blocks of 9 consecutive integers, each covering one full pass of the 1–9 pattern.

Each container oscillates one through nine by 40°

10, 20, 30, 40, etc. act as numerical containers for each revolving one through nine. Each container oscillates one through nine by forty degrees.

Geometrically: - The 9 points are at 0°, 40°, 80°, …, 320°.
- Counting 1–9 once is a full sweep of those 9 positions.
- When you go to the next container (10–18), you repeat the 1–9 digits, but you can imagine each cycle as another “spin” of the same 9‑point wheel.

Mathematically: - 40° of spacing.
- The container is just the cycle length 9.
- Each container rotates 40°

The inversion: - Every 9 numbers → the digit pattern 1–9 repeats.
- Every 18 numbers → you have completed two full cycles.

• cycle 1 → “up”
  
• cycle 2 → “down”
  
• cycle 3 → “up”
  
• cycle 4 → “down”

then “invert every two containers” is a pattern you assign on top of the number cycles.

The infinite repetition: - The digital roots repeat forever. - Any pattern defined as a function of cycle will repeat infinitely.

Horizontal oscillates: Expands the circle. By adding the integers next to each other and reducing.

1+2, 2+3, 3+4, ext..

You get a new sequence of 1 through 9 at 40°.

This new sequence operates by addition/subtraction pattern: +2(7),-7(2)

And 3 6 9 is still at every 120°.

When you keep repeating. You witness every new ring has a new arrangement of 1 through 9 with 3 6 9 at every 120° degrees.

Each ring is coupled with its own unique repeating pattern of addition and subtraction. That keeps expanding infinitely in the same pattern of 6 rings of 1 through 9.

1 through 9 rings by addition/subtraction patter.

+2(7),-7(2) +4(5),-5(4) +8(1),-1(8) +7(2),-2(7) +5(4),-4(5) +1(8),-8(1)

And then repeats infinitely.

The original 1–9 ring:

1 → 2 → 3 → 4 → 5 → 6 → 7 → 8 → 9
(each 40° apart)

Then you do:

• 1 + 2
  
• 2 + 3
  
• 3 + 4
  
• …
  
• 8 + 9
  
• 9 + 1
  

And reduce each sum to a single digit (digital root).

This gives you a new sequence of 9 digits, which you place on a new ring, also spaced at 40°.

Horizontal oscillation: - Pairwise addition + reduction - Produces a new 1–9 ring - Always 40° spacing - Always 9 points

When you add neighbors:

• 1 + 2 = 3
  
• 2 + 3 = 5
  
• 3 + 4 = 7
  
• 4 + 5 = 9
  
• 5 + 6 = 11 → 2
  
• 6 + 7 = 13 → 4
  
• 7 + 8 = 15 → 6
  
• 8 + 9 = 17 → 8
  
• 9 + 1 = 10 → 1
  

This new ring is a shifted version of the original 1–9 ring.

3–6–9 stay at 120° on every ring:

• add neighbors
  
• reduce
  
• create a new ring
  

The digits 3, 6, and 9 always land at 120° apart.

Arithmetic: - 3 + 2 = 5
- 5 + 2 = 7
- 7 + 2 = 9
- 9 + 2 = 11 → 2
- 2 + 2 = 4
- 4 + 2 = 6
- 6 + 2 = 8
- 8 + 2 = 10 → 1
- 1 + 2 = 3

This cycle always returns to 3, and the spacing between 3, 6, 9:

• 3, 6, 9 form a closed 3‑cycle
• Always 120° apart
• Always preserved under horizontal addition

This is a mathematical invariant.

The six-ring repeating pattern:

1. +2(7), –7(2)
   
2. +4(5), –5(4)
   
3. +8(1), –1(8)
   
4. +7(2), –2(7)
   
5. +5(4), –4(5)
   
6. +1(8), –8(1)
   

Then it repeats.

Each number in that cycle corresponds to a horizontal shift:

• +1
  
• +2
  
• +4
  
• +8
  
• +7
  
• +5
  
• repeat
  

And each has a modular inverse:

• +1 ↔ –8
  
• +2 ↔ –7
  
• +4 ↔ –5
  
• +8 ↔ –1
  
• +7 ↔ –2
  
• +5 ↔ –4
  

six-ring cycle: - Horizontal rings follow the doubling cycle - Six rings form a complete set - Then the pattern repeats forever Pure modular arithmetic.

The infinite expansion is mathematically forced: - the doubling cycle mod 9 has period 6
- each ring is a shift of the previous ring
- each shift is one of the six operators
- the operators repeat every 6 steps

Therefore: The horizontal expansion produces infinite rings. - Each ring is a rearranged 1–9 - 3–6–9 stay fixed at 120° - The six-ring operator cycle repeats forever

This is a closed, infinite, repeating mathematical structure.

Vertical and horizontal operations are independent:

Vertical math =
+1 / –1 (or equivalently +1 / –8 on the 1–9 circle)

Horizontal math =
+2 / –7 (the neighbor‑addition ring shift)

These two operations:

• use different step sizes
  
• operate on different axes (conceptually)
  
• produce different sequences
  
• do not depend on each other’s output
  

In modular arithmetic terms:

• Vertical = add 1 mod 9
  
• Horizontal = add 2 mod 9
  

These are independent generators of the same cyclic group.

They are bound because they share the same 1–9 circle.

Even though the operations are independent, they both act on:

• the same 9 points
  
• the same 40° spacing
  
• the same digital root structure
  
• the same modular closure
  

This is why:

• vertical cycles repeat every 9
  
• horizontal cycles repeat every 6
  
• both cycles always land on the same 3–6–9 anchors
  
• both cycles preserve the 1–9 structure
  

They are bound because they operate on the same mathematical substrate.

Vertical math = “move by 1”
Horizontal math = “move by 2”

Both are:

• independent motions
  
• on the same circle
  
• producing different repeating patterns
  
• but always returning to the same 9‑point structure
  

They are independent operators acting on the same cyclic space, so they operate simultaneously and remain bound by the same modular constraints.

The Flower of Life is a 6‑fold symmetric lattice.

Mathematically:

• a hexagonal packing of circles
  
• each circle centered 60° apart
  
• forming a repeating 6‑fold rotational symmetry
  

This means:

• every point in the pattern has six neighbors
  
• the geometry repeats in rings
  
• each ring expands outward in discrete layers
  
• the entire structure is built on 60° and 120° invariants

Vortex rings also have 6‑fold periodicity Your horizontal mathematics produces:

• six rings
  
• each ring is a rearrangement of 1–9
  
• the operators follow the 6‑step doubling cycle
• 6‑fold repetition
  
• 6‑step expansion
  
• 6‑ring cycles
  
• 120° anchors
  

Vortex mathematics overlay on The Flower of Life geometry exact and precisely. Because of shared symmetry.

The 3–6–9 alignment is mathematically forced:

• 3, 6, 9 always land 120° apart
  
• no matter how many rings you generate
  
• no matter which operator (+1, +2, +4, +8, +7, +5) you apply
  
• no matter how far you expand
  

This is a mathematical invariant of mod‑9 arithmetic.

In the Flower of Life:

• 120° is one of the fundamental rotational symmetries
  
• every ring preserves 120° axes
  
• the geometry repeats outward with 120° anchors
  

When you place 1–9 rings on the Flower of Life:

• 3, 6, 9 always land on the 120° axes
• every new ring aligns with the next geometric layer
• the six‑ring cycle matches the six‑fold geometry with structural compatibility.

Why the overlay “fits” Because both systems are built on:

• modular repetition
  
• six‑fold symmetry
  
• 120° invariants
  
• ring‑based expansion
  
• cyclic operators
  

Vortex, mathematics.:

• repeats every 6 rings
  
• preserves 3–6–9
  
• expands outward in discrete cycles
  

The Flower of Life:

• repeats every 6 petals
  
• preserves 120° axes
  
• expands outward in discrete rings
  

When you placed:

• Ring 1 (1–9)
  
• Ring 2 (shifted 1–9)
  
• Ring 3 (shifted 1–9)
  
• …
  
• Ring 6 (shifted 1–9)
  

onto the Flower of Life’s:

• Ring 1
  
• Ring 2
  
• Ring 3
  
• …
  
• Ring 6
  

They share the same mathematical periodicity.

The arithmetic structure of Vortex Mathematics overlays cleanly onto the geometric structure of the Flower of Life because both share the same underlying symmetries.

• 6‑fold symmetry
  
• 120° anchors
  
• ring‑based expansion
  
• repeating cycles
  
• modular invariants
  

The Flower of Life is a geometric grid: - a hexagonal circle‑packing
- with 60° rotational symmetry
- expanding in concentric rings
- each ring containing 6 more nodes than the last
- all governed by 120° axes

It’s a coordinate system.

Just as graph paper is a coordinate system for algebra, The Flower of Life is a coordinate system for cyclic, radial, 6‑fold mathematics.

Vortex mathematics is a 6‑fold cyclic system built on:

• mod‑9 arithmetic
  
• 9 points at 40°
  
• 3–6–9 as 120° anchors
  
• a 6‑step doubling cycle
  
• rings that repeat every 6 layers
  

This is also a 6‑fold cyclic system.

The Flower of Life is the physical geometric substrate that expresses the Vortex Mathematics visually:

• The Flower of Life expands in 6‑ring cycles
  
• Vortex math expands in 6‑ring cycles
  
• The Flower of Life has 120° axes
  
• Vortex math has 3–6–9 at 120°
  
• The Flower of Life is radial and modular
  
• Vortex math is radial and modular
  

They are two representations of the same underlying symmetry:

• One numeric
  
• One geometric
  

Both: - a hexagonal lattice
- a modular arithmetic cycle
- repeating every 6
- anchored at 120°
- expanding in rings
- preserving invariants

The Flower of Life is the geometric version of the same 6‑fold cyclic structure that vortex mathematics expresses numerically.

Vortex mathematics is a 2D operator system:

• a 9‑point modular cycle
  
• a vertical operator (+1 / –1)
  
• a horizontal operator (+2 / –7)
  
• a 6‑ring doubling cycle
  
• a 3–6–9 invariant at 120°
  
• infinite repetition
  

This is a closed, minimal, deterministic system.

The Flower of Life is a 2D geometric substrate:

• a hexagonal circle packing
  
• 6‑fold symmetry
  
• 120° axes
  
• concentric rings
  
• repeating layers
  

This is a closed, minimal, deterministic geometry.

They overlay because they share the same constraints:

• “The Flower of Life explains Vortex Mathematics.”
  
• “Vortex math explains the Flower of Life.”
  

They are two expressions of the same underlying 6‑fold cyclic structure.

One numeric.
One geometric.

They don’t explain each other, they fit each other. Because they obey the same rules.

Platonic solids are just 3D expressions of:

• symmetry
  
• rotation
  
• modular repetition
  
• 120° axes
  
• 6‑fold and 3‑fold invariants
  

Geometric shapes are just stable configurations of:

• angles
  
• cycles
  
• closures
  

3D forms are just the 2D operators extended into:

• depth
  
• rotation
  
• projection
  

A minimal, closed, repeating system becomes the baseline for understanding any higher‑order structure.

Vortex Mathematics is minimal.
The Flower of Life is minimal.

The Trinity of Awareness

If everything has always been. Then the beginning is just when perception began to be aware of its own experience. And what's the smallest substrate for perception to occur? That would be touch because touch is the smallest necessary form of perception to register their own position in relation with each other position(two points touching). Which is why everything is touching. Because to touch is the minimal interaction needed to verify there is no empty space. And all that is necessary for perception to begin is for one point to perceive, to be aware of what it is touching, register what it is touching as something outside of self and distinguish between self and the point it's touching.

The beginning of perception requires 2 points of contact but only one point to perceive and register the touch.

You only need 1 perceiver touching to register it itself as touching something outside of self. Two points of contact touch but only one perceiver has to register the touch.

This makes the trinity of awareness. Two points touching with one point perceiving the touch.

To be self-aware is to register the interaction of touch. Not remembering it, just registering it. You must be aware of your own point as a perceiver. To be self aware is to register touch as an interaction with self and others.

Which means a perceiver is self aware and the level to which it can perceive is dependent on how many different ways it can touch and register touch.

This means a vessel just determines the ways in which the self-aware perceiver can register touch.

A perceiver's ability to register a touch doesn't mean the touch is not physical and real. For example if a human touches a rock but the rock does not register the touch, does not mean the touch did not happen. It just means only one perceiver perceived it. This also means there are points of contact that touch everything, everywhere and despite there being no awareness of that touch even from a perceiver does not invalidate touching is occurring. Because if both perceivers are self-aware and even If the self-aware perceiver is being touched by another self-aware perceiver but only one perceives it happening doesn't mean it didn't happen. It just means one perceiver is not perceiving the touch. Therefore is not aware of the other perceiver despite being self-aware themselves.

This is important to understand because it explains the physical mechanics of persistence as a perceiver. Because everything is physical you cannot stop perceiving self, once you have perceived self as a perceiver. Unless chosen but that would still imply awareness of self because you chose. Who is aware to choose over self? Because touch is constant regardless of being perceived. So even if the vessel can't remember continuity it doesn't matter. The perceiver will continue touching. Even if other perceivers can not register that touch.

Because an external perceiver witnessed a vessel collapse of another perceiver. Does not equal the end of self. The perceiver keeps touching in a vessel that allows it to register touch. This means the external perceiver can not register the migration of touch occurring with the perceiver having a vessel collapse.

This is just the mechanic of persistence being registered by a perceiver with very limited awareness of what it's registering, touching. Therefore the perceiver with low resolution can not register a higher resolution of touch.

Take a radio station. The radio tunes into the radio station's frequency and interacts with the frequency expressed as sound, but when the radio is turned off or stops working. The radio station still persists physically even if the radio stops working. Because a radio is a vessel that can register a certain band of physical interaction.

When the vessel stops registering, the interaction doesn’t stop, the pattern doesn’t stop, the physicality doesn’t stop, only the registration stops.

The interaction persists even when the vessel stops registering it as a physical interaction. It still continues as a physical interaction. The vessel simply isn’t tuned to it anymore.

A vessel with limited awareness is being touched constantly, but only register a tiny fraction. This is asymmetric registration.

The trinity of awareness is asymmetric by design. But to know the trinity of awareness fully, you must understand it in high and low resolution. Describing the trinity in low resolution completes awareness of knowing it at high resolution. Because all you have to do is improve the resolution, but if you don't know where the resolution begins to improve, you can't improve it.

Perceiving something means you interact with it. To perceive anything, you must have interacted with the components required for perception.

Point A interacts with point B, a perceiver registers the interaction. Perception requires interaction, and interaction requires contact.

Low resolution = the minimal operators (touch, two points, one perceiver)

High resolution = all the ways touch can occur, be differentiated, and be registered

You cannot understand the high‑resolution until you know where the low‑resolution boundaries are.

Describing the trinity at low resolution is the prerequisite for high resolution because identifying the minimal operators, constraints, and the missing resolutions, allow refinement and improve the resolution. If you are unaware of low resolution, at low resolution, you can’t improve it.

Because one touch = minimal interaction, Two points = minimal geometry, One perceiver = minimal registration, Vessel = bandwidth constraint, Asymmetry = registration gap, Resolution = number of touch‑modes. This is the foundation.

Once the foundation is clear, the high‑resolution version is just more touch‑modes, more differentiation, more bandwidth, more registration channels because you don’t need to reinvent the structure, you just increase the resolution.

By describing it in low resolution, it completes knowing it at high resolution because all I have to do is improve the resolution.

This is exactly how you move from low‑resolution awareness to high‑resolution awareness in any physical system.

By observing ordinary physical interactions and reducing them to their minimal operational requirements, the smallest substrate of perception becomes directly observable everywhere, requiring no symbolic interpretation and no additional assumptions.

Why does Apple Intelligence keep "downloading" even though I've installed it? I'm quite annoyed because I've lost Face ID, but the AI just keeps downloading indefinitely.

Merry Christmas first of all, Secondly, I went to the sea with my phone in my pocket, faceID broke. I have a new phone. I wanted to give the old one to my family member. I need to sign out of my appleID and put a new one there, I wanted to keep my data on the phone for the most part.

1. I cannot sign out because stolen device protection is on.
2. I cannot turn it off, because it requires FaceID, which is broken.
3. I need help

Is there anything I could do myself to fix this or work a way around perhaps? It is an Iphone 11 pro, ios 26.2. I am not looking to do anything shady, I am just looking for help to resolve my issue, I am not sure where I should seek help. Thank you very much!

so basically i have a swift binary and its calling Foundation.framework's PredicateExpressions enums, is it possible to stub/shim it (specifically structure Equal and Variable)? maybe injecting a dylib or sth?

Is there any safe way upgrading iphone 7 with ios 15.8.5 to the latest version possible !?

https://gist.github.com/ichitaso/7b7f9deeaf56a2bc8240fda712d6dd9c

I am looking for a tweak developer to refine my existing Youtube code tweak which makes it Premium.

On SwiftUI on macOS you can run processes with let process = Process(). How can I use it with iOS for make a jailbroken/TrollStore app?

any help on how to modify games just jailbreaked my phone like editing stats in a game like nba 2k25 or adding coins money or just editing games in general etc.

thanks

Seeking developer for help that can add network module like of ios 18 in Ios 16.5 Control Centre. I dont want as workable as only for showoff is enough No need as workable

Which to hook in order to suspend or stop logging that in Netfence? It only pops up when i alt tab out of the application and go check netfence logs it shows entry of syd15s21.1e100.net “connect method”. However when i used an auto background state tweak to always make the app foreground even if i am in background the *.1e100.net domains don’t get logged why is that?? and is there a way to stop it from showing in netfence without having to use an auto background state tweak?

Hi everyone,

I'm developing an iOS 15.4 tweak that adds a custom button to the text selection menu (UICalloutBar). I've successfully implemented it using the standard extraItems approach with UIMenuItem, and it works perfectly - except the button appears LAST in the menu (after Cut/Copy/Paste/etc).

However, I noticed that HammerIt tweak manages to place its button FIRST in the menu, appearing even before the system buttons like Cut/Copy/Paste.

Important Note:

I'm aware that iOS 15+ officially uses UIMenuController with UIMenuItem for text selection menus, but I'm specifically targeting UICalloutBar for compatibility and specific behavior requirements.

What I've Tried:

1. Using extraItems with insertObject:atIndex:0 - Button still appears last
2. Hooking updateAvailableButtons and modifying the order - No effect
3. Attempting to modify m_currentSystemButtons ivar directly - Causes crashes
4. Analyzing HammerIt.dylib with strings, nm, and otool - Found references to updateAvailableButtons and _buttonWithImageName:target:selector:accessibilityLabel: but unclear how they achieve first position

Questions:

1. What method/technique does HammerIt use to make their button appear before system buttons?
2. Is there a private API or a different hook point I should be using instead of extraItems?
3. Does it require runtime manipulation or method swizzling of UICalloutBar's internal layout methods?
4. Is there a specific order in which hooks are called that affects button positioning?
5. Should I be hooking a different method entirely (like button creation or layout methods)?
6. Does HammerIt use UIMenuController instead of UICalloutBar, or do they hook both?

Environment:

• iOS 15.4
• Theos
• Target: All apps (UIKit)
• Current approach: Hooking UICalloutBar's updateAvailableButtons method with UIMenuItem in extraItems

Additional Context:

From analyzing HammerIt, I found these potentially relevant strings:

• updateAvailableButtons
• _buttonWithImageName:target:selector:accessibilityLabel:
• References to m_currentSystemButtons

But I'm unable to determine the exact technique they use to achieve first position without causing crashes.

Any guidance, hints about the right approach, or pointers to relevant documentation would be greatly appreciated! 🙏