Database Users

[Q] LED Notification

Hi,
I've finally received my Nexus 4, and quickly upgraded to Android 4.2.2
One thing I noticed is that my notification LED does not seem to light up when receiving email from the Gmail app, nor does it light up while charging the phone using the LG charger.
Edit:I've just noticed a white LED notification for email... I didn't notice it before because it was very low-key and had a large time interval.
Is it supposed to be like this, or is the phone faulty?
P.S. Does the LG charger make a rattling noise for anyone else when it is not connected to the phone?

Caleb666 said:
Hi,
I've finally received my Nexus 4, and quickly upgraded to Android 4.2.2
One thing I noticed is that my notification LED does not seem to light up when receiving email from the Gmail app, nor does it light up while charging the phone using the LG charger.
Is it supposed to be like this, or is the phone faulty?
P.S. Does the LG charger make a rattling noise for anyone else when it is not connected to the phone?
Click to expand...
Click to collapse
I know that the LED is not supposed to light up when charging (some custom ROMs have this feature though) and the charger "rattling" is a known issue.
The gmail thing is software side, for sure. So I'd say your phone is fine
Sent by carrier pigeon

klvnhng said:
I know that the LED is not supposed to light up when charging (some custom ROMs have this feature though) and the charger "rattling" is a known issue.
The gmail thing is software side, for sure. So I'd say your phone is fine
Sent by carrier pigeon
Click to expand...
Click to collapse
the led notifications on stock rom aren't that great. they have a very long pause in between each flash so it's hard to see.
download and use lightflow. i purchased it from the play store and it was definitely worth it. you will get the ability to customize how and when the led flashes and for which app you'd like to receive notifications from.

SeraldoBabalu said:
the led notifications on stock rom aren't that great. they have a very long pause in between each flash so it's hard to see.
download and use lightflow. i purchased it from the play store and it was definitely worth it. you will get the ability to customize how and when the led flashes and for which app you'd like to receive notifications from.
Click to expand...
Click to collapse
I hated LightFlow on my GNex, and I still hate it on my N4. I much prefer CyanogenMod's custom LED notifications. They actually work like they're supposed to, and don't get stuck on.

Light Flow works great on my N4. Have a look at the thread on it in the Apps forum, you'll see the number of people having problems is very small.
Sent from my Nexus 4

If you use light flow make sure to use their widget because with out it you will think that it was staying on when you didn't mark am e mail or sms read.
Sent from my Nexus 4 using xda premium

Issues with Mobile Data - Need Help

Hey guys this is my first thread and this is an issue i've been having since i first got the device.
Well, mobile data is always connected and blue, however, sometimes when i'm doing something that requires internet, it takes a while to start actually working and showing the up and down arrows. This causes delayed notifications in apps like whatsapp.
Example:
I open a whatsapp conversation. What I should get is the "last seen" status of my contact, but this takes up two 5 seconds for the mobile data connection to actually kick in.
Is this a known issue with the nexus 4? are there any fixes someone might direct me to? It's not a deal breaker but it's a really annoying issue that I didn't have back when I was using the S3.
P.S: If it matters in anyway, I'm using CM 10.1.2 Stable and the latest Franco Kernel nightly.
Thanks for annoying who might give me some helpful tips or ways to fix this. :fingers-crossed:

Rsoub said:
Hey guys this is my first thread and this is an issue i've been having since i first got the device.
Well, mobile data is always connected and blue, however, sometimes when i'm doing something that requires internet, it takes a while to start actually working and showing the up and down arrows. This causes delayed notifications in apps like whatsapp.
Example:
I open a whatsapp conversation. What I should get is the "last seen" status of my contact, but this takes up two 5 seconds for the mobile data connection to actually kick in.
Is this a known issue with the nexus 4? are there any fixes someone might direct me to? It's not a deal breaker but it's a really annoying issue that I didn't have back when I was using the S3.
P.S: If it matters in anyway, I'm using CM 10.1.2 Stable and the latest Franco Kernel nightly.
Thanks for annoying who might give me some helpful tips or ways to fix this. :fingers-crossed:
Click to expand...
Click to collapse
try raising your voltage at 384mhz to 800mV or higher
try a different rom
try a different kernel
it could be an issue with that/those apps.

simms22 said:
try raising your voltage at 384mhz to 800mV or higher
try a different rom
try a different kernel
it could be an issue with that/those apps.
Click to expand...
Click to collapse
I'll try raising the voltage and report back if it's better
This issue has been happening to me on stock rom/kernel, cm 10.1.2 and cm kernel as well as P.A and P.A kernel.
Thanks for the tip

simms22 said:
try raising your voltage at 384mhz to 800mV or higher
try a different rom
try a different kernel
it could be an issue with that/those apps.
Click to expand...
Click to collapse
Hey man, I tried raising the voltages, but it didn't seem to help that much.
Is there any other way to fix or make this issue better?
It's a bit annoying that other phones on the same network get instantaneous mobile data.
Looking forward to more advice! :fingers-crossed:

hey guys, im suffering from this problem too, & don't know how to raise the Voltage or how to change the kernel or rom ?

SlimBean 4.3 Screen Wake on Standby

***TL;DR***I know now that 4.3 has this bug and it is something we will deal with. I understand the causes, but the problem is buried in the kernel vs the ROM, you can still read my semi adventure but I wanted to make this edit to save you time if you think I found an answer. Overall WIFI is a huge trigger for screen wakes along with shotty or chattery reception.***
First off SlimBean is pretty much the best ROM I've dealt with, so many options, faster then I've ever experienced, and sharp looking. I've been sharking around these forums for 2 years afraid to ever make a name and post due to my lack of knowledge. I love the search options for finding answers that this forum offers to visitors and I've surely used it to root an old AT&T Atrix 4G and now my current DD the Glacier. Now I feel as though I have a little bit of sense of what the heck I am doing and would like to share my path to figuring out how to make SlimBean 4.3 work for me. Who knows maybe this may help some people that have similar problems.
The problem::: On a SEMI clean install of [UNOFFICIAL]SlimBean 4.3 \\ Nightly \\ 22.08.2013 I noticed the Glacier in standby would suddenly illuminated with light although the screen was black. It was enough to light to catch my eyes as I was starting to fall asleep. I ignored it until morning then paid attention to it happening all day at work on and off constantly with the WIFI off and just mobile network, then mobile network off, reboot, nothing seemed to help and I couldn't bare the thought of the phone's screen just on all the time.
After reading threads about HTC's possibly having bad screen made from Taiwan I was in disbelief that it was the Hardware as coming from a year old version of MIUI, I never had a problem with the screen. Leading to the idea it must be a software issue / user issue in which I must of rushed the install of the ROM or it's a quirk in 4.3.
Prior to reinstalling the same ROM, I went with trying other similar ROM's finding [UNOFFICIAL] Carbon 4.3 \\ Nightly \\ 26.08.2013 literally was just released, also a super customizable fast ROM. Everything went smooth until I played music through headphones and the illuminated black screen was back. Now I'm definitely convinced it's the software so I move on to the source code of these ROM's ev_glacier-nightly-2013.08.27.
Ev_glacier-nightly-2013.08.27 Had no screen wakes after 2 hours idle on mobile network only. I wasn't in a location with WIFI as I believe a network with a lot of information chatter may be causing these standby black illumination wakes. Back to SLIM.
SUPER clean install. 1) Format SD card completely 2) fresh download w/ checked md5 of Slimbean 3) Full Wipe "wipe data factory reset" "wipe cache" 4) format/system & format/cache manually just in case 5) Clear Dalvik 6) And fix permissions since although I believe it has no point but it's just so easy to click just in case. Probably doing things double.
Here I am now.. Slimbean is back and nothing but the .zip has been installed along with updating Nova Launcher. I am waiting to reinstall GAPPS so I can first isolate this problem within the ROM itself. What I am noticing is on just mobile network 2g/3g/2g+3g I do not get the phantom wakes, but with WIFI on it so far is only happening about 20-30 seconds after the phone drops into Standby and at least now it's not long lasting, just a few screen black flashes and it's gone. The entire 20 minutes or so I've been typing this, keeping an eye on the screen it's been quiet. Progress is being made.
Now I have thoroughly read up on and used Better Battery Stats, Wakelock detector, and Greenify to help isolate problems prior to the clean install and am waiting to install any Google apps (play store) up until tomorrow so I can pay more attention to my phone and make sure it's just a WIFI wake lock causing the screen to illuminate black. Also was toying with the idea of installing 3.0.64 kernel. I'm curious as to see if it's not just the WIFI wake lock, but all wake locks that actually wake the screen. Once I'm ready to install the play store I'm going to start combing through the device using these fantastic guides and the aforementioned apps...
[GUIDE] The Total Newb's Guide to Wakelocks ::: [HOW TO] Fix Your Skyrocket's Battery Life ::: [GUIDE] Insanely Better Battery Life When Idle
My goal with this long post is to share my experience and also commended these developers on these awesome ROM's. I will post much shorter updates on how I fixed or found the exact problem. Mainly after searching I saw similar issues but not this direct "random black illuminated screen" problem. Thanks, and be sure to call me out on anything contained in this post.

the waiting game
At 9 hours from 100% charge, I'm at 40% battery with on 1.5 hours of screen time. I went through all my settings and disabled all sounds and haptic feed back. I have yet to install any apps and am running off the bare bones of just the ROM. WiFi & 4g mobile data were on all night with the screen flashing only if I used it then locked it with the power button.
Thinking I can live with these timeout 2-5 flashes, I start browsing the forum from my phone, put it down to get ready for work, look back at the phone as it is flashing black screen rampantly on it's own. Then it holds the black screen for a solid minute or two.
WiFi chatter wake lock must be doing this... Reboot to recovery - wipe dalvik - wipe cache - reboot phone. Now to test just 4g network, flash happens on first screen lock, but not as rampant. Hmmm. My next step will be to wait for full battery drain / charge then I want to try the kernal I mentioned above. 3.0.64 kernel.

Funny stuff
Realizing the Kernel I wanted to flash doesn't work with 4.3, I hope at least some of the 86 people that viewed my post got a laugh. Even the older version of SlimBean causes the random screen flashes and the screen on while charging even with the ROM settings for such off. WiFi seems to be the greatest cause. It's as if wakelocks are actually being represented as screen flashes since the kernel is so powerful.
I just don't want to use the CM ROM...
I'm going to dig around the forums further and type in different key words of my problem just to make sure I didn't miss someone already answering this question. Slim has all the functions I always wanted out of my droid and I'm dead set to make it work...or just live with screen flashes I guess.
Hope this is a comedy for someone.

only other link
I've found on the issue I have.
http://forum.xda-developers.com/showthread.php?t=1148057

Non-Stop ROMS
1) SlimBean 4.2 & 4.3 Both have this black screen flicker / black screen wake / black screen on while charging.
2) Carbon 4.3 Had it black screen on while listening to music / black screen constant while charging
3) Evolve 3.3 based of 4.3 seemed to work fine, but I wasn't a fan of the larger Icons and screen, similair to CM 4.3 so I didn't leave it long enough to test...
4.3 CM 4.3 black screen wake almost constant / black screen on while charging... also didn't last long to really test everything.
I am down the river if I want this to just go away. I have installed all these ROM on a completey clean formated SD card each time
I'm sticking with SlimBean as it has the looks and reacts like I expect my phone to. After doing some more searching and after a little time has passed for more 4.3 development there may be a kernel that will work better for me.
Oh here is another dead end I've found... http://forum.xda-developers.com/showthread.php?t=2185747&page=3 [KERNEL] Fixed the flickering screen problem,CM10,CM10.1,SENSE3.6 4.0 4.1 That goes no where...

