[USER] CM7 General Discussion thread
- Thread starter dalingrin
- Start date
In v11 change the LCD density to either 168.33333 or 169.33333. i have used both and they both work really well. That seems to be the sweet spot right now for alot of the apps.
First off, I applaud your thoroughness!The issue is with SetCPU's profiles. You can use the app, just don't enable Profiles yet.
UPDATE:
I have been testing the use of profiles with every nightly and oc kernel from Dalingrin and as of right now, it appears that nightly 11 and the 022511 dated oc kernel for cm7 are working just fine with profiles enabled... will be testing some more.
FYI: (My nightly 11 upgrade process)
-updated to CWR v3.0.0.9 via ROM Manager; powered off; powered on; using ROM Manager - Reboot into Recovery
-working CWR v3.0.0.9; created nand backup of nightly 8; reboot
-downloaded nightly 11; copied to SD card via Samba (i love that app)
-using ROM Manager - Reboot into Recovery
-wiped cache and dalvik; manual reboot since CWR still locks after wiping dalvik sometimes
-using ROM Manager - Reboot into Recovery
-installed nightly 11 zip; installed dalingrin's cm7 oc kernel 022511; reboot
-using Root Explorer edited build.prop lcd density to 161 (169.33333 makes my clock widget look wonky); reboot
-used Dalingrins workaround for market (uninstall updates; no data or cache to wipe; deleted data for Google Services Framework) via 'Manage Apps' in settings; reboot
Market works, updated all apps. Rebooted (cause they always showed the first time anyway for me, it was all subsequent tries that broke) and My Apps still showing.
Proceeded to testing SetCPU w/ profiles and all is well so far. Monitoring my CPU the entire time I wrote this post and it hasn't moved past 2%, generally sitting between 0%-1%. That's what I call idle.
Edit: SetCPU profiles still don't work. Once the cpu was stressed via an app, it stayed pegged. Oh well.
Just a quick note...
When you reboot after wiping chache and dalvik, you should reboot back into recovery. It is my understanding that dalvik is rebuilt on first boot. So if you reboot into android and go through ROM Manager, you would need to wipe dalvik again.
Somebody correct me if I am wrong, but I am pretty sure that is how it works.
Yeah I set it to 160 which is the default for the nook right? And my market and everything works out of box... so I may just run v11 for a while given the screen density being set to its native state.
...wiped /cache
...flashed nightly 12
...flashed oc kernel
-booted fine
-market/MyApps ok without any fix (yet)
-some apps not upsizing that used to (unblock, tic tic)
-setCPU profiles still pegs cpu
Overall, nothing major except maybe not having to adjust lcd density for market to work steady
Edit - after reboot:
-market opens, but no carousel or MyApps
--Dalingrins work around clearing cache and framework data did NOT fix
--changing lcd density to 161 and rebooting: does fix (so now the issue seems to be a pure lcd density issue and not cache/data/etc) ?
still playing around.
...flashed nightly 12
...flashed oc kernel
-booted fine
-market/MyApps ok without any fix (yet)
-some apps not upsizing that used to (unblock, tic tic)
-setCPU profiles still pegs cpu
Overall, nothing major except maybe not having to adjust lcd density for market to work steady
Edit - after reboot:
-market opens, but no carousel or MyApps
--Dalingrins work around clearing cache and framework data did NOT fix
--changing lcd density to 161 and rebooting: does fix (so now the issue seems to be a pure lcd density issue and not cache/data/etc) ?
still playing around.
Last edited:
Just an update on my earlier question.
Using CPU Tuner with the profiles on, the CPU seems to scale just fine. I used Process Monitor and the most CPU usage I could get at any given time was ~50% while playing Gun Bros (40% with Angry Birds). As soon as I exited the app, CPU usage came back down to normal. It also let me visualize the frequency changes, and it seems like everything is in order. I'll continue monitoring, but I think it is safe to use CPU Tuner with the profiles on.
P.S. Can someone let me know in which instances SetCPU pegs the processor at max? I'd like to see if I can replicate it with CPU Tuner. Thanks.
Using CPU Tuner with the profiles on, the CPU seems to scale just fine. I used Process Monitor and the most CPU usage I could get at any given time was ~50% while playing Gun Bros (40% with Angry Birds). As soon as I exited the app, CPU usage came back down to normal. It also let me visualize the frequency changes, and it seems like everything is in order. I'll continue monitoring, but I think it is safe to use CPU Tuner with the profiles on.
P.S. Can someone let me know in which instances SetCPU pegs the processor at max? I'd like to see if I can replicate it with CPU Tuner. Thanks.
Hey folks I hope you all know you do not need to use any of the Market CPU adjustment apps to OC. Cyanogen has it built into it. Go to Cyanogen Settings and its under Performance.
Yes, I've noticed that, but having different profiles for "Screen off" and "Low Battery" is nice. That being said, since I just downloaded the process monitor and tested for 30 mins, I'm not sure yet it it is switching over to the low batt setting. I'll keep watching it.
Sure... with setCPU, all you have to do is Enable the profiles and wait about 2-5 seconds, the cpu ramps up and stays. don't have to DO anything, odd.
It's not the OC ability I want, it's the profiles so I can squeeze battery life by dynamically underclocking when power isn't needed... I'm gonna try CPU Tuner out.
Current build: v12
Customizations: None
USB Mass Storage not connecting to PC: Flashed v12 directly over v11 without wipe
Steps to reproduce the problem:
1) pull down notification bar
2) pressed 'USB Connect' notification.
4) NC jumped to USB Mass Storage screen.
5) pressed "Turn on USB storage" button
6) NC goes to "Turn off...' button few 2 - 5 seconds, reverts to home screen and SD card is prepared according to notification status bar. NC never connects to pc
Edit:
7) goto settings and turn off USB Debugging, goes to USB Mass storage screen.
8) press "Turn on..." button and NC connects. Able to view files on pc.
Describe the issue as well as you can:
USB Connect to PC issue-no longer cycling through connect/disconnect, but still does not connect to view files on SD card.....Edit: until USB deubbing is de-selected in application -> Development section. Attaching additional log files.
Relevant logs(logcat, dmesg)
logcat and dmesg attached
Customizations: None
USB Mass Storage not connecting to PC: Flashed v12 directly over v11 without wipe
Steps to reproduce the problem:
1) pull down notification bar
2) pressed 'USB Connect' notification.
4) NC jumped to USB Mass Storage screen.
5) pressed "Turn on USB storage" button
6) NC goes to "Turn off...' button few 2 - 5 seconds, reverts to home screen and SD card is prepared according to notification status bar. NC never connects to pc
Edit:
7) goto settings and turn off USB Debugging, goes to USB Mass storage screen.
8) press "Turn on..." button and NC connects. Able to view files on pc.
Describe the issue as well as you can:
USB Connect to PC issue-no longer cycling through connect/disconnect, but still does not connect to view files on SD card.....Edit: until USB deubbing is de-selected in application -> Development section. Attaching additional log files.
Relevant logs(logcat, dmesg)
logcat and dmesg attached
Last edited:
Hell yeah. + DolphinHD in desktop mode = You tube.... woot!
Take that iFad2
How is the performance for you?
It's a 100% slideshow for me, about 1 fps.
Is it smooth for you in the browser, and if so, how?
Sent from my NookColor using Tapatalk
Same as u....smooth at times but when there's alot of movement its like 1 fps ....better than nothing....audio is clear though..
I don't understand how TV show stream app works so well with video...smooth as heck on the nook but YouTube wont work...or works like at 1fps haha....I dunno ....I'm no dev so I'm clueless haha..
Sent from my NookColor using Tapatalk
Sent from my NookColor using Tapatalk
ok, it's not just me. I haven't played games much the last few days, but I swore that some of my apps that used to size with an earlier nightly didn't anymore... it amazes me how much lcd density seems to be causing disruptions.
I am not able to connect my NC CM7 through my Droid 1 Adhoc. I have not used the adhoc patch for other roms and have tried using the Wireless Tether and Barnacle apps. Wireless Tether will not connect at all while Barnacle seems to connect but I can not get to the internet. Any suggestions?
Note: I apologize if this is not the correct thread for this question. I did search this thread on this topic and while I found other mentions of the problem, I did not come across a solution.
Note: I apologize if this is not the correct thread for this question. I did search this thread on this topic and while I found other mentions of the problem, I did not come across a solution.
Honestly guys everything works perfectly for me at 169.33333 . I have cm7 running with no tweaks. Each update I have flashed over the previous one. I skipped from v5 to v8. beyond that i have flashed OC both with and without reboots inbetween.
My understanding is that 169.33333 is the stock setting. Am I missing something cm7 devs? Is there a reason not to make this the default for build.prop? Just asking to learn, not to criticise.
Similar threads
Top Liked Posts
-
There are no posts matching your filters.
-
50In an effort to completely document the "Going to CM7 and Coming Back from CM7" experience for myself and my fellow rooters, I have compiled the following diary of install. Please let me know if there are missing steps or extraneous steps that can be removed. Remember please that I am trying to COMPLETELY document the process (at least as much as pertains directly to CM7) and the audience is for everyone, even real noobs who you know will be trying this and crying about some dumb mistake. Thanks for your feedback.
Before beginning:
1. Booted into Recovery
2. Created new nand backup
3. Removed and stored MAIN sd
Using a new and different sd:
1. created 4gb CWR_ext4_0.1 bootable SD [Followed process here: http://xdaforums.com/showthread.php?t=959240]
2. moved flashable zip of CM7 to SD [edit: now using latest nightly found here: http://forum.cyanogenmod.com/forum/228-nightly-builds/]
3. moved latest gapps to SD [Found here: http://wiki.cyanogenmod.com/index.php?title=Latest_Version/Google_Apps
4. moved latest Froyo/CM7 overclock kernel to SD [Found here: http://xdaforums.com/showthread.php?t=925451]
4. insert into NC
Installing
1. boot with bootable sd (CWR_ext4_0.1 - ClockworkMod Recovery v3.0.0.6)
2. 'mounts and storage' --> format /system ; /data ; /cache
3. back to main menu
4. 'install zip from sdcard' --> 'choose zip from sdcard' --> select "latest_CM7_nightly.zip"
5. 'install zip from sdcard' --> 'choose zip from sdcard' --> select "gapps-gb-20110120-signed.zip"
6. 'install zip from sdcard' --> 'choose zip from sdcard' --> select "update-1100mhz-froyo_CM7-emmc-cwm.zip" [if desired]
7. 'mounts and storage' --> unmount sdcard --> remove sdcard
8. reboot
First Boot
1. (got chills seeing that little cm7 droid boot animation)
2. @ Welcome to NookColor --> waited full 5 minutes for system to settle (?)
3. tapped Droid to begin setup
4. waited for Notification Bar to show WiFi available --> dragged down to open
5. Selected my router and logged in
6. Used built in 'Back Button' in top right of notification bar to go back to setup
7. @ Set up your Google Account --> signed in
8. @ Market Apps Installer - IMPORTANT: Read This! --> OK
9. @ Choose the apps to install --> preference i guess (gmail and google search were already installed - I added YouTube) --> ok
10. above took me to YouTube install screeen from market, seleceted Install then OK
11. @ Use Google Location --> i uncheck both since it's not a phone --> Next
12. @ Back up data --> i uncheck again --> Next
13. "Your Google Account is now linked to this phone" --> Finish setup
14. now to set time prefferences --> personal preference here (set time zone and current time will adjust) --> Next
15. WOOT! CM7 Home Screen!
16. Open Apps --> Settings --> CyanogenMod Settings --> Lockscreen --> Style Options --> Lockscreen style --> change to Sliding Tab (this is because the Rotary wheel isn't sized right yet and is real hard to use currently)
17. back @ Settings --> Applications --> check allow for Unknown Sources
18. open Market --> downloaded Titanium Backup
19. Ran batch restore to replace missing user apps
20. Open and tested each user app (some worked, some didn't - but it's early)
First Backup
1. Power off NC
2. boot with bootable sd (CWR_ext4_0.1 - ClockworkMod Recovery v3.0.0.6)
3. 'backup and restore' --> 'Backup' (this creates nand backup to the SD card of the installed system)
4. 'mounts and storage' --> unmount sdcard --> remove sdcard
5. reboot
First Nightly Update
1. Download latest nightly (http://forum.cyanogenmod.com/forum/228-nightly-builds/)
2. Place new file onto the bootable ext4 SD
3. boot with bootable sd (CWR_ext4_0.1 - ClockworkMod Recovery v3.0.0.6)
4. 'install zip from sdcard' --> 'choose zip from sdcard' --> select "latest_nightly.zip"
5. 'install zip from sdcard' --> 'choose zip from sdcard' --> select "update-1100mhz-froyo_CM7-emmc-cwm.zip" [if needed, at this time the nightly will restore original clock speed]
7. 'mounts and storage' --> unmount sdcard --> remove sdcard
8. reboot
Restoring a nand backup of CM7
1. Power off NC
2. boot with bootable sd (CWR_ext4_0.1 - ClockworkMod Recovery v3.0.0.6)
3. 'backup and restore' --> 'Restore' (select the backup you wish to restore - usually one with most recent date)
4. 'mounts and storage' --> unmount sdcard --> remove sdcard
5. reboot
Reverting back to any other AOSP
********************************
**This requires having a seperate SD card or overwriting the image of the ext4 card
**All files needed are available as part of the
** "Monster RootPack/Clockwork Recovery 3.0.0.5 SD" [http://xdaforums.com/showthread.php?t=922870]
** "Nook Color Restore to Stock" [http://xdaforums.com/showthread.php?t=914690]
**You will need the following files:
** CWR-removal.zip (both threads have a CWR removal file or two, take your pick)
** repartition-boot-with-stock.zip
** your most recent NON-CM7 nand backup -OR- your preferred stock recovery .zip
********************************
1. Power off NC
2. boot with bootable sd (original_CWR - ClockworkMod Recovery v3.0.0.5) [one made using the Monster RootPack thread]
3. 'mounts and storage' --> format /system ; /data ; /cache (this is for good measure)
3. back to main menu
4. 'install zip from sdcard' --> 'choose zip from sdcard' --> select "CWR-removal.zip"
5. 'install zip from sdcard' --> 'choose zip from sdcard' --> select "repartition-boot-with-stock.zip"
*********************************
** If restoring to a nand backup, skip to step 9
*********************************
6. 'install zip from sdcard' --> 'choose zip from sdcard' --> select "nook-complete-restore-1.0.x.zip"
7. 'mounts and storage' --> unmount sdcard --> remove sdcard
8. reboot (you should boot to stock and unrooted)(AND DONT DO STEPS 9-11) [you can now re-root with autonooter instructions]
*********************************
** Only complete these steps if restoring a nand backup and NOT restoring to stock
*********************************
9. 'backup and restore' --> 'Restore' (select the backup you wish to restore - usually one with most recent date)
10. 'mounts and storage' --> unmount sdcard --> remove sdcard
11. reboot (you should be back to a working version, rooted and full of joy)43Signal bars
Signal icon should be fixed in next nightly: http://review.cyanogenmod.com./#change,10233
SOD
Also, please test the kernel. This silly SOD problem is the bane of my existence because I cannot reproduce. Really need someone to give feedback on that kernel so I know how to move forward.
ICS
Work is underway to get legacy device(thats us) to work with ICS. These legacy hal changes will make it easier to support the Nook Color but we still need to either backport DSS and SGX drivers for update to a new kernel. Both of these options are a good bit of work and won't happen overnight so please be patient. =)332.6.32 kernel for CM7 is mostly complete.
+ Sleep fixed
+ Able to build a new wifi module finally. *Should* fix wifi issues.
- Hardware overlay does not work
- No bluetooth yet. We are trying a completely different method to init and communicate with bluetooth. This will take a little time.
No hardware overlay causes higher resolution videos to be a little choppy. I am going to continue to work on this tomorrow and hopefully have something to post.28QUICK FAQ - 2/19/11
Q: WHAT IS THIS?
A developer port of Cyanogenmod 7 for the encore device, which has been in development for about two months starting in early January and has only recently been deemed good enough for a wider range of developers to use.
Q: WHERE TO GET NEWS ON PROGRESS?
I will tweet progress from time to time.
Twitter: @dalingrin
We are usually in #nookie on freenode.
You can always check the Cyanogen git@ http://github.com/cyanogenmod
Q: WHAT WORKS AND WHAT DOESN'T?
As of this writing, most things do work-- touchscreen, wifi, sound, accelerometer, etc.
See the issue list here: http://xdaforums.com/showthread.php?t=960537
Q: How do report a bug I find?
PLEASE post logs to pastebin.com and include them in your report.
To grab android logs you can run "adb logcat -d > log.txt"
This will output the log to the log.txt file and can then be posted on www.pastebin.com
Kernel logs can be had by running "adb shell dmeg > dmesg.txt"
This will output the dmesg log to dmesg.txt for easy posting on www.pastebin.com
Use this template to post a bug in this thread:
--------------------------------------------------------------------------
Which build are you running? Please mention any customizations:
App or process having the problem:
Steps to reproduce the problem:
Describe the issue as well as you can:
Relevant logs(logcat, dmesg)
----------------------------------------------------------------------------
Q: WHO PORTED THIS?
Cyanogenmod itself is the creation of thousands of developers.
A vast team from around the world including members of Team Douche as well as unaffiliated individual developers have been collaborating for about two months on this port. Additional contributions continue to come from around the Internet. You are invited to help by contributing YOUR fixes.
Q: WILL CM7 RUN OFF OF AN SD CARD? OR DOES IT USE THE INTERNAL STORAGE OF MY DEVICE?
The nightly builds are intended to run entirely off the internal storage device. Should you decide to install one of those .zip files, you should expect to overwrite whatever was installed in those partitions.
It is critical to understand that CM7 is development software that may cause serious issues, loss of data, and/or other problems with your device and to your life in general. By loading and/or running the software, you must understand and accept full responsibility for your actions and all consequences and agree to adhere to the varied licenses and terms and conditions that comprise the software.
Q: IS THERE AN SD-ONLY "BOOTABLE" VERSION?
Not from the nighty builds. However-- should someone want to create such a bootable SD-- (warning: Slightly technical answer all it would take to create one is a new uRamdisk file with the partitions in init.encore.rc pointing to the correct partitions on the SD card.
Q: I AM AWARE OF THE RISKS AND ACCEPT RESPONSIBILITY FOR WHATEVER RESULTS. WHERE DO I GET THIS?
Cyanogenmod 7 for encore is available as a nightly build. See the XDA dev thread for download and development discussion:
Q: WHAT IS "ENCORE" ANYWAY?
Cyanogenmod has a fun little convention to name ports after the device's original project name.
Q: WHERE IS THE SOURCE?
On Github.com.
Q: I'M A "TECCHY" PERSON-- WHAT KERNEL DOES THIS USE?
A somewhat-modified version of the "stock" 2.6.29 source provided by Barnes & Noble (in accordance with the GPL). Changes to this kernel include a fix for a temperature bug, a fix to a cache race-condition resulting in kernel panics, ext4 support, and support for large block devices, among other things.
A port to 2.6.32 is currently underway that may facilitate improved "deeper" sleep.
Q: IS THE KERNEL OVERCLOCKED?
Just like the original stock kernel, the CM7 kernel runs at 800Mhz. However, you may overclock the default kernel to 925mhz through Cyanogenmod Settings. Cyanogenmod has a policy to not include voltage modified kernels. If you want a faster overclock see Dalingrin's 1.1 Ghz kernel: http://xdaforums.com/showthread.php?t=925451
Use entirely at your own risk.
Q: WHAT ARE THESE OTHER VERSIONS OF CM7-BASED ROMS?
Because CM7 is open-source software, people are free to modify it as they wish and re-release, provided they are compliant with the terms of the original licenses. The CM7 developers have nothing to do with these derivative releases, which may or may not be of decent quality.Q: WHEN WILL THE FINAL VERSION BE RELEASED?
When it's ready. Please do not ask this, as it is considered the mark of a newb. In the meanwhile, nightlies are rolling out every evening with the improvements from that day, not only to the encore port in particular, but to Cyanogenmod in general.16
I created flashable zips that just installs the files needed to fix the signal bar issue and wifi driver to prevent SODs. I have shown the links below. Just install with CWM Recovery or ROM Manager. To install with RM, go to "install ROM from SD" and follow prompts. Be sure to choose "wipe Dalvik". These work with emmc installed CM7. I don't know if they work with SD installs.
This zip is for CM 7.1 stable and recent nightlies that have the 2.6.32.9 kernel. (Look in settings/about tablet)
Install zip (SOD fix only):
http://d01.megashares.com/index.php?d01=8VPCE7N
I am also including a zip for recent nightlies (234 and above) that have signal bar issues.
Install zip (SOD fix and signal bar fix)
http://d01.megashares.com/index.php?d01=KFyOSYg
I am also providing the links for just the files if you want to install them manually.
Wifi driver/module:
http://www.mediafire.com/?61b1nzzt8kq62hx
Signal bar fix:
http://d01.megashares.com/?d01=ed8d5d9
Thanks to Embedded and Keyodi for the original files.
New posts
-
-
TCL 2022 Google TVs (P635/P735/C635/C735/C835/C935)
- Latest: garethk1979