Alright, i got my Focus about a week ago. I've been through two storage cards so far, the first being an 8gb sandisk class 2 card, and when i got up to 12Gigabits, everytime i tried to go into the marketplace I would get an "Oops! You've reached the storage capacity of your phone! Please delete some data and try again." So i deleted all my music off the phone and tried again. No luck. If i turn off the phone, take out the battery, and turn it back on I maybe able to install 1 app before the message pops up again.
So.... I figure maybe it was because it was a class 2 card. So now i'm using a Sandisk class 4 16gig card and this time i synched everything (music and pictures, since i can no longer synch office files even though it's a windows phone (which will take some getting used to after having my HTC Pure and being able to put whatever i wanted on ) and got it up to 12Gigs used. Then i started reinstalling my marketplace apps, which worked up until i got to 17Gigs and the error message started again.
Next, i reformatted the phone (again) and decided to try to get whatever i wanted from the marketplace first, since that's the only time i ever seem to have a problem. 6Gigs in, i get the same error message again. I'm about to throw this phone through the window. I have no problem saving pictures, making office documents, or synching music and pictures, just no marketplace functionality.
Samsung says that the phone has shared memory, and that if I try to install more than one app at a time then it will give that error message. No matter how many times i reiterated that i've installed the apps one at a time, waiting until they were installed before doing anything else, he kept saying that was the problem.
Anyone else had this problem or is it just the particular phone that i got? I don't want to go swap it out for another one and go through all this crap again if i can just take it back and swap it for something else since i still have 22 days before the initial 30 day period is up. I figured maybe it was something to do with the marketplace itself, and perhaps it would be fixed in the february update from microsoft, but that would put me past the 30 day return time.
Any suggestions??
Thanks in advance!
EDIT:
Here's the firmware version of the phone i have
OS version : 7.0.7004.0
Firmware revision : 2103.10.10.1
Hardware revision: 3.1.0.7
Chip SOC version : 0.36.2.0
there are issues with user installed microSD. do the cards appear on the approved list here on xda?
the first time it sounds like you filled your card. I realize you say you have 16GB and only filled 12GB the first time. the zune software also shows how much space is reserved for user generated content (pictures,, etc.)
As far as your second go round, I'd say you just got a bum microSD.
The WP7 logo cards should go on sale soon.
dead_on_the_floor said:
there are issues with user installed microSD. do the cards appear on the approved list here on xda?
the first time it sounds like you filled your card. I realize you say you have 16GB and only filled 12GB the first time. the zune software also shows how much space is reserved for user generated content (pictures,, etc.)
As far as your second go round, I'd say you just got a bum microSD.
The WP7 logo cards should go on sale soon.
Click to expand...
Click to collapse
I wouldn't say it was a bum card... I used 6 gigs of a 16G card on the marketplace first, and that's when the error occured, but only in marketplace. Since then, i've added 8 gigs of music and pictures through Zune, which correctly shows the total storage of 22Gigs with 8gigs remaining. The reserved space is set at 1%. The only time the error pops up is with the Marketplace.
I'll try the "new" windows 7 cards, but we'll see. And yes, the SD card i used was listed as working from the list on the forum, that's why i made a thread to see if anyone else was having the issue.
Possible solution:
Wipe out the phone by reformatting the whole thing, then create a new windows ID so Zune and the marketplace think it is a different account?
wildbilll said:
Possible solution:
Wipe out the phone by reformatting the whole thing, then create a new windows ID so Zune and the marketplace think it is a different account?
Click to expand...
Click to collapse
I see that you have a Focus too with a 16G card in it... is it class 2 or 4? I heard the higher class cards don't work as well as the lower class cards due to the way the higher class cards are tinkered with. How much space do you have left on yours and have you not had the message?
I've tried what you suggested too, and after 7 hours wasted of my life from all the formatting and reloading, I'm about to just take the thing back.
After the last format, once i got the error message at 5 gigs full from marketplace, i decided to try and synch some pictures and music which worked flawlessly, and thus far no error message on the marketplace. I'm just paranoid it'll happen again once the card is down to it's last 6 gigs or so.
fetidflesh said:
I see that you have a Focus too with a 16G card in it... is it class 2 or 4? I heard the higher class cards don't work as well as the lower class cards due to the way the higher class cards are tinkered with. How much space do you have left on yours and have you not had the message?
I've tried what you suggested too, and after 7 hours wasted of my life from all the formatting and reloading, I'm about to just take the thing back.
After the last format, once i got the error message at 5 gigs full from marketplace, i decided to try and synch some pictures and music which worked flawlessly, and thus far no error message on the marketplace. I'm just paranoid it'll happen again once the card is down to it's last 6 gigs or so.
Click to expand...
Click to collapse
I think your phone's just borked. When I first got my phone I tried 3 cards, and while they all ended up crapping out anyways, I never ended up with the issue you had.
fetidflesh said:
I see that you have a Focus too with a 16G card in it... is it class 2 or 4? I heard the higher class cards don't work as well as the lower class cards due to the way the higher class cards are tinkered with. How much space do you have left on yours and have you not had the message?
Click to expand...
Click to collapse
It's a class 4 card. Has works flawlessly since it was installed. It came from Microcenter.
I don't have that much on it. I off load pictures and video after transfer with Zune. I have 15 gb free and no messages like you.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
wildbilll said:
It's a class 4 card. Has works flawlessly since it was installed. It came from Microcenter.
I don't have that much on it. I off load pictures and video after transfer with Zune. I have 15 gb free and no messages like you.
Well hopefully you won't. I didn't first get the message til the storage card space was full, with only 6gigs remaining.
Still running fine after the reformat though. But i now have 17.06 gigs free, so we'll see what happens after i put the rest of my music on it. Takes a few hours longer than it did with the drag and drop on my HTC Pure, so i don't know when i'll have time to do it again.
I still might swap it out on the 28th day from DOP, just to be safe. ;P
Click to expand...
Click to collapse
First, ive set the reserved space to the lowest possible. I don't have an sd card installed but I get the same error. Zune PC software says I have 200+ MB free but on the phone under the settings it says I've got 700+ mb Free. I was trying to install assassins creedand it gives me the error. I think its bigger than what the PC says I have free though so idk what to believe.
Update: I went on the Zune software and cleared up enough space larger than the game and it allowed me to install. So there is apparently about 500mb of space that my phone either thinks is available and isn't or it just won't let me use that space.
Sent from my SGH-i917 using Board Express
Related
Hi,
Just noticed this last night. I haven't taken the card out at all in months but it now comes up as not found and I can't load any programs installed on it.
It's a SanDisk 16Gb microSD card and has been fine ever since i got the phone back in November or December. If i take it out and put it back, it does show up for a minute and then drops off again, any ideas?
I can still play songs on it on the Windows Media once it's been taken out and put back in and videos still play etc, so the content of the card seems fine, and with over 12Gb of music and programs, I don't want to reformat it and am not convinced that is even the issue.
Anyone had a similar problem that knows the fix? I have a feeling this is the phone at fault. The only thing I have done differently with the phone of late is to use it as a WiFi router, which does work very well for those that haven't tried it. Just wondering if that has cooked the phone as it does get pretty warm, but that said, all Opera 9 and the other functions still all work ok.
All help appreciated.
Thanks
I am having the same issue with my 8GB SanDisk microSD.
I would use a card reader and try to transfer all the files off and then reformat the card. My card has already corrupted and it is only 2 weeks old.
MandrakeMan said:
Hi,
Just noticed this last night. I haven't taken the card out at all in months but it now comes up as not found and I can't load any programs installed on it.
It's a SanDisk 16Gb microSD card and has been fine ever since i got the phone back in November or December. If i take it out and put it back, it does show up for a minute and then drops off again, any ideas?
I can still play songs on it on the Windows Media once it's been taken out and put back in and videos still play etc, so the content of the card seems fine, and with over 12Gb of music and programs, I don't want to reformat it and am not convinced that is even the issue.
Anyone had a similar problem that knows the fix? I have a feeling this is the phone at fault. The only thing I have done differently with the phone of late is to use it as a WiFi router, which does work very well for those that haven't tried it. Just wondering if that has cooked the phone as it does get pretty warm, but that said, all Opera 9 and the other functions still all work ok.
All help appreciated.
Thanks
Click to expand...
Click to collapse
Hi guys
I got the same problem today...with my T-mobile HD2 used for 3 months.
This is the first time I met this problem and exactly the same with what you describled above. After insert, I got a minute to run program on SD but then it disappeared again. I tried soft reset several times but had the same problem.
P.S. I use a 8GB microSD, not the one in package......
Ok I have a T-Mobile HD2 running on a GTX ROM and the Desire V5 build of Android. If I use the 7.18 Version of the zimage I do not get SOD but when I use 7.25 I get SOD. I just wanted to know what ROMS you guys are using that arent giving the SOD and if anyone has found a temp fix out there. I tried searching but no luck. 7.23 version works perfect with no SOD. Only get issues with 7.25 version.
Thanks
Mike
Bumping this thread.
Lets get this going.
I get SoD on all Android builds. I have tried Chucky, Chucky Droid and now Elegencia. My radio is 210.50.26 TMO-USA.
I have a a class 2 SD card and have found that I get minimal SoD's while plugged in and charging. As soon as I take it off, within a couple minutes it's dead.
My wimo settings are all set to off.
I have tried everything save for a new SD card. I would like to get some info from those who are not getting SoD about what roms and radio versions they're running.
To clarify, does SoD refer to the phone not being able to wake up from sleep mode? If so, I have this problem as well and am looking for a fix.
freakflow said:
To clarify, does SoD refer to the phone not being able to wake up from sleep mode? If so, I have this problem as well and am looking for a fix.
Click to expand...
Click to collapse
Hello,
Yes that is SoD. Some users report not having it at all. Some say they get it with certain zimages.
I have the latest zimage and such and I still experience the dreaded SoD.
There was some talk of it being the Sharpe pannel in the US TMO based Leo, though I am not entirely convinced.
Although not very helpful. Just my experience and observation, could be nothing. I tried all the Roms for my HD2, the Only one I have NOT had a issue with SOD is Darkstone. Not once... the one that was close was "dan" rom. It booted, after the first 2 minutes I had a call, finished the call and it never woke up. Pulled the battery, and figured I would delay the time before the next SOD so I could finish some app downloads. I changed the time out to 2 minutes and shut the lock sound off. After that it woke up everytime. I uninstalled because of other reasons... Like I said, may be nothing but coincidence, but I have noticed a serious delay with the lock sound even on Darkstone. I am happy as could be with it though. Lock sound is off.
Sent from my HTC Desire using XDA App
sicdroid said:
Although not very helpful. Just my experience and observation, could be nothing. I tried all the Roms for my HD2, the Only one I have NOT had a issue with SOD is Darkstone. Not once... the one that was close was "dan" rom. It booted, after the first 2 minutes I had a call, finished the call and it never woke up. Pulled the battery, and figured I would delay the time before the next SOD so I could finish some app downloads. I changed the time out to 2 minutes and shut the lock sound off. After that it woke up everytime. I uninstalled because of other reasons... Like I said, may be nothing but coincidence, but I have noticed a serious delay with the lock sound even on Darkstone. I am happy as could be with it though. Lock sound is off.
Sent from my HTC Desire using XDA App
Click to expand...
Click to collapse
Thanks for the input.
I too am running darkstone. That is the one with which I have the most experience.
Where did you disable the screen locking?
infiniteecho said:
Bumping this thread.
Lets get this going.
I get SoD on all Android builds. I have tried Chucky, Chucky Droid and now Elegencia. My radio is 210.50.26 TMO-USA.
I have a a class 2 SD card and have found that I get minimal SoD's while plugged in and charging. As soon as I take it off, within a couple minutes it's dead.
My wimo settings are all set to off.
I have tried everything save for a new SD card. I would like to get some info from those who are not getting SoD about what roms and radio versions they're running.
Click to expand...
Click to collapse
i am in the same situation as u as well except that i am not using a T-MO HD2..
i'm also using a Class 2 SD card which came with my phone and i have SODs in ALL BUILDS of android... which is irritating to say the least.. i wonder if it is due to the slower Class 2 SD card which is causing the SODs?
can any devs working on android for hd2 share what they feel is the reason behind SODs so we can get an idea of what is the cause of SODs?
Settings, Display, Screen Timeout. I have mine set at 2 minutes, but I mostly just shut the screen down manually when I put the phone down. The lock sound can be disabled under Settings, Sounds.
Sent from my HTC HD2 DROID using XDA App
fi3ry_icy said:
i am in the same situation as u as well except that i am not using a T-MO HD2..
i'm also using a Class 2 SD card which came with my phone and i have SODs in ALL BUILDS of android... which is irritating to say the least.. i wonder if it is due to the slower Class 2 SD card which is causing the SODs?
can any devs working on android for hd2 share what they feel is the reason behind SODs so we can get an idea of what is the cause of SODs?
Click to expand...
Click to collapse
I have seen a lot of people suggest that their faster cards are the reasons they're not getting SoD's but I don't want to spend the 40 dollars only to still get SoD's.
I have also found that it doesn't matter what I set my screen time outs to. It still does it after about 10 seconds.
infiniteecho said:
I have seen a lot of people suggest that their faster cards are the reasons they're not getting SoD's but I don't want to spend the 40 dollars only to still get SoD's.
I have also found that it doesn't matter what I set my screen time outs to. It still does it after about 10 seconds.
Click to expand...
Click to collapse
if the reason for no SOD is speed class of SD card, then all i can do is wait for a NAND flash of android before i come back here.. and i am pretty sure it is the SD card which is causing problems since my phone is very new, and i have not drop it nor damage it in any way..
the only other reasonable reason would be that the hd2s in different places uses slightly different parts in the hardware which works similarly under winmo, but is slightly different in the android environment, slightly like the PSPs... ?
I have T-Mobile usa and I have no sod
I am using
2.10.50.8_2
Pongster hyper Rom v15
Zego cm6rc1
Latest 385mb zimage
The stock class 2 sdcard
Sent from my HTC HD2 using Tapatalk
u can try this. install ChuckyDroidRom with Radio 2.12.50.02_2
Mattleo 1.4 android rom and install SetCpu - you shouldnt get SOd anymore.
Just read about SetCpu and the setup for it.
Some of the fixes that has been posted
1. Reformat your sd card (fat 32). I never tried it but I tried defragmenting the card and it seemed to help for a bit, it came back later though but I was goofing around a lot - I had 4 different builds loaded at one time
2. After you get a SOD and reset/restart back into android, delete the recovered file scraps in your root directory or in LOST.DIR; use the power button to power off or reboot android. When you get back to android again it supposedly fixes it.
I would recommend trying 2 first since it's easier. If it doesn't fix it try #1.
thisguyeh said:
u can try this. install ChuckyDroidRom with Radio 2.12.50.02_2
Mattleo 1.4 android rom and install SetCpu - you shouldnt get SOd anymore.
Just read about SetCpu and the setup for it.
Click to expand...
Click to collapse
buzz killington said:
Some of the fixes that has been posted
1. Reformat your sd card (fat 32). I never tried it but I tried defragmenting the card and it seemed to help for a bit, it came back later though but I was goofing around a lot - I had 4 different builds loaded at one time
2. After you get a SOD and reset/restart back into android, delete the recovered file scraps in your root directory or in LOST.DIR; use the power button to power off or reboot android. When you get back to android again it supposedly fixes it.
I would recommend trying 2 first since it's easier. If it doesn't fix it try #1.
Click to expand...
Click to collapse
i did both..
still got SODs if i leave the phone alone for too long..
its like the phone sleeps, and does not want to wake up any more no matter what i do if i let the phone sleep too long.. im really starting to think that the speed of the sd card is the cause of these SODs.. mine is a class 2 stock 8gb SD card..
One thing that i believe helps, is disabling the sleep if not used to 30 sec, option in winmo. Could just be my imagination, but each time i disabled that, it either got rid of SoD or helped immensely with the frequency.
Susasama said:
One thing that i believe helps, is disabling the sleep if not used to 30 sec, option in winmo. Could just be my imagination, but each time i disabled that, it either got rid of SoD or helped immensely with the frequency.
Click to expand...
Click to collapse
how can i do that if i am using chuckydroid rom for booting android? it is very stripped down and has very little function as a winmo os..
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
in addition, i would like to add that i think i have found a way to overcome the SOD (at least for now for me), hopefully, it will continue to work as i have not have any SODs since i tried what i did..
this is what u need to do:
reformat ur SD card but before u click the format button, change the allocation size from the setting u see, to the largest possible...
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
after u format ur SD card, only copy in the Android boot file of the android of ur choice..
next up, prepare the phone by doing task 29, flashing a 2.08 and above radio.. i am using 2.12.50.02.2 radio from ( http://vbnfiles.com/HD2 Common/Radios/Radio_2_12_50_02_2.rar )
then, install chucky rom lite for android booting ( http://forum.xda-developers.com/showthread.php?t=734238 )
next, start up the phone and do a hard reset without the SD card inside..!
after the hard reset, boot back into winmo and change the date and time settings..
off the phone..
insert the SD card then on the phone..
run android and set up froyo..
hopefully it stops the SODs for good..
so far so good for me, its 2 hrs, and i've not have SODs.. previously the longest time b4 SOD hit me was 35 mins..
----------------------------------------------------------------------------------------------------------------------------------------------------------------
ADDED: added a pic to show what i mean..
fi3ry_icy said:
how can i do that if i am using chuckyrom lite for booting android? it is very stripped down and has very little function as a winmo os..
Click to expand...
Click to collapse
I use chuckyrom too. Just don't let android boot yet, once in winmo..
start > settings > system > power....then once in power its under one of the tabs, can't remember fully, it says something like "Turn off screen if phone is not in use for: [drop box]
I just uncheck it fully.
Also i think with this newest zimg (8/03) the sod came back, just not as prominent as 7/25 or pre 7/23. When i had the 7/23 zimg, i -never- had sod, but here recently with 8/03 it's come back a bit, not too much though.
Susasama said:
I use chuckyrom too. Just don't let android boot yet, once in winmo..
start > settings > system > power....then once in power its under one of the tabs, can't remember fully, it says something like "Turn off screen if phone is not in use for: [drop box]
I just uncheck it fully.
Click to expand...
Click to collapse
alright... will give it a shot later.. still trying all sorts of things to see if a SOD will come out after what i did above which rectified the SOD problem that has plagued me..
about the zImages, i cant comment since previously, no matter which build, winmo ROM, radio and zImages, i had SODs regardless of the combinations..
Mattc 1.4 on top of chunkyDroidRom for about 2 days with no problems no sod.
hspl 2.08
radio 2.12.50.26
On tmous hd2 with class 2 SDcard.
Haven't had any problems so I haven't installed setcpu.
I just switched to Leo_RADIO_2.12.50.02_2 coming from Leo_RADIO_2.10.50.26 and it has stopped my SoD for the time being. Using [shubCRAFT CM6RC2/Froyo/Themed V1.1]
This guide is mostly aimed to the Galaxy S i9000m owners, but it's also good for all other International SGS models as well.
The SGS family of phones were introduced July/August 2010, this give us a little bit over 6 months left of warranty, before your warranty expires, make sure the internal SD is working properly.
Upgrade to stock 2.2 as soon as possible, see if your phone can survive a month on 2.2 under heavy stress usage.
There are many LEGIT ways to test the internal SD without voiding the warranty:
Stock un-rooted methods:
Copying / Deleting large collection of music and/or videos to the internal SD
Install like 300+ apps from Android Market, then massively "Update All" in Android Market <<<<<<<<<< Most efficient test for unrooted
see if you can install any new apps from market, after the 300+
see if you can install any new apps from the External SD, if the internal SD is gone, or dying, it will get stuck on "installing....." forever
Recording 720p Videos with the camera app, until the memory runs out, repeat several times until you feel it's safe <<<<<<<<<< easy and efficient
Root required methods:
Full system Backup/Restore using Titanium Backup or similar Apps <<<<<<<<<< Best Method
mine died trying to copy the appmanager and titanium backup directories from my saved copy on external sd back to sd.. a few minutes after copying they dissappeared.. don't need to be rooted for that.
I'd like to know if anyone had their new/returned SGS with JL2 die that was NOT rooted and is completely stock. Anyone?
I have not had any issues with my SGS i9000M as of yet (knock on wood) and you will see the updates I have done since I purchased it on August 30th, 2011. I had no issues with it on JG9, JH2 (original), JH2 (bootload fix), JK4 (First official FroYo) or JL2 (Newest FroYo update) and I updated to JL2 on December 23rd or 24th so almost 2 weeks ago.
Man... I KNOCK ON WOOD so much hoping I have been one of the lucky ones!!!
can6rxw said:
I'd like to know if anyone had their new/returned SGS with JL2 die that was NOT rooted and is completely stock. Anyone?
Click to expand...
Click to collapse
you can count mine
there is a topic floating about it
can6rxw said:
I'd like to know if anyone had their new/returned SGS with JL2 die that was NOT rooted and is completely stock. Anyone?
Click to expand...
Click to collapse
I've just got mine from the Bell store where I left it on Dec 17. It's the same old from the very first batch phone. They just re-flashed it with JL2. I'm not going to root it for now so I'll try all legit methods to stress the internal storage. I was thinking, what about re-flashing JL2 using a registry hack (setting an older version) with Kies after installing 300+ apps? That should probably push it to the limit.
Install 300+ apps? That's like a day of work, don't you think?
Or you can just flash different roms with odin
AvatarReborn said:
Or you can just flash different roms with odin
Click to expand...
Click to collapse
that's not accurate, flashing the ROM leaves the rest of the internal SD untouched
you are only messing around with the partition and format, that doesn't really kill the internal SD, it just messes it up, it gets corrupted, but it can be fixed
real internal SD death are not fix-able
You are correct, I was simply being a little sarcastic as many believed it was odin messing up the phones.
AvatarReborn said:
You are correct, I was simply being a little sarcastic as many believed it was odin messing up the phones.
Click to expand...
Click to collapse
unfortunate, but true
too many people believes flashing is what kills the internal SD
simplest method which unknowingly sped up the death of my first phone was using the galaxy S to record HD video to the internal card when I was on vacation.
Or, you could just leave it plugged into a charger and leave HD video recording on. My phone died 1 day after recording about 1 hour of HD video (at various times) on the internal SD.
TorontoR said:
simplest method which unknowingly sped up the death of my first phone was using the galaxy S to record HD video to the internal card when I was on vacation.
Or, you could just leave it plugged into a charger and leave HD video recording on. My phone died 1 day after recording about 1 hour of HD video (at various times) on the internal SD.
Click to expand...
Click to collapse
That is also an excellent way to do it
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
and it's totally legit, no rooting required
TorontoR said:
simplest method which unknowingly sped up the death of my first phone was using the galaxy S to record HD video to the internal card when I was on vacation.
Or, you could just leave it plugged into a charger and leave HD video recording on. My phone died 1 day after recording about 1 hour of HD video (at various times) on the internal SD.
Click to expand...
Click to collapse
Sounds like a cool idea. I'm gonna try it.
TorontoR said:
simplest method which unknowingly sped up the death of my first phone was using the galaxy S to record HD video to the internal card when I was on vacation.
Or, you could just leave it plugged into a charger and leave HD video recording on. My phone died 1 day after recording about 1 hour of HD video (at various times) on the internal SD.
Click to expand...
Click to collapse
Thumbs up,
I think this will be much easier method for most.
Not saying this is how you should be torture testing it but alternative to what Original Poster posted.
xxgg said:
Thumbs up,
I think this will be much easier method for most.
Not saying this is how you should be torture testing it but alternative to what Original Poster posted.
Click to expand...
Click to collapse
Any reports of people successfully passing this test...? Maybe if someone could write a simple app that fills and empties the free space of the Internal SD Card...
knightdaemon said:
Any reports of people successfully passing this test...? Maybe if someone could write a simple app that fills and empties the free space of the Internal SD Card...
Click to expand...
Click to collapse
I received my phone yesterday, making a 2 and a half hour commute to pick it up. I am performing this stress test on my phone at the moment. I hope it survives.
What is the indication of having passed this test? Would I have to repeat the hour of video recording how many time? Daily over the course of a month?
I need to read up on the indicators of what constitutes a failure, besides the catastrophic kind. Any offers of advice?
Jan 8 2011 10:00 am Update:
Finished recording 1 hour of video. Repeating to further stress test. Hopefully time will tell quickly if there are any problems or not.
11:23 second hour of video completed. I will try to continue doing this cycle of recording and deleting through out the day, unless one of the experienced posters thinks this is inadvisable.
5:10 pm third hour of video complete. Decided to not delete, but fill the card up as much as possible.
6:11 pm fourth hour of recording complete, this video was recorded without deleting the third hour recording.
6:36 pm Fifth recording never reached an hour. Got a maximum recording size reached message at 20:54.
Also received an additional warning ' not enough memory available', which stopped me from doing anymore video recording. Well restart phone and try continuing.
7:25 pm sixth attempt was stopped at 40:50, along with the memory error. Tried clearing ram to see if it helped, but it did not. Restarting phone.
7:39 pm cannot attempt a 7th video. Despite restarting the phone, the memory write message persists.
Will delete videos to see if this changes things.
9:05 pm one hour video recorded, after deleting previous videos, no memory error.
10:14 pm reached 56:56 before I got the maximum recording size message.
11:14 pm was able to record another video without deleting. Recorded to 57:45.
12:32 pm hmmm . Checked my sd card memory. Only 833 MB left. Deleted all the videos, but the card is still only showing 833 MB of space left.
12:38 restarted phone. almost all the free space is now being recognized (13.02 of 13.03 GB)
Can any one interpret these results?
Jan 11 5:16 pm I got my first force close, using the xda application... maybe I will run some more stress tests.
TorontoR said:
simplest method which unknowingly sped up the death of my first phone was using the galaxy S to record HD video to the internal card when I was on vacation.
Or, you could just leave it plugged into a charger and leave HD video recording on. My phone died 1 day after recording about 1 hour of HD video (at various times) on the internal SD.
Click to expand...
Click to collapse
I tried a few times and my phone says recording failed after a few seconds... is this normal or is it a sign of a dying phone?
How cool (or sad) would it be...
If you are physically at the Samsung Service Centre yourself to pick up the phone and you perform some sdcard benchmark alike and break it on the spot
Or
You'll at a Bell Corp store and kill the sdcard on the spot too, than tell them that you want a new phone, and you break that crap again, and over and over...
go through their entire stock of galaxy to fine that one rare survivor phone.
absolutely crazy.
i hope one of those dualcore phones get released within Q1 fast.
May I suggest a another torture option?
Mount your internal sdcard connected to your PC.
Than run & repeat disk benchmark, do some disk defrag (which isn't recommended for flash type of drives, that is why you do NOT defrag SSD).
Or do a Full format over and over,
May ways to do things that you should do to a flash type of drives. (but should not die from it but shorten the life of it by xxx amount of hours of it's life. You'll probably have upgraded your phone few times more before it really dies)
I have a Verizon Galaxy Note 3, stock ROM, non-rooted. Very pleased with it overall. The KitKat update seemed to somewhat diminish battery life, but it remained acceptable.
In analyzing this further, it seems that "Media" consistently consumes a lot of the battery power, for reasons unclear to me. I just updated to 4.4.4, hoping that this would change, but after a short period of time, it's back up there, as the following screen capture shows:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
According to the Phone's description, this includes:
Download manager
Media Storage
Downloads
I do have a 64gb MicroSD Card, Sandisk, which has never given me any problems. It is about half-full - mostly photos (copies of DSLR images from my Desktop), and several movies.
But why is "Media" using so many CPU cycles? And more importantly, how can I stop this? I would guess my battery life would be significantly improved if I could prevent "Media" from consuming so many CPU cycles.
It has been this way for months, and the screen capture above is quite typical for my phone.
Any insight appreciated.
DLCPhoto said:
I have a Verizon Galaxy Note 3, stock ROM, non-rooted. Very pleased with it overall. The KitKat update seemed to somewhat diminish battery life, but it remained acceptable.
In analyzing this further, it seems that "Media" consistently consumes a lot of the battery power, for reasons unclear to me. I just updated to 4.4.4, hoping that this would change, but after a short period of time, it's back up there, as the following screen capture shows:
According to the Phone's description, this includes:
Download manager
Media Storage
Downloads
I do have a 64gb MicroSD Card, Sandisk, which has never given me any problems. It is about half-full - mostly photos (copies of DSLR images from my Desktop), and several movies.
But why is "Media" using so many CPU cycles? And more importantly, how can I stop this? I would guess my battery life would be significantly improved if I could prevent "Media" from consuming so many CPU cycles.
It has been this way for months, and the screen capture above is quite typical for my phone.
Any insight appreciated.
Click to expand...
Click to collapse
Could be a few things but I would back up your external sd and format it. Then copy what you want back over. If the card has errors or corrupt media then the system sometimes gets stuck scanning or rescanning the card. Is the phone a little warmer then normal up by the back camera?
RomsWell said:
Could be a few things but I would back up your external sd and format it. Then copy what you want back over. If the card has errors or corrupt media then the system sometimes gets stuck scanning or rescanning the card. Is the phone a little warmer then normal up by the back camera?
Click to expand...
Click to collapse
Haven't noticed any warmth or other issues.
I don't know if it's relevant, but it seems that when the phone is not being used, its power consumption is almost zero. It seems that several hours can go by, and there's no change in battery power.
So there doesn't seem to be any ongoing processes chewing up the battery. When it's in use, it does seem to go down more quickly than I think it should.
Does this give any additional clue as to the cause?
I'll probably go ahead and reformat the card - I'm leaning toward going with FAT32 - any thoughts on this vs the exFAT it came with?
Thanks for the reply.
Update:
I copied all MicroSD files to my hard drive, used EaseUS Partition Manager to reformat to FAT32, and recopied back all files. Took a long time to recopy 30gb of data, but went fine, phone saw the card as if nothing had changed.
Unfortunately, Media still came up as the highest consumer of battery after a couple of hours.
I then went into Recovery Mode, wiped the Cache Partition, recharged the phone to reset battery stats, and am trying again.
Media is still the #1 consumer of battery power, although so far by not as high a percentage as before.
This all makes it seem as if there is a misbehaving app:
The Gallery App is built-in by Samsung, although it is not my primary image viewer. I use QuickPic for that.
For Video, I have MX Player installed, along with Amazon Instant Video.
Is there an App that will show which specific Apps are the source of what the phone is now simply showing as "Media"??
Is it possible that an App I turned off could cause this behavior? I don't see any obvious candidates in my list: Audible, CallerNameID, Verizon Cloud, Google Play Newsstand, Google+, Group Play, Hangouts, NFL Mobile, S Health, Samsung Link, Samsung Push Service, Samsung WatchON, Slacker, Softcard, Support & Protection, Verizon VoiceMail (I have mine shunted to Google Voicemail).
Any suggestions appreciated. It seems that I could be getting outstanding battery life, rather than just acceptable, if I can get rid of whatever is driving Media to consumer power!
Hopefully, a "Fiinal" update:
The problem never really went away.
I even tried switching to a Samsung (vs Sandisk) MicroSD card, but there was no significant impact.
I recently did the OTA update to Lollipop 5.0, and lo and behold, during my first full day of use, Media doesn't even show up on the list of Apps using the battery.
And I can now write to the SD Card with ES Explorer, which I really missed.
So it was a Kit-Kat thing, for some reason, probably related to the large number of files on my card.
DLCPhoto said:
Hopefully, a "Fiinal" update:
The problem never really went away.
I even tried switching to a Samsung (vs Sandisk) MicroSD card, but there was no significant impact.
I recently did the OTA update to Lollipop 5.0, and lo and behold, during my first full day of use, Media doesn't even show up on the list of Apps using the battery.
And I can now write to the SD Card with ES Explorer, which I really missed.
So it was a Kit-Kat thing, for some reason, probably related to the large number of files on my card.
Click to expand...
Click to collapse
Thanks for making this thread! This is a problem that's been plaguing my phone for more than a year. I did everything you did and nothing ever fixed it, plus the slot would get hot. I've been using the same card in a different brand of phone and outside of the first scan, media has never been on my battery use list. Glad to hear that an update to Lollipop will fix the issue on my Note 3.
My Fire HD8 is dying when I'm not using it. For example, at 80% charge last night I went to sleep with the smart cover closed on the Fire and it was at 40% by morning (~5%/hr). For a few weeks now it's been dying, from full charge, within a day, without me using it. It also freezes a lot upon waking so I have to power cycle it before it's useable, which has made diagnosing what kills the battery somewhat hard.
However, I installed GSam Battery Monitor and what I've learned is that even when the smart cover is closed, most of the battery drain is due to the device being "held awake." And the "App sucker" shows Prime Photos as having used most of the power. For example, 18% out of 44% since my last full charge. The thing is I don't use Prime Photos, at all, for anything. I have no photos on the device. I've maybe used the camera once or twice. So it's not from active usage.
But Prime Photos can't be removed. I can't disable it. And I can't seem to figure out a way to stop the power drain. I've power-cycled dozens of times (not to mention the nearly daily 100% battery drain). I've cleared the cache and forced stop on Prime Photos a few times. And I'm at a total loss now as I can't seem to find anyone who is experiencing the same or even a similar issue with a Google search.
I'm current only OS 5.6. And I have added Google Play Store apps via APKs. The only option I see is a factory reset although I'd rather not do that if possible. Anyone have any suggestions about what to try? I know there's some work-arounds to remove pre-installed apps (although maybe more challenging on the latest OS). Is that the best route? Is there a better option? Or could Prime Photos be a red herring?
A few more updates:
I noticed that Prime Video was also sometime showing high usage (as had Prime Photos). So I decided maybe it was an ad locking up and holding the device awake. Based on tips I read here I contacted Amazon support to mention maybe that the ads were causing the problem and they immediately removed the ads for me. So that was nice, and my Fire immediately seemed more responsive and faster to wake.
BUT - the problem is not resolved. My Fire continues to freeze (often) with an unresponsive black screen (it's backlit, so it's on, it's just displaying black). The battery died 50% overnight while I slept. So I'm still basically facing the same problem.
Possibly unrelated is that Kindle Books seems to be re-setting to default settings often (shows the intro/new features screen as if the app was just installed/updated). This might be completely unrelated. Or maybe it's all of the Amazon apps that are causing issues.
Fire HD 8 battery drain (Fire OS 5.6.0.0)
I am also experiencing abnormal battery drain on my Fire HD 8 running Fire OS 5.6.0.0. I bought one on Thanksgiving and pretty soon after setting it up added and SD card and installed the Google Play Store and associated APKs. Shortly thereafter it started acting up - rapid battery drain, sluggishness, and difficulty powering off/on. I contacted Amazon and they processed an exchange. Since receiving the new one, I've done some reading and slowly experimented. First I set it up without adding Google Play Store or an SD card and it behaved as expected - relatively smooth performance and minimal battery drain overnight. After 24 hours I installed the SD card and immediately the rapid battery drain and rebooting difficulty returned. And, I periodically get an error message telling me the SD card has been ejected (which it has not). I believe there is a software issue with the SD card that is the culprit and is preventing the Fire tablet from sleeping - therefore the drain and performance issues. Anybody out there concur?
DyslexicPBJ said:
I am also experiencing abnormal battery drain on my Fire HD 8 running Fire OS 5.6.0.0. I bought one on Thanksgiving and pretty soon after setting it up added and SD card and installed the Google Play Store and associated APKs. Shortly thereafter it started acting up - rapid battery drain, sluggishness, and difficulty powering off/on. I contacted Amazon and they processed an exchange. Since receiving the new one, I've done some reading and slowly experimented. First I set it up without adding Google Play Store or an SD card and it behaved as expected - relatively smooth performance and minimal battery drain overnight. After 24 hours I installed the SD card and immediately the rapid battery drain and rebooting difficulty returned. And, I periodically get an error message telling me the SD card has been ejected (which it has not). I believe there is a software issue with the SD card that is the culprit and is preventing the Fire tablet from sleeping - therefore the drain and performance issues. Anybody out there concur?
Click to expand...
Click to collapse
I am having the exact same symptoms with my Fire HD 8 running Fire OS 5.6.0.0. I got it in early October and it ran fine until the recent update. It runs great with no SD card installed. As soon as I mount my 32 GB Samsung Evo card, I get battery drain while sleeping and erroneous SD card eject messages. I also get intermittent sluggish performance. I have nothing on the card, just mounting it causes problems. I have tried erasing and remounting but still problems. As soon as I remove the card, all is well. I tried an old 2 GB Samsung card I had lying around. It worked fine with that card. I too have installed the Google Play Store and associated APKs but I don't think that is part of the issue. Perhaps there is an issue with larger SD cards.
Sometimes hot mounting sdcard works. I usually start device without it and then power off and insert card in. Then at first boot with SD card I usually format it in device to avoid those problems so maybe there is an issue. Play store it self is a battery hog in my opinion. I would deactivate automatic app update in play store settings as this can conflict in with apps from Amazon app store.
Also reboot now and then is a good option.
I had my fire HD 8 for few weeks it with latest update and didn't experienced any of those issues yet.
maly82 said:
Sometimes hot mounting sdcard works. I usually start device without it and then power off and insert card in. Then at first boot with SD card I usually format it in device to avoid those problems so maybe there is an issue. Play store it self is a battery hog in my opinion. I would deactivate automatic app update in play store settings as this can conflict in with apps from Amazon app store.
Also reboot now and then is a good option.
I had my fire HD 8 for few weeks it with latest update and didn't experienced any of those issues yet.
Click to expand...
Click to collapse
I have turned off automatic updates in both the play store and the Amazon app store. The issue appears whenever I mount the SD card. I have tried hot mounting, formatting in the device, external formatting, etc. It seems to be related to certain type(s) of cards. It does not occur with my old small 2 GB card but occurs every time with my new 32 GB card.
Where did you get your SD card. Some sources sell them dead cheap but they might be capacity hacked cards. I had one of those back in a day saying that it was a 128GB. But it was really 4GB after I used low formatting- which takes some time. Try repartition your SD card. See if that issue still appears. Usually there is a bit space left unpartitioned when they are new. I would try that and see if that works.
Also Amazon might be to blame as if you choose to use it to store all your content on sdcard it usually takes up some space with on deck content without you knowing it.
Also check in file manager on your SD card if you have folder called Android. Try to delete it and see if it asks you for special permission to access sdcard. Some apps require that and maybe this is a cause.
Thanks for your suggestions. I bought my card through Amazon Prime. I borrowed a neighbor's 32 GB SandDisk HC I card. It ran fine with no memory drain or other issues. I deleted the partition on my Samsung drive and did a low level reformat. I mounted on my Fire HD 8 and memory drain occurred again. Battery level went down 7% in one hour while sleeping. It is definitely specific card related. If you are still reading this, would DyslexicPBJ post the make and model of your card? Thanks.
I took a 64 GB SanDisk card out of a Dell Windows Tablet I have. It works just fine in the HD 8. After 2 hours no memory drain. I don't know if I have a bad card or if the HD 8 just does not like Samsung 32 GB Evo cards. I put the Samsung card into my Dell and it appears to be working fine.
DyslexicPBJ said:
I periodically get an error message telling me the SD card has been ejected (which it has not). I believe there is a software issue with the SD card that is the culprit and is preventing the Fire tablet from sleeping - therefore the drain and performance issues. Anybody out there concur?
Click to expand...
Click to collapse
Very interesting. I just got the SD card error for the first time yesterday. At the time I wrote this post I would not have connected the issues to the SD card. But now I wonder. I have this card in my Fire: https://www.amazon.com/gp/product/B06XWZWYVP/ref=oh_aui_search_detailpage?ie=UTF8&psc=1
DrInsomniac said:
Very interesting. I just got the SD card error for the first time yesterday. At the time I wrote this post I would not have connected the issues to the SD card. But now I wonder. I have this card in my Fire: https://www.amazon.com/gp/product/B06XWZWYVP/ref=oh_aui_search_detailpage?ie=UTF8&psc=1
Click to expand...
Click to collapse
This is mine. https://www.amazon.com/Samsung-Micr...2768405&sr=1-3&keywords=samsung+32+gb+sd+card
Not the same, but similar. I have had no problem with 3 different SanDisk cards. Maybe the Fires just don' t like Samsung.
Well, it's confirmed. I unmounted my SD card and the problem is immediately fixed (I forgot how long the battery lasts. Over a day and a half of occasional usage and it's only dropped 20% and hasn't frozen a single time).
Is it possible to submit this as a bug report to Amazon? My girlfriend has the same SD card and is having the exact same problems, which further confirms it's the SD card at fault since my tablet has ads disabled and Google Play services, while hers still has ads and has never had Google Play installed.
I went ahead and bought the 32GB (more than enough size, for me, I think) that they recommend at http://amazon.com/firetabletstorage. Feels a little like they've duped me since I've now spent about as much on SD cards as I did on the tablet itself. But there's simply not enough storage on the device to go without any sort of backup memory and this card doesn't seem to be causing problems for people.
I replaced my Samsung 64 GB card with a SanDisk 64 GB card and all is well. It is the card that Amazon recommends. Weird that the Fire does not seem to like the Samsung cards.
mreasier said:
I replaced my Samsung 64 GB card with a SanDisk 64 GB card and all is well. It is the card that Amazon recommends. Weird that the Fire does not seem to like the Samsung cards.
Click to expand...
Click to collapse
Just to chime in, I've had a similar issue with the battery draining super fast as soon as I installed the SD Card in the tablet. I also had the tablet running very hot and draining the battery down to 2% in my bad, which was kind of dangerous. I also randomly had messages telling me that the card was not properly removed, or simply the storage settings freezing and not recognizing the card.
My SD card is an UHS-3 Samsung Evo 64GB.
I installed BetterBatteryStats (https://forum.xda-developers.com/showthread.php?t=1179809 + https://forum.xda-developers.com/showpost.php?p=67819528&postcount=4 to grant permission through ADB) on the tablet to check what was causing the battery drain.
This is what it looks like with the Samsung SD card (did not matter if it was unmounted or not, as long as the card was physically seated in the slot, it would cause drain):
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
The mmc1_detect process keeps the tablet awake while trying to interact with the SD card.
This is what it looks like without an SD card:
This is what it looks like with an UHS-1 SanDisk 64GB:
There was definitely some weird interaction between the Fire tablet and the Samsung Evo SD card.
Hi, all.
I have the same issue with Samsung 64 Gb Pro and Fire OS 5.6.0
For now decided to use Fire HD without SD card. Unfortunately...
if someone find solution - please share it.
Thanks.
likimoki said:
Hi, all.
I have the same issue with Samsung 64 Gb Pro and Fire OS 5.6.0
For now decided to use Fire HD without SD card. Unfortunately...
if someone find solution - please share it.
Thanks.
Click to expand...
Click to collapse
Unfortunately, the only solution I know of is to find another use for your Samsung card and buy one of the recommended SanDisk cards for you Fire.
mreasier said:
Unfortunately, the only solution I know of is to find another use for your Samsung card and buy one of the recommended SanDisk cards for you Fire.
Click to expand...
Click to collapse
I can confirm that this issues fixed in 5.6.0.1 at Jan 23th.
My HD 10 has recently begun doing the same thing. The only connection I can see to the posts above is that I recently transferred a few dozen ebooks from my computer to the 64gb Sandisk card via the notebook after the Humble Bundle app kept crashing. I'm now charging with the SD card removed and will remove Humble Bundle when I'm up to a full charge to see if there's any difference.
I came to inquire as to this exact issue. I have a 128 Gig Samsung EVO which when installed drains my battery from 100% to 20% in under 36 hours. Without the memory card installed, it drops about 4% every 12 hours instead. Guess I'll be buying a SanDisk 128 Gig instead. Thanks for the advice from all who posted about this already.