Thanks for the replies.
But I wonder where android sets this limit so I can modify this to
support 1024X600 or 1024X800 resolution?
David Turner wrote:
> the emulator allows you to specify a larger size with a "magic" option
> (e.g. -skin 800x600), but it seems that the 1MB is either
> in the
programs) start vmstat and logcat in the background. The free
real memory goes to 0 as the different programs start up. Then the
kernel panics.
My current stripped system has run for days at a time without crashing
before I reboot it.
You will need at least 128mb ram
Brad
--
unsubscribe:
The problem is that your kernel driver isn't allocating enough
resolution for the Android graphics subsystem to work, specifically
the yres_virtual must be at least twice as big as the yres. Android
uses double buffering and the kernel told Android that there wasn't
enough space to double buffer (
Just a few more points:
You need to fix up your boot image. It looks as if you are
mounting the the root filesystem by NFS but you probably don't have /
system in that tree. You either need to add /system or you need to
change your init.rc to get /system from somewhere.
If you are getti
Just a few more points:
You need to fix up your boot image. It looks as if you are
mounting the the root filesystem by NFS but you probably don't have /
system in that tree. You either need to add /system or you need to
change your init.rc to get /system from somewhere.
If you are getti
Probably not enough RAM. According to what I've read (and my own
experience) you might be able to run in 128m but 192m is a better
bet. I have a small footprint - bare system running in 64m but almost
all apps/services have been remove...
--
unsubscribe: android-porting+unsubscr...@googlegroups
Your /data filesystem needs to support mmap(). JFFS2 doesn't. I have
run "eclair" using JFFS2 for the system and YAFFS2 for the /data
partition (both on top of the mtd device).
Remember that you need to port all the Android changes into your
kernel (porting your drivers into a newer kernel may b
Can't give an exact answer but 64m is too little, 128m may work
(depending on what is running) and 192m is suggested (especially for a
slow processor).
On Aug 26, 5:02 am, Tung Dang wrote:
> Hi all,
>
> Do you know what is the minimum of RAM to run Android 2.2 ?
>
> Rgs,
> Tung
--
unsubscribe:
On Aug 29, 12:56 am, Dimka Kuznec wrote:
> does anyone have any pointers for me to help debug this issue?
How much RAM do you have?
There are processes that Android will restart (or retry) if they can't
run due to lack of resources (memory). A quick glance at init.rc
implies that "bootanim" may
And read all the other "Kernel panic" threads for all the other
suggestions.
Again (as a summary):
1. You need a double buffering frame-buffer driver.
2. You need MMAP() support on the /data file system.
3. You need all the Android specific kernel code enabled in your
kernel.
4. You need enough R
I don't think the standard Android kernel has swap enabled and/or
configured (and you don't want to swap to flash as you will quickly
kill the flash).
And yes, I've watched memory usage as Android boots and you need 64mb.
--
unsubscribe: android-porting+unsubscr...@googlegroups.com
website: http
:11 pm, Dmitry Grinberg wrote:
> My kernel has swap enabled.
>
>
> Best Regards
>
> On Sun, Sep 5, 2010 at 4:34 PM, Brad Davis wrote:
> > I don't think the standard Android kernel has swap enabled and/or
> > configured (and you don't want to swap to flash as
t swap in
> android's init in the ramdisk and it indeed is enabled (as seen by runnig
> top on serial console)
>
>
> Best Regards
>
> On Mon, Sep 6, 2010 at 2:38 PM, Brad Davis wrote:
> > You also need to bind swap to disk partitions and/or files (I can't
> &g
> omapfb omapfb: no displays
> omapfb omapfb: failed to setup omapfb
> omapfb: probe of omapfb failed with error -22
If you are trying to boot Android (and not just the Linux kernel) you
have to have a frame buffer.
--
unsubscribe: android-porting+unsubscr...@googlegroups.com
website: http://gro
Probably not enough RAM (see other threads about this subject). Run
vmstat.
--
unsubscribe: android-porting+unsubscr...@googlegroups.com
website: http://groups.google.com/group/android-porting
seems normal.
>
> > I am troubling what's wrong.
>
> > Are there any problem with the LCD settings?
> > Or is there any problem with the kernel?
>
> > 2010/8/6 Brad Davis
>
> > Just a few more points:
>
> >> You need to fix up y
checked the log.
> It is nomal.
>
> I/EGLDisplaySurface( 1583): xres = 480 px
> I/EGLDisplaySurface( 1583): yres = 272 px
> I/EGLDisplaySurface( 1583): xres_virtual = 480 px
> I/EGLDisplaySurface( 1583): yres_virtual = 544 px
>
> Is there anything
What you may want is an embedded LInux kernel driver writer. (I've
done an Android port but it only included special screen handling, not
other hardware. I have done drivers for other OS's.).
On Nov 23, 11:25 am, Chilston777
wrote:
> Hi everyone,
>
> We are desperatley trying to port the Androi
You still have to reduce the amount of applications (number or size)
running. Standard Android really needs 192meg to run the standard
image.
On Dec 6, 12:43 am, Vivek wrote:
> Hi,
> Thank u for your inputs. The board has only 128MB RAM. I have
> also changed the RAM size to 128MB and che
It's been a while since I did any porting so things may have changed
(donut and eclair). I just did graphics, no other devices (sound,
gps, accelerometer, etc.). Specifically, I added support for an 555
RGB in 16 bits screen.
I found that Android is mostly forgiving of the Linux kernel version
a
I did most of a port to the Atmel at91sam9263-ek board a year and a half
ago (Android 2.1 and 2.2). My board did not have enough RAM to fully boot
Android. I would get the kernel up, the splash screen up (correctly
displayes), and then the system would crash while trying to start the
essenti
21 matches
Mail list logo
