yashsingh1/xdaforums huggingface dataset:
[ONE General] waterdaan:
[MENTION=4842497]MMWolverine[/MENTION] fyi

The cm12 firmware from cm12 19-03 and 20-03 isn't working correctly on cm12

Latest would be from 18-03

See http://xdaforums.com/oneplus-one/general/rom-cyanogenmod-12-oneplus-one-t2994967 thread
[ONE General] MMWolverine:
What about firmware from 09-02, should be the same as 18-03. I left older version intentionally available, should problems appear and we had to revert. Anyway, I'll check on this tomorrow.
[ONE General] MMWolverine:
Update

Ok guys, I added the new firmware from today 21-03, seems cm made changes again, static_nvbk.bin is back to 0b, etc.

I also made the proximity sensor fix in such a way, that it creates a backup of original sensors.msm8974.so, installs the older version and keeps it when dirty flashing a rom. To remove this and revert back I added another zip in the 2nd post (or you can delete 10-KeepSensorFix.sh from /system/addon.d and reflash the rom). I've tested with latest CM12 nightly, CyanideL 03-16-2015 and Temasek-Sm v9.0, all working fine. But when re-flashing Resurrection Remix, addon.d script won't stick, so for now you have to reflash cm12_fix_proximity_sensor.zip on that rom.

Please let me know if you encounter any issues. :fingers-crossed:
[ONE General] smint86:
I'm not using MultiRom but am obviously interested in keeping my device as up-to-date as possible. That's including latest firmware as well.

My ROM is Temasek by [MENTION=3814731]katinatez[/MENTION], currently I'm using v8.8 linaro while beeing on 02/09 firmware (from here). I don't have and never had any problems with my proximity sensor.

I'm now looking forward to flash the latest Temasek version (currently v9.1 linaro, maybe I'm skipping this, as there seem to be problems with camera atm). I'm wondering, which firmware I should flash or if I should flash a "new" one at all.

There is 02/26 by [MENTION=3814731]katinatez[/MENTION] and obv the 03/21 by [MENTION=4842497]MMWolverine[/MENTION] in OP. Then the mysterious "proximity fix", which would have to be flashed on top of every ROM update, which I never needed before. As most of the users in this thread seem to use MultiRom, I'm wondering what I should do now. Maybe somebody could help out. These are my scenarios:

a) Flash new ROM without changing anything.

b) Flash 02/26 firmware and ROM on top.

c) Flash 03/21 firmware and ROM on top.

d) Flash 03/21 firmware and ROM on top, then adding proximity fix (have to to this after every ROM update).

For me, c) sounds best, but I really don't know about this proximity thing and if it's mandatory, as I never needed it before.

/edit

I compared the different firmware versions with md5sum, finding out that the 02/26 doesn't differ from the 02/09 at all (not from yours and not from the one I flashed, linked above). All files are the same. The difference your 03/21 makes are sbl1.mbn, rpm.mbn and emmc_appsboot.mbn. The rest of the files is the same in the four firmware versions I compared.

You can check the comparison here: http://pastebin.com/VhS0a5y3

I compared:

a) 02/09/15 by MMWolferine

b) 02/09/15 v2

c) 02/26/15 by katinatez

d) 03/21/15 by MMWolferine

a), b) and c) are the same, while d) differs in the three above mentioned files. So, it would be nice to know what these files change and if they make flashing proximity fix mandatory while running an up-to-date CM12 nightly based ROM (without using MultiRom).
[ONE General] MMWolverine:
You explained everything correctly and I will just confirm. Firmwares from 02/09 and 02/26 are the same, that's why I haven't released any links for 02/26. Version from yesterday differs only in those 3 files, I will check today's asap.

So if you plan on staying with Temasek you can flash 03/21 firmware or leave it as is - 02/09. There should be no issues with either. To stay updated with firmwares, you can first flash CM12 nightly and then your prefered Lollipop rom right over. However, Cyanogen doesn't update fw nightly, as apparent from the timespan between releases.

The proximity sensor fix is for when you use MultiROM, running CM11 and CM12 side-by-side. You can install my new flash-survivable version only once on Lollipop roms.
[ONE General] pSyCh¤_O_O:
[MENTION=4842497]MMWolverine[/MENTION]

Thanks for this...really helpfull..subscribed ;)
[ONE General] demon507:
U mean If i use only cm12 roms in multirom then there is no need to flash proximity sensor fix with the 03/21 firmware update?
[ONE General] MMWolverine:
Correct.
[ONE General] mikedcarr:
Unchecking the box didn't fix your issue - it only worked around the fact that your proximity sensor is not working. If the screen will not come back on by pressing the power button, it means that your proximity sensor is not working and is permanently reporting that something is in close proximity to the sensor (i.e. it thinks the phone is still in your pocket).
[ONE General] Kshishiu:
Thank You soooooooooo much... I loved it <3 Keep up great work :P
[ONE General] ricardowec:
Greetings [MENTION=4842497]MMWolverine[/MENTION] and everyone in the thread.

I just jumped In. I am new to the OPO and after doing all the initial chores (root, etc.) I am on the current BlissPop and Boffla builds. No big hassle; the device is working fine but want to move ahead with MR as I have done with several other devices Ive owned.

Now, I am bit confused with this modem and proximity sensor fixes. As I understand, by initial flashing the FW Update and thereafter, the proximity sensor fix, I am current as to this matters... but what about another 5.0.2 Rom as secnondary (eg: SlimLP). As I dont want to use KK in this deviece, I understand I have to follow the same steps in MR Advanced.. am I correct?.. Also,, where can I find your flash-survivable p.s. fix?.

Thanks for your help.

Cheers.

Edit: I found the Flash-survivable p.s. fix. I ghather is the one in the OP. Thanks
[ONE General] MMWolverine:
Hi,

if you don't plan on using kitkat with MultiRom, then there is no need to flash proximity sensor fix. CM12 firmwares from 02/09 and 03/21 both work fine even for lollipop roms in MR.

My fix should only be used when you have cm11 + cm12, cm12 firmware is required to boot lollipop roms and CM11s modem to boot kitkat roms on never kernels. But the latter breaks proximity sensor on CM12 roms, which is where p.s. fix comes in.

Flash-survivable zip can be downloaded from AndroidFileFost or Dev-Host, links in the 2nd post.
[ONE General] mephobic:
Thanks so much for this thread [MENTION=4842497]MMWolverine[/MENTION] !!
[ONE General] slebit:
Awesome work!
[ONE General] davidnewton:
Cannot connect to network after disconnecting VPN

Thanks a lot for this great instruction. I am using Mahdi Rom as primary and Euphoria as secondary following the instruction here. It works very well except one issue: on the secondary ROM (CM12 based), if I use VPN and then disconnect the VPN, then, the phone can not connect to wifi and mobile network anymore, and must be re-booted to get connection again. If I don't use VPN, or don't disconnect VPN, then, everything is fine. Please advise if there is a way to fix it. I am using CM11S modem with CM12 firmware and flashed the proximity fix on the secondar ROM. Thanks in advance.
[ONE General] Babyhustle:
1) Can the CM12 firmware be used in any Lollipop ROM? (i.e SlimLP)

2) Can the Lollipop ROM use the CM11 radio?

Your help is much appreciated :)
[ONE General] MMWolverine:
Sorry mate, I tried to replicate your issue, but for me vpn toggling works ok. Were there any reports on Euphoria thread? Which fw did you flash, 02/09 or 03/21? Maybe try full wiping or clean installing secondary.
[ONE General] MMWolverine:
1) Yes

2) Yes, accompanied by the proximity sensor fix
[ONE General] störte:
Just found your thread. Great work. Just one Question . If i use an unofficial Omnirom Android 5.1 i need to have 11s Modem in order to have sensors working.

If i use the CM12 firmware plus the sensor fix will the problem on Omni ? What do you think?
[ONE General] MMWolverine:
Yeah, I've just been reading the Omni forum. Does the screen stay on during calls? In that case you can try my fix, it should create a backup of the sensor blob and you'll find a restore zip in 2nd post. But since cm & omni are different in many aspects, cm blob might even make it worse.

I have no way to test this atm, so please report back.
[ONE General] davidnewton:
Thanks a lot for your reply. I am using 03/21 firmware. Sorry I did not mention that the VPN is not the build-in VPN, but two third-party VPN apps using SOCK5 proxy. The connection problem is not consistent either, sometimes, it works ok, sometimes, it has that problem. If I use the CM12 modem, then, there is no such problem. Hard to figure out what is wrong, it might be VPN app. Anyway, it is not a big issue since I usually keep the VPN app running all the time. Thanks anyway.
[ONE General] störte:
Tried it but die not help . needs the 11s modem.

Send by Hyperdrive on one+One
[ONE General] NickosD:
So If I want to flash ak kernel to a cm11s rom, I hav to flash the cm12 firmware and cm11s modem?

Sent from my bacon!!!!!
[ONE General] MMWolverine:
Yes, I have this configuration since ak v0.90 and it works great.
[ONE General] NickosD:
Great thanks.

Sent from my bacon!!!!!
[ONE General] nicesoni_ash:
I have a question guys..

I have CrDroid (CM11) on my opo, just to be clear what proper steps I need to take if I want to flash CM12 (Temasek unofficial) as a secondary rom?

Thanks for your inputs.
[ONE General] MMWolverine:
You start by creating a nandroid backup of CrDroid rom.

Then flash CM12 firmware (21.03.2015) and CM11s modem only (links in the 2nd post).

Then install MultiROM Manager app and flash MultiROM v32f, Recovery 2015-03-29 and 4.4.x Kernel

Finally in TWRP Recovery go into Advanced - MultiROM, add new rom Temasek CM12, go back & select the rom, from Manage ROM menu flash zip for Gapps and Proximity sensor fix (2nd post).

Choose which rom to boot from the MR menu after 1+ logo and that's it.
[ONE General] Firik:
So just a heads up and this could be beneficial to the few who are having this problem. A very limited amount of people who are using the OnePlus One have this issue with flashing any lollipop rom and getting either delayed calls/text or no calls or text. It was a known bug but no one could get it to work even after flashing the firmware/modem from CM12. This guide for updating the firmware has fixed the issue! Thank you!
[ONE General] sam razzy:
I always have a wakelock using any lollipop version with lollipop alpha modem radio. So I think this trick will solve the problem. Before I had tried this but always end with proximity sensor broken..
[ONE General] MMWolverine:
I'm glad my guide helps solve different problems on the side. :D
[ONE General] sam razzy:
Yes. This solves the wake lock problem.
[ONE General] MMWolverine:
Off-topic, I have two invites to share...

https://account.oneplus.net/invite/claim/GLXY-N0JC-9NIB-DZHO

https://account.oneplus.net/invite/claim/GLIJ-IGXV-O4TC-ABDK
[ONE General] zurden:
Thanks! I have issue with WiFi connection, hopes it will Fixed with your guide. Cm12 firmware + cm11s modem + proximity

Or modem it is just for the calls signal?
[ONE General] soorajnambala:
.. please help..

excuse me for being soo dumb... im runnig miui on opo.. i want to try cm12 as my secondary .. is this the same method ive to follow ??

hope ull reply .. thanks in advance...
[ONE General] MMWolverine:
Wifi drivers are in the kernel. On older phones baseband used to control wifi, bluetooth & gps along with cellular network, but on newer it's the kernel and the wlan drivers.

Yes, it should be the same. I only tested miui as secondary, but had cm12 firmware + cm11s modem and it worked fine.
[ONE General] soorajnambala:
thanks man...

thanks bro.. ill try.. :D:good:
[ONE General] zurden:
OK, so I need to find a kernel that keep me away of the WiFi issue I have.

Since the beginning of lollipop Roms I'm having "authentication problem" connecting to saved networks,not happening to me in kit kat Roms.

Thanks
[ONE General] MMWolverine:
Well if I recall correctly, there were some kernel commits specially for Spain. AK & Boeffla both have them and so should other kernels. I'm not sure if this fixes "authentication" or just drop-outs. But still I cannot share my experience, because I never had such issues.

Now some information on the OxygenOS release. It comes with new firmware/radio and you can flash it normally as primary rom. However, with multirom as secondary you need to be careful. I was only testing with CM11s and here are my conclusions:

1. OxygenOS does not boot as secondary

2. you have to swap primary & secondary, both roms will boot

3. cellular network on CM11s as secondary is broken (possibly because of reserve4.img)

4. flashing cm12 firmware or cm11s radio does not help

4. I restored by swapping again and restoring full nandroid backup (with persist and all)

For now I will wait on CM12S, but whatever you do, make sure you have a FULL nandroid backup.
[ONE General] sam razzy:
So MMWolverine, now oxygen Os got released. Do you have plan to give us the modem to download? Please if someone can then please give us just the modem file to flash.
[ONE General] MMWolverine:
Ok, here is OxygenOS modem (radio): download

Please remember, if you have KitKat + Lollipop multirom combination, using this modem with new firmware/kernels will result to broken proximity sensor (or even bootloops) on KitKat. Lollipop is ok.
[ONE General] DrNinjaa:
[MENTION=4842497]MMWolverine[/MENTION] I need to hug you to express my Thanks... U r a saviour, I have have been searching all over oneplus one forums to gather the firmwares and the radios to use but when i saw that, You even update the available firmwares to flash to switch between kk and lp... i turn tear eyed... thanks Buddy,

I'll reroute my xda friends to this thread who are wandering around to find the solutions about the switch of android versions. :thumbup::thumbup:
[ONE General] pSyCh¤_O_O:
I definitely get better reception with new modem.(In South of Spain). Before I couldn't stream TuneIn Radio with 3G from my living room couch (I live up in the mountains) and now it streams without a problem.

Awesome![emoji106] Thanks again MMWolverine
[ONE General] KritikSS:
So when you take the multi-rom variation out of the mix, it goes:

cm12 FW

CM11 modem

CM12 rom

Gapps

Sensor fix

is that the correct sequence?
[ONE General] MMWolverine:
Whether you flash Gapps before or after Sensor fix doesn't really matter as long as you flash both after the CM12 rom. So your order is correct. If you are referring only to Firik's post on delayed calls/text etc., then maybe try the Oxygen modem first. Users report it gives stronger/better reception.
[ONE General] fburgos:
If I'm on cm11s on primary and want to try cm12.1 on secondary

can I just flash secondary cm12.1 and sensors fix[\strike]

Nevermind I just followed the guide and cn12.1 works "fine"

If I restore the cm11s cwm backup, will the proximity sensor in cm11 go back to normal during call?

Right now in cm11 it don't work but I don't have black screen that prevents me to finish he call, screen just stays "on" this is normal right?
[ONE General] KritikSS:
I'm actually having a host of issues. Delayed texts once in two days since original flash. And when calling or having an incoming call, com.android.incallui is fc. On top of that, BT is generating a distortion on calls, but not on music playback. Figured it couldn't hurt to try this. So far no incallui fc, so I got that going for me. Is BT modem based?
[ONE General] Firik:
So the order I did it in was

CM12 Rom

Gapps

Clear Dalvik

CM12 Firmware

CM11S Modem

Then proximity fix.
[ONE General] MMWolverine:
Bluetooth is managed on the kernel's/rom's side.
[ONE General] Genericxx:
I've runned the 21.03.2015 for over a week with different CM12 and CM12.1 based roms. It turns out that it makes touchscreen sometimes sluggish for me, up to a point, where i am nearly not able to touch anything and have to reboot. First i've thought that this is because of the unofficial CM12.1 builds and maybe some bugs, but after downgrading to CM12 that problem persists. Using 09.02.2015 with new OxygenOS-Modem since yesterday with CM12.1 and the problems with touch went away.
[ONE General] Jole7:
Thank you my friend for those useful infos. I 'm on the same firmware as you are and no problems here as well.
[ONE General] rahulrai:
Hi I am just posting 2 issues on my opo. If u can help me out that will be great.

1) I am on blisspop and on installing the rom everything is fine, but after I install all my apps I get voice cracking only in outgoing call. Incoming call is fine. Its only on this rom. On both clean & dirty flash i have this problem. I know it's a problem of some app but I am not able to find the culprit. Can u help me on this?

2) After rooting & unlocking the bootloader I am having a strange issue. Whenever I keep my phone in my pocket with the proximity sensor covered or if I keep the phone facing down for more than 5mins the touchscreen hardly responds & 95% of the time It needs a reboot to get back to normal. i have already sent a request to OPO customer care but no response. Do you think it's a hardware problem or software issue?

If u can help then it woud be gr88. If not no problems.
[ONE General] MMWolverine:
Hello, ruhalrai!

I answered you in MultiROM forum. Tell me, did you remove my proximity sensor fix and does screen during calls work ok now?

Regarding 1st question maybe try eliminating apps one-by-one to find the problematic one, either by installing or removing them. If I had to guess possibilities could be call recording apps (I had problems with them before), or maybe sound enhancers (apps or scripts). Although if only on outgoing calls its really hard to say.

2nd question: I don't think it's a hardware issue, maybe check your kernel settings. Are you using stock Bliss kernel or any custom?

To me both issues seem rom related, but I'm sure you already asked on BlissPop forum. I haven't used this rom for some time.
[ONE General] msbusybee:
Hello! I just tried it on my OPO on my single rom:

- Blisspop V3.1 version 5.1 (2015-12-04 build)

- Boeffla Kernal 4.0 beta 4 for CM 12.1

I turned on my proximity sensor and made a call to myself. IT WORKS! HUZZAH! I wanted to say thank you very much for this thread. It was immensely helpful to me. I was able to follow your instructions and achieve the desired result. Big kudos to you, MMWolverine!
[ONE General] sam razzy:
Did cm12s came with new modem or old alpha modem ?
[ONE General] n30wav3:
Works fine for me on Multirom. You need to follow the same procedure as oxygen os to boot cos12 as secondary.

If you are on cm11 on primary, you need to flash the latest cm12 firmware and then cm11 modem on primary. Then you can flash the proximity fix on secondary cos12.

If you have cm12 or any 5.0 on primary then just flash the latest firmware on primary and cos12 should work fine on secondary. Working fine for me since last 12 hours
[ONE General] MMWolverine:
Same as cm12 nightly, see here: http://pastebin.com/EYMk3WCd

I will replace cm12 03-21 firmware with this asap.
[ONE General] NoFrown:
Can someone help me?

Current Setup:

CM11s Primary, Oxygen OS secondary.

I want to switch from 11S to COS12 as primary.

How should I do this?

Really don't know what to do...:(
[ONE General] MMWolverine:
You can flash CM12s, but make a full wipe first. That means you'll have to re-install multirom. What would probably also work is to flash CM12s as secondary and then swap with primary (but doing that you'll need to flash CM12s modem-firmware on primary).
[ONE General] NoFrown:
I flashed it as secondary and switched to primary.

Im running COS12 now, but unfortunately no multirom.

What kernel should i use. i want cm12s primary and oxygen secondary, no more 11s
[ONE General] MMWolverine:
Oh yeah, I forgot about the kernel. Ftm I have still stock, but will soon use AK v.141 or test v.210. Just flash that kernel in recovery on primary and inject multirom/boot.img after. Multirom will show. You can delete CM11s from secondary roms list in twrp or from the MR app.
[ONE General] NoFrown:
Flash kernel and inject boot.img?

can't I just install a kernel from the multirom app?

Can you give me more details please, I'm new in the multirom business :D
[ONE General] MMWolverine:
Sorry I ment "current boot sector", see screens below. I always tell ppl to do that, because sometimes when going back to stock kernel and then flashing ak MR menu won't show. You can flash ak from the MR app, but I'm not sure which versions are in there. You could also use Boeffla once he updates the 12s ramdisk, or any other cm12 based kernel that has the kexec patch.
[ONE General] NoFrown:
Do I have to flash AK kernel, i would like to stay as close to stock as possible, or does it have better batterylife?

What kernel do I need to flash when I want to get multirom but keep stock?

URL please :)

Many thanks for your help

EDIT:

I'm still not sure what to do :(

Do I have to flash a new kernel and afterwards select inject cur.boot?
[ONE General] DrNinjaa:
Watch the video once and U'll have very limited number of questions to ask

http://m.youtube.com/watch?v=x277XiToTWY

#HappyFlashing#
[ONE General] MMWolverine:
Here is Boeffla Kernel for CM12s, that's as stock as it gets: http://boeffla.df-kunde.de/bacon/boeffla-kernel-cms/cm12.0s_download/Test/Series 3.x/

Please read original thread here: http://xdaforums.com/oneplus-one/or...effla-kernel-1-0-2-0-beta-09-t2899974/page403
[ONE General] NoFrown:
I watched the video, but i still dont quite het it.

When installing multirom on cm11s i just pressed install kernel and it worked.

What option should i pick here? Or just flash ak kernel?
[ONE General] MMWolverine:
Well obviously you have to select 5.0.x version. :D When you reboot you can check the ak kernel version in system settings.
[ONE General] NoFrown:
I tried the 5.0.x version but in TWRP it said failed.

What should I do now?

EDIT:

Manually flashing the zip downloaded in multirom fixed the problem, thanks for everybody's help!! XDA is a great community :D
[ONE General] fburgos:
Tried cm12s and AK 211 kernel but my screen looked washed out, have to disable sunlight enhancement to fix the color
[ONE General] MMWolverine:
Yes same here. I mentioned this on ak forum, hopefully dev will sort it out in 212, at least he posted a screen with the new build on cm12s. ;)
[ONE General] abhimanyu bajaj:
Euphoria rom

im running carbon rom as primary and i want to install euphoria (lp) as secondary.... should i flash the cm12 modem files or what?
[ONE General] nicesoni_ash:
Hi mate, I have couple of questions about this post of yours.

Now Oxygen OS is here so can I flash OxygenOS_modem in place of CM11 modem if I have CM11 as primary rom and want to have lollipop as secondary rom.

Also what happened to CM12 firmware (21.03.2015) earlier available here?
[ONE General] MMWolverine:
You still need CM11 modem on CM11 rom, otherwise your proximity sensor will break. You could try using Oxygen modem on OxygenOS as secondary, MultiROM recovery has this option now. I tested this combination before, but still needed proximity sensor fix on Oxygen.

I replaced CM12 firmware (14.4.) with CM12S fw, as they are exactly the same. http://pastebin.com/EYMk3WCd Only difference between 21.3. and 14.4. was logo.bin.
[ONE General] iRushaad:
thanks :)