yashsingh1/xdaforums huggingface dataset:
[Touch Diamond, MDA Compact IV ROM Development] phhusson:
I made a quick initramfs to test WiFi, it also needs my kernel (because of problems with kernel versions) so here it is:

http://husson.hd.free.fr/angstrom-bt+wifi.cpio.gz this is the initramfs

http://husson.hd.free.fr/zImage-27-09-2009 this is the kernel

These files are hosted on my broadband connection, so please someone mirror it :)

So this initramfs will load the calibration file from the NAND, then load the wifi driver, load the bluetooth driver, and will finally print netwok scan for wifi then bluetooth. wifi scan will flood your screen.... you won't be able to see more than 2 ESSID, but you'll be able to see either it works or not.

Please note that you have to turn wifi on in Windows Mobile before starting haret !

Also, the start will be amazingly slow, something like one minute with messages "looping". If you get looped CRC errors, it's most likely because you haven't turned wifi on in Windows Mobile, so first check it before reporting.

If it works, say what works (bluetooth and/or wifi), and your phone (known to work on diam100, supposed to work on raph100, don't know for others).

If it doesn't work, you can get more informations (typically dmesg), by usb: the initramfs will create a usbnet connection with a 192.168.0.202 IP, the ssh server has empty password for root.

Please note that this kernel gives (almost) total access to NAND, so don't write to /dev/mtd* ! You even should not use any other system than my initramfs (even if i use it successfully on andoir xrom)
[Touch Diamond, MDA Compact IV ROM Development] Willis111:
I added this info to the "Hardware differences/Configurations" section of the xda wiki. I am unable to confirm this or any other settings as I don't have a raph500 so I just tossed it up as ? 2182 ? and questioned out other options the same way. Hopefully no one will get confused, if anyone can confirm this and edit the wiki themselves or even just post here that it's right/wrong it will be updated accordingly by myself or someone else.

I was hoping as well, if anyone (MrPippy please please please) could post their .config for their kernel settings (hopefully for diam500 specific devices). Seem to have a few problems with my .config I think that aren't covered in the howto on the wiki(I'll probably just grab IRC and jump on #htc-linux if I don't get a response in a day or two).
[Touch Diamond, MDA Compact IV ROM Development] imrock:
im getting CRC error even with wifi on in winmo..but superb progress!!! diam140
[Touch Diamond, MDA Compact IV ROM Development] imrock:
can i upload it on megaupload? i dont hv an account there..n all i did was to rename the 1st file to initrd.gz n the zimage n boot up..it started bluetooth n wifi scanning but in the end ggave data CRC error n some more errors difficult to read coz the screen flickers very much due to scanning

did i do anything wrong? i just read wifi n jumped onto try, so eager for wifi to work!!
[Touch Diamond, MDA Compact IV ROM Development] fliggygeek:
Mirroring

I have started an upload space on my server, androiduploads.uberatomic.com, dont abuse it or it will cease to exist.

# FTP Username: android@uberatomic.com

# Password: androiduploads

# FTP Server: ftp.uberatomic.com

# FTP Server Port: 21

# Quota: 500 MB

Shortly there will be a copy of the phhusson files residing here
[Touch Diamond, MDA Compact IV ROM Development] Willis111:
Megaupload

http://www.megaupload.com/?d=A867F612 - cpio.gz

http://www.megaupload.com/?d=9GEHT65U - rar'd zImage (megaupload doesn't seem to accept files without extenstions, just extract like any other rar archive ...)

Edit: Sweet, Wifi is working here. cdma DIAM500. Picked it up on the second card scan.
[Touch Diamond, MDA Compact IV ROM Development] fliggygeek:
Feel free to upload related files to my server, its high bandwidth and low usage atm and ive uploaded the two files.

http://androiduploads.uberatomic.com/angstrom-bt+wifi.cpio.gz

http://androiduploads.uberatomic.com/zImage-27-09-2009
[Touch Diamond, MDA Compact IV ROM Development] tallnerd1985:
Hi Everyone,

So today I decided to whipout and dust off my Touch Pro because I heard that Dzo is starting to help out here with the Diam/Ralp Android porting group. I have been using his Android port for my HTC Vogue that he started over a year ago and been loving it since.

I've tried to read thru this thread about getting it onto my VZW TP which I guess is supposed to be the RALP500 but have had no luch on getting it to bootup. I've downloaded the package from connect-utb and edited the startup.txt to change the MTYPE to 2182 because thats what someone said a couple pages back to do to get it to work but it only shows half a black screen and stays like that for minutes as opposed to my Vogue showing all the modules being loaded up.

If anybody can bring me up to date on what builds work for my phone and what neccesary files I need to download would be greatly appreciated. Sorry but the thread at this point is too long to filter out all the different builds and what model they work for.

Thanks,

Kenny
[Touch Diamond, MDA Compact IV ROM Development] ElCondor:
I am also getting that error, but on DIAM100.

Very sad...
[Touch Diamond, MDA Compact IV ROM Development] suksanto:
Could you guys be kind enough to tell me How do you start the initramfs, do I change the file name to initramfs.gz ?
[Touch Diamond, MDA Compact IV ROM Development] mixxy:
i tried the 2 files but my terminal keeps looping "waiting for SD card"

any ideas?

PS. Im using a DIAM500 with the ZIMAGE u posted, hope im doing it right, cuz when i go back to mr.pippy's old one it boots fine....not sure what im doing wrong
[Touch Diamond, MDA Compact IV ROM Development] chemical1979:
Hey phhusson,

Thanks for your work. I enabled BT and WIFI on WM, booted your kernel and initrd.gz and found that it loops with the CRC errors for about 5-7 Minutes and then stops (but doesn't freeze).

mmc0: Data CRC error
msmsdcc_data_err: opcode 0x00000035
msmsdcc_data_err: blksz 4, blocks 1
wl1251: ERROR sdio write failed (-84)
[Touch Diamond, MDA Compact IV ROM Development] phhusson:
Have you also changed the initramfs (half falsely named initrd in haret) ?

This zImage isn't meant to work with other with other initramfs (even if it should), and anyway, wifi code is in the initramfs, not the zImage.

Also try various wifi configuration on windows mobile:

I think you have to be either connected or searching WiFi (and not idling disconnected, it disables wifi most of the time).

If connected you also might have to set power mode to high performance, and maybe even do some download meanwhile.

I've done my tries with wifi in search mode. (on my WM rom, wifi logo is moving, while most of the time it's red when no search nor connection)

Also as soon as you get those message, it will fail, there is no need to wait for the end of this. But be careful, there are a lot of other errors that might happen, which are normals (I made it quick and really dirty)

If it still doesn't work, look at the startup.txt, there is a comment to slow down the SD controler, try it, set 150000 Hz as frequency, this might help. If this actually helps, try increasing frequency until it won't work, and report the last working frequency. See http://git.linuxtogo.org/?p=groups/...90ed051bb0bab540;hb=refs/heads/htc-msm-2.6.27 around line 120 to know which frequencies are supported, you can set it higher than the value, it will fallback to the nearest lowest frequency available.

Great, CDMA was the phone i thaught would be the worst one to get working :)

