Looks very hopeful/cool. But easily crashed entirely.

[whitedavidp]

My PC is Windows 10.

My phone is a rooted, A12, Moto XT2215-4. ScrCpy works quite reliably on it.

This app fires up, shows a desktop, and really looks hopeful/cool.

I added 2 of my apps to the desktop: Fossify Contacts and Next SMS. When I click either of them, the whole things crashes.

I am sure that achieving all this is NOT EASY. So not complaining, just reporting (and going back to ScrCpy for now).

Best!

[Shrey113]

Ohh thank you by more polite 😉 .... Yepp so many Android get same problem

Can you share a LOG file for it by run with cmd

"""
android_dex_win.exe --debugging
"""

... thta will gerate a "android_dex_log.txt" on root folder

[whitedavidp]

I am not being polite, just realistic. This is a very impressive and aggressive thing to try and pull off. If successful, it will be quite great!

android_dex_log.txt

I see a couple things:

1. The app I was trying to open is not shown/named. Perhaps it is because the crash happened before the log could be written?
2. The log says "Home screen tap: app.rvx.android.apps.youtube.music" and I never tapped any app like that. Later it says "Successfully connected for app.rvx.android.apps.youtube.music" and having never started the app, this is disconcerting in the extreme.
3. The log says "Connecting ADB to 192.168.29.102:5555..." This subnet/address is NOT on my LAN. What is this doing?
4. This installs an app on my Android (com.example.androiddex). At first, I did not see that on the main page but on other pages it is more explicitly stated. I can understand why that might be needed to accomplish this. Please let people know more explicitly about this.

Until this is all resolved, I will have to remove this from my machine.

Thanks

[Shrey113]

Nooo bro in 😅. Log it will show me my testing device name "OnePlus CPH2447 (Android 16)" that might be share with GitHub release but but

If you run my app with cmd

 android_dex_win.exe --debugging

... thta will gerate a "android_dex_log.txt" on root folder ....

Do like
1 - delete a old "android_dex_log.txt"
2 - open that my folder with cmd and run "android_dex_win.exe --debugging"
3 - you will see in my folder it will gerated agin "android_dex_log.txt" that you need to share

[whitedavidp]

Nooo bro in 😅. Log it will show me my testing device name "OnePlus CPH2447 (Android 16)" that might be share with GitHub release but but

If you run my app with cmd

 android_dex_win.exe --debugging

... thta will gerate a "android_dex_log.txt" on root folder ....

Do like 1 - delete a old "android_dex_log.txt" 2 - open that my folder with cmd and run "android_dex_win.exe --debugging" 3 - you will see in my folder it will gerated agin "android_dex_log.txt" that you need to share

I see now that there was such a file in the download. Ooppps!

I thought I issued the correct command but I have tried again after deleting the file and making sure I entered it correctly. It produces a file that makes more sense to me now. Sorry for being so dense. I am not sure there is much info in there to help however.

This try was with Next SMS. But I have had basically the same crash result with every app I have tried: Fossify Contacts, Next SMS, Samsung Internet, Thunderbird, Camera. If I try the included apps: Contacts, SMS, etc then I do not get immediate crashes.

android_dex_log.txt

[Shrey113]

I'm just a student and have a ton of tests and exams coming up. So, I'm going to take a break from coding for a few months. I'll be back soon! With all bug fix and somthing new
....

And also some google & Motorola device will not support by dex I found and as soon i will fix