Develop Bugs

[KITCHEN][ROM] >-=+ [mu] kitchen +=-<

Placeholder for the [mu] kitchen.
DOs and DON'Ts:
DON'T:
1: DON'T ask about vista support. I'm seriously allergic to that expression. Use WinXP SP2/3 and be happy.
2: If it doesn't suit your needs, don't b**** about it and just use another one.
DOs: if you like it, say thanks.
CONSTRUCTIVE criticism/suggestions: more than welcome via PM.
^.^
### Here's the link (lzma)##############
# http://www.mediafire.com/?oufm4oq9t2v #
##############################
### Here's the link (tar+bzip2)#########
# http://www.mediafire.com/?u4tj1jsnuzt #
#############################
1: .net framework 2.0 at least needed.
2: ms vb runtimes recommended.
3: BEST uncompress with 7zip (or any app supporting lzma) / WinRAR/WinZIP to c:\
4; there is no "readme", so place your RUU_signed.nbh (and Part*.raw) into the "source" folder in the kitchen,.
5: although I tried coding it as noob-proof as possible, the kitchen DOES require some minimal knowledge about the cooking/rebuilding process.
I DON'T intend to spoon-feed you, so if you want additional features, you need to seriously catch up on some reading.
This kitchen DOES need further/extended testing, but I decided to release it after several successful tests on 2 different systems.
Nethertheless, I CAN'T possibly account for the heterogeny of every system in the wild...
I could TRY coding the "perfect" kitchen, but that would be utterly pointless, since experienced chefs use their own kitchen/or don't use frontends.
6: last but not least: even though a cooking process might've been completed, give a few seconds till you move to the next step. HDD/IO bottlenecks tend to do strange things.
^.^
The mirror/kitchen link MAY be inaccessible at times. If you REALLY need access to anything hosted, leave me a PM.
I'll provide you with another (temporary) link.
# # #
20090110 edit
Will be uploading an updated version of the kitchen maybe next week.
# # #

Pre-applaud and Pre-thanking
Thank you...................................

Thanks Cyphol.
I will of course give credit where credit is due.
What's taking me so long is that I'm trying to make the batch as easy to read as possible, all the while trying to give as much control as possible over the entire cooking process.
It should RATHER be "noob-proof".
I don't think I will finish it today, because I only have a windows box at work to test it on.
@ home I'm all unix.
^.^

adwinp said:
Thanks Cyphol.
I will of course give credit where credit is due.
What's taking me so long is that I'm trying to make the batch as easy to read as possible, all the while trying to give as much control as possible over the entire cooking process.
It should RATHER be "noob-proof".
I don't think I will finish it today, because I only have a windows box at work to test it on.
@ home I'm all unix.
^.^
Click to expand...
Click to collapse
(pre)Thanks for sharing a probably great and useful tool !

I think it will be a great kitchen because adwinp is a very hardworking man and he reads and searches a lot.

Thanks Cyphol.
I'm honoured. Though I learned a lot from you guys.
I'm nearly done with the batch file. I'll finish and test it tomorrow.
I tried giving the end user as much control as possible, even though using just one batch.
We'll see if it works.
DOS batch coding sux.
Bash rulez.
^.^

.. [reserved] .. for private use.

The [mu] ROM is coming next.
(It might take some time for me to release a ROM worth sharing with the community. I may want to wait for the next official ROM update since I'm not really satisfied with the 1.93 base).
PLEASE DON'T ask when it might be available.
^.^
Although I respect bepe's and dutty's (DP) great work, I stick with Wally regarding protecting the ROM against disasm/copying.
Meaning: No copying protections. Feel free to do with it as you please.

I won't say thanks for this kind of Kitchen. WHAT HAVE YOU DONE???
I only want to say MARVELOUS! NICE AND CLEAN! CONGRATULATIONS.

Thanks Cyphol!
The real thanks goes to the authors of the various tools this kitchen serves as a frontend to.
I doubt this is bug-free, but I hope it will be a contribution of some sort to the community I have learned so much from.
Maybe somebody will do a much better job than I did.

Sorry,
but WinRAR says the archive is destroyed.

scorpio16v said:
[...]WinRAR says the archive is destroyed.
Click to expand...
Click to collapse
Re-download and make sure your browser doesn't screw with the file extension, it's .tbz2 (tar+bzip2) otherwise your unpacker might have issues reading it.
The Archive is fine, and adwinp: the kitchen looks extremely sexy. I'm completely new to cooking and just trying it because I want a proper JVM, but I've looked at the other kitchens, and this one is the nicest so far.
If your ROM is as hot as the kitchen, I might have found myself a new base rom

cptsunshine said:
.... otherwise your unpacker might have issues reading it.
The Archive is fine...
Click to expand...
Click to collapse
You're right.
Was my WinRAR version.
Sorry for the rumour.

scorpio16v said:
You're right.
Was my WinRAR version.
Sorry for the rumour.
Click to expand...
Click to collapse
Use 7zip for any of the archive versions.
It's a fast and free archive manager, supporting lzma.
You can still uncompress the .tbz2 archive with 7zip/winrar/winzip.

Hi adwinp,
Great tool !
Thank you very much for sharing this tool !!!
I've tried it to rebuild a .nbh with some dump files associated with a RUU_signed.nbh from a stock HTC ROM.
After the first steps, all is OK (my casserole seems to smell good ) until the Build step...
I got an abort 'BuildOS.exe ....'
any idea ?

Could you post a screenshot?
Gimme a link to the stock ROM (or tell me what version it is) and I'll check it out.

OS conflict ?
Hi adwinp,
And thanks for your reply.
So, here is what I've done :
1. Copy my 4 Part0*.raw files in y=the \source folder
2. Copy the stock RUU_signed.nbh in the same folder
Notes :
> Dump files are the parts of a french ROM from Bouygues provider avalaible here : http://dl.free.fr/rkxdkK3bp
> RUU_signed.nbh file becomes from an official HTC ROM 1.37.406.1 avalaible here : http://www.4shared.com/file/5430812...io_Signed_Diamond_5226a2509_1002503_Ship.html
3. Launch mu.bat
4. select "a" to Accept
5. select "r" to Rebuilt
6. select "d" to leave it Dirty
7. select "z" to extract OS from base (OK, new folder 'casserole' with the OS.nb file)
8. select "g" to extract system files (OK, new folder 'imgfs_e' in the casserole)
9. select "y" to extract core files (OK, new folder 'xip_e' in the casserole)
10. select "p" to concatenate system (it seems good)
11. select "o" to rebuild the base...
And then, the error message :
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
After that, I've tried to use the other method with Diamond Kitchen, and I got exactly the same error when building the OS...
plus another message :
Even if I don't really know how the BuildOS step proceeded, it seems there is an OS incompatibility or conflict, right ?

I'll try to rebuild your ROM later.
A quick question though: do you have NET Framework >= 2.0 installed?

adwinp said:
I'll try to rebuild your ROM later.
A quick question though: do you have NET Framework >= 2.0 installed?
Click to expand...
Click to collapse
A quick answer though: .NET framework 3.5
Cheer,

Hello,
@ MonteCristoffOn, you've installed Microsoft Visual C + + 2008 Redistributable Package Download

[ROM][26.07.10] >> [email protected]_2.2.0_5_os << [AOSP/NO SenseUI] [codename: Be My Hero]

[ROM][26.07.10] >> [email protected]_2.2.0_5_os << [AOSP/NO SenseUI] [codename: Be My Hero]
As mentioned in my sig., I don't mind appreciation.
Just mention your xda handle while filling in the donation form. Thanks to everybody who contributed.​
Specific/Unique Features:
- Available localisations: English, Polish, Russian and Japanese.
DON'T ask about support for other languages; should need be, download any of the locale utils on the market
- JIT, A2DP, OpenGL
- The Tasty Bits:
I've been wondering about a few aspects of the android build system, and what I have found confirmed my suspicions;
In order to minimize build-system fragmentation, and what goes with it, maintenance, most of the code is built for compatibility instead of performance.
That is why I have tried what has, to my knowledge, never been done before on Hero-like devices (dream, sapphire, eris and the rest).
Some code breakage happened along the way, but that was to be expected.
Nethertheless, the new [email protected] is built with that specific spirit in mind. Be aware, that this is HIGHLY experimental, but the latest user tests confirmed that everything's good.
GIve it a spin and leave some feedback, if you find anything out (really) of the ordinary.
This is a peel-the-skin-feel-the-bones naked version of the regular [email protected] ROM (which is mainly geared for my personal use). Bug submissions and/or constructive criticism is appreciated, but DON'T bug me about missing features.
Custom kernel.
performance tweaks
native loopback support (along with crypto)
network fixes (wlan, bridging, *tables, tunneling, etc)
utf8 (have to rebuild system apps though...)
ext2, ext4 (be aware that journalling is overkill for a 528MHz CPU)
alsa
Power savings
and others...
Is it stable? It is enough for me.
Play, test, and help out.
Issues/Bugs/Fixes:
- Force Closes
FIX:
>>> You'll have to pull the files with adb and repush them (push the odex FIRST, THEN the apk)
- Camera isn't working atm.
- Your Hero is stuck at the bootscreen, bootloops, random crashes:
FIXES:
>>>Make sure you have AT LEAST Radio version 6.35.09.26 (recommended: > 6.35.15.01 <) Click to download
>>> You might be the unlucky owner of a Hero unable to handle exotic freqs like 19 MHz/748 MHz. If such is the case, go back to recovery and flash > THIS < kernel.
RTFM:
- The ROM isn't signed most of the time. You can get by this issue by
1: installing the excellent > Clockwork Recovery <
How to install: # adb push recovery-clockwork-2.5.0.1-hero.img /cache/rec.img
# adb shell flash_image recovery /cache/rec.img
or
2: use the Engineering SPL
or
3: sign it yourself (google for autosign - you need to have android SDK installed)
- It WILL take quite a while to initialize after flashing (a few minutes).
- You MUST restart after the first boot (sys. init.), otherwise the system will work at a crawling pace, since all apps are running, due to being initialized at first boot. The cruising performance will be reached after you setup your system and restart.
You might experience problems signing in, in case you don't restart (or you can disable and re-enable mobile network).
>> AOSP Hybrid N4k3d [2.1] (current) <<
>> [email protected] semi-naked [2.2] (current) <<
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Benchmarking (Linpack:Neocore):
​

Will try out tomorrow, nice to have another Dev here. Welcome!

Great to see u in this forum sir.... android is just so much better than winmo
Thanks for the ROM

Welcome to the Android world!
Great to see (another) big name from the WinMo section in here .
Will be trying out your stuff for sure!
Quick question (no, didn't try your ROM yet, still playing around to get MCR 2.9 working ok):
You removed all but en_US you say. Also the dictionaries for the HTC_IME? I want everything on my phone in english, except the messages that I type , so it would be a shame if those dictionaries were gone.
If they _are_ gone, can you explain me which files so I can try putting them back myself from a stock ROM / MCR ROM?
(Another one actually: Did you find it hard to dive into building ROMs and customizing for Android?
With years of Linux experience I thought it was the first thing I would be doing with my 1st Android device... but it seems I played around with WinMo builds, packages, NK.exe's, ROM/SYS's for so long I'm stuck in my ways . Didn't touch anything from the SDK yet except adb.exe and fastboot.exe to flash.).

@dipje:
1: Dictionaries are untouched.
2: Customizing is a much more pleasant experience than with WinMo.
As a matter of fact, I just got my Hero device, and need to build up an Android modding knowledge (Android-specific).
Linux-specific knowledge is not a problem, since I'm an admin.
I'll be taking care of different aspects of the ROM in the long run, rebuilding and optimizing bit by bit:
base apps, kernel (I find it pointless, most of the ROMs use quite a few init scripts - even in the initrd, instead of consolidating...)
I have an idea about installing debian (arm) on android, chrooting into that, and building the android system from there.
No need to setup cross-compile toolchains on our x86 PCs (try that if you've run into problems setting a toolchain on a host PC).
^.^
Though we'll be limited to 528Mhz and ram... But hey, if you've got a big sdcard, just setup a big swap on it.
;]
Apart from that, we can have a nearly full blown linux distro running at all times on the Hero (which would negatively impact battery life, but hey, it's just for the fun)
An ad-hoc wifi would be setup at all times, + sshd (along with vnc?)
So we can always X-forward our display or whatver.
The ideas an possibilities are endless.

Hi,
will definitely try your ROM. Glad to have you here! Good Luck!
//dzieki i powodzenia
//edit
OMG this Rom is super fast. Everyting works great so far. Well done. BTW. Firmware 2.0 ??

cant we get an update.zip file for this... this adb thing is a bit difficult process....thankx for the rom anyways..

Nice another dev creating roms.
Btw, isn't advanced task manager a paid app?

Thanks a lot.
and plz continue dev

naTTan said:
Nice another dev creating roms.
Btw, isn't advanced task manager a paid app?
Click to expand...
Click to collapse
I've searched for it, and looks like it is.
Looks like the repo I was using included some warez.
Will be removed and I'll add another task manager.
Thanks for the info.
norao said:
Thanks a lot.
and plz continue dev
Click to expand...
Click to collapse
Continue?
I'm just getting started.
;]

adwinp said:
Continue?
I'm just getting started.
;]
Click to expand...
Click to collapse
Hey adwin,
ki position? glad to see you on the hero cooking path.hehehe. good job chef. will flash as soon as i get home.
cheers/
deeren

ADWINP: cool going bro. its realy nice and hopeful to see cookers joining hero cooking. keep it up bro. cheers.

adwinp said:
It WILL take a while to initialize after flashing, since I've yet to learn how to obtain .odex from apks.
Click to expand...
Click to collapse
Sorry, missed that message!
To get odex from APKs, you use dexopt-wrapper.
To put odex back into APKs, you use the smali project - http://code.google.com/p/smali/.
P

modaco said:
Sorry, missed that message!
To get odex from APKs, you use dexopt-wrapper.
To put odex back into APKs, you use the smali project - http://code.google.com/p/smali/.
P
Click to expand...
Click to collapse
Hey Paul.
I was a bit surprised at the lack of feedback, but thanks.
;]

Updates:
1: added a few screenshots of the new wip build (not yet uploaded)
2: replaced Advanced Task Manager by the quite good tasKiller
3: recompiled kernel; a few kinks to iron out, like adding the wlan module and splash, but other than that, it's fast.
Added support for a few more fs (like ext4)
Here's what you get:
sysfs
rootfs
bdev
proc
debugfs
sockfs
pipefs
anon_inodefs
oprofilefs
tmpfs
inotifyfs
configfs
devpts
ext3
ext4dev
ext2
cramfs
ramfs
msdos
vfat
iso9660
nfs
nfs4
cifs
udf
yaffs
yaffs2
rpc_pipefs
Added a few network features like net bridging, proper unicode support (though it has to be configured in the os itself; didn't check if the system libraries have utf support)
raid also was added (in case someone wants to play with ROL/RON - Raid Over Lan)
The new kernel will be available with a new [email protected] build.

Yees, glad to see another great rom cooker for HTC HERO community. Really a good news.
Good luck

silly question
Why does the firmware version say 2.0

Please, upload somewhere else.

Thanks adwinp,
Downloading now. I will run it for a while and feedback to you my comments.

So far everything looks to be working well after upgrading from MDC 2.9 without a wipe.
Not sure I like the transparent lock screen. I tend to use the default HTC scene with with the 4 icons along the bottom of the screen. When locked, the text on the icons can be seen and makes things looked a little confused.

[26-10-2010][Neopeek's Android Ports][CyanogenMod]

EDIT 26-10-2010: CyanogenMod 6.0 Final and CyanogenMod 5.0.8 Final available now!!
The following CyanogenMod-Ports are available now (stable is marked as FINAL):
VaniljEclair CM5 (Eclair / FINAL V1.3 updated on 26-10-2010 )
"Official" CM6 (Froyo / FINAL V1.0 updated on 25-10-2010])
FroyoRedux CM6
SuperF-Port
many more...
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Quick-Installation-Guide:
Read this installation instructions by chase21
Thanks go to:
Balsat, XDANDROID-TEAM, Cyanogen + Team and everyone else whom I forgot.
Used kernel + modules: htc-msm-linux by glemson and balsat
Used rootfs: XDAndroid modified to run on EXT2-Partition
Mixed-Up and ported by: Neopeek
Source: CyanogenMod 6, CyanogenMod 5
Download latest release

Added some screenshots and video for the upcoming build. 249views here and no reply here. Not bad! Nevertheless I have enabled JIT Dalvik VM and get a Linpack Benchmark of 4.04MFLOPS. Again this should work also on your devices but til now I have no feedback of anyone if the first release did work on your Blackstones. Anyone wanna try (tutorials provided when you follow main thread on XDA-Developers' HTC Diamond-section).
I only have A HTC Diamond. As described in first post you must update startup.txt with correct values for
- ramaddr
- mtype
- lcd density
If anyone gets it to work in first release than contact me and share your startup.txt with me. Otherwise I will package one into the new build for my own although I have no Blackstone. So help by anyone would be good in this stadium.

Main-thread updated with download link for new build [08.06.2010]. I have also included startups for HTC Blackstone (see main thread or my signature)

i've tried it yesterday(the 04 build!), by creating 2 partitions on my 2gb sd card, the ext one have 1,5gb and the fat32 0,5gb.
I've also modified the startup text file to be like this :
set ramsize 0x10000000
set ramaddr 0x10000000
set mtype 2030
set cmdline "root=/dev/mmcblk0p2 init=/init rootwait rw rootdelay=10 console=tty0 rootdelay=10 fbcon=rotate:1 lcd.density=210 msmts_calib=0x395.0x3c9.0x79.0x77 clock-7x00.a11=500 msmvkeyb_toggle=off pmem.extra=1 gsensor_axis=2,-1,3 acpuclock.oc_freq_khz=650000 htcblackstone-panel.no_bkl_off=1"
boot
Click to expand...
Click to collapse
after starting Haret, it loads up and execute all the scripts but it get stuck on the black screen and android don't show up.
I will try today release and i'll post a feedback!

Ok thank you for trying out.

k-zik said:
i've tried it yesterday(the 04 build!), by creating 2 partitions on my 2gb sd card, the ext one have 1,5gb and the fat32 0,5gb.
I've also modified the startup text file to be like this :
after starting Haret, it loads up and execute all the scripts but it get stuck on the black screen and android don't show up.
I will try today release and i'll post a feedback!
Click to expand...
Click to collapse
k.zik don't get higher than 512MB for ext2:
You could do it the following (assuming 2GB sd card):
1.3G FAT32
300M EXT2
300M EXT2
Also it is very important to unmount your device / sd-card before starting android up

Downloading for my Blackstone.
When i try it, i post here...

thank you for trying this out insestito!

it doesn't boot up!
I've tried it several times with the kernels avaible with haret but nothing shows up!
waiting for insestito to see if it works with him.

Can you put here a mini tutorial ???
i need linux in my computer ???
Thanks !

Notice: Sorry guys I don't have a Blackstone but I am using XDAndroid rootfs + kernels. So this should work for you. But I can't test it on my own.
So this is the way to go:
Install Linux (or use LiveCD GParted) to create the ext2 partitions (a Neopeek-User called fu-raz will publish an according tutorial for GParted LIveCD in the evening, he promised me -> otherwise you will have to follow the main thread on diamond section -> see my signature -> SuperEclair)
When you have created succesfully the partitions on your sd card you will have to extract contents of Haret-PaketV1.2.zip to your first partition (Fat32) and put the startup.txt for your device into the root of the fat32-partition
Then you will need to extract superclair02b.zip to your second partition (ext2). For this you will have to use LINUX, It won't work in Windows
After that, please unmount your device and / or sdcard and wait for complete unmount before you start android
Simply just follow the steps which I describe in main-thread and my website and reproduce all steps (+just use sdcard). I Think k-zik is on the right way. It could be just a wrong thing in startup. So you will have to try it out. Even some Diamond users got it working after trying several times. If you think the startup is ok and you don't get any errors regarding partitioning. Then maybe you should give an older zImage + kernel from XDAndroid autobuild service a go as I use the latest. Hope this helps.

where I put the contents of supereclair02b ..... ??
The content of haret-packet i put in partition fat32 ????

you will have to put the content of supereclair02b on the ext2 partition, and all the content of the haret-paket on the fat32 partition with the startup.txt!

kernel panic - not syncing: No init found.
Rebooting in 7 seconds...

@Insestito: You are on the wrong way.
Maybe I should make a video on how to do this?

vatoloco said:
@Insestito: You are on the wrong way.
Maybe I should make a video on how to do this?
Click to expand...
Click to collapse
Yes please....

Will need some time for an explaining vid, though you could also try to follow links in main thread. A lot of people got it running after trying it several times.

I followed all the instructions correctly.
but when I open haret.exe loaded and is on the line KERNEL PANIC ....

Ok thanx indeed for trying to get this running. I think I will have to get a blackstone to get it work. If anyone else want to give it a try then go for it.

i still interested in the project and i'm trying to get it to work, by using different kernels but it always stucks on the black screen and android don't show up!
i dont know where is the problem?!? is there any command that can i add to the startup to get the log file of the booting or someting?!?

Android x86 working build. [no sound compiled, and bugs, wifi and fun working )

I just found http://www.androidx86.org/ and took the time to break the dsk and the iso images to build a boot.ini via grub sitting in a directory on the disk version.
Really all you need to do is winimage the dsk from the tar.gz and then grab all the files and setup grubldr in boot.init
Anyhow It booted! On my two laptops I generally get wireless (not stable), and no sound, and vesa, maybe nvidafb on m200. The ibm t60 shows hda_intel on lsmod but files seems to be missing. The m200 didn't mention sound in the console output. The graphics didn't work on the high end (black out), but vesa did. Standby doesn't seem right but thats likely google standby behavior on a unit in gimp mode. I took some video of it running on my laptops need to upload it somewhere. I will join the x86 forum here in a moment. Just wanted to share the build here. Wish it had audio.
I don't think the android build is as advanced as what is here on the phones so development wise I'm curious if I can swap the system files from the phone to the latop but homework calls. I'm uploading the build now it says 200 minutes on my very slow connection.
Can I just say download mssmissions system.img and run the system.img or will binary-arm stuff throw me thus I need to pretend I am a gentoo user and compile stuff or is it all python and java and intependent in the system.img?
Can I merge an ubuntu and android?
Any pointers as far as setting up a dev enviroment within android? You can also run android.iso vrom virtualbox and I'm pretty sure you can tweak it to get sound but I got none if anyone is interested in that. If anyone can give me any kernel advice vs compiling known linux drivers that be nice. Can i confidently think it'll work cause I have generic linux sources. Any sage advice for ati x1300 driver or a nvidia g5500 mobile card? Also my waacom didn't work on my tablet . I just wanted to post the build someone mirror it?
When its done uploading I will edit this.. Don't want the message to time out..
I was very impressed by the browsing speed of droid on the machines...
I just sent a pm to a mod who will move this thread.

dam thats actually pretty legit lol

Drool.
Thanks I thought so too! I just found http://blog.android-x86.org/2010/01/eclair-test-build-20100115.html and my. I need to study :| android crack is bad. But eclair is out so I need to give that a shot. I just did donut. Someone who is going to go crazy please go do eclair now. please compile hoards of video and sound drivers and just upload
Download Donut prebuild. Edit boot.ini and reboot
http://rapidshare.com/files/401173367/android-system.rar.html
OR!!!!!
Download this to build your own.
http://grub4dos.sourceforge.net/
http://www.winimage.com/download.htm
http://iweb.dl.sourceforge.net/project/grub4dos/WINGRUB/WINGRUB 0.02 Build 6/WINGRB0206.EXE
http://www.androidx86.org/downloads.html
http://blog.android-x86.org/2010/01/eclair-test-build-20100115.html
(I don't think you'll need the iso, get the usb disk, but the iso is cool cause it boots in virtual box. I'm having sound issue but it looks like it is loaded. )
extract android-system from android.img from gz and put into c:\android-system
download wingrub. Run it tell it to copy stage files.
C:\grub is created
edit the attached menu.lst or use the one from the android.dsk.. Copy the splash screen.xpm.gz from the dsk root to android-system, or wherever and reference it appropriately in menu.lst.
my boot.ini
[boot loader]
timeout=30
default=multi(0)disk(0)rdisk(0)partition(1)\WINDOWS
[operating systems]
multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="Microsoft Windows XP Professional"
C:\wubildr.mbr = "Ubuntu"
C:\grldr="Start GRUB4DOS"
C:\CMDCONS\BOOTSECT.DAT="Microsoft Windows Recovery Console" /cmdcons
notice the grldr, Recovery Console, or Ubuntu is not necessary. After you install wingrub you can copy grldr to the root of the c:\ drive. Grldr is in:
C:\Program Files\WinGrub\GRUB
there is a file called grldr_p12 rename it to grldr and put at C:\grldr
my menu.lst in c:\grub
root (hd0,0)
splashimage=/android-system/android-x86.xpm.gz
timeout=600
title Live USB - VESA Mode
root (hd0,0)
kernel /android-system/kernel root=/dev/ram0 androidboot_hardware=eeepc acpi_sleep=s3_bios,s3_mode quiet vga=788 SRC=/android-system
initrd /android-system/initrd.img
title Live USB - Debug Mode
root (hd0,0)
kernel /android-system/kernel root=/dev/ram0 androidboot_hardware=eeepc acpi_sleep=s3_bios,s3_mode vga=788 SRC=/android-system DEBUG=1
initrd /android-system/initrd.img
title Live USB - Run Android-x86 without Installation
root (hd0,0)
kernel /android-system/kernel root=/dev/ram0 androidboot_hardware=eeepc acpi_sleep=s3_bios,s3_mode quiet SRC=/android-system
initrd /android-system/initrd.img
title Installation - Install Android-x86 1.6-r2 to harddisk
root (hd0,0)
kernel /android-system/kernel root=/dev/ram0 androidboot_hardware=eeepc acpi_sleep=s3_bios,s3_mode SRC=/android-system INSTALL=1 DEBUG=
initrd /android-system/initrd.img
title Windows at (hd0,0)
root (hd0,0)
chainloader +1
As far as differences in the directions to build your own or to just download the donut prebuild, I made the build I put grub in C:\boot\grub this is not the default. Wingrub installs the stage files to C:\grub by default so in the directions I went that route. I know it works either way cause I just redid that portion following my directions and it gave me stable mute android with wifi for about 30-50 minutes. Thats the only thing different between the build and the directions, and I believe if you move C:\grub to c:\boot\grub it would still work as they are booth search path for grldr.. Anyhow..
Or go download the cdrom iso's and burn it to cdrom/usb

hehehe
I've now entered all my bugs at:
http://code.google.com/p/android-x86/issues/list
here are some screenshots..
http://code.google.com/p/android-x86/wiki/ScreenShots
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Looks promising if motivated:
http://code.google.com/p/android-x86/wiki/CustomizeKernel
eclair install not going so well initrd.gz referenced but not included on usb image. downloading iso which is good to have anyways for virtual boot in virtualbox. I hope initrd.gz and kernel are in there, but sadly they are older too. So donut maybe better after all. I'm waiting to test eclair. The donut kernel addresses system.sfs the eclair references system.img perhaps i should convert the format : I would try to do a rename but I am downloading the iso.

What does it have common with kaiser on android???

It it relates. It's like sql.
Select Interest from community where Tangent=Related
Okay man its a stretch. I just got excited at the prospect of running android on my other hardware. I should migrate my tangent babbling soon. I shouldn't even be working on this at all. I.E. what does this have to do with physics ii?
Duh.
But, when I saw it I thought ok great I boot android I'll be better able to work on android builds here maybe help out with the phantom haret issue all you l33t experts ignore. I.e. the last post about me not being up to date on stuff is crap. Seriously goto the n00b thread and fix my haret issue with instructions as clear as these..
Also kernel compiling is kernel compiling. I should go to the pure android forum and will move there I guess. But playing with this makes it much easier to work with kaiser droid. From what I've been reading it also makes me wonder about kubuntu and droid as booting android from ubuntu on os86 was mentioned and the kernel compile process seemed straight forward, so it may work? Making it work on my system I could then download all the dev stuff and maybe spew out a cross compile; but then again I'm not some sort of gcc guru. I'm just trying to get to know it is all? Why you downing me brah?
Also this build looks way less advanced maybe I can get some kind of merge on the sources here for the benefit of my 86x. It's funny how sound is an issue on 86x as much as it is here and even that says hey maybe in the 86x world with a keyboard and mouse could soomething so generic be fixed on 86x that it fixes a kaiser issue? But I agree were now in tangent territory. Need to find a better home and give it a link in a more suitable audience/ stronger relationship area.. I mean the affinity isn't that much higher.
I just got done building the last boot.ini grub environment. I'll leave it on that note and find a better place to continue this and link this to that and start over if i continue this work/effort. I just like people in this forum so I wanted them to benefit from my download. But I only was so stoked because I forget how easy it is to download an iso and boot from it when I have to do something else cause my m200 doesn't have a cdrom. Anywho..
-----
http://rapidshare.com/files/401231657/AndroidX86_2.0_and_1.6.basefiles.rar.html
move everything in the archive to the root of C:\
Download (From: http://code.google.com/p/android-x86/downloads/list)
AndroidX86-1.6: donut
http://code.google.com/p/android-x86/downloads/detail?name=android-x86-1.6-r2.iso&can=2&q=
AndroidX86-2.0: eclair
http://code.google.com/p/android-x86/downloads/detail?name=android-x86-eeepc-2.0.iso&can=2&q=
Open the each iso (WinImage, Winrar, MagicIso, or other iso program) then extract system.sfs and place it in its respective directory under grub
(i.e:
android-x86-1.6-r2.iso extract system.sfs from iso and put in C:\Grub\android-donut
android-x86-eeepc-2.0.iso extract system.sfs from iso and put in C:\Grub\android-eclair )
Edit boot.ini to include:
C:\grldr="Start GRUB4DOS"
Happy booting!
Alternatively:
You can of course boot the iso's using virtualbox
Go here: http://code.google.com/p/android-x86/wiki/Releasenotefor20091024dailybuild
for any more info or to report a bug about it.. I'll bet I don't work on this for a while..
-----

I find this interesting, and somewhat relevant, at any rate it looks fun to play with
I may have to experiment with this myself, lol, wonder if it'll work on my spare laptop? ........
Good find Tyler

also a neat find..
http://forum.xda-developers.com/showthread.php?t=553366
Looks like emulation is horrible. Thats sad its a linux kernel and it has a host someone needs to paravirtualize android? I'm reading the android thread it seems like alsa sound should just work so I'm being a ninnny nanny by not compiling stuff into the g.d. kernel, yet bug reports are abundant for lack of certain functions on different devices. grr.
This thread maybe moving soon to:
xda-developers > Android Development and Hacking > Android Software Development ?
bummer the emulator doesn't work well.. I wonder if the x86 kernel does virtualized arm support, someone need to do that...
man this is a distracting bummer. I have to compile a kernel.. I just installed a grub ubuntu too , I need to see if I can just start android in that no matter what, I may get lucky.. maybe even luckier if someone will hook it up in the other thread ..

tyler51773 said:
But eclair is out so I need to give that a shot. I just did donut. Someone who is going to go crazy please go do eclair now. please compile hoards of video and sound drivers and just upload
Click to expand...
Click to collapse
I made a working android-x86 alpha eclair 2.1 build with gapps. Designed for aspire one but also should work on vmware and vbox. Will boot and work (somewhat) on most computers (built with generic kernel config so all available .ko drivers are there) however you may have to modprobe the drivers for ethernet and wlan for your hardware. http://www.aspireoneuser.com/forum/viewtopic.php?f=90&t=19299&p=116492&hilit=aoa110#p116492
Make a bootable usb with unetbootin from the .iso is the best way to use it and you can install to hdd too from it.

Password?
just wanted to give the above aspireone-x86 build a try but the rar is password protected?

[ROM][2 NOV] Virtuous Codename: Trentacinque Beta 2

Virtuous Codename: Trentacinque Beta
Maybe some of you already saw on Virtuousrom Website that I was able to leak some screenshots of the new Virtuous ROM. But now I was able to leak a complete build from them *lol*
But now to the "real" stuff:
The rom itself is based on the Runnymede RUU 1.05.401.4. After some days with trying to make this build really stable we still need to say this rom is still in a early build state. So be aware that there will be some problems left. Also there aren't any tweaks at the moment in the rom. We first want to make it stable and then begin to add some nice features.
As you maybe already saw we have no name for the rom at the moment. Therefore we started a thread in our own forum where we got a lot of suggestions for it. We will now try to pick up the best five suggestions and then start a poll here on XDA.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Changelog for Virtuous Trentacinque Beta 2
New Features
Update base to Runnymede 1.05.401.4
Update kernel to newer V10 build
Calculator with switchable different themes
Thanks to nunggg for his version
If you have already made or want to make a mod for the calculator than we will be happy to add it too if you want.
IME keyboard with switchable arrow keys
You can choose if you want to show or hide the arrow keys
Advanced Power Menu (APM)
Overglow effect
Bug Fixes
All devices are now more stable
Less output in logcat from rmt_storage
Download
MultiUpload
MD5: a123dc66ef17ce3e789108b9eec85550
G2 Users you will need the DZ hboot before you can flash this ROM, Instructions on switching can be found here.

[GUIDE] How to set up a SD swap partition
This guide will walk through how to set up a SD card swap. SD card swap allows your SD card to become a place where your physical memory can become virtual memory thus helping free up more physical memory . This is most likely needed in 512 mb devices running Virtuous Unity. This guide has in mind that you have knowledge of ADB. If not you may follow the alternate way, but I have not personally tried that way. If you would like to know more about ADB and how to set it up please go to ]this guide by theunlockr.com: http://theunlockr.com/2009/10/06/how-to-set-up-adb-usb-drivers-for-android-devices/.
*Please back up everything on your SD card before going forward, I’m not responsible if you do not follow this step and loose everything on your SD card or if your phone is killed in anyway.
* Please Upgrade to Clockworkmod to 3.0.2.6 or newer before making the partition
1) Please boot into Clockworkmod Recovery (CWM, CWM Recovery). Once there go to Advanced-->Partition SD card-->Ext and Swap partition sizes. You will want to pick 128 mb for ext and 256 mb for swap partition.
2) Reboot into your ROM and place this http://dl.dropbox.com/u/32936737/swap_enabler.sh script into the root (not with in any folder) of your SD card.
Once there you can go two directions. Direction A is through ADB, Direction B is through the terminal emulator.
3a) Type these commands in the command prompt:
Code:
adb shell
chmod 755 /mnt/sdcard/swap_enabler.sh
sh /mnt/sdcard/swap_enabler.sh
3b) Type these commands in the terminal emulator (You can find this on the market)
Code:
su
chmod 755 /mnt/sdcard/swap_enabler.sh
sh /mnt/sdcard/swap_enabler.sh
Please reboot your phone after the script is done
4) Verifying that it works. Please choose 4a if you used ADB and 4b if you chose terminal emulator.
4a) If you’re using ADB type these lines in the command prompt
Code:
adb shell
free
4b) If you’re using terminal emulator type these lines in the emulator:
Code:
su
free
If you did not get a bunch of 0s that means it is working, Congratulations.
__________________________________________________________________________________
The following code will not update partition tables on sd card, it will just switch off the swap in the system
If you want to do this enter these lines in the command prompt (If using ADB)
Code:
adb shell (skip if you're already in adb shell)
sh /mnt/sdcard/swap_enabler.sh disable
If you want to undo using the terminal emulator do
su
sh /mnt/sdcard/swap_enabler.sh disable
Code:
Credits: Give a giant thanks to nv- for writing the swap_enabler script and original walk through,
Pato for the CWM tip
Cimer for the original tutorial [URL="http://forums.virtuousrom.com/index.php/topic,58.0.html"]http://forums.virtuousrom.com/index.php/topic,58.0.html[/URL]

Reserved

YES
Sent from my Desire Z running @ 2GHZ

COOL!!!!!!!!

Gonna try this. Awesome!
Sent from my HTC Vision using xda premium

Looks interesting.
Gonna keep an eye on this.

ah! Good Friday it is!

cjward23 said:
Reserved for future use
Click to expand...
Click to collapse
its been quite some time since i last used sense rom and especially unity series roms.... i wanna know if the sms lost issue was tackled or not ? are we still dependent on gostly sms ? be it on unity or on this sense 3.5 new beta rom... thanks

hispeedworm said:
its been quite some time since i last used sense rom and especially unity series roms.... i wanna know if the sms lost issue was tackled or not ? are we still dependent on gostly sms ? be it on unity or on this sense 3.5 new beta rom... thanks
Click to expand...
Click to collapse
I never get many sms on my vison, in fact i never get any. So i have been unable to test this.
There really is not much that we can do about the missing sms issue.
How ever i'm finding that with swap enabled sense 3.5 seems to be a lot more usable than 3. So maybe it will be less of an issue. Currently ghostly is not included but can be found in the market if required.
Also there is no graphical corruption on non htc widgets when using swap.
I look forward to hearing your feedback.
Sent from my HTC Vision using Tapatalk

It made me happy. Thx.

Finally !!! me happy too...hope this as good (or better..i m sure it is) that VU 2.39...awesome work guys !!

so, any comments on this one?
@OP Will the further updates require full wipe ?

Bug tracker is live, http://bugs.unity.flemmard.net/projects/virtuous-35
please provide as much info as you can including screen shots, logcats and what device you are using
Sent from my HTC Vision using Tapatalk

Been testing for a couple of hours now, and here's my findings:
1. Had hot reboot in setup screen (entering twitter account details)
2. Cursor randomly left text boxes during setup (no issue after)
3. Trackpad wake is missing
4. In OC/UV Beater, lowest OC available is 245mhz (is 122mhz in Unity)
5. as above, lowest UV is 800mv (was 700 or 750 in Unity?)
Good points vs Unity:
1. Swap doesn't corrupt widgets, seems to work perfectly (saw 140mb free ram)
Everything else i've tried works well, smoothly, and responsive. It's a DD for me, and a lot better than some other roms out there!
Nice job!

fr3akBut said:
Been testing for a couple of hours now, and here's my findings:
1. Had hot reboot in setup screen (entering twitter account details)
2. Cursor randomly left text boxes during setup (no issue after)
3. Trackpad wake is missing
4. In OC/UV Beater, lowest OC available is 245mhz (is 122mhz in Unity)
5. as above, lowest UV is 800mv (was 700 or 750 in Unity?)
Good points vs Unity:
1. Swap doesn't corrupt widgets, seems to work perfectly (saw 140mb free ram)
Everything else i've tried works well, smoothly, and responsive. It's a DD for me, and a lot better than some other roms out there!
Nice job!
Click to expand...
Click to collapse
Thank you for the feedback.
One of the issues we had with the last release of Unity was that people were experencing random reboots caused by the default UV, being able to go as low as we allowed was not good for the majority of devices. So the lowest options that were available have been raised.
Trackpad wake is a feature that we will add soon.
There are a few issues with text input, that we know about inculding the issue you have.
And hopefully the reboot wont happena again.
Sent from my HTC Vision using Tapatalk

hmm this looks interesting gonna try it out and report any errors back... last 3.5 rom i used when i was in a call made my phone burning hot... hopfully that doesn't happen here.

cjward23 said:
Thank you for the feedback.
One of the issues we had with the last release of Unity was that people were experencing random reboots caused by the default UV, being able to go as low as we allowed was not good for the majority of devices. So the lowest options that were available have been raised.
Click to expand...
Click to collapse
Ah, i see. Could i suggest that the lower OC/UV settings be made available as a separate patch for people with devices that can handle it? (with a big warning saying that installing this patch isn't recommended etc)
Then most people would be stable, and the lucky few can have silly underclocks for better battery life at idle.
Thanks again

So far it works well! Good job guys!
Sent from my HTC Vision using XDA App

awesome, cant wait to try this when i get home, by the way how much RAM are you guys getting after flashing this?