yashsingh1/xdaforums huggingface dataset:
[ONE General] nsmart:
I have this too. I did not reboot my phone for 3 days now and sometimes "prevent accidental wake up" works and sometimes it does not not. To me it seems to be completely random, but if it does not work and I do a call, afterwards it works fine for some time but then it stops working again.

---------- Post added at 09:51 AM ---------- Previous post was at 09:34 AM ----------

The fix for Trusted Face: face unlock indicator/icon not showing current unlock status on lockscreen is pending. Let's hope the corresponding commit get's merged soon.
[ONE General] karangupta:
Are you on cm11 or cm12.1?

Just download the corresponding modem/radio for the particular version you are using and flash it(you'll find it in modem collection thread on XDA). Also update your twrp to the latest version before flashing the ROM(if you use nightlies)
[ONE General] ace_apr27:
I'm on CM 12.1. My TWRP is up to date. I have already installed the latest modem. I've been having this issue ever since I switched to CM 12.1 a couple of months back so I had tried flashing the modem then. I switched to CM12.1 by flashing a nightly first after which I tried a few other 5.1 based ROMs like Euphoria and Blisspop, all of which had the EXACT same 'incoming call screen black' issue (I thought, back then, that it was a ROM glitch) so I switched to CM12.1. Later, after a bit of reading I found that it's a glitch with CM12.1 itself (and since those ROMs were based on CM, the bug was affecting them too).

I believe there's a jira thread about it as well. The CM team hasn't said a lot about it (I'm pretty sure they will have a fix when they release a stable build) but as of now, it seems that it's a legit issue. I was wondering if someone here has managed to find at least some sort of a temporary fix as carrying a headset ALL the time isn't feasible. I have made it a habit to go around with my Bluetooth headset, but some times, it just isn't possible (headset battery's dead, I forgot the headset, etc.). At such times, it's impossible to answer calls!

One anomaly I have noticed, however, is that a reboot will usually (not always) fix this for the FIRST call that comes in. Things will be fine, I'll be able to answer and what not, but from the next call, the problem is back till I reboot. The only solution, then, is seemingly rebooting after EVERY call. And hoping it'll work :P

Any other ideas, folks? Also, are there any diagnostic details I can provide that might help track what the hell is wrong with the damn sensor?
[ONE General] Renosh:
Can you please take a screenshot of your Settings>About Phone

What baseband version do you have?
[ONE General] ace_apr27:
Attached!
[ONE General] nsmart:
The correct baseband for the nightlies is inside the zip of the downloaded rom (DI.3.0.c6-00241-M8974AAAAANAZM-1). I would recommend to extract the modem from zip of your downloaded rom and flash it in fastboot mode (fastboot flash modem non-hlos.bin). Some twrp versions don't update the modem correctly.
[ONE General] :
Uuups, it's old firmware. The current cm nightlies firmware is DI.3.0c6-00241 ... You should update! -> downgrade twrp to 2.8.6.0 and re-flash today's cm nightly - done.
[ONE General] Renosh:
You have the wrong baseband version. TWRP version 2.8.7.0 doesn't seem to be flashing the firmware correctly

Flash this custom TWRP then reboot recovery

https://www.androidfilehost.com/?fid=23991606952609056

then wipe system and reflash ROM and gapps and check your baseband, it should read the same as the one attached
[ONE General] ninjasumit:
Flash the modem from the latest nightly via fastboot. This will fix the proximity sensor.
[ONE General] novren:
Jul8 nightly is a great performer. Should I upgrade to 9th?
[ONE General] cgjjaf:
HELP - NFC looping

I tried searching this thread and replying to the only comment about this issue, but no responses, so I decided to put a new comment to see if anyone can help. My phone won't stop reading NFC tags. I have one in my car dock and I have to disable NFC because it won't stop reading the tag. I tried searching in other forums and no luck. Any help will be really appreciated. Thanks.
[ONE General] Ok_Kaleidoscope5109:
You shouldn't need to flash modems separately if you are updating the ROM. Modems are already included in CM12.1 nightlies. That's why I'm not understanding when someone said that its the modem's fault. Which nightly was the modem updated to fix the proximity sensor? I don't see any changelogs that address the proximity sensor for weeks now.

---------- Post added at 11:33 AM ---------- Previous post was at 11:32 AM ----------

Where's the commit to address proximity sensor issues? Or is this a blanket statement to flash the latest nightly even if there are no changes?
[ONE General] karangupta:
The thing is that if due to some unknown reason the modem(from cm11) stays after the cm12.1 upgrade(faulty recovery, unable to flash it) then such problems occur. So people ask someone to first verify their modem version and flash the right one cause usually flashing the modem seperately does the job that flashing the whole ROM again.

And the latest baseband has been there for a very long time now, maybe there has been some changes, idk any particular as such.
[ONE General] Emama:
https://code.google.com/p/android/issues/detail?id=165558

Google don't give a **** to it.
[ONE General] Renosh:
He posted a screenshot look at his baseband version. Then scroll down and look at my baseband version, that's the correct version. He is having problems because he has wrong firmware (TWRP isn't flashing properly) and its been happening in several threads I frequent. Use some critical thinking before posting nonsense and trying to look smart
[ONE General] ninjasumit:
There's no proximity sensor issue to begin with. There's some problem with TWRP recovery due to which it doesn't update the modem while flashing a ROM. This is what broke the proximity sensor. Flashing the modem of CM12.1 nightly via fastboot solves the issue in this case.
[ONE General] Ok_Kaleidoscope5109:
Thank you for your thorough explanation. Sorry I wasn't understanding previously, but once you clarified the issue with TWRP, it makes sense now. Yes, fastboot is always the most reliable way to flash a modem.
[ONE General] the Doctor:
I don't understand the draw to use TWRP. I've always used an ancient Philz CWM recovery and never have any of these issues.
[ONE General] fmc000:
Same for me. I simply don't trust TWRP, for me the recovery is something that simply must work when I need it. No need for fancy new functions.
[ONE General] KaZo58:
yes most reliable recovery was cwm. never had problems even older version did their jobs. since cwm is dead, twrp is ****ing it up more. is anyone working for an unofficial version of cwm? i'm on twrp (the unofficial one) right now.
[ONE General] Brian325:
7/8 nightly flashed clean with ak 274 and tk gapps. Smartmax governor. Running like a champ

Sent from Hot Bacon®
[ONE General] owennewo:
I'd stick with Jul8. I think many people here have been waiting for a fix for reboot issues. I was on 1 jul and getting reboots about 1or twice a day. It's been over 24hrs on jul8 and no reboots yet. Fingers crossed that the recent kernel fixes have made these nightlies stable. The battery isn't too bad either, certainly better than my last stable nightly which has the pulled synaptic touchscreen drivers.
[ONE General] Brian325:
7/8 nightly clean flashed with AK 274. Default kernel settings except using smartmax governor. Off charger for 14.5 hours. Brightness 50%, nothing disabled and no battery saving apps. Location set at battery saving. Not bad considering the G+ drain.

Sent from Hot Bacon®
[ONE General] seco007:
I am very tempted to try this over the weekend,,I mean I have tried other solutions that have not been not successful. My only question

is do I have to install the latest FASTBOOT IMAGE: cm-12.0-YNG1TAS2I3-bacon-signed-fastboot.zip found here:

https://forums.oneplus.net/threads/mirrors-for-official-cyanogen-roms-ota-updates.141825/

Then I do the July 08 nightly??? Then everything else. (Gaaps etc)???
[ONE General] nsmart:
The fix for Trusted Face: face unlock indicator/icon not showing current unlock status on lockscreen is included in nightly 20150710 and I can confirm it is working !
[ONE General] Ok_Kaleidoscope5109:
Dang, you are totally right.

Where can I get a modem file with the latest?

Do I just do a fastboot flash for the NON-HLOS.bin file?
[ONE General] Brian325:
TWRP advanced wipe system/data/cache/dalvic cache. Flash nightly, TK gapps then ak. Wipe cache/dalvic reboot. All you need
[ONE General] omvir:
Proximity sensor working perfectly now... But my light sensor has become super sensitive now...
[ONE General] Renosh:
You can either fastboot flash that file or use the TWRP version I mentioned earlier. It works 100% and you can even back up firmware and EFS just try it you won't regret it
[ONE General] razorloves:
Banks gapps was removed from the cm wiki on the 18th, just a few hours after all that drama started. So the one on there since then have nothing to do with banks.
[ONE General] Donald Nice:
Thx for clearing this up.
[ONE General] LeroViten:
This is not that way. The sign # stands for active root activity.

For example if you get into /system directory via any file explorer with root access, you'll get that sign in a status bar and it will remain there until you end its session (a.k.a kill an app that uses su). Mostly, clearing apps from recents is enough, but if you have an app that needs root and runs in background (e.g. Servicely) you'll always have that # sign in the status bar. Stock CM su binary gets updated by CM and you get it as soon as nightly released so you don't need to do it manually.
[ONE General] etoy:
can you please link me where i can find the nightly from jenkins? thank you
[ONE General] NoobInToto:
21 build too...lol

I saw yesterday that my pa modular gapps had Google earth a few seconds after boot,and then it was gone. It seems it is not supported in India.

Todays 21 build(cyandelta) wiped gapps in front of my eyes lol...play store icon was there a second after boot,and then poof.....damn.
[ONE General] Spannaa:
It's here ;)
[ONE General] SABman12:
What is the best kernel with this rom(CM12.1) if you looking for stabillity and battery life?
[ONE General] dolphin77:
it is mentioned few pages back. Anyway, here it is:

http://download.cyanogenmod.com/get/jenkins/107777/cm-12.1-20150421-NIGHTLY-bacon.zip
[ONE General] etoy:
many thanks, i'm feeling really dumb on jenkins ;)
[ONE General] fmc000:
I always used slim mini gapps and lately slim zero gapps since dankoman introduced this third package type. Never had a single issue and I'm using it with 0421 without a single FC.
[ONE General] giaur:
As always, I flashed my platform.xml to unlock external otg write permissions. It caused tons of fcs and I was forced to refert it and wipe data (even revert original file didn't help). So I compared old nad new platform.xml and I noticed differences:

Removed:

<permission name="android.permission.HARDWARE_ABSTRACTION_ACCESS" >
<group gid="system" />
</permission>

Added:

<permission name="android.permission.ACCESS_FM_RADIO" >
<group gid="media" />
</permission>

FM radio support? I mean 04/21 nightly

---------- Post added at 10:58 AM ---------- Previous post was at 10:55 AM ----------

Didn't work for on clean flash. Weird. Maybe I messed something because of permissions/platform xml from older build. I can't remember if it was replaced or no.
[ONE General] Spannaa:
Np.

Just wondering why cm-12.1 LUNCH=cm_bacon-userdebug is still in the Jenkins queue and is about to be built...
[ONE General] Genericxx:
Using 0421 with latest Slim Zero too. Try to install Google Maps from Playstore and see if it works. Crashes for me when starting up. Maxx Audio won't run neither, although this won't be gapps related.
[ONE General] tiny4579:
If you're using cyandelta and any build on 4/19 or later, you'll need to flash the newest cm recovery or remember to flash gapps. See Danny's comments. http://review.cyanogenmod.org/#/c/95349/

I'll try to build a twrp that has an updated kernel that doesn't have this issue but may not get to it today.
[ONE General] ketut.kumajaya:
For the new CM 12.1 nightly (post 20150418), you have to use the official Cyanogen recovery for properly restore your current GApps. An alternative solution for now, a modified TWRP with current CM 12.1 kernel (f2fs support included): http://goo.gl/G2T5yY Please check http://review.cyanogenmod.org/#/c/95349/

Too lazy to set up TWRP recovery build for now, please tell TWRP developer about this transparent lz4 compressed ext4 issue.
[ONE General] tiny4579:
I was posting about this when you were. I have a build setup process for this. Also as a bonus this unofficial twrp build would support cm updater again and have double tap to wake.
[ONE General] giaur:
will simple reflash gapps after flashing rom (without wipe) solve this problem? On unmodified twrp.

Do you mean I need f2fs system partition to use this recovery? Won't it work on ext4?
[ONE General] ketut.kumajaya:
Without in kernel transparent lz4 compressed ext4 support, you will got a strange problem now or later.
[ONE General] ketut.kumajaya:
No. It's work for both f2fs and ext4.
[ONE General] giaur:
Ok thx
[ONE General] Ok_Kaleidoscope5109:
Gotcha. Yeah I wasn't sure which file it was, but I looked through a factory image script and it does do a:

fastboot flash modem NON-HLOS.bin

So I went ahead and extracted the file from the nightly, flashed it, and now I have the latest modem. I can't believe all this time I have been on some old modem because TWRP has had issues. Thanks for your help!
[ONE General] ninjasumit:
No, there's no need to flash that fastboot zip. Just flash the nightly using TWRP and then gapps. If you face proximity sensor issue afterwards then flash the modem from the nightly zip via fastboot.
[ONE General] giaur:
So what's wrong with latest official twrp? Is this reported to twrp devs to get it fixed?
[ONE General] lordsinasina:
Guys is there a jira for the compass issue?
[ONE General] xlilo:
Trusted Face ?

Latest nightly, when trying to add "my trusted face", I get a "stopped" error message...

Known issue?
[ONE General] NOSTALGIA:
what rom are you on ??? if your on cm12s no need for that.. just download and flash it through recovery...
[ONE General] W99DEY:
My compass is working.... I think
[ONE General] giaur:
Please vote: https://jira.cyanogenmod.org/browse/NIGHTLIES-1534
[ONE General] bissa:
Why every time I reboot the phone, the Profile change to silent mode? if I change to Default mode and do restart, it changes automatically again to silent mode.
[ONE General] lordsinasina:
Its working but it is messed up . if you hold your device in portrait it points to the opposite ( wrong ) direction.
[ONE General] fmc000:
Exactly, it's been like that for ages, sadly.

---------- Post added at 11:45 AM ---------- Previous post was at 11:32 AM ----------

Maybe related to the new feature described in this video?

Unrelated to those: was the reboot problem resolved by the yesterday's nightly or is it just my impression?
[ONE General] giaur:
This feature does not apply to bacon, so I don't care (I even have not idea what is it?). But now, percentage nex to battery is showing only with charger connected, it's a bug.
[ONE General] DarkBlack22:
Guys I know this isn't related but I can't get to root my OPO. Booted into fastboot mode... PC will never ever recognise my OPO. Downloaded drivers and stuffs. Under device manager nothing showed up

Sent from my N7100 using AK47 going BAM BAM BAM
[ONE General] ace_apr27:
Alright, thanks! I'll give this a shot and report back! Should I be wiping data as well, or will that not be necessary (since I'm not changing ROMs)?

Downloading the latest nightly. It's going to take just over 6 hours hours to get done over my gazillion gigabytes per second connection -_-

I wish I had found out about this sooner. It never once occurred to me that TWRP might be glitching out :(
[ONE General] fmc000:
No doubt about it, the fact is that if you look at yesterday's commits the only group even remotely related to the battery behavior is about this "feature" (I too don't know what the heck it is, BTW).
[ONE General] kundanjuit:
I flashed the latest nightly and have a strange issue, the phone screen was turned and was idle and suddenly I started to hear some voice coming from the phone. I thought some number was dialled and tried to switch on the screen to see what was running. But the screen kept turning off as soon as it turned on and was really unresponsive. So I restarted the phone with power button. I got the restart menu on pressing the power button. This happened again after an hour and this time I heard it was some FM radio sound. Has anybody experienced this?
[ONE General] clevebb:
It's a "feature" to keep the modem more secure against mistaken flashes.
[ONE General] Ok_Kaleidoscope5109:
My issue is that I use circle battery with % inside, and whenever I plug my phone in, the % is outside. It's retarded. However with no snapshots and given that's how its been since forever, I can't report it as a bug on Jira. Kinda counterproductive.
[ONE General] Spannaa:
TBH, I prefer it the way it is now with the % inside the circle normally and the charging bolt inside the animated circle and the % outside when charging.

Sent via Bacon...
[ONE General] giaur:
Even worse if you set percentage outside. In this case, no percentage visible at all without charger connected
[ONE General] fmc000:
It seems that I was right after all. Have a look at http://review.cyanogenmod.org/#/c/102492/ and at http://review.cyanogenmod.org/#/c/102893
[ONE General] seco007:
12.1.20150704-NIGHTLY-bacon
[ONE General] fmc000:
Broken build for today:

...
target thumb C++: third_party_WebKit_Source_web_blink_web_gyp <= external/chromium_org/third_party/WebKit/Source/web/WebDateTimeSuggestion.cpp
frameworks/base/telephony/java/android/telephony/PhoneNumberUtils.java:2599: error: cannot find symbol
SystemProperties.get(PROPERTY_OPERATOR_ISO_COUNTRY, ""),
^
symbol: variable PROPERTY_OPERATOR_ISO_COUNTRY
location: class PhoneNumberUtils
frameworks/base/telephony/java/android/telephony/PhoneNumberUtils.java:2600: error: cannot find symbol
SystemProperties.get(PROPERTY_ICC_OPERATOR_ISO_COUNTRY, ""));
^
symbol: variable PROPERTY_ICC_OPERATOR_ISO_COUNTRY
location: class PhoneNumberUtils
Note: Some input files use or override a deprecated API.
Note: Recompile with -Xlint:deprecation for details.
Note: Some input files use unchecked or unsafe operations.
Note: Recompile with -Xlint:unchecked for details.
2 errors
make: *** [/opt/jenkins/android/workspace/android/cm-12.1/out/target/common/obj/JAVA_LIBRARIES/framework_intermediates/classes-full-debug.jar] Error 41
make: *** Waiting for unfinished jobs....

#### make failed to build some targets (30:53 (mm:ss)) ####

real	30m53.254s
user	509m41.891s
sys	42m45.556s
Build failed.
Build step 'Execute shell' marked build as failure
Archiving artifacts
Finished: FAILURE
[ONE General] tijuanacartel:
Anyone have an issue with the rear camera repeatedly going out of focus? In CM and google camera, latest nightly.
[ONE General] ace_apr27:
This worked perfectly! Thank you so much! I forgot to wipe the system before flashing but it worked nonetheless.

I was using AK kernel, it was causing a ton of overheating issues. I'm using stock for now, hopefully It'll fix the heating scene. Let's see.
[ONE General] tijuanacartel:
ANother issue on latest nightly...

Since I've been having problems with my microphone I got a bluetooth headset. This works well. On the earlier nightly, I could long press the multi function button on the headset and launch Google Now. Cool! But on the latest this no longer works. On investigation, the option for "Hands Free" has dissapeared from google now settings. Uninstalling the updates to Google Now doesnt bring it back. Anyone else seeing the same?
[ONE General] giaur:
https://mega.nz/#!7N1gATQA!14aX0ckFoTI0xn5HKfIBDN26D8KLh7BJKFPqyObzZr4

Not broken for me. Built without any issues. Battery percentage is fixed.

---------- Post added at 12:21 PM ---------- Previous post was at 12:19 PM ----------

Yes. From the beginning, even on cm11. I reported it very long time ago, but nobody was interested. The only sulution is to use camera next or any other 3rd party camera allowing to set focus mode to "Auto" or "Infinity"
[ONE General] fmc000:
The build fix has already been committed so you probably pulled after that.
[ONE General] aeppacher:
I never reported this because it was a problem when CM12.1 came out and I knew there were a few bugs. A few months later and it still remains. If you use wireless adb debugging and try to turn off the developer settings without manually turning it off, the phone freezes and reboots.
[ONE General] :
Is it safe to flash that build? Is it just the same as the ones on cmxlog.com?
[ONE General] tiny4579:
Without the firmware and built later. Basically the same.

7/10 seems to be OK so far. I decided to flash the latest nightly in attempt to capture more info on the system force close problem.
[ONE General] X-Nemesis:
Anyone else experience this issue. Everytime I reboot my phone, I have to manually select my network to get it to connect. Is there a fix for this?
[ONE General] whitebait:
Lately I'm finding that my phone won't wake up normally, mostly when listening to music (via shuttle+) but not always. Instead, it wakes for a second with the default background, then screen black but not off, with hardware buttons still lit. It'll usually snap out of it after a while, but in the meantime the background has changed back to default for good.

I've recently done a fresh install (few weeks ago) and this has only been happening for the last few days.

Also finding that with the music gesture on it'll often start playing via the default music app when I wake the phone up.
[ONE General] fmc000:
BTW, to flash this build is it necessary to jump to a previous firmware and back of did you "fix" the TZ check?
[ONE General] giaur:
Yes it's safe. It's built today morning (cest time zone) so it basically contains all commts visible currently on cmxlog. In addition (as all of builds I made):

- selinux is permissive

- usb storage write access is unlimited for all apps

Or you can wait for next nightly.

---------- Post added at 08:41 PM ---------- Previous post was at 08:38 PM ----------

What do you mean? I have most recent firmware/modem and there are no tz errors, it flashes without any problem.
[ONE General] diskoteer:
Same for me with Poweramp. Disabling the lock screen options (show covers or controls) seems solving the issue...
[ONE General] razorloves:
next time you post a home made rom please clearly state in the same post that you disabled these major security features.
[ONE General] giaur:
I disabled them because I don't need them, moreover they are nothing more than daily usage handicap in my opinion. You don't need to agree with me though and you can use most secured official builds if you wish.

I forgot to mention about them in the same post, but all my builds will always have selinux permissive or disabled and always writing to usb drive will be unlocked.
[ONE General] tijuanacartel:
Guys any idea? The hands-free option is completely gone from my Google App. Tried reinstalling 0710 nightly and clearing google settings.

It should be under OK google in the voice menu.
[ONE General] DarkBlack22:
Had a bootloop after turning on quickboot mode. Other than that the rom is freaking AWESOME :D
[ONE General] HaloTechnology:
Why I am still needing to flash Gapps everytime I update ( dirty flashing ) ?
[ONE General] swislii:
Battery stand-by sucks

While i where sleeping the system used this much battery.

Couple months ago would only be 1%.

Cyanogenmod 2015-7-9
[ONE General] fmc000:
Not a ROM problem, mine sleeps like a baby. Try to find which app is preventing your device from sleep (plenty of answers in this thread, actually, use the search function).
[ONE General] swislii:
If thats true why isnt there any app listed so i could see what app is cousing this. But ill try to find the application, thanks.