yashsingh1/xdaforums huggingface dataset:
[Wing, P4350 ROM development] Kuuf:
Ow that's nice!

Never seen such emulator though, my Herald is atm alwo my main phone.
[Wing, P4350 ROM development] Kuuf:
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.
[Wing, P4350 ROM development] darkstar62:
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
[Wing, P4350 ROM development] Fenopy:
I couldnt get it to reboot under lvl3 either... :'(
[Wing, P4350 ROM development] 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
[Wing, P4350 ROM development] Kuuf:
Same problem here
[Wing, P4350 ROM development] Kuuf:
Freenode?

Have to say, I'm from Belgium -> its almost five in the afternoon here.

Finding good moments might be difficult
[Wing, P4350 ROM development] darkstar62:
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
[Wing, P4350 ROM development] darkstar62:
Alright, I'll keep poking.

Any git experts out there?

- d
[Wing, P4350 ROM development] neoobs:
Whatcha need git for? Android source?
[Wing, P4350 ROM development] Kuuf:
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.
[Wing, P4350 ROM development] darkstar62:
Sweet, #wing-linux is live! Thanks Kuuf. Come join us!
[Wing, P4350 ROM development] 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.
[Wing, P4350 ROM development] Kernel Jag:
what about git?

i've a significant amount of experience with git. what do you need??
[Wing, P4350 ROM development] Kernel Jag:
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 :)
[Wing, P4350 ROM development] darkstar62:
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
[Wing, P4350 ROM development] 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
[Wing, P4350 ROM development] darkstar62:
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
[Wing, P4350 ROM development] ivanmmj:
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...)
[Wing, P4350 ROM development] darkstar62:
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
[Wing, P4350 ROM development] ivanmmj:
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.
[Wing, P4350 ROM development] darkstar62:
Excellent! We're making progress. Maybe we can close this whitescreen issue once and for all for the 0.3 release.

- d
[Wing, P4350 ROM development] ivanmmj:
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.
[Wing, P4350 ROM development] 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
[Wing, P4350 ROM development] darkstar62:
Wing Linux 0.3pre2 Out for Testing

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
[Wing, P4350 ROM development] 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 ;)
[Wing, P4350 ROM development] Kuuf:
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.
[Wing, P4350 ROM development] 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 ;)
[Wing, P4350 ROM development] ivanmmj:
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.
[Wing, P4350 ROM development] darkstar62:
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
[Wing, P4350 ROM development] Kernel Jag:
Git crash course

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.
[Wing, P4350 ROM development] 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!
[Wing, P4350 ROM development] darkstar62:
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
[Wing, P4350 ROM development] 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.
[Wing, P4350 ROM development] darkstar62:
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
[Wing, P4350 ROM development] 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?? :(
[Wing, P4350 ROM development] darkstar62:
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
[Wing, P4350 ROM development] fdez.romero:
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:
[Wing, P4350 ROM development] Kuuf:
-- nevermind, i quoted an old post .. --
[Wing, P4350 ROM development] darkstar62:
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
[Wing, P4350 ROM development] 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
[Wing, P4350 ROM development] 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
[Wing, P4350 ROM development] 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
[Wing, P4350 ROM development] Kernel Jag:
Wow..now that's quite a progress!

Cheers mate!