yashsingh1/xdaforums huggingface dataset:
[Moto Maxx Android Development] fgl27:
Yes I see you understand everything, my request was only about credits not because some one without any request was releasing my unfinished work full of bugs something that I was just testing, yes is all about the credits not anything else, I (bhb27) I'm just a big jerk, going all over xda complain (*****ing) about the great work others devs are doing releasing my unfineshed work without my Knowledge..

[MENTION=8166511]Dev Marsh[/MENTION] your tester friend Marky here tell all xda that wasn't just a few ROM like I thought, you have be using others project on yours for months with any care to informe the developer responsible, not cool man, but as I discovery it by my self and after you did the proper correction is all cool, but Marky here should not be telling everyone things like that they are not OK.

and Marky there is anything else we should know about this?
[Moto Maxx Android Development] fgl27:
I know that in a way I'm spamming, but I just like to respond when some one uses my name, post or comment I did on xda without the proper context and without understand what the point was about. not credit Marky really not credits.
[Moto Maxx Android Development] Marky__Mark:
Yes. I do want to point out that i do recall him crediting you when this project started. Thats how i think i recalled that he was even using your Kernel. Maybe it was the transition from 7.1.1 to 7.1.2. that the credit to you was missed or maybe a copy and paste error in the new OP. I dont know.

---------- Post added at 10:31 AM ---------- Previous post was at 10:29 AM ----------

And thanks for asking. I also want to point out im not his tester. Testing windows software is my occupation as well as programming. So I do know how to test. That was my point.
[Moto Maxx Android Development] fgl27:
Keep on keep it on about credits, you really get my point is all about the credits noting else... thank you.
[Moto Maxx Android Development] ChazzMatt:
No, he was crediting the stock kernel, or should have been. [MENTION=5747496]bhb27[/MENTION] codes that also. Even then there was some confusion and some users thought it was dev_marsh kernel.

I was here from the beginning.

https://xdaforums.com/showthread.php?p=71849326

https://xdaforums.com/showthread.php?p=71849730

Dev Marsh never clarified he was using [MENTION=5747496]bhb27[/MENTION] custom kernel and not the stock kernel (also coded by [MENTION=5747496]bhb27[/MENTION]).

All he said was for people to stop calling it his kernel. In his OTHER ROM, he said he used stock kernel:

If you don't understand that, he's saying he is using [MENTION=5747496]bhb27[/MENTION] coded STOCK CM/LOS kernel, specifically NOT using [MENTION=5747496]bhb27[/MENTION] custom kernel. Yet, in THIS ROM, somehow he started using [MENTION=2071726]BBH[/MENTION]27 standalone custom kernel?

AND I even helped you back then. So, don't continue with the "you're butting in" crap. OK?

https://xdaforums.com/showthread.php?p=72141740
[Moto Maxx Android Development] Marky__Mark:
As far as i can see, you're being a nescience. bhb27 and i got it straightened out. Thanks.
[Moto Maxx Android Development] Romullo Sousa:
[MENTION=6362361]Marky__Mark[/MENTION]What was the problem brother? Personally if you can stop the one regarding the problem of my use regarding the use of Felipe kernel would be cool!

As in the previous messages the [MENTION=5747496]bhb27[/MENTION] my notified regarding the inappropriate use of your kernel .. and indeed I was wrong! I used his kernel where he works and launches his zip files separately .. that is, I used something that he does not even use in his ROMs and for that mistake I apologized to him because I was really wrong! So do not generate a contrite because of this .. I credit Felipe in previous versions of ROm before changing this Thread in xda ... I just do not have but this device .. I just keep this updated ROM .. a used device tree Is credited in the description to [MENTION=5747496]bhb27[/MENTION] and the kernel used in this version is LineageOS and Felipe is also the main maintainer of it in the Lineage organization!

So just to summarize I did something wrong but I already corrected .. do not proceed with it!
[Moto Maxx Android Development] Romullo Sousa:
And regarding the kernel's use of [MENTION=5747496]bhb27[/MENTION] to credit me this is stupid! I have not renamed kermel to boast me ... if you are an experienced user you will see the user in the description with the kernel information in On the Phone .. will not see my user la! enlightened?
[Moto Maxx Android Development] Marky__Mark:
Zero problems, man. Running 8/9 and loving it. Excellent rom.
[Moto Maxx Android Development] GeekyTanuj:
time relation!

So,any approx specific ETA for that work ,since I can't wait for my quark to be firmware-e-cally light and better in gaming since in any custom ROMs till date,the graphic intensive games like asphalt extreme struggle badly since they stutter ip too much!
[Moto Maxx Android Development] Hlcpereira:
From my part, no. Maybe next to December/January...
[Moto Maxx Android Development] K3n H1mur4:
#1 rule in XDA: don't ask for ETAs. The devs here are working for free (or, at most, for donations) and we have no right to hurry them.
[Moto Maxx Android Development] LifeAsADroid:
I have read the posts already, and feel that it was my doing in the first place (asking for install help in the kernel thread) that brought all of this to light and started the 2-page war of words that ensued (pages 24-25 I believe in this thread?). So to all involved... sorry?

Anyways my main concern was the second part of my post where I was asking if anyone else is having issues with the screen timeout feature. Mine doesn't ever time out and stays on forever unless I manually press the power button to shut the screen off.
[Moto Maxx Android Development] ChazzMatt:
Sometimes that happens to me and I thought it was due to this: I keep User Aware feature on. I know it can be glitchy and stay on too long, but I like not having my screen time out while I'm looking at the display.

No that's probably not a feature of this ROM, but I am using [MENTION=5747496]bhb27[/MENTION] custom kernel again and I notice sometimes (not always) my display stays on a long time. So I didn't worry about it because I thought it was the User Aware option on the ROM I'm runny just being too hyper.

And if you're asking about the [MENTION=5747496]bhb27[/MENTION] custom kernel, then the place to ask would be to other users in the kernel thread...
[Moto Maxx Android Development] LifeAsADroid:
It is a feature on this ROM, and I don't have it on, so that's not the cause.

I am asking people that are using this ROM specifically if they have noticed any similar behavior (thus why I am asking about an issue I am having in this ROM thread). I'm trying to see if:

- it is just the way the ROM is (or the associated kernel with the ROM version installed)

- or if it could be a setting I have checked/unchecked that is causing it if others report not having trouble with this feature (and any discoveries users of this ROM have found that would cause the screen to stay on and not timeout).
[Moto Maxx Android Development] fgl27:
I saw a app doing that once, es file explorer, really bad app was good but they should just have keep the file thing separated from they bad work that they shove in the explorer...

set display to the lowest timeout (to be quickly on the test), kill the app and see what happens, if you don't use it (es file) kill/stop it app running (developers > running services) one by one until you find the one to blame, using the kill back key function may be better, to use you need to just open the offender app and hold back to kill and wait for the time out.
[Moto Maxx Android Development] LifeAsADroid:
Now this is the kind of A+ answer I was looking for. Turns out it was an app (Blackr) that was keeping the screen on. Thanks for the advice. All fixed now.
[Moto Maxx Android Development] fgl27:
theoretically oreo have a tool to prevent those for ever wakelocks, reading build warnings and reports also help, I find fascinating that some app do that, because build logs/reports really point that problem and how to prevent it.
[Moto Maxx Android Development] Bruno Wagner:
The last update does not turn on the screen with the Back Button :(
[Moto Maxx Android Development] SWEVEX:
When listening music equalizer has stopped
[Moto Maxx Android Development] Hlcpereira:
I don't know if it's time to say that or no, but I mean it's.

As far as you know guys [MENTION=8166511]Dev Marsh[/MENTION] lost his Quark some time ago. Talking with me, we decided that he's not going to provide support of AEX for us and any other support for Quarks. But I'll continue to provide AEX for us and maybe I'll get another projects for us. I don't know if he'll do an update of AEX 4.6 (already confirmed with September security patch), but I think I'll do this update. I'll publish here, so you don't have to search in Development forum to find another thread, but yes I'll create another thread. I won't stop provide support of ViperOS.

So that's it. Keep an eye! :)

#BeExtended
[Moto Maxx Android Development] Marky__Mark:
Thank you!
[Moto Maxx Android Development] otaviobravim:
Thanks a lot!

I would like to thanks the developers, in special Dev Marsh and HLCpereira, its such a GOOD ROM. I had some trouble in the 6.01 on MMaxx and all of them were solved. Except for one. I lost all colors in the bold fonts (back in MMalllow) and these upgrade did not solve this problem. I remain with, for example, whatsapp groups, all people in the same bold white font... When upgrading, I have done the basic clean (system, cache, Dalvik, except from data) and the problem remained. Does anybody think I should clean the data to solve the problem? I can't place pics because I, even though been here for a while, don't post anything because I usually find my answers... Thanks!
[Moto Maxx Android Development] Hlcpereira:
ROM Update!

Recommended Clean Install!​

Download link

Changelog

:

AospExtended:

Merge September security patch

Merge latest AOSP Tag

Merge latest CAF Tag in respective repos

New AospExtended bootanimation

Fixed adaptable storage

Fix memory leaks

Add support for more boost frameworks from Paranoid Android

Improve fingerprint scanner performance

Allow user to add or remove QS tiles with one click

DUI: Support for left landscape navbar

DUI: Migrate from broadcasts to API for some action handling

Fix few NPEs

Update all translations

Update AEX Papers

Update all pre-built packages

Performance enhancements and bug fixes

Device specific:

Changed Maintainer. [MENTION=8166511]Dev Marsh[/MENTION] to [MENTION=7838323]Hlcpereira[/MENTION]

Included TurboToast App

Found a bug?

:

Check if you make a clean install (wiping Cache, Data, Dalvik/ART Cache and System). If you did a "dirty flash" I won't give you a solution. If you made a clean install, report it, and don't forget the logcat.
[Moto Maxx Android Development] Marky__Mark:
Dirty flash was fine. Running smooth. Thanks!
[Moto Maxx Android Development] ChazzMatt:
Quark doesn't have a fingerprint scanner.
[Moto Maxx Android Development] Mario0550mg:
It refers to the AospExtended base, so other devs that port the ROM to their devices could use the fingerprint
[Moto Maxx Android Development] ChazzMatt:
I know where he got it from -- he copied and pasted from some universal ROM group document --- but if posted here it should be edited to remove features not on this phone. Otherwise, it'smisleading.

Similar to how previous dev for this ROM also copied and pasted ROM "features" from other devices like FM radio our phones do not have, and we had to keep telling him to please remove them. (He was doing ROMs for other devices, too.)

Our phone doesn't have FM radio or fingerprint sensor and any reference to such in ROM description for Quarks is misleading.

The dev could put a disclaimer statement saying this change log does not apply to THIS phone... But then what's the point of posting the change log in the thread? ;) So, simpler to remove the part that doesn't fit? That way there's no confusion.

I'm not starting an argument but it seems a change log actually posted in a ROM thread cannot just be copy and paste list. It specifically says ROM UPDATE, then has the change log. It's supposed to be the change log for this ROM for this phone, not the ROM for a Galaxy S8 or something.
[Moto Maxx Android Development] Hlcpereira:
That changelog of AEX it's for all devices, that had fingerprint sensor or not, that had FM Radio or not. I agree, that for us it's FM Radio and fingerprint sensor doesn't matter, mainly because the Quarks didn't have that, but a universal changelog of the ROM it's a universal changelog of the ROM, a device specific changelog it's a device specific changelog.

[EDIT] To proof my point look here in the Moto G3 thread of AEX
[Moto Maxx Android Development] Marky__Mark:
Doo you think people arent smart enough to figure this out? This happens in all offical changelog posts from what ive seen in all devices.
[Moto Maxx Android Development] newbe1droidx:
OK every time I try AEX I can't get past verify google account no matter what email I use, any way to bypass this?
[Moto Maxx Android Development] gimpy1:
Don't add gapps.
[Moto Maxx Android Development] ChazzMatt:
Change log posted in thread should still be for that ROM, that device unless there's a disclaimer.

Not for features, hardware not present in the ROM or on the phone.

---------- Post added at 06:00 PM ---------- Previous post was at 05:57 PM ----------

It seems if a list is posted in a device thread it should not be the changelog for all devices, it should be the changelog for this device. It should not list hardware, features this ROM does not have.

If you write a disclaimer saying this is not the real changelog for this device, then people will know to ignore it. A disclaimer saying this is a universal list that doesn't apply to this phone?

Or if you posted a link to the ROM group site, which would take users AWAY from this device thread, then if they saw the "universal" list they would not think it has to apply to QUARK.

I'm just trying to help. It's your decision, you're the maintainer now. I'm just pointing out how it can be confusing to list features and hardware our phone does not have and this ROM does not have.
[Moto Maxx Android Development] Marky__Mark:
He did. Did you not see the section called "Device Specific"?
[Moto Maxx Android Development] ChazzMatt:
Device specific: this phone doesn't have a fingerprint sensor? ;)

I'm not saying anything else, I've made the point it needs to be more accurate. I'm merely trying to help.
[Moto Maxx Android Development] Marky__Mark:
You're not helping anyone. When you installl the rom, then you can *****. Have you used this rom yet even once?
[Moto Maxx Android Development] Hlcpereira:
I know what you're talking about Chazz. I'll take look to found a half term in what we two want. ;)

Hey, let's calm down, shall we?!

I don't want to have a crap here or anything like that. Especially because I think everyone here is mature enough to not need to scold anyone.
[Moto Maxx Android Development] Marky__Mark:
I apologize. That was a little harsh. Just thought it was an odd request for something ive seen many maintainers do for an official build as what you did was more of the norm. No doubt we dont have a fingerprint. But im sure its in the code, unless you specifically removed it. So if thats the case, technically the changelog is correct.
[Moto Maxx Android Development] lRagde:
I install the ROM again but I have a question, where can I find or configure AppOps?
[Moto Maxx Android Development] gimpy1:
App ops is in the main settings?
[Moto Maxx Android Development] Hlcpereira:
Well it's not a norm, it's only a way to show the users all the changes the ROM have (of course... :silly: ), but not all the changes can be "valid" for some devices. The maintaners have the option to included some changes for his devices besides the ROM changelog, or only included in the ROM changelog the changes that affect only the device and the device changes. Or the dev doesn't matter about it and didn't publish the changelog.
[Moto Maxx Android Development] ChazzMatt:
I remember when our former CM dev REMOVED the code from our Quark CM for barometric pressure, because our Quark phones do not have a barometer. It was in there for several months, probably because it's part of CM for phones that did have it, but he removed it when he saw our phones did not in fact have that.

1) our phones couldn't use it

2) he felt not accurate to imply in even small way it did

3) less code means smaller ROM, less chances of bugs

You get the idea.

I didn't mean to start an argument, I was merely suggesting to remove that finger print sensor statement as it does not apply to our phones.

It seems there's no need to post a "universal" change log inside specific device thread, if there's features/hardware listed the do not apply to that device. What good does a universal changelog do if that feature isn't even available for use?

[*]Improved the time machine functionality so you can go back in days not just years.

Oh, sorry doesn't apply to any current phones. But some guy showed up with a 2037 Samsung and added the code to help HIS phone... ;)

Plus, some devs actually remove features from ROMs -- on purpose, not because the hardware isn't there (like FM radio or finger print sensor), but just to make the ROM simpler. In the cases, again posting universal changelog in device thread would be strange because it would be listing stuff the dev KNOWS that ROM no longer has if people installed it.

A "universal" changelog might be posted on a ROM group site. Maybe a link to such? That way users will be taken away from the device thread, so there's no confusion.

Or just remove statements that don't apply to our phone. The maintainer surely knows what does and does not apply? Why should it be up to the users to decide what is true and what is false?

With the FM radio stuff I had to PROVE to Dev Marsh our phones didn't have that hardware feature before it got removed. It was listed in the op as a ROM feature! How does a ROM magically add hardware? Oh, if you install this ROM you'll have an FM RADIO on your phone. Then, he accidentally added it back when he recreated the thread, when he changed his user name.

Some users actually thought he had somehow enabled the FM radio circuitry. And I had to show It was physically impossible or at least not very probable.
[Moto Maxx Android Development] Hlcpereira:
New Thread of AEX for Quarks

How are you guys? :)

I have open the new thread of AEX for Quarks so it's just to share the link of the new one.

[ROM][7.1.2_r29][OFFICIAL] AEX ROM V4.6 [OMS/DUI][Quarks][2017/10/17]
[Moto Maxx Android Development] lucasfxd:
hey guys! is moto display or something similar working on this rom? (proximity sensor for showing the clock and notifications on screen)
[Moto Maxx Android Development] ChazzMatt:
Yes, if you turn it on. It's Quark Ambient Display (all Quark ROMs have it) -- and you should use the thread quoted above. This one is now dead.
[Moto Maxx Android Development] lRagde:
Clean installation of version 3.3 to 4.0
[Moto Maxx Android Development] Hlcpereira:
Only a issue with dialer. I switched it over the Google dialer. Everything ok.
[Moto Maxx Android Development] ceelos218:
[MENTION=8166511]Dev Marsh[/MENTION]

Can you add an option for 3g networks under suspend action? I'm on verizon and 2g doesn't work for me. Thanks.
[Moto Maxx Android Development] ChazzMatt:
Yeah, it's probably trying to connect to 2G GSM , BUT with Verizon (CDMA-based network) it should be 1xRTT. Even EVDO (a CDMA technology) is considered "3G". :p 1xRTT is 2G for CMDA-base networks, and Verizon does still have that 2G "1XRTT" network -- but plans to shut down its 2G CDMA 1X network by 31 December 2019:

2G shutdown around the world

https://en.wikipedia.org/wiki/2G#2G_shutdown.

If you read that section, AT&T already shut down their 2G network end of December 2016, and other carriers around the world are doing the same. So, defaulting to "2G" for screen off is NOT a smart choice for many users.
[Moto Maxx Android Development] Hlcpereira:
Split screen issue. Fixed editing .prop as you can see in the screenshot
[Moto Maxx Android Development] mubaidr:
What does it do, any information?
[Moto Maxx Android Development] Hlcpereira:
App BuildProp Editor on Play Store

Link: https://play.google.com/store/apps/details?id=com.jrummy.apps.build.prop.editor

Search for the line "persist.hwc.mdpcomp.enable" and change "True" for "False" and that's it.
[Moto Maxx Android Development] ChazzMatt:
SPLIT SCREEN ISSUE - AGAIN

Yes, it was fixed a long time ago by devs in QUARK Nougat custom ROMs.

The dev can fix it by doing what [MENTION=5747496]bhb27[/MENTION] and others did to fix it. Split screen issue on Quark Nougat custom ROMs (RR 7.X, crDroid, AOKP) was fixed like 2 months ago.

5th February 2017, 09:25 AM

All subsequent ROM builds then already had that change.

Yes, that was the fix. Devs like [MENTION=5747496]bhb27[/MENTION] (RR 7.X, crDroid 7.x) and [MENTION=7237874]NepoRood[/MENTION] (AOKP 7.x) then put it into their builds so users wouldn't manually have to do it.

Note that while the Play Store Build Prop Editor is great, there's also a Build Prop Editor already included in [MENTION=5747496]bhb27[/MENTION]'s

Kernel Adiutor app.

That is what [MENTION=5747496]bhb27[/MENTION] is referencing whe he says "KA app Build prop editor". I use that Kernel Adiutor app to control functions of even stock kernel included in RR 6.X, even though I am not using [MENTION=5747496]bhb27[/MENTION]'s custom kernel.
[Moto Maxx Android Development] lRagde:
Thanks for the information now I will change the build prop!
[Moto Maxx Android Development] Romullo Sousa:
thank you friend
[Moto Maxx Android Development] Romullo Sousa:
I'll try to fix these bugs in today's update!
[Moto Maxx Android Development] luccasfr:
Please, try to fix the problem on loading video thumbnails on gallery.

This problem is slowing the gallery, the whatsapp video sharing, and everything that need to access the media, specifically the videos.
[Moto Maxx Android Development] Hlcpereira:
Try another gallery. I'm using QuickPic. I never use the stock gallery of custom ROMs
[Moto Maxx Android Development] luccasfr:
I've tried, same problem
[Moto Maxx Android Development] Eduardohanso:
I'm noticing that when I'm watching YouTube on the split screen mode, everytime I touch the screen - to scroll the app on the other window for example - the video playing on the YouTube window will stutter or even freeze completely until I take my finger of the screen, then it will resume playing. The audio will keep playing ok even when the video is stuttering.

I did a clean install. I'm not underclocking my phone through Kernel Adiutor or anything like that.

Is anybody else having this issue? Great rom by the way, I'm loving the battery life. Thanks for any help.
[Moto Maxx Android Development] Hlcpereira:
Here the Build Prop Editor of KA not works so I've downloaded the one on Play Store to fix.
[Moto Maxx Android Development] reinamesa:
Dev Marsh, great ROM!

I dont know if is a bug or some configuration, but when my phone is ringing the screen stays off, only if i press the power button it lights on

Thanks in advance

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

After trying a clean installation the problem was solved, all wipes of TWRP including format data
[Moto Maxx Android Development] Super_Commando:
Hi, I've recently installed this rom. Everything seems good except that I'm unable to send videos in WhatsApp. I've attached a screenshot of the error. Please help.
[Moto Maxx Android Development] Scrluiz:
guys, split screen problem = do not flash Kernel BHB's BHB27! It may cause instability! trust me, I f**ked up myself when I flashed another kernel! :( pls guys use Dev Marsh's original kernel! cya :)