yashsingh1/xdaforums huggingface dataset:
[Tilt, TyTN II, MDA Vario III Android Development] vj4:
igo 8

im sorry this could be a wast of time but what just installed igo 8 and it loaded a load of files one named geodb initdbfiles and geobd configinit i cant find them in the programs files but dus that look like linux maybe? inplacations being it would use the gps so somethings gotta be talking. sadly i cant get it to load i get an error at some address that looks the same style as the one in the deafult.
[Tilt, TyTN II, MDA Vario III Android Development] AstainHellbring:
How are we doing with getting sd support?
[Tilt, TyTN II, MDA Vario III Android Development] xmoo:
Try Total Commander. That shows the hidden files!! (ALL OF THEM)

I think a full functionaling android + phone is more important than sd.

I tried letting Android search for my sd card. It did not find anything. I gave android 1 hour te time to look-up.... :(
[Tilt, TyTN II, MDA Vario III Android Development] vj4:
COuldnt find any sign of them xmoo cant get it to load either dunno why theres a kaiser file in there aswell grrrrrrr back to garmin. sorry if that was a waste of time just thought it seemed a bit strange coz after it crashes screen gose black for a few secs like android rebooting befor we got the kitt style bar thing back.
[Tilt, TyTN II, MDA Vario III Android Development] AstainHellbring:
xmoo its cause there isn't the support build into the kernel if you launch angstrom-console for initrd you can use a console and check stuff like that, sd support would be nice for persistant storage and for porting this to other msm devices that don't have enough ram for the normal method
[Tilt, TyTN II, MDA Vario III Android Development] assangflexx:
But if you have te SD support, than linux has to mount this volume...

correct me if i am wrong, but each time you boot linux you have to mount the SD. Maybe Cronjob will do the trick, but i didn't still managed out there is an terminal. Whith terminal we can customize alot i think.
[Tilt, TyTN II, MDA Vario III Android Development] AstainHellbring:
right but if I place the whole android FS on the SD and use haret to run linux from SD then it will be mounted for me
[Tilt, TyTN II, MDA Vario III Android Development] xmoo:
That's also correct. But booting Android from SD works in some cases (1 out of million)
[Tilt, TyTN II, MDA Vario III Android Development] shadowline:
I actually haven't had that much more of an issue booting from the SD over booting from the device itself. It doesn't seem to crash any more than the latter and it boots fine. I am using the dutty test rom and a 4gb Sandisk MicroSDHC, Beta haret, newest zimage, and the initrd from the vogue page (with the sms app, world clock, etc)
[Tilt, TyTN II, MDA Vario III Android Development] rogro82:
Ok ive created a manual on how to I was able to make a kernel that can make the Polaris to boot android.

Hopefully someone can clean up all code and make Android work in both the polaris and kaiser and maybe some other devices.

Ive included a short manual and all files I think were needed.

http://rapidshare.com/files/176877021/Android_vogue_merge.zip

I know its not the cleanest etc... but due to my lack of time and knowledge ( ive just started working on linux/android for 2 weeks or so ) its the best i could come up with.

To boot after creating an image make sure you get the android 1.0 sdk and use the correct default.txt that can be found here in my other upload. ( page 14 of the Polaris Android thread )

Good luck :) and merry Christmas to everyone...
[Tilt, TyTN II, MDA Vario III Android Development] phoeniix:
According to the haret homepage you can enable logging by including a file called "earlyharetlog.txt" at the same level as haret.exe. This creates a file called "haretlog.txt" with logging information when haret runs.
[Tilt, TyTN II, MDA Vario III Android Development] dasilva333:
this is great i hope someone talented can come up with a cleaned and compiled version of the merged tree look forward to testing it
[Tilt, TyTN II, MDA Vario III Android Development] dcordes:
here's the rogro kernel with some minor modifications to the framebuffer code that allows it to boot on the kaiser. imho it's a very good idea to reintroduce kaiser in the latest vogue code. unfortunately I was unable to reproduce the sd stability rogro experienced with the vogue sd driver on his polaris. booting android SD makes the system die after 40 megs of extracting data.gz. I hope we can identify the parameters that influence sd stability here.
[Tilt, TyTN II, MDA Vario III Android Development] MrSmileyJr:
I'm confused, does that link you posted go to a working 1.0 android on kaiser?
[Tilt, TyTN II, MDA Vario III Android Development] mmone3:
Not working, as dcordes stated, it loses connection with the SD and fails to finish loading.

Im hopping we see a working version soon.
[Tilt, TyTN II, MDA Vario III Android Development] disturbed4686:
I think it is a booting, but not working version. It's too big to fit on the internal storage of the Tilt, and from what he says, it freezes after it gets partway through loading the system off of an sd card. I'm loading it onto my sd card hoping that this will work ::crosses fingers:: but I don't have my hopes too high yet. Pretty soon this will be working though.

EDIT: I just loaded it, and it froze with an on screen keyboard at the top of the screen, I didn't format my card or anything, I just threw the folder on my sd card with the new zimage. It loaded really quickly though before it hung up. I'm no dev, but I'll do whatever I can to get Android running. I'm sick of WM.

EDIT 2: dzo, hope you had a good holiday. Have you gotten your Kaiser yet?
[Tilt, TyTN II, MDA Vario III Android Development] Raketemensch:
It seems like this SD issue is our worst malingerer.

Can folks post other remaining major issues?
[Tilt, TyTN II, MDA Vario III Android Development] anod:
Some screens

Hi, I loaded android on my Kaiser

I Used in zImage above from dcordes and

data files from there:

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

(All the files (haret,default...) I placed in the /sdcard/android, i copied

data.img and system.img with the names data.img.gz and system.img.gz

and all 4 files also copied into the root of sdcard

Because when i loaded dcordes zImage for the first time it asked for /sdcard/system.img.gz file

)

Touch screen is not working, no radio and no buttons....

now black screen without any response

but still...

Ps on the second load: press wheel work like enter, whell up or down change current desktop, w,e on the hardware keyboard for cursor moving,

opened camera application - asking for sd card, but it's kind of stable

I attached some screens
[Tilt, TyTN II, MDA Vario III Android Development] dcordes:
crap this must be the wrong kernel. I didn't get the keyboard on top with this build. I will check this later and also put the code somewhere.

edit: anod you didn't get the keyboard on top? can you describe your sd setup? sd or sdhc? how big? one fat32 partition?

no touchscreen, no radio are epxected. it's just an ugly hack to make rogro kernel framebuffer work for kais to see what sd does. obviously anod has some success there. (as I stated earlier for me it didn't extract.)
[Tilt, TyTN II, MDA Vario III Android Development] disturbed4686:
can you post a zip file of the files you used, the way you described it is a little confusing, or at least a screenshot of your file explorer with all the files

Mine looks like

Storage Card\anrdoid\data.img.gz

Storage Card\anrdoid\default.txt

Storage Card\anrdoid\haret.exe

Storage Card\anrdoid\intrd.gz

Storage Card\anrdoid\system.img.gz

Storage Card\anrdoid\zImage.bin

Note, I also tried to use data.img and system.img, and it gets hung up on unpacking zImage, or something like that. I also had to change the defualt.txt to look for zImage.bin, because for some reason it was looking for zImage, no extension. I renamed it to that at first too, but that didn't work either. Please explain in detail what you did to get android 1.0 booting on your device. I have a feeling that I need to partition it, but I would like to be sure before I risk messing up my TomTom :)
[Tilt, TyTN II, MDA Vario III Android Development] anod:
Later I will check which files I not need...

2dcordes

I didn't formatted anything or changed on my sdcard... fat32.. sdhc... see screens

with original zImage i got keyboard pictires, but with your last, i saw message /sdcard/system.img.gz did not found, so i simple renamed system.img into system.img.gz and placed it in root...

2disturbed4686

also do this in the default.txt

