Android/Linux for PXA312 (Omnia)

[us1111]

Complete steps for booting the android linux kernel (updates follow as we progress):


Install Dev Environment:

apt-get install linux-headers-$(uname -r) gcc make kernel-package libncurses5-dev fakeroot wget bzip2 git-svn curl

Download Cross Compiler
www.codesourcery.com/sgpp/lite/arm/portal/release642

Select: GNU/Linux (and then Advanced Packages / IA32 GNU/Linux TAR)


Download and Unpack Cross Compiler
(www.codesourcery.com/sgpp/lite/arm/portal/package3686/public/arm-none-eabi/arm-2008q3-66-arm-none-eabi-i686-pc-linux-gnu.tar.bz2)

# wget http://www.codesourcery.com/sgpp/lite/arm/portal/package3686/public/arm-none-eabi/arm-2008q3-66-arm-none-eabi-i686-pc-linux-gnu.tar.bz2
# cd /usr/local ; tar -xjvf /tmp/arm-2008q3-72-arm-none-linux-gnueabi-i686-pc-linux-gnu.tar.bz2

Download Kernel (Thans to Oliver Ford!)
# git clone http://www.oliford.co.uk/hpipaq214/ipaq214.git v4

Change in Makefile:

# vi /ANDROID/v4/Makefile
ARCH ?= arm
CROSS_COMPILE ?= /usr/local/xscale/arm-2008q3/bin/arm-none-linux-gnueabi-


Adjust resolution (Thanks to z720!)
open the /arch/arm/mach-pxa/hpipaq214-lcd.c and change the folowing parameters:


.xres = 240
.yres = 400
.pixclock = 96153.



Compile kernel:
make Image

The compiled and with Haret runable image will be in "arch/arm/boot/Image"

Download Haret (I used the PXA312 version from Oliver Ford from www.handhelds.com)

http://www.oliford.co.uk/hpipaq214/files/h...aq214-aug08.exe

Change Haret Settings (default.txt)

set kernel "Image"
Set ramaddr 0xa0000000
Set RAMSIZE 0x04000000
Set cmdline "root=179:2 rootdelay=3 rw init=/sbin/init"
Set mtype 1653
Set kernelcrc 0
Set fbduringboot 1
Set forcefbduringboot 1



Bootlinux

Booting.....

If you copy the compiled Image to the directory in which you placed Haret, you should be off, the kernel will boot.. Mind you, this is just the booting kernel, the hard work will start from here!

http://i2.photobucket.com/albums/y15/just4it/Photo0201.jpg
Thanx for the picture z720!

Cross Compile busybox with static linking:

cd busybox-1.13.2/

Change Makefile to have the cross compiler active again:


ARCH ?= arm
CROSS_COMPILE ?= /usr/local/arm-2008q3/bin/arm-none-linux-gnueabi-


Make the static busybox (make menuconfig first and disable all non wanted busybox commands, leave ash, init, rclinux and telnetd active for later use!):

# LDFLAGS="--static" CFLAGS="--static" make
# file busybox
busybox: ELF 32-bit LSB executable, ARM, version 1 (SYSV), statically linked, stripped

Copy the busybox to the new initrd directory:

# cp busybox /ANDROID/initrd
# cd /ANDROID/initrd

# ln -s busybox init
# ln -s busybox ash
# ln -s busybox rclinux
# mkdir dev; mkdir sys ; mkdir proc
# cp -dpr /dev/ttys1 /dev/ttys2 /dev/ttys3 /dev/ttys4 /ANDROID/initrd/dev

Make the initrd.gz ramdisk fromout the initrd directory
# find . | cpio --create --'format=newc' | gzip >../initrd.gz

Copy it to the directory in which the kernel is placed...

Change default.txt cmdline:
Set cmdline "root=/dev/ram0 ramdisk_size=8192 rootdelay=5 rootwait rw init=/ash lpj=loops_per_jiffy boot_delay=100"


Boot and see why we need a keyboard now :( Next step is maybe auto configure network and start telnetd in the ramdisk :)










[OLD]
Hi, I read the thread about running Android on the Kaiser and was very interested to get at least a linux kernel running on my phone.. However no luck..

Well.. Tried to compile the kernel for this specific architecture (PXA312) with the gnueabi toolchain. The android kernel compiled fine with some minor changes. After that, i tried to start the kernel with HaRET but could not get it to start. I cannot determine the RAMADDR and the mtype for the omnia.

http://www.arm.linux.org.uk/developer/machines/
http://www.codesourcery.com/gnu_toolchains/arm/portal/package2549/public/arm-none-linux-gnueabi/arm-2008q1-126-arm-none-linux-gnueabi-i686-pc-linux-gnu.tar.bz2
http://code.google.com/p/android/downloads/list

HaRET does not seem to recognize the omnia's PXA312... Also i cannot determine the mtype for this.. Anyone have any ideas on how to get the kernel to boot???

[cr2]

HaRET does not seem to recognize the omnia's PXA312... Also i cannot determine the mtype for this.. Anyone have any ideas on how to get the kernel to boot???

PXA3xx is supported by linux-arm, but you need to do a lot of device research
before you can boot linux.
Can you post your 'haretlog.txt' file ?

[us1111]

I'm using the latest haret-20080927.exe which generates the attached output... Took a little while, because after running the kernel this time, all my non-rom applications did not work (no certificate)..

These are btw. the PXA settings in .config:

CONFIG_ARCH_PXA=y
CONFIG_CPU_PXA300=y
CONFIG_CPU_PXA310=y
CONFIG_CPU_PXA320=y
CONFIG_PXA3xx=y
CONFIG_PXA_SSP=y

Sure hope you can help!! I'm reasonably known with linux and a bit of programming... By the way, i completely guessed the RAMADDR. Also the mtype i hope is close enough and got it from the linuxarm site (Marvell PXA3XX DVK Zylonite). These values are most probably wrong but I haven't got a clue how to determine these with the given tools...

[sageman8]

Omnia uses DDR ram while many others use SD ram. Maybe this will help

[us1111]

Omnia uses DDR ram while many others use SD ram. Maybe this will help

Well, maybe it's my lack of knowledge, but it did not help for me.. :confused: I believe that as long as I have no MTYPE or RAMADDR values, it's impossible to boot the kernel.. So I sure could need some help with that

[us1111]

Hmmm. Maybe I can do something with the following info regarding the RAMADDR:

128.58M (0x8095800) DSK1:
| 1.35M (0x159800) Part00
| 3.08M (0x313800) Part01
| 124.15M (0x7c27800) Part02

Now I just have to figure out what is the correct base.. No luck at all finding the correct MTYPE for my PXA312 though..

[ducamie]

try mytype 1388

look here.. http://www.arm.linux.org.uk/developer/machines/

as far as i can see, the pxa300/310 has the same cpu as the 312 so theres a good chance you'd be alright with that machtype.

good luck

[kosmodisk]

is it possible to compile it for PXA 27x?

[us1111]

is it possible to compile it for PXA 27x?

Yeah.. It should:

root@JEOS:/ANDROID/android/kernel.git# grep -i pxa .config
CONFIG_ARCH_PXA=y
# Intel PXA2xx/PXA3xx Implementations
# Supported PXA3xx Processor Variants
CONFIG_CPU_PXA300=y
CONFIG_CPU_PXA310=y
CONFIG_CPU_PXA320=y
# CONFIG_MACH_LOGICPD_PXA270 is not set
# CONFIG_ARCH_PXA_IDP is not set
# CONFIG_PXA_SHARPSL is not set
# CONFIG_ARCH_PXA_ESERIES is not set
CONFIG_PXA3xx=y
CONFIG_PXA_SSP=y
# CONFIG_PCMCIA_PXA2XX is not set
# CONFIG_PXA_FICP is not set
# CONFIG_KEYBOARD_PXA27x is not set
# CONFIG_SERIAL_PXA is not set
# CONFIG_I2C_PXA is not set
# CONFIG_SPI_PXA2XX is not set
# CONFIG_FB_PXA is not set
# CONFIG_SND_PXA2XX_AC97 is not set
# CONFIG_SND_PXA2XX_SOC is not set
# CONFIG_USB_GADGET_PXA2XX is not set
# CONFIG_MMC_PXA is not set

[kosmodisk]

i´m not a programmer(i have only basic knowledge of it), but i would like to try porting android to hp ipaq rw6815/o2 atom, is it very hard? i've tried to run port for kaiser or vogue, but it stucks up on log: jumping to kernel

can you give me some advices? thanks

[us1111]

i´m not a programmer(i have only basic knowledge of it), but i would like to try porting android to hp ipaq rw6815/o2 atom, is it very hard? i've tried to run port for kaiser or vogue, but it stucks up on log: jumping to kernel

can you give me some advices? thanks

Well porting should not be a to big of an issue.. As far as i can see the kernel is the biggest hurdle (with drivers) and from then on you have to cross compile android.

[xudsa II USERT]

I'd love having my ipaq rw6828 to boot the kernel too!:) If only someone could find a way to do it.:(

[Gogeta07]

sorry...but where i can find linux for p3600?thnx

[tdh_andy]

I got the kernel config done but i get an error trying to compile the kernel. I think i don't have the proper toolchain for this. I got the arm toolchain but i get some errors i'm not sure what i need exactly to get this fully done.
Has anyone managed to complie a proper kernel for omnia? If so can you please post a how-to?

[unsungboxer]

I am happy to see someone has started some development for an android port on the omnia. I am interested in getting this phone, hopefully it can run android in the near future.

