yashsingh1/xdaforums huggingface dataset:
[Touch Diamond, MDA Compact IV ROM Development] Roflnova:
It is unrealistic to ask for Sense at this time when the Android port is so primitive.

Plus, the Hero has a lower resolution than the Diamond. I believe scaling graphics UP from a lower resolution is more challenging than scaling DOWN. **** gets pixelated and blurry.

Be realistic. Don't throw unrealistic expectations around and then tell people to "fly down" and "clean your mouth" when they scoff at your unrealistic expectations.

Also, you seem to think that the developers are porting Android just to use Sense. This is incorrect.
[Touch Diamond, MDA Compact IV ROM Development] wrsg:
i am trying to boot the android rom from http://www.androidonhtc.com

but it is stopping at the android splash screen, after the linux boot messages. has anyone got past this? i might have not installed it properly, but i basically put everything into the root of the internal storage, including the files from the 'boot' folder. it would be nice just to play around with the android gui on the diamond.

also this may be the wrong place to ask this, but if i want to help develop the android rom, where is a good starting place?
[Touch Diamond, MDA Compact IV ROM Development] alasuede:
SIM-lock

must be turned off.
[Touch Diamond, MDA Compact IV ROM Development] wrsg:
yes, simlock is turned off.
[Touch Diamond, MDA Compact IV ROM Development] dotted:
Right you are ;)
[Touch Diamond, MDA Compact IV ROM Development] HyoImowano:
Setup in Emulator?

I looked through this thread but didn't see anything touching on this, so sorry if it's been discussed at all. I was wondering if there was any way to run our Android image in an emulator or setup some of the settings (ie data, contacts, etc.) externally since it's pretty prone to crashing on the phone. I'd love to play with Android more (before I decide to make the jump to an actual Android phone) but trying to set everything up before it crashes can be a bit of a pain, any ideas?
[Touch Diamond, MDA Compact IV ROM Development] :
finally raph110 users can access there memory cards thank's to the new raph100 android build. ^^
[Touch Diamond, MDA Compact IV ROM Development] wrsg:
can someone please tell me the status of whether android can boot on diamond? mine just sticks on the splash screen. i am using BsB version M WM6.5
[Touch Diamond, MDA Compact IV ROM Development] Saturn2888:
The golden question there warsng.
[Touch Diamond, MDA Compact IV ROM Development] tamasp:
Do you have a link?
[Touch Diamond, MDA Compact IV ROM Development] BlazerRazor:
People like you should not be allowed to visit this board, seriously, can't you read?

To help you, yes, android boots on the diamond.
[Touch Diamond, MDA Compact IV ROM Development] Saturn2888:
Just not everything works. If it all does, I probably missed that somewhere in the last 100 pages of posts, lol.
[Touch Diamond, MDA Compact IV ROM Development] rgildoss:
okay i read through this entire thread and the wiki but i still cant figure out if anyone has got this working on a raphl800. i see the wiki talks about the 100 but no info on the 800 ..

so in short can anyone confirm that this is working on a raphl800??
[Touch Diamond, MDA Compact IV ROM Development] jr_daza:
I think that i see in the Connect-utb.com a bluid for ralph 800 but i have a Diamond so I dont know for sure
[Touch Diamond, MDA Compact IV ROM Development] deekjx:
There is an emulator that is included in the SDK available on androids website. It can not run this particular image, but it can allow you to get a feel for the android platform. Its missing the Market and Gmail. It does use your computers internet access so you can give the browser a spin.
[Touch Diamond, MDA Compact IV ROM Development] :
Here's the link, enjoy.

note: make sure you delete the zimage and the .xml file from the tmp folder, or else it wont boot.
[Touch Diamond, MDA Compact IV ROM Development] HyoImowano:
Drats, I was really hoping to try it more on the phone to get a more legitimate feel for it, but I appreciate the tip all the same :D .
[Touch Diamond, MDA Compact IV ROM Development] kurgandk:
sorry im sure this has been asked and answered before, but I wasnt able to find it in the thread (admittedly I didnt go though all 300 pages ;) )

im using the 0622 version, and it seems to work...

but then I come to a sim-lock screen, and the touch scrennis way off, not just offset but different areas on the screen is accessed by strange places on the touchscreen.. (some up some down...)

even so I was able to type in the sim code, but that didnt work (was not accepted)

so i went to wm and turned off simlock... but then the boot hangs at '[handover]'

