Database Info

The beginnings of the New Kitchen

Hi all,
Screen shoot of the beginnings of the new Kitchen interface.
There is still a great deal of work to do on it and I have a couple of people about to test and give some feedback and ideas.
Please feel free to post some ideas on this thread as to what usefull functionality could be added to it but no silly ideas please.
At the moment it is capable of building you four types of Rom, Vanilla, Business, Full Flavour and Custom (allowing you to select which OEMs to include) All you have to do is select your build type (and the OEMs you want added if you select Custom) then click the build button.
More functionality is being added and details will be added to this post as and when they become available
Regards,
Beast

Main point: whats working and what not working?

Hi beast0898,
Nicxe interface ! Perhaps too easy to use
I think this new kictchen will be release when the videocall will be 100% Fonctionnal
Nice work!

Is there any funtion where i can add extra oems other than given in your application (meaning from my own softwares)?

OEMs
satanisme said:
Is there any funtion where i can add extra oems other than given in your application (meaning from my own softwares)?
Click to expand...
Click to collapse
The current design of the OEMs plugin would require two modifications to add an OEM to the library.
One you must CAB the existing OEM Dir (including it's Dir name ) and two modify a text file OEMs.txt in the root of the Kitchen Dir.
The OEMs.txt file contains a list of CAB Compressed OEMs, which are extracted to the OEM folder when selected in the Kitchen. So adding your own OEMs is simple.
Cheers
Beast

fla242 said:
Hi beast0898,
Nicxe interface ! Perhaps too easy to use
I think this new kictchen will be release when the videocall will be 100% Fonctionnal
Nice work!
Click to expand...
Click to collapse
Hi,
A lot of work has been done on VideoCall and it is still not 100% functional.
I am not sure, we will probably release the Kitchen shortly, maybe a month or so after some BETA testing.
The idea is to make it very simple.
So many people want different apps and utils that I thought a simple interface with a "One Click" Build function would make using Rom kitchens more appealing to new comers and sceptics.
Of course I'll have a disclaimer to indemnify myslef from any damage caused by it's use!
Cheers,
Beast

kdskamal said:
Main point: whats working and what not working?
Click to expand...
Click to collapse
Everything is working, but I wish to add more functionality and have Rom bug fixes to sort out and BETA testing before releassing this.
This will be released as a complete Kitchen, we are not just releasing the front end to plugin to existing Kitchens (although it will if you wish) and we are hoping to cram in as many OEMs bug fixes and tweaks as possible, so the result is a decent simple to use Kitchen and a fast stable, reliable WM6 Rom to boot(No pun intended)
Cheers,
Beast

beast0898 said:
The idea is to make it very simple.
So many people want different apps and utils that I thought a simple interface with a "One Click" Build function would make using Rom kitchens more appealing to new comers and sceptics.
Click to expand...
Click to collapse
It's difficult to be easier, but probably easier than an "One Click" Build function I just can imagine a "Drag and drop" Build function without needing to change the text file OEMs.txt in the root of the Kitchen Dir.

Hi Beast,
Better, release an alpha so that people practically can realize about which feature he is missing or any bugs...etc...etc.
///Ranju
beast0898 said:
Everything is working, but I wish to add more functionality and have Rom bug fixes to sort out and BETA testing before releassing this.
This will be released as a complete Kitchen, we are not just releasing the front end to plugin to existing Kitchens (although it will if you wish) and we are hoping to cram in as many OEMs bug fixes and tweaks as possible, so the result is a decent simple to use Kitchen and a fast stable, reliable WM6 Rom to boot(No pun intended)
Cheers,
Beast
Click to expand...
Click to collapse

better to be engaged in a new build ... few who need kitchen. even in a form

mo3ulla said:
better to be engaged in a new build ... few who need kitchen. even in a form
Click to expand...
Click to collapse
I totally agree. With a new kitchen and ROM, even if they were alpha, we could track some eventual bugs and make some suggestions.
As you said a lot of work has been done and VideoCall still isn't 100% functional, therefore it seems to be difficult to estimate how long it takes to solve this VC issue...

Can you use for this project helmi kitchen rom? It was perfect, no bug with wi-fi, no bug with mms, no bug with email etc.

Kitchen update suspended for now
Hi all,
Laurentius and I have decided to release an updated Rom with bugfixes for now, so work on the new Kitchen will be delayed for a bit.
Thanks to those who were going to Alpha test, I'll get it over to you guys as soon as I can, maybe a week or two.
Cheers,
Beast

Linux Port for HTC Vox

Hi!
Since last week, I've been working on an usable kernel for the HTC Vox. I guess you've already looked at this post: http://forum.xda-developers.com/showthread.php?t=368014&page=5
More or less, I have a working kernel. I've tested some images against the modified kernel, and both Gpe and Opie get to the welcome screen (without getting stucked). Nothing is really usable, as they're not even compiled for this specific platform (cannot get to compile opie for arm by myself... yet), but as a base, it's not bad at all.
As I've seen on my previous post, there's people interested on this (3300 views make me believe that), what I would want to know is, are there more developers interested on building a linux port for the Vox? Testers will be needed also, but later, when we get to something useful for testing
If you're interested, reply!

Cannot help u develop anything here, but would be a willing tester for it... thoroughly

I'd love to help, but I'm in the middle of moving to a new place and won't have internet most of the time next 2 weeks.
Do you have a Wiki or other place for collaberating? SourceForge perhaps?
I do have a wiki, but upload is no faster than around 80kB/s

In case you haven't seen it, you have a new build of the kernel on the other post, along with links and a little manual to start a graphic environment on the vox.
@barth666, @StefanHamminga
I've been thinking about it, and... I don't know what to do I mean, I think Sourceforge is the best place to dump it all, and it gives us a wiki too. On the other side, here is the xanadux wiki, and maybe it would be a good idea to let sourceforge host the files, and leave the wiki in here with other HTC phones... what do you think?
Oh! For GPIO dumping, the only thing I've seen working is the linwizard project's Haret_Omap.exe (in case you want to try to guess where the damned keys are )
PS: Anyone has an HTC Tornado? I'd love to know if the tornado kernel makes the leds and vibrator flash, I can't find where they are!

biktor_gj said:
PS: Anyone has an HTC Tornado? I'd love to know if the tornado kernel makes the leds and vibrator flash, I can't find where they are!
Click to expand...
Click to collapse
I have a tornado (and vox and wings), so tell me what to test

I know from the ml_iPod wiki (I am the admin) that SourceForge is really slow and the Php and Sql versions are old, in case you want to set up something like MediaWiki! You might want to try http://code.google.com/ , it has a built in Wiki and you can host files!
Just a suggestion
Keep up the good work
EDIT: I could even set one up, if you want, but I am not into coding at all!

Hi! Sorry for the delay, but I'm having lots of work this week and I've been unable to keep on with this...
@Walram: On the following days I'll try to build a kernel for you, wich should put all the lights on and makes the phone vibrate until you take the battery out Obviously just for testing, it shouldn't break anything, but I need to know if the originally-made-for-the-tornado vibrator and led drivers actually work on the tornado... Thanks!
@Frauhottelmann
Didn't know that google gave that service too! will look at it this weekend and post back when I have something done with this.. thanks for the feedback!

walram said:
I have a tornado (and vox and wings), so tell me what to test
Click to expand...
Click to collapse
Hi!
Ok, here's what I want you to try. If you haven't downloaded it yet, download the Linux Test Image:
http://rapidshare.com/files/93938763/test.zip.html
Then, download the kernel for the tornado:
http://rapidshare.com/files/96145010/kernel_tornado_driver.tar.gz.html
Dump the contents of the first file to the memory card, and then overwrite the file "zImage", with the one from the second link. Run haret, and hit "Run".
It should, at least, boot. If it doesn't, tell me where it gets frozen (could be that you only se some dots on the screen, whatever appears, just tell me )
If it boots, don't stop looking at the leds (charge/bluetooth leds mainly), they should, at least, flash -theorically they should stay on all the time-. It also should vibrate, at least for a quarter of second
I just need to know what it actually does!
Thanks!

So what about a dev-page? Then you don't need to upload it to Rapidshare and you can see the progress better!

Hi frauhottelmann,
I'm going to tell you the truth. I think it would be better if it's you who admins a site for this project than if I do, for various reasons:
1. I started all this thing, but I'm no owner of anything, by now I just hacked four things to make this phone boot a kernel, but no more.
2. I've seen your work at the ml_ipod sourceforge page, and think it's usable, clean, and nice, and I think that's exactly what we would need (even if it's a little slow just as you stated in your previous post). I could make the graphics for the web (I'm quite decent at photoshop), but I have never built a wiki, or a project anywhere else, and I don't know a sh** about it, so that would be another big thing to learn, and for now, I gotta learn more about the linux kernel, and that itself it's huge.
3. I don't think I can handle work, classes, building patches, kernels and bootstrap images and administrate a site, it feels like too much for me
Conclussion? I think it's better to let people do what does better, and I'm quite sure you'll do it better than I, so if you want, it's all yours
PS: In any case, we will need a name for the project, any suggestions?

What I have heard from the ml_iPod developers is that upload to SF is not a nice process either. I still think Google code is better, although it's not as customizable as SF.net. But we could also set up a page on Googlepages (pages.google.com) and then point to the Google code site with the Wiki and downloads!

I can offer my technical know-how (SPL, GPIOs, etc.)
Since I have little time you should ask me precise questions for which I can try to find the answers.

Sorry for the delay...
frauhottelmann said:
What I have heard from the ml_iPod developers is that upload to SF is not a nice process either. I still think Google code is better, although it's not as customizable as SF.net. But we could also set up a page on Googlepages (pages.google.com) and then point to the Google code site with the Wiki and downloads!
Click to expand...
Click to collapse
So we can start using google code, and stick with it if it goes well. We can always change the hosting if something goes wrong! About the wiki, the easiest thing is start with google code too, and simply link the xda wiki to it...

i can't code, but i can keep you company maybe
i am here if help is nedeed

But what name do we want to use?
Linux for Vox?

LinVox !
how does that sound ?
just kidding
waiting to get linux running on my vox....

But what name do we want to use?
Click to expand...
Click to collapse
Hooked on Vonix!

vonix sounds ok
can also try "Mobile TUX"

wow
this is an incredible news ! linux on the Vox !
I'd love to flash mine with a movibuntu distro =)

How do you guys feel about splitting the project up in several subprojects?
Like:
Kernel and driver work: TI OMAP HTC Vox board patch and perhaps drivers
Base system: minimal rootfs and toolkit to utilize all Vox functionality
Usability: GUI and (for instance) Android support
This would also enable us to share the base system & usability work with other 'linux on smartphone' and embedded projects.
I do have a suggestion for the base system:
www.emdebian.org
Very up to date build toolchain for arm (GCC 4.x toolchains) and you can have apt support on the base rom. This would allow access to a huge amount of packages that can be used with relatively little effort. Others I've checked out are the new mobile ubuntu (system requirements way to high), MontaVista (severe lack of proper documentation to get up to speed quickly), uClinux (uses ulibc instead of the faster full fledged one, in my opinion we'd better trade some storage for more speed) and some others I can't remember now...
PS. I've got internet at my new place and I've recovered my bricked wizard from the 'spare electronics bin', so finally I can spend some more time on this

