yashsingh1/xdaforums huggingface dataset:
[Captivate Android Development] makelegs:
Pretty sure all the T9 stuff got merged already. If you're looking at merged changes, then by definition they well be in the next build, even if the actual cherry picks fail to bake in for some strange goddam reason.

Well be completely redoing my repo tonight, so hopefully the gremlins get squashed.
[Captivate Android Development] Raul77:
Thank you !!! looking forward to the new repo !
[Captivate Android Development] emuking:
Notification swipe freezes

So I have a bug report and I'm really not sure where to post this information, be it given to the CyanogenMod team, or this thread as I am using these KANG's that implement the feature "Fix usability of swipe-to-clear feature". My question is where/who do I give what I have below to?

"I've had a few instances now where the status bar notifications will freeze the input of the widget buttons on top, other notifications, and the clear button. Repro steps are specific to having a "swipe-to-clear" applicable notification, attempting to swipe it but letting go just before it's moved enough to clear off to the side. Instead of settling back in it's original position the notification will freeze, remaining unaligned, as well as freeze the remaining notification center input. However, I can still pull-down and swipe-up the notification center. Only a restart of the phone (or of the status bar app I assume) restores it back to usable."

Sorry if this post makes someone out there absolutely furious :mad: that I didn't search thoroughly for duplicate bug reports or etc etc etc etc... (I did search btw). Just trying to help.
[Captivate Android Development] makelegs:
Redemption

Sorry for that last build. I believe redemption is on it's way here very shortly. A lil bad news in the pick list, but believe me when I tell you it's prolly for the best.

Someone please confirm that the new build is not a complete POS (like the last one was) :confused:

kthxbai
[Captivate Android Development] Gromlakh:
I'd hardly call the last one a POS. It ran just fine, just like they always do. So a few picks were left out...we can deal. ;)

Not that I ever used it, so it doesn't really matter to me...but what's the reason for dumping the MIUI battery mod?
[Captivate Android Development] makelegs:
The gate keepers refused to accept it, so the dev (at someone's suggestion) opted to alter the battery mod from running horizontal along the top of the screen to running vertically along the right side of the screen. The only problem was that it really sucked that way. He'd been battling rejection for months, so, faced with some pretty understandable criticism of the newest change, he "abandoned" it. I'm surprised it lasted as long as it did. I really liked the mod, but I won't miss having to pick 4 different components with every build, quite frankly.

Oh well.... life of a #crackflasher :eek:
[Captivate Android Development] Gromlakh:
I never understood all the opposition to it anyway. I mean, it's one thing if it totally breaks the phone or the build, but all I was seeing was "I don't how it looks"/"Looks too 'MIUI'". If that's your problem...don't use it?
[Captivate Android Development] makelegs:
..#truth..

---------- Post added at 11:32 PM ---------- Previous post was at 10:46 PM ----------

Be on the lookout for occasional reboots when suspending with power button under certain circumstances. I believe it could be related to the updated patch set for lockscreen right alignment. If the dev does not revert the patch, then I may very well drop it next build. I don't use it anyway.

I know I have seen this bug the last day or 2. Not a big deal, really. Just report back if this applies to you.
[Captivate Android Development] Malorkus:
I just flashed this for the feature "Default volume control media" but I can't find the option to set it anywhere. Am I being dense or is it missing from the latest build? Thanks.
[Captivate Android Development] FireRaider:
I just flashed the 22nd update. Anything that was green is now blue. Changing themes only fixed some of them.

Edit: second reboot fixed it. Weird. I have flashed most of these Kangs with no issues at all.

sent from XDA app
[Captivate Android Development] RichMD:
Please post the 12/17 build (latest with MIUI bar)

I'm still running the 12/13 build (I think) and I would like to get the latest with the MIUI bar. I will stick with that until I upgrade to ICS.
[Captivate Android Development] mark72501:
Wifi

I've been using CM7 for awhile and recently started using the KANG builds. I have a question about an issue I have with wifi, though.

Regardless of which CM7 I've been on - including the KANGs - I cannot use wifi. I can connect fine but after a few minutes the Internet stops working...and not just on my phone but for any device on my home network. Any idea what's causing this?

Someone suggested once that it had to do with the IP address conflicting with another device on my network but messing with that I never got it to work any better. Someone have an idea?

Thanks in advance...
[Captivate Android Development] readitodie:
After toggling 2G/3G, 3G stopped working.

Clearing cashes and flashing different modem didnt help.

wifi works fine.. Anyone know how to fix this?
[Captivate Android Development] makelegs:
Ummmm....it's the default setting. With screen on, adjust volume, and it should say "media". Works for me. Not an option at all, I don't think.
[Captivate Android Development] makelegs:
Refer to: set default theme to cyanbread.

....hence the blue stuffz ;-)
[Captivate Android Development] makelegs:
There "might" be hope for getting miui back. Prolly not tonight, but all hope is not lost (except for official merger....that ain't happening)
[Captivate Android Development] lownox:
Flashed. Thanks for the present.
[Captivate Android Development] MaxRabbit:
After watching the work you've put into this, I finally flashed your KANG and Glitch kernel. Pretty happy, and thanks for all your work so far, but I'm having two issues so far:

1) Automatic brightness is extremely dim and does not increase.

2) My own ringtones and notifications in media/audio folder are not showing up; I've never had this problem before.

It would help to unmount USB storage (DURR).

Any tips?
[Captivate Android Development] makelegs:
I got nothing, man. You're the only one across 4 devices to report this. When in doubt.... wipe cache/dalvik/fix perms
[Captivate Android Development] FireRaider:
Had the reboot big numerous times on the 22nd version. Flashed the 23rd update this morning to see how it goes.

sent from XDA app
[Captivate Android Development] makelegs:
It should be gone with the newest build....(I think) :eek:

I dropped a few picks that were pretty inconsequential to me, anyway. I think they were just messed up.

---------- Post added at 11:28 AM ---------- Previous post was at 11:21 AM ----------

I will be off doing family stuff for the holiday. Unless something really big happens (highly doubtful), I won't build again until mon or tues.

Thanks again for all the support, folks!

Wishing everyone a Merry Christmas!:D
[Captivate Android Development] Malorkus:
Hmm... For me it's still defaulting to ringer volume. Any ideas for troubleshooting? I flashed the 12/22 build over the latest CM7 nightly.
[Captivate Android Development] makelegs:
I just took a screenshot of my default volume showing "media." The only possible explanation, in ur case, that I can think of is that feature was originally a 2-part (frameworks & cmparts), but only the frameworks part was merged. I'm pretty sure the cmparts pick was having difficulty merging, so I dropped it, recently. If that is causing it not to work for you, then I'm not sure why it still works fine for me...
[Captivate Android Development] Gromlakh:
Did you have any kind of sound playing while taking that screenshot? 'Cuz, for me, it's always been (and still is on the latest kang) default to modify the ringer volume if nothing is playing, but media volume if there's any kind of sound being played.
[Captivate Android Development] anishz:
Same for me.
[Captivate Android Development] makelegs:
Nope....that would sorta be like cheating if I had ;)

The Dev needs to rebase the cmparts change. Really not sure why only half of it was merged, anyway. I've been using that mod for so long that I have no clue when it may have broken for u guys.
[Captivate Android Development] edwardng:
GPS problem

How did you guys get gps lock less than 30 seconds? lol

And it's so unstable :(

PLEASE HELP ME

P/S: I tried to use gps status and toolkit still very tough @@
[Captivate Android Development] makelegs:
Ok guys... I may need some help, here. My friend's cappy, I'm told, is freezing at AT&T logo and won't boot into recovery. This sound familiar to anyone? Easiest fix? Will adb work from AT&T logo?

Sounds fixable to me....but?
[Captivate Android Development] Gromlakh:
I don't know that he'll be able to get to recovery if the freeze is happening before the kernel splash screen. He may need to go to download mode and flash a stock package to recover.

Sent via Captivate (powered by CyanogenMOD)
[Captivate Android Development] makelegs:
I guess my Odin-avoidance steak might finally come to an end, then
[Captivate Android Development] mcala:
Just use the heimdall kh3 no boot loaders. Works fine with Ubuntu with the openjdk Java. Find it in the stickies. No need for Windows.
[Captivate Android Development] makelegs:
Thanks.

I'll let ya know how it works out. B-)
[Captivate Android Development] makelegs:
Wow....that phone is seriously FUBAR!! Heimdall flashed, but didn't actually bake in cwm, and it still won't go into recovery, so I'm stuck at stock/un-rooted 2.3.4.
[Captivate Android Development] mcala:
You used this one right? This has CWM baked in.

