yashsingh1/xdaforums huggingface dataset:
[E 2015 Original Android Development] IronTechmonkey:
Clean flash recommended for jump between official and unofficial. Also there may have been some substantial changes which have required clean flashes in some cases. Where you do "system, data, cache & dalvik cache" I do: clear dalvik & system caches then factory reset. I dont know if there is significant difference between the 2 methods at that point, but I would suggest a dalvik/system cache clear after flashing ROM before first boot - always.
[E 2015 Original Android Development] Elanza_48:
As someone facing the network (RIL) problem till now i.e, because they might be using the SELinux mode changer apk, which leads to this problem because it changes SELinux mode onboot. Please use the terminal emulator to change the selinx mode manually and uninstall that apk.
[E 2015 Original Android Development] IronTechmonkey:
Good to know. Thanks. I use Tasker to set selinux to permissive at boot when needed, so I should be clear of this.
[E 2015 Original Android Development] enga018:
how do i change with termina emulator?
[E 2015 Original Android Development] Elanza_48:
#getenforce (for checking selinux mode)

# setenforce

usage: setenforce 1 or

setenforce 0

Sets whether SELinux is enforcing (1) or permissive (0).

setenforce: Needs 1 argument.
[E 2015 Original Android Development] Dexter_S:
I don't know but sounds the same. Factory reset delete your apps & data with files on internal memory. Wiping system literally delete the whole system partition. I think that's more effective than factory reset.

Then again, I don't know. I have followed this method since CM12.1 & haven't faced a problem. You have also followed your method. Both might work just the same.
[E 2015 Original Android Development] IronTechmonkey:
... but I will file your method (and others) in my head in case I need them when troubleshooting a flash and looking fr other things to try. :)
[E 2015 Original Android Development] joypurkait:
Hotspot issue

Hi developer,

It seems that this rom doesnt receive files via sharing apps such as Shareit, xender, ES file explorer etc...

It looks like there is some problem with the hotspot.

Thanks.
[E 2015 Original Android Development] Elanza_48:
That's not the problem of hotspot but the improper storage permissions which may be fixed soon.
[E 2015 Original Android Development] ricardo_beatles:
Does anybody know when we will see the first snapshot build? Greetings to all
[E 2015 Original Android Development] dbarrera:
One of the rules say: Do not ask ETA...

Once said that, to answer your question, pretty soon... Recently it got the nightly status, some bugs and quirks must be iron out, then we'll get a snapshot... So, hold on tight...
[E 2015 Original Android Development] Thamizhkavingan:
requesting list of bugs with description

hi, i wish to install the latest nightly of otus cm14.1 but the list of bugs is not clear to me what are all the bugs present in the latest nightly a list with clear description of the bug please because i can't understand what the cm filemanager bug and sd card bug is...

thank you!!

---------- Post added at 06:52 AM ---------- Previous post was at 06:42 AM ----------

if you want pixel like navigation install pixel launcher from google play store or flash with the stock open gapps pack,

google assistant is for now integrated only in the pixel phones but the feature is usable in the google allo messaging app which may be present in the stock gapps or from the playstore...
[E 2015 Original Android Development] satyamsaudai:
Update Failed! Again and again showing same reason!

How to update then?
[E 2015 Original Android Development] Dev_Mashru:
U can get assistant on any phone running above 7.0 by editing d build.prop

---------- Post added at 08:44 AM ---------- Previous post was at 08:43 AM ----------

Which version are u currently running on?
[E 2015 Original Android Development] satyamsaudai:
CM14.1 Official 16-12-2016 Build
[E 2015 Original Android Development] Elanza_48:
That's totally insane. U must know that for checking updates u must have a working network connection. Because we never faced any problem.
[E 2015 Original Android Development] satyamsaudai:
I've no Internet Connection failure! ??
[E 2015 Original Android Development] Elanza_48:
Please recheck it.
[E 2015 Original Android Development] satyamsaudai:
Showing the same!!
[E 2015 Original Android Development] ayush rao:
Dude why don't u take a look at ur own screenshot from it it is clear that there is no network connection on ur phone. Just restart it and try again. If that doesn't work then clearly YOUR data isn't working as there is no fault of the ROM here.
[E 2015 Original Android Development] satyamsaudai:
I hid my wifi from the status bar
[E 2015 Original Android Development] satyamsaudai:
I enabled now! See!
[E 2015 Original Android Development] ayush rao:
Do other apps connect to the internet with no issues?
[E 2015 Original Android Development] satyamsaudai:
Yes! Internet is working properly!
[E 2015 Original Android Development] ayush rao:
Go to CMupdater in settings and clear it's data.
[E 2015 Original Android Development] satyamsaudai:
Same thing happening! Didn't worked!
[E 2015 Original Android Development] ayush rao:
Then I don't really know what's going work in ur case. Did u mess around with the Privacy guard and disable WiFi access to CMupdater.
[E 2015 Original Android Development] satyamsaudai:
No. I gave all permissions to CM Updater.
[E 2015 Original Android Development] ayush rao:
I don't know how to help u man. Also I'm a Surnia user so I'm not entirely sure about how to solve ur issue. I can confirm I don't have this issue on Surnia though.
[E 2015 Original Android Development] satyamsaudai:
:crying:
[E 2015 Original Android Development] vinyasns:
Enable root for apps in developer options.

Then goto build.prop in /system .

Add the following lines at theend of the file :

ro.product.model=Pixel

ro.opa.eligible_device=true

Then save it and reboot your system.

That's it. Now you get Google Assistant feature and can use Pixel Launcher (Get it from PlayStore) without any issues
[E 2015 Original Android Development] Dexter_S:
Just download the latest nightly from the link provided in OP. If CM Updater is not working for you, then use manual approach. It's basically the same.
[E 2015 Original Android Development] ayush rao:
Exactly, I don't know what the fuss is about. If it ain't working for u just download it mamually and update. I always manually update coz I want flash a boot animation and SuperSU along side the ROM. [MENTION=7863284]satyamsaudai[/MENTION] it's best if u just ignore it and download the update from the website and manually flash it onto ur device. To make ur work easier download an app like root essentials and use its flasher to automate the ROM update and the wiping of cache and Dalvik.

Also if u can clean flash the latest build and see if the issue continues. If it does kindly attach a log and help the Dev out. If u need further help please do ask.
[E 2015 Original Android Development] Elanza_48:
Has anyone tried out super SU on cm 14.1, and if so, does it supports or works well ??
[E 2015 Original Android Development] ayush rao:
Yep it works fine as long as u use the latest V2.79
[E 2015 Original Android Development] laxmikant2123:
unable to update CM-13.0-NIGHTLY[otus] to CM-14.1-NIGHTLY [otus] in Moto E 2015.

iam getting the below specified error while updating the Rom cm-13.0- NIGHTLY-otus to cm-14.1-20161216-NIGHTLY-otus on Motorola E 2015 3G.

i tried update it via recovery and cm updater but getting same error..

i got this error :

Installing '/data/media/0/cmupdater/cm-14.1-20161216-NIGHTLY-otus.zip'...

Checking for MD5 file...

Skipping MD5 check: no MD5 file found

I:Zip does not contain SELinux file_contexts file in its root.

I:Legacy property environment initialized.

Target: 1481879506

Target: 1481879506

could not detect filesystem for /dev/block/bootdevice/by-name/system, assuming ext4

could not detect filesystem for /dev/block/bootdevice/by-name/system, assuming ext4

mount: failed to mount /dev/block/bootdevice/by-name/system at /system: No such file or directory

mount: failed to mount /dev/block/bootdevice/by-name/system at /system: No such file or directory

about to run program [/tmp/install/bin/backuptool.sh] with 2 args

run_program: child exited with status 127

unmount of /system failed; no such volume

unmount of /system failed; no such volume

about to run program [/tmp/install/bin/otasigcheck.sh] with 1 args

Patching system image unconditionally...

performing update

open "/dev/block/bootdevice/by-name/system" failed: No such file or directory

script aborted: E1001: Failed to update system image.

Patching system image unconditionally...

E1001: Failed to update system image.

E:unknown command [log]

I:Legacy property environment disabled.

E:Error executing updater binary in zip '/data/media/0/cmupdater/cm-14.1-20161216-NIGHTLY-otus.zip'

E:Error installing zip file '/data/media/0/cmupdater/cm-14.1-20161216-NIGHTLY-otus.zip'

Done processing script file

any help.. Thanx
[E 2015 Original Android Development] Anandabasak:
Twrp version?
[E 2015 Original Android Development] Rush94:
is any one facing storage issue like if u delete a file it doesnt reflect the storage ? i am facing the same issue on both devices condor and otus !

waiting for response
[E 2015 Original Android Development] Elanza_48:
If you are using solid explorer then it is a bug which has not been fixed till now.
[E 2015 Original Android Development] Rush94:
oh thanks i thought it a rom bug so what would u suggest ?
[E 2015 Original Android Development] Elanza_48:
Nothing to suggest. If you want to see data usage per folder basis then use the cm file manager
[E 2015 Original Android Development] Rush94:
thanks save my day:)
[E 2015 Original Android Development] dbarrera:
Guys, quick question.

I missed the alarm tones from the Stock ROM, so I downloaded the tones from here. I saved the files in a Ringtones folder on the Internal Memory. In the clock app, when setting the alarms, I can select the tone I want (Oxygen) but when I press OK it goes back to the Rooster tone.

What is interesting is that this only happens with the alarm. Probably because it is an OGG file? I have my phone ringtone set to an MP3 file and it works great.

I've already searched for a similar issue, but no luck... Any advice? I'll try and convert the OGG to an MP3 and see what happens... And is curious, given that OGG is an open-source audio file format, but MP3 is propietary (as far as I remember)...
[E 2015 Original Android Development] :
Grant storage access to clock app
[E 2015 Original Android Development] dbarrera:
Hm! Funny thing! I know I granted permission to the app when it first started... I checked in the settings and no permission was granted to the Clock app... Enabled the permission and seems to set the tone now... Testing... And it works! Thanks!
[E 2015 Original Android Development] Elanza_48:
Of course, because for others you have option for choosing between the media files on the system partition only preserved for ogg files. You can't simply copy dnd use a mp3 file on the system media. To convert simply rename the .mp3 to .ogg, that's it.
[E 2015 Original Android Development] el_charlie:
Guys.

Newbie question here. If I update the ROM via the settings>updates, what about the GApps? Do I need to apply them again?

Thanks in advance.
[E 2015 Original Android Development] Elanza_48:
No
[E 2015 Original Android Development] el_charlie:
Please elaborate.

Does the CM updater backs up the GApps or something?

The CM zip patches the whole /system unconditionally so I don't know how the GApps are kept installed. Maybe the CM updater is different.

Thanks for the fast response.
[E 2015 Original Android Development] ayush rao:
So basically there's this thing called addon.d. They are scripts which prevent a certain file or a collection of files from being uninstalled from the system. Gapps has an addon.d script and so when u update the ROM the Gapps remain untouched.

That's it basically means. I might of messed up the terms but that's how it works.
[E 2015 Original Android Development] el_charlie:
Wow the snapshot is live.

Can we update on top of the latest nightly or the snapshot code is a bit old?
[E 2015 Original Android Development] IronTechmonkey:
You are on the right track about snapshot main code being older (apart from new important commits that were put in). Yes indeed it is better to do a clean flash anytime when jumping between nightly and snapshot in either direction, perhaps more so in this case of a 1st snapshot.
[E 2015 Original Android Development] Elanza_48:
The addon.d is the backup and restore script. The apk and files which was flashed through the gapps.zip has the backup code written on that file, when you flash the rom package at first the addon.d file is executed and the as per the mentioned files the files and apks are backed up and restores after the rom is patched . The interesting fact is you can edit the addon.d script and manually and mention the files apk dex and lib files that you want keep stay after the firmware flash even if it was not flashed through the gapps package, mainly the user to system converted apk files.
[E 2015 Original Android Development] ayush rao:
Thanks for clearing it up man. I've edited it in the past when I installed opengapps stock but wanted to uninstall the apps I didn't want.
[E 2015 Original Android Development] Elanza_48:
If you are saying that you edited that because you want to get rid of apps unnecessary for u which was installed on the gapps package flashed, then you are totally in wrong path. There is a much simpler, secure and advanced process to get rid of the apps.

Check out this link and thoroughly study it :

https://github.com/opengapps/opengapps/wiki/Advanced-Features-and-Options

https://github.com/opengapps/opengapps/wiki/Package-Comparison
[E 2015 Original Android Development] diago27:
Read properly, the snapshot is for CM13, not CM14.1! DO NOT DIRTY FLASH THAT SNAPSHOT IF YOU ARE CURRENTLY RUNNING A RECENT CM14.1 BUILD.
[E 2015 Original Android Development] ayush rao:
Oh thanks for this. I knew something like this existed but I didn't really look into it. Most of the time I use the Nano package (My favourite), but I used addon.d to remove the unwanted Google apps coz I was running out of space on my phone and didn't want to have to download another package. I bookmarked it and if I ever need it I'll use it.

Thanks!?
[E 2015 Original Android Development] el_charlie:
Thanks!!!

I would be very disappointed if I made a wipe and ended up with CM13 (not to mention the gapps I have are for 7.1, the phone wouldn't even boot properly, lol).

Cheers!
[E 2015 Original Android Development] pravalik:
Any ril related issues in d recent nightly???
[E 2015 Original Android Development] Elanza_48:
I don't think that there is any use of that hexalibro theme present in cm 14.1, and honestly to say the cm superuser is not maintained. It does not give the root access to many apps even the root checker which is creating a huge problem I was facing problem on gaining root access to the latest version of Greenify after converting it into system app, it forced me to flash the superSU !!

---------- Post added at 06:18 PM ---------- Previous post was at 06:10 PM ----------

If anyone interested on substratum can u try it out and inform us about the themes working correctly.
[E 2015 Original Android Development] IronTechmonkey:
I've always wondered how many of the problems people have with native CM SU are CM problems and how many are app problems. I have seen apps (such as Afwall) develop them selves into compatibility with native CM SU but this is not to say that native CM SU could not be improved.. Perhaps that root checker app was developed during the time when native CM SU was new and more people were using SuperSU, and needs to be updated. Which root checker app is it? I can give it a test on my next flash (which may not be for several days).
[E 2015 Original Android Development] Elanza_48:
Surprise to see but this one.
[E 2015 Original Android Development] IronTechmonkey:
Surprise indeed. That is a well known one. Thanks.
[E 2015 Original Android Development] Dev_Mashru:
Every time I try to see the changelog, I get 404. Is this a bug? Anyone else experiencing it?
[E 2015 Original Android Development] Elanza_48:
Yes it is a bug and was even their in cm 13. To see the chage logs u have to download 3rd party apps from play store
[E 2015 Original Android Development] Elanza_48:
Can please checkout that weather u can set pin lock or not. Because I'm unable to. Had to flash 2.79sr1
[E 2015 Original Android Development] ayush rao:
I have the LTE version (Surnia) and i can confirm on CM14.1 on my phone (Not Otus), I am able to use a PIN lock on my phone. Of course our devices are different but I thought since u quoted me I'd just share if it worked for me as CyanogenMod bugs are common across most of their devices.
[E 2015 Original Android Development] Elanza_48:
I'm not talking about lockscreen pin. But the superSU root access pin inside the app
[E 2015 Original Android Development] ayush rao:
I dont have SuperSU Pro so I can't use a PIN Lock for SuperSU.
[E 2015 Original Android Development] Elanza_48:
Use the sudo superSU pro option in the app
[E 2015 Original Android Development] ayush rao:
Oh I didn't know it came to SuperSU. I used to use the freeload option in live boot. Yea I can confirm I'm able to set a passcode but I can't use it to give root access to any app. It keeps asking for the pin.
[E 2015 Original Android Development] Elanza_48:
But I'm not even able to set the pin. If I set a pin it automatically ingnore/disables it.

But it is all right on v2.79sr1.

Strange !!
[E 2015 Original Android Development] IronTechmonkey:
... or purchase SuperSU,.. which I just did after seeing those posts, realizing how much I've used it. Comes out to about 75 cents per device that I've used it on over 4 years. Then there is the fact that until recently many things I did depended on it. Sorry for OT.
[E 2015 Original Android Development] santoshx99:
Installed cm-14.1-20161223-NIGHTLY with opengapps-7.1-pico-20161217. Till now everything is running smooth.

Many are using SuperSU over native CM Su. But there is no reason to install SuperSu, native CM Su handles every root apps properly.

I checked by Bluetooth stereo earphones with viper audio2.4.0.1 installed. There is a very little audio glitch while listening over Bluetooth but its OK.

BTW Merry CHRISTMAS!! to all
[E 2015 Original Android Development] Rush94:
yesbro working with me on condor cm14.1 with21st dec build you need to clean the old su binaries to install new
[E 2015 Original Android Development] satyamsaudai:
Quick Unlock feature is missing! How to add?

There is no xposed module for android N. So how to add this feature?
[E 2015 Original Android Development] Dexter_S:
I just read the new about the discontinuation of CyanogenMod infrastructure. And consequently moving to a new fork Lineage. Does that affect the upcoming nightlies as well? Or will it merge the existing forks into Lineage?

https://www.cyanogenmod.org/blog/a-fork-in-the-road
[E 2015 Original Android Development] IronTechmonkey:
This may be a bigger change than just that, such as devices being dependent on individual developers, unable to rely on jenkins and other stuff so after Dec 31 no more cohesive runs of nighltys for all devices. We'll have to stay tuned.

More info: https://www.xda-developers.com/the-death-of-cyangenmod-and-whats-in-store-for-the-future/
[E 2015 Original Android Development] Dexter_S:
I thought so too. I am currently returning to the final snapshot of CM13. The loss of automated builds are a huge blow for updates. Let's see what is the future without jenkins.
[E 2015 Original Android Development] Elanza_48:
That's more than a sad news !!:(

Hoping for the newer LineageOS for all devices including ours. :fingers-crossed:
[E 2015 Original Android Development] ricardo_beatles:
The death of Cyanogenmod is really sad, but I don't know what really means that about the current versions of cm14.1 for otus, Does it mean otus won't receive any new nightly or snapshot version of cm14.1? and a personal question, shouldn't I install the last nightly of cm14.1 for daily use or I should remain in cm13?
[E 2015 Original Android Development] IronTechmonkey:
A lot of that stuff about the future of development is answered in the linked articles. No criticism implied at all here but eventually parts of this discussion may be considered off topic as it has been in another ROM thread. Even though it is about the course of development it may not be considered a software development discussion.

As to what ROM to use: CM13 is mature and less likely to have serious issues. CM14 is/ young with and almost certain to have some bugs. If your stuff is well backed up and you dont mind the work or the possibility that you'd have to fall back on CM13 then give CM14.1 a try, otherwise IMO CM13 is a safer bet. Easy for me to say, still on CM12.1 except for testing.
[E 2015 Original Android Development] squid2:
The whole CyanogenMod development community is moving over to the Lineage fork. From a user perspective, the fork is effectively a name change to avoid conflict with Cyanogen trademarks. Our goal is to preserve backwards compatibility with CyanogenMod, so that you can upgrade (dirty flash) directly from CyanogenMod 14.1 to Lineage 14.1. We still intend to have official builds. However, given the end of corporate backing, there will likely be fewer build servers, and so we may be switching to weekly builds instead of nightly builds. I don't think that will be much of an inconvenience to users, as day to day changes are usually quite small.
[E 2015 Original Android Development] IronTechmonkey:
A pleasant surprise. That is more preservation of the general structure and continuum than I anticipated. Also, I can think of reasons why a weekly schedule might be better, especially in these threads. Thanks for the information.
[E 2015 Original Android Development] Anandabasak:
Gr8 move really

Most users dont even update daily so no need of daily builds

Weekly or biweekly builds will be just gr8 and wont bother users at all

Best of luck to u and the whole lineage os team
[E 2015 Original Android Development] Elanza_48:
It's a perfect idea for weekly updates Instead of nightlies.

Awesome !!??
[E 2015 Original Android Development] ayush rao:
[MENTION=6485916]squid2[/MENTION] I had a couple of questions.

If Cyanogen is sold to some company, won't Lineage be made to like close down or rewrite code cause u guys at Lineage are just forking over everything from CyanogenMod.

Also will there be any theme engine like CMTE (or something new) or Substratum?

I know it's too early to answer the questions but if u can pls answer me.

Thanks!?
[E 2015 Original Android Development] Elanza_48:
As you know that Android is an open source project so it is very legal to fork the source code of any previous built project even it is made by the group which is no longer in it's ownership.That is why they have given the rights to the developers who wished to continue on the cyanogenMod source code. The cyanogen Mod will not able to continue just because of the brand name, that's all and it has no effect on the source of the project, may be the pace of development have an drastic effect.

CMTE is a part of the CyanogenMod project and hence it will continue. As you very well known that CMTE is move advanced than the substratum and also substratum is well supported on 7.X, so now think about CMTE.
[E 2015 Original Android Development] ayush rao:
K thanks for answering. ?
[E 2015 Original Android Development] Kuck7610:
Really Buddy UR making So Dam good Rom!!!!!!!!
[E 2015 Original Android Development] iamcr1212:
I have flashed the Dec 7 build. And the battery is draining fast. Please help
[E 2015 Original Android Development] Elanza_48:
Some please upload or share the 25th December buitd. The jenkins server is down !! :rolleyes: