Related
Since the Xperia M aka nicki is no longer maintained I decided to start my own build and I thought I share it with the community.
Full Disclosure: I am not a developer. If there are bugs in any build, I cannot solve them. So always do a backup before flashing.
Also if you do not know how to flash: leave it be. I will not help with flashing problems.
I will try to keep it up-to-date.
You can download it here: https://drive.google.com/file/d/0B7J1cVOauuana0l0NG1GWmE1aWc/view?usp=sharing
Android: 7.1.2
Security Patches: May 2017
Komapatient said:
Since the Xperia M aka nicki is no longer maintained I decided to start my own build and I thought I share it with the community.
Full Disclosure: I am not a developer. If there are bugs in any build, I cannot solve them. So do always a backup before flashing.
Also if you do not know how to flash: leave it be. I will not help with flashing problems.
I will try to keep it up-to-date.
You can download it here: https://drive.google.com/file/d/0B7J1cVOauuana0l0NG1GWmE1aWc/view?usp=sharing
Click to expand...
Click to collapse
Thank you bro for sharing and keeping the device alive ?
Btw you should consider posting this in android development forum so that people know abt it
Adarsh Dubey said:
Btw you should consider posting this in android development forum so that people know abt it
Click to expand...
Click to collapse
I intentionally posted not in the development section, since I am not developing but only building.
Komapatient said:
I intentionally posted not in the development section, since I am not developing but only building.
Click to expand...
Click to collapse
Bro you shouldn't post it in original development but you can post it in Android development as you are building the rom for the device and many of the people port roms they also don't develop nor fix bugs but post it in Android development as they are building the rom for the device
sir @Komapatient , can you please share the source kernel or ROM?
Nicklas Van Dam said:
sir @Komapatient , can you please share the source kernel or ROM?
Click to expand...
Click to collapse
Hi,
I don't understand your request. I pulled the sources from LinOS Git. There is nothing done on the source.
Komapatient said:
Hi,
I don't understand your request. I pulled the sources from LinOS Git. There is nothing done on the source.
Click to expand...
Click to collapse
Ok, it's neccesary for now. Can you please to keep update on this ROM?
Komapatient said:
Since the Xperia M aka nicki is no longer maintained I decided to start my own build and I thought I share it with the community.
Full Disclosure: I am not a developer. If there are bugs in any build, I cannot solve them. So always do a backup before flashing.
Also if you do not know how to flash: leave it be. I will not help with flashing problems.
I will try to keep it up-to-date.
You can download it here: https://drive.google.com/file/d/0B7J1cVOauuana0l0NG1GWmE1aWc/view?usp=sharing
Android: 7.1.2
Security Patches: May 2017
Click to expand...
Click to collapse
So basically you're keeping the ROM updated with latest changes from lineage OS source code , I mean bug fixes and security patches etc.
matrixex said:
So basically you're keeping the ROM updated with latest changes from lineage OS source code , I mean bug fixes and security patches etc.
Click to expand...
Click to collapse
Yes. As a courtesy to the people who cannot compile their own ROM and to give s.th. back to the community who helped me a lot of times.
Hi @Komapatient,
Glad to see you once again around here, think we last talked when you were using the Xperia V on LineageOS.
Happy to see nicki is not fully dead and that its users can benefit from newer builds.
However there's a big concern here, I pushed the Nicki official removal for two important reasons :
- Device sources are no longer updated. If there's no real issue it's fine, but might appear.
> Issues like autobrightness flashing in a weird way upon device wake/unlock is among the biggest issue fixed / wip since the changes stopped.
> Checked in my huashan sources to find common relevant things for nicki, I just pushed an overlay cleanup and fix for MMS non-Data use.
- Kernel sources are highly outdated. To put this in a easy way, we can judge the security status
> to be around December 2016 and February 2017. Therefore the security version you share here is only the ROM sources,
> though a good portion of the security patches are actually to be worked upon for each kernel.
You can find our internal CVEs vulnerabilities tracker concerning the nicki 8x27 kernel here : https://cve.lineageos.org/android_kernel_sony_msm8x27
Someone should at some point stand up and start looking at them one by one,
fixing the ones related to the kernel version by cherry-picking, testing then pushing to gerrit.
You can take my sony_msm8960t kernel as reference if you wish, only the most recent CVEs are a work in progress,
and you should therefore easily see which CVEs concern your 3.4 kernel and find the commits in my history.
I'd gladly merge commits uploaded to gerrit if they are valid and properly authored / clean.
Hope this makes the current status of Nicki a bit more clear.
Bye.
@AdrianDC
Thank you for your clarification. The kernel sources are indeed a bummer, but as my coding skills are below zero. Sadly I am not able to help here out.
Komapatient said:
@AdrianDC
Thank you for your clarification. The kernel sources are indeed a bummer, but as my coding skills are below zero. Sadly I am not able to help here out.
Click to expand...
Click to collapse
Trying to "steal" my commits from sony_msm8960t would be a good start,
you can also check the commits tags on Gerrit to see the CVE 20xx-xxxx related numbers
when the information was set as topic, helps clearing the list too.
Since the work is already done on our side, it shouldn't be a giant work to do,
and would be a good place to start with + bring back some security updates to the device.
Please try to update this rom
please try update this rom, ,
Introduction
Hello everyone, this is a thread to introduce both users and kernel developers to the concept of linux-stable as well as give developers some tips and a tree to either merge into their own, use as a base, or just as a reference. Feel free to ask questions and enjoy!
What is it?
linux-stable is, as the name implies, the stable branch of the Linux kernel, the base of Android. The phone could not run without the Linux kernel (at least not without reworking a lot of stuff). The Android kernels are based on the longterm stable trees:
Longterm
There are usually several "longterm maintenance" kernel releases provided for the purposes of backporting bugfixes for older kernel trees. Only important bugfixes are applied to such kernels and they don't usually see very frequent releases, especially for older trees.
Click to expand...
Click to collapse
Source: https://www.kernel.org/category/releases.html
All Linux development happens on the master branch, which is governed by Linus Torvalds. When issues are discovered there, the fixes are applied then backported to these various stable trees for consumption. It is not uncommon for a fix to need to go back a few years.
There is a LOT more information available in the notes repo in the android-linux-stable organization if you care to learn more in-depth: https://github.com/android-linux-stable/notes
What does this mean for me?
If you are a developer, this means you should be merging these changes into your own tree. These are vetted, stable fixes to real world problems and they are being handed out for free. It does not take long to get up to date (as you can just merge this tree directly into your own or do it yourself using the tree as a reference) and once you are up to date, there is usually a release once every two weeks, give or take. I provide a rebuttal to a lot of various complaints here. If you still feel like there is a good reason not to do this, please let me know, I'll be happy to try and debate on it!
If you are a user, it means that you should be looking for and using kernels that have these fixes, as it shows the developers care for your security and stability. The current version for this device is 4.4.78 on OOS and 4.4.100 on Lineage while the current version upstream is 4.4.162 so all you need to do is go into Settings > About phone and look at the kernel version to know if you are up to date.
How do I use?
If you are a developer, the reference tree is located in the android-linux-stable organization: https://github.com/android-linux-stable/op5
There are three branches, one for OxygenOS 8.0 stable, one for OyxgenOS 8.1 beta, and one for Lineage 15.1.
This can either be merged into your existing kernel tree if you have one or be used as a fresh base. You do not need my permission to use it nor do you need to give me credit (although it would be appreciated).
If you are a user, use a kernel that has the changes added in!
Getting notified about updates
There are a few ways to get notified of linux-stable updates:
The linux-kernel-announce mailing list: http://vger.kernel.org/vger-lists.html#linux-kernel-announce
The android-linux-stable Telegram channel: https://t.me/alsupdates
Subscribe to this thread
Follow me on Google+ or Twitter
Getting help
If you have any issues with getting these changes into your tree or want to ask a question, there are a few different ways to do it:
Post in this thread
Join the linux-stable support chat on Telegram: https://t.me/joinchat/C1UAJ1EMSX31PCFdwLnOSg
File an issue either in the android-linux-stable notes repo or the android-linux-stable repo for this device
When requesting help, please give some solid details as to what you are struggling with, as I am happy to provide assistant and clarity but not to do something for you (unless I screwed up).
From what I understand, you're creating a space where you're updating the stock Kernel to the latest Linux tags and creating a clean base that others can develop upon for a consistently updated kernel?
Seems to me like the epitome of a community project and in keeping with the heart behind open source.
Great work Nathan!!!
Sent from my OnePlus 5 using XDA Labs
rav101 said:
From what I understand, you're creating a space where you're updating the stock Kernel to the latest Linux tags and creating a clean base that others can develop upon for a consistently updated kernel?
Seems to me like the epitome of a community project and in keeping with the heart behind open source.
Great work Nathan!!!
Sent from my OnePlus 5 using XDA Labs
Click to expand...
Click to collapse
Exactly correct I have seen others grab my kernel and base their work upon (which I have zero issues with) but I know most do it because I've merged linux-stable as one of my first things. Figured I would make their lives easier (plus doing the conflict resolution summaries helped me validate my own work). I am mulling over posting these to the mailing lists so other mainline Linux developers with these devices can easily test new builds and get the latest fixes without needing to do the work themselves (even if they are fully capable).
nathanchance said:
Exactly correct I have seen others grab my kernel and base their work upon (which I have zero issues with) but I know most do it because I've merged linux-stable as one of my first things. Figured I would make their lives easier (plus doing the conflict resolution summaries helped me validate my own work). I am mulling over posting these to the mailing lists so other mainline Linux developers with these devices can easily test new builds and get the latest fixes without needing to do the work themselves (even if they are fully capable).
Click to expand...
Click to collapse
If you're doing the work anyway and it's just a simple push to mailing list then might as well. Others can choose whether to use it or not but at least it's there. :good:
Sent from my OnePlus 5 using XDA Labs
where to download the link?
Gayrat1999 said:
where to download the link?
Click to expand...
Click to collapse
This isn't a kernel you flash, this is something for developers to use in their own work. For example, my kernel Flash already has all of this, which you can flash.
Nice. How about GCC error fixes and wifi stack driver in this base?
neobuddy89 said:
Nice. How about GCC error fixes and wifi stack driver in this base?
Click to expand...
Click to collapse
I toyed with the idea of doing two branches (one for building, one for usability) but decided against it as 1. I want this source to be as plain as possible and 2. It doesn't fully fit with the idea of this project. This purely to help developers get up and running with linux-stable, not a fully fledged custom kernel. I will consider adding the GCC fixes to the usability README though, that could be useful.
You are a true asset to this community!
4.4.103 has been merged in, with conflict notes updated accordingly.
Oh boy oh boy it might be time for a rebase for me
4.4.104 has been merged in, with conflict notes updated accordingly.
I truly apologize to anyone who was tracking the tree because I just force pushed. I decided to update the location and branch name and wanted everything to be consistent. It is now up to date with 4.4.105.
I have updated the OP with the notes and tree location. The new notes are on the staging branch right now, they will be merged into master once everything is finalized.
I'm sorry being out off topic, but can i use this https://github.com/android-linux-stable/msm-3.18 kernel source as base for my soc (msm8937) sir?
zainifame said:
I'm sorry being out off topic, but can i use this https://github.com/android-linux-stable/msm-3.18 kernel source as base for my soc (msm8937) sir?
Click to expand...
Click to collapse
Most likely yes. For the future, this thread is geared towards the generic CAF trees (msm-3.18 and msm-4.4). Feel free to ask me anything over there.
4.4.106 has been merged in (conflict notes).
4.4.107 has been merged in.
4.4.108 has been merged in.
4.4.109 has been merged in (conflict notes).
4.4.110 has been merged in (conflict notes).
Introduction
Hello everyone, this is a thread to introduce both users and kernel developers to the concept of linux-stable as well as give developers some tips and a tree to either merge into their own, use as a base, or just as a reference. Feel free to ask questions and enjoy!
What is it?
linux-stable is, as the name implies, the stable branch of the Linux kernel, the base of Android. The phone could not run without the Linux kernel (at least not without reworking a lot of stuff). The Android kernels are based on the longterm stable trees:
Longterm
There are usually several "longterm maintenance" kernel releases provided for the purposes of backporting bugfixes for older kernel trees. Only important bugfixes are applied to such kernels and they don't usually see very frequent releases, especially for older trees.
Click to expand...
Click to collapse
Source: https://www.kernel.org/category/releases.html
All Linux development happens on the master branch, which is governed by Linus Torvalds. When issues are discovered there, the fixes are applied then backported to these various stable trees for consumption. It is not uncommon for a fix to need to go back a few years.
There is a LOT more information available in the notes repo in the android-linux-stable organization if you care to learn more in-depth: https://github.com/android-linux-stable/notes
What does this mean for me?
If you are a developer, this means you should be merging these changes into your own tree. These are vetted, stable fixes to real world problems and they are being handed out for free. It does not take long to get up to date (as you can just merge this tree directly into your own or do it yourself using the tree as a reference) and once you are up to date, there is usually a release once every two weeks, give or take. I provide a rebuttal to a lot of various complaints here. If you still feel like there is a good reason not to do this, please let me know, I'll be happy to try and debate on it!
If you are a user, it means that you should be looking for and using kernels that have these fixes, as it shows the developers care for your security and stability. The current version for this device is 4.4.116 and the current version upstream is 4.4.162 so all you need to do is go into Settings > About phone and look at the kernel version to know if you are up to date.
How do I use?
If you are a developer, the reference tree is located in the android-linux-stable organization: https://github.com/android-linux-stable/wahoo
This can either be merged into your existing kernel tree if you have one or be used as a fresh base. You do not need my permission to use it nor do you need to give me credit (although it would be appreciated).
If you are a user, use a kernel that has the changes added in!
Getting notified about updates
There are a few ways to get notified of linux-stable updates:
The linux-kernel-announce mailing list: http://vger.kernel.org/vger-lists.html#linux-kernel-announce
The android-linux-stable Telegram channel: https://t.me/alsupdates
Subscribe to this thread
Follow me on Google+ or Twitter
Getting help
If you have any issues with getting these changes into your tree or want to ask a question, there are a few different ways to do it:
Post in this thread
Join the linux-stable support chat on Telegram: https://t.me/joinchat/C1UAJ1EMSX31PCFdwLnOSg
File an issue either in the android-linux-stable notes repo or the android-linux-stable repo for this device
When requesting help, please give some solid details as to what you are struggling with, as I am happy to provide assistant and clarity but not to do something for you (unless I screwed up).
4.4.103 has been merged in.
This is my first Nexus / Pixel (VZW Galaxy Nexus I don't count), how soon does Google typically release the kernel source for the DP's? Only after the official software release?
I'm torn between stable + your kernel and DP + stock kernel.
Telperion said:
This is my first Nexus / Pixel (VZW Galaxy Nexus I don't count), how soon does Google typically release the kernel source for the DP's? Only after the official software release?
I'm torn between stable + your kernel and DP + stock kernel.
Click to expand...
Click to collapse
It depends. Longer DPs like the initial release of a new major number (7.0, 8.0, etc) typically get kernel source within a month of the new DP version dropping. Smaller DPs usually don't get source until release (7.1 is the only other small DP that has ever happened so not much history).
:good::good::good:
I dont mean to go too offtopic here, but does that apply to the android source codes too? I meam does it usualy take that long for them to release the sources? I am guessing we still dont have any custom roms because the sources were not released by google yet?
4.4.104 has been merged in, with conflict notes updated accordingly.
The repo location has changed (new link is in the OP).
Additionally, an 8.1 branch has been created. Google went from 4.4.56 to 4.4.88 so the branch was redone to avoid conflicts and go with Google's resolution. The notes have been updated as well. Happy kerneling!
4.4.106 has been merged in (conflict notes).
4.4.107 has been merged in.
4.4.108 has been merged in.
4.4.109 has been merged in (conflict notes).
4.4.110 has been merged in (conflict notes).
4.4.111 has been merged in.
Just as a heads up, I started school on Monday so while the updates will still continue, they may not be as timely as they have in the past, especially if there are conflicts that I need to document.
4.4.112 has been merged in (conflict notes).
I used this conflict in my video talking about thinking through linux-stable conflicts, check it out! https://www.youtube.com/watch?v=yWvU8_0O66A
4.4.113 has been merged in (conflict notes).
4.4.114 has been merged in.
4.4.115 has been merged in (conflict notes).
4.4.116 has been merged in.
The OP has been updated, including some more information for users as well as some more ways of getting help and notified of updates! Enjoy
I started working on a New Oreo Nebula Kernel, using the latest Caf for the msm8996 Series kernels..........
I started a week ago, I originally wasnt going to do a new kernel for the HTC10, But Device started to tick me off and the guy that I was going to leave it in his hands, was busy,
and I was bored and needed to do something, So I started on it.........
Let me explain something first, This isnt a LAYOVER Stock source, Meaning, I didnt not take stock and lay it over CAF,
first off that would be next to impossible with the 7400 series CAF that I used.. 7400 series is rebased CAF tag for 8.1 series kernel..
Stock source originally started with 02500, but seeing an update came out before they released it, they added in 03000 into their source..
Stock source = 3.18.63, which is 02500 in caf, 03000 = 3.18.66, HTC didnt change the sub to 66 but kept it 61.. Not sure why.. anyhow,
that is 8.0 Oreo Series, anyhow, as of Caf 05300 Oreo 8.1 Series started, CAF rebased that tag, First time I ever seen them do that..
Latest caf tag for msm8996 is CAF 07400 8.1 Series................
I originally Took the Caf 03000 8.0 Series and imported all Needed HTC components that allow HTC10 to boot and work.... I left out as much debugging and other un-needed HTC related crap
that did nothing but slow the device down.... I created a master Skeleton GIT Repo, that allowed others to take and mod to their liking..
after I finished with the master, I decided I wanted to grab the latest CAF, again 07400, and then I picked all my own commits again from master into the 07400 with a few manual changes that I had to make
for it to work right, Then Created a new master based on the 07400 tags.
From the 07400 tags, I started working on Nebula 1.0.0-2e-7400, 2e = 2nd Edition, and the 7400 = Caf Tag.....
I have working builds but Choose not to release anything on xda at this point, More testing has to be done.. If anyone is interested in testing,
then goto our Telegram Group, location in my Sig or our PureFusionOS thread..............
Nebula 2e is at its very early stages of custom mods.. So dont expect alot at this time........
I know this question will be asked, Will it work on my 7.x firmware or ROM.......
I used @flar2's commit to disable verify, allowing it to boot on all firmwares and ROMs, but Camera will only work on any rom with the 8.x blobs.....
So even know it boots on a ROM with 7.x blobs, the camera will crash unless your on 8.x blobs ROM.................
Reason be, cause I imported the stock camera from Oreo, so yes, it needs Oreo blobs to talk to hardware, otherwise it wont be able to handshake and just crash...
everything else works perfect from my testers point of view.. Some minor issues, but normally tracked down and fixed quickly....
This will be my Final Kernel work on the HTC10, after this I will most likely never work on the HTC10 again............ I am moving on....................
I just wanted to give one last thing to the public before I move on..............
ETA: Not sure.. Still testing............ Join our Telegram group to get access to test releases..............
Good luck
Great work !
Can i get one ?
Nice placeholder :silly:
Mr Hofs said:
Nice placeholder :silly:
Click to expand...
Click to collapse
Its not a placeholder when the name of the section is Guides and News and Discussion..
Eliminater74 said:
Its not a placeholder when the name of the section is Guides and News and Discussion..
Click to expand...
Click to collapse
Please take a joke, it means waiting for a link here.
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?