yashsingh1/xdaforums huggingface dataset:
[Captivate Q&A, Help & Troubleshooting] Zilch25:
Home key and prox sensor (screen not turning off on call) can't be resolved, they're kernel issues. Don't bother pushing files, all you'll do is cause graphical errors and touch screen problems- trust me. I know.

Put the root update on your /sdcard, flash stock captivate kernel, use button combos, install update package, then reflash JPH kernel (search the I9000 boards, they've got a thread about rooting that has a JPH kernel in it).
[Captivate Q&A, Help & Troubleshooting] Kaik541:
I also think the "JPC disaster" we're referring to was the forcing it to show up as a korean phone (and therefore unable to receive later updates) and the thrashing of the els (I think) folder which contained our unlock information. causing even carrier locked phones with the correct carrier SIM cards to be non-functional.

caught a lot of people off guard with an essentially unusable phone if they didn't have the unlock code already. basically it was a terrifying moment for a lot of i9000 users (I think even Zilch lost a phone in the process of playing with JPC?)
[Captivate Q&A, Help & Troubleshooting] Zilch25:
Yeah sorry forgot to elaborate on the "disaster" (sorry, lots of drinking tonight, short term memory failure- you know the drill):

Basically- JPC did what no other firmware before it did... it altered the EFS data in your phone. What's that you might ask? Well you may remember a month of so back the amazingly well publicized story about how Samsung was incredibly stupid and stored all the unlock codes for their phones in a database ON the phones... well, EFS is where that data lives.

Basically what happened was that JPC went in and created NEW nv_data.bin files in the EFS area, which caused locked devices to get jammed at that prompt for a Network Unlock code, in addition it caused I9000 users to lose their normal product code, instead of reflecting that they're from whatever euro country it would show the KOR (Korean) country code to Kies which would very easily screw up future official updates.

This problem was resolvable because Samsung mercifully BACKED UP the nv_data so you could replace the spoofed versions and return your phone to working order
[Captivate Q&A, Help & Troubleshooting] lpsi2000:
Well, I might have tried the JPH if there was a clear guide on this forum on how to get it working on the captivate, a list of the issues, and how to remove it and return back to our Normal builds (Hint Zilch25:D, just kidding:p).

Similar to the way we have everything here, but it seems as the folks who know about all of this do not think it is worth while to create a thread here with this information. I am also thinking may be they did not have a good experience so they figured why bother.

Anyhow the JPC sh*t was pretty scary too. The month of September is pretty busy for me so I don't have the time to experiment too much and put the thread together myself. Plus I need a working phone pretty regularly this month.
[Captivate Q&A, Help & Troubleshooting] BrettS:
Take a look at my guide below:)

As far as getting back to stock, you can just use the one click recover also posted in this forum.
[Captivate Q&A, Help & Troubleshooting] BrettS:
Can someone please explain to me exactly what the .pit file is and what it does? As I've been trying to flash different firmware I'm seeing instructions to use a .pit file or not use one, or to use a specific one and I keep following the instructions like the lemming I am, but sometimes I wonder why I'm doing what I'm doing;)

Thanks,

Brett
[Captivate Q&A, Help & Troubleshooting] BrettS:
OK, I have finally managed to successfully install and root JPH on my captivate. Thanks to (In no particular order) REAVER117, designgears, Aery, Kaik541 and many others:)

Some of the benefits of FROYO include...

Actual functional Bluetooth voicedialing... you can press the voice dial button on your bluetooth headset to initiate voice dialing, say a contact, say yes or no to confirm it's correct, and then have the phone dial the number without actually touching the phone... finally:)

Flash 10.1... some of the websites I frequently use need flash 10.1... and this works for me:) (Note that after you install JPH you need to go to the market and download Flash 10.1. It's a free download)

However, there are some issues too running the I9000 kernal on the captivate. here are the issues I'm aware of...

The home Button functions as Back button. For some reason both the home button and the back button return the same code when they are pressed. Apparently this is a kernel issue and cannot be fixed until we can get a 2.2 Captivate kernel. There is a workaround that can be done to make your search key act as the home button. See below for that information.

The sensors are rotated 90°. When you hold the phone vertically it thinks it's horizontal and when it's horizontal it thinks it's vertical. This means that the auto screen rotation doesn't work (although it has a notification button to stop automatic rotation), but it also means that games and other apps that rely on the sensors won't work either.

The Speaker/Headphone logic seems reversed, will only play audio through speaker when headphones are plugged in. Note that this only affects the audio when you're playing media (sound from videos or music or games, etc). The ringer for the phone, the notifications tones for email and text messages, etc and speakerphone still work normally. It's also been reported that you can plug your headset in part way to get the missing audio on the headset, but I haven't personally tried this. Bluetooth headsets with the A2DP profile will allow you to hear the missing audio as well.

The Proximity Sensor is not functioning - The phone doesn't know when you lift it to your ear on a phone call, so the screen stays on until it times out. When you move the phone from your ear you need to wake it up again before you can dial.

Most of these issues are annoying, but not showstoppers in my case. You can make your own decision and keep reading if you decide you want to move forward.
[Captivate Q&A, Help & Troubleshooting] BrettS:
Here are the instructions to install JPH on your Captivate.

To start, use the one click restore from http://xdaforums.com/showthread.php?t=731989 to return to stock firmware, then use it again to perform a master clear.

Download the I9000 JPH firmware for Odin from the first post on this thread... http://xdaforums.com/showthread.php?t=783596 (the file listed under the header "HOWTO UPGRADE TO JPH USING ODIN"). While you're there, also grab the file under "HOWTO ROOT JPH FIRMWARE" if you want to root it later.

I used the Odin 1.3 from the archive that contained the firmware as well as the 803.pit file in that archive (although a post earlier in this thread suggests that you shouldn't use the 803.pit file). I selected repartition and reboot in Odin and flashed it.

After that, the phone should boot normally into JPH, but at least in the US the modem.bin file that comes with it doesn't seem to work well. I downloaded the I9000UGJH2 firmware from http://www.samfirmware.com/WEBPROTECT-i9000.htm and used WINRAR to open the .TAR file and pull out modem.bin. Using Odin I flashed the phone again with just modem.bin in the "Phone" section. I did not use a .pit file, nor did I select repartition.

If you're happy with an unrooted phone, stop there because you're done. If you want to root the phone and apply the home key workaround, read on to the next post.
[Captivate Q&A, Help & Troubleshooting] BrettS:
Here are the instructions to root your new JPH

First, you'll need the stock captivate kernel from page 1 of http://xdaforums.com/showthread.php?t=734871, and the "Root for JPH.zip" file from this thread... http://xdaforums.com/showthread.php?t=783596 The file you need is the one linked immediately after the heading "HOWTO ROOT JPH FIRMWARE". (If you listened to me above, you already downloaded this file)

Once you have the two files and a working copy of JPH on your phone you should connect your phone to your computer and copy the update.zip file (from within the Root_for_JPH.zip file) to the root of the SD card.

Then put your phone in download mode and run the odin 1.3 from the Root_for_JPH.zip file. (I'm sure you could use another copy of Odin, but this is the one I used). In Odin make sure repartition and reboot are not selected and use the stock captivate kernel that you downloaded from this thread in the "PDA" section.

Let it flash and once Odin says it's complete, pull the battery and boot into recovery mode. (Your phone won't boot normally at this point because the stock captivate kernel won't work with Android 2.2, but that's OK, you just need to get into recovery mode). Once in recovery mode, use the volume down button to get to "apply sdcard:update.zip" and hit the power button to select it. The phone will apply the update then reboot. Once it starts to boot, pull the battery.

Put the battery back in and put it back in download mode. This time fire up Odin again, leave repartition unchecked, but reboot can stay checked. Put the I9000XXJPH_KERNEL from the "Root_for_JPH.zip" file in the "PDA" section, let it flash and reboot and you have a rooted JPH.

Keep reading for the home button workaround.
[Captivate Q&A, Help & Troubleshooting] BrettS:
Here are the instructions for the home key workaround.

Download and install File Explorer from the Android Market (I'm sure you could use another program for this, but this is what I used. Start file explorer (and give it root permission), switch to R/W mode, then navigate to /system/usr/keylayout/ and edit the melfas-touchkey.kl file. Originally it looked like this...

key 158 MENU WAKE_DROPPED
key 139 HOME WAKE_DROPPED
key 28 BACK WAKE_DROPPED
key 107 SEARCH WAKE_DROPPED

Swap the codes for home and search to make the file to look like this:

key 158 MENU WAKE_DROPPED
key 107 HOME WAKE_DROPPED
key 28 BACK WAKE_DROPPED
key 139 SEARCH WAKE_DROPPED

Exit and save it and then reboot. When it comes back up your search button will now work as your home button. Not ideal, but better than having to hit back over and over again to get back home.

Edit: I just discovered that you don't lose access to the search function by doing this. Since the I9000 doesn't have a search button you can access the search feature by holding down the menu button. That works on with the JPH firmware on the captivate as well.
[Captivate Q&A, Help & Troubleshooting] tzones:
How are the other things working with respect to audio headphone/speaker reverse issue, proximity sensor etc. What is your overall take on the performance? any lag issues sofar? Phone quality?

thanks for your time,

TZ
[Captivate Q&A, Help & Troubleshooting] BrettS:
So far so good, but I just got the modem part working this morning, so I don't have a lot of experience with it. I definitely noticed some lagging with JP3 and this seems to be much better than that. GPS seems to be locking very quickly and indoors... which is something that never happened with the stock firmware. Unfortunately the sensor and headphone/speaker issues are still present, but they're not showstoppers for me.
[Captivate Q&A, Help & Troubleshooting] BrettS:
OK, try not to laugh, but I've come up with a (really really) kludgy workaround for the speaker issue.

I took an old set of headphones and pulled out the metal part of the jack... I smoothed it off with my dremel tool and stuck it in the headset jack so there isn't much more protruding than necessary to easily pull it out.

Since I never use wired headphones anyway, this allows my speaker to work all the time.

Like I said... pretty kludgy, but hey... it works;)
[Captivate Q&A, Help & Troubleshooting] irtehun:
I was running this same setup Brett is talking about earlier and it works very well.
[Captivate Q&A, Help & Troubleshooting] hpgt:
I did the install of the jph as listed above by brett but i am running into two issues. First i am only getting edge network for data(on both the modem with the jph and the previous modem file instructions), and second i am not able to flash back to the one click odin or to any other 2.1 version. Odin freezes on do not turn off section. I can only reinstall the jph.

edit:I have the 3g working with jh2, no wifi and still cant flash back to other rom
[Captivate Q&A, Help & Troubleshooting] BrettS:
I'm not quite sure what to make of that. I never had any issues with the one click restore. You might want to post a message on that thread to see if anyone else has run into a similar issue.
[Captivate Q&A, Help & Troubleshooting] hpgt:
Well i just tried odin again first thing this morning and it worked. :confused:
[Captivate Q&A, Help & Troubleshooting] irtehun:
Odin is known to be like that. I had the same issue the other day, switched USB ports and it worked perfectly
[Captivate Q&A, Help & Troubleshooting] cruiserbax:
@BrettS, Ok I think I should make a step by step guide to get it like this. btw it was the calibration that made the proximity sensor work, and it works perfectly. I have to test BT hands free and maybe another BT device to make sure BT works (unless you have tested BT on JPH?) and if it does the only thing you can't do on this phone right now is play some sensor intense games, but since I don't play games on my phone it works perfect for me. I have been using flash 10.1 to watch the Daily Show from their desktop website and it plays very smoothly with some lag when the player tries to auto adjust the quality over wifi (on 3G it stays the same) full flash videos look great in full screen and I don't mind landscape being flipped either. I do use it as an MP3 player in my truck which I normally use the AUX port but instead I am just going to get a BT FM transmitter.
[Captivate Q&A, Help & Troubleshooting] BrettS:
Very nice. I've been playing around with it a little since you mentioned this on the other thread and I'm wondering if shutting off the screen when you're on the phone is a combination of the prox sensor and the rotation sensor... Unfortunately I ran the calibration utility before I tried to play around with it and you're right... my phone is definitely shutting off the screen when it's on a phone call and I hold it vertically and cover the prox sensor with my finger now, however, if I cover the prox sensor with my finger while the phone is horizontal then the screen doesn't shut off. I'm wondering if before the calibration was run if the phone didn't know if it was horizontal and that's why it appeared that the prox sensor wasn't working. Like I said, unfortunately I already ran the calibration before I realized this, so I can't test it at various angles with the prox sensor held unless I reflash... and I'm not planning to do that any time soon.

I did discover earlier that the prox sensor definitely was working before running the calibration utility. You can verify this by going to the phone, dialing *#0*# then chosing "Sensor" from the middle of the screen and moving your finger back and forth over the prox sensor. But until now it didn't actually work to turn off the phone while on a call. Again, though, I'm guessing that it was probably because of the calibration issue... the phone didn't realize that it was in the "against the ear" position when the prox sensor was triggered on a call.

Yes, I have a bluetooth headset (Jawbone Icon) and it works perfectly with JPH... on phone calls and with A2DP for audio.

I'm gonna play with the calibration utility a bit more and see if I can manage to get auto rotate working reasonably well, but so far things are looking reasonably good.

Thanks much,

Brett
[Captivate Q&A, Help & Troubleshooting] cruiserbax:
I just finished testing and yes that is why the prox sensor did not seem to work. also I read your post from before about the *#0*# proof that the sensor was working. I have another idea to get the rotation sensor to work like it's supposed to, but if all else fails I am more than happy with how it works now and it is be far the best rom performance wise that I have used. I will be reporting back this evening.
[Captivate Q&A, Help & Troubleshooting] BrettS:
That would make me very happy. What are you thinking of trying? I'm not sure I'm patient enough to wait until this evening;)
[Captivate Q&A, Help & Troubleshooting] irtehun:
Brett what modem are u using?
[Captivate Q&A, Help & Troubleshooting] Kaik541:
I'm fairly certain that the only froyo-compatible modem that also uses all our bands is the UGJH2 modem from the bell vibrant i9000m
[Captivate Q&A, Help & Troubleshooting] BrettS:
I9000UGJH2. I downloaded the whole ROM, then pulled the modem.bin out of it using WINRAR and flashed it to my captivate with Odin with modem.bin in the "Phone" section.
[Captivate Q&A, Help & Troubleshooting] cruiserbax:
Where can I download a stock dump of 2.1 for the captivate with all the files extracted from the RFS and such I downloaded one but it's no good as it's a tar with rfs inside. I guess if I have to I'll flash back and get the file.
[Captivate Q&A, Help & Troubleshooting] Kaik541:
do a search for "captivate system dump"

one guy has a thread with all four system dumps available
[Captivate Q&A, Help & Troubleshooting] irtehun:
I would really like a step by step guide on the calibration tool.
[Captivate Q&A, Help & Troubleshooting] cruiserbax:
Be patient, I am working on another method that "may" work better. If not then I will establish the best and easiest methods for the mods I currently have and post a guide tonight Hawaii time.
[Captivate Q&A, Help & Troubleshooting] cruiserbax:
Anyone know how to search for a file on the device based on the time that it was modified?
[Captivate Q&A, Help & Troubleshooting] irtehun:
No problem, not sure Hawaii time but probably tomorrow for me.
[Captivate Q&A, Help & Troubleshooting] BrettS:
Take a look at this post... http://ip208-100-42-21.static.xda-developers.com/showpost.php?p=8068152&postcount=14

Does the /drivers/sensor/compass/yamaha.c file mentioned there get compiled into the kernel or into another file that we might be able to pull from the captivate 2.1 ROM to see if it would work on 2.2?
[Captivate Q&A, Help & Troubleshooting] cruiserbax:
Kernel, but let me finish what I am working on, who knows what may come of it.
[Captivate Q&A, Help & Troubleshooting] cruiserbax:
OK, I've unpacked my current boot image and ramdisk so perhaps I can do something with it then repack and flash it back
[Captivate Q&A, Help & Troubleshooting] BrettS:
Are you attempting to fix the sensor/rotation issue or just come up with a good workaround?
[Captivate Q&A, Help & Troubleshooting] cruiserbax:
are you good with adb?
[Captivate Q&A, Help & Troubleshooting] BrettS:
I know enough to get around, but I'm not really an expert... what are you trying to do?
[Captivate Q&A, Help & Troubleshooting] cruiserbax:
I know it is very tricky and can be very time consuming but I have done it before outside of android so I know it IS possible. unpack the kernel/ramdisk and correcting it then repacking it while maintaining the exact original size (from the stock JPH ROM) then flashing it, though I need to be able to root this without re-flashing kernels and such just to make less work for my self while I power through this beast.
[Captivate Q&A, Help & Troubleshooting] BrettS:
Sounds like fun... but a bit above my pay grade, I'm afraid:( The only way I've been able to root this is to flash the captivate kernel, root and flash the jph kernel back.

I did find this, but I'm not sure if it would be helpful to you or not...

http://android-dls.com/wiki/index.php?title=HOWTO:_Unpack,_Edit,_and_Re-Pack_Boot_Images
[Captivate Q&A, Help & Troubleshooting] cruiserbax:
Been there done that, thank you though for your time. I have so much **** in so many directories and I already forget what editor windows is what. I have to go out to dinner with my wife now so I will save>hibernate>hope-it-restores-correctly. I am still partly convinced that if I go back to stock and dump it then run the calinration tool making a significant change then finding where it stores it's values change them around it should work. I know how it reads the sensor is in the kernel but there should be some configuration that tells it what those values should do. see running the calibration tool tells me that those new values are stored somewhere that we should be able to get access to. btw it's not ms3c-yamaha.cfg.
[Captivate Q&A, Help & Troubleshooting] cwimer:
Is AT&T 3g not working with I9000XXJPH?

I have flash the modem file you guys are talking about and calls\texts are working but I do not have any data, not even edge.

Can anyone provide some insight on this please?
[Captivate Q&A, Help & Troubleshooting] BrettS:
Yes, data is working well for me, in fact, I'm getting HSUPA upload speeds... I'm getting 2000-3000k down and 1200-1300k up.

Before you flashed JPH did you revert to stock and do the master clear? I had weird issues one time when I didn't do that. Not with data in my case, but with bluetooth. I've seen other reports of other weird things happening if you don't revert back to stock first. If you didn't already, try the walkthrough that I posted in this thread a few pages back... that method and the ROM's that I linked to are definitely working well for me.
[Captivate Q&A, Help & Troubleshooting] Zilch25:
Check in about phone and under baseband, if it says "Unknown" it's an issue with the modem.

If not, you'll have to manually add your APN settings
[Captivate Q&A, Help & Troubleshooting] cwimer:
I followed your previous posts exactly, I guess I can start over again and then come back. But I flashed to stock, booted then did a master clear. Then flash JPH with the 803 pit. Then flashed the modem file.
[Captivate Q&A, Help & Troubleshooting] cwimer:
How to I go about doing that?
[Captivate Q&A, Help & Troubleshooting] :
Hi Guys,

Can anyone please do me a favor & give me the link of "How to Install JPH" on Captivate please?

Is there any Known issues in bluetooth or Data?

thanks alot
[Captivate Q&A, Help & Troubleshooting] Zilch25:
Open settings and go to about phone =P

It's in the list
[Captivate Q&A, Help & Troubleshooting] BrettS:
The guide I posted starts at post 25 on page 3 of this very thread.

There are no known issues with bluetooth or data, however, there are some other known issues that are outlined in the guide.
[Captivate Q&A, Help & Troubleshooting] :
Is "Flash" working?

Thanks alot for your time, I'm going to check it out.
[Captivate Q&A, Help & Troubleshooting] cwimer:
No, how do I go about configuring the VPN manually?
[Captivate Q&A, Help & Troubleshooting] Zilch25:
To get to the settings-

Go to settings > Wireless and Networks > Mobile networks > Access Point Names

Hit menu button and enter in the settings below:

Name:	AT&T 310 410

APN:	wap.cingular

PROXY:	NOT SET

PORT:	NOT SET

USER NAME: NOT SET

PASSWORD: "

SERVER:	"

MMSC:	http://mmsc.cingular.com

MMS Proxy: wireless.cingular.com

MMS Port:	80

MCC:	310

MNC:	410

AUTHENTICATION TYPE:	NONE

APN TYPE:	internet + mms
[Captivate Q&A, Help & Troubleshooting] BrettS:
Yes. After you finish installing JPH you need to go to the market and download Flash 10.1 (it's free), but it does work. I haven't tried to do a stress test on it or anything, but a few websites that I regularly use that use flash are working well with JPH and Flash 10.1
[Captivate Q&A, Help & Troubleshooting] cwimer:
Thank you I will try that and post back.
[Captivate Q&A, Help & Troubleshooting] quantizationbit:
Same thing for me...pretty much everything ok to JPH. Ok didn't work at first but I rebooted and fine. Now getting HDSPA data. Not sure if it was putting in the APN (but i had none) or rebooting.

I def messed up /efs with all the nv_data files and after putting in froyo used busybox to copy them back in using backups i made in /sdcard. Key thing here is to make sure you have /efs directory correct and right chown/chmod.
[Captivate Q&A, Help & Troubleshooting] Zilch25:
If you didn't have anything in there on first boot then it was definitely the act of adding them that got you data again :)
[Captivate Q&A, Help & Troubleshooting] TheTodFather:
Looks like someone got froyo up for the cappy I saw some linpack numbers today that where in the fourteens...