yashsingh1/xdaforums huggingface dataset:
[Moto G 2015 Original Android Development] IronTechmonkey:
We're getting a bit off topic in regards to language and forum moderation. N'est pas (Isn't that so)? ;). Don't take it personally when moderators delete or modify your posts as part of their activities. In the interest of neutrality and fairness, such thread clean-ups and reminders are often generally and broadly applied as was the case here. I'm glad to hear that it is acceptable to include an English translation with the original language, which is more welcoming and helpful than that rule's typical (older) interpretation which is that posts must be in English. Thanks [MENTION=258311]Divine_Madcat[/MENTION] for dropping that knowledge.

Careening back on topic: There was a recent 3 day pause in CM12.1 and CM13 production which I had hoped indicated some movement on CM14. No such luck just yet. CM12.1/13 production resumed yesterday with no update in the CM Blog or master build list so maybe that pause was to patch the dirty cow vulnerability for which there seems to be new commits in both the CM13 and CM14 changelogs. I would not be surprised to see a new CM Blog update referring to either the status of CM14 or dirty cow soon. Staying tuned in.
[Moto G 2015 Original Android Development] Agu_Ra:
AFAIK, dirty cow is kernel vulnerability, so it have to be fixed for every device separately, it can't be fixed on the entire CM level. Here is the commit fixing it in our kernel tree. So further nightly builds are not vulnerable to it.
[Moto G 2015 Original Android Development] IronTechmonkey:
That is correct: https://dirtycow.ninja/

That may be technically true but the fix is being applied to many devices so it is still experienced by us as a general rollout that is not specific to one device. I follow the change-logs for Osprey, Peregrine, Otus and CM14 which all do have what seem to be dirty cow related commits. Whether the commits are common or device specific, at least they are there.

Yep. That was the point of my previous post.
[Moto G 2015 Original Android Development] CypherPotato:
no more updates since September 21. It seems that the ROM has abandoned gradually, or it's too difficult to update.

a big help would be to provide the source code of this rom to help their development, not the entire Cyanogenmod...
[Moto G 2015 Original Android Development] IronTechmonkey:
You don't seem to understand the cycle of CM development or the organization and planning that is part of it. For starters, this (which you would already have read if you were following or searching this thread): http://xdaforums.com/showpost.php?p=69214898&postcount=621. Also, did you read the OP of this thread (an expectation here) before commenting on source code?

-----------------

In general for those who like to hawk CM development as a non-developer (as I do) here are some informative resources:

CM Blog (important information about CM would be announced here, eg start of official CM14 nightlies when we get to that point.)

http://www.cyanogenmod.org/blog

CM build targets list (self explanatory):

https://github.com/CyanogenMod/hudson/blob/master/cm-build-targets

CM14 Changelog (still general and not device specific):

https://www.cmxlog.com/14/

CM13 Changelog. Although this is not for CM14, occasionally the activity here might have a bearing on CM14 and offfer background information until CM14 becomes official.

https://www.cmxlog.com/13/osprey/

Jenkins CM buildbot activity, if you are really jonesin' to see what official CM builds are being cranked out at the moment.:

http://jenkins.cyanogenmod.com/view/All/builds
[Moto G 2015 Original Android Development] nandakis4:
i bet alberto and others who are making this cm14 are porting latest 7.1 update also :D thats why its becoming late :)

no problem :) because we can wait :)
[Moto G 2015 Original Android Development] AndresF1406:
There's a cm 14.1 rom indeed
[Moto G 2015 Original Android Development] robot_head:
http://xdaforums.com/showthread.php?p=69347038
[Moto G 2015 Original Android Development] IronTechmonkey:
A nice option to know about, thank you (out of official TYs). That being said; although I appreciate the efforts of the developer who compiled that ROM, the claim that a ROM so early in N7.0/CM14 (and even earlier in N7.1/CM14.1) has no bugs is patently unbelievable, a fact borne out by the bug reports on the pages following that statement. This is not a matter of doubting the ROM which does get good reviews in that thread and may even run better than CM14.x at this point, nor do I doubt the good intentions of the developer, but blindly superlative statements like that undermine belief. I'll wait a bit more to see what CM14.x Alberto97 and squid2 come up with.
[Moto G 2015 Original Android Development] robot_head:
He didn't mean that the ROM didn't have bugs he meant please do not report any bugs found in the rom he was just sharing it for fun
[Moto G 2015 Original Android Development] mrvek:
Unofficialy unofficial CM-14.1 - 2016-10-31

Hi.

