yashsingh1/xdaforums huggingface dataset:
[Touch Diamond, MDA Compact IV ROM Development] NetRipper:
You're right. That's a mistake on my side ;) I updated board-htcraphael.c to include the "ether" function. The hsusb waits forever for the ether function to load before continuing to init usb.

lavender.t, were you able to use usb at all? I think it should work, but I haven't been successful yet. I especially want ether to work ;)

I'll update the git tonight.
[Touch Diamond, MDA Compact IV ROM Development] skiwithpete:
Linux hits iphone

http://www.engadget.com/2008/11/28/linux-hits-the-iphone/
[Touch Diamond, MDA Compact IV ROM Development] lavender.t:
ether now works too

right that i didnt really check the ether ... it still didnt work after adding the _ETHER=y option.

so i dug a little deeper at night after the crazy black friday shopping the whole day. the nice google developer put an important one-liner comment in ether.c:

* Implements the "cdc_subset" bulk-only protocol supported by Linux.

which hinted me looking into the cdc_subset.c in the usbnet code. very interestingly the cdc_subset devices are all matched by the vendor-id/product-id pair. obviously the Halibut vendor/product ids wouldnt match at all. to make it worse, ether.c also gives the device a CDC subclass of 0x0a (MDLM), which annoys the usbnet complaining about invalid MDLM descriptor, blah, blah.

(i just cant help wondering how the smart google developers made this work at all in their offices. i guess they'd probably built a special linux kernel).

so i made the following diffs and the USB ether worked perfectly with my debian box. just one thing odd that the diamond always creates 2 USB devices so the host will detect usb0 and usb1 two interfaces. i'm not an expert in the USB stuff so dont have the time to track it now. at least in my debian box if i assign a 192.168.0/24 ip addr to usb1 it will be able to ping and telnet 192.168.0.206 (with your almighty initrd, of course :) ).

diff --git a/arch/arm/configs/htcdiamond_defconfig b/arch/arm/configs/htcdiamond_defconfig
index ebe3131..23d5f09 100644
--- a/arch/arm/configs/htcdiamond_defconfig
+++ b/arch/arm/configs/htcdiamond_defconfig
@@ -845,7 +845,7 @@ CONFIG_USB_FUNCTION_ADB=y
# CONFIG_USB_FUNCTION_UMS is not set
CONFIG_USB_FUNCTION_MASS_STORAGE=y
CONFIG_USB_FUNCTION_DIAG=y
-# CONFIG_USB_FUNCTION_ETHER is not set
+CONFIG_USB_FUNCTION_ETHER=y
CONFIG_MMC=y
# CONFIG_MMC_DEBUG is not set
CONFIG_MMC_UNSAFE_RESUME=y
diff --git a/arch/arm/mach-msm/board-htcraphael.c b/arch/arm/mach-msm/board-htcraphael.c
index dc31af7..7015fc3 100644
--- a/arch/arm/mach-msm/board-htcraphael.c
+++ b/arch/arm/mach-msm/board-htcraphael.c
@@ -183,10 +183,10 @@ static char *halibut_usb_functions[] = {
// orig product_id 0xd00d
static struct msm_hsusb_platform_data msm_hsusb_pdata = {
.phy_init_seq = halibut_phy_init_seq,
- .vendor_id = 0x18d1,
- .product_id = 0xd00d,
+ .vendor_id = 0x049F,
+ .product_id = 0x505A,
.version = 0x0100,
- .product_name = "Halibut",
+ .product_name = "MSM USB",
.functions = halibut_usb_functions,
.num_functions = ARRAY_SIZE(halibut_usb_functions),
};
diff --git a/drivers/usb/function/ether.c b/drivers/usb/function/ether.c
index f31032e..55be4ea 100644
--- a/drivers/usb/function/ether.c
+++ b/drivers/usb/function/ether.c
@@ -207,7 +207,7 @@ static struct usb_function usb_func_ether = {
.name = "ether",

.ifc_class = 0x02,
- .ifc_subclass = 0x0a,
+ .ifc_subclass = 0x00,
.ifc_protocol = 0x00,

.ifc_name = "ether",

i guess it would feel much better to be able to telnet to the diamond. :D

cheers !

- lt
[Touch Diamond, MDA Compact IV ROM Development] NetRipper:
Sweet! Good job. I've been fiddling around with vendor/product and ifc classes as well but didn't get any further. Probably been using different values. I finally gave up. :)

Glad you got it working. I'm busy this weekend but I'm going to try right after ;)
[Touch Diamond, MDA Compact IV ROM Development] toer:
I tried the patch and i got a working usb network to my raphael :)

Nice work lavender.t
[Touch Diamond, MDA Compact IV ROM Development] Mr.Wuan:
Android

Will this work on da touch pro?
[Touch Diamond, MDA Compact IV ROM Development] AcNette:
read a bit and you'll find out the "Raphael" IS the Touch Pro...
[Touch Diamond, MDA Compact IV ROM Development] jamesd256:
Guys, I'm sitting here with a G1 in one hand and the raphael in the other (i'm typing with my c*ck).

If I can do anything to help, holla.
[Touch Diamond, MDA Compact IV ROM Development] Mr.Wuan:
Android

oh Okay I didn't know that. but anyway I downloaded everything is said 2 my phone and I get and error. what am I doing wrong? can sumbody please help thanks
[Touch Diamond, MDA Compact IV ROM Development] dcordes:
I pushed the usb ether stuff
[Touch Diamond, MDA Compact IV ROM Development] kimhoon:
Hi all,

first of all great work.. :)

Is there any progress on the sd driver :) ??
[Touch Diamond, MDA Compact IV ROM Development] Riel:
You are not serious are you?

Android and linux does not seem of any good for you know.
[Touch Diamond, MDA Compact IV ROM Development] jamesd256:
You need to re-write the kernel from scratch, then reverse engineer all the drivers.

Good luck.
[Touch Diamond, MDA Compact IV ROM Development] seanmd:
i enginered backwards drivers right i think but how to compiled kernel??
[Touch Diamond, MDA Compact IV ROM Development] jamesd256:
Do it in your head, then write down the 1's and 0's
[Touch Diamond, MDA Compact IV ROM Development] dzign-it:
Dude - Your a prick.

There some people with genuine questions, and lets face it, why on earth would people wanna spend 5 hours reading through the entire thread. A quick post to ask for help does not do any harm, you dont HAVE to reply if you feel someone is been a n00b and not reading up on things.

I hate replies like "read the thread dumbass" , especially when its a large thread, with bits of info all over, its pretty hard for people to piece together where the devs are at with progress.

So, in this case, the WIKI is ideal for keeping up with latests developments, but when it goes un-updated for some time maybe there HAS been progress, but un-reported.

So to the ass i quoted, no need to be an ass to people interested in the topic, iv seen your posts and you generally are, an ass. Did i say ass enough? Ass.
[Touch Diamond, MDA Compact IV ROM Development] NetRipper:
Please read the wiki. In short, download this file, copy it to your memory card and execute it from your pda (not on your pc). Note that it's experimental and many things won't work (again, see wiki).

(ps. you don't have to compile the kernel yourself)
[Touch Diamond, MDA Compact IV ROM Development] udayrulz:
Great work guys !

I have a very limited knowledge in this area .. but still PM me if you need help or anything .
[Touch Diamond, MDA Compact IV ROM Development] jamesd256:
Love you too :)

I'm not the guy you claim. I don't slam noobs. I even help out from time to time.

Sorry my sarcasm hurt your feelings, but I really don't know how you read my posts and got so pissed. :(

BTW, you mis-quoted me there. I have never once said 'read the thread dumbass'. In fact I've never once called people names online. Life's too short.

Have a nice day...
[Touch Diamond, MDA Compact IV ROM Development] Riel:
I agree. You can also read that that user doesn't have any knowledge at all of things, just save him and yourself from it. I know he doesn't even know what to expect! Let him do something else?
[Touch Diamond, MDA Compact IV ROM Development] lennysh:
:confused:Has this thread gotten off-topic or what? All I want to see is Android on my Alltel (CDMA) Touch Pro. It's like the sprint version, and the EXE in the WiKi will not load all the way. So, we need to get back on topic, and settle this thing once and for all!

