yashsingh1/xdaforums huggingface dataset:
[Moto X Android Development] Shoaibhassan:
I am using cm 13 unofficial rom i am facing problam when i took calls. Only loudspeaker works but earpiece not woking please help
[Moto X Android Development] h1ghland3r:
Oh my god, read the last posts..
[Moto X Android Development] riyosakura:
I just have a laptop here and a very limited internet plan.

Rereading the guide to build cm and knowing that it is almost impossible for me to build it myself. ??

Need plenty of storage spaces and a decent RAM. [MENTION=5826827]fadyrox[/MENTION] why dont you try to build cm13 and use 4.4.4 proprietary blobs, if building is successfull, it should not have a speaker bugs.

You can learn building cm13 here https://wiki.cyanogenmod.org/w/Build_for_ghost.

If it does work you can share it on xda and it will be an absolute solution for all of us (xt1056 user). ?
[Moto X Android Development] tj13:
I updated to 5.1 before going to 12.2 and then 13. I saw the call bug here. I just restored my 12.1 backup. I will test the next version, when it's posted.

Update"

Well after my restore back to 12.1 I still have the call bug on my XT1060. Still working on it. A factory reset didn't do it. I guess my phone could just be broken.
[Moto X Android Development] Fahadroid:
What it looks .. that some one xt1056 user has to be developer now to get rid from call bug !

its looks very hard to build rom .. but i can be try .. !

i just read how to build rom & i think it requires lots of time to understand all of thing !

[MENTION=5116201]Megatron007[/MENTION] : Bro you are a developers .. now here every one who has xt1056 sprint device .. cant use lollipop & even marshmallow due to call (speaker / earphone) bug ..

i think you can help us to just change little thing .. as [MENTION=5034190]riyosakura[/MENTION] said above :

why dont you try to build cm13 and use 4.4.4 proprietary blobs, if building is successfull, it should not have a speaker bugs.

& release rom for us mean for all xt1056 sprint user .. that would be really great full help to us !

if you dont have time .. so you can ask your friends developer to do it ..

Please help us bro !
[Moto X Android Development] diago27:
Does this mean there won't be Official Nightlies anytime soon?

http://review.cyanogenmod.org/#/c/136249/
[Moto X Android Development] sharukins:
that's not how it works...

cm12.1 and cm13.0 are programmed to "talk" to the 5.1 firmware blobs while cm11.0 can "talk" to the 4.4 binary

just building cm13 with 4.4 blobs won't change a thing, you will only face even more bugs.

and btw: building is the easy part of developing

if none of the xt1056 users is a developer himself the only thing you can to is to provide logs and be patient until one of the devs finds a solution.
[Moto X Android Development] riyosakura:
Xt1056 with unlocked sim have the bug using a stock 5.1. But it doesnt when using 4.4.4.

So the problem is on the driver software of 5.1 proprietary firmware. So, i thought if xt1056 using a driver software from 4.4.4 it could be work. Even though another bug that doesnt appear when using 5.1 blobs maybe appear when using 4.4.4 blobs.

If it does have a bug, maybe some change on the commit (base on other qualcomm device source or with 5.1 blobs source) will fix it. I know it not easy. But it is worth a try.

Who know, just maybe using 4.4.4 blobs will resulting the same performance with using 5.1 blobs and without the bugs.

Since there are many device using an older blobs such as galaxy ace 2 (using 4.1.2) have a working cm12.1.
[Moto X Android Development] whizinc:
I HAVE NO IDEA!! why am i NOT getting this bug? I have the same XT1056 SPRINT Moto X and i recently flashed CM13, AICP MM and Lastly i flashed XT1053 GSM Stock rom to get rid of the bugs in custom roms and again!! Didn't needed to flash modem there was no bugs at all. Didnt had any kind of Earpiece/Speakerphpne bug! Damn smooth calls! And Note that i tried thoroughly 3,4 times made my friend call me on my sim numerous times just to check if there is any bug of earphone/speaker. Also switched from earphone to speaker and didn't had any kind of bug. My friend could hear me clearly as well as i could hear him clearly also from both speaker and earpiece. I dont know why am i not getting this earpiece bug that you guys are reporting. Maybe im the only one who can help you guys. But i dont know how can i do that. Need further Assistance from experienced devs. As im not getting this error and i have the same XT1056 i could solve this bug once and for all.

Edit: Checked on earphones, earpiece of phone and also speakerphone.
[Moto X Android Development] riyosakura:
So you are using an unlocked sim phone of xt1056? If you say so. The only thing that could make the your phone doesnt have this bug is whether you've already unlocked the latest modem or your not updating both of your bootloader and modem at all (and you are not getting bug. You should get the bug if not updating bootloader though.)

Please check your bootloader from bootloader mode, it should be on the up left side. Its 30.BE on my devices. If you have the same bootloader so your phone is unlocked with the latest modem installed.

So our devices (xt1056) must perform the same method such as your to unlock the modem, since the normal method wouldnt work. Can you ask the one who unlocked your sim how to do it and sharing it with us?

Or maybe, you are not using a xt1056 variant. Maybe you are using xt0153, or xt1052, or xt1060. Since there is too many variant of this phone and the seller sometime mismatch the device variant. ?

The only solution for us (xt1056 user) to use the current ROM without speaker bug is to update the modem and unlocked the sim on the latest modem.
[Moto X Android Development] tj13:
Forgot to say I'm oc xt1060.
[Moto X Android Development] whizinc:
I already knew that the bootloader version of my Sprint Moto X is 30.BE but i checked again just to be sure and yes its on 30.BE. And yes you are right, i bought the phone with the 30.BE Bootloader and i guess the seller unlocked the sim on 30.BE thats why i am not getting bugs because my sim was unlocked on 30.BE. And I am 100% Sure my device is XT1056 i had it proven because when i bought the phone and i just reached home i connected my phone to my PC, without even touching anything in phone it was in fresh state, It showed XT1056 on my PC, when i connected it to transfer some data in it. So i guess the conclusion is: My seller somehow unlocked the sim on 30.BE bootloader thats why im not getting any kind of bug. Unfortunately i can't contact that seller again and ask him how he unlocked the sim on 30.BE because i didn't get his contact number. And i certainly cannot reach him again as his shop location is wayyy too far away from my location its nearly impossible to contact him. Also the owner of those shops change day by day so there's 1% chance i will find that same guy there again, however one more thing the seller didn't had much information on these cellphones, he was just there to sell them so i guess he won't have the knowledge on how my Phone was sim unlocked as well.

Edit: I never got any need to flash any modem or bootloader, because i never got any bug in any rom.
[Moto X Android Development] bart.found:
since blankflash files are out for this device don't you think that there is a "bricky" way to convert your phone in a xt1052 by flashing the 1052 bootloader?

I DON'T KNOW IF IT'S POSSIBLE and I'M NOT RESPONSIBLE IF ANY OF YOU BRICKS HIS OWN PHONE..
[Moto X Android Development] riyosakura:
Yeah. I know this would be a probability.

But im not brave enough yet to flash other modem for my devices atm.

Maybe someday.

Maybe flashing modem and bootloader of anyother variant such as xt1052 or xt1053 would do the job. Or even unlock lte connection.?
[Moto X Android Development] d14gvn:
Sorry for changing the topic

With lastest build Facebook app runs awful (doesnt load profile page, unable to update status, more battery draining than usual un previous versions)

Any ideas?
[Moto X Android Development] mlodykaras:
Actually your are on topic but the rest is not. I'm sorry but maybe mods can create separate thread about flashing modems and earpiece bugs with cm builds? It could clean up the mess a bit and we could concentrate on having discussion about cm13 builds. Thx!
[Moto X Android Development] riyosakura:
Its working good on my phone.

No problem at all with facebook app.
[Moto X Android Development] h1ghland3r:
Video recording should be working on the last build? I recorded some videos yesterday and all of them are noisy.

Tried listen using QuickPic.
[Moto X Android Development] regisknechtel:
It's a bug with codecs, audio on recordings is sh*t here as well, even on the latest build.
[Moto X Android Development] Fahadroid:
[MENTION=5034190]riyosakura[/MENTION] : Waiting for your response on above !

BTW .. topic is belong to cm13 .. topic is belong to bug which is in cm13 ... so we are using right platform to discuss this ..:cool:
[Moto X Android Development] bart.found:
Kill facebook and messenger and install "Metal for facebook"! ;)
[Moto X Android Development] aledex:
Facebook app is a complete and utter disaster.

Inviato dal mio K015 utilizzando Tapatalk
[Moto X Android Development] necktru:
Any advance with WIFI connect bug? It's the only thing that is awkward, Anyone knows if AICP or OCTos has the same bug?
[Moto X Android Development] cmr_noob:
Oct os doesn't have this bug
[Moto X Android Development] diago27:
How is stable is Oct OS for daily use, since you've tried it?
[Moto X Android Development] phalkon30:
Can't remember if it's this thread or another device, but some people have luck with setting their wifi channel to 1 on their router.

Latest android security patch has some foxes for wifi scanning drain btw, you guys may see a benefit from that when this rom is resynched

