yashsingh1/xdaforums huggingface dataset:
[Tilt, TyTN II, MDA Vario III Android Development] DeathmonkeyGTX:
Dude, why are you such an ass? Smoke a bowl. Or drink something. Whatever floats your boat. I don't like to drink, so I smoke. Driving high induces driving the speed limit and being courteous to other drivers. I understand how haret is a good idea, but I don't really mind excessive ROM flashing... I've been using NAND flash memory for a long while and never had a problem with using the living **** out of it. I'm also a stoner without a job, so I have plenty of time. And to the assclown that asks if using WinMo makes you MS's *****; somewhat. I really don't like Windows except for running games on XP. I run Mandriva Powerpack+ Spring 2008 for day-to-day bull****.

Defending my lack of sobriety aside, does running haret tax the MSM7200 on top of Android? I don't really like emulators for that reason. I'm not in any hurry to put Android on my phone, but it would be nifty. If I could use it on the Kaiser reliably, I'd probably start developing for it. I don't mind coding for Linux, but I despise coding for WinMo. And **** dude with his bird flu. It attacks folks with weak immune systems that work in close contact with infected poultry populations. I don't. I chill in close contact with stoners, and I don't get sick. I get allergy problems but that's about it.

I'll go back to lurking. Thanks to the one individual that wasn't a total ass and was nice enough to tell me wtf is going on.

post script; I had a Hermes first. I ran my 1998 Honda Accord EX with a 5 speed and 3.2L V6 into an '82 Caprice Classic head on at 90MPH. My Hermes flew out of my belt pouch deal and slammed screen first into the steering wheel and fell apart. Then I bought a broken WIZA100 from eBay and swapped the motherboard out of my friend's busted LCD Wizard, and voila! Then my mamma died and I used $449.99 of the inheritance money to buy me a Kaiser. Used dad's inheritance for the Hermes :-D.
[Tilt, TyTN II, MDA Vario III Android Development] Bartuk:
Ok i dont know if i did something wrong but i downloaded the new initrd and the new zimage, now when i boot it shows the red glowing thing(dunno how its called).thats good or bad?

overall its working without any problems for 45 mins now and im still playing around with it.

btw is the battery thing working for anyone?

oh and the clock seems to be somehow going to slow...
[Tilt, TyTN II, MDA Vario III Android Development] xmoo:
The red glowing thing is showing cause you use a other initrd-android.

The battery and time are not working for now......

Have fun :D

This thread get's updated very very fast :P
[Tilt, TyTN II, MDA Vario III Android Development] Bartuk:
im using the one mentioned in this post:

so this is not the newest? or its a wrong one? or i missunderstood something?
[Tilt, TyTN II, MDA Vario III Android Development] xmoo:
initrd-android is like a engine. The new one is edited by the website's owner. He has added world clock + sms and removed the API Demo's. The original one has no SMS or World Clock but has API Demo's.

There are more version on the web. Just google it and try them out :D
[Tilt, TyTN II, MDA Vario III Android Development] Bartuk:
ah ok thx for the info :)
[Tilt, TyTN II, MDA Vario III Android Development] slovoflud:
wow, clearTemp actually worked :) still get freezes, but at least it boots :)

man, i can't wait.... only sticking with my Vario because of android. WM is ass!
[Tilt, TyTN II, MDA Vario III Android Development] xmoo:
Were you got ClearTemp from?? Give me link. I'll add that in post #1.
[Tilt, TyTN II, MDA Vario III Android Development] slovoflud:
cant remember, here - i uploaded it here:

