yashsingh1/xdaforums huggingface dataset:
[Captivate Android Development] mcala:
Love the new fonts. Noticed the boot animation is back to cm7 default. Running great!
[Captivate Android Development] makelegs:
Ohhhhh ****!!!

Totally forgot

to add back the boot ani! :mad:

That was the first build on a brand new system. I knew I was forgetting something! :eek:
[Captivate Android Development] mcala:
Lol, it's cool!
[Captivate Android Development] Gromlakh:
I flashed today's kang over top of the last nightly (181). Had a few issues when everything got up and running. First flash I booted up to wifi errors. Nothing specific, wifi just wouldn't start and said "Error" in settings. So, I reflashed twice.

Both times I reflashed I was getting some kind of issue related to Google. Every time I would boot up, it would ask me if it was OK to use Google's location data stuff. I'd click yes, but on the next reboot it would do it again. And again. Also, Market wouldn't load. If I tried to launch it from a shortcut, it said it wasn't installed. I tried uninstalling/reinstalling (both with and without data), and it still wouldn't load. After the third flash, I gave up and restored my last Nandroid from nightly 181.
[Captivate Android Development] mcala:
Seems to me you formatted all data & cache instead of just cache & Dalvik. All you had to do was to install gapps again to get market back. You don't need to do a full wipe everytime you update/upgrade. I'm assuming that's the problem.

Did u check the md5sum to make sure the zip was not corrupt?
[Captivate Android Development] makelegs:
Hmmm.... I flashed it on the only cappy I have access to, and it worked just fine. Wifi and everything. Sorry to hear, man.

Pro-tip:

If the first flash seems janky, sometimes you're better off just re-downloading, instead of flashing the same file again. "Bad downloads" are not a myth. They just happen sometimes.

EDIT: Don't wipe anything unless you have to! Ever! You'll know if you need to....
[Captivate Android Development] Gromlakh:
Hmm...no idea what the problem is then. I don't ever wipe data when installing nightlies/kangs. I routinely wipe cache/dalvik, which I did this time. Not that it mattered, because the Glitch installer wipes both anyway, but whatever. I also checksum'd the zip file; it all checked out just fine.

Reinstalling Market wasn't the problem. I could reinstall it just fine (both from TiBu and from the .apk file I have on my internal SD card); it just wouldn't open once I did it.

I'll try one more flash, see if it works out. If not, I'll just wait for your next build.

EDIT: No dice. Did two more flashes, one with Glitch and one without. Same Google error on reboot, same "Market won't open" issue. Meh.

Oh well. Back to 181 until the next Kang is up! :D
[Captivate Android Development] makelegs:
Won't be long at all....like 20 minutes or so.....patching the boot animation #fail from earlier. No other (intentional) changes.

:cool:
[Captivate Android Development] Gromlakh:
People like you are bad for my flashing/crack addiction. :P
[Captivate Android Development] makelegs:
Doing my best to bring everyone else down with me!!! :D
[Captivate Android Development] Gromlakh:
Progress:

Flashed the new release; same Google error. I tried messing around with uninstalling/restoring the various Google apps to no success. I opted for mcala's suggestion of reflashing the gapps package; that did the trick. Google stuff now works correctly. From there I could reinstall my updated Market and it seems to be running fine.

Only thing that I'm not seeing is the custom boot animation that I kept reading about. I see bootanimation.zip sitting in /system/media, but when I boot I'm just getting the standard CM7 boot animation. Is there another file I need to move over and/or something else I need to do to get your boot animation working, or is something amiss?
[Captivate Android Development] makelegs:
I prolly just messed the boot animation up. Oh well. I'll fix it later
[Captivate Android Development] mcala:
Theres nothing you need to do. Just sit back and wait til it gets fixed. Updates are frequent here.
[Captivate Android Development] JiroPrinz8:
I have a confession, i flashed a KK4 ROM in the hopes of getting beter battery life. :eek: Well indeed battery life is great but, damn i miss my KANGs!!!

Please how do i get back to CM7..? can i just flash the backup i made? I'm on GB BLs as I one clicked to a stock rom with bl and cwm injected prior to flashing the KK4.. any suggestions.? :D
[Captivate Android Development] mcala:
Disable any lag fixes/ext4 and flash the latest Kang. If it was me, I would format all data while in CWM. Make sure you have the latest V13 Glitch kernel also. After flashing back to CM7 you might boot loop as it tries to change your version of CWM, just time it right with a 3 button hold & get back to CWM & reflash the zip again. Try your backup if you want. Don't forget to get the latest GAPPS also.

Be aware that the latest Kang is only 26MB. I think it's a patch for the boot animation. Just grab the Kang underneath that's 100MB in size or wait for it to be fixed next update,.
[Captivate Android Development] Gromlakh:
@JiroPrinz8:

You don't need to do nearly that much. Assuming your KK4 ROM has CWM in the kernel (which I can't imagine it wouldn't), just flash any CM7 installer zip. A Kang build, CM7 stable, any nightly, etc. It will reformat all your partitions (including data, wiping it for you) and put you back on the CM7 partition structure. You mentioned a backup; assuming that's a Nandroid backup (a "backup" from CWM), yes, you can go ahead and use the restore feature in CWM to restore your backup once you're back on BML/MTD.

The latest Kang build is not 26MB; it's 96. If you downloaded and only got 26...you got a bad download.

Oh, and I noticed you mentioned flashing back to stock "with bl and CWM." There's no need to flash bootloaders, ever. You're on the Captivate GB bootloaders now, so stick with that. If you ever decided to go away from CyanogenMOD again, make sure to flash a package WITHOUT bootloaders. A failed flash of bootloaders is one of the few ways you can hard brick your phone and render it completely unusable. As long as you're not flashing bootloaders, you should always be able to recover your phone from at least download mode.
[Captivate Android Development] mcala:
There was a 26MB build last nite around 2:00am est, it has quietly disappeared. Just helping out.
[Captivate Android Development] JiroPrinz8:
@Gromlakh

Thank you for the very informative response..! That answered a lot of my questions. I'm currently on another KK4 build, gonna try this out a lil bit, now that i know i can simply flash back to CM7 anytime.. btw, TiBu has been a big help on all of this, but isn't there a way for it to install the apps on its own? I have to manually click install app and click done after, for each of my 60 apps.. it's kinda annoying... lol
[Captivate Android Development] Gromlakh:
Glad I could help.

Yes, there is. Buy the premium version. ;)

---------- Post added at 10:05 AM ---------- Previous post was at 09:12 AM ----------

Boot animation issue solved: I downloaded one of your earlier Kang builds, unzipped it, and copied the bootanimation.zip file from that into my current /system/media. Worked like a charm. ;)

Oh, and everyone was right. That IS a pretty sweet boot animation!
[Captivate Android Development] Thunder22:
Can I solely flash gb bootloaders I am on glitch v13 and the latest kang but have froyo bl's???
[Captivate Android Development] Gromlakh:
Yes.

omg10char
[Captivate Android Development] mcala:
Yes you can but why? They are not necessary but to each his own. Check the sticky thread From ILLUMINATEDone. He has a thread with all the links you need. Find an Odin for GB bootloaders only. Be very careful, you can brick your phone!
[Captivate Android Development] Raul77:
speaking of Bootloaders, how can you tell the version of bootloader you got? if i am running the latest KANG am i guaranteed to be running GB bootloader?
[Captivate Android Development] Gromlakh:
The CyanogenMOD installers (stable/nightly/kang/etc) don't flash bootloaders; nothing you can flash from CWM does. Bootloaders can only be flashed from Heimdall or Odin in download mode.

I'm not sure there's an easy way to tell what bootloaders you're using. Have you ever flashed a Heimdall or Odin package that included bootloaders? If not, you're probably still on the Froyo/Eclair bootloaders since that's what came with your phone. If you've ever run any Samsung GB ROM (e.g. not CM/MIUI based), then you can be certain you're running GB bootloaders, because the Froyo/Eclair bootloaders can't boot Samsung GB ROMs.
[Captivate Android Development] Raul77:
Thanks for the reply, now i understand, now to my next question, does the bootloader play any role in how stable the phone runs? I got my phone on 2.1, flashed to CM7 right away, nothing else. should i get a GB bootloader on?
[Captivate Android Development] RichMD:
FWIW - I know that if you ever flashed the I9000 BLs then the recovery and download button combos are different. The I897 GB and Froyo BLs are the same.

Also, technically you CAN boot a SamSung ROM on Froyo bootloaders but the screen will be messed up - not sure how much.

Once the phone is booted then the BLs should have no effect on stability. I know that on some SamSung GB leak ROMs the only difference between I9000 and I897 BLs was some problems with the music player, etc. I "think" that related to using the buttons (vol up/down) before the screen is even unlocked but I'm not sure. There was a lot of speculation about which were better but I don't think anyone ever found any real difference after bootup other than an app or two like the music player.
[Captivate Android Development] apbthe3:
There's no reason to risk it. Like RichMD said, there's really no advantage until you upgrade to a GB ROM.

i897 bootloaders will have the AT&T initial spash screen and i9000 will have a black i9000 initial splash screen. All of the i9000 GB bootloaders kicking around are GB, but there's no good way to tell the difference between Froyo and GB i897 ones.

I would hold off until you first install a GB ROM. Flash the i897 GB bootloaders then, then never flash them again because they're compatible with everything.
[Captivate Android Development] makelegs:
OK guys.... I've been having all sorts of trouble, but I think stuff is finally working correctly, again. :eek:

New build is up. Boot animation works on my device build. Should work on cappy kang, too.

Could someone please confirm the status of the ICS fonts on the newest build?

Thx :cool:
[Captivate Android Development] RichMD:
I thought I smelled bacon :D I will flash it in the morning and let you know. What's up with the CM7 nightlies BTW - is the buildbot seriously broken?
[Captivate Android Development] makelegs:
Honestly, man...... I haven't kept up with CM nightly builds for any device in about a year. I couldn't begin to even speculate. In fact, I didn't realize they were even down. 0.o

#kangalangalang :D

PS: how can you get any meaningful rest with a rom to flash??? :eek:
[Captivate Android Development] Raul77:
just flashed to the latest, boot animation working on Captivate, so does the ICS fonts.

great job.

Cheers,
[Captivate Android Development] makelegs:
Thanks for the confirmation!

For some reason the ICS font doesn't wanna work on my N1, so I wasn't sure about cappy. But I've been breaking and fixing ****, left and right, for 2 days! 0_o
[Captivate Android Development] sixstringsg:
One of the harddrives on the buildbot broke, and the maintainer hasn't had time to replace it yet.
[Captivate Android Development] bearnakedbrew:
I too am guilty of flashing a kk4. I need to come home. So much lag!!!
[Captivate Android Development] mcala:
Has anyone noticed if they loose connection to Google after the phone comes out of sleep? Every time I get on the phone while connected to wifi the signal bars & wifi bars are white. After a while they turn green. I can surf & get texts, if I go to gmail they turn green right away. Not sure if its Kang, wifi or kernel related. Hell, it might just be my router, I just updated the firmware. Will try turning off wifi to see if I loose connection to Google servers.
[Captivate Android Development] bearnakedbrew:
I've been receiving complaints about bad sound quality. Is this common with cm7? I tried the kh3 modem and same affect.
[Captivate Android Development] apbthe3:
Try an i9000 modem. Some people swear that i897 modems work fine on CM7, but it definitely sounds static-y on the receiving end for me.
[Captivate Android Development] airtower:
I've had that problem. Wifi sleeps and when it comes back on it takes a sync event to "reopen" the connection to the google mothership.

Turn off wifi, or set the sleep policy to never (and watch your battery die). FWIW, I don't see this problem on ICS.
[Captivate Android Development] mcala:
Get back on the stock JL3 I9000 modem & the crappy static & sound will disappear! I ran all the I897 modems & they all do it.
[Captivate Android Development] mcala:
At least I'm not alone. Now I do have wifi sleep policy on "never" but it still does it. I turned off wifi & I took a nap, it never lost Google connection! So it's either these newer CM7s or my router's newer firmware cuz it never did this on stock CM7 #181 nor these Kangs prior to the 26th of Nov.
[Captivate Android Development] bearnakedbrew:
The jl3 didn't sound good either. Scored with a jk4 though. I didn't know I could flash i9000 stuff on i897 bootloaders. Obviously I'm wrong.
[Captivate Android Development] mcala:
They are just modems not roms.
[Captivate Android Development] apbthe3:
It's not a bootloader issue, you can run anything on i897 GB bootloaders. It's kernels you are thinking about, and CM7 uses an i9000 kernel (or something closer to i9000 than i897 anyway). Most of the GB ROMs are i9000 based because there is no official i897 source code yet.
[Captivate Android Development] bearnakedbrew:
Does this just apply to cm7 or is it all roms? I only ask because its been beaten into my head that the aren't compatible.
[Captivate Android Development] sixstringsg:
Does what apply to all ROM's? He had a few statements in that post. I can probably answer your question though.
[Captivate Android Development] boog:
The bootloaders shouldn't matter (well, you need gingerbread loaders to run samsung gingerbread), but for kernels, you run an i9000 modem/kernel combo, or an i897 modem/kernel combo. mixing them will create the static problems.
[Captivate Android Development] bearnakedbrew:
I was confused that we could flash elements (modems for example) from both the i9000 BL and the i897 BL. Gingerbread of course. Is this something specific about cm7 or is it all roms? Like if I'm on Fusion kk4 and flash a i9000 JK4 modem. I'm sorry if this is too unrelated to the thread.

---------- Post added at 10:42 PM ---------- Previous post was at 10:39 PM ----------

I'm so confused but I understand, cm7 being closer to i9000. Thats why my i897 modem sucked. Thanks for being patient guys.
[Captivate Android Development] boog:
We have all been there at one point. I have also gotten so excited to try something, that I ported an i9000 kernel to one of the i897 gingerbread leaks, then remembered the issue right as I got my first successful boot.

And back on topic, I guess I could try porting the kernel to my personal kang.

And why is building/flashing daily so addictive? And I still haven't figured out how to cherry pick things (well, I haven't tried), I need to study git.
[Captivate Android Development] RichMD:
Just to avoid confusion, I don't think Boog is suggesting to ever run a "true" I9000 kernel on a Captivate - that will cause autorotation and softkey mapping problems. I assume he means an I9000 kernel that is "reoriented" for the Captivate which means the autorotation will work and the softkey mapping works. Most of the SamSung ROMs on XDA for the Captivate are a port from an I9000 based ROM. There are a few (Cognition, etc) that are actually based on Captivate leaked GB and the kernel was truly designed for a Captivate so it has audience chip support (the I9000 lacks it) but you have to use a Captivate modem (and ROM) with it or you will have problems. I think that is where the confusion is coming in - A SamSung kernel designed for the I897 (Captivate) expects a modem designed with the audience chip to be paired with it. I think it is a kind of encoding - there are hardware (Captivate) and software (I9000) methods.

For CM7, there is no audience chip support in the kernel (I believe).
[Captivate Android Development] sixstringsg:
Cherry-picking is super easy. It gives you the command on gerrit (review.cyanogenmod.com) I can give you a walkthrough if you want sometime.
[Captivate Android Development] makelegs:
Speaking of cherry picks....

Grabbed a couple new picks for the upcoming build. Nothing earth shattering, but more is always better, right? :cool:

Keep an eye on twitter for build announcements :D

