yashsingh1/xdaforums huggingface dataset:
[Touch HD Windows Mobile ROM Development] Rayzer HD:
sry that im break the osk discussion but i have a question

i did compile my first kernel and want to know what i have to do when i change or make a new diff?

have i do all steps in the wiki after and with this patch -p1...?

edit: i did use the diff from cyber, but the device dont boot with my kernel i did no changes in the dif... its crazy^^

Rayzer HD
[Touch HD Windows Mobile ROM Development] orux:
We need more information to help you:

patch applied correctly, without errors?

no compile errors?
[Touch HD Windows Mobile ROM Development] Rayzer HD:
not realy... no errors...

what i have to do after change something in the diff?

1. patch

2. make config

3. export PATH

4. make zImage

is it right?

Rayzer HD
[Touch HD Windows Mobile ROM Development] CyberSalsero:
0. make config

1. patch

2. make

3. export PATH

4. make zImage

another question the diff file is create by make config, ca you explein us how to do this?

tnx
[Touch HD Windows Mobile ROM Development] Rayzer HD:
thx but if do it again there will come errors ok i give up i cant interpretate the errors and i hope u will make best of it... i will develop then games for android like i do it atm for winmo ;)

Rayzer HD
[Touch HD Windows Mobile ROM Development] orux:
You should not do changes directly in diff file. You have to apply the diff, then do changes in code, or files. Then get a new diff.

You need to undo a patch (-R option) before apply it again.

Don't desperate ;) this is an interesting world. We need more people here than writing games for android.

There are a lot of tutorials about patch, diff and git. Try again.

A diff file is created with diff app. You can get a diff, if you are in kernel directory, with:

git diff > xxxxx.diff
[Touch HD Windows Mobile ROM Development] CyberSalsero:
tnx orux!

Well, and the other files... android files, how you make them?
[Touch HD Windows Mobile ROM Development] CyberSalsero:
I tried, but it gives me an empty file :(
[Touch HD Windows Mobile ROM Development] gaelynx:
Well I'm not so sure because I just left my Blackstone with Android running (Home screen) for 20 min with msmvkeyb off and the displaying was alright this time, then I played around with the UI for a little while, still no problem..

It's definitively more stable!

The displaying getting wrong with msmvkeyb off only happened once for me (at post 100) and that was just after I change msmvkeyb to off for the first time.

So after that time, so far, the displaying doesn't seems to have any problem anymore.
[Touch HD Windows Mobile ROM Development] orux:
Try:

If the patch creates new files, you need to add them to git:

git add new-file.c

Then:

git diff HEAD > XXXXX.diff
[Touch HD Windows Mobile ROM Development] CyberSalsero:
Ok tnx...

Have you any tutorial about?
[Touch HD Windows Mobile ROM Development] jonlar:
SD card detection gpio pin

Hi! I've been following you efforts and I'm happy for the progress so far.

I have been debugging the issues with the sd and I found out that it's the wrong gpio pin that is used in board-htcblackstone.c. A bit of tracing gave that gpio pin #38 [1] is the one that shows the attach status of the sd card. Gpio #39 in VolUp and #40 is VolDown by the way.

Card detection works with this change but the kernel still has problems to access the card. Using the bundled micro-sd [2]. I'll pick up some other brand during the week. Any suggestions on brand/size?

Looking forward to move to the 2.6.27 branch.

[1] Not sure about the gpio numbering scheme but this is the number to pass to gpio_get_value(int)

[2] Transcend microSD HC class 4 8GB; http://www.transcendusa.com/Support/DLCenter/Datasheet/TS8GUSDHC4.pdf
[Touch HD Windows Mobile ROM Development] orux:
http://www.kernel.org/pub/software/scm/git/docs/user-manual.html
[Touch HD Windows Mobile ROM Development] CyberSalsero:
ok tnx... now i'm working .27 kernel

Have you any diff to start my tests?
[Touch HD Windows Mobile ROM Development] body85:
if anyone needs an tester PM me :-) i would like to help!
[Touch HD Windows Mobile ROM Development] patp:
So... it seems we have a whole load of developements in the past week:

