yashsingh1/xdaforums huggingface dataset:
[One (M9) Q&A, Help & Troubleshooting] bzhmobile:
It's my fault, my most grievous fault.

Not awake, sorry

so

0PJAIMG_HIMA_UHL_M60_SENSE70_HTC_Europe_3.35.401.12_Radio_01.01_U11440792_97.00.51203G_F_release_signed.zip is better :D

thanks to SoLdieR9312 too ;)
[One (M9) Q&A, Help & Troubleshooting] Jwtiyar:
thank you bro , so now i can flash this .zip by OPJAIMG method ? works with S-ON and unlocked?
[One (M9) Q&A, Help & Troubleshooting] Flippy498:
Yes to both. But it's 0PJAIMG.zip not OPJAIMG.zip. ;)
[Samsung Gear S2] andyjp7:
Dear all

I used to have the original samsung gear with 3g, very cool watch and the new one looks amazing. However, I know the 3g version has an embedded e sim, can this be activated and used stand alone in the uk? Does anyone know?

Regards

Andy
[Samsung Gear S2] darekz:
Definitely would work if activated in States and used in Europe but roaming charges would be a killer. I don't know of any European provider supporting esim. Tried mine in Poland (Tmobile version) and it worked.
[Samsung Gear S2] optimummind:
T-Mobile in Poland was able to activate your USA-purchased Gear S2 3G? Which USA carrier model do you own? Or is it from a different country?
[Samsung Gear S2] darekz:
Like I mentioned. Watch was activated in States.
[Samsung Gear S2] optimummind:
Which carrier model? Did the watch have to be unlocked first?
[Samsung Gear S2] darekz:
Tmobile USA version
[Moto X Android Development] Megatron007:
#include

/*
* Your warranty is now void.
*
* We are not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at us for messing up your device, we will laugh at you.
*
*/

First of all i wanna thanks [MENTION=1815755]intervigil[/MENTION] aka Ethan Chen who is currently developing cm13 for our ghost and side by side i am also contributing to CM ...so all should be thankful to him :D

When coming from any other ROM, you must do a factory reset / clean flash.

The first boot can take a very long time. Don't assume that it is a bad flash, boot loop, etc. until it has sat for at least 5 minutes.

Links

ROM: https://download.cyanogenmod.org/?device=ghost

GAPPS: opengapps.org

PROTIP: Be sure to flash gapps at the same time you flash the rom. If you boot into cm-13.0 without gapps and attempt to flash them later, you're going to have a bad time

Working Stuff

SIM

Phone Calls

Text Messaging

Mobile Data

Sensors

WLAN

Bluetooth

Camera

USB / USB-OTG

Doze mode

NFC

Tethering

Known Issues

2G/3G Switch

Video Recording

Flashlight Turns off after few seconds [WIP]

Screencast Doesnt record screen [ Need Updated Media Codecs] [WIP]

At 0% while Charging The Screen gets stuck at bootlogo

Crazy/Inverted Colour While Playing Video Through Instagram

Before posting on this thread, make sure of a few things:

You've utilized the search function of the forums. Nothing irritates me more than lazy people who do not search for an answer before asking.

If you are the only one having a problem. Boot into recovery, wipe data/factory reset, reflash the rom/gapps and nothing else. Boot up and see if the problem persists.

Make sure your post is relevant to this thread. "I'm having problems rooting/unlocking" is NOT relevant here.

LOGS LOGS LOGS!!!! Use this: SysLog by Tortel

XDA:DevDB Information

[ROM][UNOFFICIAL] CyanogenMod 13 For Moto X [12/2/16], ROM for the Moto X

Contributors

Megatron007 , intervigil , [MENTION=5604178]zwliew[/MENTION]

Source Code: https://github.com/CyanogenMod/android_kernel_motorola_ghost

ROM OS Version: 6.0.x Marshmallow

ROM Kernel: Linux 3.4.x

Version Information

Status: Testing

Created 2016-02-12

Last Updated 2016-02-12
[Moto X Android Development] Megatron007:
Thanks to all my tester - Adriano Martins , Atharva Lele , Yacob , Amar Krishna And Many More :D :)
[Moto X Android Development] Megatron007:
Heyya Guys , I wanna thanks [MENTION=5425708]tycoo[/MENTION] for allowing me to post the CM 13/AOSP/MM kernel here

Here is the links - http://romwarehouse.com/megatron007/TycooKernel/

Note its only for CM 13/AOSP/MM

Features - All the features and patches from V1.3,1.2,1.1

ENJOY ,
[Moto X Android Development] akhilnarang:
Great [MENTION=5116201]Megatron007[/MENTION]
[Moto X Android Development] regis88:
Info

