Skip to content

The screen flickers and goes black when selecting code. #2865

Description

@blanhhy

Check for existing issues

  • Completed

Describe the bug / provide steps to reproduce it

See the video. This issue occurs when the cursor crosses lines while selecting code; it happens almost always and has persisted for several versions.

Record_2026-09-08-16-05-50_a2cf8efcdd42a8e6f7906303f104fb67.mp4

Environment

Device Information:
WebView Info:
Package Name: com.google.android.webview
Version: 154.0.8037.0

App Info:
Name: Acode
Package Name: com.foxdebug.acode
Version: 1.13.3
Version Code: 1009

Device Info:
Android Version: 16
Manufacturer: OPPO
Model: PJW110
Platform: Android
Cordova Version: 15.1.0

Screen Info:
Width: 360
Height: 804
Color Depth: 24

Additional Info:
Language: zh-TW
User Agent: Mozilla/5.0 (Linux; Android 16; PJW110 Build/BP2A.250605.015; wv) AppleWebKit/537.36 (KHTML, like Gecko) Version/4.0 Chrome/154.0.8037.0 Mobile Safari/537.36

If applicable, add mockups / screenshots regarding your vision

No response

If applicable, attach your Acode.log file to this issue.

Acode.log

Activity

  1. added theissue type on Sep 8, 2026
  2. moved this from Backlog to In progress in The Code Board - Acodeon Sep 10, 2026
  3. bajrangCoder commented on Sep 11, 2026

    @bajrangCoder
    Member

    Try updating your webview

  4. blanhhy commented on Sep 11, 2026

    @blanhhy
    Author

    Hi @bajrangCoder,
    I've already updated WebView and Acode, but the issue still persists.
    Current device info:
    WebView: 154.0.8037.22
    Acode: 1.13.4
    So it doesn't seem related to an outdated WebView.

  5. bajrangCoder commented on Sep 11, 2026

    @bajrangCoder
    Member

    Hi @bajrangCoder, I've already updated WebView and Acode, but the issue still persists. Current device info: WebView: 154.0.8037.22 Acode: 1.13.4 So it doesn't seem related to an outdated WebView.

    But I tried reproducing the issue on same webview version but i can't.

    If you can test then test this development build: #2864 (comment) (make sure to back up things)

  6. blanhhy commented on Sep 11, 2026

    @blanhhy
    Author

    @bajrangCoder
    Thanks, here are my further tests:

    • I installed the development version you provided — the issue still occurs.
    • Cleared the app cache — no change.
    • On a clean secondary user profile on the same device → the flicker/black screen does NOT happen.
    • I backed up settings from the affected profile and restored them on the clean profile → the issue still does NOT reproduce.

    It seems related to app local data.

  7. blanhhy commented on Sep 21, 2026

    @blanhhy
    Author

    @bajrangCoder I figured it out!!

    The culprit turned out to be the terminal data—after I reinstalled Acode and restored the original aterm_backup.tar, the issue was perfectly reproduced.

    I can now reproduce this issue 100% of the time.

  8. bajrangCoder commented on Sep 21, 2026

    @bajrangCoder
    Member

    @bajrangCoder I figured it out!!

    The culprit turned out to be the terminal data—after I reinstalled Acode and restored the original aterm_backup.tar, the issue was perfectly reproduced.

    I can now reproduce this issue 100% of the time.

    If you can then share that backup

  9. blanhhy commented on Sep 21, 2026

    @blanhhy
    Author

    @bajrangCoder
    There is no need to look at that backup anymore.

    I reproduced the issue using a completely empty (0-byte) tar archive—so the problem stems from the restoration process itself!

    See the video below:

    VID_20260921_203405_1.mp4

    what did i do in the video:

    1. uninstall and reinstall acode
    2. create an empty file as tar
    3. show no issue occured in clean acode
    4. restore then reatart acode
    5. the issue reproduced
  10. blanhhy commented on Sep 21, 2026

    @blanhhy
    Author

    Correct: even if i did nothing, this issue always occurs the second time i start acode. so completely not related to the terminal


    However, like I said before, when I just performed these actions on the secondary user profile on the same device, it was surprisingly fine.

    I completely don't understand. The former reproduces 100%, while the latter remains perfectly fine.

  11. blanhhy commented on Sep 21, 2026

    @blanhhy
    Author

    @bajrangCoder
    I find the truth.

    The webview variations_seed on my device triggers this issue.

    It is automatically copied by android system into the app_webview directory of acode when launched for the first time, and it always takes effect on the second launch. Some of the Chrome Finch experiments interfered with acode.

    After I moved this file out of that directory, the issue no longer occurred; then, when I put it back (keep the original owner & rwx permissions), the issue was perfectly reproduced.

    the seed: variations_seed.tar.gz

  12. blanhhy commented on Sep 22, 2026

    @blanhhy
    Author

    since it likely has nothing to do with acode itself, i think this issue can be closed now?

  13. RohitKushvaha01 commented on Sep 22, 2026

    @RohitKushvaha01
    Member

    since it likely has nothing to do with acode itself, i think this issue can be closed now?

    Thank you for debugging, most users don't even respond after submitting issues

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    Projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions