yashsingh1/xdaforums huggingface dataset:
[Captivate Android Development] makelegs:
You might be over thinking this. :eek:

Let's pretend that nightly build #XYZ comes out at 1pm. It includes all the newest and coolest stuff that has been officially merged. Then I come along at 6pm and do a fresh repo sync. Anything that has changed between 1pm and 6pm will be in my build, in addition to or instead of what was in build #XYZ at 1pm. Regardless of what my build.prop is dated, the assumption is that I have repo synced (otherwise I would be building essentially the same build) and that the time stamp of the of the actual downloaded file is indicative of when, in relation to nightly #XYZ, my build fits into the timeline, and therefore what may reasonably be expected to be similar or different form #XYZ.

The cherry picks that I add are done so each time I build. While "manually merging" could technically mean a more complicated process, I do have to apply each aspect of a given pick, one at a time, to each build. In the context with which you asked, though, it's fair to say that I manually merge them.

Do not feel compelled to gauge the "feshness" of the build based on the date/time stamp in build.prop. I assure you that my build is more current than whatever official nightly preceded it.......plus we have cherries on top! It's very simple. If I "clean" my directory before each build, then the build.prop will update with each build. The drawback is that my build time will take 2+ hours vs about an hour or less, because my computer kinda sucks.

I hope that seems more clear....

JUST FLASH MOAR BACON NAO!!! :D

---------- Post added at 01:11 AM ---------- Previous post was at 01:08 AM ----------

Nandroid and Titanium are 2 of the best friends you ever had... ;)
[Captivate Android Development] RichMD:
Thanks to both Six and you for trying to help me understand. I saw your initial post about ignoring the build.prop and it makes perfect sense. I am not looking at that anymore. My second question was prompted by the fact that I was simply looking at the #179 CM build containing 7.2 came out two days before the KANG build that referenced the bump.

All I am really looking to do is for each KANG build, I would like to know which CM7 build (showing all the fixes) is included. If I can't use the date of the release then I am trying to figure out what I can use.

It would not be a bit surprising if I am "over thinking this" :p Over analyzing is one of my traits... :D
[Captivate Android Development] anishz:
Will cm7 adw launcher ever get 3d app drawer scrolling like in the adw ex. i have the adw ex but the opening and closing of the app drawer seems to be more smoother on cm7 stock adw.
[Captivate Android Development] makelegs:
I honestly don't know how to make it any more clear.

I haven't used an official nightly on my personal device in over a year. The whole point of flashing a Kang is to be just a small step ahead of the nightly builds. Cherry picks simply make that step even bigger.

The filename version (7.2 rc0) is determined by the build.prop. If I had not cleaned my build directory, then it would still say 7.1. But it still wouldn't really matter in the grand scheme of things. If the date/time stamp in my build filename is newer than the most recent nightly, then you can safely assume that you are living in the "nightly future"

KANG > NIGHTLY > STABLE
[Captivate Android Development] makelegs:
Additionally.... I am saving/shopping for parts for a more proper build machine, and hope to have CM9 builds running before the CM9 nightly builds are officially available.

We'll see if that works out or not, though... ;)
[Captivate Android Development] nkrick:
You can use that 1.2 GB of space, but not for /data/data (or /datadata if you prefer - they are essentially the same thing). On the Galaxy S phones, there is a separate partition named /datadata and /data/data is symlinked to it. Because /datadata is a separate partition, it doesn't matter how much free space you have in the root partition (/), it will not be available for /datadata.

edit: to clarify, the /data/data symlink to /datadata for Galaxy S only applies to CM (and other MTD based ROMs), not to Samsung ROMs.
[Captivate Android Development] 41LY45:
Ahh, I see what you mean.

To clarify I meant the Internal Storage (2GB partition) , not the Internal SD (10GB partition)
[Captivate Android Development] RichMD:
I see! said the blind man...

Initially, I was looking at the build.prop. Then, you told me that lags behind the code that is actually included. Therefore, I ignored the build.prop and figured I thought I could use the filename. I didn't realize that the filename was based off the build.prop so that lags as well. Therefore, when I saw CM7 179 (bumped to 7.2) came out on the 14th and your filename on the 15 still said 7.1 I thought it couldn't contain the latest merged code. I "assumed" the build.prop and filename were not linked.

---------- Post added at 08:20 PM ---------- Previous post was at 08:06 PM ----------

If I remember correctly, that design difference of CM7 symlinking data/data to a separate partition is to allow a different filesystem that is much faster which is what gives CM7 a boost - correct?
[Captivate Android Development] makelegs:
EUREKA!!! :D

It's all good man. All you really need to know is that if you are flashing this kang you are in fact accomplishing what you have set out to accomplish (that is...ur phone is a lil bit cooler than the guys flashing the official nightly builds! :cool: )

#crackflasher is a lifestyle choice \o/
[Captivate Android Development] shaolin95:
Not sure how I missed this!

Going to try it now. :-)
[Captivate Android Development] makelegs:
Do it NAO!!!! :D
[Captivate Android Development] Snow.Goose:
Tried it today, battery was amazing... They probably improved cm7, was running the stable before... Unfortunately, one of my favorite games (yubiosi) have stopped working... Not sure why... I flashed all of the current kangs and the latest cm7 nightly but it's still broken... Battery life is more important so I'll stick to the Kang for now...
[Captivate Android Development] makelegs:
BACON is curing as we speak.

There really aren't any new noteworthy cherry picks that I've noticed. I think the energy already shifted toward CM9 development.

New build should include a minor cosmetic change. See if anyone even notices :eek:
[Captivate Android Development] 41LY45:
Holla it on Twitter when she's out. :P
[Captivate Android Development] pkadavid:
Potential bugs to report. I flashed the newest build (Jan 2) this morning.

Three issues I was experiencing before flashing the newest build:

1. googlequicksearchbox FC. Happened right when I started the phone or tried to access the search widget.

2. My phone would reboot whenever I tried to enter to access the account and sync settings.

3. My calendar wouldn't start. Nothing would happen when I tried to start the app, no FC messages.

Since I think that all three of those issues are related to having an account synced with the phone, I can't retest yet.

New issue:

Flashing the newest build removed my Google account. When I try to open the market, it asks me if I want to set my account up, but nothing happens when I click on "yes."

Grateful for any help! Thanks!

::EDIT::

I reinstalled gapps, and now everything seems to be working again. For now, though, I selected to NOT back up my phone with my Google account. Maybe that's what was causing it.

I will keep an eye on it and see if I start getting FCs again. They didn't start appearing for several days last time, and I don't know of anything that I did to cause them to start happening.
[Captivate Android Development] makelegs:
When in doubt wipe cache & dalvik and fix permissions. The need to re-flash gapps like that, from time to time, seems to exist on all phones. Could be nearing the time for a full wipe. I always let google backup stuff, too.
[Captivate Android Development] makelegs:
**innocent whistling**

New build adds newest market filtering attempt. Lemme know if it works or breaks stuff (like SMS).

Had to drop the ringlock redesign pick. 1 of the parts needs a rebase. Hopefully it will be back for next build.

:D
[Captivate Android Development] makelegs:
Rings are back for this morning...forgot to update pick list, though.
[Captivate Android Development] mgfjd:
http://xdaforums.com/showthread.php?t=1411317

you want to try these?? it is great..
[Captivate Android Development] mgfjd:
Anybody here with the skills to create the framework for the captivate? the mod in my galaxy s2 is awesome..
[Captivate Android Development] makelegs:
Maybe you should code it and submit it to gerrit......then I would be happy to cherry pick it.
[Captivate Android Development] mgfjd:
I was hoping someone was going to post the modified file and the revert back. I wouldn't trust myself creating a file that can mess the phone up.

I already tried once. As long as someone post the file like the other forums, we don't need to wait.
[Captivate Android Development] makelegs:
uploading now

Couple new picks....
[Captivate Android Development] Malorkus:
Here you go, these should be CWM-flashable for recent CM7 builds and makes the scroll cache modifications suggested in that post. As always, backup first and flash at your own risk yadda yadda yadda...
[Captivate Android Development] juliobahar:
Are you guys having issues with viber? Microphone doesn't seem to work
[Captivate Android Development] makelegs:
Taking comments on boot animation...

Lemme know if the boot animation looks like crap, folks.

It doesn't scale correctly on my N1, but you have bigger screens. Not sure what the native resolution difference is. It should look better on aries devices, though.

If not, I'll change it back.
[Captivate Android Development] xThe Enforcer:
Hmn... This or the latest Nightly... Decisions, decisions! What makes this ROM better and unique? Any opinions?
[Captivate Android Development] anishz:
It's just a kang, a few cherry picks are added to the nightly. You can see them in the 2nd post. If you like the picks use this or use nightly.

