yashsingh1/xdaforums huggingface dataset:
[Moto X Android Development] zwliew:
Sorry, what's the problem with WiFi auto connect?
[Moto X Android Development] h1ghland3r:
Wifi not connect automatically. It started on the March build. The April one already fixed this issue.
[Moto X Android Development] hawkdown77:
Tycoo kernel it works now.
[Moto X Android Development] Soulj4h:
Do you guys have an issue where the battery goes to like 10 percent and all of a sudden it does to 3 percent?
[Moto X Android Development] h1ghland3r:
It's fixed if you install tycoo kernel.
[Moto X Android Development] mafri2:
using car phone via BT

Hi guys, i still have this weird Bluetooth issue, that whenever i want to make a call through my car Radio it freezes suddenly and reboots. Can someone help me ?
[Moto X Android Development] rtimoff:
What about GPS problem, is it fixed? And I'm using 1056, so after "cleaning modem stats" my SIM card shows error, and can't unlock it on CM, so need to go back to stock with RSD.

Отправлено с моего XT1052 через Tapatalk
[Moto X Android Development] shashank094:
Installed tyco kernal still facing battery drop issue,any other fix?
[Moto X Android Development] riyosakura:
Im using xt1056. It does have gps bug for the first attempt.

But it will work after couple hours of use.
[Moto X Android Development] Soulj4h:
Which kernel? I still have it after installing tycoo.
[Moto X Android Development] h1ghland3r:
Idk, here it's fine with tycoo.
[Moto X Android Development] Kiristiba:
For me it is fixed with Tyco kernel too. My phone is a xt1053. Perhaps it depends on the combination of kernel and device model?
[Moto X Android Development] simar404:
Battery life after tycoo kernel is extreme wow :
[Moto X Android Development] Soulj4h:
Maybe. I'm on xt1052. Can you send me the link you used for tycoo?
[Moto X Android Development] karolyhk:
With the last two builds - 2016-03-22 and 2016-04-16 - NFC is disabled on my xt1052 device and canot be enabled in the settings. I tried both with default and tycoo kernel as well.
[Moto X Android Development] h1ghland3r:
It's working here. Using tycoo and the last build.
[Moto X Android Development] lucasmarks1991:
Any news about the next build? News also on the official support of the CM?

I'm sorry for the questions!
[Moto X Android Development] dagrlx:
this project as they are allowed to die slowly. its leaders are busy on other projects

Enviado desde mi Moto X mediante Tapatalk
[Moto X Android Development] mafri2:
no one? is it me or am i the only one with an xt1052 de and this problem?
[Moto X Android Development] jamiejako:
I'm on the 22/3 build and I have an issue with phone calls. I can only hear incoming calls on speakerphone. I don't hear anything when I accept the call and have to put it on speakerphone. On the contrary, I can hear outgoing calls just fine through the call speaker, but if I switch an outgoing call to speakerphone, I can't hear it through the speakers and have to turn it off to only hear it through the call speaker. Has anyone else faced this issue? Are there any possible fixes?
[Moto X Android Development] tycoo:
hey guys, i am pretty sure the battery drop is not related to kernel. I didnt merge anything regarding this issue and as i purchased my phone in the middle of last year i recognized the same battery behaviour with cm12.1.

After some research in different battery threads i found out, the battery drop, the long charging time between 90-100% and the observation that the battery stays at 1% a long time before the phone shuts off, is a common issue among different phones and manufactures.

So this is primarly related to pehaps specific batteries and charging technologies, nothing that can be really addressed by a kernel or rom.

The only solution is to let the phone discharge and charge for some cycles to calibrate the battery and to hope that the battery drop become less.

As well i cannot imagine that nfc not working or working is related to a kernel too.
[Moto X Android Development] Soulj4h:
What would you recommend [MENTION=5425708]tycoo[/MENTION]?
[Moto X Android Development] riyosakura:
You need to update your modem and bootloader to the latest version.

Beware, if you using xt1056 with unlocked sim, updating modem will relock the sim and you'll need to revert the modem to the Kitkat version and reunlock it once again.
[Moto X Android Development] jamiejako:
I'm using xt1053. Can you give me links to the updated modem and bootloader? Thank you for the reply.
[Moto X Android Development] Summer Son:
Let me disagree with you.

The battery percentage is calculated from the battery voltage, and if you will observe the battery voltage once you see the 1% remaining, you will see how it will go from 3600 mV or so down to 3400 mV (I don't really remember the actual numbers). My Xperia ZL went down even to 3200 mV as far as I remember. Considering the phone's firmware sees the difference in battery voltage at 1%, why can't we adjust battery percentage to be more precise?
[Moto X Android Development] mafri2:
Is there someone out there who is having the same bug, that using the telephone over bluetooth it goes nuts????
[Moto X Android Development] kelvinmorcillo:
Had a sudden restart and cant get my play store to work. "unfortunately, the google play store has stopped" fixed permissions, uninstalled updates, cache and dalvik clear still nothing :(
[Moto X Android Development] sharukins:
yes and no

this is related to how android calculates battery percentage. to keep it short: android needs the voltage curve from fully charged to completely discharged to calculate the percentage correctly. these values are deleted on a wipe (e.g. when installing a new rom). therefore you have to go through several charge/discharge cycles to get a correct percentage again.
[Moto X Android Development] Summer Son:
I did that many times, maybe even 60% of my discharges are full cycle, just a habit from those days when the Ni-MH batteries had memory effect, but that never improved long 1% run.

I agree there is a some kind of battery calibration, which is also being called as battery statistics, but in my opinion that affects nothing more than a remaining time prediction until full discharge.

Did someone actually fixed this 1% long run by full discharge cycles?
[Moto X Android Development] sharukins:
It is in fact a matter of calibration. If you dig into the characteristics of Li-ion polymer batteries you will find that while discharging they lose voltage rapidly in the beginning while the voltage decrease becomes smaller and smaller the more depleteted the battery is. therefore 1% at the beginning of the discharge cycle can mean a drop of 50 mV while at the end a 1% change in android is a decrease of voltage of maybe 1 mV. For a proper calibration you therefore would have to completely drain the battery until the phone shuts down, but I wouldn't recommend that as it will slowly kill the battery.

The time prediction in android is based on that calibration, how would the prediction otherwise know how low the battery voltage can drop before battery electronics kick in and prevent deep discharge.

Anyway, sorry for offtopic. The bottom line: If you experience a sudden drop in battery percentage or the phone stays a long time on 1% go through several charge/discharge cycles (preferably including one where the phone runs until it shuts down). If the problem persists, report it as bug
[Moto X Android Development] aForcefulThrust:
I could really use some help.. I think my phone is broken and I'm not sure if it's the rom or not. I'm on the 3/22 build and I flashed the modem because I was having issues with hearing people on phone calls. Well the phone worked fine for a while, it had problems charging once before, but then it magically went away.

Well now, my phone will not charge when plugged into usb. But ontop of that, It will not respond or do anything -UNLESS- it is plugged into usb. It will not boot, it will not respond to swipes or unlock, it will not do anything. But as soon as i plug it into usb, it starts to respond and work fine (except it wont charge). And as soon as I unplug USB, it will stop responding to touch and everything.

Even while booting, it boots fine while plugged into usb, as soon as i unplug usb, the boot animation freezes. As soon as i plug it back into usb, the boot animation continues and it will boot.

I'm lost... and to make it worse, I'm offshore on a work boat right now with limited internet. Any ideas would be GREATLY appreciated. Thanks!
[Moto X Android Development] tj13:
I was having charging issues too. It wouldn't charge off my computers USB, but would off the wall charger. My batter life was short too. I choose to change the battery out. But after that I noticed the ear speaker wasn't working. It may have stopped before I did the battery or not. Any way I eventual put the phone back to stock and tried replacing the speaker. Unfortunately is still didn't work. I gave up on my XT1060 dev edition and bought a used XT1096 32gb. I was able to unlock the boodloader from the Motorola site. There are official cm13 nightlies for Victara. I miss the size of the Ghost. It was perfect.
[Moto X Android Development] xabr3:
Will this ROM ever be official?
[Moto X Android Development] riyosakura:
This phone maintainer still busy for another device. We need to be patient, until he has time to maintain this phone again.

But no one know when will the time come.

Edit :

I thought maybe ghost moto x devs are lack of support (donation) from user, so the team cant focus on this device, since there are many other devices with a bigger support need a maintainance to.

I think if we can give a bigger support for cm devs team, we can expect a faster official support from cyanogenmod.

Sorry if im out of topic.
[Moto X Android Development] xabr3:
I am willing to donate if developement will be faster then :)
[Moto X Android Development] omy4069:
ican donate but please give me ur PayPal or whatever to transfer $78 i have to help you continue developing this rom broo
[Moto X Android Development] tinnef:
Yes, "soon":
[Moto X Android Development] riyosakura:
The post has already past a month and a half. Lets hope 'soon' is soon enough.

I've already chat cm13 ghost project leader (ethan chen) through HO, he said, he will check for ghost if he has enough free time. He is still busy on doing something else.
[Moto X Android Development] sharukins:
as always: be patient, most of the developers are working on CM in their

spare

time.

A month and a half is nothing if you're busy at work and want to have at least a bit of social life..
[Moto X Android Development] wolker89:
Hello, I'm new to the forum .. wanted to know if the ROM also serves to verizon version (xt1060)

thanks
[Moto X Android Development] ThunderBolt_BR:
It does, but you must install it from the latest 5.1 official ROM.

[]'s

Enviado de meu LG-V500 usando Tapatalk
[Moto X Android Development] Soulj4h:
This is a good rom but the battery issue bugged me. So I switched to AICP and I don't seem to having that battery issue.

Sent via Moto XT1052
[Moto X Android Development] tj13:
Yes, it works on Verizon model.
[Moto X Android Development] shashank094:
Which Build did u flash?
[Moto X Android Development] Soulj4h:
The latest one for cm13. I believe 03 22.

Sent via Moto XT1052
[Moto X Android Development] shashank094:
I meant which build of AICP :)
[Moto X Android Development] Soulj4h:
Lol. I'm on the nightlies. So the latest one is 0502.

