On 03/28/2012 09:50 PM, Irfan Sheriff wrote:
On Wed, Mar 28, 2012 at 8:28 AM, Kostya Vasilyev <[email protected]
<mailto:[email protected]>> wrote:
When the connectivity changes, some (it seems most) firmwares
force-close any currently open connections, but some do not (two
examples: Motorola Milestone with 2.1, and a much more recent HTC
Incredible S with 2.3...).
We have had fixes around resetting connections with
connectivityservice controlling it now.
That the connecitons are not getting reset on an old Motorola Milestone
is understandable, it's really old.
Seeing the same on an HTC Incredible S with the latest 2.3 firmware is
quite amazing, especially since its twin brother HTC Desire S properly
resets connections.
So while I appeciate your response and the fact that some work has been
done in this area, it does not help much for existing devices.
It would be good to know if there are devices beyond ICS that still
have issues around not resetting socket connections when a network
goes away.
Beyond ICS? I don't know what this means.
My "flagship" Galaxy Nexus still hasn't received 4.0.3.
And what do you mean by "would be good to know"?
Should we, developers, and our users, moonlight as Android's test
department?
Ideally, apps should not have to listen to any broadcasts to handle
network switches and should get resets on an existing socket.
Not ideally -- really -- apps are supposed to work on more than the 1.6%
of devices with ICS.
And "beyond ICS" - what portion of the market is that, at this time,
exactly?
-- K
Irfan
--
You received this message because you are subscribed to the Google
Groups "Android Developers" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/android-developers?hl=en
