are there any roms for the N200 5G that would give better performance?
let me know
Try a GSI for now. One specific individual had been cranking on getting a device tree together, and if you have any experience, he could use your help.
rinnycoop121 said:
are there any roms for the N200 5G that would give better performance?
let me know
Click to expand...
Click to collapse
I recommend the CherishOS 12 GSI. It's a good GSI to start with if you're new.
twomad said:
I recommend the CherishOS 12 GSI. It's a good GSI to start with if you're new.
Click to expand...
Click to collapse
ok How do we flash roms on the N200 5G?
rinnycoop121 said:
ok How do we flash roms on the N200 5G?
Click to expand...
Click to collapse
There are multiple tutorials on the internet. Here's an example https://www.droidwin.com/install-android-12-gsi-roms-on-oneplus-nord-n200-5g/
Here is my guide:
GSIs on N200
The process of flashing alone is conventional, shouldn't even need a thread to detail, but still leaving a thread here for search indexing. With an unlocked BL, flash an ARM64 AB GSI within fastbootd, reboot to recovery, format userdata, reboot...
forum.xda-developers.com
Note that I do not recommend GSI's as I cannot get Magisk or VoLTE to work with them.
Custom ROMs will be coming soon, trees have been figured out and kinks are being ironed. More to come in the following days. Stay tuned
elginsk8r said:
Custom ROMs will be coming soon, trees have been figured out and kinks are being ironed. More to come in the following days. Stay tuned
Click to expand...
Click to collapse
great
rinnycoop121 said:
are there any roms for the N200 5G that would give better performance?
let me know
Click to expand...
Click to collapse
There are a few projects in the works. I personally am waiting to sell my current laptop to fund a ryzen 5 5600 dev rig which will allow me to build a larger variety ROMs as I add storage. I have it worked out where the price of my laptop will give me enough to order everything but storage drives. Settling with a single 16GB dimm to maximize upgradability while maintaining the best price to performance ratio currently available.
elginsk8r said:
Custom ROMs will be coming soon, trees have been figured out and kinks are being ironed. More to come in the following days. Stay tuned
Click to expand...
Click to collapse
hey buddy, i seen your trees, looking good. i just got my n200 and am waiting for unlock code. i built your rom with your trees and will flash once i'm unlocked. Thanks for all your hard work! as far as i can see you"re the only one working on n200 (dre9). do you accept pull requests rom and/or device side?
You can submit patches via review.evervolv.com gerrit. I am also on telegram if you have questions (just no eta requests). Kernel has been purged of Linux stable merges to be closer to the caf tag used. Trees are lineage compatible via 2 reverts if anyone wishes to build for lineage
I have a device tree and a kernel tree that can be used to compile LineageOS for the Nord N200. In its current state, only Wi-Fi is not working, which I have not been able to fix.
Because OOS12 came out for this device last week, I have to wait until OP releases the A12 kernel code, which could take anywhere between two and five months.
andr01dfr3ak said:
I have a device tree and a kernel tree that can be used to compile LineageOS for the Nord N200. In its current state, only Wi-Fi is not working, which I have not been able to fix.
Because OOS12 came out for this device last week, I have to wait until OP releases the A12 kernel code, which could take anywhere between two and five months.
Click to expand...
Click to collapse
WiFi is working with @elginsk8r trees. I'll run a build with your trees once I get a chance. I haven't been able to build much as work is crazy busy right now.
rc420head said:
WiFi is working with @elginsk8r trees. I'll run a build with your trees once I get a chance. I haven't been able to build much as work is crazy busy right now.
Click to expand...
Click to collapse
I also have a bunch of stuff on gerrit cleaning up previous issues and further refinement. Message me on telegram @andr01dfr3ak and maybe we can work together to avoid reinventing the wheel.
Not sure, but I got the DL link for the Android 12 OTA update...: " https://android.googleapis.com/packages/ota-api/package/2ae18bc3e36cfe74ae7f1b65d0f817043c57707a.zip "
AboveTG said:
Not sure, but I got the DL link for the Android 12 OTA update...: " https://android.googleapis.com/packages/ota-api/package/2ae18bc3e36cfe74ae7f1b65d0f817043c57707a.zip "
Click to expand...
Click to collapse
I've already started on getting LineageOS to work with the firmware included with this update, but without the kernel source code for said update, I cannot start testing.
In the meantime, my device and kernel trees are on the LineageOS GitHub repository now, so feel free to do unofficial builds and submit changes to the LineageOS Gerrit. You must be on OOS 11 firmware for it to work.
andr01dfr3ak said:
I've already started on getting LineageOS to work with the firmware included with this update, but without the kernel source code for said update, I cannot start testing.
In the meantime, my device and kernel trees are on the LineageOS GitHub repository now, so feel free to do unofficial builds and submit changes to the LineageOS Gerrit. You must be on OOS 11 firmware for it to work.
Click to expand...
Click to collapse
Alright not gonna lie man, im kind of new to all this, but I downgrade with the msm tool and ill try to figure out how to build. I know I need to fork it, but after that I have no clue what to do.
andr01dfr3ak said:
I've already started on getting LineageOS to work with the firmware included with this update, but without the kernel source code for said update, I cannot start testing.
In the meantime, my device and kernel trees are on the LineageOS GitHub repository now, so feel free to do unofficial builds and submit changes to the LineageOS Gerrit. You must be on OOS 11 firmware for it to work.
Click to expand...
Click to collapse
I found a payload dumper on github that works well. I renamed it payloaddumper+ because I felt it fit the tool name better. should work as a portable app I believe. Just run the .exe. Hope this helps.
Related
I am going to be working on a build of Lineage13 for our phone. Thanks to Corvus for the basic source.
Development source: https://github.com/JTS2111/device_le_le_zl1
To-Do (Will add to as I go):
-Get logs from CN users
-Patch kernel for safetynet
-Get a first stable build to give for testing
-Get logs from own phone (US)
-Finish To-Do
Long term To-Do:
-Stability and somewhat decent battery performance
-Completely CTS compatible (that'll be fun)
-Unified .zip for x727 and x720 (might borrow TS scripts)
-Security updates for at least a couple months.
As I get a stable build, I will post it here for testers. Right now, I'm setting up basic debugging for my phone to get the big crashes out of the way.
ETA: Hope to expect a experimental build by the end of the week.
jts2111 said:
I am going to be working on a build of Lineage13 for our phone. Thanks to Corvus for the basic source.
Development source: https://github.com/JTS2111/device_le_le_zl1
To-Do (Will add to as I go):
-Get logs from CN users
-Patch kernel for safetynet
-Get logs from own phone (US)
-Finish To-Do
As I get a stable build, I will post it here for testers. Right now, I'm setting up basic debugging for my phone to get the big crashes out of the way.
Click to expand...
Click to collapse
On behalf of all the owners of the Le Pro 3, thank you for taking the time to make a ROM for us :good:
Added long-term To-Do and tweaking build environment.
jts2111 said:
Added long-term To-Do and tweaking build environment.
Click to expand...
Click to collapse
Hi jts, I'm working on this fork too, just working on getting a fully automated vagrant setup. I'm working on a windows machine, and it's become painfully obvious windows 10 bash (a lovechild of ubuntu and windows 10) is garbage and doesn't work for literally anything you might need bash for. Setting up virtualbox is a pain in the ass. And at the end of the day, if you setup ubuntu, and need to change things for some other build, you might break your current build. I'll keep you posted.
robertzas said:
Hi jts, I'm working on this fork too, just working on getting a fully automated vagrant setup. I'm working on a windows machine, and it's become painfully obvious windows 10 bash (a lovechild of ubuntu and windows 10) is garbage and doesn't work for literally anything you might need bash for. Setting up virtualbox is a pain in the ass. And at the end of the day, if you setup ubuntu, and need to change things for some other build, you might break your current build. I'll keep you posted.
Click to expand...
Click to collapse
Bash on Ubuntu on Windows is only good for basic operations. And I'm actually just starting another Ubuntu VM. No old builds broken. Though its good to have someone to exchange code with.
I already have ~95% working builds of 13 & 14. I have issues with some missing sensors in 13 and camera problems in 14.1.
Sent from my ASUS_Z008 using Tapatalk
Cannot wait to try out this one. While we have two other CM roms, development progress of those seem to have stopped. I was disappointed then this happened. I thank you for those involved in it.
jrior001 said:
I already have ~95% working builds of 13 & 14. I have issues with some missing sensors in 13 and camera problems in 14.1.
Sent from my ASUS_Z008 using Tapatalk
Click to expand...
Click to collapse
Can't wait to try it
Many thanks for your work :good:
Good luck with this! Cant wait!!!
Only for a summery.
We have to get the source code for camera and the other stuff is ready? Or not so difficult?
So definetly possible to geht a stable rom
And i saw that there are more people in this thread who are working in lineage OS. Do you work togetjer? I hope so Then its easier for you all :highfive:
And a little question for a dev noop If we have lineage 13, is it a long and complete new way to delvelope lineage 14.1 or is it similar and not tooo difficult?
manuelbvb said:
Only for a summery.
We have to get the source code for camera and the other stuff is ready? Or not so difficult?
So definetly possible to geht a stable rom
And i saw that there are more people in this thread who are working in lineage OS. Do you work togetjer? I hope so Then its easier for you all :highfive:
And a little question for a dev noop If we have lineage 13, is it a long and complete new way to delvelope lineage 14.1 or is it similar and not tooo difficult?
Click to expand...
Click to collapse
Camera is fine on 13. Just some config stuff I'm fixing. I'm at the moment not working with anyone else, though it would be easier. In terms of 14.1, look at the omniROM 7.1. We would have the same issues with camera and sensors due to the lack of libs.
Also, as a status update, the ROM is very stable with CTS most likely to work with Magisk. Will post soon as I build it.
jts2111 said:
Camera is fine on 13. Just some config stuff I'm fixing. I'm at the moment not working with anyone else, though it would be easier. In terms of 14.1, look at the omniROM 7.1. We would have the same issues with camera and sensors due to the lack of libs.
Also, as a status update, the ROM is very stable with CTS most likely to work with Magisk. Will post soon as I build it.
Click to expand...
Click to collapse
The only major issue I have is with sensors currently on 13 branch. I've got a few missing I can't seem to get working proper. I'm sure there's other minor things but sensors is my only major hurdle right now.
Sent from my LeEco Le Pro3 using Tapatalk
@jts2111 and @jrior001
Which sensors are not working?
corvus said:
@jts2111 and @jrior001
Which sensors are not working?
Click to expand...
Click to collapse
Proximity and compass are the ones giving me trouble on lineage13.
Sent from my LeEco Le Pro3 using Tapatalk
jrior001 said:
Proximity and compass are the ones giving me trouble on lineage13.
Sent from my LeEco Le Pro3 using Tapatalk
Click to expand...
Click to collapse
Proximity works for me, at least the sensor is detected and it changes using any app that tests the sensors (cpuz or aide).
About orientation, I didn't test it so I can't say anything.
If you updated sources from Lineage in the last days, bear in mind that the sources could be broken.
Update: Broken VM environment and source setup. Will try to set up a new Ubuntu ENV. and get a build up soon.
Just for info...
Device tree:
https://github.com/LineageOS/android_device_leeco_zl1
Kernel:
https://github.com/LineageOS/android_kernel_leeco_msm8996
Code review:
https://review.lineageos.org/
codeworkx said:
Just for info...
Device tree:
https://github.com/LineageOS/android_device_leeco_zl1
Kernel:
https://github.com/LineageOS/android_kernel_leeco_msm8996
Code review:
https://review.lineageos.org/
Click to expand...
Click to collapse
Thank you for these infos :good:
Hope more ROMs for Le Pro 3 :fingers-crossed:
Le Pro 3 is listed here: https://devs-lab.com/lineageos-supported-device-rom-download.html#LineageOS_ROMs_for_other_devices
Which Rom did they link? Someone from here or who made this rom?
manuelbvb said:
Le Pro 3 is listed here: https://devs-lab.com/lineageos-supported-device-rom-download.html#LineageOS_ROMs_for_other_devices
Which Rom did they link? Someone from here or who made this rom?
Click to expand...
Click to collapse
It's chako67's test build (https://forum.xda-developers.com/le-pro3/development/lineageos-13-t3548926)
First of all, yes, we can now run 64bits ROM on our phone.
But actually we have to run app_process (system server) as 32bits, mainly cause of sensors non working actually with a 64bits system server.
More to come next, vendor tree is still missing many 64bits blobs, and some of our proprietary services still run in 32bits mode too.
What's needed:
Device Tree : https://github.com/BoulzorROM/android_device_motorola_potter/tree/bzr-64bich
Kernel Tree : https://github.com/BoulzorROM/android_kernel_motorola_msm8953/tree/bzr-64bich
Vendor Tree : https://github.com/boulzordev/android_vendor_motorola_potter/tree/bzr-64bich
Check commits history of those repos to grab needed changes.
A 64bits TWRP is available here : https://drive.google.com/file/d/1RQL-RaZh5BeBq8ARg8EBrvma4RtnhGtk/view?usp=sharing (mandatory to flash 64bits ROM)
A 64bits MultiROM TWRP is available here : https://drive.google.com/open?id=0B6-Tz_7kDyxsNGp2V2ZBRV9TV1U (thx to @GtrCraft)
BoulzorROM is available here : https://drive.google.com/file/d/1AQxlUSxrzH1Sq6L5c_ItZI_qtihfUUtM/view?usp=sharing
Validus is available here : https://drive.google.com/open?id=1-aNOD0ef3a1hqnUEeDaNs0GSgKMFBVgy (thx to @GtrCraft)
Some ROMs are almost ready to be shared here soon, stay tuned !
FAQ :
Q : I have an error regarding armv8-a not supported
A : Switch TARGET_2ND_ARCH_VARIANT to armv7-a-neon
Wow! Impressive... Exceeding Motorola/Lenovo in making firmware for their phones! [emoji106]
Subscribed. This is epic!!!
so what do testers say?
my g5+ is still locked and I am too busy to unlock flash and test but 64bit rom may be worth time
Added Validus and MultiROM to the list.
No amount of thanks will be enough for this. I seriously want to donate but I am a student with nothing to donate with. But man!! Thanks!!
The boulzor rom is nougat or oreo?
skooter32 said:
The boulzor rom is nougat or oreo?
Click to expand...
Click to collapse
It is oreo, as i tested it it works nice
Nevermind, thanks @vache!
Tysm Vache ... Best Dev I have ever seen .... Blessed to buy Moto G5 Plus and now I won't regret that I couldn't Buy Moto G5S Plus as it doesn't have any Development ONN!!
ckret said:
so what do testers say?
my g5+ is still locked and I am too busy to unlock flash and test but 64bit rom may be worth time
Click to expand...
Click to collapse
You definitely need to plan some alone time with your phone. For everything that it does for you do not neglect it. Don't you think your phone wants a 64-bit ROM just like all the other flagships.. so yes definitely set aside some time unlock your bootloader flash TWRP and get this ROM. Don't forget we are on arm64 gapps
Sent from my XT1687 using Tapatalk
So, some people here trying to take me down. You win. I can't handle haters anymore. Let us show how you can do better things
If you're maintainer, fork 64bits repos asap, i'll delete boulzordev potter repos tomorrow, as well as BoulzorROM org.
Happy flashing and happy #64bich
Cya.
vache said:
So, some people here trying to take me down. You win. I can't handle haters anymore. Let us show how you can do better things
If you're maintainer, fork 64bits repos asap, i'll delete boulzordev potter repos tomorrow, as well as BoulzorROM org.
Happy flashing and happy #64bich
Cya.
Click to expand...
Click to collapse
But sir why??? The normal people around know who does the hard work in bring up the device tree, etc.....why let one egotistic brat think he owns the world because he can do a repo sync of and already build devicee tree and sources....most of us know who does the hard work...just ignore the krackflashers...
Sir i sold my Pixel because you were here turning my cheap moto g5 wit sd625 into a pixel....
You even covered for Lenovos incompetence & brought 64bit to a 32 bit device...thats next level dedication..why leave that bc of some ignorant self-righteous prick....ur letting em win...
vache said:
So, some people here trying to take me down. You win. I can't handle haters anymore. Let us show how you can do better things
If you're maintainer, fork 64bits repos asap, i'll delete boulzordev potter repos tomorrow, as well as BoulzorROM org.
Happy flashing and happy #64bich
Cya.
Click to expand...
Click to collapse
With all due respect sir, you're the only reason I bought phone.. I'm seriously not kidding... The specs didnt matter.. development from a person like you did... Please don't abandon us... We always know you're the guy who does the hard work... I'm sure the guys who try to bring you down can do nothing without you.. Please have a change of heart
Sent from my XT1686 using Tapatalk
vache said:
So, some people here trying to take me down. You win. I can't handle haters anymore. Let us show how you can do better things
If you're maintainer, fork 64bits repos asap, i'll delete boulzordev potter repos tomorrow, as well as BoulzorROM org.
Happy flashing and happy #64bich
Cya.
Click to expand...
Click to collapse
w the hell? I am sorry that trolls trying to ruin your day.
thanks for the work you have done on maintaining this device
I bought you some beer
market88 said:
Sorry for noob question. What's the advantage of using 64-bit from? Thank you
Click to expand...
Click to collapse
You get to use the Camera NX app from the Nexus 5x with Zero-lag-shutter and HDR+ on this phone now.
Rom is smooth af too.
CreasingMass Dev said:
You get to use the Camera NX app from the Nexus 5x with Zero-lag-shutter and HDR+ on this phone now.
Rom is smooth af too.
Click to expand...
Click to collapse
Not everything is working, at least what I tried. Slowmo crashes the app and panorama as well. What is the version you are using?
CreasingMass Dev said:
You get to use the Camera NX app from the Nexus 5x with Zero-lag-shutter and HDR+ on this phone now.
Rom is smooth af too.
Click to expand...
Click to collapse
Which ROM you flashed?
Vache if you keep building and need any speedy build hardware let me know, I can give some ssd VM space on my 3.9ghz 1700 lol. Love the work, ignore the plebs. Still looking for that paypal link btw
karlmorgan92 said:
Not everything is working, at least what I tried. Slowmo crashes the app and panorama as well. What is the version you are using?
Click to expand...
Click to collapse
i haven't tested slowmo nor panorama in the app (i never use that) but everything else is working for me, i'm using this one https://drive.google.com/open?id=1zg3J0_NIccghtdj3nKuyyuHKs5VEegxh
market88 said:
Which ROM you flashed?
Click to expand...
Click to collapse
BoulzorROM, the one in OP with nano 8.0 arm64 opengapps and supersu
CreasingMass Dev said:
i haven't tested slowmo nor panorama in the app (i never use that) but everything else is working for me, i'm using this one https://drive.google.com/open?id=1zg3J0_NIccghtdj3nKuyyuHKs5VEegxh
BoulzorROM, the one in OP with nano 8.0 arm64 opengapps and supersu
Click to expand...
Click to collapse
Is video recording buggy? I might try this out later..
ROM Lineage 15.1 unofficial. Built with latest GCC+ compiler.
All credits go to Lineage team.
Download Link
https://www.androidfilehost.com/?fid=818070582850505463
XDA:DevDB Information
Lineage 15.1 Unofficial, ROM for the Nexus 6
Contributors
Rondeau79
Source Code: https://github.com/LineageOS/android
ROM OS Version: 8.x Oreo
ROM Kernel: Linux 3.4.x
ROM Firmware Required: Unlocked bootloader ,latest TWRP
Version Information
Status: Stable
Created 2018-04-03
Last Updated 2018-04-03
Or you just use the official version here:
https://download.lineageos.org/shamu
does it force encrypt the phone?
mahir555 said:
does it force encrypt the phone?
Click to expand...
Click to collapse
Yes (as every official version), but you can flash the FED-Patcher to disable it. Just flash it right after LOS.
Maybe Magisk will do the trick too.
Render issue upon booting
After the booting finishes and lock screen appears, there is a pop-up saying vendor image not up to date..i understood that it wants me to install the last available factory image from google site but I was not able to successfully do it..help please!
aradhya10 said:
After the booting finishes and lock screen appears, there is a pop-up saying vendor image not up to date..i understood that it wants me to install the last available factory image from google site but I was not able to successfully do it..help please!
Click to expand...
Click to collapse
It's just a pop up. Shamu does not have a vendor image.
Go forward, it will work
gothy.gothy said:
It's just a pop up. Shamu does not have a vendor image.
Go forward, it will work
Click to expand...
Click to collapse
Except there is exclamation point notification in upper L hand corner which says "You might be a victim of software counterfeiting" and no way to cancel it.
HueyT said:
Except there is exclamation point notification in upper L hand corner which says "You might be a victim of software counterfeiting" and no way to cancel it.
Click to expand...
Click to collapse
In terminal adb/ recovery or app shell terminal:
Setprop persist.lineage.nofool true
That will fix that annoying notification.
toto-w said:
Or you just use the official version here:
https://download.lineageos.org/shamu
Click to expand...
Click to collapse
April fool's joke is terrible.
TheGreatess1223 said:
April fool's joke is terrible.
Click to expand...
Click to collapse
The official build is dated April 2nd, did the Lineage team REALLY still make an April fool's day build? Lol
H4X0R46 said:
The official build is dated April 2nd, did the Lineage team REALLY still make an April fool's day build? Lol
Click to expand...
Click to collapse
yes. yes they did. the dirty rat bastards
H4X0R46 said:
The official build is dated April 2nd, did the Lineage team REALLY still make an April fool's day build? Lol
Click to expand...
Click to collapse
Yes and have not released a updated yet. Lol
There is the 4/12/18 15.1 version available.
Sent from my Nexus 6 using Tapatalk
@Rondeau79
Now that we have official builds I think this thread doesn't make much sense anymore.
Can you please delete it?
@Rondeau79
Unfortunately, you currently seem to be the Rodney Dangerfield of XDA for Shamu. For those unfamiliar, Rodney Dangerfield is a comedian who is known for the catchphrase, "I get no respect." First with DU and now with LOS, you are asked to discontinue your threads and builds.
Just for the record, I'm not criticizing you, or DU and LOS! I understand the situation and reasoning behind why these requests were made.
I've used some of your builds on both my Hammerhead and Shamu. I have a great appreciation for those who build roms for those who cannot. So, I thank you for both your effort and sharing your work. Most recently, I used your Omni Nougat build and it was solid. From what I've read on Omni's G+, they are never going to make Shamu official for Oreo. So, maybe Omni would be a good rom for you to build unofficially.
Omni has always been a pretty innovative rom, I think there would be decent interest here in the Shamu community. Anyway, just a thought.
Thanks,
Mike T
webdroidmt said:
@Rondeau79
Unfortunately, you currently seem to be the Rodney Dangerfield of XDA for Shamu. For those unfamiliar, Rodney Dangerfield is a comedian who is known for the catchphrase, "I get no respect." First with DU and now with LOS, you are asked to discontinue your threads and builds.
Just for the record, I'm not criticizing you, or DU and LOS! I understand the situation and reasoning behind why these requests were made.
I've used some of your builds on both my Hammerhead and Shamu. I have a great appreciation for those who build roms for those who cannot. So, I thank you for both your effort and sharing your work. Most recently, I used your Omni Nougat build and it was solid. From what I've read on Omni's G+, they are never going to make Shamu official for Oreo. So, maybe Omni would be a good rom for you to build unofficially.
Omni has always been a pretty innovative rom, I think there would be decent interest here in the Shamu community. Anyway, just a thought.
Thanks,
Mike T
Click to expand...
Click to collapse
I know who Rodney Dangerfield is/was. I can build ROM's fairly well, it took 2 years for me on and off to get CM built. I first started rooting and flashing with a low end Metro PCS phone and I finally got my hands on Hammerhead. I have flashed hundreds of different ROM's and kernels over the years. Back in the days at another forum I used to see official and unofficial builds all the time. If people have an issue with my builds then why is everything so called open source. I guess the old school grassroots base of custom ROM's allure is over. I the problem I face is no one will help me with the programing part of github and what it takes to work out the coding. To any device maintainer that could lend a a helping hand that would be great. I will leave this thread open for a few more days.
@Elektroschmock I really didn't think it would have been such an issue. I get it takes a lot of work to do this, but how is anyone supposed to learn anything without trying it themselves. If I have offended anyone then I apologise.
I personally love UNOFFICIAL builds and don't see any harm especially since OFFICIAL builds can be just as unpredictable and/or unavailable
Rondeau79 said:
I know who Rodney Dangerfield is/was. I can build ROM's fairly well, it took 2 years for me on and off to get CM built. I first started rooting and flashing with a low end Metro PCS phone and I finally got my hands on Hammerhead. I have flashed hundreds of different ROM's and kernels over the years. Back in the days at another forum I used to see official and unofficial builds all the time. If people have an issue with my builds then why is everything so called open source. I guess the old school grassroots base of custom ROM's allure is over. I the problem I face is no one will help me with the programing part of github and what it takes to work out the coding. To any device maintainer that could lend a a helping hand that would be great. I will leave this thread open for a few more days.
@Elektroschmock I really didn't think it would have been such an issue. I get it takes a lot of work to do this, but how is anyone supposed to learn anything without trying it themselves. If I have offended anyone then I apologise.
Click to expand...
Click to collapse
It's only because this is confusing users. I get so many logs from users thinking they use lineage but they're using some custom, inofficial homebrew build.
toto-w said:
Yes (as every official version), but you can flash the FED-Patcher to disable it. Just flash it right after LOS.
Maybe Magisk will do the trick too.
Click to expand...
Click to collapse
Does the fadpatcher survice lineage updates or do i need to apply it each and every time?
DDQW said:
Does the fadpatcher survice lineage updates or do i need to apply it each and every time?
Click to expand...
Click to collapse
In the meantime I found out that Magisk modifies the force encryption flag too and Magisk survives OTA updates.
So I have successfully built OmniRom 8.1 Oreo for Shamu the zip file is a little over 500mb. The package flashes correctly but fails to boot. I have already tried to change the BoardConfig.mk file to be SeLinux=Permissive but it still fails to boot. My device is decrypted as well. What could be a source of the non boot issue other than what I have mentioned. This project is taking quite some time to complete.
HELP!!!!!
Does omnirom even have a 8.1 branch for shamu? I can't see it.
Elektroschmock said:
Does omnirom even have a 8.1 branch for shamu? I can't see it.
Click to expand...
Click to collapse
No it doesn't I am trying to bring it up, I know they don't officially support it for Oreo. They don't have a device maintainer for Shamu anymore. I have been using other device trees and filling in the required files for building Omni. Like I said I can get a successful build but in won't boot.
Rondeau79 said:
No it doesn't I am trying to bring it up, I know they don't officially support it for Oreo. They don't have a device maintainer for Shamu anymore. I have been using other device trees and filling in the required files for building Omni. Like I said I can get a successful build but in won't boot.
Click to expand...
Click to collapse
Well thats not how a bringup works. You need a ****load oft kernel and device commits for shamu to Boot Oreo.
The easiest way would be forking a working device and kernel repository...e.g. LineageOS. Next step would be adapting some makefiles and overlays.
Not much to do, as we have already done the Oreo bringup months ago.
Elektroschmock said:
Does omnirom even have a 8.1 branch for shamu? I can't see it.
Click to expand...
Click to collapse
Elektroschmock said:
Well thats not how a bringup works. You need a ****load oft kernel and device commits for shamu to Boot Oreo.
The easiest way would be forking a working device and kernel repository...e.g. LineageOS. Next step would be adapting some makefiles and overlays.
Not much to do, as we have already done the Oreo bringup months ago.
Click to expand...
Click to collapse
Yeah that's what I did. When the build first starts something in the vendor folder isn't being globed. It's only 99% of that folder that is accounted for. The build is successful but it just won't boot. I don't have much coding experience so this is really hard.
Rondeau79 said:
Yeah that's what I did. When the build first starts something in the vendor folder isn't being globed. It's only 99% of that folder that is accounted for. The build is successful but it just won't boot. I don't have much coding experience so this is really hard.
Click to expand...
Click to collapse
Do an -eng build and read logcat and dmesg via ADB. Usually you see whats wrong.
Rondeau79 said:
Yeah that's what I did. When the build first starts something in the vendor folder isn't being globed. It's only 99% of that folder that is accounted for. The build is successful but it just won't boot. I don't have much coding experience so this is really hard.
Click to expand...
Click to collapse
Hey how's it going? I know you've been trying hard to get an 8.1 Omni build running. FYI, @bthorne79 put out an Omni 8.1 build for Shamu back in December of last year. I tried it at the time and it was a nice build but if I remember correctly, the theming didn't work. I tried changing to a dark theme but it just stayed on default light theme. I always use a dark or black theme on Shamu and I'd rather not have to use substratum. Other than that, the rom ran very well.
Maybe give him a shout, after all you both have 79 in your name. Good luck, I definitely wouldn't mind seeing an Omni 8.1 build.
Mike T
webdroidmt said:
Hey how's it going? I know you've been trying hard to get an 8.1 Omni build running. FYI, @bthorne79 put out an Omni 8.1 build for Shamu back in December of last year. I tried it at the time and it was a nice build but if I remember correctly, the theming didn't work. I tried changing to a dark theme but it just stayed on default light theme. I always use a dark or black theme on Shamu and I'd rather not have to use substratum. Other than that, the rom ran very well.
Maybe give him a shout, after all you both have 79 in your name. Good luck, I definitely wouldn't mind seeing an Omni 8.1 build.
Mike T
Click to expand...
Click to collapse
Yeah this project has been a real headache! Nothing like before were most of the files and programming has been done. I am not done yet, I don't give up too easy. This has been quite an undertaking.
Follow this thread: https://forum.xda-developers.com/showpost.php?p=54118631&postcount=4
That'll give you an idea about what all things to consider while building for a device :fingers-crossed:
Nitin
Rondeau79 said:
Yeah this project has been a real headache! Nothing like before were most of the files and programming has been done. I am not done yet, I don't give up too easy. This has been quite an undertaking.
Click to expand...
Click to collapse
If you push your sources somewhere where we can see it, it should be easier for us to help you.
nitin.chobhe said:
Follow this thread: https://forum.xda-developers.com/showpost.php?p=54118631&postcount=4
That'll give you an idea about what all things to consider while building for a device :fingers-crossed:
Nitin
Click to expand...
Click to collapse
Yeah that guide is so outdated! I followed that kind of stuff years ago when I couldn't build from source. I have done many builds that boot for 3 devices. This is a different problem.
Elektroschmock said:
If you push your sources somewhere where we can see it, it should be easier for us to help you.
Click to expand...
Click to collapse
Yeah I am using Omni ROM source with device trees and kernel source from Lineage Oreo. I have modified files and make sources. I have all up to date vendor blobs cloned. There is no build errors just an issue with the system not booting. Pushing my source upstream would be to my personal GitHub account which I have never had to do. Usually I repo/clone source build and upload to Android File Host for working zips. I have never pushed anything up from my laptop!
Rondeau79 said:
Yeah that guide is so outdated! I followed that kind of stuff years ago when I couldn't build from source. I have done many builds that boot for 3 devices. This is a different problem.
Click to expand...
Click to collapse
Even though it is outdated it is still very much applicable. I linked that thread because you mentioned this.
Good that you know the problem. All the best!
Nitin
Rondeau79 said:
Yeah I am using Omni ROM source with device trees and kernel source from Lineage Oreo. I have modified files and make sources. I have all up to date vendor blobs cloned. There is no build errors just an issue with the system not booting. Pushing my source upstream would be to my personal GitHub account which I have never had to do. Usually I repo/clone source build and upload to Android File Host for working zips. I have never pushed anything up from my laptop!
Click to expand...
Click to collapse
It's not that you need to push it somewhere to get working zips, it's just for us to see your modifications.
Otherwise it is just guessing what you did.
Making it compile is one thing...making it work is a whole different story. When I did the Lineage Oreo bringup I had many things to fix untill it bootet properly.
Lineage's device tree for shamu depends on several other Lineage repositories. For example:
android_hardware_lineage_interfaces
android_hardware_qcom_gps
android_vendor_lineage
android_device_lineage_sepolicy
So just cloning the device repo without examining the reason for your 'bootloop' will get you nowhere.
I'd suggest you to do an engineering build which is easier to debug. Altought I would make this build permissive as selinux denials are a common reason for a bootloop.
How about trying a known working kernel such as popcorn? If the kernel works, you might be able to get some logs. And if you know whether your kernel is the problem, you are one step closer.
runekock said:
How about trying a known working kernel such as popcorn? If the kernel works, you might be able to get some logs. And if you know whether your kernel is the problem, you are one step closer.
Click to expand...
Click to collapse
If he is based of lineage's device tree, then Lineage's kernel is the best choice.
You should always be able to grab a log, no matter which kernel you are using.
Yeah willing to help out put your stuff up on git and give links
My webhost is down right meow but I can post my Oreo build I had of Omni here I didn't use Los trees i used aosp trees from camcory , joryb and mine cleanos
---------- Post added at 08:47 PM ---------- Previous post was at 08:28 PM ----------
i found my build i had it on afh if you want it to try this was early oreo so some things not fully functional i think gps was iffy https://www.androidfilehost.com/?fid=889964283620775520 i am syncing up omni oreo again for sure will help out if you want please pm
---------- Post added at 08:47 PM ---------- Previous post was at 08:47 PM ----------
nougat builds in that root folder also
bthorne79 said:
Yeah willing to help out put your stuff up on git and give links
Click to expand...
Click to collapse
My device and kernel tree GitHub link.
https://github.com/Rondeau79
Rondeau79 said:
My device and kernel tree GitHub link.
https://github.com/Rondeau79
Click to expand...
Click to collapse
Your probably going to want to fork the toolchains over that was used with cleanaosp
<!-- Prebuilts --> <project path="prebuilts/gcc/linux-x86/arm/arm-eabi-4.9" name="joryb/arm-eabi-7.x" clone-depth="1" remote="bb" revision="master"/> <project path="prebuilts/gcc/linux-x86/arm/arm-linux-androideabi-4.9" name="joryb/arm-linux-androideabi-7.x" clone-depth="1" remote="bb" revision="master"/>
Built for fun, will maintain until LOS officially supports?
Also it is BETA, so expect bugs maybe.
I'm skipping 90% of words here because if you are here I assume you know what you are doing. And you can either Google, use the search button, or ask.
This is a private work of mine, that I use normally on my spare device. Supported as is.
Disclaimer:
Not responsible for any injuries you do to yourself or your device being damaged caused by this ROM.
Known issues:
Initial Setup for Google is buggy, keep hitting back and retrying works.
INSTRUCTIONS
Clean Flash
Download The ROM & GApps (pick latest one in drive, I use opengapps)
Wipe: System, Data, Dalvik, Cache
Flash ROM + GApps
Reboot & Enjoy
Dirty Flash
Download the ROM
Wipe: Dalvik and Cache
Flash ROM (+Magisk if rooted previously or if want root)
Reboot & Enjoy
Download Folder Link:
https://drive.google.com/open?id=1GIhp9B0rg5Z8lHDz5RIzm-gX4U_XbTHK
Device and Kernel Source:
https://github.com/LineageOS/android_device_oneplus_bacon
https://github.com/KiDwayne/bacon
Contact and Join the group!
https://discord.gg/zB3ubnj
Credits to:
LineageOS Team
@franciscofranco
Join My Discord for discussions!
https://discord.gg/zB3ubnj
Changelog for 07FEB build:
Notification LED works! (Thanks to @dar2q) (might require clean flash to work, do tell)
Updated to Febuary Security!
How stable is LOS16.0 for bacon if this is build straight from source? I saw initial device list in gerrit and still don't see bacon there, maybe it's still too buggy? Can't test it now because I'm away from home
LTMendarynas7 said:
How stable is LOS16.0 for bacon if this is build straight from source? I saw initial device list in gerrit and still don't see bacon there, maybe it's still too buggy? Can't test it now because I'm away from home
Click to expand...
Click to collapse
Other than Setup Wizard being a little buggy God knows why, I use it for Youtube and some work related stuff at home. Pretty fine I guess? I also maintain Oneplus2, I would say Pie is already quite stable.
KiD3991 said:
Other than Setup Wizard being a little buggy God knows why, I use it for Youtube and some work related stuff at home. Pretty fine I guess? I also maintain Oneplus2, I would say Pie is already quite stable.
Click to expand...
Click to collapse
Good to know, still impressed that bacon survived 6 major android versions from kitkat to pie..maybe somebody will support it when Q hits us..who knows. btw ty for shearing unofficial build
Thanks for sharing and all the efforts... Can you please confirm that NFC works on this build (tag reading, GPay, etc.)? aptX support? Ant+ support?
mixmax_dp said:
Thanks for sharing and all the efforts... Can you please confirm that NFC works on this build (tag reading, GPay, etc.)? aptX support? Ant+ support?
Click to expand...
Click to collapse
NFC works. APTx I am not sure as I don't use that. My cheapo bluetooth device doesnt support it themselves.
Great job！
Thanks for the build man, keep up the good work! Just wanted to ask, is SELinux enforcing on this build? Thanks!
I don't want to be that guy but where are the links to the sources you used?
Hey there, thanks for this build! Out of curiosity, did you compile it using TheMuppets' proprietary blobs?
CedArctic said:
Thanks for the build man, keep up the good work! Just wanted to ask, is SELinux enforcing on this build? Thanks!
Click to expand...
Click to collapse
yes it is. As it is basically pure los.
eiwarmer said:
I don't want to be that guy but where are the links to the sources you used?
Click to expand...
Click to collapse
Updated! Thanks for the heads up!
Tomoms said:
Hey there, thanks for this build! Out of curiosity, did you compile it using TheMuppets' proprietary blobs?
Click to expand...
Click to collapse
Yeah, is there something I should know. D:
KiD3991 said:
Yeah, is there something I should know. D:
Click to expand...
Click to collapse
Not at all, don't worry! I'm building LineageOS 16 for the first time today and I've just learnt that, instead of pulling the proprietary files from a pre-existing build running on my phone (as the LineageOS wiki suggests), many use TheMuppets' repos. So I've decided to try, and I asked you because I wanted to know if you used them and faced any issues or not.
Tomoms said:
Not at all, don't worry! I'm building LineageOS 16 for the first time today and I've just learnt that, instead of pulling the proprietary files from a pre-existing build running on my phone (as the LineageOS wiki suggests), many use TheMuppets' repos. So I've decided to try, and I asked you because I wanted to know if you used them and faced any issues or not.
Click to expand...
Click to collapse
The day I knew TheMuppets. Never went back. Hahaha
KiD3991 said:
yes it is. As it is basically pure los.
Click to expand...
Click to collapse
wow.. downloading bro thanks
Does your build LED notification light work or not?
Cuz I also build los 16 from source yesterday, but LED not working..
I started build my personal los16 since January,it never got booted until 20th Jan the maintainer push tons of commit.
Sent from my OnePlus3T using XDA Labs
Goog job @KiD3991,
This is not my daily driver but, so far so smooth, I appreciate the work
Leicxan said:
Does your build LED notification light work or not?
Cuz I also build los 16 from source yesterday, but LED not working..
I started build my personal los16 since January,it never got booted until 20th Jan the maintainer push tons of commit.
Sent from my OnePlus3T using XDA Labs
Click to expand...
Click to collapse
The LED's not working on my personal builds as well, however it works if I boot with permissive SELinux (set via the kernel cmdline) using this zip.
I'm pretty sure the culprit is this commit: https://github.com/LineageOS/androi...mmit/b1a798b50807a6c8b27658eeab323dc6a795f184
Thank you for the build, very solid, good battery life, daily driver material. Led not working, using black theme, however notification is white, setup wizard is buggy as stated, but everything on it is pretty awesome! Thanks again! If you could add screenshot function on to buttons, that would be lovely.
As of now I think SELinux I will let it stay Enforced, unless the LED is requested more. Will start a poll I guess?