yashsingh1/xdaforums huggingface dataset:
[G1 Q&A, Help & Troubleshooting] XBrav:
Oh trust me, I've been very aware of the Rogers / Chatr connection since the beginning. WIND was very difficult in giving me answers why they put up coverage for my area, but won't turn on the towers. Plus, their 3G is shotty.

If you remember, all Canadians want are lower rates. We don't care who offers them, as long as they are lower.

WIND only uses AWS 2100, and I didn't want to buy a new phone. So I took it to Chatr.

WIND's footprint is also missing half of SW Calgary, where I need it the most, and they couldn't even guarantee a continuous signal on the C-Train line.

Simply put, WIND launched their network prematurely.

Thanks for criticizing me, and completely dodging my question again.
[G1 Q&A, Help & Troubleshooting] lbcoder:
You need to BUILD the towers before you can turn them ON.

"shotty"? B.S. Only if you BELIEVE THE LIES that DIPSH** SPREADS.

And you won't be GETTING lower rates unless you SUPPORT COMPETITION!

1700/2100, and you can pick up an android phone from wind for $160.... and this would SAVE YOU IN THE LONG RUN since AS I SAID, what you are paying for now, will vanish the SECOND it is no longer needed.

AS IS CHATR!!!

The footprint is IDENTICAL because CHATR is ARTIFICIALLY REDUCED!

** and you obviously did NOT look up the fact that WIND will ROAM ON ROBBERS in areas without coverage.... for LESS THAN CHATR CHARGES FOR THE SAME PRIVILEGE EVEN THOUGH THEY OWN BOTH SIDES!!!

And good luck getting roaming notifications.... At least a phone on Wind will TELL you when you are paying extra!

And guess what? NEITHER WILL ANYONE ELSE!

They DID NOT. Their network is FAR more reliable than butt-munch EVER was. You can actually hold a call for more than 2 minutes without it dropping!

When you do something stupid in public, you WILL GET CRITICIZED!
[Droid Eris Q&A, Help & Troubleshooting] jjchambers:
Just started reading about my Eris today and all the "aftermarket" stuff I can do with it. I've spent the last couple hours reading through here and androidforums but can't find the exact answer I'm looking for.

I did the "HTC Eris 1 Click Root App" and all went well. I've also installed SetCPU from this site. I'm sure there is something else I have to do b/c SetCPU is giving me no options to go above 528. It appears I have to install a patch of some sort from this thread: (can't link but it's the "Overclock Patch and update.zip" thread in the Eris development area) but do I install the patch.txt, the zimage or update and what do I do after they are installed?

I've read plenty of talk about other ROMS's but I'm fine (for now) with the stock one. Can I OC without installing an entire new ROM?

Thanks in advance!

J
[Droid Eris Q&A, Help & Troubleshooting] Captainkrtek:
you need to flash an overclockable rom, try flashing this one:

http://xdaforums.com/showthread.php?t=679194

or

http://xdaforums.com/showthread.php?t=745708

those are just two of the many roms, if you need help flashing it dont bother making a new thread, do a google search, look on the xda wiki, or PM me.
[Droid Eris Q&A, Help & Troubleshooting] jjchambers:
After doing some more reading I would like to find a ROM that OC's above 700 automatically, removes the extra garbage that Verizon loaded (footprints, amazonmp3, etc...) and is a one stop shop. It looked like both of those you linked have some things missing or there are other step once you initially flash it.

When I do flash a new ROM I loose everything right? I'll have to re-load all my aps and stuff...

I'm going to go try and read up on flashing, NANDing and backing sutff up but will probably end up PMing you to make sure I got it all right.

Thanks!

J

P.S. had to remove your links so I can post my response.
[Droid Eris Q&A, Help & Troubleshooting] jjchambers:
Also, what's the difference in a ROM that has "sense" and one that doesn't? What am I missing or gaining?
[Droid Eris Q&A, Help & Troubleshooting] orkillakilla:
Sense is HTC's custom user interface. It consists of a custom theme, app launcher, and many different apps and widgets. The best way to find out what you are gaining and losing is to try out a sense rom and a non-sense (or "vanilla") rom. Always do a nand backup before flashing new roms. You never know what could go wrong.

As for the overclocking, the kernel the rom uses determines if you can overclock and how high you can go with it. Most roms are clocked to 710 as this is the highest and most stable speed that will work for all eris's. Some phones are able to get up to 804 without freezing or crashing but not all can. DO NOT check set on boot till you find a stable speed or you can get stuck on a boot loop.

Feel free to pm me if you have any more questions. I'm not a dev but I'll try my best to help you out.

Sent from my leaked rooted HTC Droid Eris with Sense-Able 3.1 using Swype
[Droid Eris Q&A, Help & Troubleshooting] TheSonicEmerald:
Best results come from doing some work yourself :)

Sent From My Eris w/Tainted Tenzo +LP Plus
[Droid Eris Q&A, Help & Troubleshooting] jjchambers:
sent you a PM Orkilla
[Desire General] brianius:
Sorry for starting a new thread, but found nothing exactly by searching...

I've read that, if you not debrand,

but root with unrevoked + newest radio + rooted 2.2 rom,

you will not be able to debrand anymore!?!

Is that bull**** or is there really a problem with the new rom or radio?

Thanks in advance for every hint!

edit: solved, is bull**** like I said!

Sent from my HTC Desire
[Vibrant General] stoanhart:
Hi guys,

I have an unlocked Vibrant from TMobile, using it on WIND in Canada. On the first day with a WIND SIM, I was able to see the WIND network, and use data as expected. Then I went to school (outside coverage) and the phone roamed to the "WIND Away" (ie: Rogers) network, as expected. However, when I re-entered the coverage area, I could no longer see the WIND Home network! I've been stuck on roaming for a few days now, and I just can't see the home network. I've scanned the for Network Operators a million times - all I see is WIND Away!

My girlfriend has the same phone, and we got her unlock code yesterday. After unlocking, she was immediately on WIND Away, too. I don't see others complaining on the WIND site, so their network must be up. What could cause this? Does Android cache the network operator list, or do some sort of automatic filtering that I can disable? This is getting pretty frustrating.

Thanks!

edit: Oh, I've tried power cycling and removing the battery.
[Vibrant General] stoanhart:
Bump?

Also tried a factory reset... What could cause the phone to simply not see a network that I know is present and that it used to see? I live less than a block from a tower.
[Desire Android Development] nolimit966:
Hi, is there a Generic 2.2 rooted rom available for the desire?? Thanks

Sorry. i have found it. please delete.

Thanks you
[Desire Android Development] kmetek:
just adding question

is there generic 2.2 rooted rom + app2sd+ ?
[Desire Android Development] snapilica2003:
the closest one to what you want is IEFtm's ROM. It only has root w/busybox, ap2sd+, OpenVPN with tun support and Wi-Fi N. It's not even deodexed so i belive it is as close to stock as possible.

If AP2SD+ is not necessary for you, you can try Paul's pre-rooted stock ROM's over at Modaco. That one only has root and nothing more (but there's version deodexed and non-deodexed)
[Desire Android Development] kmetek:
still nobody explained what is deodexed, thanks :P
[EVO 4G General] nief1313:
additional details on test:

The first part of the table is to test the rom with the stock kernel.

The second part is to see how well it performs oc/uc.

This is supposed to show how well a ROM performs by itself and how well it works while oc/uced since a lot of us do use custom kernels.

On all of the tests, there should be no widgets or apps installed that didn't come preset with rom(excluding setCPU, fps2d,quadrant, and linpack). This should help eliminate variability of what apps different users have.

On all the test (performance or battery) if the rom has preset profiles they can use them as long as it doesn't require a reboot or any 3rd party apps. all these profile should be mentioned though in additional notes.

I said no profiles on the battery test, meaning no setCPU profile due to variability of profiles.

All ROMs will be using sense except CM6

Update 8/6: Updated the spread sheet and put it up and google docs Niefs Rom Comparison

There are now explanations of the tests and I am going to start testing today. Also, looking for testers.

I have posted my scores for part of Fresh.

update: 8/12

Most ROMs are completely filled out under features

Most performance test have been ran

Few battery tests

http://i996.photobucket.com/albums/af90/nief1313/test.jpg
[EVO 4G General] seventyfive:
I think it will be a great idea... google docs might be a good way to let people collaborate, otherwise some kind of wiki.

Might be easier to organize by features such as "stripped of sprint apps" or "added X app" vs things like battery and performance which can sometimes be highly variable by device. Also, if you run performance I would maybe do a baseline of 998mhz (since we all know we can hit this clock) and then another showing oc'd (since some people can barely OC one tick).

I think there are enough people across all the roms that if the spreadsheet were public you'd gather a lot of data. I also have NAND backups of a few of the froyo roms so it wouldn't be hard to boot into recover, reflash a nand, run the benches, then reflash back to whatever i was on.

The battery ones will be a little tough #1 cuz i'm not sure how many people wanna completely lock up their phone for several hours waiting to see how long it lasts. #2, depending on how some people's batteries are calibrated and what they're running in the background, MMV.

Great idea tho!!! I think the ultimate key is thinking of a good way for everyone to easily submit their data. Anyone have suggestions?
[EVO 4G General] toastcfh:
u could add it to our wiki and update it like monthly. idk just an idea
[EVO 4G General] AlkamistStar:
Looking forward to it

This is a great idea, and i look forward to seeing this list grow. This could really help someone new to Android like me.
[EVO 4G General] nief1313:
I think adding it to the wiki would be really nice. I will try to come up with a spread sheet that only a few can edit(I don't want one person to delete or mess up all the data). I rather have were people pm there scores and other data so i can add it in.

I will finish tweaking on how to tests and how the spreadsheet will look tomorrow.
[EVO 4G General] rek410:
You should add 2 additional categories:

Does WiFi Tethering work with 3G speeds Y/N

if yes, which version of Wifi Tethering

Does WiFi Tethering work with 4G speeds Y/N

if yes, which version of Wifi Tethering
[EVO 4G General] nief1313:
I have just added that to the spreadsheet, the versions will be written down in the additional notes. Also, i just posted the link to the spreadsheet in the OP. I will be looking for testers if anyone is interested to help.
[EVO 4G General] nenn:
nief, im running EViO 2 V1.0.2

ill post results for you later.
[EVO 4G General] nief1313:
Sweet thanks for the help.
[EVO 4G General] OgremustCrush:
Which version of CM6 were you going to test? RC1 is getting pretty old, a lot of us are using nightlys. RC2 should be out soon though.
[EVO 4G General] nief1313:
I was planning on testing RC1... at least until RC2 has been released.

if some one wants to do the tests for a nightly build, i will gladly add another row :D
[EVO 4G General] omegasun18:
I noticed you had an over clocked set to test performance but for battery you have it set not to test profiles for example in battery. this can be a huge disadvantage for some roms (ie DC has profiles for performance and battery that can make a huge difference int here DConfig.) also the kernels can greatly affect these. If we wanted to actually test the rom shouldn't we be testing these with either 1 the same kernel for all or their stock kernels?

for example someone using the stock Fresh kernel may have vastly different results then someone using netarchy's kernel. this would provide skewed results for the rom test.

Same goes for Baked Snacks since there are several kernel options. if using the performance kernel for the performance test then switching to battery saving for battery saving test you will get results showing unachievable results.

I think this is a great idea but if this is going to happen i think "guidelines" should be used so that the data is as close to comparable and accurate as possible. what do you think?

something like

1) for testing purpose you should use the stock kernal with the rom for all tests.

2) with the exception of the OC tests you can not be running setCPU or any other under/overclock programs.

3) the following settings should be used. <list some basic settings>

4) if your rom has built in profiles settings that do not require a reboot or flashing anything you CAN use them.

5)etc

6)etc

If we dont have guidelines i think the results will very greatly on settings and kernel.

Even with doing the above you will still have a decent variance from usage/apps/widgets but at least this would make it as close to a level playing field and testing of the rom itself rather then the kernel/settings/who has what in setcpu
[EVO 4G General] Vinny75:
I agree. Using performance profile for the performance test and then battery profile for the battery test will lead to skewed results. Perhaps what should be done is to test each profile against all tests. So you might have DC/Performance Profile and DC/Battery Profile with results for every test. This would tell you how well the battery performs under the performance profile or how well the rom performs under the battery profile.
[EVO 4G General] sgt. slaughter:
I agree with a baseline but there should also be a performance test done where you have it maxed to the peak and state the battery life you'd get with those settings and numbers.

......

now that I think about it....

Really in the end we are speaking real world examples here and itd be best to just have the results state what rom, what kernel, and what settings you had to get "X" results and then go form there.

I dont care if DC is better on stock kernal and settings than BS. I'd rather know what settings in BS yield what results for people and the same for any other rom.

With the number of changes the dev's put in the roms doing baselines against them is kinda pointless as they might each take advantage of certain things differently. It'd be best to just notate the results for each post and state the changes made to yield the results so people can get more real world conclusions.
[EVO 4G General] omegasun18:
The thing is if you do what you suggest .. you arent comparing each roms performance really. If this is supposed to be used as a sort of guide for people to compare the roms themselves then what you said doesnt make sense since it adds a large a mount of varibales tot he "tests". Now if we are trying to compare complete packages and find what works best sure i agree with you completly. however i would not consider that to be comparing roms. which is what the origonal intent LOOKS to be.

When you are trying to compare things to get the most accurate results you compare them in as close to the same conditions and set up as possible. The more you differentiate the things you are comparing the more aspects can influence the results and the more skewed or inaccurate the results are.

If you have extremely random results based off a wide variety of conditions then the results lose there usefulness. In this case if we are trying to test ROMS then we should try to single out the roms and get them as close tot he same footing as we can so we can compare the ROMS and not the tweaks everyone can do. Maybe having another table or thread comparing different settings and tweaks and kernels would be helpful as well?

By stock kernel i mean the stock kernel that comes with each rom. The devs tweak these and make changes to give better performance/battery. I dont mean the stock as in the original froyo kernel. I also disagree that this isnt real world examples. I think it is exactly what it is however it takes out individual tweaks from the user and tries to keep everythign as close to level as possible to yield the best TEST results
[EVO 4G General] sgt. slaughter:
Still going to say these will be nice but not what people will be looking for. So what if BS beats out DC outa the box in terms of bat life and performance. Thats nice and all but if you could show that with a few tweaks with set cpu and other things included in the rom that that DC greatly outperforms BS then its completely different.

What really needs to be done is what we both are saying. one done stock with the included kernel with the rom(or whatever the developer suggests using), and then one where users can make there tweaks and post those results.

If I just knew that one rom had better battery life stock and didn't know that I could possibly use a different rom that with a few tweaks gets better battery life and performance I'd rather use the later. Some roms perform differently than others with regards to tweaks being done by the user.

I'd stress that two tests be done, one with stock rom with stuff loaded form the dev's page only, and then one done with tweaks by the user and state the results so we can really get an idea what rom is best at what performance wise at least.
[EVO 4G General] adeyo:
I was wondering if there would ever be something like this!! Great job!!! ...just on the side note, is there anyway to put the features working on the left side closer to the rom? i know a lot of users who care more about working features than technical stuff (linpack etc). I too would love to see this on the wiki!

**edit: also, maybe consider adding kernel box so we can see which kernel is being used w/ which rom and working features etc.
[EVO 4G General] nief1313:
The first part of the table is to test the rom with the stock kernel.

The second part is to see how well it performs oc.

This is supposed to show how well a ROM performs by itself and how well it works while oced since a lot of us do us custom kernels.

On all of the tests, there should be no widgets or apps installed that didn't come preset with rom(excluding setCPU, fps2d,quadrant, and linpack). This should help eliminate variability of what apps different users have.

On all the test (performance or battery) if the rom has preset profiles they can use them as long as it doesn't require a reboot or any 3rd party apps. all these profile should be mentioned though in additional notes.

I said no profiles on the battery test, meaning no setCPU profile due to variability of profiles.
[EVO 4G General] nief1313:
There is a kernel box already there, its to the very right. THis is the custom kernel used during the oc test.
[EVO 4G General] omegasun18:
Thanks for clearing up what your vision for this is.

sgt slaughter. I agree with a lot of your points. I think 2 sets could be done to better show a variety of results. I was simply arguing the merits of doing a rom specific test comparison vs a complete setup specific comparison. You are right that different roms react differently to different tweaks that was the point. BUT not only do different roms act differently, different evos with the same everything react differently to different tweaks and settings. Thus just because user A get these results doesnt always mean User B will too. that's why i thought baseline would be a better gauge on the roms themselves.
[EVO 4G General] omegasun18:
I would be glad to help with this I will do a set for DC 3.5 now and pm you the results.

Really like the descriptions under the columns explaining what was done.
[EVO 4G General] nief1313:
Yea, it is def important to have as many control variables as possible or it begins to become impossible to have a standard test. These results aren't supposed to say this one ROM will always have this much battery life. It is supposed to display a basic idea how the ROM will perform in certain areas. Thats why it is important to just have the roms pretty much standard with no extra apps, no extra widgets, no extra profiles(except the ones that come with the rom).
[EVO 4G General] ViViDboarder:
Native Froyo Wifi Tether works on CM6 and you have it as not working.

EDIT: Also you should make the spreadsheet a shared/public one. Then anyone who tests can just update it themselves.
[EVO 4G General] nief1313:
Updated CM6, I would like to have it shared/public but my only concern is only one person(whether he means to or not) can delete everyones work. I would rather just give specific permission to edit.
[EVO 4G General] ViViDboarder:
Is there no version tracking in Google docks? I guess a wiki would be best then. You'd be able to roll back changes of someone who messed it up.
[EVO 4G General] nief1313:
There is roll back but I also like to be able to confirm if the results were properly taken and recorded.
[EVO 4G General] nief1313:
Im at work, can someone update the screen shot image for me for the op? thanks
[EVO 4G General] Cal3b:
one thing you should specify is screen brightness, since that will be a huge factor in the battery tests.
[EVO 4G General] nief1313:
Screen brightness should be set to auto.

btw the battery test for DC movie has been completed. thank you omegasun18
[EVO 4G General] omegasun18:
should see dc custom kernel movie and Baked Snacks performance stock/OC updated soon as well. I cant test Idle because i use my phone to much so anyone out there who can easily test idle times this would be helpful in completing some data. its all thats left for dc 3.5

as an additional tip to get the most accurate data. I have been doing each test for performance 5 times and averaging them (except on linpack where it is highest out of 5 runs). This allows for a decent average and helps decrease the range that the tests can give.

For battery i only ran the test once simply cause it takes to long and we have to much data to collect still. Hopefully as others do these tests the data will get averaged and we can get these numbers to an accurate average for users.
[EVO 4G General] nief1313:
Thank you for the data, it has now been updated on the charts.

If anyone can help with the battery tests, or just even say what features your rom has would be a big help.
[EVO 4G General] nief1313:
Updated Avas ROM features
[EVO 4G General] oubravs2b:
Testing EViO now. Results to come via PM in a bit.

SENT PM
[EVO 4G General] nief1313:
Thank you for your help, your results have been posted.
[EVO 4G General] Hero_Over:
Please use my kernel to test battery
[EVO 4G General] duffkiligan:
Test on Eivo 2 v1.0.2. However I have upgraded to the 2.6.32.15netarchy-toastmod-4.0-g4afa082-dirty (Netarchy 4.0)

PMing results soon.

EDIT: Results PM'd, the kernel makes a slight difference in this ROM if you want to post the results.

EDIT 2: Listed under the Features Working list should be camera and "8MP Camera"

This Rom on the old kernel "kind of" has an 8MP camera, this ROM on the new kernel has an actual working 8MP Camera. Just a thought.
[EVO 4G General] patelkedar91:
I want to see Hero_Over's Baked Snack battery results!

I'm running CM6 with Snap kernel...

Why not also do tests with 3d benchmarks? Nenamark, Neocore, GLBenchmark?
[EVO 4G General] nief1313:
Will do when tested.

I have put up your results. Thank you for the help. The feature column under camera should be yes, if and only if both cameras work at there designated mp. If one of the ROMs are wrong just tell me and I can switch the results.

I would love to see more battery results also, but unfortunately(or fortunately) I'm on vacation till Saturday and wont be able to run any until then. If anyone wants to help, just run the test and pm your results.
[EVO 4G General] oubravs2b:
PM Sent with new testing on EViO 1.1 (new version out today). Great ROM.
[EVO 4G General] duffkiligan:
EViO V2 1.0.2 With the stock Netarchy kernel is not at 8MP, it is actually 3MP from what I know.

I will also be doing the benchmarks with EViO V2 1.1 as soon as I flash it.