wifi
WiFi is the biggest culprit for the random screen wakes. I've just been living with it since I dig the slimbean 4.3 ROM so much. Thought I might pop back on here to make some closure. I worked on removing some apk's from the already minimal gapps I installed and will soon start a separate thread on just that. As long as after searching I don't find the same info I figured out.

I think you've got the screen flicker bug.
Try flashing the .69 kernel, it claims to stop the flicker.
Also I know it's got something to do with the WiFi. I know a little about it though.
Sent from my myTouch 4g using xda app-developers app

thanks for the response
N_otori0us_ said:
I think you've got the screen flicker bug.
Try flashing the .69 kernel, it claims to stop the flicker.
Also I know it's got something to do with the WiFi. I know a little about it though.
Sent from my myTouch 4g using xda app-developers app
Click to expand...
Click to collapse
I see you all over the place when it comes to Glacier threads. Today at work I was searching around for a download link. I read through a ton of other ROMS threads hoping it was buried in the comments somewhere. So far I only turned up and old thread with a dead link and a couple of other threads you mentioning to other people to download the .69 KERNEL which I am guessing the full version number is 3.0.69, if it's not then there may be my first problem in finding the link...
*edit
this is the main thread I keep finding, you have so many other kernels on there
http://forum.xda-developers.com/showthread.php?p=43983635&highlight=+69#post43983635

I have a little idea about the screen flicker.
A member called zyGh0st told me. I've pmed Elgin but no response.
I'll pm coderzs too Lil.
Sent from my myTouch 4g using xda app-developers app

reading about kernals
N_otori0us_ said:
I have a little idea about the screen flicker.
A member called zyGh0st told me. I've pmed Elgin but no response.
I'll pm coderzs too Lil.
Sent from my myTouch 4g using xda app-developers app
Click to expand...
Click to collapse
All the Kernels in the Glacier Bible page you have been keeping up seem old. I'm nervous to try one since they obviously seem like they won't work. I'm game to try what ever and post on here my progress so if anyone else stumbles upon the issue they can guide their way through it.
I've been searching "kernel 3.0.69", "kernels 4.3 roms", "jb rom kernel", "4.3 jb kernel", sometimes including the term "glacier" or "MT4G" with little to no luck between XDA and just google itself. I always just find ROMS that just mention the kernel but have no downloads.

Reading your older posts I see that youve already tried the kernel.
Sent from my myTouch 4g using xda app-developers app

K is for kernel
N_otori0us_ said:
Reading your older posts I see that youve already tried the kernel.
Sent from my myTouch 4g using xda app-developers app
Click to expand...
Click to collapse
I tried 3.0.64 kernel, not this mysterious .69 kernel you have mentioned. If you have a link or mirror of it I'll be glad to give it a go.
___________________________________________________________________________________________________
Found how you added the 2 kernels to the Bible page, I just flashed .64 again and I'm nothing but bootloops. I'll give .62 a chance since now I'll have to re-flash Slim.
___________________________________________________________________________________________________
make the double bootloops with either of those 2 kernels. I waited like 5 minutes, restarted the phone to see if it would boot and it just stayed on the slim splash screen. Of course I wiped dalvik and cache before installing either.

Bottom of your 5th post
Sent from my myTouch 4g using xda app-developers app

addiction
N_otori0us_ said:
Bottom of your 5th post
Sent from my myTouch 4g using xda app-developers app
Click to expand...
Click to collapse
Oh yes, I head that already downloaded on the SD but the name CM_SENSE made me think it was a ROM not a kernel. The .66 kernel link is dead, but the .58 flashed & works but there is still the flicker on 4.22 SlimBean. 4.22 is so lame compared to 4.3. Even if there wasn't a flicker on 4.22 I don't think I'd keep it. Those big ICONS are just too much. I think that's why I like Carbon also. Anywho...
My addiction to messing with my phone is always in conflict with work. As if I don't have enough problem solving to deal with outside of cell phones.
I am going to try out the recovery I see in your signature, Recovery : 4EXT 1.0.0.5 RC8, just to see if it makes a difference. If you have the same phone without the same problem I must then eliminate the different variables to find the true problem. I found a "how to" and am either going to put in the time in a couple of hours or tonight. Then I'm going to start the rounds of testing ROMS / KERNELS all over again and I'll post my findings here.
I appreciate the back and forth, I actually got a can't thank anymore message because I used up my 8 yesterday~

Living with it
I've been just living with the screen flash. The ROM is just to sweet to give up. At some point if there it a completely stable 4.3 I may upgrade.
On a regular work day I don't have any available WIFI, so I toggle it off then reboot the phone every morning. I usually get a random screen flash everytime I manually lock / turn the screen off and that's it. With WIFI on I get random flashes at random rates and for random lengths.
Playing music invokes these random black screen wakes also, I've stuck to my old blackberry as my MP3 player...I know that statement seems extemely wrong and against all sciences, but the 9780 bold works perfect as a music player. They had the long-press song skip in the volume button well before anyone added it to Android.
If ever I find the correct ROM / KERNEL combination, or someone else figures out the problem and I find it, I will post it here. This winter I am going to get more into understanding & compiling roms + digging through code so maybe I'll find it myself...ha!

tonyMEGAphone said:
I've been just living with the screen flash. The ROM is just to sweet to give up. At some point if there it a completely stable 4.3 I may upgrade.
On a regular work day I don't have any available WIFI, so I toggle it off then reboot the phone every morning. I usually get a random screen flash everytime I manually lock / turn the screen off and that's it. With WIFI on I get random flashes at random rates and for random lengths.
Playing music invokes these random black screen wakes also, I've stuck to my old blackberry as my MP3 player...I know that statement seems extemely wrong and against all sciences, but the 9780 bold works perfect as a music player. They had the long-press song skip in the volume button well before anyone added it to Android.
If ever I find the correct ROM / KERNEL combination, or someone else figures out the problem and I find it, I will post it here. This winter I am going to get more into understanding & compiling roms + digging through code so maybe I'll find it myself...ha!
Click to expand...
Click to collapse
Have fun man, and If you ever need help or guidance just tell us, we'll be here

Kit Kat Issue Summary (Upgrading or Using on Droid Line)- Please add your issues

A list of issues I've read about with KitKat.
Install
If you previously rooted like a monkey (you blindly followed instructions without understanding them), you will probably have issues upgrading - either a brick or an unrooted KitKat.
If you are on KitKat and not rooted, you have no option to root at the present time
Battery
Totally "by feel" but it seems a touch worse to me. No empirical data to back that up. tehcodeman feels his is slightly better.
Applications
Play Store would download 100% of any new app I was trying to install then get stuck. Force stopping store & clearing store cache fixed the issue
USB OTG no longer works. You can use third party apps like StickMount but they require root
Issues with Tap & Pay not working
stock mail client will not start if you swipe its notification up from active display since the KitKat update. See https://forums.motorola.com/posts/6c3888a792 . This is true for me using stock email client to MS Exchange Server.
[*]Phone won't send mms(pic/vid/group) when connected to wifi (Metfanant). I've read there is an issue with Hangouts + Kitkat and MMS on wifi (not droid specific). Some have said using default messenger works. I tested either.
Photo bucket does not work on ART. - Probably many more apps too as this is relatively new to developers.
Root
changing the SQLite db for tether no longer works - you now need to replace the entitlement apk
If you got to KitKat and didn't Slap it first and therefore have no root, you are SOL
Xposed does not work with ART - if you have it installed and try to switch to ART, the phone will reboot but you will still be dalvik.
Cant switch to ART from dalvik - doesn't take: Do you have Xposed installed? If so that's why.
Non-Root
I've read things like foxfi and other tether apps no longer work (except maybe via bluetooth)
Other
More issues (than with 4.2) with connectivity to non VZW carriers.
My Bluetooth connection to my car (VW) drops occasionally (it never did on 4.2). Not often enough to be super annoying but enough that sometimes I think I must be getting a call, email or some other notification. Comes back on its own about 5 seconds later.

