Database Info

[Q] Partial sound until reboot, software or hardware?

My problem boils down to this:
Some sounds just randomly stop working, until I reboot. Even a soft reboot seems to work.
In particular, this seems to apply to system, ringer, and alarm volume. Media seems to be exempt (I could be wrong on this).
This leads to weird cases where the unlock sound works, but the home button sound doesn't.
Or in Super Hexagon where the announcer is mute, but the music still plays.
I have already confirmed this is not caused by Xposed.
Yes, I have checked the other threads.
No, a wipe with the factory image didn't work.
It seems to be software based, but I really can't find anything wrong with my setup
I can't get this replaced until I go back to Canada in August and it's kinda a pain since I have uni in September.
Also, it would be sad if this WAS a software issue and it happened all over again on my new replacement.
Can anyone help? Thanks in advance.

No ideas?

This has happened to me a few times.. I believe it's just a random derp which happens on the custom rom which I use (AICP). A reboot fixes it.

But this is happening almost on a daily basis. This is especially annoying with my alarm and ringer.
I wish to get to the bottom of this so I can know whether to RMA or not.

No idea what this problem is? anybody able to offer advice?

I currently have an N5 which is running PA (4.5 beta2) and Franco (R59) and i seem to come across this issue no matter what version (or combination of versions) i end up using.
The issue - After installing the rom and kernel it will work fine for a week or so and then after that period it will have this issue whereby I press the power button and nothing will happen to the screen, it just stays black but i know the phone is still on because the LED will flash. From this point onwards i usually just reset the phone and then it will work fine for the first maybe 20 mins and then it ends up doing the same thing again.
I know it isnt a problem with the power button itself cause it works totally fine after the phone resets (and im still able to reset the phone using the power button), sometimes the screen will actually power up when i press the button and it shows me my home screen but then fade to a black screen and it just does that over and over again (during that period you cant actually do anything, tried touching screen, volume up+down etc and there is just no response) unless you reset the phone.
any help would be appreciated

It could be one of a few things. Generally it will be an app or a kernel setting. I would recommend ruling out kernel first by flashing ROM without the kernel.
Sent from my Nexus 5 using Tapatalk

Yeah that definitely seems like a kernel issue. Try just flashing the rim by itself as mentioned above. Also what apps do you have install that deal with display stuff, ex. Lock screen notifications, led light etc.?

nym27jrey said:
...Try just flashing the rim...
Click to expand...
Click to collapse
Not sure you want to do that

hi guys, im pretty sure i have found the source of the problem now. I normally have the 'Twilight' app (nothing to do with teenage vampires + werewolves) in the background which softens the colours and dims the screen to a level which is more pleasant for the eyes at night. After uninstalling this it seems as though the problem has gone.
I think the app itself projects an overlay on top of the launcher to dim the screen but sometimes when the app is running and the screen is dimmed it seems to block out (unable to tick) some of the pop-up boxes which some programs throw up. Too bad, i really liked the app too, might just have to email the developer and let him know.
Now on to my next problem, anybody know of another app which does similar? lol

ticketseriously said:
Now on to my next problem, anybody know of another app which does similar? lol
Click to expand...
Click to collapse
Chainfire's C.F. Lumen

OK I was wrong. After uninstalling all the apps which have an effect on my display as well as reinstalling the ROM without the Franco kernel its still having the same issue.
I left a music app running this time and then left the phone till it put itself into sleep/lock mode. The app continued to run and I could change the volume with the side buttons but when i Pressed to get the screen on it just stays black now but it seems as though everything is still running in the background. Anybody had this type of issue with PA before? Thanks

One last question on the kernel, do you have any tweak apps running?
Sent from my Nexus 5 using Tapatalk

