yashsingh1/xdaforums huggingface dataset:
[Captivate Android Development] Nick D:
I've tried changing numerous times and can't find a way around the sleep deaths. I'm usually limited on time when I try getting it conquered but last time I got as far as installing cm9, installing glitch 14 (first time I tried it, stock crashed within an hour), finding glitch didn't help, and trying to adjust the OC/UV. I made one adjustment to voltages, bumping up 100mhz by 25mv, and it went into boot loops. It would boot all the way into cm9 and reset, so during one reboot I jumped into NStools and turned off the apply at boot. It stopped looping but tied a short while after. I gave up and Nandroid'd back to cm7.

So I hope cm7 isn't really dead, per se, since I'm slightly stuck, but at least I've got the old builds to hang onto. Any ideas what I should try next to get to cm9?
[Captivate Android Development] billyjed:
Try setting minimum frequency to 200 mhz. That did the trick for me. Using glitch v14 b6 with the latest nighty right
[Captivate Android Development] Nick D:
That was going to be one of my next steps and ran out of time. Does that burn through battery like mad? Seems like it would but I haven't read up yet. It seems that if the problem was sleep death then the lowest frequency wouldn't matter as much as whatever puts it to sleep or wakes it up.

Obviously I'm still learning OC/UV and all that.
[Captivate Android Development] boog:
Doesn't seem to kill the battery for me, but setting the min to 200mhz sure appears to fix the sleep death, and it still goes into deep sleep, according to cpuspy.
[Captivate Android Development] Nick D:
Downloaded and am installing the latest nightly as of 6AM today, and going to lay glitch v14-b6 over top of it. 200mhz minimum once I'm up and running and I'll see how things go from there. Thanks, guys!
[Captivate Android Development] makelegs:
#BACON

Ok....so I got a lil more rowdy with cherry picks, today. Got rid of the "electron beam" stuff that was thought to have been irritating some users who mess with screen colors. Added a bunch of stuff that wasn't in there yesterday. If anyone notices any obvious problems, please speak up.
[Captivate Android Development] makelegs:
.....sizzle

New skankwich cooking. Lots of merged picks. Threw in a few new cherries.

Bacon is served....in about 5 min. :D
[Captivate Android Development] Nick D:
I set it up as listed and the phone did better. Then the next morning the phone was dead and I missed an alarm. Back to cm7 I nandroided, but I did nandroid cm9 first so I can start where I left off. What should I try next? Captivated keep alive helped on stock gingerbread but I haven't needed it on cm7. Maybe I'll bring it back on cm9 as much as I hate to. I'll likely be testing intermittently with so much going on at work. Gotta have a reliable daily driver.
[Captivate Android Development] makelegs:
I would delete your cm9 backup, wipe like crazy, and try again. Make sure your using newest gapps. Maybe run stock for a bit. I assure you it's daily driver ready. There were times I had similar issues even with cm7. It always meant time to start clean.

#lifeofacrackflasher
[Captivate Android Development] makelegs:
Weird!

Over 500 DL's in 12 hours and not one single complaint??...(yet)

Is my data connection even working??? :D
[Captivate Android Development] billyjed:
No issues here.
[Captivate Android Development] makelegs:
That's what I like to hear! ;)
[Captivate Android Development] hayslett4:
I was hoping to see the random reboots stop with the 04102012 nightly, but I just had to pull the battery and restart. I can't run a logcat since I don't have a computer with me, but its been doing this since the 04042012 update. Not sure how to help, but wanted to bring it up. I haven't changed the kernel or anything other than applying the update. I did try to fix permissions and installed the latest gapps.

Update: Its been about 24 hours after installing Glitch and no reboots, no wipe, and running smooth at 1.3 GHz. So far so good.

Sent from my CM9 Cappy
[Captivate Android Development] makelegs:
Did you wipe when you flashed the new gapps???
[Captivate Android Development] hayslett4:
No. I'm going to try glitch and see if that helps... I installed NSTools and set my min CPU to 200. I did a full wipe prior to jumping from CM7, but haven't since then.

I can do more tomorrow once I get back home. I'll do a full wipe and reflash the latest nightly and gapps... then glitch if the reboots continue... trial and error... not a problem.

Update: It's been 2 days since flashing Glitch after the 04102012 nightly and no reboots. I'm running at 1.4GHz without any issues.

Sent from my CM9 Cappy
[Captivate Android Development] makelegs:
Public Service Announcement:

Wipe BEFORE flashing the 3/17 gapps!!!
[Captivate Android Development] boog:
Actually, I think it might be building now. ran make clean, then make clobber, and it is acting better, just taking forever to build.

Still interested in cherry picking though :D
[Captivate Android Development] makelegs:
*innocent whistling*
[Captivate Android Development] shaolin95:
mmmm and that means? :-)
[Captivate Android Development] makelegs:
That meant... MOAR BACON! :D
[Captivate Android Development] JiroPrinz8:
Did you say bacon..?!?!? Where where..?!?!? *panicked breathing*

Lmao!!!

Sent from my *Glitched CM7 Captivate
[Captivate Android Development] makelegs:
Always in the usual spot! ;)
[Captivate Android Development] JiroPrinz8:
Wow, talk about slow, I'm still on the 1117 build!:eek: I can't believe I missed 2 builds already! Oh well.. Time to flash!! :D
[Captivate Android Development] makelegs:
Do it NAO!!!! :eek:
[Captivate Android Development] anishz:
Downloading and doing it NAO! Thanks!!

I wanted to ask one thing, i have done a batt. mod in uot, do i have to flash it after every update, or is there anyway to make it stick. Because everytime i flash nightly i have to reflash it. Also same holds true for statusbar, bootanimation or other mods.
[Captivate Android Development] makelegs:
Not sure what all mods ur talking about. If you are using an alternative boot animation, then ur probably just putting it in the wrong directory. If you are flashing some other mods, then you may very well need to continue to flash them with each ROM flash. Just like with kernels and other various flashables. I assume that has been the case for you with other ROMs as well, no??
[Captivate Android Development] anishz:
Yes that's been the case and its irritating to do it every night so i was hoping for some workaround. Thanks, guess i will have to continue.

Also one more thing, is it possible to change the splash screen from the awful At&t screen to anything.
[Captivate Android Development] sixstringsg:
Splash screen is possible, but it requires being on stock froyo or gingerbread, and requires Bootloaders. I'm not sure about the bootloader part, but I am sure about the stock part. There are threads for it around.
[Captivate Android Development] JiroPrinz8:
Flashed the latest KANG, and everything seemed ok, but then after playing with it a bit, found out that my home key doesn't work, I mean it doesn't do anything. Haptic feedback is there, but the action doesn't happen.. tried with both v12 and v13, same thing.. lost.my.messages too.. any ideas..?

Sent from my *Glitched CM7 Captivate
[Captivate Android Development] shaolin95:
Well I can confirm that both messages and v13 are fine for me. Perhaps restore your back up and try again?
[Captivate Android Development] JiroPrinz8:
I'm at work atm, yep I did restore my stable backup which is 11.17 kang with glitch v12.. maybe I'm doing something wrong? Here's what I do:

Wipe cache/dalvik cache

Flash latest kang

Reboot phone

Reboot again to recovery

Flash glitch v13

Reboot.

Something I else I should be doing..?

Sent from my *Glitched CM7 Captivate
[Captivate Android Development] shaolin95:
I normally wipe dalvik and cache partition after flashing the nightly too just in case. Then I let it boot and wait about 10 minutes for everything to load correctly.

Then finally flash Glitch.

May want to redownload the files too just in case.
[Captivate Android Development] JiroPrinz8:
Will do that.. ill let you know how i go.. thanks bro.. :)

Anyway all in all still loving the kang+glitch combination!

Sent from my *Glitched CM7 Captivate
[Captivate Android Development] shaolin95:
Hope it goes well for you...I like these Kang builds :-)
[Captivate Android Development] airtower:
Throughout hundreds of nightlies, I've always flashed the ROM, kernel, and everything else in a single recovery "session" without a reboot in between. Never had an issue.

Home button issues make me think i9000 kernel. Shot in the dark but are you positive you have the right kernel for the captivate?
[Captivate Android Development] JiroPrinz8:
I'm pretty sure I have the right ones, but it never hurts to check, right? so yeah I'll download fresh files to make sure..

Sent from my *Glitched CM7 Captivate
[Captivate Android Development] billyjed:
Is that wipe before flashing them the first time or every time?
[Captivate Android Development] makelegs:
Just the first time! :cool:
[Captivate Android Development] Nick D:
Frustrating thing is that the last few installs have been from a completely wiped state. It doesn't seem to make a difference. Last time was a complete wipe (cache, dalvik, factory reset, and wipe of /system, not necessarily in that order) and ran stock for a short period. In just a few hours it was dying in sleep. That's when I went to glitch to see if it helped. Running glitch at 200mhz kept it alive for the rest of the day but it died overnight anyway.
[Captivate Android Development] makelegs:
When in doubt....wipe > flash ROM > gapps......use stock for a while. If SOD, either raise lower voltage, our raise min freq...or both? The only cappy I have contact with is running all stock, with no complaints. And trust me....I'd hear about it!
[Captivate Android Development] makelegs:
"Support for emojis" on the MMS app...???

Ummm....sign me up!
[Captivate Android Development] Nick D:
Fresh install today. First go round I installed my usual programs only. Titanium backup (but hadn't used it yet), lookout, tasker, llama, amazon app store and gentle alarm. I let it run awhile and got SOD. Had a moment of realization and did another wipe. Right now I'm running a clean install with no additional apps. I've not had a reboot in a while and I'm wondering if it wasn't an app incompatibility. I guess I'll add them one at a time and see what happens.
[Captivate Android Development] makelegs:
Sounds like you're on the right track! :D
[Captivate Android Development] makelegs:
I hope you guys download the **** out of the new build.....cuz it's been 3 days of banging my head against the wall just to get captivate to even build.....

#notpissedatall

/sarcasm

:eek:
[Captivate Android Development] mcdroid:
I have been installing your builds as they have come out and since your ICS builds were started I have not used another ROM. Well done!

Thank you for your dedication!
[Captivate Android Development] makelegs:
Glad you enjoy them 0/*
[Captivate Android Development] makelegs:
Updates to CM9 and CM7 are available, now...

I can't imagine why people still use CM7, but I'm trying not to bail on fascinate users, while it awaits an official CM9 merge, so I figured I'd build all three...this time.

For those of you who insist on using CM7.... Y U NO UPDATE TO CM9??? :p
[Captivate Android Development] billyjed:
I love bacon flavored ice cream sandwiches!
[Captivate Android Development] Nick D:
Still stuck with sod issues on cm9. I miss my desk job where I could be working on my phone all day. Ha! Thanks for the latest cm7s. I'm running the 0408 drop now.
[Captivate Android Development] makelegs:
That's bizarre, dude.

They just overhauled the build process to include inline kernel building (as opposed to using a prebuilt kernel), and I'm not sure if anything in stock kernel actually changed, but it may be worth a try, At the very least, you should be able to raise your minimum cpu speed to avoid SOD.
[Captivate Android Development] visionlogic:
Being that my Cappy is my only phone, and I'm not in a position to acquire a replacement, I will not move to any ICS build until there is a definitive fix for this:

[Guide] Encryption Unsuccessful - Reset Android [ICS Issue]
[Captivate Android Development] makelegs:
Literally hundreds of people have flashed these skanky cm9 builds. The bugs reported to me have amounted to a quantity of 2 or 3 phones. I run the same build on my toro as my work phone, and I seriously doubt that you are more tied to ur phone than I am for work.

Remember....nandroid is ur friend, too. Not like ur gonna break it while trying out cm9.

Justsayin
[Captivate Android Development] visionlogic:
I was happily trying various flavors of ICS, running each one for several days before flashing another, when I ran across the "Encryption Unsuccessful" thread.

If the problem occurs there is no way to communicate with the internal SD. It will not respond to requests at the hardware level, period. You can have all the nandroid backups you want, but you've got nothing to restore them to.

Certainly this problem has happened to only a relative handful of users. But Murphy lives at my house, and I'm just not willing to give him an "in" to my phone.
[Captivate Android Development] azunino:
Still on CM7 because of the encryption bug.
[Captivate Android Development] killer23d:
I think it's a good idea to spend a weekend afternoon to test it.

I have no problems with any Kang, just this one made by makeleg is much better.

I went back to stock 2.2, removed MicroSD, then Master Reset, then 2.3, then i9000 bootloader, then finally CM9 twice. I have a very functional phone as daily driver and battery life is more than awesome compare to CM7.
[Captivate Android Development] makelegs:
I clearly don't understand the problem well. Somebody explain it to me in 30 words or less, so I can be on the lookout for related cherries...

:D
[Captivate Android Development] boog:
Took me a while to get it figured out, too.

Just did an update, and at least for the crespo, it pulled down the kernel source on it's own. Now I am away from home, and will have to wait to test for other devices.

I really need to work on my ssh keys, and make my ssh available to myself from anywhere.
[Captivate Android Development] makelegs:
It's def gonna be a PITA for me to fix crespo.... #techdiff
[Captivate Android Development] boog:
I just had to delete my device folder, I had it all changed.

You building the "stock" cm kernel or a different one?

I'm going to have to find all of the new changes/setting and have a long look at them.
[Captivate Android Development] makelegs:
I haz no kernel skillz. I just build mainline.
[Captivate Android Development] hayslett4:
Bluetooth Commands

Has anyone else experienced a drop in the volume of the bluetooth voice command telling you when to, "Speak Now..." since moving from CM7 to CM9? I've tried the standard CM9 Rom and the Kang builds, and I've tried changing kernels to Glitch. I've tried different settings with the DSP manager and bluetooth settings with the stock kernel, then tried Voodoo settings with Glitch. I can barely hear the voice, but the call volume is fine and I hear every "beep" when I press a button on the headset. I've tried a Jabra headset and now I have the Jawbone. Am I missing something?
[Captivate Android Development] aehlayel:
Viber Blues..

Hey Guys,

I'm having troubles with Viber, I get unidirectional audio.. I can hear people talk, but my audio doesn't get transmitted. No one can hear me.

It's not a network issue, I have other Android phones using the same Wifi network and work properly.

I'm using the latest CM7 Kang, 19042012, but it's been going on for quite a while.

I've tried going to Glitch's 13.1 kernel and I do get the same results, it doesn't work..

Any thoughts on this? Is anyone else experiencing the same?

I'd appreciate any feedback on how to get this working..

-aehlayel
[Captivate Android Development] visionlogic:
Current thinking / nutshell version: for file transfer ICS uses MTP (Media Transfer Protocol), prior versions used UMS (USB Mass Storage). Connect ICS Cappy to PC via USB to transfer file(s) and you MAY have both MTP and UMS simultaneously accessing your internal SD (aka mmc0, aka movinand chip). If so you may have permanently killed it, which will reveal itself on the next reboot.

Sorry, more than 30 words.
[Captivate Android Development] sixstringsg:
I just want to learn how to make it build my kernel inline :)
[Captivate Android Development] makelegs:
Until someone experiences the issue while running my build, it's impossible to take it extremely seriously; especially given the small sample size of reports. I understand the fear of harming your device...but this seems like an avoidable problem, even if it actually is "REAL". I almost never usb my phone to computer. Seems like knowing what the potential "issue" is makes it pretty avoidable.

I sent an email to one of the CM guys. No guarantee that I'll hear back, though.
[Captivate Android Development] visionlogic:
Understood, and I agree. Your skill and builds are much appreciated and not in question. The Google implementation of MTP in ICS is.
[Captivate Android Development] boog:
That was my thinking too. :)

Need to figure out where it calls it. I moded it once to pull a zimage I built, but then they changed something, and it now isn't where I put it.

https://github.com/CyanogenMod/android_build/commit/a682034b7fa19872213264f092182c9bbf9b8d13

Some of the info I found on it. Looks like it should be possible to make it build from any kernel source folder and defconfig.
[Captivate Android Development] makelegs:
Frankly...I don't understand why inline kernel building became such a priority. What was wrong with the prebuilt protocol to begin with? All it did was screw everyone up for a few days and resulted in the exact same build, as best I can tell...meh
[Captivate Android Development] sixstringsg:
It just makes nightlies that much more current.
[Captivate Android Development] makelegs:
how so?
[Captivate Android Development] boog:
The ones working on pushing updates to the kernels only have to push the updates to git, not go through getting the prebuilt zimage merged in.

As soon as a new feature/fix is added to the kernel source you can pull it, just like the rest of the rom, now. :D
[Captivate Android Development] lownox:
For those of you still using CM7.2... like me... here is my latest clean build. No cherry picks.

I have been away for the past month or so.

http://androtransfer.com/center/?developer=lownox&folder=captivatemtd
[Captivate Android Development] makelegs:
I see ur point. I'm not a kernel guy, like you and Six...so I guess my perspective is a bit narrow. :eek:
[Captivate Android Development] YertletheTurtle:
I have experienced this as well. The voice command is barely audible. It has led to some awkward situations...
[Captivate Android Development] lownox:
lownox KANG Builds

OK... I may have crossed over. LOL

There is a clean CM9 build found HERE

Really wishing the epicmtd wasn't such a pita though. Can't even get a stable cm7 KANG built. /cry
[Captivate Android Development] makelegs:
I readily admit that I don't understand or necessarily "believe" in the sdcard mount "issue" that some are concerned about.... However, I noticed that there was recently merged "aries-common: Switch emmc and sdcard". Not sure if it's even relevant. It may not be at all. But it seems like anything that alters the way those 2 are recognized, might contribute to the alleviation of this concern for some of you. Especially since very few seem to have seen this sasquatch...:rolleyes:

Either way....it was merged this morning...so it will be in the new build cooking now.

I DARE you guys to find this issue on your devices!!! :cool:
[Captivate Android Development] lownox:
Uploaded a fresh clean build this morning. Enjoy.
[Captivate Android Development] billyjed:
Just a heads up, if you have apps on sd, move then back to the phone before flashing the 4/22 bulls or they will get lost because of the sdcard/emmc switch.
[Captivate Android Development] Mastamind89:
ICS ROMs seem to no longer work on my phone.

I was on a MIUI ICS ROM and I'm not sure what happened, I'm guessing a short circuit may have occurred. My power button wasn't working properly, I couldn't manually put my phone to sleep and it would wake up after 2/3 presses.

Since the ROM was beta, at the time I figured I would go back to stock since the problem was going on for a few hours....think it was me slightly freaking out, it didn't work. I couldn't even flash any ROMs due to the massive button lag.

After a day or two, the issue let up. I tried another ICS MIUI ROM and it was stuck at the splash screen for about 15mins....I tried CM9 and CWM would just crash.

Have yet to try KANG builds, figured I would give it a shot. How's the battery life?
[Captivate Android Development] lownox:
Breakfast for dinner. Just posted another clean build. Link in my sig.
[Captivate Android Development] billyjed:
Sorry. Whiny post. Please disregard.
[Captivate Android Development] lownox:
Uploaded another clean CM9 build. May pick some cherries for the next one.

androtransfer.com
[Captivate Android Development] makelegs:
New Cherries....

New build is up. Lots of new cherries. I've been working on tf101 builds all week, so I'm sorry that I didn't update captivate sooner.

Hope you enjoy.
[Captivate Android Development] billyjed:
Is anybody else having issues downloading the new skankwich build?
[Captivate Android Development] makelegs:
what kind of "issues"...??

edit: just dl'd to my build box with no problem
[Captivate Android Development] billyjed:
Issues were on my end. Download manager was corrupted. Good to go now.
[Captivate Android Development] billyjed:
Makelegs, great cherries in this build! I am loving it. Extended thumb controls in the browser, customizable lock screen shortcuts, crt animation. Thanks!
[Captivate Android Development] makelegs:
EBA was already native...it just adds the settings part to turn it off, which I find kinda pointless.... but more options = more better! ;)
[Captivate Android Development] makelegs:
NEW BACON

Get it while it's hot!!!
[Captivate Android Development] billyjed:
Amy bacon cooking with the theme functionality that is about to come out?

Sent from a glitchy skankwich.
[Captivate Android Development] makelegs:
As a matter of fact.... :)
[Captivate Android Development] boog:
New cm9 kang is up with the newly merged lockscreen features, and theme settings!

I have also included the tweak from: http://xdaforums.com/showthread.php?t=1621808 by PureMotive that is supposed to increase battery life. Let me know your results, if it seem the same, or improved any.

Download:http://tinyw.in/a8vs
[Captivate Android Development] mbc663:
Thanks boog. Been interested about this htc battery thing.
[Captivate Android Development] boog:
np, not sure how well or if it really does much. I'm testing it on my Nexus S.

The 2 files associated with it are /system/etc/sysctl.conf and /system/etc/init.d/10sysctl
[Captivate Android Development] lownox:
New CLEAN KANGS of CM7.2 and CM9.0 uploaded this morning. Get 'em while they're hot. LOL

CLICK HERE
[Captivate Android Development] killer23d:
Just tested, it doesn't have the option under Settings to swap sdcard and emmc.

Otherwise, works well.
[Captivate Android Development] kalda01:
Recommended Kernel

Is there a recommended stable kernel for this rom other than stock ?
[Captivate Android Development] lownox:
Which rom are you referring to? Thus thread has cm7 and cm9 roms.

I like glitch for cm7(v13) but I haven't tried it yet for cm9 (v14).
[Captivate Android Development] lownox:
Uploaded a fresh CM9 build and a clean CM7 build is building as I post this. :)
[Captivate Android Development] kalda01:
Sorry. I was asking about a Kernel for CM9.