yashsingh1/xdaforums huggingface dataset:
[Moto Maxx Android Development] tecsironman:
You know I've been sitting here reading about lock screens and how people don't want to use a lock pin or pattern. Here is a solution. Use pattern and just connect the the bottom 3 dots kinda like your swiping to unlock. Problem solved.
[Moto Maxx Android Development] kitcostantino:
disable active display and use this...fairly identical clone of Moto display. https://play.google.com/store/apps/details?id=com.greatbytes.activenotifications
[Moto Maxx Android Development] Chocoman:
4 dots is min)

---------- Post added at 07:03 PM ---------- Previous post was at 06:59 PM ----------

Is that solution battery friendly?
[Moto Maxx Android Development] kitcostantino:
in my experience, it is not. anything that creates more SOT drains battery. my battery is no worse with Dynamic Notifications than with CM based Active Display on, even using the "low power" option. I like the aesthetics of the version of Dynamic Notifications i use better. i use an older version that can be made to look identical to the 2013 Droids Moto display with the additional perk of user definable color. I cannot figure out if it actually uses the low power cores as the droid maxx did, but i imagine not. for me its a good solution.
[Moto Maxx Android Development] kitcostantino:
crap. dp
[Moto Maxx Android Development] gangrenius:
www.talkandroid.com/303291-system-i...+AndroidNewsGoogleAndroidForums+(TalkAndroid)
[Moto Maxx Android Development] immadeofpixels27:
Why did you post this here? This thread is for feedback on ResRemix for Quark devices...
[Moto Maxx Android Development] gangrenius:
Nah you don't say! Cause I thought I might be of help if bhb27 wanted to dig thru the system images of them and implement anything. Just trying to be helpful Mussolini!
[Moto Maxx Android Development] lkthomas:
Is it possible to improve open camera apps opening speed? It seems lagging a bit when it launch.
[Moto Maxx Android Development] monsterlucifer:
Please do not take my comments as adding fuel to the fire. I am just neutrally sharing my experience and will try to differentiate between Moto Display & Ambient Display from a user's perspective. It may already be discussed but since I haven't gone in the details so pardon me and ignore my post.

Moto Display keeps the screen black when viewing and swiping away notification. The screen does not light up (color display). It requires the circle to be touched which appears at about the middle of the screen (some precise location to be touched) to access or swipe away notifications.

Ambient Display lights up the screen (colour display) as soon as notification is swiped away. Ambient display does not require certain area to be touched. As soon as you touch the screen, it lights up the colour display. Swipe up (screen lock) does not require screen to be touched precisely at any location (like circle in Moto Display).

I wish that Ambient Display would have worked while using "None" as the lock screen...while using None as lock screen, ambient display and the notifications just does not work. I do not know what used to happen in Stock rom because I always used Swipe Up as my lock screen.

Aesthetically and from usage point of view, I find Moto Display to be more pleasing.

Having said that I am still grateful for the developers to bake in the features that closely resembles Moto Display into custom roms...because without it, we would simply be using power button to activate the screen and accessing notifications...
[Moto Maxx Android Development] quantum tao:
ambient display notifications can be dismissed by swiping sideways, they should opened by sliding up or down, that would fix the accidents. (i think someone might have mentioned this before)
[Moto Maxx Android Development] monsterlucifer:
I know it can be dismissed but it wakes the screen (in colour)...Moto Display doesn't do that...it keeps the screen black and sleeps as soon as notification is dismissed.
[Moto Maxx Android Development] quantum tao:
everyone knows it can be dismissed, my point was about opening it. should be a swipe gesture not a tap. :cyclops:
[Moto Maxx Android Development] iiWoodstocK:
But opening a notification is currently a double tap, not one tap. If it was a swipe, it would be a lot easier to accidentally open the notification.
[Moto Maxx Android Development] quantum tao:
has it already been tried with cm? moto display uses a press and swipe i used it for a year and never had it open accidentally.
[Moto Maxx Android Development] iiWoodstocK:
Moto Display functions differently though. Straight up implementing open notifications on a swipe up on CM's Ambient Display would cause way to many accidental opens. Moto Display acts as a buffer between the lockscreen and the Moto Display interface, whereas Ambient Display is essentially the lockscreen. Which is why opening notifications on Ambient Display is a double tap, to lessen the occurrence of accidentally opening up a notification.

