{
"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.
Related
Overclocked Kernel 2.55GHz for the HP Slate 21 (phobos)
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 kernel
* 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.
* A lot.
*
Please read the entire post before continuing. If you find a bug that is not listed in the "Known Issues/Bugs" section, please report it to me so that I may fix it.
Overclocked Kernel 2.55GHz for the HP Slate 21 (s100 & k100).
Here are some images:
{
"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"
}
Download:
https://www.androidfilehost.com/?fid=24438995911967002
Features:
This kernel features a modified bootloader (fastboot) which is designed to prevent bricks. The original bootloader is available on my Android File Host page.
Install/Flashing Instructions:
You will need the following things:
- A SD Card
- A USB Male to USB Male cable
- A computer with adb and fastboot installed
- Common sense
1. If you haven't already, see the post I made here on how to install the latest TWRP (provided by me).
1.5. Read "Known Issues/Bugs" below
2. Turn off device then reboot into recovery (Volume Up + Volume Down + Power). If you get a prompt asking you whether or not to leave /system unmodified, swipe on allow.
3. Go to Install then choose the zip (Overclocked_kernel_phobos_4.2.2_Quaesar.zip)
7. Swipe to Install
8. Reboot (DO NOT WIPE CACHE/DALVIK)
9. Profit! You now have an overclocked kernel on your HP Slate 21
If something went wrong or you need some additional help please either post/reply below or PM me.
Donations:
You can donate to me for my hard work through PayPal. My donation email is [email protected]. Any and all donations are welcome regardless of amount. Thanks for supporting me!
Direct link: https://www.paypal.me/Quaesar
Credits:
Building this was a collaborative effort. The following developers/beta testers helped me provide you with this:
Quaesar (me): Main person, started project, etc etc.
SLATE21&MOTOG: Beta testing
JonasFi: Beta testing
If you have any comments or questions, reply to this thread and I'll get to you whenever I can
PLEASE HIT THAT THANKS BUTTON!!! IT REALLY SHOWS YOU APPRECIATE MY WORK!!!!!
Peace,
Quaesar
Changelog:
- Nothing major to see here. First public release of ROM.
Known Issues/Bugs:
- None so far
FAQs:
Q: Bruhhhh, hook me up with dem sources
A: Dem sources can be found at teh GitHubs: (Link)
Q: Should I backup my stuff?
A: Do I need to answer that?
Q: On a scale of one to ten, how cool are you?
A: 11
Announcements:
- None right now, check later
Great kernel, makes the slate 21 snapier and faster. Apps open faster and no lag at all thanks
Governor
The default governor setting is interactive if i am not mistaken. Do you think its safe to set the governor to performance instead of interactive?
coco1476 said:
The default governor setting is interactive if i am not mistaken. Do you think its safe to set the governor to performance instead of interactive?
Click to expand...
Click to collapse
I definitely can, I thought I'd just leave it there for people who liked the idea of the device only sucking up power when it needed but staying on a touch basis the other time. This would effectively make it so that people who understand what type of power consumption they need (like you) could manually set the governor to performance default. But people who just like the idea of an overclock (because Clash of Clans was laggy or whatever) have an automatically scaling CPU which can match whatever they are doing with the right CPU clock speed, ensuring the device doesn't unintentionally get hotter than the end-user wanted.
I saw an app on the Play Store which allows you to automatically set CPU governor on boot (Kernel Auditor I think). If you use that you should be able to get this feature.
Let me know if you need anything else, hit that thanks button if I helped!
Peace,
Quaesar
I take it this will not work with your beta build of Android L. Just for use with the stock KitKat.
Quaesar said:
I definitely can, I thought I'd just leave it there for people who liked the idea of the device only sucking up power when it needed but staying on a touch basis the other time. This would effectively make it so that people who understand what type of power consumption they need (like you) could manually set the governor to performance default. But people who just like the idea of an overclock (because Clash of Clans was laggy or whatever) have an automatically scaling CPU which can match whatever they are doing with the right CPU clock speed, ensuring the device doesn't unintentionally get hotter than the end-user wanted.
I saw an app on the Play Store which allows you to automatically set CPU governor on boot (Kernel Auditor I think). If you use that you should be able to get this feature.
Let me know if you need anything else, hit that thanks button if I helped!
Peace,
Quaesar
Click to expand...
Click to collapse
I switch governor to performance and the slate 21 was cool enough to leave it set at performance and I saw a slight difference on snappiness :laugh:
charleypick said:
I take it this will not work with your beta build of Android L. Just for use with the stock KitKat.
Click to expand...
Click to collapse
No unfortunately, this uses the new kernel source and the current CM build runs the old kernel source. You could definitely atain bolt by flashing this overtop of CM but Wifi and BT will not work. That's the current issue I'm sorting out in my new CM build. Don't worry - when I release the new ROM it will have Overclock in it by default
Peace,
Q
Swap ram
Can we swap ram with this kernel? I downloaded kernel aditor from playstore and I saw virtual memory in the settings and i was wondering if i can swap some ram.
coco1476 said:
Can we swap ram with this kernel? I downloaded kernel aditor from playstore and I saw virtual memory in the settings and i was wondering if i can swap some ram.
Click to expand...
Click to collapse
Nope, this is because the Slate doesn't have the necessary partitions required for swap and repartitioning an Android device is another way of saying bricking it
Quaesar said:
Nope, this is because the Slate doesn't have the necessary partitions required for swap and repartitioning an Android device is another way of saying bricking it
Click to expand...
Click to collapse
Thanks for letting know :good:
Hey Quaesar, hope you can help me out!
I'm running your CM12.1 and TWRP 3.0 on my Slate K100.
Downloaded this kernel to my SD, checked md5sum and swiped away in recovery following all the instructions.
Rebooted and see your new flashy boot logo but then after some minute I quickly see the text "Entering RCK based on booting mode configuration" and then it just reboots into recovery again...
I have tried to re-download, re-flash, even tried whiping cache/dalvic (just to test) but still the same boot loop.
Guess I could always re-download the rom and start over, but do you have any idea on why my Slate won't boot with this kernel??
It would be so awesome to get it up to 2.55Ghz.
Henkeman0 said:
Hey Quaesar, hope you can help me out!
I'm running your CM12.1 and TWRP 3.0 on my Slate K100.
Downloaded this kernel to my SD, checked md5sum and swiped away in recovery following all the instructions.
Rebooted and see your new flashy boot logo but then after some minute I quickly see the text "Entering RCK based on booting mode configuration" and then it just reboots into recovery again...
I have tried to re-download, re-flash, even tried whiping cache/dalvic (just to test) but still the same boot loop.
Guess I could always re-download the rom and start over, but do you have any idea on why my Slate won't boot with this kernel??
It would be so awesome to get it up to 2.55Ghz.
Click to expand...
Click to collapse
Heeeey... Wait a miute, I think I messed up. This kernel is for KitKat and your CM12.1 is Lollipop, right? Haha.. Ooops!
Sorry, I will re-download the rom and start over again My bad!
Henkeman0 said:
Heeeey... Wait a miute, I think I messed up. This kernel is for KitKat and your CM12.1 is Lollipop, right? Haha.. Ooops!
Sorry, I will re-download the rom and start over again My bad!
Click to expand...
Click to collapse
Yes you are right, and I think this OC kernel is implemented with cm12.1 so you wont have to flash this kernel after installing cm12.1 its built in
Henkeman0 said:
Heeeey... Wait a miute, I think I messed up. This kernel is for KitKat and your CM12.1 is Lollipop, right? Haha.. Ooops!
Sorry, I will re-download the rom and start over again My bad!
Click to expand...
Click to collapse
Yup haha, this kernel mod is only for stock, once I finish fixing the issues with the new kernel and CM12.1, the new build will automatically be overclocked
coco1476 said:
Yes you are right, and I think this OC kernel is implemented with cm12.1 so you wont have to flash this kernel after installing cm12.1 its built in
Click to expand...
Click to collapse
You got it!
Peace,
Q
No boot
I've tried to install the OC kernel, but when the system reboots I can only see the boot screen (twice) but then the screen goes black (with backlight on). Tried to reinstall, but same result. Any suggestion, please?
does it fix only 1 core bug?
xfabio said:
I've tried to install the OC kernel, but when the system reboots I can only see the boot screen (twice) but then the screen goes black (with backlight on). Tried to reinstall, but same result. Any suggestion, please?
Click to expand...
Click to collapse
Are you sure you're on KitKat? Jelly Bean has that issue I know.
@evildog1, nope ((((( For some weird reason it doesn't want to use all cores
Quaesar said:
Are you sure you're on KitKat? Jelly Bean has that issue I know.
@evildog1, nope ((((( For some weird reason it doesn't want to use all cores
Click to expand...
Click to collapse
Hmm it should be possible to tweak the cores in the kernel but there is no infomation about it on the internet. Have you disabled some battery saving in the kernel that are not neccesary?
I have seen an option to disable 'sleep' (i forgot the excat name) in Kernel Auditor. I disabled it but it doesn't help.
My tablet starts to lag again after we used it for a month. I guess it is the I/O problem and it can be tweaked in kernel.
The annoying bug is the tablet freezes in 1 sec when i press back button to quit an app. I can try to grab the logcat when i'm home
This recovery will work ONLY for the Snapdragon 615 version of Oppo R7 Plus!
Here is an update to my UNOFFICIAL TWRP 3.0.2
Everything works well, with one caveat: It will reboot as soon as the display times out. The workaround is simple: Go to settings and disable Screen Timeout.
The -C revision is just to remind me that the recovery it is build on CyanogenMod.
If you don't need encryption and don't care about wrong date/time in your backups, then the official twrp will be all you need.
{
"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"
}
Full Source: Github.Old stuff:
My goal with this UNOFFICIAL twrp recovery is to enable encryption on Oppo R7Plus-f(Snapdragon) version.
Tested with AICP on MarshMallow. Full encryption support.
All hard work was done by the TWRP Team and the R7 kernel gurus at CyanogenMod.
I just made a few additions and changed the official TWRP kernel to the CM kernel using the AICP build system.
To get your Oppo R7Plusf encrypted, there are a few points you must follow.
Note1: This wil not work with ColorOS. The ROM must support encryption. ColorOS does not!
Note2: You will LOOSE ALL DATA if you choose to encrypt your R7Plusf.
Here is a small howto:
1. Boot to bootloader and flash TWRP-3.0.2.u
2. Boot to recovery
3. Choose A or B to backup your data
....A: Backup Data and copy it to PC (Internal Storage - TWRP/BACKUPS/xxxxxxxx/BackupName)
....B: Backup Data to the Micro SDcard (Now, be careful not to format the Micro SD)
4. Wipe -> Format Data (type YES and tap the OK/Enter button)
....This command is slow, have patience!
5. Reboot to android. The install wizard should show - be sure to create a PIN or Pattern kode during the setup.
6. Charge the phone to 90-100%
7. Open Settings/Security and -> Encrypt phone
8. Follow instructions
Click to expand...
Click to collapse
Now the device will reboot a few times and finally it will boot to the login screen and ask for your pin code.
All this will take time, have patience.
On my AICP ROM it sometimes "hang" when Finishing boot and make some tick sounds. Turning the screen off and on a few times will make it boot to the login and you can enter the PIN or Pattern. It will boot again and quickly get into your Android system.
Once booted to Android, everything is smooth and there are no more issues (at least not encryption related )
This is an issue with my AICP ROM only, CM13 start without issues.
...reserved...
Please share your experience here, if you choose to check out encryption on the R7+. Thanks.
Major Props ! Great job and you actually fulfilled a request of mine ! Thanks
I have followed the steps and @ step 5 I wasnt asked to enter any PIN , Im on CM13 latest nighly on october 31 and twrp 3.0.2 , any advise Please ?
is the backup step A or B optional or a must ?
midterm_2003 said:
I have followed the steps and @ step 5 I wasnt asked to enter any PIN , Im on CM13 latest nighly on october 31 and twrp 3.0.2 , any advise Please ?
is the backup step A or B optional or a must ?
Click to expand...
Click to collapse
It is 6 months since I tried. At that time I was asked for the pin. Don't know if that is different for the latest cm.
Note that this recovery is not perfect. It handles encryption well, but has a few issues. To avoid these, you can flash the official twrp from http://twrp.me, but don't format data - it will break encryption.
Maybe CyanogenMod recovery is fully functional now, then it might be a better choice. @maniac103 ?
Yes backup is optional. It is always your choice.
It was my mistake I selected wipe instead of format , it works now ! :good: do you know what other issues this recovery have as I want to keep
Thanks
Small update - read OP.
teemo said:
Small update - read OP.
Click to expand...
Click to collapse
I have recently done a complete new TWRP from scratch including:
- LineageOS kernel 3.10.104
- decryption using 7.1.1 LineageOS blobs
- included misc for 7.1.1
- overlay graphics support
- modem binary flashing support (no zip file required) just select non-hlos.bin from Oppo's stock ROM
- proper IMEI Partition Backup
- flashimage support in TWRP (just like fastboot)
- latest TWRP 3.0.3-0
If you would like to build one or want me to provide you a build let me know.
I pushed the repo here: https://github.com/Celoxocis/android_device_oppo_r7plusf
Of course I made it for the R7S but our two devices are almost identical so I made the necessary changes to create a R7Plus repo.
Let me know what you think.
celoxocis said:
I have recently done a complete new TWRP from scratch including:
- LineageOS kernel 3.10.104
- decryption using 7.1.1 LineageOS blobs
- included misc for 7.1.1
- overlay graphics support
- modem binary flashing support (no zip file required) just select non-hlos.bin from Oppo's stock ROM
- proper IMEI Partition Backup
- flashimage support in TWRP (just like fastboot)
- latest TWRP 3.0.3-0
If you would like to build one or want me to provide you a build let me know.
I pushed the repo here: https://github.com/Celoxocis/android_device_oppo_r7plusf
Of course I made it for the R7S but our two devices are almost identical so I made the necessary changes to create a R7Plus repo.
Let me know what you think.
Click to expand...
Click to collapse
That is simply brilliant
I just started syncing down LineageOS from scratch again. You say decryption is from LOS 14.1, but I assume you build twrp on cm-13.0.
Overlay: I have always been puzzled over the slow graphics on twrp. My old 2012 HTC is super smooth in the same recovery. I saw you discuss it somewhere, maybe on IRC you mentioned one drawback by running on overlay, but don't remember what it was ?
Modem flashing: That will be handy for testing stuff.
Proper IMEI, wasn't aware it was broken?
Flash image, another great feature, although easily done from Android as well. I have been a few times in recovery, wanting to just flash an image.
Big thanks for taking time to update plusf. I will check it out and return
EDIT: Built with following changes:
- All CyanogenMod repos changed to LineageOS in localmanifest
- kernel and dt replaced with my latest, as the supplied boots into fastboot
Will test the next few days.
Huge thanks @celoxocis
teemo said:
That is simply brilliant
I just started syncing down LineageOS from scratch again. You say decryption is from LOS 14.1, but I assume you build twrp on cm-13.0.
Overlay: I have always been puzzled over the slow graphics on twrp. My old 2012 HTC is super smooth in the same recovery. I saw you discuss it somewhere, maybe on IRC you mentioned one drawback by running on overlay, but don't remember what it was ?
Modem flashing: That will be handy for testing stuff.
Proper IMEI, wasn't aware it was broken?
Flash image, another great feature, although easily done from Android as well. I have been a few times in recovery, wanting to just flash an image.
Big thanks for taking time to update plusf. I will check it out and return
EDIT: Built with following changes:
- All CyanogenMod repos changed to LineageOS in localmanifest
- kernel and dt replaced with my latest, as the supplied boots into fastboot
Will test the next few days.
Huge thanks @celoxocis
Click to expand...
Click to collapse
Just the build tree is cm-13.0 but as you can see from the manifest everything that is required is from TWRP's Android 7.1. I.
I didn't want to test the build on an bleeding edge LineageOS 14.1 tree. As I wasn't sure about if it works and repo syncing the sources takes time.
Funny they boot into fastboot?
Kernel + DT.IMG were LineageOS 14.1 (7.1.1).
To my knowledge the kernel + DT.img are identical for the R7Plus,/R7S. The DT.img contains 15022 + 15018 as far as I know.
The only downside when using graphics overlay was that some users reported screenshot In recovery would not work. While I had one user report it works.
celoxocis said:
Just the build tree is cm-13.0 but as you can see from the manifest everything that is required is from TWRP's Android 7.1. I.
I didn't want to test the build on an bleeding edge LineageOS 14.1 tree. As I wasn't sure about if it works and repo syncing the sources takes time.
Funny they boot into fastboot?
Kernel + DT.IMG were LineageOS 14.1 (7.1.1).
To my knowledge the kernel + DT.img are identical for the R7Plus,/R7S. The DT.img contains 15022 + 15018 as far as I know.
The only downside when using graphics overlay was that some users reported screenshot In recovery would not work. While I had one user report it works.
Click to expand...
Click to collapse
Actually it didn't boot into the bootloader (fastboot screen), it was stuck on the Oppo screen. Did not respond to adb, but gave correct answer from 'fastboot devices'. Didn't check other fastboot commands though.
Screenshots works well
teemo said:
Actually it didn't boot into the bootloader (fastboot screen), it was stuck on the Oppo screen. Did not respond to adb, but gave correct answer from 'fastboot devices'. Didn't check other fastboot commands though.
Screenshots works well
Click to expand...
Click to collapse
I feel video overlay graphics in twrp recovery feels smoother than adf graphics.
Unfortunately I can't compare them side by side.
What do you think which feels smoother?
celoxocis said:
I feel video overlay graphics in twrp recovery feels smoother than adf graphics.
Unfortunately I can't compare them side by side.
What do you think which feels smoother?
Click to expand...
Click to collapse
For the filemanager, I feel it is a little smoother than before. Might be my imagination though.
It is very picky about how you scroll with your finger, sometimes mistaking it for a "tap". But old adf did the same.
I can say definitely, that the slider is much much better now. Not supersmooth as my HTC, but good enough for a recovery tool. Don't see any downsides yet.
EDIT: Funny, the slider animation is the same as on my 3.0.2-C. I made a video and compared. It's the same. I may have seen the slower animations on an older recovery, I am sure it was much more choppy before.
Is there any chance that this would be updated.?
kishd said:
Is there any chance that this would be updated.?
Click to expand...
Click to collapse
Yes I will update it. Just don't know when yet.
It's a long weekend here. So I might do it tomorrow.
I will post once updated.
x
Help please...I'm stucked at the unlock bootloader...
First to say I have root but I got root only with kingroot app...is this a problem?
I have installed the color os r7plusfEX_11_151225 (didn't do full wype data, installed over the latest color os version), but with the oppo tools it didn't do nothing so I got root with kingroot.
I can go into fastboot but when I type "fastboot oem unlock" it always say this:
"C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot oem unlock
...
FAILED (remote: oem unlock is not allowed)
finished. total time: 0.053s"
where I was wrong or where I miss something?
thanks for replies I really will to intall a custom rom on this phone........
celoxocis said:
Yes I will update it. Just don't know when yet.
It's a long weekend here. So I might do it tomorrow.
I will post once updated.
Click to expand...
Click to collapse
I hate to be a nuisance, but have you had a chance to look at this?
kishd said:
I hate to be a nuisance, but have you had a chance to look at this?
Click to expand...
Click to collapse
Yes i decided not to bring another unofficial release.
There will be an update for TWRP for the entire R7 series.
It will be made official soon.
{
"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"
}
Here's something for you guys to play around with,
the thread will be beautified and completed later.
Now the bare minimum has to suffice
this ROM includes a Wakelock Blocker and a Doze Powersave called feature to make sure your device really sleeps well
So: no Greenify, Amplify, PowerNap, etc. are needed.
From my observation the idle battery consumption is somewhat higher compared to AOSP and CM13 - but still pretty low
In addition it has several goodies from quite a lot other ROMs
Downloads
List of all Releases:
CyanogenMod based Custom ROMs -> Resurrection Remix
Latest recommended CyanogenMod release for the Sony Xperia Z5 E6853/E6803 :
ResurrectionRemix-M-v5.7.0-20160628-satsuki
Latest recommended Kernel for the CM release for the Sony Xperia Z5 E6653/E6603 :
SunKernel II.1_2 for ResurrectionRemix-M-v5.6.7-20160426 for the Z5P
Details
For Instructions on how to install, etc.
Please take a look at the CyanogenMod 13 Thread (same ROM base):
http://forum.xda-developers.com/z5-premium/development/rom-cyanogenmod-13-sony-xperia-z5-t3407396
Source Code:
https://github.com/Sony-Kitakami
https://github.com/SonyAosp
https://github.com/sonyxperiadev
https://github.com/CyanogenMod
https://github.com/ResurrectionRemix/
https://github.com/zachariasmaladroit/android_kernel_sony_msm8994_kitakami_r2
ROM OS Version: 6.0.x Marshmallow
ROM Firmware Required: 6.0 Recommended
Based On: CyanogenMod
Version Information
Status: Alpha
Created 2016-04-26
Last Updated 2016-06-29
Reserved 01 (ROM)
Reserved 02 (Custom Kernel)
Kernel Changelog/Features (II.1_2) said:
upstream sonyxperiadev sync - mmc (deferred resume) fixes
upstream sonyxperiadev sync - added proper support for replacement display panels
exfat driver
thermal and hotplug fixes
LED notification indicator changes color when battery is really full (thanks to @Tommy-Geenexus )
hardware wakelock switches (modem, wifi, bluetooth)
switch for GENTLE_FAIR_SLEEPERS
backlight calculation improvement
fixes for compiler-caused issues & instabilities
vmalloc improvements (less memory fragmentation, more reliability in the long-term)
vmscan improvements (better reliability when swap/zram is disabled; less thrashing)
cfq-iosched fixes
re-enabled deadline, row i/o scheduler
frandom
LPM (low power mode) fixes & improvements
mmc (internal storage, microSD) reliability and performance fixes & improvements
KSM more efficient scanning and packing [KSM defaults to off, it's a battery drainer]
scheduler: load balancing improvement
cpuidle fixes & improvements
reducing high load average to minimum - less/minimal idle battery drain
a few general fixes (thermal, i2c-msm-v2 [unnecessary error message upon startup/deferral], usb: f_fs, fingerprint scanner)
more governors: elementalX, ZZMove, alucard ( thanks to @AndroPlus )
backported SIM_DETECT & TRAY_SHARED_INTERRUPT_DETECT, MMC_SUPPORT_SVS_INTERVAL from Sony's copyleft kernel; possible preparation for DSDS/DSDA mode)
Click to expand...
Click to collapse
and last one
(Installation)
Q: Can i flash it without losing my actual data ?
A: If you use both zip files (ROM + kernel),
then yes, your data should be safe.
But still backup your data - you never know if it doesn't go crazy
Once you've backed up your data, done a Backup via TWRP - copy the backup of TWRP (in TWRP folder) to your PC
to be really sure
then format (advanced wipe)
/data, /system/, /cache, dalvik cache
and flash the ROM zip + kernel zip + GApps (e.g. Slim GApps)
After that you're good to go
Q: What is the correct order to install it ? Different Kernel + TWRP, then ROM and later your kernel ?
A: You're using TWRP, right ?
Not sure if there's a different TWRP available for the Z5P - but if yes,
you can keep TWRP (and don't need to flash a new recovery).
Copy ROM + Kernel + GApps to internal storage,
reboot - press vol up button to get into TWRP/recovery,
Backup your System,
Reboot and Copy the TWRP folder and ALL your important data to your PC/Mac/...
Reboot again into Recovery/TWRP,
do an advanced wipe (/cache, /data, /system, dalvik cache),
flash ROM, Kernel, GApps,
Reboot -> System
That should be all
Damn cant wait to try this
Okay
Boots up with latest kernel package. :good:
Patiently waiting
Thanks for the heads up
how about E6883
6853 cant see it?
I must be blind because i cant see the rom for 6853 keen waiting for a asop based rom
zacharias.maladroit said:
Reserved 01 (ROM)
Click to expand...
Click to collapse
He does not start , it is loaded into the logo of resurrection remix ... and I've had more than 15 minutes.
pandan80 said:
how about E6883
Click to expand...
Click to collapse
Well, constantly asking won't magically accelerate it
We're working on it, also did some testing,
but the best for now (afaik) was that one SIM card worked and microSD disappeared.
dominicstg2 said:
I must be blind because i cant see the rom for 6853 keen waiting for a asop based rom
Click to expand...
Click to collapse
6853 is satsuki,
can you post the links you're using ?
Or what issue are you running into ?
Custom Kernel is updated,
please flash it along with the ROM since stock kernel doesn't seem to work (might be due to selinux issues or others, dunno - don't have enough time and also don't feel like tracking it down right now,
there are more important priorities in my life currently)
Thanks
Rubensss said:
He does not start , it is loaded into the logo of resurrection remix ... and I've had more than 15 minutes.
Click to expand...
Click to collapse
Rubensss, you flashed the custom kernel, too ?
How did you flash it ?
edit:
you noticed that there's a new custom kernel up, right ?
@moonbutt74 just flashed it - and it appears to work fine
Okay
Boots up with latest kernel package. :good:
m
zacharias.maladroit said:
Rubensss, you flashed the custom kernel, too ?
How did you flash it ?
edit:
you noticed that there's a new custom kernel up, right ?
@moonbutt74 just flashed it - and it appears to work fine
Click to expand...
Click to collapse
I installed it as follows , please tell me where I was wrong .. I installed the kernel and recovery of moonbut74 , after flashee the rom and gapps and rebooted . your kernel you have to install before flashing the ROM and gapps ? or install your kernel and then the recovery of moonbut74 ? zacharias.maladroid thanks for your help
Rubensss said:
I installed it as follows , please tell me where I was wrong .. I installed the kernel and recovery of moonbut74 , after flashee the rom and gapps and rebooted . your kernel you have to install before flashing the ROM and gapps ? or install your kernel and then the recovery of moonbut74 ? zacharias.maladroid thanks for your help
Click to expand...
Click to collapse
Hm, so moonbutt74's recovery means TWRP ?
Not sure if there's a different TWRP available - but if yes,
you can keep TWRP (and don't need to flash a new recovery).
Copy ROM + Kernel + GApps to internal storage,
reboot - press vol up button to get into TWRP/recovery,
Backup your System,
Reboot and Copy the TWRP folder and ALL your important data to your PC/Mac/...
Reboot again into Recovery/TWRP,
do an advanced wipe (/cache, /data, /system, dalvik cache),
flash ROM, Kernel, GApps,
Reboot -> System
That should be all
was looking at the wrong links
zacharias.maladroit said:
Well, constantly asking won't magically accelerate it
We're working on it, also did some testing,
but the best for now (afaik) was that one SIM card worked and microSD disappeared.
6853 is satsuki,
can you post the links you're using ?
Or what issue are you running into ?
Custom Kernel is updated,
please flash it along with the ROM since stock kernel doesn't seem to work (might be due to selinux issues or others, dunno - don't have enough time and also don't feel like tracking it down right now,
there are more important priorities in my life currently)
Thanks
Click to expand...
Click to collapse
Waiting for DSDS version even single sim only is working.
zacharias.maladroit said:
Hm, so moonbutt74's recovery means TWRP ?
Not sure if there's a different TWRP available - but if yes,
you can keep TWRP (and don't need to flash a new recovery).
Copy ROM + Kernel + GApps to internal storage,
reboot - press vol up button to get into TWRP/recovery,
Backup your System,
Reboot and Copy the TWRP folder and ALL your important data to your PC/Mac/...
Reboot again into Recovery/TWRP,
do an advanced wipe (/cache, /data, /system, dalvik cache),
flash ROM, Kernel, GApps,
Reboot -> System
That should be all
Click to expand...
Click to collapse
Thanks installed. I have to say that to be the first version works very well, the speakers sound a bit loose but with impressive quality . As you publish a stable version will install for my daily use , I really like resurrection remix . Thank you very much for your work Zacharias.maladroid
Solid build
Continuing off the other CM build this build is also rather solid.
Once you get the camera working correctly as well as figuring out the Bluetooth issues ill have a new daily driver for sure
Living without my camera / Bluetooth isn't a option for me though haha.
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.
{
"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 affiliated with the official Evolution-X ROM developers
Updated for October 2022
Signed with my own keys
some features you may be used to from this ROM are not available (yet), I'm assuming it just takes time for the developers to add them to the still relatively new Android 13/tiramisu. If I have time, I'll see what I can do.If something is missing, it's not due to me excluding anything.
The Camera and Bluetooth are working fine now, I noticed in my last version I posted here last week for 220905 they were broken.
Kernel Source
Device, Kernel and Vendor Repos
Downloads
Instructions:
Flash the vendor_boot and boot
Sideload the ota in recovery
thank you
Can I flash from android 12?
Kings Android said:
Can I flash from android 12?
Click to expand...
Click to collapse
I think so but I was on stock Google 13 when I did mine.
Kings Android said:
Can I flash from android 12?
Click to expand...
Click to collapse
I was able to flash from the Android 12 image without issue.
The only thing I'm trying to figure out now is what's draining my battery. I've re-flashed clean this morning so I'm monitoring the battery usage to see what is consuming battery while idle.
twykomantis said:
I was able to flash from the Android 12 image without issue.
The only thing I'm trying to figure out now is what's draining my battery. I've re-flashed clean this morning so I'm monitoring the battery usage to see what is consuming battery while idle.
Click to expand...
Click to collapse
I personally haven't noticed a large drain in battery while idle on a13 evo-x but I did have that problem before I updated directly from 12. I put com.android.hbmsvmanager on restricted battery usage and it solved the problem. Maybe this will help on 13??
HI aleph.mercury,
on my P5 i flashed your ROM but WiFi / WLAN and mobile Data won't work.
Before I was on Stock Android 13 October 2022 Build, flashed the both boot images with slot all, I did an factory reset and then I installed the ROM and afterwards Wifi and mobile Data won't work.
Do you have any ideas how to solve this?
regards
EDIT: got it fixed, reflashed all the other stock partitions via flash.bat
Raz0Rfail said:
HI aleph.mercury,
on my P5 i flashed your ROM but WiFi / WLAN and mobile Data won't work.
Before I was on Stock Android 13 October 2022 Build, flashed the both boot images with slot all, I did an factory reset and then I installed the ROM and afterwards Wifi and mobile Data won't work.
Do you have any ideas how to solve this?
regards
Click to expand...
Click to collapse
Did you flash vendor_boot image with correct command?
Yep:
fastboot.exe flash boot boot.img --slot all
fastboot.exe flash vendor_boot vendor_boot.img --slot all
But I fixed it and thanks for the fast response .
just a heads-up any AT&T users will need flash this via magisk to get calling to work. This is also true with evo-x a12 rom for pixel 5. https://forum.xda-developers.com/t/mod-magisk-root-volte-enabler.4372705/
Rookie Question: how and when do I factory reset while installing this rom? I have never flashed a rom this way before and I want to make sure I do it right.
elong7681 said:
Rookie Question: how and when do I factory reset while installing this rom? I have never flashed a rom this way before and I want to make sure I do it right.
Click to expand...
Click to collapse
After flashing the boot.img and vendor_boot.img files you enter recovery and there is an option factory reset. Once you've done this you must reboot to recovery and adb sideload the rom and that's it. Make sure you keep an eye when installing the rom. I think around 47% it will ask you if you wish to continue with the flash on your phone screen. Tap yes and then it will flash the rest of the way. After this just reboot system and go through the rom setup like it's a brand new phone and welcome to Evo-x 13
TMI I'm sure but just thought I'd take you through it as best I can
DroidRommer said:
After flashing the boot.img and vendor_boot.img files you enter recovery and there is an option factory reset. Once you've done this you must reboot to recovery and adb sideload the rom and that's it. Make sure you keep an eye when installing the rom. I think around 47% it will ask you if you wish to continue with the flash on your phone screen. Tap yes and then it will flash the rest of the way. After this just reboot system and go through the rom setup like it's a brand new phone and welcome to Evo-x 13
TMI I'm sure but just thought I'd take you through it as best I can
Click to expand...
Click to collapse
Thanks for the response
To anyone noticing idle battery drain I stumbled across a magisk module called AOSP Enhancer it's supposed to tweak the kernal to be more AOSP friendly and definitely helps the battery in my opinion!
Just flash in magisk and reboot. Once booted you can open your file explorer app and navigate to / storage/emulated/0/Android. Here you will see aosp_enhancer.txt if you open this you will see something like the pic I posted
your phone may get kind of warm for about 10 or 15 mins while the module makes the tweaks but after that it will run like normal and hopefully you'll be thanking me. but for real I took my pixel off charge at 10am this morning and I'm still at 72% 13 hours later!
If this doesn't work for you pls let me know!
Thanks
DroidRommer said:
To anyone noticing idle battery drain I stumbled across a magisk module called AOSP Enhancer it's supposed to tweak the kernal to be more AOSP friendly and definitely helps the battery in my opinion!
Just flash in magisk and reboot. Once booted you can open your file explorer app and navigate to / storage/emulated/0/Android. Here you will see aosp_enhancer.txt if you open this you will see something like the pic I posted
your phone may get kind of warm for about 10 or 15 mins while the module makes the tweaks but after that it will run like normal and hopefully you'll be thanking me. but for real I took my pixel off charge at 10am this morning and I'm still at 72% 13 hours later!
If this doesn't work for you pls let me know!
Thanks
Click to expand...
Click to collapse
Did you stumble onto safetynet passing issues using magisk with evox13 ? Just checking before I load magisk onto mine
Crazyaboutroms said:
Did you stumble onto safetynet passing issues using magisk with evox13 ? Just checking before I load magisk onto mine
Click to expand...
Click to collapse
As long as you flash the latest safety net fix module in magisk you'll be fine
DroidRommer said:
just a heads-up any AT&T users will need flash this via magisk to get calling to work. This is also true with evo-x a12 rom for pixel 5. https://forum.xda-developers.com/t/mod-magisk-root-volte-enabler.4372705/
Click to expand...
Click to collapse
I added the items found in this magisk module's system.prop to this ROM, it should automatically be there in the November update. You won't have to be rooted or use magisk next time
I'm on Verizon and was missing WiFi calling as well without the module
Crazyaboutroms said:
Did you stumble onto safetynet passing issues using magisk with evox13 ? Just checking before I load magisk onto mine
Click to expand...
Click to collapse
this ROM should pass safety net rooted or not.
if you are rooted, it's possible to ruin this status by remounting the system partition RW while trying to build and install custom WiFi kernel modules on the phone in a live environment. if you do something like that, you can still pass safety net again if you use the magisk module by kdrag0n and/or the props module by didgeridoohan.
aleph.mercury said:
I added the items found in this magisk module's system.prop to this ROM, it should automatically be there in the November update. You won't have to be rooted or use magisk next time
I'm on Verizon and was missing WiFi calling as well without the module
this ROM should pass safety net rooted or not.
if you are rooted, it's possible to ruin this status by remounting the system partition RW while trying to build and install custom WiFi kernel modules on the phone in a live environment. if you do something like that, you can still pass safety net again if you use the magisk module by kdrag0n and/or the props module by didgeridoohan.
Click to expand...
Click to collapse
Thank you for this! I really appreciate you integrating that module for calling. Sorry I had no idea about the safety net thing Its pretty much just habit for me to flash the module in magisk at this point lol. Just cuz you mentioned kernels is there any chance there will be anymore cpu governors added in the future such as interactivex or anything like it? I like tweaking everything lol
I think if you want to tweak kernel parameters there's already apps that can do that; is there's kernel features you want available (such as wireguard kernel module (which I already added), a specific WiFi driver, Bluetooth feature, HID) I think I can make those available.
if you download my kernel repo on your PC (or any LINUX kernel for that matter), then navigate to it (cd kernel/Google/redbull) then type "make menuconfig" in the CLI, a GUI will show you all the available kernel settings. load the following arch/arm64/configs/redbull_defconfig from within the GUI, make changes and save. You can add the kernel to your boot.img , check out my first thread for this ROM from July/August for detailed instructions on how to use the Android boot image editor on how to replace the kernel using that technique
aleph.mercury said:
I think if you want to tweak kernel parameters there's already apps that can do that; is there's kernel features you want available (such as wireguard kernel module (which I already added), a specific WiFi driver, Bluetooth feature, HID) I think I can make those available.
if you download my kernel repo on your PC (or any LINUX kernel for that matter), then navigate to it (cd kernel/Google/redbull) then type "make menuconfig" in the CLI, a GUI will show you all the available kernel settings. load the following arch/arm64/configs/redbull_defconfig from within the GUI, make changes and save. then build the kernel. You can add the kernel to your boot.img , check out my first thread for this ROM from July/August for detailed instructions on how to use the Android boot image editor on how to replace the kernel using that technique
Click to expand...
Click to collapse