ROM Release Standartization

First and foremost, my hats (the whole rack of 'em) off to all the chefs in their respective kitchens. I've personally been a silent, yet happy customer for quite some time, and have been checking the forum daily for the next flash.
However, I've found that different ROMs will, obviously, have their list of capabilities and limits. Some support SIP better than others, some can't run iGo, etc. Mostly I flash, then find out during my installations, etc., and by that time I'm too lazy to flash back and just live with what I have. I would probably not flash ROMs that didn't support iGo and SIP if I knew that up front.
Having that in mind, I thought we could (as a group of continous beta testers and their respective gurus) try to formulate what would be a "check-list" for ROM releases, thus allowing the newbies (that don't know what to expect) and the old bees (buzzing along from ROM to ROM) to pick the right ROM flavor.
An example would be:
ROM Details
=========
ROM Name / Version: xxxx (Dutty's ..., Schap's ..., etc.)
CE Version: xxxx
Radio Versions Supported: xxxx ( So we know what we should have before flashing )
Based on: HTC WWE Release xxx (So we know if we got the new "hardware acceleration, etc")
Compatability
=========
SIP: [Not/Is] Supported, configured by ...
Skype: [Not/Is] Supported
iGo v7: Works out of the box / Requires removal of HTC Home
iGo v8: Not Supported
etc.
Thoughts about what this should include?
- SiteLister

Well I'm gonna jump on this first since chances are others won't be very nice about this thread
Not that I think your idea is a bad one, but to be honest most cooks already provide this information when they release a ROM.
If application compatibility isn't listed then the first 20 posts will bring it out....
If what you are asking is to compile a whole list of all these ROMs in one place. OK, good idea...but no one is going to do it for you.
If you like the idea...do it youself, or at least make a good start. Putting a post out like this is more likely to draw animosity since you are asking others to provide information that has been put out there numerous times. Good idea or not, you should make the initial effort and if you build something nice, people will contribut and thank you. Otherwise, they will just flame...
In addition, the Wiki would be the best place to do this.

not to say that this is a bad idea but there is one major flaw with the idea, most chefs cook for themselves and then release. with that said most of the chefs do not sit and try every possible application that can be put on your Kaiser, if you want to know what roms work with what applications and you also want to be the first to flash it and have the latest then you just have to try it for yourself. if you don't mind waiting you can wait a few days for the members that do use the programs you use to see if they say it works. i personally like to take a rom cooked by a chef, dump it and recook it for myself with the cabs my UC would usually install into the rom where i want them to be. sorry if this seems like a **** response but as far as i can see there is no way for the chefs to tell you what does and doesn't work and that's why we have threads after the rom release for people to tell others what does and doesn't work.

tubaking182 said:
not to say that this is a bad idea but there is one major flaw with the idea, most chefs cook for themselves and then release. with that said most of the chefs do not sit and try every possible application that can be put on your Kaiser, if you want to know what roms work with what applications and you also want to be the first to flash it and have the latest then you just have to try it for yourself. if you don't mind waiting you can wait a few days for the members that do use the programs you use to see if they say it works. i personally like to take a rom cooked by a chef, dump it and recook it for myself with the cabs my UC would usually install into the rom where i want them to be. sorry if this seems like a **** response but as far as i can see there is no way for the chefs to tell you what does and doesn't work and that's why we have threads after the rom release for people to tell others what does and doesn't work.
Click to expand...
Click to collapse
Most of this is true... however I don't think he is asking the chef's to do anything different, it just looks like he wants an encyclopedic reference of all ROMs and their features. Again, good idea...but just do it if you want it. Others will contribute if they find it worthy, if they don't...then oh well, at least you learned for yourself.

sitelister said:
An example would be:
ROM Details
=========
ROM Name / Version: xxxx (Dutty's ..., Schap's ..., etc.)
CE Version: xxxx
Radio Versions Supported: xxxx ( So we know what we should have before flashing )
Based on: HTC WWE Release xxx (So we know if we got the new "hardware acceleration, etc")
Click to expand...
Click to collapse
Im hip to this.. well mainly must of us do that already in one form or another just not in that pretty format
sitelister said:
Compatability
=========
SIP: [Not/Is] Supported, configured by ...
Skype: [Not/Is] Supported
iGo v7: Works out of the box / Requires removal of HTC Home
iGo v8: Not Supported
Click to expand...
Click to collapse
Not a bad idea, however this would require us to manually test a billion pieces of software in order before giving it out.
Now how about a better idea, someone should start a kaiser wiki page on bug fixes, etc... In all of my beta roms when someone points out an issue i will ask them to provide a link for a fix if i dont know it already, i actually do this for a couple of reasons.
1. it helps promote interactivity between forum members and helps to get people communicating, etc. This also helps to hinder the n00b factor and provides links for other people.
2. it provides me reference point, before i release each beta i go through the previous threads and make sure that i have fixed everything that was broken prior.

sitelister said:
First and foremost, my hats (the whole rack of 'em) off to all the chefs in their respective kitchens. I've personally been a silent, yet happy customer for quite some time, and have been checking the forum daily for the next flash.
However, I've found that different ROMs will, obviously, have their list of capabilities and limits. Some support SIP better than others, some can't run iGo, etc. Mostly I flash, then find out during my installations, etc., and by that time I'm too lazy to flash back and just live with what I have. I would probably not flash ROMs that didn't support iGo and SIP if I knew that up front.
Having that in mind, I thought we could (as a group of continous beta testers and their respective gurus) try to formulate what would be a "check-list" for ROM releases, thus allowing the newbies (that don't know what to expect) and the old bees (buzzing along from ROM to ROM) to pick the right ROM flavor.
An example would be:
ROM Details
=========
ROM Name / Version: xxxx (Dutty's ..., Schap's ..., etc.)
CE Version: xxxx
Radio Versions Supported: xxxx ( So we know what we should have before flashing )
Based on: HTC WWE Release xxx (So we know if we got the new "hardware acceleration, etc")
Compatability
=========
SIP: [Not/Is] Supported, configured by ...
Skype: [Not/Is] Supported
iGo v7: Works out of the box / Requires removal of HTC Home
iGo v8: Not Supported
etc.
Thoughts about what this should include?
- SiteLister
Click to expand...
Click to collapse
Ah configuration management then maybe ISO accreditation................
Flash, enjoy, read, explore, reflash again and again.
Remember this isn't someones job its their hobby that they share.
Remember to say thankyou every now and then.
Thanks

usually it's the base rom that isn't compatible with the software. Most chefs just take the base rom and strip it out to remove bloated software and add in their own personal software. There are some chefs that go out of their way and add in the necessary dlls and files to make certain software work, but it is really difficult for chefs to do such a thing. Maybe a specific thread for each software to work on a particular rom would be helpful.

Thanks for your replies, y'all.
To be clear (and I can see where I may have not been there), I was fishing for interest. The next thing up would be to set it up in one format or another (Wiki, whatever) - I'm just not usually for building something before there is a market for it. When I said "we could" I meant it would be something that people could contribute to (myself, amongst others), in a format better appealing than, or more appropriate than those 105-long pages mostly containing praises, bashes, and little information (there's quite the picking to do when you're actually trying to decypher what a ROM's capabilities are).
If there is an interest, I'd be happy to put in the initial effort, but I'm also fishing for content requirements - that is, I've put forward some kind of basic format, but what other information would cause people to make a judgement? what kind of apps are important, etc.
Quick replies:
bengalih - I'm hanging on the fact that people are, inherently, nice. Hopefully at a higher ratio in this forum .
tubaking - Agreed, most users will give the feedback back to the cook or the forum. I'm actually not asking anyone to do more work than they already are. My thoughts are that the feedback is sometimes lost in (or hard to gather from) the forum. Fixes are also all over the place (for example - the iGo version compatability thread). I believe it's because the tool is incorrect (discussions).
bengalih - Agreed.
shogunmark - Sounds good. Wiki then as the solution? - Possibly have one page per release, and a summary in a top-level page that contains a comparative table?
halon - I'm sure I don't say it enough --> THANKS!
thomassster - I believe that the concept is good, but you're back to trying to nitpick for each application you're interested in, in hopes that people organize it in that fashion. Additionally, you're still back into reading a bunch of acknowledgments, accreditations and bashes (which take up a good chunk of the forum content).
... Thoughts?

inconsistencies in "support"
This is a good idea (or a bugzilla-type thread/wiki) and as ShogunMark stated in his first post, the first 20 posts (pages!) bring out the main probs. the only issue there is that some posters inevitably state that something or everything is working for them (perfectly) out of the box, while others experience major dysfunction, creating a confusing morass of info.
How bout a survey page - everyone votes for what works or not?
Cheers-

Yes this sounds like a good idea for someone as a side project to document in the wiki. But really most of this information can be found in the first 20 to 30 posts. And most roms, are quickly superceded by another new version. So if you want to do it, I am sure someone will read it. But asking the chef's things like does IGO work or Skype, If they don't use them they should not be expected to test them...IGO who cares if it works or not, only the people that use it..not everyone..
SO if you want to create a wiki page with this info; go ahead and do it and maybe someone will read it...Maybe good idea, but it will quickly be outdated.

List of Cooked 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

new binder driver helps your phone run smoother

Hi guys,
I've written a completely new Android binder driver (for IPC), which is targeted to solve some fundamental issues in the existing driver. One main improvement is to make concurrent IPC calls possible. Some background info can be found in my earlier post on Android kernel group:
http: slash slash groups.google.com/group/android-kernel/browse_thread/thread/c57874670e4decb1
(oops external urls are not allowed for new users
There weren't many people interested due to low volume of the group. Now that I have completed the first version, which is back compatible with the existing driver, and fixed a few bugs. I've tested on the ICS emulator and my phone U8150 Froyo. It seems to be running quite well, but I want to see how it runs on other Android devices while I'm getting my new phone. Test results, bug/issue reports, and of course community comments will be very welcomed, which are important for me to determine how the code should further move on.
Although not proven, I'm expecting not only those dual core phones, but single core ones will get an overall smoother response in various parts of the system.
Okay if this still somehow interests you, you can find my project on github
https: slash slash github.com/rong1129/android-binder-ipc
and just dive into the release directory, use the latest version (0.4 so far) to patch your kernel source tree, then upload the new kernel image to your device and see whether it works for you.
Note this is still an early release and has very limited tests so far. Please make sure you understand the risk before you hack your phone and always back up everything before you started. As other disclaims go, I'm not responsible for any damage may be caused by or related to using or in the process of using the driver
Lastly, happy hacking!
Cheers,
Rong

*subscribing to this thread*
Hi Rong,
thank you so much
our phones, tablets, etc.
can't have too much smoothness
I hope that I'll find some time within the next weeks to also give this a test on the Xoom and see whether it works (with ICS; Team Eos kernel)
there at least seem to be issues with ICS on the SGS (galaxys s1)
http://forum.xda-developers.com/showpost.php?p=23937103&postcount=2502

I found this thread . Is this driver the same on all android devices and roms? Or do you have to mod it for every single device/rom?