yashsingh1/xdaforums huggingface dataset:
[Touch Diamond, MDA Compact IV ROM Development] bip91:
Since 09/09 release, Raphael version is a far more stable than Diamond on my DIAM100 :confused:

Is anybody as the same behavior ?

I can't have a stable 3G Data connexion on Diam version, can't Wakeup until today (13Oct) version (zImage from glemsom site). These 2 items works for me on raph version since the begin of october.

Today, the best one is the zImage.20091011_205410 which can work more than a day (charging every 3 hours ;) ):

- Battery Charging is OK if you boot android with sector connected

- Quite stable 3G and GSM (GSM interrupts are more frequent on android than win 6.1)

- Wake up gracefully (except with pm.sleep=0, i set pm.sleep=1)

- Wifi/BT not usable

- Headphones don't work when you plug its (sound stay from the phone), freeze when unplug

But, with care, you can use daily ;)
[Touch Diamond, MDA Compact IV ROM Development] bxmatus:
Working ok on raph100
[Touch Diamond, MDA Compact IV ROM Development] chemical1979:
Something else - to make the reports for the builds more efficient, there needs to be a direct reference between the kernel you've built and the version in the repository used for that build.

Right now there is a "build date", but thats no easy reference to a commit.

In CVS there were versions, in SVN build numbers. As git is decentrally organised, I think the best solution would be to add the hash of the last commit below the build date?

commit	307478c2a0b6e5d1808319d57c2bd56565df947a

Like that? So one could identify to which revision the kernel belongs to (and pin down problems).

But perhaps I'm blind and this is already possible without checking timestamps and timezones or build+cronjob delay. :D
[Touch Diamond, MDA Compact IV ROM Development] GlemSom:
You can hover your mouse over the "zImage file", this will show you the commitid for that build. (will also show you the changes since last build).

Though note: on the current SquashFS builds no changes were logged, since they were build by hand (only the Makefile was patched, to include SquashFS support).

But I guess I could add the commitid to the date field aswell... :)
[Touch Diamond, MDA Compact IV ROM Development] bojkic:
wow...

progress on all fronts :D

quetion for babijoee: what's the problem with 3g(gprs) in your build? do you think it could be fixed soon?... I am amazed by your build and speed it provides!
[Touch Diamond, MDA Compact IV ROM Development] sorrowt:
PLEASE ANSWER THIS...

1. can i get the linux boot log saved to a file?

2. the mount fails: mounting /dev/block/mmcblk0p1 on /sdcard failed:invalid

arguemnt

why mounting /dev/block/mmcblk0p1 while the card is /dev/mmcblk0? how to change this?

iam using DIAM300
[Touch Diamond, MDA Compact IV ROM Development] MarcLandis:
Please post the content of your startup.txt
[Touch Diamond, MDA Compact IV ROM Development] stefand:
Can you post your startup.txt or default.txt file? I think there is gone be the problem.
[Touch Diamond, MDA Compact IV ROM Development] sorrowt:
iam using the default startup for diamond of babijoee android pack.

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] stefand:
Try this cmdline in your startup.txt:

set cmdline "msmts_calib=115.105.863.911 msmvkeyb_toggle=off mddi.width=320 mddi.height=480 lcd.density=240 no_console_suspend"

I did also found a link to your problem http://www.htc-android.com/viewtopic.php?f=5&t=70&start=180

I'm using a diam100 but are you sure "set MTYPE 1805" is correct value for diam300?
[Touch Diamond, MDA Compact IV ROM Development] MarcLandis:
please use "search this thread" and you will find this post:

http://xdaforums.com/showpost.php?p=4689512&postcount=4518
[Touch Diamond, MDA Compact IV ROM Development] sorrowt:
nothing helps, I changed the startup.txt many time, changed the imgdevname, tried many zImages always the same as below:

