yashsingh1/xdaforums huggingface dataset:
[Touch HD Windows Mobile ROM Development] Micr0mega:
I've been following this thread since before I registered here, so I thought I'd make a little contribution myself now ;-)

I've been playing around with several builds you guys provided here and in the dev thread. I was currently testing the one provided by CyberSalsero, but I seem to have great difficulties even getting passed the PIN code screen :( When I enter my code, it will simply state that it is incorrect, while I am sure it is not. There does not seem to be a 'cancle' button like in WiMo, only the 'emergecy' button, where I can't get any further either. I also tried removing my SIM card, but then it would simply not get passed a notification that says there is no SIM card.

I've also exprienced an exception from messaging (comm.android.mms) a few times.

Also, I have not seen the new OSK yet, only the old one with the green/red/blue square. Should this be the case at entering the PIN code?

So, I have not been able to see the home screen with clock in this build yet. I hope this info might prove some use. You all are doing a terrific job, I am refreshing this page like every 5 minutes :-P
[Touch HD Windows Mobile ROM Development] xmoo:
When I boot Android 1.0 it prompts me for a PIN, when I enter my SIM PIN it says its not correct (but I'm sure it is).

The only currently known way around this is to disable 'PIN required to use phone' in windows. (By the way: this means your radio works. Congratulations.)

Faq on page 1!
[Touch HD Windows Mobile ROM Development] abats:
I have no such file in my bin directory. Like 20 others but not "arm-none-linux-gnueabi-cc". Don't get it, I downloaded the package described in the wiki.
[Touch HD Windows Mobile ROM Development] El Massman:
is there any advantage to using the off ram files? from what i've seen android seems more responsive when run from the system memory. or am i just imagining it?
[Touch HD Windows Mobile ROM Development] xmoo:
Well if you want to use android...

you need to have it off-ram.

Or do you want to stick to 96mb ram and file space...
[Touch HD Windows Mobile ROM Development] Micr0mega:
Thanks, that fixed it, I should have read that...

Though I have not managed to pop out the new OSK. Notepad does not seem to work at all, the screen is just black.

I also asked someone to call me, but when I received the call, the phone app crashed pretty bad. Wifi doesn't work either.

Something I just noticed: the light sensor works! The backlight dims if i put my finger on it and increases again when I "show" it the daylight again :)

One more thing: I was unable to find a real "back key". the F4 and END key both take you back to the home screen, but there is not a way to go back a screen. Quite annoying when you are navigating in the dev-tools, but are stuck, because you can't go back.
[Touch HD Windows Mobile ROM Development] xmoo:
Well, the keys should be mapped first.

Home back etc.
[Touch HD Windows Mobile ROM Development] Glideh:
Actually, I think [Esc] is the

default back key (can go up on

the menus) isn't it ?
[Touch HD Windows Mobile ROM Development] Micr0mega:
[ESC] doesn't work here.

But I did find out something interesting. Try this:

Go to the home screen with the clock. Press both of your fingers (nails) on the screen and keep pressing. Move one to the right and back. Move the other to the left and back. Move both in the same direction, the screen moves like normal. Now, try moving your two fingers in opposite directions and you will see the screen barely moves.

