[ROM][8.1.0][OTA][UNOFFICIAL] LineageOS 15.1 [15.11.2018]
- Thread starter #Henkate
- Start date
-
- Tags
- huawei nova lineageos oreo xda
Dear Henkate, thank you for the rom.
Unfortunately, I have 2 novas, both with broken screen, but who cares)
The ROM is really great and smooth!
An information for you - while flashing I received "Error 7" - what tells us that we are trying to flash rom not suitable for the device, so I had to edit "updater-script" following next instruction: https://xdaforums.com/showthread.php?t=2522762
For some reason my device was marked as " " - I mean no symbols at all xD
Unfortunately, I have 2 novas, both with broken screen, but who cares)
The ROM is really great and smooth!
An information for you - while flashing I received "Error 7" - what tells us that we are trying to flash rom not suitable for the device, so I had to edit "updater-script" following next instruction: https://xdaforums.com/showthread.php?t=2522762
For some reason my device was marked as " " - I mean no symbols at all xD
Thank you for your feedback!
What's your Nova model? Maybe I'll just get rid of that assert.
No, you wont. I have CAN L-11, but in system files I have NO model at all)
One more feedback - I have much better LTE signal in office. I mean on LOS 14.1 I had 9 mbps, and now about 30-40 mbps. I am happy)
Device and vendor trees are up!
DEVICE AND VENDOR TREES ARE UP!
I've cleaned the commit history of device and vendor trees and i've uploaded them to github. Check out the first post or simply go to my github. Feel free to contribute. In case you're planning to build a ROM and share it here on XDA, please keep in mind that i'm gonna build AEX. I've announced that i'm planning to build AEX Oreo since long time ago.
As a side note, i've still kept some camera commits in device tree from the days i was trying to get it working with the stock camera blob, but there were much more and even more branches lol.
Also, you might see some commits which were done yesterday or today, but they were actually done earlier (up to 3 months ago or so). The reason they were done yesterday or today is because i've had to make a new commit including e.g. commits where i've fixed a typo.
PS: i still got to clean the commit history of the kernel, but as you already know, i've published that in the day i've published lineage 15 as it's mandatory on XDA. So, please bear the commit history of the kernel for a while xD.
DEVICE AND VENDOR TREES ARE UP!
I've cleaned the commit history of device and vendor trees and i've uploaded them to github. Check out the first post or simply go to my github. Feel free to contribute. In case you're planning to build a ROM and share it here on XDA, please keep in mind that i'm gonna build AEX. I've announced that i'm planning to build AEX Oreo since long time ago.
As a side note, i've still kept some camera commits in device tree from the days i was trying to get it working with the stock camera blob, but there were much more and even more branches lol.
Also, you might see some commits which were done yesterday or today, but they were actually done earlier (up to 3 months ago or so). The reason they were done yesterday or today is because i've had to make a new commit including e.g. commits where i've fixed a typo.
PS: i still got to clean the commit history of the kernel, but as you already know, i've published that in the day i've published lineage 15 as it's mandatory on XDA. So, please bear the commit history of the kernel for a while xD.
Last edited:
I experienced this rom one day, I have to say that it is great, it runs very fast, I did not clear the data in the nougat version and went directly to Oreo, no problem, thank you for your work: good:
Something is still funny with the sources. Like the loop between lineage and the huawei mk files, vendor and device. Will set up my environment again tomorrow. Good work none the less.[/QUOTE]
Keep getting that some makefile is missing. No worries, was just playing around. I really only have an hour or two then come back to it the next day, so most probably I am missing a lot.
added code stuff but it seems to have not gone though in my post. It was:
*** Can not locate config makefile for product "lineage_hwcan"
Keep getting that some makefile is missing. No worries, was just playing around. I really only have an hour or two then come back to it the next day, so most probably I am missing a lot.
added code stuff but it seems to have not gone though in my post. It was:
*** Can not locate config makefile for product "lineage_hwcan"
Last edited:
Thank you for your feedback!
I'm not really sure what you've meant though. You mean that the in-call volume is low or that when phone is ringing the volume is low? I believe you've meant the first one, but just to make sure.
In-call volume seemed fine to me, but I'll check the logs when possible. As a side note, the in-call volume slider is not working if I'm not mistaken.
One more thing. You'd make it easier for me if you'd upload a logcat too with the issue you're experiencing. Sometimes maybe I'm not able to reproduce the same issue and that would be helpful.
Maybe I'll add a script which takes the needed logs to make it easier for people who doesn't know how to take one, although there's Google.
I'm currently trying to fix the saturation of camera and I need to learn something new within IDA or hex-editing in order to understand how to do the same change which highwaystar did for his blob.
You can't. You should be able to do such changes on other ROMs, but lineage doesn't have that as far as I can see.
Make sure that:
1) Device tree is in device/huawei/hwcan.
2) Vendor tree in vendor/huawei/hwcan.
3) Kernel source in kernel/huawei/msm8953.
Also, make sure that you've ran:
Code:
. build/envsetup.sh && brunch hwcanYou can also use lunch instead brunch if you want to. If the error still persists even if all those are "matching", then try to run . build/envsetup.sh && lunch and pick a random device. Then run make clean and then try to build for hwcan again.
If you'd like to, I can help you in "real time" if we'll speak on Skype / telegram / IRC.
Regarding adding code in post, you need to use
Code:
code here[ /CODE] (remove the space). It's same for all other tags. You can also add new lines between the tags and the tag will still apply to the new line.
Last edited:
Excuse me . Can i ask u a question .
I want to fake gps . Im a driver . ( Grab company ) .
I installed Magisk . Xposed . Grab Driver app working OK .
But when i install any fake gps app . grab driver check and not working any more . With mock mock location module , grab app not working too ....
Any ideas in my cage ???
I want to fake gps . Im a driver . ( Grab company ) .
I installed Magisk . Xposed . Grab Driver app working OK .
But when i install any fake gps app . grab driver check and not working any more . With mock mock location module , grab app not working too ....
Any ideas in my cage ???
I'm sorry, but I'm not supporting xposed. As a side note, I've just google-ed the module you've mentioned and I read in the thread that it doesn't supports Oreo...
You're using the wrong kernel. I see wireguard in the log, but that's only in cm-14.1 and los15 branches (los15 branch is basically the lineage 14 kernel updated for O).
The correct kernel source (also mentioned in the first post) is this one, the lineage-15.1 branch.
Also, it looks like you're missing python 2 or there's a symlink problem.
PS: if you'd like to or it would be easier for you, check out del.dog, hastebin.com or pastebin.com. You can upload code/log.
Last edited:
Thanks @#Henkate
The kernel was the one from your OP on this, maybe I did something wrong though (might have pulled the wrong one I guess). I will look into that and the python problem. Thanks for the help. Last thing, if I was to build AOSP, what kind of change would the files in the device tree need?
You know @#Henkate is a great person. Mult Respect!!!
The kernel was the one from your OP on this, maybe I did something wrong though (might have pulled the wrong one I guess). I will look into that and the python problem. Thanks for the help. Last thing, if I was to build AOSP, what kind of change would the files in the device tree need?
You know @#Henkate is a great person. Mult Respect!!!
I see. Well, as I've said, I've seen wireguard mentioned in the logs, but I haven't added wireguard to the new kernel (lineage-15.1 branch). Let me know how it goes.
Regarding building AOSP, you'd need to make changes to the makefiles to make it compatible with AOSP (e.g. renaming lineage to AOSP). You can check other (lineage) trees which were "aosp-ified" to get the idea. Once you can start building for hwcan, you'll get build errors which you'd have to fix, by modifying device tree, grabbing missing repos from Lineage's github.or replacing some AOSP repo(s) with lineage one(s).
As far as I know, there's some organization(s) which has the sources for building AOSP and used some lineage repos, but probably it isn't up to date and dunno how many changes there were done.
In my opinion, I wouldn't recommend building AOSP to a beginner. On the other hand, it can be a journey where he'd learn new things. Again, it's only mg opinion. You shouldn't let that influence your choice, at least it wasn't my purpose. If you wanna do it, then do it xD. I can assist regarding that, but not here.
Thank you for your kind words as always!
I wouldn't have expected you to write in Romanian. Multumesc foarte mult! (translation: thank you so much!).
Last edited:
Thank you for your kind words as always!
Thanks, it must be something in the kernel. I will try again starting fresh, in a few days (new term at school started Wang <- teacher). I know to do AOSP I need to rebuild (or at least pick what I need) from what you all have done. Will stop with non-Lineage chat, we have the off topic for that which is not relevant.
Similar threads
Top Liked Posts
-
There are no posts matching your filters.
-
27
LineageOS 15.1 for Huawei Nova CAN-L11
DISCLAIMER:
Code:* Your warranty is now void. * * I am not responsible for bricked devices, dead SD cards, * thermonuclear war, or you getting fired because the alarm app failed. * Please do some research if you have any concerns about features included * before flashing it! YOU are choosing to make these modifications, and if * you point the finger at me for messing up your device, I will laugh at you.
LineageOS is a free, community built, aftermarket firmware distribution of Android 8 (Oreo), 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. Linked below is a package that has come from another Android project that restore the Google parts. 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 out Gerrit Code Review.
What's working:
- Boots
- Wifi
- Bluetooth
- Camera and Camcorder(video recorder)
- Video Playback
- RIL (Calls, SMS, Data)
- Audio ( Recording and Playback )
- Sensors
- Fingerprint
- Notification LED
- FM Radio
- GPS
- NFC
- Hotspot
Known issues:
- some saturation issue in camera while it is focusing (it was present on lineage 14 too)
Requirements
Installation
Download
GITHUB | ANDROIDFILEHOST | MEDIAFIRE
Sources
Donations
You don't have to, but if you like my work and you wish to support the development:
1) PayPal:
https://www.paypal.me/Henkate
https://xdaforums.com/donatetome.php?u=4471434
2) Patreon: https://www.patreon.com/Henkate
3) WeChat: QR code (id Henkate)
I would use the money to upgrade my PC, so i can build with my own PC instead relaying on Google Cloud Platform.
Thank you to all donators!
Donators list:
Credits
@wangdaning
@abhishek987
@Cozzmy13
@javelinanddart
@highwaystar_ru
@BadDaemon
@_dobo
@LuK1337
@mikeioannina
forkbomb - IRC
@Grarak
@gt_o
@crpalmer
@FrozenCow
@franciscofranco
@flar2
@Sultanxda
@zx2c4
@ Google for their cloud platform and free trial
@ LineageOS
@ Huawei
XDA:DevDB Information
[ROM][8.1.0][OTA][UNOFFICIAL] LineageOS 15.1 [15.11.2018], ROM for the Huawei Nova/Nova Plus
Contributors
#Henkate
Source Code: https://github.com/skinzor/android_kernel_huawei_msm8953-1/tree/lineage-15.1
ROM OS Version: 8.x Oreo
ROM Firmware Required: Unlocked bootloader, TWRP
Version Information
Status: Stable
Created 2018-09-04
Last Updated 2018-12-0812New update
NEW UPDATE - 13/10/2018
EDIT: It looks like I've completely forgot to commit and push a change... Basically, I've switched back to the stock libacdbloader so acdbs gets loaded properly (related to audio). That's the change I've forgot to commit and push. You can wait until tomorrow when I'll publish a new build or flash this zip which I've had in my phone.
I'm really sorry for this.
10Here we have the los 15.1 with security patch updated to december. Sorry the lateness. In january I intend to post it ealier.
https://drive.google.com/open?id=1eefYrCY4qsQG8q3tCyXqUumWB05a7dGN9Thanks to @wangdaning!
First of all, let me remind you that this wouldn't have been possible without @wangdaning, at least not from me. He helped me with money to buy a new Nova in order to continue the development. With this occasion, @wangdaning, let me thank you again for trusting and helping me! I really can't thank you enough!
You can dirty flash it over lineage 14, but obviously i don't recommend that.
8NEW UPDATE - 15/11/2018
First, let me remind you again that this is possible thanks to @wangdaning who helped me to get a new Nova. Thank you!
The download links are in the first post. You should get the update through OTA too.
The sources were updated accordingly and you can find them on my github (check the first post).
If you choose to install the new update from OTA, it'll automatically reboot to recovery and install it, so basically it's dirty flashing. Keep in mind that quote though.
CHANGELOG
- synced LineageOS sources
- 5 November 2018 security patch
- enforced selinux and addressed more denials
- switch to BFQ scheduler once phone booted
- added power off alarm support: set an alarm and power off the phone. The phone will turn itself on with 1 minute before the alarm is supposed to ring. According to my tests, the alarm will ring after 30 seconds after the phone booted and lockscreen appeared.
- added Wireguard support
- reverted Huawei's change to qcom,bcl and got in-line with CAF: allow BCL to hotplug 4 cores at 10% battery instead 2 cores at 5%
- enabled Westwood TCP congestion; you can switch to it with e.g. Kernel Adiutor
- added vibration control; you can change it with e.g. Kernel Adiutor
- other misc fixes which you can see in the commit history
What about the other issues?
1. Camera saturation issue - I didn't manage to fix it and today I've asked @highwaystar if he could give me a tip. Instead giving me a tip, he actually said that he can take a look at the blob. So he did that and then he sent me the patched blob, but when I've tried it, the camera saturation issue was still there. I have no idea why it didn't work, but I know that highwaystar patched the blob properly because he has knowledge about this kind of stuff.
2. No audio through speaker for some people - I didn't had time to look more into it.
3.
I didn't had time to look into this neither. If there's any other issue which I've forgot to mention now, well, I didn't had time to look into it neither.