kind regards
[Touch Diamond, MDA Compact IV ROM Development] refl3x0r:
I think directly after a softreset it shouldn't hang at the handover.

I only got this problem running wm a while before starting haret!
[Touch Diamond, MDA Compact IV ROM Development] kurgandk:
ok so finally it booted, after af few attempt it finallay got past [handover]

i have found that the problem is that the touchscreen is in fact flipped upside-down

also sound seems to be off, but perhaps its bacause i had it silenced in wm before i booted haret?
[Touch Diamond, MDA Compact IV ROM Development] Erik_PLD:
No, it's only because sound on our devices, and on Android it's not working yet. It's posted somewhere in the 321 pages of this topic.:D
[Touch Diamond, MDA Compact IV ROM Development] kurgandk:
ah.. ic..

well I got the flipped screen fixed by modifying default.txt according to the info :

http://wiki.xda-developers.com/index.php?pagename=RaphaelLinux
[Touch Diamond, MDA Compact IV ROM Development] skorpiworm:
I have been following this thread for some time and i just read the last 10 pages.

Is there any heads up on the audio progress.

Is it the sound driver itself that is the issue or is it the link between android and the driver?

I have the android-diam100-20090222 build running on my diamond and I must say that you guys have done one heck of a job.

Im kinda new to this so parden me if this question has been answered elsewhere. How can I tell if my phone is a diam100, diam500 etc?
[Touch Diamond, MDA Compact IV ROM Development] kaju:
I've got the same problem (HTC Touch Pro), any solution? Thanks
[Touch Diamond, MDA Compact IV ROM Development] kaju:
Please, could you upload the default.txt modified? Thanks a lot
[Touch Diamond, MDA Compact IV ROM Development] wrsg:
i am trying the connect-usb build, but i am not having much luck, it is reaching the linux boot messages, but it stops at a message about mmcblk0.

i am trying this with all the files in the [internal storage]/tmp folder and then running the haret.exe

i already tried with the default directory structure, but it didnt even get that far.

sorry for the noob qns, but i really am a noob at android.
[Touch Diamond, MDA Compact IV ROM Development] kurgandk:
im simply using : msmts_calib=0x7A.0x5E.0x35A.0x37F

but you should check what device you are using...
[Touch Diamond, MDA Compact IV ROM Development] wrsg:
just for anyone who is having this ****er of a problem, rename the mmcblk0 in the default.txt to mmcblk0p0

it boots now, and it suits the diamond very well.
[Touch Diamond, MDA Compact IV ROM Development] cr2:
i have some progress on adsp_5200.c ( the cdma people will need their own adsp_6150.c, which is substantially different)

The bluetooth research has resulted in a somewhat unexpected outcome: i've changed the RX channel to 9 (=wince value) so it does not clash with USB DMA, but it seems

that the TX channel =1 (??)

Check the latest ltg git for details.
[Touch Diamond, MDA Compact IV ROM Development] Kafro:
I seem to be having troubles making calls.
[Touch Diamond, MDA Compact IV ROM Development] donald-c:
I don't think calling works yet.
[Touch Diamond, MDA Compact IV ROM Development] Kafro:
Oh, because I know SMS is working for sure , but I am aware that there are no sound drivers yet.
[Touch Diamond, MDA Compact IV ROM Development] :
Soon they will be, and maybe even for BT and gps ;D
[Touch Diamond, MDA Compact IV ROM Development] moovius:
Very interesting to watch the progress with this

I have been struggling with the windows mobile os since 2007 with my Titan and now with my Touch Pro. I HATE THIS OS!

Even my TP that has all this processing power and memory, etc... is brought to it's knees by the clunky, patchwork, excuse for a mobile os that WM6 is (also 6.5).

You know how pathetic I feel when someone with a first generation iPhone comes up to me and shows off how slick and hesitation free their OS is and then I pull out my phone and it's stalling, hiccuping and gagging to death to even load up Album 2.0 so I can show off some pictures or video (not to mention a whole slew of other programs)?

Someday there will be an alternative, someday soon I hope. Keep up the good work on the Android integration!

*Seriously, I want to drive to Redmond and assault my phone into tiny fragments in the main employee parking lot to make a statement* :mad::mad::mad:
[Touch Diamond, MDA Compact IV ROM Development] We Have Signal:
Amen brother, amen.

As I use windows every few minutes I notice just how perfectly my Diamond is shaped for throwing.
[Touch Diamond, MDA Compact IV ROM Development] fliggygeek:
FAQs