http://xdaforums.com/showthread.php?p=19172102
[Captivate Android Development] makelegs:
I'm 99% sure that's what I used. Even if it had cwm baked in, it simply won't boot to recovery... At all! It still just hangs at the att logo. It will boot into stock ROM, but that's it. Pissing me off. I'll try again tonight
[Captivate Android Development] lownox:
Latest build is running great! Smooth as Astroglide. LOL
[Captivate Android Development] makelegs:
HOLY ****!!!

I don't know what horrible atrocity was inflicted upon that cappy, but it took several acts of congress, a crossroads deal with satan, and some serious SGS noobishness to get it F#@%ING working again!! :eek::eek::eek:

#WHYIUSENEXUSDEVICES

I guess I should run a new build, now...
[Captivate Android Development] lownox:
Must charge phone ... must charge phone ... must charge phone. :D
[Captivate Android Development] makelegs:
/sizzle /sizzle

New build up in a few minutes...

FWIW...I actually updated post #2 with the most current picks. As always, the pick list at euroskank should be considered most reliable, although in this case it's a cut/paste job ;)

Added some funky picks that are newish but I must not have noticed them before. For those of you who may have had concerns about default media volume, the CMParts commit appears to have been rebased and I was able to merge it again (even though it always continued to work on my device). Hopefully it now works for everyone. Went back and forth with a few conflicting cherry-picks putting this build together. Lemme know if some picks don't appear to be working.

Enjoy!
[Captivate Android Development] edwardng:
Please include angry gps for gps lock tweaks...

Default gps lock was so ****ty that i needed to wait few minutes =="

Battery draining is so fast anyway to have a better battery life

Not sure what problem but when i try to play tiny bee, it is a very little bit laggy which is not very noticable

Btw thanks for ur effort. I love Kang build instead of samsung-based rom: touchwiz :)
[Captivate Android Development] pkadavid:
First off, I want to say thanks for this awesome rom. I finally made the jump to CM, and I just regret taking so long to finally do it. Best rom I've tried.

I haven't been able to find any info on getting a call to automatically go through the bluetooth headset when it is connected. I always have to select it manually on the call screen.

Does anyone know if there is a way to set this to use the headset by default?

Thanks!
[Captivate Android Development] hayslett4:
My BT headset will pick up the call after the first ring. I have to hit the button on the headset to answer, but the phone sends the call right over. Try to unpair and pair again... or test with another headset.

I've had to make sure the phone BT was enabled before turning on my headset... otherwise it wouldn't take the call or activate any voice commands.
[Captivate Android Development] theyurtingyeti:
NOTIFICATION FREEZE & T9 Availability

I'm seeing the same thing. I'm on the 12/17 Kang. Is it fixed for the most recent (12/27).

Also, I think that I've read that T9 is good to go on these Kangs, but I can't figure out how to get it working properly...
[Captivate Android Development] raz123:
TV Out?

Has anyone tried the TV out feature?

On the previous build, it wouldn't work properly with my setup (tried 2 TVs).

TV picture seemed out of sync.

Can anyone else give it a shot?

Thanky
[Captivate Android Development] pkadavid:
Thanks for the tip, but this is happening when I make calls. I always have to hit the button on the lower left of the call screen to get it to use the headset. I thought that there may be a setting to activate it by default.
[Captivate Android Development] makelegs:
Ya....this is a Kang not a custom ROM. Feel free to make use of any tweak, app, or fix you want. But if it ain't in gerrit, then it ain't in this build (with 3 noteworthy exceptions, only)
[Captivate Android Development] solarpenguin:
Anyone else having an issue with the android market correctly identifying your location with this kang? I had to use market enabler to set my location to USA/at&t so that I could d/l juice defender ultimate...otherwise I got the dreaded "this app isn't available on your carrier " message.

This is happening on both my phones following factory reset / install of the kang.
[Captivate Android Development] makelegs:
That doesn't seem to bode well for: [NEW] Fix Galaxy S 1 devices market filtering.

This is the first report of that issue. Hopefully others will chime in on the matter. If it's determined that pick does not work, then I'll drop it.
[Captivate Android Development] mgfjd:
Thanks. I am able to buy games again..

Don't drop the feature, please.

This is the right fingerprinting.

I just bought a bunch of games that I couldn't before.

I think it is a problem with juice defender, it is not recognizing my old fingerprinting either.

Why do you need juice defender any way? CM7 is better without it.
[Captivate Android Development] sam razzy:
Can some one please post (upload) the screenshot...? Don't put bomb on me?
[Captivate Android Development] belyle:
I'm having the same problem on the latest Kang. I flashed from the last nightly (181). I wasn't even trying to swipe to clear it, I just touched it funny, then all my drawer notifications got stuck. Had to reboot phone to fix.
[Captivate Android Development] MechaGen:
Same as above. Nicely described by Emuking.

Flashed 12272011 this morning, by noon my notification bar was frozen. Never had this or any problem with 12172011, so I restored my Nandroid backup.

Of course my notification bar froze shortly after restoring the backup. Rebooted and haven't seen it again.

By the way, stock kernel, not even running v6.

Sent from Tapatalk, NOOK Color CM7 Nightly's!
[Captivate Android Development] killer23d:
I am using 12232011 build, the drawer is working.
[Captivate Android Development] makelegs:
DING! DING! DING!

Congratulations! You have now officially been nominated to post a screenshot!

(give you a hint.....it looks EXACTLY like cm7....wonder why!?)
[Captivate Android Development] emuking:
Have you by chance exhausted the repro steps in my original post of the bug? Sadly, it could be tough to reproduce depending on how small the range is that the notification has to be swiped to make it freeze. The swiping didn't freeze it but a fraction of the times I swiped one, so even as small as a pixel's-width could be possible I imagine. I'd exhaust it myself right now to verify its consistency, but I randomly hit it 3x's throughout my use of these KANG's already and I'm now testing out ICS ;). But coming back eventually...

Are you referring to the notification center bug I posted?
[Captivate Android Development] solarpenguin:
It's not really causing me grief as I am able to get to JD by using market enabler. Just wanted to post in case it was indicative of a larger issue.

It does appear to be most probably related to JD as I am still able to get to other apps without issue.
[Captivate Android Development] raz123:
Can someone else test the TV Out feature of the 7.2 build?

Definitely not working here.
[Captivate Android Development] Twicebak3d:
I have it working on stock kernel, but it stops working when I flash Glitch. I'd just use stock but I get so much more battery out of Glitch, and its an asset for me.
[Captivate Android Development] anishz:
1st of all Happy new year to everyone here!

Hi makelegs!

What kernel are you using? The stock is very stable for me, but lags when playing GTA 3 (OC'ed to 1300mhz), any suggestions.

I always used glitch before, but there is this led notification problem. Will be trying the platypus neo kernel.

Also can anybody suggest some themes (i like simple themes and not the gaudy ones).

This past week i have been on a flashing frenzy literally jumping on a new one everyday!, and now that my flashing desires are satisfied (a bit), i am back to the most stable rom for me.

Even samsung roms are unstable for me, lots of fc's and random reboots. Thank you very much makelegs for continuous updates to this kang.:)
[Captivate Android Development] MaxRabbit:
I found my favorite themes by going to the market website, searching CM7 themes, and sorting by popularity :)
[Captivate Android Development] anishz:
Thanks, i just got the cyan ice, wp7 and mymod ver 2.1 themes.

I liked the wp7 theme, simple and elegant, i will try using launcher 7 with it.

cyan ice is cool theme, good icons.My mod is colorful icons miui style, looks good too.
[Captivate Android Development] makelegs:
sms

Anybody have SMS issues with latest build?

Reports from fascinate users that it's messed up. Works fine for me on passion, though. Not sure if it's an Aires thing, or specific to fascinate.
[Captivate Android Development] sixstringsg:
We fixed LED already by the way. Build will be out soon.
[Captivate Android Development] mcala:
SMS works fine on latest build from Dec.30!
[Captivate Android Development] anishz:
sms works fine for me too.

Thank you very much sixstringsg, willl look out for the new build.
[Captivate Android Development] MaxRabbit:
Omg can't wait.
[Captivate Android Development] MaxRabbit:
Can't find wp7?
[Captivate Android Development] anishz:
I found 2 of them, both are equally good try them out.

This One and This One.
[Captivate Android Development] Gromlakh:
Theming your Android phone with a Windows Phone 7 theme is like pimping out your Lexus by making it look like a Pinto.
[Captivate Android Development] MaxRabbit:
Dark one is beautiful!!!
[Captivate Android Development] anishz:
Dude you are right but to each his own! To be totally honest, android isn't exactly lexus, its looks dull and that's the reason for all the manufacturer bloatware skins, ICS is little better but it's difficult to read in direct sunlight. And the main reason to use android is customisation.

Sometimes the subtle design is good too (on the eyes) as i keep on changing my themes.
[Captivate Android Development] latinoguy:
Excellent nice looking rom, I just want to know how to disable led notifications and also how to imporve battery, thnks and happy new year
[Captivate Android Development] MaxRabbit:
Flashing Glitch kernel would help both.
[Captivate Android Development] latinoguy:
I tried to download but I can not do it from this post can you tell me where I can get it, thnks http://xdaforums.com/showthread.php?t=1304037
[Captivate Android Development] sixstringsg:
Try the link again, and read this time.
[Captivate Android Development] makelegs:
time for MOAR BACON!

Newest build axes the sgs1 market filter "fix"

Trying to troubleshoot this weird sms issue with fascinate users, and the market filter commit seems most likely. So, sorry in advance, to all of you who may have liked that pick.

Additionally...github has been menstrual lately, so building has kinda been a PITA. Please lemme know if any strange bugs crop up in this build.
[Captivate Android Development] sixstringsg:
Repo sync -f

Or

Modify .report/manifest.XML to be https:// instead of git://

Either should fix it.
[Captivate Android Development] makelegs:
From cyanogen:

We are having issues with the CM repositories on Github. You might not be able to sync. I opened an issue with Github.

https://twitter.com/#!/cyanogen/status/153574209384222720

-f sorta helped, earlier. Haven't tried switching to https, yet.
[Captivate Android Development] sixstringsg:
Ah, OK. Https fixed it for me. Another option: make a local.manifest.XML in .repo to take out android_prebuilt, then sync as normal, and if you need to, manually clone android_prebuilt.
[Captivate Android Development] mgfjd:
I have a captivate no problems with SMS. build 12/30 is a lot faster than 12/28. I will wait for a new Kang when the right maker finger printing iS back. I like to support the market buying games from google
[Captivate Android Development] makelegs:
Not sure if https helped or not. Definitely slower. Lots of different errors that way. -f seems to make the necessary impact. It's still ugly all the way around, though.

#gremlins
[Captivate Android Development] Raul77:
I just installed viber and had the same problem, took me a day or two to figure it out its the ROM !!! CM 181 works great, but Kang builds the mic doesnt work :(
[Captivate Android Development] RichMD:
Thanks for the builds. It seems to work well so far and I really like having the MIUI battery again. Sorry if this seems "picky" but I want to understand the CM7 / Kang build correlation a bit more. I see that CM_captivatemtd_full-179 is where the bump to 7.2.0 RC0 and it released on Nov 14 at 9:24am. The KANG build that includes that is dated Nov 16 at 03:21 - more than 24 hours later. I would have guessed the prior two KANG builds on Nov 15 and 14 (both after 179 released) would have included 7.2 if there was an automated solution where a buildbot is taking the build and merging it with your predefined "cherry picks". Are you manually merging the patches each time? It doesn't appear that we can assume the CM7 build from the same day is the base. If there was some indicator in the title (such as 179, etc) then it would make it much clearer.
[Captivate Android Development] 41LY45:
I see, kinda frustrating to see the phone still shows 1.2GB free space available. Yet I can't use it. Ohwells.
[Captivate Android Development] sixstringsg:
For the build.prop to change requires a complete rebuild, which is very slow. The buildbot does not take the cherry picks. The cherry-picks come from gerrit, where they will eventually be merged. The day the kang always comes out with the latest code, which is actually more up-to-date then the code the buildbot uses. Make sense? Here's some further gerrit explanation: Gerrit is a system for code review. Since CM7 is an open source project, anyone is allowed to submit bugfixes/new features. They go to gerrit, where a ton of people review then, then decide if they will be included. The review process can take weeks. The kangs get the code before the review process is complete.
[Captivate Android Development] anishz:
probably a stupid question, but if i flash this on top of the cm7 nightly will it wipe all my data, as i have some games which i don't want to start again. once before i backed up on tibu and went to a samsung rom but i couldn't restore data on it, it used to force close. Please help.
[Captivate Android Development] sixstringsg:
Same as any other nightly.
[Captivate Android Development] anishz:
The boot animation is (*O*). love the miui battery. Thanks.