**CM7 Build Thread**

[winner00]

Quick question: With this 2.3.5 build, is it safe to flash directly over #132? Or do you recommend a full wipe?

Its safe to flash over it. I wiped system, cache, and dalvik and it flashed fine and seems to be working fine.

[AlphaMack]

Quick question: With this 2.3.5 build, is it safe to flash directly over #132? Or do you recommend a full wipe?

Its safe to flash over it. I wiped system, cache, and dalvik and it flashed fine and seems to be working fine.

Sweet. Will be checking it out later!

[phonetool]

I'm on it like a fat kid on cake!
Thanks, winner.

- onDroid

[AlphaMack]

OK, so far so good once settled in. The jury is still out on battery life as I'm currently redoing my battery stats.

Is it just me, or does this build start up FAST?

One issue to note: At first, my phone rebooted a few times upon unlocking the screen while plugged in via USB just after flashing 141 and the deprimed kernel. So I went back and wiped the cache and dalvik cache again for good measure. No reboots since.

Maps was used for about an hour with no incidents, using the same settings I previously posted.

Battery life notwithstanding, I'm pleased overall with this build. Thanks winner.

[phonetool]

uh-oh!
I went into the V6 supercharger script in order to test the phone with the script 'unsupercharged', but touching the screen (to scroll) gives me text input at the prompt.
Looks like this:
^[[6-^[[6-^[[6-^[[5-^[[5-^[[5-
I got out of the script with a '17' entry (at first it thought I'd entered '7' and scolded me), and did a reboot, but the second time into the script still gives the weird input.

edit2: Aha! Swiftkey X is to blame. disabled that and have no problems in the script with the stock keyboard.
edit3 godammitsomuch I spoke too soon- stock keyboard also gives weird input, as does the D-button.

Ok- this time through the flash I wiped data and this issue went away. Hopefully the other issues will as well!

[zachdroid]

I've had a very annoying number of lockups and random reboots yesterday and today. It starts with incoming calls going straight to speaker, with no microphone (caller can't hear me).
Still on Winner00 132, with ChevyNo1 1GHz Low Voltage kernel and V6 supercharger 8 (Balanced 3), no swap.

Can't wait for another Winner build! many thanks in advance!

That sounds like a kernel related issue. Have you tried another kernel? Deprimed is recommended by winner. Also, I use a different minfree setting and have great results. Minfree can often be responsible for hot reboots. Hot reboots are a result of SYSTEM being killed. I use 8, 10, 20, 40, 45, 50.


Sent from the Droidforums App via a Neurocellular Processing Unit.

I tried a Deprimed kernel a few months ago when I first got into the Droid, but since then I've used ROM Manager exclusively and I see no Prime kernels. This may be why I went with ChevyNo1 kernels. Also they were mentioned in the SetCPU tutorial thread.

Once something works for me I generally stick with it and try small changes. This holds true for the V6 Supercharger script- I've stuck with 'Balanced 3' because a tutorial said it ran very well on low-memory devices. I haven't played with it since it was working fairly well.

I guess I'll have to dive into RaidZero's Recovery in order to sort out a Deprimed kernel.

I was also a bit confused about 'Primed' vs. 'Deprimed' options and what that all meant. I guess I've got some googling to do...

edit:
uh-oh!
I went into the V6 supercharger script in order to test the phone with the script 'unsupercharged', but touching the screen (to scroll) gives me text input at the prompt.
Looks like this:
^[[6-^[[6-^[[6-^[[5-^[[5-^[[5-
I got out of the script with a '17' entry (at first it thought I'd entered '7' and scolded me), and did a reboot, but the second time into the script still gives the weird input.

edit2: Aha! Swiftkey X is to blame. disabled that and have no problems in the script with the stock keyboard.
edit3 godammitsomuch I spoke too soon- stock keyboard also gives weird input, as does the D-button.

Check out kernel manager lite on the market. It has primes latest and I believe you can flash from the app like with rm.

Sent from my Droid using DroidForums

[AlphaMack]

I'm happy to report that battery life is much better with 141. My phone has been off the wall for 9 hours now and it's at 40% with some use.

[phonetool]

Check out kernel manager lite on the market. It has primes latest and I believe you can flash from the app like with rm.

Sent from my Droid using DroidForums

Hey! Thanks!
That worked perfectly.
Actually, it didn't work perfectly. During install, Kernel Manager complained about 's-on' and refused to complete the flash.
ROM Manager, however, didn't care about that and flashed the file from the Kernel Manager folder on the SD card.

So now I'm Droid/CM/Winner141/Deprimed/Supercharged. Seems to run ok, but it usually takes me a couple days to find issues.
Meanwhile, more DANCING BANANAS!!

[GohanBurner]

I really enjoy the feature of having the screen on/off animations independent from GUI animations. Now I can have the GUI animations set to fast while still having that cool on/off animation! Thanks Winner! You're the best!

[zachdroid]

I really enjoy the feature of having the screen on/off animations independent from GUI animations. Now I can have the GUI animations set to fast while still having that cool on/off animation! Thanks Winner! You're the best!

^Where did you find this at?

Sent from my Droid using DroidForums