BAH! I thought I was posting in Q&A forum - can a mod move it? unless it belongs here.

Almost good enough as a stickie!
fat-fingered and Maxx-ed out.

I don't see how any of those are issues with KitKat in the slightest. Maybe you mean "Limitations with KitKat"?
Also, my battery "feels" better than ever. I used it moderately at work today and had 80% charge at 5pm after unplugging it at 7 this morning.

tehcodeman said:
I don't see how any of those are issues with KitKat in the slightest.
Click to expand...
Click to collapse
Its meant to be a list of issues upgrading to, rooting, or applications on KitKat on the Droid Maxx/Ultra phones. If you don't see how the items posted are related to that....

The home key issue is the biggest annoyance for me. I was trying the Aviate launcher and it made it almost unusable.
Many people are reporting Bluetooth issues, particularly after the upgrade with existing devices. Sometimes unpairing and reestablishing the pair fixes the problem. I've done a factory reset and that seems to have fixed almost everything.
I concur about the battery. At best it is the same as before, but it's usually a bit worse - as much as an extra 1% per hour of drain compared with before. It was the same both before and after the factory reset that I did. It may have something to do with Google Play Services - I'm still waiting for the update. But I probably received the last, buggy update right around the time that I updated to KitKat last month. What's weird is that it isn't consistent - some days I end up with 40% battery, some days I end up with 60%, and usage is the same.
The only Play Store issues I've had came after the factory data reset - it took hours to reinstall all of my apps. Otherwise that's been rock-solid for me.

I noticed the Motorola Kit Kat build didn't include the Google Cloud Print app with native Android printing support. The app that's available from the play store doesn't work with the native print functionality, either. However, sideloading the Cloud Print apk pulled from a kit kat Nexus device does work.
It's disappointing that Kit Kat pulled USB OTG support. There are non-root apps like Total Commander+USB plugin or the Nexus Media Importer that can bring back partial support.

Biggest annoyance has been the home button double tap bug. Been playing with various xposed apps to try and override it, but so far not much luck. This needs to be fixed ASAP. I am currently rooted so everything else is fixable via xposed or 3rd party apps (tethering, blue status bar, etc). I've also had some random wakelocks that won't go away without a reboot (last one was the audioMix wakelock) but those aren't consistent so I can't really chalk that up to 4.4 as wakelock problems existed in 4.2.2. Otherwise 4.4 has been pretty good, and I especially like immersion mode (even with the hard buttons having a pulldown status bar is nice when you're running fullscreen games).

I don't use the stock email client - I just use Gmail - but I have read that the stock mail client will not start if you swipe its notification up from active display since the KitKat update. See https://forums.motorola.com/posts/6c3888a792

Phone won't send mms(pic/vid/group) when connected to wifi
Been like this ever since flashing the 4.4 soak test
Sent from my XT1080 using Tapatalk

*My Wi-Fi signal is not as strong as before
(Unrooted)
Sent from my XT1030 using xda app-developers app

Problems I faced:
-Setting default launcher and it keeps asking me to set it again and again.
-Lowest brightness is not as low as before.
Sent from my XT1080 using xda app-developers app

XBMC no longer works. I've tried all builds. Still works on my old phone with Jellybean
Sent from my XT1080 using Tapatalk

tCizler said:
XBMC no longer works. I've tried all builds. Still works on my old phone with Jellybean
Sent from my XT1080 using Tapatalk
Click to expand...
Click to collapse
Actually, just remembered that the fact that I'm on ART might affect it. Not sure though
Sent from my XT1080 using Tapatalk

Google Play services keeps force closing since I upgraded to 4.4... really don't want to have to do a FDR but I can't find another fix

rmjones2006 said:
Google Play services keeps force closing since I upgraded to 4.4... really don't want to have to do a FDR but I can't find another fix
Click to expand...
Click to collapse
Settings---->apps---->slide over to all---scroll down to Google play services select it then uninstall updates.
Sent from my KitKat Ultra

Everyone else is able to send MMS with WiFi enabled?...grrr
Sent from my XT1080 using Tapatalk

Metfanant said:
Everyone else is able to send MMS with WiFi enabled?...grrr
Sent from my XT1080 using Tapatalk
Click to expand...
Click to collapse
Yes. You do have a data connection other than wifi correct? MMS will not send over wifi
Maxx'd out Kit Kat

Settings>Battery>Battery Saver won't stay toggled on. Happened on my original and replacement device (not replaced for this particular issue)
Looks like 4.4.2 is coming to the MotoX soon so we shouldnt be far behind
http://phandroid.com/2014/01/20/at-...zon-moto-x-has-been-updated-to-android-4-4-2/

Topsnake said:
Yes. You do have a data connection other than wifi correct? MMS will not send over wifi
Maxx'd out Kit Kat
Click to expand...
Click to collapse
Yes I do...its odd...I can recieve MMS (pics/bids/group) with WiFi on...but when I go to send them it seems like the phone won't kick over to cellular data to send...
If I disable WiFi they send fine
Sent from my XT1080 using Tapatalk

[Q] Nexus 4 doesn't vibrate

Hi everyone,
I bought my nexus 4 about a year ago, and very recently I decided to give Cyanogenmod a try. I must say this was the first custom ROM I flashed on my device, and I'm quite fond of it. I also flashed a modified version of the latest franco.kernel for CM (http://forum.xda-developers.com/showpost.php?p=53707610&postcount=459)
The thing is that I noticed that my phone doesn't vibrate when it's supposed to. In fact, it doesn't vibrate at all; no matter what I try, it just doesn't. For the record, it had been working flawlessly until a few days ago.
So far I've tried:
- Disabling/Enabling vibration in keyboard, notifications and calls
- Rebooting my device several times
- Updating to 20140723 nightly (I was previously on M8)
- Disabling quiet hours
I've been doing some reading, and some old threads advise to perform a factory reset, but it's kind of a hassle for me to re-sync all the photos and stuff. So, is there anything I should try before I do a factory reset? Should I try and flash a different kernel/go back to stock kernel?
Thanks

It's most likely a hardware issue. I'd backup the phone and then flash the factory image. If it still doesn't vibrate it's a hardware issue. It doesn't cost much to replace the vibrator. Do it yourself or find a local cell repair shop.
Sent from my Nexus 5 using XDA Free mobile app

I would rather change the kernel first and see if there is any issues.

I flashed the latest CM nightly, which also changes the kernel to CM stock. This time you can hear the little buzz when you turn on the phone, but that's pretty much all the vibration I get. Phone calls and haptic feedback still don't work. At least, I know it's not a hardware issue.

ant_cc said:
I flashed the latest CM nightly, which also changes the kernel to CM stock. This time you can hear the little buzz when you turn on the phone, but that's pretty much all the vibration I get. Phone calls and haptic feedback still don't work. At least, I know it's not a hardware issue.
Click to expand...
Click to collapse
I still think it's hardware. Roms can change the force it vibrates at. But if it's still low the vibrator is bad.
Sent from my Nexus 5 using XDA Free mobile app

jd1639 said:
I still think it's hardware. Roms can change the force it vibrates at. But if it's still low the vibrator is bad.
Click to expand...
Click to collapse
Maybe I wasn't very clear; the vibration force is OK, but the thing it that it only vibrates on startup, it doesn't buzz in incoming calls or any of that. So that's why I think the vibrator isn't broken