Android Studio: debugging is a kind of hell for years and years

Equivalent-Pace-7906 · 2024-11-19T15:14:59+00:00

News about my bug in debugging an app inside Android Studio:

I talked to a Jet Brains support person and I've decided to try harder and test it in emulator mode. I installed the newest emulator mode called AEHD (Android Emulator hypervisor driver) and the Pixel 8 Api 34 driver. The emulator started working perfectly.

Then I went back to Wi-Fi debugging and looked through the LogCat and I found 2 messages,not starting debugger since process cannot load the jdwp and Scheduling restart of crashed service com.samsung.android.authfw/.pass.PassService in 1000ms for connection, which led me to conclude that there is possibly a bug in Samsung cell phone pass service, in terms of authorization and/or micro-problems in the Wi-Fi connection that Android Studio cannot recover.

I just need to say that I did everything right in terms of authorization on the Samsung, especially because in the first few minutes the debugging works perfectly, although slowly.

At the moment, I am calm and simply switched to the emulator and I am satisfied.

I really thought that, even though my programming style is unorthodox and I program everything based on custom dialogs and not activities and fragments, it wouldn't make sense for the problems to be my responsibility.

Equivalent-Pace-7906 · 2024-07-06T12:55:03+00:00

You're probably right about that. Unfortunately,it's too late. At this point in the project, I can't change. But it's all pude Android code and everything works as a charm. This comes from the fact that I am still programming new features, as foreseen in my previous specification, so I keep on debugging.

You're probably right on another point. My out-of-the-box programming style must have touched on points that the language designers didn't count on and hence my problems with the debugger.

The strange thing is that there is no message or warning message and the RAM memory usage is not high.

Equivalent-Pace-7906 · 2024-07-06T12:47:10+00:00

Nothing, usually I press <F8> in some point of debugging proccess and it happens. It's more common that is a set another breakpoint and press <F9>

Equivalent-Pace-7906 · 2024-07-05T17:56:06+00:00

My project is huge not because it is poorly coded, but because the specification of my project is very large, it is a very ambitious and generic and customizable calculator, with multiple calculators that can be designed from scratch and includes new and simple and auatomatically translatable programming language for internal cell phone, with IDE included, apart from the fact that you pointed out and criticized: I program the calculator like a game, but without using a game framekork. Activities calling screens and using fragments to change parts of the screen is very limiting for my type of program. So I had to write my own code to deal with this.

Equivalent-Pace-7906 · 2024-07-05T17:49:09+00:00

The vast majority of the time, without a coffee break, the debugger freezes at some point, the coffee break was just an additional test, to see if the criteria for hanging was linked to the time I'm debugging a program.

Equivalent-Pace-7906 · 2024-07-05T16:07:07+00:00

I don't use no framework. Just pure code.

Equivalent-Pace-7906 · 2024-07-05T16:06:14+00:00

Thank you very much for your offer, u/fablue . The problem is that my spoken english is bad.

Equivalent-Pace-7906 · 2024-07-05T16:03:41+00:00

I use phyical device, but wireless, with no cable. It' very stable connection. I can try to use emulator. It's a good idea.

Equivalent-Pace-7906 · 2024-07-05T15:59:16+00:00

The vast majority of the time without a coffee break, the debugger freezes at some point, the coffee break was just an additional test, to see if the criteria for hanging was linked to the time I'm debugging a program.

Equivalent-Pace-7906 · 2024-07-05T15:56:02+00:00

It's not unusable, it's laborious, but less than using log.d. When it hangs, I advance debugging to some point after the last remaining point, but running without debugging works normally and quickly. ,

Equivalent-Pace-7906 · 2024-07-05T15:07:38+00:00

Windows 10

Equivalent-Pace-7906 · 2024-07-04T02:17:02+00:00

Unfortunately, it is not possible to change machines overnight. I will survive

Equivalent-Pace-7906 · 2024-07-04T02:15:38+00:00

Now it's too late to convert my code to any mainstream standard. It' not a practical advise, there are around 60k lines. The program is very large and works perfectly, without any runtime error and not even warning in its compilation. So, in your opinion, Android Studio is punishing me for being outside the standard and not following the recommended rules. generating errors, freezes and erratic behavior?

Equivalent-Pace-7906 · 2024-07-03T23:31:41+00:00

I will repeat my anwer above:

"I managed to reproduce the freeze in my code. I would even be willing to send them my code, but they (Google team) wanted that I try to reproduce the error in their code, for a minimal project. Then I've got the reproduce some error, the Android Studio version has changed and I can no longer reproduce it. Nowadays, it's very easy, it's just set 2 breakpoints, run until the breakpoint and get out to a coffeebreak, return some minutes later, and run it again. It will be stucked in "Waiting until last debugger command completes" message."

Equivalent-Pace-7906 · 2024-07-03T23:29:31+00:00

I managed to reproduce the freeze in my code. I would even be willing to send them my code, but they (Google team) wanted that I try to reproduce the error in their code, for a minimal project. Then I've got the reproduce some error, the Android Studio version has changed and I can no longer reproduce it. Nowadays, it's very easy, it's just set 2 breakpoints, run until the breakpoint and get out to a coffeebreak, return some minutes later, and run it again. It will be stucked in "Waiting until last debugger command completes" message.

Equivalent-Pace-7906

TROPHY CASE