yashsingh1/xdaforums huggingface dataset:
[Touch Pro2, Tilt 2 Windows Mobile ROM Development] cajunflavoredbob:
Results for 23152 and 29007

Here are the results for 23152 and 29007. 23152 wasn't very impressive, but I found 29007 to be quite snappy. Video wasn't as spectacular on 29007, though.

UPDATES:

Please take the poll at the top of the page. I need to see whether I should move this thread to Chef Central or leave it here. I originally thought it would be Rhodium specific, but a few other users have made comments to me who have other devices.

I will begin downloading DeepShining ROMs in a few minutes to test them.

I need a few people to notify me in the thread when new builds are up for the custom ROMs I'm testing. I can't actively monitor all the threads, so it would be nice if a few of you could call dibs and monitor some of the custom ROM threads.

I am looking into purchasing a HTC HD2 in a few weeks. Once that happens, I will be able to devote more time to testing as I won't have to swap SIM cards with a different device. I kind of want an Android device too, but I've spent a while in the forums over there, and the flame wars are ridiculous, so I'll probably wait a while on that.
[Touch Pro2, Tilt 2 Windows Mobile ROM Development] cajunflavoredbob:
It's getting more and more difficult to do these benchmarks. I'm sorry to say that I have to put it on hold for a bit while I finish up some work in real life. If anyone has a spare device to donate, then I could do this very easily, but seeing as all I've got at the moment is this one device, flashing on it is only possible for me in the evenings. I need to have a working phone during the day to conduct business. I am planning to grab a HD2 in the next month or so, and that might help out, but until I get a second device, I don't think I'll be able to do much of anything here.

I do still have plans for this project, so don't think I'm abandoning the thread. I still want to be able to test custom ROMs, as that was my original intention for the thread. I also plan to open a new thread in Chef Central with this same information, but with more detailed SYS results like you see in the custom ROM results. I would also like to include a comparison of the latest blank builds in that thread. This thread here will be more for benchmarking custom ROMs and such.

Again, sorry to bring such disappointing news, but that's the way it works. I really wish someone was generous enough to donate the money to purchase another device, or donate/sell cheap a used one. I will try to post when I can in here, but even weekends are semi-booked for a bit. Hopefully things level out soon, or perhaps I can get some more help with work if it remains this busy. Time will tell.

-CFB
[Touch Pro2, Tilt 2 Windows Mobile ROM Development] TechKit:
build question

Hi cajunflavoredbob,

After doing a little study on the benchmark masterlist, I was just wondering why the chefs aren't using build 23667 or 23691 (23667 with better results). Reading the above quote gives a little insight but was it because of the memory loss? The reason I'm asking is that I cannot find any ROMs based on these builds by energy, deepshining, etc. (possibly i'm not looking correctly).

Its just that i'm a nut for performance and the rhodium ain't a powerhouse with winmo on it, lol:) (also, 23667 stacks up very closely with 28244, which i really like)

Regards,

-Techkit
[Touch Pro2, Tilt 2 Windows Mobile ROM Development] cajunflavoredbob:
You could always build your own ROM with the build you want in it. That's what I did. I didn't like the move away from 28244 in Energy ROMs, so that provided me with the motivation to finish working on my personal ROM. I like the way it came out so far. It's been a long time since NRG use 23xxx in a ROM. I think he transitioned to another branch back in October or September or something.

As far as the memory leak goes, several users have their theories. I believe it really comes down to the s***ty drivers for the Rhodium. The Raphael runs the same ROMs with relatively no memory issues like we have. (Raphael = Original Touch Pro) Memory is leaked like a sieve in any ROM on this device. Some of the builds do a better job of holding it in, but some packages like, gwes.exe and manila.exe, do piss poor jobs of freeing up memory once they're finished with it.

As a fun fact for you, the main reason there were ever multiple start menu options in NRG's ROMs were because of the memory leaks on the Rhodiums. Other devices don't have this problem as badly as we do. It's a constant struggle to contain as much as we can until someone figures out how to solder on another gigabyte of RAM on this thing.
[Touch Pro2, Tilt 2 Windows Mobile ROM Development] TechKit:
I fully agree with you, the drivers for the rhodium have been sorely neglected and it shows to the point where people are writing driver packs... As far as adding ram to the phone, thats not such a bad idea...:p

