StupidIdea said:

Hi,

I saw no point in maintaining the app when stock Android removed navigation bar and added gestures. Add rooting struggles and you get the picture. I felt over-burned from fighting new Android restrictions in every release. I removed XDA and my dev mail account from my phone and moved on. I abandoned my dream to make a living as indie dev. On the other hand I'm doing great as a java dev in a big company. I'm ok.

As you have noticed I removed all my apps from Play Store a couple months later too. It only took this long because I literally had to fix all "required" promotion materials before it allowed me to remove the apps.

Play store still shows ~600 installs of full version and ~800 installs of free version.

Please do not collect bounty. I cannot promise anything. My Pixel 2 is not rooted and I haven't used Android SDK for years. I want to fix small/simple bugs so you can use the app as long as it work but I need to review the situation first.

Wow I'm surprised you guys are still using it with Android 11.

Click to expand...

daddyc said:

Have you found any solution for apps not launching with gesture without using tasker?

you can use almost any app that makes shortcuts

It works perfect for me, but after 15 minutes the gestures start working with a delay of 5 seconds or more... android 13, galaxy S21

daddyc said:

Have you found any solution for apps not launching with gesture without using tasker?

fedex_742 said:

you can use almost any app that makes shortcuts

It works perfect for me, but after 15 minutes the gestures start working with a delay of 5 seconds or more... android 13, galaxy S21

I use it on Android 13 on Samsung Galaxy s23 ultra.

Basically the app works. The most important from it works:
- it perfectly detects the screen
- it perfectly detects the borders
- it perfectly registers the gestures
- zones are also working as trey should

So the main engine is operational.

It needs so little work to become Android 13 fully compatible.

It is true that its service gets killed after some time. That is why I used Tasker to kill GMD and start it again (hidden from recent apps) and going back to the previous app (alt+tab) upon every screen unlock. This way I don't even see that GMD is restarted when I unlock my phone.

Also GMD doesn't detect keyboard up/down now too.

The rest I was able to make work with Tasker.
- Kill current app
- Alt+tab
- Open apps
- Back
etc

Again, gesture implementation and registering works fine. This is the core of the app. Therefore I am sure it needs only little work to get it back to original.

I hope @StupidIdea would bless us with his grace. It wouldn't hurt him so much. And he would make people who supported him happy...

tiho5 said:

I use it on Android 13 on Samsung Galaxy s23 ultra.

Basically the app works. The most important from it works:
- it perfectly detects the screen
- it perfectly detects the borders
- it perfectly registers the gestures
- zones are also working as trey should

So the main engine is operational.

It needs so little work to become Android 13 fully compatible.

It is true that its service gets killed after some time. That is why I used Tasker to kill GMD and start it again (hidden from recent apps) and going back to the previous app (alt+tab) upon every screen unlock. This way I don't even see that GMD is restarted when I unlock my phone.

Also GMD doesn't detect keyboard up/down now too.

The rest I was able to make work with Tasker.
- Kill current app
- Alt+tab
- Open apps
- Back
etc

Again, gesture implementation and registering works fine. This is the core of the app. Therefore I am sure it needs only little work to get it back to original.

I hope @StupidIdea would bless us with his grace. It wouldn't hurt him so much. And he would make people who supported him happy...

Click to expand...

It definitely depends on the ROM, because on my tablet with crDroid Android 13 nothing actually works, whatever I change in settings

Lord Sithek said:

It definitely depends on the ROM, because on my tablet with crDroid Android 13 nothing actually works, whatever I change in settings

My advice is to make s gesture that gives a toast. Then play with device setup and start changing manually the settings there until you find a working combination. The toast is going to show if/when touch events are registered.

tiho5 said:

My advice is to make s gesture that gives a toast. Then play with device setup and start changing manually the settings there until you find a working combination. The toast is going to show if/when touch events are registered.

Belive me, I've tried every combination

tiho5 said:

I use it on Android 13 on Samsung Galaxy s23 ultra.

Basically the app works. The most important from it works:
- it perfectly detects the screen
- it perfectly detects the borders
- it perfectly registers the gestures
- zones are also working as trey should

So the main engine is operational.

It needs so little work to become Android 13 fully compatible.

It is true that its service gets killed after some time. That is why I used Tasker to kill GMD and start it again (hidden from recent apps) and going back to the previous app (alt+tab) upon every screen unlock. This way I don't even see that GMD is restarted when I unlock my phone.

Also GMD doesn't detect keyboard up/down now too.

The rest I was able to make work with Tasker.
- Kill current app
- Alt+tab
- Open apps
- Back
etc

Again, gesture implementation and registering works fine. This is the core of the app. Therefore I am sure it needs only little work to get it back to original.

I hope @StupidIdea would bless us with his grace. It wouldn't hurt him so much. And he would make people who supported him happy...

Click to expand...

I thought tasker was for making the shortcuts work, but it makes sense that you can revive the app every 15 minutes... do you have a screenshot of the script you use to kill and revive the service in tasker?

I'm going to try to make it work myself anyway.

The only thing that scares me a little is the impact it may have on the battery.

But I think it's worth it, this application makes my life easy.
Thank you very much for answering.

fedex_742 said:

The only thing that scares me a little is the impact it may have on the battery.

Didn't notice any.

Just tell Tasker event unlock to kill GMD wait 200 ms and start it again. You can also apply go home action after GMD started or even go to the previous app (alt tab).

tiho5 said:

Didn't notice any.

Just tell Tasker event unlock to kill GMD wait 200 ms and start it again. You can also apply go home action after GMD started or even go to the previous app (alt tab).

Can I do the same with macrodroid? Doesn't want to buy tasker just for this

daddyc said:

Can I do the same with macrodroid? Doesn't want to buy tasker just for this

I am not familiar with macrodroid, but I think a shortcut to any app that can provide shortcuts to actions is ok.

tiho5 said:

Didn't notice any.

Just tell Tasker event unlock to kill GMD wait 200 ms and start it again. You can also apply go home action after GMD started or even go to the previous app (alt tab).

Im really dumb I finally made it work with shortcuts. By the way, to launch GMD service in background, you can use this in Run Shell action:
am startservice -n com.goodmooddroid.gesturecontrol/com.gmd.gc.BackgroundService

Lord Sithek said:

Im really dumb I finally made it work with shortcuts. By the way, to launch GMD service in background, you can use this in Run Shell action:
am startservice -n com.goodmooddroid.gesturecontrol/com.gmd.gc.BackgroundService

That's huge, because restarting the app when unlocking the phone takes me out of the game that I play... thanks I'm going to try it in tasker to see if it works for me

fedex_742 said:

That's huge, because restarting the app when unlocking the phone takes me out of the game that I play... thanks I'm going to try it in tasker to see if it works for me

I have set a profile in Tasker with kills GMD and restart it at once in background on Display On. So far so good, I'll be monitoring this