yashsingh1/xdaforums huggingface dataset:
[Touch Diamond, MDA Compact IV ROM Development] kholk:
mmh... it looks like we can fix the bluetooth and WiFi issues using parts from hero's kernel if it integrates the MSM7200A modules.

MSM7200 and MSM7201 should share the same WiFi/Bluetooth/(GPS?) chip!

The MSM chipset is only an integrate that integrates CPUs, DSPs and wireless chips ;)
[Touch Diamond, MDA Compact IV ROM Development] phhusson:
1.Wifi just works

2.BT mostly works, the lacking part is only a matter of clocks, which are NOT the same

3.Anyway, for everything (Wifi/BT/GPS/Camera), we already have codes from various boards, they just aren't exactly the same, the problem being to know the differences mostly in term of clocks/GPIOs/vregs/RPC. (the last one being the hardest because wince API isn't the same at all as android's one)
[Touch Diamond, MDA Compact IV ROM Development] magicman0:
shouldn't getting this to work be a little easier since the Sprint HTC Hero uses 7201A?
[Touch Diamond, MDA Compact IV ROM Development] IceBone:
What happened to babijoee and his new pack? :(
[Touch Diamond, MDA Compact IV ROM Development] babijoee:
Sorry IceBone, i totally forgot to upload it when i went into uni. I'll do it sometime this weekend or early next week :)
[Touch Diamond, MDA Compact IV ROM Development] IceBone:
Oh, poppycock... :(
[Touch Diamond, MDA Compact IV ROM Development] bip91:
I'm quit suprising because i have a diamond which has a MSM7201A.

I understand better why RAPH kernel work better than DIAMOND one on my phone.

A good news for the thread, this means that Hero package would work on some diamond with the same CPU/ Archi ?
[Touch Diamond, MDA Compact IV ROM Development] kholk:
Hmm... The most important things here are the GPIOs... so... I was thinking that they was sharing the same GPIOs (and clocks/vregs/RPC), not for the camera, but for GPS.

I don't use GPS on my Diamond, but I wrote it only for helping users who uses it.

However, if they doesn't share the same addresses, then it's an hard work :)
[Touch Diamond, MDA Compact IV ROM Development] krylle:
This link may be a little help for die "Android on Diamond" project

http://developer.htc.com/
[Touch Diamond, MDA Compact IV ROM Development] qumani:
Gonna take a go at it...

I installed virtual box and ubuntu on my windows machine so that I could can take a stab at trying to port some of the hero build into what we already have and see if there is any better luck...

I have no linux or android programming experience, but I figure I might as well jump in. Figure I taught myself .NET and other programming. It helps alot when alot of the work is already done....... Alot of great developers have givin their time and work so that we could make it this far, I would just like to make a contribution.
[Touch Diamond, MDA Compact IV ROM Development] MrPippy:
1.6 on DIAM500

I've compiled a new kernel for DIAM500--only difference from the last one is the inclusion of SquashFS. I tried it with babijoee's 1.6 pack, and it works pretty well.

There's still no GPU accel or phone functionality, but it seems to use less RAM than 1.5 did. Watching logcat, GC is running much less often (as compared to 1.5, where it was running constantly), so 1.6 seems faster and more responsive.

As before, this is for mtype=2040 and DIAM500.
[Touch Diamond, MDA Compact IV ROM Development] gleng:
Yay! Thanks MrPippy.

I assume this is based on the same kernel version as last time?

Also, using your last kernel I did have phone functionality, just no microphone support. I could hear people but they couldn't hear me, and I could send and receive text messages.
[Touch Diamond, MDA Compact IV ROM Development] GlemSom:
Maybe your patches should be submittet upstream?

(unless they break something else though...)
[Touch Diamond, MDA Compact IV ROM Development] beboxed:
GlemSom, I'm getting a 509 "Bandwidth limit exceeded" when trying to download the latest kernel :S
[Touch Diamond, MDA Compact IV ROM Development] GlemSom:
Yeah. Seems like I've reached the limit on my filehost! :(

Anyway, I'm currently uploading to code.google.com.

My site will be updated shortly!

EDIT:

My website now updated to use code.google.com as filehost.

The rest of my autobuild system will need to be adjusted accordingly. This will happen later today.

As of now, all zImages are now hosted on code.google.com
[Touch Diamond, MDA Compact IV ROM Development] aussiewan:
My DIAM130 has MSM7201A as well... but the DIAM kernels seem to be fine...
[Touch Diamond, MDA Compact IV ROM Development] boas:
Wierd bhaviour in winmo

After using plenty of Andorid port' on my Raph, I feel that I must give info about this.

I don't have any knowledge about how Android uses the memory in the phone, but what I can see is that winmo is crashing several times daily since I started testing the Android ports.

From freezes to weird looking icons, something is happening somewhere. The correlation is with out doubt with the Android builds, but causation don't need to derive from the correlation.

Also, latest builds using X-rom is getting MUCH better! Hardly none loopt or acore crash.. Still there is much that needs to be fixed, but you all developers is doing a superb job with the port! I hope you know how many people that is thrilled by your work :D
[Touch Diamond, MDA Compact IV ROM Development] ydoucare:
Is there any way you could zip up what you have? I've been trying to get this working with babijoee's 1.6 pack but all I can get it to do is either power off or reboot after the android boot logo. Are you using a different startup or the one from babijoee's (with 2040 mtype)? I've tried using the startup from babijoee's with 2040 mtype as well as the startup from your last package you posted a while ago and same thing. Not sure what i'm doing wrong...

Thanks
[Touch Diamond, MDA Compact IV ROM Development] dcbogdan:
I'm experiencing similar problems on Diamond since I've started playing with Android. My problem is worse. The phone freezes after a while and it won't boot into WM unless I do a hard reset.
[Touch Diamond, MDA Compact IV ROM Development] patrikbarden:
Do I need to flash back to 6.1?

Have tried several builds and serveral versions av haret, but I cant get Android to boot. Could this be cause I'm running Window Mobile 6.5.1? Do I need to flash back to a 6.1ROM to get Android to work?

If not, could someone explain to me what I'm doing wrong? I have tried the three most recent builds at connect-utb without success.

have a DIAM100 if that matters...
[Touch Diamond, MDA Compact IV ROM Development] Ludacris:
you sould get the package from 09.09.09 - it works like a charm! (expect sending textmessages, reciving them works well)
[Touch Diamond, MDA Compact IV ROM Development] patrikbarden:
I have tried that one allready! unzipped the content to the root of my storage card and ran Haret.exe. It starts to boot, but ends up in some kind of loop that it never gets out of. I have waited for more then 30 minutes, but it never gets any further.

Does the version of windows mobile matter at all?

EDIT: the loop goes like this:

00000, edge 00000000, polarity 00000000

[ XXX, XXXXXXX] msm_gpio_enter_sleep gpio 160-191 enable 000

00000, edge 00000000, polarity 00000000

00000, edge 00a00000, polarity 00820000

[ XXX, XXXXXXX] msm_gpio_enter_sleep gpio 32-63 enable 000

00000, edge 00000000, polarity 00000020

00000, edge 00000000, polarity 00000000

[ XXX, XXXXXXX] msm_gpio_enter_sleep gpio 160-191 enable 000

00000, edge 00000000, polarity 00000000

and so on. The X'es are increasing numbers.
[Touch Diamond, MDA Compact IV ROM Development] mchh:
Did you edit the file startup.txt ?
[Touch Diamond, MDA Compact IV ROM Development] patrikbarden:
I copied the content from the Diamond.txt in the startup-configs folder. My startup.txt goes lite this.

set RAMSIZE 0x08000000

set MTYPE 1805

set KERNEL zImage

set initrd initrd.gz

#

# The following kernel parameters are useful

# ppp.username - The username used to connect to the network when dialing #777

# ppp.password - The password used to connect to the network when dialing #777

# msm_sdcc.msmsdcc_fmax - The maximum frequency (in Hz) used by the SD controller

# pm.sleep_mode - The mode used when the phone is off

# 0=Power Collapse Suspend, 1=Power Collapse, 2=Apps Sleep,

# 3=Slow Clock and Wait for Interrupt 4=Wait for Interrupt

# Default is 3, use 0 for best power savings

# board-htcvogue.panel_type - Panel type used to power the panel off and on

# 0=Don't power off the panel (Default)

# 1=Hitachi 2=Topoly 3=Samsung

# mddi.width - width of the scaled display

# mddi.height - height of the scaled display (these should be multiples of 16 for the camera to work I think)

set cmdline "msmts_calib=115.105.863.911 msmvkeyb_toggle=off mddi.width=320 mddi.height=480 lcd.density=240 ppp.apn=movistar.es ppp.username=MOVISTAR ppp.password=MOVISTAR no_console_suspend"

#set cmdline "no_console_suspend"

# fbcon=rotate:1

# console=ttyMSM0"

boot
[Touch Diamond, MDA Compact IV ROM Development] mchh:
The second line is missing, should be :

set ramaddr 0x10000000

This is my startup.txt for diam100:

set ramsize 0x08000000

set ramaddr 0x10000000

set mtype 1805

set FBDURINGBOOT 0

set KERNEL zImage

set initrd initrd.gz

set cmdline "init=/ console=tty0 mem=76M msmsdcc_id=3 imgdevname=/dev/mmcblk0p1 imgdevnum=1 imgdir=/ ppp.nostart=1 msmts_calib=0x7a.0x5e.0x35a.0x37f mddi.width=320 mddi.height=480 lcd.density=210 msmvkeyb_toggle=off"

boot
[Touch Diamond, MDA Compact IV ROM Development] patrikbarden:
My starup.txt now goes like this:

set RAMSIZE 0x08000000

set ramaddr 0x10000000

set MTYPE 1805

set KERNEL zImage

set initrd initrd.gz

boot

Still the same. I've tried typing ramaddr in capital letters as well. Should I give up??

EDIT: I've also tried with your startup.txt, but still no luck...
[Touch Diamond, MDA Compact IV ROM Development] mchh:
You could try with my whole config maybe.

Make sure it's not due to the zImage file, did you change it ?

try with the latest ones on http://glemsom.anapnea.net/android/diamond/
[Touch Diamond, MDA Compact IV ROM Development] patrikbarden:
did try your whole config. Just tried one of the latest builds from the site you linked to. Got a different error message this time.

Failed to mount the SD card. Cannot continue

/ibn/sh: can't access tty; job control turned off

/ # _

(the underscore is blinking like it's waiting for a command)
[Touch Diamond, MDA Compact IV ROM Development] mchh:
You may have to wait a bit during the first startup..

If it still doesnt work, i'd recommend you to clean up all linux-related files and copying the files again , using my startup.txt and the latest zImage. Maybe some files are messed up.

I read that someone had the same error when booting from WM6.5 .. I dont know if it could be a reason ..
[Touch Diamond, MDA Compact IV ROM Development] patrikbarden:
believe me, I have waited! :)

Gonna flash a 6.1 ROM now to see if that makes a difference. Thanks for your help so far!
[Touch Diamond, MDA Compact IV ROM Development] patrikbarden:
Okey, so now i have flashed a 6.1 ROM, and guess what? Still the same thing! Now I have deleted all files (again!), back to square 1. I'm not giving up on this, but I really don't know were to go from here. I'm lost! help me.... :)
[Touch Diamond, MDA Compact IV ROM Development] mchh:
I'm afraid i can't help you much more .. are you sure to have a diam100 ?? (check under the battery). Did you you ever change the filesystem of your internal storage ? (I also read this issue)

Else, I'd suggest you to search through the topic .. good luck ;)
[Touch Diamond, MDA Compact IV ROM Development] TheShortBuss:
I'm having the same problem with my Diam500 and MrPippy's latest zImage. It either shuts down or reboots after showing the android logo. I used the diamond.txt file from babijoee's 1.6 pack modified for mtype 2040 and I also tried the startup suggested from here: http://forum.ppcgeeks.com/showthread.php?t=84214
[Touch Diamond, MDA Compact IV ROM Development] AndroHQUist:
Have you tried chkdsk the memory card? Out of space when building the 128mb data.img that happens on first boot?

I sometimes have to reset the phone before entering haret to get a "clean" environment.
[Touch Diamond, MDA Compact IV ROM Development] patrikbarden:
Yep, DIAM100 it is. That was among the first things I checked. Thank you anyway!
[Touch Diamond, MDA Compact IV ROM Development] patrikbarden:
I just ran a chkdsk /r on my storage card. No problems found. Out of space on the Device or on the Storage card? Have about 2,5GB free on the storagecard, so that shouldn't be an issue. The filesystem is FAT32.

I don't have to wipe everything else on the storage card, right?
[Touch Diamond, MDA Compact IV ROM Development] boas:
I think I've read somewhere in this thread that a guy never could get Haret to boot sucessfully. Then he tried an other SD-card and it worked. If you can, try it =)

And no, you shouldn't need to wipe the card =)
[Touch Diamond, MDA Compact IV ROM Development] MarcLandis:
Make sure that the partition on your sdcard is configured as primary partition and not as logical partition.
[Touch Diamond, MDA Compact IV ROM Development] patrikbarden:
and how do I do that? BTW the diamond doesn't have an SD-card, just 4 GB of internal storage.
[Touch Diamond, MDA Compact IV ROM Development] toastcfh:
idk... but ive compiled afew images even that one and all mine have the same problem. currently im tryin to get this whole telnet into linux thing setup so i can troubleshoot the problem.
[Touch Diamond, MDA Compact IV ROM Development] patrikbarden:
OK, so now my Internal Storage is configured as "Primary Partition". Works fine with usb-cable plugged in. Copied the files back to the storage and unplugged. But I can no longer find the Internal storage from File Explorer on my device! What to do? Or is there a way to make it logical again? Now i'ts just a fancy USB-stick :)
[Touch Diamond, MDA Compact IV ROM Development] jaellis:
Any Suggestions for DIAM400

It is basically a cross between a CDMA Raphael and CDMA Diamond. No Keyboard, but it has a SD Card, and very limited internal storage. Any thoughts I have not had any luck getting android to run, it normally gets into a loop repeating.

[ xxx.xxxx] msmfb_start_dma xx.xxx ms after vsync request
[ xxx.xxxx] msm_gpio_enter sleep gpio 0-31: enable 00800000, edge 80a00000, polarity 00820000
[ xxx.xxxx] msm_gpio_enter sleep gpio 32-63: enable 00000700, edge 00000002, polarity 000000c0
[ xxx.xxxx] msm_gpio_enter sleep gpio 64-95: enable 400000000, edge 40000000, polarity 40000000
[ xxx.xxxx] msm_gpio_enter sleep gpio 96-127: enable 00000002, edge 00000002, polarity 00000002
[ xxx.xxxx] msm_gpio_enter sleep gpio 128-159: enable 00000000, edge 00000000, polarity 00000000
[ xxx.xxxx] msm_gpio_enter sleep gpio 160-191: enable 00000000, edge 00000000, polarity 00000000

forever, essentially that anyways... Thoughts? I am using the 22-09-09 Version here

http://www.connect-utb.com/index.php?option=com_rokdownloads&view=folder&Itemid=68&id=5:htc-diamond

I Think I found a Solution

set RAMSIZE 0x08000000
Set ramaddr 0x10000000
set MTYPE 2040
set KERNEL zImage
set initrd initrd.gz
#
# The following kernel parameters are useful
# ppp.username - The username used to connect to the network when dialing #777
# ppp.password - The password used to connect to the network when dialing #777
# msm_sdcc.msmsdcc_fmax - The maximum frequency (in Hz) used by the SD controller
# pm.sleep_mode - The mode used when the phone is off
# 0=Power Collapse Suspend, 1=Power Collapse, 2=Apps Sleep,
# 3=Slow Clock and Wait for Interrupt 4=Wait for Interrupt
# Default is 3, use 0 for best power savings
# board-htcvogue.panel_type - Panel type used to power the panel off and on
# 0=Don't power off the panel (Default)
# 1=Hitachi 2=Topoly 3=Samsung
# mddi.width - width of the scaled display
# mddi.height - height of the scaled display (these should be multiples of 16 for the camera to work I think)
set cmdline "msmts_calib=0x81.0x393.0x358.0x7D msmvkeyb_toggle=off mddi.width=320 mddi.height=480 lcd.density=240 ppp.apn=sprint ppp.username=username ppp.password=password no_console_suspend"
#set cmdline "no_console_suspend"
# fbcon=rotate:1
# console=ttyMSM0"
Boot
mkdir /proc
mkdir /sys
mount -t proc proc /proc
mount -t sysfs sysfs /sys
mount -t tmpfs tmpfs /dev
mdev -s
"ls -l /dev/mmc*"[code]
[Touch Diamond, MDA Compact IV ROM Development] schteve:
I had this happen when the mtype was set wrong.
[Touch Diamond, MDA Compact IV ROM Development] IceBone:
babijoee, wherefore art thou?
[Touch Diamond, MDA Compact IV ROM Development] aussiewan:
That's normal while you have the USB cable plugged in and not in ActiveSync mode. Disconnect the cable and the drive should re-appear.
[Touch Diamond, MDA Compact IV ROM Development] patrikbarden:
Yeah, I know that. The problem is that it doesn't re-appear. Just flashed a stock rom to see if that did the drick, but no luck. My internal storage is gone. Guess I have to figure out a way to convert the primary disc back to a logical one...
[Touch Diamond, MDA Compact IV ROM Development] babijoee:
well here it is guys. new package. enjoy :)

http://www.4shared.com/file/143985806/b1edbe82/babijoee_donut_16_27-10-09.html
[Touch Diamond, MDA Compact IV ROM Development] ElCondor:
Downloading atm:D will report back!

Edit: I can't get it to work, it boots succesfully but Android doesn't show up. Only a white _ at the top, not more.

Forgive my noobness, but how do I get this to work?
[Touch Diamond, MDA Compact IV ROM Development] Erik_PLD:
Thanks Babijoee! Let's play! xD

cheers
[Touch Diamond, MDA Compact IV ROM Development] xjarox:
is this for diamond? My diamond still reset after start booting haret.exe

Edit: o.k. this is 4 raphael. I changed startup.txt for diamond and works o.k.
[Touch Diamond, MDA Compact IV ROM Development] c4software:
Whats news its this package ?
[Touch Diamond, MDA Compact IV ROM Development] beboxed:
First findings on my DIAM100:

I couldn't get it to boot with the supplied kernel, the console freezes when handing over the console. When ik replaced the zimage with most uptodate one (25-10) Android booted perfectly.

Although the screen dimensions are not correct, the bar and icons are very small whilst the area used by the applications is just a small rectangle in the middle of the screen. Couldn't fix it by settings the mddi.height and width to 640x480.

I noticed a wifi icon flashing by, but then the battery was drained so I'll have to charge it first....
[Touch Diamond, MDA Compact IV ROM Development] brachialis:
i have the same findings, but i just changed the startup.txt and it worked, but with the screen dimensions all messed up, i can't turn on wifi or bluetooth :(
[Touch Diamond, MDA Compact IV ROM Development] Nakebod:
:cool:

Things I did, before I first booted this build, modify startup.txt for the Diam100:

set RAMSIZE 0x08000000

set MTYPE 1805

And ... haret time! So far it boots fine, screen resolution is higher, and therefor it looks smaller :)

Can't start wifi (Enabled in WM first) and BT doesn't want to start either. (Also enabled in WM)

Time to play more :D
[Touch Diamond, MDA Compact IV ROM Development] bheremans:
I also modified startup.txt and it boots fine. I tried to install rosie, I saw the package in the app directory but it does not want to install. Need to play further but is seems promosing.
[Touch Diamond, MDA Compact IV ROM Development] boas:
How are we supposed to enjoy it when the GPS freezes the phone 50 sec after boot?:p:rolleyes: How can it be turned off? :)
[Touch Diamond, MDA Compact IV ROM Development] babijoee:
The GPS shouldnt be on in the first place. If you activated it and now it auto turns on, i sugguest you delete your data.img and try again.
[Touch Diamond, MDA Compact IV ROM Development] boas:
Of course haven't I activated it...

This has actually been an issue since a couple of weeks ago, when tested a new zImage from the autobuild (together with your previous pack). GPS is turned on automatically somewhere and nothing can be done to prevent it, phone freezes before you can go in to the menu. That is I have of course deleted the data.img with every new release, also this time.

