yashsingh1/xdaforums huggingface dataset:
[Moto G5 ROMs, Kernels, Recoveries, & Other Develop] LambdaPerl:
Cheers for your reply.

I get this kind of output:

chmod: /storage/cb7a775e-c876-454f-af3d-x//.android_secure: Permission denied
chmod: No /storage/cb7a775e-c876-454f-af3d-x/files: Permission denied
chmod: No /storage/cb7a775e-c876-454f-af3d-x/Videos: Permission denied
chmod: No /storage/cb7a775e-c876-454f-af3d-x/Android: Permission denied
chmod: No /storage/cb7a775e-c876-454f-af3d-x/TWRP: Permission denied
chmod: No /storage/cb7a775e-c876-454f-af3d-x/IntStBk: Permission denied
chmod '/storage/cb7a775e-c876-454f-af3d-x/' to 40660
chmod '/storage/cb7a775e-c876-454f-af3d-x/lineage_cedric-ota-bcf3b49f1e-dld20171112.zip' to 100660
chmod '/storage/cb7a775e-c876-454f-af3d-x/files' to 40660
chmod '/storage/cb7a775e-c876-454f-af3d-x/Videos' to 40660
chmod '/storage/cb7a775e-c876-454f-af3d-x/logo.bin' to 100660
chmod '/storage/cb7a775e-c876-454f-af3d-x/addonsu-14.1-arm-signed.zip' to 100660
chmod '/storage/cb7a775e-c876-454f-af3d-x/NanoMod-uninstaller-14.9.20171213.zip' to 100660
chmod '/storage/cb7a775e-c876-454f-af3d-x/NanoMod-patcher-14.9.20171213.zip' to 100660
chmod '/storage/cb7a775e-c876-454f-af3d-x/logo_airbusOrange.zip' to 100660
chmod '/storage/cb7a775e-c876-454f-af3d-x/Android' to 40660
chmod '/storage/cb7a775e-c876-454f-af3d-x/TWRP' to 40660
chmod '/storage/cb7a775e-c876-454f-af3d-x/IntStBk' to 40660
chmod '/storage/cb7a775e-c876-454f-af3d-x/lineage-14.1-20171018-UNOFFICIAL-cedric.zip' to 100660
chmod '/storage/cb7a775e-c876-454f-af3d-x/app-debug.apk' to 100660
chmod '/storage/cb7a775e-c876-454f-af3d-x/app-release.apk' to 100660

I have trimmed some of the output as it contained all my files on the SD card basically.

The above output is when I pipe both stderr and stdout to a file and, as you can see, stderr has been segregated from stdout even though it shows as inline in the terminal. I couldn't see an easy way to fix that.

I'm not sure this will lead to anything though, as the following still stands when I `stat` the SD card:

$ stat /storage/cb7a775e-c876-454f-af3d-x/
File: /storage/cb7a775e-c876-454f-af3d-x/
Size: 4096 Blocks: 16 IO Block: 4096 directory
Device: 1ah/26d Inode: 0 Links: 13
Access: (0755/drwxr-xr-x) Uid: ( 0/ root) Gid: ( 9997/everybody)
Access: 2018-03-31 22:30:04.982130209 +0000
Modify: 2018-03-31 23:01:49.005046770 +0000
Change: 2018-04-01 09:51:24.599334636 +0000
Birth: -
$ su
cedric:/ # stat /storage/cb7a775e-c876-454f-af3d-x/
File: `/storage/cb7a775e-c876-454f-af3d-x/'
Size: 4096 Blocks: 16 IO Blocks: 512 directory
Device: 18h/24d Inode: 0 Links: 13
Access: (771/drwxrwx--x) Uid: ( 0/ root) Gid: ( 1015/sdcard_rw)
Access: 2018-03-31 22:30:04.982130209
Modify: 2018-03-31 23:01:49.005046770
Change: 2018-04-01 09:51:24.599334636

It seems like the filesystem presents a different group ID depending on what user is logged in. It looks like it might be a primitive alternative to ACLs...
[Moto G5 ROMs, Kernels, Recoveries, & Other Develop] wzedlare:
But you should've used this command as root.
[Moto G5 ROMs, Kernels, Recoveries, & Other Develop] LambdaPerl:
Sorry to not make it clear, but I did :S.

Chmod'ing the files would have failed if I wasn't, right?

I also just tried the above with SELinux in Permissive mode (`setenforce 0`) but the results are the same.
[Moto G5 ROMs, Kernels, Recoveries, & Other Develop] LambdaPerl:
Some research later, I think I know what causes it, but I don't know how to fix it for myself.

Basically, since Android 6.0 (my previous device was an Android 5), apps now have to ask for the permission at runtime to write to the SD card, as described in https://source.android.com/devices/storage/, otherwise they get shown a version of the SD card where the group owner is 'everybody' and write access is restricted to the owner, root.

Yet, enough of my apps don't seem to cope with this properly and don't seem to be making the proper API calls to ask for that permission at runtime, possibly because they were written in simpler times when you could get the permissions at install-time, like you would expect from a sane system. Sadly, this is no longer the case.

Thanks [MENTION=6810779]wzedlare[/MENTION] for trying to help with this but I think it might be up to the application authors to have to adapt to this new-fangled system.
[Moto G5 ROMs, Kernels, Recoveries, & Other Develop] crns:
Hello, I recently installed Lineage on my Moto G5 XT1676.

Almost everything works fine but something is wrong with the FM Radio App. When people are talking it sound quite normal but if it plays music the pitch changes alot, it sounds distorted and sometimes it reverberates.

I also noticed that if I use the default music app and I'm clicking onto the bar with the current song, the app closes but the music continues.

I did not had any of these problems with the custom rom. I'm looking forward for some help. Thanks!
[Moto G5 ROMs, Kernels, Recoveries, & Other Develop] trance89:
+1

This is the only problem i have with this rom, fm radio is totally useless this way

Can it be fixed or is there any working 3rd party radio app?
[Moto G5 ROMs, Kernels, Recoveries, & Other Develop] ektus:
+2

There is one app on f-droid (GPL3 version of spirit fm, https://f-droid.org/en/packages/fm.a2d.sf/) but that one doesn't work. It starts and acquires root privileges, but fails to activate the fm radio.

Google play reports https://play.google.com/store/apps/details?id=com.nextradioapp.nextradio as being not compatible. I haven't found more apps yet.

Regards

Ektus.
[Moto G5 ROMs, Kernels, Recoveries, & Other Develop] Astitva_:
Even pdanet isnt working..... actually the problem is that the phone is taking the comp as a simple charger and not a computer:confused:,.... plz help with this thingy
[Moto G5 ROMs, Kernels, Recoveries, & Other Develop] Alchedin:
Do NOT quote the first post!

Whenever you connect the phone to the computer, you can switch modes by pulling down the top menu (in android)(on the phone) and change the mode from only charging to other modes like data transfer. So I can imagine PDAnet "even not working" is an problem of -you- the user to use hardware/software correctly.
[Moto G5 ROMs, Kernels, Recoveries, & Other Develop] Mister-XY:
Sometimes I have the problem that I am connected to the internet, but no data is loaded.
[Moto G5 ROMs, Kernels, Recoveries, & Other Develop] Astitva_:
No, there IS no menu in the notification panel that ur talkin abt....I'd say it's the problem of the rom and NOT our handling...

Kindly fix it and also, the battery drains veery quickly
[Moto G5 ROMs, Kernels, Recoveries, & Other Develop] DaLiCaM:
Is this firmware valid for xt1670 Latin America?
[Moto G5 ROMs, Kernels, Recoveries, & Other Develop] ryandanieldonovan:
building lineageOS14.1 for MotoG5

I was attempting to use the repositories as available, but I"m hitting this error. Anyone know how to get around it?

ln: failed to create symbolic link '/home/ryandanieldonovan/android/lineage/out/target/product/cedric/system/bin/expat': File exists

find: ‘/home/ryandanieldonovan/android/lineage/out/target/common/obj/SHARED_LIBRARIES/libwifi-hal-mock_intermediates’: No such file or directory

Starting build with ninja

ninja: Entering directory `.'

ninja: error: '/home/ryandanieldonovan/android/lineage/out/host/linux-x86/bin/dtbToolCM', needed by '/home/ryandanieldonovan/android/lineage/out/target/product/cedric/dt.img', missing and no known rule to make it

