yashsingh1/xdaforums huggingface dataset:
[Moto Maxx Android Development] johnbravado:
[MENTION=3250376]ChazzMatt[/MENTION] i had that happen to me a lot also. i asked the same question so long ago. do you use xposed? i believe my issue was with an exposed file. i tried reinstalling and updating and everything trying to get it gone. i ended up installing just RR ROM. then installing apps little by little saving backups everyy time it loaded well. it turned out to be either an xposed module or the fact i forgot to clear data on kernel auditor and it was giving issues. i think process error was xposed mod setting though. i believe the kernel auditor was a different error. it happened a long time ago.
[Moto Maxx Android Development] ChazzMatt:
No, don't used exposed. I may in the future but I just switched from CM12.1 to RR last week. I can't switch my wife over until I figure out why this is happening.

It's not every time I boot up, but like every 5th or 6th time. I set my phone to auto reboot at least once a day early in the morning, and then daily or every other day I make a TWRP backup which is another reboot.

Hmmm.... I'll try clearing the kernel app just in case.
[Moto Maxx Android Development] johnbravado:
[MENTION=5747496]bhb27[/MENTION] this latest ROM and Kernel install i love it man. The last few ROMs have not agreed with my setup and has been killing my battery. This one is awesome though.
[Moto Maxx Android Development] fgl27:
I reboot a lot when I'm testing... never see this problem...

You can try two things old version of SuperSu or just use this ROM Stock SU.

I would recommend check what app are in privacy guard "boot up" section and may be halting boot, but that only works with Stock SU.
[Moto Maxx Android Development] JFCostta:
Does it realy deactivate Su or just hides it from root scanners? If is the second option, shouldn't be better rename the button to "Hide" instead of "Deactivate"?

BTW, nice app! Flashing the new ROM right now to test it out, the later was draining fast my battery in stand by mode.
[Moto Maxx Android Development] JFCostta:
Folks,

Has anyone managed to install and sucessfully run Moto Voice? Is it possible in this ROM?
[Moto Maxx Android Development] johnbravado:
after installing this latest ROM i found something broke. My ability to connect to the ocmputer and view files. i used to be able to plug into my computer and move files around. now though all i can see are folders and .zip files. but individual docs, photos, movies.... actual files i cannot see. i have tried to reboot phone and the computer and clear cash and runnning SD Maid to try and rsolve bug issues.
[Moto Maxx Android Development] Hawtpants:
[MENTION=5747496]bhb27[/MENTION] any possibility to add viper4android to the ROM? Would be such a welcome implementation given that the XT1225 has such ****ty speakers
[Moto Maxx Android Development] gangrenius:
That's happened like that occasionally for months on boot up with this rom I don't know why. Didn't happen this go round. But I'm sure it will.
[Moto Maxx Android Development] ChazzMatt:
Mine works fine for viewing individual files. I'm rurning latest ROM update. I see all files, not just folders -- like JPG, MOV, PDF.
[Moto Maxx Android Development] fgl27:
I understand you, the switch and about don't mach descriptions...

I need to deactivate SU to current workaround to work, you can check that by trying a SU app(like kernel adiutor) after turning it off will not work.

No those type of third party app is a mess to make it work and is not a thing to all I my self don't really need it other too....

Was already share on the thread how to make such a app to work with he ROM take a search if you can't, as I remember is a simple flash zip and some config to the app...
[Moto Maxx Android Development] johnbravado:
yeah i dont think it is the ROM honestly. i was looking at files then something happened and i couldnt. i think there is some other bug apart form the ROM. Is there a way to reinstall the motodrivers that ar eon the phone into my computer?
[Moto Maxx Android Development] ChazzMatt:
https://motorola-global-portal.custhelp.com/app/answers/detail/a_id/88481
[Moto Maxx Android Development] eddiemc12:
check if your system took updates recently,same thing happened to me when windows 10 updated mtp and adb functions were no longer available only PTP and that only shows your DCIM folder had to do a system restore to before the updates were installed to get everything working again.
[Moto Maxx Android Development] NepoRood:
You are, as always, correct sir! [MENTION=7048584]Hawtpants[/MENTION], look at this Works on the Turbo (XT1254) for sure :good:
[Moto Maxx Android Development] Septfox:
Yes, thank you for fixing the SU problem, and iSU works perfectly as far as I've seen :)

Why was Safetynet failing before? Was SuperSU not completely removing root?

---

Also...has anyone had problems with the phone waking while in a pocket with the Wave gesture (to pulse Ambient Display) enabled? Three times earlier, I pulled my phone out of my back pocket to find it turned on and I'd apparently been butt-typing garbled messages in Messenger. Fortunately it never managed to send anything...

Turning off the Wave gesture "fixed" it, but...then I can't wave-to-wake : \
[Moto Maxx Android Development] Latiken:
There's an option in Display settings under Screen called "Prevent accidental wake-up" turn that on.
[Moto Maxx Android Development] Septfox:
First thing I tried. That appears to use the IR/proxy sensor to prevent the screen from waking by movement triggers (Pick-up/Unstow), it doesn't seem to do anything for pulses generated by the sensor.
[Moto Maxx Android Development] fgl27:
No it fails before because missing kernel safety implementation, this is all very new (safety net related) and I need to adapt...

In the pocket maybe you need to disable "Pick-up" use only wave...

Prevent accidental wake-up is related to the power button, but it is not working on this devices will remove, was add to fix the problem to some users that after some time had the proximity sensor stop working and breaking the wave gesture.

@ all

About: The problem to some users that after some time had the proximity sensor stop working and breaking the wave gesture.

Was a general CMAction problem affecting others device too, it received a update to prevent that from happening... Will included on the next V and you guys tell me the result...
[Moto Maxx Android Development] monsterlucifer:
I'm on the latest version with stock kernel. While in a voice call over SIM, the signals just vanishes and comes back...ongoing call drops...this is recurrent even after flashing twice with wiping all data and partitions...any heads up?

Flashing bhb kernel could possibly resolve this situation? Or should I look over to alternate modem? I'm on droid turbo XT1254.

It was working fine with older release of RR, CM13 as well as Brazilian and Indian stock variants...and I've never flashed any modem ever...whatever came, it came with the above ROMs only...

My current baseband reads: MDM9625_104651.11.05.16.02R

Kernel: 3.10.103-Stock-CM-Kernel-Mod_by_BHB27

bhb27@Android # 1

Resurrection version: ResurrectionRemix-M-v5.7.4-20161006-quark

Build number: Resurrection Remix Marshmallow 6.0.1_r66 - MOB31E
[Moto Maxx Android Development] Septfox:
Ah, I see. It looks like you got it fixed properly, though, not a single complaint from the Helper app or PokeGo so far :good:

No effect. Pick-up detection does actually seem to use the proximity sensor, and will not pulse if the phone is tilted up while the sensor is blocked. It seems to work quite well.

I was doing some more testing, and I found what may be considered a "bug". Or maybe it's intentional and the problem was caused by me misunderstanding the intent.

It appears that when the proximity state changes, it pulses Ambient Display. The problem, I think, is that the pulse should only be sent when going from high (close proximity, detecting an object) to low (detecting nothing).

Example:

With the Wave gesture enabled, try placing the screen of the phone against your leg. The expected behavior is to stay off, and only pulse Ambient Display when moved away from your leg; this is how it's implemented in CM13 for the Droid 4/Maserati and it works almost flawlessly, providing that phone with both (short-range) Wave and Pocket/Unstow detection using just the proximity sensor. I think the stock ROM's sensor services disregard the input completely if it's not momentary (like a wave).

But in RR on the Quark (and perhaps CM13, and on other phones? I don't know), it will pulse as soon as the sensor's state changes, when it "sees" your leg or any other object. So if you try to slip it into your pocket, it unintentionally pulses. If you unblock the sensor after the display timeout, it will pulse again; there appears to be little or no debounce.

If your pocket is dry, then nothing bad happens, Ambient Display times out and the phone sleeps. But if it's damp with sweat, interesting things can happen; in my case I was slipping it into my back pocket expecting it to stay off, but instead it pulsed on and was kept on by the sweaty fabric (working outside in the cooler weather today). Eventually it managed to unlock itself and do all sorts of things. Very nice and sensitive screen on the Quark :silly:

I think fixing it - if the behavior is unintentional - would be as easy(?) as modifying/adding an option to Wave detection to only send a pulse when the sensor state goes from high to low. This shouldn't reduce its sensitivity much if at all, and will also prevent other actions from unintentionally pulsing Ambient Display (such as flipping the phone face-down), saving an extra small amount of power.

Alternatively, it could take the orientation of the phone into account and block proximity sensor input completely if it's beyond a certain angle. I doubt anyone would miss the ability to wave the display on while hanging upside-down...

If this is the wrong place to report this, I apologize; I have no idea if the behavior is unique to your ROM or not. I'll install CM13 tomorrow and check to see if it's a common issue, but for now, I really need to get some sleep.
[Moto Maxx Android Development] gumbi2647:
Yes my xt1254 has done it a couple of times since the last update. I was wondering how I was typing group messages and a bunch of garble.
[Moto Maxx Android Development] ChazzMatt:
HOW are you typing any messages if you display is locked? If your butt is accessing your messaging app, then your display is NOT locked and has nothing to do with Ambient Display.

Ambient Display only works if you display is locked. And as far as I know, you can't access any message apps until your display in UNLOCKED -- unless you have some completely different setup... No one has ever been able to explain that because I don't think it can happen.

Even if Ambient Display fires up and shows your messages in your pocket, it's not like you can reply to them with Ambient Display turned on (locked display).

You have something set up wrong. Seriously.

You either have a simple swipe to open your phone and not a pattern or number code, or you have on-body detection (which defeats a lock screen and prevents Ambient Display from working) or you have some ridiculously long delay from when your screen goes dark to when it actually locks.

With a locked display, if I touch on a message showing in Ambient Display mode, ALL THAT WILL HAPPEN IS MY SECURE LOCKSCREEN PATTERN SHOWS. Until I actually unlock my screen I cannot type or respond to any messages.

NO MATTER HOW MANY TIMES I CLICK ON AN AMBIENT DISPLAY NOTIFICATION, UNTIL I ACTUALLY SWIPE THE COMPLEX SECURITY PATTERN, nada. Nothing.

Do you not have an immediate lock when the display turns off? Do you keep it UNLOCKED for like 2 minutes, 5 minutes even after the display goes dark? (Some people do that and it makes no sense. If the display is not locked, it is active, even though dark. Ambient Display does not work with an unlocked display.)

Do you have "smart lock" on-body detection? In which case the display is unlocked. Ambient Display does not work with an unlocked display. (Someone did that and still blamed Ambient Display! When they were the person at fault, because their display was unlocked and active.)

At least to me it seems somehow your display is NOT locked and you are blaming Ambient Display. At least that how it's always been for anyone else blaming Ambient Display. ;)

Tell me how your butt is accessing your messaging app with a locked display?
[Moto Maxx Android Development] quantum tao:
this is also when it would happen to me, outside chopping wood and sweating. it is a rare occurrence now since Skrilax_CZ squashed the bug. ChazzMatt is still adamant that whoever is having an issue with it must be doing it wrong. He might be right, but we dont want to tell him that, it might go to his head. :eek:
[Moto Maxx Android Development] ChazzMatt:
Yes, I am adamant because I have explained all the scenarios.

Try to access your messaging app with a locked display. You can't.

NO matter how many times you click on a locked screen notification, until you actually UNLOCK the screen, you cannot reply to it.

Therefore, if somehow your butt is replying, then the display is UNLOCKED. Find out WHY the display is unlocked and stop blaming Ambient Display (which only works when the display is LOCKED.)

Either

you have a simple swipe to unlock. YOU have unlocked the display in your pocket, whether you meant to or not. Change that to a pattern or number code.

or you have on-body detection or some other "smart lock" which is defeating the lock screen.

or you don't have an immediate lock when screen goes dark. (Why? If the screen is dark, it should be locked.)

This is what your setting should be:

And be careful of any Smart Lock exceptions! Do NOT use On-Body detection! I only used Smart Lock with my previous car which had a bluetooth stereo. My current car doesn't have that (yet), so not using Smart Lock at all right now.

Those are the only scenarios it can happen -- and any time the display is UNLOCKED, Ambient Display is NOT involved in any way whatsoever.
[Moto Maxx Android Development] Septfox:
People actually set things other than swipe-to-unlock? :>

Yes, I know, don't look at me like that.

I don't usually feel the need to set a lock pattern/pass/PIN because my phone is always either being used or safely in a pocket. So yes, I use the swipe-to-unlock/simple keyguard unless I know I'm traveling out of familiar territory.

Instant-locking was defaulted at 5 seconds, but doesn't appear to affect how the phone behaves when swipe-to-unlock is being used; the keyguard always comes up after the screen is turned off regardless if by timeout, tapping the statusbar or power button. Smart locking is off completely.

How was the keyguard being dismissed? I don't know. I was helping unload 150lb+ fire-safety equipment boxes, it's probable that the phone was jostling around enough for a fling to be registered to unlock. To be honest, I was too preoccupied with the whole "not being injured while unloading 150lb+ metal boxes" thing to notice what my phone was doing while it should have been sleeping :v

I'm not saying that Ambient Display is at fault. It's what's triggering Ambient Display that's at fault. It being pulsed on is what's allowing subsequent "taps" to bring the display fully on and good times to be had.

Unless it cripples the responsiveness to Waving that much when set up otherwise, I don't see why it should be pulsing when something is blocking the proxy sensor. Not setting up a "proper" screen lock is my fault; the sensor triggering the display on when it's not appropriate and (among other things) wasting power...isn't.

...is that the fix that [MENTION=5747496]bhb27[/MENTION] was referring to earlier?

If so, sorry for the wall of text, guys : \

---

By the way, do the bottom IR sensors actually do anything in CM13/RR? I'm guessing they're used in the stock ROM to roughly "image" the user's face to keep the screen on, but it looks like the main proxy sensor is used for that here to not quite the same effect.
[Moto Maxx Android Development] NepoRood:
I "swipe" too, lol (my phone is in a case, not my pocket)

And, I can double tap a message notification, in Ambient Display, and go straight to the message (no unlock required)...
[Moto Maxx Android Development] quantum tao:
no, that is from a while back, this problem used to be worse.

it could be what he is talking about the proximity sensor, since theoretically it should prevent this behavior regardless of screen lock situation because it would prevent the screen from waking at all.

i have turned off ambient display, this problem never happened on moto display, not even once. but since we have a little green light that flashes its all good.
[Moto Maxx Android Development] ChazzMatt:
If you had a pattern or number code you can't do that. The entry comes up for the unlock code and you can't get past it.

Your display sensor must be interpreting that "double tap" as a swipe? or because you don't have a secure method (pattern, number password) double tap is an allowed method in addition to swipe?

I don't know. I I have to have one or the other (pattern or code) for my corporate email account to work on my phone, so simple swipe is a greyed out option for me.

But I would have it anyway for security, in case I lost my phone or it was stolen.
[Moto Maxx Android Development] Septfox:
Indeed, I can recognize that it's wiser to have the security on regardless of location. Constantly unlocking just bugs me is all, and the little bit I've tried Smart Unlock has found it...fidgety.

I guess you get used to the unlocking when it's a mandatory requirement, though...

By the way, my phone happened to come with the Diztronic case you recommended, and its inclusion was at least partially responsible for that particular purchase. I've been loving it, fantastic-feeling and adequately protective case, thank you for showing it to me. A chunkier/grippier Speck Candyshell case was also included, but I'm definitely getting more mileage out of the Diztronic :good:
[Moto Maxx Android Development] Chocoman:
So, Moto Display ≠ Ambient Display. Moto Display is much better. What about vote?)
[Moto Maxx Android Development] ChazzMatt:
No need to vote. Quark Ambient Display is better and you're not going to get Moto Display on custom ROM anyway. So, "vote" is wasted time.

Spend that time learning how Ambient Display works. ;) Like only a locked display and don't set some easy "swipe" unlock so you can accidentally unlock it in your pants and blame Ambient Display when YOU unlocked the phone. Ambient Display didn't unlock the phone and butt dial. YOU did.
[Moto Maxx Android Development] quantum tao:
moto display is better
[Moto Maxx Android Development] fgl27:
Lets go again... intervene before you guys go beyond the point...

This is a development thread... check General thread and post thing related to taste there, after all already have many thread about it...

This discussion already happens too many times here, this will not improve the Software be developing here...

If any one wanna a featuring from a Stock ROM fell free to try to do it work on Custom yourself, if was simple it was already ported if is not is probably not possible do how much work need to be done to make it work.
[Moto Maxx Android Development] Chocoman:
Maybe would be better to add function that would be disable touchscreen for ambient display, I prefer to use power button, or touchscreen will work only in backlighted zones. Or it's to difficult?
[Moto Maxx Android Development] iiWoodstocK:
If you don't want Ambient Display to be responsive to touch at all times (in other words, waking the phone via power button only), just turn off the wake gestures.
[Moto Maxx Android Development] Chocoman:
Touches and wake gestures, there is some differences, isn't it?
[Moto Maxx Android Development] NepoRood:
No, lol, it says "Tap again to open", after 1st tap. Sorry, [MENTION=5747496]bhb27[/MENTION], I had to point that out...

