yashsingh1/xdaforums huggingface dataset:
[ONE Android Development] KeyperOS:
Guys sorry for getting a bit off topic but for those of you that flashed OnePlus' Alpha build you need to check what it actually flashes!

Besides the ROM (system + kernel) it also flashes a bunch of secondary partitions including but not limited to a new bootloader (Oppo instead of CM!!!), a new logo (red 1+ instead of white) and A NEW MODEM.

That last part about the phone not waking up after dt2w or pressing the power button mysteriously has to do with the modem. Now why the modem messes up the proximity sensor is beyond me mind you but there you have it. Also in my case it took considerably longer to get a signal and it also caused the modem (the hardware) to reboot once (not the rom/phone, just the modem).

So, in order to fix that you need to reflash at least the modem partition (NON-HLOS.bin) or, if you want to revert to full stock, all the bellow partitions back from 44s. This means:

fastboot flash modem NON-HLOS.bin
fastboot flash sbl1 sbl1.mbn
fastboot flash dbi sdi.mbn
fastboot flash aboot emmc_appsboot.mbn
fastboot flash rpm rpm.mbn
fastboot flash tz tz.mbn
fastboot flash LOGO logo.bin
fastboot reboot

Again, if you don't want to revert everything and just want your phone to wake up again after pressing "power" you only need to flash the modem from 44s, no wipes necessary and you can safely restore an earlier nandroid.

That means just run "fastboot flash modem NON-HLOS.bin" from within the (Oppo) bootloader.

Thank you for your time, you can now resume the talk on how awesome daleski75 is :D
[ONE Android Development] konigche:
If now I have a previous version of this ROM and want to upgrade, you need to wipe? Sorry for the English.
[ONE Android Development] counterfeit187:
Yes, i have had that all day on the 1/1 build.
[ONE Android Development] tobitege:
It's a bug introduced in CM code it seems and should be fixed with next build.
[ONE Android Development] solar_burn:
Anyone else getting wake issues? My phone won't wake from the power button nor double tap.
[ONE Android Development] highdiver_2000:
Anyone having problems using Wifi Tethering?

I could ping, but I could not the browser to work. or telnet to port 80.

weird
[ONE Android Development] tobitege:
Reflash the CM11S modem from the Modem Collection thread.
[ONE Android Development] solar_burn:
Fixed! Thanks! Wake is delayed though. Any fix for that?
[ONE Android Development] tobitege:
That could be due to the "Prevent accidental wakeup" option in Settings if it's on (I'm not on this rom currently, you might need to check).
[ONE Android Development] solar_burn:
Holy **** your Right! Thanks dude!
[ONE Android Development] AcmE85:
Don't worry it will fix itself eventually. Happened to me before and it was gone after some time...
[ONE Android Development] Norapapa:
OT:

I have three invitations for the OPO 64gb sandstone. If interested a PM to me.
[ONE Android Development] daleski75:
New build up guys
[ONE Android Development] Norapapa:
Works this build with PA full gapps?
[ONE Android Development] daleski75:
Yes
[ONE Android Development] 69gm:
Thanks for the heads up. Yeah I was one of those curious ones and I HATE that ROM! Really screwed up my phone, not even being able to get into TWRP anymore!

Anyway my question is on the bootloader...does that new one screw us up somehow? I previously had an unlocked bootloader...Did it get relocked somehow? Is there a way to check? Sorry for the noob questions...I am just mad that OPO gave us such a crappy ROM to try out and it migh've messed up my previously smooth running phone on THIS ROM. Argh!!! My apologies for being OT...

---------- Post added 2nd January 2015 at 12:00 AM ---------- Previous post was 1st January 2015 at 11:57 PM ----------

Thanks for this to get back to how things were before this hideous ROM from OPO. Sorry for the noob question but where do I find these files?
[ONE Android Development] daleski75:
Go into the boot loader and run fastboot OEM device-info that will tell you if the boot loader is locked etc.
[ONE Android Development] srgank:
Does the last build support the new camera api? To manual focus and so on.
[ONE Android Development] tobitege:
[MENTION=4151403]69gm[/MENTION]: you could also go with Bacon Root Toolkit (if using Win), which does all the steps as well for you (did it yesterday myself).
[ONE Android Development] giaur:
Nope. Don't expect it soon. Camera api is most buggy thing now, it does not even allow to record 4k with 3rd party apps, auto focus is totally brokon etc
[ONE Android Development] dsmpampis:
Hey guys I'm using the bpear-gapps-lp-20141122 with no issues at all but now I want to make a clean flash using the PA GApps. Which one should I flash? The Stock or the Full package?

Thanks in advance.

Tspatalked with my crispy Bacon!
[ONE Android Development] hidea:
Either package are great. The Google Stock Package has all the Google apps bundled in a typical Nexus phone; I'd flash this one if you want to get as close to a Nexus experience possible. The Google Stock package also removes AOSP apps that duplicates the Google Apps functionality (browser, Email, camera, etc.). I just go with this one most of the time.

The Full Package is nearly similar to the Google Stock Package, except it doesn't bundle nearly as many apps, and it does not remove any of the AOSP apps. You might be seeing doubles (AOSP browser, and then Chrome. What's the point, right?).

At least that's to my understanding.
[ONE Android Development] blackfire2802:
Hello guys, I have a problem..... Every time I try to apply the update it goes into bootloop until I flash the ROM again....can anyone please help? What should I do
[ONE Android Development] wq2020wdm:
I flashed 01/01 build, and when I swipe from home button to google, it shows Android system fc. Does the latest build fix that？
[ONE Android Development] freezer2000:
Systems FC that I was facing with 01/15 update has been resolved for me. So guess this holds true for others too wtih 02/15 build
[ONE Android Development] Yeasis:
Black screen?

Like 90% of the time when i turn off the screen, i can't seem to get it back. So pretty much this ROM is useless to anyone since i have to tap the screen every 10 second for it to not go into sleep mode and make me restart te device by pressing the power button for 10seconds. I didn't change anything in the settings, any suggetions?

edit:i didnt root the device, might that be the problem???
[ONE Android Development] cubeever:
Is the 02/15 Build stable enough to use it as a daily rom?
[ONE Android Development] hidea:
For those who had crashing issues (particularly Android System), this might be the culprit:

Indeed, it was an issue on 01/01/2015 but that's been patched. In case you're interested, this is the commit that fixed it: http://review.cyanogenmod.org/#/c/83403/

I flashed 02/1/2015 build, and the issue is gone. No more FC when a Default App Picker is called.
[ONE Android Development] giaur:
Of course, next time don't flash any mess from oneplus.net
[ONE Android Development] mik.caldentey:
There is a workaround about the screen issue, disabling ambient display on display preferences.

It works for me.
[ONE Android Development] jam90:
Guys do you have camera next working for build 01/02/2015? The one i have doesn't works anymore
[ONE Android Development] Blümchen Blau:
Fail boot after full shutdown

As even with a clean install (wiped System, Data, Cache, Dalvic) with todays image and Mini-GApps the AOSP keyboard wouldn't swipe I'll try it with the full Modular package.

BUT, the reason for flashing with full wipe is, that since days it happens that when I shut down and boot after some time I can't log into the mobile network. WiFi is up and running, but I am not asked to enter PIN and therefore cant connect mobile. For that reason, I assume, the launcher (NovaLauncher) shows only for a glimpse after boot and after unlocking the phone. I can solve this behaviour only by flashing a working backup. (Had that behaviour at any boot with yesterdays image. Since starting with "Stock UNOFFICIAL CM12 Builds I haven't flashed any other images.)

Hope to solve this with the new clean install. (So this 2nd part is just information to our well-thanked maintainer!;))

System with TWRP 2.8.3.0 and SuperSU 2.42

BB
[ONE Android Development] miragez:
Daleski75 thanks for building the 02012015,

Now my doubts was right it got to do with some nullpointer that was broken on 01012015 build.

Using your latest 02012015, everything is back to normal. Just heads for those, I do clean install, with ak v74 kernel and also pa-gapps..

Please dun keep asking what gapps is being used...
[ONE Android Development] giaur:
It works fine, no problems.
[ONE Android Development] jam90:
Can you post me the link where you downloaded camera next working?
[ONE Android Development] liviugreuu:
Hello a todos.

I wish you happy new year.

I install this final build. and I have a problem.

If you answer the phone and call you, put black screen and not reignite until the call closes. Like the proximity sensor does not work with this rom? or you can make it work better?

Thank You
[ONE Android Development] Norapapa:
Camera next auto focus do not work on the latest build for me. Google Kamera works fine
[ONE Android Development] giaur:
Yes you are right... you need to touch screen to focus... damn

---------- Post added at 02:10 PM ---------- Previous post was at 02:05 PM ----------

Actually, autofocus in camera next is working. But you need to set focus mode to continous picture
[ONE Android Development] jam90:
camera next, to me, give always force close! It never open
[ONE Android Development] giaur:
Try this: http://www.apkmirror.com/apk/cyanogenmod/cyanogen-camera/camera-2-0-004-5fa8c79c0b-30-apk/
[ONE Android Development] jam90:
neither this...always force close...can someone post me the file "camera.msm8974.so" from "/system/lib/hw" ?
[ONE Android Development] KeyperOS:
Again guys, read before flashing. The OnePlus thread states on the very first post pretty clearly:

