(Q) Flashing Galaxy FW Tab over Galaxy S - Galaxy S I9000 Q&A, Help & Troubleshooting

Hi I already hate my Samsung Galaxy S I9000, no matter what your guys do always become slow and slow, I have a iPhone 4 is nothing to compare.
I am thinking to buy a HTC.
The Questios is any one here try it to flash the FW for the TAB over Galaxy S? I am willing to try it.
There is any risk of full brick withour recover?
Any results???

It's not possible to simply flash the firmware from an entirely different device, sorry. It would take work to port it over, and if you don't know how, then that's not going to happen.
If you try the latest Froyo releases JPM/JPA/JP6 which run pretty well already, and once Voodoo for Froyo comes out very soon, I can't see how you are dissatisfied with the performance.
If you need something fast right now, throw on JM9 with Voodoo.
And while you may feel that the iPhone is smoother at times, that's simply because it's doing much less.

Actually I am running JP6 (Kies) with OCLF, but I will try ir JM9 + Voodoo as you mention.
Thanks....
Really I dont want a lot of app running and services in background I just want to switch from one to other fast without lag. I think this is going to be difficult with this device.
But thanks to every dev, here that work hard in order to make this device smooth.

I installed jp6 with oclf - OMG it was slow.
Voodoo + JJ1 is so much faster its not even funny.

You can either wait for Supercurio to finish off his Voodoo kernel for froyo, or you can try the new z4mod. But really, I'm running JPM with no lagfix, and while it's not super-speedy, it's certainly fairly quick in most tasks (NewsRob is borderline acceptable). It's definitely much faster than the older firmwares.

Related

[Q] Refund or Exchange?

My wife recently got a Galaxy S (I9000) and is far far from happy with it....
We tried the OneClickLagFix (improved lag, but still slow accessing the database), then moved onto Voodoo (improves lag significantly).
After this the part that seemed to be slowing the phone down was TouchWiz, so we swapped for LauncherProPlus (big improvement). Anything "Saumsung'd" on the phone is slow (dialer, contacts app, system menus (eg reboot, silent).
My question is ... Is this acceptable to have a 1Ghz phone that is slow, and needs multiple fixes and replacements? I personally have the HTC Desire, although not perfect (small internal memory) it out performs the Galaxy S (stock).
Has anyone gone back to T-Mobile, Vodafone etc and asked for a replacement?
Tony
If it still slow it must be something wrong with it.
What firmware do you use?
My phone is fast and i have no lag.
I use jpk firmware and have the latest oclf.
My girlfriend will buy a sgs also.
She like it more then my iphone and hers phone got stole yesterday.
Sent from my GT-I9000 using XDA App
That is encouraging.. thanks
She is still on Stock 2.1, not ventured into the leaked ROMs yet.
Can I ask which Lag Fix you're using? My understanding is that the Voodoo lagfix cannot con-exist with Clockwork Recovery?
Cheers
I use ryanza oclf.
I use jpk firmware.
I did upgrading first from stock to jm1. Only that was an improvement.
Im waiting also for the real froyo, but jpk firmware working fine for me.
I do plan to use an other lagfix that is in development. I think that will be something sweat for this phone.
Sent from my GT-I9000 using XDA App

[Q] My Samsung Galaxy S is damn sluggish, what can I do ?

Hello people,
I just purchased a Samsung Galaxy S, and the overall user experience is very sluggish.
Is there anything I can do to have a freaking fast and smooth UI just like an iPhone 4 would have ?
I ran a lagfix (OCLF) that almost doubled my Quadrant scoring, but that seems to be the benchmark part of things. The user interface is still damn slow and buggy.
Any help will be appreciated,
Cheers
Depends on how far you want to go. (Ie, are you willing to void your warranty? )
You can start by installing alternative UIs, like launcherpro, or ADW..
Install increasingly warranty-voiding lagfixes, (actually once you root your phone, i think the warranty is void)
Flash a different kernel (check out android dev subforum)
Flash a different rom w/ all the above (I'm using Doc's froyo rom, it's pretty awesome)
nwsk said:
Depends on how far you want to go. (Ie, are you willing to void your warranty? )
You can start by installing alternative UIs, like launcherpro, or ADW..
Install increasingly warranty-voiding lagfixes, (actually once you root your phone, i think the warranty is void)
Flash a different kernel (check out android dev subforum)
Flash a different rom w/ all the above (I'm using Doc's froyo rom, it's pretty awesome)
Click to expand...
Click to collapse
Hi there and thank you for taking the time to answer.
I don't really care voiding my warranty, all I want is a fast phone.
I just installed Launcher Pro, and entering/exiting apps is now much faster.
However, I still experience some lags from time to time. Its weird, I don't even know how to explain it, but the overall user experience is not as fast and smooth as it could be on an iPhone 4 or even on a Windows Phone 7.
So far, here is what I've done :
- Applied OCLF lag fix, which doubled my Quadrant benchmark score
- Installed Launcher Pro
Is there anything else I could do other than flashing a new ROM (Doc's Froyo ROM install procedure seems to be very time-consuming) ?
Cheers
Flash an optimised kernel? Preferably one that has lag fixes in it.. there are a bunch of them in the android dev forum. Remember to undo any existing lagfixes before flashing, or it might mess up..
Don't think doc's rom install thing is really time consuming.. though i guess it depends on how long your definition is took maybe 30 mins to do it, not including downloading time. (And most of that time was spent re-reading instructions to make sure I didn't mess up )
I use autokiller on aggressive.
Never use anything samsung made, like the widgets, the keyboard, the messaging app,the dialer.
I found vooodoo much quicker than oclf in real life but now im using darkies rom. Its ok, but i think stock fw with voodoo might have been faster.
Btw darkies rom is REALLY easy to flash, you might want to try that, just check the devs forum.
theophane said:
Hello people,
I just purchased a Samsung Galaxy S, and the overall user experience is very sluggish.
Is there anything I can do to have a freaking fast and smooth UI just like an iPhone 4 would have ?
I ran a lagfix (OCLF) that almost doubled my Quadrant scoring, but that seems to be the benchmark part of things. The user interface is still damn slow and buggy.
Any help will be appreciated,
Cheers
Click to expand...
Click to collapse
Welcome to sgs world.
Oclf is an old way to speed up the sgs.
The new way is to flash a custom kernel and apply lagfix. Basically you converting the filesystem.
You can also in some kernel apply different tweaks.
Sent from GT-I9000 jpo. My own kernel for z4mod and with 342MB Ram
theophane said:
Hello people,
I just purchased a Samsung Galaxy S, and the overall user experience is very sluggish.
Is there anything I can do to have a freaking fast and smooth UI just like an iPhone 4 would have ?
I ran a lagfix (OCLF) that almost doubled my Quadrant scoring, but that seems to be the benchmark part of things. The user interface is still damn slow and buggy.
Any help will be appreciated,
Cheers
Click to expand...
Click to collapse
If you don't want to stuff around and have a phone that works out of the box sell it.
Does this lag applies to all phones ???
I have mine updated to froyo 2.2 and Installed tons of apps and games and widgets, I cant seem to notice any lag.
Animal06 said:
If you don't want to stuff around and have a phone that works out of the box sell it.
Click to expand...
Click to collapse
I'll be doing this in the very near future, but I want to fully test the device before I say it's crap
Coolman4now said:
Does this lag applies to all phones ???
I have mine updated to froyo 2.2 and Installed tons of apps and games and widgets, I cant seem to notice any lag.
Click to expand...
Click to collapse
Two of my colleges have a Samsung Galaxy S, and I can confirm that laggy behavior on both of their devices.
Here is a video illustrating the problem :
http://www.youtube.com/watch?v=cB1b0UrX9e0
If you make a couple of Google queries, you'll see that the world wide web is full of reviews, topics and videos regarding this problem.
I bet 5 Euro that you're running Android 2.1 in the device.
Logseman said:
I bet 5 Euro that you're running Android 2.1 in the device.
Click to expand...
Click to collapse
Cool, you know owe me a pint of San Miguel
Use cm beta if your willing to out up no GPS or Bluetooth.
Other than that is the most customisable and fastest rom for our phone
~Webstar1
theophane said:
Cool, you know owe me a pint of San Miguel
Click to expand...
Click to collapse
I'll pay it gladly ^^ I've been running 2.1 and I can understand why people would want to get rid of it ASAP.
Still waiting for official SGS Froyo update here in India before doing fixes.

[Q] Captivate Custom ROM Noob!!

Hi,
I have a few questions about Custom ROMs:
1. I have a basic idea about custom ROMs, but what why are there different Kernels for the same hardware? And is one better than the other? What makes a certain Kernel, better? As I understand with custom ROMs, you don't really have a choice in choosing the kernel you run, because each ROM is built on a specific kernel - am I correct about this?
2. I am looking to put a gingerbread 2.3 ROM on my Samsung Captivate, and I am looking for a ROM which is minimalistic Android and doesn't come with, shall we say 'bloatware' - for the lack of a better word. Of course, I would be looking for something stable and optimized for performance. Any recommendations?
Thanks.
1) Different kernals do offer different features. But they are swapable. That is why the kernals are available in seperate threads in the dev section. The biggest feature that is kernal dependent is overclocking. I have never been a fan of overclocking, don't think its needed on this phone. I also have never had good luck flashing different kernals. Whenever I have tried that the ROM runs buggy, freezes, lots of FCs. While you can change the kernal at any time, I have always found best performance with the kenal the dev chose to include with their ROM. I'm sure there are a hundred people here that would disagree with that. Just like ROM choice it's a personal decision.
2)ALL the ROMs here 2.2 or 2.3 will be de-bloated. I have tried all the 2.3 ROMs, and the only thing that is consistent with them is their unstableness. I can't get more than 2 hours of use without a freeze that needs a reboot, or it rebooting on it's own. The only reason I a sticking with a 2.3 ROM is Netflix. The app works on the 2.3 ROMs, but I cannot get it to work on 2.2. If you want something stable and optimized for performance: stay on FroYo. I recommend FireFly. If you want to take the plunge to 2.3 (after you have read EVERY GB sticky twice, paying attention to the bootloader info, or you'll have an expensive paperweight) I recommend GR, Perception II, or Mosaic. Mosaic was the most stable for me, but runs the same touchwiz as froyo, so it just feels like buggy froyo. The other two run touchwiz 4 from the SGS II.
[email protected] said:
Hi,
I have a few questions about Custom ROMs:
1. I have a basic idea about custom ROMs, but what why are there different Kernels for the same hardware? And is one better than the other? What makes a certain Kernel, better? As I understand with custom ROMs, you don't really have a choice in choosing the kernel you run, because each ROM is built on a specific kernel - am I correct about this?
2. I am looking to put a gingerbread 2.3 ROM on my Samsung Captivate, and I am looking for a ROM which is minimalistic Android and doesn't come with, shall we say 'bloatware' - for the lack of a better word. Of course, I would be looking for something stable and optimized for performance. Any recommendations?
Thanks.
Click to expand...
Click to collapse
I have to respectfully disagree with quarlow. He is right about the the kernel swapping, and whatever kernel that comes with the ROM is gonna work and work well. The thing that distinguishes different kernels from one another is again the ability to OC and there is also BLN features and UV capabilities, so it is all user preference. HOWEVER it is the same as flashing a ROM. I have NEVER had an issue or seen a ROM get freezes or FC's because of flashing a different kernel. Not unless your are OC'ing. But it could just be my luck too (with the exception of the trident kernel which came OC'd to 1.4ghz, which was silly because if your phone can't handle that, it won't boot.. luckily mine can)
As far as the 2.3 ROMs go, again I have to disagree. I have been running CM7 for weeks without a single issue. As a matter of fact it keeps getting better. I'm not gonna talk up CM7 but I will say if that other user cannot get more than 2 hours without a freeze or having to reboot, then he is doing something wrong. I have tried Perception (beta2), and C5 RC3.. both are nice. Especially if you want a samsung ROM with all the features you are used to. CM7 is completely different built from AOSP. IMO, they are all really stable to use on a daily basis. Again, if my phone was freezing or needing a reboot every couple hours i would NOT be telling you they are stable.
All the 2.2 ROMs are sweet.. all user preference. Like the quarlow said, make sure you read the OP and re-read the instructions. Bootloaders are something you don't want to F up But, CM7 just got easier, and you don't have to flash any i9000 bootloaders.
Just my 2cents
...no offense quarlow
Coreym said:
...no offense quarlow
Click to expand...
Click to collapse
I take no offense, that's why I said there are probably a hundred people that will disagree with me ... the kernel game is not a game I enjoy. I have never had trouble until I had a ROM with OC enabled, and got the sleeping death, flashed a different kernel, and got freezes, general buggyness, and FCs. I ended up downgrading to the older non-oc version to avoid the sleep death, and had no problems. I have only flashed a kernel a few times before that, and because of that experience none since. Maybe my experience was a fluke ...
I have never tried CM7 because the last time I looked at the installation instructions I didn't feel I understood them well enough ... because of how different it was to the FroYo ROMs of the time (Recovery then install ... 2 steps). Looking at it now, it's not nearly as unusual after all the i9000 GB ROMs. I really have had bad stability with the i9000 GB ROMs. Not that it freezes every two hours, but after two hours of constant use it freezes, and needs a reboot, or every once in a while while listening to music the music stops and I look at my phone to see it have rebooted for no reason. All of the i9000 GB ROMs I have tried did this (some worse than others): Perception, Continuum, GR, Mosaic, Symply, subpression, etc. I've gone back to Stock eclair with a Master Clear, wiped the various caches, nothing I do seems to fix this. I have attributed it to the Beta tag that is still attached to most of the ROMs. Maybe this weekend I'll give CM7 a try.
quarlow said:
I take no offense, that's why I said there are probably a hundred people that will disagree with me ... the kernel game is not a game I enjoy. I have never had trouble until I had a ROM with OC enabled, and got the sleeping death, flashed a different kernel, and got freezes, general buggyness, and FCs. I ended up downgrading to the older non-oc version to avoid the sleep death, and had no problems. I have only flashed a kernel a few times before that, and because of that experience none since. Maybe my experience was a fluke ...
I have never tried CM7 because the last time I looked at the installation instructions I didn't feel I understood them well enough ... because of how different it was to the FroYo ROMs of the time (Recovery then install ... 2 steps). Looking at it now, it's not nearly as unusual after all the i9000 GB ROMs. I really have had bad stability with the i9000 GB ROMs. Not that it freezes every two hours, but after two hours of constant use it freezes. All of the i9000 GB ROMs I have tried did this: Perception, Continuum, GR, Mosaic, Symply, subpression, etc. I've gone back to Stock eclair with a Master Clear, wiped the various caches, nothing I do seems to fix this. I have attributed it to the Beta tag that is still attached to most of the ROMs. Maybe this weekend I'll give CM7 a try.
Click to expand...
Click to collapse
Yeah, i guess now that i look back on C5, there was some lagginess to it- but having the samsung cameras back were a bonus CM7's install is now done from froyo ROMs.. Much easier than the Odin stuff before. Don't even need a computer now
Quarlow ... I think you got a lemon..
If everything was as buggy as you make it out to be I don't think the captivate would have as much dev support as it does. Or as many flashers, If all of us are running fine on our phones and you are the only one with these huge issues that I've never even heard of (force closing from swapping out a kernel) maybe your phone has got a less than adequate component in there, inconsistent builds are a very real thing and looks like yours sucks...
studacris said:
Quarlow ... I think you got a lemon..
If everything was as buggy as you make it out to be I don't think the captivate would have as much dev support as it does. Or as many flashers, If all of us are running fine on our phones and you are the only one with these huge issues that I've never even heard of (force closing from swapping out a kernel) maybe your phone has got a less than adequate component in there, inconsistent builds are a very real thing and looks like yours sucks...
Click to expand...
Click to collapse
How do I fix that? Go to att with "Bad GPS"? My GPS has been fine. I have a build 1006, had this on hold for me the day they released. Never had shutdown issue except that OC kernel I tried. My warranty is going to be up in a month, think I should try to swap before that runs out?
Sent from my Captivate running GR-12
I'd say so ... I have never had the issues you have. I have run every rom with every kernel, never once caused a force close and all the gb roms I've been on have been pretty stable 2 days without even charging let alone reboot.
Does your phone actually have ****ty gps cause if you use that excuse you're gonna have to prove it ... if however your phone for some "strange reason" doesn't boot at all you could use the "i was using kies and it never came on" excuse....
But if you have bad gps while on stock that should be enough to swap it out.
My GPS has always been fine. Longer time to get a lock than my iPhone before, but with 15 seconds it always gets a lock. Would I be better to go with random shutdown?
Sent from my Captivate running GR-12

[Q] Personal Recounts of Rooting + Lagfix

I've been mulling over the idea of rooting my phone just for the lagfix - the unrestricted access to the phone is just a bonus for me since I haven't had the urge to delve into ROMS and other things requiring rooting.
Seeing as there are ways to flash the phone back to stock if the need arises for a warranty (cracked screen, faulty wiring, and what have you) there would seemingly be a small risk in that regard.
For people who have rooted their Captivate, do you find it "the best thing ever"? Can you go back to an unrooted Captivate? I've read many people saying they felt their Captivate performing x2 faster with the lag fix, what are your experiences?
You can read whole forum topics of people arguing about whether lagfix helps or not. It's really subjective and depends on a lot of different factors, so it's kind of like trying to judge which modem has faster data transfer. Maybe it's the modem, maybe it's where you were standing when you did the test My feeling is that it helps initially but I don't feel like it makes a substantial difference in the long run. If the ROM I'm running doesn't have it, I never apply it, but I never remove it if it comes with it either.
As far as rooting is concerned, you are correct that, barring a hardware defect like a bad USB port that prevented you from flashing, you can always go back to stock for warranty work. As long as the warranty situation doesn't bother you, there aren't any disadvantages to rooting as long as you do your research before you dive into your root folder and start deleting things
If all you want is lagfix and nothing more, I personally wouldn't bother. However, if you're looking to ease your way into learning more about the inner workings of your phone, maybe trying different ROMs, and generally tinkering, I think it's a great place to start.
Good luck!
I see, thanks for the information apbthe3!
I've decided to go ahead and root my phone, which I did successfully. Now when it comes to the lagfix, they all seem to be fairly outdated - at least the threads on here. Can anyone point me in the right direction to a working lag fix? As far as I've researched, http://project-voodoo.org/download is a good one, but it worries me because it says it's for "Froyo 2.2" whereas I'm running "Gingerbread 2.3"... will this be a problem?
Honestly, there is no reason I wouldn't want to root a captivate. It is much easier than my past experience with my G1 (HTC dream). Nothing but benefits can come about as a result of rooting your captivate. I would definitely try out flashing ROMs too, that's where you get the best increases in performance.
If you want to stay with Froyo, you can just flash a KB1 kernel that supports Voodoo and root. You can keep stock rom but have Voodoo lagfix, sound and Color fix + root. And In my opinion Lag fix is a big deal on Froyo roms, not so much on Gingerbread, though I use it on I897 roms.
prbassplayer said:
If you want to stay with Froyo, you can just flash a KB1 kernel that supports Voodoo and root. You can keep stock rom but have Voodoo lagfix, sound and Color fix + root. And In my opinion Lag fix is a big deal on Froyo roms, not so much on Gingerbread, though I use it on I897 roms.
Click to expand...
Click to collapse
Will Voodoo lag fix work with 2.3? Did some more reading and apparently it doesn't require your phone to be rooted.
Yes but not the link you posted. You need a kernel for gingerbread that had it baked in...
I see. I guess this is more trouble than what it can provide me. Was thinking it was as easy as a "one click" lag fix thing but after reading around it can get pretty over complicated with some methods...
Vinhwut said:
I see. I guess this is more trouble than what it can provide me. Was thinking it was as easy as a "one click" lag fix thing but after reading around it can get pretty over complicated with some methods...
Click to expand...
Click to collapse
Dont get too overwhelmed. The process of flashing a kernel is downloading one file, connecting your phone, and clicking a button. You just have to make sure its the right and compatible kernel or you risk some big problems. Someone better with 2.3 based roms can help you find a kernel compatible with the stock rom.

should I update to 2.3.5 now?

Is there a point in updating my I9000 to 2.3.5 from 2.3.3 considering ICS for I9000 might be out in the near future?
I'd recommend upgrading to 2.3.5 because I found it to be a lot snappier. Besides, I don't think a stable, fully-functional ICS ROM for i9000 is coming out that soon anyway
i would recomend it too, im curently on a ics port though
but it will take the devs a good while to make a fully functional rom, as for samsungs developers im not even sure if they plan to make ics compatible with our old galaxies
Sent from my GT-I9000 using XDA App
How long do you think it will take the devs to develop a staple working ics port?
well i upgraded from XWJVH 2.3.3 to XXJVT 2.3.5 and tbh i dont see that much of an improvement (if at all), the phone seems more laggy to me (especially on web browsing as i said in this thread: http://forum.xda-developers.com/showthread.php?t=1354323)
im seriously thinking of going back to 2.3.3 (if it was not for losing all the apps and definitions i have on it i would have done it already.)
DarknessWarrior said:
well i upgraded from XWJVH 2.3.3 to XXJVT 2.3.5 and tbh i dont see that much of an improvement (if at all), the phone seems more laggy to me (especially on web browsing as i said in this thread: http://forum.xda-developers.com/showthread.php?t=1354323)
im seriously thinking of going back to 2.3.3 (if it was not for losing all the apps and definitions i have on it i would have done it already.)
Click to expand...
Click to collapse
That's what I thought, if 2.3.5 is such a minor improvement over 2.3.3, then there's really no point. I am happy to use 2.3.3 for the next few months and wait for the ICS.
install jvt and root it with semaphore 1.8.2, install simplicity rom, and convert to ext 4...bet youll think its much more snappy.
BTW simplicity appears very stock looking. hence the name.
thats the thing, idk about OP but atleast i do want to stick to stock as much as i can. (only with root and a couple other things)
i've tried CM7.1 and a lot of other ROMs (haven't tried simplicity, so i dont really have an opinion about it) and i really dont like it, i like the stock feel.
i dont want to get stuff just to beat quadrant's records, i want something (as much as possible) bug-free that i can rely on, not something that i have to be patching and fixing all the freaking time, where the alarm doesnt go off when it should, that can't run some apps, or do videocalls (CM7.1 i'm looking at you), or the icons are plain freaking ugly and different sized...
just my 2 cents, i hope i dont hurt anyone's feeling with this
EDIT: i also hate to lose all the crap and having to install/configure everything again (main reason i dont format my computer that often too), thats why i just want a stable, fast ROM/Kernel that i dont have to patch/fix/reflash/etc for months or even years (or until ICS is released to SGS ).
investmenttechnology said:
How long do you think it will take the devs to develop a staple working ics port?
Click to expand...
Click to collapse
My personal opinion?
Its really hard to tell, they have come very far, suprisingly fast with a new release almost every night. this devs are fenomenal!
i dont think it will take them to much time to get to beta stadium instead of alpha, but i'm an outsider, no real contact with the developers, but if they work out the rest of the problems in the same pace they have done so far it wont take too long to see a good beta build
Waiting hopefully for a new baby to be born!
Off-topic, sorry

Categories

Resources