yashsingh1/xdaforums huggingface dataset:
[Touch HD Windows Mobile ROM Development] shadowline:
I agree, there needs to be an android port forum as there truly is a lot of hardware wise like devices that could benefit from a central place of development. kaiser/vogue merged, diamond/raphael merged, diamond2/touch pro2, etc especially if we can get a single setup working across such devices where you can boot android on a kaiser, then take your files and boot it right into a diamond. though it would be nice just for it to work right now. :P
[Touch HD Windows Mobile ROM Development] puregenius:
Alright, I dropped a little note in the suggestions box in case anyone wants to argue in favor or against a seperate "Porting Android" subforum.
[Touch HD Windows Mobile ROM Development] Powerbik:
Good effort and idea. We might be better off with a general OS Porting Section though since it eliminates the need for too many subforums. Lets keep things general :)
[Touch HD Windows Mobile ROM Development] ASK768:
any news about android?
[Touch HD Windows Mobile ROM Development] Jewstie:
Will this help?

http://translate.google.com/transla...os-draaien.html&sl=auto&tl=en&history_state0=

Its an automatic translation of a tweakers.net newsmessage. atm i don't have time to translate it properly. Will do it this evening if necessary!

Oh it is about virtualizing Android on basicly every mobile os.
[Touch HD Windows Mobile ROM Development] Cyclone_storm:
It's much easier to read in the original language for me haha. But to come to the point, I think it could work perfect. But we need to be able to use or get the software in order to get this to work. And in the article they already sad, that they were unsure of consumer use. Great post. :D:D:D
[Touch HD Windows Mobile ROM Development] Jewstie:
Translation:

Open Kernel Labs has released OK:Android. With this Android can run aside any other mobile OS. It is mostly meant to help developers/fabricators of phones. The only requirement is, the processor must support OKL4

OK:Android runs as a guest-OS aside any other mobile OS on a smartphone or other phone. This happens in a secured hypercell, which encloses de virtual machine completely from other virtual machines or OS's running on the hardware of the phone. OK:Android use Open Kernel Labs' own virtualisationplatform, OKL4. This has been distributed with 300 million phones, like the Xperia X1 en T-Mobile G1 (First Android phone, it's called T-Mobile G1 all over the world right?)

OK:Android is meant for phone manufactures. They can test Android OS more easily on a new phone with the help of the virtualisation-software. Plus multiple version of Android can run side by side, so compatibility can be also tested more easily. There is also a possibility that cheaper hardware could run Android, which could bring cheaper Android phones to the market.

Het is niet de eerste keer dat er geprobeerd wordt Googles mobiele OS in een virtuele omgeving te laten draaien. Eerder liet VMware al zien dat Android en Windows CE naast elkaar kunnen draaien. Het is onduidelijk of consumenten ook gebruik kunnen gaan maken van OK:Android

Link to Open Kernel Labs: http://www.ok-labs.com/releases/release/ok-labs-accelerates-smartphone-deployments-with-okandroid
[Touch HD Windows Mobile ROM Development] baptiste14:
:confused: So, did android work on ours touch hd ?:confused:
[Touch HD Windows Mobile ROM Development] jeanfrederic:
Hey guys, this could help you, maybe http://www.ipmart-forum.com/forumdisplay.php?f=739 (need to log-in)
[Touch HD Windows Mobile ROM Development] BigDaemon:
Ok, so if i understand this news right, if anyone would get this OK:Android for us, we could all run Android in something like a virtual machine on our phones.....this combined with the most minimalistic rom anyone could cook could perhaps be a sollution for now :)