http://www.4shared.com/file/50007273/5101a7bb/ClearTemp.html
[Tilt, TyTN II, MDA Vario III Android Development] xmoo:
Thx added in first post.
[Tilt, TyTN II, MDA Vario III Android Development] Laubscherc:
Worked 1st time on L26 V5. Just the cab install, and then the upgraded zimage
[Tilt, TyTN II, MDA Vario III Android Development] xmoo:
Try for 2nd time 3th time ...... :P
[Tilt, TyTN II, MDA Vario III Android Development] slovoflud:
i noticed in clearTemp you can reset SoftReset Count - my was on 10 when i reset mine. maybe it has something to do with that?
[Tilt, TyTN II, MDA Vario III Android Development] Laubscherc:
5th time and it still boots! - Changed to a newer initrd-android, still using stock haret

Haha, and now it hangs!
[Tilt, TyTN II, MDA Vario III Android Development] xmoo:
We are getting closer to the lighttt :D
[Tilt, TyTN II, MDA Vario III Android Development] Laubscherc:
Haha.... As long as you are not a bug, the light is cool! I am enjoying my kaiser again, and cannot wait to test the newer versions once the radio has been ported!
[Tilt, TyTN II, MDA Vario III Android Development] Imsaffor:
when I load with the latest zImage, using the cab installer and the latest haret "top link" It loads every time out of Haret. but I get an error on a black screen.

the resolution is pretty bad on the text but I believe it says

Kaiser_init_mmc: vres enable failed (-1)

what could this mean?
[Tilt, TyTN II, MDA Vario III Android Development] xmoo:
Dunno, you are the first who is getting this problemmmm
[Tilt, TyTN II, MDA Vario III Android Development] Imsaffor:
Just to add, I am using L26 V5 ROM.

EDIT: apparantly running from storage card was my problem, trying it from my internal storage runs perfect.
[Tilt, TyTN II, MDA Vario III Android Development] Mikulec:
I am total noob in this and I have just one question. When the android is fully functional (radio, connection, ....), how it will be ported to Kaiser? Will u still need WM to launch it?
[Tilt, TyTN II, MDA Vario III Android Development] slovoflud:
Linux, mate :)
[Tilt, TyTN II, MDA Vario III Android Development] ljinsane:
hey........HEY!

WE DONT CARE...THIS THREAD IS FOR lINUX ON kAISER DEVELOPMENT...LETS KEEP IT THAT WAY period.....THANKS
[Tilt, TyTN II, MDA Vario III Android Development] :
Dad wasn't good for much was he :-p

I'm sorry, I couldn't resist. I had to add one small piece of drivel to this thread.

Haret is a bootloader. It's a piece of software that almost all OS's need to get started. It doesn't tax the MSM7200 in any way (that I am aware of). As far as I can tell, it should totally blow away Windows Mobile when it starts up and put the device in a clean state, from which it can then bootstrap and start androids linux kernel.

This isn't unlike how android would start once it can be flashed to the devices nand memory, but a different bootloader is probably used at that point.

Windows, Max OSX, Linux, all have some kind of bootloader to get things going.

-James
[Tilt, TyTN II, MDA Vario III Android Development] guizzzmo:
Two interest link

http://www.oesf.org/forum/index.php?showtopic=25292&st=0

and

http://www.frandroid.com/393/installation-dandroid-sur-un-nokia-n810/

But i don't found the final version to install. Before that i want to test with haret if it's possible. But after compiling, i don't know what doing with all .img and zimage lol.
[Tilt, TyTN II, MDA Vario III Android Development] DJ_Steve:
i managed to get bot to partly work but it kernel panics just as part of android begins to boot. (if you extract the system and data gz's using something winrar then rename the system and data1 files to system.img and data.img before copying them to memory card you can bypas the dma errors for now)
[Tilt, TyTN II, MDA Vario III Android Development] qetuR:
Well, I guess theres more people smoking then you think. And as stated above, how the **** can you bring up your old Hermes stories, how you mum died, your car, and so on.

Go to some social forum, this isn't. In a way. At least not this thread.
[Tilt, TyTN II, MDA Vario III Android Development] corvus:
Prepare for a large post... :). Hi dcordes... maybe you remember me trying to port gpe to Universal...:D

