For those of you who know me and my benchmark thread in the Rhodium forum, this will be the same thing. The only difference is that I plan to redo all the benchmarks with my Leo instead. Seeing as this is the most powerful WM device available, it only seems right that I use that for the results.
I'm currently working on building everything and cooking it all. For now, here is a link to the original thread.
[PRJ] SYS Builds: What's the difference?
I'll be updating this thread throughout the week as I burn through the builds. They each take about thirty minutes to do, so don't expect them all to show up at once. This will likely take me about three or four weeks to complete. This time, I'll be using the detailed results for more accurate comparisons, however.
Before anyone asks, I have not yet done the new builds from DFT (29018 and up).
Hopefully this thread is more useful over here.
I'm putting up this thread because there is a good bit of questions that get asked about the speed difference between the SYS builds. While Microsoft and its partners don't give us a real breakdown of them, we can at least get results on which one is faster than the other. That is the purpose of this thread. If you have any relevant information for me to add to this, let me know. If I add your suggestion, I will, of course, credit you. This is relevant to pretty much all WM6 devices. I am using a 1024_Leo to do the benchmarks as this is the most powerful WM device that was released, which I also had access to. I'm following the same pattern from the benchmark thread HERE.
To start off, Da_G, a1d2catz, and Cotulla originally posted about the different builds. OndraSter posted to elaborate on a couple of the builds.
Branches of WM Development: Here is what all these different version numbers relate to, and a summary of their features.
212xx = AKU1, all builds leading up to and including WM 6.5
213xx = MOT motorola
214xx = ???
215xx = SAM samsung
216xx = HTC htc
217xx = COM1, continuing dev of 6.5.0.1 - 6.5.0.40
218xx = COM2, continuing dev of 6.5.0.50
219xx = MD, feature test branch, pretty much dead now. (unstable features are added here, this tree is based on COM1, so older base OS code, but the UI/UX code is newer)
22xxx = SEMC sony ericsson
*230xx = COM3, continuing development
*234xx = COM4, appears to be abandoned.
*235xx = COM5, more GUI changes here. New Outlook Interface.
*236xx = LG Electronics Branch
*24xxx = Possible HTC branch
*25xxx = SEMC - Sony Ericsson
*280xx, 282xx = WMD. This is a continuation of com3 from 23090. Most of the changes appear to be with IE
235xx is the only branch that has threaded email natively
290xx = Unknown branch
There was 219xx about half year ago, with numbers ending about 21936 (or maybe 45 or about that). It was test branch, where new features (like... supernew, something like previous 230xx where appeared huge softkeybar etc) were added. This branch was dead, just as looks 234xx now.
But, there was also COM2, with numbers 218xx. Well it reached its maximum, 21899. But instead of making new number line, MS/HTC chose to use already used 219xx. Here is where the mess comes from
The WM version numbers are as follows:
216xx = 6.5.3
219xx = 6.5.0
220xx = 6.5.3
231xx = 6.5.3
235xx = 6.5.5
236xx = 6.5.3
246xx = 6.5.3
250xx = 6.5.3
282xx = 6.5.3
290xx = 6.5.3
Click to expand...
Click to collapse
Updates:
19 April 2011: Thread begins
Results
I based these blank uncompressed ROMs on the latest shipped T-Mobile 6.5 ROM (3.14.531.1), disabled all ext packages, and swapped builds. I've listed all of the builds that I currently have. If you have one for me to test that's not on the list, send it my way as long as it's WVGA.
SYS builds being tested:
216xx: 21659, 21661, 21663, 21665, 21671, 21674, 21677, 21679, 21680, 21681, 21682, 21683, 21684, 21685, 21686, 21687, 21689, 21690
219xx: 21904, 21905, 21907, 21908, 21909, 21911, 21914, 21916
220xx: 22013, 22018, 22019, 22021, 22022, 22024, 22027, 22031, 22036, 22037, 22038, 22040, 22041, 22042, 22044, 22046, 22047
231xx: 23120, 23121, 23129, 23130, 23132, 23133, 23134, 23135, 23136, 23138, 23139, 23140, 23142, 23144, 23145, 23146, 23148, 23149, 23150, 23151, 23152
235xx: 23569
236xx: 23651, 23654, 23656, 23658, 23659, 23662, 23664, 23667, 23670, 23676, 23678, 23680, 23683, 23686, 23688, 23689, 23690, 23691, 23694, 23697, 23698, 23699
246xx: 24609, 24610, 24611, 24614, 24618, 24619, 24620, 24626, 24627, 24628, 24630, 24631, 24635
250xx: 25018, 25024, 25026, 25027, 25028
282xx: 28233, 28236, 28237, 28238, 28240, 28242, 28243, 28244, 28245
290xx: 29002, 29003, 29004, 29005, 29007, 29008, 29009, 29011, 29013, 29017, 29018
Problem builds:
These are builds I was either unable to import into my kitchen, or cook for various reasons:
22016, 21664, 23123, 23125, 23126, 23127, 23566, 23694
Reserved #2.
FAQ
When posting to this thread, please use proper English only, and do not use profanity.
You should not type like a high school girl, either. Leave the "plz," "sum1," and "u" back on the playground.
Ask for help like an adult and be treated like one.
1. What are these benchmarks for?
Basically this is just a measure of performance on different SYS builds to see which one is the fastest. These tests do not indicate which build is really “the best.” It is a measurement of speed on the process of copying files, reading directories, and playing video. To truly “test” a ROM, you need to spend a few days with it.
2. Which radio version are you using?
To the best of my knowledge, this has no affect on the results. However, my current radio version can be found in my sig. I do not change it for these tests.
3. Does a task29 before each flashing affect the results?
There are problems with "ghosting" in ROMs where residual data is left over from a previous ROM. To avoid this, I perform a task29 first. If you want to know more about task29, then visit that thread.
4. Are those benchmarks accurate?
I test the ROMs with SPBBenchmark once as it averages the results of 13 tests each. I use three rounds of OpenGL and use those results as it takes the highest result from there, which is what we want. An average in that category is useless as we want to know what the best result is for this, not the average. I run each Avatar trailer three times and take that average. Flash is pretty straightforward and kind of just for fun, so I only do one test. All of this means that the results may vary by a very small margin. If you don't believe my findings, you are always welcome to test yourself. Anything within a 1% margin of error is acceptable.
5. Why do you disable "Built-in applications (whole category)," "Arkaball frames per second," and "Copy 1 MB using memcpy" for SPB Benchmark on the blank builds?
They don't make a noticeable difference in the results. I could grab the *.xml results file from \My Documents, but it's not that big of a deal in the blank builds as they are just a stepping stone for chefs to see what they like and don't like. If you want to see the results, test them. I use them for custom ROMs because it makes sense to do so. People will interpret these results loosely, and it is better to be more accurate with them.
6. Why aren't you using Linpack?
Great question! I would if this were Android as there are current programs for it. The only one available for use on the WinCE platform is almost three years old at this point. Also, SPBBenchmark measures MFlops, so I don't really need it, do I?
7. Why don't you test battery life?
Battery life testing takes too long, plain and simple. When you flash a new ROM, getting the battery set properly takes about two or three cycles (drained to 10% and then charged to 100%) before it "settles." Even if I did nothing but play movies with the backlight and sound at max while downloading files via wifi and using Bluetooth file transfer, it would still take about an hour or so to drain the battery enough to charge it back again. You would need to drain and then charge AT LEAST once, preferably twice, before running a battery meter to test. This means I would be stuck on one ROM for hours before moving to the next one. My current set up allows for about 30-45 minutes per ROM to test. This is much more reasonable than 4 hours each, don't you think? If you decide to do test it yourself and want to share, then be my guest.
8. I didn't see you use xxxxx version of a build. Why is that?
I either don't have access to that build, or it isn't a WVGA build. If it is a WVGA build and I don't have it listed, send me a link, and I'll test it out.
9. Can I test the ROMs too?
Sure, why not? I won't use your results, though. There was a massive flame war in the aforementioned original thread that was partly fueled by other users posting results. I don't plan to start any nonsense here.
10. Would you mind testing a custom ROM for me?
YOU MUST GET THE CHEF'S PERMISSION FOR THEIR ROM'S RESULTS TO BE POSTED. I need them to PM me with an ok. I basically want it in writing. NOTE: Once a chef says it's ok to test, I will not remove them from the tests; make sure they understand this.
11. Why am I getting different results?
There are several little nuances that can influence the results in minor ways. If you're getting significantly different results than I am, then I'll look into it again. Keep in mind that using a different device than I am may affect the results as well. However, I will not use any other users' results without verifying them myself.
12. Some of this material looks familiar. Did you steal this?
Yes, basically I did. I figured I'd restart something similar for reasons I've mentioned as well as making it more Rhodium specific. Besides, the original poster, daeron.be, hasn't even logged on in a long time. His thread hasn't been updated since September of 2009 as well. I'm going to use most of their formatting and previous material to build on. If someone has a legitimate problem with this, then PM me.
13. I don't believe that you got "X" results with "X" ROM! I think it's WAY better than all the rest!
I don't care what you think. That isn't a question anyhow. I'm doing this for myself and sharing with you all. Either take it for what it's worth or do it yourself.
14. You didn't respond to my post. What gives?!
I have a life. I'm on XDA way more than I should be as it is. I will generally respond to questions and the like. If you just post to say "Good job" or "Thanks, man," don't expect me to respond. I might, just don't expect it. Just consider this answer here as a general "Thanks" and "You're welcome."
15. You're from New Orleans? What's it like?
People are wonderful; food is amazing; Mardi Gras rocks. Let's keep the thread on topic, please.
Reserved #4.
Would be interesting to see your results...
To continue, or not.... ?
Since it appears that we won't be getting anymore SYS updates to WM6.5, does anyone feel I should continue with this? I've got over 100 of these things cooked, but if WM is not reaching its EOL, then is there a point?
I leave it up to you guys. If anyone cares whether I redo these or not, I will, but if not, then I'm going to scrap the thread and return to the Rhodium one. There will be a poll at the top in a few minutes. Please take it when you see it.
EDIT: Poll is up.
Just voted and we can make this alive and hope to get new builds out from DFT (with the help of some friends .
Thanks.
I promise I'm not trying to spam or bump this thread or anything, but I kind of would like to see more votes about this. Doing all of these benchmarks and comparisons is REALLY tedious work. It takes a very long time to do and isn't much fun either. I do it for you guys. I just need to see that this would actually be a good idea to get started on before I redo every test that I have already done before. If I am fast about it, this will take me about 30 minutes for each build. multiply that times 128 builds will take me 64 hours to complete. That isn't including the time it takes to set up the spreadsheets and do comparisons and such.
Please give some feedback if you guys care whether I do this or not. This is a big undertaking for me to do if there aren't many people who it will benefit.
cajunflavoredbob said:
. If I am fast about it, this will take me about 30 minutes for each build. multiply that times 128 builds will take me 64 hours to complete. That isn't including the time it takes to set up the spreadsheets and do comparisons and such.
Click to expand...
Click to collapse
In order to save your time, I suggest that you could just redo the tests for the builds with best performance scores in every series among those builds you have tested. Of course, for those builds not yet tested, you could test one by one.
cheers_w said:
In order to save your time, I suggest that you could just redo the tests for the builds with best performance scores in every series among those builds you have tested. Of course, for those builds not yet tested, you could test one by one.
Click to expand...
Click to collapse
I would do that, but the ones I had already tested were on the Rhodium. I can't really use those to compare to the builds on the Leo. It would kind of be like comparing apples to oranges, as the saying goes. That's why I want to know if this is going to be helpful to anyone before I begin on it, since it's a very big project.
I hope Micro$oft will work on WM at least until this summer...and DFT team will help the community and share new builds, as they did until now.
I think maybe you could integrate the Rhodium benchmarks with latest build, and then choose only the most significant builds to benchmark with the Leo.
We can choose together criterions (the latest for each branch; latest+fastest?)
Putting all these informations together will create a really wonderful encyclopedia.
Monfro said:
I hope Micro$oft will work on WM at least until this summer...and DFT team will help the community and share new builds, as they did until now.
I think maybe you could integrate the Rhodium benchmarks with latest build, and then choose only the most significant builds to benchmark with the Leo.
We can choose together criterions (the latest for each branch; latest+fastest?)
Putting all these informations together will create a really wonderful encyclopedia.
Click to expand...
Click to collapse
Well, the trouble is that not all branches are that cut and dry. Some of them are all very close together in terms of results. The other thing is that when I did the Rhodium benchmarks, I left out some fields and rounded up the decimals. I would rather leave them in for more accurate results. This would force me to do all of the builds over again on the Leo. I don't mind doing that at all as long as this is actually going to benefit users. I'll check again on Monday and begin doing this then if their is enough interest.
I know its hard and tedious, but I can say at least that I am interested in the results.
I am at a point of choosing a xip for the next update for my rom, and this kind of research from you make likes much easier.
So whatever you do, I really appreciate whats you've done and hope o see more. At the very least, if dev of new xip is stopping, then once you are done you got it done for everybody for all time. Future cooks will have here to look when they need it.
bryanwieg said:
I know its hard and tedious, but I can say at least that I am interested in the results.
I am at a point of choosing a xip for the next update for my rom, and this kind of research from you make likes much easier.
So whatever you do, I really appreciate whats you've done and hope o see more. At the very least, if dev of new xip is stopping, then once you are done you got it done for everybody for all time. Future cooks will have here to look when they need it.
Click to expand...
Click to collapse
I'm glad to see people actually use these results, or at least they say they do. I will try to get on with the results, beginning with the 290xx branch this weekend. For those of you who followed my other thread in the Rhodium area, expect these benchmarks to be more detailed.
cajunflavoredbob said:
I'm glad to see people actually use these results, or at least they say they do. I will try to get on with the results, beginning with the 290xx branch this weekend. For those of you who followed my other thread in the Rhodium area, expect these benchmarks to be more detailed.
Click to expand...
Click to collapse
Thank you. I'll be watching. I partcularly appreciated your notes on each build. For example, some were slow in general, some were slow to open folders, others had smooth scrolling, etc.
That type of information is very helpful.
Small update
Sorry for taking so long with this. My Rhodium's keyboard died and had to be sent in for repairs. I have it back now, so I'm going to start benchmarking as soon as possible. I promise this isn't a dead thread. If you're wondering what my Rhodium has to do with me testing on my Leo, well, I can't test on the same device I use for business, now can I?
Related
Well I have been accused by some of not sharing some tweaks I used to get the results that I posted in a screenshot of a Benchmark in the benchmarking thread. http://forum.xda-developers.com/showpost.php?p=5333039&postcount=203
First of all let me say I share with any and everybody, unless I have good reason not to.
I was just testing some things I already suspected as was on our Blackstones. I never really intended to use these tweaks in one of my ROM's. After you read below you will understand why.
I will post all the things you need to get these benchmarks in the next couple of hours. But before I do I want to tell my feelings on this whole obsession with speeds and benchmarks.
[MY STORY]Most of us come from the Blackstone or Diamond so we were all faced with the same problems in trying to run software that was meant for 1gh processor on a device with half as much. It was more important for us to get the speed to have a smoother and quicker HTC Sense. That was then and this is now.
I'm sure I was just like all of you who were blown away with the speed of our HD2 compared to the blackstone or diamond. Now I for one was so pleased to see the HTC Sense running as it should that I felt like it was my birthday.
Now what I see going on here in the benchmark thread etc is a shame IMHO. Cooks sparring back and forth with other cooks and the tester. I understand we all have competitiveness in our nature. But to take it to this limit is unbelievable. Out of all the ROM's I have tried, I have not found one that was in any way slow or gave any feeling of sluggishness. We should all focus more on stability than on a benchmark that shows a few points higher and that is impossible for the user to tell the difference. There are some people who will stop at nothing to be on the top of a benchmark score (not meant at anyone but in general). I had the fastest WM 6.5 ROM's on the blackstone. I very rarely even benchmarked my own ROM as others were doing it and I concentrated on other things. But I didn't get caught up in the chase or race to the fastest.
In Summary I hope all cooks will continue to better there ROM's and make stability the number one concern. It is a shame in my opinion to release a ROM on this device that is not stable due to trying to improve speed.
[/MY STORY]
The rest will come in part 2 after I eat.
Now first let me explain again. I don't recommend using these. Which is why I'm not using them. They cause problems just as has been mentioned by Dutty and others. I posted a screenshot of a ROM I made just as a novelty with all the hooplaa going on in the benchmark thread. I never intended on using them. Later I was accused of not sharing them so here they are. If you want to use them go ahead but I will not as they will cause problems with outlook sync, notes etc. You will also not be able to use the new Manila 2.02 as the device will not boot with storage card. And other instabilities.
PART 2:
Ok for the OEXXIPKernel:
Remove the following:
bmui.nb0
zbmui.nb0
htcfsfilter.dll
For the MSXIPKernel:
Remove the following:
cachefilt.dll
fsreplxfilt.dll
hd.dll
mencfilt.dll
osaxst0.dll
Edit or use the boot.rgu attached
Edit the boot.ms.rgu and change the following: add a "-" sign to remove this key
[-HKEY_LOCAL_MACHINE\System\StorageManager\FATFS\Filters\ENCFilt]
"Dll"="mencfilt.dll"
"Order"=dword:5
Also remove this key from the rgu in MSXIPKernel: Add a ";"
;[HKEY_LOCAL_MACHINE\System\StorageManager\Filters\ENCFilt]
"EncryptByDefault"=dword:0
So that's it now I have publicly shared my so called secret tweaks so anyone can use. I hope this is the End of this and now I can go back to my work on my ROM. I didn't think it was worth sharing as it does not work without problems. Be warned I told you it will not work without problems.
Now that I have a clear head on this matter I'm going back to work on my ROM.
this person should be stopped from revealing any secrets.
Fully agree, so far I had no complains on speed.
Stability and battery are for me the most important points.
I cannot judge on the "secret" issue, but I do not understand why not sharing information and help therefore others to improve.
Best regards,
dingolino
bobsbbq said:
I will post all the things you need to get these benchmarks in the next couple of hours.
We should all focus more on stability than on a benchmark that shows a few points higher and that is impossible for the user to tell the difference.
Click to expand...
Click to collapse
I really don't see any effects on benchmark numbers and never did test any of my roms using any benchmark tools.
In my opinion what counts most if the device is stable and fast for user and higher numbers in benchmarks don't mean this. If the ROMs are good for everyday use who cares about numbers.
What are these magnificent secrets to be shared ???? I always did this question to myself and will do this question to you...are we clever than MS or HTC to remove XIP components to make the ROM faster?
What do you think that MS or HTC want their products to be slower than we do? No my friends they always want to have their products on top, thus if there are un-needed components in XIP or SYS I'm sure that HTC or MS would have removed them, as HTC is doing in HD2 (removing MS BT stack and some other components from MS SYS).
I hope to be clear on this point. I wanted just to share this because I've read all the posts and negative discussions on benchmarks thread between cookers but didn't want to post there. So guys continue to make your ROMs as everytime and forget about benchmark numbers...we need to collaborate between each other and not flame each other.
I don't know what bobsbbq is going to reveal, but I think those tweaks are no secrets, you can find them on the forum.
Well, maybe he has some secrets to reveal as well.
I'd love to see these tweaks and try them in my rom. I'm really interested to see if they make a difference in real world performance. If they don't, it will be something fun to try anyway
rofl @ " i had the fastest rom on the blackstone"..
i know lots of xip tweaks, i wonder which of the ones i found out and have shared amongsy the chefs wothout such a massive ego youre going to 'reveal'..
wondrr how many of these you understand what they do....
fwiw benchmarks are a worthless pile of crap mostly. the ones people seem to use all the time are based around a really old system, 2003. and are easy to beat with large file cache. which is not the way to have a fast responsive rom.
eagerly awaiting further posts, haven't had a decent laugh since kholks daily soap opera..
fards said:
rofl @ " i had the fastest rom on the blackstone"..
i know lots of xip tweaks, i wonder which of the ones i found out and have shared amongsy the chefs wothout such a massive ego youre going to 'reveal'..
wondrr how many of these you understand what they do....
fwiw benchmarks are a worthless pile of crap mostly. the ones people seem to use all the time are based around a really old system, 2003. and are easy to beat with large file cache. which is not the way to have a fast responsive rom.
eagerly awaiting further posts, haven't had a decent laugh since kholks daily soap opera..
Click to expand...
Click to collapse
I'm glad this is comical as this is exactly what it is to me. That why I'm posting it in such a way.
It's not a ego I stating exactly the opposite. But I did have the fastest 6.5 ROM's and not using any of these tweaks.
I agree about the benchmarks which is why I said what I did.
I'm sure some of these have been around I never said I invented them. I was just accused of not sharing them.
Fards I'm not as technical as you are, and not trying to be. I understand the general idea of what these do. But I'm not pretending I know it all as I don't.
Now to update with part 2.
I use some of the tweaks in my ROM (only those of which I'm sure that they don't reduce stability), but I'm not sure whether they make any difference in real world performance. Maybe a bit, cause my ROM is very fast
But anyway, if you use the forum search, you can find most (if not all) of those tweaks. I really wonder why some chefs make such a big deal of them and try to keep them secret. Isn't this community about improving our devices, which can only be done by working together?
Let's see if bobsbbq has any previously unknown tweaks to share, and whether they affect anything other than benchmark scores.
Updated Part 2. I can confirm these don't really add anything other than a number and loss of stability is a certainty.
Bob you did a right thing sharing your hardly tested "secret" knowledge with the community. Keep this spirit.
Same as Bob, I would advise to fellow cookers that it's not a good idea to mess with XIP, because side effects will happen and only numbers will change...nothing more, leave the things how MS and HTC has on XIP part and don't touch them.
bobsbbq said:
Updated Part 2. I can confirm these don't really add anything other than a number and loss of stability is a certainty.
Click to expand...
Click to collapse
Yep, exactly the tweaks I expected. Let me repeat the warning: Those tweaks will reduce the stability of your ROMs. That's not an assumption, that's for sure.
If you want to make good ROMs instead of just being the "benchmark king", then deal with them very very carefully. We all know the HD2 is increadibly fast without tweaks, thus stability should be the number one thing to take care of when making ROMs.
Thanks for clearing things up, Bob.
miri said:
Bob you did a right thing sharing your hardly tested "secret" knowledge with the community. Keep this spirit.
Same as Bob, I would advise to fellow cookers that it's not a good idea to mess with XIP, because side effects will happen and only numbers will change...nothing more, leave the things how MS and HTC has on XIP part and don't touch them.
Click to expand...
Click to collapse
Thanks Miri, some people just will not get it. You know I have shared all the time. And I feel it is the right thing to do as others have done for me.
I'm happy with my own little stable ROM now. Not sure if it is too stable or really bad? Several hundred downloads but no comments. I guess no comments are ok.
Yes it's like that
No comments means a stable thing
bobsbbq said:
Thanks Miri, some people just will not get it. You know I have shared all the time. And I feel it is the right thing to do as others have done for me.
I'm happy with my own little stable ROM now. Not sure if it is too stable or really bad? Several hundred downloads but no comments. I guess no comments are ok.
Click to expand...
Click to collapse
I want SPEED!!!!!!
If you want stability use stock rom.
Thanks for every rom cookier that bring us new levels of performance. HD2 are running near to 40% faster with cooked rom than with stock rom, and I am sure people can get more!
Believe me speed is not noticeable, but noticable are the lockups
Thiago Fialho said:
I wan't SPEED!!!!!!
If you wan't stability use stock rom.
Thanks for every rom cookier that bring us new levels of performance. HD2 are running near to 40% faster with cooked rom than with stock rom, and I am sure people can get more!
Click to expand...
Click to collapse
Yeah, so many downloads, but littele feedback... I guess people only comment when there's something wrong.
Again, thanks, there's really no benefit in keeping things secret. And the race for benchmarks scores only results in bad ROMs.
@Thiago Fialho
High benchmark scores don't mean high speed. A ROM may have high scores but be totally laggy. Because benchmarks can not measure that lag, and they can not measure stability. If your ROM locks up all the time but has high benchmark scores, would you call this a speedy ROM?
Certainly not.
Firstly (before my question) I'd like to thank everyone on here who shares or helps us all either with providing knowledge & experience or by providing ROM's (i.e. many hours of their time) and especially when I see some of the questions & demands that the various cooks face in their threads.
I cook my own ROM's so that my phone's (and a few friends) get exactly what they want tailored to their requests and try to stay with the latest stable OS / Manila version, other tweaks etc to get best performance and functionality.
Can I ask based on all of your experience which of these tweaks are actually "Safe" and which will cause instability - I'm going to do some testing anyway but advice is always taken ....
Thanks to Bob for opening this up.
Does anyone else want to add any further known XIP tweaks to the public domain with their experience of them ...
Thanks again to all who contribute.
Hi guys,
It's totally nonsense what you guys talk to my opinion.
If you patch XIP good in a appropiate way there's nothing wrong with it and it won't harm the rom at all.
Because you guys keep nagging about this subject but you all love to patch XIP and wanna be first in benchmark I'm realy not in the mood to talk to you
but you are forcing me in a certain way as I'm number one in the bench.
My rom is stable and fast as hell and no one can prove it isn't.
So swollow it and stop this grap, happy cooking
Grtz Leo
freyberry said:
Yep, exactly the tweaks I expected. Let me repeat the warning: Those tweaks will reduce the stability of your ROMs. That's not an assumption, that's for sure.
If you want to make good ROMs instead of just being the "benchmark king", then deal with them very very carefully. We all know the HD2 is increadibly fast without tweaks, thus stability should be the number one thing to take care of when making ROMs.
Thanks for clearing things up, Bob.
Click to expand...
Click to collapse
@DeeTee73
It depens on your ROM which tweaks are safe.
You'll have to invest a lot of time and work to find that out.
For me, disabling fsreplxfilt (NOT removing it) for some folders is the only tweak that I consider safe (for my ROMs, yours might be different!).
@Laurentius
Who cares if you're number one in benchmarks?
I could easily be number one, I've invested lots of time in improving the tweaks and testing what is stable and how they increase the scores. Based on the testing, I've only applied some tweaks to keep my ROM stable.
Because I want my ROMs to be stable. I don't care about being the "benchmark king". Benchmark scores are worth nothing when ROM sucks in other areas.
But if it makes you happy to have high benchmark scores, go on... I don't care.
My understanding is that a cooked rom is a rom that has lots of bit's taken out and then cabs etc put back to make the HD2 run with better performance etc.
But there are so many roms on here, that it has become confusing as to which rom to put on my device. Also what happens when a new legit rom from HTC comes out - doesnt that mean that all the cooking starts again and we end up with thousands of roms?
I would have thought that the additional software installations after installing a new ROM to get the phone in a decent state would put most people off lol.
This is not a dig btw - i have installed a cooked rom, but i think the forum needs to be maybe reshaped a little more i.e. another category with each rom version.
Agree. Would like to see some kind of categories, maybe one for "Featured ROMs", they are cool, gives a hint of what will come, but they might be unstable. One category for ROMs really close to stock, but with minor changes...
i totall agree.. i am a new member as you can see on my number of posts.. i would really like to get to know which rom update is for what and which works best with htc hd2.
need help.
Just do some more research and find what you like.. and use it very often.
Custom Roms are for everybody and each chef has his own kitchen.. and receipe. Someone goes for speed the other for stability.. and some other chef again for a better layout.
I agree sometimes it is difiicullt to see what features are added and to compare which rom suites your needs best, but you could filter it all for you self. Select all Roms that have your interest and filter down to 2 or 3 Roms... then flash those 2 or 3 roms and try them for a few days. You will able to tell which one is best for you
It's up to you which one you choose.. so for lazy people who do not want to search.. stick to the shipped Roms
Bouloama said:
Just do some more research and find what you like.. and use it very often.
Custom Roms are for everybody and each chef has his own kitchen.. and receipe. Someone goes for speed the other for stability.. and some other chef again for a better layout.
I agree sometimes it is difiicullt to see what features are added and to compare which rom suites your needs best, but you could filter it all for you self. Select all Roms that have your interest and filter down to 2 or 3 Roms... then flash those 2 or 3 roms and try them for a few days. You will able to tell which one is best for you
It's up to you which one you choose.. so for lazy people who do not want to search.. stick to the shipped Roms
Click to expand...
Click to collapse
+1 for this one.
It's ur own thing!
Well, All these roms are the personal preference of the maker with some feedback and input from the users. The only way is to decide is read the descriptions and perhaps see what apps are included and mainly, which version of windows mobile (all 6.5 but some the newer 6.5.3(?) version with the taskbar at the bottom and some fingerfriendly stuff), which version of manilla (2.5.1922 is the newest with a document tab but some bugs), etc.
The rest is just a matter of personal preference and trying.
It has always been like this and it works wonderfully... newbs that come here and say this kind of stuff should first try to understand how this forum works and WHY there are so many roms..
Like i said - i agree on the principle of it - but why not create sub forums with rom versions etc so the layout is easier. Being called a newbie because i havn't posted many threads is rather insulting
I really love the way it is now. It gives you freedom to choose, and make your device more custom. I would however like to see alot of cooks go together and create "the perfect rom".. Some cooks go for stabillty, others for speed, someone for visuals. Combine all those chefs recepies and you would have one fantastic rom i believe
I agree with Da9L!
If you spend more time with xda-devs you will see a structure. If i need a WM 6.5.3 ROM i search only for the Sys.Build (28xxx). Very easy.
1. I like having the choice between many different ROMs..you simply have to see what fits your needs the best.
2. Most people stick to their favorite cook because they have similar "taste" and usually you stick with it.
we have many 5-star cooks here and its hard to single out ONE great ROM. There is no universal solution so take a close look at the ROM description and see whats added and removed, look at the bugs and changelogs, the builds and decide if it might be your taste.
i love changing roms in search of features speed and new layouts.. but i always forget which rom was on which version when i last tried it . and now especially with new and different versions of manila and htcsense it is getting a bit of confusing...
I wish if there is a single chart of all roms where they keep atleast some basic information...
like
Name of ROM -- LAST UPDATED-- OS VERSION-- MANILA Version -- Changelog etc
something like this (except its for ANDROID ROMS)
http://db.androidspin.com/android_build_information.asp
tell me what you guys think of this....
Variety
That's like walking into a restaurant and saying, 'why all the different meals?' Or a bar and, why all the different girls? Or why all the different cars? It's the whole point of this site. Viva la difference!
Xaddict said:
That's like walking into a restaurant and saying, 'why all the different meals?' Or a bar and, why all the different girls? Or why all the different cars? It's the whole point of this site. Viva la difference!
Click to expand...
Click to collapse
True...
But with a menu, you have categories. "Main meals" (full featured rom?) "starters" (clean rom without manila or any addons?)
You just have to have a look at this forum
TheDynamo said:
My understanding is that a cooked rom is a rom that has lots of bit's taken out and then cabs etc put back to make the HD2 run with better performance etc.
But there are so many roms on here, that it has become confusing as to which rom to put on my device. Also what happens when a new legit rom from HTC comes out - doesnt that mean that all the cooking starts again and we end up with thousands of roms?
I would have thought that the additional software installations after installing a new ROM to get the phone in a decent state would put most people off lol.
This is not a dig btw - i have installed a cooked rom, but i think the forum needs to be maybe reshaped a little more i.e. another category with each rom version.
Click to expand...
Click to collapse
You just had to read and learn
the thread title is very misleading based on what the TS has to say
in any case, the current layout is fine. i do not think it is very "efficient" to keep going down sub-menus
It would be nice to have a XDA market were al ROMS and stuff can be rated, that would certainly sort things out
Personally I wish there were more ROMs! Like someone said, this is how its always been, this is how it is, and this is how it will always be.
It would be good if the chefs stuck to the official thread naming scheme.
I was gonna provide a link to it, but cant find it now
Rated by who
nwolsink said:
It would be nice to have a XDA market were al ROMS and stuff can be rated, that would certainly sort things out
Click to expand...
Click to collapse
The only one that can rate the best rom for you is you
What might be the case
Many of the ROM's have no layout customizations and vary
often only a little in included applications, tweaks/driver patches.
If a new user installs a couple of ROM's , chances
are differences aren't all that big, and the question arises, what's the point ?
If one looks at the older devices, one can see an almost vulgair
choice of styled, tweaked and pimped beyond recognition ROM's.
I mean the ROM's where you open the default games folder and there's 10 games, 19 great themes to choose from, 6 clocks, and what's more.
The fact those ROM's aren't available (yet) could be strange to people relatively new to XDA.
Maybe it's something all different
Edit : forgot to mention Xanitechs Pandora ROM which has "styling" (works like a charm for me)
Maybe it’s just me but I wanted air my views on current crop of cooked ROM’s. I have been an avid flasher since the glory days of cooked ROM’s from the Hermes (TyTN) era but recently I no longer feel the urge to flash, I guess the novelty has worn off me or I’ve just become a boring old fart whatever but to me it seems that a lot of talented chef feel the need or urge to release a ROM every other day with all the bells and whistle i.e. latest drivers, builds etc…. Quantity rather Quality!! The latest and the greatest does not always mean it’s the best!!!
Initially it’s great to have that choice and flash the ROM of the day until the next, just like a kid in a sweet shop all that choice but surely is it not better to release a ROM a few weeks or month down the line then to release it almost on a daily basis? At least that way one would be able to see significant improvements on the ROM!
I would like to make it clear there are very good cooked ROM’s here that would put some stock ROM’s to shame and with the recent advent of the 576 RAM hack it’s just another valid reason for novice to flash, all I’m saying is can we have more Quality ROM’s then Quantity it’s getting to the point “Too many cook spoil the broth”
well, there are many broths out there, not only 1 broth. So it doesnt matter to me.
i am inclined to agree, up to a point.
I used to cook firmware for LG phones (Viewty / Renoir) and often got accused of releasing too many, sometimes just days apart. My arguement then, and now, is that nobody if forcing you to upgrade.
However, the choice of cooked roms is mind-boggling, and there seems to be no definitive comparison table to easily show the differences between them, and the information supplied with each one is not always accurate. I have only had my HD2 for a week now, (and still loving it ) and i have flashed about 5 different roms, and keep going back to the same one, Leo Lite, by Mr Vanderlay. For me it is the best. And so far, seems to be the fastest for my own useage.
I do think there needs to be some collaboration between cookers to make comparisons easier. And perhaps slowing down releases, just a bit would make a world of difference.
Not naming names or ROMS, but some i have tried are indeed the latest and greatest, but some fundamental things remain broken and are therefore not useable in an everyday situation. This is a PHONE after all, and whats the point of reinstalling everything evry single day?
Find something you like, and stick with it
I think the section should be more organised, e.g. a WM6.5 and 6.5.x subsection with WM build and Manila build specified in tags.
g.lewarne said:
i am inclined to agree, up to a point.
I used to cook firmware for LG phones (Viewty / Renoir) and often got accused of releasing too many, sometimes just days apart. My arguement then, and now, is that nobody if forcing you to upgrade.
However, the choice of cooked roms is mind-boggling, and there seems to be no definitive comparison table to easily show the differences between them, and the information supplied with each one is not always accurate. I have only had my HD2 for a week now, (and still loving it ) and i have flashed about 5 different roms, and keep going back to the same one, Leo Lite, by Mr Vanderlay. For me it is the best. And so far, seems to be the fastest for my own useage.
I do think there needs to be some collaboration between cookers to make comparisons easier. And perhaps slowing down releases, just a bit would make a world of difference.
Not naming names or ROMS, but some i have tried are indeed the latest and greatest, but some fundamental things remain broken and are therefore not useable in an everyday situation. This is a PHONE after all, and whats the point of reinstalling everything evry single day?
Find something you like, and stick with it
Click to expand...
Click to collapse
Of course no one is forcing anyone to flash! and yes I do have a preferred ROM, my own custom ROM!
Jack E said:
I think the section should be more organised, e.g. a WM6.5 and 6.5.x subsection with WM build and Manila build specified in tags.
Click to expand...
Click to collapse
+1
Great idea. I'd love something like that as well. I feel overwhelmed trying to swim through all the choices sometimes.
Hi !
I think some chefs should work toghether creating the best rom ever ;-)Collaboration is the best !!
not wishing to sound elitist, cos im pretty noob at the whole cooking game, but do you not think the lack of a super simple join the dots scheme actually helps prevent accidents by forcing people to do a little investigation themselves?
if it were boiled down to "click here for best rom" people with zero idea what they are actually doing would be flashing like crazy, then complaining when they get a brick.
samsamuel said:
not wishing to sound elitist, cos im pretty noob at the whole cooking game, but do you not think the lack of a super simple join the dots scheme actually helps prevent accidents by forcing people to do a little investigation themselves?
if it were boiled down to "click here for best rom" people with zero idea what they are actually doing would be flashing like crazy, then complaining when they get a brick.
Click to expand...
Click to collapse
i think you misunderstood, what we have said is some sort of comparison chart / better named and layed out ROM section would make it easier for everybody. Nobody has stated they want a "click here for the best ROM" system.
eg:
ROM SECTION
--------------------WM 6.5
-----------------------------"Freds rom v1.1" 21889 Manilla 2.5.2010 WWE
-----------------------------"Marys rom v4.5" 21890 Manilla 2.5.1922 GER
--------------------WM 6.5.x
-----------------------------"Andys rom v1.0" 25315 Manilla 2.5.1921 WWE
-----------------------------"Janes rom v2.3" 24001 Manilla 2.5.2010 ITA
whats so wrong with that sort of layout? at least it makes it easaier to find the type of ROM you want rather than trawling through 3 or 4 pages of highly confusing rom names that get all muddled up. Its even worse where some chefs have WM6.5 and 6.5.5 roms with similar names.
Since Leo is currently the most powerful WM device, most cooks definitely would get one, and is understandable lot more cooked roms would be available.
You folks should feel lucky for that. (man, I am still waiting for the NA version...)
jackleung: import one from Australia! 850 3G compatible!
Also, someone tried to create some 'sense' of the ROMs by making www.xdaroms.com but it comes a bit short.
The concept is sound but some things need to happen to make the site great. Namely:
1) Chef support: Dedicated accounts where they can upload freely, add details, etc.
2) UI revision: It looks like the same damn mobile oriented sites we've seen for the past decade
I like the fact that there are many releases and so quickly. I also like the fact chefs are pushing the latest tech to us so quickly even if the rom is not perfect. release early get bug reports release fix etc.. its moving the platform forward and keeping it interesting imho. sure some better organization would be nice but the changelogs on the chefs pages for me do a good job of telling me what's inside the latest creation.
now I have just cooked my own rom I want more faster latest releases of dev branches to play with
I think too that there are too many choices without clear layed out differences between them.
I hope that there were some comparasion but I think its just a matter of variety
There is no substitute for real-life usage bug discovery, so I think releasing newer tech as soon as possible (letting people know that it is sort of beta and will contain bugs) means those bugs can be found and resolved quicker.
Actually, most chefs do tag the topics with WM6.5 or WM6.5.3 and mostly even include the Sense version.
After a while you realize what rom offers what. Personally, i stick with one rom that i am happy with, until the cook changes something that doesn't fit my needs anymore.
Also generally there are concepts to rom design: Some chefs cook roms with particular flavor, i.e. tweaks, hacks, design changes (such as custom task bar, backgrounds, boot splashes), and some just create "stock rom like" roms, that mostly offer either a stock rom with removed junk, or a stock rom with updated components. I prefer the latter.
gfreek said:
Maybe it’s just me but I wanted air my views on current crop of cooked ROM’s. I have been an avid flasher since the glory days of cooked ROM’s from the Hermes (TyTN) era but recently I no longer feel the urge to flash, I guess the novelty has worn off me or I’ve just become a boring old fart whatever but to me it seems that a lot of talented chef feel the need or urge to release a ROM every other day with all the bells and whistle i.e. latest drivers, builds etc…. Quantity rather Quality!! The latest and the greatest does not always mean it’s the best!!!
Initially it’s great to have that choice and flash the ROM of the day until the next, just like a kid in a sweet shop all that choice but surely is it not better to release a ROM a few weeks or month down the line then to release it almost on a daily basis? At least that way one would be able to see significant improvements on the ROM!
I would like to make it clear there are very good cooked ROM’s here that would put some stock ROM’s to shame and with the recent advent of the 576 RAM hack it’s just another valid reason for novice to flash, all I’m saying is can we have more Quality ROM’s then Quantity it’s getting to the point “Too many cook spoil the broth”
Click to expand...
Click to collapse
I feel the same, in fact my new years resolution this year is to only flash stock ROMs!. My HD1 was the worst for it, every other day I would be flashing a new ROM, the pattern would normally go something like this:
Week 1
"Steve" finds a new way of improving speed and creates a ROM including the fix, I flash it but find that a few other things are broken.
Week 2
"Sam" then builds a ROM with the new speed improvement and nothing broken. So I flash it. But then realise that its blisteringly fast, because the ROM has nothing in it!
Week 3
"John" then builds a ROM that looks beautiful and has many applications, but lacks the new speed improvements. I flash, and am back to square one! And the cycle continues...
I don't think its anybodies fault, and I don't want anything to change, but I think that perhaps some of the more experienced users are feeling a little jaded now. Whereas the newer users are still in the honeymoon phase of being able to flash new, varied ROMs! I also think that there is more competition between chef's these days, and users demand the new discoveries in their favourite ROMs. (576mb / 1gz for example), meaning that the cycle is becoming ever shorter, as people are discovering new things almost daily!
it is very hard to flash rom every day this way you cannot keep any data on deice you need to inistall programms every day apply tweaks every day so so hard
Schooleydoo said:
I feel the same, in fact my new years resolution this year is to only flash stock ROMs!. My HD1 was the worst for it, every other day I would be flashing a new ROM, the pattern would normally go something like this:
Week 1
"Steve" finds a new way of improving speed and creates a ROM including the fix, I flash it but find that a few other things are broken.
Week 2
"Sam" then builds a ROM with the new speed improvement and nothing broken. So I flash it. But then realise that its blisteringly fast, because the ROM has nothing in it!
Week 3
"John" then builds a ROM that looks beautiful and has many applications, but lacks the new speed improvements. I flash, and am back to square one! And the cycle continues...
I don't think its anybodies fault, and I don't want anything to change, but I think that perhaps some of the more experienced users are feeling a little jaded now. Whereas the newer users are still in the honeymoon phase of being able to flash new, varied ROMs! I also think that there is more competition between chef's these days, and users demand the new discoveries in their favourite ROMs. (576mb / 1gz for example), meaning that the cycle is becoming ever shorter, as people are discovering new things almost daily!
Click to expand...
Click to collapse
Well said, I couldn't agree more!
All true and all the different choices don't make it easier but I do notice I usually stick to a few cooks having my favorite roms...
I mean, I like a certain windows build, certain looks (default white clock, no transparent stuff), some basic apps and functionality, no need for a document tab, etc...
As a result I stick mostly to the Miri roms (and every now and then I try another, now running energy since I really liked that on the touch pro) so once you have your mind made up about what you want in general a number already drops out of the picture.
Wouldn't it be better to ask some of this enthusiastic "chiefs" to help developping Android instead for developping redundant versions of windows mobile in different "flavours". It is just waste of time. We need Android, where the real fun is!
Don't worry, NRGZ28 has no plans to retire yet (I hope ). This thread may get closed or may only get a few replies, but your feedback is appreciated if you would be kind enough to post a few words...
It's not one of the usual "which ROM should I choose threads". I'm experienced here enough not to annoy you all that much!
The problem is that since I flashed my first EnergyROM on my Diamond or TP (can't remember which), I can't divert from them. Great for NRGZ28...that's obviously the desired effect, but I see so many other ROM threads in these fora, and it's obvious so many people choose them over EnergyROMs for one reason or another. Basically, I like the fact that they look great and come "fully-loaded", and a big thing for me is that the latest WM build (currently 23563) is used to cook from. A "stock" or "lite" ROM isn't much good to me as I would just fill it with all the same stuff anyway, only not being cooked in it probably wouldn't all work together so well.
What I'm asking for is what others are using instead of EnergyROM and why.
What I'm most worried about is that I'm so stuck on EnergyROMs that I might be missing something else. I recognise completely that all of the ROM chefs are super talented in what they do and I wouldn't know where to begin in cooking myself. I mean I like to think that I'm pretty well techie-minded, but the thought of ROM cooking hurts my head! All those XIP and SYS and pagepools, lua script & manila files, all the ExtROM stuff that gets constantly updated that I wouldn't be able to get hold of, not being in the right circles. I just can't bring myself to try because I know it could always be better.
But also, I don't like to constantly flash all the time, once a week is enough I think and this is what keeps me from testing other ROMs.
Thanks for reading and I hope I didn't just waste 2 minutes of your life and a few kilobytes on the xda server! I'm sure there are more "EnergyROM addicts" out that are wondering if anything else compares.
Whatever ROM you choose you will be missing something. The right question is:
Can I live without that feature/application/tweak/theme/etc?
Choosing custom ROM over stock has its obvious advantages. Using stock has its advantages also: warranty is not violated, you have support from manufacturer etc.
Custom ROMs are different story. They are made by individuals according to their taste: from eye-candy (or lack of it) to choice of apps and tweaks.
EnergyROMs have nice eye-candy, they are nicely optimized with good app choices. There are ROMs that are faster. There are ROMs that are close to stock look, so you can modify it according to your own taste. There are ROMs with no additional apps so you can install exactly what you need. Some chiefs refresh their ROMs more frequently than NRGZ28, so you get new build faster.
Personally, I stick to the "good old" 21XXX builds and flash only when there is important update in newer build. Something like improvement in speed or some feature that is important to me (battery life, newer Office build, or fix for something that was not working as it should).
EnergyROMs are used by many so bugs and problems are found much faster and, consequently, fixed faster.
I have tried almost all other ROMs but for some reason, EnergyROM on HD2 presents for me, personally, perfect combination of looks, features, stability and battery life.
You make some very valid points...am I right in considering you an EnergyROM addict too?
In fact all of what you have said is completely my way of thinking. Although I use the 23XXX builds. For some reason I have some (un)healthy compulsion to have the latest of everything, which is one of the main reasons I use EnergyROM in the 1st place (and I also why I bought a HD2 when I had a perfectly good TP2, much to my wife's dismay!
)
I couldn't go back to having the "Start" and "X" buttons at the top. That's SO 4 months ago!
Anyone else wanna throw anything in?
Admire al chefs but..
Yes, I admit I have a NRG addiction as well.....
I do try other chef's cooking as well, especially because NRG takes the time to release new builds, and others come out with theirs earlier. I find myself time after time going back to his, either 'downgrading' or flash one of his as soon as they come out.
What other ROMs I try?
I would categorize them like this:
1. Eye candy - Some chefs here are extremely talented is combining their own looks, or co-operating with people with high skills of developing beautiful looking screens.
2. Performance - I always look for a ROM that will have no lag , be memory efficient (not that the HD2 lacks any) , and one without bloating.
I think the appeal NRG ROMS has on me (at least) is the combination of the Italian beauty (see the cars they make) and the German precision. On top NRG is here in the US, and it gives him another advantage for me. Not sure if he is on AT&T or not, but until now any recommendation he has (like going back to 2.07 radio) was a great advice.
I try from time to time Miri's , Tom Codon's , IT's (sorry, not on this forum any more, but still a great chef) and Dutty's, even some others. All are great piece of work, and I do want to take the opportunity and thank all of them, but as stated - NRG's are always the ones I finally keep on my phone, and dare travel with..
i think there are some fundamental differences in chefs way of thinking.
I for one (and i know a few others who have stated as much) are cooking primarily for ourselves. we just choose to share the work. I will listen to requests, and if it is valid that it gets taken care of. Of course bugs affect everyone, so they take a priority.
Many other Chefs seem to "cook for the masses" and therefore appeal to a wider audience.
I dont think it is any any way fair to consider one chef over another by something as simple as post count on their rom thread (not saying you do this its just an observation).
If you feel comfortable with a style of rom, there is nothing wrong with sticking to it. but as you say, it never hurts to look, and so you have.
Going back time and again to one chef is more a compliment to that person, and nothing to be concerned over.
matmaneyre said:
But also, I don't like to constantly flash all the time, once a week is enough I think and this is what keeps me from testing other ROMs.
Click to expand...
Click to collapse
I flash every morning (atleast)...sometimes even before taking a crap
Anybody knows any bone diseases I may end up with, please warn me !
On the better side of the thread intention , I for one personally end up with a Clean rom with no extra apps so I can make it my 'own'.
Always two sides to a coin... or many sides to a paper note if you fold it
ok so we are all aware of all the various android builds out there for different phones. some with sense, some stock. all the chefs have their own basic formula for the perfect rom when they try to cook them for us. now most builds we apply to our phones are mod's of builds for other phones. After working with so many builds and liking certain features of each, but only available to each, i found myself asking the following question.
Companies like htc, etc. are assigned to build a certain phone with a certain android build with certain features activated/deactivated (ex. some builds have tethering, but tmobile said to cut tethering option out of g2. or some builds have a 2g/3g on off option where as others don't) this must mean that there is a general android build they start with that has all features and they just decide to keep/omit things they want or things carriers don't want. (or add some version of sense ui to it or touchwiz). My question is, is there a general ultimate android build that is available that has every feature there? i'm not a developer so i've never cooked a rom, but it would be awesome to have one build with everything and a simple way for users to decide which options they want or to omit. i know it sounds simple in theory and will never be that easy. but it would be awesome to have one general build with all options and can choose which ones i want to use or not to use vs. a developer selecting them for me.
this is a major problem with many winmo builds i've worked with compared to android builds, but its still something that bugs me when i try a rom and say damn i wish there was a 2g/3g on off in the network options vs having to dig for gsm/wcdma options. like i said in theory it sound easy and i'm sure its not, thats why i give all the chefs credit. but just throwing it out there in case something were to exist like that. thanks
I think I understand what you mean.
I've played with the Android SDK and the BASE 2.2 (what we know as Froyo) has all you mention (tethering etc), but looks kinda bland, this may be that I'm now so used to Sense and it's niceties that anything less than Sense to me just looks wrong.
If you want to see Android as Google intended for us all to use just download the SDK and start a 2.2 session with no modifications and you'll see the differences that carriers and the cooks here do, it's amazing work.
Also, almost all cooks here in XDA will try and give you access to everything the phone itself can do, that's part of the fun of running a rooted OS.
thanks for the tip about trying out the sdk Reno, i'm gonna check it out this weekend. Don't get me wrong, i love all the fun of flashing and its an addiction since 2007 on my HTC 8525/G1/HD2 lol. and i give mad props to all the chefs, god knows if i started messing with code, my phone would be a brick an hour later lol. Android chefs are really good and don't tweak much like winmo chefs do at times which i like. so many builds for winmo you'll find are scraped down to bare minimum because the chefs wanted a bare rom that gave u the "most space and fastest speed" which all went to hell once u install crap you want on it anyway, but half of the features and options have been deleted! thank God android chefs are good with keeping things there.
woohoo sdk fun friday night! will i become a chef? do chefs need to wear the silly hat?
I'll be perfectly blunt you'll need more than just the SDK to get a build made. I only downloaded it out of pure curiosity. You'll hopefully see in the attachments exactly what default Froyo looks like and realise even more what a godsend these guys here are.
I would honestly love to make my own build (more for my own fun and use than for general consumption) but I realise after many hours of reading and research that it's ridiculously hard work and these guys deserve every penny we can afford to donate for their toil.
Going back to the original point though: I think to create one overarching build that upon install you could pick: stock/sense/launcherpro or whatever other flavour there is available out there would actually be impossible. The look of the build is so deeply embedded in the build itself and requires so many different parts of the operating system itself to be changed you would need several copies of each file with the different variations for each look/style you'd end up with HUGE download sizes and it would be more difficult to keep up with when there is an update.
As things stand now, I know I could never drop my Sense builds, I love hastarins kernel tree, and I have my favourite small group of cooks that I follow, and that helps me limit what builds I download and test. Having a couple of small spare memory cards helps and only cost me £20 or so to give me that choice.
Reno i feel that you are correct. i couldn't resist and went to download the SDK after replying to your post. its still downloading a bunch of things and as i read the android developer page i'm enticed to hit the cancel button! I think i'll just go back to picturing the chefs as the magicians and let them entertain, instead of being the guy who tries to figure out all the tricks lol.