yashsingh1/xdaforums huggingface dataset:
[ONE General] bozzykid:
Anyone have a problem with Smart Lock? I set a trusted place, yet it never works. This worked in previous builds but has been broken in the last few.
[ONE General] skiely666:
Same, had to turn it off..
[ONE General] challl88:
Flashed 0319 nightly and have problem with proximity sensor in call... Anybody?
[ONE General] eminence84:
Sorry if it was discussed, but I can't find it... Can you guys put a link to the CM camera apk you're using with the nightlies? I can't find a working one on Play, and I'm really annoyed by the bugs in the app that comes with the nightlies...

Thanks!
[ONE General] ancarloro:
x2
[ONE General] Spannaa:
Don't bother with the playstore, Search on xda!

Maybe seaech for the ported ColorOS camera too - it's even better than CameraNext and it works on cm12 too ?

Sent via Bacon...
[ONE General] AcmE85:
Apkmirror.com the camera app can be found there.

And don't believe the hype, the color os camera is not better

In terms of picture quality. They are on par.

It brings burst mode though which is a nice addition.
[ONE General] Spannaa:
It's the plugins that make the difference.

I'm not about to dump CameraNext though - panorama works well on this one.

No harm in having a few camera apps for different situations ?

Sent via Bacon...
[ONE General] BrandoHD:
I was just coming here to post about this, it seems directly related to Google Play Services updating itself to the latest version
[ONE General] cyberon:
Smart Lock is not working when other apps turn the screen off, like Action Launcher double tap to sleep.
[ONE General] geowolf1000:
Nope working for me with double tap to statusbar and hardware ?

What google service do you have?

Try generic x430
[ONE General] MarceloLagos:
Have you tried CameraNext (the one that comes with the stock ROM for the OPO)?

I'm very happy with this modded version of it: http://xdaforums.com/oneplus-one/themes-apps/app-cameranext-modded-t2999275
[ONE General] mankidavu:
OK. When initial builds of xposed came it had a lengthy process. So somewhere I found that it works only with a custom kernel which allow selinux to be changed to permissive mode.

So when I switched to cm12, I followed that tested method.

Install cm12, flash ak kernel, install the selinux mode changer apk, change the mode to permissive, install closed zip for lollipop.

Don't we need that method anymore?

I need xprivacy and YouTube ad block modules.

Sent from milkyway.
[ONE General] fmc000:
Yes, confirmed. Probably because of the new firmware included, which judging from the numbering seems to be designed for CM11. Anyways, I reverted to 0317 and all seems to work fine again.
[ONE General] cyberon:
Did you even read my post? App not CM feature. ?

More details on the link below.

https://code.google.com/p/android/issues/detail?id=79735

A workaround for this is using Smart Unlock app from Xda.
[ONE General] geowolf1000:
You are right did not fully read your post
[ONE General] BrandoHD:
Nah, nothing about my setup changed except Google Play Services itself
[ONE General] LeroViten:
Yeah, just the same. :(

~• Posted via Baconed Tapatalk •~
[ONE General] cyberon:
Have you tried clearing data from Google Settings and re-enable Smart Lock?
[ONE General] BrandoHD:
The only thing I haven't tried is flashing back to an older version of GPS
[ONE General] tiny4579:
03/19 has new but old firmware? Might have been an accident.
[ONE General] fmc000:
It has a different firmware for sure, I suppose it's an old one because the string contains the "old" MPSS.DI.2.0.1.c7-00020-M8974AAAAANPZM-1. And the symptoms are the same we had a couple of months ago: no proximity sensor working during a call.
[ONE General] fards:
seems odd, but might just need another file not pushed yet.

will have a look at it in ida tomorrow
[ONE General] waterdaan:
Something strange is going on if you look at the size of

Emmc_appsboot

Non-hlos

Static
[ONE General] Mecca EL:
Does the unofficial ROM have the latest firmware, or will I have to flash 3/18 and then unofficial 3/19?
[ONE General] fmc000:
The latest firmware is included in the official 0319, this one.
[ONE General] tiny4579:
Unofficial builds don't include firmware. So if you flashed 3/19 then you'd have to flash an older nightly or manually reflash the firmware.
[ONE General] MarceloLagos:
Just to be clear, you're saying that it's best to keep away from the firmware in 3/19 for the moment right?
[ONE General] Mecca EL:
3/19 is an old version

Thank you!
[ONE General] ragnarokx:
I ran into this problem when Lollipop was released on my Nexus 5. On KitKat I used Screen Off and Lock to turn off my screen when swiping up from navbar home key. When I updated to Lollipop, I learned that doing this "broke" the Trusted Device/Place feature.

My workaround was using Tasker to execute a terminal command to lock the screen, which preserved the functionality of the Trusted Device/Place feature of Lollipop. I linked swiping up from navbar home key to this Tasker task, and bam - worked like a charm. Those with Tasker, feel free to get creative with this - or just link it to a navigation key like I did.
[ONE General] waterdaan:
Yesterday's firmware http://dl.dropboxusercontent.com/1/view/0uhs70ltcsdbp29/xda/CM12firmware.18-3.zip
[ONE General] Mecca EL:
Dude, you rock!!! I ran out of Thanks, so I got you on the next round!!! :cool::highfive:
[ONE General] giaur:
https://jira.cyanogenmod.org/browse/NIGHTLIES-888

Vote up.
[ONE General] fmc000:
done.
[ONE General] aswinrulez:
Any idea what change this firmware is bringing?
[ONE General] the Doctor:
Not clear what you're asking for, but check here first:

http://www.cmxlog.com/12/bacon/
[ONE General] aswinrulez:
Thanks but that is the changelog for the nightlies. What i want to know is what is in the firmware update?What are the improvements with the new firmware?
[ONE General] fmc000:
CM stated a couple of weeks ago that the bootloader that they were shopping included some debug code that had to be striped before the final release, maybe this is the only change.
[ONE General] fards:
We don't know, there aren't any changelogs usually for those.
[ONE General] the Doctor:
This post implies a new camera module and new drivers.

https://forums.oneplus.net/threads/android-lollipop-update-official-release-dates.282330/
[ONE General] geowolf1000:
I receive 404 error

Is posible to upload to drive?
[ONE General] LeroViten:
+1 to this. Share please, guys... ;)

~• Posted via Baconed Tapatalk •~
[ONE General] giaur:
https://mega.co.nz/#!2VMSyKRY!3C1AJZmyovubqhFU3J2OjlZCqiBTgUOMJUsJHv3SzUU
[ONE General] Mecca EL:
https://onedrive.live.com/redir?res...8696&authkey=!AKp0nshrjp4ISVU&ithint=file,zip

---------- Post added at 07:44 AM ---------- Previous post was at 07:38 AM ----------

Done!
[ONE General] LeroViten:
Thank you, bro. [emoji121] [emoji6]

~• Posted via Baconed Tapatalk •~
[ONE General] Vriesdejoop:
yes..... +1
[ONE General] fards:
been having a look and play the firmwares included with the 19/3 build.

the rpm, static_nvbk and non_hlos are the 44s version in every single way.

it's interesting as the last few builds have had an empty static_nvbk so I've been testing the difference (and taking photos of the eclipse :D )

Using the empty file my opo doesn't pick up new data connection when switching some cells, this never used to happen until a few weeks ago.

It often sits with an exclamation mark on the signal and won't connect until rebooting the modem completely.

Using the 44s 3/19 nvbk it connects fine, on initial testing on one known black spot, I'll check some more later on.

The 44s version does have a lot of modem calls in there. I haven't flashed anything else just that one file.
[ONE General] kenhicg:
I flashed it but the sensor is still not working.
[ONE General] geowolf1000:
Thats why we vote
[ONE General] Daniel.Stevens:
I flashed back to 18/03 and then thought "what the hell"...

Wiped Dalvik/Cache, re-flashed 19/03, flashed the firmware (from the mega mirror), flashed the gapps from the start-post, wiped Dalvik/Cache again and: Sensor is working again and deep-sleep seems fine... ;0)

(GPS 7.0.97)
[ONE General] kenhicg:
I flashed this zip file then went back in and wipe cache and dalvik and everything is working fine now.

Thank you.
[ONE General] tiny4579:
Do you know when static_nvbk changed? Oh you said a few weeks ago? Hmm, maybe that had a negative impact on my battery life and I didn't realize it.
[ONE General] fmc000:
It changed with the latest update, February 16 (according to Lord Boeffla).
[ONE General] tiny4579:
The oldest nightly I have a copy of is from 2/23 and static_nvbk.bin on it is 0 bytes. Maybe it's been an empty file for a while.
[ONE General] fmc000:
http://boeffla.df-kunde.de/bacon/modems/
[ONE General] remix96:
I use cm11 rom, what cm12 i should flash? I mean the most stable nightly
[ONE General] geowolf1000:
i test again face unlock and all are normal

No more the apps use camera

Only smart lock and system

Edit : proximity after wipe is working fine
[ONE General] fullerphoto:
I just flashed 19-3 nightly with cmdelta and suddenly I now have a euphoria splash screen, is this correct? First time I've seen this on a cm nightly and it smells fishy.
[ONE General] DARLAIVE:
If you Euphoria Dark Theme is normal.

---------- Post added at 05:30 PM ---------- Previous post was at 05:22 PM ----------

Do you have an exit time for the nightly today ?
[ONE General] samflorin:
You flashed latest nightly and wiped caches and all works normally? Or did you flash the old firmware too?
[ONE General] fards:
yeah I can see the change in the 16/2 nightly. no idea why it was empty but further testing this afternoon (day off so I decided to go do my commute ride anyway to test it :D ) and modem switches properly.

On the downside both the left hand side of my xiaomi pistons died as did the left hand terminal of my sony bt headset pro while out (separate incidences) I hate coincidences!

If it wasn't for the fact that I can still hear whinging at home I'd thought I'd gone deaf in one ear.

I wish there was more info on the relationship between some of these fw files, been try to cross reference what I can, but even IDA is struggling with them.
[ONE General] AcmE85:
Today's nightly will finally include the commits which fix the play services wakelocks

and the sound issues. The cm buildbot hasn't started bacon yet but the nightly should be online in around 2-3 hours.

Would be good to know if there is any change in today's firmware/modem.

[MENTION=3505564]geowolf1000[/MENTION]

So you're saying that a clean flash from yesterday's 19.03 nightly with the included firmware

works on your device and the proximity sensor is fine?
[ONE General] fullerphoto:
Thanks buddy that's it.
[ONE General] Vaibhavarora52:
Ubifocus and super zoom not working
[ONE General] geowolf1000:
Only wipe dalvck after firmware

No clean flash
[ONE General] DARLAIVE:
With nightly yesterday, I always this problem of non-display lock screen and the PIN code request. I reinstalled the nightly, remove cache and system. Everything is up to date, I'm using the latest version of Google Apps for Lollipop and TWRP 2.8.5.1. At the first start after reinstalling or emptying caches, it works (not all the time), but as soon as I turned off or I reboot it again my problem. I hope that of today will correct that.

If you are going to test Oxygen OS?
[ONE General] AcmE85:
Could you please answer in a full sentence so that we don't spread any misunderstanding in this thread:

Did you flash the old firmware after flashing yesterday's nightly? What firmware are you using exactly?

Your answers couldnt be more confusing.
[ONE General] f231f:
Being built right now. Should be soon.
[ONE General] geowolf1000:
What exactly done

First i use delta updater

I read fmc post that new firmware is in last nightly

I download and flash it

The proximity did not worked

I flash mecca el from onedriver

The proximity still did not worked

I wipe dalvick only and the proximity working fine

I receive calls and screen light from sleep

I speak screen turn off and when i want to close screen turn on
[ONE General] f231f:
3/20 up now
[ONE General] DARLAIVE:
Installed
[ONE General] cyberon:
Are the proximity sensor issues fixed?
[ONE General] DARLAIVE:
For now I will say yes

---------- Post added at 07:42 PM ---------- Previous post was at 07:35 PM ----------

My problem with the lock screen and the PIN code request which showed no further been corrected.
[ONE General] AcmE85:
Not fixed. Sensor does not work.
[ONE General] DARLAIVE:
With my flip cover that works.
[ONE General] cyberon:
Yep, not fixed here also. ?
[ONE General] DARLAIVE:
What is unfortunate is that when the battery saver is activated, there is no vibration when receiving notifications / calls / sms.
[ONE General] whee90:
For me this fixed it: http://xdaforums.com/oneplus-one/ge...ips-tricks-t3027926/post58776196#post58776196
[ONE General] cyberon:
Which zip did you flashed?
[ONE General] waterdaan:
You need to flash cm12 from 18-3 or earlier,

There's one somewhere in this thread
[ONE General] cyberon:
Already flashed 18-3 and it worked, 19-3 from the other post is working for you?
[ONE General] vacenzo:
Hello guys,

I have clean flashed 03.15 nightly few days ago then updated via cyandelta .

Any of you experiencing poor battery?

Any ways to fix the wakelock problem?

Thanks in advance.

BTW, my NFC and WiFi (including scanning) are switched off
[ONE General] bozzykid:
Unfortunate? That is sort of the whole point of battery saver so that is saves battery.
[ONE General] geowolf1000:
I update to 20/3 and proximity still works ....
[ONE General] DARLAIVE:
True, but at least we know that we are called and we received a text message.
[ONE General] cyberon:
Did you flashed the 18-3 firmware/modem zip previously?
[ONE General] geowolf1000:
I explain at previously post

I did not re flashed at tonight built

That concern me is we hsve different results

Are we have different hardware?

I v seen this too with samsung devices and i know that different factories have variance to their material

I hope that not happend with opo
[ONE General] superiscch:
If I believe Google the OPO supports Ant+, still I can't connect my heart rate monitor to my phone. Is this a CM12 issue or isn't art+ supported.
[ONE General] BrandoHD:
Lol

Has anyone been able to test the fix for the Google Play Services Drain?

I'm here still trying to charge to 100%
[ONE General] fards:
Just downloaded but not at pc to check the firmware on the 20/3 build.

Wonder if the used eclipse to build it ;)
[ONE General] cyberon:
On call loudspeaker not working here, 20/04 Nightlie + 18/04 firmware. ?
[ONE General] tiny4579:
3/20 nightly appears to have the older modem. If you don't manually flash the firmware from an older nightly, you would have the proximity issue.
[ONE General] BrandoHD:
It's working for me here with the same setup
[ONE General] giaur:
Proximity is not fixed, still need to flash firmware. Loud speaker.... it have never worked, still does not work.
[ONE General] fards:
I'm beginning to suspect there's different hardware on these opos.

Not had an issue with loudspeaker.
[ONE General] fards:
One day scooter are going to have to build beyond compare for android.

Would make things so much easier
[ONE General] fmc000:
Neither had I. Always worked from day one (unless I'm misunderstanding you, guys. Do you mean playing music or doing phone calls using the speakers?)
[ONE General] AcmE85:
You never know what audio mods, custom kernels and other shenanigans users might have on their devices...

Unless someone proves me wrong I highly doubt it is different hardware, rather user error.

Never had any issues with the speaker on phone and with music on my device.
[ONE General] giaur:
I mean that weird icon available on screen while calling. It does nothing. As far as I remember it's called Volume Boost (english is not my daily driver). It only always says me thast volume boost is off.
[ONE General] waterdaan:
[STRIKE]https://docs.google.com/file/d/0B6Xp-OPuddGwZjlWWHhIaFBFRms/edit?usp=docslist_api[/STRIKE]

I flashed

NON-HLOS.bin and rpm.mbn

From 18-03

Seems to work fine, proximaty sensor and loud speaker while on call

Google search showed that rpm.mbn has to do with Resource +Power Management and NON-HLOS.bin is the modem

Question

I'm unsure what happens in recovery while I dirty flash, seems not everything gets flashed . Recovery log says already up to date and I guess it won't get flashed

EDIT https://docs.google.com/file/d/0B6Xp-OPuddGwUjFIYTl3eDhxT00/edit?usp=docslist_api
[ONE General] cyberon:
My "on call" loudspeaker wasn't working, cleaning both caches and rebooting fixed the issue.
[ONE General] giaur:
There must be flashed something else because with latest firmware proximity sensor does not work
[ONE General] geowolf1000:
But worked for me.....

And did not flash anything else
[ONE General] waterdaan:
I flashed latest nightly and

NON-HLOS.bin and rpm.mbn

From 18-03
[ONE General] kthejoker20:
muffled microphone... no one can understand me on calls, latest nightly cm12
[ONE General] spyd4r:
Last 2 builds the phone app is useless. Just makes the screen black and unresponsive to any buttons.
[ONE General] Donald Nice:
Disable OK Google on any screen.
[ONE General] j3di:
My Ant+ heart monitor belt works fine, but you need to download "Ant+ Plugins Service" and "ANT Radio Service" from Google Play.
[ONE General] geowolf1000:
With last built.... ?
[ONE General] fards:
Ok furrher testing on the firmware.

Still losing data on cell change with just nvbk swapped out to 44s version

Still not got any logs of it, but observed completely lots of signal (I know where it is exactly now so will reproduce with logging) followed by reconnection of voice but no data. Shouldn't lose signal, I wonder if there's a msm reset.

Hmmm
[ONE General] mishko:
Thanks for the tip but what do u mean by 'on any screen'?
[ONE General] WhiteHartMart:
Google settings have 2 options - enable OK Google from home screen and also 'from any screen' - disable the 2nd option I guess ;)

Brought to you by a CM12 Lollipopped OnePlus One :)
[ONE General] mishko:
Got it, I think![emoji4]
[ONE General] vacenzo:
Wakelock problem seems to be fixed on 03.20 nightly.

No issues with proximity sensor either.
[ONE General] fmc000:
Just to be clear: did you flash the 0320 nightly and nothing else? Can you please post a screenshot of the "about" page? I'm asking because 0320 ships with the wrong firmware so it's hard to believe that you have the proximity sensor working without further actions on your side...
[ONE General] bagadj:
flashed latest nightly via cyandelta and got bootloop.... :(:( no way to get phone back even tried to flash a previous nightly, now i'm restoring a backup...
[ONE General] vacenzo:
Updated via system updates, wiped cash and dalvik and works like a charm so far.

I only checked while on phone call tried to cover the sensor and it switches screen off and when uncover - screen comes back on.

EDIT: works some times, just had few apps launched with my ear while on phone
[ONE General] fmc000:
OK, thanks. Let's wait how long it takes for CM to correct their mistake and ship the right firmware again.
[ONE General] DrearierJester1:
Force turn off for 3 mins and turn back on, it should boot fine.
[ONE General] Naughtie:
The last few updates have really messed up the phone. i have had few issues from last few days some of them are now kind of fixed(I hope)

1. Proximity Sensor(Not Fixed)

2. My voice not audible on the other side during calls(Not fixed)

3. Smartlock with Mi Band(was broken for couple of days, working alright as of now)

4. Bluetooth pairing (again Mi Band, either the smart lock was broken or it was getting unpaired every now and then, looks fixed now)

5. Massive Battery drain(Not Fixed)

6. Wakelock(Not fixed, could be a proximity sensor issue)

I don't know how to fix everything but the biggest problem for me is the Proximity sensor. Devs need to push an update for fixing Proximity sensor, Wakelock and Voice quality at the earliest using the phone with these is a major PITA.

Regards
[ONE General] polishpt:
calls not working

Flashed the latest 20150320 nightly yesterday and since then im not able to make/receive calls, sms messages are working fine.

After that i flashed 20150318 nightly and old bacon firmware from 2015-02-09 but still can make or receive calls.

Is there a fix for this or we need to wait for CM team to fix it in next nightly ?

Thanks
[ONE General] waterdaan:
Read a bit
[ONE General] vacenzo:
Those who have wakelock problem try disabling "prevent accidental wake up"
[ONE General] fards:
Further testing.

Using 18/9 non hlos with the rest of

20/3 firmware results in no working proximity sensor, 11ma draw from sensor but reliable cell switching.

Using 18/9 hlos results in working proximity sensor 0.34ma draw but flaky cell switching.

Looks like I was wrong with the nvbk.

For anyone using the 20/3 and thinks they have a working proximity please grab a sensor app from the play store and check the power draw of it.
[ONE General] Sk.D:
New cm12 builds are good, except for video buffer bug!!!!!!!
[ONE General] Naughtie:
I tried but too much unnecessary information in between. I read last 5-6 pages and realized that quite a few people have been reporting problems and some have linked to solutions also but seems its more of a hit and trial and not a sure shot fix. For example there was a link for a fix for proximity sensor fix but it was directed towards people with multirom and running both CM11s and CM12 having proximity sensor issues.

Just saying...
[ONE General] geowolf1000:
What appp want to use?

Is maybe relate to root?

I use supersu

Is any with problem ussing supersu?

Lets test and this
[ONE General] BrandoHD:
A few posts back, someone posted a link to the firmware from the nightly that was labeled the 18th, if you flash that, the proximity sensor would be wrong again (it's what I did)
[ONE General] Renosh:
For Proximity Sensor issues flash this

For voice quality issues disable Ok Google detection on any screen (Look for Google Settings in app drawer > Search & Now >Voice > "Ok Google" detection

The rest; I don't have bluetooth devices I use and don't have massive battery drain on 03/20 nightly with Google Play Services any more
[ONE General] AcmE85:
Today's nightly is online and the

static_nvbk.bin is back to 0 mb size.

Today's nightly fixes the proximity sensor

I just dirty flashed it without wiping anything.

Baseband-Version is:

DI.3.0.c6-00230-M8974AAAAANAZM-1
[ONE General] Naughtie:
Flashed the file through TWRP and proximity sensor is working alright it seems. Thanks for that :)

And the google voice search services were already switched off. Maybe the latest CM Nightly fixed that :).

Will search for the rest solutions on the forums/thread itself.

Thanks Again
[ONE General] hughfollett:
Today's nightly is up! Anyone knows if the proximity sensor is fixed without flashing the 1803 modem?
[ONE General] AcmE85:
Usually I'm not that kind of guy, but did you seriously miss my post?

Good example of what is wrong in this thread. smh
[ONE General] hughfollett:
Sorry for that! I actually missed your specific post I asked because the post previous to yours still suggests to flash the old modem. Sorry, again, but I always read the thread..

EDIT: just noticed the I may have missed your post thanks to chrome adapting the page after finishing its load. (I'm from mobile)
[ONE General] dubazar:
deleted.
[ONE General] spanielhead:
Proximity sensor working on today's nightly, 21/3 :)
[ONE General] polishpt:
sorry for mentioning this again but flashing latest nightly 21/3 didnt solve the issue i have.

after flashing 20/3 nightly yesterdaty i do not get notification when there's an incoming call. a caller hears a signal but there's nothing on my phone.

also, i cannot make calls, 'Dialling...' flashes on a screen but a person im calling to never gets a call

Im able to send and receive messages and mobile data works fine.

Tried flashing a 15/3 night (latest working for me) and that still didnt fix the issue. any ideas? Im really confused now

Thanks
[ONE General] giaur:
Don't use non stock kernel

---------- Post added at 04:18 PM ---------- Previous post was at 04:17 PM ----------

Yes, I can confirm.