yashsingh1/xdaforums huggingface dataset:
[ONE Android Development] spyd4r:
hrmmm...
[ONE Android Development] fmc000:
Try this :

* exit Nova

* start launcher 3 "just once"

* open drawer

*press home button

You should see the launcher FC. Select Nova as home "just once" and repeat the steps :you should see Nova FC. Then select Nova "always" and you'll be fine.
[ONE Android Development] miragez:
I tried your steps, no fc appearing at all.
[ONE Android Development] fmc000:
Sorry if I wasn't clear, what i meant is that you should see no direct "system has stopped" FC but only the launcher restarting.
[ONE Android Development] miragez:
I actually understand what you look at :p coz it happens to me on build 01012015, but on build 02012015 it has been resolved.
[ONE Android Development] fmc000:
Uh, ok, thanks for your time, then. I'm able to reproduce the bug with both launcher3 and launcher 8 pro (which is my default launcher). However, it doesn't bother me at all, as I set launcher 8 pro as default home "always". I think this is something that is not worth a clean flash for me IMHO.

So I will see that if further releases will take care of this as a side effect. Thanks again.
[ONE Android Development] MickyMax:
Where did you found that?
[ONE Android Development] fards:
Look through the commits
[ONE Android Development] MickyMax:
Of cm11 or cm12?
[ONE Android Development] fards:
Does that really need asking?
[ONE Android Development] daleski75:
Doing a new build now guys a lot of good commits in this one.
[ONE Android Development] daleski75:
New build up guys go grab it.
[ONE Android Development] jdfeos:
I love you dude :p
[ONE Android Development] opee:
Wi-Fi gets broken for me by dirty flash! Do a clean flash later this day...
[ONE Android Development] fards:
Might be an issue with proximity and deep sleep.

Testing at the mo
[ONE Android Development] blackfire2802:
I have a problem with contacts syncing... Please help.. I have contacts synced...but every time I receive a call or text it shows only the number
[ONE Android Development] tobitege:
Try setting all animations in developer options back to 1 if not already set that way. This was suggested by some user(s) in other threads but may still be buggy.
[ONE Android Development] AcmE85:
No problems here with dirty flashing.
[ONE Android Development] fards:
WiFi is ok here, have you flashed a custom kernel?
[ONE Android Development] hapee:
No wifi problems after dirty flash, no problem at all so far
[ONE Android Development] blackfire2802:
Animations are already set to 1...is there anything else thant I can try?
[ONE Android Development] meisell:
WiFi os for me too, also dirty flashing :)
[ONE Android Development] tsiftsism:
Same issue here, WiFi is grayed out.

Just flashed todays build over 25/12 build, Slim_full_gapps.BETA.5.0.x.build.0.x-439 and boeffla 3.0-alpha10 kernel.

Do you think that the kernel causes the issue?
[ONE Android Development] PresidentMcCain:
Yes, I think so. Lots of changes relating to Wi-Fi were made to the CM kernel within the last day or so.
[ONE Android Development] tsiftsism:
Just dirty re-flashed rom and gapps without the custom kernel and WiFi is working again.

That was the problem. ;)

Thanks again.
[ONE Android Development] nicola1989:
My wifi work's without any problems here!
[ONE Android Development] kitkatcamusa:
WiFi work's better from yesterday build for me!
[ONE Android Development] Santic7:
Is anyone having problem in the latest build with dt2w? The screen isn't responding, only when i tap few times more. I dirty flashed, as all previous builds and i had 0 issues...:) Definitely best Lollipop rom for One +1.

