Related
Hi Nexus 10 owners,
Love my Nexus 10 but I have an issue with the notification light under the screen.
It was working fine when I first got it on Friday, with it dimming on and off when an email is received.
But since yesterday, it hasn't light up at all, for any notifications, and I do have the "Pulse Notification Light" checked in setting.
So I was wondering if anyone else have any problems with the notification light? Could it be a bug, or perhaps my light broke after the first day?
Thanks in advance for any response.
I might suggest trying https://play.google.com/store/apps/details?id=com.coolbeans.ledtester&hl=en to see if your light still works
espionage724 said:
I might suggest trying to see if your light still works
Click to expand...
Click to collapse
Thanks for the suggestion.
Just tried the app and there's no light.
However, could it be that this app doesn't work on the Nexus 10 yet?
imistw said:
Thanks for the suggestion.
Just tried the app and there's no light.
However, could it be that this app doesn't work on the Nexus 10 yet?
Click to expand...
Click to collapse
Yea it might be possible that app doesn't work; may want to see what an actual N10 owner has to report though
Works fine on my N10, only flashes white though, regardless what colour I pick.
Sent from my Nexus 10 using Tapatalk 2
alias_neo said:
Works fine on my N10, only flashes white though, regardless what colour I pick.
Sent from my Nexus 10 using Tapatalk 2
Click to expand...
Click to collapse
So I guess it's really just my N10 then.
Thanks though.
No problem, try reflash with stock images and you might get lucky. My Nexus 10 is buggy as sh** and I put it down to 4.2. It'll all get sorted out soon enough, hopefully yours is just a bug too. Hope you solve it.
Sent from my Nexus 10 using Tapatalk 2
UPDATE
Just reset my N10 and now the notification light works again.:victory:
Guess it must have been one of the app interfering with the light.
BTW, when I tested it with a LED tester app, it can actually show green, red, blue and purple lights.:good:
alias_neo said:
No problem, try reflash with stock images and you might get lucky. My Nexus 10 is buggy as sh** and I put it down to 4.2. It'll all get sorted out soon enough, hopefully yours is just a bug too. Hope you solve it.
Sent from my Nexus 10 using Tapatalk 2
Click to expand...
Click to collapse
Thanks, I actually just solved it so now I am happy. haha
BTW, what do you mean by reflash with stock image and put it down to 4.2?
imistw said:
Thanks, I actually just solved it so now I am happy. haha
BTW, what do you mean by reflash with stock image and put it down to 4.2?
Click to expand...
Click to collapse
If I understand right, he just flashed a factory 4.2 image from Google, without any OTA updates.
You can get the factory software from the Google developer site and you can download it to your nexus device in case anything gets messed up.
By "put it down to", I mean I blame 4.2 (Android version on the Nexus 10) for all the bugs I'm having. It's a new OS, and this multiuser stuff amongst others means some pretty major changes so I expect it to be a little unstable for a while. Still a better state than honeycomb was when I bought my XOOM on launch day, boy was that a mess.
You're right about the lights, I just got it to work with all the different colours, cyan and then purple look nice
Sent from my Nexus 10 using Tapatalk 2
alias_neo said:
You can get the factory software from the Google developer site and you can download it to your nexus device in case anything gets messed up.
By "put it down to", I mean I blame 4.2 (Android version on the Nexus 10) for all the bugs I'm having. It's a new OS, and this multiuser stuff amongst others means some pretty major changes so I expect it to be a little unstable for a while. Still a better state than honeycomb was when I bought my XOOM on launch day, boy was that a mess.
You're right about the lights, I just got it to work with all the different colours, cyan and then purple look nice
Sent from my Nexus 10 using Tapatalk 2
Click to expand...
Click to collapse
Wow, I did not know about the factory software from the Google developer site. Guess i learned something new today. :laugh:
UPDATE #2
The notification light is not working again
Reset my N10 again, then performed a LED light test each time I install a new app.
Until the last app installed, the notification light was working, then after a few minutes it stops working again.
So I guess it's not really caused by 3rd party apps.
So I ask again, has anyone had problem with their N10's notification light?
Still hoping that it's a bug instead of just me having a defective unit.
Thanks again!
I'm having the same issues. Sometimes the LED seems to be working, others it's not. I installed LED tester and again, sometimes it works fine and others not at all. I have tried to spot a pattern to see what causes it to stop and start and have drawn a blank - no idea. I have since installed light flow but this has not helped. Seems to me that there is either a software bug and we haven't yet figured what the trigger is, or there is a dodgy hardware batch (I hope it's the former!)
hefferman said:
I'm having the same issues. Sometimes the LED seems to be working, others it's not. I installed LED tester and again, sometimes it works fine and others not at all. I have tried to spot a pattern to see what causes it to stop and start and have drawn a blank - no idea. I have since installed light flow but this has not helped. Seems to me that there is either a software bug and we haven't yet figured what the trigger is, or there is a dodgy hardware batch (I hope it's the former!)
Click to expand...
Click to collapse
I think I've found the trigger. If I turn the device completely off, and turn it back on with the charger plugged in, notifications work. If I turn it back on with the charger unplugged, notifications do not work.
Other things I have tried which made no difference included factory reset and factory reflash.
Can some other folks see if their behavior matches mine? I have a replacement device being shipped to me, but if this is a software problem I'd rather not swap hardware. I'm very curious to hear if there are any devices that have a working LED under both boot up scenarios.
I think you are right. LED notifications were working ok when I had a freeze in google now. I restarted (on battery) and tested the notifications - no LED. I plugged in the charger, restarted the system and retested - LED working again. Looks like we have a workaround and a confirmed software bug rather than a hardware fault.
I'll test when I get home, but, I've only ever noticed the light when my tablet is plugged in, so it could be the same for me too. Shouldn't be a major problem, will get fixed in the next update as long as Google are aware.
alias_neo said:
I'll test when I get home, but, I've only ever noticed the light when my tablet is plugged in, so it could be the same for me too. Shouldn't be a major problem, will get fixed in the next update as long as Google are aware.
Click to expand...
Click to collapse
I'm not entirely sure, there are people who are claiming that their LED works 100%.
kftrav said:
I think I've found the trigger. If I turn the device completely off, and turn it back on with the charger plugged in, notifications work. If I turn it back on with the charger unplugged, notifications do not work.
Other things I have tried which made no difference included factory reset and factory reflash.
Can some other folks see if their behavior matches mine? I have a replacement device being shipped to me, but if this is a software problem I'd rather not swap hardware. I'm very curious to hear if there are any devices that have a working LED under both boot up scenarios.
Click to expand...
Click to collapse
Just tried this but still nothing.
Called Google today and they are sending me a replacement.
Ok, this is ridiculous.
Just unplugged my N10 and now the notification light is working.
So apparently it's working randomly.
Hopefully my replacement device works 100% of the time.
BTW, are replacement devices new, or refurbished?
Well. It worked up until about 20 mins ago. Then randomly just stopped working. Ive rebooted, shut down, enabled and disabled the feature in settings. Fixed permissions for the heck of it. Cleaned the screen. Reset calibration, etc. Nothing seems to work. I can double tap to shut the screen off easily, and it works flawlessly, but trying double tap to wake is completely useless. Any suggestions?
Sent from my LG-LS980 using xda app-developers app
Burkettacb said:
Well. It worked up until about 20 mins ago. Then randomly just stopped working. Ive rebooted, shut down, enabled and disabled the feature in settings. Fixed permissions for the heck of it. Cleaned the screen. Reset calibration, etc. Nothing seems to work. I can double tap to shut the screen off easily, and it works flawlessly, but trying double tap to wake is completely useless. Any suggestions?
Sent from my LG-LS980 using xda app-developers app
Click to expand...
Click to collapse
Wow this is happening to me as well. I'm running the optimus rom currently. I'm reverting to stock here shortly in hopes for the KK update soon so I'll see if that fixes it.
nope. up to date stock zva now and knock on doesnt work but knock off does work as you stated. well this is wierd.
Well thats ****ing depressing
Sent from my LG-LS980 using xda app-developers app
Tons of lg users are experiencing this issue. Its a design flaw with a hardware component that easily breaks. Wonderful build quality -_-...right. So only option is replacing the phone. But to how soon, until the other one breaks. So its kinda like. Well. This blows. I suppose Ill install a custom kernel and enable screen wake features that way.
Sent from my LG-LS980 using xda app-developers app
Okay. So after hours of tapping. Which might i add. My fingers hurt, I am now able to activate the screen. Pausing after each tap, using my finger print area to tap "not to be confused with finger tip". The screen will activate. Also note, the standard two taps works sometimes, but with four presses, i seem to get the best results. Give it a try people. I have a theory the hardware has not failed. But yet, the activation area pixel size value changed. Either due to a conflicting app install. A intermittent system glitch etc
Sent from my LG-LS980 using xda app-developers app
I'm having the same issue with my G2. Knock-on/off was working fine. Had the phone in the sun for a little while (maybe 2 hours) and the knock-on has stopped working completely. Used a drawing app on my screen and found no dead pixels or strips. Knock off still works perfectly though.
This could also be an issue with your proximity sensor. If something (screen protector, finger, dust, etc.) is blocking your proximity sensor, it could be reporting to the phone that it is in a pocket, and to keep the screen off. Try to clean that area, and avoid obstructing the sensors "view". As for the leaving it in the sun, you could have damaged the sensor? You could test it by making a call real quick and see if the screen turns on when you pull the phone away from your face.
Sent from my LG-LS980 using XDA Premium 4 mobile app
The sensor seems to be working fine. Just tested it.
DrZeuss said:
I'm having the same issue with my G2. Knock-on/off was working fine. Had the phone in the sun for a little while (maybe 2 hours) and the knock-on has stopped working completely. Used a drawing app on my screen and found no dead pixels or strips. Knock off still works perfectly though.
Click to expand...
Click to collapse
Ya i got the same problem....at home it works perfect but when i went outside in the sun i can double tap like hell and screen didnt turn on(it turns on but cant see anything because its too dark like screen brightness is lower than low)...also power button didnt work...the proxi sensor is ok...i run the test menu and it shows that everything is ok...i also sent it back to my carrier and after a week of testing got it back. They found nothing and said that my described problem is a "feature".... sometimes it turns on after tapping und pushing the power button like hell and sometimes it doesent..
Your screen turns also on with very very low brightness or it is off? When u look really really close u can see it...for example hold power button and u can hardly see the white power off/reboot popup...but i dont know where the problem can be...germany d802 version..(Sorry for my BAD english)
4NDR345 said:
Ya i got the same problem....at home it works perfect but when i went outside in the sun i can double tap like hell and screen didnt turn on(it turns on but cant see anything because its too dark like screen brightness is lower than low)...also power button didnt work...the proxi sensor is ok...i run the test menu and it shows that everything is ok...i also sent it back to my carrier and after a week of testing got it back. They found nothing and said that my described problem is a "feature".... sometimes it turns on after tapping und pushing the power button like hell and sometimes it doesent..
Your screen turns also on with very very low brightness or it is off? When u look really really close u can see it...for example hold power button and u can hardly see the white power off/reboot popup...but i dont know where the problem can be...germany d802 version..(Sorry for my BAD english)
Click to expand...
Click to collapse
My screen turns completely on and off when I use the button/knock-off feature. I'm going to take it to a technician today and see what they have to say about it.
First, What are you running on your device? Stock? Rooted...
Burkettacb said:
Tons of lg users are experiencing this issue. Its a design flaw with a hardware component that easily breaks. Wonderful build quality -_-...right. So only option is replacing the phone. But to how soon, until the other one breaks. So its kinda like. Well. This blows. I suppose Ill install a custom kernel and enable screen wake features that way.
Sent from my LG-LS980 using xda app-developers app
Click to expand...
Click to collapse
That's odd, I have not seen much on this... if running stock
Burkettacb said:
Okay. So after hours of tapping. Which might i add. My fingers hurt, I am now able to activate the screen. Pausing after each tap, using my finger print area to tap "not to be confused with finger tip". The screen will activate. Also note, the standard two taps works sometimes, but with four presses, i seem to get the best results. Give it a try people. I have a theory the hardware has not failed. But yet, the activation area pixel size value changed. Either due to a conflicting app install. A intermittent system glitch etc
Sent from my LG-LS980 using xda app-developers app
Click to expand...
Click to collapse
Or againg, a ROM you may be using.
More detail would be helpful:good:
For me it happend on stock and rooted with aospa... Dont know What can cause this. I Sent it to my Carrier they found nothing....
Gesendet von meinem LG-D802 mit Tapatalk
running stock myself. Technician was useless and told me nothing.
DrZeuss said:
running stock myself. Technician was useless and told me nothing.
Click to expand...
Click to collapse
Same here
Gesendet von meinem LG-D802 mit Tapatalk
Did you try the Stop Having Sprint fix?
Sent from my LG-D800 using XDA Premium 4 mobile app
I got the d802...
Gesendet von meinem LG-D802 mit Tapatalk
Burkettacb said:
Okay. So after hours of tapping. Which might i add. My fingers hurt, I am now able to activate the screen. Pausing after each tap, using my finger print area to tap "not to be confused with finger tip". The screen will activate. Also note, the standard two taps works sometimes, but with four presses, i seem to get the best results. Give it a try people. I have a theory the hardware has not failed. But yet, the changed. Either due to a conflicting app install. A intermittent system glitch etc
Sent from my LG-LS980 using xda app-developers app
Click to expand...
Click to collapse
I had given up on knock on but tis actually works. (not 100%) but it actually turns it on. WOW
Is there a way to adjust the "activation area pixel size value"?
ingoljosh said:
I had given up on knock on but tis actually works. (not 100%) but it actually turns it on. WOW
Is there a way to adjust the "activation area pixel size value"?
Click to expand...
Click to collapse
This^. For me I have to use my entire thumb or even palm, but it occasionally works.(still like 1/30 tries). This leads me to believe that it is software related. This one issue is killing me. I hate using the power button on the back so I only used knock on. Now that it's not working I'm hating this phone. Knock off works great and I know knock on is kernel based so maybe someone can create a kernel that fixes this issue.
This did work for me. Fixed the knock on feature on my D802.
Credit: Smith I Run (Thread from android central. Can't post link to thread)
There is a solution; (not sure about it, my friend had the same problem and he fixed it with this method)
Open dialer menu and type;
5689#*980# (Sprint)
3845#*801# (T-Mobile)
3845#*803# (AT&T Canada)
3845#*802# (International)
3845#*800# (At&T)
3845#*980# (Verizon)
And when hidden menu is showed up, go to "Settings"
and go to "Update Touch Firmware".
The touchscreen won't work until after 5 seconds, Wait for it and if touchscreen gets working, exit the menu.
Lock the phone and try knocking on the screen, It should be working :laugh:
Click to expand...
Click to collapse
Double tap to wake is the feature I almost explicitly use to wakeup my phone to look at the notifications, especially so in Zuk Z, which has this crazy fast fingerprint scanner.
Lately, it stopped to work. I was trying to figure out the latest changes I did in my phone and I couldn't think of anything but the last CyanogenOS OTA update (YOG4PAS3OH) but it might be just coincidental. I have done quite a bit of troubleshooting, involving (but not limited to) disabling/enabling the feature, removing proximity sensor check, rebooting, etc but haven't done factory reset (which I'd be very reluctant to do anyway). Double tap to sleep is working fine though.
Few questions for folks here:
1. Is it working for you after the latest OTA?
2. Could this a hardware issue?
3. Any suggestions for me to try and make this work again?
Thank you!
malikons said:
Double tap to wake is the feature I almost explicitly use to wakeup my phone to look at the notifications, especially so in Zuk Z, which has this crazy fast fingerprint scanner.
Lately, it stopped to work. I was trying to figure out the latest changes I did in my phone and I couldn't think of anything but the last CyanogenOS OTA update (YOG4PAS3OH) but it might be just coincidental. I have done quite a bit of troubleshooting, involving (but not limited to) disabling/enabling the feature, removing proximity sensor check, rebooting, etc but haven't done factory reset (which I'd be very reluctant to do anyway). Double tap to sleep is working fine though.
Few questions for folks here:
1. Is it working for you after the latest OTA?
2. Could this a hardware issue?
3. Any suggestions for me to try and make this work again?
Thank you!
Click to expand...
Click to collapse
1. if by "the latest OTA" you mean cm-12.1-YOG4PAS3AJ (About phone: Kernel version 3.4.0-cyanogenmod-gef06bf8), then that is what I have, and double tap is working just fine.
2. although i am no engineer nor software developer, i feel i could say with fair confidence it is definitely a software issue. why? because i have used custom kernels that added such a feature to phones that didn't come with it.
3. you can try disabling Display & lights | Prevent accidental wake-up; use a task manager or Apps to look at your running processes and stop any that shouldn't be running then try again.
Thanks for the reply. If you read my post again, you'll see that I've provided the name of the OTA that I was referring to. It's not the one you have, and now I'm curious which one is the latest and why are we on different versions. Can you go check for any pending updates for your phone ?
I also believe that it's software related . I've tried quite a few things and nothing seem to be helping resolve this issue so far. Changed settings, remove some apps i lately installed, etc but no luck. I guess I'll do a factory reset and see if that takes care if this issue.
Sent from my ONE A2003 using Tapatalk
Im on 3OH. Double tap to wake wasn't working straight after the update, but i did some fiddling like turning it on and off, played with settings and after a reboot it was working again.
Thank you sir. You just gave me a huge hope. I'll keep playing and will hopefully make it to work. Cheers,
Sent from my ONE A2003 using Tapatalk
malikons said:
Thanks for the reply. If you read my post again, you'll see that I've provided the name of the OTA that I was referring to. It's not the one you have, and now I'm curious which one is the latest and why are we on different versions. Can you go check for any pending updates for your phone ?
I also believe that it's software related . I've tried quite a few things and nothing seem to be helping resolve this issue so far. Changed settings, remove some apps i lately installed, etc but no luck. I guess I'll do a factory reset and see if that takes care if this issue.
Sent from my ONE A2003 using Tapatalk
Click to expand...
Click to collapse
indeed you have (supplied your version no.), please excuse my oversight.
yours would appear to be newer than mine and, no, just checked & not available for me yet. sorry i can't be of help. hope someone else could. cheers.
I'm on 3OH and it works for me
After power on or reboot, go to settings-display, disable DTTS, turn off the screen with power button, turn on the screen, enable DTTS and now the DTTS will work until next reboot or power off. This is the way I manage to make it works. I hope Cyanogen will solve this bug in next build.
I have also problems with double tap, happened already 2 times in 5 days, reboot solves the problem...
Not sure what I did but the double tap to wake feature has started to work again. I messed around quite a bit with the settings and also rebooted the phone a few times. Although, the response is quite slow, like there is some lag between double tap and when the screen wakes up. It seems to be improving in response time as I play with it more, not sure if its psychological though . Hopefully cyanogen guys will take care of it in the future update.
Stopped working for me too! Seems since the last 2 updates things have gotten bad! If it ain't broke, why fix it?
Sent from my Z1 using Tapatalk
Double tap to wake is working again! I think my phone has a mind of it's own lol!
Sent from my Z1 using Tapatalk
Mine has been behaving much better now. I'm seriously considering cyanogenmod . I think it'll be a lot better than COS.
Sent from my ONE A2003 using Tapatalk
Double tap to wake has stopped working again! Bloody updates.
Sent from my Z1 using Tapatalk
Keep playing with the settings and it'll start to work again
Sent from my ONE A2003 using Tapatalk
Lol! Thanks will try that but shouldn't have to.
Sent from my Z1 using Tapatalk
---------- Post added at 05:58 PM ---------- Previous post was at 05:56 PM ----------
malikons said:
Keep playing with the settings and it'll start to work again
Sent from my ONE A2003 using Tapatalk
Click to expand...
Click to collapse
Thanks it worked! Lol
Sent from my Z1 using Tapatalk
Agree , we shouldn't have to but this phone isn't very stable at the moment. Sometimes I wonder why I'm even using it there's something in this phone I really like though and I believe in cyanogen
My phone was perfect when I bought it. The problem started with the countless updates I've had since then.
Sent from my Z1 using Tapatalk
malikons said:
Mine has been behaving much better now. I'm seriously considering cyanogenmod . I think it'll be a lot better than COS.
Sent from my ONE A2003 using Tapatalk
Click to expand...
Click to collapse
It also happens with CM nightlies
Thank you for saving me a lot of time and frustration
Hi all,
I'm running stock 6.0.1 rooted with Xposed (only using gravitybox). When I do the double tap on power to launch the camera, nothing happens other than the power button functioning normally. It did work at one point but I'm not sure if it was an app, Xposed or a system setting which stopped this feature from working. Has anybody else run into this or have a few ideas to try? I tried disabling Gravitybox but left Xposed itself still installed. I've also tried changing the "Power buttons locks instantly" setting under Security but that didn't make any difference either.
Thanks
Try reflashing the vendor.img.
I'm rooted with stock rom, camera would start but not show any picture and you couldn't do anything with the app. I reflashed vendor.img now the camera will work ONCE after a reboot. Also check to see if your flashlight works.
ttillman2177 said:
Try reflashing the vendor.img.
I'm rooted with stock rom, camera would start but not show any picture and you couldn't do anything with the app. I reflashed vendor.img now the camera will work ONCE after a reboot. Also check to see if your flashlight works.
Click to expand...
Click to collapse
If you used traditional root and flashed the boot.img from an older version, it breaks camera for all apps. I had to switch to systemless root to fix the camera.
Also, just verifying that you are using a 6p not a Nexus 6, as your signature states. This is the 6p forum.
See if that setting is checked under the Display settings
pipnmike said:
See if that setting is checked under the Display settings
Click to expand...
Click to collapse
Gosh darn it. I feel dumb now but I swear I spent 30 minutes going through the settings menus trying to find if there was a setting for this. Needless to say, it was turned off somehow (probably by me accidentally) and turning it back on makes it work perfectly fine.
Thanks!
mbazdell said:
Gosh darn it. I feel dumb now but I swear I spent 30 minutes going through the settings menus trying to find if there was a setting for this. Needless to say, it was turned off somehow (probably by me accidentally) and turning it back on makes it work perfectly fine.
Thanks!
Click to expand...
Click to collapse
After updating to Nougat, double click stopped and the setting was off for me as well. But I don't feel dumb. I think whoever in Google thought this was a good place to put this setting should get that privilege. I don't know how I found that setting when I got the phone originally, but I can pretty much guarantee that I read that somewhere and enabled it. No way I went to Display Setting to find how to quickly start the camera app.
Sent from my Nexus 6P using XDA-Developers mobile app
Lenovo started sharing the update now with Android 8.1
Sharing at least in Finland works fine.
Update for TB-X304F also has gone live. Works.
One thing I noticed is a new 'OEM unlock' in the developer settings - I haven't tried it yet, but perhaps this will open up this device more easily to 3rd party roms?
Upgrade
devil-kin said:
Update for TB-X304F also has gone live. Works.
One thing I noticed is a new 'OEM unlock' in the developer settings - I haven't tried it yet, but perhaps this will open up this device more easily to 3rd party roms?
Click to expand...
Click to collapse
Were you rooted when you upgraded? If so what steps did you take to get there? I have the upgrade file but when I tried to install it, twrp message came back and said I had the wrong package.....but it is the same model as yours
No, not rooted.
Sent from my ONEPLUS A6003 using Tapatalk
I don't know if it's the 8.1 update since I wasn't on Nougat all that long after I got the tablet. But does anyone have an issue with the lock screen? Sometimes it take me at least 5 times to swipe the lock screen up. Don't know if it's a software issue or the touchscreen is just not that good.
jsgraphicart said:
I don't know if it's the 8.1 update since I wasn't on Nougat all that long after I got the tablet. But does anyone have an issue with the lock screen? Sometimes it take me at least 5 times to swipe the lock screen up. Don't know if it's a software issue or the touchscreen is just not that good.
Click to expand...
Click to collapse
Working well here.
Eagle-no1 said:
Working well here.
Click to expand...
Click to collapse
Well I don't know why it seems so finicky with me. With my Nexus 10, I was able to just do a short flick on the lock screen and it would unlock. It seems like with this tablet, I have to really do a good, long, specific swipe to unlock it. It also seems to respond better with my knuckle for some reason. Maybe I just have to get used to it. The tablet seems fine everywhere else.
Can anyone just help me downgraded the system with system sparse image in fastboot mode provided by o.p. of rooting thread, but now it is not booting up just showing lenovo logo and in fastboot mode again