Swipe up to open a notification on CM's Ambient Display would require reworking Ambient Display so that it's not an extension of the lockscreen, but a whole "layer" in itself.
[Moto Maxx Android Development] monsterlucifer:
Anyway, my point was not about how Ambient Display dismisses with swipe or double-tap. It's about Ambient Display waking up the screen...that is why Moto Display is more aesthetically pleasing...as it does not wake the screen once notification is dismissed. This cannot be achieved using Ambient Display.
[Moto Maxx Android Development] newbe1droidx:
Aaaaashhhhhhhh won't be long now ehhh! :laugh:
[Moto Maxx Android Development] Chocoman:
I'm agree with you about screen wake(in colour).

Would be good if someone could turn off the digitiser, maybe better to use power button?
[Moto Maxx Android Development] gumbi2647:
I only put mine in my pocket when I carry my .40 cal and it wasn't until recently that it was butt dialing. I have been on RR for a long time and only recently had this issue. Now that I think of it this latest build is not doing it or it isn't as noticeable. My settings are pretty much the same on all builds so that's why it seamed to be a problem within the build. I think its fixed now but to say that it was an issue with the user was just plain ignorant! Especially when it was all of a sudden happening with no changes to the ui input. Just my two cents because it sounds like some people always think that we don't know what we are doing when we do!
[Moto Maxx Android Development] jb14813:
The only thing I've found that fixes issues with audio glitch is to disable mp-decision. If I don't then my audio always glitches every few seconds.
[Moto Maxx Android Development] pedrohxn:
I faced the same issue some time ago and found out the same as you: MPDecision.

Could manage to solve this by making the CPU governor a little bit more aggressive OR changing to a customizable hotplug driver.

Nowadays, I'm using Bricked hotplug and getting more battery life, no more audio glitches and more fluid experience.

In my humble opinion, MPD is too aggressive in both ways: on plugging in and plugging off CPUs.
[Moto Maxx Android Development] fmz0507:
So I've been able to use isu to get safety net to work until this evening, when I realized I can't pass the check anymore

(last success was 6 hours ago when I added a credit card to my android pay).

Does that mean google has patched it? I wiped everything and did a clean install as i did 6 hours ago but can't pass it with isu anymore..
[Moto Maxx Android Development] immadeofpixels27:
They're all still in the same spots on MM.
[Moto Maxx Android Development] kenennaoyeka:
o it was under Gestures....my bad. I remember [MENTION=5747496]baybutcher27[/MENTION] said for it to work u are to disable and re-enable it. Its working now.

Thanks man
[Moto Maxx Android Development] GreaterLesser:
Latest build and kernel - No issues with any of the features except QPU and the governors on the latest build seems a bit touchy with certain voltage settings but that's to be expected. Only then still not working properly is Screencast (known issue) and Quick PIN Unlock. As I mentioned before if I accidentally type the PIN wrong and it doesn't error out, I clear the entire field and try to type again it doesn't recognize even the correct PIN number and locks me out for 17-32 seconds (it's random). Just wanted to see if anyone else could replicate this. On the upside everything else works and Cell Standby is done to 4% from previous 36-44%.
[Moto Maxx Android Development] colthars:
Using latest rom and kernel, all seems fine. Can't cast screen mirror to chromecast. Any suggestions how to make it work?
[Moto Maxx Android Development] Nitefire77:
Use the Chromecast app
[Moto Maxx Android Development] ceelos218:
Great battery life so far :)
[Moto Maxx Android Development] hpbrasil:
music animation on the lock screen is giving locking.
[Moto Maxx Android Development] colthars:
I'm using it. Made a factory reset on chromecast, re-installed app. Nothing seems to work. It just don't connect...
[Moto Maxx Android Development] Latiken:
I just now noticed that they're missing. Where are the security lock options?
[Moto Maxx Android Development] immadeofpixels27:
Settings>Lock screen>Display music visualizer

I have the option on, and it's not working for me either.
[Moto Maxx Android Development] Latiken:
Never mind just found it. Back in RR LP, the options was in Security. I even searched for the screen lock options using the search and didn't find it.

Music visualizer + pattern lock is working for me though.
[Moto Maxx Android Development] Nitefire77:
That's weird my Chromecast has been working great
[Moto Maxx Android Development] colthars:
Casting is okay, just screen mirroring not works. It work for you?
[Moto Maxx Android Development] mirdones:
My phone is overheating a lot and, after sometime, I am getting the "Can't connect to the camera" error when I try to open any camera.
[Moto Maxx Android Development] Nitefire77:
I just opened my Chromecast official app and screen is mirroring no problems
[Moto Maxx Android Development] mirdones:
I forgot to mention that the heating happens when I am charging.

The "Can't connect to the camera" also happens on CM13.

At first, this error does not happens, but then not even restarting the phone solves this.
[Moto Maxx Android Development] immadeofpixels27:
Heating while charging is normal, especially if you're using an adapter that supports Qualcomm's quick charging technology (the one included with the phone does).

As for the camera, have you tried reinstalling the latest RR version without xposed or any other apps that don't come from the play store?
[Moto Maxx Android Development] immadeofpixels27:
Small bug report of my own: I went into the "battery optimization" sub-menu of battery settings, and when I went back certain parts of the settings menu were blue 0.o
[Moto Maxx Android Development] mirdones:
It actually heated much more than the usual. My phone is a lttle more than 13 months old.

As for the camera, I wasn't using xposed or any app that is not from the play store.

As I had the same bug on CM13, but it took longer to nappens on it, maybe its a common bug on both?
[Moto Maxx Android Development] gumbi2647:
Small bug, I have been on the latest build with the test 13 kernel and my usual performance enhancements. Today I had no data and I tried rebooting several different ways and turned everything off and back on. Eventually turning the WiFi off fixed it. Just wanted to let everyone know if you have any issues. Just turn WiFi off and when Data comes back up then you can turn WiFi back on with no problems.
[Moto Maxx Android Development] jb14813:
I will have to give that a try. The only other problem I've had is that if I loose service for more than a minute then I have to restart the phone to get any data back. I'm running RR clean flash with the cleanmodem.zip and still same issue.
[Moto Maxx Android Development] gumbi2647:
I had that issue too but now I randomly flash the radio file. Also I had to go back to the .44 radio because of issues and battery drain.
[Moto Maxx Android Development] kingersj1:
I have been unable to use either Android Pay or Pokemon Go all day. I too wonder if the exploit has been patched.

Hhhmmmm
[Moto Maxx Android Development] fgl27:
no more poke-FUN to CyanogenMod users :crying:

Is not related to kernel or SU, the lock that google is using now is something else related to CyanogenMod or something in CyanogenMod ROM's... I don't know what exactly... If I find something I post here...
[Moto Maxx Android Development] khangozzy:
[MENTION=5747496]bhb27[/MENTION]

I have problem with mobile data, it is very slow when browsing web or tapatalk, even in some apps it does not work such as Whatsapp, Messenger. I did checked & changed apn, flashed your modemstats clear zip, reflashed su4tl-44 modem but no luck.

Everything is OK when on wifi, and mobile data worked well when put this SIM into another phone.

Pls find log attached

http://cloud.tapatalk.com/s/58003075afab3/logs_Oct_14_2016_08_09.zip
[Moto Maxx Android Development] fgl27:
Do you understand that I usually can't solve a problem that happens to one users?

Is very simple all users have problem I can fix one I don't if I start make changes others users will have problems.

IS VIETTEL a CDMA or GSM network... as you have a XT1254 the device is setting it self as CDMA and that may be the problem.

As this is a isolated incident may it just be a device incompatibility with the network or some special config need just for you...

To force yours device to a real GSM do this in bootloader:

fastboot oem config fsg-id singlela

To fully test the change is need to do a clean install after the command. Do a backup try if good or bad report.
[Moto Maxx Android Development] khangozzy:
Well, my carrier is GSM an now they only provide 3G only, and the problem solved by use only 1 APN and deleted all others, all of them are default generated.

I don't know why it messed the mobile data up as I use your ROM with all these APNs for year since LP build and this issue just start a few day ago.

Anyway, thanks for your response.
[Moto Maxx Android Development] Hawtpants:
Anyone else not able to get xposed to work since latest update? Using with BHB's kernel too.
[Moto Maxx Android Development] fgl27:
Like I wrote your device is be setup as Verizon CDMA device it may work like that but how I don't know I can't test the exactly situation you are on, all I know is if I set my as XT1254 like yours is I have a lot of data problems...