OK. This is the status now for everybody knowing:

1) We have 2 android images:

The dcordes one: http://linuxtogo.org/~lgorris version 0.8 (correct me if i'm wrong)

and the vogues one: http://it029000.massey.ac.nz/vogue/android-23-10-08.zip (version 1.0)

2) We have some kernels:

The dcordes one from here: http://linuxtogo.org/~lgorris (new image) that i think is the patch against the android source you mentioned

The TheSurfer's that we was compiling yesterday and adding loop, nls_codepages and so on (read de las 10 pages)

The vogues one (in the zip from vogue) that must not work.

3) We all know (or must know) that the rootfs image must be 20M max or haret doesnt work. In the vogues image it seems to resolve this using a initrd that decompress system and data gz, mounts the image in a loop device and mount de loop device as /data and /system and then booting init1 (elf binary that i dont know what does)

dcordes kernel + dcordes 0.8= boots ok, but crush in android and map. Status reported earlier

dcordes kernel + vogues 1.0= boots, but android doesnt boot. Cant mount sdcard by codepage problems

TheSurfer kernel + vogues 1.0= boots, but androids doesnt boots, resolved problems with codepages, loop devices and now problem with irq (see TheSurfer post some pages back)

vogues kernel + vogues 1.0= Freeze in haret

I can test all the kernel/rootfs you want... please send me...

Corvus

PD: DeathmonkeyGTX and qetuR, please, it difficult maintain this forum free of "its ready?" "doesnt work" etc... if you both throw more sh**it to it the people that try to help will go to try to jump from eiffel tower without parachute... :rolleyes:
[Tilt, TyTN II, MDA Vario III Android Development] DJ_Steve:
is their a way of not using dma mode to access the memory card, i know it may be a bit slower but that may help to avoid the issues we are having at the moment
[Tilt, TyTN II, MDA Vario III Android Development] beboxed:
When its possible to extract the system.img and data.img from the vogue .gz archives and try to boot them, it's also possible to try and boot from the original Android 1.0 system.img and userdata.img file right?

I wonder what the difference between the vogue's .img file and the original Android .img files are.
[Tilt, TyTN II, MDA Vario III Android Development] DJ_Steve:
i dont have access to the original android 1.0 files but the vouge images wot boot currently (even in extracted form) - im going to try and compile up a new kernel to get round this dma issue
[Tilt, TyTN II, MDA Vario III Android Development] corvus:
Thats why i ask for the ones that yesterday compiled the 1.0 original to put the resulting files somewere to compare them... but not response... :(

Corvus.

PD: Yesterday I try to compile it but was unable...:(
[Tilt, TyTN II, MDA Vario III Android Development] DJ_Steve:
i cant imagine the android files them,selves have been modified, it wil be a matter of getting the kernel to work as needed more than the android files, - i managed to get android to partly boot but it kernel paniced.

compiling a new kernel now, added a load of new features into it , most are likely surplus but may aswell give them a try
[Tilt, TyTN II, MDA Vario III Android Development] beboxed:
I'll try to upload the .img's of Android 1.0 to aximilation's ftp server.

I'm waiting for the login credentials now
[Tilt, TyTN II, MDA Vario III Android Development] DJ_Steve:
ive managed to get rid of the dma errors by looks of it, still checking

least the system image extraction seemed to work better and didnt throw errors until it segfaulted
[Tilt, TyTN II, MDA Vario III Android Development] corvus:
It segfaulted whe trying to run init1??? Same problem here...

I just run the commands in ./init manually to see whats is wrong... I can mount /sdcard, can setup the loop devices, can mount it, but segfaults whe launch init1

Anyone knows what init1 does???
[Tilt, TyTN II, MDA Vario III Android Development] TheSurfer:
Good point, I uploaded the resulting system.img and userdata.img files:

http://rapidshare.com/files/157055066/system.img.html

http://rapidshare.com/files/157053299/userdata.img.html

On a related note: Google just committed some G1-specific code, see http://git.source.android.com/?p=platform/vendor/htc/dream.git;a=tree

It seems like the WiFi-part is proprietary, the Kaiser probably needs the /system/etc/wifi/ files from a G1 in order to get that working.
[Tilt, TyTN II, MDA Vario III Android Development] TheSurfer:
If it segfaults you probably didn't built ashmem in the kernel. Make sure CONFIG_ASHMEM=y is in there.

How did you get rid of the DMA errors? Did you disable a setting in the kernel config?
[Tilt, TyTN II, MDA Vario III Android Development] DJ_Steve:
enabled allow large block devices and other things - ill upload the zimage soon, wifi i also enabled in the kernel so waiting to see if that helps (if i can get android booting, its extracting data image at the moment - disabled the system image extract for now and modded the initrd a liitle so i can watch more what its doing

EDIT: ok it does kick out with dma errors but it takes way longer to do it - progress. anyone know how to force pio mode transfers as that would likely stop the dma errors
[Tilt, TyTN II, MDA Vario III Android Development] beboxed:
-- snip, not necessary anymore --
[Tilt, TyTN II, MDA Vario III Android Development] piethein:
You can set this with "hdparm". Is there such a commando?

hdparm -S /dev/hda
[Tilt, TyTN II, MDA Vario III Android Development] DJ_Steve:
yes hdparm is in the initrd so i just modified the inti script to try using that on /dev/block/mmcblk0 (which seems to be the mem card) - trying now

EDIT: nope hdparm wont work on block devices only hard drives, any other ideas lol
[Tilt, TyTN II, MDA Vario III Android Development] dubbeld00:
http://en.wikipedia.org/wiki/Runlevel

http://en.wikipedia.org/wiki/Init

"Single-user mode with all local filesystems mounted (read-write)"

Format the SD card to Ext3 (kidding...), no I really don't know, rewrite the driver, or just boot from ROM

There is some nice documentation on DMA... maybe you can do something with it... I really don't know what the exact problem is ;) And don't have the time to find it out...
[Tilt, TyTN II, MDA Vario III Android Development] DJ_Steve:
init1 is a file so i doubt its actually runlevel 1 - besides runlevel needs to be like 3 or 5 normally for all features to work on linux
[Tilt, TyTN II, MDA Vario III Android Development] corvus:
lol

init1 != init 1 :P

init1 is the last command (a elf binary) that init script runs...
[Tilt, TyTN II, MDA Vario III Android Development] DJ_Steve:
making progress sort of, managed to get the 'android' text up, getting few errors after that now lol but working on it :)
[Tilt, TyTN II, MDA Vario III Android Development] corvus:
/dev/block/mmcblk0 is like /dev/hda (disk, well card)

and /dev/block/mmcblk0p1 is like /dev/hda1 (partition in the sd card)

And yes, you cant do it in a block device...:S

I suggest you try to skip the dma problem using a pc to work with many data because people more skilled than us (dcordes and others) spend many hours in this and cant fix it...
[Tilt, TyTN II, MDA Vario III Android Development] corvus:
How???

:confused:
[Tilt, TyTN II, MDA Vario III Android Development] DJ_Steve:
ive got round the dma issue for the moment, i now get loads of binder releated errors, any ideas folks ??
[Tilt, TyTN II, MDA Vario III Android Development] TheSurfer:
Did you make sure to enable CONFIG_ANDROID_BINDER_IPC=y in the kernel?

Any info how you got 'round the DMA issues?
[Tilt, TyTN II, MDA Vario III Android Development] DJ_Steve:
i modified the mmc driver a little bit - qworking with uncompressed images too but im not stuck with androids 'binder' app that keeps killing itself

going to upload zimage and initrd shortly just compiling a new kernel to test something
[Tilt, TyTN II, MDA Vario III Android Development] DJ_Steve:
not 100% sure on weather i have got round dma issues, but ive had no errors in that respect at the moment ,

and yes binder ipc is set to y,
[Tilt, TyTN II, MDA Vario III Android Development] DJ_Steve:
ok new zimage and initrd (not many edits to initrd though)

http://www.dmpwap.net/android/zImage

http://www.dmpwap.net/android/initrd.gz

extract the system and data gz files and rename outputs to system.img and data.img that should help - still getting binder errors haven got a clue why though :S
[Tilt, TyTN II, MDA Vario III Android Development] corvus:
Maybe this can solve???

chmod -R a+rw /dev/binder
[Tilt, TyTN II, MDA Vario III Android Development] DJ_Steve:
ill give that chmod a go but i doubt its going to help lol
[Tilt, TyTN II, MDA Vario III Android Development] echofloripa:
First Page Status!!!!!

PLEASE PLEASE PLEASE, Can someone update the first and second posts with a bread summary of were we are? It's becoming a pain keep up with all this distracting posts and irrelevant discussion.

Lukas (Dcordes): do you have the rights to edit the first post? If not, who's got it? If no one have it, I would suggest to have a new thread, which should have its first page updated as we move along...

Or at the minimum, you guys could also edit the first post and add the last relevant posts with the current status from dcordes and corvus.

regards

Emerson
[Tilt, TyTN II, MDA Vario III Android Development] DJ_Steve:
can someone remind me if sound workedo n android at all ? im adding network and sound into my kernel while i recompile.
[Tilt, TyTN II, MDA Vario III Android Development] DJ_Steve:
i agree echfloripa, we probably need a new thread though very likey
[Tilt, TyTN II, MDA Vario III Android Development] corvus:
I thinks sound only works in speaker... but not sure
[Tilt, TyTN II, MDA Vario III Android Development] DJ_Steve:
just got another kernel panic, ill let some of the more smart people take a look at this for a bit, new z image has been uploaded at limk above
[Tilt, TyTN II, MDA Vario III Android Development] corvus:
Segfault do you mean?

Kernel panic is an oops and freeze, segfault (Segmentation Fault) crash program...

A curious discover... ls works, but ls -la segfaults :rolleyes:
[Tilt, TyTN II, MDA Vario III Android Development] DJ_Steve:
nope this one was a kernel panic, said so on the screen :) theirs something in that android file image thats booting things out, but cant for the life of me work out what
[Tilt, TyTN II, MDA Vario III Android Development] TheSurfer:
Thanks, it would be nice if you could also post the diff of the source code, so the DMA fixes/hacks can be incorporated.
[Tilt, TyTN II, MDA Vario III Android Development] DJ_Steve:
dont know how to do diffs- simple fix though, go into drivers/mmc/core open up core.c and search for limit_us change it to 400000 and 200000 for each of the 2 lines you should see with numbers on them

EDIT: back to datamover errors now :( looks like my dma hack hasnt fully worked
[Tilt, TyTN II, MDA Vario III Android Development] TheSurfer:
Thanks, I played a bit with those settings, but it doesn't really fix the DMA errors (they keep popping up later).

We either need a fix for these errors, or strip the system.img (remove some apps) so it will be small enough to boot without problems.
[Tilt, TyTN II, MDA Vario III Android Development] DJ_Steve:
yea, or we need to find out the controlloer for the sd cards and fidn a better driver perhaps
[Tilt, TyTN II, MDA Vario III Android Development] corvus:
dcordes upload one new diff in:

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

You must use it in the android source...
[Tilt, TyTN II, MDA Vario III Android Development] DJ_Steve:
how do you run diffs against code ?
[Tilt, TyTN II, MDA Vario III Android Development] TheSurfer:
patch -p1 < ../path/to/diff

This patch is against the following branch btw, not the android source: http://github.com/android/kernel_msm/tree/android-msm-htc-2.6.25

Resulting zImage can be found at http://rapidshare.com/files/157095774/zImage.html, unfortunately still DMA errors.
[Tilt, TyTN II, MDA Vario III Android Development] drdingo21:
You haven't been reading this thread for weeks. You asked three questions that were already answered several ****ing times.

Now shut your suck hole before I go back through this thread and quote the answers to the questions you asked. **** Knuckle.
[Tilt, TyTN II, MDA Vario III Android Development] DJ_Steve:
any ideas if we can 'force' hdparm to turn off dma ? becasue thats what we really need ta do
[Tilt, TyTN II, MDA Vario III Android Development] corvus:
But with decompressed images androids boot??'

Did you see dma errors in dmesg or where??? i didnt get dma errors...
[Tilt, TyTN II, MDA Vario III Android Development] edzilla:
I was wondering why exactly we need to boot of the sd card? on my kaiser I have enough room on the integrated space to copy all necessary files to /
[Tilt, TyTN II, MDA Vario III Android Development] piethein:
What's the difference between this branch: http://github.com/android/kernel_msm/tree/android-msm-htc-2.6.25

and this branch: http://git.linuxtogo.org/?p=groups/mobile-linux/kernel.git;a=shortlog;h=refs/heads/htc-vogue
[Tilt, TyTN II, MDA Vario III Android Development] DJ_Steve:
just had a thought, this may or may not work though, how about having more than one 'boot image' eg have system which contains the root files then an image called lib for example which gets mounted to /lib on boot - would that get round harets issues ?
[Tilt, TyTN II, MDA Vario III Android Development] corvus:
I think i post this before, but this is the way they are doing... at least in vogue files (i think android ones creates 3 files too, system, data and ramdisk).

We have a ramdisk/initrd that has less tha 20M and boots from haret, then configure 2 loop devices and mount system and data in this devices... so no problem with 20M limit.

Corvus.
[Tilt, TyTN II, MDA Vario III Android Development] DJ_Steve:
what i was thinking (and am trying now) is putting all of the primary android system into the initrd, then having the system/lib and system/apps folders (which total about 25+mb) in seperate images as those 2 folders will be rarely edited so the dma issue we have may not be a problem
[Tilt, TyTN II, MDA Vario III Android Development] corvus:
Maybe to avoid DMA errors can disable +CONFIG_HAS_DMA=y in htckaiser_defconf... but will be slow... very slow...
[Tilt, TyTN II, MDA Vario III Android Development] dot.treo:
This will only postpone the problem, if it works at all. I think it is good that is such a show stopper at the moment, so it will be resolved as soon as possible.
[Tilt, TyTN II, MDA Vario III Android Development] DJ_Steve:
yes it will be resolved when someone most likely rewrites the entire mmc driver for the kernel probably
[Tilt, TyTN II, MDA Vario III Android Development] DJ_Steve:
:0 my combining the files didnt work anyway, kernel can only load a 4mb ramdrive :(,

EDIT: my error i get at the moment

A N D R O I D
sh: cant access tty; job control turned off
binder: 508:508 unknown command 25356
binder: 508:508 ioctl c0186201 be89caf8 returned -22
binder: 508:508 ERROR: Thread Waiting for process work before calling

then if i wait about 2 mins i get crap loads of datamover errors and such
[Tilt, TyTN II, MDA Vario III Android Development] Speaking_On:
Related question

Please try it and let us know how far you get. Reporting on which of the Windows mobile ROMs you're starting with would also be a big help.

I had actually been wondering something similar: how much of the Windows Mobile ROM could be stripped away for the system to be functional enough for haret to boot. That doesn't change the basic strategy (having Windows Mobile be present to run the bootloader), but if we can leave out major portions of the ROM, it might be slim enough to work. To take one example, could you leave out the Windows mobile radio, and rely on the linux/android side to provide that?

Testing this pretty much requires a system you can live without, though, as it presumes you wouldn't be able to switch back to Windows Mobile.