Sent from One +1
[ONE Android Development] fards:
From what I can see (not on pc do can't adb) looks like proximity is having issues.

Disable the pocket protection and it works a treat
[ONE Android Development] tiny4579:
Does it work better if you disable accidental waking? Proximity sensor seems messed up for me right now.
[ONE Android Development] Santic7:
Disabled it and it looks like it works better... Will report later if "the problem" is still there. Thank you.

Edit : It seems disabling accidental waking didn't fix the problem, it's still here.

Sent from One +1
[ONE Android Development] hidea:
I've been trying to turn on encryption, but I haven't had much luck so far.

When I try to turn on encryption, it just shows me that outlined Bugdroid, and reboots the phone shortly after. Seems that it's not encrypting anything at all.

E/QSEECOMAPI: ( 216): Error::ioctl call to create encryption key for usage 1 failed with ret = -1, errno = 22
E/Cryptfs ( 216): Error enabling encryption after framework is shutdown, no data changed, restarting system
E/qdoverlay( 217): Bad ov dump: mdp_overlay z=0 fg=0 alpha=255 mask=-1 flags=0x0 id=64
E/qdoverlay( 217): src msmfb_img w=1536 h=1920 format=5 MDP_RGB_888
E/qdoverlay( 217): src_rect mdp_rect x=0 y=0 w=1080 h=1920
E/qdoverlay( 217): dst_rect mdp_rect x=0 y=0 w=1080 h=1920
E/qdoverlay( 217): Bad ov dump: mdp_overlay z=0 fg=0 alpha=255 mask=-1 flags=0x0 id=64
E/qdoverlay( 217): src msmfb_img w=1536 h=1920 format=5 MDP_RGB_888
E/qdoverlay( 217): src_rect mdp_rect x=0 y=0 w=1080 h=1920
E/qdoverlay( 217): dst_rect mdp_rect x=0 y=0 w=1080 h=1920
I/qdhwcomposer( 217): handle_blank_event: dpy:0 panel power state: 0
E/qdoverlay( 217): Cant open device /dev/graphics/fb0 err=1
E/qdoverlay( 217): Ctrl failed to init fbnum=0
E/qdoverlay( 217): Cant open device /dev/graphics/fb0 err=1
E/qdoverlay( 217): Ctrl failed to init fbnum=0
E/qdoverlay( 217): Bad ov dump: mdp_overlay z=0 fg=0 alpha=255 mask=-1 flags=0x220000 id=-1
E/qdoverlay( 217): src msmfb_img w=1152 h=1920 format=13 MDP_RGBA_8888
E/qdoverlay( 217): src_rect mdp_rect x=0 y=0 w=1080 h=1920
E/qdoverlay( 217): dst_rect mdp_rect x=0 y=0 w=1080 h=1920
[ONE Android Development] zag0:
Does anyone have a problem with proximity sensor on the latest build (14/01/03)? When I'm in call the screen won't turn off, I have to press the power button to lock the phone and then unlock it when I want to end the call (if the other side doesn't do it before me). I didn't have this problem 2 builds back (14/01/01).
[ONE Android Development] dsmpampis:
I have the same issue(Broken WiFi) flashing a custom kernel(AK 0.74)!

But on stock the issue is gone .....
[ONE Android Development] L10nH34Rt:
Got a proximity sensor issue as well. Couldn't wake up the phone at all. Had to turn it off and the back on again.

Disabled Accidental Wake-Up Prevention feature and will see if that will help.
[ONE Android Development] xdaywalkerx:
:good: same here with ak 074
[ONE Android Development] giaur:
I can't confirm, I don't have any problems
[ONE Android Development] ntonzrockz:
Hi guys

Well i heard that there is Problem between CM and OPO, I guess the official CM 12 will not launch in anytime soon.

So I will try this unofficial build, but can you guys tell me what is the major bugs in this ROM for daily usage?

Thanks
[ONE Android Development] Borsutkar:
Me too having problem...with dt2w and also the power button doesn't seems to wake the device from deepsleep....

And not even the incoming call...

Only way is reboot or connect a charger...

Any fix for this...

Todays build dirty flashed followed by supersu and wipe davlik and cache
[ONE Android Development] tsiftsism:
It seems that the only option for the moment is to stick with the kernel comes with the rom, until the devs update their kernels.
[ONE Android Development] hidea:
You mean between the two companies? Well… there's no official statement from the two companies as to how their relationship in the future will develop. However, if you look at CM's gerrit (review.cyanogenmod.org) there are still commits related to OPO being made. In my personal opinion, if CM's no longer planning to support the OPO, they'd stop making commits related to bacon on CM12; but after seeing that work is still being done, I'm inclined to say things are still looking positive. Also, CM did make the claim they will support the OnePlus One for at least 2 years (correct me if I am wrong); and breaking this promise is going to have serious repercussion on CM's brand & image.
[ONE Android Development] Borsutkar:
I confrim that proximity sensor is broken in todays build...

This prevents phone wakeup by any means like dt2w or power button if prevent accidental wakeuo is ticked under display settings...

Also, when we recieve a call the screen goes blank irrespectively whether proximity sensor is blocked or not...

Any solutions from experts is welcome..

---------- Post added at 05:51 PM ---------- Previous post was at 05:42 PM ----------

Have you disable pervent accidental wakeup under display setting...If so please try enabling this and try to wake up the phone from deep sleep...

Also, you can check by receiving any call.This give blank screen due to broken proximity sensor on todays build...

I may be wrong though...
[ONE Android Development] giaur:
Yes I have it disabled. There are no any problems, dt2w, wake power button, receive call, all ok.

There is no need to enable it, did you try to disable and see if it helps?
[ONE Android Development] Borsutkar:
Thanks for quick reply,

Just checked again dialing a call and it goes blank, until respondent disconnects the call

I will try flashing again...
[ONE Android Development] Spewmonic:
DT2W is somewhat broken on today's build.. I have to do it 4 times to get it to work properly.

If I flash boeffla's A10, my WiFi wouldn't work. I didn't try AK though.

Edit: Nvm, he just released A11. Let's see if that fixes the WiFi.
[ONE Android Development] Borsutkar:
just dirty flashed todays build again...

Now dt2w with accidental wakeup prevention works fine, but in call proximity is broken.

Screen wont turn blank on calls in proximity...
[ONE Android Development] giaur:
LOL gps is broken again. Freeze after fix, then disconnect from satellites and we need to wait for fix again. What a fault.... damn. It's introduced in today build, there is new gps config in changelog and they made things broken again
[ONE Android Development] andip71:
Update to Boeffla-Kernel alpha11 and WiFi will be working again, kernel has been updated a few minutes ago to latest cm code (incl. Wifi drivers)

Andi
[ONE Android Development] asafba:
the touch response dramatically improved in the last build! finally :)
[ONE Android Development] n2851991m:
in call proximity broken

Ok so I installed today's (01/03) build (dirty flashed) and yeah proximity sensor on call seems to be broken, like the screen turns off on call and never turns back on.

I accidentally discovered a workaround though, Press the power button which locks the phone and then double tap on the screen to wake it.

That or just enable power button to end call in Buttons ?

This is not a biggie but just something till tomorrows build ;)
[ONE Android Development] spyd4r:
good thing no one ever calls me :P
[ONE Android Development] giaur:
Actually screen should stay on during incoming call. However, I can't reproduce this problem. My test:

- wait fot screen off

- call my number from other phone

- wait for screen off on incoming connection

After press power butoon I can see incoming connection screen, so serms to be ok
[ONE Android Development] CptAwesomeTT:
I can confirm screen does not turn off when placed by ear during a call.
[ONE Android Development] filmaker:
Guess it's just me? Lol
[ONE Android Development] giaur:
Indeed, the same here
[ONE Android Development] Borsutkar:
That's what i am trying to tell...since long

Anyway...we have to live it till CM fux it..
[ONE Android Development] giaur:
So, actually it's not worth to flash today build. It introduces a few annoyin bugs:

- proximity sensonr does not work

- gps is broken. It can be reverted by hand if you wish, I already reported this to CM and got response from Steve Kondik (you can see comments for commit).

I suggest to stay with 01.02.2014 build until that issues are fixed, hope it will be soon
[ONE Android Development] flxvh:
next to the issues stated above, my accelerometer? does not work, so my screen does not rotate when tilting,...

or am i the only one with this issue?
[ONE Android Development] AcmE85:
Works here with stock kernel.
[ONE Android Development] keanyiap:
u mean 02.01.2015 build? haha
[ONE Android Development] fmc000:
GPS perfectly working here, less than two seconds for a fix and navigation with Nokia Here without issues. Can confirm the proximity big, though.
[ONE Android Development] fards:
Ok proximity sensor works with the opo alpha modem & nvbk ¡

Here's flashable zip with those..

Only for people knowing how to reverse this!

https://docs.google.com/file/d/0B1xWJTWr72ktUmxoMTJHbTdHWFU/edit?usp=docslist_api
[ONE Android Development] giaur:
As most people. you are unable to see issue. Because it freezes for 30 seconds after fix, then works fine. You don't have any chance to see it with nokia here because you don't start to move immediatelly after fix :) But problem exists, install GPS Test and watch what happens. Fix in 1 second, then freeze for 30 seconds. Then lost fix, and then get fix again and then all is ok. Don't tell us that issue doesn't exists because it's already confirmed by CM

It happens only after phone wake up from deep sleep. I reverted config changes made by CM team and issue is gone. It's baceause they changed config as it neede by new gps firmware, but new firmware is not merged yet (as far as I understand).

Look here: http://review.cyanogenmod.org/#/c/83511/
[ONE Android Development] tiny4579:
Steve pushed an updated GPS commit this morning. I had a fix in seconds and it seemed stable for over a minute using GPS test.
[ONE Android Development] giaur:
That config actually makes gps broken. You will get a fix then freeze for a 30 seconds. At least in my case. I was forced to revert config changes to deal with it. Most important - it happens only after deep sleep. If you used gps after phone wake up and you got a fix and then use gps test, all is ok.

[edit] Or it's already fixed after daleski75 released his build, I have no idea.
[ONE Android Development] tiny4579:
Steve's commit a few hours ago I think was basically a revert of the one that broke it. Hopefully later today proximity will be fixed. I think those were the main issues from the 1/3 build. New touchscreen firmware seems to be quicker in response.
[ONE Android Development] giaur:
Ok, so let's wait then. Perhaps you are right, it might be already fixed. I'm on daleski's build so I don't have latest commits.
[ONE Android Development] DrearierJester1:
Also have wifi issues here and proximity issue ... Using Ak kernel 74.
[ONE Android Development] tiny4579:
For wifi use stock kernel. The custom kernels may not have the driver updates yet.
[ONE Android Development] fards:
People are obviously ignoring this.

Please read

The alpha aosp modem fixes proximity on 03/01 build!
[ONE Android Development] giaur:
So there is nothing to fix at Cyanogen side?
[ONE Android Development] fards:
Not that i can see,

reading the commits they have new firmware, not huge stretch to presume this is the same fw:)
[ONE Android Development] fards:
Interesting. Proximity Sensor draw with 28/11 modern and non functional 11ma!

With newer modern and functioning

. 0.38ma
[ONE Android Development] tobitege:
[MENTION=265575]fards[/MENTION]: I'm sorry, but I don't understand your last post, what it means (11ma, .38ma)? :confused: Thanks for any clarification.
[ONE Android Development] MickyMax:
So the last build (CM12s) should now works fine with the alpha radio from opo?
[ONE Android Development] giaur:
If I understand it correctly, we now need the same modem that is used by official opo lollipop alfa build, right? And it's not compatible with cm11 and older cm12 builds
[ONE Android Development] fmc000:
Would you mind preparing also a revert zipfile, please?
[ONE Android Development] Yammertime:
Is there an issue with the proximity sensor in the 03/01 build?
[ONE Android Development] giaur:
I can confirm - flashing new modem resolved issue with proximity sensor on today build. Also we need to revert gps configuration changes, hopefully it wil be fixed in tommorow build (seems there are some fixes merged after today build made)
[ONE Android Development] fjsferreira:
How about rotation? I built temasek today and get no rotation whatsoever either :S
[ONE Android Development] jam90:
Rotation working fine here

---------- Post added at 08:17 PM ---------- Previous post was at 08:10 PM ----------

What's the problem with GPS?
[ONE Android Development] fmc000:
Just flashing the zipfile under TWRP?
[ONE Android Development] giaur:
It was discussed on previous page. Look here: http://review.cyanogenmod.org/#/c/83511/

Basically, if it's not problem for you to wait approx 40-50 seconds for usable gps, you should not care

---------- Post added at 08:37 PM ---------- Previous post was at 08:23 PM ----------

Yes
[ONE Android Development] Yammertime:
Clean flash? I don't think anyone else here has reported a bug with display rotation. Apparently, there's an issue with the proximity sensor and GPS (which takes longer to lock on). I'll just wait for tomorrow's build. I'm still using the 29/12 build without any issues, as far as I'm aware.
[ONE Android Development] johno4444:
Sorry but what modem should we be running now? And is there a zip file for it to flash. Thanks
[ONE Android Development] KeyperOS:
Excuse me but could you please tell me what the "static_nvbk.bin" is and where it goes? (how it's flashed).

Like how you'll "fastboot flash modem NON-HLOS.bin" for the modem.

Thanks!!!

EDIT:, ok, if I'm reading your installation script right it should be "fastboot flash oppostanvbk static_nvbk.bin", is that right? What does it do? Or is it another ColorOS leftover?
[ONE Android Development] giaur:
Yep, there is
[ONE Android Development] fards:
There's a revert file (28/11) for the modem in the modem thread.

Unless cm revert that proximity commit I'm sticking with the current.

It's much much more stable for me signal wise. Dt2w is quicker as well
[ONE Android Development] fards:
There are various programs for measuring the power consumption of every piece of software and hardware

This proximity sensor code only uses.0.38ma draw when used with the newer alpha modem.

The same code with the older modem is reporting as using 11ma of power. Which is quite a lot, especially for something that isn't working using the older modem.
[ONE Android Development] fards:
Don't think I've seen a fastboot method for it. Can dd it into the relevant /dev which is what the zip file does

. "/dev/block/platform/msm_sdcc.1/by-name/oppostanvbk"
[ONE Android Development] fards:
As long as fastboot recognises the partition it should be fine
[ONE Android Development] giaur:
Why should they revert while new stuff works better?
[ONE Android Development] fards:
Dunno. Someone asked for one
[ONE Android Development] giaur:
Because he did not know that he need to flash new modem, I guess
[ONE Android Development] fjsferreira:
The new modem makes dt2w very slow... even pressing the power button to wake the device is slow, anyone having this also?
[ONE Android Development] fards:
Nope the opposite here. Quickest is ever been. Are you using anything specific on

Lockscreen (pin pattern etc? I'm just using swipe)

I am about to clean flash the lot, because I've been Experimenting a little the past few days and have a very messy set up.
[ONE Android Development] giaur:
Nope, it's rather not related to modem. I had it before too, sometimes. Now it's fast even after updating baseband. I have no idea what causes this
[ONE Android Development] fards:
Can always get logs to check, something will show up
[ONE Android Development] fjsferreira:
That's very strange. Switching to cm11s modem returns dt2w to normal, but sensors break in today's build. Flashing the new baseband fixes sensors but makes waking up take 3 or 4 secs. Well, I'll build again tomorrow.

EDIT: after a reboot dt2w is normal again... Sorry for the confusion.
[ONE Android Development] tobitege:
Isn't dt2w also kernel related and may need extra commits? I think there are more puzzle pieces that need to interconnect.
[ONE Android Development] KeyperOS:
I concur, the latest modem works great with the latest build and dt2w takes a few hundred milliseconds, less than a second here. The modem also locked much faster than with the pre-03/01/15 build, it further shows that the latest build is meant for the latest firmwares.
[ONE Android Development] matase:
is there a mod that allows phone to be turned to silent (vibration disabled) using volume keys? I had one of the first CM12 builds before and it was annoying that you couldn't turn off vibration with volume keys.
[ONE Android Development] etoy:
edit: nvm,solved
[ONE Android Development] johno4444:
Hi, thanks. Can you post a link for it?cant see it in the main thread
[ONE Android Development] fards:
wonder if the http://review.cyanogenmod.org/#/c/83511/1/gps/izat.conf

line 128 is causing issues ?
[ONE Android Development] i4mt3hwin:
https://onedrive.live.com/?cid=CB008980D51C1072&id=CB008980D51C1072!11193&authkey=!ACiQCqa5IgoJbF4
[ONE Android Development] giaur:
Have no idea, I reverted all 3 files. But seems you have more fresh build, so tell if gps issue still exists?
[ONE Android Development] fards:
http://review.cyanogenmod.org/#/c/83732/ simples ! :)

tbh I was struggling to replicate the issue, playing with locus pro while out and about today I had a decent lock all the time, with no obvious issues.

Can see decent amount of info using that, no freezes noticed, even when staring at the gps info screen.
[ONE Android Development] cundiffr:
Which one of the two do you flash? Sorry I'm never really confused when it comes to flashing radios. Twrp or fastboot? Thanks in advance
[ONE Android Development] matase:
how do I change the DPI? I tried using texdroider dpi but DPI doesn't change after restart.
[ONE Android Development] jam90:
Is there a way to add a shortcut of cm profiles on the home? Widget "settings shortcut" doesn't have the profiles. Maybe with a thirdy app? It's so annoying to do the long way anytime
[ONE Android Development] giaur:
We'll see, I'm going to test as soon as daleski75 post new build.
[ONE Android Development] fards:
just use the zip I posted earlier today..

it's not difficult to look back through the thread is it?
[ONE Android Development] fards:
better to point people to the post from this thread with the zip in it.

http://xdaforums.com/showpost.php?p=57924760&postcount=4088

Less chance of 20x10^6 questions the same then :P
[ONE Android Development] giaur:
Edit build.prop with text editor.
[ONE Android Development] riki126:
Build 3/12 doesnt respond to proximity during call
[ONE Android Development] fjsferreira:
You have to flash the new modem. Some posts behind and you'll find it.
[ONE Android Development] andip71:
Mine is since today around 1pm CET already...

In this case no.

Dt2w is a feature that is implemented and working fine for a long time, so there are and were no changes to it in the past weeks.

Andi
[ONE Android Development] jmudrick:
Still working here.
[ONE Android Development] cundiffr:
It is pretty difficult ?
[ONE Android Development] futuro82:
Any answer for this question ?
[ONE Android Development] omvir:
[MENTION=265575]fards[/MENTION] hello!! I just wanna clear somethings up for myself and maybe others. The new alpha modem you speak of... Is it the one from the new alpha lollipop ROM released by OPO forums? And also, you say its working better for you compared to the current one in cm12 unofficial nightlies??
[ONE Android Development] AcmE85:
The cm12 unofficial nightlies do not come with an included modem.

You have to wait for official nightlies.

So basically you are using an cm11 modem.

Today's nightly 03/01 has an updated proximity sensor driver which

ends up not working with any modem other than the one provided by

OnePlus with their lollipop Alpha build.

So unless cm revert the sensor changes, which is unlikely,

you will need the new modem.

It will get updated nevertheless when official nightlies are out...

Personally I did not see any bad behavior with the new modem yet.
[ONE Android Development] omvir:
Thanks bro! Cleared it all up !