mmc1: new high speed MMC card at address 0001
mmcblk0: mmc1:0001 XEE0AM 3932160KiB
mmcblk0: p1 < p5 >
Running an fsck on the SDCARD
dosfsck 3.0.1, 23 Nov 2008, FAT32, LFN
Logical sector size is zero
mount: mounting /dev/block/mmcblk0p1 on /sdcard failed: Invalid argument
Failed
Failed to mount the SD card. cannot continue
/bin/sh: cant access tty; job control turned off
#
[Touch Diamond, MDA Compact IV ROM Development] chemical1979:
1.

- Install the Android Developer SDK

- Install the provided USB driver for the USB device that pops up when booting Android (MSM USB)

- Reboot Android

- go to Android Developer SDK/Tools, start: "adb shell"

if you get to the "#" prompt, type "dmesg" as soon as possible.

Nearly all boot messages from the kernel (not from the scripts) will now scroll through.

2.

You're using the wrong statement for imgdevname in your startup.txt

Go to the "set cmdline" and change imgdevname=/dev/mmcblk0p1 to imgdevname=/dev/mmcblk0
[Touch Diamond, MDA Compact IV ROM Development] sorrowt:
I did search, and tried this NOT WORKING, it reads /dev/block/mmcblk0p1 from somewhere and ignores the imgdevname=/dev/mmcblk parameter in the startup.txt
[Touch Diamond, MDA Compact IV ROM Development] bxmatus:
I had similar problem with my 4GB card and problem was in the card itself - it was working ok under WM, no bad sectors, no detected errors during disk check, no problem during format, but under android it was not working, after i change it to new 8GB card it start to work perfectly.
[Touch Diamond, MDA Compact IV ROM Development] Dayd:
Hi. Great project!

same error with the last kernel and diam100

i'm using:

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

@bxmatus: we can't change card with diamond and i don't think that is the problem, it works with the babijoee kernel.

Sorry for my bad english.

and thanks all for your work ;)
[Touch Diamond, MDA Compact IV ROM Development] c4software:
on your startup.txt the imgdevnum is not correct if you look the wiki you have to set to the value 0 and not 1
[Touch Diamond, MDA Compact IV ROM Development] bxmatus:
Dayd: oops, sorry, i didn't realize that we are speaking about diamond ... and my old card was also working with some versions of kernel ... maybe speed issue, i don't know ...
[Touch Diamond, MDA Compact IV ROM Development] Dayd:
Thanks c4software you're right, but same error with imgdevnum=0 :(
[Touch Diamond, MDA Compact IV ROM Development] sorrowt:
just formatted the internal storage of the diamond, still not working!
[Touch Diamond, MDA Compact IV ROM Development] AndroHQUist:
Choppy sound anyone ?

First, thanks to all hard working developers for making this dream (!) come true...

I just tested the babijoee-wifi pack, not for the wifi part but just to test a more recent pack than I used to run... The speed is awsome but I have not sucessfully managed to get gprs to connect yet.

I however noticed that playing songs from my sd-card does not run well at all.. The sound is really choppy and a new kernel did not change the sound problem so maybe it´s related to the sqash pack?? the alternate kernel I tested was zImage.20091013_124438 from glemsom.

Raph100
[Touch Diamond, MDA Compact IV ROM Development] PlackSlayer:
Did you try deleting your data.img and starting over?

--PS
[Touch Diamond, MDA Compact IV ROM Development] Dayd:
I delete "data.img" every time. same.

the error is:

mount: mounting/dev/block/loop1 on /system failed : No such device
Failed
Failed to mount /system
/bin/sh: can't access tty; job control turned off
[Touch Diamond, MDA Compact IV ROM Development] hotib:
i have this problem when i use the squashfs-diamond kernel, but i have system.img not system.sqsh....
[Touch Diamond, MDA Compact IV ROM Development] Dayd:
ahhhhh ok, thanks :)

i have system.sqsh :p

works with latest kernel with squashfs. :)

otherwise where i find system.img? just rename?

sorry if i'm noob :D
[Touch Diamond, MDA Compact IV ROM Development] IceBone:
Babijoee: Can you tackle the hero build? I love the performance of yours, but the original skin looks kinda bleh compared to Hero. :)
[Touch Diamond, MDA Compact IV ROM Development] c4software:
Something have change in the lastest Kernel ? its seems support sharp panel of diam100 (my screen gone off :) and i can wake it up).