I am currently rocking android on the vogue thanks to Martin (DZO's) hard work. Happy porting!

-Unsung.

[ollnixon]

Has anyone got anywhere with this? Or does anyone know of any projects under way where we can help and contribute to?

[AkshayGenius]

Any updates on this guyz? I would love to contribute in any way(donate, test, etc)...

[smwald]

just picked up an omnia from verizon and am hoping to get android up and running on it - wondering if anyone had any progress or needed any help to further development.

[Arty68]

Hi guys,

I have done some tests with Haret and some HP IPAQ images.
Good news linux is booting with this image.

[Arty68]

Hi guys,

I have done some tests with Haret and some HP IPAQ images on the omnia.
Good news linux is booting on the with this image.

http://www.handhelds.org/moin/moin.cgi/hpipaq214Downloads

The resolution is not good enought to see what is happening and linux seems to crasch

[us1111]

Hi guys,

I have done some tests with Haret and some HP IPAQ images on the omnia.
Good news linux is booting on the with this image.

http://www.handhelds.org/moin/moin.cgi/hpipaq214Downloads

The resolution is not good enought to see what is happening and linux seems to crasch

Nice find!! This enabled me to work towards compiling the kernel myself!! I compiled the kernel and the kernel boots with Haret at least!!!

Install for example JEOS (in an Virtual Machine)


Install Dev Environment:

apt-get install linux-headers-$(uname -r) gcc make kernel-package libncurses5-dev fakeroot wget bzip2

Download Cross Compiler
www.codesourcery.com/sgpp/lite/arm/portal/release642

Select: GNU/Linux (and then Advanced Packages / IA32 GNU/Linux TAR)


Download and Unpack Cross Compiler
(www.codesourcery.com/sgpp/lite/arm/portal/package3686/public/arm-none-eabi/arm-2008q3-66-arm-none-eabi-i686-pc-linux-gnu.tar.bz2)

wget http://www.codesourcery.com/sgpp/lite/arm/portal/package3686/public/arm-none-eabi/arm-2008q3-66-arm-none-eabi-i686-pc-linux-gnu.tar.bz2
cd /usr/local ; tar -xjvf /tmp/arm-2008q3-72-arm-none-linux-gnueabi-i686-pc-linux-gnu.tar.bz2

Download GIT Kernel
# apt-get install git-svn

Download Kernel
# git clone http://www.oliford.co.uk/hpipaq214/ipaq214.git v4

Change in Makefile:

# vi /ANDROID/v4/Makefile
ARCH ?= arm
CROSS_COMPILE ?= /usr/local/xscale/arm-2008q3/bin/arm-none-linux-gnueabi-

Compile kernel:
make Image

The compiled and with Haret runable image will be in "arch/arm/boot/Image"

Download Haret (I used the PXA312 version from Oliver Ford from www.handhelds.com)

http://www.oliford.co.uk/hpipaq214/files/h...aq214-aug08.exe

Change Haret Settings (default.txt)

set kernel "Image"
Set ramaddr 0xa0000000
Set RAMSIZE 0x04000000
Set cmdline "root=179:2 rootdelay=3 rw init=/sbin/init"
Set mtype 1653
Set kernelcrc 0
Set fbduringboot 1
Set forcefbduringboot 1

Bootlinux

Booting.....

If you copy the compiled Image to the directory in which you placed Haret, you should be off, the kernel will boot.. Mind you, this is just the booting kernel, the hard work will start from here!

[Soul_Est]

Nice find!! This enabled me to work towards compiling the kernel myself!! I compiled the kernel and the kernel boots with Haret at least!!!

Install for example JEOS (in an Virtual Machine)


Install Dev Environment:
apt-get gcc
apt-get make
apt-get install linux-headers-$(uname -r)
apt-get install kernel-package libncurses5-dev fakeroot wget bzip2

Download Cross Compiler
http://www.codesourcery.com/gnu_toolchains...?@template=lite

Select: GNU/Linux (and then Advanced Packages / IA32 GNU/Linux TAR)


Download and Unpack Cross Compiler
wget http://www.codesourcery.com/gnu_toolchains...nux-gnu.tar.bz2
cd /usr/local ; tar -xjvf /tmp/arm-2008q3-72-arm-none-linux-gnueabi-i686-pc-linux-gnu.tar.bz2

Download GIT Kernel
# apt-get install git-svn

Download Kernel
# git clone http://www.oliford.co.uk/hpipaq214/ipaq214.git v4

Change in Makefile:

# vi /ANDROID/v4/Makefile
ARCH ?= arm
CROSS_COMPILE ?= /usr/local/xscale/arm-2008q3/bin/arm-none-linux-gnueabi-

Compile kernel:
make Image

The compiled and with Haret runable image will be in "arch/arm/boot/Image"

Download Haret (I used the PXA312 version from Oliver Ford from www.handhelds.com)

http://www.oliford.co.uk/hpipaq214/files/h...aq214-aug08.exe

Change Haret Settings (default.txt)

set kernel "Image"
Set ramaddr 0xa0000000
Set RAMSIZE 0x04000000
Set cmdline "root=179:2 rootdelay=3 rw init=/sbin/init"
Set mtype 1653
Set kernelcrc 0
Set fbduringboot 1
Set forcefbduringboot 1

Bootlinux

Booting.....

If you copy the compiled Image to the directory in which you placed Haret, you should be off, the kernel will boot.. Mind you, this is just the booting kernel, the hard work will start from here!

This is wonderful work! While I don't known an Omnia, it is good to see initiative taken on projects such as these.

[Arty68]

Merry Xmass every body !!
And thank you so much for the method us1111 !!

Just a question us1111 : which def_config file do you used ?

Nice find!! This enabled me to work towards compiling the kernel myself!! I compiled the kernel and the kernel boots with Haret at least!!!

Install for example JEOS (in an Virtual Machine)


Install Dev Environment:
apt-get gcc
apt-get make
apt-get install linux-headers-$(uname -r)
apt-get install kernel-package libncurses5-dev fakeroot wget bzip2

Download Cross Compiler
http://www.codesourcery.com/gnu_toolchains...?@template=lite

Select: GNU/Linux (and then Advanced Packages / IA32 GNU/Linux TAR)


Download and Unpack Cross Compiler
wget http://www.codesourcery.com/gnu_toolchains...nux-gnu.tar.bz2
cd /usr/local ; tar -xjvf /tmp/arm-2008q3-72-arm-none-linux-gnueabi-i686-pc-linux-gnu.tar.bz2

Download GIT Kernel
# apt-get install git-svn

Download Kernel
# git clone http://www.oliford.co.uk/hpipaq214/ipaq214.git v4

Change in Makefile:

# vi /ANDROID/v4/Makefile
ARCH ?= arm
CROSS_COMPILE ?= /usr/local/xscale/arm-2008q3/bin/arm-none-linux-gnueabi-

Compile kernel:
make Image

The compiled and with Haret runable image will be in "arch/arm/boot/Image"

Download Haret (I used the PXA312 version from Oliver Ford from www.handhelds.com)

http://www.oliford.co.uk/hpipaq214/files/h...aq214-aug08.exe

Change Haret Settings (default.txt)

set kernel "Image"
Set ramaddr 0xa0000000
Set RAMSIZE 0x04000000
Set cmdline "root=179:2 rootdelay=3 rw init=/sbin/init"
Set mtype 1653
Set kernelcrc 0
Set fbduringboot 1
Set forcefbduringboot 1

Bootlinux

Booting.....

If you copy the compiled Image to the directory in which you placed Haret, you should be off, the kernel will boot.. Mind you, this is just the booting kernel, the hard work will start from here!

[unsungboxer]

Merry Xmass every body !!
And thank you so much for the method us1111 !!

Just a question us1111 : which def_config file do you used ?

Thank you everyone for your hard work on this. I will likely get an omnia once I see that android boots beyond the linux kernal. Keep it up!

btw if you head over to the android vogue forum, both DZO and f00bar are very knowledgable in this development.

[BigDaemon]

too sad that it looks like the development on Android for samsumgs i900 omnia has stopped at this point :-(
I will get mine in a few weeks and will start playing around a bit with this, but without help i won´t get too much, because i don´t know much about linux and ppc :-(

[Girvo]

Top notch work so far! I'm guessing that there hasn't been much progress since?

May I ask what now needs to be done, because I'd love to help :)

[us1111]

Hi, because of lack of time, i'm not getting much further soon anyway.. I've looked into the kernel display driver (Sa1100.c??) to get the resolution and refreshrate on par with the samsung's screen. But due to the lack of time, no go. This is the information I gathered about the screen.

LCD Panel:
ELA UNIT-LCD UNIT ASSY(SGH_I90
QLC01
GH96-03195A
SGH-I900XKCDTM
[GH96-03195A]

Without proper refresh rate and resolution, the screen could be damages so that's the very first thing to fix in the kernel. Should'nt be too hard if you have an idea of what you're doing (unlike me;) )

I believe the next goal should be to run a minimal shell like busybox fromout the compiled kernel.

[oxiroxt]

When I run Haret, the screen freezes with the letters: Jumping to kernel... And it stops there.

I followed though all steps, however I had to "make menuconfig", then saved with the defaults, before "make Image". Could this be wrong?
Help, please?

Thanks,
oxi

[us1111]

Can you boot with this image?:

http://www.handhelds.org/moin/moin.cgi/hpipaq214Downloads

That should work.. If that works, you could try the compiled kernel. If it doesn't, there's something else wrong.

[oxiroxt]

LOL, with that image (http://www.oliford.co.uk/hpipaq214/files/Image-ipaq214-20081108) right after "jumping to kernel" the phone will start vibrating, and the flash will light up for a moment.

I wouldn't recommend anyone else to try this one. Doesn't feel so good xD
I appreciate your help thou :)

I'm wondering what could be wrong?

Thanks,
oxi

[oxiroxt]

I was thinking... maybe it has to do with the mem settings? But since those parameters are called ramaddr and RAMSIZE, I'd guess no... Anyways I got the 16gb version, anyone got it to work on this one? Maybe it only works for 8gb ver.???

Also, I'd like to know what root=179:2 means. I have tried it both from internal flash mem and microsd, same results, except it won't start vibrating for the latter.

cheers,
oxi

[chomi7]

LOL, with that image (http://www.oliford.co.uk/hpipaq214/files/Image-ipaq214-20081108) right after "jumping to kernel" the phone will start vibrating, and the flash will light up for a moment.

I wouldn't recommend anyone else to try this one. Doesn't feel so good xD
I appreciate your help thou :)

I'm wondering what could be wrong?

Thanks,
oxi

I have the same problem. I have de 8Gb model. Can somebody help us please?

[oxiroxt]

I have the same problem. I have de 8Gb model. Can somebody help us please?

So, it seems the problem has nothing to do with which model we have... either 8gb or 16
Maybe there's something different in our phones? I bought it in Spain, and (as I've seen in another forum your nationality) you might have bought it in Spain too?

Please, could anyone else report on this?

Thanks,
oxi

[oxiroxt]

Hi,

I don't know about hacking, but I tried to find any difference from your logs.
Hopefully this will mean something to you. It doesn't make any sense to me:

< Function '?GXOpenDisplay@@YAHPAUHWND__@@K@Z' in library 'gx' at 02A789EC
< Function '?GXCloseDisplay@@YAHXZ' in library 'gx' at 02A78DD8
< Function '?GXBeginDraw@@YAPAXXZ' in library 'gx' at 02A782A8
< Function '?GXEndDraw@@YAHXZ' in library 'gx' at 02A7836C
---
> Function '?GXOpenDisplay@@YAHPAUHWND__@@K@Z' in library 'gx' at 029E09EC
> Function '?GXCloseDisplay@@YAHXZ' in library 'gx' at 029E0DD8
> Function '?GXBeginDraw@@YAPAXXZ' in library 'gx' at 029E02A8
> Function '?GXEndDraw@@YAHXZ' in library 'gx' at 029E036C

< WinCE reports memory size 117440512 (phys=101994496 store=94134272)
---
> WinCE reports memory size 117440512 (phys=101404672 store=86523904)

I went through the haret docs and realized I can't watch the gpios nor irqs, but I can read the mem. Then how to write drivers for the phone once linux boots correctly for everybody?

edit: Please, anything I can do to gather info for you, ask away.

P.S: I apologize for flooding this forum. I realize it's intended for htc devices, as I'm the proud owner of a (bricked, not so proud) Uni.

Thanks,
oxi

[us1111]

I too have the flashing of the light, however after that, the kernel boots (be it in the wrong resolution) and shows some kernel information.

[vipwolf]

Hi I have the DXHL3 firmware and cant even get haret to start. It just tells me that all parameters are set
Set Ramsize ...
Set cmdline ....
etc.
and then

Calling WSACleanup
Shuting down.

Anybody can help me in what step you undertook
I tried both my selfcompiled kernel as well as the one from handhelds.org for the IPAQ with both the IAPQ haret version and the stock version. Results are the same

[oxiroxt]

So, I'm thinking the problem might have to do with the firmware?

Could you, us1111 and chomi7 post your firmware version? And anyone else too, reporting whether they can get the ipaq image to boot or not?

You can check this in Settings->System->Version. Post the alphanumeric sequence after the slash in PDA.

I haven't flashed my device yet:

Can't boot.
XJHJ2

Thanks,
oxi

[us1111]

My firmware is:

i900DXIA1/QB01M Before that it was DXHL3.. Mine also flashes the flashlight while booting the kernel. Also the resolution is way off so the LCD screen makes a high pitch noise.. Like i said. That should be the first thing to work on (LCD settings are done somehow in SA1100.c)

[chomi7]

Actualy I have the HL2 and I try with the HJ6 and the same. With the hp image I have the flash and vibrate problem and then I compile my own image and this disapear but the kernel don´t run.

[vipwolf]

I found the erro why my image wont boot.
The default.txt postet earlier was missing one vital command

"Bootlinux" ;) so the full default.txt should look like this

set kernel "Image"
Set ramaddr 0xa0000000
Set RAMSIZE 0x04000000
Set cmdline "root=179:2 rootdelay=3 rw init=/sbin/init"
Set mtype 1653
Set kernelcrc 0
Set fbduringboot 1
Set forcefbduringboot 1

Bootlinux

[oxiroxt]

I've just tried with DXHL3. Still no luck :confused:
I got the usual flashing and vibration and the kernel won't load... :(
Gotta try to figure out what the real problem is...

Thank you so far,
oxi

[z720]

nobody continue to do more research?
I'm trying to download the git, it took me whole morning but still not yet completed. :mad:
really wish to see omnia in linux !!!:D

[dejfson]

hi all,
i've compiled git version of kernel by using default config from the ipaq mentioned somewhere above in the thread. linux runs ok, however the driver for framebuffer is not working correctly as it does not recognize the resolution/clocks etc.

i wonder what type of framebuffer it is. i doubt about vesafb, i think that with pxafb we have better chance do to. I've been looking on the web for 240x400 displays, there are not many so I guess that by reading the datasheet like this one:

http://www.optrex.com/products/partdetail.asp?PartNumber=T-55149GD030J-MLW-AJN

we could estimate the parameters. I'm not sure whether I have correctly setup all the parameters, but i've tried this default.txt:

set kernel "Image"
Set ramaddr 0xa0000000
Set RAMSIZE 0x04000000
Set cmdline "root=179:2 rootdelay=3 rw init=/sbin/init video=pxafb:mode:240x400-16.active:pixclock:100000:pixclockpol:0:hsync:0:vs
Set mtype 1653
Set kernelcrc 0
Set fbduringboot 1
Set forcefbduringboot 1

Bootlinux


apparently the video=pxafb.... does not lead to correct solution (maybe the pxafb cannot be used, instead we would have to program a new driver for renesas r61509 as stated in datasheet of display)

in case of any progress i'm interested in more info...

just a quick hint: do not let the display work in malicious mode for a long time. if improper clock is setup, you can break your lcd by presence of DC voltage on the pixel cells.

[oxiroxt]

Hi,

I finally managed to make it boot!

It will boot in these cases:
*From internal memory(NOT 8/16gb mem):
*Without a MicroSD card inserted: Will boot MOST of the time, just not always
*With a MicroSD card inserted: Will boot SOMETIMES, sometimes not
*Connected via usb with activesync activated in the device to haretconsole:
It will boot from internal memory, as well as from the 8/16gb mem, by running the corresponding default script from haretconsole. Note that I have only tried once for each of these two later cases.

It won't boot:
*From 8/16gb memory
*From MicroSD card

At least, these cases apply to me.

Maybe you could try this to see if it boots, chomi7, and report :) As for the other people who made it boot before, maybe you want to confirm if this is the case? I mean, confirm you were making it boot from the internal memory... (possibly without a micro sd card inserted) :)


Some spare thoughts:

*dejfson: Someone posted a link in modaco to a samsung omnia service manual, with lots of info about the hardware. Here's the url to that thread: http://www.modaco.com/content/i9x0-omnia-http-omnia-modaco-com/276182/samsumg-omnia-service-manual-leaked/ (Note that I'm not directly linking to the manual itself). I was hoping to find some useful info there to rewrite a driver for the screen if necesary. I'll be more than happy if you can do that earlier, as it will take a lot of time to me, or forever in the worst case :D

*I've read throu a thread about the guy who ported linux to ipaq214, that is Oliver Ford. I came to the conclusion that if you modify haret to make it recognize the device properly instead of as a "Default device", you should be able to get GPIOs readings and such... I don't see why doing simply that should work... It seems too simple. Again, maybe it's not that simple to make the changes to haret in order for it to recognize the device properly... I just don't know. Someone should look into this. I think it could prove useful.

*Even if we get a readable screen I feel that we should aim at communicating with the device so we can test things easily and quickly. My main concern is the user input in terminal, as the device doesn't have a hardware keyboard. I don't know if there are software keyboards for text mode nor how much effort that will take to implement, but I'm guessing a means of communicating with a pc would be easier than that. I'm thinking this may be even more important than solving the screen issue... well, if it weren't because of the risk of having the screen at bad sync for a long while... Maybe we can turn it off(the haretconsole commands for this will work) and focus on the communicating issue.

*I think I'm getting a kernel panic "unable to open root device" blah blah, but I'm not sure, as I can barely read the screen. Are you guys getting that too?

Oh, by the way I have just tried the ipaq214 image. Tomorrow I'll compile one and try it...

Cheers,
oxi

[z720]

i successful to fix the screen resolution,
I use the ipaq214 config as normal, open the /arch/arm/mach-pxa/hpipaq214-lcd.c changed the .xres = 240 and .yres = 400, .pixclock = 96153.
after make Image i'm able to see the penguin. Not sure this is correct:confused:
But the kernel stop at "Driver 'sd' needs updating - please use bus-type method.
I dont think this is an issue.
Any idea?

http://i2.photobucket.com/albums/y15/just4it/Photo0201.jpg

[Verrigan]

I don't know if this will help with the SD card issue or not... But the android image from Majister's Titan setup handled my 8GB msdhc card just fine, and every other kind of card I threw in my titan when I had it. Majister's Titan Android: http://magister.ipsys.net/lang/en/projects/android-for-titan/

I can't wait to see Android on my Omnia.. Looks like progress is being made rather quickly. :)

[us1111]

i successful to fix the screen resolution,
I use the ipaq214 config as normal, open the /arch/arm/mach-pxa/hpipaq214-lcd.c changed the .xres = 240 and .yres = 400, .pixclock = 96153.
after make Image i'm able to see the penguin. Not sure this is correct:confused:
But the kernel stop at "Driver 'sd' needs updating - please use bus-type method.
I dont think this is an issue.
Any idea?

http://i2.photobucket.com/albums/y15/just4it/Photo0201.jpg

Nice going! Out of curiousity, how did you determine the pixclock?

[z720]

I'm now able to fix the Driver "sd" issued. Just commented out the scsi driver, which are not use at all.
Now kernel able to boot until portion looking for root folder.
I try to fix the default.txt with many option but still fail to get the kernel found the root.
i'm using micro sd, so my sd detect as mmcblk0. Im partition the sd to 2 partition, 1 is mmcblk0p1 for Fat, another mmcblk0p2 for ext3.
so I try to set the
root=/dev/mmcblk0p2 -- fail
root=uuid -- fail
root=/dev/mmcblk0 -- fail

i'm out of idea but will still keep trying other method.

helo us11111
try to get the ipaq214 config from your mentioned site.
then goto /arch/arm/mach-pxa/hpipaq214-lcd.c
search for .yres ; .xres an .pixclock.

.pixclock = 96153,
//.pixclock = 110000,
.xres = 240,
.yres = 400,
.bpp = 16,

and recompile the kernel.
Hope this help.

[oxiroxt]

Hey, great job, z720!

I'm going to try this right now :)

pixclock = hfreq * htotal ( http://linuxconsole.sourceforge.net/fbdev/HOWTO/3.html )
We're missing the horizontal "refresh" rate. Couldn't find anything about the lcd, beyond its s/n.

I read that lcd screens do not actually have a refresh rate because they just keep displaying an image continuously for as long as there isn't any changes in the image. So I guess in such cases the hfreq value refers to the times the lcd can update in a second. Then I don't see how setting a low hfreq value could damage the lcd... Also, I calculated the freq being used by the ipaq214 and it seems way too high o_O I just don't know

Cheers,
oxi

[us1111]

I'm now able to fix the Driver "sd" issued. Just commented out the scsi driver, which are not use at all.
Now kernel able to boot until portion looking for root folder.
I try to fix the default.txt with many option but still fail to get the kernel found the root.
i'm using micro sd, so my sd detect as mmcblk0. Im partition the sd to 2 partition, 1 is mmcblk0p1 for Fat, another mmcblk0p2 for ext3.
so I try to set the
root=/dev/mmcblk0p2 -- fail
root=uuid -- fail
root=/dev/mmcblk0 -- fail

i'm out of idea but will still keep trying other method.

helo us11111
try to get the ipaq214 config from your mentioned site.
then goto /arch/arm/mach-pxa/hpipaq214-lcd.c
search for .yres ; .xres an .pixclock.

.pixclock = 96153,
//.pixclock = 110000,
.xres = 240,
.yres = 400,
.bpp = 16,

and recompile the kernel.
Hope this help.


Hmm.. Don't you need the scsi driver to acces the SD card itself? Also, could you please post your .config file? I lost mine while cleaning up my virtual machines :(

By the way.. I also updated the first post with information found in several posts.. I used your screenshot z720, hope you don't mind?

[giorgosm]

I have found this for ASUS P535. Im not so sure but couldnt be work for omnia also?

Here is the youtube video: http://www.youtube.com/watch?v=0GZwguPJCmI

Execution Files for ASUS P535: http://cid-6fac71b8e8cee5b6.skydrive.live.com/self.aspx/android/AndroidOnP535.rar

Seems that more functions work on Asus.
There are steps how to do it but shown for Asus. I guess it can be similar to all WM devices.

There are nice instructions here but i dont have the time to work on this one and not so experienced on Linux.

Check the instructions here: http://sites.google.com/site/siteofhx/Home/android/android-porting-steps/english

[us1111]

Looks like I can see the partitions on the memory card:

here are the available partitions:
b300 5970432 mmcblk0 driver: mmcblk
b301 5966336 mmcblk0p1
b308 7864320 mmcblk1 driver: mmcblk
kernel panic... Unable to mount root fs..

I have a 6GB storage card with 1 partition, so that works out! Next thing is repartition and reformat with ext2 and compile a busybox init/shell...

Also slowed down the kprints so you can actually read the messages that normaly fly-by:

enable CONFIG_BOOT_PRINTK_DELAY

add the following to the kernel arguments:

set kernel "Image"
Set ramaddr 0xa0000000
Set RAMSIZE 0x04000000
Set cmdline "root=mmcblk0p1 rootdelay=10 rw init=/ash lpj=loops_per_jiffy boot_delay=100"
Set mtype 1653
Set kernelcrc 0
Set fbduringboot 1
Set forcefbduringboot 1

Bootlinux

[oxiroxt]

Argh... back to start :(

I am unable to boot my self compiled kernel. It compiles fine, but it just won't work. Tried with the default .config, and with arch/arm/configs/zylonite_defconfig and arch/arm/configs/littleton_defconfig. I just did "make menuconfig", save and exit, then "make Image". Of course, I have alredy made the changes regarding the toolchain and platform to Makefile.

I get not flash light, no nothing, just a dull "Jumping to kernel..." :(

Help please? :_(

Glad to hear that us1111.
Edit: Would you lend me your .config file, please? Or point out what I might be doing wrong? Thanks

BTW, shouldn't we register a new mtype and derive from Oliver's work, if we're already modifying drivers?

[us1111]

When you do a


# make vmlinux
# file vmlinux
vmlinux: ELF 32-bit LSB executable, ARM, version 1 (SYSV), statically linked, not stripped


Do you see the same? I've attached the config.txt (rename to .config ofcourse).. This config works for me on "my storage". Also when I put haret and the kernel on local storage, I see the internal 8GB as mmcblk1.. However, it gives an error -110 I/O error on this storage device.

It sees the storage card, but cannot mount it somehow :( "Unable to mount root fs on unknown-block"

[oxiroxt]

Thank you very much us1111, your config file worked a treat :)

With the default config file (the one I got by simply running "make menuconfig" when there's none before), I get:
vmlinux: ELF 32-bit LSB executable, ARM, version 1, statically linked, not stripped
It's just missing the "(SYSV)" part afer "version 1".
With your config file I get exactly the same as you :)

I'll make a diff of your config file and the other one. I have so much to learn.

I made the changes that z720 said, and can see the screen correctly now :)

I'm a little bit worried about the pixclock setting. I don't know how much of an impact this has, nor how dangerous would be to leave the lcd on with an incorrect pixclock setting for a long time... I'd really like to know so I can breath easily :D

Unfortunately it still doesn't boot for me from "my storage", nor it does boot when a MicroSD card is inserted, but it does boot from the normal storage, so I guess it's okay to bypass this for the moment and focus on further development.

As for mounting, I'll try to create an ext partition on "my storage" and try to mount that. I just don't know how yet, lol. I remember trying a distro on my old htc uni, that didn't require any ext partition to run. I think it used a file in vfat to work as a partition. I guess it did that the same way virtual machine emulators do.

Once again, thanks us1111.

P.S: Can you hear a quiet beep too when you put the phone on your ear?

[us1111]

Thank you very much us1111, your config file worked a treat :)

With the default config file (the one I got by simply running "make menuconfig" when there's none before), I get:
vmlinux: ELF 32-bit LSB executable, ARM, version 1, statically linked, not stripped
It's just missing the "(SYSV)" part afer "version 1".
With your config file I get exactly the same as you :)

I'll make a diff of your config file and the other one. I have so much to learn.

I made the changes that z720 said, and can see the screen correctly now :)

I'm a little bit worried about the pixclock setting. I don't know how much of an impact this has, nor how dangerous would be to leave the lcd on with an incorrect pixclock setting for a long time... I'd really like to know so I can breath easily :D

Unfortunately it still doesn't boot for me from "my storage", nor it does boot when a MicroSD card is inserted, but it does boot from the normal storage, so I guess it's okay to bypass this for the moment and focus on further development.

As for mounting, I'll try to create an ext partition on "my storage" and try to mount that. I just don't know how yet, lol. I remember trying a distro on my old htc uni, that didn't require any ext partition to run. I think it used a file in vfat to work as a partition. I guess it did that the same way virtual machine emulators do.

Once again, thanks us1111.

P.S: Can you hear a quiet beep too when you put the phone on your ear?

Glad to see it's working!! The more look at this, the better..

About mounting.. You should at least see messages about an MMC card being found. There should be a message about "driver mmcblk" and earlier in the process it should load the MMC driver.

If i'm correct, booting should be slowed down by the printk_delay and the kernel arguments (default.txt).

If we could somehow manage to read from a file or partition, we're at the point of rewriting drivers. From there on, things could go very fast.

I compiled an arm version of busybox with a shell, rclinux and init. It should run, if we only could recognize and use a partition.. You got me thinking however, maybe we can use an initrd.. Gonna try that asap.

About the beep, i think that has to do with the wrong pixclock.. Maybe someone smarter than me can figure out how to calculate the pixclock. Maybe read it from withing a running windows even..

[us1111]

YAH!!

I've been able to boot into a ramdisk and get the "press enter to enable console" message!!

Cross Compile busybox with static linking:

cd busybox-1.13.2/

Change Makefile to have the cross compiler active again:


ARCH ?= arm
CROSS_COMPILE ?= /usr/local/arm-2008q3/bin/arm-none-linux-gnueabi-


Make the static busybox (make menuconfig first and disable all non wanted busybox commands, leave ash, init, rclinux and telnetd active for later use!):

# LDFLAGS="--static" CFLAGS="--static" make


root@JEOS:/ANDROID/busybox-1.13.2# file busybox
busybox: ELF 32-bit LSB executable, ARM, version 1 (SYSV), statically linked, stripped


Copy the busybox to the new initrd directory:

cp busybox /ANDROID/initrd
cd /ANDROID/initrd

ln -s busybox init
ln -s busybox ash
ln -s busybox rclinux
mkdir dev; mkdir sys ; mkdir proc

Make the initrd.gz ramdisk fromout the initrd directory
find . | cpio --create --'format=newc' | gzip >../initrd.gz

Copy it to the directory in which the kernel is placed...

Change default.txt cmdline:
Set cmdline "root=/dev/ram0 ramdisk_size=8192 rootdelay=5 rootwait rw init=/ash lpj=loops_per_jiffy boot_delay=100"


Boot and see why we need a keyboard now :( Next step is maybe auto configure network and start telnetd in the ramdisk :) Also, USB events are nicely logged on the console (attach/detach laptop) so in theory we have USB...

[z720]

good job us1111..

hope to see the linux screen on omnia soon..:cool:

[bootsan]

Hi everybody !!!

Very Good Job us1111 !!!! :)

