Hi to every one I have seen this threat in other forums, it seems the sysem automaticaly kills the gallery app and this make the music apps to stop playing or at least thats what the other forums say, it's really random, does this has happen to any of you and if yes is there any workaround other than upgrading the Android os or installing a Custom Rom.
Actually I've only had this start happening since I flashed a custom rom, never happened to me on stock rom rooted. I'm guessing it has to do maybe in the power savings settings or something, which would explain it being turned off after a certain amount of time. But I dunno.
MoPhoACTV Initiative
Actually, I get this all the time in Pandora. I get "Pandora has been running for 45 minutes" and something about it draining the battery. (The 45 minutes I remember, cant remember the exact words on the battery) If you ignore it, it will shut it down. Problem is, phone is usually next to me sleep and I do not get notification like I have a text or e-mail, so I dont see it.
The other jacked up thing about it, for whatever reason, it disconnects my bluetooth headphones even though they are on. I have to (In this order) shut off headphones, turn BT off on phone, Turn BT on on the phone, then turn headphones back on!! This pisses me off because for some reason, I ALWAYS get a phone call when I'm doing this and have to hold the phone to my ear and tell whoever I will call them right back!!
Well I flashed the 4.5.1A-1_SUN-198_6 leak, and I got it rooted and unlocked, maybe thats the reason.
Related
I've noticed here recently that when I turn on my phone, it displays standard time, then military time, which it is set to. Sometimes, it will show an outdated time before it updates itself. We're talking a matter of seconds, but I didn't know if anybody had an idea.
I see the same thing. It's annoying.
Especially the standard time to Military time.
I could partly understand the update in a time from when the phone went to sleep, or screen is shutoff to when it wakes up, but this is poor programming.
Anyone have an idea for a fix?
Once my phone was off 20 minutes when I woke up. It would update each minute just fine, except it was off exactly 20 minutes.
I had to reboot to fix it. I don't believe I was stock, but I don't remember which kernel I was running. I flashed it again shortly after that.
Hasn't happened since.
This is one of the many reasons I NEVER trust the alarm on a phone. I've had problems of them not going off even back when I had a razr.
If I'm travelling, I'll make sure to set the alarm on at least 2 phones (if I'm with others), just in case.
Ok so this morning I had a little bit of a frustrating time getting out the door and I'm wondering if anyone has good info to help me and others. Specifically, I'd like to hear from those that actually understand what is going on under the hood so that I can have a morning routine with my phone that gets me out the door with minimal frustration...
First off, I know that the easiest solution is to revert back to an ICS rom. I know that until source drops the JB roms are experimental and that issues are to be expected. We are so lucky to have the devs that support our phone. They have brought us this far and we should show appreciation through the "thanks" button and, as means allow, through donations. Don't get me started on the ridiculous lament of some that can't afford it - Guys if you can afford a phone plan (or a cup of coffee), kick the dev a fiver (not much, but if everyone did it would add up)- side rant off
Back on topic - my two issues are my paranoia over the deep sleep issue when pulling phone off charge and losing in call volume. For me the two issues are related. Like many, I need my phone to maximize it's battery potential. I can't afford to pick up my phone in the afternoon to place a call only to find that it has been draining battery because it was not properly sleeping because of how it was pulled off the charger. I have no rogue apps running and I am not entirely convinced that unlocking it before removal from the charger fixes the deep sleep issue. I am further convinced that nobody, not Samsung nor our amazing devs can fix this issue. It must be a hardware problem as Samsung had to be aware of it before the ICS update and were not able to fix it. My solution currently is to reboot my phone every morning after I take it off the cradle.
This leads to my second issue. After I reboot my phone, I immediately dial my home phone number to verify that I have in call volume. In most instance I know immediately if I hear the phone ringing through my note's ear speaker even before my home phone starts ringing. If I hear this, I am good to go - as long as my phone does not randomly crash throughout the day I am sure that if someone calls me, I will be able to hear them or if I need to place a call the phone will act as a phone.
Through the work of our devs, we have some very stable roms and random crashes are minimal. I am going into my third day on Manelscout4life's eclipse rom and have yet to experience a random reboot! My problem this morning was that I lost in call volume after my voluntary reboot and had a hell of a time trying to get it back. For those, who understand what exactly is happening, I would ask - how is the quickest way to get up and running so that I can get out the door?
-I know that the issue has been linked to rebooting while connected via wifi so I toggle it off before rebooting
-I know that sometimes a simple reboot fixes it so I try that -however today three simple reboots served only to waste valuable morning time and drain 3% of precious battery life.
-clear app data and force stopping phone and related apps before rebooting sometime works - no dice this morning
-clearing caches and fixing permissions in recovery sometimes works- this was the kicker today, but only on second try...
I know that the in call volume issue will more than likely be fixed once JB source is dropped by Samsung. It is a known issue that affects all JB roms currently out and I know the devs are working hard to fix it without Samsung's help. But I think if someone can give me a sure fire morning routine (preferably under 5 minutes). I would be good to go with the present state of JB stability....
Just bought a second hand GS3 from ebay, the screen had a small crack but otherwise was meant to be OK. I put Foxhound ROM on (I'm just used to having to upgrade the rom) and am finding that the sound will work fine after a restart, but then, after it has gone to sleep all sound will stop working.
I've tried clean wipes/formats etc. and also checked all relevant settings I could find (including turn off all sound in accessibility, what an odd option).
I've tried two ROMs and three kernels.
I've tried searching google and xda for hours but haven't found anything that wasn't related to the headphone port; this affects both speaker and headphone, although when the headphone is in and the sound has died I can hear some strange static noises when it's meant to play sound, could be interference or a clue.
I've dismantled the phone and inspected for damage, nothing obvious. While dismantled I tried applying pressure to the speaker flex cable and various other IC's to no effect.
It really seems like a software glitch since it only happens when the device goes to sleep;
You can turn the screen off and unlock within 3 seconds and it will be OK.
If you wait 5 seconds with the screen off - boom, no sound.
Any ideas? Is there some deep idle sleep setting that kicks in after 3 seconds I can disable or some way to log audio errors or... something?
Thanks
defroster said:
Just bought a second hand GS3 from ebay, the screen had a small crack but otherwise was meant to be OK. I put Foxhound ROM on (I'm just used to having to upgrade the rom) and am finding tht the sound will work fine after a restart, but then, perhaps after it has gone to sleep once or twice (never more than a few minutes unless I'm plying a game, in which case it stays on just fine) the sound, all sound, will stop working.
I've tried clean wipes/formats etc. and also checked all relevant settings I could find (including turn off all sound in accessibility, what an odd option).
Any ideas?
Click to expand...
Click to collapse
May Be The Phone Was Damaged, Try Stock ROM
i'm downloading a different ROM now but it takes hours (rural australian phone lines...)
same result with a different ROM =/ I've fixed many phones, computers etc before but not sure what to investigate here, guess i'll dismantle it and see.
A second rom and kernel same result.
Seems to lose sound as soon as it goes to sleep (screen off), really seems like a software problem but can't find any other reports on this phone similar.
Help!
Anyone?
Looks like a software problem but can't say where you can look.. If kernel is not the cause..
Maybe hardware after all..
sent from here, there, somewhere!!
The only way I can imagine it being hardware is if it's heating an audio ic during boot to make a connection and then when sleeping it cools and the connection is lost. It's a long shot but if it's software why is it not happening to anyone else? No weird software installed or anything.
defroster said:
The only way I can imagine it being hardware is if it's heating an audio ic during boot to make a connection and then when sleeping it cools and the connection is lost. It's a long shot but if it's software why is it not happening to anyone else? No weird software installed or anything.
Click to expand...
Click to collapse
Does the sound still work through headphones (after the sound stops working)?
Sent from my GT-I9300 using Tapatalk 2
no, it doesn't seem to be headphone jack related.
the only thing I changed (aside from the rom) that I can think of that MAY have done something is some network setting for my carrier (vodafone .au) - there was an option in foxhound rom or something, but I can't for the life of me remember what it was called, I googled it at the time to see what it was but have since lost the browser history, it was some feature of the phone network that stops sending requests to the network when the phone is sleeping or some such... I'm really grasping at straws there though.
can't seem to find a stock rom for Australia either?
updated OP with more info, sorry for the bump, i'll let this die if no-one's got any ideas.
defroster said:
no, it doesn't seem to be headphone jack related.
the only thing I changed (aside from the rom) that I can think of that MAY have done something is some network setting for my carrier (vodafone .au) - there was an option in foxhound rom or something, but I can't for the life of me remember what it was called, I googled it at the time to see what it was but have since lost the browser history, it was some feature of the phone network that stops sending requests to the network when the phone is sleeping or some such... I'm really grasping at straws there though.
Click to expand...
Click to collapse
I think you are talking about fast dormancy toggle.. But I do not think it will cause any problems.. Also as you have already done factory resets an app should not be a problem..
I can only think of hardware faults..
sent from here, there, somewhere!!
yes i just finally remembered it and tried disabling, you're right, no difference.
I'm having trouble figuring out how hardware could be the culprit though, since it's triggered by the screen off for more than 3 seconds, there's something in software causing it.. but you're right, why does it persist over a wipe then? argh!
Downloaded stock rom, problem remains
Hey guys!
I'm kinda lost here. I've had my Archos Gamepad with Android 4.1.1 (sorry, forgot to put the device in the title) for a few weeks now. Yesterday I noticed there's no sound coming from it anymore. Since I mostly use it for things that don't require sound I can't really say when was the last time it worked. When I loaded up an N64 game yesterday I first noticed that there was no sound. Luckily, a reboot helped, I played for a few minutes and then put it away. Later that night I picked it up again, sound was gone.
After rebooting and fiddling around with settings about a thousand times, I can now say it will always go like this:
Reboot, unlock, unlocking sound is heard, clicking a few things, sound is fine, then all of a sudden it's gone.
But here's the strange part: When I lock the screen, it will always play that little *click* from the speakers. That one never fails. There's no sound at all no matter what I do, but as soon as I press the power button it goes *click*.
So here's a few facts:
- Sound stops after a few minutes of working, no matter what I do, even after factory reset
- Lock sound always plays
- Headphones do the same, working for a while then stopping, lock sound stays
- of course sound levels are at max, and there's no apps that do anything sound-related
- after connecting it to my laptop today it worked for for a while, longer than usual, but was gone again when I picked it up later
- auto-rotation of the screen also started failing on me from time to time, maybe related?
As a sidenote, a few days ago my washing machine broke, releasing a flood of water on the floor and my Gamepad just so happend to lay there, getting a little water on it. I picked it up right away, dried it off and shut it down. I don't know if that's anything to do with my problem because a) it worked fine when I turned it back on later, b) since the lock sound keeps playing I don't think my sound is broken hardware-wise, and c) I can't tell when sound stopped working because like I said before I don't always need it.
The working lock sound is what really confuses me about this. I just don't know what to make of this.
If anyone has even the slightes idea it will be much appreciated!
mookieananas said:
Hey guys!
I'm kinda lost here. I've had my Archos Gamepad with Android 4.1.1 (sorry, forgot to put the device in the title) for a few weeks now. Yesterday I noticed there's no sound coming from it anymore. Since I mostly use it for things that don't require sound I can't really say when was the last time it worked. When I loaded up an N64 game yesterday I first noticed that there was no sound. Luckily, a reboot helped, I played for a few minutes and then put it away. Later that night I picked it up again, sound was gone.
After rebooting and fiddling around with settings about a thousand times, I can now say it will always go like this:
Reboot, unlock, unlocking sound is heard, clicking a few things, sound is fine, then all of a sudden it's gone.
But here's the strange part: When I lock the screen, it will always play that little *click* from the speakers. That one never fails. There's no sound at all no matter what I do, but as soon as I press the power button it goes *click*.
So here's a few facts:
- Sound stops after a few minutes of working, no matter what I do, even after factory reset
- Lock sound always plays
- Headphones do the same, working for a while then stopping, lock sound stays
- of course sound levels are at max, and there's no apps that do anything sound-related
- after connecting it to my laptop today it worked for for a while, longer than usual, but was gone again when I picked it up later
- auto-rotation of the screen also started failing on me from time to time, maybe related?
As a sidenote, a few days ago my washing machine broke, releasing a flood of water on the floor and my Gamepad just so happend to lay there, getting a little water on it. I picked it up right away, dried it off and shut it down. I don't know if that's anything to do with my problem because a) it worked fine when I turned it back on later, b) since the lock sound keeps playing I don't think my sound is broken hardware-wise, and c) I can't tell when sound stopped working because like I said before I don't always need it.
The working lock sound is what really confuses me about this. I just don't know what to make of this.
If anyone has even the slightes idea it will be much appreciated!
Click to expand...
Click to collapse
As you still have audio with the lock sound it doesn't sound like you broke it totally with the water damage so I recommend contacting Archos for a return/replacement.
So I bought my phone from AT&T just as the new M8 was coming out (got a good deal as a result) and ever since that day its been dependable, efficient, and never lagged a single second.
But then the HTC Sense 6 ROM started to act up, opengl issues, and various bugs that drove me insane! So I switched to CM11, (btw no IR or radio or hardware encoding support on it) and all went well until about 2 weeks ago.
Suddenly my phone is sluggish at times, especially on switching applications, and the battery life went from around 10 hours average usage, to 5... Now its down to 3... Not only that but the phone is HOT!
If I even watch a Twitch stream, or YT video, or play a game, or even navigation, camera, chrome, anything with it (including listening to music), the device gets to 43 degrees C. That is with the device out in the air, passively cooling.
If I leave it on a surface, with the back covered up (like in my pocket, or watching a video in my bed) it will go past 50 C, and climb further! At one point in my car while driving, (was charging and navigating, aux was connected so i could get audio navigation through my speakers) I suddenly realized I had past my exit 5 miles back, and had to stop to check the phone...
The phone was not responding to my wake button presses, nor holding it down, it was not outputting directions, and the red LED light was softly lit (not flashing) so immediately I unconnected the charger, and aux cable. The phone still didn't respond, holding power + vol up soft resetting it worked. But what struck me most was how blooming hot it was! It was NOT in direct sunlight, nor was the display on. It practically burned my hands! I had to look up how to soft reset the phone, using my old LG Nitro HD which is my GPS tracker for my car (nifty setup btw).
Now I had an LG Nitro HD which did this sort of thing 24/7 and I could not STAND that phone, since you had to baby the device every second to keep it cool, otherwise you would need to restart.
I have seen numerous threads online about the HTC One getting toasty, and it has before for me, but NEVER THIS HOT! Also this only JUST started happening (its not related to CM11 since I had a backup of HTC's ROM and it did the same thing (in fact it was even slower x.x)
Now here is my question : is this a normal occurrence for smartphones of this age? I think its 1-2 years old... Its past the warranty I suppose (still have the card, and box btw) Is this something that I just have to deal with?
I have used the phone alot while it was charging, and left it on a charger for a long time after it was fully charged... (i thought newer phones had a disconnect for charging)
What bothers me is how suddenly the phone has become stricken with this... problem. It has only been 2 weeks, and battery life is effectively halved, and I am afraid to even USE navigation anymore (unless I hold the phone up infront of an AC vent, which I did all the way home >.< not a fun task since its a manual!)
Thanks in advance!
I had this issue with my M7 for T-Mobile. I would factory reset it and things would be okay for a while until I logged into all of my common apps and realized it would happen again... Some apps make the phone work harder and a lot more on the M7... The way I fixed this was I removed apps I didn't really use and make sure to not be logged into apps that I don't commonly use... The other thing I did was restart after using any video and audio apps... One more thing was I turned on the power saver option with vibrate and cpu unchecked and my phone started acting better...
Edit: if you have insurance through at&t I would go back to complete stock (get rid of tampered flag and red warranty warning included) and let them know it's freezing up. They should send you a replacement and it may help you out...
OfficialLocdoGg said:
I had this issue with my M7 for T-Mobile. I would factory reset it and things would be okay for a while until I logged into all of my common apps and realized it would happen again... Some apps make the phone work harder and a lot more on the M7... The way I fixed this was I removed apps I didn't really use and make sure you not be logged into apps that I don't commonly use... The other thing I did was restart after using any video and audio apps... One more thing was I turned on the power saver option with vibrate and cpu unchecked and my phone started acting better...
Click to expand...
Click to collapse
Yeah actually I just factory resetted the phone, and its absolutely normal now... Furthermore the USB speed is no longer 1mb/s and instead is back up to USB3 speeds!
BTW I did a firmware AND software factory reflash / reset.