#set KERNEL zImage

set KERNEL zImage-kaiser-goes-vogue-sd_01.bin
[Tilt, TyTN II, MDA Vario III Android Development] disturbed4686:
i renamed zImage-kaiser-goes-vogue-sd_01.bin to zImage.bin, which is what I put in default.txt

set KERNEL zImage.bin

Now I am getting stuck loading linux. I can't really read it...its tiny.

looks like it says [ 9.006819] mdp irq already on 4 4

[9.010001] mdp_dma_to_mddi: busy

is that one of the dma errors that everyone is talking about?
[Tilt, TyTN II, MDA Vario III Android Development] anod:
Did you placed images into root of sdcard??

like on my second screenshot

you should see before this message this message:

[ 1.800085] SD Init Retry

[ 1.803036] mmc0: new SDHC card at address d555

....

gzip:/sdcard/system.gz: No such file or directory

so, you should place system.img and data.img (just have checked... without of .gz suffix) into Storage Card\
[Tilt, TyTN II, MDA Vario III Android Development] disturbed4686:
i tried that before, and it didn't work. i'm trying again...will update in a few

Update:

8.660001 Code:e1a00000 e1a00000 e1a02000 e4f03001 (e3330000)

8.661253 Kernel Panic - not syncing: Fatal exception

Update 2: any chance you could just zip up the files you need? This doesn't seem to be working for me :(

8.800656 init:untracked pid 417 exited

That's my latest error, with the files in the images i attached.
[Tilt, TyTN II, MDA Vario III Android Development] anod:
Sure, uploading now....

Strange, Looks fine...

I will post link in 30min

Backup and remove your files and extract into the root of sdcard:

http://rapidshare.de/files/41237182/android1.0_kaiser.rar.html
[Tilt, TyTN II, MDA Vario III Android Development] Bartsimpson69:
New French Google Android Forum

Hi all of you... Just wanted to say to all french developpers that their is a new Google Android french forum on http://www.blog-mobile.com

French post ar welcome ! :)
[Tilt, TyTN II, MDA Vario III Android Development] disturbed4686:
i'm downloading from you site (slowly). where is your server located? Australia? lol

It'll be done in 21 mins, going at 15KB/sec
[Tilt, TyTN II, MDA Vario III Android Development] SharpieMarker:
Android 1.0 sdk r2 released

Android 1.0 sdk release 2 available as of November 2008. Didn't know if anyone else was using the latest release. Thanks again for all your dedication and hard work.

http://code.google.com/android/download_list.html
[Tilt, TyTN II, MDA Vario III Android Development] anod:
disturbed4686

at my home :)

hope it will help you...

http://rapidshare.de/files/41237182/android1.0_kaiser.rar.html
[Tilt, TyTN II, MDA Vario III Android Development] disturbed4686:
nope, still gettin stuck here

init:untracked pid 417 exited
[Tilt, TyTN II, MDA Vario III Android Development] anod:
maybi it's sdcard type? do you have sdhc? fat32? which size?
[Tilt, TyTN II, MDA Vario III Android Development] disturbed4686:
sandisk sdhc, 4GB, and I can't tell what format, cuz i dont have a card reader at work, ive been loading everything on over usb right through the phone. I assume its FAT32, but im not sure
[Tilt, TyTN II, MDA Vario III Android Development] dcordes:
I have 4gb SDHC class4 with one fat32 using all of the card's size. and as I said I don't have the stability here. data.gz only extracts to about 40M until sd dies.

edit: you can easily check this. after the system died and you softreset, just check how big the data file is.
[Tilt, TyTN II, MDA Vario III Android Development] xerootg:
So im playing with the last posted android set, and i must say, im impressed! it actually booted! lol, no but really, no touch screen, no buttons what so ever, except for the center button on the d-pad. non the less, im impressed!

oh, 8gb sdhc class 4

