yashsingh1/xdaforums huggingface dataset:
[ONE Android Development] mannu_in:
auto unlock when entered the correct password

Is "auto unlock when entered the correct password" there in any of the build. I remember it was there in CM11 versions but didn't find this feature in CM12 versions. Am I missing anything here/any option to to select for enabling the feature?

UPDATE - So that is Quick Pin Unlock which is mentioned few posts before..... [MENTION=1095206]daleski75[/MENTION] - any chance to get this feature in your builds?
[ONE Android Development] highdiver_2000:
Hi Anyone having problems with the proximity sensor? I noticed that when I am on a call, the screen did not go off when I hold it next to my ear. It turned off due to the screen saver. So when I hold it down, all I get is a black screen.

4 Jan stock.
[ONE Android Development] hidea:
According to this post: http://xdaforums.com/showpost.php?p=57960104&postcount=4249

We just need to wait for those commits to be merged into CM12! Hopefully sooner than later ;).
[ONE Android Development] davru:
Flash the new modem
[ONE Android Development] giaur:
CM11 nightlies are not showing in cm updater any longer. Official cm12 nightlies are coming.
[ONE Android Development] Izachii:
[MENTION=2225481]dals[/MENTION]eki75 thanks for doing all the new build for oneplus! After using this rom for days, i can report back is that the bluetooth latency is vert low nowadays so whenever your using a bluetooth headphones the video or anything your watch will actually sync between the audio and the visual. When i was on KitKat they always had that problem. Thanks man!
[ONE Android Development] PuCiNhOOO:
What modem? Can you post a link for the download?
[ONE Android Development] davru:
Took 10 seconds to find it with search function https://mega.co.nz/#!MMJhBBJR!GoXHNociOvfByHrijY4RVsTlR_EooAFiUaLBYeSk32k
[ONE Android Development] dohnkendall:
Here it is. This has been discussed several times in this thread.

Nok918 - Nok5160 - MotoP280 - MotoT720 - MotoV551 - SoErW200 - BBBold9700 - SamGS - SamGS3 - OnePlusOne
[ONE Android Development] Spewmonic:
Anyone else faced a delayed dt2w after taking the phone out from a pocket?

I've flashed the Alpha Modem after each build so just wondering if I'm the only one facing this.
[ONE Android Development] Izachii:
Not for me.
[ONE Android Development] AcmE85:
It has nothing to to with the modem. Happened to me couple times in the past with cm12.

It also was asked in this thread a couple times.

Just wait, it will fix itself eventually...
[ONE Android Development] tiny4579:
Rebooting after the first boot after the flash helped for me.
[ONE Android Development] Spewmonic:
Um... Why is it that nearly all the replies asking about the DT2W not working get a reply of "Please flash the Alpha Modem and it will be fixed." or something along that line? :|

Before the 2015 builds, I've never had any issue with DT2W or the touchscreen. :|

Alright, will reboot a few more times and see what happens.
[ONE Android Development] jam90:
does the proximity sensor works properly with this 01/05/2015 build, finally?
[ONE Android Development] uktechguru:
I have experienced the same problem with the dt2w delay and having to double tap more than once to wake the phone up. The modem flash is to do with the proximity sensor which makes the screen black out when the phone is to your ear whilst making/receiving calls to avoid accidentally pressing on the phone and inadvertently doing something. It may even help on the ambient display too as that uses the proximity sensor.

Problem with this forum is that when you ask a harmless question you get either a rude response to make you feel dumb or like an idiot for asking or a smart arse reply. I agree that some queries have been dealt with and people should read back before posting but it's those few people who are rude that ruin it for others. I thought the point of forums was to help each other out and not get shot down for asking questions.

[MENTION=1637948]daleski[/MENTION] is doing a fantastic job but some people are taking over with their own 2 cents and confusing things for those of us who aren't up with the finer details of the roms and contents of the builds. I've already been shot down with a rude reply. Those people should, in my opinion, either be nicer to other users or just don't reply at all.
[ONE Android Development] Jur1nator:
yes, forums are so that people can help each other out but this here is still supposed to be a dev thread.

if you want to ask questions without even making the effort to read the last few pages like most people here do that get shot down, there is also a dedicated Q A thread.

