Android P NotoColorEmoji Replacerget Android P's emojis on any Android device running Android 5.0+!
Hi all,
This is my first Magisk module, and with a very simple purpose: Getting the newest Android P emojis working in your device running Android 5.0+ with Magisk (as a possibility to install them systemlessly), or replacing the actual font using the included Flashable Zip.
How did it look?
Old Emojis:
Android O's Public Beta 1 Emojis:
Prerequisites
Magisk v11.6 or higher, in case of using the Android O Magisk Module.
Magisk v15.0 or higher, in case of using the Android P Magisk Module.
A working custom recovery (TWRP, PhilZ, etc.)
Tested on
Both module and flashable Zip had been tested on AOSP 7.1.1, AICP 7.1.2 and RR_N, working perfectly in the three scenarios. However, except for the 'racial' emojis, they should work in any Android 5.0+ device.
If you own a device which is running Android between 5.0 and 6.0.1, please kindly let me know if the module works as expected
Downloads
Magisk Module - from the attachments, in the future in the Magisk Manager repository (once topjohnwu adds it!), and from my server.
Flashable Zip for System A partitions - from the attachments, and from my server.
Flashable Zip for System A/B partitions - from the attachments, and from my server.
Differences between Magisk Module and Flashable Zip versions
Magisk Module - Requires Magisk installed, and will work systemlessly, without modifying the system partition of your device (recommended!)
Flashable Zip - Replaces the system font inside your device, so making a backup of it before is highly recommended.
Installation instructions
Magisk Module (via Magisk Manager) - Download it from the attachments or from my server. Open the Magisk Manager app, go to the Modules section and hit the + button. Choose the downloaded Zip and install it. Once done, reboot your device as suggested by Magisk Manager.
Magisk Module (via Custom Recovery) - Download it from the attachments or from my server. Reboot your device into recovery mode, then choose Install, locate the downloaded Zip and flash it.
Flashable Zip - Download the version depending on your device's needs, either from the attachments or from my server. Reboot your device into recovery mode, then choose Install, locate the downloaded Zip and flash it.
Troubleshooting
I've seen some people that wiped their /data partition (aka Wipe Data/Factory reset), and thus losing their magisk.img and all their modules, since they're stored there.
This means: If you factory reset your device and didn't flash Magisk flashable Zip again, none of the modules will be able to work.
To fix it, flash Magisk flashable zip again, then flash all your modules, and it should all be working again.
Apart from this I've also seen that Substratum themes custom fonts override the system fonts, so maybe there's another reason why it sticks to the old font. If that's the case, try removing them and see if the new emojis display or not.
Much love <3
Cant install it, there's an error when I flash using TWRP wich says 'Status Error 7: Tu madre'
What can I do?
Enviado desde mi Xperia M2 Aqua mediante Tapatalk
iFlashed said:
Cant install it, there's an error when I flash using TWRP wich says 'Error 7: Tu madre'
What can I do?
Enviado desde mi Xperia M2 Aqua mediante Tapatalk
Click to expand...
Click to collapse
Hi Daniel, nice to see you here too
Have you tried doing "sudo rm -rf /" already?
NOTE in case it wasn't clear enough: This is obviously a banter...
linuxct said:
Hi Daniel, nice to see you here too
Have you tried doing "sudo rm -rf /" already?
NOTE in case it wasn't clear enough: This is obviously a banter...
Click to expand...
Click to collapse
Nice! Working now thanks for your contribution!
Enviado desde mi Xperia M2 Aqua mediante Tapatalk
Nice for those interested, hope you'll do a Magisk emoji replacer to have Android Nougat Emoji's on Android O Final release. I don't really like the new one, it seems, to me, that we're going back to the old emojis from the skeuomorphic Apple Era.
Bokoblin said:
Nice for those interested, hope you'll do a Magisk emoji replacer to have Android Nougat Emoji's on Android O Final release. I don't really like the new one, it seems, to me, that we're going back to the old emojis from the skeuomorphic Apple Era.
Click to expand...
Click to collapse
Firsts things first, let's hope that the (already-in-the-works) Magisk v13.0 is fully compatible with Android O final release, or if it isn't, that topjohnwu doesn't need much effort to get it working . And once that happens, try to get the old-school emojis back with it.
However, I have to note the following: In Android O, there's a new feature called EmojiCompat, which is a library that allows emojis to be downloadable per-app needs. This means that, if a developer includes the library, it will try to download the newest possible emoji fonts directly from Google and apply them inside the app.
Here's an example in Allo.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Those [x] symbols in the right screenshot, using the EmojiCompat library, would convert into a taco and a unicorn again just like the sender sees them, no matter what version of Android you're running (starting from Android 4.4+).
Providing this, it's possible that, if apps start to implement it, you'd see the newest emojis although you systemlessly replaced them by the old-school ones...
Have this link as reference: https://developer.android.com/preview/features/emoji-compat.html
linuxct said:
Firsts things first, let's hope that the (already-in-the-works) Magisk v13.0 is fully compatible with Android O final release, or if it isn't, that topjohnwu doesn't need much effort to get it working . And once that happens, try to get the old-school emojis back with it.
However, I have to note the following: In Android O, there's a new feature called EmojiCompat, which is a library that allows emojis to be downloadable per-app needs. This means that, if a developer includes the library, it will try to download the newest possible emoji fonts directly from Google and apply them inside the app.
Here's an example in Allo.
Those [x] symbols in the right screenshot, using the EmojiCompat library, would convert into a taco and a unicorn again just like the sender sees them, no matter what version of Android you're running (starting from Android 4.4+).
Providing this, it's possible that, if apps start to implement it, you'd see the newest emojis although you systemlessly replaced them by the old-school ones...
Have this link as reference: https://developer.android.com/preview/features/emoji-compat.html
Click to expand...
Click to collapse
Yey, finally they did something about it haha, that's awesome. Thanks for the module btw (I personally don't like stock Google emojis tho xD)
Awesome. Good work on the module. Keep it up.
Great Emojis thanks for this running LineageOS 13.0 Sprout device.
Working on LG G5 with Android 7.0
Thanks for the good work.
Working without issues on LG G5 with Android 7.0
Applied it but the emoji haven't changed. I clear the data of the keyboard. Does it work with swiftkey app?
Sent from my Moto X Play using Tapatalk
I Will test on s8+ now
K.khiladi said:
Applied it but the emoji haven't changed. I clear the data of the keyboard. Does it work with swiftkey app?
Sent from my Moto X Play using Tapatalk
Click to expand...
Click to collapse
I'm not sure if Swiftkey bundles their own emoji set, and I've only tried on Google Keyboard. Try downloading Google's Keyboard (AOSP Keyboard is also valid), and see if they changed there or not.
However, although it doesn't necessarily need to be related to this case, I've seen some people that wiped their /data partition (aka Wipe Data/Factory reset), and thus losing their magisk.img and all their modules, since they're stored there.
This means: If you factory reset your device and didn't flash Magisk flashable Zip again, none of the modules will be able to work.
To fix it, flash Magisk flashable zip again, then flash all your modules, and it should all be working again.
works great on my lineageOS 14.1 kenzo
Just installed it on my Nexus 6P running dirty unicorns 11.3.
Sent from my Nexus 6P using XDA Labs
Flashed via TWRP. All good ? Xperia ZR stock.
Thanks for sharing.
Just tested the zip and flashed true twrp and cleared cache but not working for me in latest dirty unicorn on my oneplus 3.
Did try twice and with google aosp keyboard and swift keyboard but no luck with both off them.
Regards ysco..
Does the phone has to be rooted in order for this to work?
ysco said:
Thanks for sharing.
Just tested the zip and flashed true twrp and cleared cache but not working for me in latest dirty unicorn on my oneplus 3.
Did try twice and with google aosp keyboard and swift keyboard but no luck with both off them.
Regards ysco..
Click to expand...
Click to collapse
Can you please try the following?
linuxct said:
However [...], I've seen some people that wiped their /data partition (aka Wipe Data/Factory reset), and thus losing their magisk.img and all their modules, since they're stored there.
This means: If you factory reset your device and didn't flash Magisk flashable Zip again, none of the modules will be able to work.
To fix it, flash Magisk flashable zip again, then flash all your modules, and it should all be working again.
Click to expand...
Click to collapse
Mania626 said:
Does the phone has to be rooted in order for this to work?
Click to expand...
Click to collapse
Root =/= having a working recovery. It's specified in the OP that all you need is a working Custom Recovery like TWRP (and magisk if you're doing it systemlessly) in order to get it working.
Mania626 said:
Does the phone has to be rooted in order for this to work?
Click to expand...
Click to collapse
Yes
Related
SPEC-GAPPS KitKat-4.4.4 Package
SPEC-GAPPS is a Specialized Google apps package built with Performance and Graphic enhancing mods.
Package follows the same rules as any gapps package. Follow your Roms instructions. Unless instructed otherwise.
Credits and Thanks to...
Jeeko for Pure Performance X Zeno Edition
(zeppelinrox for his default.prop of V6
ImbaWind for his parts of Adrenaline Engine
Exit_Only for his Turbo concepts, there aren't any parts of his work in mine
idcrisis for his CrossBreeder
nicolassp for his S1_Optimize
L.E.D 26 for his support)
Sony for Bravia Engine 3 X-Reality
VillainRom team for vrtheme system
XDA, Cyanogen, Google.
Plus Anyone I forgot.
******************************************
Spec-Gapps-4.4.4-Basic-V2.6
10/11/2014
Built with no mods included.
For those who want a clean system or want to install
and test other modifications.
Dalvik Enabled at boot
Art Compatible OTA Compatible
Added and Edited backup scripts for better OTA compatability
Flash these once and all apps and files installed should survive OTA updates.
4.4.4 KitKat supported
Updated Files from 4.4.4
CM11s OnePlus One Camera with Clear View 38R
CM11s OnePlus One NextGallery
(Sync+Share photos from Facebook, Google+, and more)
Android L Google Keyboard with Material theme.
(Leave on default theme for Cm11 themes)
Google Playstore,Services,YouTube,Google+,Maps,Gmail,Google Keyboard,Keep,Books,Movies,Music
Download Here-Spec-Gapps-4.4.4-Basic-V2.6
Spec-Gapps-4.4.4-Basic-V2.5
8/26/2014
Built with no mods included.
For those who want a clean system or want to install
and test other modifications.
Dalvik Enabled at boot
Art Compatible OTA Compatible
Added and Edited backup scripts for better OTA compatability
Flash these once and all apps and files installed should survive OTA updates.
4.4.4 KitKat supported
Updated Files from 4.4.4
CM11s OnePlus One Camera with Clear View
CM11s OnePlus One NextGallery
(Sync+Share photos from Facebook, Google+, and more)
Android L Google Keyboard with Material theme.
(Leave on default theme for Cm11 themes)
Google Playstore,Services,YouTube,Google+,Maps,Gmail,Google Keyboard,Keep,Books,Movies,Music
Download Here-Spec-Gapps-4.4.4-Basic-V2.5zip
Flash Instructions:
1.Flash Rom with Gapps in Recovery.(Dont forget to wipe.)
2.Reboot and Enjoy!
Spec-Gapps-4.4.4-BetaV2-XXX
8/1/2014
Dalvik Enabled at boot
Art Compatible
4.4.4 KitKat supported
Updated Files from 4.4.4
CM11s OnePlus One Camera
CM11s OnePlus One NextGallery
(Sync+Share photos from Facebook, Google+, and more)
Android L Google Keyboard with Material theme.
(Leave on default theme for Cm11 themes)
Pure Performance X -Edited
Added Some more Scripts for Performance
SD Card and Net boost tweaks
Buildprop tweaks
Bravia Engine X-Reality
Darkscript101 + More
Google Playstore,Services,YouTube,Google+,Maps,Gmail,Google Keyboard,Keep,Books,Movies,Music
Download Here-Spec-Gapps-4.4.4-BetaV2-XXX.zip
Flash Instructions:
1. Enter Recovery, Wipe, Install Rom and SuperSu Root(If Necessary) then reboot device.
2. After reboot go back to recovery and flash Spec-Gapps. Some scripts need this in order to work properly.
3. Enjoy
Flash http://download.chainfire.eu/supersu if you lose root otherwise mods won't stick.
If you update your rom by either flashing or ota you will need to reflash Spec-gapps.
Wipe if you run into any issues.
Any issues let me know.
Feedback is appreciated.
********************************************
*****-Disclaimer-*****
Flash this at your own risk. Only you are responsible for your device.
Thank you, Enjoy!
Reserved
Thanks, how about GooglePlay Wakelocks after flashing this Gapps, i have done several modifications with Autorun Manager and Android Tuner. Must i do this again, to solve the Wakelock Problem on Firmware 25R ?
I wouldn't flash this with the stock firmware. Just aosp roms. But you could give it a try if your brave. And I haven't had any issues with wakelock.
Exclusive Member of the OnePlus One Club
By the way, your OP post links to SuperSU 2.01. The latest SuperSU is 2.02 http://download.chainfire.eu/452/SuperSU/UPDATE-SuperSU-v2.02.zip or if you want to simplify things direct it to http://download.chainfire.eu/supersu and it'll automatically link to the newest SuperSU
Yeah I need to update that. I just copy and pasted from my other thread. And changed a few things. Thanks for the top about the link too.
Exclusive Member of the OnePlus One Club
Just to let you know, the add-on.d script doesn't back up the CM camera. Found out when I updated my opo today to the latest nightly.
Sent from my Nexus 7 using Tapatalk
stab244 said:
Just to let you know, the add-on.d script doesn't back up the CM camera. Found out when I updated my opo today to the latest nightly.
Sent from my Nexus 7 using Tapatalk
Click to expand...
Click to collapse
When you say CM camera (11S camera)... normally you would just install the CM camera as a user app and not system app.
zephiK said:
When you say CM camera (11S camera)... normally you would just install the CM camera as a user app and not system app.
Click to expand...
Click to collapse
The zip installs it as a system app and thus it gets deleted if it isn't included in the back up script.
Sent from my bacon
stab244 said:
The zip installs it as a system app and thus it gets deleted if it isn't included in the back up script.
Sent from my bacon
Click to expand...
Click to collapse
Hm well you don't really need it to be a system app, you can just sideload the app as a user app and it works fine.
https://mega.co.nz/#!d0EHGLDZ!FW4an4m_9ESnFw8jotLdxmWLYuS9sRxWZe9MXzesuOg
You can just install that as a regular app and then on rom updates, it won't delete.
zephiK said:
Hm well you don't really need it to be a system app, you can just sideload the app as a user app and it works fine.
https://mega.co.nz/#!d0EHGLDZ!FW4an4m_9ESnFw8jotLdxmWLYuS9sRxWZe9MXzesuOg
You can just install that as a regular app and then on rom updates, it won't delete.
Click to expand...
Click to collapse
I understand what you're saying but since OP's zip installs into /system, he (or she) might as well add those items into the backup script. Much easier for users of this gapps package. There also needs to be an entry for the gallery too.
Sent from my bacon
stab244 said:
I understand what you're saying but since OP's zip installs into /system, he (or she) might as well add those items into the backup script. Much easier for users of this gapps package. There also needs to be an entry for the gallery too.
Sent from my bacon
Click to expand...
Click to collapse
I'll add those into the backup script.
Exclusive Member of the OnePlus One Club
Updated to BasicV2.1. Edited 70-gapps.sh to include all apps and files installed by package to survive OTA updates.
BetaV2 will remain as is for now.
It is compatible with slimkat rom?
I used this with Slim before. As for ota. Not 100% sure. It extracts whatever's in addon folder and runs it. I believe it should work with ota. Even though they named there script 80-gapps. Their backup script doesn't seem to look for a specific addon script. Same goes for PA. Worst case you'll have to reflash your gapps. Let me know if you've tried. Or someone correct me if I'm wrong.
Sent from my A0001 using Tapatalk
Him it looks pretty good for me but...
Can I get special symbols in your google keyboard ? I mean long press on letters make a special symbols..
It's not my Keyboard. It's pulled from the Android L preview. It's Google built.
Exclusive Member of the OnePlus One Club
darkchyldx101 said:
It's not my Keyboard. It's pulled from the Android L preview. It's Google built.
Exclusive Member of the OnePlus One Club
Click to expand...
Click to collapse
i see...
do you know, is there way to get special symbols on "L" keyboard?
You can try the PC layout. It also adds the number row. The symbols don't show but it's there when you long press.
To enable PC layout on the stock Google keyboard, go to its settings, and then navigate to Advanced Settings. Tap the Custom Input Styles option, and then click on Add Style. Now, select your language, and select PC from the Layout drop-down menu.*The Google keyboard with the PC layout actually shows up as a different keyboard altogether, so you will need to switch to it before you can use it.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Exclusive Member of the OnePlus One Club
@DARKCHYLDX101 can you update these with newest update
Prerequisite
Magisk is required to be installed on your device!Magisk - The Universal Systemless Interface
Support Devices
All Magisk compatible devices
Downloads
My Xposed zip is universal across all architectures and Android versions.
https://androidfilehost.com/?fid=1395089523397956629
Install Guide
Install the XposedInstaller in the attachments
Follow the instructions in the Magisk release thread to install Magisk on to your device
Install Xposed within Magisk Manager's Download Section, or download the zip and flash in custom recovery
For uninstallation, remove the Xposed Magisk Module within Magisk Manager
Systemless Xposed does not pass SafetyNet!!!
Credits
@rovo89 for creating Xposed
Source
All binaries are downloaded and repacked from either places:
Official build from rovo89
I did not recompile/change anything how Xposed works, the behavior should be 100% identical to original sources, if you experience any Xposed issues, please directly report to the original threads.
Changelog
v87.0
- Include fix from rovo89 to prevent bootloops in the latest security patch
- Android 5.1 (SDK 22) was broken after one Magisk upgrade, it's now Magisk version independent
v86.6 (Downloaded 126324 times)
- Update to support the new repo system of Magisk
- Fixed incompatibility of suhide
v86.5 (Downloaded 174328 times)
- Update for the new API of Magisk v4
- NOTE: In order to update to Magisk v4, you are required to uninstall Magisk completely before upgrading. Please look at the main Magisk thread for more info
v86.4 (Downloaded 16246 times)
- Revert the disable to not mount method for Android Pay
- Fixed alt version script typo
v86.3
- Use Magisk as dependancy
- Support all the way back to Android 5.0
- Android Pay
v86.2 (Downloaded 30608 times)
- Script updates, more info here
v86.1 (Downloaded 10185 times)
- Minor fixes, release notes here
v86.0
- Massive update, see release notes here
v85.7 (Downloaded 15774 times)
- Hot fix for some devices which breaks proper init commands
v85.6
- Add SELinux label when executing script, should fix the few devices that aren't working
- Massively improve the script to handle /cache to /data migration (the rare case when /data isn't available in TWRP)
- Add Pixel C support (not-tested)
- Combine all architecture into an All-In-One flash zip, users will only need to be aware of their own Android version
v85.5
- Combine image mount and bind mount into one single script, should be more reliable and cleaner, hopefully it will fix ALL previous issues
- Add more logs to boot for debugging
- Add SDK 22 support (un-tested!!)
v85.4
- The mounting method should now support all devices
- The installer will now merge Xposed Image if possible, so feel free to place your own files under /xposed
v85.3
- Improved compatibility for some recoveries with incorrect libraries
- Changed the method to mount xposed.img, hopefully will fix issues on some devices
v85.2
- Separate Systemless Xposed from SuperSU. It now uses it's own image in data (/data/xposed.img)
- Won't effect SuperSU anymore. Both are now working independently
- Massively updated flash script, should be more reliable (e.g. Prefer sukernel in su.img over bundled binary)
- (Derived from Wanam's update) Add Huawei theming engine support (details); Ensure the recompilation on Huawei EMUI Roms (details).
v85.1
- Fixed flash script not installing files issue
v85.0
- Initial release
Wow! I will test it as soon as possible!
If you agree I can merge your changes in my build and add these zip files in the available zip files list to download
Updated the OP for more information
Thanks for experimenting with this!
I haven't installed it yet - I'm currently running XtreStoLite 3.1.1 with systemless SuperSu 2.74 and a conventional Wanam Xposed arm64 v85 installation on zeroflte (Galaxy S6).
Even with the conventional Xposed installation, toggling off Xposed in the latest rev (5/29) of @DVDandroid's installer and rebooting allows Android Pay to work. ART cache didn't rebuild either as noted in your post.
This is great progress!
5upon said:
Thanks for experimenting with this!
I haven't installed it yet - I'm currently running XtreStoLite 3.1.1 with systemless SuperSu 2.74 and a conventional Wanam Xposed arm64 v85 installation on zeroflte (Galaxy S6).
Even with the conventional Xposed installation, toggling off Xposed in the latest rev (5/29) of @DVDandroid's installer and rebooting allows Android Pay to work. ART cache didn't rebuild either as noted in your post.
This is great progress!
Click to expand...
Click to collapse
Oh really?!
This is cool, it seems that the Safety net check is not that strict lol
Any one test this xposed in Galaxy S7 ?
Edit.
I try on S7 and no framework loaded. ;-(
koko115 said:
Any one test this xposed in Galaxy S7 ?
Edit.
I try on S7 and no framework loaded. ;-(
Click to expand...
Click to collapse
Please follow the OP for bug report, thanks.
Send me your boot image after flashing the zip.
topjohnwu said:
Please follow the OP for bug report, thanks.
Send me your boot image after flashing the zip.
Click to expand...
Click to collapse
https://drive.google.com/file/d/0B86MsntyFnN1ZF9vbFAzM2pHemM/view?usp=drivesdk
koko115 said:
https://drive.google.com/file/d/0B86MsntyFnN1ZF9vbFAzM2pHemM/view?usp=drivesdk
Click to expand...
Click to collapse
Your boot image seems good.
What is your actual issue?
The framework doesn't work? Did you install the Xposed Installer stated in the OP (it has been updated)?
If you have all the things above, please post the screenshot go the Xposed Installer modules section, thanks
5upon said:
Thanks for experimenting with this!
I haven't installed it yet - I'm currently running XtreStoLite 3.1.1 with systemless SuperSu 2.74 and a conventional Wanam Xposed arm64 v85 installation on zeroflte (Galaxy S6).
Even with the conventional Xposed installation, toggling off Xposed in the latest rev (5/29) of @DVDandroid's installer and rebooting allows Android Pay to work. ART cache didn't rebuild either as noted in your post.
This is great progress!
Click to expand...
Click to collapse
This is actually not true on my side.
Disabling it will not make android pay to work. I just tested it.
I have to use systemless Xposed to pass safety net check.
topjohnwu said:
This is actually not true on my side.
Disabling it will not make android pay to work. I just tested it.
I have to use systemless Xposed to pass safety net check.
Click to expand...
Click to collapse
Hmm. How did you test? I used to get blocked by SafetyNet when I tried to add a card. Today, after deactivating Xposed and rebooting, I was able to add a card, but I haven't tried to make a purchase yet.
I'll switch to systemless Xposed the next time I update my ROM. Hopefully it will become the default install method. @rovo89 mentioned the possibility of going systemless a while ago but said he didn't plan to work on it.
topjohnwu said:
Your boot image seems good.
What is your actual issue?
The framework doesn't work? Did you install the Xposed Installer stated in the OP (it has been updated)?
If you have all the things above, please post the screenshot go the Xposed Installer modules section, thanks
Click to expand...
Click to collapse
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I'm still not sure from reading the op or any posts whether ap works with this. Anything conclusive?
i Found one bug
i founded one bug, is in update-binary, doesnt extract xposed.prop ,xposedbridge.jar and libxposed_art.so.
In /su i dont see any xposed files
---------- Post added 30-05-2016 at 12:04 AM ---------- Previous post was 29-05-2016 at 11:40 PM ----------
I manually put missing this 3 files to /su and works great. THX
Thank you @koko115
OP updated with a version that should be working.
I forgot to put spaces in the previous release
The x86 version has a few downloads now.
Is the x86 working as expected? Can anyone report if it works?
I'm getting hung up on this step: "Flash systemless Xposed"
Would that be to say reboot into TWRP, press Install and pick the arm64 for my HTC 10?
Thanks!!
UPDATE: That's exactly what I did, worried I bricked my phone there for a second the boot logo took very long but now it's optimizing all the apps and starting up.
UPDATE 2: Success!!
Works great! Only the app says xposed 85.0 is installed but it's actually 85.1. Probably something you didn't edit because twrp also thought it was 85.0 [emoji2]
Sent from my SHIELD Tablet K1 using XDA-Developers mobile app
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
OMNIROMUNOFFICIAL
He guys. I managed to find the time to port Omni to the z5c. Since it compiled, booted and works well (except camera) I thought I would upload to share. My goal being that we would have greater choices available adding to Stock, CM and AOSP roms. Note: This is not a developer thread. I'm just sharing this because it worked and others might be interested.
About Omni:
The goal of Omni is to experiment with Android development because we enjoy it. Omni isn’t better, just different. It’s another option for the billion Android users out there. Android (vs. iOS and every other mobile OS) has thrived on options as well as the gigantic, talented development community that has emerged to build those options. That’s the beauty of Android – that you can pick and choose from a smorgasbord of devices with varying features and functionality. https://omnirom.org/
BIG THANKS to...
@humberos - for creating the first omni device tree (that I know of) for the kitakami family. (my suzuran dev tree is largely his work)
@CTXz - for all the work he and the kitakamy dev team have done/will do for CM that will find its way in to the omni flavour of aosp.
@superR - I used his kitchen to make the zip file with sparse dat .img
The Sonyxperiadev team for releasing their sources to the public
The good..
Compiled with latest camera and vendor blobs provided by Sonyxperiadev.
Full working omni features
- Comes with latest TWRP packed in the kernel
- Advanced reboot menu - boot directly in to twrp or boot-loader, or reboot and hold up when led turns purple)
- Omni switch
-Advanced power menu (like kernel auditor)
The not so good..
Camera is slow.
- Colours are inverted on screen for main camera but pictures are fine in photo viewer.
- Colours are fine on screen for front camera but inverted heavy blue tinge in photo viewer.
Security in settings F/C (there is no trustzone for CM yet, when they reverse sonys binary and include it in their code I will kang it )
No fingerprint detection/ firmware (yet - this will be reversed from sony at some point as well.)
-Bluetooth reported to have the same limited functionality as AOSP.
-Root: The ramdisk.img patcher within systemless SU installer is detecting that Omniboot.img is already patched/rooted when its not, so aborts, thus at this stage we cant get full root. (Im working on this)
If anyone is interested in building Omnirom for the z5c let me know and Ill push my device tree and provide a link.
Here is the twrp installable zip for omni. Do NOT install this on another device other then the E5823
Do a factory reset/full wipe in twrp before you install. Make sure wou have GAPS and the latest SU zips ready to go as neither are included.
https://mega.nz/#!kkZRTb5Z!i96cGUNUztTAATQ8mkkv0ivcQI9aOqErZNjgVqNFoAE
Enjoy.
Kernel source is:
https://github.com/omnirom/android_kernel_sony_msm.git
Device tree/s :
https://github.com/joeisgood99/TWRP_device_sony_Omni-suzuran_MM.git
https://github.com/omnirom/
Reserved
wow finally,gonna transfer from cm to it
EDIT:no way to dirty flash from cm,android.phone will crash,will do clean flash.Camera seems better than cm one,keep going!
Really thank you! Will try soon!
Not sent by me!
Best of luck for your project and thank you!
Sent from my E5803 using XDA-Developers mobile app
All functions seem to work fine though I couldn't get SuperSU working. Flashed the latest update but no dice. Just kept saying I had no root.
Also no icon appeared in the app drawer.
mangusmeister said:
All functions seem to work fine though I couldn't get SuperSU working. Flashed the latest update but no dice. Just kept saying I had no root.
Also no icon appeared in the app drawer.
Click to expand...
Click to collapse
same here, flashed latest beta and installed apk through adb because security settings crash when you try to enable untrusted apks.
What supersu version should be used ?
Good work btw.
daanwassenaar said:
same here, flashed latest beta and installed apk through adb because security settings crash when you try to enable untrusted apks.
What supersu version should be used ?
Good work btw.
Click to expand...
Click to collapse
I tried the one from cm13 thread on these forums and the latest update from the site and same result with both.
Edit : deleted duplicate post.
mangusmeister said:
I tried the one from cm13 thread on these forums and the latest update from the site and same result with both.
Click to expand...
Click to collapse
daanwassenaar said:
same here, flashed latest beta and installed apk through adb because security settings crash when you try to enable untrusted apks.
What supersu version should be used ?
Good work btw.
Click to expand...
Click to collapse
mangusmeister said:
All functions seem to work fine though I couldn't get SuperSU working. Flashed the latest update but no dice. Just kept saying I had no root.
Also no icon appeared in the app drawer.
Click to expand...
Click to collapse
Excellent feedback guys.
I didn't test it with SU. I assumed it would need SU 2.7.1. Try installing it after the first or second full boot. Could someone test that for me?
In the mean time as it's systemless root, I'll look to see if it's trying to install in a folder within the kernel that doesn't exist in omni (not much to the ramdisk, just 4 binaries.)
Thanks!
Awesome work mate! Always good to have another ROM to choose from
Joeisgood99 said:
Excellent feedback guys.
I didn't test it with SU. I assumed it would need SU 2.7.1. Try installing it after the first or second full boot. Could someone test that for me?
In the mean time as it's systemless root, I'll look to see if it's trying to install in a folder within the kernel that doesn't exist in omni (not much to the ramdisk, just 4 binaries.)
Thanks!
Click to expand...
Click to collapse
Tried latest beta 2.74 via twrp.
Unable to find stock img
Unable to find ramdisc img
Installation failed.
Hope this helps.
This was after a clean install of just the rom and gapps and a couple of reboot cycles.
mangusmeister said:
Tried latest beta 2.74 via twrp.
Unable to find stock img
Unable to find ramdisc img
Installation failed.
Hope this helps.
This was after a clean install of just the rom and gapps and a couple of reboot cycles.
Click to expand...
Click to collapse
Double thanks.
I installed the su package and gapps with no errors in twrp. However there was no su apk in app drawer and gapps (smallest package) caused continues launcher f/c. I will have to see what a can do re adding apk to the installable zip...
Did you have trouble installing gapps?
Thanks again guys
Joeisgood99 said:
Double thanks.
I installed the su package and gapps with no errors in twrp. However there was no su apk in app drawer and gapps (smallest package) caused continues launcher f/c. I will have to see what a can do re adding apk to the installable zip...
Did you have trouble installing gapps?
Thanks again guys
Click to expand...
Click to collapse
I only had gapps issues if I did a reboot between the rom and gapps. Flashed together they were fine.
Concerning the SuperSU install in twrp, it appears at a glance to install ok but if you read what comes up in twrp(see my last post) it fails. Tried a few times and always the same result.
daanwassenaar said:
same here, flashed latest beta and installed apk through adb because security settings crash when you try to enable untrusted apks.
Click to expand...
Click to collapse
You can tweak with settings via adb shell, and the 'settings' command, ie: to allow untrusted apk installation :
settings put secure install_non_market_apps 1
Same problem with supersu. But otherwise, quite nice, and stable till now.
Does Bluetooth work?
civicsr2cool said:
Does Bluetooth work?
Click to expand...
Click to collapse
Same errors as in cm13.
mangusmeister said:
I only had gapps issues if I did a reboot between the rom and gapps. Flashed together they were fine.
Concerning the SuperSU install in twrp, it appears at a glance to install ok but if you read what comes up in twrp(see my last post) it fails. Tried a few times and always the same result.
Click to expand...
Click to collapse
LolaPalocz said:
You can tweak with settings via adb shell, and the 'settings' command, ie: to allow untrusted apk installation :
settings put secure install_non_market_apps 1
Same problem with supersu. But otherwise, quite nice, and stable till now.
Click to expand...
Click to collapse
Now I believe the issue is when the SU install script tries to split the kernel. the script is expecting to find /kernel & /ramdisk.cpio after splitting the boot.img. Omni boot.img has a slightly different ramdisk format. The file path to the ramdisk once split from kernel is /sbin/ramdisk.cpio (as ramdisk.cpio and ramdisk-recovery.cpio both occupy the sbin directory, which sits beside <init> which is just a simlynk to the real <init> inside /sbin/ramdisk.cpio/
I will look at either modifying the systemless su install binary which is a little difficult as Chainfire's script writing ability is a little more advanced then mine...:silly: OR modding the kernel to fit the script, root it then using the rooted ramdisk, re configure to original format, and re pack.... Ill keep you guys posted. Omni needs root.
Joeisgood99 said:
Now I believe the issue is when the SU install script tries to split the kernel. the script is expecting to find /kernel & /ramdisk.cpio after splitting the boot.img. Omni boot.img has a slightly different ramdisk format. The file path to the ramdisk once split from kernel is /sbin/ramdisk.cpio (as ramdisk.cpio and ramdisk-recovery.cpio both occupy the sbin directory, which sits beside <init> which is just a simlynk to the real <init> inside /sbin/ramdisk.cpio/
I will look at either modifying the systemless su install binary which is a little difficult as Chainfire's script writing ability is a little more advanced then mine...:silly: OR modding the kernel to fit the script, root it then using the rooted ramdisk, re configure to original format, and re pack.... Ill keep you guys posted. Omni needs root.
Click to expand...
Click to collapse
Good luck!!!
Got time to do my own testing with SU.2.7.1
The error Im getting is that su installer detects that the stock omni boot.img is already su patched....
Stay tuned.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Blobs Forever
If you have upgraded your Nexus or Pixel device to Android 8.0 and you are missing Google's blob emoji, then this module is for you. I was very disappointed when I found out that Google was getting rid of the blob emoji. At first, I thought I could get used to the new emoji, but I always miss the blobs. This simple module will replace your emoji with the blob emoji from Android 7.1.
I have tested it on my Google Pixel running Android 8.0, with Magisk 14.2 beta. It is not guaranteed to work on other devices, but please feel free to try it out. It does require at least Magisk 14.0. For Pixel devices, 14.2 is required.
To install this module, use Magisk Manager to install the attached zip file. I am planning to submit this module to the Magisk Manager module repo soon. I did find another module that is supposed to provide the Android 7.1 emoji, but it appears to be unmaintained, and one user has reported that it is not working on their Pixel running 8.0.
Let me know how it works for you!
Screenshot:
New emoji + blob emoji
I made a similar module a while back but never released it because I was unable to include the new emoji missing from the old notocoloremoji file. I had every set up but I was unable to compile a working tff file. If anyone is interested I can give it another try on a different computer.
mrgooglegeek said:
I made a similar module a while back but never released it because I was unable to include the new emoji missing from the old notocoloremoji file. I had every set up but I was unable to compile a working tff file. If anyone is interested I can give it another try on a different computer.
Click to expand...
Click to collapse
Great , umm can you help me please , I am trying to compile a .ttf emoji font and i have all the .svg files which i guess are required to compile a emoji ttf font. I want to make a .ttf file for tweemojis
mrgooglegeek said:
I made a similar module a while back but never released it because I was unable to include the new emoji missing from the old notocoloremoji file. I had every set up but I was unable to compile a working tff file. If anyone is interested I can give it another try on a different computer.
Click to expand...
Click to collapse
Interesting. I didn't actually realize that there are new emoji that aren't in the font from Android 7.1. What tools were you using to extract/compile the ttf files?
bdr9 said:
Interesting. I didn't actually realize that there are new emoji that aren't in the font from Android 7.1. What tools were you using to extract/compile the ttf files?
Click to expand...
Click to collapse
I was using a Java app called Emoji Tools, located here: https://github.com/MitchTalmadge/Emoji-Tools/releases
mrgooglegeek said:
I was using a Java app called Emoji Tools, located here: https://github.com/MitchTalmadge/Emoji-Tools/releases
Click to expand...
Click to collapse
Cool, thanks. I'll check it out. It would be great to get the new emoji from Android 8.0 while still keeping the blob emoji for the rest of them.
sry I have a question. Can you please tell me how this is different from this module?
https://forum.xda-developers.com/apps/magisk/module-notocoloremoji-blob-patch-t3677992
https://github.com/Magisk-Modules-Repo/magisk-notocoloremoji-replacer
Emenaria said:
sry I have a question. Can you please tell me how this is different from this module?
https://forum.xda-developers.com/apps/magisk/module-notocoloremoji-blob-patch-t3677992
https://github.com/Magisk-Modules-Repo/magisk-notocoloremoji-replacer
Click to expand...
Click to collapse
Whoops, it looks like someone else had the same idea before me. I didn't see that one.
My module provides only the blobs, while the NotoColorEmoji Replacer module mixes the blobs with the new emoji from Oreo. Use whichever one fits your needs.
Works great on my 2013 Moto G. Running AOSPE 5.0 . Thanks!
Please help me get the blob emoji back!
Hi, so glad I stumbled on your post! I have a Google pixel XL. Can you please direct me step by step how to get the blob back? I would appreciate it soooo much! I'm not a developed by any means so I'm not as savvy as others on this forum, but I'm smart enough to go step by step if you'd be so kind to help me! I miss the blob emoji so bad and HATE these new emoji.
I googled magisk 14.2, downloaded it, phone said it couldn't open file. Came back to your post, downloaded zip, phone said couldn't open file. No app for magisk in Google play store.
What am I doing wrong? Please help me!!!!
iluvmynxd said:
Hi, so glad I stumbled on your post! I have a Google pixel XL. Can you please direct me step by step how to get the blob back? I would appreciate it soooo much! I'm not a developed by any means so I'm not as savvy as others on this forum, but I'm smart enough to go step by step if you'd be so kind to help me! I miss the blob emoji so bad and HATE these new emoji.
I googled magisk 14.2, downloaded it, phone said it couldn't open file. Came back to your post, downloaded zip, phone said couldn't open file. No app for magisk in Google play store.
What am I doing wrong? Please help me!!!!
Click to expand...
Click to collapse
To install Magisk you have a couple of options. But first of all I'd like to point out that the best way to get the proper installation files is from the release or beta threads here on xda. Googling, you'll never be sure what you find...
Easiest way to install Magisk is to simply flash the zip (stable or beta) in TWRP. Done.
If you don't have TWRP, you can install the Manager (you won't find it in the Play store, Google doesn't like it) and let it patch the stock boot image (extract it from a factory image) and then flash that to your device with fastboot.
There are installation instructions in the release thread and you might also find some info in the installation and troubleshooting guide.
If you've got questions about any of the above, first try searching through your device's forum, the Magisk forum and the rest of xda. Most beginner questions have been asked and answered many, many times.
Once you have Magisk up and running on your device, you just need to flash the zip from the OP in the Manager (Modules section, "+" button at the bottom) or in TWRP to get the blobs you want.
I'm still stuck!
Hello and thank you for the response! I've downloaded magisk and I've downloaded TWRP from the Google play store, yet it still won't open the zip file. So frustrating! Would it be crazy of we talked on the phone and u helped me lol... I'm serious! What am I doing wrong I can't figure out that image thing either.... The image I need to have beforehand? Ughh please help!
iluvmynxd said:
Hello and thank you for the response! I've downloaded magisk and I've downloaded TWRP from the Google play store, yet it still won't open the zip file. So frustrating! Would it be crazy of we talked on the phone and u helped me lol... I'm serious! What am I doing wrong I can't figure out that image thing either.... The image I need to have beforehand? Ughh please help!
Click to expand...
Click to collapse
You need to start by doing a lot of reading. A lot... Before you start doing this stuff you need to know a little bit more about what you're doing.
First: You don't download TWRP from the Play store. It's a custom recovery that you install on your device to do a lot of fun stuff (flashing ROMs, custom kernels, root, mods, making backups, etc). More on TWRP here: https://twrp.me/
I'd start looking through the Pixel XL forums. There you're probably gonna be able to find some guides and beginners threads to start you on your way. The users there are gonna be able to provide a lot more help as well, since they often know the device pretty good.
And before you do anything, make sure you have a backup of any important data before you do anything. When learning, you will end up wiping your device a few times. Just make sure to read, read and then read some more before continuing...
bdr9 said:
Cool, thanks. I'll check it out. It would be great to get the new emoji from Android 8.0 while still keeping the blob emoji for the rest of them.
Click to expand...
Click to collapse
Ya I would love to have all the new O emojis in blob style!
- Copying zip to temp directory
- Installing BlobsForever.zip
- Mounting /system, /vendor, /data, /cache
***********************************
! /data/magisk isn't setup properly!
! Please install Magisk v14.0+!
***********************************
Failed!
! Installation failed
Is this module compatible with Magisk v15.3?
Cleath said:
Is this module compatible with Magisk v15.3?
Click to expand...
Click to collapse
It works fine with me on v16.0
Love this module, thank you so much.
What I like with this one better than the "Blobmoji" found in the Magisk download, is that it leaves all the old icons intact. They are so great
I cannot seem to get this module to work properly on my OnePlus 2, running Cosmic OS 3.1 Oreo, any advice?
Successfully changed my emoji to blobs on Mi Max 2. I'm using custom ROM, DotOS.
Thanks for making this! I would be sad if an upgrade to LineageOS 15.1 meant losing my beloved blobs.
Quick question though. Does this module support new emojis like ? that are present in the new Android emoji set but not present in the Nougat blob set? I am asking because someone sent me ? in a Hangouts message and it didn't display right on my phone with this module installed.
Is there a way to use the android 6.0 blob emojis on oreo, while the new ones can be used where blob 6.0 dont exist?
Description:
This is the Xposed Framework compiled with the Unity Installer. Why is this different? This an all-in-one zip. Unity Installer auto-detects for SDK version, System or Magisk install, and uninstall. There's no need to have multiple zips for different scenarios.
Bundled is of course Xposed Framework by @rovo89 as well as Material Xposed Installer by @DVDAndroid. Some script work and hex patches used by @topjohnwu were included as well.
Compatibility:
Anything Official Xposed Framework supports
Android Lollipop - Oreo
init.d (other root & rootless)
MagiskSU & SuperSU
Magisk & System install
Nexus/Pixel support (A/B OTA)
SELinux enforcing
Works with nearly every device, kernel, and rom
Magisk Version Compatibility:
v15.3 - v18.1
Install:
Remove & uninstall any and all previous Xposed Frameworks and .apks
Install via Magisk Manager, Flashfire, or recovery (Magisk or System install will detect automatically)
Uninstall:
Delete module in Magisk Manager
Flash same version again in Magisk Manager, Fashfire, or recovery
Add "uninstall" to zip name to force uninstall
Downloads
XDA:DevDB Information
Xposed Framework Unity, Tool/Utility for all devices (see above for details)
Contributors
ahrion, Zackptg5, topjohnwu, rovo89, DVDandroid
Source Code: https://github.com/therealahrion/Xposed-Framework-Unity
Version Information
Status: Stable
Current Stable Version: v89/v90b3 r22
Stable Release Date: 2019-01-16
Created 2017-10-31
Last Updated 2020-01-01
ahrion said:
Description:
This is the Xposed Framework compiled with the Unity Installer. Why is this different? This an all-in-one zip. Unity Installer auto-detects for SDK version, System or Magisk install, and uninstall. There's no need to have multiple zips for different scenarios.
Bundled is of course Xposed Framework by @rovo89 as well as Material Xposed Installer by @DVDAndroid. Some script work and hex patches used by @topjohnwu were included as well.
Click to expand...
Click to collapse
Thanks for that, working perfectly well on my Huawei P10
funiewski said:
Thanks for that, working perfectly well on my Huawei P10
Click to expand...
Click to collapse
for me too, on my Huawei P10 plus
I'm glad it seems to be working for those who are trying it out. I'm assuming those who've downloaded and haven't commented means it's working for them as well.
For me it is working too. I'm on S7 Edge with SM 2.7.0 and Magisk v14.3 unofficial from 02.11.2017.
Hope you can bring your xposed version to the Magisk repo.
Thx for you work.
BustedFly said:
For me it is working too. I'm on S7 Edge with SM 2.7.0 and Magisk v14.3 unofficial from 02.11.2017.
Hope you can bring your xposed version to the Magisk repo.
Thx for you work.
Click to expand...
Click to collapse
@topjohnwu denied it because he said it would "confuse" users.
I compose this whole thing and after submitting I get a toast saying no permission and post is gone. Ugh.
UNITY working fine here, system/classic mode.
ZTE Axon 7, Dark ROM, SuperSU 2.82-SR5.
Various modules work fine.
Previously running unofficial by PurifyOS. Mostly because of Unicon. Unicon works on v88.x also but only with older installers.
If only there was a way to get it to work with the newer installers I'd be a happy camper. Otherwise I might have to go back, if I really want the module badly.
ZTE Axon 7 A2017U, Dark ROM, Tapatalk 4.9.5
marcdw said:
I compose this whole thing and after submitting I get a toast saying no permission and post is gone. Ugh.
UNITY working fine here, system/classic mode.
ZTE Axon 7, Dark ROM, SuperSU 2.82-SR5.
Various modules work fine.
Previously running unofficial by PurifyOS. Mostly because of Unicon. Unicon works on v88.x also but only with older installers.
If only there was a way to get it to work with the newer installers I'd be a happy camper. Otherwise I might have to go back, if I really want the module badly.
ZTE Axon 7 A2017U, Dark ROM, Tapatalk 4.9.5
Click to expand...
Click to collapse
You should probably consult the dev about updating it!
The Unicon dev long discontinued it but since it does work, in general, maybe I can plead my case. I'll give it a try.
ZTE Axon 7 A2017U, Dark ROM, Tapatalk 4.9.5
Can any1 confirm it working on the galaxy note 8 snap dragon samfail?
mister_propa said:
Can any1 confirm it working on the galaxy note 8 snap dragon samfail?
Click to expand...
Click to collapse
Does Magisk work on it? Does it have root? Unlocked bootloader?
ahrion said:
Does Magisk work on it? Does it have root? Unlocked bootloader?
Click to expand...
Click to collapse
dont think magisk works with the sd , i tried the other xposed but they only give me bootloops
Does it work on bluestacks 3?
Sir @ahrion,
In the OP, under Compatibility, it shows "Android KitKat+".
Seeing that it sounds as if this AIO package will also work with KitKat. I thought cool, I'll give it a try. Turned out to not be the case. Needs minAPI21.
So what does "Kitkat+" mean exactly.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
ZTE Axon 7 A2017U, Dark ROM, Tapatalk 4.9.5
marcdw said:
Sir @ahrion,
In the OP, under Compatibility, it shows "Android KitKat+".
Seeing that it sounds as if this AIO package will also work with KitKat. I thought cool, I'll give it a try. Turned out to not be the case. Needs minAPI21.
So what does "Kitkat+" mean exactly.
ZTE Axon 7 A2017U, Dark ROM, Tapatalk 4.9.5
Click to expand...
Click to collapse
Typo. Should read LP+
mister_propa said:
dont think magisk works with the sd , i tried the other xposed but they only give me bootloops
Click to expand...
Click to collapse
lieuliau said:
Does it work on bluestacks 3?
Click to expand...
Click to collapse
It's still Xposed. If the regular or Magisk Xposed works than so will this.
I wouldn't see why BlueStacks wouldn't work.
Thank you for creating a unity installer saved me a lot of data, installed it on all of my 4 devices, Tab S ironrom mm, Note 4 LL stock, Le Eco 3 AOSP 7.1.2 and Huawei Mediapad 2 MM stock.......:good::good:
jstvens16 said:
Thank you for creating a unity installer saved me a lot of data, installed it on all of my 4 devices, Tab S ironrom mm, Note 4 LL stock, Le Eco 3 AOSP 7.1.2 and Huawei Mediapad 4 MM stock.......:good::good:
Click to expand...
Click to collapse
Did it work on all of them?
Unity 2.2 is live! Xposed has just been updated with this new version
still doesnt work on the note 8 snapdragon version smh