yashsingh1/xdaforums huggingface dataset:
[G 2014 Android Development] Danilo-Sanchez:
I've uploaded a new build including the fix for screen brightness.
[G 2014 Android Development] taurelio:
Awesome work Danilo. Thanks for the new build with the the fix for screen brightness. Working perfectly and very, very, very smooth. Congrats

Will you update the builds monthly like with cm 12.1?
[G 2014 Android Development] marcelo1998:
Please add screnshots?
[G 2014 Android Development] riancarlos18:
Thank you so much!

Great job, Danilo. I'm so glad to know that the Moto G 2014 hasn't been forgotten by developers. This ROM is running flawlessly on my titan.

I only have a question: How can I grant root access on LineageOS 13? I've tried to flash the addonsu-arm-signed zip, found in the official's LineageOS website, but it doesn't work at all.

Thanks in advance.
[G 2014 Android Development] Danilo-Sanchez:
Yes, I will update montly or if there's some important changes in source code I can update earlier.

Su addon isn't working yet on Lineage 13.

For now you can use SuperSU Beta: https://xdaforums.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133/post55256620#post55256620

Next build I'll make it pre-rooted.
[G 2014 Android Development] Danilo-Sanchez:
It's almost the same as CM13, but updated.
[G 2014 Android Development] riancarlos18:
It works!

This time the SuperSU Beta works too well. Thank you, Danilo! :good:
[G 2014 Android Development] riancarlos18:
Here you can see the LineageOs 13 screenshots. :good:
[G 2014 Android Development] tasvar:
Running fine and smooth.

Thank you Danilo.
[G 2014 Android Development] sayco23:
Hi, first thank you for your work. I am a satisfied user of your rom [UNOFFICIAL] [TITAN] [5.1.1]. And this new rom I like but could you add to this rom the gesture function of your old rom 5.1?

Thank you.
[G 2014 Android Development] Danilo-Sanchez:
I'll add it in the next build ;)
[G 2014 Android Development] NGowtham:
How is the battery life?

Edit:- Nevermind​, tried it myself. Getting good battery back up. This rom is so smooth and no lag at all. Only problem is my sd card doesn't show in any file manager nor in storage settings. I have to remove and reinsert every time. Didn'this problem on Danilo's CM12.1 and other Nougat rom's.
[G 2014 Android Development] Crix.Ful92:
Nice rom, bugfree and smooth.

Spotify notification does not expand in lock screen. Please fix it.

Thanks Danilo for another perfect rom!?

Inviato dal mio Moto G 2014 utilizzando Tapatalk
[G 2014 Android Development] Danilo-Sanchez:
Maybe it's something related to your sdcard. Try to backup your files and format your sd card.
[G 2014 Android Development] Danilo-Sanchez:
I'm uploading a new build today.

Changelog:

- Security patch of February.

- Gestures

- Pre-rooted

Edit: upload finished.
[G 2014 Android Development] m.lucas:
OK! Waiting....
[G 2014 Android Development] Danilo-Sanchez:
It's available already!
[G 2014 Android Development] NGowtham:
I'll give it a try.
[G 2014 Android Development] simfun:
Have you upgraded on latest Nova launcher without problems?
[G 2014 Android Development] mariojpereira:
No latest versions of nova launcher and greenfy as well makes the device anetr in bootloop. Tha solution is install an old version. In fact it's what I did. To remove the app you may reboot the device in safe mode and remove the app that's causing bootloop. I gess thats possible too enter on twrp and mount system, than hit to file explorer and navigate to system/privapps then delete 'nameapk.apk' and reboot it should work I guess.
[G 2014 Android Development] tejasrao1996:
I made backup of my apps on my SD card, but when i try to access it with file manager, it force closes. Happens with only that folder. This happens only with in Marshmallow ROM, that too recently. Does not happen with Nougat ROMs. Anyone else faced this?
[G 2014 Android Development] Danilo-Sanchez:
New build is available:

- Sources updated

- Security Patch: Sep-2017
[G 2014 Android Development] gokuss1234:
yes file manger crashes even in the latest build
[G 2014 Android Development] GSebas:
Greenify, Nova Launcher, X-plore, and others apps that are build with Android Studio 3 causes bootloop/crashes.

See bug 64434571 for more information.

https://issuetracker.google.com/issues/64434571
[G 2014 Android Development] simfun:
Thanks for clarifying this. It is really serious. Will they fix it anyway?
[G 2014 Android Development] simfun:
Migrated to Lineage 14.1 Official. Everything seem to work fine and no bootloop so far with any app. Thanks everybody for help, on this topic.
[G 2014 Android Development] Somebod y:
Don't want to migrate to Lineage 14.1, because this is the last Los version with xprivacy working.
[G 2014 Android Development] GSebas:
Supposedly is fixed (in build-tools 27), now wait for the applications being updated
[G 2014 Android Development] atomomega:
What a pain in the *ss. So I wasn't wrong, and it wasn't just my phone, I just didn't know how to debug it. Hope it gets fixed, I'm back to stock in the meantime
[G 2014 Android Development] sapo_joe:
Lineageos 14.1 is perfected to the point of being as stable as stock. Why not try it?
[G 2014 Android Development] CMKdaGreat:
You can also try AOSP Extended. Its very stable and performance is incredible(better than lineage os in some cases)
[G 2014 Android Development] n2droid:
Is the dev actively updating this? It was all smooth sailing since Friday, was very stable and was planning on keep this as daily driver, but once I installed Camera Roll from F-Droid, all hell broke loose. Everything keeps crashing, i cannot start the app, I cannot even uninstall it cause Package Manager crashes. Soft reboots when I try to start the app. Any ideas?

[edit]

Found a solution on that google thread posted earlier
[G 2014 Android Development] J4jks:
Hey [MENTION=6882175]Danilo-Sanchez[/MENTION] can u update with latest patches,

for major fixes like KRACK-ATTACK

BTW Thanks for the ROM
[G 2014 Android Development] J4jks:
[MENTION=6882175]Danilo-Sanchez[/MENTION] Giving force closes so many

Magisk doesn't work giving reboot while trying to open Magisk

Got root with add-on los 13 but every app is giving force close

I'm downgraded from los 14.1
[G 2014 Android Development] Danilo-Sanchez:
I'll make another build this week
[G 2014 Android Development] J4jks:
Thanks and fix the force closes and reboots
[G 2014 Android Development] Somebod y:
No need to write "please"?
[G 2014 Android Development] J4jks:
"PLEASE" fix the force closes

I really wanted an updated MM ROM [MENTION=6882175]Danilo-Sanchez[/MENTION]
[G 2014 Android Development] jonaaa:
Yeah yeah yeah you ALREADY said that, can you PLEASE let Danilo work now? He will release a new build when he get any FREE TIME.
[G 2014 Android Development] Danilo-Sanchez:
New build is available:

- Sources updated until Nov-16th

- October Security Patch

Try it and let me know if this fixes the force closes and reboots.
[G 2014 Android Development] J4jks:
Thanks, downloaded now

Try n give feedback
[G 2014 Android Development] J4jks:
Same happening ..?.

Installed los13+add-on los 13+ xposed

After reboot trying to install any app gives filemanager force close even didn't install xposed manager

