Related
So, a little history...
I'm on my 2nd Captivate (unrelated issue). The boot problems didn't arise until I restored my data onto it. The first time I tried restoring system data along with my apps (which I figured was safe since I was going from 2.1 stock to the same) but that had lots of issues. So I did a factory reset, and started over. This time I just restored apps and their data, and a few specific pieces of system data (contacts, wifi APs, etc). That worked better. But later I got too aggressive with what system apps I "froze" (using Titanium Backup), and it got into boot loops I couldn't break out of. So I did another factory reset.
This time, first I carefully froze only apps I was to confirm were safe to freeze. I didn't proceed restoring my apps until I was done freezing and ensured it was booting fine. I then restored all my apps (and their data). The problem is now that it takes forever to boot... in fact, it'll go into a boot loop if I just leave it be. It seems the only way I can gain access is to try and unlock it before it's done booting, clear any "Force close" errors (sometimes takes a few tries) and given enough attempts, I can get in. But the boot takes an unbelievable amount of time, and even with my original apps is many times longer than before on my previous Captivate. Once I fuss my way in, it seems mostly fine, but something is obviously wrong and I want to get it straightened out.
Aside from doing another factory reset, and reinstalling all my apps (which takes like a day without troubleshooting after each, since batch restores in TB don't seem to work well on the Captivate so I have to do them one by one), I'm hoping there's a way to troubleshoot it in its current state and try to fix the problem surgically versus erasing and starting over. I looked at the logcat logs but got in over my head... there are so many errors and warnings and I don't know what's normal and what isn't... too many to know where to begin with searching Google.
So... advice? What tools are available? Even the logcat doesn't seem to kick in until the boot is mostly done, so I'm not sure if it can catch the problem while it's happening. One frustrating thing about Android is that is seems to have no "safe mode" or other diagnostic boot or full logging where you can methodically look at what's happening and experiment with the config. If this was a Windows, Linux or FreeBSD box I'd be in my element and able to get to the bottom of this, but on Android I feel even more crippled, locked-out and helpless than even on Windows. Urgh.
There's got to be a better way to troubleshoot and fix than endless random factory resets. This is something us anti-Windows people scold PC makers for, with all their use of "Restore CDs" for every minor and trivial software issue.
Thanks!
I can't help but think you are still disabling some essential system apps. Either that or one of your apps is causing major problems. Please list what you have frozen in tibu. Btw, the batch function works fine and is what most people on here use.
Also, what is force closing after you restore your apps.
newter55 said:
I can't help but think you are still disabling some essential system apps. Either that or one of your apps is causing major problems. Please list what you have frozen in tibu. Btw, the batch function works fine and is what most people on here use.
Also, what is force closing after you restore your apps.
Click to expand...
Click to collapse
First of all, thanks for taking a stab at this.
My frozen apps are:
* AllShare
* AT&T FamilyMap
* AT&T Hot Spots
* AT&T Maps
* AT&T Music
* AT&T Navigator
* AT&T Radio
* Daily Briefing
* Days
* Instant Messaging
* Media Hub
* Mini Diary
* Mobile Banking
* Mobile Video
* MobiTV
* Where
* Write and Go
* YPmobile
I also tried removing my MicroSD card, as well as switching back to Touchwiz (from LauncherPro). Didn't help.
Yeah the batch problem in TB is very frustrating. I'm using the pay/donate version so I'm missing out on a feature I paid for. I've been exchanging emails with Joel (the author) and we haven't figured it out yet. Batch backups work fine. Batch uninstalls also work fine (update: phone just spontaneously rebooted after about 50 or so uninstalls in a batch). It's the batch restores that seem to choke it. It's not corrupt backup files... a verify runs fine, and I can individually restore the same handful of apps one by one that will choke and hang/reboot the Captivate if attempted to restore in a batch.
The FC error I get is on boot-up, as I try to unlock the screen prior to the boot finishing. I often see "Process system is not responding".
I have aLogcat installed, if that's any use. A few questions about that:
- What's the best logging level to view on? In other words, do I care about "Warnings"?
- What errors are common, harmless, and safe to ignore?
Currently I've tried uninstalling everything down to just a few core apps. Certainly boots fine now, but I get plenty of warnings and errors in logcat.
Are u restoring just the user installed apps+data, or system apps too? Or restoring system stuff like contacts data, accounts prefs, etc?
diablo009 said:
Are u restoring just the user installed apps+data, or system apps too? Or restoring system stuff like contacts data, accounts prefs, etc?
Click to expand...
Click to collapse
I did not do a "restore system data" or any batch/bulk option in TB that restored all system data. As I recall, the only system data I restored a-la-carte (by selecting the individual item from the TB list) were:
Accounts
Bluetooth pairints
Bookmarks
Calendar
Contacts
Wi-Fi Access Points
These were all items in green in TB. I don't believe I restored anything else. Possibilities I suppose are wallpaper settings, "Country, Launguage, Time Zone"... but I definitely would not have restored anything not green.
Are these items safe? Is there any system data definitely not safe to restore? I have to wonder though, if "system data" is unsafe to even restore to the same stock OS version... why back it up at all?
I'm not a long distance from doing yet another factory reset I suppose, if it must come to that. But I'd love a way a bit more analytical/exacting to try and troubleshoot this other than "reinstall one app, reboot, see what happens" as that will take me a week to get back to where I was. I also suspect it's not just one single app that would suddenly show a huge difference after installing, but instead might be the cumulative errors from several apps and knowing how to identify that and clean them up would be useful.
Using adb logcat you can view what is occurring while the phone is booting and possibly see where it is hanging or what is causing the slow boot times. I have seen problems from restoring data such as accounts and contacts with titanium backup but does not seem that it should be an issue when using the same system though I have very little experience with the stock firmware. I know it is not an answer to your question but it seems that you are wanting to remove all the att/Samsung BS so why not flash a rom that does this as well as much more?
Sent from my ADR6300 using XDA App
Thanks for the tip about adb. I've actually not needed adb for anything yet so I've never set it up or used it. I wasn't aware that the service would be active early enough on the phone's boot process to allow it to log boot logs... nor was I even aware it could do this. I'll definitely check out how to set this up... however, if you have a free second and can point me in the right direction (FAQ, instructions, etc) it'd certainly be appreciated otherwise I'll search around and try to find it.
I could probably find other ways to restore contacts and could set my accounts up again manually but I really doubt that's the cause and the other ways are sort of a pain and imperfect. Since neither of us is really convinced that'd be it I won't bother yet until/unless you really suspect it.
I wondered how long it'd take before someone would suggest a custom ROM, this being XDA and all. Short version is I'm not really sold on the concept, as they are all based on the buggy beta leaked ROM, or 2.2 ROMs from other devices that have been hacked up to sort of work as well as possible on the Captivate. All seem to have issues... enough that I'm not really left feeling confident about them. Seems every release unleashes new issues despite addressing old ones, and all seem to have at least a handful of gremlin items that just don't work quite right. Don't have a warm fuzzy feeling, and I still feel like Samsung is going to release an official 2.2 for the Captivate within the next month or so, so I'm interested to see what comes of that. If nothing else, it'll give a better baseline for custom 2.2 ROMs. Then there's the 2.3 being worked on... now that might be interesting.
I don't really think my issue here is related to me running 2.1.
On my phone so it is a pita to search and add a link for you but search for android sdk and you will find what you need to get adb up and running.
And as far as the rom issue goes..it is your phone and I respect your concerns I just had to ask
I would think its media hub that slows it down. It will search your SD cards on every boot. I would start there first.
smokestack76 said:
I would think its media hub that slows it down. It will search your SD cards on every boot. I would start there first.
Click to expand...
Click to collapse
That's one of the apps I've frozen though.
For me the longest process while booting is the stupid media scanner upon bootup. Takes FOREVER for the phone to finally "boot" all the way up.
Been looking for a way to disable it (not really lol) and only have it scan manually to see if the boot time will improve. I'd start searching there.
Also - from what I've read nothing you did should have affected the phone. BUT - if your using Google for your Calendar and Contacts.. and they all get synced up to Google? Why bother doing the restore for those? After you sign up with the Market they get pulled back down to your phone automagically
It's definitely more than just the media scanner. I watch that. When everything is loaded up, it actually reboots in a loop unless intercept the FC. The media scanner will rerun over and over each time... far more than the standard two times.
And I use Google Calendar for my events, but I keep my contacts locally on my phone.
So what is the FC again?
Yep.. my media scanner will run at least 3 times before it stops checking everything.
Very frustrating that the software does this EVERY time I boot back into my phone - you'd think a programmer would put a check to see if it had run before or make it user configurable to scan when you want it to.
avgjoegeek said:
So what is the FC again?
Click to expand...
Click to collapse
See my second post (reply #3):
"Process system is not responding"
LOL sorry not enough coffee and a lil' guy that decided to wake up at 4a.m. = not a good mix.
Well.. did the ol' wise search of Google and came up with:
Might be a permissions issue. Easiest way to fix it is to run ROM Manager and have it fix permisions.
Run the command yourself in ADB:
Code:
Open terminal and
>su
$mount -a
$fix_permissions -r
The -r is optional, but necessary if you find orphaned apps (the app not found please reinstall message)
And reboot. That may help.
And it was also stated that you might have an errant widget/application causing the issue as well. That will be fun trying to figure out what it is.
And.. from my non-dev/non-professional experience - I have checked the logs on my phone and do see a large number of warnings on the phone - but never hindered performance.
So.. 99% of the time you can probably ignore them.
But back to the FC issue - I would try doing a restore of your apps/data again (I read where you have it back down to the "core) and then run the permission script or have ROM Manager do it for you and see if it returns.
Just an update that I think the "fix permissions" thing solved most (but perhaps not all) of my issues. Thanks so much for the tip. I've been reinstalling apps in batches and it's much better, although I see it getting bogged-down bit by bit and I can't pin down what or why.
Thing is, the apps I'm installing in these later rounds/batches shouldn't be resident all the time, shouldn't be auto-loading, and don't come up in things like Startup Cleaner or Advanced Task Killer. Nor do the various process monitors I've tried seem to have the granularity/ability to catch them while they're happening.
So things are better, but I still have some issues without a suitable means to diagnose. I don't get why just having more apps installed, but not running, should affect boot time so much. Hmm...
An inability to troubleshoot certainly rains on my love-affair with Android... not that I'm jumping to another platform anytime soon, but I really want this to work well (as well as be a good salesman to friends and family who often turn to me to show off quality technology).
So a friend of mine updated his T-Mobile UK Samsung Galaxy S to the official 2.2.1 JPY firmware using Odin a few weeks ago. This went well, and is the same firmware that I've had on my unbranded SGS since December.
However, he has an interesting problem. Some of his apps (Handcent, Dolphin HD, plus a few others) seem to forget all of their settings every time the app is exited. For example, every time he goes back into Dolphin it enters the setup wizard as it it's being ran for the first time. This doesn't happen on every app, and it doesn't happen every time.
I noticed there are a couple of other threads on here with people reporting similar issues on custom ROMs (with no solution), but this is a stock ROM from samsungfirmware.com and certainly doesn't happen on my SGS, so it's not the ROM to blame.
Anyone know of a fix?
This question posted in the last few days .
jje
As I said in my post "I noticed there are a couple of other threads on here with people reporting similar issues ... (with no solution)". I wasn't being lazy and just starting another thread without doing some research first. I've read the other threads and they do not contain a solution that will work for him.
I'm assuming you're referring specifically to this thread? http://forum.xda-developers.com/showthread.php?t=992335 In my friend's case, rooting is not an option, so this solution won't work for him.
However, based on that it looks like a factory reset may fix it. If I don't come back people reading this can assume it worked.
Hello
I experimented the same issue.
Looking at some log traces event it reported some permissions errors on intestinal filesystem like database location access write errors. This can explain setting persistence trouble.
After various workaround, bypass or others kind of fallback I did a full reinstallation of filesystem including a wipe data of the system. Take care to backup application and sensible data SMS, photo...
Since all is working fine and no more problems with settings
I don't know if it's helping you.
This is just my personal experience on this same problem.
Perhaps more simple solution is possible
Regards
Gilles
Thanks. So far so good after a Factory Reset. If it were my phone I'd be looking at Logcat, etc, too, but it's a bit hard to do remotely.
It's odd how some apps saved their settings fine, but some don't.
A factory reset did fix it... for a while. But then other apps started suffering from the problem.
So I've been researching this a bit more today. Here's what I've discovered:
The problem is unique to Samsung Galaxy S phones, and appears to be only ones running 2.2.1 (but maybe 2.2. too?).
Samsung have renamed /data/data to /dbdata/databases, and shared preferences for applications are persisting in this folder even if the application is uninstalled. If you install the app again, the app becomes a different user from the one that owns the shared preferences.
For example - If you install some random application and you look at its process running with the ps command, it will show as "app_XX", where XX is some number. For our example here let's say it shows as "app_55". When it then saves its settings in /dbdata/databases the folder the settings are saved in will have owner (shown by ls -l) as "app_55" too. That's fine, and normal.
The seed of the problem is sewn when you uninstall the app. Those shared preferences are not removed. Even using the "Clear data" option before uninstalling doesn't seem to help. If you then install the app again and look at the output of ps you'll see the new app is "app_56". The shared preferences are still there from last time with owner "app_55", hence the permissions error when it tries to save its settings, as user app_56 cannot modify user app_55's files.
A factory reset obviously cures it as this, at least temporarily, as it wipes the data in /dbdata/databases.
If you're rooted, you can go into /dbdata/databases and delete the relevent folder for the application that's having the problem. It will be recreated with the correct owner next time the app saves its settings.
I didn't try chown to change the owner to the correct one, but maybe that's a way to keep the old settings and correct the problem.
Bingo. No wonder my titanium backup is not remembering the preference settings.
Titanium Backup recently enabled conversion of app databases to a new WAL format. Is this safe to do? Can any dev's shed any light on this new file type?
Sent from my DROID3 using XDA App
Avoid
This ****s me I did this on my Samsung Galaxy, it WIPED ALL SETTINGS on my phone. no warning that it is dangerous!
Had to revert back, and then restore all settings again.
I learned quickly not to do anything that hasn't been discussed and tested by these talented people with XDA. And its still not 100 percent safe even then. I noticed by the release notes for the new TB Pro that its for all 2.3 roms, recognized by sqlite3, and is supposed to be faster than the old app database file type. What I don't know is the side effects, and what effect it has on rom updates applied over the change
Droid 1 Rooted (ChevyNo1 0.9MV Kernel, LGB2.6)
Droid 3 Rooted (Stock Kernel, Custom lite De-bloat)
Settings wiped out confirmed plus MAYBE a few very destructive glitch (Unconfirmed by others):
Power button only lists one entry: Power off instead of the original three - Confirmed by bonks
Home button not working (In respect, task switcher not available) - Confirmed by 0nebukadnezar0
Search button not working - Confirmed by bonks
Android market not connecting - Confirmed and solution provided by 0nebukadnezar0
SMS wiped
Nexus S Stock ROM 2.3.4 rooted (Kernel Netarchy Nexus 1.3.7)
Added symptoms :
Lost APN settings (0nebukadnezar0 on Galaxy S)
Screen lock not working (0nebukadnezar0 on Galaxy S and bonks on Motorola Droid 3 rooted)
Facebook authentication lost (0nebukadnezar0 on Galaxy S)
Some other application's settings (0nebukadnezar0 on Galaxy S and bonks on Motorola Droid 3 rooted)
Do not run this batch until further update!
Do not use this function!
I've also been hit by this. I paid for this software and it should really have a warning that:
1. it affects all application data: I was under the impression it affects only the TB internal database
2. it converts user data of the complete device: I had thought twice if this had been clear
3. one should create an up-to-date backup first
Instead it highly praised that this is a performance improvement traded against little higher storage usage. Why shouldn't I want to enable such a feature?
Had I known the implications I would've created a full backup first and thought twice. Now I had to go back to a three day old backup. My phone was completely wiped. No error message. Still some settings were missing after restore: TB still seems not to be able to correctly restore ActiveSync settings, and all widgets were gone from my start pages.
This is extremely unsatisfactory for an app I paid for. Please, developer: Improve your warnings in an application like a backup app which handles sensible data.
I noticed it in the change log, and was like " Uhh... why, in the last 6 months, have I not heard of this new super fast database conversion before now... I better ask someone before I mess with it"
Luckily I did, I'm still running the stock rom minus vcast and a few additional bloaties removes, and have dreaded altering anything without the bootloader unlocked, as this is my second device, the first returned returned DOA. I appreciate your testimonials guys, our stories will save the devs a few headaches, and will give titanium devs some live input on the batch operation. If Pzouza or Chevy has any comments on it, the input would be welcomed, as this is the first most of us have heard of it
Droid 1 Rooted (ChevyNo1 0.9MV Kernel, LGB2.6)
Droid 3 Rooted (Stock Kernel, Custom lite De-bloat)
verkerria said:
I noticed it in the change log, and was like " Uhh... why, in the last 6 months, have I not heard of this new super fast database conversion before now... I better ask someone before I mess with it"
Luckily I did, I'm still running the stock rom minus vcast and a few additional bloaties removes, and have dreaded altering anything without the bootloader unlocked, as this is my second device, the first returned returned DOA. I appreciate your testimonials guys, our stories will save the devs a few headaches, and will give titanium devs some live input on the batch operation. If Pzouza or Chevy has any comments on it, the input would be welcomed, as this is the first most of us have heard of it
Droid 1 Rooted (ChevyNo1 0.9MV Kernel, LGB2.6)
Droid 3 Rooted (Stock Kernel, Custom lite De-bloat)
Click to expand...
Click to collapse
+1 Droid3 rooted and de-bloat via titanium
Same thing happened to me. Not very pleased. Titanium Backup usually warns against dangerous options. This batch option not having one gives a false sense of security. I'm restoring a month old nandroid backup via clockworkmod now and then hopefully restoring my TB backups.
same thing on my Galaxy S:
- home button does not work anymore
- Market "Server Error", this has been cleaned through "Clear Data" under Manage applications
- lost 3G settings, it was necessary to enter the APN configuration manually
- screen lock does not work anymore
- lost the facebook authentication
- some other apps have lost her settings
Titanium Backup DB modes
Rooted Droid 3 with TB pro
Power button only lists two entries rather than I think the three or four it had.
Home button not working
Search button not working
Screen lock not working
Some other apps have lost their settings
-> Widgets needed to be readded
-> All email accounts had to resync
What I did:
Wokeup, saw TB update, downloaded & installed, tried new feature in TB for faster databases.
Ran the "Convert DBs to Rollback Journal mode (works on all ROMs)" batch process. It completed successfully.
Ran the "Convert DBs to WAL mode (faster, slightly bigger, Android 2.3+ only)" batch process. It completed successfully.
Hit the home button, tried to open an app. Force Close. Tried a few more apps, all force closed.
Restarted.
The white animated "DROID" screen infinitely repeated itself.
Removed battery.
Powered On.
Successfully reached Home screen (ADWLauncher EX).
My fault for trying these new features without looking into it first, but I did not think they would be dangerous.
Now, are Journal mode and WAL mode the two available types of DBs. Could I just run the Rollback Journal mode to revert back? Is this safe?
Their wiki says it's safe but has anyone tried this? matrixrewriter.com/wiki/tiki-index.php?page=TB+-+Technical+FAQ&highlight=rollback%20journal
(#32 and #33)
Woah, glad I googled this before running it on my Galaxy Tab. Will avoid.
From Titanium Support:
We're truly sorry about this issue. Yes, today we discovered a terrible bug in the SGS2 stock ROM, which explains what happened. Titanium Backup has converted your databases to WAL fine, but the SGS2 stock ROM itself does not support WAL properly: instead of opening the WAL databases, it will silently erase them and then claim that the open has succeeded!
Before allowing any conversion to WAL, Titanium Backup performed a verification, which we have tested and properly fails on older ROMs. On the SGS2 though, the verification passes because the test database is fine after the conversion - well yes it's fine, but it's empty.
We have improved the WAL testing code and we will release an updated version as quickly as possible. The new version has been tested well on SGS2 and detects the problem properly (ie: it prevents conversion to WAL format). This only applies to stock ROMs though, as CyanogenMod (for example) does not contain the buggy Samsung code and fully supports WAL without issues.
If you have no backups of the erased databases, we're very sorry to confirm that it cannot be recovered, unfortunately. Please accept our deepest apologies for this issue. If you would like a refund, please let us know because we stand behind our product.
Click to expand...
Click to collapse
I converted back to journal mode but this did not fix any of my issues. I'm guessing that the lockscreen, home button, and search buttons had some kind of association to a database from the manufacture install which I don't know how to recover. Any ideas?
Bad Titanium Pro!
GldRush98 said:
Woah, glad I googled this before running it on my Galaxy Tab. Will avoid.
Click to expand...
Click to collapse
ditto to that, I was just about to hit that button and thought maybe I should do some googling...
All, the standard rule to all root users, is to do full nandroid backups before making any serious changes to your phone. changing database formats is a major change. You should have all done a full nandroid, then a full tb backup. That's the main rule of thumb if you start down the road to root. Anytime you play with root focused apps, you're playing with fire. At some point we all get burned. I have plenty of times, but always get back with a nand restore. we all learn eventually. I know I've messed up a few phones this way, but that's the joy of going the root route. Its all in fun.
I wasn't aware of this feature and definitely will be trying it now that its been posted.
Sent from my DROID3 using XDA App
Ok, after doing a full nandbackup, and TB backup of User Apps. I did successfully migrate all the DBs to WAL format. I then rebooted right into CWM, formated the cache to avoid any old data crap, rebooted back into normal phone. Ran my most common apps and had no issues I've got 217 user apps on my phone, I think I ran 20 of the core apps I use. no issues in the first 1 hour. I did confirm all the previously posted issues and experience none of them within the first hour of testing. This is probably due to me not messing with the system apps. I'll test that next for the fun of it and report back. But, I can safely say, in my case, I had no issues with this conversion of "user" apps.
Power button only lists two entries rather than I think the three or four it had.
Home button not working
Search button not working
Screen lock not working
Some other apps have lost their settings
Widgets needed to be readded
All email accounts had to resync
Stay tuned for round 2 of testing
---------- Post added at 10:52 PM ---------- Previous post was at 10:39 PM ----------
Ok Round 2 WAL conversion and testing completed.
Everything works perfectly. Not sure why everyone else is having issues. I would say anyone else should be free to do the conversion. Again, this is how I did mine. I did a full nandbackup, in case i screwed things up and messed my phone up. Did a full TB backup of system apps. Then did the conversion to the system apps. Immediately after rebooted into CWM. I formatted the cache. Rebooted, let my phone load up. I did notice during the first 5-10 seconds of the loading home apps and widgets half of the widgets gave a widget error, but I was patient enough to let the phone get fully loaded. After that all widgets did start back up just fine. I tested all reported bugs and errors everyone else had, and I had no issues with anything. I'll keep an eye on things for the next few days. I'm a heavy, nerdy user of my phone, and am constantly tweaking it so i'll know if I screwed something up and report back.
Widgets all loaded fine after reboot.
Search works as it should
Long Press Power button pulls up standard 4 options.
Home works fine
Long press home pulls up all recent items (do keep in mind if you reboot there are no recent items so you have to go into apps for it to tell you recent items)
Lockscreen works as it should.
I would say this WAL conversion for both System and User apps works just fine. But, that is only in my case apparently. I am using Steel Droid 3 (v1).
Good luck to the rest of you. Oh, and I have no affiliation to TB, but I must admit that its one of my most used Root apps since it helps me unscrew myself when I do fudge things up. It is just so much faster to fix mistakes than a full nandrestore. Albeit the NandRestore is my Plan B fix it solution TB is plan A.
Where exactly is this option? I havent seen anything and just redid apps for data
WAL DB Conversion Success
I followed Izeltokatl's information by performing a full backup with Titanium Backup and ClockWorkMod via ROM manager, then updating the system and app DBs to WAL via TB, then immediately booting into recovery and wiping the cache.
I'm happy to report complete success updating my Ideos U8150 running Gingerbread 2.3.7 to WAL DB without any problems.
Even after wiping cache, the quick search function was force closing, so I just restored it from TiBu.
So what are real benefits of Wal or Rollback Journal databases of android. Is it really faster? Are there any reasons to make Rollback journal conversion on unsupported roms?
Has anybody tested it?
Some good reading.
http://www.sqlite.org/draft/wal.html
The ROM I was running was using SQLite version 3.7.2, and I unchecked 'force system SQLite' in preferences and it upgraded to the TiBu optimized version which is quite a bit newer. Seems to speed things up slightly if you convert to WAL.
I use note 7000b 2.3.5dxkk1
rooted
I found this problem that app I installed in sdcard
their icon on home sceeen sometime they disappear
they change to gray clour and cant open it.
Hv to restart it and will be normal its happen several time
so where this problem might come from
anyone hv this before?
Thanks
Oh and sometime my gallery is empty too
u think is might comefrom exsdcard(Sandisk class6 32g)
I have the exact same issue. I guess it's titanium backup related. Have you ever get your apps frozen via titanium backup or moved them to sdcard using titanium backup?
Rebooting the device once solved my problem for good. I never had such issue ever since I rebooted.
Sent from my GT-N7000 using xda premium
captainhakan said:
I have the exact same issue. I guess it's titanium backup related. Have you ever get your apps frozen via titanium backup or moved them to sdcard using titanium backup?
Rebooting the device once solved my problem for good. I never had such issue ever since I rebooted.
Sent from my GT-N7000 using xda premium
Click to expand...
Click to collapse
I never used titaniumbackup for anything yet
only back up once for game never restore.
So I glad atleast the problem might not came from sdcard
which I just bought it.
So May be hv to wait for ICS. Its may help my issue.
Thanks a lot.
captainhakan said:
I have the exact same issue. I guess it's titanium backup related. Have you ever get your apps frozen via titanium backup or moved them to sdcard using titanium backup?
Rebooting the device once solved my problem for good. I never had such issue ever since I rebooted.
Sent from my GT-N7000 using xda premium
Click to expand...
Click to collapse
This has been happening to me too and I'm on an unrooted stock ROM with a 16-gb Class 4 Transcend micro SDHC.
don't install too many apps to sd and you won't have this problem.
known issue with sd card. but none of the devs fix the problem
Let me give it to Samsung Gnote ... i never used to install so much apps on any of my previous devices. So much built in memory is provacating
darrensnake said:
don't install too many apps to sd and you won't have this problem.
known issue with sd card. but none of the devs fix the problem
Click to expand...
Click to collapse
Actually I install only a few app
and couple game in sd card mostly,
I only kept my file in it.
I hv change my sd class4 to class6 once
I though its too slow but problem still there
Fast Boot option may be the culprit
This is actually a long-standing problem in Android OS, going back at least two years (donkey's years in this technology!)
Something about the interaction of the OS and an sdcard formated for holding apps creates odd behaviours.
Lots of complicated suggestions have been made, including reformatting sdcard, reinstalling ROMs, changing launchers (the one suggested here) and such.
None of these approaches seems really to solve the problem even in most cases.
This is the first I have read about app overload on an sdcard being a "known issue" (known to whom? XDA?), although I can well believe the possibility that it COULD be true. Still... Just where might the cutoff point be? Also, isn't an active app loaded into memory, so this would be the real bottleneck?
What seems to be working for me (at least for the last week or so) is the following very simple tweak.
CUT TO THE SOLUTION BELOW -- SEARCH FOR ////
Some (not all) of my apps moved to SD (all by Titanium Backup Pro) have begun to disappear and (sometimes) reappear without warning after I began to add and delete large Virtual Machines created in QEMU from my 16GB SanDisc class 10 microSD card on my HTC Droid Incredible running rooted stock Verizon Android Froyo 2.2.3. I know this thread is far from my phone's "home base", but from what I can tell this problem with disappearing apps located on an sdcard is NOT determined by hardware or even Android version.
I also happen to use LauncherPro by Federico Carnales instead of the built-in HTC Sense launcher. I noted elsewhere on XDA that a user had suggested that because at least some (maybe all) launchers start before the SD Card that this may be a problem, especially if changes are made to the sdcard that the launcher did not perform, or was not active during their performance by other apps such as Titanium Backup. That fits my situation, because I unmounted the SD, physically removed it to a PC, and added/deleted large VM files to save (lots) of time. No problems of this sort before I did this, so there must be some connection.
I noted that other users have tried reformatting SD, substituting different brands of SD, using newer/older SD etc. None of these reliably helped. So I skipped these options.
//// The (simple!) solution I tried that SEEMS to work (only time will tell!) is buried in the main Android Settings (accessed from the Menu button while in Home screen). Under "Applications" there is a setting "Fast Boot" that I checked long ago and forgot about (it seemed like a good thing to do at the time). The text warns "Turn off to use some Market apps" (that shows the age of my 2-yr old used phone and Android OS -- ohmygosh!-- because it refers to Market rather than Google Play Store!) Anyway, I unchecked the option and rebooted the phone.
Yes, it took a bit longer to boot (maybe a whole minute!), but after waiting about another minute ALL my home screen apps had normal icons and loaded properly. Titanium Backup Pro batch scenarios confirmed there were no apps in a forced uninstalled state (i.e. I had not done the deed, the system somehow had done it or at least rendered the apps "invisible" to Titanium, which decided they needed reinstallation).
The only odd behaviour was that auto brightness was turned off after I unchecked Fast Boot and rebooted. Going into Android Settings > Display and rechecking "auto brightness" took care of that. No other oddities or strange behaviours thus far (but it has only been about an hour).
I will report anything further on this thread only (Samsung Fascinate > Fascinate Q&A > What just happend? apps on sdcard) if anything else requires reporting. Silence implies success!
link: http://forum.xda-developers.com/showthread.php?t=1873670
(I am copying this post to other relevant threads, but will not post anything further elsewhere -- only there. This is a bit arbitrary (especially now that the chosen thread no longer is the most recent active one on this topic), but I hope this approach pleases the XDA sysops/admins) :angel:
So after some great help by gregbradley and others, I have a rooted T and now have an OTA 195 update.
However I have a couple of questions (apart from my continued quest to find a way to get the phone to save camera output in less compressed fashion.
1) Is it usual for mediaserver to be the 2nd great drain on battery after the screen and ahead of android system?
(there appear to be many web discussions on this, but I could not find a definitive answer. Mine has always been like this even before I tinkered with it, or before I put the sim in (I didn't put the sim in until after I had rooted and updated. I do not have an SD card in there yet (64Gb on order) and I have not added any new pics or movies to the stock provided ones.
2) Can you change where apps are installed? Can this be changed for Google Play apps (like xda) Is the default to install to "phone memory" rather than "internal storage". Given that "phone memory" is only ~ 2Gb, it would be good to install to "internal storage"
3) Are apps on the home screens (eg Walkman) always running, even when not in use (the walkman example is the app 4x1 icons wide and has basic controls on it)?
Many thanks as always!
icstm
some clarification I should have added yesterday...
1) quite simply I would be keen to know what type of apps call on the mediaserver process
2) I know that from the "apps" in settings" some apps can be moved, but that appears limited and no default can be set
3) when I say apps, I mean widgets and the like, not the simply shortcut icons
icstm said:
some clarification I should have added yesterday...
1) quite simply I would be keen to know what type of apps call on the mediaserver process
2) I know that from the "apps" in settings" some apps can be moved, but that appears limited and no default can be set
3) when I say apps, I mean widgets and the like, not the simply shortcut icons
Click to expand...
Click to collapse
1) Anything that needs to scan the sdcards for contents will call on the media server. After a fresh flash many apps will be collating their cache so the mediaserver may have a high battery drain, you should never worry about battery drain untill you have run a ROm for at least 3-4 days to let it settle
2) Yes, use apps such as link2sd or app2sd, free in the market. However I have not yet felt the need to do this with a 16gb internal memory
3) Thos e widgets are just shortcuts, e.g. I have a weather app set to refresh every 2 hours...it will be woring in the background whether or not the homescreen widget is on the homescreen or not.
However, do not worry about task killers, since android 2.1 the best task killer is the one that comes with the OS. The only other exception is if you install init.d scripts and supercharge scripts etc, but you may want to leave that for a bit and get used to the phone first.
So I am on the xda app, much better way to view the site than mobile browser .
However, I cannot see what you wrote when I reply.
But it relates to your last point on making customisations. And not just keyboard which prefers US spellings over UK ones .
I am thinking of tinkering with the OS files as I am very upset with the compression of photos. So I am keen by what you say just below number 3.
Sent from my LT30p using xda app-developers app
AW: [Q] Couple of days in - a couple of Qs...
Change your keyboard or even better your whole phone to UK in language and keyboard setting and it'll propose BE instead of USE.
Greg is correct, the media server goes nuts the first two to three days after (re)flashing or taking up a device. You can improve the situation by keeping your folder structure clean and neat and trash out left over files, old garbage and file system junk.
Thanks for your posts in both threads.
As for mediaserver, yes all is quiet now.
Not sure about which system files to delete at this stage, but I sure do keep a neat folder structure for my content.