can we put a link to the FAQs on connect-utb on the first page of the thread in order to weed out all the n00bs that wont read the rest of the thread?

http://connect-utb.com/index.php?option=com_content&view=article&id=174:frequently-asked-questions-about-the-porting-project&catid=42:the-android-port&Itemid=1
[Touch Diamond, MDA Compact IV ROM Development] fliggygeek:
Monies

is there a way to give monies to ppl involved with this project as a thankyou present/hurry up? I'd certainly want to give some to ppl.
[Touch Diamond, MDA Compact IV ROM Development] Untouchab1e:
Hi and thanks for noticing the FAQ page! I will add it to my signature here so that more people can pick up on it ;)

Regarding money-donation I dont really think it its needed and therefore woulndt make the development process going any faster for now. If it would I would gladly pay whatever the cost would be myself instead of trying to figure out things myself :P

I kindly appreciate the offer though and I am sure Jobo and the others do too ;)

Just keep up your hope and support :)
[Touch Diamond, MDA Compact IV ROM Development] gebruikershaes:
We could set up a donation page with a counter like the Omnia has. The one or the ones who successfully port android to our Diamonds get all the money?

http://androidomnia.com/
[Touch Diamond, MDA Compact IV ROM Development] Untouchab1e:
Problem is that the porting proccess isnt a one man job, at least not in this case. Its not like someone can just look at the drivers issue and go "Ah, but what if we do this?" and then suddenly everything works :) Again, I dont think money is what we are working for. At least not myself.. I wont speak for the other devs ..
[Touch Diamond, MDA Compact IV ROM Development] Untouchab1e:
Heh, the worst thing is that HTC on the other hand makes such lovely Windows Mobile devices that just looks awesome.. Then comes Android devices from HTC that just looks like cheap toys :( (HTC Hero is slightly better but nowhere near the beauty of Touch Pro 2 or Diamond 2)
[Touch Diamond, MDA Compact IV ROM Development] Marcellus_pnz:
Beauty of Diamond2? In my opinion, it's a brick. The only beatiful phone is the first diamond (but when you use it for a while - WM ruins all of the beauty). But I think Magic is cute too, and Hero is just adorable and stylish! Tastes differ)
[Touch Diamond, MDA Compact IV ROM Development] fliggygeek:
On another note, is there a priority list for the tasks that need doing?

I know that once calls and battery/power/standby is fixed i will use android full time. Is this a common feeling?
[Touch Diamond, MDA Compact IV ROM Development] Mrheineken08:
it seems as though the driver problems are related to wm running and linux running at the same instance. the compononents are already in use by windows and therefore can not be turned on by a nother program such as android. they are either on or off and wm takes precidence because of signed drivers snd suc turning the component on would be alot easier if a nbh was compiled with all the nessecary files and drivers mapped to their destinations. try doing some more development on an android kitchen and maybe edit some preexisting android drivers to make components work. try some c++ and java and some xml. yall can make your own os in less time thsn it tskes to reverse engineer a crappy one making it take up more cpu cycles and ram.
[Touch Diamond, MDA Compact IV ROM Development] demacus:
+1

absolutely agreeing with this

Maybe someone here has an idea how to start with dreating a flashable android rom. I'm willing to flash it to my phone as soon as it's there for testing!

regards
[Touch Diamond, MDA Compact IV ROM Development] Soaa-:
I don't think WM and Linux run at the same time. If my memory serves me right, Haret uses a mechanism in WM to boot the image as a bootloader would. WM effectively shuts itself down as that happens.
[Touch Diamond, MDA Compact IV ROM Development] demacus:
Maybe you're right, but for me it looks like windows just "stucks" when haret is loading. In example: charge light stays on if the phone were charging while haret starts. It's just a thought but maybe it would be helpful if we try. I would love to see android working stand alone!

At the moment I'm trying to extract a DREAIMG.NBH, but till now I had no luck with this. If someone has any Idea how I could try to create a flashable nbh, please let me know and i'll try!

regards
[Touch Diamond, MDA Compact IV ROM Development] Erik_PLD:
+1, I'll be glad to try it as soon as we have a *.nbh rom with android. :)
[Touch Diamond, MDA Compact IV ROM Development] ducamie:
this is correct
[Touch Diamond, MDA Compact IV ROM Development] Kafro:
Yeah, the process is ... Load up Haret, then it shutsdown WM and boots Linux.
[Touch Diamond, MDA Compact IV ROM Development] babijoee:
Where did you get this info on? As reading through the first page and many others, its clear that haret run and wm shuts down and then android is then booted. As for Android rom, its not a good idea as yet as most functions dont work for daily use. As for flashing a rom from a different device most likely ends up making your device bricked or cause many headaches for trying to fix you device.
[Touch Diamond, MDA Compact IV ROM Development] :
dont even think about flashing your device with that DREAIMG.NBH, or your going to have a nice black styled brick.
[Touch Diamond, MDA Compact IV ROM Development] XDA-Geek:
Andriod supported but the drivers do not load up
[Touch Diamond, MDA Compact IV ROM Development] los1223:
I've been following this thread for a while, but I'm not quite sure how the whole, haret/android things works behind the scenes. Is there anything keeping us from using a Hero flavor of android? That looks wicked sick! Could we just replace the cupcake android image with a hero image or something of the such?
[Touch Diamond, MDA Compact IV ROM Development] mdrobnak:
Here's where things are:

The main line (Google developed) Android is what is being used in the project right now. The main issue is getting all of the hardware to work with the current Google software. This entails working on the hardware drivers in the Linux kernel, which all Android devices use.

Because each device is different, you cannot simply throw the kernel from one onto another and expect full functionality - some things may be the same, but in all likelyhood not.

There are some very smart people on this board, and I don't doubt that after the release of the Hero (if it hasn't been already, though I don't think so), someone will get the ROM off of it, and extract the customized Android build off of it. Between that and and a fully functional kernel from the people working on this project, and yes, you can have what you're looking for.

No guesses as to a timeframe though.

Hope this helps answer your question.

-Matt

PS No, still don't really have time to devote to this right now, work has been insane for months, just doing some quick browsing before work...Looks like some progress is being made. Good job everyone. :-)
[Touch Diamond, MDA Compact IV ROM Development] demacus:
I didn't want to flash a pre-build Android image, I just wanted to extract the image in order to see how it's build. Still had no Luck with this till now. I'm gonna try to find a way creating a flashable image. Any help is welcome.

regards
[Touch Diamond, MDA Compact IV ROM Development] los1223:
I understand the state of the project. What I'm unsure of is where the driver issues are. Are the drivers missing from the linux kernel or Android? My understanding, and it could very well be wrong, is that haret or the linux kernel is what loads up the drivers and Android kind of rides on top of that. So this would mean that once everything is sorted out in the linux kernel, you could use whatever version of Android. Right, or am I way off?
[Touch Diamond, MDA Compact IV ROM Development] Untouchab1e:
This is correct. The issues are on the linux kernel level and not related to Android itself.

I dont know where you have this from but it is incorrect. The fact is firstly that haret shuts down Windows Mobile before booting up Android but secondly, the fact is that the reason we have anything working at all is because of the inits WM does. I am pretty sure we are going about it from the right angle, its just very slow and difficult. I dont have that much low-level programming experience so I just try to help out where I can..
[Touch Diamond, MDA Compact IV ROM Development] espenfjo:
I can explain why parts of the phone have to be activated in WM before it can be used in Linux/Android, and a bit how haret works.

The way normal firmware and drivers work are by telling the device (WIFI, GPS etc.) that it should activate and start doing it job.

This can be as simple as telling it to power on, or more complex routines having to send data back and forth before it powers on.

So when you in WM tell the GPS to turn on and activate it still will be activated after booting Linux.

Haret loads the Linux kernel into memory while WM is running, then it takes control over the entire device, disabling memory management functions (MMU), copies the Linux kernel from one place in memory, to the place it should be, and executes (jumps) to that location. (Very simplified)

(Haret might not work in future versions of WM since the MMU takover only works on OSes with no security, and running every app in RING 0/Kernel space. Just like DOS did).

When haret jumps to the Linux kernel location the Linux kernel starts and clears, and writes over the entire memory used by WM.

The GPS device is still activated and transmitting data even though WM is gone.

This is why the LED state also "hangs" after booting Linux/Android.

In WM when the usb charger is connected WM tells the LED to light. When WM is gone there is nothing there to tell it to stop.

There shouldnt (read shouldnt) be any differences in running Linux from Haret or running it native other than that you have to initialize all the devices in your phone again.

Hope this can shed some light on how Haret and Linux works.
[Touch Diamond, MDA Compact IV ROM Development] espenfjo:
Ok, i guess i should read some more, but im asking anyway.

Is there a way to ssh/log remotely into the device?

That way i can test and debug the kernel a bit better, i really hate the small blue-box keyboard :)