--

Edit : In fact the diam100 shutdown after 1 or 2 seconde when the panel turn off
[Touch Diamond, MDA Compact IV ROM Development] hotib:
its not possible to continue the development of babijoees 1.6 wifi-kernel, on http://glemsom.anapnea.net ? to make it more stable and faultless?

Andorid is so great, and fast! I buy a G1...
[Touch Diamond, MDA Compact IV ROM Development] sorrowt:
hi, the MSM USB device is poping up on my windows, where to find the driver?

the driver in the SDK under \android-sdk-windows-1.6_r1\usb_driver are not matching!
[Touch Diamond, MDA Compact IV ROM Development] GlemSom:
After thinking a bit about it, I agree with your point here!

We need to be able to correctly identify a build!

So, I've replaced the "build date" field with a "build id" field instead.

All new builds will now be submitted with the git commitid, so we can identify them like "squashfs-diamond f524306ab293e5faa4b736657b2718f9b3dee643"

Using the commitid, one can go to the GIT repository, and look at the sourcecode at that specific time. (usefull to track down regression bugs!)

On "older" builds, the commitid is fetched from the changelog.

EDIT:

The popup "changelog from last build" is moved to the zImage build log... Seems to make more sense there...
[Touch Diamond, MDA Compact IV ROM Development] chemical1979:
Don't know why this is the case, but MSM USB pops up three times in a row (if you cancel it each time). The first time it fails to accept the driver ("Cannot install this hardware"), the second time it works, copies the driver, and I haven't seen the popup since then.

Anyway, if I check with USBDeview the VendorID 0bb4 / ProductID 0c02 matches the Composite ADB Interface of the HTC Dream on my DIAM300:

android_winusb.inf:

[Google.NTx86]
; HTC Dream
%SingleAdbInterface% = USB_Install, USB\VID_0BB4&PID_0C01
%CompositeAdbInterface% = USB_Install, USB\VID_0BB4&PID_0C02&MI_01
%SingleBootLoaderInterface% = USB_Install, USB\VID_0BB4&PID_0FFF
; HTC Magic
%CompositeAdbInterface% = USB_Install, USB\VID_0BB4&PID_0C03&MI_01
[Touch Diamond, MDA Compact IV ROM Development] MacWell:
Same problem here with the babijoee-wifi version (i also have a Diam100) if i go to Call settings abd click on GSM settings i get an error "network or SIM card error." Simcard is in my phone? what could it be?

Other problems: i have seen this problem before in the thread, Choppy sound!

Also when i want to charge the phone it only charges when i put in the charger in while i'm in WM and start Android.. if i unplug it and plug it back in it doesn't charge the phone while in android..(might all be known issues but i'm not sure(A))

And my Wi-Fi doesn't work at all i can find a network and it connects but if i start the browser or anything it doesn't do anything??
[Touch Diamond, MDA Compact IV ROM Development] dzo:
I've built a new rootfs that should give a more reliable data connection.

http://vogue-android.googlecode.com/files/rootfs-14-10-09.img

All credit for this goes to mdrobnak, he's spent a long time figuring out how to fix the ril for diamond.

Source for this is here:

http://github.com/vilord/android-htc-ril (in the diamond branch)

and here:

http://github.com/vilord/android-initrd
[Touch Diamond, MDA Compact IV ROM Development] mmone3:
Has anyone got any of the donut builds working with GPRS? I'm running it on a raph110 and the only way i've found to get it to connect is to remove the ppp.nostart=1 from the startup.txt, but then it freezes up soon after it tries to connect.

Opps I missed the above message, giving the new zImage a shot.
[Touch Diamond, MDA Compact IV ROM Development] :
Hey is your system also restaring by itself wile using donut 1.6 builds?, this happens to me on my rap110 also.
[Touch Diamond, MDA Compact IV ROM Development] :
The new rootfs works like a charm, great work mdrobnak, testing it on a motorola blur image so far so good, i manage to create the moto blur account =], it also detected my apn setting's from my sim card.
[Touch Diamond, MDA Compact IV ROM Development] Homeryz:
Rafy can you give the links of the files you are using?

Thanks

Homeryz
[Touch Diamond, MDA Compact IV ROM Development] PlackSlayer:
I wonder if the difference between the GSM and CDMA Raphs Bluetooth chip or chip implementation is causing this huge issue and no CDMA/data yet for the RAPH800.

The FM radio works on the diamonds and GSM raph's but not on the CDMA raph - coincidence?

--PS
[Touch Diamond, MDA Compact IV ROM Development] paede:
FM Radio works?
[Touch Diamond, MDA Compact IV ROM Development] PlackSlayer:
Sorry to be misleading - FM radio works on those devices in WinMo - not in Android yet that I know of.

--PS
[Touch Diamond, MDA Compact IV ROM Development] boas:
Really? The link is in the text YOU quoted on the same page!:confused:

http://vogue-android.googlecode.com/files/rootfs-14-10-09.img:confused:

Good development the last days! We are all loving it (perhaps not the Raph800 users :D)
[Touch Diamond, MDA Compact IV ROM Development] MasterMerlin:
I like your style ... :)

Development was so rapid those days .. I have been away for 2 days ... -> 2.5 Pages of comments.

Will give the latest Builds a shoot using the new rootfs.img file.
[Touch Diamond, MDA Compact IV ROM Development] GlemSom:
I've been looking through the last commits.

Commit 3096b02c48ad1b85e5669107b221560e16bb0d5b added support for SquashFS by default.

So, there's no need for me to continue my SquashFS branch - now that patches have finaly landed upstream! :D

I will however keep the squashfs builds a little longer - just for reference. :)
[Touch Diamond, MDA Compact IV ROM Development] sorrowt:
update:

I tried now to mount the sdcard after the boot by:

mount /dev/block/mmcblk0p1 /mnt/

and I get the error:

attempt to access beyond end of device
mmcblk0p1: rw=0, want=4, limit=2
EXT3-fs: unable to read superblock
attempt to access beyond end of device
mmcblk0p1: rw=0, want=4, limit=2
EXT2-fs: unable to read superblock
mount: mounting /dev/block/mmcblk0p1 on /mnt/ failed: Invalid argument

problem with the card? do u have any clue?
[Touch Diamond, MDA Compact IV ROM Development] rattenfanger:
Isn't it only enabled for Diamon by default, not for Raphael and others?
[Touch Diamond, MDA Compact IV ROM Development] GlemSom:
hmm, you're right - it's currently only for Diamond...
[Touch Diamond, MDA Compact IV ROM Development] MarcLandis:
You need to mount it as FAT32 and not EXT3/EXT2
[Touch Diamond, MDA Compact IV ROM Development] sorrowt:
hey Danke ;)

just tried that

mount -t vfat /dev/block/mmcblk0p1 /mnt/

the error this time is only:

mount: mounting /dev/block/mmcblk0p1 on /mnt/ failed: Invalid argument

do you know why this happens or at least how to get more info about the problem?
[Touch Diamond, MDA Compact IV ROM Development] MarcLandis:
I am not 100% sure but the mount point should be

mount -t vfat /dev/block/mmcblk0p1 /sdcard
[Touch Diamond, MDA Compact IV ROM Development] MarcLandis:
something about sdcard issues:

http://wiki.xda-developers.com/inde...dwarex20.differencesx20.andx20.configurations
[Touch Diamond, MDA Compact IV ROM Development] Homeryz:
Not Really.:rolleyes: I mean the rest of the files, zimage, system etc... since he said he was using files from the Motorola.. :D

Good Day

Homeryz
[Touch Diamond, MDA Compact IV ROM Development] boas:
Well since that links existed in the recent pages before last page, it would not be that difficult do find that either. Why not use the search function, or google in the future? It's really not difficult.

http://connect-utb.com/

http://glemsom.anapnea.net/android/
[Touch Diamond, MDA Compact IV ROM Development] sorrowt:
update:

after running:

mdev -s

