Related
I am on CM 4.0.2. All my apps seem to work fine, but there seems to be some slight hesitation when lifting the app drawer - just slightly choppy. I saw a lot about the fix_permissions in console, does this address that? Or is that solely for apps that are not working? I am under the impression it does NOT help this.... but wanted to be certain. Does this mean I perhaps need to adjust my SD partitions?
Should one run that code even if all of the apps appear to be working correctly?
I did not see steps for running the script in all of the posts I saw... any help on this?
This will not help. You fix permissions to possibly help with FC.
Choppiness comes from not enough memory. Check what's running in the background and adjust accordingly. Check your comcache settings, adjust. Check your swap settings, adjust. Be advised though... there's only so much you can do, we are working with very limited hardware here.
FYI... I would really look into what's running in the background first. I run cm 4.02 with default comcache, no swapper. I have 7 widgets and it only stutters occasionaly, I barely notice. I would REALLY look into your backgrouds. Also, don't forget about GPS/Wireless location issue, that may be causing it too.
Good luck
Interesting... i use advanced task killer prior to rooting and when apps were killed i was around 55MB. Now, after root i can only get around 41MB. I never understood what made this lower... i assumed it was stuff cyan added to make his rom open. I do not use many widgets (3 maybe) and generally leave wifi and gps off.
Thoughts?
Hi fellow XDA'rs.
As most you probably know, the way android and most os's works, every time you start up your device some/many apps startup with it.
This certainly bogs things down on startup but also in the long run when they stay resident idling in mem.
Android allows apps to register for events that are then started whenever triggered.
For example, on my phone prior to getting this app, everytime I pressed the camera button Camera, SMS commander (WTF), ChompSMS (WTFF), and Snaphotopro ran code. I could even see it happening in a task manager.
Sometimes apps stay in memory indefinitely after doing something irrelevant to their function like clicking camera/downloading something .
So I disabled everything except my main camera and everything still works the same, but ONLY SnapPhoto runs code and uses memory.
The real place i think autostarts shines is that it not only allows you to selectively disable what starts on boot, but also control what happens on every event.
It's on the market for like 98cents or some crap, and I REALLY think we should support the dev for this top-notch app.
It does way more for me than overclocking etc.. and i'm not advertising LOL.
What do you guys think??
Stock Apps that May Be Unsafe To Disable
Messaging (Disabling Is Known To Hinder SMS-Retrieval)
Google Talk (Disabling Is Known To Cause Trouble with the Market)
Stock Apps That Appears to be Safe to Disable
Maps (Disabled on startup without issues)
Clock (Disabled on start without any issues thus far)
Camera (Disabled Stock camera from running when camera button is pressed without issue)
Pico TTS (A text-to-speech thing that runs code every time an app is installed Disabled without issue)
MP3 Store (Runs code whenever an app is replaced, disabled, no issues)
i used it before, but i noticed that if you disable some apps on startup, it will make those apps not function anymore. for example, i remember i disabled the default message app and a bunch of other "normal" apps, and then i would not get any SMS anymore or some of my apps stopped loading. also even after you uninstall the app, it would not return to normal. they listed this as a bug for the version i tried so i couldnt restore the apps i disabled.
right now i just use advance task manager and put the one click widget on my home screen. so after every event i get in the habit of just clickin that widget and it iwll close all apps. and everything works fine.
That's true. Disabling messaging will prevent you from getting sms's even if you have chompsms, chomp's main functionality is as a front-end to the messaging app, not the core. This is not the apps fault
The reason I made this post is so we could compile a list of apps that are okay to disable and aren't. I forget to mention that in the OP .
I will edit the first post with the list but I need input from the community.
So far..
Messaging (Disabling Is Known To Hinder SMS-Retrieval)
Google Talk (Disabling Is Known To Cause Trouble with the Market)
For the most part disabling stock apps isn't the brightest idea.
Autostarts will warn you when you try to disable a stock component.
Also you can view only non-stock apps, if you don't want to mess with the settings.
Some can be disabled without any apparent trouble.
In my case..
Maps (Disabled on startup without issues)
Clock (Disabled on start without any issues thus far)
Camera (Disabled Stock camera from running when camera button is pressed without issue)
Pico TTS (A text-to-speech thing that runs code every time an app is installed Disabled without issue)
MP3 Store (Runs code whenever an app is replaced, disabled, no issues)
There are several more instances of the same apps that are disabled.
So far no FC's or problems. I've reduced the amount of times I need to end all apps by about 90%
Feel free to help add to the list!
I don't disable any stock apps as they seem to die by themselves after a while. Meanwhile I disable pretty much all 3rd party apps (except things like Sim Checker).
This app is amazing!
By the way, if you disable "Widget updating" it also removes unwanted widgets (I tend not to use any).
Glad it's working well for ya Karolis.
Thanks for the tip!
I havent actually tried it, but i'll remember that if I ever have too many widgets in the list.
Another tip is to check out Menu -> View.
You can enable the unknown's and have more options to disable
Is anyone else annoyed by devs who don't allow their apps to be purchased through your T-Mobile account? Something about putting $0.99 on my credit card annoys me. No biggie, but it would be nice if that option was available for this app.
TeeJay3800 said:
Is anyone else annoyed by devs who don't allow their apps to be purchased through your T-Mobile account? Something about putting $0.99 on my credit card annoys me. No biggie, but it would be nice if that option was available for this app.
Click to expand...
Click to collapse
Well what can we do except take it
I use Startup Auditor, works pretty well, compared to Autostarts. I also believe it doesn't list anything that would damage your bootup.
tehseano said:
I use Startup Auditor, works pretty well, compared to Autostarts. I also believe it doesn't list anything that would damage your bootup.
Click to expand...
Click to collapse
I hadn't heard of Startup Auditor either, but after reading about it, it seems a little more appealing than Autostarts. Especially the part about not disabling anything important from starting. Thanks!
Startup auditor isn't bad.
It doesn't have even a third of the options as autostarts though.
I tried it and although the GUI was nice, and it worked, the lack of choices made me uninstall it in a matter of minutes.
Also, if you're worried about messing up your phone with autostarts just go to Menu -> View -> Hide System Apps and its pretty much the same thing as startup auditor.
I just purchased Startup Auditor and it seems like a nice app. However, I disabled a few apps and then rebooted. When the reboot finished, some of the apps that I had just disabled were still running! I've e-mailed the dev and will post if I get a response. Has anyone else experienced this with Startup Auditor or any other startup app?
I've been using Autostarts for a while and I really notice the difference on boot up time. Before Autostarts it would take forever to boot up the system, then it would be super sluggish. Now since it doesn't start nearly half the apps on boot, it's much faster.
Some apps I question on why it's doing what it's doing. Like Tunewiki for instance. Why does it need to start when an application is replaced or removed? Cleared those out and everything is much speedier!
A lot of them are triggered by strange things.
Like you said, tunewiki when adding or replacing an app.
I think this is their way of staying in the background, which speeds up opening tunewiki but at the cost of slowing everything else down.
I hate developers that do this..
How does the system determine which apps to run at boot?
Whenever i try to disable the amazon mp3 autostart the program tells me to wait and gets stuck on the please wait screen... Any clue if this is normal operation?
amazon mp3 does not seem to want to be disabled.
edit: i think i figured out the problem with amazon mp3. you have to disable it in two places, once in the after startup but also in the connectivity changed section. also i was having trouble with other programs but i forgot i those had widgets. i think for apps that have widgets will cause those apps to load on start up. if you want to disable them you have to do so in the widgets section. just dont do it for widgets you actually have in use.
Does this app not work on latest superd? i get fc everytime on g1.
Anyone know where there are two (2) Messanger apps AND two (2) Handcent apps listed for after startup?
Seems like I should be able to disable messanger, but from these posts perhaps not.... can I disable handcent with no issues... seems like a text received would trigger it to open with no problems.
Why (and can I stop) is Voice Dialer involved with all changes to applications (installed/removed)?
s15274n said:
Anyone know where there are two (2) Messanger apps AND two (2) Handcent apps listed for after startup?
Seems like I should be able to disable messanger, but from these posts perhaps not.... can I disable handcent with no issues... seems like a text received would trigger it to open with no problems.
Why (and can I stop) is Voice Dialer involved with all changes to applications (installed/removed)?
Click to expand...
Click to collapse
I was wondering this too. Maybe it starts to read the app names so it can "read" the filename so if you call it through Voice Search it knows what app to call up. Not sure.
Imho, this app is absolutely amazing.
I had the problem, that although i am using Handcent only, still every text was shown as new in the message application as well (and the icon on the homescreen shows one new message). Now i have removed message completely - only my handcent widget shows any test infos
Besides that, i could disable a lot of useless or at least strange applications starts triggered by certain events.
In this point of view, it's very useful, for Galaxy S as well!
Hey all,
I installed Super Rooter shortly before it became SRE, I based it on the JH3 firmware. With it is SLA4 and I used the packaged lag-fix and bloatware remover. It was going great for a while, but recently things are getting screwy. Things that are happening once in a while:
I click home, and the home screen is entirely blank and all the icons and apps have to re-load
When installing programs, everything is horribly slow
Unlocking the phone sometimes is very delayed
Is anyone else experiencing any of these problems? Also, I have a lot of apps installed. Always running are: SmartBar, SystemPanel and Tasker.
Let me know if I left out any important information.
Thanks!
Mine was like this for a while. Problem went away when I rebooted. This was on stock firmware with RyanZA lagfix only.
I'm having the same problem with the Lagfix installed. I tried to uninstall it to see if that was the problem, but it messed up and screwed up my data. I have to reinstall a ROM now.
i have noticed the exact same lags....the one where everything has to reload is especially annoying. happens every once in awhile when i open the app drawer too.
surprisingly enough, i am also running jh3 with super rooter (before it became sre)...i was excited because i came home today expecting to do a jh7 flash with the latest SRE, and then i see unhelpful updated his kernal, and DG is going to take a few days and update the whole sre program to either a full blown rom or add many options for flashing.
Sounds like a your running out of RAM, not filesystem lag issues.
Get a task killer, configure it to ignore the apps/widgets you dont want it to kill. Add the task killers "Kill All" widget to your default home screen and hit the kill all widget every time you back out of an application you are done using.
When your captivate is unable to keep more than 100-140MB of RAM free its time for a reboot. If you can never maintain this much free RAM even after a fresh reboot, cut down to 2 or 3 home screens and and less widgets.
With ADW.Launcher, 2 home screens and 3 Widgets total I never fall under 200MB of RAM free (Rooted)
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.