Got it flashed and my typical setup all worked out. Seems to run about the same as AOSP's build but of course will have to run it more.
Sent from my HERO200 using XDA App
yes, ive been waiting for this for a long time! now a true cm7 rom for the heroc ok, enough ranting. i suppose that backing up my current install of aospCmod would be a good idea. ill go back to that if things dont work well for me with the nightly 3.
question: why is it called nightly 3 when its the first one? were there 2 private nightlies?
From what I understand of the CM build environment, it increments the build # (nightly number) for each build, even if they fail. Since there's no "nightly 1" or
"2", I'm guessing those failed, and 3 was the first successful one.
Edit: usually, you could check buildbot.teamdouche.net for a history of this, but it's not public right now for whatever reason.
From the initial commits that Darchstar submitted, it's Decad3nce's kernel source/configuration (when you flash the nightlies, it will say ameer@darchstar #1 for the kernel name) - this is an uncapped kernel config, but will be set to 691 max by default.
Thanks to Jaybob for picking up the torch on this!
So if I have been flashing Deca's 691 kernel to use CW 2.5 to run aospCMod, theoretically with the CM7 nightlies I can do without flashing a capped kernel.
(That was a giant sentence.)
Should work fine, yep! My hero can't go to 768, and is overall shakey above 691. I've had no problems with the prebuilt kernel in darchstar's heroc device tree.
Effe yeah! Does anyone know if "lack of space" problem on AOSPGBMod from 2/18 appears in this rom?
isecond that! Think I'm gonna keep them both for awhile! Can we flash over new nightlys like we do with AOSP?
Well guys, it's a sad thing to have to say, but I've finally made the decision to move on from the Hero. Currently, I now own an EVO 3D and loving it to pieces. The Hero has been a ridiculously resilient phone. What's been done with it is nothing short of incredible. It's gone through and will probably continue to go through every version of Android that we've thrown at it.
It's been a great deal of fun being at this section of XDA, but now I must take my leave. Thank you to everyone who made my phone experience what it was.
The links in this thread should remain accurate with no need to change them, but I will not be updating it when major versions come out or if RCs come out.
So I guess it's mediaserver (/system/bin/mediaserver) that's stalling after a while, looks like something with the cache? Anyway, a quick and very dirty temporary workaround without rebooting the phone is, as root:
killall mediaserver
Edit: not to worry, the service will start itself back up automatically.
yes
or you can do it adb style
adb shell
killall mediaserver
edit: someone can even probably make a one click apk that will run that shell script (not me though )
Here is how its different
These are OFFICIAL nightly builds as part of OFFICAL cm7 also with nightly builds we will get newer commits every night hence the term nightly
aosp has done great work but he hasn't made his tree available so cyanogen wants no part of his work nor does aosp want to share
Sent from my PC36100 using XDA App