yashsingh1/xdaforums huggingface dataset:
[Moto X Android Development] se1961:
I did some searching, and found this exact behavior described in a thread about CM13 in the Cyanogenmod forums. The workaround they suggested was to only enable media OR phone in the device settings, but not both. I unchecked "media" and I'm now able to make BT phone calls perfectly. This works much better for me than turning Bluetooth off to make a call, because I make many handsfree calls using Bluetooth. Might not work for everyone, but I'm thrilled with this solution. :D

And I believe I forgot to say a big thank you to the developers for this ROM and Tycoo Kernel. I was getting 5-6 HOURS of battery on stock KitKat, and I'm now back to a good day and a half off the charger. :good::good:
[Moto X Android Development] rc125:
The issue is the current build of gapps - quick workaround is to manually set the Phone/Dialer app as the default Phone App in Settings -> Apps -> Gear Icon on the top -> Default Apps -> Phone App.
[Moto X Android Development] alex37v:
A lot of thanks to developers.

About this BT problem. Some one knows if ResurrectionRemix or OctOS (based on cm13 too) have the same problem?

Regards.
[Moto X Android Development] mafri2:
Yes, they have!
[Moto X Android Development] Megatron007:
http://romwarehouse.com/megatron007/test/

New Build , cmactions ported to moto x if anyone willing to test it , can go forward and report bugs here
[Moto X Android Development] h1ghland3r:
I'll be flashing today. Thanks!
[Moto X Android Development] omy4069:
what is cm action??
[Moto X Android Development] Megatron007:
Cmactions is same as motodoze ,
[Moto X Android Development] omy4069:
aaa oey thanks broo, this is my gmail

emapeye@gmail.com contact with me to work send pf the ghost device please
[Moto X Android Development] lucasguanabara1:
CMactions doesn't working here, always shows the message "CMActions stopped''
[Moto X Android Development] Megatron007:
arr..
[Moto X Android Development] Megatron007:
Thanks man , Sending ..
[Moto X Android Development] h1ghland3r:
Having 'CMActions has stopped all' the time.

Flashing 04.16 again. =(
[Moto X Android Development] hawkdown77:
Last stable version is 22/03/2016??
[Moto X Android Development] dsiva:
Hey guys,

I have a huge problem here. Please give me an idea if you could see the problem I am having.

Issue: I had installed Megatron's CM12 ROM before I decided to upgrade to CM13 recently.I had CM13 working fine until I restarted the phone after installing some apps, at which point the SystemUI started crashing even if I rebooted several times. Then I reflashed the ROM, but the device went to Bootloop. After I do a clean install, It says "Optimizing X apps of 65" and finishes all the apps but then starts the whole process again. I have been trying to get my phone back by flashing and reflashing CM12 and CM13, with and without GAPPS, but the situation persists.

What I am thinking is that, doing a Factory Reset doesn't actually erase the partitions. If not from where does that 65 apps come even after doing several factory resets.

Constraints:

-My USB is damaged -- I can only charge the device, no data transfer.

-I have both CM12 ROM and CM13 ROM on 'media', and GAPPS for 6.0

-Recovery: CM

-Bootloader unlocked

I know, it is very stupid of me for not making Nandroid backup, and for damaging the USB. :( Please help. Thank you.
[Moto X Android Development] akanealw:
Do you have twrp installed? Can you boot into that? If you can, wipe system and factory reset inside twrp and reflash cm13 and gapps.
[Moto X Android Development] h1ghland3r:
Yes.
[Moto X Android Development] abacate123:
Getting the "Cmactions has stopped" error at the 27/05 test build, and it keep poping up until I reboot lol.

Anyways, thanks for solving the crash in the quick settings on this build, it's gone now :)
[Moto X Android Development] h1ghland3r:
I tried to keep on 27/05 build, but this pop up kills me =( I had to go back to 16/04 build.
[Moto X Android Development] Sebaaaa:
stable

Rom cm13 stable? :confused: :(
[Moto X Android Development] riyosakura:
Someone have already tried clean flash by wiping data partition?

Maybe something on data partition mess things up and causing error?

---------- Post added at 05:31 PM ---------- Previous post was at 05:29 PM ----------

Btw, for everyone please give logcat for the errors, since logcat is necessary for devs to solve the error.
[Moto X Android Development] h1ghland3r:
Yes, I tried a clean flash (system, data and cache wipe). The popup error remains.

I've just moved on to AICP, so I don't have logs =(
[Moto X Android Development] dsiva:
As I said above, I have CM recovery which does not seem to help. Thanks for the reply though.
[Moto X Android Development] Kiristiba:
Hi

Qualcomm released new adreno drivers for nexus phones.

The drivers work on Nexus 4 too, even if it is not in support list, only nexus 5, 6 and 7.

https://developer.qualcomm.com/software/adreno-gpu-sdk/tools

I flashed them on my zuk z1 and it fixed my problems with green pinkish embedded videos in chrome.

As our phone also has the same adreno 320 gpu as the nexus 4, I thought this driver could fix the bug here too.

Sadly it doesn't work. There is only a black screen after boot logo.

Does somebody know the difference between moto x and nexus 4 in terms of gpu drivers?
[Moto X Android Development] ts_firehawk:
Quick report: been using this ROM for 2 days now. Everything is smooth, with the only problems being the known ones. Other than that, I think this is pretty much daily-material. Thanks for your work!
[Moto X Android Development] tycoo:
May you link the source?
[Moto X Android Development] harsh54:
Stuck on Bootloop after installing SuperSU.zip

Hello guys plz help me my device (Moto X) is stuck on boot loop after installing supersu.zip after installing cm13 ,

cm13 was working fine but flashing the supersu.zip made it worse i have tried re-flashing cm13 twice and also tried another ROM (AICP 11.0) still no success plz help me guys ASAP
[Moto X Android Development] h1ghland3r:
Flash SuperSu 2.67 Beta or Higher.
[Moto X Android Development] h1ghland3r:
[MENTION=5116201]Megatron007[/MENTION]

Can I flash tyco kernel in this thread also in AICP?
[Moto X Android Development] se1961:
No LTE...?

I have an xt1060 Developers edition, unlocked, have installed the 0416 build with tycoo kernel and flashed the modems as suggested above. Everything is smooth and stable, and I have great battery life, but just realized that I am never getting LTE any more. I haven't seen it as a bug, but I do notice that some folks on other CM threads with other phones report not getting LTE. Has anybody else noticed this? Any fixes? Thank you in advance... :)
[Moto X Android Development] ts_firehawk:
AFAIK support is only given with the stock kernel, but I suggest you looking into your APN settings and, if possible, flash the stock kernel again (reflash the CM zip to do this).
[Moto X Android Development] se1961:
Thank you! Will do so immediately. :)
[Moto X Android Development] chatian18:
Just flash latest twrp via bootloader then..
[Moto X Android Development] se1961:
I just reflashed the 0416 version of this ROM. Is this what you meant by "reflash the CM zip"? I presume so, since we don't have an official CM for this phone. I gather that this will re-flash the stock kernel?

If I'm correct, I can report that I'm still showing 3G and no LTE signals, even though I DO get LTE when I flash the debloated stock Lollipop ROM.

Does anybody have any suggestions about how to get LTE working? I wonder how to find the APN settings on this ROM, and what I would do to them if I could find them. :D

I really, really really don't want to go back to Lollipop, since battery life is the most important thing to me, and am considering just living with 3G. But 3G kind of stinks on the rare occasion when I need to download maps, etc.
[Moto X Android Development] riyosakura:
If you get 4g on lolipop, but you dont get it on cm, i assume you are using xt1058.

Stock xt1058 has a bug regarding signal mark. It is showing 4g, but it literally using a 3g freq. If you want to make sure, your phone really get a 4g, then you have to check it through *#*#4636#*#* . there will be info what band is your phone using.

In my friend case, it is showing 4g, but it doesnt, since ive already check it through the code and his sim card doesnt support the same band with the phone giving. In my country i need band 3 support which is only xt1052 have on x13.

Sorry for my bad english.
[Moto X Android Development] ts_firehawk:
Yep, that does flash the stock kernel. You can find APN settings going in Settings > Cellular Networks > Acess Point Names. If there is nothing when you open this screen, you'll have to manually add it. Ask for your carrier how to do this, they usually have it on their support pages.
[Moto X Android Development] se1961:
Thanks for both of your replies. I don't think I have the xt1058 bug, since I have an xt1060, and the problem was that I wasn't getting LTE at all, ever. Only 3G showed in my notification bar. There is no Access Point Names menu under Cellular Networks on my phone, so I downloaded LTE Discovery from the Play Store, and used it to reset the data connection. It bumped me from a 3G data band to XLTE (I didn't see LTE in the notification bar, but I used the test number to confirm-- what a great discovery that was, thank you!)-- but after the phone went to sleep for awhile it dropped back to 3G. It seemed as though my phone is not automatically choosing the correct data band. So I went into the "select radio band" menu in the test menu, and chose SET GSM/UTS Band as USA. Now for the first time LTE pops up right away, even on the notification bar! So far it has persisted. We'll see. Thank you again.
[Moto X Android Development] se1961:
I spoke too soon. It turns out that if I choose USA as my GSM/UMTS band, I can't make any phone calls. I set it back to "Automatic" and and I can make calls but immediately my cellular data drops to 3G. I feel so close to figuring this out, but I'm stuck. Any help would be appreciated.
[Moto X Android Development] dsiva:
That's is the problem. I can't transfer any data to phone since my USB can only charge.

I guess I know the answer -- there is no solution for this except to buy another phone.
[Moto X Android Development] ThunderBolt_BR:
You can try to repair/ replace your USB module as well. It will be way cheaper than buying a new phone.

[]'s

Enviado de meu LG-V500 usando Tapatalk
[Moto X Android Development] js290:
Clean flash or upgrade over 22/3/16?

Adding logcat and bugreport for "CMactions has stopped"
[Moto X Android Development] omy4069:
broo u not need transfer any daa to ur phone....

u only need put your phone on bootloader and use the command promp with correct adb and put the comands and flash the twrp.
[Moto X Android Development] Megatron007:
bro its not the actual log , how did u take this ? do with adb method :)
[Moto X Android Development] simar404:
Thank you for making a new build again. I want to know if battery drop issue has been fixed?
[Moto X Android Development] Megatron007:
I literally didn't did any changes regarding the battery i was just testing the cmactions for moto x and it got fc's
[Moto X Android Development] simar404:
Kk thanks and what do u mean by it got fc's?
[Moto X Android Development] Megatron007:
force closes :)
[Moto X Android Development] h1ghland3r:
[MENTION=5116201]Megatron007[/MENTION]

Remember tyco kernel you recommended us to test on this rom?

Is it work on AICP?
[Moto X Android Development] Megatron007:
yup , it will work
[Moto X Android Development] Ishaan Gupta:
Can we use the hybrid kernel? You never made a thread for it.
[Moto X Android Development] Megatron007:
yeah , you can use
[Moto X Android Development] riyosakura:
is there going to be new cm13 build anytime soon?

im still on 3/22 atm, since it is the most stable version afaik. 4/16 have bug regarding tile fc and 5/27 build seem solved it, but another bug cmaction fc is occuring.
[Moto X Android Development] js290:
The same way that the CM developers ask for it in jira:

logcat -d -f /sdcard/logcat.log *:V

Followed by adb bugreport > bugreport.out.
[Moto X Android Development] dsiva:
I guess you did not read my prev post. Imma try to replace USB connector and see if I can get it to work. Thanks for the reply though.
[Moto X Android Development] harsh54:
[MENTION=4879880]h1ghland3r[/MENTION] i have flashed higher version of SuperSu (BETA-SuperSU-v2.74-2-20160519174328.zip) as u told but still on bootloop, by the way i have installed that supersu on cm11 i thought of flashing an old rom first let it boot for the first time then install the latest cm 13 as mentioned in one of the post of " recovering from CM bootloop", and im using philz touch recovery now, i have also tried CWM and TWRP to flash cm13 but still no progress, Plz reply ASAP Thankyou :)
[Moto X Android Development] h1ghland3r:
Well, changing to SuperSu Beta is what I did when I get bootloops. =(
[Moto X Android Development] harsh54:
Your Are the last hope Megatron007

[MENTION=5116201]Megatron007[/MENTION] Please help me out here buddy you are the last hope now, i always figure out a way to resolve these problems but this time i'm out of options, i literally have tried everything to get out of bootloop,

1) flash old cm then flash the latest cm 13

2) flashing cm in different recovery's

3) flashing the latest and oldest supersu

4) flashed several different rom's

Is there anything im doing wrong plz reply ASAP [MENTION=5116201]Megatron007[/MENTION] Thankyou :)
[Moto X Android Development] Megatron007:
if u are facing bootloops with new beta use old su.zip or else turn on the inbuilt root from developer setting :)
[Moto X Android Development] harsh54:
Finally Problem Resolved

Thankyou for Replying [MENTION=5116201]Megatron007[/MENTION], Well the problem was solved by flashing the stock rom then letting it boot for the first time and flashing CM13 again worked for me buddy, Anyways thanks Buddy, now the problem im facing is that supersu of cm13 is not working, I keep getting a message "SU binary needs to be updated" any solution on that, well i would like to mention that this was the problem for which i flashed the supersu.zip on cm13 which made my cell stuck on bootloops any soultion on this Bro ?
[Moto X Android Development] Megatron007:
flash the new one su.zip if it bootloops use old one :)
[Moto X Android Development] duwi3:
Really awesome ROM... but I have just one problem, so far.

The WiFi keeps disconnecting from hotspots, both at home and work. The WiFi will also be on and it doesn't auto connect. I'm not sure why but it's rather annoying especially because data here is expensive. Please prepare a fix ASAP :)
[Moto X Android Development] Kiristiba:
Don't use inbuilt su with supersu app from play store. Inbuilt su has its own GUI.

I think it's in developer settings too.

If something doesn't work for you that is working for everybody else

you most likely did something wrong.

Doing it wrong multiple times doesn't make it right ;)
[Moto X Android Development] Megatron007:
http://romwarehouse.com/megatron007/test/

Build - 2/6/16

Changelogs - A try to fix flashlight

Updated Media Codecs

A try to fix snapchat/screencast recording

Implemented Custom Audio policy ,

Bugs , report here :)

PS - I dont know whether it is fixed or not , i dont have my device on my hands to test this stuff :)
[Moto X Android Development] ysop:
sad,flashed new build,torch no fix,still like before...
[Moto X Android Development] xabr3:
What about media codec bugs?
[Moto X Android Development] ysop:
I tried screen record and play it by stock picture app,fc happened.now i have flashed AICP back to see if sound work.

edit:i cant listen any sound.maybe because i only record for 10s?
[Moto X Android Development] pankaj.jajoria:
Unable to have root access..

Tried from develeoper option(app/app+adb) but no luck :(
[Moto X Android Development] lucasmarks1991:
Flashed today's build over 16/04 build.

Torch, screen recorder and mic don't work.
[Moto X Android Development] abacate123:
[MENTION=5116201]Megatron007[/MENTION] there's a bug in the telephone/dialer app when I receive or do a call in this new test build 06/02, everything bugs and I can't hear anything nor the person can hear me... The interface just bug too. Came back to the 05/27 one.
[Moto X Android Development] riyosakura:
aicp has the same behaviour?

or you cant listen sound because only 10s recording on cm13?

mic dont work?

and it does work on 16/04?

interface bug??

so on 05/27 you dont have cmactions fc?
[Moto X Android Development] se1961:
I thought it was worth posting the outcome of my struggles with LTE-- after flashing this, CM 12.1 and stock, multiple times, I followed the advice on the CM forum and went to Verizon to get a new SIM. LTE is working beautifully, perfectly, ever since. I started on stock and then reflashed the 0416 build of this CM13 ROM, and it's still perfect. Definitely worth a try if there are radio-related problems-- the guy at Verizon seemed to think this was common.
[Moto X Android Development] riyosakura:
reporting in.

Flashlight still does not work. It behave the same with 03/22.

Media codec seems broken. Audio FX always fc-ing. Unable to play anysound including volume sound, music, calling, etc.

Not try snapchat or screencast, but i believe it will not work properly.

Custom audio policy seems broke something related to sound.

Here is the logcat.

I hope you figure out something. :D

btw, im back to 03/22 build. does 04/16 build better than 03??
[Moto X Android Development] riyosakura:
i tried to back to 3/22 build without wiping data.

but still bootloop on the bootanimation. :(
[Moto X Android Development] lucasmarks1991:
Mic and sound (with / without headphones) don't works on today's build.

On 16/04 build, mic and sound works!
[Moto X Android Development] riyosakura:
but there is still tile setting crash on 16/04 build, doesnt it?
[Moto X Android Development] Haidersaleem:
This rom is getting worse day by day. [emoji31]
[Moto X Android Development] Megatron007:
Solving the bugs without the device is imposssible for me atleast...If you are telling worse than dont use it atleast i am trying my best to build test builds
[Moto X Android Development] js290:
Flash light still turns off after a few seconds. Including logcat and bugreport.
[Moto X Android Development] Megatron007:
maybe i am not going to continue cm13 unofficials build from now :)
[Moto X Android Development] xabr3:
Are you saying this rom is dead now?:(:crying:
[Moto X Android Development] riyosakura:
This is sad.

But maybe, another devs maybe would continue build the rom for ghost user? At least for cm sources update.

[MENTION=5808966]abinsur279[/MENTION] [MENTION=5294352]cyril279[/MENTION]

Since, i thought there is not much problem for just compiling the rom with a little cherry pick from cm13 sources??
[Moto X Android Development] Haidersaleem:
I didn't mean to hurt you.

Sorry. [emoji52]
[Moto X Android Development] ivlivs:
Awesome so far, thanks! :)
[Moto X Android Development] T-1311:
I'm neither able to update (160202) nor to flash after a complete wipe.

Tested with TWRP 2.8.6.0 and 2.8.7.0

Used format F2FS for all partitions. Formated again. Then tried ext4 for cache. Then tried ext4 for System.

Nothing. I'm not able to flash 160216 on my XT1052
[Moto X Android Development] Megatron007:
whats the error comming ?
[Moto X Android Development] regisknechtel:
I had the same problem. Just flash stock 5.1 through RSD to easily fix partitions, reinstall TWRP then flash CM13+gapps and it'll work just fine.
[Moto X Android Development] goducks3620:
Do you need TWRP 3.0 to flash this?
[Moto X Android Development] T-1311:
E: Error executing update binary in zip '/usb-otg/Custom rom/CM/CM13.0-20160216-UNOFFICIAL-ghost.zip'

---------- Post added at 02:44 PM ---------- Previous post was at 02:44 PM ----------

Ok, I will try it.
[Moto X Android Development] dani.galla:
Nope

---------- Post added at 02:47 PM ---------- Previous post was at 02:46 PM ----------

Perfect Roms! I'm using it as a daily driver! Everything's working perfectly
[Moto X Android Development] Megatron007:
Guys One More Good News is Coming :P
[Moto X Android Development] simar404:
And wat wud be dat[emoji4] [emoji4] ?
[Moto X Android Development] Megatron007:
Ok Guys , Time to Reveal Good News ;)

Now 2g/3g Network switch also has been fixed , thanks to [MENTION=5857684]TheStrix[/MENTION] for pointing me out , and flashlight/torch is also working relatively fine for about 1 min or so ..So i removed my old 16/2/16 build and re-uploaded the new build , So here goes the changelogs

Changelogs -

Fixed 2g/3g Switch

Fixed Video Recording Bug With Snapdragon Camera

Inverted /Crazy Video Has been fixed due to updated media codecs by [MENTION=5604178]zwliew[/MENTION] and [MENTION=4403780]TeamMex[/MENTION]

Sync With latest Cyanogenmod 13

Included all device specific patches which merged in device tree

Enjoy :)

Now the rom is suitable for dailydriver and is almost Stable :)
[Moto X Android Development] h1ghland3r:
Nice! Looking forward the weekend to flash on my X.
[Moto X Android Development] dani.galla:
Hi!

Thanks for your hard work!

There's a little bug:

When you call someone and the other ends the call before you, there's a pop up with written invalide number.
[Moto X Android Development] Megatron007:
yeah i am looking in to it :)
[Moto X Android Development] gowtham nkg:
can I just flash this built over 12.2.16 without gapps??
[Moto X Android Development] Megatron007:
yeah you can , but clean flash is recomended
[Moto X Android Development] gowtham nkg:
Thank you.. :) and the ROM is awesome.
[Moto X Android Development] johnbidwell:
Google Now on tap is not working for me :(
[Moto X Android Development] rtimoff:
Is this new one "# 2"	2016-02-16 15:08?
[Moto X Android Development] 690sid:
Okay so the 16th Feb build is great. Except for a few tiny bugs, like -

1. The Flash bug

2. The "Invalid number" bug

Everything else seems to work just fine, and as its supposed to. I'm really happy with Marshmallow. Waited too long for it. Thanks a ton Megatron!

PS: This bug might not be rom related because I remember it being on cm12 too... The vibrator works at its own whims... Mostly, I'm just left with sound, and once in a while, the vibrations will show thier existence. Anyone else with this issue? If not, I'm hoping its a hardware issue.
[Moto X Android Development] Megatron007:
yeah
[Moto X Android Development] CsR0501:
Please no! ?

Enviado desde mi Moto X mediante Tapatalk
[Moto X Android Development] abacate123:
That's really sad man... For sure you are one of the best, thanks for the effort :)

I just would like to see a last build, I mean, a "most stable as possible" one of this great rom... If possible, someday.
[Moto X Android Development] attaullahsahito:
Kamal karte ho pande ge.. hum ne sharab chorne ko kaha tum to duniya he chor gae :(

one last build
[Moto X Android Development] abacate123:
English, please.
[Moto X Android Development] Megatron007:
Guys , it is very hard to solve the bugs without the device . I can make a last build but it will same bugs as before :)
[Moto X Android Development] js290:
Your cm13 unofficial seems to work better than the official cm12.1. I don't care that much about the flashlight.
[Moto X Android Development] CsR0501:
We can be your testers!!!... please don't let us!!! [emoji22]

Thanks for all your great support bro'!!!

Enviado desde mi Moto X mediante Tapatalk
[Moto X Android Development] Megatron007:
it's not about testing , i have to get the logcats then see where the problem is and if i am not able to solve it or whatever i need to use the prebuilts libs and need continuous testing , hope u get it
[Moto X Android Development] hbenz2008:
Megatron007, arent you getting a Moto x!

Anyway, we appreciate all your efforts.

Flash light isn't a deal breaker at all.

Keep it up man,still hoping to get N on moto x haha ✌
[Moto X Android Development] Megatron007:
I already got a nexus 5x and though i am a college student i dont have a penny to buy it :p
[Moto X Android Development] hbenz2008:
Read some 1 offered you one. I guess that deal didn't go through!

Anyway its all good man.