We decided to start a survey for OsBilder users. The question of it is the following:
What new options/settings/possibilities do you want to have in future releases of the program?
Please leave the detailed description of these options, as well as specify the reason why they so are necessary or desirable for you.
Your ideas and recommendations could be useful for further development of the program.
Do not post requests to implement complete support for building ROMS for some definite device name or brand - Barin cannot buy all the brands available at the market to carry out tests with them.
If you stubbornly want this support – you are free to buy and send a desired device to Barin for testing.
Requests to add one or another program option without giving a reason to do it – won’t be under consideration.
Requests to translate program interface into any language other than English and Russian won’t be answered here. We can only talk about the options related directly to functionality of DumpTool and OSBuilder features.
Concerning bug reports for currently implemented features – they should be also posted in the main OsBuilder thread.
Note about the Rom-Protection feature of OsBuilder for WP7.
The OsBuilder developers and the other members of asusmobile team get a lot of PMs from xda rom-cooking guys with the requests to implement kinda “rom protection” feature for WP7 roms.
Guys and gals!
For the moment only one developer has a real reason to protect his own work. It’s DFT, because DFT makes real development. With unique programs and features included. With new cool possibilities enabled.
But DFT is able to PERFECTLY protect their work without our humble assistance.
The rest of us guys – have NOTHING to protect. All of us have the identical registry tweaks, unlocks etc.
Protection of your personal “eye candy” stuff is considered to be a waste of time – all nice pictures are available in web.
So guys – please stop PM-ing about WP7 rom protection – at least until we all start to really develop WP7 – not just dump stocks and rebuild them moving away some langs and adding some pictures.
One more important thing: dumping DFT PROTECTED roms will NEVER be implemented as DumpTool feature.
Changing the LOGO and SLDR1-2
NK.bin XIP as well as automatic
1: Changing the LOGO and SLDR1-2
thanks
pdaimatejam said:
NK.bin XIP as well as automatic
1: Changing the LOGO and SLDR1-2
thanks
Click to expand...
Click to collapse
Changing LOGO - already implemented. Will be available in the next public version (coming soon).
Base OS.nb file is over 300Mb in the kitchen. So I have to rebuild it into smallest size manually. (after reduced its size about 20Mb)
My suggestion is OSbuilder will auto reduce base OS.nb after run dump/create packages to get smallest kitchen folder size. Thanks so much.
Regards.
nhathoa said:
Base OS.nb file is over 300Mb in the kitchen. So I have to rebuild it into smallest size manually. (after reduced its size about 20Mb)
My suggestion is OSbuilder will auto reduce base OS.nb after run dump/create packages to get smallest kitchen folder size. Thanks so much.
Regards.
Click to expand...
Click to collapse
We are working on it, but we don't have enough info about some data structures in NB to recreate them. If you have all info about them, please PM me. (logical/checkpoint sectors recreation, mapping tables, etc...)
EDIT: nhathoa, thanks for your advice in PM
nhathoa said:
Base OS.nb file is over 300Mb in the kitchen. So I have to rebuild it into smallest size manually. (after reduced its size about 20Mb)
My suggestion is OSbuilder will auto reduce base OS.nb after run dump/create packages to get smallest kitchen folder size. Thanks so much.
Regards.
Click to expand...
Click to collapse
If we get any new *.nbh file then OSBuilder display error, but if we get os.nb.payload from this same ROM, then OSBuilder support this file
Important:
OSbuilder: - In this moment no extract/dump of some files *. nb0 (SAMSUNG), and *.nbh (exam. HTC Spark/Mozart/Mango)
Nokser said:
In this moment no extract/dump of some files *. nb0 (SAMSUNG), and *.nbh (exam. HTC Spark/Mozart/Mango)
Click to expand...
Click to collapse
OSbuilder supports Mozart/Spark stock rom, but do not try to dump DFT protected ROMs.
Btw i've got Mozart and i made the dump with OSBuilder
Guys, this message is about Rom-Protection feature of OsBuilder.
The OsBuilder developers and the other members of asusmobile team get a lot of PMs from xda rom-cooking guys with the requests to implement kinda “rom protection” feature for WP7 roms.
Guys and gals!
For the moment only one developer has a real reason to protect his own work. It’s DFT, because DFT makes real development. With unique programs and features included. With new cool possibilities enabled.
But DFT is able to PERFECTLY protect their work without our humble assistance.
The rest of us guys – have NOTHING to protect. All of us have the identical registry tweaks, unlocks etc.
Protection of your personal “eye candy” stuff is considered to be a waste of time – all nice pictures are available in web.
So guys – please stop PM-ing about WP7 rom protection – at least until we all start to really develop WP7 – not just dump stocks and rebuild them moving away some langs and adding some pictures.
One more important thing: dumping DFT PROTECTED roms will NEVER be implemented as DumpTool feature.
This message will be added to the first post
will ROM protection ever be implemented in future version of OS Builder?
though, i suppose, one knows they have a 'good' ROM when others' 'take' from it.
would like to see...
a. Settings be save-able and imported
b. being able to import .CAB files (i.e. OEM firmware updates)
also, in the current version of OS Builder,
if Expand/Collapse button is Expanded and the content is refreshed, the Expand/Collapse button doesn't revert to Expand even though it is Collapsed.
hope that made sense.
sh4d0w86 said:
...being able to import .CAB files (i.e. OEM firmware updates)
Click to expand...
Click to collapse
We are working on it
Really hope i well see other web viewer like opera or firefox
Maybe we well see a new way to custom our home screen
hossam.salah, heh
I would also like to have new opera and customized homescreen.... And even something else... like new WP7 phone set
Hate to disappoint you, but we discuss here future OsBuilder features. OsBuilder does not provide any new OEM packages or custom screens. It's an advanced tool for creating roms.
So your dreams should be published maybe in WP7 Software development thread...
sh4d0w86 said:
b. being able to import .CAB files (i.e. OEM firmware updates)
Click to expand...
Click to collapse
I would love to see that
IzaacJ said:
I would love to see that
Click to expand...
Click to collapse
Will be implemented in future public
Changing the logo
florirs said:
Changing the logo
Click to expand...
Click to collapse
Implemented already! Since OS Builder V1.3.189 FULL (08.11.2011)
Read changelogs!
http://forum.xda-developers.com/showpost.php?p=19168768&postcount=65
POLL What new features do you want to have in OsBuilder future releases
Hey guys What apps do you use most and are best with HTC HD2?
because we can get widgets made to link these apps on the touchxperince homescreen
mine in google maps with street view
BiapLorScarp said:
Hey guys...
Click to expand...
Click to collapse
Hey guy!
If you are able to explain - what is common between OsBuilder features thread and Google Maps with touchxperience on Leo - we will definitely talk about that....
Otherwise - try to find yourself another topic to talk.
Start point for bulding wp7 for hd2
mb a basic non protected non dft dump?
not sure what i just sayed but i think you understand what i meen.
will Samsung support be coming to OSBuilder?
Related
this is rom for new gene ie ht8xxxxx
nothing new just port xip sys for new gene
original rom
here is kitchen only work for new gene
part1 part2
extract all file in same folder
Thank you for the same. Just for the sake of curiosity, how much RAM is available free, on startup, in this ROM?
Hey Ankit, you did it yourself? have you found out the kitchen?
After reading the original thread, i guess there are many unsolved issues with this ROM. Calculator doesn't works, calender gives problem, powerpoint gives some certificate error, No java etc. And i think this also does not include Windows Live.
So i dont think its worth an upgrade. This ROM needs some serious tweaking before i can use it. I haven't installed this ROM but i got all this conclusion from the original thread. Is anybody's experience better with this ROM?
dheerajk27 said:
Thank you for the same. Just for the sake of curiosity, how much RAM is available free, on startup, in this ROM?
Click to expand...
Click to collapse
According to the author, you'll have about 29 MB. Haven't tested yet.
krazy_about_technology said:
Hey Ankit, you did it yourself? have you found out the kitchen?
After reading the original thread, i guess there are many unsolved issues with this ROM. Calculator doesn't works, calender gives problem, powerpoint gives some certificate error, No java etc. And i think this also does not include Windows Live.
So i dont think its worth an upgrade. This ROM needs some serious tweaking before i can use it. I haven't installed this ROM but i got all this conclusion from the original thread. Is anybody's experience better with this ROM?
Click to expand...
Click to collapse
yes i did it myself
i port xip sys first then use Ramersonw's Kitchen (some modification required )
i will upload kitchen tonight so u modify it
because my exam is there i not be able to Cook rom
can u post some screen shots plzzz..if u hav any
thnx
@ankit360: I would really appreciate it buddy if you share with me the details of the process of XIP porting you gone through. I want to learn the whole process as its quiet an important information to cook a ROM successfully. After knowing all this, i would be able to create ROMs and share them with our friends here.
Its really great man! you learned the process so quickly. Hats off to you!
Hey Ankit,
I tried this ROM. Its clean and ultra fast and very little problems. I am sure if they are ironed out, this could be an ultimate ROM for Gene. i have written about the problems in my previous post. In addition to those here is another one.
I tried installing windows live on this rom too but it didn't worked. Since this is a quiet clean ROM with no Windows Live in ROM, there is no possibility of any conflict. I think the problem is related to some certificates.
I examined my original WM 6 ROM and found that All the ROMs in this forum contains all the other certificates except these two from HTC on the top of the list, see the attached files.
I think this could be the cause of all the Windows Live problems as may be since these certificates are not present, windows live is unable to communicate with the server over an encrypted ssl connection.
What do you think?
I will try to extract these out of the ROM. You try yourself too and PM me if there is any success.
can u list out all bug so i will try to fix it
Just trying out your ROM, its lightning fast!
Thanks for the ROM
60 MB free after restoration of around 300 contacts! Wow, Gr8 Word
@ankit360: OK, here is the list of bugs:
1. Calculator is not working. Reports a missing file "\windows\spbcalc_p.gif".
2. Calender not working.
3. Java runtime is not included (if you correct this error and insert a java runtime, use the latest JBed version, it is the only runtime that can run opera mini fullscreen)
4. Powerpoint shortcut not working. It needs a change in registry. If you click the shortcut it will say some certificate thing but thats not true. The shortcut points to the shortname :MSPOWERPINT. These shortnames are created in registry and the path to powerpoint exe is not correctly given there. either correcting the path in registry or making the shortcut directly point to the powerpoint executable will correct this error.
5. Small bug but there is no option to set the device lock (password when the phone is restarted)
6. No Transcriber (Not really a bug but i need it)
7. Clock canot be set to 12 hour format. it always returns to 24 hour format.
8. Search feature that comes with default windows mobile has been removed.
9. Tabs in HTC home show up even when they are removed from settings>today>htc home setting. It happens sometimes only i think.
10. Windows Live not working at all even after installing the official cab. I tried about 10 cabs from this forum. Nothing worked. It confirms that the issue is not due to conflict with older version of live on ROM coz this ROM doesn't have windows live on it.
Thats all i can think of right now. Will post more if i find some.
man i don't have time to fix this issue bcoz my exam is there
i make kitchen for this rom work only for new gene
try to fix bug and release some nice rom
happy rom cooking
part1 part2
extract all file in same folder
Hey ankit,
I have succeeded in porting the XIP of the default kitchen given by Ramersonw by using my original Wm 6 XIP as base. I have created a ROM based on that kitchen which i will post tomorrow as i am currently uploading both of these.
The kitchen is working perfectly for new GENE and i am 90% sure that i'll be able to port most of the ROMs using this kitchen. Will post kitchen on the Ramersonw's thread also.
that's grate news plz post only xip or changes u made is default kitchens i will not able to download whole because i don;t have enough bandwidth
Hi Ankit,
I am uploading the zip file with changes only. Here is the link for it. And dont forget to read the Readme.txt i have included in it. I am also uploading the ROM i created. Wait for the new ROM thread. Here is the address for the zip file:
http://cid-988261b694475a67.skydriv...gesOnly|_for|_NewGene|_Kitchen|_Ramersonw.zip
thanks for sharing file i will test it
i want to know is ur xip porting procedure is work on different gene rom ?
my xip port procedure work on only this rom
My XIP will work on any ROM which has the same version of WM 6.1. Actually buddy, as you might already know, what happens is that XIP contains a portion of the main files of the WIndows Mobile operating system which are executed without loading into main ram. That is why this part is called XIP (eXecute In Place). So These files have to be the exact same version as the rest of the OS. My XIP is from CE OS 5.2.20931 (Build 20931.1.5.0) so all the ROMs that use this version of WM 6.1 can use this XIP as base.
And this is true for your ROM too. You can use the XIP with any ROM with same version and build no.
I hope i have made myself clear but feel free to ask more.
thanks for info man i really don't known this
Sorry for bumping this.
I have installed this ROM, And I really liked this. It has fastest responce times, and the most Available RAM, from all the ROM's for Gene(More than 25% using even after 2 Hrs of use.)
So Ankit or Sumit, if you have time, will you please modify this rom (I still need to learn cooking.)
Download Java - JBed
Attached the spbcalc_p.gif. Placing it in windows dir, works.
Thanks
Sumit
brother Sumit / Ankit: Please cook and release for Old Gene also.
We are in a very need for such application that saves our PPC a lot of Flashing.
I think my GENE Device is about to kill me because i'm flashing it almost every day with each of my cooked ROM for testing.
I searched all the WEB without any success till now.
I'm requesting Everybody that has any single piece of success in this regard to tell us HERE about his tries and to make this Thread helpfull for everybody .
please go ahead all and put your comments.
There is no emulator available for cooked roms, not even for official HTC roms. The Microsoft emulator uses a very different file format a lot of other utilties inside the roms that run inside emulators. I have searched a lot and this is the answer i have come up with.
Well, there is a way. You could use samWMEmuKitchen. It has some bugs, but you can try your modifications with it, as add a package to test, registry modifications, etc. Only works with wm6.1 and has some limitations. I used it some time ago to test some modifications before flash my device.
ramersonw said:
You could use samWMEmuKitchen.
Click to expand...
Click to collapse
i appreciate that effort ramersonw.
i already used your emulation kitcken long time ago.
there might be missunderstanding, i'm looking for emulator that i can inject with any cooked ROM but your kitchen can be used perfectly for testing some minor changes
for example. i tried to inject Arabizer and it come with black screen, i might use it in a wrong way, would you please help me?
Hi there!
I need a working ROM for my HTC Touch Pro.
I found one (hxxp://forum.xda-developers.com/showthread.php?t=470164) but that one was posted in 2007 so the download file is long gone from the internet! It was a ROM with a Stock market tab in FT3D.
I've read the rules and the Wiki but still I can't find what I'm looking for on this forum because of the many ROM's people have made! Don't get me wrong: I think that's great but I need help locating the right manilla that can be downloaded! Or point me in the direction were to look!
Thanks for your help! and greetingz from Holland
Mike
Er...
Well the latest is Manila 2.5 or sense 2.5 w/e you want to call it.
Most of the roms offer one or the other.
perrsonally i recommend energy rom... they're wonderful.
Leo version is slow but pretty
Pheonix two is strong.
rahul_bhatia said:
Well the latest is Manila 2.5 or sense 2.5 w/e you want to call it.
Most of the roms offer one or the other.
perrsonally i recommend energy rom... they're wonderful.
Leo version is slow but pretty
Pheonix two is strong.
Click to expand...
Click to collapse
Agreed.
rahul_bhatia said:
Well the latest is Manila 2.5 or sense 2.5 w/e you want to call it.
Most of the roms offer one or the other.
perrsonally i recommend energy rom... they're wonderful.
Leo version is slow but pretty
Pheonix two is strong.
Click to expand...
Click to collapse
Oké! Thanks for your replay. I've read somewere that manilla 2.6 is still in beta?
I know (from the wiki) that I have a HTC "Raphael" (touch pro...duh! ) but I see a lot of ROM's for the Diamond and pro 2 aswell! Do they all work fine on the Touch pro to? As a newbie I don't know were to look for when I'm looking for a ROM.
Can I create a ROM of my one? What need I to do that? I know my way around Paint Shop Pro but not around programming like in C++.
Manila (aka SenseUI)
Newer versions of Manila may require that you use a WinMO 6.5 custom ROM as HTC released the new 2.x versions of Manila (aka Sense) on devices that sported WinMO 6.5.
Additionally, some of the recent Manila releases (ex: 2.5, 2.6) may be versions obtained from dev/test ROM source. If you're after stability or rely on your device, this may not be preferable.
Custom ROM's
There are several customs available ... some chefs even release different ROM streams. In many cases, custom ROM's will also contain recent application updates. If you're after stability or rely on your device, once again this may not be preferable.
Custom ROM's are usually specific to devices. For example, if you own a Raphael GSM device, you only flash custom ROM that are Raphael GSM specific. Flashing custom ROM's from a different device or CDMA may permanently damage your device.
Kitchen (DIY Custom ROM)
Building a custom ROM has become much simpler. Many chefs who have moved onto another mobile device will often release a final ROM as well as the kitchen they use to prepare the ROM ... this serves as a great starting point.
Additionally, there are many tutorials available on how to use kitchens floating around the forum.
Lastly, moderators typically close threads requesting "What's The Best ROM" as selecting a custom ROM is like choosing a vehicle, house, partner ... it's all about personal preference. And from past experiences, these types of threads usually get out of control pretty quick. So, to avoid having a thread that you start closed, it is best to avoid "What's The Best ROM" discussions.
HTH,
OH..........sorry!
Don't want to upset the moderators!
Then I have just one final question:
Is there on this forum-part a topic with a standard ROM with instruction on how to customize it? Or can I find those things in the Wiki?
I would like to contribute to theme's or even a Dutch ROM.
I only need to know/learn how to do that! Can someone give me a link to some documentation and files/programs to use?
Thanks!
mww1977 said:
Is there on this forum-part a topic with a standard ROM with instruction on how to customize it? Or can I find those things in the Wiki?
Click to expand...
Click to collapse
AFAIK, there isn't a "Generic" ROM with customization tips. What most members do is download a kitchen and post any customization related question in the corresponding kitchen thread.
[KITCHENS & OEM PACKAGES] Raphael GSM Devices
http://forum.xda-developers.com/showthread.php?t=582134
I would like to contribute to theme's or even a Dutch ROM.
I only need to know/learn how to do that! Can someone give me a link to some documentation and files/programs to use?
Click to expand...
Click to collapse
For additional applications and theme customization, look at these sections of XDA. They may provide the information you are after.
Windows Mobile Development and Hacking
http://forum.xda-developers.com/forumdisplay.php?f=522
Windows Mobile Development and Hacking
http://forum.xda-developers.com/forumdisplay.php?f=473
Cheers,
Without the inclusion of proper documentation included with an Android Rom or an Android Build users will start filling up the HD2 Android Development Forum with why this wont work when it does on someone elses Rom. To stop this from happening there will be a requirement when creating a Thread for a Rom with Android included, or an Android Build.
------------------------------------------
------------------------------------------
If you are making a Rom with Android built in or an Android Build that is run from haret then please INCLUDE with your file a readme.txt file in the ROOT of your release archive with the following information:
*What BUILD version?
An internal version # that can be used to identify the authors exact release (e.g. my-rom-v0.5.zip) for easier reference for the users and fellow developers benefiting from the release.
*Which kernel image and kernel modules are used?
Where are zImage and modules.ko originally downloaded (in case the chef didn't compile on their own) and where is the kernel source code for the kernel and modules.
In case the chef did not compile on his own, he should still be able find out where the source code is.
(The license under which the Linux kernel is released requires the distribution of the source code that was used when distributing builds.)
*What rootfilesystems are used?
Where was it taken from, what does it include (android version it's based on etc) and in case of self compilation, where is the source code.
(In case of most windows mobile shipped devices that's often some rootfs file e.g. named android.ext2 and an initial ram filesystem often named initrd.cpio.gz).
*ChangeLog*
A ChangeLog is really an essential addition in every build as it informs the end user what modifications have been made from the last build. This will save you ALOT of questions as to what has been added, deleted or modified and therefore is a requirement for everyones benefit.
*WindowsMobile version your Android Build was tested on*
Please include your WinMo Build version, HTC OemDrivers (if known), XIP (if known) and Radio version so that users know what the Android Build was tested on and can replicate if neccessary for fault finding purposes.
------------------------------------------
------------------------------------------
If you are unable to obtain any of this information and thus can't make it available through an included readme.txt you should not distribute your rom and keep it for personal use only.
If you are using an exact copy of a present release (e.g. in case of a WinCE rom that has an android 'dual boot' option) you must include the readme.txt from the original rom chef.
If you release a Rom and do not have the required information then you will be asked to either create and include a readme.txt file with your Rom or ask for the thread to be deleted.
If you have any comments or questions on this please feel free to post.
Mark.
** reserved **
Thanks a lot for the quick action, Mark. I am glad to see a first positive response.
If this will establish I hope that
*users are informed about what they get
=>less unneeded questions and thus more room for constructive feedback
*developers have an easier time to benefit from present releases
*new developers must try to get an understanding of what they are doing
=>more quality releases
The original post can be found here.
I think it would be nice to hammer out the readme.txt requirements together with chefs so we can get some convention that satisfies everybody.
edit: Think it will really be good to always put readme.txt in root of release archive so everybody knows where to look for it.
dcordes said:
edit: Think it will really be good to always put readme.txt in root of release archive so everybody knows where to look for it.
Click to expand...
Click to collapse
Edited the 1st post to include this
Mark.
Will be following this convention for any future releases
DarkStone1337 said:
Will be following this convention for any future releases
Click to expand...
Click to collapse
Thank you
Future releases soon I hope lol
Mark.
May I suggest that the readme include the date of ROM compilation, as well as the date the kernel and root file systems files. I think this will help users and chefs to easily build there own compilations and keep track of it's validity.
And a title format like: [date]-[name]-[version]-{[kernel]-[kerneldate]}-{[modules]-[modules-date]}-[rootfs] (just like rules for 'regular' roms). Both for the post and the archive preferably?
Personally I switch between versions a lot, to find differences/improvements/bugs.
Clear archive-naming should simplyfy this .
Excellent rules! We need to improve stability of ports and eliminate all unnecessary questions !
P.S. Hope there won't be any "bogus", or "copy-paste-claim" ROM-s.
dcordes an mskip +1
ahbad said:
May I suggest that the readme include the date of ROM compilation, as well as the date the kernel and root file systems files. I think this will help users and chefs to easily build there own compilations and keep track of it's validity.
Click to expand...
Click to collapse
Very good idea. I think we should at least add the rom release date to minimum required readme.txt information.
For the rootfs release date I think we should leave it up to the chefs because I think it will be hard to find out in many cases. Reason is rootfilesystems get passed on 20 times...
In case of the kernel release date it might be a good idea to add it. should be easy to find out. When you grab the kernel e.g. from the two sources I link to in the thread
http://oe.netripper.com/files/htcleo_autobuild/
http://cotulla.pp.ru/leo/Android/
you can just copy paste the date from filename or information on the site. This would be very useful assuming the kernel images will be removed at some point.
On a side note: For both kernel examples the source code repository to add in readme.txt is
git://git.linuxtogo.org/home/groups/mobile-linux/kernel.git htc-msm-2.6.32
gitweb: http://git.linuxtogo.org/?p=groups/mobile-linux/kernel.git;a=shortlog;h=refs/heads/htc-msm-2.6.32
So currently in every leo rom readme.txt this must be linked to as kernel source reference. netripper autobuild zImages using this exact source code and cotulla zImages share same codebase (although currently the latest changes are unavailable but will be added in git soon)
shufflez said:
And a title format like: [date]-[name]-[version]-{[kernel]-[kerneldate]}-{[modules]-[modules-date]}-[rootfs] (just like rules for 'regular' roms). Both for the post and the archive preferably?
Personally I switch between versions a lot, to find differences/improvements/bugs.
Clear archive-naming should simplyfy this .
Click to expand...
Click to collapse
To me that seems over exaggerated. Rom version in file name should be enough. Rest can be looked up in readme.txt
So what does everybody think? If we add the release date of kernel and completed rom, do we have an agreement ? In that case we should compile an example and add it in the first post.
best regards
your right dcordes too much information in the title can be a bad thing. Something more like
[Date] [Name] [Version] [Build] [maybe Kernel version]
That should be Enough i think so for Example
[21/07] [Darkstone1337] [v5] [Eclair w/sense] [2.6.32]
Everything else should stay a change log for people to read
David Balfour said:
your right dcordes too much information in the title can be a bad thing. Something more like
[Date] [Name] [Version] [Build] [maybe Kernel version]
That should be Enough i think so for Example
[21/07] [Darkstone1337] [v5] [Eclair w/sense] [2.6.32]
Everything else should stay a change log for people to read
Click to expand...
Click to collapse
I am sticking with my opinion:
*in filename require internal chef rom version
*in readme.txt add:
-rom release date
-kernel release date
Mark what do you think? Any other opinions?
Install to folder
May be a good idea install all files to appropriate folder, not directly root of SDcard as in last darkstone FROYO. Greatly simplify process of testing and changes between several images and don't messy root. Switching between different versions is than as easy as renaming directory.
I think we should also leave directory structure etc to the chef as long as readme.txt with all the required information exists in archive root so users can find it easily.
so do we have some agreement here? Mark ? If so you should update the first post to compile final set of information needed and clarify that it is not a nice extra but a requirement.
dcordes said:
I am sticking with my opinion:
*in filename require internal chef rom version
*in readme.txt add:
-rom release date
-kernel release date
Mark what do you think? Any other opinions?
Click to expand...
Click to collapse
I agree with you on this theres no need to make things more complicated than they need to be. Although there does need to be some sort of standard for the thread title.
And no I cant think of anything else right now that needs to go in.
dcordes said:
I think we should also leave directory structure etc to the chef as long as readme.txt with all the required information exists in archive root so users can find it easily.
so do we have some agreement here? Mark ? If so you should update the first post to compile final set of information needed and clarify that it is not a nice extra but a requirement.
Click to expand...
Click to collapse
Also agree that its upto the chef how they want their files set up as long as its clearly stated in the readme.txt what to do to get it working.
Everything sounds fine What needs adding to the first post to make it complete?
Sorry I have been working on my Loader but its all finished now (I hope).
Mark.
HD2 Android Image & Instructions
Hi All,
Can somebody confirm if there is a working Android image for the HD2 yet? From reading previous threads, it would seem there is still some technical challenges, no image is available yet.
If I am wrong, please could somebody tell me the location of an image and instructions so I can install Android on my HD2? I am struggling with WM6.5 and I much prefer Android. I have used WM for 9-years now but it just doesn't compare - partially because there are limited decent apps available.
All the best,
Youdaler
youdaler said:
Hi All,
Can somebody confirm if there is a working Android image for the HD2 yet? From reading previous threads, it would seem there is still some technical challenges, no image is available yet.
If I am wrong, please could somebody tell me the location of an image and instructions so I can install Android on my HD2? I am struggling with WM6.5 and I much prefer Android. I have used WM for 9-years now but it just doesn't compare - partially because there are limited decent apps available.
All the best,
Youdaler
Click to expand...
Click to collapse
I will just give you a friendly warning this time as it is your first post. This thread is for the discussion of information to be included by Android builders.
If you look in the Android forum then you will see working builds by DarkStone and by Dan1j3l. Look at their threads for how to load Android. to answer your question yes Android does work (95%) on the HD2.
Please confirm you have read this so I can delete these posts and keep the thread clean. In futured please only post in the correct thread and if you arent sure then post in the Q&A thread at the top of the Android forum.
Mark.
Understand. Thanks for clarifying.
I think we should extend the readme.txt items with some section like 'expected issues' or 'known problems' .
And in the readme.txt , could help too:
Tested with:
-WinMo rom x.xx.xx
-Radio rom 2.xx.xx
Sent from my HTC Desire using XDA App
Welcome to an experiment... members only AND FREE online kitchens for CyanogenMod 6.0.0 Release and Nightly builds.
Update: The auto-updating nightly kitchens are now online!
About the MoDaCo Online Kitchen infrastructure
Regular readers will know we've been running an online kitchen for a while, providing ROM building services to AdFree and Plus members. The reason the kitchens have only been available to members is simple - load. The infrastructure required to support kitchens for a large number of users and devices just isn't economically viable.
At the time of writing, the MoDaCo infrastructure consists of four dedicated servers (all running quad core processors with large disks and a large amount of memory). These servers run custom load balancing software designed to ensure that all of the servers are utilised as optimally as possible to provide the best possible build experience.
The experiment
I have set up two free kitchens below to use one of these servers, leaving the other 3 servers load balancing for Ad Free and Plus members. Now, there's a possibility that the free kitchen could become overloaded and collapse in a big heap, but to a certain extent that is the point of this exercise. To get a gauge on the impact of making an online kitchen more widely available. This is a very limited test and won't be extended to all kitchen ROMs.
The kitchen provides both the stable release build and the current unstable 'nightly' build (with update checks hourly).
Is there a difference between the members only and free kitchens?
The biggest difference of course is the allocation of servers in the farm, which equates to speed and availability. The other difference is that the member kitchen can create signed builds, whereas the free kitchen cannot.
Awesome! How do I support future kitchen developments?
Details on how to donate are in the original post at MoDaCo.
Do we post feedback on the CM 6 ROM here?
Only feedback on any issues relating to the kitchen... feedback on the ROM itself should be posted at the CyanogenMod forum.
Anything else?
The kitchens can be found here (unfortunately there's no way for me to embed them into this post) . Enjoy!
P
Very cool, thanks
Cool.
Im an AdFree Modaco Member.
I will really enjoy the nightly kitchen with (maybe?) an old App2sd+ option.
Nice. Oh and have you abandoned sense for nexus? Wanted trackball colours to make it complete
ermacwins said:
Nice. Oh and have you abandoned sense for nexus? Wanted trackball colours to make it complete
Click to expand...
Click to collapse
Not at all, finishing up the new Desire Froyo / Sense port (details) then i'll drop in the bits for N1 support.
P
Thanks for all this information
paulobrien said:
Not at all, finishing up the new Desire Froyo / Sense port (details) then i'll drop in the bits for N1 support.
P
Click to expand...
Click to collapse
thats great, is it possible to get ta support?
ermacwins said:
thats great, is it possible to get ta support?
Click to expand...
Click to collapse
Of course.
P
Update: The auto-updating nightly kitchens are now online!
P
Update: The auto-updating nightly kitchens are now online!
P
paulobrien said:
Update: The auto-updating nightly kitchens are now online!
P
Click to expand...
Click to collapse
Great! (they update same time as the nightly's?) Awesome!
Excellent idea Paul! Suggestion: I've always wondered if it would be possible to save my kitchen selections so I don't have to click all over the place every time I download. Nice work!
Yeah, that feature is coming!
P
AWESOME!
I did a CM Nightly, removed all the stuff I never ever use and now as soon as it downloads I just have to sign it and flash!
I wonder how it'll run.
Or just flash using clockworkmod recovery where signing isn't needed...
P
I am new here, I try to update the Kitchened ROM. But it failed, Error: Status 6.
Pls advise.
Thanks!
Tony
Which options did you bake in / out?
P
Hi Paul... I cooked a (nightly) rom with your "premium" kitchen... but I've got a question: if I try to look for an upgraded version of the rom (through the "Rom update utility") it say that there are no updated version of it.
This happens every night I try.
So... what I have to do to upgrade my nightly "cooked" (clean by all unused stuff ecc...) cyanogen rom? I don't want to upgrade to the stock nightly one, this way the online cooking became useful!
Thanks in advance and... sorry for my bad english, I'm from Italy.
spelverso said:
Hi Paul... I cooked a (nightly) rom with your "premium" kitchen... but I've got a question: if I try to look for an upgraded version of the rom (through the "Rom update utility") it say that there are no updated version of it.
This happens every night I try.
Click to expand...
Click to collapse
Rom manager only checks for the original Nightly zip file. The kitchen adds the selected Gapps into the zip. ( I think )
spelverso said:
So... what I have to do to upgrade my nightly "cooked" (clean by all unused stuff ecc...) cyanogen rom? I don't want to upgrade to the stock nightly one, this way the online cooking became useful!
Click to expand...
Click to collapse
I dont use Rom manager anymore.
Only press: Power> Reboot> Recovery> wipe> install from sd> reboot
Titanium backup for some settings......done
spelverso said:
Thanks in advance and... sorry for my bad english, I'm from Italy.
Click to expand...
Click to collapse
I'm from Sweden....
The kitchen is missing the main ingridient,
the 040411 rom. (001328 rom was ok)
PM sent.
EDIT: Working now.