build/core/ninja.mk:151: recipe for target 'ninja_wrapper' failed

make: *** [ninja_wrapper] Error 1

make: Leaving directory '/home/ryandanieldonovan/android/lineage'

#### make failed to build some targets (30 seconds) ####

---------- Post added at 06:23 PM ---------- Previous post was at 06:00 PM ----------

Tried this: stackoverflow.com/questions/31098588/cm12-build-for-one-plus-failed?utm_medium=organic&utm_source=google_rich_qa&utm_campaign=google_rich_qa

make clobber

brunch cedric

.. I end up with this:

Checking build tools versions...

find: ‘/home/ryandanieldonovan/android/lineage/out/target/common/obj/SHARED_LIBRARIES/libwifi-hal-mock_intermediates’: No such file or directory

build/core/base_rules.mk:183: *** vendor/qcom/opensource/cryptfs_hw: MODULE.TARGET.SHARED_LIBRARIES.libcryptfs_hw already defined by device/qcom/common/cryptfs_hw.

build/core/ninja.mk:166: recipe for target '/home/ryandanieldonovan/android/lineage/out/build-lineage_cedric.ninja' failed

make: *** [/home/ryandanieldonovan/android/lineage/out/build-lineage_cedric.ninja] Error 1

make: Leaving directory '/home/ryandanieldonovan/android/lineage'

... so not the solution I need.

..
[Moto G5 ROMs, Kernels, Recoveries, & Other Develop] wzedlare:
$ rm -rf device/qcom/common
$ git clone https://github.com/LineageOS/android_device_qcom_common -b cm-14.1 device/qcom/common
[Moto G5 ROMs, Kernels, Recoveries, & Other Develop] ryandanieldonovan:
Thanks. i got a bit further. I ended up also having to pull in resources from potter and android_packages_resources_devicesettings before I could get a build. ... Downloading the image now.... will see if it works.
[Moto G5 ROMs, Kernels, Recoveries, & Other Develop] trance89:
Please can we get an updated build with latest security patches?

Thanks very much
[Moto G5 ROMs, Kernels, Recoveries, & Other Develop] staffe:
Got an updated build if interested:

lineage-14.1-20180612-UNOFFICIAL-cedric.zip

lineage-14.1-20180612-UNOFFICIAL-cedric.zip.md5

Nothing special. Just latest LineageOS 14.1 buildt with the default toolchain and device tree/kernel/blobs from the 1st post.

Security patch level is still 5th of May though
[Moto G5 ROMs, Kernels, Recoveries, & Other Develop] k4tfish:
I'm interested. Is that your build?
[Moto G5 ROMs, Kernels, Recoveries, & Other Develop] staffe:
Yes, just the build not the development/git work. I also think you can dirty flash over OPs latest build, cause the device specific files haven't changed since then. But i'm not 100% sure about that.
[Moto G5 ROMs, Kernels, Recoveries, & Other Develop] zitronenmelissa:
still no usb-tethering and fmradio is still weird, but very good Rom - thank You ... #interested :D
[Moto G5 ROMs, Kernels, Recoveries, & Other Develop] staffe:
I'm glad to share.

Btw, the security patch level of the 14.1 sources is now June 2018.

I've updated my above post with a newer build.
[Moto G5 ROMs, Kernels, Recoveries, & Other Develop] tjMF6:
Has anybody tested this build? Can i flash it over the latest build from wzedlare?