(last night's kang made it up to

over 120 dl's!

that's the record so far....might be time to bring in the vibrant and fascinate boys/girls!)
[Captivate Android Development] Gromlakh:
Maybe I missed it, but is there a changelog or something where you've listed what you're cherry picking for each release?
[Captivate Android Development] sixstringsg:
http://fitsnugly.euroskank.com/gigglebread/captivatemtd/

Over on the right.
[Captivate Android Development] mcala:
Its located at the Kang download site, look to the right.

EDIT:

He beat me to it
[Captivate Android Development] n0stalgia:
Any way to get a green MIUI battery bar without switching to androdian?
[Captivate Android Development] Gromlakh:
Herp derp...

My screen cut off EXACTLY after the "Date Modified" column and I didn't see the slider...
[Captivate Android Development] bearnakedbrew:
You guys are amazing! Thank you!
[Captivate Android Development] sixstringsg:
The MIUI battery bar color is controlled by the theme. All of the themes need to be updated to take advantage of it if I understand correctly, which likely won't happen until it gets officially merged.
[Captivate Android Development] codeblue315:
Awesome! Giving these KANG builds a try for the first time, gotta get my flash fix while the CM7 nightlies are still down. :P
[HTC Sensation] kpf16:
Ok so I got a sensation off eBay and its on orange unlocked to any sim. I root and s off and flash a stock HTC Rom great.

1. How can I unroot to get back to original hboot but with stock current Rom for HTC sensation as if I brought sim free with out orange bloated stuff.
[HTC Sensation] kpf16:
I know you might think I am mad to want to un root but this is because I want to just get read of the orange stuff. If the flashed Rom is stock HTC will I get ota updates like everyone else would normally?
[HTC Sensation] piimp:
Go read the stickies in the dev section..

Sent by my feau gee
[HTC Sensation] kpf16:
So to make it easy my question is if I am rooted with a stock Rom will I get ota updates or not?
[HTC Sensation] moto211:
You can have s-off and stock ROM without root. S-off and root are not the same thing. Also, I believe you can be s-off with unrooted stock ROM and get official OTA's if you have the stock recovery. And to more directly answer your question, if you are running a rooted stock ROM (with stock recovery), you should be able to get OTA's but they might break root. That would be an easy fix since you would retain s-off and could just flash cwm and use that to flash su.
[HTC Sensation] kpf16:
Stock recovery meaning nandroid back up of a stock rom?
[HTC Sensation] EddyOS:
If you want to go back to 100% but unbranded, you need to:

1. Write Super CID to the phone (see the S-Off guide in the Dev forum for details)

2. Flash the RUU you wish to use (either 1.45.401.3 of 1.73.401.4)

3. Write the stock CID to the phone (stock = HTC__001)

4. Then S-ON, again using the S-OFF guide

The phone will now bee 100% stock and unbranded. I'd personally stick to the non-XE ROMs as the OTA's will work without issues, can't comment on the XE RUU
[Verizon Droid Charge] juanzr1:
I want to send some to a buddy using root explorer but I can't find them anywhere

Sent from my SCH-I510
[Verizon Droid Charge] Bfitz26:
Use his phone sign in download them done.
[Verizon Droid Charge] juanzr1:
Any other way?

Sent from my SCH-I510
[Verizon Droid Charge] juanzr1:
There's no way to sign out anyways

Sent from my SCH-I510
[Verizon Droid Charge] Bfitz26:
Download app saver and save them to sd card put your ad card in save to his phone
[Verizon Droid Charge] Dalamar1320:
Amazon apps WON'T work unless signed into the Amazon app store anyways.

I just sign in on my wife's, daughter, and friends phone and tell then not to buy anything lol. Amazon supports like 20 devices on your account anyways.
[Verizon Droid Charge] Bfitz26:
Or you could download it then change the password
[Verizon Droid Charge] juanzr1:
Thanks guys

Sent from my SCH-I510
[Samsung Epic 4G Touch] xgimpster:
I've had a E4GT for a few months now and have had no issues. Been trying out different ROMs since day one: midNIGHT, Starburst, Calk's, etc.

Recently (as in the last couple of days), everytime I lock the screen, it turns the phone off, and I need to boot the phone up again.

At first, I thought it was a problem with the ROM (Starburst 1.9.5 at the time), so i updated to 1.9.8r and still had a problem. I then moved over to Calk's ROM v1.1 and it's happening more and more.

Any suggestions? Is it a problem with the ROM or a certain application/script? T__T
[Samsung Epic 4G Touch] lballer69:
Your phone is going into the sleep of death the undervolt scripts or your own personal setup is to low for your phone causing it to not wakeup , ok if your on calks rom he has a flashable zip for stock voltage try that i should be ok

---------- Post added at 05:22 AM ---------- Previous post was at 05:19 AM ----------

flash the stock mv settings

http://xdaforums.com/attachment.php?attachmentid=773923&d=1320602404
[Samsung Epic 4G Touch] scottspa74:
Damn, so ET4G is where calk went? That Guy is the ****.
[Samsung Epic 4G Touch] xgimpster:
I did that and the sleep of death is still gripping my phone. :(
[Samsung Epic 4G Touch] demonlordoftheround:
Are you using the for four tab lock screen? I thought I read that one was causing problems.

Sent from my Epic 4G Touch
[Samsung Epic 4G Touch] xgimpster:
no I'm not. just a normal pattern lock. I'm going to try and use a different rom tonight to see if anything happens.

this doesn't happen all the time. sometimes there are times when it doesn't happen all day but then does the next.
[Samsung Epic 4G Touch] nacron:
The screen on my 20 day old E4GT started flickering and had gray alternating lines down the screen but strangely only from the taskbar down. If you rotate the clear part stayed on the same part of the screen. Took it to sprint...hopefully I get a new one. Rocking my vibrant for the evening.

http://www.youtube.com/watch?v=uFzUx8my7SM
[Samsung Epic 4G Touch] lballer69:
i looked @ your setup ,where you overcloaked ..........looks like it overheated .......next i would suggest a different kernel
[Samsung Epic 4G Touch] nacron:
I was running it at 1.2
[Samsung Epic 4G Touch] lballer69:
Hmmmm defective unit
[Samsung Epic 4G Touch] wase4711:
and, after 20 days, refurb is the word, so don't expect a new one
[Samsung Epic 4G Touch] AestenD:
And in a couple weeks someone else will get his phone as a refurb! :D
[Samsung Epic 4G Touch] graffixnyc:
Not necessarily true. I got a replacement a couple of weeks ago for my device which I had a few days after launch. My replacement didn't come in the retail box but it was not a refirb. I confirmed this by running a qst code (I forget off the top of my head) and there is a "reconditioned" field that will either say yes or no. But that was a few weeks ago and maybe by now they do have refirb units available. I lucked out though :-)

Sent from my Samsung Galaxy S II Epic 4G Touch
[Samsung Epic 4G Touch] Beejis:
Just got a replacement myself and it's brand spanking new. Just checked ##786#