yashsingh1/xdaforums huggingface dataset:
[Tilt, TyTN II, MDA Vario III Android Development] uplinked:
So, can we take a moment to clarify exactly what we need to fix the SD issues? I feel like I can probably help, if someone will hold my hand.

Literally, what we need is a working SD driver (right?). For someone to code a working SD driver, they'd need a linux install, a kaiser, and a lot of programming expertise.

I have the Kaiser and the dev environment. I have a fair amount of programming experience, but little-to-no experience working in hardware/drivers, especially in linux. I'm not familiar with Android and the subsystems involved. But I learn very quickly.

If you want my credentials, I'm 20 years old with no college education, and I've had two internships with Microsoft since I graduated high school, in addition to a myriad of chump ASP and Flash coding jobs. I'm a strong programmer. I can work on big projects. I can figure **** out. And I've never met a problem I couldn't debug.

If someone [dzo, dcordes, anyone qualified] is willing to lend some guidance, point me at the files I need to edit, drop me some wikipedia links and show me what's not working right, specifically, I think I can solve this problem, no collection-fund-for-a-new-phone necessary. And it sounds to me like dzo would prefer someone else try fixing this before we resort to mailing him phones (here). I'm moving to LA in a week, and I'll have about a month of spare time to work on this before I even have to find a "real job."

If you're a qualified mentor who wouldn't mind taking me under your wing for this, hit me up via PM, or on AIM
[Tilt, TyTN II, MDA Vario III Android Development] dy2592:
Dont know about you guys but I like Uplinks tone. His comment actually caught my attention. He means business and the more help we can get the better.
[Tilt, TyTN II, MDA Vario III Android Development] cijoml:
Hi there,

I can mentor you if you can. But I don't have any personal interrest to code anythink - my family take me all my personal free time.

You can start reading this:

http://www.linuxhq.com/lkprogram.html

To learn more about MMC/SD driver you can start study files:

Listik:/usr/src/linux-2.6.27# find . -name *mmc*

Especially drivers in drivers/mmc/ and

arch/arm/*/include/mach/mmc*

Best regards and have happy hacking ;)
[Tilt, TyTN II, MDA Vario III Android Development] uplinked:
cijoml, great start, thanks! I'll start reading tonight.

do you mind if I pm you with a few questions regarding basic android layout and build?
[Tilt, TyTN II, MDA Vario III Android Development] dwaradzyn:
Please don't move to private with technical stuff. There are others like you that would love to get involved (and work together) if guided.
[Tilt, TyTN II, MDA Vario III Android Development] uplinked:
Fair enough. I was planning on putting all the technical contents in a wiki, probably at androidonhtc.com [which currently seems short on contributions]. I've started adding on there, mostly just aggregating information on the initial setup and build process so far.

I've got my android repository downloaded from git, but I'm under the impression that there are some patches, somewhere, between the main google repo and the progress xda has made so far. I tried search and failed. I've been re-reading post-by-post since ~page 125, and I can't find where the most recent code branch is, or how to switch repo to synch from it.

It seems to me like, since there's very little documentation on this subject so far, I may as well update the wiki.

I'm not sure how accurate the Kaiser Port Status page is, so I'd appreciate help from anyone who knows exactly what needs to be fixed. I've already started reading up on the SD issues, but it'd be great if someone could update the wiki to include specifics on the other bugs, and maybe a suggestion of what's wrong, estimate scope of fix, etc.
[Tilt, TyTN II, MDA Vario III Android Development] cijoml:
You should better modify handhelds.org wiki and read sources ;)
[Tilt, TyTN II, MDA Vario III Android Development] uplinked:
Even better, thanks! Didn't know this existed.
[Tilt, TyTN II, MDA Vario III Android Development] Lokioki:
I dl`d the latest package and when I try to boot it with my Kaiser > 1.844.13] Kernel Panic - not syncing: attempted to kill process. Did I miss something ?

Using latest hd`s rom if it matters.
[Tilt, TyTN II, MDA Vario III Android Development] cijoml:
Seems like you miss /dev/sdX2 partition (ext3 type)
[Tilt, TyTN II, MDA Vario III Android Development] Lokioki:
Think me as an idiot which I am clearly and explain again ;)
[Tilt, TyTN II, MDA Vario III Android Development] Isaygarcia:
you need to make another partition on your microSD, an ext3 type partition.

you should copy the system in there.
[Tilt, TyTN II, MDA Vario III Android Development] Apallo:
How to you do that?
[Tilt, TyTN II, MDA Vario III Android Development] Civil:
Use:

fdisk /dev/sdx [where x is where your linux computer saw the micro SD card]

(d)elete the existing fat partition

create a (n)ew (p)rimary partition (1)

starting a 1 and ending where you want depending on size

give it a (t)ype c [fat32]

create another (n)ew (p)rimary partition (2)

I accepted the recommended starting and ending points and made my second partition 500MB

give it a type 83 [Linux]

(w)rite the changes to the disk

I had to remove the disk and reinsert it

Then you need to write the filesystems to the disks.

Use:

mkfs.vfat /dev/sdx1

mkfs.ext2 /dev/sdx2

I used ext2 filesystem because it has fewer writes to the disk and will let your SD card live longer before dropping sectors.

Then extract the angstrom files to the second partition.
[Tilt, TyTN II, MDA Vario III Android Development] Lokioki:
I wuw you, thanks alot :P
[Tilt, TyTN II, MDA Vario III Android Development] edzilla:
I usually make partitions with gparted, I don't trust myself with command lines that could break my debian :-)
[Tilt, TyTN II, MDA Vario III Android Development] dcordes:
it's better to use ext2. the permanent accesses to the card needed for the journaling make it die quicker
[Tilt, TyTN II, MDA Vario III Android Development] cijoml:
BTW today's flash memories has more than 1 milions writes to a single cell. You are almost unable destroy it writing to flash. To save flash you should better think add to /etc/fstab noatime,nodiratime and prolong sync period to for example 5 minutes.

If you really want save flash, use read only squashfs.
[Tilt, TyTN II, MDA Vario III Android Development] dcordes:
sorry I saw this on tv
[Tilt, TyTN II, MDA Vario III Android Development] SharpieMarker:
News fellas.

Android 1.0 ported to Nokia N810

http://www.engadget.com/2008/12/05/android-1-0-gets-ported-to-the-nokia-n810/

Sim/Hardware unlocked android dev phone on sale for $399 USD.

http://www.engadget.com/2008/12/05/sim-hardware-unlocked-android-dev-phone-1-surfaces-for-399/

Thanks for all your persistence.

On another note. Who are we waiting for to get this thing moving more expediently?

Thanks again.

-Sharpie
[Tilt, TyTN II, MDA Vario III Android Development] cijoml:
no fight - it was just FYI ;)
[Tilt, TyTN II, MDA Vario III Android Development] dzo:
I don't think PIO mode works with the driver version we are using, try the 2.6.27 driver in the latest kernel from here:

http://android.git.kernel.org/?p=ke...17c17acf1b72;hb=refs/heads/android-msm-2.6.27
[Tilt, TyTN II, MDA Vario III Android Development] dcordes:
dzo, I tried it. put msm_sdcc.c and msm_sdccc.h in place. the c needed some changes to compile. they moved the include fodler to the arch folder so I corrected pathes and I needed to remove something in the suspend and resume function.

when I boot the card doesn't initialize correctly. I tried both, PIO and dma mode, doesn't seem to make any difference.
[Tilt, TyTN II, MDA Vario III Android Development] BARIO:
Guys,

I guess we all agree that thread is a mess. I suggest you coders create a wiki page here:

http://www.androidonhtc.com/

regards to all
[Tilt, TyTN II, MDA Vario III Android Development] cijoml:
You suggest wrong.

http://www.handhelds.org/moin/moin.cgi/SupportedHandheldSummary

is the central wiki where almost all develop milestones are centralized for almost all linux handheld ports
[Tilt, TyTN II, MDA Vario III Android Development] uplinked:
I agree that an up-to-date wiki on the technical highlights of all of this, but this thread is about the development. And the information being exchanged is more troubleshooting and less documentation. Putting the "This does not work: " comments in a wiki is silly.

A forum just makes sense. Unless you'd rather be reading IRC logs for this.
[Tilt, TyTN II, MDA Vario III Android Development] echofloripa:
That site is more as a summary. The wiki is good to keep updated information. If is the wiki at the xda site or the other one, I don't know which would be better/easier.
[Tilt, TyTN II, MDA Vario III Android Development] dzo:
Hi,

Good news is that I'm being sent a fully working Kaiser by an xda member (who wants to remain anonymous). I'm going away until just after xmas so won't be able to do anything until I get back but then I'll be spending lots of time with it.

Thanks anonymous Kaiser donor.
[Tilt, TyTN II, MDA Vario III Android Development] lando:
Great news. That will be my favorite Xmas gift :)
[Tilt, TyTN II, MDA Vario III Android Development] ducamie:
great news

thanks dzo
[Tilt, TyTN II, MDA Vario III Android Development] dcordes:
that's great news. thanks a lot anonymous donnor. I highly appreaciate that and I think most people reading this threat do too. dzo, can't wait for your first findings. enjoy your vacation and the holidays.
[Tilt, TyTN II, MDA Vario III Android Development] wim26:
yeah agree....thanks a lot anonymous donor :)
[Tilt, TyTN II, MDA Vario III Android Development] sswalia:
THANK YOU ANONOMOUS DONOR !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!

really thanks.... i cant wait till the new year !!!!

ps: thx to the donor
[Tilt, TyTN II, MDA Vario III Android Development] imfloflo:
Great news , thanks to anonymous donor, and thanks DZO for all stuff you do for vogue and now kaiser polaris too
[Tilt, TyTN II, MDA Vario III Android Development] dzo:
Just to make you guys jealous, here a youtube vid of a Vogue:

http://www.youtube.com/watch?v=6iKje_0lUYg

It doesn't show everything, the camera works too, but gives a fair idea of how usable it is.
[Tilt, TyTN II, MDA Vario III Android Development] rkadar1:
htc touch vs tilt?

soo jealous only question i can think of is how is the battery life?
[Tilt, TyTN II, MDA Vario III Android Development] SharpieMarker:
Alright, now I've got wood... Damn, hopefully my Android/Kaiser holiday wishes will come true.
[Tilt, TyTN II, MDA Vario III Android Development] Apallo:
Only one problem I use XP.
[Tilt, TyTN II, MDA Vario III Android Development] SharpieMarker:
Just use bootable GParted to accomplish the partitioning and renaming.

GParted link

http://gparted.sourceforge.net/
[Tilt, TyTN II, MDA Vario III Android Development] TaC:
Is that work yours?? :eek:

Man, it looks the best thing i've ever seen in an HTC. Do you think you can do it in Kaiser too?
[Tilt, TyTN II, MDA Vario III Android Development] wanderso:
With all due respect to Anthon, I believe that there are more than just DMA issues for the Kaiser. However, now that Martin is getting a Kaiser from an anonymous donor, I expect that progress will be rapid. Moreover, and this is key, the Kaiser is much more similar to the G1 (AKA Dream) than is the Vogue (e.g. it has a keyboard and it is UMTS rather than CDMA). So hopefully the remaining issues for the Android port to Kaiser (GPS, BT) will be easier to resolve on this somewhat more isomorphic platform.

Having said that, the progress that Martin has made on the Vogue (along with all the other contributors, of course) is nothing short of astonishing. It is first-class work.
[Tilt, TyTN II, MDA Vario III Android Development] drofmij:
Building From Source android-kernel

I'm trying to build from android kernel sources via:

git clone git://git.android.com/kernel.git

git checkout -b android-msm-2.6.25

I tried to apply this diff:

http://linuxtogo.org/~lgorris/diffs/git-diff-android-msm-htc-2.6.25_kaiser_20082410.diff

patch -p1 < ../git-diff-android-msm-htc-2.6.25_kaiser_20082410.diff

but I get errors during the patch like:

patching file arch/arm/mach-msm/smd_tty.c

Hunk #1 FAILED at 83.

Hunk #2 FAILED at 101.

Hunk #3 succeeded at 197 (offset -6 lines).

2 out of 3 hunks FAILED -- saving rejects to file arch/arm/mach-msm/smd_tty.c.rej

patching file arch/arm/mach-msm/timer.c

Hunk #2 FAILED at 283.

Hunk #3 succeeded at 299 (offset -8 lines).

1 out of 3 hunks FAILED -- saving rejects to file arch/arm/mach-msm/timer.c.rej

patching file arch/arm/mach-msm/tsc2003.c

patching file arch/arm/mach-msm/vreg.c

Hunk #1 FAILED at 82.

1 out of 1 hunk FAILED -- saving rejects to file arch/arm/mach-msm/vreg.c.rej

can't find file to patch at input line 5964

Perhaps you used the wrong -p or --strip option?

The text leading up to this was:

--------------------------

|diff --git a/block/blk-core.c b/block/blk-core.c

|index 2a438a9..4b35824 100644

|--- a/block/blk-core.c

|+++ b/block/blk-core.c

--------------------------

File to patch:

1 out of 1 hunk ignored

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

Hunk #2 succeeded at 27 with fuzz 1 (offset -2 lines).

Hunk #3 FAILED at 67.

Hunk #4 succeeded at 368 (offset 24 lines).

Hunk #5 succeeded at 395 (offset 24 lines).

Hunk #6 FAILED at 404.

Hunk #7 succeeded at 421 (offset 25 lines).

Hunk #8 succeeded at 451 (offset 23 lines).

Hunk #9 succeeded at 466 (offset 23 lines).

2 out of 9 hunks FAILED -- saving rejects to file drivers/i2c/busses/i2c-msm.c.rej

patching file drivers/mfd/Kconfig

Hunk #1 succeeded at 15 with fuzz 2 (offset -7 lines).

Hunk #2 succeeded at 53 (offset -7 lines).

patching file drivers/mfd/Makefile

Hunk #1 FAILED at 3.

1 out of 1 hunk FAILED -- saving rejects to file drivers/mfd/Makefile.rej

patching file drivers/mfd/htc-egpio.c

patching file drivers/mmc/card/block.c

Hunk #1 succeeded at 643 (offset -7 lines).

patching file drivers/mmc/host/msm_sdcc.c

Am I doing something wrong? or is that the wrong diff file for android kernel? Any ideas?
[Tilt, TyTN II, MDA Vario III Android Development] SharpieMarker:
Now the biggest question in my opinion is... Are the issue that you're referring to the issues that are left to iron out in .8? What about Android 1.0? Has development even started on that version?
[Tilt, TyTN II, MDA Vario III Android Development] wanderso:
The particular issues that I mentioned (GPS and BT) are singled out in the Vogue Android thread as features that are not currently working on that platform.

I'm pretty sure that what was shown running on the Vogue video is based on 1.0. I'm certainly not an Android expert, but the functionality shown in the Vogue video sure looks a lot more like the G1 than the 0.8 kernel stuff that I have booted earlier.

So, and it is up to Martin to respond here, I would guess that if the Kaiser "port" is based on the Vogue work, that it will be based on 1.0...

Edit: According to Martin's webpage for the vogue (http://it029000.massey.ac.nz/vogue/), that work is based on SDK 1.0.
[Tilt, TyTN II, MDA Vario III Android Development] dzo:
Yes, we're currently using the image from the 1.0 SDK. The latest open source release also boots but doesn't include the maps api so is not as functional.
[Tilt, TyTN II, MDA Vario III Android Development] dasilva333:
can you post your working copy of android v1.0 SDK for the kaiser so other people can try it? i don't mind not using the maps api id like to test the general OS.
[Tilt, TyTN II, MDA Vario III Android Development] liamhere:
good evening all

i have been asked to clean this thread up....

so i will remove all off topic and " thanks" posts

if you have a problem please pm me....im here to help :rolleyes:
[Tilt, TyTN II, MDA Vario III Android Development] slovoflud:
good luck with the 290 pages :)

P.S. Sorry for the post :)
[Tilt, TyTN II, MDA Vario III Android Development] BombaMyte:
Okay, probably an off-the-wall question here, but it's worth a shot. Is there any way to extract the GSM radio from Android, or is it hard-coded into the OS itself?
[Tilt, TyTN II, MDA Vario III Android Development] Cal-El:
Or is there a way anyone could post the radio and I could attempt to port it! :)
[Tilt, TyTN II, MDA Vario III Android Development] Speaking_On:
Android "cupcake"

http://source.android.com/roadmap/cupcake

Quite a few new resources in this code branch. I don't see anything specific to SD files, but it would be a nice target for future work.
[Tilt, TyTN II, MDA Vario III Android Development] rhornig:
Hm. based on 2.6.27 linux kernel. It might make a big difference rgarding the SD problem.
[Tilt, TyTN II, MDA Vario III Android Development] silasrye:
Helpfull Porting Info

I posted this before, it got taken off, I'm posting it again.

This is instruction on porting android, it lists the differences between some of the android kernal and the linux 2.6.25 kenal. I think it might be helpful here, so please take a look

http://www.linuxdevices.com/articles/AT2892720865.html
[Tilt, TyTN II, MDA Vario III Android Development] SharpieMarker:
I guess the reason I ask is because all of the pages that talk about the status of porting Android refer to the progress with version .8 unless the information also applies to the 1.0 sdk.

Example:

http://www.androidonhtc.com/port_status

Thanks again guys for all the hard work.
[Tilt, TyTN II, MDA Vario III Android Development] dalingrin:
Most of the porting being done has to do with the kernel. Main work is being done to prepare the underlying system on top of which Android will run. Until DMA on the storage is fixed you will continue to see talk of v0.8 because without DMA we cannot run anything greater than v.08
[Tilt, TyTN II, MDA Vario III Android Development] alex_time:
On the 26th of January 2009, HTC will start selling a kind of Touch HD with Android...maybe then we will have a good start point to port the 1.0, look at this:

http://www.cellphonesignal.com/t-mobile-g2-coming-on-january-26th-09/
[Tilt, TyTN II, MDA Vario III Android Development] wanderso:
Only a rumor, and not a very well substantiated one at that - I wouldn't hold my breath...

I'll bet that we have Android SDK 1.0 booting on the Kaiser before we see a T-Mobile G2. The G1 just hasn't been out long enough.
[Tilt, TyTN II, MDA Vario III Android Development] rogro82:
I managed to merge the basic changes of DZO in the 2.6.25 kernel into my own with basic polaris support.

Im able to boot android SDK 1.0 but there still a lot of work to do.

http://xdaforums.com/showpost.php?p=3078729&postcount=140

Im going to start with a clean commit and make the appropriate changes and then post a diff file so other people can work on it. Im guessing this will almost work out of the box on a kaiser because the polaris/kaiser are much alike.
[Tilt, TyTN II, MDA Vario III Android Development] mmone3:
Tried rogro82 build on my kaiser and it starts booting for about 2 sec's, then it just goes to a blank screen with a keyboard on top. Is there a boot error log?
[Tilt, TyTN II, MDA Vario III Android Development] ducamie:
i tried it on my Nike (polaris kernels usually boot fine on the Nike). i get the tux screen but its hanging and wont boot further.
[Tilt, TyTN II, MDA Vario III Android Development] hah2110:
So sorry to be a pain but this is not an easy thread to digest. I want to install android on my FUZE. I have the instructions but where do I download the most recent, fully functional version? I thought the download files from like april didnt even work completely.

Thanks!
[Tilt, TyTN II, MDA Vario III Android Development] rocky814:
the stuff for the fuze is located in the diamond roms in the android on diamond thread
[Tilt, TyTN II, MDA Vario III Android Development] riano:
I've read it and like the idea of booting directly into Android.. the only problem here is that our Kaisers run awfully on Android still. Haret does it's work while still allowing us to use the phone for daily purposes after a soft reset.

Once Android runs stable we can make a package and have it flash our phones
[Tilt, TyTN II, MDA Vario III Android Development] dcordes:
I detailed on how to build the kernel in the other thread. http://xdaforums.com/showthread.php?t=383695

If you are not up to improving the code I doubt you really want to build it. find latest build here

http://git.linuxtogo.org/~lgorris/kaiser/zImage_03-06-08.zip

xmoo you can use this instead of the rapidshare link
[Tilt, TyTN II, MDA Vario III Android Development] riano:
I'm now running the by dcordes provided zImage and init from the vogue

I noticed that the vogue init has the red dot at boot

and "Force quit" wont work :P I've gotten the message about 6 times now for dailer without result.. think I'll softboot and try again ;)
[Tilt, TyTN II, MDA Vario III Android Development] echofloripa:
worked

After a couple of tries with older images I managed to get it to work. With:

- Image from the initial post

- Initrd from the vogue page (http://it029000.massey.ac.nz/vogue/initrd-android)

Review:

- Worked for several minutes (more than 15).

- It rebooted twice when I got in to the maps application.

- The sms app that comes with that initrd doesn't work there, as we don't have a working radio, I presume. It tells it sent the sms, but the target phone didn't get it.

- Locked second time i tried the sms application.

- To use numbers in the keyboard you need to press FN key again before pressing the number. Can live with, but that's not the behaviour on the windows.

Well done guys, hope that now we can get the radio to work then.

Regards

Emerson
[Tilt, TyTN II, MDA Vario III Android Development] riano:
awesome... hehe, in one word, just that :D

@dcordes:

I'm wondering if you took a look at the pointer calibration that the Vogue developer wrote for that phone? If so, I wont have to bother ;)

Some findings in no particular order:

It works mostly.. I went through the menu's a bit, the pointer app in the dev tools shows me to have about a cm offset from the bottom. Once I got back to the desktop (heh) and the menu wouldn't close anymore.. it was still clickable, it just wouldn't disappear. I turned on the cpu tracking and that shows that the cpu of the phone is at best 50% used in a peak, on average it doesn't even get above 25% for doing something. I wasn't able to check the time on my device but eventually, it locked up.

edit: I forgot, it rebooted Android when trying the maps application (thanks to Emerson for reminding me ;))
[Tilt, TyTN II, MDA Vario III Android Development] xmoo:
This phone has Linux on it. So It has a Linux booter. Kaiser has a WM booter. This was mentioned in prevoius posts.
[Tilt, TyTN II, MDA Vario III Android Development] xmoo:
Added it.

The thing with this zImage is that it reboots in some apps/menu's. It reboot 3/4 times before a freeze of deaht. Has this somethin to do with the zImage???
[Tilt, TyTN II, MDA Vario III Android Development] Untouchab1e:
Get the following error:

"Please set start of ram (RAMADDR)"..

Im using the HTC Touch Dual, and im following the guide on the first page of this thread..

Thanks
[Tilt, TyTN II, MDA Vario III Android Development] sswalia:
Remember This Is Only For The Kaiser!!!

REMEMBER THIS IS ONLY FOR THE KAISER!!! (POST 1)

The zImages posted here are specific for the kaiser, there maybe zimages in the touchdual forum that you could use, but they would have unique features when compared to these zImages.

Bottom Line: the zImages u find here wont work for you, sorry.
[Tilt, TyTN II, MDA Vario III Android Development] Untouchab1e:
Ah okey!

Thanks!
[Tilt, TyTN II, MDA Vario III Android Development] Untouchab1e:
I found a zImage from someone who used it with a touch dual, but when booting, the turns off... Any suggestions?

EDIT: Using the files found here.. anyone know what the difference between the Touch and Touch Dual would be in terms of default.txt?