yashsingh1/xdaforums huggingface dataset:
[Touch Diamond, MDA Compact IV ROM Development] touch of jobo:
media

Simply mounting the filesystem under /sdcard in stead of /mmc has the effect that android can no longer mount anything that would wipe the fs from under it. (I tried it and I don't have anything in music or gallery.) Changing the sdcard device in /system/etc/mountd.conf is the only way I know of. I'm not sure it is a problem that the same fs is already mounted under /mmc. (Android sees stuff but it doesn't work quite as well as when I boot off /dev/mmcblk0p2 and mount /dev/mmcblk0p1 on /sdcard )

-Jobo

EDIT: @ refl3x0r: could it be so easy that you just need to type /init.android ?
[Touch Diamond, MDA Compact IV ROM Development] refl3x0r:
@ jobo: there's no keyboard and any changes with msmvkeyb_toggle were followed by "mounting /dev/mmcblk0 at /mmc failed: invalid argument
[Touch Diamond, MDA Compact IV ROM Development] Riel:
mmcblk0: unknown partition table yes.

Also with your variant, Jobo.

I do have keyboard when pushing blue square. In landscapemode.
[Touch Diamond, MDA Compact IV ROM Development] oaa8:
That was exactly were it got stuck for me but the usb connection seemed to solve the problem for me sorry I was of no help
[Touch Diamond, MDA Compact IV ROM Development] Untouchab1e:
Thanks to Jobo, Ive uploaded a new updated Android package for the Raphael. Ive created a download category here which will always host the full, newest build available. Feel free to give it a go!

EDIT: Whoever edits the wiki, feel free to add that link there so that people who just want to give the newest available build a spin to try to it out!

Great work everyone!
[Touch Diamond, MDA Compact IV ROM Development] Untouchab1e:
Anyone else having problems with dragging down the notification "curtain"? It works fine when using the stylus, but I cant manage it with my finger. Might be the fact that I dont have long nails right now, but I can do it just fine on the G1. Dont know if its the visual keyboard, the resistive screen or something else thats in the way..
[Touch Diamond, MDA Compact IV ROM Development] Untouchab1e:
To boot up on the Diam100 you need to replace the initrd.droid.cpio with the one designed for Diamond. I think you can use the one from this package good luck
[Touch Diamond, MDA Compact IV ROM Development] Vector-SS:
While I have not tried the G1, trying to drag the curtain and icons is definitely not easy and more like the HTC Touch, not the Diamond.

A bit of nail makes it a lot easier.
[Touch Diamond, MDA Compact IV ROM Development] oaa8:
I have not tried the G1 either but dragging works fine for me strangely enough. It could just be how one expects the response to be.
[Touch Diamond, MDA Compact IV ROM Development] norkoastal:
Boots up great. Thanks for making the sign on a breeze :D
[Touch Diamond, MDA Compact IV ROM Development] lupine_85:
X.org

With some help from tmzt, I've managed to get X and Angstrom working properly on my device, a RAPH100.

Two main obstacles to getting something vaguely usable (still sans sound, hardware keyboard, and indeed, everything phone-like, but you know what I mean) - firstly, tslib was incompatible with the touchscreen driver, and secondly, the evil fb updating bug gets in the way.

The first issue is easy enough to solve - we just need to register pressure events with the input framework. http://rafb.net/p/3fHpBx69.html does that in a desultory, 4:30am-in-the-morning fashion. The second issue is slightly more intractable - j0b0's VDH is a workaround as long as the vkeyb is present (i.e., you don't pass msmvkeyb_toggle=off) to the kernel. A saner long-term solution should be sought, since I don't intend for that vkeyb to be around forever.... ;)

/Nick
[Touch Diamond, MDA Compact IV ROM Development] Kives:
Latest root.cpio.gz contains an init that mounts the sdcard.

"busybox mknod /dev/mmcblk0p1 b 179 1"

This seems to work with Touch Pro that has a card slot with a sdcard.

Diamond instead has this sdcard look a like "internal storage" and some how it isn't working the same way as a real sdcard.

Can you mount the Pro sdcard with out the partition pointer p1?
[Touch Diamond, MDA Compact IV ROM Development] SummersPittman:
Added the new kernel to Jojo's package

Hey guys,

I am a little new at this, but I think I have put together a build with a newer kernel image. At least, it does the double buzz on boot that is in the latest commit log.

The rest of the package is the same as the ones posted on connect-utb today.

I can confirm that SMS does work, but sound does not so calls are still a bit off.

Android felt snappy and stable however.

I couldn't seem to browse the internet, but that could be anything right now.

It is 1:47 AM local time, I am going to hit the hay.

Here is a link, beware my hosting is comcastic.
[Touch Diamond, MDA Compact IV ROM Development] Marcellus_pnz:
Well, I played a lot with mounting images and creating folders trying to browse my storage from android, but nothing helped. Once, when I created /sdcard manually and put some files in it, the gallery application seemed to scan all of the file system and I have seen my documents and photos, but then it crashed. I failed reproduce this situation.

I downloaded Jobo's last package, but it doesn't run on my diam100, i think it can't find needed images at /mmc/tmp. Then I tried the initrd from http://xda.willboost.com/diam-20081229.tar.gz, like Untoucheb1e advised, but it behave like before - Internal storage can't be used.
[Touch Diamond, MDA Compact IV ROM Development] refl3x0r:
This one worked for me out of box, thanks very much!!!
[Touch Diamond, MDA Compact IV ROM Development] Kives:
Put your phone's product code to your signature

this small bit of info might help us all to follow this thread.
[Touch Diamond, MDA Compact IV ROM Development] Untouchab1e:
Nice work. If you make any other builds, you could send them to me and I could host them so that we have everything in one place. Keep up the good work
[Touch Diamond, MDA Compact IV ROM Development] touch of jobo:
This is a bit of a chain reaction of hacks.. ..to the extent where one fix can break another work around.

Right now, the touchscreen driver uses polling rather than interrupts (irq won't fire, or wont fire reliably / consistently). Because of that, we go through the touchscreen handler 20x/sec whether or not there is activity.

The touchscreen handler also drives the virtual keyboard, and periodically redraws it, even if there is no activity. The virtual keyboard, after drawing itself, marks the area where the keyboard is drawn as dirty, so that it gets redrawn on the next update. But..

..the infamous VDH forces update of the entire buffer, not just the dirty area. This is why enabling the vkeyb has the same effect as dcordes update thread. (..and both of them are ugly.)

A 'saner solution' would have the drawing functions that X uses not merely poke in the frame buffer, but also somehow signal the msm_fb driver to set the msmfb_info->update_info->left,top,eright,ebottom. (Yes .. 'somehow' means 'I dont know' .. through an ioctl, or by using functions internal to msm_fb, ..)

-Jobo

By the way: The VDH is not mine. I believe it is druidu's. Only the interaction between msmfb_pan_update() and msmvkeyb_ts_handler(), msmvkeyb_draw() is.
[Touch Diamond, MDA Compact IV ROM Development] Untouchab1e:
Dont know to what extent, but will a polling solution on the touch screen drain the battery and/or performance more than an interrupt-driven one? (Not that this is important at this stage anyways). Recently worked with a microprocessor where we compared various polling solutions to the equivalent IRQ solutions, and no suprises there
[Touch Diamond, MDA Compact IV ROM Development] NetRipper:
Yes it is more draining. The screen gets needlessly updated as well. With that regard, none of the power management functions are implemented, so running Linux as it is, will drain the phone pretty fast.

Regarding the "Very Dirty Hack". A bit technical... The proper way is to get the touchscreen interrupt to fire (haven't had any luck on that yet though) at which point the 20 times a second thread will be removed. However, this will cause the vkeyb not to update anymore. The vkeyb will then get a thread of its own to update itself every x ms (being the whole vkeyb is a hack of itself, it doesn't matter that it also has a thread running). The last issue is that X (using the "fbdev" driver) simply updates the framebuffer. However the msm_fb driver should be signalled to do a proper update, which Android does. The correct way to solve this issue (IMHO) is to write a driver for X, much like "fbdev" but then something like msmfbdev. This way it is solved in user-space instead of kernel-space, and no weird threads need to be running in the kernel.
[Touch Diamond, MDA Compact IV ROM Development] touch of jobo:
The hack in msm_fb.c that calls msm_ts_handler(0,0,-2) will draw the vkeyb to the frame buffer just before the frame buffer gets dma'd to mddi (in case the vkeyb got overdrawn). The periodic redrawing of the vkeyb is not necessary (in android, as it properly marks the fb dirty), with or without the ts irq firing. (msm_ts does not need to call msm_ts_handler(0,0,-1) at all.)

This draws the vkeyb only when there is touchscreen activity or when the fb gets updated. It would be nice to test at that point whether the dirty region intersects with the vkeyb rect, and not redraw the vkeyb if it doesn't.

That way we always draw when necessary and only when necessary. (To jobtimize even further, we could invalidate the rect for individual keys as they get pressed / released.)

-Jobo

EDIT: Oh, and by the way: Having the touchscreen driver supply ABS_PRESSURE makes the pointer location app in androids dev tools display this value at the top of the screen. :) (It also has a field for 'size'...?)
[Touch Diamond, MDA Compact IV ROM Development] Bad HAL 9000:
Has anyone been working on the color issues on the RAPH800?

I noticed with the latest(?) build my screen has been acting strange, besides the colors obviously. Sometimes it scrambles, and after a bit it goes back to normal. But if I am in andoid for more then 20-30 seconds it scrambles too badly and I can no longer see what is going on, the VDH is stuck all over the screen and I that is mostly what I end up being able to see.
[Touch Diamond, MDA Compact IV ROM Development] Kevbodian:
I am pretty sure it has been narrowed to the fact that there is a different chip on the RAPH800. This may be why it is having this adverse effects. Something like MSM7501A instead of MSM7201 as with all the others.
[Touch Diamond, MDA Compact IV ROM Development] Kevbodian:
Does this site help your cause?

http://it029000.massey.ac.nz/vogue/

Android on the vogue; even the camera works.

Cheers,
[Touch Diamond, MDA Compact IV ROM Development] Untouchab1e:
speaking of keyboard, dont know if this has been discussed, but cant we use the cupcake on-screen keyboard instead of the one we are currently using?
[Touch Diamond, MDA Compact IV ROM Development] sibbor:
Well... In one of jobo's older images I was able to use the onscreen keyboard for my DIAM, but jobo is using a RAPH for development and tried out different approaches for hardware button mapping and the hardware keyboard... he got Android to switch between portrait and landscape mode when changing state of the keyboard slider; I was told the GPIO reports 1/0 depending on state and for DIAM this state was always "out"... so I guess that's why I haven't been able to get the onscreen keyboard in Android working in jobo's latest images.

Although I haven't used jobo's latest image on my DIAM yet, so I don't know if I'm able to use the onscreen keyboard in portrait or landscape mode at the moment. I don't even know if Android supports onscreen keyboard in landscape mode, but hopefully!

EDIT: From the link Kevbodian linked to you can read this: "Update(01/12/08): Switched to cramfs for the system image, just put system.img on the card. Double clicking the cam button now switches from portrait to landscape mode. Camera works better."... so it seems Android is able to switch between portait and landscape mode by code. Perhaps we could investigate if they have onscreen keyboard working in both modes?
[Touch Diamond, MDA Compact IV ROM Development] jornvandereng:
For some kinda reason, whenever I start haret.exe my diamond say's i don't have the right certificates...

I used this link to download my software:

http://wiki.xda-developers.com/inde...ux#Currentx20.statex20.-x20.Androidx20.1x2e.0

Does anyone has solution for this problem?

Thanks! :)
[Touch Diamond, MDA Compact IV ROM Development] dejant_9:
I've a diam 100 and all jobo's zimage work for me (keyboard and all other functions) and i've noticed that power button can switch sreen to landcape or portrait.
[Touch Diamond, MDA Compact IV ROM Development] touch of jobo:
It has happened before. As far as I know you have to hard reset. (And you probably can not run a bunch of other programs as well..)

Typing the term 'signed' in the thread search box turned up these:

You could browse around those posts for something interesting, but I can't remember any other cure than hard reset. If you do find one, add it to the wiki please.

I think that NetRipper has suspicions or even proof that it is related to which ram address and size you use.. ?

-Jobo
[Touch Diamond, MDA Compact IV ROM Development] sascha.egerer:
yes! hard reset is the only solution....
[Touch Diamond, MDA Compact IV ROM Development] NetRipper:
Can you let me know which package you downloaded exactly? Haven't seen this problem for quite a while. You're the first one to report this again.

I thought it was related to the MSM NAND drivers (not movinand) we had in some earlier kernels. The new kernels all have the NAND drivers disabled, as far as I know.

Another thing I noticed was that I was getting more stable results when using the 0x2* memory address range, but lately it seems it doesn't make a difference anymore.
[Touch Diamond, MDA Compact IV ROM Development] lixxus:
hi i would like to know. will these devices ever be able to directly boot into android, without having to use haret. ?
[Touch Diamond, MDA Compact IV ROM Development] frysee:
I've updated Wuala with SummersPittman's build. ;)

