[Q] The LED of the 18th Oct CM10 - Defy Q&A, Help & Troubleshooting

The LED of the 18th Oct CM10 works not normally.When there is a missed call,it will flash when the screen is off.And when it comes to app notifications,it works well,too.However,when there is a missed message,it doesn't work well.It will flash when the screen is on,but once the screen is off,it won't flash any more.
Is this a special case,or a bug?
Who can tell me how to fix it?

Look in your parameters' calls and sms if the option of led is on.
If yes, re install the last version of Quark them the last zip update.

Related

[Q] Flashlight not working after CM 10.1 or Eclipse

Has anyone else had an issue where the flashlight (i.e. Torch) stops working after the lasted 10.1 nightly from skrilax or release 3 of Eclipse? i am restoring my stock ROM to see if it starts working again.
so, after careful inspection, I now notice that when I turned on my camcorder light, the LED for the flash has a very faint light, but never gets bright. Did the 7/9/2013 Skrilax nightly kill my flashlight / LED?
Factory Reset, and still no flash wish factory kernel, baseband, 4.1.2 Android, nothing loaded. Looks like the LED got killed.

[Q] CanĀ“t use Phone app

Hello, I have problem.
Iam using noobdev 4.4. CM11 nightly on my i9505 without problem, but suddenly, maybe after last nightly update phone app stop work.
I can go to internet, receive messages, but when i want to call someone the screen goes black and doesn't answer and the menu bar "flash" I have to wait during 20-30 seconds before to return on my home screen. When I receive a call, after answering it, screen goes black too. I cant hear the person on the other side, and they cant hear me.
I tried everything, flashing many other modems/radios, roms, restoring backups, flashing another recovery, flashing official firmware and it still dont work.
Help me please:crying:

[Q] S4 i9506 solk2 port - thanks, and issues observed

Hi - I'm very new to the forum and less new to custom ROMs and software.
In the last few days I installed solk2's unofficial CyanogenMod port, 20140711 root build. Went well; overjoyed to be rid of Samsung's bloatware. Thanks!
Since then, updated to first 20140808 and now 20140813. Used CWM recovery (installed via theunlockr dot com/2013/12/09/install-custom-recovery-samsung-galaxy-s4-gt-i9506shv-e330s/) directly instead of CM Updater - updater downloads the builds but when it reboots into recovery to apply them the process there cannot find the build file to install.
I've noticed:
1) When making / receiving calls, the face sensor doesn't appear to work any more - before CM, the sensor would notice when the phone is held to my cheek and blank the display, and light it up when I move the phone away. No longer.
2) The front start button doesn't appear to wake up the device from sleep any more (maybe I've missed a setting to toggle for that?)
3) the CM updater doesn't appear to work, as mentioned above
4) CyanDelta doesn't know about this set of nightlies I think - I've tried it a couple of times and it doesn't pick up deltas
5) the power button doesn't wake the device when it has darkened due to being on a call; instead it may cause the device to flash its screen up but then immediately darken again
1 & 5 make it quite difficult to control the phone during calls. Initially I thought this might have to do with ShakeCall, but the issues persist after uninstalling that.
I've cleared my cache and dalvik cache after the most recent flash to 0813.
I should say, this is relating to http://forum.xda-developers.com/showthread.php?t=2767448 and I'd have posted there but I cannot yet.
This is still an issue for me with cm-11-20140909.
Is there anything I can do to help find and fix these items?
Is this the right place to ask, even? Does @solk2 work?
pfm102 said:
This is still an issue for me with cm-11-20140909.
Is there anything I can do to help find and fix these items?
Click to expand...
Click to collapse
Proximity sensor fixed a long ago. There something wrong in yours phone. Install this recovery. Then try clean install of latest nightly or SNAPSHOT-M10 and set update recovery in Developer settings. Recovery you have has different mount points so thats why it can't find updates.
Delta updates isn't supported though.
solk2 said:
Proximity sensor fixed a long ago. There something wrong in yours phone. Install this recovery. Then try clean install of latest nightly or SNAPSHOT-M10 and set update recovery in Developer settings. Recovery you have has different mount points so thats why it can't find updates.
Delta updates isn't supported though.
Click to expand...
Click to collapse
Thank you very much - I'm running 20140914 and the proximity sensor now works during calls.

In/Out CallUI serious problem

Hey guys, I've rooted and installed custom roms without any problem on my note 2 and hammerhead. yesterday I rooted my brothers' in law note3, using cf auto root. Had some problems with flashing cwm, but finally made it. now im on philz newest recovery. I tried already like 5-6 different roms and versions ( aosp - slimroms, cm, liquidsmooth ) and everywhere I encouter the same problem - when dialling number screen suddenly goes black, I can't see picture, in calling buttons, the only way i can finish call is by pressing home button, swiping down notification drawer and finish call from there. The same happens when I try to answer the call, I get initial screen, and after accepting the call screen goes totally black. It happens on every rom I flash ( aosp ). Any ideas? I would appreciate your help so much,
mikael91 said:
Hey guys, I've rooted and installed custom roms without any problem on my note 2 and hammerhead. yesterday I rooted my brothers' in law note3, using cf auto root. Had some problems with flashing cwm, but finally made it. now im on philz newest recovery. I tried already like 5-6 different roms and versions ( aosp - slimroms, cm, liquidsmooth ) and everywhere I encouter the same problem - when dialling number screen suddenly goes black, I can't see picture, in calling buttons, the only way i can finish call is by pressing home button, swiping down notification drawer and finish call from there. The same happens when I try to answer the call, I get initial screen, and after accepting the call screen goes totally black. It happens on every rom I flash ( aosp ). Any ideas? I would appreciate your help so much,
Click to expand...
Click to collapse
Try the link in my signature. It is used to diagnose and eliminate most problems that most custom ROM users face.

half blue half black screen after flashing a rom

hi everyone.
i am having this wierd issue for a month or so, when i try to update RR rom.
after i flash the rom, i get the screen attached. screen seems for like 2 seconds, and goes this half black / half blue screen. screen is still responsive, i can receive calls and if i double tap anywhere, screen locks. there is no problem with screen on twrp or anything ( because sometimes after flashing the rom i dont get this screen, so i don't do anything else, except use it normally.) but today it happened without a reason, the phone was in my pocket when i took it out and saw the screen in this state.
i always flash by following the steps given. i know it is not hardware related. where is the problem? what do i need to do?
p.s. : when charging, blue part goes yellow.
thank you all, waiting for a solution
rukenau said:
hi everyone.
i am having this wierd issue for a month or so, when i try to update RR rom.
after i flash the rom, i get the screen attached. screen seems for like 2 seconds, and goes this half black / half blue screen. screen is still responsive, i can receive calls and if i double tap anywhere, screen locks. there is no problem with screen on twrp or anything ( because sometimes after flashing the rom i dont get this screen, so i don't do anything else, except use it normally.) but today it happened without a reason, the phone was in my pocket when i took it out and saw the screen in this state.
i always flash by following the steps given. i know it is not hardware related. where is the problem? what do i need to do?
p.s. : when charging, blue part goes yellow.
thank you all, waiting for a solution
Click to expand...
Click to collapse
First go to recovery and check that display problem present or not if not then flash any other custom rom or reflash rr
if you are unable to go to recovery then flash stock rom via odin it will fix every software related issue
and if flashing stock rom doesn't work then it may be hardware issue
You confirmed the model # in download mode? Tried using different version of TWRP?
I am facing same problem recently, did you find any solution ?
still no solution. this problem is not hardware related since i can use it perfectly now. i tried to flash (via twrp) RR-N-v5.8.5 exactly as described in op. rom boots, i can see the home screen for a brief moment but screen goes immediately black and blue. i can receive calls, lock and wake screen, that's all. then i have to restore everything. i am currently on hexagon rom v2.5 and no issues but i like RR.
again, this problem is not hw related. i follow all the steps again and again checking everything..
any ideas?
blue screen
rukenau said:
still no solution. this problem is not hardware related since i can use it perfectly now. i tried to flash (via twrp) RR-N-v5.8.5 exactly as described in op. rom boots, i can see the home screen for a brief moment but screen goes immediately black and blue. i can receive calls, lock and wake screen, that's all. then i have to restore everything. i am currently on hexagon rom v2.5 and no issues but i like RR.
again, this problem is not hw related. i follow all the steps again and again checking everything..
any ideas?
Click to expand...
Click to collapse
make a clean install and try a different kernel than pre installed one
maniwaraich said:
make a clean install and try a different kernel than pre installed one
Click to expand...
Click to collapse
clean install worked for a day or so, until i turned off ambient dislpay and restart. then it went blue&black again.
i tried a few kernels, some bootloaders and modems (including nordic) but problem persists.
i will try to get a logcat :/
In case anyone has the same problem: reboot to safe mode, go to settings, flip cover and turn off S-View flip cover.
Same issue un lineage og 15.0 and 15.1 on samsung galaxy S 5 mini G800F someone find a solution?
pierpa2 said:
Same issue un lineage og 15.0 and 15.1 on samsung galaxy S 5 mini G800F someone find a solution?
Click to expand...
Click to collapse
Read thread .
Flash stock rom and test .
But this is the Note 3 forum not your phones forum .
JJEgan said:
Read thread .
Flash stock rom and test .
But this is the Note 3 forum not your phones forum .
Click to expand...
Click to collapse
lareay flashed lots of time differents ROM sorry for the wrong forum but i can't find a solution.
Stock rom with oreo does not exist.
Solved turning off smart cover

Categories

Resources