If you are in a GSM networks I recommend two options:

set it up as XT1225 with is a full GSM device

fastboot oem config fsg-id singlela

Use CM workaround but that is more recommended to a VZW user with you are not

fastboot oem config fsg-id verizon_gsm

You can also try a XT1225 radio.img in all test if you do you need to do it fallow by a clean install...
[Moto Maxx Android Development] gumbi2647:
Latest build and latest kernel! Parse error? Can anyone help?
[Moto Maxx Android Development] immadeofpixels27:
Nobody can help with so few details :silly:

Are you talking about a parse error when trying to install apps? If so, is it just one app or all apps?
[Moto Maxx Android Development] gumbi2647:
Yes and all apps! Sorry feeding baby
[Moto Maxx Android Development] immadeofpixels27:
Are you installing from Play Store or .apk files? If Play Store, did you try clearing its data and rebooting?
[Moto Maxx Android Development] gumbi2647:
Apk actually the update for XDA labs

---------- Post added at 01:13 AM ---------- Previous post was at 01:12 AM ----------

The play store installs with no problems. All of my apk files have parse errors. I wiped cache and still not working
[Moto Maxx Android Development] immadeofpixels27:
Try looking at the apk in a file manager and see if it shows the icon for the app on the file. If not, it's definitely a corrupted package, in which case retry the download. If it seems fine in a file manager, maybe try updating your GApps package and/or clearing the data of Package Installer
[Moto Maxx Android Development] monsterlucifer:
Just a heads up that built in Explorer under settings > storage won't install apps... You need to have a file manager like Solid Explorer...
[Moto Maxx Android Development] kitcostantino:
totally been there, man. ;)
[Moto Maxx Android Development] gumbi2647:
I just did a clean install and all is good! Thanks for the info because I changed back to open gapps too!
[Moto Maxx Android Development] :
I'm having a Apps with usage access issue anytime I download an app like an app lock app it's never in the usage access page area where you slide the slider to the on or off position how can I use these apps, is there a work around or I just can't use them. Thanks
[Moto Maxx Android Development] mrkhigh:
I recently had to roam to another network.

Had a terrible time because it was attempting to pick up the wrong towers.

I had to physically choose the network operator I wanted to use (bell) then my data settled down.

Is it possible this is your issue? This is a little bit the wrong forum for this.
[Moto Maxx Android Development] ankurcshah:
I love this ROM but only problem I see is it says I have apps installed for 7 GB whereas I'm sure it shouldn't be more than 3-4
[Moto Maxx Android Development] Septfox:
Uh, guys...I can still log into Go fine, as long as I make sure SU is toggled off first. I have the latest version, not doing anything particularly special to pass the check. I haven't been on any 30min+ outings in the last couple days, so I don't know if it'll pass subsequent checks, but I don't see why it wouldn't...

Make sure to completely exit Go if you fail the check (due to having SU toggled on or whatever); either using the task manager or "Back button to kill" at the bottom of Development Options.

An interesting thing: I updated it, and forgot to turn off root before running it. With root enabled it now gives a proper warning message (device, software etc not compatible) instead of the ambiguous "Unable to authenticate" crap. Well done, Niantic, only took you how many updates to get that working properly...

It should be noted that the only things I've done with root are messing around in Kernel Aduitor, BetterBatteryStats and file managers; no ad-blocking or any such.

I haven't rebooted in a week, though, so maybe this peace I have with it is fragile and it'll break as soon as I do. *shrugs*

Edit: latest version of RR, but not of the kernel: I'm still using the build from Oct 4th (2.0.2-1). Perhaps a change made to the latest is causing it?
[Moto Maxx Android Development] fgl27:
Yes you are right, v2.0.2-1 of the kernel is working...

This thing is just too much confusing, I remove unsafe things from the kernel because I was shore they may break some security, but in the true they just hide some insecure thing I'm just a little confuse with this all.

I revise the kernel and ROM implementation to see if next version are 100% regards safety net pass.

I test with bhb27-kernel v2.0.2-1 and iSu v1.2 so is need to flash the "iSu_Reboot_Service_Support_V_1_2_and_up.zip" before or after the kernel, and if iSu 1.2 apk doesn't install just delete the isu folder under system/priv-app/isu reboot then install the app

iSu download folder

