Program crashes

[kleytr6s]

I am using the portable edition. I downloaded the VCRUNTIME140_1.DLL file and pasted it into the folder of the portable edition. Androiddrive crashes when I connect the phone. Also, I noticed in task manager there are 2 adb.exe (32 bit) processes. One is constant and the other terrminates and reappears every 1 - 2 seconds. I ran the command prompt listed in your instructions for phones not detected. The phone is a listed device.

AndroidDriveDebugLog20250708230625.log

[GustavLindberg99]

I would need more information to fix this. Could you do the following?

1. Unzip and open this file: LocalDumps.zip
2. Restart AndroidDrive
3. Reproduce the crash
4. Go to C:\Users\<your username>\AppData\Local\Temp\AndroidDriveCrashDumps in Windows Explorer
5. Attack the files that are in that folder to this issue (there will probably only be one .dmp file, but if there are several attach them all)

[kleytr6s]

It does not create a .dmp file. But, the debug log has more info.

AndroidDriveDebugLog20250722080748.log

[GustavLindberg99]

The debug log doesn't contain enough information. If you update to AndroidDrive version 2.4.4 it will show an error message if it crashes with some debug information. Could you attach that information?

[kleytr6s]

I have enabled USB Debugging, the phone is authorized. But, this message appears.

[GustavLindberg99]

You need to do as it says. Try unlocking your device. If it shows you a dialog asking if you want to allow this computer to access phone data, tap "Allow". If it doesn't show that dialog, disable and re-enable USB debugging. If it still isn't working, try unplugging and then re-plugging your device.

[kleytr6s]

I have followed those directions. When I open Windows File Explorer or AndroidDrive it crashes.

[GustavLindberg99]

If it crashes it will show you an error message like this but with different numbers:

If it does, please share those numbers.

If it doesn't, it's not a crash. The error message you posted earlier is not a crash, it's a warning that the device is unauthorized. AndroidDrive gets that information from ADB, so it's not an AndroidDrive bug.

[kleytr6s]

When I open the program or Windows Explorer it terminates/no longer listed in Task Manager. No error or crash windows appear.

[GustavLindberg99]

Are you sure you have the latest version?

[kleytr6s]

Yes, I were able to trigger an error window.

[GustavLindberg99]

Ok, I would need a stack trace to fix that. To get one, follow these instructions:

1. Download and install Qt Creator from here. In installation options, check both "Qt 6.9 for desktop development" and "Custom installation", then make sure that "Qt > Qt 6.9.1 > MSVC 2022 64-bit" is checked, as well as "Qt Creator 17.0.0", "CDB Debugger Support" and "Debugging Tools for Windows" under "Qt Creator".

2. Download and extract this zip file.
3. Open the sources/AndroidDrive.pro file with Qt Creator.
4. Make sure that "Debug" is checked, then click Configure Project:

5. Close AndroidDrive if it's currently running.
6. Click on the arrow with the bug on the bottom left. If it shows you a dialog box about missing debug information just click OK and don't worry about it. This will start Android Drive in debug mode (AndroidDrive might ask you if you want to install an update, if it does click No).

7. Reproduce the crash.
8. Instead of crashing, it will show a dialog saying "Exception Triggered", and the debugger in Qt Creator will show a bunch of information. Click OK, then send me a screenshot similar to the one below:

[kleytr6s]

no compiler set in kit. how do i fix it/which do i choose?

[GustavLindberg99]

You need to download the MSVC compiler from https://visualstudio.microsoft.com/downloads/:

1. Choose "Community" under "Visual Studio 2022":

   

2. Open the downloaded .exe file and wait for it to download the installer.

3. Scroll down and select "Desktop development with C++":

   

4. Click "Install".

5. Restart Qt Creator, then Qt Creator should auto detect the compiler.