Great Work!

What about GPS, Random Reboots and battery life?
[Moto X Android Development] Megatron007:
gps untested till now ,,no random reboots ..battery life is great :)
[Moto X Android Development] lucasmarks1991:
Great Work!!

Great Work!!

Can I use CM12.1 recovery to flash this rom?

Thanks!!
[Moto X Android Development] Megatron007:
yeah :) but do clean flash :)
[Moto X Android Development] hawkdown77:
Screenshots??
[Moto X Android Development] rafatosta:
Congratulations!

How will support the correction of this ROM? Frequency of updates?
[Moto X Android Development] Megatron007:
i will do weeklies till the cm nightlies start :)
[Moto X Android Development] Megatron007:
Added just two :)
[Moto X Android Development] Megatron007:
[MENTION=5425708]tycoo[/MENTION] Waiting To See your MM Kernel :D
[Moto X Android Development] valeron94:
I come from a 4.4.4 stock based rom and I get an infinite boot loop (at the moment 30 minutes and couting) after flashing the rom and gapps all together. I'm using twrp 2.8.7.0 and first I've done a factory reset. Any suggestion or reason because of this?
[Moto X Android Development] dani.galla:
Probably you have to flash first LP.
[Moto X Android Development] cell2011:
Getting force close in google card setting when trying now on tap? Im using pico gapps is that why?
[Moto X Android Development] requiiiem:
[MENTION=5116201]Megatron007[/MENTION] WiFi is wlan? :confused:
[Moto X Android Development] valeron94:
Thank you, it worked! First I restored an old twrp nandroid backup based on cm12.1 and then I flashed this rom and gapps and it works great :D.

This note might help somebody else if added to the main post.
[Moto X Android Development] athulele:
Yup, everything works great over here.

GPS, Mobile Data, Wi-Fi, Bluetooth. Perfectly fine.
[Moto X Android Development] brickhayabusa:
AWESOME

Thinking about last night wifi and bt won't work XD

you're awesome bro.! :b

keep it up good work
[Moto X Android Development] Megatron007:
Screenshot Posted -- http://imgur.com/a/CfEko
[Moto X Android Development] Bomberlt:
Sorry to bother, but can someone confirm that Ambient Display and Google Camera works good?

I saw some complains in this thread and want to be sure. I'm thinking about using this as a daily driver and most important thing for me to have Ambient Display and camera.

P.S. Thanks for quick development guys :)
[Moto X Android Development] Megatron007:
both are working fine here ,
[Moto X Android Development] ThunderBolt_BR:
Just amazing.

CM13 has brought back battey life to our beloved Moto X 2013. Thanks a lot Megatron and Ethan Chen! Now I can finally wait for the next generation of phones with 14/16nm + Fynfet to change my phone.

[]'s
[Moto X Android Development] T-1311:
Finally managed to flash CM13. I don't know why but I needed to delete the first line in the updater-script which checks the model. Then flashing worked fine and booting too.

Works perfect at XT1052 (20160212 and 20160217)
[Moto X Android Development] regisknechtel:
Auto rotate still stop working a few minutes after reboot on my xt1058 :( (clean install, 17/02 build)
[Moto X Android Development] Megatron007:
deleted
[Moto X Android Development] Megatron007:
logs plz
[Moto X Android Development] regisknechtel:
I'm a bit noob about logs, sorry. I kinda know how to use logcat, but how do I get a log of a bug i don't know the exact moment it triggers? When I reboot, it works fine for some minutes. When i pick my phone later, it already stopped working
[Moto X Android Development] maiconjs:
Great Job !

Please, add support to F2FS in /cache to more speed.
[Moto X Android Development] ThunderBolt_BR:
You can use ghost_F2FS_enable_v1 to use cache in F2FS. It works just fine.

I still have the unknown number alert bug after the other side ends a call in today's nightly, but I dirty flashed it on top of yesterday's nightly. Anyone?

Is a clean flash necessary to get rid of this bug?

[]'s
[Moto X Android Development] Ytecob:
The rom work very well thanks you nice joob, but what about xposed I can't found the good version I tried to flash but It's bootloop after
[Moto X Android Development] lucasguanabara1:
Here on my phone appeared the bug "invalid number" when I finished the call.

I've installed the last build (17/02).
[Moto X Android Development] maiconjs:
poxa mano, até o momento os erros que vi foram em relação ao GAPPS, toda vez que faço o flash me surge a tela com vários force close. Sobre o F2FS vou testar aqui. Obrigado pela dica :D
[Moto X Android Development] Megatron007:
sorry , for me it didnt occured for 1-2 time now its occuring ...will look at one more time :)
[Moto X Android Development] ThunderBolt_BR:
Don't write in portuguese here at XDA: it is against the rules...

You must flash the Gapps package right after flashing the ROM to avoid SELinux erros after the first boot. I use Opengapp's pico package without issues. CM13 is quickly becoming the best ROM for our device.

Thanks again Devs!

[]'s
[Moto X Android Development] p4df:
Thank you for great update.

but i couldn't update to 0217 from 0212.

got script error when update on TWPR.

tried to erase first line on script file as mentioned other post, but still no luck.

any solution?
[Moto X Android Development] joshhjsj:
What about random shut down...... I am experiencing it after doing some heavy stuff like steaming on Netflix...... High quality videos
[Moto X Android Development] kkkarl:
works great for me, thanks megatron007.

today i'm gonna test the snapdragon camera since it is the area i am interested the most.

Again, thanks megatron007, great work, greetz from italy
[Moto X Android Development] simar404:
You have to delete the following text from updater script exactly nothing more or less:

assert(getprop("ro.product.device") == "xt1052" || getprop("ro.build.product") == "xt1052" || getprop("ro.product.device") == "ghost" || getprop("ro.build.product") == "ghost" || getprop("ro.product.device") == "xt1053" || getprop("ro.build.product") == "xt1053" || getprop("ro.product.device") == "ghost_retail" || getprop("ro.build.product") == "ghost_retail" || getprop("ro.product.device") == "xt1055" || getprop("ro.build.product") == "xt1055" || getprop("ro.product.device") == "ghost_usc" || getprop("ro.build.product") == "ghost_usc" || getprop("ro.product.device") == "xt1056" || getprop("ro.build.product") == "xt1056" || getprop("ro.product.device") == "ghost_sprint" || getprop("ro.build.product") == "ghost_sprint" || getprop("ro.product.device") == "xt1058" || getprop("ro.build.product") == "xt1058" || getprop("ro.product.device") == "ghost_att" || getprop("ro.build.product") == "ghost_att" || getprop("ro.product.device") == "ghost_rcica" || getprop("ro.build.product") == "ghost_rcica" || getprop("ro.product.device") == "xt1060" || getprop("ro.build.product") == "xt1060" || getprop("ro.product.device") == "ghost_verizon" || getprop("ro.build.product") == "ghost_verizon" || abort("This package is for device: xt1052,ghost,xt1053,ghost_retail,xt1055,ghost_usc,xt1056,ghost_sprint,xt1058,ghost_att,ghost_rcica,xt1060,ghost_verizon; this device is " + getprop("ro.product.device") + "."););

Or u can download the script which i attached below its already edited:

https://docs.google.com/uc?id=0B9wMp0pyS11uVjZldzFUbG10YnM&export=download
[Moto X Android Development] abacate123:
I'm in this build and everything is fine over here, apk installing without any issues.
[Moto X Android Development] flyers00:
Everything is working fine here. Did you change setting for unknown sources? Think its under security. Good luck
[Moto X Android Development] vinay.ryder13:
I feel that RAM management is bad in the build. its forcing me to clear the memory manually using a third party app.

Any idea how to fix bluetooth? It automatically turns on after switching it off.
[Moto X Android Development] CsR0501:
Ok... I'm gonna re-download the ROM and I'm gonna try a clean flash...

Thanks for your help...

Enviado desde mi Moto X mediante Tapatalk
[Moto X Android Development] ph0b0z:
"Same" here, i don't want to complain and be ungrateful but i went back to OctOS for now. With the nightlies i had very severe slowdowns and lags that i can't really pin down to a specific app or reason, apart from background App-updates, for example, which render the phone more or less unusable. :/
[Moto X Android Development] riyosakura:
Im not experiencing any of it. The phone is snappy and have a very good power consumption.

You dont need any third party app for RAM management, such as clean master, etc. It just make thing worse.

Bluetooth is working very good.
[Moto X Android Development] vinay.ryder13:
I am using third-party because the phone is starting to lag after opening few apps.

And regarding bluetooth, the issue I mentioned is persistant. Even after I switch off bluetooth for the first time, it stays connected and switches back on automatically after 5-10seconds. ill have had to switch it off again to fully turn it off.
[Moto X Android Development] riyosakura:
Maybe you install too many apps?

I have about 50 apps installed, it does decrease performance a little if compare to fresh cm install. But it not much and still snappy to use.

Too many apps start on boot and running in the background may cause performance decrease.

Regarding bluetooth, ive never got such a problem since using cm13 from unofficial version. Now, everything is just improve in term of performance, etc.

The only bug is video recording noise. Or loudspeaker if you turn mic to analog, other than that, i dont see any bugs. You'll suffer much performance decrease if turning on multi window feature though and cm has mention it, it still an experimental feature on cm13.
[Moto X Android Development] vinay.ryder13:
I removed all social apps suspecting foul play in slowing the phone. but it still lags, and no, multi-window mode is not turned on for me. I've not tried anything experimental.

Why haven't there been any releases since 15th??
[Moto X Android Development] sharukins:
simply because new nightlies are only build if there are any changes in the code that affect the specific device. see https://www.cmxlog.com/13/ghost/ for moto x changes and builds

and there haven't been any changes regarding RAM management in ages for CM-13.0. So I assume you should probably do a clean install and see if the problem persists
[Moto X Android Development] vinay.ryder13:
that question was a seperates thing. m curious on why there have been no releases
[Moto X Android Development] sharukins:
but it boils down to the same thing, on cmxlog you can check if a problem might be related to a certain commit in the code or if it's your setup where things go wrong.

and you can see if there are any changes that require a new build ;)
[Moto X Android Development] aledex:
Funny thing is, I remember that audio recording was just fine with old CM13 versions (like from last June). What happened?
[Moto X Android Development] Ryuller_br:
Also I'm the same audio noise problem ...
[Moto X Android Development] Start77:
hi, i installed the CyanogenMod 13 on my moto x with gapps mini, but when i incoming a call the phone reeboot, both numbers that contacts!!!! Help me!!!!

And I would like to remove the google now launcher with che google search bar and set the standard launcher of cyanogenmod....what is the procedure to be done?

thank you
[Moto X Android Development] simar404:
[MENTION=5116201]Megatron007[/MENTION] Hey bro any news of cm14?
[Moto X Android Development] _Morfic_:
When flashing gapps, you can either use the aroma package installer or manually set up the features that you'd want installed/kept through the gapps config file. Basic example:

- exclude the google now launcher

Exclude
GoogleNow

- exclude both search and google now launcher

Exclude
Search
[Moto X Android Development] Start77:
OK, i've solved:

I installato the Ron and the pico gapps, calls working e launchee is OK.

But now the GPS not working!!

Do you havw solution for fix?
[Moto X Android Development] aledex:
Yup, from fastboot

fastboot erase modemst1
fastboot erase modemst2

Firt boot could take awhile / reboot by itself.
[Moto X Android Development] Start77:
but the command in bootloader mode???
[Moto X Android Development] aledex:
I'm sorry I do not understand what you mean.

You have to boot in bootloader, then enter the commands from a pc shell.

Follow this guide if you have problems http://www.teamandroid.com/2015/01/08/enter-moto-x-fastboot-mode/
[Moto X Android Development] vinay.ryder13:
An horrendous issue - when the phone is connected to a headset through bluetooth, it's getting hanged whenever I get a call. There is no response from the screen whatsoever. and after a restart the call log is registering the call I missed
[Moto X Android Development] _Morfic_:
Yes, run them in bootloader mode.

Yeah, that's my biggest problem so far as well, and it seems to be CM wide, not only for our handset. Or perhaps it used to affect multiple devices and some of them got fixed, but I wasn't able to find any decent/relevant information after looking around for a couple of hours so I temporarily stopped searching.

As I was saying in that linked comment, in the BT settings for the paired device you can disable "media audio" and you can have regular calls, but you won't be able to play music. While it can't be considered a fix, this workaround allows you to keep using CM if you want to...
[Moto X Android Development] 690sid:
Free Unlimited Storage

Guy, the craziest thing just happened.

I have CM13 + Xposed + N-ify and this is what google photos is telling me
[Moto X Android Development] abacate123:
Well, android nify is known now to camouflage your build prop as a pixel phone for activating the new pixel Google assistant on the Google app for lower Android versions and other phones and roms, so this should be only a feature consequent due to this "pixel phone camouflage". So there's nothing amazing nor crazy in there since unlimited Google photo sync backup is a pixel thing.
[Moto X Android Development] sharukins:
and google will probably soon take counter measures, cause you didn't pay for this as you didn't buy a pixel
[Moto X Android Development] abacate123:
Nah, android is open source don't forget this. Google has the rights towards their own apps, but since the changes are not made inside the app itself it has been made as a build prop camouflage, so the app thinks the phone you have is another one. Google may take down this method as soon as possible. But that's the only thing they will do, take down the method. It's not user's fault if an application has a breach to be explored.
[Moto X Android Development] sharukins:
that's basically what I just said, just in more detail :p

I won't discuss the legal stuff about this, as I'm not an expert but I'm pretty sure a user who activley installs Xposed and N-ify can be thought of as a person with technical knowledge about what he is doing there. Therefore some courts might be of the opinion he "betrayed" google on purpose to get unlimited storage (this also highly depends on your country and the local laws there). But this will probably never happen, google will find some technical way to lock out users who don't own a Pixel.
[Moto X Android Development] toehser:
2 bugs: bluetooth audio+phone profile; home wifi becomes stuck "broken" after days.

2 bugs: #1: phone reboots if bluetooth both media and phone active.

I can reproduce that with latest nightly, I can have bluetooth media-only or phone-only with no problems, but the phone freezes then reboots itself if both profiles are active and I use the bluetooth for phone calls.

2 bugs: #2: After a few days, home wifi won't connect.

From a clean install of nightly, after a few days, my home wifi network becomes "constant failure".

All other phones / computers work with it, including CM12.1 on the same phone. Only CM13 fails.

The CM13 phone works with _other_ wifi networks - but it "decides" not to work with my home network.

It works _at first_ - during setup and for a day or two - but then gets "stuck broken".

The home network has 2 routers both running openwrt, fwiw.
[Moto X Android Development] abacate123:
Have no such issues with cm13, have you tried a clean install already? Or cleaning cache and dalvik cache.
[Moto X Android Development] toehser:
Yes all and more multiple times.

CM12: both issues don't happen.

CM13: both issues do happen.

The wifi one is a MUCH bigger problem. Bluetooth, I can just go in settings and turn off 'media' when I'm using it as a phone, and turn off 'phone' when I'm using it for media, I can tolerate that.

The wifi problem is killing me- after a few days from clean install, it just "refuses" to connect to my home network anymore.

Sequence:

CM13 install. Use the home network for the initial restore of apps from google etc.

Home network works fine at first.

After a couple of days, though, the home network shows 'saved' but refuses to connect.

Other networks continue to work fine from the phone.

Other phones continue to work fine with the home network.

Wiping and reinstalling cm13 fixes it... for a couple of days.

Reproduced and repeated several times now.

CM12 does NOT show this problem.

Sigh.
[Moto X Android Development] riyosakura:
It strange if it only doesnt work with your home network.

Have you tried to forget the network when it doesnt work anymore?

I dont have the wifi problem. Only the bluetooth problem.
[Moto X Android Development] danielcr12:
This is odd I don't have any of those issues, my setup is pretty flawless and bug free
[Moto X Android Development] toehser:
Yes, I've tried everything like forgetting, turning wifi off and on - I think there must be _something_ about the wifi network that it doesn't play well with. It is a 2.4 OpenWrt network with one Asus router and one Buffalo router, both configured by me with OpenWrt. All other phones work fine. Once it "goes south", it won't come back.

And, it is weird that it works for a day or two before it "starts refusing to connect".

Right now, I'm back to Lollipop... But I'm glad to go back to CM13 if there are any tests / logs I can contribute.

On 12.1-20160822-NIGHTLY, it "just works fine"...

On 13.0-20161022-NIGHTLY, it "works for a day or two, then refuses to connect to that network ever again".
[Moto X Android Development] govardhan87:
Can some one reply please,

What are the dormant bands available in LTE of xt 1053 ..

2 4 17 are enabled by default.

I need either 3 or 5 or 40 .

From searching xda I got that if 2 ,4, 17 are enabled then the set of frequencies that are possible are 1, 2,4,5 ,8,12,17

Can cyanogen mod 13 contain modem files to enable band 5 lte ?

LTE available here in my area is 3,5,40 alone.
[Moto X Android Development] tycoo:
Like to share the Kernel with the fix for the "Dirty Cow" vulnerability http://www.xda-developers.com/9-yea...-dirty-cow-can-root-every-version-of-android/ here too.

No mods or tweaks, pure cm-13.0 stock kernel branch but with all updates from Linux until 3.4.113 included.

Download at my mm_x_kernel thread: http://xdaforums.com/devdb/project/dl/?id=21168

Source Code: https://github.com/tycoo/moto_x_kernel/commits/cm-13.0_stock+3.4.113
[Moto X Android Development] halomademeapc:
Hi all.

On the moto x with this rom, incoming calls go onto speakerphone and the speaker toggle in the call ui does nothing. Outbound calls behave normally. I'm thinking this might have something to do with car mode (on stock lollipop the device always thought it was in car mode for some reason) If anybody can provide insight into this, I'd greatly appreciate it.
[Moto X Android Development] vinay.ryder13:
updated apn settings in 27-10-2016 update ****ed up internet connectivity again