on a separate note, I had my eye on the upcoming HD7 pro, but i'm not sure if i'll make the leap now if it has similar issues, wp7 or not. Mind you, i'll consider it if there are energyroms...lol

Also, would you be interested in posting your rom? I haven't got a clue how to make them and I got more confused just trying to find the files as (some of) the download links dont work (doesn't help if you dunno programming also :)).

Thanks again,

-Techkit
[Touch Pro2, Tilt 2 Windows Mobile ROM Development] cajunflavoredbob:
If you want some more info on WP7 HTC 7 Pro, you can head over to THIS THREAD to see what others have posted about it.

To get started cooking your own ROMs, head over to CHEF CENTRAL to learn about it. As long as you read and search before posting, there are tons of users, including myself, who will guide you in the right direction.

I will probably not post my personal ROM as it is now. The way I have it set and themed, I doubt many would like. I may release a ROM soon, though. I need to get a secondary device to handle my business on while I do that stuff on this one. I posted a screen shot in the Energy ROM thread of my homescreen from it a while back when I showed the diagonal swipe gestures on CHT.
[Touch Pro2, Tilt 2 Windows Mobile ROM Development] TechKit:
Hi, CFB,

Thanks for the info, I had a deep dive into the threads and info there and found huge amounts of valuable info. I have no idea what i'm doing though, it looks like one of those things where there needs to be classes tought in a school...lol. I had a look at the different kitchens, hyperkitchen, instructions, posts, etc... and it leads me to think I should step back a bit, its quite overwhelming even with the instructions and just using one or two of the kitchens.

I'll leave it to the people who know what they are doing I think, before I screw my phone and bury it out the back:rolleyes:. I would love to see an energyrom attempted on the 23667 build if possible, or at least an update to the energy 28244 (really keen on the 23667 though, love to see how it works out):).

I'll leave my ranting there I think, I seem to have gotten good at it lately as well as thinking out loud:D, lol.

Regards,

-Techkit
[Touch Pro2, Tilt 2 Windows Mobile ROM Development] cajunflavoredbob:
New builds finally.

Well, I've gotten my hands on a few new builds. I'm building them into ROMs right now and will post results when I finish. There are three of them that I have right now, but several more will be coming soon. First up is 21687 and 29008. Check back later for the results.

EDIT:

Two new builds have now been tested. I like 21687 very much. It's very fast. 29008 wasn't bad, but I'm still not particularly fond of the branch.
[Touch Pro2, Tilt 2 Windows Mobile ROM Development] wmg316:
I'm looking at the stats, and it appears that 29008 rates better across the board except on the video tests (actually kill the video tests, and 29008 overall performance is higher than 21687).

Will you expand (if you have a minute) on what makes 21687 better in your opinion? And why your not fond of the 29xxx branch?

Thanks!
[Touch Pro2, Tilt 2 Windows Mobile ROM Development] cajunflavoredbob:
I can upload the blank ROMs if you would like to test them. I found that 21687 was considerably faster in scrolling, and opening files. 29008 lagged a bit more and required a stiffer press on the screen to get it to scroll fluidly. It wasn't a big difference between the two, but I prefer 21687 between the two of them. I'll be testing 29009 and 29011 later tonight or tomorrow. I've also got a review of Wild Child's Illuminati ROM coming.
[Touch Pro2, Tilt 2 Windows Mobile ROM Development] Jackos:
Hey Pringles package!

Just a quick question, as you're expert in WM builds:

28236 vs 28244

Still cannot decide between those two builds. From tests it appears that 28236 is faster then 28244, but does speed come together with stability? Can elaborate this a little bit more?

Thanks for your time and hard work,

Jackos
[Touch Pro2, Tilt 2 Windows Mobile ROM Development] cajunflavoredbob:
I'll run them side by side for you tonight or tomorrow. I'll even do a detailed run down, since you made me laugh. :D

It's been a while since I've done those, but I really like 28244. I know that some chefs reported errors and instability in the 282xx branch, but since I don't test EXT packages, I didn't get their errors. I've cooked it into my personal ROM with excellent results, as has NRGZ28. The only other branch I like as much as that one is 216xx.
[Touch Pro2, Tilt 2 Windows Mobile ROM Development] Jackos:
I'm actually running 28244, no issues so far. Of course I had to patch/mix a lot of EXT packages.

Both builds run quite well, just curious if there is anything I should be aware off.
[Touch Pro2, Tilt 2 Windows Mobile ROM Development] cajunflavoredbob:
There aren't any problems that I noticed with the SYS and OEM packages. I don't use the EXTs in testing, but I had to mix some as well with my ROM to avoid some problems. It was simple enough, and I find the build to be one of the fastest available. I think that 21687 gives it a run, though.

Between 28244 and 28236, I think the only difference you'll see is going to be performance. I'll have to run the numbers and flash them again, but I do remember 28236 being the faster one of the branch.
[Touch Pro2, Tilt 2 Windows Mobile ROM Development] EVEALEX62:
Hello cajunflavoredbob

Thanks a lot for this works, it is a very good idea ;)

Can you running test with 29011 and compare to 29007 please ?

Thanks in advance.

Best regards
[Touch Pro2, Tilt 2 Windows Mobile ROM Development] cajunflavoredbob:
Update

Ok, so I'm extremely busy right now finsihing up more work than I thought I had. I'm going to do my best to get the rest of the new builds benched this weekend, but I'm not promising anything. I've got a HD2 on its way to my front door soon, so that'll help out a while lot. Sorry guys, just be patient with me on this.
[Touch Pro2, Tilt 2 Windows Mobile ROM Development] cajunflavoredbob:
21689, 28245, 29011, 29013

I'm tired, so I'm not posting a big review. Suffice to say that 28245 came out WAY on top. 21689 was nice as well. I'm still not big on the whole 290xx branch, but they both did ok. 29013 was a bit slower than 29011, but not by much. The start menu was kind of jumpy on 29013.

I'm planning to finish up a couple of requests for people as well as finish up the detailed results for the latest builds. I'll explain more later. I've got a review of Wild Child's Illuminati ROM coming up soon. I just need to put my outline into a review. I also need to finish that 28236/28244 comparison for Jackos. I think my HD2 comes in tomorrow, so I'll be busy all evening, I think.

Enjoy the results.
[Touch Pro2, Tilt 2 Windows Mobile ROM Development] wmg316:
Any more benchmarks? 29018 or 29019? Or 21690? (Waldo)
[Touch Pro2, Tilt 2 Windows Mobile ROM Development] cajunflavoredbob:
Yea. There are four or five new builds that are trickling out right now. I can't actually do the testing on my Rhodium at the moment, though.

I began redoing the benchmarking on my Leo a couple of days ago. I'm still in process of cooking them all up again, though. The new thread is in Chef Central. I will still update this one, but probably not for a while. Either that, or I'll just do a benchmarking thread for full ROMs or something. I really haven't decided yet.

[PRJ] Latest WM benchmark results
[Touch Pro2, Tilt 2 Windows Mobile ROM Development] cajunflavoredbob:
I've made the decision to abandon this thread. It doesn't seem to make since to have two threads dedicated to the same thing. If anyone is interested, I also do reviews every now and then in the [Resources] Rhodium ROM Repository thread.

I could benchmark ROMs for you guys, but it would need to be more involved than this thread is. I mean more involved from the community in requesting ROMs to benchmark and compare. It didn't seem to be very popular or useful for me to compare custom ROMs anyway, so it's up to you guys. If you would like me to continue benchmarking custom Rhodium ROMs, then I guess I still could do that, but only if you guys want me to. Otherwise, I'm just going to ditch this whole thread.

If you want to follow the new thread, I'll have updates posted in there soon, I hope. My replacement Rhodium finally came in, so I can begin benchmarking on the Leo now. I'm not going to begin tonight or tomorrow night, but I hope it will be soon. I'll be doing the 290xx branch first, since everyone is using it.

[PRJ] Latest WM benchmark results
[Touch Pro2, Tilt 2 Windows Mobile ROM Development] monomer888:
Thanks for the work you've put in to benchmarking the builds, I'm sure many people are appreciative of your work, but only just lurk so haven't said anything.

