yashsingh1/xdaforums huggingface dataset:
[Moto G5 ROMs, Kernels, Recoveries, & Other Develop] TheFixItMan:
They must be busy - iv no idea how long it takes - I know the moto g4 lte took a year or two to get official support but this device has been much quicker to support im guessing because its not a dramatic leap from the g4

All you can do is wait

---------- Post added at 06:59 PM ---------- Previous post was at 06:54 PM ----------

No problems downloading it here

I would do as it suggests -

use google chrome

Get yourself a mega account if you dont already have one (its free)

use the mega sync (iv got it running on windows 10 and ubuntu and it works great for syncing everything you put in the sync folder and downloading too)

Check that mega is not blocked in your country - works fine in the uk
[Moto G5 ROMs, Kernels, Recoveries, & Other Develop] b.zill:
Thanks, but this is not an option here, would need straight and web standards compliant download.
[Moto G5 ROMs, Kernels, Recoveries, & Other Develop] TheFixItMan:
Like I said works totally fine on my laptop with direct to pc download or using the mega sync - so looking at the errors its your laptop - out of memory suggests you are using a low end computer that cant handle the large temp file

Nothing else I can suggest other than using a different browser as its not the link or mega that is the issue here
[Moto G5 ROMs, Kernels, Recoveries, & Other Develop] b.zill:
It is server error messages, not on client side, probably due to poor coding of the non-standard JavaScript download handler. Enough space here and working with the web all day.
[Moto G5 ROMs, Kernels, Recoveries, & Other Develop] andyro2008:
Did you read before answering? Using the expanded desktop does not disable the navbar permanently. It will reappear when you open the keyboard, and also takes time to disappear, temporarily blocking access to a part of the screen while it is floating over.

qemu.hw.mainkeys=1 disabled it totally. I'm missing that. Which by the way is the original factory designed behavior of the navbar in the Moto G5.

[MENTION=6810779]wzedlare[/MENTION] I hope that you have time of reading this.

Enviado desde mi Moto G5 mediante Tapatalk

---------- Post added at 09:53 PM ---------- Previous post was at 09:37 PM ----------

[/COLOR [MENTION=6810779]wzedlare[/MENTION] If you look at the bottom of the screenshots, you will notice that the navigation bar remains visible for a while after using the keyboard. Blocking access to various buttons, icons, in multiple apps. It should be disabled completely or it should fade immediately after hiding the keyboard.

Enviado desde mi Moto G5 mediante Tapatalk
[Moto G5 ROMs, Kernels, Recoveries, & Other Develop] Fedray:
Expanded desktop works that way, there is nothing to change there. The only way is to completely disable the nav bar.
[Moto G5 ROMs, Kernels, Recoveries, & Other Develop] andyro2008:
That is what I want but qemu.hw.mainkeys=1 is not working anymore. So I can't disable the navbar completely like could in previous builds.

In short I'm asking to the dev to enable again the ability to disable the navbar via build.prop as in past builds.

I was explaining to [MENTION=4728903]TheFixItMan[/MENTION] why expanded desktop can't replace qemu.hw.mainkeys=1. effectively.

I know what is expanded desktop, how it works, but I'm talking about a different thing. I wasn't talking about expanded desktop, [MENTION=4728903]TheFixItMan[/MENTION] was.

So, stop nagging about expanded desktop and please read before answering. I don't want to be rude, but my English is limited and I want to be categorical about that. Imagine my words in a kindly manner.

Anyway, thanks for your answer. And sorry about my harsh language.

Enviado desde mi Moto G5 mediante Tapatalk
[Moto G5 ROMs, Kernels, Recoveries, & Other Develop] m_vaisakh:
The camera breaks (stops working) when you put in the line qemu.hw.mainkeys=1. We're working on the issue, and if it gets fixed a new build will be released.
[Moto G5 ROMs, Kernels, Recoveries, & Other Develop] mtthws01:
Someone can tell if the navigation with fingerprint is working?
[Moto G5 ROMs, Kernels, Recoveries, & Other Develop] m_vaisakh:
It is working in all the ROMs.
[Moto G5 ROMs, Kernels, Recoveries, & Other Develop] andyro2008:
So the dev has disabled it, to keep people from stumbling with the camera problem over and over again.

Thanks for your answer and your work!

Enviado desde mi Moto G5 mediante Tapatalk
[Moto G5 ROMs, Kernels, Recoveries, & Other Develop] m_vaisakh:
The bug has been fixed. Dev will soon release the build.
[Moto G5 ROMs, Kernels, Recoveries, & Other Develop] andyro2008:
Wow I wasn't expecting it so fast. Thanks for your help and thanks to [MENTION=6810779]wzedlare[/MENTION]

Enviado desde mi Moto G5 mediante Tapatalk
[Moto G5 ROMs, Kernels, Recoveries, & Other Develop] olekvanbolek:
Thanks for adding the moto gestures. :) finally able to lock the device via fingerprint sensor again. Nice.
[Moto G5 ROMs, Kernels, Recoveries, & Other Develop] benkybenkyo:
Some issues with root

Hi guys, this is my first post on XDA. I'd like to thank wzedlare for building this ROM, and also everyone who contributed to making it better!

As mentioned before there seems to be a problem with root sometimes. I've installed lineage-14.1-20170811-UNOFFICIAL-cedric.zip on my XT1676 (3 GB RAM, 16 GB storage) and rooted it with addonsu-14.1-arm-signed.zip according to TheFixItMan's instructions.

Now AdAway has no problem writing the hosts file, I was able to delete system apps with OpenAPK and I can browse the full file system with Total Commander and add/remove/rename files.

However, when using Greenify as root, it will tell me something like "Hibernating app X failed" most of the time, and when configuring the Yalp Store to install packages using the root method, it says "Could not install".

andyro2008 said ‘I think it's related to some weird segmentation fault errors’. Now I don't know what those mean, but when running pm in an adb shell I sure get them. When I keep trying, 1 out of 10 or 20 times pm will actually work, but most of the times it just returns "Segmentation fault". Same for am. I found out about this because I wanted to run a pm and an am command to enable something in Greenify now running in non-root mode (since root mode didn't work).

So what can be done to fix this? Should I provide some log files or something? Run some tests? Please let me know!
[Moto G5 ROMs, Kernels, Recoveries, & Other Develop] TheFixItMan:
Im using greenify with no problems

If I get su can't mount errors when trying to mount system just restart phone - normally happens if you switch from no root to root in dev settings so after you have enabled root restart phone

As for the other app I don't know as Iv not used it

Some apps require a specific super to run eg supersu - which you can flash - Just make sure to remove the inbuilt root to avoid conflict
[Moto G5 ROMs, Kernels, Recoveries, & Other Develop] andyro2008:
My post will be long, but I will try to explain the problem in detail to help the dev.

The segmentation fault error occurs even before rooting the device after a clean flash. I noticed it trying to grant permission to a non root app (SecureTasks, AutoTools and ForceDoze). Permissions like WRITE_SECURE_SETTINGS, READ_LOGS, DUMP and CHANGE_CONFIGURATION should be granted to an app trough ADB command "pm grant" in any NON-rooted device.

As [MENTION=8497272]benkybenkyo[/MENTION] reported, inputting "pm" or "settings" multiples times in the terminal will eventually work. (1/20 times). I attached a screenshot of it, please take a look of it [MENTION=6810779]wzedlare[/MENTION]

Apps like Disable Services, Link2SD and Titanium Backup needs the "pm" command combined with root access to freeze, unfreeze, apps and services.(Because of that I tough initially that it was a root related problem). And apps like Greenify and Servicely needs the PM to force stop the background apps. Consistently, if you hit the button freeze, or Greenify multiple times it will eventually work.

The segmentation fault error is also affecting the command "settings", used by apps like ForceDoze, NapTime to change the doze settings. The will not output any error, and you will think that it worked, but if you reopen the app, you will notice that the settings is unchanged (looks they are not programmed to handle the error).

You will notice the same behavior in any app that depends of commands of these kind. By example trying to freeze an app in Titanium backup pro or Link2SD will work after hitting repeatedly "freeze".

If you look carefully this thread there are more people complaining about problems related to the apps mentioned. By the way, I tried everything, Wiping everything, reinstalling everything, root trough SuperSu, Magisk 11.6/13, SU add-on (clean install after trying each one), changing the BusyBox, enabling disabling ADB, using non-root mode of certains apps. So far nothing worked.

It's a logcat after trying multiple times the command PM: http://cloud.tapatalk.com/s/59...279dd2/2017-07-25-12-12-33.txt

Enviado desde mi Moto G5 mediante Tapatalk
[Moto G5 ROMs, Kernels, Recoveries, & Other Develop] TheFixItMan:
[MENTION=6810779]wzedlare[/MENTION]

The reason magisk doesn't flash on this device is because f2fs is outdated

There are two options

1- use the cache partition instead

2- update f2fs

Would it be possible for you to update the kernel sources so a later version of f2fs works on lineageos
[Moto G5 ROMs, Kernels, Recoveries, & Other Develop] wzedlare:
It seems like su(root) can not get enough memory to work.Any ideas to fix?
[Moto G5 ROMs, Kernels, Recoveries, & Other Develop] andyro2008:
To take root out of the equation, I disabled the root access and tried a command that should work without root. Now the error is a bit different, "zygote" appears to be the process crashing.

08-24 08:04:21.449 560 560 F libc : Fatal signal 11 (SIGSEGV), code 1, fault addr 0x9c in tid 560 (zygote)

I tried a long list of adb/shell commands, most seem to work exept "pm", "am", "settings", "backup".

The problem does not seem to be when performing an action. For example I can open applications normally on my phone, but when I try to open an application through adb with "am start" the segmentation fault error appears.

Do all those commands have something in common? 3 of them are at least package related (pm, am and backup).

Sorry im not a Dev so i cant help in the fix :( Infinite thanks for your time!

It´s the logcat of the error:

https://drive.google.com/file/d/0B_0j4xu8tnkJN3RWVUMxQWN5Qlk/view?usp=sharing
[Moto G5 ROMs, Kernels, Recoveries, & Other Develop] the_clapper:
Hi all,

great job :good:. Just got my moto g5 a few days ago, tested it and decided to keep it. As I am also new to installing custom ROMs, do the above installation steps refer to TWRP? So install TWRP and boot to that, then choose wipe data inside TWRP?

Thank you
[Moto G5 ROMs, Kernels, Recoveries, & Other Develop] TheFixItMan:
yes - install twrp

if first time booting into twrp then format data to make it mountable (our twrp does not support data encryption) than restart back into twrp

goto wipe

advanced wipe

wipe delvik/art cache - system - data - cache

install

select rom zip

install

select arm 7.1 nano gapps from http://opengapps.org/

install

select suaddon zip

wipe delvik/art cache

restart
[Moto G5 ROMs, Kernels, Recoveries, & Other Develop] the_clapper:
thank you very much for the details. Why not pico gapps, would be even less g to start with?
[Moto G5 ROMs, Kernels, Recoveries, & Other Develop] TheFixItMan:
iv answered this before

because if you use pico apps you won't get some google services eg the use of "ok google" and the following

Face Detection for Media, Face Unlock

off-line speech files

Device Health Services

Google Search

Its your choice but I use nano as it gives all the google services that you need whilst not installing all the apps into system you can download from the playstore
[Moto G5 ROMs, Kernels, Recoveries, & Other Develop] the_clapper:
thank you. So it is personal preference, not a dependency for the ROM.
[Moto G5 ROMs, Kernels, Recoveries, & Other Develop] TheFixItMan:
Indeed
[Moto G5 ROMs, Kernels, Recoveries, & Other Develop] Ray-Ven:
encryption problem with twrp

Thank you for porting lineageos to moto g5 cedric! I really like it!

Unfortunately, with encryption enabled I cannot mount data partition in twrp - password is not accepted, while it is in lineageos. I know that this isn't a lineageos problem, but probably someone can give me a hint?

Thx, Ray
[Moto G5 ROMs, Kernels, Recoveries, & Other Develop] infixremix:
Lol this isn't a port reflash twrp and wipe data straight away
[Moto G5 ROMs, Kernels, Recoveries, & Other Develop] TheFixItMan:
our twrp recovery does not support encryption - do not encrypt if you want to use twrp

you will have to format data to use it unencrypted
[Moto G5 ROMs, Kernels, Recoveries, & Other Develop] wzedlare:
If you guys want it, I can disable encryption of los so that you won't have any data problem with twrp in the future?
[Moto G5 ROMs, Kernels, Recoveries, & Other Develop] TheFixItMan:
wouldn't it be better to compile a twrp to the latest version and see if it fixes encryption?

also updating the f2fs in the kernel source

It does warn on the twrp thread for this device that encryption is not supported and that you need to wipe data to decrypt but people just don't read

I would leave the option for encryption enabled in case someone wants to build a new recovery/kernel to test in future
[Moto G5 ROMs, Kernels, Recoveries, & Other Develop] blackfurball:
Yeah, better leave it in there. I'd rather don't use TWRP then leave /data unencrypted.
[Moto G5 ROMs, Kernels, Recoveries, & Other Develop] andyro2008:
I prefer the encryption, it's a deal breaker for me. I live in a very insecure country. Phones are stolen everyday, and the data unencrypted is a dangerous problem.

A workaround is creating a titanium Backup, taking the backup out of the cell, and later restoring it. Now the phone is unencrypted with minimal data loss. Flashfire would be an optimal workaround but it isn't working.

Enviado desde mi Moto G5 mediante Tapatalk
[Moto G5 ROMs, Kernels, Recoveries, & Other Develop] TheFixItMan:
Flashfire does work but you need to use supersu as your superuser or with the latest version of the Flashfire app you can use lineageos inbuilt superuser (the suaddon zip) but you will need to set selinux mode to permissive (there are apps that can do this)
[Moto G5 ROMs, Kernels, Recoveries, & Other Develop] andyro2008:
It don't work for me. I don't understand where is the difference :(

With su Add-on, and permisive mode it gets stuck on "getting root access" after asking for root permission successfully.

And I can't flash SuperSu, i get and error when it's writing the ramdisk.

Enviado desde mi Moto G5 mediante Tapatalk
[Moto G5 ROMs, Kernels, Recoveries, & Other Develop] TheFixItMan:
Well are you using the inbuilt Linageos superuser and if yes have you set selinux to permissive

If no then you will get stuck on the obtaining superuser screen

If you have set selinux to permissive it will show in about phone see my screenshot

Can't give you anymore help with this as you have the answer
[Moto G5 ROMs, Kernels, Recoveries, & Other Develop] andyro2008:
Yes, im using Lineage SU add-on, and yed Selinux IS in permissive mode. However flashfire still gets stuck in acquiring root access.

(Permisivo is Permissive in Spanish). Any extra ideas?

About SuperSu. Have you installed it sucefully? Any version en especial? At least the least one can't extract the ramdisk.

Enviado desde mi Moto G5 mediante Tapatalk
[Moto G5 ROMs, Kernels, Recoveries, & Other Develop] TheFixItMan:
And I assume you have enabled root & adb in dev settings cause it works fine for me

This is the screen I get when starting flashfire using LineageOS su & selinux set to permissive

If you want supersu then flash the Linageos su uninstall zip (available on lineageos website under addons) Then flash the supersu zip from supersu website
[Moto G5 ROMs, Kernels, Recoveries, & Other Develop] andyro2008:
Yes, I had root and ADB enabled. Also I flashed supersu.zip in a clean LineageOS install. The last version and the 2.78 version just to try. Nothing worked.

I ran out of ideas, thanks for your attention. Any other clue?

Enviado desde mi Moto G5 mediante Tapatalk
[Moto G5 ROMs, Kernels, Recoveries, & Other Develop] too_many_accounts:
Hi wzedlare,

Sorry to bother you, but do you have any updates regarding the following bug?

Cheers,

t_m_a.
[Moto G5 ROMs, Kernels, Recoveries, & Other Develop] NM99:
I currently have the 20170706 version of this ROM... should I dirty flash a new version? If yes, how do I dirty flash?
[Moto G5 ROMs, Kernels, Recoveries, & Other Develop] TheFixItMan:
go into twrp

select install

select latest rom zip file

wipe cache from option after zip has flashed

restart

done
[Moto G5 ROMs, Kernels, Recoveries, & Other Develop] NM99:
Damn, you're always at it. Thanks once again!
[Moto G5 ROMs, Kernels, Recoveries, & Other Develop] :
I have two questions about this Lineage ROM. first one is will you be updating this to android Oero? The second one is how fast are you with updating this ROM? Thanks in advance!
[Moto G5 ROMs, Kernels, Recoveries, & Other Develop] TheFixItMan:
1 - lineageos hasn't even updated its sources to oreo

2 - as fast as a tiger but not as fast as a cheetah

please note - ask silly questions you get silly answers

go look at the xda rules
[Moto G5 ROMs, Kernels, Recoveries, & Other Develop] :
Okay thanks dude!?

---------- Post added at 11:33 PM ---------- Previous post was at 11:30 PM ----------

I was just wondering if the guy who made this was up to the job of updating this it Android Oreo. There's no reason to be like that!
[Moto G5 ROMs, Kernels, Recoveries, & Other Develop] TheFixItMan:
Like I said - sources are not currently available so right at this moment in time the answer is no

When Linageos update their sources maybe but it will be much easier when Motorola update their sources (less work)

Now please follow the rules & stop asking for updates - people do this in their own time & if everyone keeps going when is xyz update coming or are going to get xyz then think how much spam this thread will contain & I don't like spam - I'm more of a ham person

The reason I'm like this is because of the countless threads people are creating about updates or lack of
[Moto G5 ROMs, Kernels, Recoveries, & Other Develop] :
Okay thank you. I haven't seen the rules yet. Sorry
[Moto G5 ROMs, Kernels, Recoveries, & Other Develop] andyro2008:
Finally, I made it work!. The trick was closing and reopening Flashfire until it gets root without it crashing. It isn't a perfect solution but I is very useful.

Creating a backup with Flashfire, and restoring it with TWRP is a great way to decrypt your device. Thanks for your help.

Enviado desde mi Moto G5 mediante Tapatalk
[Moto G5 ROMs, Kernels, Recoveries, & Other Develop] olekvanbolek:
The gallery app occasionally crashes, so that you can't watch videos or gifs. Is there a fix? Restarting the phone also works, but is kind of annoying.
[Moto G5 ROMs, Kernels, Recoveries, & Other Develop] :
One problem the navigation buttons stay after turning on fingerprint gestures!? Please fix!
[Moto G5 ROMs, Kernels, Recoveries, & Other Develop] TheFixItMan:
just use quickpic (playstore)

the stock gallery app has never worked properly in any phone iv ever used
[Moto G5 ROMs, Kernels, Recoveries, & Other Develop] TheFixItMan:
enable expanded desktop from the display settings

note that nav bar will appear when keyboard is showing - this is how android works and is not a bug
[Moto G5 ROMs, Kernels, Recoveries, & Other Develop] :
Okay thank you
[Moto G5 ROMs, Kernels, Recoveries, & Other Develop] raulillo88:
How is battery life with this rom. I've recieved the phone today and I'm in doubt if go with stock rom or install lineage OS. How is your experience? Thanks in advance
[Moto G5 ROMs, Kernels, Recoveries, & Other Develop] TheFixItMan:
battery life depends what you do with it

If you sit and play games on it for a few hours it wont last long

if you have the screen off all the time it will last days

in other words with average use it will last an average amount of time and there are no issues
[Moto G5 ROMs, Kernels, Recoveries, & Other Develop] raulillo88:
I already knew that. my question is if battery life is better than stock or worst.
[Moto G5 ROMs, Kernels, Recoveries, & Other Develop] TheFixItMan:
I would say no difference (it uses the same kernel as stock I believe with little modification) but again its subjective
[Moto G5 ROMs, Kernels, Recoveries, & Other Develop] ektus:
I can't tell the difference because I switched to LineageOS the first day I got the phone :)

I can tell the pure GSM/LTE standby time approaches 2 weeks. That is with power safe mode on, location, mobile data and WiFi off and just let it sit there, only reachable for phone calls and SMS. Admittedly, that's not the intended use case for this type of phone, but anyway, it's possible :)

Regards

Ektus.
[Moto G5 ROMs, Kernels, Recoveries, & Other Develop] ektus:
LiveBoot?

Is there a way to get LiveBoot working on this ROM? It installs and acquires ROOT privileges, but the test run does nothing, it doesn't show up during boot and doesn't write a logfile either.

Any hints?

Regards

Ektus.
[Moto G5 ROMs, Kernels, Recoveries, & Other Develop] andyro2008:
Is your SeLinux in permissive mode? If the answer is yes:

Your problem is almost certainly related to what I described a few comments back. Several applications have problems to perform their functions because of an "Segmentation Fault" error when trying to execute certain commands.

If you repeat an action several times, it eventually works. Almost 1/30 times. By example Flashfire app if opened and closed enough times eventually will get root an will work. So far this pattern was repeated with all the applications that gave me kind of problem.

But I do not know how it would apply in this situation. Maybe if you reinstall the liveboot script enough times at some point it will work. Or it may work once every many reboots.

To confirm you can try pressing the test button multiple times very fast for a couple of minutes. If my suspicion is correct you will eventually see the test window.

Anyway, opening and closing an application or pressing a test button is fast compared to rebooting the phone, this workaround is probably not useful to you. It will be tedious to try.
[Moto G5 ROMs, Kernels, Recoveries, & Other Develop] m2habert:
Sorry if I'm totally off-base here, but ¿is there any chance of the "seg fault" error being related to the following:

https://www.xda-developers.com/psa-...broke-titanium-backup-substratum-heres-a-fix/ ?
[Moto G5 ROMs, Kernels, Recoveries, & Other Develop] andyro2008:
It successfully fixed the Titanium Backup app restoring problem, but it still can't freeze apps. Which makes sense, because it depends on the pm command, which still fails, just like the rest of the applications.

In other words, the Titanium problem when restoring applications was not related to the Segmentation fault error And it can be fixed with the steps mentioned in the page that you shared.

However the rest of the applications affected by the error "Segmentation Fault" (like Flashfire, LiveBoot, Disable Service, Greenify, PM, AM, ADB backup commands, Freezing apps ) doesn't got fixed with this and the are generating the same error as always.

So they are two totally different issues.
[Moto G5 ROMs, Kernels, Recoveries, & Other Develop] TheFixItMan:
The strange thing is I don't have any issue with any of those things

If I type pm in terminal it works every time

Greenify works perfectly

Flashfire opens up without problems every time

I can freeze an app without error every time (I used link2sd)

Then I downloaded & tried with titanium backup - again froze an app first time no errors
[Moto G5 ROMs, Kernels, Recoveries, & Other Develop] hop01:
I have also the "seg fault" error with this rom
[Moto G5 ROMs, Kernels, Recoveries, & Other Develop] CodeZero:
just got Oreo booted on our beloved Moto G5