yashsingh1/xdaforums huggingface dataset:
[Android Apps and Games] tliebeck:
No way to contact actual users. It does show individual crashes, but it's just a stack trace with a phone model and Android version.

I can actually see the Xposed crashes pretty readily...there tends to be an Xposed line in the stack trace, e.g. last line of this:

java.lang.RuntimeException:
at android.app.ActivityThread.performResumeActivity (ActivityThread.java:3535)
at android.app.ActivityThread.handleResumeActivity (ActivityThread.java:3575)
at android.app.ActivityThread.handleLaunchActivity (ActivityThread.java:2814)
at android.app.ActivityThread.-wrap12 (ActivityThread.java)
at android.app.ActivityThread$H.handleMessage (ActivityThread.java:1544)
at android.os.Handler.dispatchMessage (Handler.java:110)
at android.os.Looper.loop (Looper.java:203)
at android.app.ActivityThread.main (ActivityThread.java:6293)
at java.lang.reflect.Method.invoke (Method.java)
at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run (ZygoteInit.java:1084)
at com.android.internal.os.ZygoteInit.main (ZygoteInit.java:945)
at de.robv.android.xposed.XposedBridge.main (XposedBridge.java:102)

I need to get a device set-up with Xposed again.
[Android Apps and Games] tliebeck:
Thanks, also need to get Magisk set-up.

Have never tried it, as I'd rather be warned what about what uses SafetyNet so I can uninstall it. Not happy about the idea of apps that are intentionally designed to not work on free-as-in-freedom OSes. Happy it exists to make the point that SafetyNet is ineffective though.
[Android Apps and Games] GermainZ:
If it's just that last line that only indicates that Xposed is installed, it's not usually caused by Xposed or an Xposed module.
[Android Apps and Games] tliebeck:
The other data point on these though is that all reports shows Xposed as installed.

One of the crashes is a call to Activity.getApplication() that throws a ClassCastException when I try to cast it to the FX application class.
[Android Apps and Games] GeTex:
It might be one of my devices to be honest. Idk I'll have to look, I've got some crashy devices that everything dies from very bad rom programming.

Does it say what sdk the crash reports are from? Even a device build or something?
[Android Apps and Games] KaMyKaSii:
Hello, I'm running the latest beta on Marshmallow. After downloading a text file from XDA Forums (Labs), I click on the notification to open the file. Then I select the FX Text Viewer and then the app crash. It happens every time, here is the stack trace, I hope it helps

java.lang.NullPointerException: Attempt to invoke virtual method 'boolean java.lang.String.contains(java.lang.CharSequence)' on a null object reference
at android.content.ContentResolver.checkLeakDetectIgnoreList(ContentResolver.java:2695)
at android.content.ContentResolver.openTypedAssetFileDescriptor(ContentResolver.java:1178)
at android.content.ContentResolver.openAssetFileDescriptor(ContentResolver.java:958)
at android.content.ContentResolver.openInputStream(ContentResolver.java:678)
at nextapp.fx.ui.viewer.a.r(Unknown Source)
at nextapp.fx.ui.viewer.TextViewerActivity$3.run(Unknown Source)
at nextapp.maui.k.d.a(Unknown Source)
at nextapp.maui.k.d.run(Unknown Source)
[Android Apps and Games] tliebeck:
Thanks, have looked into it, and this turns out to be a bit of a confusing one. The obvious has been ruled out, FX is correctly checking for nulls here.

So I went and looked at the Android source code to see what the crash is all about, and that top method, "checkLeakDetectIgnoreList()" doesn't actually exist in the stock Marshmallow source.

Can you tell me what you're using to download the text file from XDA labs, and which text file you're downloading so I try to recreate this here? Also what device/ROM?

Thanks again for reporting!
[Android Apps and Games] KaMyKaSii:
I'm using the default download manager (com.android.providers.downloads), but I just realized that opening the file by the Android's own file manager (com.android.documentsui), through Settings > Storage > Internal Storage > Explore also causes the same crash. Opening the same file through another app like ZArchiver works normally

The text attached in the post below:

https://xdaforums.com/general/paid-software/flashfire-t3075433/post73791195

Quantum Go 4g running Marshmallow 6.0 almost pure, but have some modifications of Mediatek. You should not know, because it only sells in the Brazilian market. Below is the official website link. And if you want to take a look at my rom files, you also have the download link

https://www.meuquantum.com.br/celular-quantum-go/t/20

