[BUG] Chromium not found while running the pre-backed image

[timoa]

Describe the bug
Hi 👋
Thanks for this project! I tried using Ubuntu 26.04 LTS, and I was able to launch the pre-backed image, run adb commands, and see that adb devices showed I was connected.

I let Hermes Agent, using the Deepseek v4 Pro LLM, interact with the Docker image to test a URL blocked by Datadome, but it said that Chromium or Chrome app was not found by Damru on the Android device.

The agent has been able to use the default WebView with a few Websites, but the one protected by Datadome failed to pass since it doesn't use the Damru patches.

To Reproduce
Steps to reproduce the behaviour:

1. OS / Environment: Ubuntu 26.04
2. Damru Mode: Auto
3. Target Site/Script:
4. See error

Expected behaviour
I was expecting to find the Chromium browser installed (maybe the pre-backed Android image doesn't have Chromium installed by default, and I have to run more commands to get it?)

Screenshots/Logs
I will try to get more logs

Additional context

[akwin1234]

No worries. A new more stable & easy to use version is coming soon, may be by tomorrow (may be). but please answer something for me.

1. Chromium or Chrome app was not found by Damru on the Android device.

what was exactly error in python with debug mode on? Did you provide APK path to damru?

2. can you please specify you were using which website for Dat@dome so I can cross check and launch patch accordingly?

3. also did you verified if, IP was not already banned on dat@dom site you mentioned? Akam@i and Dat@dom works fine unless the IP itself is preflagged. these 2 patch rotating residentials also by sensing IP behaviour across all of their clients.

4. was all patching successful to redroid or was there any issue?

[timoa]

Don't worry!
To be honest, I followed the steps in the README until ADB found the device in the list with the command adb devices. After that, I left it to a Hermes Agent, and it started trying to connect and follow the README. I think it pre-flagged my IP right away after it tried using the WebView because it couldn't find the Chrome or Chromium app installed.
I will try again with a clean image from the Drive and see if I can launch Damru.
Thanks for your time! I'll follow your repo for future updates in the meantime.

[akwin1234]

Don't worry! To be honest, I followed the steps in the README until ADB found the device in the list with the command adb devices. After that, I left it to a Hermes Agent, and it started trying to connect and follow the README. I think it pre-flagged my IP right away after it tried using the WebView because it couldn't find the Chrome or Chromium app installed. I will try again with a clean image from the Drive and see if I can launch Damru. Thanks for your time! I'll follow your repo for future updates in the meantime.

yeh that seems like it. IP is only thing thats biggest con again dat@dom or akam@ia
while making damru without rotating residential with large pool they both gave me a lot of pain due to IP.
i am making auto setup everyting future and remove image dependacy or make it optional too. stay tuned hopefully all works.
regarding chrome issue damru needs path and i think its missing in python code. it will be stable too soon. in 1-2 days. stay tuned

[akwin1234]

@timoa a major update has been pushed, Please try now. things should be way stable now, read the readme again. if you still face same issue again let me know. package is now transformed