yashsingh1/xdaforums huggingface dataset:
[Moto Maxx Android Development] iiWoodstocK:
FWIW, that APN setup is not what stock 5.1 uses, not does other devices use that configuration. The attached screenshots is the APN setup from SU4TL-49. AND the VZWINTERNET APN is close to what many current devices use.
[Moto Maxx Android Development] JayCizzo:
Just flashed BB's kernel and now wave to wake works fine. I might have the same as you still but my phone gets shut off 1-2 times a day so that might be why. If it stays working I'm not touching this damned thing again. Everything else is flawless.
[Moto Maxx Android Development] gangrenius:
This will eventually shut down. I think everyone's wave to wake shuts down.
[Moto Maxx Android Development] johnbravado:
I just moved from Arizona to Maryland and now my APN uses tracfone APN instead of vzwinternet. Is this normal? I have been having issues where I loses signal completely and then can't get it back so it just drains my battery until it dies or I restart.
[Moto Maxx Android Development] gumbi2647:
Try deleting the straight talk APN
[Moto Maxx Android Development] newbe1droidx:
+1
[Moto Maxx Android Development] fgl27:
regards the problem of proximity sensor used to wake the screen ambient display etc... that some users report

Is any user with XT1225 have this problem?

and if yes have you update your firmware to Marshmallow stock ROM?

I never see this problem on my device and it may be do some firmware update we have on Marshmallow and those XT1254 user have not received it, then related libraries that are update to Marshmallow stock and place on the ROM may be causing the problem to XT1254 users...

I will make some changes to the next ROM to see if those can help on that....
[Moto Maxx Android Development] 5525:
I switched to the Brazilian marshmallow for the DT (with BB's kernel) and saw immediate signal and battery improvement.

Screen on time was drastically reduced by the end of the day (not as a measure of battery, but as a measure of how long the screen was on) with much more battery left. I'm thinking two things in MY SPECIFIC CASE:

The cellular signal and cell drain was improved. Phone felt cooler.

For whatever reason the MM ambient display just wasn't equivalent in battery use to the Moto active display. Which makes sense because the Moto design is using the specific core and the system used to display it is completely separate than the normal unlocked GUI. Ambient display seamlessly transitions from locked to unlocked which makes me think it's not actually in the low power mode the Moto gets to. Because of this I think the constant pulsing and accidental screen turn ons in my pocket were counting as screen on time and all its associated battery use. I remember always being shocked at the battery usage and the amount of time the phone claimed I would have the screen on, despite being at work with little opportunity to do so.

All in all very pleased with stock Moto marshmallow. I miss the customization of this ROM but I'm finally back to normal MMS, normal signal, 5 hour SOT, and a phone that isn't always warm.
[Moto Maxx Android Development] iiWoodstocK:
FYI, signal strength appears better, but the actual signal strength measurement (dBm) is the same. Stock Motorola uses a different scaling than the CM based ROMs. The dBm scaling in relation to how many "bars" full the mobile data icon is is different between stock Motorola and CM based ROMs.

And [MENTION=1410291]skrilla[/MENTION]x_CZ ported Moto Display to CM (and CM based ROMs) and from what I understand, he made CM's Ambient Display functionality exactly the same as Motorola's Moto Display. Functionality and implementation (regarding how efficient it is) is the same as stock Motorola's Moto Display.

And with regards to your APN issue, I just deleted all the APNs except for the VZWINTERNET one, then I reconfigured that one to be like the APN used on SU4TL-49. I haven't had any issues with MMS, data, or signal strength. The way the APNs work is that the field entitled "APN" cross references a "library/book" of APNs that are already on the phone.
[Moto Maxx Android Development] 5525:
I appreciate the hard work in porting, but I just don't think it's as efficient as the stock implementation - at least on my phone.

I tried everything to edit the APNs to be the same as stock 49 but if I touched certain fields the APN would just delete itself. It was bizzare and maddening and occurred on Bliss and RR, which makes me think it was related to CM itself. I'm the only one with this problem though apparently.

When I installed your MM 6.0 I did a full factory reset and restored apps alone from TiBu so perhaps that alone explains my improvements. I doubt it though because I wiped all cache and davlik etc many many times before this...

I think at this point I'm going to stick with your 6.0 unless Vzw releases their own and CF gets his hand on it. Great work.
[Moto Maxx Android Development] gangrenius:
So if we go back to stock rom from this rom it asks us to uninstall sensor firmware. So I agree that that is the cause possibly.
[Moto Maxx Android Development] fgl27:
The thing it is, When I go back to stock 6.0.1 it doesn't ask me to uninstall firmware, So I know I'm using the latest version of firmware, and on this ROM and others CM we use the latest libraries to match that 6.0.1 firmware.

Theoretically that may be the problem if are not using the latest firmware that unfortunately only available to XT1225 users, if the user is on XT1225 and update to the latest and that fix it, then is possible to know the "Fix"... in the XT1254 case we can't know for shore until 6.0.1 is released, there is no way that I know to update only the firmware for the sensors, as I don't have the device can't do any test in this level and this type of test can temp brick a device so it is a thing only for the more hardcore users...

Let see how things stay on future RR update...
[Moto Maxx Android Development] newbe1droidx:
Yes, if you go back to stock ROM 5.1, it will want to revert back.
[Moto Maxx Android Development] Marky__Mark:
Official android 7.0 has been released. We'll see how long it taked CM to build it.
[Moto Maxx Android Development] Latiken:
My Cell Standby is draining battery like crazy again. The only thing I've done is change the APN, but then it changed back and it's still draining.
[Moto Maxx Android Development] Marky__Mark:
You might have to wipe everything and reinstall. That happened to me and re-dirtyflashing didnt help.
[Moto Maxx Android Development] iiWoodstocK:
It always will "drain" when connected to LTE and Wi-Fi. It's a bug with Marshmallow itself. You can alleviate it by using an Xposed module that'll switch to 3G when your screen is off, but aside from that you can't get away from it when your connected to Wi-Fi and transitioning from LTE.

FWIW, I've never noticed any adverse effects of the Cell Standby"drain." My battery life is the same as Lollipop, even though Cell Standby appears to be eating my battery.
[Moto Maxx Android Development] fgl27:
ROM update! ResurrectionRemix-M-v5.7.3-20160824-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 last version is really complete RR add some nice new changes most to improve looks, Marshmallow base is update, I add a Turbo toast app it works perfect if the user don't like can just disable it + general improves all over.

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] NepoRood:
As [MENTION=7109882]iiWoodstocK[/MENTION] stated, the "Drain" is just an Android 6 bug, it's a mythical number that doesn't really mean anything. If you use your phone constantly all day, SOT will take over and the CSB drain will go down the list.

There's really NO WAY your battery can use more than what it has to give...

IF

your SOT is like mine (less than 3 hours per day on most days, usually less), and you're still having to charge everyday, it's most likely a "user" issue, and not a "ROM" issue.

Regards,

Nepo
[Moto Maxx Android Development] hpbrasil:
Does anyone know why this cell waiting spends much battery? It appears first on the unit of consumption, many people with this problem and so far no one has a concrete answer on this.

Thank you. :o:o:D:D

Used Google Translate.
[Moto Maxx Android Development] gumbi2647:
Read through the thread!! Its a known issue in MM but with a few kernel tweaks and turning off mobile data while on WiFi. You can improve the battery life! I actually have good battery life while on WiFi and mobile data but my cell standby is high too! Its a mythical number like fairy's and unicorns....
[Moto Maxx Android Development] hpbrasil:
Weird
[Moto Maxx Android Development] NepoRood:
Agreed
[Moto Maxx Android Development] Marky__Mark:
So what exactly is this drain? Because I dont think i have it. I got WiFi on half the day and there is no change in battery stats. Cell standby is always less than 10%. Usually at 5. I notice when im using my phone it uses some juice, but thats to be expected. When its asleep its completely normal. It used to be really bad. But not in the last couple months.
[Moto Maxx Android Development] iiWoodstocK:
It's an issue that occurs when Wi-Fi is on and also LTE. So let's say you're on LTE then connect to Wi-Fi, Cell Standby's "Cellular Radio Active" time increases. Also, if you're on LTE and Wi-Fi is on, but not connected, "Cellular Radio Active" time will also increase. This issue doesn't occur on 3G, usually by using a third party like Smart Radio (Xposed) or GravityBox's Smart Network, nor when Wi-Fi is disabled (when connected to LTE), nor when mobile data is disabled when connected to Wi-Fi (although MMS won't send or receive when mobile data is off).

