|
Magic Numbers is an ad-free, offline, and open-source Android app that generates spiritual numerology messages based on the **Rhythm of the Moment**. All calculations are performed locally on the device using a deterministic numerology engine implemented in Kotlin. You can download the latest release directly from GitHub. |
- Numbers are generated on demand.
- The random generator is seeded using:
Random(System.currentTimeMillis())- Default length: 6 digits
- Leading zeros are preserved.
- Fully deterministic per millisecond of interaction.
Implemented in:
calculateCrossSum(number: String)- All digits are summed.
- If the result is greater than 9:
- It is reduced step-by-step
- Reduction stops if:
- A single digit is reached
- A master core number (11, 22, 33, 44) appears
Example:
0 + 8 + 2 + 0 + 0 + 9 = 19
1 + 9 = 10
1 + 0 = 1
The full reduction path is always displayed.
Detected if either:
- Cross sum before reduction matches
- Reduced value matches
Supported core masters:
11, 22, 33, 44
Core master numbers have highest summary priority.
Detected by substring presence inside the number:
11, 22, 33, 44, 55, 66, 77, 88, 99
- Multiple amplifiers supported
- Ordered by appearance in the number
- Do not override core masters
Implemented in:
getAngelResIds(number)Triggered when at least two identical digits appear consecutively:
Examples:
00
11
222
3333
444444
- Supports up to 6 repetitions.
- No detection of non-adjacent patterns.
- No false positives.
Detected dynamically:
123
1234
12345
123456
Other ascending sequences return a generic ascending message.
Detected dynamically (e.g., 654, 4321).
Detected if:
number == number.reversed()Special handling for 4-digit mirror format (ABBA).
Detected for 4+ digits:
ABAB
1212
3434
Exact repetition required.
Applied only for:
- 4-digit numbers
- 6-digit numbers
Implemented in:
getResonance(number)- AAAA (Monotype)
- AABB
- ABAB
- ABBA
- None (fallback)
- AAAAAA (Monotype)
- AAABBB
- ABCABC
- Palindrome
- None (fallback)
Each resonance provides:
- Title
- Meaning
- Focus hint
Implemented in:
getDominantRepeatDigit(number)If a digit appears 3 or more times, it influences:
- Summary
- Energy Flow
Implemented in:
calculateFrequencyScore(number)Formula:
average(digits) / 9.0
- Clamped between 0.1 and 1.0
- Displayed as percentage
- Visualized with HSV-based color gradient (0–120° hue)
Implemented in:
getStateResId(frequency: Float)| Frequency Range | State |
|---|---|
| ≥ 0.95 | Pure Clarity |
| ≥ 0.90 | Strong Clarity |
| ≥ 0.85 | Medium Clarity |
| ≥ 0.80 | Weak Clarity |
| ≥ 0.75 | Strong Alignment |
| ≥ 0.70 | Weak Alignment |
| ≥ 0.65 | Strong Tension |
| ≥ 0.60 | Weak Tension |
| ≥ 0.55 | Strong Focus |
| ≥ 0.50 | Weak Focus |
| ≥ 0.45 | Strong Shift |
| ≥ 0.40 | Weak Shift |
| ≥ 0.35 | Strong Transformation |
| ≥ 0.30 | Weak Transformation |
| ≥ 0.20 | Reflection |
| ≥ 0.15 | Open |
| ≥ 0.10 | Withdrawal |
| ≥ 0.05 | Fragile |
| < 0.05 | Void |
Implemented in:
getPseudoHzFormatted(frequency: Float)The app derives a symbolic “frequency resonance” value from the calculated frequency score.
Formula:
Hz = (frequency × 900) + 100
| Frequency Score | Displayed Hz |
|---|---|
| 0.1 | ~190Hz |
| 0.5 | ~550Hz |
| 1.0 | ~1000Hz |
- The Hz value is symbolic and not scientifically measured.
- It is intended as a spiritual visualization layer.
- The value is always clamped between:
0.1f – 1.0f- Final output format:
~550Hz
MagicNumbers analyzes every generated frequency across multiple spiritual layers.
The Harmony Engine evaluates the energetic resonance of a number based on its calculated frequency.
- Frequency ≥ 0.5 → Harmony
- Frequency < 0.5 → Learning Field
For the calculated root number and any detected amplifier numbers (11, 22, 33, 44, 55, 66, 77, 88, 99), individual interpretations are dynamically loaded.
Examples:
- 4 → Stability, structure, and grounding
- 7 → Inner wisdom and spiritual growth
- 11 → Intuition and higher awareness
- 22 → Manifestation and master builder energy
Depending on the resonance score, meanings are presented as:
- Harmony
- Learning Opportunity
- Growth Potential
Each frequency is also connected to an energetic center (chakra).
| Number | Chakra |
|---|---|
| 1 | Root Chakra |
| 2 | Sacral Chakra |
| 3 | Solar Plexus Chakra |
| 4 | Heart Chakra |
| 5 | Throat Chakra |
| 6 | Third Eye Chakra |
| 7 | Crown Chakra |
Master Numbers have dedicated chakra associations:
| Master Number | Chakra |
|---|---|
| 11 | Third Eye Chakra |
| 22 | Root Chakra |
| 33 | Heart Chakra |
| 44 | Throat Chakra |
| 55 | Solar Plexus Chakra |
| 66 | Sacral Chakra |
| 77 | Crown Chakra |
| 88 | Root Chakra |
| 99 | Crown Chakra |
For every detected frequency, MagicNumbers generates a chakra-specific interpretation, connecting numerological symbolism with energetic awareness.
Each generated message combines multiple spiritual systems:
- Numerology
- Master Numbers
- Angel Numbers
- Chakra Associations
- Harmony & Learning Fields
- Archetypal Symbolism
This creates a multidimensional interpretation of the generated frequency, transforming a simple number sequence into a meaningful spiritual snapshot of the moment.
Implemented in:
getPersonalResonanceChakraBalance(reduced: Int, amplifiers: List<Int>)The Personal Resonance Chakra Balance extends the existing chakra interpretation with a dynamic seven-chakra balance model. It combines the numerological input with Fibonacci weighting, the Golden Ratio, chakra activation, temporal resonance, and a personal resonance wave.
The result is a balance percentage from 0–100% for each chakra, together with one of three states:
| Balance | Status |
|---|---|
| ≥ 80% | Balanced |
| ≥ 50% | Adjustment |
| < 50% | Imbalanced |
The calculation starts with the reduced number and all amplifier numbers:
val values = (listOf(reduced) + amplifiers).distinct()Only unique values are used.
The personal resonance value is the sum of all unique input values:
Resonance Value = Σ unique resonance values
This value is used as an individual parameter throughout the resonance calculation.
The seven chakras use the predefined Fibonacci chakra weights:
Fibonacci Weightᵢ
The weights are normalized first:
Fibonacciᵢ =
Fibonacci Weightᵢ / Σ Fibonacci Weights
This produces a relative Fibonacci distribution across all seven chakras.
The Golden Ratio is defined as:
φ = 1.618033988749895
The Golden Ratio weighting pattern is:
[1/φ, 1, φ, 1, φ, 1, 1/φ]
These values are also normalized:
Goldenᵢ =
Golden Weightᵢ / Σ Golden Weights
This provides an additional symmetrical Golden Ratio component for the seven-chakra target distribution.
Fibonacci and Golden Ratio weighting are combined using a 70/30 split:
Target Weightᵢ =
Fibonacciᵢ × 0.70
+ Goldenᵢ × 0.30
The resulting target weights are normalized once again:
Target Percentᵢ =
Target Weightᵢ / Σ Target Weights × 100
Thus:
70% Fibonacci
30% Golden Ratio
The resulting percentage represents the calculated target distribution for each chakra.
Each unique resonance value is mapped to its corresponding chakra.
For every value, the matching chakra receives one activation point:
Activationᵢ =
Number of unique resonance values assigned to chakra i
The total activation is:
Total Activation = Σ Activationᵢ
The activation percentage is:
Activation Percentᵢ =
Activationᵢ / Total Activation × 100
This represents how strongly each chakra is activated by the current numerical input.
The current device date and time are converted into a continuous numerical time value:
Time Value =
Year × 365.2425
+ Day of Year
+ Hour / 24
+ Minute / 1440
+ Second / 86400
The fractional day allows the calculation to respond to the current hour, minute, and second.
Each chakra receives an individual frequency:
Frequencyᵢ =
φ + (i + 1) × 0.1618033988749895
where i is the zero-based chakra index.
The temporal phase combines the current time with the personal resonance value:
Phaseᵢ =
Time Value × Frequencyᵢ
+ Resonance Value × φ
A sinusoidal wave is then calculated:
Waveᵢ = |sin(Phaseᵢ)|
Therefore:
0 ≤ Waveᵢ ≤ 1
The wave is converted into a percentage:
Wave Percentᵢ =
Waveᵢ × 100
This creates a dynamic time-dependent resonance component for each chakra.
A second sinusoidal component is calculated directly from the personal resonance value and chakra index:
Resonance Influenceᵢ =
(1 + sin(
Resonance Value × (i + 1) × 0.618033988749895
)) / 2
The result is normalized to:
0 ≤ Resonance Influenceᵢ ≤ 1
and becomes a 0–100% component when used in the personal state calculation.
The three dynamic components are combined using a 40/35/25 weighting:
Personal Stateᵢ =
Activation Percentᵢ × 0.40
+ Wave Percentᵢ × 0.35
+ Resonance Influenceᵢ × 100 × 0.25
The weighting is:
| Component | Weight |
|---|---|
| Chakra Activation | 40% |
| Temporal Wave Resonance | 35% |
| Personal Resonance Influence | 25% |
| Total | 100% |
The resulting Personal State represents the calculated current resonance state of the chakra.
The personal state is compared with the calculated target distribution:
Differenceᵢ =
|Personal Stateᵢ - Target Percentᵢ|
The difference is normalized:
Normalized Differenceᵢ =
clamp(Differenceᵢ / 100, 0, 1)
A value close to 0 means that the personal state is close to the calculated target. A value close to 1 represents a large deviation.
The normalized difference is converted into a harmony factor using exponential decay:
Harmony Factorᵢ =
e^(-2 × Normalized Differenceᵢ)
The final balance percentage is:
Balance Percentᵢ =
Harmony Factorᵢ × 100
The result is constrained to 0–100% and converted to an integer for display.
The exponential function makes the balance score decrease progressively as the distance from the target increases.
The final balance percentage determines the displayed state:
Balance ≥ 80%
→ BALANCED
Balance ≥ 50%
→ ADJUSTMENT
Balance < 50%
→ IMBALANCED
This creates an intuitive interpretation:
- 🟢 Balanced — relatively close to the calculated target distribution.
- 🟡 Adjustment — moderate deviation from the target.
- 🔴 Imbalanced — stronger deviation from the target.
Reduced Number + Amplifiers
↓
Unique Values
↓
Personal Resonance
↓
Chakra Activation
↓
Fibonacci + Golden Ratio
↓
Target Balance
↓
Current Time
↓
Temporal Wave Resonance
↓
Personal Resonance Influence
↓
Personal Chakra State
↓
Difference to Target
↓
Exponential Harmony
↓
Balance 0–100%
↓
Balanced / Adjustment / Imbalanced
The calculation is deterministic for identical input values at the same date and time. Because the current device time is part of the formula, the calculated temporal resonance changes continuously over time.
The Fibonacci and Golden Ratio components define the target distribution, while numerical activation, temporal wave resonance, and personal resonance determine the current state that is compared against that target.
This functionality is an interpretive/spiritual visualization model implemented mathematically in the app. The calculated percentages represent the application's internal resonance model and are not scientific measurements of physical energy, chakra activity, or frequency.
The calculated frequency also controls the UI energy color.
Implemented in:
frequencyColor(percent: Float)The hue is mapped dynamically:
Hue = frequency × 120
| Frequency | Color |
|---|---|
| Low | Red |
| Medium | Yellow |
| High | Green |
The visualization uses the HSV color model:
Color.hsv(
hue = hue,
saturation = 1f,
value = 1f
)Implemented in:
getTimeEnergyMessage(context, currentTime)The app can attach a spiritual “time resonance message” to the current moment.
The current device time is formatted as:
HH:mmExamples:
22:22
07:07
11:11
03:33
The engine converts the current time into a dynamic string resource key:
time_2222
time_1111
time_0707and attempts to load a localized message from Android resources.
Implemented using:
context.resources.getIdentifier(...)val normalized = currentTime.replace(":", "").trim()
val resName = "time_$normalized"If the matching string resource exists:
<string name="time_1111">
A gateway of alignment is opening around you.
</string>the message is displayed automatically.
- Fully offline
- Based on device local time
- Optional system
- No internet requests
- Fully localized through Android string resources
- Missing entries safely return:
nullThe battery is interpreted as a symbolic spiritual frequency state.
Examples:
| Battery | Meaning |
|---|---|
| 11% | Intuition becomes stronger |
| 22% | Manifestation energy rises |
| 44% | Protection surrounds you |
| 77% | Mystical resonance appears |
| 88% | Infinite energy awakens |
| 100% | Universal alignment achieved |
🔋 Battery Energy 66%
Heart energy shines brightly.
If a valid time message exists:
- The current time is shown
- The resonance text is displayed
- The section becomes part of:
- UI output
- Clipboard export
Example:
Time Energy: 22:22
Alignment between intention and manifestation is strongest now.
Time energy messages support all translated languages automatically via:
res/values-xx/strings_time.xml
This allows culturally adapted interpretations for symbolic times such as:
- 11:11
- 22:22
- 03:33
- 07:07
- 12:12
- etc.
Implemented in:
getEnergyFlowResId(...)Priority order:
- Master Core
- Dominant repeated digit
- Reduced cross sum
Exactly one energy flow message is shown.
Based on:
sumBeforeReduce
Supported values:
1 – 33
Includes traditional karmic numbers: 10, 13, 14, 16, 19, etc.
Implemented in:
getSummaryResId(...)Priority:
- Master Core
- Multiple Amplifiers
- Dominant repeat (≥3)
- Reduced cross sum
Angel numbers and resonance never override each other.
The generated clipboard text includes:
- Title
- Message for the moment
- Cross sum steps
- Master energy section
- Angel section
- Harmony & Chakra Interpretation Engine
- Frequency %
- Digit vibration (unique digits only)
- Digit descriptions (with amplification text)
- Resonance section
- Summary
- Karmic detail (if applicable)
- Energy flow
Markdown formatting is cleaned before export.
- Language: Kotlin
- UI Framework: Jetpack Compose (Material 3)
- Architecture: Single Activity
- State Management: rememberSaveable
- Minimum SDK: 24 (Android 7.0)
- Target SDK: 35+
- License: MIT
No ads.
No tracking.
No analytics.
No internet required.
The app is fully translated into:
- 🇸🇦 Arabic (العربية)
- 🇧🇬 Bulgarian (Български)
- 🇨🇳 Chinese Simplified (简体中文)
- 🇭🇷 Croatian (Hrvatski)
- 🇨🇿 Czech (Čeština)
- 🇩🇰 Danish (Dansk)
- 🇳🇱 Dutch (Nederlands)
- 🇬🇧 English (UK)
- 🇺🇸 English (US)
- 🇪🇪 Estonian (Eesti)
- 🇫🇮 Finnish (Suomi)
- 🇫🇷 French (Français)
- 🇩🇪 German (Deutsch)
- 🇬🇷 Greek (Ελληνικά)
- 🇮🇱 Hebrew (עברית)
- 🇮🇳 Hindi (हिन्दी)
- 🇭🇺 Hungarian (Magyar)
- 🇮🇩 Indonesian (Bahasa Indonesia)
- 🇮🇹 Italian (Italiano)
- 🇯🇵 Japanese (日本語)
- 🇰🇷 Korean (한국어)
- 🇱🇻 Latvian (Latviešu)
- 🇱🇹 Lithuanian (Lietuvių)
- 🇳🇴 Norwegian (Norsk)
- 🇵🇱 Polish (Polski)
- 🇵🇹 Portuguese (Português)
- 🇷🇴 Romanian (Română)
- 🇷🇺 Russian (Русский)
- 🇷🇸 Serbian (Српски)
- 🇸🇰 Slovak (Slovenčina)
- 🇸🇮 Slovenian (Slovenščina)
- 🇪🇸 Spanish (Español)
- 🇸🇪 Swedish (Svenska)
- 🇹🇭 Thai (ไทย)
- 🇹🇷 Turkish (Türkçe)
- 🇺🇦 Ukrainian (Українська)
- 🇻🇳 Vietnamese (Tiếng Việt)
| Welcome Screen | Message View |
|---|---|
 |
 |
(To display these images, create an art folder in the project's root directory and place your app's icon and screenshots there.)
- Kotlin: As the primary programming language.
- Jetpack Compose: For the declarative and modern UI toolkit.
- Material Design 3: For design components and theming.
- Android Studio: As the Integrated Development Environment (IDE).
You can download the app from the Google Play Store (link will be added here once available) or build the project yourself.
- Clone this repository:
- Open the project in the latest version of Android Studio.
- Let Gradle sync the project dependencies.
- To sign the app for release, you will need to create your own
keystore.propertiesfile or modify thesigningConfigsblock in theapp/build.gradlefile. - Run the app on an emulator or a physical device.
Contributions are welcome!
- Fork the project.
- Create your feature branch (
git checkout -b feature/AmazingFeature). - Commit your changes (
git commit -m 'Add some AmazingFeature'). - Push to the branch (
git push origin feature/AmazingFeature). - Open a Pull Request.
This project is licensed under the MIT License - see the LICENSE file for details.