I don't have a multicore phone. I'm from Romania. I don't think that they introduced multicore phones here and even if they did the price is prohibitive. I think I've managed a workaround that issue and I'll be uploading the solution once I test it on a friends HTD Desire phone and if it works of course. Still I cannot understand why creating an object in the UI thread and accessing it in another newly created thread (created in the UI thread that initialized the object) does not work. After creation the object is only accessed from the new thread, never from another.
On Sep 27, 2:50 pm, Kevin Chadwick <[email protected]> wrote: > On Mon, 26 Sep 2011 18:44:55 -0600 > > Tim Mensch <[email protected]> wrote: > > I just have to disagree with your premise: There simply isn't likely to > > be a difference in how Java behaves between platforms EXCEPT FOR TIMING > > ISSUES when you have a faster CPU. That's where threads can get you in > > trouble. > > Why not try your app on other multicore phones and see if it crashes. > > Multicores were a compromise in order to keep gaining speed without > heat but bringing lots of software problems. It's a bit silly to use > them on phones that can't have large heat sinks! Not that we can change > the marketing, like tiny lens with 14 megapixel camera. -- You received this message because you are subscribed to the Google Groups "Android Discuss" 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-discuss?hl=en.