Just wanted to share cm-14.1 update until devs find the time to update.

This is my own personal build so it slighly differs from upstream/offical cyanogenmod.

Differnences/changes:

Camera and camcorder working: photos, video recording/pausing/resuming
Marked device as low ram with enabled high end gpu properties
Fixed constant restarting of config_bt_addr service
Enabled sdcardfs (primarily based on [URL="https://github.com/Alberto97/android_kernel_motorola_msm8916/tree/cm-13.0-sdcardfs"]Alberto97's kernel branch[/URL])
SELinux is still permissive
Enabled dex preoptimization: this is the reason for the large size of the update package)

Sources (with the changes not included in mainline cyanogenmod) can be found at my github repo. The rest is at CyanogenMod gerrit.

NOTES:

Disclaimer is as usual: responsibility is all yours and you take the responsibility for any and all issues.

Please be kind and wise and do a full nandroid backup so you can easily restore if needed.

Download

File size: 455,232,781 bytes

md5sum: 51cd856543fc1fc75344523e944bc096 or use the attached zip

@Alberto97

1) The reason you opted for aosp version od sdcardfs is just to be inline with aosp? Asking since I've found no issues with your cm-13.0-sdcardfs branch that I'm using for some time now.

2) Fixes for the camcorder are taken from https://gist.github.com/updateing/9d3683b058d3d0cb1ae7a602213a8cb7 ; I haven't tested http://review.cyanogenmod.org/#/c/165140/

3) support for color aspects causes build failure (log here). Assuming kernel pathes are need but since I was not ableto find them I reverted the merge that introduced it
[Moto G 2015 Original Android Development] AndresF1406:
I think it's better do a clean flash because you need to flash 7.1 gapps, with dirty flash it can happen fc or another unespected bugs
[Moto G 2015 Original Android Development] Gravemind2015:
[MENTION=6685762]Nikos dima[/MENTION] : A clean flash is always recommended.

Broadcasted from Zeta Reticuli
[Moto G 2015 Original Android Development] Nikos dima:
[MENTION=7112679]Gravemind2015[/MENTION] [MENTION=7351117]AndresF1406[/MENTION]

I known clean flash is better but i dont want to lose my apps and settings thats why i want to know if dirty flash is possible

Sorry for bad english
[Moto G 2015 Original Android Development] AndresF1406:
I think it's possible.
[Moto G 2015 Original Android Development] Gravemind2015:
Certainly possible, but the build having differences that too from different developers makes clean install a better choice. You can use TiBu to backup and restore your user apps+data,sms,call log and wifi passwords though.

Broadcasted from Zeta Reticuli
[Moto G 2015 Original Android Development] Nikos dima:
[MENTION=7112679]Gravemind2015[/MENTION] [MENTION=7351117]AndresF1406[/MENTION]

Ok thanks.. I will make a back up and then clean flash
[Moto G 2015 Original Android Development] mrvek:
The differences are minimal so should not require clean flash. I.e., I updated without data wipe.

And yes, I "tested" my own private build. I even tend to use them :p Actually, using as we type.
[Moto G 2015 Original Android Development] Alberto97:
Thanks for your build, I need all my available mobile data in the next days.

The answers now; cm-13.0-sdcardfs is a quick implementation of sdcardfs which has been adapted in order to use vfs_readdir instead of iterate_dir. I don't actually know the difference but to avoid every issue I preferred implementing the iterate_dir way since it's the one sdcardfs uses natively.

Yes I know we can fix the camcorder by reverting back to unified mediaserver and cameraserver. I've successfully tested this way: http://review.cyanogenmod.org/#/c/167269/ which is properly "ifdeffed" to be merged.

Thanks for providing the build log, it saved me some minutes. The build fixes have been merged some minutes ago.

Also thank you for that kernel panic fix... I wasn't able to fix it since lollipop.

Inviato dal mio XT1635-02 utilizzando Tapatalk
[Moto G 2015 Original Android Development] Hedied4me:
He probably has a life. Also just because devs don't respond doesn't mean there isn't work going on in the background. Just follow his github.
[Moto G 2015 Original Android Development] Nikos dima:
Does anyone know what exactly SDCARDFS is or what do ???
[Moto G 2015 Original Android Development] anubis2591:
From what I understand just as an Android and Linux user, not a developer, is that sdcardfs is an alternative method of handling internal (emulated SD) and external storage in a more efficient way. Android uses a userspace (not system/kernel level) method of mounting and modifying filesystems called FUSE. Fuse is often used since it is a well tested easy way to work with filesystems in userspace. However this can come with disadvantages mainly because FUSE is just an intermediate layer between the filesystem and the kernel. sdcardfs however is integrated into the kernel which should mean faster filesystem tasks at the cost of ease of development for Android/Kernel developers. For all intents and purposes this is not a user facing feature so don't worry about it.
[Moto G 2015 Original Android Development] cviniciusm:
Hello,

And some technical info: https://groups.google.com/a/chromium.org/forum/m/#!msg/chromium-os-reviews/GJD3km0lF64/kj-I25iOAQAJ

Copyright (c) 2013 Samsung Electronics Co. Ltd*

+ * * Authors: Daeho Jeong, Woojoong Lee, Seunghwan Hyun,*

+ * * * * * * * * Sunghwan Yun, Sungjong Seo*

+ **

+ * This program has been developed as a stackable file system based on*

+ * the WrapFS which written by*

+ **

+ * Copyright (c) 1998-2011 Erez Zadok*

+ * Copyright (c) 2009 * * Shrikar Archak*

+ * Copyright (c) 2003-2011 Stony Brook University*

+ * Copyright (c) 2003-2011 The Research Foundation of SUNY*

And this too: https://android.googlesource.com/kernel/common.git/+/android-4.1/fs/sdcardfs/

main.c :

/*

* fs/sdcardfs/main.c

* Copyright (c) 2013 Samsung Electronics Co. Ltd

* Authors: Daeho Jeong, Woojoong Lee, Seunghwan Hyun,

* Sunghwan Yun, Sungjong Seo

* This program has been developed as a stackable file system based on

* the WrapFS which written by

* Copyright (c) 1998-2011 Erez Zadok

* Copyright (c) 2009 Shrikar Archak

* Copyright (c) 2003-2011 Stony Brook University

* Copyright (c) 2003-2011 The Research Foundation of SUNY

* This file is dual licensed. It may be redistributed and/or modified

* under the terms of the Apache 2.0 License OR version 2 of the GNU

* General Public License.

*/

Enviado de meu MotoG3 usando Tapatalk
[Moto G 2015 Original Android Development] CypherPotato:
I'm having high battery discharge issues in this build, anyone else?

- wiped everything

- flashed this ROM

- flashed Gapps (nano)

- wiped cache/dalvik

- flashed my pixel launcher package

- wiped cache/dalvik again

- booted normally
[Moto G 2015 Original Android Development] Nikos dima:
Flash a custom kernel
[Moto G 2015 Original Android Development] champagne66601:
they are good kernels there?
[Moto G 2015 Original Android Development] Nikos dima:
The only kernel that support android nougat for now is ruthles kernel. The batery backup is better than stock cm14.1 kernel ;)
[Moto G 2015 Original Android Development] Gravemind2015:
Optimus is updated for 7.0 and 7.1 too :D

Here is the link- http://xdaforums.com/showthread.php?t=3300877

Broadcasted from Zeta Reticuli
[Moto G 2015 Original Android Development] Nikos dima:
Is optimus kernlel overcloced??

Also ruthless kernel is based on optimus so i dont think they have diferences
[Moto G 2015 Original Android Development] Gravemind2015:
I can't remember for sure about the highest frequency it has, but it is overclocked. You're right, ruthless is originally based on optimus but it is slowly being stand-alone project with more differences with each build.

Broadcasted from Zeta Reticuli
[Moto G 2015 Original Android Development] HelpMeruth:
optimus is clocked at 1401 mhz,

please dont just asume that my kernel is the same as optimus that hurt my feelings :p
[Moto G 2015 Original Android Development] Nikos dima:
I'm not saying thats your kernel is the same as optimus.. I'm just saying is based on optimus and i prefer more your kernel than optimus becase your kernel has some good features ;)
[Moto G 2015 Original Android Development] pave_07:
Did you expirience any unusual Google App bug? for example, i've lost Google Now on Tap as well as voice recognition, any ideas? and before anyone else asks, yes i've already reflashed the ROM
[Moto G 2015 Original Android Development] rahul9999:
You guys should give a try a CM 14.1 which is created by [MENTION=6519039]jhenrique09[/MENTION]

i m using this ROM since last 5 days & seriously no bugs found while using this ROM, everything is working fine for me even 1080p video recording on default Camera app is working fine.

Just Clean Flash with latest open Gapps.

CM 14.1 - 01/11/2016

-Latest cm updates

-Camcorder fixed

https://www.androidfilehost.com/?fid=385035244224393254

Send from my XT1550 :) :)
[Moto G 2015 Original Android Development] odysseus84:
Does now on tap (or the assistant stuff) work?
[Moto G 2015 Original Android Development] sakshay1997:
No it does not work
[Moto G 2015 Original Android Development] pave_07:
now on tap is working for me, it has to be set over in settings.. it's really annoying actually because I think it's very useful, but not many people like it so..
[Moto G 2015 Original Android Development] Vink67:
Someone know a solution for theme in Nougat ? I try Layer and Substratum but doesn't work really well, too many glitch.

I would like a nice dark theme.

Sent from my MotoG3 using my finger.
[Moto G 2015 Original Android Development] cviniciusm:
Hello,

See: https://r.tapatalk.com/shareLink?ur...e819946be79e4da74&share_fid=4119&share_type=b

CM14 is landing

Enviado de meu SM-T520 usando Tapatalk
[Moto G 2015 Original Android Development] nandakis4:
LOL :D falcon-aka MotoG(1stgen) users :D :D they are the ones who saw many generations :D :laugh:
[Moto G 2015 Original Android Development] hareshsangar:
Build by fococo

may be some of you will love this :

its build by facoco

https://androidfilehost.com/?fid=385035244224394534
[Moto G 2015 Original Android Development] rahul9999:
have you personally tried it? is everything working in this Rom like 1080p recording on default camcorder..Also please share bug list if any
[Moto G 2015 Original Android Development] IronTechmonkey:
Please before blindly posting "where is it"?...

As explained in the CM Blog here http://www.cyanogenmod.org/blog (and in the the general CM14 change list until it was made device specific) as well as other places, devices are added as they are made ready by developers and maintainers. There are as yet less than 20 devices on the official CM14.1 build list.https://github.com/CyanogenMod/hudson/blob/master/cm-build-targets. One of the devs for Osprey (@squid2) also handles Otus, Falcon and perhaps other models as well as TWRP and kernels. You can learn more about the state of development for Osprey by finding a post by him in the Falcon thread.

---------- Post added at 02:42 PM ---------- Previous post was at 02:36 PM ----------

Is this ROM you are discussing part of the development arc for the ROM being discussed in this thread (which is almost certainly the one which will become official)? If not then it might be appropriate to discuss it elsewhere so people dont get confused when testing the ROM from this thread.
[Moto G 2015 Original Android Development] Alberto97:
Finally An update! This build doesn't fully include november security patches because some of them broke the camcorder again (so before going official we need a fix for this). Talking about device specific sources, they should be pretty much the same that we'll use for official builds so we can consider today's one something like a pre-official build.

Also a thank you goes to [MENTION=4493088]Shreps[/MENTION] who provided us some libs from athene's nougat soak test which allowed us to get rid of a couple of camera hacks.

As always you can find the download at the second post.
[Moto G 2015 Original Android Development] Shreps:
You're welcome ;)
[Moto G 2015 Original Android Development] Aneuryst:
Does this have lockscreen quick unlock?
[Moto G 2015 Original Android Development] sensi277:
Is this in any way related to jhenrique09's build? Been running that for a few days and it's been really good.
[Moto G 2015 Original Android Development] Ahmed Hady:
Thanks bro for your work :)

some logcat errors reflects an error of connecting to hidden wifi network ... couldn't connect to my wifi network because it's hidden

then after 3 min it connects .... i'm facing this error when i try to toggle wifi

11-11 03:18:13.768 3044 3658 E WifiHAL : nl80211: requestResponse->nl_recvmsgs failed: -5
[Moto G 2015 Original Android Development] rahul9999:
Thank you so much for you're efforts sir.. cant wait to test this ROM,

Will definitely test this & report if any Bugs present.. Sound's interesting Pre- Official Build :D
[Moto G 2015 Original Android Development] valkaizer2594:
yes did clean flash already :)
[Moto G 2015 Original Android Development] valkaizer2594:
absolutely its a great rom :)
[Moto G 2015 Original Android Development] kr428:
Hi there;

thanks for your feedback and sorry for being annoying then. Yes I've been actually searching the thread and stumbled across several posts mentioning that CMTE is not yet available, but some of them were "older" and I wasn't / am not sure how to figure out whether or not this is still how things are. So is there any good way to figure out on my own whether CMTE or similar features have come to the ROM? At least in the cm13 nightlies changelog, in example, I wasn't able to spot when the CMTE UI changed the way it is now. I sort of feel dumb asking questions like this, but as the osprey is my daily driver, "just installing" and trying out a ROM is something that doesn't really work too well... ;)

Thanks in advance and all the best,

Kristian
[Moto G 2015 Original Android Development] rahul9999:
As per CM Gerrit CMTE is in works for CM 14.1, we hopefully get it in next build.
[Moto G 2015 Original Android Development] jhenrique09:
[MENTION=4480917]Alberto97[/MENTION]

Which commits you used to fix the camera? In addition to the vendor on your gitub
[Moto G 2015 Original Android Development] althafvly:
Oo .. Great.. A fully working 7.1 rom
[Moto G 2015 Original Android Development] Agu_Ra:
This commit was used to enable the needed hack in libstagefright and somewhere else I don't remember. But if you build against the latest CM sources, it won't work as 7.1_r7 merge broke it because of hardening. So it should be reverted (at least in frameworks_av, I guess) until the fix arrives.
[Moto G 2015 Original Android Development] Malgotra:
Anyone tried installing SuperSU with latest build??

Does phone recognise sim after installing SuperSU??
[Moto G 2015 Original Android Development] mksail:
Don't need to install SuperSU..this ROM is already rooted ;)
[Moto G 2015 Original Android Development] IronTechmonkey:
I'm always out of TYs by the time I get to this thread but thanks for dropping some knowledge here.:good:

---------- Post added at 11:24 AM ---------- Previous post was at 11:23 AM ----------

Test it and let us know :)
[Moto G 2015 Original Android Development] Agu_Ra:
A little feedback

A little feedback about the ROM. At first, I'd like to mention that it is the first custom ROM version I'm using with this device, so I'm comparing it rather to the stock ROM experience than to CM13. Maybe there are some other people who come from stock, so it would be informative for them (especially considering quite unlikely official Nougat update, for which many of us were hoping). I really enjoy CM implementation of Moto features: Ambient display is quite more handy, informative, straightforward and, I would say, natural, wave-to-wake is one more nice feature, chop-chop gesture seems to be more sensitive (on stock it needs the powerful shake to get activated) and fast, maybe it only seems more sensitive because it's response time is shorter.

Talking about device-related features:

- Wi-Fi sometimes is taking quite long to connect. At the same time, it seems that it works faster, maybe it's just placebo but it seems that apps from the Play Store are downloading noticeably faster.

- Maybe also the placebo but it seems for me that call voice quality is better than in stock. Either way, it needs further testing to be confirmed.

CM bugs (for information):

- Battery style can't be changed, despite the corresponding item is present in settings (ah, I miss that circle battery icon).

- Gallery freezes when launched from the Camera app.

- Maybe there are other, CM14.1 is in development stage.

Overall experience is very smooth and almost stable, yet there were some barely noticeable lags, but they eventually disappeared. Thanks to @Alberto97 for the such a great and flawless ROM experience.

BTW, @Alberto97, there is a commit about enabling sdcardfs but storage is still fuse-mounted and the prop from the commit is still not present. Could you please explain why is it not applied? Stock ROM uses esdfs, which is also, as sdcardfs, the fork of Samsung's wrapfs, just curious why is it not in CM as it is not proprietary (or only its kernel-side is open-source?).
[Moto G 2015 Original Android Development] IronTechmonkey:
CM is natively rooted, and CM's native SU for apps has come a long way in the last year but there are still some ROM/app combinations that like SuperSU better so there are valid reasons why someone might need SuperSU. That being said, it makes sense to try native SU first, and CM ROM bug testing/reporting should be done under native SU.

---------- Post added at 11:39 AM ---------- Previous post was at 11:30 AM ----------

I'm quite interested in this aspect as it may relate to something which IMO has been a bug (or at least a desired improvement) in Android and or CM since Kitkat/CM11. Do you get connected to Wifi faster when doing so directly from the list of wifi networks, and is the delay is worse when you connect using the wifi toggles in quick settings panel or top level of settings panel?
[Moto G 2015 Original Android Development] rahul9999:
Thanks for detailed review.. I have also experienced same bugs while using this ROM.. I know [MENTION=4480917]Alberto97[/MENTION] will fix this bugs in his upcoming update.. Patiently waiting for next update..
[Moto G 2015 Original Android Development] Agu_Ra:
I doubt that it is Android/CM bug, more likely to be some Wi-Fi driver/config specific, as on my older device (well, only on custom ROMs, on stock it took quite long) and in Moto stock ROM everything's fine with Wi-Fi. Connection delays are random regardless of enabling it from QS tile, or trying to connecting from the list in Settings/QS.