Could you please upload your Image and busybox files ?
Or just the config file for the 2.

Thanks in advance !!

[roboticienfr]

Hi Everybody!

I'm also interested in the Image :) Could you upload it please.
Thanks in advance ;)

PS : It's my first message in this forum and I follow it every day. I want to congratulate you for all these jobs.

[us1111]

Hereby the files needed to run.. These files are for your own risk.

Files included:
default.txt
earlyharetlog.txt
image
initrd.gz

You'll need the haret from the first post:

http://www.oliford.co.uk/hpipaq214/files/h...aq214-aug08.exe

The initrd is changeable so you can test stuff yourself.. The used config file is posted earlier..

Please use the files and info for further development!

[z720]

hi us1111 try to download this "initrd-angstrom-console"
@
http://dx.infernix.net/kaiser/initrd-angstrom-console

you should able to see something excited :cool:

Currently dont have extra phone to snap pic, try to upload by this weekend.

with this cmdline

set CMDLINE "root=/dev/ram0 ro init=/init console=tty0 mem=94M"

but.......... stuck at touchscreen...:(

[oxiroxt]

Hi all,

I've got some news for you. First off, let me thank tmzt, without his help I couln't have accomplished anything of this. So thank you tmzt, and you're most than welcome to post on this thread.

*New values for pxafb_mode_info structure. No pixclock confirmation for the moment.

*No more flashing nor vibration while booting. This should avoid some potential damage.

*We can now mount an ext2 partition on "my storage". Not in the external memory card yet.


New values for pxafb_mode_info structure.

Open arch/arm/mach-pxa/hpipaq214-lcd.c , and chage "struct pxafb_mode_info" to look like this:
static struct pxafb_mode_info hpipaq214_mode = {
.pixclock = 96153,
.xres = 240,
.yres = 400,
.bpp = 16,
.hsync_len = 8,
.left_margin = 8,
.right_margin = 8,
.vsync_len = 4,
.upper_margin = 38,
.lower_margin = 38,
.sync = 0,
};

How did we get this?:
tmzt asked me to paste this code on haretconsole:
pd 0x44000000 0x20
With the output:
44000000 | 03b008f9 07071cef 26260d8f 04700014 | ..........&&..p.
44000010 | 8400fe92 3f3f3f3f 00000000 00000000 | ....????........
...and a program (decoder?) I don't know about, he determined the correct margin values for pxafb_mode_info. I think it should have given some info about the pixclock, but unfortunately it didn't. tmzt suspects this info may be elsewhere in the memory.


No more flashing nor vibration while booting.

Open arch/arm/mach-pxa/hpipaq214.c , and change hpipaq214_init to look like this:
static void __init hpipaq214_init(void)
{
hpipaq214_init_lcd();
hpipaq214_init_mmc();
/*
hpipaq214_init_mfp();
hpipaq214_init_misc();
hpipaq214_init_lcd();
hpipaq214_init_mmc();
hpipaq214_init_keypad();
hpipaq214_init_nand();
hpipaq214_init_usb();
hpipaq214_init_audio();
hpipaq214_init_power();

//add the various platform devices
platform_add_devices(hpipaq214_devices, ARRAY_SIZE(hpipaq214_devices));
*/
}

Open arch/arm/mach-pxa/hpipaq214-lcd.c , and change hpipaq214_init_lcd to look like this:
void __init hpipaq214_init_lcd(void)
{
/* int err;

platform_device_register(&hpipaq214_backlight_device);

err = gpio_request(gpio_lcd_setup, "LCD setup gpio");
if(err){
printk("Unable to register LCD setup gpio (%i)\n",gpio_lcd_setup);
gpio_lcd_setup = -1;
}else{
gpio_direction_output(gpio_lcd_setup, 1); //keep it on for now!
}
*/
set_pxa_fb_info(&hpipaq214_lcd_info);
}

What's this for?:
As you can see, we're commenting out a lot of hardware initialization. This will prevent potentially damaging the omnia and let us focus on what we need for the moment. The mmc initialization is needed for the next step, so it's left uncommented.
With the above changes I'm finally able to boot from the "my storage" device, and I don't quite recall whether I'm able to boot from the card as well...

We can now mount an ext2 partition on "my storage".

Connect your omnia to the computer using the usb cord, and in winmo select "my storage" as usb connection, instead of activesync or the external card.

Make a backup of the complete "my storage" device on your computer. In my computer this was detected as /dev/sde, with /dev/sde1 being an extended partition, and /dev/sde5 being a logical vfat partition. I made the backup using dd, like this: "dd if=/dev/sde of=/home/oxi/mybackup.bin". This kind of backup (a whole device) will ensure you're keeping not only the partitions content, but the partition table as well, so you should be ok if you ever want to restore. This took around an hour to complete for my 16gb mem. Maybe you can speed up the process by using high blocksize value in dd.

Make the new partition/s on the "my storage" device. You may want to use fdisk or cfdisk for this. Since the default vfat partition is logical, I kept the extended partition, created a new logical 2gb ext2 partition at the end and then created a new logical vfat partition at the beginning. I did this so to prevent possible problems if the omnia/winmo couldn't rightly handle primary partitions on this memory. Now I must say I'm not that sure I did the right thing. Now winmo is able to see the ext2 partition and depicts it as "my storage2"; also, my computer will mount it as an vfat if no type is specified. So I wouldn't recommend this partition schema. I will be repartitioning the "my storage" device to have just two primary partitions, the first one being vfat, and the other one ext2, ASAP, because I don't really like all this behaviour. But I can't recommend this second schema as I have not tried it yet. Note that the default vfat partition is of type: 0b, not the usual 06.

Edit: Of course, create the new filesystems on the partitions.
mkfs.vfat /dev/sdXY
mkfs.ext2 /dev/sdXZ
I have now tried the second schema, that is, creating two primary partitions. Results are exactly the same. For some strange reason, when you disconnect the usb cord, winmo has the bad habbit of writing two files in each partition, no matter if it's an ext2 partition, winmo will write them to it in FAT format. This apparently doesn't pose any problems, but just to be on the safe side I run a fsck.ext2 on the partition everytime before I mount it on my computer.

You can now deploy a busybox(or whatever) on the ext2 partition. Just set the cmdline of default.txt accordingly, by setting the proper init parameter, and setting the root to your ext2 partition.
If you're using an extended, and logical partitions:
root=mmcblk0p6 1 is the extended partition, 5 is the first logical partition (vfat in my case), 6 is the second logical partition (ext2 in my case)
If you're using primary partitions:
root=mmcblk0p2 1 is the first primary partition (the vfat partition, maybe), 2 is the second primary partition (the ext2 partition, maybe)
Note that if you have an external memory card inserted, you will need to use mmcblk1 to access the "my storage" device, because even if we can't use yet the external card, it is detected and named as mmcblk0. If no card is inserted then the "my storage" device will be named mmcblk0, and the examples above should work for you.

Edit: Set rootdelay parameter on cmdline to an appropriate value, so to give time for the memories to be detected. A value of 10 is more than enough.

Now I feel we should be directing our efforts on trying to establish a connection with the computer, as a means of communicating with the device without having to constantly reboot, etc. Maybe start by uncommenting the usb initialization related stuff and set up a telnetd or ssh in a busybox.

I hope I'm not leaving anything behind...

Once again, thanks go to tmzt

Needless to say, I don't take any responsibility for any damage, data loss, etc. you may get by using this info.

Cheers,
oxi

[us1111]

Now I feel we should be directing our efforts on trying to establish a connection with the computer, as a means of communicating with the device without having to constantly reboot, etc. Maybe start by uncommenting the usb initialization related stuff and set up a telnetd or ssh in a busybox.


I agree... Does anyone know if we can configure TCP/IP on the USB cable?

[oxiroxt]

If I let the usb initialization uncommented, and set the config file to compile OHCI support it won't boot for me. Do you experience this problem too?

When I connect the device to my computer it's detected as a UHCI device... I don't know a thing about this, but I've read some devices implement UHCI and others OHCI depending on the motherboard. Could this mean the omnia board can only make the usb work as UHCI? If so, shouldn't we use another usb driver instead of that of the ipaq214? (There are several references to OHCI in the code)

Cheers,
oxi

[dejfson]

could somebody please post working .config and defaut.txt wrt to git gernel of hpipaq mentioned here? For me it was somehow working before, now i did some changes and it does not boot anymore

thanks

[us1111]

could somebody please post working .config and defaut.txt wrt to git gernel of hpipaq mentioned here? For me it was somehow working before, now i did some changes and it does not boot anymore

thanks

Actually, we did that allready! A few posts back is the complete haret environment and before that the config...At your service!

[dejfson]

Thanks. I know about these. But from unknown reasons on one computer do not even compile:


<stdin>:1325:2: warning: #warning syscall ppoll not implemented
<stdin>:1365:2: warning: #warning syscall epoll_pwait not implemented
CHK include/linux/compile.h
CC arch/arm/mach-pxa/pxa3xx.o
arch/arm/mach-pxa/pxa3xx.c:230: error: 'CKEN_MMC3' undeclared here (not in a function)
make[1]: *** [arch/arm/mach-pxa/pxa3xx.o] Error 1
make: *** [arch/arm/mach-pxa] Error 2

(using arm-2008q3-72-arm-none-linux-gnueabi-i686-pc-linux-gnu.tar.bz2)

on other computer using the same compiler it compiles (different config), however it does not work and stops when haret tries to run the kernel :(

any ideas why i get compilation error? anyone had the same issue?

thx
d.

[oxiroxt]

Hi, dejfson

CKEN_MMC3 seems to be defined in these files:
$ grep -ir "CKEN_MMC3" .
./include/asm/arch/pxa3xx-regs.h:#define CKEN_MMC3 5 /* < MMC3 Clock Enable */
./include/asm/arch-pxa/pxa3xx-regs.h:#define CKEN_MMC3 5 /* < MMC3 Clock Enable */
./include/asm-arm/arch/pxa3xx-regs.h:#define CKEN_MMC3 5 /* < MMC3 Clock Enable */
./include/asm-arm/arch-pxa/pxa3xx-regs.h:#define CKEN_MMC3 5 /* < MMC3 Clock Enable */
Maybe your Makefile is not pointing to the right include directory?
Maybe you have en environment variable set that is affecting the include directory passed onto gcc?

Try this:
make clean
make V=1 Image | grep "^ /.*gcc"The include parameter (-I) should be pointing to the include directory in the same level as Makefile, that is: -Iinclude

I'm attaching some files for you. Namely: .config, default.txt, Image and initrd.gz. That initrd and default.txt should get you a root prompt (#). Quite useful without a keyboard, ain't it? :D
Sorry, but for some strange reason it won't let me upload the zip file. BTW: How does one cross out some words? :confused:

I have disabled mmc support as I have been experiencing some strange behaviour lately, and I wouldn't recommend using an ext2 partition on "my storage" anymore. Stick with the initrd method for the moment :)

Also, lately sometimes all the lines in my screen will have an offset and start from the middle... I hope this doesn't mean we're damaging our screens or related hardware...

[Stefano_1986_]

Hi,
congratulations for your job!
I don't understand if is possible to start android on the omnia.
Is it now possible?
Best regards
Stefano

[z3ntn3l]

Hi,
congratulations for your job!
I don't understand if is possible to start android on the omnia.
Is it now possible?
Best regards
Stefano

Or maybe the Ubuntu-Mobile? Is there a real chance that its possible or are you guys just playin' around with some small Linux-Code?

Sorry for the dumb question but i dont understand that much in this Thread :-) But it looks good ;-)

