I have the CyanogenMod and It comes with 5 screens but I cant use advantange of it because my phone gets so slow.. I use like 5 widgets and everytime I go to my home its frozen for like 10 seconds untill eveything is loaded again. I have apps2sd so im wondering is their a way to make the G1 lightning fast because its acting so slow it was like this in the stock rom also
What 5 widgets? Have you experimented with disabling them? What other apps do you have installed? Some wait in the background and use up memory / CPU. CM is pretty much the fastest ROM, so you need to look at the apps if things are slow.
You can also try the links in my sig for info on using compcache or swap to reduce the delays when you switch back home or in and out of the browser.
Well I have the free weather widget, retro time, retro date, and a battery widget and a few other application shortcuts on the home screen and it still lags when I go to home and its always like this and what does a swaper do?
blackfire1 said:
Well I have the free weather widget, retro time, retro date, and a battery widget and a few other application shortcuts on the home screen and it still lags when I go to home and its always like this and what does a swaper do?
Click to expand...
Click to collapse
I would activate your linux-swap partition or use the compcache userinit.sh. I wouldn't use swapper, its out-dated.
Basically what swapper (and linux-swap) is, is like creating extra memory for your phone to use, but places it on the sdcard. The increased memory allows for you phone to do more at once without having to constantly close programs left and right, speeding it up. But, the constant read/write of the sdcard wears it down quicker (don't worry, you'll still get about 2yrs of life out of that sdcard) and can become slow if it is writing/reading to the memory at the same time is it reading an app or file from the sdcard. Not noticeably slower, but slower nonetheless.
Compcache is a better solution IMO (its the new thing haha). What happens is that whatever RAM stores is compressed instead. Because its compressed, you can store more stuff on it. so like 24MB of RAM would be extended to 72MB of RAM and then you wouldn't have to read/write to the sdcard so often, saving its life and allowing for a small speed boost compared to a swap file.
There are threads on how to do both of these things in the development thread. The compcache is pretty easy, all you have to do is copy userinit.sh to your /system/sd/ and your pretty much done. Linux-swap requires you to create a 3rd partition in addition to the FAT32 and ext2/3. A little extra work, but well worth it. Most ROMs will automatically activate the linux-swap partition if you have it.
Note: Compcache can also use linux-swap as a backup, allowing for an even faster phone. I'm using jacHEROskiv1.4C_a2sd and it works pretty fast IMO. Certainly not as fast as Cyanogen's but fast enough for day-to-day use.
If you really really really really, don't want to mess with any of that, I would just use swapper. Its like linux-swap (follows the same principle), but its not as fast. If you do choose to use this solution, make sure you place the swapfile on /system/sd/ so that when you mount your SD you won't mess up your phone.
Can you please show me a link of how to do the Compcache because ive searched and only found nothing yet.
blackfire1 said:
Can you please show me a link of how to do the Compcache because ive searched and only found nothing yet.
Click to expand...
Click to collapse
Link: http://forum.xda-developers.com/showthread.php?t=537236
Also, the command to include linux-swap as a backup (if you choose to) is on page 14, last post on the page. Good luck
Does having 5 home screens use more memory than the original 3?
slightly, but not enough to make the kind of differences that the OP is describing. I know cyanogen and dude's builds both have 5 home screens, not sure about the rest, but this is the first slowdown complaint I've really heard.
The two questions I would ask to the OP is this: 1. how many applications do you have installed? 2. What size and class SD card are you using?
I get a black screen and have to wait 15-30 seconds for the launcher and icons to show up when exiting an application. This has happened to me with earlier cyanogenmod versions as well. I was thinking maybe I should wipe and reflash the ROM. Does anyone know the cause of this and any fixes?
Thanks.
Wipe is definitely in order but first you should look at your usage:
1. How many widgets do you have on your screens? How many apps do you have on your phone? Do you use "Advanced launcher"? Obviously all of those factors will make a difference.
2. Get an "Advanced Task Manager" from the market and see how many programs do you have running that you don't need. You can set it up so ATM closes unneeded programs once every 30 min thus freeing up your ram memory, make sure to exclude google stuff and programs that need to be running at all times (like weather widgets)
3. Do you use any 3D graphic intensive apps or watch a lot of video? If not, then 10mb hack is in order and is the best thing to happen to a man since the sliced bread.
4. Go into Spare Parts and activate "Keep home app in memory", it makes a world of a difference but may drain your battery faster, although not a big deal for me.
5. Wipe your dalvik-cache from SD. A regular wipe only goes so far so you need to make sure that you wipe Dalvik-cache every now and then.
All in all, let's face it, our G1s are very limited in terms of CPU power and Ram memory so anything we do will have trade-offs. Cyan's roms push it pretty much to the limit so lag is expected, although can be minimized.
Good luck.
nasman1993 said:
I get a black screen and have to wait 15-30 seconds for the launcher and icons to show up when exiting an application. This has happened to me with earlier cyanogenmod versions as well. I was thinking maybe I should wipe and reflash the ROM. Does anyone know the cause of this and any fixes?
Thanks.
Click to expand...
Click to collapse
get rid off linux swap it slows down the phone cuz cy doesnt use swap in his rom b get Set cpu or overclocking widget.
Thanks for the info borodin.
I wiped and reflashed the ROM, as well as flashing the 10 mb RAM hack. I've also done everything else you mentioned.
Is there a way to get rid of the regular launcher after installing advanced launcher?
Reboot into recovery, make a back-up, drop into console and
Code:
mount /system
mount /system
rm /system/app/Launcher.apk
rm -r /system/sd/dalvik-cache
reboot
Same thing with any other system apps you don't like (such as amazon.mp3, or whatever else). Just make sure to make a back up and stay away from google stuff. If you need to see exact names of apps you can use ls command
Hi,
I'm running CyanogenMod-4.2.13. 8 GB Class 6 SD card with Apps2SD formatted with EXT4 and something like a 20mb swap partition. I have around 35 applications on my phone.
My home screen consists of 3 screens - 1 widget (Power Control) and 12 icons.
Here's the issue: When I hit the home button from any application, it takes about 20 seconds to load the home screen. If I hit the phone button from any application, it takes about 20-35 seconds to load the Dialer application. The phone just feels laggy. Task manager apps only show a couple processes running - nothing excessive. Is this normal?
If this is not normal, how do I fix it? I wipe about once a month. I've tried clearing the dalvik cache from terminal with this:
mount system/sd
rm -r system/sd/dalvik-cache
reboot
... with no luck. Any suggestions?
Thanks in advance
Do you have compcache enabled in spare parts?
Do you have 'keep home in memory' checked in spare parts?
No, I didn't. I just checked them and the home seems to load a bit quicker. The phone app still takes awhile. Should I expect it to speed up as it starts caching stuff?
is the phone app taking 10 seconds?
What are you using to setup your swap?
Try changing the swap size to 32 or removing it all together. compcache should be enough for a donut rom.
You can download CacheMate (the one with the icon of a recyle bin/trash can) and try deleting all the cache. That can really speed up a phone.
Or go into the recovery and delete the dalvik-cache or just backup everything and wipe everything on the phone possible and partition your sdcard like this
512 mb ext 3/32 Mb swap (or if you want a swap size that is good for all roms like donut/eclair/hero then make the swamp 96 Mb)/ rest fat32
It looks like it's getting better. I restarted my phone and it's taking less than 5 seconds for the dialer app.
If it starts slowing down again, I'll try messing with the swap.
Good to hear. are you using the default launcher.apk from cyan mod? Because i know it comes with 5 screens, i know you're either using an alternate launcher or just using 3 of the 5 screens.
Hello team:
I have tried several Hero ROMs, and some of them are pretty fast once installed and even when you have installed 30 or 40 apps, but for some strange reasons, after 2 or 3 days of normal use, all of them become too slow...
I have noticed this annoying effect on MLGIN 3.2, Maxisma Sapphire 2.0.1 and MgthyMax 1.9.1
Anyone know the cause of this behaviour? any way to fix this?
I´m currently running MghtyMax with a Swap partition of 192 Mg (Class 2 8GB SD card, 60 Swappiness)
Many thanks
Rgds
iamarock said:
Hello team:
I have tried several Hero ROMs, and some of them are pretty fast once installed and even when you have installed 30 or 40 apps, but for some strange reasons, after 2 or 3 days of normal use, all of them become too slow...
I have noticed this annoying effect on MLGIN 3.2, Maxisma Sapphire 2.0.1 and MgthyMax 1.9.1
Anyone know the cause of this behaviour? any way to fix this?
I´m currently running MghtyMax with a Swap partition of 192 Mg (Class 2 8GB SD card, 60 Swappiness)
Many thanks
Rgds
Click to expand...
Click to collapse
how do you set the swappiness? I have mine 128 swap 512 ext4 and its class 6
Hero Roms are supposed to be used with Class 6 but I've been using Class 2.
I used ext3 (since not all ROMs support ext4 for some reason) - 512 mb, 96 swap, and rest fat32.
This is what I do to keep Hero Roms fast
1) Install the apps that you use a lot or need. You will be surprised at all the apps that you never used. I have about 20-25 apps installed in MLIGN 3.2B
2)Get the app CacheMate (the one with the trashcan icon) and use that to clear cache. This will speed up the phone a lot.
3)Once you boot up your phone go through all the homescreens and let everything load up (like widgets) and then go through and open up the Sense UI apps (stock apps that came with the ROM) and let them load. Go through all the options.
4)If things let you auto rotate, let them auto rotate for a while (like for camera, albums, browser, mail clients, etc) I let them auto rotate after I boot up the Hero Rom and the Rom gets faster.
5)Over clock to 528 min and max when the screen is off and 328 min and max when the screen is off. I use SetCPU and this helps with performance when using the phone and saves battery when the phone is in sleep mode.
6)If things start slowing down, reflash the ROM without wiping (like I flash MLIGN 3.2B and Deport 1.0 if the ROM starts slowing down and it speeds things back up)
AndroidNoobie said:
Hero Roms are supposed to be used with Class 6 but I've been using Class 2.
I used ext3 (since not all ROMs support ext4 for some reason) - 512 mb, 96 swap, and rest fat32.
This is what I do to keep Hero Roms fast
1) Install the apps that you use a lot or need. You will be surprised at all the apps that you never used. I have about 20-25 apps installed in MLIGN 3.2B
2)Get the app CacheMate (the one with the trashcan icon) and use that to clear cache. This will speed up the phone a lot.
3)Once you boot up your phone go through all the homescreens and let everything load up (like widgets) and then go through and open up the Sense UI apps (stock apps that came with the ROM) and let them load. Go through all the options.
4)If things let you auto rotate, let them auto rotate for a while (like for camera, albums, browser, mail clients, etc) I let them auto rotate after I boot up the Hero Rom and the Rom gets faster.
5)Over clock to 528 min and max when the screen is off and 328 min and max when the screen is off. I use SetCPU and this helps with performance when using the phone and saves battery when the phone is in sleep mode.
6)If things start slowing down, reflash the ROM without wiping (like I flash MLIGN 3.2B and Deport 1.0 if the ROM starts slowing down and it speeds things back up)
Click to expand...
Click to collapse
Many thanks for your reply, AndroidNoobie, very helpful
I will follow each one of your steps!!
Rgds
AndroidNoobie said:
Hero Roms are supposed to be used with Class 6 but I've been using Class 2.
I used ext3 (since not all ROMs support ext4 for some reason) - 512 mb, 96 swap, and rest fat32.
This is what I do to keep Hero Roms fast
1) Install the apps that you use a lot or need. You will be surprised at all the apps that you never used. I have about 20-25 apps installed in MLIGN 3.2B
2)Get the app CacheMate (the one with the trashcan icon) and use that to clear cache. This will speed up the phone a lot.
3)Once you boot up your phone go through all the homescreens and let everything load up (like widgets) and then go through and open up the Sense UI apps (stock apps that came with the ROM) and let them load. Go through all the options.
4)If things let you auto rotate, let them auto rotate for a while (like for camera, albums, browser, mail clients, etc) I let them auto rotate after I boot up the Hero Rom and the Rom gets faster.
5)Over clock to 528 min and max when the screen is off and 328 min and max when the screen is off. I use SetCPU and this helps with performance when using the phone and saves battery when the phone is in sleep mode.
6)If things start slowing down, reflash the ROM without wiping (like I flash MLIGN 3.2B and Deport 1.0 if the ROM starts slowing down and it speeds things back up)
Click to expand...
Click to collapse
I'm going to try that out too. What are the default min and max settings? Also, how low can I go when the screen is off?
I have done my NC and a couple of others, here are the steps I am using for IMHO the ultimate NC setup, FYI. This guide is adapted from the guide posted for installing CM7 http://forum.xda-developers.com/showthread.php?t=1030227 with many of my own extra steps. I recommend reading the original guide first.
I get an average of >12 hours battery life with very stable performance with these settings on my NC.
In short, this is how I think the Nook Color should have been done from the beginning. I have attempted to balance some goals that are pretty common to other users. This guide walks you through steps that will accomplish all of these goals, but you may decide to keep some and skip others.
Here is what this will do:
Root your Nook Color and put a variant of CM7 ROM on it. This is an "AOSP", or "generic Android" installation. Nook Color comes standard with Android under the covers of B&N's launcher and suite of apps. Many of the tweaks and advantages in this guide cannot be had without first abandoning B&N's standard OS in favor of CM7.
Enhance performance by overclocking. The Nook Color is 800MHz max clock rate from the factory, and this guide will allow it to run at 1.2GHz (50% faster), along with tweaking the governor settings to ensure you do not sacrifice battery life.
Improve battery life. My goal was to have a device that I can use on flights between Austin, TX and Europe to read books or watch movies without access to a power outlet. I believe I have achieved that goal.
Enhance stability. While many ROMs (such as the new ICS work) may favor bells & whistles and tinkering over stability, I want my device to be rock solid and never, ever crash. The goal here is a device that *just works*, much like Apple devices are known to *just work*.
Smooth and responsive UI. One common complaint of Android devices vs. Apple stuff is on smoothness and responsiveness of the UI, in particular scrolling, screen switching, etc. Glitchy or erratic movements, abrupt or stuttery scrolling, etc. all gives a feeling of poor quality or lack of "polish" IMHO, and I have made an effort to fix this flaw in Android on the NC, mostly because the hacky feel distracts from my enjoyment of the device.
Flexibility and efficient use of storage. My guide will swap the /emmc and /sdcard mountpoints as well as repartition the internal memory of the NC, with the goal of efficiently utilizing the internal storage space, and allowing the SD card to be used in a more portable fashion, not required for operation but interchangeable. Mostly this is because for me, I have a LOT of music and limited space on my 32GB SD card for other media. But on long trips, I may want to bring along movies to watch and they are far more portable when put on tiny microSD cards. So I want to be able to change SD cards and change the media content on my NC, without having to reboot or lose access to some apps.
NOTE
These instructions will root your device and install a variant of CM7 onto your Nook Color in the internal memory, EMMC. This will destroy the original (stock) Operating System and you will lose whatever you had in your Nook Color before the install. It is destructive and likely difficult to reverse. If you have reservations about changing it or wish to change back, don't use these instructions. Try someone else's less-permanent means of doing so. You may screw up a step or I may have missed something, or your NC may not respond like I expect, so if you brick your Nook, then you are on your own. There is no warranty included with these instructions.
These instructions are for those of you who want a smooth, fast and stable NC Android experience, with exceptional battery life as well as efficient usage of internal and external storage. IMHO, this is how they should have done it from the factory. Someone else likely figured out a better way, but this is my way, and it works for me. You do this at your own risk.
This is not for those of you who want the Barnes & Noble experience. And this is certainly not for those of you who are on the fence about whether to re-flash. As far as I know, there is no going back, or if there is, it probably is hard to do. I don't know, because I never considered it.
There. Now you're on your own
Also NOTE
I am not the developer of the ROMs, image files, tools for repartitioning, or any of the other stuff mentioned here. I simply am noting my method for doing the installation and settings. Full credit and thanks are due to all of the original developers of this content.
mr72's setup guide:
Power up your brand new Nook Color and register the device. Note: I have seen a few refurb NCs that needed to be returned... don't skip registering it! Might save you some heartache.
You will need two SD cards: the "boot SD", which will be used to install clockworkmod, the OS, and google apps; a "data SD" which will be used to install the repartitioning scripts and then can be used for data storage. You can use the same SD card for both, but you may want to reformat it after using it to install the OS. IMHO, 1G and 2G microSD cards are cheap and it makes sense to make the "boot SD" on one of these and keep it around for recovery, using a much larger microSD (16GB or 32GB) for data storage later.
Use Win32DiskImager to write the 1gb_clockwork-3.2.0.1-eyeballer.zip image to the boot SD. You must run Win32DiskImager as administrator!
Copy the following files to the "boot SD" which you prepared with Win32DiskImager (Note: do not unzip them.):
A. The CM7.20 Stable ROM
B. gapps-gb-20110828-signed.zip
Copy the following files to the "data SD" card (Note: don't unzip these either.):
reformatData-v1.zip
repartition2GBdata-v1.zip
Power off your Nook. Put the "boot SD" card in (the one with the 1gb_clockwork image), and then power it back on. It should boot into ClockworkMod Recovery ("CWM").
Navigate in CWM using the volume up/down keys to go up and down, N button to accept, power button to go back.
Optional: Now is a good time to back up the factory OS. Use "Backup" from the ClockworkMod menu.
Go back and navigate to "Install .zip from sdcard", then "Choose .zip"
Flash the files in this order:
1. update-cm-7.1.0-encore-signed.zip
2. gapps-gb-20110828-signed.zip
Once you've flashed the files, in the ClockworkMod main menu select "wipe data/factory reset"
Go back to the main menu, remove the "boot SD" card and put in your data SD card. Choose "Reboot system now", which should boot into CyanogenMod (CM7). Note, it requires an SD card to boot at this time.
Once you boot into CM7, you must add your Google account, which will require wifi access. You can set up wifi by using the menu on the status bar. It may be kind of tricky to set up the wifi and get through the wizard. But it will eventually work.
Go to the market and search for "ROM Manager", and install the latest version.
Then just open up Rom Manager from the app drawer and hit "Flash ClockworkMod Recovery" and choose "Nook Color". It's on the list, even though the list may not be in any discernible order.
Optional: While in the market, you probably want "ES File Explorer", makes life easier when trying to navigate files.
Reboot into recovery, and back up the current ROM. Seriously, now make a backup. This is a basic starting point before you add apps and do a lot of tricky stuff, so this is an excellent place to make a backup that may save you later.
Install the reformat/repartition using precise instructions in this thread
Follow the instructions to use custom 1.96GB "/data", 4+GB "/media" partitioning to the precise detail.
This process is destructive and may feel quite risky. I suppose it is! So be careful and don't make a mistake here. It is worth it. By repartitioning you will wind up with 2GB of space for apps (vs. 1GB stock) and the other 4GB is usable as temp storage (like an SD card). This will also allow you to run your Nook Color with no SD card installed, plus hot-swap SD cards with no effect on running apps.
Now, back to Menu -> Settings -> CyanogenMod Settings
Application
- uncheck "Allow application moving"
- Install location: "Internal"
- check "Use internal storage"
- uncheck "Permission management"Note: This will cause the SD card to be mounted at /emmc and the internal 4G partition will be mounted at /sdcard. The result of this is your actual SD card does not have to be installed in order for the NC to work, apps that require /sdcard for storage will use the internal memory. This also means your SD card can be "clean", with only media on it, and interchangeable so you can have more than one SD card with content. The 2GB partition will be used for apps. You will have a hard time running out of application storage space with 2GB.
If you didn't repartition, then you will have 5GB for apps and only 1GB will be used for /sdcard stuff, which IMHO, is too little space for the /sdcard temp/settings storage, and way more than you can ever use for apps (certainly if your apps require sdcard space). So the repartition is IMHO necessary to make the sd/emmc swap feasible.
Install the V6 Supercharger script, update 8. Download it and use ES File Explorer or other tool to move it to the root level of the SD card partition (/mnt/sdcard). You will have to run the script in Terminal Emulator with the following commands:
su
cd /mnt/sdcard
sh V*
0
9
16 Note: this changes the way apps' memory is managed and results in more available memory for the active app more often. This makes things faster. However, you may find that it winds up killing background apps more frequently, so there is a tradeoff. So if you pause your Angry Birds game and go do web surfing for a couple of hours, Angry Birds may have to restart when you return to it rather than staying in memory the whole time. FYI.
Also Note: There are some other tweaks floating around that are said to improve performance; in my observation, they do not really improve it, and they are not necessarily persistent across boots. The V6 Supercharger does the trick, and doesn't require anything else to get the job done, IMHO.
Some performance tweaks, if you want iPad-like scrolling and smoothness and 12+ hours of battery:
Menu -> Settings -> CyanogenMod Settings
Performance (say OK to the "Dragons ahead" warning)
- CPU Settings
- Governor: InteractiveX, min 300, max 1200, set on boot checked. Note: the Conservative governor may result in better battery life, InteractiveX will result in a more responsive device. I switch between the two depending on whether I need long battery life, such as on a long flight where I plan to read or watch movies. - Use JIT - checked
- Enable surface dithering - checked
- Use 16bit transparency - checked
- Allow purging of assets - checked
- Lock home in memory - checked
- Lock messaging app in memory - unchecked (there is no messaging on a NC) You will have to reboot for these to take effect.
Undervolt/Frequency settings (this improves battery):
Run the Nook Tweaks app
CPU Settings
Clock Settings
CPU Stepping 1: 350mhz
CPU Stepping 2: 600mhz
CPU Stepping 3: 800mhz
CPU Stepping 4: 1000mhz
CPU Stepping 5: 1200mhz
Set on boot: Checked Voltage Settings
Stepping 1: 0.925v
Stepping 2: 1.05v
Stepping 3: 1.2v
Stepping 4: 1.275v
Stepping 5: 1.325v
Note: you can set the CPU minimum to 300 MHz to eek out a tiny bit more battery but when I do this, I get occasional SOD that are alleviated completely by using 350 MHz min.
I continue to update this whenever I have something meaningful to report. The truth is that for months now I have just basically been using my Nook Color regularly with no problems whatsoever, so this doesn't really require regular attention. Once ICS is fully-baked, I am sure I will come up with an alternative using ICS. For now, this setup appears to be rocking.
With this setup, with wifi disabled I achieved over 17 hours of battery life while reading ebooks with Moon+ Reader and the screen on (not night mode, this is white background, black text, and brightness about 10%). I also got about 10 hours of battery while watching movies. I think this is pretty great battery performance.
UPDATES CM10!
I have completed my experiments with CM10 and CM10.1 and (drum roll!)... they are not good choices IMHO for NC.
Battery life was about 1/2 on CM10 or CM10.1 what it was with CM7.20 and performance was very sluggish. Web browsing in particular is almost useless. I found I ONLY used my NC for reading books (since Moon+ Reader worked just fine) and I seriously hated having to use it for anything else.
The battery would not last throughout one overseas flight just reading books.
Just not nearly enough battery and performance for me, and while I like some of the UI enhancements (and particularly the ability to use Chrome browser) with CM10/10.1, they were in no way worth the extreme tradeoff in performance.
In the meantime I also dropped my NC and crunched the corner on it, so while it works, it does need to be replaced.
So, back to CM7.20 for me on the NC. I'm actually following my own guide right now to get it rebuilt the way it was. I'll be shopping for a new tablet to get maybe this summer that will run CM10+ with performance like I was getting from my lowly NC. Long live CM7.20 on NC!
Great!
It's very detail but some miss
If you put all 4 .zip files into ONE bootable CwMR uSD, step 9 you remove the uSD, insert the new one in, assuming it is blank then jump to step 14, you wont have the format file if you not re-insert the first usd back.
Also, flashing CwM into eMMC very convenience, yes, but it is a pain if you want to go back to stock ROM. I always preferred boot into CwM R via a bootable uSD card.
Your note in step 15, I personally do not believe it is 100% true. In my case, without an external uSD card plugged in, Aldiko Reader won't work. And yes, my system set up is like what you said.
votinh said:
Great!
It's very detail but some miss
Click to expand...
Click to collapse
Thanks, I updated it. Maybe didn't catch everything.
Also, flashing CwM into eMMC very convenience, yes, but it is a pain if you want to go back to stock ROM.
Click to expand...
Click to collapse
IMHO, if you have reservations and think you might want to go back to the stock ROM, then my instructions above are not for you.
Your note in step 15, I personally do not believe it is 100% true. In my case, without an external uSD card plugged in, Aldiko Reader won't work. And yes, my system set up is like what you said.
Click to expand...
Click to collapse
I have not tried Aldiko but I have probably 100 other apps and none of them require the SD to be installed. IIRC Aldiko does require you to tell it where the library is located; maybe this is the problem? I don't remember.
I switched to Moon+ Reader for my books, which I wholeheartedly recommend over Aldiko. I found Aldiko was crashing and causing my whole NC to crash/spontaneously reboot, etc., when you leave it running in the background for a long time. I think Aldiko likely has a memory leak.
While I am talking about app recommendations, I also suggested Go Launcher EX, which I really like. It feels faster and is more configurable in ways that improve responsiveness for my tastes compared to ADW. I have some theme preferences that I could share, which I think are optimal for the NC given the screen size, but I have found that most other people I know who are over 30 tend to think my settings for screen sizes of icons and controls are too small, so I didn't bother. Normal Tablet Tweaks and the default CM7 setup may be ok for you. I do prefer Dolphin HD browser over the stock browser, and I also tried Maxthon, Firefox Mobile, and Opera Mobile as well as Opera Mini. I like features of all of them, but on balance Dolphin HD is the winner.
votinh said:
Also, flashing CwM into eMMC very convenience, yes, but it is a pain if you want to go back to stock ROM. I always preferred boot into CwM R via a bootable uSD card.
Click to expand...
Click to collapse
I've tried a few of the new posts about returning to stock ROM and found it was really easy myself. YMMV
Thanks for the guide mr72.
The one thing I'd recommend to people who haven't done the cpu frequency / voltage tweaks before is to set it and test it out for a while without making it set on boot. The frequency settings are quite safe / standard, but the voltage settings vary a little more from person to person. If you've used it that way for a few hours without issue, then make it set on reboot.
insz said:
Thanks for the guide mr72.
The one thing I'd recommend to people who haven't done the cpu frequency / voltage tweaks before is to set it and test it out for a while without making it set on boot. The frequency settings are quite safe / standard, but the voltage settings vary a little more from person to person. If you've used it that way for a few hours without issue, then make it set on reboot.
Click to expand...
Click to collapse
Good point.
Also note, my settings are quite conservative. I have run them much lower and the NC was still stable, for at least a few hours. However, I figured I'd err on the side of stability.
Also note the impact screen brightness will have on battery life. While it may be second nature for some of us to turn down the brightness we might want to point out that it is the single biggest drain on the battery,
--------------------------------
Sent from the Center of my Mind
Nice work! I just updated Nook Tweaks with those settings. I updated to the SKANG RC-2 Mirage and so far the Nook is much speedier than stock CM7 RC1.
Will post back after I test these settings a bit.
MISRy said:
Also note the impact screen brightness will have on battery life.
Click to expand...
Click to collapse
That's true. Mine is normally about 40%. However, in my e-reader app (Moon+) I tend to adjust it to about 15-20% when reading with the lights on, and about 6% when reading in the dark. But the whole screen is mostly white so this is really a worst-case battery drain app for screen usage.
I managed to watch HD movies with wifi enabled but not streaming for 7 hours and the battery was maybe 30% afterward. So I think it has 10 hours of movies in it. With wifi disabled, it is better.
mr72 said:
I have not tried Aldiko but I have probably 100 other apps and none of them require the SD to be installed. IIRC Aldiko does require you to tell it where the library is located; maybe this is the problem? I don't remember.
Click to expand...
Click to collapse
Back to your "previously step 15", which probably a step 17 now, external uSD related. I just glanced through one of my previous post that talking about the requirement of an external uSD.
Can you do a quick test? Remove uSD off your NC, then capture the screenshot using the built-in feature (press and hold power button to bring up the menu).
See if it let you save the image or not.
votinh said:
Back to your "previously step 15", which probably a step 17 now, external uSD related. I just glanced through one of my previous post that talking about the requirement of an external uSD.
Can you do a quick test? Remove uSD off your NC, then capture the screenshot using the built-in feature (press and hold power button to bring up the menu).
See if it let you save the image or not.
Click to expand...
Click to collapse
Next time I have my SD card removed, I can try that. I'm not going to do it today. But trust me, it works just fine. The Android OS doesn't know there is no physical SD. You just have to make sure the internal partition is mounted at /sdcard. No part of Android OS can write to the partition without going through that mountpoint.
http://forum.xda-developers.com/showthread.php?t=1030227
Nice re-iteration of eyeballers thread..
Although I didn't use this post to setup my nook. It confirms some things. Also it said in the op and even links to eyeballers thread that this is how mr72's setup went and how he used settings to optimize his nook. I kinda like having the changes in one place.
khaytsus said:
http://forum.xda-developers.com/showthread.php?t=1030227
Nice re-iteration of eyeballers thread..
Click to expand...
Click to collapse
Sent from my NookColor
I've seen votinh talk about not wanting to install CWR to emmc, and have wondered why. I kinda just assumed it was some ethical dilemma concerning the warranty. It is pretty easy to wipe, in my experience at least.
One note to mr72. The V6 supercharger script is used to change the minfree values, and locking home in memory can conflict with its operation and cause lag. If you run the script in a terminal you can see it explained right beneath the script’s 17 option menu.
Just a note.
mateorod said:
I've seen votinh talk about not wanting to install CWR to emmc, and have wondered why. I kinda just assumed it was some ethical dilemma concerning the warranty. It is pretty easy to wipe, in my experience at least.
Click to expand...
Click to collapse
Maybe because I'm a bit of paranoid but since joining the forum and helping others, the most itchy issue that I've seen so far is restoring back to stock and a lot of people suffering the hiccup due to CwMR flashed into eMMC using ROM Manager.
In order to get out of it, they have to perform 8-boot ??? or whatever it is.
While w/o CwMR installed in eMMC, restore back to stock is just simply as re-flash a ROM.
Again, NOT ALL people hit the head-scratching issue but some did.
hhmm ... I wonder how this setup would work on ICS?
Once we get fully-functional, stable builds of ICS then I am sure I will do the same kinds of experiments as I have with CM7+ and wind up with a similar set of recommended tweaks and settings, if I have success running ICS and don't go back.
FYI, regarding battery life:
I got a PM asking for a little more detail. I am getting >12 hours of battery with the screen on while reading ebooks. This was on a series of flights overseas wherein I used the NC with Moon+ Reader, and wifi disabled.
I just got finished watching a movie for pretty much right at an hour, with wifi enabled, here at my house. MX Video Player, a DVD-rip of a movie, with the brightness on about "3" (set on MX Player). Battery went from 91% when I started to 80%. If it is linear, that's 9 hours of battery watching movies.
IMHO, this is pretty great. And it matches my rough experience from the previous experience watching movies.
Of note:
in MX Player, XviD movies play far better and consume less battery than x264. I got more like 15% per hour with x264 (BRrip, 720p) and frequently had to resync the audio and video. And also I have switched to the InteractiveX frequency scheduling, using the "SW Fast" decoder for MX Video Player, as an experiment to see if it improves video playback (it doesn't). But it doesn't seem to adversely affect battery life.
@mr72
I've been using Go Lancher EX on my CM7.2 NC (and Galaxy S2) and prefer it to AWD EX's features and performance. You mentioned earlier that you had some GO-specific tweaks that you'd be willing to share. I'd love to see how they compare with mine if you're still willing.
Thanks!
I just installed to and am running CM 7.2 from an SD card. Last night I full charged and today I noticed that my battery says that its at 15%, but the voltage is at 3693 mV. I know the max charge is around ~4200 mV, so the percentage seems very low considering the voltage value. Anyone help?