Yes, you are right. I will not work more on this rotation problem. That is why I choose the easy way and set the app to always stay in portrait mode.
On 6 Dec, 10:51, Kostya Vasilyev <[email protected]> wrote: > Since this crash only happens on SE devices, they should really debug > this themselves. Could be a firmware bug (they do happen, especially > with the amount of customization SE does, compared to stock Android). > > I mean, they've got firmware developers, with full source code of what > goes onto their phones, with system-level debugging already set up, etc. > etc. etc. > > Should be pretty easy - provided they are willing to do this. Maybe you > can convince them? > > -- Kostya > > 06.12.2010 12:37, Eyvind Almqvist пишет: > > > > > > > I have already searched this forum and others about double buffering > > and I am already using SurfaceView. This is the info that I found: > > > "The idea of a double buffer is to hide the current drawing while it's > > happening and then flip to the entire drawn frame (back > > buffer / front buffer). When I use lockCanvas and post on the surface > > view, it doesn't show what I'm drawing until I post the entire canvas, > > which is the whole idea of double buffering." > > > I am already using lockCanvas unlockCanvasAndPost, so haven't I > > already implemented double buffering? In that case, there is not much > > more to do. > > > On 4 Dec, 11:27, Yahel<[email protected]> wrote: > >> For the screen-orientation, you just have to specify the one you want > >> in the activity tag of your manifest.xml : > > >>http://developer.android.com/intl/de/guide/topics/manifest/activity-e... > > >> I agree with Dianne on the not so impressive Sony-Ericson way to help > >> you fix an issue for THEIR devices !! > > >> As for double-buffering : Youappoffers psychedelic animation...I had > >> not notice the flickering as I thought it was part of the "What did I > >> smoke this time ?" concept :D > >> But if it was not intended you should definitely use double buffering. > >> Although it is weird because I had understood that SurfaceViews > >> implemented double buffering out of the box. Are you using > >> SurfaceView ? > >> Double-buffering being very straightforward, i'll let you search for > >> it. The basic idea being that you don't draw directly to screen but in > >> a bitmap the size of your screen first and then draw that buffer to > >> the screen while computing the next frame. > > >> Yahel > > -- > Kostya Vasilyev -- WiFi Manager + pretty widget > --http://kmansoft.wordpress.com- Dölj citerad text - > > - Visa citerad text - -- 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
