LINUX BOOTS at OPAL! Thanks to linwizard project!

[cijoml]

Hi there,
I got Linux to boot at OPAL via linwizard project. Here are steps needed to get it work.

1) download image from:
http://tinderbox.x86.dev.gentoo.org/embedded/linwizard/gizard-20080602.tar.bz2
2) copy content of file to the microSD card
3) edit default txt and replace init=/linuxrc with init=/bin/sh
4) run haret and let it boot.

After a while you'll get to shell. No graphics.
Now you can attach microusb cable and connect it with your linux laptop (I recommend ubuntu)
and you will get usb0 interfece to start up.

Which IP to use to connect with OPAL I still must investigate.

[cijoml]

Well ip connectivity now works:
ip=<client-ip>:<server-ip>:<gw-ip>:<netmask>:<hostname>:<device>:<autoconf>

Notas:/# ifconfig usb0 up 192.168.2.200 netmask 255.255.255.0
Listik:/usr/src/linux-2.6.27/Documentation# ping 192.168.2.202
PING 192.168.2.202 (192.168.2.202) 56(84) bytes of data.
64 bytes from 192.168.2.202: icmp_seq=1 ttl=64 time=2.95 ms
64 bytes from 192.168.2.202: icmp_seq=2 ttl=64 time=1.72 ms

And how to do it:
prolong "set CMDLINE" line with
ip=192.168.2.202:192.168.2.200:192.168.2.200:opal: usb0

But in this image there doesn't seem to be any telnet/ssh server running. I will try cook image with ssh server support later

[zqyhqw]

Download error
Were not able to re-upload

[donsalari]

404 file not found error!! :(

[OndraSter]

http://tinderbox.x86.dev.gentoo.org/embedded/linwizard/

and open latest gizard-<date>.tar.bz2

or that I suppose.

The latest link should be http://tinderbox.x86.dev.gentoo.org/embedded/linwizard/gizard-20090703.tar.bz2

[jonrulezz]

does this mean any chance of android working? anyone tried?

[MusikMonk]

Hey,
I'm a new Opal user and I'm interested in getting *nix running on my device. I still haven't had the chance to mess around with this stuff but I'm excited to see this thread.
I was looking into the possibility of running Android on the Opal and it seems the closest thing is this thread bout running it on the Herald (http://forum.xda-developers.com/showthread.php?t=398830) (it uses the same processor as the Opal).
I don't any experience in Linux porting so I thought I'd share this, in case anyone else is interested. And at the same time, I'll try to see if I can get something working based on what has been/is being done for other devices.

Sorry for the long post.

[msigeek]

Hey Folks,

Any progress on getting Android on Opal? I am eagerly waiting to load one.
Kindly let me know, if this version of Linux when loaded, gives the UI.

Cheers'
Vijay

Hi there
I got Linux to boot at OPAL via linwizard project. Here are steps needed to get it work.

1) download image from:
http://tinderbox.x86.dev.gentoo.org/embedded/linwizard/gizard-20080602.tar.bz2
2) copy content of file to the microSD card
3) edit default txt and replace init=/linuxrc with init=/bin/sh
4) run haret and let it boot.

After a while you'll get to shell. No graphics.
Now you can attach microusb cable and connect it with your linux laptop (I recommend ubuntu)
and you will get usb0 interfece to start up.

Which IP to use to connect with OPAL I still must investigate.

[MusikMonk]

I have some good news, Android can boot on the Opal. This is just a proof of concept as it's missing tons of drivers and is completely useless.
Touchscreen and all keys except for the volume control (and obviously the reset button) are not working. So you basically can't do anything when you run it.

What I tried is the same as what's written in this thread (http://forum.xda-developers.com/showthread.php?t=496692) about running Android on Gene. They're using the build made for the Herald/Wing (just as I was proposing in my last post) with customized initramfs and kernel.
You'll find all the necessary details in that thread. However, there's a newer build than the one mentioned there it's wing-linux-0.4pre2.cab. And the suitable kernel for that build is supposed to be the pre2 posted in this post (http://forum.xda-developers.com/showthread.php?t=496692&page=14#134) but it didn't work on my Opal so I tried the older Gene kernel and it worked. The main difference between the two is bluetooth support, and that's obviously is of no use for us.

This doesn't effect the Windows rom, nor does it requires any special partitioning. Still it's best to have everything backed up before launching it, just in case.

This is the official site for the wing/herald build:
http://wing-linux.sf.net/

This thread on their forums about the Gene port will probably be of use to us:
http://sourceforge.net/apps/phpbb/wing-linux/viewtopic.php?f=4&t=4

I'm reading about the next steps but as I said before, I don't have any previous experience or knowledge about this type of things. If someone can give me hand, I would be more than grateful. At any rate, once I have better understanding of the concept I'll contact the people behind the Wing and the Gene ports.


P.S: If you do try to run this, keep in mind that this will take lots of time, specially for the first launch. And when you get an error saying something like "android sh: can't access tty" just ignore it and keep waiting. After a while you'll have a flashing "android" on the screen, and after some more waiting you'll reach the main screen.

[msigeek]

Sooper Stuff..!! So is this just THE BEGINNING??
How do we port the drivers and other required information in the build?

Cheers'
Vijay
www.msigeek.com

[kshaurya]

I'm going through the Gene port thread here and on the Wing-linux sourceforge forums but I'm still a bit overwhelmed.
I would appreciate any help as I'm completely new to porting. I have some programming and linux knowledge but never attempted this type of things.

So am I.

Hmmm...
Right. Lets do it the way I did it.

1. Get the touchscreen working. Through HaRET, you must have got the GPIO interrupt whenever you pressed the touchscreen. You must have got two numbers corresponding to each press - a smaller number and a bigger number. The smaller number is the GPIO, and the larger number is, well, lets say a special GPIO value for the same pin.

Now checkout the Gene branch through git.

Goto /wing-linux/kernel/arch/arm/mach-omap1/board-htcherald.c

Scroll down to a block of code where you'll see the touchscreen code. Enter the smaller number in the .dav_gpio statement, and the IRQ number in the OMAP_GPIO_IRQ() statement below.

2. Follow the Kernel build instructions on the development section of the wing-linux wiki (the two make commands)

Copy the zImage into the linux folder on your SD card

Boot into wing-linux. The touchscreen should start working.

3. Now, hopefully, after the touchscreen's working, You would essentially just require two more buttons - the home button and the back button for minimum functionality. Everything else can be worked on by the touchscreen.

Then follow the instructions on the wing-linux forum (Page 2) to get the KEY(row,col) values of the keys on your handset. Hopefully you should get atleast a couple. Note down the corresponding keys and their KEY(r,c) values output.

4. Fire up board-htcherald.c again and goto the place where you have the KEY(r,c,KEY_blah) thing and replace the codes as per your obtained KEY(r,c,KEY_blah) values (The Home button is the one commented as Left Button)

5. That's all I can help you with as of now. I'm also figuring out a stable way of getting the DPad and the center select key to work, but It'll take some time.

[MusikMonk]

Thanks kshaurya!
(This guy right here is the one who fixed the kernel for Gene, I asked him for some pointers).

I don't want to take my device apart just yet (I usually do my best not take to dismantle anything that I haven't owned for at least 3 months unless absolutely necessary) and I couldn't find a place that states what touchscreen it uses. I'm just hoping that it's the same a tsc2046 as well. [Is there anyone without a warranty and/or willing to check for us?]

I'm gonna double check the values I got from the touchscreen as for some reason I seem to have to IRQ values, probably forgot to get rid of some spamming irq. And, at the same time, I'm currently setting up a VM as a building environment, my main boot is Intrepid 64 and there's no 'psyco' package for 64 machines.


If anyone else have some experience and wants to try this, refer to: http://www.handhelds.org/moin/moin.cgi/HaRET_20Documentation (using haret to get the GPIO and IRQ values needed).
And to:
http://sourceforge.net/apps/trac/wing-linux/wiki/Development (acquiring the source code from Wing Linux and how to build it).




And a quick question for anyone that tried booting Android on the Opal, what screen did you get when Android finally finished booting?

[kshaurya]

I don't want to take my device apart just yet
Huh? where did that come from? Wing Linux will not touch your WM.

I seem to have to IRQ values
Do you mean two? Well, that's exactly what you should get. Even if it's just one, enter that value in the code.

my main boot is Intrepid 64 and there's no 'psyco' package for 64 machines
Oh no. dont tell me that you are building the entire thing. all you need to do is build the KERNEL! Please! Don't go into building the whole thing from scratch. Use the make ARCH ARM commands given on that page.

[MusikMonk]

Huh? where did that come from? Wing Linux will not touch your WM.

I mean to check the screen, in case it turned out to be different that what you have.


Do you mean two? Well, that's exactly what you should get. Even if it's just one, enter that value in the code.


Yeah, stupid typo. :o
I noticed now that one of them appears when I keep the screen 'touched' for a bit longer.



Oh no. dont tell me that you are building the entire thing. all you need to do is build the KERNEL! Please! Don't go into building the whole thing from scratch. Use the make ARCH ARM commands given on that page.

I'm not gonna build the complete thing. Seems like I got too exited and failed to notice that building the kernel only requires a cross-compile toolchain, te rest is for compiling the whole thing.

I'm not THIS stupid usually . Honestly! :p


Thanks again!

[kshaurya]

I'm not THIS stupid usually . Honestly!
Its pretty normal :P

[MusikMonk]

Weird.
I've only changed the two touchscreen values and built the kenrel. It finished without any error but now it won't boot.
It gets stuck, even before the space allocation part, with this error: "sh: can't access tty; job control turned off". And then it displays a prompt.

I'll try modifying an older build, I'm pulling them from the repos at the moment.
After all, the pre2 kernel from Gene didn't boot on my device (although it got stuck later on).

[kshaurya]

Try doing a clean install - Remove the linux folder and try again.
Also, make sure that you're not forgetting to checkout the Gene branch.

git checkout Gene

Is your default.txt modified? And have you downloaded the modified initramfs.cpio?
check in the Gene forums for that.

[MusikMonk]

Already tried the clean install, no dice. The default.txt is untouched and I'm using the modified intramfs. What happened this time is different from what happens using the original one, it's not asking me to specify the partition size but instead it's waiting for a command. I could probably ssh via usb but I have no clue how that might help.
And I've already checked out the Gene branch from the beginning.

I've tried compiling the kernel for pre1 (after changing the screen values) from SVN and it did boot (both using the cabs for pre1 and pre2) but no touch screen yet. All in all, I'm guessing that there's too much hardware difference here.

And the button for lowering volumes didn't work either, it seems like whatever you changed for getting it to work on Gene is the same as what we need here, but I'll think about that later.

I only have two ideas left:
- Trying to go back to a more stable build (with lesser features and lesser possibilities for errors). Maybe 0.3.
- Trying to create some kind of hybrid kernel using this alongside the HTC Vogue build as it probably has closer hardware to the Opal (obviously, I'm talking about everything beside the MSM7500 400MHz processor that it has). I'm hoping it won't get to this cause I'm definitely under qualified for that at the time being.

[kshaurya]

What happened this time is different from what happens using the original one, it's not asking me to specify the partition size but instead it's waiting for a command.
Could you post a screenshot?

I've tried compiling the kernel for pre1 (after changing the screen values)
I'm assuming you mean the touchscreen values? Try interchanging and see.

Trying to go back to a more stable build
I wouldn't recommend that. Defeats the whole purpose.

Why don't you try getting in touch with darkstar?

[MusikMonk]

Could you post a screenshot?


A friend borrowed my digital camera, I tried my laptop's webcam but the text it too blurry. Couldn't fix it using gimp either. So here's exactly what's showing on the screen:

mdir: Cannot creat directory `/mnt' : File exists
modprbe: could not parse modules.dep
initramfs: Creating device nodes:
initramfs: Loading /initrd.d/10-initfs.sh module
initramfs: Loading /initrd.d/30-wingboot.sh module

Selected:
ROOT_DEVICE=/dev/
CMDLINE=debug quiet psplash=false loglevel=7 init=/sbin/init console=tty0 video=omapfb:accel fbcon=rotate:3 4 root=/dev/
initramfs: Loading /initrd.d/80-loopboot.sh module
initramfs: Loading /initrd.d/85-blockboot.sh module
booting from: /dev/
mount: Mounting /dev/ on /mnt failed: Invalid argument
Unable to mount rootfs device

sh: can't access tty; job control turned off
/ $


And after the prompt, on the same line, there's a flashing '_' waiting for input.
Using the original zImage (from the pre2 cab) it's right around here that the screen clears and the Wing Linux installation script kicks in.



I'm assuming you mean the touchscreen values? Try interchanging and see.


Will try that next.


I wouldn't recommend that. Defeats the whole purpose.


I meant it as just a temporary test to till the cause of the incompatibility is figured out. With less things that could go wrong, it'll be easier to locate the ones that are going wrong.


Why don't you try getting in touch with darkstar?

You're right. I should post a thread on the project's forums asking for his help.

[jonrulezz]

some guys have managed to port the htc hero build to the vogue, wondering if its the same of you will have to wait till it gets ported to the gene and then modify it?

[MusikMonk]

I've posted a thread on the forums for the Wing-Linux project, maybe the developers there can give us some pointers (https://sourceforge.net/apps/phpbb/wing-linux/viewtopic.php?f=4&t=6).

This sums up where we stand right now:
Installing the cab and running it as is will get the installation stuck at space allocation as the Opal doesn't have a keyboard. The solution was to modify that particular script int the initramfs. When I found that the people working on the Gene port already made that modification I just used theirs.

With the initramfs replaced, the installation runs smoothly and Android boots. However, there's no touchscreen and none of the keys (beside 'volume up') works. Using the zImage from the Gene port, the 'volume down' button worked.

I've tried pulling the Gene branch from git and modifying the gpio and irq values for the touchscreen, the way kshaurya told me (here) that he did for the Gene zImage. But I'm either doing something wrong when checking out the branch or the branch itself has something wrong, cause the zImage I'm getting after building doesn't work (even without any modification from my side). It just gets stuck (before space allocation).

I tried pulling the master branch without checking out any branch and building that, and it did boot. But I still didn't have a working touchscreen after modifying the required values with the ones I got from haretconsole. I also tried the 0.3 and 0.4pre1 builds from the SVN to no avail (I did that before trying the master branch from git, somehow that didn't occur to me at that time).


some guys have managed to port the htc hero build to the vogue, wondering if its the same of you will have to wait till it gets ported to the gene and then modify it?

There's no need to wait for a full port. If we manage to catch up to them, we should be able to progress in parallel.

[bolillo]

Ok i have one little problem right after i se the big android icon it show the home screen then it says powering off.
Im using build 0.4pre1 ill try other two versions and see if thats the problem.

[darkstar62]

Ok i have one little problem right after i se the big android icon it show the home screen then it says powering off.
Im using build 0.4pre1 ill try other two versions and see if thats the problem.

Using 0.4pre1 or pre2, can you log in via SSH over USB to your phone during this and provide the output of the following commands:


ls -l /android/sys
ls -l /android/sys/class/power_supply
ls -l /android/sys/class/power_supply/*
cat /android/sys/class/power_supply/*/*
ls -l /sys
ls -l /sys/class/power_supply
ls -l /sys/class/power_supply/*
cat /sys/class/power_supply/*/*
ls -l /android/sys_dev


That'll give me a good indication of what Android is seeing. Also, if you can supply the output of:


chroot /android /system/bin/logcat


that would be excellent. On most every other device, this isn't an issue -- not sure why you're having this problem, but let's see if we can get to the bottom of it. :)

- d

[MusikMonk]

I was out of town for the weekend (that's Thursday and Friday in my country). So I couldn't reply earlier.

Using .4pre1 with the initramfs and zImage from the Gene project, I've booted Android and executed these commands. If it makes a difference, when it booted, the screen I got this time was the one with "google search" at the top and some icons (messaging, dialer...) at the bottom.

I've redirected output and error to files for ease, and zipped them all together.
The first command's output is the file named 1, the second's is 2 and so on. And I also included the touchscreen values that I got from haretconsole and the output of: dmesg

I'm not sure what to look for in the outputs myself, but I noticed that "/sys/class/power_supply" is empty. Seeing that there are three commands concerning its contents, I'm gonna take a wild guess here and say that it shouldn't be :D

For some reason haret has decided to start refusing all connection attempts (it connects then terminate the connection directly) so I can't offer anything else using haretconsole, that it's till I figure out what's going on here.


Thanks for your support!


P.S: Quick note for anyone that wants to connect via SSH, here's the necessary information: https://sourceforge.net/apps/trac/wing-linux/wiki/PartitionInstallation (step 10 is all you need).

[darkstar62]

Just thought I'd let you all know that Wing Linux 0.4pre3 is out on Sourceforge. Get it at http://wing-linux.sf.net.

The installation for this one works a bit different than previous ones. In particular, there's two cab files of interest -- the *-rootfs.cab file, which contains all the common root image and kernels, and the *-herald.cab file which contains the Herald-specific files. You'll want to install both of these (Herald because we don't yet have board support for the Opal).

Please also remember to delete any rootfs.img file you might have in your /Storage Card/linux directory if you installed previous versions of it, as it will not be replaced automatically.

The initramfs should no longer need patching, as it will automatically time out without any keyboard input, accepting defaults (250mb image). Just wait, and it will automatically install.

Lemme know how it works!

- d

[MusikMonk]

Just thought I'd let you all know that Wing Linux 0.4pre3 is out on Sourceforge. Get it at http://wing-linux.sf.net.

The installation for this one works a bit different than previous ones. In particular, there's two cab files of interest -- the *-rootfs.cab file, which contains all the common root image and kernels, and the *-herald.cab file which contains the Herald-specific files. You'll want to install both of these (Herald because we don't yet have board support for the Opal).

Please also remember to delete any rootfs.img file you might have in your /Storage Card/linux directory if you installed previous versions of it, as it will not be replaced automatically.

The initramfs should no longer need patching, as it will automatically time out without any keyboard input, accepting defaults (250mb image). Just wait, and it will automatically install.

Lemme know how it works!

- d

The new installer does look nice, but that's as much as I can say. Before the touchescreen gets supported, the calibration screen is as far as the Opal can get.

I'm about to go have lunch right now, but afterwards I'll try to get on IRC and see if I can get enough help to make some progress.

[MusikMonk]

Just thought I'll let you guys know where we stand right now.
Touchscreen is still not working :( I'm asking for help and ideas everywhere I can.
Buttons, however, are now working after some small modifications. So it's possible now to move around Android a bit.

If you want to try it yourself, obviously at your own risk, you'll need to be able to SSH to your phone (I'll provide an alternative way when I find out how to disable touchscreen calibration).
Here are the steps:

Download and install wing-linux-0.4pre3-rootfs.cab and wing-linux-0.4pre3-herald.cab from https://sourceforge.net/projects/wing-linux/files/Wing%20Linux%20Development/ , make sure to install to storage card not to main device.
Download the attached zImage.zip and extract it.
Replace the zImage under \storage card\linux with the one you just extracted.
Run haret from the previous folder or Wing-Linux from programs under start menu.
Click on run.
When prompted to enter partition sizes you can either leave it till it times out or click the centre button. Both ways will use default values.
Keep waiting till you get to the touchscreen calibration.
Connect the device to your computer via usb and connect via SSH (step 10 here: https://sourceforge.net/apps/trac/wing-linux/wiki/PartitionInstallation)
Through SSH, run startAndroid.
You can now disconnect the connection and wait till Android finishes booting.
When done reset the device to go back to windows.
If you did do that, please post about your experience.


You'll also need to know the keymapping:

DPAD works normally: Up, Down, Left, Right and Enter.
Volume up is mapped to menu button.
Volume down is mapped to cancel/back.
Green/Red buttons are mapped normally (notice that, by default, Red button puts the device in standby and that's not implemented yet. Press any key to get back to Android).


This is the status at the moment:
GSM is, to a good extent, working:

I can call out successfully and the mic seems to be working well.
When calling in, the call is directly disconnected but appears in the log.
I couldn't find a way to send a message (as I don't have an input method).
Receiving SMS was successful.
Haven't tried GPRS (same problem as sending SMS, no input to set up APN).

Bluetooth:
Won't turn on. Tried having it on from WM before running, the only thing that changed was that the blue led was still flashing on and off normally, Android still considers it off and scanning for bluetooth device from my laptop yields nothing.

Backlight:
It's on, but changing brightness from settings does nothing.

Buttons:
After the small modification to the code, except for the power button, everything is working.

LED:
Green led is flashig normally when device is on, and it stop when device enters standby.
Yellow led (events, charging) doesn't seem to work. Nothing changes when connected to pc or power and when havig unread SMS.
Blue led, as noted before, worked when bluetooth was turned on from WM before booting.

USB:
I can connect and SSH successfully, so yes it does work.

SD Card:
I can access my sd under /media/windows (via SSH), does this count as working? Under Android's settings, the SD card supposedly has 242MB of total space, with 156MB available (note that I'm using a 2GB card).

Real Time Clock:
Seems to be functional.

Framebuffer/Rotation:
I didn't know how to test this. The only option concerning rotation that I found was the "Switch orientation automatically when rotating phone" and the Opal doesn't have the hardware for that. However, I remember booting into a landscape Android one time during my initial testing, so I guess it might be considered as working?

Vibration:
Again, I'm not sure how to test this. Under settings all I found was "Vibrate phone for incoming calls" and that's obviously not gonna help, if checking that is supposed to make the device vibrate on messages as well, then it's not working.

Battery, WIFI, Camera, Audio:
Not implemented yet.

[darkstar62]

It just occurred to me...MusikMonk, there's a driver in the kernel for the ADS4947 / TSC2046 touchscreen / battery driver. That driver is different from ours in that I think it assumes 8-bit mode, while our's does 16-bit. I tried using it on my Herald to see if I could get battery info for free, but I was getting constant 0, 0 from it touchscreen-wise, like you are for our driver.

It might be worth it to try that driver for the Elf -- maybe the chip on yours is running in 8-bit and would work with that driver. You'll need to make sure to enable it in your kernel config, and supply the necessary board info in board-htcelf.c -- I can help with that if you need it.

- d

[MusikMonk]

It just occurred to me...MusikMonk, there's a driver in the kernel for the ADS4947 / TSC2046 touchscreen / battery driver. That driver is different from ours in that I think it assumes 8-bit mode, while our's does 16-bit. I tried using it on my Herald to see if I could get battery info for free, but I was getting constant 0, 0 from it touchscreen-wise, like you are for our driver.

It might be worth it to try that driver for the Elf -- maybe the chip on yours is running in 8-bit and would work with that driver. You'll need to make sure to enable it in your kernel config, and supply the necessary board info in board-htcelf.c -- I can help with that if you need it.

- d

It's definitely worth a shot.

I can probably figure it out on my own in time, but that'll take ages. :o
So, I better act smart and ask for your help.

What changes do I need to do to enable it in the config? And what's the mtype for elf? I think that it was the same as wizard's (1229), right?

Edit: I'll be on IRC for an hour or two.

[MusikMonk]

Okay, I tried using the ADS7846 driver and it didn't work.
I tried to take board-nokia770.c as an example and modified board-htcherald.c, as always, and got a new zImage.
Everything boots normally, except that when "checking for tsc2046" appears: instead of getting the calibration screen, android starts booting directly. Obviously it didn't find it.
Afterwards, I tried ts_test and got an error stating that /dev/touchscreen0 doesn't exists. So it seems like the system can't see the touchscreen at all.
Running dmesg seems to confirm this as there's no mention of a touchscreen anywhere in the output (http://pastebin.com/m3920656b).
With the previous driver I had:
input: TSC2046 touchscreen as /class/input/input3

I'm not entirely sure that it's the driver's fault.
It might be that I overlooked something when changing the code. That's not unlikely with my experience. So I'm taking another look at the new structs and trying different values to see if anything happens.

darkstar62, I also wanted to check with you if the current build (pre3) looks for the tsc2046 driver directly in any place beside the initial calibration. I know that this isn't the problem but just to see what I might need to look at.


Edit:
This is the board I'm using: http://pastebin.com/m3b8ad98f
Any touchscreen related changes have //Monk beside them.

Edit2:
Figured out why the system didn't see the screen. It was extremely simple, I just had to change the alias to tsc2046 :)
However, still not working :(
Printk statements showed that the driver isn't getting any calls, not even for initialization. Still can't figure out if I did something wrong or if the driver is simply incompatible.

[raditzgds]

I'm trying to boot androind n my htc opal... my english is very poor.... so ...I'll try to be as clear as possible
I read the forum, and after follow the steps on (the post named "A Lil' help :)")
and I'm suck in "Then follow the instructions on the wing-linux forum (Page 2) to get the KEY(row,col) values of the keys on your handset. Hopefully you should get atleast a couple. Note down the corresponding keys and their KEY(r,c) values output." and I'donk know how to catch de key's irqs
y read also Haret doc... but... for example trying to chatch power button irq ...that disable the usb connection
Also, seeing carefully the board-htcherald.c file, I saw that thing "#define HTCHERALD_GPIO_POWER 139" maybe this conflicts with the touch screen irq wich is 139, some Idea? ... (sorry for my english... usually speak spanish...).

[raditzgds]

Well I'm readin the previous post of Musikmonk, i think I have the same problem, android start directly without the calibration touchscreen; but unlike the Senior Musikmmonk I have no idea about how can I make toucheable my screen. I'll wait hopefull the solution.
About the touch pad, I made a test kernel asigning arbitrary keys values (letters) to an array with 4 rows and 4 columns, and by pressing buttons while android boot (before the X starts) then I have some idea about wich array index have each key. After then my board-htcherald.c results some like this:
static int htc_herald_keymap[] = {
// Volumen keys 0,3 UP; 1,3 Down
KEY(0,3,KEY_VOLUMEUP),
KEY(1,3,KEY_VOLUMEDOWN),
//----------------------------
KEY(2,2,KEY_SLASH), // enter
// teclas cursor
KEY(0,1,KEY_TAB), //arriba up
KEY(1,1,KEY_ENTER), //abajo down
KEY(0,2,KEY_DIRECTORY), //derecha rigth
KEY(1,2,KEY_CALENDAR), //izquierda left
//----------------------------------------------------------
// tecla SEND
KEY(0,0,KEY_PHONE),
// tecla END
KEY(1,0,KEY_CANCEL),
//----------------------------------------------------------
0 }

But the cursor keys as U imagine does anything except what expected, this whas just a test; but I'd like to know if exist some like KEY_LEFT or whatever was the direction ... for assigning to those keys, at least for a while (while I can do something under android) those key do something, but not what they should do.
Other thing is that, the buttons leds stays power on all the time, and the power button, does nothing and also I'm still lokking for haw to enables it.

[MusikMonk]

My Spanish is probably rusty from lack of practice but I'll try to post in both languages. It's acceptable in the forum rules to use a language other than English as long as the English translation is included.

I've already done what's mentioned in that post you're talking about.

The thread on wing-linux that he's talking about is this one:
http://sourceforge.net/apps/phpbb/wing-linux/viewtopic.php?f=4&t=4
And this thread is for the Opal, it has some development information that aren't mentioned here:
http://sourceforge.net/apps/phpbb/wing-linux/viewtopic.php?f=4&t=6
You'll notice that I got all the keys (except for the power button) working properly.
As for #define HTCHERALD_GPIO_POWER 139, you're right. It does conflict with the touchscreen. I noticed that earlier and changed the value to 135 (which is the GPIO vlaue I got from haret for the power button right before the connection is closed). After doing that, the device no longer starts powering off directly after booting.

If you're interesting in helping with the development, check out the kernel-candidate branch from the git, that one has the latest developments. We should set up a new board for the Opal but till then I'm still just changing the board-htcherald.c. And I attached here the modified version of that file with the keys mapped correctly.
For building, use this:
make ARCH=arm omap_android_850_defconfig && make ARCH=arm CROSS_COMPILE=/home/amarus/CodeSourcery/Sourcery_G++_Lite/bin/arm-none-eabi- zImage

You might want to take a look at all that has been said here and one the Opal thread on wing-linux (the one that I linked earlier). If English is giving you trouble, try running things through http://translate.google.com/ if that didn't help, contact me.

By the way, are you using 0.4pre3 or a different version?

-------------------------------------------------------

Mi español es, probablemente, terrible por la falta de práctica. Pero voy a tratar de escribir en los dos idiomas. Usar un idioma diferente del Inglés, es aceptable en las reglas del foro si la traducción Inglés está incluida.

Ya he hecho lo que se menciona en el puesto que estás hablando.

El "thread" de wing-linux que está mencionado es este:
http://sourceforge.net/apps/phpbb/wing-linux/viewtopic.php?f=4&t=4
Y este "thread" es para la Opal, tiene alguna información sobre el desarrollo que no se mencionan aquí:
http://sourceforge.net/apps/phpbb/wing-linux/viewtopic.php?f=4&t=6

Notarás que tengo todas las llaves (excepto para el botón de encendido) funcionando correctamente.
En cuanto a # define HTCHERALD_GPIO_POWER 139 , tienes razón. Hay conflicto con la pantalla táctil. Ya me di cuenta de eso y ha cambiado el valor a 135 (que es el GPIO que obtení de Haret para el botón de encendido justo antes de la conexión está cerrada). Después de hacerlo, el dispositivo ya no se inicia de apagar directamente después de encender.

Si estas interesado en ayudar al desarrollo, ver el "kernel-candidate branch" del git de wing-linux, que tiene los últimos cambios. Debemos crear un nuevo "board" para la Opal, pero hasta entonces todavía estoy cambiando board-htcherald.c. Y aquí la versión modificada de esto con las claves asignadas correctamente.
Para construir, utilizar esto:
make ARCH=arm omap_android_850_defconfig && make ARCH=arm CROSS_COMPILE=/home/amarus/CodeSourcery/Sourcery_G++_Lite/bin/arm-none-eabi- zImage


Es mejor echar un vistazo a todo lo que se ha dicho aquí y un el "thread" del Opal al wing-linux (mira el "link" anterior). Si el Inglés te da problemas, trata de usar http://translate.google.com/ si no te ayuda, puedo tratar de ayudarte.

Por cierto, ¿estás utilizando 0.4pre3 o una versión diferente?

[darkstar62]

Okay, I tried using the ADS7846 driver and it didn't work.
I tried to take board-nokia770.c as an example and modified board-htcherald.c, as always, and got a new zImage.
Everything boots normally, except that when "checking for tsc2046" appears: instead of getting the calibration screen, android starts booting directly. Obviously it didn't find it.
Afterwards, I tried ts_test and got an error stating that /dev/touchscreen0 doesn't exists. So it seems like the system can't see the touchscreen at all.
Running dmesg seems to confirm this as there's no mention of a touchscreen anywhere in the output (http://pastebin.com/m3920656b).
With the previous driver I had:
input: TSC2046 touchscreen as /class/input/input3

I'm not entirely sure that it's the driver's fault.
It might be that I overlooked something when changing the code. That's not unlikely with my experience. So I'm taking another look at the new structs and trying different values to see if anything happens.

darkstar62, I also wanted to check with you if the current build (pre3) looks for the tsc2046 driver directly in any place beside the initial calibration. I know that this isn't the problem but just to see what I might need to look at.


Edit:
This is the board I'm using: http://pastebin.com/m3b8ad98f
Any touchscreen related changes have //Monk beside them.

Edit2:
Figured out why the system didn't see the screen. It was extremely simple, I just had to change the alias to tsc2046 :)
However, still not working :(
Printk statements showed that the driver isn't getting any calls, not even for initialization. Still can't figure out if I did something wrong or if the driver is simply incompatible.

The board changes you made look right to me. In the dmesg logs, you probably wouldn't see anything about tsc2046 -- it would be ads7846, and you should get an input device from that. If you're not, then it's not registering in your board correctly (did you remember to include the driver in your .config?)

If you see that in dmesg, you should be able to at least start responding to interrupts. I'll dig around a bit, I had an implementation I was trying for herald that at least got interrupts (I got 0, 0 for all my coordinates though).

EDIT: Now that I look at it again, maybe if you put the ads7846_dev_init() call above the spi_register_board_info() call...might have to claim the GPIO before the SPI gets initialized.

- d

[MusikMonk]

The board changes you made look right to me. In the dmesg logs, you probably wouldn't see anything about tsc2046 -- it would be ads7846, and you should get an input device from that. If you're not, then it's not registering in your board correctly (did you remember to include the driver in your .config?)

If you see that in dmesg, you should be able to at least start responding to interrupts. I'll dig around a bit, I had an implementation I was trying for herald that at least got interrupts (I got 0, 0 for all my coordinates though).

EDIT: Now that I look at it again, maybe if you put the ads7846_dev_init() call above the spi_register_board_info() call...might have to claim the GPIO before the SPI gets initialized.

- d

The order of ads7846_dev_init() and spi_register_board_info() it's the same as what's written in the boards of all devices using this driver.
Anyway, it was just being stupid, even for my standards... I did include the driver in .config but, without thinking, I ran make ARCH=arm omap_android_850_defconfig
After fixing my mistake, the driver is now receiving irq (with a value of 299, same as with the previous one).

Coordinates seem to have maximum values instead of 0,0. I have some errands to run so I'll investigate this further when I'm back.
Other devices running this driver seem to have different structs, I'll see if I can come up with something.

Still the implementation you have will definitely be welcomed if you can find it. And if it's not much of a hassle, can you please check what irq value the touchscreen driver is receiving on the Herald and if it's related to what you get from Haret? I'll understand if you don't have the time. I'm just curious about this.

Edit: Coordinates are always x=8163, y=8163, Rt(Pressure?)=0.
Tried different types of structures with various values. Nothing seems to change...
This is starting to get really frustrating...

[raditzgds]

Well thanks Musikmonk for your file (and off course for your translation to spanish).
In order to answer you i'm using 4pre3.
I'm trying some other things to make toucheable the screen, but nothing results at all, but I'm still working.
I'm interestedly, off course, on port android to the Opal, but I'm still too newbie on this.
Im use linux as deskopt OS long time ago, even in my work, I'm using ubuntu now but I'm start with SuSE 5.0 (Before the Novell intervention) so this thing of try to make the things work on unexplored devices results me an interesting thing. Well thanks again and I'll being workin' on port android to opal.
(by the way I'm so far away to results you useful, but ... well here I am... )

[htcfreak]

Hey whatz the user name & password for "gizard-20090703"

[darkstar62]

Hey whatz the user name & password for "gizard-20090703"

Check http://linwizard.sf.net for that.

- d

[raditzgds]

Well Musimonk I compile my kernel with your board-htcherald.c, and the systems boots but not starts the X, sudt says some like can not find rootfs, so I go back to mi borad-htcherald.c and made the changes on the keymap struct definition and It's works, anyway the screen isn't touchable already.
I want to know how you try some others drivers, to help you if is it possible to discard possibilities and find out a solution.
Maybe this was an incredible stupid question but, can the rootfs.img be modifying in order to load somes drivers? like in en iX86 linux, by changing some stuff in the /etc directory or adding services at init.d? for example assigning priorities a some services or modifying the parameters of others? I'm trying to do some analogy with linux for x86.
Well maybe this is an donkey idea, but it's the only I have right now.

[MusikMonk]

I must have made a mistake and uploaded a wrong version of the file. As long as the keymapping works for you the rest isn't that important.

For other drivers, I've only tried one other driver(ads7864) and it's for the same touchscreen
chip (ts2046). That's because all OMAP HTC devices seem to have that same chip. Might be worth a shot to try other ones as well.
Anyway, to do that, I've used a simple method:
-Look for another device that uses the driver you want (grep, should be useful).
-Copy the driver specific definitions, structs and functions to the herald board to replace the ones already there (check my previous posts for an example if you want).
-Change the GPIO value to 139.
-Modify the ".config" file to include the driver you're trying.
-Build the zImage but make sure not to make my mistake and use a command that overwrites the config file.
-Putting some printk statements in the driver code is useful for tracing what's going on.
-I also tried changing some values from the structs I copied to see if I can get different results.

As for your other idea, I'm not sure that it would work. I think that specific driver interfaces are hardcoded in the kernel. Still, I'm as much of a newbie here as you are (apparently even more so ;)). You'll have to check with Darkstar or someone from linwizard about this.

I'm not home right now and I won't have a chance to any testing today before at least 6 houres. I still want to chech something with the drivers I was trying before moving on.

I'll share here what I do so that we don't accidentally try the same things.

[darkstar62]

Well Musimonk I compile my kernel with your board-htcherald.c, and the systems boots but not starts the X, sudt says some like can not find rootfs, so I go back to mi borad-htcherald.c and made the changes on the keymap struct definition and It's works, anyway the screen isn't touchable already.
I want to know how you try some others drivers, to help you if is it possible to discard possibilities and find out a solution.
Maybe this was an incredible stupid question but, can the rootfs.img be modifying in order to load somes drivers? like in en iX86 linux, by changing some stuff in the /etc directory or adding services at init.d? for example assigning priorities a some services or modifying the parameters of others? I'm trying to do some analogy with linux for x86.
Well maybe this is an donkey idea, but it's the only I have right now.

You can log in to it over SSH using a USB cable. Then it's just like most any other Linux -- you have init scripts in /etc/rc*.d, modules in /etc/modules and /etc/modutils, etc. You've also got ipkg (similar to dpkg and apt), so if you can get your phone online (either routing through the usb or over gprs), you can download and install software online with 'ipkg install <progname>'.

- d

[raditzgds]

Lets assume, for a while, this: "the driver TSc2046 works fine" , so the main problem is the power button, so fixing this, at least the complete keyboard was work, and maybe by this way we can disscard conflicts between power btn and touchscreen, I assume that: the keyboad is loaded before the touchscreen.

By the way; and related qith my previos post, je... viewing the "make menuconfig" the drivers are built-in on kernel.... I'll be try to connect by SSH.

[MusikMonk]

Lets assume, for a while, this: "the driver TSc2046 works fine" , so the main problem is the power button, so fixing this, at least the complete keyboard was work, and maybe by this way we can disscard conflicts between power btn and touchscreen, I assume that: the keyboad is loaded before the touchscreen.

I looked at the power button, and actually it is working, just not correctly mapped.
SSH to your device and modify /system/usr/keylayout/qwerty.kl and change line 11 to:
key 116 POWER WAKE
You'll have to either use vi or copy the file via ssh (using scp for example).
After you do that, restart the device and boot android, then the power button will work. It doesn't seem to do anything other than waking the device from standby. You can change "POWER" in that line with another value (I tried "P") to see that it's working properly.
I think that this file should have this change for all devices and not only Opal. Darkstar, am I right?
And I couldn't find anything that suggests a conflict between that button and the touchscreen, other than the value we already changed to 135.

I also noticed another small thing while looking for this, I mapped the dpad center to KEY_ENTER, it should be KEY_SLASH. That way it'll work as dpad center in Android instead of a keyboard enter key. However it would also mean, that before Android boots (during the installation for example), this button will work as a slash '/' (kind of obvious). That's not much of a problem but it's possible to fix it quickly by changing line 44 from:
key 28 ENTER
to
key 28 DPAD_CENTER WAKE_DROPPED
And leaving it mapped to KEY_ENTER.
By the way, look at include/linux/input.h in the kernel source to understand where these numbers are coming from.

I haven't had a chance to try anything concerning the touchscreen yet. I'll see if I can do some testing before my brain shuts down and I have to sleep:D

Oh, and one last thing, the git repos are now at git://wing-linux.git.sourceforge.net/gitroot/wing-linux/wing-linux in case you're trying to update the source and getting an error.

[raditzgds]

Well I do wat you do, and I guess, with the pwr btn solved we can disscard it as a trouble.
Analyzing the make process of the kernel I saw that somo structs was defining but not used, typically this shows a warning at compiling time, o I comment the lines useless on board-htcherald.c
/*static struct tsc2046_platform_data htcherald_ts_platform_data __initdata = {
.ts_x_plate_ohm = 496,
.dav_gpio = 76,
// .dav_gpio = 139,
.gpio_debounce = 0,
.ts_max_pressure = 100000,
.ts_touch_pressure = 5000,
};
*/
/*static struct spi_board_info htcherald_spi_board_info[] __initdata = {
{
.modalias = "tsc2046",
.platform_data = &htcherald_ts_platform_data,
.max_speed_hz = 2500000,
.bus_num = 2,
.chip_select = 1,
.irq = OMAP_GPIO_IRQ(139),
}
};
*/
just change the line

#define HTCHERALD_GPIO_POWER 135

and the keypad; compile and everything fine except for pwr btn and the tsc.

I do the changes of keybord layout; but nothing happen the pwr btn still dead. But maybe for the above reasons... I will try some others idea.. when those arrives....

[MusikMonk]

The structs you commented are used. I'm surprised that the kernel did build after commenting them.
Inside the function
static void __init htcherald_init(void)
there should be this
spi_register_board_info(htcherald_spi_board_info,
ARRAY_SIZE(htcherald_spi_board_info));
I think that there's something wrong in the board file you're using.
And by the way, ".dav_gpio" should be 139, not that it matters much since the driver doesn't work :rolleyes:

It's weird that the power button doesn't work. Can you check something for me? In the herald board, does this struct look the same for you?
static struct gpio_keys_button herald_gpio_keys_table[] = {
{KEY_POWER, HTCHERALD_GPIO_POWER, 1, "gpio-keys: POWER", EV_KEY, 1},
};

You probably have another line for GPIO_SLIDE but that one doesn't matter (for the obvious reason that there's no sliding keyboard for the Opal). Just this line matters.

If you have any other ideas, please don't hesitate to share them.
In the mean time, I'm setting up a new board for the Opal. I'm getting bored of using herald's :p

[MusikMonk]

I think that the RAM on my phone got damaged from the constant testing....
I've suddenly started getting this kernel panic when booting:
KERNEL PANIC - NOT SYNCING: BROKEN PADDING

Right after "extracting initramfs". What's before that is normal.

From my limited knowledge of linux, I believe that this is caused by bad ram modules.
At first I thought that I screwed the code while testing, but I tried a clean installation of 0.4pre3 using default kernel and herald's mtype (a setup that I previously tested and know to work) and I got the same error.
I'm trying to find some tools for diagnosing HTC devices but everything I can find is device specific and nothing for the Opal/Viva.

Till I figure out what's wrong here, I'm not gonna be doing any more testing. I apologize, but I really can't afford damaging my device.

[raditzgds]

Well... welcome at your first "Kernel Panic".. I remember when in a desktop system usually gets that error, 'cause my hdd-controller has some failure.But Puntually in your case that message was printed by the procces:
NORET_TYPE void panic(const char * fmt, ...) (line 65 ../home/german/wing-linux2/kernel/kernel/panic.c) obviously try to change the code to avoid the error is some stupid thing..., this file only have the purpose to handle those events that cause the kernel stop working literaly the file says
/*
* This function is used through-out the kernel (including mm and fs)
* to indicate a major problem.
*/.

So, my friend... I, think you've goy a major problem. Try, deleting rostfs.img and do the installing again.. if the problem persists... I have no idea... maybe your sd is damaged.

By the way I wa triying to load the driver of touchscreen as module... compile the kernel without all drivers SPI (tsc related) an set it's as "M" (MODULE) with make menuconfig; after compile the kernel those gives me an kernel capable of loading modules at runtime. But.. after we need de loadable modules for this use some like this:
~$ make modules ARCH=arm CROSS_COMPILE=/"your-install-path"/CodeSourcery/Sourcery_G++_Lite/bin/arm-none-eabi-
All the modules will be created en each driver directory in the touchscreen case in the /kernel/drivers/spi/ files *.ko; after I add those to the rootfs.tar.gz in the sub dir /lib/modules/<kernel-version>/.
Del the older rootfs.img on your phone linux directory and boot android.
After, with ssh, try to load the modules with modprobe <module>.ko or insmod <module>.ko but don't worry about the complicated of all process; none of the modeles works. :(
Ahhh... my power key still doesn't work ... even do the changes of the qwerty.kl.

[MusikMonk]

Well, it's my first Opal kernel panic, I had a couple of those on computers :)

Already tried deleting rootfs.img and that didn't work. Either way, it's crashing before it reaches the point where it loads that. I have a spare sd card here somewhere, I'll look for it and give that a shot. I hope that it turns out to be the problem although I really doubt that.

Do you know if there's some tool to test device memory? I couldn't find any.

About touchscreen, it doesn't make sense for the Opal to have anything other than tsc2046. Even though I tried a couple other drivers, that's the only one that seemed promising (since it receives irq in the right time). And it's the one used for all omap devices.
Perhaps we need to change some values in the spi_board_info struct. I was planning to try that out before this happened.

By the way, I've registered Opal on http://www.arm.linux.org.uk/developer/machines/
This way it's possible to create a new board for the Opal. This are the steps (taken from http://sourceforge.net/apps/phpbb/wing-linux/viewtopic.php?f=3&t=12):

Some things to note:

* First off, I notice there isn't a machine registration for the excalibur or dash -- you'll need to add one at http://www.arm.linux.org.uk/developer/machines/. Once you've done that, download a new version of the mach-types file from that site and put it in arch/arm/tools.
* The board files live in arch/arm/mach-omap1 -- you'll need to copy board-htcherald.c and board-htcherald-i2c.c. There's also include/asm-arm/arch-omap/board-htcherald.h which you'll need to make a copy of for your board.
* Make sure you change all "herald" references to "excalibur" for your board files and in the header file
* Grep for instances of machine_is_herald(), and add in machine_is_excalibur() (or whatever macro yours is -- derived from the mach-types file).
* Grep for any CONFIG_MACH_HERALD and make the appropriate changes in those files
* Add a CONFIG_MACH_EXCALIBUR (or whatever name makes sense) to arch/arm/mach-omap1/Kconfig and to the Makefile there
* I would recommend copying drivers/video/omap/lcd_htcherald.c for your board, as it contains video auto-detect code that could be useful to you.

I've done this on my laptop but I haven't submitted it.

[MusikMonk]

Seems like it might have been a corrupt SD, I've found the spare card and when I tried it I stopped getting the kernel panic. Perhaps I panicked too much :p

I'm currently trying to figure out where the tsc2046 driver fails. Apparently, that and the ads7846 driver are our best shots. Plus, I can't really think of anything else to do. The only other option is tracing memory through haret to write a new driver, and that's not something I'm planning to do in the near future...

[raditzgds]

After several tryings and analyses I was arrived to this conclusion the drive (perhaps U has noted this long time ago) tsc2046_ts; work but is not converting appropriately the screen coordinates; by ssh using the command cat cat /procs/interrupts (without touching the screen) I obtain the below output (the configuratio board-htcheral have irq 139 for the screen, seems the command make need the target all for remake all modules and .o files) root@localhost:~$ cat /proc/interrupts
CPU0
2: 332 MPU omap_udc pio
3: 0 MPU omap_udc iso
4: 277 MPU GSM ICR
19: 15035 MPU DMA
20: 0 MPU DMA
21: 0 MPU DMA
22: 0 MPU DMA
23: 0 MPU DMA
24: 0 MPU DMA
25: 12285 MPU LCD DMA
26: 18683 MPU mpu_timer1
30: 0 MPU mpu_timer2
31: 9 MPU lcdc
36: 18 MPU i2c_omap
55: 21917 MPU mmci-omap
57: 0 MPU rtc0
58: 0 MPU rtc0
61: 183 MPU omap_udc
66: 142 MPU GSM RF
67: 0 MPU omap-keypad
78: 0 MPU peripheral wakeup
85: 0 MPU DMA
86: 0 MPU DMA
87: 0 MPU DMA
88: 0 MPU DMA
89: 0 MPU DMA
90: 0 MPU DMA
91: 0 MPU DMA
92: 0 MPU DMA
93: 0 MPU DMA
94: 0 MPU DMA
295: 0 GPIO gpio-keys: POWER
299: 0 GPIO tsc2046-ts
301: 0 GPIO i2c-htcpld-btns
Err: 0
root@localhost:~$

As you can see at 299: CPU value 0 GPIO tsc2046-ts is working, if I touch the screen, and perform the same command the output:
299: 2 GPIO tsc2046-ts

Deppendig of the touch instensity and/or durtion this values increments one by one, but this is related with the delay between the performs of the cat command.
bY adding a print output at process static void tsc2046_ts_rx(void *arg) in tsc2046_ts.c before the coordinates convertions:
xN = ((pA * x) + (pB * y) + pC) / pS;
yN = ((pD * x) + (pE * y) + pF) / pS;
And killing X mode (via ssh running the command /etc/init.d/android stop)
each time I press the screen I see the print output wich I definned. Seems to by a conversion problem.
Obviously each modiffication of source code, need a kernel compilation.
By the way I'm happy cause Mr MusikMonk is back In bussness.

[MusikMonk]

I didn't try using "cat /procs/interrupt", because I didn't know it before :o (every noob has to start somewhere, right? :D)

However, I was using printk statements in the driver's code for tracing, and I did notice that it's receiving irq=299 when the screen is touched.

Printing x and y in the function tsc2046_ts_rx give the values 4095 for both. At first I was doing a mistake and printing in the update_pen_state function, that showed the values at 0, 0. I've noticed now that this happens when the timer function calls update_pen_state when the pen is up. But when the pen is down, tsc2046_ts_rx fails to call update_pen_state because the values of x, y and pressure are above limits.

Right now, I'm trying to figure out where the actual reading of the coordinates (and pressure obviously) happens.

[raditzgds]

Yes... that was my idea tray to determinate the correct coordinates...using too a printk en tsc2046-ts.c .... well ... I hope we have a goods news at brief time..

[raditzgds]

Yes... that was my idea try to determinate the correct coordinates...using too a printk en tsc2046-ts.c .... well ... I hope we have a goods news at brief time..

[MusikMonk]

Yes... that was my idea try to determinate the correct coordinates...using too a printk en tsc2046-ts.c .... well ... I hope we have a goods news at brief time..

I'm glad to have someone else working with me on this.

Sadly, I'm not any closer to figuring out what's wrong... Are you doing better than me?

[raditzgds]

well I was thinking propouse you analize the actual tsc2046 driver, lasy nigth I arrivtd to the conclosion evry data sending by the screen device is FFFF, so any conversin (CONv_ d1, d2 ) return a 12 bits answer 4095, I thik maybe the driver reads an erroneus mem address, maybe the error was in the init procedure of the driver. Email me, perhaps we can do some progress

[MusikMonk]

well I was thinking propouse you analize the actual tsc2046 driver, lasy nigth I arrivtd to the conclosion evry data sending by the screen device is FFFF, so any conversin (CONv_ d1, d2 ) return a 12 bits answer 4095, I thik maybe the driver reads an erroneus mem address, maybe the error was in the init procedure of the driver. Email me, perhaps we can do some progress

It looks like we're thinking around the same lines, but this where I got stuck.
I've sent you an email, perhaps I'll be able to help you.

[MusikMonk]

Good news!
With the help of various persons, the Touchscreen is now working! The calibration is still a little bit off but it should be fixed soon.

I've attached the zImage in case anyone is interested in trying it.

* First download wing-linux-0.4pre3-rootfs.cab from http://sourceforge.net/projects/wing-linux/files/Wing%20Linux%20Development/
* Now install it to storage card.
* Download the attached zip file, it contains two files zImage and Default.txt.
* Copy both files to the "linux" folder in your storage card. There should already be a zImage there, overwrite it.
* Now run haret from that folder (or wing-linux under programs in the start menu) and click on run.
* Don't click anything during installation, let it use defaults.
* Grab yourself a cup of coffee and wait till installation finishes, first boot takes a lot of time.

I gave the key mapping in a previous post, but here it is again:
- D-Pad + Centre: works normally.
- Green: Dialer.
- Red: Default behaviour under Android is like this:
* Short press: puts device in standby (check next link for information about that). This can be changed in the settings.
* Long press: Display menu to turn off device (again refer to next link), put device in airplane mode...
- Volume up: menu key (it's the key that unlocks the screen as well).
- Volume down: back/cancel.

Look here for some informations that you might need:
http://sourceforge.net/apps/trac/wing-linux/wiki/FAQ

This is the status of wing-linux on the herald:
http://sourceforge.net/apps/trac/wing-linux/wiki/Status
We're still missing these stuff:
- Backlight
- LEDs
- Bluetooth
- Vibration

And I'm having trouble setting up my APN, I might be using wrong settings. Unless someone else confirms this issue, I'm gonna consider it an error from my side.


If anyone has some questions or bugs to report, feel free to do it here. But please avoid questions already covered in the FAQ linked above.

[angel7.cz]

Wow man that looks great. I will try it and post my feelings. Thank you very much.:)

[angel7.cz]

Installing and booting ... Ok.
Android and apps are running smoothly.
GSM, WiFi, BT, Batery not working.
It looks realy great but not usefull at this point.
TouchScreen is moved little bit.
Good work ! Looking forward for some news.

[MusikMonk]

Installing and booting ... Ok.
Android and apps are running smoothly.
GSM, WiFi, BT, Batery not working.
It looks realy great but not usefull at this point.
TouchScreen is moved little bit.
Good work ! Looking forward for some news.

First of all, thanks for the feedback.

GSM should, to a certain extent, work. On my phone I was able to make calls (mic works, so the other side can hear you but you wont hear them), receive and send SMS. Incoming calls are disconnected directly but show up in the log.
And as I wasn't able to set up my APN, I was unable to test GPRS.
And yeah, touchscreen calibration is a little bit off. I'll see if I can get this fixed tomorrow. Can you tell me what problems did you have?
And by the way, if your SIM is locked, you'll need to unlock it from WM first. Although Android can accept the pin and unlock the SIM, it'll have trouble connecting to network afterwards.

Development is probably going to be slow, it seems that there's only raditzgds and me working on the Opal. And, although I have been lucky with some stuff so far, I lack the experience and knowledge for this project. I'm still learning as I go. Plus, at the moment, our progress won't go beyond what wing-linux are achieving, and that project is also suffering from lack of developers.

[phatboijp]

thanks musikmonk!! ive been keeping tabs on this for the past few weeks, wow! you're the only reason why i think i might be keeping my viva hahahaha!!! please keep up the good work, we owe you a lot! i wish i could help!!!! but i don't know any programming , i'll be learning soon tho ...but not going to be in your level anytime soon! how long do you think it will take till wifi starts working hahhahaha!!!

[angel7.cz]

Ok i need to unlock my sim thak you:) Well i have some knowlage of programing in c++, but realy don't know what should i do to help you with development (where to start). So maybe i can help you little bit. Sorry for my english :)

[XirXes]

I tried it out today and I had some different results than others. First, my touch screen seemed pretty accurate, tho I didn't use the stylus. Second, I was able to make an outgoing call.

[MusikMonk]

Sorry for disappearing for a while.

I tried it out today and I had some different results than others. First, my touch screen seemed pretty accurate, tho I didn't use the stylus. Second, I was able to make an outgoing call.

Yes, making outgoing calls is something you should be able to. I'm not sure if we should be able to receive calls or not. It's not like it'll be of any use without sound, but I'll check with the wing-linux guys to get this out of the way.
Using stylus you'll notice that calibration is a little off, but that's no longer an issue. The touchscreen can now be calibrated on first boot.

Here's the Opal's status in the project:
http://sourceforge.net/apps/trac/wing-linux/wiki/HTCOpal
The question marks should read "Not working", I'll ask someone to update it later.

I've submitted some patches to wing-linux so they can add some support for our device. The next build (0.4pre4) should be out soon, when it is, it'll have cabs for the Opal making things easier.

Besides touchscreen calibration, not much has changed. This build of wing-linux is mainly done to include new devices.
Once it's out, I'll probably make a fresh new thread to be able to keep things updated and tidied up.

I'm currently working on getting bluetooth to work, can't tell when/if I'll get it right. raditzgds seems to have disappeared, so I don't know if he had better luck than me or if he's still going in the same direction.

And about sound and wifi, it'll probably be a while. I'm not helping with the development for those, so I don't know the exact details. Developers from wing-linux and linwizard are working on it.

[jagan2]

Thank u bro i left the idea of android os just then today i read ur post in which u gave default.txt boot script for opal plus ur image file i did according to ur instructions and succeeded although i had to uninstall and reinstall the cab two times. Now about the rom its excellent its speed is really awesome but bro when enabling and disabling something for example airplane mode its too much slow. Plus its not searching any network i wanted to use interent but no network searching even for calling someone :( just just now installed will tell if i get some problems.

And yes ur awesome developer.


Bro one more request can u port the latest wm 6.5 build 23047 to opal through ervius kitchen if u need help porting i will do actually me net slow so i cant download the kitchen and port further my exams are going on will u plz i request? :)

[MusikMonk]

You're giving me too much credit here :D
I'm only trying to get the Opal supported by making small changes to what the developers of wing-linux and linwizard already did.

Is you SIM locked by any chance? If it is, you'll need to unlock it from windows before booting android. Even though Android can accept the PIN code and unlock the SIM, it'll have trouble connecting to network after that.

For speed, I really can't help there. I'm only working on kernel level support (i.e. drivers and the like), actual Android development is being done by darkstar62.
Still, speed might be slightly improved in the future, I think that the processor is running at 195mhz, it might be possible to run it at 201mhz in a next version (not THE next version). But don't take my word for granted.

And about my last post, I checked with darkstar62 about incoming calls, it's a know bug. Should be fixed in the next version.

By the way, someone made a small tut for installing apps on Android, it requires using a linux distro on the pc:
http://www.youtube.com/watch?v=Wwk25mBHYsw
It can be done in other ways as well such as scp (copy over ssh).
I haven't tried it myself, and I haven't even searched for a place to download applications from.


And please, everyone keep in mind that this is a work in progress. It's still far from being a complete replacement for WM.


For WM6.5, I haven't tried cooking roms before. So far I've been avoiding 6.5 because I don't want to deal with it bugs. I might give it a look if I find that I have the time. I can't promise anything.

[bttoxic]

thanks!!!!

[MusikMonk]

The new development release (0.4pre4) from wing-linux is out. You can download it from their site here:
http://wing-linux.sf.net/
The download link is on the right.

The zip, that you'll find there, has multiple cabs. You'll only need to install two of them: rootfs and opal.

Please refer to these links for more informations:
FAQ: http://sourceforge.net/apps/trac/wing-linux/wiki/FAQ
Device Status: http://sourceforge.net/apps/trac/wing-linux/wiki/HTCOpal
Main features of new release: http://sourceforge.net/apps/phpbb/wing-linux/viewtopic.php?f=3&t=30

[jagan2]

Thanks bro for the quick reply i didnt expected that so was offline yesterday.
Now i gave so much credit to u because until wing linux 0.4pre3 they have not given opal board support so i was unable to boot android on opal after using ur image and opal boot script i successfully installed opal.

Thanks for informing about wing linux 0.4pre4.

Now bro i experimented little and found this:
Actually first i inserted airtel sim(india) i donno what it is i mean i think its gsm only but not worked.
Then i inserted reliance gsm sim it worked. And about the speed problem i was saying that android is much much faster then wm but when switching something like switch from cellular mode to airplane mode it takes long times never finished i had to soft reset and also android dont shutdowns everytime i have to soft rest.
Now about the gprs it completely dont works i tested the android emulator on pc and found that in apn menu automatically there a connection would appear but in the mob in apn section nothing appears plus no option to add new connection :mad:
And one more thing due to lack of keypad on htc opal we are unable to specify the android installing size i mean it by default installs 250 mb due to this iam unable to access storage card. and one more thing how to explore storage card in android.

When the boot starts screen looks awesome because i have never seen pc like boot on mobile :D

And about wm 6.5 rom i didnt say to cook a room but porting. Porting means copying the xip and sis file of rom of some other device like daimond to opal rom its basically rom upgrading a thread is there in opal rom development that is ervius visual kitchen. U dont have to cook something just follow the steps and a new rom will be created actually my net is too slow to download the kitchen so i was requesting u anyways will try to download the kitchen if u have time then plz say i will guid u through remote support then a new Chief for opal will be born :D and that is u.

Once again thanks for the reply hope will reply this one too :D

[MusikMonk]

...
android dont shutdowns everytime i have to soft rest.


Shutting down doesn't work yet, it's best to follow this:
https://sourceforge.net/apps/trac/wing-linux/wiki/FAQ#Q:OkthenhowdoIreboot


Now about the gprs it completely dont works i tested the android emulator on pc and found that in apn menu automatically there a connection would appear but in the mob in apn section nothing appears plus no option to add new connection :mad:


You can add a new APN connection. Go to APN settings and click the menu button (Volume Up) and you'll find the option to to that.
However, there's currently an issue with entering new APN data, if it's not already listed in the file apns-conf.xml, it won't be accepted. You can add it there via SSH.


And one more thing due to lack of keypad on htc opal we are unable to specify the android installing size i mean it by default installs 250 mb due to this iam unable to access storage card. and one more thing how to explore storage card in android.


The default space is enough for now, you won't need anything bigger. Once more space becomes needed, this can be easily fixed.
Using 0.4pre3, Android didn't read the storage card correctly. That was fixed in pre4. As for exploring the card, Android doesn't have an application for that by default, you'll need to install one.

For WM, I'll send you a PM in a minute.

[jagan2]

Do one thing bro send me pm in which tell me ur yahoo id and come online in yahoo messenger now there we can discuss comfortably.:)

[msigeek]

Woahhh.. I just booted Android on my HTC Viva. its just funntasstic..! I never, loved the UI on my mobile so much before.

I really wish if we can build a build, with which I can run this permanently on this device. Great job guys.

Cheers'
Vijay Raj
MS-MVP [Setup-Deploy]
www.msigeek.com (http://www.msigeek.com)

[matzino]

hi!!! with this new version android works on my viva (opal)! but in my case the htc shows a block screen and says to press menu button... how could unlock it? We don't have menu button.

Thanks

[MusikMonk]

hi!!! with this new version android works on my viva (opal)! but in my case the htc shows a block screen and says to press menu button... how could unlock it? We don't have menu button.

Thanks

Key mapping is already posted:


I gave the key mapping in a previous post, but here it is again:
- D-Pad + Centre: works normally.
- Green: Dialer.
- Red: Default behaviour under Android is like this:
* Short press: puts device in standby (check next link for information about that). This can be changed in the settings.
* Long press: Display menu to turn off device (again refer to next link), put device in airplane mode...
- Volume up: menu key (it's the key that unlocks the screen as well).
- Volume down: back/cancel.


Power button can work but is currently not mapped to anything as standby is still not working.




I'm currently working on bluetooth, there's some progress but it's still not really usable yet. If anyone cares to see the modified code for bluetooth, contact me.

[matzino]

THANK YOU!. great! thanks i've no read that.

[msigeek]

Hi MusikMonk, Kindly lemme know, if we have any updates regarding this.

Cheers'
Vijay Raj
MS-MVP [Setup-Deploy]
Weblog: www.msigeek.com

[rhiakath]

Is there any place where i can get a tutorial, or an how-to about installing android on my HTC Touch Viva (Opal) ?

Thanks

[MusikMonk]

Is there any place where i can get a tutorial, or an how-to about installing android on my HTC Touch Viva (Opal) ?

Thanks

Eveything you would need to know have already been posted or at least linked in this thread, please look in the previous pages.



Sorry for the lack of updates, but, truth be told, there isn't much to say. My university started a couple of weeks ago and I haven't been able to give this much time.
The guys at wing-linux and linwizard are trying to move to a newer kernel (which should get sound and wifi working) but I'm having some issues getting the Opal to work with that kernel.
With the older kernel, I managed to get bluetooth somewhat working but it was highly unstable, which is why I didn't post about it. The newer kernel might fix that.
Vibration, leds and backlight will probably take a while as the relevant hardware seems to be different from that of other devices.

[tuxonhtc]

Just bought my brand new HTC touch, and installed the Android (thanks musicmonk! u rock!).. Thanks to winglinux.. :) Just awesome! Far better than crapdos mobile :p

Musicmonk, thanks for ur efforts! I'm sure you'll get the wifi golden soon..

But the problem is that It won't shut down :( even the soft reset key aint workin!

[MusikMonk]

It won't shut down :( even the soft reset key aint workin!

That can't be the fault of wing-linux, soft reset doesn't have anything to do with the system. It's pretty much like taking the battery out and putting it back in.

Try the stuff here:
http://sourceforge.net/apps/trac/wing-linux/wiki/FAQ#Q:OkthenhowdoIreboot

If that didn't work, remove the battery and you'll be back to windows when the device is on. But I would advice you to check if the reset button works or doesn't at all.

[tuxonhtc]

That can't be the fault of wing-linux, soft reset doesn't have anything to do with the system. It's pretty much like taking the battery out and putting it back in.

Try the stuff here:
http://sourceforge.net/apps/trac/wing-linux/wiki/FAQ#Q:OkthenhowdoIreboot

If that didn't work, remove the battery and you'll be back to windows when the device is on. But I would advice you to check if the reset button works or doesn't at all.

Oh so it's supposed to work like this.. Nevermind, i'll proceed with battery removal :(

Still android rocks, even with these limitations.. I guess I made the wrong choice.. :( Anyways thanks a lot for porting this properly to Opal! Keep us updated musicmonk.

Cheers! :)

[XirXes]

It looks like excitement has dwindled here a bit but for anyone that would like to know Wing linux 0.4 came out a few days ago. Get it here. (http://sourceforge.net/apps/trac/wing-linux/wiki)

[MusikMonk]

It looks like excitement has dwindled here a bit but for anyone that would like to know Wing linux 0.4 came out a few days ago. Get it here. (http://sourceforge.net/apps/trac/wing-linux/wiki)

I'm really glad to see someone else is interested in this :D

I've been meaning to post that, but haven't gotten around to doing it.
This version doesn't differ by much from 0.4pre4. Probably the only thing you'll notice is the inclusion of "AndExplorer" which is, as the name implies, a file explorer. That should make installing apps easier (just copy the .apk files to /system/app and you're done). So again, don't think that you'll be able to throw WinMo away just yet.

The next planned release is 0.4.1, the main goal of that release is upgrading to the latest Angstorm distro.

Some work is being done by darkstar62 and the linwizard guys to get the upstream kernel working for omap devices. But I haven't had much luck with Opal yet.

[Lord Magnus]

The alredy released 0.4!

[jagan2]

Musikmonk can we expect android 2 on viva or first android 1 will be developed?:)

[MusikMonk]

Musikmonk can we expect android 2 on viva or first android 1 will be developed?:)

Don't wait for that to happen. At the moment the next goal is switching to the newer kernel to get everything working (sound, wifi, camera...).
So, until that happens, it's very doubtful that wing-linux would switch to a different Android version. Especially since wing-linux's general goal is to get Linux working on omap devices with Android just being the user interface of choice.

[Lord Magnus]

Don't wait for that to happen. At the moment the next goal is switching to the newer kernel to get everything working (sound, wifi, camera...).
So, until that happens, it's very doubtful that wing-linux would switch to a different Android version. Especially since wing-linux's general goal is to get Linux working on omap devices with Android just being the user interface of choice.

Can't wait for them to do that. As soon as everything is working, I'll switch to android as main system... :)

[jagan2]

Musikmonk but still the development is going too slow. Still there are many peoples who are supporting this project we love android. I also cant wait to see all the working things on android and succesfully running on opal.:)

[MusikMonk]

Still there are many peoples who are supporting this project...

Correction, there are many people who are waiting for this project to finish. And a few actually working on it.


I also cant wait to see all the working things on android and succesfully running on opal.:)

Well then, why don't you try to help with development. ;)

[jagan2]

hmm... musikmonk sure i would like to help u as well as the development but i dont think i could coz i have no idea on linux.. If there is anyway i can help tell me i will surely try my best. :)

[MusikMonk]

Wing Linux 0.4.1 Released:

http://forum.xda-developers.com/showthread.php?t=586333

[jagan2]

Wing Linux 0.4.1 Released:

http://forum.xda-developers.com/showthread.php?t=586333

Just saw, some very good improvements i will try this soon after the download completes. Thanks for informing good luck for the development.:)

[Lord Magnus]

Wing Linux 0.4.1 Released:

http://forum.xda-developers.com/showthread.php?t=586333

I'm passing through the first boot with this release. I don't know if it's something with my cell phone or what...

[MusikMonk]

I'm passing through the first boot with this release. I don't know if it's something with my cell phone or what...

That's weird, as far as I know the kernel haven't changed. So there's no reason for this to stop working on the Opal.
I haven't had the chance to try this yet. I'm installing the cab right now and I'll post what I find.

Edit:
Works fine for me, booting time is a lot shorter than before and the whole system has a snappier feeling to it.
Delete rootfs.img (NOT rootfs.img.status) from /Storage Card/linux then make sure that you have at least 250MBs free on the sd card and try booting again. If it doesn't work, tell me exactly what you see.

[Lord Magnus]

That's weird, as far as I know the kernel haven't changed. So there's no reason for this to stop working on the Opal.
I haven't had the chance to try this yet. I'm installing the cab right now and I'll post what I find.

Edit:
Works fine for me, booting time is a lot shorter than before and the whole system has a snappier feeling to it.
Delete rootfs.img (NOT rootfs.img.status) from /Storage Card/linux then make sure that you have at least 250MBs free on the sd card and try booting again. If it doesn't work tell me exactly what you see.

Oh, maybe that is the problem. I didn't have that free space.
I get this error:
switch_root: chdir(/mnt/loop0): No such file or directory

I waited all night yesterday and nothing happened. I'll cleaup the SD card and try again.

[MusikMonk]

Oh, maybe that is the problem. I didn't have that free space.
I get this error:
switch_root: chdir(/mnt/loop0): No such file or directory

I waited all night yesterday and nothing happened. I'll cleaup the SD card and try again.

Yeah, that sounds like a space issue.
By the way, if you didn't already try a second time. You might want to try 0.4.2:
November 21, 2009

We received feedback from Star Trek users that the 0.4.1 release would not boot, even though 0.4 would. We tracked this down to a problem in the build system, and have released 0.4.2 to correct this issue.

Additionally, 0.4.2 includes the ability to reboot your phone from Android -- simply hold down End and select Power Off. Your phone will reboot.

Enjoy!

http://wing-linux.sf.net/

[Lord Magnus]

I have tried to install, with 4GB free space, and the boot gets freezed in "Configuring compcache-module". I'ts been like this for the past 2 hrs... I'm afraid to turn it off... :p

Do you think it would be possible to have some kind of scrub for WM to allow choosing the OS you want to boot? It would be a good idea don't you think?

[MusikMonk]

I have tried to install, with 4GB free space, and the boot gets freezed in "Configuring compcache-module". I'ts been like this for the past 2 hrs... I'm afraid to turn it off... :p

Do you think it would be possible to have some kind of scrub for WM to allow choosing the OS you want to boot? It would be a good idea don't you think?

I apologise for taking so long to reply, got busy with uni midterms...
Anyway, about choosing what OS to boot, I've heard that there's already a boot-loader called EOL. I haven't looked at it however, right now I don't find it that essential as linux/android is still far from being completely usable.
Plus, right now Windows is configuring the radio (as in all phone functionalities) for Wing-Linux, so if we're to use a boot-loader we'll lose that. But don't be turned down by this because that can be easily fixed.

As for the error you're getting, I honestly don't have a clue. Perhaps you're using a wrong default.txt? Check if the mtype in your default.txt is 2392, that's the one for Opal. But I'm only guessing here, I'll point some more experienced people here to see if they can help.

[Lord Magnus]

I apologise for taking so long to reply, got busy with uni midterms...
Anyway, about choosing what OS to boot, I've heard that there's already a boot-loader called EOL. I haven't looked at it however, right now I don't find it that essential as linux/android is still far from being completely usable.
Plus, right now Windows is configuring the radio (as in all phone functionalities) for Wing-Linux, so if we're to use a boot-loader we'll lose that. But don't be turned down by this because that can be easily fixed.

As for the error you're getting, I honestly don't have a clue. Perhaps you're using a wrong default.txt? Check if the mtype in your default.txt is 2392, that's the one for Opal. But I'm only guessing here, I'll point some more experienced people here to see if they can help.

No problem anymore. Did a hard reset and the android loaded beautyfully. The only problem is that SMS is not working. I can't open de inbox.

Thank you!!!

[MusikMonk]

No problem anymore. Did a hard reset and the android loaded beautyfully. The only problem is that SMS is not working. I can't open de inbox.

Thank you!!!

I've only tried SMS with 0.4pre1, methinks. I'll check later if it works for me on 0.4.2.

I have a uni free week so I'm planning to try if I can get the Opal to catch up with the Herald for the upstream kernel. If that happens we would be a lot closer to a functional system.

[TheRem]

i'm also interested... i'll try this later when i get home.

[TheRem]

wow! it works!

i can sms and call (though i can't hear anything).

[logicfox]

MusicMonk,

0.4 worked great on my Opal. However, 0.4.2 doesn't get past the calibration screen. After calibration, it dumps me at a prompt that says:

net.ipv4.conf.all.rp_filter = 1

and the cursor keeps blinking. Any idea why? Looks like one more person is having the same problem at the Wing-Linux Opal SF forum. :(

[alpert]

first of all, thanks for all the work you do for giving us a working "androidphone" :D
i tried wing linux on my htc viva and it works.. not at all!

the first time i booted, it stopped at configuration of "compcache" trying to calibrate the screen but nothing else happend..
so i rebooted the device and re-run haret. this time android started!
but when i run it for the second time it shown a window saying "SIM locked", the clock and "for unlocking the screen click on menu button".
the htc vivo doen't have the menu button.. :confused:

after a while i found the "menu" button: is the "volume-up"! so now i could unlock the screen..
summarizing, for the htc touch viva we have this button configuration:
volume up: menu (unlock the screen, opens the menu of each application and the desktop menu)
volume down: go back (closing applications, screens, messages, ...)
end call: closes applications and, if hold down for a while, show the option panel (also for rebooting the device)
start call: opens the phone application (numer dialing, sms, contacts, ..)

however, i'm just a beginner on linux and i have no experience on kernel and hardware configuration, but i'd like to help in some way that project, because i'm really interested on using android on my htc..
is there something i can do? btw, i'm studying computer engineering so this is a good chance to learn someting new..

[MusikMonk]

First of all, I apologise for not responding earlier.
I've been rather busy with university work (still am actually, I have three homework due tomorrow, two of which I was given today).

MusicMonk,

0.4 worked great on my Opal. However, 0.4.2 doesn't get past the calibration screen. After calibration, it dumps me at a prompt that says:

net.ipv4.conf.all.rp_filter = 1

and the cursor keeps blinking. Any idea why? Looks like one more person is having the same problem at the Wing-Linux Opal SF forum. :(

I'm not sure what cold have caused this, tried reproducing and did around a dozen installation but it didn't happen on my side. The only thing that happened occasionally was a freeze.
Usually, reseting the device and starting wing-linux again would do the trick. Have you tried that??
If that didn't work, delete the rootfs.img (not rootfs.img.status) file in the linux directory on your sd card and try booting again.

@alpert: I've just posted a reply to your post on the wing-linux forums :D
I've posted the keymapping somewhere in this thread. But I guess it has been buried.

Been meaning to post a new thread dedicated to wing-linux on the Opal to keep things updated, but haven't had the time to do it yet. (If anyone is feeling up to it, be my guest).

Edit:
I haven't noticed this thread earlier:
http://forum.xda-developers.com/showthread.php?t=598996

The blog linked there seems nice, it'll probably be useful for newbies:
http://omokute.blogspot.com/2009/11/android-on-htc-opal.html

[alpert]

sorry, but i have to post my answer here because sourceforge forum doesn't accept it..

@musikmonk:
don't worry for your delay, as a universitary student i understand you

:mrgreen:
and i'm a bit busy too in these days.. but thanks for your answer!
btw, in Italy we call Informatics Eng. too, but i heard some people in

other countries calling it computer eng., so.. (darioshow, i'm italian

too!)

I forgot to post the keymapping here, I only posted it to the xda

forums. As the Viva doesn't have many buttons, I had to sacrifice the

volume keys.
As I haven't used an Android device, I have no clue if this will prove to

be an issue in the future. But I doubt that it would be more than an

annoyance when wanting to change volume quickly.

ok i found it here:

http://forum.xda-developers.com/showthread.php?t=462188&page=3
why don't we add a page that explains these information on the status

porting of htc opal? maybe under the "notes" column of each topic..

can you please post what WM rom you've been trying with?

wing linux 0.4.2

I can think of two areas to work with;
1) The bluetooth driver: I think that the thread I posted here sums up the

important sides of what I did, but I'll take a look later to see if there's

more info to be added.
2) Moving to upstream: There's some work being done by darkstar62 and

linwizard devs to switch to the newer linux-omap kernel and getting omap850

officially supported there.

ok, i'll think about that.. i will also read your post about bluetooth here

in opal forum.

but i can't understand this:
what are the differences between wing-linux and linwizard?
wing uses the kernel developed under lin? because the cpu architecture is

the same, isn't it?


@darioshow:
i'm to hear you tried it again!
the gsm network doesn't work also for me (i use vodafone), but i have no

hurry :)
go on on testing features!

[sanchitgrover]

after a while i found the "menu" button: is the "volume-up"! so now i could unlock the screen..
summarizing, for the htc touch viva we have this button configuration:
volume up: menu (unlock the screen, opens the menu of each application and the desktop menu)
volume down: go back (closing applications, screens, messages, ...)
end call: closes applications and, if hold down for a while, show the option panel (also for rebooting the device)
start call: opens the phone application (numer dialing, sms, contacts, ..)

bro,i tried the same... but when i press the volume up button it takes me to some other page,which has a blinker on it's top... but i wasn't able to come out of the lock.
my screen just showed pres the menu button to unlock..
i'm notable to receive calls when... no voice....
i also want android on my opal,but it's solely dependent on devs...

[Lord Magnus]

after a while i found the "menu" button: is the "volume-up"! so now i could unlock the screen..
summarizing, for the htc touch viva we have this button configuration:
volume up: menu (unlock the screen, opens the menu of each application and the desktop menu)
volume down: go back (closing applications, screens, messages, ...)
end call: closes applications and, if hold down for a while, show the option panel (also for rebooting the device)
start call: opens the phone application (numer dialing, sms, contacts, ..)

bro,i tried the same... but when i press the volume up button it takes me to some other page,which has a blinker on it's top... but i wasn't able to come out of the lock.
my screen just showed pres the menu button to unlock..
i'm notable to receive calls when... no voice....
i also want android on my opal,but it's solely dependent on devs...

Well in fact, the key configurations is in the begining of the thread. :)

[alpert]

bro,i tried the same... but when i press the volume up button it takes me to some other page,which has a blinker on it's top... but i wasn't able to come out of the lock.
my screen just showed pres the menu button to unlock..
i know man, i have some problem too with that screen.. try to use the volume down.. but it makes me crazy sometimes and i don't know how to resolve the prbolem! just wait and retry..

i'm notable to receive calls when... no voice....
audio is not supported yet

[thestory101]

is this still an emulator or have to flash rom ? i still not get an idea ?
Please post some screenshot to show me please ?
thanks

[MusikMonk]

is this still an emulator or have to flash rom ? i still not get an idea ?
Please post some screenshot to show me please ?
thanks

It's neither.
What Haret does is something like this: First, it takes control of the device memory, it stops all the Windows Mobile processes and then it gives the memory to a linux kernel so it can boot.
So it's not an emulator because it doesn't run on windows but in it's place. And there's no need to flash the device to get it running.

There are some vids here:
http://sourceforge.net/apps/trac/wing-linux/wiki/Videos

[thestory101]

It's neither.
What Haret does is something like this: First, it takes control of the device memory, it stops all the Windows Mobile processes and then it gives the memory to a linux kernel so it can boot.
So it's not an emulator because it doesn't run on windows but in it's place. And there's no need to flash the device to get it running.

There are some vids here:
http://sourceforge.net/apps/trac/wing-linux/wiki/Videos

Thanks MusikMonk , for light me up.

But after it's finish . Could it flash to permanent in rom ?
ps. if i wanna try on my opal , it's won't affect to my device right ?

[MusikMonk]

Thanks MusikMonk , for light me up.

But after it's finish . Could it flash to permanent in rom ?

I don't think that it's possible to completely get rid of windows mobile. The best that can be done, as far as I know, is having a bootloader that allows choosing what you want to boot (WM or Wing-linux) when the device is turned on.
I've been told that there's a bootloader called "EOL" that can do that, haven't tried it myself.
But at the time being, wing-linux depends on windows for initializing radio. So right now, if we don't start wing-linux after windows, it wouldn't have any phone functionalities. It's possible to change that but I don't think that it's very important at the time being.

[MusikMonk]

Just wanted to tell you that this project isn't dead yet.
I'm still unable to find time to work on this (and by the looks of it, I won't be able to get anything done before the end of semester one month from now). But I was taking a look at the wing-linux forums and found this:
http://sourceforge.net/apps/phpbb/wing-linux/viewtopic.php?f=4&t=45

Looks like it won't be much longer till we have audio :D

[jagan2]

Great muskimonk thanks for sharing and also dont worry this project wont be dead as we would always be supporting u and ur team.:)

[amidore]

How we return windows mobile?
Do have a return? :confused:

[amidore]

wing-linux-0.4.2-opal
wing-linux-0.4.2-rootfs install and run ......... process began

but
did not complete the process :(
I soft reset, turned wm :rolleyes:

[jagan2]

As its already proved that Android can be run on our opal (omap-850 device) which is based on a linux. So i was just thinking whether we could run maemo which is another new and linux based operating system? I know it required higher hardware requirement still i just want to know is it possible to run that?

[gp.triple]

someone knows these projects?
archmobile.org/
omapedia.org/wiki/Main_Page

[anticshree]

Hi

There is no default.txt in given zip file.

shri

[gp.triple]

Hi

There is no default.txt in given zip file.

shri

this is an old thread
you can find all the new info here
http://forum.xda-developers.com/showthread.php?t=628917

[genius_y]

tried twice... but installation process couldnt complete
has to soft reset

anyone? thanks

[preetdil.singh]

When I am trying to install version 0.4.2
I have both the files opal and rootf and i have installed the both but when i run wing linux at the time of configuring compcache-Module it got stuck.I have tried it reinstalling but same problm is coming.
This is my first time I am trying to install the android on my touch viva.................
help me so that i can install it..