PS: I confirm that if wifi is on, but not searching nor connected, it won't work. But don't worry about it, even if we can't stop the wifi chip ATM, the radio can still be stopped, so there won't be big battery problems. And anyway cr2 rocks, so he'll find the correct (de)init code :-)
[Touch Diamond, MDA Compact IV ROM Development] babijoee:
Are you guys running this in Android or Angstrom?

If Angstrom could someone link me to a page where i can read up, setup and download Angstrom?

Tried this in Android by replacing initrd.gz and zImage and Haret says

"Image too large (1462396 + 27726336) - Largest size is 25165824 :confused:
[Touch Diamond, MDA Compact IV ROM Development] phhusson:
It's angstrom, but it's all in the initramfs, you don't need anything else.

Your message states a 27MB file, the initramfs is 13MB, you must have done something wrong, maybe you extracted the initramfs while you should not, initramfs IS a gz file ! do NOT "unzip" it. Just unrar it if you used the rar one.
[Touch Diamond, MDA Compact IV ROM Development] babijoee:
Thanks for the quick reply. Got it booting

How long would you usually wait for the wlan drivers to loop?

It started around 80.xxxxxx and now has jumped to stopped at 430.xxxxxx.

Been booting screen for about 5 mins now. Report back in 20 minutes.
[Touch Diamond, MDA Compact IV ROM Development] Nakebod:
Negative for me, on my Diam100, using xRom's Android, I can't use the hardware buttons, thus not unlock the device @ boot.

I had this problem before with a different zImage, so maybe that the WIFI/BT is working, but I can't test it :(

But it you/someone has another/better Android version, please tell :P
[Touch Diamond, MDA Compact IV ROM Development] suksanto:
My DIAM100, I tried both WIFI connected, WIFI searching in WM, still get looping with error

mmc0: Data CRC error

msmsdcc_data_err: opcode 0x00000035

msmsdcc_data_err: blksz 4, blocks 1

wl1251: ERROR sdio write failed (-84)
[Touch Diamond, MDA Compact IV ROM Development] chemical1979:
Before these messages loop, there is some other interesting stuff scrolling through the screen.

One line definately states BUG: sleeping function called from invalid context in line kernel/mutex.c:88

Btw, I forgot to mention that I'm on a DIAM300.

I looked at the code clock-wince.c and found the clocks at line 122-125 (12, 19.2, 24 and 32MHz). I tried the slowest (msm_sdcc.msmsdcc_fmax=12000000) as kernel parameter but there was no change.

After using 150000 as clock the errors started to get different. Lots of command timeouts during startup, and the loop now looks different:

wl1251: ERROR sdio write failed (-110)
mmc0: Command timeout

I'll start increasing the clock until I see some other behaviour. :)
[Touch Diamond, MDA Compact IV ROM Development] babijoee:
Success!

Using connect-utb latest raph build and changing frequency to 150000 I saw the wlan drivers successfully booted.

Unsure about bluetooth though.

Still waiting for Angstrom to boot :(
[Touch Diamond, MDA Compact IV ROM Development] druidu:
It's druidu (actually, it used to be just druid but it's already taken almost everywhere) :D

Well, the linux kernel boots pretty much all the way through, as you can see from NetRipper's photos, "Freeing init memory: 108K" means that the kernel is alive and kicking, just that a lot of the drivers are not working properly or not working at all. Framebuffer is functional although most likely the driver couldn't power up the lcd if we were not "hijacking" the device from windows. I suspect most of the drivers don't work because of the smd code (shared memory communication interface).

I can't work full time on this because I have work to take care of, but I am eager to get Android on my Diamond.

On-screen keyboard and stuff like that will be a breeze. Problem is with lack of documentation for all the hardware inside. Once we're done with the drivers, everything else is open source and will be much easier.
[Touch Diamond, MDA Compact IV ROM Development] computerguru:
is it ready yet? :-p hahaha...had to say it.

hey...if anyone needs help with debugging the kernel. i plan on loading the dev tools this weekend, and i bought my touch diamond on thursday (in fact, i'm using it to post this reply right now...lol)

i havent done much kernel work for a few years...but will help out with whatever coding or testing you need done :-)
[Touch Diamond, MDA Compact IV ROM Development] NikPraskaton:
Thumbs Up for everyone trying to get this runnin!! Cant wait.
[Touch Diamond, MDA Compact IV ROM Development] fumanchu182:
Druidi I offered my help before with the Kernel before, if you want you can catch me on Freenode usually and we can discuss some of the drivers that need to change.
[Touch Diamond, MDA Compact IV ROM Development] dta1974:
Hi guys

I got my G1 3 days ago and I love it so far,the browser is faster than the version of opera that the Diamond has.The touchscreen is so smooth,it has nothing to do with the Diamond.

The system itself runs really well,it's not as sluggish as WM,still needs more software but little by little is being released.

After year with WM I have to say that Android rocks,so it would be a great idea for your Diamonds.

See ya.
[Touch Diamond, MDA Compact IV ROM Development] Gluck:
druidu

I have the Touch Pro.

And your zImage(with Tux) ends with different messages then on wiki images.

After "Freeing init memory 108K"

next message repeats 9 times:

{

mmc0: Command timeout (c3c4fed4 c3cff0c 0000 0000 00000000)

}

after each aprox. ~120 sec:

{

INFO:task rpcrouter:13 blocked for more than 120 seconds"

"echo 0 > /proc/sys/kernel/hung_tusk_timeout_secs" disables this message

... skipped ...

}

Can help with test on Touch Pro if you need.
[Touch Diamond, MDA Compact IV ROM Development] liamhere:
can't you dunp the rom?
[Touch Diamond, MDA Compact IV ROM Development] mp.goldfinger:
Might be helpful

http://www.spinics.net/lists/arm-kernel/msg47464.html

I think this might be helpfull I havnt put my time on android but will try things when I have time
[Touch Diamond, MDA Compact IV ROM Development] computerguru:
I also bought a G1...had it shipped overnight, but it was DOA. The idiots at T-Mobile left it on in the box, and I think they jammed the SIM card in too hard because the pins were causing too much resistance when pushing it in...that it would put a huge scratch on the card.

Plus...it took me an hour to get through their crappy automated telephone system to get to the person I needed to talk to about returning it...and they wanted to temporarily charge me another $179 while the phones were cross-shipped! They wouldn't let me just send them the phone, wait for them to receive it, then ship me the new phone. So, I told them where they could put their G1 (somewhere where the sun don't shine...lol), and I got my touch diamond through Sprint. It makes more sense for me to have the diamond anyways...since I'm a Windows Mobile developer.

So...anyways, if you need any help...you got an eager touch diamond/linux/java geek right here with too much time on his hands...lol.
[Touch Diamond, MDA Compact IV ROM Development] los1223:
Show off! =P

I'm anxious to see this come to life as well. I had a semi-functional version of Android on my Touch, so I got to spend some time with it. From what I got to see it looked petty cool... =) If there's anything I can do to help this along let me know!
[Touch Diamond, MDA Compact IV ROM Development] druidu:
Linux shell + virtual keyboard running on Diamond

Here it is, my latest creation [us at your own risk, but you should be ok :)].

Made a touchscreen driver and a virtual keyboard driver that uses the touchscreen driver. The drivers are a big hack right now: touchscreen IRQ won't fire on Linux, although it shows up in Haret, so the driver has to poll the touchscreen 20 times a second and it writes directly to FB memory so the msm_fb had to be slightly modified to update whole screen every time.

Above link is a linload version of Haret that should work on Diamond (and on Raphael too, but didn't test it). It will start with an early console using the console driver I wrote and will switch to the framebuffer device with tux on it once it is initialized.

Using the virtual keyboard:

1. Don't touch the screen while booting (ignore the errors about usb ethernet)

2. After you entered the shell, tap the screen once (you will get a message saying you entered calibration mode)

3. Tap the red pixel in the upper-left corner of the screen (a message will confirm your selection)

4. Tap the red pixel in the lower-right corner of the screen (a message will confirm your selection)

5. You can draw yellow dots on the screen by tapping and dragging

6. Type by tapping the keys;

Shift/Alt/Ctrl/Caps/SysRq are sticky keys, they work in toggle mode;

Left Shift/Alt/Ctrl reset automatically after tapping a normal key;

Activating Shift shows the alternate chars on each key;

Alt+Sys+KEY is the magic SysRq, see Alt+Sys+h for more info.

Shift+PgU/PgD work for scrolling the framebuffer console (careful that you won't see the keyboard anymore, but the keys are still there and if you click them it will reset the scroll and go back to the bottom, showing the keyboard again).

It's not the most friendly way of input text, but it's still better than writing binary codes using the gpio keys that work by default...

The initrd is NetRipper's build, it has a busybox with lots of stuff in it, and also mounts /proc and /proc/bus/usb filesystems (cat /init to see what it does).

I did want to make a nice screenshot, but I don't have a camera lying around that would produce a reasonably good macro photo, so I'll leave that to the readers :D
[Touch Diamond, MDA Compact IV ROM Development] TripleQ:
In my Rapheal it says booting linux..after that i see some linux lines scrolling..and within a second I see a white screen...tried it a few times...
[Touch Diamond, MDA Compact IV ROM Development] druidu:
That's when the msm_fb should come in, but I guess it doesn't. As I said, didn't test it in Raphael.

Maybe try this one; it's compiled without the early console... might work, but anyway, if it won't you will only see Haret's message "booting linux" and nothing else.
[Touch Diamond, MDA Compact IV ROM Development] NetRipper:
Nice job!

Unluckily on my Raphael it also gives a white screen, and doesn't respond after that.

Pretty neat you got it working for your Diamond though, it's a step in the right direction. :)
[Touch Diamond, MDA Compact IV ROM Development] n.mowberry:
:o

How exciting!! I can't wait until our Diamond is fully featured in linux!
[Touch Diamond, MDA Compact IV ROM Development] TripleQ:
hmm..that one gives my after "booting linux" directly a white screen...no linux after lines like that other one... But thanks anyway, I understand you dont have a raphael too test it :)
[Touch Diamond, MDA Compact IV ROM Development] qetuR:
This makes me soooo excited! :)
[Touch Diamond, MDA Compact IV ROM Development] druidu:
Maybe someone with Diamond can test it, it should work on that. Did I mention you can fingerpaint? :)
[Touch Diamond, MDA Compact IV ROM Development] Pixel du Rezo:
I just try it on my diamond, and it works :

after a lot of errors "gpio_keypad_scan_keys: unmapped key, 4-5 (31-37) changed to 1", I successfully calibrate the screen and enter the console
[Touch Diamond, MDA Compact IV ROM Development] gebruikershaes:
So how does that work? Do I just install the exe or what? And will it affect my WM os? If not I could test it on my Diamond.
[Touch Diamond, MDA Compact IV ROM Development] IceBone:
Sounds good, can't wait til it's integrated into the zImage (or however it works). What about battery life in pure Linux? Is it an issue there as well or is it only in Android?
[Touch Diamond, MDA Compact IV ROM Development] chemical1979:
I found that f=1,5MHz solved the error loop of sdio writes, now I'm on a "htcraphael" login prompt waiting for a login with an Angstrom-ASCII Art above.

The last lines above the login prompt are:

Complete wifi scan:
lo Interface doesn't support scanning.
dummy0 Interface doesn't support scanning.
rmnet0 Interface doesn't support scanning.
rmnet1 Interface doesn't support scanning.
rmnet2 Interface doesn't support scanning.
usb0 Interface doesn't support scanning.

SSID-only wifi scan:
BT scan:
Scanning ...

I would guess there is the wlan-interface missing, so something else doesn't work as expected.

No android. Guess I have to enable that keyboard with the blue dot again, to login as root and do some stuff?
[Touch Diamond, MDA Compact IV ROM Development] ElCondor:
I am finally able to get to this. First I got the known loop of errors, but I tried it another time, and know it works (without setting the frequency)

What's the login pass? I tried 'root' but without any succes.
[Touch Diamond, MDA Compact IV ROM Development] Nakebod:
Ok, tried some more, I got a little bit further then before,

