It looks like the issue is that you don't have make or wget
installed. The patches exist. Instead of using wget, try just
downloading them though a browser. I put it as command line, so they
could easily be turned into a script, so people wouldn't have to
manually do all of it.
On May 21, 2:21 pm, yalcin.akdo...@chello.at wrote:
> On 21 Mai, 15:26, yalcin.akdo...@chello.at wrote:
> > hello Lorraine,
> > thank you for your document. I started porting android on N800 as
> > newbie and installed ubuntu 8.04.
> > I have now troubles on the wiki document at step 4- compiling the
> > kernel.
> > in linux-2.6.21 dir running make:
> > > make ARCH=arm CROSS_COMPILE=../arm-2008ql/bin/arm-non-linux-gnueabi- bzImage
> > make: ../arm-2008ql/bin/arm-non-linux-gnueabi-gcc: Command not found
> > /bin/sh: ../arm-2008ql/bin/arm-non-linux-gnueabi-gcc: not found
> > make[1]: *** [arch/arm/kernel/asm-offsets.s] error 127
> > make: *** [prepare0] Error 2
> > could you tell me what is wrong?
> > yalcin
> > On May 21, 8:11 am, Lorraine <lorrai...@gmail.com> wrote:
> > > !!!!!!!!!!!!!!!!!!!!!!!!
> > > THANK YOU for posting the n800 patch!!!!!!!!!!! I thought it was just
> > > me not knowing how to use the n810 patches being provided to me. I'll
> > > try it immediately!!!!!
> > > Also.. I mentioned earlier in these posts that I was going to post a
> > > guide for total newbies to get Android to work on the n800 using
> > > Ubuntu.
> > > On May 20, 8:09 am, "Andrea Bernardi" <abernar...@gmail.com> wrote:
> > > > Thanks at all, I have Android on N800 with touchscreen.
> > > > I've used the attached patch obtained from NuuNeol patch, modified to work
> > > > on TSC2301 driver present on N800 driver instead of TSC2005 present on N810
> > > > and applied after patchv1 of android-on-n8xx.
> > > > To change between maemo and android coordinate you should insert the
> > > > following line in the start_android.sh script:
Jonathan,
wget and make is available for sure in Ubuntu out of the box... I
started with a fresh install.
yalcin,
I noticed that you typed:
"make ARCH=arm CROSS_COMPILE=../arm-2008ql/bin/arm-non-linux-gnueabi-
bzImage"
I noticed that 1 is a lower case l instead? When using the make
command, the things after "CROSS_COMPILE=" is a path to the cross
compiler. So go look for where you downloaded your cross compiler,
and then type it after "CROSS_COMPILE=" so if it's at /home/yalcin/
arm-2008.... then you need to use CROSS_COMPILE=/home/yalcin/
arm-2008 ... and so on.
On May 21, 2:27 pm, Jonathan Herriott <herri...@gmail.com> wrote:
> It looks like the issue is that you don't have make or wget
> installed. The patches exist. Instead of using wget, try just
> downloading them though a browser. I put it as command line, so they
> could easily be turned into a script, so people wouldn't have to
> manually do all of it.
> On May 21, 2:21 pm, yalcin.akdo...@chello.at wrote:
> > > could you tell me what is wrong?
> > > yalcin
> > > On May 21, 8:11 am, Lorraine <lorrai...@gmail.com> wrote:
> > > > !!!!!!!!!!!!!!!!!!!!!!!!
> > > > THANK YOU for posting the n800 patch!!!!!!!!!!! I thought it was just
> > > > me not knowing how to use the n810 patches being provided to me. I'll
> > > > try it immediately!!!!!
> > > > Also.. I mentioned earlier in these posts that I was going to post a
> > > > guide for total newbies to get Android to work on the n800 using
> > > > Ubuntu.
> > > > On May 20, 8:09 am, "Andrea Bernardi" <abernar...@gmail.com> wrote:
> > > > > Thanks at all, I have Android on N800 with touchscreen.
> > > > > I've used the attached patch obtained from NuuNeol patch, modified to work
> > > > > on TSC2301 driver present on N800 driver instead of TSC2005 present on N810
> > > > > and applied after patchv1 of android-on-n8xx.
> > > > > To change between maemo and android coordinate you should insert the
> > > > > following line in the start_android.sh script:
# tar -cvf system.img -C /sdcard /system tar: permission denied
# su tar -cvf system.img -C /sdcard /system # after that can't find the result system.img file.
--- info about history: busybox versions 1.10.1 and 1.10.2 did not work on AMD64 with ubuntu 8.04. i downloaded the last build from 18.mai and installed busybox (pushed to emulator) there were no tar under /data/busybox nor /sbin. I added tar from Desktop (adb push) to /data/busybox.
yalcin wrote: > an additional question. > i use sdk: android-sdk_m5-rc15_linux-x86 > wiki paper is related to: android-sdk_m3-rc37a > which sdk is actual to use?
> yalcin
Currently only m3 runs on the nokia n8xx. Sittiphol managed to get m5 to run a couple of times but it doesn't seem to be stable yet.
---- Georges Toth wrote: > Currently only m3 runs on the nokia n8xx. > Sittiphol managed to get m5 to run a couple of times but it doesn't seem to be stable yet.
> -- > regards,
> Georges Toth
Thank you. Maybe that was the source of my troubles. I'm going to give new start with m3.
Thanks to a patch made from Sittiphol, now I've Android m5-rc15 run on N800.
After have downloaded the kernel obtained from android-on-n8xx and applied the patch v1 from the same site and for the touchscreen in a my previous post, you have to add the following line in omapfb_main.c in path drivers/video/omap/:
line 579: if (var->xres + var->xoffset > var->xres_virtual) var->xoffset = var->xres_virtual - var->xres; if (var->yres + var->yoffset > var->yres_virtual) var->yoffset = var->yres_virtual - var->yres; + var->yres_virtual = var->yres_virtual * 2; // Add this line line_size = var->xres * bpp / 8;
On the ramdisk of m5-rc15 I've applied the same changes of the m3-rc37a (init.rc and qwerty.kl).
After I launch the m5 from maemo running with the following two script:
start_android_m5_script.sh
#!/bin/sh -x echo "Starting Android m5..." mount /dev/mmcblk1p2 /media/mmc1p2 rm -rf /media/mmc1p2/tmp/* umount -l /proc umount -l /sys sleep 1 mount -t proc proc /media/mmc1p2/proc mount -t sysfs sysfs /media/mmc1p2/sys mount --bind /dev /media/mmc1p2/dev chmod -R 777 /media/mmc1p2 echo z > /media/mmc1p2/proc/sysrq-trigger umask 000 chroot /media/mmc1p2 /a.sh
There are again stability problem but the m3-rc37a is more responsive... In the last versione I wait around 10-15 sec between the click to browser icon and the Google page but maybe is caused by memory problem (I launch Android with Maemo running and with only 40MB free).
> There are again stability problem but the m3-rc37a is more responsive... > In the last versione I wait around 10-15 sec between the click to browser > icon and the Google page but maybe is caused by memory problem (I launch > Android with Maemo running and with only 40MB free).
"Andrea Bernardi" wrote: > Thanks at all, I have Android on N800 with touchscreen. > I've used the attached patch obtained from NuuNeol patch, modified to work > on TSC2301 driver present on N800 driver instead of TSC2005 present on N810 > and applied after patchv1 of android-on-n8xx.
sorry but i can't find any .....patchv1. i assume it is the -> linux-2.6.21_rx-34_android-m5-rc14.bz2
i use your touchscreen patch. and i put the line "echo z > ...." in start_android.sh
but having problems on platform M3 - fatal error opening "/sys/android_power/last_user_activity"
Android should still start even if you are getting that error.. it
does for me anyway. Look in the older posts on this thread by Mohan,
he posted a modified version of power.c that will get rid of that
problem.
On May 24, 1:09 am, yalcin <yalcin.akdo...@chello.at> wrote:
> "Andrea Bernardi" wrote:
> > Thanks at all, I have Android on N800 with touchscreen.
> > I've used the attached patch obtained from NuuNeol patch, modified to work
> > on TSC2301 driver present on N800 driver instead of TSC2005 present on N810
> > and applied after patchv1 of android-on-n8xx.
> sorry but i can't find any .....patchv1.
> i assume it is the -> linux-2.6.21_rx-34_android-m5-rc14.bz2
> i use your touchscreen patch. and i put the line "echo z > ...." in start_android.sh
> but having problems on platform M3 - fatal error opening "/sys/android_power/last_user_activity"
Lorraine wrote: > Android should still start even if you are getting that error.. it > does for me anyway. Look in the older posts on this thread by Mohan, > he posted a modified version of power.c that will get rid of that > problem.
i got power.c from the discussions and solved the problem with it.
How you describe in your paper, the screen is dark, and after i touch the screen, can see the cylon picture. but nothing more.
Ok, so u never get past the cylon eye... did you check if
android_power folder is in /sys before you start android? If the
folder is not there then you need to flash the kernel again
> Lorraine wrote:
> > Android should still start even if you are getting that error.. it
> > does for me anyway. Look in the older posts on this thread by Mohan,
> > he posted a modified version of power.c that will get rid of that
> > problem.
> i got power.c from the discussions and solved the problem with it.
> How you describe in your paper, the screen is dark, and after i touch the screen, can see the cylon picture. but nothing more.
The principal problem is for low memory, because this version uses around 50MB of memory and maemo up and running uses 80MB. To solve this problem I've reflashed N800 with the option "--*set-rd-flags*=no-lifeguard-reset" so I can stop X and other essential service without reboot the device. I launch the following free-memory.sh script:
After this script Maemo uses only around 60MB of memory and after than I run Android with more success. Moreover, actually I launch Android via init with the following script start_android_init.sh:
At last, I've compiled in the kernel also the module low-memory-killer present on android linux kernel. I think isn't fundamental but if you want insert this driver apply the patch attached to the mail.
After that, if your sound subsystem works tell me what you have done...:D
Best Regards, Andrea Bernardi
P.S.: the patch for the double buffer showed in the previuos mail isn't perfect, you see only interleaved frame on your screen...
> Thanks for your kindly post here and I followed you steps > provided to porting > Android to N800. For M3 sdk everything is Ok. But for M5 ,the things > are a little > weird . Sometimes I can see the Android desktop appears then freezes, > I can do > nothing. Most times it cannot lauch successfully , from logcat , I can > see that > it cannot find service activity and waited for it endlessly . Do you > have any idea > of this ?
> Thanks a lot.
> On May 23, 11:50 pm, "Andrea Bernardi" <abernar...@gmail.com> wrote: > > Thanks to a patch made from Sittiphol, now I've Android m5-rc15 run on > N800.
> > After have downloaded the kernel obtained from android-on-n8xx and > applied > > the patch v1 from the same site and for the touchscreen in a my previous > > post, you have to add the following line in omapfb_main.c in path > > drivers/video/omap/:
The screen is normal in few 10~20 seconds, and then it blinks.
Afterwards, the while screen is shown.
BTW, I try to path lowmemory.patch, and make this function enable.
But some error was occurred.
If I add "CONFIG_LOW_MEMORY_KILLER=y", there will be a compile error.
--------------------------------------------------------------------------- --------------------------------------------------------------------------- -----------------------------------
CC drivers/misc/lowmemorykiller/lowmemorykiller.o
drivers/misc/lowmemorykiller/lowmemorykiller.c:24: error: variable
'lowmem_shrinker' has initializer but incomplete type
drivers/misc/lowmemorykiller/lowmemorykiller.c:25: error: unknown
field 'shrink' specified in initializer
drivers/misc/lowmemorykiller/lowmemorykiller.c:25: warning: excess
elements in struct initializer
drivers/misc/lowmemorykiller/lowmemorykiller.c:25: warning: (near
initialization for 'lowmem_shrinker')
drivers/misc/lowmemorykiller/lowmemorykiller.c:26: error: unknown
field 'seeks' specified in initializer
drivers/misc/lowmemorykiller/lowmemorykiller.c:27: warning: excess
elements in struct initializer
drivers/misc/lowmemorykiller/lowmemorykiller.c:27: warning: (near
initialization for 'lowmem_shrinker')
drivers/misc/lowmemorykiller/lowmemorykiller.c: In function
'__check_cost':
drivers/misc/lowmemorykiller/lowmemorykiller.c:46: error: invalid use
of undefined type 'struct shrinker'
drivers/misc/lowmemorykiller/lowmemorykiller.c: At top level:
drivers/misc/lowmemorykiller/lowmemorykiller.c:46: error: invalid use
of undefined type 'struct shrinker'
drivers/misc/lowmemorykiller/lowmemorykiller.c: In function
'lowmem_init':
drivers/misc/lowmemorykiller/lowmemorykiller.c:106: warning: implicit
declaration of function 'register_shrinker'
drivers/misc/lowmemorykiller/lowmemorykiller.c: In function
'lowmem_exit':
drivers/misc/lowmemorykiller/lowmemorykiller.c:112: warning: implicit
declaration of function 'unregister_shrinker'
make[3]: *** [drivers/misc/lowmemorykiller/lowmemorykiller.o] Error 1
make[2]: *** [drivers/misc/lowmemorykiller] Error 2
make[1]: *** [drivers/misc] Error 2
make: *** [drivers] Error 2
--------------------------------------------------------------------------- --------------------------------------------------------------------------- -----------------------------------
No matter I patch the lowmemorykiller.c or not. As long as I set
CONFIG_LOW_MEMORY_KILLER=y, the error was occurred.
I am trying to slove this problem. and I hope that I can startup
Android without maemo.
I think that insufficient momory issue will be not exist . :)
Sorry, in the previous lowmemory patch I have forgotten something. That attached in this mail is correct...I hope ;D
An other problem encountered, is due to Android power management and is also described in http://elinux.org/Android_on_OMAP#Power_management. In practice, the system starts properly but after 2-3 minutes if you don't use it on goes to suspend mode (black screen). From that state it wakes up only with a click of the power button of N800. In the case remains in suspend mode for around a minute, it powers off.
Maybe also your problem is due to Android power management, otherwise I don't know.
> The screen is normal in few 10~20 seconds, and then it blinks. > Afterwards, the while screen is shown.
> BTW, I try to path lowmemory.patch, and make this function enable. > But some error was occurred. > If I add "CONFIG_LOW_MEMORY_KILLER=y", there will be a compile error.
> --------------------------------------------------------------------------- --------------------------------------------------------------------------- ----------------------------------- > CC drivers/misc/lowmemorykiller/lowmemorykiller.o > drivers/misc/lowmemorykiller/lowmemorykiller.c:24: error: variable > 'lowmem_shrinker' has initializer but incomplete type > drivers/misc/lowmemorykiller/lowmemorykiller.c:25: error: unknown > field 'shrink' specified in initializer > drivers/misc/lowmemorykiller/lowmemorykiller.c:25: warning: excess > elements in struct initializer > drivers/misc/lowmemorykiller/lowmemorykiller.c:25: warning: (near > initialization for 'lowmem_shrinker') > drivers/misc/lowmemorykiller/lowmemorykiller.c:26: error: unknown > field 'seeks' specified in initializer > drivers/misc/lowmemorykiller/lowmemorykiller.c:27: warning: excess > elements in struct initializer > drivers/misc/lowmemorykiller/lowmemorykiller.c:27: warning: (near > initialization for 'lowmem_shrinker') > drivers/misc/lowmemorykiller/lowmemorykiller.c: In function > '__check_cost': > drivers/misc/lowmemorykiller/lowmemorykiller.c:46: error: invalid use > of undefined type 'struct shrinker' > drivers/misc/lowmemorykiller/lowmemorykiller.c: At top level: > drivers/misc/lowmemorykiller/lowmemorykiller.c:46: error: invalid use > of undefined type 'struct shrinker' > drivers/misc/lowmemorykiller/lowmemorykiller.c: In function > 'lowmem_init': > drivers/misc/lowmemorykiller/lowmemorykiller.c:106: warning: implicit > declaration of function 'register_shrinker' > drivers/misc/lowmemorykiller/lowmemorykiller.c: In function > 'lowmem_exit': > drivers/misc/lowmemorykiller/lowmemorykiller.c:112: warning: implicit > declaration of function 'unregister_shrinker' > make[3]: *** [drivers/misc/lowmemorykiller/lowmemorykiller.o] Error 1 > make[2]: *** [drivers/misc/lowmemorykiller] Error 2 > make[1]: *** [drivers/misc] Error 2 > make: *** [drivers] Error 2
> No matter I patch the lowmemorykiller.c or not. As long as I set > CONFIG_LOW_MEMORY_KILLER=y, the error was occurred.
> I am trying to slove this problem. and I hope that I can startup > Android without maemo. > I think that insufficient momory issue will be not exist . :)
Andrea Bernardi wrote: > Hi, also on my N800 m5-rc15 give me some problem.
> The principal problem is for low memory, because this version uses > around 50MB of memory and maemo up and running uses 80MB. To solve > this problem I've reflashed N800 with the option > "--*set-rd-flags*=no-lifeguard-reset" so I can stop X and other > essential service without reboot the device. I launch the following > free-memory.sh script:
> After this script Maemo uses only around 60MB of memory and after than > I run Android with more success. Moreover, actually I launch Android > via init with the following script start_android_init.sh:
> At last, I've compiled in the kernel also the module low-memory-killer > present on android linux kernel. I think isn't fundamental but if you > want insert this driver apply the patch attached to the mail.
> After that, if your sound subsystem works tell me what you have done...:D
> Best Regards, > Andrea Bernardi
> P.S.: the patch for the double buffer showed in the previuos mail > isn't perfect, you see only interleaved frame on your screen...
> 2008/6/4 las <jilte...@gmail.com <mailto:jilte...@gmail.com>>:
> Hi, there
> Thanks for your kindly post here and I followed you steps > provided to porting > Android to N800. For M3 sdk everything is Ok. But for M5 ,the things > are a little > weird . Sometimes I can see the Android desktop appears then freezes, > I can do > nothing. Most times it cannot lauch successfully , from logcat , I can > see that > it cannot find service activity and waited for it endlessly . Do you > have any idea > of this ?
> Thanks a lot.
> On May 23, 11:50 pm, "Andrea Bernardi" <abernar...@gmail.com > <mailto:abernar...@gmail.com>> wrote: > > Thanks to a patch made from Sittiphol, now I've Android m5-rc15 > run on N800.
> > After have downloaded the kernel obtained from android-on-n8xx > and applied > > the patch v1 from the same site and for the touchscreen in a my > previous > > post, you have to add the following line in omapfb_main.c in path > > drivers/video/omap/:
