yashsingh1/xdaforums huggingface dataset:
[ONE General] kendallgreen:
I was using cm 12.0YBG1TAS213-bacon.signed.zip I was flashing cm12.1 20150807-NIGHTLY-bacon.zip. TWRP was baconhwd.img. I downloaded the 12.0 YNG1TAS -bacon-signed-fastboot.zip. Unziped it and fastbooted all of the files into my OPO. I then had to reinstall everything including TWRP 2.8.7, UPDATE-superuser.
[ONE General] nsmart:
I would use offical twrp 2.8.7.0, not baconhwd.img as there were several upgrades to unoffical twrp for bacon with the same filename. Maybe you got an old revision of baconhwd.img that could not handle decryption of oxygenos (see here for details). Or you can try to flash recovery from stock rom with fastboot and redo the full wipe with stock recovery.
[ONE General] Ok_Kaleidoscope5109:
Thanks for the instructions. Now any good text editor with line #s you recommend? Something like Notepad++ for Android?

---------- Post added at 12:07 PM ---------- Previous post was at 11:56 AM ----------

If you're updating from a CyanogenOS to CM12.1 I honestly would do a full wipe.
[ONE General] Coraz:
Where should I write about a font/text issue that I discovered?

Sent from my OnePlus One
[ONE General] Ok_Kaleidoscope5109:
BTW, the magnetometer fix seems to mess things up for me. Now the compass shows me 180 degrees in the wrong direction in Google Maps.
[ONE General] tiny4579:
Mines correct. I may have mentioned it in another thread but an issue I did notice is the landscape vertical compass is messed up still. Can't thinkof a time anyone would ever use KT this way but still. Maybe on a car mount using nav.
[ONE General] SomeFormOFhuman:
After certain testing with [MENTION=4800121]Sultanxda[/MENTION] 's fix I realised the same thing was happening. It works for a brief period but direction goes astray after that.

So I decided to take matters into my own hands and began testing a different sensor .conf file this time from OmniROM. I realised OmniROM does not seem to exhibit compass issues, and I used it as my daily driver for a month. And always points in the right direction no matter how I turned my phone.

The file is below in the following Dropbox link. It seems to work as expected on my end (Currently testing [MENTION=1228651]fusionjack[/MENTION] 's SlimSaber ROM) and I just need testers to confirm. I will continue to flash other ROMs especially the official CM nightly to ensure its workability.

https://www.dropbox.com/s/vipehdnps8ba706/sensor_def_qcomdev(OmniROM).conf?dl=0

As usual, navigate to:

system/etc/

Make a backup of the current sensor_def_qcomdev.conf and replace it.

Give it -rw-r--r-- permissions.

NOTE: Please remember to remove (OmniROM) from the downloaded .conf file above as this is to help you remember and differentiate this is coming from OmniROM's magnetometer configuration. It's a ~17kb file anyway which is significantly smaller.

I'm not if this is the right way to credit OmniROM for using their sources for the purposes of testing but, Thanks OmniROM, or whoever the maintainer is. :)

Thanks for your help. Let me know if it helps and give a thumbs up below if it works!
[ONE General] giaur:
But will I able to flash gapps with cm recovery?

What about empty system partition (wiped with twrp)?
[ONE General] ketut.kumajaya:
Activate "Update Cyanogen recovery" in Developer options and then reboot. Reboot to recovery to check your recovery version.
[ONE General] ketut.kumajaya:
Please check the nightly zip, system.new.dat is a pre-formatted image, after 20150418 lz4 compressed ext4 :( Transparent lz4 compressed ext4 mean the filesystem still in ext4 format but some files compressed in lz4 :(
[ONE General] giaur:
Looks normal. 1A with screen on, 2A with screen off

---------- Post added at 02:41 PM ---------- Previous post was at 02:40 PM ----------

Ok, but flashing in to empty /system should not cause any problems? There will be nothing to restore and there will be lz4 compresse system as a result, right?
[ONE General] :
twrp is still here...

can be cm recovery flashed manually?
[ONE General] ketut.kumajaya:
Yes.

Yes, http://goo.gl/BPQrC0 .
[ONE General] ghismo83:
i am on 0421 but the process com.android.phone won't work so i can't set lte or apn :( any solution?
[ONE General] giaur:
No problems here
[ONE General] :
Ok, no problems installing Apr. 21 nightly using stock recovery

Thanks!
[ONE General] shoman94:
Will that overwrite twrp? Or will twrp still be able to be accessed?

---------- Post added at 09:42 AM ---------- Previous post was at 09:39 AM ----------

Thanks... I'll test it out. When I had flashed 4/19 even around 50% it was only charging at 290mA. I flashed last night and went to bed... When I woke it was at 99% and Ampere only showed 10ma.... After reboot it seems better. I will test it out today.
[ONE General] ketut.kumajaya:
You can try the modified TWRP version. I just replace the kernel and the device tree image, keep the original ramdisk.
[ONE General] giaur:
Isn't it already ready to flash? Why replace kernel etc
[ONE General] Spannaa:
Yep, the modified TWRP works nicely ;)

Just test flashed the 20150421 nightly with it - Gapps didn't need re-flashing this time around and I didn't need to reinstall the V4A driver :good:
[ONE General] ketut.kumajaya:
TWRP need a proper kernel for properly access lz4 compressed ext4. I was getting tired explaining this with my limited English :(
[ONE General] :
link to the modified twrp?, please
[ONE General] shoman94:
http://xdaforums.com/showthread.php?p=60253571
[ONE General] giaur:
Not so nicely. I can't backup my current installation. Backup fails without any reasonable error message
[ONE General] dolphin77:
Recovery has its own kernel. Not the one located on the "boot" partition. What ketut.kumajaya did - he replaced the kernel which is in the recovery image and is used when you boot into recovery, so that it support lz4 compression - as a result it can update without the need of re-flashing gapps.
[ONE General] jeebuspwnz:
how are some of you flashing the 4/21 nightly? I can't seem to find anything newer than the 4/18 nightlies even after refreshing the download pages ?
[ONE General] giaur:
But trying to backup: http://pastebin.com/83tTekBE

Any ideas? Pretty useless if I can't backup or restore.
[ONE General] Sultanxda:
Placebo effect ^9001 with the OmniROM config

The sensor registry will only be reset with the default values from sensor_def_qcomdev.conf if the registry is completely missing or if the version string for an entry in sensor_def_qcomdev.conf is greater than the version string for the same entry in the existing registry.

In other words, that config did absolutely nothing unless you performed a clean flash or deleted /data/misc/sensors/sns.reg after installing it. Also, the configuration from OmniROM has the same values set for the magnetometer, so it wouldn't do anything differently with the magnetometer even if you forced a rebuild of the sensor registry.

Your results with the magnetometer are highly subjective. If there's any source of electric/magnetic interference nearby then it won't function correctly as a compass.

[MENTION=3500210]tiny4579[/MENTION] The landscape vertical compass is working fine for me?
[ONE General] SomeFormOFhuman:
Thanks for your input SultanXDA,

No I didn't delete sns.reg, I just grabbed Omni's sensor config and replaced it. It was not a clean flash too (based on fusionjack's 0608 build); I'm just reporting what I did and it wasn't anything I did that was complicated.

Rest assured when tested I wasn't standing with any source of electric/magnetic interference nearby. If you have watched my video it was also in the same room and same position I was standing.

Moreover if it was a placebo I'm not sure why [MENTION=2249907]dmo580[/MENTION] and I are getting the same issues after sometime with it.

I'll probably make a new video and hopefully will explain it.
[ONE General] Ok_Kaleidoscope5109:
Flashed 0808 nightly which overrode my sensors conf file. When I'm in Google Maps in Portrait, my orientation is correct now. That's odd. I'll have to do some more testing when I need to walk around in the city tomorrow.
[ONE General] Sultanxda:
That's because the official CM nightlies have the old magnetometer version string in its sensor conf, so my new values were not overridden in the sensor registry.

In other words, your sensor registry is still using the correct values. Delete /data/misc/sensors/sns.reg then reboot your phone, and your compass will be broken again.
[ONE General] fmc000:
Unfortunately I can confirm that after some hours my compass started to behave randomly again. Only thing I've done are charging the phone, reboot to recovery to take a nandroid and reboot to system, no flashing whatsoever. I'm starting to lose hope. Luckily the nav app I use (Here) doesn't seem to care about it.
[ONE General] infatality:
Same here.. Works for awhile then it's goes bonkers again.
[ONE General] Ok_Kaleidoscope5109:
So I did that rebooted and tried navigating to the ice cream shop down the street walking and it seems to work still. Checked my conf file and its the old 100003 version.

I haven't really used walking directions but the last time I noticed it being 90 deg off was a while ago.
[ONE General] Drastiques:
Proximity sensor bug

i have proximity sensor bug i tried installing custom recovery and reflashed nightly but there's no changes :(((
[ONE General] hogze94:
https://jira.cyanogenmod.org
[ONE General] pocvitaldo:
just wanted to report that yesterday i dirty flashed 08/06 build using updater coming from 07/25 without any issues at all.
[ONE General] cshuwing:
https://jira.cyanogenmod.org/browse/BACON-2492

Not many people voted for this. This is happening to my stock CM 0808 nightly now, anyone knows solution?
[ONE General] Vinoy Thomas:
com.android.phone stopped working

Hi Everyone,

I really need help. I have tried wiping all the data FULL wipe from TWRP and installing the latest cyanogen mod multiple times over. cm-12.1-20150809-NIGHTLY-bacon.zip with no resolve to my issue.

I keep getting this error message "com.android.phone has stopped working". I can't use my phone service, there is no single with two different SIMs. I am losing hope. I can't believe I lost my money on this phone if I can't get this to work.

Please help, I've looked everywhere, resetting caches etc.

Thanks,

Vinoy
[ONE General] :
Calm down. Nothing is ruined.

What version of TWRP? Latest version doesn't flash modems properly.

Also, define what you consider a full wipe?

If you are very concerned just restore to stock via fastboot (you can use a toolkit)
[ONE General] Vinoy Thomas:
OMG, thanks for replying.

Okay I'm using TWRP version 2.8.7.0 (the latest i think). If this isn't a good one which release should i download?

What I meant by "full wipe" is in TWRP I went to advanced wipe then checked everything (Dalvik Cache, System, Data, Internal Storage, Cache). Then I swiped to wipe. Then I went back and tapped on "format data". Those are the two wipes i did.

How do I restore to stock via fastboot? i tried to revert to 4.4.4 with TWRP but I get error "Error Executing updater binary in zip" so i couldn't do that.

But I haven't heard of the method you mentioned using fastboot and a toolkit?

Links would be super helpful cause I'm so lost.

THANK YOU SO MUCH!

Also how do i revert to an older recovery?

I download the older revision of twrp recovery then what?
[ONE General] dgjenkins:
I'm still on 2.8.6.0 (materialised version) and it's all good. If you download a .zip then flash from your current recovery. If you download a .img file then use Flashify from the Play store.

Try this. https://www.androidfilehost.com/?fid=23991606952609056
[ONE General] Renosh:
I'm also using this version of TWRP linked by [MENTION=4315891]dgjenkins[/MENTION] it works perfectly and it allows you to backup firmware between ROMS. Highly recommend it.

The latest version of TWRP has issues flashing firmware so replace it and reflash you should be ok then
[ONE General] Vinoy Thomas:
OMG THANK YOU GUYS SOOOOO MUCH. I was able to successfully install cm 12.1 with Lollipop. With no issues.

FOR ANYONE WITH THE COM.ANDROID.PHONE ISSUE THIS IS THE SOLUTION!!!!!!!!!!!!!!!!!!!

I very much appreciate everyone's help thank you once again.
[ONE General] belrik:
Builds from the 7th and 8th were not working with mobile data. The 9th (latest) build is working again. Weird.
[ONE General] :
Strange, I haven't had any problems with last nightlies regarding mobile data ...
[ONE General] belrik:
I spent a while tinkering, seemed to have reset my APN data coming from 2015-08-02 to 2015-08-08 build, flashed 7th to see if I could find a build before the error. Didn't help but flashing the 9th build fixed it. Looked like the radio was OK but phone wasn't registered with APN. Repeatedly updated APN but no change until I flashed the last build. A confusing error.
[ONE General] novren:
Screen is turning on while phone is inside pocket. This used to happen some nightlies ago, and like then, proximity sensor works ok on phone calls. Firmware is of course 241, and prevent accidental wake-up is also checked.
[ONE General] tiny4579:
There were no changes to the ROM that could have possibly had any impact from 8/8 to 8/9. Now if firmware like modem was changed I wouldn't see it in the changelog. I somehow doubt that.
[ONE General] Tr4il:
What kernels are you guys using with the official nightlies? I'm looking for stability and battery life. I used franco kernel, but franco is not updating for 5.1
[ONE General] :
I'm using Boeffla Kernel.
[ONE General] tiny4579:
Just use stock IMO.
[ONE General] NOSTALGIA:
stock is definetly beautiful
[ONE General] criminalzen:
stock is good.. many use ak
[ONE General] AcmE85:
Stock Kernel offers the best performance and battery life for my usage.
[ONE General] batwingnz:
I've been of boeffla for ages. Tried stock once last week, got a random reboot (the reason I left stock) went back to boeffla and no more reboots.
[ONE General] tiny4579:
If you were getting reboots on stick I'd so love to known what boeffla is doing differently. This reboot issue still hasn't been resolved and cm isn't taking the issue seriously enough. I don't have the issue myself but I'd love to see the jira for this closed.
[ONE General] lephoenix73:
Hi all

What's proper TRWP version to use to go from Stock CM12S to CM12.1 ?

I've read here TRWP 2.8.7.0 has problem., should I install 2.8.6.0 or 2.8.6.1 ?

Thanks
[ONE General] phillibl:
AFAIK you should use 2.8.6.0. I use that with no issues.
[ONE General] lephoenix73:
Thanks.

Did you use TWRP 2.8.6.0 from https://dl.twrp.me/bacon/ or one from 'materialized' set (https://forums.oneplus.net/threads/materialised-twrp-for-oneplus-one.305017) ?
[ONE General] phillibl:
I use the normal one. Haven't even looked at the materialized one, but it should function the same.
[ONE General] lephoenix73:
I've read TWRP 2.8.6.1 was released to support Qualcomm decrypt.

Is it needed to flash CM12.1 nighly on a stock CM12S or the goold old 2.8.6.0 is enough ?

Thanks for your feedbacks, I'm a bit experienced in flashing CM11/12/12.1 on S3 but never did it on OPO yet, so I want to avoid "tragic mistakes" :)
[ONE General] nsmart:
If this describes the error you get, please vote for it: https://jira.cyanogenmod.org/browse/NIGHTLIES-1593
[ONE General] NikoSoti:
The good old 2.8.6.0 is enough for what you want! It will do the job! Happy flashing! ;)
[ONE General] NOSTALGIA:
not getting any reboot on stock here.
[ONE General] nsmart:
If you use device encryption you will need twrp 2.8.6.1 or 2.8.7.0. Previous twrp versions cannot mount data on encrypted devices if you flash the cm12.1 nightlies.

If you want to upgrade from CM12S (cyanogen stock rom) to cm12 or cm12.1 it is recommended to wipe the data partition (no internal sd card). Some more information here.

There is a bug in twrp version 2.8.6.1 and 2.8.7.0 that prevents flashing the correct modem version (241) for cm12.1. Easiest way is to use fastboot to update your modem.
[ONE General] lephoenix73:
So I'll ensure encryption is not set and stick with 2.8.6.0.6 Materialized as many reported it to works well.

I'm on Ubuntu where fastboot/adb are available via sudo apt-get install android-tools-adb android-tools-fastboot

Are my steps are correct ?

copy gapps 5.1 and latest nightly to OPO :

adb reboot bootloader

fastboot oem unlock

fastboot reboot

adb reboot bootloader

fastboot flash recovery recovery.img # from materialized zip

fastboot reboot

Then wipe all, cache and dalvik

install nightly and gapps

Should I expect to flash modem using fastboot then ?
[ONE General] nsmart:
Just check for correct modem version after you installed cm12.1 in settings / about phone. Correct modem version string should start with "DI.3.0.c6-00241-M8974..."

Be sure what happens to you phone data when you do a fastboot oem unlock. Usually this wipes the device completely.
[ONE General] Renosh:
Backup all your data in your phone. fastboot oem unlock will wipe internal storage. When wiping wipe all except internal storage and USB OTG and then flash CM12.1 (includes modem) + gapps (TK gapps) , reboot and you're good to go
[ONE General] lephoenix73:
Thanks guys. I planned to reinstall OPO from scratch so all datas have already been backuped.

If modem firmware didn't start with DI.3.0.c6-00241-M8974., I guess I should do a

fastboot flash modem NON-HLOS.bin

Where could I find up to date NON-HLOS.bin ? I have one in cm-12.0-YNG1TAS17L-bacon-signed.zip, but unsure if it's the very latest.
[ONE General] fmc000:
The latest is included in the nightlies.

---------- Post added at 10:50 AM ---------- Previous post was at 10:45 AM ----------

Today's nightly installation (coming from 0808) didn't optimize any apps. It went straight from the bootanimation to "starting apps" and then to the lock screen. Cool.
[ONE General] lephoenix73:
Thanks :)
[ONE General] belrik:
Thanks for the reply. Now even more confused as I didn't see reasons either. Oh well, maybe my operator was doing something, the stars mis-aligned or I had a bad flash somehow.
[ONE General] ketut.kumajaya:
TWRP 2.8.7.0 mount /firmware partition on boot for decryption support but no GUI access to umount it after. Firmware partition get locked, that's why modem update failed. I silently working to fix this issue. I hope Materialized TWRP still has a complete backup support and also a working decryption feature.
[ONE General] fmc000:
So your 2.8.7.0.1 materialized (this file, to be clear) can backup the firmware partitions, flash modems and decrypt encrypted phones?
[ONE General] ketut.kumajaya:
I mean the next version of Materialized TWRP :)

EDIT:

1. I found fsflags support broken in TWRP, mount after unmount /firmware not working. Maybe that's way [MENTION=912474]Dees_Troy[/MENTION] keep it mounted all the time. A simple change in source fixed it

2. Unmount /firmware after decryption routine will fix firmware flashing issue but I have no plan to encrypt my device for a test

3. The next version Materialized TWRP will be available soon
[ONE General] mykyy:
proximity sensor

Hey, I have problem with my phone OPO. I use CM 12.1-20150810-NIGHTLY-bacon and my proximity sensor don't work.

When check this sensor in "Sensors Multitool" show only Proximity : 0,0 cm.

Please help.
[ONE General] AcmE85:
What is your Baseband-Version in "About Phone"?

It should be DI.3.0.c6-00241-M8974AAAAANAZM-1
[ONE General] mykyy:
Baseband-Version: MPSS.DI.2.0.1.c7-00020-M8974AAAAANPZM-1
[ONE General] AcmE85:
Flash this in recovery: https://www.androidfilehost.com/?fid=23991606952609056

Then reboot the recovery and reflash the latest nightly.

It will fix your issue...

Next time please search and read the thread.

You are not the first one with this problem!
[ONE General] ketut.kumajaya:
Please check http://xdaforums.com/showpost.php?p=62267969&postcount=667
[ONE General] dukeoflove:
Hi everyone, I'd like to try out CM12.1 build 20150725, but it seems like the official link is down. I would appreciate if anyone could reupload the build. Thanks
[ONE General] lephoenix73:
Many here mentions build 20150725.

Did recent builds like build 20150808, 20150809 or 20150810 are broken ?
[ONE General] tiny4579:
I don't think so. 8/10 is fine for me.
[ONE General] eris23:
You can try my unofficial build at https://www.androidfilehost.com/?w=files&flid=30241

You'll probably need to install the earlier firmware at https://www.androidfilehost.com/?w=files&flid=34453 then the ROM then the later firmware.

My builds are pure cm source, and they have a trustzone problem if the firmware's not in the ROM.
[ONE General] Ok_Kaleidoscope5109:
Check permissions to the AFH share. I don't think its working on my end.

The URL should look something like this https://www.androidfilehost.com/?w=files&flid=33863 (my own share)
[ONE General] pabsrocka:
Since 08/08 too much idle drain here... :\
[ONE General] udjat:
Agreed.
[ONE General] eris23:
I fixed the links (I think).
[ONE General] detted:
no data, when wifi is off

rom: 08-07 nightly, baseband: 00241

Not sure if just 08-7 only or it has been all along. Just found out today. If wiif is off, no data connection, only voice. Anyone has any idea?
[ONE General] dmbkiwi:
Is fine for me

---------- Post added at 03:47 AM ---------- Previous post was at 03:44 AM ----------

Any ideas what the kernel changes in the latest nightly relate to (http://www.cmxlog.com/12.1/bacon/ )? Got a random reboot today - first in a while. Just wondering if there was anything the 08-10 build that might have caused this, and whether the kernel changes in the 08-11 build address them?
[ONE General] Coraz:
Can anyone tell me what does "video: mdss: Implement PCC combining for LiveDisplay" mean? (Took it from 08/11 nightly changelog) LiveDisplay is a function that really interests me so I'd like to know what's changing. Thanks.

Sent from my OnePlus One
[ONE General] Bwyan Benton:
These are the notes about it

video: mdss: Implement PCC combining for LiveDisplay *

If we send calibration data via ioctl, we want to make sure it's preserved when applying RGB offsets via LiveDisplay.

* Add support for combining the values, using the calibrated PCC value as a scaling factor.
[ONE General] razorloves:
sounds like the apn you're using is wrong.

double check all the values
[ONE General] Not_A_Dev:
I don't usually complain about battery life (because 4.5 hours of SOT works for me). But since the last couple of nightlies, battery life has become a very ugly story. I'm at 33% remaining with 2 hours SOT. That's just ridiculous.
[ONE General] AcmE85:
Yesterday I was at 5h sot with 25% left before I plugged my device in to charge.

On yesterday's nightly. That was including flashing the nightly which loses around 8% for the app rebuild.

So?
[ONE General] Coraz:
I was around 31% last night, I flashed the latest nightly and fell asleep while waiting for optimization. When I woke up 5 hours later, the battery was still at 25%

Sent from my OnePlus One
[ONE General] GRLDT:
Downloaded latest 08/11 update, got md5 verification failed. Does anyone got this message too? Or is it just me? Downloading again atm...
[ONE General] ketut.kumajaya:
No problem here, a bad download?
[ONE General] detted:
Thanks. APN change resolved it. from "T-Mobile US LTE" to "T-Mobile US LTE IPv6". Just visited Quebec from US east coast. It was through quite a few Network Operator. The phone (unknowingly) worked ok before the trip, then back at home found out the issue. Strange.
[ONE General] GRLDT:
Yup, redownloaded it and everything is back to normal :D

Sent from my A0001
[ONE General] sabrefresco:
On a different note, I still have the bug where the screen doesn't turn on when I am receiving a call (about 7 out 10 times). I have to hit the power button to silent the call and the screen then switches on for me to receive it. This bug is still here for everyone? Any fixes?