My i9300 lags extremely bad when copying large files or sometimes fully locks up and I need to reboot. Also, when downloading torrents it also usually ends up lagging at some point and occasional full lock ups I've tried the SDS checker but it says I don't have the 'insane' chip. So basically writing to the storage is causing this. Does it either with the internal or external storage. Other than when copying files or using torrents I never get lag.
Any ideas guys?
Related
Hey everyone-
I don't know if anyone else has experienced this problem before, but I've been trying to transfer a fairly large amount of music to my Vibrant from my pc lately and I keep getting error messages whenever I attempt any transfers, even ones less than maybe a 1.5 gigs. Whenever I attempt to do this the transfers stop about halfway through the process. And I've tried flashing a couple different roms and that hasn't helped, and I've obviously made sure I have enough free space on my internal SD beforehand. Any ideas?
-thanks, bobofosho123
Yea tried 8gb and didn't work
So just try 2gb at a time
Sent from my SGH-T959 using XDA App
There are two reasons for that.
First, some roms have a problem with that, there is a fix in dev section if you are using Froyo
Another problem could be (it did happen to me) that there are certain symbols on songs titles that Android won't recognize creating an error
If it always fails in certain file or folder, try renaming it osr skipping it and see what happens
Thanks for the help guys, I figured it out. I was able to transfer all 11 gigs of my music to my Vib without a hitch, thnx.
Hello, I was hoping someone could help me fix this:
For some time I have had this issue that every time my phone locks up while taking photos or video (I often switch camera apps multiple times when taking photos) my phone reboots and no longer will scan the media card (well, I should be precise and say that a notification briefly pops up that it is scanning but it does not completely scan). It's odd because I have no problem connecting by usb, unmounting and remounting the card (I've tried this over-and-over yet when it is remounted it will still not scan), and I can open a file manager and navigate through my files and even move them but it will not let me open anything for instance music or photos (which made me question if the permissions had been changed but everything is still fully readable/writable). In the past it has fixed it by restoring from a backup (sometimes of which I have had to do several times) but this time I deleted all but one recent backup and it is not fixing the problem this time... I feel I have exhausted my options but would definetely like to avoid a total data wipe (I do have recent Titanium Backups done on all my apps and data but I would also like to avoid having to use the time to restore them and all my settings, etc. back to exactly how I had my phone configured). Also, I would appreciate a solution that does not involve hours and hours of reconfiguration and loading as I am consistently using my camera apps all the time and I am really really getting sick of rebooting, restoring, ect. over and over.
I am running MIUIwiz with ED01, OTB v1.6 and CWM 3.x although I dont think this issue necessarily has anything to do with any of these because I had the same problem on stock froyo anyway.. (if anything might it be a kernel issue?)
Thank you in advance for any input!
gOofeye
any ideas?
Almost sound like the SD card is corrupt but you said you can access it and move items.
If it was me, I would back it up and try a restore.
I understand the Prime has a quad-core processor, along with the fifth primary core. I also know it has 1GB of RAM.
My question is this, whenever I'm downloading multiple torrents, I can barely use any other applications. Everything is slow or stops responding, then just force closes, or reboots.
Is this normal? With this much processing power, I thought the Prime would be able to handle multiple torrents and app usage. Am I wrong?
Mine does the same thing. Its so annoying that I can barely do anything if I'm downloading a torrent. What torrent program are u using? I'm using aDownloader
I'm using aTorrent. I haven't tried any other ones, but now I might just to see if it's the app causing the system to slow down to a halt/crash.
Yeah that's why I asked. If you were using the same app as I was then I would be suspicious of the app but we are using different programs so I doubt its the cause.
Yes prime does have 1gb of memory BUT only like 500-650mb or so is available to use for apps n multitasking. The rest is being used by Android OS itself to run system processes.
well when downloading large files like movies which i bet you are it takes a lot of resources!
Downloading multi torrents your maxing out the read and write if the internal memory causing everything to slow down to a crawl. Has nothing to do with the CPU.
Thanks for the clarification! Does make me feel better that it's not an issue with my Prime. At the end of the day, I'm still happy that I can even download torrents directly to my Prime.
dabbill said:
Downloading multi torrents your maxing out the read and write if the internal memory causing everything to slow down to a crawl. Has nothing to do with the CPU.
Click to expand...
Click to collapse
QFT...if you're able to, save to the SD card rather than internal storage
TF201 | XDA Premium
Are you referring to an external micro sd? I'm only asking because the internal storage on the Prime is named SD Card.
Hi when I download highspeed content from the browser or download torrents to the prime, is unusable, and often stop responding until the download is done.
It dont even need to be faster then 500kbp for this to happen, so it seams to me that it is a problem with the disk speed, dose any one else have this problem, and do any one know why this happens?
The internal memory in the prime, cant possibly be that slow?
There is an I/O issue for the Prime. It appears to be a software issue and not hardware (good news!). So, the best solution to do, is download those files directly to a micro sd or regular SDXC card for the keyboard.
For example, if I download a large torrent using aTorrent to the internal flash memory, my Prime becomes extremely unresponsive. If I download the file to external storage, it will not slow down the system.
Hopefully this will be fixed soon. With the new .13 update, flash memory (there is no disk) performance is up as well.
Hello.
After reading all similar posts, and not finding any solutions I'm turning to XDA developers for help.
I own a brand new (3 month old) T999V Galaxy S3.
The phone is not rooted, and for now, I do not plan on rooting it , in order to keep the warranty.
Approx a month ago , I have noticed, that at times my phone becomes non responsive, and stays non responsive for many hours in a row, significantly heats up, and looses a lot of battery charge.
I have investigated the issue: process /system/bin/sdcard hogs 47-50% of the CPU.
Killing the process simply restarts it again, rebooting the phone does not help.
Galaxy S3 has a "build in" internal SD card, and I'm also using an external one.
I have tried using two different external SD cards, but result was the same.
I have tried running the phone without any external SD card - the result: /system/bin/sdcard at 45% of the CPU !
So it seems that external sd cards are not causing the problem.
I suspected, that a media storage might cause this issue: I had completely reset media storage - to no avail.
Any suggestions, short of "factory reset your device", are more than welcome.
Few illustrations are attached.
Anyone?
Anyone? No one willing to help with the issue?
Solution found
As I figured out that none is volunteering to help, I had resorted to figuring it out myself.
So first I'd like to properly describe the problem:
Every time the galaxy was rebooted, the phone was unresponsive for many hours in a row.
Using an android app called process monitor, I have established that the process that was occupying CPU was named, /system/bin/sdcard .
After reading some Android development documentation I came to a conclusion that the process itself is not to blame: /system/bin/sdcard is a process spanned by SD card access service, and the real culprit could be any application accessing the SD card.
My gut feeling told me that it is somehow related to the notorious media scanner. So I went to Settings>Applications>Running applications, and stopped application called Media. Then I cleared the memory , and suddenly CPU consumption was normal again.
So I found the "what" now I needed to figure "why".
Using android programming documentation again, I have determined that the way media scanner is working is by traversing all directories for all files, and then my bet was that the scanner is getting stuck in one of those directories.
In order to empirically detect which directory was problematic I have used "Storage analyser".
This is a tool showing the size of the folders, and I figured that if a scanner got stuck on a problematic folder, "Storage analyser" will also get stuck on it.
As predicted it got stuck on a following folder:
/Android/data/com.sec.android.allshare .
Using file browser I have determined that the folder contained around 62000 (yes sixty two thousand) files.
As it was impossible to browse within this folder (the file browser was getting stuck when entering this folder, I have simply deleted it.
Further investigation shown that the folder is getting regenerated after reboot, and it contains Samsung Allshare temporary files.
So that's it - removing the folder with a very large number of files has done the trick.
Now my phone works flawlessly, and I'm keeping my eye on the Allshare folder (Samsung shame on you).
So anyone with the "media scanner running slow" problem. Search your drive for a folder with exceedingly large number of files, and get rid of this folder (if you can).
Keywords:
Galaxy S3 high CPU consumption,Android high CPU consumption,Android media scanner slow, Galaxy S3 Slow, Phone is slow on boot.
Amazingly enough, I had this same issue, and I was up to 80k files. Took 3 hours to delete them all. What got me searching was the fact that my tumblr app stop animating gif files. Not sure how, but they were indeed related. Perhaps being rooted had something to do with it. Anyways, I've removed allshare, and there are no signs of temp files growing again.
Removing large folder resolves problem
I too had a similar problem on my Galaxy S3, however, I'm running CyanogenMod 10.1 and not the stock ROM, so my problem was not related to the Allshare app.
I started noticing terrible battery drain (suddenly), I knew something had to be wrong because my battery usually lasts forever, so I started digging. I found that the /system/bin/sdcard process consuming almost all of my battery (battery stats screen under settings).
So next I opened up SSH and connected to my phone's shell. Took a look at top and can see that /system/bin/sdcard was consuming all of my CPU constantly, thus draining my battery amazingly fast. After searching around a bit about this problem, I came across this thread (after looking at pages of similar error reports with no real answers). So I decided to see if I could tell what the sdcard process was doing with files.
So next I ran:
lsof | grep media_rw
Which will show you any files opened by the user media_rw (the user running /system/bin/sdcard)... this led me to the application and directory that was causing the problem. The application stores an image cache and that directory had over 60,000 files in it. Some oddities however, the folder did have a '.nomedia' file in it, which should have told the media scanner to skip it. The files were also not named with an image extension. Also, these files were not on the sdcard at all but the internal phone storage.
I decided to give deleting the files a try, so I did a
rm -f *
in that directory... I got an error message indicating that there were too many arguments... a limitation in the rm binary or the filesystem maybe as well. So I backed up a directory and did a rm -Rf on the directory, which after some time removed the files. Immediately my CPU and battery stabilized and are back to normal.
All of this makes me think that there is really just some limit around 60,000 (65K is a magic number?) to what the filesystem can handle in a single directory (efficiently).
Anyhow thanks for pointing me in the right direction.
Wouldn't putting .nomedia in the root of the folder prevent it from being scanned at all? Rather than deleting folders that you don't know the function of?