yashsingh1/xdaforums huggingface dataset:
[Moto Maxx Android Development] gimpy1:
Ok. Not even worry about the message and the play store app, then?

I will include the SuperSU zip from twrp whenever I install something then and be good to go?

Thx.
[Moto Maxx Android Development] rkoonts4:
On the 6/9 build. Using BB's battery savings settings on his kernel. Phone has been off the charger for 8 hours 45 minutes and battery is at 93% (statistics say over 2 days left). Definitely liking this rom!
[Moto Maxx Android Development] rkoonts4:
After installing the latest nightly (nightly	Download: MK60.1-quark-201606132221-NIGHTLY) the wifi stopped working. Continuous scanning but never finding any networks. I restored the backup I made of yesterday's update and wifi was restored.
[Moto Maxx Android Development] vasyltheonly:
Advanced calling

Does anyone know if advanced calling is working on the newest ROM and how do you activate it?
[Moto Maxx Android Development] boomslick08:
I've been running Mokee L for a month or so, and I finally decided to go to Mokee M. I wiped dalvik, cache, system, and data. Then flashed the latest nightly, suggested gapps, BBs kernel, then SU. Phone boots and goes into setup wizard, then Google play services crashes and sticks me in a setup loop. What causes this loop, and can it be fixed?
[Moto Maxx Android Development] Debuffer:
You'd have to install the rom without gapps.

Install rom

Complete setup

When you're in the home screen, reboot

Install gapps.
[Moto Maxx Android Development] gimpy1:
I'm not sure about this latest nightly. I've been having fc's in the MoKee Center in settings and my browser (Naked Pro) force closes, too. I manually reinstalled the rom, but didn't seem to help. I did notice that the download size is quite a bit different than the last few have been. Hopefully tomorrow's update will be a little better.

I have upgraded to the latest KA and to the latest kernel. I am not using bhb's kernel right now and still have those fc's.
[Moto Maxx Android Development] gimpy1:
I just did the install of the latest nightly from the MoKee Center in settings. The install failed and, I guess, went into a boot loop. I let it go for over an hour. I finally had to go into twrp thru the "fast boot" method, I think it's called. Anyway, I am now on my restored backup from a week or so ago.

As far as I know, I didn't do anything to cause the boot loop? When I did the restore on the backup, twrp had a message in red letters that said failed to mount '/system (invalid argument) . This is an FYI in case others have a problem.
[Moto Maxx Android Development] gimpy1:
I just did a reinstall oh the 06-29 nightly, and it installed fine on my restored back up which, I think was from the 18th . So, not sure what caused the boot loop? I have not installed/updated the kernel or anything extra, yet. Do that tonight.
[Moto Maxx Android Development] hpbrasil:
WiFi signal is weak, had a lg g4 and was stronger: / is to improve?
[Moto Maxx Android Development] dextroit:
Hey, I just installed this ROM and everything was fine until I tried to update SU binary via the app then/twrp but that not worked, so I flashed the zip and now it's stuck in bootlogo I don't have the ROM File to re-install or a backup, what can I do?

Thank you
[Moto Maxx Android Development] gimpy1:
Can you get into recovery and try restoring the rom?

Bad terminology. Reinstall the rom? MAKE A BACKUP! First order of business??. Hope you get it fixed.
[Moto Maxx Android Development] fgl27:
TWRP is just like the android OS in most situation, so you can share files between PC and the Phone when on TWRP, just plug the USB cable the you must see on the PC the device, of course yours PC must be ready to connect with the phone, maybe need to install drivers on the PC.

Then you have USB-OTG support on TWRP.

Of course in both cases is need to have the ROM zip, not on the device but in some PC to use as source...

Then if none of those is possible, you may be able to wipe Dalvik/art Cache, Cache and Data on TWRP then boot (wipe a total of tree partition, don't confuse Dalvik with cache), if after those wipe there is no boot, you broke the system and that can be only fix by flash of the ROM zip, or of course a working backup...

* wipe of the data erase all your apps, app data and changes you made to the ROM, it doesn't erase your files on internal memory.
[Moto Maxx Android Development] Quetzalfp:
Hello, I installed the last nightly and wifi is not working, everytime I try to connect it fails and instead start the phone wifi hotspot. I'll return to an older nightly
[Moto Maxx Android Development] dextroit:
Thank you!!! Ok now is fixed, just one more question how do I gain root access? I can't flash SU and from Play Store the binaries won't update.
[Moto Maxx Android Development] fgl27:
way you cant flash Su?

I always use v 265 no problem maybe the problem is on the zip or version you are using.

Mokee comes with building super su disable by default, enable it on developer options (about a phone tap on build number many times) then back... developer options > Root access > Apps only.
[Moto Maxx Android Development] dextroit:
I can flash it but that was the reason that the phone got stuck in boot logo.... I flashed v 2.46 from chainfire page I guess is not updated
[Moto Maxx Android Development] gimpy1:
I just wanted to say that I have been on MoKee for the last four or five days. I mostly do the nightly updates, then always install K. A. and bhb's kernel. So, today I installed the nightly 7/8 (the current one). I then hit the button to do the update. Normally this does a complete install thru twrp automatically rebooting.

Today it did not install the script in recovery and reboot. It has done this before. The only way I know to get out of the boot loop it does, is to do the fast boot (?) recovery and then get into twrp and restore a backup. That is what I did. I restored my RR backup which is what I am on now. As I said earlier, I've had to do this before.

My question is, why does sometimes it works properly, and other times (like today) it doesn't. Is there something wrong with the updater or what?
[Moto Maxx Android Development] Quetzalfp:
Hi guys, a little help over here.

I installed again the last nightly and wifi still is not working, everytime I try to connect it fails and instead start the phone wifi hotspot and turn off the mobile data. The only nightly that work for me is the MK60.1-quark-201607012026.

Am I doing something wrong? I start the installation from the Mokee Center, from there it reboots to TWRP, start the flashing and then reboots.

Thanks in advance!
[Moto Maxx Android Development] fgl27:
Must be of common Knowledge that a android OS is not met to be update every day, what you are doing is a dirty flash doesn't matter that is from a update OTA file from the update app is a dirty flash of the OS, in those cases a new change to the system is not compatible with the old Data, so a clean install is advise.

the above and below must help you...

.......

I update the OP so it doesn't mislead.
[Moto Maxx Android Development] Quetzalfp:
Thanks, I'll try that.
[Moto Maxx Android Development] cnoevl21:
nightly vs release

nvm. i was lazy and didnt read posts. sorry
[Moto Maxx Android Development] cnoevl21:
no OS after flash?

i downloaded the latest 'release' zip and tried to flash it. I tried flashing it a half dozen time, but when i go to reboot i get a message saying "no os installed."

what am i doing wrong?
[Moto Maxx Android Development] gimpy1:
He suggests doing a clean wipe if there are problems. Have you tried that, yet? Then dl and flash the rom, then flash gapps and reboot.

I would do nightly updates, but then every once in a while, the updater would not work and it would send me into a boot loop. The only way I knew how to get out of it was too restore a backup. Now, if I am understanding him correctly, is you have to do a clean wipe and new install to the "releases", not necessarily to the "nightlies"?

I had not realized that there were different types of automatic downloads until you mentioned it here.

Having to do periodic clean installs is going to take away some of the desire to do updates so often. ????
[Moto Maxx Android Development] cnoevl21:
i wiped dalvik, system, data, cache. then flashed the rom. says no os installed. super weird. im coming from computerfreek 5.1. Is there like a root rom you need to flash first? then update to one of the newer versions?
[Moto Maxx Android Development] fgl27:
The ROM zip is 500+MB and in the name must have Quark word.... Check those, and when install it twrp will display way it fail after install, print the screen on twrp and post here, may need more them one print.
[Moto Maxx Android Development] cnoevl21:
the one i downloaded was mk60/1-quark-160712-RELEASE.zip 556mb. ill get the other info later on tonight.
[Moto Maxx Android Development] gimpy1:
Well, I did today's update. When it rebooted, the opening page and the password page were upside down. I had read other posters refer to this in other threads but didn't pay any attention to their fixes for it.

The lockscreen wouldn't let me/take my password. The only way to get it to work was to go into recovery and do a restore. So, I will wait a nightly or two before updating again ????.
[Moto Maxx Android Development] aleks_tar:
I've just installed this ROM from MK60.1-quark-160712-RELEASE.zip, wiped cache and dalvik, rebooted the phone and it started without problems, but after I installed the GApps from Slim_zero_gapps.BETA.6.0.build.0.x-20160516-2250.zip, wiped cache and rebooted I got a lot of error messages like "Unfortunately, Google Play services has stoped" and "Unfortunately, Setup Wizard has stopped". The same case with other GApps from open_gapps-arm-6.0-pico-20160717.zip. Each time I tried new GApps, I reinstalled the ROM from scratch (wiped all except internal storage). Does anyone have the same problems?

My device: XT1225 Motorola Moto Maxx.
[Moto Maxx Android Development] fgl27:
You are not following Installation Instruction of OP, they must be fallow.
[Moto Maxx Android Development] cnoevl21:
stuck on motorola screen for more than 20 min. im guessing this is not normal?
[Moto Maxx Android Development] cnoevl21:
here are images of what i get after flashing.
[Moto Maxx Android Development] fgl27:
Ok, the second pic, Show to you right after you click on reboot to system on the first pic?

I need to understand that.. if really you do noting else after the first pic, if you just click Reboot to system...

TWRP can take logs after the installation before reboot or do other thing take one... Advanced>Copy Log.

The log will be on internal memory.

or if you have a USB driver plug to TWRP you can before take a log, go to Mount> check if is Mount>Select Storage> Chose USB OTG...

then take the log it will be on the root of the driver...

Share here please, if XDA zip it in case XDA says the file is not supported...

:good:
[Moto Maxx Android Development] cnoevl21:
Yes. after flashing (first picture) all i do is hit reboot system. Does twrp take logs automatically? I have since flashed back to 5.1. If i flash mokee again i cant reboot (no os) so how would i get the log?
[Moto Maxx Android Development] fgl27:
Assuming you flash back 5.1 without erasing internal memory, the log will be there doesn't matter the OS you load.

TWRP can conect via PC to file share.

if no usb driver is available, use a normal usb cable take the log and copy it to pc.
[Moto Maxx Android Development] gimpy1:
cn, that is exactly the message that I have received a couple of times. Unlike you, I did not flash back to 5.1. Instead I had to get into twrp (by fast boot method? It was the only way) and I restored a RR backup. I'm back on MoKee now. The lady nightly I updated made things upside down (7-22).I'm now back on 7-21 waiting for another update ????.
[Moto Maxx Android Development] cnoevl21:
what would the log file be called? And where in internal storage? i dont see any log folder in the twrp folder

---------- Post added at 12:36 PM ---------- Previous post was at 12:34 PM ----------

i just picked up an otg flash drive and put my computerfreek 1.3.7 backup on it. so thats what i flashed back to.
[Moto Maxx Android Development] fgl27:
a log file call recovery.log in side internal memory no folder.

things are simple.
[Moto Maxx Android Development] cnoevl21:
Hope this is the right thing.
[Moto Maxx Android Development] frankeegee:
I have three backups on my phone all the time. One is computerfreek's, one is MoKee and one is RR. I keep MoKee and RR up to date, but have not used cf's in a while.

So, I can always reinstall MoKee or RR if need be.

FYI, just the way I do it. ☺️
[Moto Maxx Android Development] ChazzMatt:
Even though I have the 64GB XT1225, I don't have enough space to keep 3 backups! I only have enough space to keep two. When I make the 2nd everyday, I then delete the previous one to only keep one. If I forget to delete the old one, the next backup (a 3rd one) will fail due to lack of space.
[Moto Maxx Android Development] gimpy1:
I only have the 32 gb, which makes it tight for space. For whatever reason, I don't know/understand how to do it, but I can not back up to my computer like I want to (cf's backup). I've tried several times to back up via OTG from twrp and it will not backup to the computer. Pretty sure I'm not doing something right, either from the computer or the phone.
[Moto Maxx Android Development] fgl27:
Do you understand that I need a log of the problem?

That what you share is a random TWRP log, if you are doing before take that log the process that you describe before sorry because there is noting on the log.

+ before you do go TWRP thread and Download and Flash the latest Mod version you are using the old TWRP the new I made is better for install backup logs etc...

:good:
[Moto Maxx Android Development] cnoevl21:
pick up an otg flash drive. 64gb for $10 on amazon
[Moto Maxx Android Development] theatomizer90:
For the GPS fix:

Do I have to use mfastboot for this or can I flash it with TWRP?
[Moto Maxx Android Development] ChazzMatt:
Yes, you have to msfastboot it.

Also, you have to be on the XT1225, NOT the XT1254:

The "clean modem" file mentioned later in this thread and other threads are better for your use. Or you can flash the TWRP-flashable Droid Turbo radios found over in the Droid Turbo forum.

[Droid Turbo XT1254] Bootloader & Radio Packages (+Unlocked warning removal)

http://xdaforums.com/droid-turbo/development/droid-turbo-xt1254-bootloader-radio-t3259327

Look specifically for the TWRP flashable links in that thread. They are there in the OP along with traditional msfastboot links.
[Moto Maxx Android Development] theatomizer90:
Oh... It's good I didn't then I am on the 1254 (turbo) so does that mean I have to flash back to stock? The process is:

Flash to stock

Get a gps lock (so just find myself on maps)

Then flash mokee over the top? Do I have to wipe before I flash mokee?
[Moto Maxx Android Development] ChazzMatt:
See my edited reply.

You can flash TWRP radio or use [MENTION=5747496]baybutcher27[/MENTION] "clean modem" file.

_____

That quote is mostly for the Clean Modem file download, which works for all Quarks with TWRP custom recovery installed.
[Moto Maxx Android Development] theatomizer90:
Thanks a bunch! I didn't think that flashing radios would solve it but it makes sense. I appreciate you taking the time to help me out.
[Moto Maxx Android Development] gimpy1:
Can someone tell me how to get the Mokee boot animation to working? I am wanting the dark or black Mokee animation.

I think it is probably theme related that I can not get it as I have applied and restored different themes over time. I have tried but can't get it back. I am currently on the "default" theme. But the Mokee boot is not working. The animation is a blue squiggly line with an "eye" in it that propels itself like an octopus. I would like to get rid of it, but can't. Any suggestions is appreciated. Thx.
[Moto Maxx Android Development] fenix3nk0r3:
How to remove a google keyboard in the rom and after flash opengapps?

because i install opengapps but google keyboard was not updated
[Moto Maxx Android Development] gimpy1:
A little while after yesterday's update (8-25-2016) my phone started a system ui crash. None of the on screen buttons would work. I had to do a reboot to get the phone to work. But then it would crash again. After two or three sessions of this, I finally did a restore of my backup. I'm now on RR rom. Anyone else have this happen with the new update? I'm using the xt1254 on Verizon.

Is there anything else that could have caused it? I didn't install any other apps than normal that I can think of - - xposed, govtuner, updated K. A. and kernel. And an updated theme using Arcus and moelles' pitch-black dirty unicorn theme.

That's pretty much it.
[Moto Maxx Android Development] rkoonts4:
I didn't experience that on yesterday's update, but I did have it happen to me on the 8-03 release. The release had actually run fine for about 3 days, then the crash. Rebooting did nothing. I dropped back to my backup of the 7-28 release and then reflashed the 8-03 release and have not experienced it again.

Other apps I install are govtuner, KA and kernel.

On another note, I'm starting to experience a lack of responsiveness with the power button. It doesn't happen often, but it is increasing. Don't know if that is rom related or just the power button wearing out.
[Moto Maxx Android Development] gimpy1:
I had just backed Mokee rom up, but instead restored my RR rom. I will use it for a couple of days, then reinstall Mokee. RR just came out with an update. I will update and use it for a bit. Hopefully, the problem won't be there on my backup. ??
[Moto Maxx Android Development] gimpy1:
I've been busy with Mokee today. I did a restore of the version previous to the one with the system ui problem. I then saw a new release version and updated to that version. I then updated to the latest nightly version. A lot of updating?. Right now, everything seems to be working fine.

A couple of questions. I have not done a full default wipe in some time (a couple of months?). Should I, if everything seems to be working good?

I would like to get my Mokee boot animation back (The black "pig with the yellow eyes"). A few weeks ago, i somehow put another boot animation on, I'm assuming from one of the themes I have downloaded and used. Nothing I have done, including restoring the default theme brings him back. Amy theme I install brings back the one I currently have, which I don't want. It is a little squiggly blue line with an eye in it, which will sit there a couple of seconds, then propel itself off screen. It looks like an octopus when it does the propelling. Would doing a full default wipe bring him back? If not, what do I need to do to get my Mokee back?

Thx?
[Moto Maxx Android Development] hpbrasil:
Downloads 0? What? :/
[Moto Maxx Android Development] gimpy1:
This morning I did the nightly update using the mkupdater in the Mokee center in settings. I dl'd the update. Once the update download was finished, I received a pop up that asked if I wanted to update. I said yes, update. This is the same with every nightly update. About one out of every three or four nightlies, the updater does not work. That happened this morning. The bootup went into a bootloop where the screen just freezes. To get out of this frozen bootloop screen, I have to do a restore thru twrp.

There is no warning or anything when this happens. I am wondering if it happens only to me or if others go thru this bootloop? As I said before, it seems to happen every three or four nightly updates.

Thx.
[Moto Maxx Android Development] matcatsc:
The sign into network pop-up that appears when you connect to a public wifi came up a few days ago for me telling me I need to sign into Verizon wireless network ( cell) even puts an exclamation point next to the cell network icon, and it will not go away. If I click it it opens up a browser to connectivitycheck.gstatic.com then closes right away with no content and the sign in icon comes right back. Cell network is working. How can I fix this?
[Moto Maxx Android Development] diegolopez10:
Weird... I have the exact same issue, both my WiFi as well as my (T-Mobile) network are prompting to sign in. It started sometime yesterday. I'm on the 8/11 version.
[Moto Maxx Android Development] matcatsc:
I am on 815 myself.
[Moto Maxx Android Development] diegolopez10:
Good, thanks for telling me what version you're on. I was about to update hehe... I've already cleared cache/dalvik, rebooted multiple times, also took out my SIM card... nothing worked. Thankfully, all connectivity is working fine.
[Moto Maxx Android Development] gimpy1:
I started getting this same message yesterday morning. I can't get rid of it, either. I even did a clean default wipe. Everything "seems" to be working fine for now, but I would like it to go away.

But, doing a clean wipe did bring back the original Mokee boot animation that I had lost and could not restore.?
[Moto Maxx Android Development] gimpy1:
I updated to the new nightly this morning and the warnings disappeared.

But, I did lose my ambient display. Haven't figured out how to get it back, yet.
[Moto Maxx Android Development] theatomizer90:
I have the same problem, factory reset, reinstalled 7/5 and nothing works!!! I guess I'll try the newest nightly. Everything Technically works but it is highly annoying as the notification will not go away.

Edit: confirmed, new nightly repairs issue.
[Moto Maxx Android Development] Debuffer:
New stable fix it as well. 05/09 build.
[Moto Maxx Android Development] JFCostta:
Hey guys, is there a way to enable the user detection sensor in this ROM (to keep the screen on while someone is looking at it)?

And, one more thing: pop-up messages in Whatsapp are shown in the first time they arrive, but after a few seconds, the screen gets off and pulse notifications are gone, I have to manually press power button to see them again. Anyone found this same bug?
[Moto Maxx Android Development] gimpy1:
About a week ago I did a clean default install of this Rom (xt1254 on Verizon). When I did I lost the ambient display.I have not been able to get it back. I had the ambient display with the green light notification. Now I have neither. I would like to get them back if possible.

I've gone into settings>gestures and display, but no luck. Any help would be appreciated. I use bhb's updated kernel and KA and the xposed module.

THX
[Moto Maxx Android Development] fgl27:
This ROM is 100% base on Official CM. Some of those are not enable in CM and not here.

User-aware display, Notification light (green led), HDR support, is or disable or never implemented. In marshmallow ROM they only are enable in RR or any ROM that uses my RR device specif trees to Quark.

That Whatsapp may be related to ap permission, check in Setting>Apps, and give the app some permission, if that doesn't help try to check for apps that have notifications access there may be a conflict with one, the only pre-build app that ave is The theme app, if you are using a theme it may be the theme, if not may be another app that has notification access that you use.

Ambient display is fine, you need to enable it in "Display & ligth" then Go back to main settings go to "Gestures" and Disable then enable the Pick/Wave, that disable enable is a small bug of 100% CM base ROM, that bug is not present in RR or RR base device tree.
[Moto Maxx Android Development] JFCostta:
Actually Ambient Display is working fine, except when a WA popup comes, but indeed there's one app granted with notification access: Garmin Connect. I'll try uninstall it and see what happens.

Before Mokee I was testing your RR build, that's why I asked about green light (really helpful to me) but what caught my attention is Mokee frequent OTA updates. As of now MK already has September security patch, RR was in August last time I checked. Any chance RR gets OTA updates too?

And thanks for all your hard work, will surely donate to MK =).