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!
Related
Normal: http://www.tabbal.net/files/Dragon-Kernel-Voodoo-v3.1.2.zip
OC: http://www.tabbal.net/files/Dragon-Kernel-Voodoo-OC-v3.1.2.zip
I rebased on the latest source from Samsung, JPX. Yes, it's still i9k based. Hopefully it helps a little with battery and such, won't know till it's been out for a while. The speedmod patch has also been updated, but the OC patch is the same. I also included my backport of the auto-group scheduler patch. So far, both of them are working well for me.
Both kernels are voodoo enabled and will enable voodoo if you don't already have it. If you don't want that, you need to install the voodoo-disable zip before flashing, or just put the disable-lagfix file in place before flashing. If you already have voodoo enabled on your phone, you do NOT need to disable it before flashing these kernels, as long as your current kernel has voodoo recovery (red Clockwork recovery), you are good to go.
Tested on Nero V5, but should work on other Froyo based ROMs as well.
If you are going to try the OC version, please download both of them and have the normal version ready, just in case. You can also use adb push from Clockwork if you can get it booted to recovery. Clockwork also has USB storage you can enable to be able to mount your phone's memory cards from a computer, so that you can put the non-OC version on there if you get stuck.
NEW for OC users.
The OC kernel defaults to 1Ghz. To enable OC, you can use the Voltage Control app that the OC ZIP installs for you. This is a MODIFIED version, so please don't update it. Load the app, then pull up the "states" drawer at the bottom of the screen. Select the frequencies you want to enable. Then set the "Limit clock to" spinner to set the max clock rate the system will use. You can change the UV settings if you like as well. To test, hit menu then apply for now. When you are happy, use "save as boot settings" and the system will set the frequencies at boot. I recommend you only change one thing at a time, and throughly test, before setting at boot. Bad OC/UV settings can cause all sorts of instability issues. Flash the stock clocked kernel if you get stuck, then delete /system/etc/init.d/S_volt_scheduler before flashing the OC kernel back on. That will force the system to boot limited at 1Ghz again. If you are so stuck you can't get to recovery, you can use download mode to apply a stock kernel with heimdall, just pull the zImage from the ZIP and flash that.
I'm not sure it will help anyone to post your OC/UV setup as every phone is different. But feel free to try it if you like. I haven't done much more than test that it can set the options and my phone is still running fine at 1280. I'll experiment with other speeds and such later.
Please note: Not every phone will work at any particular frequency. Many can run 1.4 just fine, others can't do much better than the stock 1Ghz. I recommend trying one step at a time, and testing throughly before setting at boot. Run some games and such to really push the system. I also recommend using only one or two OC settings enabled in the states. Every frequency step requires the system to notice you are asking for more CPU than the threshold, resulting in lag getting up to speed. I run with only 1400 enabled from the OC section and disable 200 just to speed up the transitions.
Changes from v3.1.1
Fixed sensors (auto rotation, auto dim screen, compass, etc)
Updated OC code to be more stable, courtesy of Morfic. Many thanks to him for providing code and assistance.
Updated Voltage Control app to reflect the standard voltages used.
My phone runs stable at 1.4Ghz now.
Changes from v3.1:
Fixed Mobile AP on Bionix V.
Changes from v3.0:
Updated speedmod patch to k12p
Updated Voodoo Sound to V2
Credits:
Speedmod patch from here: http://forum.xda-developers.com/showthread.php?t=822756
OC patch from here: http://forum.xda-developers.com/showthread.php?t=822027
Supercurio for voodoo and voodoo sound
Sweet!! gonna test it out now..thanks for this!!
Downloading now
THANK U!! flashing right now (normal version)
just flashed it and for some reason screen looks dimmer (to conserve more battery i guess??) or is it just me? one more thing speedmod is not really necessary right?
So this thing helps with battery?
Sent from my SGH-T959 using XDA App
downloading now...was just thinking about flashing the new trigger rom from Einherjar to try it out....will flash this with it and report back any problems
Been running the OC kernel at 1280 with CFQ, everything runs smooth and lightning fast!! Not one reboot or freeze up. Linpack is in the 20's. Thanks again T!!!
Edit: had this running on my phone for almost 2 hrs
KA6 DeOdexed
Will this work on the KA6 DeOdexed leak rom with voodoo lagfix enabled?
So far, so good at 1.2
Nicely done. I had 2.7 for a few hours and it kept freezing up. Hope this is the sweet spot. Just for clarity, the only difference between "apply for now" and "save as boot settings" is that the settings will need to be re-done when rebooted? Sorry if that's a completely "duh" question. One more: having the Voltage Control app now, is it recommended to freeze or uninstall Set CPU, or does Voltage Control trump Set CPU, or, vice versa? I notice the main screen does theoretically allow the slide bar to go to 1.4. TIA...
It's running great. At first, it got stuck while flashing the kernel and I had to odin back but it's fine now.
As far as battery life is concerned, it has only been about two hours so I can't say. The kernel itself has voodoo sound v2 so even ttabbal hasn't had it for long (as that JUST came out) so no one will know what kind of battery life the phone has.
On a side note: ttabbal: Did you get my PM about the FM radio? Is the module loaded trying to access the non-existing hardware? I wonder if that is what's killing the battery on the non-vibrant kernels. (Doesn't the 959D also have a FM radio?)
I tried to push it to 1400 with cfq but got a freeze up instantly. Went back to 1280, now everything is running smooth again. One thing I noticed though, my wifi is broke
My wifi is working...did yours stop working after you pushed 1400?
w00t! thanks ttabbal for being the Dev to provide Voodoo sound!
Mine stopped at 1.4 too. But right now im running 1.2 with 25 under. 25 under on 1. 50 on most the others except 100 which I went 75 under. Right now its really stable and fast so ill leave it like this for boot and try other stuff with the apply now. Hint only hit on boot if its 100% stable. Be careful with setcpu too.
Sent from my SGH-T959 using XDA App
Fedburin said:
My wifi is working...did yours stop working after you pushed 1400?
Click to expand...
Click to collapse
Yeah..noticed it stopped after I pushed 1400.. So be warned
love your kernels. i will have to donate again
So does this kill the wifi hardware at 1.4? If so, ttabbal has to modify the first post. (Or I will do it if he doesn't and we start getting more people complaining.)
On another note: Voodoo sound = gooooooood
Anyone else notice the automatic brightness setting is WAY dark? I've been running the T959D dragon kernel and this one is alot darker by default.
Thanks for the heads up.
Sent from my SGH-T959 using XDA App
bahnburner said:
Anyone else notice the automatic brightness setting is WAY dark? I've been running the T959D dragon kernel and this one is alot darker by default.
Click to expand...
Click to collapse
yeah, its the new version of speedmod that he incorporated, link to that thread is in the op
Anyone have the latest Flash releasing today?
Other than the old leak, i still haven't seen it anywhere offically....
It's in the market. I dont know how much of a difference it makes since I didn't test it much.
Videos are def more stable now , when there in full screen there even better
what roms/versions are able to get flash from the market?
I'm able to get it from the Market on Nookie Froyo. The prior Market version did not work and I had to revert to the downloaded Flash101.apk. Thankfully 10.2 does work perfectly well so far =) I can't see any obvious improvements though.
doesnt work wid hc v4 2nd edition
On CM7, not only was it the featured app in the Market advertising space, it was also waiting to be installed as an update to 10.1
Cm7 flash 10.2 =
Spoke too soon. For some reason Flash 10.2 stopped working on my Nookie Froyo, but rolling back to the Flash101.apk worked.
Had Flash 10.2 working on Phiremod 5 (CM7). Worked fine for both flash video (given video slowness) and for flash games. Upgraded to day to Phiremod 5.1 and now can't get either Flash 10.1 or 10.2 to work in Browser. YouTube app working very well, tho.
Installed flash 10.2 last night on my froyo 0.68 emmc install from market (it wouldnt do thst for me last week). My stock browser and dolphin browser now successfully play flash and embedded movies.
I am most pleased.
Sent from my Nook Color (zoom2) using Tapatalk
Works great so far on nookie froyo for me. BBC video play smooth
glgehman said:
Had Flash 10.2 working on Phiremod 5 (CM7). Worked fine for both flash video (given video slowness) and for flash games. Upgraded to day to Phiremod 5.1 and now can't get either Flash 10.1 or 10.2 to work in Browser. YouTube app working very well, tho.
Click to expand...
Click to collapse
I can see it in market, but wont let me download. Download always fail..
Fro 2.2.1
Sweet Honey
Just completely remove flash and reboot and then it should install.
Sent from my Amazing Captivate using the XDA Premium App Infused with Tiger Blood
Wow not looking good based on the responses
pceasar said:
Wow not looking good based on the responses
Click to expand...
Click to collapse
Remember that the only stable installation of NC is the rooted stock B&N which is 2.1 and thereby does not support Flash at all.
SO, only unstable beta builds that change daily, support Flash.
The fact that some of the posters have it working is actually looking good to me.
Nookie Froyo is pretty stable already. The base build is not being tweaked much anymore. It's Gingerbread and Honeycomb that are still a big work in progress.
ADude said:
Remember that the only stable installation of NC is the rooted stock B&N which is 2.1 and thereby does not support Flash at all.
SO, only unstable beta builds that change daily, support Flash.
The fact that some of the posters have it working is actually looking good to me.
Click to expand...
Click to collapse
Sent from my Nexus One using XDA App
I can't even see Flash 10.2 in the Marketplace and I'm running Nookie Froyo. It's interesting to see that some are able to make it work.
EDIT: After reading through other posts, I decided to access the Marketplace through Dolphin. I can see it--but when I try to download it, I get the error message
"There are no Android phones associated with this account. Please sign in with a different account."
I don't have an Android phone. Any thoughts.
Great news, Hulu Plus is now available for 6 Android devices. I wonder if we can get an apk from a compatible smartphone and test it on Nook Color. The compatible devices are:
Nexus One, Nexus S, HTC Inspire 4G, Motorola Droid II, Motorola Droid X, and the Motorola Atrix
Update: Found it here
http://forum.xda-developers.com/showthread.php?p=14993003#post14993003
The app seems to work perfectly on my Nook Color running phiremod v6.3.
Not supported
Not supported on CM7 n102. Installs fine but wont play anything.
OK, tested it and works fine on my CyanogenMod 7.
soricon said:
OK, tested it and works fine on my CyanogenMod 7.
Click to expand...
Click to collapse
What nightly are you using ? Please and thank you.
Latest 7.1 beta and latest Dalingrin OC kernel.
Sent from my Nook Color
By latest 7.1 beta I assume you mean nightly 110?
When I run the app, I get a red and white message popup saying that my device isn't supported. It will allow me to login and manage my queue (big whoop), but it won't play anything.
I'm on CM7 nightly 106, Dal's OC kernel. Build prop is edited for manufacturer = HTC for netflix.
I tried changing my buildprop to match my Nexus one (all kinds of combos until it broke when I changed the processor type), but no joy.
Coincidentally, I am having problems on my Nexus One running CM7 stable (7.0.3-N1-signed). It will start playing, but immediately buffers and then complains about the network (I'm on WiFi).
Any ideas? I'll upgrade to nightly 110 after I run a backup.
rbenchley said:
The app seems to work perfectly on my Nook Color running phiremod v6.3.
Click to expand...
Click to collapse
Also running phiremod 6.3, app runs but when I click to view any show it force closes. You are able to view shows?
TPR300C said:
Also running phiremod 6.3, app runs but when I click to view any show it force closes. You are able to view shows?
Click to expand...
Click to collapse
Shows stream perfectly for me. Did you modify your build.prop or is it standard? Have you tried using using Rom Manager to fix permissions?
Works perfectly for me too. I'm CM7.1, Build GRI40. My NC thinks it's a "Nexus S" by "samsung" in name only. No fingerprint mods were made when I did this a while back to make Netflix work (which also runs great).
I found my APK here instead: http://forum.xda-developers.com/showthread.php?t=1136634
Well, CM7 nightly 110 didn't help. Switching to Phiremod 6.3 didn't make a difference. Tried Nexus S / Samsung in build.prop (after switching back to nightly 110) and not only did Hulu+ android app refuse video playback, Netflix is impersonating Alvin and the Chipmonks©.
Guess its back to HTC in the build.prop and waiting for an update to Hulu+ for me.
Oh, and the problem with my Nexus One constantly buffering was my modified hosts file for AdBlocking. I had to "Revert" to normal to get Hulu+ working on my N1. (It made no difference on my Nook either).
Question for folks that have it running on your Nooks: Did you ever modify your Flash player to get Hulu working in your browser prior to installing the dedicated app?
DiDGR8 said:
Well, CM7 nightly 110 didn't help. Switching to Phiremod 6.3 didn't make a difference. Tried Nexus S / Samsung in build.prop (after switching back to nightly 110) and not only did Hulu+ android app refuse video playback, Netflix is impersonating Alvin and the Chipmonks©.
Click to expand...
Click to collapse
I'm running the official CM 7.0.3 (Encore build) with stock / non-overclocked kernel. Your issue is likely kernel / overclock related. It could also be that the unstable nightlies don't work. Try a stable build.
epakrat75 said:
I'm running the official CM 7.0.3 (Encore build) with stock / non-overclocked kernel. Your issue is likely kernel / overclock related. It could also be that the unstable nightlies don't work. Try a stable build.
Click to expand...
Click to collapse
I don't think the OC is the problem (except for the Netflix Chipmonks, that's a "known issue"). To be sure I didn't load one until I restored my CM7 n110 install at the end.
Phiremod 6.3 includes an OC kernel and soricon reports that he or she runs dalingrin's OC kernel, so I don't think that has anything to do with it.
Phiremod is also based on 7.0.3 stable and soricon uses "latest 7.1 beta" (which I take to mean "latest nightly").
Those users are reporting a "functional" program. I just hope that means they have Hulu + accounts, have logged in, and have actually played videos in the app and not in the browser.
Those users are reporting a "functional" program. I just hope that means they have Hulu + accounts, have logged in, and have actually played videos in the app and not in the browser.[/QUOTE]
You are right, I do have Hulu+ account and it runs in the app just fine.
I am running the Phiremod test build (which is nightly 102) with the 061311 Kernel and it works great for me.
Did you do the WIN or IE6 mod to your browser? I am using Dolphin HD...in settings, go to USER AGENT and use CUSTOM. Under CUSTOM USER AGENT, enter WIN for windows.
In the stock browser under SELECT USER AGENT, use IE6.
That may be where your getting stuck.
dkymala said:
I am running the Phiremod test build (which is nightly 102) with the 061311 Kernel and it works great for me.
Did you do the WIN or IE6 mod to your browser? I am using Dolphin HD...in settings, go to USER AGENT and use CUSTOM. Under CUSTOM USER AGENT, enter WIN for windows.
In the stock browser under SELECT USER AGENT, use IE6.
That may be where your getting stuck.
Click to expand...
Click to collapse
We are discussing running the new dedicated app for Hulu+, not going to hulu.com in a browser. I was concerned that there might be confusion on that matter.
I am also interested in knowing whether or not anyone that *IS* getting the app to run had previously been using the modified flash program in a browser to access hulu.com
Thanks
DiDGR8 said:
We are discussing running the new dedicated app for Hulu+, not going to hulu.com in a browser. I was concerned that there might be confusion on that matter.
I am also interested in knowing whether or not anyone that *IS* getting the app to run had previously been using the modified flash program in a browser to access hulu.com
Thanks
Click to expand...
Click to collapse
I'm using a non-modified version of Flash on phiremod v6.3 and the hulu + app is streaming perfectly. When hulu + was announced the other day, it was not available to me in the market. I downloaded the apk from the Android development thread here on xda. Once I installed the apk with app installer and entered my hulu + account info, it just worked perfectly. No modified Flash, no modified build.prop. Let me know if there is any additional information that I can share to help out.
Thanks for the info. It looks like CM 7.1 stable is going to drop in the next build, so I'll get all my backups up to date and prepare a totally fresh install (wiping EVERYthing). I'll try Phitemod first, but I'm hoping CM will work.
I have a theory that the apk I harvested from my N1 originally hosed something deep and switching to the app from xda later never really "took". That or the Netflix build prop changes and / or brian21f's fixer app changed something deep.
We'll see
It's running fine on my NC - CM7.0.3 stable, hulu-fied Flash, have not changed the build.prop (although I tried and couldn't get it to write for some reason).
I used to have Hulu+ but discontinued it a few weeks ago.
I watched on of the free streams this morning and it looked beautiful.
How much I love this forum! Pherimod 6.3 and Hulu + is running perfectly on my NC.
When I plug my phone in to charge it stays at 800mhz instead of throttling down to 100-400mhz like its supposed to. I'm on pinnacle ROM and its taking forever to charge. Anyone else have this issue and maybe have a fix for it? Thanks.
Are you using Tegrak?
Yes, I do have it set to throttle down and using Ondemand scheduler.
Kill it and check if it get fixed. I recommend rebooting it after you change tegrak's settings.
Killing it seemed to have worked for now. How can I fix it so I can still overclock? It hasn't done it all the time, Just recently but I haven't installed any new apps or anything.
Sent from my Cappy using the XDA app.
Try clearing the app's cache. Maybe even Dalvik if you have too? Don't know.
I'll try, thanks man.
Sent from my Cappy using the XDA app.
well, getting rid of tegrak didn't help. Still charges and stays at 800mhz.
Sent from my Cappy using the XDA app.
Try unistalling it then installing it? I've used tegrak on 2.3.3 and 2.3.4 and never had any issues with it.
prbassplayer said:
Try unistalling it then installing it? I've used tegrak on 2.3.3 and 2.3.4 and never had any issues with it.
Click to expand...
Click to collapse
Tried that and still no difference......can't figure it out.
What Freq and Voltage you running on each level? Are you using Tweaks? You said you had it "Ondemand" scaling but what min-max Freq?
Edit: I decided to test Tegrak on a 2.3.5 Beta Fusion build, seems to work fine.
Edit 2: Flashed another 2.3.5 beta build and I got that problem you had. Ill keep looking in to it
prbassplayer said:
What Freq and Voltage you running on each level? Are you using Tweaks? You said you had it "Ondemand" scaling but what min-max Freq?
Edit: I decided to test Tegrak on a 2.3.5 Beta Fusion build, seems to work fine.
Edit 2: Flashed another 2.3.5 beta build and I got that problem you had. Ill keep looking in to it
Click to expand...
Click to collapse
It might be a problem with something included in Pinnacle but I can't narrow it down.
Ondemand 100min-1200max with stock voltage settings.
Na Fusion VII Beta is doing the same thing. I think its a tweak on the kernel maybe? I've been kinda busy and will be for the next few days, so don't know when I'll mess with different kernels.
I'll try the other kernel option and see what I can find.
Sent from my Cappy using the XDA app.
I'm having the same issues on continuum with latest talon kernel. And it's been installed on my phone for weeks now and the problem just started. I also have an issue with media server running constant and it gets the phone hot and drains the batt....not sure if the two things are related, but it all just happened all of a sudden.
rmntruexjr said:
I'm having the same issues on continuum with latest talon kernel. And it's been installed on my phone for weeks now and the problem just started. I also have an issue with media server running constant and it gets the phone hot and drains the batt....not sure if the two things are related, but it all just happened all of a sudden.
Click to expand...
Click to collapse
Using cpuspy or other monitoring software, what speed is it stuck at when charging? Are you running tegrak as well?
Sent from my Cappy using the XDA app.
Well tried a fresh install of Fusion and it still does it......
Geezer000 said:
Well tried a fresh install of Fusion and it still does it......
Click to expand...
Click to collapse
Ya Just used Fasty KI2 and It does it with out Tegrak. What ever it is, its anoying not enough to reflash to stock to check if its the rom or kernel.
prbassplayer said:
Ya Just used Fasty KI2 and It does it with out Tegrak. What ever it is, its anoying not enough to reflash to stock to check if its the rom or kernel.
Click to expand...
Click to collapse
I have flashed Fasty ki2, Fusion, Pinnacle, Apex and so far they all do it with or wothout tegrak.
Fresh look bump.....
model: SGS international GT-I9000
due to corrently hot topic ICS on air everywhere
so im going go give it a try
at the first whn im on 1.12.30miui rom with glitch kernel, i upgrade to OneCosmic 2.11 with glitch kernel too, i realize that my phone is hot, after that i use all the check what happen with my cpu keep running on max speed for few hours for DRM, Media storage and download manager...
after 1day of using on 2.11 i feel like not hitting my target of lagfree, so im changing bk to miui 1.12.30 and after boot up, i get the same thing happen again, my cpu keep running on max speed for same, seem like it keep running on scanning media storage.
i just want to know why it keep running like thay, can anyone give me a answer? or is it because of gallery+?
SGS GT-I9000 OneCosmic latest build!
onecosmic is still in beta is not final ics so there's bug, because the cpu heat is forced because of such applications that are open gallery
c0c05 said:
onecosmic is still in beta is not final ics so there's bug, because the cpu heat is forced because of such applications that are open gallery
Click to expand...
Click to collapse
i dont think so...
when i change back to miui 2.1.13 im also having the same problem...
SGS GT-I9000 OneCosmic latest build!