device went to sleep and i couldnt get it to recover from sleep, probably a function of the lack of buttons.
[Tilt, TyTN II, MDA Vario III Android Development] Bimboy:
I also have the Sandisk 4GB SDHC, single Fat32 partition. I am also getting the same errors as disturbed is.

AT&T Tilt...
[Tilt, TyTN II, MDA Vario III Android Development] angeloso:
Here it's working.

Using data.gz and system.gz, the kaiser reboots while gunziping the file. But I have seen this, inside initrd.gz:

mount -t vfat /dev/block/mmcblk0p1 /sdcard
[ $? -eq 0 ] || fail "Failed to Mount SD Card"
if [ ! -e /sdcard/system.img ] ; then
echo "Please wait... extracting System Image"
gzip -d /sdcard/system.gz
[ $? -eq 0 ] || fail "Failed to extract System Image"
mv /sdcard/system /sdcard/system.img
echo "done"
fi

So I put system.img and data.img (not gzipped) on SD and kaiser boots without problems (No touchscreen, etc but it boots).

I have a 4gb SDHC with one fat32 partition.
[Tilt, TyTN II, MDA Vario III Android Development] anod:
2dcordes

I'm not used in gz file, maybe this is the reason, why it's working,

like described in the previous post
[Tilt, TyTN II, MDA Vario III Android Development] rogro82:
Extracting it by hand doesnt solve any stability problems... on my polaris i can extract the files easily.

I do it two / three times a day without ever suffering from failures (yet).
[Tilt, TyTN II, MDA Vario III Android Development] anod:
I don't notice any stability problem,

I'm loading it without problem, i found working buttons and opened most of applications and examples...

Maybe somebody can help me:

I want to get touch screen and radio working, do I need to recompile kernel?

where I can find some info about configuration, and if i need to use in diff files, and what the steps to get current kernel?

disturbed4686

I also saw this message but after that android splash screen start
[Tilt, TyTN II, MDA Vario III Android Development] milas:
I used the .rar file anod posted on my 2GB MicroSD and it booted up fine. Got to the android homescreen, but couldn't really stress test it because of the lack of touchscreen/buttons. It did however stay up fine for about 20 minutes just sitting as well as through several sleeps/unsleeps.
[Tilt, TyTN II, MDA Vario III Android Development] rogro82:
@Dcordes ive rebuilded a new kernel using the latest diff file you suggested on htc-linux made some minor changes ( board/touchscreen related mainly ) and it boots :)

Also added cramfs support to the kernel so now im able to boot the latest DZO image.

Strange thing is that im not getting any operator ( i did get android on the old image ). Already changed the modemsetup in the initrd to use the old method, but still no luck.

Any ideas?
[Tilt, TyTN II, MDA Vario III Android Development] blasti99:
the rar that anod posted works fine on my kaiser... also some buttons work and also some keys on the hardware keyboard, so I could start some apps and they all seemed to work ok, however without the touchscreen support it was difficult to really use them.

I played around for 30min and had no problems at all. looks like a good start to me.
[Tilt, TyTN II, MDA Vario III Android Development] rogro82:
Someone needs to adjust the board and touchscreen to match the kaiser...

If im right the only thing dcordes changed was the framebuffer to make the video work on a kaiser. So input etc is still from my Polaris build.

If someone experienced in building kernels want to build one just use the files i posted on the previous page.
[Tilt, TyTN II, MDA Vario III Android Development] angeloso:
Before using data.img and system.img, I recovered the ext3 filesystem, don't know if it can make a diference.

angeloso@yopispo android $ file *.img
data.img: Linux rev 1.0 ext3 filesystem data (needs journal recovery)
system.img: Linux rev 1.0 ext3 filesystem data (needs journal recovery)

angeloso@yopispo android $ /sbin/fsck.ext3 -v data.img
e2fsck 1.41.3 (12-Oct-2008)
data.img: recovering journal
data.img: clean, 213/16384 files, 26572/65536 blocks

