Omnirom Z5C - Xperia Z5 Compact Android Development

Omnirom Z5C - Xperia Z5 Compact Android Development

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.

Related

[RECOVERY]TWRP 2.4 - TeamTX

Hello fellow old friends! I've brought something new and cool to this old forum(slow to keep up with the latest stuff).. And exremely cool for guys with non-working sd slots; You can now easily flash roms using "ADB Sideload" feature of TWRP.. bla bla...
UPDATE - 12MAR2013 - TWRP 2.4 Build taken down due to huge size which can't fit in our recovery partition.. Currently trying to slim it down..
Today, I felt like getting my ubuntu up and doing some fun stuff like old day. There! I decided to get another build of TWRP. I couldn't really test is as my bros phone is nowhere to be found . However, since I used the exact same source as the first build it should work just fine. Anyone willing to try their luck is welcome and appreciated..
{
"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"
}
Introduction:
Team Win Recovery Project 2.3, or twrp2 for short, is a custom recovery built with ease of use and customization in mind. We started from the ground up by taking AOSP recovery and loading it with the standard recovery options, then added a lot of our own features. It’s a fully touch driven user interface – no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.
Key Features:
Touchscreen driven with real buttons and drag-to-scroll
XML-based GUI that allows full customization of the layout – true theming!
Settings are saved to the sdcard and persist through reboots
Ability to choose which partitions to back up and which to restore
Ability to choose to compress backups – now with pigz (multi-core processor support for faster compression times)
Onscreen keyboard
Decryption of /data
Easy selection of internal/external storage
See changelog below for 2.3 features
What's new in 2.3:
-Rebased onto AOSP Jelly Bean source code
-Rewrote backup, restore, wipe, and mount code in C++ classes for easier maintenance going forward
NOTE: backups from prior versions of TWRP are still compatible with 2.3
-ADB sideload functionality from AOSP is included in 2.3, see this link for more info
-Re-wrote fix permissions entirely in C++ and runs in a few seconds instead of a few minutes (thanks to bigbiff)
-Improvements to zip finding in OpenRecoveryScript (should be a lot fewer GooManager automation issues)
-Faster boot times
-Added charging indicator while in recovery (only updates once every 60 seconds)
While this update may not bring a host of new must-have features, this update is a significant re-write of much of the core TWRP code. AOSP Jelly Bean recovery source moved to mostly C++ code and now all of the "TWRP" code is fully rewritten into C++ as well. Now that we've laid this groundwork, we're in a much better position to pull in future AOSP recovery updates as well as implementing more great new features.
Since TWRP 2.3 is based on AOSP jelly bean sources, TWRP now uses recovery API 3 instead of 2. Some zips may no longer work if the developer is using an out-of-date update-binary. This API change should not be a problem on newer devices, but older devices will probably encounter several zips that need to be updated. If needed, you can try using this update-binary that was compiled with current sources. It goes in your zip file in the META-INF/com/google/android folder.
What's new in 2.2 & 2.1:
On-screen keyboard! -- supports long press, backspace repeat, and swipe left deletes everything left of the cursor
Name new backups before creation and rename existing backups
Rename files and folders in the file manager
Pseudo-terminal emulator
Support decrypting an encrypted data partition on Galaxy Nexus (enter password using keyboard)
Backup archive splitting -- allows backup and restore of data partitions larger than 2GB
Simplified XML layout support between resolutions
Added dual storage selection radio buttons to zip install, backup, and restore pages
Improved zip install compatibility
Updated update-binary source code
Numerous small bug fixes and improvements
Zip queuing as seen in TWRP 1.1.x is back
Slider control (swipe to confirm most actions aka swipe to wipe)
Lockscreen (with slider to unlock)
Basic file manager (copy, move, delete, and chmod any file)
Added support for devices with /data/media (most Honeycomb tablets, new ICS devices like Galaxy Nexus)
Displays sizes of each partition in the backup menu
Added listbox GUI element (currently used for listing time zones)
Updated stock XML layouts to be more consistent and easier to port to different resolutions
XML layout files are significantly smaller
Partitions available backup are more accurate for some devices
Removed unneeded error messages (/misc errors, unable to stat sd-ext, etc.)
Fixed a bug with blkid detection code
Fixed bug where a blank line was inserted between every line of text during zip installs
Fixed a bug during zip installs where an invalid zip would cause TWRP to get stuck in the zip install
Added setting for themers to toggle simulation mode to make theming easier
New devices added - Galaxy Nexus GSM & CDMA (preview only, manual install), Acer Iconia Tab A500, HTC Vivid, Motorola Defy
Added support for .jpg images in the theme engine
Changed images for stock tablet theme - makes tablet builds about 500KB smaller
Removed unneeded non-GUI images from GUI - makes all builds about 100KB smaller
In addition to the above new features, TWRP 2.2 features a scripting engine that allows an app to send commands to the recovery for the recovery to perform during startup. We call this scripting engine OpenRecoveryScript. This engine will be put to use immediately in the GooManager app. GooManager will be able to install recoveries automatically for most supported devices. The app will also let you choose to install multiple zips from within Android, wipe cache & dalvik, and run a backup.
Theming:
Information on TWRP 2 Theming - http://teamw.in/project/twrp2themers
Known Issues: (General TWRP issues)
CWM backups are not compatible - please make a fresh backup in TWRP as soon as you have flashed it

Issues I found:
-UMS doesn't work

i installed but couldnt install any zip's or back ups looks really good tho...nice 2 see summit different :victory:

Congrats bro on your first source build!!! :thumbup:

shmokeyuk said:
i installed but couldnt install any zip's or back ups looks really good tho...nice 2 see summit different :victory:
Click to expand...
Click to collapse
Ill check install from zip. But backup was working good..
rishabh.raj37 said:
Congrats bro on your first source build!!! :thumbup:
Click to expand...
Click to collapse
actually not my first.. I'm building aosp for my nexus
Sent from my Galaxy Nexus using xda app-developers app

Haha grats i would count this as your first source build AOSP for maguro is officially supported and not much needs to build it just select the option

-Grift- said:
Haha grats i would count this as your first source build AOSP for maguro is officially supported and not much needs to build it just select the option
Click to expand...
Click to collapse
Well, yeah you have a point.
Sent from my Galaxy Nexus using xda app-developers app

Great, thank you! but where can I find "erase battery stats"? It's gone from the wipe menu!

Punkiderma said:
Great, thank you! but where can I find "erase battery stats"? It's gone from the wipe menu!
Click to expand...
Click to collapse
Ill see that when my bro comes back home...

XiproX said:
Ill see that when my bro comes back home...
Click to expand...
Click to collapse
Confirmed: can't install zips
Thanks anyway! I'll be waiting for further verions =D

Well thats weird I just checked now and it looked like it flashed AOSP 1.4 successfully.. Ill check again after a full wipe..
And yes battery stats button is gone. Have no idea why.. I had just disable sd_partitioning to lower recovery image size to fit our phone. I dont remember disabling anything else.. Why do you even need wiping battery stats?

did a full wipe including system and flashed:
1.AOSP GB 1.4 -- FLASHED
2.TX-MIUI-SDSL -- FLASHED
3.Grifts CM10 build -- Took longer than the previous 2 roms but FLASHED (I was even gonna make a battery pull cause I thought it was doing nothing, then just saw the final show_progress)
4.IceCreamSwift RC2 -- FLASHED
As you can easily see, it has no problem flashing android 2.3.7, 4.0.4, 4.1.2...
if you still cant flash, please try some other rom and report.. Thanks1

XiproX said:
did a full wipe including system and flashed AOSP 1.4 and successfully booted..
Ill be testing these roms and report..
1.AOSP GB 1.4 -- FLASHED
2.TX-MIUI-SDSL -- FLASHED
3.Grifts CM10 build -- Took longer than the previous 2 roms but FLASHED (I was even gonna make a battery pull cause I thought it was doing nothing, then just saw the final show_progress)
4.Miro's Oxygen
Click to expand...
Click to collapse
miro has oxygen ? you mean 4.0 that is based on ice cream swift ?

smileydr0id said:
miro has oxygen ? you mean 4.0 that is based on ice cream swift ?
Click to expand...
Click to collapse
yeah, but I think my bro deleted that rom from sd. so Im gonna try flashing IceCreamSwift RC2
btw, I think it was based on AOSP not CM

XiproX said:
yeah, but I think my bro deleted that rom from sd. so Im gonna try flashing IceCreamSwift RC2
btw, I think it was based on AOSP not CM
Click to expand...
Click to collapse
Can you explain me how did you ported it ? i wanna try to port it on my xperia U

smileydr0id said:
Can you explain me how did you ported it ? i wanna try to port it on my xperia U
Click to expand...
Click to collapse
if its TWPR you are asking, I had already got my build environment set up following this, then it was really easy to build TWRP;
you can simply follow those instructions there for ubuntu, udev rules, and other tools like java, then skip Gnex stuff, use the same process for getting repo commands and instead of initializing AOSP source initialize CM source(https://github.com/Cyanogenmod -----...). After getting the cm repo follow The official TWRP guide. NOTE: Youll need device files for your phone. I hope someone has an open-source project
Good Luck! feel free to pm if you need something. And in case of any problem with building twrp or other twr related make sure you check their freenode you'll get your answer faster than you would on the guide thread..

Again, if you still cant flash roms, please briefly explain what happens and provide a log (Advanced>Copy Log to SD) Thanks!

XiproX said:
Again, if you still cant flash roms, please briefly explain what happens and provide a log (Advanced>Copy Log to SD) Thanks!
Click to expand...
Click to collapse
My problem is not flashing roms (didn't tried either), is flashing mods (apks, fixes, and so on). With those installation fails always and with the previous version of TWRP they install correctly

coto39 said:
My problem is not flashing roms (didn't tried either), is flashing mods (apks, fixes, and so on). With those installation fails always and with the previous version of TWRP they install correctly
Click to expand...
Click to collapse
it could be because of TWRP 2.3 being based on AOSP jelly bean sources, "TWRP now uses recovery API 3 instead of 2. Some zips may no longer work if the developer is using an out-of-date update-binary. This API change should not be a problem on newer devices, but older devices will probably encounter several zips that need to be updated. If needed, you can try using this update-binary that was compiled with current sources. It goes in your zip file in the META-INF/com/google/android folder."
if there was a particular reason then it would affect ROM flashing too. (I guess).. I think you should try to flash a not working patch with the above provided update-binary..

XiproX said:
it could be because of TWRP 2.3 being based on AOSP jelly bean sources, "TWRP now uses recovery API 3 instead of 2. Some zips may no longer work if the developer is using an out-of-date update-binary. This API change should not be a problem on newer devices, but older devices will probably encounter several zips that need to be updated. If needed, you can try using this update-binary that was compiled with current sources. It goes in your zip file in the META-INF/com/google/android folder."
if there was a particular reason then it would affect ROM flashing too. (I guess).. I think you should try to flash a not working patch with the above provided update-binary..
Click to expand...
Click to collapse
That's right I also had that issue but it was because of older binaries.
But I do have another issue, this version backs up my rom without problem but when it comes to restore, i just get bootloops. The thing is that apparently there are no errors restoring the backup. I have TWRP 2.1.4 and 2.3.1.1 flashable zips for when I need to restore
Are you aware of this XiproX?

[2020-01-27] ®FDE.AI - Ultimate Android Optimizer

{
"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"
}
Code:
Your warranty is now void.
I am not responsible for bricked devices, dead SD cards,
thermonuclear war, or you getting fired because the alarm app failed. Please
backup your data before flashing it!
YOU are choosing to make these modifications, and if
you point the finger at me for messing up your device, I will laugh at you.
Do everything at your own risk!
Intro:Hello everybody. My name is Fera. I want to share this project with you for free. I made it myself from scratches once again. Please hit "thanks" button, rate this thread 5-star, or consider donating me to support my work. (Thanks!)
What's in:FeraDroid Engine (simply FDE) - an All-in-One ultimate optimizer for all devices on Android OS. No settings/customization and rest 'headache' - all parameters are individual for EVERY device depending on it's hardware/software characteristics. All parameters are very balanced - you may gain performance without increase of power consumption AND reduce power consumption without losing performance. FDE is totally compatible with very wide range of devices and Android versions.
Installation requirements:Supported CPU arch's:
ARMv7 (armeabi-v7a) (32bit)
ARMv8 (arm64-v8a) (64bit)
x64bit (x86_64)
Supported Android OS versions:
4.1 and higher
Detailed tech description:FDE - very universal Android OS optimizer. Very wide-range settings of OS and Linux kernel are configured, still being cross-platform utility, maximally compatible with all devices. This means that it doesn't have any dirty hacks/hardcore and 3rd part binaries (except busybox) & config files. FDE applies configurations depending on It's hardware and software, so that in the end every device is configured individually.
New unique method of execution - all required FDE components are loaded directly to RAM and executed from there. System partitions are remounted RW only once while installation. This means high speed (the worst RAM will have at least ~500MB/s of I/O speed), no power consumption (no NAND memory I/O occurs) and security (system partitions are in read-only state). Also new-gen FDE is synced with OS boot process - so tweaks will be applied in correct time. All system partitions are trimmed and checked for errors after every OS boot with FDE onboard. Universal installer automatically detects what ROOT-method you use and how to auto-start. Finally, FDE is not only about optimization. It's also about security and feature-enabler.
See compacted list of most included features HERE.
Artificial Intelligence:
As you may notice from the name "FDE.AI" - can tell us that it has real AI inside. AI will learn how do you use your device, check out current usage scenario and adapt some system parameters real time to give you best usage experience. Details HERE.
Why to optimize?First of all to make you happy with your device, to make it live longer & be snappy. Another reason is garbage. WTF? Yes. There is a world problem of e-garbage utilization, especially electronic devices & their toxic stuff like batteries..etc.. I'm not against progress - I'm against the selling politics of corporations, which add features slowly, to make people buy them. I'd say OKAY if it wasn't harmful, but in fact Africa became a toxic garbage continent - they need somewhere to put retarded e-devices & that's sad. It costs them cheaper to move toxic garbage to another country, rather then properly utilize it. You may say, how FDE can help with that, are you mad bro? Well, I hope that if you install FDE on your device, you'd use it for longer time, because of all optimizations. So that it will make you happy & you won't change it too frequent, in fact possibly reducing the amount of e-garbage. Thanks.
Installation:
WARNING! Don't use any other All-in-One tweakers or things may get much worse! I warned you!
Make a backup just in case something goes wrong.
Download latest version of FDE and install it via custom recovery OR add zip in modules list if you are using Magisk systemless root.
After OS boot, you will get vibration and a log file /sdcard/Android/fde.txt will be created if FDE worked OK.
If you want to uninstall FDE simply remove module from Magisk Manager if you are on Magisk OR flash this zip in custom recovery.
Download:
FDE.AI-v7.3-20200127
About FDE APK
FAQ
Related Videos
Join my group in Telegram for 24/7 support.
Join my Facebook group.
Thread at 4PDA.
Fan-art
Thanks to all guys, who contributed, helped, tested my work.. You all are wonderful, amazing, smart, super cool, beautiful people!
Consider donating me to support my project if you like it. Thanks!
XDA:DevDB Information
FDE.AI - Ultimate Android Optimizer, Tool/Utility for all devices (see above for details)
Contributors
FeraVolt
Version Information
Status: Stable
Current Stable Version: v8.0
Created 2019-03-10
Last Updated 2020-01-27

FDE.AI FAQ
Will it work on this or that device?
It will work on any device which runs Android OS.
Will it work along with this or that tweak/optimizer?
NO. Don't use any other All-in-One tweakers or things may get much worse!
Can I use this on custom kernel?
Yes, why not? It will work even better on custom kernel.
Does FDE has any configuration/logs?
No configurations. This is "flash & forget" optimizer. It will configure your system depending on you hardware/software automatically & individually. Log is available in /sdcard/Android/fde.txt
Is it worth to try FDE if I have a powerful flagship?
Yes, sure. FDE not only gives performance, but also increases power-saving.
Is there any difference between zip from Magisk module repo and zip provided here?
The difference is only in installer - zip provided here is universal, while one in Magisk repo is for Magisk root only.
I have ROOT, but don't have recovery. Can I do something?
You may try to install FDE via Flashfire app.
I have ROOT - not Magisk, and not SuperSU, and I don't have init.d support. What to do?
Try to emulate init.d support with app like Universal_Init.d_Support or similar.
Installation was successful, but no vibration. What does this mean?
Try to reboot device. Wait for a minute or two more. Maybe it will work, but a little later than expected. Also check for /sdcard/Android/fde.txt file. If still no luck, try to update your ROOT method (Magisk preferred). If you do have log and it says "all good" - then don't worry at all. Some rare devices doesn't support vibrations triggered by script. If still not working, read THIS post.
Do I need busybox?
No, FDE has a built-in one already. But if you already have one - they will not conflict.
Are project treble ROMs supported?
YES.
Flashed fine, but can't find icon for FDE. Huh?
This is not an Android apk and it has no interface yet.
Can I flash FDE right after ROM installation?
NO. Boot ROM first, then install FDE.
AI says '...turbo' is not supported. What can i do to make it work?
You may try to install another custom kernel. Those features are kernel dependent.
It's running fine, but i got a problem...
FDE.AI is under active development. Please attach any useful information such as log/screenshot, name of your device, ROM/recovery version. I am developer of FDE and I will help you to figure out the problem.

Nice mod, please check your git

Where is the download link???
来自我的 SM-G920F 上的 Tapatalk

There is a 'downloads' tab over main post

FeraVolt said:
There is a 'downloads' tab over main post
Click to expand...
Click to collapse
Error executing update-binary

Here is zip with fixed recovery installation. Forgot ';' in script...

No log file for me

I test your mod and I dont have any log, and any change in my device; galaxy tab pro 8.4 with SlimLP 5.1.1

russia101 said:
No log file for me
Click to expand...
Click to collapse
kioshio said:
I test your mod and I dont have any log, and any change in my device; galaxy tab pro 8.4 with SlimLP 5.1.1
Click to expand...
Click to collapse
Make sure you have mounted system partition in recovery before flashing.. This is beta version..being under development.. Also possibly it simply didn't run on boot. Please specify your device, android version and rom and i will try to check this out. I tested it from 2.3 till 5.1.1 android version..stock roms..

FeraVolt said:
Make sure you have mounted system partition in recovery before flashing.. This is beta version..being under development.. Also possibly it simply didn't run on boot. Please specify your device, android version and rom and i will try to check this out. I tested it from 2.3 till 5.1.1 android version..stock roms..
Click to expand...
Click to collapse
I'm using a s3 LTE and I'm currently on marshmallow 6.0.1

No log file. I Followed instructions. Stock Android 4.2.2
Still......noticeable improvement in loading of apps. Any other way to see if it flashed correctly?

Seems installed, let's see if it works. 5.1 OxygenOS. Here is my log: https://drive.google.com/file/d/0B1B_Q2k5VDqYUml1bTBJd2ZFMk0/view?usp=docslist_api
You should provide an Uninstaller, just in case. Cheers
Enviado desde mi ONE E1005 mediante Tapatalk

ChavitoArg said:
Seems installed, let's see if it works. 5.1 OxygenOS. Here is my log: https://drive.google.com/file/d/0B1B_Q2k5VDqYUml1bTBJd2ZFMk0/view?usp=docslist_api
You should provide an Uninstaller, just in case. Cheers
Enviado desde mi ONE E1005 mediante Tapatalk
Click to expand...
Click to collapse
Yes..it's working on your device fine. Do you notice any improvement? In case of high-end devices, most noticable should be a battery consumption decrease.
Will provide uninstaller asap.

hipocrazy said:
No log file. I Followed instructions. Stock Android 4.2.2
Still......noticeable improvement in loading of apps. Any other way to see if it flashed correctly?
Click to expand...
Click to collapse
Yes..via terminal emulator type:
su
sh /system/engine/as.sh
sh /system/engine/feradroid.sh
Then recheck log file..

FeraDroid-Engine-v0.19-beta2
FeraDroid-Engine-v0.19-beta2
Changes captured:
https://github.com/feravolt/FeraDroid-Engine/commits/master

Manuall FDE run
Here is a little instruction in case you couldn't install FDE on your device. Recovery doesn't install it well..or..FDE doen't autostart or you just don't have a recovery for your device (as in my case with china noname phone).
So:
-> Download latest FDE zip and extract it.
-> With any root explorer copy engine folder to /system/
-> Set 777 (check all tabs) permissions to whole engine folder and what is in there and in every folder content
-> Then get 'Terminal Emulator' app from Google Play store, run it and type:
Code:
su
-> Grant root permission then type:
Code:
sh /engine/as.sh
-> After that reboot your device and in 2 minutes, check log file on path: /sdcard/Android/FDE.txt
-> If there is no FDE.txt log then open Terminal Emulator again and type:
Code:
su
sh /system/engine/feradroid.sh
-> Wait it's completion, then check log file again. If it exists, please send it to me to deal with autostart issue for your device. You should run theese two commands every time you reboot your device..
Hope this will help you and you will be happy to see your device runnign fast. :fingers-crossed:

Log file
FeraVolt said:
FeraDroid-Engine-v0.19-beta2
My log file looks not like it's working correctly and this logfile only appears after I typed the command which you posted for terminal
View attachment FDE.txt
Click to expand...
Click to collapse

init.d start
russia101 said:
FeraVolt said:
FeraDroid-Engine-v0.19-beta2
My log file looks not like it's working correctly and this logfile only appears after I typed the command which you posted for terminal
View attachment 3598637
Click to expand...
Click to collapse
Thanks for feedback.It worked for you untill you reboot.
Here..try this zip with a try to be started at boot by init.d.. mount system partition..flash .zip and check log.(remove it beforeflashing this)
Click to expand...
Click to collapse

FeraVolt said:
russia101 said:
Thanks for feedback.It worked for you untill you reboot.
Here..try this zip with a try to be started at boot by init.d.. mount system partition..flash .zip and check log.(remove it beforeflashing this)
Click to expand...
Click to collapse
Ok did what you said and it looks Like everything works
View attachment FDE.txt
Click to expand...
Click to collapse

[KERNEL][Stock 224/253][Z5C][6.0.x]OM5Z Kernel

Latest Version: V2.0
Changelog:
Version 1:
Add kexec-hardboot
ramdisk: use init_sony, no outdated bootrec scripts
ramdisk: fix USB on Stock when using MultiROM
Remove broken Sony MHL driver
Update to 32.2.A.0.224
Merge caf/LA.BF64.1.2.2_rb4.40
Various CVE Fixes
Initial Z5 and Z5C bringup, based on Zombie Kernel with these features
Bug fixes for touchscreen / fingerprint / scheduler drivers
Stripped unnecessary debug nodes, legacy code and disabled KSM
Turquoise LED when EOC is reached (when battery is fully charged)
CPU-Speedbin visible in debugfs node (sys/kernel/debug/msm8994_cpuinfo/*Speedbin)
Calibrated JDI Novatek Panel to 6500K Color Temperature and 2.2 Gamma
Tomtom-Codec Digital Speaker-, Mic- and Cam-mic-Control
Underclocked both Cluster to 1,344/1,536 GHz respectively, resulting into HUGE Temperature improvements
Version 2:
Ability to disable the underclock (added on public demand) See OP for instructions
Removed TomTom Audio
Update to 32.2.A.0.253
Update init_sony
include DRM Fix by @tobias.waldvogel
Add support for sumire_dsds (E6633 and E6683). Thanks to @tOrNadO™ for testing
For a detailed Changelog, check the Github Commit history:
https://github.com/Myself5/android_kernel_sony_msm8994_OM5Z/commits/

[KERNEL][Stock 224][Z5C][6.0.x]OM5Z Kernel
Tried to flash this in twrp, but it fails. Downloaded again and tried to flash but still fails
I have stock rom with androplus kernel

I think that should be done a tutorial for the stock users...
Enviado do meu E5823 através de Tapatalk

mele80 said:
Tried to flash this in twrp, but it fails. Downloaded again and tried to flash but still fails
I have stock rom with androplus kernel
Click to expand...
Click to collapse
Can you please say what the error message was? also, maybe your download was corrupt. You can redownload and see if that helps.
I just tried flashing the zip in twrp and it works.

[KERNEL][Stock 224][Z5C][6.0.x]OM5Z Kernel
Zip signature verification failed
Error installing zip file
Flashing from adb worked

This kernel include pacthes from here http://forum.xda-developers.com/xperia-z5/development/root-automatic-repack-stock-kernel-dm-t3301605 ?

There is any tutorial to flash this kernel?
Can i flash it up on the stock rom and stock recovery?
Enviado do meu E5823 através de Tapatalk

arhangel78ru said:
This kernel include pacthes from here http://forum.xda-developers.com/xperia-z5/development/root-automatic-repack-stock-kernel-dm-t3301605 ?
Click to expand...
Click to collapse
yes "RIC off" and "DRM patch" are included.
jdcchora1533 said:
There is any tutorial to flash this kernel?
Can i flash it up on the stock rom and stock recovery?
Click to expand...
Click to collapse
As mentioned in the thread title, this is for .224, so obviously you can flash it on stock rom.
Not sure what you mean with stock recovery though.

Trying to install the zip file with TWRP 3.0.2 and got this error
Updater process ended with ERROR: 7
Error installing zip file '/external_sd/(folder where i have the zip)
What i am doing wrong?
regards

fridlack said:
Trying to install the zip file with TWRP 3.0.2 and got this error
Updater process ended with ERROR: 7
Error installing zip file '/external_sd/(folder where i have the zip)
What i am doing wrong?
regards
Click to expand...
Click to collapse
Does your folder have weird characters or spaces in the name? Please try moving the zip to another directory.

oshmoun said:
Does your folder have weird characters or spaces in the name? Please try moving the zip to another directory.
Click to expand...
Click to collapse
I try to move to internal storage root folder and same result [emoji21]

fridlack said:
I try to move to internal storage root folder and same result [emoji21]
Click to expand...
Click to collapse
Which TWRP 3.0.2 recovery are you using? I use oshmoun's MultiROM TWRP, and it works very well! (You don't need to install or use the MultiROM part of it.)

Thanks for your great work. I ran into an issue with root acting weird after kernel install. It actually messed up binary folders. I have no idea how but apps were getting root denial with this awesome kernel.
Intsallation went ok with twrp 3.0.2.0. So no issues there.
Have you guys noticed this kind of behaviuor with the kernel?
Sent from my E5823 using XDA-Developers mobile app

I see the underclocked cores and I'm curious about battery life improvement... someone?

Triflot said:
Which TWRP 3.0.2 recovery are you using? I use oshmoun's MultiROM TWRP, and it works very well! (You don't need to install or use the MultiROM part of it.)
Click to expand...
Click to collapse
I am using this revovery http://forum.xda-developers.com/showthread.php?t=3334568 and xpower 3.0 rom with stock kernel
Is the update script checking if the device is correct? Maybe xpower rom have something changed?
Enviado desde mi E5823 mediante Tapatalk

fridlack said:
I am using this revovery http://forum.xda-developers.com/showthread.php?t=3334568 and xpower 3.0 rom with stock kernel
Is the update script checking if the device is correct? Maybe xpower rom have something changed?
Enviado desde mi E5823 mediante Tapatalk
Click to expand...
Click to collapse
ok sorry about that. I think I should update the recovery thread to mention that it's not maintained anymore.
Yes there is a device check, but usually if that fails then it would tell you what it was expecting (in this case that'd be suzuran, E5823, E5803).
Could you please try the multirom recovery. It's basically TWRP only with multirom additions. The multirom recovery works pretty well regardless if you have multirom installed or not.

Good to see another kernel in the panorama! As soon as i get the latest MM update, i'll surely test it.
However i'm interested in the standby consumption during night, did you test it? every stock based kernel-rom combination seems to be plagued by high drainage even in offline mode without particular wakelocks

oshmoun said:
ok sorry about that. I think I should update the recovery thread to mention that it's not maintained anymore.
Yes there is a device check, but usually if that fails then it would tell you what it was expecting (in this case that'd be suzuran, E5823, E5803).
Could you please try the multirom recovery. It's basically TWRP only with multirom additions. The multirom recovery works pretty well regardless if you have multirom installed or not.
Click to expand...
Click to collapse
After installing the multi recovery ( via fastboot, zip file had the same problem) I install zip kernel without problems, thanks so much!
But now I have a new problem, can not update supersu binaries, got an error, I tried to install stable and beta supersu and same result with both, anyone with the same problem?

fridlack said:
After installing the multi recovery ( via fastboot, zip file had the same problem) I install zip kernel without problems, thanks so much!
But now I have a new problem, can not update supersu binaries, got an error, I tried to install stable and beta supersu and same result with both, anyone with the same problem?
Click to expand...
Click to collapse
Yep. I have exact the same issue. Su wants to update binary without success. It doesn't matter which su I use.
Sent from my E5823 using XDA-Developers mobile app

Lineage OS XT907_JBBL

Lineage OS 14.1 for Moto Razr M JBBL
{
"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"
}
Hi all!
I'm have ported LineageOS 14 for the xt907_jbbl
lineage-14.1-20170707-port-ilichva-xt907_jbbl
lineage-14.1-20170804-port-ilichva-xt907_jbbl
Enjoy.
XDA:DevDB Information
Lineage OS 14 for Moto Razr M_JBBL, ROM for the Motorola Droid RAZR M
Contributors
ilichva
ROM OS Version: Android 7.1.2 Nougat
Version Information
Status: Nightly
Created 2017-03-23
Last Updated 2017-08-05

Thank you so much for this! Even though it's a bit sad it's only for JBBL...
Do you know what are the differences between both bootloaders? I mean, why ROMs made for one don't boot in the other one?

trivialPotato said:
Thank you so much for this! Even though it's a bit sad it's only for JBBL...
Do you know what are the differences between both bootloaders? I mean, why ROMs made for one don't boot in the other one?
Click to expand...
Click to collapse
Rom JBBL (4.1) - kernel 3.0
Rom KKBL (4.4.2) - kernel 3.4

ilichva said:
Rom JBBL (4.1) - kernel 3.0
Rom KKBL (4.4.2) - kernel 3.4
Click to expand...
Click to collapse
Hm... Interesting... That means that a custom kernel would allow them to boot, right?

The custom kernel can be JB (3.0) or KK (3.4)
Therefore, the Lineage OS KKBL must have a core of 3.4
If you replace only the core, the ROM will not work.

ilichva said:
The custom kernel can be JB (3.0) or KK (3.4)
Therefore, the Lineage OS KKBL must have a core of 3.4
If you replace only the core, the ROM will not work.
Click to expand...
Click to collapse
Hm, I didn't get that, replacing the kernel would not allow them to boot? They'd need to be built from scratch?

Hello ilichva, big thanks. And what about root???

mastnacek said:
Hello ilichva, big thanks. And what about root???
Click to expand...
Click to collapse
Install SuperSU...

ilichva said:
Install SuperSU...
Click to expand...
Click to collapse
I just found this thread. When I flashed this ROM, I installed Magisk for root and haven't noticed anything negative, but have found benefits (e.g. installing/running Viper, work around for failing init.d etc). It also appears to be the choice on other devices, in newer ROMs .
@ilichva is there any specific reason you suggested SuperSU? or is it just that you haven't personally tested Magisk?
Originally I was kind of worried that the vanilla style of Lineage OS would bug me (as I am used to ROM's with a lot of customisations). However, I have Magisk (the apparent latest way to root), V4A, a Linux Swap Partition and have Xposed the...err...heck! out of the ROM (8 Xposed modules), including "Settings Editor" which enables you to add things to the settings menu that makes the additions (eg Viper) appear like they are actually part of the ROM.:good:

ilichva said:
Install SuperSU...
Click to expand...
Click to collapse
Thanks, works. In CM13 was supersu already. Good work.

I'm using supersu2.76 zip and install viperatmos stock5.4 and using exposed too, all working well on enforcing mode

dedik46 said:
all working well on enforcing mode
Click to expand...
Click to collapse
Do you have or are you using any boot scripts? ie init.d

DiamondJohn said:
Do you have or are you using any boot scripts? ie init.d
Click to expand...
Click to collapse
No...i didn't use init d or any script

dedik46 said:
No...i didn't use init d or any script
Click to expand...
Click to collapse
I think you may of misunderstood me. I was *not* asking if you used any init.d scripts to achieve viper & enforcing, but if you used init.d scripts for anything at all eg to set up the cache amount on your sd card, disable IO logging, instance a file/partition swap etc.
I have seen an su.d directory on my previous builds (instanced from flashing a viper install) but it was not being called/triggered by the SuperSU installed on the previous CM 13 build.

DiamondJohn said:
I think you may of misunderstood me. I was *not* asking if you used any init.d scripts to achieve viper & enforcing, but if you used init.d scripts for anything at all eg to set up the cache amount on your sd card, disable IO logging, instance a file/partition swap etc.
I have seen an su.d directory on my previous builds (instanced from flashing a viper install) but it was not being called/triggered by the SuperSU installed on the previous CM 13 build.
Click to expand...
Click to collapse
I've never try to use any script on init.d and i don't know if init.d is working or not, maybe i will try to use magisk for the next update..

dedik46 said:
I've never try to use any script on init.d and i don't know if init.d is working or not
Click to expand...
Click to collapse
And that's what I was checking. init.d does not work in this lineage ROM, nor in another devices (Nexus 5) lineage based ROM; ie Resurection Remix on N5. I am really surprised how little attention this artifact is getting.
dedik46 said:
maybe i will try to use magisk for the next update..
Click to expand...
Click to collapse
Although not an issue for me, it has extra features such as allowing some apps that wont run on rooted phones, to have su hidden from them. I like the fact that is has pre-built modules to support extra's such as V4A. I also liked the fact that it has its own init.d functionality that I use since the ROM's init.d does not work. And it appears to be the direction newer custom ROM's are heading for root.
Really, your already thinking about the next build? I am more thinking about the method/steps I did wrong or could of done better from the flash of the last build.

Wifi issue is not only our device
Some people have noted an issue with Wifi. I too have had the issue with the wifi loosing its connection and not automatically re-connecting. even though the Wifi is available and well within range.
I looked into it a little further (created a quick app that logged numerous broadcast messages, and logged them to a file), and as part of that I also tested the "pass" situation on my spare Nexus 5 phone, also connected top my Wifi. However, it too failed! it was however better in that it didn't randomly loose the wifi.
With the N5, if I was connected to Wifi (very strong signal), went into settings, turned off the wifi. When I turned the wifi back on, it did NOT automatically re-connect.
The N5 is running a MM Resurrection Remix (one of the latest builds, based on Lineage I think)
So, It would appear that this wifi issue is not specific to our devices. I am not sure if thats a good or bad thing.
Anyway, I have my logging test app running, and like a watched kettle, it hasn't lost its Wifi connection

Has anyone else had their "Recents" button on the NavBar fail to pull up recents? :crying:
It has happened to me randomly once before, and then it just came back randomly as well a few days later.
I am thinking it may be caused/triggered by the fact that I have a customized NavBar, and am using Xposed (Gravity box is one which modifies the NavBar) as well.

DiamondJohn said:
Has anyone else had their "Recents" button on the NavBar fail to pull up recents? :crying:
It has happened to me randomly once before, and then it just came back randomly as well a few days later.
I am thinking it may be caused/triggered by the fact that I have a customized NavBar, and am using Xposed (Gravity box is one which modifies the NavBar) as well.
Click to expand...
Click to collapse
I got the recents working again.
I tried turning all my xposed modules off (including a couple that affected the navbar), but it was still failing.
Then I noticed that for the first minute or so it would work every boot, but then eventually stop. So I thought it was some installed app/config that only started later in the boot sequence. This "app" must have root to do such damage, so I went down that path. Thought it might be Magisk (since I appear to be one of the only on it). So I uninstalled Magisk, and flashed SuperSU. Still failed.
Anyway, I got it working again by turning off Super User access to all apps individually (after a restore back to my original starting point), then turning it back on (with a few reboots between). I couldn't identify exactly which caused it, but now it all works :highfive:, and I have a technique to hopefully correct it in the future.:good:

and downloading now!
http://4pda.ru/forum/index.php?showtopic=403669&st=21880#entry60269538
Thank you @ilichva:good::good::good:
-------------edit
just noticed the link is in the first post

[Magisk Module][Flashable Zip][5.0+] Android P NotoColorEmoji Replacer v5

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

Database Develop

welcome