Cybersalsero - made some config changes which seem to have enabled a bunch of hardware to be detected; got SD booting (which was actually working all the time in Orux kernels, but not noticed because it doesn't work with all cards!)

Orux - ported to .27 kernel

Pichurri - added support for bottom row buttons

Jonlar - debugging the SD card problem and othe gpio stuff.

have I missed anything? It would be good if someone with more technical knowledge than me could summarize on wiki and for the front page. Are ther various diffs compatible with each other or does it break things if they all get applied?
[Touch HD Windows Mobile ROM Development] xmoo:
Pichurri - added support for bottom row buttons

wich buttons are working then???
[Touch HD Windows Mobile ROM Development] orux:
There is a kernel .27 with support for ALL buttons. Pichurri was correcting some bugs. I expect he will be able to post zimage + diff soon.
[Touch HD Windows Mobile ROM Development] pichurri:
Sorry the delay Orux.

Here it is (extracted from just updated wiki):

Running Android 1.0

1. Disable the PIN from wince

2. Unzip to your SD card (it should create a directory named tmp):

http://www.gavero.com/pichurri/blackstone/android1.0/android_1.0_2009-03-03.zip

3. Unplug your phone from the USB or configure it to use "Activesync" and not "Disk Drive".

4. Run haret.exe on your phone (under /tmp/boot)

Enjoy.

Again, great work from Orux (Hard buttons).
[Touch HD Windows Mobile ROM Development] oNNoZeLe:
As a firsttimer, i am running you supplied package but it stops with 10 times:

mmc1: Command timeout

the previous line was:

msm_rtc msm_rtc: setting system clock to 2009-03-03 15:19:08 UTC (1236093548)

FYI i guess

when i release the SD from its socket is displays a statuschange from 1 to 0.

inserting the SD back in again displays the statuschange from 0 to 1 and showing the 10 times timeout again.
[Touch HD Windows Mobile ROM Development] scottyuk:
I've also tried loading Android for the first time, and i also hung on the same line, but i tried a few more boots and it seemed to get further each time.

I think i get to the part where in starts loading the Android files and then i get the following messages.

cannot find 'system/bin/sh, disabling 'console'

down to

cannot find 'system/bin/installd, diabling 'installd'

And thats where it hangs for me.
[Touch HD Windows Mobile ROM Development] 1337_V1k1n6:
??

I tried the posted files, and it boots perfectly. hardwarebuttons works and i can send / receive sms..

keep up the good work
[Touch HD Windows Mobile ROM Development] mücke007:
Congratulations. Works very well with me.

How can I do access data with the Filebrowser ? Are there USB drivers?

mücke007
[Touch HD Windows Mobile ROM Development] scanny:
Hi...what's your sd card?with mine (trascend) won't work!
[Touch HD Windows Mobile ROM Development] mücke007:
SanDisk 8GB micro SDHC

mücke007
[Touch HD Windows Mobile ROM Development] xmoo:
Same problems again with the sd-cards.

For me it worked.

16GB SDHC SANDISK

Ooh my god.

Time is working, signal is working buttons are working.

Only button not working a.t.m is the Power. The Volume up down work as scroll.

Some apps aswel arn't working correctly.

I think next hing to do is just like the kaiser, getting good battery drivers.

I don't know if they already fixed the battery ? issue...

Good job!
[Touch HD Windows Mobile ROM Development] orux:
There is a lot of interesting source code for sapphire (blackstone cousin) in android repo:

http://android.git.kernel.org/?p=ke...01eac78495b4e41643356a52888b43e2e030a;hb=HEAD

I am going to start playing with camera. It seems compatible with our device.
[Touch HD Windows Mobile ROM Development] CyberSalsero:
Superb!

It Works very well!

We now must investigate about callings and a menu button!

Now I'm @ work but this evening I can help you.

Tnx Orux, tnx Pichurri!!!!

When u can, post your diff file.

p.s. now the screen timeout not hangs the phone!

Great work guys!
[Touch HD Windows Mobile ROM Development] patp:
Looks amazing. Lots of stuff in the commitdiff of "[ARM] sapphire: Initial import of Sapphire board support" especially.
[Touch HD Windows Mobile ROM Development] technononsense:
I've looked into the sd card issue and it seems that we cant use class 2 cards. my HD (orange uk ) was bundles with a class 2 sdhc sandisk card that wouldn't work. However, using a class 4 card does.
[Touch HD Windows Mobile ROM Development] mücke007:
So I have a class 2 card, and it works for me .

mücke007
[Touch HD Windows Mobile ROM Development] 1337_V1k1n6:
class 2 card

erm.. I have a class 2 card also, and everything works fine.. :D every time :D
[Touch HD Windows Mobile ROM Development] schreda:
i have also a class2 card but it work only every 2. or 3. try...

it hangs at mmcblk0: p1

i want to help developing, i have some knowledge about coding, but not on linux! Is it easy or should I let the pros do?
[Touch HD Windows Mobile ROM Development] Emblema:
I have a model 4 and not working
[Touch HD Windows Mobile ROM Development] Bl@ck:
moved post to correct place :P
[Touch HD Windows Mobile ROM Development] quale:
Hi, it´s my first post on this thread, and i want all you to know that i can call and send sms with android!!!!!

Android Rules!!!!!!!!
[Touch HD Windows Mobile ROM Development] markusmuster:
Sorry, does not work for me.

All I get is:

...

/init: line 4: mkdir: not found

/init: line 5: mount: not found

mount: mounting /dev/mmcblk0p1 on /mmc failed: No such device or address

mount: mounting /mmc/tmp/system.e2img on /system failed: No such file or directory

mount: mounting /mmc/tmp/cache.e2img on /cache failed: No such file or directory

A N D R O I D init:cannot find /system/bin/sh, disabling ´console´

... cannot find servicemanager

... cannot find mountd

... cannot find debuggerd

... cannot find rii

... cannot find app_process

... cannot find mediaserver

... cannot find dbus-daemon

... cannot find installd

and hangs here. Seems like a classical linux boot failure when not finding it's root/boot device

I've a transcend 8GB SDHC Class 6 card shipped with my phone. I'll try it tomorrow with another 4GB card.
[Touch HD Windows Mobile ROM Development] patp:
Please, help to keep this thread clean. we have a testing/discussion thread so that developers can easily find things in this thread. It is VERY helpful to have lots of people trying it out, but please report your findings on the other thread! Thanks.​
[Touch HD Windows Mobile ROM Development] bimboles:
I'm having exact same issue with the 8gb Class 6 card that came with phone.
[Touch HD Windows Mobile ROM Development] markusmuster:
Of course you are right. But I ran Linux on (quiet) every supported device yet and I've experience in development of linux drivers/applications for over 15 years right now. My first was Kernel 1.x on Amiga 1000 for which I developed a driver for the Tseng ET4000...

I've read the complete thread several times but there aren't enough informations about getting deeper in the development right now. I'm willing to help but please post some useful infos on remote console an so on.

That's the only way ppl with fundamental linux skills can help.

(and yes, i do not love windows at all - All I run for years is linux and the only reason I set up another computer with windows was my mobile toy. I develop software mostly for linux and from time to time for Windows but that's kindly rare)

Thanks in advice.
[Touch HD Windows Mobile ROM Development] stefh:
First of all, great work you guys! Really thankfull!

Couple of questions:

Is it possible to create a shortcut inside Android to reset the phone? Taking of the back cover all the time gets annoying. However I have no idea if this takes much effort to implement? My feeling says it should not be that difficult.

About the screen: I think the calibration is slightly positioned too high and should be a little lower. Try for example to tap the top of the clock or the topbar. The topbar does not respond if you press it at the lower end or in the middle. It starts to respond when you hit the upmost top. (At my device at least) Or can this easily be altered by myself by just changing the values in default.txt?

As all the menu animation and stuff still goes much smoother on for example the G1, I was wondering if this had to do with the higher resolution or is it because of not all the possible hardware acceleration being enabled? Maybe this is too early to ask.

And is it difficult to option for a lower resolution to see if the smoothness increases? I would not mind because of it also results in the OSK being bigger for my fingers to press?
[Touch HD Windows Mobile ROM Development] pichurri:
Hello markusmuster,

Plz have a look at the wiki, there is plenty information on getting started in development for blackstone's linux kernel, which is the main objective now. Personally I would like to have Power management support, phone calls, and sms, so that I can switch to android, :)! Also GPS and wifi would be really nice, but so important (for me...).

Wiki link:

http://wiki.xda-developers.com/index.php?pagename=BlackstoneLinux

Diff is already in the wiki.

Ps: Sorry for posting the instructions here, :p.

People, plz take all the discussion to the other forum:

http://xdaforums.com/showthread.php?t=468360
[Touch HD Windows Mobile ROM Development] johndox:
I just tested SD write access. It works. (I will update the wiki.)

Regarding the SD mount problem. The Transcend class 6 card, shipped with my device definitely doesn't work.

I looked at the partition table: the partition starts at cylinder 10 and not at 1, as I expected (WTF?), but that was not the problem)

I repartioned and formatted both the Transcend and a SanDisk class 4 card, put pichurri's files on both and booting with SanDisk succeeded on every try, while Transcend failed.

So there definitely is a problem with the shipped Transcend cards.

At least the simple "mounting /dev/mmcblk0p1 failed"-posts can stop for now until someone has an idea how to fix it. It is a known problem and there is no solution yet.
[Touch HD Windows Mobile ROM Development] markusmuster:
One thing I noticed while examining the msm_sdcc.c driver is that the kernel parameter "msmsdcc_id=2" is not referenced anywhere in the whole kernel. I know that the blackstone driver was forked from raphael/tpro driver where this was relevant.

Did I missed something or does anyone know where it does come from?

Another (maybe stupid) question is: Does anyone knows a way to get the kernel messages (dmesg) out of the device? Connecting to HaRET gives the HaRET console only.

Thanks in advance
[Touch HD Windows Mobile ROM Development] patp:
In the Raph thread several ppl mention having to set it to =3 to get a boot. I tried it to no avail, unsurprising if it's been deprecated.
[Touch HD Windows Mobile ROM Development] markusmuster:
Seems to be a problem with Class 6 cards at all. I've tried it on another SanDisk C6 Card with no success too. Tonite I'll make a test with a third one (NoName Class2) Card. If this works, it seems to be speed related.

The msmsdcc module knows several parameters (* are default values):

msmsdcc_4bit=0|1*

msmsdcc_1bit=0*|1

msmsdcc_pwrsave=0|1*

msmsdcc_nopwrsave=0*|1

msmsdcc_fmin=144000*

msmsdcc_fmax=32000000* (in .28 kernels it is 50000000)

I just played with them a little bit (no success), but the main problem must be in in ./arch/arm/mach-msm/board-htcblackstone* forked from board-htcraphael*

There also seems to be quiet interesting parallels to

"http://android.git.kernel.org/?p=kernel/common.git;a=tree;f=arch/arm/mach-msm;h=a1c88fb4dd93914401e5ecc53ee3fec645570de6;hb=HEAD"

Both sources are talking to the same hardware ;) But I need to sort out everything first and run a diff over it...
[Touch HD Windows Mobile ROM Development] orux:
msmsdcc_id=2 is not necessary in our device. It comes from raph, where sd can be on sdcc slot 2 (raph100) or slot 3 (raph800).

We have like raph100, and the slot 2 is selected hardcoded.

This is the correct kernel in android (msm-2.6.27). Look at shappire board.

http://android.git.kernel.org/?p=ke...d-msm-2.6.27;hb=refs/heads/android-msm-2.6.27

Annex wince dmesg dump. I suppose you want wince dmesg, because Haret only works with wince. I you want linux dmesg, use angstrom dist (wiki).
[Touch HD Windows Mobile ROM Development] patp:
The error is a "Command timeout" - maybe some cards are a bit slow.

What does CONFIG_MMC_MSM7X00A_RESUME_IN_WQ do? Have we got it enabled?
[Touch HD Windows Mobile ROM Development] tomj333:
I dont know if this is a know fact or not but, you can recive and make calls on andoid 1... only thing is it does not detect the speaker/mic so obviously you cannot talk or hear but it does allow network activity.
[Touch HD Windows Mobile ROM Development] Emblema:
one information:

if I want to try to compile autonomy in my kernel, the result is ON ram or OFF ram ?

Thanks to all
[Touch HD Windows Mobile ROM Development] markusmuster:
I want a way to get the printk messages somewhere else than on screen only. I do not have a dev-board and so no serial port for those messages. I can remember to get them over usb but cannot find that pages right now....
[Touch HD Windows Mobile ROM Development] markusmuster:
Would guess that too, but Class 6 cards should be faster than the lower ones, and thus your suggestion should not be valid. But what would be when the C6 cards are too fast?

Anyway that "Command timeout" message appears to be in IRQ context as far as I've reviewed the code. Most parts of the blk100 diff is based on raph code. Even most hasn't be renamed yet. There's really much, much that could go wrong... I still need to dive into the code - deeep (And what I really need is something like kerneldebug over USB first {If I could only remember that page where Ive read about that})

;-) Don't know yet ;-)

Another suggestion: What's the devicename of the internal datastorage (imgdevname=/dev/???) ? Perhaps I could boot it from the internal flash to get at least a running kernel for further debugging...
[Touch HD Windows Mobile ROM Development] jonlar:
Personally I use Angstrom initrd to debug the kernel. With that one you can login over ssh as root. Look in the wiki for instructions.
[Touch HD Windows Mobile ROM Development] markusmuster:
Thanks for the hint! I'll try it tomorrow.
[Touch HD Windows Mobile ROM Development] jonlar:
Transcend SD

Enabled debugging of the mmc subsystem to try to track down the Transcend issues. These are the logs leading up and including the first command that times out. Does anyone have any tech knowledge of the SD protocols and can interpret this?

[ 403.775523] msmsdcc_platform_status_irq: 102

[ 403.775615] mmc1: Slot status change detected (0 -> 1)

[ 403.792094] mmc1: clock 0Hz busmode 1 powermode 1 cs 0 Vdd 16 width 0 timing 0