ticketseriously said:
OK I was wrong. After uninstalling all the apps which have an effect on my display as well as reinstalling the ROM without the Franco kernel its still having the same issue.
I left a music app running this time and then left the phone till it put itself into sleep/lock mode. The app continued to run and I could change the volume with the side buttons but when i Pressed to get the screen on it just stays black now but it seems as though everything is still running in the background. Anybody had this type of issue with PA before? Thanks
Click to expand...
Click to collapse
its sod, sleep of death. its not really known what causes it on the n5, but it happens. raising your voltages might help you, as it helps a few, but not all. if it happens that often, id see about an rma after flaahing the factory img to test.

Running beta software, custom kernel... Seems you're in for more that what you've bargained for.
Just do as simms22 says and flash latest factory image.

[Q] Nexus 5 stopped being able to vibrate

So I recently bought a Nexus 5. A short time after, I noticed that when I would type on the keyboard, it would sometimes stop vibrating. When this would happen, nothing would make it vibrate. The back and home buttons wouldn't vibrate (yes, they should according to the settings), and my phone wouldn't vibrate when receiving texts or other notifications (again, they should be). It seems the fix was to just turn the screen off and back on. Now however, it seems vibration constantly doesn't work. Nothing that should be vibrating according to the phones settings would vibrate. Occasionally, vibration would randomly start working again, but once I turned the screen off and back on, vibration would stop working again. This was on Android 4.4.4. When the factory images for 5.0 were released yesterday, I installed it on my phone using the android sdk, instead of waiting for the OTA. I figured since this caused a factory reset, that it would fix the vibration issue. Nope, still there. Is there anyway that I can fix this, or is this just a hardware issue and I'm stuck dealing with whether it wants to work or not? Oh, when it does vibrate, it doesn't vibrate weakly. It vibrates as it should.

thexlizardxking said:
So I recently bought a Nexus 5. A short time after, I noticed that when I would type on the keyboard, it would sometimes stop vibrating. When this would happen, nothing would make it vibrate. The back and home buttons wouldn't vibrate (yes, they should according to the settings), and my phone wouldn't vibrate when receiving texts or other notifications (again, they should be). It seems the fix was to just turn the screen off and back on. Now however, it seems vibration constantly doesn't work. Nothing that should be vibrating according to the phones settings would vibrate. Occasionally, vibration would randomly start working again, but once I turned the screen off and back on, vibration would stop working again. This was on Android 4.4.4. When the factory images for 5.0 were released yesterday, I installed it on my phone using the android sdk, instead of waiting for the OTA. I figured since this caused a factory reset, that it would fix the vibration issue. Nope, still there. Is there anyway that I can fix this, or is this just a hardware issue and I'm stuck dealing with whether it wants to work or not? Oh, when it does vibrate, it doesn't vibrate weakly. It vibrates as it should.
Click to expand...
Click to collapse
Hardware. The vibration module is located on the backcover and is attached by a small sticky pad which can become dislodged or loose for various reasons. Some who have the issue have reported success giving the phone a smack, others choose to open it up (careful, lots to damage) while others take the RMA route wanting to keep their warranty intact.

bblzd said:
Hardware. The vibration module is located on the backcover and is attached by a small sticky pad which can become dislodged or loose for various reasons. Some who have the issue have reported success giving the phone a smack, others choose to open it up (careful, lots to damage) while others take the RMA route wanting to keep their warranty intact.
Click to expand...
Click to collapse
Well, I'm going to avoid opening the phone up. Tried smacking it, but that has yet to work. Would Google replace the phone because of this, or am I just stuck with how it is?

thexlizardxking said:
Well, I'm going to avoid opening the phone up. Tried smacking it, but that has yet to work. Would Google replace the phone because of this, or am I just stuck with how it is?
Click to expand...
Click to collapse
Of course. If the vibration module isn't working as intended then they will accept your RMA request and send you a refurbished replacement device.

bblzd said:
Of course. If the vibration module isn't working as intended then they will accept your RMA request and send you a refurbished replacement device.
Click to expand...
Click to collapse
That's good. I hit it a couple more times, and it's working right now. I'll see how it progresses.
Thanks

[Q] Phone only rings for about one second and then stops.

After upgrading to lollipop, I have noticed when recieving a call that sometimes my phone will ring for about 1 second and then stop but continue to vibrate. I am not using any quick cover or anything. This doesnt happen all the time but it does happen quite often. Has anyone else had this problem? I'm completely stock on 5.0 (i have deleted my cache partition and the problem still persists)

c4sh said:
After upgrading to lollipop, I have noticed when recieving a call that sometimes my phone will ring for about 1 second and then stop but continue to vibrate. I am not using any quick cover or anything. This doesnt happen all the time but it does happen quite often. Has anyone else had this problem? I'm completely stock on 5.0 (i have deleted my cache partition and the problem still persists)
Click to expand...
Click to collapse
Are you using a custom ringtone?

Aerowinder said:
Are you using a custom ringtone?
Click to expand...
Click to collapse
No, just the stock tones. I find it happening sometimes with my SMS messages as well but not all the time.

Update: I have since unlocked my bootloader (wiped) and rooted my phone and the problem still persist. Seems like I'm not alone, I have starred this so hopefully someone can see it. https://code.google.com/p/android/issues/detail?id=81178#makechanges
Anyone have any suggestions that I could try?

update
I had thought I had fixed the problem by re flashing the stock image of lollipop, the problem went away and my phone started to ring again but shortly its back to only vibrating. I noticed that the little vibrate symbol was popping up in the status bar whenever I received a call, even when I turned off the also vibrate for calls option. I then remembered that when I use the volume butler app and set it to my vibrate profile that symbol would also pop up. I uninstalled volume butler and everything seemed to be working fine. Next I Checked the play store for comments regarding the issue and I noticed two things: There was a recent fix "ringtone changing to silent upon first install" and it said that the app was installed onto my device and not requiring an update even though I had just uninstalled it. So I decided to open it up and it was as if I was starting the app for the first time as none of my previous data was in there for testing purposes I decided to set up the same profiles that I had before and try calling my phone and my phone rang like it should, weird. Perhaps I had two versions and that was the one that I originally uninstalled is that even possible?( I could have sworn I had updated it,as it was under the up to date app list) Regardless, I uninstalled it again and everything is still working as it should. Hoping that this was was the culprit I will continue to test my phone and see.

[Q] Black screen after pressing home...?

Doesn't always happen but on occasion upon pressing the home button the entire screen goes black aside from status bar happen even w/o xposed enabled on stock rom hardware problem or software bug? Phone restart fixes it but it gets annoying restarting it everytime
EDIT: Power menu is also visible I have flashed my phone through flashtool already
z3 d6603

Hi. Did you find a solution to this issue? My Z3 is doing the same.
Thanks.
Sent from my D6603 using XDA Free mobile app

I have a similar problem. Randomly something will cause the screen to completely blank out. I can't see anything but I know the screen still turns on and off when I press the power button because the screen will be dimly lit when on. The only thing I can do is hold the power button down and get the power menu. Restarting fixes it. It has been happening more and more frequently. I am on the tmo rooted lollipop build with xposed.

In stock everything and get this, friends z3 does this to

I don't remember this ever happening on KitKat. It's getting really annoying and it seems to happen randomly. Sometimes on app crash/hang or just when I try to turn the screen on after getting the phone out of pocket. I wonder if its a lollipop thing.

Okay so I figured out that uninstalling the smallapps bar stuff with titanium backup was the root of my problem... if anyone else has done this definitely not a good idea haha

Stock, unmodded, didn't happen once, so I guess software problems (at least I hope for you) :/

try disabling any active app lock... this issue happened in my friends xperia z3 after the lollipop update but disabling/uninstalling app lock works sometimes.....

Did you find a solution? My z3c does exactly the same

do you guys have smart lock enabled ? Or do you have tasker/llama to activate lock/unlock based on position/network cells ?
I'm getting this bug now on a 2 month old Xperia Z3 D6683 more and more frequently and I have location based unlock rules in Llama...
I'm trying "Disable hardware overlay" in developer settings and I will see if it solves the issue.