Ok so i did some searching and really didnt find an answer. With in the past few weeks my music will play fine on my way to work.. but on my way back it will pause everytime i open an app or do an action. I.e open settings, open dolphin browser, press home, open my txt msgs. Literally i cant do anything with out the music stopping. If i reboot it works fine again till the next morning when im on my way to work a d i have to reboot again. I have no idea why this is happening or how to fix it.
Im running task650 aokp4.1.2 with stock kernel
Power amp.
Monster turbine headphones.
Im not running any sound hacks or anything like that, and its getting kind of annoying. Any ideas???
No one??? I tried turning off start and stop when plugging in the head phones, also tried clearing data on power amp... only thing u can think of next us clearing cahce and dalvik... any one have any other ideas??
Bumped from the dead... so i wiped dalvik and cache stil same issue. Reinstalled the latest version of my rom, nothing. But i noticed that if i leave my phone on vibrate it doesnt do it. Its weird, when i put my ringer on by the end of the day i need to reboot. Putting it back to vibrate doesnt fix it. Any ideas wth is going on??
iLLdWes said:
Bumped from the dead... so i wiped dalvik and cache stil same issue. Reinstalled the latest version of my rom, nothing. But i noticed that if i leave my phone on vibrate it doesnt do it. Its weird, when i put my ringer on by the end of the day i need to reboot. Putting it back to vibrate doesnt fix it. Any ideas wth is going on??
Click to expand...
Click to collapse
Kinda weird for it to do that o.0 I'm on MA6 using power amp and i've never had that happening to me.
does your rom have ' Kill all processes on close / Don't keep activities ' under the dev options checked?
Do you have any task killers that shut poweramp or the poweramp service?
Do you have keep service checked marked under the poweramps Misc > Tweaks?
Try uncheckmarking the first option i suggested ( If it is even check marked )
and then check the second option.
it just seems like poweramp doesnt keep it's service running or it turns off when you're running
a ton of background apps reaching the background app limit.
This is my suggestion, I don't have any others.
Related
I've had this problem sometime over a month now, can't remember if I did anything to make it like this. I made a post somewhere about it happening the 17th of May, so it started somewhere before that.
My phone will freeze for 2 seconds and then reboot itself.
It started while I was on stock 4.0.2 and now I'm on stock 4.0.4 IMM761. I have a GSM Galaxy Nexus.
It only happens just after the phone has been woken up and something is started. The most common (as it's my go-to-way of forcing it, to see if it's still there) is after waking up the phone, sliding down the notification bar and pressing "settings", which doesn't open but the phone freezes and reboots itself. I first discovered this when I wanted to go in there to change screen brightness. It's also happened when I went into the notification bar and pressed a battery app there. It doesn't matter if I'm doing it in the lock screen or after the lock screen.
It's also happened when I wake up the phone and enter the camera through the lock screen.
It also regularly happen if I set an alarm in the morning. When my alarm is suppose to play it freezes and reboots, and when it's rebooted, the alarm has been cancelled without ever playing.
It doesn't need to wake from deep sleep to do this, I've had it happen mere minutes after trying to see if it's there.
I don't know if it has something to do with this, but the 21st of April I tried to do the "clear google services framework" trick to force 4.0.4 ( I was on yakjuxw), but it did not work and I remember my phone acting janky and I was scared it messed something up, but I seem to remember it getting better. I can't remember what exactly it did though.
I've read that 4.0.4 would fix the reboots that a lot of people were having (don't know if it was the exact same kind of reboots as mine) so I did this to make my phone a yakju (translated from Danish):
http://translate.google.dk/translat...at-modtage-opdateringer-til-din-galaxy-nexus/
I did that the 8th of June, and it worked flawlessly and I was on 4.0.4 IMM761 in no time. Unfortunately it did nothing to stop these reboots.
As part of the process of making my phone a yakju I, of course, did a complete factory reset, although I did make a copy of my entire SD and transferred everything over again after the process.
These past two weeks I've tried the following to fix it:
Clear cache partition in recovery.
Clear google services framework.
Clear media storage.
Tried to uninstall many apps, 2-3 a day, to see if they were causing it, re-installing them when I still had the same problem. If it's an app causing this I've yet to find it, but I find it weird that an app could be causing this.
It happens once a day, but never close to each other. It seems that some time has to pass before it can happen, and it only ever happens just after the phone is woken up, either by my alarm or by me opening the notification bar and pressing something there.
Please help me, this is unbearable.
Another thing, yesterday I tried to let it run without me pulling down the notification bar and pressing "settings", which would set off the freeze-reboot. I found that my phone would not freeze-reboot but very often it would "reload" app icons and widgets when I went around my homescreens. Where I can only see my wallpaper for half a second and then the icons/widgets appear. It would do this very often throughout my 1day 5hour uptime, and a couple of times I would try to force the reboot (by pressing "settings" in the notification bar), after the icons/widgets did the invisible/load thing and it didn't reboot. This must have something to do with it?
hi,
experienced this on my nexus s back then what i did is from recovery>mount and storages>formatted system, boot, and everything else except sd card.then it was all gone.btw you will have to flash your rom and kernel again as this is a full wipe.hope i helped and do this on your own risk
daff
bump
did it cure your reboots?
daff
dark06 said:
did it cure your reboots?
daff
Click to expand...
Click to collapse
I haven't tried that yet. I'm trying a "RAM booster" app to see if that helps, but that doesn't sound too stable even if it does.
I'm going to do a full factory reset and installing nothing, or moving anything to the SD, and just let it run like that to see if it works.
Just writing an update for anyone googling themselves here with the same problem, I had it resolved.
I found out that if I didn't force the reboot (by turning on the phone and quickly pulling down the tray and pressing something there) it could last a long time with just the launcher resetting, but it would lead to complete freezes (anywhere I was on the phone) and would require a battery-pull.
My plan was to wait for jelly-bean before doing another factory reset, I got the JB update and it completely removed the problem. I still don't know why the problem suddenly started or what caused it, all I know is that the JB update fixed it, and the update is fantastic, my phone's never been better.
Hi all -
I'm on AT&T, 100% stock, non-rooted, etc. I upgraded to JB last night via Kies without issue.
However, ever since the upgrade, my phone won't go more than 5 minutes without freezing and then crashing.
It's a very odd behavior... the screen will still animate. So, if I'm playing a game with a timer, the timer will still count down. But all touch input (including menu/home/back) does nothing. Home/back don't illuminate or do anything, but they do provide haptic feedback. Power button does turn the screen on/off.
Eventually after a few minutes, the lock screen comes up with the "tip" even though I've clicked to never show it again. However, it barely registers a swipe to unlock when it freezes again. At that point, it will usually self-reboot.
I've tried to enable some of the developer options to see if maybe there was a rogue program that was incompatible with JB, and maybe causing the issue, but I couldn't see any correlations.
I really want to avoid doing a factory reset if at all possible, as I have a game that I worked really hard on to beat a few levels, and I'd hate to lose my progress.
Anyone have any ideas on what I can try?
I should note that uninstalling programs is iffy... sometimes it works, other times it just uninstalls indefinitely.
Thanks!
Castaway78 said:
Hi all -
I'm on AT&T, 100% stock, non-rooted, etc. I upgraded to JB last night via Kies without issue.
However, ever since the upgrade, my phone won't go more than 5 minutes without freezing and then crashing.
It's a very odd behavior... the screen will still animate. So, if I'm playing a game with a timer, the timer will still count down. But all touch input (including menu/home/back) does nothing. Home/back don't illuminate or do anything, but they do provide haptic feedback. Power button does turn the screen on/off.
Eventually after a few minutes, the lock screen comes up with the "tip" even though I've clicked to never show it again. However, it barely registers a swipe to unlock when it freezes again. At that point, it will usually self-reboot.
I've tried to enable some of the developer options to see if maybe there was a rogue program that was incompatible with JB, and maybe causing the issue, but I couldn't see any correlations.
I really want to avoid doing a factory reset if at all possible, as I have a game that I worked really hard on to beat a few levels, and I'd hate to lose my progress.
Anyone have any ideas on what I can try?
I should note that uninstalling programs is iffy... sometimes it works, other times it just uninstalls indefinitely.
Thanks!
Click to expand...
Click to collapse
This sounds somewhat familiar to my experiences with JB. I rooted right away with the stock JB and had freezing / crash issues. So I then went pure stock and had issues (un-rooted). I then tried a custom TW-based ROM called BlackJelly and had issues. Now I am on CM10.1 which is AOSP JB4.2.1 based and things are even worse.
There seems to be no JB ROM that is stable for my phone. Getting very tired of this.
See my thread for details:
http://forum.xda-developers.com/showthread.php?t=2044769
- Ed
Strangely enough, my issue ended up going away. I think it was a rogue program that needed it's dalvik cache rebuilt. Once uninstalled, the phone worked great. Not sure what app it was.
Alright I have a problem with my N7.
Putting it here since more people see this thread
So I guess my N7 restarted sometime at night and when I turned it on, I noticed that first my password lock wasnt there, nor was there a lockscreen.
Then a notification came up saying:
"Unfortunately, Google partner setup has stopped.
My notification bar, wifi, and home buttons dont work. I can force stop apps in the settings, but anytime i click clear cache it reboots.
I tried to do a factory reset and when I enter my password lock and click ok, then settings force closes. I'm not sure what to do.
I forced stopped google partner setup and gallery, those two popups came when the N7 would turn on that it wouldnt work. Now they dont come up anymore but that didnt solve anything.
Any help??
I am stock and unrooted btw. The night before this happened all I did was watch netflix
some other things to add, if i uninstall an app, it reboots and the app wont uninstall.
The notification bar actually comes down, its the other one with the toggles that doesnt.
well I was able to get into recovery mode and do a factory reset that way. Didn't know that was possible without root haha. Everything seems to be ok for now...
tankmaster90 said:
well I was able to get into recovery mode and do a factory reset that way. Didn't know that was possible without root haha. Everything seems to be ok for now...
Click to expand...
Click to collapse
When stuff like that happens I get paranoid my nand or ROM is bad and do all sorts of tests lol.
I'm glad to hear that all is well again. Now root that puppy put twrp on it, make a backup and flash a good ROM lol.
Hey so my speaker phone is always on whenever I make or receive a call. I've gone through every single setting, made sure no apps are installed making it default to be on (voice recorders, GPS apps, ect) yet it is always on?
Anyone know how to fix this? Is there some app that I can install that can force it stay off unless I turn it on?
Some people say its the phone thinking its in dock mode. Is there any way to disable that?
This is driving me nuts. I've tried pulling the battery, rebooting and nothing is working.
Thanks for the help!
Is there some app that I can install that can force it stay off unless I turn it on?
Click to expand...
Click to collapse
You shouldn't need an app to do what the phone already natively "normally" does. More than likely, some app you installed is causing your problem. Even if you disable apps to not have speaker on by default, perhaps the app cache settings are still affecting your phone.
If you're still agonizing over this problem by the time you read this... I would clear all the app cache, clear data on each installed app, disable all installed apps (force stop), and if that doesn't work, back up your data and factory reset. More than likely a factory reset will get your phone working correctly again. A pain, I know, but... better than going nuts! Good luck!
Yeah I've gone through every conceivable app that would have anything to do with my speakerphone and it hasn't helped. I'm afraid to do a factory reset because I honestly don't think it is going to fix it. I'm starting to think more and more that it is a hardware issue with the USB port and not a software issue. I may have to go to a Verizon store and see what they say. I'm sure once the guy can't figure it out he will tell me that I have to factory reset it at which point I want to make say if it doesn't fix it, I'll need a new phone.
So annoyed it's not even funny.....
UPDATE:
Ok so I still can't figure out what it is, I've cleared all data and cache on all apps (including the phone app) but nothing seems to help.
For ****s and grins I wanted to see if I plugged in my headphones what it would do. When I plugged them in and tried to make a call, this time the speakerphone button is NOT illuminated BUT.........IT STILL PLAYS THROUGH THE SPEAKER PHONE AND NOT THE HEADPHONES????
I know, mind...blown.
Now if I push the speakerphone button, it turns green (on) and the sound still comes through the speaker phone but if I push it again, it turns off and now the sound plays through the headsets.
What on earth is possibly going on??? Can the phone dialer app be corrupted? What else can I try other than a hard reset? Is there a way I can reinstall the phone dialer app?
I know you stated you looked at all the apps you could, but did you look into the S Voice settings to see if Auto start Speakerphone is enabled? Supposedly it'll be used only when S Voice is used, but who knows when something might be corrupted.
Already tried that, didn't fix it. Even tried disabling Svoice.
I also booted up in safe mode and it still was doing it so I know it isn't any installed app that I have that is doing it.
At this point I think have no choice but to do a hard reset unfortunately. SO incredibly annoying.
Well, I hope you solve the problem. At least with the hard reset you'll get a clean start. Nah... nothing good about a hard reset! Damn annoying! Let us know how you solved it once you get it going.
So this is driving me nuts. I just picked up an S7 Active, and restored my data from Samsung Cloud. Everything restored fine except for Settings. That part fails every time. No big deal, I thought. I just set it up again how I like it. As soon as I got everything how I wanted it, Do Not Disturb immediately started acting super-weird. It turns on by itself, and it takes 2-3 times of turning it off to get it to stay off. When I finally get it off, it resets the settings (stays custom, but turns off all alarms, calls, and messages). I want it to allow alarms and calls/messages from favorites, and as soon as I enable those, it automatically turns Do Not Disturb back on. Turning it off again starts the whole loop over. Clearly, my Do Not Disturb settings are corrupt. Is there a way to wipe those settings, without wiping the phone and starting fresh?
Not a super helpful response, sorry in advance, but i think you may have answered your own question. Sounds like something got corupt in the copy over.
With out manually looking at all of the settings and or alot of trial and error... you may just have to reset it and start fresh...
But when you say wiping the phone, i just want to confirm that your intentions arnt to go factory reset... just do a "reset settings" and "reset network settings" dont wipe your whole phone.
Acinko said:
Not a super helpful response, sorry in advance, but i think you may have answered your own question. Sounds like something got corupt in the copy over.
With out manually looking at all of the settings and or alot of trial and error... you may just have to reset it and start fresh...
But when you say wiping the phone, i just want to confirm that your intentions arnt to go factory reset... just do a "reset settings" and "reset network settings" dont wipe your whole phone.
Click to expand...
Click to collapse
Yes, factory reset, or worst case, ODIN flash the firmware. I just wanted to see if it was something anyone else had run into. I'll tackle this over the weekend. Thanks for the response!
bug
I had turned facebook and gmail to silent notifications. DND has not turned on and media volume has not turned to zero since allowing these apps to show with sound again.
Think every time a notification comes in media volume is set to 0 and DND turned on.