yashsingh1/xdaforums huggingface dataset:
[Moto Maxx Android Development] iiWoodstocK:
I use yankactive. Interactive kept giving my random reboots.

Something I noticed, prior to the latest update, Cell Standby was really, really high no matter where I was. On the latest version, Cell Standby is still high, but it only increases greatly when I'm home. Yesterday, before I went to school, Cell Standby was listed at about 19%, while I was at school Cell Standby dropped down to around 7%, then by the end of the night at home it was at 31%. Before this update though it would've been a really high number throughout the day. I don't have the best signal at home, but I never had this issue on RR 5.5.9
[Moto Maxx Android Development] immadeofpixels27:
I find it very odd that I experience all the bugs others do, except for the ones that drain battery faster than normal.
[Moto Maxx Android Development] iiWoodstocK:
I'm not really experiencing any battery drain issues either, but the Cell Standby bug visually says I should be getting reduced battery life. My battery life has roughly been the same as RR Lollipop, but maybe Marshmallow is just battery efficient enough that it's negating any drain from the Cell Standby issue. ¯\_(ツ)_/¯
[Moto Maxx Android Development] immadeofpixels27:
Hmm that seems pretty likely. I'm also getting almost identical battery life on MM as I did on LP.
[Moto Maxx Android Development] gumbi2647:
Cell standby isn't showing up on mine but when it does it is no more than 2%. That's with all versions of this ROM.
[Moto Maxx Android Development] immadeofpixels27:
This happens on a daily basis for me:
[Moto Maxx Android Development] iiWoodstocK:
Here's a few screenshots of my Cell Standby "drain," right before I charge. I often screenshot my best battery life, that way I, 1) have references should my battery life unexpectedly decline, and 2) so I can try to diagnose it with the expanded stats. And it comes in handy for these situations.

Also, those screenshots are rather inaccurate, though. (Well, if that's the way things stay by time you charge, then its not too inaccurate. But standalone as is, its not too accurate.) For example, yesterday I had a point where Cell Standby was at 7%, but that was in the middle of my charge cycle (maybe at 65% battery). By the end of the day (about 10% battery) Cell Standby was at 40 something percent. Screenshots with very little usage and very little time since unplugged do virtually nothing to predict battery life. It works by predicting previous usage and adjusts. So if you just unplugged and used your phone for 30 mins straight, it might say something like 12 hours remaining. Likewise if after using your phone for 30 mins straight you set it down for 6 straight hours, it might say 1 day remaining, 2 days remaining, 3 days remaining, etc. The only way the battery stats screen is accurate is right before you charge. Otherwise it's constantly adjusting as time passes.
[Moto Maxx Android Development] fgl27:
I post this on the OP.

If there is more bugs that happens to all users let me know.

Thanks for the users workaround for the bugs that we have today... :good:
[Moto Maxx Android Development] streebs87:
Yup, settings are enabled. And I don't have Xposed installed. When I flashed the first build of this the twist to camera was working just fine because I remember setting it up to work with Motorola Camera rather than the camera that the ROM comes with. It now just isn't working, and I'm not sure why. I checked permissions and all that, rebooted, etc.

If no one else is having this issue is there any suggestions? It's not a huge deal to me, but if it's not broken then it will bother me as to why it's not working, lol.
[Moto Maxx Android Development] gumbi2647:
I know that the time left is not the actual time but I take mine off the charger at 7:30a.m and at 6:30p.m I still have 81% left with only 1% on cell standby. I changed from omni gapps to the slim mini gaps and it has help the behavior of my phone greatly. As far as cell standby I never had a problem.
[Moto Maxx Android Development] gumbi2647:
These are my settings with no problems with cell standby. I am also running greenify and amplify. All on Droid Turbo xt1254
[Moto Maxx Android Development] iiWoodstocK:
Hmm, I'm using different kernel settings, and OpenGApps, but I've been using this setup since the end of December. Perhaps it's because I flashed the SU4TL-44 radio. Maybe when I flash v1.2.6 test 09 kernel, I'll reflash ROM and GApps, but no SU4TL-44 radio this time and see how that works.
[Moto Maxx Android Development] gumbi2647:
Try slim mini gaps, omni gapps acted up for me.
[Moto Maxx Android Development] kitcostantino:
i dont see anyone here using the newest dankoman slim.zero gapps builds, but they have been great for me so far. i went back to LP RR, so i think its time for some MM RR love. ;) you can find dankoman here:

https://androidfilehost.com/?w=files&flid=15385

---------- Post added at 08:12 PM ---------- Previous post was at 08:02 PM ----------

that is awesome. did you use the phone much? lol. (SOT?) glad to see battery bueno
[Moto Maxx Android Development] raspdeep:
Slim zero doesn't support Now On Tap I think
[Moto Maxx Android Development] streebs87:
Sorry for the noob question, but I've never flashed just gapps before. Would I just flash then reboot? Any wipes needed?
[Moto Maxx Android Development] gumbi2647:
I use it moderately during the day and more at night. I have been on it now for two hours straight and the battery is down to 50%. As far as Slim gapps I have been using the mini gapps since the 12.1 based RR ROM. The only problems are the usual like screen freezing while playing a game and the chop chop flashlight. Other than that it is running smooth butter!
[Moto Maxx Android Development] wheels01:
I tried applying your CPU settings and my battery continues to drain at a higher than normal rate due to the cell stand by. I have to admit I haven't flashed a custom ROM in over a year but I followed all instructions. Unlocked my xt1254, rooted, installed twrp, made a backup and then did a full wipe (including internal storage). Installed latest build via adb sideload, recommended gapps and test kernel. Everything works great. Only bugs are the chop gesture for the flashlight, MMS being blurry and battery drain. Been running for 3 days. I'm going to still run it. It's worth it. Great work!
[Moto Maxx Android Development] ceelos218:
Ahhh I can tell my battery will be much better.. I've applied some of the settings some of you guys suggested. Including zzmove, profile 5 zbattp, lowered GPU to 700, installed open gapps mini instead of pico.. These settings in combination with greenify and amplify have done it. I was meaning to go back to 5.1 but looks like I'm good so far. Thanks guys for all the help.
[Moto Maxx Android Development] immadeofpixels27:
That's how it's done in stock Android. However, the animation is probably different in CM/RR, which causes the perceived jump in scroll. There's no option to change that animation in the settings, but you could try using a different recents menu altogether. (RR comes with Slim and Omni recents menus, found under settings>configurations>recents)
[Moto Maxx Android Development] Nitefire77:
Have you tried rebooting? I'm not having video issues in any app
[Moto Maxx Android Development] RLShiftyDoggit:
Yeah I have this is weird
[Moto Maxx Android Development] ChazzMatt:
If you restore to TWRP backup you have, does it still do it? If you flash an earlier version of ROM does it still do it? Did you flash any recent apps, install xposed modules? Did you flash the bad display drivers for the Nexus 6 not meant for our phone?
[Moto Maxx Android Development] RLShiftyDoggit:
If I revert it works it and I haven't flash anything besides ROM update kernel xposed and my gapps other then that nothing has changed
[Moto Maxx Android Development] Hawtpants:
Running latest RR + latest BHB27 kernel + intelliprofiles from Debuffer and everything has been silk smooth. Great job from Baybutcher and Debuffer.
[Moto Maxx Android Development] TheSt33v:
In case this helps anyone, I was having issues connecting to my office WiFi (my home WiFi works fine) on the last few builds of RR. I solved it by going to developer options and enabling Use legacy DHCP client and restarting the phone.
[Moto Maxx Android Development] xboxbr:
my phone reboot in idle many times a day and I don't know why .last build and kernel., no overclock, default voltage
[Moto Maxx Android Development] Moondroid:
Thanks for that tip. At home I'm using a mapped static IP address which makes Wifi connect really zippy. But I certainly might need your technique when I travel.

_______

Ok so: I still have the problem where my phone refuses to boot up when I dirty- or clean-flash ROM 5..7.0 + any bhb27 kernel beyond v129-9.

I either get a bootloop (twice) or the phone turns off about 2 minutes into the reboot (twice). Wiping dalvic+cache (multiple times) has not helped.

It happens when I use this process (on TWRP 3.0.2.0):

-- Wipe Dalvic + System + Cache ...or... Wipe everything except Internal Storage

-- Flash ROM 5.7.0 + pico-Gapps + SuperSU 2.65

-- Reboot

-- Make sure the kernel gets root

-- Back in TWRP, flash kernel v200-4 or v200-5

-- Wipe dalvic+cache

-- Reboot

Boot animation starts, goes on for minutes or phone turns off, never makes it to Optimizing apps.

Can't recall if both 200-4 and 200-5 give exactly the same problem result, but so far neither one of them has worked on my phone.

ROM 5.7.0 comes up fine when I don't flash the kernel. That's what I'm running now and it's purring sweet. (And I'm back on cellular, reactivated the phone, all is well on that side of things.) 5.7.0 also works fine for me with the v129-9 kernel.

Bottom line for me is I'm happy with what I have now. I'm oosting this mainly in case I'm doing something wrong or it can help development in any way at all.

Specific files used:

.. ResurrectionRemix-M-v5.7.0-20160622-quark.zip

.. open_gapps-arm-6.0-pico-20160612.zip

.. UPDATE-SuperSU-v2.65-20151226141550.zip

.. BHB27-Kernel-V200-4-M.zip

.. BHB27-Kernel-V200-5-M.zip

FWIW, the only other things I've flashed at any time with this ROM are:

.. xposed-v85-sdk23-arm.zip

.. Moto_Camera_plus.zip

This is an XT1254 verizon straight from stock SU4TL-44, nothing at all between that and this RR 6.x.x.
[Moto Maxx Android Development] rohheat:
http://xdaforums.com/lg-g3/development/rom-fulmics-rom-3-0-tweaks-hub-ota-v30b-t3304556

can any one port this rom for our device?
[Moto Maxx Android Development] Nitefire77:
I highly highly doubt that would be possible. Its based on an LG stock rom. Our phones don't use the same processor, a lot of the code, drivers, etc in that rom are LG's anmd closed source. Its not open source like AOSP Roms are. Its just about near impossible for our phones, and IMO Lg's UI sucks
[Moto Maxx Android Development] immadeofpixels27:
Have you tried flashing RR, then kernel, then everything else? That's what I always do and I've never had problems.
[Moto Maxx Android Development] Moondroid:
You mean RR + kernel without rebooting between? I'm asking because the first time I installed RR I flashed everything in one swipe, and it worked fine . . . ?
[Moto Maxx Android Development] rohheat:
okay.bro..thanks... any other rom which can be ported for out device?

any of the nexus 6 ported roms????? it has many roms

same processor as ours

---------- Post added at 01:51 AM ---------- Previous post was at 01:50 AM ----------

can any one port custom roms of nexus 6 for us?
[Moto Maxx Android Development] immadeofpixels27:
Yes, without rebooting.
[Moto Maxx Android Development] gumbi2647:
I just reflashed mine and updated my open gapps. I flashed ROM, gapps and kernel. Wiped dalvik and cache. Then I flashed my xposed, and SuperSU. Reboot and all is good!
[Moto Maxx Android Development] Nitefire77:
While our phone is very similar to the nexus 6, Moto did a lot of things differently on our phones and Nexus 6 ROMs isn't an easy port. We also have just 2 active developers for our phone, which we are very lucky and blessed to have

What I suggest, if you must have a different ROM, read a tutorial on how to build a ROM a few times, sync the repos and build it yourself. If you don't want to do that, enjoy the ROMs we do have because we are very lucky to have them and the 2 wonderful developers we have working on them
[Moto Maxx Android Development] Nexovox:
Anyone else have this kind of battery drain? I don't know if it's just a bug because according to the battery ussage the call standby uses 10719mAh. That's not even possible because the battery only has 3900mAh. I've had this issue trough out the last few versions of the ROM and even clean flashed in between. I also tried turning off LTE and only use 3G because that's a known issue with Marshmallow but it didn't help.
[Moto Maxx Android Development] Nitefire77:
Yep that's the marshmallow bug. The reporting is way off, and its a glitch with the reporting because we only have a 3900mah battery. However the only thing that seems to really fix the battery drain for me is turn off mobile data while I',m on wifi
[Moto Maxx Android Development] gangrenius:
I second that conclusion
[Moto Maxx Android Development] Nexovox:
Ok thanks. In that case I'll set up a system profile to turn off mobile data with a wifi trigger and a second profile to turn mobile data back on as soon as wifi is disconnected. I guess that's the best way to do it.
[Moto Maxx Android Development] xboxbr:
I do this way

install ROM + GAapps + xposed, wipe cache and reboot (SuperSU isn't necessary, I think it's inside the ROM)

then I go again to recovery to install Kernel and other zips like "BLOATWARE remove", but

DONT wipe cache

this time

don't forget to update kernel auditor custom version
[Moto Maxx Android Development] Moondroid:
As far as I understand, installing SuperSU just gets us (other than a newer version) a GUI that lets us look at what's rooted, etc.

Another fail . . .

-- First I tried reflashing everything in one swipe. That got me the low-memory notice again, and wiping dalvic+cache didn't solve it. 4.23gb free, but the notification told me I only had 290mb free.

-- For a second try I first re-downloaded the ROM, pico-gapps and kernel 200-5 and reflashed all + SuperSU + Xposed. This time it got stuck in bootloop again.

I hope I'm not just throwing a bunch of red herrings out here. It's obviously either a weird procedural error on my part or there's something quirky about my phone. XT1254, unlocked with Sunshine. It's running great with 5.7.0 and the base kernel (or the 129-9 kernel), I just haven't been able to get the 200-4 or 200-5 kernels to work right for me.
[Moto Maxx Android Development] fgl27:
ROM update! ResurrectionRemix-M-v5.7.0-20160628-quark.zip​

Download-ROM

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).

