Is there anyway to, as they say 'overclock' the wizard. It's a great PPC/phone, but runs quite slow. Thanks. [/b]
try the search button. use querry "omap"
The utility in this thread is what you need: http://forum.xda-developers.com/viewtopic.php?t=55782
It works on the Wizard, Charmer and Prophet. After installing you should find that you can run your device at 260Mhz rather than the factory set 195. 8)
Was able to download the battery-plug-in software. didn't damage anything on my wizard, but am not realy sure if it increased the speed or not. stil seems mighty slow.
You'll find this by searching too, scattered about. Programs like SPB Diary, SPB Pocket Plus make the Wizard sluggish even when you've overclocked. I learned the hard way to be very choosy about programs that run automatically. Today agenda, SPB weather, PHM Traylaunch and Batterystatus are the only things on my today screen. Smartskey insures that practically nothing is running in the background. I have the latest rom, and I used Xelencin's version (now my own version) so that I have much more space on the device. The effect of all this is that my device is very snappy, except when it decides it needs to talk with the network at length and a good 15 seconds can go by while it does something with the network. Then it just doesn't do anything for 15 seconds, which seems like an eternity when you are about to show someone something, need to check an address or phone number, etc. But 90% of my complaints went away when I eliminated automatic programs, many of which I'd spent money on. It isn't that these programs don't offer functionality, they do, but most of that functionality is also offered by programs that have a smaller footprint.
You'll find this by searching too, scattered about. Programs like SPB Diary, SPB Pocket Plus make the Wizard sluggish even when you've overclocked. I learned the hard way to be very choosy about programs that run automatically. Today agenda, SPB weather, PHM Traylaunch and Batterystatus are the only things on my today screen. Smartskey insures that practically nothing is running in the background. I have the latest rom, and I used Xelencin's version (now my own version) so that I have much more space on the device. The effect of all this is that my device is very snappy, except when it decides it needs to talk with the network at length and a good 15 seconds can go by while it does something with the network. Then it just doesn't do anything for 15 seconds, which seems like an eternity when you are about to show someone something, need to check an address or phone number, etc. But 90% of my complaints went away when I eliminated automatic programs, many of which I'd spent money on. It isn't that these programs don't offer functionality, they do, but most of that functionality is also offered by programs that have a smaller footprint.
I like SPB Diary and Pocket Plus though. Between the larger cache trick and OCing it with battery status, the speed is fine for me. It was a mite too slow without the OC.
After using it for a little less than half a day, I do feel that there is some improvement in terms of speed. However, it still pales in comparison with the xda mini which I used to use. Is this the maximum speed that the wizard can process?
omapclock
Do you have omap running? I run mine at 247MHz but some people are running as high as 260 and report stability.
Re: omapclock
prestonmcafee said:
Do you have omap running? I run mine at 247MHz but some people are running as high as 260 and report stability.
Click to expand...
Click to collapse
Yes - 260Mhz is just fine. 8)
I use omapclock and clock to 264 MHz with it, rock solid at that speed, but higher speeds are no go. The battery plugin shows 286 MHz when omapclock says 264 though
Yeah, have mine running at 260mhz, but don't see much improvement still. Am i doing something wrong? I copied the cab file into the main memory (but not directly into the windows folder), then executed it.
Yeah, have mine running at 260mhz, but don't see much improvement still. Am i doing something wrong? I copied the cab file into the main memory (but not directly into the windows folder), then executed it.
How do you know it is at 260?
If you use batterystatus, you can toggle back and forth from 260 to 195. That way you know if it is running and how fast. It doesn't need to be in Windows; mine is in My Documents/Programs. But it needs to be turned on; it is off by default even if installed, which is why I asked.
If it is, then other than the missing drivers, then the chances are that either a subset of Kaisers, or roms, or third party apps are causing some devices to be a LOT slower than others.
There are people claiming that their devices take three seconds to change orientation. They also claim that you can actually see the icons being "drawn" on the screen.
As a happy Kaiser owner, I have never experienced anything like that (except when syncing over USB - when the device pretty much stops responding for the first few seconds of syncing and then returns to normal.
Changing to landscape on mine take approx 0.3 seconds (I say approx as its too quick to actually time).
Now I made a horrible error. I tried to point out to the defensive people over on the classaction thread that if their device was really that bad, they could try a different rom and see if that makes their device better. I didnt argue that "the" drivers weren;t missing or that their devices would be fine without them. All I did was try to get some research to see if there was an obvious group of devices or roms or apps that was causing the problem.
If like me, you prefer to sort these things out - rather than wait for a year for a class action - then try the benchmarking test in my sig and post your results and rom details. Hopefully, we can find the cause of the major differences in performance.
My device scored 1643 overall.
He's right, people should start blaming the device for everything. Bring back the days when you'd clean up your device when you'd feel it being slow.
Mine is in 1680 or so as well.
Unwired 4,
Can you perhaps provide a detailed list of all the applications you have on your phone?
I ask you this because I don't have alot of apps on my phone; mainly Googlemaps, livesearch, TCPMP, Dutty 1 calc, HTC Album, Opera mini and Palringo.
I don't have any SPB products clogging up my today screen with its numerous shortcuts. I haven't tweaked my clock appearance and I'm using the original windows blue background on my today screen.
My phone looks pretty similar to when it was bought yet I have noticed a lag, even when it comes to changing the screen orientation from portrait to landscape. It takes roughly one second. Sometimes opening an application takes forever, and closing it down to.
I had an issue with video playback, but the member 'Audio' and co offered settings which greatly improved movie playback. So that’s one tiny area fixed
What are you doing on your device which is causing your phone to run so fluidly?
I was happy with my device running the stock Orange Rom. It was quicker than my Hermes running the Black Majik rom. I recently flashed the V3 Dutty Rom and its a little faster - not much though.
I have a 4gb microsd card that I install most apps on. I use the HTC Home screen - with no other plug ins.
See below for screen grabs of installed programs.
Underwired 4,
Thanks for the response. I have an 8GB memory card, and I install all my applications on this card, and not on the device memory. The only thing I've installed on the device memory, that I can recall, is the PIE fix, and the slight fix for the camera. That is all. Everything else goes onto my 8GB storage card, of which I have over 5GB of memory left over. From the looks of it, I have more device storage memory than you do, but slightly less programme memory than you.
My free storage memory reads: 112.76 MB
My free programme memory: 48.54 MB
I’m left scratching my head...
Graphics Test 1 1060
Others Test 2 1730
JPEG Test 3 2246
Games Test 4 1261
Sound Test 5 0669
Final Score: 1393
246810 said:
My free storage memory reads: 112.76 MB
My free programme memory: 48.54 MB
I’m left scratching my head...
Click to expand...
Click to collapse
I have scratched my head about this before too. I tested this last night and if you take the card OUT, you will see a BIG increase in your memory.
My feeling is that maybe if you have shortcuts on the phone TO those apps on the card, at boot time, the phone reads all of those and maybe that is what does it? Or 1 or 2 of those apps on the card load (somehow) on the boot up.
I hope I explained that correctly
Here's my list (doesn't have all I have installed) and it's not slow whatsoever.
My VSbenchmark overall result is 1600-something.. I'm really using it, and Kaiser is coping with it with no problems.. my Wizard would beg for mercy at this point.
MirrorminD said:
Graphics Test 1 1060
Others Test 2 1730
JPEG Test 3 2246
Games Test 4 1261
Sound Test 5 0669
Final Score: 1393
Click to expand...
Click to collapse
Thanks Mirror. Where are you? What device is it (ie tilt, tytn2 vario3) and which rom?
246810 said:
Underwired 4,
Thanks for the response. I have an 8GB memory card, and I install all my applications on this card, and not on the device memory. The only thing I've installed on the device memory, that I can recall, is the PIE fix, and the slight fix for the camera. That is all. Everything else goes onto my 8GB storage card, of which I have over 5GB of memory left over. From the looks of it, I have more device storage memory than you do, but slightly less programme memory than you.
My free storage memory reads: 112.76 MB
My free programme memory: 48.54 MB
I’m left scratching my head...
Click to expand...
Click to collapse
Have you run any tweaking programs to set page pools etc? Such as Kasier Tweak or Shaps advanced config tool?
Mines a bit random.
Sometimes about 1 second, sometimes more. Sometimes it redaws off center and has to draw again. Seems to take longer when sliding the keyboard back in than it does the other way.
Can't say it really annoys me too much... I just wait for it
unwired4 said:
I was happy with my device running the stock Orange Rom. It was quicker than my Hermes running the Black Majik rom. I recently flashed the V3 Dutty Rom and its a little faster - not much though.
I have a 4gb microsd card that I install most apps on. I use the HTC Home screen - with no other plug ins.
See below for screen grabs of installed programs.
Click to expand...
Click to collapse
Since you seem to be on a mission, please provide us video of your screen rotation. Actually 2 videos; one with only today screen showing and one with any program open on it. If im on Today, the screen rotates in about a sec, but if I have i.e. Opera Mini open it takes 3 sec at least.
I just said on the classaction.org thread that i had a friends Ipaq 6915 for few days and the difference in speed, i.e. opening programs menu is obvious.
Im still running Duttys WWE lite rom with Spb Pocket Plus + Diary + weather, S2U2, WkTask, TC, Office, Live etc installed. On my today i have only 4 quick launch icons and the Spb Diary.
BTW. Its a joke playing even Spb Arkball on the Kaiser...
foobar1977 said:
Sometimes it redaws off center and has to draw again. I just wait for it
Click to expand...
Click to collapse
Yes, that happens, especially if there is some program running....
graphics: 1084
others: 1831
jpeg: 2286
games: 1284
sound: 0681
final score: 1433
Stock Tilt Rom, without the AT&T software.
The only mission I am on is to imporve the plight of the unhappy Kaiser owners.
Despite accusations of being an HTC spy etc etc, I just want to back up that my happiness with my device is due to it responding as fast as I need it to- which may also explain why HTC think the device is fast enough.
(Am trying to shoot vids now. Opera Mini will always take longer to redraw as its a java app inside a midlet mgr).
Sane said:
I just said on the classaction.org thread that i had a friends Ipaq 6915 for few days and the difference in speed, i.e. opening programs menu is obvious.
Click to expand...
Click to collapse
Just for the record, my fiancee's Wizard (used to be mine) is a faster when opening menus and redrawing the screen. Why? It's running WM5 stock ROM with almost nothing on it but basic functions. The today screen is empty. Only thing it has is S2U2 running on background (so that her purse doesn't keep calling me).
My Kaiser is filled with stuff, as you can see screenshots on my previous post in page 1.. and it's a it slower.. delay of 0.4 seconds doesn't bother me.
sharpja said:
graphics: 1084
others: 1831
jpeg: 2286
games: 1284
sound: 0681
final score: 1433
Stock Tilt Rom, without the AT&T software.
Click to expand...
Click to collapse
It seems that reflashing to Dutty's v3 ROM makes it a bit faster. And, splitting hairs, replacing ati_d3d.dll to the one from LG seems (judging by VS benchmarks) to make it a tiny little bit faster as well.
Really bad quality videos... sorry! Did them in a rush on my old sony digital camera. Focussing would have helped...
Switching in today - portrait to landscape is faster than I am! Back to portrait takes nearly a second.
Switching and scrolling through emails.
My "stock" Kaiser - ATT Tilt -with a few apps installed and running Hotsynch to get my corporate mail, I scored the following:
Test 1 - 1067
Test 2 - 1772
Test 3 - 2176
Test 4 - 1244
Test 5 - 0786
Final Score - 1409
I got 1441 after soft reset with HotSynch running to synch mail wirelessly, then removed hotsynch and got 1509.
So, I guess I need to go ahead and flash my ROM.
I am new to the site and have to start reading the threads and getting familiar, but to jumpstart me, is there a "best" or "most used" ROM and Cab config that is popular and stable amongst the group? I saw a touchflow video on youtube - do many of them have that?
Tom
pearsth said:
I am new to the site and have to start reading the threads and getting familiar, but to jumpstart me, is there a "best" or "most used" ROM and Cab config that is popular and stable amongst the group? I saw a touchflow video on youtube - do many of them have that?
Tom
Click to expand...
Click to collapse
Welcome, Tom =)
Most used ones are probably Dutty's v3 ROM and Alex's Home ROM. Also, many of our "most famous" cooks are testing and creating stable ROMs that run WM 6.1.. so if you want, you can just wait for a bit and reflash 6.1 ROM.
I'm putting up this thread because there is a good bit of questions that get asked about the 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, but I'm making this specific to the Rhodium as that is the only device I plan to support with benchmark results. I'm following the same pattern from the benchmark thread that was started HERE by daeron.be.
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:
14 March 2011: Finished benchmarks on 21689, 28245, 29011, 29013.
09 March 2011: New builds have begun rolling out. Testing begins tonight on 21687, 29008, and 29009.
...trimmed every month...
Results
I based these blank uncompressed ROMs on the latest shipped T-Mobile 6.5 ROM (1.91.531.4), 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 tested:
216xx: 21659, 21661, 21663, 21665, 21671, 21674, 21677, 21679, 21680, 21681, 21682, 21683, 21684, 21685, 21686, 21687
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
290xx: 29002, 29003, 29005, 29007, 29008, 29009
Custom ROMs tested so far:
NRGZ28 Energy: 21916, 21684, 28244, 23148, 23699 - Update coming soon!
Ondraster LBFAR: 21899, 23569
dotcompt DeepShining: Coming soon!
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
Method and relevant information
If you are planning to send me results or anything, be sure to include the version numbers of the programs you used. SPBBenchmark and Test OpenGL are both freeware. Coreplayer Mobile costs around $30.
Benchmark programs used:
1. SPBBenchmark 1.6
2. Test OpenGL 18.01.2010
3. CorePlayer Mobile 1.2.5
Test Method for blank builds:
1. task29 then flash the ROM without the SIM card.
2. The storage card is left in to install the benchmark cabs.
3. Go into airplane mode.
4. Disable switching screen off and turning the device off.
5. Install benchmarking apps
6. Soft Reset
7. Run SPBbenchmark and disable the following:
Built-in applications (whole category)
Arkaball frames per second
Copy 1 MB using memcpy
8. Run TestOpenGL for about 3 cycles of benchmarks (each cycle is 4 benchmarks) and then turn it off
9. Run three Avatar trailers, note down the results (%). Use default Coreplayer settings and run benchmark immediately after files are loaded.
Trailer found HERE. Note that trailers ARE copyrighted material and are NOT subject to fair use. The link provided is to show what I am using. I own the BluRay disk and ripped it from there. The link is also 720p. My original clip was 1080p. Each exported trailer was set to 800x480 resolution.
One trailer was converted to 25fps, 768 kbps - XHQ
One trailer was converted to 23.976fps, 512 kbps - HQ
One trailer was converted to 20fps, 384 kbps -MED
I wasn't able to determine the original qualities from daeron.be's thread, so I made my own. If you know more about it, please let me know for more accurate results.
10. Run Video Flash benchmark with PIE using a downloaded version of the animation found HERE. If you plan on doing this yourself, download it to your device and run it with IE. Just put it in a root dictionary (\) and then input \benchmark.swf address in IE. On some ROMs you might have to wait a while before the flash starts (there won't be any signs of loading). Run the benchmark (if you want your result to be compatible with mine you MUST run it with flash file in full screen).
11. Collect results
Test Method for Custom ROMs:
Same as above with three exceptions.
1. Run SPB Benchmark with ONLY "Built-in applications (whole category)" test disabled. Leave everything else on.
2. Connect the device to the PC after running the SPB Benchmark test. You may have to go to Start > Settings > Connections > USBtoPC and untick the "Enable faster data synchronization" box to get it to work.
3. Copy the "Spb Benchmark Results.xml" from \My Documents to the PC and grab the results from there with the decimals. I use every decimal in the file. I then trim the trailing zeros in the Excel results file.
I figure since some people will probably use this as a guide of which ROMs are "best" or "fastest," that the results should be as accurate as possible, which is why I'm including the decimals in the custom ROM results, but not in the blank builds.
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.
Requests
If someone wants to change the BG colors of the spreadsheet to something they like better, be my guest. If I like the colors, I'll keep it.
Please take the poll at the top of the page. If enough people use this thread with other devices, then I will consider moving it to the Chef's Central forum.
I am slowly adding custom ROMs to the results. I need a few people to notify me when the ROMs you're using are updated. This includes Energy, Simplicity, DeepShining, Core Cell, and other popular ROMs.
Custom ROM testing
Ask your chef if he/she would mind having their ROM(s) tested and compared in my results. See below for rules:
All custom ROMs would be separate of the clean builds, but compared all together.
Understand that once permission is given, it cannot be taken away. (I don't want anyone trying to revoke permission after results are posted to take advantage of my system.)
Have the chef PM me with the green light if they want it included.
All results will either be performed by me, or verified by me.
I will not measure battery performance. See FAQ.
These results are not conclusive to picking a "good" ROM. It's a jumping off point. Test yourself and see which one works for you. This tests certain factors of the ROMs. This doesn't test for stability or feel of the ROM. Do that yourself.
Chefs are allowed to "pick and choose" which ROMs they want tested. If they cook multiple flavors or builds, they can decline to have certain ones excluded from results.
If you have a problem with my methods, you are welcome to do them yourself. I am doing my best to ensure that this is as objective as possible.
Contact
If you feel like contacting me or need to request info or whatever, you may PM, e-mail, or message me on Twitter.
Donate
Coffee keeps me cranking out results. DONATE to keep the caffeine flowing. If I see that you've donated, I will probably take a bit more care in listening to your problem/suggestion/comment. Make sure that you include your XDA user name so I can give you credit.
beautiful... cant wait to see results
Subscribed.
Imho you should test blank WM builds. Or at last be sure that the EXT/XIP packages are same. However the idea of testing different builds fits me.
Shame that usually the fastest builds leak memory like hell.
Jackos said:
Subscribed.
Imho you should test blank WM builds. Or at last be sure that the EXT/XIP packages are same. However the idea of testing different builds fits me.
Shame that usually the fastest builds leak memory like hell.
Click to expand...
Click to collapse
I used to believe that until we started seeing the 21680 and 21681 builds come out. They really are quite faster than most of the others. When NRG was using the 23xxx builds, that was the case where the faster they ran the more memory was "spirited away," so to speak. I'm finding a much more stable experience with the 21680 and 21681 builds than most that I've seen.
In any case, the results will speak for themselves. The first three should be posted in a few hours or so.
For anyone who missed it, I've posted the first test file. I only did a single test for each one. In the future I will do an average of three results per test. I only did a single one due to time constraints mostly. That being said, this first file is just a test both for me and for anyone viewing to get a feel for what it's going to look like.
Any questions; let me know.
cajunflavoredbob said:
Requests
The first thing I could use help with to speed up my testing is for someone to point me to the reg key that disables Sense. This would make it easier for me to just drop it into XDA_UC to have the changes made automatically.
[..]
Click to expand...
Click to collapse
This isn't a reg key, but I think there are mortscripts that disable Sense. Maybe this might help?
http://forum.xda-developers.com/showthread.php?p=8684203
I think JVH3 talked about scripts that disable sense too, so perhaps he might be able to help you out there too?
Great work, this is really interesting!
Using mortscript you can do this:
Code:
RegWriteDword("HKLM","\Software\Microsoft\Today\Items\" & ManilaName,"Enabled","0")
RedrawToday
Sleep(5000)
ManilaName is usually HTC Sense, I think. The sleep can probably be shortened. Nice thread!
why not just build a rom free of all ext packages?
just sys and oem packages.
that way it is a better comparsion of sys builds.
no?
sh4d0w86.
cajunflavoredbob said:
The first thing I could use help with to speed up my testing is for someone to point me to the reg key that disables Sense. This would make it easier for me to just drop it into XDA_UC to have the changes made automatically.
I could also use the reg key that sets the device into flight mode for the same reasons.
Click to expand...
Click to collapse
Disable Sense:
Code:
[HKEY_LOCAL_MACHINE\Software\Microsoft\Today\Items\HTC Sense]
"Enabled"=dword:0
Flight mode on boot:
Code:
[HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\Power\State]
"Phone"=dword:00000000
[HKEY_LOCAL_MACHINE\Software\Microsoft\RIL]
"LastEquipmentState"=dword:00000001
[HKEY_LOCAL_MACHINE\System\State\Phone]
"Status"=dword:00400030
"Radio Ready State"=dword:00000000
Random offtopic: I believe that all roms should have the radio turned off by default.
Jackos said:
Random offtopic: I believe that all roms should have the radio turned off by default.
Click to expand...
Click to collapse
I'm curious, why?
seeM_ZA said:
I'm curious, why?
Click to expand...
Click to collapse
Because not anyone wants to run the Connection setup after rom upgrade? Not anyone wants to get all those sms messages right after flash. It's just more convenient then taking the sim card out and putting it back into the device when you're ready (not healthy for the card too).
Not to mention the CDMA phones without simcard, having the radio enabled by default in ROM must be a pain in the ass if you flash several times or hardreset to test different software!
Excellent work on this, cajunflavoredbob!
I look forward to reviewing the results that you come up with on your comparisons.
I am already interested in some of the results that you found in the first tests and will watch that pretty closely.
One thing that I noticed - when I first opened the spreadsheet the colors pretty much come on like a freight train - can those be toned down a tad? These old eyes finally adjusted to them but a lighter shade of colors may be more aesthetic...
Thanks for this contribution!
sh4d0w86 said:
why not just build a rom free of all ext packages?
just sys and oem packages.
that way it is a better comparsion of sys builds.
no?
sh4d0w86.
Click to expand...
Click to collapse
If you read the first two posts, I addressed this twice. That's what I plan to do. I need to get a feel for this myself and find ways of doing it quickly before I move on to the kitchen.
Jackos said:
Disable Sense:
Code:
[HKEY_LOCAL_MACHINE\Software\Microsoft\Today\Items\HTC Sense]
"Enabled"=dword:0
Flight mode on boot:
Code:
[HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\Power\State]
"Phone"=dword:00000000
[HKEY_LOCAL_MACHINE\Software\Microsoft\RIL]
"LastEquipmentState"=dword:00000001
[HKEY_LOCAL_MACHINE\System\State\Phone]
"Status"=dword:00400030
"Radio Ready State"=dword:00000000
Random offtopic: I believe that all roms should have the radio turned off by default.
Click to expand...
Click to collapse
Wonderful! Thanks. This will save some time! I agree with you on the radio being off by default. With the number of times I flash my device during the week, it would really help not to hear the alerts going off twenty times when I start up. I use NRG's ROMs by day, backup with Sprite Backup, and then toy with my personal ROM at night normally. Now, of course, I'm going to be flashing even more than that with this new project.
toucan said:
Excellent work on this, cajunflavoredbob!
I look forward to reviewing the results that you come up with on your comparisons.
I am already interested in some of the results that you found in the first tests and will watch that pretty closely.
One thing that I noticed - when I first opened the spreadsheet the colors pretty much come on like a freight train - can those be toned down a tad? These old eyes finally adjusted to them but a lighter shade of colors may be more aesthetic...
Thanks for this contribution!
Click to expand...
Click to collapse
I can't promise you that I'll get to it, but I'll put it on my to-do list. I basically stole the formatted speadsheet from the other thread. I was about 2/3 of the way through with making my own, when it dawned on me that there was probably one already made. Their formulas covered some things I hadn't yet thought of, so I'm going to be using this for a while.
In other news, I'll be working on this again today, so check for updates tonight. I'll post any updates in the second post.
cajunflavoredbob said:
To-Do List
Change crazy background colors on spreadsheet.
Build clean ROM based on latest T-Mobile shipped ROM
Clean up first post.
Finish learning Italian.
Click to expand...
Click to collapse
One down (see attached).
piaqt said:
One down (see attached).
Click to expand...
Click to collapse
Thanks, but I still need the backgrounds. It helps me find the fields more easily. I'm going to experiment with different colors soon. This isn't my top priority, though. I think, lighter, not brighter colors would do better. We'll see what happens. I'm working on cooking the new ROM right now. Well, not right now, but I'll be starting soon. Hopefully I can get this completed within the week. I can only flash/work at night on this as I need a functioning device during the day.
cajunflavoredbob said:
Thanks, but I still need the backgrounds. It helps me find the fields more easily. I'm going to experiment with different colors soon. This isn't my top priority, though. I think, lighter, not brighter colors would do better. We'll see what happens. I'm working on cooking the new ROM right now. Well, not right now, but I'll be starting soon. Hopefully I can get this completed within the week. I can only flash/work at night on this as I need a functioning device during the day.
Click to expand...
Click to collapse
Haha... I wholeheartedly agree - it is absolutely necessary to have the colors - but perhaps not so bright!