tl;dr: it's a bug with Wi-Fi and LTE, together in any form; Wi-Fi connected & LTE disconnected / LTE connected & Wi-Fi disconnected. In both scenarios, both are enabled but one isn't connected.

I personally believe it's not exactly as big of an issue as some people state. The battery stats definitely say is using a lot of battery, but that's an estimation based on data it's collecting. Generally for me it'll say Cell Standby has used an absurd amount of battery, for example 9000 mAh, which is more than 2 times the capacity of the Quark (I'm also usually on Wi-Fi nearly 80-100% of the time). I personally don't see any negative difference between my battery life on Lollipop and Marshmallow, even though on Marshmallow it says Cell Standby is using a lot of power.
[Moto Maxx Android Development] Marky__Mark:
I know what it is. I went back to lollipop for a month after CM13 became official be because it was a big difference. Then i came back to CM13 and didnt notice a difference. Its either fixed or so small, its not even an issue. Or the cell drain comes only during the phone being in use. Ive googled about it and didn't find much on it being a global Google bug.
[Moto Maxx Android Development] gangrenius:
The wave to silence alarm and the wave to see notifications still are quitting, on the droid turbo Verizon 1254 the pick up always works but after 2days wave stops working. ?
[Moto Maxx Android Development] gumbi2647:
What is #128546? Don't know that one!
[Moto Maxx Android Development] Marky__Mark:
This rom is rock solid. However, the Usb mount isnt working correctly. When i plug in my computer, i cant see all my files in the sdcard. Any way to remedy this?
[Moto Maxx Android Development] gumbi2647:
Go to developers options and scroll down until you see the one USB configuration. Then choose mtp for media transfer protocol. You have to do that every time but that's how you do it!
[Moto Maxx Android Development] NepoRood:
~Duplicate answer~
[Moto Maxx Android Development] Marky__Mark:
Thanks, but did that. This problem started happening after 5.7.1. I think 5.7.2 it was worse and couldn't see half the folders. Now i can see all the folders, but it doesnt show all the files within those folders. Isyncer doesn't work so i know its not working. Isyncer is an itunes music importer for mp3 mp4 files. So it cant import those into my phone.

---------- Post added at 09:32 AM ---------- Previous post was at 09:23 AM ----------

If anyone wants to try to reproduce it, i would appreciate it. That would tell me that maybe im missing drivers or something. Wouldn't make sense though because it works on prior releases.

---------- Post added at 09:59 AM ---------- Previous post was at 09:32 AM ----------

I bet it has something to do with the stock kernel, actually.
[Moto Maxx Android Development] gangrenius:
Hey bruh!, he built a fix in for this in the latest update hence why I mentioned it AGAIN!
[Moto Maxx Android Development] fgl27:
Not A ROM or ROM version xxx problem, android/app/changing too much your ROM yes...

That seems to be a permission problem you can see your files on the device but you are using special privilege that the PC don't have.

Usually happens when you create a file/folder on Stock ROM and can't see that when running custom ROM, or a file/folder created by another user , or a app saving files with wrong permission or user tag...

Just cut all the content you can't see to a folder that you can see and they will appear, then cut they back from were you cut them form in the first place...

This process doesn't work on empty folders so test before you do with a file or a none empty folder.
[Moto Maxx Android Development] Marky__Mark:
Let me give you an example. Its strange. I open my downloads folder and see about 25% of my files. I open up my music folder and see only one folder of an artist. And there are about 30 folders per artist with music in it. I first noticed it in 5.7.2. I couldn't even see most of my folders in the internal storage. Then i flashed 5.7.3 and i see all folders but only some of whats in them.

---------- Post added at 03:31 PM ---------- Previous post was at 03:28 PM ----------

And im on the stock kernel. I have a feeling if i flash your modded kernel, it will work. But im debating that because i like how my phone behaves now.
[Moto Maxx Android Development] fgl27:
Es file manager with root permission must see it all. go to the root of internal data:

/data/media/0

do what I post before cut> past on new folder > check them cut back but this time on the "sdcard" folder.

The ROM/Kernel have no problem in relation of what you post:

there is too many user on this ROM if this was a problem of the ROM must have more them just you with the problem so stop thinking this or that version ROM/kernel ETC...
[Moto Maxx Android Development] gangrenius:
Yeah never seen this as stated above
[Moto Maxx Android Development] Marky__Mark:
Ill try it.
[Moto Maxx Android Development] colthars:
i have a issue like this too. when connect to pc, i can just see newer files. old ones (like 30 days or more) don't appear on windows. already made a clean install and no results. always using last bhb kernel and rom.
[Moto Maxx Android Development] ChazzMatt:
Do you have Droid Turbo also?
[Moto Maxx Android Development] colthars:
mmaxx Brazilian version.

also, i have this bug where on boot s2w turn off and make dt2w stop working.
[Moto Maxx Android Development] gumbi2647:
Brush, I have never heard anything about #128546. That's why I was asking! You ask a question on here that I was wondering what you are talking about. You are about an arrogant MF as they come!! I won't ever ask you a question again. I wasn't being a smart ass like you!!!!!
[Moto Maxx Android Development] ChazzMatt:
Well, there goes that theory. I was thinking it was something specific to the Droid Turbo XT1254 perhaps.
[Moto Maxx Android Development] gangrenius:
Are you that slow? U asked me about #128456 wtf is that? I thought u were being a smart ass and saying that's how many times someone has mentioned the wave to silence problem. Where did u come up with that big ass number. And for what.
[Moto Maxx Android Development] hpbrasil:
Please if you do not mind can fix the bugs in theme I have?

I am unable to make a correction here, if correct and send the corrected apk am very grateful.

1 Bug on the themes selector (is white in color)

2 Bug at the source of the notifications is in black color and font have to is white in color

3- Whatsapp some places as settings is with black font and the font has to be white, the prints are the links I sent.

The prints with the said bugs are the link, thank you.

I am very grateful if you can do it

[MENTION=6324546]baybutcher[/MENTION] or [MENTION=3250376]ChazzMatt[/MENTION]

Exo UI

https://drive.google.com/open?id=0By5f1ehza_9AWTBMYzBpb3p4MW8

Prints

https://drive.google.com/drive/u/0/folders/0By5f1ehza_9AZWMzamEyREJaNkU

Use Google Translate.
[Moto Maxx Android Development] gumbi2647:
I'm not slow apparently you are if you typed it and don't remember! Notice the screen shot of your post....
[Moto Maxx Android Development] ChazzMatt:
Your screen shot is showing something that is NOT there. Your app (or whatever you are using to see XDA) can't decipher the emoji and is subbing an error message or something.

Your quote even shows the emoji -- in Chrome browser! Compare the two images below...

CHROME BROWSER

YOUR SCREENSHOT
[Moto Maxx Android Development] gumbi2647:
I'm using the XDA labs app! But thanks for clarifying that.. I wasn't sure why it showed up with numbers.
[Moto Maxx Android Development] iiWoodstocK:
XDA Labs shows &#128546 probably because XDA is still built on BBCode, and XDA Labs/Android doesn't read those emojis and/or those emojis aren't defined within Unicode's emojis.
[Moto Maxx Android Development] ChazzMatt:
When I use a smiley face in Outlook some email apps displays it as a "J". My sister asked me, why do people keep putting J J J in their emails? I had no idea what she was talking about, and she said "You do it too!" So, I had to read one of MY emails on her phone and then figured it out.
[Moto Maxx Android Development] gangrenius:
Yeah man whatever you are seeing is not what was written WOW! THAT'S CRAZY
[Moto Maxx Android Development] fgl27:
this is a android problem, can happen to any device on any ROM, like I post before...

Do you understand what are you asking? please try to understand...

most .apk can't be modify, you need the source and rebuild it, go to the dev and ask him for a fix, this is not the type of things to ask on a ROM thread.
[Moto Maxx Android Development] Marky__Mark:
This worked. Thank you. I didnt want to go through the whole cut and paste process so i just booted into recovery and copied my two folders i cared about onto my desktop. Yes they were visible. Then deleted the folders and booted back into android then copied the folders back to internal storage.
[Moto Maxx Android Development] fgl27:
Regards those with sensor problem...

This are the files responsible they are in the system folder:

bin/stm401 0755

etc/firmware/cy8c20247_24lkxi.hex 0644

etc/firmware/sensorhubfw.bin 0644

etc/firmware/sensorhubfw_p1.bin 0644

etc/firmware/sensorhubver_p1.txt 0644

etc/firmware/sensorhubver.txt 0644

lib/hw/sensorhub.apq8084.so 0644

lib/hw/sensors.apq8084.so 0644

vendor/lib/libsensor1.so 0644

Lets try to use the files from the latest stock Moto/VZW ROM SU49, I don't have it will take a wile to me to get it so... those on XT1254 one must have a backup of it, TWRP backups can be open on winrar or related, just replace the .win with .tar and use any app that can read tar files use the system.ext4.win may have more then one file win000 and win001 change that to .tar extra it on a separated folder then paste one on the top of the other to make one full system/ folder...

make a backup and try those files, the number next to the file is it permission after replace it check that and reboot, in case of problem use the backup or dirty flash the ROM you are using... then report on the tread and share those files on a zip here...

:good:
[Moto Maxx Android Development] Shooting Star Max:
It has happened to me too. The 'bug' happens when a Microsoft Outlook user (the desktop programme, not the website) types ':)' and autocorrect converts that into an ASCII smile: . I don't really know why and how it gets converted into a 'J' in other mail apps, but it happens.
[Moto Maxx Android Development] hpbrasil:
Sorry.....
[Moto Maxx Android Development] iiWoodstocK:
For those who don't want to be bothered with swapping these files themselves, I can probably have a flashable .zip ready by Wednesday (8/31), but I make no promises as I have a few VoLTE theories that are higher priorities.
[Moto Maxx Android Development] NepoRood:
These files are all present on latest Bliss Rom I built, I started using stock unmodified apq8084 kernel source. Guess that it explains lack of display issues in my thread. I too have a TWRP backup of SU49 update and can get all these files pulled for you later today, after work :good:

Regards,

Nepo

PS: I knew you would figure this out :highfive:

EDIT:

Didn't figure it would take long, so I just went ahead and did it. Here's all the files from my TWRP backup (SU-49) attached
[Moto Maxx Android Development] fgl27:
I believed the kernel is not the problem here, you have no report may not be relate to the problem not be existent on other ROM, I don't have the problem ever so it must be a relation of device VS blobs, if you are using CM-13 tree for vendor you are using blobs from marshmallow XT1225 and them the problem of sensor must be present unless it is a relation to something else that I'm not aware that not affect XT1225 and that is odd and hard to find if it is...

I really wanna to understand from were this comes from and the kernel must not souse it as I never change any related to this sensors... but if you have some test that prove this let me know..

Will push a flash zip with this files after I do some test I post on the tread.
[Moto Maxx Android Development] fgl27:
I made A zip for XT1254 to test the sensor problem... "SU49_Sensor_Files_Flash.zip"...

In case some one wanna to go back just use the "CM13_sensor_files_Flash.zip"

I test this it work on a quick test on my device, so it must work ok on XT1254, let me know the result... :good:
[Moto Maxx Android Development] NepoRood:
It was just a guess my friend, lol. Not a lot of difference in our ROMs on the inside (both being CM based), aesthetic values mostly. But, I am using Bliss Roms toolchains and qcom common device, and honestly don't know if that has anything to do with it either. However, when I was playing around with different TC's, my ambient display did start acting up...

Regards,

Nepo

PS, I'm using the vendor that I forked from you.
[Moto Maxx Android Development] JFCostta:
Appears to be fixed

I was having this issue too, ambient sensor only worked when my hand waved very close to the upper sensor (next to front camera) and now after flashing this zip it is more responsive. But one thing is still broken: the green notification LED (man, I didn't even know my Maxx had this one =)), it just remains on when a notification comes, instead of blinking and disappear as expected.

Anyway, thanks for this fix, even the battery drain looks better.
[Moto Maxx Android Development] iiWoodstocK:
The green LED doesn't blink. It's original purpose on stock was to be a "sign of life" indicator, not a notification light.
[Moto Maxx Android Development] JFCostta:
Thanks for clarification, I will leave it enabled for a few days and watch if battery draining has increased. It helps me a lot when the notifications are set in Priority mode.