Changelog

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

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-V200-5-M.zip base on Moto 6.0.1 source or BHB27-Kernel-V129-9-M.zip base on Moto 5.1.1 adapted to work on 6.0.1, please don't report a bug if not using the stock kernel of this ROM or my kernel this version always use the last version...

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] gimpy1:
Do you have a RR backup in twrp? If so, I would, and have, start all over again. Restore the backup.

Once it is restored, I would then do a rom and gapps update only. Then, if everything is working fine, do the other installs one at a time and make sure everything works correctly. It's a little tedious and time consuming, but it may help you determine the problem.

I am currently on the MoKee rom, but also use RR. Three or four days ago, everything was working fine, then went to crap, seems like. Several normal apps are fc'ing. Don't know for sure, but I think it was a couple of bad nightly updates that didn't work well with some of my apps. The latest nightly seemed to fix everything. Working smoothly now.

Whoops, I digress.

Good luck
[Moto Maxx Android Development] Moondroid:
Yep, I have 4-5 backups. Great suggestion, haven't thought of that among all the other scenarios I've tried. I'll give that a run in the next day or two.

The thing is, my phone works great on 5.7.0 with either the base or 129-9 kernel. And truth be told, I'll be very happy with that if I can't ever get the newer kernels to work for me.

I couldn't find the log files. Please remind me exactly how to generate them and where they're stored? Thank you :o:good:
[Moto Maxx Android Development] Nitefire77:
Installed without a hitch. Running purrrrrfect :)

I dunno why ottgers had issues with previous build not booting. It, and latest update has ran fine.

I dirty flash ROM+Kernel+gapps+viper+xposed+supersu2.74 in that order. No reboots in between. All and done
[Moto Maxx Android Development] gimpy1:
Yesterday on MoKee, I was having a hard time trying to get the latest kernel to stick also (2.0.0-5-m, or whatever it is). I had tried three or four different times. It would not install and stick even though I had the latest rom and KA installed. I kept trying to manually install it thru twrp. Finally, trying one last time, it gave me the choice to install it using the "flashify" app. Now, I had not used flashify in a few days but thought I would try it.

Voila! Flashify took it thru the entire process and after it had rebooted, I checked the phone settings and the 2.0.0-5 had been applied. So, go figure.

Might be worth a shot, if nothing else world.
[Moto Maxx Android Development] Moondroid:
It's a b.f.mystery to me too. :rolleyes:

Dirty flash - what exactly did you wipe before you installed, if anything at all?

Just to clarify, my one-and-only issue is the newer kernel(s), clean or dirty.
[Moto Maxx Android Development] gangrenius:
U change themes like my grandma changes her diapers

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

Wondering why it's called 5.7.0 when that's the last version? Is this a mistake or?....
[Moto Maxx Android Development] Nitefire77:
I only wipe cache/dalvik after everything's done flashing and I reboot

I did t change my theme only the wallpaper and home icon this time

Its still called 5.7.0 because that's the current version. RR 5.7.1 isn't out yet and this update just includes the latest CM and RR changes to github. But its still a 5.7.0 version untill RR does 5.7.1
[Moto Maxx Android Development] immadeofpixels27:
5 backups?! Move some of those to a computer or flash drive if you have an OTG cable. That's what is probably causing your low storage woes
[Moto Maxx Android Development] iiWoodstocK:
Low storage warning is a warning from the system, especially when it says there's a lot of space available. The root directories have a size of approximately 3.2 GB (well at least that's what my phone currently says) and sometimes updating ROMs for some reason increases the usage in the root directories. I don't know what causes it, but I've had that happen numerous times in the past. I used to rarely make TWRP backups, so what I used to do was reflash the previous RR (and everything else I flash) to put my device back to the RR I was coming from. Reboot system, then flash the RR update. That always fixed it for me.
[Moto Maxx Android Development] Moondroid:
I consistently have 4-6gb of free storage every way I look at it. And no problem at all with any installs at all except the 200-x kernels. I don't want to delete anything (more) and try to eliminate this particular "problem", because it only shows up when I try to move from the base or v129-9 kernel to a 200-x build.