angeloso@yopispo android $ /sbin/fsck.ext3 -v system.img
e2fsck 1.41.3 (12-Oct-2008)
system.img: recovering journal
system.img: clean, 350/16384 files, 48221/65536 blocks
[Tilt, TyTN II, MDA Vario III Android Development] anthonws:
Great news!

Thank you to all the hard workers :)

Does this means that the DMA issues are gone?

I'm going to try it later.

Best regards,

Anthon.

Update:

Tried the rar file from ano and I got the "untracked pid 417 exited" error.

I'm using DK9 Rom.

Going to check my SD filesystem settings.

Thanks!
[Tilt, TyTN II, MDA Vario III Android Development] disturbed4686:
How long did you have to wait for the splash screen? I have had it sitting here for about 10 minutes, and it is still stuck :(:confused:
[Tilt, TyTN II, MDA Vario III Android Development] agentofboom:
boot success!

Im up and running. No radio, touch, etc. button mappings are all over the map, screen is slightly misaligned, but WOW! Looks great! Boot seems faster than .8 release.

I just took the files from here (Thanks rogro82)

http://xdaforums.com/showpost.php?p=3083999&postcount=1781

used this zImage (Thanks dcordes)

http://xdaforums.com/showpost.php?p=3088810&postcount=1784

Modified my default.txt to

set KERNEL zImage.bin

Renamed zImage-kaiser-goes-vogue-sd_01.bin to zImage.bin

Placed in ROOT of SD card

boot Haret (also in root)

in no time, linux verbose boot, then a really kewl Android splash screen (gave me geek chills)

Im using a 4gb sdhc card and Solace 1.5 ROM on Kais100 (AT&T Tilt)

Now to repair and recompile....:eek:
[Tilt, TyTN II, MDA Vario III Android Development] milas:
Another note, my SD card has two partitions, an ext3 and fat32 one, but for this test I was only booting off of fat32. So I dunno if the different partitions/SD cards are what's affecting the boot.

I am running a HyperDragon M2D ROM, one of the November ones I believe, maybe the Dec 3 one however.
[Tilt, TyTN II, MDA Vario III Android Development] KeizerBAAS:
1.0 looks great

Got it to boot, straight on the first time use only the files in android1.0_kaiser.rar, copied to sd card, 4gb sandisk sdhc, one fat32 partition, rom currently eos FiRe, no changes in default.txt.

Boot indeed seemed to be faster than .8. Nice splash screen, made me think it was VGA, cause it seemed not to fit, but this is probably not the case.

No touch screen, not a lot of keys work. It did seem to take the time WM was running on, could set an alarm. Browser works, no connection though. Scroll wheel double clicking indeed seems to work as enter. Only up and down keys found, plus sleep, back, menu, edit (with which an app can be added to the desktop, in order to try out)

Camera app. gives error that it needs sd card, pictures app tells us there are no pictures, media scanner hanged when searching for SD card, which makes me wonder is this problem is solved.

Again, I'm not into compiling or anything, but sure this looks great!

btw: only the data.img and system.img appear on the sd card...
[Tilt, TyTN II, MDA Vario III Android Development] KeizerBAAS:
Update: de RAW Image viewer in Dev Tools is able to show images from the SD card! crashes after a couple of images though.

In case I can help with making the touch screen, key mapping, key board, radio etc work for kaiser, please let me know. Also if you need details on how it boots with me...
[Tilt, TyTN II, MDA Vario III Android Development] anthonws:
I still can't find out why Android doesn't boot on my kaiser.

1. Formated my Sandisk Premier 2GB with FAT32 FS.

2. Formated ROM storage (hard-reset)

3. Tried a load of file combinations, gz's, not gz's, etc

4. With android folder, with all files in the root

5. Did a check in data and system journal

Sometimes it stops with a "kernel panic (...)", or with a "untracked pid 417 exited".

I do see a lot of "end request, I/O erros" and also "(...) irq already on already on 4 4".

Going to buy a 4GB SDHC card later and see if I'm able to "enter with the right foot" in 2009 :)

Could anyone tell me what am I doing wrong?

Happy 2009 for everyone!!

-= More Info =-

Phone Model: Kaiser 130

ROM: DK9 (no manilla no nothing, hard-reset)

Radio: 1.71.09.01

HardSPL: 3.56

MicroSD Card: Sandisk Premier 2GB

FileSystem: FAT32 (Cluster size: 512 Bytes)
[Tilt, TyTN II, MDA Vario III Android Development] disturbed4686:
im doing the same exact thing, and seeing the same problems as you anthonws. Hopefully somebody can help us out.

Share the android!
[Tilt, TyTN II, MDA Vario III Android Development] KeizerBAAS:
Ok, 4GB SDHC works for me, so I tried a normal 1GB sdcard. Just copied and the extracted files from anod's rar file again: http://rapidshare.de/files/41237182/android1.0_kaiser.rar.html to the SD card, no further actions taken.

Works fine as well! I think normal SD or SDHC doesn't make a difference, should be something like the rom used or kaiser model (mine is KAIS130, running eos FiRe)

I've now got the music app running, it's recognising mp3s on both sd cards, and actually playing (though no sound and a little buggy, but it works!) I did need to run the media scanner under dev tools again in order for it to recognise the sd card, before this it didn't work.
[Tilt, TyTN II, MDA Vario III Android Development] anthonws:
KeizerBAAS,

Thanks for the feedback!

I'm going to change my SPL and ROM and test it again. Maybe Radio version too.

Best regards,

Anthon.
[Tilt, TyTN II, MDA Vario III Android Development] disturbed4686:
im running the stock wm 6.1 update, i think stock spl too. it ran .8 fine every time, so idk why this isnt working
[Tilt, TyTN II, MDA Vario III Android Development] KeizerBAAS:
Understand that this version for Kaiser really doesn't have any capabilities yet, it's nice to play around with, but without touch screen, correct key mapping, connectivity, we are nowhere, but I'm quite sure all the guys that got 0.8 running for the kaiser, are already working on this...

Happy new year to all of you, may it bring Android to our Kaisers!
[Tilt, TyTN II, MDA Vario III Android Development] biscuits1978:
I was able to get it to boot up on a Kingston 2GB microSD card, HardSPL 3.29, and running the latest Phoenix ROM. I did what was stated before -- just unpacked the RAR file to the SD card and it booted right up. Same as others, only have some weird capabilities with certain keys on the slide out keyboard, and the jog wheel works for scrolling. This

has

to be a step in the right direction!!
[Tilt, TyTN II, MDA Vario III Android Development] DJ_Steve:
copying this to my kaiser now totry, if it works ill see if i can have a look at getting a new kernel built over the weeekend. this is sort of a mute point for me now though since i got a G1 for xmas :) but ill try :)
[Tilt, TyTN II, MDA Vario III Android Development] DJ_Steve:
i got the previous io errors onmy kaiser also, investigating the img files on my laptop now though
[Tilt, TyTN II, MDA Vario III Android Development] anthonws:
It worked!!!

I assume the problem was the ROM, but I changed everything.

SPL, radio and ROM :)

See signature for more info.

Thank you all!

Anthon.
[Tilt, TyTN II, MDA Vario III Android Development] KeizerBAAS:
Nice! Now what would be the difference in these roms that makes it work in one and not in the other?

@DJSteve Would love a G1 as well, but here in the Netherlands we'll have to wait till February probably... In the meantime, a more or less working version would be great, thanks for the efforts!
[Tilt, TyTN II, MDA Vario III Android Development] ryoojin83:
Hey, I was having the same problems as you, but I only changed my Radio to get it working.

Old Radio: 1.65.21.18 [Kaiser]

New Radio: 1.65.24.36 [Neon / Niki]

ROM: Re-cooked version of NATF v5 [ATT Fully Loaded]

SPL: 3.29.Hard
[Tilt, TyTN II, MDA Vario III Android Development] biscuits1978:
Come to think about it, my radio is the 1.65.24.36 radio too.