yashsingh1/xdaforums huggingface dataset:
[Galaxy S I9000 Themes and Apps] MarcusNO:
You dont need to swipe from the arrows on SGS1 , it´s the same that way, hold anywhere and swipe..
[Galaxy S I9000 Themes and Apps] alcurtis93:
I hate to say it but its the same with picture and different icons

Galaxy S - no point in writing rom or kernel constantly changing!
[Galaxy S I9000 Themes and Apps] coldflid:
Another thread like this one posted already:

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

I made a themed version of the original glass lockscreen
[Galaxy S I9000 Themes and Apps] illini71:
I dont know how i missed that thread. I tried the theme it worked, but its not the same as the real thing.

Since its not part of the i9000 rom its must solely made for the S2.

I guess to make it work one would have to get ahold of the S2 rom and pull it out some how.
[Galaxy S I9000 Themes and Apps] Mr Woolf:
Try widget locker mate, put whatever you want on your lockscreen.
[Galaxy S I9000 Themes and Apps] zaanrider:
is this working?
[Galaxy S I9000 Themes and Apps] taha_e:
its already ported to samsung galaxy s you can follow this thread

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

thanks to dhiru1602 for his efforts
[Vibrant General] mugenfiji0327:
Does anyone close to the houston area have a download jig that I can try on my phone before I send it to samung. If so I am willing to meet you up to try it if so please let me know. I would really like to avoid sending my phone to samsung. Thanks in advance
[Nexus S General] Yogi3:
Good luck y'all with the SGS4G ... its Wasatch great phone but its not getting enough love not even from T-Mobile itself ... I now am a proud owner of a Nexus S 4G and this is some fast internet ... Anyways good luck y'all
[Nexus S General] DKYang:
Glad you like the nexus s, but huh?
[Nexus S General] SupaDupaFly24:
Yeah I am kinda lost as well!
[Nexus S General] ScooterG:
Blibbiddyblooblahpblahpbloo to you too!
[Nexus S General] LoveisPeace2012:
Que dijo???
[Nexus S General] Yogi3:
My bad I meant to post this on the SGS4G forum ... if this could be posted in the SGS4G forum I would appreciate it...

PS.

this was just my rant of how I hate T-Mobile and the lack of love to the SGS4G aka the Dreamcast of the phone world ...
[Nexus S General] zephiK:
you do know the number of Nexus S users here are on T-Mobile... right?
[Nexus S General] Longcat14:
Basically, until the Sprint stores open, it's all T-Mobile Nexus S users.

I'm getting a Nexus S 4G soon, but I don't really care what carrier it is, since both T-Mobile and Sprint are great.

Soo... will different ROM's have to be developed for the Nexus S 4G, or not? That's what I wonder.
[Nexus S General] Yogi3:
Well that makes sense cause the AT&T version came out about 3 weeks before the Sprint version...
[Nexus S General] Yogi3:
I was wondering the same thing if the Nexus S stuff would be compatible with the Nexus S 4G...
[Galaxy S I9000 Q&A, Help & Troubleshooting] Wicksy:
At first i tried updating to the latest available update from Kies, once again it ****ed up my phone. So i flashed the latest stock update with Odin. At first i could not open up my Phone app/Contact app tho i got a signal and my Network was working perfect. I went into recover mode and cleared the cache and set the phone to default wipe. Now i get a phone signal, can open up all the applications but i get no Network signal. How can i fix this? Thanks in advanced, Wicksy.
[Galaxy S I9000 Q&A, Help & Troubleshooting] Wicksy:
-Sorry for double, would not let me save with that info for some reason-
[Galaxy S I9000 Q&A, Help & Troubleshooting] kilokilo1066:
Have you tried going into the network APN settings and checking that they are the same as what your network provider uses?
[Samsung Mesmerize] Ntruder:
Basically all I'm trying to do is get a stock 2.2 Mesmerize that isn't all laggy and stuttery, (and I'd love to get rid of that annoying blue hue to the screen). I read that the Voodoo kernel is the best thing for this.

I started with the official 2.2 update from Samsung, and did the following actions in this order:

-rooted with superoneclick (not sure if this step was necessary)

-flashed Voodoo kernal with Odin as per the instructions here: http://project-voodoo.org/installation

-rebooted, heard the robot voice talking about installing the lagfix, said lagfix was complete. Waited another five minutes, yanked the battery and rebooted, and it gets stuck in the Samsung Galaxy S i-9000 boot screen and never boots

-tried to enter stock (blue) recovery by holding the 3 buttons, and it mentioned a mounting error "e:/ can't mount something or another... invalid argument", which apparently is an error you get if you install the voodoo kernel and then do a reset and attempt to change back the filesystem to stock with voodoo still installed

-So I followed the recovery instructions in this thread and once I re-flashed the stock 2.2 ROM, the phone worked. I did not have to make the "disable lagfix" file. It just worked when I flashed.

-This time, I decided to try the non-ODIN method of installing the voodoo kernel, again, as per the developers instructions; by copying the zip file to the SD card, booting to recovery, and selecting update.zip. This was about 5 minutes ago, and my phone has been sitting on a black screen with a "!" inside a triangle with the android robot doing absolutely nothing. I'm guessing I'm going to have to reflash back to stock yet again...

Can anyone figure out what I'm doing wrong here? How do I know if the "Voodoo lagfix" is active? Would flashing back to the stock ROM somehow disable it? I've combed through these forums and read about a million threads, and it seems like I'm missing something.

Voodoo is just a kernel which is just a piece of code that tells your software how to interact with your hardware, correct? And I can just flash a kernel to the phone without doing anything weird, right? Also, lets say I want to remove the Voodoo kernel entirely and revert back to the stock method of software/hardware interaction. How would I go about doing that?

At the moment, I'm not interested in custom ROM's or anything, I just want a smooth phone. (Former iPhone user)

Any advice is appreciated.
[Samsung Mesmerize] Ntruder:
Right now when I boot in recovery, I have the following error:

"E: Can't mount /dev/block/mmcblk0p2

(no such file or directory)"

Not sure if this is relevant. I was able to reboot the phone just fine and it works, but I'm almost certain Voodoo is still not installed... (as is evident by the stock USCellular boot screen and overall crappy, laggy performance.)
[Samsung Mesmerize] akellar:
Yeah sounds like you've jacked up your phone pretty good. First problem was that you didn't flash a kernel built for our phone. You flashed one for the European Galaxy S so that's why it didn't work. Second, you didn't disable lagfix before using odin to get back to stock, which likely caused additional issues with your phone. At this point, you have screwed it up beyond my knowledge. My suggestion would be to go to the #samsung-fascinate irc channel and see if one of the guys there can help you out. For future reference, read the information here before you just randomly flash stuff not meant for your phone.
[Samsung Mesmerize] Ntruder:
Ok first of all, I read on THIS FORUM that the voodoo kernels were generic, so I'm not just banging sticks together. I've spent the last couple days reading thread after thread.

http://xdaforums.com/showthread.php?t=1009414&page=2

Secondly, the phone works exactly as it did when I bought it, so there's no need to get all worked up. I'm just asking for input on what I did wrong. You seem to identified the Voodoo kernel as not being the correct kernel?

Is there a proper Mesmerize EC10 kernel that I should be using?
[Samsung Mesmerize] Ntruder:
Here was the path of reading that I took before "randomly flashing things," all from this forum:

Mesmerize stock EC10 Voodoo lagfix install made simple

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

Which tells you to download the EC10 voodoo kernel here:

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

This thread links to a TouchWiz kernel, which I don't want

Which links to the original post by jt1134 here:

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

and lists several Voodoo kernels for custom ROM's, which I do not want (I want the stock ROM)

Which links to voodoo's site where I downloaded the kernel, here:

http://project-voodoo.org/lagfix

So again, can you point me in the direction of a proper Mesmerize EC10 Voodoo kernel?
[Samsung Mesmerize] add144:
But you see, all of the threads you just posted talk about generic EC10 kernels, and none of the kernels on the Voodoo website say they're generic EC10 kernels. No pro or con, I'm just saying akellar wasn't off the mark in what he said. The threads say generic EC10 voodoo kernels, not generic voodoo kernels. You simply must pay attention.

In continuance of that, you really do have to read what the posts actually say. Those threads you posted aren't trying to direct you from one thread to another, to another, and to another just to give you a kernel. They're giving credit to where the kernel came from, which the OP configured/modified/ported/whatever for our phones. If you keep following the paper trail you will end up with a completely different thing - which is what happened. That Comavolt kernel you posted a link to will be just fine.
[Samsung Mesmerize] scarmon25:
The voodoo kernels in the fascinate forums. OTB and Peanut Butter Jelly time work on our phones. I have used both. If you are on stock froyo then u need touchwiz kernels as u are using a touchwiz based ROM. All of the kernels I have found to work have been from the fascinate forums. They are built off The EC10 source. I would post links but I'm doing this from my phone and am kinda short on time. Under facinate development you should be able to find eithet OTB or the Peanut Butter Jelly time. OTB is by nemmisses2all and PBJT is by imunts. Either ome of those touchwiz will work on stock 2.2 mesmerize.

Rockin Heinz 57 w/ Ultimate Honeycomb and OTB Voodoo.
[Samsung Mesmerize] Ntruder:
I get that now; generic EC10 voodoo kernel =/= generic voodoo kernel. To somebody with minimal programming experience, this is kind of like learning to speak Chinese by moving to China... The level of newbie hand-holding is very minimal amongst the programming community.

Nevertheless, I think I figured out why/how I missed the correct EC10 kernel; I did not realize that "Touchwhiz" refers to the default framework. I read the Glossary twice, but I still had it in my head that Touchwhiz was a custom ROM, so I skipped over any mention of EC10 Voodoo kernels for Touchwhiz, because I wanted to keep the stock ROM
[Samsung Mesmerize] Ntruder:
Right... That was the key piece of information I was missing which led me to an incompatible kernel. Thanks for the advice, I will check those out.

I'm not expecting it to work, as I see someone else did the same thing I did and hasn't been able to get the Voodoo kernel's working since:

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

Although to be honest I'm not quite clear on why you can't flash a kernel that reverts the filesystem back to default, essentially undoing what Voodoo does... Is there no way to remove that kernel completely once it has been installed? Or is the problem simply that when you overwrite it, the filesystems remain changed and there is no software to revert the filesystems back to stock?
[Samsung Mesmerize] scarmon25:
The way I always went back to stock was to diasble voodoo by putting a folder named disable_lagfig in the voodoo folder on the sd card. Rebooted. Then after that's was done I placed the stock ec10 kernel on my card booted into CWM 2.5 and flashed the stock. After that and phone was booted. I would delete the voodoo folder off my card. I have done this several times after going through many different kernels and finding the one I liked. I would revert back to stock kernel and flash the one of my choice fresh. The stock ec10 kernel can be found in ths stick titled files to get your mesmerize back to stock. There is a file there that is just the kernel towards the bottom. I would post links but again doing from phone. Sorry. You will need to odin the cwm.recovery.tar file as well to give you the CWM 2.5. That link should be in that sticky as well.

Edit. That sticky is in the developmemt forum for memserize.

Rockin Heinz 57 w/ Ultimate Honeycomb and OTB Voodoo.
[Samsung Mesmerize] Ntruder:
Ah, thank you. Sounds straight-forward enough. Disable-lagfix file, flash, and delete. I've even already got the stock kernel from that link; I used the 2.1 files in that thread to downgrade to 2.1 when I realized my Mesmerize was missing like 1/3 of the calls that came in
[Samsung Mesmerize] scarmon25:
Yeah USCC is supposedly working on a update to fix the missed call issue. I fortantely havent been as effected by this as some. Glad that helped.

Rockin Heinz 57 w/ Ultimate Honeycomb and OTB Voodoo.
[Samsung Mesmerize] Ntruder:
Yeah that helped a lot. I've always understood the basics of the different pieces of software in our phone's OS, but getting basic information is often pretty tough, because everything is in developer-speak, and everything has its own code name with an acronym, both official and non-official releases. Even the so called beginner guides are all in code, like CWM, touchwhiz, "blue" recovery, etc... You literally need a manual to decode all the acronyms

Anyway, thanks.
[Samsung Mesmerize] Ntruder:
Can we get like a master thread with all relevant links to downloads? I have 17 Firefox windows open right now, all XDA. :) It would be spectacular if we could consolidate all the relevant ROMs, kernels, PC programs, guides, etc into one thread for the newbies (like me).
[Samsung Mesmerize] add144:
Its called tabs. ;)
[Samsung Mesmerize] ChromWolf:
See, this tells me I need to polish the Glossary, because if it's not immediately evident to someone who's read it twice and can, in spite of that, form solid sentences in English, then it means I haven't accomplished my goal.

I may add an FAQ section to the 2nd post as well, a collection of "How To" links to point you to any file you may want to download/process you may want to attempt... All in one thread. That's *sort* of there with Bde's How to Customize Your Phone sticky, but that doesn't cover everything under the sun. That said, my "How To" section, while it would cover everything, would only do so briefly, with links to the real threads. No point in me trying to reinvent the wheel, all those guides have been written already.

Thanks for the indirect feedback Ntruder. :)
[Samsung Mesmerize] Ntruder:
Haha! I meant tabs. I think my mother is the only person alive who doesn't use tabs.
[Samsung Mesmerize] Ntruder:
No, the glossary is spectacular, I'm not sure there's much you could do to make it better. I just didn't memorize it all (yet)

BDE's how to post is pretty comprehensive actually now that I look back at it. What is strangely absent (and everyone under the sun seems to use them) are the voodoo kernels.
[Samsung Mesmerize] defenestrado:
Kernels are in the second post here:

http://xdaforums.com/showthread.php?t=1013312
[Samsung Mesmerize] bdemartino:
Hey - I covered those :)

I noticed now that i didn't really reference voodoo in any of that, so I'll make sure to polish that part off when I get a chance. you seem to have some decent general technical knowledge and if you're struggling to understand then my guide isn't doing it's job (to the best of it's ability) :).

The problem is most of us have been here for awhile now, so as we update guides and post new things we forget what wasn't obvious to us as a new person, so it's good of you guys to call us out so that we can be made aware of these things :).
[Samsung Mesmerize] Ntruder:
Yup, exactly.

I found your voodoo references today actually. Every time I read that post, it all makes a little more sense.

Still having trouble relating to the wrong Voodoo kernel flashed. I have the newest CWM installed with Voodoo but it won't activate. I'm going to try to manually disable the lagfix and reflash to stock and start over, see if that wipes it. The phone works fine, but the lagfix won't turn on.
[Samsung Mesmerize] scarmon25:
Just a thought but if you still have the disable lagfix in the voodoo folder it won't convert. I say you have checked that but just wanted to throw it out there. I personally have been guilty of doing this.

Rockin Hienz 57 w/ Ultimate Honeycomb and OTB Voodoo
[Samsung Mesmerize] ChromWolf:
that's actually why I've never disabled lagfix by way of a file, bit let the recovery interface handle it. that's just how I go about it though.
[Samsung Mesmerize] scarmon25:
That's cool. Recovery does pretty much the same thing I have noticed when I disable through recovery it places the folder in there. But if you have enabled through recovery then it should delete it. Anyway food for thought.

Rockin Hienz 57 w/ Ultimate Honeycomb and OTB Voodoo
[Samsung Mesmerize] Ntruder:
Ha! Yeah I did have it in there at one point but already removed it. Not sure what the i-9000 voodoo kernel did because I can still access my files after reflashing to stock; just unable to get the lagfix running now.

Tried installing the EC10_ulv_voodoo.zip from CWM and I'm getting some installation errors.

"Amend scripting (update-script) is no longer supported.

Amend scripting was deprecated by Google in Adroid 1.5.

It was necessary to remove it when upgrading to the ClockworkMod 3.0 Gingerbread based recovery.

Please switch to Edify scripting (updater-script and update-binary) to create working update zip packages.

Installation aborted"

Anyone seen that before?
[Samsung Mesmerize] scarmon25:
What version of CWM are u running

Rockin Hienz 57 w/ Ultimate Honeycomb and OTB Voodoo
[Samsung Mesmerize] akellar:
You need to downgrade from cwm3. Also just to make sure, don't try to use rom manager for anything as it doesn't work for our phones.
[Samsung Mesmerize] Ntruder:
Ok, I think I need to just put this phone away That is the second time that I've followed what I thought to be a logical link pattern and installed the wrong thing. :o
[Samsung Mesmerize] scarmon25:
We all make mistakes. Its ok. Go to facinate forums under development and find the sticky clockwork recovery. You will find. Cwm.rwcovery.tar file. Download and put that into pda slot in odin. Put phone into download mode. Flash and u will be on. 2.5

Edit. My mistake. I pointed u to wrng forums. I will correct in a min

Here ya go

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

Rockin Hienz 57 w/ Ultimate Honeycomb and OTB Voodoo
[Samsung Mesmerize] Ntruder:
Are you talking about this one?

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

When I flash that .tar file it reverts to what looks like the stock blue recovery. This is supposed to be a red recovery, correct? :confused:
[Samsung Mesmerize] scarmon25:
That's the right thread. If u flash that .tar file then boot using three finger method you should get red recovery 2.5. If u are still getting blue stock recovery then there maybe something else going on. When u flash in odin does it say succeeded 1 failed 0 when its done

Rockin Hienz 57 w/ Ultimate Honeycomb and OTB Voodoo
[Samsung Mesmerize] scarmon25:
Another thing u may try if ur rooted. Download quickboot from market and then choose to boot to recovery from the app.

Rockin Hienz 57 w/ Ultimate Honeycomb and OTB Voodoo
[Samsung Mesmerize] Ntruder:
<ID:0/004> Odin v.3 engine (ID:4)..

<ID:0/004> File analysis..

<ID:0/004> SetupConnection..

<ID:0/004> Initialzation..

<ID:0/004> Get PIT for mapping..

<ID:0/004> Firmware update start..

<ID:0/004> recovery.bin

<ID:0/004> Removed!!

<ID:0/004> Completed..

<OSM> All threads completed. (succeed 1 / failed 0)
[Samsung Mesmerize] Ntruder:
Boots straight to blue recovery. :confused:

I should note, that 3.0 CWM worked; at least I could boot to it. Can't seem to boot to 2.5 CWM after flashing it
[Samsung Mesmerize] scarmon25:
K that's good. Try the app quickboot. You should be getting red recovery

Got ninjad. Sorry.

Rockin Hienz 57 w/ Ultimate Honeycomb and OTB Voodoo
[Samsung Mesmerize] scarmon25:
You may wanna jump on the irc. Honestly this has now went beyond my knowledge at this time. Ill try to find the irc channel for you.

Rockin Hienz 57 w/ Ultimate Honeycomb and OTB Voodoo
[Samsung Mesmerize] Ntruder:
There's no reason why the 2.5 CWM shouldn't come up directly after flashing it... It must have something to do with that original i-9000 voodoo flash I did.

Is it a horrible idea to reflash that incorrect kernel and then attempt to disable lagfix with it installed? Perhaps that kernel is the only one capable of undoing whatever it did. But then again, I couldn't boot the phone with that kernel installed and I'm not quite sure how to push a file from my computer to the phone using ADB. I'm used to the whole "click and drag in windows" thing
[Samsung Mesmerize] scarmon25:
Irc channel is #samsung-mesmerize. Ive never been on it so don't know anything on how to use irc but that's the channel.

I wish I could do more or give ya the answer man sorry. But those guys on there should be able too.

Rockin Hienz 57 w/ Ultimate Honeycomb and OTB Voodoo
[Samsung Mesmerize] scarmon25:
I wouldn't flash that kernel again. Unless they on the irc told me too.

Rockin Hienz 57 w/ Ultimate Honeycomb and OTB Voodoo
[Samsung Mesmerize] scarmon25:
You said in an earlier post u went back to 2.1. Is this correct

Rockin Hienz 57 w/ Ultimate Honeycomb and OTB Voodoo
[Samsung Mesmerize] Ntruder:
That was before I ever flashed any custom ROM's. I just flashed down to 2.1 via one of the guides on here to fix my missed call issues. Then I went back to 2.2, and flashed the wrong voodoo kernel
[Samsung Mesmerize] Ntruder:
Well judging by a few threads I found on XDA, a few people have done the same thing I have done, so hopefully there is a fix.

But as of now, the phone works as stock, so worst case scenario isn't all that bad.

Actually worst case scenario would be bricking the phone, which, with phone insurance, would cost me $100. Annoying, but certainly nothing to lose sleep over
[Samsung Mesmerize] scarmon25:
OK I was just rereading the thread to see if I missed something. Honeslty, it soulds like something may have messed with the recovery side of the phone. Im not a developer and could be wrong but it seems like if it is writing the file to the recovery partition, for what every reason it is not accesing it. The only thing I can think to do would be to get on the IRC. I would suggest ODIN back to stock 2.2 but with knowing for 100% fact that voodoo isn't enable or hasn't converting anything I would NOT do that. Even though you havent gotten the wierd voice it may still be converted.

On another note. You will only get the lady vpice on the inital conversion.

Example, stock to voodoo, lady voice

voodoo to voodoo no lady voice
[Samsung Mesmerize] Ntruder:
I got the robotic voice when I installed the wrong kernel. Not since then. And since after that, the phone was locked up and I had no way of accessing the SD card, I couldn't disable the lagfix, so I had no choice but to flash back to stock and hope that I could disable it after the fact.

Plus, after I installed the incorrect kernel, I already flashed back to stock 2.2 without doing any type of lagfix disabling... (I couldn't) so whatever damage was to be done by that process has already been done.
[Samsung Mesmerize] akellar:
When you get to blue recovery did you chose flash update.zip? You may need to do that at least the first time. Also you will need to have the update.zip file from the cwm.zip
[Samsung Mesmerize] defenestrado:
Odin to stock again, but check the box on the left of the Odin window that says repartition. I can't even remember what I screwed up now, but I had to do that a while ago when I couldn't disable lagfix for some reason, and everything worked perfectly afterwards.

Sent from my CM7'd Mesmerize