Related
I'm having some trouble lately, maybe the past week? I keep seeing low memory, and I'll go in and delete some apps and it'll go away, and keeps coming back, I've cleared all my caches and such and am still hovering around 15-16MB of memory.. I rooted my phone about a month ago and flashed Fresh 2.4.0 onto it, and have really liked it versus stock! But, this low memory thing has me a little worried.. I've tried searching and haven't found much, anybody have any advice for me?
I've found that after wiping data and reinstalling my apps, I gained about 50 megs. Even with all the same apps and data from titanium restore... Just a lot of trash gets built up over time (it had been months since I had wiped data)
Sent from my HERO200 using XDA App
Andrew486 said:
I'm having some trouble lately, maybe the past week? I keep seeing low memory, and I'll go in and delete some apps and it'll go away, and keeps coming back, I've cleared all my caches and such and am still hovering around 15-16MB of memory.. I rooted my phone about a month ago and flashed Fresh 2.4.0 onto it, and have really liked it versus stock! But, this low memory thing has me a little worried.. I've tried searching and haven't found much, anybody have any advice for me?
Click to expand...
Click to collapse
Use firerat's internal partition mod...
http://forum.xda-developers.com/showthread.php?t=754805
It repartitions the internal space. When youre donr you have 2-300 mb of space for apps and cache. Very simple to do
you have a few choices here
1. switch to an odex'd build these have more internal space because of how odexing works
2. modify your partition like PMDColeslaw suggested
3. delete some of the apps your not using, i know on my phone i can name atleast 6 apps i have installed that i use barely at best
Andrew486 said:
I'm having some trouble lately, maybe the past week? I keep seeing low memory, and I'll go in and delete some apps and it'll go away, and keeps coming back, I've cleared all my caches and such and am still hovering around 15-16MB of memory.. I rooted my phone about a month ago and flashed Fresh 2.4.0 onto it, and have really liked it versus stock! But, this low memory thing has me a little worried.. I've tried searching and haven't found much, anybody have any advice for me?
Click to expand...
Click to collapse
If you switch to cm, you'll gain about 50 mb of storage immediately
Sent from my hero running froyo... take that Sprint!
I would like to know how many of you had successfully updated their SGS (Samsung Galaxy S) to Froyo. I think this will help us understand the failure rates so people who do not want to risk bricking their phone.
1) Updated with no problems
2) Updated with problems
3) Tried to update and having problems
4) Did not update at all
If you are talking about roms.. Well most are a 1. I habent heard of an official froyo update. And.if.you by chance do.brick it, there are ways to unbrick it pretty easily.
Sent from my SAMSUNG-SGH-I897 using XDA App
I have the Bell Vibrant which is the I9000M.
I thought that Bell released an official update for their new Froyo. Check it out here
mobilesyrup.com/2010/12/08/bell-samsung-galaxy-s-vibrant-upgrade-to-os-2-2-froyo-coming-december-10th/
Did update my Bell Samsung Galaxy S GT-I9000M with Bell release Froyo available using Kies and all seemed to be running smoothly until I had issues connecting my bluetooth and trying the voicedialing features that did not work in my case and after got Force close on every apps. Did a shutdown and got the device in a loop at boot up.
Will try tonight to reload the device with 2.1 and see from there to retry 2.2.
Finger cross !
I upgraded with no problems but I did do a factory reset as things started to get a bit slow and from what Ive read it is a good idea to do a reset to get rid of any residual 2.1 stuff on the device. Since then the update has been working well for me...
KNOCK ON WOOD!!!
I have 2 SGS phones so you'll just have to add another vote to the "successful upgrade" option in addition to the one I was able to cast
I've flashed the following 2.2's without any problems so far:
- unofficial JK3 (Canada) via ODIN
- official JK4 (Canada) via Kies
- straight JPU via ODIN
- JPU Doc RomMOD v2 via update.zip recovery
No problems with flashing.
And yes, clearing data & cache is helpful (mandatory?). Backups are good!
there is NO problem upgrading.
the Internal SD failure comes AFTER you have SUCCESSFULLY upgraded the phone, a few hours to a few days later
ssj2miguelx said:
I would like to know how many of you had successfully updated their SGS (Samsung Galaxy S) to Froyo. I think this will help us understand the failure rates so people who do not want to risk bricking their phone.
1) Updated with no problems
2) Updated with problems
3) Tried to update and having problems
4) Did not update at all
Click to expand...
Click to collapse
AllGamer said:
there is NO problem upgrading.
the Internal SD failure comes AFTER you have SUCCESSFULLY upgraded the phone, a few hours to a few days later
Click to expand...
Click to collapse
Cool. That makes this type of poll misleading then because someone reporting success today may have issues tomorrow (we can't change our vote correct?).
That's right. I saw your post about your phone going bust. Sorry to hear that.
I just can't get Kies to work -- it just says "connecting to device" and it hangs
Also can't install MPT USB drivers -- always fails. I installed the correct x64 bit Windows 7 drivers and everything.
Ughh
Wow. I didn't think people would have problems after the update. Man, I really should wait until we all know that its okay to update. I am new when it comes to the SGS so if I fail at it, I don't want to start crying. This is such a nice phone....so if it works, why break it?
ssj2miguelx said:
Wow. I didn't think people would have problems after the update. Man, I really should wait until we all know that its okay to update. I am new when it comes to the SGS so if I fail at it, I don't want to start crying. This is such a nice phone....so if it works, why break it?
Click to expand...
Click to collapse
Same - I am hessitant now to upgrade.
I had one of the original phones, it sucked, no GPS, etc. and it died on me.
I got a new phone, for free, my buddy works at bell, GPS works fine, and this one I think had the internal card failure b/c one day it just went black - reboot and the bottom lights light up but it doesn't boot in.
I did a recovery mode -> hard reset seemed to fix it -- tho i lost all my apps and contacts etc.
Now I haven't rooted or lag fixed, but I REALLY want froyo.
But what's the point ? I already had to do a reset b/c of internal card failures in the past, that means im almost guaranteed to lose this one if i upgrade,...
Funkadelick said:
Same - I am hessitant now to upgrade.
I had one of the original phones, it sucked, no GPS, etc. and it died on me.
I got a new phone, for free, my buddy works at bell, GPS works fine, and this one I think had the internal card failure b/c one day it just went black - reboot and the bottom lights light up but it doesn't boot in.
I did a recovery mode -> hard reset seemed to fix it -- tho i lost all my apps and contacts etc.
Now I haven't rooted or lag fixed, but I REALLY want froyo.
But what's the point ? I already had to do a reset b/c of internal card failures in the past, that means im almost guaranteed to lose this one if i upgrade,...
Click to expand...
Click to collapse
If your card is gonna die its gonna die no matter if you upgrade or not....Flashing just seems to speed up the corruption.
Thats a good question. People seem to be having big issues with this new Froyo update here, http://forum.xda-developers.com/showthread.php?t=867157. I really hope Bell gets a fix for this new "firmware Froyo 2.2" that they just released.
If the Nexus S is the so similar to the SGS I9000M why dont we have Gingerbread (2.3) yet?
Again people. It's not the froyo update that's a problem it's bad internal SDcards. These phones were dying before froyo came out and without ever flashing anything.
If they're gunna die, they're gunna die. Flashing just helps to speed up the failures. SO flash away and hope it blows before your warranty is up.
Funkadelick said:
Same - I am hessitant now to upgrade.
I had one of the original phones, it sucked, no GPS, etc. and it died on me.
I got a new phone, for free, my buddy works at bell, GPS works fine, and this one I think had the internal card failure b/c one day it just went black - reboot and the bottom lights light up but it doesn't boot in.
I did a recovery mode -> hard reset seemed to fix it -- tho i lost all my apps and contacts etc.
Now I haven't rooted or lag fixed, but I REALLY want froyo.
But what's the point ? I already had to do a reset b/c of internal card failures in the past, that means im almost guaranteed to lose this one if i upgrade,...
Click to expand...
Click to collapse
If I was you I'd flash the crap outta your phone. If your black screen was due to a weak internal SD then it's gunna go. So flash it and hope it goes so you can get a new(repaired) one. Of course the wait time is a bit long right now for repairs. And there's no guarantee that the newly repaired one won't blow.
Damn this phone....
And yes, clearing data & cache is helpful (mandatory?). Backups are good!
Click to expand...
Click to collapse
How to do it?
It will delete also my files (photos, music....) on the internal memory?
Regards
Sent from my GT-I9000 using Tapatalk
AllGamer said:
there is NO problem upgrading.
the Internal SD failure comes AFTER you have SUCCESSFULLY upgraded the phone, a few hours to a few days later
Click to expand...
Click to collapse
yeah!
my phone upgrade went well..but i have occasional force closure on apps. Then one day it just hang using Msn Talk Pro and I had to pull the battery out to reboot and it never came back on - stuck after the bootup S logo. grrrr..
how long does the warranty repair usually takes?
Anyone in Vancouver Canada that are non Bell subscriber have any problem bringing it in? Which store do you guys go to? I will try the same store for hassle free repair job. Thanks
Videonut said:
Again people. It's not the froyo update that's a problem it's bad internal SDcards. These phones were dying before froyo came out and without ever flashing anything.
If they're gunna die, they're gunna die. Flashing just helps to speed up the failures. SO flash away and hope it blows before your warranty is up.
Click to expand...
Click to collapse
Is there a chance that my phone has a bad internal SDcard?
betaboy00 said:
yeah!
my phone upgrade went well..but i have occasional force closure on apps. Then one day it just hang using Msn Talk Pro and I had to pull the battery out to reboot and it never came back on - stuck after the bootup S logo. grrrr..
how long does the warranty repair usually takes?
Anyone in Vancouver Canada that are non Bell subscriber have any problem bringing it in? Which store do you guys go to? I will try the same store for hassle free repair job. Thanks
Click to expand...
Click to collapse
Took mine into the bell store at guilford mall, originally purchased at wireless wave.Unlocked and being used on the fido network. No issue at all, the guy took down my cell number as a way to track its progress.
ssj2miguelx said:
Is there a chance that my phone has a bad internal SDcard?
Click to expand...
Click to collapse
There's no way to know for sure. Some ppl seem to have a bunch of force closes bfore it dies and others just turn it on and it's dead.
Hi all I'm having this problem that's doing my head in. I went to use OCLF but was informed that I didn't have enough space in my phones internal memory. On checking it, apparently I only had 800 mb free, so I went and deleted all my large apps, and left a whole bunch of small apps about 4-5 mb in size (in total there wouldnt have been more than 30 mb combined). This didn cut it as now I only had 1100 mb free and I needed 1.5 gb to run the fix. After reading a few forums my understanding was that I had to do a factory reset to free up the rest, but in doing so I would lose my contacts, messages etc. So I used titanium to back some important things up then did the reset. On rebooting my phone I was shocked to see that my free available memory was still around 1.1 gb, and the reset was in vain as I had lost everything and my backups didn't work. Wats worse is the reset left some apps behind but none of them work! I ruined my phone and gave myself a big headache for nothing! Please somebody help! How can I free up some bloody internal memory so I can run OCLF and wat can I do about my failed titanium and astro backups?? Any help would be greatly appreciated
sf1nkxxx said:
Hi all I'm having this problem that's doing my head in. I went to use OCLF but was informed that I didn't have enough space in my phones internal memory. On checking it, apparently I only had 800 mb free, so I went and deleted all my large apps, and left a whole bunch of small apps about 4-5 mb in size (in total there wouldnt have been more than 30 mb combined). This didn cut it as now I only had 1100 mb free and I needed 1.5 gb to run the fix. After reading a few forums my understanding was that I had to do a factory reset to free up the rest, but in doing so I would lose my contacts, messages etc. So I used titanium to back some important things up then did the reset. On rebooting my phone I was shocked to see that my free available memory was still around 1.1 gb, and the reset was in vain as I had lost everything and my backups didn't work. Wats worse is the reset left some apps behind but none of them work! I ruined my phone and gave myself a big headache for nothing! Please somebody help! How can I free up some bloody internal memory so I can run OCLF and wat can I do about my failed titanium and astro backups?? Any help would be greatly appreciated
Click to expand...
Click to collapse
OCLF?
Isn't Voodoo Lagfix is a better solution?
I'm assuming you are still on the Stock 2.2 Firmware, right?
41LY45 said:
OCLF?
Isn't Voodoo Lagfix is a better solution?
I'm assuming you are still on the Stock 2.2 Firmware, right?
Click to expand...
Click to collapse
Yeah, OCLF is so deprecated, any thread that relates to it on these forums should be eradicated.
But isnt OCLF supposed to have a much faster fix than voodoo?? If not, then i'll be damned. I bet knowing my luck voodoo wouldnt require as much internal space. All this headache seriously for nothing - everything I intended to be removed off the internal storage is still their only corrupt and doesnt run, and everything i intended to keep through backup is lost through backups that don't work! ARGH!
Back to the matter though, how can I clear my internal storage if factory resetting isn't clearing up the 2g internal partition??
AND does anyone have any experiences with voodoo being much faster, efficient to use etc. than OCLF?? Thanks in advance
OCLF used black magic and trickery to get high benchmark scores but is not faster/smoother/better than ext4 voodoo.
Where have you been all these months and please don't tell us you are still on 2.1 or something.
haha ive been extremely busy with work over the last few months and haven had any time to play around with my phone or even come back on here (i forgot my old username and password cos i didnt come on in so long). that was until last week when i upgraded to 2.2 (and am hearing rumours of 2.3 coming officially coming soon?), rooted my phone and tried this OCLF rubbish all in the same night.
hard reset ur phone, then apply the oclf, not just the factory data reset..heres the dialer for hard reset
*2767*3855#
Sent from my SAMSUNG-SGH-I897 using XDA App
ok so i tried a new approach and im having more problems. sorry i guess its my inexperience. first problem was when i tried the hard reset by dialing *2767*3855#. The phone went through the process of 'resetting' the phone only when it rebooted, all the damaged apps which id been seeking to remove were still there (since initially trying the 'soft' reset option under privacy in settings, anytime i try to open one of the apps left behind the phone will vibrate twice then force close the app). the second problem was when i tried to flash voodoo using the recovery mode. i can enter the 3 button recovery mode only i cant move up or down the menu using the volume keys! fml
you need to just put it in download mode and flash back to stock.
Pirateghost said:
you need to just put it in download mode and flash back to stock.
Click to expand...
Click to collapse
This, use odin one click to flash back to JF6 and start over before it gets worse.
Sent from my GT-I9000 using XDA App
I finally updated to the official AT&T Froyo 2.2 probably about a month ago. Everything was working great. I wanted to root/enable sideloading apps/unlock. I used SuperOneClick 2.1.1. The root worked fine (at least I think so). I was not able to enable sideloading apps so I read online how to change the value of sideloading apps from 0 to 1. I also unlocked the phone using the Galaxy S unlock app from the the Market.
Almost right after the SD Scan would take a long time and then I would get a red SD card symbol saying "Low on Space - Database storage is getting low". I tried clearing cache's to fix the problem. It didn't fix anything. Soon thereafter I started getting "Message Memory Full - Incoming messages rejected due to full...." I cleared phone log/txt messages but it hasn't fixed anything. I looked at my internal and external SD card. My external card is 3.68 total with 17MB available. My internal has 12.67GB available.
Today all of a sudden if I try to look at my missed call I get "samsung captivate the application phone (process com.sec.android.app.dialertab) has stopped unexpectedly. Please try again". I get similar messages trying to open Gmail. I haven't gotten it on any other apps yet as far as I know. It vibrates like crazy when the apps crash.
Can anyone help me with the problem? It's making my phone useless right now and my battery is dying much quicker than before. Thanks!
-T
My vote is to go with a custom ROM. It will solve all of these problems. Cognition is the most similar to stock and is quite easy to flash. As for the problems you are having, I don't know what to tell you.
Try Cognition 4.5.3. You won't be disappointed.
Thanks for the quick replay Jack especially on a Fri night. What exactly do I do? Is it difficult to do?
Well, not busy tonight. Watching pre-season football.
Flashing a Froyo rom is not too bad. Since you have stock 2.2 it will be a little more tricky than if you were still on 2.1.
First, what is your build number? look on the sticker under your battery to see a four digit number beginning with either 10 or 11.
I will private message you with more.
taltal13 said:
Thanks for the quick replay Jack especially on a Fri night. What exactly do I do? Is it difficult to do?
Click to expand...
Click to collapse
Make sure you READ EVERY LINE OF THE OP. When you think you got it, read it again, then give it a shot. For the time being just factory reset your phone, should clear up some of your issues. Good luck
sent from long ago, in a Galaxy far, far away.
^^^ he's right. READ, READ, READ... until you're sick of it. It will pay off and keep you from bricking. Sorry I didn't mention that. But I will be glad to help you if you need.
and if (or when) you manage to brick it do not panic,, go back and read some more,, seems that almost everything an idiot like me can do is fixable,, and most normal people are pretty safe,, they are not going to kill their phone,,,,if they read and follow instructions,,,not doing those two have found my phone in some pretty unresponsive states,, but I am running mosaic VI now and loving it,,but have been on so many I had to go look,,and have finally I hope learned the value of reading ( and those other people probably do know more than me so I should not think I know better ,,,yet)
taltal13 said:
I finally updated to the official AT&T Froyo 2.2 probably about a month ago. Everything was working great. I wanted to root/enable sideloading apps/unlock. I used SuperOneClick 2.1.1. The root worked fine (at least I think so). I was not able to enable sideloading apps so I read online how to change the value of sideloading apps from 0 to 1. I also unlocked the phone using the Galaxy S unlock app from the the Market.
Almost right after the SD Scan would take a long time and then I would get a red SD card symbol saying "Low on Space - Database storage is getting low". I tried clearing cache's to fix the problem. It didn't fix anything. Soon thereafter I started getting "Message Memory Full - Incoming messages rejected due to full...." I cleared phone log/txt messages but it hasn't fixed anything. I looked at my internal and external SD card. My external card is 3.68 total with 17MB available. My internal has 12.67GB available.
Today all of a sudden if I try to look at my missed call I get "samsung captivate the application phone (process com.sec.android.app.dialertab) has stopped unexpectedly. Please try again". I get similar messages trying to open Gmail. I haven't gotten it on any other apps yet as far as I know. It vibrates like crazy when the apps crash.
Can anyone help me with the problem? It's making my phone useless right now and my battery is dying much quicker than before. Thanks!
-T
Click to expand...
Click to collapse
Not sure how much of knowledge you have gained before doing these attempts of changing some values to enable side-loading...
I would suggest to do factory reset since you are still on FROYO and see if this does the magic.
If it gets locked back to AT&T, I suggest just talk to AT&T rep to unlock & side-enabling. Once all is well, you can do rooting as you did before. Hope this helps to solve your problem.
For any other help, we have XDA here and get some time to go through forums. As others suggested, please read, understand and act.
A day after I posted this the phone seemed to be working right. However Jackman pointed out if it happened once it's almost sure it will happen again. I tended to agree with him so did a factory reset and then flashed with Cognition 4.5.3 with a lot of Jack's help of course. Right now seems to be working flawlessly. I do like this whole custom ROM idea. Even thinking about buying a used Captivate on ebay just so I can mess around with other ROMs. Thanks everyone for your help & input. If you have any other suggestions my ears are always open...
Tal
taltal13 said:
A day after I posted this the phone seemed to be working right. However Jackman pointed out if it happened once it's almost sure it will happen again. I tended to agree with him so did a factory reset and then flashed with Cognition 4.5.3 with a lot of Jack's help of course. Right now seems to be working flawlessly. I do like this whole custom ROM idea. Even thinking about buying a used Captivate on ebay just so I can mess around with other ROMs. Thanks everyone for your help & input. If you have any other suggestions my ears are always open...
Tal
Click to expand...
Click to collapse
Just for a bit of encouragement ive been using Cognition 4.5.3 as my daily driver for the past 4-5 months and have never had a single issue with great battery life. Ive tried numerous other roms on this forum and always have run into a boot loop, force close, or other random issue that makes my phone unstable but with Cognition I experience what my phone was meant to be like.
Holler y'all, I'm hoping you might be able to lend me a hand with these here droid troubles, you see I was fiddling with my Streak and I seem to have broken something kinda important. My droid now tells me my internal storage has a total space of 0.00B on which 2.15GB of applications are installed, contradiction I know. What's kinda weirdypants is that I seem to be able to install new apps fine, but when I try to use the camera I get the "Please insert an SD card before using the camera" nonsense. I should probably note that I also have an external SD plopped into the slot. So there's actually two SD cards, why the camera doesn't see either I ain't got a scoob.
So how did I get here? Well... I had been using that CM10.1 rom, which was quite shexy and all, but the lack of camera and the constant crashing that required a reset made it too unreliable for my use. I decided to downgrade back to Honeycomb and everything seemed to point towards StreakDroid-HD7-R8, but things went a little sideways and I ended up in a boot loop. Perhaps I shouldn't be fiddling with things when I'm so shleepy. Anyways I got my paws on a stock rom and managed to install it with fastboot and recovery. Everything looked fine and I went ahead with setting it up and installing apps, until I got errors about the SD not having enough space to install some apps when it really should've had plenty. I rooted it, tried clearing caches, formatted it, but there was no change except for me having to install all my apps again. Oh yeah, I couldn't backup in Titanium either. So here I am.
Perhaps the SD is dying, perhaps I corrupted it with my fiddling, maybe it's something to do with the partitioning, maybe it's something else? If anyone has any ideas or suggestions, please share.
Also, if the SD is to be retired, is there anyway of redirecting apps which would normally use the internal SD use the external instead, for example the camera app?
Thanks in advance.
That is becuase CM10.1 changes the partition tables.
Does not anyone read around here? There is like 10 people who have posted the exact same thing.
You need to restore to Android 2.2 and then upgrade from there.
giveen said:
That is becuase CM10.1 changes the partition tables.
Does not anyone read around here? There is like 10 people who have posted the exact same thing.
You need to restore to Android 2.2 and then upgrade from there.
Click to expand...
Click to collapse
Offt, that was a tad fiesty. My apologies hombre, I do read and I've ready plenty on this forum, but I guess I haven't read the right threads, perhaps I didn't know the right combination of words to search for. Slap me with a wet fish and shower me in stale coco pops - I am a daftie! You're a mighty fellow, so I shant be cheeky, you've spent a great deal of time making the streak more awesome for all of us, which I do appreciate greatly. Thank you.
Now when you say restore to Android 2.2, are we talking stock ROM here? And do I have to do anything special beforehand or is it just a case of plopping the ROM on my SD and restoring? Thanks kindly for your help captain.
You need to grab the NVFlash pack to restore to Android 2.2, which will also restore the Dell crappy partition tables.
Look at TheManii's DevHost page, he should have it.
Partition tables had to be changed as Dell did not correctly do Android, resulting in the sdcard daemon being broken, so they created something called like "oem_sdcard". If they had just done it right the first time, we would be in this predicament.
Oh and anytime you need to be slapped by fishes, I'm more than glad to. If you had merely scanned the General section, before you posted, you would have seen at least, three threads, where people were having the same problem, and where each time I already stated the exact same thing that you needed to do.
I'll take the slap. I think I spent most of my time in the Dev section, yet I post here in General, you see, that is why I am daftie! My internal compass is corrupted.
Many thanks for the help and info, perhaps someone should slap Dell with a fish? Anyways I best go correct my wrongs now.
I have read many threads and I have the same problem. However, I already used nvflash to repartition my Dell and revert back to 2.2.2. I then updated back to Honeycomb 3.2 and I still have this issue. I ran it a couple times... repartition and restore back to 2.2.2 but still no luck. Any thoughts? Sorry to respond to such an old thread, just fishing for any ideas.
Sent from my SAMSUNG-SGH-I337 using xda app-developers app
xcover2 Same issue
I am facing same issue with my xcover2 , any solutions ?