Develop Bugs

Synergy Godmode

RC2+ Godmode looks pretty damn tempting, but does that performance enhancement drain the battery life? currently on evokings alliance rsl1 and the battery life is pretty awesome. battery is something i enjoy keeping up but a boost in performance no one can turn down

coke32 said:
RC2+ Godmode looks pretty damn tempting, but does that performance enhancement drain the battery life? currently on evokings alliance rsl1 and the battery life is pretty awesome. battery is something i enjoy keeping up but a boost in performance no one can turn down
Click to expand...
Click to collapse
Looking forward to the answer to this myself

coke32 said:
RC2+ Godmode looks pretty damn tempting, but does that performance enhancement drain the battery life? currently on evokings alliance rsl1 and the battery life is pretty awesome. battery is something i enjoy keeping up but a boost in performance no one can turn down
Click to expand...
Click to collapse
Personal experience so far is that I have taken a huge hit in battery performance. If I use my phone for 5 minutes or so, it drops almost 10%. After that it slows down its battery drain to about 5% every 20 minutes or so. YMMV so take my experience with a grain of salt.
*Edit* I'll add that RC2 Godmode just came out last night, so there's still plenty of tweaking to be done, workarounds for issues to be figured out, and other such stuff that comes with a pivotal rom release. I'm not switching to another rom because of Godmode, but if battery life is a concern, try out Godmode, if it doesn't pan out, head back to regular RC2. 'nuf said.

My honest opinion is to sit tight a few days. I have rc2-gm sitting on my phone and I decided to wait.
The kernel source is out now. SO man things about to happen. Nets already dropped a version but its a basic universal. Plus it seems a high ratio(my option) of people are having issues with rc2-gm it seems.
This is coming from someone that literally has every current Rom downloaded to his pc.
Sent from my PC36100 using XDA Premium App

i feel really dumb asking this, but i saw the ext2 for the file system and yaffs2 for the wear leveling. whenever i see ext2 i think of an sd card partition. does godmode partition the SD or does it format the NAND so it reads that way?
again im not exactly a noob but this just confused me

thoughtlesskyle said:
i feel really dumb asking this, but i saw the ext2 for the file system and yaffs2 for the wear leveling. whenever i see ext2 i think of an sd card partition. does godmode partition the SD or does it format the NAND so it reads that way?
again im not exactly a noob but this just confused me
Click to expand...
Click to collapse
I asked basically the same question. I had mine set to an ext3 for the 3.0 roms but went to normal rc2. Apparantly godmode makes its own ext2 partition while installing.
Sent from my PC36100 using XDA Premium App

blizzard1017 said:
I asked basically the same question. I had mine set to an ext3 for the 3.0 roms but went to normal rc2. Apparantly godmode makes its own ext2 partition while installing.
Sent from my PC36100 using XDA Premium App
Click to expand...
Click to collapse
oh okay does it reformat the sd in the process or just makes a partition using the free space?

To my understanding it just makes a partition and does NOT reformat the sdcard.
I might flash it today and report back but I do know people were restoring stuff just fine. I haven't read the past 4-5 pages but I read the 1st 10 lol since it dropped and nothing leans towards a full wipe.

blizzard1017 said:
To my understanding it just makes a partition and does NOT reformat the sdcard.
I might flash it today and report back but I do know people were restoring stuff just fine. I haven't read the past 4-5 pages but I read the 1st 10 lol since it dropped and nothing leans towards a full wipe.
Click to expand...
Click to collapse
your insight has been great please report back when you flash it

this has nothing to do with your SDcard. It just uses a different filesystem on your internal memory.
When you partition your sdcard for apps2sd, you need a filesystem on that partition. ext2/3/4 are native linux filesystems so that is what gets used. The other partition that you see from Windows is FAT32 which is a near universal filesystem across Windows, MacOS, and even Linux... but has it's limitations.
ext2, ext3, and ext4 are all just versions of the ext filesystem. Much like FAT, FAT32, and NTFS are all filesystems.
wikipedia:
ext filesystem
YAFFS filesystem

How do I get synergy? I downloaded the link from the forum but all it turned out to be a html document

it worked for me: very quick. and I am coming from an AOSP, with zero bloat - see below:
{
"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"
}

Battery life was terrible when I first flashed it. After a few reboots and charges its starting to last longer. The Rom is extremely snappy and nothing seems to be wrong with it. Give it a couple days and you won't regret flashing this Rom (godmode rc2)
Sent from my PC36100 using XDA App

ivalwsbncrz said:
How do I get synergy? I downloaded the link from the forum but all it turned out to be a html document
Click to expand...
Click to collapse
click on the link and it should take you to wupload.com then scroll down the page and click the slow download unless you want to pay for the premium.

sooo.... my phone is stuck at the HTC evo screen.. i know what to do bootloader wipe and flash something else.. i did that i flashed the just synergy. but want this... so can some 1 help me out plz

