Note that there are some explanatory texts on larger screens.

plurals
  1. USadamacdo
    primarykey
    data
    text
    plurals
    1. This table or related slice is empty.
    1. COWhen we ran into the issue regarding the Task Manager I had to use some very iffy logic. First I created a BaseActivity class that all of my activities extended. I created a "navigateFromScreen" boolean that I would set to true each time I was switching the activities within the app and set to false OnCreate of the BaseActivity. OnPause I would check if the navigateFromScreen variable == false and if so I would restart the last activity I loaded (held by another global variable.) It worked to prevent switching to any other app, but it was a pain to fine tune.
      singulars
    2. COYour explanation did make sense, and it worked perfectly. There was only a little flicker from my main app to the home hijacker...but that is to be expected by switching apps. Upon start, I moved the hijacking app to the back, which helped reduce some of the flicker.
      singulars
    3. COI'm using Samsung Galaxy Tab's, the 7" version. I have a dual core, 2.2GHz i7. I get that they are slow now because I've attached many devices in the past, but I'm trying to find the solution to speed it up. Not having attached the devices to the computer isn't an option, as it has already been done. My question is how to return the speed to what it was. I assume the drivers for the older devices are still in memory somewhere, but after uninstalling all of the Android ADB drivers from Device Manager the detection process is still too slow.
      singulars
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload