Database Info

[ROM(ABANDONED)] [4.4.4] [UNOFFICIAL] CyanogenMod 11 for ChaCha [07.22.2014]

{
"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:
#include
/*
* 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
* do some research if you have any concerns about features included in this ROM
* 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.
*/
We've done it! Thanks to the androidarmv6 team's work, and the great people over at Team Simplicit(Especially Olivier, as he got it working on the Wildfire S and a couple other devices),
we now have a functional KitKat rom for the ChaCha!
This rom SHOULD now be daily driver ready. Please leave feedback on any issues.
I will also note that it takes a rather long time to boot. I don't know if it will stay this way or not, so don't ask.
And lastly, I recommend leaving the device for at least a minute after first boot, before going through the setup wizard. Otherwise it will be very laggy.​
NOT WORKING/BROKEN/ISSUES
Bluetooth
Screen video recording (I believe we have a fix in the works)
ART (doesn't support ARMv6)
SELinux
USB/WiFi tethering
Camera orientation is sideways
Phone takes a long time wake during call or alarm
Symbols/zero key bringing up the input method selection window, regardless of whether alt is pushed.
Arabic keyboard not working?
incoming call crashes ui. dialer crashes when you try to open it after ui crash.
Trebuchet launcher crashes repeatedly, making phone unusable
MTP and PTP Modes cannot be selected under USB Connection menu, Settings Crashes. Setting does not save.
Trebuchet unable to remove widgets due to missing "X"
CHANGELOG
Code:
[B][U]07/22/2014[/U][/B]
[LIST]Updated recovery to 6.0.5.3[/LIST]
[LIST]Fix for flashing older zips[/LIST]
[LIST]Fix for partitioning SD card from Advanced menu[/LIST]
[B][U]07/22/2014[/U][/B]
[LIST]Trebuchet now able to remove widgets(Temporary workaround)[/LIST]
[LIST]Version bump to 4.4.4_r2[/LIST]
[LIST]Kernel updated to 2.6.36.1 (as well as various tweaks)[/LIST]
[LIST]Changed default governor to SmartAssH3, as it seems to be stable now on the ChaCha[/LIST]
[LIST]Arabic keyboard SHOULD be fixed, please give feedback[/LIST]
[LIST]Symbols/Zero key should now bring up the Symbols menu, and allow FN+0 to type "0" (thanks [URL="http://forum.xda-developers.com/member.php?u=3517907"]WinSuk[/URL]![/LIST]
[LIST]"F"(Facebook) key has been re-enabled and now launches the Browser[/LIST]
[LIST]Re-fixed camera orientation[/LIST]
[LIST]Recovery updated to 6.0.5.2, Softkeys now work, Swipe should work, Lights removed(no need for it)[/LIST]
[B][U]06/13/2014[/U][/B]
[LIST]Dialer and Contacts List no longer crash on incoming/outgoing calls[/LIST]
[LIST]Trebuchet no longer crashes repeatedly[/LIST]
[LIST]Changed default CPU Governor to minmax[/LIST]
[B][U]06/08/2014[/U][/B]
[LIST]Fixed Camera Orientation/Rotation (thanks [URL="http://forum.xda-developers.com/member.php?u=5095490"]Kevinjoa[/URL]!)[/LIST]
[B][U]06/07/2014[/U][/B]
[LIST]CM/androidarmv6/Google/AOSP upstream (incl. Android 4.4.3)[/LIST]
[LIST]Disabled fading edges on text for a small speedup - [URL="http://winsuk.net/screens/liberty/fadingbefore.png"]before[/URL], [URL="http://winsuk.net/screens/liberty/fadingafter.png"]after[/URL][/LIST]
[LIST]Switched to gps.conf with SUPL (assisted GPS) support[/LIST]
[LIST]Changed default CPU Governor to ONDEMAND[/LIST]
[LIST]Changed default min. CPU frequency to 245 Mhz[/LIST]
[B][U]06/04/2014[/U][/B]
[LIST]Included additional Keyboard Layouts (the Symbols/zero key currently isn't behaving properly. fix for this soon I hope)[/LIST]
[LIST]Wifi Fix.[/LIST]
[LIST]New Simplicit-ULTiMATE kernel[/LIST]
[LIST]Included Bare Minimum GApps[/LIST]
[LIST]Disabled First Boot Setup Wizard[/LIST]
[B][U]05/30/2014[/U][/B]
[LIST]First Build.[/LIST]
CREDITS
TeamSimplicit (Olivier, izi501, feroxx, Kevinjoa, thehacka1, WinSuk, Mazer.One)
benjamingwynn, niks255
androidarmv6
JDevs and the OWL Team
luzifer1984, adlx.xda
CyanogenMod
DOWNLOAD
ROM | Mirror
GApps to Cache | Mirror - Thanks to WinSuk for this (original thread)
SCREENSHOTS
RECOVERY
Recovery gets built with rom, I will update this anytime the recovery is changed.
Current Version is 6.0.5.3
Download Here | Mirror
How to flash recovery:
Terminal Method:
Stick the "recovery.img" file on the root of your sdcard. Open a terminal emulator, and type:
Code:
su
flash_image recovery /sdcard/recovery.img
After typing "su" you'll want to allow terminal emulator root access.
Fastboot method:
Stick the "recovery.img" file in the same directory as your fastboot executable binary.
Put your phone in fastboot mode.
Open a command prompt and use the fastboot tool to type:
Code:
fastboot flash recovery recovery.img
PH06IMG.zip method:
Put your phone in fastboot mode, and use the fastboot tool to type:
Code:
fastboot getvar all
You'll want to make note of the "version-main" value, the "cidnum" value, the "modelid" value, and the "hbootpreupdate" value.
Stick the "recovery.img" file in a folder somewhere, and create a new text document called "android-info.txt"
Put the values you noted earlier into the "android-info.txt" in the following format(this one works for my device):
Code:
modelid: PH0613000
cidnum: TELUS001
mainver: 1.60.0.0
hbootpreupdate: 12
note that "mainver" is the value you noted earlier from "version-main".
Now zip the "recovery.img" and the "android-info.txt" together, and name it "PH06IMG.zip"
Put that file on the root of your sdcard, and reboot into the bootloader. It should detect the zip, and ask you to update. choose yes, and you're off to the races!
SOURCES
androidarmv6/android
androidarmv6/android_device_htc_chacha
androidarmv6/android_device_htc_msm7x27-common
androidarmv6/android_kernel_htc_msm7x27
androidarmv6/proprietary_vendor_htc

Removed

Finally CM 11 in HTC chacha, i will Test it as soon as i can
i Made this Key Character Map File for "Arabic", Please add it to your Build
chacha-keypad-ara.kcm.zip
Thanks kronflux, Olivier, and all the Simplicit Team for this Great Effort :good:

Will add that, thanks.
Gesendet von meinem Xperia S mit Tapatalk

I am Really Enjoying Kitkate right now
———
Installing Steps:
1) I Tried to install the Recovery using the boot loader method but it failed with an error "CID incorrect, update fail”.
So i used fast boot Method with my PC & this command "fastboot flash recovery recovery.img”
2) Installed The Rom
3) Installed “CronMod-INT2EXTV2+_signed.zip” (Great INT2ext mod to increase internal Memory form SD card, now 1.5GB) :angel:
The system Feels good, but i couldn’t live with it without updating the minimum CPU frequency to 245 MHZ
Problems i faced At my first look
System:
Wifi & Hotspot NOT working
Bluetooth NOT working
USB Mass Storage Mode (UMS) NOT working ( I can Not connect my phone to the pc with any mean )
3G Stop working after WAKE - I Must Manually disable and re-enable it
Battery Still Testing
Apps:
Camera image is rotated !
Phone app buttons really needs to be reorganised
Keyboard:
@ and ~ are misplaced , should be switched (FN+y) with (FN+p)
No Number “0”
Lang, & Facebook Keys are not Functional
No Arabic Keyboard
Overall, Very Good for a First Build. I am Excited to Test the Next Build and i am ready for Testing

Yehia2amer said:
[*]USB Mass Storage Mode (UMS) NOT working ( I can Not connect my phone to the pc with any mean )
Click to expand...
Click to collapse
I will say that mass storage mode works perfectly for me. but I will do some testing with other micro sd cards, and see what happens.
But thanks for testing!

((
Good JOB...
Lot's of problems... it's better that we think about a new KERNEL:good: instead of a new ROM...

mortal19xx said:
Good JOB...
Lot's of problems... it's better that we think about a new KERNEL:good: instead of a new ROM...
Click to expand...
Click to collapse
Keep in mind, this is absolutely NOT a stable release. entirely a testing/dev release.
That having been said, if you want to start the efforts of working on a new kernel, I certainly wouldn't complain, and I'd even try my best to help.

[A]
kronflux said:
Keep in mind, this is absolutely NOT a stable release. entirely a testing/dev release.
That having been said, if you want to start the efforts of working on a new kernel, I certainly wouldn't complain, and I'd even try my best to help.
Click to expand...
Click to collapse
Keep going... :good:

Hey guys,
you can flash my kernel if you want. I have fixed wifi.
Gesendet von meinem Xperia S mit Tapatalk

thanks
i m glad to see our chacha reborn with new build and developers, thank you guys for the time you spend on this phone
keep up
i'll test and report

Olivier said:
Hey guys,
you can flash my kernel if you want. I have fixed wifi.
Click to expand...
Click to collapse
When talking about a new kernel: Is it possible to enably 2-way-call-recording there?

Flexmaen said:
When talking about a new kernel: Is it possible to enably 2-way-call-recording there?
Click to expand...
Click to collapse
It's certainly possible. I don't know if I'll do it to my own fork of the currently used kernel, or if maybe Olivier will do it, but I will definitely look into it in the next few days, see what I can come up with. I have found a patch used on a samsung device that uses the msm7227 like our device, so as long as it's similar enough, and still works with kitkat, it shouldn't be too hard.
No promises though

kronflux said:
It's certainly possible. I don't know if I'll do it to my own fork of the currently used kernel, or if maybe Olivier will do it, but I will definitely look into it in the next few days, see what I can come up with
Click to expand...
Click to collapse
Ah ok great.
Anyway, the biggest downside of the custom roms for the Chacha is the bad keyboard integration. If you compare it with a Nokia E71, the original ROM is already bad. But if you use a custom ROM, than you are lacking even more keyboard shortcuts (especially when handling calls). So I guess improving this would be the best thing for this phone.
But let's see... whatever you decide it's great there there is still so much work going on for this phone!

Flexmaen said:
the biggest downside of the custom roms for the Chacha is the bad keyboard integration.
So I guess improving this would be the best thing for this phone.
Click to expand...
Click to collapse
Unfortunately, I can only judge by the English keyboard configurations, because I don't know any other languages xD
But the next build(which, if all goes well, will be later this afternoon/evening) will have the keyboard configs the same as the other recent custom roms, primarily the ones by adlx.xda, as it's his repos we got the configs from.
But after I release this new update, if you tell me what's wrong with the keyboard specifically, I may be able to help out a little.

ohh finally ! , how good of you , i will try it sure and tell you if there is anything wrong .. but is the kernel support swap ? , and the keyboard support arabic language and the buttons ? thanks alot

mohabmoka said:
ohh finally ! , how good of you , i will try it sure and tell you if there is anything wrong .. but is the kernel support swap ? , and the keyboard support arabic language and the buttons ? thanks alot
Click to expand...
Click to collapse
the next release(which is currently compiling. takes a LONG time xD) SHOULD have proper arabic support, and I believe it does support swap, but I don't know for sure.

good xD , and please if you can , attach pics of the rom

Is it mandatory to install recovery v 6 to flash this?

swashie said:
Is it mandatory to install recovery v 6 to flash this?
Click to expand...
Click to collapse
no, however it is recommended, and I can't guarantee that future releases of the rom won't require it.

Discusion about Android Lollipop (initially for Mi3W)

Hello,
This is a thread about Android Lollipop for Mi3W. I make it because this build by Ivan is also compatible with the Mi4W. I can't share links because it's not my work and Ivan didn't release his sources. I make it for discussing around this build and your feedback because I think we should not spam Mi3 section with feedbacks about Mi4.
Here are some of my screenshots :
{
"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"
}
With some test I can say that on Mi4 :
-Video recording is broken (but can be fixed using one+one camera app)
-HDR picture doesn't work with stock google camera
-Good picture quality
-Good sound quality (better than MUI with headset in my opinion, in fact I use a jack-tape adapter in my care and sound is less saturated for higher volume)
-No random reboot on this device (contrary as Mi3 wich reboot in deep sleep mode)
-No unlock with menue keys (contrary as Mi3)
-USB OTG working
-Wifi and bluetooth working perfectly (and MiBand is compatible)
-MMS not send while using wifi (normal but MIUI is capable of auto switch between Wifi and mobile data for sending or receiving an MMS)
The last but not the least :
On Mi4 it seems that maximum CPU frequency is lower than normal (Mi3 users have 2.3GHz and they run 2.3GHz on lollipop), I'm not sure if it's 1.1GHz or 1.7GHz max on Mi4 but I tried several overclock apps wich allows me to get 2.5 but only when they are open, after frequency automatically switch to a lower frequency (tested with stress test, and observed with cpu spy). So it seems impossible te get higher frequency on this device.
Anyway wit such low frequency Lollipop still smooth to use.
If someone managed to make it run higher that would be nice to know how.
And you what's your opinion about this port?

I flashed Lollipop 2 day ago. No problems at all, except the camera bug but I'm using one+one camera and I don't have any problems. Regarding the frequency, I hope Ivan will fix it even if the device runs very smooth (more than Miui 6) also with the lower frequency (it could be an advantage for battery saving). Maybe picture and video quality could be better but except this I'm very satisfied with this rom.

I hope the same, that would be perfect to have a fully working Android L on our devices. MIUI is not smooth at all in balanced mod. And with android L everything is smooth with lower frequency. It seem that MIUI is only good with high frequency CPU...

lollipop issues
I found some issues like wifi stop working and its hard to reconect this also applies for celular network like when using a elevator (normal), the signal is gone but after you leave the elevator it keeps without signal for a while.
Improvements reboot to recovery and screenshot would be nice
The volume widget is usefull but if you could add a volume icon in the notification bar would be awesome. (Also be able to modify this icons wold be nice)
Sometimes the gps keeps turned up even with no apps using it
I dont like voice commands or voice talk to write so i disable but when i disable after reboot if keeps active strange.
But beside that a ****ing awesome rom to my opinion the best one

https://mega.co.nz/#!kwFCXD5A!c7ama3gHUVLYlF754BtkihOpe8EURnOyBwVZA0LEKpc
Sorry for spamming.. Can test this and report back if it work on Mi4..this CM12 for Mi3.. Just give feedback here. List all bug if you can. Thanks.

audahadi said:
https://mega.co.nz/#!kwFCXD5A!c7ama3gHUVLYlF754BtkihOpe8EURnOyBwVZA0LEKpc
Sorry for spamming.. Can test this and report back if it work on Mi4..this CM12 for Mi3.. Just give feedback here. List all bug if you can. Thanks.
Click to expand...
Click to collapse
Hi, It's not spamming, no problem guy, I was spamming Mi3 sections about flashing these roms on Mi4.
Basically yes it'll boot on this device but only if you first get a perfectly clean phone (No miui installed and full wipe performed), let me explain, I hope to be clear :
- I managed to flash the previous build without TDB and makes it boot, but I had got a bunch of FC (not efficient wipe) and Gapps where not present even after flashing micro Gapps.
-With TDB enabled, installing CM12 result on non booting CM12 (bootloop or trying to boot on MIUI but with bootloop) and totally messing my MIUI rom on system 1. Plus messing my sdcard (all files placed in a folder called (0)
The biggest issue with flashing CM12 build comes from CWM recovery, I guess all the CancroCM team should start by working on a perfect CWM recovery. Because the ones we actually have (furniel and donbot's one) :
-Are not able to dual boot MIUI and CM12 (as it's an alpha an I only have one phone I use it as daily basis so I can't afford to always restore it, I need a perfecly working rom too)
-Are not able to perform any wipe (cache, dalvik, data) this results on not working rom (doesn't flash rom or rom get into bootloop at first start)
So if your team have some time to check it that would be perfect. I really hope you'll do something for a perfect CWM. Because I love CM (more than MIUI) and I really appreciate your work that's why I want to test it but I need to keep another rom.

Riichard63 said:
Hi, It's not spamming, no problem guy, I was spamming Mi3 sections about flashing these roms on Mi4.
Basically yes it'll boot on this device but only if you first get a perfectly clean phone (No miui installed and full wipe performed), let me explain, I hope to be clear :
- I managed to flash the previous build without TDB and makes it boot, but I had got a bunch of FC (not efficient wipe) and Gapps where not present even after flashing micro Gapps.
-With TDB enabled, installing CM12 result on non booting CM12 (bootloop or trying to boot on MIUI but with bootloop) and totally messing my MIUI rom on system 1. Plus messing my sdcard (all files placed in a folder called (0)
The biggest issue with flashing CM12 build comes from CWM recovery, I guess all the CancroCM team should start by working on a perfect CWM recovery. Because the ones we actually have (furniel and donbot's one) :
-Are not able to dual boot MIUI and CM12 (as it's an alpha an I only have one phone I use it as daily basis so I can't afford to always restore it, I need a perfecly working rom too)
-Are not able to perform any wipe (cache, dalvik, data) this results on not working rom (doesn't flash rom or rom get into bootloop at first start)
So if your team have some time to check it that would be perfect. I really hope you'll do something for a perfect CWM. Because I love CM (more than MIUI) and I really appreciate your work that's why I want to test it but I need to keep another rom.
Click to expand...
Click to collapse
Which cwm u used?..

Hadi al-Haiqal said:
Which cwm u used?..
Click to expand...
Click to collapse
I was using the furniel and donbot 11th release (r11) 6.0.5.1
Envoyé de mon MI 4W en utilisant Tapatalk

Riichard63 said:
Hi, It's not spamming, no problem guy, I was spamming Mi3 sections about flashing these roms on Mi4.
Basically yes it'll boot on this device but only if you first get a perfectly clean phone (No miui installed and full wipe performed), let me explain, I hope to be clear :
- I managed to flash the previous build without TDB and makes it boot, but I had got a bunch of FC (not efficient wipe) and Gapps where not present even after flashing micro Gapps.
-With TDB enabled, installing CM12 result on non booting CM12 (bootloop or trying to boot on MIUI but with bootloop) and totally messing my MIUI rom on system 1. Plus messing my sdcard (all files placed in a folder called (0)
The biggest issue with flashing CM12 build comes from CWM recovery, I guess all the CancroCM team should start by working on a perfect CWM recovery. Because the ones we actually have (furniel and donbot's one) :
-Are not able to dual boot MIUI and CM12 (as it's an alpha an I only have one phone I use it as daily basis so I can't afford to always restore it, I need a perfecly working rom too)
-Are not able to perform any wipe (cache, dalvik, data) this results on not working rom (doesn't flash rom or rom get into bootloop at first start)
So if your team have some time to check it that would be perfect. I really hope you'll do something for a perfect CWM. Because I love CM (more than MIUI) and I really appreciate your work that's why I want to test it but I need to keep another rom.
Click to expand...
Click to collapse
For now we only support installation on system 1.. No dualboot. But we'll look at this.

audahadi said:
For now we only support installation on system 1.. No dualboot. But we'll look at this.
Click to expand...
Click to collapse
Oh okay, nice to hear some news, I hope that'll be possible

audahadi said:
For now we only support installation on system 1.. No dualboot. But we'll look at this.
Click to expand...
Click to collapse
Oh but if only system 1 is supported that means that there is a script on the zip file that force flash to system 1 right? So that may be why I was thinking that wipe with this recovery wasen't efficient.

[KERNEL][.253][Z3+/Z3+ Dual] OM5Z Kernel

{
"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 am NOT resposible for any damage done to your device, your neighbor, or any other things you like/hate.​
Introduction:
Myself5 said:
@oshmoun and I were in need for a custom stock kernel to mess with. Since all the available Options were not fitting our needs, or gave us bad experience on some aspects, and we knew about Zombie Kernel from Tom, we decided to start working on that. So I brought up support for the Z5, we ported Kexec to it, updated it to 224 and added various things. Since the kernel gave us very good experiences, we decided to make it accessible to the public.
About:
This Kernel is based on @Tommy-Geenexus Zombie Kernel. He was ok with us continuing/porting his projects, so oshmoun, and me started to create the "oshmoun Myself5 Zombie Kernel" aka OM5Z Kernel.
Click to expand...
Click to collapse
After the v2.0 release, @Olivier, @a-st and I decided to make it for Z3+ single and dual SIM. We hope you'll enjoy it!
Features and Commit History:
Check 2nd Post!
Installation Instruction:
THIS DOES ONLY WORK ON UNLOCKED BOOTLOADER!
You can either flash the provided boot.img via fastboot, or flash the zip in recovery.
Additional Information:
The Kernel is underclocked by default. Both Cluster are underclocked to 1,344/1,536 GHz respectively, resulting into HUGE Temperature improvements. However, due to public demand, V2 features the ability to disable the underclock (in case you need to make some baked Eggs real quick, whatever). All you need to do is run this code after boot (Kernel Adiutor has the abilty to execute scripts at startup, just a reminder).
Code:
echo "0:4294967295 1:4294967295 2:4294967295 3:4294967295 4:4294967295 5:4294967295 6:4294967295 7:4294967295" > /sys/module/msm_performance/parameters/max_cpu_freq
What it effectively does, is resetting the max clock limit for each core to the default (unset) values, allowing you to set whatever frequency (from the ones available ofc) you want.
Download:
OM5Z Kernel (Release Versions)
---> DevDB download section <---
boot_ivy_OM5Z_253.img
OM5Z-Kernel-V2.0-M-ivy.zip
boot_ivy_dsds_OM5Z_253.img
OM5Z-Kernel-V2.0-M-ivy_dsds.zip
Naturally, ivy_dsds files are for Dual SIM, ivy for Single SIM
Myself5 said:
Thanks/Credits:
Tommy-Geenexus - You can guess why
oshmoun - for obvious reasons
FreeXperia Team (especially Jerpelea) - for too many things!
CarbonRom Team - for too many things!
phaseburn - for being a good friend and helping me with almost everything !
infected_ - for help with SM!
My Big Brother Eric - for helping me keeping focused on Development!
My friend Silas - for letting me use his servers and being awesome!
If I forgot you, please tell me.
If you think we deserve a donation, I won't stop you
To Donate to Tommy-Geenexus:
To Donate to me:
To Donate to oshmoun:
PM Spam him to create a PayPal Donation system, he doens't have one yet
Thanks a lot to those who have donated!​
Click to expand...
Click to collapse
Myself5 said:
Additional Information:
As you might have seen in my MultiROM Thread, some stock kernels require different Recovery Images than AOSP Kernels. We set an end too this, and fixed init_sony, rather than using some very outdated software which somehow works. This means, you might need to use a different recovery with this kernel if you're currently on a "stock" recovery. We're hoping that other stock kernel devs adapt our solution, so we can set an end to the old scripts.
Click to expand...
Click to collapse
XDA:DevDB Information
OM5Z Kernel, Kernel for the Sony Xperia Z4
Contributors
airlessproject, Olivier, a-st
Source Code: https://github.com/Myself5/android_kernel_sony_msm8994_OM5Z
Kernel Special Features:
Version Information
Status: Stable
Current Stable Version: v2.0
Stable Release Date: 2016-07-19
Created 2016-07-19
Last Updated 2016-07-21

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/

My E6533 got in bootloop.
Edit: waited for recovery to flash supersu and xposed. Since twrp wasn't there, so it bootlooped. Will try again. Error was on my end.

waseemakhtar said:
My E6533 got in bootloop.
Click to expand...
Click to collapse
- .253 stock ROM?
- where does it hang, kernel logo or bootanimation?
- which file did you flash?
- did you have xposed or supersu installed before? if yes, did you reinstall them after flashing the kernel?

Nice to have more options with another Kernel. Was waiting for a Kernel which is underclocked by default. Flashing Kernel+SuperSu 2.76+Systeless Xposed 85.7 went fine (E6553+.253). After that i had to flash twrp to "recovery" partition, FOTA-twrp doesnt boot. Looks really good for the first few minutes.

Trilliard said:
Nice to have more options with another Kernel. Was waiting for a Kernel which is underclocked by default. Flashing Kernel+SuperSu 2.76+Systeless Xposed 85.7 went fine (E6553+.253). After that i had to flash twrp to "recovery" partition, FOTA-twrp doesnt boot. Looks really good for the first few minutes.
Click to expand...
Click to collapse
hey buddy thanks for the nice words, I hope you'll enjoy the kernel.
btw the "recovery" partition is an alias for FOTAKernel afaik, so I don't quite get "FOTA-twrp doesnt boot", tho I must admit I don't know what's FOTA-twrp
I mean as you said, I too flashed twrp to recovery and it works with volume up on the purple led just as it should..

airlessproject said:
hey buddy thanks for the nice words, I hope you'll enjoy the kernel.
btw the "recovery" partition is an alias for FOTAKernel afaik, so I don't quite get "FOTA-twrp doesnt boot", tho I must admit I don't know what's FOTA-twrp
I mean as you said, I too flashed twrp to recovery and it works with volume up on the purple led just as it should..
Click to expand...
Click to collapse
Well i´m not that into recoverys with sony devices as this is my first and there seems to be a difference between flashing twrp from pc to "recovery" and flashing twrp to FOTA Kernel like this. I dont know if it is the same at the end, but some Kernels have twrp included, some not. If you change the Kernel you cant use twrp without flashing it new. I allways had htc devices before and you only flash twrp once and it´s there allways and forever xD. After flashing your Kernel it recognizes my TWRP in FOTAKernel, yellow led went on and changed to purple after pushing vol- but it doesnt boot, just purple led for two minutes after that i rebooted. As i said just flashed it to recovery and everything is working fine.

Trilliard said:
Well i´m not that into recoverys with sony devices as this is my first and there seems to be a difference between flashing twrp from pc to "recovery" and flashing twrp to FOTA Kernel like this. I dont know if it is the same at the end,
Click to expand...
Click to collapse
I think these two methods should have the exact same result at the end, but I may be mistaken
Trilliard said:
but some Kernels have twrp included, some not. If you change the Kernel you cant use twrp without flashing it new. I allways had htc devices before and you only flash twrp once and it´s there allways and forever xD. After flashing your Kernel it recognizes my TWRP in FOTAKernel, yellow led went on and changed to purple after pushing vol- but it doesnt boot, just purple led for two minutes after that i rebooted. As i said just flashed it to recovery and everything is working fine.
Click to expand...
Click to collapse
it should be vol+ I think, vol- is usually for the in-kernel recovery (from my experience with Xperia Z)..
anyway for me it worked after I reflashed the kernel for testing purposes, it entered twrp when I press vol+ (didn't try vol- tho)
also yes, this kernel doesn't include twrp in itself so you'd have to either use the one in FOTAKernel/"recovery"

just to be sure, this kernel supports root right? :angel:

could someone report performance, temprature, stability, lags, and such?
Thanks!
---------- Post added at 19:47 ---------- Previous post was at 19:36 ----------
Misanful said:
just to be sure, this kernel supports root right? :angel:
Click to expand...
Click to collapse
most probebly does why make a rom without root acces?

bjowol said:
could someone report performance, temprature, stability, lags, and such?
Thanks!
Click to expand...
Click to collapse
I think it´s too early to say something definitive but it looks really good, temperature is a little bit lower than with Stock or any other Kernel. I dont see any differences for the perfermance between this and Stock or AndroPlus, so far no laggs or bootloops or other problems.

Trilliard said:
I think it´s too early to say something definitive but it looks really good, temperature is a little bit lower than with Stock or any other Kernel. I dont see any differences for the perfermance between this and Stock or AndroPlus, so far no laggs or bootloops or other problems.
Click to expand...
Click to collapse
ok thanks, have u done any thermal throttling modifications?

bjowol said:
ok thanks, have u done any thermal throttling modifications?
Click to expand...
Click to collapse
No, just flashed kernel, su, xposed and twrp and thats it. But usually testing a new kernel takes a few days, thats all first impression.

Trilliard said:
No, just flashed kernel, su, xposed and twrp and thats it. But usually testing a new kernel takes a few days, thats all first impression.
Click to expand...
Click to collapse
Alright sure! but as you may know, i have an unusual hot device, and on stock configurations it reaches 60 degrees really quickly. and on stock config 60 degrees is the point when the device starts to throttle, and degrade performance. But thank you, i think ill try it out!

Misanful said:
just to be sure, this kernel supports root right? :angel:
Click to expand...
Click to collapse
Sure does. Just flash systemless SuperSU (last stable is always tested with the kernel).
bjowol said:
could someone report performance, temprature, stability, lags, and such? [emoji14]
Thanks!
---------- Post added at 19:47 ---------- Previous post was at 19:36 ----------
most probebly does why make a rom without root acces?
Click to expand...
Click to collapse
Performance should technically be a tad worse than other kernels, caused by the underclock. HOWEVER, due to the S810s hot nature, it wont run very long on its highest clock, and will underclock (even under our underclock limit) rather fast. So after all, you probably wouldnt see MUCH degradation especially not in real life situations, if at all you'd see them in Benchmarks. Temperature, should be way better than on stock thanks to the underclock (my Z5 is IMO cooler than my Z3 on Carbon LP and a performance optimised Kernel (M5 Kernel).
Lags: Helll naaahhh.
Stability: Using the kernel since release (that is Z5 release ofc) +1 Month. Had 3 reboots I am aware of. All while playing Pokemon Go. So, not sure if kernel or Game related at this point.
And Such: You won't see as much features in OM5Z as other competitiors provide. Thats because we focus on having a simple, basic daily usage kernel, with small and sensible additions here and there (e.g. kexec).
Hope that clears some stuff up.
Sent from my E6653 using Tapatalk

Testing it !
Hi,
12hr using, so far everything works well, no boot loop, no hangs, no lag,
For those who like me are not as expert as others a resume what i did:
* Download .253 from xperifirm (Custum DE)
* Remove fwinfo file from download
* Create flashable bundle (omit all .ta files) on flashtool (Answer no to script question)
* Backup (always backup )
* Flash bundle into the phone... I didn't wipe userdata but i can be done (Answer no to script question)
* Restart into system normally
* Flash vía terminal (cmd on windows) this kernel "boot_ivy_OM5Z_253.img" --- To get fastboot mode (Hold volume + while conecting usb cable until blue led flashes)
fastboot flash boot boot_ivy_OM5Z_253.img
* Flash twrp 3.0.2 for ivy
fastboot flash recovery twrp-3.0.2-0-ivy-20160606.img
* Restart on recovery twrp ( Power on phone, pres vol+ once while orange led flashes)
* Flash newest superSu stable (2.76 at this time) vía flash zip
* Wipe caches
* Restart to check root :good:
Enjoy this awesome work ... thaks

Your Kernel is working really good when using it as a "user" but something is a little bit wired with this Kernel. I dont get full access to the whole System. When using TWRP it doesnt show the temperature and it doesnt show severall partitions like oem an these small ones. When Android is booted i get access to all partitions using a root explorer, but cannot access all files on all partitions. All other Kernels have no problems with this, testet all there are for our device (stock,androplus,zach´s) and om5z is the only Kernel which produces this phenomenon. Would be wonderful if you can fix this, it´s a great kernel for daily usage.

Trilliard said:
Your Kernel is working really good when using it as a "user" but something is a little bit wired with this Kernel. I dont get full access to the whole System. When using TWRP it doesnt show the temperature and it doesnt show severall partitions like oem an these small ones. When Android is booted i get access to all partitions using a root explorer, but cannot access all files on all partitions. All other Kernels have no problems with this, testet all there are for our device (stock,androplus,zach´s) and om5z is the only Kernel which produces this phenomenon. Would be wonderful if you can fix this, it´s a great kernel for daily usage.
Click to expand...
Click to collapse
other kernels have twrp embedded in the boot.img, using rootkernel script. That one is modified to fix the cpu temp issue you mentioned, and also offers the ability to mount the other partitions.
OM5Z boots recovery from the FOTA/recovery partition, so as to try and seperate boot and recovery as much as possible. Those issues are basically recovery issues, not so much kernel issues.
About access to partitions on android, did you install supersu?

Trilliard said:
All other Kernels have no problems with this, testet all there are for our device (stock,androplus,zach´s)
Click to expand...
Click to collapse
did you actually use pure stock kernel from the firmware or you used the one repacked with the rootkernel script @oshmoun mentions?
also should be noted that you can use twrp with pure stock kernel only by fastboot boot, not by fastboot flash recovery because stock doesn't have init_sony and purple keycheck light
oshmoun said:
About access to partitions on android, did you install supersu?
Click to expand...
Click to collapse
I think he meant he has access to partitions inside the ROM, only not in recovery..
PS I had only 2% overnight drain in almost 7 hrs with wifi on and being logged in on several huge drainers like Facebook, Messenger, Viber etc.. whereas before I had always >1% per hour
That should say enough about this kernel's power savings... Simple stuff but pretty effective

I used Stock Kernel with rootkernel mod. And yes your declaration that this is related to the recovery itself makes sense. The Problem with access to some files when android is booted could also be relatet to latest systemless root (2.76) i dont know. I had access to all partitions when android was booted but not the rights to access some of the files (copy or delete files).
Well cause of the limitations of twrp which could be used with your Kernel, i cant use it for the Rom i´m actually working on, need access to all partitions hehe. Is there a way to integrate modified twrp into your Kernel?
The power savings are awsome, no other Kernel has such a good batery life.

[ROM][7.1.2][AOSP] Android N for MeMOPAD 10 FHD LTE

Android N for the MeMOPad FHD 10 4G - ME302KL ​
{
"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
* do some research if you have any concerns about features included in this ROM
* 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.
*/
Talking about Overclocking:
Overclocking (or underclocking) is optional. The installer lets you choose the maximum frequency. You can set the maximum frequency individually for each CPU core in the installer. Whatever frequencies you chose in the installer will be set at boot for each CPU. Not all devices can handle overclocking. The stock maximum CPU frequency is 1512MHz. I recommend a mild overclock, like 1728MHz for daily use. Clocking higher creates heat and wastes battery for very little performance gain. (FROM ELEMENTALX POST)
talking about CPU voltages
The installer allows you to choose from several undervolting options. These automatically undervolt the lowest frequency (384MHz) where the CPU spends most of its time. The voltages for other frequencies are assigned based on the PVS bin of your phone. CPU voltages are fully customisable with apps such Kernel Tuner or Trickster Mod, but I recommend leaving these other voltages as-is unless you are prepared to do a lot of testing. Be careful, lowering voltages can cause instability. Generally, having reboots while the phone is asleep or other weird problems is a sign that your minimum voltage is too low. The minimum voltage allowed is 700mV. (FROM ELEMENTALX POST)
Max CPU Freqs avaiable (0ver stok 1512000) : 1620000, 1728000, 1836000, 1890000, 1944000, 2052000, 2160000, 2214000
Max GPU Freqs avaiable (Over stock 400): 450, 477, 491, 504, 531, 555, 585
talking about GPU Governor
In wizard you can choose also the simple governor.
Installation
You have to unlock tablet with asus app.
You have to use SevenMaxs TWRP RECOVERY for Me302kl
1. Download the ROM from the link below
2. Download GAPPS (OpenGapps Micro tested)
3. Transfer the zip files to your SD card
4. Reboot to recovery mode
Note: You Must use TWRP recovery
5. Optional: Do nandroid backup
6. Wipe data / Factory Reset
7. Install the rom zip
8. Install GAPPS
9. Install SuperSU to root the Tablet
10. flash Overlay Fix and Init.d Enabler https://www.androidfilehost.com/?fid=529152257862728608
11. Reboot to system
Enjoy Android 7.x !
The ROM is not rooted, so you have to download and install SuperSU with TWRP. You have to use SuperSU
To Set Overclock/undervolt Parameters:
1) go again in TWRP and flash the ElementalX for ME302KL Zipfile
2) follow the wizard to set the parameters
3) reboot the tablet.
4) Use EX Kernel Manager fron google play or Kernel Adiutor to fine tuning of these parameters.
-----------------------------------------------------------------------------------------------------------------------------------------------------------
Download 7.1.2 r12 Releasehttps://www.androidfilehost.com/?fid=817550096634776292
with ExKernel 6.08 inside. https://www.androidfilehost.com/?fid=889764386195906335
ATTENTION !!!!
This is a new release wit a new kind of ramdisk. System is adapted to it too
Don't install older release of Ex Kernel (before 6.08) or Glitch Kernel (before r566) on this rom if you don't want a bootloop...
Download TWRP Recovery by SevenMaxs : http://forum.xda-developers.com/showpost.php?p=68444210&postcount=44
To install recovery exstract frm the zip the file recovery.img and put it on the sdcard.
Then connect to the tablet with adb:
Code:
adb shell
su
dd if=/sdcard/recovery.img of=/dev/block/mmcblk0p25
Reboot into recovery VOL+ AND POWER
-----------------------------------------------------------------------------------------------------------------------------------------------------------
Source
Check out the KERNEL Source available on https://github.com/yatto/ElementalX
The rom is the Nexus 7 AOSP 7.1.2 Nougat by @DevSwift1 and @zaclimon and @followmsi without some libs : system/lib/keystore.msm8960.so and others and with the /system/vendor/lib/files from Me302kl 4.2.2 ROM
Feel free to submit any fixes, Just remember to give proper credits when using other people's source.
Credits
@DevSwift1
@zaclimon
@SevenMaxs
@followmsi
-----------------------------------------------------------------------------------------------------------------------------------------------------------
XDAevDB Information
Android Nougat AOSP 7.1.2 for Me302kl, ROM for the Asus MeMO Pad FDH 10 LTE
ROM OS Version: 7.x
ROM Kernel: Linux 3.4.x
Version Information
Status: Stable

If you have previously flashed CM13 with f2fs filesystem on data and cache, remember to convert to ext4 again because this is an AOSP ROM so doesn't supprt f2fs filesystem.
Later this evening i'll try to flash Asus Apps and if they will work i'll make flashable zips for community and i'll share here with some screenshots.
I also will test if this AOSP has the same issues of Nexus 5 Nougat rom.
Thank you Yatto!!!!!!!!!!!!!!!!!

Screenshots

@GiGiSSiMo: AMAZING...

Well, I made what you wrote:
1) Flash ROM
2) Flash NANO Open GApps
3) Flash SuperSU version suggested as OP
4) Boot and configure your Google account
5) Install from Play Store ZenUI Launcher
5) Flash the Asus App file.
I only have to install IME apk for Asus keyboard. All the Asus Apps are working fine...
Good JOB !

Instructions zenUI
1) Flash ROM
2) Flash NANO Open GApps
3) Flash SuperSU version suggested as OP
4) Boot and configure your Google account
4 BIS) Install from Play Store ZenUI Launcher https://play.google.com/store/apps/details?id=com.asus.launcher
5) Flash the file I will attach later (I'm writing from tab): https://www.sendspace.com/file/9izug7
6) Boot tablet and reinstall by APK you find into the zip file gallery and ime (keyboard)
7) Enjoy

Amazing, you are unstoppable! ^_^
I tried this ROM and I can say that it works very well.
I think the only bugs I noticed so far are those two that also occurred with CM roms.
The first one is those blue flashes that appear when using keyboard.
And the second one is that it' impossible to power off tablet if it's connected to a charger or PC - it'll power on again.
That's all that got my attention for now.
By the way, tutorial in the main post says "7. Install CM zip", while this ROM isn't CM. ^^

redunka said:
Amazing, you are unstoppable! ^_^
I tried this ROM and I can say that it works very well.
I think the only bugs I noticed so far are those two that also occurred with CM roms.
The first one is those blue flashes that appear when using keyboard.
And the second one is that it' impossible to power off tablet if it's connected to a charger or PC - it'll power on again.
That's all that got my attention for now.
By the way, tutorial in the main post says "7. Install CM zip", while this ROM isn't CM. ^^
Click to expand...
Click to collapse
For keyboard flashing you have to enable developer options and enable disable overlay hw, or install zenui kB. [emoji6]

GiGiSSiMo said:
For keyboard flashing you have to enable developer options and enable disable overlay hw, or install zenui kB. [emoji6]
Click to expand...
Click to collapse
I know about those solutions.
But I would like to see this issue fixed completely.

Some bugs:
1) adopted storage formatting exit with errors, SD card results broken and needs formatting again, but works only as external storage
2) Nougat general problem /System is not mounted as rw, so apps like AdAway doesn't work: solution is through adb shell creating a symlink:
su
mount -orw,remount /system
rm /system/etc/hosts
ln -s /data/data/hosts /system/etc/hosts
mount -oro,remount /system
3) I can't access to external SD card with mame or ScummVM emulator

GiGiSSiMo said:
Some bugs:
2) Nougat general problem /System is not mounted as rw, so apps like AdAway doesn't work:
3) I can't access to external SD card with mame or ScummVM emulator
Click to expand...
Click to collapse
It Is non a Bug. It Is Android N. Adaway has a systemless host file to flash with twrp
Read here:
http://forum.xda-developers.com/showthread.php?t=2190753

redunka said:
I know about those solutions.
But I would like to see this issue fixed completely.
Click to expand...
Click to collapse
Offline Charging bug is present since Asus stock 4.2.2. My tab always poweron when i connect power source and it always return alive when poweroff withpower source.
Blue flickering is hard to fix. Many device have this bug after an update to lollipop and later....

yattodettaman said:
Offline Charging bug is present since Asus stock 4.2.2. My tab always poweron when i connect power source and it always return alive when poweroff withpower source.
Blue flickering is hard to fix. Many device have this bug after an update to lollipop and later....
Click to expand...
Click to collapse
Strange, I never had that charging bug on stock 4.2.2.
Anyway, these bugs are minor, nothing to really worry about.
Thank you for all hard work.
On an unrelated note: couldn't someone share a backup of EFS partition, please?

Do I have to install the third version of TWRP or 2.8.1 will perfectly do the trick?

SnuffyRus said:
Do I have to install the third version of TWRP or 2.8.1 will perfectly do the trick?
Click to expand...
Click to collapse
No, you have to install last recovery : ME302KL_TWRP-3.0.2.1-M by @SevenMaxs

yattodettaman said:
No, you have to install last recovery : ME302KL_TWRP-3.0.2.1-M by @SevenMaxs
Click to expand...
Click to collapse
Thanks a lot for your work, keep it up!
Some screenshots:

@all
Hello friends. What about battery in this rom? In cm 13 it has configured wrong.
And also, how i can backup my efs partition via dd?
And if I read correctly, if I install asus keyboard, i do not have any isues with blue flashes?

WARNING
I think I should warn everybody about this.
Be careful when restoring backups with TWRP 3.0.2.x.
At least three people have confirmed that restoring backups of all partitions using TWRP 3.0.2.x will brick device.
It happens only with TWRP 3.0.2.x, while TWRP 2.8.0.1 can restore backups of all partitions without any problems.
@SevenMaxs, do you have any ideas for why this may happen?

redunka said:
I think I should warn everybody about this.
Be careful when restoring backups with TWRP 3.0.2.x.
At least three people have confirmed that restoring backups of all partitions using TWRP 3.0.2.x will brick device.
It happens only with TWRP 3.0.2.x, while TWRP 2.8.0.1 can restore backups of all partitions without any problems.
@SevenMaxs, do you have any ideas for why this may happen?
Click to expand...
Click to collapse
What you mean when you say "all partitions" ? If you restore only /data /system and /boot ? What did it happen ?

LazyMind said:
@all
Hello friends. What about battery in this rom? In cm 13 it has configured wrong.
And also, how i can backup my efs partition via dd?
And if I read correctly, if I install asus keyboard, i do not have any isues with blue flashes?
Click to expand...
Click to collapse
With Asus apps (Zen Launcher and Asus Keyboard) the blue flickering's gone
Why you say that battery is wrong ? Only form mah reporting from some apps ?

[UNOFFICIAL][20191230] LineageOS 17.0 for UMIDIGI F1 [Android 10]

Introduction
This is my port of LineageOS 17.0 for the UMIDIGI F1, with things mostly working as they are expected to. This ROM depends on the official vendor image, so please be sure you are on the latest official build before flashing this ROM onto your device. Also, since these MTK devices often come with some strange variants, please be aware that your lineage may vary.
Known Bugs
- VoLTE does not work (and probably won't work on any MTK device with custom ROMs any time soon) due to MTK's proprietary extensions.
- (Fixed since 20191230) Sometimes data connection can be randomly lost during reconnections. This can be fixed by either a reboot or `pkill phone` in a root shell (terminal).
Flashing Instructions
1. You MUST flash my TWRP port available here before trying to install the ROM
2. Reboot into TWRP, wipe data (no format needed), then install the ROM zip
3. Install anything else you would like (Magisk, OpenGAPPs, etc. OpenGAPPS beta for Android 10: https://sourceforge.net/projects/opengapps/files/arm64/beta/)
4. Reboot into system and enjoy.
Downloads
20191230-1: https://www.androidfilehost.com/?fid=4349826312261687930
20191105-1: https://www.androidfilehost.com/?fid=4349826312261619909
Source code
Device tree available at https://github.com/PeterCxy/android_device_umidigi_F1
Kernel source code is not available from UMIDIGI, unfortunately.
Screenshots (with OpenGAPPS beta)
{
"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"
}

What do you mean by "This ROM depends on the official vendor image" Do I need to flash the latest firmware from Umidigi, then flash Lineage?

Lolithetrolli said:
What do you mean by "This ROM depends on the official vendor image" Do I need to flash the latest firmware from Umidigi, then flash Lineage?
Click to expand...
Click to collapse
Actually I don't think there is much change in umidigi's firmware so you are probably fine with pretty much any vendor image. I am on the September vendor image which shows as 20190724

While I enjoy your effort for the port it's really rough around the edges. Settings randomly crash, NFC randomly crashes, there's no difference between default dark mode and black dark mode, it lacks accents other than default, after enabling developer settings numbers appear on the left hand side of the status bar, and GAPPS doesn't even have android 10 available yet. Again, thanks for the port, but it's not for me.

Lolithetrolli said:
While I enjoy your effort for the port it's really rough around the edges. Settings randomly crash, NFC randomly crashes, there's no difference between default dark mode and black dark mode, it lacks accents other than default, after enabling developer settings numbers appear on the left hand side of the status bar, and GAPPS doesn't even have android 10 available yet. Again, thanks for the port, but it's not for me.
Click to expand...
Click to collapse
Somehow I'm using it without any random crashes... Are you sure you have tested on the latest firmwares from umidigi? And are you sure you have wiped data properly? If those crashes only happen for you and not for me, then without logs it's simply impossible for me to fix anything.
And OpenGAPPS has beta version for Android 10, check it out at https://sourceforge.net/projects/opengapps/files/arm64/beta/
On the accent color thing, please wait until LineageOS 17 ports every feature over. For now having most things working is the primary focus.

Thanks for bringing a new life to an already awesome device! I was thinking on changing device due to lack of support, but now I'm surely sticking around! I have a couple of questions tho:
- Is it possible to add tweaks to this kernel? Like 2DTW, F2FS and maybe some more performance/battery gains? Or maybe upgrade it, like to 4.9?
- What about performance in games and/or more demanding tasks? I noticed this on all the GSI's that I tried, because they weren't optimized for the device, and it got hot easily.
Thanks once again for making this dream a reality! I Will test this along with your recovery when I can! Cheers!

SnapTheRipper said:
Thanks for bringing a new life to an already awesome device! I was thinking on changing device due to lack of support, but now I'm surely sticking around! I have a couple of questions tho:
- Is it possible to add tweaks to this kernel? Like 2DTW, F2FS and maybe some more performance/battery gains? Or maybe upgrade it, like to 4.9?
- What about performance in games and/or more demanding tasks? I noticed this on all the GSI's that I tried, because they weren't optimized for the device, and it got hot easily.
Thanks once again for making this dream a reality! I Will test this along with your recovery when I can! Cheers!
Click to expand...
Click to collapse
This seems to be built with stock kernel. As there is no kernel source released, the addition to kernel mods is not currently available.

mrmazak said:
This seems to be built with stock kernel. As there is no kernel source released, the addition to kernel mods is not currently available.
Click to expand...
Click to collapse
Well I found some P60 sources from Nokia, idk if it could be useful...
https://github.com/nokia-dev/android_kernel_nokia_mt6771
Amdroid Pie:
https://github.com/nokia-dev/android_kernel_nokia_mt6771/tree/android-9.0

SnapTheRipper said:
Thanks for bringing a new life to an already awesome device! I was thinking on changing device due to lack of support, but now I'm surely sticking around! I have a couple of questions tho:
- Is it possible to add tweaks to this kernel? Like 2DTW, F2FS and maybe some more performance/battery gains? Or maybe upgrade it, like to 4.9?
- What about performance in games and/or more demanding tasks? I noticed this on all the GSI's that I tried, because they weren't optimized for the device, and it got hot easily.
Thanks once again for making this dream a reality! I Will test this along with your recovery when I can! Cheers!
Click to expand...
Click to collapse
It is not technically impossible, but it would require a LOT of effort to reverse-engineer an entire kernel by piecing together open-source components from other manufacturers, and many of these vendors using MTK SoCs do not have open-source kernel just like Umidigi, though it's technically illegal to do so. I'm definitely not going to do this any time soon.

PeterCxy said:
It is not technically impossible, but it would require a LOT of effort to reverse-engineer an entire kernel by piecing together open-source components from other manufacturers, and many of these vendors using MTK SoCs do not have open-source kernel just like Umidigi, though it's technically illegal to do so. I'm definitely not going to do this any time soon.
Click to expand...
Click to collapse
Now I'm lost ? don't get me wrong, I didn't started yet to develop, but if Umidigi has an "open source" kernel, could it be decompiled somehow from the stock firmware?

SnapTheRipper said:
Now I'm lost ? don't get me wrong, I didn't started yet to develop, but if Umidigi has an "open source" kernel, could it be decompiled somehow from the stock firmware?
Click to expand...
Click to collapse
Linux being open-source doesn't mean any modification to it is easily reverse-engineerable. There is no such thing as "decompilation", only reverse-engineering, which is exactly what I referred to as "not totally impossible". However, if you hope someone to devote an enormous amount of effort just to "decompile" a kernel, you'd better off just sue the manufacturer for kernel source code (they are legally bound to do so by using the Linux kernel). It's far more plausible.

PeterCxy said:
Linux being open-source doesn't mean any modification to it is easily reverse-engineerable. There is no such thing as "decompilation", only reverse-engineering, which is exactly what I referred to as "not totally impossible". However, if you hope someone to devote an enormous amount of effort just to "decompile" a kernel, you'd better off just sue the manufacturer for kernel source code (they are legally bound to do so by using the Linux kernel). It's far more plausible.
Click to expand...
Click to collapse
Anyway
I tried the exact same steps but ended up in a splash screen loop. Any idea how to fix this (or how to grab a log of this, if needed)?

No service on two of the sim card. Phone shows carrier, but no network.
Edited: Never mind. Start from fresh umidigi system, and all good.

SnapTheRipper said:
Anyway
I tried the exact same steps but ended up in a splash screen loop. Any idea how to fix this (or how to grab a log of this, if needed)?
Click to expand...
Click to collapse
TWRP keep system read only, no more boot loop.

test on Umidigi F1 Play
I make Kernel Changes to make your rom work on umidigi f1 play and it booted but a lot of issues :
- sim card doesnt recognize in second reboot
- A lot of NFC Force closes
- Sound is deteriorated (i Think it because the besloudness in the stock rom)
- Rom has a lot of features that not working (example percentage of battery is not showed after i enable it)
this just a report of 15 minutes testing roms

It's possible to revert to stock? How?

sinergine said:
It's possible to revert to stock? How?
Click to expand...
Click to collapse
That would be easiest if you use twrp and make a backup , before flashing this. Same as with any rom, you should make backup first.
If you didn't do that, or the restore fails. Then use sp-flash tool and flash factory firmware.
Umidigi posts the firmware on there community web forum.

SnapTheRipper said:
Anyway
I tried the exact same steps but ended up in a splash screen loop. Any idea how to fix this (or how to grab a log of this, if needed)?
Click to expand...
Click to collapse
Same for me
hyibin said:
TWRP keep system read only, no more boot loop.
Click to expand...
Click to collapse
How to resolve?

sinergine said:
Same for me
How to resolve?
Click to expand...
Click to collapse
Resolved with reflash
hyibin said:
No service on two of the sim card. Phone shows carrier, but no network.
Edited: Never mind. Start from fresh umidigi system, and all good.
Click to expand...
Click to collapse
Now i've this problem.
Tried to restart all step from fresh system but no network

sinergine said:
Tried to restart all step from fresh system but no network
Click to expand...
Click to collapse
You have to put sim cards in before the initial boot. I gave up because too many bugs.