Getting a HandlerThread. (Android Performance Patterns Season 5, Ep. 5) December 13, 2019 16 By Peter Engel CategoryArticles BlogTagsandroid app application applications asynctask fullname: Colt McAnlis GDS: Full Production Google handlerthread how howto instructions intentservice lecture lesson Location: MTV memory Product: android Team: Scalable Advocacy threading threadpool to tutorial Type: DevByte 16 Comments Jubin Mathai says: March 22, 2016 at 5:12 pm I've got to learn the art of Threading 👍😊Thanks for the tip Reply Cristopher Torres says: March 22, 2016 at 7:45 pm My Lg Optimus L90 Lags. Please Help. Reply Ahmed Hegazy says: March 22, 2016 at 10:46 pm We need a blog post assigned to each video of those to describe the patterns you're talking about. This will help so much. Reply Igor Ganapolsky says: March 22, 2016 at 11:39 pm You talked about setting priority for the HandlerThread. But how do we, devs, decide which priority is right for our thread? Reply Ronaldo Pace says: March 23, 2016 at 9:10 am wrong information on this video. It says that AsyncTask is great for 99% of the cases, but it's something it is only useful for 'HelloWorld' on real world cases it barely ever applies and even was mentioned before by Ian or Reto in some of their videos (or was podcast?) Reply TLCM says: March 23, 2016 at 12:37 pm I had this loader calling a postMessage from a handler in the onLoadFinished callback. The handler commits a new fragment to the activity, and I was receiving a: "You cannot perform this operation in onLoadFinished callback" . Is this the right approach? , or where would be the right place to handle the fragment transaction after onLoadFinished. Reply HOUSSEM ZAIER says: March 23, 2016 at 1:29 pm I used to use Handlers/Messages to communicate between Threads but when my app is getting larger this get harder to scale is there any better tool for sending data between threads ? Reply Rafael Monico says: March 24, 2016 at 7:07 pm Come back to meth Heisenbergh! Reply Greg Ennis says: March 25, 2016 at 4:21 pm I would not say that AsyncTask is good for "99%" of threading needs. In fact I would rather see it's usage discouraged. For example, showing loading an image using AsyncTask is putting people down the wrong path. App developers should be using libraries like retrofit, glide, dbflow, priority-job-queue, etc., that offer ability to do just about anything that shouldnt be done on the UI thread. Every time I see a code base with AsyncTask all over the place I know we've got trouble. Reply Renam Philippi Antunes says: March 25, 2016 at 9:04 pm "99% of your thread work AsyncTask is the right solution" 4Head Reply Piotr Mądry says: March 26, 2016 at 3:35 pm RxJava is much easier to work with. And do the work right Reply jaskaran singh says: March 27, 2016 at 4:38 pm I want to start learning app development but I don't know from where to start.So could u guys suggest me in this field??? Reply David Hwang says: March 28, 2016 at 11:14 pm 3:01 Yikes, primitives might herp me? Time to get paranoid. 😀 Reply RAVIRAJ DARISI says: November 29, 2016 at 1:35 pm As per my understanding, u can run many instances of asynctasks at a time using thread pool configuration, but you are telling all asynctasks requests will be running serially on asingle thread, could somebody clarify more on this,,, Reply omkar kulkarni says: March 3, 2018 at 7:27 am Thankyou So Much It Really Helped !! i was stucked with my performance issues but now i am good to go thankyou so much Reply Prashanth Wagle says: July 14, 2019 at 11:01 am Most of the articles didn't help me.A single 3 minute video has proven to be effective.Thanks Android Developers! Reply Leave a Reply Cancel reply Your email address will not be published. Required fields are marked *Comment Name * Email * Save my name, email, and website in this browser for the next time I comment.