This does not happen with the xRom release and any new zImage. =)

Edit: This has been reported before as well. http://glemsom.anapnea.net/android/squashfs-raphael/
[Touch Diamond, MDA Compact IV ROM Development] leobaillard:
Did you, by any chance, activated the Android locating stuff at the initialisation during the first boot without data.img ? Because it asks if satellites have to be used to determine location iirc.
[Touch Diamond, MDA Compact IV ROM Development] boas:
AAAAAAAH!! leobaillard your a genius! That must be the all of ours issue with the freezing! Thanks a million! :D

EDIT: Not so sure that was the reason, this time I did not even come to the options to allow location pinpointing before the GPS froze Android... Will try again!

EDIT2: Sorry leoballiard, you had me going there ;-) But it wasn't those options that activates the GPS, if unboxed and everything, then it still activates and freezes the device regardless..
[Touch Diamond, MDA Compact IV ROM Development] AndroHQUist:
My raph100 hangs after a while

Edit: Oops.. I have location awareness enabled... Guess thats why it's freezing.

Just some feedback.

Have been trying the latest babijoee donut but have not been able to connect to data. I also have this problem that it keeps freezing after a few minutes.. Have tried the babijoee_stock_kernel and the latest raph-squash zImage.20091025_103428 kernel. Is it possible to have stable networking and running 1.6 ?

Raph100
[Touch Diamond, MDA Compact IV ROM Development] boas:
Have the same device, but location awareness disabled, and it still froze :(
[Touch Diamond, MDA Compact IV ROM Development] patrikbarden:
Finally got my Internal Storage back by using diskpart's CLEAR command. So now I'm back on track!

Still no luck booting Android though. Maybe I'm not supposed to :)

Tried the latest package posted in this thread but no luck...
[Touch Diamond, MDA Compact IV ROM Development] AndroHQUist:
Ok, I haven´t tested without local awareness disabled yet but I guess it would not solve the freezing problem then.