yashsingh1/xdaforums huggingface dataset:
[Captivate Android Development] TheEscapist:
Yeah, it was Maps/new Market. And yes, I installed it as well. Everything worked after (relatively speaking), so no issues.

Also, anyone else have issues with it charging with the screen off? I left mine on the charger when I went to bed, and it crashed (locked up, colored bands everywhere). Scared the **** out of me cause my room lit up with color right as I was falling asleep.:rolleyes: It's not a huge deal as I'm used to having "Stay Awake" checked off in Applications(Damn charge sleep death:mad:), but still an issue.
[Captivate Android Development] flashman2002:
I can't comment because I turned my phone off because of reboots. My biggest issue is keyboard lag. Input is so slow to register at times. Otherwise stuff has worked well for me.

sent from my Nexus SGS Captivate.
[Captivate Android Development] kdwolf85:
Turns out it's not just auto rotate that's broken. Its the whole accelerometer. Tested with Google skymap.

Sent from my Nexus SGS
[Captivate Android Development] inneyeseakay:
Yeah... I noticed this when trying to use shootme to take screenshots.

On a good note; bluetooth works quite nicely, making this my daily-use ROM until I see something that changes my mind. I rarely use my camera and never use WiFi, so this actually works for me. Plus: I love the screen off animation! :cool: LOL
[Captivate Android Development] TheEscapist:
Are you getting constant reboots with wifi off? I was, which is why I can't use it yet.
[Captivate Android Development] vbhines:
No, I am not. No reboot issues at all, here. What kernel release are all of you using? I'm still on V5.

I can't comment on reboots with wifi on. I used it to install my apps last night but otherwise always keep it turned off on any ROM that I run.

Comment: I'm still grasping that I have AOSP on my Captivate :-D I finally was able to turn off ALL calendar reminders.
[Captivate Android Development] TheEscapist:
V5. I never went up to v6. I was getting near constant reboots this morning with wifi off, and one or two with it one, this morning, as well as the charge crash (which may have been wifi related). I'll try doing v6, then downgrading to v5.
[Captivate Android Development] vbhines:
Ok, but your situation strikes me as odd. I've never gone to V6 because I read of button mapping issues (that I haven't heard of again today). I just stayed on V5 and rooted manually.

If the crashes happen relatively recently, have you tried running logcat under ADB to watch what's triggering it? It might be helpful to find out to prevent the same thing from happening to others.

Also, I don't see why it should matter since your wifi is off, but I also disabled wifi sleep completely before I turned wifi off.
[Captivate Android Development] inneyeseakay:
No... I haven't turned WIFI on yet (I really never use it, unlimited data FTW)... but my phone hasn't reboot on my yet ::knock on wood::

I even charged it all night last night without any charge death.

I flashed v6, installed SU, then flashed v5 reoriented...
[Captivate Android Development] nbs11:
If I am correct, the list of things currently NOT working are:

GPS and Accelerometer
[Captivate Android Development] vbhines:
Yes - I do believe it's sensor aiding in general.

Has anyone noticed a decreased tolerance in touch radius / accuracy? I can't tell if it's just in my head, but it seems as though I have need to try harder to press buttons smack dab in their center. It's not a complaint, of course - I just don't want to start tracking down the cause if I'm imagining it.
[Captivate Android Development] bames:
yes most notable in the keyboard for me...particularly the buttons towards the bottom (actually right of screen due to my phone forcing landscape on the keyboard)
[Captivate Android Development] vbhines:
That's interesting it's more prominent there as that's where the Nexus S' screen is the most prominently curved. I'm sure it's a coincidence, but it does make you wonder if it's fisheyed, for lack of a better term.
[Captivate Android Development] RMGeren:
I had no issues with the keyboard, but I couldn't get an ip address through my router. I got 3g for about 30 seconds, But not long enough to sign in to my google account.

The orientation issue is pretty random. I got several reboots, and sometimes the screen would stay in portrait, but would quickly shift.
[Captivate Android Development] inneyeseakay:
I did notice this at first boot when trying to setup my gmail account. I couldn't hit the "Next" button for the life of me.
[Captivate Android Development] plasticdarlow:
Thanks! Wasn't looking at my phone when the prompt came up! :D
[Captivate Android Development] vbhines:
The same exact thing happened to me - I sat there for about thirty minutes before I noticed my screen light up with the prompt and remembered that I hadn't used su in adb since my last flash.

I wasn't having any issues with wifi or reboots, but I made some changes in build.prop via Root Explorer (polling interval from 15 to 90, added channel limit to 14 from blank) and I also increased the dalvik vm heap size from 32m to 48m.

I actually couldn't find the jit option, disabled or enabled, in build.prop, but confirmed via terminal that is is (predictably) enabled already.
[Captivate Android Development] vbhines:
In case anyone was curious, updating the build.prop fingerprint to:

ro.build.fingerprint=verizon_wwe/inc/inc/inc:2.2/FRF91/231334:user/release-keys

and rebooting/clearing market data/cache gave me back my protected apps without any issues so far.
[Captivate Android Development] h8rift:
I am as well. According to supercurio, this is part of the WiFi sleep issue. Question....since you flashed this kernel on your phone...did you ever turn WiFi on? I know you have it off now....but did you ever turn it on? I think that may be the reason we experience it and others do not.

Thanks,

h8
[Captivate Android Development] inneyeseakay:
I ran the marketfix from SGStools to get mine back... worked fine, no FC's or anything afterwards.
[Captivate Android Development] vbhines:
Yes, I turned it on - before I started messing with build.prop, too. As soon as I enabled it, I completely disabled WiFi sleep, though. As others have mentioned, the dev team is aware of issues with WiFi sleeping. I noticed, for instance, that even though I had WiFi sleeping disabled, it slept anyway when the screen was off.

But I've turned it off and on several times the last two days and have had no rebooting issues.

EDIT:

Additional settings I'm running, in case it helps bug track.

* Network Notification OFF

* Linked to WPA2 network
[Captivate Android Development] h8rift:
sweet. I just set that option as well. In my playing, I lost 3G data...so I'm playing with APNs to get it back right now. Looks like this ROM is gonna be a daily driver for me for awhile :P.

Thanks!

-h8
[Captivate Android Development] h8rift:
Also...which modem are you using? I had it running on jk3 earlier...
[Captivate Android Development] inneyeseakay:
I'm on JK4
[Captivate Android Development] vbhines:
Yeah, I haven't quite figured that out yet. I've got APNs set to automatic, but every time I reboot I have no data UNTIL I enable WiFi - then my signal bars turn from white to green and I can disable WiFi - mobile data stay connected. I had data switch off after some minor changes, the same process restored it.

As far as the touch sensitivity, I installed the HTC_IME_MOD keyboard, which happens to have much larger keys (at least on the one that I themed)...I have to press smack dab in the middle of the letters, otherwise it doesn't register. Pressing towards an edge of a letter is like I'm not pressing anything at all.

I imagine the properties for touch tolerance are built within the kernel. I've settled on this as my daily driver as well.

Hopefully my trials, errors and comments are helpful to others and not simply noise in the thread :)

EDIT: JK4
[Captivate Android Development] inneyeseakay:
I seem to be having better luck with swype... but I know some people don't like it.
[Captivate Android Development] bblaze1874:
Ive been having what i thought was the wifi sleep issue as well. Tried disabling wifi sleep, doing a fresh install and never enabling wifi, but nothing worked. Phone would reboot every other time i locked it, as well as every 3-4 minutes at random. Finally went into settings and disabled all animations. Works perfect now. Seems the fancy screen off animation was giving me problems.....hope this helps someone.

Keep up the amazing work devs:D

Update: went in and enabled wifi, still working perfect...definitely something with animations was rebooting my phone
[Captivate Android Development] bambamboom:
im gonna come off as a total **** head here, i know.

i've been reading the directions OVER AND OVER again, trying to get the balls to do it. It seems simple enough, but for some reason, thoughts of effing it up keeps creeping in my head. I mean, I REALLY want to do this though.

**** head part, does anybody have aim or something that they could walk me through step by step...? i know, a person like me shouldnt really be doing stuff like this but a part of me is dying to get into this.

any help? :/ i could pm my SN or google talk if someone has some time to kill to help a noob out.

edit:

to show how much of a chicken iam when it comes to this lol, im running stock 2.1 with only the "unleash the beast" as a mod.
[Captivate Android Development] flashman2002:
Oh my god, WTF is wrong with you!?!?!? Just do it.

JK, sure PM me I flashed it. It is really easy. I have Gtalk as well. But don't be scared. If you have your 3 button combo working, please make sure it is. You would be able to get into download mode to reflash back from 2.3
[Captivate Android Development] accinfo:
Can you NOT PM him? Reply him HERE, so other people who are having problems, idiots like me can learn something. Thanks.
[Captivate Android Development] flashman2002:
Dude, just having a little fun. And I am willing to help the guy so just calm down a quick second. Nothing wrong with a little humor now and again, especially since he called himself out ;) No harm no foul.
[Captivate Android Development] biggem001:
have you tried wiping to stock and reflashing. to be honest, not all flashes are the same. i can flash the exact same rom 3 times and quite possibly get 3 different bugs. i know with the CM i have, GPS didn't work until i wiped to stock and reflashed about 2 more times then magically, GPS worked.

-edit-

also, try different modems. i've noticed different abilities with different modems across roms. i dont know why, but some modems have effects on the phone quite a bit. whether it be GPS function, wifi and even random reboots. I just switched to the new modem (the telus one i think??) whatever the newest one is, and i've completely lost random reboots, when i would have them quite often.
[Captivate Android Development] SiL3nTKiLL:
cant wait for this to be fully done!!!
[Captivate Android Development] biggem001:
cant stress this one enough. If you have a 3 button combo working, you are perfectly fine. beleive me, i've put some messed up roms on my captivate, but i 3-buttoned out of it every time. just make sure you can get in to download and you are golden. if not, i would suggest not even touching it.
[Captivate Android Development] silverslotcar:
Or get a jig. :-)
[Captivate Android Development] TheShamsMan:
Hahahah. Ahh... I remember those days.

I still get a little adrenaline going some times when flashing.
[Captivate Android Development] lrs421:
Word. I almost bought a nexus one but the 3 button combo (rescue) has me afraid to leave the captivate. I too have flashed some suspect roms on my phone and odined my self back to safety.
[Captivate Android Development] TheEscapist:
I'll try this, re-flashing v5 now. I have the exact same problem as you had, turning off screen = reboot.

EDIT: Still got the issue when i set wifi sleep to screen off. With it set to never, it seemed okay. How ever, I lost the crt animation, and that's the main reason why I want this rom. :rolleyes:
[Captivate Android Development] kennethpenn:
Updated my detailed guide to v6 to account for the new features. :)

Still unstable... I get constant reboots due to wifi as well. Progress is happening, though! Big TY to all the devs.
[Captivate Android Development] opcow:
2 buttons plus plugging in USB for download mode works fine. 3-button combo to recovery fails. I've tried a couple of dozen times, but could never get into recovery (not a huge problem since changing kernels with odin works fine, but it would have been nice to be able to swap kernels sans PC). After flashing back to a setiron kernel the recovery combo works again.
[Captivate Android Development] opcow:
The link says guide, but the target is a kernel.
[Captivate Android Development] ademejia:
has anyone done the system update?
[Captivate Android Development] keredini:
Can't wait to get home and flash this...stupid holiday parties ;)

Sent from my brain to your screen over teh interwebz
[Captivate Android Development] bryman27:
recovery mode doesn't work for anybody yet, related to the kernel

I have, I don't think it is actually applied, but the update notification goes away so that's good
[Captivate Android Development] keitht:
Not using this yet but SC said here or in the other thread that it will download but not apply the update.
[Captivate Android Development] danquirk2000:
Is there a specific modem that I need to have in order for data/voice to work properly? If so, could someone please tell me what I would be required to flash?
[Captivate Android Development] vbhines:
Since there seem to be some of us with reboot issues and some of us without, even though we seem to be running similar setups, I still think it would be very helpful for bug tracking if someone with issues would post a logcat at reboot/crash. I think this would be especially useful from anyone that reports this issue being related to screen animations, because that could tie in to a lot of other potential fixes.
[Captivate Android Development] vbhines:
Supposedly any 2.2 modem should work fine - I've had no issues at all with JK4.
[Captivate Android Development] danquirk2000:
Will the kernel posted in the I9000 forums work correctly with our captivates? Or is there one designed specifically for our devices?
[Captivate Android Development] ademejia:
look a few pages back look for the one xcal made.
[Captivate Android Development] danquirk2000:
I tried that one and I could not get gingerbread to boot. I had a successful boot when I used the kernel from I9000 but data/voice would not work.

Edit**

Has anyone attempted going to gingerbread from cognition 2.2B8?
[Captivate Android Development] ademejia:
thats the only one that will work properly with the captivate, try flashing the supercurio then flash over it with xcals. if that fails just go back to command prompt and start over.
[Captivate Android Development] danquirk2000:
Has anyone else had issues with screen orientation when opening apps using xcals kernel?
[Captivate Android Development] bryman27:
the accelerometer is broken in all builds so far
[Captivate Android Development] ademejia:
My screen orientation fine v5
[Captivate Android Development] bryman27:
Really? sure you don't have auto-rotation disabled
[Captivate Android Development] plasticdarlow:
I am runing v6 with xcals kernel [posted on pg 38] wifi and data are working, but i cannot connect to the internet via the browser. Anyone else experiencing this?

Edit: Works via wifi, not data connection.
[Captivate Android Development] ademejia:
i have it checked on auto orientation , the only time the orientation was off is when i was fiddling with my sim and battery to get a connection. i did a few reboots and it was fine. im using jl3 modem and i upgraded from cyanogenmod nightly build. right now gingerbread i been using over 8hrs on my work day no problems for me except dont fiddle with your battery cause it made me lose voice connection. besided that everything works wifi,data,voice
[Captivate Android Development] bryman27:
interesting, I guess I'll be installing the cyanogenmod nightly and jl3 modem this weekend
[Captivate Android Development] metalgeek:
Can't wait for a full stable ROM!
[Captivate Android Development] mrbloog:
I finally got it installed, but instead of flashing the kernels or modems your all talking about. I flashed the one from the guide, but since this isn't official. I've tried with reboot recovery in terminal on Android 2.3 and it always fails even reboot download. And my computer isn't picking up the phone anymore, and I installed the Nexus S drivers.

So, if any could help me it would be appreciated. I am trying to get to download to flash back to stock, or recovery to flash back to preception.
[Captivate Android Development] Khaos-Rage:
Did and data works fine, but no voice.

Take out batt, sim, sdcard. Open odin then put batt back in and hold both vol up and vol down, then plug in usb cable and it should go into download mode and be recognized by odin.
[Captivate Android Development] ademejia:
you dont necessarily have to install cyanogenmod to get this to work. just follow the guide from i9000 forums or the guide from here that kenneth made on page 1.
[Captivate Android Development] Min1123:
WebM!

I am using the XCal kernel mentioned earlier with the system dump setup as on the first page flashed with Heimdall. Asides from the issues noted previously, voice, data and wifi play nice. Most importantly for me is the WebM support works. Camera App is broken currently, so I couldn't check for the possibility of WebM encode, but I was able to push a webm encode (made with a newish version of ffmpeg from the command line) to my phone and watch it with audio and video. BTW, the "Movie Player" from the original and other ROMs doesn't apply here, access movies via the Gallery App.
[Captivate Android Development] opcow:
See Khoas-Rage's post regarding getting into download mode.
[Captivate Android Development] mrbloog:
Thanks, man do I love XDA for everyone being nice. :D
[Captivate Android Development] maxjivi05:
Awesome progress I can't believe how fast you all are with porting this! Thanks so much for your hard work!!!
[Captivate Android Development] kennethpenn:
My bad here you go. :)
[Captivate Android Development] danquirk2000:
Frequent reboots. At this current stage of development I would not recommend flashing this.
[Captivate Android Development] designgears:
Working 3G on the captivate :)
[Captivate Android Development] danquirk2000:
Designgears, do you receive frequent reboots while on GB? I had the same modem and kernel that you had flashed per your picture.
[Captivate Android Development] mikejames07:
:eek::eek::eek:
[Captivate Android Development] designgears:
No reboots yet, been beating the crap out of it too.
[Captivate Android Development] bfgarzilla9k:
designgears, you sunovab!+©#.. *manly handshake*

Man, this is getting exciting. ;D
[Captivate Android Development] Torridred04:
First post, scoped the forums since I got my Cappy and switched from my iphone. Found a lot of great information here, so i figure i could try and help out as well. Using this same setup as Design it's running beautifully. Service/Data did not work until after the first few reboots. Cannot test calling yet but will asap. Great work everyone!
[Captivate Android Development] Banditlol:
hey dg did you have that modem from 2.2? or did you flash that while on 2.3?
[Captivate Android Development] vbhines:
There's been working 3g for a while...JK4 is what I've been using, not a single reboot or connection drop in the three days since my first boot.
[Captivate Android Development] TheEscapist:
You lucky ho. :pI've got everything I need working, other than those damn reboots. I'm even running the same modem.
[Captivate Android Development] Sebring5:
works as advertised, great job supercurio and xcaliburinhand and everyone else who worked on this (special thanks to CB Wolf (ISS?) for his helpful posts)
[Captivate Android Development] vbhines:
I've asked it a dozen times - would some enterprising individual with reboot problems *please* plug your phone in, run logcat, and post or PM me the output at the time of the crash. Thanks!

Signed,

Your friendly neighborhood bug tracker
[Captivate Android Development] TheEscapist:
Will do. It's just logcat > log.txt, correct?

Edit: Here's the log. I had to trim it down a bit, was too big for the forum. I left everything at the end. I didn't see anything to exciting. Going to wipe and reflash, see if that clears it up.
[Captivate Android Development] opcow:
I was going to do it, but I decided to do a clean reinstall first since I had let it do the OTA update (although I don't know what, if anything, that changed). After reinstalling I'm getting no reboots, however. I can't remember if I got reboots before I said yes to the update.
[Captivate Android Development] vbhines:
Thank you :-) I'll take a peak after figgy pudding, etc.
[Captivate Android Development] TheEscapist:
Still getting reboots after a fresh wipe. Wifi hasn't been touched. Going to try setting wifi sleep to never, but still not turn it on.

EDIT: Nope. Still getting reboots. Going to do a new logcat.
[Captivate Android Development] vbhines:
I took a look at the three different logcat dumps. I know the dev team is already aware of a wifi sleep bug, but if it helps anyone...

I haven't had any reboot issues even with wifi on, but I run it with network notification off and wifi sleep off *completely*. After reading the logcat dumps, I enabled wifi, enabled notification, and turned on "wifi sleeping when screen off." Had my first reboot in about 30 seconds :-) (I wasn't connected to an access point either).

After restart, I turned off wifi sleeping again, but kept network notification enabled, wifi on, and still not connected to an access point - no more reboots.

Turned off notification and wifi - still no reboots.

If anyone isn't aware, to get to the sleep settings, to to Settings > Wireless & Networks > Wifi Settings. Press the Menu button, then press the Advanced option. Change wifi sleep policy to "Never", press Menu and Save (or just go back). That seems to solve the problem for me. Wifi sleeping is nice, but without it enabled I'm able to use this as a fully functional daily driver.
[Captivate Android Development] nbs11:
I also noticed that both logs I found ended with this thing

D/dalvikvm( )

I wonder what that is
[Captivate Android Development] kdwolf85:
Your welcome. I'll continue to test the new builds as they come out and as before as soon as I find a bug that affects my Captivate I'll post my findings. I'm normally just one to attempt some theming. However, I like the GB theme for now so I may not make an attempt to change it for a few more weeks.
[Captivate Android Development] vbhines:
It might help if people clarified when they are doing a "fresh install" whether they mean flashing the kernel (which is what the team is working on) or simply decompressing the tar file (which is not a dev product - just a dump of the actual Nexus S system). Disabling wifi sleep is working for me, but it's disabled by default, you need to do it manually. I'd disable it even if you're not using wifi. Also, if you overwrite the GB folder with a new decompress, you would need to disable wifi sleeping again.
[Captivate Android Development] TheEscapist:
I have been doing that, still getting reboots. In fact, my last logcat on the fresh decompression didn't even have wifi in it, as far as I can tell. I'll try one more time.

EDIT: Yup, still getting reboots within 15 seconds or so of the screen being off. It's almost like the never sleep isn't sticking. Any way to manually force it?

SECOND EDIT: Not getting reboots with notification off and sleep set to never when plugged in(my phone is plugged in).

THIRD EDIT: Switched back to never, no reboots. Minute I unplug, I start getting reboots.
[Captivate Android Development] opcow:
When I do a fresh install I go back to my froyo kernel, delete everything in /data/gingerbread, do the same steps I did the first time I installed it and then flash the gingerbread kernel. I don't know what other way you could do it.