I know whats wrong.. with CM7..
All i need IS ANY DEV to.. take.. all of CM7 RC1 and take the BT/WIFI Drivers from BUILD #19 CM7 Nightly and replace them with the CM7 RC1 drivers..
THIS WILL FIX THE WIFI ISSUES WITH CM7 RC1
CM7 19 NIGHTLY was the ONLY NIGHTLY that had fully WORKING wifi for my Slide..
My slide has the broken WIFI issue
any dev WHO can do this..
Will have a DONATION from me im sure the rest of us broken WIFI slides will do the same
http://www.mediafire.com/?1y0brnx6fl4nx3h - CM7 Nightly 19
bumping my post
Related
Hi guys,
Just have a quick question- wondering if anyone is running into the same problem. I just installed Cyanogen 7 rc1, and it is force closing between the load screen and the welcome screen (for the first time).
I'm not sure if this is the correct place to post this, but any help would be great.
Thanks
Based off what I've read in the development threads, the RC does't seem to be too much of an RC. I'd restore and wait.
you have to flash RC1 over a nightly build.
Nowak4G said:
you have to flash RC1 over a nightly build.
Click to expand...
Click to collapse
Yep! Its was a known issue with the first build of RC1. Something was botched. I recommend you either flash RC1 over nightly build #38, or you just flash nightly build #39 (which already includes fixes that were left out of RC1).
Cheers!
My Nook Color runs fine with CM7 7.0.3 stable and Dalingrin OC kernel 042411, but 802.1x EAP Wifi doesn't work. (Neither does AutoProxy, but that is another story.)
Changing to Dalingrin 040411 solves the 802.1x problem, but the CM7 boot animation disappears and my Nook is slow to boot. The comments in the main Dalingrin discussion thread suggest performance is best using 042411 with 7.0.3, yet Wifi 802.1x is broken.
So questions:-
* anyone else with the same problems, or is it just me (which would suggest I've made a simple mistake somewhere?)
* is 042411 the last pre CM 7.1 kernel? (which means the above problem will not be fixed against 7.0.3?)
* Quote: "2.6.29 releases are discontinued and no longer supported" which ones are these exactly? With the exception of /051311/update-Froyo1.2-dalingrin-2.6.32-emmc-051311.zip the kernels have _dates_ not build numbers?!?
* is my best bet to go to CM7.1 RC0 and the latest Dalingrin kernel? Has anyone else got 802.1x working with this or a similar combination?
Sorry for all the questions. I feel like I am assembling a jigsaw puzzle without the illustration on the box...
Thanks
Yeah, my wifi is broken with the latest nightly and kernel. Waiting for a response in the main daligrin thread
Sent from my NookColor using Tapatalk
I've solved the problems, although I still don't know all the answers to my questions.
I've switched to CM7 7.1.0 RC1 with Dalingrin OC 063011 and Wifi 802.1x is working fine. So far so good!
ezlxq73 said:
I've solved the problems, although I still don't know all the answers to my questions.
I've switched to CM7 7.1.0 RC1 with Dalingrin OC 063011 and Wifi 802.1x is working fine. So far so good!
Click to expand...
Click to collapse
Yeah... I had the same issues and had to do exactly what you did... so far so good.
anyone using cm7.2 rc1 yet? i've been trying to download it, but it's really slow. Been pretty happy with the nightlies so far, and am looking forward ot cm7.2 stable (and cm9 stable of course)
any new bugs that i should be aware of before flashing? I'm not too android savvy, so any tips are appreciated.
thanks
I'm trying to get it too, many people have same issue. The CM servers are hot these days
As far as i know there might be some issue with ringtones when stored on sd card...?
You can check official 'bugzilla'
I did dig but didnt find anything to worry.
tried the official update but it was "meh"
almost same with the nightlies, minus some features from nightlies
I went back to euroskank nightly instead
i suggest using the newest nightlies, 'cause they have some bugs fixed, which RC1 don't. You should see the CM7.2 RC1 thread, there is a .torrent link which is running full speed, opposite to their sever
I'm downloading now will share my experience once I'm done!
Hi Guys, just a quick question here, I recently changed my ROM from CM 7.2 to CM 7.2 Mirage - Kang Build by using a CWM Recovery SD, clearing cache and such, all worked correctly and properly, just that I didn't know that the Kang Build did not support 16bit Frame Buffer that I wanted so that NC can atleast run Blood & Glory.
Now my question is if I reverted back to CM 7.2 by clearing Dalvik Cache and Cache first, would there be any problems in terms of the system and apps?
No, there would be no known issues... both are the same build as far as that goes...
thewaywardgeek013 said:
Hi Guys, just a quick question here, I recently changed my ROM from CM 7.2 to CM 7.2 Mirage - Kang Build by using a CWM Recovery SD, clearing cache and such, all worked correctly and properly, just that I didn't know that the Kang Build did not support 16bit Frame Buffer that I wanted so that NC can atleast run Blood & Glory.
Click to expand...
Click to collapse
I've posted a 16 bpp kernel here for that build.
Frank
frankusb said:
I've posted a 16 bpp kernel here for that build.
Frank
Click to expand...
Click to collapse
Hi Frank, I also read your posts in Mirage - Kang Thread, thank you for posting the thread of your kernel, didn't know you posted it here.
Also thanks DizzyDen, was a bit cautious at the time because there were a lot of changes that was done from Cm 7.2 > Mirage, didn't know that it would just overwrite it.
P.S.
@Frank - there's a new CM 7.2 MiRaGe - KANG build
Here:
Update 06/23/2012:
- New 06232012 build, synced with CM
I just don't know if the sync was for a Nightly Build of CM.
thewaywardgeek013 said:
@Frank - there's a new CM 7.2 MiRaGe - KANG build
Here:
Update 06/23/2012:
- New 06232012 build, synced with CM
I just don't know if the sync was for a Nightly Build of CM.
Click to expand...
Click to collapse
There were no kernel changes between 6/8 and 6/23. Actually you can probably run either of the kernels I posted with any CM7 build.
Frank
pls fix wifi tethered for cm9 or cm 10...urgen!!!