yashsingh1/xdaforums huggingface dataset:
[Galaxy S 5 General] Flow-Wolf:
Hi everyone!

I want to share with you my top Tips & Tricks for our Samsung Galaxy S5!

[YOUTUBE]suNWZEAALDM[/YOUTUBE]

Enjoy :D Don't forget to thumbs up & Share

If you have any questions !
[Galaxy S 5 General] D33KK:
Would you recommend taking the plastic off the camera?
[Galaxy S 5 General] eyecon82:
I left it on my s4 and never had an issue with it

I think I'll leave it on the s5 too

Sent from Tapatalk
[Galaxy Note 10.1 Q&A, Help & Troubleshooting] shaft19:
Hello everyone,

first I'd like to apologize for my English. I prefer the German but this isn't allowed here as far as I know.

I have a big problem with my Note 10.1 N800. I rootet it when I baught about one year it and it worked fine until some days ago.

Neither did I use a custom rom nor any tweaks.

Now my problem: The tablet won't boot. It stays in the screen "Samsung Galaxy Note 10.1" until the battery is emty.

It is not pssible to turn the device off, it just will sart again and remain in the same screen.

I'm not able to acces the recovery mode, but I can starte the tablet into downloadmode.

I flashed the latest stock rom to get the stock recovery but that didn't help. It's still the same problem

Do you have any idea how I could fix my Note 10.1?

Thank you for your aswers.
[Xposed Framework Modules] tkgktyk:
**THIS MOD IS NO LONGER BEING MAINTAINED**

Use Niwatori - One-Handed Mode.

Flying Android - an Xposed module to move the window of Android.

I support the one-handed operation!

Flying Android (FA) is a module of Xposed. FA introduces a movable mode called "Flying" to any screens. In the Flying mode, you can move the window of apps because drag events are intercepted and the whole window containing the Action Bar is dragged. On the other hand, click events are processed normally.

Features

Move the window of activities, dialogs and expanded status bar.

Pin the window after moving.

User Interface

Activities start as the normal mode (the same as before installing FA).

Launch "FA Toggle" to toggle mode, and drag to move.

Tap the outside of apps to back to the normal mode after moving.

Tap the pin to fix position of the window.

FA Toggle just sends a broadcast "jp.tkgktyk.flyingandroid.ACTION_TOGGLE". Because it is an Activity (but no display), you'll feel a time lag until toggle is done. If you want to avoid this time lag, use a background service (other app) to send ACTION_TOGGLE.

Settings

Flying

Speed

Choice the speed in the Flying mode.

Initial position...

Move to this position when you launch FA Toggle. Drag to change the position and press back key to save.

Notify flying

If checked, draw boundary of application while flying.

Flying dialog

If checked, you can fly dialogs. Note that IME is also dialog.
​

Pinning

Use pin

If checked, other settings for pinning are enabled.

Always show pin

Pin is always shown on apps regardless of whether flying.

Pin position...

Show a pin button on this position while flying. You can edit this position by dragging.

Auto pin

Window is pinned automatically. Select a behavior from disabled, when takeoff or after moving.

White list...

Select applications that apply pinning. If not check anything, pin is shown in all apps.

Flying status bar

If checked, you can fly (expanded) status bar.

Reset when collapsed

This is an option for Flying status bar. If checked, reset the state of Flying when status bar is collapsed. This requires Android 4.2 or later.
​

Troubleshooting

Force set black background...

Check apps for clear background if you encounterd a ghost on the outside of app after moving. I saw ghosts on Chrom, Firefox and Feedly.

Black list...

Select applications that don't apply Flying Android for avoiding trouble.
​

TODO

Transparent background -> Pending

Problem (reported): scrolling is partially while pinned.

Problem (reported): black / white lists don't work correctly.

Download

http://repo.xposed.info/module/jp.tkgktyk.flyingandroid

Full Changelog

https://sites.google.com/site/tkgktyk/android/flying-android

Source code

https://github.com/tkgktyk/FlyingAndroid

Special thanks

Xposed framework by rovo89

Reference mods (A-Z):

GravityBox by C3C076

SwipeBack by PeterCxy

XHaloFloatingWindow by zst123

And there is a full text on https://sites.google.com/site/tkgktyk/android/flying-android.

Demo

Demonstration movie for version 0.5.x (on Youtube).

Screenshots

-> after moving

Flying Status Bar

Flying Dialog
[Xposed Framework Modules] tkgktyk:
Release / Status

version 1.1.0 (stable)

Changes:

* Added: notification toggle (thanks to Joe R.)

* Added: animation when takeoff or go home