I got the mmc* under /dev . I could mount the sdcard with:

mount -t vfat /dev/mmcblk0p5 /sdcard

so what to do next? how can i trigger init by hand?
[Touch Diamond, MDA Compact IV ROM Development] MarcLandis:
update your startup.txt and change imgdevname=/dev/mmcblk0p1 to imgdevname=/dev/mmcblk0p5
[Touch Diamond, MDA Compact IV ROM Development] sorrowt:
wish it was that easy!!!!

regardless what is in the startup.txt, after the boot it tries to mount:

/dev/block/mmcblk0p1

dunno why!
[Touch Diamond, MDA Compact IV ROM Development] oliwan:
Hi, I think this is the page you are looking for...

http://code.google.com/p/vogue-hero/downloads/list

Download the system you want. system-motoblur 0.6.sqsh works well.

On a separate note... I'm still having trouble with the phone coming out of sleep. What is the best pm.sleep_mode to use with the latest kernels?
[Touch Diamond, MDA Compact IV ROM Development] mmone3:
About half of the time I do get reboots and the rest are freeze ups.
[Touch Diamond, MDA Compact IV ROM Development] Willis111:
I had that same problem where it was trying to mount up mmcblk0p1 all the time but somehow my card had a logical drive/extend partition set up on it. I just fdisk'd it and created 1 primary partition that uses all the space available, now when it tries to mount mmcblk0p1 it's actually there. If you fdisk your card, removing it completely and then format it with your phone it uses the space to make the logical/extended partitions every time for some reason.

I'm running a diam500, this lets me boot older images and MrPippy's with the correct mtype set. Everytime I would update the wiki with my mmc settings for my diamond500 someone would remove it, so it must have been wrong.
[Touch Diamond, MDA Compact IV ROM Development] toastcfh:
diam500

well i got the latest kernel to boot for the diamond from glemstorms site. i used mtype 1910. the colors were messed but it did boot. unfortionatly it boots to a screan that says shutting down. think its the bat driver.. idk... can u fake the battery durring boot with haret?
[Touch Diamond, MDA Compact IV ROM Development] Tenny:
Did you try booting twice? I got the power issue on every new compile, but on the second boot it would work. I think this was because there were battery problems and it would always recognize it as having 0% charge, so it was trying to shutdown.
[Touch Diamond, MDA Compact IV ROM Development] sorrowt:
indeed, the stupid diamond created only one partition p5 as logical partition and left 60 mb un allocated...

just removed all the partiations on the card, created new primary partition and ANDROIDDDDDDDDDDDDDDDDDD

thanks all for the help, it took long :D
[Touch Diamond, MDA Compact IV ROM Development] MarcLandis:
Nice that it is working now :-)
[Touch Diamond, MDA Compact IV ROM Development] babijoee:
+1 good to see people have it working. :D
[Touch Diamond, MDA Compact IV ROM Development] MarcLandis:
With the latest rootfs I have a rock solid stable 3G connection. So the only thing that is keeping me from using it daily is the power management. :)
[Touch Diamond, MDA Compact IV ROM Development] :
Here you go mate http://code.google.com/p/vogue-hero/downloads/detail?name=system-motoblur 0.6.sqsh&can=2&q= , there's the link to download the motorola blur image im using.
[Touch Diamond, MDA Compact IV ROM Development] babijoee:
Update: babijoee donut pack 1.6 wifi reconstruct

I've successfully been able to have a stable wifi connection. It however is very random. The device has to be still and only started to work while my computer was downloading a new build. Maybe wifi needs to be connected at a slower speed or frequency.:confused:

Perhaps someone would like to try this
[Touch Diamond, MDA Compact IV ROM Development] nearlybritish:
Thanks for the shared link - I can get to the setup menu but for me no data works on my Fuze. I'm on AT&T and the system actually sets up the APN correctly but no data is going up or down... puzzling :confused:

I'm using dzo's new rootfs as well... what does your startup file look like rafy?
[Touch Diamond, MDA Compact IV ROM Development] DSF:
What version are you using? I'm using babijoee 1.6 donut version (not the one with wifi) ... and it just restarts after a while when trying to get a data connection. And, yes, i have the latest rootfs posted here..