Makelegs: The bootanimation doesn't look good on cappy either, please go back to the one from rascarlo.
[Captivate Android Development] mcala:
This Kang also has the latest updates since the build bot went offline back at #181.
[Captivate Android Development] makelegs:
Hmmmm......I can't begin to imagine why this might be better than a 2 month old nightly build without any cherries..... :rolleyes:
[Captivate Android Development] boog:
I am working on doing it in the java source and compiling it in. Just not an expert, so I will have to do some experimenting. Hoping it will be better than decompiling and messing with smali.

Have it sizzling now :)

I think I have it if anyone is interested. This is just like a nightly with (hopefully) the scrolling mod compiled in.

my server is slow, sorry about the speed. haven't taken the time to upload somewhere like dropbox

http://boog.is-a-geek.org/kang/update-cm-7.2.0-Captivate-boog-01-08-2012-15:34:31.zip
[Captivate Android Development] Cor-master:
So I'm running the Kang build from 1/2/12, with glitch v13. 1. Was running it without glitch till yesterday, seems now my alarm clock app doesn't work, force closes when I open it. I might reflash the Kang build. There an issue with glitch and this rom?
[Captivate Android Development] tbrummell:
This ROM & Glitch go hand in hand. My Alarm CLock works just fine, use it twice daily. Try a Fix Permissions from Recovery, if that doesn't work, flash the ROM again.
[Captivate Android Development] Cor-master:
I just reflashed and no luck. Alarm clock won't open, force closes, I've wiped data to it, cleared cache, no dice, not sure the issue. Might just freeze it and find another alarm clock app, I don't feel like doing a total wipe. Any other suggestions? Anyone got the apk for the alarm?
[Captivate Android Development] Cor-master:
I just removed it with titanium backup, got an app off the market, more options, tested and works
[Captivate Android Development] boog:
What about just clearing the data for your alarm app?

Or you could always try to pull it from another cm7 rom. But, I have been using alarm clock xtreme for months, and I like it better than the default one.
[Captivate Android Development] Gromlakh:
There's also been the suggestion to fix permissions from recovery, which I didn't notice you saying you'd tried. That usually fixes force close issues.

Sent via Captivate (powered by CyanogenMOD)
[Captivate Android Development] makelegs:
Wipe system only and then flash ROM and gapps, and everything should be back to normal.
[Captivate Android Development] boog:
I'm guessing you quoted the wrong post :D

But, yes, I would suggest fixing permissions, too. As well as clearing the data for the acting up app.

But it looks like he has already moved to a different alarm app.
[Captivate Android Development] Gromlakh:
Yeah, sorry, should have clarified that... :P
[Captivate Android Development] makelegs:
Fyi....there's a really good chance that the next build will have miui battery back

Justsayin
[Captivate Android Development] Malorkus:
I don't know if anyone else flashed the "scroll cache fix" ZIP I posted the other day, or followed the instructions themselves, but yesterday I noticed a strange problem where the clock widget on my homescreen wasn't updating the time reliably. I've never seen that before so I flashed back to the previous non-scroll fix framework, and haven't noticed it since. Since I never noticed that big of a difference from that "fix" anyway, I'm not going to bother testing further, but before anyone submits this to be cherry-picked in future builds, I would suggest being on the lookout for a similar issue like this to avoid introducing a new bug...
[Captivate Android Development] Cor-master:
Yeah I did try fixing permissions, no luck, also cleared data also no luck. Anyway everything else seems to be working fine and i grabbed alarm clock plus from the market, deleted the stock one. Also paid the $2 for ad free, so problem resolved. The stock android apps all kinda blow anyway so anytime you can replace one its a good thing anyway
[Captivate Android Development] makelegs:
JUSTSAYIN'

*cough* *cough*
[Captivate Android Development] JiroPrinz8:
Oh man.. i just flashed the 0108 build today..! Oh well guess i better start downloading the latest..
[Captivate Android Development] Cor-master:
Today my whole system went haywire. constant force closes on google framework, gapps, etc. I cleared dalvik cache and that fixed the problem. After that I decided to go ahead and update to the newest KANG and I cleared dalvik cache as well as installed glitch before I booted it up, and its working fine, and the Alarm clock works again. Apparently I needed to clear the dalvik cache from the beginning. Its actually running alot faster now!
[Captivate Android Development] makelegs:
new pick

HOLO lockscreen anyone??
[Captivate Android Development] lownox:
Sweet. Thanks. I was still running Christmas Eve build.
[Captivate Android Development] boog:
If anyone is interested, here are my random builds. Should mostly be similar to nightlies. Not doing any changelogs or anything yet.

http://boog.is-a-geek.org/kang/captivate/?C=M;O=D
[Captivate Android Development] makelegs:
If someone could confirm that the holo lockscreen made it into the build, I would appreciate it. There may have been a derp along the way.
[Captivate Android Development] skyxliner:
I don't think holo made it unless I need to change any settings
[Captivate Android Development] makelegs:
cmsettings > lockscreen > style options > ring-lock style
[Captivate Android Development] skyxliner:
Got it to work thanks. I like it.

This build is significantly faster loading apps for some reason. Pretty good!
[Captivate Android Development] makelegs:
Good deal. Other thread had me concerned for a sec! :eek:

It's purrrdy!
[Captivate Android Development] mnjm9b:
Still having an issue with my kang...

I finally figured out the repo sync issue. And I got it building again.

Everything new seems to work fine.

However, the galaxy s settings (ariesparts) keeps fc'ing.

Got this from logcat:

W/Resources( 9274): Converting to string: TypedValue{t=0x10/d=0x640 a=-1}

W/Resources( 9274): Converting to string: TypedValue{t=0x10/d=0x17 a=-1}

W/Resources( 9274): Converting to string: TypedValue{t=0x10/d=0x2 a=-1}

W/dalvikvm( 9274): Exception Ljava/lang/UnsatisfiedLinkError; thrown while initializing Landroid/hardware/TvOut;

D/AndroidRuntime( 9274): Shutting down VM

W/dalvikvm( 9274): threadid=1: thread exiting with uncaught exception (group=0x40015560)

Any ideas?

Replacing ariesparts with an older version works but then there is no tv-out settings....
[Captivate Android Development] boog:
Interesting, it looks like mine has it too. I am guessing they may have something broken in the repo.

I guess that gives us something to look into...
[Captivate Android Development] MaxRabbit:
There's something glitching in the top of your screen!

Trolololol :)
[Captivate Android Development] mnjm9b:
Well, its good to see its not just me....I was about to toss this...lol

Is this same problem happening with makelegs? Can someone confirm.
[Captivate Android Development] makelegs:
Been having weird issues, lately, but nothing prohibitive. Built 5 devices last night.
[Captivate Android Development] boog:
But, does settings>device setting fc for your builds?

If so, I would bet they will have it fixed in the next few updates. If not, we will have to figure out what we have wrong.
[Captivate Android Development] mnjm9b:
I have been having this issue for every build after they put tv-out stuff in...(I have built about a dozen after #181)

so unless there is a pick that makelegs is putting in separate that addresses this issue, I doubt his works either. (again, someone using his rom can confirm???)
[Captivate Android Development] Time_Zone:
And I see it has changed from Blue to Green.

It is unconfigurable and that is mean

I guess I'll live with it, or so it seems.
[Captivate Android Development] tbrummell:
I'm running makelegs' build from the 9th, I can enter Device Settings without error...
[Captivate Android Development] Malorkus:
Quick question: Has anyone looked into the Google Maps vibration force-close for versions above 5.11? It's been a while and I'm surprised it hasn't been fixed yet afaik..
[Captivate Android Development] mnjm9b:
ok then... so any thoughts on what is fc'ing it on a basic build with no added picks other than what had been already merged from gerrit.

what are we missing???
[Captivate Android Development] makelegs:
If your build is compiling, it should work. How many projects are syncing when you repo?
[Captivate Android Development] Raul77:
I have the same issue, i really hope something could be done, i had to go back to CM7 181 since i use viber a lot to make calls :(
[Captivate Android Development] makelegs:
I know squat about viber...but is there some way to incorporate their function into the native SIP function of cm7. I use gtalk/gvoice for SIP calls (every once in a blue moon). Works fine for me, and is essentially the same thing....I think

Just a thought
[Captivate Android Development] boog:
How do you tell? I see things about ics, but I have it the repo init for gingerbread. I wouldn't think it would pull ics stuff when set to gingerbread.

everything builds just fine for me, but still get the fc issue. I also went as far as doing a factory reset, fix permissions, then testing before restoring everything.
[Captivate Android Development] makelegs:
Not easy to diagnose. I wouldn't worry about the fact that some ICS branch stuff gets synced. How many projects are fetched? have you tried nuking your directory and starting fresh? My most recent error has to do with a .mk file for lg e730, of all things. Keep having to trick the directory into building past the error. Haven't ever had the type of problem you're describing, except when I cherry picked something that caused it. Sounded as though you were building vanilla, sooooo.....dunno.

#gremlins
[Captivate Android Development] mnjm9b:
compiles fine...

syncing 313

I may need to nuke it...

I tried that before and was having trouble syncing

so I just used my last backup that I had which was from just before the tv-out stuff.

I am sure there is something buggy there but I am unsure how to fix it so I will try to do a fresh sync and see what happens.
[Captivate Android Development] makelegs:
local_manifest

I'm syncing 327 projects. You're likely missing some stuff on sync.
[Captivate Android Development] mnjm9b:
****....now that i completely wiped and restarted i am only getting 312???
[Captivate Android Development] boog:
Now I see what your talking about!

I am only getting 312 as well. did you have to edit some of your .repo/ files? I was getting some server hung up errors and had to change the git:// to https://

I wonder if that is causing the problem? Did yours sync properly after nuking it? Did you nuke your entire folder, or just everything but the .repo folder?
[Captivate Android Development] juliobahar:
There is no way to incorporate Viber into CM7 SIP. VIBER uses its own proprietary VOIP technique, which I don't know. Fring on the other hand works fine btw.
[Captivate Android Development] makelegs:
https should help out quite a bit.
[Captivate Android Development] makelegs:
Was afraid that might be the case. I guess I just don't relate to the "need" by some for Viber.
[Captivate Android Development] boog:
It did.

Could you post your default.xml? I would like to see the difference, and what we are missing.
[Captivate Android Development] fatbas202:
Hello,

I was wondering if the Jan 10th build has LED Notifications enabled and if so, where the heck can I turn them on? I'm running Glitch 13.1, which has support for said notifications.

Thanks!
[Captivate Android Development] MaxRabbit:
Should be enabled by default if you have the application set to light up LEDs.
[Captivate Android Development] mnjm9b:
where are you syncing from???

I am using:

repo init -u git://github.com/CyanogenMod/android.git -b gingerbread
[Captivate Android Development] boog:
I think your question is directed to makelegs, but that is what I am using too.
[Captivate Android Development] mnjm9b:
nvm...I think I figured it out.... I will let you know if I am right in a bit...
[Captivate Android Development] makelegs:
GIGGITY!!!

What have we, here???
[Captivate Android Development] JiroPrinz8:
Hmm.. i don't see a new build so I'm guessing one should be uploaded soon..?
[Captivate Android Development] mnjm9b:
yep...I figured it out...

syncing the repo doesn't fetch the new samsung proprietary file

for the tv-out. which was crashing the settings app without it.

so while I was waiting for the repo to sync yet again...

I tried manually copying the new libtvout_jni.so file directly to my phone.

and guess what....

no more FC !!!!!!

I have yet to actually try the tv-out....but that will wait till tomorrow.

here is the file if you need it....unzip and put it in /system/lib/
[Captivate Android Development] makelegs:
Nice!!!! :)
[Captivate Android Development] Gromlakh:
*sniff sniff*

I...smell...BACON!!!!!!!! :D
[Captivate Android Development] makelegs:
Bacon-wrapped bacon, fried in bacon grease....and served on a bed of bacon :D
[Captivate Android Development] boog:
So, I am guessing that this should also go into vendor/samsung/aries-common/proprietary to get it built in?
[Captivate Android Development] mnjm9b:
There also needs to be a line added to aries-vendor-blobs.mk

So it depends how you get those files in the first place...

If you are using the scripts in the device folder then those have been updated to pull the needed files.

Or if you download a set from say github then re-sync to that.

(I got mine from koush)
[Captivate Android Development] Time_Zone:
I went with Yellow. Thanks for this!
[Captivate Android Development] MaxRabbit:
Hey, makelegs, thanks so much for all your work! I'm moving on to an SGS2 but I always loved your Kangs :)
[Captivate Android Development] makelegs:
Nice device! I'm sure we'll meet again. Pretty sure there's already an sgs2 skanky build ;-)

Sent from my Galaxy Nexus