should we all pick a specific winmo build and radio and test our android builds on it?
that way we can pinpoint the issues easier.
because as of now theres about a dozen different winmo builds running under android and the whole ****load of issues were having with android gets blamed on different radio and winmo builds.
can we kinda get our sht together( the users not the developers and cooks) and participate a lil more in this? at least by submitting productive reviews of the android build we use.
and having same exact winmo build and radio would im sure help alot in tracking down the problems that we re having.
i mean does it take alot to agree on one winmo build at least untill android is able to boot itsself up without winmo.
because as everyone can see,
even though the cooks claim to have no problems, we still get problems with pretty much everything, happening on random phones, and im assuming part of the reason is using different winmo builds.
i agree. there are many good winmo builds. and a great number of them run flawlessly with android. however its always a good idea to run what the developer is running. as i have been using the 'standard' energy build with 2.12.50 and have still been encountering strange issues like settings not being present on my phone (froyostone)
id personally like to hear what the developers think is the best winmo base rom.
and have everyone who wishes to run android and participate in bug reporting etc. to switch over to the chosen winmo rom.
would make life easier. +1 to the OP
I pretty much keep quiet in these forums but think this is a great idea. I'm using radio 2.12.50.02_2 which I've found as best and Elegencia V2.0 Final WWE rom.
Maybe we can force some sort of format to be used when stating an issue? Region, carrier, WinMo rom and version, settings changed, Android build? Maybe we should vote on a main rom for WinMo ment just for Android, with an active chef, that way we can iron out the bugs.
a group effort would help alot i think, since we all technically testing the builds we might as well be a bit more organized as HD2 users since it would benefit all of us by speeding up the android development.
i havent been diggin thru this phone long enough to know the whole system, maybe one of the cooks or few cooks can get together and bake an apropriate android winmo rom so we can all use it as a reference.
since most of android users/ testers run android daily without going to windows much i dont think anyone would suffer from running a stripped winmo build.
and once the robot can breathe on its own we can then focus on stability with different winmo builds, if that would be needed at all.
that involves cooks as well, i know you guys are running your own builds and all
but it would be a lil harder for us users to switch winmo builds for every different version of android that is coming out, because theres a new andy build almost every day.
if we could pick one and update it when needed????
well i see there are couple roms that are made for android,
i personally been using chunkyrom for all my androids
and seen alot of them beeing used as well.
can someone list the roms so i can make a poll
As stated earlier, just follow the setup the developer is using and you minimise any issues.
Personally I think a specific rom will be useful in trouble shooting.
But personally I cant stand most of the winmo rom's I dont use it very often but Incase something isnt working I need a rom that i can switch to and everything works.
I've tried chucky ive tried miri and both didnt work out. Honestly I am more versed in android than I am in winmo. So when I had problems with data connection Id revert back to energy.
So id have to vote for any energy based rom with working tethering!
Sorry, I dont think this is ever gonna work. I use my own WM ROM that I cooked myself, it has been stable for the last 6 months and I really cont be bothered faffing around changing the rom as it is exactly how I like it. The hardcore flashers may just about go with this but I actually have to use winmo quite heavily for work.
I have played about with the radio but still prefer the old 2.08 because it works best for me on my carrier where I live, but for someone else a different radio will be better for them. See where I am going with this?
I don't think it'd be a good idea, personally. One of the things I love about these android builds, and the wm roms, is the available choices. (But I also love tinkering with things, so it could just be a personal preference.)
hazard99 said:
Personally I think a specific rom will be useful in trouble shooting.
But personally I cant stand most of the winmo rom's I dont use it very often but Incase something isnt working I need a rom that i can switch to and everything works.
I've tried chucky ive tried miri and both didnt work out. Honestly I am more versed in android than I am in winmo. So when I had problems with data connection Id revert back to energy.
So id have to vote for any energy based rom with working tethering!
Click to expand...
Click to collapse
Same for me, Energy roms are the only winmo rom's that I haven't had issues with so I vote for energy based roms.
you guys dont understand, nobody is forcing you to stay with one,
all im sayig is to pick one while the android is in development stage, that way we know that the problems are coming from android and not winmo build since we use same build, or how about 3 builds that we can pick and stick to it untill we get android on main memory working, then you can all go back to any winmo build,
if you dont want to participate like i said nobody is forcing you , im simply suggesting this in hopes of speeding up the development since with same build we can actually trace the problems easier than having 30 random problems with different builds that are not even related to android.
so far i ve seen alot of chunky roms and energy roms used with android.
is there another popular roms there so i can list them in the poll
+1 .... Energy barebone for use andriod as an everyday OS radio 2.12.50
Sent from my FroyoStone V.1using xda app
This could be problematic when you consider that the ROMS being developed on are made for different phones, different version of WinMo, and different carriers. Each variation has the potential to change the quality of the outcome.
How about this instead. The cook develops the A-ROM on whatever W-ROM meets the cooks requirements and releases it. The cooks part is done. People can either use it or wait until a test group tests it against a base W-ROM.
For those who want testing before using an A-ROM, then a stripped down base W-ROM can be developed in minimal variations (device, OS, carrier) for the end users to test against.
This way cooks get what they want, bleeding edge users get what they want and those less willing to chance a balky phone get what they want.
I'm all for standardizing, but trying to limit a cooks options is not the way to go. In fact, it totally defeats the whole purpose of what they are doing.
some input from developers would be of great help. since they know more about the workings of the systems.
im just assuming that this might help.
if it would great im willing to use a single rom for all my andro builds since i dont ever go back there( like dos)
a good example would be battery life.
im running the new Nexus One Android 2.2 Build FRG33
and today my battery went down by only 1/4th all day in standby,
then another user reports that his battery leaks out like water.
Hi guys
After reading around the forum a bit, it seems some people were in similar situations as me, but I still don't have a definite answer.
I have been using a HTC Dream for about a year, and have been an avid fan of cyanogenmod. Although I like the fact that it's rooted and I can install any ROM i liked, I stuck with cyanogen because:
1. It's extremely stable
2. It's well established - they guys got their own site, a central location for all ROM info, all files are found in the same place, they continuously update the ROMs and it pretty much always gets better
The above points for me were reason enough to not even bother with any other ROM. I bought a HTC HD2 a few days back, and I now want to have the phone dual boot Android. What android rom is as good as cyanogen, where "good" is defined by my points above? I know there is a ported cyanogenmod rom, but how well does the port work, will it be updated often as new cyanogenmods get released, etc? Also, I'm no fan of nightly builds, so I don't want a port based on a nightly build - it must either be experimental, release candidate or stable. I also want to stick with the ROM I choose, so it should be continuously updated for the foreseeable future..
First of all, you say you don't want nightly builds, but experimental is okay? Not exactly following, but hey.
There are a couple of CM based roms, if i'm not mistaken 3 are still being maintained:
-JDMS
-HD2ONE
-Mychiprima's (not sure if I'm spelling his name right here) build, it doesn't really have a name (thread contains "htc_linux_wince" at the very beginning)
Mychiprima's builds are based on the autobuild, and are therefor not checked and may contain bugs. JDMS and HD2ONE however are being thoroughly checked & optimized by the respective chefs, so I don't really see a point in not trying them.
Still, if you really want builds based on CM-stable there's always shubcraft and hyperdroid, but both have been discontinued for some weeks already, so you won't get the recent optimizations.
yusufm786 said:
Hi guys
After reading around the forum a bit, it seems some people were in similar situations as me, but I still don't have a definite answer.
I have been using a HTC Dream for about a year, and have been an avid fan of cyanogenmod. Although I like the fact that it's rooted and I can install any ROM i liked, I stuck with cyanogen because:
1. It's extremely stable
2. It's well established - they guys got their own site, a central location for all ROM info, all files are found in the same place, they continuously update the ROMs and it pretty much always gets better
The above points for me were reason enough to not even bother with any other ROM. I bought a HTC HD2 a few days back, and I now want to have the phone dual boot Android. What android rom is as good as cyanogen, where "good" is defined by my points above? I know there is a ported cyanogenmod rom, but how well does the port work, will it be updated often as new cyanogenmods get released, etc? Also, I'm no fan of nightly builds, so I don't want a port based on a nightly build - it must either be experimental, release candidate or stable. I also want to stick with the ROM I choose, so it should be continuously updated for the foreseeable future..
Click to expand...
Click to collapse
check this out http://android.hd2roms.com/
StephanV said:
First of all, you say you don't want nightly builds, but experimental is okay? Not exactly following, but hey.
There are a couple of CM based roms, if i'm not mistaken 3 are still being maintained:
-JDMS
-HD2ONE
-Mychiprima's (not sure if I'm spelling his name right here) build, it doesn't really have a name (thread contains "htc_linux_wince" at the very beginning)
Mychiprima's builds are based on the autobuild, and are therefor not checked and may contain bugs. JDMS and HD2ONE however are being thoroughly checked & optimized by the respective chefs, so I don't really see a point in not trying them.
Still, if you really want builds based on CM-stable there's always shubcraft and hyperdroid, but both have been discontinued for some weeks already, so you won't get the recent optimizations.
Click to expand...
Click to collapse
Thanks for that info. When I said experimental, I meant their beta versions - maybe my terminology is a bit wrong, but I know with the Dream, sometimes they used to release a beta version, then a RC, then a stable. From my understanding nightly builds were often buggy as they weren't tested. I'l have a look at those ROMs you suggest though. Aside from cyanogen, are there any other ROMs you think fit my two point criteria I gave in my first post?
leon98408 said:
check this out - link
Click to expand...
Click to collapse
Thanks a lot. That's very helpful. I'll have a look through that
yusufm786 said:
Thanks for that info. When I said experimental, I meant their beta versions - maybe my terminology is a bit wrong, but I know with the Dream, sometimes they used to release a beta version, then a RC, then a stable. From my understanding nightly builds were often buggy as they weren't tested. I'l have a look at those ROMs you suggest though. Aside from cyanogen, are there any other ROMs you think fit my two point criteria I gave in my first post?
Click to expand...
Click to collapse
I assumed that's what you meant, but RC's and nightlies are both just called experimental.
It's true nightlies as such aren't tested, because they are autobuilt. But the code that goes into it (in modules) does get tested first, so you'll usually have a nice working rom. (I'm talking about officially supported CM devices now, I already said how we do it with HD2).
There are other established builds (on HD2, you don't call them Android ROMs, but builds, because they run from sd card. ROMs are WinMo) yes, MDJ's got a whole series but I'm not a big fan of Sense myself. They're pretty popular though!
StephanV said:
I assumed that's what you meant, but RC's and nightlies are both just called experimental.
It's true nightlies as such aren't tested, because they are autobuilt. But the code that goes into it (in modules) does get tested first, so you'll usually have a nice working rom. (I'm talking about officially supported CM devices now, I already said how we do it with HD2).
There are other established builds (on HD2, you don't call them Android ROMs, but builds, because they run from sd card. ROMs are WinMo) yes, MDJ's got a whole series but I'm not a big fan of Sense myself. They're pretty popular though!
Click to expand...
Click to collapse
Ah i see. Thanks man - I got a lot to learn
Hey guys and gals, this may seem like a reasonably stupid, long-winded question, but please bare with me.
I've been cooking WinMo ROMs for ages now, loving it, it's great as a hobby. Not to mention cooking enables you to experiment with / use the later versions of HTC packages and WinMo versions and builds. Honestly I found myself cooking and flashing on a weekly basis.
But when it comes to Android I find myself asking questions like "Why bother?" and "what can I achieve?"
I will admit I have only just begun with Android. I've never had any success with linux on any of my home computers but I've never been afraid to try. So I downloaded my first build of Android, DarkStones SuperRAM build. I have to say I'm insanely impressed with the speed, the stability and the insane level of cusomization that comes with such a build.
But that's just it, in my eyes it's an excellent build and not much could be done to improve upon it, with the exception of maybe some tweaks (I can't find any that I need atm), or addons (which are so small and easily installed via the market)
So again I beg the (n00b) question of why cook an Android ROM? Is it really worth learning to cook it when all I'll be doing is maybe upgrading a kernel here and there, or integrating some tiny little component that I'd otherwise be able to download and install in seconds? The only real thing I'd be doing right now if I new how to cook for Android is remove some basic integrated wallpapers and maybe change some settings so it's more of an HD2 build than an HTC desire build.
My mind is in a quandry, I'm loving DarkStones' build so much that I haven't used WinMo in days, yet I yearn to cook something LOLs
P.S DarkStone if you read this, I'm liking your build so much, you've done excellent work and provided me with an excellent first Android build. Keep a eye on my sig, I'm gonna try and create a decent looking DarkStone banner, got any ideas?
There are a few things that need to be fixed ie usb thetering, wifi hotspot, gps and some minor things..
I'm not that big on debugging or programming, so fixing bugs is one thing I probably couldn't do.
Maybe ill just keep darkstones build up to date and see what changes between builds, I should soon see what can be done when cooking and see then if it's something I can get into
Sent from my HD2 using the XDA Android app
Most builds start out as "I want something CLOSE to what you have"...
From there you tweak and change, add things you like, and remove things you don't... You end up with either:
A) A build which (as you say) is so close there's no point releasing it, but it's still AS you want it, with your settings, so you keep doing it in the background, updating kernels etc.
B) A build which has gone off on a tangent, and is dissimilar enough to be released.
I cook android to have my phone set up, how I want it, with what I want on it, as soon as I flash. It's (reasonably) close to the ROM I started with, so I don't release it, but I'm much happier after a flash, that the set-up is non existent, and everything is pre-configured. For this reason, I continue to do it.
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?