paimon-moe VS termux-adb-fastboot

Your pulls are simulated (with odds gathered from paimon.moe) 100.000 times.

because furina's C2 had the highest % drop rate an among all characters in paimon.moe's data (more that raiden and nahida) and furina's C2 is for characters who want a universal buffer that doesn't depend on the field character's HP% fluctuation and furina can go with everyone's favorite ST healer, which is bennet.

Paimon.moe has a wish tracker that can do that.

According to paimon.moe, I'm more unlucky than about 90% of people, wishing on the character banner. FML

I just lost my 50/50 to Qiqi 20 minutes ago, and I noticed it's not showing up in my wish history. In fact, none of my wish history has registered for the last 4 days. I still have Qiqi and all the other 4 star characters I've pulled since then. Is this a glitch??? I've never had this problem before. Not even the paimon.moe wish counter can pick it up.

paimon.moe you can upload your wish history to it. Avg amount is entirely luck dependent but you can use https://qiqisfather.github.io/universal_roll_simulator/ to get a simulation of how your pulls may go.

That's the one I've been using lol. i used paimon.moe to get the file and just used it on this site because the link on the site seems to just not been working and all my info is on this one

I think it falsely warning since paimon.moe use script to get ur pulling info and anything that is 3rd party software (script) is consider dangerous for any antivirus software

Using only the device itself (you will need to be connected to wifi for this to work, these instructions are hot garbage): Install Termux from F-Droid. In termux install platform-tools adb/fastboot. Then Enable Wireless ADB, Settings-> System -> Developer Options -> Wireless Debugging, turn the slider to on, then get the port number from the Wireless Debugging sub menu get the port number. (Remember to turn off Wireless Debugging when done!). In Termux run adb connect localhost:PORT then check adb devices you should see an authorization prompt for a debug connection, you'll need the connection challenge code from settings (this authorization only needs to happen once). Then adb shell and run one of the commands below.

Termux for the help install in termux this: https://github.com/rendiix/termux-adb-fastboot pair your localhost:port with termux's adb connect to it and run adb shell wm size [Xres]x[Yres] -d [display number]

Just a heads up for anyone reading that tries this and finds it doesn't work: in the comments /u/-korni- linked to an alternative version of adb and I found that fixed the problem for me and the task works again.

There is a known bug with Samsung devices and the version of android-tools included in the repo. You have to use a different version of ADB to getaround the issue with the server not running right, I personally use https://github.com/rendiix/termux-adb-fastboot on my A32 5G. Not sure if others like termux-ADB work.

This one works; https://github.com/rendiix/termux-adb-fastboot

newest binary