Understood. But why would it make such a difference (why does this problem show) only when I flash one of the newer kernels? I can install the 5.7.0 ROM all day with maximum wipe (all but internal storage) or no wipe at all, with base kernel or 129-9, no problem whatsoever.

I don't get any indications of any problems at all except with kernel 200-4/5. Minus those kernels the phone runs sweet as silk, everything works fine and smooth, data, wireless, battery life is the best-ever on this phone . . . . I just can't install the newer kernels without getting "low memory" or bootloop or shutdown during reboot.

---------- Post added at 18:55 ---------- Previous post was at 18:46 ----------

Earlier today, after restoring a working 5.7.0 backup with the base kernel, I tried twrp'ing the 200-5 kernel only. I got the low-memory notification (250mb). Then I re-restored the 5.7.0 with base kernel, booted up, back to twrp and flashed the 129-9 kernel. It installs and works just fine, time after time after time.
[Moto Maxx Android Development] RLShiftyDoggit:
Everyone having battery issues and I'm sitting here like

View attachment 3797516
[Moto Maxx Android Development] rohheat:
i have been using this rom for passed 4 weeks now.. and yesterday found a major bug... when i opened my moto camera the slow motion video doesnot work... when i click on video icon on the right it clicks phots.. infact video recording works on moto camera.. and i need that moto camera for slow motion video..............
[Moto Maxx Android Development] NepoRood:
Reading the last few pages...

I just thought I would share :)

I noticed most everyone has a slightly different method to do an "upgrade" and most seem to work. Here's what I do, as long as I'm on the same branch of Android:

1) Load TWRP and backup current Data

2) Wipe (Factory Reset)

3) Install ROM Zip

4) Wipe Cache/Dalvik

5) Restore Data Backup

6) Reboot System

After the apps "optimize" and boot finishes, I do another system reboot.

I use stock kernel and I've never had to flash GApps more than once. I've used this method on several devices and I've never had any issues.

Regards,

Nepo

PS, I also don't use Xposed framework...
[Moto Maxx Android Development] kitcostantino:
okay. i saw your post and checked my slo mo camera. indeed, it did not work. the fix is to uninstall it (i used titanium backup and a reboot to uninstall) and reinstall it from the Play Store. Works perfectly on mine now. ;)
[Moto Maxx Android Development] Hawtpants:
Have been using RR + BHB27 kernel + intelliprofiles since I got my Quark. Everything has been running silk smooth and I'm having average 2 days of battery life with 7 to 8 hours SOT. Usage is browser/spotify/games/whatsapp. Absolutely fantastic job!! I suggest everyone using Intelliprofiles by [MENTION=5321318]Debuffer[/MENTION]
[Moto Maxx Android Development] Debuffer:
Thanks, bro. I wish you like the usage of this awesome rom, kernel and mod :)
[Moto Maxx Android Development] rohheat:
i shall try ....as u said
[Moto Maxx Android Development] Nitefire77:
I've been using the Moto Camera from the Moto G4 and its been working very well for me.

I gave the intelliprofiles 5.0 for a try a few days ago and regretted it. I'm sure its great for a lot of people, just didn't fit my needs. Star Trek Timelines took longer to load with them, lagged, my slot games took longer to load and the whole phone seemed sluggish. I was using the daily profile.

But, what doesn't work for me doesn't mean its not perfect to others.

I'm back to using the settings from iiwoodstock which has giving me incredible performance and battery life and am a lot happier. I recommend everyone try different settings to see what works best for them
[Moto Maxx Android Development] gumbi2647:
I tried the in teller profiles too and I had random reboots. I think that I fixed the radio issue that I was getting when coming off of WiFi. I for some dumb reason kept flashing the Volte zip that was released a while back. I guess I was hoping that each update would have gotten the Volte to work. Last night I clean wiped and reinstalled all but that and this morning no problems. ROM is running great with the latest everything!