yashsingh1/xdaforums huggingface dataset:
[Moto Maxx Original Android Development] ChazzMatt:
Well, glad we sorted that out. :p

But at least we got to the real issue -- your unfortunate Smart Lock options are keeping your display unlocked. Thus, you are accidentally sending text messages/"ass dialing" with an unlocked/active touchscreen display --- and for some reason blaming Ambient Display, when Ambient Display is only relevant and working when your display is locked.

It's like blaming the dog for eating your homework and the dog wasn't even in the room.

Anyone who does not have "on body detection" enabled would not have this problem. It has nothing to do with Ambient Display and everything to do with which Smart Lock options are chosen.
[Moto Maxx Original Android Development] brennam7:
Possibly dumb question...

I have ambient display turned on (latest nightly) and i have my lock screen set to swipe. But none of the display actions are working. Am i missing something?

Also, if i wanted to go to moto display, is there any apk for it? I've done a bit of searching, but nothing has turned up.
[Moto Maxx Original Android Development] Gambler_BE:
God dammit [MENTION=3250376]ChazzMatt[/MENTION]. I know you contribute a lot to the xt1225 forum and make a lot of useful posts. But, pardon my language, you can really be an ass sometimes!

This has happened before, where you treat someone with a question like they're idiots with an IQ of 10. [MENTION=6082582]quantum tao[/MENTION] knows what you're saying, but it's not what is causing the problem.

I'm in the exact same situation. I have smart lock enabled with my moto 360. This DOES NOT remove the lock screen. It just removes the pin, but I can still lock my phone, ambient display still works, except that I unlock my phone by swiping, instead of entering my pin. And no the on body detection thing is not turned on.

Like [MENTION=6082582]quantum tao[/MENTION] mentions, ambient display will sometimes light up in your pocket. If your trousers are thin enough the screen will detect a "touch" from your leg and then the fun can begin, where if you're unlucky it'll swipe to unlock and even send texts, pause music,...

Sure, once the screen is unlocked the texting is not happening because of ambient display. However, it all starts with Ambient display lighting up when it shouldn't, causing the screen to respond to your leg.

I hope this post describes what happens in a way where you can understand and accept that it's not just the fault of our settings.
[Moto Maxx Original Android Development] quantum tao:
Thank you. Ok, i will go back to being dead now. :cool:
[Moto Maxx Original Android Development] junior_ilha:
[MENTION=2342630]Gambler_BE[/MENTION] you're right, sometimes it's better exercise our silence than be rude, but you can't also blaiming some function without knowing how to properly configure it.

Peace.
[Moto Maxx Original Android Development] Gambler_BE:
Sure, that's definitely true. But in this case it doesn't seem to be a configuration problem. It seems like the algorithm just doesn't take as many factors into account as moto display did. This results in turning on the screen from which I assume is movement in your pocket, without realizing it's in your pocket and not being turned over on a table.
[Moto Maxx Original Android Development] Skrilax_CZ:
[MENTION=6082582]quantum tao[/MENTION] was correct, there is a bug, where you can get a doze when the phone is stowed, when the IR sensor gets excited (looks like it got missed in the rewrites). Fixed. Also did checks on the chop chop, looks like perhaps people at Moto found it not stable enough (let's see what they put to final SW, since soak #3 doesn't appear to be final after all), but anyway I put it back as it doesn't seem to behave differently than it used to be.
[Moto Maxx Original Android Development] cdudeman:
Is there a new nightly that has these fixes? I see 5-24 nightly as the latest on the download page.

thanks!
[Moto Maxx Original Android Development] quantum tao:
Next nightly. https://www.cmxlog.com/13/quark/
[Moto Maxx Original Android Development] ChazzMatt:
The errant texting and butt dials is what he is blaming on Ambient Display and he's wrong. He had a pass code on Ambient Display, so it was IMPOSSIBLE to be sending a text. Finally he's admitted to using Smart Lock -- and THAT is what is causing the problem.

People have the exact same issues with Moto Display when using ON BODY DETECTION Smart Lock.

MOTO DISPLAY AND SMART LOCK

http://phandroid.com/2015/08/05/moto-g-2015-first-things/

If you unlock your display, not matter using Moto Display or Ambient Display, neither one is on. And you can butt dial and sent texts. The options being used in Smart Lock is the issue here.

If you say Ambient Display can light up while in your trousers, I will not disagree with that. There are pick up/stow option you can turnoff if it bothers you too much.

If you say Ambient Display will dial phone number and send texts you are wrong. The only way you are sending texts is if your phone display is unlocked and it also happens with Moto Display and Smart Lock (on body detection option). They are both lock screen displays.

---------- Post added at 10:26 AM ---------- Previous post was at 10:09 AM ----------

I do not disagree Ambient Display may light up in your pants. Not making a joke there, by they way.

And I even admitted if he had swipe to unlock maybe that was the issue. He said no, he had a passcode.

OK, now Ambient Display and Moto Display are no longer on the table. They are lock screen displays. Do you understand that? If he's sending texts, his screen is not locked and he has a passcode to unlock his screen. So WHAT is unlocking his screen? (Hint, it's not Ambient Display and it's not swipe in Ambient Display)

So, how is his screen becoming unlocked? OH! Then he admits he's using Smart Lock -- probably with on body detection. Duh.

And guess what, people have complained about Moto Display doing the EXACT same thing.

Because you are unlocking your screen and sticking it in your pants and keeping it unlocked. So, any pressure on on active touchscreen will launch apps, send texts, etc. And Moto Display will do that too, because Moto Display also unlocks with on body detection in Smart Lock. I quoted a tech writer above who had the exact same issue with Moto Display.

I'm specifically refuting the errant phone calls/gibberish texting being blamed on Ambient Display.
[Moto Maxx Original Android Development] quantum tao:
Wow
[Moto Maxx Original Android Development] drizzzzzz:
chop chop looks like it's back
[Moto Maxx Original Android Development] RanonBR:
NFC Smartlock Issue and Miracast Issue

But, Sirs, I'm having a possible issue with the smartlock. I'm using NFC tags to unlock my xt1225 by touch my wallet that have a tag inside.

Tried to use a tag outside my wallet too, and tried other types of tags.

But, for the first try it's go ok. But, if phone locks, no more is possible to unlock using NFC.

This problem was rarely on stock 5.0.2.

Other issue:

- Green screen when using miracast's screen mirroring.

I have tryed at my TV, my WDTV and always get Green Screen.

I don't have a chromecast. Only use miracast feature.

And the problem doesn't occurs on the stock 5.0.2.

Is this issue only in quark or it's at all cm 13 distributions?

Is there a workaround? I will love to solve that to play emulated games using a Bluetooth controller and my TV!

Thank all of you!
[Moto Maxx Original Android Development] Gambler_BE:
[MENTION=3250376]ChazzMatt[/MENTION] I'm going to stop responding as long as you treat this as if it's a criminal trial. "he admit's... " sounds a bit dramatic, no?

You realize Skrilax already answered right? Confirming that the IR sensor was set too sensitive causing the screen to light up in our pocket. So yeah, I think we're done here. I haven't installed the latest nightly yet but sounds like Skrilax fixed it. Now both [MENTION=6082582]quantum tao[/MENTION] and me can use ambient display, in combination with smartlock again, hopefully without pocket dials. And no I don't have the ****ing on body detection on, and quantum tao never said he had it on either, you've just been assuming that the whole time.

Lots of love <3

---------- Post added at 04:41 PM ---------- Previous post was at 04:37 PM ----------

I can't help you with the NFC thing, I've never tried using that.

I'm pretty sure the miracast is a known bug. Not sure if it's just quark or all cm13. If I remember correctly it took a while on 12.1 before screen cast worked correctly, and even then it wasn't always super smooth. So I don't think there's anything you can do to fix it until the dev finds a solution.
[Moto Maxx Original Android Development] cdudeman:
I installed the 5-26 nightly and wiped everything beforehand. When it finally boots it will not show any notifications and the quick toggles are gone. I have tried installing the 5-24 nightly as well and had the same thing. I have wiped and reinstalled twice with the same results. Even when I know I have a notfication it shows nothing. Any ideas?
[Moto Maxx Original Android Development] quantum tao:
What else are you installing?
[Moto Maxx Original Android Development] cdudeman:
Only other thing i installed was gapps. (open_gapps-arm-6.0.1-stock-20160422.zip)

Just installed only the rom and works fine. Guess my gapps dont like this. Thanks for the idea.
[Moto Maxx Original Android Development] quantum tao:
I always use the newest nano, i dont need all the extra google apps but i can still install them from the store if i want. I also flash rom and gapps at the same time.
[Moto Maxx Original Android Development] jdl512:
I am on the may 24 nightly and don't have these issues. They were in the late April nightlies, but were fixed in a week or so. Verizon turbo.
[Moto Maxx Original Android Development] cdudeman:
It was my gapps. I am using the latest nano gapps now and it is working fine.
[Moto Maxx Original Android Development] quantum tao:
yippee! i actually helped someone. see, i dont always just complain.
[Moto Maxx Original Android Development] Dark Obsessions:
is there any way to remove the root sign from the status bar ?
[Moto Maxx Original Android Development] RLShiftyDoggit:
There is a xposed module that will do it says CM12 but it worked on CM13
[Moto Maxx Original Android Development] anishmohandas:
[MENTION=2228410]Skrilax_CZ[/MENTION] any chance of Gello browser making it into moto Maxx builds?? And it replacing default browser??
[Moto Maxx Original Android Development] ChazzMatt:
You can download Gello yourself and install:

http://www.apkmirror.com/apk/cyanog...-42-0-2311-1179-c5cc6d7-android-apk-download/

Any app you have on your phone you can make the default for it's action.

Just like I make Chrome my default browser, although I have a couple of others installed also.
[Moto Maxx Original Android Development] emi.guego:
Hi everyone, I got the next problem:

Maybe since mid May builds I can't use the Theme Engine, I don't know why. I was using Xposed so immediately I disabled it but still couldn't use it. I thought it could have been that build so I have been installing updates since that but I still can't use it.When I select the theme section on the Settings it just tell that the Theme app stopped. Any idea of what could be causing the problem?

Thanks!

PD: Sorry about my English, greetings from Mexico.
[Moto Maxx Original Android Development] anishmohandas:
Yes, I am aware of that... As per cyanogenmod blog the device maintainer needs to enable Gello to be available for the particular device. So was just asking are their any plans to enabling it for our Moto MAXX [emoji4]
[Moto Maxx Original Android Development] ChazzMatt:
Really? You can't just install the apk? OK.

Many people are using this build:

http://xdaforums.com/android/apps-games/app-gello-browser-t3295743

and here:

http://xdaforums.com/android/apps-games/app-download-t3384244
[Moto Maxx Original Android Development] Skrilax_CZ:
Finally, kernel source is up:

https://github.com/MotorolaMobilityLLC/kernel-msm/releases/tag/MMI-MPG24.107-70.2
[Moto Maxx Original Android Development] quantum tao:
Using bhb27's version now on official cm13. So far so good.
[Moto Maxx Original Android Development] Skrilax_CZ:
Not sure if you understood - Motorola released official kernel source for stock 6.0.1. By the way, notice the commits from May 2016 and the tag MPG24.107-70.2.
[Moto Maxx Original Android Development] quantum tao:
Yes, and butcher already modded it.

http://xdaforums.com/moto-maxx/development/kernel-bhb27-kernel-t3207526/post67278098#post67278098
[Moto Maxx Original Android Development] koftheworld:
Any applicability to Verizon users? In particular, I was wondering if this might help the volte situation on custom roms for Verizon users?
[Moto Maxx Original Android Development] fgl27:
I get last Friday off so I start to work on that when moto released it.

I used yours change to 5.1.1 source to CM 13 tree to make it work, those display changes you did are need...

Did not update linux to make it faster and to try without then with latter, then compare.

I off selinux too for a propose of making a universal kernel to all ROM with that enable I had no luck to make a unified version that fully work the way I wanna...

I move thermal-engine to system/bin to make it work from vendor it doesn't, I like it is better then the kernel thermal driver, but selinux doesn't like it I see some warning about it, as I off it no problem for me.

Moto f2fs is fine, but Moto wifi driver is soak 4 radio.image only, I use the latest wifi from CAF to make it work...

Moto enable Zram, and add that to fstab, and on fstab they add f2fs to data and place it on the top of ext4 data, don't know if that gives priority in case of data formatting for the system.

I notes when I erase the data partition on bootloader a data that is formatted as f2fs, them boot on custom ROM it will be formatted as ext4 after the ROM finish boot, don't know if that is because you place ext4 on top or not, didn't test after changing f2fs to the top, but some day I will, just didn't had time to make full backup of internal and test this...

Moto add a PowerHAL, I believed on those power 8084 libs, it works with they kernel and interactive cpu gov, mpdecision and thermal-engine, I didn't test on custom but that may work well on CM as you make it to work on they stock kernel config... But don't know it that can have a good effect as the OS, frameworks, hal etc are different...

I know some of this you already know but it may help your process, check the tree I have work in here

https://github.com/bhb27/android_kernel_motorola_apq8084/commits/NEW

When you update the tree if I find some thing to add/change I let you know... :good:
[Moto Maxx Original Android Development] vinydasilveira:
I'm having some problems with the camera and flash. Sometimes when I restart my Droid Turbo, or just the battery completely, the camera and flash simply stop working. I can only solve formatting the ROM. I am using the 06/11
[Moto Maxx Original Android Development] RLShiftyDoggit:
What do you mean by "or just the battery"
[Moto Maxx Original Android Development] vinydasilveira:
"when the battery reaches 0%" I'm sorry, I ended up eating a few words at the time to translate.
[Moto Maxx Original Android Development] RLShiftyDoggit:
I have no issue w it if your using stock kernel I'd try using the BHB27-kernel see if the problems persists change the camera app
[Moto Maxx Original Android Development] vinydasilveira:
But I changed my camera. Not solved. I can only solve with the factory reset
[Moto Maxx Original Android Development] RLShiftyDoggit:
Change your kernel to the BHB-27 kernel that fails try Resurrection Remix ROM
[Moto Maxx Original Android Development] vinydasilveira:
I'm using the BHB-27 kernel
[Moto Maxx Original Android Development] RLShiftyDoggit:
I'd suggest changing the ROM i have no issues w RR
[Moto Maxx Original Android Development] vinydasilveira:
I'll do a test in the future. I noticed that this problem is related to data. Doing wipe data solves. However I tried to manually clear the data from the camera and any other related app, but not resolved. And whenever I give only wipe cache and dalvik by TWRP 3.0.2-0, not all apps are optimized. I'll do a clean install of CM13 06/15, but will not install the BHB-27, to see what happens after a few reboots during the week.
[Moto Maxx Original Android Development] RLShiftyDoggit:
Wipe everything cache data and internal and start all over
[Moto Maxx Original Android Development] iiWoodstocK:
I wouldn't wipe Internal Storage. Then he'll have to use fastboot to flash a ROM. Internal Storage shouldn't be causing any issue, but wiping /data will definitely narrow down a cause. [MENTION=5623977]vinydasilveira[/MENTION]
[Moto Maxx Original Android Development] RLShiftyDoggit:
No he won't all he has to do is mount in twrp then move the files on then flash I've done that myself
[Moto Maxx Original Android Development] iiWoodstocK:
Eh, forgot about that. But wiping Internal Storage is pretty much unnecessary.
[Moto Maxx Original Android Development] RLShiftyDoggit:
It can help sometimes (very rarely though)
[Moto Maxx Original Android Development] vinydasilveira:
I found causing the problem, at least in my case using the CM13 and the camera app from Motorola.

"Temporal Noise Reduction" this is the name of the problem. I believe that regardless of being a Custom ROM or stock, enabling this option in the "secret" menu tab on motcam will cause a conflict and causing the camera / flash become disabled. In my case, the way I found was to format the phone, because the problem is in the "data". And yes, I exclude several datas manually mainly from own motcam but not resolved. I wiped the settings, the SystemUI, and nothing. I tried to change camera after completely uninstall the motcam and nothing has changed. Yet I make more tests to find the file on the data that it may become corrupted when enabling Temporal Noise Reduction.
[Moto Maxx Original Android Development] c3pbl4:
Hello.

I have xt1225 moto maxx * 6.0.1 soak 3 stock root * from here

I want to flash 6.0.1 CyanogenMod 13

What I did

Everything from 1st post (link)

I tried to flash last nightly (cm-13.0-20160618-NIGHTLY-quark.zip) and earlier (cm-13.0-20160614-NIGHTLY-quark.zip)

I flashed with all wipes in TWRP - all boxes checked

Flash process good, I saw desktop.

But smth wrong with calling part - when smb call me or when I try to call smb, smartphone reboot. After reboot I see no carier service.. I see carrier service only after reflashing.

I tried to flash different modems and radio via bootloader, but unhappy.

Befor Soak3 I have CM from this thread during 1 year and everything work fine.

Please help me.

I thing smth wrong I do with radio or modem
[Moto Maxx Original Android Development] iiWoodstocK:
Settings -> Apps -> gear icon (top right) -> Default apps -> Phone app -> select "Phone" (should be the only option)

If your GApps package installed Google Dialer, you have to manually select a phone app. The above will set your default phone app.
[Moto Maxx Original Android Development] kingersj1:
What gapps did you use? Sounds like open gapps. They have Google Dialer framework in the package for our phone, you have to go into settings and set the default dialer. Check their blog for more details and a video for how to set default.
[Moto Maxx Original Android Development] c3pbl4:
Yes, open_gapps-arm-6.0-stock-20160618.zip

Thanks.

I will try.
[Moto Maxx Original Android Development] quantum tao:
I use nano, never have a problem. You can add the other stuff from the store if you want it after.
[Moto Maxx Original Android Development] c3pbl4:
Ok. Thanks. I will try nano.

