Gemini does not remember previous message

[KiGamji]

What happened?

After c87422a was introduced, with the following prompt in a fresh conversation (tested with gemini-2.5-pro, reasoning can be disabled):

---

### Technical Specification (TS) for “SimChassis” Xposed Module Development

#### 1. General Description

**Project Name:** SimChassis  
**Project Type:** Android application with Xposed module functionality.  
**Objective:** Automatic switching of mobile data between two SIM cards based on analysis of cellular signal quality. The app must also provide a user interface for fine-tuning switching rules and manual control.

#### 2. Project Technical Requirements

*   **Programming Language:** Java  
*   **Build System:** Gradle  
*   **`compileSdk`:** `35`  
*   **`targetSdk`:** `35`  
*   **`minSdk`:** `28`  
*   **`buildToolsVersion`:** `"35.0.0"`  
*   **Key Technologies and Practices:**
    *   **View Binding:** **MANDATORY** for all Activities. **ABSOLUTE AVOIDANCE OF `findViewById`**.
    *   **Material Design 3:** Use components from the `com.google.android.material:material` library to create a modern, responsive UI.
    *   **AndroidX:** Use libraries from the `androidx` package (especially `appcompat`).
    *   **Java Version:** `JavaVersion.VERSION_1_8`.
*   **Main Dependencies:**
    *   `androidx.appcompat:appcompat:1.6.1`
    *   `com.google.android.material:material:1.11.0`
    *   `de.robv.android.xposed:api:82` (with `compileOnly`)

#### 3. Architecture and Components

The project consists of two logical parts: UI (settings application) and backend (Xposed module).

##### 3.1. Backend Components (Module Logic)

1.  **`XposedMain.java` (Module Entry Point)**
    *   Implements `IXposedHookLoadPackage`.
    *   Target hook package: `com.android.phone`.
    *   Hooks `Application.onCreate` to obtain `Context`.
    *   **Tasks within hook:**
        *   Obtain `Context` of `com.android.phone` app.
        *   Initialize `NetworkSwitcher`.
        *   Launch `SignalMonitor` via the static method `SignalMonitor.start(context)`.
        *   Register `BroadcastReceiver` for listening to `ACTION_MANUAL_SWITCH`.

2.  **`SignalMonitor.java` (Signal Monitor)**
    *   **All methods and fields are static**.
    *   Contains `ScheduledExecutorService` for periodic signal checks.
    *   **Method `start(Context context)`:** Initializes all managers (`SettingsManager`, `SubscriptionManager`, etc.) and starts the scheduler.
    *   **Method `checkSignal()`:** Gets SIM data and signal strengths, and, based on rules from `SettingsManager`, calls `NetworkSwitcher`.

3.  **`NetworkSwitcher.java` (Switch Executor)**
    *   Contains method `switchToSim(int subId)`.
    *   **Implements a robust two-step switching mechanism:**
        1.  Changes “source of truth”: `Settings.Global.putInt(resolver, "multi_sim_data_call_subscription", subId)`.
        2.  Calls hidden method `SubscriptionManager.setDefaultDataSubId(subId)` via reflection for instant application.
    *   Provides detailed Xposed logging.

##### 3.2. UI Components (Settings App)

1.  **`SettingsActivity.java` (Main Settings Screen)**
    *   Uses **`ActivitySettingsBinding`** for all UI element access.
    *   On launch (`onCreate`), initializes `SettingsManager` and loads preferences into the UI.
    *   Implements logic for manual switch buttons (sending Broadcast).
    *   Implements “Save” button logic.
    *   Implements Action Bar menu with “Reset to Defaults” option.

2.  **`SettingsManager.java` (Settings Manager)**
    *   Works with `SharedPreferences`.
    *   Contains **`public static final` constants for all keys and default values**.
    *   Provides public `get...()` and `set...()` methods for each setting.

##### 3.3. Resources and Configuration

1.  **`app/build.gradle`:** Must include all dependencies listed in section 2 and the `buildFeatures { viewBinding true }` configuration.
2.  **`AndroidManifest.xml`:**
    *   Declares `SettingsActivity` as the entry point (`LAUNCHER`).
    *   Contains meta-tags for the Xposed module.
    *   Requests the `android.permission.READ_PHONE_STATE` permission.
3.  **`res/layout/activity_settings.xml`:** Settings screen layout. All interactive elements **MUST have `android:id`**.
4.  **`res/menu/settings_menu.xml`:** XML menu file with a single item: “Reset”.
5.  **`res/drawable/`:** Must contain vector icon `ic_reset.xml`.
6.  **`res/mipmap-*`:** Must contain adaptive app icons (`ic_launcher.xml`, `ic_launcher_round.xml`).
7.  **`assets/xposed_init`:** Text file with the fully qualified entry point class name (`com.ki.simchassis.XposedMain`).

---

### 4. Code Delivery Format

1.  **One file — one command:** Each project file is provided as a separate, self-contained PowerShell code block.
2.  **Use of `Set-Content`:** Code for each file must be wrapped in a `Set-Content -Path "path/to/file" -Value @' ... '@` block.
3.  **Full source code:** The block `@' ... '@` MUST contain the **full, final source code** of the file. No shortening, no `//...` comments, no “finish yourself” stubs.
4.  **Directory creation:** If needed, a `New-Item -Path "path/to/dir" -ItemType Directory -Force | Out-Null` line is allowed before `Set-Content`.

**Example:**

```powershell
# Create package directories
New-Item -Path "app/src/main/java/com/ki/simchassis" -ItemType Directory -Force | Out-Null

# Create and fill XposedMain.java
Set-Content -Path "app/src/main/java/com/ki/simchassis/XposedMain.java" -Value @'
package com.ki.simchassis;

// ... FULL CLASS CODE HERE ...

public class XposedMain implements IXposedHookLoadPackage {

    // ... full implementation ...

}
'@

---

After waiting for the response to finish generating, you can ask Gemini or any other model (like GPT-4.1) something like "what were we just talking about?". Before the problematic commit, any model would easily respond, knowing the technical specifications for the task and the implementation it just did, but after upgrading to this commit or to the latest one, it would simply respond that it has no clue what was the previous message.

Code of Conduct

• I agree to follow this project's Code of Conduct

[KiGamji]

Also, PLEASE, remove the Max Output Tokens override, if possible. It is then saved to other endpoints when switching, and makes other models cut off sometimes.

[danny-avila]

Feel free to submit a PR if you've identified the issue. From this message alone, it's not clear

[danny-avila]

it's probably a context issue:

It is "remembering" previous messages as long as they fit in the context. We are conservative with the limits, so gemini-2.5-pro has a hard limit of 900k tokens to account for margin of error.

[danny-avila]

it can also present itself when timestamps are missing

[KiGamji]

Messages "fold" when there is a timestamp discrepancy between messages. If the timestamp of the messages of the export differ from the server, this issue can be created as your new messages will actually be interpreted as "older", as the frontend sorts by timestamp to target the correct parent message IDs.

We already have some things in place to help protect against this, but I think in the area of importing, we can improve it further (it's robust now when forking as opposed to importing).

so that's why.. I have literally no idea how this happens a lot on my instance, but I do think parentMessage inheritance is a much more reliable approach for this tbh. why not to use it by default?

[danny-avila]

@KiGamji I added robust timestamp handling for conversation imports, so importing will no longer create "folds" (still yet to merge changes).

However, in the process, I discovered that the issue was still happening but for a different reason.

The response has a recorded tokenCount of over 1.2m tokens:

            "content": [ /* some long response */],
            "tokenCount": 1215679, // <------ token count surpassing gemini context window
            "unfinished": false,
            "updatedAt": "2025-07-01T16:09:14.675Z",
            "depth": 1,
            "siblingIndex": 1
        },

this would essentially create the original issue of "not remembering"

Not sure how this amount of tokens was recorded for the output, since it's not accurate, and on re-running the original prompt, I don't have the issue:

[danny-avila]

this large tokenCount can be found in the file you shared: SimChassis_Xposed Module Development(1).json

[KiGamji]

That's actually nice to hear! I am too unsure how in the world would this happen, but glad to see these edgy cases being handled as well. Thank you for your cooperation!