Sorry for the off topic but anyone Know an app to sync facebook contact?
FYI everyone: tomorrow's nightly will likely break compatibility with all third party kernels. We completely revamped the kernel to base it off newer samsung (and caf) source. Also - we are no longer going to support variant recoveries. You'll need a jflte recovery. Here's a flashable zip of the lastest clockworkmod for jflte: http://www.invisiblek.org/recovery/jflte/jflte_recovery-cwm-6.0.5.0.zip
FYI everyone: tomorrow's nightly will likely break compatibility with all third party kernels. We completely revamped the kernel to base it off newer samsung (and caf) source. Also - we are no longer going to support variant recoveries. You'll need a jflte recovery. Here's a flashable zip of the lastest clockworkmod for jflte: http://www.invisiblek.org/recovery/jflte/jflte_recovery-cwm-6.0.5.0.zip
You are late a bit. They changed the name of that option few days ago, and they did it with a reason.
So what would one expect? I expect the exact thing you described: covering proximity sensor and trying to switch on screen should result in screen not turning on. Yet, it does... and additionally creates a wakelock until switching that option off and reboot
IR Sensor still working since day one...
What is your Problem?
Gesendet von meinem GT-I9505 mit Tapatalk
You are late a bit. They changed the name of that option few days ago, and they did it with a reason.
First name was ambiguous in that it could be interpreted like the wake up feature which is using the proximity sensor.
My opinion at least.
FYI everyone: tomorrow's nightly will likely break compatibility with all third party kernels. We completely revamped the kernel to base it off newer samsung (and caf) source. Also - we are no longer going to support variant recoveries. You'll need a jflte recovery. Here's a flashable zip of the lastest clockworkmod for jflte: http://www.invisiblek.org/recovery/jflte/jflte_recovery-cwm-6.0.5.0.zip
You can guarantee that even though people have been warned, there will still be posts here saying "I flashed the latest nightly with [whatever] kernel and it won't boot. Please help."
For those I this thread that do bother reading everything, please tell the non-readers that the problem is with their kernel being out of date, not a bug in CM, and that they should go to their kernel's thread for support.
Yes I have, and my reaction is related to its first part, a 'question' 'what would one expect? '.Did you really read the post I quoted?
The option "prevent accidental wake-up" does nothing than create a wake-lock.
It should prevent the screen to be switched on if the phone is for example in a pocket. But if I cover the proximity sensor while the screen is off and then press home, the screen switches on and can even be unlocked.
In addition to that, a wake-lock will be created until I turn that option off and reboot the phone.
Gesendet von meinem GT-I9505 mit Tapatalk
Regarding the rest of your post, about the possible bug, I can confirm that covering the sensor, and pressing the home button does turn the screen on. On the other side I haven't noticed any wakelock running, so no need to reboot.So what would one expect? I expect the exact thing you described: covering proximity sensor and trying to switch on screen should result in screen not turning on. Yet, it does... and additionally creates a wakelock until switching that option off and reboot
Do you know if the next M build will be the same?FYI everyone: tomorrow's nightly will likely break compatibility with all third party kernels. We completely revamped the kernel to base it off newer samsung (and caf) source. Also - we are no longer going to support variant recoveries. You'll need a jflte recovery. Here's a flashable zip of the lastest clockworkmod for jflte: http://www.invisiblek.org/recovery/jflte/jflte_recovery-cwm-6.0.5.0.zip
#include <std_disclaimer.h>
/*
* Your warranty is now void.
*
* We are not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at us for messing up your device, we will laugh at you.
*
*/
@invisiblek,
I wonder if currently the developer or rom mainteiner for S4 need people to test the nightly to report about the random reboots issue or sending logs or they know already the basic information to investigate. I suppose should be possible to indentify which day the issue has started and which commit is the "guilty". Just to know. Sorry if I miss some information on this thread.
Thanks