WIFI connected in WM, BT enabled, and I got the "famous" error :+

msmsdcc_data_err: blksz 4, blocks 1

mmc0: Data CRC Error

msmsdcc_data_err: opcode 0x000000035

w112521: Error_sdio write failed (-84)

After the hints from chemical1979 I've added the following parameter in the startup.txt:

msm_sdcc.msmsdcc_fmax=1500000

WIFI

After the boot (But it doesn't load Android's GUI, only the console), I can see it find at least 1 network (Probably more, text scrolls to fast), I'm able to see the neighbors SSID, and below this, I see:

SSID-only wifi scan:

BT scan:

Scanning...

[ Angstrom ascii logo ]

htcraphael login: _

But without keyboard, I can't login, neither can I ping my device.

BT

Searching for new devices from my Windows PC, it is able to find "htcraphael". I can't connect to it, probably because it needs a keypair.
[Touch Diamond, MDA Compact IV ROM Development] Willis111:
rename the initramfs to initrd.gz and rename the cpio.gz to zImage or edit your default/startup.txt and change "initrd.gz" to "initramfs" and "zImage" to cpio.gz

set RAMSIZE 0x08000000
Set ramaddr 0x10000000
set MTYPE 2040
set KERNEL zImage
set initrd initrd.gz

to

set RAMSIZE 0x08000000
Set ramaddr 0x10000000
set MTYPE 2040
set KERNEL cpio.gz
set initrd initramfs

Should work I think(ignore mtype, it's for my diam500 of course).

Is there no module versioning support in these kernels/.config? Possible to download a pre-compiled module and load it on any machine etc ....
[Touch Diamond, MDA Compact IV ROM Development] chemical1979:
For the record, the kernel parameter msm_sdcc.msmsdcc_fmax takes the argument in Hz, so only this works as expected:

msm_sdcc.msmsdcc_fmax=1500000
[Touch Diamond, MDA Compact IV ROM Development] Nakebod:
Strange, it worked with 1,5Mhz in it :confused:

Anyway, if it is supposed to contain 1500000, I'll edit my message to prevent confusion.

Sometimes the result varies from boot to boot :+

Now I got:

Complete wifi scan:

lo Interface doesn't support scanning.

dummy0 Interface doesn't support scanning.

rmnet0 Interface doesn't support scanning.

rmnet1 Interface doesn't support scanning.

rmnet2 Interface doesn't support scanning.

usb0 Interface doesn't support scanning.

SSID-only wifi scan:

BT scan:

Scanning ...

<hardware addess> computername

And again no Android GUI, so I can't really test if BT works, except it can be detected from my computer.

Edit, is there an easier way for the logs/debug? Anyway, I caught some messages:

Fatal error could not open /lib/.. * ... /modules.dep

Can not load firmware file (:?)

Cannot find BTS file /lib/firmware/TIInit_5.3.53.bts

Probably not the exact messages, but it could be a hint to something.
[Touch Diamond, MDA Compact IV ROM Development] ElCondor:
You can do this by setting msmvkeyb_toggle=on

But what login pass should you use then? the wpa key?

Guys, the frequency isn't important. The only config I made is enabling the keyboard, which is not related to any wifi actions. After 3 or 4 boots, it worked.

Edit: I tried the network name (SpeedTouchC772BE) for the htcraphael login. After that, I have to type in the password. I tried to type the wpa key but if I type something, it doesn't appear. So you can't see what you're typing.
[Touch Diamond, MDA Compact IV ROM Development] chemical1979:
As phhusson post states, the root password is empty. If you enable the msmvkeyb_toggle (hide/on) you can use "root" on the login prompt, and after enter you're on the root prompt.

root@htcraphael:~#

However, as I already guessed in my last post, something is missing here. ifconfig only lists lo and usb0 as network interfaces, there is no wlan0 or sth.

I'm checking dmesg output right now to find a clue..