yashsingh1/xdaforums huggingface dataset:
[Vibrant Q&A, Help & Troubleshooting] zimphishmonger:
Mods, thanks for moving the thread.

I wanted to clarify, as there seems to be some confusion. I was using the Voodoo-modified CWM kernel from Morfic at 1.4Ghz (the one with the "voodoo" red Clockwork Recovery built-in).

I am using Nero b3, no other lagfixes or tweaks to the file system. The key was the error logs that pointed out that fat.format couldnt be executed, because "Linda" actually says "converting system, converting data, etc" but if you check in terminal or via adb, you will still see your partitions mounted as /ext4 (Voodoo Enabled).

Right after pushing the stock fat.format and attempting a conversion back to RFS, it completed the process, AND gave a time estimate (something it didnt do when it errored out). I hope this helps people.

I have attached a FLASHABLE version of fat.format to make things easier for everyone. It just puts the correct file in /system/bin/ so you dont have to work in terminal or adb :D
[Vibrant Q&A, Help & Troubleshooting] BruceElliott:
Thanks, Zimp! This type of solution research is of great value to the community!
[Vibrant Q&A, Help & Troubleshooting] zimphishmonger:
NP, glad to share....:D

OP updated with flashable version (for laziness\ convenience)
[Vibrant Q&A, Help & Troubleshooting] c-brit323:
How did you try to convert back to RFS and what does RFS mean? Sorry for the noob questions. I have just never ran into this problem but you seemed to have saved my phone. I hope lol
[Vibrant Q&A, Help & Troubleshooting] c-brit323:
It says "missing bitmap cannot indeterminate (code -7)" what does that mean!?! I can disable voodoo... But where do I go from there
[Captivate Android Development] ozone777:
The purpose of this thread is to diagnose, and possibly fix, the dropped network connection issue when using i9000 based ROMs on the Captivate.

If you don't know what I'm talking about, then you probably can ignore this thread.

But if, like myself, your connection to your provider's network is hit and miss after installing an i9000 ROM then I want to hear from you.

Why go through all this trouble?

Because most i9000 ROMs run circles around the current Captivate ROMs in terms of speed as well as function.

Bluetooth is a prime example since voice dialing with a BT headset works on i9000 but does not on Cappy ROMs.

It will help if you provide the following:

1. Carrier (mine is AT&T).

2. Approximate date you bought your phone (got mine launch day back in August).

3. Current ROM and/or ROM you experienced the issue with (I've used just about every i9000 ROM out there but currently I'm using Axura 2.3).

4. Your ideas/theories as to why the problem occurs.

5. Any "fixes" you may have tried that improved or solved the issue.

One theory I have as to why this is happening is that my carrier (AT&T) may be intentionally "kicking" me off the network when it sees that I'm using a phone that is configured for another network. (:mad: bastards!)

If that's the case, then maybe there is a way to spoof and make AT&T think the phone is still pure Captivate.

Or, maybe an app can be developed that will monitor connection status and automatically reboot the phone when connection is lost for more than a couple of minutes.

I'm pretty sure we can figure this thing out if we put our heads together.

Thanks in advance for any assistance given.
[Captivate Android Development] Jay120171:
Seems like modem would be an important thing to track IMO.
[Captivate Android Development] stuff:
AT&T wouldn't boot you off. Because if they did, they would have been booting me off daily with my Nexus One.

I was having problems with a rom. When I lost connection (say at my UNI, since they have poor service in the lecture halls) it would reconnect, but data wouldn't ever work again. I would have to reboot my phone to get it to work.

I since reinstalled an updated ROM, but haven't been back to UNI to test it out, since the semester is over.

I just assumed it's a bug in the modem that was being used in my rom.
[Captivate Android Development] hellishhorses:
Carrier - AT&T

Purchased - Launch Day

ROMs Tried - All the i9000 modems lost service and the i9000 kernels paired with captivate modems wouldn't give me call sounds.

Currently on a JJ4 Kernel+Voodoo 5 / JJ4 Modem slow upload speeds but d/l~3.2mbps and definitely seems the most stable as of now

Fix - no earthly idea
[Captivate Android Development] doctahjeph:
Have you tried the new JK3, JK4, or JL3 modems? I had similar issues with the old JG8 modem, but with the new 2.2 modems out there I no longer have these issues.
[Captivate Android Development] DAGr8:
so yea , the jl3 gives me roaming issues ,..

the jk3 rarely does ( and I say like it happened twice)

so I say its the modem ..

btw I m on fido / rogers ..
[Captivate Android Development] hellishhorses:
Yes all three modems tried with JJ4 Kernel- Didn't have in-call sounds (ringing, dialing, other person talking, other person hearing me). Data speeds were great, but I can't live without the phone part of my phone.

AND when I tried pairing the JK4 modem with i9000 kernel it was super fast but kept getting "no service"
[Captivate Android Development] Jay120171:
Not trying to derail this thread and I realize I am new here but are you saying you were running an i9000 kernel on your Captivate? If you run an i9000 ROM you must use a reorientated kernel like xcaliburinhand's.

For reference: I am running Darkyy's 5.5 JPU ROM, xcalibur's reorient kernel 2.2.1 and the JPU modem on my Captivate. I have been running a JPU modem and Darkyy's JPU ROM (5.2-5.5) for a few days now and I haven't had any issues with data.
[Captivate Android Development] hellishhorses:
Yes these were all reoriented i9000 kernels for the captivate

I'm seeing that the phones purchased after the launch date aren't having these issues
[Captivate Android Development] purav17:
I am not sure if i have the same issue...Although my data speeds are very crapy lately...Does this have anything to do with what you are talking about
[Captivate Android Development] ozone777:
So do you think that if I exchange my phone for a more recent one the issue may go away?
[Captivate Android Development] ozone777:
All of those modems dropped service for me.

I'm currently running the JL3 and my service just dropped about an hour ago and I had to reboot to get it back.

That's why I don't think the modem is the issue...it's either in the kernel or the network is rejecting the phone.
[Captivate Android Development] hstuart.2012:
I have been having problems since I flashed Axura 2.2 on my captivate. I do not receive any phone calls or texts, of course my carrier is ATT
[Captivate Android Development] hellishhorses:
That's certainly a possibility. The reason I haven't done this yet is that the inconvenience of having to "stock" my phone then trick AT&T into thinking there's something wrong with my phone even though it's just their lousy service and them retarding the phone so it doesn't beat their almighty iPhone far outweighs the benefits of getting a slightly faster phone. Plus, I'm waiting on a fix for this one, cause I've kinda grown attached to her.
[Captivate Android Development] ozone777:
Is there anyone that has this issue and is NOT on the AT&T network?

Or is it isolated to just AT&T phones?
[Captivate Android Development] Sirfearoth:
i have been having this issue too mainly cm6.1 betas, tried different modems all do the same thing, wondering if its a combo of firmwares
[Captivate Android Development] glitterballs:
You're missing the two most important pieces of information, kernel and modem version.

There after known modem kernel incompatibilities. I've been on an i9000 modem & kernel since we got the first ones back in the end of september or beginning of october, and I've never had an issue with anything.

Build date (underneath the battery) would probably be more helpful than purchase date if it's actually a hardware issue.

Sent from my brain using Thumbs 2.0.
[Captivate Android Development] ozone777:
Who is your carrier and what is the build date of your phone?

Which number is the build date by the way?
[Captivate Android Development] keener31:
there have been a few threads on this. they were also moved because some more than "helpful" people decided it didnt belong in the development forum (i, obviously, dont agree there).

however, we have made some headway. please see the following 2 threads:

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

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

you can continue chatting here or take up over there.

tl;dr - we have been working on this. it seems like launch captivates are the hardest hit, and it seems like i9000 based roms AND modems cause the issue. running a captivate based rom (the most important part) and modem seems to get you back in action. - easiest move: flash cog2.3b6 (dont have a DL link right now and DG took it off his repository) which is captivate based. for performance, toss the latest voodoo kernel in there.

keep us posted on your findings otherwise.
[Captivate Android Development] hellishhorses:
Batch #1006 (assuming that means June 2010, if it's anything like the printed control boards I warranty for work)

Rev. 0.4

I've got a JJ4 modem paired with a JJ4+Voodoo kernel right now and very stable and no "No Network" issues. But it is a fair bit slower than the Perceptions and other i9000 based ROMs. Something I'll just have to deal with I assume.
[Captivate Android Development] SnakeHaveYou:
I'm having this issue too, and i'm on Claro Argentina (850MHz 3G), BUT only with Axura Captivate Edition.

No issue on any other i9000 based ROM..
[Captivate Android Development] Klyentel:
There's an app in the market called "Signal Refresh", cost about 3 bucks, but worth every dam penny. Works beautifully. Keeps me from posting threads like this, although, it would be nice to find a permanent solution to the problem, and not a work-around. But hey, that's what the app market is for right? Whatever is you need to do, there is an app to accomodate the task...lets face it, no phone or computer comes just the way ya want it.
[Captivate Android Development] BLWedge09:
I have the issue of losing all signal randomly (usually once every two or three days) when I'm on a i9000 ROM/Modem too. The framework/ROM must be more important than the modem and kernel though, becuase I've been running Cognition B7 since it came out and haven't lost signal once. For those that aren't familiar, Cog B7 is Captivate framework with an i9000 based kernel/modem combo. dg did this accidentally, but it has worked flawlessly for me. I have since upgraded the modem from jk3 to jk4, but that shouldn't make a difference.
[Captivate Android Development] JayPhill89:
Don't forget to mention Band Selection settings. Even though some i9000 ROMs listed here say they have 850 enabled by default, I've had issues and switching to a newer modem and playing with band settings seems to help (particularly disabling 1900 or 900)

I ran into no signal issues the other day on a JPU modem. Switched to JK4 modem and tried different combinations of enabled frequencies and rebooted.

Its been working better than I've ever seen on any ROM (great service even where I usually had little.

At&t on Darky's v5.5 (JPU) with Setirons 1.28ghz 1.4.3 and JK4 modem
[Captivate Android Development] lpsi2000:
That is a ROM issue with JK3 modem. If you switch the modem or ROM you will be okay.
[Captivate Android Development] ctfeet:
I don't think it's fair to blame AT&T for their "lousy" service since it only seems to be happening on early production phones.

I have the issue and have had it since I first flashed an i9000 rom.

I bought mine on launch date

Have AT&T as my carrier

Currently running Perception B9

The version number is either 1006 or 1008 (my eyes can't tell) rev 0.4

Randomly loses service mostly overnight.

I have an insurance plan on my phone so I may have to "accidentally" drop it and get a later build phone if it is, in fact, build date related.
[Captivate Android Development] Stephenv1971:
I noticed this on my jpu installed. seems 850hz was disabled.

to fix:

*#2263*

combi bands

WCDMA 850 (FDD V)

menu key

(back)

back_key back_key
[Captivate Android Development] dimab:
1. Orange, Israel

2. Bought very close to launch date

3. Axura 2.2 (jk4 modem), Perception b8 (jk4 modem), Cog b7 (jk3 modem), Killer23d's Doc_V4 (jl3 modem)

4. some specific devices that were bought close to launch date got this issue, it looks like more some hardware issue since some people exchanged their captivates at at&t and this problem gone for them

5. install cog b6 (that's what people say)

(i got "1006" under the battery)

there is cog b8 out which is purely captivate (though i got some issues installing it :( )
[Captivate Android Development] keener31:
posted this in the thread we have going on Q/A about this same topic. wanted to share.

that thread: http://xdaforums.com/showthread.php?p=9889923
[Captivate Android Development] bsc7080xsc:
I am running Perception 9 right now, and have experienced this issue on Cognition 2.3b7 as well as Perception 4 and up. Here is something I noticed however, tell me if you all see the same experience at your end :

Whether plugged into my USB port, the wall, or car adapter... it eventually goes to flight mode and thus requires a reboot to get my signal back. However, I have left my phone unplugged for the last 3 hours... and I still have a network connection!

Coincidence ???

1. Carrier : AT&T.

2. Purchase Date : July 2010

3. ROMs : Cognition 2.3b7, Perception 4+

4. Causes : See above

5. Fixes : Don't plug your phone in.... hardly a fix I would think unless we have a way of charging up a separate battery without the phone.
[Captivate Android Development] dimab:
I would say a coincidence...

I had the connections dropping all over the day, both while having the phone plugged and unplugged...
[Captivate Android Development] 10tonhammr:
Carrier: ATT

Phone: Captivate

Batch #: 1007, purchased sept. 2010

Rom(s): All non-captivate based roms (Perception, axura, di11's, tayutama's doc's, mikeymike's)

Kernels: Cogkernel2, 3, and 4; Setiron's (most of them), xcali's

Modems: JPM, JK2, JK3, JK4, JJ4, JL3, probably others I'm forgetting

My problem has persisted across all of the different variations I listed above. Every time I reboot/battery pull/shut down, I have no data connection initially when I turn the phone back on. Toggling airplane mode, data networks, or wifi does nothing. The only way to restore data connection is to toggle Mobile Ap on and off, and poof, data is back up and running. Always works.

During these "dark data" cycles phone calls and text message services are not affected, just data. This issue has persisted on ALL the rom's I've tried (most of the roms available for the captivate) that are NOT captivate based. Every time I flash back to stock, the issue is gone. Every time I flash Cognition (DG's captivate based rom) the issue is gone. Its only i9K and vibrant based roms.

I have flashed my phone more times than I can count, and I'm meticulous when doing so. I've also experimented when flashing and changing up my normal routine and nothing works- and like I said, whenever I flash Cognition, the issue is no longer present.

Weird, right?!!?!!!??!

This is nothing more than conjecture for the sake of comedic irony (because I really have NO IDEA why this is happening) but if AT&T really is to blame, its hilarious that the only thing that fixes the problem (Mobile AP) is a feature AT&T says I'm not supposed to have, lol.

At this point, I just deal with the issue because I love Perception and its really nothing more than a minor inconvienence, seeing as how it only happens when restarting the phone.
[Captivate Android Development] hellishhorses:
Don't want to get anyone's hopes up but I've been running six consecutive days on Perception 9 (JL3 Kernel/JL3 Modem I believe) oc/uv - off. Recharged twice, once from dead, once from ~7%. I have yet to have any issues that I have seen. It may be dropping service whilst in my pocket and I wouldn't know about that, but no dropped service while in use. Several speedtests performed, lots of browsing/downloading, texting, handful of calls all virtually flawless.
[Captivate Android Development] derek_h77:
did you fully recharge the phone to while still turned on? i've seen my service drop once the battery hits 100% with the phone still on.
[Captivate Android Development] hellishhorses:
Yes, fully recharged with phone on last night with no issues :fingerscrossed
[Captivate Android Development] dimab:
Still no disconnects? Anyone else tried it?
[Captivate Android Development] hellishhorses:
Day seven, phone did randomly shutdown this morning :confused: but has otherwise been stable
[Captivate Android Development] ozone777:
If anyone is still watching this thread, I have an update:

After trying every "fix" I came across to no avail, I finally gave in and traded in my phone for a newer version.

I had version "1006" and the phone I got yesterday is version "1009"...the newest they had at the ATT service center.

I'm happy to report that after 24 hours with an i9000 ROM installed, I have NOT experienced any drop in service! :D

In fact service has been better than ever and GPS was working, out of the box, without any modifications.

With the "1006" phone, I never got more than 6 hours of stability using any ROM other than Captivate flavored. And my GPS was always hit and miss.

Now, after installing the Serendipity ROM, GPS is still working great and, as I said above, no drop in service after 24 hours.

It may be too soon to make a final judgement, but I feel pretty positive at this point. I'll report my progress after a couple more days.
[Captivate Android Development] Kaik541:
Carrier: AT&T

Purchase Date: July (Batch 1006)

ROM: Perception/Phoenix/Darkytt3r

Idea: As we've all said, seems to be directly related to 1006 batch. I think it's also possibly related to 2.2.1/2.2 discrepancies.

Fix: I've noticed when using a 2.2.1 modem (the only one I know of that works with our phone natively is the i9088KP1 modem) with a 2.2.1 kernel, I don't see this issue.

Running a 2.2.1 kernel with 2.2 modem = "no service" when fully charged or random lack of use

2.2 kernel with 2.2 modem (earlier builds of perception) = never saw this issue

2.2 kernel with 2.2.1 modem = "no service" but less often

so far, the way I've seen to "fix" it is to use either JK3 with a 2.2 kernel (where I never once ran into the issue) or to use KP1 with a 2.2.1 kernel (I only got "no service" once, but it was actually in a place where I get no reception)
[Captivate Android Development] ozone777:
I had tried most of those combinations (except for ones with the i9088KP1 modem) with my 1006 device and always ran into the dropped service thing.

It's been a day and a half now with the new 1009 model and still no dropped service! :p

So far so good.
[Captivate Android Development] Dankenstein:
I was having issues with GPS & battery without any i9000 ROM's. But that was it.

Then I tried flashing the 2.2.1 ROMs and other i9000 reorienteds. Data connections nowhere to be found --- GPS screwy (even for my Cappy) ---- and Gmail just deciding to stop sending (this was the ONLY problem I had while running Tayutama's JPM Froyo w/Xcaliburinhand's Re-oriented Kernel - 11/04/2010 ----- which is the ONLY "newer" ROM other than a DesignGears creation that I could even run with any semblance of working. But even that reliable, quick and awesome JPM based ROM let me down eventually with the Gmail sending issue and Outbox saturation.

. . . or should I say that my phone let the ROM's down . . .

Well, I got tired of fiddling and tweaking. So more reading led me to this thread. And then I re-examined my attachment to this exact phone . . .

Went to AT&T local -- redirected to the service center. My closest one was one of about 1/2 dozen in the NY Metro area, and it took me longer to find parking nearby than to get to it from my apartment. Anyway, exchanged my 1007 for a NON-serialed re-conditioned (NOT refurbished or used -- I discussed it at length and real lawyer-like with the patient Warranty Center rep.).

Within 10 minutes, I had confirmed everything working (3 button fix, too. Although this was never a problem for my 1007 phone)--- and I had flashed Andromeda.

Shocker . . . everything worked, including hyper-fast H data connection (which had only worked for like 15 minutes during one of many i9000 flashes on various different recent ROM's). Wifi works awesomely -- mobile AP works awesomely

. . . and the GPS location

AND

tracking . . . fuggeddaboudit.

NOTE TO ANY CAPPY OWNER INSIDE THE YEAR, WHO IS ANNOYING THEMSELVES WITH THESE ISSUES:

GO EXCHANGE YOUR PHONE. DO IT NOW!

Seriously. I can't begin to tell you how much happier I am now.
[Captivate Android Development] degenerazn:
This thread finally explained to me what no one else was ever able to figure out.

I guess I have the very first release of the Captivate, 1006, and have never been completely happy with any of the roms I've tried. Major issue is always with dropped signals and going into airplane mode.

Now I just gotta find some way to convince ATT to issue me a new phone without telling them mine's not working cuz I want to use custom roms.
[Captivate Android Development] Dankenstein:
Heh. Funny you should mention it. Should have responded to you here, instead of the PM -- for all to benefit.

As I said, my issue with the i9000 ROMS and (non-WiFi) data connection has NOT been fixed . . . and here's the text of the PM response I sent (yes, I am an effort economist):
[Captivate Android Development] degenerazn:
Thanks. My question to you was more of, how did you convince AT&T to replace your phone since I'm assuming, everything works fine when its stock, its only when you flash to I9000 roms that you're experiencing problems.
[Captivate Android Development] gerbig:
I've been having a problem with the at&t connection going away during charging (especially charging when full or right after unplugging) on Darky's ROM. I was traveling in a place with terrible 3g (vegas!) so I switched my phone to 2g only (settings-mobile networks-network mode-gsm only) so that I could at least place calls. When I got home, I forgot to turn my phone back to 3g (gsm/wcdma auto).

Long story short, I've found that my phone doesn't do the no service thing if I charge it overnight in gsm only mode. I unplug it and turn it back to auto in the morning and it seems to avoid the problem (5 days in a row when it used to happen everyday).

So far this is keeping me happy, but I may decide to exchange my phone at some point anyway. If everyone having this problem is really on a 1006 or 1007 phone then I think they'll all qualify for exchange because of the "shutdown problem".

I have no idea if this will fix the issue for anyone else, but 5 days in a row seems like more than a fluke to me :)
[Captivate Android Development] dimab:
Still working with perception? with no disconnects?

I'm so jealous of you guys who can go to at&t and switch the phone for newer version, unfortunately i bought it form ebay to get the phone to israel so it's not an option for me :(

gonna try today some newer roms, will report then,

meantime i'm with cognition b8, and with sucky gps...
[Captivate Android Development] h8rift:
I can verify this issue resides with certain builds of Captivate.

I have one I purchased close to launch day:

Build 1007 - Hates i9000 modems (issue mentioned here occurs)

Was given another Captivate from a friend:

Build 1008 - Has absolutely no issue with an modem i throw at it.

I'd assume 1006 and some 1007 (if not all) have this problem.

Thought i'd throw some more data at ya :).

Thanks!

-h8
[Captivate Android Development] k2snowboards88:
I originally thought this could be a network topology thing, where it affected us because of where we live. I received a new phone the other day because I had the shut down issue. The new phone handles i9000 roms without problems. It's definitely a phone issue.