[Wiki] Google Andriod for Herald and Tmobile Wing

[darkstar62]

Is this current work checked in to svn?

Where can I find it?

I don't have it available quite yet -- still trying to work out the remaining kinks with the touchscreen.

All I did to get cupcake working was to download the sources from Google and build it. Then I copied the contents of the <build_root>/out/target/generic/system to my device and tweaked the init.rc to align more with what they had in <build_root>/out/target/generic/root.

As for the kernel, I've attached the latest one, along with the /etc/pointercal file that goes with it. You'll need that to use the touchscreen in GPE. Just point your default.txt at the new kernel to boot it (you'll need to copy in pointercal to your /etc directory in Linux before you can use the touchscreen there). If you've got SSH access to your phone from Linux, it's as easy as:

scp pointercal root@10.100.0.1:/etc

Otherwise you might want to use a card reader and copy it from Linux on your computer.

I *think* android 1.0 should work with the updated touchscreen driver, but I don't know -- haven't tested it.

- d

[expone]

Hmm. I have already touchscreen support on GPE with your package "wing-linux 0.2". Also the keyboard is working nearly correctly.

However, once I start, android crashes by pressing some key - I have been reported it.

As a no linux expert - I can't understand why the touchscreen and keyborad works on GPE and not under Android.

According my knowledge, driver will compile in the linux kernel. But we use the same kernel for both surfaces (GPE/Android) over HARET, or not?

When it true, it must imply that android knows the correct driver for keyboard and touchscreen, or not?

[darkstar62]

Hmm. I have already touchscreen support on GPE with your package "wing-linux 0.2". Also the keyboard is working nearly correctly.

However, once I start, android crashes by pressing some key - I have been reported it.

As a no linux expert - I can't understand why the touchscreen and keyborad works on GPE and not under Android.

According my knowledge, driver will compile in the linux kernel. But we use the same kernel for both surfaces (GPE/Android) over HARET, or not?

When it true, it must imply that android knows the correct driver for keyboard and touchscreen, or not?

Yeah, the key crash in Android is still an issue. I think we're missing a mapping from our keyboard to Android's key layouts. Haven't worked on it yet though.

Yeah, the touchscreen is a weird beast with Android. What works beautifully in GPE and everywhere else in Linux causes headaches for Android. It depends on the driver giving very precise events (like pen-up and pen-down at the right moments, along with device coordinates in the correct scale) that things like tslib (which GPE uses) can calibrate around. So basically, we have to calibrate the touchscreen driver to android, not the reverse which to me would make more sense...oh well.

Yeah, the same driver is used for both GPE and Android -- changes we make in the touchscreen driver have little effect on GPE (other than requiring a new pointercal file -- easily generated with the ts_calibrate program...which I just realized isn't distributed in WL-0.2...oops).

- d

[ivanmmj]

Yeah, the key crash in Android is still an issue. I think we're missing a mapping from our keyboard to Android's key layouts. Haven't worked on it yet though.

Yeah, the touchscreen is a weird beast with Android. What works beautifully in GPE and everywhere else in Linux causes headaches for Android. It depends on the driver giving very precise events (like pen-up and pen-down at the right moments, along with device coordinates in the correct scale) that things like tslib (which GPE uses) can calibrate around. So basically, we have to calibrate the touchscreen driver to android, not the reverse which to me would make more sense...oh well.

Yeah, the same driver is used for both GPE and Android -- changes we make in the touchscreen driver have little effect on GPE (other than requiring a new pointercal file -- easily generated with the ts_calibrate program...which I just realized isn't distributed in WL-0.2...oops).

- d
I wonder if that's because Android doesn't use styluses. It probably expects a screen that doesn't require a stylus or alignment.

[darkstar62]

I wonder if that's because Android doesn't use styluses. It probably expects a screen that doesn't require a stylus or alignment.

That would seem to mesh with what I've found online. The synaptic capacitive touch screen that's used in the G1 doesn't need to be calibrated. Makes life kinda hard for those of us with resistive touch screens...:)

- d

[expone]

Perhaps, the following article is able to help us?

http://www.kandroid.org/android_pdk/keymaps_keyboard_input.html#androidKeymapKeyLayout MapTitle

[darkstar62]

Perhaps, the following article is able to help us?

http://www.kandroid.org/android_pdk/keymaps_keyboard_input.html#androidKeymapKeyLayout MapTitle

Awesome, that should help a LOT! All kinds of good stuff in there. I'll have to take a look, it doesn't specifically mention touchscreen drivers, but their input sample driver is close.

Great find, expone!

- d

[EDIT: Added the link to the wing linux wiki homepage]

[expone]

Perfectly!

I had the page already found long ago, before this topic. But then, I couldn't find it again. But know, they can help us, I hope so ;)

It is too a great chance for noobs like me, in context of linux development. It could be to help me to get a understanding of linux and driver development.

Finally: You, darkstar, hat now the task develop a full supported android for my wing. let's go!

[darkstar62]

Go here:

http://www.youtube.com/watch?v=2aakZoAmHJg

Then go here:

http://dl.getdropbox.com/u/198699/linux_wing/wing-linux-0.3pre1.zip

- d

[ivanmmj]

Go here:

http://www.youtube.com/watch?v=2aakZoAmHJg

Then go here:

http://dl.getdropbox.com/u/198699/linux_wing/wing-linux-0.3pre1.zip

- d

ohhhh you rock!
Any changes to the display driver, though? I wonder if the white issue is still there...

[darkstar62]

ohhhh you rock!
Any changes to the display driver, though? I wonder if the white issue is still there...

Sadly, I think it probably still is there. You can try the kernel alone if you'd like -- maybe there's something changed.

http://dl.getdropbox.com/u/198699/linux_wing/zImage34

I've put working that issue on hold for now, since I don't have access to a device that does that (and it's really hard to debug problems you're not personally having :)) I think there's probably still a weird initialization happening in one of the chips, but I've taken people through all the settings I can think of, and nothing seems to help, so I'm kindof at a loss for what more to try.

On your device, when you boot, does the screen fade to white like mine does initially, and then just stay there?

- d

[neoobs]

Sadly, I think it probably still is there. You can try the kernel alone if you'd like -- maybe there's something changed.

http://dl.getdropbox.com/u/198699/linux_wing/zImage34

I've put working that issue on hold for now, since I don't have access to a device that does that (and it's really hard to debug problems you're not personally having :)) I think there's probably still a weird initialization happening in one of the chips, but I've taken people through all the settings I can think of, and nothing seems to help, so I'm kindof at a loss for what more to try.

On your device, when you boot, does the screen fade to white like mine does initially, and then just stay there?

- d

Just so you know the build.prop file in the boot.img now has a way to change screen sizes (I think it is screen sizes or DPI)

[ivanmmj]

Sadly, I think it probably still is there. You can try the kernel alone if you'd like -- maybe there's something changed.

http://dl.getdropbox.com/u/198699/linux_wing/zImage34

I've put working that issue on hold for now, since I don't have access to a device that does that (and it's really hard to debug problems you're not personally having :)) I think there's probably still a weird initialization happening in one of the chips, but I've taken people through all the settings I can think of, and nothing seems to help, so I'm kindof at a loss for what more to try.

On your device, when you boot, does the screen fade to white like mine does initially, and then just stay there?

- d

I don't have an SD card set up to try that ATM. I'd have to wait until later on today. On another note:
I have a few optimizations for you to try:

A better dalvik vm (http://forum.xda-developers.com/showpost.php?p=3861699&postcount=26) from the Ion build.
And read about Odex files. (http://forum.xda-developers.com/showthread.php?t=520411) Read the whole thread.

[neoobs]

I don't have an SD card set up to try that ATM. I'd have to wait until later on today. On another note:
I have a few optimizations for you to try:

A better dalvik vm (http://forum.xda-developers.com/showpost.php?p=3861699&postcount=26) from the Ion build.
And read about Odex files. (http://forum.xda-developers.com/showthread.php?t=520411) Read the whole thread.

two very good threads. I have been trying to make dream roms by merging two roms. I have yet to flash my herald but that is my next task this week. Maybe I will see what I can do.

[ivanmmj]

two very good threads. I have been trying to make dream roms by merging two roms. I have yet to flash my herald but that is my next task this week. Maybe I will see what I can do.

The RAM and ROM size will be an issue, but I can try to help as much as I can.
I might not know as much as you about linux but I am starting to learn a lot about android having an android phone myself.

[Fenopy]

On your device, when you boot, does the screen fade to white like mine does initially, and then just stay there?

- d

It fades just like yours, but instead of flashing and having a bunch of rolling text, mine flashes a brighter white (like full brightness) and stops there (the phone also starts making a very high pitched noise).
This is just using Haret loader RAR you uploaded.

[expone]

Unfortunally, when I using the package wing-linux 0.3 pre 1, my phone boots only with GPE.

I use the default default.txt with start-command-last-number 5 - for android.

The boot need a lot of more time. In GPE I enter the both commands:
fixbacklight
startAndroid

Now, I can see the text message "android" on screen. After this, on the console I get for six time the message failed.

Then, I am on the console user login...

Whats happen?

[darkstar62]

Unfortunally, when I using the package wing-linux 0.3 pre 1, my phone boots only with GPE.

I use the default default.txt with start-command-last-number 5 - for android.

The boot need a lot of more time. In GPE I enter the both commands:
fixbacklight
startAndroid

Now, I can see the text message "android" on screen. After this, on the console I get for six time the message failed.

Then, I am on the console user login...

Whats happen?

Yeah, that's my bad. 5 = GPE, 4 = Android, 3 = Text.

You should eventually see the Android startup logo the way you did it though -- just gotta wait a bit.

- d

[expone]

Maybe I have something wrong words.

I had used the default "default.txt" with number 5. Ok, you has write a wrong definition. It's not Android but it is GPE.

That was not the main problem. After starting GPE, I was in the terminal and has try to start Android (command: startAndroid). My phone was leaving GPE mode and had try to boot Android.

During this step, the phone is leaving the graphical mode and enter in to text-mode of "Angström-Linux". Before I get the login mask again, I get the error message "failes." for six times.

I believe the start script is corrupt for this version.

Thats to this try in the past.

------

After your reply I has tried to start Android directly by changing default.txt. I had set the number to "4".

Now, after a lot of text-state-messages, I see the "Angröm" bootscreen. It was overpainted by Android-Starting-Script and the text-message "Android_".

After over 5 minutes on this screen, the phone seems to be switched off. Power on/off button has no effect. Display is off. It was need to press soft-reset button to enable again the power button and to start Windows Mobile.

Is this problem known? And is there an Solution? When I has some time, I will repeat this last step SSH-Connection to see more information, perhaps.

Thanks a lot to your work. Best regards,
expone.

[darkstar62]

Maybe I have something wrong words.

I had used the default "default.txt" with number 5. Ok, you has write a wrong definition. It's not Android but it is GPE.

That was not the main problem. After starting GPE, I was in the terminal and has try to start Android (command: startAndroid). My phone was leaving GPE mode and had try to boot Android.

During this step, the phone is leaving the graphical mode and enter in to text-mode of "Angström-Linux". Before I get the login mask again, I get the error message "failes." for six times.

I believe the start script is corrupt for this version.

Thats to this try in the past.

------

After your reply I has tried to start Android directly by changing default.txt. I had set the number to "4".

Now, after a lot of text-state-messages, I see the "Angröm" bootscreen. It was overpainted by Android-Starting-Script and the text-message "Android_".

After over 5 minutes on this screen, the phone seems to be switched off. Power on/off button has no effect. Display is off. It was need to press soft-reset button to enable again the power button and to start Windows Mobile.

Is this problem known? And is there an Solution? When I has some time, I will repeat this last step SSH-Connection to see more information, perhaps.

Thanks a lot to your work. Best regards,
expone.

Ok, here's some detail about how all this works. The "Failed" messages you're seeing are because the script repeatedly tries to unmount /android/sys, as android's startup will try and mount it (on top of the replacement we added). The "Failed" messages are it saying that it isn't mounted, so they can be safely ignored.

As to the screen shutting off after 5 minutes, yeah, the screen has a 5 minute timeout to go into power saving. You should be able to get it out by hitting any key.

The distribution I sent out has an empty /android/data directory, so Android has to rebuild all the data there on boot. It takes a while (not sure how long, been a while since I did it, but probably a good 5 minutes at least). Rest assured your phone is working and doing everything properly.

When you did the startAndroid from GPE, there's some commands to change the terminal. That change no doubt brought you to a text login. That's OK, Android should be booting in the background.

Moral of the story, you're doing everything right -- just give it some time to start. A first boot of Android without the /data directory can take some time, but after that it should be much quicker.

- d

[expone]

Unfortunatly, after six hours in the night, Android was not booted up. It stay on the text-logo "Android_".

Any Ideas?

[darkstar62]

Unfortunatly, after six hours in the night, Android was not booted up. It stay on the text-logo "Android_".

Any Ideas?

Could be something is crashing...

Try this:

Boot into Linux using runlevel 3 (console mode). Then attach your phone to your computer and log in with SSH. This'll help you observe what's going on.
Post the output of the following commands:

# ls /android
# mount
# cat /bin/start_android
# cat /android/android.sh

Run "start_android" from your SSH session. You should start to see log information go by. My guess is that you'll also start to see Java exceptions or other errors. Let it go for a little while (until you start to see errors, maybe after 3 minutes or so) and copy/paste the data that was put to your console here (from as far back as you can -- might be helpful to adjust your scrollback buffer to be as long as possible).


Good luck, lemme know if any of that is unclear.
- d

[expone]

Ok, I wwill try it in the next hours. Need now to works sth.

Where are you from, darkstar? You reply me around the clock ;)

[neoobs]

OK this is so horrible, but I just noticed that the thread title is a little decieving.

I googled
http://www.google.com/search?q=Andriod+for+Herald
and
http://www.google.com/search?q=Tmobile+Wing

LOL now what? LOL

[Kuuf]

So, it has been I while since I've posted here but I didn't have much time.
Last few days I've been trying to boot the new versions, but still no luck for me, I've still the white/blank screen.

I do have got a working linux from Gizard or something.
I can boot en can even start the interface. But I couldn't mount my partition with android, and so I couldn't try to boot it.

Then I've been playing around with the zImage en default.txt and so, trying to boot the wing zImage34 with the working default. But no luck.

Also, Gizard has (had?) no ssh, so couldn't really do anything.

Atm I have some time so I will keep trying.
Also, I will have an iPhone in August (I'll start working then, and the company gives me one) so I'll probably use my Herald (yes it's a herald, no wing) for Android testing only :-)

Maybe darkstar is something with the fact that I can boot (a) linux ...
(for solving the whitescreen info for some people)

[Saew]

Sometimes Android boots just fine, other times I get the Android_ logo and I go back to my terminal.
Below I've posted the logs of what happens when android fails to boot.

root@htcherald:~$ ls /android
android.sh etc sdcard
bin init sqlite_stmt_journals
cache init.goldfish.rc sys
data init.rc sys_dev
default.prop proc system
dev sbin

root@htcherald:~$ mount
rootfs on / type rootfs (rw)
/dev/root on / type ext3 (rw,errors=continue,data=ordered)
proc on /proc type proc (rw)
sysfs on /sys type sysfs (rw)
/dev/root on /dev/.static/dev type ext3 (rw,errors=continue,data=ordered)
tmpfs on /dev type tmpfs (rw,size=2048k,mode=755)
/dev/mmcblk0p1 on /media/mmcblk0p1 type vfat (rw,sync,fmask=0022,dmask=0022,codepage=cp437,ioch arset=iso8859-1)
/dev/mmcblk0p3 on /media/mmcblk0p3 type ext3 (rw,errors=continue,data=ordered)
devpts on /dev/pts type devpts (rw,gid=5,mode=620)
usbfs on /proc/bus/usb type usbfs (rw)
tmpfs on /var/volatile type tmpfs (rw)
tmpfs on /dev/shm type tmpfs (rw,mode=777)
tmpfs on /media/ram type tmpfs (rw)

root@htcherald:~$ cat /bin/start_android
#!/bin/sh

#if grep -q /android/dev /proc/mounts; then
# true
#else
# mount --bind /dev /android/dev
#fi

#if grep -q /android/proc /proc/mounts; then
# true
#else
# mount --bind /proc /android/proc
#fi

if grep -q /android/sys_dev /proc/mounts; then
true
else
mount --bind /sys /android/sys_dev
fi

chvt 3
chroot /android /android.sh &
chroot /android /system/bin/logcat
kill_android
chvt 1

root@htcherald:~$ cat /android/android.sh
#!/system/bin/sh

export LD_LIBRARY_PATH=/system/lib
export ANDROID_BOOTLOGO=1
export ANDROID_ROOT=/system
export ANDROID_ASSETS=/system/app
export ANDROID_DATA=/data
export EXTERNAL_STORAGE=/sdcard
export DRM_CONTENT=/data/drm/content

export TSLIB_CONSOLEDEVICE=none
export TSLIB_FBDEVICE=/dev/fb0
export TSLIB_TSDEVICE=/dev/input/event1
export TSLIB_CALIBFILE=/etc/pointercal
export TSLIB_COINFFILE=/etc/ts.conf
export TSLIB_PLUGINDIR=/usr/lib/ts
export LD_PRELOAD=/usr/lib/libts-1.0.so.0:/usr/lib/ts/pthres.so

/init &
/system/bin/sleep 2

/system/bin/umount /sys
/system/bin/umount /sys
/system/bin/umount /sys
/system/bin/umount /sys
/system/bin/umount /sys
/system/bin/umount /sys
/system/bin/umount /sys

#/system/bin/app_process -Xzygote /system/bin --zygote &
#/system/bin/dbus-daemon --system &
#runtime

And this is what I get when trying to run android:
root@htcherald:~$ start_android
Unable to open log device '/dev/log/main': No such file or directory
killall: logcat: no process killed
[1] Terminated /init
killall: vold: no process killed
failed.
failed.
failed.
failed.
failed.
killall: servicemanager: no process killed
failed.
killall: app_process: no process killed
killall: system_server: no process killed
killall: installd: no process killed
killall: mountd: no process killed
killall: mediaserver: no process killed
killall: rild: no process killed

[neoobs]

Just out of curiosity does adb work?

[expone]

OK, there are the wished information.

File: output__ls_mount_cat_cat.txt
----
Output of the posted commands.


File: bin,start_android.txt
----
Copy of /bin/start_android


File: android,android.sh.txt
----
Copy of /andrid/android.sh


File: output__start_android.txt
----
Output of command "start_android". During this command, I get console putput in a loop. Same messages has repeated.


Can you work with this information?

[expone]

adb?

PS: I think I have the same result as Saew....

[neoobs]

adb?

PS: I think I have the same result as Saew....

I have a funny feeling only darkstar can answer that.

ADB is to connect to Android for developers. It lets you see the android log on your computer in real time and would help figure out the problems.

I am actually going to flash my wing to android (if you consider it flashing) today/tomorrow and try to help all of you out since I am pretty fluent in android for the G1.

[Kuuf]

I am actually going to flash my wing to android (if you consider it flashing) today/tomorrow and try to help all of you out since I am pretty fluent in android for the G1.
Nice neoobs! :-)

[Kuuf]

So, I've been able to boot GPE too now.
Using linwizard first and by formatting the gpe/android partition as ext2, apparently, linwizard doesn't support ext3. Pitty.

But when I run startAndroid, I first get "segmentation fault /init", and than also 6 times "failed". A few seconds later I got another error, regarding usb0 and than it stops. Nothing more happens (and yes, I waited a while).

I guess I should first try to fix the segmentation fault.
Any idea darkstar? Maybe android needs ext3 or something.

[darkstar62]

So, I've been able to boot GPE too now.
Using linwizard first and by formatting the gpe/android partition as ext2, apparently, linwizard doesn't support ext3. Pitty.

But when I run startAndroid, I first get "segmentation fault /init", and than also 6 times "failed". A few seconds later I got another error, regarding usb0 and than it stops. Nothing more happens (and yes, I waited a while).

I guess I should first try to fix the segmentation fault.
Any idea darkstar? Maybe android needs ext3 or something.

Which kernel are you using? If it's one of the linwizard kernels, I think theirs doesn't have the Android patches. The "failed" messages are OK -- that's it trying to make sure the /android/sys filesystem stays emulated and doesn't actually get mounted as a real /sys filesystem (needed until we get proper power management).

- d

[darkstar62]

So, it has been I while since I've posted here but I didn't have much time.
Last few days I've been trying to boot the new versions, but still no luck for me, I've still the white/blank screen.

I do have got a working linux from Gizard or something.
I can boot en can even start the interface. But I couldn't mount my partition with android, and so I couldn't try to boot it.

Then I've been playing around with the zImage en default.txt and so, trying to boot the wing zImage34 with the working default. But no luck.

Also, Gizard has (had?) no ssh, so couldn't really do anything.

Atm I have some time so I will keep trying.
Also, I will have an iPhone in August (I'll start working then, and the company gives me one) so I'll probably use my Herald (yes it's a herald, no wing) for Android testing only :-)

Maybe darkstar is something with the fact that I can boot (a) linux ...
(for solving the whitescreen info for some people)

That's interesting...Where did you get the kernel for that? Maybe everyone having white screen problems should try that...If it fixes it, there's no doubt something in that kernel that ours doesn't have that could fix it.

Sometimes Android boots just fine, other times I get the Android_ logo and I go back to my terminal.
Below I've posted the logs of what happens when android fails to boot.

<snip>

And this is what I get when trying to run android:
root@htcherald:~$ start_android
Unable to open log device '/dev/log/main': No such file or directory
killall: logcat: no process killed
[1] Terminated /init
killall: vold: no process killed
failed.
failed.
failed.
failed.
failed.
killall: servicemanager: no process killed
failed.
killall: app_process: no process killed
killall: system_server: no process killed
killall: installd: no process killed
killall: mountd: no process killed
killall: mediaserver: no process killed
killall: rild: no process killed

OK, that looks like the contents of /android/dev are wrong -- there may be a problem with the image I posted. I'll go back and check.

Just out of curiosity does adb work?

In theory, yes, but the kernel would have to be rebuilt with USB support set to Android Debug (currently it is an ethernet gadget). I just use SSH + logcat to see log messages (specifically, chroot /android /system/bin/logcat).

OK, there are the wished information.

File: output__ls_mount_cat_cat.txt
----
Output of the posted commands.


File: bin,start_android.txt
----
Copy of /bin/start_android


File: android,android.sh.txt
----
Copy of /andrid/android.sh


File: output__start_android.txt
----
Output of command "start_android". During this command, I get console putput in a loop. Same messages has repeated.


Can you work with this information?

Yeah...Looks like your /android/data directory might not have good permissions.

Try these commands:


# chown -R root:root /android
# chmod 755 `find /android -type d`
# chmod 644 `find /android -type f`


If that doesn't work, post the output of the following command:


# ls -l /android/dev


- d

[Kuuf]

Which kernel are you using? If it's one of the linwizard kernels, I think theirs doesn't have the Android patches. The "failed" messages are OK -- that's it trying to make sure the /android/sys filesystem stays emulated and doesn't actually get mounted as a real /sys filesystem (needed until we get proper power management).

- d

You're right, it's a bad kernel.
I've found a kernel able to boot android now, one bad thing, it boots the android of the given android-initrd in default.txt

I'm playing around now to be able to boot your android fs.
I'll keep you posted

[expone]

It doesn't work. I will try to set up completly new by using your installation tutorial on wing-linux 0.3 pre1-package.

It is wrong to set persissions to 777 on / recursivly?
(Naturally, on a productive system, this is a security problem. )

[darkstar62]

It doesn't work. I will try to set up completly new by using your installation tutorial on wing-linux 0.3 pre1-package.

It is wrong to set persissions to 777 on / recursivly?
(Naturally, on a productive system, this is a security problem. )

Yeah, that's dangerous. Things *might* work, but I'd expect it to be even more broken with that. Some programs won't operate if they see permissions like that.

- d

[ivanmmj]

This is where he probably got gizzard from:


http://forum.xda-developers.com/showpost.php?p=2508370&postcount=5

[darkstar62]

This is where he probably got gizzard from:


http://forum.xda-developers.com/showpost.php?p=2508370&postcount=5

The link in that forum seems to be old. Here's a recent one:

<link removed -- It's not the kernel, looking for it>

Can everyone who's having white screen problems go and try the linwizard kernel above? You'll need to use their default.txt to boot it. Don't worry about trying to get into the system itself -- we just need to see if the screen is readable when it comes up.

- d

[darkstar62]

The link in that forum seems to be old. Here's a recent one:

<link removed -- It's not the kernel, looking for it>

Can everyone who's having white screen problems go and try the linwizard kernel above? You'll need to use their default.txt to boot it. Don't worry about trying to get into the system itself -- we just need to see if the screen is readable when it comes up.

- d

Kuff, can you post a link to the kernel you're working with? I'm having trouble finding it.

Thanks
- d

[Kuuf]

http://forum.xda-developers.com/showpost.php?p=2156270&postcount=28

[darkstar62]

http://forum.xda-developers.com/showpost.php?p=2156270&postcount=28

Sweet, thanks.

I've got a new kernel up to try too:

http://dl.getdropbox.com/u/198699/linux_wing/zImage35

I noticed earlier linwizard kernels didn't have some initialization code for the framebuffer that initially turns it off...I tested removing that code from our kernel, and I get the early framebuffer messages much longer, but then the main framebuffer kicks in immediately -- no white screen period.

So, give this one a try. If it doesn't work, you might try Kuuf's kernel (use MTYPE 1229 for that one in your default.txt, otherwise it definitely won't boot).

Good luck, and lemme know if it works.

- d

[Fenopy]

Sweet, thanks.

I've got a new kernel up to try too:

http://dl.getdropbox.com/u/198699/linux_wing/zImage35

I noticed earlier linwizard kernels didn't have some initialization code for the framebuffer that initially turns it off...I tested removing that code from our kernel, and I get the early framebuffer messages much longer, but then the main framebuffer kicks in immediately -- no white screen period.

So, give this one a try. If it doesn't work, you might try Kuuf's kernel (use MTYPE 1229 for that one in your default.txt, otherwise it definitely won't boot).

Good luck, and lemme know if it works.

- d
Here is zImage34 & zImage35 w/Log Files
http://rapidshare.com/files/239779890/zImage.rar.html

http://forum.xda-developers.com/showpost.php?p=2156270&postcount=28
Can everyone who's having white screen problems go and try the linwizard kernel above? You'll need to use their default.txt to boot it. Don't worry about trying to get into the system itself -- we just need to see if the screen is readable when it comes up.

- d
Here is w/Kuuf's Image (Which seems like it was working?!?!)
http://rapidshare.com/files/239782449/KuufImage.rar.html
-OR-
http://www.megaupload.com/?d=86GU6BLO

Kuuf Image Log:
HaRET(5)# bootlinux
boot KERNEL=Image INITRD=
Opening file Image
boot params: RAMADDR=10000000 RAMSIZE=04000000 MTYPE=1229 CMDLINE='debug quiet psplash=false loglevel=7 root=/dev/mmcblk0p3 init=/sbin/init console=tty0 video=omapfb:accel 5'
Boot FB feedback: 1
Built virtual to physical page mapping
Allocated 616 pages (tags=50B00000/10f79000 kernel=50B01000/10f7a000 initrd=50D64000/111dd000 index=50D64000/111dd000)
Built kernel tags area
Built page index
Video buffer at 48900020 sx=240 sy=320 mx=60 my=53
Video Phys FB=20001020 Fonts=111df064
preload=2264@50D67000/111e0000 sj=50D67000 stack=50D65000/111de000 data=50D66000/111df000 exec=111e0128
Reading 2498840 bytes...
Read complete
Launching to physical address 111e0010
Trampoline setup (tram=136@000241C0/080241c0/105651c0)
MMU setup: mmu=AC3A0000/103a0000
Go Go Go...

[darkstar62]

Here is zImage34 & zImage35 w/Log Files
http://rapidshare.com/files/239779890/zImage.rar.html



Here is w/Kuuf's Image (Which seems like it was working?!?!)
http://rapidshare.com/files/239782449/KuufImage.rar.html
-OR-
http://www.megaupload.com/?d=86GU6BLO

Kuuf Image Log:
HaRET(5)# bootlinux
boot KERNEL=Image INITRD=
Opening file Image
boot params: RAMADDR=10000000 RAMSIZE=04000000 MTYPE=1229 CMDLINE='debug quiet psplash=false loglevel=7 root=/dev/mmcblk0p3 init=/sbin/init console=tty0 video=omapfb:accel 5'
Boot FB feedback: 1
Built virtual to physical page mapping
Allocated 616 pages (tags=50B00000/10f79000 kernel=50B01000/10f7a000 initrd=50D64000/111dd000 index=50D64000/111dd000)
Built kernel tags area
Built page index
Video buffer at 48900020 sx=240 sy=320 mx=60 my=53
Video Phys FB=20001020 Fonts=111df064
preload=2264@50D67000/111e0000 sj=50D67000 stack=50D65000/111de000 data=50D66000/111df000 exec=111e0128
Reading 2498840 bytes...
Read complete
Launching to physical address 111e0010
Trampoline setup (tram=136@000241C0/080241c0/105651c0)
MMU setup: mmu=AC3A0000/103a0000
Go Go Go...


Awesome post, Fenopy! Those videos are really helpful -- it looks like the problem lies squarely in the framebuffer initialization code -- the last line seen is right before FB init.

Very interesting that Kuus's kernel works with your phone. I looked at it, and it was built circa April 23rd 2008. Looking through the Linwizard commit history, that is right around the time some changes were made in the frame buffer code to do de-init and re-init at startup. That kernel appears to be before that code was introduced.

Give this kernel a shot:
http://dl.getdropbox.com/u/198699/linux_wing/zImage36

I played a bit with the init code and modified some of the configuration flags. If you could take another video with it, that would be awesome too. :)

- d

[Fenopy]

Awesome post, Fenopy! Those videos are really helpful -- it looks like the problem lies squarely in the framebuffer initialization code -- the last line seen is right before FB init.

Very interesting that Kuus's kernel works with your phone. I looked at it, and it was built circa April 23rd 2008. Looking through the Linwizard commit history, that is right around the time some changes were made in the frame buffer code to do de-init and re-init at startup. That kernel appears to be before that code was introduced.

Give this kernel a shot:
http://dl.getdropbox.com/u/198699/linux_wing/zImage36

I played a bit with the init code and modified some of the configuration flags. If you could take another video with it, that would be awesome too. :)

- d
We still get a white screen... :'(

http://rapidshare.com/files/239817861/VidzImage36.rar.html

Uploading Video Now... Damn you slow UL...

HaRET(5)# bootlinux
boot KERNEL=zImage36 INITRD=
Opening file zImage36
boot params: RAMADDR=10000000 RAMSIZE=04000000 MTYPE=1232 CMDLINE='debug quiet psplash=false loglevel=7 root=/dev/mmcblk0p3 init=/sbin/init console=tty0 video=omapfb:accel 5'
Boot FB feedback: 1
Built virtual to physical page mapping
Allocated 415 pages (tags=51800000/11cba000 kernel=51801000/11ccb000 initrd=5199B000/11b1f000 index=5199B000/11b1f000)
Built kernel tags area
Built page index
Video buffer at 48900020 sx=240 sy=320 mx=60 my=53
Video Phys FB=20001020 Fonts=11b1d064
preload=2264@5199E000/11b1c000 sj=5199E000 stack=5199C000/11b1e000 data=5199D000/11b1d000 exec=11b1c128
Reading 1675280 bytes...
Read complete
Launching to physical address 11b1c010
Trampoline setup (tram=136@000241C0/1a0241c0/107a91c0)
MMU setup: mmu=AC3A0000/103a0000
Go Go Go...

[darkstar62]

We still get a white screen... :'(

http://rapidshare.com/files/239817861/VidzImage36.rar.html

Uploading Video Now... Damn you slow UL...

HaRET(5)# bootlinux
boot KERNEL=zImage36 INITRD=
Opening file zImage36
boot params: RAMADDR=10000000 RAMSIZE=04000000 MTYPE=1232 CMDLINE='debug quiet psplash=false loglevel=7 root=/dev/mmcblk0p3 init=/sbin/init console=tty0 video=omapfb:accel 5'
Boot FB feedback: 1
Built virtual to physical page mapping
Allocated 415 pages (tags=51800000/11cba000 kernel=51801000/11ccb000 initrd=5199B000/11b1f000 index=5199B000/11b1f000)
Built kernel tags area
Built page index
Video buffer at 48900020 sx=240 sy=320 mx=60 my=53
Video Phys FB=20001020 Fonts=11b1d064
preload=2264@5199E000/11b1c000 sj=5199E000 stack=5199C000/11b1e000 data=5199D000/11b1d000 exec=11b1c128
Reading 1675280 bytes...
Read complete
Launching to physical address 11b1c010
Trampoline setup (tram=136@000241C0/1a0241c0/107a91c0)
MMU setup: mmu=AC3A0000/103a0000
Go Go Go...


OK...Try this:

http://dl.getdropbox.com/u/198699/linux_wing/zImage37

This one has the de-init code completely disabled, which is what I think Kuuf's had. Should that not work, try this one:

http://dl.getdropbox.com/u/198699/linux_wing/zImage38

This one has the de-init code enabled, but some printk() calls to dump out the contents of a crucial register. I want to see how it compares with what mine gives. You'll more than likely need to SSH into your phone and capture the output of the 'dmesg' command to get that. If you can redirect the output to a file and send me that file, that'd be great:

On the phone:


# dmesg > /tmp/dmesg.txt


Then on your computer:


# scp root@10.100.0.1:/tmp/dmesg.txt .


(Sorry if you already know how to do this.) Don't worry about taking a video this time, I think we're about as far with that as we can get. Huge help that, by the way.

- d

[Fenopy]

OK...Try this:

http://dl.getdropbox.com/u/198699/linux_wing/zImage37

This one has the de-init code completely disabled, which is what I think Kuuf's had. Should that not work, try this one:

http://dl.getdropbox.com/u/198699/linux_wing/zImage38

This one has the de-init code enabled, but some printk() calls to dump out the contents of a crucial register. I want to see how it compares with what mine gives. You'll more than likely need to SSH into your phone and capture the output of the 'dmesg' command to get that. If you can redirect the output to a file and send me that file, that'd be great:

On the phone:


# dmesg > /tmp/dmesg.txt


Then on your computer:


# scp root@10.100.0.1:/tmp/dmesg.txt .


(Sorry if you already know how to do this.) Don't worry about taking a video this time, I think we're about as far with that as we can get. Huge help that, by the way.

- d

Linux hates my wireless card... So I am loading a virtual machine w/Ubuntu 9 right now.... Waiting for it to download...

[Kernel Jag]

I've toiled with kernel programming and have coded on UNIX internals (took a course in uni), I've two hands and soon I'll have lots of spare time!! Only prob, I've a Herald that I use as my main phone :(

Would it possible for us to get hold of an OMAP850 emulator, maybe create one using QEMU? Would certainly speed up our dev..

[Kuuf]

I've toiled with kernel programming and have coded on UNIX internals (took a course in uni), I've two hands and soon I'll have lots of spare time!! Only prob, I've a Herald that I use as my main phone :(

Would it possible for us to get hold of an OMAP850 emulator, maybe create one using QEMU? Would certainly speed up our dev..

Ow that's nice!
Never seen such emulator though, my Herald is atm alwo my main phone.

[Kuuf]

OK...Try this:

http://dl.getdropbox.com/u/198699/linux_wing/zImage37

This one has the de-init code completely disabled, which is what I think Kuuf's had. Should that not work, try this one:

http://dl.getdropbox.com/u/198699/linux_wing/zImage38


No luck with both of them.
But it seems to take longer before the blank screen comes.
I see whole lot of outputs on the screen. And if I'm not mistaking, the last thing I saw before the blank screen was "into configuration" or something (with zImage38) and something like "omap done" on zImae37.

So, I couldn't give you any dmesg info because I cant boot into either modes.

[darkstar62]

I've toiled with kernel programming and have coded on UNIX internals (took a course in uni), I've two hands and soon I'll have lots of spare time!! Only prob, I've a Herald that I use as my main phone :(

Would it possible for us to get hold of an OMAP850 emulator, maybe create one using QEMU? Would certainly speed up our dev..

Yeah, my phone is my main one too. I keep a spare one handy so I can swap out the sim card if I'm expecting a call.

The qemu emulator is about as good as I'm aware of. It can emulate the same ARM instruction set that our phones use. Unfortunately though, we couldn't use it for kernel development, as it supplies a very different hardware configuration as our phones. Most of the problems we're encountering now deal with the hardware (differences in configurations and a general lack of knowledge about the specs of the phone).

That being said, we could use it for general Linux and Android development though, as there's nothing fancy about the way those binaries are compiled.

If you're interested in hacking on some code, lemme know -- I can add you as a developer to the project. You might take a look at the active tickets on http://wing-linux.sf.net to see what needs to be done.

No luck with both of them.
But it seems to take longer before the blank screen comes.
I see whole lot of outputs on the screen. And if I'm not mistaking, the last thing I saw before the blank screen was "into configuration" or something (with zImage38) and something like "omap done" on zImae37.

So, I couldn't give you any dmesg info because I cant boot into either modes.

Ok, that sounds a lot like what Fenopy was seeing. I think at this point it's safe to say that the problem lies with framebuffer initialization. It seems like something in your kernel is our winning ticket, though, since it works for at least two people with whitescreen issues. I'll need to dig into the code for that more to try and figure out what changed between theat one and ours. Maybe I'll try and build a kernel from those sources so that we can make sure they produce working results. Just gotta figure out how git works...

The only real way you'd be able to get dmesg output would be to go in using USB with SSH. Fenopy was reporting that his phone doesn't allow him to log in though, so I suspect the kernel is crashing somewhere later in the runtime (possibly even at framebuffer init). If you've set your runlevel to 3 (the last number at the end of your CMDLINE), you can try blindly logging in by entering the username and password ("root" and "wing"), and typing "reboot". If after a while your phone reboots, you should be able to use SSH.

- d

[Fenopy]

If you've set your runlevel to 3 (the last number at the end of your CMDLINE), you can try blindly logging in by entering the username and password ("root" and "wing"), and typing "reboot". If after a while your phone reboots, you should be able to use SSH.

- d

I couldnt get it to reboot under lvl3 either... :'(

[darkstar62]

Slightly off topic...Would you all find it useful if I started an IRC channel for this development (#wing-linux, perhaps)? Just thinking that interactive communication can be really good for development.

- d

[Kuuf]

I couldnt get it to reboot under lvl3 either... :'(

Same problem here

[Kuuf]

Slightly off topic...Would you all find it useful if I started an IRC channel for this development (#wing-linux, perhaps)? Just thinking that interactive communication can be really good for development.

- d

Freenode?

Have to say, I'm from Belgium -> its almost five in the afternoon here.
Finding good moments might be difficult

[darkstar62]

Freenode?

Have to say, I'm from Belgium -> its almost five in the afternoon here.
Finding good moments might be difficult

I was thinking freenode. It's 8 in the morning here (Seattle), so at least there's some overlap it seems. It would of course be open all the time, and we could join in or not as we feel like it. Just wondering if that would be useful to everyone.

- d

[darkstar62]

I couldnt get it to reboot under lvl3 either... :'(

Same problem here

Alright, I'll keep poking.

Any git experts out there?

- d

[neoobs]

Alright, I'll keep poking.

Any git experts out there?

- d

Whatcha need git for? Android source?

[Kuuf]

I was thinking freenode. It's 8 in the morning here (Seattle), so at least there's some overlap it seems. It would of course be open all the time, and we could join in or not as we feel like it. Just wondering if that would be useful to everyone.

- d
I quickly registered wing-linux at freenode. Join and I'll make you founder, as you are a bit of the leader of the project


Any git experts out there?

- d
I've experience with svn, but not with git.

[darkstar62]

I quickly registered wing-linux at freenode. Join and I'll make you founder, as you are a bit of the leader of the project


I've experience with svn, but not with git.

Sweet, #wing-linux is live! Thanks Kuuf. Come join us!

[ivanmmj]

Btw, I just wanted to say, that Android DOES boot on my phone with the 35 kernel. The screen isn't aligned and won't let me do anything and pressing any key resets the interface, but it boots. :p But, it boots straight to GPE FIRST. Then I have to launch android from there, instead. (And it looks like it's not working at first for a while then finally it starts loading Android.)
I've got screenshots, if you want them.

[Kernel Jag]

i've a significant amount of experience with git. what do you need??

[Kernel Jag]

Yeah, my phone is my main one too. I keep a spare one handy so I can swap out the sim card if I'm expecting a call.

The qemu emulator is about as good as I'm aware of. It can emulate the same ARM instruction set that our phones use. Unfortunately though, we couldn't use it for kernel development, as it supplies a very different hardware configuration as our phones. Most of the problems we're encountering now deal with the hardware (differences in configurations and a general lack of knowledge about the specs of the phone).

That being said, we could use it for general Linux and Android development though, as there's nothing fancy about the way those binaries are compiled.

If you're interested in hacking on some code, lemme know -- I can add you as a developer to the project. You might take a look at the active tickets on http://wing-linux.sf.net to see what needs to be done.



Ok, that sounds a lot like what Fenopy was seeing. I think at this point it's safe to say that the problem lies with framebuffer initialization. It seems like something in your kernel is our winning ticket, though, since it works for at least two people with whitescreen issues. I'll need to dig into the code for that more to try and figure out what changed between theat one and ours. Maybe I'll try and build a kernel from those sources so that we can make sure they produce working results. Just gotta figure out how git works...

The only real way you'd be able to get dmesg output would be to go in using USB with SSH. Fenopy was reporting that his phone doesn't allow him to log in though, so I suspect the kernel is crashing somewhere later in the runtime (possibly even at framebuffer init). If you've set your runlevel to 3 (the last number at the end of your CMDLINE), you can try blindly logging in by entering the username and password ("root" and "wing"), and typing "reboot". If after a while your phone reboots, you should be able to use SSH.

- d

I'd love to hack something useful for the project, but I'll need time to aquaint myself with chain compiling for our device, and generally tinkering with Android code. That being said, I'll continue searching for a emulation solution and keep you guys in the loop. And lastly, thanks for pushing the progress this far darkstar!

Really and truly appreciate it...hats off to you, and everybody who's contributed to this thread :)

[darkstar62]

I'd love to hack something useful for the project, but I'll need time to aquaint myself with chain compiling for our device, and generally tinkering with Android code. That being said, I'll continue searching for a emulation solution and keep you guys in the loop. And lastly, thanks for pushing the progress this far darkstar!

Really and truly appreciate it...hats off to you, and everybody who's contributed to this thread :)

No prob, it's been fun :)

I'm trying to set up the source repository better so that we can just do an svn co of the build root, run make, and it'll handle downloading openembedded, the kernel, and android and building them together. Got some work still to do on that though. This is all part of my push to get this stuff into svn (and off my harddrive!). Hopefully once that's done, building everything will be easy.

As for git...I'm trying to pull out a specific revision from a remote branch, and I can't even figure out how to switch to the branch, let alone get the revision out. Can you help?

- d

[darkstar62]

Btw, I just wanted to say, that Android DOES boot on my phone with the 35 kernel. The screen isn't aligned and won't let me do anything and pressing any key resets the interface, but it boots. :p But, it boots straight to GPE FIRST. Then I have to launch android from there, instead. (And it looks like it's not working at first for a while then finally it starts loading Android.)
I've got screenshots, if you want them.

Took me a sec to realize that your phone wasn't working before. That's stupendous!

The fact that it's shifted is something I saw in other threads. Could be we need to adjust the mode timings for your screen. Can't recall, did you send me mode timing information when I asked for it a while back? (I'm gonna look too, it'd be in the ticket if you did). Could be the other video mode I programmed in is better suited to your phone.

EDIT: Found them, they're the second set of timings I programmed in. Lemme try and rebuild zImage35 with the other timing set.

- d

[darkstar62]

Took me a sec to realize that your phone wasn't working before. That's stupendous!

The fact that it's shifted is something I saw in other threads. Could be we need to adjust the mode timings for your screen. Can't recall, did you send me mode timing information when I asked for it a while back? (I'm gonna look too, it'd be in the ticket if you did). Could be the other video mode I programmed in is better suited to your phone.

EDIT: Found them, they're the second set of timings I programmed in. Lemme try and rebuild zImage35 with the other timing set.

- d

Everyone try this one out:

http://dl.getdropbox.com/u/198699/linux_wing/zImage40

There's a bunch of new stuff in this one. The disabling code at init can now be toggled on and off with a command-line argument. Add the following to your set CMDLINE in default.txt:

heraldlcd=screen:0,noinitdisable

This selects screen configuration 0 (the one I've been using for all the kernels), and noinitdisable disables the screen disable code at startup. This is the code that was added in later kernels to try and fix white screen problems (and was the cause of ivanmmj's white-screen).

You can use screen:1 to change to the second configuration (ivanmmj and Fenopy, you'll want this one, it should hopefully fix the screen offset problem you had; I only include you in this, Fenopy, because you had the same timings. Hopefully you can find a configuration that will boot.)

If you omit all options, the default is to use screen 0 and to enable the newer screen disabling code.

Lemme know how it works, and if you manage to find a configuration that works.

- d

[ivanmmj]

Everyone try this one out:

http://dl.getdropbox.com/u/198699/linux_wing/zImage40

There's a bunch of new stuff in this one. The disabling code at init can now be toggled on and off with a command-line argument. Add the following to your set CMDLINE in default.txt:

heraldlcd=screen:0,noinitdisable

This selects screen configuration 0 (the one I've been using for all the kernels), and noinitdisable disables the screen disable code at startup. This is the code that was added in later kernels to try and fix white screen problems (and was the cause of ivanmmj's white-screen).

You can use screen:1 to change to the second configuration (ivanmmj and Fenopy, you'll want this one, it should hopefully fix the screen offset problem you had; I only include you in this, Fenopy, because you had the same timings. Hopefully you can find a configuration that will boot.)

If you omit all options, the default is to use screen 0 and to enable the newer screen disabling code.

Lemme know how it works, and if you manage to find a configuration that works.

- d

I tried this kernel and added: heraldlcd=screen:1,noinitdisable
Boots, but I still have to load Android from GPE. Also, the touchscreen is still not registering my touch correctly and the keys crash the launcher.apk (that's what it looks like, anyways...)

[darkstar62]

I tried this kernel and added: heraldlcd=screen:1,noinitdisable
Boots, but I still have to load Android from GPE. Also, the touchscreen is still not registering my touch correctly and the keys crash the launcher.apk (that's what it looks like, anyways...)

Yeah, that won't change for the kernel. Are you using the 0.3-pre rootfs image?

How was the screen alignment issue this time around?

- d

[ivanmmj]

Yeah, that won't change for the kernel. Are you using the 0.3-pre rootfs image?

How was the screen alignment issue this time around?

- d

Yes. (I believe so, I can't check it since I don't have my laptop in front of me. But I believe that's what I downloaded.)
The screen seemed aligned just fine on both kernels.

[darkstar62]

Yes. (I believe so, I can't check it since I don't have my laptop in front of me. But I believe that's what I downloaded.)
The screen seemed aligned just fine on both kernels.

Excellent! We're making progress. Maybe we can close this whitescreen issue once and for all for the 0.3 release.

- d

[ivanmmj]

Excellent! We're making progress. Maybe we can close this whitescreen issue once and for all for the 0.3 release.

- d

I'm about to make those changed we talked about.

Let's see:
*walks away from computer*
*edits the files in laptop*
*puts laptop away*
*inserts SD card into phone*
*watches the android bootup screen*
Touch screen works!
But... after a minute, it crashed... It may have tried going into the saver mode or whatever the screen timeout is called.

[darkstar62]

Alright. Everyone, try this:

http://dl.getdropbox.com/u/198699/linux_wing/zImage42

A bunch of us on IRC have been working with this kernel since last night, and it seems to fix all white screen problems. There's some kernel command-line options you should be aware of:


heraldlcd=screen:[0|1]{,noinitdisable}


Basically, there's two options to this. The screen: option takes either a 0 or 1, and allows you to switch video timings. (0 is what I use, others need 1). the optional 'noinitdisable' switch turns off some initialization code that I suspect is causing problems for some. If you can't get in without the switch, try adding it.

This all goes at the end of your CMDLINE in default.txt. An example might look like:


set CMDLINE = "... heraldlcd=screen:0,noinitdisable ..."


(other stuff left out)

Give it a shot, lemme know what configuration works, or if none do.

Fenopy, you'll want to use screen:1. It matches the timings you sent me a while back.

Enjoy
- d

[darkstar62]

All,

I've put out a second pre-release of 0.3 for your testing pleasure:

http://dl.getdropbox.com/u/198699/linux_wing/wing-linux-0.3pre2.zip

This includes the new zImage42 kernel that quite possibly fixes all white screen problems (just know of one phone that hasn't been tested. All others report success!) There's also keyboard fixes -- the cursor and direction pad buttons no longer crash, but actually work as expected. The dpad center button is another "Enter" key.

Android has been updated for the keyboard too, although many of the keys are mismapped (many produce symbols instead of letters). The back button is mapped as the left bar key, and menu is the right bar key.

Make sure you read the UPGRADING and INSTALLING files -- there's some changes in there you need to be aware of.

Happy testing!
- d

[fdez.romero]

Hello all,

I'm new to this topic and I've been watching your success trying to run Android. I'm the happy owner of a Spanish HTC P4350 (not Wing) unlocked from factory (if this makes a difference). I don't know if my P4350 is HardSPL'ed or CID unlocked, all I know is that is SIM unlocked.

I've tried all the zImages posted, but only had little success with the last zImage42. I suffered the white screen issue as well, but it seems to be solved with the last 0.3pre2 version. The bad thing is that even though I select boot option 5 (Android) in default.txt, my Herald always enters the GPE GUI and it doesn't continue booting Android as I've seen in Darkstar62's video. I deleted all the files from both the vfat and ext3 partitions, extracted the new rootfs.tar.bz2 and copied the new Windows files. ¿Is there anything that I'm missing?, ¿is there any way to boot Android from the GPE GUI?.

I would like to contribute to this awesome project, at least in the testing part. Here are some more details about my device:

Model (in the battery): HERA160
Model (in device information): HERA100 (??)
Processor: OMAP850-201MHz
Memory: 43.90 MB left
SO CE 5.2.1238 (Windows Mobile 6 Professional, original from HTC Club)

ROM version: 4.17.412.2 ESN
ROM date: 06/20/07
Radio version: 02.94.90
Protocol version: 4.1.13.44
ExtRom version: 4.17.412.102


Hope this information helps. I'm willing to test anything you might need, send logs... whatever.

Keep the good work guys ;)

[Kuuf]

¿is there any way to boot Android from the GPE GUI?.


Open a terminal, type "startAndroid" and hit return.
If that doesn't work try "start_android".

For quick questions, you can always join our channel on IRC.
(server: freenode, chat: #wing-linux)
Atm I'm there.

[fdez.romero]

Thanks to Kuuf, I was able to boot directly to Android (5 was actually GPE, so I changed it to 4). But I still have some problems with the screen:


screen:0 -> The image is still, but shifted to the right (by 20 pixels or so) and color depth seems to be 256 colors.
screen:1 -> The image "vibrates", but is correctly aligned. Color depth is OK.


This is the "dispdump.txt" log:
HaRET(2)# pdump 0xfffec000 0x20

fffec000 | f8000089 09010cef 0478053f ff30000f | ........?.x...0.

fffec010 | ffffffd2 5c00f000 fffffc00 fffffd3f | .......\....?...

HaRET(3)# pdump 0xfffee300 255

fffee300 | 00000000 00000000 00000000 00000000 | ................

fffee310 | 00000000 00000000 00000000 00000000 | ................

fffee320 | 00000000 00000000 00000000 00000000 | ................

fffee330 | 00000000 00000000 00000000 00000000 | ................

fffee340 | 00000000 00000000 00000000 00000000 | ................

fffee350 | 00000000 00000000 00000000 00000000 | ................

fffee360 | 00000000 00000000 00000000 00000000 | ................

fffee370 | 00000000 00000000 00000000 00000000 | ................

fffee380 | 00000000 00000000 00000000 00000000 | ................

fffee390 | 00000000 00000000 00000000 00000000 | ................

fffee3a0 | 00000000 00000000 00000000 00000000 | ................

fffee3b0 | 00000000 00000000 00000000 00000000 | ................

fffee3c0 | 00000000 00000040 00001000 0000681e | ....@........h..

fffee3d0 | 00000000 00000000 00000000 00000000 | ................

fffee3e0 | 00000000 00000000 00000000 00000000 | ................

fffee3f0 | 00000000 00000000 00001610 00000000 | ................

HaRET(1)# set MTYPE 1232

HaRET(2)# set KERNEL "zImage42"

HaRET(3)# set CMDLINE "debug quiet psplash=false loglevel=7 root=/dev/mmcblk0p3 init=/sbin/init console=tty0 video=omapfb:accel heraldlcd=screen:1 4"

HaRET(4)# log "earlylog.txt"

And this is "earlylog.txt":
HaRET(5)# bootlinux

boot KERNEL=zImage42 INITRD=

Opening file zImage42

boot params: RAMADDR=10000000 RAMSIZE=04000000 MTYPE=1232 CMDLINE='debug quiet psplash=false loglevel=7 root=/dev/mmcblk0p3 init=/sbin/init console=tty0 video=omapfb:accel heraldlcd=screen:1 4'

Boot FB feedback: 1

Built virtual to physical page mapping

Allocated 409 pages (tags=4AB00000/1393a000 kernel=4AB01000/1393b000 initrd=4AC95000/13acf000 index=4AC95000/13acf000)

Built kernel tags area

Built page index

Video buffer at 48A00020 sx=240 sy=320 mx=60 my=53

Video Phys FB=20001020 Fonts=13ad1064

preload=2264@4AC98000/13ad2000 sj=4AC98000 stack=4AC96000/13ad0000 data=4AC97000/13ad1000 exec=13ad2128

Reading 1652252 bytes...

Read complete

Launching to physical address 13ad2010

Trampoline setup (tram=136@000241C0/180241c0/10d381c0)

MMU setup: mmu=AC390000/10390000

Go Go Go...


I hope someone will find out what's happening with my screen, because any screen option is working 100%. I'll be in the IRC channel if you need any other test ;)

[ivanmmj]

Hello all,

I'm new to this topic and I've been watching your success trying to run Android. I'm the happy owner of a Spanish HTC P4350 (not Wing) unlocked from factory (if this makes a difference). I don't know if my P4350 is HardSPL'ed or CID unlocked, all I know is that is SIM unlocked.

I've tried all the zImages posted, but only had little success with the last zImage42. I suffered the white screen issue as well, but it seems to be solved with the last 0.3pre2 version. The bad thing is that even though I select boot option 5 (Android) in default.txt, my Herald always enters the GPE GUI and it doesn't continue booting Android as I've seen in Darkstar62's video. I deleted all the files from both the vfat and ext3 partitions, extracted the new rootfs.tar.bz2 and copied the new Windows files. ¿Is there anything that I'm missing?, ¿is there any way to boot Android from the GPE GUI?.

I would like to contribute to this awesome project, at least in the testing part. Here are some more details about my device:

Model (in the battery): HERA160
Model (in device information): HERA100 (??)
Processor: OMAP850-201MHz
Memory: 43.90 MB left
SO CE 5.2.1238 (Windows Mobile 6 Professional, original from HTC Club)

ROM version: 4.17.412.2 ESN
ROM date: 06/20/07
Radio version: 02.94.90
Protocol version: 4.1.13.44
ExtRom version: 4.17.412.102


Hope this information helps. I'm willing to test anything you might need, send logs... whatever.

Keep the good work guys ;)

The first boot will always boot there. Log into it, (root:wing) then type startAndroid and press enter and wait. You'll see it give you some errors and log you out. That's fine. Just wait. Wait a while. Eventually, it'll start booting. After that first time, it should boot normally the next time.

[darkstar62]

Thanks to Kuuf, I was able to boot directly to Android (5 was actually GPE, so I changed it to 4). But I still have some problems with the screen:


screen:0 -> The image is still, but shifted to the right (by 20 pixels or so) and color depth seems to be 256 colors.
screen:1 -> The image "vibrates", but is correctly aligned. Color depth is OK.


This is the "dispdump.txt" log:
HaRET(2)# pdump 0xfffec000 0x20

fffec000 | f8000089 09010cef 0478053f ff30000f | ........?.x...0.

fffec010 | ffffffd2 5c00f000 fffffc00 fffffd3f | .......\....?...

HaRET(3)# pdump 0xfffee300 255

fffee300 | 00000000 00000000 00000000 00000000 | ................

fffee310 | 00000000 00000000 00000000 00000000 | ................

fffee320 | 00000000 00000000 00000000 00000000 | ................

fffee330 | 00000000 00000000 00000000 00000000 | ................

fffee340 | 00000000 00000000 00000000 00000000 | ................

fffee350 | 00000000 00000000 00000000 00000000 | ................

fffee360 | 00000000 00000000 00000000 00000000 | ................

fffee370 | 00000000 00000000 00000000 00000000 | ................

fffee380 | 00000000 00000000 00000000 00000000 | ................

fffee390 | 00000000 00000000 00000000 00000000 | ................

fffee3a0 | 00000000 00000000 00000000 00000000 | ................

fffee3b0 | 00000000 00000000 00000000 00000000 | ................

fffee3c0 | 00000000 00000040 00001000 0000681e | ....@........h..

fffee3d0 | 00000000 00000000 00000000 00000000 | ................

fffee3e0 | 00000000 00000000 00000000 00000000 | ................

fffee3f0 | 00000000 00000000 00001610 00000000 | ................

HaRET(1)# set MTYPE 1232

HaRET(2)# set KERNEL "zImage42"

HaRET(3)# set CMDLINE "debug quiet psplash=false loglevel=7 root=/dev/mmcblk0p3 init=/sbin/init console=tty0 video=omapfb:accel heraldlcd=screen:1 4"

HaRET(4)# log "earlylog.txt"

And this is "earlylog.txt":
HaRET(5)# bootlinux

boot KERNEL=zImage42 INITRD=

Opening file zImage42

boot params: RAMADDR=10000000 RAMSIZE=04000000 MTYPE=1232 CMDLINE='debug quiet psplash=false loglevel=7 root=/dev/mmcblk0p3 init=/sbin/init console=tty0 video=omapfb:accel heraldlcd=screen:1 4'

Boot FB feedback: 1

Built virtual to physical page mapping

Allocated 409 pages (tags=4AB00000/1393a000 kernel=4AB01000/1393b000 initrd=4AC95000/13acf000 index=4AC95000/13acf000)

Built kernel tags area

Built page index

Video buffer at 48A00020 sx=240 sy=320 mx=60 my=53

Video Phys FB=20001020 Fonts=13ad1064

preload=2264@4AC98000/13ad2000 sj=4AC98000 stack=4AC96000/13ad0000 data=4AC97000/13ad1000 exec=13ad2128

Reading 1652252 bytes...

Read complete

Launching to physical address 13ad2010

Trampoline setup (tram=136@000241C0/180241c0/10d381c0)

MMU setup: mmu=AC390000/10390000

Go Go Go...


I hope someone will find out what's happening with my screen, because any screen option is working 100%. I'll be in the IRC channel if you need any other test ;)

Looks like your screen timings match up exactly with the screen:1 configuration. The screen shaking could be an indication that the pixel clock for that mode is slightly off for your phone. I can build a test kernel that should auto-detect the proper settings.

...maybe I should have done that to begin with ;P

- d

[Kernel Jag]

No prob, it's been fun :)

As for git...I'm trying to pull out a specific revision from a remote branch, and I can't even figure out how to switch to the branch, let alone get the revision out. Can you help?

- d
Sorry, I'd disappeared in the last few days. In case you're still struggling, the steps are:

Clone the repo to your PC first
git clone ssh://myserver.com/var/git/myapp.git
List all the branches, note the name of the one you'd wanna use
git branch -a
Point to note, master is usually the main branch
Now for the part about shape-shifting (some call it voodoo magic)..the following command will automagically transform your current repo directory into the desired branch
git checkout XYZ
To move back and forth within the branch, you could use the HEAD mnemonic and give instructions relative to this. HEAD is the top of the branch.
git checkout HEAD
To go three step below, you can say HEAD~3. The format is HEAD~n for n steps below.
git checkout HEAD~n


Resources:
http://toolmantim.com/articles/setting_up_a_new_remote_git_repository
http://www-cs-students.stanford.edu/~blynn/gitmagic/ch04.html

DISCLAIMER:
I've had a bit of a role change @ work, and it's been about 4-5 months since I've used git. So forgive me if there are any mistakes in the instructions above.

[Fenopy]

So I spent part of my work day waiting for my Wing to DL the HaRet loader + zImage42. It runs, gets past what I think is where it would normally white-screen, but then I get other errors, but after reading them, I am fairly certain it is SD-Card format based.

So the question is, how do I format my SD-Card? How large do you make partitions and of what File System?

I will be trying all of this tonight to see if I can get Android up!

[darkstar62]

So I spent part of my work day waiting for my Wing to DL the HaRet loader + zImage42. It runs, gets past what I think is where it would normally white-screen, but then I get other errors, but after reading them, I am fairly certain it is SD-Card format based.

So the question is, how do I format my SD-Card? How large do you make partitions and of what File System?

I will be trying all of this tonight to see if I can get Android up!

You can try going through the procedure in the INSTALL file included with the distribution. It takes you all the way through, partitioning, making the filesystems, and copying the root filesystem image on. It should tell you everything you need.

Lemme know if you need more help. Glad to hear you're getting that far! That tells me for sure we can close this white screen issue once and for all.

- d

[neoobs]

Just curious... how do we access the executables in the /android/system/bin? I keep trying but keeps telling me it isn't found.

These are vital systems to figure out what is going wrong inside android.

[darkstar62]

Just curious... how do we access the executables in the /android/system/bin? I keep trying but keeps telling me it isn't found.

These are vital systems to figure out what is going wrong inside android.

Heh, yeah...I'm not sure why that happens, but you can't run the binaries in /android/system/bin directly.

Do it like this:

chroot /android /system/bin/<program>

Alternately, you can get a shell inside that so everything you run will be from that:

chroot /android /system/bin/sh
export PATH=/system/bin

Then you should be able to run binaries as if you were in the Android console.

- d

[Kernel Jag]

Hi everyone, I finally took out time to experiment with Android on my Herald. Was stuck on the partitioning bit for a while (don't have internet on the Ubuntu install which made things harder) but finally was able to figure it out. So now I've got 3 partitions, same order as in the INSTALL readme. The partition numbers got incremented by 1 though. So my ext3 parition is mmcblk0p4. I made the change in default.txt for the same.

Unfortunately, I get stuck before the fs gets loaded. Here's a screen dump from the end:


Warning: unable to open an initial console
Failed to execute /sbin/init. Attempting defaults...
Kernel panic - not syncing: No init found. Try passing init= option to kernel


Might help to add that the screen appears somewhat shifted towards the right, on the x axis.

Anyone got any clue what's going on?? :(

[darkstar62]

Hi everyone, I finally took out time to experiment with Android on my Herald. Was stuck on the partitioning bit for a while (don't have internet on the Ubuntu install which made things harder) but finally was able to figure it out. So now I've got 3 partitions, same order as in the INSTALL readme. The partition numbers got incremented by 1 though. So my ext3 parition is mmcblk0p4. I made the change in default.txt for the same.

Unfortunately, I get stuck before the fs gets loaded. Here's a screen dump from the end:


Warning: unable to open an initial console
Failed to execute /sbin/init. Attempting defaults...
Kernel panic - not syncing: No init found. Try passing init= option to kernel


Might help to add that the screen appears somewhat shifted towards the right, on the x axis.

Anyone got any clue what's going on?? :(

We talked on IRC about the partition issue.

As for the screen, what screen: parameter are you using? The default? If so, you might try screen:1. If that doesn't work, I have timings for a screen:2 that might work in your case.

- d

[fdez.romero]

We talked on IRC about the partition issue.

As for the screen, what screen: parameter are you using? The default? If so, you might try screen:1. If that doesn't work, I have timings for a screen:2 that might work in your case.

- d

Yeah, I had the same issue with the screen (it was shifted to the right like 20 pixels, and the image in this column was deformed). Try with screen:1 in the CMDLINE inside default.txt as Darkstar62 says, and if you get vibrations or flickering in the display, then try with the screen:2 config I got yesterday from my P4350.

Little by little, but we are going into it...:rolleyes:

[Kuuf]

-- nevermind, i quoted an old post .. --

[darkstar62]

Yeah, I had the same issue with the screen (it was shifted to the right like 20 pixels, and the image in this column was deformed). Try with screen:1 in the CMDLINE inside default.txt as Darkstar62 says, and if you get vibrations or flickering in the display, then try with the screen:2 config I got yesterday from my P4350.

Little by little, but we are going into it...:rolleyes:

Heh, I really should put out the kernel that has that config, before you try it :) I'll try and get that out later today.

- d

[darkstar62]

Alright, try this:

http://dl.getdropbox.com/u/198699/linux_wing/zImage47

For this kernel (and all new kernels from here on out), remember to set your MTYPE to 1461, otherwise it won't boot.

This kernel supports the two screen:0 and screen:1 configs, as well as the new screen:2 config that we recently added. Give that one a try and lemme know if it works. You can also specify each of the timing parameters on the command line for even more fine grai ned control. That's how we got screen:2. We can get into that if we need to.

Enjoy.
- d

[neoobs]

Fixed the keyboard... well for the most part, still working on the alt functions but that is harder.

Will upload it to the svn tomorrow as I am beat. All the other developers went to sleep hours ago LOL

[darkstar62]

Hey all, thought I'd post an update for those who don't frequent the IRC room. Thanks to neoobs, we now have a fully working keyboard in Android including the directional pad. Very nice! I'm also putting the finishing touches on the build system and in allowing all this to run without partitioning. Preliminary tests show it works beautifully. I'm waiting on a final test build to complete, and I should be able to put out a 0.3pre3 with the following installation instructions:

1. Copy everything in the wing-linux-0.3pre3 directory to /Storage Card/linux

2. Run HaRET

The system auto-detects the new installation and sets it up, asking for various things like how much storage space you want and such. Then, it boots straight in. No more need to do anything from a Linux computer, no more complex partitioning schemes -- it all runs from the windows partition of your storage card.

For those who have installed previous releases to partitions, the bootup will auto-detect that and ask you which installation you want to start.

Ivanmmj has agreed to help us package this up in a .cab file too once it's all ready, so that's coming soon too. I'm also working on an idea for the kernel that will auto-detect your video settings so in most cases you souldn't need to specify the screen parameters anymore.

Stay tuned!
- d

[Kernel Jag]

No more need to do anything from a Linux computer, no more complex partitioning schemes -- it all runs from the windows partition of your storage card.

Wow..now that's quite a progress!

Cheers mate!

[darkstar62]

Alright, its out! Get it while it's hot:

http://files.getdropbox.com/u/198699/linux_wing/wing-linux-0.3pre3.zip

Installation Instructions:

1. Create a directory /Storage Card/linux

2. Unzip the contents of the zip file there

3. Move the files in wing-linux-0.3pre3 to /Storage Card/linux

4. Run HaRET

5. Follow the instructions.

If you've installed the previous releases and have a partitioned SD card, the bootloader will automatically detect that and prompt you for which one you wish to boot. Use the arrow keys or DPAD to select one.

I haven't yet added the video autodetection support yet, so you'll still need to edit your default.txt file and ensure the heraldlcd parameter is set correctly for your device. If you don't know what to put there, leave it as is -- most users should find it works well enough.

New things in this release:


Root filesystem was created using a build system commited to SVN, instead of by copying files off my phone -- it's reproduceable!
The DPI setting of Android has been changed to fit our smaller screens a bit better. The phone dialer still has overlapping buttons, but you can now read the letters on the bottom of them and using them is much easier.
The Angstrom system has been pared down to a simpler console-only system to save space. It now just sits in the background, and Android loads automatically.
No more SD card partitioning is necessary! Simply unzip and enjoy!
Console access is available through USB as always
Android keyboard and button support is now 99% complete (only missing mappings for a couple of the side buttons). Arrow keys / direction pad works as expected, and alpha / symbol mappings are correct per WM6 settings, so you can use the keyboard like you're used to. Thanks neoobs!


As always, I'll be in the chat room to help or discuss ideas. Happy testing!

- d

[darkstar62]

OK, I've made it even easier. Go to the downloads section of the wing-linux site and grab the 0.3pre3 development CAB file. Install this to WM6, then click Start->Programs->Wing Linux.

Enjoy.
- d

[darkstar62]

Quick update...I've added video mode autodetection to the kernel, as well as disabling the suspend mode (as it's currently broken). Once you've got 0.3pre3, grab this and give it a roll:

http://files.getdropbox.com/u/198699/linux_wing/zImage51

Put that in your /Storage Card/linux directory and modify your default.txt appropriately. Be sure to remove any heraldlcd options you might have -- they will override the autodetection.

Happy testing!
- d

[darkstar62]

It's official -- 0.3 is out! Grab it at:

https://sourceforge.net/project/platformdownload.php?group_id=253356

Enjoy!

- d

[apreichner]

It's official -- 0.3 is out! Grab it at:

https://sourceforge.net/project/platformdownload.php?group_id=253356

Enjoy!

- d

Wow... you guys are doing awesome. I never thought I'd see the day, but it looks great! Can't wait to try it.

Keep up the good work. I can't wait for WiFi and GSM!

[N3xt2N0N3]

Just updated the first page with darkstar26's instructions on Wing LINUX 0.3. I'm sorry for the lack of updates. My wing took a crap. It doesnt even charge now.

Waiting for my girlfriend to get a new phone so i can take her wing. hehehe

But besides that. I am still here so if theres anything i missed and you feel it should be on the first page let me know.

Thanks

[hogindas]

do you have to have linux on your computer to do this, cause i put the android on my phone, and i cant do anything, no service, nothing, is that for everyone or just me?

[ivanmmj]

do you have to have linux on your computer to do this, cause i put the android on my phone, and i cant do anything, no service, nothing, is that for everyone or just me?

No, you don't have to have linux.
As far as service, it's an early alpha, it doesn't have working service, yet.

[DestructDez1]

Great job. .03 is amazing. when do you estimate service will work? There are some issues with speed but its understandable and there is a hang that resulted in a crash when you press the record video button. keep up the good work.

[darkstar62]

Great job. .03 is amazing. when do you estimate service will work? There are some issues with speed but its understandable and there is a hang that resulted in a crash when you press the record video button. keep up the good work.

I'm hoping we'll have at least data service early in 0.4 development. If all goes well, we can try for sound support too, which would lead to being able to make calls too. We already have a working GSM driver that I've used to successfully make a call (no sound though), so getting data working shouldn't be too far off as I see it.

Can you reproduce that hang and crash?

- d

[suprduprchunk]

I tried to install the .3 cab file and I am getting the message:

switch_root: Bad console '/dev/console'
Kernel panic - not syncing: Attempted to kill init!

I am using WinMo 6.5. Would that make a difference whether it will run the Android or not.

[Sincidius]

I got the same message. I ran it on a 6.1 on OpenTouch 7.5 I didn't have a microSD with enough space (256M!) I put in my 1Gig and it worked fine.

[ivanmmj2]

It needs at least 300mb free + 64mb's free for the swap, I believe.

[darkstar62]

I tried to install the .3 cab file and I am getting the message:

switch_root: Bad console '/dev/console'
Kernel panic - not syncing: Attempted to kill init!

I am using WinMo 6.5. Would that make a difference whether it will run the Android or not.

Shouldn't make any difference. Did you install the cab to your storage card? That's a must -- along with at least 400mb free. The cab only uses about 30, but when you install, it uses an additional 364mb at a minimum for the base system image and swap files.

- d

[darkstar62]

So I figured it'd be good to give everyone an update on 0.4 development. I'm closing in on full support for GSM in Android -- including making calls and data access (though no sound, so calls aren't too useful right now). I've got Android recognizing the GSM, connecting to the carrier, and even starting up the data connection -- just need to do a bit of polishing to get it all consistent and reproduceable.

I'm planning to put out a 0.4pre1 with the changes once I'm happy with them. Should make things a lot more fun to test.

Until then.
- d

[Kuuf]

So I figured it'd be good to give everyone an update on 0.4 development. I'm closing in on full support for GSM in Android -- including making calls and data access (though no sound, so calls aren't too useful right now). I've got Android recognizing the GSM, connecting to the carrier, and even starting up the data connection -- just need to do a bit of polishing to get it all consistent and reproduceable.

I'm planning to put out a 0.4pre1 with the changes once I'm happy with them. Should make things a lot more fun to test.

Until then.
- d

Very nice let me/us know when we can test it.
I'm moving right now, that's why I haven't been online very much lately

[suprduprchunk]

Shouldn't make any difference. Did you install the cab to your storage card? That's a must -- along with at least 400mb free. The cab only uses about 30, but when you install, it uses an additional 364mb at a minimum for the base system image and swap files.

- d

I did install it on the Micro SD which has about 2000 free MB. I installed the cab. Then accessed the linux folder in storage card, ran Haret. When I run default.txt from Haret it asks me how much space I want to allocate for Wing Linux and how much space I would like to use for virtual memory. I keyed in 400 mb and 128 mb. After it do all that it finally ends at that message.

[darkstar62]

I did install it on the Micro SD which has about 2000 free MB. I installed the cab. Then accessed the linux folder in storage card, ran Haret. When I run default.txt from Haret it asks me how much space I want to allocate for Wing Linux and how much space I would like to use for virtual memory. I keyed in 400 mb and 128 mb. After it do all that it finally ends at that message.

Hmm, I'll have to test that configuration. I've never tried entering something different than the defaults. Could be a bug in the installer.

- d

[suprduprchunk]

Hmm, I'll have to test that configuration. I've never tried entering something different than the defaults. Could be a bug in the installer.

- d

I will try running it using the defaults and see what it does. Thanks

[suprduprchunk]

I tried just hitting enter when it asks for the memory values and I tried typing in the defaults and I am still getting the same message.

[darkstar62]

I tried just hitting enter when it asks for the memory values and I tried typing in the defaults and I am still getting the same message.

That's really weird... Maybe try the 0.4pre1 cab and see if that helps. It's in the next post. :)

- d

[darkstar62]

Go play with it and lemme know:

https://sourceforge.net/projects/wing-linux/files/

You'll need to set up your APN for data to work -- restart after configuring it (or enable/disable airplane mode twice).

Also, if you're upgrading, remember to remove your /Storage Card/linux directory after uninstalling the old release! Otherwise nothing will be updated.

- d

[suprduprchunk]

That's really weird... Maybe try the 0.4pre1 cab and see if that helps. It's in the next post. :)

- d

Worked this time. Looks good bro. Thanx

[moneyslap03]

I need Help i had setup T-Mobile APN settings and press save and it didnt save the settings i tried to disable and enable the airplane mode to see if the network would start up and nothing i am using the new 0.4pre1 cab

EDIT: I restarted Android it took about ten seconds to show bars great work you have hear i would to follow up the progress on this project also how would i go about using the Data network as only the cellular part is working

[xda-dude]

Good for you, guys! Keep up the good work! I hope we'll have our Xmas' gift before December!

[darkstar62]

I need Help i had setup T-Mobile APN settings and press save and it didnt save the settings i tried to disable and enable the airplane mode to see if the network would start up and nothing i am using the new 0.4pre1 cab

EDIT: I restarted Android it took about ten seconds to show bars great work you have hear i would to follow up the progress on this project also how would i go about using the Data network as only the cellular part is working

What did you enter for your APN? You have to have the right address, and MCC / MNC codes (I think it's MNC...the two or three digit one). Otherwise Android won't use them. If you've got it right, you should see your new APN in the APNs list.

- d

[moneyslap03]

I have the text and calling feature working the data just isnt working for MCC/MNC i have 310 and 260 By the way this is T-Mobile US network i am on

EDIT: I Finally got it i was messing around with androind i added my own lockscreen and i restarted the phone another time and the G with the arrows came up waiting for E to show up but data is now shown im currently testing right now thanks again

[moneyslap03]

EDIT: Sorry my internet connection Bounced sorry for the double post

[ivanmmj]

The Dream forums have an APN list that's included with the Dream ROMs that automatically configures the APN. Maybe we can borrow it from them.

[darkstar62]

The Dream forums have an APN list that's included with the Dream ROMs that automatically configures the APN. Maybe we can borrow it from them.

That's a real good idea. Android will use the /system/etc/apns-conf.xml file as the default when you first boot, so if it has something that matches, it'll use it. That way nobody has to manually enter their settings.

- d

[ivanmmj]

That's a real good idea. Android will use the /system/etc/apns-conf.xml file as the default when you first boot, so if it has something that matches, it'll use it. That way nobody has to manually enter their settings.

- d

Do you want it off of my phone?

[darkstar62]

Do you want it off of my phone?

Sure. You can even add it to the build system if you'd like. Just add it in buildsys/trunk/oe/android-1.5, and modify the buildsys/trunk/oe/android_1.5.bb file to include it.

- d

[ivanmmj]

Sure. You can even add it to the build system if you'd like. Just add it in buildsys/trunk/oe/android-1.5, and modify the buildsys/trunk/oe/android_1.5.bb file to include it.

- d

Done. Let's hope I did it right. :p

[xardas_90]

just wanted to say good luck with this project i think it's a revolutionary port for the android....i love it

[adelco93]

Done. Let's hope I did it right. :p

i dont mean to sound impatient, lol , but are you going to post the cab with the built in apn list. :D

[razorbone]

Tried it on my Herald. The interface is very slow. Have to wait like 2-3 seconds before a function responds after a press.

Looking promising though! If this project becomes successful, count me in to be using this ROM! :)

[darkstar62]

i dont mean to sound impatient, lol , but are you going to post the cab with the built in apn list. :D

Here's an updated cab file:

http://files.getdropbox.com/u/198699/linux_wing/wing-linux-0.4pre1.cab

I haven't tested it yet, so ymmv. It includes the new file, though, so you should in theory be good to go.

- d

[darkstar62]

Tried it on my Herald. The interface is very slow. Have to wait like 2-3 seconds before a function responds after a press.

Looking promising though! If this project becomes successful, count me in to be using this ROM! :)

That's my experience too. Working is step 1. After that, then we make it fast :) I think there's going to be considerable optimizations to be done to get it running as nicely on our wings as it runs on the g1, simply because we have half as much memory as the g1.

- d

[xda-dude]

Hello, Darkstar62!

There's a minor bug that needs to be fixed. Let me explain that to you:

I installed Wing Linux 0.4pre1 in my TMo Wing. It booted very well using default settings. I always have to put a pin code to use my SIM card in any phone, so I was asked to put it in on the screen. Well, on that first screen it appears the following message: "SIM CARD IS LOCKED " and "SCREEN LOCKED". I push the button that is above the END key and it gives me another screen where I have to put my pin number, but it says " Incorrect PIN Code!", after I put the right numbers and the "Unlucking SIM Card" message appears; even though I'm putting the right pin as I already said. So I can't go past those two screens. Why do you think is that? Well, in the meantime, I'll try to free my SIM card from the PIN code to test it better ;)
Update: The softkey numbers sometimes are wrongly mapped(e.g.: when I click on the 8 key, it maps the OK key).
Thanks for your efforts!

XDA-DUDE.

[darkstar62]

Hello, Darkstar62!

There's a minor bug that needs to be fixed. Let me explain that to you:

I installed Wing Linux 0.4pre1 in my TMo Wing. It booted very well using default settings. I always have to put a pin code to use my SIM card in any phone, so I was asked to put it in on the screen. Well, on that first screen it appears the following message: "SIM CARD IS LOCKED " and "SCREEN LOCKED". I push the button that is above the END key and it gives me another screen where I have to put my pin number, but it says " Incorrect PIN Code!", after I put the right numbers and the "Unlucking SIM Card" message appears; even though I'm putting the right pin as I already said. So I can't go past those two screens. Why do you think is that? Well, in the meantime, I'll try to free my SIM card from the PIN code to test it better ;)
Thanks for your efforts!

XDA-DUDE.

Yup, known issue. I've re-opened the GSM ticket until I can get that fixed.

- d

[marek1]

First you made nice work that you port Android and run it from WM but.

The Android is not usefull for normal using, I thing that Is just for test.

Problems:
WIFI
CAMERA
POWER SAVING ( LCD )
Configuration of MMS or Internet GPRS connection
No task manager
NO file explorer
No any video player
MP3 player
Document editor
Time and Data change
Other settings

If you will fix all things then it will be great.

[Kuuf]

Dude, why being so negative?
Darkstar knows there's yet much to do, but the project is evolving ...
D, together with some other people, is working on it ...

[marek1]

I am not negative but I just mentioned what the main issues are.

[darkstar62]

OK, between posts on here and in IRC, this is getting out of hand.

Firstly, this is a volunteer effort. I work on this in my free time, as do the others on the team. As such, development can be slow at times. If you want it faster, feel free to submit patches and get in on the development.

Secondly, all status questions can be answered by reading the wiki. If you don't have the link, google for "wing linux", or go here: http://wing-linux.sf.net. There's a link on the right for "Status" that shows the state of things as of the latest -pre release. If it's not listed as working, it doesn't work.

Thirdly, we have a bug tracking system on the wiki. Click the "Tickets" link and select a report. I usually use "all tickets (including closed) by milestone". If you see a ticket listed for your problem, it's a known issue and will be worked. If you see something you can help with, by all means feel free to work it. Patches are always welcome. If you found a problem that's not listed in the Status page and isn't in the existing bugs, file a ticket, using as much information as you can give me as to the problem.

Fourthly, we're only at 0.3 stable. That means third alpha release. Things won't work completely at this point. When we hit 1.0, that's when you can expect everything to be working. Until then, the "stable" releases are considered stable up to what we have working, and the -pre releases I periodically put out are test versions intended to get newer bleeding edge features out for testing sooner -- they are not considered stable!

If you're feeling like you can't contribute to the project because you don't know how to work on the kernel or on Android, I can tell you that I didn't either when I started working on this. I had never even worked with the kernel, let alone writing drivers. And Android is totally new to me too -- most of what I find out I get by googling around and by following IRC channels such as #android, #linwizard, #htc-linux, and our own #wing-linux. Best I can say is, jump in and try it. Grab the build system and try and build yourself a CAB file. Grab the kernel and try and build yourself a custom kernel. Then, try and modify them. The best way to do this stuff is to just get in and play with it.

I want to stress that, with some exception, I am the only one on the project putting in significant contribution. But I have a job, and a family, which means I don't always have time to work on this stuff. Nobody's paying me to work on this. I do it out of the sheer enjoyment of working with this stuff.

But I can use all the help I can get. Submit kernel patches. Try and get more apps in Android (via the build system, please -- we can't distribute programs with Android that are illegal to distribute, or unobtainable through public means). Do some research about hardware. Try and get the EOS bootloader to work so we can boot from storage card directly. There's many ways to contribute. Find something interesting and go for it.

And please please please, check the wiki before you post questions. There's a good chance we know of the issue, and maybe even have a fix planned.

- d

[marek1]

Yes I know that is very hard, and is great that someone do this job.

OK, now I can see what is not working. I didnt mean it bad, just for info.:)

[xardas_90]

darkstar we all apreciate your work and effort and we are forever gratefull for doing this for us freely...not to mention nobody else would have done it even for money...thank you again and if people will be rude and critic please ignore them and think of us the people who really care and apreciate this at it's real value

[xda-dude]

darkstar we all apreciate your work and effort and we are forever gratefull for doing this for us freely...not to mention nobody else would have done it even for money...thank you again and if people will be rude and critic please ignore them and think of us the people who really care and apreciate this at it's real value

Just what he said, please!:D

[moneyslap03]

Yes.. please think of us i had finally got the Wing off my fathers hands because of him keeping the Wing for stereo bluetooth while he had the G1 i installed cupcake so fast on his G1 for stereo bluetooth just to get the Wing, now i wanna have a fully functional Android OS running on my wing. I love this Project So keep up the good work and dont listen to the negative comments because ive seen devs get Angry and called projects off whilelist on the PSP scene

[darkstar62]

Thanks for all the positive feedback, I really appreciate it. I'm not going to call the project off. I just don't want anyone to have the misconception that our project is far enough along to be used full-time. We're definitely getting there, but there's a lot more work to do. All our releases so far have been for testing. I like to put out frequent releases to get new stuff into your hands faster. Release early, release often -- that's the mantra of open source. That way I can find what doesn't work for you that does for me, so we can get all the variations and bugs worked out.

I'll continue to put out periodic pre releases like I have been -- without that I wouldn't have learned about the locked SIM card issue until we put out 0.4 (whenever that will be). By all means, don't feel like you can't report problems here. Just be sure it's something I don't already know. :) Reading posts here and looking at the wiki are the best ways to figure out what I know.

And as always, the more help I get with all this, the faster we can go. Feel free to contribute any way you feel comfortable. It's always welcomed.

Thanks again for the positive comments and for all the testing feedback. Let's get back to work, shall we? :)

- d

[moneyslap03]

Im not sure if you said this earlier but do you know about the SD card issue as i was trying to download a app and a few photos off the web browser and it said the card was not inserted?

[darkstar62]

Im not sure if you said this earlier but do you know about the SD card issue as i was trying to download a app and a few photos off the web browser and it said the card was not inserted?

I've been working on a fix to that, and at least in the repository is checked in a fix that should allow Android to see the contents of your storage card as an actual storage card. With all defaults, you end up with ~200mb free of device memory and all the rest of your storage card for storage. Seems to work well for me (or would if I didn't have filenames that Android doesn't like :)) That'll be in 0.4pre2, whenever it makes it out.

- d

[moneyslap03]

I look forward.. thanks for the reply

[jsievert]

First off, thanks darkstar62 for all the hard work on this project. I just got a used wing and am excited to give this a try. I do have one quick question that I did not see on the site. Is it possible to go back and forth between android and the default os? Forgive me if this questions sounds silly. I would like to try it knowing that its alpha be able to go back to the current one.

Thanks again all!

[xnappo]

I am sure in some way I am being a moron, but I have tried multiple ways of extracting both .3 and .4pre1, and whenever I try to launch 'Wing Linux' either from the icon, or the direct 'haret-0.5.2' I get 'haret-0.5.2' is not a valid Pocket PC application.

Any ideas? I have downloaded the cab from multiple computers, and tried downloading the cab directly from my Wing...

xnappo

[ivanmmj]

I am sure in some way I am being a moron, but I have tried multiple ways of extracting both .3 and .4pre1, and whenever I try to launch 'Wing Linux' either from the icon, or the direct 'haret-0.5.2' I get 'haret-0.5.2' is not a valid Pocket PC application.

Any ideas? I have downloaded the cab from multiple computers, and tried downloading the cab directly from my Wing...

xnappo

Extracting?

[xnappo]

Extracting?

Meaning I tried installing the cab from the Wing as usual, and when that didn't work, I tried manually extracting the files in WinZip and moving them over. Same thing. Also tried downloading haret-0.5.2 from here:
http://www.handhelds.org/~koconnor/haret/

Same thing... Weird.

xnappo

[ivanmmj]

Meaning I tried installing the cab from the Wing as usual, and when that didn't work, I tried manually extracting the files in WinZip and moving them over. Same thing. Also tried downloading haret-0.5.2 from here:
http://www.handhelds.org/~koconnor/haret/

Same thing... Weird.

xnappo

Your phone is not signature unlocked. What ROM are you using?

[xnappo]

Your phone is not signature unlocked. What ROM are you using?

Some ancient Touch-IT ROM from here(from like two years ago)... 'About' says:
CE OS 5.2.19199 (Build 1919905.2.4)

Thanks,
xnappo

[ivanmmj]

Try finding "aserg's policies" and installing that first.
That's the easiest way to "bypass" the signature policies aside from modifying the kernel itself while cooking.

[darkstar62]

First off, thanks darkstar62 for all the hard work on this project. I just got a used wing and am excited to give this a try. I do have one quick question that I did not see on the site. Is it possible to go back and forth between android and the default os? Forgive me if this questions sounds silly. I would like to try it knowing that its alpha be able to go back to the current one.

Thanks again all!

...whoah, there's been a lot of activity...wonder why I didn't get an email.

Anyway, yes, it's absolutely possible. When you're ready to reboot back to wm6, just reset your phone. It boots that by default. The installation is perfectly safe -- everything goes to the storage card and runs from there. No bootloader replacement is made, nor is the ROM touched in any way. Simply reboot to be back into WM6.

- d

[darkstar62]

Meaning I tried installing the cab from the Wing as usual, and when that didn't work, I tried manually extracting the files in WinZip and moving them over. Same thing. Also tried downloading haret-0.5.2 from here:
http://www.handhelds.org/~koconnor/haret/

Same thing... Weird.

xnappo

You don't perchance have a non-English phone, do you? There's been some discussion on the SF forums about this issue. Apparently WM6 will locale-ize the "Storage Card" directory, making the hack I put in to force to storage card fail miserably for phones that aren't localed in English.

- d

[xnappo]

You don't perchance have a non-English phone, do you? There's been some discussion on the SF forums about this issue. Apparently WM6 will locale-ize the "Storage Card" directory, making the hack I put in to force to storage card fail miserably for phones that aren't localed in English.

- d

Well, my phone was not originally non-english, however I believe the ROM I am running is actually a Herald ROM (I have to run AEKMap for the hardware keyboard to work right).

I tried the 'aserg policies' cab, but it didn't seem to do anything.

Sounds like I need to update to a 'modern' ROM. As you can tell, I have been out of it for a while.

Thanks for the help guys,
xnappo

[htc_wing23]

SO this google android, is it the same program that the G1 is running? I saw a t-mobile wing on youtube running android 1.5. Which one is faster on the wing? android of windows mobile 6.5? How many android software is there? thanks

[moneyslap03]

yes it is the same OS as the G1. Currently Windows Mobile 6.5 is more stable then Android running on the Wing. Android is open source so it can be ported to any platform that is hardware capable.

[darkstar62]

yes it is the same OS as the G1. Currently Windows Mobile 6.5 is more stable then Android running on the Wing. Android is open source so it can be ported to any platform that is hardware capable.

Even better, Android can be made to run on hardware it's not designed for :) I will agree though, WM is currently more stable than Android, though Android has some speed advantages over WM (except when you run low on memory, which happens almost immediately right now).

- d

[darkstar62]

So we've got a new forum system setup for wing-linux based on phpBB. Should be a lot better, and we can start topics on targeted things here instead of just posting continuations to this thread. It can be had at:

http://sourceforge.net/apps/phpbb/wing-linux/index.php

We've got forums currently for general use of the project, development, and another for just any conversation that doesn't quite fit anywhere else.

There's currently a topic going concerning development on the HTC Gene, so if you know anything about that, feel free to join in. :)

And as always, we've got our chat room at #wing-linux.

See you there.

- d

[PublicITI]

I would also like to give a feedback.
- It runs fast
- I really like it
- It irritates that the Buttons are mapped wrong
- I can't unlock the device, if I inserted my Swisscom SIM-Card.
|--> It keeps telling me that my Code is wrong, but it isn't

[darkstar62]

I would also like to give a feedback.
- It runs fast
- I really like it
- It irritates that the Buttons are mapped wrong
- I can't unlock the device, if I inserted my Swisscom SIM-Card.
|--> It keeps telling me that my Code is wrong, but it isn't

Buttons mapped wrong...What device are you using? Is it an English phone or a different language? Currently the mappings we use are geared towards English phones, so that could be why the mappings are off.

As to the sim card issue, that's known, and I've manage to get recent development versions to accept the pin, but Android then doesn't continue connecting. I need to do more research on that. In the meantime, the only way to use it is to disable the PIN password.

- d

[ivanmmj]

They're mapped to the Wing, not the Herald, I believe.

[neoobs]

We can fix that if someone with a Herald wants to come forward and help, currently I do not have a herald so I can't make the mappings for it and test if they work.

[darkstar62]

Been a while since I posted here. So, I come bearing gifts! Check it out:


Many popular APNs have been integrated for GPRS support out-of-the-box
Bluetooth works (Linux only, no Android for now)
Somewhat working screen rotation support
No more use of swap files! We use compressed main memory now!
New friendlier installation using progress bars and dialog boxes
Storage card support in Android -- uses your windows partition
Real-time clock support


https://sourceforge.net/projects/wing-linux/files/

Remember to remove your rootfs.img and rootfs.img.swp files before running this, or nothing will upgrade! You'll lose any settings you may have had.

Enjoy
- d

[oenukr]

Hello.
I have a problem with 0.4pre2. I can not see any APN's in settings and I can not add new APN (it is not saved, after I enter settings).
I have Xda Terra from german o2 and also o2 sim card.

[darkstar62]

Hello.
I have a problem with 0.4pre2. I can not see any APN's in settings and I can not add new APN (it is not saved, after I enter settings).
I have Xda Terra from german o2 and also o2 sim card.

Classic problem...what are you using for your MNC/MCC numbers, and can you supply the output of the command:


chroot /android /system/bin/logcat -b radio


You can get to a console using SSH over a USB cable. If you don't have the right numbers, you won't see the entry in the list.

- d

[oenukr]

Classic problem...what are you using for your MNC/MCC numbers
I used numbers found in internet:
MCC - 262
MNC - 07

and can you supply the output of the command
see attachment

[darkstar62]

I used numbers found in internet:
MCC - 262
MNC - 07


see attachment

Hmm..hard to tell from the logs. It'd be better if you could get the logs right after a fresh boot.

When you entered the info, did you make sure to do Menu -> Save instead of just hitting the back button? Gotta do that, otherwise it won't save.

- d

[N3xt2N0N3]

How is this going my Wing died RIP T-Mobile Wing. You guys mad huge advancements with this. Good JoB!!

EDIT: Is there anything that needs to be updated on the first page?

[darkstar62]

How is this going my Wing died RIP T-Mobile Wing. You guys mad huge advancements with this. Good JoB!!

EDIT: Is there anything that needs to be updated on the first page?

I don't think so. Maybe add something about the wiki and a blurb about it all, but it's up to you.

- d

[N3xt2N0N3]

I don't think so. Maybe add something about the wiki and a blurb about it all, but it's up to you.

- d

ok cool. your doing an amazing job.

[moneyslap03]

Thanks for the update its looking great but how would i be able to access the android market as its not apart of the Firmware

[darkstar62]

Thanks for the update its looking great but how would i be able to access the android market as its not apart of the Firmware

The market app isn't open source, so it isn't distributed as part of the android source code. I think the only way you'll be able to make any use of it is if you find it somewhere online and install it. It not being open source means I can't distribute it, so I think that's your best bet.

It might need the google login service too, which I have yet to figure out how to get working.

- d

[DrE_braxx]

Anyone have any idea as to when this project will be complete, or if it is near completion :o?

[darkstar62]

Anyone have any idea as to when this project will be complete, or if it is near completion :o?

Check out the status page on the wiki for the latest on features:

http://sourceforge.net/apps/trac/wing-linux/wiki/Status

As for when we'll be complete...whenever we complete. :) Development is done on a volunteer basis on spare time, so the more help I get with this, the faster we can go.

- d

[DrE_braxx]

Check out the status page on the wiki for the latest on features:

http://sourceforge.net/apps/trac/wing-linux/wiki/Status

As for when we'll be complete...whenever we complete. :) Development is done on a volunteer basis on spare time, so the more help I get with this, the faster we can go.

- d
Wow so you guys have really gotten far :D!! w00p w00p, is it possible for the android to be umm.. whats the word...e.e idk but w/e into an NBH file :o? or is it always going to have to be booted from the phone and be a temporary image :S

EDIT: How far are you guys from enabling service, me wanna call n text! o.o

Edit(again): disregard that question lol.. but good luck on getting the rest of it to work ^.^

[darkstar62]

Wow so you guys have really gotten far :D!! w00p w00p, is it possible for the android to be umm.. whats the word...e.e idk but w/e into an NBH file :o? or is it always going to have to be booted from the phone and be a temporary image :S

Not sure about flashing, but there's EOL, which is a boot loader for booting off storage card. In the future, we could possibly use that to bypass booting into WM and boot straight to Linux/Android. I think currently it doesn't support SDHC cards though, so we'd be limited to 2gb cards. However, we could have Android/Linux taking up the entire card and all would be good.

I think there is preliminary support for the disk-on-chip flash, but I haven't tested it yet (kinda worried to, in case something bad happens). If we have access to that, there's really nothing stopping us from loading something like uboot or redboot as an on-flash bootloader to get into Linux directly. Then we could package that up as an NBH file for flashing.

We've got a ways to go before we're ready for that though, unless someone wants to take up work on that.

- d

[ivanmmj]

We could even (as a first step) set up a completely stripped ROM (like TOTALLY stripped) that automatically boots it while booting. (That is until we can get any of the other options you mentioned set up.) But then we'd have to have access to the main storage. And we'd need to let Android know to create it's files in the writable storage partition.

[darkstar62]

We could even (as a first step) set up a completely stripped ROM (like TOTALLY stripped) that automatically boots it while booting. (That is until we can get any of the other options you mentioned set up.) But then we'd have to have access to the main storage. And we'd need to let Android know to create it's files in the writable storage partition.

Getting Android to be able to write to the storage is easy -- in fact, it should work without modification right now. We'd need to add some redirection in the apps directory to allow storing apps to storage card, but that's easy enough.

Lemme find out more about the DoC support we have from the linwizard kernel -- it may not be ready to use yet.

UPDATE: Just talked with ali1234 -- the DoC driver can presently read the entire flash, but we can't mount the filesystem or write to it yet, so we'll have to wait a bit for that.

- d

[illconcepts]

Wow great work! It runs smooth! I don't think all the apps are showing up for me though (email mainly) how do i go about installing new apps? Sorry if its already been asked.

[N3xt2N0N3]

The market app isn't open source, so it isn't distributed as part of the android source code. I think the only way you'll be able to make any use of it is if you find it somewhere online and install it. It not being open source means I can't distribute it, so I think that's your best bet.

It might need the google login service too, which I have yet to figure out how to get working.

- d

Yes you are required to login your gmail account to use the android market. I can also supply you the apk of market if you want it. I also have youtube gmail etc. whatever you need. Just PM me darkstar.

I could supply the market

[neoobs]

you can't just add the market and other apks... you need to build it with those integrated because of the login service. Otherwise they just forceclose because the login libraries are missing.

[DrE_braxx]

Pardon me aswell if this has already been asked, but how do i get the GSM to work, i don't have any service, and on top of that my storage card isn't showing up.
(lucky person up there his runs smoothly, meanwhile mine runs slow at times.)

And if this has any rellivancy to my question and can help you answer it, i have a 4GB sd card :l..

EDIT: Gmail login thingamabob can go to h*ll -.-....

[ivanmmj]

you can't just add the market and other apks... you need to build it with those integrated because of the login service. Otherwise they just forceclose because the login libraries are missing.
We, G1 owners, get ROMs that are build from the source code that have the login service and the market so it's done, but I'm not sure what exactly the insert into the ROM. (What libraries and such.) We should contact Cyanogen from the Dream android development forum. He would know.

[neoobs]

The repo has changed since I last looked at it. There is a googlelogin service folder now. Maybe this is what works... I can talk to cyn or a couple others.

[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.

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.

Lemme know how it works!

- d

[aerovolce]

Awesome work! But it's not working too well for me.

It boots up fine and I get all the way to the home screen. But the touchscreen doesn't seem to work. I have to navigate using the wing's hardware buttons. Touching the screen would result in unselecting (ex.If Artist was selected in the Music section, tapping the Albums would result in Artist being unselected. If I opened the Menu in the homescreen to add stuff, the menu would just close.)

Also, how come it starts out in landscape mode? It's really weird, especially because the Wing's keyboard is on the otherside. And is the sleep button mapped to the end call button? Because pressing that causes the Wing to go into command prompt with "android_power_suspend" printed on the screen. Though pressing it again will allow me to get back to Android.

Besides that, it seems very quick and responsive. Great improvement over the last build I tried. Keep up the mind blowing work!

[darkstar62]

Awesome work! But it's not working too well for me.

It boots up fine and I get all the way to the home screen. But the touchscreen doesn't seem to work. I have to navigate using the wing's hardware buttons. Touching the screen would result in unselecting (ex.If Artist was selected in the Music section, tapping the Albums would result in Artist being unselected. If I opened the Menu in the homescreen to add stuff, the menu would just close.)

Also, how come it starts out in landscape mode? It's really weird, especially because the Wing's keyboard is on the otherside. And is the sleep button mapped to the end call button? Because pressing that causes the Wing to go into command prompt with "android_power_suspend" printed on the screen. Though pressing it again will allow me to get back to Android.

Besides that, it seems very quick and responsive. Great improvement over the last build I tried. Keep up the mind blowing work!

When you installed, did you delete your rootfs.img file from /Storage Card/linux? Upon first boot you should have gotten a touchscreen calibration view just before it starts android. If you didn't get that, try removing rootfs.img and starting it again.

The touchscreen driver for 0.4pre3 changed so that it requires ts_calibrate data to operate correctly. This was so we could get as many different touchscreens working as possible with their own unique calibration. Without any calibration at all, the driver reports raw events, and Android doesn't understand that.

I think default behavior for the End button is to go into suspend. You can change that through the Spare Parts app to just take you home, or do nothing. It does actually work to end calls too.

As for the starting in landscape mode, I think that has to do with the lid switch initial position in the kernel. Gotta figure that one out -- sliding the keyboard out and back in should fix it.

- d

[ivanmmj]

I had the same issue but it may have been that the first calibration point got pushed by me accidently before I realized that it was asking for a calibration point. I'll try again today.

[aerovolce]

Ah! Well I saw multiple rootfs and I just deleted one thinking that the other one was supposed to stay. I guess I was wrong. So i deleted everything and decided to go for a fresh install and it worked like a charm!

BTW, is there a way to turn off the emulator without restarting the whole phone?

Thanks again.

[ivanmmj]

BTW, is there a way to turn off the emulator without restarting the whole phone?

Thanks again.
No, since it's not an emulator. It literally kicks Windows Mobile out of RAM.

[aerovolce]

No, since it's not an emulator. It literally kicks Windows Mobile out of RAM.

oooh, my bad. Thanks for the clear up bro. I swear, you're everywhere. Especially when someone is needed.

[ajige]

Great work!

It's amazing how far it's come. Yesterday, I could send and receive SMS under Android on my Wing:). It was interesting though that these messages didn't show up when I rebooted into Windows mobile, but I guess that's because Android takes over completely when it's running.
Interesting that you can call out and you can hear the other person, but the person can't hear you! Also I guess it can't get incoming calls?
It will be great when the phone and internet works too.

Keep up the good work! Thanks!

[DrE_braxx]

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.

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.

Lemme know how it works!

- d

So all the other cab files need to just be deleted, or just ignore them?

Edit:I just love how when you call someone they can hear you but you can't hear them LMFAO, and wooo the screen goes into landscape mode when you flip out your keyboard lovley lovley ^^

[darkstar62]

So all the other cab files need to just be deleted, or just ignore them?

Edit:I just love how when you call someone they can hear you but you can't hear them LMFAO, and wooo the screen goes into landscape mode when you flip out your keyboard lovley lovley ^^

yeah, the cab files that don't apply to the herald should just be ignored -- they contain default.txt files for the other platforms.

- d

[DrE_braxx]

yeah, the cab files that don't apply to the herald should just be ignored -- they contain default.txt files for the other platforms.

- d



I just can't wait untill you can actually hear the person that you are talking to on the phone lol XD just keep up the good work :)

[EmilianM]

and wooo the screen goes into landscape mode when you flip out your keyboard lovley lovley ^^

Darkstar62..this is not happening on HTC Wizard...do we have to modify some file somewhere ?

[marek1]

Hi Guys,

nice work with the 0.43 build works very well. Well done. Keep working on it.
How can I configure the connection that Internet Browser will find the connection settings ?


Just to know what doesnt work:

The HW keyboard rotation doesnt work properly in some applications
ring melody cant be configured
Calendar doesn't work
File browser will be nice to have it
Cant view which mobile operator I am using

Wifi doesnt work
Camera doesnt work
cant view SDcard

[ivanmmj]

Not even the G1 has a file browser. :p You have to download a third party app for it. But you know what? I don't miss having one. For some reason, I don't need it like I did with my Wing. :p

[marek1]

1.How can I configure the connection that Internet Browser will find the connection settings ?

2. How can I know which mobile provider phone uses ?

[enatefox]

Hey, I just got a Wing given to me. I've been working with Android on Kaiser/Vogue for over a year. Forgive me for not having read every post on this thread but I'm not sure how far you've been able to get-- I just see that it kinda sorta boots.

Seems this thread is dead. I will see what I can come up with as I think this phone will be almost the same for me. I'll keep you updated.

[kingsteve032]

This still being worked on?

[darkstar62]

This still being worked on?

This thread may be slowing, but our project is still under heavy development. Some highlights coming soon:

Android Eclair is undergoing testing. Currently it boots, but is slow. Optimization is needed before we can release it.

Audio support is very close to ready. Only a few odds and ends remain before the driver is 100%.

With help from Google, we'll soon have working GSM audio routing, enabling full two-way audio during calls without having to boot in during a call.


It may not seem it, but we're very active on #wing-linux, and there's a lot coming. Stay tuned :)

- d

[numaverick]

It's great!...

thanks..

[aerovolce]

Yay! Thank you. I was worried for a second there haha. Thank you guys for all the hard work :) looking forward to it.

[CheeseDave]

yEp I'm waiting for it too.
Will be there any ways to run Windows Mobile games on it?

[darkstar62]

yEp I'm waiting for it too.
Will be there any ways to run Windows Mobile games on it?

Yes -- reboot your phone :)

Our Android installation doesn't replace Windows Mobile -- it runs completely from storage card. So in effect, you can dual boot (though you need to boot Android from WM; you can't boot directly in yet).

- d

[numaverick]

Thanks for all!!

may be used Gen.Y dualboot?...

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

but says: "solution for Windows Mobile devices with XDANDROID"

[darkstar62]

Thanks for all!!

may be used Gen.Y dualboot?...

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

but says: "solution for Windows Mobile devices with XDANDROID"

Hmm, there's a VERY good shot that would work for us. It requires haret.exe to exist either at the root of the storage card or in /Storage Card/Android, so all we'd need to do to use it is rename the existing /Storage Card/linux directory to Android and set the appropriate registry key for the bootloader.

I might just test this later this afternoon. :)

- d

EDIT: Hmm...Simply renaming the linux folder to Android would make our boot scripts die a horrible death. We'd need to create a new Android folder instead and copy herat.exe, zImage, initramfs.cpio.gz, and default.txt in there to make it work. Maybe I can contact the author of it and have him add support for /linux in addition to / and /Android... :)

[djnek]

this is amazing i jut got a Wing and I can say this is just amazing, can't wait till we got 2 way communication...

[rshabou]

audio support yet?

[numaverick]

hey darkstar62

"XDAndroid For TouchPro2 Wifi Working"...

There is some progress t.mo wing?

thanks in advance..

[darkstar62]

Slow progress. Many (most) of the developers, myself included, have become rather busy lately and haven't had a chance to work much. Audio support is in the works, but there's still some bugs to iron out. More developers on the project can always help, especially in the Android parts of things, but we need people willing and able to dissect the hardware in their phones too.

Until and unless we have more developers or time, things will probably remain slow for a while. But fear not, we're still going.

- d

[N3xt2N0N3]

If anyone has any input and are willing to help please let us know.

[numaverick]

I can be a betatester : )

you can apply themes / skin?...

[daniel_costa_rj]

The linux android for Wing is nice, but very slowly and must of the keys doesn't work. I liked android linux sistem, but with those conditions I can't use all days. :(

But thank you DEVs for your hard work. :)