yashsingh1/xdaforums huggingface dataset:
[HD2 Android Q&A, Help & Troubleshooting and Genera] robrob777:
I trew the tower

I bought another phone already.

I couln't wait any more for NAND, I went for the G2, last saturday, I kinda miss my big screen. but I like the battery life in the G2, so far 2 days and it keeps going.

The reason I left the HD2 is because i was spending too much time trying to make android work 100%.

There is so many reasons I won't ever use Winmo again. I could write a book.

Even a simple things like set a password if the phone is not used for 1 hour are not correct, the device ask and ask the password every time it wakes up in any Rom.

I'll still wait for Android Nand, and will donate more when it is done.

Best regards

-Rober

by they way now that I have another phone, I'm trying to check the standby time of the HD2. I'll let you know guys,
[HD2 Android Q&A, Help & Troubleshooting and Genera] steven1234:
yes, android on HD2 is broken and I don't think even NAND will fix it. I really don't want to downgrade screens but if the mytouch comes out and android is still unusable then i'll probably switch.
[HD2 Android Q&A, Help & Troubleshooting and Genera] JonSolo:
Android broken on HD2? I have a premature flash which is fixed from what I understand, and blurry MMS, which also has a fix. Just waiting for the next build. Otherwise, not broken.

Winmo? Froze every hour on the hour. Even with flashed ROMS. SBP shell lasted a few days till it slowed to a crawl.

Froyostone 3.1

ChuckyDroid latest.

2.12 radio

TMOUS

J
[HD2 Android Q&A, Help & Troubleshooting and Genera] agentaaron:
I came from preordering the G1...to the MT3G...went to an iPhone 3G (sorry...had to see what the buzz was about)...to a Nexus One...to the HD2

I am very comfortable with Android and what it can do (though I never got into the development part...my career is testing software) I would say that I have seen much more incomplete software than the Android that we have.

The only reason I stood in line in March to buy my HD2 was because I knew that it would have Android sooner or later.

I never even really used my HD2 until early July when Darkstone first put out a Android build that didnt greenscreen after 2 minutes...I always used my Nexus as my daily driver. I could never get the hang of WinMo...even using good cooked ROMs like NRG and Kumar...along with CHT and SPB MS, it still felt very uncomfortable to move around in.

Am I tired of it? No way...I have not booted into WInMo since Darkstones first Desire build (except to upgrade ROM/Radio stuff), my Nexus has now taken its place in the closet and my HD2 is now my daily driver.
[HD2 Android Q&A, Help & Troubleshooting and Genera] shadiku:
The only thing I'm sick of is the touchscreen freezes so I've had to completely remove all my sensors files to stay sane, fortunately other than that I'm content with Android at the moment and I'm one of the many who can't wait for NAND.
[HD2 Android Q&A, Help & Troubleshooting and Genera] steven1234:
no offense but screen turn on lag one every build + data connection drops along with the occasional complete cell signal drop = broken and unless the devs can fix these things the HD2 will never go a single day without causing the user a headache in Android. BTW lol at t-mo and HTC bending the consumer over by rereleasing the HD2 as the HD7... slick move. That along with not releasing a 4.3" screen phone with android to compete with the HD7 is some great business practice.
[HD2 Android Q&A, Help & Troubleshooting and Genera] THUDUK:
The reason I sold my Android based Galaxy S was because I knew the HD2 and XDA developers was the ultimate team...

90% of the time I run Android now as it allows complete cloud syncing with my google account, facebook and online usage with flash is easy and nice to use.

the small remainder of the time I will use Windows mobile now for some of the applications in particular older apps like memory map navigator, pocket birds guides and the rest of the series and the camera is still better in Windows mobile.

I like the fact I have two devices in one, and later on XDA are bound to bring us Windows 7 on the HD2 which I will test also, what with NAND, Windows 7 and more updates and builds to test than any other device, the HD2 for me is the only device to own.