cstyle101 said:
sooo.... my phone is stuck at the HTC evo screen.. i know what to do bootloader wipe and flash something else.. i did that i flashed the just synergy. but want this... so can some 1 help me out plz
Click to expand...
Click to collapse
You may have figured this out already, but after flashing the Synergy RC2 + GM, your phone will often sit at the boot screen for much longer than normal. Then you get to the animation screen where it will also sit for quite some time. This is due to all of the tasks that the ROM installation is performing during boot-up. Some folks have waited 15-20 minutes to get to the lockscreen.
I hope that this helps.

Can you nandroid backup and restore it with godmode like normal?
Sent from my PC36100 using XDA App

Synergy RC2 + Godzilla Mode - installing, and what you 'might' expect.
(Preface: Search for a download a copy of Cirus' VR_SUPERWIPE.zip, and leave that on the root of your SDcard for as long as you intend to be flashing ROMs on your phone.)
To install the Synergy RC2+Godzilla Mode ROM, copy all of the contents of your SD card onto your computer. Then partition and format your SD card. I created a 1024MB ext2 partition, assigned 32MB for swap (which won't be used until kernel support is there, but its coming), and the rest to the regular FAT partition. Once that was completed, upgrade the ext2 partition to ext 3. Do not upgrade it to ext4 at this time. Its better and we want to, but its not supported yet.
Now, copy all of the contents back onto your SD card. In recovery, wipe everything (except SDcard) in Amon Ra's "Wpe" section once. I then recommend that you flash Virus' VR_SUPERWIPE.zip file. Now you're ready to flash a ROM.
Flash the ROM itself. Expect it to take longer than usual to flash. Reboot when prompted, and now expect to wait far longer than usual for it to boot up. This is often 15-20 minutes. Along with the usual, it is creating ext2 images of some of the partitions that exist in the system memory, and that takes time.
Once it boots completely, go through the basic setup wizard to get your phone up and running but don't start installing/restoring all of your apps yet.
Search the Synergy thread, find and download the dta2sd for Synergy RC2+GM, and flash it in recovery. This will replace the a2sd script thats in their by default, and will move your dalvik back into system memory by default.
Boot up, and download A2SDGUI from the market. Launch it, and on the tab it opens on, select to enable zipalign on each boot. **Optional: on the memory tab, choose your preferred memory profile (I used Agressive).** Now reboot, and when it comes back up, install/restore your apps.
NOTE: when I began installing/restoring apps, I started getting low memory warnings. I opened A2SDGUI, went to the information tab and I did indeed have very little system memory available. At this point, I went to the Dalvik tab and selected 'Dalvik on SDcard', and pressed 'move and rebuild'. It does its thing and reboots the phone. This will also result in a longer than normal startup, and it may reboot during the initial boot-up. You are not in a boot-loop, so don't get nervous about it.
Once it came back up I had sufficient memory available. Also, based on what I read in other pposts I expected a performance hit by relocating the dalvik cache to my SDcard (its in the ext 3 partition with the apps), but I did not see one at all.
Finish installing your apps, and enjoy a nice ROM that benchmarks through the roof!
**NOTE 2: Although the Synergy RC2+GM does achieve very nice Quadrant scores, I personally found it to be quite slow to respond...laggy. Choosing the Agreessive memory profile in A2SDGUI (DTa2sd) did help with this. But, if I were to do it over again, I'd leave that setting alone and run the "V6_SuperCharger_for_Abdroid" shell script in the Terminal Emulator instead. I used that in the Synergy RC2 no-GM, which was not as laggy to begin with, but after running that script there was zero lag anywhere. It is simply an amazing script.
Regarding battery life, a few users reported horrible battery life, most reported as good as the no-GM version, and a few reported better battery life that the no-GM version. I say try it; either it will be good or bad. Some folks had to flash and build the ROM 3-4 times before getting that magical install that runs great.
One more thing. I only install about 40 apps, including all three Angry Birds. A single nand back-up of this ROM as setup on my phone is 1.09GB in size.
I hope that this helps clarify things. Thank you for your time.

WOW! Thanks for that
sent from my synergized supersonic

thoughtlesskyle said:
your insight has been great please report back when you flash it
Click to expand...
Click to collapse
Well I am about 24 hours in and absolutely love it. Super fast, battery isn't as bad as I thought it would be. I ran it down today but had some heavy use. Can't wait for the mods/extras to catch up.
Sent from my PC36100 using XDA Premium App

[Dev/Chefs] Market download loops, hogging internal storage: /data/cachemnt

I am cross-posting this from here because the issue is not limited to that particular ROM.
I have searched for /data/cachement, cachement, market duplicating downloads, etc. and have not found any discussion on this. I can't be the only one with this problem.
I would like to check other's /data/cachemnt folders and see if this is a systematic issue where APKs get orphaned.
------------
ROM: Mikhei777's Sense 3.5
Market Version: 2.3.6
APKs in cachemnt: Yes
------------
Summary finding:
Seems like only Sense ROMs have /cache mapped to data partition instead of cache partition (Thanks iamcxa).
The mapping of /cache to data partition causes app install failures because the market download can take up the space needed for the app install. This becomes a cyclic problem because each subsequent market download only frees up enough space for the download, not for the install.
Ideally, if /cache is contained within data partition, market should use hard links to install apks from /cache to /data/app. This allows cache to be cleaned up without affecting installed apps while not taking up extra space. I'm not sure if this is doable, but my feeling is that it is not without modifying market app. The app is designed for a separate cache partition and we cannot hard link across partitions.
I believe it is better for /cache to be mapped to cache partition:
-Mapping /cache to data partition creates the appearance of more internal storage, but it is used twice as fast and results in app install failures.
-Mapping /cache to cache partition should allow Android (or app level?) to manage the contents when it is full.
-No app install failures until you are really out of space on data partition.
-The free space of data partition is the actual usable space for app install.
-When downloading apks from market are greater than cache partition size, market app actually queues the downloads so that everything completes successfully when there is sufficient data partition space for installation.
Alternatively, we can link /cache to /sdcard/cachemnt:
-Same benefits as linking to /cache, but without using internal storage space.
-Market won't be able to manage cache usage until it fills sdcard, but user can clean this manually quite easily.

OCedHrt said:
I am cross-posting this from here because the issue is not limited to that particular ROM.
I have searched for /data/cachement, cachement, market duplicating downloads, etc. and have not found any discussion on this. I can't be the only one with this problem.
I would like to check other's /data/cachemnt folders and see if this is a systematic issue where APKs get orphaned.
------------
Market Version: 2.3.6
APKs in cachemnt: Yes
Click to expand...
Click to collapse
Yes i found them there only thing i could tell you if this really bothers you just delete them. Btw this is the wrong section

sportsstar89 said:
Yes i found them there only thing i could tell you if this really bothers you just delete them. Btw this is the wrong section
Click to expand...
Click to collapse
Well, I wasn't sure if this was strictly a question. If something is hogging up 50% of my data partition, it's no longer a "it bothers me so I'm going to delete them" question. If this is not typical Android behavior, then there is a bug somewhere.
Just like other threads to track / collect data on other issues, such as GPS battery drain, or BT voice commands / no sound problem, etc, this is a problem.

OCedHrt said:
Well, I wasn't sure if this was strictly a question. If something is hogging up 50% of my data partition, it's no longer a "it bothers me so I'm going to delete them" question. If this is not typical Android behavior, then there is a bug somewhere.
Just like other threads to track / collect data on other issues, such as GPS battery drain, or BT voice commands / no sound problem, etc, this is a problem.
Click to expand...
Click to collapse
Well first wyou have to figure out if more people have it
Sent from my Transformer TF101 using xda premium

sportsstar89 said:
Well first wyou have to figure out if more people have it
Sent from my Transformer TF101 using xda premium
Click to expand...
Click to collapse
That's the purpose of this thread
I am going to test the CWM backups I have for this.

OCedHrt said:
That's the purpose of this thread
I am going to test the CWM backups I have for this.
Click to expand...
Click to collapse
did you means the /cache and /data/cachemnt have the same file?
if yes i can explain ... they are be linked together when all Sesne build runs initrd.gz.
*seems only sense builds have this link

iamcxa said:
did you means the /cache and /data/cachemnt have the same file?
if yes i can explain ... they are be linked together when all Sesne build runs initrd.gz.
*seems only sense builds have this link
Click to expand...
Click to collapse
Right. The issue is that the contents are not cleaned up correctly. I assume that after Market installs an APK or if the download fails, it should delete the file. However, this is not happening and the file remains.

OCedHrt said:
Right. The issue is that the contents are not cleaned up correctly. I assume that after Market installs an APK or if the download fails, it should delete the file. However, this is not happening and the file remains.
Click to expand...
Click to collapse
oh, i got what you mean. i have tried moved it to link to ram folder in my test build but seems not a good idea.

iamcxa said:
oh, i got what you mean. i have tried moved it to link to ram folder in my test build but seems not a good idea.
Click to expand...
Click to collapse
Especially when it is taking up more than 100mb!

OCedHrt said:
Especially when it is taking up more than 100mb!
Click to expand...
Click to collapse
well ... that's serious. but I haven't see that, although I think can use a cron or a script let android clear it every day around sleep time , like when 4:00 am then try to kill all of /data/cachemnt/.apk or just kill all of them under /cachemnt/*.

iamcxa said:
well ... that's serious. but I haven't see that, although I think can use a cron or a script let android clear it every day around sleep time , like when 4:00 am then try to kill all of /data/cachemnt/.apk or just kill all of them under /cachemnt/*.
Click to expand...
Click to collapse
That's just a small part of it...we can also clear cache from CWR, or use the cache partition instead of linking to data partition.
The problem comes when the cache partition is linked to the data partition. I think it is only cleaned up (FIFO) when there is insufficient space, since it is using the internal storage, it isn't cleaned up until there is insufficient space on the internal storage. This may sound okay, but half the time the market download successfully fits into /cache but does not leave enough space to install the apk. This causes the install the fail and you are likely unable to install any app until some space is freed up. If you try to install a different app, it will just replace another item in the cache and there will still not be enough free space to install. I would rather dedicate a fixed partition to the cache so that it does not interfere with application installation.

OCedHrt said:
That's just a small part of it...we can also clear cache from CWR, or use the cache partition instead of linking to data partition.
The problem comes when the cache partition is linked to the data partition. I think it is only cleaned up (FIFO) when there is insufficient space, since it is using the internal storage, it isn't cleaned up until there is insufficient space on the internal storage. This may sound okay, but half the time the market download successfully fits into /cache but does not leave enough space to install the apk. This causes the install the fail and you are likely unable to install any app until some space is freed up. If you try to install a different app, it will just replace another item in the cache and there will still not be enough free space to install. I would rather dedicate a fixed partition to the cache so that it does not interfere with application installation.
Click to expand...
Click to collapse
so that is the reason let some rom link this /cache to sdcard, and seems solved this issue ... even it don't cleared that folder still doesn't matter.

iamcxa said:
so that is the reason let some rom link this /cache to sdcard, and seems solved this issue ... even it don't cleared that folder still doesn't matter.
Click to expand...
Click to collapse
Yes. Then app installs will not fail. But doing so still breaks market apps management of the cache partition because it doesn't run out of space. Although this is not a big deal I think.
Thanks for providing the key explanation to help me wrap my head around what's happening. I have updated the first post.

OCedHrt said:
Yes. Then app installs will not fail. But doing so still breaks market apps management of the cache partition because it doesn't run out of space. Although this is not a big deal I think.
Click to expand...
Click to collapse
yeah I think that's fine, because we already broken the android and rebuilding for HD2 ... so any help can i provide?

iamcxa said:
yeah I think that's fine, because we already broken the android and rebuilding for HD2 ... so any help can i provide?
Click to expand...
Click to collapse
You can have a thanks
I think ultimately the goal is to raise awareness for chefs to not link /cache to /data/ but rather link it to /sdcard or cache partition.

OCedHrt said:
You can have a thanks
I think ultimately the goal is to raise awareness for chefs to not link /cache to /data/ but rather link it to /sdcard or cache partition.
Click to expand...
Click to collapse
lol thanks , you know i'm a thanks meter Collectors now

To further emphasize why this is a major problem, I have attached screen captures of market downloading the same app multiple times simultaneously. I just purchased 5 apps, but market has already downloaded over 17 apks and is still going. I had 160 mb free prior to this and am now out of space before any app is even installed!
{
"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"
}
Sent from my HTC Runnymede using XDA App

OCedHrt said:
To further emphasize why this is a major problem, I have attached screen captures of market downloading the same app multiple times simultaneously. I just purchased 5 apps, but market has already downloaded over 17 apks and is still going. I had 160 mb free prior to this and am now out of space before any app is even installed!
Sent from my HTC Runnymede using XDA App
Click to expand...
Click to collapse
the pics are very small. try this script, put it to /init.d and set permission to 755, when reboot should works.

iamcxa said:
the pics are very small. try this script, put it to /init.d and set permission to 755, when reboot should works.
Click to expand...
Click to collapse
Oh sorry about that. I guess they get resized when uploaded using the XDA app
Thanks for the script! I'm not sure that I fully want them on my sdcard just yet. I upgraded to the new market because at least it only downloads 1 apk at a time - and I think this may be the reason for that change.

OCedHrt said:
Oh sorry about that. I guess they get resized when uploaded using the XDA app
Thanks for the script! I'm not sure that I fully want them on my sdcard just yet. I upgraded to the new market because at least it only downloads 1 apk at a time - and I think this may be the reason for that change.
Click to expand...
Click to collapse
i saw have someone dl my script, seems i made some mistake it will work first time , when second reboot maybe no go. so i upload new one.

Do you see something wrong with this?

Ok this is scary. Phone is stuck on this! Erased some apps but it won't go away! Please help!! I don't like this number!
{
"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"
}
Killing Zombies With My Galaxy S II

Devil Phone!
Sent from my SGH-T989

Lol
Sent from my SGH-T989 using XDA

Googleing images for 666 makes me scary too! you should throw that devil away!

Haha that's sweet.
There is enough hate in the world. Why can't we all get along here ...?

You are the anti christ
Sent from Flip's SGS2

Upload a hi-res picture of Jesus onto your phone. Make sure it is on your system memory, not your SD card. That should fix it.

Haha, just get a gameloft game
It will ALL be fine
Sent from my SGH-T989 using xda premium

A Tebow wallpaper will fix it all.

CincoDeDrinko said:
A Tebow wallpaper will fix it all.
Click to expand...
Click to collapse
Roflmfao...that might make it worse
Sent from the horsemen of death using the galaxy at his will

darkside79 said:
Ok this is scary. Phone is stuck on this! Erased some apps but it won't go away! Please help!! I don't like this number!
Killing Zombies With My Galaxy S II
Click to expand...
Click to collapse
well that's what you get for killing zombies...
is joke
you would want to delete a SYSTEM app. like when you go into TB, they're the red fonts.
Or just download something into the ROOT of your phone or somewhere along there.
sdcard is internal
external_sd is your microsd
anything on the ROOT:apps, system, lib, etc is the system partition.

zander21510 said:
Upload a hi-res picture of Jesus onto your phone. Make sure it is on your system memory, not your SD card. That should fix it.
Click to expand...
Click to collapse
lmao!! do this quick OP. You will be saved from the clutches of evil

Jokes aside, what theme are you using?
Sent from my SGH-T989 using xda premium

What theme is that?
Sent from my SGH-T989 using xda premium

darkside79 said:
Ok this is scary. Phone is stuck on this! Erased some apps but it won't go away! Please help!! I don't like this number!
Killing Zombies With My Galaxy S II
Click to expand...
Click to collapse
Download and use this if you can get into recovery mode
http://forum.xda-developers.com/showthread.php?t=1477955
1.download and place darkside super wipe on the root of your SD card.
2.boot into recovery mode wipe data factory reset .
3.select install from internal SD card and select install darkside super wipe then flash whatever rom then wipe dalvik cache and fix permissions reboot let phone sit for at least 10 minutes reboot again and you should be good.
4.
Sent from my SGH-T989 using xda premium

dawgboy1783 said:
Download and use this if you can get into recovery mode
http://forum.xda-developers.com/showthread.php?t=1477955
1.download and place darkside super wipe on the root of your SD card.
2.boot into recovery mode wipe data factory reset .
3.select install from internal SD card and select install darkside super wipe then flash whatever rom then wipe dalvik cache and fix permissions reboot let phone sit for at least 10 minutes reboot again and you should be good.
4.
Sent from my SGH-T989 using xda premium
Click to expand...
Click to collapse
i don't think he wants to wipe his phone clean..

Haha I gotcha bro, does anyone know if darkside79 has a dl link for his darkside blue theme x?
Sent from my SGH-T989 using xda premium

use Link2SD and get a good sized SD card
check out my Link2SD topic in the INDEX
darkside79 said:
Ok this is scary. Phone is stuck on this! Erased some apps but it won't go away! Please help!! I don't like this number!
Killing Zombies With My Galaxy S II
Click to expand...
Click to collapse

Prolly answered, but hopefully this is helpful
darkside79 said:
Ok this is scary. Phone is stuck on this! Erased some apps but it won't go away! Please help!! I don't like this number!
Killing Zombies With My Galaxy S II
Click to expand...
Click to collapse
IF THIS IS ALL YOU SEE ON BOOT SKIP FIRST PARAGRAPH AND TRY SECOND BOOT IN TO RECOVERY AND CLEAR YOU CACHE AND DALVICK CACHE AND THEN UNDER ADVANCED RUN FIX PERMISSIONS AND RESTART. DON'T GET TOO UPSET IF THIS DOES NOT WORK I BET YOU JUST HAD SOMETHING GO WRONG AND A FRESH INSTALL OF A ROM WILL HELP [BE SURE TO CLEAR CACHES AND /DATA AT VERY LEAST I HIGHLY RECOMMEND WIPING SYSTEM BUT UP TO YOU].
You could also look in to e2fsck. If you use a terminal emulator or adb if you cant get past that screen and a computer you can copy e2fsck [be sure to find a version that works with android [or try to run it from /system/bin or /system/xbin as it should be there I believe and with google you can pull out the command for it and run a disk check on any mounts [fdisk -l should work] use adb shell from any computer [again google if you need to download adb]
Also, you guys do realize unless you go way out of your way to purchase a super fast SD Card installing apps to SD will really slow the phone down as a whole and with 2gigs of system storage and 11G of sd for "standard google app to sd" [basically widgets will not work if app is on sd so keep apps with widgets on phone] and still keeps the phone reading remaining apps from phones memory [using "root apps2sd" method you are basically tricking the phone in to thinking space on the SD is actually the phones memory and is why things like widget will run BUT phone doesn't know what is SD and what is phone memory in this scenario it looks the same so any media file indexing or regular system caches end causing heavy SD usage and can be a HUGE bottleneck [just saying lets not start nit picking and figuring out who is bigger these are just my 2cents and I recognize your views may differ from mine and that is totally cool with me just throwing out my 2 cents for newbs and others who WANT to read it ;-)[/B]
I am pretty sure someone explained this already your System storage is different than your SD Card and internal SD Card [even though from what I have read system storage is a partition of the USB storage]. You would have to either [add/remove apps to your phone storage [installing to SDCard would not change system storage value], clearing your cache and/or dalvick cache [see recovery menu [hold vol up+down as you power on phone and release as soon as you see the white Samsung logo [release vol keys BEFORE it goes away]. wipe cache is on main men and dalvick cache is under advanced. You could also move apps in manage apps from phone storage to SD Card [will use USB Storage if you have not inserted a "real" SD-Card in to your phone] This may cause widgets to break or apps to slow down so be sure to use your judgement.
RECOVERY MENU FIX [POSSIBLE] in more detail
If all that did not work clear your cache [main menu] and dalvick cache [advanced menu] and then go under advanced and choose fix permissions and allow that to run [depends on how many files you have as to how long this takes but it usually is not long at all and then go back to main menu and choose restart system and see if that clears the issue for you.

[Q] any advice on fixing sdcard problems?

ive looked over the internet and found no solutions that helped
recent my samsung epic began giving me messages like microsd card unexpectedly removed etc. So i did what i read online and formated it on my pc and its "settings" of course i made a pc backup as well.
well it was all well for only two days and i got messages that now said sd card safe to remove. and the apps on the sd card wouldnt open no more and give a message of app not installed. so i factory reset in settings, format sd card again in settings I tried flashing a new rom, wipe data and dalvik etc ....
but the problem returns shortly after trying these ... on cwm log it shows me "cant format unknown volume /sdcard and /emmc"
now my pc and phone still read my card but it doesnt allow me to save anything or open anything on there such as apps, photos, etc.
now ive seen online suggestions of using odin or more cwm options that i have not tried because im not an expert at all yet. im in highschool so i cant really afford to expeirement myself and rather ask an expert on here.
if i should use odin or other options can someone please tell me how and what to do?
btw i have a 32gb sandisk card and im running cm10 and have never flashed other roms since i rooted first time. and i believe this started happening after i did a restore on one of my nandroid backups and i never wipe before restoring so maybe that might be the root of this conundrum i now face...

nikon120 said:
Tutorial on using ODIN and getting back to stock
Don't bother with the EL30 tar. Start just below that where the SPH-D700-FC09-8Gb-REL.tar download link is. That is the file which will give you 100% current stock.
EDIT:
After reading your original issue with the SD card...
You should remove the card from the phone.
Connect the card to a computer.
Backup whatever stuff you want to keep.
Format the card. (FAT32)
Move whatever stuff you backed up, back to the card.
Put card back in phone.
In CWM, run Fix Permissions in the advanced menu.
Optional: clear cache partition
Try again with the steps you took where you encountered the write issue to the card.
If you still experience the problem, then try ODIN to test against 100% stock.
If you still experience the problem on 100% stock (FC09), then replace the SD card.
Click to expand...
Click to collapse
That was my original reply in the other thread. Since you've formatted already, use the fix permissions option in CWM and try again.
If nothing, then go back to stock and try again. If that doesn't work, then replace the card.

Alright well I'm try this Saturday and post back here to let you know how it went
Sent from my SPH-D700 using Tapatalk 2

sorry for making you wait man but i had to take the act yesterday and i didnt want to f up my phone right before test day... but i was going to ask that i have a samsung usb cable that looks different than other samsung cables i have . and i used it before to root my phone and another phone and had no problems with it but it is samsung so could i still use it?

alright i just looked up what cables samsung has so i can which one i got and my mine i believe is their "travel charger" cable, the ends are a smooth glossy type plastic. it has the square shape adapter.
{
"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"
}

holy **** i used samsung usb cable and did what you said ...and ill be damned im running fc09 right now..thanks man alot appreciate it alot Ima try it for a whole day tommorow see how it goes with the sd card and go from there.
aww damn its been only a few minutes and the phone already said sd removed but it reread it again ...
and its still working..i think

nike0518 said:
holy **** i used samsung usb cable and did what you said ...and ill be damned im running fc09 right now..thanks man alot appreciate it alot Ima try it for a whole day tommorow see how it goes with the sd card and go from there.
aww damn its been only a few minutes and the phone already said sd removed but it reread it again ...
and its still working..i think
Click to expand...
Click to collapse
Have ya tried formating with your phone?
Seen that you tried it once before but when my epic's sd was glitching out simularly unmounting and remounting.
Or partitioning it for installing apps to it?
The other thing that maybe at fault is that when you formated with you computer is that it may have defaulted to a 'quick' format option. I've had nothing but mixed results with quick or fast formating option on windows and linux alike. There should be a check box option or advanced button in the formatting window on windows that gives the option for a full and lengthy format. Note: formatting on either your phone or your computer will sertianly delete the data, so, backup. One other note: when your doing something critical with data storige and such, its a good idea to close all other windows, espechealy the ones that are accessing your file system; such as file brousers and downloading files.
One more thing about restoring a backup on your phone after restoring the restore to a new or different sdcard: it can fail spectacularly if something gets corupted during all that movement and copying, so when you do get a sd card working whether it be new or newly formated it might be a good idea to make a new backup.
Sent from my T-Mobile myTouch 3G Slide using xda app-developers app

yeah i tried all of that and i used a full format and didnt even restore to it ..
im on stock right now and it seems to randomly unmount but remount by itself when it says scanning media...
im going to root again before the end of tonight bc it sux on stock and ill check to see if the problem persists and im going to try replace the sd card slot too tonight because i have a few epics laying around so i check back in here tommorow afternoon
its not my sdcard for sure bc it works flawlessly on other phones and my phone did it to other sdcards as well.

Best thing you can do imo is to get a new sd card. Unless its the hw on the phone. You could solder up your own I bet, if its new for you it will be aventurous!

nike0518 said:
its not my sdcard for sure bc it works flawlessly on other phones and my phone did it to other sdcards as well.
Click to expand...
Click to collapse
Seems like you've found the fault with the hardware. Before repair I'd try cleaning the contacts. Hope its just software though as it be a pain to do a repair and still have the same issue.
Sent from either my SPH-D700 or myTouch3Gs using XDA app
"it never hurts to help"

well i was sure it was hard ware after the message appear on 100% stock but the good thing i have a few epics sitting around with cracked screens/bricked/other issues so i got replacement parts.
but i fixed the problem !
i opened my epic and took out it sd card slot completly off the motherboard and same to other epic and swapped them.
and it didnt require any soldering since the epic is bada** phone .. very precise placement required though to put the slot back on the motherboard but i matched it after taking my time lol
now im just to going to root and flash and be a happy camper.
thanks very much though guys now im more confident in unrooting my phone and i know how to as well.
it seems the problem is gonnne.

crappppp the problem returned but now it fixes itself right after but this can trick some of the apps.
like apollo .
i have a few songs on there and unless i pop out and reinsert the sdcard or reboot it Apollo will think i dont have those songs ...which sux bc i use it frequently but yeah im just try swapping the sdcard slots again .

[Q] TWRP 2.4.1.0 backup amount smaller?

So the other day, I found my S3 to have apps crashing all over the place... nothing had changed prior to this, I literally just picked it up and saw avast anti-virus had crashed, and continued to do so, as did the stock browser and so on (still have absolutely no clue what caused this in the first place). I figured I'd just reboot....except then it wouldn't proceed past the s3 splash screen (thankfully I can still boot into recovery or download modes).
Had to wait to get a SanDisk Ultra 64 GB MicroSDXC Class 10 UHS-1 Memory Card (SDSDQU-064G-AFFP-A) delivered, as I had a lot to backup via the TWRP 2.4.1.0. However it lists the following under backup device:
System (387MB)
Data (1755MB)
Boot (10MB)
Recovery (10MB)
Cache (85MB)
This comes to 2247MB, but I know I have around 20-22GB on the internal storage.... I ran the backup and that's all it's reporting as having backed up. I need to really get my phone back up and running, but I'd rather not loose any photos or anything else on the internal storage.
Also, while I'd love to just copy files via usb, none of the computers I currently have access to can properly install the Samsung usb driver... it's rather frustrating, as I spent many hours attempting to get it to work last night.
*edit*
Figured it out (yay lots of googling!), doesn't backup the DCIM folder and such. Copying that over to the external sd card manually...though so far not even a hint of blue on the progress bar and it's been 10min...

GB452 said:
So the other day, I found my S3 to have apps crashing all over the place... nothing had changed prior to this, I literally just picked it up and saw avast anti-virus had crashed, and continued to do so, as did the stock browser and so on (still have absolutely no clue what caused this in the first place). I figured I'd just reboot....except then it wouldn't proceed past the s3 splash screen (thankfully I can still boot into recovery or download modes).
Had to wait to get a SanDisk Ultra 64 GB MicroSDXC Class 10 UHS-1 Memory Card (SDSDQU-064G-AFFP-A) delivered, as I had a lot to backup via the TWRP 2.4.1.0. However it lists the following under backup device:
System (387MB)
Data (1755MB)
Boot (10MB)
Recovery (10MB)
Cache (85MB)
This comes to 2247MB, but I know I have around 20-22GB on the internal storage.... I ran the backup and that's all it's reporting as having backed up. I need to really get my phone back up and running, but I'd rather not loose any photos or anything else on the internal storage.
Also, while I'd love to just copy files via usb, none of the computers I currently have access to can properly install the Samsung usb driver... it's rather frustrating, as I spent many hours attempting to get it to work last night.
*edit*
Figured it out (yay lots of googling!), doesn't backup the DCIM folder and such. Copying that over to the external sd card manually...though so far not even a hint of blue on the progress bar and it's been 10min...
Click to expand...
Click to collapse
I often find myself too lazy to dig out my USB cable. So I start the FTP server (FTPDroidPro (ie Pure-FTPd) because it has root access) on my phone and my computer is the client. You don't need cables.
Update TWRP.
Wipe data/factory reset (need TWRP user to confirm, but CWM does not wipe intsd when you use this option). Stock recovery WILL wipe your internal sd.
Install rom again.
Copy pictures to computer. I've said it more times than I can count, but I'll do it again. Always have a backup of important files. Pictures cannot be replaced. Perhaps invest in some Dropbox space. Then use the Dropbox app to automatically upload pictures you take. I think GDrive is cheaper. But you need G+ to autoupload there. You can send manually, but you have to remember to do it. I suppose Carbonite Mobile would work. Carbonite is a good service, but their apps have always sucked. Windows, mobile, etc.

Thought this would be a good place to mention it, but when copying the dcim folder check the thumbnails file inside it first. Mine often gets up to 10gb in size! More than the actual photos!
Anyone know why it does this?
Sent from my SGH-T999L using xda premium

Please read forum rules before posting
Questions and help issues go in Q&A and Help section
Thread moved
Thank you for your cooperation
Friendly Neighborhood Moderator

Backed up stuff and manually copied over what I could to the external sd card. Wiped cache/dalvik factory reset, flashed cm 10.1 and gapps..... rebooted....still stuck at s3/cm splash screen. What do I do now?

GB452 said:
Backed up stuff and manually copied over what I could to the external sd card. Wiped cache/dalvik factory reset, flashed cm 10.1 and gapps..... rebooted....still stuck at s3/cm splash screen. What do I do now?
Click to expand...
Click to collapse
Take out the battery, and tell me what the sticker on the inside of the battery compartment says.

Aerowinder said:
Take out the battery, and tell me what the sticker on the inside of the battery compartment says.
Click to expand...
Click to collapse
MODEL; SGH-T999
FCC ID: A3LSGHT999
RATED: 3.8V 1025mA
After that is the IMEI number and serial number.
I know I downloaded the proper cm for the galaxy s3 under t-mobile (http://get.cm/?device=d2tmo).
If I have to wipe the internal memory/format then that's what I'll do... gotta get this back up and running sooner than later.

Did you update TWRP?

Aerowinder said:
Did you update TWRP?
Click to expand...
Click to collapse
That's the one thing I hadn't done. I'll have to grab the update, and look up how to do that while in recovery mode.

Link in my signature for the tar file you flash with Odin, or the zip you flash in recovery here: http://db.tt/RkfTm2cd

Aerowinder said:
Link in my signature for the tar file you flash with Odin, or the zip you flash in recovery here: http://db.tt/RkfTm2cd
Click to expand...
Click to collapse
Thanks, I'll take care of doing that and report back.
*edit*
Nope...updated and re-did all the steps... still stuck at the s3 logo splash screen.
I presume formatting is in order?

You did a factory reset and reflashed the rom?

Yes and yes.

Salvage your data and Odin root66. Unsure what the problem is, unless your ROM download was corrupted.

Aerowinder said:
Salvage your data and Odin root66. Unsure what the problem is, unless your ROM download was corrupted.
Click to expand...
Click to collapse
Can't imagine the download being corrupted, nothing seemed amiss. I presume I am to follow: http://forum.xda-developers.com/showthread.php?p=30386309, but just need to find the bootlink files for tmobile instead? Will there be any issues with the fact that I can't get the samsung usb drivers to install on this laptop (no matter what I do, it's always shown as not having the driver required in the device manager, code 28), when running Odin?

You don't need that guide, pretend you didn't see it.
What version of Windows are you on?

Aerowinder said:
You don't need that guide, pretend you didn't see it.
What version of Windows are you on?
Click to expand...
Click to collapse
Ok, I'll ignore it then. I'm on Windows 7. I have the exact same problem with an old XP machine. Drivers report installation is successful, but once it's plugged in, drivers are either not found and/or weren't installed right. I've tried installing them in safemode, with no difference.

1) Plug phone into computer.
2a) In the control panel, uninstall Kies and SAMSUNG USB Driver for Mobile Phones.
2b) In the Device Manager, right click > Uninstall the phone device. Check the delete drivers box if it is there. Rescan for hardware changes.
3) Repeat step 2b until the phone shows up as "Android".
4) Unplug phone from the computer.
5) Install these: http://db.tt/nugwjVWT
6) Plug phone in - if still not working, it's an issue with your phone's micro USB port, your cable, your USB port, or your Windows installation.

Aerowinder said:
Issues with USB devices/drivers are usually a pain to fix, but let's try this:
I uploaded an extracted driver package for you, here: http://db.tt/As7SW9sy
Uninstall the drivers (and Kies) from the control panel. Then, when you plug in your phone, go into the device manager, right click the phone (should be pinged), select Uninstall and check delete the driver software for this device.
Then Action > Scan for hardware changes - phone should come up unrecognized (if it's recognized, repeat above step until it no longer does). Right click > update driver > point it to the extracted contents of above zip file.
Click to expand...
Click to collapse
Thanks, as soon as I get back in from walking a dog I'll try this out. Thanks btw, for all the help thus far.:good:

Aerowinder said:
1) Plug phone into computer.
2a) In the control panel, uninstall Kies and SAMSUNG USB Driver for Mobile Phones.
2b) In the Device Manager, right click > Uninstall the phone device. Check the delete drivers box if it is there. Rescan for hardware changes.
3) Repeat step 2b until the phone shows up as "Android".
4) Unplug phone from the computer.
5) Install these: http://db.tt/nugwjVWT
6) Plug phone in - if still not working, it's an issue with your phone's micro USB port, your cable, your USB port, or your Windows installation.
Click to expand...
Click to collapse
I'm starting to suspect the cable. It's not the original one, but I had to use another micro usb cable as my cat decided to chew on the other one until it fell apart. Haven't had an issue with charging, but it may be the cause with the PC to phone connection.
Did all the steps but:
{
"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"
}
is where I'm at.
Looks like I'll have to postpone this until tomorrow afternoon, and see if I can't utilize another neighbor's computer, one which has never had problems with the PC to phone connection (and I only hope that stays true with this current cable).