Root Cyanogenmod 5.0.6 is out

[Redflea]

Just released, check ROM Manager for Cyanogenmod 5.0.6.

Changelog:

---- 5.0.6-Droid
* Fixed MMS Videos (PDR447, slayher, DroidMod all had a hand in this)
* Fixups to 4/5 column launcher
* Fixed ##program menu
* Fix fstab bug (DroidMod)

Thread:

Cyanogenmod For Droid V5.0.5.7 (04/05/2010) - CyanogenMod Forum

Enjoy...

<EDIT> 5.0.6.1 has been released, presumably to fix the wifi issues, and remove setcpu from the ROM....

 

[geezman]

Just tried it and had issues with Wi-Fi. It kept saying "Unable to start Wi-Fi". I was not the only one having the issue. There where about 5 other people with the same exact problem. You may want to wait for version 5.0.6.1. I'm back to BB 0.9 for now.

 

[endorphine44]

Just tried it and had issues with Wi-Fi. It kept saying "Unable to start Wi-Fi". I was not the only one having the issue. There where about 5 other people with the same exact problem. You may want to wait for version 5.0.6.1. I'm back to BB 0.9 for now.

Reinstall the kernel, that seemed to fix wifi issues for most of those guys. I'm finishing a backup now so I can upgrade.

 

[Redflea]

Yup -just flash the kernel of your choice after loading the ROM and everything is fine w/wifi...I favor p3Droid's kernels recently, run very cool.

The 5.0.6.1 release should fix the wifi issues.

 

[condog]

i just upgraded from 5.0.5.7 and i still have launcher2 force closes like i had from when i jumped from 5.0.5.6(maybe earlier). is there any fix for this?

 

[silkchaos]

condog - i did too, but i did my FC, did a reboot and it was fine.

 

[tfleming23]

Not sure about anyone else, but I ran the update to 5.06 last night and upgraded the p3droid's low voltage 1250 max kernal. Two things I've noticed so far. I am running WAY hotter than before. I am hanging out in the 37-41 degree Celcius range when I am used to being in the hig 20's-low 30's at the same CPU clock.

Secondly, I just tried upgrading to 5.06.01 and it went into a point where it said it could not open the file, that the file was bad. Anyone else run into that?

 

[jackburnt]

Try clearing the cache and redownloading. That should fix that issue (hopefully).

I just installed it and bekit's 1.2 low voltage. So far so good. 27c and going down.

 

[johnlgalt]

Yeah, with regards to P3 versus bekit, reports everywhere have folks saying that the BeKit kernels are significantly cooler running (and in some reports, also more stable).

 

[Redflea]

Yeah, with regards to P3 versus bekit, reports everywhere have folks saying that the BeKit kernels are significantly cooler running (and in some reports, also more stable).

That's interesting, the exact opposite of my experience. Both were stable for me, but p3droid's kernel is running cooler for me than the Bekit kernel I ran before...

 

[GirLuvsDroid]

This just further illustrates that everyone's Droid is different. I can't run low voltage kernels on mine, which I understand from ChevyNo1, is the case with only about 10% of Droid owners. You just have to try different kernels until you find the one that best fits your Droid.

 

[Redflea]

Very true, GirLuvsDroid...

There's talk at cyanogenmod of auto-brightness being broken on this ROM...anyone who's flashed it seeing that issue?

 

[bp328i]

Very true, GirLuvsDroid...

There's talk at cyanogenmod of auto-brightness being broken on this ROM...anyone who's flashed it seeing that issue?

I flashed it for about 10 minutes today and did not notice it, but then again it was only 10 minutes. I like the NexTheme too much.

 

[shadowdude777]

Very true, GirLuvsDroid...

There's talk at cyanogenmod of auto-brightness being broken on this ROM...anyone who's flashed it seeing that issue?

Yep. Just tried it out. Auto-brightness doesn't do anything, whether I shine a bright flashlight on the phone or cover both the camera and the proximity sensor area, it doesn't change the brightness. I never use auto-brightness so I can deal, but that might be an issue for some.

 

[ska.t73]

I don't know anyone that uses auto-brightness really, it is a known battery hog... I just flashed 5.0.6.1 and am loving it... Tried out a few different ROMs for a while but seem to keep coming back to CM... now I'm just waiting for a theme Bgill updated his themes for 5.0.6.1 but the links aren't working at the moment so I sit and wait...

 

