yashsingh1/xdaforums huggingface dataset:
[Touch Diamond, MDA Compact IV ROM Development] druidu:
Did any of you guys see this?

This means no open source for the G1 kernel, so all we can hope is that Android team will add all the support we need for MSM7201A in kernel git. We can expect that the linux kernel will be much more secure than wince is now (something like Haret would be much harder to implement).

As for what we have, here's a summary of what code/drivers we have:

Low-level stuff

/arch/arm/mach-msm/

/include/asm-arm/arch-msm

/include/linux/msm_adsp.h

/include/linux/msm_perf.h

/include/linux/msm_rpcrouter.h

MDI/MDDP framebuffer

/drivers/video/msm/

/include/linux/msm_mdp.h

We have the core and we have Toshiba LCD controller already implemented (which is probably used in G1 and hopefully in Diamond too). A bit of docs about the code is also available. Vogue's msmfb modifications might also be useful.

i2c

/drivers/i2c/busses/i2c-msm.c

NAND

/drivers/mtd/devices/msm_nand.c

USB

/drivers/usb/function/msm_hsusb.c

/drivers/usb/function/msm_hsusb_hw.h

MMC

/drivers/mmc/host/msm_sdcc.c

Serial

/drivers/serial/msm_serial.c

/drivers/serial/msm_serial.h

/drivers/serial/msm_serial_debugger.c

RTC

/drivers/rtc/rtc-msm7x00a.c

Misc stuff

/drivers/android/pmem.c

/drivers/net/msm_rmnet.c

Google's announcement (long time ago):

Something that could also be useful, the vogue git.

To sum up, steps we need to do to get the kernel boot up on Diamond:

- make some bulletproof asm code to have simple binary output (like a led, buzzer, lcd on/off, anything really)

- start putting checkpoints in the kernel code (using the above technique for feedback) to see where it crashes

- implement a basic lcd driver

- add support for the lcd in msmfb

- see which drivers already work, which ones need tweaking and which ones need complete rewrites, then make them all work :)

Btw, what LCD panel is used in Raphel (name, panel_id)?
[Touch Diamond, MDA Compact IV ROM Development] sir0x:
I don't understand, why haret could not use the framebuffer !? because i can change the framebuffer on my own hand

pfh VRAM 480*1 0x0099

and the first line is blue
[Touch Diamond, MDA Compact IV ROM Development] NetRipper:
Yes, that works, but that is because IRQs are still enabled at that point. Once IRQs are disabled, it seems the framebuffer is not getting updated anymore. Probably due to some driver that signals the LCD that it needs updating.
[Touch Diamond, MDA Compact IV ROM Development] Saturn2888:
You might have to hit apply somewhere.
[Touch Diamond, MDA Compact IV ROM Development] celsius0010:
I searched all thru a few threads... what is the best build for a sprint touch pro. I loved android on my mogul i wanted to try it out on this phone but it seems the touch pro thread is behind this one thanks for the help
[Touch Diamond, MDA Compact IV ROM Development] touch of jobo:
That 84% is hard coded (see the commit) , just to make sure the test couldn't fail because of battery smem layout differences making it report zero.

-	buffer->level = capacity;
+	buffer->level = 84; // capacity;

You can check dmesg to see if it detects sane values. If so, and if we can get confirmation for raph/diam 800, we can remove that hack.

Can you fetch from git, apply patches, and build and run your own kernels, or do you need prebuilt kernels? I'd love to see some feedback on the touchscreen area size thingy, but I have to rebase this test stuff up to current head before I can build one that works on Diamond.

Also, you might want to make 2 (or more) partitions. One vfat for haret and images and one (or some) ext2 (or 3) to boot directly into.

-Jobo
[Touch Diamond, MDA Compact IV ROM Development] etx:
Same here on my sprint cdma diamond. Any developments on this?
[Touch Diamond, MDA Compact IV ROM Development] sibbor:
I'll see what I can do. Tested this out yesterday, but just moved to a new apartment w/o Internet connectivity so couldn't report back. I'll see if I can get hold on a dmesg log.

Would love to test this out on my DIAM100, but as it looks now I'll need pre-built images.
[Touch Diamond, MDA Compact IV ROM Development] touch of jobo:
Is there any MTYPE with which you do have access to internal storage? (Like maybe 1805?)

Forget about the colors for now, I want to try this approach for the color issue, which should not depend on MTYPE. But first we need storage mounted.

Now that these changes (on an old kernel) make Diam100s work, here is another kernel that is based on the same changes as the previous one, but now on current git head (and htcraphael_android_defconfig) rather than on a month old git head. If it still works, that would confirm that new commits haven't broken it since.

So if that is all OK, here is yet another kernel that is the same, plus the touchscreen area size patch plus the mdp 565 vs. 666 patch. (So for Diam500: if you have an MTYPE that fixes storage but breaks color, this kernel _might_ fix color without breaking storage, on the same MTYPE.)

Thanks for your feedback,

-Jobo

EDIT: So here are the things we should now be able to tell but aren't known yet:

* Do all devices boot into android on that 1st kernel (or on the 2nd for that matter..), without complaining about battery/charging? - Probably yes, but Diam500 needs an MTYPE that fixes mmc, not color.

* Does touchscreen size report work for Diam100 (with the 2nd kernel)? - I guess it does, but please confirm.

* Does touchscreen size report work for Raph/Diam 800/500? - No idea. Its possible that it does, as it uses raw data, not calibrated. Please confirm.

* Does the 2nd kernel fix colors for Diam500, using an MTYPE that enables mmc, and what is tat MTYPE? - I have good hope that it works. I guess the MTYPE would be 1805. Please confirm.

* Does the battery driver detect sane values for 4-byte smem layout (Raph800/Diam800)? - I don't think it does. Someone with the device should adjust the battery_table_4 (or post the values the driver logs for almost full, for almost empty, and for something less than half full).

EDIT: Clarificación

The touchscreen patch is supposed report how hard and/or 'big' you touch the screen, as per this post. You can see the effect in Apps > DevTools > Pointer Location and in Apps > ApiDemos > Graphics > TouchPaint
[Touch Diamond, MDA Compact IV ROM Development] frodo9999:
Hi Jobo,

I´m sure you are waiting for new about the dmesg output but I´m in a bussines travel and I can´t test it as I like.

First of all I said that as sibbor I need pre-build Image files. The second thing is that i dont have a lot of linux/unix knowledge and is difficult to me understand the output of some commands.

I test your 2 last zimage files and both run in DIAM100. The first one boot but I have a problem with the diamond keys and once I go to the battery menu I can´t go out of this menu and I reboot my DIAM. The second one boot ok and all keys run well. Trying the second kernel I execute dmesg and I see it report a 40% battery level that is near the 48% that wm6.5 report. I´m not sure but I think DIAM don´t detect when I plug the USB.

Do you know a easy think to export dmesg output in a file and put it in internal storage to send it to you? (I´m not sure if android could access to internal storage).

I try to do more test this weekend and report it.

Thank you Jobo.

EDIT:

frodo9999 => wm6.5 48% -> android 36%

frodo9999 => wm6.5 38% -> android 31%

Marcitus => He think android report the battery power without problems.

EDIT2:

Touchscreen works ok with DIAM100. I don´t found issues in the touchscreen area (I only use the stylus to test it, I don´t know if you like I test it with some android software or command)

EDIT3:

I don´t have a image with contains developers tools. I usually download file image from Balsat server, but today is down. Jobo or Balsat, Could you share a link with a full android image file that contains developer tools?

EDIT4:

Frodo - DIAM100 -I have a Build with devtools and i can confirm that touch screen detect the touch size area. The circle is small when i touch with the stilus, and a little biger when i press hard with the stylus. If i touch with a finger i can see a big circle.

Erik - DIAM100 - Tha size of the circle is diferent when he touch the screen with a stylus ans when he touch the screen with the finger.
[Touch Diamond, MDA Compact IV ROM Development] torpie13:
Don't flame me guys but, from the Wiki there's no progress since March '09. So, what really changed from that date ? any progress on Raphael's side ? Sorry but It's hard to read every post from a +300 page thread !!!

Cheers
[Touch Diamond, MDA Compact IV ROM Development] Soaa-:
The DIAM500 can boot under the DIAM100's MTYPE, but of course, with the wrong colors.

I'm not sure if it actually mounts anything from within Android, but it does read the images and does load up Android correctly.
[Touch Diamond, MDA Compact IV ROM Development] andrewloh:
I hope i cannot see "NOT YET WORKING" in the topic. :)

Add oil!!!!
[Touch Diamond, MDA Compact IV ROM Development] Willis111:
It's funny, I've posted on this and put this in the wiki only to have it removed .... Mtype 1805 + the mdev instructions I threw up on the wiki are the only way android USED to boot. Now there's no input (keyboard doesn't work, can't configure networking etc on the device because of no input). Changing the mtype from 1805 it's failed every time. I'm not sure why android boots, the keyboard is displayed and then when you try to type on it it won't output anything to the prompt but ...It kind of reminds me of how I've been adding mmcblk0p5 for the diam500 image device name but someone keeps clearing it out(the mtype is actually going to fix colors??), even though I've seen a few other diam500 users saying "I have mmcblk0p5 but it's not working!!!" Almost need another thread or something for end users to post their info that won't get flooded w/"is it working, how do I ..."
[Touch Diamond, MDA Compact IV ROM Development] frodo9999:
I think I have found the last image build by Balsat (2009-05-28) for touch diamond in a russian forum. I´ve upload it here:

http://www.gazup.com/J62ax-android-28may-09.tar.gz-download-mirrors
[Touch Diamond, MDA Compact IV ROM Development] gebruikershaes:
Not sure if anyone has posted this allready, but it seems that Open Kernal Lab has released a virtualization tool that allows Android to run on top of any guest OS.

http://www.ok-labs.com/releases/release/ok-labs-accelerates-smartphone-deployments-with-okandroid
[Touch Diamond, MDA Compact IV ROM Development] etx:
Hey Jobo, I just tested your second kernel with all the patches on my DIAM500 and the screen colors are correct!! Well done! I'm using 1805 as the mtype and the touch screen calibration values from a RAPH800 and its pretty close.

The build I have does not have the dev tools, and for some reason the newest build someone posted a few posts back from balsats server will not boot for me. So i cannot test the touch screen mods right now.
[Touch Diamond, MDA Compact IV ROM Development] frodo9999:
Hi ext,

Here you have some files that I took of Jobo server.

http://www.gazup.com/v7NSd-diamond-jobo-050509.zip-download-mirrors

If you overwrite that files you have a build with devtools.

The build I post some post back don´t boot in my DIAM100 too. I use that files with the lastest jobo zimage file to make possible to boot it, but that build don´t have devtool.
[Touch Diamond, MDA Compact IV ROM Development] etx:
Hey Frodo, Thanks! That build is really nice, looks like its much more current. I made a video of the touch working on my diam500, and i'm going to look up that network over usb stuff so i can dump some dmesg output.

https://dl.getdropbox.com/u/120967/MVI_1826_sm.MOV

My battery is showing 84% with the newest jobo kernel. I only have a windows box and a osx box here at home so i dont think ill be able to setup net over usb anytime soon. But if you can tell me any info you need I will absolutely get it from my diam500 for you. I could setup virtualbox and network to that, so if you need dmesg output or anything else please do let me know and I'll get it. I really appreciate your hard work, I would love to be able to use Android on my diamond as well and I used to use it on the Touch port!

Also, I'm curious if ADB from the sdk can connect to android on the diamond if usb networking works. I'll try on my dev box at the office tomorrow.
[Touch Diamond, MDA Compact IV ROM Development] Saturn2888:
Awesome man! :D YAY For DIAM500
[Touch Diamond, MDA Compact IV ROM Development] BlazerRazor:
I just tried the new build on my DIAM100 - just have a little problem... I can't unlock the phone after I've booted :D

