bads3ctor is the only user to have successfully gathered a Logcat dump to give definitive information regarding the "long-press and drag and drop" bug in this phone. Looking further into the issue and doing a little more reading, I don't think we've utilized Logcat to it's full potential and I also don't think the issue has anything to do with a broken digitizer or bad drivers (I suspect it's the way some firmware is compiled with the rom or kernel, ie: inputdispatcher.cpp)
Using the "Log" class in ADB can be scary to new users, but is a life line for devs to debug and fix errors, it essentially is Android's built-in bug-finder.
To learn a little more about what some of the Logcat "flags/switches" do you can read here:
Running Logcat (Advanced way)
and here
Flags
A developer at XDA, named Michael Perez, made an app to easily gather Logcat information (with many flags, and also supports kernel logging) specifically tailored to those of us who are not devs or power users.
This application is called "LogThis" and can be found at the Play Store here:
LogThis
In the attatched youtube video, it gives a description of how to run and how to create an output, according to Michael Perez, once the app is running it collects data for around ~10 minutes, just long enough to minimize the app, go to the homescreen and try to drag an icon around until the error manifests itself again, and then go back to the app to collect the log.
Using the "Log" class in ADB can be scary to new users, but is a life line for devs to debug and fix errors, it essentially is Android's built-in bug-finder.
To learn a little more about what some of the Logcat "flags/switches" do you can read here:
Running Logcat (Advanced way)
and here
Flags
A developer at XDA, named Michael Perez, made an app to easily gather Logcat information (with many flags, and also supports kernel logging) specifically tailored to those of us who are not devs or power users.
This application is called "LogThis" and can be found at the Play Store here:
LogThis
In the attatched youtube video, it gives a description of how to run and how to create an output, according to Michael Perez, once the app is running it collects data for around ~10 minutes, just long enough to minimize the app, go to the homescreen and try to drag an icon around until the error manifests itself again, and then go back to the app to collect the log.