greetz

edit: added jobos kernel, too :D
[Touch Diamond, MDA Compact IV ROM Development] Untouchab1e:
Yeah, but there is no point in building an Android ROM before everything is working, so we are booting it from Haret for now ^^
[Touch Diamond, MDA Compact IV ROM Development] Marcellus_pnz:
It's doesn't boot for me. Reason is the same - it doesn't mount the images. (line 4 mkdir not found, line 5 mount not found)/ Tried different sdmmc_id's, no help.
[Touch Diamond, MDA Compact IV ROM Development] Untouchab1e:
Its out on Connect-utb as well ;)

Btw, didnt notice it before, but the cupcake on-screen keyboard is present there :)

SummersPittman, I did suddenly get a calendar notification that was mean for you ^^ Hehe!

Something still needs to be done with the notification curtain though. Its impossible for me to drag it down without a stylus. Maybe its just me, but as I said, it works perfectly fine on the G1
[Touch Diamond, MDA Compact IV ROM Development] Marcellus_pnz:
what?)) is it for me?)
[Touch Diamond, MDA Compact IV ROM Development] zycho:
same here on diam300

maybe is is only for raph (it doesnt mount internal storage i think)
[Touch Diamond, MDA Compact IV ROM Development] DfenZ:
Howto?

Can someone post a howto in the thread or on the wiki?
[Touch Diamond, MDA Compact IV ROM Development] Untouchab1e:
howto on what?
[Touch Diamond, MDA Compact IV ROM Development] BGH80:
I'm using a DIAM100 on three in Australia. Android can't find my network and just says "no service". If I go to call settings in the settings section it just sits there searching indefinitely and I need to reset. I was under the impression service was working and SMSs could be sent.
[Touch Diamond, MDA Compact IV ROM Development] SummersPittman:
Well that is creepy ;).

