yashsingh1/xdaforums huggingface dataset:
[Captivate Android Development] Thnikk:
Look back a page.
[Captivate Android Development] rwells813:
Good find, yea it works. Tried it on nightly 16

SGS SGH-I897 CM7 2.3.4 Using the CyanXDA App
[Captivate Android Development] Emperor Jon:
Not that it's a huge deal or anything.. But it was something I liked about the Captivate and all other roms I've tried..

But is there any way, from the contact list, to restore the function where you can swipe the contact left to make a phone call, and swipe right to send a message?

Forgive if this has already been answered or addressed, I tried to use the search function on the forums but it's been down :(

Any answers would be much appreciated. Thanks :)
[Captivate Android Development] RockRatt:
Yes it has been asked before in this thread but I know it is a long post so finding would never be easy, but from what I remember it asked before is people wanted it and no was the answer since it is a samsung thing. But for something like that to be implemented would probably need to be brought up higher up the cyanogenmod chain. I have never looked for it but there is a place to make feature request I believe. I too liked it and have just gotten used to it. That said something like that would be very cool. Maybe you can look it up or I will try also to see where to ask about feature request.

Sent from My KickAss Captivated CM7 OC'd 1.55Ghz/Undervolted
[Captivate Android Development] RockRatt:
Now what can be done in Safe Mode? If we are in a boot loop can we get into safe mode to change something/whatever we tried doing that caused a boot loop? Is it so we can restore something safely? I have been wondering what we really could use it for. Hoping one of the development Dev's this and can explain.

I know what can be done for fixing things in safe mode on a PC, just wondering what effect it would be for our phones.

Sent from My KickAss Captivated CM7 OC'd 1.55Ghz/Undervolted
[Captivate Android Development] Emperor Jon:
You seem to be relatively knowledgeable in this department lol.

I've been trying to find info on this on google, but haven't had much luck... Any other suggestions on where I might look? Or who I might be able to escalate it to?

On another note, since you seem to be really helpful :)

I just flashed and am coming from Firefly rom. I actually enjoyed the keyboards they had on that rom..

I don't suppose you know of any way I can find either similar keyboards, or port those keyboards to this rom eh?
[Captivate Android Development] rwells813:
My bad, with this post. Chuck will find me dont worry
[Captivate Android Development] rwells813:
This was mainly the most talked about I found is that you can fix " force close loops" app's that act up/causing a boot loop. If were to occur, sometimes you wouldnt be able to uninstall the app like normal. So theres safe mode to do that, but I am also curious as to what differs And any other real usefullness of this on our OS. Lol I was hoping you knew.

SGS SGH-I897 CM7 2.3.4 Using the CyanXDA App
[Captivate Android Development] Johnston212:
I'm wondering about this "new" version of CM7 that I keep seeing mentioned lately. I've noticed a few people talking about CM7 Kang 7.1.5...., but I can't find anything on the sourceforge site. I'm currently on 7.1.0, which is what is on the sourceforge site. Am I missing something?
[Captivate Android Development] littlewierdo:
It has been reported that there is an official GB coming BUT given that they made the same announcement for Froyo and we saw how long it took for that to happen, I dont have high hopes.

Back to the distinction between i9000 and i897 phones, I had a brain fart but it is partially not my fault.

Often times, roms will say 'uses 2.1-2.2 Froyo bootloaders' or 'uses 2.3 GB bootloaders'. This is where the disconnect happened I think for me.

These are not Froyo/GB bootloaders, these are i9000 and i897 bootloaders (if I am understanding you correctly).

Even Cyanogen is guilty of using the wrong nomenclature (I believe it states 2.2 bootloaders are used) by stating incorrectly that they are Froyo / GB bootloaders when they really are in fact i9000 / i897 bootloaders.

I guess what we need is for an official GB based rom for the cappy so that all of this can go away. I dunno, I love my cappy but I am frustrated beyond belief with how disorganized it is and even further, the blatant disregard for other peoples hardware when you just post a GB rom that has a very real possibility of permabricking.

Ive had perfectly good roms just soft brick for no particular reason during the install - it happens all the time. But if it happens for one of these i9000 roms, you are screwed and I think the lack of responsibility on the part of people posting these roms... well, I better stop before I piss everyone off...
[Captivate Android Development] Maltz:
Guys is any one having problems with 720p recording?
[Captivate Android Development] Smasher816:
@littlewierdo

I am almost 100% sure that cm7 does NOT touch your bootloaders. That's why they have you flash back to the stock 2.2 ones. The perm-bricks come from an incorrect match of pbl and sbl, or a bad flash. This is all because the ginger leak has changed bootloaders, besides flashing that you should never need to touch them.
[Captivate Android Development] EnemyOfGlaDOS:
+1. All the other gingerbread ROMs are based on the i9000 source and mess with bootloaders (GB Bootloaders ), which (+1again) you shouldn't mess with them:)
[Captivate Android Development] aehlayel:
"Please wait, while loading changesets and nightlies...

Device not found. Maybe you misspelled the device name in the url, or device isn't supported yet. This is still WIP, i'll add all CM supported devices eventually. Please click a link in the header."

anyone else seeing this on the device specific changelog?
[Captivate Android Development] thejonesyboy:
So, with the most recent KANG 7.1 update, do LED notifications work at all? With update #16, LED notifications work fine, but the LEDs do not stay on when the phone is unlocked. I would like the LEDs to be lit while in use in the dark AND for notifications. Is that possible with atinm's 7.1 release?
[Captivate Android Development] HaiKaiDo:
Excuse me for poking my nose into this....but which rom on the captivate forums doesnt have giant warnings ALL OVER THEM about having to flash to I9000 bootloaders and how to return to stock. every single one of them IVE seen has this.

as for the whole "ye shall not use I9000 bootloaders" rhetoric, thats just stupid. Its all we have at the moment(as a temporary fix not a solution) and there are plenty of safety precautions inplace to make sure people dont go retardedly flashing things without knowing it (that is unless like most, they just dont read. they download and flash, which is their own fault). Also this business about "But, since the winzip developers want to play with GB too and don't know how to develop a working AOSP kernel"......why would there be a crap ton of AOSP roms out there...that would be stupid. CM7 fills the gap for the AOSP, and for the offcial side their are official source based roms. im sure the community of developers at XDA dont appreciate being called "winzip devs" for all the work they put into their releases.
[Captivate Android Development] PuffinNugz:
Nice long post full of misinformation. You obviously don't know how things work. No one should attempt to flash anything without reading as much as they can beforehand. If they don't take the time to learn about the risks, they get no sympathy from me or the dev, which is the way it should be.
[Captivate Android Development] bradasmith:
Can someone point me to the thread about CynogenMod and related topics?

:)
[Captivate Android Development] littlewierdo:
As I stated, I know enough for it to be dangerous. Again, point me to where the information is because other than fragments of information, there is very little to be had.

Im not asking for sympathy, Im asking for information.

Not intending to out anyone but here is a post made by someone who isnt 100% sure either. This should indicate that there is very little information about this.

Yep, my apologies. I didnt mean to derail the conversation. Just trying to understand how all of this works and not getting much help except from a few.

This was the wrong forum to get into this... *sigh*.
[Captivate Android Development] capsin6:
Build #13 is the last one on which these work. I've tried Hotspot personally on this build (13) and it works flawlessly. I have not tried it on the 7.1 build yet.
[Captivate Android Development] EnemyOfGlaDOS:
Wifi tethering is working on 7.1 :)

You should wiki it! Lots of helpful info. Also Google it. There is an overwhelming amount of CyanogenMod info at the tip of your fingers ;)
[Captivate Android Development] markdexter:
littleweirdo obviously likes the sound of his own....... typing fingers
[Captivate Android Development] Keland44:
i would like to know if it's possible to get the swype keyboard from firefly on this rom too i have the swype beta through the beta program but it's something about how it worked on firefly that really made me like it more then the swype beta
[Captivate Android Development] melbourne408:
I'm currently using swype atm

On 7.1, cheer up, the goodies are here.:D

You can customize the swype apk and that whole speel...if you want to, no reason for me here, I just prefer something that understands and can dictate with ease, my sloth terminology.
[Captivate Android Development] Keland44:
nice i think i'll wait till the nightlies are back up though
[Captivate Android Development] littlewierdo:
Did something happen or has there not been any updates since 5/25? I assume Nightly 16 is the latest isnt it??
[Captivate Android Development] Keland44:
lol yea based on what i read so far 16 was the last nightly the process that usually makes the nightlies is broken at the moment but close to being fixed

and i'm guessing 7.1 is considered a stable build? someone correct me if i'm wrong

i'll probably check 7.1 tonight depending on how bored I am.
[Captivate Android Development] melbourne408:
Nothing here is, and I'm sure has been furiously repeated, reiterated, "stable" rather, experimental,but the work put forth is astounding and an art and I'm loving it.
[Captivate Android Development] jbinc:
installed CM7 nightly #15

so, i just updated my CM7 to nightly build #15, and all went awesome, but now rather than simply seeing "ROGERS" on my lockscreen and under my notification drop down, I see "CAN Rogers Wireless Inc." It's kinda weird, not a big deal, but ugly none the less. Anyone know how I can get that back to just say "Rogers" or better yet, nothing at all?

Thanks !
[Captivate Android Development] oliverpeabody:
Mine did the same the right after I flash #16 but it went back to just plain Rogers after awhile II don't know what changed it but it did change

Sent from my SGH-I897
[Captivate Android Development] Keland44:
tru i'm loving it also have you seen the change log it's crazy it's a ton of stuff in there can't wait for the next update
[Captivate Android Development] littlewierdo:
7.1? Is this different from the #16 nightly build and if so, where do you get it from?

Wait, I got it...

I think...

http://sourceforge.net/projects/teamhacksung/files/captivate/
[Captivate Android Development] EnemyOfGlaDOS:
not much different..

http://sourceforge.net/projects/teamhacksung/files/captivate/
[Captivate Android Development] dhostetter:
http://sourceforge.net/projects/teamhacksung/files/captivate/
[Captivate Android Development] skatcat31:
actually this us the right forum to discuss the bl of roms, but the wrong thread. It us common knowledge that you should not flash a rom without three button ability and odin capability. With common know some devs do miss posting how to get back to stock. Many users even wail on people for it. But some people will always provide the information when asked.

Also this forum has stickies, including this one: http://xdaforums.com/showthread.php?t=884364

Information on flashing and returning to stock. If you don't read the stickies, don't ask for help is the rule here. This thread actually walks you through using odin as well.

Now to cm. has 7.1 been released through cwm or am I misunderstanding things?
[Captivate Android Development] jbinc:
I hope so, LOL.

Thx!
[Captivate Android Development] EnemyOfGlaDOS:
Not trying to answer for the CM team... 7.1 was built after the buildbot broke (the build bot is down, but sounds like it'll be fixed soon) Yes, you flash 7.1 from cwm as you will not find it in the ROMManager premium tab.

Basically anyone can make these builds(with a little bit of knowledge) and it is called a "kang". It is the latest update.
[Captivate Android Development] littlewierdo:
No 7.1 is not yet available thru CM, I had to download it from the above link and flash thru RM.

Now unless I am misunderstanding, before CM is 'stable', I think I read that they wanted to improve battery life more and it needs to read the sdcard (which it currently does not).
[Captivate Android Development] EnemyOfGlaDOS:
can be flashed from cwm as well;)
[Captivate Android Development] littlewierdo:
Well, yea, thats what I meant to say. The install failed thru RM but it rebooted into the recovery menu and I installed it from there.
[Captivate Android Development] zelendel:
Ok guys lets get back on topic here. Research is a big part of what goes on here. While the winzip devs/rom chefs as you call them (while not to far off really, I prefer rom Chef as that is close) work hard at what they do, they release it to be nice. They/We could also just keep them for our selfs and not share them with the public sense, the public doesnt seem to like to read and learn what they are doing. No matter what you do there is always a chance of bricking your device, Flashing roms are not for the every day Joe. It takes research, learning, and more research. As for not knowing how to make an AOSP kernel that is not true as I could very well Boot into Linux and compile one and build off it but to be honest I dont want to. I work with a base that is sure to have most of the things working out of the box. the CM team does great work on building from nothing. I take nothing away from that.

As for the warnings about the bootloaders, there is info all over XDA about it. Do we expect you to look for the info you want? YES we do. This is not a place to come to and flash your phone when this is your first time at the rodeo. I have seen far to many threads about "this is my first smart phone and I tried to flash XXXXX rom and now I am bricked" Well lets take a look as to why. Did you read up on what you were doing? No. Did you research your phone to know what can be done and cant be done? No. Did you sit down and spend some time reading the Wiki or the FAQ? No. Well what did you expect to happen then?

So from here on out if it is not about CM7 then lets leave the OT out of it ok.
[Captivate Android Development] Smasher816:
The changelog is back online :)
[Captivate Android Development] g1ddy:
No google account option

So I noticed that tethering was broken in update 16 and decided to flash back to 15...well now I don't have Google under Add Accounts in "Accounts & Sync".

The gmail + google apps are there but tell me to go add my account. I've even tried reinstalling the google apps for the heck of it with no luck.

So confused...

what do?
[Captivate Android Development] Emperor Jon:
And you're using swypebeta? and suggesting customization of that?

Or.... using a different swype and customizing that?

In which case, which one?

I just really liked the look and feel of the swype on firefly. If there is a way to customize it to fit CM7, I'd be more than willing to take the time to research how to do it..
[Captivate Android Development] Keland44:
that would be really coo

i've been using swiftkey beta it's actually pretty cool i'm slightly starting to prefer it over swype
[Captivate Android Development] goabunny:
I am on 7.1 and my screen goes blank most of the time after placing the call. I have to press the power button to get the screen back. I tried waving my hand over the proximity sensor to see if it is a sensor issue but it doesn't come back even then. When I press the power button, it comes back and it works fine from there.
[Captivate Android Development] TheEscapist:
Erm, what? unless you have a 3rd sdcard hidden somewhere in your phone, cm reads both sdcards perfectly fine.
[Captivate Android Development] littlewierdo:
Really? Because I have all my app backups (done with TB) on the SDCard and I have Audible audio books on the sdcard. TB doesnt see the sdcard when I manually click 'detect' for it to find the backup folder location and Audible does not see any audio books on the sdcard. As soon as I simply copied the books and app backups to the internal memory, voila, the phone sees it.

However, back on Cognition 4.51, with all my backed up apps, TB (when I tell it to manually detect the backup location) finds my backups on the sdcard. And Audible automatically sees the audiobooks on the sdcard.

So what am I doing wrong?

Oh, and Root Explorer, when I browse to SD-Ext shows it as being empty.
[Captivate Android Development] jhernand1102:
The sd card is now seen as emmc as for TB you can point it to emmc to your backup folder.
[Captivate Android Development] TheEscapist:
External sdcard is at /mnt/emmc, not SD-ext. If it doesn't show up under /mnt/emmc, then you're using GB bootloaders. If you're not using gingerbread bootloaders, than congrats, you found a bug. :p
[Captivate Android Development] kschumake83:
You need to look under emmc that is where your external sd is located not sd card or anything like that. If you have music on your external sd it will still show up and you can view all your files in root explorer. I'm not sure about titanium backup but there is probably a way to tell it where to look.
[Captivate Android Development] madamimadam:
My wife just bought me an iPad 2...and less than 48 hours later it was sold on eBay.

When she asked me why I sold it, I told her " I cant install CM7 on it, its useless to me"

Thank you to all the devs on this project, it keeps getting better and better with each nightly build, your hard work doesn't not go unappreciated or unnoticed.

Installing 7.1 now...

Edit* First boot I notice that the blue circle at boot animation doesnt lag anymore!
[Captivate Android Development] cumanzor:
Nothing personal but if I were your wife I'd be very pissed off. :p

Is anybody here able to flash any other kernel? I tried a couple of days ago with Le Kernel's latest nightly and lost signal. Restored to a previous nandroid backup, but it never got any signal back**. Had to go back to stock and redo everything. Anyone else with a similar story?

**I know this sounds unlikely, but I either did something stupid along the way or I somehow managed to screw up the phone.
[Captivate Android Development] EnemyOfGlaDOS:
Tk-glitch has a kernel working for the latest nightly as does the escapists kernel- did you try nightly #3. (i'm pretty sure anyway:p)

Also, if you have trouble with your modem, you can swap the modem.bin from the modem zip with the one from the 7.1kang update then reflash and that should give you back service. Or go to the CM7 modem stickies and try some of the modems from there.
[Captivate Android Development] madamimadam:
she is...

it appears that wifi hot spot is not working on 7.1 :confused:
[Captivate Android Development] EnemyOfGlaDOS:
is working for me.. did you try twice. For some reason doesn't work the first time, always have to select it twice :rolleyes:

*EDIT* ..just quickly tested and works. Only tried wifi tethering though.
[Captivate Android Development] sixstringsg:
I've found tk-glitch's kernel to be the best. And it now has a captivate thread instead of just i9000!

Sent from my CM7 powered captivate
[Captivate Android Development] atinm:
Just uploaded 06032011 Nightly:

http://sourceforge.net/projects/teamhacksung/files/captivate/

In addition to the changelog on the site linked in the OP, I also added some lower brightness settings from Nexus S that we used to have before. Other than that, if builtbots work tonight, this'll be a repeat. I'll merge the brightness changes soon so builtbots pick them up as well.
[Captivate Android Development] madamimadam:
just tried again...and...it works, just took longer to connect than im used to, which is probably more related to the crap service in my house than CM7
[Captivate Android Development] digitalbots:
need help

Ok my wife had me load this

http://ars.samsung.com/customer/usa...ID=2&PROD_SUB_ID=557&PROD_ID=558&AT_ID=368733

on to her phone and now she wants me to root it but when i tried to use the Rom Manager i only get the options to

reboot system now

reinstall packages

delete all user data

delete cache data

format internal sd-card

i have tried to use the option to install rom from sd card found with in the Rom Manager app and asked it to make a backup before clearing out the info. The phone reboot and give me only these 5 options. has anyone else see this before?
[Captivate Android Development] mnjm9b:
There should be a thanks button in the xda app.

So here...

(thanks) click...
[Captivate Android Development] EnemyOfGlaDOS:
There's a browser button.. which will open your phones browser to the thread.. where you can press thanks.. if you wanted to;)
[Captivate Android Development] rwells813:
I got assert failed, E: error with " cm7 update package.... showed up as I9000m. Installation aborted. I used the link provided. Just did it as i always usually would.

EDIT: LOL i DL wrong package. Usually first one is the one for me. Not this time. I should have paid more attention.

SGS SGH-I897 CM7 2.3.4 Using the CyanXDA App
[Captivate Android Development] markdexter:
im currently on #16, to flash the new one, i just wipe cach and dalvik and flash over?
[Captivate Android Development] ls377:
Don't download the "latest version" at the top. Get it from the group of downloads.
[Captivate Android Development] EnemyOfGlaDOS:
that'll do it.:)
[Captivate Android Development] littlewierdo:
Yea, this is bizarre, Audible doesnt see the sdcard, finally got TB to see if by browsing manually to it
[Captivate Android Development] :
Youre going to need to flash another kernal using Odin or SGS Kernal Flasher after you root it. There is something new in package signing so you cant just flashcwm through recovery anymore. I suggest flashing Speedmod. PM me and i can provide you with various links that will help you root and flash this so i dont fill up the CM7 forum.
[Captivate Android Development] veener79:
Is this update for the 7.1 version only?
[Captivate Android Development] XGX5309:
You need to use the ODIN one click to flash UCJF6. That will put you on 2E recovery. The package you installed has 3E recovery, and that's why you're having trouble flashing CWM from the recovery menu.
[Captivate Android Development] EnemyOfGlaDOS:
It's a nightly update. They are cumulative so... it doesn't matter what nightly you are on.
[Captivate Android Development] rwells813:
When i flashed 0603 ,rom manager was missing. Had to re download it from market. Kinda weird, first time thats happend to me. This phone is flying with that update btw

SGS SGH-I897 CM7 2.3.4 Using the CyanXDA App
[Captivate Android Development] veener79:
Thanks I wanted to confirm. It did not show up on Rom Manager for a update.
[Captivate Android Development] cumanzor:
Just tried the Cappy version. Same issue, no signal, no service after rebooting. I'll install the newest nightly, but I'm positive I'll have to return to stock to regain signal again. Same thing happened last time.

This is so ****ing strange. Please tell someone else is having this issue! :(
[Captivate Android Development] Tinyboss:
Is there a trick to sliding across the status bar to change brightness? I have the checkbox for it enabled, and I don't have auto-brightness on. I've gotten it to change the brightness maybe twice out of 50 or so attempts.

I've been trying the old stock way of touching the status bar until the pull-down thing shows, then sliding left or right.