Anyone have a similar problem? can I disable unlock on boot?
[Touch Diamond, MDA Compact IV ROM Development] Erik_PLD:
You only have to quit the sim lock in winMo before lunching Haret, and android will boot fine. ;)
[Touch Diamond, MDA Compact IV ROM Development] BlazerRazor:
No success, I am running WM6.5 and I do not have any lock enabled but I still get the sim locked when entering Android. What am I doing wrong here? I used to be able to boot android without SIM locked popping up.
[Touch Diamond, MDA Compact IV ROM Development] touch of jobo:
If it reads the images, then your SD card or internal mmc gets mounted. This is done by the init script tho, not Android. In order for Android to mount anything, you need a modified vold.

Nice, this means that the mddi/mdp patch works. I would like someone wise to look at it and judge whether it is pretty. Then we can push it to the repo. Thanks for testing and reporting, etx. And frodo9999 too of course.

It is actually not very current (late April or early May, you can tell from Settings > About Phone > Build Number), but young enough to complain about battery, so good enough for testing this. I built a new one yesterday. If I get the chance I will turn it into a set of images and upload it. This may not be for another week tho as I'm away. (There is nothing really new in there anyway..)

So the pressure/size patch works for Diam500. I'm doing a wild guess here: since you use calibration from Raph800, it probably works for -800 models too. Very nice.

One BATT line from dmesg, plus the capacity windows reports would be useful, (or a Haret dump for that matter, pdump 0x01ffc100 0x48) so that we can see whether it is 100-ish or 800-ish. On the other hand, I'm convinced the battery driver could just detect the smem layout, in stead of getting it from pdata based on mtype. Running a virtualbox and networking from it to the phone works fine. ADB does not work in our kernel.

So it looks like we now have:

* mmc for all devices (now together with good color),

* correct colors for all devices (now together with mmc),

* touch screen pressure size for all devices (but not yet confirmed for -800)

* battery for -100, maybe also for -500, needs some twiddling for -800 (Battery driver does not (yet?, on -100?) detect cable status, or control charging. It only reports capacity.)

I'm probably not going to be able to do a lot of work on this this week, so if someone wants to go ahead and make a battery driver that detects status, controls charging, works on all devices regardless of mtype, .. ..

Thanks,

-Jobo

Congratulations :rolleyes: on 3000 posts.
[Touch Diamond, MDA Compact IV ROM Development] brumbrum:
How simular is the Raphael and Blackstone in hardware?

Is it possible to port the kernel easy to work with blackstone?

I would really like to have android on my blackstone. Tried to create a working image to flash into a X1, but it wasn't possible with my knowledge :-(. Really hope someone will make a flashable image soon for other devices then Dream and Saphire.
[Touch Diamond, MDA Compact IV ROM Development] slovoflud:
great news!

anyone willing to update the Wiki?

I can do it, all I need is compiled info
[Touch Diamond, MDA Compact IV ROM Development] Erik_PLD:
it will be very useful, but i think there are a lot of info to put into.
[Touch Diamond, MDA Compact IV ROM Development] nizzon:
Same here.

Its very sad that there isnt any progress on the Blackstone-port.

We can just hope all the work here can be used for future Android Blackstone devs.
[Touch Diamond, MDA Compact IV ROM Development] c4software:
WoW nice a lot of progress are made. I'm really impressive. :) Great jobs Devs.

Lastest build is on blasat server ?
[Touch Diamond, MDA Compact IV ROM Development] Untouchab1e:
Someone has to explain this to me, but by the sound of it, it has to be useful for our project somehow..

I am trying to figure out what OK:Android actually is. I will quote from the press release:

.

And a quote from
[Touch Diamond, MDA Compact IV ROM Development] elamodelmerol:
hey jobo, let me thank you for all the progress you've made so far

i'm using the 2nd kernel you just posted and i have an DIAM100 it appears that it always detect 84% no matter what the battery conditions are, it successfully detects when it starts and stop charging (though there is little delay but still works :) )

Keep up the good work!
[Touch Diamond, MDA Compact IV ROM Development] Untouchab1e:
Still, it seems like a good way of solving alot of problems we are facing..
[Touch Diamond, MDA Compact IV ROM Development] frysee:
Also seems like a good way of uniting thousands of different smartphone communities to join forces on a single project :cool:
[Touch Diamond, MDA Compact IV ROM Development] Untouchab1e:
Got a reply on my email..

Ive replied and eagerly awaiting their response :)
[Touch Diamond, MDA Compact IV ROM Development] rmonday:
Hey guys,

Steped away from this thread for several months seems like alot of active users. The Wiki has not been updated in several months so I am curious is development has reached a slow halt or no one is updating the wiki?
[Touch Diamond, MDA Compact IV ROM Development] saudoo:
rmonday: The latter, luckily... :P

Untouchab1e: I guess once in our lives we should all be able to take the shortcut rather than the long way 'round the lake (or whatever).. right? It would be great if this could mean that Android could be up and running in a couple of months.... hopefully with close to no performance loss. ;~]
[Touch Diamond, MDA Compact IV ROM Development] Untouchab1e:
A bit of both, but mostly that noone has updated the wiki. People are still working on the project!

I for one is following up on a lead which may or may not lead to a siginificant breakthrough, Il share my findings once I conclude my research :)
[Touch Diamond, MDA Compact IV ROM Development] Gluck:
I have read this tread from time of first post.

Tied by waiting for Touch with android.

A month ago i sold HTC Touch Pro, which was bought for Android.

And I bought G1!

Android is the best! Keep working! :)
[Touch Diamond, MDA Compact IV ROM Development] slovoflud:
I'm willing to update the Wiki, since I've started one back in the Kaiser days but I've not been following the progress that closely recently. can someone PM or email me the latest and greatest of our project, I'll filter compile the info and post an update.

Edit:

where's dcordes?
[Touch Diamond, MDA Compact IV ROM Development] AdamHC:
Same boat as you, don't think I can stand WinMo anymore. might sell my Diamond now and get a G2...
[Touch Diamond, MDA Compact IV ROM Development] strages:
wow i just checked and installed an android version of http://www.connect-utb.com on my phone and i am really amazed how far you guys already are. I hope that there is soon going to be some reall damn good progression in this project as android really rocks on diamond!

btw just a newbie question what are the problems currently faced wanting to port android to htc?
[Touch Diamond, MDA Compact IV ROM Development] dariusperini:
Hi all !

I've juste installed Android (from connect-utb) on my HTC diamond and I have a little problem, after the android boot I am asked for the PIN, I'm sure I type the correct one but it keeps saying me it's wrong :(

Anyone can help me ?
[Touch Diamond, MDA Compact IV ROM Development] nizzon:
It would be nice if you could put some videos up on YouTube so we can see how its working. :)
[Touch Diamond, MDA Compact IV ROM Development] yann79:
solution

you need to un activate the pin code in winmo.

When you restart android it will just won t ask it anymore

Yann
[Touch Diamond, MDA Compact IV ROM Development] :
Hey guys, just wanted to say that im booting balsat android 1.5 build on my raph110, but i cant get android to read my sd card, i was reading the wiki and it says that you have to point the default.txt with the right mtype in order for android to recognize your sd card but i cant find the mtype for raph110, so if anyoone can point me into the right direction, il apreciate it. btw keep up the good work devs

Regards

Rafyvitto
[Touch Diamond, MDA Compact IV ROM Development] touch of jobo:
Hola Rafyvitto, You're not the only one...

vold is the 'volume daemon'. Android uses it to enumerate and mount volumes. In order for this to work on a Raph/Diam you need to modify it to cope with our sysfs structure, which is apparently different from G1/2.

If you use images that mount on an initrd, the SD card is already mounted when android boots, so it mounts read-only. If you boot directly into a different (ext2/3) partition, it can mount your VFAT partition read/write. Either way you need a modified vold (and depending on how you hack vold, also vold.conf).

