yashsingh1/xdaforums huggingface dataset:
[Moto G 2015 Original Android Development] tazlooney89:
Stuck on boot too, (xt1540) with nightly cm-13.0-20161113 :( return to cm-13.0-20161107
[Moto G 2015 Original Android Development] swordfish:
Guys are you updating through CM OTA Updater or manually flashing?
[Moto G 2015 Original Android Development] Anandabasak:
Bith tried.....via cm updater as well ad clean flash via twrp manually plus i lost all data during clean flash
[Moto G 2015 Original Android Development] mikib1:
11.13. stuck on bootlogo

I have the same , I think this update is broken...

I tried both way (OTA and via teamwin) still boot logo stuck

I"m Waiting for next update, I also went back to 11.07.
[Moto G 2015 Original Android Development] Rammar515:
[MENTION=4480917]Alberto97[/MENTION]

Why don't we move to weekly cm13 instead of canceling it?
[Moto G 2015 Original Android Development] Casper1982:
Whatttt?

What happened here...

https://www.cmxlog.com/13/osprey/
[Moto G 2015 Original Android Development] Gravemind2015:
New changelogs will be here - https://www.cmxlog.com/14.1/osprey/# once nightlies start to roll out.

Broadcasted from Zeta Reticuli
[Moto G 2015 Original Android Development] Cinyk:
Anyone know how to get xposed working on this ? I tried flashing xposed-v79-sdk23-arm.zip and xposed-v86-sdk23-arm.zip and xposed wasn't on my device after reboot :/
[Moto G 2015 Original Android Development] Gravemind2015:
Did the TWRP install go fine? Go to xposed installer>framework and check if xposed is active.

Edit : In case you missed, you need to install Xposed installer from here - *Note - Did you actually installed the xposed installer apk from here http://xdaforums.com/showthread.php?t=3034811, the flashable zip doesn't include it.

Broadcasted from Zeta Reticuli
[Moto G 2015 Original Android Development] HelpMeruth:
no more cm13 nightlies, cm14.1 all the way :)
[Moto G 2015 Original Android Development] Cinyk:
Ooh ! Did not realise it wouldn't install the Apk :P

Thanks a lot :)
[Moto G 2015 Original Android Development] accforfree:
Last cm13 build

Hello [MENTION=4480917]Alberto97[/MENTION]

Could you give us last booting build of cm13? It would be nice to have last cm13 (with november security patches) before cm14.1 will become as advanced as cm13.

(or some weekly/monthly builds?)

Thank you.
[Moto G 2015 Original Android Development] Alberto97:
CM policy. If you have one you can't get two. I guess they do in this way to prevent an infinite build queue. That would be even possible for now, but later when more devices will be supported by cm-14.1 you would get a build per week when it should be daily.

Is the today's one still having issues while booting?
[Moto G 2015 Original Android Development] EsromTech:
[MENTION=4480917]Alberto97[/MENTION]

I fully agree with you!

I would like to know if we will have the cm13 with branch stable when it exists?

I'm using the compiled version of cm13 today (20161114), it works perfectly. [MENTION=4480917]Alberto97[/MENTION]

I noticed a commit that said something about NotificationManager and lights, can you explain what it was?
[Moto G 2015 Original Android Development] juanpm77:
I've an error with file manager, it crash when i try to open, any solution? thanks !!
[Moto G 2015 Original Android Development] novy0:
V. 20161114 work with xposed? Didn't boot when I install xposed
[Moto G 2015 Original Android Development] Gravemind2015:
Xposed isn't released for Nougat 7.x yet. Here is the official announcement thread - http://xdaforums.com/showthread.php?t=3034811

Apologizes. I thought I was in the CM 14 thread. May be november security patch broke it as [MENTION=7316748]vicky90[/MENTION] said.

Broadcasted from Zeta Reticuli
[Moto G 2015 Original Android Development] novy0:
I install xposed on cm13 v. 20161114
[Moto G 2015 Original Android Development] vicky90:
May be it's related to November security patch update, I'm getting same error.
[Moto G 2015 Original Android Development] EsromTech:
I am using xposed in build 20161114, it works normal, I had problems only with the greenify module.

EDIT:

I withdraw what I said, in fact the xposed is starting with the rom normally but I can not activate any module, I believe it is something with the new security patch maybe ....

After activating the modules below all caused bootlop:

Xuimod

QS x Tile

Greenify.
[Moto G 2015 Original Android Development] kr428:
Not here. Can't activate xposed. First flash (ROM, xposed, supersu) ended up in xposed complaining that some modules aren't enabled, which, in the Xposed installer, turned out to be xposed not available at all. Flashing xposed again ended up in the device not booting anymore (and me reverting from 1114 to 1107 again... ;) ).
[Moto G 2015 Original Android Development] EsromTech:
You're correct, maybe my bad English might have disrupted the understanding of what I said.

I said just that. Not working xposed on this new build, the reason is the new security patch.

I already went to the xposed sector here in xda, I found everyone with the same problem and the developers are making the solution for this.
[Moto G 2015 Original Android Development] kr428:
Ahh ok - thanks. Then indeed I just got you wrong - obrigado! :)

K.
[Moto G 2015 Original Android Development] Alberto97:
I have no idea if there will be other cm13 snapshots, I don't think so.

I can't remember such commit, link it and I'll tell you.

Inviato dal mio XT1635-02 utilizzando Tapatalk
[Moto G 2015 Original Android Development] EsromTech:
But would not it be important to have a stable build on the cyanogenmod server?

[MENTION=4480917]Alberto97[/MENTION]

Sorry for not informing you before, I was talking about these commits, could you help us by saying what is it?

lights: Use NotificationManager to figure out LED capabilities (android_packages_apps_Settings)

NotificationManager: Concentrate LED light capabilities at a single location (android_frameworks_base)
[Moto G 2015 Original Android Development] Checon56:
I think I will jump to CM 14
[Moto G 2015 Original Android Development] kr428:
Same here - but only as soon as CM14 has theming engine and the Swift Dark theme has been updated to work with it. ;)
[Moto G 2015 Original Android Development] jason9088:
Does this rom supports Volte...???
[Moto G 2015 Original Android Development] IronTechmonkey:
Derp, wrong thread. Apologies. Post content deleted.

But still... [MENTION=5823021]jason9088[/MENTION]...searching for answers is an expectation and in fact is an XDA rule;) A search for the term 'volte" yields over 50 results in this thread alone.
[Moto G 2015 Original Android Development] sakshay1997:
please first seach before asking such questions answered many times already
[Moto G 2015 Original Android Development] neodrabi:
Try last Nightly

I had the same issue even with clean install of the same nightly, dirty flash 11/14 fixed it, if not, try clean install
[Moto G 2015 Original Android Development] WaxysDargle:
lol one post EVER and it's a VoLTE question.

priceless.
[Moto G 2015 Original Android Development] adrianogoes:
Hi.

I'm having trouble to boot into the new NIGHTLY (20161114) after flash Xposed.

Anyone?
[Moto G 2015 Original Android Development] kr428:
Same here. Doesn't boot.
[Moto G 2015 Original Android Development] EsromTech:
The security patch for the month of November has caused this error to occur. It will not be any good to ask for correction for cm13 to work xposed, this will start from the developer xposed to work around the situation, it is impossible for cyanogemod not to use the security patch just so we can use xposed.

Use a previous build if you want xposed, it will work fine.
[Moto G 2015 Original Android Development] kr428:
Yes I know, thought it got fixed. Hmmm I actually just use Xposed anymore for greenify; would be sad to have to give up on that as long as there is no viable alternative...
[Moto G 2015 Original Android Development] Alberto97:
Devices must be device-specific issues free to get snapshots. People were having issues with GPS those days and secondly I did not get any notification about stable builds had to get out.

They tried to get rid of many overlays in favor of just one but they apparently have broken the logic around config_ledCanPulse which we set as false (while with the new logic it can be only true) on osprey. If I'm right in the latest nightlies you should be able to see a "new option" under the battery light settings called "Pulse if low battery" which doesn't work for us and it was hidden if config_ledCanPulse = false.
[Moto G 2015 Original Android Development] EsromTech:
[MENTION=4480917]Alberto97[/MENTION],

Forgive those unoccupied people who post frequently asked questions for no reason, I really would like to help with this.

Unfortunately for these people, we who want to help in development will be blocked for this, (I applied for RC but still no response).

I hope I can help in any way.

I'm using your official build and am getting ready to post a technical comment about rom.
[Moto G 2015 Original Android Development] acejavelin:
Dumb question... What are using the Xposed Greenify module on that can't be done without it? Every time I Greenify system services it causes instability or bugs.
[Moto G 2015 Original Android Development] EsromTech:
I could sometimes go through the previous pages where I and some others talked about xposed, I would like to make it clear once again and if the users collaborate I hope it is the last time.

Xposed is not being supported by current cm13 builds because of the November security patch, instability should be questioned or circumvented by the xposed developer. Cyanogen has nothing with xposed.

What's more, xposed is not a type of application suggested by the developer, so its use should not be handled in this thread.

use here - Support Xposed in XDA
[Moto G 2015 Original Android Development] kr428:
Hmmm. Why so offensive? I take as granted that devs don't suggest using xposed. Fine. I'm not complaining or asking for support - I'm just looking how to replace a solution that worked *pretty well* for me (closed+greenify) on a system that doesn't work with xposed anymore...
[Moto G 2015 Original Android Development] acejavelin:
That wasn't really question...

I haven't used Xposed since KitKat, and likely never will again... I was wondering what people are trying to Greenify with Xposed, because only system services require that method.
[Moto G 2015 Original Android Development] Checon56:
You did somenting wrong. 1114 working perfect here

Edit: Sorry, I did not tested Xposed
[Moto G 2015 Original Android Development] acejavelin:
How was that question offensive, it was just simple curiosity...

My issues with Xposed are hardly secret, after working on a few rom development teams and seeing the results of it I have some strong negative feelings about Xposed and what it does. Yet I respect the developers and what they have done for the Android community. All that said, I made no mention of that I my question.
[Moto G 2015 Original Android Development] EsromTech:
Do not have an offensive person here, we are just guiding you about, we just want to be helpful.

I really understand you. :)
[Moto G 2015 Original Android Development] kr428:
Sorry, maybe I got your 'dumb question' comment the wrong way then. Greatly appreciate your support and work guys.
[Moto G 2015 Original Android Development] acejavelin:
LOL... Yeah... I was meaning MY question might be dumb. It's all good, no worries.
[Moto G 2015 Original Android Development] Checon56:
Did you mean hacking apps?
[Moto G 2015 Original Android Development] kr428:
Ok then. ;)

Cheers,

K.
[Moto G 2015 Original Android Development] acejavelin:
No, not specifically, those are bad for other reasons... With how it works, It messes with the framework and can seriously ruin a custom ROM, which uses its own custom framework already, and updates and security patches, as we have seen repeatedly, can render a device unusable. Not because of the update, but because of Xposed. It is designed for purely stock devices, not any implementation that has modified framework, like CM and almost all custom roms.

Xposed will die soon, if not with Nougat, then the next Android version or two, because of how Android is designed and how security is being tightened down. The fact it works on Marshmallow is a pure fluke, the developers of it almost dropped it last year thinking they could never get it to work, but a shear accident found a way and have clearly stated that may not be an option going forward.
[Moto G 2015 Original Android Development] kr428:
Is there any way to achieve things like blocking apps from reading my phone provider or Google account data without using Xposed? I never gave much on most of the modules available for Xposed but actually greenify and xprivacy surely had some value, and even the 6+ permission settings leave out a few interesting aspects....
[Moto G 2015 Original Android Development] acejavelin:
Unfortunately no there isn't... But I would suggest getting used to it or doing away with Google Services entirely, the current Marshmallow permissions are not getting better with Nougat, and will the granularity will just get worse going forward. I recommend this only because Xposed will die, maybe not with this android, but before too long.
[Moto G 2015 Original Android Development] EsromTech:
Announcement

Just for the useful information of cm13 users, as many are known to be doing repetitive questions about xposed, I beg you to look at that thread.

[ANNOUNCEMENT] CM Bootloop Issues and XPosed with Early November CM Releases

As has been said, this will not be fixed by the CyanogenMod team, will be circumvented by the Xposed development team.
[Moto G 2015 Original Android Development] kr428:
Not nice. But thanks nevertheless... :(

K.
[Moto G 2015 Original Android Development] acejavelin:
I'm too old to sugar coat it... When I say Xposed will die, it's mostly not opinion, the developers have stated it can't continue forever as Android tightens it's permissions with each version, it'd harder and harder to keep it working. Just like chainfire's has stated about root, Google could shutdown root or Xposed on a whim, even he says it's only a matter of time.
[Moto G 2015 Original Android Development] ehbm:
XT1543 dual-sim from Brazil, unbranded and unlocked. Tried RR rom, pacman and same problem. My simcards arent recognized. Works just on stock Rom.
[Moto G 2015 Original Android Development] ChinmayKunkikar:
[MENTION=4480917]Alberto97[/MENTION]

I'm using the build for a week now.

Almost bug free build leaving the CM bugs.

One thing is that I'm noticing a huge battery drainage and the doze mode doesn't seem to work.

(XT1550)
[Moto G 2015 Original Android Development] dhk.-:
[MENTION=7019930]diegodamohill[/MENTION] can you help us? What xt1543 do you have? 8/1gb o 16/2gb? And what baseband do you have?

Enviado desde mi MotoG3 mediante Tapatalk
[Moto G 2015 Original Android Development] Alberto97:
A new build is out. Custom kernels need an update due to some WLAN changes (see the second post) so you can't install them for now else you'll lose the WiFi functionality. About CDMA Virgin Mobile, I've made some changes to the apn list, please report if everything is fine out of the box now :)

Just another thing, we're doing a common device tree for Moto E 2015 LTE (surnia), Moto X Play (lux) and for our Moto G 2015 (osprey) so official builds won't come before this unification. You can follow our work here.
[Moto G 2015 Original Android Development] JoshinPl:
And how can you made the unification with lux? There are other soc than osprey/surnia

Enviado desde mi MotoG3 mediante Tapatalk
[Moto G 2015 Original Android Development] xclusive36:
For Virgin Mobile, after first boot, It does not show cell or data. Once I switch to LTE from Global, I'm only able to receive 3g. No LTE.

When I bring up phone testing *#*#4636#*#* it is correctly set to LTE/CDMA auto (PRL). RUIM/SIM is also set by default.

The only issue I see is that the APN is not being set. I can send and receive phone calls with no issue so i'm happy with that. Keep up the good work, Your making great progress. Thank you
[Moto G 2015 Original Android Development] hossman:
Same exact result on virgin xt1548
[Moto G 2015 Original Android Development] str8killinya:
Are these the correct named gapps I should be using

arm 6.0 pico 13 December 2015

Thanks just want to make sure I get the right ones

Sent From My PacMan Powered Moto G 2015
[Moto G 2015 Original Android Development] diegodamohill:
Here's a capture of my moto g, i have The 2gb/16gb Brasil retail version
[Moto G 2015 Original Android Development] ehbm:
Wich GAPPs do you recommend?
[Moto G 2015 Original Android Development] Setialpha:
I'm using the latest opengapps and no more setupwizard fc.

Gesendet von meinem MotoG3 mit Tapatalk

---------- Post added at 07:26 AM ---------- Previous post was at 07:20 AM ----------

@Alberto97 great work, almost perfect. Only problem so far is, that themes do not properly apply.

GApps and Setupwizard no more fc out of the box, LTE aswell.

Gesendet von meinem MotoG3 mit Tapatalk
[Moto G 2015 Original Android Development] ehbm:
I just installed the ROM but it does not recognize my sim slots = (

Did a clean install, why is it that this is happening with all custom ROMs here at Moto G3? Only with stock Rom my two simcards slots works perfectly.
[Moto G 2015 Original Android Development] SirSoviet:
What model is your phone?
[Moto G 2015 Original Android Development] DarkElf:
Guyss i am getting a strange issue...sometimes my wifi automatically switches off then again reconnects...any workaroud for it?? Facing it when updated to latest build...thanks
[Moto G 2015 Original Android Development] valkaizer2594:
is facebook and snapchat working in the latest build?
[Moto G 2015 Original Android Development] rcaliman:
Wonderful. So far everything running smooth and error-free in this latest version. Congratulations Alberto. You are great.
[Moto G 2015 Original Android Development] dhk.-:
I think that only the xt1543 1gb/16gb are having problems with no sim being recognized by any custom rom. Is there somebody with this variant not facing this problem?

Enviado desde mi MotoG3 mediante Tapatalk

---------- Post added at 08:14 AM ---------- Previous post was at 08:08 AM ----------

He and I own xt1543 1gb/16gb

Enviado desde mi MotoG3 mediante Tapatalk
[Moto G 2015 Original Android Development] SirSoviet:
Tried both Blu Spark and Squid kernel, both had Wi-Fi not working. Blu Spark probably isn't going to be updated any further, and we'll just have to wait for Squid to release a compatibility fix build unfortunately :(
[Moto G 2015 Original Android Development] vandermark:
Why did you try when Alberto allready mentioned this in the change-log?
[Moto G 2015 Original Android Development] SirSoviet:
Looks like I'm too lazy to read. Thanks for pointing that out to me!
[Moto G 2015 Original Android Development] kr428:
No need to sugar-coat. I actually see that coming for Xposed. But root, in custom ROMs, as long as there is AOSP and people buying phones that can be unlocked 'officially' without hacking them? Generally still I'd prefer a device on which I would need neither root nor Xposed, for that matter...

All along the lines, after going without xposed for a day, the only thing I really miss is applications that are 'hibernated' being woken up in case of cloud notifications...
[Moto G 2015 Original Android Development] IronTechmonkey:
Very good points in your last few posts about Xposed, particularly the deep level at which it lives in the system. In terms of CM ROM testing and reporting Xposed has been a nightmare, although though no fault of its own. The availability of Xposed allows less knowledgeable device users to make changes deeper in the system without understanding the ramifications of those changes... and then report issues here as if from a clean ROM. Most of the false positive bug reports I've seen in XDA CM threads turn out to be caused by Xposed and reported by users that dont understand.

LOL I was about to apologize for going off topic but is it really off topic to remind people not to report bugs from devices running Xposed?
[Moto G 2015 Original Android Development] acejavelin:
No... It's not off topic, and should be common sense and in every single rom thread 1st post. Xposed + custom rom equals you're on your own, from the developers perspective at least. Any question/problem/bug on a rom where the user has Xposed should be ignored.
[Moto G 2015 Original Android Development] kr428:
Though maybe off topic here: I got into both custom ROMs and xposed by trying to figure out how to keep at least a slight level of control over my data on Android 4.0. Back then, the only real viable solution I ended up with was xprivacy which in turns required xposed so I went down that route, also at least initially totally unaware of what I was doing.

Reading through what xposed actually does and how it works later on, I felt slightly dizzy; from a security point of view this seems a mess, and the fact that it obviously does this by exploiting various Android flaws doesn't make it better. However I guess xposed, in the end, is something a load of people end up with as the only solution to fairly valid desires (leaving the GPS hacks for Pokémon Go aside for a moment), and these aren't necessarily deep into understanding how these things *actually* work. I don't think this is good or desirable, but somehow I understand why it is the way it is.... :(
[Moto G 2015 Original Android Development] veloz46:
Hello [MENTION=4480917]Alberto97[/MENTION] , will there be a snapshot version?

Enviado desde mi MotoG3 mediante Tapatalk
[Moto G 2015 Original Android Development] accforfree:
No.

Mods, please lock also this thread. Spammers just gotta spam.
[Moto G 2015 Original Android Development] veloz46:
Relax, my friend, relax a little.

Here spam is clear what it is, this is a question of whether there will be development for a SS or not, I have talked several times with Alberto, even helped me to compile some Rom, and I have shared CM12.1 updated to date ( http://xdaforums.com/2015-moto-g/orig-development/rom-cyanogenmod-12-1-moto-g-3rd-gen-t3386367 )( Which is no longer officially updated) I simply want to know if support will be given to SS or I start compiling CM13 by myself and being able to share with the community.

But with people like you one you end up wanting to share anything.

Attack relentlessly on spam, and do not create a member of the law with powers.

Greetings and discuss this comment.

Thanks for your attention.
[Moto G 2015 Original Android Development] IronTechmonkey:
Welcome to XDA. Your post is no better. Try being productive. Closing the thread, as happened with Osprey CM14.1 thread, is OP/developer's prerogative and can provide him with a welcome break but make no mistake, doing that disproportionately punishes thread regulars who would self police the thread by setting good example, and does not inform the hit and run users because,,, they are hit and run users. I have no complaint about that thread being closed because I respect the developer's decision but let us be realistic about what that really achieves and not throw that suggestion around so easily.

---------- Post added at 03:05 PM ---------- Previous post was at 02:59 PM ----------

DERP stricken out. Proper response here http://xdaforums.com/showpost.php?p=69701707&postcount=2992

Asking for ETAs is considered inappropriate in developer threads. Just dont do it in spite of the temptation. There are other ways to get that information such as searching for on-line CM and XDA resources or sending a PM to other XDA member (not the developer!). EDIT removed comment only applicable to CM14.1 Also, consider that we just started getting official nightlys and at this point would not know when the ROM will be polished enough for a snapshot.

---------- Post added at 03:12 PM ---------- Previous post was at 03:05 PM ----------

Yep, It's a useful utility that can do things that cannot be otherwise done but should be kept in a separate space from ROM testing/bug reporting.