Have a nice day to all!:p
[Touch Diamond, MDA Compact IV ROM Development] pixelwix:
i agree where is the exe that works on the RAPH800 both exe's on the wiki only work for the RAPH100 and RAPH101 works great on my wife's fuze. I cant for the life of me get to boot on my sprint pro...
[Touch Diamond, MDA Compact IV ROM Development] dcordes:
you need the raph800 mddi and resolution patch posted earlier in this thread. we should put it in the git. NetRipper did you try finding a solution to make it nicer and not interfer with raph100 and diam100 ? is there any interference? if not we should just push it as is.

I think nobody find a solution for the color problem though
[Touch Diamond, MDA Compact IV ROM Development] slovoflud:
Asstastic!
[Touch Diamond, MDA Compact IV ROM Development] etiger13:
i dont have time to read this whole thread right now, but i will.

I wanted to ask the community what they think of having info for this project posted at http://www.myhtcphone.com ?
[Touch Diamond, MDA Compact IV ROM Development] NetRipper:
I have, but nobody seems to have tested the kernel I have posted yet. I'm ready to commit it to git if someone would please just test it. :)

Anyone with a RAPH800 (= sprint raphael or sprint diamond), please test this kernel:

http://www.netripper.com/raphael/zImage-raph800-01

And let me know the results. Thanks.
[Touch Diamond, MDA Compact IV ROM Development] etiger13:
wow that was an incredibly slow download. ill try testing though.
[Touch Diamond, MDA Compact IV ROM Development] ecker2008:
i will also test, but kinda a noob.. just started looking at this android stuff... what do i all need to test this out? and do i just put this as a text file somewhere or what? i am more than happy to test with my sprint Diamond and looking forward to help as much as i can!.. so just let me know.. i was looking at the wiki, but no help. should i download haret or the exe on there and switch out the files..i guess i should ask what the kernel actually is and how to run it... sorry for the noob questions, but i am really interested and would love to help you guys out!
[Touch Diamond, MDA Compact IV ROM Development] NetRipper:
1. Download the contents of this (mirror) to a local directory.

2. Open default.txt and change last line from "ramboot" to "bootlinux"

3. Delete the zImage

4. Download zImage-raph800-01 (kernel) and rename it to zImage

5. Copy all files to your storage card and run haret.exe, then click 'run'.

Thanks.

Strange. Should be a pretty fast host. Stationed in Amsterdam/ams-ix.
[Touch Diamond, MDA Compact IV ROM Development] jfs1179:
I was able to boot with this kernel on my sprint raphael. I got to the calibration step, tapped the dots and then it dumped me to the console.
[Touch Diamond, MDA Compact IV ROM Development] NetRipper:
Press any key on the virtual keyboard after calibration to continue booting (if you're using my android initrd, that is). Anyway, that you got this far, already confirms it's working ;)
[Touch Diamond, MDA Compact IV ROM Development] Srem:
anyone got a vid of the latest android performance on diamond?
[Touch Diamond, MDA Compact IV ROM Development] jfs1179:
Ok, I switched out the initrd to android and it started up. However the colors do no look right. I'm at work so I don't have a camera to take a picture of the screen.
[Touch Diamond, MDA Compact IV ROM Development] NetRipper:
That's a known issue. Can't help that for now. Thanks for testing. :)
[Touch Diamond, MDA Compact IV ROM Development] ecker2008:
thanks for the instructions NetRipper..i am downloading now.. as for speed, i am getting about 30 - 35 KB/s, so its not too fast... i will be testing it out as soon as it is finished and post my results..
[Touch Diamond, MDA Compact IV ROM Development] seanmd:
Sorry dude, I was trolling.

I do really appreciate the work being done so far on this, and I aspire to write something worthwhile enough to contribute to it.
[Touch Diamond, MDA Compact IV ROM Development] ecker2008:
alright NetRipper.. everything worked fine... i did the calibration during boot and android booted up.. the colors were messed up (just like the pictures that were in wiki).. i'm not really sure how to bring up the on screen keyboard, or anything really else.. i am not sure if there is a "back" button, but once i went into something, say contacts, nothing i pressed would let me go back to the main android screen.. if there is anything else you need me to do or test, just let me know..i don't really have a great camera to take good screen shots, but i took one with my laptop's webcam just so you could see the colors and attached it here (sorry for the horrible quality) .. thanks and let me know if i can help with anything else...
[Touch Diamond, MDA Compact IV ROM Development] Willis111:
boots on my cdma telus touch diamond, I did notice when booting I got an error

"[6.495471}clock_late_init() disabled 20 unused clocks"

"[6.500946]drivers/rtc/htcosys.c: unable to open rtc device (rtc0)"

before I get the touchscreen calibration menu.

Colors are off in X, no sound, seems the hardware buttons aren't working and there seems to be no onscreen keyboard so I had some trouble testing things like phone and basically just pissed around with some apps, plugged in my usb cord and nothing. Seems when I open an app that requires typing my * key is held down or something , screen calibrates perfect though and of course I love you man! No complaints from me, any progress is great!

@ecker2008:

As far as buttons the only thing I've found working was the stylus for back.
[Touch Diamond, MDA Compact IV ROM Development] ecker2008:
ahh.. the one thing i didn't try :) thanks for the tip... so @anyone... is there a working onscreen keyboard and if so, how do you bring it up? thanks
[Touch Diamond, MDA Compact IV ROM Development] katmandu421:
Wow, this is too cool...what great progress!!

I tried this a month or so ago and must have skipped the posting about having to switch out the zImage when running this on the Spring Diamond, so I never got to the calibration screen. I booted right in this time. Same colors as previous posters, but this is known. I'm just happy to get into a UI other than winmo, and it's super fast launching the apps and browser! I hope this performance sustains as all the great devs on here polish things up.

AWESOME!!
[Touch Diamond, MDA Compact IV ROM Development] sibbor:
Good that you include RAP800 support into the git.

The performance will probably remain the same as it is now until the developers gets Android to boot nativly, with correct support for the hardware in the phone/-s... once they do, the performance will be staggering!
[Touch Diamond, MDA Compact IV ROM Development] piethein:
A lot of drivers were added lately;

http://review.source.android.com/user/arve,,android.com

http://android.git.kernel.org/?p=kernel/msm.git;a=shortlog;h=refs/heads/android-msm-2.6.27

Maybe it will help to port android?
[Touch Diamond, MDA Compact IV ROM Development] sibbor:
Hmm, these seem pretty interesting, but perhaps they don't apply to QC 7201A?

* [ARM] msm: msm72k_udc: gadget driver for Qualcomm MSM 7200

* [ARM] msm: trout: Refactor msm_hsusb platform data for msm72k_udc driver
[Touch Diamond, MDA Compact IV ROM Development] slovoflud:
hmmm...

I'm not a programmer, but....

This whole porting thing is taking too long... I'll help you out guys..

should go something like this:

for i in boot do
(

if winCE then(
skip;
)

else(
boot.linux;
get param. user
user param = Android1.0; drivers=true; ringtones=true
)

end

there.
[Touch Diamond, MDA Compact IV ROM Development] Marcellus_pnz:
Already tried that. Doesn't work. Maybe because the i is indefined, or maybe beacuse this cycle is endless... Need to test more.
[Touch Diamond, MDA Compact IV ROM Development] slovoflud:
endless?

'End', means 'End', or is it different in programmerland? :)
[Touch Diamond, MDA Compact IV ROM Development] Marcellus_pnz:
endLESS. That means without an end.

Ну "бесконечный" же. У него граничные условия не заданы)
[Touch Diamond, MDA Compact IV ROM Development] Neutron83:
Hi Folk,

as i dont see anyone got a workaround with the flickering to FB written soft keyboard i liked to add this to our thoughts:

http://sicksand.net/post/59437720/android-on-screen-keyboard-is-out

didnt tried it jet but would be great if anyone could intigrate that into the android image.