PS, as [MENTION=7109882]iiWoodstocK[/MENTION] stated, it can be turned off if it's causing issues
[Moto Maxx Android Development] iiWoodstocK:
Yes. But if it never wakes, then it won't register touches.
[Moto Maxx Android Development] Septfox:
I've been having problems with notification sounds cutting out, and wifi...

When a notification comes in, the sound begins playing, but is cut off when the screen turns on. It's actually been happening for quite some time - I've been missing texts and emails when it's on my nightstand because the sound cuts out quickly - but it was only tonight when it was laying on my desk that I realized what was going on. I thought it was Ambient Display causing it, but turning that off and using a third-party app finds that the sound still cuts off when the screen lights up.

Wifi behavior is erratic and disconnects/reconnects while the phone is awake. It nearly always disconnects immediately after going to sleep and refuses to come back up until the screen is turned back on. I do have "Keep Wifi on while sleeping" set to "always".

It seems to behave itself better on my work network, but still occasionally disconnects.

Logcat attached, contains putting the phone to sleep and sending myself an email to trigger a notification, and letting Ambient Display pulse several times just because. Did I manage to break something?

edit: actually attached the logcat, durr
[Moto Maxx Android Development] gangrenius:
Delete
[Moto Maxx Android Development] Chocoman:
I like when it wakes.
[Moto Maxx Android Development] ChazzMatt:
Since I can't use easy swipe (security) and have no desire to, I have no idea that option is there. And I don't care. ;) That option is NOT there on pattern nor number code unlock. It must only be there on silly unsecure easy swipe.

Anyone who uses easy swipe deserves all the butt dialing problems they encounter if they put their phones in their pockets.

_________

I've given the solution many, many times. So, anyone who complains is just likes to complain. Not you, for this comment, I'm just commenting generally for snarky comments about Ambient Display that I've refuted and yet people still want to hold to them, when they are at fault not Ambient Display. ;)

As [MENTION=5747496]bhb27[/MENTION] said, if you don't want to use Ambient Display there's a stock based ROM you can use.

If you do want to use Ambient Display (Quark version), it's amazing. I use a pattern security lock.

I also never carry my phone in my pocket on a daily basis. It's too expensive! I keep keys, coins, pens in my pocket which could scratch the screen.
[Moto Maxx Android Development] Chocoman:
What about those, who are using smartlock with smartwatches or smart bracletes without screen?
[Moto Maxx Android Development] ChazzMatt:
Same thing as on-body detection.

Then you are purposely unlocking your display. IT's YOU. Ambient Display only works on a locked display. If your display is unlocked, Ambient Display has NOTHING to do with what your butt is doing, messaging anyone, calling anyone.

If you are going to keep your display UNLOCKED, don't stick it in your pocket! Put it in a belt holster or something if you must. I only use Smart Lock on something like my car stereo and then my phone is safely mounted in a windshield clasp.
[Moto Maxx Android Development] Chocoman:
I don't remember any problems like this one with moto display)

And i understand that i can't use moto display with custom firmware.

Simply i don't think that is really good solution(pattern lock or others), and it's ambient display fault, not mine.
[Moto Maxx Android Development] solidus636:
The apps with usage access feature needs to be fixed.

I have an app called 'accubattery' installed, and its asking for permission for usage, when I try to do that, the list of apps is not accurate and accubattery is not listed.

This is the only bug I've found

Apart from this issue, ROM is rock solid !! I've used countless devices, every single flagship, this is one of the best yet.