it's that Easy
[ONE Android Development] AcmE85:
Because these users restarted their devices to flash the modem. So actually it was the restart not the modem.

This happened to me once since I already had flashed the new modem. So it was again not "fixed" by the modem.

As I said before, it fixed itself after some time without restarting my device.

edit: there are some open camera commits in the pipeline, I wonder what they might fix.
[ONE Android Development] giaur:
Very interesting commit! http://review.cyanogenmod.org/#/c/83417/, not merged yet
[ONE Android Development] ale_bot:
hi everyone

my nexus still has PA 4.4.4, what do i have to do to flash this unofficial cm12?

do i have just to download zip and flash it or, coming from KitKat maybe i have to flash also something else (modem?)?

Thanks :)
[ONE Android Development] AcmE85:
You should ask in the Nexus # (# = your device number) section on XDA. This thread is strictly for the OnePlus One.
[ONE Android Development] AcmE85:
It is this questions that p*** some people off and I can understand them...

To answer this another time:

Yes the proximity sensor works fine, if you flash the new modem provided by OnePlus Alpha Rom.

If I flash something I make sure that I read read read...

This file was last posted only two pages ago

https://mega.co.nz/#!MMJhBBJR!GoXHNociOvfByHrijY4RVsTlR_EooAFiUaLBYeSk32k

If searching the thread is too much for some people, they just shouldn't flash custom roms, period.
[ONE Android Development] jam90:
before you'll get an heartache, my question was if now the proximity sensor works WITHOUT FLASHING THE MODEM by oneplus alpha rom..."Period"
[ONE Android Development] i4mt3hwin:
No, again as stated multiple times in the last 20 pages it won't and never will. The implementation of the proximity sensor was changed in firmware and going forward you need the new modem for the sensor to work with CM12. This won't be reverted it's just how it's going to be from this point on.

I mean I get that XDA/Forums are not the best way to convey information like this (roms with constantly changing info) but just the other day I was able to figure out everything i needed to flash this and getting it running on my phone within like 10 minutes. If you don't want to spend 10 minutes learning what you need to learn then you should probably just stick with stock or whatever.
[ONE Android Development] AcmE85:
I'm not mad at you, you just served as a good example. I don't care what you think because I don't know you personally.

Therefore it is not my goal in any way to offend you :)

Also that was not what you asked, you should have phrased your sentence better then.

I'm pretty sure that from now on, an updated modem will be needed.

Why else should OnePlus use it for their own Alpha Build? Also CM isn't writing the drivers (camera, proximity sensor...) themselves.

Opo delivers them... and they are using the same one for the proximity sensor in their own Alpha.

Keep in mind that every commit that is beeing merged isn't there to make us happy!

The work is done so that finally the official nightlies can be released WHEN THEY ARE READY and

they will provide the needed modem! Each official cm11 nightly came packed with a modem!
[ONE Android Development] airtower:
This isn't directed at you or anyone else in particular, but I think it puts into prospective why some people on xda come across as rude.

People are rude because there's two type of people in each thread. There's people that effectively read every post and come in several times a day, and there's people that just drop in and ask redundant questions about issues that have been previously discussed ad nauseam. The first group spends so much of their resources keeping up to date on the bleeding edge that they feel offended someone should come in and get an answer so easily. So to make up for it they take the time and effort to post something terse or demeaning just to assert their greater intelligence on the subject, as opposed to a simple answer. The relationship between the complexity of the question is inversely proportional to the magnitude of the outlash against the naive poster.

This ^
[ONE Android Development] jam90:
damn, guys, I was just asking...

I flash custom roms since i had my samsung galaxy wonder, I'm not a noob just because I didn't see some of the thousands replies (btw I didn't see any question like mine, but only "why sensor proximity doesn't work??")

I was asking just because i read this at first page

msm8974: Enable new proximity sensor code

Just a quick answer or maybe just a "no" was more than enough...now please, let's stop talking about this to avoid messing up this thread.

Peace
[ONE Android Development] AcmE85:
This commit actually hasn't changed since it was initially merged:

http://review.cyanogenmod.org/#/c/83272/

It's just that a commit gets pushed to the top of the list each time a dev comments on it (compare the date and time).

[MENTION=1095206]daleski75[/MENTION] I think you overlooked that.

Peace, no hard feelings there
[ONE Android Development] i4mt3hwin:
I mean I agree with this to an extent. I think for constantly moving material, like a nightly rom, forums in general are a horrible way to convey this type of discussion/chat. I mean when a big update hits the information can literally be scattered across 30 pages within a day and it's not like the search really helps you locate the information you're looking for.

That being said, the radio/proximity sensor has been covered to death for the last several days. I check this thread maybe once every 2-3 days and I have no problems spending 10 minutes catching up on what I need to get my phone working. You can infer a lot from various posts too that don't quite have all the information but enough for you to make an educated guess or point you in the right direction.

It gets frustrating though when out of those 30 pages 10 of them are people asking the same question or saying they have a problem with the proximity sensor and literally 2 posts above someone says "flash the new modem to fix the issue". Granted in this particular case Jam90 already knew the radio fixed the issues but was wondering whether the new nightly remedied the need for the radio in the first place.

I think daleski75 should add that the new radio is essentially necessary for the newer builds in the OP.
[ONE Android Development] jam90:
glad to see this :D
[ONE Android Development] v0 HaVoK 0v:
Hey, does anyone get the problem with no reception during deep sleep?

As you can see from this picture, the no cell reception all night destroys my battery. Im using ak077.
[ONE Android Development] cheatbreak:
This thread has 500 pages so no crying please.
[ONE Android Development] fragargon:
avoiding this Op daleski could add this on his first thread!

just m2c
[ONE Android Development] uktechguru:
Yep I agree with what people have said so far but the q&a thread doesn't get an answer sometimes which is probably why some might jump onto this thread being the main one to re ask the question in mind.

I visit the thread quite a lot throughout the day to see what's new etc. It's the remarks like when there was the problem with missing root/super user and apparent merge into privacy guard and I got a remark back after I commented by saying I reflashed the su to get root back. The comment being something akin to "oh look at him thinking he's smart!" That's what hurt when a simple "no that's not it, it's been merged into privacy guard" would have done.
[ONE Android Development] highdiver_2000:
I wonder what changed in the CM12 code that requires a new driver installation. It is not as if we are unlocking some hidden function. Weird
[ONE Android Development] AcmE85:
To change the subject, work to implement the new camera2 api has started

http://review.cyanogenmod.org/#/c/83901/

(not merged yet)

There are also more camera related commits to be merged soon.
[ONE Android Development] giaur:
Hope they are going to fix 4k recording with 3rd party apps.

---------- Post added at 06:03 PM ---------- Previous post was at 06:00 PM ----------

Yep, but note that he probably have no time to read all messages posted and decide/verify what to add to first post.
[ONE Android Development] Spewmonic:
Now something else is bothering me.

If I restart the phone after setting it up, no matter what kernel I use, the phone will go and bootloop. It boots up until the lock screen, let's me unlock and then it just hangs there and restarts itself after a while. I honestly have no idea what could be causing this.

I wiped twice over the course of my last post. Even if I now flash 04/01, it will still restart itself. :| Help. :(
[ONE Android Development] v0 HaVoK 0v:
That's sounds like something I had before, had to reflash persist to fix it.
[ONE Android Development] giaur:
Have you tried to wipe data? Maybe try to flash complete stock cm11s via fastboot and see if it helps. Also - you should not ask here, you should create thread in troubleshooting section, especially if cm11s will not work as well. It should not happen, possibly you have some hardware problem?
[ONE Android Development] hidea:
if you have the time and willing figure out what's the cause (solely to entertain your curiosity), try using adb logcat. I did that a few days ago for a CM specific issue, it was very VERY satisfying at the end knowing it was only something CM could fix. :P
[ONE Android Development] tobitege:
[MENTION=2135181]Spewmonic[/MENTION]: have you flashed new OPO LP modem (see few pages back) on current build? It should be.
[ONE Android Development] giaur:
I tried with older modem, it only breaks proximity sensor, no bootloops. There must be wrong something else
[ONE Android Development] Spewmonic:
Well, I thought someone else has experienced this. Rather than splitting everything everywhere, yes I know it ain't proper, I thought I'd just be that dumbass that asks stupid question that everyone would hate.

I'm pretty adamant about staying with CM12 so I won't be flashing 44S just to see if it works or otherwise.

Sadly, I do not have the time to logcat and figure it out during the weekdays.

Yes, I did that after every flash for the past 2 days.

If anyone could tell me how to get rid of the # logo at the top, that would be great as well.
[ONE Android Development] highdiver_2000:
Did you flash the right gapps?

Cleared the cache?
[ONE Android Development] kamil205:
I cannot have any signal with the new modem. Tried in dirt flash, clean flash, and even other cm12 builds and cannot manage to get any signal in 1+1 int.

I am currently in Portugal, do not know if this a lack of compatibility with the band in the country. Never had any issue with any international modem, so it is not a weird country :P I also tried several to flash zip packages and in all the same result.

If I flash back the previous modem, signal comes back as previous, but I get the reported problems.

Any idea?
[ONE Android Development] tobitege:
[MENTION=2135181]Spewmonic[/MENTION]: You only need to flash a modem once, it's not touched by rom flashes/wipes.

The "#" sign is either that SuperSU wants to apply an update OR on newer builds a new CM feature to indicate that an app is using root permissions.
[ONE Android Development] highdiver_2000:
# logo = su app needs to be updated
[ONE Android Development] Spewmonic:
Hmmm... Alright, I'll keep that in mind about the modem.

I did get a message saying SuperSU is old when I opened TiBu for the first time after a clean wipe. Not sure how to do it, now.

I thought as much but I'm seriously not sure how to do it.

Edit: just to be clear, I know how to update, flash the SuperSU zip but with CM's latest settings, the app would be restored if I flash the zip.
[ONE Android Development] giaur:
You don't need to stay with 44s, maybe there is something messed and flashing complete stock image can help. Then you can flash cm12 again
[ONE Android Development] captive:
You are wrong:

# logo = an app running (even in background) required root privileges
[ONE Android Development] giaur:
It's not true, on cm12 it indicates active su session, it's not notification, only icon on taskbar.
[ONE Android Development] hidea:
[MENTION=2135181]Spewmonic[/MENTION] FYI, that pound sign (I refuse to call it 'hashtag' in this context) is to indicate there's a 'su' session running. In the most recent CM12 nightlies (last two days?), the Superuser app is deprecated; the functionality is now a sub-feature within Privacy Guard. I'm unsure if it's an indicator for anything else (such as outdated su binary or something else), though.
[ONE Android Development] Norapapa:
TB do not work with the included superuser. After I Flash SuperSU, TB works perfect.
[ONE Android Development] Spewmonic:
I realize that CM has updated their SU handling into Privacy Guard.

Check the screenshot and tell me if anyone has the same. I do feel that I should flash the SU zip again but I don't want a boot boot boot boot bootttttttt. :crazy:
[ONE Android Development] airtower:
Not exactly. # to the left is probably from supersu, # on the right (near the signal indicators, clock, etc) is CM root telling you an app has root access. It cannot be cleared like the supersu notification.
[ONE Android Development] giaur:
I think it's TB fault, you should report issue to them. Also you can try with permissive selinux, it may help. Also, what if you ignore this warning?
[ONE Android Development] MickyMax:
The audio stuttering is it solved in the last nightlies? I have more than 5 GB of music synchronized in Spotify and I would only flash if I can listen music.

Thanks
[ONE Android Development] Spewmonic:
I ignored the warning and backed up everything without issue. It's the only thing, so far, that's hinting to me that my SU may be using an outdated binary and there's no way for me to check conclusively.
[ONE Android Development] giaur:
I tested yesterday build and seems to be all ok (1.5 h listening without issues).
[ONE Android Development] rlaw:
TiBU has had issues with built-in superuser for a long, long time now.

Certain functions may not work (backup/restore), certain system apps may not allow you to freeze/uninstalling them etc.

Those are the problems I've run into with TiBU and built-in superuser and these go back a long time. SuperSU is just much, much more stable and usable.
[ONE Android Development] kozianozdra:
In "Status bar" menu I change "Battery status style" to "hidden" and after restart battery icon appears again... every time

And Gestures are lost. Please bring back V-torch light and O-camera.

And more customize options for Lock Screen will be appreciated . Thank you!
[ONE Android Development] mani0608:
It's coming friends. Finally!!

http://review.cyanogenmod.org/#/c/83417

http://review.cyanogenmod.org/#/c/83418
[ONE Android Development] union1mc:
I'm still having a few stuttering issues, but it's much more minor. This is using PlayerPro, so another music player may produce different results.
[ONE Android Development] giaur:
Let's consider something. Titanium Backup is the only app having problems with built in root access. From unknown reasons. I think it's TB issue, CM built in root access is ok and stable. I see no reason for flash super su now and make mess in my installation. If titanium backup can't respect granted root permissions, I would rather drop titanium backup.
[ONE Android Development] nolsen311:
TB does warn about mount namespace separation; has anyone investigated this?
[ONE Android Development] Spewmonic:
I decided to flash SuperSU 2.40 anyways just to see what happened. Too early to tell if I would stop getting the reboots.

Fingers, toes and anything I can cross are definitely crossed.

Thanks everyone for your suggestion. Let's hope there would be a solution for this if anyone else has it.
[ONE Android Development] i4mt3hwin:
Yeah I still have a few issues too -- with PlayerPro, Shuttle and Google Music. Sometimes I get a little bit of skipping and it seems like if I leave my device on for a few days without restarting I get some glitching, where it makes a weird screeching noise.
[ONE Android Development] fards:
Not actually true. D2tw relies on proximity check if you have the prevent accidental wake up ticked.

The modem fixes proximity.

Proximity does not work on the current builds without the modem.

And for those complaining about rude responses, think on this...

asking the same question without bothering to investigate is rude.

It's against the forum rules, it takes second's to search the thread. There's a very high chance your question has been asked several times already and answered just as many.
[ONE Android Development] daryelv:
This thread isn't about feature requests or asking Daleski75 to make fixes. Daleski75 is kind enough to compile the CM12 code from the CM repo for our device and post it online for us to use. He does a straight build without cherrypicks. Please log the bugs and feature requests on the CM jira website here https://jira.cyanogenmod.org/browse/BACON so that the people handling the code can make the bugfixes and changes.

-Daryel
[ONE Android Development] djbenny1:
Guys I updated the radio but now android phone crashes on boot and I've no signal??? Am I being stupid? I just flashed the radio zip in recovery?
[ONE Android Development] insestito:
Why when i update from settings "CM Updater" i have bootloop?
[ONE Android Development] :
cause that doesnt work on this... cm does not have a build rom officially out.
[ONE Android Development] tobitege:
Try flashing the rom again as usual with wipe cache/dalvik, might fix it.
[ONE Android Development] sbenson1226:
Face palm.
[ONE Android Development] rlaw:
I did state TiBU specifically has these issues and that SuperSU is the solution. I understand the coolness and convenience of controlling all app permissions, including su, from one central location but superuser/CM apologism doesn't change the fact that SuperSU results in a superior user experience.

This all regardless of my personal opinion that Chainfire is the most knowledgeable and experienced in the Android dev scene when it comes to su solutions..
[ONE Android Development] AcmE85:
Yes I know, but with the old modem and new sensor firmware dt2w always worked for me, regardless if "prevent accidental wake up" was ticked or not.

I was responding to the claim that the new modem fixed delayed dt2w for some users.

:good:
[ONE Android Development] giaur:
I have no bootloop, just no update found.
[ONE Android Development] LiquidSolstice:
Yes, because there is no nightly server right now. It will not do anything because official nightly builds have not begun. Daleski is compiling and uploading for you so that you don't have to compile yourself. He'll most likely stop when official nightly builds start, and trust me, you'll be well aware of when official nightly builds will have started.

Stop trying to use it.
[ONE Android Development] AcmE85:
Up until today's build, the cm updater showed cm11 nightlies.

He must have still been on yesterday's or a previous build,

of course his device will go into bootloop when flashing those...

As often it is the users fault here for not reading what the device is showing him.

btt:

many camera and framewrk audio/video fixes have been merged to the oneplus kernel this hour :)