Database Info

Touch Software Collaboration

I wanted to get a thread dedicated to getting the applications out of the Touch .nb, and into the Wizard - and specifically the "cube" and "touch" functionality that is the trademark of the new phone.
Please save "oh, I'd like" or "oh, wow" stuff for other threads - this is a dev discussion.
Criteria: Working discussions on what's been done, what are we doing, and what could be done to get the excellent new features to work.
I hope that by sharing information - we can key in on the results much faster then everyone working on their own.

Software Packages
This post is a running list of applications, and their status:
Application............. .Status:
HTC Camera ............. .???
MediaHubMini ............. .???
QuickDial ............. .???
Streaming Media ............. .???
Streaming Player ............. .???
Cube ............. .French rom working, no WWE yet
Dialer Pad ............. .Done
Comm Manager ............. .Done
Today Home Theme ............. .Done
If someone can PM me who's current on this thread, I'll update the remaining items.
.

Kickoff Status
Here's what I've tried so far:
Using the 1413 as a base, I've taken and replaced the OEM folders from the touch build and replaced the 1413 folders -completly. This resulted in the phone self power cycling at the 3rd splash screen.
I've also taken the entire touch build, replaced the ROM contents with the one from 1413 (and I might have replaced the /SYS/OS folder as well - going off memory). This was the most successful, as I was able to boot the phone and get a lot of the touch's functionality. Issues were: SID Lock error, no "touch" function, and button mapping was wrong - only button 1 showed up on settings - buttons.

More info (a little)
Well, to follow up on my note in the other thread. I did pretty much what you did and ended up in the same place.
I did discover that the two other "raw" files in the original leak contained xip contents. I'm not sure why there are two of them, and they contain similar contents. I ran a build using the one I've labeled xip1 and it gave an error about missing build.rgu in buildos. I then ran a build using the one I labeled xip here (which has a build.rgu) and it built and booted, but worked essentially the same as when using an older wizard xip.
Anyway, time for bed now.
PS I tried to upload a zip of the two xip sections but it failed. Forum maintenance I suppose. Maybe I'll try again tomorrow if anyone seems interested.
Edit: Tried again to upload, failed.

I think we should start by the Dial Pad... I think it will be the easy thing to do.
Check this Hermes Rom:
http://wmblack.info/
and this:
http://www.4winmobile.com/forums/hermes-black-rom-support/9792-released-black-iv-shadow.html

Why not port the entire ROM ?
Just a thought.
BTW, from what I know, in order to make it work, you will have to use the XIP from the Wizard, not the one from Touch.
I have some work now...but i will try and do that bit later...today or tomorrow.

anichillus said:
Why not port the entire ROM ?
Just a thought.
BTW, from what I know, in order to make it work, you will have to use the XIP from the Wizard, not the one from Touch.
I have some work now...but i will try and do that bit later...today or tomorrow.
Click to expand...
Click to collapse
I also thought this... But now we have an official build from ms... I think it is a bit more stable than a ported version (if i'm wrong, please correct me).
@joaosousa:
I tried to port the Dialpad yesterday... But it seemed that I missed some needed files/registry hacks.... Still trying.
Vi

I also think we should keep the official build from ms... It's very stable...

any luck with touch dialer skin?

In all seriousness... the Today plug-ins for the HTC touch are fricking ugly.

Anything new in here?

joaosousa said:
Anything new in here?
Click to expand...
Click to collapse
Ya... I just flashed my wizard... Without the correct XIP partition -> stuck at 87% but bootloader works... so i think i'll get my wizard back
vi

omg... Hope all goes right with your wizard...

For those who want to play...
OK, for those who want to play with the Touch Rom, here's a rapidshare link to download a "working" nk.nbf. I've also included total commander, and a registry editor for those who might want to tinker with getting things to work.
The main issues are these:
1) Pull the sim card before flashing, or you won't be able to to get to the today screen.
2) Since the elf is only a one button machine, most of the buttons do nothing, including the power button. You'll have to take out the battery to turn it off. (Unless you can figure out the registry changes needed to make it work.)
3) Don't worry about setting your timezone in the initial screen. You can set it later from the settings menu.
4) Be ready to flash back from bootloader mode when you're done exploring!
5) I pulled adobe acrobat, catalog, autoupdate. Everything else is pretty much stock. So you can get a feel for what's included, and what you might want to pull for use in the Wizard!
This is OS only.
Have fun!
Rapidshare Link: http://rapidshare.com/files/36574080/TouchROM-nk.nbf.rar

Here's a question to those who have tried it so far: has anyone seen it working, or know which application controls the 'cube' function? Is it the biotouch app?