This one is not particularly clean but it works for me: system/core diff and vold.conf. Please don't hesitate to come up with an approach that does not require hacking vold, or one that is just nicer. ;)

-Jobo

EDIT:

These (090615-images & 090615-fs) are fresh and have vold hacked and setup to mount mmcblk0p1. If it works, please host them.
[Touch Diamond, MDA Compact IV ROM Development] esveinsvoll:
I am looking forward to this project getting it to work. Would be nice not having to buy a touch magic for good andriod implementation:)

Cheers
[Touch Diamond, MDA Compact IV ROM Development] cr2:
got a persistent oops in ksc-led code

[ 188.173327] ------------[ cut here ]------------
[ 188.173327] WARNING: at kernel/mutex.c:135 __mutex_lock_slowpath+0x5c/0x224()
[ 188.173358] Modules linked in:
[ 188.173388] [<c002794c>] (dump_stack+0x0/0x14) from [<c0047f58>] (warn_on_slowpath+0x4c/0x84)
[ 188.173449] [<c0047f0c>] (warn_on_slowpath+0x0/0x84) from [<c022efdc>] (__mutex_lock_slowpath+0x5c/0x224)
[ 188.173480] r6:00000001 r5:d4a3ce24 r4:d4a3ce24
[ 188.173510] [<c022ef80>] (__mutex_lock_slowpath+0x0/0x224) from [<c022f1cc>] (mutex_lock+0x28/0x30)
[ 188.173571] r7:d4a3ce24 r6:00000001 r5:00000001 r4:d4a3ce24
[ 188.173602] [<c022f1a4>] (mutex_lock+0x0/0x30) from [<c019e05c>] (micropksc_set_led+0x40/0x90)
[ 188.173663] r4:d4a3ce20
[ 188.173663] [<c019e01c>] (micropksc_set_led+0x0/0x90) from [<c019421c>] (microp_keypad_led_event+0x34/0x40)
[ 188.173724] r7:00000003 r6:d4a4e800 r5:00000001 r4:d4a4e800
[ 188.173785] [<c01941e8>] (microp_keypad_led_event+0x0/0x40) from [<c018fa48>] (input_handle_event+0x47c/0x4c4)
[ 188.173846] [<c018f5cc>] (input_handle_event+0x0/0x4c4) from [<c019099c>] (input_inject_event+0x78/0xc0)
[ 188.173876] [<c0190924>] (input_inject_event+0x0/0xc0) from [<c014e004>] (kbd_bh+0xf0/0x158)
[ 188.173937] [<c014df14>] (kbd_bh+0x0/0x158) from [<c004d1dc>] (tasklet_action+0x74/0xcc)
[ 188.173999] r6:0000000a r5:c030f7e8 r4:00000000
[ 188.174029] [<c004d168>] (tasklet_action+0x0/0xcc) from [<c004cfe0>] (__do_softirq+0x58/0xc8)
[ 188.174060] r4:00000001
[ 188.174090] [<c004cf88>] (__do_softirq+0x0/0xc8) from [<c004d09c>] (do_softirq+0x4c/0x58)
[ 188.174121] r6:00000000 r5:00000000 r4:60000013
[ 188.174151] [<c004d050>] (do_softirq+0x0/0x58) from [<c004d464>] (ksoftirqd+0x74/0x13c)
[ 188.174212] r4:d7822000
[ 188.174212] [<c004d3f0>] (ksoftirqd+0x0/0x13c) from [<c005d9ec>] (kthread+0x5c/0x94)
[ 188.174273] r6:c004d3f0 r5:00000000 r4:d7822000
[ 188.174304] [<c005d990>] (kthread+0x0/0x94) from [<c004af10>] (do_exit+0x0/0x760)
[ 188.174334] r6:00000000 r5:00000000 r4:00000000
[ 188.174365] ---[ end trace 1a281162bca4adf4 ]---
[Touch Diamond, MDA Compact IV ROM Development] seb071:
What's that code is about, I understand nuthin' ? Can anyone explain pleaze