LineageOS 16.0 for Xiaomi Mi 5 with 4.4 kernel
Remember this is a beta release, althought I've been using it for more than a week and it's working perfectly.
If you experience any bugs, panics or so, please report full logs to me (logcat and dmesg, you can look in /sys/fs/pstore)
Installation:
You can flash it on top of OFFICIAL 3.18 LOS also you can always go back within a dirty flash.
For safety reasons always perform a backup of your important data!
Features:
This is well-known LOS, none of the functionalities have been altered.
Build is running 4.4.189 kernel with many improvements over 3.18, it will keep this device alive for upcoming Android releases.
Kernel is suited with initial bug fixes, however, it's a stock kernel without any advanced tweaks. It's built with CLANG (!).
Working:
Probably everything!
Not working:
Kernel is permissive
Temporary MTP fix (I didn't have enough time to investigate it well):
Developer settings -> Default USB conf -> MTP -> connect cable -> profit
READ ONLY IF YOUR DEVICE IS ENCRYPTED:
There is an incompatibility between 3.18 and 4.4 kernels, you have to flash new TWRP with 4.4 kernel, otherwise your data partition will be DAMAGED!
Nevertheless there could be a need to full wipe your /data (magic Format Data button in TWRP) so perform a FULL BACKUP.
Download:
LineageOS zip
TWRP
Future development:
Device tree will be created from scratch over new Qualcomm tag to get rid of old junk. Full Treble compability will be provided.
More kernel bug fixes
Vendor update
FAQ:
Can I install XXX ? Does it support XXX ?
- It's still LOS, it supports everything what stock LOS does.
Can't you ship kernel package only?
- No, ROM has to be modified to meet 4.4 requriements. You can't flash 4.4 kernel on top of 3.18 ROM.
But why 4.4? Do I need it?
- More fixes, more performance, more support. If you want, search for kernel changelog.
EAS?
- Not now, there are more important things to work on.
If you want to buy me a coffee, please consider donating, I've put much effort to make it working.
DONATE
Join Mi5 group on Telegram
Huge thanks to Zuk kernel team for initial 4.4 support!
Credits:
@DD3Boh
@YaroST12
@kenny3fcb
@Luk1337 - fix for USB
@Jawor245 - random stuff
@RadixCube
XDA:DevDB Information
LineageOS 16.0 with 4.4 kernel, ROM for the Xiaomi Mi 5
Contributors
xNombre
Source Code: https://github.com/xNombre/msm-4.4
ROM OS Version: 9.x Pie
ROM Kernel: Linux 4.x
Version Information
Status: Beta
Created 2019-09-01
Last Updated 2019-09-01
Reserved
Reserved
In Antutu 7.2.3 tested fresh, stock LOS + nano gapps and fresh this rom + nano gapps on my 32Gb version. Biggest improvement for my device is memory +22% in Antutu points.
Stock: 144 086 overall
CPU: 50 420
GPU: 53 892
UX: 34 159
MEM: 5 615
4.4 LOS: 148 079 overall
CPU: 50 600
GPU: 54 615
UX: 35 657
MEM: 7 207
@xNombre great job!
I'll be testing your ROM in the future for sure. Looks very promising.
It would be great if you pulled the Floppy Kernel mods to tweak your 4.4 kernel
(Just my wish)
However, congratulations man.
I really appreciate your effort I would love to test your ROM But I only want to know 2 things before if someone can help.
1. Can I use it as daily driver?
2. Android Auto is working?
3. Will I need to do clean flash for future updates? Atleast for couple weeks.
Thanks
I'm using it for two weeks and no problems here.
If Android Auto is working on official LOS it will for for mine, too.
Nope, not for now.
#edit
Here is the new kernel you can flash on top of my LOS. (DON'T FLASH IT ON ANYTHING ELSE)
https://androidfilehost.com/?fid=1899786940962575411
Changelog:
add exFAT and NTFS
fix problems with wakelocks
use LZ4 for ZRAM
debloat a bit
skip sync for better battery
@xNombre What is the reason behind choosing 4.4 instead of a newer LTS version like 4.9 or 4.14? Or was the decision out of your hands?
Damn, do you think it's easy to port it on 4.14? For small group of users? Totally for free?
Two devices were fried with 4.9 kernel test version and in result I've spent many many hours of work for nothing.
Och, and remember, I had to buy a new mobo to restore my dd.
msm8996 has official support of 4.4 kernel and that's enough. I won't go any further, even if it's possible.
xNombre said:
Damn, do you think it's easy to port it on 4.14? For small group of users? Totally for free?
Two devices were fried with 4.9 kernel test version and in result I've spent many many hours of work for nothing.
Och, and remember, I had to buy a new mobo to restore my dd.
msm8996 has official support of 4.4 kernel and that's enough. I won't go any further, even if it's possible.
Click to expand...
Click to collapse
Whoa, calm down, mate. I just wanted to know the rationale. Knowing that msm8996 supports 4.4 is good enough for me. :good:
Sorry to hear about the two damaged devices, though. That must have been extremely frustrating.
xNombre said:
Damn, do you think it's easy to port it on 4.14? For small group of users? Totally for free?
Two devices were fried with 4.9 kernel test version and in result I've spent many many hours of work for nothing.
Och, and remember, I had to buy a new mobo to restore my dd.
msm8996 has official support of 4.4 kernel and that's enough. I won't go any further, even if it's possible.
Click to expand...
Click to collapse
Lots of love for 4.4 kernel.
Hello
Thanks for this amazing work.
I have a question (probably stupid) will voWifi work better than with a 3.18 kernel or there is no relationship between kernel and voWifi?
Thank you for your work. This is quite big actually.
Thx
Myxomatom said:
Hello
Thanks for this amazing work.
I have a question (probably stupid) will voWifi work better than with a 3.18 kernel or there is no relationship between kernel and voWifi?
Click to expand...
Click to collapse
There it no correlation between kernel and RIL. No changes here. Maaybe sth nice will happen with new vendor blobs but you have to wait for it.
great job, it heats a lot less than the miui .. today it's only the first day but it seems to me that the battery lasts much longer !!
bido1 said:
great job, it heats a lot less than the miui .. today it's only the first day but it seems to me that the battery lasts much longer !!
Click to expand...
Click to collapse
yeah ... been using it for the last 3 days ... the battery performance is better than the official one without any tweak
can't flash it under lineage-16.0-20190809-nightly-gemini-signed.zip. error code: 7. any clue why?
netrixken said:
can't flash it under lineage-16.0-20190809-nightly-gemini-signed.zip. error code: 7. any clue why?
Click to expand...
Click to collapse
Are you using TWRP provided in first post?
Related
July 18: New build is up. This is LP 5.1.1 r.8
Latest PA changes
FM radio incorporated
Slim Launcher instead of Launcher3
All hardened features are in
Latest M5 kernel with voltage, kcal, sound, hotplug, multiple governors and TWRP
Download Link: http://forum.xda-developers.com/devdb/project/dl/?id=13577
P.S. Although, clean install is preferred, you may flash dirty if you are upgrading from the prior PA version. Still, to escape conflicts I would format everything including internal sd, then flash the rom, then flash Supersu, then do Xposed if you use it, then restore data partition that you previously backed up with TWRP, then reboot
______________________________________________________________________________________________________
Rom Updated on July 13. Latest changes. Also new kernel based on M5 with numerous governors/sound/kcal/voltage and others.
Download Link: http://forum.xda-developers.com/devdb/project/dl/?id=13516
Credit for kernel to Myself5
Kernel Source: https://github.com/AOSPME/android_kernel_sony_msm8974
_______________________________________________________________________________
Here is the latest Paranoid Andoird LP5.1 for Honami. Latest AOSP/Paranoid features.
My changes:
1. All security features including ciphers, random number generation, 256 bit encryption, SElinux out included
2, Kernel with sound, screen calibration, voltage, overclocking and TWRP
3. Evil IPs removed
4. WIFI background scanning disabled
5. Network selection is handled by System and you can set any available combination in Cell Networks and your selection will stick
6. VOLTE enabled, you are all set if and when your carrier offers the service
7. Camera mike sound fixed
8. Thermanger tweaked to prevent flickering
Instructions:
1. Full factory reset and separate wiping of System/Cache/Data
2. Flash the rom
3. Reboot and enjoy
Warnings: If your device dies or kills everybody in the vicinity, blame yourself. This is XDA, if you can't help yourself, stick with stock
Another Warning: Please no dumb questions in this thread, such as: where is my network, I am on C6902; where is my recovery; where is the gapps; No comments like this: great rom, except for one thing ; can you take a nose from DirtyUnicorns and stich it to this rom; oh, my god, the phone bootloops.. This rom boots and works. Also, no complaining about bugs without posting a readable logcat. Again, if you can't help yourself by reading, no one will help you. Can I support multi-rom? Never, multirom/kexec the way it is implemented on Android (by teenagers who have no concept of security) is a glaring security hole exposing your phone to multiple threats...
Download Link: http://forum.xda-developers.com/devdb/project/?id=10677#downloads
Credit: Paranoid Android and Myself5 for initial kernel sources
Kernel Sources: https://github.com/HonamiZ1/android_kernel_sony_msm8974
XDA:DevDB Information
Paranoid Android LP5.1 Unofficial, ROM for the Sony Xperia Z1
Contributors
optimumpro
Source Code: https://github.com/HonamiZ1/android_kernel_sony_msm8974
ROM OS Version: 5.1.x Lollipop
ROM Kernel: Linux 3.4.x
ROM Firmware Required: Unlocked Bootloader
Based On: AOSP
Version Information
Status: Stable
Stable Release Date: 2015-07-06
Created 2015-07-06
Last Updated 2015-07-18
Reserved
Reserved
Reserved
Mine...
Subscribed...
Sent from my Xperia Z1 using Tapatalk
You planning to regularly updating this build ?
Rom updated
New build is up. See the OP.
Please don't expect nightly files, which make no sense. There will be at least monthly updates or so.
The kernel in this build allows for much deeper undervolting. I have been testing different values in the past 24 hours and here is what I have:
300mhz 720
422mhz 730
652mhz 745
729mhz 765
883mhz 785
960mhz 800
1036mhz 810
1190mhz 825
1267mhz 840
1497mhz 860
1574mhz 880
1728mhz 900
1958mhz 925
2150mhz 950
And it is stable. No issues. I use lionheart cpu governor, which is the most lag free.
This works for all Z1's correct?
hakkai999 said:
This works for all Z1's correct?
Click to expand...
Click to collapse
If you have c6902, then you have to apply the patch to have network. Otherwise - yes.
Alright I got it to work. So far so good. Smooth as butter. Battery life is amazing. The only thing I sadly miss is the ability to use native Sony apps. I wish the Play Store would still count the phone as Z1.
Does anybody know a port for the stock Sony apps? Testing the ROM now. Thanks
Enviado do meu C6903 usando XDA Forums
nArdow said:
Does anybody know a port for the stock Sony apps? Testing the ROM now. Thanks
Enviado do meu C6903 usando XDA Forums
Click to expand...
Click to collapse
As far as I know you can't port the Sony apps because you need the Sony framework to run them.
LSD DREAMER said:
As far as I know you can't port the Sony apps because you need the Sony framework to run them.
Click to expand...
Click to collapse
That sucks. I wanted the camera and its libraries because the camera in this is less than stellar.
hakkai999 said:
That sucks. I wanted the camera and its libraries because the camera in this is less than stellar.
Click to expand...
Click to collapse
There is a port for camera.
http://forum.xda-developers.com/showthread.php?t=3154772
nArdow said:
There is a port for camera.
http://forum.xda-developers.com/showthread.php?t=3154772
Click to expand...
Click to collapse
Which one should I use? Its only for Dirty Unicorn, Resurrection Remix and CrDroid.
hakkai999 said:
Which one should I use? Its only for Dirty Unicorn, Resurrection Remix and CrDroid.
Click to expand...
Click to collapse
I didn' tested it. Yet. But it should work with all AOSP ROMs. I'm going to test and report back here
Could you please take this discussion about taking a nose from one rom and stiching it to this rom somewhere else?
Look in cross device development...
optimumpro said:
Could you please take this discussion about taking a nose from one rom and stiching it to this rom somewhere else?
Look in cross device development...
Click to expand...
Click to collapse
Sorry, m8.
Here... I just realised that there is two files for download. What are the differences between both?
nArdow said:
Sorry, m8.
Here... I just realised that there is two files for download. What are the differences between both?
Click to expand...
Click to collapse
Look at the dates: the latest one is July 13. If you want to look at changes, go to
https://github.com/aospa-l
optimumpro said:
Could you please take this discussion about taking a nose from one rom and stiching it to this rom somewhere else?
Look in cross device development...
Click to expand...
Click to collapse
Sorryyyy just wanted to have a better camera. You could at least... you know... advise us what our alternatives are? I mean we do love the rom. Just that we would want some features added.
LineageOS 13.0
Marshmallow - Android 6.0
About LineageOS
LineageOS is a free, community built, aftermarket firmware distribution of Android 6.0.1 (Marshmallow), which is designed to increase performance and reliability over stock Android for your device. LineageOS is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. You will need to provide your own Google Applications package (gapps). LineageOS does still include various hardware-specific code, which is also slowly being open-sourced anyway.
All the source code for LineageOS is available in the LineageOS Github repo. And if you would like to contribute to LineageOS, please visit our Gerrit Code Review. Your changelog is whatever was merged into gerrit.
Additional Information:
maguro wiki page
toro wiki page
toroplus wiki page
Download:
The latest builds & changelogs are available at
https://download.lineageos.org/maguro
https://download.lineageos.org/toro
https://download.lineageos.org/toroplus
Extras:
su (arm)
su removal (arm)
Google Apps can be found at http://opengapps.org/?api=6.0&variant=pico - beware that only the pico version will fit, unless you change your partition sizes! Also, starting from M, it's recommended to install gapps before the initial boot so the permissions are properly set up.
Bugs:
- Sometimes, quiet speaker pop sounds can be heard at the beginning and/or end of some audio streams (ie. touch sounds - the workaround is to disable them). For some reason, this isn't affecting everyone.
- Report back anything else you find which isn't listed here
FAQ:
Does this ROM supports F2FS?
- Yes, on /data and /cache - although /cache F2FS support might get removed in the future, as it's worthless.
Does this ROM uses DDK 1.9?
- Yes, with all the camera issues (ie. pink lines, rare crashes) resolved.
Why does the initial boot take so long, and where are my live wallpapers?!
- To make room on the system partition for the (bigger) M gapps packages, I had to sacrifice dexpreopt and the live wallpapers. This can result in pretty long initial boots or upgrade boots, and dexpreopt might run during the first time setup wizard as well, slowing down the system for an additional couple minutes.
Will you release newer ZMoD builds or something?
- Yes, as soon as the memory optimizations are finalized and I find enough time...
Want to support development? You can consider donating, I spent countless of hours with this
XDA:DevDB Information
LineageOS 13.0, ROM for the Samsung Galaxy Nexus
Contributors
Ziyan, MWisBest, Android-Andi, Everyone else who helped me: AOSP, Hashcode, ...
Source Code: https://github.com/LineageOS
ROM OS Version: 6.0.x Marshmallow
ROM Kernel: Linux 3.0.x
Version Information
Status: Nightly
Created 2016-02-11
Last Updated 2018-12-30
Does it have more ram 802 like the kernel used in cyanogenmod 12.1 you posted? Thank you!!!
Awesome!
Enviado desde mi GT-I9300 mediante Tapatalk
Thank you!!
AOSP Keyboard keeps crashing.. Apart from that everything seems to be working. Will check for more bugs in the meantime
Extraordinary work!!
PD: Device doesn't receive Internet connection. My ISP is Oceans Network from Spain.
You are a king!
Running on it for 1 hour, and already impressed... WOW !!!
Works perfectly
Works great! No problems at all and have been running it for 3hrs. Have xposed also installed. Great work!
I will continue to use and report any bugs i encounter.
great...Testing this rom right now. I had to rewipe,since installing gapps after the rom boot cause google play service to crash. I really wish there will be an official cm13 for galaxy nexus.I have a nexus 5 but I like galaxy nexus design and amoled screen...
Edit: this ROM runs very well,maybe a little better than other ones based on marshmallow
How much free ram? Is it 802mbytes or 762?in cn 12.1 there was a kernel boot img by zuyan that gave 802 mbytes of ram
Good job @Ziyan
Please guys, can anyone link me that kernel? I can't find it
Need suggestion, rootexplorer shown no root on this rom, how do i.
I try to flash ROM with TWRP, then fix root permission. @Ziyan could you please create this ROM support CWM.
Having random reboots now, is this happening to anyone else?
Reboots? Not yet
Gesendet von meinem Galaxy Nexus mit Tapatalk
@Ziyan can i flash kernels for lollipop like the one you posted on cm 12.1 recently?
NightWolf1396 said:
Having random reboots now, is this happening to anyone else?
Click to expand...
Click to collapse
Logs?
nikodr said:
@Ziyan can i flash kernels for lollipop like the one you posted on cm 12.1 recently?
Click to expand...
Click to collapse
No, but I attached a new kernel which has 811 mb userspace ram available (instead of the usual 756 mb). I think the crashes and tiler out of memory problems are gone, but report back if there's one single camera/camcorder crash happening
EDIT: the transition from the bootloader logo (google logo) to the boot animation won't be.. uhm... smooth, but it's nothing to worry about, I forgot to work it around this time
Ziyan said:
Logs?
No, but I attached a new kernel which has 811 mb userspace ram available (instead of the usual 756 mb). I think the crashes and tiler out of memory problems are gone, but report back if there's one single camera/camcorder crash happening
EDIT: the transition from the bootloader logo (google logo) to the boot animation won't be.. uhm... smooth, but it's nothing to worry about, I forgot to work it around this time
Click to expand...
Click to collapse
Will get them as soon as I get home
Ziyan said:
Logs?
No, but I attached a new kernel which has 811 mb userspace ram available (instead of the usual 756 mb). I think the crashes and tiler out of memory problems are gone, but report back if there's one single camera/camcorder crash happening
EDIT: the transition from the bootloader logo (google logo) to the boot animation won't be.. uhm... smooth, but it's nothing to worry about, I forgot to work it around this time
Click to expand...
Click to collapse
I will try zImage in my AOSP rom thanks can i use it no ?
Also there is no git commit for this extra RAM netither in OMAP4-AOSP or Ziyann github
werty100 said:
I will try zImage in my AOSP rom thanks can i use it no ?
Also there is no git commit for this extra RAM netither in OMAP4-AOSP or Ziyann github
Click to expand...
Click to collapse
Using the zImage on any DDK 1.9 / Android 6.0.1 ROM should be fine.
There is no git commit because I didn't push it yet (the values aren't final), but to get the same kernel I uploaded:
Clone https://github.com/CyanogenMod/android_kernel_samsung_tuna/tree/cm-13.0, and apply this, but with the following values:
CONFIG_ION_OMAP_TILER2D_SIZE=72
CONFIG_ION_OMAP_IPU_MEM_IOBUFS_SIZE=32
uji_sine said:
Need suggestion, rootexplorer shown no root on this rom, how do i.
I try to flash ROM with TWRP, then fix root permission. @Ziyan could you please create this ROM support CWM.
Click to expand...
Click to collapse
Enable root the same way you did it on CM12.1: enable developer settings, then you'll find the root option there. And just forget about CWM... don't use fix permissions and friends, as it might cause problems.
Ziyan said:
Using the zImage on any DDK 1.9 / Android 6.0.1 ROM should be fine.
There is no git commit because I didn't push it yet (the values aren't final), but to get the same kernel I uploaded:
Clone https://github.com/CyanogenMod/android_kernel_samsung_tuna/tree/cm-13.0, and apply this, but with the following values:
CONFIG_ION_OMAP_TILER2D_SIZE=72
CONFIG_ION_OMAP_IPU_MEM_IOBUFS_SIZE=32
Click to expand...
Click to collapse
I try before with zImage but rom was no booting i will try alter with commits thanks and kernel source
Hi OnePlus 5 peeps!
Today (June 27th), I graduated from high school!
In more important news, I finished upstreaming the OnePlus 5 kernel to the latest stable kernel version...
Whoa, what is this?
This is my personal kernel that I run as the OnePlus 5 is my daily driver.
I will not claim my work as the best at anything, but just know that I would not do anything to this kernel that could potentially ruin my own device.
Additionally, this is the kernel that comes built into CarbonROM.
There are three versions of this kernel:
AOSP aka AOSP/LOS build - Flash this on any source built custom ROM except for CarbonROM
CR-5.1 aka CarbonROM build - Flash this on CarbonROM
OOS aka OxygenOS build - Flash this version on OxygenOS
Main features:
Upstreamed Linux kernel version, went from v4.4.21 -> v4.4.79
Backported random driver from Linux v4.12 (latest and greatest)
Backported scheduler from Linux v4.9 (latest android kernel branch)
Upstreamed F2FS driver from f2fs-stable/linux-4.4.y
KGSL driver improvements
MDSS driver improvements
SOC driver improvements
Built using Optimization Level 2
Added maple io scheduler (default) by frap129
Added adreno idler by arter97 with tweaks from frap129
Vibrator motor control by flar2
Kcal control driver from EX kernel
Many wakelocks disabled
Switched to power efficient workqueues across the kernel
Built with Google's latest stable gcc-4.9
Anykernel 2.0 by osm0sis! Compatible with all OxygenOS based roms
Download:
Latest builds
OxygenOS boot.img
How to install:
1. Reboot into the latest stable TWRP build
2. Download kernel zip and make sure it is in your internal storage (/sdcard)
3. Reboot into TWRP
4. Double check here to see if you require any additional instructions
5a. Install -> Install image -> select oxygen-4.x.x-boot.img -> swipe to install
5b. Install -> select CarboniteKERNEL-XXX-Rx-OP5-N.zip -> swipe to install
6. Reboot
DISCLAIMER!
If you don't understand my instructions, that's too bad >
If you are unsure about what this thing is, I highly advise you do some research before going through with installing...
Updates will come as regular as I want them to, don't ask me when I'll release cause you'll know when it comes out >:'D
XDA:DevDB Information
CarboniteKERNEL for the OnePlus 5, Kernel for the OnePlus 5
Contributors
adinkwok, nathanchance, flar2, Lord Boeffla, osm0sis, etc
Source Code: https://github.com/adinkwok/oneplus5-kernel
Kernel Special Features: One of Taylor Swift's exes should write a song called "Maybe You're the Problem"
Version Information
Status: Testing
Created 2017-06-28
Last Updated 2017-08-02
While this reserved post is not being used, enjoy this video! (Find me at 0:50s and twice at 2:54 :silly
For OxygenOS users:
Code:
[B]If you are on OxygenOS and are coming from another custom kernel:[/B]
Download the latest stock.4.X.X-boot.img
You [B]must[/B] flash the boot.img before flashing the kernel!
[B]If you are on OxygenOS are switching to a different custom kernel:[/B]
Download the latest stock.4.X.X-boot.img
You [B]must[/B] flash the boot.img before switching kernels!
For AOSP/LOS/RR/etc users:
Code:
[B]If you are coming from another custom kernel:[/B]
You [B]must[/B] reflash your ROM build before flashing this kernel!
[B]If you are on AOSP/LOS/RR/etc and are switching to another custom kernel:[/B]
You [B]must[/B] reflash your ROM build before flashing another kernel!
Why is it like this?
I have included some ramdisk modifications that set the default settings for this kernel. When you come from a different custom kernel, the ramdisk changes from that kernel may conflict with the changes I intend to have. Likewise when you switch to a different kernel; my ramdisk changes may conflict with the changes they intend to have. When you flash the stock boot.img, it replaces the modified ramdisk with a clean one, removing these conflicts.
And it's here, get it while it's hot folks! First upstreamed kernel for the OP5
Thanks for joining the party :highfive:
Sent from my OnePlus5 using XDA Labs
gz on graduating! and thx for the kernel :=
Congratulations on the graduation buddy,
Just flashed and I had charging cycling on and off (using dash charger in car on freedom v1.1). Flashed EX and charging is fine. Need charge ATM but maybe a little later I can help you get a log.
Sent from my OnePlus5 using XDA Labs
congratulations! awesome... so smart!!!!!!!
rav101 said:
Congratulations on the graduation buddy,
Just flashed and I had charging cycling on and off (using dash charger in car on freedom v1.1). Flashed EX and charging is fine. Need charge ATM but maybe a little later I can help you get a log.
Sent from my OnePlus5 using XDA Labs
Click to expand...
Click to collapse
Hmmm never noticed this... I guess the graduation drinks are getting to me. I'll re-upload a stable build without upstreaming as that's definitely the culprit.
What an amazing day for you (Congratulations!) and the OP5 community!
I was really loving and enyoing all your efforts you did for the OPO (Pure Nexus port) and the amazing Carbon ROM.
adinkwok said:
Hmmm never noticed this... I guess the graduation drinks are getting to me. I'll re-upload a stable build without upstreaming as that's definitely the culprit.
Click to expand...
Click to collapse
I'm the first to report so let's see if anyone else has the same issue. I will also try for logs later on though I do have a lot on today (so might be this evening).
I didn't actually reboot or get to try a different charger to help diagnose so don't want you doing more work that you need to for what could me my issue
Sent from my OnePlus5 using XDA Labs
rav101 said:
I'm the first to report so let's see if anyone else has the same issue. I will also try for logs later on though I do have a lot on today (so might be this evening).
I didn't actually reboot or get to try a different charger to help diagnose so don't want you doing more work that you need to for what could me my issue
Click to expand...
Click to collapse
I can confirm the issue because while I was bringing up the upstream branch I ran into this issue with dash charging and I thought I solved it. Time to debug!
Edit: link updated without the upstreaming, everything else still stands though
adinkwok said:
I can confirm the issue because while I was bringing up the upstream branch I ran into this issue with dash charging and I thought I solved it. Time to debug!
Edit: link updated without the upstreaming, everything else still stands though
Click to expand...
Click to collapse
No problem buddy,
Be good once it's all resolved and we have the benefits of upstream kernel code as well!! Your time and effort is appreciated!
Sent from my OnePlus5 using XDA Labs
@rav101 happy to see u around buddy
dukat0s said:
@rav101 happy to see u around buddy
Click to expand...
Click to collapse
For sure my friend.
How you finding the OP5?
Sent from my OnePlus5 using XDA Labs
rav101 said:
For sure my friend.
How you finding the OP5?
Click to expand...
Click to collapse
Cool my friend !like it.just got rid of my s8+. Was bored
Is DT2W working for you guys?
bartelamo said:
Is DT2W working for you guys?
Click to expand...
Click to collapse
Seems to be a problem among a few custom built kernels, we're looking into it.
bartelamo said:
Is DT2W working for you guys?
Click to expand...
Click to collapse
adinkwok said:
Seems to be a problem among a few custom built kernels, we're looking into it.
Click to expand...
Click to collapse
It's because OOS has a hal that already uses a switch for dt2w.
New update, still looking into the gestures issue.
However, Dash Charging is fixed on the upstream kernel so here it finally is! I also added a bunch of sched patches, a thermal patch, and some other misc stuff from the latest CAF branch.
Adin-Kernel-R2-OP5-OOS-N.zip
What is the difference?
RELEASE: Tested after integrating new features, more stable than NIGHTLY. (Odexed builds)
NIGHTLY: Built daily with newest code and experimental features, might contain undiscovered bugs. (Deodexded builds)
HISTORY: Final odexded builds once a newer Android version is out and being built.
EXPERIMENTAL: Released when a new device is added or when a new feature is added for public beta testing and feedback. (Deodexded builds)
UNOFFICIAL: Maintained separately by individual developers, usually involves modification of shared code which cannot be merged (affects other devices), therefore maintained by the developer himself.
THIS IS A UNOFFICIAL VERSION BECAUSE IT CAN'T BE BUILT AT OFFICIAL SERVER! I just want you know Mokee and other AOSP ROM can't be official unless alberto96's lineage os be official.
I won't have time to update it anymore,you can use my source to continue it.See you next summer,everyone.(if nobody want to continue it,I will update it mouthly.(Sometimes weekly)
About
MoKee Open Source is based on the Google AOSP. We update our source code frequently to keep up with the latest development, and not forgetting to merge in special features of our own at the same time.
A small group of people from around the world who are interested in Android launched this project on the 12th of December 2012, and is committed to make this ROM better and better. Like most contributors of open source projects (Omni, CyanogenMod, Slim AOSPA etc), we are doing all these in our free time as our passion…
Since this project is open source, anyone interested can participate in the development (maintain new devices, contribute code etc). Newcomers are always welcomed!
Read here for developer application: http://www.mfunz.com/en/developer-application, you can host your unofficial MoKee builds on our server!
Credits:
Google, Qualcomm, Linux Kernel Organization, Motorola, Samsung, Lge, TI, Nvidia, Intel, Sony,
CyanogenMod, Omnirom, Slim Roms, Koush for open-sourced SuperUser, lineageOS, TeamWin,
Smartisan Digital Co, Substratum Development Team, The Open GApps Team.
ContributorErag0n(Migrate source from Lineage OS and build a zip) @sunilpaulmathew(Thanks for his suggestions and reply, most importantly, his awesome Kernel source.) @Alberto96(all hard work)
Features
1.Fully OMS Supported
2.Xposed Framework Supported
3.Can make a dirty flash which Lineage OS can't.
4.Phone & Messaging:Quick contacts look up, speed dialing, caller location and other useful features
5.Colorful Themes:Unleash the creative side of you, customize how your phone looks; make it cool, make it colorful!
6.Smart Controls:Increase your productivity with Active Display, Lockscreen Notifications and other shortcuts
7.Power Saver:With our unique battery saving strategies, get the most out of your phone's battery
8.Latest source merge from google android source.
9.Minimal but not simplify.
10.Delta update:8~15Mb, more than 300mb download space saved.
11.OTA Update
12.Odexed
Supproted Devices
ja3gxx(GT-I9500),ja3gchnduos(GT-I9502),jaltelgt(SHV-E300L),jalteskt(SHV-E300S/K),ja3gduosctc(SCH-I959).
After Odexed,ROM may have a large size(600~700MB),but it can get a better improvement.
Enjoy it!
Change logs:
MK60.1-8.13
Alpha build,this build is a stable RELEASE version,what is RELEASE?Please see the first line of post.
MK71.2-7.23
First build,sync to latest Mokee Source.
MK71.2-7.24
Second build, sync to lastest Mokee Source, Delta update available, Automatical translation, charger:fix small capture font.
MK71.2-7.25
Sync to lastest Mokee Source, change pixel launcher to default launcher, new kernel merged, now you can use Kernel Adiutor to custom kernel governor.
MK71.2-7.25-17.06
Fixed all bug, include high sensitive screen, display mode, novbar.Alberto not fixed bug I unable to fix.
MK71.2-7.26
Sync to latest source.
MK71.2-7.27
Sync to lastest Mokee Source, Kernel updated to 3.4.113, thanks to sunil.
MK71.2-7.28
Sync to latest source, stability is improved.
MK71.2-7.28-19.31
Sync to latest source.
MK71.2-7.29~8.05
Sync to latest source,new LawnChair launcher is added.
MK71.2-8.12
Xposed app added,automatical translation.Update to android-7.1.2_r29-tag
MK71.2-8.13
Only update for ja3gchnduos,jaltelgt,jalteskt.
MK71.2-8.20
Update source,probably fixed jalteskt incoming problem.OTA update supported,Gapps added.
MK71.2-8.26
Device Source updated,PowerHAL added,odexded,improve boot speed,Blur effect added and etc.
MK71.2-8.30
Source Update,bug fix.
MK71.2-9.02
Hardware source update,in next build,Gapps will be removed.
MK71.2-9.09
Source Update and Gapps removed, device ja3gduosctc added.
MK71.2-9.15
Source Update.
MK71.2-9.23
Source Update,kernel change to origin.
Delta update and full download：
Everyone can use delta update now, even installed stock gapps.
Delta Update can save your download time but get full function which contains in full update.
Full update is made for who use Mokee just once or need system files repaired.
Delta(OTA) update will keep 1 generation system up to date, in order to save space.
Version MK 71.2-7.23~7.26
https://drive.google.com/folderview?id=0B5BV4JClBJELa19mNjU4b2ZubUk
You must choose a version which is correct for you.
Version MK 60.1-8.13&MK 71.2-7.27 and above.(You can find all ROM contains MK 60.1 in it)
https://www.androidfilehost.com/?w=files&flid=202052
Recommend Kernel: (Now is build-in in Mokee.)
SmartPack is a good kernel that can give you better battery drain and system fluency.Thanks to sunilpaulmathew for making a awesome kernel.
If you want to see more about kernel,here is the link:https://forum.xda-developers.com/ga...nel-smartpack-project-lineage-os-14-t3590858/
How to build:https://github.com/exynos5410/manifest There are some unique changes for mokee open source,if you want to build one,ask me for help without hesitation,I will try my best to help you.
Issues (copy from Alberto's post)
MK 71.2 issues:
Filesystem Socket Whitelist (https://goo.gl/1N6n7G) - The only issue that requires to be fixed in order to get official.
SELinux (Permissive)
BASED ON USERS FEEDBACK: Mobile Signal Reception isn't 100% stable.
Shared Storage (doesn't encrypt the storage)
ja3gxx: In-Call Echo Effect (random and rare)
ja3gxx: In-Call Volume can't be increased/decreased
ja3gxx: OK Google (Automatic Voice Recognition)
ja3gchnduos: Missing Dual SIM support.
jalteskt: Mobile Data and Incoming Calls don't work.
jalteskt: USSD Codes can't be sent.
jaltelgt: RIL crashes on boot, meaning that Calls/Data won't work.
MK 60.1 issues:
1.Audio HAL isn't working correctly, causing VOIP issues, HDMI audio instabilities and mixer paths conflicts
2.STK Toolkit isn't working yet, SMSs aren't properly sent (RIL issue)
3.SELinux policies are almost complete, with just some minor missing rules
4.Wireless Display (or Miracast if you like) stream is corrupted, buffer issues
5.Adoptable Storage isn't stable, crashes while encrypting the external storage (Kernel Panic). Read Here: http://goo.gl/0w6DPt
6.Device Encryption isn't stable for the same issue that affects Adoptable Storage
Problems report
You need report problems with your
ROM Version
Step to get bugs
If possible,with a logcat is better.
Source Code
https://github.com/Dracanrage
Sorry for my bad English
ROM OS Version: 7.x Nougat
ROM Kernel: Linux 3.4.113
ROM Firmware Required: Lollipop Bootloader and Modem, TWRP 3.1.1 as Recovery
Based On: AOSP
Version Information
Status: UNOFFICIAL
Created 2017-07-23
Last Updated 2017-09-23
Screenshots
Is there any differences between Los and it?
Super Sha said:
Is there any differences between Los and it?
Click to expand...
Click to collapse
Yes.
1.Pixel Round Icon
2.Substratum build-in and OMS supported.
3.Merged source from Android O
4.Xposed Framework build-in.
5.Battery Save and etc.
6.Delta Update can make dirty update and save more than 300MB download space.(In next build)
(As we know Lineage OS can't make dirty update，and don't have a theme engine, a rounded icon.)
Erag0n said:
Yes.
1.Pixel Round Icon
2.Substratum build-in and OMS supported.
3.Merged source from Android O
4.Xposed Framework build-in.
5.Battery Save and etc.
6.Delta Update can make dirty update and save more than 300MB download space.(In next build)
(As we know Lineage OS can't make dirty update，and don't have a theme engine, a rounded icon.)
Click to expand...
Click to collapse
Nice work!I will try it soon. Will it be official?
Super Sha said:
Nice work!I will try it soon. Will it be official?
Click to expand...
Click to collapse
Sorry, it can't be.
As Alberto says, unless Samsung update the Kernel source to fix the Zygote problem, it can't be official.
i will try, thanks.
Is there any problem with mobile data and call echo?
tosunkaya said:
i will try, thanks.
Is there any problem with mobile data and call echo?
Click to expand...
Click to collapse
As Lineage OS, there should not have any problem with mobile data, but call echo will appear randomly (according to different hardware which Samsung use).
app to sd
how to move app to sd card ?
RahmahTunisa said:
how to move app to sd card ?
Click to expand...
Click to collapse
There is a error in make SD card as internal storage, so it can't move app to SD card in Nougat.
This error is mentioned in Alberto's post, I use his device, vendor, hardware source to make this ROM, so this ROM have the same problem.
What about battery draining?
It's like lineage ?
Mohamed rajab said:
What about battery draining?
It's like lineage ?
Click to expand...
Click to collapse
I think it maybe a little better than Lineage OS because source is optimized.
Here is the screenshot, regularly, if it show's 3 hours left, it actually can use 3~4 hours
Lineage OS often show's 2 or 3 hours left, so I think it was a little better than Lineage OS.
But due to the exynos hardware, it will be heat if you use your phone to play a big game or other heavy CPU work, it can't be solved because exynos 5410 is heat and battery drain since it be announced.
Hey, guys.
Delta update is come back now, you will see it in today's update.
Edited
Delta update is available.
Camera2.zip for installed stock gapps guys.
About how to use, please read the main post.
Edited
This file is useless, you need get Camera2.app from 7.23 ROM zip.
Edited 7.25
Mokee updated the check script, it is no need to keep Camera2 installed.
Nice work
Thank you so much
Erag0n said:
I think it maybe a little better than Lineage OS because source is optimized.
Here is the screenshot, regularly, if it show's 3 hours left, it actually can use 3~4 hours
Lineage OS often show's 2 or 3 hours left, so I think it was a little better than Lineage OS.
But due to the exynos hardware, it will be heat if you use your phone to play a big game or other heavy CPU work, it can't be solved because exynos 5410 is heat and battery drain since it be announced.
Click to expand...
Click to collapse
Tell me, what bugs are there? And can I use opengapps aroma?
What bugs do we have here?
Does it support remapping the hardware keys (like RR) for example, you can use long press on back button to get you back to home..
Please make a telegram group to discuss the ROM..
And for battery drain, I suggest you to underclock the CPU to 450mhz and use only two cores.
I didn't understand how to use smart pack Kernel, can you explain?
nebrassfarfoor said:
Tell me, what bugs are there? And can I use opengapps aroma?
What bugs do we have here?
Does it support remapping the hardware keys (like RR) for example, you can use long press on back button to get you back to home..
Please make a telegram group to discuss the ROM..
And for battery drain, I suggest you to underclock the CPU to 450mhz and use only two cores.
I didn't understand how to use smart pack Kernel, can you explain?
Click to expand...
Click to collapse
Yes, you can use aroma, but had better not install Google camera in order to use delta update.
It support remapping the hardware but not support long press custom.
About bugs, please read the main post
About battery drain, Mokee Open Source make some optimizations, and kernel is not been limited.
About using smartpack Kernel, you can use twrp to flash it, and I am working for merge smartpack kernel to Mokee.
About telegram group, I am so sorry that I can't make one because Chinese telephone number is limited in sent message to strangers.
Hey, guys.
I fixed my S4 today.
Now I can test a amazing Kernel.
Thanks to @sunilpaulmathew for his help and smartpack source.
Hi
Bug = not notification miscall and sms
deletanha said:
Hi
Bug = not notification miscall and sms
Click to expand...
Click to collapse
Oh, it was terrible.
Let me check.
Waiting for a minutes please.
Edited
In my S5 official Mokee, missing was common if I use Aegis.
Did you use it?
The Unlegacy Android Project
TF201 | TF300T/TG/TL | TF700T
Introduction
Unlegacy Android started out as the OMAP4-AOSP Project. It was created in late 2015 in order to maintain a clean and organized place for pure AOSP support for various OMAP4 devices, such as the Galaxy Nexus and the Samsung Galaxy Tab 2 series. Over time this evolved to support more than just these devices, but still maintains its roots of supporting "legacy" devices that no longer receive "official" updates: hence Unlegacy Android was born. In our opinion, these ROMs are how the official updates would look.
On top of AOSP, we only include changes which are necessary to support the hardware, be secure, and get acceptable performance. Current features for the Asus Transformer Series include:
- Linux kernel 3.4.y (currently 3.4.113)
- BFQ IO scheduler (official kernel 3.4 release), set up so GUI processes have the highest priority
- F2FS support from kernel 4.9 (for /data and /cache)
Installation
You must have NvFlash backup. It is MANDATORY!
You need to use modified TWRP recovery that works with updated F2FS. If you're planning to install GApps, be sure to read the second post!
Problems
Non working/Known bugs:
- GPS; - need a device owner to configure!
- Camera (both);
- Dock special keys (top row);
- Modem on TG and TL;
- GUI crashes; - occure less often
Currently, no one from Unlegacy Team, has TF300T/TG/TL device. Help in developing or device donation would be highly appreciated.
Downloads
See: http://builds.unlegacy-android.org. Our automated builds ensure that we always have the latest Android security patches merged in, without having to manually start and upload builds Else is enclosed in downloads.
Features?
There isn't much to say here - this is AOSP, if you install GApps, you pretty much get the same thing that's running on the Nexus devices (see the second post). The aim of this project is to create a fast and stable ROM - although, one could use Xposed (or similar) to add extra features.
As usual, feedback is appreciated
Contacts
You may join Telegram development group, where all fresh staff is published and tests are made.
XDA:DevDB Information
Unlegacy Android Project, ROM for the Asus Transformer TF300T
Contributors
Clamor, Ziyan
Source Code: https://github.com/Unlegacy-Android
ROM OS Version: 7.x Nougat
ROM Kernel: Linux 3.4.x
ROM Firmware Required: Bootloader 4.2 JB
Based On: AOSP
Version Information
Status: Beta
Created 2018-02-18
Last Updated 2018-10-17
Installation gide (for those who uses F2FS)
Before installing ROM you need to update your current recovery with this TWRP, else you will get a bootloop with next format from fastboot. Install zip from your current recovery and reboot into your current system. Than boot into new recovery and install ROM (with factory reset).
Currently 3.4 kernel isn't stable enough for daily use. You may use updated 3.1 _that16 kernel, it works fine with this ROM. To make wifi work with _that16 kernel just move nvram_nh615.txt from system/etc to data/misc/wifi and rename to nvram.txt
You may use KatKiss 7.1 if you want, but you must flash a _that16 kernel every time after flashing KatKiss ROM. Else you will get a bootloop with next format from fastboot.
If you want to go back to ordinary TWRP, you need to make a format from fastboot, flash TWRP and make formats from there as well.
REPARTITION and TREBLE
I worked on this for few last weeks to make it stable and simple enough to any user to install this update. As usual NvFlash is MANDATORY! TF300TG/TL users shouldn't use this as it can harm your tablet.
So, UA_Bootloader.zip includes latest JB4.2 10.6.1.27.5 bootloader, modified TWRP [email protected] from Downloads section and my new partition table. It's main benefits are /system partition increased to 1GB and /vendor partition. This means that we may install bigger gapps packages and support of TF's may be extended plus having /vendor partition gives us at least hardware support for Project Treble, even if there is no 8.1 builds currently.
Before installation copy everything from tablet on PC, else all you data will be lost! To install this update just install it via TWPR and when flashing is finished press reboot into system. Than wait till blue line gets to the end and tablet reboots. Tablet will than stuck into ASUS screen with Device is Unlocked sign in top left corner. Than reboot manually into recovery and format /system to ext4; /cache to ext4 or f2fs; /data to ext4 or f2fs and you are good to go.
New partition table is compatible with all existing ROMs for TF's. If you flash ROM with system in .img file you need after flash into recovery do Wipe -> System -> Advanced Wipe -> Change or resize partition -> Resize filesystem. If you want to restore 4.2 state you can flash Stock or Bootloader 4.2 attached in Downloads section.
How is this project going? and why you choose android 7.1? instead of the new android 8.0? because i would definitely want to help with a android 8.0/8.1 rom
androidjel said:
How is this project going? and why you choose android 7.1? instead of the new android 8.0? because i would definitely want to help with a android 8.0/8.1 rom
Click to expand...
Click to collapse
8.1 is my next step, it'll be easy to reach. But to have good experience with 8.1 we need a stable fully functional 7.1 build.
Clamor said:
8.1 is my next step, it'll be easy to reach. But to have good experience with 8.1 we need a stable fully functional 7.1 build.
Click to expand...
Click to collapse
Ah okay thats clear, a other question i want to try this rom but there are no downloads.
I want to test for you if you want? :good:
androidjel said:
Ah okay thats clear, a other question i want to try this rom but there are no downloads.
I want to test for you if you want? :good:
Click to expand...
Click to collapse
All needed files you can find in Downloads tab on top of this thread
Clamor said:
8.1 is my next step, it'll be easy to reach. But to have good experience with 8.1 we need a stable fully functional 7.1 build.
Click to expand...
Click to collapse
Clamor said:
All needed files you can find in Downloads tab on top of this thread
Click to expand...
Click to collapse
I see tnx, what do you want to know or what do you want to have tested to help you?
and Btw which TWRP is that? i have the last one already installed.
androidjel said:
I see tnx, what do you want to know or what do you want to have tested to help you?
and Btw which TWRP is that? i have the last one already installed.
Click to expand...
Click to collapse
Nothing, you may install Rom to see current project progress (If you have TF300T there will be no sound). For further developement test device is needed, or a developer with TF300T(better solution). Mostly all major functions are fixed, see buglist, and 3.4 works on all transformers on Tegra 3.
That is KANG TWRP with support of updated F2FS
TF300T users, if you are interested in further developement, please help me with debuging sound driver. I need a tester, with TF300T and some free time.
Clamor said:
TF300T users, if you are interested in further developement, please help me with debuging sound driver. I need a tester, with TF300T and some free time.
Click to expand...
Click to collapse
I am more than willing to be a tester if you want. Heck, I will even find a cheap TF300T to load only this on. My mornings are relatively free as my business doesn't pick up till noon or so. Just PM me specifics of what you need. Any more development for our tablets is a blessing as far as I am concerned
I would love to help debugging, testing and developing. I'm currently in possession of a tf300t with dock and an me301t. Do you think it will be possible to port this to the ME301t?
@gs-crash-24-7 please write me in PM. Actually ME301t was supported at early stages of 3.4 bringup. I fully excluded it from board since I couldn't test it and Memopad parts made transformers board really messy. I had enough problems with TF stuff at that moment.
3.4 kernel porting and repartitioning before were just a dream, but now they are real. Memopad bringup depends only on your interest in it.
Oreo 8.1
Yesterday I have quickly build 8.1 ROM for transformers. There doesn't work almost anything and I won't have excess to my TF201 for a while to fix stuff Rom can be booted with same requirements as N roms. Here is first build. Please don't post any issues/logs here from O for now. I know already about all major issues.
I have some good news. Here is mostly working Oreo build with issues from N + non working bt. I'm still working on fixing staff so this isn't last build.
P.S. Remove system/lib/hw/bluetooth.default.so to avoid constant bt crash
Any possibility of sharing the 3.4 kernel supporting the ME301t...I have that little bugger and the latest software updates from my TV provider and Netflis like programs are all KK dead for the most part. Having unlegacy on the Me301t would be a dream come true and would avoid trashing this one and getting a new one just because I want to see some shows or TV. Thank you for your work. I will assist to the best of my knowledge.
@AlphaDivxMovies nothing impossible, but first of all, I have no MemoPad and it's hardware isn't that close as my Prime is with TF300T. Second is that I put huge amount of my time and afforts in porting transformer board so I have no desire at all to do this once more time, I can help with suggestions but actual development will lie on your shoulders.
P.S. To just boot rom atm you would need only a kernel port, ROM is mostly compatible. Almost all drivers memopad uses are already included. You may contact @gs-crash-24-7 as well, he has memopad and if he agrees, than work in pair is much more simple.
@Clamor , Where is the oreo version? https://builds.unlegacy-android.org/ here i could only find the 7.1.2 version.
The other downloads in this post dont work anymore (oreo).
@androidjel sure, since there are no stable enough builds on O and even N builds aren't for everyday use with 3.4 kernel. I didn't launch O builds for a long time.
Clamor said:
@androidjel sure, since there are no stable enough builds on O and even N builds aren't for everyday use with 3.4 kernel. I didn't launch O builds for a long time.
Click to expand...
Click to collapse
@Clamor But could you launch a O build again? maybe i could try to help, I have some time to do that at the moment.