https://mega.nz/#!SlgR3TZD!nEd_Y_jrCnNvwzT-gfNPduqfxDM4yRTiO_yX7K0A0ms
[Android Apps and Games] tliebeck:
Thanks again for the detailed report...I just tried on a 6.0 device to (Galaxy S5, so very much not pure and not MediaTek)... not reproducible there. I don't think FX is doing anything wrong here. I've now added a RuntimeException check there in FX (for all the "viewer" activities and for the text editor). So for next release you'll get an "Internal Error" type dialog instead of a crash, and it'll be logged to FX's internal log (viewable via system status).

And yes, checking for RuntimeExceptions in places where they're not supposed to occur is generally bad programming form...but I'm only capturing them for this single method call after validating the parameters being sent beforehand.
[Android Apps and Games] tliebeck:
Need a favor of anyone with a Pixel or Pixel XL on the September security patch....

Could you try turning on web access, and uploading a 3GB or larger file to your device?

A user e-mailed me stating it causes the phone to slow to a crawl, and when it's about to finish, the device reboots entirely. I'm just curious if they all do this. Apparently it started after the latest security update, patch level dated September 5.

Thanks!
[Android Apps and Games] osm0sis:
Sounds like the device ran out of space.
[Android Apps and Games] Omel:
Root access

Hi

I have a problem With the newest stable fx the root add on behave strangely

When I enable the root addon it is disabled in fx explore and when I disabled it its enable in fx explore .. but I can not see the listing when I try to list root

What can I do .. I have tried to reinstall but with no luck

I'm on android 5.1.1
[Android Apps and Games] ipdev:
I ran into the same on a 5.1.1 device a little over a week ago.

Go back to FX 6.0.2.3 (r6012) and give it a try.
[Android Apps and Games] tliebeck:
Note that the button in "add-ons" is used to toggle it to the other state. So if it says "Disable", that means it's enabled, the disable button disables it.

I want to re-do the add-ons screen altogether, I really don't care for it.
[Android Apps and Games] osm0sis:
A few things off with the new SMB implementation still:

1) sizes are all reported oddly, often rounding to the nearest 4kb. This is a regression, they used to be accurate.

2) some files don't edit correctly across SMB, I'm mostly noticing this on my shared files that are part of Cygwin's tree, like a git project, but moving to device, editing and moving back does work. This is also a regression as these used to edit fine.

3) my SMB v1 server disabled but client enabled Windows setup still doesn't work in FX of course, but remains working fine on Google's example Android Samba Client app (and my Nvidia Shield TV's network storage mount feature).

Anything at all that I can provide you to help debug this stuff?
[Android Apps and Games] tliebeck:
Thanks for the reports, as always!

#1 is fixed for next release. API I'm using is new and so docs are pretty scarce...only means I saw of obtaining file size was "getAllocationSize()" which is rightly in big increments. Turns out "getEndOfFile()" is the correct call. That's what MS calls it. :)

I'm still not certain on #3. I need to update the new SMB lib to a later version yet (may be in next release or shortly after).

What kind of behavior are you seeing on #2? Is this a "partial save" warning or something that is occurring on opening or something else? This could be related to #1 as the editor does do some checking on file size.
[Android Apps and Games] osm0sis:
I'm at work right now, but #2 is a write error at save time, if I recall correctly.

Thanks for looking into these things, and all the work you put into FX. I'll keep testing whatever you throw our way. I quite enjoy FX and it's pretty integral to my workflow at this point. :)
[Android Apps and Games] BobboVilla:
Hi, I have an odd problem when using the root option from the home screen. All the folder and files names are garbled, and I can't enter them. I attached a screenshot of how it looks.

I'm running the latest released version of FX, but I don't know whether this issue wasn't in a previous version.

The device is Asus ZenFone 2, running Android 5.0, stock and rooted, but without anything else (Magisk, Xposed, etc.). If you need any other information and/or logs let me know.
[Android Apps and Games] tliebeck:
Are you using a custom busybox? This looks like a modified version has been installed that is doing color-highlighted directory listings (those look like ANSI color codes prefixing the file names).

This should be solvable by having FX use it's own busybox or using one that hasn't been modified/configured to do color coded listings.
[Android Apps and Games] BobboVilla:
I don't have any busybox installed on my device, and am using FX's busybox.
[Android Apps and Games] tliebeck:
Thanks, actually looks like the color flags are enabled in FX's busybox. Will be disabled in next release. Not sure why this issue never presented itself elsewhere, but thanks for report!
[Android Apps and Games] BobboVilla:
Thanks! ANSI codes. I knew it looked familiar, but I just couldn't place it :).
[Android Apps and Games] osm0sis:
Following up on these now that I've had a day off at home.

In a totally bizarre turn of events I was changing the channels of my WiFi network to less congested ones and all of a sudden #3 works again. Still weird that Google's example code could handle it the whole time, but hey, I'm just happy it works now. My best guess is an IP conflict on the network for that computer that finally resolved itself with a few reboots of the router from the settings changes.

And as for #2, the full error is at save time, and is "Save failed: the file could not be written to.", and the associated logcat error is as follows:

10-06 01:34:34.012 W/nextapp.fx(19661): SMB Error
10-06 01:34:34.012 W/nextapp.fx(19661): com.d.h.b.b: STATUS_ACCESS_DENIED(3221225506/3221225506): Create failed for cygwin\home\Chris\AnyKernel2\META-INF\com\google\android\updater-script
10-06 01:34:34.012 W/nextapp.fx(19661):	at com.d.h.g.k.a(Unknown Source:48)
10-06 01:34:34.012 W/nextapp.fx(19661):	at com.d.h.g.k.a(Unknown Source:9)
10-06 01:34:34.012 W/nextapp.fx(19661):	at com.d.h.g.k.b(Unknown Source:33)
10-06 01:34:34.012 W/nextapp.fx(19661):	at com.d.h.g.c.a(Unknown Source:8)
10-06 01:34:34.012 W/nextapp.fx(19661):	at com.d.h.g.c.c(Unknown Source:32)
10-06 01:34:34.012 W/nextapp.fx(19661):	at nextapp.fx.dir.smb.e.a(Unknown Source:78)
10-06 01:34:34.012 W/nextapp.fx(19661):	at nextapp.fx.ui.textedit.EditorActivity$50.a(Unknown Source:50)
10-06 01:34:34.012 W/nextapp.fx(19661):	at nextapp.maui.k.d.run(Unknown Source:10)
[Android Apps and Games] tliebeck:
I've just updated the SMB library to the latest version in my work tree here, will be in next (6.1 beta) release. This might just be a file locking error, which I know they've worked on since the version that's presently shipping in FX.
[Android Apps and Games] Je5hu4ver:
So you can just share a folder for anyone that ouches backs with your phone?

That sound awesome, but I assume that bot people need the app or it wont work in any way.
[Android Apps and Games] tliebeck:
Yes, via "FX Connect" under "File Sharing". Both devices need to have FX+ . For the touch connect to work, both devices have to have FX open. You can also start FX Connect directly from the "File Sharing" screen on both devices and associate them wirelessly.

The not-yet-but-soon-to-be-released 6.1 should improve FX Connect's reliability and performance quite a bit. I'd always seen that some devices have some major reliability issues with dropping connections, failing to connect, or having horrible transfer rates. It turns out that the problem is with the Dual Wi-Fi adapters in mid-high end devices. When one is connected to a Wi-Fi access point and the other is used for Wi-Fi direct, the performance can be quite bad. Some devices work just fine. And some of the worst offenders are higher-end stuff. In 6.1, there's a default-enabled option to disconnect from any associated Wi-Fi access point first....now seeing an average 15 megabytes/second transfer rate between a PIxel C Tablet and S7 Edge that previously wouldn't talk to each other at all. :)
[Android Apps and Games] slonn:
Any plans to add a backup/restore option?
[Android Apps and Games] Ultramanoid:
https://xdaforums.com/showpost.php?p=64771041&postcount=2879
[Android Apps and Games] slonn:
Thanks - may as well be written in Chinese [emoji4] - I'll rely on titanium backup instead
[Android Apps and Games] GeTex:
Are you talking of backup/restore for FX and files only? or backup/restore for all applications?
[Android Apps and Games] Ultramanoid:
It's just two script files, backup.sh and restore.sh. Tap on the appropriate one within FX and run it.
[Android Apps and Games] slonn:
Backup/restore for FX app setup
[Android Apps and Games] GeTex:
just goto a directory, make a new file, name it backup.sh and the other restore.sh, then copy paste the code that tliebeck wrote and after that just click on the file to execute it.

if you need help just ask
[Android Apps and Games] fidorulz:
Need some help here. Using latest version of the app from the play store and I have had the following issues in and off for a few months on various ROMs

I do a clean install and then install FX and give root access as well as read/write permission for my external SD on my S7 edge

Once it a while I try to erase something from my external SD or copy to it I get a popup saying

Access was denied

This is even with all the permissions being ok

See this video to see what I mean. Any ideas why this keeps occurring?

https://youtu.be/EpZ1W0ohWOM
[Android Apps and Games] MrWasdennnoch:
A little improvement idea I just found: Since N Android offers File-Based encryption which stores some files in different paths; example:

/data/user_de/0/de.robv.android.xposed.installer

