I'm testing SD card speeds/rates on Note 10+ (512GB, Exynos) with Androbench. The same way as I did for my Note 9. The results go into the same google sheet as the old ones. As of this moment, it is mostly Work in Progress... and it should get some LG results, too, some day Soon(tm). I'll hopefully get most of the Note 10+ stuff done tomorrow.
Sheet here: https://docs.google.com/spreadsheets/d/1rs8S2yreJYYms6ik8NgoGagZ_6OKrU5bu1FotHJVz6g/edit?usp=sharing
Preliminary results with only 3 cards tested: seems my Note 10+ is getting even slightly slower results than Note 9.
Lucky me, it seems I won't be using an SD card on this phone; I got the 512GB model so there is plenty of internal storage, and I might end up using the slot for second SIM. (And the Note 9 will remain in use for video recording, due to needing 3.5mm mic input, which seems to be a no-go with the Note 10+ for the time being... So I won't be even needing much of that big internal space on the N10+ anyway.)
Feel free to add your own results in this thread, like done in the old thread for Note 9, I'll copy them to the sheet. Please remember to specify the particular Note 10+ model (i.e. which SoC), its state (which firmware and version, rooting/scheduler tweaks/etc.) and which card (preferably with specific product code / SKU, as namings are often ambiguous (due to manufacturers reusing the same name for different card tech/generation/whatnot, see how I record them on the 'extras' sheet).
Here is the Note 9 thread for reference: https://forum.xda-developers.com/galaxy-note-9/help/note-9-sd-card-slot-speed-rating-t3833981
EDIT: All the significant tests are done (need to clean up the sheet, still). Most cards behave relatively the same way as on Note 9, i.e. slower card is still lower, with roughly the same proportions. But there are couple notable differences. Especially Lexar 633x 128GB managed to squeeze a higher random write rate (yet is otherwise slower just like other cards). The UHS-II 3 card is still utter crap (with decent sequentials, which are comparable to good UHS-I cards) - i.e. even this flagship phone still doesn't work with that better interface, but only with UHS-I.
And indeed almost all results are slightly down compared to Note 9 results. Since there was a random good peak sequential result among everything, it makes me think the system could do better, if the firmware was working better for this use case. Perhaps, e.g., the scheduler/CPU state management and Androbench combination somehow has timings which end up mostly keeping the work on a slower core and/or in a slower state, and the result is unnecessary delays or such. And the random high score could be explained then by a random higher-demand process keeping the CPU at better state for a moment, Androbench benefiting from it as a side-effect. All that is just speculation, of course. And it does not affect the end result: most users may see less than flagship level card performance.
This is mine also using a samsung 64gb orange and white 512gb note 10+ 5g xenos version
liggerz87 said:
This is mine also using a samsung 64gb orange and white 512gb note 10+ 5g xenos version
Click to expand...
Click to collapse
Judging from those numbers, I think you forgot to switch the test target to the card in the settings; it measured the speed of the internal storage, which is indeed reeeaally fast.
Oops feel a tit now haha just added it again
Here is mine. Samsung 512GB EVO Select (U3) 100MB/s
Galaxy Note 10 Plus 5G Verizon
My Note 4 pretty much gives the same results. 82MB/s seq R, 54 MB/s seq W, 9.9 MB/s random R, 2.8 MB/s random W.
This is with SanDisk extreme UHS-I A2 256GB. I wish they made the card interface faster as everything else gets faster!!!
Hi guys, just found this topic and tested my card in Note 10+
It's weird, I have high read speeds but very slow write speed. Have Samsung EVO Plus 128GB.
OP, I think you may be missing the whole point of using a data drive, its primary purpose is to retain critical data. It read speed is somewhat critical in that you need to be able to play music and vids from it with no glitches. The 10+ with a V30 rated card is well capable of that.
Data drives should never used for running apks.
Internal memory should never be used for critical data storage; only the OS, loaded apks, temporary folders and the DCIM folder (for temporary holding until transferred to data drive).
Temporary folders/vetting data before it goes onto the data drive is important, use the download folder for this. Open any downloaded images in the download folder before transferring to the data drive. A malware jpeg will do far less damage here than if it gets on the data drive! I've had a malware jpeg that effected the Android OS, they are real. Generally their rein of terror is confined to the folder they're in, but not always especially if you unwittingly move it!
Scan anything questionable (especially apk downloads)with online Virustotal.
Any downloads not recognized, delete without opening! Trojan preloaders will sometimes get by the browser and autodownload in spite of settings. Look at the download folder daily for crap that don't belong. This happens very rarely but it's of paramount importance you nip it in the bud.
Everything you need for a full reload including installable app copies, backup setting for all apps that support it, any passwords, all critical data that is on the phone goes on the data drive.
Back the SD card up redundantly with at least 2 hdds that are physically and electronically isolated from each other and the PC. I use more than 2 hdds including a .5tb OTG flashstick. Stagger backups when possible to help limit the possibility all will be compromised by a malware file.
Using the SD card as a data makes the phone more secure and secures your critical data better. Makes backups and reloads much easier.
Done right no PC, cloud crap or internet is needed for a full reload/restore. Plan ahead and develop a plan that protects and preserves your critical data or you will lose it eventually. Plan ahead for a factory reset so it goes fast and seamlessly to a fully restored phone with little or no data loss.
Currently I'm using 68 of 512gb internal and 344 of 465gb on the SD card. Will be upgrading to a 1tb card soon.
blackhawk said:
OP, I think you may be missing the whole point of using a data drive, its primary purpose is to retain critical data. It read speed is somewhat critical in that you need to be able to play music and vids from it with no glitches. The 10+ with a V30 rated card is well capable of that.
Data drives should never used for running apks.
Internal memory should never be used for critical data storage; only the OS, loaded apks, temporary folders and the DCIM folder (for temporary holding until transferred to data drive).
Temporary folders/vetting data before it goes onto the data drive is important, use the download folder for this. Open any downloaded images in the download folder before transferring to the data drive. A malware jpeg will do far less damage here than if it gets on the data drive! I've had a malware jpeg that effected the Android OS, they are real. Generally their rein of terror is confined to the folder they're in, but not always especially if you unwittingly move it!
Scan anything questionable (especially apk downloads)with online Virustotal.
Any downloads not recognized, delete without opening! Trojan preloaders will sometimes get by the browser and autodownload in spite of settings. Look at the download folder daily for crap that don't belong. This happens very rarely but it's of paramount importance you nip it in the bud.
Everything you need for a full reload including installable app copies, backup setting for all apps that support it, any passwords, all critical data that is on the phone goes on the data drive.
Back the SD card up redundantly with at least 2 hdds that are physically and electronically isolated from each other and the PC. I use more than 2 hdds including a .5tb OTG flashstick. Stagger backups when possible to help limit the possibility all will be compromised by a malware file.
Using the SD card as a data makes the phone more secure and secures your critical data better. Makes backups and reloads much easier.
Done right no PC, cloud crap or internet is needed for a full reload/restore. Plan ahead and develop a plan that protects and preserves your critical data or you will lose it eventually. Plan ahead for a factory reset so it goes fast and seamlessly to a fully restored phone with little or no data loss.
Currently I'm using 68 of 512gb internal and 344 of 465gb on the SD card. Will be upgrading to a 1tb card soon.
Click to expand...
Click to collapse
I agree with blackhawk. I have owned Samsung Galaxy devices, including SM-N975F 256GB/256GB since S6.
I store my CD audio on the SD, and I also store my backups of my phone there.
If you end up somehow clobbering your OS and need to restore there is no better way than having a backup that is easily available!
thevmax said:
I agree with blackhawk. I have owned Samsung Galaxy devices, including SM-N975F 256GB/256GB since S6.
I store my CD audio on the SD, and I also store my backups of my phone there.
If you end up somehow clobbering your OS and need to restore there is no better way than having a backup that is easily available!
Click to expand...
Click to collapse
Exactly. I just upgraded from a .5tb to a 1tb V30 SD card on my N10+.
These speeds are real usage and more then fast enough to use as a data drive for streaming vids, whatever.
Internal copy times:
Old .5tb card (read speed)
SD card > internal memory [email protected]
New 1tb card (write speed)
Internal memory>SD card [email protected]
Both cards are V30 Sandisk Extremes.
N975U running on Pie.
The N10+ is a snappy fast device with exceptional capabilities if used correctly.
By comparison the new Samsung flagships suck.
My other N10+ N975U1 it came factory loaded with Android 10, neither one will be upgraded.
Sandisk Extreme V30 rated, 1tb:
Related
I keep looking at other forums and am trying to figure out if the SD card in the problem why the phone freezes? Does anyone know anything about this... Agree or Disagree
ldominguez1986 said:
I keep looking at other forums and am trying to figure out if the SD card in the problem why the phone freezes? Does anyone know anything about this... Agree or Disagree
Click to expand...
Click to collapse
I happen to agree, based on the evidence in the half-dozen more threads here discussing that same thing. It'll be pretty easy to determine if that's your issue...try running the phone without the card in it, and see if that makes a difference.
Now, technically, I believe the issue is related to the card, but may not be beacuse of the card itself....it seems like the phone chokes when there's a lot of files on the card and it has to index them. People who install apps to the card seem to experience this (or at least report it) more than people who don't, which would support that theory because installing apps to the card fills it up with files faster (per MB of space) than even moving a bunch of music might...and a large number of files to index could lead to this kind of behavior (theoretically) as opposed to just a card that was "full" by occupied volume. Again, you can test this by starting with an empty card, then filling it up gradually, and seeing if the issue appears at some point in the process.
In my opinion, the commonly-seen lagging issues in these phones may often (but not always) be casued by a combination of factors:
-class-2 card
-high file count on the card
-sense's (and maybe winmo's..?) constant re-indexing of card contents
Now, some people have reported that copying the card's contents to your desktop, reformatting the card, then copying the files back on to it resolves the issue for them. So, bottom line...who knows?
EDIT: here's maybe a better explanation (by example) of what I'm trying to say about the card being "full"...
Example 1: you have a handful of .mkv files ripped straight from bluray on your card, ~2GB each....putting 7 of those files on your (16GB) card would almost fill the available volume. But, since that's a small number of files, it wouldn't take the phone long to index them at all, despite the card being almost completely full. (again, my guess)
Example 2: you install a bunch of apps (say, 30-40), and almost all of them to the card. Even though those apps won't eat a whole lot of space on the card total (far less than 1GB probably), each one can have potentially dozens of individual files installed for it. In this case, the card wouldn't show as being very full (just from the apps anyway), but the large number of files would potentially cause any indexing of the card to slow down in proportion. (guess what...still just my guess) And, a lower-class card could contribute to the slowness in this case too...that bottleneck could multiply the effects.
It may help some people out to hide the program folders on the card from indexing, just to reduce the file count that has to be sorted through, but that's just an idle thought that just occured to me.
sirphunkee said:
I happen to agree, based on the evidence in the half-dozen more threads here discussing that same thing. It'll be pretty easy to determine if that's your issue...try running the phone without the card in it, and see if that makes a difference.
Now, technically, I believe the issue is related to the card, but may not be beacuse of the card itself....it seems like the phone chokes when there's a lot of files on the card and it has to index them. People who install apps to the card seem to experience this (or at least report it) more than people who don't, which would support that theory because installing apps to the card fills it up with files faster (per MB of space) than even moving a bunch of music might...and a large number of files to index could lead to this kind of behavior (theoretically) as opposed to just a card that was "full" by occupied volume. Again, you can test this by starting with an empty card, then filling it up gradually, and seeing if the issue appears at some point in the process.
In my opinion, the commonly-seen lagging issues in these phones may often (but not always) be casued by a combination of factors:
-class-2 card
-high file count on the card
-sense's (and maybe winmo's..?) constant re-indexing of card contents
Now, some people have reported that copying the card's contents to your desktop, reformatting the card, then copying the files back on to it resolves the issue for them. So, bottom line...who knows?
EDIT: here's maybe a better explanation (by example) of what I'm trying to say about the card being "full"...
Example 1: you have a handful of .mkv files ripped straight from bluray on your card, ~2GB each....putting 7 of those files on your (16GB) card would almost fill the available volume. But, since that's a small number of files, it wouldn't take the phone long to index them at all, despite the card being almost completely full. (again, my guess)
Example 2: you install a bunch of apps (say, 30-40), and almost all of them to the card. Even though those apps won't eat a whole lot of space on the card total (far less than 1GB probably), each one can have potentially dozens of individual files installed for it. In this case, the card wouldn't show as being very full (just from the apps anyway), but the large number of files would potentially cause any indexing of the card to slow down in proportion. (guess what...still just my guess) And, a lower-class card could contribute to the slowness in this case too...that bottleneck could multiply the effects.
It may help some people out to hide the program folders on the card from indexing, just to reduce the file count that has to be sorted through, but that's just an idle thought that just occured to me.
Click to expand...
Click to collapse
Thank you, I do understand what you mean by the amount of files on the card. By the way, are you havong freezing problems with your phone??
ldominguez1986 said:
Thank you, I do understand what you mean by the amount of files on the card. By the way, are you havong freezing problems with your phone??
Click to expand...
Click to collapse
Actually, no...I've had absolutely zero issues with this phone, and I've had it (and used it constantly) for two weeks as of tonight. No freezing, no lag, nada. I don't keep a ton of stuff on my memory card (~15 mp3's, 4 .avi's, and 30-40 archived cabs, small handful of other junk), and I don't install any apps there (though I haven't bothered to remove the stock stuff put there by tmo).
I experience this lag, and altough i kinda agree with the card being the issue at the same time i am kind of hesitant. See the Card is a Class 2 which in theory will have a throughput of about 2mb a sec right? Mine peaks out at about 2.8mbps..... to me thats fast.... so i am not sure but i feel like the choke point is porbably in hardware. Again this is probably all bogus lol.
Like i said i do have this problem too, and i even reformatted my SD card and loaded all my files again. The problem still persist, and i really only notice it when i am listening to music via usb in my car. Also when i am scrolling through the pictures in my gallery(pics are in the SD).
Hope this makes atleast a bit of sense lol.
Disable Document Indexing by editing the registry or using a cab floating around the forums. Do a quick search and you should find it. This eliminates that lag no matter how many files on you SD card, with no degradation of performance opening files on the card that I can see.
nice man, thanks will have to look into that...
I have two HD2s (mine and my wife's). The experience with the two phones couldn't be more different. Mine has been perfect. My wife's has been very problematic. She has experienced slow, laggy performance, freezing that is only cured by pulling the battery, inability to unlock, text messages freezing for a minute plus, etc....... She isn't happy in the least that I convinced her to get rid of her blackberry.
On my wife's phone. I have tried a hard reset, various tweaks from these forums, switching in a 4GB class 6 card, removing the SD card completely and a few other things. Some helped a little but the phone just never worked right. It is currently being replaced by Tmo. With the troubleshooting I did I can't blame the SD card for the problems that phone had.
My phone on the other hand has been great and I have not had any problems with the SD card. I install all my games and non-essential apps to the SD card. I have ~650 MP3s on the card as well as ~900 various files that I take to and from work. There is a little over 8GB of data on the card with all these files. The only lag I have experienced is when switching to the HTC media player it takes a while (< 1 min) for it to index all my music and get to a usable state. I can try swapping in a 4 GB class 6 card to see if it makes a difference though since I have not had a problem I'm not sure I will notice a difference.
jehlinger said:
Disable Document Indexing by editing the registry or using a cab floating around the forums. Do a quick search and you should find it. This eliminates that lag no matter how many files on you SD card, with no degradation of performance opening files on the card that I can see.
Click to expand...
Click to collapse
Will that mess with anything on the media player, tho? Like will it still sort the music into albums, artists, etc on the HTC media player?
illconn said:
I experience this lag, and altough i kinda agree with the card being the issue at the same time i am kind of hesitant. See the Card is a Class 2 which in theory will have a throughput of about 2mb a sec right? Mine peaks out at about 2.8mbps..... to me thats fast.... so i am not sure but i feel like the choke point is porbably in hardware. Again this is probably all bogus lol.
Like i said i do have this problem too, and i even reformatted my SD card and loaded all my files again. The problem still persist, and i really only notice it when i am listening to music via usb in my car. Also when i am scrolling through the pictures in my gallery(pics are in the SD).
Hope this makes atleast a bit of sense lol.
Click to expand...
Click to collapse
From wikipedia, here's info on the speeds of the different class-ratings for SD cards:
The following are the ratings of some currently available cards:
Class 2: 16 Mbit/s (2 MB/s)
Class 4: 32 Mbit/s (4 MB/s)
Class 6: 48 Mbit/s (6 MB/s)
Class 10: 80 Mbit/s (10 MB/s)
Click to expand...
Click to collapse
so, if your transfers are capping out at 2.8Mbps, that's just a hair more than 1/8th of the 2MBps that the card should be able to handle.
jehlinger said:
Disable Document Indexing by editing the registry or using a cab floating around the forums. Do a quick search and you should find it. This eliminates that lag no matter how many files on you SD card, with no degradation of performance opening files on the card that I can see.
Click to expand...
Click to collapse
Will the phone work as normal after installing the cab?? I am knew to xda and winmo. Been on android os since it came out. I hate to ask but could someone post the link for that .cab file that fixes the lag
I saw that sirphunkee had posted in another thread that simply turning off your "recent documents" tab in sense should stop the indexing and therefore the lag as well. I had turned off the recent documents tab from almost the start of using the phone. I have not experienced the lag problem so this might be a testament to this working. I will turn it back on and see if things change for the worse throughout the day.
UPDATE: I have a had a little time to play with it during my lunch break. Everything seems to be fine with recent documents tab turned on. The slider seems a little slugish in now, like there is a second of lag before it moves. It doesn't happen all the time and I may not notice if I wasn't looking for it. I can brows just fine in the file explorer, texting isn't a problem other than the clunky interface, all is well so far.
Also of note is that I am running the stock ROM with co0kie's home tab and a slew of other visual mods (mostly transparencies). I also made quite a few changes to memory allocation via registry edits. This might be the difference and worth trying. I made many of the changes noted in this thread, basically all of them after "Suitable for all ROMs" and before "Added 11/2/10". I wish I would have thought about this earlier.
Has anyone laid out the procedure for what to do with a new SD card and WP7 install? I've noticed many posts about it but no one saying exactly "this is what to do". I think this might be why there are so many posts about SD card failures. So if I have a new SD card and an HD2 and I want WP7, what do I do? Thanks ahead of time... Mod if there is an answer to this, I couldn't find it.
thuddome said:
Has anyone laid out the procedure for what to do with a new SD card and WP7 install? I've noticed many posts about it but no one saying exactly "this is what to do". I think this might be why there are so many posts about SD card failures. So if I have a new SD card and an HD2 and I want WP7, what do I do? Thanks ahead of time... Mod if there is an answer to this, I couldn't find it.
Click to expand...
Click to collapse
If you're just planning to run WP7 (so no fancy dualbooting with Android), there's not much to do, besides backing up anything on the card that you would like to keep. Your phone will create the necessary partitions and take care of the formatting on first boot, if I'm not mistaken.
Not really sure what you mean by "SD card failures". I don't recall reading any posts about that, unless you're referring to the random problems people are having with WP7 and some brands/types of SD cards (not really the result of any card failure).
aye what he said, if you have issues such as lag, wifi not working, random reboots etc then its an SD issue, that means you are out of luck with that current card, . Dont believe anyone when they tell you to buy a spacific card, there is no consistancy in the building of these things so where as you might have issues, someone else with the same card may be fine.i personally have had a wee bit of luck by filling my card with more music
the story is, i had no issues at all with my SD card, but one day after dumping some more music on i started getting reboot issues, took the music off and all was well, then i tried slapping more music on, about 200MB more, and that was it, all is ok again.
its a pure guess, well perhaps an educated guess, but i believe that for whatever reason WP7 had issues accessing a portion of my card, by filling it up some more it prevented WP7 from using it, and thus all is ok again, to be clear, the music played fine however!
dazza9075 said:
aye what he said, if you have issues such as lag, wifi not working, random reboots etc then its an SD issue, that means you are out of luck with that current card, . Dont believe anyone when they tell you to buy a spacific card, there is no consistancy in the building of these things so where as you might have issues, someone else with the same card may be fine.i personally have had a wee bit of luck by filling my card with more music
the story is, i had no issues at all with my SD card, but one day after dumping some more music on i started getting reboot issues, took the music off and all was well, then i tried slapping more music on, about 200MB more, and that was it, all is ok again.
its a pure guess, well perhaps an educated guess, but i believe that for whatever reason WP7 had issues accessing a portion of my card, by filling it up some more it prevented WP7 from using it, and thus all is ok again, to be clear, the music played fine however!
Click to expand...
Click to collapse
That's interesting because I have had the same experience. I have been playing around with multiple size cards and brands. I have yet to get one work right. I have also discovered how you format them makes a difference; for example I have a Patriot class 4 16GB card that using EASEUS to format (low level) it worked but had lag at certain times, for example when going through setup on a fresh install of WP7. It was at a dead crawl with the same config with Android. I then formatted it with Minitool and it was unusable (dead dead crawl) with either WP7 and Android. I also tested a Kingston class 4 32GB w/ wp7 and it was about the same as the Patriot w/ EASEUS formatting. No card I have found outperforms (in the phone) the Sandisk Class 2 16GB card that came with the phone. My suspicion is that the cards that came with the phones have had something done to the sectors by the phone manufacturers. I need to hear from someone who really knows the I/O and Cardbus architecture of phones. My point is there should be a way to get all cards working with any phone, might not be to specs of the card but between tweaking formatting and other hacks they all should work.
thuddome said:
That's interesting because I have had the same experience. I have been playing around with multiple size cards and brands. I have yet to get one work right. I have also discovered how you format them makes a difference; for example I have a Patriot class 4 16GB card that using EASEUS to format (low level) it worked but had lag at certain times, for example when going through setup on a fresh install of WP7. It was at a dead crawl with the same config with Android. I then formatted it with Minitool and it was unusable (dead dead crawl) with either WP7 and Android. I also tested a Kingston class 4 32GB w/ wp7 and it was about the same as the Patriot w/ EASEUS formatting. No card I have found outperforms (in the phone) the Sandisk Class 2 16GB card that came with the phone. My suspicion is that the cards that came with the phones have had something done to the sectors by the phone manufacturers. I need to hear from someone who really knows the I/O and Cardbus architecture of phones. My point is there should be a way to get all cards working with any phone, might not be to specs of the card but between tweaking formatting and other hacks they all should work.
Click to expand...
Click to collapse
My phone came with a Sandisk 2GB card and WP7 has offered me a SD Card Failed message regardless of what technique I have used to Format it...
thuddome said:
That's interesting because I have had the same experience. I have been playing around with multiple size cards and brands. I have yet to get one work right. I have also discovered how you format them makes a difference; for example I have a Patriot class 4 16GB card that using EASEUS to format (low level) it worked but had lag at certain times, for example when going through setup on a fresh install of WP7. It was at a dead crawl with the same config with Android. I then formatted it with Minitool and it was unusable (dead dead crawl) with either WP7 and Android. I also tested a Kingston class 4 32GB w/ wp7 and it was about the same as the Patriot w/ EASEUS formatting. No card I have found outperforms (in the phone) the Sandisk Class 2 16GB card that came with the phone. My suspicion is that the cards that came with the phones have had something done to the sectors by the phone manufacturers. I need to hear from someone who really knows the I/O and Cardbus architecture of phones. My point is there should be a way to get all cards working with any phone, might not be to specs of the card but between tweaking formatting and other hacks they all should work.
Click to expand...
Click to collapse
Lower class sd-cards have way better random reads/write speeds. This means they are better for storing file-caches, system files, and other rather small/scatered files. A higher class card will have awesome read/write speeds, but they do sacrifice the random speeds (they will preemptively load huge chunks of the file they are writing/reading to/from. So, they will have an overhead when accessing a file, that will be attenuated only if the operations made with that file are long. If u wanna write/read a large chunk of small non-sequential file/s, a class 2 is awesome. Which means that these cards are adequate form OS being run from them. Of course, when syncing with zune, you WILL notice a very decreased speed (since the files are being passed sequencially), but the system per se will operate silky smooth.
Hope this helped. Kudos mate
ei05035 said:
Lower class sd-cards have way better random reads/write speeds. This means they are better for storing file-caches, system files, and other rather small/scatered files. A higher class card will have awesome read/write speeds, but they do sacrifice the random speeds (they will preemptively load huge chunks of the file they are writing/reading to/from. So, they will have an overhead when accessing a file, that will be attenuated only if the operations made with that file are long. If u wanna write/read a large chunk of small non-sequential file/s, a class 2 is awesome. Which means that these cards are adequate form OS being run from them. Of course, when syncing with zune, you WILL notice a very decreased speed (since the files are being passed sequencially), but the system per se will operate silky smooth.
Hope this helped. Kudos mate
Click to expand...
Click to collapse
just about to write all of that myself but you beet me too it!
to add to that, no two cards are alike, make and model makes no difference hence my issue with the "working SD card" thread on here, there is no way to know other than trying it
My wee issue is possibly related to some dodgy parts within the card, it reports perfect but if internal components are not consistant it may explain my rather odd situation
dazza9075 said:
just about to write all of that myself but you beet me too it!
to add to that, no two cards are alike, make and model makes no difference hence my issue with the "working SD card" thread on here, there is no way to know other than trying it
My wee issue is possibly related to some dodgy parts within the card, it reports perfect but if internal components are not consistant it may explain my rather odd situation
Click to expand...
Click to collapse
In your situation i'd risk say it might have occured some corruption when transfering those musics. At least, considering that all is well now. It is unlikely that a sector of your card is/was permanently damaged, as repeting the operation worked, aye? Also, since I don't know what the file system is used by WP7, I do not know what maintenance the file system requires (such as defragmentation and whatnot)
perhaps, but it is repeatable, if i remove 400MB of music from my device its fine, if then copy 200 on to the card it reboots randomly, if i then copy the additional 200 back to the card it works fine
Potentially your correct, it may be some sign of wear on the card, but either way the music plays fine, which possibly suggests the random access speeds issue again, if it is sub-par sectors on the card that may explain it
The one described here: http://forum.xda-developers.com/showthread.php?t=1010807
http://forum.xda-developers.com/showthread.php?t=1021647
Doubled my read speeds. Went from @15 to 30+. Gallery seems snappier. Media Scanning finishes up quicker.
However - Write speeds seem wonky, they vary from 2 to 6 depending on how the phone feels I guess. I don't think the patch is a monumental change, and it makes me wonder why the cache size wasn't increased to begin with since it obviously effects read speeds. Maybe Samsung knows more than us.
Will this not shorten the lifespan of the SD card? There has to be a downside somewhere...
I tried it and it works great. Just make sure after you flash it you check the permissions to make sure it is correct.
LordLugard said:
Will this not shorten the lifespan of the SD card? There has to be a downside somewhere...
Click to expand...
Click to collapse
It just changes the read-ahead cache on the phone so your phone reads larger chunks of the sd card in one burst. So instead of doing 5 reads (for example) the phone can read 5x as much at one time and hold that data in the cache. That way it doesn't get stuck waiting on the sd card every time it runs through the data held in the cache.
No big downside for this one.
Finally decided to buy a new laptop to replace my old one. It came with Windows 8 (x64) pre-installed and 8GB DDR3 physical RAM.
My question is: Is it worth using ReadyBoost on the system?
Currently it only has a standard 5400rpm HDD, and an SSD isn't an option for the time being. I have a 16GB Class 10 UHS1 MicroSD card which I had dedicated to ReadyBoost, but after some digging, it seems like ReadyBoost is pretty much useless if the system has more than 1GB of physical RAM.
Sent from my GT-N7105
ReadyBoost is potentially useful with any amount of RAM, but the point at which it becomes useful varies depending on usage. If you only ever run one 2MB install footprint / 5MB working set program on Windows, 1GB of RAM is plenty and ReadyBoost won't help you; SuperFetch will happily cache that program in the handful of spare RAM that the system already has. If you run a ton of background processes that use up 6GB of RAM at all times, and then periodically want to run a program that has a 10GB install footprint, then 16GB of ReadyBoost (which is just SuperFetch cache) will dramatically improve the load times for that program.
Thanks for that. I've had my lappy for more than a month now and my RAM usage rarely goes above 20% (and never goes above 24%) so I don't think RB is necessary for me.
I also read on somewhere that ReadyBoost can wear out a device through constantly writing to it. Is that true? Can ReadyBoost do more harm than good?
Sent from my GT-N7105
I dont use RB, nor superfetch either..truth is i disable all but bare essentials.
Ive also heard that rumor, about excessive wear. Im sure there is some truth to that. Usage causes wear. Just how much wear I have no idea. Im sure it dont help mechanical drives...ssd's prolly dont bother them. *shrugs*
Best practice I have found is just to keep your system maintained, and clean of bloat/malware.
With todays hardware, gains im sure are marginal at best. Seriously you cant wait n extra second for that app to load?
Sent from my LG-E730 using xda app-developers app
@KCA.: In your case, I don't think you would benefit much from ReadyBoost, no. You can always add it later if you want, though. I mostly find it useful with games that have very large install footprints, as Flash memory reading is typically much faster than magnetic hard disk reading. However, reading from RAM is much faster still, and if you're only actively using up to about 2GB of your RAM, that means the other 6GB is already being used for a SuperFetch cache.
@13lack13ox: Your system, your choice of how to use it... but unless you're already seriously stressing out the capabilities of you hardware, caching (which is all that SuperFetch and ReadyBoost are) can significantly improve performance. On an old machine I had with 1280MB of RAM, loading Eve Online (which at the time had about a 2GB install footprint) took almost twenty seconds on Windows XP and only about six seconds on Vista (with a 2GB SD card being used for ReadyBoost) even though the system was massively above the XP minimum specifications and only slightly above the Vista ones. It's a much bigger difference than a mere extra second.
As for wear, it's true that RB will shorten the life of Flash storage. NAND Flash memory (the type used in all flashdrives, SD cards, SSDs, and so forth) has a limited number of write operations for a given block of storage, and ReadyBoost will probably write to your SD card much more often than it would be written to if it just sat in your camera or similar. However, the write limits for modern Flash storage are typically in the tens or hundreds of thousands of times, and the storage controllers use a technique called "wear leveling" to ensure that no portion of the storage gets burned out early. The SD card will almost certainly become obsolete due to size and speed well before ReadyBoost would wear it out, so if you want to use it for that purpose, go ahead.
13lack13ox said:
Best practice I have found is just to keep your system maintained, and clean of bloat/malware.
With todays hardware, gains im sure are marginal at best. Seriously you cant wait n extra second for that app to load?
Click to expand...
Click to collapse
Lol can't argue with that.
GoodDayToDie said:
@KCA.: In your case, I don't think you would benefit much from ReadyBoost, no. You can always add it later if you want, though. I mostly find it useful with games that have very large install footprints, as Flash memory reading is typically much faster than magnetic hard disk reading. However, reading from RAM is much faster still, and if you're only actively using up to about 2GB of your RAM, that means the other 6GB is already being used for a SuperFetch cache.
As for wear, it's true that RB will shorten the life of Flash storage. NAND Flash memory (the type used in all flashdrives, SD cards, SSDs, and so forth) has a limited number of write operations for a given block of storage, and ReadyBoost will probably write to your SD card much more often than it would be written to if it just sat in your camera or similar. However, the write limits for modern Flash storage are typically in the tens or hundreds of thousands of times, and the storage controllers use a technique called "wear leveling" to ensure that no portion of the storage gets burned out early. The SD card will almost certainly become obsolete due to size and speed well before ReadyBoost would wear it out, so if you want to use it for that purpose, go ahead.
Click to expand...
Click to collapse
Thanks for the info. I'll just leave it. Seems like the benefits are negligible.. A waste of a port
KCA. said:
Finally decided to buy a new laptop to replace my old one. It came with Windows 8 (x64) pre-installed and 8GB DDR3 physical RAM.
My question is: Is it worth using ReadyBoost on the system?
Currently it only has a standard 5400rpm HDD, and an SSD isn't an option for the time being. I have a 16GB Class 10 UHS1 MicroSD card which I had dedicated to ReadyBoost, but after some digging, it seems like ReadyBoost is pretty much useless if the system has more than 1GB of physical RAM.
Sent from my GT-N7105
Click to expand...
Click to collapse
Readyboost uses high speed USB drives to swap kernel memory. If you have an SSD, there is no point. If you are using a conventional HDD, the readyboost will improve performance (that is why they made it). I use it on all my Windows 7 machines except my ultraportable, which has an SSD. With USB drives so cheap, why not? Of course, you need to make sure the USB drive supports ReadyBoost; not all of them have good enough performance.
Unless MS changed this since Vista, ReadyBoost does *NOT* swap kernel memory. ReadyBoost had a specific requirement that removing the device while it was in use shouldn't disrupt the system (even so far as crashing a program). Removing paged-out kernel memory would very quickly cause a BSOD. If you have any additional info, please do share it; I'm curious.
Now, it's possible that RB will act as a read cache (not a write cache, because any changes must be written down to disk) for the pagefile. In that case, it may still improve performance. However, what I read about it initially said it was simply additional SuperFetch cache (SF typically uses unallocated RAM to pre-load files that it expects you to need soon, based on past usage patterns, so that they are available instantly without waiting on disk access). For machine with limited RAM (or which load very large programs or files), SF can dramatically improve load times. RB storage, while not as fast as RAM, is still faster than disk access.
In any case, if you have gobs of RAM, ReadyBoost doesn't matter. The kernel won't be paging stuff out, so no need for a kernel swap cache. The pagefile won't be getting much use at all, in fact (some writes to "clean" changes in memory so it can be swapped out fast, but very few reads). Unless the files you access are large than your free RAM, they shouldn't slow anything down either.
GoodDayToDie said:
Unless MS changed this since Vista, ReadyBoost does *NOT* swap kernel memory. ReadyBoost had a specific requirement that removing the device while it was in use shouldn't disrupt the system (even so far as crashing a program). Removing paged-out kernel memory would very quickly cause a BSOD. If you have any additional info, please do share it; I'm curious.
Now, it's possible that RB will act as a read cache (not a write cache, because any changes must be written down to disk) for the pagefile. In that case, it may still improve performance. However, what I read about it initially said it was simply additional SuperFetch cache (SF typically uses unallocated RAM to pre-load files that it expects you to need soon, based on past usage patterns, so that they are available instantly without waiting on disk access). For machine with limited RAM (or which load very large programs or files), SF can dramatically improve load times. RB storage, while not as fast as RAM, is still faster than disk access.
In any case, if you have gobs of RAM, ReadyBoost doesn't matter. The kernel won't be paging stuff out, so no need for a kernel swap cache. The pagefile won't be getting much use at all, in fact (some writes to "clean" changes in memory so it can be swapped out fast, but very few reads). Unless the files you access are large than your free RAM, they shouldn't slow anything down either.
Click to expand...
Click to collapse
OK, I should not have mentioned kernel. I found a short article that indicates it swaps out pieces of the software that would otherwise be swapped to the slower HDD. It will not crash because when it writes to the readyboost, it also writes to HDD - but it can read the readboost much faster than the HDD, so it increases performance when it has to pick up that data again. And the article mentions that more memory is better than readyboost (but I still use it on my Windows 7 machine with lots of memory).
Earlier explanations did not mention the pagefile, although that seems to be to be the better name for what is swapped. But I'm not sure about that. The early web postings indicated that it wrote parts of the Windows system that were frequently accessed.
http://blogs.msdn.com/b/tomarcher/archive/2006/06/02/615199.aspx?Redirected=true
EDIT: From the Q&A it sounds like it is indeed the pagefile.
Cool, thanks for the link! Sounds like it does indeed act as a read cache. Very cool.
Still probably not a *big* boost on a machine with lots of RAM, but I expect it'll help anyhow.
This sucks. I got a 16 GB model some time ago expecting marshmallow and a good microSD card to be the ticket. I have a Sandisk Ultra 128 Gb class 10 card which is well regarded for speed and reliability. I FINALLY got Marshmallow recently and went through the process of getting my card reformatted for adaptive storage. I was surprised during the process that the phone gave me a warning that the card was slow and I may experience problems, but I pressed on.
Everything seemed to work fine after the 'conversion' and the phone seemed snappy enough. Though I hadn't yet installed any new programs in the new configuration. I merely backed up photos and audio media that was being stored on the card, and then restored them to their proper location after the reformat to integrate the card with internal storage.
I then installed some apps I had removed to make space on internal storage previously. Now the phone is totally unusable. I get about 1-3 minutes of usage after boot before it hangs up on a screen, or with the notification shade pulled down. The phone just totaly freezes; I can't even power it down (need to look up how to force it to shut down).
What have I gotten myself into? Why would that card be considered 'slow and/or inadequate' when I purchased it less than 6 months ago and it is rated a good and fast card?
Any suggestions on how to proceed? I need and counted on the combined storage capability (or I never would have gone or the 16 Gb model).
Thanks for any help.
oh, and random reboots and also the screen going blank but the phone not actually being off (battery died really fast) overnight. I'm trying to get into the bootloader and do traditional things like clearing dalvik cache (is that current? I haven't done much rooting and messing around with the guts of Andriod since Kit Kat), etc.
I had to revert too. Limited TWRP support, very slow apps, couldn't connect via USB to the SD storage. I bought the 16GB thinking the same thing. Was a mistake as of now.
Besides not being able to do anything with the card in TWRP, I'm having no problems using adaptive storage, and I too use a 128GB SanDisk Ultra.
Sent from my XT1575 using Tapatalk
I'm not worried about TWRP. I'm actually content with the phone non-rooted if adaptive storage works, since it's not carrier locked and I can do things that previously Verizon wouldn't let me. I'm not interested in mucking around with new ROM's and stuff anymore; too busy with other tinkering projects and i have plenty of other viable devices to do that with (amazon phone and tablet, older android phones, etc.). I want this one to be a stock daily driver; but I want it to f'ing work as indicated.
I just got done doing a factory reset, formatting the SD card as internal and restoring (system tool; is that a Moto thing or Lollipop+?). We'll see how it goes. I may just have mucked it up trying to convert to adaptive storage after having used it with Lollipop AND even moving some apps to the SD card.