Database Users

[Xposed][APP][ICS-LP]SwipeBack2 - Finally back alive

After nearly one year's silence, SwipeBack is now back alive, known as SwipeBack2.
SwipeBack2 is the continue of SwipeBack. It has still the basic feature, swipe-to-return gesture, inspired by the library SwipeBackLayout written by @Ikew0ng(a.k.a. IssacWong, 碎星iKe, 碎iKe). It provides a smooth, nature-like and highly customizable swipe-to-return gesture. This module is initially a wrapper of SwipeBackLayout in Xposed, and was welcomed widely by Xposed users. Gradually it has gained much new features that is more than SwipeBackLayout.
If you have installed the old SwipeBack, please uninstall it first, and then you can install SwipeBack2
Features:
* Swipe-to-return gesture
* Per-activity settings which means you are able to customize settings on <strong>each page of each app</strong>
* Experimental hacks for Lollipop (may not work, use with caution, do not turn it on globally)
* More experimental features are coming in future releases.
Note that SwipeBack2 is now only a rewrite and a port to Lollipop (but it still works fine on ICS/JB/KK). It has many work to-do, as:
* Pure-gesture mode (disable scrolling effects, enables compatibility with apps that consist of Fragments but not Activities, and can work with Browsers)
* Fully-costomizable trigger area (at <strong>any</strong> position on the edge, to fix compatibility with apps that has a gesture like drawers already)
* Automatic bug report and crash log submitter
* More (<strong>advices are always welcome)
SwipeBack2 is free software released under the terms of GNU GPLv3. Source code available at https://github.com/PaperAirplane-Dev-Team/SwipeBack
Download:
From Xposed Store: http://repo.xposed.info/module/info.papdt.swipeback
From Google Play Store: https://play.google.com/store/apps/details?id=info.papdt.swipeback
Changelog
1.0.0
- Initial Release
FAQs:
Q: Why renamed to SwipeBack2?
A: Because SwipeBack2 is completely rewritten, and is refactored to have a better stability and flexibility. And another reason is, that SwipeBack (us.shandian.swipeback) is blacklisted by Alipay because of the unsecure SwipeBack, so I just renamed it to SwipeBack2 (info.papdt.swipeback), hoping that it will not be blacklisted any more.
Q: Would you add feature X / fix bug X?
A: Feel free to send emails or open issues on GitHub page. I may not have time to reply to you all, but I will take a look at bug reports and feature requests and have the resonable ones implemented in new releases.
Q: SwipeBack is great! Do you accept donations?
A: Well, not now.
XDA:DevDB Information
SwipeBack2, ROM for all devices (see above for details)
Contributors
PeterCxy
Source Code: https://github.com/PaperAirplane-Dev-Team/SwipeBack
ROM OS Version: 5.0.x Lollipop
Version Information
Status: Beta
Created 2015-03-31
Last Updated 2015-03-31

[TOOL]Cloud_Commander Ver1.3 (Blue Builds) [BETA]

Hi guys,
Cloud_Commander is an android shell code tool that can reserve android shell scripts from common tools like rooting tools, password cracking tools e.g John the reaper.
Most tools are bundled up by devs from around the globe and shared to everyone.
Currently the available commands are not yet polished but some still work and are being revised on daily basis.
Anybody can add a command provided he has created a dev page that explains the functionality of his tool/command.
This software will contain almost every android tool that is currently in use and outdated since Devs will merge their own stuff here.
There are two ways to add commands:-
You can use the command creator from the toolbar in the menu.
However you can create commands straight into the xml files which this software uses.
The commands created in this software will be stored in our server and used by everyone who updates the tables, if you use the other method (XML editing) which is not recommended, please share you files with your users.
All bugs should be reported to [email protected]
NB: PLEASE DON'T SEND COMMANDS THAT ARE NOT TESTED PERSONALLY !
SCANNED WITH BIT-DEFENDER ANTI-VIRUS
After downloading make sure you update the tables the press refresh and also checkout setups to install tools.
Version 1.2 does not update tables since we shifted our servers to cloudflare and has some minor engine flaws thus it's obsolete.
Download the latest version to maintain commands compatibility.
DOWNLOAD_HERE VER1.2
DOWNLOAD_HERE VER1.3
XDA:DevDB Information
Cloud_Commander Ver1.3 (Blue Builds) [BETA], Tool/Utility for all devices (see above for details)
Contributors
kenkitt
Version Information
Status: Testing
Current Beta Version: 1.3
Beta Release Date: 2016-01-30
Created 2016-02-02
Last Updated 2016-02-02

[TOOL] Android Scriptmaker - Make flashable .ZIP(s) from stock ROM

Android Scriptmaker is a little software piece which is able to make the required lines to set the right permissions in a recovery script.
The idea behind this script is to be able to make a flashable .ZIP out of any ROM, such as stock ROMs, custom ROMs that are unavailable anymore, etc.
This script is COMPLETELY compatible with the Unix Shell without any previous modifications.
Required installed software: grep, wc and cat. The script will test if your device lacks support of any of them.
Read more (documentation, download and usage): https://github.com/FacuM/android_scriptmaker
XDA:DevDB Information
Android Scriptmaker, Tool/Utility for all devices (see above for details)
Contributors
facuarmo
Source Code: https://github.com/FacuM/android_scriptmaker
Version Information
Status: Stable
Created 2017-02-03
Last Updated 2017-02-03

Batik(TWRP)Treble-non Treble Alpha-02-kenzo

BATIK RECOVERY OFFICIAL ALPHA-02 Kenzo
Support : TREBLE | NON TREBLE
Changelog :
- Initial build base TWRP-3.2.2.x
- Upstreamed Source Omni Oreo
- Add Featured : Extra Tools
Link :
BATIK RECOVERY
ALPHA-02
TREBLE | NON TREBLE
CHANGELOG :
- Initial build base TWRP-3.2.2.x
- Upstreamed Source Omni Oreo
- Add Featured : Extra Tools
DOWNLOAD :
Kenzo - https://t.me/ZHANreport/7161
#batik #recovery #kenzo
Source : ZHAN Project
• Channel Blog nTu21
• Channel Youtube Blog nTu21
This is not my work I am just sharing
Working perfectly all about good.?

why alpha? when can we expect a stable build?

shawon11 said:
why alpha? when can we expect a stable build?
Click to expand...
Click to collapse
Sorry bro but this is not my work I am just sharing good TWRP:good:

Azizbagwan said:
BATIK RECOVERY OFFICIAL ALPHA-02 Kenzo
Support : TREBLE | NON TREBLE
Changelog :
- Initial build base TWRP-3.2.2.x
- Upstreamed Source Omni Oreo
- Add Featured : Extra Tools
Link :
BATIK RECOVERY
ALPHA-02
TREBLE | NON TREBLE
CHANGELOG :
- Initial build base TWRP-3.2.2.x
- Upstreamed Source Omni Oreo
- Add Featured : Extra Tools
DOWNLOAD :
Kenzo - https://t.me/ZHANreport/7161
#batik #recovery #kenzo
Source : ZHAN Project
• Channel Blog nTu21
• Channel Youtube Blog nTu21
This is not my work I am just sharing
Working perfectly all about good.?
Click to expand...
Click to collapse
can u explain me what is treble?? advantage of treble??
i see on RN5 development there is many treble rom & treble twrp..

robbayani said:
can u explain me what is treble?? advantage of treble??
i see on RN5 development there is many treble rom & treble twrp..
Click to expand...
Click to collapse
Project Treble is the Answer
The reason manufacturers have such a hard time pushing out prompt updates is because of all the work that has to go into getting the operating system to communicate with the hardware.
Traditionally, it worked something like this: the OS framework and low-level software were all part of the same code. So when the OS got updated, this low-level software–technically referred to as vendor implementation—also had to get updated. That’s a lot of work.
So, starting with Android 8.x (Oreo), Google separated the two. That means the Android OS itself can be updated without having to touch the vendor implementation. That, in turn, can be updated by itself if needed.
To put that in full context, before an update can be pushed out to an Android 7.x (or earlier) device, not only does the Android OS code have to be updated, but so does the low-level hardware code, which is generally maintained by the chip maker. So, for example, if Samsung wants to push an update to one of its phones, it has to wait for Qualcomm (or whoever made the chip) to update its code to work with the new Samsung code. That’s a lot of wheels turning at once, and each one is dependent on the other.
With Android 8.x and beyond, it won’t be like this anymore. Since the core hardware code is separate from the OS code, device manufacturers will be free to update their software without having to wait for the silicon maker to also update its code.
This should dramatically speed up the update process—in theory, at least. Updating devices will still be in the manufacturer’s hands, and since the first Oreo devices outside of the Google-maintained Pixel line are just now rolling out, we haven’t yet had a chance to fully see this in practice. Hopefully, it actually makes a significant change to the speed in which updates are written and pushed out.
Will My Device Benefit from Project Treble?
Now that’s the million dollar question, right? Unfortunately, the answer isn’t so simple (surely you didn’t expect it to be). That said, here are some facts:
If your device never gets updated to Oreo, it will never get Project Treble. No way around that. Sorry.
If your device does get updated to Oreo, it’s still not required to support Treble—that’s up to the manufacturer.
If you buy a new phone that runs Oreo out of the box, it is required to support Treble out of the box.
In short: Treble support on updated systems is still up to the manufacturers, but new Oreo devices will be required to support Treble moving forward.
So, for example, the Pixel 2 already supports Project Treble. The forthcoming Galaxy S9 will also support Treble out of the box. Google also updated the Pixel 1 to support Treble, but it’s unfortunately it looks like Samsung left it out of the Oreo build for the Galaxy S8.
If you’re curious about your own device, Android Police has a running list of all devices that will get Treble support, as well as a which ones will get updated to Oreo without Treble.
Android OS updates have been a constant point of contention for many years now, so it’s good to see Google finally addressing the issue. With any luck, this will put all Android devices closer to parity with Apple in terms of device updates.

MagiskFixes (Fixing Magisk with Magisk)

Welcome to the MagiskFixes XDA thread!
This module applies a few patches to help Magisk work on GSIs, and maybe a few other devices (targeting Motorola oem at the moment, but more will be added as I get feedback). Obviously it's neither perfect nor universal yet.
Currently targets Motorola and Google devices running either phh or Erfan GSIs, but and Motorola devices running stock.
If you have a fix for a specific device, let me know here! I'll be happy to add it in
As usual, I'm not responsible for any bricking of devices, or things caused by that. No cats were harmed in the making of this module
Currently implemented fixes
- Added a few missing libs for GSIs
- Nuked a Motorola specific boot script (this may depend on how early the module mounts. May need reevaluated on execution)
- Add key layout for phh gsi on Google devices
V1. 2+ uses MMT-ex, and earlier versions used Unity
Thanks to @topjohnwu for Magisk and @Zackptg5 for the template
XDA:DevDB Information
MagiskFixes, Tool/Utility for all devices (see above for details)
Contributors
linuxandria
Source Code: https://github.com/Magisk-Modules-Repo/mgskfixes
Version Information
Status: Stable
Current Stable Version: 1.2.2
Stable Release Date: 2020-03-01
Created 2019-10-03
Last Updated 2020-03-17

Does it work with Moto x4 on PE?(Android 10)

Can you add fingerprint support for gsi on realme 3 pro (rmx1851)

What does should it fix on Motos?
I've two Moto Z2 Force with stock Pie on board and they seems to work fine with Magisk and EdXposed too...
What does should be addressed. on Motos by this module?!?
I'm interested and I can help with testing if needed...

Compatable with Metro PCS Moto e5 Play XT 1921-3 stock rom, rooted with Magisk?

If you're not going to respond to any questions or post about updates, etc then what's the actual point in this thread @linuxandria ?

Listy2021 said:
If you're not going to respond to any questions or post about updates, etc then what's the actual point in this thread @linuxandria ?
Click to expand...
Click to collapse
I've said it before in my other threafs I am significantly more active on telegram than XDA

Thejayyadav said:
Can you add fingerprint support for gsi on realme 3 pro (rmx1851)
Click to expand...
Click to collapse
Not unless I know what's needed

V1. 2.2 released!
Changelog:
- Rework fixes for generic and Motorola
- Add fixes for Google devices (only supports phh GSIs for now)

Wow greate idea

What exactly is fixed with this module the description is very vague if anyone could enlighten me it would greatly be appreciated
Sent from my Phh-Treble vanilla using Tapatalk

@linuxandria might you help out with sepolicy? kindly head over to my post
https://forum.xda-developers.com/t/edxposed-framework-not-recognizing-riru.4334587/post-86405127