[dejfson]

Dear all,
i've found finally what is wrong. by repeating all the steps from the first page it works. so I started to look on a difference in initialization of lcd. In fact, oxiroct recommends another update of init of the display:

static void __init hpipaq214_init(void)
{
hpipaq214_init_lcd();
hpipaq214_init_mmc();
/*
hpipaq214_init_mfp();
hpipaq214_init_misc();
hpipaq214_init_lcd();
hpipaq214_init_mmc();
hpipaq214_init_keypad();
hpipaq214_init_nand();
hpipaq214_init_usb();
hpipaq214_init_audio();
hpipaq214_init_power();

//add the various platform devices
platform_add_devices(hpipaq214_devices, ARRAY_SIZE(hpipaq214_devices));
*/
}


this DOES NOT WORK FOR ME.
From unknown reasons it is mandatory to call initialization of audio as well, thus my routine looks like:


static void __init hpipaq214_init(void)
{
/* hpipaq214_init_mfp(); */

// when misc running on omnia, it turn on the flash-lamp of the
// camera. therefore one of the gpios used in this routine turns it on
/* hpipaq214_init_misc(); */
hpipaq214_init_lcd();
hpipaq214_init_mmc();
/* hpipaq214_init_keypad(); */
/* hpipaq214_init_nand(); */
/* hpipaq214_init_usb(); */
hpipaq214_init_audio();
/* hpipaq214_init_power(); */

//add the various platform devices
platform_add_devices(hpipaq214_devices, ARRAY_SIZE(hpipaq214_devices));
}

If audio init is called, the kernel works. Next step for me is to try initrd + busybox, then tcpip over usb if possible

hope it helps a bit

[us1111]

Or maybe the Ubuntu-Mobile? Is there a real chance that its possible or are you guys just playin' around with some small Linux-Code?

Sorry for the dumb question but i dont understand that much in this Thread :-) But it looks good ;-)

Well, the fun thing is that if we get the kernel working right (including drivers :cool:) then you can compile near to everyting for the phone.. As long as it doesn't take too much memory..

For example.. I have an Asus500g router.. The thing runs a custom mips Linux environment where I compiled darkstat to get a nice html page about my monthly internet usage..

As soon as the kernel works, evey binary/library you compile could run... The drivers are the hardest part in this..

The next step for example is to get USB working right and maybe do TCP/IP or TTY..

[us1111]

Found the following, Serial over USB is also a possibity
http://lists.denx.de/pipermail/u-boot/2004-October/007585.html:

On the PC and phone side, you need to configure the kernel to support USB
serial devices. Assuming you are using "make menuconfig"
or "make xconfig", go to "USB Support" section and enable the options
as follows ("M" means "enable as a loadable module"):

If, and only if, "Support for USB is set to <N>, then:
- Support for USB <M>

Also enable the /proc filesystem for USB:
- Preliminary USB device filesystem <Y>

Then choose a driver for your USB controller and enable it as module,
i.e. exactly one of the following:

- UHCI (Intel PIIX4, VIA, ...) support <M>
or
- OHCI (Compaq, iMacs, OPTi, SiS, ALi, ...) support <M>

Then go to "USB Serial Converter support" subsection and enable:

- USB Serial Converter support <M>
- USB Generic Serial Driver <Y>

Next, recompile the kernel and install kernel itself and modules as
usual.



On the host side, you need to load kernel modules, exactly in the
following order, by typing:

insmod [host controller driver]
insmod usbserial vendor=0x0451 product=0xe003


Then re-plug the USB cable and examine log files (usually somewhere
in
/var/log, check your /etc/syslog.conf) on the host system. You should
see something like the following (date and host name fields are
skipped):

kernel: hub.c: USB new device connect on bus1/1, assigned device
number 9
kernel: usb.c: kmalloc IF c0f74ec0, numif 1
kernel: usb.c: new device strings: Mfr=1, Product=2,
SerialNumber=0
kernel: usb.c: USB device number 9 default language ID 0x4e3e
kernel: Manufacturer: Texas Instruments
kernel: Product: TI PET Bootloader
kernel: usbserial.c: Generic converter detected
kernel: usbserial.c: Generic converter now attached to ttyUSB0
(or usb/tts/0 for devfs)
kernel: usb.c: serial driver claimed interface c0f74ec0

Now you can run minicom with your usb configuration: 'minicom usb'.
You should
see the first few lines of your u-boot console.

[oBADGERx]

Would it be possible to see the current boot status in a video?
Maybe someone could upload one to youtube please?

I just want to see how this works. I really want Android on my omnia :D

[AkshayGenius]

Looking good guyz, although I don't understand what your're doing, it seems to be pretty usefull.

Keep it up,
Akshay

[pistax]

hello to everyone and very compliments for the good work made!
I'm sorry for my english
I need help about make images of kerner.
I follow the instructions in the first page of this post but i have a problem with the cross compiler.now i explain:i have installed the cross compiler arm-2008q3-72-arm-none-linux-gnueabi-i686-pc-linux-gnu.tar.bz2 but in the folder /usr/local i don't find no folder xscale:confused:
how to change written the make file

ARCH ?= arm
CROSS_COMPILE ?= /usr/local/xscale/arm-2008q3/bin/arm-none-linux-gnueabi-

but i find the folder /usr/local/arm-2008q3/bin/arm-none-linux-gnueabi- so i changed the make file in
ARCH ?= arm
CROSS_COMPILE ?= /usr/local/arm-2008q3/bin/arm-none-linux-gnueabi-


but when i try to build make image i find the following error:

andrea@ubuntu:~/Desktop/android/v4$ make image
HOSTCC scripts/basic/fixdep
HOSTCC scripts/basic/docproc
HOSTCC scripts/kconfig/conf.o
HOSTCC scripts/kconfig/kxgettext.o
SHIPPED scripts/kconfig/zconf.tab.c
SHIPPED scripts/kconfig/lex.zconf.c
SHIPPED scripts/kconfig/zconf.hash.c
HOSTCC scripts/kconfig/zconf.tab.o
HOSTLD scripts/kconfig/conf
scripts/kconfig/conf -s arch/arm/Kconfig
make: *** No rule to make target `image'. Stop.
andrea@ubuntu:~/Desktop/android/v4$




thanks to everyone by by

[dejfson]

pistax, to your questions:

for first problem you did right. compiler can be installed wherever. I have it in /opt/arm, thus my path in Makefile is /opt/arm/bin/arm-none-linux-gnueabi-

to second question: linux is case sensitive. Therefore you have to call it 'make Image'. Just in case, 'make' itself works as well. Your image is then stored in ./arch/arm/boot/Image

hope it helps

[dejfson]

here you go:

http://www.youtube.com/watch?v=5bWSX3WDcrU

[dejfson]

hi us1111,
i have few questions. could you post your config from busybox please? i'm not getting the same results. there is something not quite right about serial port devices. when system boots, it declares existing ttyS0, ttyS1 and ttyS2 (FFUART,BTUART,STUART), however in the recipe you copy from your system pc folders to ttys1..ttys4. these are not existing on my system (gentoo), where I have only ttyS0..ttyS3. when I create links to initrd/dev/ttyS0, or I make them by mknod and try to run the system from such initrd, i get 'almost' the same results as you, i.e. it says 'Please enter to activate this console...', however it does not stop there, instead it continues complaining about missing /dev/tty4 (?). I have no clue where the /dev/tty4 comes from when I declared everywhere only serials in form /dev/ttySx. Therefore I think that this is a problem of busybox configuration.

Another unresolved issue for me is the /etc/init.d/rcS file. I tried to compile busybox with stty and i have created in the ramdisk the rcS file containing queries for these serial ports:

rcS:
/stty -F /dev/ttyS0
/stty -F /dev/ttyS1
/stty -F /dev/ttyS2

to my surprise, whatever I did, either the system claimed that 'no such file or directory', or in one particular case I got 'permission denied' error.

by this exercise I wanted to see whether the serial ports are correctly recognized by system and what is their setting

i guess if we want to use serial console, it must be the one connected to ttyS0 (FFUART) as the others are dedicated to other things....

any ideas?

d.

[us1111]

Hi, I've included my complete /dev files. Hope this helps. About the busybox executable.. I've only disabled what I don't need. Maybe enable as much as possible may be a better idea in the beginning..

[us1111]

And the busybox config...

[dejfson]

ok, previous problem with tty was resolved. stupid me. i was supposed to copy/mknod tty0-tty5, not ttyS0. console now works for me, I have compiled busybox with depmod stuff to be able to insert serial module and made /etc/init.d/rcS script as follows:

#!/bin/sh
# configuration file for initramdisk
# let's see what is the default configuration for serial ports:
/bin/echo "Starting sysinit script for kerner"
/bin/uname -a
/bin/echo "Inserting usb serial:"
/sbin/depmod -ae
/sbin/modprobe /lib/modules/2.6.26-rc8-arm-dejfson/kernel/drivers/usb/serial/usbserial.ko vendor=0x0451 product=0xe003
/bin/echo "creating node:"
/bin/mknod /dev/ttyUSB0 c 188 0
/bin/echo "Sysinit finished"


it works until modprobe. the modprobe fails with 'operation not permitted'. have no clue why.
of course consecutive mknod fails as well with 'operation not permitted'. it is questionable whether second error is due to non-existent ttyUSB0 link from serial driver, or it is caused by the same thing as modprobe call.

ideas?

[us1111]

ok, previous problem with tty was resolved. stupid me. i was supposed to copy/mknod tty0-tty5, not ttyS0. console now works for me, I have compiled busybox with depmod stuff to be able to insert serial module and made /etc/init.d/rcS script as follows:

#!/bin/sh
# configuration file for initramdisk
# let's see what is the default configuration for serial ports:
/bin/echo "Starting sysinit script for kerner"
/bin/uname -a
/bin/echo "Inserting usb serial:"
/sbin/depmod -ae
/sbin/modprobe /lib/modules/2.6.26-rc8-arm-dejfson/kernel/drivers/usb/serial/usbserial.ko vendor=0x0451 product=0xe003
/bin/echo "creating node:"
/bin/mknod /dev/ttyUSB0 c 188 0
/bin/echo "Sysinit finished"


it works until modprobe. the modprobe fails with 'operation not permitted'. have no clue why.
of course consecutive mknod fails as well with 'operation not permitted'. it is questionable whether second error is due to non-existent ttyUSB0 link from serial driver, or it is caused by the same thing as modprobe call.

ideas?

Nice work so far! A few things that pop up in my head, maybe there's something that could help:

- Does depmod give any errors?
- Is your kernel module from the same build time as the kernel itself?
- Just to be sure, are you sure you're root?
- Is the RAm filesystem read/write?

You could try to see what dmesg is saying.. So maybe a tail of dmesg at the end of your rcS script?

If all else fails.. What about compiling the usbserial into the kernel for now? As soon as we have tty access to the system, we can debug a LOT easier.

[oxiroxt]

Hi there,

No progress on my side... :mad:
I've crosscompiled lsusb, lspci(yeah, so what -_-) and lshw to no avail. Got no sensible info at all, and darn you bet I had to make some tweaks to make them compile. Just trying to get some info. Maybe this was a stupid idea and waste of time. :o

Of course I mount /proc, and "ls -lhR /proc" will throw some directory hierarchy of some sort. Maybe I should save mounted /proc to the "my storage" partition so I can examine it thoroughly...
I've included all usb serial and network related stuff in the kernel...

I just don't know what direction to take from here (maybe try a usb driver that makes use of uhci), but I think that if the kernel can't see the device usb ports, nothing that makes use of usb will work. Maybe not.

Looking forward to your comments,
oxi

[dejfson]

okay, i've found the problem with modprobe. it did not incude modues due to improper owner of the files. when i have installed the modules into initrd, i've put them under my login. that's wrong. you have to chown -R root:root all the modules

now i'm fighting with usb gadget driver on omnia to be able to use usb over serial - if possible. so far no success as omnia refuses to load g_serial module
d.

[dejfson]

hi oxitoxt,
what you mean no sensible info? did lsusb/lspci return some information? or it just crashed?
d,

Hi there,

No progress on my side... :mad:
I've crosscompiled lsusb, lspci(yeah, so what -_-) and lshw to no avail. Got no sensible info at all, and darn you bet I had to make some tweaks to make them compile. Just trying to get some info. Maybe this was a stupid idea and waste of time. :o

Of course I mount /proc, and "ls -lhR /proc" will throw some directory hierarchy of some sort. Maybe I should save mounted /proc to the "my storage" partition so I can examine it thoroughly...
I've included all usb serial and network related stuff in the kernel...

I just don't know what direction to take from here (maybe try a usb driver that makes use of uhci), but I think that if the kernel can't see the device usb ports, nothing that makes use of usb will work. Maybe not.

Looking forward to your comments,
oxi

[oxiroxt]

hi oxitoxt,
what you mean no sensible info? did lsusb/lspci return some information? or it just crashed?
d,

Hi, dejfson
They do work fine, it's just there's no output from lsusb nor lspci :(
lshw will return just this (copied by hand):
_none_
description: Computer
width: 32 bits
*-core
description: Motherboard
physical id: 0
*memory
description: System memory
physical id: 0
size: 106MiB
*cpu
physical id: 1
bus info: cpu@0

No much use :(

Cheers,
oxi

[dejfson]

Dear all,
i've tried to dig a bit into usb-serial conversion. Well, in fact i did not make it running. Did you, us1111, made it running? I think that there is one major problem. The USB to serial works (according to what i understood) in the way, that on the phone one has to modprobe serial gadget (g_serial module). Then on PC you do modprobe usbserial with some fancy parameters and you should get a new usb device registered so you can use it with minicom.

I've tested to import the g_serial device. It does not work and when modprobed, it claims that 'device does not exist'. This seems to me rather logic as when one compiles the usb gadget, the correct chipset must be provided. The problem is, that omnia contains USB3319 chip to perfoms the usb communication. The gadget driver for this chip was not written so far. Thus I guess that until we are capable to communicate to usb3319, there is no way to make it running. Am i right?

another stuff is, that apparently some series of ipaq21x have this chip as well. However i was looking into sources for usb for ipaq and i didn't find any info about this chip..

any ideas?

[Stefano_1986_]

Hello,
I don't know if this news may be useful,
but look here (http://www.generalmobile.com/new/Default.aspx?PageName=Products&ProductId=200).
This phone is similar to our omnia and its operating system is android.
processor OMNIA = Marvell PXA 312 (624 MHz)
processor DSTL1 = Marvell PXA 310 (624MHz)+NXP 5209
screen resolution OMNIA = WQVGA / 260K Colors / 240 x 400 pixels
screen resolution DSTL1 = WQVGA / 260K Colors / 240 x 400 pixels
bye

[us1111]

Dear all,
i've tried to dig a bit into usb-serial conversion. Well, in fact i did not make it running. Did you, us1111, made it running? I think that there is one major problem. The USB to serial works (according to what i understood) in the way, that on the phone one has to modprobe serial gadget (g_serial module). Then on PC you do modprobe usbserial with some fancy parameters and you should get a new usb device registered so you can use it with minicom.

I've tested to import the g_serial device. It does not work and when modprobed, it claims that 'device does not exist'. This seems to me rather logic as when one compiles the usb gadget, the correct chipset must be provided. The problem is, that omnia contains USB3319 chip to perfoms the usb communication. The gadget driver for this chip was not written so far. Thus I guess that until we are capable to communicate to usb3319, there is no way to make it running. Am i right?

another stuff is, that apparently some series of ipaq21x have this chip as well. However i was looking into sources for usb for ipaq and i didn't find any info about this chip..

any ideas?

To be honest.. I'm thinking about dumping my omnia.. I'm finding out that mine has too many quirks phone and pda wise.. Since 2 days the phone part seems to be defective.. I'm using my spare SE750i now and suddenly I can understand people as they are speaking to me through the phone..

So don't expect much input from me from now on.. I'm sorry for that... Hope very much that you get further though.. Maybe the wireless driver is an easier path?

Again, sorry for bailing out on this one and not helping much!

[whiplash000]

Wow I'm glad I found this topic. I knew someone had to be working on this. I can help you guys out by (attempting to) disassemble WM's drivers to speed up the process of porting the kernel to the Omnia's hardware. What's the project's current status?

[dejfson]

hi whisplash000,
good to have another soul to help. current status of the project is 'nothing'. it means that we have progressed so far to run linux kernel, however we do not have for the moment any means how to write by remote on ttys. i think that usb-serial way is quite complex to do for the moment. maybe wireless is the way.

if you know how to decompile xip files back into DLL, that would help a lot as wm6 contains zylonite_usb2 driver which is linked to ceddk xip. i'm not so good hacker to be able to reconstruct it in IDA and find how the driver initializes usb chip and what gpios it uses

[whiplash000]

I'll look into the usb drivers WM uses and see what I can pick up from that. Also, why not just use the touchscreen and get an onscreen keyboard? Do you need to upload stuff? Also, how do I partition my storage to hold the rootfs along with being able to use half of it with WM?
The xip you're looking for is located in the kernel, right? Where are all the drivers embedded into? I haven't been able to dump anything useful from my i910 probably because the tools were designed for the i900. If you know how to dump the kernel image, I can look into it

[z720]

I'll look into the usb drivers WM uses and see what I can pick up from that. Also, why not just use the touchscreen and get an onscreen keyboard? Do you need to upload stuff? Also, how do I partition my storage to hold the rootfs along with being able to use half of it with WM?
The xip you're looking for is located in the kernel, right? Where are all the drivers embedded into? I haven't been able to dump anything useful from my i910 probably because the tools were designed for the i900. If you know how to dump the kernel image, I can look into it

I agreed with whipash000. we need to get the touchscreen to work 1st.
Im still trying on searching for the generic touch screen kernel driver..but dont know which manufacturer..

[dejfson]

I agreed with whipash000. we need to get the touchscreen to work 1st.
Im still trying on searching for the generic touch screen kernel driver..but dont know which manufacturer..

driver for touchscreen should work. it is the same chip as in ipaq and the driver (wm9713) is there. therefore one should write down _application_ of on screen keyboard.

i've sent request for usb datasheet. if i get it, i'll try to write down the driver. meantime, investments into touchscreen keyboard is the way

[dejfson]

Hello,
I don't know if this news may be useful,
but look here (http://www.generalmobile.com/new/Default.aspx?PageName=Products&ProductId=200).
This phone is similar to our omnia and its operating system is android.
processor OMNIA = Marvell PXA 312 (624 MHz)
processor DSTL1 = Marvell PXA 310 (624MHz)+NXP 5209
screen resolution OMNIA = WQVGA / 260K Colors / 240 x 400 pixels
screen resolution DSTL1 = WQVGA / 260K Colors / 240 x 400 pixels
bye

Stefano_1986_, good hint. problem is that i did't find a single piece of information or source code on this mobile :(

[z720]

driver for touchscreen should work. it is the same chip as in ipaq and the driver (wm9713) is there. therefore one should write down _application_ of on screen keyboard.

i've sent request for usb datasheet. if i get it, i'll try to write down the driver. meantime, investments into touchscreen keyboard is the way


Im try to use the linux ramdisk rescue to install the linux once successeful boot to the below img part, i'm stuck because of touchscreen.. no keypad to choice the option :mad:
http://i2.photobucket.com/albums/y15/just4it/Photo0214.jpg

[us1111]

By the way.. Keypad is only possible if you have a running X... As far as I know.. The USB-tty/Wireless is the way to go imho..

[dejfson]

By the way.. Keypad is only possible if you have a running X... As far as I know.. The USB-tty/Wireless is the way to go imho..

well, theoretically it should be possible as well for frame buffer, right? so if we'd be able to compile e.g. directfb, then it should be ok. but this seems to me harder work than implementing usb driver.

question is whether the wifi connection works out of the box. could someone test it? ipaq is claimed to have good wifi support. we are using the same chipset

[SiLviO_]

might this help?
I'm very newbie and i dont know anything about linux but I saw some touch drivers.

http://www.elotouch.com/Support/Downloads/dnld.asp

[[opensys]]

Hello,
I try to bot the android in my omnia from a compiled source with the correct modifications, like lcd refresh, and others. Now the device stuck in fs mounting.

with the hp utility is possible to add a fs image file?

my default.txt have this lines:


set kernel "Image"
Set ramaddr 0xa0000000
Set RAMSIZE 0x04000000
Set cmdline "root=mmcblk0p1 rootdelay=10 rw init=/ash"
Set mtype 1653
Set kernelcrc 0
Set fbduringboot 1
Set forcefbduringboot 1
Bootlinux

Im now on linux at 8 years and i really interested in put the android in my omnia.

see the image in attachment.
http://www.vslinux.net/android/omnia_android.jpg

[dejfson]

;3367021']Hello,
I try to bot the android in my omnia from a compiled source with the correct modifications, like lcd refresh, and others. Now the device stuck in fs mounting.

with the hp utility is possible to add a fs image file?

my default.txt have this lines:


set kernel "Image"
Set ramaddr 0xa0000000
Set RAMSIZE 0x04000000
Set cmdline "root=mmcblk0p1 rootdelay=10 rw init=/ash"
Set mtype 1653
Set kernelcrc 0
Set fbduringboot 1
Set forcefbduringboot 1
Bootlinux

Im now on linux at 8 years and i really interested in put the android in my omnia.

see the image in attachment.
http://www.vslinux.net/android/omnia_android.jpg

Hi opensys,
so far apparently to somebody in this thread it is not recommended to boot from fs, i did not test this so far. all the attempts are still in initial ramdisk + busybox.

[pistax]

pistax, to your questions:

for first problem you did right. compiler can be installed wherever. I have it in /opt/arm, thus my path in Makefile is /opt/arm/bin/arm-none-linux-gnueabi-

to second question: linux is case sensitive. Therefore you have to call it 'make Image'. Just in case, 'make' itself works as well. Your image is then stored in ./arch/arm/boot/Image

hope it helps
Reply With Quote

i'm sorry i'm late with the answer.
thank you very much for your help;)
it' all right thanks dejfson.

[[opensys]]

ok
now i get press enter to enter in the console.
I found this was miss and is not in forum
in default.txt need the line: initrd "initrd.gz"
now have the file system

in the some last lines i get:
cannot run /etc/init.d/rcS

i create it and set execution permissions but he do not detect it.
I also get errors that can't get the /dev/ttyX. I create it on dev no more show up in console.

this script will be able do run some programs in busybox like ifconfig to get the serial port working, because i knows that this device have also a network controller thats belong to NE2000, that used to work with the activesync and if he working, may have include some telnetd server on device.

[z720]

im screw the Image, now stuck @ kernel bootinng :confused:
not able to figure out what's wrong where i did wrong. :(
Could somebody share with me the .config and hp214*.c :o

[[opensys]]

I try to build one usb converter thats permit me to connect the omnia to a external usb keyboard, but no luck the keyboard leds blinks, but no action on wm or android. i also get some information about the usb3319, this ic is responsible to switch the usb connection at two ways and power some device parts. This is the switch that works with the card storage or data link usb like the network controller ne2000, so this driver is needed at all to get some serial port working by the usb cable or any communication from it.
The pdf of usb3319 is in this url:http://www.smsc.com/main/datasheets/3319db.pdf.
The file arch/arm/mach-pxa/hpipaq214-usb.c have some clues.
So the only way is put the BT device working or the wireless network card named sychip jaguar to get a serial port. Other things included is dissembled the device and get the serial port from the gps module or make other hard hacks on the device board.

The data sheet service mode for Samsung SGH-i900 omnia: http://www.palmpc.cz/soubory/1229854/SGH_i900_service_manual.pdf.

find also that to the usb have working he needs +5v on usb3319 to detect some device connected.

[dejfson]

Dear All,
i've managed finally to force haret to recognize PXA processor, so I was able to watch over gpios and what is where connected. Unfortunately the only thing I was able to find so far is

GPIO23 = touch screen (turned to '1' when presses screen, turned back to '0' when released)

GPIO17 = button which ends the phone call (again '1' when pressed, '0' when not)

GPIO20 = always transitions when user passes finger by optical cursor

this is what happens when one turns off the camera light:
008.363 GPIOS GPLR0: GPIO0(0)=1 GPIO4(4)=0
008.363 GPIOS GPLR1: GPIO47(47)=1 GPIO53(53)=1
008.363 GPIOS GPLR2: GPIO90(90)=1
008.363 GPIOS GPDR3: GPIO127(255)=0
008.553 GPIOS GPLR0: GPIO0(0)=0
008.553 GPIOS GPLR1: GPIO47(47)=0 GPIO53(53)=0
008.553 GPIOS GPLR2: GPIO90(90)=0
008.553 GPIOS GPDR3: GPIO127(255)=1

this is to turn the light on again:
053.718 GPIOS GPLR0: GPIO23(23)=1 <-- taping on the screen
053.837 GPIOS GPLR0: GPIO23(23)=0 <-- taping on the screen
053.848 GPIOS GPLR0: GPIO0(0)=1
053.848 GPIOS GPLR1: GPIO47(47)=1 GPIO53(53)=1
053.848 GPIOS GPLR2: GPIO90(90)=1
053.848 GPIOS GPDR3: GPIO127(255)=0
054.046 GPIOS GPLR0: GPIO0(0)=0 GPIO4(4)=1
054.046 GPIOS GPLR1: GPIO47(47)=0 GPIO53(53)=0
054.046 GPIOS GPLR2: GPIO90(90)=0
054.046 GPIOS GPDR3: GPIO127(255)=1


--- NO OTHER GPIOs move. This means that either pxa3xx series has different/additional locations for gpios (as I've ran haret in pxa27x emulation mode)

or everything is driven by i2c bus

or there is an expander of gpios (like one of those pcaxxxx)

or i2c&expanders

as i2c seems to run correctly in linux, i'd say that i could test some of the 'standard' expanders whether they respond on the i2c bus and then - if this is the case - implement it into haret to be able to see the rest of gpios

d.

[dejfson]

additional info:

GPIO125 connected to accelerometer sensor ( when phone moves, signal changes)

GPIO79 = something related to the vibrator of the phone

turn on the phone transmitter and log on gsm network:

001.893 GPIOS GPLR2: GPIO81(81)=1
002.090 GPIOS GPLR3: GPIO107(107)=1
002.495 GPIOS GPLR2: GPIO81(81)=0
007.700 GPIOS GPLR3: GPIO106(106)=1
014.706 GPIOS GPLR2: GPIO71(71)=1
014.775 GPIOS GPLR2: GPIO71(71)=0
015.682 GPIOS GPLR0: GPIO23(23)=1
015.799 GPIOS GPLR0: GPIO23(23)=0
016.519 GPIOS GPLR0: GPIO23(23)=1
016.637 GPIOS GPLR0: GPIO23(23)=0
016.713 GPIOS GPLR2: GPIO71(71)=1
016.777 GPIOS GPLR2: GPIO71(71)=0
016.868 GPIOS GPLR0: GPIO23(23)=1
016.973 GPIOS GPLR0: GPIO23(23)=0
017.205 GPIOS GPLR0: GPIO23(23)=1
017.325 GPIOS GPLR0: GPIO23(23)=0
018.715 GPIOS GPLR2: GPIO71(71)=1
018.778 GPIOS GPLR2: GPIO71(71)=0
018.938 GPIOS GPLR0: GPIO23(23)=1
019.056 GPIOS GPLR0: GPIO23(23)=0
020.716 GPIOS GPLR2: GPIO71(71)=1
020.779 GPIOS GPLR2: GPIO71(71)=0
022.717 GPIOS GPLR2: GPIO71(71)=1
022.780 GPIOS GPLR2: GPIO71(71)=0
024.719 GPIOS GPLR2: GPIO71(71)=1
024.782 GPIOS GPLR2: GPIO71(71)=0
026.720 GPIOS GPLR2: GPIO71(71)=1
026.783 GPIOS GPLR2: GPIO71(71)=0
028.721 GPIOS GPLR2: GPIO71(71)=1
028.784 GPIOS GPLR2: GPIO71(71)=0
030.722 GPIOS GPLR2: GPIO71(71)=1
030.785 GPIOS GPLR2: GPIO71(71)=0
032.823 GPIOS GPLR2: GPIO71(71)=1
032.928 GPIOS GPLR2: GPIO71(71)=0


GPIO3/GPIO76/GPIO84 (some polling done on this pin)/GPIO71/GPIO48 = bluetooth module

sequence:
001.003 GPIOS GPLR0: GPIO23(23)=1
001.124 GPIOS GPLR0: GPIO23(23)=0
001.950 GPIOS GPLR0: GPIO3(3)=0
001.950 GPIOS GPLR2: GPIO76(76)=0
001.968 GPIOS GPLR1: GPIO48(48)=0
001.968 GPIOS GPLR2: GPIO71(71)=1
002.970 GPIOS GPLR1: GPIO48(48)=1
002.970 GPIOS GPLR2: GPIO71(71)=0

turns the bluetooth module off

turn the wifi on:
029.241 GPIOS GPLR0: GPIO3(3)=1
029.260 GPIOS GPLR0: GPIO16(16)=1
029.260 GPIOS GPLR3: GPIO104(104)=1 GPIO118(118)=1
029.271 GPIOS GPLR0: GPIO8(8)=1 GPIO16(16)=0
029.329 GPIOS GPLR0: GPIO9(9)=1
029.329 GPIOS GPLR1: GPIO48(48)=0
030.330 GPIOS GPLR0: GPIO9(9)=0
030.330 GPIOS GPLR1: GPIO48(48)=1
034.351 GPIOS GPLR0: GPIO9(9)=1
034.351 GPIOS GPLR1: GPIO48(48)=0
034.852 GPIOS GPLR0: GPIO9(9)=0
034.852 GPIOS GPLR1: GPIO48(48)=1
035.353 GPIOS GPLR0: GPIO9(9)=1
035.353 GPIOS GPLR1: GPIO48(48)=0
035.854 GPIOS GPLR0: GPIO9(9)=0
035.854 GPIOS GPLR1: GPIO48(48)=1

turn the wifi off:
001.489 GPIOS GPLR0: GPIO8(8)=0
001.489 GPIOS GPLR3: GPIO104(104)=0 GPIO118(118)=0
001.493 GPIOS GPLR0: GPIO9(9)=1
001.493 GPIOS GPLR1: GPIO48(48)=0
001.498 GPIOS GPLR0: GPIO3(3)=0
002.494 GPIOS GPLR0: GPIO9(9)=0
002.494 GPIOS GPLR1: GPIO48(48)=1

[dejfson]

look on the ownership of these files. they must be owned by root:root

;3369389']ok
now i get press enter to enter in the console.
I found this was miss and is not in forum
in default.txt need the line: initrd "initrd.gz"
now have the file system

in the some last lines i get:
cannot run /etc/init.d/rcS

i create it and set execution permissions but he do not detect it.
I also get errors that can't get the /dev/ttyX. I create it on dev no more show up in console.

this script will be able do run some programs in busybox like ifconfig to get the serial port working, because i knows that this device have also a network controller thats belong to NE2000, that used to work with the activesync and if he working, may have include some telnetd server on device.

[dejfson]

opensys, could you be please more specific about this: but no action on wm or android. -- you made android running on omnia?


;3373327']I try to build one usb converter thats permit me to connect the omnia to a external usb keyboard, but no luck the keyboard leds blinks, but no action on wm or android. i also get some information about the usb3319, this ic is responsible to switch the usb connection at two ways and power some device parts. This is the switch that works with the card storage or data link usb like the network controller ne2000, so this driver is needed at all to get some serial port working by the usb cable or any communication from it.
The pdf of usb3319 is in this url:http://www.smsc.com/main/datasheets/3319db.pdf.
The file arch/arm/mach-pxa/hpipaq214-usb.c have some clues.
So the only way is put the BT device working or the wireless network card named sychip jaguar to get a serial port. Other things included is dissembled the device and get the serial port from the gps module or make other hard hacks on the device board.

The data sheet service mode for Samsung SGH-i900 omnia: http://www.palmpc.cz/soubory/1229854/SGH_i900_service_manual.pdf.

find also that to the usb have working he needs +5v on usb3319 to detect some device connected.

[dejfson]

confirm:

set gplr(4) 1 -> turn on the camera light
set gplr(4) 0 -> turn off the camera light

[[opensys]]

no dejfson, sorry my mistake. But why? cant be work with the ARM cpus ?

the /etc/init.d/rcS seams now thats was be found, no error. I cant explain why but seams the initrd image have some bad things, i create other and works fine, no error.

As i cant output messages in to the lcd ? the /dev/tty0 or tty1 do not work.
and clue ? I try to put some echo in rcS and in rclinux but no output, any help?

As you tested the gpios ?

opensys, could you be please more specific about this: but no action on wm or android. -- you made android running on omnia?

[dejfson]

Hi all interested.
as this topic goes quite far, i'd suggest to make at some stable place a svn repository where we put all the necessary stuff and which will provide us with some sort of background (mailinglist) on that topic.
i'm trying to make a project on sourceforge.net, so far waiting for authorization.
once done, i'll upload all the context so far I made running.

any stable developers interested?

[dejfson]

:) reversed from drivers: it seems that USB reset pin is connected to GPIO12

[z720]

I found that kernel Image wont work after upgrade to IA2
Not sure anything I did wrong here :mad:

[dejfson]

I found that kernel Image wont work after upgrade to IA2
Not sure anything I did wrong here :mad:

z720 give me some days.i have
registered a project on sourceforge.
i will dvmp there all my resources
including configuraon fíles
d.

[z720]

z720 give me some days.i have
registered a project on sourceforge.
i will dvmp there all my resources
including configuraon fíles
d.

finally i get back the bootable kernel image. :rolleyes:
anyway i found that ipaq214 config just help on minor boot up but not much.
As dejfson said might need to fine tune the GPIO.

[steove]

Hi Guys,

Sorry I can't help in coding for this project, but I think it would be great to get android on the Omnia, Keep up the great work.

I will be watching with much hope........ and I'm sure there are many others doing the same.

[dejfson]

finally i get back the bootable kernel image. :rolleyes:
anyway i found that ipaq214 config just help on minor boot up but not much.
As dejfson said might need to fine tune the GPIO.

I have started investigation of GPIOs using haret. I've found some things, however, the thing which makes me a bit of strange feeling is, that when I compare the GPIOs what I have found by haret (or reversed from drivers), the sometimes DO NOT MATCH with the parts of schematics of samsung omnia presented in the 'service manual' appearing on the internet

d.

[z720]

I have started investigation of GPIOs using haret. I've found some things, however, the thing which makes me a bit of strange feeling is, that when I compare the GPIOs what I have found by haret (or reversed from drivers), the sometimes DO NOT MATCH with the parts of schematics of samsung omnia presented in the 'service manual' appearing on the internet

d.

Looks like might need to open out the omnia to get detail on the hardware... :cool:

[android_omnia]

Anyone have any luck with any of this yet?
It seems to be complicated, but i'm sure that it will be done someday (hopefully soon :))

[ricflairandy]

yeah, progress seems to be being made on the xda devices,but i suppose they havea larger community than the omnia

[android_omnia]

Unfortunately you're absolutely correct :(
I have the Omnia and the hardware is out of this world ... the downside is that the OS its using is total rubbish; I am just praying the Android gets ported sooner rather than later.
thanks to all involved :)

[petzy]

Hi guys,

what does it mean "investigating on GPIOs" exactly?
Is there any possibility to give you any help for understanding what the problem is?
Petz

[maverick62]

Hi everybody, are there other ways to run a linux system on the omnia? It should be great.

Where download HaRET for this phone? I try thelinks of the first page but ive a 404 error.

Thanks you, i am reading all your work and i will test when i get Haret.

[ricflairandy]

My omnia should be here tomorrow,so if i can help in anyway

[ricflairandy]

is anyone working on this still?

[vcoc93]

Hi um Im new on these programmer stuff and my english isnt so good either because im from latin america and i havent finished my english lessons yet. Could someone please explain me a little bit more detailed how to install this rom on my omnia, with more "simple" terms

Thanks in Advance:)

[qduaty]

Hi guys,
I'm glad to finally see linux asking me to press Enter on my omnia ;) Great job.

They (click (http://samsung-omnia.handster.com/software.php?id=3339&for=Samsung+Omnia)) claim that you can switch the omnia's USB port into host mode programatically and connect a keyboard to it.

Edit: Or maybe not... I don't really get it how they connected a keyboard to omnia.

[maverick62]

Thanks, but, do you have Haeret for the omnia? Could you send it me to aleleu62[at]gmail[dot]com. Thank you

[qduaty]

This is the broken link from us1111's post: http://www.oliford.co.uk/hpipaq214/files/h...aq214-aug08.exe (it has an ellipsis added by forums). Click on it, then go one level up, to the files/ directory, and you will have two versions of HaRET. I use the aug08 build.

[maverick62]

thanks you, i am trying.

[Mertoglu]

Guys, when will android be ported on Omnia?? Count me in for 20 dollars.

Is there any progress? Or say it is not gonna happen and we won't HOPE and wait for it.

[zeski]

I'm a bit of a rookie on linux.... and programming in general...

But from the look of things you guys are able to get the kernel up... I didn't follow the thread too closely but does that mean you guys can get to "bash" and run commands already?

Just to get my head around the porting process -
The first stage is to create an image of the kernel as per http://www.kandroid.org/android_pdk/bring_up.html and then run that on HaRET

The second stage is to then implement display, audio and input drivers (which seems to have been done to the extent that the display res is correct but because this is a touchscreen phone the key inputs can't really be configured yet)

The third stage is to configure telephony and then I guess X and all the good stuff

From what I understand of what I've read and the OP's last edit... he now wants to telnet into the kernel running on HaRET? Is this to facilitate easier entry of commands? If you guys are at a bash prompt... how is anyone typing commands into it? Are you guys preparing scripts on your PC's and then running them?


Sorry for the barrage of questions but I'm very curious about the status and very keen to do what I can to help this off the ground. I feel like the Omnia has the body of a shark but the mind of a brain damaged jellyfish.


P.S. On the note of keyboards - would it maybe be possible to install a keyboard via Bluetooth?

[ibuycheaprice]

Money for the developer who is able to port Android to the Omnia. www.AndroidOmnia.com

[kalekume]

Maybe this will help......

there is a soft keyboard available in Android 1.5 "Early Look" SDK

http://i.gizmodo.com/5210852/android-15-early-look-sdk-now-available-adds-soft-keyboard-video-recording-and-way-way-more

[xmoo]

Maybe this will help......

there is a soft keyboard available in Android 1.5 "Early Look" SDK

http://i.gizmodo.com/5210852/android-15-early-look-sdk-now-available-adds-soft-keyboard-video-recording-and-way-way-more

Old news,

the cupcake edition has the keyboard already!

[meGenius]

hi all,,

i'm interested in such topic, cuz i'm one of the omnia owners who wants android.
i read the instructions in the first post, but understood nothing.
if you can provide a ready image of the whole work, i'll be thankful.
or, if you can rewrite the instructions in more simple way, i'll be thankful, too.

thnx in advance

rgrds ||| meGenius

[meGenius]

please guys,,

i'm a newbie in such field, so i need a full instructions to start the kernel. now i have omnia with WinMo 6.1, how to start & where to go??

i tried to apply the instructions but faced a lot of problems:
1. the dir for Makefile is "/ANDROID/v4", while it's "usr/local/v4/"
2. the dir for the CROSS_COMPILE is "/usr/local/xscale/arm-2008q3/bin/arm-none-linux-gnueabi-", in fact, there's no such bin file
3. there's difference between the downloaded package & the extracted package, the first is: arm-2008q3-66-arm-none-eabi-i686-pc-linux-gnu.tar.bz2, while the other is: arm-2008q3-72-arm-none-linux-gnueabi-i686-pc-linux-gnu.tar.bz2

i need to know whether it's my problem , or there's any mistake in the instructions..

rgrds ||| meGenius

[renlok]

HaRET does not seem to recognize the omnia's PXA312... Also i cannot determine the mtype for this.. Anyone have any ideas on how to get the kernel to boot???

could you not just get in contact with samsung to get the answer to this?
http://www.samsung.com/uk/info/contactus.html

[annethony32]

umm is this thread dead? I think nobody is working on the program anymore..

[whiplash000]

It seems that the only thing holding back this project, besides a lack of interest (with skilled people, fans notwithstanding (http://androidomnia.com/)) is that we can't communicate with the phone. If you guys can help me get the kernel running, I can start porting WM drivers and once we get that done, Android can be run without much more work.

[petzy]

Hi all,
just a question: could be useful waiting for the new android samsung phone for trying the porting?
Petzy

[whiplash000]

Doubt it. The hardware's proabally completely different, in fact the only thing they have in common is they both say Samsung on them...

[fella_]

i get my omnia in few days so i can help this project!
i build the kernel, busybox etc already... i hope it works...
then i can help making the usb/wireless drivers!!!

sry for my bad english :´(

still waiting for my omnia...

so long ;)

[fella_]

ok i got my phone 2 days ago...
all works fine - no i hang on the rcS problem!

i created the /etc/init.d/rcS file where the /dev and /proc folders are with the content

CODE
#! /bin/sh
echo hello


then chown -R root:root /etc and made the initrd.gz file...
but when i run the kernel it says /etc/init.d/rcS no such file or directory!
workin on this now

[fella_]

rcS problem solved!
we now working on this project HERE (http://support-köhler.de/andromnia/index.php)

[renlok]

rcS problem solved!
we now working on this project HERE (http://support-köhler.de/andromnia/index.php)

wow looks like some really fantastic work your doing :D
and it looks like youve got a few people helping out :) hopfully youll be able to get it working as that would be truly fantastic as winmo is sooo bad.

[fella_]

i think we are one step from an running android!
the current problem is to enbale double(frame)buffer/page flipping for the pxafb.c...
but this is very hard cause we have no good C'ler atm :(

[fella_]

ANDROMNiA 0.2.0 (POC) - based on rev78
-----------------------------------------------------------------------------------

!!!THIS WILL NOT MODIFY YOUR PHONE!!!

INFO:

This is only a proof of concept! No help or support will be given!

This package features these lovely omissions:
-No battery support
-No touchscreen support
-GPS, GSM, 3G, EV-DO,WiFi, Bluetooth or any other kind of connectivity are also NOT supported

INSTALLATION INSTRUCTIONS:

-Set the Omnia's USB mode to Mass Storage, Storage Card (Start->Settings->Connections->USB Connection Mode)
-Make a primary ext2 partition on your sd-card. We suggest doing this with an Ubuntu live cd if you're running Windows. Once it's started, run gparted from the terminal and REMEMBER TO CHOOSE THE CORRECT DEVICE!
-Extract the contents of rootfs.tar.bz2 to your SD card.
-Copy haret-0.5.2.exe, default.txt and Image to your phone. (Anywhere will do, except for the SD card)
-Start haret-0.5.2.exe, click run and see what happens ;)


PROBLEMS:
If:
-Your screen turns black,
-Your text streaks vertically,
-The flash stays on, or
-The text gets chopped off
...reset your phone and try again. If you get all 4 of these in a row you win a cookie!
Also, you'll have to re-format your ext2 partition. :)


VISIT US AT:
irc.freenode.net:6667
#andromnia



DOWNLOAD:
http://netload.in/dateieLlYUBovPG/andromnia_0.2_rev78_poc.rar.htm

http://img233.imageshack.us/img233/4159/dsc00431resized.jpg
http://img229.imageshack.us/img229/4774/dsc00432resized.jpg
http://img26.imageshack.us/img26/1311/dsc00433resized.jpg
http://img222.imageshack.us/img222/2839/dsc00434resized.jpg

[android_omnia]

What does this mean?
Can someone please confirm that this works?

As far as I understood ... it will work (but i wont be able to do anything as touchscreen doesn't work ... did i understand properly?)

[fella_]

yes thats right android boots!

but it's only a proof of concept :)

we are working on bat & touch driver now...



greetings, fella & dev team :)

[tedpixie]

So how is this project coming along? Your POC worked as advertised with no hick-ups, so I am very interested to know if this project is still alive and if its
a chance that it will work some day. I would be very happy to see a working
Android on my Omnia.

[Jclarkk]

The project still works only they moved forums, Android now works with touchscreen support and they are working on creating/modifying rest of drivers.

For more info:
http://support-köhler.de/andromnia/viewforum.php?f=1&sid=95fac0e4cf8692107cb2e2465b1add7b

[ruckuus]

Is there any kernel config to share?

Thanks,

[fella_]

https://dotpt.com/svn/andromnia/trunk/

wifi & internal memory now working.

most time we are talking over irc.freenode.net #andromnia

[greekpower]

:mad::confused:Many Hobist that like to jump from WIN Xp To Linux OS or WIN-7
or MAC OS NOW is A problem on Line on Smartphones. Units like Omnia i900
Blackbery, Dash, Fake iPhones. Try to Unlock and run Sebian, WM 6.5 Android
and other OS that comming cross on line.
If you have Omnia i900 don't waste your time to install the Android, I try is disaster. what Happen
:rolleyes:Your Omnia is no Damage Because the os is on external SD Card.
:mad:1- Audio is No Working
2- Mouse IS DEAD
3- Network Connection is DEAD
4- WI-FI is DEAD
5- Dial out is DEAD
6- Camera is REAL DEAD
7- Video is Real DEAD
8- GAMES not Suport
9- GPS OUT Real DEAD
10-Time Is dead
12-Instalation confused
12-interface Butons IS DEAD
:)13- Screen push IS OK
OPA!!! after all the No 13 is working must be a miracle...

Now I have Omnia i900, I have iPhone, I have G1 Android

from all those 3 only :rolleyes:Omnia i900 is workning great with wm 6.5 and interface with spb software
you can make your omnia look like any other phone, Run any Multimidia
Run Live Flash TV broadcast or radio stations. spb tv. and spb Radio.
Windows Mobile is a lot of proof, More FREE Memory, this is a real Computer and Multimedia unit on your Fingers.
Download all your neads on www.spbsoftware.com

[luismanson]

[QUOTE=greekpower;4713680]
If you have Omnia i900 don't waste your time to install the Android, I try is disaster
1- Audio is No Working
2- Mouse IS DEAD
3- Network Connection is DEAD
4- WI-FI is DEAD
5- Dial out is DEAD
6- Camera is REAL DEAD
7- Video is Real DEAD
8- GAMES not Suport
9- GPS OUT Real DEAD
10-Time Is dead
12-Instalation confused
12-interface Butons IS DEAD
:)13- Screen push IS OK

3 WORKS
4 WORKS
5... it dials but then nothing else...
10 works
11 ?
12 not really
12 works for me

also SD card works... ;)

anyways, im getting segfault some times with SVN and 159 kernels... :(

[maverick62]

Hi everybody! :)
I have a litlle problem.
I format my sd-card with gparted (ubuntu 9.10) => OK
I put haret and "image" on the memery (NOT on sd but on the internal memory). => OK
I extract rootfs on the sd card => OK
I launch haret=>Not ok
I have a "kernel panic"

So, i try to format on fat and re-format to ext2 = the same
try to format on ext3 = the same

I don't know what i can do to get it works!

Please Help!

ps: does it work with all sd-cards?

Thanks

[roopart]

As i know andromnia project is still under development. So is there any possibility that we can install the files from the andromnia website and once when omnia has linux or android running on it we can flash cooked andoid rom. Will it work on omnia ???

[roopart]

As i know andromnia project is still under development. So is there any possibility that we can install the files from the andromnia website and once when omnia has linux or android running on it we can flash cooked andoid rom. Will it work on omnia ???

[haz82m]

just fYI ,

i tested the andromnia rev 0.32 it works fine after following the instruction posted on the andromnia website


however it gets little bit tricky with the wifi and GSM support for me

CDMA and 3g 2G is not supported yet according the andromnia team


please keep posting yout comments on these thread , especially for the omnia users

[roopart]

As you said you have tested it on omnia just wanted to know that your omnia is running on both platforms windows as well as android??? please confirm.

[Nebroc]

It's a phone of a much lower class but do you think this could be used to put 1.6 on a Samsung Mythic