By 
The CyangonMod crew is hard at work tidying up the code for the latest release of their custom ROM for Android. CyanogenMod7 has reached release candidate 4 status and is no available for all supported devices. Nothing major here, this is mostly a bug-fixing release bringing the ROM build a little more up to snuff. The largest improvement of the batch seems to be the addition of hardware acceleration for the NOOKcolor, though EVO GPS issues and a Nexus One calling bug are not addressed.
Head on over to the source link below to track down the build for your device (if it is supported). Happy rooting!
[via CyanogenMod]
I went back to Stock GB to see what it was like and I now get 2 days battery life instead of 1 with CM7. Will way until full release is out before I try it again.
I do miss the features of CM7 though.
I went back to Stock GB to see what it was like and I now get 2 days battery life instead of 1 with CM7. Will way until full release is out before I try it again.
I do miss the features of CM7 though.
I wish all Android users had that option. :(
I wish all Android users had that option. :(
EVO GPS issue? I feel like that was fixed a while ago.
The GPS on CM7 for my EVO has been working perfectly for a while now…
EVO GPS issue? I feel like that was fixed a while ago.
The GPS on CM7 for my EVO has been working perfectly for a while now…
What about G2 GPS issues? How come no one talks about this, when almost every G2 user has them?
What about G2 GPS issues? How come no one talks about this, when almost every G2 user has them?
i had issues with gps going to RC1. So i made a backup(of rc1), wiped, flashed cm6, used gps to get a lock and then with gps on lflashed the backup i made of cm7 rc1 and it worked. A lot of work but it worked for me. Skipped rc2, wiped and flashed rc3 (gps still worked), wiped and flashed rc4. Always fixed permissions inbetween and it took a few minutes to get the first lock, after saying -location unavailable-, after that the gps was speedy. It takes a lot of forum reading and quite a bit of work but there are a few work arounds for the time being. Not saying one of them will work for you but keep trying if cm7 is worth it to you… or go back to stock were everything works as it should.
i had issues with gps going to RC1. So i made a backup(of rc1), wiped, flashed cm6, used gps to get a lock and then with gps on lflashed the backup i made of cm7 rc1 and it worked. A lot of work but it worked for me. Skipped rc2, wiped and flashed rc3 (gps still worked), wiped and flashed rc4. Always fixed permissions inbetween and it took a few minutes to get the first lock, after saying -location unavailable-, after that the gps was speedy. It takes a lot of forum reading and quite a bit of work but there are a few work arounds for the time being. Not saying one of them will work for you but keep trying if cm7 is worth it to you… or go back to stock were everything works as it should.
i had issues with gps going to RC1. So i made a backup(of rc1), wiped, flashed cm6, used gps to get a lock and then with gps on lflashed the backup i made of cm7 rc1 and it worked. A lot of work but it worked for me. Skipped rc2, wiped and flashed rc3 (gps still worked), wiped and flashed rc4. Always fixed permissions inbetween and it took a few minutes to get the first lock, after saying -location unavailable-, after that the gps was speedy. It takes a lot of forum reading and quite a bit of work but there are a few work arounds for the time being. Not saying one of them will work for you but keep trying if cm7 is worth it to you… or go back to stock were everything works as it should.
i had issues with gps going to RC1. So i made a backup(of rc1), wiped, flashed cm6, used gps to get a lock and then with gps on lflashed the backup i made of cm7 rc1 and it worked. A lot of work but it worked for me. Skipped rc2, wiped and flashed rc3 (gps still worked), wiped and flashed rc4. Always fixed permissions inbetween and it took a few minutes to get the first lock, after saying -location unavailable-, after that the gps was speedy. It takes a lot of forum reading and quite a bit of work but there are a few work arounds for the time being. Not saying one of them will work for you but keep trying if cm7 is worth it to you… or go back to stock were everything works as it should.
EVO, running CM7 Build 32 ( the build right after RC3) – My issue is with the reset / load times with CM7… prior to rooting my phone, my stock rom would power off and on again in approximltly 1 minute and 15 sec. now with CM7 it takes over 2 minutes and another 20 sec’s or so to process the SD card…. All in all, the phone isn’t fully ready for close to 3 minutes! What gives…. Is this just a rooting thing, a CM7 thing or what…
EVO, running CM7 Build 32 ( the build right after RC3) – My issue is with the reset / load times with CM7… prior to rooting my phone, my stock rom would power off and on again in approximltly 1 minute and 15 sec. now with CM7 it takes over 2 minutes and another 20 sec’s or so to process the SD card…. All in all, the phone isn’t fully ready for close to 3 minutes! What gives…. Is this just a rooting thing, a CM7 thing or what…
HHope we get this for our Thunderbolts soon
HHope we get this for our Thunderbolts soon
HHope we get this for our Thunderbolts soon
HHope we get this for our Thunderbolts soon
tmo vibrant still without support /cry
tmo vibrant still without support /cry
tmo vibrant still without support /cry
tmo vibrant still without support /cry
With this, I can’t download anything from the Market over about a megabyte. What gives? It was the same with RC3, but not with the stock, unrooted firmware.
With this, I can’t download anything from the Market over about a megabyte. What gives? It was the same with RC3, but not with the stock, unrooted firmware.
With this, I can’t download anything from the Market over about a megabyte. What gives? It was the same with RC3, but not with the stock, unrooted firmware.
The fine folks on the CyanogenMod IRC channel sorted me out, big thanks to them (I had to wipe the cache from the Recovery boot menu).
The fine folks on the CyanogenMod IRC channel sorted me out, big thanks to them (I had to wipe the cache from the Recovery boot menu).
The fine folks on the CyanogenMod IRC channel sorted me out, big thanks to them (I had to wipe the cache from the Recovery boot menu).
The fine folks on the CyanogenMod IRC channel sorted me out, big thanks to them (I had to wipe the cache from the Recovery boot menu).
With this, I can’t download anything from the Market over about a megabyte. What gives? It was the same with RC3, but not with the stock, unrooted firmware.
release candidate 4 status and is no available for all supported devices.
Proof reading is a lost art.
release candidate 4 status and is no available for all supported devices.
Proof reading is a lost art.
release candidate 4 status and is no available for all supported devices.
Proof reading is a lost art.
release candidate 4 status and is no available for all supported devices.
Proof reading is a lost art.