yashsingh1/xdaforums huggingface dataset:
[Android Apps and Games] tliebeck:
Can you post a screenshot of the ugliness?

The logo is supposed to "come in to focus" as the bar scrolls out, that is, it's very blurred when the drawer initially slides out and then it should be fully-non-blurred when the drawer is extended. There's a black shadow image gradually appears behind it as in un-blurs.

[YOUTUBE]K5OJoQ7NR5g[/YOUTUBE]

It should be very smooth (video doesn't show this as the screenrecorder burns a lot of CPU).
[Android Apps and Games] Morinzo:
[MENTION=863226]tile[/MENTION]beck any plans for a Android TV version??
[Android Apps and Games] mbc07:
Apparently that's not the case. My Xperia M5 is running Android 5.1 and I got a KitKat style status bar. Tested in my mother's Xperia Z3+ with Android 6.0.1 and in my uncle's Xperia M4 Aqua with Android 5.0 and all of them had a KitKat-like status bar. So, I think it's safe to say it affects all Xperia devices...

Well, well, well, here we are again discussing about the slide-out menu again. At this point I think it's useless to keep complaining about that but let's try a last time. Firstly, huge paddings and wasted space are still there, please do something with them (take some inspiration from that mockup I posted a while ago). Secondly, the new animation in the slide-out menu: I actually like it, but I think the "fx" letters should be moved up a little bit so they don't appear to be "glued" on the bottom border. And finally, can we have an option to hide the FAB and bring back the menu entry for a new window instead? I used to hate the menu entry but now I became so used to it that I find the FAB "meh, it don't look right being here"...

But, design choices aside, now that you showed how the slide-out menu is supposed to look, the status bar behavior is even weirder here. It'll show with KitKat style when I open FX. However, the portion of the slide-out menu that is supposed to be "covered" by the status bar will have Lollipop style (it's literally mixing up both KitKat and Lollipop styles at the same time here). And I noticed something that looks like another glitch? Every single page of FX Settings now shows a "slide from bottom to top" transition (the same from when you start/exit a new app). On previous versions I remember having this transition only when entering/exiting settings screen, not when going back and forth on other pages. Is that intended too?

(check the attachment, it's a screen recording demonstrating what I'm talking about)
[Android Apps and Games] thedicemaster:
https://drive.google.com/file/d/0B6ZdEUOFDbiwcmJHb3h5SGt2Qjg/view?usp=drive_web

until it's halfway extended the logo looks like that, and then the "fx" text jumps into focus(nothing gradual about it)

at this same point the grey goes away, and the background shapes appear and get their proper animation.
[Android Apps and Games] tliebeck:
Could someone with the KitKat-gradient-status-bar try the following APK:

http://android.nextapp.com/fx/junk/LayoutTest2.apk

This is *NOT* any kind of version of FX, it's just a layout testing APK. I need a screenshot of what it looks like with the drawer open and closed. Thanks!

Screenshots below are what it looks like on a Nexus 5 (6.0.1 stock).
[Android Apps and Games] thedicemaster:
https://drive.google.com/open?id=0B6ZdEUOFDbiwNUlBd1htRWJvQVk

https://drive.google.com/open?id=0B6ZdEUOFDbiwSU8zMW55VkZ2UU0

I couldn't upload them through xda because the upload dialog won't open in Atlas.
[Android Apps and Games] Ultramanoid:
There's no need to quote fully the huge first post only to ask a question. There's no reason to quote it at all actually, and people using applications instead of browsers, and/or small devices to read through the thread will be very inconvenienced.
[Android Apps and Games] mbc07:
Show the same as current beta of FX. KitKat gradient while closed, Lollipop tint on the slide-out portion...

(that's on Xperia M5 with stock Android 5.1 ROM)
[Android Apps and Games] tliebeck:
Thanks, really appreciate it! Not the result I wanted of course. :(

BTW, I imagine people may be somewhat confused as to why I can't manage to get this right with FX, in comparison to every other app on the Play Store that gets it right. There is a reason for this nonsense.

FX doesn't use Android's v7-appcompat APIs (yet). I may have to change this. It shouldn't need them as I'm using custom widgets to render the ActionBar (so that I can do things like drag-down-for-split-window). If I add that library into FX, it adds just enough bloat to exceed Dalvik's 65,536 method limit. Which means I have to enable "multidex." Which means compiling takes five minutes. Which quite frankly makes development incredibly difficult. I'm trying to figure out how v7-appcompat is setting up the layout to work properly on all devices...and so far am failing to do so on more "skinned" devices like Samsung stuff.
[Android Apps and Games] BobboVilla:
So basically you're wasting so much time because you don't want to waste so much time? ;)

But I think I get what you mean. You have a certain way of doing things, and you're annoyed that you have to change the way you work "just because", with no major benefits from the new/other method.
[Android Apps and Games] GeTex:
You have no idea how much time it wastes. As a developer you recompile near hourly to even every 30 minutes or less during development of stuff. Going from a nice small 1.5 minute or less compile to a 5 minute plus is the difference of taking 3 hours to develop an update to near 6-8. It can be insanely ridiculous so he's trying to optimize everything to keep it lightweight, but he's struggling. Enabling multi dex also has a performance drop for some devices and systems because of the way dalvik VM works and the dex system and tbh I can't even remember

The dev can explain better but all I know is they are trying to do this the most optimum way without wasting because google is very very wasteful with resources and such, which is why lots of stock devices are bloated
[Android Apps and Games] BobboVilla:
I actually know how using a slow tool is increasing development time. I'm a programmer for information systems, and one of the tools we sometimes have to use is so slow that it increases the development by 4 or 5 times, meaning that something that takes an hour in one tool took me 6 hours in the slow (but newer, and therefore supposedly better) tool.

Thanks for the information regarding compiling in Android. It seems like a bit of a mess :).
[Android Apps and Games] GeTex:
A big thing is unlike apple who has one device line and when something becomes old, they just end support, we in android have a large variety but attempt to make all the customization and special devices work with unified development. When we unify all these devices it becomes a complex mess that has little to no logic behind it
[Android Apps and Games] Thirumalai.K:
As of now, Keeping the app backward compatible is a challenging task than the development....:crying:
[Android Apps and Games] Ultramanoid:
I've been testing with Android 6.0.1 and unfortunately all the bugs I reported with 5.1.1 are there too.

SONY devices, but with AOSP and CM 13 roms, so can't blame it on OEM's soft I guess.
[Android Apps and Games] tliebeck:
Thanks, don't worry about this though, problem is corrected in local source, hope to have a new release in the beta channel very soon.

And for those technically inclined/finding this in a Google search in frustration regarding their own projects...the problem is that using the line:

<item name="android:windowTranslucentStatus">true</item>

to simply draw under the status bar yourself turns out to be problematic. I believe the correct behavior is for the device to render a slight dimming layer over whatever you draw in the status bar (as is done by all Lollipop and later Nexus/Motorola devices). Unfortunately it appears many devices (Samsung Lollipop stuff, and apparently a lot of Sony stuff) choose to render the KitKat style gradient.

Most people simply use the appcompat libs to work around this, but as said previously those add a fair amount of bloat and in the case of FX would push us over the limit for having to use multidex. It turns out you can make it work with a standard DrawerLayout, but I found some major problems getting it to behave. If you don't pass in a style with "fitsSystemWindows" set to true at *construction time* it will never work. And for drawers to slide underneath the status bar I had to borrow a copy of "ScrimInsetsFrameLayout" from the appcompat libs. Fun times.

This bug was a week. And not a fun one.
[Android Apps and Games] tliebeck:
FX 5.1.0.17 Released (Beta channel)

This one is just a bugfix release:

Status bar should now appear as solid color on all devices.

Slide-out animation bug fixed when using translucent themes.

Video player fullscreen fix.

Direct Download: http://android.nextapp.com/fx/r5117/FX_r5117.apk

Beta Testings G+ Community: https://plus.google.com/communities/101301040394875566704 (join community, then go to https://play.google.com/apps/testing/nextapp.fx )

This release was just uploaded to beta channel, it may take an hour or two to become available via the Google Play Store (if you are a beta tester).
[Android Apps and Games] GeTex:
Any input you'd like for this beta? I can test and feedback if you'd like
[Android Apps and Games] Ultramanoid:
All visual glitches fixed as far as I can tell, and that most annoying autonomous reposition of FX in the task manager's stack of cards as well.