Sent via Moto XT1052
[Moto X Android Development] wizardknight:
Any news on a fix for the 5Ghz hotspot not transmitting on 5Ghz?
[Moto X Android Development] msuab:
Hello all! What about bug with flashlight? This is very important for me. Maybe some people know how fix this problem?
[Moto X Android Development] ThunderBolt_BR:
App

You can use an app to trigger the flashlight on and off, and that works just fine. I use an app called Flash+Free, avaliable at the play store. It is ad free, and get the job done.

[]'s
[Moto X Android Development] miqueletti:
Hi everybody,

i'm using a CM13 based ROM on my X2013 (Ghost). I'm having an issue with teh compass calibration. The magnetic field sensor seem not to be working properly.

Here are some screenshots. The first is before calibration, the second after calibration and the last one just about 30 seconds after it had lost the calibration.

Any clue on what's happening? Any solution?

Edit: I used Tasker to get the info about the sensors. It displays a message "Couldn't get values from sensor". if I do the calibration during the execution of the task it shows me the values.

Thanks
[Moto X Android Development] diago27:
Are you for real?
[Moto X Android Development] Megatron007:
[MENTION=5034190]riyosakura[/MENTION] see whether [MENTION=5808966]abinsur279[/MENTION] audio patch in tesla rom thread solved you're call audio problem or not ?
[Moto X Android Development] riyosakura:
Thank you for your suggestion. I'm going to try it soon.

But from the fact that it (.so files) pulled from cm13, i dont think it will make any differences from cm13 behave.

Do i need to flash tesla rom to test the patch, or i can just flash it on cm13 (im using cm13 atm)?

Btw, i have a workaround that work regarding incoming call issue on xt1056 with unlocked sim.

To answer incoming call to earpiece, i need to push volume button and wait for a couple seconds (about 5 sec), and then incoming call work through earpiece (switch to loudspeaker does not work though). If im not pushing volume button and wait for a couple seconds, incoming call only work on loudspeaker.

Weirdly, it does not have any problem making/receiving call through another apps (Whatsapp, BBM, line, etc). It only does not work with sim card (phone) making/receiving call.

I addressed it as major bug, but i do have a little workaround. And i can live with it atm. Someone said (@mrroks) it does work updating modem to xt1058 lolippp version, but i can't confirm it yet, since i haven't tried it And don't have enough time to reunlock everything if the sim locked following the flash modem procedure.
[Moto X Android Development] Megatron007:
flash it over cm13 and let me know
[Moto X Android Development] riyosakura:
Thank you. I'll try it. And report it here.

Btw, for the wifi always on see screenshot.

Do we have anyway to fix this? I've already tried turn off wifi always scanning, but it seem does not affect anything. It seem drain battery a little, although i'm always ignoring it atm.

