Hi,
Does anyone know if it is possible to cook a ROM that is cabable of using your external memory card as extra RAM,(swop memory) for the Hermes 200?
I got the idea from the new Windows Vista operating system using your flash stick as extra swop space/RAM.
Any usefull replies will be appreciated!
Good Question and it has been asked many times before (there are old threads about it). Unfortunately the answer is always NO...
flash to very slow compared to real ram
which is why as pda's starting using flash for stroage
pagepool was made which is really the opposite
from what you ask
as some of the internal ram is used for cache for
the flash
the reasons why it's not possible is
speed
and 2th flash have a limited number of writes
before flash dies kinda like a dvd-rw or cd-rw disk
just more writes then them of cause
but "internal ram" is written to ALOT!
my sd card is 4gb, why was detected only 800 mb or same to the large size of partition my sd card
why about my problem..??
This happens if I use the rom sense, but normal when using cyanogen rom
sorry for my bad english...
I may not know much but it is advised to wipe data/cache before flashing a rom. Also, if you are using xtrSense, I presume you are; since it has App2Sd implemented, I think it only recognizes the sd-extension. I think that's the issue, though, keep this in mind when flash a rom wipe data/cache; to avoid overlapping consistencies of issues.
Hope this helped
Subsequently, I am not very adept in these things, and I am only helping you from my knowledge I perceive.
My phone (sk17i ) did a hard reset with a full wipe of the sd card contents. Do not know how this happened. I was at 10 percent battery, i just pressed the button on top and it just restarted and now the sd card is wiped clean but i do have my google account on the phone. This is stock firmware , stock rom , rooted with blocked bootloader, only modifications are systemui and quickpanel ( colored ) . Other root applications are Xperia Cwm Auto Installer and titanium backup. Is there a log i can look into to see what happened ?
kasmq said:
My phone (sk17i ) did a hard reset with a full wipe of the sd card contents. Do not know how this happened. I was at 10 percent battery, i just pressed the button on top and it just restarted and now the sd card is wiped clean but i do have my google account on the phone. This is stock firmware , stock rom , rooted with blocked bootloader, only modifications are systemui and quickpanel ( colored ) . Other root applications are Xperia Cwm Auto Installer and titanium backup. Is there a log i can look into to see what happened ?
Click to expand...
Click to collapse
I think there isn't any log for that action.
Are you sure you didn't doing something with your SK17i before it got fully wiped..??
By default, there is no background logging process in order to have better performance and battery life.
I did not do anything . i was just checking the battery life. so i opened the phone looked at the 10% of battery that i had left and closed it. Now- any good sd card data restoring software anybody can help me with. I need a good one , and i tried 4 until now and i can't seem to find anything on that sd card.
If the SDcard was formatted, then there is only a very small chance to restore anything.
From Wikipedia
As in file deletion by the operating system, data on a disk are not fully erased during every[17] high-level format. Instead, the area on the disk containing the data is merely marked as available, and retains the old data until it is overwritten. If the disk is formatted with a different file system than the one which previously existed on the partition, some data may be overwritten that wouldn't be if the same file system had been used. However, under some file systems (e.g., NTFS, but not FAT), the file indexes (such as $MFTs under NTFS, inodes under ext2/3, etc.) may not be written to the same exact locations. And if the partition size is increased, even FAT file systems will overwrite more data at the beginning of that new partition.
From the perspective of preventing the recovery of sensitive data through recovery tools, the data must either be completely overwritten (every sector) with random data before the format, or the format program itself must perform this overwriting, as the DOS FORMAT command did with floppy diskettes, filling every data sector with the byte value F6 in hex.
However there are applications and tools, especially used in forensic information technology, that can recover data that has been conventionally erased. In order to avoid the recovery of sensitive data, governmental organization or big companies use information destruction methods like the Gutmann method or the DoD 5220 of the National Industrial Security Program[18]. For average users there are also special applications that can perform complete data destruction by overwriting previous information. Although there are applications that perform multiple writes a single write is generally all that is needed on modern hard disk drives.
Click to expand...
Click to collapse
From my personal experience i restore from my sd card in photocamera (fat32 like here) few 5 years photo even when i using this camera. Its becouse theses jpg files wasnt ovewrited with other. But that program was especialy designed for photo files only.
My point is i thing there is bigger chance just keep away from formating and ofc make restoring to your hard drive
Sent from my ST15i using XDA
So - for photos i used East Imperial Soft Magic Photo Recovery - did a great job, except it changed the names of the photos .
And for the other files i'm using EASUS data recovery wizard -this is the best thing ever. It recognized a ton of files and right now i'm restoring all my files.
Has anyone with a GT-I9100 experienced recurring FAT filesystem corruption problems with the 11.5GB /sdcard (aka "USB storage", a partition of the onboard 16GB eMMC)?
The /sdcard filesystem on my GT-I9100 can go from being fsck_msdos'ing as clean in the morning to corrupt by the afternoon, with no intervening reboots, crashes, power cycles etc. When the problem occurs, it's always in /sdcard/newsrob, which is where NewsRob keeps its article cache (I sync upto 600 articles four times per day). I'm 99.9% sure it's not NewsRob's fault because the author says it's just using normal Java file IO; it's almost certainly just because NewsRob is the most prolific writer to /sdcard. I can read all the eMMC's blocks (using dd if=/dev/block/mmcblk0 ...), so I don't think the eMMC is wearing out. Once fsck_msdos'ed, all files are apparently readable, but some of the most recent NewsRob articles usually have corrupt filenames.
I've seen the problem with Gingerbread 2.3.5 and ICS 4.0.3. To me it looks like one or more of a) a bug in the kernel's FAT code b) a bug in the kernel's MMC code c) a hardware bug (Chainfire's 'Got Brickbug?' says I have the known-bad VYL00M rev. 0x19 - I wonder if this component has more just the MMC_CAP_ERASE bug?) d) a hardware fault on my specific handset.
The problem is easy enough to fix when it occurs; fsck_msdos the filesystem, answer 'N' to all 'extend?' queries and 'Y' to all 'truncate?' queries from fsck_msdos, and remount rw, but it is annoying, especially if I don't notice for a while and my NewsRob articles don't get updated.
cowbutt said:
Has anyone with a GT-I9100 experienced recurring FAT filesystem corruption problems with the 11.5GB /sdcard (aka "USB storage", a partition of the onboard 16GB eMMC)?
The /sdcard filesystem on my GT-I9100 can go from being fsck_msdos'ing as clean in the morning to corrupt by the afternoon, with no intervening reboots, crashes, power cycles etc. When the problem occurs, it's always in /sdcard/newsrob, which is where NewsRob keeps its article cache (I sync upto 600 articles four times per day). I'm 99.9% sure it's not NewsRob's fault because the author says it's just using normal Java file IO; it's almost certainly just because NewsRob is the most prolific writer to /sdcard. I can read all the eMMC's blocks (using dd if=/dev/block/mmcblk0 ...), so I don't think the eMMC is wearing out. Once fsck_msdos'ed, all files are apparently readable, but some of the most recent NewsRob articles usually have corrupt filenames.
I've seen the problem with Gingerbread 2.3.5 and ICS 4.0.3. To me it looks like one or more of a) a bug in the kernel's FAT code b) a bug in the kernel's MMC code c) a hardware bug (Chainfire's 'Got Brickbug?' says I have the known-bad VYL00M rev. 0x19 - I wonder if this component has more just the MMC_CAP_ERASE bug?) d) a hardware fault on my specific handset.
The problem is easy enough to fix when it occurs; fsck_msdos the filesystem, answer 'N' to all 'extend?' queries and 'Y' to all 'truncate?' queries from fsck_msdos, and remount rw, but it is annoying, especially if I don't notice for a while and my NewsRob articles don't get updated.
Click to expand...
Click to collapse
Hi,
I'm getting exactly the same thing, but usually only about once every 6 months I'm running stock 2.3.6, and use NewsRob very regularly.
I correct the problem by mounting my internal SD card via CWM Recovery and then running the DOS command: CHKDSK L: /F
Though, I wish there was a way to solve this issue without using a PC, so you could be repaired when away from home.
I actually think it may be a NewsRob issue. This problem is described in this thread:
http://groups.google.com/group/newsrob/browse_frm/month/2012-08?pli=1
knowthenazz said:
I'm getting exactly the same thing, but usually only about once every 6 months I'm running stock 2.3.6, and use NewsRob very regularly.
I correct the problem by mounting my internal SD card via CWM Recovery and then running the DOS command: CHKDSK L: /F
Though, I wish there was a way to solve this issue without using a PC, so you could be repaired when away from home.
Click to expand...
Click to collapse
There is, providing your device is rooted (I assume it is, since you're using CWM Recovery). See the last paragraph of my previous post; you'll need /system/bin/fsck_msdos. You'll also need the device node, so make note of it now, whilst it's working - if you reboot your device and it won't mount, it'll be harder to figure out. If you catch it just after the error has occurred, then Android will mount it read-only. Naturally, for fsck_msdos to be safe to use the block device it checks must be mounted read-only or be unmounted altogether. A note of warning, however, if your card has relatively large amounts of corruption, then it can be a bit painful to drive in the way I describe above (lots of 'y' and 'return' keystrokes!)
I actually think it may be a NewsRob issue. This problem is described in this thread:
http://groups.google.com/group/newsrob/browse_frm/month/2012-08?pli=1
Click to expand...
Click to collapse
Naw, I'm actually the other person posting in that thread. According to its author NewsRob doesn't do anything but plain Java file IO, so it's a hardware bug, or a bug in the kernel that Samsung are shipping (whether it's failing to mask an issue with the hardware, or the FAT filesystem driver isn't multi-thread safe, or whatever). Unprivileged user mode applications should never be able to cause filesystem corruption, providing the system they're running on isn't powered down or reset whilst they're writing.
cowbutt said:
There is, providing your device is rooted (I assume it is, since you're using CWM Recovery). See the last paragraph of my previous post; you'll need /system/bin/fsck_msdos. You'll also need the device node, so make note of it now, whilst it's working - if you reboot your device and it won't mount, it'll be harder to figure out. If you catch it just after the error has occurred, then Android will mount it read-only. Naturally, for fsck_msdos to be safe to use the block device it checks must be mounted read-only or be unmounted altogether. A note of warning, however, if your card has relatively large amounts of corruption, then it can be a bit painful to drive in the way I describe above (lots of 'y' and 'return' keystrokes!)
Click to expand...
Click to collapse
Thanks for describing how to fix this with the fsck_msdos. I didn't know that you could do this. I'll do a little more research on this and look into this further.
cowbutt said:
Naw, I'm actually the other person posting in that thread. According to its author NewsRob doesn't do anything but plain Java file IO, so it's a hardware bug, or a bug in the kernel that Samsung are shipping (whether it's failing to mask an issue with the hardware, or the FAT filesystem driver isn't multi-thread safe, or whatever). Unprivileged user mode applications should never be able to cause filesystem corruption, providing the system they're running on isn't powered down or reset whilst they're writing.
Click to expand...
Click to collapse
So a hardware or kernel bug huh. Interesting, that I have 4 other devices that run newsrob regularly (sync between once every 15-120 min), all running 2.3x to 4.x.x, and have never run into this issue besides on my SGS2.
knowthenazz said:
Thanks for describing how to fix this with the fsck_msdos. I didn't know that you could do this. I'll do a little more research on this and look into this further.
Click to expand...
Click to collapse
I'm 99.9% sure that the standard startup runs fsck_msdos as Android boots, but if there's anything more than very simple corruption, it needs human input, and there's no user-friendly way of doing this as the handset boots. When fsck_msdos can't fix a filesystem automatically, it stays unmounted, and Android pops up the oh-so-user-friendly "sdcard is damaged, would you like to format it to fix it?" message.
So a hardware or kernel bug huh. Interesting, that I have 4 other devices that run newsrob regularly (sync between once every 15-120 min), all running 2.3x to 4.x.x, and have never run into this issue besides on my SGS2.
Click to expand...
Click to collapse
Same here; I used NewsRob on my old HTC Hero and never had these problems. Of course, it was storing its local article cache to a real micro SD card rather than internal eMMC memory pretending to be an SD card, but that shouldn't make any difference, providing the kernel's MMC driver and the eMMC hardware is functional. Note, of course, that the various Android components that Samsung ship won't necessarily be the same as the Android components shipped by other manufacturers, even if they're nominally the same version of Android.
cowbutt said:
I'm 99.9% sure that the standard startup runs fsck_msdos as Android boots, but if there's anything more than very simple corruption, it needs human input, and there's no user-friendly way of doing this as the handset boots. When fsck_msdos can't fix a filesystem automatically, it stays unmounted, and Android pops up the oh-so-user-friendly "sdcard is damaged, would you like to format it to fix it?" message.
Click to expand...
Click to collapse
Thanks for this info... it helps to understand the process a bit.
cowbutt said:
Same here; I used NewsRob on my old HTC Hero and never had these problems. Of course, it was storing its local article cache to a real micro SD card rather than internal eMMC memory pretending to be an SD card, but that shouldn't make any difference, providing the kernel's MMC driver and the eMMC hardware is functional. Note, of course, that the various Android components that Samsung ship won't necessarily be the same as the Android components shipped by other manufacturers, even if they're nominally the same version of Android.
Click to expand...
Click to collapse
There was some talk that there might be an option in NewsRob to save the feeds to the external SD card, but, it's been complicated by how Android defines the path to the SD card.
I hope that if we can write the feeds to the external SD card instead, it might resolve this issue. At a minimum, if the OS encounters an SD card problem, that it may only make the external SD card read-only, instead of both.
FYI, I've also experienced the same problem when using gReader instead of NewsRob. I'm even more sure it's a Samsung kernel or hardware problem now.
Reluctantly, I've disabled both gReader and NewsRob. They're killer apps for me, but the inconvenience was too great.
I am having a very strange problem that i haven't been able to identify why it happens. The problem is that i am building Android 4.4.2 for an H3 based board, i made a few customizations, including a resize on the partitions, so the system partition is around 2GB, Livesuit does flash the nand perfectly with no issues, but when i use phoenixcard for production, the SD card gets flashed ok with no errors, but when i try to make it to burn the nand, the green bar on the monitor stops in the middle and it never gets to burn the nand, the thing is that i need the phoenix card or another tool that lets me flash in production mode. The files that i modified were sys_partitions.fex, Boardconfig.mk and even the boot-resource.ini but phoenix card keeps doing the same specifically when the image gets to be a little bigger, specially the system partition (though i need that partition with that size).
I would really like some help, thanks in advanced.