Why is wzedlare not updating his greatfull rom :crying:
[Moto G5 ROMs, Kernels, Recoveries, & Other Develop] :
Because he's busy, he doesn't have Cedric anymore or 14.1 is old now and 15.1 is newer and better
[Moto G5 ROMs, Kernels, Recoveries, & Other Develop] trance89:
14.1 is old but rock solid stable and still we can use it with latest security patches, staffe's build is perfect too, same stability as wzedlare's builds just with latest security patches, only problem with 14.1 builds is buggy fm radio (99% of people don't use this function i think) and the usb tethering but this we have from the beginning, wifi tether is ok so no problem

15.1 is still buggy, maybe after official oreo with sources/blobs will be released we will get more stable roms

and for example dualsim g5 (xt1676) users like me get bootloops after installing any oreo rom with gapps (a lot of people complaining in los15.1 and aosp topics), this is a major bug and until this will be fixed i will not touch any oreo based rom again

yes it's working perfectly after dirtyflash with latest pico opengapps package
[Moto G5 ROMs, Kernels, Recoveries, & Other Develop] wzedlare:
I was going to update the rom but I had been waiting for June security patch.Staffe published the build earlier than me, so I do not need to update it for now.
[Moto G5 ROMs, Kernels, Recoveries, & Other Develop] floydburgermcdahm:
Yes - it worked flawlessly.
[Moto G5 ROMs, Kernels, Recoveries, & Other Develop] tjMF6:
Works perfectly!! Could flawlessly be installed over the latest build from topic creator! June Security Patches integrated! :cool::good:

THANKS
[Moto G5 ROMs, Kernels, Recoveries, & Other Develop] ektus:
Thank You! Installed on my XT1776 (3GB Dual-SIM) and it's still alive :cool:
[Moto G5 ROMs, Kernels, Recoveries, & Other Develop] filipedonato:
Thanks!
[Moto G5 ROMs, Kernels, Recoveries, & Other Develop] rapmed090983:
Does this ROM record videos with audio in good quality? I'm using the Viper ROM and the sound on the recorded videos comes out distorted, especially when the background sound is too loud.
[Moto G5 ROMs, Kernels, Recoveries, & Other Develop] tablord:
Mediocre call quality and MTP broken

Thanks for all your efforts providing this ROM [MENTION=6810779]wzedlare[/MENTION] and [MENTION=4053902]staffe[/MENTION]

Unfortunately, the in call quality is so mediocre that I can not really use it as a daily driver. This has been mentioned in previous posts, e.g. post74751719 or post74746530 or post74713310, and seems to be prevalent in all non-Stock Roms.
[MENTION=7828377]b.zill[/MENTION] mentioned (AMR-WB) settings as an approach to tackle this issue in this post. However, [MENTION=5445560]soumitro316[/MENTION] confirmed here that it was not working for him.

Don't you devs have these issues or do you have a hint how to fix it?

MTP is not working either (on Windows 10) in the sense that copying files from the Moto G5 to PC is not working at all while the other way around works flawlessly. This too seems to be a common problem with this device but in contrast to the call quality issues I can circumvent with the help of the cloud etc.
[Moto G5 ROMs, Kernels, Recoveries, & Other Develop] b.zill:
Mediocre call quality, MTP and USB tethering broken

Yes, same here. I avoid using the Moto G5 for telephony, as I often can hardly understand the callers (while they don't seem to have a problem), especially in noisy environment. It sounds like calling from Mars and seems to be related to transmission modes, sometimes it's worse. Sound is slightly distorted, high middle and high frequencies seem to be cut.

Call quality and USB problems (MTP and tethering not working) are the major issues for me as well.

Very sad, but as I gained the feeling that the OP did not really want to address any of this or support the ROM besides recompiling with Lineage patches, I gave up on contributing to this thread.

Lineage 15.1 for cedric seems to have the same issues, so I am hoping that the upcoming (?) 15.1 Oreo stock release might help on this.
[Moto G5 ROMs, Kernels, Recoveries, & Other Develop] tablord:
For me it is mostly stuttering and rustling sound which renders calling feature unusable. I too have had similar issues with the Unofficial Lineage 15.1 Rom. Additionally encryption did not work on that Oreo build, so I thought that by switching to this supposedly more stable and mature Nougat Rom I could avoid the issues... Encryption works fine with this one but the lousy call quality remains an aggravating disadvantage.

I'll wait and see if [MENTION=6810779]wzedlare[/MENTION] or [MENTION=4053902]staffe[/MENTION] are at least replying in the coming days. Else I will probably just move on. That is return to the Stock Rom at least for now. [MENTION=7828377]b.zill[/MENTION] have you went back to stock successfully? I have read that some folks have had trouble loosing their IMEI etc.
[Moto G5 ROMs, Kernels, Recoveries, & Other Develop] b.zill:
No, I did not revert to stock since I got that device to run Lineage on it. And I did not install Lineage 15.1 either, as I don't see an advantage in having the same problems as on 14.1 plus 64-bit trouble.

As long as it is not really known what exactly causes the IMEI or 4G loss (and what else is affected/lost), all guides and hints seem preliminary except using a 32-bit recovery. After reverting to stock, I would avoid OTA updates.
[Moto G5 ROMs, Kernels, Recoveries, & Other Develop] staffe:
To be clear: I'm not a developer. I just took the source files from LineageOS and [MENTION=6810779]wzedlare[/MENTION] and compiled it. That's just a few commands in the correct build environment.

As for the call quality, i had this problem too but it somehow has gotten better for me on LineageOS 15.1. Only thing i did was to grant all permissions to the phone app (by default this wasn't the case) but i have no idea if that had something to do with it.
[Moto G5 ROMs, Kernels, Recoveries, & Other Develop] tablord:
Seems like a trap to me then. If it means either giving up the calling feature or risk bricking your device when reverting back to stock. Is it not possible to fully recover the custom rom including IMEI etc. if it was properly/fully backed up in TWRP before? Just in case the stock rom installation is not successful.

Hey [MENTION=4053902]staffe[/MENTION], thanks for clarification. What exactly do you mean by "gotten better for me"? Is the call quality now on par with the stock rom or official lineageos custom roms on other phones? Or just a little less awful but still way below average or what one would expect? So is it acceptable to you now? Of course expectations are always highly subjective...

And did you try that trick - granting all permissions to the phone app - on this LOS 14.1 build as well? If so, what happened?
[Moto G5 ROMs, Kernels, Recoveries, & Other Develop] ektus:
I have sound distortion when trying to use the FM radio, but not for phone calls. I believe phone calls are GSM, though, not LTE, so perhaps the sound path and codec are different. I have two SIM cards in use, a prepaid one for data and SMS (if any) and another, older one without data using a different provider for phone calls.

Regards

Ektus.
[Moto G5 ROMs, Kernels, Recoveries, & Other Develop] staffe:
To be honest, i have no comparision to stock. I flashed a Custom ROM on my G5 the 1st day i had it :eek:

With "it's gotten better" i meant, that i can now understand every word during a call without problems. That wasn't even slightly the case before.

Sorry, didn't try that on 14.1

While it sure is worth a try, i somehow have a doubt that just changing permissions will fix this issue. Maybe [MENTION=5982915]CodeZero[/MENTION] changed some blobs or some sourcecode regarding to it? (i'm on a two weeks old, self buildt LineageOS 15.1)

Another thing you can try (just for the sake of testing) is to flash gapps from opengapps.org if you haven't already. As far as i know it includes the Google Dialer and the DialerFramework. Just a wild guess but i noticed some people with this problem stated, that they are running LineageOS without gapps. Including me but as mentioned, call quality is okay for me now.
[Moto G5 ROMs, Kernels, Recoveries, & Other Develop] ektus:
I've got Open GApps installed (pico), the dialer is com.android.dialer version 3.00.00. Sound is quite clear, but I don't have a comparison to stock either.

Regards

Ektus.
[Moto G5 ROMs, Kernels, Recoveries, & Other Develop] tablord:
I did in fact think about using opengapps (instead of microG) at least for testing purposes too. For now I will probably start playing around with the dialer permissions, then maybe try another (stock) dialer and eventually flash opengapps as a last resort. Or is it possible to update or replace the DialerFramework without flashing a whole gapps package?

Regarding your self built LineageOS 15.1: Do you still have the "well known" issues (MTP USB just working PC -> G5 & Encryption fails) with your build?
[Moto G5 ROMs, Kernels, Recoveries, & Other Develop] tablord:
Thanks for the info. I will give it a shot if all other measures fail.
[Moto G5 ROMs, Kernels, Recoveries, & Other Develop] staffe:
Not tested it myself but there's a Magisk module you can try:

https://xdaforums.com/apps/magisk/module-google-dialer-t3530916

Copying files from PC to Phone works for me.

Copying files from Phone to PC however does not. I use this very rarely so i just boot into TWRP for that.

I first have to fully charge my G5 to test encryption but if it doesn't work i think it's more likely a TWRP issue.

EDIT: Encryption is working fine with TWRP 3.2.1 provided by CodeZero (ARM64)
[Moto G5 ROMs, Kernels, Recoveries, & Other Develop] TheFixItMan:
Encryption would be a twrp issue

It's fully working in my official build with lineageos 14.1 but obviously you need the unofficial 64bit version if using lineageos 15.1

I no longer own this device but if someone wants to use my source code to build a 64bit version feel free

I'm pretty sure encryption works on a 32bit build of lineageos 15 so I presume it was built using someone else's source code and not a fork of mine

Edit - I just looked at the device tree for I presume is the 64bit twrp and the way they have encryption is totally different from mine so basically what I would do is look at my device tree and everything under first commit merge into the 64bit tree

Just copy and paste the relivent missing files & then go through things like board config and change the paths to mine & anything else relating to my first commit

That may get encryption working on the 64bit twrp
[Moto G5 ROMs, Kernels, Recoveries, & Other Develop] Moorm@nn:
I built a new update with microg installed.

Unfortunately I am not allowed to post links yet. But If you are interested:

Android file host

File ID: 5862345805528067603

File name: lineage-14.1-20180806-UNOFFICIAL-cedric.zip

As this is my first build, I highly recommend to perform a full backup ;)

On my device it is working perfectly without wipe.
[Moto G5 ROMs, Kernels, Recoveries, & Other Develop] filipedonato:
Thank you for making this update available. I am downloading.
[Moto G5 ROMs, Kernels, Recoveries, & Other Develop] Moorm@nn:
Pleasure :)

Is it working on your devices as well as on mine?

If so, I could provide an update each month with the latest security patches. I am also thinking of including root directly.
[Moto G5 ROMs, Kernels, Recoveries, & Other Develop] fre@kadelle:
thank you [MENTION=9348228]Moorm@nn[/MENTION] for the build. Works perfectly after dirty flash.

I would suggest not to include root, so everyone can decide for himself.
[Moto G5 ROMs, Kernels, Recoveries, & Other Develop] Moorm@nn:
Thanks for the feedback :)

Regarding root: You could still decide whether or not to activate it under the developer options.
[Moto G5 ROMs, Kernels, Recoveries, & Other Develop] Will Rodrigues:
I install the rom normally, but the play store does not appear because? help me...
[Moto G5 ROMs, Kernels, Recoveries, & Other Develop] TheFixItMan:
Custom roms do not contain any Google apps because licensing forbids Google apps to be bundled with custom roms

You need to flash gapps - for this device & rom I suggest nano gapps

https://opengapps.org

Arm - 7.1 - nano

You need to flash gapps after you have flashed the rom zip so you may need to format data if the rom doesn't boot if you have already booted it
[Moto G5 ROMs, Kernels, Recoveries, & Other Develop] Will Rodrigues:
I give flash in the rom and in the gapps nano, but when the boot and I configure, when I go to the home screen does not appear the play store ...
[Moto G5 ROMs, Kernels, Recoveries, & Other Develop] TheFixItMan:
If flashed correctly in twrp - it will be in the app draw of your launcher

Correct process

In twrp

Format system data cache

Install rom zip

Install gapps zip

Optional install root zip

Wipe cache/delvik art

All I can say about this is there's a user error somewhere
[Moto G5 ROMs, Kernels, Recoveries, & Other Develop] Moorm@nn:
Dear all,

I moved to lineage 15.1 so I will no longer build for 14.1.

Except the video recording everything works fine for me with 15.1.

Cheers

Moorm@nn
[Moto G5 ROMs, Kernels, Recoveries, & Other Develop] wzedlare:
New build with August security patch is up! :)

https://drive.google.com/file/d/1509KZQxxmKkT8V5dMDgnr8GvLY73tz2y/view
[Moto G5 ROMs, Kernels, Recoveries, & Other Develop] tjMF6:
Great!! Thank you very much! :good::cool:
[Moto G5 ROMs, Kernels, Recoveries, & Other Develop] filipedonato:
Thank you! This rom is great.
[Moto G5 ROMs, Kernels, Recoveries, & Other Develop] mdlgpt:
Hey folks! Im coming from stock nougat, made root, twrp, everything works fine, unless VoLTE. My carrier supports, because when i was in stock, volte was working OK. In *#*#4636#*#*, The key to turn on volte provisioning is greyed. AnY help?

Screenshot is attached.