So go and search for this tool guys ^^
[Touch HD Windows Mobile ROM Development] stepw:
OKL is present in a certain form in most devices based on Qualcomm chipsets, however they are not designed to run secondary/guest OS. This feature has to make it into new devices before it can be actually used. It doesn't resolve unsupported hardware issues either and this is what's plaguing current attempts to run Android on HD... Not very handy :(
[Touch HD Windows Mobile ROM Development] ddhb:
It seems that no dev is currently working on a HD port of Android :confused:
[Touch HD Windows Mobile ROM Development] tuxhero:
Iam Working on it.

Current Blackstone Code was ported from Raphel kernel as Raphel kernel itself is incomplete, and everyone is depending on them to write code so that we can use it for our blackstone. But I don't want to depend on them so i started working on it myself.

Request:

If any one knows how to extract file from Radio ROM Please post them here.

Latest Updates:

Migrating from htc-msm-2.6.27 to android-msm-2.6.29 for keeping our self up-to-date with android kernel.
[Touch HD Windows Mobile ROM Development] ataide26:
UPDATES

Hi Guys,

I have been here all days looking for new updates about this project.

It would be very nice to have the Android in the BlackStone.

Whats seams to be the problem?
[Touch HD Windows Mobile ROM Development] nedge2k:
What he said ^
[Touch HD Windows Mobile ROM Development] Rumbi:
@tuxhero

It's nice to hear some progress. Is there anything else we could do to help you with your development ?
[Touch HD Windows Mobile ROM Development] tuxhero:
Thankyou

Thankyou for your support. I am currently porting old code to new android kernel after finishing i will surely getback to you.
[Touch HD Windows Mobile ROM Development] tuxhero:
New Thread

This Project is restarted. You can find updated in this thread http://xdaforums.com/showthread.php?t=524898 i will be looking forward for you help and support with my new Blackston-Android Project.

Thankyou
[Touch HD Windows Mobile ROM Development] nizzon:
Awesome! :D

Good initiative tuxhero!

Hope you get some help too so you get this project moving even faster.

Im following this every day, Android will make the Touch HD shine.

MOD EDIT HDuser

I have closed this thread as a new one as been opened (post above)

If any be feels that this is wrong then PM me
[Touch HD Windows Mobile ROM Development] patp:
have you tried booting this version?
[Touch HD Windows Mobile ROM Development] xmoo:
This is the cupcake version:

The off-ram version is the cupcake version (I believe it was)

The off-ram version os the raphael version. And on wiki it is saying that it is the cup cake version.

Booting did work with the old kernel (sd included, screen fix not included)

So now it is not working, until sd drivers comes.....
[Touch HD Windows Mobile ROM Development] patp:
It looks like we can expect it to work - after all it is not using any low level hardware we don't already have (just screen, stylus?).

We need to try disabling the linux kbd to see if it makes the screen glitches go away.
[Touch HD Windows Mobile ROM Development] xmoo:
From the screenshot's i;ve seen.

And also booting the off-ram version (Linux does get booted but android doesn't boot)

The on screen keyboard is gone!

So just add sd-drivers to kernell

use off-ram image

And we're off :D
[Touch HD Windows Mobile ROM Development] JanSchotsmans:
The console OSK is pritty useless for anything other then some simple commands, its better to use SSH or an actual keyboard.

If one of the boot images is cupcake, that would be the brilliant.
[Touch HD Windows Mobile ROM Development] xmoo:
http://www.youtube.com/watch?v=9zgC9vNrjIU

This was the cupcake version.

As you can see, the screen is messed up.

But still you can see that there is no on screen keyboard located on the screen.
[Touch HD Windows Mobile ROM Development] patp:
There's a tool someone generated to enable/disable/hide the kbd in the RAPH thread.

I think for the purposes of development the linux one is not a priority - if turning it off gets the screen stable, we can leave debugging it for later and concentrate on more important stuff. Android denies proper shell access anyway (there is a limited terminal app called pTerminal) - if we want full linux root CLI we shouldn't boot Android.
[Touch HD Windows Mobile ROM Development] Rewpparo:
That's why I was asking if anyone has a full angstrom initrd
[Touch HD Windows Mobile ROM Development] dwaradzyn:
You can download Angstrom from:

http://linuxtogo.org/~lgorris/raphael-bootkit/
[Touch HD Windows Mobile ROM Development] JanSchotsmans:
Would it be to far fetched to think that the OSK in Android is like all other Mobile OS OSK's and pops up only when needed?
[Touch HD Windows Mobile ROM Development] El Massman:
yeah, from the videos i've seen it'll pop up when you select a text input box and disappear when it's deselected.
[Touch HD Windows Mobile ROM Development] xmoo:
That;s correct.

But I think i've seen a keyboard app on the Android Market.

It works like WM. whenever you press on the keyboard logo it will pop-up.
[Touch HD Windows Mobile ROM Development] Mykstar:
Orux... Would it be possible to obtain a diff for the working screen when you have chance. Would like to try and compile a kernel without the OSK and also merge into .27 branch of the Kernel.

Not sure if this has been suggested but would be nice to have a blackstone research page like : http://wiki.xda-developers.com/index.php?pagename=RaphaelResearch

Nice one on getting the screen working :D
[Touch HD Windows Mobile ROM Development] patp:
It's on the wiki and on the second post of this thread already. I think Orux is already working on the .27 merge - why not address the OSK issue in .25 rather than double up the work?

Good idea on the wiki page. You know what to do....!
[Touch HD Windows Mobile ROM Development] CyberSalsero:
I have compiled my kernel... on boot linux find mmc0 but android check the files in /mmc/ why?

tnx
[Touch HD Windows Mobile ROM Development] orux:
Tested a kernel without OSK. Display instability persist. And without KB, you can't return to main menu.

I have been working with sd in .25 kernel. Sd detection works, but I can't mount the device. It is time to go to .27 kernel
[Touch HD Windows Mobile ROM Development] xmoo:
Configure the home button :$
[Touch HD Windows Mobile ROM Development] CyberSalsero:
wowww

booted the last android release on sd!!

It seems to work the network and the dialer!

On composing it crash! :(

Yess the network works: Signal OK
[Touch HD Windows Mobile ROM Development] xmoo:
Android 1.5??

Where you got the images from??

Share plz.
[Touch HD Windows Mobile ROM Development] CyberSalsero:
sorry Isn't 1.5 but the latest in android sdk!

Ok, uploading now!

http://www.portalesalsero.it/public/zImage.bin

This is my kernel

and in the default I have made this change:

set cmdline "root=/dev/mmc0 init=/init console=tt0 mem 64M msmsdcc_id=2"
[Touch HD Windows Mobile ROM Development] xmoo:
Please also upload the zImage. Or is is the same that orux made??
[Touch HD Windows Mobile ROM Development] patp:
This sounds amazing. Can you tell us what kernel version? What changes have you made? Is the android image one you made yourself or is it somewhere we can download? If you made it, can you put it somewhere for us?

Great work.
[Touch HD Windows Mobile ROM Development] CyberSalsero:
I have followed the tutorial on wiki for the kernel, but I have edited the diff.

Now on the linux boot the phone vibrate.
[Touch HD Windows Mobile ROM Development] xmoo:
The mem can be up to 98. I've tested it. As soon as I did 100 or more the phone would freeze. 98 Is the highest.

MSMSDCC_ID=2 stands for storage card. This was in android version of Raphael and Diamond.
[Touch HD Windows Mobile ROM Development] CyberSalsero:
ok I try to change to 98
[Touch HD Windows Mobile ROM Development] xmoo:
console=tt0

Was for the keyboard I believe it was.

do you see the on screen keyboard??

And dit is work 98.. any diffrence in speed?
[Touch HD Windows Mobile ROM Development] CyberSalsero:
98 freeze the device and it not boot android!

Yes I see the keyboard

also tried 86M freeze!
[Touch HD Windows Mobile ROM Development] xmoo:
hmz so the off-ram version only works @ 64mb

And the on-ram version only works @ 98mb...
[Touch HD Windows Mobile ROM Development] CyberSalsero:
restored @ 64 and boot!

But now android.process.acore crash @ boot and I can't use android :(

help me!!
[Touch HD Windows Mobile ROM Development] CyberSalsero:
Ok now it boot without error... only when I try to call me that crash the process com.android.phone!

I have just replaced the android files.

Anyone have tried my zimage?
[Touch HD Windows Mobile ROM Development] Thegn:
Hi,

I would like to test the image, but at least for me, the link: http://www.portalesalsero.it/public/zImage.bin does'nt work. Error 404.
[Touch HD Windows Mobile ROM Development] CyberSalsero:
NEWS:

the android onscreen keyboard works well!!

It appears when click on text area!

wifi not works.
[Touch HD Windows Mobile ROM Development] CyberSalsero:
tried now it works

http://www.portalesalsero.it/public/zImage.bin
[Touch HD Windows Mobile ROM Development] xmoo:
Could you upload all ur files?

When I use ur zImage on the cupcake edition.

My phone soft-resets...
[Touch HD Windows Mobile ROM Development] patp:
diff?

or at least tell us what you changed
[Touch HD Windows Mobile ROM Development] orux:
Hello;

Finally I have done an express migration to .27 kernel.

The problem is that mddi_remote has a different interface than .25 kernel, and the hack that fixes display does not work.We need to find a place to put it. It should not be a problem.

I will post a diff as soon as possible.
[Touch HD Windows Mobile ROM Development] CyberSalsero:
Is very important that you put all files in your SD in tmp folder

Now I upload all files...

edit:

http://www.portalesalsero.it/public/Android-Cyber.zip

I have used the Xmoo files

http://img9.imageshack.us/my.php?image=webcam2009022701591.png

http://img3.imageshack.us/my.php?image=webcam200902270200.png

http://img3.imageshack.us/my.php?image=webcam200902270159.png

http://img120.imageshack.us/my.php?image=webcam200902270201.png

http://img3.imageshack.us/my.php?image=webcam200902270203.png
[Touch HD Windows Mobile ROM Development] fuxer:
CyberSalsero working great so far but after 2 tries,i got an error and phone freezes

it says that message program has stopped working,and i can press force close but it locks everything so i have to reset.
[Touch HD Windows Mobile ROM Development] orux:
Please, keep this thread clean.

Works, not works, nice, ... to:

http://xdaforums.com/showthread.php?t=468360&

CyberSalsero, did you do changes to the kernel code, .config, or only compile it?
[Touch HD Windows Mobile ROM Development] xmoo:
Bro

Can you show ur default.txt

I'm @ work, internet is ****ti, so I cannot download ur .zip file.
[Touch HD Windows Mobile ROM Development] mücke007:
Hi xmoo

set MTYPE 2030

set KERNEL zImage.bin

set INITRD root.cpio.gz

set cmdline "root=/dev/mmc0 init=/init console=tty0 mem=64M msmsdcc_id=2"

bootlinux
[Touch HD Windows Mobile ROM Development] xmoo:
Thx, but it is not working for me :S

So I think I have to download the files as soon as I get back to home.
[Touch HD Windows Mobile ROM Development] CyberSalsero:
try to replace the files .img with yours.

Now I have tried to change this line: set cmdline "root=/dev/mmc0 init=/init console=tty0 mem=64M msmsdcc_id=2"

with this

set cmdline "root=/dev/mmc0 init=/init console=tty0 mem=76M msmsdcc_id=2"

I have less errors in android.

p.s. I have edited the orux diff changing any line of wifi and mmc config
[Touch HD Windows Mobile ROM Development] CyberSalsero:
4 Xmoo:

In the orux diff the Ram is setted to 76M, I think that if we set more ram in default txt android crashes!

The next step (this evening, now I'm @ work) is to try to change this value in the diff file!
[Touch HD Windows Mobile ROM Development] xmoo:
So ur saying that I need to remove the mem part in default.txt?
[Touch HD Windows Mobile ROM Development] CyberSalsero:
Try to do it
[Touch HD Windows Mobile ROM Development] gaelynx:
Using CyberSalsero's version (post 58), many of android's built-in applications can run.

Also using DevTools/Terminal Emulator, I could access to the SD card
[Touch HD Windows Mobile ROM Development] xmoo:
Nope it reboots again.

The haret bar load to 100%

Give me black screen, after 2/3 sec soft-reset.
[Touch HD Windows Mobile ROM Development] mücke007:
Hello xmoo

Here all the files on FTP Netload. I hope this helps you.

FTP Server:

upload.netload.in

FTP Port:

21

FTP User:

XXXXXXX

FTP Pass:

XXXXXX
[Touch HD Windows Mobile ROM Development] funk1980:
Android boots prefectly, but give an error stating com.android.mms and com.android.media has stopped unexpecttedly. Clicking the 'Force close' button doesn't work because there is something wrong with my screen alignment (clicking somewhere in the middle activates the keyboard buttons etc). So... how do I align the screen in this version??

I can see that I'm receiving signal :). T-Mobile NL and three bars signal strength!
[Touch HD Windows Mobile ROM Development] JanSchotsmans:
Wouldn't it be best to recompile andoid against the same compiler and kernel we're using atm?

I see several andoid specific kernel modifications in the source we're using. So maybe the UI part of android would prefer to be compiled against that.
[Touch HD Windows Mobile ROM Development] xmoo:
IT does work.

But....

550 Permission denied.
[Touch HD Windows Mobile ROM Development] mücke007:
ftp://u197128:XXXXX@upload.netload.in/
[Touch HD Windows Mobile ROM Development] xmoo:
Nope doesn't work.

I need the files in de boot directory.

Cause the images were the same file size as mine.

Can someone make a zip of the files in BOOT

and then upload it on www.speedyshare.com
[Touch HD Windows Mobile ROM Development] mücke007:
http://www.speedyshare.com/125927764.html

Please edit Netload Login Information (XXXXX). Thank you!
[Touch HD Windows Mobile ROM Development] xmoo:
hmz. Thx, but still soft-reset.

Anyone else is using dutty's 1.9 rom??

I'ma try on-ram.

EDIT!!

On ram works.

Off ram reboots :(
[Touch HD Windows Mobile ROM Development] funk1980:
I'm using Dutty's 1.9. Works great (except for the part where I can't get my screen aligned...)
[Touch HD Windows Mobile ROM Development] xmoo:
how come? Is it to fast or something?

Mayb someone can align the screen 100% correct

And we can add the lines to default.txt
[Touch HD Windows Mobile ROM Development] funk1980:
Well I don't see the message 'Stub stub stub' upon booting Android. And because the previous build I tested didn't need calibration, I never got familiar with it... I'm probably doing something wrong aren't I.... :confused:
[Touch HD Windows Mobile ROM Development] orux:
Could you post config changes?
[Touch HD Windows Mobile ROM Development] patp:
Yes please CyberSalsero - this thread is meant for us to talk in some detail about this - can you describe what you've done in some way. I don't even know which kernel this is (.25 or .27).
[Touch HD Windows Mobile ROM Development] patp:
Also xmoo, I'm a bit unclear which image is booting for people - I think it's one that you provided. Where's it from? Is it a recent Raphael build? Their most recent one is 03Feb in the .25 kernel, 19Feb for .27 kernel
[Touch HD Windows Mobile ROM Development] CyberSalsero:
well friends,

1)I have used the off-ram files by Xmoo

2)I have followed YOUR TUTORIAL on wiki pages to recompile the kernel (I dont know the version but I thing the .25)

3)Before the patch I have changed any entries in the ORUX.diff file

4)I have seen the errors on linux screen then I have changed a entry in default.txt

This is what I do

I'm lucky? Yes, can to be!

My diff is on my pc @ home this evening I post it.
[Touch HD Windows Mobile ROM Development] CyberSalsero:
4 xmoo:

How have you created or downloaded the android .img files and gpio?

Have you a tutorial for this?

tnx
[Touch HD Windows Mobile ROM Development] Micr0mega:
Your kernel is .25, I just checked in dmesg. There seems to be no uname command available in the terminal emulator.
[Touch HD Windows Mobile ROM Development] funk1980:
My mistake. Just figures out how :p

Anyhow. It seems to work slower then the 1.0 kernel build I donwloaded form the wiki...
[Touch HD Windows Mobile ROM Development] orux:
Well guys, another key revealed.

The sd was working all time.

I have change my stock 8gb sdhc for an old 512mb and Opsss! working.

Check and test different sd. Perhaps sdhc dont work fine.
[Touch HD Windows Mobile ROM Development] orux:
Works on Angstrom too:

root@htcraphael:~# mount -t vfat /dev/mmcblk0p1 /mnt/card/

root@htcraphael:~# ls /mnt/card/

/mnt/card/01 - Pista 1.mp3 /mnt/card/03 - Pista 3.mp3 /mnt/card/EncFiltLog.menc /mnt/card/tmp/

/mnt/card/02 - Pista 2.mp3 /mnt/card/04 - Pista 4.mp3 /mnt/card/black/
[Touch HD Windows Mobile ROM Development] patp:
cool! however cybersalsero seems to have done some other stuff re radio?
[Touch HD Windows Mobile ROM Development] patp:
If you add these to the cmdline bit of default.txt, you won't have to calibrate and the osk will be off.

msmts_calib=0x37b.0x3ca.0x72.0x72 msvkeyb_toggle=off

(note touch screen coordinate system seems to be opposite to raph. it's xmin.ymin.xmax.ymax - our mins are big our max are large!)
[Touch HD Windows Mobile ROM Development] orux:
Very good news.

root@htcraphael:~# uname -r

2.6.27-00245-ged619de-dirty

working, with screen OK, and sd OK (512mb, not 8gb)
[Touch HD Windows Mobile ROM Development] Rayzer HD:
orux plz dont spend the sdhc a so big role! i have a 16gb sdhc and android boots and works fine!

btw. a little question orux do you work with debian or ubuntu? and a other question did i noticed it right that all changes for the kernel will be done in the diff? and if yes can i edit the diff simply like with mcedit or each other texttool?

Rayzer HD
[Touch HD Windows Mobile ROM Development] orux:
Yes, the problem is not sdhc. There are flash devices that do not work properly with linux.

I am using ubuntu 8.10 64bits. All the changes are in diff files. You can edit it with any text editor, and you can do changes manually in your kernel. But except minor changes, those files are big files normally.
[Touch HD Windows Mobile ROM Development] BigDaemon:
Just found something on booting, it says something about the filesystem, i guess fat32 is not included?!

But SD works fine for me, it also shows me the size of the card and all info about it in android (options->storage or something like this)

Nice work, another big step i guess, even since GSM seems to work somehow now :-)
[Touch HD Windows Mobile ROM Development] orux:
With .27 kernel we will stay like here:

http://wiki.xda-developers.com/index.php?pagename=RaphaelLinux
[Touch HD Windows Mobile ROM Development] CyberSalsero:
ok this is my diff

http://www.portalesalsero.it/public/black-cyber.diff
[Touch HD Windows Mobile ROM Development] gaelynx:
I tried it:

The default calibration works fine but the osk hack was still there!

I left android running for 10 min without touching anything, the display got wrong by itself, it didn't crash though.

The problem is that Cupcake's osk only popups in text boxes (for eg. doesn't appear in the Terminal Emulator where it would be very useful), we need it to stay all the time on the screen (or have a way to call it any time) to replace the hacked osk (and therefore fix the instability of the displaying).

However Android's soft keyboard is not as good as the hacked one.

So I think that at our current state we should be able to write an osk that is run by android, and that also contains the keys for back, home, and menu.

Nevertheless, according to this source, Cupcake's input method framework is not yet finished.
[Touch HD Windows Mobile ROM Development] patp:
oops. it's msmvkeyb_toggle

gonna have to check my output more!
[Touch HD Windows Mobile ROM Development] gaelynx:
Ok thanks, msm osk is off now, but displaying still gets wrong after a while.

And ofcourse no way to go to home, menu or back.
[Touch HD Windows Mobile ROM Development] patp:
So can we say teh display problem that happens after a while is not to do with the msmvkeyb OSK?