yashsingh1/xdaforums huggingface dataset:
[Moto Maxx Android Development] calsurferpunk:
I had this problem on other ROMs as well until I restored the original manufacturer ROM, set GPS to device only, verified it worked, then flashed the new ROM. You might have to do the same here. I believe it's been a long ongoing bug with CyanogenMod (and probably others).
[Moto Maxx Android Development] tuzky:
pretty thx for the cm13,did it have ambient display?
[Moto Maxx Android Development] frankeegee:
I am downloading this at work right now. It is slow and will take me a couple to download.

While it is dl'g, I have a question about wiping. Do I still need to do a factory reset if I am coming from a marshmallow cm13 RR rom?Baybutchers?

Also, I have not been able to get my GPS to work properly. In your post #17, you referred to original manufacturer rom. Where can I get this rom to set the gps? I do have computerfreek's room saved as a backup if I could use it? I don't have easy access to a computer to do a fastboot.

Thx.
[Moto Maxx Android Development] Debuffer:
Wait, ROM was updated to day 24?
[Moto Maxx Android Development] Debuffer:
This unofficial had. The official hasn't.

Sent by me using my fingers
[Moto Maxx Android Development] mirdones:
This thread should be closed
[Moto Maxx Android Development] calsurferpunk:
Was there anything else this had that the official doesn't? I haven't used the official nightlies yet. I would like to know if there is any performance difference as well.
[Moto Maxx Android Development] Debuffer:
Unofficial used to be more battery friendly than official.

Sent by me using my fingers
[Moto Maxx Android Development] rascal9:
I felt like your experience was smoother im just hoping the nighties keep getting better. I just flashed 4-13
[Moto Maxx Android Development] calsurferpunk:
I'll probably do another build and release it if the official seems to be a little worse. If it's ongoing, perhaps I'll continue this longer after all.
[Moto Maxx Android Development] Debuffer:
Can you make an unofficial Mokee 6.0?

It would be nicely appreciated :)

I'm expecting Mokee MM so much

Sent by me using my fingers
[Moto Maxx Android Development] rascal9:
I would love you long time. Even if you ported nighties and sprinkled in your updates. Saves you the leg work of smaller bugfixes and allows more time to push cool features we request and donate for your beer supply :)
[Moto Maxx Android Development] mirdones:
If there are differences and the developer wants to keep this going, this rom should be rebranded as not CM and proper credit should be given to CM developers where it is due.
[Moto Maxx Android Development] calsurferpunk:
I said this on the very first page. It is still CM 13, just with some tweaks apparently (and additions from baybutcher27s github repo).
[Moto Maxx Android Development] ChazzMatt:
You seem to have an issue with this thread. If you don't like it, why read it?

What do you suggest he add to what he wrote below in the op post? He credits the devs, he states clearly what it is, besides the thread title itself.

It's basically his personal unofficial version of CM13. If you don't like it, you don't have to use it.

Many, many device threads here in XDA have official and "unofficial" builds of branded ROMs. I have two friends with LG G2 phones on which I installed "unofficial" CM Lollipop ROM. It has a few custom tweaks, but it's CM. I installed an "unofficial" CM ROM on my mother-in-law's Nexus 7.

Three years ago when I was on the Nexus 5, I remember one well-known ROM dev group (not CM) made a decision to lock users into a certain configuration -- whereas before they gave people a choice, an option. Suddenly they said, "Our way or nothing." It was their ROM, they had that right... But still, it rubbed a lot of users the wrong way, to change that ROM philosophy so drastically. It was clearly the best AOSP ROM available until then -- and except for that unfortunate decision was still the best ROM. SO, unofficial ROMs then arose -- based on that ROM -- to again give people a CHOICE to configure their devices to meet their needs. ;) Those "unofficial" ROMs clearly stated they were based on that branded AOSP ROM, but detailed the few changes that were made to again give users a CHOICE.

That is what Android is all about -- open source software to let people have control of their devices. It also goes to the heart of XDA, giving people a forum who want to control their devices.

CM is a great ROM. I'm still using CM12.1 on two of my three Quarks.

But if [MENTION=6069596]calsurferpunk[/MENTION] wants to tweak CM13 a little and release it publicly -- as long as he gives credit where it is due, there is nothing wrong with continuing this unofficial build of CM13. He's giving his time, his effort.
[Moto Maxx Android Development] Debuffer:
There's no chance about you doing a Mokee rom, bro?

It's the best rom for maxx on LP and I think everyone would like to try it for MM.

Sent by me using my fingers
[Moto Maxx Android Development] calsurferpunk:
I just posted a new build, synced to the latest repos (some from baybutcher27 github [device, stock kernel], others from CyanogenMod github as in the previous builds). I noticed the size increased as additonal libs are included by default now. This is a good test to see how it compares to the latest official nightly.
[Moto Maxx Android Development] Debuffer:
What features and tweaks you got from butcher at all? Battery tweaks?

Sent by me using my fingers
[Moto Maxx Android Development] calsurferpunk:
It's the same as in the previous builds where I use the device information from his github instead of CyanogenMod. To be honest, I'm not entirely sure of all of the differences (at least how they affect operation). It is possible to see a comparision of his github vs CyanogenMod though. I also always use his latest kernel, so I'm sure most of the tweaks are really in there.
[Moto Maxx Android Development] immadeofpixels27:
Read the OP. He grabbed some code from Ressurection Remix to enable it.
[Moto Maxx Android Development] Debuffer:
[MENTION=6069596]calsurferpunk[/MENTION] are you able to do a Unofficial Mokee MM Version?

Sent by me using my fingers
[Moto Maxx Android Development] ChazzMatt:
Look, you've asked three times in less than 24 hours. Why? If he doesn't want to answer, then the answer is no. ;)

[MENTION=5747496]baybutcher27[/MENTION] is doing Mokee Lollipop in this very forum. Why don't you go ask him to do MM version?
[Moto Maxx Android Development] Debuffer:
The lp Mokee was discontinued, so I don't think he'll make a mm version

Sent by me using my fingers
[Moto Maxx Android Development] calsurferpunk:
LOL. Well I don't mean to be rude, but I just find it odd asking for something that is still actively being done by someone else. I'm really just updating this version of the ROM by picking the github repos that seem to work the best and syncing (in addition to tweaking it to compile sometimes). Getting involved in a full on port is not something I really have time for, especially since I'm not and haven't used it before. I am actively working on a hopefully soon to be released android app in between work and family life as well.

Thanks for helping fill in the "missing space" there ;).
[Moto Maxx Android Development] Nitefire77:
I swear some people can just never be happy. I never request features or for someone to make something, because I'm Thankful for the ROMs and features we do have. I love resurrection remix and bhb27 kernel. I have no complaints and am very very happy with it.

Maybe its just me but I find it disrespectful to be needy and constantly trying to want or demand more. If I was a dev doing an active ROM I'd feel a little bit frustrated and down about it
[Moto Maxx Android Development] calsurferpunk:
I guess it's okay to mention a problem/bug or a feature that would be nice (if active development is happening), but I totally agree. With all of the software I write at work it can be frustrating when I add a new feature/fix something, only to have more requests or complaints. Fortunately the people I work with are grateful every time I make life a little bit easier for them and improve the tools they use.
[Moto Maxx Android Development] Debuffer:
I'm really grateful for your and bhb works, bro.

I just asked you about Mokee because it's a famous rom, nobody is doing it at this moment (and I don't think bhb gonna do because the lp Mokee was discontinued by him and kept being updated only in official website) and it is a cool rom for our device. Sorry for the inconvenience, I didn't mean to be mean.

Sent by me using my fingers
[Moto Maxx Android Development] calsurferpunk:
No worries. I wasn't insulted or anything. I didn't intend for it to sound mean either.
[Moto Maxx Android Development] Andrey G.:
Deleted
[Moto Maxx Android Development] quantum tao:
[MENTION=6069596]calsurferpunk[/MENTION] , maybe you and Skrilax_CZ could work together on CM for quark.

also, does the bhb kernel offer benefits if you just install it but dont mess with any settings? in other words, is the same as stock until you make adjustments in kernel auditor, or is provide improvement right off the bat without tinkering?
[Moto Maxx Android Development] Debuffer:
Bhb configured the kernel to be good at 'stock' configuration. If you want to mess with configurations it'll get better, but you can just install and leave it as it is.

You may use Intelliplug instead of mpdecision, so your phone will not be hot if you don't play.

Sent by me using my fingers
[Moto Maxx Android Development] ChazzMatt:
It has some audio volume options not present in CM kernel.

Also, Westwood Plus is the default TCP algorithm in BHB27 kernel, which I prefer over Android default Cubic.

The I/O scheduluer in BHB27 is BFQ instead of the Android default (Noop, Row? I forget).

He also overclocks the GPU to 800MHz from stock 600 MHz by default.

So, yes it's different settings from CM kernel.

You can then mess with even more settings, if you wish. You use Kernel Aduitor app to adjust the settings. [MENTION=5747496]baybutcher27[/MENTION] even releases a customized version of the app for his kernel.
[Moto Maxx Android Development] Andrey G.:
AFAIK, on the last version BHB returned to stock 600 MHz, other then that you're totally right.
[Moto Maxx Android Development] ChazzMatt:
OK, I missed that because I already set mine for 600MHz. ;) I decided a while back I didn't need overclocking.
[Moto Maxx Android Development] calsurferpunk:
I didn't know if you saw yet, but there is an official Mokee for 6.0 now:

http://download.mokeedev.com/?device=quark
[Moto Maxx Android Development] rascal9:
I actually just seen this. But cant find any real official post with features and what nots. Just bay post on the 5.1.1 ROM
[Moto Maxx Android Development] Debuffer:
I've seem it 17min after it was released. I'm using it with the stock kernel. I gotta wait butcher release the kernel.

Sent by me using my fingers
[Moto Maxx Android Development] eddiemc12:
it works fast and smooth so far,been on it since yesterday and it works perfectly.
[Moto Maxx Android Development] quantum tao:
what is advantage of mokee? other than open source.
[Moto Maxx Android Development] Debuffer:
It's optimized by Mokee. I'd prefer this over cm, to be honest. It's more optimized, has more features but only really needed features. Has lock in memory feature (in recents) and some other stuffs.

I'm just waiting for bhb Kernel and it'll be perfect.

Sent by me using my fingers
[Moto Maxx Android Development] calsurferpunk:
Synced to repos as of 4/23/16.
[Moto Maxx Android Development] calsurferpunk:
Repos synced again as of 4/25/16. The last build (2016-04-23) seemed to have broken video recording. It is fixed in this update.
[Moto Maxx Android Development] Kaus Reche:
Are you using the BHB for Marshmallow, or Lollipop?

I'm gonna use this kernel on my Moto Maxx

att
[Moto Maxx Android Development] calsurferpunk:
Since this is a marshmallow (6.0.1) ROM, you'd want to flash the marshmallow kernel. You can get to it directly with the link on the first post, which is:

https://www.androidfilehost.com/?fid=4996500813288309056
[Moto Maxx Android Development] deepss1:
Running so smooth..
[Moto Maxx Android Development] tuzky:
Hey,calsurferpunk.I've used the apr.25TH rom for 2days,it's smooth and battery really good.

But how to active the pick-up gesture? I enable the ambient display in the settings and Pick-up/wave in the Gestures,but still not work...

--------

sorry,i forget to reboot.....thx for the rom,it's really nice
[Moto Maxx Android Development] calsurferpunk:
Repos synced again as of 5/5/16. This includes the latest Google monthly security updates.
[Moto Maxx Android Development] deepss1:
How to select weather service provider ?
[Moto Maxx Android Development] calsurferpunk:
It looks like these are separate downloads from the google play store at the moment. I found 2 that can supposedly be used:

Weather Underground:

https://play.google.com/store/apps/details?id=org.cyanogenmod.wundergroundcmweatherprovider

Yahoo:

https://play.google.com/store/apps/details?id=org.cyanogenmod.yahooweatherprovider

Here is also a blog from CyanogenMod about it:

http://www.cyanogenmod.org/blog/plug-play-weather
[Moto Maxx Android Development] davecowan:
Best CM 13 Mod for my Droid Turbo that I have tried

[MENTION=6069596]calsurferpunk[/MENTION], thanks so much for this ROM. Love it, smooth, very stable. Best I've tried to date!
[Moto Maxx Android Development] calsurferpunk:
I just synced again. One of the more noticeable changes is that finding a weather plugin source is much easier now.
[Moto Maxx Android Development] davecowan:
Anyone else getting an "unfortunately AudioFX has stopped working" message while in any apps or games? It doesn't crash the app but it keeps popping up and I have to click okay to continue.

Thanks
[Moto Maxx Android Development] calsurferpunk:
I think this has happened over in the resurrection remix rom forum as well. I think it's just a bug with Cyanogenmod 13 at the moment. I haven't actually seen it though as I think this is one of the apps I keep from starting/running at boot
[Moto Maxx Android Development] davecowan:
That's a great idea. I'll block it as well. Thanks again.
[Moto Maxx Android Development] ChazzMatt:
does this ROM have the Google Store Moto app download permissions like Resurrection Remix?
[Moto Maxx Android Development] Andrey G.:
Yes, tested the ROM with normally downloaded from GP MotoCamera and MotoGallery..
[Moto Maxx Android Development] kenennaoyeka:
Hello all, just came to this rom from RR, i have only been on it for about an hour but i love it more than RR. I was wondering, can i take the Nightly CM Updates in 'About'? I dont want to have to wipe my phone all over.
[Moto Maxx Android Development] RLShiftyDoggit:
Anyone else's Facebook app being stupid after the update last night all it does is open freeze and close
[Moto Maxx Android Development] quantum tao:
What about verizon stuff?
[Moto Maxx Android Development] calsurferpunk:
You might be able to, but it is definitely not the same ROM. That would just be the normal stock CyanogenMod 13. Worst case you could just make a backup, try what you wish, go back if it didn't end up working well.
[Moto Maxx Android Development] ChazzMatt:
Not speaking for the dev, but it's a Motorola Quark ROM which is sold by many, many various carriers worldwide. If the dev included one carrier's apps permissions he would have to include them all.

Verizon's Quark, the Droid Turbo XT1254 is just one of the Quarks. The Droid Turbo wasn't even the only Quark sold in the U.S. -- there's also the U.S. Moto Maxx XT1250. The Droid Turbo device was NOT exclusive to Verizon in any way. Just the "Droid" name -- which Verizon licenses -- not the device. Many other carriers in the U.S. sold that SAME Quark phone which Verizon calls the "Droid Turbo". :rolleyes: The U.S. Moto Maxx XT1250 was sold by at least a dozen regional CDMA/LTE carriers -- which all probably have apps for their customers. It's identical to the Droid Turbo XT1254 in every way, same CDMA/LTE bands, including the same FCC ID (but with bootloader that can be unlocked via Motorola website).

The "international" Moto Maxx XT1225 and Moto Turbo XT1225 was sold by various carriers in Mexico, Brazil, Chile, Puerto Rico, India -- as well as straight from China Motorola factory. Bet a lot of those carriers have apps!

Why would we want Verizon apps on non-Verizon phones? I know I don't want any Verizon crap on my phone. ; ) Two of my XT1225 were sold by Claro carrier in Puerto Rico -- and I don't even want Claro stuff on my phone! (I use AT&T). My third is from Mexico.

Whereas all the Quarks are made by Motorola, so of course Moto apps are fine. I like the Moto camera.
[Moto Maxx Android Development] quantum tao:
Because this developer is on Verizon network and he originally made this rom for himself. So it is logical to think he might have added verizon permissions. BB put them in RR and he is not even on verizon.
[Moto Maxx Android Development] davecowan:
Agreed Chazz. I like the Moto camera too. It is so nice not having the Verizon crap anymore either since their customer service pissed me off and I took my Droid Turbo and business elsewhere :o
[Moto Maxx Android Development] calsurferpunk:
I was just thinking you meant if they work with this ROM the way I read that. I think they do and it should be the same as with RR but I haven't tried. I just looked on the play store and it says they can be installed though.
[Moto Maxx Android Development] quantum tao:
Cool, i might give it this rom a try, i dont really need all the extra RR stuff.
[Moto Maxx Android Development] Astrobrewer:
I just installed this ROM today. I have used CM ROMs in the past and have always liked them. I've been on stock ROMs since I've had the turbo and finally got inspired to change. So far everything works well. I do miss the chop-chop light on gesture. I took the dogs for a walk this evening and ran across a snake on the sidewalk (really!). It would have been really nice to be able to turn on the light quickly, but by the time I dragged the dogs away from the snake and fumbled with the phone the snake was long gone. I hope chop-chop comes back.

I have been having issues with device encryption. I had encrypted the data partition while still on the stock ROM, and of course flashing CM13 left it encrypted. I got the phone all set up when I discovered that the GPS receiver wasn't working. Searching the thread I found a link to a flash-able radio image to fix that, and when I rebooted to TWRP it prompted me for a password to decrypt the data partition! Unfortunately it didn't like my PIN no matter how many times I entered it. I don't know if there's something about entering a numerical PIN on the qwerty keyboard, but it had worked earlier in the day before it stopped prompting for passwords. After a bunch of tries and reboots I gave up and downloaded a fastboot flashable version of the same. I've spent most of the day screwing around with this phone already and I'm not going to reformat the data partition again today for sure! Maybe it just needs a good night's sleep.

Anyway, aside from that this ROM seems great! I forgot how much I had missed CM over the past months.
[Moto Maxx Android Development] ChazzMatt:
[MENTION=5747496]baybutcher27[/MENTION] lives in Brazil and he hasn't added Brazil carrier stuff. :) Yet, he added Verizon stuff? :confused: That's fine, but is a little strange...

Sure, and I said I wasn't speaking for you [MENTION=6069596]calsurferpunk[/MENTION]. It's just soon I will be switching to a Marshmallow ROM and if this ROM had Verizon-specific stuff installed or would nag me to install Verizon-specific stuff when I visited the Play Store, that would not be cool.

However, if it's just permissions to allow Verizon subscribers to install Verizon apps, and the users want that, OK. But what happens when people in other countries want all their carriers' added? (Vivo, TIM, Claro, etc -- I haven't even listed all the regional U.S. carriers that sold the XT1250.) :p Well, it is YOUR ROM, so you can say no to other carriers (and you do use U.S. Verizon yourself).
[Moto Maxx Android Development] calsurferpunk:
No problem, I understand. I appreciate you trying to prevent lots of requests at the same time. I wouldn't be adding anything anyhow since I'm just taking everything straight from the github repos without any modification.
[Moto Maxx Android Development] calsurferpunk:
I just posted a new build for 5/23/16.

*redoing - put wrong time in build for some reason*
[Moto Maxx Android Development] deepss1:
That's why I saw the wrong build date in newer build.
[Moto Maxx Android Development] calsurferpunk:
It's fixed now :). I had to do a total clean and start over. Some kind of strange bug. It technically worked fine, but it bothered me and probably would have bothered others more too.
[Moto Maxx Android Development] RLShiftyDoggit:
6.0 will not be rooted for quite some time BL unlock wont work at that point now Motorola won't know unless you have to send it in and they look installing will not relock the bootloader as long as its not official 6.0 OTA from Motorola and I gotta ask is your warranty actually with moto or verizon BC I believe you have to go to motos website and actually buy a warranty plan and pay monthly now w that being said If your warranty was with Verizon I believe its only a one year warranty

If you want to stay stock LP you can or you can run Computerfreak's stock based ROM

If you want custom ROMs 5.1/6.0 you have

Cyanogen Mod

Resurrection Remix

Personally I'm running RR 6.0.1 w a custom kernel also CM can run custom kernels too if you didn't know.

But I'd say do it if your warranty is up w Verizon and you don't have a warranty plan w moto what do you have to lose

Hope this helps
[Moto Maxx Android Development] iiWoodstocK:
He has the Indian Moto Turbo XT1225, so bootloader unlock will be the official one from Motorola.
[Moto Maxx Android Development] RLShiftyDoggit:
Oh dude then he's golden
[Moto Maxx Android Development] iiWoodstocK:
Yep. And I believe he can even flash the Brazilian Moto Maxx XT1225 6.0.1 Marshmallow soak onto his device without encountering any issues. Not 100% on that though, but I'm pretty sure.
[Moto Maxx Android Development] calsurferpunk:
I just updated the build again. I noticed that there used to be a problem with the battery indicator circle icon being incorrect, but it is now fixed in this build.
[Moto Maxx Android Development] Astrobrewer:
I've been running this for a couple weeks now and it's all good. Very happy with everything except for one thing. It looks like there is no mobile data while the phone is in use. The Turbo had this feature with KitKat, but when Lollipop OTA came out it was fixed and I got used to being able to use data while on a phone call. Is there a work around (besides using wifi) for this? Thanks.
[Moto Maxx Android Development] mrkhigh:
The turbo only has data during calls on stock based ROMs.

Until a Dev spends some SERIOUS time on this. We will have to live without it or use a stock based ROM.
[Moto Maxx Android Development] ChazzMatt:
Droid Turbo, not just "Turbo".

My Turbo has data while calling. But then I have a Moto Turbo. ;)

You guys need to learn to stop saying just "Turbo". There's TWO Quarks called Turbo. :silly:

Moto Turbo XT1225 (in Latin America also called the Moto Maxx XT1225)

Droid Turbo XT1254

And the Moto Turbo is discussed in this same thread too:
[Moto Maxx Android Development] Astrobrewer:
Interesting. Let me see if I understand this.

My XT1254 can run the same Quark ROMs as the XT1225. XT1254 doesn't have data while calling, and XT1225 does have data while calling running the same ROM. So that implies that the ROM isn't the reason that there's no data while calling. But with a stock-based ROM the XT1254 does have data while calling, so that says that it is the ROM that makes the difference. What's going on?

:confused: