yashsingh1/xdaforums huggingface dataset:
[Captivate Android Development] RockRatt:
I believe platypus is not up to date with CM7, and why your getting the baseband unknown. For Escapist kernel it is working perfectly for me at 1.5Ghz and uv'd. For the Escapist kernel you need to know which nightly build your running, for example if you are now on nightly 7.1 then use Escapist #3. If your on an older build of cm7 make sure to get the correct kernel that will work for it. I think the Escapist has the older kernels for older builds in post #1 of his thread and the newer nightly builds in the second post. Come on over the water is good.

Sent from My KickAss Captivated CM7 OC'd 1.55Ghz/Undervolted
[Captivate Android Development] dhostetter:
Modem Issue - Help

I flashed one of the CM7.1 modems listed a page or two back to see if I could get back to the connection speed I had with perception and now I have no connection at all. I reflashed 7.1 thinking it would replace the modem and still no connection. I even reflashed CM7.1 again but no go.

Anyone have any suggestions before I wipe this bad boy and start over from scratch?
[Captivate Android Development] comdei:
What is this talk of 7.1?
[Captivate Android Development] markdexter:
Im on CM7.1, when im plugged into the USB phone will not power off, just restart.

If the phone is off and i plug in the usb, it automatically boots up?? So i can only charge the phone when it is on?? Or is there something im missing, im using stock kernel if that makes any difference
[Captivate Android Development] tjsooley:
no your not missing anything.

P.S. if you read a few posts back you would not of needed your post
[Captivate Android Development] melbourne408:
after flashing 7.1, then Escapist's kernel I simply let it boot, turned off my phone and installed it through CWM and rebooted
[Captivate Android Development] jaysix79:
what version of Escapist are you using?

I tried this multiple times... with couple of clean install from stock... and no matter what modem I use i'm not getting any network signal...

I tried 7.1 with escapist 5.3 (tried it about 6 times)

i tried #16 with escapist 5.3 (i tried this twice)
[Captivate Android Development] Johnston212:
Thanks, back when 16 came out, I asked and got the right one, as well as the one for when I tried flashing back to 15. I got a lot of force closes and issues. I may try it again soon. So far I am definitely seeing an improvement in battery life.

I also think the baseband unknown was due to me attempting to flash one of the 7.1 compatible kernels. I am guessing that they still can't be flashed, but have to be added to the 7.1 update file instead.
[Captivate Android Development] Johnston212:
Yeah, that has been the case for a few months/builds now. I wish it could be fixed, but I just have to deal with it.
[Captivate Android Development] jaysix79:
http://xdaforums.com/showthread.php?t=982776
[Captivate Android Development] melbourne408:
With 7.1 use the Escapist's nightly build #3, not 5.3

Scroll down some more
[Captivate Android Development] kinubic:
got a question. so im running CM& from cognition what i noticed was that there was a Memo pad app in cognition but non in CM& . i do have some important files or memos id il like to get . is it possible to grab em without flashing back to cog restoring via tibi then jsut copying my memos manually or is there a way to grab it from tibi via cm7?

edit.found the file on tibi folder named com.sec.android.app.memo-xxxxxxxxxxxxxxxxxxxxxxxxxxxxx.apk.gz

anyway to read whats on it or so? thanks
[Captivate Android Development] Haloruler64:
Hey guys, I'm on build #16. Is there anything new out? I can't find any info....
[Captivate Android Development] veener79:
Wondering the same thing. I see all the 7.1 talk. When I look for updates the latest one I see is #16.
[Captivate Android Development] cease:
7.1

7.1 is available for download; search this thread for 7.1 Kang. It's a great release and works beautifully! Read why it's called Kang above also.
[Captivate Android Development] RockRatt:
I only got the baseband unknown when I was first trying to install 7.1 and got in a boot loop. I used a name restore back to nightly #16 and still had baseband unknown. So I took the older versions of modems I listed and flashed them via cwm and got my phone back to #16 with the jk4 modem. Then I redownloaded CM7 7.1 and this to.e it installed correctly. I let it boot up. Then I powered it back to the recovery menu immediately and installed Escapist #3 and let it boot up. It showed I had jl3 modem. I then went back out to recovery and flashed EACH of those modems listed AS FOR 7.1 for testing and they ALL worked for me. So I am still running the JV6 modem from the link I put up earlier.

To me it sounds like 1) you grabbed the wrong one from what I posted links to. 2) For some reason your CM7 7.1 isn't allowing you to install the modems correctly. 3) Possibly the stock kernel is not allowing you to change the modems and the Escapist Kernel #3 is letting me. 4) I wish I could help further but I am out of ideas for you unless you try the order I just listed as to what and how I did it. I posted the same links in the modem sticky thread and have seen many who were able to use them without issues (they are the exact same links). Hopefully you get it figured out.

Sent from My KickAss Captivated CM7 OC'd 1.55Ghz/Undervolted
[Captivate Android Development] Haloruler64:
That took a lot of searching lol, thanks. Downloading and will flash soon! Does Escapists nightly #3 work on it? Or will I need to use stock kernel for a while?
[Captivate Android Development] jaysix79:
this one works man thanks...

escapist nightly 3 works with newer build....!!!
[Captivate Android Development] Haloruler64:
Above post answered my question. Thanks. I'm so behind these days O.o stupid finals and school in general. Sorry for the n00b questions!
[Captivate Android Development] snorkle:
Anyone know how to save contacts to sim? The option doesn't show up at all. I'm on 7.1
[Captivate Android Development] makelegs:
JOC...Why would you want to? Google syncs ur contacts to gmail and restores them to phone automatically after a wipe. What's the point of saving to SIM??
[Captivate Android Development] ademejia:
now i can enjoy cm7 with my replacement cappy

finally got rid of that captivate with revision 1007 can't use i9000 modems. But why did they send me a revision 1005 the "home" button dosent light up At&t always finds a way to win.
[Captivate Android Development] RockRatt:
That is weird, two of my phones are 1007 and have NEVER had issues with any modems, kernels,overclocking/undervolting, or roms. They have been pretty perfect as compared to some other revisions. Must of been a bad batch for you I guess. Now my wife's 1010 model works good but has been a little finicky at times, but then the kids get a hold of hers more often.

1005! That is a revision you don't hear about much, I think I have only heard of 1006 on up ever. Well now you can exchange that one too before you get too involved with her...

Sent from My KickAss Captivated CM7 OC'd 1.55Ghz/Undervolted
[Captivate Android Development] Kaik541:
I didn't know that the 1005 revision even *existed*... 1006 is the earliest I've ever seen and I got mine at launch. you may have gotten an earlier revision than retail was supposed to give out.

broken home lighting is liveable, but don't forget you have another 90 days on that warranty replacement.
[Captivate Android Development] ademejia:
oh **** sorry guys its revision 1105
[Captivate Android Development] ademejia:
sorry my mistake was too excited its revison 1105 working great
[Captivate Android Development] superj3211:
what the word on that new KANG build....is it as stable as 11...i been on 11 for a while now...
[Captivate Android Development] pamaguin:
I am stuck in a bootloop, HELP!!
[Captivate Android Development] Smasher816:
Not sure. I haven't had any problems though.

Try in order untill it is fixed

Reflash update

Kernel Cleaner Script

Wipe Data

Go Stock and restart :(
[Captivate Android Development] pamaguin:
I can't go pass the CM7 boot screen; it freezes and reboots. I was trying to go back to stock but phone won't go to download mode. Will a JIG help at this point? If so, I will have to stop by radioshack tomorrow to get some resistors :(
[Captivate Android Development] Haloruler64:
Format /data /datadata /system /cache then reflash the update. If that fails, format the 4 partitions, redownload the zip, go into mounts and storage, mount USB, and throw it on. Might be a bad zip.

And if you REALLY want to flash to stock, I believe a JIG will help.
[Captivate Android Development] Smasher816:
@pamaguin.

All of the things sugested sofar should be done in recovery (minus flash stock).

To get into recovery and download mode without booting try using the 3 button combos.

Recovery = Vol UP+DOWN, +Power.

Download = Vol UP+DOWN, +Usb cable
[Captivate Android Development] pamaguin:
I tried both with no luck...looks like I will be making a JIG tomorrow
[Captivate Android Development] Kaiser_Beef:
Kang

Is clockwork supposed to be missing? I just installed Kang (from zip in recovery from rooted eclair) and there is no clockwork to install google apps, or anything else for that matter. I guess I can find a apk for it but seems a bit odd.
[Captivate Android Development] Haloruler64:
Clockwork is not an apk and is not an app at all. You're probably thinking of ROM Manager. Clockwork is built into the kernel, just hold power and reboot and recovery, and you'll be there. If you want to use a GUI, download ROM Manager from Market, there is a free version (which is usually distributed in ROMs).
[Captivate Android Development] snorkle:
What if my next phone isn't an android?
[Captivate Android Development] emuking:
Have you tried what's posted here? How to unbrick the totally bricked Captivate

It's saved me from bricking my phone two or three times now... Though, I only hope that the kernel for CM7 doesn't prevent this from still working.
[Captivate Android Development] littlewierdo:
Well, to be honest, I am a little confused as to what I should be using.

I perma bricked when I tried running the official European based GB rom that was released for the cappy and then tried to reflash to stock using the 1 click Odin that comes with AIO Toolbox. This 1 click package worked great for me until I had the GB based rom.

I replaced the phone and my new Cappy just refuses to restore to stock using any 1 click package. I had to look for an alternative and I now use a modified

I897UCJH2 image where I removed the bootloader file (sbl.bin) using Odin 3 click v1.00.

I am quite simply afraid of any GB based roms now as my phone was pretty pricey to replace and CM is the only one I trust because they are still using 2.2 bootloaders.

So in short, my new cappy doesnt restore to stock using any 1 click package I have tried and I am afraid of GB based roms because I both dont know how to restore to stock without permabricking (when coming from a GB based rom that changes the bootloaders) and since one click packages dont seem to work for me anyways, I really unsure of the 'proper' method to restore to stock (again from a GB based rom that changes the bootloaders).

This 'was' a fantastic phone for playing with different roms and was virtually indestructible until Samsung changed the bootloaders (which as far as I can tell, no apparent reason).

Even more frustrating is, there is hardly any information on this. There should be warnings galore about this and proper instructions for how to make sure you dont permabrick if coming from a rom based on the new bootloaders back to a rom based on the older bootloaders.

This is really a precarious position that the Cappy is in - should devs start all upgrading their roms to the newer bootloaders to prevent the permabricking? I mean, if every custom rom used the newer bootloaders, this problem would go away yes? The problem of course is getting everyone on the same page and removing any older versions of roms based on older bootloaders...

There are several solutions to the problem, its going to be real interesting when every country has GB available for the cappy as a stock rom. I think we will start seeing bricks galore when people start trying to flash their new Cappy freshly updated to stock GB to another custom rom...
[Captivate Android Development] Palmetto_X:
and that is with no misspellings.................or you will get the dreaded.........

This forum requires that you wait 20 seconds between searches. Please try again in 20 seconds and do not refresh the page or the timer will reset. (This is to prevent robotic abuse)
[Captivate Android Development] Sarcoid:
I've used google contacts with my iphone. If a smartphone can't sync with popular services, it's not smart.
[Captivate Android Development] pparavas:
Even if your next phone is not android you can still get your contacts from google.... what's the big deal in it?
[Captivate Android Development] stuff:
lold @ you.

Any new phone can sync with google's servers to bring back your contacts.. It doesn't have to only be an android.
[Captivate Android Development] tjsooley:
I need help I am on kang 7.1 5.29

I can recive text messages fine and I can send fine.

The problem is that if i send a text to a iphone it says it sent but the iphone doesn't recive them. also the same thing happens if i send a text to my firends blackberry on verizon. I can recive fine and i can send fine to my email.

the smsc is correct. I am on the jv6 modem.

HELP

P.s. does the sam thing on edge or 3g.
[Captivate Android Development] jhernand1102:
I'm on the same build using the JK4 modem and I can send and receive texts & mms to and from my daughters iPhone. Maybe a bad flash, did you try reflashing the 7.1 version?
[Captivate Android Development] tjsooley:
Thanks I have not yet.

I am trying my sim in another phone now to see that.

I will try a reflash after
[Captivate Android Development] Roof King:
I was using google to sync contacts with my Blackberry before I even had an android phone. It's the easiest and most efficient way that I know of to keep all your contacts in one place with ota syncing. Can't beat it.
[Captivate Android Development] tjsooley:
issue was that the smsc on my sim got messed up and cm7.1 cannot change it correctly.

I placed my sim in a bold 9700 and added the smsc and now the textx work on cm7 thanks
[Captivate Android Development] nkrick:
There seems to be 2 different types of rev 1007 Captivates. There is a version that works perfectly fine, and a version that doesn't like i9000 modems. On my 1007, I thought it would not take i9000 modems initially because the couple of times I tried, I had no signal at all. I then read very early on this thread (back in March) someone suggested flashing the modem 2x on a 1007 Captivate. I tried that and it works well for me. The first time I flash a i9000 modem and restart, I get no signal (or if I wait awhile, I can eventually pick up a signal, but can't keep it). So, then I reboot to recovery again, flash the modem again, and the modem will work fine from then on. It doesn't make any sense to me, but I have tested it several times and it always takes two flashes of an i9000 modem to get it to work properly.
[Captivate Android Development] jaysix79:
I don’t know if this one is mentioned before. The issue is when you have your headset plugged in the phone and you make a call. The sound doesn’t come out in the ear piece unless you unplug it and plug it back in during the call, it also happen when you’re receiving a phone call. When you pick up you can’t hear anything and sometimes you end up hanging up cause you think it’s disconnected. Another thing to be you can’t answer call with the headset button.

This happen to me in multiple nightly I just forgot to mention it. It happen on stock kernel and also with other kernel such as escapist, and kangs (also I'm using stock headset by Samsung and I tried other headset)
[Captivate Android Development] nkrick:
You seem to be confused. There is NO official GB rom released for the i897 Captivate. There are i9000 GB ROMs which have been "ported" to the Captivate by modifying the kernel and using the new i9000 GB bootloaders.

To be clear, Samsung has NOT changed the bootloaders for the Captivate i897 (yet). You used a bootloader designed for a different phone that does not work 100% properly on the Captivate.

I completely agree. It is reckless for any of the "winzip developers" / "Samsung ROM chefs" to be creating ROMs for the Captivate based on the i9000 GB bootloader without giving clear information about exactly what is being done, what the risks are, and exactly how to revert back to stock.

Captivate ROMs absolutely should NOT be using i9000 bootloaders. But, since the winzip developers want to play with GB too and don't know how to develop a working AOSP kernel, they are risking their devices and other people's devices by using an unsupported bootloader and not even telling people what they are doing. Just using an unsupported i9000 bootloader is not a solution as it would not work with the existing Froyo ROMs. So unless you are proposing ONLY have i9000 based GB ROM's and removing all traces of Froyo ROMs and CM, there is no way to accomplish this.

I still think you are confused. Only AT&T has the i897 Captivate. The statement " once [sic] every country has GB available for the cappy" doesn't make any sense at all. It appears that you think that all the Galaxy S phones are essentially a Captivate, which is not true except maybe in the broadest sense. The Captivate i897 and the Galaxy S i9000 share a lot of hardware, but are NOT the same phone.

I do agree that there will be problems, confusion, and a lot of bricks, if AT&T/Samsung release an official GB ROM for the Captivate that uses a new bootloader, but at this point, that is an "IF."
[Captivate Android Development] sixstringsg:
In case you didn't notice, all of you have been running 7.1 since the 2.3.4 update. The only reason the filename is different is because it was built on a personal system, not on the buildbot. That is also why it says KANG on it, its the name that upstream gives to it, has nothing to do with the developer kang.

Sent from my CM7 powered captivate
[Captivate Android Development] snorkle:
And the funny part being? Having a back up on the sim is funny? It would be more then stupid to say that no one here hasn't dropped or broken a phone in the past, and what do we all go back to? That brick Nokia for the few weeks tell we get another phone.
[Captivate Android Development] melbourne408:
Ahmen
[Captivate Android Development] nkrick:
I considered saying something about this in the Q&A thread, but I figured it is not hurting anyone to think that they recently "upgraded" from 7.0 to 7.1. ;)
[Captivate Android Development] Keland44:
can anybody confirm if usb tethering and/or hotspot tethering is working on the latest nightly? i'm still on 16 and was looking over the thread after i tried to use it and saw it's not working on 16
[Captivate Android Development] sixstringsg:
Yeah, but then nobody knows which build they're actually running.

Sent from my CM7 powered captivate
[Captivate Android Development] comdei:
I am confuse, are the nightlies going to restart?

How are people getting the updates now, are they compiling themselves.

If so I'm in
[Captivate Android Development] EnemyOfGlaDOS:
The nightlies are not being pushed out because the buildbot is down. As soon as it's fixed the nightlies will start up again. The nightly that you are referring to is the same 7.1kang update everyone else is talking about (..i think:p)

..and yes you can compile your own build. I don't actually know how to do all that- but i believe it's more or less the same as what the buildbot builds.:rolleyes:
[Captivate Android Development] comdei:
Um I'm on nightly 16, is that what everyone is talking about
[Captivate Android Development] EnemyOfGlaDOS:
Nightly 16 was the last one to get pushed out by the buildbot. Everyone else is talking about the kang update.. i think that's the update being talked about anyway:rolleyes:

http://sourceforge.net/projects/teamhacksung/files/captivate/
[Captivate Android Development] Smasher816:
There is also the more recent KANG 7.1

Edit: Ninja (can you delete posts?)
[Captivate Android Development] RockRatt:
I do understand that we have been running the 7.1 since 2.3.4 but why all the talk about differentiating between build Kang 7.1 and the other nightlies #16 and older is the fact the partition for the radio image is different. Since the radio partition is different flashing modems is not exactly the same as in the file. So for right now at least the easiest way to differentiate between them is what we/most have been doing. Other factors come in to play also, for example if you are running specific builds of CM7 nightlies #16, #15, Etc and want to use a Escapist kernel then they were made for each seperate build. If you are on Kang 7.1 then you would use Escapist build #3.

So basically it is how we are calling the nightlies so others know which version of nightly they are running. Not trying to argue with you but just pointing out why it has been discussed this way.

Sent from My KickAss Captivated CM7 OC'd 1.55Ghz/Undervolted
[Captivate Android Development] pvr:
Let me add something here. It might've been AT&T in your case but I had the same issues with Kang1 using JL3, JK4 or JV8.

In all cases the connection was "up" but it seemed intermittent so texts I've been sending through WhatsApp would get there whenever they wanted even though the connection was live.

Reverting back to build #16+JK4 pretty much made my day. Will keep a look for the future but there seems to be something broken in KANG1 regarding data - No, I have no logcats, dmesgs or whatever as I was working while this was going down and I could not care (really) as I needed to have my phone up and alive.
[Captivate Android Development] Smasher816:
Anyone else notice that the changelog page was removed?
[Captivate Android Development] Keland44:
i thought i was the only one
[Captivate Android Development] comdei:
the download link is also down
[Captivate Android Development] wingman_214:
http://download.cyanogenmod.com/?device=captivatemtd

Nothing new.
[Captivate Android Development] comdei:
Wait I'm so confused...

Whos pushing nightlies now..?

kang?
[Captivate Android Development] atinm:
No. All "self" built CyanogenMod updates are called KANG builds - they have KANG in the name. Those just happen to be built by me and I didn't rename them because I don't intend to do any more and it is a KANG build. I would really rather the nightlies just restarted, and we're close.
[Captivate Android Development] chibixzero:
I don't quite understand what do you mean we're closed? You stopping releases?
[Captivate Android Development] RockRatt:
The build bot is down which what was used to make the nightlies. What he is saying is that he is not going to make any further nightlies until the build bot is fixed and we can start using rom manager again. Also he means the build bot is close (as in almost ready) to working again.

Sent from My KickAss Captivated CM7 OC'd 1.55Ghz/Undervolted
[Captivate Android Development] chibixzero:
Okay sorry is a bit late and I'm tired. Keep on keeping the good work man.
[Captivate Android Development] RockRatt:
I saw something posted yesterday in one of the gingerbread roms that if when you are rebooting and ONCE the boot animation comes up, hold down on the menu button and keep holding it until it fully boots up you will be in safe mode. Well I tried it with CM7 Kang 7.1 and it works also. I am guessing that if we have issues we could use the safe mode to do some fixing, just as you would a PC? If so pretty cool. Has anyone tried or used it this way?

And do not be scared but when in safe mode your normal launcher screen will not be there. Just hold down the power button and reboot again and you will be back to your normal screens and apps and all.

Sent from My KickAss Captivated CM7 OC'd 1.55Ghz/Undervolted
[Captivate Android Development] dave1977nj:
any reason why there hasn't been any updates since 16? I know there are kangs but it's supposed to be less stable then the others. :confused: