I just noticed that when I get a call, the moment the screen of answer/decline/sms shows up with the contact's name, the notification LED flashes once in white, and flashes once again if I don't answer at all, right at the moment the screen disappears.
Is this a defect in 4.4.4? perhaps my particular device? I'm running fully stock, unrooted.
I'd say that's a feature...
Perhaps... since this hasn't occurred to me with my N4.
i have same problem also with custom rom.
by using light manager it works without problems
Related
Hi everyone,
Thanks to KarrdeNZ's well written guide, I managed to flash my rom to
********Hero ROM for Magic modded for TW users (based on Fatal1ty2787's releases)********
07/18 myhero-08 by redglasses
I just noticed that my phone's LED lights are missing. The LED doesnt light up while charging, and it doesnt light up when receiving SMS as well. I think the LEDs just disappeared completely.
Anyone encounters this and is there anyway to solve it?
Thanks!
Hero ROMS currently have the following issues
Bluetooth headset/mic support is broken, though Bluetooth headset playback works fine - no known solution.
TouchFLO sluggishness - don't use it or minimise widget use - especially clocks.
LEDs mapped incorrectly - no known solution.
Camera flipped/oriented wrong - need to reinstall old Camera package to fix
Take a look here : http://wiki.xda-developers.com/index.php?pagename=HTC_Sapphire_Hacking
I got my sms led working, via chompsms.
Charging still doesn't work but tats not really.important I guess
Yeah you can use chompSMS or SMS popup to get the message notification LEDs working again.
Also the LED does work while charging, well sort of, it will turn green when it's 'charged' but won't glow orange like it used to whilst 'charging'.
cenedra said:
I got my sms led working, via chompsms.
Charging still doesn't work but tats not really.important I guess
Click to expand...
Click to collapse
Roy_Drage said:
Yeah you can use chompSMS or SMS popup to get the message notification LEDs working again.
Also the LED does work while charging, well sort of, it will turn green when it's 'charged' but won't glow orange like it used to whilst 'charging'.
Click to expand...
Click to collapse
mine don glow at all while charging.
Well its a minor issue, so im not really concerned abt it
Hello everyone,
I've been having quite an interesting issue on my NS4G. I'm currently running the latest available CM7 nightlies/gapps, as well with Pete Alfonso's kernel. The underlying system in the phone (radio/etc) is all running the current latest available from Sprint as well.
Now the issue in question, I've been having an issue that seems to be occurring more and more frequently on my phone. Now because I am already running a custom ROM and not just stock, this makes me unsure if the issue is coming from the software, or if there is an actual hardware issue with my phone.
Occasionally (I would say as infrequently as once every 2 days or so) when I unlock my phone with the power button, for a split second after the CRT animation I see my phones screen as all green (with a hint of purple), almost the color you associate artifacting with. Now I am not overclocked, but I am running this custom kernel. But the thing is, I'm not 100% on this, but If I remember correctly I do remember seeing this issue on other kernels as well before (I've been running Pete's for some time now).
I also occasionally experience issues with lets say finishing up a phone call, and my phone may lock up with that green screen w/ purple, and then CM7 will automatically reboot the phone for me. I've also experienced my phone rebooting into "Safe Mode".
Essentially what I am wondering is if anyone can shed some light, are these just software bugs that I am running into that other users are experiencing as well, or is this an issue with my phone?
Thanks everyone!
boktai1000 said:
Hello everyone,
I've been having quite an interesting issue on my NS4G. I'm currently running the latest available CM7 nightlies/gapps, as well with Pete Alfonso's kernel. The underlying system in the phone (radio/etc) is all running the current latest available from Sprint as well.
Now the issue in question, I've been having an issue that seems to be occurring more and more frequently on my phone. Now because I am already running a custom ROM and not just stock, this makes me unsure if the issue is coming from the software, or if there is an actual hardware issue with my phone.
Occasionally (I would say as infrequently as once every 2 days or so) when I unlock my phone with the power button, for a split second after the CRT animation I see my phones screen as all green (with a hint of purple), almost the color you associate artifacting with. Now I am not overclocked, but I am running this custom kernel. But the thing is, I'm not 100% on this, but If I remember correctly I do remember seeing this issue on other kernels as well before (I've been running Pete's for some time now).
I also occasionally experience issues with lets say finishing up a phone call, and my phone may lock up with that green screen w/ purple, and then CM7 will automatically reboot the phone for me. I've also experienced my phone rebooting into "Safe Mode".
Essentially what I am wondering is if anyone can shed some light, are these just software bugs that I am running into that other users are experiencing as well, or is this an issue with my phone?
Thanks everyone!
Click to expand...
Click to collapse
go to the main settings, cyanogenmod settings, display.. turn on the screen off animation. then go back to cyanogenmod settings, lockscreen, delay and timeout, turn both screen timeout delay and screen turned off delay to immediately. that should fix the green screen.
Hi. I'm on a rooted Nexus 5, stock ROM & Kernel, and I'm experiencing two little issues:
1) Proximity sensor problems
When I answer a phone call the screen just doesn't go off. The same if I make a phone call. This is pretty annoying because during phone calls I often touch buttons with my face and I mess up with settings.
2) Notification LED stuck
Sometimes, let's say about once every two weeks, the notification LED keeps flashing even after I wake my phone and read the notification. The only way to reset it is to do a hard reboot.
Do you have these problems too? How could I resolve?
Hello!
My oneplus one is having this issue for a while now, When I plug it in and lock the device, there is a 60~70% chance that the display stays on but its just blank, I have to unlock it and lock it again to fix it.
Recently this also started happening when it was not charging and the screen would often stay on causing massive battery drain :/
This happens on every single rom all the way from CM11S up to CM13 and also oxygen os,...
Does anyone know what the problem is?
Thanks,
Noahvt
I have the same problem since I can remember, also looking for an answer.
I have a similar issue. Sometimes the screen stays on, but is dimmed. A simple double press of the power button resolves it (turn on full, turn off screen) but its mildly irritating. I have only noticed it since being on sultanxdas cm12 ROM. I had an issue with a notification LED app not working since a recent ROM update so uninstalled it. Maybe the issue was related to that app as I cant remember the issue occurring since I uninstalled it a few days ago.
This is my first time installing custom ROM's on my otherwise stock Sprint Motorola photon 4G LTE. After successfully flashing CM13 (2016_08_20 snapshot release), I tried to make a call, and upon hitting "call" from the dialer, the screen goes black and stays that way. The only recourse is to hold down power button long enough to reboot. While the screen is black, there is no sound from the ear piece (i.e. it does not appear that the call is connected). Finally, while the screen is black, the phone does exhibit some reactions: it vibrates sometimes if I hit the power button, in other words, the device is still 'on" until I have to reboot it.
After this happened, I gave up on CM13 and flashed CM-12 (the latest snapshot release, from 2015) , and experienced the same behavior.
The call apparently was completed, because the other party received a missed call. However, there was no sound on my end (although there was side-tone, when I breathed on it)
I googled for about an hour, and saw examples of the same behavior on other devices claiming to be related to the proximity sensor (though in those cases, there apparently was audio in the ear piece-- ie. the call completed, and was in progress while the screen was black). This behavior was not observed a few minutes before under stock ROM in the same device (so doubt it's a strictly hardware issue, so doubt I need to open the device and clean the sensor, per some of the suggestions out there).
I suspect the answer is very basic, because I found no similar threads searching XDA.
Please let me know any ideas. I did not do anything about updating my baseband version from stock before flashing the CM ROMs., but don't know if I have to I'm a noob at custom Rom's and just remembered that you had to worry about the baseband / radio version back on the HTC Evo 8 years ago, which was my last time flashing. Again, the ROM itself worked fine-- wifi and 3G/LTE connectivity was a success.
Let me know any ideas.
thanks
After restoring to stock, dialing worked again on the phone, but the behavior on the device was different from two other photons I tested next to it.
In the stock ROM, the call connected, but the screen turned off immediately upon hitting "call" (even when the phone was on the desk). You could get the screen back (in stock only) by hitting the power button.
In my other two photons, the black screen does not kick-in immediately. So it does appear it could be something having to do with the proximity sensor (i.e. it's always engaged). I don't have the skills to confirm. I am writing-off this phone for now, and have a different device (so not a high-priority thread at this point), but let me know if anyone has any ideas. Thx.
There's a way to validate if the prox sensor is working - zDeviceTest in the Play Store will test all of the hardware, and it will also show the metrics each piece of hardware is receiving - the prox sensor being fairly simple, it just identifies if an object is "near" or "far".
I always recommend making sure everything works in the stock ROM before flashing anything custom - as you need to validate everything works before making tweaks.
My advice is the same as arrrghhhs. (This name really looks like it was typed with a Photon Q with some characters repeated by the device >.>)
I noticed that my proximity sensor sometimes "stuck" to near (I use some different app [SatStat] so it shows 3 cm or 100 cm instead of near/far). Winking a little above the sensor helps sometimes. But your problem sounds like a defect.