Related
Just a quick opinion required from the chef types. THere are lots of prebuilt roms floating about in here. And since the newer 1620 and 1908 etc versions surfaced, i have given a few of these a go. And they rock!!! I have never seen the messaging app run so fast, no key lag whatsoever and deleting items etc is almost instant.
However, every rom i have tested has something i dont like about it. IE netowrk config tool, i never use this, and there are tons of other apps that i will never use.
It seems to me there are 4 basic levels of users on these forums
1. Flash prebuilt roms only, dont want to use kitchens
2. Able to flash roms and like to mess with kitchens
3. All of above but can also extract roms and tweak
4. Uber chefs that are porting and messing with modules etc
I would put myself in group 2, i have used many kitchens and cooked a lot of roms for personal use only, as this way i get WM6 with only the apps i need, and ones that arent listed in any roms.
However i havent had much success with extracting 1908 roms to use in a kitchen to put my own apps in.
WHy not when the chefs are releasing their prebuilt roms can they not release a clean SYS and ROM folder so that many users like myself can just pop it into their kitchen of choice and cook up exactly what they want, getting their perfect selection of apps while also getting hte benefit of a nice new rom base??
And if any of the chefs on here would even like to send me the above but not make it public i would be most appreciative, i just really want to cook up my own 1908 rom for my own use and no one elses. I ike a clean rom as i have a cab i made to install my exchange settings and locale etc, and mms server settings and wifi networks, owner info etc.
Thanks for taking the time to read this
Colin aka saywhat
Most of the 1908's i tried the chef's had removed the rgu files, thus device would just hang when booting after flashing. Try extracting something like BD3 which still has the RGU files in the ROM
Kitchen Based on HyperCore and Bepe's new Compact ELF/IN DevPack.
SuperProCore Is On Hold
Ported XIP Caused SD reading Issues and Bluetooth Radio Issues.
(Syrop how's this working on your version?)
This is an OpenKitchen anyone can contribute, this is for the community and those pesky users that come download and never report issues or say thanks.
SuperProCore, is a kitchen based on a new small simple kitchen made by Bepe (as usual).
Of which you will find the original thread here.
What Makes it SuperPro, is hopefully the amount of Packages/Selectable Apps and options that will show up when you start building the ROM.
What Makes it Core is that hopefully i'll learn how to get some of the great tools in the HyperCore Kitchen...
Everythings discusable.
It's because Microsoft doesn't like to listen that most of us hang out at XDA.
Buttttt.... I have to make one Dictotariol Discision.
Help Files Are A No No.
I have never opened one.
And anyone that needs them on their phone should notbe flashing their Phone.
I onlyleave .htm files in that are doubtfull or needed.
6 Years ago when i first flashed my firt HTC/02 Device XDA allready was about downloading a RomCustomizer, choosing your options then flashing it.
Now since HTC got a bit more stuck up and build a lot more security into their Devices other tools are needed and used. And getting your own custom Rom needs a lot of reading and testing.
The thing is the tools are available, and everyone should be able to do cook their own personal Rom.
Now knowing myself i could work 24/7 on this project (I'm a ****ing Chaotic,Paranoid, Compulsive Cooker), but sadly, i also have a life and need to keep myself healthy.
So i'm hoping Some people will jump on this project, even if it means putting "Cooks" out of busines. But hey it will propably also get some people more nights of decent sleep
For now i'm just curious of the opinions and discusions that will pop up.
The Beta v3 ELF/IN Devpack should be enough for some old and new "cooks" (40 downloads) to play with.
So here's an easy deadline, Small update coming next week Wednesday.
Now let's get this thread Sticky.
Extended Elf/Elfin Kitchen for WM6.1
Version 0.6
Download
Nothing New Here.
Requires the Microsoft Visual C++ 2008 Redistributable Package
Bepe's Original Kitchen for ELF/IN.
Just the files to cook with.
So it can be seperatly be updated with New Batch files, Tools and flashing methods.
Why seperate?
Because there are people that know a lot more about writing batch files and apps then me (I know jack ****).
This way if anyone can contribute just to the small kitchen others don't need to download all the seperate packages for the update.
Changelog
XIP ELF/IN Core
Version 1.2
Download
This OEM Package can be used only ihttp://rapidshare.com/files/95392724/ROM.zipn the ELFIN Kitchens.
Why Seperate XIP Package?
Well maybe some people want to get it working in other kitchens
ChangeLog
XIP ELF Only Core
Yeah this one has 4MB PP
XIP taken from hdubli's WM6.1 CE OS5.2.1238 (Build 19521.1.1.0)
Hopefully SOMEONE gets this working.
I have Put the XIP in the Above XIP package SYRXIP (It's Extracted from Syrup's Rom Which Worked, but extracted Bluetooth is dead SD is dead and Wifi IS Dead)(But maybe i remember it incorrect)
OEM Package Update
Version 1.2
Download
This OEM Package can be both Kitchens (If i ever get the SuperProCore Working)
Why Seperate OEM Package.
Well the OEM will become smaller and smaller as parts move into the SYS package and as files get merged or deleted from OEM Package.
ChangeLog
SYS Package Update
Version 1.2
Download
This SYS Package can be both Kitchens (If i ever get the SuperProCore Working)
Why Seperate SYS Package.
Well the SYS will become BIGGER and BIGGER as parts from OEM move into the SYS package as selectable options and new Packages get added to it.
ChangeLog
Rules
What Rules?
Oh Yeah..!
This is not a "I'm Having Trouble FlashingThread"
Packages must have a Byte Count in the <Tip> Field.
Explanation Here.
Add Blank Safety Files To Prevent Overlapping Packages.
Explanation Here.
IMportant Links Thread
Important Reading Material
Cooking Class
Bepe's Beta Kitchen
Suggestions?
Roms Created By Contributors (for the really lazy people out there)
My Personal Rom Cooked With This Kitchen
You?
Explanation Of Byte Field In option.xml file
Well as some people might want to hit a specific target for their end RUU_Signed.nbh file.
It might be handy to have some bytes to give them an indication of how much space a package might takein the file .NBH file.
And maybe if we are very nice and Bepe's very happy, he might consider to Change/Patch BUILDOS to read a new option.xml field with these Bytes to Calculate the end result build, while still in BUILD OS so it wont run when under 50MB?
Methinks that wouldbe a nice feature.
And it would propably need to read a settings.xml file that contains The Core bytes count and wwehter this Security feature is on or of.
What do you think Bepe Nice Idea?
Explanation Of Blank Safety Files
Let's Say there are 5 different Commanagers and you select two?
Well Buildos will tell you which folder itlast processed butit could even be moreacurate orexplanatory.
What if it's a package only containing an registry setting that will kill another registry setting in a similar or different package?
Well if it's known and both packages would have a blankfile with name that will give you the crucial hint where to look for the wrong selected option.
The GlyphCache Packages are a small and explanatory example of what mean.
They all Contain a blank text file without extension name
"You Have Selected Mutliple Options In The GlyphCache Section"
So when you select two by accident you get the regular BUILD OS error but becauseit shows you the file name, it's easier to find.
Again it would be nice if this could be done by BUILDOS by reading another option.xml file.
Oh, nice work! Thanks!
Checking the size in the batch files before we call BuildOS could work!? Well using VBS might be easier... I couls write the target size check if i know how you want to impliment the byte size stuff.
For instance how big is the base? Then each package...
Is it possible to calculate the byte size simply by how big the folders are?
Ouch brain hurts!!
bytespider said:
Checking the size in the batch files before we call BuildOS could work!? Well using VBS might be easier... I couls write the target size check if i know how you want to impliment the byte size stuff.
For instance how big is the base? Then each package...
Is it possible to calculate the byte size simply by how big the folders are?
Ouch brain hurts!!
Click to expand...
Click to collapse
Nah the size of the folder or even just the files that get cooked do not match the eventual size they take in the eventual os.nb or RUU_Sigtned.nbh.
Besides you make the selection of batch/packages inside BUILDOS so depending on that selection you get different outcomes.
At the moment in between living a normal live I run the proces with and then without certain packages and add it to the tip field. So when you mouse over the Option/package in buildos you get the indication.
The eventual base OS i haven't calculated yet as it's not as Base as i want it yet
Good thing there's someone that knows more about some stuff then me.
Tnx
Noonski said:
Stilldon't know what the prefered place is formost cooks to put theirpackages on ELF cooking?
Yes the OEM folders need updates to.
As i'll be merging PROVXML files and taking out parts of the registry to some Seperate SYS Packages to avoid Cooking Conflicts.
All in Time.
Click to expand...
Click to collapse
here is one i like to add to my roms...
Ok, tried it, added some things I usually add, flashed it.
You're saying (or Bepe is) that 19199 is the latest version, yet after flashing it, I'm getting the "old" phone app, not the new one like in Shadow 2.0. Weird? On startup it says Windows mobile 6.09 too... I'm a bit suspicious here
Also, it seems the 8 buttons com manager isn't able to start the wifi properly. PhoneAlarm (accessing the WLAN driver directly) works though.
The esmertec Java package is outdated too, it's back from April.
Otherwise, I'm ending up with much less RAM than Shadow 2.0. Around 3 MB with the same apps installed. I don't understand how that can be ! (8MB PP each)
Positive side is that my touch is much more responsive. I'll keep track of the memory leaks. seems 6.1 handles memory much better, which was really needed with the ELF !
zeflash said:
Ok, tried it, added some things I usually add, flashed it.
You're saying (or Bepe is) that 19199 is the latest version, yet after flashing it, I'm getting the "old" phone app, not the new one like in Shadow 2.0. Weird? On startup it says Windows mobile 6.09 too... I'm a bit suspicious here
Also, it seems the 8 buttons com manager isn't able to start the wifi properly. PhoneAlarm (accessing the WLAN driver directly) works though.
The esmertec Java package is outdated too, it's back from April.
Otherwise, I'm ending up with much less RAM than Shadow 2.0. Around 3 MB with the same apps installed. I don't understand how that can be ! (8MB PP each)
Positive side is that my touch is much more responsive. I'll keep track of the memory leaks. seems 6.1 handles memory much better, which was really needed with the ELF !
Click to expand...
Click to collapse
The Phone skinn is not New to WM 6.1
It's just a ported Phone pad from somewhere....
The emsertec Package might indeed not be new i just grabbed what could get because Shadow Rom was not extractable for Java rgu files.
Nothing has been tweaked memory wise, but if anyone has any ideas.
zeflash said:
Ok, tried it, added some things I usually add, flashed it.
You're saying (or Bepe is) that 19199 is the latest version, yet after flashing it, I'm getting the "old" phone app, not the new one like in Shadow 2.0. Weird? On startup it says Windows mobile 6.09 too... I'm a bit suspicious here
Also, it seems the 8 buttons com manager isn't able to start the wifi properly. PhoneAlarm (accessing the WLAN driver directly) works though.
The esmertec Java package is outdated too, it's back from April.
Otherwise, I'm ending up with much less RAM than Shadow 2.0. Around 3 MB with the same apps installed. I don't understand how that can be ! (8MB PP each)
Positive side is that my touch is much more responsive. I'll keep track of the memory leaks. seems 6.1 handles memory much better, which was really needed with the ELF !
Click to expand...
Click to collapse
Had the same with the comm manager. The one attached works fine.
Added Random Acces and seperate Default Contacts/Addressbbook packages with Security files so they cant be installed together.
(No worries the default is just rgu file.
Added LargeTitleBar to packages thanks Pkoper.
Renamed it to 000_LargeTitleBar tho.
Did Byte Count for Auto Udate. (131072 Bytes)
Now checking what's different with the Commanager you just posted as i allready had an 8 button original one in there.
(i first took out the link.exe but i put it back)
Hmmmmm yours has a different lay out....
Well looks like an extra option package ten don't need all the Graphics and exe's for that in the kitchen.
I'll post what i mean.
A **** it... added Your CommManager anyway. 7-Zip will not take up any more packeging space when files are identical anyway.
Did change UID to be safe.
And added security file will maybe do a byte count sometime.
Keep em Coming.
Maybe tomorow maybe in the weekend, next assignement is make package for new taskmanager and remove it correctly.
And remove SQM (M$ Phone Home) correctly.
probably doesn't belong here, but check this one out http://www.ultimatelaunch.de/
i got the com manager of swiftblade... had similar issues back when i was playing with GTouch....
There is like 4 of us working on a german version of the kitchen at the moment..... headaches!
this one could really grow out of proportion...
There is so much **** one could include.... the size would be just huge
maybe set up a rapidshare thingy for the packages?????
I could probably spare some webspace and traffic...
Where to from here?
Desi Vanilla Shiv Rom: My First Attempt (Includes Weird results - weird things, raw, but somewhat usable )
This is based on the cook-able rom - VERSION 4.1 thingonaspring.6.1.19188.REALVGA
End Result:
Storage Free: 41.87 MB
Program Memory Free: 31.50 MB
... is that Good or bad?
Didn't know how to change the ROM version to my name or DVSR (Title) - guess I need help on that, so it still shows original cooker.
Important Warnings:
- It is not fully Vanilla but I've removed tons of things (and alot of "useful items too)
- Ive removed things generally not available in India (CSD Dialers,etc) and support for out-dated things (infrared,etc)
- If you expect or want a fully featured phone or even half featured - don't try this. I removed tons of OEM & HTC default items that will prevent normal features to work as well (However common and general user - features remain)
- Don't report bugs....I dont know how to fix them
- Feel free to request old OEM modules (I'll cook out a new rom with the original items or extras based on requirements) but I do take a lot of cooking time.
Major Changes:
- Lots of OEM operations removed
- Office Removed
- Infrared system files removed (not all)
- All Sound files removed
- Most help files removed
- Tons of files that seemed useless (to me) removed
- Not for Business Men, More for Testers or Users who want to rid of outdated features, and remove features not supported in "India" or most parts of India.
PS - Will upload file a few hours (24 hours or so)...
- Anyone with experience on cooking roms get in touch with me, I DO need help to get better ROMs out.
Need graphic designers to work out some new icons and changes to various things in the rom
Need someone to send me a zip full of optional components (preready to copy over to the main ROM / sys folder) to get ready....
I'm not a hardcore cooker..I actually "suck" at it, but since I dont see much activity here Im gonna try to make some "stuff" and hopefully learn to be better. Any GOOD CHEF...please get in touch with me and help me out
Regards
WILL USE THIS POST SECTION FOR AN UPDATE or a new rom update.
UPDATE: Moderators - Lock this thread till I update. Seems Ive run into a few more interesting problems. Will need another 48 hours before I release the file.
Anyone who can get me cookable Ranju ROM let me know....Or one of the latest PDAV Roms
This is my 3rd post ever here, so please be gentle.
Crogon said:
I can't seem to find it now, but didn't there used to be a list of pre-cooked ROMs here somewhere?
I think what I'm aiming at is a fully patched / hacked 6.1 HTC ROM with everything fixed and no bugs. Preferably minus any bloatware. If it has recommended utilities pre-installed great, if not, no big loss. Did they ever finish hacking a video driver together? I lost track of that thread, and can't seem to find any current info.
Click to expand...
Click to collapse
Update: I found a tidbit somewhere that says the newest video driver updates should be cooked into the newest ROMs.. but how do I figure out which ones have all the bug patches and hacks installed, and etc. like I mentioned above? I know there USED to be a list of pre-cooked ROMs, but I can't find it now.
Hmm.. Am I maybe thinking of a list of pre-cooked ROMs for the Wing, or some other HTC? If I am, I'm DEFINITELY going to need some ROM recommendations.
Here are my stats, if it helps any:
rom version 3.57.502.2 WWE
rom date 7/17/08
radio version: 1.65.21.18
protocol version: 25.88.40.05H
tri-color screen
KAIS1*0
SPL-3.56.Hard
CPLD-8
.
.
Serial
image version 3.57.502.2
R 1.65.21.18
G 25.88.40.05H
D 3.57.00.00
Thanks again for any help!
if u really want a good cooked rom i suggest you try Garmins roms....they have the latest htc drivers built in...
thats all i can say
mazin13 said:
if u really want a good cooked rom i suggest you try Garmins roms....they have the latest htc drivers built in...
thats all i can say
Click to expand...
Click to collapse
he DOESN'T WANT a cooked rom he is looking for a pre-cooked rom.
@op did you check the kaiser wiki or htc's website?? 'cuz that is where you will find all the latest roms for your device that aren't cooked by a chef.
Also, look around for mbavrian's Kitchen Elements.
The "Base ROMs" on which our Chefs makes their gourmet meals are difficult to locate. Some chefs refuse to share like little playground children.
Others, Like NotATreoFan, have released their base for other people to use to make ROMs. Great Contributors.
Woops!
I guess I stated that incorrectly. Sorry!!
Actually I DO want a custom 'Cooked' ROM. My main purpose of reflashing the ROM is to get rid of all known bugs and bloatware. So I WANT all the custom registry hacks and patches to make everything run smoothly. I want the hacked video drivers (as they appear to currently be stable) and etc..
SO.. I'm looking for:
1) 6.1 OS with fast drivers and all known hacks and patches to have as few bugs as possible. UNLESS 6.1 has introduced some known bugs that can't be fixed (wouldn't surprise me with an MS product). IF there's a bug free FASTER version 5 OS, that will run on the Tilt, I'll be happy with that. One time I installed Win95 on a 1.6Ghz T-bird. Power on to fully loaded desktop was like 2 seconds flat.
2) bloatware removed so as to free up space, and I assume cleaning crap out of the registry wouldn't hurt with speed. Is there a system cache, and would it be beneficial to move it to the SD card? I've read that moving the IE cache to the SD card is asking for trouble, not sure that there's a concensus on that or if it's just opinion though.
OK.. that's going to get confusing. Scratch that and start over:
1) All known bugs hacked or patched.
2) All known speed enhancements (that don't compromise system integrity).
3) Rip out MS (or HTC ..or both?) crapware that COULD be replaced with faster / more functional counterparts.
4) Optional: pre-installed or at least packaged (cab?) applications to enhance functionality. My priority in applications is utility enhancement. Example: I can download 200 Flash / Java / MAME games to the SIM card some day if I get bored, don't need it in the OS. However, if there's a remedial photo editing utility that will allow me to edit my pics before I upload them somewhere, I want it.
I did manage to stumble across a wiki page last night: http://wiki.xda-developers.com/index.php?pagename=Kaiser_Cooked_ROMs
32 Developers and countless ROMs without any comparison isn't much help though. Can I assume all current ROMs are posted there?
Browsing through them, I recall that Alex's ROMs used to be the last word in ROMs, apparently dutty's were until he switched gears. HyperDragon seems to be terribly popular at the moment, but popular doesn't mean better.
I suppose I could try to gather all the available info into a giant spreadsheet, but the fact that about half the ROMs link out to a feature list is slightly discouraging. I think dutty's list of registry hacks ends in '.. and a bunch of other stuff I forgot', which is TERRIBLY discouraging (when trying to compare features).
Anyway, sorry if I'm rambling on here. Please don't take anything I'm saying as judgemental, I'm sort of thinking out loud trying to decide how best to proceed.
Say, has anybody considered building a CVS tree of sorts? I don't suppose you could have actual CODE stored in a repository without violating some sort of copyright or reverse engineering crap.. but a list of known code changes and etc. would seem to be a good idea. Since neither MS nor HTC has stepped up to the plate over the years, due to corporate greed, some sort of XDA-Dev code change tracking system seems like 'the last best hope' to get a decent OS. Ever.
That's why I'm jumping ship to try out the G1 after this. I don't believe MS will ever invest the effort to give us a 'business class' reliable bug free solution. ..let alone one that's innovative or even exceptional. They're style would lead me to expect them to wait till we have 800mhz handhelds, then 'patch' over top of everything they don't like to make it appear to behave better. ..and of course they would deem it necessary to add another programming layer to the OS to 'increase functionality' (read: bog down the OS).
Yup.. I'm definitely babbling now, so I'll just cut myself short.
I guess my bottom line questions are, Is there a more complete list of ROMs anywhere I should be using? ..or one which already compares all the features, so I don't have to?
Better yet, Is there a ROM build specifically to fit what I'm looking for? I seem to recall Alex's were built somewhat similar, but the newest one is quite old now. Hmm.. there is no Windows Mobile revision list is there? I have no way of knowing which older versions would be good, and when bug patches were introduced and etc.
Oh well, guess there's nothing to do but dive in head first and start putting together the best feature list I can with what resources I have.
Thanks for any help! ..and if you read this whole thing, thanks for putting up with my rambling, lol.
Crogon said:
I guess my bottom line questions are, Is there a more complete list of ROMs anywhere I should be using? ..or one which already compares all the features, so I don't have to?
Click to expand...
Click to collapse
I've never seen one and I don't believe one exists. You'll just have to do your own research.
Crogon said:
I guess I stated that incorrectly. Sorry!!
Actually I DO want a custom 'Cooked' ROM. My main purpose of reflashing the ROM is to get rid of all known bugs and bloatware. So I WANT all the custom registry hacks and patches to make everything run smoothly. I want the hacked video drivers (as they appear to currently be stable) and etc..
SO.. I'm looking for:
1) 6.1 OS with fast drivers and all known hacks and patches to have as few bugs as possible. UNLESS 6.1 has introduced some known bugs that can't be fixed (wouldn't surprise me with an MS product). IF there's a bug free FASTER version 5 OS, that will run on the Tilt, I'll be happy with that. One time I installed Win95 on a 1.6Ghz T-bird. Power on to fully loaded desktop was like 2 seconds flat.
2) bloatware removed so as to free up space, and I assume cleaning crap out of the registry wouldn't hurt with speed. Is there a system cache, and would it be beneficial to move it to the SD card? I've read that moving the IE cache to the SD card is asking for trouble, not sure that there's a concensus on that or if it's just opinion though.
OK.. that's going to get confusing. Scratch that and start over:
1) All known bugs hacked or patched.
2) All known speed enhancements (that don't compromise system integrity).
3) Rip out MS (or HTC ..or both?) crapware that COULD be replaced with faster / more functional counterparts.
4) Optional: pre-installed or at least packaged (cab?) applications to enhance functionality. My priority in applications is utility enhancement. Example: I can download 200 Flash / Java / MAME games to the SIM card some day if I get bored, don't need it in the OS. However, if there's a remedial photo editing utility that will allow me to edit my pics before I upload them somewhere, I want it.
I did manage to stumble across a wiki page last night: http://wiki.xda-developers.com/index.php?pagename=Kaiser_Cooked_ROMs
32 Developers and countless ROMs without any comparison isn't much help though. Can I assume all current ROMs are posted there?
Browsing through them, I recall that Alex's ROMs used to be the last word in ROMs, apparently dutty's were until he switched gears. HyperDragon seems to be terribly popular at the moment, but popular doesn't mean better.
I suppose I could try to gather all the available info into a giant spreadsheet, but the fact that about half the ROMs link out to a feature list is slightly discouraging. I think dutty's list of registry hacks ends in '.. and a bunch of other stuff I forgot', which is TERRIBLY discouraging (when trying to compare features).
Anyway, sorry if I'm rambling on here. Please don't take anything I'm saying as judgemental, I'm sort of thinking out loud trying to decide how best to proceed.
Say, has anybody considered building a CVS tree of sorts? I don't suppose you could have actual CODE stored in a repository without violating some sort of copyright or reverse engineering crap.. but a list of known code changes and etc. would seem to be a good idea. Since neither MS nor HTC has stepped up to the plate over the years, due to corporate greed, some sort of XDA-Dev code change tracking system seems like 'the last best hope' to get a decent OS. Ever.
That's why I'm jumping ship to try out the G1 after this. I don't believe MS will ever invest the effort to give us a 'business class' reliable bug free solution. ..let alone one that's innovative or even exceptional. They're style would lead me to expect them to wait till we have 800mhz handhelds, then 'patch' over top of everything they don't like to make it appear to behave better. ..and of course they would deem it necessary to add another programming layer to the OS to 'increase functionality' (read: bog down the OS).
Yup.. I'm definitely babbling now, so I'll just cut myself short.
I guess my bottom line questions are, Is there a more complete list of ROMs anywhere I should be using? ..or one which already compares all the features, so I don't have to?
Better yet, Is there a ROM build specifically to fit what I'm looking for? I seem to recall Alex's were built somewhat similar, but the newest one is quite old now. Hmm.. there is no Windows Mobile revision list is there? I have no way of knowing which older versions would be good, and when bug patches were introduced and etc.
Oh well, guess there's nothing to do but dive in head first and start putting together the best feature list I can with what resources I have.
Thanks for any help! ..and if you read this whole thing, thanks for putting up with my rambling, lol.
Click to expand...
Click to collapse
You have to spend some time and TRY each ROM and see which one is suited for you.
Again, READ and spend time.
Read WIKI especially.
There is no 100% perfect ROM even if it is official one.
Crogon said:
I guess my bottom line questions are, Is there a more complete list of ROMs anywhere I should be using?
Click to expand...
Click to collapse
http://wiki.xda-developers.com/index.php?pagename=Kaiser_Cooked_ROMs
If you want a newest list, you are always welcome to Update the wiki
I'm heading for the aspirin bottle just now. I spent like 3 hours reformatting the info on the wiki page into a spreadsheet.. when I discovered that some of the authors are still releasing, but it's not on the list!
AAHHH!!
So basically, A full up to date list is needed. Let alone version comparisons or features and bug fix lists.
Good grief.
No wonder most people opt to install ROMs randomly till they happen across one they like.
.. I think I'll make a new wiki page eventually. Something along the lines of a Kaiser ROM Feature Comparison page.
Do I get a XDA-Dev decoder ring if I actually finish it? lol
ROM modders/developers!
I'm the developer behind ROM Updater. It's meant to be an universal ROM updater (which means, it doesn't really care if you're on CyanogenMod or you're on the "whitelist"-free of ROM Manager). There is even a PHP script (on the website) which will automatically create incremental updates, cool feature of my app which lets both you and users save a lot of bandwidth. Please consider "adopting" it, it's free ^^
elegos said:
ROM modders/developers!
I'm the developer behind ROM Updater. It's meant to be an universal ROM updater (which means, it doesn't really care if you're on CyanogenMod or you're on the "whitelist"-free of ROM Manager). There is even a PHP script (on the website) which will automatically create incremental updates, cool feature of my app which lets both you and users save a lot of bandwidth. Please consider "adopting" it, it's free ^^
Click to expand...
Click to collapse
Nice work Elegos
Fantastic, consider me a supporter.
I think u have delivered it pretty well
Update: I've released incremental.jar and relative sources. Go to the website and check
New in version 1.8 (from version 1.7):
- Tried to fix a Null exception error, received via Market (thanks for reporting!) (please test)
- Added incremental.php and incremental.jar (plus sources) in the git repository to easily create incremental updates
- Moved common variables in a singleton (SharedData class) and more comments for easier understanding of the code and less variables around
PLEASE NOTE:
You don't have to mess up with the ROM name anymore, the program will check for the ro.build.display.id (MOD name) and ro.build.version.incremental (!!!INTEGER!!! version number), as well as ro.product.model (for future releases, in our case be sure is "Nexus One"). The repository main.json file has a new variable, "model" which is, indeed, the same of ro.product.model. Future versions of the app will make impossible to download updates not for your phone.
DEVELOPERS:
You have no excuses now ! I've talked with some other modders who say, for example, their updates are changing rather all the files, and I say you it's not true. Making some tests I saw that using incremental updates make the update 50~75% smaller, even with MIUI weekly releases. This means "bye bye" to the bandwidth problems, both for hosters and users.
Just added your page as my favorite. Will study and use it later, hehe ,need some time to know about it~~~~
So how do I set up repository for. CM7 nightlies? Do I have to enter it manually?
Sent from my Nexus One using XDA App
I'll give it a go. I have been using ROM Manager and it works very well but I was getting concerned with the bandwidth used for the CM7 nighties.
This does support CM7 nighties right?
Also, what about getting notifications when there is a new build for ClockworkMod Recovery and backup/restore options for ROMs that I keep on my phone?
Wow, as a themer, I would have to say that the idea behind this is amazing. I would love to see it adopted by everyone. I would like to be able to see what exactly has changed between updates, it would save me a lot of time personally. I commend you for your work on this. Woot
@apratomo: you need someone who sets up a CM7 nightly repo. I can't, as it would mean I should support every ROM out there, and my bandwidth is limited (I can host one ROM if you want, not 1000 ). By the way you should edit the build.prop file in order to edit the incremental value and make sure the ROM name is allways the same (display.id).
@pfran42: it supports any ROM you want, this is why I made it
It actually don't check for new recovery images, as it relies on external repositories only, I may create a different application for that though. As of backup/restore, it currently has an option to backup the current ROM wherever you want (see options). When I discover how to restore a nandroid backup via command line, I'll add that feature too.
This is a great idea, however adoption may be slow. Even though its an AWESOME idea, it may be a good idea for you host a popular ROM elegos to get the ball rolling. I'd hate to see this die...
Ok so I have to launch a poll. Problem is that:
1. In the generic Android Development forums (where this really thread should stay) is overcrowed with posts, most of them are just publicity for apps on the market.
2. I'd love to have the attention of all the android people to partecipate to the poll. Of course I MAY create a CM7 nightly repo, but it would mean daily work for me (and a lot of space on my host).
I'm working on a system that should keep a list of repositories automatically updated every time you download a ROM with the app (accepting to send anonymous data). It's ready in the git repository, I'm waiting to push it live 'cause I want to create an interface to grab that data too (a sort of list ordered by phone model).
I think that just for starting I'd love to host a Nexus One Gingerbread AOSP, just like MicroMod777's one (TBH I already have that repo online, but it's frozen at version 20 as MicroMod is focusing on CM 7 custom builds, which I dislike for its too many customizations (both CM itself and MicroMod's)). Alternatively an AOSP 2.3 with no apparent changes (i.e. maybe CM with standard launcher). Any idea?
Sometimes you just have to prove how good your ideas are, because people are lazy... good luck my friend.
Sounds interesting.
I'm going to release a "major" update: all the times a user downloads a ROM and accepted to send anonymous data, the repository, ROM name & version and phone model will be sent to a database, which will return back a list of repositories directly in the settings menu!
I've released version 1.9 and made a Enomther Nexus One repository. Enjoy!
Version 1.9.1
- Fixed an untranslated italian string
- Fixed the import of a repository URL via the repositories list (new line at end of repository)
- Made the application more solid when there are connectivity problems / no internet available (no crash anymore)
awesome work!!
have tagged the link shall go thru it...gr8 job elegos ..!! ..PeacE
Awesome ^-^