* Added: Chinese text (zh-rCH, zh-rHK and zh-rTW; thanks to CodeingBoy)

* Added: Japanese text

* Modified: use two-pane layout for settings on the large display devices.

* Changed: the speed setting from list box to edit text.

* Modified: behavior of pin which is always displayed.
[Xposed Framework Modules] tkgktyk:
Tips

For launchers (such as LMT)

You might not be able to launch FA Toggle from launcher if it is registered as app (activity). In such a case, try register as a shortcut. FA supports creating shortcut to FA Toggle from version 0.6.5.

VPN setting

You must add VpnDialogs (com.android.vpndialogs) into blacklist for using VPN setting.

For Feedly

"FA Toggle" and Feedly are not well-matched. Display pin always by setting "always show pin" as workaround.

Appear ghosts on background

Check the problem app in "Force set black background" setting. If checked, the outside of the app after moving is overwritten by black solid to clear background. I saw a ghost on Chrome, Firefox and Feedly.
[Xposed Framework Modules] Aashuk Mehta:
Took so long to come to xda well better late than never. Finally you are here and more people will know about your awesome xposed module☺
[Xposed Framework Modules] pitastrudl:
Some visual information would be helpful for some users. Nice module btw.
[Xposed Framework Modules] Jimmy34742:
I just flashed a completely different ROM to upgrade my S4 to 4.4.2 (CM 11.0), and I still have the same white and black list problem and the same partial-scroll-while-pinned problem.

EDIT: I had to revert to 0.6.2 because the app kept flying my keyboard app, Kii. I always type by swiping, and the flying keyboard made that impossible, which is why I need to black list it. 0.6.2 allows me to black list apps, no problem.
[Xposed Framework Modules] tkgktyk:
Implementation became so complicated by some options, I rewrote hooks for FA. Owing to this, options menu problem is fixed on my phone. I hope that the partial-scroll problem is also fixed. And, I adjusted lists with reference to 0.6.2. But if list's problem is caused by reloading settings without rebooting...
[Xposed Framework Modules] Jimmy34742:
0.6.7: no improvements. I still have the partial-scroll-while-pinned problem, the white and black lists can't be modified, and the new "Reset when collapsed" feature has no effect.

Here's something I discovered: when I install 0.6.2, I can modify the black list. If I then install 0.6.7 without manually clearing data or uninstalling, then 0.6.7 will inherit 0.6.2's black list, and will operate with those apps blacklisted. But 0.6.7 still can't add to or subtract from the black list, and of course I can't use 0.6.2 to edit the white list. If I clear the FA's data and uninstall it using Android Tuner, then reboot, then install 0.6.7, then reboot, it still behaves the same way.

By the way, when testing, I reboot after making any change in the options.
[Xposed Framework Modules] tkgktyk:
"Reset when collapsed" feature hooks a method "PhoneStatusBarView#onAllPanelsCollapsed".　Android 4.1.2 or earlier don't have this method, so not work. Does your ROM have this method? if not so, FA will log "PhoneStatusBarView#onAllPanelsCollapsed is not found." via Xposed framework.

For the partial-scroll-while-pinned problem, does your ROM customize how to render views?　Is the scroll region clamped by the edge of the screen?

For lists problem, I found an another difference between 0.6.2 and newer. It is flag when open preferences. In 0.6.2, preferences is opened with MODE_PRIVATE flag, but new versions use MODE_WORLD_READABLE flag to reload settings without reboot. Are there similar troubles at your ROM's community? Especially about get/putStringSet with MODE_WORLD_READABLE flag.
[Xposed Framework Modules] Jimmy34742:
All my system info is in my signature:

Galaxy S 4 I9500 (CM 11.0 ROM (Android 4.4.2), PhilZ Touch CWM 6.0.4.7)

Galaxy Note 2 N7100 (CM 11.0 ROM (Android 4.4.2), PhilZ CWM Touch 6.0.4.5)

I'm not sure what you mean my "clamped by the edge of the screen." My fly position is at the bottom, and the pin position is center left. Everything looks normal, except the scroll amount is limited to the same number of slots that would have scrolled without flying.

The settings problem is the most serious, so maybe it would be best to try to fix that first. I don't have issues with settings in any other app. Perhaps make it a user option to have immediate settings changes or settings that require reboot? The user would know to choose which option depending on whether or not there are problems. Currently, if I check a box in the black (or white) list and then press "show only black (or white)," it shows nothing, and then the checkbox is cleared when I go back to the regular view. I've never seen this problem anywhere before, and have never seen CyanogenMod users talking about it. The problem is the same on both of my phones.
[Xposed Framework Modules] tkgktyk:
You can see Xposed's logs at "Xposed Installer" -> "Logs". Is there "PhoneStatusBarView#onAllPanelsCollapsed is not found." ?

A question "clamped by the edge of the screen." is an example, sorry. My main question about the partial-scroll-while-pinned problem is previous one. I want to know whether custom ROM has potential of causing this (or these) problem or not.

And for settings... honestly, I don't know what to do if the cause is not CM 11.0.
[Xposed Framework Modules] Jimmy34742:
I saved and then searched my Xposed log, and there is no reference to PhoneStatusBarView#onAllPanelsCollapsed.

I posted a question about the settings issue at the CM 11.0 discussion thread.
[Xposed Framework Modules] H.Pfitzinger:
Touch events don't get through

I was looking hard for any possiblity to contact you, the developer of the Flying Android module, but no chance, so I would be happy if you would contact me.

I am the developer of the App "Field Recorder" and since a couple of days I receive complains from my customers that my App is not receiving any screen touches when Flying Android version 0.6.6 or higher is active. What can we do to solve the problem?
[Xposed Framework Modules] Jimmy34742:
Can your users blacklist your app in FA as a temporary workaround?
[Xposed Framework Modules] H.Pfitzinger:
You experienced that blacklisting is really complicated above 0.6.2 as you already wrote:

But at the moment, some of the customers disabled "Flying Android" and are desperately waiting for an update of Field Recorder. So, I need to contact the developer concerning Android-internal stuff like onTouchEvent() and dispatchTouchEvent() ...

There must be tons of games which also don't work with Flying Android versions 0.6.6 and above.
[Xposed Framework Modules] Jimmy34742:
Yeah, but I thought blacklisting might be working for some people because the dev says it works for him. In that case, it would be good to know which ROM's allow blacklisting, and then that way the dev might have more information to fix the settings problem.
[Xposed Framework Modules] H.Pfitzinger:
I have no chance to get the information which ROM's on which devices do or don't allow blacklisting because these problems appear on customers' devices to which I have no access.

Actually, this is a more general problem, as there are obviously many apps which work, so I am willing to adapt my touch analysis according to the instructions of the developer.

Obviously versions prior to 0.6.6 have been working perfectly. So, the developer should know what the internal change was, that avoids apps to get touch events any longer.
[Xposed Framework Modules] Mos3ab077:
Note3

Plz I need help this module freeze my camera
[Xposed Framework Modules] Jimmy34742:
Can you blacklist your camera in FA as a temporary workaround?
[Xposed Framework Modules] Mos3ab077:
I already did that. But unfortunately it didn't work :(
[Xposed Framework Modules] tkgktyk:
This result says that you hook the method correctly but function is not work. Umm... I have no idea to analyze this problem.

Thank you for your action. I'll wait for solution expectantly.

My Galaxy's camera app has similar problem, also status bar (on Android 4.2 or later). I already fixed them in my local version. It will be uploaded in a few hours later as version 0.6.8.

However those problem has occurred before 0.6.6 unfortunately.

Does your black list behave the same as [MENTION=4155835]Jimmy34742[/MENTION]'s it perhaps? What is the ROM you are using?
[Xposed Framework Modules] Mos3ab077:
I am using Android 4.3 . plz find solution for this bro. I was waitting all your updates. Until 6.4 works normally with my phone. But unfortunately I found my camera always freezing
[Xposed Framework Modules] tkgktyk:
Doesn't blacklist work for all apps or camera app only?

And, does camera stop perfectly? Or doesn't touch event work?
[Xposed Framework Modules] Mos3ab077:
The blacklist is not working for any kind of apps. If I check one app after few seconds it unchecked by itself. And the camera is not working at all freezing completely. No any action working in camera. Even the settings button.
[Xposed Framework Modules] Jimmy34742:
[MENTION=5692104]tkgktyk[/MENTION]: for the black and white list problem, why not simply go back to using the MODE_PRIVATE flag? Or at least make that a user option named "Require reboot after changing settings."
[Xposed Framework Modules] Mos3ab077:
Thanks a lot bro. After your new update the camera is working perfectly. I am really happy because finally the tweak is compatible and working perfectly in my device. You really did a great job. You are the best man :good::laugh:
[Xposed Framework Modules] Jimmy34742:
You mean the black list works for you now?
[Xposed Framework Modules] Jimmy34742:
[MENTION=5692104]tkgktyk[/MENTION]: the clean up background feature was useful--can you bring it back?
[Xposed Framework Modules] tkgktyk:
There are three reasons as follows.

I like this feature very much. Thanks to your suggestion!

I was optimistic about this problem because it is standard function of Android, though its effect is serious.

Now, all of settings are saved to one file. This is standard implementation. Then I want to make such an option however I have to "open" file of settings to decide a way to "open" it. Modification to avoid this issue is trouble. Trouble means that I need a large block of time.

I need this feature only for Chrome, so background of Chrome and apps having similar implementation is automatically clean up in the latest version. Are there another apps to require this feature? Please tell me.
[Xposed Framework Modules] seaskyways:
VPN Issues

I have noticed VPN issues with this module, please check it out
[Xposed Framework Modules] Jimmy34742:
Firefox and Solid Explorer fly OK at first, but then when I move their windows around, it leaves a lot of ghost images. There may be other apps, but these are two that I use often, so I remember them.
[Xposed Framework Modules] Mos3ab077:
yes it works perfectly. Thank you.
[Xposed Framework Modules] faulty_machine:
Blacklisting "VPNdialog" worked for me.

Try it, and maybe describe your problem a lil better?
[Xposed Framework Modules] tkgktyk:
In the next version, Solid Explorer's background will be fixed. But I cannot fix Firefox. Now FA overwrites a background of window by app's default background as workaround, however Firefox's default background is the same as before overwriting. So my workaround has no effect for Firefox.
[Xposed Framework Modules] Jimmy34742:
Thanks. The settings issue is much more serious. Can you produce a test version of 0.6.9 that does setting like 0.6.2 so we can verify the cause of the problem?
[Xposed Framework Modules] Little Zed:
I can't seems to activate this module on Xperia U 2.3.7 firmware... Sorry.. I don't know how to send logs... Just feedback for you..
[Xposed Framework Modules] tkgktyk:
Now, mod is changed radically to fix options menu by menu button so your request is hard. But in new version, I fixed background for Firefox at least.

EDIT: now I release a test version 0.6.11 for reload-timing of settings.

I received some reports that FA causes bootloop on GB. I got a log from [MENTION=3185569]coolkaas[/MENTION] however the exception is caused in Xposed Additions, not FA. I cannot find out the exact reason without a device running GB.
[Xposed Framework Modules] Jimmy34742:
Settings still not working on test version 0.6.11.
[Xposed Framework Modules] onyxogen:
Is this working in the app Feedly for anyone? It seems that it doesn't work for me...
[Xposed Framework Modules] tkgktyk:
That's bad news.:crying:

I fixed the bug in version 0.6.12. However "FA Toggle" and Feedly are not well-matched. Display pin always by new setting "always show pin" as workaround.
[Xposed Framework Modules] Jimmy34742:
The problem with ezPDF has returned: there's some kind of translucent white overlay that prevents seeing the list of documents clearly. That issue was connected with the background feature that was removed, as I recall.
[Xposed Framework Modules] tkgktyk:
I'm sorry, my trial period of ezPDF was done so I cannot fix it immediately.

Is "ezPDF Reader Lite" the same about the problem?
[Xposed Framework Modules] Jimmy34742:
I have the paid app, so I don't know about the Lite. I presume it's the same, but you can check in ezPDF's listing of recent files (in list format), because the problem's very obvious there.
[Xposed Framework Modules] Lord Childe:
Work of genius.

Perfect for one-handed operation on a 7" Tab - Extremely stable, not had a problem yet.
[Xposed Framework Modules] imrude:
how to use without FA toogle, i already try to set the takeover positon : center,bottom, lower left,lower right, but when i swipe up/down/left/right nothing happen, only work when i use the FA toogle, my device is galaxy note 2(running 4.4.2 (dn3 v5 rom), with physical home button, long press show me recent app.
[Xposed Framework Modules] tkgktyk:
About ezPDF on my device...

General - list contents have white background. If disabled FA, wallpaper is shown.

My docs - FA Toggle doesn't work.

Recent - FA Toggle doesn't work. However looks fine expect that.

All PDF - FA Toggle doesn't work.

Web docs - I can fly this page only.

I'll try to fix.

EDIT: I updated to v0.6.14 to fix above problems.

Please start FA Toggle from other launcher app like LMT launcher. If you don't like Pie control, use the pin with "Always show pin" option.
[Xposed Framework Modules] sunny1234590:
keep it up!!!

I am quite impressed with the idea and how it works.. almkst perfect for me...

Thank u for this...!!!
[Xposed Framework Modules] m11kkaa:
sry, but what's the purpose of this if you can't have multiple apps flying around?

great work anyway :)
[Xposed Framework Modules] darkguset:
Any specific installation instructions? Or just install the APK and away we go? Running BeanStalk 4.4.2
[Xposed Framework Modules] tkgktyk:
My concept is to support one-handed operation. It is similar to "one-handed mode" by Samsung or "Layout adjustment" on Google's IME. So my main target is Android smartphones with large size display around 5-inch. Such a display is too large to operate only one-hand but it isn't enough to show multiple windows (apps) for me. Also, I think one-handed operation and multiple windows are exclusive.

Well, the exact reason is that I can't implement the feature :p

I'm sorry if I interpret your question wrongly.

You need two steps.

Install the APK from Xposed repository. This is the same as other mods.

Register "FA Toggle" to your launcher app like pie control, NavRing and so on.

However I don't know about BeanStalk, sorry.
[Xposed Framework Modules] Daedulus Minion:
[MENTION=5692104]tkgktyk[/MENTION] great app. Do you have any plans for updating it to have mutliple widows open? Kind of multi tasking feature. Hope you understand what I am saying
[Xposed Framework Modules] tkgktyk:
No, I have no plans because a great multi-window mod, XHaloFloatingWindow developed by zst123, already exists.
[Xposed Framework Modules] Daedulus Minion:
Thank you for your reply.
[Xposed Framework Modules] evanovici:
Statusbar fly not working

I'm on latest Slimkat, Samsung N7100, and the fly statusbar option is not working for me. Any clues?

Edit: last update got it working
[Xposed Framework Modules] Antitype:
Could you kindly please increase the speed to x5.0? It is bit slow for me on a tablet at x3.0 speed. Thank you.
[Xposed Framework Modules] tkgktyk:
I am relieved. :)

I changed the speed setting up to x9.0 in version 1.0.2 (beta). This change is temporary. I am planning to reduce its variable. For example,

x7.0 (planning)

x5.0 (planning)

x3.0

x2.0

x1.5

x1.0.

Please tell me a value which you need after testing new speed for a while.
[Xposed Framework Modules] Antitype:
I tested the different speeds last night on 2 devices; Nexus 10, Nexus 7. Speed variable x9.0 was the clearly the best choice for the Nexus 7. I felt it a bit slow on the Nexus 10, but it depends on the person using it.

I was up all night testing Flying Android with different apps and then I got to thinking it might be better if Flying Android just allowed users to customize any speed they need. Just warn users higher variables might be unstable and not highly recommended.
[Xposed Framework Modules] tkgktyk:
Thank you for your feedback. I didn't think that the speed is required such a wide range (so I decided to use a few choices for speed).

I'll change the speed option from list-box to direct-input on the next version. Append a warn as you say or print recommended value.
[Xposed Framework Modules] marcusflint:
I tried installing on Gingerbread, im getting problem parsing package error ?
[Xposed Framework Modules] tkgktyk:
This mod doesn't support Gingerbread. I think you cannot install FA on Gingerbread, what do you mean?
[Xposed Framework Modules] marcusflint:
Yeah sorry, my bad. I saw it in the changelog of 0.63 and thought it still supported gb :( would have been cool though
[Xposed Framework Modules] tkgktyk:
You are right. FA supported GB temporary however FA didn't work correctly on GB and caused some bugs on Android 4.X. So I stopped to support it at version 0.6.6, sorry.
[Xposed Framework Modules] qqstars:
Bug on Color OS V1.x based on 4.3

Hi, this component is excellent for us who us the big screen machine.

And I found the bug that, on Color OS V1.x which based on 4.3, after the FA launched in Xposed (Activated but not "fly"), the internal Phone, SMS, Contactor APP will occur the same error: the "..." button menu will not be displayed. After disable the component in Xposed, it works fine.

And, the internal APP "..." button is like that: after click, the entire frame will be move up and will be little shorter. And there is another panel layer displayed on the bottom of the screen. Means, it NOT like the tranditional menu which is an active window or covered layer "flow" on main screen, but have the main screen changed and "attach" the menu into the main screen.

Whatever, the menu contains the operation list, blacklist, settings 3 element only. The first one can be done within long press the screen and the second one can be done within internal blacklist APP. So, I will still use your excellent component and waiting for your updating.
[Xposed Framework Modules] tkgktyk:
Can I see these problems on standard Android 4.3 or other versions? I have no chance to use Color OS.
[Xposed Framework Modules] qqstars:
---

maybe that should not. Because the issue caused by special app with special movement of the menu.

But I have attached the internal MMS apk here. Maybe that should NOT work on other OS but I think that should help you to identify what to do of the menu when the "..." has been clicked.

You can find the apk from attached file.