yashsingh1/xdaforums huggingface dataset:
[Moto Maxx Android Development] calsurferpunk:
Hi all. I realized it had been a while since I last did an update, so here's a new build:

https://androidfilehost.com/?fid=1322778262903995736

I'll probably make another in the next couple weeks in order to get security updates for September, but this will at least provide some important updates in the meantime.
[Moto Maxx Android Development] EVNS:
Thanks u very much! I really like ur work with LineAge, I only use ur version ROM.

Waiting for news :)
[Moto Maxx Android Development] Melchiori:
Hi, first of all, tks for this great work. I'm having a very strange problem. Sometimes, when I reboot or just turn on the phone it takes MINUTES stopped in the Boot Loader Image, after a while it start the Lineage normally. Is anyone with the same problem? Any sugestion? It is a very anoying bug.
[Moto Maxx Android Development] EVNS:
Aaah I'm too with same problem, freeze in bootloader image after update to lastest.
[Moto Maxx Android Development] EVNS:
Hi again,

Can someone explain me about Magisk Hide problem... my question, after updates Magisk hide keep with problem to keep activated, if u allow it u cant install nothing, get a error to install in play store apps or external... is a problem with Lineage ROM or really with the Magisk?

Where i can ask for solution?

Thank very much!
[Moto Maxx Android Development] kozzney:
Thanks [MENTION=6069596]calsurferpunk[/MENTION] works great for me, appreciate what you do for us few remaining quark owners
[Moto Maxx Android Development] FlavioV:
There's a known issue with Magisk, it seems to affect some Oreo-based roms and only got worse with v17.1. I've seen some reports in the Magisk forums but no proper fix yet.

Thankfully there's an easy workaround: disable Magisk Hide in the manager settings and reboot. Feel free to turn it back on afterwards so you can pass on SafetyNet, but remember to turn it off before rebooting again.

If your Magisk Manager doesn't work or you can't install/update it due to this bug, you'll have to uninstall Magisk and start all over. Download the latest files from the official thread and do this:

1. Reboot into TWRP and flash the uninstaller;

2. Reboot into system. You can install apps now;

3. Install Magisk Manager;

4. Reboot into recovery and install Magisk;

5. (optional) If you use a custom kernel, install it now;

6. Reboot into system.

Now Magisk is properly installed and up to date, and you should be able to access its settings to control Magisk Hide. The only downside is that you'll have to reinstall any modules you use.

As for SafetyNet itself, I can pass out of the box using the latest Magisk and BHB27 kernel, nothing else needed. If you still have trouble with SafetyNet try the MagiskHide Props Config module.
[Moto Maxx Android Development] imcensored1:
[MENTION=6069596]calsurferpunk[/MENTION] I've been running 9.15

I've noticed that once I drop below 60 percent, the battery drains extremely fast.

I also screwed something up, I rebooted my phone one night, and ever since my phone always boots straight in to twrp. I have to reboot to bootloader from twrp, and then click start to get the OS to load. In addition, if I power down my phone and plug the power cord in, it boots to twrp. I've literally wiped everything and reinstalled trying to fix this, and I can't figure it out.

Anyway, I'm about to flash the latest version of the OS and see how things go.
[Moto Maxx Android Development] dingernalt:
Thanks a lot dude. Works great! :good::good::good::good::good: Amazing work.
[Moto Maxx Android Development] calsurferpunk:
Hi again everyone. I just updated the latest build to include the September security updates:

https://androidfilehost.com/?fid=1322778262904008080
[Moto Maxx Android Development] joshua7727:
just clean installed this, but got the lockscreen problem, i read something bout kernel but i didn't understand, what should i do?
[Moto Maxx Android Development] FlavioV:
What do you mean by lockscreen problem?
[Moto Maxx Android Development] nnjimmy59:
[MENTION=6069596]calsurferpunk[/MENTION]

Just dirty flashed the new update, which I always do, and phone got stuck in loop upon reboot. The lineage animation, I don't know what else to call it, just kept continuing and I had to reboot into recovery and restart a backup.

Any thoughts?

