Jump to content
Sign in to follow this  
cosote

LeapDroid support

Recommended Posts

1 hour ago, ardalan12 said:

Well tnq zer0god  ifix  every think    .   infrasonic  try this                    mybot.run profilename leapdroid vm2   and mybot.run profilename leapdroid

im boting easy now but  somting worng   after  15 + 20 min some time s more  leapdriod  get a  some random error ucant click on anythink in game and you must reset full leapdroid any idiea  what i do? even bot cant click any think but can zoom out.

 

" mybot.run profilename leapdroid vm2 " where profilename is mybotrun profile? For example village1, and so on?

 

I do not have any freeze or error problems with leap droid so far 14 hours online non stop.

Share this post


Link to post
Share on other sites
2 hours ago, dharyadi said:

any one having issue with zoom out ?

and

LeapDroid cannot use ADB for mouse events, "qwerty2" not found

 

 

11 minutes ago, ahsan iqbal said:

same here stuck at zoom out

 

 

Share this post


Link to post
Share on other sites

MEmu and LeapDroid , running first the MEmu : LeapDroid error :) 

AMD-V is being used by another hypervisor (VERR_SVM_IN_USE).

VirtualBox can't enable the AMD-V extension. Please close all other virtualization programs. (VERR_SVM_IN_USE).

jqU4TnP.png

  • Upvote 1

Share this post


Link to post
Share on other sites

Hi guys,

 

I'm back from a beautiful vacation :D

I think I do remember LeapDroid has some issues with AMD processors :( 

They released now 1.7.0 ... before my vacation I've tested that 1.6.1 was running fine with bot and keyboard issues resolved with vm3 and more instances...

here some commands to clone instances (make vm3-vm6 from vm1, last commands just change the cpu count and memory to 512 MB, oh, and change vboxmanage to your program files folder you've installed LeapDroid):

"D:\ProgramData\LeapDroid\vboxmanage" clonevm vm1 --name vm3 --mode all --register
"D:\ProgramData\LeapDroid\vboxmanage" clonevm vm1 --name vm4 --mode all --register
"D:\ProgramData\LeapDroid\vboxmanage" clonevm vm1 --name vm5 --mode all --register
"D:\ProgramData\LeapDroid\vboxmanage" clonevm vm1 --name vm6 --mode all --register
"D:\ProgramData\LeapDroid\vboxmanage" guestproperty set vm3 adb_port 5530
"D:\ProgramData\LeapDroid\vboxmanage" guestproperty set vm4 adb_port 5540
"D:\ProgramData\LeapDroid\vboxmanage" guestproperty set vm5 adb_port 5550
"D:\ProgramData\LeapDroid\vboxmanage" guestproperty set vm6 adb_port 5560
"D:\ProgramData\LeapDroid\vboxmanage" modifyvm vm3 --cpus 1 --memory 512
"D:\ProgramData\LeapDroid\vboxmanage" modifyvm vm4 --cpus 1 --memory 512
"D:\ProgramData\LeapDroid\vboxmanage" modifyvm vm5 --cpus 1 --memory 512
"D:\ProgramData\LeapDroid\vboxmanage" modifyvm vm6 --cpus 1 --memory 512

There's a tricky problem with ADB connections :(

BlueStacks has a similar, but "the other way" around... meaning: In multi Android installations, MEmu + BS2 + ... , BlueStacks2 ADB only connects when ADB Daemon is started after BS.

This is already done by the bot. Now, LeapDroid is the other way around and not yet handled by the bot... in order to run LeapDroid, the ADB Daemon must be launch prior to the LeapDroid.

Bad, because the bot restarted currently ADB Deamon quite often when there's a ADB connection problem... and then LeapDroid fails to connect until all LeapDroid's are closed and all are started again.

Will address that in next release somehow ;) Reported bug to LeapDroid team, but have not received any feedback yet...

 

Cheers - Cosote.

Edited by cosote
  • Upvote 4

Share this post


Link to post
Share on other sites

=============================== BOT LOG ===============================
[7:02:40 PM] LeapDroid Background Mode is not available
[7:02:49 PM] LeapDroid Background Mode is not available
[7:02:50 PM] Starting LeapDroid and Clash Of Clans
[7:02:52 PM] Please wait while LeapDroid and CoC start...
[7:03:41 PM] LeapDroid Loaded, took 49.16 seconds to begin.
[7:03:44 PM] LeapDroid (vm1) running in window mode
[7:03:44 PM] LeapDroid window resize didn't work, screen is 860 x 537
[7:03:45 PM] LeapDroid Background Mode is not available
[7:03:46 PM] LeapDroid ADB script file folder doesn't exist:
[7:03:46 PM] Pp\
[7:03:46 PM] MyBot doesn't work with LeapDroid screen resolution of 860 x 537!
[7:03:46 PM] Set LeapDroid Display Font Scale to normal
[7:03:47 PM] Stopping LeapDroid....
[7:03:47 PM] Please wait for full LeapDroid shutdown...
[7:03:53 PM] Failed to stop LeapDroid
[7:03:54 PM] Set LeapDroid screen resolution to 860 x 732
[7:03:55 PM] LeapDroid Background Mode is not available
[7:03:55 PM] A restart of your computer might be required
[7:03:55 PM] for the applied changes to take effect.
[7:03:56 PM] LeapDroid Background Mode is not available
[7:03:56 PM] Starting LeapDroid and Clash Of Clans
[7:03:58 PM] Please wait while LeapDroid and CoC start...
[7:04:18 PM] LeapDroid (vm1) running in window mode
[7:04:21 PM] LeapDroid Loaded, took 23.12 seconds to begin.
[7:04:21 PM] LeapDroid window resize didn't work, screen is 860 x 537
[7:04:22 PM] LeapDroid Background Mode is not available
[7:04:23 PM] LeapDroid ADB script file folder doesn't exist:
[7:04:23 PM] Pp\
[7:04:23 PM] MyBot doesn't work with LeapDroid screen resolution of 860 x 537!
[7:04:23 PM] Set LeapDroid Display Font Scale to normal
[7:04:24 PM] Stopping LeapDroid....
[7:04:24 PM] Please wait for full LeapDroid shutdown...
[7:04:29 PM] Failed to stop LeapDroid
[7:04:30 PM] Set LeapDroid screen resolution to 860 x 732
[7:04:31 PM] LeapDroid Background Mode is not available
[7:04:31 PM] A restart of your computer might be required
[7:04:31 PM] for the applied changes to take effect.
[7:04:31 PM] LeapDroid Background Mode is not available
[7:04:32 PM] Starting LeapDroid and Clash Of Clans
[7:04:34 PM] Please wait while LeapDroid and CoC start...
how fix that??????????

Share this post


Link to post
Share on other sites

Hi,

 

@myapp If you have installed LeapDroid 1.7.0, go back to 1.6.1 and set manually the screen in LeapDroid to 860x732, 160 DPI.

Support for LeapDroid 1.7.0 and automatic screen adjustment fix for 1.6.1 and 1.7.0 will be available in next release :)

 

Cheers - Cosote.

Edited by cosote

Share this post


Link to post
Share on other sites
3 ساعات مضت, cosote said:

Hi,

 

@myapp If you have installed LeapDroid 1.7.0, go back to 1.6.1 and set manually the screen in LeapDroid to 860x732, 160 DPI.

Support for LeapDroid 1.7.0 and automatic screen adjustment fix for 1.6.1 and 1.7.0 will be available in next release :)

 

Cheers - Cosote.

that error with out fix files to

Share this post


Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Sign in to follow this  

×
×
  • Create New...