yashsingh1/xdaforums huggingface dataset:
[Captivate Android Development] chasesavestheday:
i only installed the beta2.2 zip and everything has worked fine. all was included. not sure what you were suppose to do with the root back or odin. mine was already rooted. what happens if we need to flash to stock since we would have to change back to a 2.1 kernel, can we just re flash with the packed odin to a fresh 2.2?
[Captivate Android Development] revjwb32:
I think so, it is more like a real web experience with flash 10.1 mine is not jerky as some has stated.

and just a side note att just sent me a text saying i was getting an update LOL im already on 2.2, it would be nice if it was froyo but im sure its the last update.
[Captivate Android Development] vikdmon:
I don't remember seeing a camera update firmware in Android 2.1. I just noticed it in Froyo under camera settings. Apparently if you click on it, and ask to check or download a firmware it prompts you with a warning that additional fee will be charged.

What is that about!!!
[Captivate Android Development] fatbas202:
I've searched this thread and found nothing, so please forgive me if this has been asked before.

I'm running Cognition 2.2 BETA (the first one). I'm seeing that my battery is dropping like crazy. After 2 hours I've used 30%. GPS off, Wifi off, same setup with 2.1 got me about 25 hours on one charge.

So I'm looking at "Battery Use" in Settings to figure out what the heck is drinking all of the juice and it appears that things like applications an GPS no longer show up in there. Is that wrong or did I get a bad flash?

Thanks!
[Captivate Android Development] ranjo65:
If you want to flash back to stock you'll have to download Odin3 One-click that comes with JF6 bundled in.
[Captivate Android Development] biggem001:
i would reccomend reflashing. make sure its on a FULL charge (left on still after 100% for a few hours just in case)

this happened to me on other builds and the battery monitor became incredibly innaccurate.
[Captivate Android Development] phohammer:
Very cool! It seems to not work with Google voice tho...
[Captivate Android Development] fatbas202:
That's what I thought. I know that WinMo ROMs needed time to 'learn' how the battery drained, but it makes sense the ROM assumes it's at 100% when the OS first boots.

Is Battery Use on your 2.2 install showing apps? I only get Cell Standby, Display, and Phone Idle.
[Captivate Android Development] yhbrandon:
I've been using this ROM all day and it is holding up just fine. However, i have noticed two little bugs.

When you hop on a call and then end the call. The status bar freezes and wont work until you reboot.

Also, when you reboot, it turns off debugging mode. I didnt know if this is a bug on froyo or a built in feature.

Its still great, and easy to live with those problems.
[Captivate Android Development] gocats7:
NOLed worked in 2.1 with google voice. I cannot get it to work in 2.2 with google voice though for some reason as well.
[Captivate Android Development] Bowsa2511:
Edit: nevermind
[Captivate Android Development] schuob:
Thanks man that helped
[Captivate Android Development] old Tech:
Any way to prevent the Cog email client from forcing PIN on lock screen when using exchange mail? Please please please.
[Captivate Android Development] sinichi21:
whats vodoo voice? sorry for the noobness
[Captivate Android Development] fosdos4790:
Can someone post the new wallpaper, I accidentally lost it. Thanks.
[Captivate Android Development] skinien:
A sexy (female) robot voice tells you the progress of voodoo.
[Captivate Android Development] sinichi21:
so basicaly its just a talking bot that says the progress of vodoo?
[Captivate Android Development] JPxM0Dz:
I second that!

Thanks in advance ;)
[Captivate Android Development] KewlRobD:
Select Reinstall Packages and the ClockworkMod Recovery screen should load. If not select Reinstall Packages one more time. That should do it.
[Captivate Android Development] jdubdieslo:
Thanks. so when i select reinstall packages is it reinstalling the clockwork recovery or just some how tricking the phone to go to the mod recovery?
[Captivate Android Development] silverslotcar:
What steps did you use flashing from beta 7 to beta 9?? The clockwork way? Did you do a reset or master clear before installing the zip from sd?? Plz elaborate steps for a clean flash from beta 7 to 9 using cw.
[Captivate Android Development] KewlRobD:
I am not really all that technical when it comes this stuff but I know the first time you sometimes need to do it twice. After that you will always enter the regular recovery mode first and after selecting Reinstall Packages you will get the ClockworkMod Recovery screen. As long as the update.zip file on your internal SD card is the ClockworkMod one.
[Captivate Android Development] cebb:
So far beta 9 on my cappy is running well with voodoo....never had a lag fix of any sort on my cappy, I'm impressed with the quicker response of my phone now...good battery life and somewhat improved gps..only thing I've noticed is that when I select reboot it takes a little longer than usual to power back on.

Flashed via odin from beta 6 without going back to stock or master clearing with no problems.

Good job on this beta version.
[Captivate Android Development] silverslotcar:
Yea bcuz reinstall packages just unzips whatever update.zip is on your internal sd. So keep cw update on your sd to always be able to go into that recovery.
[Captivate Android Development] gr4v3r:
I tried installing 2.2beta 9 using rom manager, everything seemed to go well but after itt was finished my phone keeps restarting in system recovery... I can't turn the phone on. Any advice?
[Captivate Android Development] Jirv311:
I'm wondering if this isn't a setting your Exchange Admin has put in place? I'm using the Cog email client with an Exchange account and do not get this.
[Captivate Android Development] jdubdieslo:
Thanks. Makes sense.
[Captivate Android Development] jdubdieslo:
So what needs to be done to get a2sd extra on this Rom?
[Captivate Android Development] ratflinger:
Moved from Beta6 to Beta9 tonight. Used cwm - blue tooth came back, but voodoo didn't. Even trade, I'm not as app heavy as most.
[Captivate Android Development] Pirateghost:
Install it from the market

Sent from my AOSP Captivate
[Captivate Android Development] gr4v3r:
The way I installed it was using Rom manager, pointing to Cognition2.2BETA9.zip then flashed it. Is there a step I'm missing that would cause this issue?
[Captivate Android Development] jdubdieslo:
I'm referring to apps 2 my partitioned SD ext 2/3/4. Does this Rom support it? If so is there thread some one can poiny me too?
[Captivate Android Development] Jirv311:
Also just to reiterate for those that may have missed it. You should flash when you have 100% battery. I did this today and so far, best battery life out of this phone yet. 8 hours unplugged and I'm only down to 60% battery. And I've been using it more than average.

Very nice work DG!
[Captivate Android Development] Pirateghost:
App2sd?

Its an app in the market. Works for me.

Sent from my AOSP Captivate
[Captivate Android Development] drancid:
Use Odin to flash beta9.

Had same problem with Tom manager but I reflashed with Odin everything works great!!

Love beta9 so far!!!
[Captivate Android Development] EsotericPunk:
Thought I'd share my B9 experience so far...

I grabbed CWM B9 late last night and flashed. After completion, I had no splash screen and no voodoo (sad face). I also noticed that, for some reason or another, I couldn't get ODIN to master clear my phone. It would get all the way through to a reboot then the factory reset would FC and no files would be removed.

To remedy this, I rebooted to recovery and used recovery mode to clear user data and cache. Once these were completed I tried ODIN master clear again and achieved success.

With the ROM cleared out, I flashed the ODIN version of B9. Worked flawlessly. Splash screen shows up now (nice work reefermattness!) and all my base are belong to voodoo once again. Not sure what happened with CWM but, from reading through the thread, it seems I was not alone in my troubles.

Hope my comments help, I'll post up any issues if I find them. Great work as always DG; you are the savior of the Captivate IMO.
[Captivate Android Development] mattbeau:
So my experience so far:

Much faster lock on GPS

Android. Kb still no haptic feed back seems lagier then beta 7. Easy fix for android ID NP for me. Get fc when I change wallpaper in launcher pro. Get quit a.few fc. Randomly. Not as stable as other versions. Lag fix never seems to be a priority for me I would prefer rock solid stability and full functionality vs speed and added features. Otherwise great work DG expect another donation in a week or so
[Captivate Android Development] saoirse_go_deo:
What exactly do you use Bluetooth with? I have been trying to connect to my Dell laptop ever since using Cognition ROMs and I never could get recognized. And yes, I made sure the phone's visibility was on. Just wondering if there's a known issue with Bluetooth capability.
[Captivate Android Development] Jirv311:
I just noticed that my "power button menu" to bring up reboot etc no longer works. I hold the power button for 2 seconds and I get a quick vibe and then a few seconds another few quick vibes, like a force close feel, and then my phone reboots to the cog boot logo. Is this menu handled by framework-res.apk? If so, can someone post up the original framework-res.apk for me because I may or may not have but definitely did replace it for the circle battery mod. :)
[Captivate Android Development] schuob:
I had the same problem with using CWR from stock 2.1 but I ended up using ODIN and it worked fine. I actually dont like the new boot animation- anyone know how to get the default Samsung S animation back?
[Captivate Android Development] rickzotz:
YES! Thanks for attempting this.

My phone's symptoms were exactly the same after upgrading with RM. I followed your steps, and I'm back in business with the Voodoo directory and the bootup spash screen. Restoring now with TB. Looks good so far.
[Captivate Android Development] zielins1:
Can anyone direct me to a resource for disabling the default_wallpaper.jpg thing? I'd rather be able to choose my wallpaper.
[Captivate Android Development] sinichi21:
guys how do i get my 3 button to download mode? ive been trying to press it but all im getting at is the e2 recovery mode btw im running cog 2.2 beta 8.1
[Captivate Android Development] opcow:
While holding vol up and down, plug in the usb cable.
[Captivate Android Development] zielins1:
To clarify, any wallpaper other than a Live wallpaper that I switch to in both Launcher Pro and TW won't replace the default Cognition wallpaper. Just was on the chat, apparently this isn't a problem for many others. Perhaps a system setting I wasn't supposed to restore with TiBu.
[Captivate Android Development] tkienzle:
Im using 2.2 beta4 and i want to upgrade to the new ver. Do i have to us odin? I run linux and with no plans to install windows and it looks like odin only runs in windows could someone that has done this in linux point me in the right diretion please. Thank you..
[Captivate Android Development] delutedsoul23:
ok guys im a noob...i just switched from and aria to the captivate...im rooted and i have clockworkmod installed but when ever i try and flash this rom,it keeps going to the world phone screen twice then back to clock work any ideas
[Captivate Android Development] opcow:
You can try clearing cache and user data from recovery and then flash with clockwork or use heimdall.
[Captivate Android Development] EsotericPunk:
It's gonna have to be Heimdall I think. If I recall correctly, B4 doesn't support Clockwork.

Edit: Yep, just checked the changelog and Clockwork wasn't on Cog until B6.
[Captivate Android Development] tkienzle:
You are right where could i get heimdall? I did a search but hard to filter all the crap on a cell phone... Thanks for the help guys...
[Captivate Android Development] waghoba:
Odin is the answer! Use Odin to flash. Read FAQS from cognition page.
[Captivate Android Development] waghoba:
Again read the FAQ page. DG has posted links to everything there!
[Captivate Android Development] sinichi21:
just flash cog beta 9 everything is awsome :D although anyone can tell me where is the cog android background wallpaper? I want it back =(
[Captivate Android Development] Lee1733:
Personally I'm not having any force closes as was mentioned earlier, and I'm also using launcher pro. Sounds like you may need to try flashing again IMO if you are getting a lot of them. The reboot option also works fine for me and I appreciate it being there.

The only new bug I've found while running this all day is that the "lock screen sound" goes off even when I don't press the power button to lock it; for example, if I'm on a call for a few seconds so the screen turns off, it will make the lock sound.. not very pleasant with the speaker so close to my ear, lol. Also the lack of a timer sound like I mentioned earlier. Other than those, great rom! My battery life has been noticeably better than 2.2b7 and earlier.

Sent from my Samsung Captivate.

Current rom: Cognition 2.2b9
[Captivate Android Development] tkienzle:
I found it doing a google search thanks again guys and i do apologise waghoba for the clutter in you thread...
[Captivate Android Development] opcow:
http://www.glassechidna.com.au/products/heimdall/

I built it on my Ubuntu server and the libusb libraries in the repositories were too old so I had to get them from here and here.

Instructions for building and using heimdall are here.
[Captivate Android Development] a3plew:
I noticed the lock screen lock sound going off during calls since beta 7...
[Captivate Android Development] Eibon:
Considering flashing this soon.

I have one question though, I'm currently using cog 2.1.6 (with hsupa) and I am planning on doing a master clear/reset/stock reflash/whatever it is called in odin before flashing cog b9 (this through odin afterwards).

Do I need to disable the lagfix before I flash to stock through odin, or will odin take care of removing voodoo for me
[Captivate Android Development] dayv:
If hiemdall does not work out, you can try virtual box. I have successfully flashed with odin in a win xp virtual box on an ubuntu linux machine. The version of virtual box in the repos did not work but the latest version directly from sun's vb web site worked

http://www.virtualbox.org/
[Captivate Android Development] dayv:
I have successfully flashed once without disabling voodoo, but it may not be a good idea as if you get part way through the flash and it gets interrupted without properly reformatting the data partition you could end up having a hard time getting your internal drive mounted correctly - this could be a big head ache. I would suggest disabling the lag fix to be safe.
[Captivate Android Development] smokestack76:
Just snooping through the thread is unreal. How can anyone want to argue with how to flash after looking through here? Im not sure how many of you are from the WinMo world but if you are you will remember all the NK.exe hacks and what not. All the test builds of 6.5. You always flash stock first because stuff hangs around in the system. Stock wipes most of that much better than another custom ROM. Android is the same. Just browse this thread for how different it is for everyone.

I always do a master clear. Format my internal SD. Boot recovery and wipe cache and data.I Never backup because thats a quick way to drag issues from ROM to ROM. And NEVER leave your SIM in the phone!!! Last thing you want to do is kill your SIM or have it pulling data from the radio while you are trying to flash one. The fact anyone argues that shows just how new most of you are. Thats how i flash and dont have almost any of the issues alot are having. PLUS that way everyone is on the same page and solving issues is much easier. I would do away with clockwork and have only 1 way to flash as well to help solve issues but thats just me. If any of you think the whole remove SIM is new go look at other phone threads. Point being i always follow my steps and never have issues.

And sure i could just flash and flash and maybe get lucky. But you will eventually start to get issues without a wipe. You wouldnt use the restroom and not wipe would you?
[Captivate Android Development] sinichi21:
anyone know how to get the default wallpaper back?
[Captivate Android Development] ranjo65:
Maybe we're talking about different things, or perhaps I'm just thick-headed, but it seems to me that the entire purpose of a System Restore is to undo any changes that have been made and to revert back to the default settings of whatever ROM is being run. The likelihood of carrying over files and or settings from ROM A to ROM B seems greater to me if you DO NOT perform some sort of reset.

I know that when I flash back to stock JF6 in prep. for moving to a new ROM, the old files are still in evidence on the internal SD until I do a Master Clear in Odin (which throws the phone into Factory Reset). After that all the old files are gone, I have a clean slate to start over with.

I'm not trying to be argumentative, it's just that what you're saying makes no sense to me.
[Captivate Android Development] ranjo65:
+1 Exactly!
[Captivate Android Development] opcow:
I've seen a couple of examples in the last 30 or so pages where people flashed to stock and still had problems is just one reason. Another, the distinct possibility of a brickage. Everytime you flash there is the possibilty of a failure. If you're phone has the permanent button activated download mode then fine; you have nothing to lose but a little time.

Android and WinMo are not the same. The fact that results are so varied just goes to show that there is no clear answer. Let me ask you: what happens when you flash with odin3? Does the procedure include a master clear or the equivalent? I don't know the answer. Do you? Anyone? Do you or anyone else here know for certain that the one click flash to stock cleans the system any better than directly flashing froyo with odin?

I think it's worth questioning the idea that going back to stock is safer, especially in light of the fact that flashing to stock is not risk-free.

Restoring apps when the OS version hasn't changed is not that risky. Whatever the risk, the benefit out-weighs it, in my subjective opinion. Restoring with TiBu is a big enough of a pain as it is, downloading everything over from the market is something I'll only do as a last resort. Being careful is fine, but you can take it too far. What I would recommend is, if you are going froyo-froyo or eclair-eclair then restore user apps+data, otherwise restore user apps, but never restore system apps and data.

With regard to pulling the sim before flashing, fine. It's conceivable that it could cause a problem if the card crashes or is otherwise in a wonky state when the system reboots. I'm still extremely skeptical that it would cause ongoing battery drain issues, but there's not much of a downside to pulling it.

And yet I can say the same thing about how I flash. Not that I don't have problems, but I've only had problems related to flashing when I used CWM (and even then I don't know if CWM or something to in the update package is to blame). Nonetheless, I don't advise people to never use CWM and I'm sure I'll use it in the future. People should just be advised of the possibility of issues.

It's a noble idea to have a single procedure to cut down on the variables, but I would't think about forcing people to go back to stock unless I had very good reason to believe it was necessary. Your WinMo experience doesn't convince me.

Unless you have some evidence to back up you premise that flashing a froyo rom using odin leaves more/any junk in the system that flashing with odin one-click and then odin doesn't, I'll call that conjecture. You also make a false analogy when you presume that flashing with odin3 isn't wiping anything.

Do it your way. I'm not going to tell you you're being stupid for going all the way back to stock. But don't tell those of us who argue that the benefit may not be worth the risk (certainly for those who have a brickable phone) that we are just being silly n00bs.
[Captivate Android Development] mcord11758:
Did you have a lag fix installed

Captivate

Cog 2.2
[Captivate Android Development] ranova:
installing from market is very finicky. cleared it's cache and it still gets stuck in preparing to download limbo.
[Captivate Android Development] Demented71:
Since Cognition 2.2 beta 9 supports bootanimation.zip files, I started a thread in Captivate Themes and Apps:

Captivate Boot Animations!

It has some animations I have made and tested on my phone, and hopefully others will share theirs.

Check it out!
[Captivate Android Development] evanstapler:
Got to mess around with beta 9 last night before I went to bed, and it's awesome. Thanks for all the hard work, it's appreciated!
[Captivate Android Development] keitht:
Try this.. worked for someone else:

http://xdaforums.com/showpost.php?p=8765392&postcount=5057
[Captivate Android Development] sparker366:
If he is on Cog b9 or Cog b8.1 then he can just hold the power button and then reboot into recovery. If he is on an older rom he can use rom manager if installed and reboot in to clockwork which also has that option. He can also use adb to reboot into recovery.

Some people, myself included have issues with getting in to recovery using the buttons. Best to offer alternatives if that fails.
[Captivate Android Development] Coldheat1906:
Help SIM not recognized!!!

Never mind. figured out how to fix it.
[Captivate Android Development] ratflinger:
Blueant Q2 ear piece. Had to re-pair the devices
[Captivate Android Development] ewingr:
Well, I find the same thing. I'm on 8.1. So I put the original framework-res.apk back and now wit works right. Which leaves me with a question: I noticed otheres discussing how they install lthe battery circle: have those methods worked w/o this problem? Or is installing the battery circlel stuff a problem for this rom?
[Captivate Android Development] mcord11758:
On 8.1 installed minumalistic mod with bat circle. Power button works with no issues

Captivate

Cog 2.2
[Captivate Android Development] sschrupp:
kekeke, thanks, first laugh of the morning!
[Captivate Android Development] pyrplhaze:
....MMS not working for me.

I can send one to myself, but when I try and send one to other people I get "Error in Server Response"

Not sure if that's something on my end or the ROM...assuming it's the rom, cause I was able to do it just fine before. Tried sending one to folks on verizon and one to others on ATT and sending it to myself is the only way it worked :(

like I said before...flashed via CWM, sim/ext SD removed, all went well. Everything else so far has gone swimmingly except this
[Captivate Android Development] ewingr:
WIFI...

I have found that WIFI is disconnecting and reconnecting. I'm on 8.1. I recall others mentioning WIFI issues, I think on 8.0, and previous ROMS.

They are short disconnects. I notice them because I have a Tasker Profile that announces WIFI Lost when I lose connection to my SSID; when I lose that connection it forwards the phone to VM. But if the connection lost less thatn 20 seconds it does not forward it.

Anyone elsle seeing this, and is it better on b9?
[Captivate Android Development] mindfrost82:
What ROM did you have before?

With Froyo, you need to change your phone numbers to 1-999-999-9999 format, otherwise you'll get that error. Take out any (). I haven't had a single problem sending pics after changing all my phone numbers to that format.
[Captivate Android Development] pyrplhaze:
upgraded from beta7. never had any issues with formatting before, but I'll give it a shot. hopefully that'll fix the problem. I don't use MMS much, but when I do need it, I need it, ya know?

**edit**

just tried mms'ing my sis. tried before, no luck. just now, changed the format, and BAM! we are good!

thanks for the help Mindfrost. guess now I've gotta have a sit-down with the phone and change all my damn numbers :(
[Captivate Android Development] tegots:
how do i change the number format ?! that might fix my problem too