Related
Hello --
I have come across an issue that, as far as I have looked, doesn't have a dedicated thread. I've seen a few people with similar issues, but wanted to post a dedicated thread so that all of us can try to get some help. Thanks in advance to those that are willing to help
Down to business...
For the life of me, I cannot get my phone to boot an overclocked ROM. I've been mostly running DC roms, so, naturally, when the the .29 OC'd kernel was released, I flashed it. It threw my phone into a wicked loop where it wouldn't boot past the black-and-silver HTC screen.
Out of pure curiosity to see how an OC ROM would perform, I tried a number of other ROMs that advertised that they were OC'd. Every single one of them puts my phone into the same boot loop.
Does anybody have any ideas as to how I might be able to approach getting this fixed? I am at a total loss. Could it be a possible hardware issue?
murdocthc said:
Hello --
I have come across an issue that, as far as I have looked, doesn't have a dedicated thread. I've seen a few people with similar issues, but wanted to post a dedicated thread so that all of us can try to get some help. Thanks in advance to those that are willing to help
Down to business...
For the life of me, I cannot get my phone to boot an overclocked ROM. I've been mostly running DC roms, so, naturally, when the the .29 OC'd kernel was released, I flashed it. It threw my phone into a wicked loop where it wouldn't boot past the black-and-silver HTC screen.
Out of pure curiosity to see how an OC ROM would perform, I tried a number of other ROMs that advertised that they were OC'd. Every single one of them puts my phone into the same boot loop.
Does anybody have any ideas as to how I might be able to approach getting this fixed? I am at a total loss. Could it be a possible hardware issue?
Click to expand...
Click to collapse
I and others have had the same issue. I subscribe to the thread for the kernel in hopes that the issues will be solved.
I also had the same issue,
But then I flashed the recovery image from the darchdroid thread and
it booted right up, I'm wondering if it was an issue with godspeed or something.
Jwahlg said:
I also had the same issue,
But then I flashed the recovery image from the darchdroid thread and
it booted right up, I'm wondering if it was an issue with godspeed or something.
Click to expand...
Click to collapse
Interesting. I think I tried that recovery image yesterday before I flashed and rooted the official 2.1. I wonder if that recovery image will still work...?
Jwahlg said:
I also had the same issue,
But then I flashed the recovery image from the darchdroid thread and
it booted right up, I'm wondering if it was an issue with godspeed or something.
Click to expand...
Click to collapse
I dunno, the penultimate update worked in 1.6.2 (And I was like "HOLY CRAP I HAVE AN OC/AOSP ROM??? DDDDDDDDD"), and then the most recent worked in godspeed. I don't think it's a recovery issue. :/
Well if you want a thread like this then in order to try to find the culprit I would list all available info.
----------------------------
Hero Hardware version: 0002
Firmware 2.1 fresh-toast
baseband: 2.42.00.03.10
Kernel: 2.6.29-Godmode-OC-BFS 710 mhz
Build: Fresh-Toast 2.1
Software: 2.27.651.5
PRI: 2.10_003
PRL: 60660
-----------------------------
And just for the recored I have run every OC on here with no problem
nfinitefx45 said:
Well if you want a thread like this then in order to try to find the culprit I would list all available info.
----------------------------
Hero Hardware version: 0002
Firmware 2.1 fresh-toast
baseband: 2.42.00.03.10
Kernel: 2.6.29-Godmode-OC-BFS 710 mhz
Build: Fresh-Toast 2.1
Software: 2.27.651.5
PRI: 2.10_003
PRL: 60660
-----------------------------
And just for the recored I have run every OC on here with no problem
Click to expand...
Click to collapse
Alright, hopefully this helps...here is all of my available info. Currently running DC 2.09
----------------------------
Hero Hardware version: 0002
Firmware 2.1-update 1
baseband: 2.42.01.04.27
Kernel: 2.6.29-d30020a8 [email protected] #1
Build: DamageControl v2.09
Software: 2.20.651.1
PRI: 2.10_003
PRL: 60664
-----------------------------
Hello
I currently have a nexus one flashed with CM 6 RC2. I would like to get the new korean radio and flash with the new CM RC3 rom or with LimeMOD R4. I am not sure which one is better I am quite new to this. I would like to have the 720p video function and would like to not have ADW launcher built in. Could you please tell me which one to get. Also if there is any way to be able to change the trackball color for incoming calls i would like to know how to do that.
Thanks
I am new to this could you please give me a step by step explanation on how to flash the new firmware, google apps and radio.
Thanks
To make things easy and since you're already running CM6 RC2, I would open up ROM Manager and simply download CM6 RC3. CM6 RC3 comes with 720p and is much easier to do rather than flash a new radio and then flash CM6 or the other ROM that you stated.
If you don't have ROM Manager, go install it from the Market. Click Download ROM>CyanogenMod>CyanogenMod 6.0.0-RC3
Simple as that =).
sheanzyy said:
To make things easy and since you're already running CM6 RC2, I would open up ROM Manager and simply download CM6 RC3. CM6 RC3 comes with 720p and is much easier to do rather than flash a new radio and then flash CM6 or the other ROM that you stated.
If you don't have ROM Manager, go install it from the Market. Click Download ROM>CyanogenMod>CyanogenMod 6.0.0-RC3
Simple as that =).
Click to expand...
Click to collapse
Thank you very much! I would like to get the Korean radio though because i here it is much better than the one that comes with RC3. Do you know how to get it?
njiwani said:
Thank you very much! I would like to get the Korean radio though because i here it is much better than the one that comes with RC3. Do you know how to get it?
Click to expand...
Click to collapse
To be completely honest, I get amazing speeds with RC3 and WildMonks Kernel, so for me to flash a radio isn't necessary. A lot of the speeds posted about the Korean radio are from domains that aren't completely accurate, so make sure you do your research first.
There is no doubt an increase in speed, but like I said, RC3 with WildMonks Kernel gives me phenomenal amount of speed.
Okay that sounds good. Does the kernel come with RC3 or is that something seperate? I am not really sure what the kernel is..
The kernel that comes with RC3 is good enough. I shot 720p @22 FPS and when I flashed WildMonks Kernel, I shot 720p @24 FPS.
I see what your saying. I was wondering if there is an ADW launcher in the RC3 and if there is a way to change the color of the trackball for incoming calls.
Yes ADW Launcher comes stock with it and yes there are trackball color notifications for your dialer.
So where do i change those notifications? Also currently when using RC2 I am having some issues with Launcher Pro and I do prefer that over the ADW Launcher. SOmetimes when I open the app drawer it gets glitchy and some of the app dont show up. Also a lot of the time launcher pro has to do a force close. Do you know if that it fixed in the RC3?
I use Launcher Pro and I haven't had any issues with lag or FC's with RC3. For the LED notifications you simply go to Settings>CyanogenMod Settings>User Interface>LED Notifications> Dialer .
Update to RC3. It's a big improvement from RC2 and plus, you get 720p
and RC3 doesn't include a radio it keeps your existing, so if you want to flash the korean radio, there shouldn't be any problems (im using it on mine as we speak)
y2whisper said:
and RC3 doesn't include a radio it keeps your existing, so if you want to flash the korean radio, there shouldn't be any problems (im using it on mine as we speak)
Click to expand...
Click to collapse
How exactly do i flash the korean radio? Like a step by step please because I am very new to this.
Thanks
njiwani said:
How exactly do i flash the korean radio? Like a step by step please because I am very new to this.
Thanks
Click to expand...
Click to collapse
Make sure you do a nandroid backup first... that is very important!!
This is how I did it...
1. Downloaded the radio update from http://forum.xda-developers.com/showthread.php?t=723839
2. Copied the update to the root of my SD card
3. Rebooted phone and help the power button and the VOL down button to enter the fastboot/recovery mode
4. Use the VOL down key to select "recovery"
5. Phone reboots into recovery mode (I am using Amon Ra's 1.7.0.1)
6. I selected the option "flash .zip from SDcard"
7. It gave me a selection of the .zip files I had on the root on the SD
8. I selected the file that I downloaded in step 1
9. I applied the update and then the phone rebooted
10. Phone came back in recovery mode (I believe it wiped the cache)
11. Once the cache was wiped (it was automatic) I just rebooted the phone and started using like normal
Let me know if you want some screenshots or if I didn't explain something right. That is pretty much exactly what I did... step by step. Hope that helps.
njiwani said:
So where do i change those notifications? Also currently when using RC2 I am having some issues with Launcher Pro and I do prefer that over the ADW Launcher. SOmetimes when I open the app drawer it gets glitchy and some of the app dont show up. Also a lot of the time launcher pro has to do a force close. Do you know if that it fixed in the RC3?
Click to expand...
Click to collapse
Its a problem with Cyanogen and the launcher rotations, go into the launcher settings and disable auto rotation and all the FC's go away.Im not sure if this was fixed in RC3, but that was the problem in Rc2
Thank you very much! I will try this out and let you know. Also would it be better to do this before or after i install RC3? Or does it not matter.
Thanks
shouldnt matter
Blueman101 said:
shouldnt matter
Click to expand...
Click to collapse
I just flashed the korean radio...thank you for your help! It seems to be working fine..took a little while to boot up but other than that its good. Now if i flash with Rc3 it will keep the korean radio right?
njiwani said:
I just flashed the korean radio...thank you for your help! It seems to be working fine..took a little while to boot up but other than that its good. Now if i flash with Rc3 it will keep the korean radio right?
Click to expand...
Click to collapse
yes, the radio is something totally separate from the rom, which is why it is so important not to mess up a radio update, you can brick your phone if a radio update goes south, not even a nandroid can fix that. But yup your radio is stuck at 5.08 until you flash over it with a newer/older radio image.
Thank you very much! It its all done now
Sent from my Nexus One using XDA App
Actually there was one more thing. When I set the dialer led color to be red it stilshows up as white when the call comes in
Sent from my Nexus One using XDA App
so before any of us have to answer this question again please read this thread
so with dzo's port of the newest kernel he started including a wlan.ko compatible with the newer 2.6.32.nbh's into his builds. this left small fragmentation issue with people still using the older kernel
so when you use android on any of the phones in our project your nbh/ zImage is where your kernel is
so you have 2 options for your .nbh/zImage their are
2.6.25 (older kernel)
2.6.32 (newest kernel)
the older 2.6.25 kernels are available on dzo's site (should be a link to it in the first post of this thread) the last one he made was 26-07-2010 (what i use on my touch)
the newest kernels 2.6.32 are avalible for download from the kaiser kernel thread
if using a 2.6.25 kernel you need an update for the wifi this is attached to this post
now those instructions are assuming you have a kaiser if you have a polaris you need the wifi update for it reguardless the one for the 2.6.32 kernel that is also attached
for older polaris kernels i am not sure where the wifi update is for it but a forum search should find it easily if you know what your looking for
and lastly if your on a vogue, wifi will never ever work ever so stop asking
i think that should cover it if i missed anything everybody feel free to chime in (also if this could get stickied that be great)
Good stuff, glad to get that off your chest?
Haha does it show?
Sent from my HERO200 using XDA App
perfectly working
This should be stickied tbh. This question is one that pops up the most followed by questions about .nbh's. Such as how do I edit them, how do I use a vogue rom on my kaiser, etc.
Mind awfully if I link this in my mini-faq, since it's definitly a frequently asked question
Sent from my HTC Dream using Tapatalk
zenity said:
Mind awfully if I link this in my mini-faq, since it's definitly a frequently asked question
Sent from my HTC Dream using Tapatalk
Click to expand...
Click to collapse
please do, i wrote this for the intent of not having to answer it again so if people use the FAQ like they should to start it will make for way less hassles
well it's sitting at near 7000 views, so it's getting looked at
Just thought it would help keep it from getting buried
Help my WIFI doesn't work!
Just kidding
Thank you for organizing all of the answers in one place.
Sorry for bothering you but i can't install this update.
I just get "failed to extract" message after each attempt.
Hope someone can help me to solve this problem.
I've got kaiser with .25 kernel installed on it, system stored on nand and data on ext2.
Did you open the zip you downloaded or try to. flash it as is, if you flashed it as is that's your problem
Sent from my HERO200 using XDA App
Hi,
I am having problems getting any Android ROM to have working Wifi.
I have tried several different ROMs along with the corresponding Kaisimg.nbh generated using the NBH Editor and have tried applying the Wifi update after testing the 'virgin' install. Still no success.
I have an UK O2 Stellar. Could someone tell me a combination of NBH and ROM that has working Wifi (with or without the fix).
edit : just fixed by using the NBH from DZO's site instead of the Editor default.
thoughtlesskyle said:
Haha does it show?
Sent from my HERO200 using XDA App
Click to expand...
Click to collapse
What's an nbh? Just kidding
sorry for stupid question , but how can i instal this fix?
robgie said:
sorry for stupid question , but how can i instal this fix?
Click to expand...
Click to collapse
Extract wifi update zip file.
Copy androidupdate.tgz to Andboot Folder on your SD Card
Enter Android install menu
Select Install Update
Select Fix Permissions
Quit the menu and check wifi connectivity
Sorry for pushing this thread...
I had Fat Free Rom running for some months and now wanted to switch to an newer one. But I can't get WiFi working.
I tried:
Scoot Cyanogenmod RLS6
Thoughtlesskyle's Not So Super Froyo RLS18
New KAISER ROM Valentine 1.0.2
Krazy-Killa's Kernel Release - RLS5.9.1.2 Alpha
I also updated the Radio to
1.70.19.09 and now 1.71.09.01
and suggested or newest Kernels.
Furthermore I tried ALL fixes for WiFi I could find in this forum like:
http://forum.xda-developers.com/showthread.php?t=848921
http://www.ziddu.com/downloadlink/13294643/androidupdate-unpack-me.rar (from valentine)
and of course the updated linked here.
What's wrong with my Kaiser? WiFi never worked at first offence in Android and even with FatFree I needed to fix it (forgot how I did ^^, guess with new Kernel)
did you use the update with the Krazy-Killa kernel before posting?
What do you mean? ^^
I downloaded this http://forum.xda-developers.com/showthread.php?t=980551 and used atools to get "RLS 5.9.1.2 NBH.7z" and "HAReT Kernel Files.tar" into 1 file. Afterwards I flashed it.
im on the cache kernel 2.6.32 and im having problems with wifi. everytime i try to turn it on it says error
wifi worked fine in the super froyo, but it doesnt now that im on the dzo rom. i tryed to install the update from the cache kernel rar file and it failed to exract. its a androidupdate.tar file
I havent actually seen the Cyanogen Rom/Vibrant thread so I figured Id start one. So after my buddy put it on his captivate, I figured I would take the plunge and I would try it on the Vibrant. I was running Obsidian v5 and ported right from that. I take no credit for this, aside from doing it, Give the devs the credit, there the one keeping the community going.
GOES WITHOUT SAYING I AM NOT RESPONSIBLE FOR YOUR PHONE! FLASH AT YOUR OWN RISK
Steps for Flashing
Source:Cyanogen i9000 forum
1. Make sure your phone is fully charged! Update process will take some time.
2. Make sure that you've not applied any lagfix to your phone. Otherwise remove it!
3. Make sure you're actually on JPM Firmware or newer. If not, flash and boot into it. We need this Modem Firmware!
4. Download initial Kernel (Link).
5. Download CyanogenMod Beta3 (Link) and copy it onto your internal sdcard. Don't extract!
6. Optional: Download Google Addon (Direct DL Link) and copy it onto your internal sdcard.
7. Make sure you have more than 500 MB free space on internal sdcard.
8. Flash initial kernel "CM-GalaxyS-Kernel-initial.tar" as PDA via odin (no pit, no repartition).
9. Reboot into Recovery
10. Do a Nandroid Backup. Choose "Backup and Restore", then "Backup". It's very important!
11. Go back and do a factory reset / data wipe. It's really necessary otherwise your phone won't boot.
12. Choose "install zip from sdcard" -> "choose zip from sdcard", choose CyanogenMod and apply it! This will take some time!
13. After this your phone should boot. Don't touch it for a few minutes (4-5), it has a lot to do.
14. OPTIONAL: Enable Wifi, reboot to recovery and flash Google Addon (choose "install zip from sdcard" -> "choose zip from sdcard" -> "gappsXXX"). Reboot!
15. Setting up your google account can take some minutes. After this you should enable Wifi immediately!
Click to expand...
Click to collapse
Addons
BRAND NEW JK6 modem (for da speedz)
Thanks to scrizz, he was nice enought to pull out the JK6 modem from the latest released samsung code and I just flashed it and am getting WAY faster network speeds. You can get it from his thread here. Just flash thru CWM and reboot. Let it sit a few minutes and reboot again just to be safe. (I noticed weird hangups and after the second boot it was better)
Eugene Kernel 13 CWM (OC/UV tweaked)
~ Scaling tweaks
~ Battery Drain Tweaks
~ OC / UV
~ 1.12GHz OC
~ 100MHz to 400MHZ voltage drop is -50 / 800 to 1.12 is -25
~ To get more Battery Life, Disable 3G when not using Data! 2G works Fine regarding battery life.
~ Kernel Panic's Fixed
~ Wake issue's Fixed
~ OC App's Now work Fine without issue ( SetCPU / OC Widget )
Direct Download > Here
Click to expand...
Click to collapse
Installed it last night and Initial thoughts... AWESOME. Granted yes this is still very beta and buggy. Other than that, flash went smooth and have only noticed a few things.
Noticed Issues
Cyanogen Issue Tracker
1. Haptic feedback doesnt work outa the box
2. Installed better kb for kb haptic feedback, but the 4 btns on the bottom still dont have it.
3. Fixed with Eugenes Beta3 kernel You have to install the toggle headset widget and set it at every boot
4. Fixed with Eugenes Beta3 kernel Seems the Home and Back buttons act the same sometimes. (Hit home and it goes back)
5. Havent heard 1 issue about this on the vibrant My buddy on the captivate noticed on his that every call the hearing got worse for the person on the other side, and the other person had a hard time understanding him
6. Disreguard Angry Birds and a select few other apps causes an acore FC, followed by a "stopped unexpectedly" FC
7. Camera display is B/W but it does take color pics
8. Fixed WirelessAP doesnt work (fixed per codeworkx twitter) Use wifi Tether pre_15
Click to expand...
Click to collapse
Battery Test
After a fresh Cyan install, and the JK6 modem, I wiped the battery stats and let it go overnight with minor texting(in 3g and HSDPA)
13hours 31min and it died
Click to expand...
Click to collapse
COOL feature, Somehow, the apps I had installed before were pushed from Obsidian v5 and now to Cyanogen. I didn't reinstall them but they are still there. lol
Other than that all the gApps work, texting, fbook, phone (except for the talking issue I mentioned earlier which I havent tested on the vibrant yet), tweetdeck
VERY smooth and I think ill be on it from here on out.
Enjoy.
GIVE THE dev teams the credit they deserve. I just flashed the rom, they did the work. They get the credit.
Developers:
cyanogen - http://twitter.com/cyanogen
codeworkx - http://twitter.com/codeworkx
dumdidum - http://twitter.com/dumdidum
coolya - http://twitter.com/coolya
finghin - http://twitter.com/finghin
eugene - http://twitter.com/eugene_373
and a lot more!
Cool thanks. Im guessing this is not built off the new jk6 hotness?
Sent from my SGH-T959 using XDA App
mr.orange303 said:
Cool thanks. Im guessing this is not built off the new jk6 hotness?
Sent from my SGH-T959 using XDA App
Click to expand...
Click to collapse
I dont think so since I was mid-flash when I saw the tweet from samFirmware about the release. lol
mr.orange303 said:
Cool thanks. Im guessing this is not built off the new jk6 hotness?
Click to expand...
Click to collapse
Most certainly not. AFAIK, much of the point of any CM build is that it built from the AOSP source.
mr.orange303 said:
Cool thanks. Im guessing this is not built off the new jk6 hotness?
Sent from my SGH-T959 using XDA App
Click to expand...
Click to collapse
Just looked, its the jk2
Flashing now... perfect timing too, I just got a new vibrant.
a1cshowoff said:
Flashing now... perfect timing too, I just got a new vibrant.
Click to expand...
Click to collapse
Nice way to break it in!
Wasn't this already posted few weeks back...correct me if I'm wrong but u can't even make phone calls with this rom or something wasnt quite right with phone....i forget
Sent from my SGH-T959 using XDA App
demo23019 said:
Wasn't this already posted few weeks back...correct me if I'm wrong but u can't even make phone calls with this rom
Sent from my SGH-T959 using XDA App
Click to expand...
Click to collapse
I havent seen a CM6 thread after searching. I might be wrong but I made sure to look. If its a dupe sry :/
I was able to make calls right after I flashed, worked fine, you just have to make sure you have the Toggle headset enabled so it doesnt think theres a headset in there.
Yea I wasn't sure I never tested it just read something but couldn't remember but yea think its what you mentioned
Sent from my SGH-T959 using XDA App
how to enable toggle headset
yungballla6 said:
how to enable toggle headset
Click to expand...
Click to collapse
install the widget, long press on the home screen, add the widget, and click it and notice the headset icon in the upper notification tray go away
its a duplicate but nice fine all the same eugene posted a week or so ago its on his site as well. i heard its fast and has just under 3000 quadrant and 15ish linpack as is
so did you install a vibrant kernal after you got this up and running?
hotadef said:
its a duplicate but nice fine all the same eugene posted a week or so ago its on his site as well. i heard its fast and has just under 3000 quadrant and 15ish linpack as is
Click to expand...
Click to collapse
Just ran Quadrant = 2025
Linpack = 14.2
So not that fast. but come an official release I dont doubt that at all itll come close.
vortec87 said:
so did you install a vibrant kernal after you got this up and running?
Click to expand...
Click to collapse
Nope, odin'd the GalaxyS-Kernel.tar
Did the wipe
Flashed the rom and let it reboot, waited like 5 min,
Went to recovery lashed gapps and rebooted
sorry that guy used jfs overkill lagfix to get that score but 2000 is not bad with no lagfix installed. i wonder how much more performance can they squeeze out of this phone. its plenty fast enough to do anything. but a hobby is a hobby
Umm theres a better version (a vibrant version) put out by eugene. Plus you should flash the stock 2.2 kernel to fix the buttons. Been running cm6 for a week now
Edit. When tring to flash a new kernel on this beta version from the i9000 remove the ext support or flash a kernel with ext2/3/4 support built in.
Sent from my vibrant
blackerwater said:
Umm theres a better version put out by eugene. Plus you should flash the stock 2.2 kernel to fix the buttons. Been running cm6 for a week now
Sent from my vibrant
Click to expand...
Click to collapse
You have the link for eugene's build?
Its on eb-productions.com under vibrant.
Sent from my vibrant
Probably is something on my Nook Color. But since I upgraded yesterday from 41 to 7.0.2 there is noticeable degradation of youtube videos playing on the default browser. Used to be fluid now is very choppy.
About the NC
Stock ROM 1.20 (upgraded yesterday)
CM 7.0.2 (from SD using Verygreen's instructions)
NO other kernel changes
EDIT: I think I confused everyone on my post..
I meant that I kept the NC stock ROM and upgraded to the new one (1.2) released by B&N on 4/25
The NC is running CM 7.0.2 from uSD without kernel changes. CPU settings: Performance. Max: 925Mhz
Haven't had that problem, have you tried flashing with the new kernel, OC at 1.3, check it out... that might help.
Do you know if after updating CM7 I need to reset or clear something?
I guess that could be the cause of my issues.
There's a 1.3 kernel??? Dalgrin's? Where?
silentbushido said:
Haven't had that problem, have you tried flashing with the new kernel, OC at 1.3, check it out... that might help.
Click to expand...
Click to collapse
shawn605 said:
There's a 1.3 kernel??? Dalgrin's? Where?
Click to expand...
Click to collapse
Kernel Manager app
Do not set the overclock on boot until you know its stable.
Have not had that You Tube problem here.
Dalingrin's beta kernels are up to 1.2 and 1.3 I believe; but they are beta; 1.3 would not load on my CM7.02 set up at all, and then you have to revert back to get your tablet back. Others are reporting it is working fine, but the safe bet is to wait until he officially releases one IMO.
LBN1 said:
Have not had that You Tube problem here.
Dalingrin's beta kernels are up to 1.2 and 1.3 I believe; but they are beta; 1.3 would not load on my CM7.02 set up at all, and then you have to revert back to get your tablet back. Others are reporting it is working fine, but the safe bet is to wait until he officially releases one IMO.
Click to expand...
Click to collapse
The 1.3ghz is ready to release. It is just a matter of whether your Nook can handle the overclock or not. It should boot regardless though. The overclock is not set until after the OS boots to UI.
did you have OC before installing 7.02? installing 7.02 resets your cpu back to 800 MHz, and you need to reinstall OC kernels to get it back to what you had before
lanzagas said:
Do you know if after updating CM7 I need to reset or clear something?
I guess that could be the cause of my issues.
Click to expand...
Click to collapse
Been using the 1.3 oc kernel flashed through kernel manager. Seems to be working fine at 1.3 with oc set in cm settings.
No YouTube issues for me on new cm7.
Loving my week old nook color so far.
Sent from my HTC HD2 using XDA App
I didn't have a OC kernel before nor after.
I was using CM7 CPU settings. Max:925Mhz.
I had the 1.1 stable overclock before and currently am using it again. When I added the 1.3 uimage onto my Nook and tried to reboot, it stopped before the CM7 logos popped up. Blank screen with a "-" cursor and that's about it.
Glad to hear it is almost ready to be released, and will certainly try it again.
Oh, thanks Dalingrin for all your hard work on the kernels!