Going through file manager also giving force close
[G 2014 Android Development] Somebod y:
Same here, rom is working fine, patch level is 20171001, but updating several apps causes bootloop..... :(

---------- Post added at 12:22 AM ---------- Previous post was at 12:01 AM ----------

Updating theese apps on Los14 causes no problem, so this is related to Los13
[G 2014 Android Development] Danilo-Sanchez:
It seems that this issue is related to LOS 13 in general and not only on Titan.

https://jira.lineageos.org/browse/BUGBASH-1052
[G 2014 Android Development] J4jks:
I think ,without any extra zips it works flawlessly

Did anybody try ?
[G 2014 Android Development] sapo_joe:
I tested the build before the latest and it worked fine with nano gapps and SuperSU. Good performance and very stable.
[G 2014 Android Development] Somebod y:
Is anybody working on this problem?
[G 2014 Android Development] J4jks:
For me with magisk it was problematic with the previous build too..
[G 2014 Android Development] Danilo-Sanchez:
I didn't find anything related to this bug in code review, so I think that unfortunately there's no one working on it.

Even 14.1 isn't receiving so much attention these days.
[G 2014 Android Development] J4jks:
today I tried again with SuperSU ,untill xposed is installed it worked fine and no force closes and all

but with Xposed(tried v86,v87 and v88.2 too) it started force closes from trebuchet and to file managers even didnot able to iinstall Xposed manager but installed it through TWRP and now trying to pen the Xposed installer gives reboots

Is it with xposed or Los13 only..?

Does anybody have issue like this on LOS13 with and without Xposed..?
[G 2014 Android Development] hrby:
I probably have this problem after updating Audio Recorder from F-Droid.

It then comes "trebuchet is terminated because of errors", "F-Droid ...", "Audio Recorder ..." and then reboot.

After reboot I tried to uninstall the audio recorder, but it does not work.

Then I manually deleted the audio recorder with Ghost Commander in "root: / data / app" and the phone was normal.

Is this the problem?

PS: I have neither Xposed nor Gaps installed.
[G 2014 Android Development] Somebod y:
I am running xposed 87 without any problem until i try to update apps. Some apps are updating without any problem, some cause crashes.
[G 2014 Android Development] hrby:
Yes, that's the way it is with me, only I have not installed Xposed.
[G 2014 Android Development] MariferC:
And also has a [untested] patch :o (by Olaf Titz)

--- AssetManager0.cpp	2017-11-23 22:13:49.276849476 +0100
+++ AssetManager.cpp	2017-11-23 22:13:49.868848761 +0100
@@ -417,9 +417,9 @@
ap.type = kFileTypeRegular;
ap.path = String8(apkPath);

- ResXMLTree tree;
-
Asset* manifestAsset = openNonAssetInPathLocked(kAndroidManifest, Asset::ACCESS_BUFFER, ap);
+ {
+ ResXMLTree tree;
tree.setTo(manifestAsset->getBuffer(true),
manifestAsset->getLength());
tree.restart();
@@ -438,7 +438,7 @@
pkgName = (str ? String8(str, len) : String8());

}
-
+ }
manifestAsset->close();
return pkgName;
}

EDIT: Here is attached the library with the fix for this bug based on the previous patch. I've tested with the apps Greenify 3.6.2 , Magisk Manager 5.3.0 and Nova Launcher 5.4.1 and no more bootloops. In any case, backup the libandroidfw.so file that is on /system/lib and install the zip from recovery.
[G 2014 Android Development] hrby:
Everything happens with the patch.
[G 2014 Android Development] JheymersonLira50:
This patch works very well. Do you know if there is a patch like this for Danilo's CM 12.1, because this problem of apps making the phone reboot is happening also in Cyanogen 12.1
[G 2014 Android Development] Danilo-Sanchez:
It seems that the fix for bootloops was merged in Lineage 13.0 sources.

So, I'll make another build soon to include this fix. ;)
[G 2014 Android Development] Danilo-Sanchez:
I'm having some problems to make the new build.

As soon as I fix this problem I'll inform here.
[G 2014 Android Development] Somebod y:
Happy new year, Danilo!
[G 2014 Android Development] hrby:
Hello Danilo,

is end of life?
[G 2014 Android Development] Danilo-Sanchez:
Happy new year!

Sorry, I was in vacation, but now I'm back.

I'll try again to make a new build.

If everything goes right I'll upload until Friday.
[G 2014 Android Development] Somebod y:
So no need to worry about you. Good luck
[G 2014 Android Development] emil_515:
Could someone enlighten me on the difference(if any) between this Rom and the regular CM13 ones ?
[G 2014 Android Development] sapo_joe:
Main difference is that this one still gets updates. :D
[G 2014 Android Development] tejasrao1996:
AFAIK, there is no difference except for bug fixes and security patches. They just changed the name from CM to LineageOS.
[G 2014 Android Development] Danilo-Sanchez:
New build is available!

