I did a search but I only have a phone to do this from so hopefully I didn't miss it.
Is it possible to make ram run off of the SDCard in a new partition (or even a current partition) simalar to Readyboost for vista? With all these home screen apps taking up so much RAM is would be helpful.
I am what you would call an advanced noob at this so don't flame me if I'm totally off.
I don't believe android supports something like this, this is sort of like Virtual Memory in Windows. However, the effectiveness of this isn't very good, moreover, the speed of the SD card or even support for this feature is... unknown. So, for now, I'm going to have to say I don't think so.
http://forum.xda-developers.com/showthread.php?t=483110&highlight=swap
Yeah, it's in the market now too. I haven't tried it out though, I don't want to make my microSD card last even less now... =P
axion68 said:
http://forum.xda-developers.com/showthread.php?t=483110&highlight=swap
Click to expand...
Click to collapse
Thank you for that.
amgupt01 said:
Yeah, it's in the market now too. I haven't tried it out though, I don't want to make my microSD card last even less now... =P
Click to expand...
Click to collapse
Any idea how much less?
mmafighter077 said:
Any idea how much less?
Click to expand...
Click to collapse
Linux swap partitions aren't designed for flash memory like Readyboost is. Microsoft says Readyboost is designed to make your memory last at least 10 years with moderate use, but Linux swap might stress it more. MicroSDs are really cheap though.
nm page didn't load right, i thought i was the first post with useful info.
mmafighter077 said:
Any idea how much less?
Click to expand...
Click to collapse
It should still last you years.
Each sector on flash media can be written to something like 10,000 times. After that's worn out, I believe it just ignores that sector. Meaning when your mem stick starts dying, you'll just have less space available to you.
I currently run my notebook with a Compact Flash card in the notebooks built in CF slot, and run my swap file on that. It's been a while, and it still hasn't died.
It's quite a long time - a sector isn't written 10,000 times sequentially, the hardware in the chip moves the writes around to avoid wearing out any single element (wear levelling), and if any single element does go it'll just ignore it, as you mentioned.
Any modern SD is likely to outlive the phone, basically. I've got entire computers running off SD and I've never had a failure (hard drives fail way more often, due to their mechanical nature).
my android is running off a SD card.
anyone please exxplain what is 'NAND'?
I think it is short for Nandroid. Which is a backup made by either Titanium backup,CWM or another program that can do advanced backups.
Sent from my GT-N7000 using Tapatalk
NAND flash memory
NAND flash memory is a type of non-volatile storage technology that does not require power to retain data.
There are two types of flash memory, NAND and NOR. The names refer to the type of logic gate used in each memory cell. (Logic gates are a fundamental building block of digital circuits). NOR flash was first introduced by Intel in 1988. NAND flash was introduced by Toshiba in 1989.
The two chips work differently. NAND has significantly higher storage capacity than NOR. NAND flash has found a market in devices to which large files are frequently uploaded and replaced. MP3 players, digital cameras and USB drives use NAND flash. NOR flash is faster, but it's also more expensive. NOR is most often used in mobile phones.
Some devices use both NAND and NOR. A pocket PC, for instance, may use embedded NOR to boot up the operating system and a removable NAND card for all its other memory/storage requirements. NAND has a finite number of read-write cycles, though the total number continues to increase with each generation of chips. If the NAND card wears out, the user simply buys a new one and the device continues to function. By passing the expense of additional storage on to the consumer, manufacturers have been able to lower the price of consumer electronic devices significantly.
An important goal of NAND flash development has been to reduce the cost per bit and increase maximum chip capacity so that flash memory can compete with magnetic storage devices like hard disks. New developments in NAND flash memory technology are making the chips smaller, increasing the maximum read-write cycles and lowering voltage demands. Such improvements will continue make the technology even more common in laptops and thin client desktop computers.
MoPhoACTV Initiative
Thank you, very interesting reading.
Thanx everybody for the info, appreciate it so much... looking for nand for htc hd mini...
solleh.mc said:
Thanx everybody for the info, appreciate it so much... looking for nand for htc hd mini...
Click to expand...
Click to collapse
That makes no sense. What exactly do you think it is you are looking for? Memory? SD card? Backup?
DirkGently said:
That makes no sense. What exactly do you think it is you are looking for? Memory? SD card? Backup?
Click to expand...
Click to collapse
this is what im talking about...
http://forum.xda-developers.com/showthread.php?t=1455555
Photonic CM 7.2; No GPS
I'd been using this rom since day 1 Schlund upload it at Xda-Developer.
Until now my GPS dont working at all, anyone can help me out?
regards...
I dabble in microprocssors such as AVRs and such and they have a flash life of around 40,000 flashes before they are dead.
I was wondering what the "Flash Life" of tablets are. Will there be a time when they will finally burn out?
Now 40,000 flashes are more than anyone would be able to flash this device in a reasonable tablet lifetime before it is obsolete. Just wondering what the number would be.
Since all flash is in the eMMC, firmware flashes count as normal writes. The eMMC is using MLC or even TLC, so we are talking about a few 1000 writes for each cell, distributed over the full capacity by the eMMC's FTL for wear leveling. So let's say 64 GB * 1000 = 64 TB total writes, but this has to be divided by the write amplification factor. It's a bit hard to estimate write amplification due to the primitive controller and FTL - it could even be up to 1000 in the worst case of all random 4 kB writes (each would need to rewrite a full erase block). More realistic may be a factor of 5 to 20 - so let's guess 64 TB / 10 = about 6 TB written in total.
Fascinating question:
Only thing I see are claims from Hynix (formerly Hyundai) that their recent SSD and NAND memory has up to 2,000,000 hours MTBF.
Don't see how this claim would hold water in a real sense....just a calculated guess on the manufacturers part.
Hard to tell when write failure will occur at the lower voltage levels used for eMMC's.
I'd think 40 to 60,000 hours would be more in line.
Thanks _that.
I should be able to burn this thing out in a month or so. LOL J/K.
When flashing does the eMMC get totally erased before writing or are just the addresses used in the code written to the chip? This would determine the life of the chip as a total erase would shorten the life. Am I correct in assuming this or is my understanding all wrong?
Is there a data sheet available for the eMMC used in these devices or is it an ASUS trade secret?
Thats OK, are you talking about actual hours flashing or just the run time of the chip?
Dee Envy said:
Thanks _that.
I should be able to burn this thing out in a month or so. LOL J/K.
When flashing does the eMMC get totally erased before writing or are just the addresses used in the code written to the chip? This would determine the life of the chip as a total erase would shorten the life. Am I correct in assuming this or is my understanding all wrong?
Is there a data sheet available for the eMMC used in these devices or is it an ASUS trade secret?
Thats OK, are you talking about actual hours flashing or just the run time of the chip?
Click to expand...
Click to collapse
Ah I was looking at time before failure on Hynix eNAND.
That 2 million hours seemed a bit way out.
Just searching around for a data sheet on the Hynix M26M64002BNR is turning into a dead end.
Everything goes to an HY27 number looks like the chip has been replaced from the maker.
I was hoping I could find actual read\write white paper for the chip.
Dee Envy said:
When flashing does the eMMC get totally erased before writing or are just the addresses used in the code written to the chip?
Click to expand...
Click to collapse
Flash memory has 3 operations: erase, write, read.
Magnetic storage has only 2: (over)write, read.
So, to overwrite something in flash memory, an erase operation is always necessary. And this operation has a granularity in the megabyte range - that's why random 4k writes are so slow.
If you want to know how flash cards work, read this:
https://wiki.linaro.org/WorkingGroups/KernelArchived/Projects/FlashCardSurvey
Thanks for the link, _that.
There's some good reading there.:good:
Moving the intent of a few posts on LineageOS thread to here.
rb1979 said:
Hi everyone,
Some of you reported that SD Card stopped working. This happened to me too today after about 20 hours after the latest update. The case with me is it doesn't fix itself even after a restart. I'm kind of stuck, whatever I want to do with the SD Card it wants me format it. I always had it as internal storage with apps and other things there. I have the the backup from the before the update. Will that fix if I restore it? Just want to mention that I update every week and never missed one. I had very minor issues up until now. Week in and week out everything has been fine and I started using the rom with the first release, all clean, full format and then weekly over the air updates every single week.
If anybody know any solution please let me know, if nothing works or I don't hear anything I'll probably try the backup restoration. BTW, to be specific about SD card no working I always get two notifications, one is "Unsupported SanDisk SD card" and the other is "SanDisk SD card missing"
Thank you
Click to expand...
Click to collapse
KrisM22 said:
Use a card brand other than sandisk and size 32GB or less.
Click to expand...
Click to collapse
rb1979 said:
Thank you for you help, I really appreciate it. The problem I see, right or wrong, is that I had this card for a year with no issues, first under stock rom, then under CM, and now under LineageOS up until the latest update with no issues at all. So it's just hard for me to take the card as the problem. Especially after seeing other people reporting it too lately. Do you have more information than just that? Meaning LineageOS and won't ever get along with sandisk or size larger than 32GB because of some external hardware limitation or something like that. Or this is just general knowledge what works best with LineageOS? In the first case I can think about case I can go and invest into a new card but in the second case I can just wait it out until codebase improves. It would good to know more so I can make better decisions.
Thanks for your help again.
Click to expand...
Click to collapse
KrisM22 said:
In my experience, most folks presenting SDcard problems have sandisk. I personally have had problems with sandisk that has led me to avoid them. I prefer samsung. There are many others. edit currently using a pny U3 32GB, but it's an old one and only does 56/29MBs R/W.
Click to expand...
Click to collapse
adityak1303 said:
+1 @KrisM22. I agree that almost all the users that state that there's a problem with their SD card were using a SanDisk SD card including myself. @rb1979, if you really think that your card isn't faulty, then try using it in some other phone. If you face the same errors then your card is faulty. If it works fine on the other phone, only then can it be considered as a problem with the ROM.
Click to expand...
Click to collapse
rb1979 said:
Thanks both of you, I'll do some testing around and get back to you with my findings.
Click to expand...
Click to collapse
KrisM22 said:
I just ordered one of these because I want to test the 64GB thing as it keeps coming up.
Samsung 64GB 100MB/s (U3) MicroSDXC EVO Select Memory Card with Adapter (MB-ME64GA/AM) - $23 + some silly $3 thing to get free shipping over $25. There are faster ones out there but I'm a cheapskate and don't use it enough to justify it.
Click to expand...
Click to collapse
That's most of it - then it goes verbose and wobbly.
I welcome any and all comments about SDcards!
There is no OT here but remember the XDA rules and try to be nice to folks. You can learn without trying to control others' behaviour.
No need to pretend you are TD. (allusion to Alice in Wonderland - Top Doormouse)
Thanks for creating this thread. There are surprisingly few other recent threads that discuss this topic on XDA apart from the one I've previously linked to (https://forum.xda-developers.com/android/help/micro-sd-write-access-format-exfat-t3358275). Also, I'm bringing over the well informed SD related comments that you left behind.
---------------------------
I've got to push back on the apriori assumption that these are specifically Sandisk brand card issues without knowing the specific details of the issues and seeing actual logs, and also without knowing the history of the individual cards in question (details of every device it was connected to and how it was connected, what OS and what file management methods were used, and how full the card typically is, and how frequently it might be disconnected in the middle of a file operations, among other things).
We must be mindful of the fact that the majority of SD cards in circulation are Sandisk cards which means that the majority of reported problems will be on Sandisk cards but this does not mean that the Sandisk cards are experiencing proportionately more issues than other brands. I don't doubt individual experiences, but it they may not speak to a larger picture. For example: Having supported large systems (>300 devices) running Linux directly from SD cards I did not see more problems with Sandisk cards than others. We've not seen enough evidence here to declare that this this is a Sandisk problem.
rb1979 said:
...I had this card for a year with no issues, first under stock rom, then under CM, and now under LineageOS up until the latest update with no issues at all.So it's just hard for me to take the card as the problem
Click to expand...
Click to collapse
The fact that a card has been used for a long time under different circumstances does not support a logical argument that the problem is in the ROM, in fact that supports the logical argument that the problem is with the card.
adityak1303 said:
....if you really think that your card isn't faulty, then try using it in some other phone. If you face the same errors then your card is faulty. If it works fine on the other phone, only then can it be considered as a problem with the ROM.
Click to expand...
Click to collapse
Good advise since, if the cards is having problems it should bring the problems to the other devices. Testing a different card in the first device on which the problem was noticed is also a good test.
--------------------------
Here is some supplemental information specific to Sandisk SD cards' built in data protection on cards experiencing failure. https://forum.xda-developers.com/android/help/micro-sd-write-access-format-exfat-t3358275. To summarize what is there: An SD card may begin to fail unknown to us, and then when the built in data protection is invoked it "breaks" the card with a dirty bit at beginning of drive so it cannot be written to or formatted but still allows us to copy data. The symoptoms when that data protection is invoked are similar to those bing reported by people who can no longer mount the card in Android devices (Android devices require read and write access to mount the card, unlike when the card is access via card reader on computer).
Just an update. I tried to format the card as portable storage (after this failure as internal and being burned I have hard time trusting it now) but it fails. I didn't do any testing with other phones just went straight for format. I might just buy another card. I think the phone specs say it's 32 GB max, is it still the case with different OS or not (meaning it was due to software not hardware) if I could get something higher than 32 (the current broken one is 32) I would go for it.
Thanks
rb1979 said:
Just an update. I tried to format the card as portable storage (after this failure as internal and being burned I have hard time trusting it now) but it fails. I didn't do any testing with other phones just went straight for format. I might just buy another card. I think the phone specs say it's 32 GB max, is it still the case with different OS or not (meaning it was due to software not hardware) if I could get something higher than 32 (the current broken one is 32) I would go for it.
Thanks
Click to expand...
Click to collapse
I believe after you use it as internal, and then try to use it as external, you first have to write an MBR on it and a partition formatted FAT32. i use a bootable stand-alone GPARTED to do that.
http://gparted.org/
Moto says it's limit is 32GB. Folks have, I believe, used much bigger cards on it. Don't know what is the limiting factor - be it software (ROM) , hardware, or licensing (exfat for Microsoft). I have ordered a 64GB Sammy which I should get in 1/2 week so I can test. Course I wouldn't be doing exactly what you would be doing so the test would only show that the G3 could read/write to it. I will only use it as external storage. I don't really "need" 64GB but it will allow me to be a bit more sloppy vis a vis nandroid backups.
It could be that after you format yours, that it will suddenly work just fine. Then again I just had a thumb drive go belly-up from I/O errors - once in a great while, it happens.
KrisM22 said:
... Moto says it's limit is 32GB. Folks have, I believe, used much bigger cards on it. Don't know what is the limiting factor .
Click to expand...
Click to collapse
I've got a 128gb in my Moto G (3rd - XT1540 2GB), and I have used the card for a long time. It works just fine for me, and the space is obviously fantastic to have. Every now and then (every few months or so, I'd say - maybe 3 times in the 18 months I've had it), it does become corrupted, though, and I get those same error messages. A backup, wipe/re-format, and restore, and I put it right back in my phone and it works just fine again. Seems like that's happened in other devices, though, too.
The card is a SanDisk Ultra SL128 (Class 10/UHS-1, man'd Jan 2016). I've only ever used it for external storage, never adopted, and I've only ever formatted the card as FAT32, using my PC. I'm running stock Android 6.0 24.24.1 at the moment, with TWRP.
beachfl said:
I've got a 128gb in my Moto G (3rd - XT1540 2GB), and I have used the card for a long time. It works just fine for me, and the space is obviously fantastic to have. Every now and then (every few months or so, I'd say - maybe 3 times in the 18 months I've had it), it does become corrupted, though, and I get those same error messages. A backup, wipe/re-format, and restore, and I put it right back in my phone and it works just fine again. Seems like that's happened in other devices, though, too.
The card is a SanDisk Ultra SL128 (Class 10/UHS-1, man'd Jan 2016). I've only ever used it for external storage, never adopted, and I've only ever formatted the card as FAT32, using my PC. I'm running stock Android 6.0 24.24.1 at the moment, with TWRP.
Click to expand...
Click to collapse
Thanks - Becoming corrupted every 6 months seems excessive, but with heavy use...? So what do you use it for? Also it sounds like you are using something other than the phone to format it...?
At least you are ready for it and just re-format it!
beachfl said:
I've got a 128gb in my Moto G (3rd - XT1540 2GB), and I have used the card for a long time. It works just fine for me, and the space is obviously fantastic to have. Every now and then (every few months or so, I'd say - maybe 3 times in the 18 months I've had it), it does become corrupted, though, and I get those same error messages. A backup, wipe/re-format, and restore, and I put it right back in my phone and it works just fine again. Seems like that's happened in other devices, though, too.
The card is a SanDisk Ultra SL128 (Class 10/UHS-1, man'd Jan 2016). I've only ever used it for external storage, never adopted, and I've only ever formatted the card as FAT32, using my PC. I'm running stock Android 6.0 24.24.1 at the moment, with TWRP.
Click to expand...
Click to collapse
That may not be drive corruption but rather a corrupted file or files. If it is localize drive corruption it may still be there without having any impact until some data is written to that part of the drive. Unlike platter based hard drives, when these drives actually start to fail they may invoke a built in data protection (dirty bit) which resembles being locked in read only mode preventing the drive from being formatted which is obviously not your case. Have you ever done a sector scan of the drive, eg chkdsk <driveletter> /f /r or done a full format (as opposed to quick format)? Either of those things may flush out localized damage and the scan might fix it but they would take a long time.
KrisM22 said:
Thanks - Becoming corrupted every 6 months seems excessive, but with heavy use...? So what do you use it for? Also it sounds like you are using something other than the phone to format it...?
At least you are ready for it and just re-format it!
Click to expand...
Click to collapse
Yeah I guess it is kinda a small PITA lol. Could just be from me starting and cancelling or moving too many things at once, I don't know.
I've never actually come close to needing all that space to TBH. I could probably do just fine with a 64, but it's nice to know I could record or store hours of HD video, for example, if I need it. I got nearly 30 gigs of music on it. I keep tv and movies on there, too, in case I get caught bored somewhere. Full Nandroid and Titanium backups are on there, as well.
I use a microSD adapter and a small (76 kb) utility for Windows called FAT32Format (Ridgecorp).
---------- Post added at 22:00 ---------- Previous post was at 21:45 ----------
IronTechmonkey said:
That may not be drive corruption but rather a corrupted file or files. If it is localize drive corruption it may still be there without having any impact until some data is written to that part of the drive. Unlike platter based hard drives, when these drives actually start to fail they may invoke a built in data protection (dirty bit) which resembles being locked in read only mode preventing the drive from being formatted which is obviously not your case. Have you ever done a sector scan of the drive, eg chkdsk <driveletter> /f /r or done a full format (as opposed to quick format)? Either of those things may flush out localized damage and the scan might fix it but they would take a long time.
Click to expand...
Click to collapse
I've had that problem before, too, but not on the 128 I have in my phone now. That is very frustrating. One of my 32 gb cards suddenly went into "read-only" mode as you describe, and nothing I can do will get it useable again. All the files are still readable from it (except the part of one huge video file that is on the bad sector that seems to have caused the problem).
So right, my 128 card doesn't have that problem, and seems to be corrupted files, as you say, not the drive itself. I do actually do what you talk about - when I do find I have to re-do the 128 sd card in my phone, I run a Windows chkdsk /r before I re-format it, and a chkdsk /f afterward, as a check. The chkdsk /r does take quite a while, yeah .. a few hours.
Cheers
beachfl said:
Yeah I guess it is kinda a small PITA lol. Could just be from me starting and cancelling or moving too many things at once, I don't know.
I've never actually come close to needing all that space to TBH. I could probably do just fine with a 64, but it's nice to know I could record or store hours of HD video, for example, if I need it. I got nearly 30 gigs of music on it. I keep tv and movies on there, too, in case I get caught bored somewhere. Full Nandroid and Titanium backups are on there, as well.
I use a microSD adapter and a small (76 kb) utility for Windows called FAT32Format (Ridgecorp).
---------- Post added at 22:00 ---------- Previous post was at 21:45 ----------
I've had that problem before, too, but not on the 128 I have in my phone now. That is very frustrating. One of my 32 gb cards suddenly went into "read-only" mode as you describe, and nothing I can do will get it useable again. All the files are still readable from it (except the part of one huge video file that is on the bad sector that seems to have caused the problem).
So right, my 128 card doesn't have that problem, and seems to be corrupted files, as you say, not the drive itself. I do actually do what you talk about - when I do find I have to re-do the 128 sd card in my phone, I run a Windows chkdsk /r before I re-format it, and a chkdsk /f afterward, as a check. The chkdsk /r does take quite a while, yeah .. a few hours.
Cheers
Click to expand...
Click to collapse
Great that you're running chkdsk on it. May be caused if you cancel or something happens in the middle of a move. Only other thing I could suggest is to do your format on the phone itself, after you've done everything else on the PC. Don't know if that would make a difference. Shouldn't but I've run across vy experienced folks saying to do that. But... Yeah you've got me hankering to put a 128GB on it...
edit: for read only cards before you trash them I would run them by gparted just to see if re-creating the MBR and partition would change its mind. I have successfully done that with thumb drives but not with cards/adapter/reader.
KrisM22 said:
Great that you're running chkdsk on it..
edit: for read only cards before you trash them I would run them by gparted just to see if re-creating the MBR and partition would change its mind. I have successfully done that with thumb drives but not with cards/adapter/reader.
Click to expand...
Click to collapse
Yeah, thanks for reminding me about fixing the errors, IronTechmonkey. It's kinda an important step I forgot to mention.
I not sure I have the bad card still. I didn't think about GParted, should have. I tried Paragon, among other things, but to no avail.
What speeds are folks getting from a U3 SDE card? I bought what I thought was a 100/60MB/s card and it does about what my old PNY card did - R=40-50, W=34-40MB/s. Is the phone the limiting factor or did I get a bum card?
KrisM22 said:
What speeds are folks getting from a U3 SDE card? I bought what I thought was a 100/60MB/s card and it does about what my old PNY card did - R=40-50, W=34-40MB/s. Is the phone the limiting factor or did I get a bum card?
Click to expand...
Click to collapse
AFAIK the the phone hardware/OS is unlikely to meet the advertised speeds of the cards. Likewise and perhaps more so for USB 2.0 ports and anything using MTP.
I dont know how this compares but for what it is worth: With a Sandisk Utra SDHC (Class 10 - Video, Ultra High Speed Class 1 - whatever that jargon means) touting 80 MB/s read speeds and 40 MB/s* write speeds; the read speeds did consistently approach the rating (getting hot enough to scorch the logo) and the wite speed occasional did. Another factor is the size of files being copied, larger quantities of smaller files taking more time per MB, unless using some dedicated test utility I've never actually done a test of SD r/w speeds on the device. What are you using to measure those?
* In re write speed ratings: Digging into the small print of the specifications may reveal that the manufacturer uses different size cards each for the reed and write speed ratings, effectively padding the write speeds by citing test results from smaller capacity cards.
IronTechmonkey said:
AFAIK the the phone hardware/OS is unlikely to meet the advertised speeds of the cards. Likewise and perhaps more so for USB 2.0 ports and anything using MTP.
I dont know how this compares but for what it is worth: With a Sandisk Utra SDHC (Class 10 - Video, Ultra High Speed Class 1 - whatever that jargon means) touting 80 MB/s read speeds and 40 MB/s* write speeds; the read speeds did consistently approach the rating (getting hot enough to scorch the logo) and the wite speed occasional did. Another factor is the size of files being copied, larger quantities of smaller files taking more time per MB, unless using some dedicated test utility I've never actually done a test of SD r/w speeds on the device. What are you using to measure those?
* In re write speed ratings: Digging into the small print of the specifications may reveal that the manufacture uses different size cards each for the reed and write speed ratings, effectively padding the write speeds by citing test results from smaller capacity cards.
Click to expand...
Click to collapse
Thanks.
Interesting - so you were testing it on windows (?) I did test them on linux and got W=74 on the PNY and 77MBs on the Samsung. That's through a USB3 cardreader.
On the phone I used A1 SD Bench, SD card test, and disk speed test.
Off to try windows...
I was just going to boot up a WinPE and test it there. What prog did you use to test it?
Yes, both of these cards test at about R=81 , W=66.
KrisM22 said:
Thanks.
Interesting - so you were testing it on windows (?) I did test them on linux and got W=74 on the PNY and 77MBs on the Samsung. That's through a USB3 cardreader.
On the phone I used A1 SD Bench, SD card test, and disk speed test.
Off to try windows...
I was just going to boot up a WinPE and test it there. What prog did you use to test it?
Click to expand...
Click to collapse
Yes, Windows 7, which reports file data transfer speeds in the copy process window so I did not use a utility. I've done this enough times in geneal, and a few times specifically with large files and a stopwatch, so I know the speed in the file copy window is relatively accurate (for single large files). The speeds you get on linux seem reasonable. I'll test A1 SD Bench on Osprey when I have a chance. Thanks.
---------- Post added at 11:09 PM ---------- Previous post was at 11:08 PM ----------
KrisM22 said:
Yes, both of these cards test at about R=81 , W=66.
Click to expand...
Click to collapse
Also seemingly reasonable.
My card seem to be working just fine on my Lineage OS. I rebooted by device and now it says it's corrupted. Is there any way out? Will I be able to get my data back?
jay.bhadra1995 said:
My card seem to be working just fine on my Lineage OS. I rebooted by device and now it says it's corrupted. Is there any way out? Will I be able to get my data back?
Click to expand...
Click to collapse
My suggestion would be to copy whatever you can off it and re-format it asap. If you can't read it via phone, try PC.
EDIT: I am assuming you are using it as external. If you are using it as internal, I believe you have lost everything. I know of nothing that can read it. GPARTED can only re-add an MBR and a partition and make it usable again, but all data is lost.
KrisM22 said:
My suggestion would be to copy whatever you can off it and re-format it asap. If you can't read it via phone, try PC.
EDIT: I am assuming you are using it as external. If you are using it as internal, I believe you have lost everything. I know of nothing that can read it. GPARTED can only re-add an MBR and a partition and make it usable again, but all data is lost.
Click to expand...
Click to collapse
Yeah. I copied everything and made a backup. Luckily I use it only as a storage device and not an internal drive for apps. But how do I re-format it? I tried using the format option that my phone gives me but to no avail.
jay.bhadra1995 said:
Yeah. I copied everything and made a backup. Luckily I use it only as a storage device and not an internal drive for apps. But how do I re-format it? I tried using the format option that my phone gives me but to no avail.
Click to expand...
Click to collapse
Do you have a little card reader so you can plug it into your PC?
KrisM22 said:
Do you have a little card reader so you can plug it into your PC?
Click to expand...
Click to collapse
No. Sadly I don't. Is there no other way round to format it?