As for the bootloader, apart from saying Oppo and having Ollie winking at me in Chinese, I didn't really have any issue so far. In fact I myself had the same problem with the screen not turning on and I flashed the 44s modem back using this latest bootloader and it flashed fine. However if you want to make sure then do as Daleski said, run the oem info command and if you'd prefer, flash back the old bootloader using the " fastboot flash aboot emmc_appsboot.mbn" command.

The 44s ROM can be found here: http://builds.cyngn.com/factory/bacon/cm-11.0-XNPH44S-bacon-signed-fastboot.zip Just extract the zip and all the images Daleski mentions are inside, as for the last command, it flashes the entire ROM itself for a second time (not sure why but there you have it).

Guys, do keep in mind that this is an Alpha release i.e. even less stable than the first bppear's builds. Only flash if you want to be a guinea pig and know how to get back from it. With CM royally screwing OnePlus they needed a new ROM and while they would get around to it eventually they had to hasten their plans. Issues are to be expected but the return is even more choices (unless CM screws them AGAIN and doesn't release CM12s as they said they would...)

@daleski75, maybe it'd be a good idea to put the whole modem/screen off thing on the first post, we've got more and more people complaining about it and the latest ones don't even bother to mention they flashed the OnePlus ROM and instead dish it on this one...
[ONE Android Development] kutulu32:
I try to install 2\1\2015 version to my opo with twrp 2.8.3.0 and after wipe when i start to install the rom twrp reboots. I tried mounting unmounting system cache and nothing happens. Any idea?
[ONE Android Development] KeyperOS:
The first things I'd do would be to save everything from the SD Card to the PC, redownload the rom in case of an error, reflash the sdcard partition from the 44s ROM (fastboot flash userdata userdata_64g.img for the 64Gigs OPO version), reflash TWRP and start again.

Obviously that'd erase everything hence the backup above.
[ONE Android Development] liviugreuu:
hi all

I put the last build, but call screen remains black. turns back only if close call. what can i do?
[ONE Android Development] miguepereira77:
Setting>Display>disable "prevent accidental wake-up"
[ONE Android Development] liviugreuu:
Yes, but I disabled , during the call remains black. like I'm holding the phone to your ear.
[ONE Android Development] tobitege:
Also disabled "Ambient display"?
[ONE Android Development] liviugreuu:
No. must be disabled?
[ONE Android Development] kutulu32:
Thanks a lot for your suggestions! I am lucky after restoring my 44s nandroid backup it installed ok after wipe.
[ONE Android Development] daleski75:
A fair bit is broken still ie cellular service not working, system ui crashing. so I won't be uploading this alpha but i will compile it when I can and if it becomes stable I will upload it.
[ONE Android Development] daleski75:
Cellular does not work but wifi seems to, systemui crashing, so not fit for use yet but I will compile when I can and if I am happy it's stable then I will upload PA as well and provide links.
[ONE Android Development] stizolo:
Wow! Smoothest build yet! I can confirm it works with MultiRom V29 (dual-booting) only mishap is trebuchet (force closing) but we can live without it for now... Keep Up the Awesome work!
[ONE Android Development] gianton:
[MENTION=1095206]daleski75[/MENTION] thanks for sharing mate!

DT2W and ambient display working great! Flashed it over K900's build no issues so far.
[ONE Android Development] gigashadow:
Yessss
[ONE Android Development] fmc000:
Sorry but what do you mean with this? No mobile data on this build?
[ONE Android Development] daleski75:
It's too broken right now but keep an eye on this thread.
[ONE Android Development] daleski75:
No mobile data and no service, heck no icon display for the signal.. nadda

Note this is only for the Paranoid Android 4.0 Alpha-1 NOT CM12 ;)
[ONE Android Development] Spewmonic:
Anyone flashed this ROM with boeffla's kernel? Wanna know if it works with DT2W and this ROM in general.
[ONE Android Development] fmc000:
Oh LOL I got confused by the partial quoting, sorry.

So, let me summarize: on this build:

* video recording bug is fixed;

* no contacts FC;

* no "close all" systemui FC;

* dialer still FC when displaying the complete call history;

* (other bugs maybe ...)

I'd really like to test it in the weekend. Many thanks for your work :good:
[ONE Android Development] capitanouncino:
Is it possible dirty flash over k900 build?
[ONE Android Development] daleski75:
Yes others have and it seems to be ok.
[ONE Android Development] daleski75:
Note to self..

DO NOT repair permissions on TWRP it kind of breaks CM12 :(
[ONE Android Development] duquesa:
I've just finished a clean install and don't have any of the above problems, everything works very smooth, lets see how the battery goes through the day.
[ONE Android Development] fmc000:
That's great! Thank you very much.
[ONE Android Development] poczynek:
Anyone's ambient display working intermittently?
[ONE Android Development] daleski75:
Mine seems to be perfect done a fair bit of testing with it using pushbullet.
[ONE Android Development] DespairFactor:
Mine doesn't seem to be working, but I dirty flashed and don't use it anyways since I have a moto 360:)
[ONE Android Development] capitanouncino:
"Big" problem...hardware buttons stay ON even with screen off
[ONE Android Development] freezer2000:
+1
[ONE Android Development] jcespi2005:
Thanks for tour work...

Can you make your build compatible with multirom? Should be nice to test it...

Sent from my OnePlus One ;)
[ONE Android Development] dsmpampis:
No sounds at all, only notifications and ringtone.

I don't know what it's going on maybe it's related to AK kernel?

Tapatalked with my crispy Bacon!
[ONE Android Development] sebfar:
Protected folder too

Envoyé de mon A0001 en utilisant Tapatalk
[ONE Android Development] daleski75:
Try the stock kernel if possible just to rule out AK.
[ONE Android Development] poczynek:
Whenever I dirty flash Google search force closes!
[ONE Android Development] daleski75:
Which gapps are you using?
[ONE Android Development] daleski75:
I think they are adding different ways of waking up and sleeping the screen and made a mistake it's double tap to sleep the screen not wake so will amend now.
[ONE Android Development] poczynek:
I've tried three different ones. Strangest thing. It just will not work. Tried restoring from tibu but no go. Will clean flash I guess but was hoping for dirty flash!
[ONE Android Development] daleski75:
That is strange I use bpears 20141118 gapps and then I created a zip with tibu of all my apps and restore them that way which seems to work well.
[ONE Android Development] dsmpampis:
It's not a kernel issue... ?!

Do you still have the same issue?

Tapatalked with my crispy Bacon!
[ONE Android Development] daleski75:
Sorry unless cm add support for it then it won't be done.
[ONE Android Development] dsmpampis:
Try PA gapps!

Tapatalked with my crispy Bacon!
[ONE Android Development] daleski75:
Mine seems to be OK can play music videos etc and all OK and notifications now work fine although a bit quiet for my liking
[ONE Android Development] poczynek:
Will do! Link?
[ONE Android Development] daleski75:
PA gapps is weird sometimes it says an error saying you must already have PA gapps installed to use it.

And not sure if you know bpears 20141121 gapps had the same issue.
[ONE Android Development] acuicultor:
Running 21/11/2014 build in secundary flawesly

Sent from my Crispy Bacon
[ONE Android Development] dsmpampis:
The notifications sounds and ringtone are working only the music sounds (YouTube, keyboard etc) are not working.

http://xdaforums.com/showthread.php?t=2397942

I'm using only PA gapps with no issues at.....

Yes I know bpears but I choose PAs....

Tapatalked with my crispy Bacon!
[ONE Android Development] jcespi2005:
Seems 21 versión works as posted another user...

Perhaps some of the changes between 21 and 22 versions broke multirom support... just saying...

Sent from my OnePlus One ;)
[ONE Android Development] miv_3180:
On every single thread about CM12 I've read devs say NOT TO DIRTY FLASH cause crashes. It's useless to comment your troubles if you dirty flash. Clean install and you'll see most of your problems are gone. Dirty flash on lollipop it's an issue. Another thing try stock kernel ffs. If yiu're flashing a ROM that works and than flashing a experimental kernel you would never know where the problems come from. Try all the features on stock kernel than if you're not happy with it can try a custom kernel. No offense, just my thoughts.
[ONE Android Development] aznracer62:
The dev in this thread confirmed that dirty flashing is ok. I've been dirty flashing and everything is working fine for me. If something does force close, that's when I wipe everything. Do your own reading before you bash someone else.
[ONE Android Development] jam90:
up
[ONE Android Development] Beaster:
Guys i know this was answered before but i am still having the hardware button backlight issue.. Changing timout doesnt help.. If i lock the screen with double tap the backlights stay open.

Any fix? Thx!
[ONE Android Development] Borsutkar:
Just reuploading camera.msm8974.so

https://www.dropbox.com/s/m0zyqhk50l05mvo/camera.msm8974.so-custom.zip?dl=0

https://www.dropbox.com/s/amuq2lq1i1og2e4/camera.msm8974.so?dl=0

Credits to original uploader...
[ONE Android Development] fmc000:
Still FC with launcher 3 or any other launcher moving from the drawer back to the home screen if it the home app was selected "just once" instead of "always".
[ONE Android Development] doublem75:
I should first flash this and camera apk next?
[ONE Android Development] Borsutkar:
This is been uploaded by someone as a solution for panaroma not working in cameranext app...

Just flash the zip, should fix cameranext I guess...

Someone with knowledge can guide you better
[ONE Android Development] doublem75:
I flashed this zip and all my cameras apk don't work
[ONE Android Development] Borsutkar:
This is original camera.msm8974.so from todays build..just replace with any root browser and give proper permission..

https://www.dropbox.com/s/4yy92hc441kp5cs/camera.msm8974.so?dl=0
[ONE Android Development] Borsutkar:
Refer this for permission..
[ONE Android Development] doublem75:
Can I just reflash the rom?
[ONE Android Development] Borsutkar:
That is anytime better...
[ONE Android Development] Nagasaky2x:
Using here build from today and works flawlessly too, no more FC when app picker shows neither any problems with camera next.
[ONE Android Development] andip71:
Deleted.
[ONE Android Development] AcmE85:
More opo goodness is being merged right now...

New WiFi driver, GPS configuration...
[ONE Android Development] gadget069:
Maybe I'll wait to flash lol.
[ONE Android Development] fards:
hmmm http://review.cyanogenmod.org/#/c/83272/1/msm8974.mk

PRODUCT_PROPERTY_OVERRIDES += \
+ ro.qti.sensors.ir_proximity=true
[ONE Android Development] AcmE85:
A wild guess could be that this commit fixes the screen-off on incoming calls when

the proximity sensor is covered.
[ONE Android Development] fards:
looking for the supporting code now..

enabled it in build.prop on the 02/01/ build and wake up is a bit snappier on d2tw, but that could be placebo as I can't be arsed to test it properly :D

doesn't fix the alpha/find7 modems killing the sensor readout though.
[ONE Android Development] fards:
Only thing I can see is the wifi proximity code.
[ONE Android Development] AcmE85:
OK thanks.

Great, they merged an updated touch panel firmware for cm12!
[ONE Android Development] omvir:
Seems like we might soon see a nightly, judging from gerrit.
[ONE Android Development] tiny4579:
Hmm. With the proximity commit, my proximity doesn't seem to work in calls. Need to try with a clean build.
[ONE Android Development] BoboBrazil:
Sweet, been waiting for official nightlies before jumping into Lollipop.
[ONE Android Development] omvir:
I'm totally just guessing here. I just have a feeling.
[ONE Android Development] BoboBrazil:
I'm actually surprised it's taken this long. 2 months is a long time for cyanogen.:D I wonder if the official update for one plus coming this month will be L or still 4.4.4?
[ONE Android Development] fards:
they are pushing commits to 4.4 "ready for ota" so I guess that means another 11s.
[ONE Android Development] :
[MENTION=1685515]BoboBrazil[/MENTION]

What official update?
[ONE Android Development] omvir:
Probably one last polished up 4.4.4. We still have until the end of January(they promised us 3 months) before we see an official CM12s. But hopefully nightlies soon!!!!
[ONE Android Development] BoboBrazil:
Ah, I figured so, but I was holding out some hope. Apparently according to One Plus there will be some surprises in this OTA.

Cyanogen will release a rom update for 11S sometime this month according to One Plus.

Yeah, it seems like they are a little behind schedule unless the update for January is Lollipop.
[ONE Android Development] spyd4r:
i'll hold my breath now for an official january CM12S release.

side note, weren't official dailies supposed to be a thing for CM12 by now according to the schedule?
[ONE Android Development] techeretic:
I built using these the latest commits.... Running quite good here....
[ONE Android Development] spyd4r:
is there a way to have the new Google Calendar from the Play Store overwrite the existing AOSP Calendar? I had to disable notifications in the AOSP one as I was getting double notifications.
[ONE Android Development] wq2020wdm:
Install PA stock gapps
[ONE Android Development] spyd4r:
I did, i used pa_gapps-stock-5.0.1-BETA5-20141225-signed.zip
[ONE Android Development] filmaker:
Is it just me or is the camera quality on CM12 atrocious? I could not get any good shots, especially with HDR on.
[ONE Android Development] wq2020wdm:
Strange. My Google calendar replaced the aosp calendar with pa stock gapps.
[ONE Android Development] miragez:
Are you coming from a clean install or dirty flash ? If it's dirty flash, have you tried clean install, I am using nova launcher without any issues after build 02/01/2015.