Related
I just recently got the vibrant and got the OTA the same day, the gallery freezes about half the time, and about half of the time that it freezes i have to pull the battery, i cant get to task manager or put the phone to sleep and wake it up.
I searched google and there are alot of links regarding it but i didnt find any that gave any ideas to fix it.
I searched this forum and nothing came up. Anyway, I have a class 6 card, the gallery on my nexus is very quick and has never frozen, so it is definitely the phone.
In my experience with the g1, MT3g, N1 and now this vibrant, any time ive received an OTA it has come with costs, it always brings fixes and features but also causes new problems, large and small. So I dont doubt what I found while searching, that the gallery issue is a result of the recent OTA for the GPS fix. Anyway, its kind of silly that this awesome, technologically advanced device freezes when you open up one of the native apps. But can we do anything about it? And if not, is it likely that Samsung will address it in another OTA? thanks
edit: ive also just recently had my phone just turn off every day or so, and it wont power back on until i pull the battery. Maybe these 2 issues mean i have a defective device? Or is this par for the course with the tmobile galaxy s?
Overclock your phone to only run at 800-1000MHz. It completely solved this for me, 400-1000MHz still hiccups.
thank you, yet another reason to root i suppose...
So no way to fix that with stock phone? =(
heygrl said:
Overclock your phone to only run at 800-1000MHz. It completely solved this for me, 400-1000MHz still hiccups.
Click to expand...
Click to collapse
overclock huh,, i never tried i am there is a link here let me go look or how did u do it
/
That is odd, I've never had my gallery freeze or my phone reboot... Are you sure you don't have some rogue app? Perhaps you should factory reset and start fresh? Do you have any "junk" apps on your phone (stupid apps)?
I had a freeze on opening gallery right after the JI6 was released. I think it was trying to recreate the thumbnails from scratch and download pics from my Picasa acct.
Happened one time only and I actually had to pull the battery since it went unresponsive. Never had a problem after that.
~SB
perhaps unmount and remount the INTERNAL memory card. I've done this before just because I saw it as a suggestion and it recreated my gallery.
I having the same issue. I am ready to delete it and use a different app. Is that possible?
acjames said:
I having the same issue. I am ready to delete it and use a different app. Is that possible?
Click to expand...
Click to collapse
If you're rooted you can probably remove it.
I have tried factory reset so I don't think its a rogue app. I got the ota the day I got the phone so I can't compare before and after. If some people aren't having the issue period maybe a warranty replacement would resolve it. Of course, if we do end up getting froyo maybe that's something that will improve. Love the phone either way, I just get fed up with stuff like gallery freeze, random reboot, GPS issues, etc... stuff that i would think shouldn't get past product testing.
OP, this is discussed at the thread below. (use the search next time)
You are not the only one having this issue.
http://forum.xda-developers.com/showthread.php?t=805784
Quick Summary:
- Even with the removable card blank, the Gallery still have the same issues.
- I did a complete wipe and still have the same issues.
- I cleared data through System Settings which recreated thumbnails and other data, still have the same issues.
androidmonkey said:
OP, this is discussed at the thread below. (use the search next time)
You are not the only one having this issue.
http://forum.xda-developers.com/showthread.php?t=805784
Quick Summary:
- Even with the removable card blank, the Gallery still have the same issues.
- I did a complete wipe and still have the same issues.
- I cleared data through System Settings which recreated thumbnails and other data, still have the same issues.
Click to expand...
Click to collapse
Wow i am so sick of reading some loser tell somebody to "search next time". You'll be so very relieved to know that I actually did search, and all i found out is that you dont have any friends. But honestly I did find your thread, however it didnt seem to me to be on point with what i wanted to ask specifically. Your post says that "watchdog" told you your gallery is a "resource hog" and that you have to kill it. I dont know what watchdog is, nothing told me anything i just cant get into my gallery app very often, so that didnt seem applicable. Also, i got ji6 the day i got my phone so putting the gallery issue in the context you did ("since ji6 update") didnt mean anything to me, i dont anything about this phone pre-ji6 update. All I know is that my gallery app sucks, your thread was a bit technical for me to be able to apply to my particular issue
Anyway, now my gallery freezes every single time i initially try to open it, i have had to pull the battery 6 times in a row, it works after the pull. This has been my favorite android phone (of 4) but now i just want to set it on fire and run over it with my car. I guess Samsung and Android arent interested in making their $600 products work, does anybody know how i can fix my phone so that it does what it is supposed to? Also im not rooted which i assume probably makes it impossible for me to fix? thanks for any help.
DMaverick50 said:
Wow i am so sick of reading some loser tell somebody to "search next time". You'll be so very relieved to know that I actually did search, and all i found out is that you dont have any friends.
Click to expand...
Click to collapse
lol
also bump
I have gone through countless battery reconditions, following various methods, very tediously, various roms (nero, bionix, trigger, etc.) trying to get acceptable battery life. After a lot of detective work I finally pinned down the problem to the 'mediaserver' process within the system processes. It runs CONSTANTLY and drains the batter within half a day from a full charge. This problem has been documented on google code: http://code.google.com/p/android/issues/detail?id=6765
The process cannot be killed via any task manager as it seems to be a sub-process. So I finally mustered the courage to move the file from its directory into the parent directory to see if that would do the trick and restarted.
Now I'm stuck on the boot screen.
Can someone please help find a solution for this issue? I think I can recover from the boot screen issue but I know I will just encounter the same issue again and again.
I am currently on trigger 2.6.1.
Help?
I should also ask if it is possible to even ODIN back to stock from a ROM that has the voodoo fix enabled?
Just odin back, root, flash a rom, freeze the app with titanium backup.
Edit, n/m, just realized you weren't talking about an app. I'll read the link you posted.
I'm on trigger 2.6.1, no issues here. You sure it's not a bad app man?
As far as I can tell, no. It certainly could be but the I've been having battery issues since bionix 3 I think.
However I did read on that google link that certain media centric apps can cause it to go nuts. I am using the winamp beta app and youtube pretty heavily (although thats obviously unlikely to be the culprit).
I thought about freezing it but ya, its a sub process under the 'system processes'...process so I can't freeze it without taking down the whole thing and probably causing way more issues.
Thanks for the response though, appreciated.
Dude, winamp and youtube are going to use a lot of power.. How long is a full charge for you?
About 8 hours. I pull it off the charger at 7:30am, use winamp for music for about 1 - 1.5 hours and other moderate use. Dead by the time I leave work at 5. Get home, charge it up until I hit the gym (usually get it to roughly 50%) and listen to music, watch a couple videos and its begging for the charger by the time I get home.
Furthermore, I use the system panel app to find out exactly what is eating CPU cycles. That 'mediaprocess' thing is exponentially above everything else. So either a bad app is causing it to run and keep it running or something else is triggering it. I formatted both SD Cards per some of the suggestions elsewhere, but no dice.
seems like your getting normal battery life.
heavy usage on your phone will eat up the battery. especially watching videos.
So what do I make of the mediaserver process that is using up 40-50% of the battery? Watching videos, listening to music or not, I get the same results. I really don't think its that.
Are you sure you're completely killing the apps when you're not using them? Use the task manager and be sure the app is not running. Otherwise, be sure to freeze media hub and the DRM storage with TB. It should help with drain while the phone is on standby.
Sent from my SGH-T959 using XDA App
Ya I'm sure. I don't even have mediahub installed on the phone however I am going to try freezing / removing the DRM storage thing.
Mediaserver constantly running is the reasons the battery drains. I didn't know if anyone has any solution as to how to kill it, or how to keep it from running continuously. This is a known bug as shown in the link in OP.
I'm guessing everytime I open up winamp or something it starts, then never stops after that. Who knows.
mkearney83 said:
Ya I'm sure. I don't even have mediahub installed on the phone however I am going to try freezing / removing the DRM storage thing.
Mediaserver constantly running is the reasons the battery drains. I didn't know if anyone has any solution as to how to kill it, or how to keep it from running continuously. This is a known bug as shown in the link in OP.
I'm guessing everytime I open up winamp or something it starts, then never stops after that. Who knows.
Click to expand...
Click to collapse
Do you have allshare installed?
running Trigger 2.6
W/ dragon kernel uv/oc to 1.28
and Adw launcher ex
No sir. I've deleted pretty much anything DRM, Mediahub or Allshare related. Most of it is already removed with Trigger (ROM I'm using right now) and I removed a couple more services / apps in the quest for better battery life.
Ever since I installed Bionix v1.3.1 my phone randomly stops being able to play music. It happens every 2 hours or so. I've tried different music players and they all have the error above. The only thing that fixes it is a reboot. This works but takes so long, and I usually go to play music in the car and all of a sudden its broken again.
And its all my music not just certain files. System sounds still work tho, so its something with the internal storage because I don't even use the external sd. I've been trying to find an app or something that can remount the internal storage and not the Ext. SD.
Yes, i've also tried different roms, like Loki, Trigger and others. The other day I ODIN'ed back to JFD and rooted and started all over but the problem persists. I've noticed some other people asking questions about this but nobody has a definite answer besides reboot. We shouldn't have to reboot to listen to music every so often. Some people said unplugging your usb cord without unmounting can cause that, but I've tested it both ways and still the issue comes up. Anybody with some know how or some devs willing to input? Thanks. Running the latest Trigger at the moment if that matters.
Bumpitty Bump
Never experienced any of this. What music players are you using and what format is your music in?
Yeah this used to happen to me until on day it just stopped working and now it plays one song and freezes.
Sent from my SGH-T959 using XDA App
Sdobron said:
Never experienced any of this. What music players are you using and what format is your music in?
Click to expand...
Click to collapse
They're all mp3's and I used the stock player, the MIUI player, mixzing, mort player and poweramp too.
Have you tried changing back to stock rom? Or maybe trying other formats? Cuz I have no clue... =P Sorry
Delete the twitter app. Mine was doing the samething, now its fixed after deleting the twitter app
Twitter doesn't cause the problem. I've had it installed for months.
I'm having the same issue, but I'm on the stock 2.2 and rooted. There's been other lingering issues as well, like wifi not reliably connecting, the system thinking it's in debug mode with just a car charger attached, and other things that are irritating, but nothing major like that.
I've found something else interesting about this.
The YouTube player also fails to load any videos when this happens - I get the "there was an error while playing - touch to retry" message.
The music player will also still play .wav files just fine - which may explain why the system sounds still work.
I'm guessing that the youtube app and MP3s share a codec somehow, and something is failing to work properly. Beyond that, I know little else.
Yes, I noticed youtube too..I found a pretty quick work around. Download Hot Reboot from the market. You just push the hot reboot button on the widget and restarts the whole system without rebooting the actual phone. Once you push it, it shows you the android boot screen for a couple seconds and then back to your home screen and the sounds work again. So weird. I can't wait until we have a good 2.3 version working, because out of all the gingerbread roms I tested the issue was non existent. Good luck Everyone.
Trust me on this.. you can check my other posts on this same issue... I started getting this same error out of nowhere and it happened all the time... someone said delete the official twitter app. I did and it has not happened since.
I have been using plume.
And I don't care about these people who say twitter is not the cause. When there is an issue and changing or removing one thing solves that issue... then that one thing was the problem.
That was DEFINITELY the problem..Uninstalled twitter yesterday when you posted that and I haven't had the issue since. You sir are awesome. By the way, how did you find out twitter was the cause?
Confirmed fixed by uninstalling the Twitter App
That definitely fixed it for me. All my music started playing fine right after the uninstall finished.
thanks!
I'm reporting the bug.
Greg
lupascu.marius said:
That was DEFINITELY the problem..Uninstalled twitter yesterday when you posted that and I haven't had the issue since. You sir are awesome. By the way, how did you find out twitter was the cause?
Click to expand...
Click to collapse
I realized that the music errors were almost insync with when i would check my twitter.... or at least I just felt it was, ha. then searching through the interwebs someone else said they were having problems and they thought it was related to twitter so i said screw it and deleted my twitter app and the problem went away.
your welcome
Awesome!
ipeench said:
I realized that the music errors were almost insync with when i would check my twitter.... or at least I just felt it was, ha. then searching through the interwebs someone else said they were having problems and they thought it was related to twitter so i said screw it and deleted my twitter app and the problem went away.
your welcome
Click to expand...
Click to collapse
Wow thats a whodathunka for sure!
Sure works tho, I was begining to think the 2.2 update jacked the phone...
+10
I have the same problem.
I've uninstalled twitter but the problem still exists. So I guess twitter was not the main or only cause.
Are the files you're tyring to play acc or mp3?
ipeench said:
I realized that the music errors were almost insync with when i would check my twitter.... or at least I just felt it was, ha. then searching through the interwebs someone else said they were having problems and they thought it was related to twitter so i said screw it and deleted my twitter app and the problem went away.
your welcome
Click to expand...
Click to collapse
I'm having the same issue with the of mp3 files that I know work but my music player saying "unsupported file".
And yes a reboot does get me where I can play the media file. Also this issue not only stops local mp3's from playing but also youtube wont play a clip, short video clips wont play thru the browser option, I can have ever choose "internet" and the file downloads to my phone (feels almost like I'm back on winmobile 6.5).
I do have the Offical Twitter installed on my Cappy, but as of this posting, I;ve unsinstalled Twitter and when with another app. I will post back tommorow is my phone does the same thing again now that Twitter is removed.
Much Thanks....
{Edit}...I must say that my phone actually feels more responsive since removing Offical Twitter for Plume but Plumes Widget is not that great all the app looks nice, its been 4 hrs and music still plays from default music player.
I was skeptical about this solution, but I tried deleting the Twitter app anyhow. It completely solved the problem. Bravo to whomever figured this one out.
I'm using the latest nightly, but I've been seeing this pretty much since I started using KitKat on my phone.
The problem goes like this. I'm listening to music, and after a random amount of time, the music stops playing and the player hangs. It doesn't matter if I kill it. I have to reboot the phone to make it work again. I've tried wiping the player's cache as well as using different players and it's the same.
I've been noticing a pattern with several apps unrelated to music. The Opendelta app which I use for upgrading nightlies sometimes also hangs when patching the zip, and provides an ETA that finishes about the same time as the Universe itself.
The phone also hangs when I'm copying files in USB storage mode from my computer.
I think I read over the i9100 forums that the KitKat driver for these phone's storage is really buggy or something, and thus behaves like that.
Has anyone have had the same problem?
Is there any hope for such a driver to be fixed in any ROM or Kernel for the i777?
Should I just revert to 4.3?
I'm not very Android/Linux savvy, but I could provide system logs if needed.
Mighty_Rearranger said:
I'm using the latest nightly, but I've been seeing this pretty much since I started using KitKat on my phone.
The problem goes like this. I'm listening to music, and after a random amount of time, the music stops playing and the player hangs. It doesn't matter if I kill it. I have to reboot the phone to make it work again. I've tried wiping the player's cache as well as using different players and it's the same.
I've been noticing a pattern with several apps unrelated to music. The Opendelta app which I use for upgrading nightlies sometimes also hangs when patching the zip, and provides an ETA that finishes about the same time as the Universe itself.
The phone also hangs when I'm copying files in USB storage mode from my computer.
I think I read over the i9100 forums that the KitKat driver for these phone's storage is really buggy or something, and thus behaves like that.
Has anyone have had the same problem?
Is there any hope for such a driver to be fixed in any ROM or Kernel for the i777?
Should I just revert to 4.3?
I'm not very Android/Linux savvy, but I could provide system logs if needed.
Click to expand...
Click to collapse
This is a known issue, and there's no fix for it at this time (that I'm aware of). It has to do with Exynos devices, so you're not alone.
http://forum.xda-developers.com/showpost.php?p=51013349&postcount=569
cyril279 said:
http://forum.xda-developers.com/showpost.php?p=51013349&postcount=569
Click to expand...
Click to collapse
Hadn't seen the exFAT bit, but it isn't linked exclusively to the external SD. It happens with the internal as well. And, as I said before, with other apps besides music.
SteveMurphy said:
This is a known issue, and there's no fix for it at this time (that I'm aware of). It has to do with Exynos devices, so you're not alone.
Click to expand...
Click to collapse
Oh, I see.
I think I'll just get this over with and flash a nice JB ROM.
Just out of curiosity, has Exynos support so far been depending on Samsung or are the drivers reverse engineered by someone?
Based on the thread, and what you've reported in the OP, these issues are one and the same.
The thread agrees with you, that the issue is NOT exclusively associated with the external SD. Folks are re-formatting both internal AND external SD, and reporting positive results.
further, the Open delta issue is suspected to be related, as a "fuse daemon" issue.
Try reading the thread, even if only starting from page 17.
Happy Flashing
-Cyril
Mighty_Rearranger said:
Hadn't seen the exFAT bit, but it isn't linked exclusively to the external SD. It happens with the internal as well. And, as I said before, with other apps besides music.
Click to expand...
Click to collapse
Thanks for all this information! Very helpful
i've recently been encountering random reboots on my Galaxy Note 3 (N9005), on stock 4.4.2 ROM.
The reboot occurs regardless of time, foreground/background running apps, battery level and anything else i can think of. for instance, it can just instantly hang+auto-reboot while i'm browsing facebook, surfing on chrome, switching tracks on poweramp, or even when the screen is off doing nothing (deep sleep)!
I've tried to uninstall some of the recent installed apps, but still unable to find any culprit. is there any way i can identify the culprit, without resorting to factory-reset for my device? i spent a lot of time doing the configuration for each app that i use, and wouldn't want to repeat the whole process..
Thanks in advance for your help!
could anyone help please?
Only way to know would be to get a logcat or last_kmesg. You might try something like this since it is so random:
https://play.google.com/store/apps/details?id=org.jtb.alogrec
es0tericcha0s said:
Only way to know would be to get a logcat or last_kmesg. You might try something like this since it is so random:
https://play.google.com/store/apps/details?id=org.jtb.alogrec
Click to expand...
Click to collapse
i downloaded aLogRec as requested and recorded the log for the entire day.
this is the log for the first 16hours - i opened it with notepad++ and the log was super short - is it normal?
Link 1
this is the log for the next few hours, where the random reboot occurred halfway - seems that it's empty. does that mean there's no way for me to know how the reboot came about?
Link 2
dylansmith said:
i downloaded aLogRec as requested and recorded the log for the entire day.
this is the log for the first 16hours - i opened it with notepad++ and the log was super short - is it normal?
Link 1
this is the log for the next few hours, where the random reboot occurred halfway - seems that it's empty. does that mean there's no way for me to know how the reboot came about?
Link 2
Click to expand...
Click to collapse
Yea, that app definitely didn't work. Not really sure why. But other than catching it in the act using the logcat, whether it is another automatic one or just the manual way via the phone or computer, there's no other way to tell. You do know that you can backup most of your apps and settings with a variety of tools? It won't make everything perfect, but cuts the time of restoring your phone after a factory reset way down. I literally wipe my entire phone and reset it up like 3 times a week on average. It usually takes me about 20 minutes to an hour depending on if I just need it usable or exactly the way I like it.
es0tericcha0s said:
Yea, that app definitely didn't work. Not really sure why. But other than catching it in the act using the logcat, whether it is another automatic one or just the manual way via the phone or computer, there's no other way to tell. You do know that you can backup most of your apps and settings with a variety of tools? It won't make everything perfect, but cuts the time of restoring your phone after a factory reset way down. I literally wipe my entire phone and reset it up like 3 times a week on average. It usually takes me about 20 minutes to an hour depending on if I just need it usable or exactly the way I like it.
Click to expand...
Click to collapse
thanks for the reply. got a few questions:
1. other than aLogCat, any other app i can try to catch the random reboot in the act?
2. yes, i could backup all my apps+settings using TB, but would i also be restoring the 'random reboot' in this case as well?
3. another symptom just occurred and i'm not sure whether it's relevant to the random reboot. after the random reboot (or so it seems), all my saved WIFI passwords get forgotten, and i need to re-enter the passwords for it to auto-login to my home/office network. i also realize it loses one of the settings i previously adjusted in Developer Options - the transition animation scale was set to 0x last time and set back to 1x.. but when it random reboots nowadays, it will just default back to 0x (which isn't the correct default).
i'm so frustrated at the number of problems my phone is facing right now..
dylansmith said:
thanks for the reply. got a few questions:
1. other than aLogCat, any other app i can try to catch the random reboot in the act?
2. yes, i could backup all my apps+settings using TB, but would i also be restoring the 'random reboot' in this case as well?
3. another symptom just occurred and i'm not sure whether it's relevant to the random reboot. after the random reboot (or so it seems), all my saved WIFI passwords get forgotten, and i need to re-enter the passwords for it to auto-login to my home/office network. i also realize it loses one of the settings i previously adjusted in Developer Options - the transition animation scale was set to 0x last time and set back to 1x.. but when it random reboots nowadays, it will just default back to 0x (which isn't the correct default).
i'm so frustrated at the number of problems my phone is facing right now..
Click to expand...
Click to collapse
https://play.google.com/store/apps/details?id=scd.lcex - looks pretty solid and more updated than the other one.
Possibly, but since we don't know what caused it, no way to know. What you do is backup everything, reset, then test, then start to add apps back in and test. Sucks, but just one of those things. Software issues can be tricky because there are so many different factors in play.
But it seems like this might be an issue with certain Samsung phones with batteries that are not performing as they should:
http://forum.xda-developers.com/showthread.php?t=2567941&page=3
es0tericcha0s said:
https://play.google.com/store/apps/details?id=scd.lcex - looks pretty solid and more updated than the other one.
Possibly, but since we don't know what caused it, no way to know. What you do is backup everything, reset, then test, then start to add apps back in and test. Sucks, but just one of those things. Software issues can be tricky because there are so many different factors in play.
But it seems like this might be an issue with certain Samsung phones with batteries that are not performing as they should:
http://forum.xda-developers.com/showthread.php?t=2567941&page=3
Click to expand...
Click to collapse
alright, will try the Extreme version and hopefully it catches the culprit.
As for the battery problem, it doesn't seem like the same case as mentioned in the other thread - he had a reboot loop and crazy drain, both of which are not existent (luckily) symptoms on my end.
Your issues could definitely be explained by battery issues though. Have seen stuff like this before at my shop. Batteries are less than $10 typically and worst case, you have a spare battery so if you go out and about and the phone dies, you don't have to run to a charger / outlet.
es0tericcha0s said:
Your issues could definitely be explained by battery issues though. Have seen stuff like this before at my shop. Batteries are less than $10 typically and worst case, you have a spare battery so if you go out and about and the phone dies, you don't have to run to a charger / outlet.
Click to expand...
Click to collapse
hmm, pretty sure it's not a battery issue then. just bought a new battery and the same problem exists.
my logcat files appended as follows: https://www.dropbox.com/s/yjtio2je6h71mre/LogCat.zip
would appreciate everyone's help!
thanks!
I was experiencing random reboots on the stock ROM for my KFHD when I was running stock. Turns out it was caused by me adjusting the DPI to a custom value.
>>>Sent from my homebuilt TARDIS running Android 4.4... or maybe it's a Kindle Fire HD running Cyanogenmod 11<<<
Ph0enix_216 said:
I was experiencing random reboots on the stock ROM for my KFHD when I was running stock. Turns out it was caused by me adjusting the DPI to a custom value.
>>>Sent from my homebuilt TARDIS running Android 4.4... or maybe it's a Kindle Fire HD running Cyanogenmod 11<<<
Click to expand...
Click to collapse
that could be one possible cause as I have certain preset dpi's for apps using Xposed.
any other possibilities and any other way to avoid it?
dylansmith said:
that could be one possible cause as I have certain preset dpi's for apps using Xposed.
any other possibilities and any other way to avoid it?
Click to expand...
Click to collapse
The only thing I can suggest is resting the DPI to stock, unfortunetly. Or a DPI that is known to work well with your device.
Ph0enix_216 said:
The only thing I can suggest is resting the DPI to stock, unfortunetly. Or a DPI that is known to work well with your device.
Click to expand...
Click to collapse
just curious - did anyone look through my logcat to see if there are other causes? i already restored to default DPI but still experiencing the same issues.