yashsingh1/xdaforums huggingface dataset:
[Android General] flipmode_11:
Is this the same project as photo attached??

What do you mean by ""This application should NOT - I REPEAT SHOULD NOT be run on a computer that can be directly accessed outside of the local network."" ???

Why would you not have the computer connected to WIFI? Is this a licencing issue?

I cannot understand why no one adjusts the name slightly when reviving these projects (e.g. adbGUI v2 OR.... adbGUI for MAC, etc).

So Linux only support??

EDIT: Looks like the project is now "ADBWUI" @ https://github.com/mitchellurgero/ADBWUI
[Android General] sandix:
This project is stale. I wouldn't use it. The warning is there because it runs a webserver without any authentication for the UI. This project runs on NodeJS - so supports any OS that supports node.
[Sony Xperia XZ Premium Questions & Answers] filiii:
I'can't connect to wifi of my university. Wifi is protected from peap 802.1x. I'used the same setting on my friend's smartphone and wifi worked, someone have a solution? Sorry for bad english
[P8lite Q&A, Help & Troubleshooting] Vincent00z51:
Can Any One Help Me how To make My Phone Support OTG !!?
[P8lite Q&A, Help & Troubleshooting] XTutorials:
This phone doesn't support OTG
[P8lite Q&A, Help & Troubleshooting] Vincent00z51:
I know that this phone doesn't support Otg

But i want to make my phone support. Otg .. !
[P8lite Q&A, Help & Troubleshooting] persona78:
Just can´t! No hardware support on tthis device.

.
[P8lite Q&A, Help & Troubleshooting] HoldMySoul69:
In Build prop i found otg.test or smth and key was false I changed it to true and now I can connect my mouse and works well
[P8lite Q&A, Help & Troubleshooting] XTutorials:
WHAT?! :cool:
[P8lite Q&A, Help & Troubleshooting] persona78:
Just can't be... There is no power on usb to activate mouse, keyboard, whatever...

Doesn't work on TWRP to.

.
[P8lite Q&A, Help & Troubleshooting] PeJe80:
I have enabled the function otg.test in the build.prop, no otg support here. checked with usb stick and mouse.

our phone dus not support otg.
[P8lite Q&A, Help & Troubleshooting] ScarySquirrel18:
This caused me a bootloop! Don't try it
[Networking] UAxDEATH:
Hi all,

I'm always being shy to post, but this is an amazing place for information, this time i couldn't find anything that I was looking for so here it is the question:

- I have bought LG v30 from South Korea unlocked 128gb phone

- its recognize Verizon sim card

- 4LTE internet is working

- text messages or voice phone calling is not working, if something else is calling me it goes to voice mail.

I have called to Verizon tech support they told me that they cant enter manually the IMEI address since such phone doesn't exist yet in they data base.

Dear community,

I'm asking for help or guidance - what can I do to make this amazing phone working. I own a business so its very sensitive for me to receive phone calls or txt messages.

PS my previous phone LG V20 got completely ****ed up on construction site.

THANK YOU
[Networking] Guyinlaca:
In order for a phone to work reliably on Verizon it must have LTE Band 13. I'd imagine the Korean version does NOT support Band 13. Most phones support Band 4, which Verizon sometimes uses, but without 13, you're out of luck in most places. I'd either wait for the unlocked American V30 or get the Verizon branded one.
[Networking] mrbidjey:
I suggest you take a look at the video in that link below. Although it is for the Note 8 Unlock version but you never know.

https://youtu.be/W9EEbYHWD40
[Moto G5 Guides, News, & Discussion] andyro2008:
The Segmentation Fault error is fixed on LineageOS. It will be fixed progressively in any other ROM in the upcoming updates.

Infinite thanks to [MENTION=6810779]wzedlare[/MENTION], and the other persons and devs that helped us. Im gonna request to mods to close this thread