[Fadelight]

i just upgraded from 5.0.5.7 and i still have launcher2 force closes like i had from when i jumped from 5.0.5.6(maybe earlier). is there any fix for this?

Updated ROMs will never "fix" this issue. It is up to the dev of the launcher to make sure it works with the ROM, not the other way around.

Helix1 works, regardless. Given the choice between older ROMs and helix2 vs newer ROMs and helix1, I'll deal without the 3D app drawer for a while until they figure that one out.

 

[ska.t73]

I haven't had a problem with CM and the helix2 beta that is out there... my understanding is that the Dev of helix2 is working closely with Cyanogen and Koush to get it stable on their roms... Haven't had an issue yet today with 5.0.6.1...

 

[MisterEff]

I just went from 2.1, which I manually installed within minutes of us getting the update.zip, back to 2.0.1 and am not running my first modded ROM, this one. I tried HelixLauncher2 and it doesn't work for me. I hope they get that fixed soon because I am about to stop using the normal launcher and go back to helix like I had on 2.1

 

[Redflea]

I don't know anyone that uses auto-brightness really, it is a known battery hog... I just flashed 5.0.6.1 and am loving it... Tried out a few different ROMs for a while but seem to keep coming back to CM... now I'm just waiting for a theme Bgill updated his themes for 5.0.6.1 but the links aren't working at the moment so I sit and wait...

Hasn't been a battery issue for me...I'm at 70% at the end of the work day when I'm in an area where there's a decent signal and the phone isn't spending all the time hunting for 3G...

I can't live w/out auto-brightness myself...guess I'll have to keep riding 5.0.5.7 until Koush fixes the issue.

 

[condog]

Updated ROMs will never "fix" this issue. It is up to the dev of the launcher to make sure it works with the ROM, not the other way around.

Helix1 works, regardless. Given the choice between older ROMs and helix2 vs newer ROMs and helix1, I'll deal without the 3D app drawer for a while until they figure that one out.

its not helix or anything. its just the standard 3d launcher that cyan put on there. and i have no way of switching or turning it off making it impossible to use the ROM. ..... where is pete with 1.0 when i need him

 

[GirLuvsDroid]

its not helix or anything. its just the standard 3d launcher that cyan put on there. and i have no way of switching or turning it off making it impossible to use the ROM. ..... where is pete with 1.0 when i need him

Can't you just rename the .apk with a .bak extension or remove it from /system/app?

 

[Redflea]

its not helix or anything. its just the standard 3d launcher that cyan put on there. and i have no way of switching or turning it off making it impossible to use the ROM. ..... where is pete with 1.0 when i need him

You can use recovery to wipe system and re-install the ROM.

 

[Redflea]

OK...got an update on auto-brightness from PDR477 on Cyanogenmod forum:

redflea: auto-brightness works, it it's only "one way" now since google's latest change. when the screen is unlocked it takes a reading and sets the brightness appropriately. from that initial set it will only go up until the screen is shut off again. this is the new "normal". gotta just get used to it.

nothing changed regarding brightness from 5057 to 506. it changed back at 5056. 506 works just like your current 5057.

So if you were OK w/how auto-brightness has been working on 5.0.5.6 or later, you're supposedly still good.

However, I checked my phone running 5.0.5.7 and the screen will dim after brightening, so as far as I can tell autobrightness does work on 5.0.5.7...if it doesn't on 5.0.6 then something has changed between the two builds.

 

[ska.t73]

Ok so I am having a really weird issue with CM 5.0.6.... I'm trying to install the Red Rum theme from BGill and for the life of me it will not install... Tried it earlier today and as soon as it went to the Clockwork Mod screen I got a zip bad error and it reboots back to stock CM... so I deleted the download off of the SD card and tried it again through RomManager... same thing... so I re-did CM 5.0.6 and deleted the RR theme from the SD card and tried again through RomManager... same thing...

So I just deleted the RR theme from the SD card again and tried again through RomManager... this time it gets about halfway done and give me the zip bad error and re-boots.... never had this happen before and BGill and everyone else are not having any problems with it...

Any ideas at all guys?

 

[Redflea]

Can you open and read all the files in the RR zip from your PC?

Have you tried downloading the file via your PC, copying it to your SD card, and then using the install rom from SD card option?

Finally, maybe your SD card has a file system error...might want to run a check on it.