If any one has anything to add let me know...

:good:
[Moto Maxx Android Development] fmz0507:
I don't know for sure but I did do a reboot after my last success and it seems like that's probably why you are still able to pass the safetynet check (it looks like you haven't rebooted yet since your last success). To me it seems like maybe the new safety net checks something when you first boot up?
[Moto Maxx Android Development] johnbravado:
I am having a battery drain and am curious if any one knows what it is. I looked it up on had something to do with kernel and 3g but not sure is that applies to the turbo. The top 2 I think may be linked but they are killing my battery

I am running latest RR and bhb kernel without modifications from kernel auidtor
[Moto Maxx Android Development] khangozzy:
My top 2 wakelocks, they are related to kernel, anyone have a suggestion to reduce it?
[Moto Maxx Android Development] fgl27:
safety net only runs when you open a app that uses it, doesn't matter when you boot how you reboot, if the system is "safe" for it will work and give a OK if no NOK... but it changes every now and them it just make things complicates safe thing became unsafe and vice versa...
[Moto Maxx Android Development] fmz0507:
You're right, it does make it seems quite confusing. Cuz I did go back and flash the same kernel and isu as Septfox and you mentioned but no luck. It's hard for me to wrap my head around how come Septfox can still pass the safety net test but I can not anymore.. Well, regardless thanks for all you've done :)
[Moto Maxx Android Development] jmscaramal:
Hello guys...

First of all, thank you bhb27 for all the work you've done so far.

I've been used the RR for a week (clean install), and everything seems to work perfectly, except for 2 issues (until now) :

1 - Screen mirroring (cast) isn't working. On my TV I can see the msg "connected", however it only shows a green screen. Moreover, it's not possible to use the Maxx while "casting". Did someone have a similar issue?

2 - When playing some games, I feel I kind of lag. Even more simple and "soft" games (regarding graphics). My actual cpu governor is interactive, a tried to disable MPD (as suggested in previous answers), but I could not see any improvement. Any suggestions? In the bhb27 kernel, there's no "ondemand" option for cpu Governor?

3 (I'm not sure if it is a bug) - it seems like the 4G performance decreased. However, I'm not sure if it's due to the RR or maybe some problem with my cell phone company. I need to investigate a little more. (I've already flashed the radio.zip, it solved a problem with GPS.)

Anyway, if there is someone with similar issues, please let me know.

Once again, thanks bhb27 for all the work. This rom is awesome and I always wanted to use it on my Moto Maxx! :good::victory:
[Moto Maxx Android Development] rohheat:
yes screen cast doesnot work... green screen
[Moto Maxx Android Development] fgl27:
kernel adiutor > misc > selinux(on) set to enforcing

As other had reported before mirror cast was working, I have no device to test that... if you test others ROM I can use that may be a problem, if you test and it doesn't work may be a config missing that you need to learn...

ondemand doesn't work there is other 20+ govs included update version of ondemand in the kernel I make...

Those signal problem in most cases is from the carrier side, the ROM doesn't change a thing related to signal must be as good as any other custom or stock ROM.
[Moto Maxx Android Development] Septfox:
I can also pass Safetynet with Permissive set, at least for the initial login. No idea if the 30min checks are any more thorough.

Well again, make sure you're running the latest RR, and specifically kernel 2.0.2-1. If you are and still can't get it to run, try wiping /system and reflashing the above and gapps...it's possible you have something lingering from past flashes. If you've run SuHide before, make sure you're no longer running the modified boot image it generates, either.

The only time I've had trouble so far is when iSU decidedly to randomly botch root access and die, so not only was I not passing Safetynet for some reason, I didn't have root access. I had to reflash the kernel to fix it since I rebooted without root, but it looks like bhb has added support for this problem in 1.2 with his reboot service.

Speaking of 1.2...

[MENTION=5747496]bhb27[/MENTION], I like the toasts you added when SU is toggled, very amusing :silly:

"Stock" Interactive settings are a little shuttery in listviews, but I wouldn't call them laggy...it should perform adequately from a fresh install.

To make sure it's the CPU causing your problems, use the Performance governor, this will instantly ramp the CPU up to full power when load is applied. Make sure your max CPU speed to set to stock limits, 2649mhz I believe, or you'll heat things up pretty quick and end up being heat-throttled before you can do any useful testing.