Related
I managed to compile cm12.1 for the D800 using vendor and device files from TheMuppets, and Kernel from Lg-devs.
I dirty flashed over cm12, still discovering issues. You MUST flash a cm12.1 gapps if you had gapps before or you will boot loop. Also highly recommend uninstall/re-install other google apps (like "keep").
Works:
Booting up
Wifi
LTE Data(using T-mobile APN)
Voice
Rotation (be sure you have the latest baseband)
I have the OEM case with the window on it for the watch thing:
The watch thing doesn't appear because that is not implemented(yet) in CM but it does sleep and wake with the magnet thing.
Knock to Wake
Double tap status bar to sleep
Stuff not tested:
LTE or voice on AT&T APN (I use T-mobile on this device) Please provide feedback
pretty much everything else
Not Working:
Does not grant me 3 wishes even if one of those wishes is for an iPhone
Download here:
Removed by OP for now
Contributors
SergeantWagner, cyanogenmod, TheMuppets, CAF
ROM OS Version: 5.1.x Lollipop
ROM Kernel: Linux 3.4.x
ROM Firmware Required: LG G2 D800
Based On: CyanogenMod
Version Information
Status: Nightly
Created 2015-06-30
Last Updated 2015-06-30
reserved
Do you have @Rashed97 consent and permission? Just like the thread below, this will probably get closed.
http://forum.xda-developers.com/lg-g2/development/cm12-1-caf-5-1-1-variants-dt2w-t3122206
I have not. I'll reach out to him and see what's up. Closing this thread in the mean time (if I can figure out how)
Edit: could not figure out how to close the thread so I took down the download links.
SergeantWagner said:
I have not. I'll reach out to him and see what's up. Closing this thread in the mean time (if I can figure out how)
Edit: could not figure out how to close the thread so I took down the download links.
Click to expand...
Click to collapse
It's all good man, just wanted to inform you that Rashed didn't want his CM sources out yet until finished and didn't want ya getting 'punished' so to speak
Pseudo_Soldier said:
It's all good man, just wanted to inform you that Rashed didn't want his CM sources out yet until finished and didn't want ya getting 'punished' so to speak [emoji14]
Click to expand...
Click to collapse
However, there are at least 5-6 roms which are using these sources, so... [emoji14]
Because, as far as I'm concerned - RR, Bliss, 2x Euphoria, AICP and some builds by zg85 (for d802) - all of them are more or less based on lg-devs sources.
Hbohd said:
However, there are at least 5-6 roms which are using these sources, so... [emoji14]
Because, as far as I'm concerned - RR, Bliss, 2x Euphoria, AICP and some builds by zg85 (for d802) - all of them are more or less based on lg-devs sources.
Click to expand...
Click to collapse
From how I understand it, those use official CM sources as Rashed has not pushed CAF into CM yet. Yes they work on the CAF bootstacks but are not fully based on the rest of Rashed CM work. It's confusing to me tbh, I was simply referencing the previous closure not stating rules or anything. No source has been posted for these builds in OP so I can't be sure.
Hbohd said:
However, there are at least 5-6 roms which are using these sources, so... [emoji14]
Because, as far as I'm concerned - RR, Bliss, 2x Euphoria, AICP and some builds by zg85 (for d802) - all of them are more or less based on lg-devs sources.
Click to expand...
Click to collapse
Right, and drgravy is a member of lg devs, so he is allowed to use his own work.
Other ROMs have seaked permission from rashed and the lg devs.
The problem is people go all lolololololololopensource and don't have enough respect to ask the guys working on it, and giving proper credits.
I reached out to @Rashed97 to see what I can do to help move things along, my main goal was to try to get official nightlies kicked off for the D800, and using the sources mentioned in the OP it has been stable for me for about a day so far. It looks like his main concern with the linked post was it may be dangerous to flash with the wrong bootstacks and he doesn't want peeps to claim his work as their own. Perfectly understandable. So I won't upload builds until rashed is cool with it, but if you want to try this yourself you can compile using the sources mentioned above with minimal configuration changes. I got my d800 on the cheap from e-bay so I'm not too worried about bricking it, but if you are worried about yours maybe you should just wait .
[ROM] [7.1.x] [OMS] [EAS] ibrokemyLINEAGE [LOS] [20170807]
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Code:
*** Disclamer
no legal responsibility taken for anything.
use at own risk.
install with full knowledge that this //could// make your phone 100% unusable and out of warrantee.
INTRODUCTION
This is a personal LineageOS build, based upon 14.1. I pull in changes as I see them, and sometimes this breaks things. I will upload builds as I build them, as long as they pass brief personal testing (eg they boot)
Posting this as a seperate thread mainly because it may take a different direction to others, and is not meant to just be a LOS nightly, I will be pulling changes at my discretion, this ROM is being built by me, for me, and I just happen to be sharing it.
Feel free to contribute, recommendations and (new) bug reports are always very welcome.
Click to expand...
Click to collapse
SPECIAL FEATURES
At the moment this may seem a little bland, but the point is not to become a new big rom, but simply to be a LineageOS based rom with the latest little addons, which at the moment include:
@tabp0le Kernel built with rom (Source)
FULL Energy Aware Scheduler support
FULL ROOTLESS Substratum theme engine support with ThemeInterfacer and OMS7
Substratum app pre-included with app store updates
SU_ENABLED by default (builtin root manager from CyanogenMod)
FULLY compatible with both firmwares (MM and N)
Supports F2FS
SELinux ENFORCING
ForceEncrypt DISABLED
Click to expand...
Click to collapse
INSTRUCTIONS
Download the rom, check the hash and flash it and ARM64 7.1 GAPPS (Dynamic/Beansgapps recommended) through TWRP.
For updates, dirty flash of ROM only should do, if you have played around with system apps then perhaps clean the dalvik and cache, just to be safe.
Click to expand...
Click to collapse
BUGS
None known
Click to expand...
Click to collapse
DOWNLOADS
LATEST:
20170807
older versions:
20170502
20173003
20170903
20170131
20170131
20161218
20161215
20161215
Click to expand...
Click to collapse
CHANGELOG
Code:
Rebuild on latest sources
Update OMS
Update themeinterfacer
Fixed sdcard issues
Fixed USB OTG issues
Older changelogs:
Code:
Remove snap camera
Add google camera
UBERTC
Snapdragon LLVM
Update OMS commits
Add substratum as system app
Substratum verification
Rebase of sources upon tabp0le's eas
Fix SD issues
Add back software nav bar
EAS config changes
Improved hardware blobs
Updated power config
Updated hardware overlays
LOS upstream changes
Kernel upstream changes
WLAN wakelocks toggleable
Improved battery usage
Removed some redundant dev settings
Update some drivers/configs for camera and display
Adds Qualcomm Snap Camera
Add OMS7 rootless commits
Fix inclusion of Substratum app (604)
Replace masquerade with ThemeInterfacer (v50)
Compiled with UberTC and Snapdragon LLVM
Tabp0le kernel 1.03
Updated vendor files
Pre odex enabled (faster first boot)
GPS config updated
fix fingerprint sensor
update from upstream
include bluetooth aptx support
new vendor blobs
Rebrand to ibrokemyLINEAGE
Switch from Elite Kernel to Tabp0le Kernel
Better OMS7 integration
FINGERPRINT SENSOR works on both firmwares without need for patches
Substratum app now updates correctly from store
EAS support enabled by default, Kernel and Ramdisk support out of box.
Rebase on CAF sources
Latest patches/fixes
GPS fixes
WiFi stability improvements
WITH_SU set to true
Forceencrypt disabled again
Rebase on LineageOS 14.1
Update kernel
Refactor OMS changes
General cleanups
Latest source from upstream.
OMS7/Masquerade, the backend for the new SUBSTRATUM theme engine. Simply download the substratum app from the play store to use it!
FINALLY a working subwoofer (bottom speaker)
innumerable misc patches
other misc perf changes
Revert breaking audio commits. - https://github.com/ibrokemypie/android_device_htc_pme/commit/928c5e1674571fac980d2e730983c4c59c55f412
Build with Elite Kernel, thanks @buckmarble! - https://github.com/ibrokemypie/android_device_htc_pme/commit/6df6a1b650336bd9f97bed756dc397f1a2862d50
Click to expand...
Click to collapse
Thanks To/Credits
Code:
rc420head, Mahdi786, crpalmer, leedroid, buckmarble and tabp0le
XDA:DevDB Information
ibrokemyLINEAGE 14.1.x, ROM for the HTC 10
Contributors
ibrokemypie, rc420head, Mahdi786, crpalmer, leedroid, buckmarble, tabp0le
Source Code: https://github.com/ibrokemypie/android_device_htc_pme/
ROM OS Version: 7.x Nougat
ROM Kernel: Linux 3.10.x
Based On: LineageOS
Version Information
Status: Beta
Created 2016-12-15
Last Updated 2017-03-29
XDA:DevDB Information
ibrokemyLINEAGE 14.1.x, ROM for the HTC 10
Contributors
ibrokemypie, rc420head, Mahdi786, crpalmer, leedroid, buckmarble, tabp0le
Source Code: https://github.com/ibrokemypie/android_device_htc_pme/
ROM OS Version: 7.x Nougat
ROM Kernel: Linux 3.10.x
Based On: LineageOS
Version Information
Status: Stable
Current Beta Version: ibrokemypie
Created 2016-12-15
Last Updated 2017-08-10
Reserved
I shall give this a try. Thanks @ibrokemypie!
Yup me too, I will also try it. I tested the RR Android N this morning with ZERO issues coming from BadBoys (Sprint HTC 10). I remained on the MM kernel so even TWRP worked with no issues. VERY excited and glad to see N is coming to the HTC 10!
Thanks for contributing! I wish I had the knowledge to contribute .
Moderator Warning,
Thread cleaned. Flaming users is not acceptable on XDA. If you have an issue with a post, report it and move on.
This is amazing! EVERYTHING works (except GPS), I did a GPS lock in the Sense OS but still cannot see the satellites but this is OK, I know it will come in time! I am coming from Sprint HTC 10 (BadBoys/official), wiped everything full/clean and installed this with PICO GAPPs, data works, TXT/MMS works, cellular works, no issues with anything except GPS. VERY WELL DONE! Speed test shows BLAZING LTE so I know its seeing the basebands correctly, etc., so all is good from my side, very happy! FINALLY a working N AOSP for my Sprint HTC!!
GROOVYJOSHCLARK said:
This is amazing! EVERYTHING works (except GPS), I did a GPS lock in the Sense OS but still cannot see the satellites but this is OK, I know it will come in time! I am coming from Sprint HTC 10 (BadBoys/official), wiped everything full/clean and installed this with PICO GAPPs, data works, TXT/MMS works, cellular works, no issues with anything except GPS. VERY WELL DONE! Speed test shows BLAZING LTE so I know its seeing the basebands correctly, etc., so all is good from my side, very happy! FINALLY a working N AOSP for my Sprint HTC!!
Click to expand...
Click to collapse
What about the speaker problem?
GROOVYJOSHCLARK said:
This is amazing! EVERYTHING works (except GPS), I did a GPS lock in the Sense OS but still cannot see the satellites but this is OK, I know it will come in time! I am coming from Sprint HTC 10 (BadBoys/official), wiped everything full/clean and installed this with PICO GAPPs, data works, TXT/MMS works, cellular works, no issues with anything except GPS. VERY WELL DONE! Speed test shows BLAZING LTE so I know its seeing the basebands correctly, etc., so all is good from my side, very happy! FINALLY a working N AOSP for my Sprint HTC!!
Click to expand...
Click to collapse
Did you flash the N firmware?
mcwups1 said:
Did you flash the N firmware?
Click to expand...
Click to collapse
Nope, stayed with MM, and I had speaker, no issues with sound, maybe I am lucky, IDK but TWRP worked, and everything I need from my daily driver except GPS.
Hello, the codename "pme" which version of HTC 10 corresponds?
All these.. perfume_uhl, perfume_whl and perfume_ul?! Thanks!
pickandrew said:
Hello, the codename "pme" which version of HTC 10 corresponds?
All these.. perfume_uhl, perfume_whl and perfume_ul?! Thanks!
Click to expand...
Click to collapse
those are the country codes are they not? pme is perfume in general
Stephen said:
Moderator Warning,
Thread cleaned. Flaming users is not acceptable on XDA. If you have an issue with a post, report it and move on.
Click to expand...
Click to collapse
Edit: only quoted you because the post I was replying to got erased.
Thanks for following rules. Sorry if I'm breaking them.
BUT
As far as I'm concerned flaming should be done if source is not public on github and someone hacked your private github account. But sharing is caring
And It benefits us all.
I didn't Flame when I asked in a thread if anybody was working on cm-14.1 and when I started work on it I didn't even write what the commit was that I added but somehow cm-14.1 still came and all the work I done was used. IT REALLY WASNT USED. as there is plenty of github sources to give ideas and plenty of code changes. We as developers need more developers as the code game is big. If someone is contributing to a worthy cause let them. Do any of you developers out there like having sleepless nights trying to figure out code? I don't think so. And me I don't know **** but I can figure it out hahahaha.
This post is just a general post so report me but let people learn dammit. And a guide doesn't teach you how to fix building errors so guides don't help. Going through code of familiar devices does.
twinnfamous said:
Edit: only quoted you because the post I was replying to got erased.
Thanks for following rules. Sorry if I'm breaking them.
BUT
As far as I'm concerned flaming should be done if source is not public on github and someone hacked your private github account. But sharing is caring
And It benefits us all.
I didn't Flame when I asked in a thread if anybody was working on cm-14.1 and when I started work on it I didn't even write what the commit was that I added but somehow cm-14.1 still came and all the work I done was used. IT REALLY WASNT USED. as there is plenty of github sources to give ideas and plenty of code changes. We as developers need more developers as the code game is big. If someone is contributing to a worthy cause let them. Do any of you developers out there like having sleepless nights trying to figure out code? I don't think so. And me I don't know **** but I can figure it out hahahaha.
This post is just a general post so report me but let people learn dammit. And a guide doesn't teach you how to fix building errors so guides don't help. Going through code of familiar devices does.
Click to expand...
Click to collapse
Hey, I didnt see your post from before, this whole thing, I really didn't mean to offend or steal, I just wanted to make the progress accessible to people who dont have the time or resources to build the code themselves, even if it is mostly just following a guide. Beside from that, the point of open source is for people to take something and make it do what they want, without restrictions, and to be able to give and take if they can. I am not simply taking the work of others and packaging it as my own, I am trying to make contributions, even if I am not a super great programmer like @crpalmer, who is putting together the pieces to make this work for us all. I am not taking the work of others and claiming ti was mine. That was not my intention at all and I am sorry it may have seemed as such.
GROOVYJOSHCLARK said:
Nope, stayed with MM, and I had speaker, no issues with sound, maybe I am lucky, IDK but TWRP worked, and everything I need from my daily driver except GPS.
Click to expand...
Click to collapse
Hey, about to start properly looking into GPS as I was able to repro the problem, however GPS satellites are being detected, and certain bits are working, so I feel fixing it should be within my capabilities, however for the moment I am working on including theming through Substratum, with full implementation with the inclusion of Masquerade backend (OMS) which should be build ready in a little while.
Hey @ibrokemypie,
Out of curiosity, are you duel booting Linux, using a VM Linux environment or just generally using Linux as your OS and building Cyanogenmod from there? Also how much space have you got allocated for building Cyanogenmod. I'm trying to figure out if I have the capability to do it on my MacBook Pro if I clear out some space.
Sent from my HTC 10 using XDA Labs
ibrokemypie said:
Hey, about to start properly looking into GPS as I was able to repro the problem, however GPS satellites are being detected, and certain bits are working, so I feel fixing it should be within my capabilities, however for the moment I am working on including theming through Substratum, with full implementation with the inclusion of Masquerade backend (OMS) which should be build ready in a little while.
Click to expand...
Click to collapse
That's awesome, I really appreciate it! This is the only thing keeping me from fully committing to this as my daily runner. I use GPS pretty much every day so I need it. I've always ran with AOSP on all of my androids and this is usually an issue across the board in the initial releases so I get it and appreciate your hard work!
sent from my HTC 10
rav101 said:
Hey @ibrokemypie,
Out of curiosity, are you duel booting Linux, using a VM Linux environment or just generally using Linux as your OS and building Cyanogenmod from there? Also how much space have you got allocated for building Cyanogenmod. I'm trying to figure out if I have the capability to do it on my MacBook Pro if I clear out some space.
Sent from my HTC 10 using XDA Labs
Click to expand...
Click to collapse
Well, initially I tried just building on my macbook, but ran out of space verrrry quickly. Do not recommend even trying unless you have a MINIMUM of 150gb that you can dedicate it, wasted a whole two days with this.
Tried building on a ****ty laptop too, but discovered that you really can't build at all unless you also have at the very least 8gb of ram, so ended up taking the drive out of that and sticking it in my gaming rig with 16gb ram.
Building on an arch linux install, mostly just via ssh with a tmux session to reduce overhead.
GROOVYJOSHCLARK said:
That's awesome, I really appreciate it! This is the only thing keeping me from fully committing to this as my daily runner. I use GPS pretty much every day so I need it. I've always ran with AOSP on all of my androids and this is usually an issue across the board in the initial releases so I get it and appreciate your hard work!
sent from my HTC 10
Click to expand...
Click to collapse
hey, just as a test, could you try setting your location to device only, open up google maps and tap the little icon to go to your location? I think it will ask you to allow it access to enable wifi/cell location, so deny that and tap it again, and you should see your location as a grey dot. If this works, can you then tap it once more, and take your device somewhere? There is a chance gps is wokring after all, just not reporting itself as suck to anything...
ibrokemypie said:
Well, initially I tried just building on my macbook, but ran out of space verrrry quickly. Do not recommend even trying unless you have a MINIMUM of 150gb that you can dedicate it, wasted a whole two days with this.
Tried building on a ****ty laptop too, but discovered that you really can't build at all unless you also have at the very least 8gb of ram, so ended up taking the drive out of that and sticking it in my gaming rig with 16gb ram.
Building on an arch linux install, mostly just via ssh with a tmux session to reduce overhead.
Click to expand...
Click to collapse
Yeah I think it's gonna be a no go for me then as my MacBook Pro only has 256gb in total and im currently using 60gb for Windows 10.
If I were to get a build PC together, what components are most required for building Android? After having at least 8gb of ram, is it all processor or a mix of processor and gpu?
Trying to think if I can make an Intel NUC type PC with the built in graphics card or if I need to be getting discrete graphics card as well.
Sent from my HTC 10 using XDA Labs
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).
WARNING:
This is not a post targeted to end users. It is a development reference. If you expect any installable download or even added features out of this thread, please close your browser. Thank you.
What is Umbrella?
Umbrella is a project that aims to make the kernel sources that HMD released for Nokia 8 Sirocco (A1N) compatible with the Nokia 8 (NB1). The idea behind this is to replace the outdated 8.0 kernel sources that HMD released for NB1 with more up to date ones that are used in the 9.0 builds for Nokia 8 Sirocco.
Why do this, you might ask. Well, the answer is simple: The devices are so similar that HMD / FIH already have their kernel sources in a shared source tree. You can validate that yourself, by downloading the kernel config from a stock NB1 kernel (under /proc/config.gz), unpacking it, and searching for the commended entry "CONFIG_FIH_A1N". What umbrella does is take the sources that were released for A1N, readd all device specific files for NB1 (they were pruned) from it's original kernel soure, and integrate the stock kernel config (also called defconf) from NB1.
Doing this also lead to some other small quality of life improvements that are not directly relevant to an end user.
Umbrella contains the latest changes from linux-stable (v4.4.179 at the time of writing, compared to the stock v4.4.153), and Qualcomms Codeaurora upstream
The WiFi driver from Qualcomm is compiled directly into the kernel, instead of being loaded as a module. This allows you to flash umbrella based kernels to every build version while keeping everything else working correctly. The stock kernels use signature enforcement, which means that the wifi module that is loaded from the system partition has to be signed against the kernel, which is not the case for every custom kernel or even the kernels that were built for a different security patch.
Unlike the officially released kernel sources, umbrella does not have stupid typos in it's device trees that cause the phone to display white bars on all of your screen etc.
Umbrella disables the block that FIH put in place to prevent users from rebooting into EDL mode from within android (using adb reboot edl).
Umbrella also includes a patch that causes the device to not reset it's entire memory when the kernel crashes, therefore retaining the last kernel output log, which can be used for debugging
You can compile the kernel with compilers newer than GCC 4.9 (not clang though), without having it immideately crash at boot.
It includes a tool that automatically sets up a crosscompiling environment for the kernel.
What Umbrella is not
Umbrella is not a project to add significant new features, or the ability to tweak things beyond what the stock kernel already offers (which is technically not that bad). It aims to be a reference kernel, a base for (potentially) other kernels that are based on it and add those features. I know that that is kind of a broad goal, considering I am the only one who seems to do actual development for this phone, but who knows. Having a lower entry level might help in case someone is curious and wants to get into kernel hacking. And I would certainly be happy if I wasn't the only one developing for this device.
If you want Umbrella to contain features like:
Overclocking
More governors / schedulers / whatever
Color / Sound / whatever control
Wakelock blocking
etc. etc. etc.
then please Alt-F4 your browser right now. Ok, don't do that but at least please don't request it because it will make you get ignored, nothing else.
Why the name Umbrella?
While I developed the initial prototype I watched through 3 Resident Evil movies, and this is kinda a zombie project, so I think the name fits quite well.
Why are you posting this?
I am posting this because I am hoping that it will be useful for anyone that would like to get into kernel development and tweaking without the hassle that comes with setting up the kernel sources that are released by HMD.
But, one disclaimer: I am not a kernel developer. I am a curious CS student suffering from a bad mix of too much time and stupid ideas that solve stupid problems. I am trying my best to produce something useful and be of help, but please don't expect wonders from me, thanks.
Links?
Source: https://github.com/resident-nokia/umbrella
Download: None, this is a development reference.
Looks promising
Sent from my NB1 using XDA Labs
Nice. this will likely be useful in the future
Updated the umbrella source to the latest 4.4.180 kernel, and May 07 CAF tag (LA.UM.7.4.r1-05100-8x98.0). Also readded some NB1 specific code where it was missing (discovered by doing a diff against the 5140 kernel source that Nokia recently released).
Just in case anyone actually cares about it
THMSP said:
Updated the umbrella source to the latest 4.4.180 kernel, and May 07 CAF tag (LA.UM.7.4.r1-05100-8x98.0). Also readded some NB1 specific code where it was missing (discovered by doing a diff against the 5140 kernel source that Nokia recently released).
Just in case anyone actually cares about it
Click to expand...
Click to collapse
I do. Who knows, in a year's time I might have enough knowledge to build a custom Rom for this phone
Kernel sources which is used on pie has been released officially. Finally, we have an "original" kernel and we've got closed one more step to custom roms.
https://www.nokia.com/phones/en_int/opensource/
techno_man000 said:
Kernel sources which is used on pie has been released officially. Finally, we have an "original" kernel and we've got closed one more step to custom roms.
https://www.nokia.com/phones/en_int/opensource/
Click to expand...
Click to collapse
@THMSP it would be interesting to let us know how different is your kernel mod from the newly released official pie kernel for Nokia 8
MDV106 said:
@THMSP it would be interesting to let us know how different is your kernel mod from the newly released official pie kernel for Nokia 8
Click to expand...
Click to collapse
As I described here: https://forum.xda-developers.com/nokia-8/development/official-source-code-releases-nokia-8-t3930324, they are identical. The only difference are the device tree files (which still contain typos that break the display), and of course all modifications I made to the sirocco kernel source that Umbrella is based on (wifi driver, EDL mode reactivation, upstreaming, etc.)
THMSP said:
As I described here: https://forum.xda-developers.com/nokia-8/development/official-source-code-releases-nokia-8-t3930324, they are identical. The only difference are the device tree files (which still contain typos that break the display), and of course all modifications I made to the sirocco kernel source that Umbrella is based on (wifi driver, EDL mode reactivation, upstreaming, etc.)
Click to expand...
Click to collapse
So, are these new codes broken like 4.84?
techno_man000 said:
So, are these new codes broken like 4.84?
Click to expand...
Click to collapse
I wouldn't call Nokia sources broken, but I would call them incomplete, outdated and impractical to work with. And that hasn't changed.
Iam currently building device tree for nokia 8..
Unable to figure out how to edit init folder specifically for nokia8
[email protected] said:
Iam currently building device tree for nokia 8..
Unable to figure out how to edit init folder specifically for nokia8
Click to expand...
Click to collapse
Please do so! We can't let this phone die so early!
which defconfig file should choose?
lk
[email protected] said:
which defconfig file should choose?
Click to expand...
Click to collapse
nb1_defconfig is for Nokia 8
Can somebody help me? I have built Lineage OS 16.0 for the Nokia 8 with the Umbrella Kernel. However I am facing issues with getting it into work. Firstly TWRP fails to flash it with error 7. I am including the recovery.log file in case anyone wants more detail. I then proceeded to extract the payload.bin file, and flashed boot.img and system.img seperately. However that didnt work either as my phone got stuck at the Bootloader unlocked warning screen. If anyone is interesteed I can upload the .zip outputed by the build
Device Tree: https://github.com/GPUCode/android_device_nokia_nb1
Recovery.log: https://hastebin.com/akohutiwed.sql
Thanks in advanced
emufan4568 said:
Can somebody help me? I have built Lineage OS 16.0 for the Nokia 8 with the Umbrella Kernel. However I am facing issues with getting it into work. Firstly TWRP fails to flash it with error 7. I am including the recovery.log file in case anyone wants more detail. I then proceeded to extract the payload.bin file, and flashed boot.img and system.img seperately. However that didnt work either as my phone got stuck at the Bootloader unlocked warning screen. If anyone is interesteed I can upload the .zip outputed by the build
Device Tree: https://github.com/GPUCode/android_device_nokia_nb1
Recovery.log: https://hastebin.com/akohutiwed.sql
Thanks in advanced
Click to expand...
Click to collapse
hey, did you wipe userdata before flashing this? I think you need to do that, like when switching to using GSIs.
also, have you checked this https://github.com/resident-nokia/twrp? Specifically the fstab file for NB1.
oaid said:
hey, did you wipe userdata before flashing this? I think you need to do that, like when switching to using GSIs.
Click to expand...
Click to collapse
Thanks for the suggestion. I have flashed GSIs before but never had any problems. Also I cannot find any userdata partition in TWRP. I asked in the Lineage OS discord and I was told that probably that TWRP image is broken. I am confused
emufan4568 said:
Thanks for the suggestion. I have flashed GSIs before but never had any problems. Also I cannot find any userdata partition in TWRP. I asked in the Lineage OS discord and I was told that probably that TWRP image is broken. I am confused
Click to expand...
Click to collapse
that's the data partition, if I'm not mistaken ?*
which twrp image are you using? Maybe try Dorian's latest?
oaid said:
that's the data partition, if I'm not mistaken ?*
which twrp image are you using? Maybe try Dorian's latest?
Click to expand...
Click to collapse
Yes I am using the latest TWRP. Before flashing I erased the data partition but still the error persisted
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?