edhaas said:
OK, for those who want to play with the Touch Rom, here's a rapidshare link to download a "working" nk.nbf. I've also included total commander, and a registry editor for those who might want to tinker with getting things to work.
The main issues are these:
1) Pull the sim card before flashing, or you won't be able to to get to the today screen.
2) Since the elf is only a one button machine, most of the buttons do nothing, including the power button. You'll have to take out the battery to turn it off. (Unless you can figure out the registry changes needed to make it work.)
3) Don't worry about setting your timezone in the initial screen. You can set it later from the settings menu.
4) Be ready to flash back from bootloader mode when you're done exploring!
5) I pulled adobe acrobat, catalog, autoupdate. Everything else is pretty much stock. So you can get a feel for what's included, and what you might want to pull for use in the Wizard!
This is OS only.
Have fun!
Rapidshare Link: http://rapidshare.com/files/36574080/TouchROM-nk.nbf.rar
Click to expand...
Click to collapse
what do you mean of working nbf, did you mean it is Touch fully rom, or mixed with wizard rom??

anichillus said:
Why not port the entire ROM ?
Just a thought.
BTW, from what I know, in order to make it work, you will have to use the XIP from the Wizard, not the one from Touch.
I have some work now...but i will try and do that bit later...today or tomorrow.
Click to expand...
Click to collapse
Yes, understood. I think the fact that it works just as well with either XIP just shows how similar the two machines actually are. Either that, or whoever "leaked" the rom included an appropriate XIP on purpose.

its right said:
what do you mean of working nbf, did you mean it is Touch fully rom, or mixed with wizard rom??
Click to expand...
Click to collapse
Fully Touch Rom. But it has been restructured to fit inside the partition settings of the Wizard.

mattk_r said:
Here's a question to those who have tried it so far: has anyone seen it working, or know which application controls the 'cube' function? Is it the biotouch app?
Click to expand...
Click to collapse
For me it didn't work. Did you notice a kind of "klick" every 2 - 5 seconds? it sounds like if the speaker are turnend on and off...
Vi

its right said:
what do you mean of working nbf, did you mean it is Touch fully rom, or mixed with wizard rom??
Click to expand...
Click to collapse
The SYS and OEM folders from Touch, the ROM folder from 1413 (going off assumption here - correct me if I'm wrong )

Yikes!!!

Okay,
I have had my wizard for about a year now and in that time have flashed countless ROMs without any major problems, but yesterday I came as close as I ever have to bricking my device, and the crazy thing is that I have no idea why. I am hoping that the "real men of genius" here can help me figure out what the freak happened, or specifically what I probably did wrong
Before anyone asks, yes my phone is SIM and CID unlocked and it is a G3.
I recently moved from Core 2.0n to mfrazzz XDA Mobile 6. I really liked it but with mattr_k's easy kitchen and stripped down base I figured I could play with it a little to get some more of the apps and settings I like in it from the get go, and save the space without the ones I don't. I had been playing around with the core kitchen and the first kitchen mattk_r upped so I had a pretty good idea of what to do.
here is what happened as best as I can remember ( I should have taken notes as it was happening but I was too freaked out!)
I created the OEM directory and copied the reg tweaks and packages that I wanted from Pandora's Box (v2). I ran Build OS and selected all and it completed without problem. I ran createROM.bat and no problems there. I went into flashing, built the nbf and flashed. The flash went fine with no hang ups.
When the device restarted after flashing it went to the first splash screen and then stayed white. I left it this way for 10 minutes and then it was still like this I tried a soft reset. It reset fine but stayed white. I then tried flashing back to the original mfrazzz ROM but when it got to 95% the flash tool errored out and closed. The phone was stuck with the progress bar at 95%.
I freaked out a little and then rembered that I still had a copy of wizard love on this computer so I put it in bootloader mode and then flashed that. That got the phone back up. I then tried reflashing my "cooked" ROM. It loaded this time, but the today screen was a white background and some of the today plugins were extremely distorted and it just wasn't right.
I reflashed wizard love, and then reflashed the mfrazzz's original XDA Mobile. My phone is now fine.
Any ideas on what the heck happened.

Just guessing here....did you messed with the splash screens ?

anichillus said:
Just guessing here....did you messed with the splash screens ?
Click to expand...
Click to collapse
Not on purpose, followed the steps above as far as I can recall.

You almost wrote a book about this ;P
The day when my device amost brick by dcdivenut
"..Was raining on this night and my device stop to work.."
hehe only joking

When you built the nk.nbf file, did you build in a splash screen or htc_logo? Or did you only build the OS into the file? If you built a splash screen, you have to verify the file sizes. htc_logo has to be exactly 64K, and the splash screen has to be 196608 bytes in size. If these are off, you will have hangs and stuff.
If you only did the OS, what is the size of your nk.nbf? If its too big it wouldn't have flashed.
BTW: Welcome to the world of rom cooking... I've scared myself a few times

ouch - been there a few times myself - but usually 'cause I was really hacking the OS components, like compressing the files in the XIP or OS directory.
If you mixed a Pandora kitchen with another OEM folder (or visa-vera), you might have left out critical components from the OEMAPPS/OEMDRIVERS, etc, Default and Langdb folders. I moved them to the SYS folder to allow more "generic" OEM package contents.
You might start with a complete base kitchen and work from there. Be wary of mixing - until you're very comfortable moving OS components - and can recognize critical pieces!

When you built the nk.nbf file, did you build in a splash screen or htc_logo? Or did you only build the OS into the file? If you built a splash screen, you have to verify the file sizes. htc_logo has to be exactly 64K, and the splash screen has to be 196608 bytes in size. If these are off, you will have hangs and stuff.
I didn't touch splash or anything like that.
mattk_r said:
ouch - been there a few times myself - but usually 'cause I was really hacking the OS components, like compressing the files in the XIP or OS directory.
If you mixed a Pandora kitchen with another OEM folder (or visa-vera), you might have left out critical components from the OEMAPPS/OEMDRIVERS, etc, Default and Langdb folders. I moved them to the SYS folder to allow more "generic" OEM package contents.
You might start with a complete base kitchen and work from there. Be wary of mixing - until you're very comfortable moving OS components - and can recognize critical pieces!
Click to expand...
Click to collapse
I did use only your base kitchen from the "stripped thread" and actually redownloaded the OEM package from the same post as well so I wouldn't mix packages. I guess I will give it another shot when I have the time to rescue it from the dead if need be!

boto said:
You almost wrote a book about this ;P
The day when my device amost brick by dcdivenut
"..Was raining on this night and my device stop to work.."
hehe only joking
Click to expand...
Click to collapse
well it would definitely be a tragicomedy!! or perhaps a nail biting thriller! I wanted to give as much detail as possible since I hate it when someone posts, "I bricked my device, what happened?!?!?! PLEASE HELP!!!!"

dcdivenut said:
When you built the nk.nbf file, did you build in a splash screen or htc_logo? Or did you only build the OS into the file? If you built a splash screen, you have to verify the file sizes. htc_logo has to be exactly 64K, and the splash screen has to be 196608 bytes in size. If these are off, you will have hangs and stuff.
I didn't touch splash or anything like that.
I did use only your base kitchen from the "stripped thread" and actually redownloaded the OEM package from the same post as well so I wouldn't mix packages. I guess I will give it another shot when I have the time to rescue it from the dead if need be!
Click to expand...
Click to collapse
If you're using the whole thing, just be sure to only enter WWE for language, and check only OS line box, point to the ../temp folder for the ...-OS.nb file, select OS from the drop down on the same line, and click the mouse in the address box so it will auto-fill, but don't change it.
I have added splash screens and extended roms in, but not in the kitchen, or any roms I post. I figure it adds too much completixy and liability for users.

mattk_r said:
If you're using the whole thing, just be sure to only enter WWE for language, and check only OS line box, point to the ../temp folder for the ...-OS.nb file, select OS from the drop down on the same line, and click the mouse in the address box so it will auto-fill, but don't change it.
I have added splash screens and extended roms in, but not in the kitchen, or any roms I post. I figure it adds too much completixy and liability for users.
Click to expand...
Click to collapse
I don't think I entered WWE for language, but I did everything else, and didn't do anything extra. That is something to try...

UPDATE!!
I am not sure that something as simple as typing WWE in the language field is what made the difference but I did and it worked. On my home computer I redownloaded the kitchen, base and OEM packages.
I first flashed it with nothing added to the OEM folder and it worked
Then I added to the OEM folder and that worked.
Then I got cocky, redownloaded mfrazzz's original XDA Mobile 6, used Corekitchen to dump, extracted the x-mfrazzz and x-faria settings, combined parts from both and that...............
WORKED!!! YAY! doing a jig (quielty so as not to wake the fiance at 1AM!)
Now all I need to do to really get this to what I want is to make make packages for the following
1. Live search (not live, just search)
2. CloseAll (I just like it!)
3. Softkey from mfrazz's (I prefer it to the Sharkey 48 I have)
4. Get working package of Photodialer today plugin
5. Time sync package from XDA Mobile 6
Any help from the pros in getting this up woudl be awesome! Hopefully others will be able to use them as well.

dcdivenut said:
Then I got cocky, redownloaded mfrazzz's original XDA Mobile 6, used Corekitchen to dump, extracted the x-mfrazzz and x-faria settings, combined parts from both and that...............
WORKED!!! YAY! doing a jig (quielty so as not to wake the fiance at 1AM!)
Now all I need to do to really get this to what I want is to make make packages for the following
1. Live search (not live, just search)
2. CloseAll (I just like it!)
3. Softkey from mfrazz's (I prefer it to the Sharkey 48 I have)
4. Get working package of Photodialer today plugin
5. Time sync package from XDA Mobile 6
Click to expand...
Click to collapse
IF you used Core Kitchen to dump my rom then you have the OEM folders I used and that has SoftKeyEx, TimeSync and you'll find Windows Live and Windows Live search are actually there in the OEM and not in SYS. So I think you have most of what you need now .

mfrazzz said:
IF you used Core Kitchen to dump my rom then you have the OEM folders I used and that has SoftKeyEx, TimeSync and you'll find Windows Live and Windows Live search are actually there in the OEM and not in SYS. So I think you have most of what you need now .
Click to expand...
Click to collapse
SWEET!
Soft key - Check
Time Sync - Check
I found this in the .rgu file in the x-mfrazzz apps. is this for the softkey app or something else?
[HKEY_LOCAL_MACHINE\Services\Stk_service]
"Dll"="\\windows\\STK_Service.dll"
"Description"="STK Service"
"DisplayName"="STK Service"
"Context"=dword:00000001
"Keep"=dword:00000001
"Order"=dword:00000005
"Index"=dword:00000005
Windows Live search - In your OEM folder there are two folders, WindowsLive and WindowsLive_DPI_96. These are both currently also in the SYS folder of mattr_k's base so wouldn't this throw an error? I know I am missing something stupid here.
Ring tones - Is there anyway I can build mp3's into the ROM? I tried placing them in the x-mfrazzz settings folder in my SYS but that didn't work, even though they get built into the windows directory. I looked in the .rgu and there doesn;t seem to be anything about where to place these
PHMReg Edit - I thought I remembered you saying something about being able to export reg settings in the correct format. I was playing around with this and the closest thing I could find was backup. That created a .rbk file but I get gibberish in notepad when I try to open it. My thought process here was to use get all the reg setting the way I want, export them, get them into a .rgu file and then build them in. Any ideas?
How do I get it so that ini_tray.lnk is not automatically in startup?.

Has anyone seen an error message when starting buildOS that just says there was a bug and the app is shutting down?

dcdivenut said:
Has anyone seen an error message when starting buildOS that just says there was a bug and the app is shutting down?
Click to expand...
Click to collapse
Yes... If I remember right that was when I had a options.xml that wasn't saved in Unicode (or maybe it was the .rgu or .dsm). Pull packages out and you can figure out which one is teh offending package. Then look at the xml, rgu, and dsm (but I'm pretty sure it was a bad options.xml)

mfrazzz said:
Yes... If I remember right that was when I had a options.xml that wasn't saved in Unicode (or maybe it was the .rgu or .dsm). Pull packages out and you can figure out which one is teh offending package. Then look at the xml, rgu, and dsm (but I'm pretty sure it was a bad options.xml)
Click to expand...
Click to collapse
Cool, will check when I get home, any thought on post above?

Hmmmmmm...
Seems to me your mind was on your woman and not your Wizard... just a thought,ehehe!
Congrats bro!

My woman gets mad because my mind is usually on my Wizard and my Hermes.. lol .. and not on her.. go figure...

Madcap180 said:
My woman gets mad because my mind is usually on my Wizard and my Hermes.. lol .. and not on her.. go figure...
Click to expand...
Click to collapse
dc just got engaged.....

Congrats DC ... if you ever need someone to pick the lock on that ball and chain, let me know...j/k

[REF]Linwizard/ Linux running on Elf! Now what?

Hi guys!
It took me a while to make it running. I get into the login screen, but login without keyboard is kind of tricky. Anyone an idea how to proceed from here?
Squix

Could you share?
Hi,
could you please share how you did it and post the necessary files? Once i have it running maybe i can help you, but it doesent work on my touch yet. Are you using haret? If so could you post your default.txt initrd haret.exe ... and all the other files needed? Which ROM are you using, how much memory do you have free (RAM/ROM). Sorry if i annoy you, but i want to run Linux on my elf
greetz and thx
Oli

You guys are out of your minds... I'm excited how your experiment will turn out....

up up!! =) This was my dream from the beginning, can't wait))

i tried, but i think that our elf is poor of RAM memory...

squix78 said:
Hi guys!
It took me a while to make it running. I get into the login screen, but login without keyboard is kind of tricky. Anyone an idea how to proceed from here?
Squix
Click to expand...
Click to collapse
Did you make any change to Linwizard? Care to share how you get it working? How about getting Android running on the Elf?

Hi guys!
Sorry I couldn't get back to you earlier. I'd like to zip my haret setup and post it here, but right now I don't have the time for it. Maybe tonight...
But basically I'm using the standart linwizard initrd and zImage files, but I replaced the older 0.5.0 version of Haret if the newer 0.5.1. For the first run I connected to the Elf with telnet to see which processes were running and killed all, that I thought I wouldn't need. Then I made a shortcut to the haret file and made sure, that it would be available in the start menu. So I didn't have to run the file explorer which consumes a lot of RAM. I also closed ActiveSync and made a soft reset before running haret and linux.
For the subsequent runs i added the kill commands to the default.txt file. Of course, this is a little bit dangerous, but works well. Ah, and another thing:
I added the root wait to the default.txt command line options. This leaves some time for the system to recognize the file system. Before that I sometimes out Kernel Panics. Here's my default.txt, but be careful with the kill commands!!!
kill QuickDial.exe
kill MediaHubMini.exe
kill APLauncher.exe
kill Biotouch.exe
kill tmail.exe
kill SAPSettings.exe
kill connmgr.exe
set MTYPE 6666
set KERNEL "zImage"
set INITRD "initrd"
set CMDLINE "rootdelay=10 root=/dev/ram0 ramdisk_size=20504 init=/linuxrc rw"
bootlinux
About my initial question: after getting to the login screen I can connect to the Elf with the USB wire and on my WinXP machine I get a "new hardware found : ether gadget" dialog. But I can't find any drivers for that. Does anyone knowwhat I could do here (besides the obvious tip to use Linux on the desktop machine). If that would be working, I could use ssh to log in to the touch ssh server and I could start the x server from there...
So far I had no luck to run android. This might be because it's compiled with different options or because it consumes more RAM. I think the Elf resets immediately after pressing run in Haret.
[UPDATE]: I could solve the "no keyboard" problem by attaching the fully bootet linux-on-elf to my Mac. The Mac recognized the CDC Ethernet device and I could login using ssh to the dropbear server on the ELF. From there I could run startx and even had a very simple x server running with a clock and a xterm! If this is running, why shouldn't we make android running on our touch?!

Perhaps that's because Elf has small RAM as you mentioned... did any1 tried on Elfin?

After I could bring up the Linwizard's x server with the two mini apps I could even boot into the first three boot messages of android. But after that it dies:
...
init: HOW ARE YOU GENTLEMEN
init: reading config files
init: device init
_ (blinking cursor)
does anyone have an idea what that could mean? the blinking cursor somehow seems to signal that it hasn't died yet, but there's no progress either...
[Update]: Hm, the linux really didn't die. When I plug in the usb wire I get:
udc: USB reset done, gadget ether. The question is, how can I continue from here. What is androids IP. I tried to pass it to the cmdline argument, but no luck so far

Android Kernel and Framebuffer
There are several Problems. First you need an Android patched and enabled kernel. I am working on that now. The second Problem is that the omap framebuffer driver doesnt support double buffering.
With the little hack from here it could work. But i havent had the time to try it yet. When i am finished with testing i'll post my results here.
greetz
Oli

I'm able to boot Linwizard 0.2.0 on my Elfin. Great work from the Linwizard team!

With the new Linwizard kernel I even get the tux Logo and after using the android initrd I get a ANDROID line and a blinking cursor. How far are we now from bringing up the x server?

Anyone successful?
I forgot to mention that I have a WM6.1 Blue elves images on my ELF. With the KILL commands I'm trying to free up some space before starting linux

Hav you tried with the light ROM?? and please anyone who has an ELFIN try to run android on it)) if it's successful I'll buy one)) for now I have just an ELF

For the moment my N95 is in service for repair, so i can't loose my only way of comunicating with the outer world, but as soon as it gets back me, i'll try Android and post back results

Sorry, didn't have time to try the light rom yet and probably neither for the rest of the weekend... I hope to get to that next week...

And try to find the reg tweaks to save RAM. Coz for now I'm not ready to to change my ROM and delete everything))

NFS?
Was any one of you mounting the android image over nfs? What are the CMDLINE options and which IP will the kernel have afterwards? Before going on I'd like to try the NFS way, just to see how far we can get, if the cell phone is attached to a supporting Laptop (not that mobile though)

First you need the Linwizard android branch kernel. I've downloaded the android branch from Linwizard git server and compiled my own.
After that you need to export your android file system via NFS on the PC side. On your Elf, do a 'mount -t nfs -o nolock <you pc ip address>:<file path to your android file system> <local mount point on Elf>'. After that, do a chroot on Elf to start Android. See http://elinux.org/Android_on_OMAP#Start_up for details.
I've tried this on my Elfin and I can see the red eye moving. But after some time I get a segmentation fault and the red eye stops. The Elfin did not hang though. I can still ssh into it. I have not had time to further test after this.

nothing booting?
on my HTC elf it says not much text. last line is: booting to kernel.
after that it goes gray and 2 seconds later it goes to a white screen what am i doing wrong.
my default.txt is attached.
thanks

Official "Native Linux/Debian" Thread

Ok, theres a lot of threads out there on getting Debian working "with" Android side by side. What about getting Debian working primarily and natively? You can easily modify the bootloader to boot into Debian.
No I'm not talking about chrooting into debian from the Android environment.
With this being said there are plenty of possibilities. Debian works natively with ARM, so you can go ahead and install Xorg with touchpad driver etc. and get Debian working up to fullspeed. Believe me, it works a 1000x better than using AndroidVNC and tightvnc server. You can actually use mplayer with ffmpeg to play any type of vidoes off your sdcard at fullspeed.
So anyway, what do you guys think? Maybe theres a way to modify the bootloader so at boot time you can choose to boot into debian or android etc. or maybe it would be possible to lets say "boot debian" and vnc into androids fb to "make a phone call" etc., kind of a like a reverse vnc method we use to get into X on the debian side. Heck - we could maybe even figure out how to access the framework to make calls natively through debian. The possibilities are endless.

Also, I'll edit this post and try to get a guide going here in a couple days on how to get Debian ARM/Xorg working.

I was actually wondering myself if this could be done. Heck, not like I do not enjoy android or anything. It would be great to be able to run a lot of my *nix apps natively on my phone.
I already have Debian runnin off my 8GB sdcard(unfortunately a class 2) and I enjoy it. Problem is having to shut it down and restart it so much to get functionality out of my G1.
Keep me up to date on your progress and let me know the best GUI to use for better performance.

so whats the deal, anyone actually got this working? i have no use for my brothers g1 considering the low call quality/not recieving mms'es, i mean literally if i put them side by side, my excalibur has better service/reception. and id be pretty sweet to have crystal fvwm running on g1. so it doesnt really matter to me if i could get it to make calls, as theres always skype/amsn w.e. so pretty much anyone got any links on getting a native debian install?

dinscurge said:
so whats the deal, anyone actually got this working? i have no use for my brothers g1 considering the low call quality/not recieving mms'es, i mean literally if i put them side by side, my excalibur has better service/reception. and id be pretty sweet to have crystal fvwm running on g1. so it doesnt really matter to me if i could get it to make calls, as theres always skype/amsn w.e. so pretty much anyone got any links on getting a native debian install?
Click to expand...
Click to collapse
Yes they got this working. If you looked at the bible you would've seen this. But I will give you the link enjoy it is very cool. Youtube has some videos also.
http://www.saurik.com/id/10

Royalknight6190 said:
Yes they got this working. If you looked at the bible you would've seen this. But I will give you the link enjoy it is very cool. Youtube has some videos also.
http://www.saurik.com/id/10
Click to expand...
Click to collapse
no you misunderstand . i mean run debian native, as in to replace android

dinscurge said:
no you misunderstand . i mean run debian native, as in to replace android
Click to expand...
Click to collapse
Gotcha Sorry, um let me look around for yeah.

hey...check this out
http://www.youtube.com/watch?v=tX1BOGl8Fnw
and heres another xda thread here
http://forum.xda-developers.com/showthread.php?t=624392

USHERROB said:
hey...check this out
http://www.youtube.com/watch?v=tX1BOGl8Fnw
and heres another xda thread here
http://forum.xda-developers.com/showthread.php?t=624392
Click to expand...
Click to collapse
ahh thx for the link i saw this before but misplaced the bookmark. but im afraid thats not exactly what im looking for but that probably doesnt exist. as this is only set up to have dual boot booting android/debian of 3rd part on sdcard. and as far as i am seeing in the thread it isnt working to well. that im just going to have to wait and see what happens.

This is an old thread, but still a very interesting topic.
Would be *great* to but debian at the bottom of things.
A note about the bootloader: It is ***ALREADY DUALBOOT***. There are TWO boot partitions on the phone: "boot" and "recovery". If you want to set it up to dualboot, but your primary (automated) boot kernel into "boot", and your secondary in "recovery".
As long as you have an engineering SPL, the actual recovery is not required -- in fact, if you WANT to boot into recovery, you can always "fastboot boot recovery.img" without even having to flash the recovery to the phone.
I tell you the thing that really bugs me about android: that it doesn't support existing X.
What I dream of at night is running the ANDROID stuff ON TOP OF X. It would present a little bit of a challenge in terms of having the PHONE app (or whatever) be able to pop up to the top. There would also be some RESOURCE challenges. DREAM may not be the best hardware to implement this on.

Native Xorg
A slight off-topic because I have Samsung Galaxy
I was also fascinated by this possibility of running debian linux, Xorg on the phone.
So I created this project "linux-on-android" (sorry, I am not allowed to post links yet) on the google code where I am going to post instructions and code. Please, join the project if you are interested. It should be completely open.
The idea is to start with something simple but working and move slowly. In order to run X server from the Debian distribution it is enough to just use the Android kernel, with only a little change to the framebuffer driver. I don't change the boot procedure - only turn off the android services and put things like startx instead. Now I am trying to use matchbox+LXDE and they look nice and fast. Wifi and touchpad work. Nothing else does. I thought about what would be the minimal working configuration and decided that power management + telephony would be very good.
With the telephony I plan to leave the android RIL daemon and write a small python program that would communicate with it and act as a dialer. It appears to be not such a problem, at least I am able to communicate with the daemon now and all requests are nicely wrapped in python methods. The next step is to write phone GUI/dialer.
I think it would be already very nice to have Xorg and debian running on top of the android daemons and android kernel replacing this "zygote" stuff. Also if we do something in this way, it would probably work on any android-based phone without big changes.
About dual-boot: I am still using chroot, I don't find anything bad in it. I have two different boot.img files, they only differ by init.rc, one which starts zygote, and one which starts Xorg. In Android I press a button and reboot in debian, in debian I press a button and reboot in android.

klinck said:
A slight off-topic because I have Samsung Galaxy
I was also fascinated by this possibility of running debian linux, Xorg on the phone.
So I created this project "linux-on-android" (sorry, I am not allowed to post links yet) on the google code where I am going to post instructions and code.
Click to expand...
Click to collapse
I'll post it for you in the hope to get something good going here
http://code.google.com/p/linux-on-android/

Wow klinck you really seem to be making awesome progress here man. Just looking through your project page and i see it being updated every day. I just watched the video proof and i must say it's really quite impressive.
What needs to be done now is make a guide for this, so people can easily install this on their G1 and test it.
Also, this will give it more developer attention. I really think this deserves a chance
EDIT: added links for easyness

Jefmeister said:
EDIT: added links for easyness
Click to expand...
Click to collapse
To Jefmeister: thanks for posting the links and your interest.
About G1: As I said, I have Samsung Galaxy, so I don't have a chance to test it on G1. But still I can probably make a "binary distribution" for G1 and somebody else can test it. There are some hardware differences, to summarize, there are 3 things I need to change:
I need a kernel for G1 with ext3 support, and patched framebuffer driver which turns double buffering into single buffering and automatically updates screen at regular intervals
I need to know if tslib driver works with touchscreen from G1 and what is the corresponding device (it is /dev/input/event2 in my case)
I need to know where to put the debian distribution. In Galaxy we have a separate 1Gb ext3 partition on SD card which is normally used for '/data' directory, so there is a plenty of free space there. But I guess it may be different on G1.

klinck said:
To Jefmeister: thanks for posting the links and your interest.
About G1: As I said, I have Samsung Galaxy, so I don't have a chance to test it on G1. But still I can probably make a "binary distribution" for G1 and somebody else can test it. There are some hardware differences, to summarize, there are 3 things I need to change:
I need a kernel for G1 with ext3 support, and patched framebuffer driver which turns double buffering into single buffering and automatically updates screen at regular intervals
I need to know if tslib driver works with touchscreen from G1 and what is the corresponding device (it is /dev/input/event2 in my case)
I need to know where to put the debian distribution. In Galaxy we have a separate 1Gb ext3 partition on SD card which is normally used for '/data' directory, so there is a plenty of free space there. But I guess it may be different on G1.
Click to expand...
Click to collapse
(3): You could certainly put it all on the sdcard in exactly the same way. As long as you have the sdcard driver built into the kernel, the sdcard is just like any other storage device.

I dont know if this is going to be of any help to you, but as I was searching around for a way to nativly install linux on my dream I found this.
http://www.htc-linux.org/wiki/index.php?title=Dream
It may interesting as a point of refrence.
anyway, keep up the good work, once my conract expires this is exactly the kind of thing I would love to do with my old phone

Hi all !
I have actually an Debian NATIVE on my G1, both Debian/OpenMOKO/Android on the SAME phone.
android are into NAND FLASH, OpenMOKO (for tests and few binaries/config files) into SD2 Partition, and Debian with all tools to compilation, into SD3 Partition.
Actualy work on my Debian G1 :
USB NET
Xorg
Keyboard (but one touch not responding)
Touchscreen (but the calibration into Worg not work, into FBCONS it's OK)
Trackball (but the ball not "click")
I trying to make call, with OpenMoko I can ring my phone.
I trying also WiFi : Crash :'(
for bluetooth, I don't have the fu***** firmware ...
For ALL : You can boot debian with fastboot or recovery.
Debian CAN be into SD1/FAT32 parition, into loop file. I make an boot img, who can boot from SD1 part with loop image you don't must repartition SDCARD, or have dedicated SD card.

Auto-Starting Android without flashing

Perhaps this should be in the apps thread, but it's just intended for use with Android ROMs. I wanted an easy way to automatically boot to android without having to flash my Kaiser (ie: when Android needs rebooting ), so I wrote this small utility to automatically start HaRET.
This app will wait a predefined number of seconds before starting android, with buttons to both abort or start immediately.
I am giving this out to the community as XDA has done so much for me. It's not much but it's something I can do!
1. This project uses the .NET 2.0 Compact Framework and the source/binaries are available here:
http://rapidshare.com/files/338902988/AutoStart.zip.html
MD5: 0310EEC13DA72C4A533A4036AF1CDAA5
2. Copy autostart.txt to the root of your device (just "/")
Modify it to your liking (be sure to save as plain text)
3. Copy your default.txt to startup.txt (assuming it has the "boot" command) and move this file to the root of your device with autostart.txt.
BE SURE TO CHANGE FILE PATHS
Instead of:
Code:
set KERNEL zImage-15-12-09
set initrd initrd.gz
Change it to:
Code:
set KERNEL "/Storage Card/android/zImage-15-12-09"
set initrd "/Storage Card/android/initrd.gz"
4. Copy "AutoStart" (or AutoStart.lnk) to /Windows/Startup on your device. You may have to modify it if your HaRET is not in /Storage Card/android
To do this I used Notepad++. You could also create a shortcut using WinCE by selected AutoStart.exe -> copy -> paste shortcut.
This is an example of the contents of a .LNK (shortcut) for WinCE:
Code:
99#"\Storage Card\android\AutoStart.exe"
5. Copy AutoStart.exe to /Storage Card/android
Assuming HaRET/AutoStart/etc. resides on your SD card, if you have problems then just pull out the card and android will not start.
In summary, a working install could be:
Code:
/Windows/Startup/AutoStart.lnk
/autostart.txt
/startup.txt
/Storage Card/android/HaRET.exe (and all other android files)
/Storage Card/android/AutoStart.exe
Please let me know if it doesn't work for you! Be sure to validate all of your settings and paste them here if you need help
EDIT: PS if anyone wants to include this in their android/haret builds please feel free!
EDIT: Added a screenshot in a post below

OR.. You just just rename default.txt to startup.txt and copy a shortcut to HaReT to your startup folder.
Job done.

but it seemed like such a GREAT idea at the time!!! lol
Honestly I just want a delay so I can catch it but I guess you could just pull the SD card entirely and forget about that.
Hmmm... well gee I feel kinda stupid lol

aikeru said:
Hmmm... well gee I feel kinda stupid lol
Click to expand...
Click to collapse
Some stupid guy won't have made a topic like this with that amount of info.
Keep it up dude, maybe there's a good chef in you

aikeru said:
but it seemed like such a GREAT idea at the time!!! lol
Honestly I just want a delay so I can catch it but I guess you could just pull the SD card entirely and forget about that.
Hmmm... well gee I feel kinda stupid lol
Click to expand...
Click to collapse
Nah, don't feel stupid. You worked hard at your little program and provided loads of info on how to use it. That's a hell of a lot more than many people ever bother to do.
Maybe someone will even find a use for a program that lets you abort the Android boot without having to yoink the SD card out.

Great job, maybe you make a screen so the user can stop the autostart of haret? this help a lot, cause removing the SD card is not a great idea. chears

Thanks!! This is a very friendly community!
It does allow you to abort (there are two buttons, one that starts android immediately and one that aborts) provided the timer hasn't run out (it will wait a number of seconds before starting android as specified in the autostart.txt)
Well hopefully I will find other good ways to contribute.
I've attached a screenshot of what it looks like so you know what I mean

Why not use a Android background??? is much friendly. your work is very good keep up bro.

Beackman said:
Great job, maybe you make a screen so the user can stop the autostart of haret? this help a lot, cause removing the SD card is not a great idea. chears
Click to expand...
Click to collapse
Another easy way is to leave the default.txt as default.txt and not startup.txt; then place a shortcut to HaRET in your /windows/start up folder; this way it will alway boot HaRET run screen on startup and then you have to hit RUN to load android. And if you don't want to, then just exit. However it always requires you to press RUN

I konw man, i just want to help him to make the soft more friendly. he worked hard on this.