PitsGetslotfrombufferlocked:unknown buffer:0xab7115e01. In the Cotton Candy (6.0) inexplicable unknown buffer error, Baidu a bit, it seems that this is Android6.0 bug??, so white busy, this pit can't fill up, and so Google to fill it 2. When using the Android Device Monitor tool, Tip:Could not open Selected VM Debug Port (8700), I rub?? This TM is what ghost, immediately after the author is again a data, the port is occupied http://www.lai18.com/content/2395135.html specific see this article 3. In the process of solving issue 2, there is an article to be resolved through DDMS (Device debug Monitoring service) configuration, see http://blog.csdn.net/wwzqj/article/details/37599437 This article, but the new version of Android Studio in preferences really can't find Android options ah??, just this time again to open Android device Monitor to see, the original DDMS was integrated here, the corresponding open Android device Monitor's preferences we see the Android option, go in and choose Ddms to make the appropriate changes. 4. In other words, why do I encounter the above three pits for no reason, in fact, when doing the paper read and write test of the problem, the first demo whether it is read or write will let the app stop running, and to data/data/package name/not appear in the book data/data/package name/ Files file, so I think is not the file read and write need permission to apply, it is obvious that after reading a few blog, not so, see http://blog.csdn.net/u012702547/article/details/50269639 this article for details. Then the author made a simplified version of the second demo by solving the above three problems, the successful completion of the file read and write operations.
2017-6-14 Pit Summary (Android file read and write related issues)