It does not behave like this on my moto g using official cm13.
[Moto X Android Development] requiiiem:
turn off WiFi search on location settings
[Moto X Android Development] riyosakura:
This One?

Look like ive already turn it off.

[MENTION=5116201]Megatron007[/MENTION] ive already flashed the Audio Patch from twrp 3.0.0 wipe cache and dalvik, but the problem still persist.

Edit :

Ive already turn it off, but the problem still persist [MENTION=6150522]requiiiem[/MENTION] . Do you have any suggestion?
[Moto X Android Development] ConstantHero:
Keep WiFi on during sleep?
[Moto X Android Development] XdxH62:
my experience

I've been using this version on my xt1052 for some weeks now. Here are the quirks that I've noticed.

* If a call arrives while I use the phone (screen not locked) I don't hear the other person and they don't here me.

* I never have 4G/LTE reception although I live in a city.

* 802.11ac networks (5 GHz) don't show up. This feature was the major reason to buy to phone so it kinda sucks.

* FDE (full disk encryption) doesn't work.

Am I alone with those problems? If not I'd suggest to mention them in the OP.
[Moto X Android Development] omy4069:
bro u only need install Blisspop rom 5.1.1 by megatro n and wait for stable version of cm13

---------- Post added at 03:23 PM ---------- Previous post was at 03:22 PM ----------

the developer is working on this rom to fix these problems bro
[Moto X Android Development] riyosakura:
To fix call issue you need to flash latest modem.
[Moto X Android Development] jay_em:
How does this ROM compare to stock CM 12.1? If I want stability should I just stick with 12.1?
[Moto X Android Development] omy4069:
if u want stability install the stock rom or other rom development by Megatron like Blisspop 5.1.1 is the beat lollipop rom is really stable and have a lot of features, wait for megatron fix the bug of this rom and come back
[Moto X Android Development] js290:
Modem updates may be found here: http://xdaforums.com/devdb/project/?id=10785#downloads
[Moto X Android Development] hawkdown77:
Im getting GPS problems. I can only use GPS with: wifi, 2g, 4g or no connection. If i try use GPS in 3g it dont fix and no signal is found. Any solution?
[Moto X Android Development] js290:
Just started using the 3/22/2016 build on my XT1060, and it is by far better than https://download.cyanogenmod.org/get/jenkins/146437/cm-12.1-20160127-SNAPSHOT-YOG7DAO3J1-ghost.zip. Why is this not part of the official NIGHTLIES from CM?
[Moto X Android Development] riyosakura:
There are some problem on this ROM :

- torch on quick setting tile

- incompatible media codec, which occuring some problem regarding video recording such as noise on video recording, snapchat error, etc.

By far, this is major problem for this ROM i've noticed.

Btw, i never use cm12.1 as my daily driver. Does media codec problem present on cm12.1? I know, torch is working good on cm12.1.
[Moto X Android Development] rtimoff:
I have this problem on all non stock ROMs - AOSP or CM. There is no sound on recorded video, only strange noise.
[Moto X Android Development] riyosakura:
I can record video with voice, although it does have a little noise. But the sound can clearly be heard.
[Moto X Android Development] js290:
Yeah, the torch and codec doesn't bother me, though basic camera recording seems to work fine. What's fixed in the unofficial cm13 is the incessant motorola.motgeofencesvc.MotGeoFenceStateMachine fatal exception when using Waze. And, "ADB Only" under root configuration works as expected. The mute problem still exists though.

From my perspective, cm13 unofficial is a net gain over cm12.1 release. If they're not going to support 12.1, might as well make cm13 part of the nightly builds.
[Moto X Android Development] simar404:
What about the battery drop issue, plz fix this
[Moto X Android Development] KevinCephas:
This is a really smooth and responsive rom however I did notice one or two bugs, the first and most annoying being the clock app, if you open the clock app and try head into the settings menu the app just crashes with a message saying "Unfortunately, Clock has stopped" please fix this. Also another significant bug is the flashlight button in the notification tray, as mentioned before it just turns off after a few seconds of being pressed, please fix this. Those are the main two bugs I've noticed, battery life is okay but standby time is quite disappointing even on power saving mode. The screen cast app is practically useless because the screen can be recorded however when I try to play the video recorded it just says "can't play video". Apart from that everything else is great, YouTube playback works really well and so does now on tap.

Flashed on Moto x xt1052,UK O2 network.
[Moto X Android Development] riyosakura:
Clock setting is working well on my end.

Try change your theme, since maybe theme mess thing up.
[Moto X Android Development] h1ghland3r:
[MENTION=7476411]KevinCephas[/MENTION]

Clock works fine. Flashlight is a well known bug since the first release.
[Moto X Android Development] KevinCephas:
I haven't used any themes and I also cleared the data and cache from the clock app, but it still crashes when I try to head into the settings menus(clock app).:confused:
[Moto X Android Development] js290:
Try Settings -> Apps -> Clock -> Storage -> Clear data. If that doesn't help, try a clean install.

FWIW, cm13 unofficial doesn't suffer from this problem: https://jira.cyanogenmod.org/browse/CYAN-7374

Yet another net positive over the cm12.1 official release.
[Moto X Android Development] mjf042:
Is there going to even be a official cm13 for the moto x?
[Moto X Android Development] lekam8:
Have you tried modify the line "persist.audio.handset.mic=digital" on build.prop?

If you didn't, change with Root Explorer (you must use this app, I tried other and the result was a bootloop) the word digital to analog, save and reboot.
[Moto X Android Development] rtimoff:
No, I have not. I even never know about this method at all, thanks a lot, next time I`ll try when goes to CM. Now I`m on stock modded ROM.
[Moto X Android Development] xabr3:
Any updates on the flashlight and screencast bugs? :)
[Moto X Android Development] riyosakura:
[MENTION=5116201]Megatron007[/MENTION] hey there.

AT&T has pushed new update for Moto X. It mean maybe all variant will receive the same update in the near future.

Does this update will help anything in the incoming development of aosp ROM?

I hope using latest propietary blobs will improve Moto X performance and resolved some of the problem. Or it does not affect the development on AOSP ROM at all?
[Moto X Android Development] h1ghland3r:
It's Google security patch update. Nothing related with Moto.
[Moto X Android Development] riyosakura:
Oh. Okay. ?

Yep, it mainly for security patch. But, who know maybe there are something related to something else.
[Moto X Android Development] otonieru:
The updater binary is still buggy though..., still need to delete the first line,

Anyhow, awesome work!
[Moto X Android Development] rafatosta:
Hello [MENTION=905098]Megaton007[/MENTION], came a new version of xperience kernel, a new version of Hybrid Kenel possible?

http://xdaforums.com/showthread.php?t=3319833
[Moto X Android Development] TeamMex:
If you get that update could send it to me?

I would like to check :D

cheers
[Moto X Android Development] riyosakura:
Unfortunately im not using stock ROM atm and will not revert to the stock at the near future, since ive already using cm as my daily driver.

maybe someone else could help our devs?
[Moto X Android Development] dsiva:
fix for phone dialer app making the phone reboot

Hey, I just wanted write about an issue I had, maybe several of you guys had and fixed it by yourself. It is just that the Phone Dialer app would make my phone reboot every time I try to make a call or when I receive a call. I had to set the Phone Dialer app as default in settings to fix the issue. I had already reinstalled the ROM entirely before trying this simple fix. I am not sure if the issue is discussed here but a search did not any relevant results.

Great work Devs. Thank you.
[Moto X Android Development] js290:
http://xdaforums.com/showpost.php?p=66795452&postcount=1266
[Moto X Android Development] dsiva:
I guess you really didn't read my post. That's fine. I was just posting a fix/solution I found for my issue. :D
[Moto X Android Development] riyosakura:
Yep, i dont see any relation between js290 post and dsiva. :D hahaha.
[Moto X Android Development] phalkon30:
Great find, was having that issue on another phone!

Sent from my SM-G900R4 (klteusc) running CM13 5.22.16 official with xposed
[Moto X Android Development] js290:
My bad, I misread your post. :confused:
[Moto X Android Development] se1961:
Yes I have this problem! Just discovered it today. I have the latest rom, tycoo kernel and I flashed the modems so that I could get phone calls to work. Everything else is working great. But when I have bluetooth connected, and try to make a call, the phone app freezes and ultimately reboots. I also can't hear the call through the bluetooth, although I can hear the dialer. Came back here to see what the fix was. I'm disappointed that nobody else is experiencing it. :crying: Because every other problem had a quick and easy fix. Guess I won't be using bluetooth for awhile.
[Moto X Android Development] cmr_noob:
Yes there is an issue with using Bluetooth while making or receiving calls ...The only workaround is to switch Bluetooth off and then pick up the call