yashsingh1/xdaforums huggingface dataset:
[EVO 4G General] -shift-:
I agree, it's not uncommon. I just seem to have them where it limits my kernel flashing hobbies.

Swyped from my EVO via the XDA app
[EVO 4G General] p-slim:
It does work just not right when you open the camera. If you slide the zoom bar once, then after that double tap to zoom will work
[EVO 4G General] beatblaster:
God, that SUCKS. I would lose my flippin mind if that happened to me. Excuse me while I go knock on wood :)
[EVO 4G General] -shift-:
You have no idea.... =(

Swyped from my EVO via the XDA app
[EVO 4G General] krazyflipj:
I asked this before, but I didn't get a response. Has anyone got the following to work on the latest nightly?

http://github.com/CyanogenMod/andro...mmit/5e847a1217dd54c7f9eb66474323f57965ea1bc1
[EVO 4G General] beatblaster:
You're right. I don't :( Maybe we should start a "let's get Shift_ a new EVO" bounty thread. Wait, not bounty.... that's such a bad word. lol
[EVO 4G General] MrDSL:
I havent been able to flash a nightly in awhile either and if i do flash a nightly and it boot loops i cant even flash cm6 final it will boot loop also.

i have to flash another rom all together like a sense rom and then cm6 final for it to work again!! :(

I dont know what is going on!!!!! I have always been able to flash nightlies..
[EVO 4G General] -shift-:
haha dude, i less than three you :p

that's weird.. i'm assuming you've done dalvik/cache wipes between flashing nightlies? jmxp69 gave me a perl script that i run on my ubuntu box to check kernel sizes on boot.img on flashable roms. i check the kernel image size before flashing, and the biggest i can boot is cm6 final :(

what's the latest nightly you can flash?
[EVO 4G General] bpqow:
I haven't had any problems flashing nightlys. On 9/13 now.
[EVO 4G General] MrDSL:
The last one I was able to flash I think was 09-08 but now I can't even flash that one..I dont know what the deal is :(
[EVO 4G General] -shift-:
Hmmm... The kernel size hadn't changed much since 9/8. You did the full wipe?

Swyped from my EVO via the XDA app
[EVO 4G General] davpel:
I'm having the same issue. Can't flash any CM6 without boot loops now. Never a problem before. Anxious to try the new Snap with the latest nightly, but just can't get it working.
[EVO 4G General] -shift-:
with a full wipe? when was the last build you were able to successfully flash?
[EVO 4G General] MrDSL:
Oh yeah a full wipe and everything! I flashed the nightly last night and it boot looped so I wiped everything and it bootlooped on cm6 final. Thats when I had to flash a sense rom and then the final worked again. I was scared for a sec!
[EVO 4G General] davpel:
Wiped data/factory and then cache and dalvik twice each for good measure. This was with an attempted flash of the 9/13 nightly and the new Snap bfs. Then tried the same thing with a few prior nightlies. Haven't tried final yet.

The last time I successfully flashed CM6 was the final version a few weeks ago. Since then, I've been using Burnt Droid and then Fresh 3.2.0.
[EVO 4G General] davpel:
I'll try a sense rom and then back to cm6 later tonight and report back.
[EVO 4G General] p-slim:
Those not able to flash, did you try different recoveries?
[EVO 4G General] MrDSL:
If I get a chance to flash tonight I will go with amon and see.
[EVO 4G General] davpel:
I've been trying with Amon exclusively. Maybe I'll give clockwork a try tonight -- although from what MrDSL reports, this is unlikely the issue.
[EVO 4G General] p-slim:
Yeah that's what it sounds like, I have no clue what's going on, that's so weird
[EVO 4G General] Vivix729:
I'm gonna Nandroid and try tonight's nightly, to see if I'm having these issues as well :P
[EVO 4G General] davpel:
Question for those of you who cannot get CM6 to flash. Is your SD card partioned or unpartioned. The reason I ask is that I read some reports elsewhere that the partition might cause the boot loops. Mine is partitioned.
[EVO 4G General] -shift-:
Cyanogen just tweeted back to me, saying that he'll try to get it done tonight... Slimming down the kernel.

Swyped from my EVO via the XDA app
[EVO 4G General] MSmith1:
Anything on the music battery drain?
[EVO 4G General] -shift-:
Nothing as of yet. Been testing with snap, and it improves, but the problem still persists.

Swyped from my EVO via the XDA app
[EVO 4G General] nicholaaaas:
have you tried the "fix" yet?
[EVO 4G General] -shift-:
Not home yet.... Itching to give it a whirl lol

Swyped from my EVO via the XDA app
[EVO 4G General] MSmith1:
Damn. I love CM6 but I don't miss that drain.
[EVO 4G General] davpel:
If I'm flashing CM6 and then immediately flashing Snap before a reboot, why would the stock CM6 kernal size matter in terms of the bootloop issue? Sorry if this is a dumb question.
[EVO 4G General] -shift-:
Yea man :(

Yes it wouldn't matter, but for those who don't want to flash Snap are in trouble.

Swyped from my EVO via the XDA app
[EVO 4G General] davpel:
So since Snap is only about 3mg, I guess it's safe to assume that kernal size is not what is causing my boot loop problem, right?
[EVO 4G General] krazyflipj:
Just flashed latest nightly and the new swipe notifications is awesome!
[EVO 4G General] beatblaster:
Whoa. I must have missed something somewhere. You guys talking about battery drain with the stock music player or all music players in general? I found mortplayer and love it so far but I thought I noticed some battery issues.

Then again, I stream too much bluetooth and play too much armored strike too notice if there's a real drain issue or not. I'm killin the battery as it is with normal use.
[EVO 4G General] bpqow:
What are swipe notifications?
[EVO 4G General] MSmith1:
In my experience and testing, CM6 has a much higher than expected battery drain when playing music through any music player. I've gone so far as to flash a sense based rom to test and the drain on a sense based rom is significantly less. Overall, I was getting great battery life on CM6 mind you, but playing music would would kill my battery faster than it should.
[EVO 4G General] -shift-:
the snap kernel image is 2.2 mb. i have no issues flashing 2.2mb. i'm not sure what your limit is though.

edit:

the cm kernel is currently 2.4mb. it needs to be 2.2mb for everyone to flash it. i'm surprised not more people are having this issue or raising hell about it lol.
[EVO 4G General] krazyflipj:
U get to swipe individual notifications (similar to web os)

Sent from my CM6 powered device
[EVO 4G General] zonyl:
I would imagine the DSP manager would suck down some serious battery. Have you all tried turning that off?

---

I believe the long-press back button is enabled in the Settings -> Applications -> Development screen.
[EVO 4G General] -shift-:
yes, that's the first thing to go.
[EVO 4G General] MSmith1:
This issue goes waaaaayyy back. Long before dsp was ever introduced. And to answer your question, it was never enabled.
[EVO 4G General] -shift-:
exactly... we've been testing this since.. well, the first nightlies.
[EVO 4G General] Vivix729:
shift_, installed the latest nightly with no issue :(
[EVO 4G General] Bizdady:
whats new in the newest nightly? swipe to side clear notification?
[EVO 4G General] nicholaaaas:
you would be incorrect... the snapturo file contains more than just the kernel
[EVO 4G General] killi:
I am sorry if it sounds lame, but I also have no idea what this means, as I never used web os and am not sure what this actually.... does. do you just open the notifications area and swipe an individual one away?
[EVO 4G General] DomSim:
The swipeing for notifications just means if you have multiple notifications you can drag down the notification bar then swipe an individual notification to the side to dismiss just that one but leave the rest still there.
[EVO 4G General] DomSim:
Works as advertised! That's awesome!
[EVO 4G General] -shift-:
did it screw up your homescreen setup? i'm trying various tricks to get the new nightly, so far, no success...
[EVO 4G General] davpel:
Well, after many attempts, I was finally able to flash CM6 with snap, but the only version that would work was the final build. Nightlies are still a no go. That being said, I'm definitely enjoying the new snap.
[EVO 4G General] -shift-:
welcome to my "small nand available" club.
[EVO 4G General] davpel:
I guess if I have to be a member of a small something club, nand is okay!
[EVO 4G General] -shift-:
my sentiments exactly.
[EVO 4G General] nicholaaaas:
i think i'm on the right track with a fix... but i think i would be much easier in linux... maybe i'll get up early and work on it
[EVO 4G General] -shift-:
me too. i'm debating whether or not to take my 2 laptops to work tomorrow to get some snap work done along with this small kernel bs...
[EVO 4G General] nicholaaaas:
i cleared about 40 gigs on my hdd... some maybe i'll get linux setup in vmware tomorrow
[EVO 4G General] rjacobs:
Just knocked out a 2200 quadrant with the latest nightly and the snap7.6BFS kernel running SnapTurbo. Damn this thing is sickeningly fast.
[EVO 4G General] amw1972:
I'll bump to that!!! I broke 2200 same same!!!:D
[EVO 4G General] ranmasaotome510:
Oh, i can only assume the reason alot of ppl are not raising hell is due to the nature of the issue at hand. gotta look at it at a normal persons perspective. HOPEFULLY If they read the fine print on Cyanogens nightly build site about not posting bug reports with nightlies (because the majority of us being male :D ), then the first thing you'd expect is that anyone experiancing bootloops are gonna be tight lipped in fear of being shunned for reporting a bug on a NIGHTLY. as i, like probably many, have noticed this RIGHT after the 9/6 nightly, when the kernel changed.

But yes, as to your proposition that it could be because of a band block, i cant believe our phones aren't smart enough to just write around the band block, or is that just how NAND works? you need a consistent stream of data, no interruptions, like on a magnetic tape? silly. but then again i didn't invent NAND >_>

Edit: P.S - ****.. now i want a new phone (bad NAND block free) so i can bask in new cm kernel glory T_T
[EVO 4G General] -shift-:
the bad nand block is in boot sector. i wish it could write around the bad blocks... =/

as for raising a ruckus for nightlies, i just let cyanogen know and he said he'll get to it tonight. hopefully, tomorrow will be more promising. this is a very important issue as bad nand blocks is not an uncommon issue. in the meantime, i'm trying to incorporate the snap kernel zimage into a nightly build boot.img. hopefully, i can get that working tomorrow...

edit:

i want a new phone too now, but, knowing my luck, it'll be a crappy version that couldn't handle uv or has issues with radios or has worse bad blocks...
[EVO 4G General] nicholaaaas:
i'm guessing this isnt a warranty issue :-P (until i have bad block too)
[EVO 4G General] -shift-:
it could've been a warranty issue if i bootlooped within the first month or even continuously since then...
[EVO 4G General] ranmasaotome510:
Actually just remembered something while lying In bed. My sisters bf's verizon touch (vx6900) that I helped put froyo on. During the android installation process. I remember it reporting like 3 bad blockes yet it was still capable of writing the os. Then again it was just the os. I guess once kernels done. It dictates how data is written, thus ignoring bad blocks and writing around them. Iono.. great to know cyanogens on it. But now I'm immesly curious as to how he's going to solve our bootloop woes. If kernel size tweaking is all there is to it, Then God this phone is a lot more lame then I thought. But I don't know cyanogen. He might pull something crazy and make everything work again + 4G :-) lol. Alright ima go too bed now haha.
[EVO 4G General] pitmanr2003:
Can't download mms message
[EVO 4G General] davida72:
I'm still not able to charge via my pc's usb....that's the only issue having with the latest nightly, so went back to my previous :(
[EVO 4G General] MrDSL:
I was able to flash last nights nightly with no problems..Finally!!
[EVO 4G General] amw1972:
I've HAD boot loop issues with nightlies before...saw that as a necessary evil actually. Also..until i hit up SNAP 7.5 and now 7.6...I can ONLY run SNAP 5.0 with ZERO random boots.

I am currently successfully running Sept 14th's nightly with SNAP 7.6 immediately flashed on top ON SNAP Turbo.
[EVO 4G General] davpel:
That's great to hear. I assume this was from a complete wipe as opposed to flashing over some pre-9/8 version of CM6?
[EVO 4G General] locozildjiangodx:
Hey yall,

I was wondering if there is an (un)official changelog for each nightly, or at least weekly or something. It looks like this thread started out as that but hasnt been updated in a month. thanks
[EVO 4G General] stangdriverdoug:
A lot of the guys follow cyanogen on twitter and keep an eye on updates that way. This thread has died a bit because this rom is about as good as it gets. Just about everyone that runs this rom and has an evo is waiting to see when or if they get 4g running.

Snap Powered
[EVO 4G General] -shift-:
stangdriverdoug is correct. i would also add to follow @cmsrc on twitter. that's the cm commit github twitter account. it tweets all of the commits to every line for cm. keep an eye for supersonic and the froyo base line. :)
[EVO 4G General] locozildjiangodx:
thanks shift!
[EVO 4G General] rjacobs:
I think I spoke to soon. Banged out a 2620 then a ~2400 a few times.
[EVO 4G General] MrDSL:
I had to drop the latest nightly cause it would not let me send txt messages..Gave me some kind of network error and told me to call customer care.

Loading a backup to make sure its not on my end.
[EVO 4G General] eddieroger:
This is a Sprint problem - one of my friends was having the same issue with a Pre, and when she called Sprint, the IVR said they were aware of the issue.

edit: forgot to quote
[EVO 4G General] MrDSL:
I restored my backup and txt messages send fine now.. I guess it could be a coincidence but I need my txt messages so I'm not gonna bother going back to the nightly.
[EVO 4G General] beatblaster:
If it makes you feel better I just had this exact same issue this morning on cm6 final. All I did was resend the text message and it worked fine after that and hasn't happened again since. If it starts becoming common then I think we have something to worry about. for now I'm just shrugging it off as a fluke.
[EVO 4G General] posguy99:
Speak for yourself. 4G is irrelevant unless you live in a 4G area. There have been plenty of desirable changes committed since 6.0-release.

Unfortunately, they're paired with the .34.5 kernel, which is... skippy.
[EVO 4G General] TZAK34:
Has anyone had their battery icon in the status bar stop working? Mine won't update anymore after I changed some colors in the status bar. Just shows the lightning bolt like it's charging?
[EVO 4G General] -shift-:
Stock theme?

Swyped from my EVO via the XDA app
[EVO 4G General] stangdriverdoug:
Ok maybe not just about everyone.....but a lot and the number is growing daily. All in saying is that 4g needs to be implemented into this rom for it to keep it's long term relevency. I personally keep a nandroid of cm6 final and a sense rom because I'm in 4g territory from time to time. Sorry to get off topic.

Snap Powered
[EVO 4G General] TZAK34:
Using elegant steel theme actually. Problems? I tried reflashing the them already to no avail.
[EVO 4G General] -shift-:
just try to see if you have the same issue with stock. it looks like they may have changed the framework a bit in the latest nightly, throwing off most themes.
[EVO 4G General] davpel:
Well, after successfully flashing CM6 final + the new Snap yesterday, I tried an update to last night's build. No dice. To paraphrase on of my favorite Seinfeld characters: You are a band nand . . . a very band nand.
[EVO 4G General] -shift-:
*bad lol

but i'll let this one pass since i love seinfeld too :p
[EVO 4G General] davpel:
Shift:

Given that you've been in contact with Cyanogen directly regarding this issue, do you think it would still be worthwhile to post a formal bug report on the issue tracker? I'm very anxious to get this problem resolved and start flashing nightlies again.
[EVO 4G General] -shift-:
Bug reports for nightlies aren't accepted.

Swyped from my EVO via the XDA app
[EVO 4G General] MrDSL:
And its the leading cause of male impotence!
[EVO 4G General] davpel:
That's what I thought, too. But then I was looking at some of Cyangoen's Twitter posts, and he has recently responded to several people who complained of issues with nightlies by telling them to file a bug report.
[EVO 4G General] davpel:
Very good! And don't even get me started regarding the ramifications of "flashing nightlies."

I read a post elsewhere here recently about an option built into the CM6 settings to correct screen colors. I think it was supposed to be in settings/CM6settings/display/render, or something close to that. But I can't find it in CM6 final. Is this feature only in the newer nightlies?
[EVO 4G General] -shift-:
Yea, I saw that too, but I'm just being careful.

Swyped from my EVO via the XDA app
[EVO 4G General] -shift-:
The render settings are in that exact path you said lol. I'm running 6.0 and just confirmed it.

Swyped from my EVO via the XDA app
[EVO 4G General] davpel:
Hmm. When I go into CyanogenMod Settings, I get the following options: Application Settings, Input Settings, Performance Settings, Sound Settings and User Interface. No Display Settings.
[EVO 4G General] -shift-:
Sorry, it's in User Interface.

Swyped from my EVO via the XDA app
[EVO 4G General] shawnathan9:
I already saw that Shift responded to you.

However, this made me LOL. I'm not that obnoxious but I love how technical jargon can skew the thought process at times..

What's a UI???? :)
[EVO 4G General] -shift-:
ui = user interface

also..

gui = graphical user interface
[EVO 4G General] davpel:
Thanks! Don't know how I missed that. I thought I checked all of the CM settings.
[EVO 4G General] Jon:
Yesterday I wiped my 6.0 final and did a fresh install of Nightly 09142010(default kernel) and it's working great :)

I was having some problems with freezing/FC's, didn't really care to look into their causes as I wanted to feel like i had just gotten a brand new EVO :p

Cyanogen MOD is awesome.
[EVO 4G General] tsatrom:
Did you find a fix?

Did you find a fix for this? My dock doesn't work either on the latest nightly...
[EVO 4G General] DomSim:
nightly failed
[EVO 4G General] MSmith1:
Mighty quiet around these parts lately. Seems like things have been moving pretty slowly since 6.0.
[EVO 4G General] p-slim:
6.0 doesn't run the .34 kernal. I notice significant difference with it
[EVO 4G General] -shift-:
i'm wondering how many people are having issues with making the nightlies boot up...
[EVO 4G General] Shidell:
I just tested the latest nightly (9-15) successfully--everything worked for me save for Bluetooth (which is nothing new, and why I'm here.)

I'd like to offer a bug in CM6 to be possibly recorded/tracked by this thread. The issue is simply that in RC1, Bluetooth would connect/talk with my vehicle (Hyundai Elantra '09) and since RC2 will not.

The Headunit is a "BlueConnect" model. I can dig up more information if necessary.

Essentially, in RC1, everything works great. Enable BT, shortly thereafter (with the car's power on, of course) it detects the headunit and a pairing request is made. Finish the pairing request and the two sync up for phone calls through the headunit.

Since RC2, the headunit no longer shows up. No pairing request, can't find it while searching for devices, etc. CM6 Final and the latest nightly behave the same way.

I know that a lot of work was done between RC1 and RC2 regarding BT, and that it solved a lot of issues for people. My objective is to get logcats of pairing with RC1 and then trying to do so with RC2.

I do have a few questions:

Who might be intimately familiar with the BT changes between RC1-RC2? The individual working on those changes might be well aware what could be causing my trouble, and so they might be able to alleviate it (or point me in the right direction of doing so)

Am I the only person to have BT pair/sync problems since RC1? Surely others are having similar difficulty?

Thanks for any help or advice you might be able to lend.
[EVO 4G General] amw1972:
I've had several random reboots from the last few nightlies...matters have cooled since I started flashing SNAP7.6 w/SNAPTurbo enabled.

I have not had issues with booting the last couple of nightlies...but then again...I reflash 7.6 in the same recovery session per the guidance in the SNAP thread.
[EVO 4G General] MSmith1:
That is very true.

I have to admit that im kind of disappointed that not many of the evo specific bugs have been squashed out in the 6.1 nightlies. I was hoping that once the 6.1 nightlies started that wed see some more Evo specific progress, and im not talking 4G HDMI etc. there are a lot of other smaller Evo specific tweaks that would help a lot of people. Not complaining. Was just hoping.
[EVO 4G General] galt:
I just flashed the 9-15 nightly, no problems booting at all (was actually crazy fast for a first boot), so far all is awesome. You tube works, swipe notifications work, had one camera app crash after playing with touch to focus in camcorder mode.

I love stock android with the cyanogen tweaks so much that I don't think I can ever go back... even if it fracks my battery like it did before (will report on that after a few days) .
[EVO 4G General] dwntwnall4u:
No issues here.
[EVO 4G General] fragchild:
Let me first state that I'm not a dev and wont be able to help you but the people who can will need some sort of logging.

Get a logcat of it pairing and working with RC1. Then grab another logcat of the pairing process failing. Then post those logs.
[EVO 4G General] mkeena0305:
+10 I was flashing every nightly. Now its getting old with the lack of development.
[EVO 4G General] davpel:
I am still unable to flash any new CM6 nightlies, apparently due to the kernal size/bad nand issue. Waiting (not so) patiently for a fix!
[EVO 4G General] kawasaki00:
I am unable to flash any of the nightlies after about 9-06-10

I am running 9/2 with snap 7.6 and everything is great, If i flash any of the newer ones over the top of it or do a clean wipe it doesnt matter. I am flashing the 7.6 right after the nightly flash and it bootloops every time.
[EVO 4G General] DarkPhoenix:
I'm trying to flash the 9-15 nightly with clockwork recovery and I keep getting the following error.

-- Installing: SDCARD:cm_supersonic-09152010-005429.zip

Finding update package...

Opening update package...

Installing update...

Welcome to CyanogenMod-6-09152010-NIGHTLY-Supersonic!

assert failed: getprop("ro.bootloader") == "0.76.2000" || getprop("ro.bootloader") == "0.79.0000"

E:Error in /sdcard/cm_supersonic-09152010-005429.zip

(Status 7)

Installation aborted.

Has anyone had this problem and if so is there a way to fix it?

I used the search button by the way and couldn't find anything regarding this.

Thanks
[EVO 4G General] fldash:
CM6 9/15 does not work for me... I get white screen bootloops even after wiping everything 3x... No idea why... never had this issue before so I went back to CM6 final.
[EVO 4G General] -shift-:
Yea that's a good point. Hopefully, they come up with some stuff soon.

Swyped from my EVO via the XDA app
[EVO 4G General] DarkPhoenix:
I just tried flashing the 9-14 nightly with the same results.
[EVO 4G General] jorgeszabo:
Someone correct me if I'm wrong but I believe you need the eng bootloader (0.76) to flash CM6. From the error code you got it appears that you have the original bootloader that came with the Evo (0.79). I don't have the link right now but if you look around the forums you'll find instructions on how to flash the eng bootloader.

Hope this helps.
[EVO 4G General] DarkPhoenix:
That won't affect the unrevoked s-off root at all will it?
[EVO 4G General] DarkPhoenix:
That fixed it. I actually had (0.93). I installed (0.76) and am flashing the newest nightly now. Thank you!
[EVO 4G General] p-slim:
good job jorgeszabo you're a gentlemen and a sholar!

thanks for posting the logs, otherwise other people wouldve never got the problem fixed.