Thank you very much.
[Android Apps and Games] thedicemaster:
the glitch i reported earlier with the animated fx logo in the sidebar is still there.
[Android Apps and Games] simonbellu:
[MENTION=2954544]tliebeck[/MENTION]

Bug report.

1- With the last beta if you go back from settings window to main one, the 3dots menu and the search icon on the top right change their original vertical position and go inside the status bar.

2- On large tablet display, the FAB for adding new windows are not in the correct position, but higher.
[Android Apps and Games] mbc07:
Hey [MENTION=2954544]tliebeck[/MENTION], updated to the latest beta and while the KitKat style statusbar were fixed, a new issue appears. Check the screenshots, fx-pos-5.1.png is what is shown when you open the app (of if you close it through recents menu and reopen it). So far, so good, however, if you do something that makes the action bar change or hide (going to FX settings or switching to another theme, for example) will glitch out the status bar (fx-pos-5.1-buggy.png and fx-pos-5.1-buggy-slideout.png), it'll basically draw behind status bar with no effect (neither Lollipop nor KitKat style). Ad as last, there's an additional screenshot (fx-pre-5.0.png) which shows how FX looked on the previous versions. If you compare the two, current beta of FX will have a slightly darker status bar (to make clear, I'm not complaining about such a minimal difference, but I think it's worth mentioning, maybe that give you some clue on what's happening).

As usual, tests ran on Xperia M5 running stock Android 5.1 ROM...
[Android Apps and Games] tliebeck:
What device/ROM is this? Does it work correctly when a non-translucent theme is selected?

The animation glitch was a result of adjusting too many parameters of those three rectangles in response to drawer movement. I was changing translationZ, rotation, rotationX, and rotationY. The fix was to disable changing rotationX and rotationY when a translucent theme was used. Disabling hardware acceleration also cures it.

The problem is that it appears Android is quite broken...not sure how I can detect it either.
[Android Apps and Games] tliebeck:
Changing themes unfortunately has caused this type of behavior for a long time (between translucent and non-translucent themes). Will take a look to see what I can do, may even be possible to fix as a result of new layout structure.

I may need to simply add a note when changing to/from translucent themes that you might want to quit FX entirely.
[Android Apps and Games] mbc07:
What I actually mean by changing theme is that simply changing the colors of the default theme will trigger this, the same if you enter into FX settings then go back to the file manager. This definitely doesn't happen on previous versions...
[Android Apps and Games] thedicemaster:
samsung galaxy note 4 N910F Android 5.1.1

I see now that the bug isn't in the grey behind the fx logo, but when the animation starts(which is when the sidebar is halfway open)

when a transparent theme is set the squares become invisible the moment the animation starts, and gradually become visible from left to right like a progress bar while at the same time rotating 45°.

when an opaque theme is set the squares are visible the whole time, and start their 45° rotation at the halfway point.

the blurring in the fx logo i mentioned does look to be the way you intended, but it looks like bad loading because of both the glitch with the squares and because the sharpening doesn't occur until the halfway point and then goes really fast.

have you considered starting the sharpening right from the beginning(or was this maybe even the intention?)
[Android Apps and Games] tliebeck:
Thanks now have this replicated on an S5.
[Android Apps and Games] tliebeck:
Looks like I can fix this bug by installing a blank FrameLayout as the root of the screen, rendering the screen, and then installing the FX layout again. Replacing one DrawerLayout with another that's drawing under the status bar just doesn't work otherwise. I'd tear into the code and try to figure out what's really going on in DrawerLayout....but can't waste any more time on this crap.

Android's UI framework is just plain sad. Like Visual C++ GUI work in 1999 sad.
[Android Apps and Games] tliebeck:
I've added a "GPU Accelerated Animations" checkbox to the settings which will be out in the next version. I wish I had a more elegant solution, but as far as I can tell this is simply bug(s) in Android's hardware acceleration implementation. I don't know how I can test for this. Nexus devices don't have the problem on Android 5. Samsung S5 on Android 5.0 even works fine. I was only able to replicate the problem by turning (part of) this animation on for KitKat devices and testing it on a Note3.
[Android Apps and Games] tliebeck:
:rolleyes: :vomit:

/**
* This method works around Android bugs found in certain devices where replacing
* one DrawerLayout with another (as is done when createImpl() is invoked a second time)
* results in incorrect rendering of the status bar.
*
* FIXME If possible, determine a list of devices / OS versions affected by this issue
* FIXME and skip this hideous code for those that are unaffected.
*/
private void doDrawerLayoutChangeWorkaround() {
setContentView(new FrameLayout(this));
uiHandler.post(new Runnable() {
@Override
public void run() {
setContentView(contentFrame);
uiHandler.post(new Runnable() {
@Override
public void run() {
contentFrame.requestLayout();
}
});
}
});
}
[Android Apps and Games] tliebeck:
FX 5.1.0.18 Released (Beta channel)

This another bugfix release for UI issues.

Worked around Android bug on certain devices where changing settings/themes would cause menu to appear under status bar.

Worked around Android bug on certain (other) devices where drawer slide-out "animation" would seize/flicker/do ugly things.

Added option to disable GPU accelerated animations to fix exceptionally broken devices.

Thank you all again for the bug reports, really appreciated. Apologies for the sarcasm, I really wish the bugs would more often be in my code rather than Android/device implementations thereof...heck of a lot easier to fix my own broken work than someone else's. :D

*** BAD RELEASE DO NOT USE ***

Direct Download: http://android.nextapp.com/fx/r5118/FX_r5118.apk[/strike]

Beta Testings G+ Community: https://plus.google.com/communities/101301040394875566704 (join community, then go to https://play.google.com/apps/testing/nextapp.fx )

This release was just uploaded to beta channel, it may take an hour or two to become available via the Google Play Store (if you are a beta tester).
[Android Apps and Games] thedicemaster:
disabling gpu acceleration fixed the animation for me.

the blurred fx logo still looks a bit odd/cheap to me, but the glitches are gone.
[Android Apps and Games] simonbellu:
With last build, Unchecking Animation option in settings now force close the app. Cannot open it anymore. Have to delete app data and cache to open again the app
[Android Apps and Games] Ultramanoid:
Same here, and as I had that option unchecked in the previous version I just got an instant crash every time I launched the new version without any idea about why until I read the post above...
[Android Apps and Games] tliebeck:
Thanks, emergency release momentarily.
[Android Apps and Games] tliebeck:
FX 5.1.0.19 Released (Beta channel)

Fix for crash when disabling animations.

Direct Download: http://android.nextapp.com/fx/r5119/FX_r5119.apk

Beta Testings G+ Community: https://plus.google.com/communities/101301040394875566704 (join community, then go to https://play.google.com/apps/testing/nextapp.fx )

This release was just uploaded to beta channel, it may take an hour or two to become available via the Google Play Store (if you are a beta tester).
[Android Apps and Games] Thirumalai.K:
[MENTION=2954544]tliebeck[/MENTION]

Is there any way to move files inside external sd without copying? When I move large files like movies it's frustrating.

Probably a limitation from SAF. May need a work around. But, Copying the files to target location & deleting the source file is not the efficient way. I have to still depend on stock file manager for moving large files.

One more thing, is there anyway to keep the time attributes when copying/moving the file to external storage..?

Currently I am lossing it when copying or moving to external storage. After Copying or moving multiple files it becomes very hard to identify the older or new files. Have to manually compare the contents.
[Android Apps and Games] tliebeck:
Regrettably can't be done until Android N, they just added moveDocument in API 24. Edit: Good news is it appears to work. Will be in next beta for N-devices.

I don't know of any way to update file modification times without using superuser privileges. java.io.File.setLastModified is inert if I recall correctly, though I ought to check it again and see if they added an implementation in Android M/N.
[Android Apps and Games] tliebeck:
Just revisited the last-modified issue... Google is never going to fix this.

https://code.google.com/p/android/issues/detail?id=18624

https://code.google.com/p/android/issues/detail?id=25460

Tried both File.setLastModified(), and also "touch" command. Both fail.
[Android Apps and Games] GeTex:
Any specifics you would like me to test? Currently have 2 GS5's one on MM and the other LP and a GS3 running JB
[Android Apps and Games] tliebeck:
Thanks, does the slide-out render properly on all those?

Other than UI stuff, the biggest change in 5.1 is the USB OTG support.
[Android Apps and Games] Thirumalai.K:
Google is always lazy in hearing developers feedback.

BTW, is it not possible to move a file with mv command...?

I am not sure whether it can be used with SAF or not.

One more thing, what's the technical difference between ”Explore Archive" & ”Archive Extractor"...…?

FYI,

When extracting a rar using "Explore Archive" copy and paste it takes mins to extract the files where as in "Archive Extractor" it takes few seconds to extract the all files of the sane rar archive. Looking for the same performance in Archive Explorer as well.
[Android Apps and Games] tliebeck:
mv won't work with SAF. To work with SAF you have to use the SAF Android API, as your app's process never has permission to manipulate files directly.

There are performance differences that need addressing between Explore Archive/Archive Extractor, will look into it specifically on RAR to see if the explorer mode can be optimized. Archive Extractor has the benefit of working through the archive linearly.
[Android Apps and Games] GeTex:
I cannot test on every devices yet but my AICP v11(CM 13 MM device) had the following results when testing the action bar

But when I tested on my GS5 running TW Lollipop this happened. Should I try disabling hardware acceleration?

Next to test, Acatel One Touch, U510 Obamaphone, LG Optimus C, Galaxy S3.

EDIT: LG Optimus(running Android 2.1) actually crashes when trying to open settings. It appears FX doesn't work on 2.1 anymore?(lol)
[Android Apps and Games] thedicemaster:
on the gs5 disable hardware acceleration.

apparently it's a samsung issue, I had to do the same on my note 4.
[Android Apps and Games] GeTex:
Tested FX on the U510(kitkat) and it performs as expected

On the GS5 running LP disabling gpu accel in FX fixed the animation. The GS5 on AICP v11 however does not require disabling GPU accel so there may be evidence there is no problems for those using CM and CM based devices.

Testing on the GS3 running CM12 shortly however the GS3 running JB is not functional. I have a mediatek 6572 device I can test as well but the screen is partially broken and hurts to use
[Android Apps and Games] ruifung:
FX SFTP functionality does not work with my SSH server which is configured in a way that requires both a Private Key and a Password when connecting to it.
[Android Apps and Games] thedicemaster:
finally, after about a year, I've tracked down the trigger of a bug that slows FX down to a crawl.

FX would always stutter and freeze when displaying the android/data and android/obb folders on the sdcard and internal storage.

today I found out it's specifically the folder "net.fishlabs.gof2hdallandroid2012" that causes the problems.

deleting it, or moving it to a location that doesn't generate app-folder icons fixes the problem(but, obviously, makes the associated game unplayable)

this folder belongs to the play store version of galaxy on fire 2.

perhaps now this problem can get fixed.

if necessary i can provide a resources.arsc file that should contain the icon that causes the problems(i don't have a way to extract it myself).
[Android Apps and Games] tliebeck:
Just tried downloading it, started up, killed the three pirates, got to the space station.

But I'm not seeing the lag browsing that folder. Icon appears properly. Folder only has 30 files in it (does yours have a bunch more?)

This is on a Nexus 5, totally stock, (almost) latest version of Android 6, viewing as normal user. Don't have root access on this phone at the moment though, is this via root only?
[Android Apps and Games] GeTex:
I read that and was so confused for a second till I realized what was going on. I was in tears laughing.
[Android Apps and Games] tliebeck:
LOL, yeah, can see how that might have been an odd thing to read. :D
[Android Apps and Games] thedicemaster:
I was going to write a whole story, but I got more useful info:

it's a conflict between the icon and FX's translucent themes.

any screen showing the GoF2 icon (data/obb/user-installed apps view) lags for me when I have a translucent theme set, switching to a solid theme fixes it.

device specifics:

samsung galaxy note 4(N910F)

android 6.0.1(and older)

stock rom with goodlock(and without), no root.
[Android Apps and Games] tliebeck:
Really odd. Not seeing it on N5/6.0.1 at all. Is this the icon?
[Android Apps and Games] thedicemaster:
yes.

I guess it's a samsung thing.
[Android Apps and Games] mbc07:
About KitKat-style status bar on Lollipop: apparently even Google can't get that right, the last update to the Google Fit app introduced the same issue FX was having a while ago in setting the proper status bar style, Google Fit is displaying KitKat gradient everywhere now :eek: