N4 Purity Rom Camera flash bug. plz help - Nexus 4 Q&A, Help & Troubleshooting

Hello everybody! I have very annoying bug with my camera flashlight. when i touch the screen to focus the flashlight turns on and sometimes a very strange sound appear (the same like short circuit ) and the phone freeze and reboot itself. Any ideas?
Thank you!
P.s. I use Purity Rom + HellsDoctor R20 + T.A.R.D.I.S + Trickster.

Get the logcat. If you don't know how, check this.

If the flash stays momentarily then it's not an issue else take the log cat...
Sent from my Nexus 4 using Tapatalk

Related

HD2 keypad light stays On while screen is ON?

Hi
Is there a method to keep HD2 keypad light On (all the time) while screen is ON and turn it off while in standby?
Thanks
I second that.
Anybody? I've been lookin for such a fix for a long time now.
Specially when I read in my bed and the lights are off i wish for a solution that would keep the lights on for easy navigation.
Thanx in advance
Could be in theory possible with the latest cyanogen builds.
You can specify your buttons luminosity (0-255), depending on your light sensor (dark room for example) !
But it doesn't work with me (hastarin 7.6), maybe with another kernel?
please anyone have a solution?
Yeah !!!
I'm also still looking for à method or a trick to keep my hd2 keypad on as well as the screen remain on...
Please, share, find à solution... tanks.
Did you tried cm 6.1 ?
Sichroteph said:
Did you tried cm 6.1 ?
Click to expand...
Click to collapse
Yes, I'm using CM6.1 but I dont'know how to solve.
Can you help me?
thanks
Check into cyanogen mod settings, where you can set the screen luminosity depending on the light sensor. On the second column you can set too the buttons backlight. try it and please report if it works. It didn't for me two weeks ago, could be a cm6.1 nighty bug, or our kernel that doesn't recognize well the demand.
Else I was thinking about the xda developer that made blinker, maybe you can ask him for a app that so that, could be very ready for him to do.
zolom said:
Hi
Is there a method to keep HD2 keypad light On (all the time) while screen is ON and turn it off while in standby?
Thanks
Click to expand...
Click to collapse
+1
Someone have solution?
I have tried with CM6.1 RC2 and Hastarin 8.5.1, still no joy with the cm6 keypad led settings....
+1 For a solution from me as well...
Is there anyway to switch them on from the console?
anyone got an answer?
I'm not sure but you can try MDJ kernel s7 with new lights driver. The lights only go off when you press the power button. I hope that what you are thinking of
still no solution???
Hello,
you can turn on your keypad liegt by write 1-255 ind this file "/sys/class/button-backlight/brightness" on your android-device. if you write 0 the light will be off.
The problem ist that the system change after 10 seconds the count to 0.
I like to write an android app which helps that the keypad light stay on.
I havn't much experience in programming an android app. Can anybody tell me how i edit a file?
Anyone know which ROM supports this feature nowadays? Thanks

Cannot wake up the screen after ending the connection.

Hello everybody. I have an issue with the screen wake up. I use this rom, the latest version. Everytime I end a conversation the screen is turning off. That is normal. But the problem is, I cannot wake it up afterwards. The hardkeys backlight is turning on for just a moment and off. The only solution is taking out battery and booting Android once again. I know that changing the build would might be helpful but this ROM is really fantastic and I would like to avoid changing it. Could anyone help with this? Thanks.
boober78 said:
Hello everybody. I have an issue with the screen wake up. I use this rom, the latest version. Everytime I end a conversation the screen is turning off. That is normal. But the problem is, I cannot wake it up afterwards. The hardkeys backlight is turning on for just a moment and off. The only solution is taking out battery and booting Android once again. I know that changing the build would might be helpful but this ROM is really fantastic and I would like to avoid changing it. Could anyone help with this? Thanks.
Click to expand...
Click to collapse
This question would be better answered if posted in the thread created for the ROM. The other users may also be experiencing the issue and have a solution, or the chef may not even be aware of the problem and should be notified.
This is not the rom's problem, ...
it's your proximity sensor, quick fix is to put it under a bright light or zap it with an IR remote (the proximity sensor is located top-left

[Q] Is this a Sod?

Hey guys , I am expriencing a sudden shutdown of the screen after ending a call.
When it happends the screen goes black but everything else function, u can still hear it when u press on the buttons and the only way to make it work again is to pull off the battery and restore it.
the question is : if its a sod , a faulty device or just a user error.
I've searched the forums with no luck so I am here asking you.
thanks
Sounds like a perfect example of a SOD to me.
Oky, thanks for the fast replay, mods can lock this thread now.
thanks again.
try disabling proximity sensor in call settings, it's possible that the sensor is faulty, mine is and it causes the same effect.

[Q] How do keep screen on during calls? on Rooted, PA ROM

Greetings!
I have three Nexus 4s all having the same problem: The screen turns off when the phone rings and I have to press the power button to turn it on so I can press the button to pick up the phone.
I'm new to Rooting and customizing. My stock 4.2 build had the problem of the screen going black when I tried to calling or receiving a call. It went black during Skype and Viber calls too. I took off the screen protector and it's still happening.
I then rooted it, it still happened. I installed CyanogenMod, it still happened. Then I learned it had something to do with the proximity sensor. I then tried to load franco kernel on it and I found out that you needed a JSS ROM, so I now loaded Paranoid Android onto the phone. Then GAPPS and the Franco Kernel.
Device: Nexus 4
ROM name: Pandroid Android
Build: pa_mako-4.3-BETA4-20140513
Kernel: franco.Kernel-nightly-r207
It's suppose to be like this. The screen will go off so you won't press anything on the screen with your ear. And you're right, it's not a bug, just the proximity sensor working.
See if there's an option in call settings to not use/turn off proximity sensor during calls, some roms have this option. I think you can also do it with and app or xposed module.
Enviado de meu Nexus 4 usando Tapatalk
Yes, but it's malfunctioning like it is for a lot of other users. The solutions I've found are mostly for Samsung S2 & S3 phones.
I've checked my phone app, it doesn't have the turn phone off setting.
Ex. My most annoying problem is when I want to check messages, the volume is too low and the screen stays black persistently despite repeat pressing of the power button.
When I want to put on speakerphone, how do I keep it on? The phone keeps turning the screen off.
Skype gives a lot of problems, but that could be because the program is buggy.
You mean the screen go off but doesn't turn on after you end the call? I had this problem on stock, but couldn't find a solution. Even on custom roms it happened sometimes for me (CM and old Slim builds), but don't happen anymore with recent SlimRom builds.
Enviado de meu Nexus 4 usando Tapatalk
Yep, that's whats happening.
I'm putting SlimRom down on my shortlist.

CM11 and call/screen (proximity sensor) problem --- ALSO CM12!!!

Hi, I've been having this issue since installed CM11 on this phone (D800, happens aswell on other models). Sometimes the proximity sensor will not trigger when incall and taking away the phone from your face. So the only way to get the screen back (to hang-up the call for example) is hitting the back button -wich is annoying-. The sensor is ok since it is working fine (call and screen) on a G3 based rom. Is there any workaround for this? Can anyone help to fix this?
Thanks all in advance!
I have same issue and been searching and posting to find the cause and solution.
But unfortunaly no responses and/or fixes so far.....
Incredibly, this bug happens me aswell on cyanogenmod 12 (lollipop)... Should I start thinking about a radio problem? Wich other radio could be tested with this roms?

Categories

Resources