yashsingh1/xdaforums huggingface dataset:
[Moto G 2015 Original Android Development] Agu_Ra:
Well, it's done not to confuse impatient users, I guess. Device is still in CM-14.1 list in CM's Hudson. Due to some reason CM didn't start any builds today. They have had some issues with build servers recently: some nightlies were "aborted". Maybe they're not solved yet. Stay tuned to CM's Jenkins.
[Moto G 2015 Original Android Development] EsromTech:
I'm also inside CM Jenkins, and I see that some cm14.1 builds started there ... we should not be desperate but any time it comes out to build.

Anyway if you do not leave, [MENTION=4480917]Alberto97[/MENTION] has already done a good job.
[Moto G 2015 Original Android Development] Devtaji:
I'm downloading opengapps.

Do I need ARM or ARM64?
[Moto G 2015 Original Android Development] EsromTech:
ARM only
[Moto G 2015 Original Android Development] SayantanRC:
As far as I know, it will be ARM, Android 7.1, micro.
[Moto G 2015 Original Android Development] VladMav:
Screen goes off and phone dies during call

Hi guys,

dunno if anyone had similar issues, but my phone screen goes black and I cant do anything to turn it back on after I place a call (is the same for all calling apps like whatsapp skype). Power button ends call is also checked, but does not work. Also tried to diasble the sensor, that doesent work. Do you have any idea what I could to? already tried emptying the cache and cleaning the sensor, its definetly a software problem.

Except this the ROM is great, big thanks [MENTION=4480917]Alberto97[/MENTION]
[Moto G 2015 Original Android Development] guest_2011:
Only using 14.1 a few days and already noticed it's draining battery a lot faster than 13.1 when i had lots of apps. I use Shutapp but it doesn't seem to do anything. Also takes a lot longer to charge, about 3? hours. Not streaming audio/video, screen off, no data, no bt, airplane mode, only wifi enabled.
[Moto G 2015 Original Android Development] Agu_Ra:
New build skipped

[MENTION=4480917]Alberto97[/MENTION], due to some obscure thing build for our device started but it finished "with success" even without building. Here is the log on Jenkins.
[Moto G 2015 Original Android Development] notDroid:
I have the XT1542 version and it works great. No problems with sim.
[Moto G 2015 Original Android Development] playenball:
[IMG="CM 14.1"]http://i.imgur.com/34yMJOz.png[/IMG]

According to Jenkins cm14.1 successfully built for osprey. I would assume it will be on the official download page shortly.
[Moto G 2015 Original Android Development] alaxricard:
Did not leave the official cyanogenmod list as it is in the list and here is the link to see and someone could tell me why it was not released on the server to leave the official today?

https://download.cyanogenmod.org
[Moto G 2015 Original Android Development] nandakis4:
i heard the same complaint from a user several days ago.. he mentioned the same problem ..

please confirm this : can u reproduce this problem on STOCK rom ??

if you see same kind of behaviour from your Proximity sensor.. :rolleyes: then its defnitly wrong of your sensor but not the ROM..

else .. calibrate the Sensor

---------- Post added at 08:24 AM ---------- Previous post was at 08:20 AM ----------

today morning when i saw this 14.1 as UNofficial -- i reloaded the page ( thought my webpage showed cached page )

but its real..

hm..

again to unofficial?? made me think !!

is it because of Cm13 snapshot ?? as alberto has mentioned his concern about removing CM13 somewhere..

if this is reason, then CM14.1 might be stuck at unofficial for several more days ..
[Moto G 2015 Original Android Development] sagar27691:
don't know what is going on but our device is already removed from the cm13 section to the cm 14.1 changelog in cm changelog site. See the SS.
[Moto G 2015 Original Android Development] citizen30:
[MENTION=5917809]cucumber09[/MENTION] On Jenkins , it can be seen that cm 14.1 osprey is build successfully and it's status is stable....so what happens now?
[Moto G 2015 Original Android Development] VladMav:
Had stock ROM on it before, everything worked fine. Also took down the screen protector since some peope mentioned that could cause bugs. As I said, its definetly NOT a sensor problem
[Moto G 2015 Original Android Development] PABLEXWorld:
SIM is broken on clean flashed (data, cache and dalvik wiped) XT1543 with SuperSU v2.78-SR4-20161115, Magisk v9 and Open Gapps stock package from 20161111 with custom gapps-config. Says no SIM card could be found. Worked on both stock and official CM13. Just thought I'd report that. I'm from Argentina, by the way. hope this helps..

My gapps-config.txt:

forcedpi320

PreODEX

(FMRadio)

Include

CalendarGoogle

CalculatorGoogle

CameraGoogle

Chrome

ClockGoogle

CloudPrint

ContactsGoogle

DialerFramework

DialerGoogle

Docs

Drive

ExchangeGoogle

FaceDetect

FaceUnlock

Gmail

GooglePlus

GoogleTTS

Hotword

KeyboardGoogle

Maps

Messenger

Music

PackageInstallerGoogle

PixelIcons

PixelLauncher

Photos

PlayGames

Sheets

Slides

Search

Speech

StorageManagerGoogle

VRService

Wallpapers

WebViewGoogle

YouTube
[Moto G 2015 Original Android Development] HelpMeruth:
Dont flash superSU
[Moto G 2015 Original Android Development] IronTechmonkey:
We wait to see if there is just a lag in posting the completed build or we wait for the next nightly run. There are a few types of things that could delay a first official nightly such as a broken build (seemingly not the case for us) or perhaps some administrative thing that prevents the build from being handled by the system that posts the completed builds for download. In any event, it wont be long before they start rolling.

[EDIT] For what this is worth: The jenkins console output for the seemingly successful Osprey build reports "error: Exited sync due to fetch errors" which AFAIK is related to failed builds and this "Device osprey not found. Attempting to retrieve device repository from CyanogenMod Github (http://github.com/CyanogenMod)." which doesn't sound good either. Also, the output lacks the statement "#### make completed successfully (35:31 (mm:ss)) ####" and other details typically associated with successful builds.
[Moto G 2015 Original Android Development] EvilHowl:
Hi, did you see the build only taked 6min?
[Moto G 2015 Original Android Development] IronTechmonkey:
No I did not notice that (thank you) but that fact lines up with some other things I saw in the console output (and was back-filling into previous post as we cross posted http://xdaforums.com/showpost.php?p=69644277&postcount=890. So, something wrong with the build and we wait another day. So it goes.
[Moto G 2015 Original Android Development] EvilHowl:
Another day :(
[Moto G 2015 Original Android Development] sakshay1997:
u mean we have to wait for one more day for official nightlies to start?
[Moto G 2015 Original Android Development] Tron_Legacy1680:
Can I flash the full gapps? It didn't work when the rom was in 7.0 and I had to flash mini.

Thanks!
[Moto G 2015 Original Android Development] :
Currently m ussing full gapps without any error...

And i also replace dialer and contact to google sialer and contact..
[Moto G 2015 Original Android Development] Tron_Legacy1680:
Thanks for replying! I'm going to flash full gapps then!
[Moto G 2015 Original Android Development] mruwek:
As far as I understand the build log, there was some error while git fetching one of the repos, so Jenkins didn't find "any changes" since last build and didn't start compiler. I'm sure [MENTION=4480917]Alberto97[/MENTION] saw this and will fix it as soon as possible. I'm using version from 10/11/2016 and it is stable as rock here.
[Moto G 2015 Original Android Development] PABLEXWorld:
Thanks. I've entered TWRP, ran pigz -d on the backup stock_boot, then flashed it and deleted both the backup and su.img, it works now.

May I ask why flashing SuperSU breaks SIM?
[Moto G 2015 Original Android Development] Agu_Ra:
It is marked as successful by mistake, actually build itself didn't even start because of some sync errors. It is software, it can't be ideally robust, you know, especially in case with such complex build systems relying on scripts.
[Moto G 2015 Original Android Development] Agu_Ra:
As far as I remember, dual-sim RIL activation relies on the one of init files in boot image ramdisk, which is replaced by SuperSU one in order to activate systemless root in its hacky way.
[Moto G 2015 Original Android Development] JuanSiddharta:
chip issue

Guys, when I instaled this ROM, the chip and 4G works perfectly, so flashed the last version of Supersu from (xdaforums.com/apps/supersu/stable-2016-09-01supersu-v2-78-release-t3452703) and I got the same problem people are having (Chip stoped work)
[Moto G 2015 Original Android Development] Devtaji:
Some apps are not able to access the external memory card.

Even the cyanogen file explorer is unable to mount it.

Is there any solution to that?

Can it be because of this in the Open Gapps package?:

Google Storage Manager (replaces stock/AOSP Storage Manager)
[Moto G 2015 Original Android Development] shankufx4y:
moto gallery and moto camera doesn't wrk... if any posibility fix this...
[Moto G 2015 Original Android Development] notDroid:
I'm using Moto Camera without problems.

But Moto Gallery isn't compatible with 7.1 I guess.
[Moto G 2015 Original Android Development] danpan11:
Hi Man, it seems that this bug happens to me every morning when I leave for work, but I wanted to ask you, I tried the command for the temporary solution but my rom does not have su, any safe way to do this? since I have seen some posts of people losing SIM card connection.

Thanks in advance!
[Moto G 2015 Original Android Development] shankufx4y:
my problem is.... camera app instaled but touch is not wrking
[Moto G 2015 Original Android Development] notDroid:
Weird, my app is working as intended. You can try wiping the data and cache of the app.
[Moto G 2015 Original Android Development] shankufx4y:
the version i got 6.0. iam stucking on the first page of app.... the next button wont respond....
[Moto G 2015 Original Android Development] S¡lver:
Did you change the display size in settings? The Moto Camera app is hard coded with the dpi. It doesn't change the touch positions based on the display size
[Moto G 2015 Original Android Development] notDroid:
Go to Settings > Devloper options and under Networking section, enable the Cellular data always active

I'm testing with that option and it seems to work.

To see the Developer options under Settings you have to do: Settings > About phone > tap seven times on Build number, then go back and you will see the Devs Opt.

Hope it helps.
[Moto G 2015 Original Android Development] danpan11:
Thanks! will change that option and let you know if it works as well.

BR,
[Moto G 2015 Original Android Development] shankufx4y:
Yeah.... Solved man... The problem is DPI..... I changed to small that was the problem... What about Motorola gallery... Any hope...
[Moto G 2015 Original Android Development] S¡lver:
I didn't try Moto Gallery, so I don't know..
[Moto G 2015 Original Android Development] :
Will u give me post no. So i read easily...
[Moto G 2015 Original Android Development] S¡lver:
http://review.cyanogenmod.org/#/c/171440/

Could it be that this commit would fix the unsuccessful build? (As in, the next attempt of building will not have sync errors?)
[Moto G 2015 Original Android Development] melp57:
Here you go.

http://xdaforums.com/2015-moto-g/orig-development/rom-unofficial-cyanogenmod-14-t3466246/page73

look down towards bottom of page.
[Moto G 2015 Original Android Development] EvilHowl:
Maybe.

Alberto is a great developer and I am sure tomorrow we will have official CM14.1.
[Moto G 2015 Original Android Development] pio80:
It works good, I checked it.
[Moto G 2015 Original Android Development] shankufx4y:
Which version u tried...
[Moto G 2015 Original Android Development] pio80:
This is ver dedicated for moto g3.
[Moto G 2015 Original Android Development] IronTechmonkey:
Thanks [MENTION=5917809]cucumber09[/MENTION] for some genuinely informative posts about the state of the first Osprey nightly. Unfortunately that good information is buried in a sea of hit-and run posts from people who seem to think XDA is a free software and support portal.

To newer XDA members: Please know that reading OPs and searching for answers BEFORE posting a question are XDA rules. XDA is not a free software and tech support distribution portal. This is a place to contribute to development of the software. At the very least you search before posting and follow XDA rules. Even better would be to provide viable testing results in proper bug reports. All of these posts might as well be tattoos on the forehead that state "I did not bother to read the rules and I'm here only because I want something". That may not be how you mean it but it is how it looks, and it bogs down the thread.

[MENTION=5864394]subins mani[/MENTION], - http://xdaforums.com/showpost.php?p=69648274&postcount=905

[MENTION=7825746]sakshay1997[/MENTION], - http://xdaforums.com/showpost.php?p=69648591&postcount=908

[MENTION=4665219]michkost858[/MENTION], - http://xdaforums.com/showpost.php?p=69650212&postcount=922

I am sorry to be so direct but posts like those make it more difficult to find good information in the thread. If you participate in the spirit that XDA is intended then you'll find that people jump in to willingly test your problems and help you fix them. Please don't waste that dynamic here on XDA.

[EDIT] Removed one link to post that did not belong on this list, with apologies [MENTION=4714682]mruwek[/MENTION]. Others seem to have been deleted.
[Moto G 2015 Original Android Development] shankufx4y:
Were did u get... Plz give a link... When I tried to install I got this...
[Moto G 2015 Original Android Development] pio80:
Google Play store [emoji1]

I have to add: the quality of sound recording in both (moto and cm) is not good you should know.
[Moto G 2015 Original Android Development] Hedied4me:
Man I could not have said it any better. This post was much needed. Sadly I think it will have very little effect. People will continue to post about the lack of a nightly build to the point where Alberto97 had to change the title of the thread back to Unofficial. Very few people truly understand these threads are meant for development purposes. That being said my post adds little to the thread itself.
[Moto G 2015 Original Android Development] drkhalidomer:
You might have changed DPI !!! Moto Camera will work in default DPI of 320.
[Moto G 2015 Original Android Development] CypherPotato:
why flashing super su? Cyanogenmod has a self-root manager hidden in developer settings thats much better :P

---------- Post added at 05:56 PM ---------- Previous post was at 05:37 PM ----------

install it in /system/app/MotoGallery/<place apk here> and restart
[Moto G 2015 Original Android Development] IronTechmonkey:
Speaking from my own usage case: There may still be some important apps that work better under SuperSU. In my case that list included, Better Battery Stats, Titanium Backup, LMT Launcher, Afwall +. Over time most apps have been tweaked to work under native CM SU but Afwall + is still sorting that out. So I install CM and go as far as possible with native CM SU. That being said, ROM testing and bug reporting should be done under native CM SU.
[Moto G 2015 Original Android Development] karelcristian:
How to make the TV app work?
[Moto G 2015 Original Android Development] :
Use jiotv app.. watch more thn 350 imcluding hd channels...

By the way this is not the right place to post ur questions...
[Moto G 2015 Original Android Development] EsromTech:
Hi, my friend, I am in full agreement with you and satisfied with the rules of xda. Although the members seem to continue in a stupid way asking the same questions.

ATTENTION

You need to stop this attitude of yours as quickly as possible before any moderator can take any action against you.

The topic of this discussion is for development only, yes DEVELOPMENT!

It does not matter to anyone here if some alternate app does not work.

It does not matter if it stopped working something only because you installed what it should not.

It does not matter if you want to use xposed or whatever.

What really matters is that CyanogenMod14.1 works correctly. If your root does not work, try going into "programmer options" and activating it.

Do not install things that are not suggested by the developer, if you install, then do not come troublemaker, that's not the focus here, read the rules and help the development of better quality.
[Moto G 2015 Original Android Development] IronTechmonkey:
OK, trying to get myself back on topic: I'm wondering if anybody has seen a certain obscure bug(?) that has lingered in CM since at least CM11: "Countdown timer passes zero and does not sound until screen is powered on or some other event occurs." I've personally seen this in CM11, CM12.x, and CM13, across 5 different Android devices, and others have reported in several other devices. At one time in CM11 there was a jira ticket for this which went nowhere https://jira.cyanogenmod.org/browse/CYAN-6137. I'll be testing for this (among other more important things) but am fishing for details from anybody who may have seen this or something similar in CM14.1. Thanks.

[EDIT] Greetings [MENTION=4730968]EsromG5[/MENTION], You sound like me about Xposed :)
[Moto G 2015 Original Android Development] pave_07:
Today i've tried to merge the SD card with internal memory to see if it continued with the negative numbers problem.. it's still not fixed. Memory working without problems though
[Moto G 2015 Original Android Development] notDroid:
I've used the Coundown timer at least 6 times since I flashed CM14.1 and haven't noticed that bug yet.
[Moto G 2015 Original Android Development] :
Sorry for that, fellow Moto G3 users. Maybe I rushed my post and shouldn't have posted it. However, I got confused since jenkins said that the build was successful but there was no build on get.cm (again tho I should have looked for an answer in the thread!)
[Moto G 2015 Original Android Development] bluematrix46:
VOLTE Problem

Hey Alberto Nice job with CM14.1 loved it

Everthing is working Fine but i cannot switch my VOLTE its just getting disabled is there any procedure i should do or should i wait for another patch update ?

Thanks
[Moto G 2015 Original Android Development] Andresmoraj:
Read comments
[Moto G 2015 Original Android Development] shankufx4y:
1st day usage experience.....

The os working perfectly there is no doubts and excellent job...

1. while plugged into charger... The screen doesn't goes automatically turned off. Need to tap on the power button for turning of...

2. battery back up is normal on night...(cell standby : 6% screen : 3%)
[Moto G 2015 Original Android Development] debopriyobasu:
Hello everyone! I just wanted to know where should I report bugs in CyanogenMod? I have noticed a bug which had been there since CM 13 and hasn't been rectified in CM 14.1. This thread is full of duplicate posts and conversations and I don't expect the developer to swipe through hundreds of pages reading each comment. Can anyone describe to me how to correctly post bug reports(with catlog or adb) and how to properly post the bug report in an appropriate format and in an appropriate forum/bug tracking site where I can check whether it's reported or not and correctly post it so that it can be noted and rectified?

Note: I reported the bug in the CM13 "bugs section" (available on top, beside discussion)post by the same developer few months ago. But it seems it hasn't been noticed.

It's NOT just another VoLTE related stuff:laugh:
[Moto G 2015 Original Android Development] creative21:
make sure 'stay awake' is off in developer options
[Moto G 2015 Original Android Development] rahul9999:
I Don't think currently there is any proper bug section for CM 14.1 yet.. you can PM Dev to rectify bugs because this thread is spammed with VOLTE related complaints..

Hope i have resolved your quarry.. :o
[Moto G 2015 Original Android Development] shankufx4y:
it is off
[Moto G 2015 Original Android Development] creative21:
my screen turns off automatically while plugged into charger on latest build of cm14.1. maybe some app is causing that problem, try charging only mode if ur charging form pc usb.
[Moto G 2015 Original Android Development] EvilHowl:
CM14.1 for osprey is in queue in Jenkins!

Let's go!
[Moto G 2015 Original Android Development] melp57:
Nice. Still don't know what the big deal is about being official. Hope it means some things will be fixed, like Circle battery and add theme engine. etc...

can't wait, and thanks for sharing.
[Moto G 2015 Original Android Development] twigster:
CM official means regular builds of updated code which is being actively maintained and improved by CM recognised contributors, and with proper support for our device.

Circle battery may not be fixed immediately, but there is more chance it will get fixed and be fixed properly.
[Moto G 2015 Original Android Development] Pranay 7:
I think before CM 14.1 goes official there should be a snapshot of CM13. So after CM13 snapshot is created CM14.1 goes official.
[Moto G 2015 Original Android Development] debopriyobasu:
[MENTION=4912374]rahul9999[/MENTION] [MENTION=6341989]drkhalidomer[/MENTION] the problem is that AudioFX sound effects are directly related to the visualisation effects. If visualisation is off then Audio FX fails to start. When I begin playing music, audio FX doesn't start. When I turn off screen and turn on, the lock screen visualiser starts up and immediately the effects are audible. I suspect Audio FX fails to run in the background when not used for a long time.
[Moto G 2015 Original Android Development] rahul9999:
---------- Post added at 02:50 PM ---------- Previous post was at 02:50 PM ----------

[/COLOR]

Requesting users to stop sharing their thoughts about CM 14.1 release & spamming this post.. When the build is ready Official developer will be share it over here.

---------- Post added at 02:55 PM ---------- Previous post was at 02:50 PM ----------

[MENTION=6614165]debopriyobasu[/MENTION] i'm not a Dev of this ROM, please try to contact [MENTION=4480917]Alberto97[/MENTION]
[Moto G 2015 Original Android Development] IronTechmonkey:
That is not correct. Now that Osprey has gone official for CM14.1, new builds will be posted here https://download.cyanogenmod.org/?device=osprey without necessarily being announced by developer in this thread. IMO it is nice to know through email notification from XDA posts that a particularly important build is ready (and we are on the cusp of first official nightly - an important build). Also we are sharing details about how the CM system works which is good knowledge to spread around. This thread has a nice # of people who are actually checking CM resources and interested in installing Osprey CM14.1 which is good because a larger group of users makes for better tested and more robust ROM.

BTW, The build has completed and is in the posting phase, although the overall list is only up to "kltechnduo" so we may have an hour or 2 to go go (there are 9 builds between kltechnduo and Osprey and the system usualy spits out 4-6 an hour). https://download.cyanogenmod.org/...althuough there are some errors in previous device builds. Fingers crossed.
[Moto G 2015 Original Android Development] rahul9999:
Thanks for the clarification & my bad i was mentioned some wrong information while posting.. :o & also thanks for some important information :highfive::victory:
[Moto G 2015 Original Android Development] Jithin91:
First official Nightly Build of CM14.1 for Moto G 2015 is built successfully and added to getcm.

Will be available to download in a short while --> http://get.cm/?device=osprey

Update: Download is now available on the osprey page.

Here's the direct link --> https://download.cyanogenmod.org/get/jenkins/186980/cm-14.1-20161117-NIGHTLY-osprey.zip
[Moto G 2015 Original Android Development] UltraMaks:
http://get.cm/?device=osprey does not show anything. though the direct link downloads the file )
[Moto G 2015 Original Android Development] Jithin91:
try this -- http://get.cm/?device=osprey&type=

click b/w nightly and all.. you can see.