yashsingh1/xdaforums huggingface dataset:
[Epic 4G General] boodies:
hi guys, I am coming from the vibrant forums. just letting you folks know that a new leaked rom for our phones fixed this GPS issue and we connect to 8-10 sats with flying colors :) http://xdaforums.com/showthread.php?t=782215 A full update from Sammy should be expected soon.
[Epic 4G General] aero1:
meaningless since Vibrant's GPS issues are totally unrelated to Epics
[Epic 4G General] aero1:
Ray, you cant have aGPS on without GPS on.
[Touch Cruise General] chivas228:
I tried the TC 09 and with WinMo 6.5, it BLOWS!!!

maybe i need to try to flash it back to 6.1 but everything about the TC (polaris) is perfect EXCEPT it can do with more RAM and faster processor. the radio ROM is great and the size and everything is great for me. it's light weight and even though it lacks a qwerty keyboard, i don't really want one.

good to be back... time to relearn all the reg hacks (like removing Dismiss when sending text among other things)
[Galaxy S I9000 Android Development] ppeccin:
Anyone please?

My holiday is ending, and I still have to find an answer! :-)

Thanks.
[Galaxy S I9000 Android Development] jjwa:
There are a lot of lag fixes, and their differences are beyond 'this one is better'.

So in the end it's down to personal preference and the way you use your phone.

I personally like supercurio's Project Voodoo lagfix the most. He will release a public version (beta2) pretty soon :).
[Galaxy S I9000 Android Development] CazeW:
If you want a lagfix right now, use One Click Lag Fix. If you can wait, wait for supercurios Voodoo lagfix beta 2.
[Galaxy S I9000 Android Development] hacksome:
There is a tiny battle going on between filesystem of choice - EXT2 or EXT4 - for lagfix. This is good for us users for speed and stability of the fix. I would suggest you wait for a couple of days to see if Voodoo Beta 2 fits you. Else you have OCLF which yields a lot of Quadrant scores and keeps a lot of people happy here already.

Personally, I am on JM7 with Voodoo Beta 1.
[Galaxy S I9000 Android Development] Kasha:
I have JM7 with the One Click Lag Fix, suits me perfectly, the phone just "flies". Also, the ease of install is the best - just install it from the market.
[Galaxy S I9000 Android Development] azgull:
I have a couple of questions. Do I need to root in order to do the lag fix? I noticed that the One Click Lag Fix app can root my device too.

Also, how will my phone react when Froyo is released? Can I upgrade my phone through Kies without doing anything, or do I need to somehow get rid of root/lag fix?
[Galaxy S I9000 Android Development] Prankey:
Tried all the lag fixes EXCLUDING Voodoo. I can say my phone is better off them even when it WORKS. While they do some "cosmetic" speed improvement, I find them actually INCREASING lag in some typical activities like installing, uninstalling apps, multitasking, etc.

Latest I tried OCLF 1.6 and finally revert the lag fix to see my phone working "normally". Hope you could read through the punctuations ;)
[Galaxy S I9000 Android Development] devabhishek:
what version rom are u using??
[Galaxy S I9000 Android Development] distortedloop:
The easiest lagfix (which also greatly improves GPS (in my opinion) as a side benefit) is to just upgrade your firmware to one of the following: XFJM6, HVJH1, or XWJM7. Note the bolded F in the JM6, XWJM6 is not lag-free.

Those three firmwares seem pretty lag-free out of the box, though after a lot of up time, you might get some lag, but that took a couple of days for me, and a reboot fixes.

The next easiest lag-fix is to disable all the fancy animations and window transitions in the GUI. Do this in Settings.

The next easiest lag-fix is to get AutoKiller from the Market and use one of the medium to aggressive settings in the pre-sets. This works well at reducing some lag, and has the benefit of being easy to uninstall if you're not happy with it for some reason.

Now, if those three things don't give you a happy phone experience, personally I am in the Voodoo (by curio/supercurio) camp to be the BEST experience so far. Easy to install, best overall reduction in lag (as in I have ZERO lag even after 90+ hours of uptime and heavy usage), no Market install/download issues, no random freezes. EVERY OTHER lag-fix, from Mimocan to RyanZA's OCLF have those issues still, Voodoo does not, for me.

If I couldn't use Voodoo, I would use the mimocan fix, specifically by using the Samset/mimocan kernel.

I won't get into the ext2 vs ext4 debate that the supercurio and ryanza camps have fallen into.

My advice right now, try the first three things I suggested and WAIT until the end of the week to try supercurio's Voodoo Beta 2 when he goes public with it.

As of right now, I am on XWJM7 firmware with voodoo beta 1, and installing voodoo beta1 is the first time since buying this phone that I have been satisfied with its performance. YMMV, of course.

edit: ps - to be clear, I have tried just about all of them...
[Galaxy S I9000 Android Development] RyanZA:
I agree completely with you, except about waiting for Voodoo BETA 2 at this point. Please note the BETA - even though it will be pretty heavily tested, please don't jump onto these lagfixes until they are out of beta, especially if you don't know what you're doing. There may be complications, especially if you grab it as soon as it's released.

Please, this type of thing is marked BETA for a reason! When it goes to RELEASE, then you can jump on it! :)

Of course if you want to test stuff out, then please try the betas, but things can and do go wrong!

As far as the OCLF fix, it has proven so far to be very safe, with thousands of people using it without issue so far. Comments and stats available here, and this only includes market downloads: http://www.appbrain.com/app/com.rc.QuickFixLagFix

The general consensus is that OCLF does make your phone faster, but these types of things are very subjective. :) It also doesn't use custom kernels or similar, and works on all firmwares, which is a plus for some.
[Galaxy S I9000 Android Development] distortedloop:
Your point that Voodoo is in beta, make that BETA, is well taken. Supercurio won't release it to public until it's well tested. Some of the other methods released here weren't approached so conservatively in their early days, but anyone in this particular forum should be aware of the risks.

Please note that the original poster said "I want the best/newer one (in terms of speed and stability), I don't mind if its not the easiest to install," which implied to me he's up to some beta stuff.

That said, your method's lack of needing custom kernels being a plus is spot on as well, but it also opens the door to the whole ext2 vs ext4 debate, since you're using ext2 and that's why it doesn't need a custom kernel, and I specifically said that I wasn't going to step into that one... ;)

Anyways, I think your method has some plusses, of course, and it turns in some amazing Quadrant scores, for whatever that's worth, but in every day use, lag and GUI freezes still exist occasionally with it, and that is not my experience with voodoo. Voodoo also turns in some great Quadrant scores (about right in the middle of what mimocan and OCLF give me (mimo-1400, Voodoo-1800, OCLF-2200)).

Voodoo works best for me in every day "feel" of the phone. It's my recommendation to anyone if they can get into the beta. It's truly lag-free. And free space on the device is accurately reported.

Mimocan works well and is based on the apps2sd concepts that have been tried and tested over many devices and firmwares and mods like Cyanogen's. It's mostly lag-free.

OCLF is super easy to install with apps from the app store and batch programs for Windows users and has a very dedicated and respected devs behind it. It's mostly lag-free, but I'm not comfortable with the whole ext2 loop mount business it uses and the last time I used it had the disadvantage of inaccurate free space reporting, and the huge file it creates makes clockwork backups very slow and very large. I'm not recommending against OCLF, It's just not my first choice.
[Galaxy S I9000 Android Development] RyanZA:
Not true at all, EXT4 is very easily added to the running kernel as a module. Tayutama has an EXT4 version that works fine on the stock Samsung kernel. People just don't use it very much because it's slower. *shrug* I haven't had any requests to include EXT4 in my app either, so I haven't done it yet. And you stepped into it, but I needed to clear it up. ;)

Unfortunately, both mimocan and voodoo (BETA1, hopefully fixed in BETA2) have very annoying battery issues, and bad battery life is worse than occasional lags. Your experience with it might have varied though. :)

I'm currently trying to get a fix similar to voodoo going that won't need a custom kernel, but it unfortunately needs gnu parted to do that. :( And gnu parted is proving to be horribly difficult to port to Android. :(
[Galaxy S I9000 Android Development] distortedloop:
No, I still haven't stepped into the ext2 vs ext4 debate, but I stand corrected that you don't need a custom kernel to use it. Is that a recent innovation?

I'm specifically avoiding the speed and potential for data loss argument. It's debated ad nauseum in several other threads.

I suspect the reasons you didn't see requests for ext4 in your own apps are two-fold. 1- you are very clearly against it, and argue strongly that ext2 is faster and that that is part of the reason your fix works and that ext4 would slow things down *shrug* and 2- many, like me, incorrectly assumed you needed a custom kernel for it. Go figya! ;)

I've heard battery complaints about your fix method as well. I do not experience them at any noticeable rate with any of the methods. I've never made it through a full day without using up most of battery with any smartphone since my first iPhone; others claim to make it for 2-3 days. Who knows what we all do different that impacts this. It's a cheap and easy shot to take at any app or rom or mod, and for every one complaint of "drains my battery faster" there's usually a post from someone who says "doesn't affect mine."

Battery complaints are such a sore spot in the Android community. Every new custom ROM for the Nexus One, the first thing you'd see is dozens of complaints of battery life sucking. It's the same with the SGS, and now the various lag-fixes.

I'm not sure which is more obsessed about with SGS owners; lag, GPS, or battery life.
[Galaxy S I9000 Android Development] RyanZA:
I get tons of emails and messages every day about OCLF, and none have mentioned EXT4 or battery that I can think of. About a million other issues though! Mostly getting to recovery console though. :)

I haven't heard any battery complaints about OCLF so far, but I may have just missed em. Anyway, my complaints with battery life on custom kernels are entirely that - my complaints. Whenever I use a custom kernel and leave my device overnight, it drains around 30% of the battery or more. With a Samsung kernel, it usually drains at most 10%. This seems to be mirrored by others I talk to as well. I believe it may be wifi-driver related - the GPLed driver may not be as good as the proprietary driver or something equally bizarre. :)
[Galaxy S I9000 Android Development] skiddhard:
I agree with the fact that RyanZa's solution is by far the simplest of the methods available. You can easily make out that me is a still a noob.... ;)

I don't speak for others, but my best guess is for some the ease of use matters, and for some, regardless of the complexity involved, the other methods work just fine. It usually really is a personal choice and an equally personal experience. What works best for some, does not necessarily work best for others. Some like a mild fight put up by the hardware, some dont (I dont. Yet!! ;))

Not wanting to get caught in you folks exchange here, but I guess the saying sums it all.

To each, his own....

P.S.: Dont flame for it... ;)

Cheers....
[Galaxy S I9000 Android Development] RyanZA:
Gonna flame you! What are you doing here if you don't like messing with your phone/toy?! :)

But yeah, that's the whole point of computers, phones, and almost everything else. Making it easier for others. :)
[Galaxy S I9000 Android Development] ppeccin:
Wow! Thanks for the answers guys!

I think I'm gonna wait 1 or 2 weeks... maybe the 2.2 update comes to change all of this.

Regards!

Paulo
[Galaxy S I9000 Android Development] Chainfire:
I won't go into saying which method is best, definitely not, nor will I mix myself into ext2 vs ext4.

However, I have seen some people claim both in this thread and in other threads that upgrading firmwares alone is enough. I assure you it isn't. Whether you use mimocan's, mine, Ryan's, curio's, etc fix they all result in having a much faster device. Sure, each of the fixes has their own quirks, con's and pro's, but give it time, one of us will get this exactly right, sooner or later. If not, mayhaps Samsung will.

To be honest, I didn't notice _that_ much difference in speed initially either. And indeed noticed that in some places it was occasionally a tad slower (though with the latest versions of the various fixes I haven't personally experienced this). The only place where I noticed an amazing difference was the email app (5 exchange accounts synced, with 100's of messages a day, on 30-day sync). The difference just blows you away - with setting up the accounts too, not just using them.

But today I had the greatest notice of all. By now some of my coworkers have SGS's as well, but I'm the only one running a lagfix at the moment. It's in the small things: when I put my lagfixed device next to one of their non-lagfixed devices, even with the latest firmwares, it's just amazing how much faster mine is, how much more responsive. Simple taps that resond twice as fast. Granted, theirs aren't usually slow, but mine is just noticably faster, to a level where I'm annoyed by the few millisecond delays when handling their devices.

At the moment, I would say curio's method is the most promising, though certainly not what I would advise just anyone to use. And by curio's method I mean converting the flash itself to a filesystem, instead of using a filesystem image inside an existing filesystem. If his implementation will be the best, remains to be seen :)

Don't make the "n00b" mistake: I don't see a difference, I'll uninstall. Because probably, your device is fresh and clean. Once it gets cluttered a bit the lagfixed definitely help!
[Galaxy S I9000 Android Development] lokhor:
I currently use official JM1 firmware with OCLF apk and find it still lags a bit although not as much. I'm a little worried about the custom kernel fixes not working once froyo comes out as it's mere weeks away.
[Galaxy S I9000 Android Development] zimphishmonger:
Like most, I would say wait till Curio's beta2 is released later this week (hopefully). Ive used almost every variation of every method of seen of the forums, and found the using an ext4 partition on my external sd to store my dalvik-cache and app data is the most smoothest & most reliable 'band-aid'.

Although all the loopback methods work well (EXT2 or EXT4, not getting into it), data corruption is inevitable due to the fact that our loopback partition is never getting properly unmounted on shutdown or reboot. Although the corruption may be mild, I found it eventually starts to lag again as you use the fix for a week or more (more corruption each reboot\power cycle). Even using a fschk, you eventually will get corruption :(

Ive used all the loopback method several times for around a week or so, and found the smoothest, most reliable method is using an ExternalSD for dalvik-cache and app data until a native EXT file system can be put on /data.

Although Ive throughly tested my conclusion (and I wish it werent true, as I love the speed immediately after installing a loopback lagfix), these are simply my observations and I'm throwing them out there for others.

Thanks to everyone who is working hard to fix the "lag" issues on Galaxy S devices. Its quite an ordeal to fix this, and IMO, not enough "thank yous" get passed around, despite differing opinions. :D
[Galaxy S I9000 Android Development] RyanZA:
This isn't corruption that you're hitting, it's probably RAM. You seem to not really understand what corruption will do: if you click an app, and instead of launching it just crashes, that is corruption.

It's possible to make this happen using any filesystem: while downloading an app from the marketplace, pull the battery the instant it finishes installing. When you reboot the phone and try to run the app, it has a good chance of crashing as you click the icon. This is corruption. :)

Corruption can't slow your phone down, it can only stop it from working. Slowdowns are something else - background tasks, high ram usage with bad android task killer settings, etc etc.

You also can't get corruption after using a fsck - it will clean up any corrupt files by deleting them, and remove any bad file links, etc etc.
[Galaxy S I9000 Android Development] distortedloop:
I respectfully disagree, somewhat.

When I upgrade to one of the three firmwares I mentioned above (XFJM6, HVJH1, XWJM7), my phone experienced little lag. I didn't say no lag, and when it did appear after a couple of days, a reboot solved this. For those who want to wait for the issues of the other various lag fixes to be resolved, this is an acceptable solution.

I certainly agree that once you've done any of the lag fixes, your phone will run much "snappier", more "fluid", and don't forget the precious higher benchmarks you'll get.

That said, this doesn't mean that for the typical user the performance of the phone (on the newer leaked firmwares) isn't acceptable. For most people, driving a stock Chevy is just fine for getting around town, but what you're saying is that once a speed freak has supercharged the engine, they'll never be happy in a stock car again. While this may be true for the speed freak, it doesn't make the stock car a bad choice for most.

Certainly Samsung has taken what has all the components to be a turbocharged Corvette, and thrown a transmission into it that turns it into a Chevy Malibu. It's lame, but a Malibu's not a bad ride for most, especially if they've never driven a 'vette.
[Galaxy S I9000 Android Development] Chainfire:
Your points are of course valid. I would however imagine that most folks on here are the "speedfreaks", at least I know I am ;)

Re: usability, as stated my biggest difference is in the email app. Without the lagfix and the setup mentioned in my previous post, opening an email account could well take 3 minutes... Utterly unusable. With lagfix: instant. If it weren for the lagfixes, I would have returned the SGS, 100% sure.
[Galaxy S I9000 Android Development] armaniii:
i'm getting my SGS tomorrow...

So you all recommend to wait till Curio's beta2 will come out?
[Galaxy S I9000 Android Development] distortedloop:
Yeap, I almost mentioned that in my post, that anyone reading this forum regularly probably shouldn't be considered a normal user. I'm a speed freak, also, of course.

I honestly never had that issue with email.

I would have returned my SGS as well, over this lag business, just in the general GUI and responsiveness of the phone in swiping screens, answering calls, etc, if I had had the option, but mine was bought sight unseen from overseas with no option to return unless it was physically defective. I didn't feel like I'd win the "usability" debate with the seller.

I'm still leery recommending the phone to my friends who are ready to upgrade iPhones to a new device, specifically because of the lag issues, though with voodoo, I may start recommending it to the slightly more technical crowd.

Damn you, Samsung, for screwing up what should have been the hottest phone on the market for the last half of 2010.

It just depends on how willing you are to mess around with the phone and how much the lag bugs you out of the box. If you don't mind a lot of tweaking and reflashing roms and undoing previous fixes you've installed, go for one of the ones listed in this thread or the new sticky at the top of the forum. If you're like me, and can burn out on it easily, a few days wait won't hurt. Of course, we're assuming that beta2 will be readily available to the public. Beta1 was short-lived in that regard, and you had to be watching the dev pretty closely to get it.
[Galaxy S I9000 Android Development] rui.mamede:
1 - If you feel like trying a beta, wait a few days for voodoo2 (i'm using beta1 myself and it is FAST and I don't suffer from any wierd problems you might have read about).

2 - If you don't feel like waiting, get a good external sd card and use mimocan's (which still is the "official xda way" of doing it, I used it in the past and it was really good as well)

3 - If you feel like showing off you quadrant scores, install OCLF... But then once again I must cite Cyanogen http://briefmobile.com/cyanogen-demonstrates-quadrants-flaws
[Droid Eris Q&A, Help & Troubleshooting] chaos0422:
So I know if I run the ruu ill lose root, but will it totally get rid of the recovery and everything having to do with root such as the radio returning to stock and the build numbers. What is the stock build number and what is the stock radio.
[Droid Eris Q&A, Help & Troubleshooting] bftb0:
If you apply the RUU or the Leak-V3 "PB00IMG.ZIP" ROM, they will alter:

- hboot

- recovery

- boot

- system

- data

- radio

- "nvram"

and will leave misc, cache, and about 43 MB of "mystery" NAND memory untouched.

Upon the very first boot, the phone will recognize that it is eligible for the July 2010 OTA, which contains (of course) the most recent radio.

http://androidforums.com/eris-all-things-root/87118-reference-what-htc-rom-do-i-have.html

http://xdaforums.com/showthread.php?t=686598&highlight=Consolidated+MD5

bftb0
[Streak 5 Themes and Apps] imperial_patrick:
is there anyway to install the appslib apk. on the streak without getting an incompatible error
[Epic 4G General] robl45:
so my friend has the droid2 and can literally speak in full text messages and have it understand accurately what he is saying. I try it on mine and i'm lucky if it understand 30% of the time. I watched him speak to his and then to mine and his was perfect and the epic sucks. is this something that is better in 2.2 like he has or another flaw in the epic?
[Epic 4G General] gophergun:
I'm not positive, but I think the Droid 2 uses proprietary software for its speech to text.
[Epic 4G General] gamescan:
I've had zero problems with the Epic voice recognition. It's using the standard Google stuff, but it's spot on for me. The only time it has issues is with proper names that aren't standard spellings (like Flickr) but that's to be expected.
[Epic 4G General] robl45:
well I tried again with mine, if I'm lucky, i might get one sentence 100% and then the next sentence it gets a word off or so, not very useful when texting, no problems with the droid2. and i'm not talking about names and stuff like that, just common words.
[Vibrant General] Babyface1249:
I have noticed my battery seems to be draining excessively and the voice calls seem to be the culprit. Attached are two screenshots, one of the overall battery usage over 17 hours, and another showing the hour and a half of voice calls that composed 70% of my battery drain. With these numbers, Samsung's claim of 6.5 hours of talk time seems completely outrageous. Anyone else having similar drainage or is this abnormal? Any feedback will help. I'm trying to decide if I need to ask for a replacement (which would be the second replacement). Oh and battery was at 4% when this screen shot was taken.

View attachment 395827

View attachment 395828
[Vibrant General] wazmoo:
I'm also experiencing the same issue... talked for 4minutes and 44 secs.... and it took 17% of my battery.... my 2nd vibrant btw, 1st one was atrocious and drained even more :(
[Vibrant General] q426669:
Same thing here, unrooting, and trading out tomorrow...maybe that'll help... :/
[Vibrant General] DreamcastDC:
If you are in a low reception area during a call it will drain more of your battery.