Looks like multi-touch capable to me, doesn't it? :D
[Touch HD Windows Mobile ROM Development] Mykstar:
I get to the console and can configure screen but then nothing happens. It looks like i get errors about mounting the SD card and directories on the SD card (/system/bin/*someprogramname* before the screen calibration but I dont get to the Android boot screen. I've tried all the files in the post so far :(.. anyone had the same issue ?
[Touch HD Windows Mobile ROM Development] CyberSalsero:
QUICK TIP:

F1 in android to open options!

:)
[Touch HD Windows Mobile ROM Development] stefh:
Ok this is my experience so far with the CyberSalsero update. THANKS MAN!

Nothing new that was not mentioned before I think.

- Time is wrong, but clock works.

- Shows right network and signal strength properly.

- Battery shows question mark

- I can see my pictures on the SD card and scroll through them in the gallery. looks good. When the pictures get listed I don't see a thumbnail however.

- calendar does not work.

- error message: the application messaging (process com.android.mms) has stopped unexpectedly. please try again.

- using the dialer works. Pressing ENTER after a entered number it starts dialing but then I get two error messages:

the application messaging (process com.android.mms) has stopped unexpectedly. please try again. and another non detailed error. and then my phone locks up.

- camera gives me these white and gray blocks on the display, I see a camera icon in the bottom right corner.

- If I want to go back I use F4 or sometimes ESC.

- I can start playing SNAKE (slow) by pressing up after starting SNAKE.

- I found the official on screen keyboard too small. Somehow it looks bigger on XMOO's picture. For my fingers it is really not ok.

- Calculator works nice.

- When using the overlay keyboard the screen gets wrong alignment. (OLD NEWS)

- Music player works, although slow. The sound card doesn't give any output however, sound driver needed I guess.

I hope there will be found a work around soon for the "hardware" buttons to work. I would not care for the volume rocker to really work as volume control. This can also be done manually inside the software.

I was also wondering if it is possible to let the screen output a lower resolution as everything is very small in 800x480. Maybe there can also be a part of the screen reserved for soft "hardware" buttons. (Like MENU)

The lower resolution will probably also result in better screen/animation smoothness. Maybe I am wrong.

(e.g. When I open the bottom menu that slides open to the top, it will go slower when more icons get visible.)
[Touch HD Windows Mobile ROM Development] Rewpparo:
Apologies, the name is arm-none-linux-gnueabi-gcc (just checked), but the kernel handles that anyways, so let him worry.

-->It doesn't change the fact that all you did wrong was to forget a dash at the end of your kernel compile command (make zImage blabla), as I said two pages ago. Don't forget to execute the EXPORT line before you try it.

Try that line again and post the result if it doesn't work.
[Touch HD Windows Mobile ROM Development] furrypotato:
I got a question for developers. I've been trying to keep up and learn a bit about the process.

So the hard part about all this is getting a kernel to work, is that right ?

And so people are trying to get a linux kernel to work which android basically uses ?

And from booting up I see it's a kernel developed by Raphael/Diamond guys, and the the specific Android bits get added ( diffs ?)

But people keep pointing out how similar (not exactly but a lot) our processor hardware is to the G1. So why not use the G1's kernel as a base instead ? I assume the source code is available as people have been hacking it. Why is it better to be starting from scratch like this ?

Just something thats been bugging me today, sorry if it's a stupid question.
[Touch HD Windows Mobile ROM Development] CyberSalsero:
Yes I confirm them all.

The errors I think is because the os can't write on SD.

In effect when I try to insert a new contact it works, but when I try to save it crash!

Another example is the thumbnail: I think that android try to create a db file with its.

Sms and mms, notepad and email same problem.

We must investigate about the write permission on sd!

On boot linux give a warning message about ext2 fs....
[Touch HD Windows Mobile ROM Development] stefh:
Maybe it works with a microsd card formatted in ext2 or ext3 format? Have you tried. Of course it should be compatible with FAT32. But it is worth a try.

NB on wiki:

On all versions it says that it is impossible to run from SD Card and that you need to put the files on the internal memory of the device itself, but it just works fine from SD. On RAM, all versions I tried and OFF Ram only CyberSalsero's version so far.
[Touch HD Windows Mobile ROM Development] Mykstar:
I can't get the new image booting at all.. I've DL'ed and extracted the ZIP from the dev thread here :

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

and placed in tmp folder in root of the SD Card.

Every alternate boot I get the OSK appear. I get to the point where i can calibrate the OSK which says is successfull but nothing after. I dont get to the android boot screen :(

I do get errors on the console about mounting /system/bin/*programname* and /dev/mmcblk0p1 on /mmc.

last line in console : 3.641193] init: cannot fin /'system/bin/installd, disabling 'installd'

alternate boots just crash before on the line :

set_sdcc_host_clock 2000000, 190080

Anyone got any ideas ?
[Touch HD Windows Mobile ROM Development] stefh:
I was exactly thinking the same thing since the beginning. But the processor is not the problem as Android supports the most. And of course it is not just about the CPU. According to some website it also has the same soundchip and stuff, but when digging deeper there are actual differences. Although, finding them out is difficult als probably only HTC knows what they used exactly.

So the way I understand it, the problems lie much deeper as several controllers seem to be different. But I am not sure as I am not a developer.
[Touch HD Windows Mobile ROM Development] stefh:
Have you changed 64 MB in 76 MB as stated a couple of pages back? I never tried with 64 MB as I directly put in 76 MB. And it is working fine. It also loads very quick in the HARET launcher. But I also use the standard factory rom as I don't want to lose my warranty. But maybe I already have by running Android... :P
[Touch HD Windows Mobile ROM Development] Rewpparo:
I'll explain the relationship between device, kernel and android for a bit. First, know that we _ARE_ using the G1 and raphael/diamond kernel code.

The kernel's goal is to provide an interface between hardware and software. For example, if a software wants to draw something on the screen, it uses an interface the kernel provides. The kernel uses a driver to convert orders from this interface to a language the device understands, and perform the task. This allows software to ignore completely what device it's running on, but only use an interface that the kernel is in charge of making work.

In the case of Blackstone, they've had problems with the screen.

When android tries to draw something, it asks the kernel. The kernel uses a standard interface, that is the exact same for every screen, be it a PDA screen or 26 inches desktop flat screen.

But not every screen accepts the same input format for the image, so it needs to be converted. A part of the kernel called MDP (Mobile Display Processor) is in charge of that.

Then it is sent to the screen. This is done though an interface called MDDI. MDDI needs a driver for the specific screen used by the device.

Most of the work was already done. MDP was working, MDDI was working, thanks to the G1 code. However, because Blackstone has such a big screen, the LCD controller, the chip that controls the screen, is different from G1. G1 had Toshiba, Blackstone has Epson. This means that they needed a brand new MDDI driver for the screen controller.

They also had problems with the fact that MDDI and MDP were not communicating right. They had to make some tweaks, but that took a while as the options were poorly documented.

So, we're lucky that the major parts of graphic processing was working thanks to G1 and raphael code, and that the hardware was almost the same, otherwise it would have taken months of hard work to code everything, assuming they had proper documentation. Years without documentation.

They had the documentation for the Epson LCD controler, so they were able to make a quick driver. It's far from perfect, but it's sufficient to draw things.

However, screen power management, for example, is not implemented, that's why android crashes if you leave it alone for a minute. Android tries to access the kernel interface to shut down the screen, but it's not hooked to anything, so it crashes. That's an example of the work that needs to be done.
[Touch HD Windows Mobile ROM Development] patp:
I think if you flash using the USPL you can restore to shipped status. Of course if it broke you might not be able to! Personally I can't see much benefit for this device - my previous was a Hermes, which was not adequate in it's shipped config, but the factory HD rom seems pretty stable and quick when tweaked. Can't see why anyone bothers.
[Touch HD Windows Mobile ROM Development] Mykstar:
I tried changing the mem to 76MB in default.txt but still pauses after calibration. The OSK still works. I can touch the keys etc but wont boot as far as the android loading screen.

Does anyone have really simple ste by step instructions on getting to boot. Im really stuck now.
[Touch HD Windows Mobile ROM Development] stefh:
Yeah I am actually pretty happy with the tweaked factory rom. But I would actually love to try dutty's 1.9 version with all the new and prettier stuff inside! It's tempting.

But I am a little bit affraid to do it because of my warranty. I just have the HD for 3 weeks or something, maybe that's the reason.

Thanks for pointing out the USPL option. But let's stay on topic. :)
[Touch HD Windows Mobile ROM Development] orux:
Try another sd, if you can.

My stock sdhc 8gb does not work with linux.

An old sd 515mb yes.
[Touch HD Windows Mobile ROM Development] Rayzer HD:
i want to add that there are no problems with sdhc! on my 16gb sdhc from sandisk android boots fine :)

Rayzer HD
[Touch HD Windows Mobile ROM Development] Mykstar:
Has anyone booted with a Transcend 8GB ??

Perhaps the format of the card makes a difference.. going to try and re-format my card.
[Touch HD Windows Mobile ROM Development] orux:
My transcend sdhc 6 8gb does not work.
[Touch HD Windows Mobile ROM Development] BigDaemon:
http://www.portalesalsero.it/public/Android-Cyber.zip doesn´t work for me either.

I tried it from SD and from device, with 64M and 76M, it always stops before the screen-calibration (i never come there with this files)....

By the way: i guess it has nothing to do with the SD/SDHC, don´t ask me why, just a feeling ;-)

//edit\\ ok, found it, the Folder on my SD was TMP not tmp (capital letters), so it won´t work :-)

Changed it, now i came until "enter pin", just rebooting to disable pin :D
[Touch HD Windows Mobile ROM Development] CyberSalsero:
4 all that not boot

check the path! It's case sensitive and must ho be:

YourSD/tmp/..

My sd is a kingston of 8gb sdhc!!!
[Touch HD Windows Mobile ROM Development] jura55:
Side by side

Hi, interesting article about winmo and android running simultaneously:

http://www.linuxdevices.com/news/NS9339320882.html
[Touch HD Windows Mobile ROM Development] orux:
Does anyone know if android lets you change font and icon size?

We have a new kernel, with new functionality, but letters and icons are ultra-small in android. We don't know if it is an android or a kernel issue.
[Touch HD Windows Mobile ROM Development] El Massman:
it does, it's under spare parts and then font size. there's 7 options ranging from extremely small to extremely large. not too sure about icons though.
[Touch HD Windows Mobile ROM Development] orux:
Thanks,

With extremely large fonts, still not readable. Strange.
[Touch HD Windows Mobile ROM Development] body85:
in the .zip file are /tmp/BOOT/ (with the files insert...)

did i have to make a new tmp folder??? like /Storage Card/tmp/tmp/BOOT

or u mean /Storage Card/tmp/BOOT

both things dosent work wor me.... :-)
[Touch HD Windows Mobile ROM Development] orux:
Should be: /Storage Card/tmp/BOOT
[Touch HD Windows Mobile ROM Development] body85:
dont worked...
[Touch HD Windows Mobile ROM Development] CyberSalsero:
Any error or it freeze on boot?
[Touch HD Windows Mobile ROM Development] xmoo:
Mine still reboots :(
[Touch HD Windows Mobile ROM Development] orux:
Try this files:

replace only zImage.bin and default file.
[Touch HD Windows Mobile ROM Development] falluja:
i have the same problem, but when i get the on ram version and put it into the sd it worked, but its crazy when i get in into the android/interface
[Touch HD Windows Mobile ROM Development] idokk:
same here

hi

i got the same problem here .

from the errors i got , i can see that the line im having trouble with is :

"mknod /dev/mmcblk0p1 b 179 1" (in the init file in root.cpio.gz)

that line fails saying the device could not be found .

after this line , the system fails to mount the 3 ext2.img fs files and hangs a bit later .

my guess is that some sd cards aren`t mapped to "b 179 1" ... but i dont know how to help finding where they rally are ... you could also try and use the main device memory that i would expect to map to the same place in every device (or at least would be less versatile than SD cards .

im using 8GB Transcend card

hope the info will help .
[Touch HD Windows Mobile ROM Development] ugumba:
Just a wild thought: could this be related to the common issue of people not being able to flash their HD from their Transcend SD cards? (myself included.) The bootloader claims it simply can't find the file. Apparently Sandisk cards work fine in this respect.
[Touch HD Windows Mobile ROM Development] jimplode:
The 8Gb Transcend card doesnt appear to work with linux, I was able to run the CyberSalsero package from a SanDisk card but received the path not found errors with the Transcend.
[Touch HD Windows Mobile ROM Development] Caid444:
It works.

Pretty cool project. I have only been able to get it working with usb however. That means, if my phone is connected via usb, it all boots fine, but if there is no link, they keyboard doesn't show up at the top of the screen with Haret, and the process won't complete.

Is this normal?

Caid
[Touch HD Windows Mobile ROM Development] Rayzer HD:
sometimes u need more than 1 try.. its doesnt matter whether u have a usb connection or not

try to boot simply sometimes without usb and u will see it will boot normally but sometimes not ;)

Rayzer HD
[Touch HD Windows Mobile ROM Development] body85:
:eek:
[Touch HD Windows Mobile ROM Development] xmoo:
I think there is a problem or something with the drivers.

On the old Diamond raphael kernell. I booted from 16GB SDHC.

And now people witness problem with 8GB + SDHC....

Orux will try ur file.
[Touch HD Windows Mobile ROM Development] body85:
i´m using the SD card who comes with my HD... is that the prob?
[Touch HD Windows Mobile ROM Development] xmoo:
I press Run, but nothing happens.
[Touch HD Windows Mobile ROM Development] body85:
if u replace ONLY the zImage.bin it worked....

for me... the same prob :-)
[Touch HD Windows Mobile ROM Development] stefh:
Sometimes I get this at the end of the booting text, when booting for the first time after editing something inside default.txt and putting the card back in the phone:

.....

drivers/rtc/hctosys.c: unable to open rtc device (rtc0)

mmc0: host does not support reading read-only switch, assuming write-enable

mmc0: new SDHC card at address 9e33

mmcblk0: mmc0:9e33 SU08C 7761920KiB

mmcblk0: p1

phone then freezes. When I reset my device and start android again, it works.

(using included Sandisk 8gb microSDHC)
[Touch HD Windows Mobile ROM Development] xmoo:
You hhad the same problems booting on sd = reboot?
[Touch HD Windows Mobile ROM Development] body85:
nope.... hangs by booting on sd card.... (look the picture in my last post)

with "for me the same prob" i have mean that my old prob with the new zimage.bin are the same prob is....

sry for my english :-P
[Touch HD Windows Mobile ROM Development] xmoo:
Alright.

It workes.

I had to add a enter on bootlinux.

Boothing trough 16GB SDHC.

Thx Orux.
[Touch HD Windows Mobile ROM Development] CyberSalsero:
to body85:

mmm... Linux not finds the system files post the path with case.
[Touch HD Windows Mobile ROM Development] body85:
im downloading the Android Cyber.zip extract it to my storage card go to the BOOT root and run the haret.exe

my Device/Storage Card/tmp/BOOT/haret.exe

or did i have to copy other files to my device?
[Touch HD Windows Mobile ROM Development] mücke007:
Hi guys.

Here is a video how it works by me.

Video

mücke007
[Touch HD Windows Mobile ROM Development] xmoo:
Is it posible to give screen align point a function?

Cause I think this way we have to bind the keys....
[Touch HD Windows Mobile ROM Development] mücke007:
Sorry, my english is too bad.

mücke007
[Touch HD Windows Mobile ROM Development] CyberSalsero:
Yes, you must copy all files of the zip!!
[Touch HD Windows Mobile ROM Development] Rayzer HD:
hey how did u get in german?(du kannst auch in deutsch antworten, wenn du magst...^^)

Rayzer HD
[Touch HD Windows Mobile ROM Development] CyberSalsero:
great!!!

Hey xmoo why not insert my files in the first post?
[Touch HD Windows Mobile ROM Development] mücke007:
Hallo Rayzer HD

Das ist aber schön hier mal paar deutsche Worte zu lesen ;) . Ich stehe mit dem englischen etwas auf Kriegsfuß .

Das Android kann man doch umstellen auf "deutsch" :

Einstellungen - Region Text - Sprache wählen(Settings - Locale & text - Select locale )

War so was in der Art .

mücke007

P.S. mücke007 ist auch nicht mein richtiger Nick , aber für "Duron" habe ich die EMail nicht mehr und das Passwort hab ich vergessen . Ich hab mich schon versucht mit den Admins hier zu verständigen , aber die wollen oder können mich nicht verstehen. Somit bin ich hier als "mücke007" unterwegs.
[Touch HD Windows Mobile ROM Development] stefh:
OK I noticed after switching off the overlay keyboard, that there are still "glitches". Example: try to move the clock, you will notice some vertical stripes appear now and then.

BTW: Who cares about the language settings? I tried it in Dutch, but that really looks like poop. But hey I also ordered the UK version of the touch HD, as I don't like anything that has to do with computer stuff and is in Dutch. Translations are often very weird and don't make sense.
[Touch HD Windows Mobile ROM Development] body85:
hehe i know i have copyed the complete tmp folder to my storage card... ive mean that i have to copy other files to my device... what is the latest complete android pack who worked on the 8 GB card (the shiped one...)???

Deutsch: Geil deutsch... hier???? *gg* is ja mal geil vielleicht kann mir ja von euch einer helfen, hab den kompletten tmp ordner aus der android-cyber.zip auf meine speicherkarte kopiert die mitgeliefert war. bekomms da nich zum laufen...
[Touch HD Windows Mobile ROM Development] mücke007:
hallo body85

Wollen wir mal hoffen das wir hier keine Verwarnung kassieren , wenn wir uns hier auf deutsch verständigen ;) .

Ich nutze auch dieses Pack , aber in der default.txt hab ich kleine Änderungen.

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 msmts_calib=0x37b.0x3ca.0x72.0x72 msvkeyb_toggle=off"
bootlinux

Du kannst es auch mal mit :

mem=76M

versuchen , denn das läuft auch bei mir.

mücke007