Please try it and tell me if this build fixes the bootloop issue.
[G 2014 Android Development] rexit1979:
New build Bootlooping on my G2
[G 2014 Android Development] zitronenmelissa:
bootloop on mine two times before sim unlock screen, but the third boot was fine: pin code, setup, etc. it's all working

---------- Post added at 18:14 ---------- Previous post was at 18:13 ----------

thanks for including cmactions again!

---------- Post added at 18:54 ---------- Previous post was at 18:14 ----------

best thing is, that I can install apps, I wasn't able to install on any custom marshmallow rom e.g. Yr.no or new zarchiver 0.9.1

that is fantastic, now I don' t need to install older versions anymore :)
[G 2014 Android Development] Danilo-Sanchez:
Thanks for your feedback :)
[G 2014 Android Development] Thariq hussain:
I have installed the rom but I could see root access only for ADB, So I tried flashing magisk manger but it is not listing any where also the root option was gone from 'deveoper options' how could I get complete root access?

I need to restore files from titanium backup
[G 2014 Android Development] Danilo-Sanchez:
Download su add on from Lineage official website.
[G 2014 Android Development] Thariq hussain:
Thank you, Does it has feature like mgisk hide? because some apps like Google tez will not be installed on rooted device and I usually add these applications to magisk hide.
[G 2014 Android Development] Danilo-Sanchez:
No, if you want to hide root from apps you need to install Magisk.
[G 2014 Android Development] Danick8989:
The rom works great, but for some reason im experiencing freezes on the twitter app. I tried reinstalling it several times but it's no use
[G 2014 Android Development] sapo_joe:
Does this ROM feature the theme engine found on CM13 or was it removed? I tested CM13 the other day, and that theme engine is awesome!
[G 2014 Android Development] Danilo-Sanchez:
It has CMTE.
[G 2014 Android Development] sapo_joe:
Many thanks! :D
[G 2014 Android Development] sapo_joe:
How's the ROM? Have the force closes and bootloops stopped? I'm thinking about going back to it because of the theming capabilities...
[G 2014 Android Development] zitronenmelissa:
I've been using Danilo-Sanchez Roms a long time, cm-12/lineage-13. It's stable and optimized for Moto G2 eg. CMActions (Wake Gesture) for Moto G2 is an extra brought to Moto G2 by Danilo-Sanchez, no standard for thea/titan. Best Roms ever for Moto G2!
[G 2014 Android Development] sapo_joe:
Thanks a lot!

By the way, cmactions can be enabled on any lineage or cm based ROM, even on nougat, I'm using it on Lineage 14.1. Take a look here: https://xdaforums.com/moto-g-2014/themes-apps/mod-enable-cmactions-cm13-t3368084
[G 2014 Android Development] nbah07:
{ESL here}

Please, don't say I'm in trouble! Tell me this has support, instead!

I flashed LOS 13 MM because had been looking for a MM ROM to enhance the battery charge frequency, since I no screen-on time counting type[...] Lasting 2 days with my routine of usage. (no greenify or other power saver apps, yet. Just flat standard LOS13 with its own settings/profiles tweaking)

After changing some settings from default, including 'Not to turn on screen when power plugged AC outlet'. Not saying this particularly caused the fault, but humans like to blame someone, everytime.

Result: the first time AC outlet was plugged, it did keep "quiet". Right next, to make sure everything worked, I pressed power button and had no sign of operation. Big Fail.

Opened a CMD prompt with ./adb devices and ./fastboot devices with USB cable attached = No response.

Ok, what can I do now? help?!
[G 2014 Android Development] nbah07:
call to developers

I had trouble with LOS13 MM. Did some config alterations, including "Don't momently turn screen on when pluging power charger". Gave me such bad week. Dark screen error. No clue how to fix by then. Like the 90's all over again.

But there is the 120 second vol down and power buttons hold which led me access fastboot commands and even TWRP recovery, all of them with dark screen. Flashed stock MM (v6) XT1068_TITAN_RETBR_DS_6.0_MPB24.65-34-3_cid12_CFC.xml.zip without gpt.bin and motoboot.img; later attempt with both, the whole procedure. No results! No screen turning on. No viewable display.

Any thoughts? It can't be hard bricked, can it?

Well, if flashed with custom rom (stock?), work as debugging device for developers.
[G 2014 Android Development] taurelio:
It seems screen backlight not working...

Sent from Mi A1 with Tapatalk Pro
[G 2014 Android Development] CLPose:
If you flash it with latest stock firmware, it should work unless there's a hardware problem. As you described it, it seems to be a hardware problem. So sorry!
[G 2014 Android Development] Danilo-Sanchez:
As [MENTION=6310891]CLPose[/MENTION] wrote, If you flashed stock firmware and the problem persisted, I think it's a hardware issue.
[G 2014 Android Development] nbah07:
more feedback

I'm glad there's been back up from you.

What exactly hardware are you talking about? What brightens the LED(?) screen component, isn't itself? Would 'backlight' be this particular brightening component? You know, I was suggested to change the whole (mother?)board by the mobile technician. He's not seems to be opportunist, but if the repair is simpler than that, I could advice him, apparently new in the business, to follow yours (xda's) advices against his former diagnosis.

I would repair it myself, since pondering to buy a solder iron, estimating needed wattage for my eventual fixing set and additional supplies of its own, anyway.
[G 2014 Android Development] Danilo-Sanchez:
I don't know exactly what is the problem, but if the problem persists when you enter fastboot mode and even after flashing stock rom, then this is not software related.

Try to take you phone to another person to get other diagnosis.

I don't think you need to change the whole motherboard. I think the problem is on the screen.

I saw some phones with motherboard problems and I wasn't able to flash stock rom because they didn't enter fastboot mode.
[G 2014 Android Development] Andrio:
Is the problem fixed yet? Or you stopped working on it?:confused:
[G 2014 Android Development] Danilo-Sanchez:
I was busy and didn't try to build LOS 13 again. But as I've built AEX Oreo, I think it's fixed. I'll try to build LOS 13 next week.
[G 2014 Android Development] Andrio:
That'd be awesome. Can't wait:D
[G 2014 Android Development] aaruni_k96:
Uh, bump?
[G 2014 Android Development] Danilo-Sanchez:
Unfortunately, I'm not with the PC that I used to build roms. The PC that I'm using now can't handle this.
[G 2014 Android Development] aaruni_k96:
Do you mind if I pm you ?
[G 2014 Android Development] Danilo-Sanchez:
No, you can pm me. ;)
[G 2014 Android Development] Crix.Ful92:
Spotify's lockscreen bug it's persist with last build.. please fix it :(

Another question, the only way to remove # (root) from the status bar is to install supersu beta from recovery or you can add a flag in settings to remove it.

Sorry for english :3

Inviato dal mio Moto G 2014 utilizzando Tapatalk
[G 2014 Android Development] Danilo-Sanchez:
Could you please send me a screenshot of Spotify's bug?

For now, the only way to remove # from statusbar is to install supersu, but I'll see if I can add an option to remove it.
[G 2014 Android Development] Crix.Ful92:
I can't expand this Spotify notification in lock screen

Inviato dal mio Moto G 2014 utilizzando Tapatalk
[G 2014 Android Development] leomalaj10:
I am using LineageOS Nougat, can downgrade with LineageOS MM? Thank you very much in advance.
[G 2014 Android Development] CLPose:
Hi! This Xposed module offers the possibility to hide # symbol: http://repo.xposed.info/module/com.smartmadsoft.xposed.aio. You may take a look at this to find some hints! ;) Good luck!
[G 2014 Android Development] NGowtham:
Lol just noticed this Easter egg xD
[G 2014 Android Development] @anonymous94:
Is this model compatible for this rom??
[G 2014 Android Development] issux:
Have you seen this message?

https://xdaforums.com/android/general/how-to-remove-superuser-indicator-cm13-t3490425
[G 2014 Android Development] Danilo-Sanchez:
You can downgrade. Just make a clean install.

Yes, it is compatible.
[G 2014 Android Development] Danilo-Sanchez:
Thank you! I'll try to add an option to enable and disable it.
[G 2014 Android Development] Danilo-Sanchez:
How did you get to this easter egg?

I've clicked on Android Version and Lineage Version and didn't get to this.
[G 2014 Android Development] joshdsy:
[MENTION=6882175]Danilo-Sanchez[/MENTION]

could you post your .repo/local_manifests/roomservice.xml for LineageOS 13.0

<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<project name="LineageOS/android_device_motorola_titan" path="device/motorola/titan" remote="github"$
<project name="LineageOS/android_device_motorola_msm8226-common" path="device/motorola/msm8226-commo$
<project name="LineageOS/android_device_qcom_common" path="device/qcom/common" remote="github" />
<project name="LineageOS/android_kernel_motorola_msm8226" path="kernel/motorola/msm8226" remote="git$
</manifest>

this is what i use

Im not sure what to use for the proprietary bits.

I was looking at the same guide you have used but its for Lineageos 14

https://xdaforums.com/moto-g-2014/general/guide-build-lineageos-titan-ubuntu-t3537396?nocache=1

If i try to use some of the muppets stuff i also end up with a similar error

make: *** No rule to make target 'vendor/motorola/msm8226-common/proprietary/bin/hardware_revisions.sh', needed by '/home/josh/android/out/target/product/titan/system/bin/hardware_revisions.sh'. Stop.
[G 2014 Android Development] Danilo-Sanchez:
<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<project name="LineageOS/android_device_motorola_titan" path="device/motorola/titan" remote="github" />
<project name="LineageOS/android_device_motorola_msm8226-common" path="device/motorola/msm8226-common" remote="github" />
<project name="LineageOS/android_device_qcom_common" path="device/qcom/common" remote="github" />
<project name="LineageOS/android_kernel_motorola_msm8226" path="kernel/motorola/msm8226" remote="github" />
</manifest>
[G 2014 Android Development] joshdsy:
so your using the same as me?

some how I keep seeing errors such as this one about hardware_revisions.sh

make: *** No rule to make target 'vendor/motorola/msm8226-common/proprietary/bin/hardware_revisions.sh', needed by '/home/josh/android/out/target/product/titan/system/bin/hardware_revisions.sh'. Stop.
[G 2014 Android Development] Danilo-Sanchez:
Did you extract proprietary files?
[G 2014 Android Development] joshdsy:
I did run ./extract-files.sh but im running nitrogen os at the moment would that make a difference? its a 7.1 rom .
[G 2014 Android Development] Danilo-Sanchez:
Yes, this can be the problem.

The first time I built Lineage 13 I had to install CM13 to extract the files.
[G 2014 Android Development] joshdsy:
Hmmm let me try that. thanks for your time
[G 2014 Android Development] NGowtham:
I guess it's because I've applied CM Theme (coalfield).
[G 2014 Android Development] sayco23:
Simply a perfect rom.

Thank you.
[G 2014 Android Development] abi23:
best rom every thing is perfect. :) :)only one thing wifi network is not stable any one have same problem ??:mad:
[G 2014 Android Development] taurelio:
Yes WiFi is not stable in public networks. I havê spent 3 days in a hotel. Whit los 13 sometimes loose connection. Whit cm 12.1 on the same place no problems with WiFi. Maybe something to do with los 13. But still a great rom
[G 2014 Android Development] @anonymous94:
Phone is awake while charging
[G 2014 Android Development] Danilo-Sanchez:
I've had some issues with wifi in earlier stages of CM13 and solved upgrading firmware of my router, but unfortunately we can't do this with every router.

I expected to have better battery backup, but doze isn't working here.

I'm thinking about going back to CM12.1.
[G 2014 Android Development] taurelio:
Yeap. I also have returned to CM12.1. Cant you make a new build with the brightness bug fix? CM 12.1 its super smooth and stable. I think the problems with lineage 13 is that is not build for our line products. If falcon was suported it would be more stable with titan.