For the Olleh ROM (2.3), the Gallery process --com.cooliris.media keeps loading automatically despite manually killing it.
I am so frustrated as this process seems to chew up the DS5's battery.
There seems to be 2 processes related: The usual Android Gallery process --com.cooliris.media, and one that looks like a OEM provided one: Gallery version Stage_1.5.1_KT-113.
Please help me: my phone's not rooted (long story...), and I am looking for other ways to stop these 2 apps from loading / running up all the time.
Any advice, any kind of apps recommendation that I can use to pin these 2 processes down is most appreciated.
Thanks!
Root. It's the only way you'll be able to kill the process permanently, since you can then remove the offending app. However, you'd be better off rooting and installing a custom ROM such as DSC that fixes many of the bugs found in the Olleh KT ROM.
Related
Alright guys, I'm in need of some help.
I've been flashing MIUI on my Fascinate for months now and recently I've run into a problem. On RickS' 1.12.9 I'm getting a lot of FCs. About 24-48 hours after flashing and setting up my phone I get a notification at boot that every GApp along with TB, Facebook, Script Manager have "stopped unexpectedly" and need to be force closed. My flash process is as follows:
1) ODIN either DL09 or EH03
2) ODIN CWM4
3) 3 finger boot to CWM and flash RickS 1.12.9
4) Everything is fine up to here
5) TB - Restore missing user apps (just apps, not data)
6) Set up Supercharger script (update9 RC5 test 2), Voltage Control OC/UV, Glitch kernel leakage/screen state
7) Reboot
8) Wait about a day and a couple of reboots later for the force close party to start.
Has anyone run into a similar problem? I've tried a few solutions (i.e. mixing up my flash routine, fix permissions...)
Thanks,
EJ
EDIT: Also, whenever I flash weblexa's builds after step 7 I get stuck in a bootloop. I'm going to try to just flash it and reboot to see if I don't get stuck (which, if I don't probably means that something I'm doing while setting up my apps and such is the cause of the problems).
.Ejekt said:
Alright guys, I'm in need of some help.
I've been flashing MIUI on my Fascinate for months now and recently I've run into a problem. On RickS' 1.12.9 I'm getting a lot of FCs. About 24-48 hours after flashing and setting up my phone I get a notification at boot that every GApp along with TB, Facebook, Script Manager have "stopped unexpectedly" and need to be force closed. My flash process is as follows:
1) ODIN either DL09 or EH03
2) ODIN CWM4
3) 3 finger boot to CWM and flash RickS 1.12.9
4) Everything is fine up to here
5) TB - Restore missing user apps (just apps, not data)
6) Set up Supercharger script (update9 RC5 test 2), Voltage Control OC/UV, Glitch kernel leakage/screen state
7) Reboot
8) Wait about a day and a couple of reboots later for the force close party to start.
Has anyone run into a similar problem? I've tried a few solutions (i.e. mixing up my flash routine, fix permissions...)
Thanks,
EJ
EDIT: Also, whenever I flash weblexa's builds after step 7 I get stuck in a bootloop. I'm going to try to just flash it and reboot to see if I don't get stuck (which, if I don't probably means that something I'm doing while setting up my apps and such is the cause of the problems).
Click to expand...
Click to collapse
I have had this same issue, and for months it drove me nuts cause I couldn't figure out the problem.
It didn't happen so much with all google apps, mainly the market, but I did get it on others.
What used to work for the market, set your language in the phone settings. Not market settings, the phone. I set mine to English (United States) and I didn't get a FC on market since.
With other google apps, or other apps in general there are a couple a things you can try.
1. If you changed any permissions, i.e. disabled apps from loading on boot, turn them back on 1 at a time. When I disable Google Talk from loading.. I get FC's.
2. Try a clearing data/cache for the app and re-installing over the app... or clearing data/cache and uninstall... and re-install.
3. Have you changed your screen DPI? Below 190ish causes problems for me, like if I dial a number it FC's.
There is a couple more, I just got out of class and can't think of em for the life of me. I will post when it comes to me.
Hope this helps!
Maniac
MrManiacNF said:
I have had this same issue, and for months it drove me nuts cause I couldn't figure out the problem.
It didn't happen so much with all google apps, mainly the market, but I did get it on others.
What used to work for the market, set your language in the phone settings. Not market settings, the phone. I set mine to English (United States) and I didn't get a FC on market since.
With other google apps, or other apps in general there are a couple a things you can try.
1. If you changed any permissions, i.e. disabled apps from loading on boot, turn them back on 1 at a time. When I disable Google Talk from loading.. I get FC's.
2. Try a clearing data/cache for the app and re-installing over the app... or clearing data/cache and uninstall... and re-install.
3. Have you changed your screen DPI? Below 190ish causes problems for me, like if I dial a number it FC's.
There is a couple more, I just got out of class and can't think of em for the life of me. I will post when it comes to me.
Hope this helps!
Maniac
Click to expand...
Click to collapse
Thanks for the quick reply!
1) No permissions were changed.
2) I tried wiping davik/cache. As for the individual apps, the vast majority of the ones that are FCing are system apps; uninstalling isn't exactly an option unless I just remove them from the rom.
3) DPI hasn't been touched.
-EJ
I would be willing to bet you have alot of apps installed and your datadata folder is full. There is a thread on rootzwiki on how to fix this if uninstalling or moving apps to sd is not an option for you.
On my Galaxy Tab 10.1 running 'In Paris V4' with preshoot's kernel I have the following problem:
Android media process hogs CPU (47%, which means 100% for one thread on this dual core device).
The device was running fine for a few months, so the problem is not the ROM/kernel but was caused by something else later on.
I would like to fix this problem (without reformatting/reflashing the whole ROM). If there is no easy solution I just want to disable it, but could not figure out how.
Killing the process helps for some time, but after some minutes/hours the process is back. I tried 'pm disable com.android.providers.media' as well as 'pm disable com.android.providers.media/com.android.media.MediaScannerReceiver' -- both with no result (it helps for a few minutes but then the process is back again!).
I don't know how/where this process is started so that I can make a modification there to disable it or which package I should delete to get rid of the process.
Any help/suggestions are appreciated.
This obviously seems to be the wrong board I am posting that supposedly simple question in -- could somebody please point me in the right direction and I will ask again in a more appropriate board.
I'd say the board is the right one ... but at least I can't help you here, as I don't know the answer .
My only advice would be to flash a newer ROM, isn't inParis kinda "outdated"? I think android.media has something to do with connecting USB devices to the tab, since it's the thing that crashes on ICS KANGs when you plug out your USB stick ... but that's all I can help you with (if it's any help)
mrmagmrmag said:
On my Galaxy Tab 10.1 running 'In Paris V4' with preshoot's kernel I have the following problem:
Android media process hogs CPU (47%, which means 100% for one thread on this dual core device).
The device was running fine for a few months, so the problem is not the ROM/kernel but was caused by something else later on.
I would like to fix this problem (without reformatting/reflashing the whole ROM). If there is no easy solution I just want to disable it, but could not figure out how.
Killing the process helps for some time, but after some minutes/hours the process is back. I tried 'pm disable com.android.providers.media' as well as 'pm disable com.android.providers.media/com.android.media.MediaScannerReceiver' -- both with no result (it helps for a few minutes but then the process is back again!).
I don't know how/where this process is started so that I can make a modification there to disable it or which package I should delete to get rid of the process.
Any help/suggestions are appreciated.
Click to expand...
Click to collapse
Freeze the app with Titanium Backup or use this specific purpose app from the market
https://market.android.com/details?id=com.addz.mediascannerroot
Worked for me
mrmagmrmag said:
On my Galaxy Tab 10.1 running 'In Paris V4' with preshoot's kernel I have the following problem:
Android media process hogs CPU (47%, which means 100% for one thread on this dual core device).
The device was running fine for a few months, so the problem is not the ROM/kernel but was caused by something else later on.
I would like to fix this problem (without reformatting/reflashing the whole ROM). If there is no easy solution I just want to disable it, but could not figure out how.
Killing the process helps for some time, but after some minutes/hours the process is back. I tried 'pm disable com.android.providers.media' as well as 'pm disable com.android.providers.media/com.android.media.MediaScannerReceiver' -- both with no result (it helps for a few minutes but then the process is back again!).
I don't know how/where this process is started so that I can make a modification there to disable it or which package I should delete to get rid of the process.
Any help/suggestions are appreciated.
Click to expand...
Click to collapse
search pershoot's thread... Or check his website... it's there...
@slack04
Thanks a lot -- I used this solution:
http://forum.xda-developers.com/showthread.php?t=1258302
to automatically kill the process once it starts running. No real solution, but it helps until I manage to update the tab to ICS.
mrmagmrmag said:
@slack04
Thanks a lot -- I used this solution:
http://forum.xda-developers.com/showthread.php?t=1258302
to automatically kill the process once it starts running. No real solution, but it helps until I manage to update the tab to ICS.
Click to expand...
Click to collapse
Honestly, I was going to say that you'll spend less time doing the ICS update than looking for this; especially on that ROM (great ROM.... 6 months ago...). I'd suggest go with the last milestone from Romann.
mrmagmrmag said:
@slack04
Thanks a lot -- I used this solution:
http://forum.xda-developers.com/showthread.php?t=1258302
to automatically kill the process once it starts running. No real solution, but it helps until I manage to update the tab to ICS.
Click to expand...
Click to collapse
I would check your media files... delete them or put .nomedia file in all those places.
Next thing to try is to clean dalvik cache.
Thanks -- tried to flash latest Milestone and b26 releases. Unfortunately VPN is not working and I can only download apps via marked when connected to a VPN (even if this does not change my IP as I often just connect to my Router). So -- until VPN is supported with any ICS ROM I am stuck with my old In Paris 4 (with pershoot kernel to mount SMB shares via CIFS).
mrmagmrmag said:
Thanks -- tried to flash latest Milestone and b26 releases. Unfortunately VPN is not working and I can only download apps via marked when connected to a VPN (even if this does not change my IP as I often just connect to my Router). So -- until VPN is supported with any ICS ROM I am stuck with my old In Paris 4 (with pershoot kernel to mount SMB shares via CIFS).
Click to expand...
Click to collapse
I can understand if you'd just rather wait because of having to bother with reinstalling every thing, but it looks like you can change ROMs quickly. So why not goto Task14 while you wait for ICS?
There might be device issue I'm not aware of also, so just wondering.
If you can read this, thank the person that taught you how.
Hi,
I was gladly using CM7 for a month now but now these things started to bother me:
android.process.acore stops unexpectedly. (very frequent)
google processes stop unexpectedly. Viber, Tango contacts do not show up.
when I read mails in Gmail app, unread ticker still remains.
lower video playback compared to stock firmware.
no radio.
Now my plan is to revert back to stock firmware ONLY keeping root privileges.
My questions are:
1) Which firmware should I select? (there are tens of different firmwares for different regions) Does it matter which one I choose?
2) When I flash the stock firmware, does the kernel remain the same? Or will it be replaced with the kernel inside the stock firmware?
3) When I flash the stock firmware, do the root privileges remain?
4) Which kernel gives the best performance with the stock firmware? I guess CF-Root and SiyahKernel are some of the best options. Which one do you suggest?
Thanks a lot!
All answers to be found in the various stickies/FAQs that you're going to discover when you use the "search" function. If that simple task is beyond you, check the links in my sig.
I've done that but it's not easy for a newbie to extract what you need from those posts.
plus, I was hoping for a solution to
android.process.acore stops unexpectedly. (very frequent)
google processes stop unexpectedly. Viber, Tango contacts do not show up.
ksoze11 said:
I've done that but it's not easy for a newbie to extract what you need from those posts.
plus, I was hoping for a solution to
android.process.acore stops unexpectedly. (very frequent)
google processes stop unexpectedly. Viber, Tango contacts do not show up.
Click to expand...
Click to collapse
It's easy enough, just takes time. But what you read and learn will be for your benefit in the future.
Never used CM7, but flashing a stock firmware - as you want to do - is probably the best solution for your FCs.
I'll start you off - I'd use XXL1 or LA4 firmware and CF root if I were you. The rest is up to you
ksoze11 said:
I've done that but it's not easy for a newbie to extract what you need from those posts.
plus, I was hoping for a solution to
android.process.acore stops unexpectedly. (very frequent)
google processes stop unexpectedly. Viber, Tango contacts do not show up.
Click to expand...
Click to collapse
Solution don't use beta firmware stick with stock .
[Q] Root for original firmware
Hi,
I was gladly using CM7 for a month now but now these things started to bother me:
android.process.acore stops unexpectedly. (very frequent)
google processes stop unexpectedly. Viber, Tango contacts do not show up.
when I read mails in Gmail app, unread ticker still remains.
lower video playback compared to stock firmware.
no radio.
Now my plan is to revert back to stock firmware ONLY keeping root privileges.
My questions are:
1) Which firmware should I select? (there are tens of different firmwares for different regions) Does it matter which one I choose?
its your choice alone .
2) When I flash the stock firmware, does the kernel remain the same
NO
? Or will it be replaced with the kernel inside the stock firmware?
YES
3) When I flash the stock firmware, do the root privileges remain?
NO
4) Which kernel gives the best performance with the stock firmware? I guess CF-Root and SiyahKernel are some of the best options. Which one do you suggest?
None its up to the user to try them .
jje
Thanks alot! I've found Gingermod, its quite cool, nearly stock excluding all the ****ty Samsung apps.
Then I've installed siyah kernel on top of it.
Cheers!
Sent from my GT-I9100 using XDA App
Hi,
From my own experience, Gingermod is a good choice, just take care to one point Siyah on top of Gingermod will prevent you from using the OTA module of Gingermod... This is not a major issue but always good to know
Cheers
I've updated to ICS via Mobile Odin, I tried Polish LPQ and now I'm on 3UK which I'm very happy with and I'll use it as my daily.
I've removed all the normal bloatware via Titanium, eg Weather/News/Games apps.
Is there a list of Apps/Services that are safe to remove from SGS2 ICS and an explination of what those apps do, eg MapServicesSamsung or the 2 Software updates ?
Thank you
Dmonty
This thread might be of help.
There's this big topic; at the end you'll find some ICS-specific discussions.
Thanks for the link guys, I'll have a look through there. Originally I wrote that off as I thought it was for GB..
Cheers
Dmonty
I don't think you'll find too many apps in ICS that weren't in GB. Obviously the framework is different, but you only need to be especially careful with removing system apps (as Vaxxi said, there's a bit on ICS in that thread).
Frankly, I wouldn't remove anything when it's just as easy to freeze apps & have exactly the same effect as removing them, but with the safety of simply unfreezing them if you run into trouble. Obviously if you remove a system app & you run into problems you're in strife unless you have a backup.
Just my opinion FWIW tho.
Can anyone tell if there is a quick and easy fix to call lag - force incallui to memory or something in stock Sony JB ROM? I know in some 4.4 AOSP roms it is fixed, but do you know how can I interpret it in stock rom?
There's xposed module called 'App settings' that supposedly let's you lock certain apps into memory (along other features), but it doesn't seem to work. Any help appreciated
Would love a fix for the Xperia U to, but I'm afraid that the stock roms will never get a decent Phone. Devs have gone a long way with the sources, but they are only used in the next versions. Blame Sony for never fixing the Phone. It's broken since ICS. They never bothered to fix it.
After looking into several tricks to get the PhoneApp locked into the memory, I tried to install xposed framework with the module "app settings". In this module I've made com.sonyericsson.android.socialphonebook and com.android.phone resident. This means these two apps should be locked into the memory. The most recent calls I've received went smooth without any lagg. Testing further if this is a permanent solution for stock rom. I'm running devswifts v7 light stock jb.
old method:
creating local.prop in /data and adding the following lines
- sys.keep_app_1=com.android.phone
- sys.keep_app_2=com.sonyericsson.android.socialphonebook
did not work for me
When you have a custom kernel you can try to play with different governers and schedulers, this worked for me.