Quest v51 Events not working

[alexyao2015]

It seems that as of the v51 update for Oculus headsets, drag events are not functioning for whatever reason. Specifically, this is not working. It seems that starting drag and drop doesn't send events. Touch events up are also not being sent.

It seems like the best option would be to add a simple drop down menu instead of drag and drop.

PiLauncherNext/Launcher/App/src/main/java/com/veticia/piLauncherNext/ui/AppsAdapter.java

Line 168 in 497ee60

view.startDragAndDrop(dragData, shadowBuilder, view, 0);

[Veticia]

If someone knows the underlying reason or is familiar with an quest's accepted workaround / preferred method for handling drag and drop it would be appreciated.

I'm not yet willing to to make it a drop down menu if there is a more elegant way of doing this, but may eventually have to do it if no other options are possible.

[alexyao2015]

You don't need to remove the drag and drop functionality. You can just add a drop down menu to the long press on the app outside of editing mode (the drag and drop long press doesn't work) as a temporary fix so it's at least usable.

[Thoms04-source]

It would be pretty epic if there is a workaround. Cuz like Alexyao I need to move games/apps to the correct folders in order to make sense of my library, and atm that functionality isn't working. As of v51 oculus the device is on android 12. Android 12 includes a new drag and drop API.

Chatgtp gave me 2 suggestions that might be worth to check out.

1.The new API requires that you explicitly set a drag start point using startDragAndDrop() method. In the startDragAndDrop() method, you can set the x and y offset to zero.
Example:
view.startDrag(dragData, shadowBuilder, view, 0);
to
view.startDragAndDrop(dragData, shadowBuilder, view, 0, 0, 0)

2. Chatgtp response: ' One possible reason why drag and drop functionality might have stopped working after upgrading to Android 12 is that the operating system has introduced changes to the way touch events are handled. Specifically, Android 12 introduces a new feature called "Touch Accommodation" which can impact drag and drop behavior.
   To fix the issue, we can try adding a touch listener to the view that allows for drag and drop.

Note: I am a product manager, not a developer, so above are just suggestions that might help you forward and they might not :)

[Veticia]

@Thoms04-source

The new API requires that you explicitly set a drag start point using startDragAndDrop() method.

It would be nice to get to the source of that information. No source I could find mention anything like that changing.

[Veticia]

I've tried to run it on emulator on android 12 (api 31), 12L (api 32) and even android 13 on real hardware (api 33) and drag-and-drop still works fine. Must be an issue with quest specifically. Does drag and drop work in other apps (no piLauncher derivatives)?

[alexyao2015]

Yeah honestly I built a couple different variations to try it on there including trying startDragAndDrop and looking for motion up events and both were not working... I'll see if I can find something else, but a drop down menu would be a nice to have even if we do get the drag and drop working again. It would also be better than my current workaround of manually editing the shared preferences xml (huge pain btw).

I found one option that might work which is using androidx drag and drop but not too hopefully since those are just overlays on the base API.

[niktn10]

For me, this is also a big problem. It would be great if this could be fixed somehow.

[niktn10]

manually editing the shared preferences xml

How do you do it? How can I access this file and where is it located? In the absence of other options, I would use this one.

[alexyao2015]

You can use adb backup, extract, edit, repackage, restore. The second option is to use run-as to execute in the shell of the package. Then execute vi from toybox to edit the preferences. Honestly both options are extremely technical and not exactly easy to do for a normal user. The second option is slightly easier.

[JarJarBlinkz]

This is what is happening when starting drag and drop i have also raised this with oculus as i think you are correct that it is purely oculus related and only started doing this after upgrade to v51 ptc release of android 12 also has the same issues with dreamgrid and pi launcher but all seem to work fine on android 10 v50 public release

https://youtube.com/shorts/6WWX51ascIk?feature=share