Develop Bugs

[Q] Notification sound and vibrate not working

For some reason the notification sound and vibrate won't work on my Galaxy Nexus for long periods of time even though they are set to. It doesnt matter what the notification is for, text message, facebook, gmail, etc I will not get a sound or a vibrate to let me know, just the LED will flash. It will be like this for hours and then work for a bit and then stop working again! What is going on? I'm running stock 4.0.2

For me sounds work but vibrate for notifications doesn't
Sent from my Galaxy Nexus using Tapatalk

karallam said:
For me sounds work but vibrate for notifications doesn't
Sent from my Galaxy Nexus using Tapatalk
Click to expand...
Click to collapse
Go into settings that are in the sms app and select vibrate always, it will be way at the bottom
Sent from my Galaxy Nexus using XDA App

For me I have absolutely no clue what the problem is. I know its not settings because I have looked everywhere plus it goes back and forth between working for a bit and not working for a long time all on its own. I've even tried a factory reset and the problem persists. Could it be a hardware issue?
Sent from my Galaxy Nexus using xda premium

Same problem for me, vibrates for phone calls, and when shutting down, also when turning volume down, but not for any other notifications. (Yes, I set all the individual settings to "vibrate".) Must be a bug with the phone, lots of others are complaining about this problem as well. Hopefully this will be fixed with an update.

bovineyard said:
Same problem for me, vibrates for phone calls, and when shutting down, also when turning volume down, but not for any other notifications. (Yes, I set all the individual settings to "vibrate".) Must be a bug with the phone, lots of others are complaining about this problem as well. Hopefully this will be fixed with an update.
Click to expand...
Click to collapse
Have you looked here in the sms settings
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sent from my Galaxy Nexus using XDA App

Just tried Sound Manager V2, and set vibration to "vibrate whenever possible". Now all is well! Disappointing that this setting does not work in Android settings though.

So I know this thread is pretty old but I never did find a solution to this problem and thus got rid of my Galaxy Nexus and went to an iphone for a while. I have a galaxy Nexus again and am having the exact same problem. I have done everything everyone has suggested and trust me it has nothing to do with settings. For a while notifications will work as they are supposed to but then they will suddenly stop working properly (won't vibrate or make the sound) until i reboot the phone and then it will work for a short period before not working again. I've tried a factory reset and all that fun stuff and nothing helps.

Sound Manager V2 worked for me
Same issue here, and Sound Manager V2 fixed the vibration issue for me. Had every vibrate setting I could find set to always vibrate and yet my phone would only vibrate on the vibrate only setting.

I hate to bump an old thread... but, it perfectly explains my issue. Has anyone ever discovered the cause or a fix for this? All of my settings are properly enabled. The issue seems to occur any time I switch the phone to "vibrate" mode, using either the volume rocker or the power menu. Whenever I try and turn the volume back up (again, either via volume rocker or power menu), notifications stop completely, except for the notification light. Reboot fixes the issue each time. But, it's very frustrating, and reminiscent of the BlackBerry days of battery pulls. Ugh!

same problem
same here -_-

Jellybean problems

First off, if this has already been done then sorry im obviously blind, if not then i think its a good place to post any jellybean related problems and fixes that people have discovered.
so here goes, i updated from the ota on thursday the 12th of july i had a totally stock yakju device with the build number imm761 (JRO03c after update)
problems i have found so far are
1.after every reboot the, screen stay awake during charging option is ticked in developer settings
2.the google now command of navigate me home will take you to a random address near your home even after setting home address in navigation app and in latitude (as far as i can tell this is only happening outside the us)
3.lock screen will only ever say 99% charged even when in battery settings it reports fully charged
i have not found a fix for any of these issues nor do i know if they are just problems on my device (barring the google now navigate me home command)
so if anyone could report if they have the same issues or have found fixes please post here.
thanks

Now has stopped listening for the keyword "Google". After a couple days with out reboot it seems that Now no longer responds when I say Google. I have to hit the mic button. A reboot would fix it... but a weird bug to say the least.

GldRush98 said:
Now has stopped listening for the keyword "Google". After a couple days with out reboot it seems that Now no longer responds when I say Google. I have to hit the mic button. A reboot would fix it... but a weird bug to say the least.
Click to expand...
Click to collapse
yes i knew i forgot something thanks also the option to enable this feature randomly disappears

I have a big problem since I did update to Jellybean
My phone charge itself, without it connected to AC power or PC.
And when I want to charge the power source does not load.
Last night I put in charge and not loaded than when we closed and I pressed power button + down button.
and camera, how do I set resolution? I make pictures. PNG 720x1280 on ICS I could change the resolution,
Jealybean sucks
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Shot at 2012-07-19

tuice said:
My phone charge itself, without it connected to AC power or PC.
Click to expand...
Click to collapse
You have reached the Holy Grail of getting power to a mobile device—this is not a problem/consider yourself very lucky.

I do not think this is too good for battery life, and actually not charge only indicate that charge

Probably hardware issue.
Sent from my Galaxy Nexus using Tapatalk 2

omrij said:
Probably hardware issue.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
I didn't have this before upgrading to Jealybean

tuice said:
I didn't have this before upgrading to Jealybean
Click to expand...
Click to collapse
That's a pretty common Samsung issue, usb port dirty, faulty.
Either clean it or go to repair.

leeskywalker said:
2.the google now command of navigate me home will take you to a random address near your home even after setting home address in navigation app and in latitude (as far as i can tell this is only happening outside the us)
3.lock screen will only ever say 99% charged even when in battery settings it reports fully charged
i have not found a fix for any of these issues nor do i know if they are just problems on my device (barring the google now navigate me home command)
so if anyone could report if they have the same issues or have found fixes please post here.
thanks
Click to expand...
Click to collapse
2) I'm in the UK and don't have this bug, ensure your home address is set correctly on maps.google.com and that when you click it the pointer is showing your house only and not a generic area.
3) Again, not experienced this. My lockscreen shows 'Charged' when at 100%
Sorry fella

I can't speak to the first two problems but I can confirm that it only charges to 99%. It's been that way on every ROM I've used since stock 4.0 so now I just say 'close enough'.

Taboobat said:
I can't speak to the first two problems but I can confirm that it only charges to 99%. It's been that way on every ROM I've used since stock 4.0 so now I just say 'close enough'.
Click to expand...
Click to collapse
i found after a reboot while plugged in it will go to 100%

cymru said:
2) I'm in the UK and don't have this bug, ensure your home address is set correctly on maps.google.com and that when you click it the pointer is showing your house only and not a generic area.
3) Again, not experienced this. My lockscreen shows 'Charged' when at 100%
Sorry fella
Click to expand...
Click to collapse
i have my address set in every possible place of my google account still no luck

I've never been able to get Google Now to start voice recognition by saying Google. I was beginning to think it was just a myth. Any ideas how to force it?
Sent from my Galaxy Nexus using Tapatalk 2

tuice said:
I do not think this is too good for battery life, and actually not charge only indicate that charge
Click to expand...
Click to collapse
Battery stats is what's responsible for indicating charge to my knowledge. Try wiping battery stats in CWM

tuice said:
I have a big problem since I did update to Jellybean
My phone charge itself, without it connected to AC power or PC.
Click to expand...
Click to collapse
I've seen this happen before on a brand new HTC X One, happened after about 4 days of being used. We let the phone fully run down and then just changed it, didn't come back again.

Echo after Rooting Galaxy S3, other issues

I rooted my Sprint Galaxy S3 last week and have had some problems with echoes since then on the normal handset and on Bluetooth. This is after finding suggestions to turn off noise reduction. I didn't have this problem prior to the rooting. I used this tutorial at this link http://forum.xda-developers.com/showthread.php?t=1743780. I have not been able to find anyone else with this problem, I do have backups using Titanium afterwards and have tried it again and even without the backups. Any suggestions appreciated.
"This video will show you the latest and easiest method to root the Sprint, ATT, T-Mobile and Rogers Samsung Galaxy S III! No data will be wiped. If you have any questions at all, please ask! THIS WILL WORK ON 4.1.1 JELLY BEAN"

Are you running a custom a Rom?
Sent from Pluto.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

No just the stock ROM

Anyone? Should I try a new ROM?

Anyone? Should I try a new ROM?

Try a different ROM, if its still happening, its most likely a hardware issue
I dont think theres any "setting" that rooting it could have changed and introduced the echo
Sent from my PG06100 using xda premium

I can try one, I wasn't doing this until the root, its the stock ROM now. Any ROM suggestions?

same on tmobile
yeah i'm having a similar problem too on my tmobile s3 but it only happens when i have a custom rom(i tried a couple custom roms and they all seem so have the same effect). when i go back using my nandroid back up of the stock rom and kernel, the problems not there anymore... and turning off noise reduction seems to work for some ppl but not mine. i noticed that the closer u talk to the bottom of the phone, the less echo there is. so maybe the second mic on top is reacting too?
-------------------------------------------------------------------------------------------------------------------------------------------------------
i'm new to this, so any tips would b nice!:laugh:

I'm having the same issue -annoying echoes on my phone after rooting. I figure it's probably part of the beast - I'm finding my S3 to be a very strange bird indeed.
Sent from the house halfway up the next block

echo
sparkie6point0 said:
I'm having the same issue -annoying echoes on my phone after rooting. I figure it's probably part of the beast - I'm finding my S3 to be a very strange bird indeed.
Sent from the house halfway up the next block
Click to expand...
Click to collapse
Mine has just started doing the same thing. any fix?

I did a dirty flash and it fixed the problem
Sent from my SPH-L710 using xda app-developers app

Rooted GS3, stock Touchwiz
I was having the annoying echo when calling anyone on any set, any carrier. Noise cancellation on or off, did not make a difference. had tried to disable all sorts of voice activation....nada.
So got frustrate and did a full data wipe. After setting all accounts and apps back to normal (no nandroid and/or titanium baks), problem was solved! I was so relieved!
One day I accidentally opened S voice by clicking home twice, then called my wife after some time....hated echo in my ear was back!
I then rebooted to recovery, cleared cache and dalvik a couple of times and made another test call.
All back to normal.
I'm thinking about forcefully removing S Voice (should be called @$$ Voice)....
NOTE: as S Voice is a system app, I think to remove it I'd need to fiddle with the system/app folder and remove the apk...however, the application can actually be disabled! Will report back on results

Maybe BT is the issue?
So yesterday I kept S Voice disabled from app manager, then I would connect and disconnect from my car's bluetooth as I needed. The echo would still return and it would only go away if I rebooted. I also did the eq/sound check for right/left ear available from the dialer's menu just to rule it out: no difference. Echo still there. Rebooted phone, called from car BT, no echo.
As of now my last call after a reboot was fine, no echoes. I will keep the phone in the current state but WILL NOT turn off BT as I usually do during the day to save battery. Wil test later and report back.
One more thing, i noticed when the echo appears on BT, it also appears using the gs3 normally talking from it.

Echo is gone, day 2
Hello Everyone!
So I've been watching my phone since my original post here last week. I have to say there was nothing really I could pinpoint that would cause the echo. Noise cancellation ON or OFF, on my car's BT or not, on the phone's original wired headset...echo will go away ONLY if I rebooted a couple of times or did a factory reset from recovery. Mind you, the fix would only last for one or two calls. After that I'd have to either reboot multiple times or go to recovery and reset everything. So......
I finally broke down and called Sprint for a repair/diagnostics. Fortunately there is a center right by my house! Unfortunately it'll cost me between $50 and $100 just for the appointment...
I then proceeded to reset counters (gigantic thanks go to chainfire for his triangle-away which I bought to support the team!) un-root my GS3, remove apks than might hint at a rooted phone, rebooteed.
And what do you know? Echo is GONE....
It has been 2 full days and many calls (my wife is an angel....) made without a reboot or a factory reset.
I also have to add that since I was getting tired of TouchWiz, yesterday afternoon I replaced my launcher with Apex.
Does anyone think the launcher would affect the echo issue in any way?
BTW I always use qbking77's root/unroot instructions. Thanks go to him for always having an answer and a way!
Hope all this helps anyone in fixing his/her GS3 because it is in the end a great phone, and if a definite solution is found, I'll sure root my phone again!

LG G4 screen turning itself on after timeout/lock

I've had the G4 since it was launched and until now been very pleased. A couple of days ago it started to turn the screen on by itself every time it timed out or I pressed the lock button... Unless it's plugged into a charger.
I've tried pulling the battery and uninstalling any recent apps I'd installed but to no avail.
Annoyingly, by the time I got myself to carphone warehouse to get it sorted I was just outside my 28 days.
Seen a lot of people having issues with the screen but can't find anyone having this exact problem. Anybody experiencing similar? Any thoughts? Cheers.
Sent from my LG-H815 using XDA Free mobile app

Guess there's not a lot of people suffering the same issue... Noticed something odd today with the battery. Never seen it drain this fast before, is there any way the screen issue could be related to the battery? It would kinda corroborate that the phone acts totally normal when it's charging... Trying to find someone else with this phone to try swapping batteries is... Difficult.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sent from my LG-H815 using XDA Free mobile app

Factory reset.

Done it, twice.
Sent from my LG-H815 using XDA Free mobile app

Do you have a screen protector on? If you do, is it possibly covering the light/prox sensor?

Nope, no protector, and I often manually cover the proximity sensor to demonstrate more easily what the phone's doing. Screen times out straight away and them comes back on just as quickly.

Same issue here
Sorry to drag up a thread but ive been having this issue from day 1 and its driving me MAAAAD! Press the lock screen button, the second the screen turns off it comes back on and its on the lock screen (like it would if i used the power button to unlock it)
I turned on "show touch screen touches " in developer options to see if the screen protector was touching anything but its not As far as i can tell it looks like the lock screen sensor might be dicky/weak from the factory? Major sads considering its the button I use on a hourly basis!
Any help or ideas greatly appreciated, i dont really fancy taking it back after 4 weeks to have it sent of for months to be looked at/repaired

H815P suffering the same but mine is randomly. I hardly ever notice but sometimes I just look at the phone and the screen is on.

Also same issue it s wake up randomly, screen is on suddenly and turn off, any solution?

volkie1912 said:
Also same issue it s wake up randomly, screen is on suddenly and turn off, any solution?
Click to expand...
Click to collapse
do you use greenify on unrooted phone?

vati said:
do you use greenify on unrooted phone?
Click to expand...
Click to collapse
yea, i am using greenify on unroot phone

volkie1912 said:
yea, i am using greenify on unroot phone
Click to expand...
Click to collapse
That is the problem.
if yo use the auto hibernate in greenify, it wakes up the phone, turns on the screen than after hibernation turns off the screen. That is why I use only the manual hibernation. On unrooted phone it cause more battery drain than running the pr in the background

vati said:
That is the problem.
if yo use the auto hibernate in greenify, it wakes up the phone, turns on the screen than after hibernation turns off the screen. That is why I use only the manual hibernation.
Click to expand...
Click to collapse
himm thanks for your help, also if i rooted the phone, no anymore wakeups on lock screen?

volkie1912 said:
himm thanks for your help, also if i rooted the phone, no anymore wakeups on lock screen?
Click to expand...
Click to collapse
yes, on rotted phone the grennify is working as system app in the background and makes the hibernation without waking up the phone and screen + on rooted phone you can hybernate system apps too.

vati said:
es, on rotted phone the grennify is working as system app in the background and makes the hibernation without waking up the phone and screen + on rooted phone you can hybernate system apps too.
Click to expand...
Click to collapse
Thanks for info dude[emoji106]
Sent from my LG-H815 using Tapatalk

vati said:
yes, on rotted phone the grennify is working as system app in the background and makes the hibernation without waking up the phone and screen + on rooted phone you can hybernate system apps too.
Click to expand...
Click to collapse
Hi there! thank you for the post thread! I recently got changed of my LG G4 motherboard by LG as I had another problem, and since I got back my phone it keeps turning the screen on-off randomly. I tried to change the auto-screen-off setting you described (hibernation) but the screen keeps turn on and off itself every 15secs! I even changed the phone settings to no background processing at all but same thing on and off again.. I did several factory resets, even tried not to install any app or even update the basics ones and keeps doing it randomly. I dont know what to do here please any help would be appreciated :S:crying:

turn off daydream clock in display settings
---------- Post added at 11:07 PM ---------- Previous post was at 11:06 PM ----------
choroz_niki said:
Hi there! thank you for the post thread! I recently got changed of my LG G4 motherboard by LG as I had another problem, and since I got back my phone it keeps turning the screen on-off randomly. I tried to change the auto-screen-off setting you described (hibernation) but the screen keeps turn on and off itself every 15secs! I even changed the phone settings to no background processing at all but same thing on and off again.. I did several factory resets, even tried not to install any app or even update the basics ones and keeps doing it randomly. I dont know what to do here please any help would be appreciated :S:crying:
Click to expand...
Click to collapse
turn daydream clock display settings

Hey its the sensors next the the front camera that is causing this i had this look reply typed and it just disappeared but long story short i noticed it didnt down it when the phone was facedown so i tried covering the sensors next to the front camera and it didnt do it at this point it could just be a program error or hardware problem idk how it turn off the sensors and it may look tacky but use something to cover the sensors and you should be fine im not 100% sure this is the problem im still testing but so far it works

Try disabling knock to wake feature. I recently noticed that I could tap anywhere and then again somewhere else, minutes later, and the screen would turn on. It was so sensitive that sometimes it would wake by just blowing on the screen.
To get to this setting, I created an activity widget using Nova launcher. (It's under the Settings -> Knock settings).
You can also use Better Battery Stats or Amplify to see what's keeping your screen on

fixed mine
Here you go...
Settings > Display > Motion Sensor Calibration

LineageOS 7.1.1 G900T randome blue black screen

I have a G900T running Lineage OS 7.1.1 latest build. When I am out and want to use my phone I keep getting this screen, and I want to know how can I fix it. I keep having to remove my battery and reboot to clear it up until it happens again. Any ideas?
https://www.dropbox.com/s/eeir3ey2u6sy9gl/2017-04-08%2014.25.56.png?dl=0

I am just wondering if I am the only one having this issue?

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
我從使用 Tapatalk 的 SM-A800IZ 發送

The image is not showing.

Maverick923 said:
I have a G900T running Lineage OS 7.1.1 latest build. When I am out and want to use my phone I keep getting this screen, and I want to know how can I fix it. I keep having to remove my battery and reboot to clear it up until it happens again. Any ideas?
https://www.dropbox.com/s/eeir3ey2u6sy9gl/2017-04-08 14.25.56.png?dl=0
Click to expand...
Click to collapse
Are you saying it doesn't happen at home? Maybe something to do with location or data? Or is it just not waking up properly?
(When I first instilled 7.1.1 I had a black screen from boot but I had the notification bar showing and other layers like power menu would show, is your whole screen black)

IronRoo said:
Are you saying it doesn't happen at home? Maybe something to do with location or data? Or is it just not waking up properly?
(When I first instilled 7.1.1 I had a black screen from boot but I had the notification bar showing and other layers like power menu would show, is your whole screen black)
Click to expand...
Click to collapse
That is exactly what I am saying. Sometimes I just look to see the time. When I press the power button to wake it up when it does happen which is quite a bit and I never know when.
When it does happen it will wake on that screen and sometimes I will see the lock screen for a second then it goes to that. I need to then remove the battery and reboot the phone.
This mostly seems to happen when I am out. Usually when I need to do something at the worst time.
Then if I am looking something up for someone, I need to be telling the person holdup while I reboot my phone.

Maverick923 said:
That is exactly what I am saying. Sometimes I just look to see the time. When I press the power button to wake it up when it does happen which is quite a bit and I never know when.
When it does happen it will wake on that screen and sometimes I will see the lock screen for a second then it goes to that. I need to then remove the battery and reboot the phone.
This mostly seems to happen when I am out. Usually when I need to do something at the worst time.
Then if I am looking something up for someone, I need to be telling the person holdup while I reboot my phone.
Click to expand...
Click to collapse
strange that you get that screen, otherwise it sounds a bit like people who have lock screen issue & have to reboot to get phone working again. Related to display &/or touch problem I think
This is often caused by dropping their phone, have you? Knocking it on different edges sometimes fixes it, but you need to be careful not to break screen! Though better solution probably is to open it and reseat pcb, screen connectors etc.
Also using magnetic phone covers can do this, I think.
Else can't think of anything apart from software (affecting your phone only it seems) maybe clear data on lock screen service app .... maybe clear any profiles you are using ...... else the dreaded factory reset or clean flash, but I'm sure you know that and don't want to do it!

IronRoo said:
strange that you get that screen, otherwise it sounds a bit like people who have lock screen issue & have to reboot to get phone working again. Related to display &/or touch problem I think
This is often caused by dropping their phone, have you? Knocking it on different edges sometimes fixes it, but you need to be careful not to break screen! Though better solution probably is to open it and reseat pcb, screen connectors etc.
Also using magnetic phone covers can do this, I think.
Else can't think of anything apart from software (affecting your phone only it seems) maybe clear data on lock screen service app .... maybe clear any profiles you are using ...... else the dreaded factory reset or clean flash, but I'm sure you know that and don't want to do it!
Click to expand...
Click to collapse
Yeah this only started happening after installing Lineage OS 7.1. I will try another lock screen. Hopefully that will take care of it. You are right I don't want to do a reset.

Maverick923 said:
Yeah this only started happening after installing Lineage OS 7.1. I will try another lock screen. Hopefully that will take care of it. You are right I don't want to do a reset.
Click to expand...
Click to collapse
hope it works or an update to a future release of LOS just fixes it, as happened with my notification bar