And over again thanks to all! I'm so happy now!
[Moto G5 Guides, News, & Discussion] mrfrantastic:
Great thread! My device is also affected and matches the mentioned specs.
[Moto G5 Guides, News, & Discussion] ektus:
I've got the recommended LineageSU method installed but normally don't use ADB. The only application I did try to use is Liveboot, where the test mode fails to start quite often. Transferring files via USB won't work on the first try, but I don't know how to tell if that is related. My device also is the European G5 with triple slot, 16GB and removable battery, type XT1676 or M2675. Currently running the unofficial LineageOS 14.1 build by [MENTION=6810779]wzedlare[/MENTION] from August, 2017.
[Moto G5 Guides, News, & Discussion] andyro2008:
The easiest way to check if a problem is caused by the segmentation fault is open a terminal emulator session (you can install any terminal emulator from the Playstore), and write:

su

logcat | grep "signal 11 (SIGSEGV)"

It will filter the logcat showing the Segmentation Fault errors. If you get new errors when performing an certain action, or opening certain app, it's affected by the error.

Enviado desde mi Moto G5 mediante Tapatalk
[Moto G5 Guides, News, & Discussion] ektus:
That one shows quite a number of results, at a first glance most with

signal 11 (SIGSEGV), code 1 (SEGV_MAPPER), fault addr 0x9c in tid xxxxx (zygote)

and one of each with

(app_process)

and

(Downloadmanager)

The fault addr is always the same except for the Downloadmanager where it's

code 2 (SEGV_ACCERR), fault addr 0x200006464

.

Regards

Ektus.
[Moto G5 Guides, News, & Discussion] floydburgermcdahm:
Just for reference and to add to the discussion started in the Moto G5 TWRP thread, I never had any such issuess. My model is the 3GB dual sim version, bought at Amazon Germany. LineageOS with root addon.
[Moto G5 Guides, News, & Discussion] mrfrantastic:
Don't know if it is of importance but it never got to boot a clean system with changed filesystem. Tried to change /data to ext4, also tried it with /system as f2fs but nothing worked. This also happened with the new TWRP 3.1.1.

I also tried to flash phh supersu with noverity. But could only boot to bootloader which gave me an error.

Just wanted to share my attempts. I have limited knowledge of the fundamentals of segmentation so I just tried whatever I could find.
[Moto G5 Guides, News, & Discussion] andyro2008:
F***! what will be the difference between your device and mine?

Did you ever use the rooted stock ROM?

Can you please, share these numbers from the sticker behind your battery, to know your exact device variant:

Thanks for your help!

Enviado desde mi Moto G5 mediante Tapatalk
[Moto G5 Guides, News, & Discussion] andyro2008:
Anyone affected with segmentation fault error, o with a device with Dual SIM, please share these numbers.

A picture is not necessary, just the numbers. It's behind the battery

Enviado desde mi Moto G5 mediante Tapatalk
[Moto G5 Guides, News, & Discussion] mrfrantastic:
Here is mine.

Edit: if picture is too small, it is the same phone as yours...
[Moto G5 Guides, News, & Discussion] TheFixItMan:
Just for reference my phone doesn't have any issues with root function

XT1675

2+16gb

All other numbers are the same

The FCC ID is the registration code for the United States

Federal Communications Commission

First three letters are grantee code - the rest is product code

I think the type relates to the battery size
[Moto G5 Guides, News, & Discussion] andyro2008:
Let's see if [MENTION=8009781]floydburgermcdahm[/MENTION] has exactly the same device. Perhaps there is more than one 3gb Dual SIM Variant.

Enviado desde mi Moto G5 mediante Tapatalk
[Moto G5 Guides, News, & Discussion] floydburgermcdahm:
Mine is: XT1676, 3+16GB, FCC ID: IHDT56VF4, Type: M2675

So, no idea what the difference between our devices might be. :( I did use the stock ROM briefly, but never rooted it. Went straight to LOS with root addon.

Yeah and thanks for reminding me that the bloody case is a ***** to open! :p :D
[Moto G5 Guides, News, & Discussion] mrfrantastic:
So if you type "pm" in a terminal you don't get a segmentation fault?
[Moto G5 Guides, News, & Discussion] andyro2008:
I tried a strace with the command "pm". Something of this can be useful? Can it be something related to libraries? Those "No such file or directory" are weird. The full log files, one from a successfull pm and another for a failed one, are attached. Thanks for your atention, i hope you could help us.

openat(AT_FDCWD, "/system/lib/libart.so", O_RDONLY|O_LARGEFILE) = 5
fstat64(5, {st_mode=0, st_size=1, ...}) = 0
read(5, "\177ELF\1\1\1\0\0\0\0\0\0\0\0\0\3\0(\0\1\0\0\0\0\0\0\0004\0\0\0"..., 4096) = 4096
_llseek(5, 5888928, [5888928], SEEK_SET) = 0
read(5, "\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0"..., 4096) = 1320
_llseek(5, 4584364, [4584364], SEEK_SET) = 0
read(5, "\0.symtab\0.strtab\0.shstrtab\0.inte"..., 4096) = 4096
_llseek(5, 4584348, [4584348], SEEK_SET) = 0
read(5, "libart.so\0\0\0\21\r\350\370\0.symtab\0.strtab"..., 4096) = 4096
close(5) = 0
openat(AT_FDCWD, "/system/lib/.debug/libart.so", O_RDONLY|O_LARGEFILE) = -1 ENOENT (No such file or directory)
openat(AT_FDCWD, "/usr/lib/debug/system/lib/libart.so", O_RDONLY|O_LARGEFILE) = -1 ENOENT (No such file or directory)
clock_gettime(CLOCK_MONOTONIC, {7390, 135831818}) = 0
openat(AT_FDCWD, "/system/lib/libandroid_runtime.so", O_RDONLY|O_LARGEFILE) = 5
fstat64(5, {st_mode=0, st_size=1, ...}) = 0
mmap2(NULL, 1075276, PROT_READ, MAP_PRIVATE, 5, 0) = 0xaaada000
close(5) = 0
openat(AT_FDCWD, "/system/lib/libandroid_runtime.so", O_RDONLY|O_LARGEFILE) = 5
fstat64(5, {st_mode=0, st_size=1, ...}) = 0
read(5, "\177ELF\1\1\1\0\0\0\0\0\0\0\0\0\3\0(\0\1\0\0\0\0\0\0\0004\0\0\0"..., 4096) = 4096
_llseek(5, 1074116, [1074116], SEEK_SET) = 0
read(5, "\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0"..., 4096) = 1160
_llseek(5, 1073810, [1073810], SEEK_SET) = 0
read(5, "\0.shstrtab\0.interp\0.note.android"..., 4096) = 1466
_llseek(5, 1073782, [1073782], SEEK_SET) = 0
read(5, "libandroid_runtime.so\0\0\0o\223i\206\0.sh"..., 4096) = 1494
close(5) = 0
openat(AT_FDCWD, "/system/lib/libandroid_runtime.so", O_RDONLY|O_LARGEFILE) = 5
fstat64(5, {st_mode=0, st_size=1, ...}) = 0
read(5, "\177ELF\1\1\1\0\0\0\0\0\0\0\0\0\3\0(\0\1\0\0\0\0\0\0\0004\0\0\0"..., 4096) = 4096
_llseek(5, 1074116, [1074116], SEEK_SET) = 0
read(5, "\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0"..., 4096) = 1160
_llseek(5, 1073810, [1073810], SEEK_SET) = 0
read(5, "\0.shstrtab\0.interp\0.note.android"..., 4096) = 1466
_llseek(5, 1073782, [1073782], SEEK_SET) = 0
read(5, "libandroid_runtime.so\0\0\0o\223i\206\0.sh"..., 4096) = 1494
close(5) = 0
openat(AT_FDCWD, "/system/lib/.debug/libandroid_runtime.so", O_RDONLY|O_LARGEFILE) = -1 ENOENT (No such file or directory)
openat(AT_FDCWD, "/usr/lib/debug/system/lib/libandroid_runtime.so", O_RDONLY|O_LARGEFILE) = -1 ENOENT (No such file or directory)
openat(AT_FDCWD, "/system/bin/app_process32", O_RDONLY|O_LARGEFILE) = 5
fstat64(5, {st_mode=0, st_size=1, ...}) = 0
[Moto G5 Guides, News, & Discussion] andyro2008:
Sorry repeated post
[Moto G5 Guides, News, & Discussion] TheFixItMan:
Both them lib files are present in system/lib

I don't have any knowledge of coding to be of assistance
[Moto G5 Guides, News, & Discussion] floydburgermcdahm:
Nope.
[Moto G5 Guides, News, & Discussion] mrfrantastic:
Since we only have a very small number of affected devices it is obviously difficult to extrapolate general statements. But for now(!) it seems(!) that there are models which are not affected by the fault although they match (on first glance) OP's and my phone's specs. On the other hand there are (again: for now) only devices with above mentioned serial number affected by the fault.

Since we tried different ROMS with different sources could it be kernel related? I am assuming that all ROMS at least partially share the same kernel. And if so, how do we get someone to try to fix the kernel?

The next common denominator might be either TWRP or SU...
[Moto G5 Guides, News, & Discussion] andyro2008:
At least Xposed is NOT affected in any way by the Segmentation fault error, so you can use it without problem.

Enviado desde mi Moto G5 mediante Tapatalk
[Moto G5 Guides, News, & Discussion] andyro2008:
It could be the Kernel or the ROM. In the case of ROMs, although different ones, they shares large pieces of code.

SU is no the problem, pm, am, settings commands should be accessible even on unrooted devices, and the get the error even without root installed.

Enviado desde mi Moto G5 mediante Tapatalk
[Moto G5 Guides, News, & Discussion] mrfrantastic:
Is it? It did install it without a problem but amplify and greenify don't work with it. Might be because the modules are not yet up to date for Android N.

Edit: Amplify shows wakelocks if you set selinux mode to permissive :good:
[Moto G5 Guides, News, & Discussion] Katmando:
Hello everyone!

My G5 is also affected. Have bought it via Amazon Germany, too.

Also getting the same errors/behavior when typing 'pm' at the terminal.

Model: XT1676 3+16GB

FCC ID: IHDT56VF4

Type: M2675

Let me know if I can help with further information, but I have to state I'm not a developer but a user :)

KR

Katmando
[Moto G5 Guides, News, & Discussion] andyro2008:
From where country is your device from?

Enviado desde mi Moto G5 mediante Tapatalk
[Moto G5 Guides, News, & Discussion] floydburgermcdahm:
Germany
[Moto G5 Guides, News, & Discussion] icantlogin:
Hi, I'm using an XT1676 with 3 GB RAM and 16 GB of storage, bought in The Netherlands at a major Dutch smartphone webstore (not Amazon). It has dual SIM and a removable battery. It suffers from the segmentation fault bug.

For me the biggest problem this causes is not being able to use Greenify in root mode. Workaround: using Greenify in non-root mode works fine. I wish I could use it in root mode though.

I'd also like to be able to use a better root solution than the LineageOS built-in one. I mean, it works fine but I'd prefer more configuration options. Since I'm running AFWall+ which is constantly using root, I always have a # in my taskbar, so I can't see when a different process is using root. So I'd love to switch to SuperSU or Magisk or something, but I tried those and they didn't work. I think I even tried to install SuperSU just as the manager, after rooting with LineageOS SU, but it didn't work.

I was wondering if anyone else experiences extremely long boot times? Whenever I have to reboot my phone it takes up to five minutes, displaying the boot logo all this time. I imagine this is caused by a lot of segmentation faults and processes just retrying until they succeed.
[Moto G5 Guides, News, & Discussion] ektus:
Same here, but I don't know which boot time would be "normal".

I've just now posted a logcat in https://xdaforums.com/showpost.php?p=74315051&postcount=733

Regards

Ektus.
[Moto G5 Guides, News, & Discussion] icantlogin:
With stock ROM it was about 30 seconds for me. Previously I owned a Moto G from 2014 running CyanogenMod 13 which also booted in about 30 seconds I think.
[Moto G5 Guides, News, & Discussion] Rascjp:
I have exactly the same problem with the same phone bought from amazon UK.
[Moto G5 Guides, News, & Discussion] LambdaPerl:
I have this Segmentation Fault problem on a device bought from Motorola.co.uk.

It is the Dual SIM, 3GB RAM + 16GB Flash variant (don't have the model number atm but XT1676 sounds right).

Here is a logcat of a segmentation fault arising from the use of 'pm' command: hastebin . com /raw/idirubiwal

There were some other instances of this (during boot?), not explicitly caused by me, which had the same error message but I've only included the one I caused.

Happy to provide further information on request.

Edit: I should note that the first noticed effect of this was trying to execute termux-setup-storage in the excellent Termux app, which leads to a Segfault as it uses 'am'. Workaround: Spam the command about 25 times (using VolUp+W & Enter to repeat the command) until it works / doesn't give Segfault.
[Moto G5 Guides, News, & Discussion] andyro2008:
You will find that the problem is with things that you can't spam an action.

By example Greenify, spamming hibernate all until all apps gets grenified will take lot of time and battery. Or with SuperSU and Magisk, both suffer from segfault every time that something ask for Root. So yo need to spam every Root session.

(That is the reason that Magisk or SuperSU will not work on our devices until someone fixes the problem, and if you want Root, yo will be forced to stay in a room that uses LineageOS SU)

Enviado desde mi Moto G5 mediante Tapatalk
[Moto G5 Guides, News, & Discussion] LambdaPerl:
I'm not sure what Magisk or SuperSU offer above the LineageOS root, but I'm perfectly happy with LOS root... (Granted I think it's important that there should always be choice)

Anyway, aye, I can imagine there being issues with actions that aren't feasible to spam (and let's be honest, spamming an action 25 times before it works isn't incredibly elegant..).

I might do some digging into the issue myself but Android development/debugging is really out of my reach, and I'm not happy that I could probably mess up my device badly if I do something wrong. :eek:
[Moto G5 Guides, News, & Discussion] andyro2008:
The problem is that LOS root is not available for every ROM. By example in Resurrection Remix, or AOSP it will not work.

Enviado desde mi Moto G5 mediante Tapatalk
[Moto G5 Guides, News, & Discussion] infixremix:
If your this botherd swap ur file system to ex4 and magisk will pass and all the modules will work
[Moto G5 Guides, News, & Discussion] TheFixItMan:
doesnt work for me as if you format data to ext4 the phone asks for the decryption key on boot and no matter what you put it says cannot decrypt and tells you to format data

Even if the phone is not encrypted and you have no screen lock key it still asks for this

Anyway f2fs is far superior in terms of read/write speed so by formatting to ext4 you are decreasing the performance of your phone

Its better if someone with the knowledge can fix selinux on this device (kernel related) so magisk can work as intended
[Moto G5 Guides, News, & Discussion] infixremix:
It's nothing to do with selinux , F2fs is more updated than stock , nothing is so called broken it never worked in the first place . It's to do with magisk . I don't know what the problem is I have magisk 14.3 running root no problem . No Dev needs to fix . All it needs is upstreaming it might not even be F2fs it might be the same problem as pixel [MENTION=4728903]TheFixItMan[/MENTION]
[Moto G5 Guides, News, & Discussion] TheFixItMan:
indeed magisk runs with root no problems on f2fs - but magisk hide doesnt work which is caused by a permission denied due to selinux (at least that was the response I got on github)

Its not the version that is the issue - its the implementation
[Moto G5 Guides, News, & Discussion] infixremix:
Permission denied we are on enforcing unless you want a less secure device no Dev will change to persmivive , u can do it via terminal just Google see if that works like I said we're on enforcing changing to persmivive will make ur device less secure , yes version does matter magisk is updated to the latest kernel version , we're on 48 the latest is 78 . When you upstream it updates F2fs .
[Moto G5 Guides, News, & Discussion] TheFixItMan:
I know the difference between enforcing and permissive thanks

Its the implementation in this device (blame motorola) - magisk hide should work with enforcing

Like I said the kernel needs fixing
[Moto G5 Guides, News, & Discussion] andyro2008:
I'm not sure what you mean. The segmentation fault error present in the Cedric variant with 3gb of RAM is affecting any root method, including unrooted devices.

Commands like "am" or "pm" should run even without root. In addition, we never received a " permission denied" just a "segmentation fault" and a crash.

In the case of MagiskSU, like the PM and AM commands, it works in approximately 1/30 times that a process ask for Root. In the other 29 times we get the segmentation fault error, and the crash of zygote (it makes MagiskSU almost useless for us). It's random and not continuos.

On other Cedric's with 2GB of RAM, not affected by the segmentation fault, MagiskSU works perfectly. Even without touching the format of the filesystem.

By the way even with selinux enforcing disabled (I'm using AICP and SeLinux can be disabled trough the settings menu) the seg fault error is present. The error is present also in unrooted devices, in all the customs ROMs.

Further more, If you read the thread carefully, you will see that we already tried using EXT4 to solve the problem. It resulted in a dead end.

At this point, it is obvious that there is some problem in memory management in the 3gb devices, in a part of the code that all ROMs use equally. We need to stop denying the existence of the problem, and start looking for a solution.

I hope some developer takes their sparse time and helps us!!

Enviado desde mi Moto G5 mediante Tapatalk
[Moto G5 Guides, News, & Discussion] LambdaPerl:
Do we know if the errors are present in stock?
[Moto G5 Guides, News, & Discussion] icantlogin:
I haven't heard anyone talk about this segmentation fault occuring with the stock ROM.

I succesfully rooted stock with Magisk and used Greenify in root mode for more than a month. Both are things that don't work now that I'm using LineageOS, because of this segmentation fault.
[Moto G5 Guides, News, & Discussion] andyro2008:
Yes we know. The error is NOT present on stock ROMs. Only custom ROMs are affected. (I suspect that the error is in the source code released by Lenovo) and it only affects 3gb devices.

Enviado desde mi Moto G5 mediante Tapatalk
[Moto G5 Guides, News, & Discussion] TheFixItMan:
Have you tried comparing the kernels between the 2gb model and the 3gb model and see if there is any difference
[Moto G5 Guides, News, & Discussion] infixremix:
If you know so much fix it you self how can devs fix it when ur not doing anything to make it better , is get logs zygote is an error in every ROM causes no problem at all . Get logs or don't complain of a problem is you have logs add them to the op . or at least send as!

Edit : I need to read op didn't appear on phone sorry, but the point still is why not learn to fix ur self
[Moto G5 Guides, News, & Discussion] TheFixItMan:
I'll answer this

Because I have no knowledge (that's going to be of any use) of c++ or java & I have no intention of learning an entire programming language

We can probably work out what is causing it - but without very advanced programming language knowledge no one will be able to fix it and there doesn't look like that there is any advanced programmer who supports this device
[Moto G5 Guides, News, & Discussion] LambdaPerl:
Does this mean we can replace the kernel in non-stock with the stock kernel and work around the issue?

---------- Post added at 11:03 PM ---------- Previous post was at 11:02 PM ----------

Do you know where I can find a stock kernel for the 2GB model?
[Moto G5 Guides, News, & Discussion] TheFixItMan:
Very unlikely it will boot - I think this is the boot image see attachment
[Moto G5 Guides, News, & Discussion] LambdaPerl:
Thank you very much good sir.

Would you mind enlightening me with your reasoning for saying it's unlikely to boot? I'm quite curious.
[Moto G5 Guides, News, & Discussion] TheFixItMan:
Kernels for custom roms are normally modified in some way in order for them to boot the custom rom

I don't build kernels so I can't be more specific
[Moto G5 Guides, News, & Discussion] LambdaPerl:
I've unpacked the boot images and decompressed the kernels, there are indeed differences. The sizes are exactly the same, but a cursory glance with a binary diff tool (DHEX) shows:

Often (see screenshot for an idea of the frequency), a single byte will differ in the 3GB model, being exactly 2 less than the corresponding byte in the 2GB model kernel.

There are a few nybbles (much rarer) which differ more substantially than that.

N.B. I'm not saying the above 2 points have any substantial meaning to our investigation; they are merely remarks after spending a minute in a diff tool.

I'm going to have a more substantial look tomorrow, but it's getting late-ish here now.