[ 403.794169] mmc1: clock 144000Hz busmode 1 powermode 2 cs 0 Vdd 16 width 0 timing 0

[ 403.796214] mmc1: clock 144000Hz busmode 1 powermode 2 cs 1 Vdd 16 width 0 timing 0

[ 403.797221] mmc1: starting CMD0 arg 00000000 flags 000000c0

[ 403.797252] mmc1: msmsdcc_start_command: op 00 arg 00000000 flags 000000c0

[ 403.797679] mmc1: req done (CMD0): 0: 00000900 5f590000 3c1b7f80 0a40003e

[ 403.803233] mmc1: clock 144000Hz busmode 1 powermode 2 cs 0 Vdd 16 width 0 timing 0

[ 403.804332] mmc1: starting CMD8 arg 000001aa flags 000002f5

[ 403.804362] mmc1: msmsdcc_start_command: op 08 arg 000001aa flags 000002f5

[ 403.805217] mmc1: Command timeout

[ 403.817454] mmc1: req done (CMD8): -110: 00000900 5f590000 3c1b7f80 0a40003e

...and more commands + timeouts

My plan is to buy an microSD->SD adaptor and try to access the card in linux but using another host-controller.
[Touch HD Windows Mobile ROM Development] patp:
SDIO spec is available here:

http://www.sdcard.org/developers/tech/sdio/sdio_spec/

Lacks detail though. Little mention of CMD8
[Touch HD Windows Mobile ROM Development] pichurri:
Also you can telnet to the latest version of Android. Same IP as Angstrom 192.168.0.206.
[Touch HD Windows Mobile ROM Development] mpc8248:
Hello Developers, the maximum clock frequency for identification mode is for transcend cards in a range of 100 up to 400kHz.

So it should have the right timing if the baudrate generator is initialized proper. On my screen i can see the line

[21.102946] mmc1: MMC clock 144000 -> 32000000 Hz, PCLK 66000000

Maximum clock is 25MHz for data mode (Transcend card)

My SanDisk 8GB HC also has timeout and didnt work.

In summery we have a timeout with set_sdcc_host_clock (21,144000) ..why ever 144kHz thats ok or BRG? Fast clock in data mode with set_sdcc_host_clock (21,32000000) is with 32MHz too fast => If the config registers on the sd card are not accessible, its not possible to set up maximum speed correct. In the CSD (Card specific data register)the TRANS_SPEED field (register) is the info for maximum clock typical value is 25MHz. Maybe the input clock of the chip is different (display or any other HW demands) and PLL or dividers have to be tuned a little bit. Mostly clock stuff is not autodetect :-) So we have to measure the SD clock pin to know if we have a problem with BRG (Baud rate generator)
[Touch HD Windows Mobile ROM Development] patp:
we don't know. ask in the discussion thread. read the last 50 posts first!
[Touch HD Windows Mobile ROM Development] stoolzo:
not really dev but may be some help, delete if need be.

I am getting this problem as well. It seems to be intermittent in some ways. I got it first with this latest version when trying on RAM, one of the chaps in the DEV thread told me to try offram, that worked a few times but now i am back to this problem again. I initially solved it "again" by closing explorer before clicking run on haret, that worked a few times and now again it doesnt. This is very odd indeed. It is as if something is getting corrupted somewhere in the installation files. TO test this I deleted everything and low and behold when i tried again it worked a few times and now I am back to it not booting again. I Wonder if anyone can explain this?
[Touch HD Windows Mobile ROM Development] xmoo:
My off ram worked 2 times.

Now everytime I boot it, it gives me a error in android.

Something about loading the home screen.
[Touch HD Windows Mobile ROM Development] oNNoZeLe:
i don't know if this is any helpfull info but i just ran into this blog posting..

Maybe there are some brains that can use this info to develop progs to make porting easier to HD..

http://blogs.technet.com/deviceshastra/archive/2009/03/08/installing-android.aspx
[Touch HD Windows Mobile ROM Development] DarkWolve:
Did you even read this? It has NOTHING to do with porting anything to anywhere!

This is about the Android SDK (SDK = Software Development Kit)

pls read first THEN post!!

(sry for this post!!!)
[Touch HD Windows Mobile ROM Development] oNNoZeLe:
Do you really think that i didn't read this before posting? :rolleyes:

Maybe you missed the line

So i guess that there is no need to develop special tools/software to get Android 100% HD compliant, my bad..

@Mods, please delete all the 3 messages to keep this thread clean.
[Touch HD Windows Mobile ROM Development] pichurri:
Just for the sake of clarifying, it is actually useful. I had to install the android SDK to get some of the stuff that everyone is running today on their Blackstones. Have a look at:

http://wiki.kldp.org/wiki.php/AndroidPortingOnRealTarget

http://elinux.org/Android_on_OMAP

The thing is that you actually need the emulator that comes with the Android SDK to get the /data and /system contents produce the Android images (these 2 dirs reside in the ext2 images that reside in /tmp, these are mounted on the init)

Furthermore, if you want to have a look at the init, read:

http://www.d33z.com/dan/index.php?title=Customizing_Android_Initrd

PS: I'm adding these 3 links to the wiki