yashsingh1/xdaforums huggingface dataset:
[Moto X Android Development] h1ghland3r:
Hi, again [MENTION=2658922]hachamacha[/MENTION],

Firstly, thank you for being so nice with us!

On CM, the options in Gesture are: Ambient Display (Wake the screen when recieve notifications), Pick up, Hand wave, Camera (Classic twist), Flashlight (Chop).

So, I disabled chop gesture and the wave to wake works as the same (like any CM12.1 or CM13 rom/based rom I've tested). I need to wave at least three times to get my screen on. Sometimes it works on the first time.

Edit: Read the PS in the end of the answer.

When I was on Kit Kat the hand wave gesture was so good T_T. Every movement wake the screen up as it should.

OBS: The 4 bin and 4 txt files are there as you said.

PS: After so many movements, I believe I got how to use it. I had to wait at least 5 seconds before try another wave gesture to work on the first time.
[Moto X Android Development] Gaburieru Pucho:
Can't Flash. It says Error executing Update Binary. My model is XT1052. Please help.
[Moto X Android Development] simar404:
Ur issue is resolved here: http://xdaforums.com/showthread.php?p=65997783
[Moto X Android Development] Gaburieru Pucho:
Thank you!
[Moto X Android Development] riyosakura:
[MENTION=5116201]Megatron007[/MENTION] and all moto x13 (ghost) devs regarding to some unlocked sim phone have a calling problem, such as muted when called or unable to switch from earphone to loudspeaker.

I've made a logcat for the error. Here it is. Maybe it could help to fix the problem :

https://onedrive.live.com/redir?resid=D5185EA6251B9EA3!1514&authkey=!AEjHxkK5k9YTdGc&ithint=file,txt

Btw, the only solution i found is to flash lolipop modem and it should fix the problem.

The problem is on unlocked sim phone, if we flash 5.1 modem the sim will be lock. Ive tried to reunlock it (with 5.1 modem installed) but no hope. I got access denied when executing nv-unlock.

So, i revert my modem to 4.4.2 and unlocking procedure was successfull.

I wonder, is there no way to fix this on sources. Since it work pretty good on cm11 or stock kitkat?

I do believe there is way to fix it on sources.

Im using cm13 on my Xt1056 at the moment.

Maybe just a suggestion or something i need to do to fix the problem?

I hope the devs could figure it out how to fix this problem. Thank you very much.
[Moto X Android Development] Fahadroid:
i m also waiting for solution of above issue !
[Moto X Android Development] riyosakura:
[MENTION=5116201]Megatron007[/MENTION] ive some report that aicp 5.1 rom doesnt have earphone and speaker problem.

I've already installed stock official 5.1 in the past. It behave the same way, speaker and earphone problem.

Maybe the problem is on Lolipop factory image, since maybe cm13 or anyother latest rom build base on moto x lolipop factory image. If aicp 5.1 work then maybe it using 4.4 image as it base to build the rom. That explain why both speaker and earphone are working properly.

I hope moto x devs could figure it out what is the problem with the rom.
[Moto X Android Development] mauri6870:
Can I dirty flash this over cm12.1?
[Moto X Android Development] firiel:
Thanks for this mod, its great to finally put in use this msp430 chip again. One question, as these features (wave2wake, ambient display, twist to camera) work already in CM13, how can I be sure that the mod is installed correctly?
[Moto X Android Development] zwliew:
The features implemented in CM 13 do make use of the msp430. However, the current implementation is made to work with the 5.1 firmware (the sensor IDs are different in 5.1 and 4.4), so I can't guarantee that they the feature controls will continue to work once you revert back to 4.4 firmware.
[Moto X Android Development] Ishaan Gupta:
If we can use msp430, is it possible to bring touchless control back?
[Moto X Android Development] firiel:
If this is correct then there would not be any use for this mod with this ROM. Right?

Are you sure that cm features use the msp430?

Can you provide your sources?
[Moto X Android Development] h1ghland3r:
No. =(
[Moto X Android Development] Saini003:
Remove the line till word ifelse (not the word ifelse) in updater script
[Moto X Android Development] hachamacha:
5.1 stock and 4.4 stock are interchangeable in so far as the register control and upload from ./firmware to MSP430. I've tested that many times. All 5.1 did was change out the code that did wave-to-wake for chop-chop. The part I never knew or looked at was other ROMs, like this one. If the current implementation (as in cm13) is made to work with 5.1, it should work fine with 4.4.4, but you'd have to change the settings (I suppose in ./settings or wherever I said ^^ before). I'm at work and can't get to my Moto X at the moment.

It sounds like what you're saying is that someone actually wrote new firmware for the msp430 to go along with cm13, as that's the only way you'd get triple motionless functionality out of it. That would really be nice to see if you've a link to the msp430 part of this project.

I noticed that, for me, on an xt1060, that with all the cm13 ambient settings enabled, that basically the "move the phone to display notifications" and "double rotate to camera" worked, but not the chop-chop. I figured that made some sense, and I had no idea if it used the msp430 or didn't. Thanks for the clarification.

Like someone else asked: Could you give a link to the source where the firmware is a) uploaded and to b) the code executed when the ambient/gestures settings are changed, and perhaps c) what happens during boot to initially load the firmware to the 430.

Many thanks.
[Moto X Android Development] firiel:
OK but after installing the script, how can I identify if it the wave2wave feature uses msp430 or not? And does ambient display uses it aswell?
[Moto X Android Development] hachamacha:
Unless someone whose a contributor to CM13 (ghost) and knows better comes here and tells us different, I can think of one way to tell you an answer to that:

The link (s) I put out to the wave-to-wake thread where I had a post with the wave-to-wake.zip file also had a link in the same post to "revert-wave-to-wake.zip". (sorry, it's a few pages back. I didn't keep track)

Here's what wave to wake.zip does: It moves the ./firmware from 4.4.4 over the ./firmware from 5.1 (if it exists, else it just writes files to /system/etc/firmware).

And revert-wave-to-wake.zip: It does the opposite, but it always moves the ./firmware from 5.1 into /system/etc/firmware, overwriting identically named files if it's there.

SO:

If you use revert-wave-to-wake, you can do a test and see if chop-chop suddenly starts to work. The only way it can be working is from the msp430 if you're just using the cm13 + my revert file because that's the only place that ./firmware code can run on a motoX.

When you're satisfied (or not) , then just re-use the wave-to-wake file again because there's no limit as to using, re-using the two files.
[Moto X Android Development] regisknechtel:
Is there any workaround to this wifi not auto connecting bug? I don't want to go back to the older build with the auto rotation bug :(
[Moto X Android Development] Fahadroid:
Speaker / earphone bug solution ?

Any one find speaker / earphone bug solution ??
[Moto X Android Development] Fahadroid:
[MENTION=6293373]Haidersaleem[/MENTION] : bro .. how did you resolved earphone / speaker bug ???

what bootloader / modem files you flash via fastboot mode ?

which rom are you using ?

do u using xt1056 sprint ..

Please tell me details !
[Moto X Android Development] mlodykaras:
Megatron are we going to get a fix for that wifi bug anytime soon? I'm thinking about going back to cm12.1 because it drives me crazy! It wouldn't be a problem for me if I only had to manually connect to the network. Wifi just drops by it self all the time. Other than that I can live with the small bugs still present in this build. Please! Make me smile again hahaha :P ;)
[Moto X Android Development] zwliew:
No, firmware wasn't written for it.

I wasn't the one who originally wrote the package and jni ioctl calls that call the msp430 sensor (Ethan was) but I've skimmed through it a couple of times. So I'm working off what I got from the code.

Here is the app and jni library source code: https://github.com/CyanogenMod/android_device_motorola_msm8960dt-common/tree/cm-13.0/doze

In one of the changes, Ethan updated the sensor IDs to be compatible with the 5.1 MSP430 firmware instead of the 4.4 firmware: https://github.com/CyanogenMod/andr...mmit/82adebb1cb25fc879a622d2ffc84b14ef838afe8

I'm assuming this makes the library incompatible with the 4.4 firmware. Along with it, chop chop support was also added.

Anyways, for me, all the gestures supposed to work on stock work on CM13.
[Moto X Android Development] riyosakura:
No one here capable of helping us? unlocked sim XT1056 Moto X user?

Im desperate for help because this is one of the major bug that need to be solve. :(

I hope some one will help us.

[MENTION=5116201]Megatron007[/MENTION] and all Moto X Devs.

This is only calling and receiving logcat. It should help us to get rid of the problem.

When calling the sound can be heard from the earphone (earpiece on the logs), switching to speaker will make the phone mute, both microphone and the speaker.

When Receiving, earpiece make the phone mute, both microphone and the earpiece (the sound cannot be heard), while switching it to speaker make the sound can be heard and microphone working.

I hope somebody can figure how to fix it out. :(
[Moto X Android Development] Megatron007:
CDMA ?
[Moto X Android Development] riyosakura:
Yep im using XT1056 Sprint. It should be for CDMA card. But i've already unlocked it and i'm capable of using GSM.

I've read the entire forum, the only way to solve the problem is by updating the modem, NO-HLOS and fsg to the latest version to match the latest bootloader (i've already have 30.BE). But flashing both of it will resulting my device sim locked. I try to unlock it, but no hope. there is no way to unlock the latest modem at the moment. The only way to reunlock the sim is to revert back to the older modem and reunlock it the famous method on the general thread.

So that, I think fixing it from the sources maybe the only way to fix the problem.

i've attached the logcat maybe there is something over there to fix the problem. :(
[Moto X Android Development] Megatron007:
as i dont own a cdma variant idont know much about this stuff ..let me check if i can do anything or not and can you send me logs in pm ?
[Moto X Android Development] simar404:
[MENTION=5116201]Megatron007[/MENTION] i hope u r aware of wifi issue and my device also reboots suddenly and also have sudden battery drain issue. However the sudden reboot issue started after i flashed [MENTION=2658922]hachamacha[/MENTION] 's wave to wake mod. May be [MENTION=2658922]hachamacha[/MENTION] u could put some light on sudden reboot issue.

I have attached sudden battery drain screenshot below:
[Moto X Android Development] Haidersaleem:
[MENTION=5826827]fadyrox[/MENTION]

I have xt1060.

I think modem problem is existing only with xt1056.
[Moto X Android Development] h1ghland3r:
If you started having random reboots after the mod, just flash the revert mod provided.
[Moto X Android Development] hachamacha:
[MENTION=5604178]zwliew[/MENTION] ; Thanks much for the updates & links , info, etc. Much appreciated. By the way: "Ethan" : I'm guessing he is this guy: Ethan Chen aka intervigilium(in the Gerrit world? Is that right?

[MENTION=6890013]simar404[/MENTION] : Hi and I haven't experienced a single reboot in what feels like a couple of weeks of using the latest .zip of cm13. Of course, we've got different apps, phones, etc so it's not apples to apples. It seems far-fetched that anything including utter BS loaded into the 430 would be responsible for a reboot, but no doubt it must be possible.

Like highland said: If you just use revert-wave-to-wake, you'll be back at square one assuming you started from 5.1 before the update to this Cm13 ROM. If it was the msp430, then reverting should fix it. (well, revert, reboot, etc). I'm thinking I should stop wasting so much of this thread on this topic since it's not a) life or death and b) cm13 is clearly trying to implement it's own version and if I have time to work on this again in the future, I'll just take any output over to the cm13 world. Cheers.
[Moto X Android Development] simar404:
Tnks so much [MENTION=2658922]hachamacha[/MENTION] for the info i flashed the revert will see now how things go

I really appreciate the time and hard work u put on for ppl like us

Thank you
[Moto X Android Development] Fahadroid:
[MENTION=5034190]riyosakura[/MENTION] : You explained that bug very well

Now waiting for solutions from Dev & [MENTION=5116201]Megatron007[/MENTION]

---------- Post added at 10:22 AM ---------- Previous post was at 10:05 AM ----------

_____________________________________________________________________________________________

i have same bug which [MENTION=5034190]riyosakura[/MENTION] tell you on cm13 thread !

i upgraded 30.BE boot loader

Modem i m using 4.4 stock

Details :

1-i got earphone / speaker bug, searched a lot.

2-downloaded modem files from here xt1056 sprint :

http://xdaforums.com/moto...hable-t3155843

XT1056 Sprint (Version: 222.26.10.ghost_sprint.Sprint.en.US)

Modem Firmware (http://xdaforums.com/devd...t/dl/?id=16267)

3- flashed all files (which were in xt1056 modem zip files) NON-HLOS.bin / erase modemst1 /erase modemst2 / flash fsg fsg.mbn / flash boot.

4- bootloader updated from 30.B7 to 30.BE got sim locked

5- flash 4.4 stock modem files & used nv item reader soft to unlock sim.

6-sim unlocked but earphone / speaker bug still exist !

see further details

phone : xt1056 sprint (using sim Telenor GSM)

ROM: AICP MM ROM FROM YOU !

BOOTLOADER: 30.BE

MODEM FLASHED : ghost_sprint_4.4.2_modem.ZIP

BASEBAND : MSM8960PRO_BP_2323.031.111.00R

[MENTION=5116201]Megatron007[/MENTION]

i am really hoping that me & [MENTION=5034190]riyosakura[/MENTION] will get solution soon !
[Moto X Android Development] Kiristiba:
Isn't your solution written all over the place?

You need to flash modem firmware from 5.1 final stock rom.
[Moto X Android Development] Fahadroid:
i have xt1056 sprint ... i flashed modem firmware of 5.1 (Sprint) & it locked my sim ..

this is a link where i downloaded sprint modem files & rom !

http://xdaforums.com/moto-x/development/xt1053-retail-stock-lollipop-flashable-t3155843

Which final stock rom (modem files) i should use to get rid this bug !

can you give me link ??

Please share some more details !
[Moto X Android Development] whizinc:
Your problem is that your phone was unlocked through software method and not by the official sim unlock method! So you will always get sim locks. I also have the XT1056 Sprint variant and i dont have any kind of bug that you're constantly posting about. Give the developers a break please. The help they're providing us for free is already more than any human can help. I repeat your problem is: Your phone wasnt unlocked by the official method. I am also from Pakistan and i know that alot of people unlock phones by software method to safe money and time. Hope this helps. Peace. Again i repeat i have the same XT1056 and i dont have these bugs in any MM rom. Dont know about Aicp tho because im waiting on the new build to come out without the google FC bug.

P.S: My XT1056 was unlocked through official sim unlocking code method.
[Moto X Android Development] ysop:
reflashed it.

but do NOT run

fastboot erase modemst1

fastboot erase modemst2

just run

fastboot flash modem NON-HLOS.bin

fastboot flash fsg fsg.mbn

fastboot reboot
[Moto X Android Development] Fahadroid:
you mean .. sprint modem files .. which is in following links ? right ?

http://xdaforums.com/moto-x/development/xt1053-retail-stock-lollipop-flashable-t3155843
[Moto X Android Development] ysop:
http://xdaforums.com/devdb/project/dl/?id=16267

try.
[Moto X Android Development] Fahadroid:
Thanks for you details reply .. if you see all threads .. you will find people .. who are keep asking regarding this bug !

what i got from your msg that wait untill someone find solution !

1 thing i want to clear that this bug is just in MM rom while aicP LP rom was not have that bug !

now i m thinking to go back to lollipop :( because this bug is being discussed from many times but no resolved yet !

---------- Post added at 03:54 PM ---------- Previous post was at 03:49 PM ----------

[MENTION=5244685]ysop[/MENTION]

this a same file when i flashed i got sim lock .,,,, !

what i did in past is :

$ fastboot flash modem NON-HLOS.bin

$ fastboot erase modemst1

$ fastboot erase modemst2

$ fastboot flash fsg fsg.mbn

$ fastboot reboot

i got bootloop so i flashed :

$ fastboot flash partition gpt.bin

$ fastboot flash motoboot motoboot.img

$ fastboot reboot

(it was written on that thread that i if you get error / boot loops just flash partition/mootoboot.img)

after that bootloop gone & phone booted successfully ! but got sim unlock ..

at your message i found i should not have been flashed modemst1/modemst2

$ fastboot erase modemst1

$ fastboot erase modemst2

right ??

do i need to reflash as you said above ??

are you sure my sim will not be locked ??
[Moto X Android Development] whizinc:
i can understand your problem, but what i cannot understand is that i have the same variant and im not facing these bugs. I guess i bought the phone with the 5.1 stock installed and the seller also said that my phone was unlocked through official method. I think the only solution for you is to Flash the Whole phone from RSD LITE, that will give you a clean end to start your work from. It will get your sim locked again but atleast you will have the Clean 5.1 stock installed on your phone. If you're interested in it then take a good look on my thread which i posted on how to revert to stock means deleting all the partitions of your phone and reflashing everything again to get a new start

Here's the link of my thread. I explained everything in detail and its a noob proof thread so anyone can perform it.

http://xdaforums.com/moto-x/general/guide-newbies-how-to-revert-to-stock-t3104208
[Moto X Android Development] ysop:
now that your bootloader have been updated,so just run as I said

fastboot flash modem NON-HLOS.bin

fastboot flash fsg fsg.mbn

fastboot reboot

i only can confirm if i dont want my sim locked in china,I shouldnt run

$ fastboot erase modemst1

$ fastboot erase modemst2

so i just said "try".not sure.
[Moto X Android Development] Fahadroid:
REally thanks for your help ..

i will try & will give you feedback ..

Again Thanks !

---------- Post added at 04:28 PM ---------- Previous post was at 04:25 PM ----------

adding [MENTION=5782800]whizinc[/MENTION]

What you think about above flashing .

will it lock my sim ???
[Moto X Android Development] diago27:
Any news about when official nightlies will begin? Also, can I use this as a daily driver?
[Moto X Android Development] sharukins:
official nightlies will start as soon as the torch bug has been resolved, according to the following link:

https://review.cyanogenmod.org/#/c/136249/
[Moto X Android Development] diago27:
Also is the WiFi autoconnect bug an isolated bug or is it affecting everyone?
[Moto X Android Development] sharukins:
I don't know exactly, cause I'm not using the ROM, just following the development via:

http://review.cyanogenmod.org/#/q/project:CyanogenMod/android_device_motorola_msm8960dt-common+branch:cm-13.0

and:

http://http://review.cyanogenmod.org/#/q/project:CyanogenMod/android_device_motorola_ghost+branch:cm-13.0

but I don't see any wifi patches, so if it's a device specific bug it's probably not yet fixed
[Moto X Android Development] h1ghland3r:
The Wifi bug is not isolated =(
[Moto X Android Development] hachamacha:
In the Gerrit review, I don't see the things that might be more important that the torch (when using built in "tile") bug. Any third party widget is a workaround for that anyway. The review page causes me to wonder whether all current "ghost/cm13" bugs (which aren't very many) came from cm13 work, or whether some of them came from this local build as well. It's tough to know where to try to mention things without knowing that.

I probably don't have a good understanding of what "unofficial" versions of cm13 consist of. Anyway: I would prioritize some glitches (that I can recall anyway) as follows:

Priorities for bugs I've seen in current cm13/ghost:

1) DHCP unable to reconnect to WIFI. (This one seems fairly large, and has no easy workaround aside from manually connecting, static IP, etc)

2) Chromecast (also only as a built-in tile) : Not a biggie since ( like flashlight), you can get things working just using chromecast from the play store. (e.g. Netflix/Amazon/some others, all work well to my TV & ROKU).

3) that whole wave-to-wake/motion-detection/chop-chop world of little problems: Working on it, but I don't see it mentioned other than in this thread.

4) torch: (only as built in tile): Not a biggie, but sure, should be fixed, but I'd prioritize it as last rather than make it seem like it's why cm13 /ghost isn't going official.

5) was there Bluetooth problems? I've not been using it for anything so don't know but I'm sure it was mentioned.

There's a few other things that I've not personally experienced that are in this thread. I only use this as a dev phone for work projects these days with occasional skype calls, so I'm sure I've missed seeing other bugs.

I logged into Gerrit and was going to add a line to the review but realized that without knowing if these problems exist in the build Gerrit looks at that I shouldn't add anything unless I know we're both looking at similar builds. I guess I'll just bite it and download yet another huge ~40GB git(cm13) to my linux box.. ;;)
[Moto X Android Development] firiel:
Thank you for your contribution so far and I think this is a subject for the general feature. If you could maintain a topic there, that would be very helpful and positive for the community.

Also for others, my wifi works just great.
[Moto X Android Development] hachamacha:
It's also not a problem in everyone's implementation of 6.0.1. I've mostly read about it on the 5x and here, maybe a couple of others.

OR: Is it way more widespread than that and I just don't know it? I'm sure that's possible & likely. Somewhere a few (or more) pages back in the thread, I pointed to the issue base (Google's) where someone named Dan said it was fixed about 3 months back. Fixed for what and implemented for what, I have no clue..

---------- Post added at 11:41 AM ---------- Previous post was at 11:35 AM ----------

Thanks, [MENTION=456259]firiel[/MENTION] :

Question: When you say "my wifi works just great": 1) are you using the lastest build. 2) Sorry if I missed this, but which model phone do you use? (xtXXXX?) and 3) your phone does "disconnect" now & then right? 4) Which type of connection are you using mostly (WPA, OPEN, others?)? Any other info?

If your phone hasn't disconnected (which is normal) , then could you please just crank up a logcat >> {somefile} and during the logcat, disconnect wifi by turning wifi off. Then turn on wifi without selecting anything to connect to. Whether it connects or not, could you attach or PM me your logcat for about a minute following the disconnect & connect (or whatever it does for you).

Thanks.