Stupid question, our smartphone's platform is ARM or ARM64? I forgot. Sorry
[Moto Maxx Original Android Development] quantum tao:
Arm.
[Moto Maxx Original Android Development] mentality513:
Using this rom on a verizon droid turbo. Anyone able to get xposed working? Downloaded latest Sdk 23 arm release for framework and install via TWRP then install apk and I'm getting "Xposed is not (yet) compatible with android SDK version 23 or your preccessor architecture (armeabi - v7a)".

Any help is greatly appreciated.
[Moto Maxx Original Android Development] quantum tao:
http://dl-xda.xposed.info/framework/sdk23/arm/xposed-v85-sdk23-arm.zip
[Moto Maxx Original Android Development] Cobra04:
Make sure you use the 3.0 alpha apk (below). Had the same problem

http://xdaforums.com/attachment.php?attachmentid=3383776&d=1435601440
[Moto Maxx Original Android Development] ChazzMatt:
I was going to suggest that -- that installing xposed in the post-Kitkat era is actually installing TWO parts, not just one...

But I didn't know if that was still necessary. It's been a year since I used xposed, I haven't really kept up with it. I thought by now they would have improved it by now, to make it more a seamless all-in-one installer. After more than a YEAR, why is it still called "alpha"? :silly:
[Moto Maxx Original Android Development] mentality513:
That was exactly my problem. Figured it out via another forum. Thanks!
[Moto Maxx Original Android Development] c3pbl4:
I did it.

I install nano open gapps and everything works fine.

@ quantum tao

Thanks.
[Moto Maxx Original Android Development] siberian85:
Anyone tried or know if TV out is working properly I am on xt1250 but would figure is the same on cm 13 just don't know if would work
[Moto Maxx Original Android Development] mrkhigh:
TV out?! You mean screen mirroring?
[Moto Maxx Original Android Development] guguts:
Can anybody that has been using this ROM to give input on how it is?

Is it better than stock firmware? Battery life equals/surpasses stock?

I just adquired a moto maxx, and im a big cyanogen fan, but i don´t wanna risk to sacrifice battery life.
[Moto Maxx Original Android Development] mrkhigh:
It seems comparable. I did not note any real change.
[Moto Maxx Original Android Development] siberian85:
Seems that cell radio drain is still present
[Moto Maxx Original Android Development] mrkhigh:
101% .....
[Moto Maxx Original Android Development] siberian85:
Anyone know why usb otg is not working on cm 13 it used to work
[Moto Maxx Original Android Development] ChazzMatt:
@ Skrilax_CZ, just wanted to make sure you saw this... Is the function in this xposed module something that could be coded into CM13?

---------

EDIT: never mind. [MENTION=5747496]baybutcher27[/MENTION] says it doesn't really fix anything.

http://xdaforums.com/showpost.php?p=67616177&postcount=2476
[Moto Maxx Original Android Development] Lou 270:
Is there anyway to boost my reception it seems like I get less bars lately and my LTE has dropped also
[Moto Maxx Original Android Development] junior_ilha:
I'm not sure if it doesn't really fix anything. My Cell standyby shows 8000mah of consumption. I know that it is impossible and it doesn't really change SOT or total time, but it scrambles ouro status and it difficults to keep track of our consumption.. This bug sucks..
[Moto Maxx Original Android Development] magi1991:
GPS problem

hello

sorry for my english

im on stock rom havent any problem with GPS

speedometer sygic and maps work nice

but on CM13 speedometer cant find satelitte and maps cant find my positions

how can i fix this?
[Moto Maxx Original Android Development] ChazzMatt:
1) what phone are you on?

2) try [MENTION=5747496]baybutcher27[/MENTION] clear modem zip file

3) try TopNTP app in Google Play store.
[Moto Maxx Original Android Development] mrkhigh:
#2 will most likely fix it. There is an odd bug going between moto stock and cyanogenmod.

Before that file was created the fix was simply reload original stock based ROM get a GPS sync then immediately flash cm. (I had to do it, Iran compfreaks ROM for all of 3 minutes to get it done... )
[Moto Maxx Original Android Development] ChazzMatt:
Also if #1 answer is XT1254, there are a couple of "good modem" TWRP files people have posted.
[Moto Maxx Original Android Development] Shooting Star Max:
Anyone having problems with auto-rotate in latest nightly? I tried clean-flashing to no avail.*Now I am downloading an earlier build.

Update: I am having the problem with the 201600707 nightly too. Now I am trying the latest snapshot.