(guess how I figured this out...).

As you see the files are structured by packages like in /data/data/ but FX doesn't display app icons for them, it would be nice if you could add that "encrypted" path to the folder icon manager :)
[Android Apps and Games] slonn:
Tried creating a backup.sh file but it just returns empty when creating via Text Editor. Not sure what is missing...
[Android Apps and Games] Ultramanoid:
Here you have them. It's just a copy and paste operation to create them. If you open the .txt files on any text editor you can read how the backup or restore is done. Change the .txt extension to .sh to use them.
[Android Apps and Games] GeTex:
I woulda just posted the .sh files in a zip file
[Android Apps and Games] Ultramanoid:
Given slonn seems to have a problem creating .sh files with a text editor I thought I'd play it safe and also show that it's literally just a text file with the code copied on it.
[Android Apps and Games] GeTex:
changing extensions confuses alot of people... they make like backup.sh.txt
[Android Apps and Games] Ultramanoid:
I'll make sure to stop helping after giving the link to the answer next time, or better yet, just point to XDA forum rules : "search before asking", and leave it at that. Which for some reason, I didn't do this one time.

Have a good day / night.
[Android Apps and Games] GeTex:
I'm not attacking you? I'm just saying...
[Android Apps and Games] ipdev:
[MENTION=2954544]tliebeck[/MENTION]

I apologize it took so long. (I wanted to make sure it was not a user error or a custom rom issue.)

Running Android 5.1 and 5.1.1 (API 22)

When I select System(Root) from the home page I get this error.

“The operation could not be completed.”

Seems to be be related to internal busybox (FX Provided Busybox) and affects API 22 only.

If I install a busybox and select /system/xbin/busybox then FX works fine on API 22.

Notes:

Tested with Nexus(s), google factory image(s), SuperSU 2.82-SR5 and FX_r6017.

4.4.4 API19 - r6017 (FX Provided Busybox) works

5.0.x API21 - r6017 (FX Provided Busybox) works

5.1.x API22 - r6017 (FX Provided Busybox) error

6.0.x API23 - r6017 (FX Provided Busybox) works

7.0.x API24 - r6017 (Did not test, missed it actually :silly: )

7.1.x API25 - r6017 (FX Provided Busybox) works

8.0.0 API26 - r6017 (FX Provided Busybox) works

- API 22 was tested with SuperSU 2.46, 2.65, 2.82-SR4 and 2.82-SR5.

FX_r6015, r6016 and r6017. -

Attached is the last error log. (Nexus 7)
[Android Apps and Games] tliebeck:
FX 6.1.0.0 Released (Beta Channel)

Hello all, just uploaded the first 6.1 beta. This release also contains a lot of miscellaneous fixes and improvements due to extensive review of code both manually and using automated tools.

New SSH implementation: much faster transfer rates, improved compatibility with modern higher-security SSH servers.

View thumbnails over network connections.

View thumbnails inside archives and APKs.

Thumbnails are now stored in WEBP format, internally in a private cache directory. Existing thumbnails stored in internal storage will be deleted and re-rendered.

FX Connect now provides the option (enabled by default) to shut down connection to Wi-Fi access point upon connection. Modern mid-high-end devices are supposed to be able to be connected to two Wi-Fi networks at once (one being an AP network, the other being FX Connect's established Wi-Fi Direct network). Unfortunately in practice, this just plain doesn't work a lot of the time. Presently the Wi-Fi disconnect is done once FX Connect begins establishing its network, but I may change this to shut it down the moment you request a connection. Without this feature, some devices experience 80% packet loss. The worst offenders were an S7 Edge (7.0) talking to a Pixel C tablet (8.0). Shutting down the connection to the Wi-Fi AP makes everything work, and fast.

DEX browsing: browse inside .DEX files, including those within .APK files. Browse class/method/field structure. Use this feature to analyze third party libraries embedded in applications (e.g. potentially malicious/nefarious ones used by installed software, or illegal use of your open-source software). Also nice for verifying Proguard obfuscation in your own applications. Long-press on an APK, choose "Explore with FX", and then open the .dex files inside.

Fixed launcher shortcuts in Oreo. You can’t create shortcuts in Pixel launcher though, because Google chose not to implement the new API from Google. Yes. This.

Massive code review.

EDIT: I forgot to mention FX Connect update....added.

Direct Download: http://android.nextapp.com/fx/r6101/FX_r6101.apk

Beta Testing G+ Community: https://plus.google.com/communities/101301040394875566704 (join community, then go to https://play.google.com/apps/testing/nextapp.fx )
[Android Apps and Games] osm0sis:
Not sure if this is why, but Lollipop had a particularly broken toybox implementation of sed, so maybe FX relies on it somehow in its root directory parsing and should use its internal busybox (after adding sed to it) instead?

Edit: Just checked the log, that linker warning doesn't look so hot, though I guess the command could still execute correctly. Do you have a full content SuperSU log you could post of FX's busybox failing on 5.1?

Nice! This fixes the file size reporting via SMB, but I'm still getting that write error I didn't previously before you added SMBv2.
[Android Apps and Games] tliebeck:
Thanks much for the detailed reports, that's a lot of work!

It appears it's the linker warning that's killing it. That's going to stderr, and for certain commands FX assumes this is catastrophic.

Not certain what the correct solution is for this i.e., if the linker warning is actually an issue, or if it's just a side-effect on SDK 22 devices. It'll be easy enough to run those through a regex and ignore them on SDK 22 if that's the answer.
[Android Apps and Games] slonn:
Thank you! Turns out I did manage to do a backup yesterday but when running the .sh file it just said Empty so I didn't think it actually worked, but it did in fact create a backup folder on the SD card.
[Android Apps and Games] fidorulz:
I uninstalled everything FX related and installed this update

I am still getting

Access was denied

When attempting to move files to my external SD or modifying files on my external SD. Root access works fine and I made sure to enable write access

See this video to see what I mean. Any ideas as to what else I can do at this point?

https://youtu.be/EpZ1W0ohWOM
[Android Apps and Games] tliebeck:
Thanks for detailed report! Which S7 Edge is this? Snapdragon or Exynos? Are these real ROMs or just modified stock stuff that runs on the bootloader locked US-spec S7? Other file explorers work?

Have a US-spec S7 Edge as a test device, has always consistently worked correctly here. It's bootloader-locked but have run engineering BL/root with no issue.

Anything in the error log concerning this? (Settings->Error Log). It probably won't be logged as an error there because it's not interpreting this as a proper "failure", just that you've tried to write to an area you can't. (Think I may actually want to add a "log everything" setting for these cases though).
[Android Apps and Games] fidorulz:
Sorry if I lacked info.

Using SM-G935W8 on SuperMan-Rom V2.7.0 which is using Exynos with TWRP and rooted. To my knowledge the bootloader is unlocked

At fastboot screen I see the following

Download Speed-Fast

Product name--Sw-G935W8

Current Binary-Custom

System Status-official

FAP LOCK-OFF

Secure Download-Enabled

Warranty Void: 1 (0x0500)

AP SWREV: B:1 K:0 S:0

No logs seen for issue in the app

Found something curious. The issue occurred when I was trying to write to a specific folder on external SD. For the hell of it I tried writing on the root of the external SD and it worked fine. After that I was able to write in the folder I had issues prior

Odd thing is this seems to occur on and off at random for past few months on various roms but never bothered to report it
[Android Apps and Games] tliebeck:
Thanks! Added icons for /data/user/#/app and /data/user_de/#/app, will be in next release.
[Android Apps and Games] ipdev:
From tonight.

Nexus 7 WiFi (2013)

5.1.1 (LMY48T)

SR5-SuperSU-v2.82-SR5

FX_r6101

SuperSU log.

cat /proc/mounts >"/data/data/nextapp.fx/app_Pipe/Pipe_1507685806860_1" 2>"/data/data/nextapp.fx/app_Pipe/Pipe_1507685806862_2"
/data/data/nextapp.fx/app_Exec/busybox ls -dAlnp --color=never --full-time "/" >"/data/data/nextapp.fx/app_Pipe/Pipe_1507685806950_3" 2>"/data/data/nextapp.fx/app_Pipe/Pipe_1507685806950_4"
[Android Apps and Games] gazzacbr:
Hi, just saw the latest update and installed it but my problem is the same. On HTC M8 LineageOS 14.

I have a mp4 movie file on internal 1.5GB and when I copy it to removable sd card the progress 'clock' counts correctly. But the copied file size is between only 20mb and 50mb (varies each time)

Copying with the lineageOS files app works fine (and is quicker)
[Android Apps and Games] tliebeck:
FX has to use the "storage access framework" to write to the SD card while the stock file manager gets to execute the copy directly. Could you test this with a third file manager (of the variety that requires granting standard SD card write access, rather than using root)? That should tell us whether this is an FX issue or a broken storage access framework implementation on the device.

I'm on LineageOS as well (and have an SD card)...have not seen this before.

Does the copy finish in FX? Check the completed transfer statistic (tap on the "Completed") item in the slide out. Let me know if there were any retries/errors mentioned.