yashsingh1/xdaforums huggingface dataset:
[Captivate Android Development] nfs_phone:
Not working inside a case

I was afraid I'd get suckered by this, and that's why I mentioned using it while the phone's in a case. This just doesn't cut it in that situation.

I actually bothered to install the ROM and test it out. I can get it to work when the phone's screen is active without touching the phone, but NOT when it's dark. So, no way to get it to work when the phone is in a case on my belt.

I also tried working with Guardian Bob's Bluetooth Launch, but it didn't help. Seems like the current version of Vlingo overrides anything I tried to do with BL.

Looks like I'm going back to a ported I9000 ROM in the 2.2.1 type of flavor. If AT&T releases this as it is in 2.2 format, well, I hope they get sued when someone crashes cause they couldn't use hands free dialing.

-nfs
[Captivate Android Development] Rrryan2:
I get a different md5 checksum on the libsecgps.so in /system/lib/ so a mismatched secgps.conf could potentially even be the problem.

Maybe Samsung *finally* got around to updating the driver. Some of the other gps settings seem to have been improved as well. Jupiter.xml no longer points to the expired spirent-lcs.com for instance, the first time I've seen it changed in any Samsung release. I'm still poking around trying to see what else is changed but nothing else significant so far.

I've been working on a GPS fix (http://xdaforums.com/showthread.php?t=957164) but don't think my fix will play well with KB1 in its present state with the new libsecgps shared object. I could put something together if you want to experiment.
[Captivate Android Development] Pirateghost:
im trying to get it working without a GPS fix at all. i didnt think they could screw it up even more.....
[Captivate Android Development] Rrryan2:
Did you start getting problems before or after swapping in the Andromeda secgps.conf?

Are the SUPL/CP settings in LbsTestMode matching the Jupiter.xml settings?
[Captivate Android Development] Pirateghost:
honestly i assumed it would be needed since everyone includes fixes anyway :P

i am trying it out now without any type of fix, just stock. i will give it a shot tomorrow on the way to work. i just spent the last couple of hours decompiling/compiling apks and jars.....
[Captivate Android Development] rajendra82:
Whatever Samsung did to the GPS in this release is working for me. My GPS was always pretty good, and only flaked out occasionally while moving. That being said, it always took me at least 5-10 seconds to get a lock on the satellites after Google Maps or GPS Status app were launched. After flashing in KB1, and not touching any GPS settings other than deleting old data using LbsTestMode after first boot, my GPS floored me today. I launched Maps, and the GPS was locked to my position with 10 M accuracy by the time the display switched over. Fired up GPS Status a few minutes later, and the moment it updated the screen, the satellites were already locked on and green. Granted it was a sunny and clear day, and I was in an open parking lot, but my phone has never locked on that quick, ever.
[Captivate Android Development] Rrryan2:
They did update the shared object library and the jupiter.xml settings to be less retarded, things that were long overdue and can only help. I'm still combing through to try to figure out if the implementation can still be tweaked. All in all though it's probably the first non-stupid stock configuration I've seen from Samsung.

Among other potential improvements, gps.conf still calls only north-america.pool.ntp.org. This will likely lead to mediocre-ish time syncs for users in North America (it's a big place!) and degraded times for those in other regions.
[Captivate Android Development] Rrryan2:
In this case a drop-in config file from a previous version might be the culprit. Won't really know until I've seen it, and in the absence of documentation, sdk etc. still might not know definitively even then.

Early indications are that the stock config in KB1 might potentially be a lot less retarded than anything we've seen so far. In fact, I have a healthy suspicion that the developers were looking at Da_g's thread quite carefully. Things is, that's not really saying too much and there are still some potential hardware design and manufacturing QA considerations that might be tough to overcome.
[Captivate Android Development] JRd1st:
Maybe this should have been tried out "as is" to see what was broken before we started fixing in.
[Captivate Android Development] rajendra82:
I stll see www.spirent-lcs.com bogus server listed in the jupiter.xml. I have gone ahead to edit that out, and replace it with h-slp.mnc410.mcc310.pub.3gppnetwork.org, to use the AT&T server. I've also edited out the gps.conf to use us.pool.ntp.org. Can't hurt to do that.
[Captivate Android Development] Rrryan2:
Hm. I hadn't managed to extract the .tar, but in looking at Pirateghost's .zip I did see the jupiter.xml with 3gppnetwork.org specified. He didn't mention swapping jupiter.xml specifically but maybe he had. Maybe I'll have to flash the Odin file so I can look at the raw source.

3gppnetwork.org by the way is *not* AT&T's own server. 3GPP is an international industry consortium of which AT&T is only a member: http://en.wikipedia.org/wiki/3GPP

I agree that changing those setting could do nothing but help, at least for US users. Setting NTP to 0.pool.ntp.org might be a better setting for a global user base, or else it could be localized (europe., usa., ca.) etc. for specific regions.
[Captivate Android Development] scottlinux:
Does the camera app in I897UCKB1 allow you to disable geo-tagging?

(Disable with a check box in the camera settings like in Android 2.1?)

I897UCJI6 removed this functionality and all photos are geo-tagged unless you manually toggle the GPS.
[Captivate Android Development] emuneee:
Nope, you still need to manually toggle GPS to turn of geo-tagging.
[Captivate Android Development] xsteven77x:
Ugh...everyime i try to unzip the odin flashable it's corrupted. This computer is about to go out the mother ****ing windows.
[Captivate Android Development] rajendra82:
Use 7-zip. Free, and better than the built in zip support in windows.
[Captivate Android Development] xsteven77x:
Will try that now thanks. Though it was saying it was corrupt in winrar also...I know it is not since not one other person has said this. I have even reinstalled windows completely over this entire issue, and still does not work. Also cannot get kies mini to install either. Saying it cannot copy data to temporary location. Tried it on a win 7 x64, x32, win vista x64, x32 installs, none worked. Unreal!
[Captivate Android Development] xsteven77x:
Just tried still failed. If someone could upload me just the pda file and a .pit one if i need it also i would be forever grateful. I seriously do not know what else to do at this point. I cant install any custom roms because every single one errors out on Line # (depending on the rom) cannot symlink system/xbin/su. Does not matter what rom it is, how many times i have flashed back to recovery, or master cleared. I am totally screwed. If i could just get this pda file at least i can have 2.2. I honestly give up with this and would just really like to have 2.2.
[Captivate Android Development] Pirateghost:
i have seen you post your problems of this same thing ....are you using a download manager or accelerator of some kind?
[Captivate Android Development] RepublicanDaddy:
Installed Cog4 last night...team it all day today.....love it already....absolutely NO ISSUES! A great combination of form, practicality and no bloatware...thanx DG can't wait to see you make this even better with your magic touch.....

Also, with heavy use today, (bluetooth and Wifi on about 60% of the day) I still have 39% battery remaining....
[Captivate Android Development] xsteven77x:
No i am not. And as i asked in the other thread, and not to be rude, but what does that have to do with the symlink error? I have downloaded the roms from the computer and transferred and have downloaded them directly on the phone. The downloads are legit. This phone never had this problem. A couple days ago i flashed back to stock to put cog4 on and this all started. I didnt not do anything different that i did not do the other 50 times i have flashed this phone back to stock and master cleared and installed a custom rom.
[Captivate Android Development] Pirateghost:
the reason i asked is because if you were using a download accelerator or manager, it could corrupt the downloads....

forgive me for actually trying to help troubleshoot...its my job, start out with the basics and work your way toward the goal.
[Captivate Android Development] xsteven77x:
Thats why i said not to be rude...
[Captivate Android Development] xsteven77x:
Sorry if you took my comment as being snippy, was not meant to sound like that. Thank you for trying to help me.
[Captivate Android Development] Pirateghost:
no i understand. i went through a couple hours of this one night....i had a bad line in one of my zip files and after trying a bad one, every one after that failed....unless i rebooted into recovery and THEN tried one that i knew was good....but, my error was it wouldnt even open up the zip file. yours appears completely different....but along the same lines and is definitely frustrating as hell
[Captivate Android Development] stangri:
Pirateghost -- any chance you can re-do your CWM-flashable file with the stock files Rrryan2 referred to?

I'd like to flash it but GPS is essential to me and I'd like to get it closer to stock as the Rogers ROM made GPS usable for me.
[Captivate Android Development] xsteven77x:
Yep! Flashed cog4 (original) which was known to be corrupted and now anything i try to flash is ****ed! Doesnt matter how many times i restore to stock or anything else!
[Captivate Android Development] Pirateghost:
i will do it tonight
[Captivate Android Development] JRd1st:
Awesome, thanks! I'm interested is that too. :)
[Captivate Android Development] pietro_spina:
does flashing this with Odin cause User and Application data to be lost? (of course I'll be backing up) but I'm wondering if an Odin flash of this will behave much like a the Kies flash as published on sammy's site.
[Captivate Android Development] ryude:
That's why I never flash sbl.bin or boot.bin.
[Captivate Android Development] stoobie-doo:
It kept my apps and data; just some widget issues
[Captivate Android Development] pietro_spina:
Thanks for the note. If any one cares, I flashed this on a fully stock att captivate no root no lagfix, using Heimdall on Ubuntu 10.10 64bit and had no problems. The wait at the Galaxy S screen is long. (do your self a favor and do something else while it sits there.)

You just have to untar the zip one step further and put the factory.rfs/zImage/cache.rfs/modem.bin in their corresponding spots in the heimdall-frontend.

It reset my home screens completely but that's no biggie.

EDIT: actually it said Baseband Version "unknown" until I rebooted the phone. now I897UCKB1

EDIT2: and I just noticed that, while it removed the option to set "keep screen on while charging" it kept it the way I had it set (screen on) soo that's kind of annoying.
[Captivate Android Development] stangri:
Thanks man, really appreciate it. If I will be updating from your current CWM (yeah, Rogers ROM was a bag of hurt for dealing with internal SD, so I flashed) to the one you hopefully will push out tonight, will I need to wipe?

thanks again for your efforts!
[Captivate Android Development] ineedaname:
Does this ATT rom have the stupid mp3 ring tone restriction that the leaked 2.2 rom had?
[Captivate Android Development] pietro_spina:
not sure what restriction you are talking about, but I am using an MP3 ringtone I made that is 137KB and had been using prior to upgrade.
[Captivate Android Development] Pirateghost:
http://www.mediafire.com/?7c8le9r43e289e9

it will wipe for you.

also, keep in mind that this includes all the same ATT bloat...i didnt delete that (in this version anyway)

rooted, deodexed, zipaligned, no tethering restriction (warning is still there, but tethering works), added captivate sgs tools and tibu, no 'gps fix', stock kernel + voodoo + cwm, stock modem (UCKB1)

no edits done aside from that...basically just a flashable zip that gets you to a 'stockish' kb1 ;)
[Captivate Android Development] javieromarg:
hi everyone this last couple of days finally we have the emotion we need with this rekease.

i just want to know if any body here will make a mod for the shutdown menu to include reboot and the other custom menus you see on other roms. i have install the custom rom in the first post with voodoo, deodexed and zipaling

thanks for any help you can
[Captivate Android Development] Pirateghost:
there are already mods done. http://xdaforums.com/showthread.php?t=966804
[Captivate Android Development] Radukk:
For those who have unregistered device problem.

Uninstall IE9 first to avoid crash.

http://xdaforums.com/showthread.php?t=822407&page=4

i9000 Doc's ROM or some other i9000 ROMs may change your product code in /efs/nv_data.bin from I897ZKAATT to I897ZKAXEU or something.

I tried odin oneclick, odin 3buttonfix and AIO toolbox and keep getting unregistered device.

Googled, and found This thread.

1. You are on stock JH6 firmware.

2. Root using oneclick or AIO toolbox.

3. Download, install Busybox and RootExplorer(or alternatives) from market.

4. Using RootExplorer, go to /efs folder and delete nv_data backup related files except imei and nv_data.bin.

5. move nv_data.bin to /sdcard folder.

6. mount storage and open nv_data.bin using Hex Editor.

7. Find text string 'XEU' or 'I897ZKA' and change them to I897ZKAATT

8. Save and unmount.

9. Move nv_data.bin back to /efs folder.

10. Mount again.

11. You should have Android SDK and get platform tools using SDK Manager.exe.

11-1. Open command and cd to your SDK installed folder/platform-tools/

11-2. type below

- adb shell

daemon starts running

- su

superuser request popup will be shown on your captivate. Allow it.

then $ will be changed to #

- busybox chown 1001:1001 /efs/nv_data.bin

done!

12. Unmount and reboot device.

13. Change USB setting to Kies and connect cappy.

14. Profit!

Thank to Kard and Methyldioxide and FU to samsuck software.
[Captivate Android Development] stangri:
Thanks so much, will try to flash it over the weekend. What did you do yourself -- did you switch to the stock GPS-related files which were different or did you stay on the previous CWM-flashable ROM you've made?
[Captivate Android Development] Pirateghost:
lol...i dont stay on any rom long enough. right now im using my unlocked TMob G2 while i experiment with my captivates
[Captivate Android Development] javieromarg:
dude 1 million thanks didnt find this i will star working on it. here is the best for android

edit: try it but have to go back because i loose bat mod to bad :(

edit 2: i take the mod framework and run it trow uot Kitchen and came out with all including the bat mod. so now you know how to get it all
[Captivate Android Development] stangri:
Thanks man -- flashed it earlier today and didn't have any problems. Didn't have a chance to test GPS yet, but it can't be worse than GPS in a stock 2.1, eh? :)

Bloat is not an issue since you've included Titanium Backup. I have a license and removing bloat on a rooted phone is a snap.

Thanks again, great ROM!
[Captivate Android Development] qwertyaas:
Sorry to bump this. I have to send my Cap back to ATT. I can just odin3 straight to KB1 with the first link (odin3 version)?

Just place the.tar in the pda slot and start it up? Or should I just odin back to JF6 and kies to KB1?
[Captivate Android Development] Rrryan2:
Unless it came with KB1 pre-installed I wouldn't worry about putting KB1 on it for them. They flash them all anyway and don't really care as long as it's not bricked. JF6 + Master Clear = good enough.
[Captivate Android Development] qwertyaas:
Oh really? I thought KB1 would be necessary now as they were pretty adamant in making sure I had KB1 installed (otherwise their answer would be: KB1 will fix all issues). So I said yes, I had 2.2 installed ;) Which is... true!

I think it's now in their check list before sending in a phone.
[Captivate Android Development] Rrryan2:
They might insist on KB1 before agreeing to take it back, but it's not like they're going to be taking it out of the box and checking it to see if you did. About all they do is check for physical damage, water intrusion etc. and then put it on the pile of ones to get refurbed. As long as you return a working, undamaged phone you should be good.
[Captivate Android Development] qwertyaas:
I see, good point. Although I thought they would check the phone firmware to see if it's official or not, but I doubt they even go that far. Maybe they just check recovery to see if the phone even turns on or not (in which case they see which recovery you have).

Either way, they said keep the extra a few days to test out that it works fine before sending mine back. They said if not, they will try to set me up with a new phone. Although I'm growing attached to the Captivate. Especially now with CM7 coming out and the real quality Roms we have. I can't not use Supernova now!
[Captivate Android Development] stangri:
This seems to be going thru my battery faster than the stock Rogers 2.2. Not sure wherever it's a kernel or the SD filesystem, but the battery life difference is palpable.
[Captivate Android Development] pietro_spina:
with any ROM give it a few days of draining and charging... the first couple of days on KB1 for me I was loosing like 20% over night... last night I lost like 2%

In my case the big variable was that when I lost 20% I was starting from 100% but when I lost 2% I was starting at 35%
[Captivate Android Development] Psyclotr0n:
I'm about to try this as I was going to just try out stock but figured I'd see how this works (i've been trying to run Cog 4.2 but keep getting hard lock ups requiring reboot).

incidentally, any other threads anyone can suggest or bump for stock or stockish ish CWM flashable KB1?

edit: just flashed and so far so good, no crashes, smooth, and got a Quadrant of 1509 :D

now all i need is the stock froyo lockscreen...
[Captivate Android Development] AReynante:
I know this thread was sort of dead, but I had to say thank you. You saved me $430 :D If there was a way to hide / uninstall / change name & icon of superuser, that would be perfect.
[Captivate Android Development] rajendra82:
There is. Superuser is in the market, and you can freely install/uninstall it. The su binary will still remain though, so you are still rooted.
[Captivate Android Development] AReynante:
I tried that, didn't remove the icon that came with the rom
[Captivate Android Development] Pirateghost:
install terminal emulator from the market,

su

accept superuser prompt

rm /system/app/Superuser.apk

you can try that...
[Captivate Android Development] AReynante:
Thank you very much, it worked. :D
[Captivate Android Development] noma_pride:
E:Can't mount /dev/block/stl10

I just flashed the stock 2.2, using Odin3 1.7. Odin PASSed, but then when the phone rebooted, I got a "Can't mount" message on the recovery screen that instructed me to format the media card. So I did, and got this message:

update media, please wait

E:Can't mount /dev/block/stl10

(Invalid argument)

E:copy_dbdata_media:Can't mount DBDATA:

your storage not prepared yet, please use UI menu for format and reboot actions.

copy default media content failed.

Formatting SDCARD:...

update media, please wait

E:Can't mount /dev/block/stl10

(invalid argument)

E:copy_dbdata_media:Can't mount DBDATA:

your storage not prepared yet, please use UI menu for format and reboot actions.

There is no sim, or ext media card installed. If I choose to reboot the system I get the ATT screen, then the Galaxy S screen, but then the screen goes black and the phone does one vibrate every 30sec-1min.

Has anyone ever seen this behavior before? Any suggestions?

EDIT: I just flashed back to stock 2.1 with Odin3 (I have a 1010 build so didn't use 1 click). Everything is fine, but I'm still curious what the heck happened.
[Captivate Android Development] Nnyan:
If I'm running Serendipity VII with the boatloader/kernel will this take care of everything of do I need to handle those things separately?
[Captivate Android Development] Jwtiyar:
with heimdall will this work? and this work for nexus s ?

thanks.
[Captivate Android Development] Pirateghost:
You're joking right?

Sent from my Inspire 4G
[Captivate Android Development] TheBassman369:
Nope, man, we're stuck with AOSP. This will not work on the Nexus S.

Sent from my Google Nexus S
[Captivate Android Development] Jwtiyar:
because they list this thrad from nexus s thread .so i came here.

thanks.
[Captivate Android Development] baghera1979:
Does this package contain bootloaders? I am on GB bootloaders now but am I trying to get back from MIUI. Build of my phone is 1012. Was going to try Cezars safe method of going back to stock but he had mentioned that 1010 builds and higher don't seem to play well with his method. So he linked to this.

Just trying to get all my ducks in a row before I make the jump. Don't wanna hard brick the phone
[Captivate Android Development] 4-2ndtwin:
I looked at the files inside of the .tar that is in the Odin flashable link and the only files that I see are

cache.rfs factoryfs.rfs modem.bin zimage

So, no bootloaders.

Used IZarc to extract the files and take a peek.
[Captivate Android Development] baghera1979:
thanks much. i wanna get back to stock KB1 from MIUI and just dont want to screw myself in the process.
[Captivate Android Development] gemuse:
MIUI doesn't have any exciting bootloaders, as far as I know.
[Captivate Android Development] baghera1979:
right... its supposed to run on froyo BL's but GB ones work as well.

i had a problem before when i went from MIUI to 2.3.4 GB and wound up with a hard brick phone. just being cautious now

want to keep the ODIN flashing to minimum so as to avoid any more problems
[Captivate Android Development] baghera1979:
how long should this take to flash through odin? its been about 15 minutes now and the screen on odin still says FACORTYFS...

ideas? should i just pull battery and try again?
[Captivate Android Development] mrhaley30705:
Try my kf1 package to get back to Samsung framework.

Edit

Use the 3 file one, not the 1 click.
[Captivate Android Development] syanz87:
Please some one update CWM version link in OP.. its dead please
[Captivate Android Development] ou812bkewl:
Link in the OP is updated. Sorry about that.

http://www.mediafire.com/?7c8le9r43e289e9