Oh yes and it runs Android slicker and smoother than my Samsung Galaxy S ever did...
[HD2 Android Q&A, Help & Troubleshooting and Genera] Jammie_1989:
What about desire hd 4.3" and Android :-s
[HD2 Android Q&A, Help & Troubleshooting and Genera] GbrilliantQ:
I guess I've been spoiled for months. I've never been happier with my hd2. Im getting 12hrs of heavy use. No freezing, or drops in data. Nothing. The only time I need to restart is if I'd like to try something new. Android on my HD2 is perfect and not broken. Never been happier and couldn't possibly think about downgrading to something else.

Sent from my HTC HD2
[Captivate General] cruiserbax:
This will be the start of a hopefully short lived thread as I only intend to use it to post my findings about the affects of a lagfix. Alright if you are going to come in here to start a flame war about how you know it works or doesn't work just "because" do not even post just leave now! if you have actual measurable data or intelligent input then please contribute.

So a lot of folks state that the advantage lagfix has for them is general responsiveness of applications like touchdown or the market or even jsut opening speedtest.net app. I already no that the direct read/write speed to the FS where the OS resides shows the Captivate much faster than the Nexus one and there is no general feeling that the N1 needs any lagfix. So we can not measure any advantage of a lagfix just by testing the read/write speed of the FS. what then? if it's application responsiveness that is the difference then we have to create environment in the form of a measurable benchmark. So right now I have a ver VERY comprehensive I/O bench script running. it creates an application level benchmark environment where several to many processes are each running various mixed mode I/O streams (read/write/cache) doing this with the exact same standards on a non-lagfix FS and a lagfix FS will show even the smallest most tiny variations in the different types of I/O. it will let us know if perhaps there is a certain type of stream (buffer size, block size, file size) that a lagfix might be improving upon. once the results finish here in about half an hour I will sift through the results, build a graph then post it! I am in no way on one side or the other of a lagfix, I have used both and would rather keep my opinion to my self right now. check back later today for results. I welcome all constructive input/ideas/do it better benchmark (currently 1429 Hawaii standard time)
[Captivate General] gabby131:
This is also a question that came in to my head before installing a lag fix.

Well i notice some lags in a stock non-lag fixed captivate. Examples are in games like asphalt (when you win/lose a race) and in N.O.V.A. (progress save) and sometimes in google search widget (when you tap on the text bar, a little sec before the virtual keyboard appear).

I thought that these are just bugs on software or the app itself, but everything is gone when i install lag fix. Yes there are still lags but not as much as before.
[Captivate General] phishie:
This is awesome, can't wait to read it. Are you considering releasing the batch script so others can attempt to contribute?
[Captivate General] bts0uth:
Already got moved but it doesn't matter. I for one can not wait to see your results cruiser. If you do decide you want to let someone else try your benchmark I'll gladly run it as well.
[Captivate General] cruiserbax:
Absolutely! I take no credit for these tools and credit will be given where due once the graph is up. I only wrote a script to create the benching environment I wanted. using these tools you can write a very comprehensive script to create the benching environment you want/need for the specific aspect that is being benched. these tools don't just test hardware as hardware is nothing without great software. so using the application level software components to perform these benches and bouncing them off the hardware benches you can see what areas of the software environment are choking what part of the systems performance and vice the versa.
[Captivate General] alphadog00:
There are a few different lagfixes out there - so don't leave any out. Also, some attack one partition, others attack more then one (/dbdata) - so you need to take this into account. Also Touchdown, and i believe stock email app, benefit because they store data on dbdata in a database - so database throughput should be part of the equation.

Benchmarks are nice, but i have tried with and without and see the difference deleting emails using the stock client. That being said, I rolled back to stock because one-click odin does a poor job of reformatting everything - I don't want to get stuck with an EXT4 filesystem and stock kernel with no way to go.
[Captivate General] Clienterror:
I found with 2.2 it is way faster than 2.1. But 2.1 with any lag fix is still faster. Now you could run 2.2 with no lag fix and it's definetly fast enough but with a lag fix it's amazing. It's like buying a 300hp sports car then the sales guy asks you if you want the 400hp model for a free upgrade and it gets the same gas milage and you saying no because 300hp is plenty to get you around town. If theres even a chance a lag fix makes a difference why not do it, it's not gonna make it any slower thats for sure.

Sent from my SAMSUNG-SGH-I897
[Captivate General] keitht:
Just my 2 cents, I do think that lag fix will give you better performance with certain apps however, it is not that significant and with Froyo, I had problems with apps force closing and battery drain (probably from all the background crashes) with it enabled. I do not think it is needed and may cause more problems than it is worth. Maybe later once the official Froyo is out for a while and the lag fix apps are improved, it may be worth another look. But for now, I do not think it is worth it. But your mileage may vary and if you think your phone is too slow without it, you may have some other underlying issue that needs more attention than trying to fix it with a lag fix.
[Captivate General] cruiserbax:
Duty calls, this is taking longer than I anticipated so I'll still be running this on different file systems tomorrow after work. very interesting results so far though! Spoiler alert! there are obvious gains from database read/writes, only milliseconds but I suppose that counts when it comes to responsiveness of certain programs.
[Captivate General] mr.jaguar:
I can't wait to see the results.
[Captivate General] newter55:
I wanted to say that I am interested in what you are trying to do here and appreciate the time you are putting into making this an unbiased effort at answering this question.

I also wanted to provide you with my own real world experience based on three different captivates all presently using cognition 2.2b5.5...until later tonight...lol

I have never installed a lag fix on two of the phones (my wife and duaghter's) and held off on reinstalling the ext lagfix on mine again until yesterday as I wanted to see if it would benefit the performance prior to updating again to beta6

On the phones that my wife and daughter use, I can see where the lagfix is not necessary and they don't complain about any hangups. However, on mine I definitely see a performance improvement with the lagfix installed and i am quite sure that the reason is I am addicted to widgets almost as bad as flashing and I cannot seem to get away from them. After installing the lagfix I do not get the occasional "freezes" that occurred without it and music never skips when opening other apps.

Also, all three phones are running launcher pro, using at least a few widgets, such as friends, messaging, weather, etc. Not sure how you would reflect this in your testing but I do see a difference here though I would love, and certainly tried, to not use the lagfix.
[Captivate General] TheYar:
It seems people have gotten bored of this issue. I will say this:

When I ODINed directly from 2.2Beta2 to 2.2Beta5.5, lag was undeniably horrible and OCLF made a huge difference.

When I master-cleared 5.5, ODINed to stock 2.1, then ODINed to 2.2Beta6, everything became zippy fast again without any lagfix. I'm afraid to even try to put OCLF on there now.

Anyone experiencing lag when others say they shouldnt: go through most or all of the steps I laid out for battery drain. Quirks abound, and your lag and lagfix situation could be an indirect side-effect, and not a direct result, of the ROM you've flashed to.
[Captivate General] shaolin95:
I agree. Some of the claims are down right odd about lag issues so I too feel a lot has to do with "left overs".
[Captivate General] shawnl01:
My Experiences

i didn't install the lag fix because of the horror stories in the forums about applying an update and having to roll everything back. Normally it's not so bad but I've noticed some of the behavior mentioned. Are these issues addressed in the Froyo leaks (hopefully official) or will these always be a problem.

-Load time of games (using Asphalt 5 and comparing the load times to an IP4 running the same game). The Captivate load times were very slow.

-The appearance of freezing when you win / lose a race in Asphalt 5?

It may not be a fair comparison for load times but it's obvious signs something is wrong when I'm trying to brag to my friends about how my phone is better then theres :)

The biggest issue I have is with the music stuttering though. I listen to music at work (normally the 13GB data partition is full of music) and the email client is running in the background. The music stutters A LOT when it's downloading the emails. Is this issue no longer a problem in Froyo?
[Captivate General] TheYar:
Hopefully this settles it.

Here's a vid I made. I don't know how to split-screen, but I think this makes the point regardless.

I master cleared, then stock 2.1, then Cog 2.2B6. I didn't restore any backups, all fresh installs and configs.

When I ODINed directly from Beta3 to Beta6, the lag was horrible. Doing a master clear, stock, to 6 was much better. But even then, as seen below, there is blatantly noticeable lag. That only leads me to believe that the issue relates to something like fragmentation, and that if people used beta6 for a few weeks without a lagfix, they'll end up with really bad lag too.

For the record, I doubt any of this has much to do with DG's work. I don't think DG is responsible for lag. DG is only responsible for giving us awesome alternatives to choose from when we don't like what the factory gave us and we're willing to take the risk. However, the lag is not a placebo, and your benchmarks are deceiving you.

I picked Touchdown because it was an easily reproduced example, but I notice a difference all over.

[YOUTUBE]LdP-mgqr624[/YOUTUBE]

The stopwatch is to add legitimacy. The iPhone, to add irony. There's a glass of beer off-camera you can't see, but it's responsible for most of the background noise.
[Captivate General] cruiserbax:
Alright folks!

Those of us in the Military know how your work schedule can tends to change randomly causing you to change your plans a lot. Anyway as I don't see myself with the free time to spend making a cool but not very practical PowerPoint right now I am going to tell ya'll what I found and post the DHT tools so you can play around with it yourselves.

First to those who wish to try the tools, read the vague overview file in there it's as good as it gets as far as information from DHT. you HAVE to run the IO bench several time in both read, write ADN mixed modes. Make sure you run each mode a few times specifying different files sizes block sizes AND numbers of IO streams! each specific setup should be run 5 times and averaged, if run in each set is 5% or more from the rest it should be scrapped and run again. NOTE: some modes require you to have already deployed a file or DB to run the test on!

Alright so I found the difference in every area except one to be non-substantial! and by that I mean 5%+/- (within the considered error margin)

I ONLY HAVE HAD THE TIME TO TEST OCLF! all benches were run on Cognition 2.2B5.5.

When you start getting more than TWO IO streams you start to see a substantial difference in the DB IO streams. in my last run in mixed mode multi-stream bench of 5 runs (all within the acceptable margin) it showed a 19% increase in throughput over the stock FS! I know that doesn't sound like a lot but milliseconds count when it means the responsiveness of an application! One thing I did not do which I wont get to for a while is look into how many IO streams are running and in what modes while running some common applications! this could give us an idea of what kind of bench environment to set up and perhaps give us a base (just for information sake) % throughput increase with a certain FS. just to give you an idea (I am sure most people already know this but wth) of what types of application might take advantage of an increased IO throughput on DB read/writes. A lot more applications do DB IO streams than you might think, some email applications/exchange contact syncs, even some system settings are stored in DB anyways I say it's up to the person! I wont personally use a FS patch "lagfix" until A at least as stable as the current COG2.2B6 Voodoo kernel is done for the captivate. I don't feel like messing with the loopback stuff and whatnot, I can live with it like it is as I don't feel it's bad enough to HAVE to have one, but again everyone is different! However when Voodoo comes standard in a good ROM like COG I say what the hell~! even if it's only 10% gain and only in certain situations! if it's stable and cooked in then it can't hurt me right! ok enough now hope you guys can figure out the tools well enough. it is clear that no matter what anyone says it is factual that no matter how small in SOME situations/applications there IS an IO throughput gain when using OCLF and I am sure any other EXTx FS. weather or not the gain % is worth the possible side effects, well like everyone keeps saying (well almost everyone, some do just cry "MUST HAVE IT") that's up to you!
[Captivate General] shaolin95:
Ok great video mate.

I also noticed one HUGE lag difference which now made me a believer.

I use Launcher Pro and when adding applications to the lower scrolling bar there was always lag the first time accessing the applications.

I timed it at 17 seconds without lag fix and no delay with lag fix...that is BIG!
[Captivate General] newter55:
That was one of my bigger lag issues too...lp seeming to freeze but after finally giving up on touchwiz a while ago and removing it I have been able to get by without the lagfix though I am probably going to use one again as soon as voodoo is available for 2.2

Posted from my phone using some technology I don't understand
[Captivate General] TheYar:
I originally intended to include a few other tests in the video:

* Adding an app shortcut

* Opening the app drawer

* fast scrolling through the 3D app drawer and some widget-heavy home screens

* boot times (particularly initializing widgets on the home screen)

However, in prepping for the video (and most particularly after removing TW), I determined that I could not reproduce the lag effect as consistently in any of the above. I've definitely seen what you describe, and noticed lag differences OCLF vs. not OCLF in all of the above, but I've also ran some tests where I couldn't reproduce it. Touchdown was one of the easiest to demo and that never fails to present an obvious difference.

My current theory is that while Froyo has performance tweaks, a lot of the reason people think there is no need for lagfix anymore is because more people were master-clearing and flashing stock before flashing Cog betas. This gives you a clean slate on your fs, with little chance of fragmentation or other inefficiencies that crop up in a well-used file table. Like I said, flashing without going stock or master-clearing, or restoring lots of backups afterwards, seem to be what bring back the lag. A well-managed cache like you get with a lagfix helps that a lot. I still say that even those who claim to see no lag, if they put some heavy use and load some heavy databases and throw some I/Os at them, then over time they will see more and more of the same lag others see. I don't know that for sure, but I do know for sure what you can see in the video. And that's on a recent setup of master-clear, stock, beta, and no backup restores whatseover.
[Captivate General] Trevor.Richard89:
This probably in the wrong section, but I recently purchased the captivate through an upgrade, and read about and installed the lagfix. Yes it did speed up my phone considerably. My quadrant score was about 2386. I was pretty damn impressed. But then I wanted to go back to stock, and just did a factory reset. I don't think the lagfix is installed anymore. But I just want to know if I didn't hurt my device by doing so. Thanks
[Vibrant Q&A, Help & Troubleshooting] Jarnold86:
Anyone else have this problem? I am Rooted on the stock firmware with Eugine's lag fix.

When I install it and then open it it just stays at a black screen. I searched but could not find anything in regards to the issue I am having.

Additionally I deleted my stock browser.apk and it will not let me install it anymore.
[EVO 4G Q&A, Help & Troubleshooting] jttraverse:
I want to update my EVO to the latest firmware, etc. (currently still on Firmware version 2.1-update1, Build number 1.47.651.1). I'm still on a stock ROM, rooted, unrevoked forever, Titanium Backup, got ClockworkMod Recovery and Amon RA, etc.--primarily to backup everything and to have wireless tether if I needed it. I'm thinking of installing my first custom ROM to get the update, and to have all the niceties already installed since you fine developers have done so much great work.

I've read what I could find and have been considering the latest Fresh EVO or Ava-Froyo. Anyone have thoughts on the pros-cons of these?

Since I've been pretty happy with the stock ROM, I'm looking for reliability first and foremost--I definitely want to keep 4G running and the camera fully functional (at 8mp). I am hesitant after reading about people losing their RSA keys and having WiMax problems with some ROM's, so that is a major concern obviously.

Anyone having problems or perfect experiences with either of these two ROM's, I'd appreciate hearing opinions.

Thanks,

JTT
[EVO 4G Q&A, Help & Troubleshooting] wfrandy:
If you are mainly interested in reliability, you can't go wrong with Fresh 3.3.0.1, in my opinion.
[EVO 4G Q&A, Help & Troubleshooting] dabezt1:
I tried both and found Ava was a little smoother. But not really noticeable. I staid with Ava and flashed kings #11 kernel
[EVO 4G Q&A, Help & Troubleshooting] dom085:
RSA keys should only be a problem if you're flashing radios.

ROMs work above the radio level, so they won't be changing them.
[EVO 4G Q&A, Help & Troubleshooting] ramiss:
I have tried both and prefer Fresh. Both seem just as smooth but I get better battery life wth Fresh.
[EVO 4G Q&A, Help & Troubleshooting] freeza:
Another vote for Fresh here.
[EVO 4G Q&A, Help & Troubleshooting] stangdriverdoug:
Both roms are extremely reliable, and are supported very well by their developers. You can't go wrong with either one, they are just a little different. I would suggest giving both a try and see what you think. Dont worry about the RSA keys.....you won't run into that problem....when you do a nandroid backup of your stock rom RA recovery will back up your wimax anyway.
[EVO 4G Q&A, Help & Troubleshooting] Crossrocker:
Fresh is much more stable and has more people using it