Related
i checked internal nand speed with j Bench Mark and the result is a 0.09 MB/s in write and 3.51 in read. (/sdcard mount point vfat)
My cheap and old micro sd (sdcard/sd) in write go up 2.00 MB/s.
Now i understand why we need mimocan hack to speed up the phone.
Other mount point (system dbdata ecc) rfs type are also so slowly?
You're unlucky with write, here 1.85MB/s
but you're luckier with read, here 2.75MB/s
Same phone, same bench.
Data size 10MB
Buffer size 2KB.
Slow, indeed.
AFAIK, for reasons unknown to me, the physical media where /sdcard resides is the slowest in our phone. That's why we're taking /data/data away from it (no matter how). The smaller internal NAND, which should be the one hosting /dbdata and /system, is much faster. Or maybe I got it all wrong...
If that's the case, anyone who knows better, please correct me...
Rizlo said:
AFAIK, for reasons unknown to me, the physical media where /sdcard resides is the slowest in our phone. That's why we're taking /data/data away from it (no matter how). The smaller internal NAND, which should be the one hosting /dbdata and /system, is much faster. Or maybe I got it all wrong...
If that's the case, anyone who knows better, please correct me...
Click to expand...
Click to collapse
I believe you have it reversed. The internal SD card is faster than the internal NAND.
dalingrin said:
I believe you have it reversed. The internal SD card is faster than the internal NAND.
Click to expand...
Click to collapse
don't think so, if that really was the case then how do you explain the fact that the mcr lagfix speeds the phone up? all the mcr lagfix does is move the app data from the internal sd to the nand. the reason we have the lag problem in the first place is because the internal sd card is way to slow, both the nand memory and the external sd card has much faster read speeds than the internal sd.
dalingrin said:
I believe you have it reversed. The internal SD card is faster than the internal NAND.
Click to expand...
Click to collapse
wrong! the boot process would be quite slow if this would be the case...
try hdparm -t on both if you don't beliefe us. i get read speeds of 50Mb/s on the nand and 10Mb/s on the internal sd with it.
I don't think either of these are the real cause of the problem. Why? because with JM2 only, i can without a doubt say my phone is just as fast as with mimocan lag fix (judging from videos). Yes i know that the quadrant score improves etc. but that to my knoweledge is not exactly relevant to opening and closing programs and the lag in between.
IMO opening and closing an android app to ram is not exactly that big of deal, that reading/writing speed differences of this amount would really show.
I think the problem is more related to memory management. Perhaps im totally wrong here?
Just did this test and this is the resultfrom the /sdcard part:
Write Performance: 3.1(MB/s)
Read Performance: 5.46(MB/s)
Test of the Internal NAND:
Write Performance: 1.65(MB/s)
Read Performance: 2.59(MB/s)
Running Firmware JG3 with Paul's MCR r2 and mimocan's fix
What software did you use for testing?
jodue said:
wrong! the boot process would be quite slow if this would be the case...
try hdparm -t on both if you don't beliefe us. i get read speeds of 50Mb/s on the nand and 10Mb/s on the internal sd with it.
Click to expand...
Click to collapse
Hi, sorry for the noob question, but can you please explain how I can choose the device to test (sdcard or NAND) with the hdparm command?
Moved to General forum. The development forum is only for development threads. (Threads with actual development happening.)
Questions should always be in the General forums (or Q&A if your device has a Q&A forum.)
Is a 16g card to big for the nook? On most dl's I see 2g, 4g, 8g, etc but no 16g.
No. 16GB is not too big.
The NC maxxes out at 32GB.
http://www.barnesandnoble.com/nookcolor/features/techspecs/index.asp
cool thanks
I'm using a SanDisk 32g Class 4 for mp4 movies (CM7 1.1 OC) and works fine.
Question on sd card
skeeterpro said:
I'm using a SanDisk 32g Class 4 for mp4 movies (CM7 1.1 OC) and works fine.
Click to expand...
Click to collapse
Is our CM7 also running off the card? (noobie question). I recently placed the CM7 on a Sandisk card, 16m, Class2 and all my MP4 videos are choppy or out of sync. I've tried several video players.
A related question: Is the SD image of CM7 the same as the stable version of the EMMC version since the video is reported to be working great in that version.
polarborn said:
Is our CM7 also running off the card? (noobie question). I recently placed the CM7 on a Sandisk card, 16m, Class2 and all my MP4 videos are choppy or out of sync. I've tried several video players.
A related question: Is the SD image of CM7 the same as the stable version of the EMMC version since the video is reported to be working great in that version.
Click to expand...
Click to collapse
I' only loading movie files from the 32G uSD. Running CM7 from eMMC. I did run CM7 from a uSD a while ago on a Transend 8G Class 6 which the consensus seems to be the card to use. Class 6 seems to be the "sweet spot". Others have run Class 10s with very mixed results. Lower class ditto.
As far as the version of CM....I don't believe so. The stable signed is 7.0 (7.02) and have not personally seen a uSD version but I could be wrong.
(Edit): Try using VitalPlayer. My sotware of choice.
skeeterpro said:
I' only loading movie files from the 32G uSD. Running CM7 from eMMC. I did run CM7 from a uSD a while ago on a Transend 8G Class 6 which the consensus seems to be the card to use. Class 6 seems to be the "sweet spot". Others have run Class 10s with very mixed results. Lower class ditto.
Click to expand...
Click to collapse
The "class" of an sdcard measures the sequential read/write speed. The deciding factor for how well an sdcard would run a rom seems to be something else: the small block random read/write speed (which does not seem to be listed on the package); see
http://forum.xda-developers.com/showthread.php?t=1005633&page=2
for an interesting discussion & data (esp OP and post #19). Speaking for myself, I had a great deal of troubles running nookie froyo on two class 6 cards, but I had no problem using a cheap class 2 sandisk. You guess it: the sandisk's small block r/w speeds is almost 10 ten that of the two class 6. Right now I'm running CM7.02 on a class 4 sandisk and it's running great.
YMMV.
Updating the SD Card
I had used the image from Verygreen's link which is 7.0.0-RC2 but re-reading his original post it appears I can just copy the latest build from
"mirror.teamdouche.net/?device=encore"
and copy into the first partition then reboot in recovery.
Can someone comfirm this will still work? I'm having issues with choppy video and terrible battery life - though I realize the battery life is much less than stock. The stable version, 7.0.2 was suppose to address many issues and from reports is running great.
Thanks!
polarborn said:
I had used the image from Verygreen's link which is 7.0.0-RC2 but re-reading his original post it appears I can just copy the latest build from
"mirror.teamdouche.net/?device=encore"
and copy into the first partition then reboot in recovery.
Can someone comfirm this will still work? I'm having issues with choppy video and terrible battery life - though I realize the battery life is much less than stock. The stable version, 7.0.2 was suppose to address many issues and from reports is running great.
Thanks!
Click to expand...
Click to collapse
This will work.
I have a 16 GB card and I'm glad to hear it will work. However, which image should I use? Why isn't there a dedicated image for the 16 GB size? Will I only be able to use half my card?
Kernels
ylixir said:
This will work.
Click to expand...
Click to collapse
Sounds great - Thanks. I realized that I could just make my own image using Winimage of my current working CM7 SD install and use it to re-flash if things messup. ( slaps head, duh). I am confused about this from Verygreen's post:
OC Kernel installation instructions:
After you have a running CM7 by doing the steps above.
Get CM7 OC kernel from Dalingrin's thread. Unpack the zip file, the result should be a file with the name "kernel" and some other stuff. Rename the kernel file to uImage.
Shutdown your nook and take the uSD card out (make sure the nook is not plugged into USB bus or it'll boot into eMMC then).
Plug the SD Card into the computer, copy uImage file you just created to the first partition (the partition name would be "boot") instead of the existing file with this name (might want to save the original file just in case).
Now you are ready to go again.
You'll need to repeat these steps every time you upgrade to a new nightly build, because they carry their own kernels with them.
Is this still necesssary? The first section instructs to place the newest build .zip image on the 1st partition and recovery boot - the install works like the original install. Also do I need to also re-install Gaaps?
Thanks - I searched Verygreen's long thread but could not find the answer or a link to Dalingrin's thread.
EDIT: Nevermind - I'm learning... so the Kernel is the basic element that is found in the image file. Different beast than placing the .zip image on the sdcard.
10 char doublepost
I am not sure about the size of the card, but what matters more IMHO are the real-world sequential read and write speeds. I purchased a 4GB Class 10 Patriot uSD card and loaded CM7 per Evergreen's instructions. The performance is TERRIBLE, slow and market d/l is extremely slow as well. I attribute this to Patriot misrepresenting the sequential write speeds of the card. I would go with Sandisk Class 4 uSD or Transcend Class 6 uSD (on order) as well as other Brand uSD cards reported by XDA users to run CM7 well on NC.
It works great
Flashed the latest CM7 7.0.2 to my Sandisk 16g, Class 2. Movies play great with several different players. Still want a better class sd card and will use suggestions found in this forum. I swear, is it more fun to see movies play great on my nook or just trying different "hacks". Love this forum.
Thanks to all those who help us newbies.
I bought a 16GB Sandisk (class 4) card today to replace a Transcend 8GB class 6 -- unlike the Transcend, which I had *maybe* 1-2 Fcs total in the 3 days I've had it running, I've been getting errors and FCs not infrequently with the new card
I even tried wiping it and installing fresh downloads of CM7 and gapps to see if that was the problem.
Could it be I just had the bad luck to get a not-so-good Sandisk card?
I'm running the CM7 (stable) install w/ multi-boot menu, only OC'ing to 925mhz via Cyanogenmod settings for both cards. No launcher mod, just a bunch of game apps, moboplayer, quickpic (same set of apps on both cards). Can't figure out why I'm getting random FCs otherwise in the Sandisk card...any ideas?
------ updated : -------
Ran diagnostics on card, everything (including physical surface check) came back clear. r/w scores were OK (a bit low on the r/w 4ks) but nothing terrible.
When I used a different installer all my FC issues dissapeared. The one I had been using (and still have on my Transcend 8GB card) is the 2GB (extendable 4th partition) + multiboot install. It runs flawlessly on the 8GB card but for some reason caused my 16GB install to crash a lot (FCs and error messages).
When I installed verygreen's agnostic SD card version, the issues I was having on 16GB disappeared. Running very smoothly @ 925Mhz CM7 OC. I've thrown a bunch of movies at it and it looks great, no chop. So YMMV.
SkittlesAreYum said:
I have a 16 GB card and I'm glad to hear it will work. However, which image should I use? Why isn't there a dedicated image for the 16 GB size? Will I only be able to use half my card?
Click to expand...
Click to collapse
There is... I put this together and uploaded when there were so many issues with 16GB cards not being formatted.....
Get 16 GB VeryGreen's generic card (preformatted) here
Isn't the point of verygreen's size-agnostic image that you can install it on any size card? I used it on a Sandisk unclassed (so, 2) 16GB from Radioshack, and CM7.0.2 is running great--much smoother than stock 1.2 on the eMMC.
dohturdima said:
I am not sure about the size of the card, but what matters more IMHO are the real-world sequential read and write speeds. I purchased a 4GB Class 10 Patriot uSD card and loaded CM7 per Evergreen's instructions. The performance is TERRIBLE, slow and market d/l is extremely slow as well. I attribute this to Patriot misrepresenting the sequential write speeds of the card. I would go with Sandisk Class 4 uSD or Transcend Class 6 uSD (on order) as well as other Brand uSD cards reported by XDA users to run CM7 well on NC.
Click to expand...
Click to collapse
As others have said, it's not the sequential r/w but the small-block, random r/w that counts for running an OS, and class ignores this benchmark entirely. Your Patriot was very likely performing exactly as advertised, but what it's advertising is how well it will perform in a 10+megapixel DSLR camera taking rapid-fire photos or a half-hour video. It gains that performance at the expense of small-block r/w, sometimes gaining 5-10x the sequential r/w by sacrificing 100x or greater the small-block speed.
Taosaur said:
Isn't the point of verygreen's size-agnostic image that you can install it on any size card?......
Click to expand...
Click to collapse
Yes, but there are several posts regarding issues with the mke2fs failing on 16GB cards.... that is why I made the 16 GB version available....
I tried with 3 different 16 GB cards that would fail... so I presented my solution for 16 GB cards.
I was having problems with the 2GB expandable install on my 16GB card (ok on my 8GB). Just wiped and installed verygreen's agnostic and so far no FCs or oddities that I've noticed; if I start having issues I'll try yours thanks for posting it!
CM7 on 16 GB Kingston...slow as molasses!
I finally got everything copied, imaged, written, etc. It's working...except being able to access the SD card to move all my stuff onto it...but SLOW!
Should I just chalk it up to the card or are there other settings or things to check? I was a bit overwhelmed by the CM7 settings/options...lot of things there...
Thanks
Alright, so after doing my research, I bought an SD card today (SanDisk 8GB, not sure of the class but it worked) and I am now running CM7 (the stable version) on my Nook Color. I had a few questions that I was hoping people could help me out on:
1. I noticed that people were commenting on the move of the notification bar to the top of the screen and its convenience. Mine is at the bottom--is there any way to change that?
2. I was watching a video on how to run Netflix on my NC, and I needed to use ES File Explorer. When I attempt to run Root Explorer in settings, it says test failed, and I don't know why.
3. Now that I have CM7 running on my NC without my SD card in, can I wipe all of that info from my SD card and have it work as a normal SD card (kind of how I use my SD card on my stock Droid 2 to save pictures, video, etc.)? If so, how can I do that?
4. The video I used never said anything about overclocking or kernels or any of that stuff, but I understand that it makes my Nook run faster--that would help, seeing as it has been a tiny bit laggy. Is there any way for me to install a kernel without reinstalling CM7, and if so, how?
Thanks in advance for all of your help!
NYwRiter94 said:
1. I noticed that people were commenting on the move of the notification bar to the top of the screen and its convenience. Mine is at the bottom--is there any way to change that?
Click to expand...
Click to collapse
Go into Settings/Cyanogen Settings, look for tablet tweaks. There should be a check box for bottom status bar.
NYwRiter94 said:
3. Now that I have CM7 running on my NC without my SD card in, can I wipe all of that info from my SD card and have it work as a normal SD card (kind of how I use my SD card on my stock Droid 2 to save pictures, video, etc.)? If so, how can I do that?
Click to expand...
Click to collapse
Do you mean that you flashed the internal memory (eMMC) with CM7 now? Or that you have booted up CM7 off the SD card and want to use it as a normal SD card now? If you have moved to eMMC CM7, then yes you can format it and use as normal. If not on eMMC, then don't take it out, you will still have some space on the SD card to utilize (I believe, I have only run eMMC versions)
NYwRiter94 said:
4. The video I used never said anything about overclocking or kernels or any of that stuff, but I understand that it makes my Nook run faster--that would help, seeing as it has been a tiny bit laggy. Is there any way for me to install a kernel without reinstalling CM7, and if so, how?
Click to expand...
Click to collapse
Here is the latest OC kernel for 7.0.3 (modified for ext4 so it works)
For SD : http://db.tt/3CnQxjo
For eMMC : http://db.tt/sMdWUs1
If you are still on SD version, goto the Development Section and search for answers on how to install OC kernel there, or maybe someone can help you with answers here, like I said, I haven't run a SD version yet.
Hope this helps,
Ronin
Thanks for the quick response. I managed to move my notification bar to the top, and that's a big help.
I did in fact save the mod to my internal memory, and my SD card is not in my NC anymore. How do I reformat it so that I can put it back into my NC?
And lastly, you provided me with a link to a kernel, but I am still not sure how to get it onto my NC without redoing the whole thing. Any easy to follow, step by step instructions?
And then, of course, if anyone else could help out with the Netflix/ES File Explorer, that would be great.
NYwRiter94 said:
I did in fact save the mod to my internal memory, and my SD card is not in my NC anymore. How do I reformat it so that I can put it back into my NC?
Click to expand...
Click to collapse
Do NOT use the format option inside CM7, it is a known issue that will F up your Nook and make getting things back up and running a huge pain in the a$$. Format it thru a card reader on your PC/laptop. Reboot with SD card installed in Nook, good to go.
NYwRiter94 said:
And lastly, you provided me with a link to a kernel, but I am still not sure how to get it onto my NC without redoing the whole thing. Any easy to follow, step by step instructions?
Click to expand...
Click to collapse
Boot into recovery, choose install zip from SD, choose zip from SD, flash OC kernel.
NYwRiter94 said:
And then, of course, if anyone else could help out with the Netflix/ES File Explorer, that would be great.
Click to expand...
Click to collapse
Another option is to explore the zip for CM7, find the build.prop file in the zip, open and edit to whatever you need to. Reflash from CWR (recovery), then flash OC kernel afterwards
If thats too complicated, check this thread
http://forum.xda-developers.com/showthread.php?t=1076145
Alright, so after screwing up attempting to get the kernel in, I rebooted to stock NC software and then again to CM7. Now I need to know how to get the free version of SetCPU onto my NC, or another free program that works just as well.
NYwRiter94 said:
Alright, so after screwing up attempting to get the kernel in, I rebooted to stock NC software and then again to CM7. Now I need to know how to get the free version of SetCPU onto my NC, or another free program that works just as well.
Click to expand...
Click to collapse
CM7 has a built in governor under Cyanogen Settings->Performance->CPU
SetCpu doesnt play well with CM7, it eats battery.
Alright, well I found it and it gives me 300, 600, 800, 1200 or 1300 MHz increments to use, but I thought that the highest that anyone uses was 1100. Does that mean I can't overclock mine?
NYwRiter94 said:
Alright, well I found it and it gives me 300, 600, 800, 1200 or 1300 MHz increments to use, but I thought that the highest that anyone uses was 1100. Does that mean I can't overclock mine?
Click to expand...
Click to collapse
Nope, the newer OC kernels have different speeds, the older one's limit was 1.1
set it 300 low, 12 or 13 high, and use ondemand as a gov or if it's in the build smartass. Download quadrant standard the market, try running the benchmark with different settings.
Alright, well I got a score of 2293 with max 1200 and 2674 with max 1300, so I guess I'll leave it at 1300.
Ronin, thanks a ton as you've been the only responder and you've helped tremendously.
Lastly, if anyone has a response for the question about Netflix/ES File Explorer, that would be great. It's telling me that the test failed and that my 'phone' can't run it.
Check this thread about getting the Netflix running. There is modified app out that doesn't require editing your build.prop
http://forum.xda-developers.com/showthread.php?t=1076150
Thread title pretty much says it all. I'm trying to install CM7 to boot from SDcard, following verygreen's instructions here using a Class 4 4gig Sandisk uSD. The Nook Color is running 1.3 Stock, has not been rooted.
No matter what I did, I ended up with similar results: after putting the card in the NC it would start the CM7 set-up routine, but would eventually start kicking back dozens of lines of "end_request: i/o error, dev ###" (bunches of numbers and etc). The install would finish despite these, but on trying to boot the NC using the card, it would either end up in a bootloop on the CM7 logo (the circle just going around and around endlessly) or lock up right at the green cyanogenmod logo.
Did a whole lot of reading on the forums, and testing:
I used both WinImage and Win32diskimager to write the image to the card.
I tried a different cardreader than the one I was first using.
I tried a wholly different 4G class 4 Sandisk uSD.
I tried different CM7 ROM releases (stables and nightlies).
I ran chkdsk and h2testw on the cards to verify they were good (they were; no read/write errors).
(Note: using Easeus PM, I wiped the cards and recombined the partitions after each failed attempt.)
I couldn't find anything else about this type of error, except something on it being an error caused by specific Linux kernels or OMAP or something in respect to SD cards. (Not a Linux guy, so it was all a bit greek.)
Afterwards, I went out and bought a Class 4 8gig Sandisk uSD, installed and booted without a hitch on the first try.
From all this I can assume: it's not the card reader, the cards aren't bad, it's not the image or the ROM choice, it's not the imaging program I'm using, the NC and the NC's slot are fine.
So, anyone have any ideas why the 4gig cards won't work? What is causing that error? And how or if it is possible to correct that error? (I have another NC I'd like to use one of the cards with.)
I know "just be happy with the 8G card and forget about it"...I could. But I'm more curious to find out why the 4G's aren't working and see if it is possible to get them to work.
Did you FORMAT the SD cards FAT32?
I did not see that in your posting above.
rampart51 said:
Did you FORMAT the SD cards FAT32?
Click to expand...
Click to collapse
Sorry. Yes, all the cards were formatted to FAT32.
Some more info:
The problem appears to occur when the card is partitioning itself. Immediately after this line: "writing superblocks and filesystem accounting information", with the errors happening on "mmcblk1".
I've also tried creating the cards with this method and a couple of different images. The image appears to write fine, but either the install hangs while the ROM's files are being inflated (I get no I/O errors), or the install completes, but the NC will not boot.
So I want to simply suspect the cards are bad, but none of the programs I've run on them can find any bad sectors or kick back any read/write errors??
Hello,
I'm wondering if others have the same issue.
Issue: Whenever I unlock the phone (via fingerprint or PIN), I notice the response time is 2-3 seconds slower after mounting my microSD Card (Samsung 256GB EVO+ microSDXC). The SD Card is filled with 199GB of files. My little workaround for now is to unmount the microSD card when I'm not using it. Anyone have a similar issue? I am running on the latest stock ROM (rooted) for H918.
- Will
I'm on the same phone, same SD card. Deff different kernel. My finger unlock is actually TOO fast (phone turns back on if I turn off using my print finger). So look for optimizations elsewhere is my advice.
533y4 said:
I'm on the same phone, same SD card. Deff different kernel. My finger unlock is actually TOO fast (phone turns back on if I turn off using my print finger). So look for optimizations elsewhere is my advice.
Click to expand...
Click to collapse
May I ask what ROM + Kernel you are using. I may look into it. Thanks.
aznxwill said:
Hello,
I'm wondering if others have the same issue.
Issue: Whenever I unlock the phone (via fingerprint or PIN), I notice the response time is 2-3 seconds slower after mounting my microSD Card (Samsung 256GB EVO+ microSDXC). The SD Card is filled with 199GB of files. My little workaround for now is to unmount the microSD card when I'm not using it. Anyone have a similar issue? I am running on the latest stock ROM (rooted) for H918.
- Will
Click to expand...
Click to collapse
aznxwill said:
May I ask what ROM + Kernel you are using. I may look into it. Thanks.
Click to expand...
Click to collapse
NATF with NotSoStock 6.5 kernel. I also flashed the FluenceUHD optimization patch. Big difference with the FluenceUHD patch in general. Better battery and less lag overall. I do get the occasional stutter when typing but that has more to do with my governors and such than the optimizations. Also, I am using T-UI as a launcher, dunno if that plays into it at all. I know that launcher is godly for battery. :highfive:
I came to a similar conclusion a few weeks ago. Removing the SDCard speeds up unlocking, and also seems to clean up some of the settings not saving.
Depends on what you have the sdcard FS as. if its fat32 it will probably be slower
me2151 said:
Depends on what you have the sdcard FS as. if its fat32 it will probably be slower
Click to expand...
Click to collapse
According to DiskInfo, the sdcard FS is texfat (which I assume is exFAT) while the system is ext4. It makes me wonder if it's better to format the sdcard as ext4 since that FS is native to linux.
For those who have fast unlock responses for your sdcard filesystem?
Thanks.
TexFAT is NOT exFAT. TexFAT is actually one of the slowest filesystems you can use. Even slower than Fat32 by almost 2-4 times. That right there is your issue. your computer will possibly have issues if you format to ext4 though so i recommend just formatting to exFAT using twrp.