yashsingh1/xdaforums huggingface dataset:
[Moto Maxx Android Development] fgl27:
What are you flashing???

"SU49_Sensor_Files_Flash.zip" file for XT1254 user only.

"CM13_sensor_files_Flash.zip" Files already on this ROM

there is no problem regards proximity sensor for XT1225 user, you be from Brazil I believed you have a XT1225, you can use the files if you wanna but they are not intended to use and can bring some odd problem....

The led can be on and off, so it can "blink" at least my blinks.

If you are charging it may be always on, but if the device is not it will be on for some time very short time then off do some "blinks" until device goes to sleep, then it will do a "blink" from time to time when it comes back from sleeps.

There may be notifications app, battery apps or xposed modules that can affect and or conflict with this... Or maybe some leds are different that may be the way Moto doesn't uses this in any way, but if any led can be on and off it can simulate a blink...
[Moto Maxx Android Development] fgl27:
A specific toll can't affect a device and not the other.

I start receiving reports after the updates from SU44 to Soak 4 blobs update, at the same time the stock kernel was update and change from CM13 allow it to be compiled with google tools (or google update they tools) the google toolchaing is present on all CM base source that don't change it and most don't do on marshmallow, so the changes that cause this come with the use of new blobs or me starting using google tool with must not be or I and other XT1225 user would have been affected and that doesn't happens or happens on my test with others tool I have used but those test all in the pass...

When user report with 100% that this sensor zip have no good effect I start to look on some place else...
[Moto Maxx Android Development] NepoRood:
I see what you're saying, I couldn't get the kernel to build without error unless using Uber 4.8, as you originally suggested to me. I don't know enough about kernels to fix build errors, yet. So I stuck with that one, but I tried some SM and Hyper ROM chains, each had various results, and eventually I went back to Uber 4.9 for ROM.

I still have SU49 system extracted, if there's anything you need from it, just let me know, I'm happy to help out any way I can.
[Moto Maxx Android Development] drtweak:
Just tossed this on my Turbo coming from CM13. Was having too many issues on CM13. Some features working. some not. battery life i notice seemed to get worse with each update. Head a lot about this ROM. Very smooth as faster than CM13. Great job!
[Moto Maxx Android Development] iiWoodstocK:
So I tried the SU4TL-49 sensor files (I made my own flashable zip), and my IR sensors still stopped working (after about 1.5 days).

[MENTION=5747496]baybutcher27[/MENTION]
[Moto Maxx Android Development] JayCizzo:
When it stops working does a reboot fix it? I ask because I haven't had issues with the sensors but I turn off my phone pretty much every day because I can't take it into work. I'm on the newest build and I didn't flash the SU4TL-49 sensors.

Unrelated, I tried the Bliss ROM and had sensor issues along with other issues. Gotta love how differently all our phones behave on these ROM's. :eek:
[Moto Maxx Android Development] iiWoodstocK:
Yup, when it happens a reboot always fixes it. But since I started having the problem I haven't been able to go more than approximately 72 consecutive hours without it failing.
[Moto Maxx Android Development] gumbi2647:
I tried the 49 files and updated to the 49 radio and had issues like before. So I am back on 44 and the only issues are that the sensors are weak! You have to wave your hand real close and over it a few times to work. But it does work!
[Moto Maxx Android Development] iiWoodstocK:
That's is because of the regular proximity sensor (to the left of the front facing camera). If you turn off wave to wake, but leave on pickup, place your finger over the proximity sensor then remove. It'll activate Ambient Display. That proximity sensor is sensitive to about 1 inch away.
[Moto Maxx Android Development] fgl27:
The 44 files was used on all CM from April until the end of July, we never had problems on those... noting like the need to be really close maybe is just a incompatibility with current ROM...

@ all

I need logs from devices with problem logs after the problem are manifested and before any reboot...

This is a very particular problem that doesn't manifest on all device included my, so I need to check what is happen on the logs...

kernel adiutor app > setting > Logcat and Driver Message, files in internal memory...

:good:
[Moto Maxx Android Development] iiWoodstocK:
I will get back to you in about 1-2 days, as it should stop working within that timeframe. Oh, FWIW, the issue started for me with either the 06/15 or 06/28 build.
[Moto Maxx Android Development] fgl27:
Are you shore about jun? maybe jul?

rom changes

kernel changes

-------------------------

After I released a New ROM tomorrow I will released a test version of my the kernel with changes to the sensors, Moto did some changes to the sensor last year included on the XT1225 kernel but never push those changes to XT1254 kernel and this changes are more then a year old they came before any XT1254 kernel released by Moto, maybe they did not because they find a XT1254 problem or some other thing doesn't cost to test...

If they had released a 6.0.x to XT1254 it would be easier to understand and make things more stable...
[Moto Maxx Android Development] iiWoodstocK:
OH! Your right, 06/15 and/or 06/28 were the last builds that worked because I was using my soak 4 build the second half of June. I *think* the last RR build I used prior to having the issue was 06/15, as I don't think I used 06/28 long enough to notice if the issue began with that build. Definitely the beginning of July builds because that's when I came back to RR, and I remember going through quite a few different clean flashes to see if it was a problem on my end.
[Moto Maxx Android Development] Latiken:
My sensors are currently failing on the latest ROM, here is the driver, I can't upload my logcat because it exceeds the limit. [MENTION=5747496]bhb27[/MENTION]

EDIT: I uploaded the logcat to some random website, heres the link:

http://www.megafileupload.com/oejX/logcat.txt
[Moto Maxx Android Development] fgl27:
ROM update! ResurrectionRemix-M-v5.7.3-20160831-quark.zip​

Download-ROM

Changelog

If dirty flash and the device don't boot make a clean install (Wipe dalvik cache, cache, system and data) then install the ROM + Gapps (demanding when clean install flash ROM+ Gapps at the same time).

...............

Notes:

This ROM doesn't have my kernel it have Stock-CM-Kernel but you can download and use it, I do this because some people may not need custom kernel or wanna to test without it.

Download BHB27-Kernel

Use only the latest version of my kernel today BHB27-Kernel-V201-3-M.zip base on Moto 6.0.1 source.

Bug report: make with in the most accurate description possible, do not spare words, screens and logs, a bug that i can't understand can't reproduce I can't fix.
[Moto Maxx Android Development] fgl27:
I made some changes to the next V of my kernel removing Moto's changes to sensor that are not present in XT1254 kernel...

Download

This may help/solve the sensor problem... This version is 100% stable on my device, full changelogs when I released officially...

For those that don't use my kernel to get back to stock one is need to restore a full backup or dirty flash yours current ROM...
[Moto Maxx Android Development] immadeofpixels27:
FYI, you forgot to close a parenthesis on the changelog and broke the link ;)
[Moto Maxx Android Development] quantum tao:
what was wrong with calendar? now i dont have one.

also, "unfortunately contacts has stopped"
[Moto Maxx Android Development] drizzzzzz:
Download Google's calendar app.

Also, yeah contacts is crashing.
[Moto Maxx Android Development] quantum tao:
I don't use any google spy services. Using an android phone is scary enough.
[Moto Maxx Android Development] gangrenius:
Do u guys not read changelogs?
[Moto Maxx Android Development] quantum tao:
Yes, hence why I said "what was wrong with calendar?".
[Moto Maxx Android Development] gangrenius:
Did anyone find a fix for contacts force closing?
[Moto Maxx Android Development] fgl27:
it seems you didn't, at least not to the fullness...

do you need the app ask...

There is a problem with connection with google on aosp calendar, but if wanna I can re-included...

My is 100%, but I clean install it...

maybe a "clear data" of the app can resolve but I advised clean install in any of this FC situations...
[Moto Maxx Android Development] hpbrasil:
Contacts force closing :/
[Moto Maxx Android Development] gangrenius:
A clean install is a hell of a task for me BHB. I have lots to reflash and back up. A pain in the arse!
[Moto Maxx Android Development] immadeofpixels27:
He's just talking about clearing the Contacts app's data. All you have to do is backup your contacts.
[Moto Maxx Android Development] immadeofpixels27:
Also, is this happening to anyone else?

(See attached screenshot)
[Moto Maxx Android Development] gangrenius:
No he said if that doesn't work to clean install.
[Moto Maxx Android Development] McDastardly:
Clean install didn't help either. Had to uninstall it, reboot, and install it from the play store.
[Moto Maxx Android Development] gangrenius:
That's what I was figuring thanks for doing it first haha

---------- Post added at 03:01 AM ---------- Previous post was at 03:00 AM ----------