Just out of curiosity, do you think your replacement Rhodium will benchmark at the same scores as the one that broke (on the same SYS builds)? :)
[Touch Pro2, Tilt 2 Windows Mobile ROM Development] motisu:
Like the man said, there are plenty of followers (I think :)) but don't have anything contributory to say. I, for one have followed this thread since the beginning. I guess that as long as there is a thread that does comparisons, even if not for exactly the same hardware, that should give us enough knowledge to make an educated guesstimate of what to expect from a given ROM.

P.S. I am also curious if the new Rhodium will perform the same as the old one or if they slipsteamed improvements without telling anybody.
[Touch Pro2, Tilt 2 Windows Mobile ROM Development] cajunflavoredbob:
Even if you guys tried to benchmark the same exact builds as mine on your devices there would be a bit of variation. I've always maintained that anything less than 5% variance is acceptable. Obviously, overclocking isn't a factor here, though. It may also vary more depending on the custom ROM installed at the time.

I can try a couple to see if they stack up with this new one, but I've had it replaced before with no noticeable difference in performance, except for the orientation switching more quickly for some reason on my last one.

In the new thread, results are going to be higher than in here. I've already seen a handful of results that I haven't reported yet. I'm working right now on some business matters, so I'm really hoping to put out the 290xx branch this weekend if I can. My current goal is to benchmark one branch per week.

I was also thinking about starting a contest for developers and chefs to build their own. I know that Wild Child mixes and matches parts of builds to make the most out of them. Perhaps if a reward is issued, other chefs may be more inspired. That won't happen anytime soon, though. I need to concentrate on getting the benchmarking done again, so I can go back to cooking. I miss the feeling of using a ROM that I actually created.
[Desire Q&A, Help & Troubleshooting] -=Fire4Effect=-:
Recently rooted HTC Desire (CDMA). Still running the stock rom, just wanted to remove some of the bloatware on my phone. I installed Titanium Backup, ran a batch to backup all apps+system data. I uninstalled City ID, rebooted, and just for fun I went back into TB to see if I could restore it. To my surprise it wouldn't let me. Next I tried uninstalling the reddit app. Rebooted and it allowed me to restore that one. Does TB not restore apps that came pre-loaded on the phone?
[Desire Q&A, Help & Troubleshooting] Cyanoid:
I prepared my 8gb SD card (that came with the Desire) to receive LeeDroid's well-loved Froyo ROM, using ROM Manager. I specified 512mb for the EXT and 0mb for the swap. Windows shows 6.92GB free. I understand it can't see the Linux part, but the Quick Info app and HTC sees 6.92gb. Shouldn't they see about 7.5gb? Where did the 512mb go? How can I even check if RM put a 512mb EXT3 partition on the card (oh... I don't do Linux!).

Should I go ahead with the A2SD LeeDroid install or worry some more?

(Btw... my username is for sale. But if anyone wants it to name a ROM they created... I give it for you gratuit :D ).
[Desire Q&A, Help & Troubleshooting] viva.fidel:
An 8GB SD card only really has 7.456GB of usable space

Quick System Info, the phone and Windows all see the FAT partition of the card, so when they report 6.92GB it's accurate

That 512mb missing shows that the ext3 partition was successfully made, it should be reported as 512MB free in the A2SD storage bit in quick system info
[Desire Q&A, Help & Troubleshooting] Cyanoid:
Thanks. In A2SD storage in QI it says "Information not available". But could that be because I have not yet installed the LeeDroid ROM, and am still on the original Android 2.1 the phone came with?
[Desire Q&A, Help & Troubleshooting] viva.fidel:
Most likely yes, a custom ROM that supports A2SD+ creates symlinks between the internal storage and the sdcard, as these obviously aren't there in the stock Eclair rom then there is no link to the ext3 partition and free space isn't being calculated.
[Desire Q&A, Help & Troubleshooting] Hungbi:
After partitioned my SD card, Quick system info shows me that A2SD storage only have 113MB. I checked with Windows 7 disk manager and see that there is a 488MB linux partition. So where is the rest space? Could any one help me out?
[Desire Q&A, Help & Troubleshooting] Meaple:
You want something that can read sd-ext like root explorer and that will tell you. A2SD is weird and it depends on how the scripts and stuff are done and installed. Sometimes you can look in storage settings and it will tell you there, sometimes you use an app like Quick System Info, and sometimes it is just useless and won't tell you. If you have an SD card partitioned with a primary FAT32 partition first, then a primary ext3/4 partition second, it will work.
[G2 and Desire Z General] waiting89:
How do you factory reset, I try power and vol down and it kinda work, but then idk what else to do. can someone please help me out?
[G2 and Desire Z General] jashsu:
Settings > Privacy > Factory data reset