Meanwhile it looks like cupcake has been merged with the Android master branch.
[Touch Diamond, MDA Compact IV ROM Development] SummersPittman:
I can only get Android to boot if the Raphael is plugged in to my windows computer AND setup to sync the device. Android will not load if the device is configured to act as a storage device.

I have seen posts on the forum indicating this is the case so I am not suprised that is the behavior, but I am wondering why it works that way.
[Touch Diamond, MDA Compact IV ROM Development] Untouchab1e:
Personally, in my experience, I plug the Raph in as a storage device, copy over the tmp folder, soft reset the device, than boot up through haret without being connected to the computer at all
[Touch Diamond, MDA Compact IV ROM Development] Charevian:
Probably you can get the G1 rom running on the Diamond... they both have the same processor chip?

HTC T-Mobile G1:

Processor	Qualcomm® MSM7201A™, 528 MHz

Operating System	Android™

HTC Touch Diamond:

Processor	Qualcomm® MSM7201A™ 528 MHz

Operating System	Windows Mobile® 6.1 Professional

...

i hope it will work ;)
[Touch Diamond, MDA Compact IV ROM Development] DeadDaemon:
Hello! Can someone tell why system freeze after this last line?

console handover: boot[htc_fb0] -> real [tty0]

Can somebody help?

P.S. i know what this problem in cdma devices, but i need know _why_ kernel freeze
[Touch Diamond, MDA Compact IV ROM Development] jdegroot:
This worked great for my Sprint Touch Pro. Running 1.0 (with color issues) as we speak. Thanks!
[Touch Diamond, MDA Compact IV ROM Development] BGH80:
Never mind, I tried a later build and it all works and I can send SMSs etc.

New question though. I thought the newer builds included the cupcake update. How do I display the built in keyboard?
[Touch Diamond, MDA Compact IV ROM Development] Untouchab1e:
try writing a new text message, thats when I got the keyboard up (using the latest build from connect-utb)
[Touch Diamond, MDA Compact IV ROM Development] balsat:
Jobo's build also have a cup of cake! ;>)
[Touch Diamond, MDA Compact IV ROM Development] Untouchab1e:
yeah, I found out ^^

Overall though, I am slightly sceptical to the combination of Android, VGA resolution and the resistive touchscreen. :( I cant pull down the notification curtain, and the on-screen keyboard isnt very good to type on compared to the G1 :)

Will be interessting to see how it finally turns out!
[Touch Diamond, MDA Compact IV ROM Development] sibbor:
That might just be the case. Yesterday night I tried both your new zImage-press-jobo out and "Pittmans", which nicely ****ed up my device. Had a look in the default.txt before I started HaRET and found out that he uses 76MB instead of 64MB.. also some other diffs to yours.

Damn, now I'm sad - can't backup my SMS:es and have to hard-reset.

Well, that's what you get when you're eagerly testing Android out... fooled around with it quiete much now, and really looking forward to it.

-sibbor
[Touch Diamond, MDA Compact IV ROM Development] touch of jobo:
sdcc, mem, landscape keyboard

Ok, so it's sdcc ID 3 for Sprint Touch Pro. (Raph800?) For my Raph100 it is 2. Also, I believe (correct me if I'm wrong) that Raphaels have their internal storage on /dev/mmcblk0p1 and Diamonds on /dev/mmcblk0 (no p1).

(If we were to gather this information on the wiki, should it be on the Raphael Linux page or somewhere under Research?)

I think you can get rid of the ramsize line and only have the mem= option in the cmdline. (0x60000000 = 96M anyway..)

76M is the number that would consistently work (for me). I was ramping up the mem and over 80 it would sometimes not bring up the android boot screen (with the glowing robot). Other images, like angstrom X11, will happily run with mem= up to 96M.

Switching to landscape mode and having a soft keyboard are separate things.

Android will bring up the virtual keyboard when you have to input text but there is no hardware keyboard. So if you switch to landscape mode by sliding out the hard keyboard (or by spoofing that) you don't get a soft keyboard. (Not even the dialer has soft keys when the hard keyboard is out.) If android switches to landscape mode for other reasons than the hard keyboard being out (like when an app requests it 'by code', or maybe by g-sensor), then it would still show the soft keyboard for text input. The only apps I know of that switch to landscape are camera and camera preview. These don't expect text input, so no soft keyboard.

This could be down to your touchscreen calibration being too tight. Try doing the calibration again, or alternatively try increasing the ymin (2nd number in the boot option) of you calibration.

-Jobo
[Touch Diamond, MDA Compact IV ROM Development] DfenZ:
how to get android running :)
[Touch Diamond, MDA Compact IV ROM Development] TheLord-Akira:
read the wiki !!!!!!!!!!!!!!!!!!!

WIKI !!!!
[Touch Diamond, MDA Compact IV ROM Development] mugglesquop:
read the Wiki.

edit - too late lol
[Touch Diamond, MDA Compact IV ROM Development] Untouchab1e:
If you even bothered to read the first page of this thread you would find a link to the Wiki with details on both progress and detailed guide on getting Android running. Connect-utb.com hosts the latest prebuilt packages of Andriod for the Raphael, and lots of other useful links are found on the Wiki!
[Touch Diamond, MDA Compact IV ROM Development] sibbor:
Something wierd happend with that other guys image either way - so like I told you - I've got that "not signed" errors now... From now on I only trust dcordes, NetRipper, you - jobo - and lavender.t ;)!

Thanks for the explanation and the attached image showing onscreen keyboard in landscape mode.

So I should be able to use the onscreen keyboard in both portrait and landscape mode using your images with my DIAM100? Atleast I see the keys in the dialer... now onto the "Google search box" :)
[Touch Diamond, MDA Compact IV ROM Development] NoBody20013:
is anybody working on the sound problem? sorry but it seems to me that everybody is trying to get the onscreen keyboard working for days now....

or is it so dificult? is there anybody who can get the sound to work? i don´t know your skills ;)

-this is only a question - no criticism!!!
[Touch Diamond, MDA Compact IV ROM Development] Bad HAL 9000:
Yea, I was the original poster of that information at PPCGeeks, it is indeed sdccid 3. And yes, Raph800 has it's internal storage on /dev/mmcblk0p1, not p0
[Touch Diamond, MDA Compact IV ROM Development] jamesd256:
Low hanging fruit is always more tempting. Both are needed, so it doesn't matter what order.

No offence, but have trust in the people working on it and be patient. We are lucky enough to have a group of experienced linux hackers actively engaged.
[Touch Diamond, MDA Compact IV ROM Development] Kevbodian:
There's much more to these devices than just that one chip. There are different devices on board that do the same things. Drivers have to be coded and tested and coded and tested again. These people are working hard at it despite most likely having day jobs aside from this.
[Touch Diamond, MDA Compact IV ROM Development] Kevbodian:
The vogue is of course on different hardware than the diamond, so that link may be full of what's already known. I just figured since the author of that page has his code open there we may be able to analyze the code and see how he dealt with the touchscreen polling issue, soft keyb etc.
[Touch Diamond, MDA Compact IV ROM Development] SummersPittman:
Ouch, sorry dude.

The only difference from the previous build which was posted on utb is the zImage file. Everything else is exactly the same. The zImage file was built using the instructions on the wiki. I swear there is nothing malicious.

Meanwhile, could you not put my name in quotes? It isn't a handle, it is my actual name.

Double meanwhile, I have been trying to get the yaffs images that the Android build process produces to run on my device without much luck. I tried adding yaffs to the kernel (different build from what I posted), but that didn't work either. Can someone point me in the right direction?

Thanks

Summers
[Touch Diamond, MDA Compact IV ROM Development] balsat:
Have you tried to put YAFFS2_FS=y to yout .config file?