Thanks for all your hard work. The ROM is great!
[Moto Maxx Android Development] joshua7727:
after a restart, the phone starts but the lockscreen background is all black, the battery percentage is at 0%, time is wrong, date is wrong, and it just freezes there
[Moto Maxx Android Development] newbe1droidx:
Better wipe everything but internal storage and clean install with latest gapps, sounds like bad download too, might redownload and clean install, good luck!
[Moto Maxx Android Development] imcensored1:
I installed the latest version Monday, and im running Kernel BHB 9.17. My phone dropped below 60% last night and started doing it's random restart/rapid battery drain thing. Im thinking on one of the reboots it corrupted a file. My phone booted back with all of my settings defaulted back to factory, all my default apps defaulted back to factory. The notification bar is useless, i can drop down and touch like Wifi, Bluetooth, etc, but i cant expand it to all of the options. I also don't see any notifications at any time, it stays blank. My home button stopped working, and my app switcher button stopped working. Both vibrate on long press, but physically don't do anything to the phone. I have to back out of whatever app I'm in to get back to the home screen, and i cant switch between apps.

i've restarted

i've reflashed the os & kernel from recovery.

both did not fix the concern. Is there anything i can do to rectify this without doing a factory reset/full wipe/restore from backup?

EDIT: I went ahead and wiped the device and reloaded. Google is restoring my apps/data right now, phone is working as designed again (except for the issue where recovery is first boot instead of OS, and except the rapid battery drain with crashes at battery levels below 60% level)
[Moto Maxx Android Development] newbe1droidx:
I know it can be a pain to do but try clean install, gapps then dont do a restore of apps do everything new and see what happens. Are you running latest twrp for quark?
[Moto Maxx Android Development] nnjimmy59:
Downloaded update again and reinstalled. Everything's OK now.
[Moto Maxx Android Development] rammx:
The automatic email updates (15 mins) I think is broken.
[Moto Maxx Android Development] bearhawk:
trouble with Gapps

I was using lineage 14.1. I updated TWRP to 3.2.3mod1. I then wiped off everything via TWRP and loaded lineage-15.1-20180917-UNOFFICIAL-quark. I wiped delvik cache/art. I then loaded BHB27-Kernel-Oreo-V9.17 and again wiped delvik/art. I then tried loading open_gapps-arm64-8.1-pico-20180922 but error 64 occurred. I thought maybe it was corrupted so I downloaded it again and still got error 64. I then downloaded and tried to install open_gapps-arm64-8.1-nano-20180922 but I still get error 64.

What am I doing wrong?

Edit: it appears it is the wrong version. I should have downloaded open_gapps-arm-8.1-nano-20180922 (arm not arm64)
[Moto Maxx Android Development] calsurferpunk:
Quick update everyone: I noticed that once bluetooth is turned on it doesn't let you turn if off/on again properly. Fgl27 had a fix for it that I hadn't noticed, so I'm rebuilding the ROM again. As soon as it is done I'll be sure to post it.
[Moto Maxx Android Development] calsurferpunk:
Okay, all updated with everything up to today and the bluetooth fix. Seems like it's always the bluetooth that has an issue when any issue appears :p. I tested it on mine and it was all working well now.

https://androidfilehost.com/?fid=1322778262904011914
[Moto Maxx Android Development] krishna sai:
[IMG="version"]https://dc5.androidfilehost.com/dl/JtYqSDKcbecAZxBMqIVc1g/1538169976/1322778262904014523/Screenshot.png?[/IMG]hi, im currently using stock rom 6.0 anyone help me how to install twrp and this rom
[Moto Maxx Android Development] rammx:
In the last update the flash light don't work

Thank's
[Moto Maxx Android Development] imcensored1:
Question: is there anyway to change the bootloader settings. I think my phone always loading twrp on start up is in the boot loader. To get in to the operation system, I have to reboot from TWRP to bootloader and then click start.
[Moto Maxx Android Development] calsurferpunk:
It's working fine for me and after a dirty flash from the previous version. Perhaps you need to wipe your cache under TWRP and/or do a complete wipe and reinstall? It sounds like it might just be specific to your phone/setup. I'm also using fgl/bhb's 9.17 kernel in case that is different than your setup.
[Moto Maxx Android Development] ChazzMatt:
Some people have that issue when having outdated TWRP installed. Don't ask me why. But installing newest version solves the booting problem. If you already have newest TWRP, then I don't know.
[Moto Maxx Android Development] imcensored1:
I thought this as well, so I installed 3.2.3.0 yesterday, but without any luck.

I've also noticed that if my phone is powered off, and I plug on the charger, it will boot in to TWRP instead of showing me the battery charging screen ?*♂️
[Moto Maxx Android Development] newbe1droidx:
Try modded twrp for quarks bhb27/fgl27 made...
[Moto Maxx Android Development] imcensored1:
I just flashed it, no luck.

I noticed in TWRP that when I flash the recovery image that I have the ability to flash a boot image as well. Is there a separate quark boot image out there that I could flash?
[Moto Maxx Android Development] newbe1droidx:
You'll need to find the correct one for your phone model, you may need to flash complete stock and start all over. By that I mean wipe everything including internal, load stock that has bootloader and radios in it to internal, then flash that. Reboot and set up. Then load custom ROM and gapps to internal, wipe all but internal, I do 3 times just cause I do, then flash ROM and gapps. Hope this helps, find one for your phone model only!
[Moto Maxx Android Development] imcensored1:
This morning my phone crashed, i saw the battery charge screen, and it booted back directly in to the O.S. I guess it took some time for it to correct itself after installing the custom TWRP.

Thanks!!

Now on to my next issue, which i believe is a cross between a possible hardware/battery issue, and the OS/Kernel response to it (as in, seeing the battery is low/dead, and powering down the phone). Below 60%, my phone will randomly shut off. I can prolong it's use by using battery saver mode. I've noticed a couple times that if i immediately try to boot back, i get a dead battery notification before it would start up. Every time the phone shuts off and restarts, i notice about 10% less battery life than before it shut off. My battery is about a year and half old.
[Moto Maxx Android Development] newbe1droidx:
Have you reset battery stats?
[Moto Maxx Android Development] rigues:
Issues with battery and sudden "blackouts"

Hi everyone,

First, thanks for the work on this ROM, my MOTOMAXX feels brand new! I have a newer phone (Blu Vivo 8/Gionee A1), but switched back to the MOTOMAXX because of the fresher OS.

However, I'm having 2 issues with the latest version of this ROM. The first one is Battery Life: I left home with 67% battery at 09:30 AM, and now (12:00 AM) I'm at 24%. With no calls, no Waze/Google Maps, no games, not installing apps or streaming music, no heavy texting. Mostly idle time, with 2 or 3 pictures taken during the period. I'm on a 4G network with strong signal. I even saw a 2% battery drop in 10 minutes with the phone idle in my pocket.

According to the battery stats screen, "Apps" were responsible for 85% of the battery usage since the last full charge, but it does not say which apps. The ROM was freshly installed from a USB OTG Drive and EVERYTHING was formatted on TWRP, including the internal data partition.

The other issue is random "blackouts" during usage. The screen suddenly goes black, stops responding, and the only way to bring the phone back is with a reboot. Anyone saw anything similar? Those issues did not happen in RR 7.1.

Also, I noticed that with a freshly installed system some apps (like TurboToast and BHB27 Kernel Auditor) do no get root permissions, and say that the device is unrooted. Is this intended? The "fix" is to flash the latest SuperSU from recovery.

Regards,
[Moto Maxx Android Development] imcensored1:
I have not. Unfortunately during some of these instances, files become corrupt and I have to wipe and reinstall the system. Sometimes I have to wipe the data too and reinstall all of my apps. So getting the battery to completely drain without destroying the system is hard.

It appears that the comment directly above this one and below the one I quoted states that they are having the exact same issue as me.
[Moto Maxx Android Development] newbe1droidx:
Yes, to reset battery stats boot into bootloader, go to logs, I think one up, hold power button until phone boots, all set. Good luck
[Moto Maxx Android Development] imcensored1:
Done. I'll report back next time my phone drops below 60 %
[Moto Maxx Android Development] calsurferpunk:
Hi again everyone. Here's an updated build with the latest October security patches:

https://androidfilehost.com/?fid=1322778262904026799
[Moto Maxx Android Development] rigues:
UPDATE: things got a bit better after a few full charge/discharge cycles, and after adjusting the BCL Low/High Voltage Threshold to 3.700/4.000 mV, as instructed on the 8.1 RR Remix Thread. However, yesterday the device shut down (as if it was without charge) with 30% charge left. I will try resetting the Battery Stats and see what happens.

Regards,
[Moto Maxx Android Development] imcensored1:
I have that same issue. Phone shuts off as it were dead but anywhere below 70%.

My problem with attempting to clear battery stats, is that it requires a full discharge of the phone. However whenever it starts doing the random shut off thing, it will do it on start up, and that corrupts the file system on the phone causing me to have to wipe system, and data and reinstall. So I can't fully drain the battery.

I'll have to check out the low/high voltage threashold thing.
[Moto Maxx Android Development] rammx:
A little bug, the time can't change automatic when travel
[Moto Maxx Android Development] imcensored1:
After a few weeks with the adjustments to the battery thresholds, I have noticed that instead of the phone powering off (thinking zero %) below 60%, now it shuts down below 60%. This is good for data corruption prevention, but doesn't quite solve my issue.

I was able to get the phone to completely drain (after what felt like 30 shutdowns and restarts), performed a full charge and wiped the battery stats file with no affect.

Maybe the replacement battery in this phone is just junk.
[Moto Maxx Android Development] 3Dota:
thanks for the update m8 ...
[Moto Maxx Android Development] darkghost568:
Hey if I wanted to build from source myself how would I do it? I ran the lineage git commands up through repo sync from the official lineage 15.1 page (https://wiki.lineageos.org/devices/cheeseburger/build) (I also have a Oneplus 5), and then ran the commands on BHB27's github page (https://github.com/fgl27/device_motorola_quark), but I'm getting "Use the ROOMSERVICE_BRANCHES environment variable to specify a list of fallback branches.

build/core/product_config.mk:238: *** Can not locate config makefile for product "lineage_quark". Stop.

build/core/product_config.mk:238: *** Can not locate config makefile for product "lineage_quark". Stop.

** Don't have a product spec for: 'lineage_quark'

** Do you have the right repo manifest?"

It doesn't seem to be able to find the roomservice.xml file I made in a new "local_manifests" folder. Help please?
[Moto Maxx Android Development] fgl27:
do you have the folders for the device? (device/kernel/vendor)

it folder must be there in roomservice.xml there is it entry and in it a "path" e.g.

<project name="fgl27/device_motorola_quark" path="[COLOR="Red"]device/motorola/quark[/COLOR]" remote="github" revision="O" />

so do you have those folder and they have files inside the same as in my source, if not that is the issue, you need to repo sync after creating the roomservice.xml

Also check that roomservice.xml to see if those error did not change the file as when you try to build and the device is not found the source tries to pull the files by adding the lineage repositories there, and lineage repositories for quark can't be used as they are too out of date.

I also don't build on lineage OS for a long time, I don't know if the tree works, I assume yes, so if you have all folders and it doesn't work let me know.
[Moto Maxx Android Development] darkghost568:
I do have all the folders (like device/kernel/vendor) and I made a new local_manifests folder to put the roomservice.xml in. After it wasn't working, I also pasted the roomservice.xml in the main manifests folder too. I searched the folder hierarchy and I couldn't find any "roomservice.xml" files anywhere else (it wasn't in device/motorola/quark , I don't even have the motorola folder under device). I'm not sure how to reply in a long written paragraph, so here are all the things I'm working with:

Screenshots of the folder hierarchy: https://imgur.com/a/f6zQbMF

Terminal output with errors: https://pastebin.com/YVkJ201L
[Moto Maxx Android Development] fgl27:
You placed

<remote name="github"
fetch="https://github.com/" />

Under

</manifest>

can you see the diference?

I wrote

so if doesn't have and under <manifest> not under </manifest> so at the top.

as here

https://github.com/LineageOS/android/blob/lineage-15.1/default.xml#L4

but as you can see is already declared in the default so is not needed to added

That .repo/local_manifests/roomservice.xml is not working because of that, so fix it and try to repo sync again and check if the folders are created, if not there is the chance that the .xml file you created is not see as a xml file as that can happen if you create it manually, so just copy .repo/manifests/default.xml to .repo/local_manifests/roomservice.xml" delete everything between <manifest> and</manifest> and past the content of

https://github.com/fgl27/device_motorola_quark#how-to-build-this

make shore the end result of the file is just this:

<?xml version="1.0" encoding="UTF-8"?>
<manifest>

<!-- Strings for LineageActions app-->
<project name="LineageOS/android_packages_resources_devicesettings" path="packages/resources/devicesettings" remote="github" revision="lineage-15.1" />

<!-- Device/kernel/vendor-->
<project name="fgl27/device_motorola_quark" path="device/motorola/quark" remote="github" revision="O" />
<project name="fgl27/BHB27Kernel" path="kernel/motorola/apq8084" remote="github" revision="O" />
<project name="fgl27/proprietary_vendor_motorola" path="vendor/motorola" remote="github" revision="O" />

</manifest>

and try again to build.
[Moto Maxx Android Development] darkghost568:
Ok fixed that, and still getting the same errors. I copied the default.xml from manifests and save as to the local_manifests folder then overwrote it with the roomservice.xml code.

Here's a new screenshot: https://imgur.com/a/NLVtfbn

And here's the error output from terminal (seems to be the same as before): https://pastebin.com/KbYZkPtg
[Moto Maxx Android Development] ChazzMatt:
It was a good run. Thank you for your work.
[Moto Maxx Android Development] fgl27:
If you can't see the device folder start over because I don't know what can be.

simple cmds that I use and works

mkdir source_oreo

cd source_oreo

repo init -u git://github.com/LineageOS/android.git -b lineage-15.1

cd .repo

mkdir local_manifests

cd local_manifests

echo '<?xml version="1.0" encoding="UTF-8"?>
<manifest>

<!-- Strings for LineageActions app-->
<project name="LineageOS/android_packages_resources_devicesettings" path="packages/resources/devicesettings" remote="github" revision="lineage-15.1" />

<!-- Device/kernel/vendor-->
<project name="fgl27/device_motorola_quark" path="device/motorola/quark" remote="github" revision="O" />
<project name="fgl27/BHB27Kernel" path="kernel/motorola/apq8084" remote="github" revision="O" />
<project name="fgl27/proprietary_vendor_motorola" path="vendor/motorola" remote="github" revision="O" />

</manifest>' > roomservice.xml

cat roomservice.xml

cd ../../

repo sync device/motorola/quark

cd device/motorola/quark/

ls -l BoardConfig.mk

as you can see I only test to see if the device tree worked and it did, so the xml is created and works just fine, after that successfully repo of device you can just "repo sync" everything that will work, but don't try to repo the source until you fixe manage to pull a folder from roomservice.xml and tested to see the folder, as will be very slow do to how many files need to be downloaded.

change "source_oreo" to wherever name you wanna the sorce to have

mkdir source_oreo

cd source_oreo
[Moto Maxx Android Development] fgl27:
and after doing the full "repo sync" and trying to build I get the expected ROM as result

[100% 11029/11029] build bacon
Package Complete: /home/fgl/android/source_oreo/out/target/product/quark/lineage-15.1-20181210-UNOFFICIAL-quark.zip

#### build completed successfully (25:13 (mm:ss)) ####

real	25m12.525s
user	57m47.721s
sys	3m30.078s
[Moto Maxx Android Development] fgl27:
probably your OS is not ready to build as I can build just fine the source is OK, there is this in the read.me from the device tree

that reference to this

https://github.com/fgl27/scripts/bl...machine--adb-shell-and-fastboot-for-debugging
[Moto Maxx Android Development] darkghost568:
Thank you!! It turns out this is a "me" problem because I was trying to build using WSL which doesn't support running 32-bit binaries. ( https://github.com/Microsoft/WSL/issues/1687 & https://github.com/Microsoft/WSL/issues/1771 ). I'll boot off a Ubuntu live external USB and try again.
[Moto Maxx Android Development] fgl27:
Oh I see, I run straight linux 64 on the machine, maybe virtual box similar running a VM can give you a better performance, as usb may be slower and if is will slow down the build time that already can be very slow depende on the hw you have.
[Moto Maxx Android Development] lucasfxd:
my phone keeps dying when I'm using it at 30% of battery... was working fine with the original firmware... I tried to "calibrate" the battery, leting reach 0% just with the screen on (took hours from 20 to 0), and then charging to 100%.. is not working. I'm using the stock rom kernel (provided here). could change the kernel solve my problem? or an calibration app? I love the rom, everything works fine, and I don't wanna come back to android 6... thank you :(
[Moto Maxx Android Development] FlavioV:
This rom has been discontinued for months now, don't expect any support here.

Using the custom kernel might help, and you can try the BCL controls in KA to mitigate the issue (see here, post #2 random power offs and reboots), but you should consider replacing your battery.

I've been using RR (different rom same device tree, both LOS based) ever since the first Nougat rom, and I've had the same issue as you for months until I replaced the battery earlier this year. Currently on RR Pie (same link as above) and now the battery works as intended.
[Moto Maxx Android Development] lucasfxd:
Como tá esse pie? É rápido? Botei o 7.1 RR e tá bem mais rápido que o 8.1 q eu tava, mas o problema persiste. Acha que tá valendo trocar pro pie em termos de desempenho e estabilidade? Sacanagem porque no 6 stock q eu usava não acontecia esses problemas que relatei de se desligar. Você conseguiu achar uma bateria original de verdade? Onde comprou? Valeu!

Edit: Basically I was asking about the stability and speed of the pie. And where he bought the new battery in Brazil.
[Moto Maxx Android Development] Davi_15:
Only English
[Moto Maxx Android Development] lucasfxd:
Basically I was asking about the stability and speed of the pie. And where he bought the new battery in Brazil. Sorry for that.