Sent from my SM-G900R4 (klteusc) running CM13 1.30.16 with xposed
[Moto X Android Development] Camilo Olivares:
AICP doesnt have that bug.
[Moto X Android Development] ndasarathy:
guys help me with this error.it's the second phone giving me the same error
[Moto X Android Development] ysop:
you can confirm your device is motox2013?xt10xx?:confused:
[Moto X Android Development] diago27:
Update to TWRP 3.0.1
[Moto X Android Development] ndasarathy:
please provide me the link
[Moto X Android Development] ysop:
try this:https://drive.google.com/file/d/0B-tlso-zNf9NMXNfem50U0ZWRFk/view

though only 2.8.7,it's enough to flash 6.0.1.now i use it,works well.

i dont think we need to update to 3.0+, very slow to wipe data.And fast format build is not perfect.

thread links:http://xdaforums.com/moto-x/orig-development/official-twrp-motox-2-8-0-1-10-22-2014-t2925321/page8
[Moto X Android Development] Megatron007:
New cm build testing on its way ;)
[Moto X Android Development] diago27:
I'm getting a sudden battery drop with the 22/03 build along with tyco's kernel v1.3. Battery suddenly drops from ~30 to ~15
[Moto X Android Development] sharukins:
any new commits or device specific bug fixes? I didn't see anything new in the projects CyanogenMod/android_device_motorola_msm8960dt-common and CyanogenMod/android_device_motorola_ghost

this is fixed in the stock CM kernel, so it probably belongs into tycoo kernel thread
[Moto X Android Development] Megatron007:
Coz i didnt submitted patch to CM :P
[Moto X Android Development] sharukins:
neither did one of the other devs ^^

so just upstream changes... curious if this fixes one of the bugs :D
[Moto X Android Development] Megatron007:
not just upstream changes i was working on screencast/snapchat fixes (still working on it )
[Moto X Android Development] h1ghland3r:
[MENTION=5116201]Megatron007[/MENTION],

First of all, thanks for keep working on updates for our X1.

I'd like to know if the Wifi bug from the last build will be fixed on the next update.
[Moto X Android Development] Megatron007:
fixed :P
[Moto X Android Development] simar404:
I downgraded to cm 12.1 snapshot as snapshots are known for their stability but i hv found bugs in this too. So now i hv decided no matter how many bugs cm13 has i will install ur coming cm 13 update. [MENTION=5116201]Megatron007[/MENTION] ROCKS!!!
[Moto X Android Development] mlodykaras:
I hope I will be able to test this new build ;) Just ordered HTC 10[emoji14]
[Moto X Android Development] riyosakura:
Any news regarding call bug on old modem? Since maybe someone here unable to update it. ?

Do you cherry pick latest commit from cm12.1 since it has something related to calling?

I hope there will be at least a workaround for this prob.
[Moto X Android Development] tycoo:
I thought that was fixed in the device branch already and not be a kernel issue [MENTION=5116201]Megatron007[/MENTION] ?
[Moto X Android Development] Megatron007:
it was regarding device tree
[Moto X Android Development] Megatron007:
which commit and which blobs we are using stock 5.1 blobs right now
[Moto X Android Development] g0nzal3s:
One core gets regularly stuck at 1.7GHz and 100% load for me. Monitoring apps claim that no app is causing any significant load. My devices gets hot and the battery drains fast.

I am using the latest build.

Is anybody else experiencing this issue?
[Moto X Android Development] hawkdown77:
[MENTION=5116201]Megatron007[/MENTION]

Its fixed in this new build screen mirroring??
[Moto X Android Development] Megatron007:
somewhat not
[Moto X Android Development] Megatron007:
which kernel ..if you are using custom kernel you need to adjust governer and hotplug
[Moto X Android Development] g0nzal3s:
I am using tycoo's kernel right now. What does governor and hitplug need to be set to?

But I think I had the same problem with stock cm kernel as well.

Gesendet von meinem Moto X mit Tapatalk
[Moto X Android Development] g0nzal3s:
I just realized that I am currently using zwliew r13 Kernel... (which fixes the WiFi bug for me). But I definitely had the CPU stuck problem with the stock kernel as well.

Gesendet von meinem Moto X mit Tapatalk
[Moto X Android Development] hachamacha:
After putting in a fair amount of code analysis of the DHCP problem when trying to reconnect to WIFI and seeing the issue in the Google code-base that is identical, which was claimed to have been solved, but not necessarily distributed yet. (so that we don't know which code-bases have it working).

Anyway: This post ^^ made me take a far less-intellectual re-look at the problem. I know there's nothing about the zwliew kernel that's going to really affect this problem that I and many others have had for at least 3 weeks, and I know there's nothing, as far as this problem goes, about any of the available kernels (stock or Tycoo) that should affect this, so I started to wonder if it was just a luck/alignment thing that just reinstalling the same kernel a few times might change.

I re-installed the same kernel (Tycoo) that I've been using, and strangely enough ... I'm having no problems with WIFI Connectivity now. Damn, what a ****ty solution. It's actually disappointing to wind up knowing so little about what you did to get something working.. However, it did work. For me it worked the 2nd install. Not just in my house, in the 3 places with wifi I've visited since I did this. The thing I'm wondering about is whether unpacking (via updater-script) to /system/lib/modules is taking a funny turn at times. I'm getting good and sick of reinstalling SuperSU each time I try the kernel.

Go figure! (And no way I'm calling that a solution, just something that worked for me. By the way, I couldn't connect to wifi at all , period, with zwliew kernel). I don't think there's anything wrong with that kernel either, just a lot of as-of-yet-unexplained junk happening.
[Moto X Android Development] ThunderBolt_BR:
Thanks for the test build [MENTION=5116201]Megatron007[/MENTION]. I've been running it all day without issues.

[]'s
[Moto X Android Development] diegomartinezlovey:
flashligt still doens't work?
[Moto X Android Development] regisknechtel:
How can I get the test build? Thanks
[Moto X Android Development] stefanthehuman:
Me too please :D
[Moto X Android Development] riyosakura:
http://review.cyanogenmod.org/#/c/139451/

This commit from cm12.1 nightly.

Anyway, what do you think if we build a cm13 rom base on 4.4.4 blobs. Will it work? Or there will be much more bugs that will occured? Sorry if out of topic.
[Moto X Android Development] Megatron007:
its nothing related to call issue and if we build with 4.4 blobs more bugs "may" occur
[Moto X Android Development] riyosakura:
Btw, is there any hint which file that is used for calling. I'll pull it from 4.4.4 and push it to this ROM and hope it will work. ?

Work of desperation.
[Moto X Android Development] ysop:
i guess the link is:http://romwarehouse.com/megatron007/test/ :fingers-crossed:
[Moto X Android Development] Megatron007:
DAMN !! you guys xD :P
[Moto X Android Development] simar404:
I just downloaded it now lol. I am going to test it today
[Moto X Android Development] h1ghland3r:
Just downloaded too. Should we use tyco kernel?
[Moto X Android Development] diago27:
Try testing it with the stock cm kernel that comes with the build.. Then maybe after a day or two flags tycoo's kernel and check.
[Moto X Android Development] mlodykaras:
Well dirty flashed the test build with tycoo's kernel and I still have the wifi bug!

WTH!
[Moto X Android Development] ThunderBolt_BR:
Settings crash when entering Live display menu under screen on the last test build. Not a major issue as I can still enable it by the live tile.

[]'s

Enviado de meu Moto X usando Tapatalk
[Moto X Android Development] h1ghland3r:
It's true. Wifi bug has not been fixed, at least with tyco. I will flash again, but now with stock kernel.
[Moto X Android Development] Megatron007:
Dont use the test builds it may have problems wait for the releases
[Moto X Android Development] h1ghland3r:
Dirty flashed the test build again, but now I had not flash Tycoo kernel. The wifi bug remains (I mean, it doesn't connect automatically on my home Wifi), maybe I need a clean flash.. =(
[Moto X Android Development] simar404:
Where can I find stock cm 13 kernel?
[Moto X Android Development] h1ghland3r:
I mean the kernel that comes with the rom itself.
[Moto X Android Development] simar404:
Aah kk, so I am already with stock, I notice dat my device takes hell lot of time to charge. And I still have wifi bug
[Moto X Android Development] hachamacha:
If you've done a twrp/{whatever} full nandroid bkp of the stock cm13, then you should be able to restore boot.img and the contents of /system/lib/modules from your backup, and from your custom recovery, restore them. I think you could do it all from any recovery with a .. file manager and sideloading. Easiest from adb on a PC to get the modules and mount /system RW , then copy them over the ones from the other kernel. For the boot.img, just restore it from the backup.

I've done this on several devices before. No doubt, this'll mess with your SuperSU install, so after a reboot and testing SU, just back to recovery and install the latest SuperSU again.

If you're doing this to try to get wifi working, that is way more random than just installing some particular kernel and not kernel related (I'm pretty sure of that). Mine's working now, but I have no idea why (see my last post ^^), but I installed tycoo twice, 2nd time wifi began working fine. No sense to it.
[Moto X Android Development] abacate123:
That's great, new updated coming! Thanks for the development [MENTION=5116201]Megatron007[/MENTION] and I hope the "wifi not automatically connecting" issue have been solved.
[Moto X Android Development] jude007@excite.com:
No sound and laggy keyboard

Hi. Firstly, thanks [MENTION=5116201]Megatron007[/MENTION] for the time and effort put into this great ROM.

I'm new to this, so please bear with me...

I did a complete wipe, installed cm-13.0-20160322-UNOFFICIAL-ghost ROM as well as the open_gapps-arm-6.0-full-20160414 package, for good measure, also installed the 3.4.110_x_CM13_MM_kernel_v1.3 package. All installed with no errors. I did a restore before rebooting.

Device boots up ok. Wifi, auto-rotate, and radio all work. I can capture video, but there is no video playback.

Also, I have no sound, and my keyboard has lag (characters take about 2 - 3 seconds to show up when I type.

Is there something I'm not doing right ??

Thanks

J
[Moto X Android Development] abacate123:
Great work with the new build [MENTION=5116201]Megatron007[/MENTION], the "wifi not automatically connecting" issue has been solved, thanks bro, awesome
[Moto X Android Development] regisknechtel:
When I'm listening to Google Play Music streaming through loud speaker, sound goes up and down out of nowhere. It doesn't matter what build I use and it didn't happen on stock. Anyone with this problem?
[Moto X Android Development] Soulj4h:
I'm running into an issue. So I have my bootloader unlocked and it's rotted with TWRP 2.8.7.0 installed. If I install during recovery I run into an error, something about the executable. How can this be fixed?
[Moto X Android Development] Soulj4h:
Here is the screenshot of my error. I have uploaded it as an attachment. You will see the other ROM installing here, but I uploaded the wrong screenshot. I also tried with this rom. Same exact error.
[Moto X Android Development] simar404:
Decompress the rom which u r flashing. Locate updater-script file in meta-inf/com/google/android and edit the file and delete the text till if else but don't delete if else. Then decompress the rom and flash.
[Moto X Android Development] h1ghland3r:
Flashed the April 15th build and the Wifi issue has been fixed. LiveDisplay is also not crashing anymore as the April 14th build.

=)
[Moto X Android Development] Soulj4h:
Thank you. I managed to get it working another way.
[Moto X Android Development] Soulj4h:
I seem to be facing another issue. Is there a WiFi problem? Basically, I have to manually go into the WiFi settings for it to detect my wife.

Secondly, I'm unable to update SU binaries. How do I do that?
[Moto X Android Development] regisknechtel:
If you read any of the last 20 pages you'd know there's a WiFi problem.
[Moto X Android Development] hachamacha:
If there's a list for these 'test builds' or a link to them, I'd be interested in trying them out or getting on the list. Thanks.

[MENTION=3184901]Soulj4h[/MENTION] : Updating SuperSU binaries via the apk hasn't worked (as far as I can tell) since V5.x. Just get Chainfire's latest SuperSU .zip and install from recovery and don't use any TWRP options to update SU, just treat as normal .zip install.
[Moto X Android Development] h1ghland3r:
Yes, there is. But right now there is anything listed.

http://romwarehouse.com/megatron007/test/
[Moto X Android Development] simar404:
There isn't anything in test build now but we have a nrew 16/04/16 build lying just outside here: http://romwarehouse.com/megatron007/
[Moto X Android Development] hachamacha:
[MENTION=6890013]simar404[/MENTION] & [MENTION=4879880]h1ghland3r[/MENTION] :

Thanks to both of you. I'll give that one from today a try. I've got a working git of cm13/TWRP/device repos for ghost now, so have made my own, but am looking around for the ones that're up to date for this ROM to try to play with the wave/wake/motion code. I'll reread the OP again since I must have missed it.

Edit:: [MENTION=5116201]Megatron007[/MENTION] :

I'm just trying to do some work on something as recent as the last "official unofficial" build from 0322. Are your changes a combo of whatever happened in CM13 + https://github.com/CyanogenMod/andr...CyanogenMod/android_device_motorola_ghost.git ? (+ whatever kernel you're defaulting to)? Just searched github again and noticed your(I think) repos : https://github.com/Megatron007/.... .

It's just 'local' work unless I come up with anything that gets CM to function with motion detect as it did during 4.4.4 & 5.1 stock.

Thanks.
[Moto X Android Development] h1ghland3r:
Should be a new build =D
[Moto X Android Development] Soulj4h:
Thanks guys. I have not been in the custom rom scene in forever. Pardon my ignorance. So do we plan on having the WiFi issue fixed soon?