Why was this change made to SocketInputBuffer for Ice Cream Sandwich?
Can anyone help me understand this "fix": https://www.gitorious.org/rowboat/external-apache-http/commit/e30b5b55806b31d1a61e2885b854dd7b8da1a07a It's causing my motion jpeg (mjpg, mjpeg) code to slow way down as I'm reading the jpg images. The fix seems horrible to me, completely ignoring the passed parameter and therefore giving the caller no chance to adjust the value. Is there a way to work-around the change so that I can use a larger buffer size?
From the commit log: Make Apache HttpClient play nice with large kernel socket buffers. Given the large maximum size likely to be set for kernel socket buffers on LTE devices, we need to stop Apache HttpClient from allocating some integer multiple of that size on the heap for each socket. On one device, 16 HTTP connections would fill the heap. This basically means that Android doesn't trust LTE devices to set their own buffer size, because it would fill the heap too quickly. As a workaround, try extending the AbstractSessionInputBuffer to create your own version of the SocketInputBuffer class.
Listview Android onClick defaul event
Android listview refresh only once
NFC card emulation
Android MediaRecorder Unlock API14+
Up Navigation not working
What size to store image on server to use with Android app
Apportable soundeffect delay
how to manage alarms of my alarm clcok applications
Navigation Drawer Activity
loading html file is showing error webpage is not available [closed]
Opening fragment from another activity with additional information
Android login registration with postgresql
How to access map tiles from external storage in PhoneGap?
Android difference betwen API: 19 Android 4.4 (Kitkat) and Google APIs (Google Inc.) (API 19)
Starting device gallery application from my application causes activity to call onCreate again?
Android Studio and Getting Maps Correctly installed