And i guess there isnt any way we can install the kernel source on the device and modify, compile, load modules?

It all have to be done externally?
[Touch Diamond, MDA Compact IV ROM Development] druidu:
I know usbnet is working, didn't test it though. You could modify the initrd image to run a ssh server before starting up android, then log in via usbnet.

Look here for a very small ssh server that you can use.

PS: sorry for totally disappearing half a year ago, I've been really busy with school & a lot of other projects. I'm happy see that somebody finally figured out how to make the IRQs for the touchscreen work and cleaned up my messy code :)

I'll soon be rejoining the fight to make Android running smoothly. WM is so damn annoying that I'll either get rid of it or go totally crazy :eek:
[Touch Diamond, MDA Compact IV ROM Development] saudoo:
Woop woop.. More coders. Glad to see you back on track (android wise).
[Touch Diamond, MDA Compact IV ROM Development] Untouchab1e:
Connect-UTB.com is having some issues with the MySQL Database. The webhost has been contacted regarding the matter and will hopefully sort it out ASAP.

Sorry for any inconvinence..
[Touch Diamond, MDA Compact IV ROM Development] computerguru:
Hey...I was just wondering how the sound issues are coming along on the current kernel. Are there kernel modules that can be tested?
[Touch Diamond, MDA Compact IV ROM Development] espenfjo:
.config of connect-utb