Thanks :)
[Touch Diamond, MDA Compact IV ROM Development] slovoflud:
:) понил, камандир!

sorry everyone :)))
[Touch Diamond, MDA Compact IV ROM Development] etiger13:
could someone write up what they do exactly when working on the port? i want to help but i have never compiled a linux kernal before but i am good at figuring code out. If someone could point me in the right direction, I could compare the Vogue's progress with this and see what I could incorporate from that. I tried a bit from last night Haret wouldnt launch, but it was an amateurish first step.

I also created a couple of forum topics for this over at http://www.myhtcphone.com/forum if anyone wants to use them. I created the site for the Vogue port but now that I have a Touch Pro, I am going to add stuff for that as well.
[Touch Diamond, MDA Compact IV ROM Development] keerttttt:
I could be mistaken, but this project looks really dead. Big shame, it had much promise and would be great news if succeeded...
[Touch Diamond, MDA Compact IV ROM Development] rl2000:
I don't think it's dead, I just think it stalled due to winter exams for many of the skilled people :)
[Touch Diamond, MDA Compact IV ROM Development] NetRipper:
It's not. Many people are just really busy. Myself included. Even if it takes a while, there's at least a lot of potential to get Linux up and running on the Diamond and Raphael with a lot of hardware support. It's not like we reached a dead end.
[Touch Diamond, MDA Compact IV ROM Development] jamesd256:
Rome wasn't built in a day. It will happen.
[Touch Diamond, MDA Compact IV ROM Development] straylight:
Will booting into Android (eventually) be able to access things WM cant? like a locked down GPS? or does Android currently only see and use devices WM can?

I was always a little confused about that, Is this implementation running Android INSIDE of WM6.1? or is it truly booting into a new OS?
[Touch Diamond, MDA Compact IV ROM Development] espenfjo:
Oh.. ok..

Sorry for double posting, but this is new information, and the previous post was long enough already.

It seems like there is a section after the mmu_trampoline aswell, the preloader.

The FB shows that it jumps to the PSR-part (Program Status Register, the thing that holds the flag information about programs and instructions) in the preloader.

However, it doesnt seem like it will continue after this(the fb doesnt show anything else atleast), and only come this far only one out of thousand tries (well.. haven tried that many times yet tho..).

Tho.. The logging often surpass the FB information.

So this seems the furthest i can go without having any means to stabilize the FB output, or run an external debugger like gdb on haret.
[Touch Diamond, MDA Compact IV ROM Development] Global_Inferno:
Has anyone had a look at Ubuntu Mobile Edition??

http://www.ubuntu.com/products/mobile
[Touch Diamond, MDA Compact IV ROM Development] skiwithpete:
Ubuntu MID is aimed more at computer/netbook devices like the EEEpc, MSI Wind, etc.

On the Ubuntu MID site it confirms that a MID device has:

Note that while it says 3G this is implied for data transfer and it doesn't say Phone functionality. For mobile phone based Linux, the bleeding edge is really Android.
[Touch Diamond, MDA Compact IV ROM Development] Global_Inferno:
Oh ok... Just was curious as I dont know much about the whole Linux Mobile OS development at the moment, in what sort of state is Android at the moment then? Usable?
[Touch Diamond, MDA Compact IV ROM Development] sensorama:
Have you even read this thread? :confused:
[Touch Diamond, MDA Compact IV ROM Development] sama:
I hate it when ppl do that, they see the title of the thread and are too lazy to read the whole thing. They expect someone to just summarise the entire thread for them... and worst of all, is that this realisation will come as a shock to them and they'll get offended by it, as that's not what the meant... grrrr.....

not my best morning today either
[Touch Diamond, MDA Compact IV ROM Development] Global_Inferno:
Um I have read the thread, but as it goes off topic about every 1 in 3 posts, it's kinda hard to see where people have got too... From the looks of it, noone has even managed to get Android to start up, let alone be usable? That sound about right?

Next question, what can people do to help?
[Touch Diamond, MDA Compact IV ROM Development] sensorama:
Spot on as you can see. :D
[Touch Diamond, MDA Compact IV ROM Development] Global_Inferno:
Im asking if I can help and you flame me.... right then.. **** the lot of you then.
[Touch Diamond, MDA Compact IV ROM Development] skiwithpete:
Global>

Here's some stuff you can help with:

1)

http://www.gnome.org/mobile/

What is it? Is it just another MID interface?

What does it need to run on top of? Android or not?

Can you find instances of mobile devices running it?

2)

Compile some youtube videos of other phones running Android, to add some motivation.
[Touch Diamond, MDA Compact IV ROM Development] espenfjo:
What about keeping this thread as on topic as possible?

At the moment my problem is still harets unstable FB. The FB address should be right, but it might be a size problem or something?
[Touch Diamond, MDA Compact IV ROM Development] Riel:
Not much about help. Just lazy question IMHO.

That Linux-booting thing must just be a small glitch. I just feel not very much people are trying it :) I really do not like WM. I am still waiting for linux to go onto or mobiles.

I have bought a Motorole Z6 just because it's running linux :)
[Touch Diamond, MDA Compact IV ROM Development] Global_Inferno:
1) Looks to me as though it's an entirely new branch of GNOME development, based off the foundations of X, GLib and the D-Bus. Using normal GTK+ UI toolsets and offering API's in C, C++ and Python. (Although there really, isn't a lot of information on it available at the moment!)

So what is it? An completely new Mobile OS, based on the existing GNOME Desktop and Embedded builds, with API support for developers.

Licence? It's distributed under the terms of the LGPL which, in there own words, "allows for royalty-free use in proprietary software products, but encourages contribution of platform code changes back to the community."

What does it need to run on top of? Nothing, as far as I can see.. Other than a Linux Kernel.

Android or not? Not.

Any devices running it? Not currently, all the information relating to the devices which will be supported are all shown running their own proprietry software currently.
[Touch Diamond, MDA Compact IV ROM Development] Global_Inferno:
Demo:

http://www.youtube.com/watch?v=1FJHYqE0RDg

http://www.youtube.com/watch?v=arXolJrLVEg

http://www.youtube.com/watch?v=4PRfVKzuUJ4

http://www.youtube.com/watch?v=DfruA4RzzpQ

http://www.youtube.com/watch?v=iBHx5jHsqiU

Development:

http://www.youtube.com/watch?v=QBGfUs9mQYY

http://www.youtube.com/watch?v=fL6gSd4ugSI

http://www.youtube.com/watch?v=MPukbH6D-lY

http://www.youtube.com/watch?v=I6ObTqIiYfE
[Touch Diamond, MDA Compact IV ROM Development] espenfjo:
I have a question.

The Diamond utilizes an ati chipset, or an ati portion of the msm7201, right?

the ati driver is the ace_ddi?

But.. I cant seem to find an ace_ddi on my diamond, and haret wont utilize the ati fb portion either..

So.. Are we just missing a driver? or is it something else?

EDIT: Ok.. found out that some ati functions are in ahi2dati.dll, edited haret to use that instead of ace_ddi, hacked som more on it to not include missing functions in the ahi2dati, got this info;

HaRET(2)# atidbg
ATI asic* =0x50F00000 / 0x02b8f000 ret=0

ATI ChipId = 0x51301002
ATI Revision = 0x00000000
ATI RevisionId = 0x00000000
ATI BusInterfaceMode = 0x00000002
ATI InternalMemSize = 0x00040000
ATI ExternalMemSize = 0x00000000
ATI Caps1 = 0x00000031
ATI Caps2 = 0x00000001
ATI Caps3 = 0x00000000
ATI Caps4 = 0x00000000
ATI ctx* =0x50F12888 / 0x02b7d888 ret=0

ATI mmPLL_REF_FB_DIV = 0x08924924
margins: xrest=0 yrest=0 left=0/0 right=0/0 up=0/0 down=0/0

pll: ref_div(M)=4 div_int(N_int)=9 div_frac(N_frac)=2 lock_time=8 Fout=2*xtal

sclk: sysclk_src=0 sysclk_div: fast=0 slow=0

pclk: pixclk_src=0 pixclk_div=0

Hope someone can get something out of this