Also, the data connection is stable in xRom (updated 9/9/9) .. but this version is soo slow in menus ..

BTW, i like more the gray theme instead the black one (hero one)

(using touch pro gsm)
[Touch Diamond, MDA Compact IV ROM Development] MarcLandis:
I am using babijoee 1.6 donut version without wifi and dzo latest rootfs.

Make sure you delete your data.img/data.sqsh before booting into an updated version.
[Touch Diamond, MDA Compact IV ROM Development] :
I have attached my startup.txt, hope it helps.

cheers

rafyvitto
[Touch Diamond, MDA Compact IV ROM Development] raymondw:
Very Nice :D

Tried it during my lunch break and workes oké on my Raphael.

Had to look twice at the red "dots" ;)
[Touch Diamond, MDA Compact IV ROM Development] ermin15:
Just tried it on my 02 xda touch diamon. Should there be any difference to a htc touch diamon?

Either way, it boots. Tux and the virtual keyboard besides him appears, but the whole time the following message is printed on the screen:

gpio_keypad_scan_keys: unmapped key, 4-5 (31-37) changed to 1
[Touch Diamond, MDA Compact IV ROM Development] Pixel du Rezo:
As it was said in a previous message, this error appears when the stylus is in the phone.
[Touch Diamond, MDA Compact IV ROM Development] jamesd256:
Just a boring post from me to say, thanks to all. Very exciting day.

Boots and calibrates fine on my Raphael. Reminds me of the day I first booted slackware back in the mid nineties.

Keep it up guys, you are awesome.
[Touch Diamond, MDA Compact IV ROM Development] willyy1991:
Great, a breakthrough!

Keep up the good work :)
[Touch Diamond, MDA Compact IV ROM Development] cr2:
What is wrong with the current angstrom feed ?
[Touch Diamond, MDA Compact IV ROM Development] Howell:
Confirmed to work on my Diamond (French) too ;)

Great job :D

Keep up the good work :D
[Touch Diamond, MDA Compact IV ROM Development] ftdm.mav:
Confirmed to work on my Diamond (Portuguese) :D

Very nice job :D
[Touch Diamond, MDA Compact IV ROM Development] hillsdale:
Tried the raph_20081027 version on my new Sprint Touch Pro. No go - I get "HaRET: Booting Linux ...", and then the yellow line gets about 95% of the way across, and then hangs. Once or twice its made it 99% of the way across.

Tried a number of times, reset my device, made sure all apps were stopped, etc. Happy to keep testing!
[Touch Diamond, MDA Compact IV ROM Development] Bandit13:
Its just an exe ? Is it an install or an 'app' ?

Sebastien
[Touch Diamond, MDA Compact IV ROM Development] NetRipper:
Try disabling touchflo 3d (start -> settings -> today -> items -> uncheck touchflo3d -> ok) then softreset and try again. It'll make more memory available to haret. Perhaps that fixes it.

I haven't had to do that yet, but I'm running a cooked (= more memory-optimized) rom.
[Touch Diamond, MDA Compact IV ROM Development] NetRipper:
Look on the wiki page: http://wiki.xda-developers.com/index.php?pagename=RaphaelLinux

There are links for both a Diamond and Raphael executable. It's not a cab you install, you just copy the .exe to your device and run it.
[Touch Diamond, MDA Compact IV ROM Development] Pixel du Rezo:
It's an app. You just have to run it.

Edit: not fast enought ;)
[Touch Diamond, MDA Compact IV ROM Development] Bandit13:
ok

Just have an error : "gpio_keypadscan_keys : unmapped key, 4-5 (31-37) change to 1"
[Touch Diamond, MDA Compact IV ROM Development] aximilation:
Just within the last two pages...do a little reading for yourself next time please...I got that just by scanning over them once.
[Touch Diamond, MDA Compact IV ROM Development] Bandit13:
Yeah ! It works !

I'm so excited !

Good Job !!!

Sebastien