Is it possible to get the .config for the diam500-builds connect-utb are providing?
[Touch Diamond, MDA Compact IV ROM Development] frysee:
Try this one: click

greetz
[Touch Diamond, MDA Compact IV ROM Development] espenfjo:
If that is the same as the file from connect-utb the .config isnt in it.

Thanks anyway
[Touch Diamond, MDA Compact IV ROM Development] gm112:
Well, there has been progress it seems. I can finally get to a boot screen. Although, that's as far as it gets. My device is a RAPH110. Keep up the work :D... this really excites me because I simply can't wait to see Android running on my phone.

Question, is this code based on Android 1.5?
[Touch Diamond, MDA Compact IV ROM Development] :
I also have a raph 110, the latest build for the raph100 boots just fine on my raph110, and yes this build is based on android 1.5 cupcake.

regards

Rafyvitto
[Touch Diamond, MDA Compact IV ROM Development] defidami:
Android on Diamond

Hi, I'm from Italy and I'm very interested in making Android work on an HTC Diamond mobile. I'm kind of a developer as I'm still doing school...I wonder if you could tell me where's the problem in making Android run on the phone. I will try to help as much as I can. Byeeeeez
[Touch Diamond, MDA Compact IV ROM Development] ElCondor:
Haha I like this very much, my friend has a topaz and he's very jealous!

But still there are many things to do... I can't help with developing because i've not much skills for that. Good luck with developing, don't stop the good work and if I can be of some help, just ask!

I work a lot with graphics etc. so if some graphics need to be modified I'm ready to help!
[Touch Diamond, MDA Compact IV ROM Development] Untouchab1e:
If you are good at assembly and are confident with low-level driver development, feel free to pop in at the #htc-linux channel at Freenode ;)
[Touch Diamond, MDA Compact IV ROM Development] ElCondor:
A few bugs I noticed (are these known?)

What doesn't work:

1. lock button :(

2. no softkey buttons

3. IM work

4. camera

5. Calendar

6. In music, error 'your phone does not have an sd card inserted

7. battery status

Are these known bugs?

I didn't know anything about Android, but now I have it and it's absolutely gorgeous! Everything works so intuitive!:) Thanks again!
[Touch Diamond, MDA Compact IV ROM Development] diboze:
i see you have the same rom (gen.y 1.25).

have you changed anything to make it run? Or which package did you use?

I cant get it to work on my diamond :(
[Touch Diamond, MDA Compact IV ROM Development] ElCondor:
I'm sorry but my signature is a little old, I flashed another rom today (bsb 65m). But have you already tried the alternate version?
[Touch Diamond, MDA Compact IV ROM Development] diboze:
yop, both versions. Normal and alternate vom connect-utb
[Touch Diamond, MDA Compact IV ROM Development] donald-c:
If you are trying the 22nd of Febuary (something like that) version, try http://www.connect-utb.com/index.php?option=com_rokdownloads&view=file&Itemid=68&id=17:-android-for-htc-touch-pro-raph-a-diam it's the newest one on that site, although it's under Raph. versions it's for Diamond too.