I am missing the point of this post.
Are you saying that there is no solution?
If so, what do you suggest? Just stop developing for Android?

When I say "not aware of that", I mean that it doesn't show up as a 
practical solution from the eyes of developers.
Maybe they're aware of that and do internal meetings and discussions about 
it, but it's not something that I know of.

On Wednesday, July 31, 2013 5:43:42 PM UTC+3, a1 wrote:
>
> 1. Share and find some practical solutions, if there are any.
>>
> There isn't any, for some specific use cases (games) best solution is to 
> use higher level API (game engine).
>
> 2. Bring the seriousness and span of this issue to Google's attention - as 
>> there seems to be complete ignorance and self-delusion regarding it.
>>
> And you are saying that because of what exactly?
>  
>
>> So far I haven't seen any official Google source admit that this issue 
>> even exists, or provide any practical way of dealing with it.
>>
> There is no practical way of dealing with it (except of on device basis 
> which, according to you, isn't practical), if you search this group and 
> stackoverflow you will find several examples where Android team engineers 
> talk about device bugs so I really have no idea why you think they aren't 
> aware of that, moreover anyone who has ever work with J2ME is more than 
> aware that avoiding this is impossible (and J2ME was few orders of 
> magnitude worse due to differences in underlying OSes, drivers, CPU 
> architectures etc).
>
> --
> Bart
>

-- 
-- 
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
--- 
You received this message because you are subscribed to the Google Groups 
"Android Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
For more options, visit https://groups.google.com/groups/opt_out.


Reply via email to