Really? I thought cupcake will be the first release to support non-HVGA screen sizes. Has this changed?
On Tue, Mar 10, 2009 at 9:56 AM, Dianne Hackborn <[email protected]>wrote: > Flickering indicates you aren't handling page flipping correctly. > > Note that Cupcake does not official support anything beside 320x480, and > you can expect there to be UI issues running at any other resolution. (Not > flickering issues like you describe here, but UI elements not being > positioned correctly etc.) > > > On Tue, Mar 10, 2009 at 2:54 AM, harish <[email protected]> wrote: > >> >> Hi, >> >> I am trying to run android on s-video interface. >> my tv resolution is 640x480. >> >> i am able to bootup the android and logo and applications are >> running. >> but, during booting, android logo shakes and flickers. >> >> when the applications loaded, it is stable. >> >> when i click icons, the launching of new application flickers and >> comes. >> >> samething for browser also. >> >> Is any optimization to be done for reduced display size like 640x480 >> like to suit for TV standards. >> >> Regards, >> HarishKumar.V >> >> On Mar 10, 7:52 am, allstars <[email protected]> wrote: >> > for kernel part >> > first you need to modify DMA memory size in >> > kernel/include/asm-arm/memory.h >> > modify CONSISTENT_DMA_SIZE >> > originally it was only 2M , >> > so when you specify larger than 800x650 (800 * 650 * 4 = 2080000 => >> > almost 2M) >> > you can see out of memory in framebuffer >> > >> > but the maximux value of DMA_SIZE is only for 4M >> > (the size of the page table used by DMA) >> > >> > if you want to use more video memory >> > you can use boot_mem_alloc functions >> > >> > for emulator part >> > i have also enlarge linux memory in qemu >> > external/qemu/vl.c >> > modify DEFAULT_RAM_SIZE >> > otherwise the available memory after booting up is only a few >> > >> > for framework part >> > you need to modify the heap size for dalvikvm and surfaceflinger >> > if you want a very high resolution >> > >> > surfaceflinger: >> > mSurfaceHeapManager = new SurfaceHeapManager( SIZE_YOU_WANT << 20) >> > >> > and modify dalvik startup options >> > -Xms4m or 8m >> > at that time i found that if the startup memory size and maximux size >> > are the same >> > dalvik will behave strangely >> > >> > i've done this several months ago >> > so somethins might have changed >> > but above is what i have done before >> > >> > good luck to you anyway >> > >> > On Mar 9, 8:11 pm, Bill <[email protected]> wrote: >> > >> > > I'm trying to port Android to a screen with a higher resolution. I >> > > saw a previous post about this but, no one responded. Seems the issue >> > > has something to do with a limit possibly set in the kernel. Has >> > > anyone had any success porting to a bigger screen with resolution >> > > greater than 800x600 and if so could you please share your experience? >> > >> > > Here is the previous thread on the topic: >> http://groups.google.com/group/android-porting/browse_thread/thread/6... >> > >> > > Thanks! >> >> > > > -- > Dianne Hackborn > Android framework engineer > [email protected] > > Note: please don't send private questions to me, as I don't have time to > provide private support. All such questions should be posted on public > forums, where I and others can see and answer them. > > > > > > --~--~---------~--~----~------------~-------~--~----~ unsubscribe: [email protected] website: http://groups.google.com/group/android-porting -~----------~----~----~----~------~----~------~--~---