Did you uninstall contacts storage also or just contacts?
[Moto Maxx Android Development] McDastardly:
Just contacts
[Moto Maxx Android Development] Marky__Mark:
If you could add those back, that would be awesome. My aosp calendar sync works just fine. And its a CM app so it gets themed and is a part of the CM theme engine. Removing the dynamic wallpapers is fine. Just battery wasters.
[Moto Maxx Android Development] rohheat:
can we expect 7.0 for our device?
[Moto Maxx Android Development] gangrenius:
Yeah!! you haven't downloaded it yet? ???
[Moto Maxx Android Development] NepoRood:
Yes, as soon as CM gets everything working. All CM based ROMs (RR, Bliss, etc) pretty much have to wait for them to get the code working. Then they have to hammer out the bugs, then we have to update device trees to work with Nougat, then hammer out more bugs...

We'll get 7 when we can, just gotta have a "good" source to work with :good:
[Moto Maxx Android Development] rohheat:
okay
[Moto Maxx Android Development] Asyt:
Question: trying to get this back as my full time device and RR has been an awesome build. One thing on the list of things to try is encryption again. Last time I tried it was a mess, but now with TWRP 3.0.2.0 and these stable MM RR builds, are there any known issues that would prevent me from running encrypted? I would do a clean install before encrypting, but anything else to know: such as you can't flash ROM updates as easily?
[Moto Maxx Android Development] fgl27:
Custom ROM have too many changes, clean install is demanding after a while...

with Titanium backup .zip the process is 10 to 15min, including making the TIBU .zip, a TWRP backup and config the ROM the way I like...

Shore I share the app lather on the thread as I only make on ROM a week will take some days until the next, you or any other can use it with the latest ROM V

I use that app for months and had no problem, the one from play in theory is the one on the ROM, google update the app I will included the update version on next V (the app looks really better) but the play version is the old the same as the ROM...

What is the version you have?

app info can show that...

And what gapps you used?

as some gapps remove CM Contacts storage or included a google version of Contacts storage and CM Contacts storage works great with google contacts integrates better with this ROM, and some gapps can do other things related that can affect this app...

I test this without gapps so I'm not affected by any problem related to a gapps pack know, but in the pass I test with gapps no problem...

----------

If any one had any more problem with this app report what gapps are using and only reports after clean install, If there is too many problem is one line to change and go back to AOSP...

:good:
[Moto Maxx Android Development] McDastardly:
I have 1.5.16 installed now. I flashed open_gapps-arm-6.0-pico-20160901.zip for Gapps.
[Moto Maxx Android Development] iiWoodstocK:
[MENTION=6324546]BayB[/MENTION]utcher27, here's the logcat.txt and dmseg.txt (both zipped together) after I noticed my IR sensors stopped working. 08/31 RR 5.7.3 & v2.0.1-4 BHB27 kernel. However, I just realized I didn't flash the SU4TL-49 sensors zip. If testing v2.0.1-4 of your kernel, should I have also flashed the SU4TL-49 sensors?
[Moto Maxx Android Development] fgl27:
app on the atthachments

not a flash zip... extract place the .apk on system/app folder set permission of the .apk to 0644 reboot the app must run OK...

Probably not try with current sensors files of the ROM, if it fail give it a try on the SU49

Ok, that is the latest google up the play version... I will check how things work with open as they set google contact sync that may be the problem conflict wit CM one not the contacts.apk problem, but a conflict with the two contact sync...

I never used the last V of open when I was on gapps because they experiment too much, I find a good version and if some day that cause problem then I update, that may not be the case just pointing that... gapps don't really change that much all the app that can be update will via play and those that can't if they work they will for a long time, so is not need to have the last V of a gapps...

Second post of TWRP thread there is a help about that I have made a how to encrypt decrypt backup etc. Only the Mod version of TWRP have encrypt backup support...

the encryption is on the Data, ROM .zip is on the system so must have no problem on running with encryption you can always backup before and then try, the only advice is encryption is to the Data all the data included internal memory so if you have problem and need to remove the only way is erasing the data partition and that erase/clean all yours data and internal memory so be aware of that...

encryption is a common android thing you can google that to see how it is on this and other devices will be no different...
[Moto Maxx Android Development] iiWoodstocK:
Ok. I flashed the SU4TL-49 sensors after getting those logs. I'll see if this makes any difference.
[Moto Maxx Android Development] fgl27:
I believed the kernel is the problem, after finding the Moto changes they are really big, will check them against the logs shared here to see If I can find some conclusion....

-----------

Quoting the kernel If any one have sensors problem try that one and post here, if find problem with the kernel post with logs...
[Moto Maxx Android Development] iiWoodstocK:
HEY!!!!!! YOU CHANGED YOUR USERNAME! lol, hello bhb27! :P
[Moto Maxx Android Development] gangrenius:
Bay butcher always reminded me of the Boston strangler or the butcher of Bakersfield
[Moto Maxx Android Development] kitcostantino:
im confused...also, for some reason "baybutcher" reminded me of Two Gallants "Steady Rollin'". ;)

im pretty sure i cant thank twice.
[Moto Maxx Android Development] Marky__Mark:
Heres a future request, if you can do it. Can you add the broadcast tile to the quick settings tile options? I believe this is an aosp marshmallow thing and not CM. I want to add the battery tile to my quick settings.
[Moto Maxx Android Development] NepoRood:
IF you're talking about the battery saver, it's already there. You just have to add it, with "edit tiles". IF that's not what you're talking about, well, then...
[Moto Maxx Android Development] Marky__Mark:
Nope. The battery button already in the notification drawer so i can use android n ify.
[Moto Maxx Android Development] iiWoodstocK:
This battery tile? It's a Nougat feature, but Android N-Ify has it.
[Moto Maxx Android Development] Marky__Mark:
Marshmallow aosp includes a tile called broadcast that can be used to make whatever tile you want to add. CM removed that for whatever reason. Theres an app called custom tile settings that can be used in conjunction with that tile. I have it on my tablet. Its pretty cool.

---------- Post added at 03:44 PM ---------- Previous post was at 03:43 PM ----------

It does. But the latest versions are too unstable.
[Moto Maxx Android Development] iiWoodstocK:
Stable enough for me. Currently using #576 because I haven't updated yet. No FCs, no issues. My only issue is that double tap to switch apps doesn't work, but it never worked for me.
[Moto Maxx Android Development] Marky__Mark:
Ill try that one. Thanks

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

Its still buggy. Doesn't work well in landscape. It will be sweet when its stable!

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

Turn off fancy transitions and it works.
[Moto Maxx Android Development] iiWoodstocK:
Landscape animations are a known issue. They were disabled some time ago, and because there's so many other features, I don't think it's as high of a priority.
[Moto Maxx Android Development] Marky__Mark:
Yea. And it works well with Deep Darkness N theme.
[Moto Maxx Android Development] fgl27:
There was in the pass a tile to add others tiles... that is what you are asking right?

That was removed because performance problem, but there is a option for that but not in quick setting it self...

Setting > configurations > QuickSettings panel > Quick Setting Tiles

if is not that try again explain it better...
[Moto Maxx Android Development] Marky__Mark:
Its not a big deal. I figured out a solution. Thanks for the response.
[Moto Maxx Android Development] devilvj:
Hey [MENTION=5747496]bhb27[/MENTION], could you enable VoLTE for the Resurrection Remix ROM using the same method this guy here used for the Nexus 6?

http://xdaforums.com/nexus-6/general/verizon-nexus-6-verizon-users-volte-t3058117

Thanks.
[Moto Maxx Android Development] iiWoodstocK:
That won't work since the VoLTE files aren't even found in the ROM to begin with. And on top of that, Verizon likely is using proprietary stuff to implement VoLTE on the Droid Turbo. And for non Droid Turbo/Verizon users, VoLTE is usually something a carrier needs to approve for a device, which the XT1225 probably isn't approved since the XT1225 firmware doesn't even have VoLTE files either.
[Moto Maxx Android Development] iiWoodstocK:
So I just had the IR sensors stop working again. This time I'm using 08/31 RR 5.7.3, v2.0.1-4 kernel, and the SU4TL-49 sensors. I was able to go almost exactly 48 hours before the IR sensors stopped working. I noticed it once the 15% battery saving mode kicked in, however, I also entered battery saving mode at 15% yesterday and my IR sensors continued to work. I don't know what made this time different. I attached both the location and dmseg in case this one shed a little more light, since I know exactly what event caused it to occur.

Edit: So after charging my phone to 100%, I manually activated battery saver and initially my IR sensors flickered like they do when they stop working, but after about 1 second, they stay lit like they should when they are working. So I *think* battery saver might have some influence in "breaking" the IR sensors, but not consistently.
[Moto Maxx Android Development] fgl27:
Can you guys or any one with this problem Stop using Xposed?

I need logs of a clean install of the ROM no xposed installed.

The logs are too much full of xposed error logs and is hard to get what is coming from system or xposed...

The same goes to any one with this problem, report logs without xposed....

:good:
[Moto Maxx Android Development] JFCostta:
Same happened to me, as I've told before but right now there's another issue. When whatsapp shows me a Popup Notification, wave or pick up to wake doesn't work, I have to press power button. GPS lock wasn't working either but reflashing stock radio.img solved it. I had Greenify and Greenpower installed on the device and removed them but problem remains.
[Moto Maxx Android Development] iiWoodstocK:
FWIW, I was looking through my logcat and just about all the clutter is from other stuff (kernel stuff, GSam, Zooper Widget), not Xposed. Besides, I start classes tomorrow, so I might not have the time to monitor exactly when my IR sensors stop working since it usually takes 24+ hours for them to stop.

Anyways, maybe this will help. The exact time I hit 15% and battery saver enabled was at 20:28:25, so my IR sensors stopped working at/shortly after that time. Since I was looking through my logs, I also have a cut down version of my logcat that starts at 20:00 (I can also cut it down to start exactly at 20:28:25) if you want that.
[Moto Maxx Android Development] fgl27:
ROM update! ResurrectionRemix-M-v5.7.3-20160905-quark.zip​

Download-ROM

Changelog

If dirty flash and the device don't boot make a clean install (Wipe dalvik cache, cache, system and data) then install the ROM + Gapps (demanding when clean install flash ROM+ Gapps at the same time).

...............

Notes:

This ROM doesn't have my kernel it have Stock-CM-Kernel but you can download and use it, I do this because some people may not need custom kernel or wanna to test without it.

Download BHB27-Kernel

Use only the latest version of my kernel today BHB27-Kernel-V201-4-M.zip base on Moto 6.0.1 source.

Bug report: make with in the most accurate description possible, do not spare words, screens and logs, a bug that i can't understand can't reproduce I can't fix.
[Moto Maxx Android Development] iiWoodstocK:
Oyyy, new Verzion stuff from the N6! I was finally going to make that VoLTE test thread I promised over a month ago! I've been busy on and off between then, and every time I have free time, I think of something else that delays the creation of the thread, lmao. Hopefully this includes some stuff I didn't pull from Shamu that helps with VoLTE.
[Moto Maxx Android Development] quantum tao:
Flashed ROM, pico gapps, and kernel, all my galleries are duplicated. Tried clearing data for gallery but still duplicated. Any ideas?

---------- Post added at 06:52 PM ---------- Previous post was at 06:50 PM ----------

Also there is new option for turning on enhanced LTE, hopefully 1 step closer to volte!
[Moto Maxx Android Development] iiWoodstocK:
Ayyyy, that probably negates my numerous VoLTE zips, LOL. All I've been able to do is get the AOSP "Enhanced 4G LTE Mode" toggle.
[Moto Maxx Android Development] quantum tao:
For some reason they pics are in both /sdcard and storage/emulated
[Moto Maxx Android Development] immadeofpixels27:
Could someone please grab this compass app and check the calibration of the magnetic sensors? Mine seem to be stuck at terribly calibrated and I want to know if it's a ROM issue or just my device
[Moto Maxx Android Development] iiWoodstocK:
/sdcard and /storage/emulated/0 reference the same location. As well as data/media/0
[Moto Maxx Android Development] quantum tao:
That's what I thought , but why are they both showing up in gallery? Come to think of it I did get some sort of storage error when I installed the last RR version., maybe its time to do a whole new fresh install.
[Moto Maxx Android Development] iiWoodstocK:
No idea. It doesn't show up on the gallery I use (old Play Store detached version of QuickPic)
[Moto Maxx Android Development] gangrenius:
Running new Firmware and kernel everything seems stable and smooth vzw droid turbo 1254
[Moto Maxx Android Development] Murd0c:
Edit: Fixed it
[Moto Maxx Android Development] SimpTheChimp:
So... Is the new build supposed to fix this contacts problem? Because it still crashes on me.

Flashed using new RR build, standard kernel, pico open Gapps.

Or is there something else I have to do to get it working?