It's the same as performing a reset from recovery. Wipes /data and /cache
[G2 and Desire Z General] waiting89:
For real? I tho it wasnt the same thats why I didnt do it. like it will remove apps install on my SD and everything??
[G2 and Desire Z General] waiting89:
I still want to do it the recovery way how is it done?
[G2 and Desire Z General] ddgarcia05:
You could remove the card before doing the reset. I did a reset to mine last night. I had a 6 set temp root which I think would break the 1 click-tempt root when I tried to run the app. The reset fixed that up real nice. Now I have the 1-click tempt root running, my wifi tether started working again after it stopped working with the 6 step tempt root.

I also swapped out my 8gig card for the HD2's 16gig class 2 card and it working very good. I couldn't be happier. I used app control to backup my apps (sucks to reinstall cuz you gotta do it one by one.) Now I have titanium backup, I hope it works should I ever need to use it.
[Motorola Droid and Milestone General] DexterFichuk:
Ok so yes i am going to pay $20 to whoever knows how i can fix this problem i am having, i've flashed my droid to the network tbaytel, Everything works except for incoming texts which i need to work. The only way i can get them to work is if i use the zeusdroid rom and for thsoe of you who don't know what it is, its the htc desire rom thats been ported to the nexus one then ported to the droid. So its because of that that it's slow, buggy and i can't get data. i've tried alot of solution including changing basebands ( including to the brazalian one), i've tried different settings and im nto sure if it would be apn but my networkdoesn't have an apn for android yet. so yes if you know what it could be or have any ideas please tell! thank you
[General Questions and Answers] rad1ant:
I was going through the market & seeing nes,snes,gbc and psx really brought back memories *sniff*. I was wondering if the sega dreamcast would run smoothly on the xperia x10i.. would love to play crazy taxi/sonic/tekken roms on this!
[General Questions and Answers] rad1ant:
...or if it would run at all?
[Vibrant Q&A, Help & Troubleshooting] mmas0n:
I searched and didn't see any threads related to this yet, so please forgive me if this has been covered. Is there a way to adjust the brightness of the LEDs behind the 4 buttons on the bottom of the Vibrant? I have seen this touted as a positive feature in articles comparing the Vibrant to the Captivate, but I'd actually rather they were dim or have their brightness linked to the screen brightness setting.

Cheers.
[Vibrant Q&A, Help & Troubleshooting] }{Alienz}{:
Where did you read that?

I've never heard of this until now and I'm a regular on XDA. Love your idea though :)
[Vibrant Q&A, Help & Troubleshooting] mmas0n:
I edited the OP without re-reading and before submitting and it may have resulted in some confusion. It is a fact that the buttons are brighter on the Vibrant than on the Captivate. I have read at least one comparison article where this was touted as a positive feature (although I've also read where it was called out for being distracting, as it is for me). I did not mean that I had read anywhere that the brightness could indeed be adjusted on the Vibrant.

Not sure how you interpreted the OP, but thought I should clarify anyway.

I think there are two options here:

1) The Captivate uses a fixed resistor to limit the brightness of the LEDs

2) The Captivate simply takes advantage of a programmable VRM to limit the brightness of the LEDs

If it's option 1, well ... ****

But if it's option 2, I REALLY hope somebody figures out a way to access it.
[Vibrant Q&A, Help & Troubleshooting] All~G1:
I think if someone had figured how to access it w would have a LED notification by now.
[Vibrant Q&A, Help & Troubleshooting] mmas0n:
Not exactly. Flashing a chip once to use a different voltage at all times is not the same as interfacing with it to allow for flashing notifications.
[G1 General] imar3l:
Hi,

I've followed the guide on this page

How to Root Your T-Mobile G1 Without Bricking from factoidz (can't post the link here!!!)

and i got the g1 to work pretty ok, still under testing..but the volume buttons on the side does not work anymore...I do have sound and i can adjust the volume through the settings but not physically from side buttons...

appreciate your help...:D

btw, what are some better roms for g1 since the September release...