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)
Related
ALL WORK HAS MOVED TO THE 3.4 BRINGUP. YES, THAT MEANS 3.4 IS BOOTING AND WIP AND THIS KERNEL IS NOW DEPRECATED! CLICK HERE TO VIEW 3.4 PROGRESS
Check latest posts for updates
As you may be aware, we've been trying unsuccessfully to boot Nvidia's 3.4 kernel for tegra 3 on grouper.
Progress has pretty much halted, as this project needs to be finished before we have any hope of 3.4 ever working.
SAUCES
-
WE ALSO HAVE A GITHUB ORGANIZATION
What is this?
An attempt to get Google's ludicrously outdated grouper 3.1 kernel up-to-date with Nvidia's 3.1 kernel.
Why?
1) It'll be, put simply, "better" than Google's out-of-date kernel (...potentially)
2) This *must* be completed before work on 3.4 goes ahead
3) Hopefully other kernels, such as franco's, could be merged with this
How?
I did a "git rev-list" of Nvidia's branch, then Google's branch, all the way back to the point where Google added grouper support (Around March 2012), then diffed the result. I've attached the files in this post: The commits in the diff which have a + next to them are Nvidia's commits, as these are not present in Google's log. I simply need to cherry-pick all 1,699 of these, and make sure to manually update the grouper board files exactly as Nvidia's dev. boards are updated (because of course grouper itself is not updated at all in Nvidia's source). Then I need to fix all the compilation errors. If I get through around 50 - 80 commits a day, and fix the compilation errors the next day, I should be finished in 2 months max. Then serious 3.4 work can begin.
Should I use it?
From a user's perspective, in all honesty, no. This is a) a WIP and b) a means to another end (3.4). Other offerings such as franco's kernel are so far more improved than Google's anyway that this will not be necessarily "better" than those simply due to a load of updates from Nvidia. What *will* make this useful is if the final product is merged, as I said, into existing kernels, thus improving those. That said, I'll never upload a new version before having tested it myself, so you can be in the very least assured that it'll boot and run.
HOWEVER it would be extremely useful if you could run this simply for testing purposes. All my trust is placed in Nvidia's commits and my own ability to fix conflicts and compilation errors. Things may go wrong and your help would be massively appreciated.
Shutupandletmeflash!!!
I'll post updates regularly as possible here. I've used agnostic as it's fantastic. The naming scheme is: Alpha whilst I'm still cherry-picking, Beta once that's done and we're testing to fix bugs, then RC once its in a stable, releasable state (there'll probably only be 1 RC, then no more work); The numbering is x.y where x indicates major release (0 is Alpha, 1 will be Beta) and y will be increment by 1 on every single release.
Credits
@sgt. meow
Nvidia
Google
Asus
@legolas93 for F2FS
@frantisek.nesveda for agnostic-kernel
Anyone else I've forgotten (sorry, it's a while since I opened the 3.4 discussion thread)
XDA:DevDB Information
linux-tegra-nv-3.1-grouper, Kernel for the Nexus 7
Contributors
HTCDreamOn, Ziyan, n1kolaa, sgt. meow
Source Code: https://github.com/Ziyann/android_kernel_asus_grouper
Kernel Special Features:
Version Information
Status: No Longer Updated
Created 2014-11-23
Last Updated 2015-06-07
FAQ
Q: Why is TricksterMod/ CPUSpy/etc. Not showing 1300MHz?
A: read this post.
GREAT! :good:
Its great to see people giving attention to an old device.
I will look forward to it.
What you forgot me
You know moral support!!
Lol J/K
Good thing you put it in original development
That will help.
So keep up the... Hmm dont know how to express it....
Your doing an beyond awesome job!
Maaayyybeeee Google will update the grouper kernel when Lollipop code will be pushed to AOSP... But I'd be suprised if the Nexus 7 even got official Lollipop.
frantisek.nesveda said:
Maaayyybeeee Google will update the grouper kernel when Lollipop code will be pushed to AOSP... But I'd be suprised if the Nexus 7 even got official Lollipop.
Click to expand...
Click to collapse
I'm sure we will get Android 5 one way or another
USBhost said:
I'm sure we will get Android 5 one way or another
Click to expand...
Click to collapse
Well, it will be official, at least according to Android Police.
http://www.androidpolice.com/2014/10/15/being-the-will-of-our-lord-duarte-the-nexus-7-2012-will-receive-the-holy-blessing-of-android-5-0-official/
frantisek.nesveda said:
Well, it will be official, at least according to Android Police.
http://www.androidpolice.com/2014/1...ve-the-holy-blessing-of-android-5-0-official/
Click to expand...
Click to collapse
USBhost said:
I'm sure we will get Android 5 one way or another
Click to expand...
Click to collapse
I appreciate your interest and support, but please, this is a development thread, and nothing to do with L whatsoever. That topic belongs here. If you want to post here a bugreport or in the very least a relevant question from a development perspective is all I ask. Thanks.
frantisek.nesveda said:
Maaayyybeeee Google will update the grouper kernel when Lollipop code will be pushed to AOSP... But I'd be suprised if the Nexus 7 even got official Lollipop.
Click to expand...
Click to collapse
I expect the kernel will be updated as it was for 4.4 from 4.3. I'm still carrying on with this, however, as of course the new kernel will still be 3.1.10. Then I can apply those updates on top of this.
P.S Did some more cherry-picking today. Mostly smooth, very few conflicts so far.
HTCDreamOn said:
I appreciate your interest and support, but please, this is a development thread, and nothing to do with L whatsoever. That topic belongs here. If you want to post here a bugreport or in the very least a relevant question from a development perspective is all I ask. Thanks.
Click to expand...
Click to collapse
Sorry, I got a little carried away with the Lollipop release. I'll test the kernel during the weekend. This is only for AOSP, or can we run it on CyanogenMod as well?
frantisek.nesveda said:
Sorry, I got a little carried away with the Lollipop release. I'll test the kernel during the weekend. This is only for AOSP, or can we run it on CyanogenMod as well?
Click to expand...
Click to collapse
Same here
the kernel should work with CM
frantisek.nesveda said:
Sorry, I got a little carried away with the Lollipop release. I'll test the kernel during the weekend. This is only for AOSP, or can we run it on CyanogenMod as well?
Click to expand...
Click to collapse
No idea... CM use CAF for Qualcomm but we're Tegra 3 so I think it should be fine. Nandroid, flash, restore if it breaks, and no harm done. I'm uploading Alpha 0.1 right now Android browser is a pain with attachments, 0.1 will be tomorrow.
HTCDreamOn said:
No idea... CM use CAF for Qualcomm but we're Tegra 3 so I think it should be fine. Nandroid, flash, restore if it breaks, and no harm done. I'm uploading Alpha 0.1 right now.
Click to expand...
Click to collapse
Awesome will test 0.1
also 0.0 booted just fine on All-F2FS CarbonROM
USBhost said:
Awesome will test 0.1
also 0.0 booted just fine on All-F2FS CarbonROM
Click to expand...
Click to collapse
0.1 uploaded. Glad it works.
0.1 running ok so far only thimg i have noticed is interactive locks at 1200mhz on all 4 cores. On demamd scales fine
gptwarrior said:
0.1 running ok so far only thimg i have noticed is interactive locks at 1200mhz on all 4 cores. On demamd scales fine
Click to expand...
Click to collapse
Interactive has never ran good on my tablet no matter what kernal.
Sent from my Nexus 7 using Tapatalk 2
gptwarrior said:
0.1 running ok so far only thimg i have noticed is interactive locks at 1200mhz on all 4 cores. On demamd scales fine
Click to expand...
Click to collapse
Thanks for pointing this out, I hadn't noticed this before but it's happening to me as well. I seem to remember a commit affecting cpufreq scaling somewhere so this could be it, but it should be easy to fix. I might stock up these smaller problems and fix them right at the end to reduce conflicts, but if its simple enough I'll fix it soonish.
In other news, Alpha 0.2 has been uploaded (first post as usual) mostly just more commits picked, but we're starting to get to the good stuff: changes to tegra3 drivers etc. And some things I can use to update grouper board files :good:
Alpha 0.2 works well here.
Snappy for a stock kernel.
Only things to report:
Max freq is 1200 with all governors.
To turn the tablet on after sleep I have to press the button a lot.
Keep up the good work!!!
Agreed with alpha 2 running smooth same as above with frequency at 1200 keep up the good work looking forward to future updates
I just installed Alpha 2 on LiquidSmooth 3.2. After the first boot, I got multiple force closes on "com.android.acore" but after a reboot everything seems to work just fine. I will use it for the next days and report any bugs I encounter.
I just tried the alpha 2 on my tilapia running a clean install of CyanogenMod 2014-10-23. On the first boot everything is fine, but after a reboot I get SystemUI FC's everytime I unlock the device and it relocks again.
When I install M-kernel a69 or alpha 1 of this kernel, everything seems to be fine. I am using Data-F2FS, if it matters somehow.
I can post a logcat or kmesg tomorrow, right now I screwed up my hackintosh bad and it doesn't even boot, so I don't have a way to access adb.
Edit: I no longer own this phone. Information in the OP may be outdated and/or incorrect. Please go to the new thread at http://forum.xda-developers.com/nexus-6/development/rom-cyanogenmod-13-nightlies-snapshots-t3363769
DISCLAIMER: I AM IN NO WAY RESPONSIBLE FOR ANY PROBLEMS ON YOUR DEVICES CAUSED BY FLASHING THESE BUILDS. THE UPSTREAM CODE AND BUILDING IS MAINTAINED BY THE CYANOGENMOD TEAM, NOT ME. I AM NOT ASSOCIATED WITH THEIR TEAM, I AM JUST THE THREAD OWNER.
It was a fun round of unofficial nightlies but the official upstream CM13 builder for shamu is active! Please use the new download links below to grab the official nightlies. Dirty flash seems to work fine if you go from my unofficial 11-29 build to the official 11-30 one. As mentioned in the first post, I will be ceasing my personal builds for now and leave it to the CM team.
Notes: CyanogenMod's stock kernel forces encryption of storage. Please download one of the third party kernels if you wish to avoid this. Also this thread assumes you have kept up to date with bootloaders and radio. At the time of writing, the latest is from the MRA58K release and can be downloaded here.
CyanogenMod 13.0 Nightlies: Download
Open GApps: Download (I recommend arm, 6.0, micro)
Changelog: CMX Changelog
Third party kernels:
Elite Kernel
Hells Core
XDA:DevDB Information
CyanogenMod 13.0, ROM for the Nexus 6
Contributors
djh816
ROM OS Version: 6.0.x Marshmallow
Based On: CyanogenMod
Version Information
Status: Nightly
Created 2015-11-22
Last Updated 2015-12-06
There's already a thread
http://forum.xda-developers.com/nexus-6/development/rom-cyanogenmod-13-0-android-6-0-t3231497
HipKat said:
There's already a thread
http://forum.xda-developers.com/nexus-6/development/rom-cyanogenmod-13-0-android-6-0-t3231497
Click to expand...
Click to collapse
Correct, but not nightly and as far as I can tell albinoman887 is also making fixes which implies altering of upstream code. My thread intends to serve as a purely upstream source build.
djh816 said:
Correct, but not nightly and as far as I can tell albinoman887 is also making fixes which implies altering of upstream code. My thread intends to serve as a purely upstream source build.
Click to expand...
Click to collapse
I would like to say thank you, and I believe that this ROM deserves its own thread respectfully. Since there isn't much action from that other Alpha build and if you are truly building on a nightly basis then this is much appreciated and I look forward to testing.
Thanks!
HipKat said:
There's already a thread
http://forum.xda-developers.com/nexus-6/development/rom-cyanogenmod-13-0-android-6-0-t3231497
Click to expand...
Click to collapse
A Thread with Zero Support from the Thread OP and no Nightlys , its good to see this Thread with hopfully regular updates since I currently have working in the border guarding Work and never have time for building. But what i know from @djh816 updates come many times.
Tylog said:
A Thread with Zero Support from the Thread OP and no Nightlys , its good to see this Thread with hopfully regular updates since I currently have bodybuilding in the border guarding Work and never have time for building. But what i know from @djh816 updates come many times.
Click to expand...
Click to collapse
Thanks for the support and glad to build it. Just to make sure credit is given where due, any bug fixes will be made only by the CyanogenMod team and/or any git contributors. Not sure if you'll get much support from me either but I'll certainly be glad to give any tips I find. For example, if this one specific bug rears its ugly head again, you may need to rename the SetupWizard apk inside /system/app-priv/ as that has been constantly force closing for me prior to today's build.
djh816 said:
Thanks for the support and glad to build it. Just to make sure credit is given where due, any bug fixes will be made only by the CyanogenMod team and/or any git contributors. Not sure if you'll get much support from me either but I'll certainly be glad to give any tips I find. For example, if this one specific bug rears its ugly head again, you may need to rename the SetupWizard apk inside /system/app-priv/ as that has been constantly force closing for me prior to today's build.
Click to expand...
Click to collapse
MAybe test other Gapps, i had this isues with a few cm 13 builds in combination with banks gapps , i like Banks gapps but for now not with CM13 . No support for me no problem , only 1 builds in 3 Weeks in this early stage is a problem , thats what i mean . I have at the moment zero time , i am one day in the week at home and thats time for my son and my wife
Thanks for the builds. I tried (unsuccessfully) to build my own, so this helps out a lot!
nightlies has not started yet.. looking forward..
Awesome! Thanks!
Sent from my Nexus 6 using Tapatalk
Can anyone confirm that you can write to system on this build???? Wasn't working on a build from 11.20.
Sent from my Nexus 6 using Tapatalk
mexiken said:
Can anyone confirm that you can write to system on this build???? Wasn't working on a build from 11.20.
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
Still is not working.. I'd love to know of a fix, if any...
mexiken said:
Can anyone confirm that you can write to system on this build???? Wasn't working on a build from 11.20.
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
I modified build.prop just fine.
---------- Post added at 03:10 AM ---------- Previous post was at 03:08 AM ----------
Thanks OP, for bringing this to us. Seems pretty good for such an early build. I just barely flashed it but seems great so far.
Does ad away work on this build? It wouldn't work on the previous build.
Is security disable on the ROM?
cz829x18 said:
Does ad away work on this build? It wouldn't work on the previous build.
Click to expand...
Click to collapse
Doesn't seem to just yet. As others have mentioned, no /system writing just yet.
evolishesh said:
Is security disable on the ROM?
Click to expand...
Click to collapse
Doesn't seem like it, I've tried "adb shell" with "su" after but still drops me to a "$" shell rather than "#"
Will you be adding any features or will this be more of a slim to stock cm13 builds? Also thanks for your contributions
nighthawk626 said:
Will you be adding any features or will this be more of a slim to stock cm13 builds? Also thanks for your contributions
Click to expand...
Click to collapse
No features added whatsoever If they add it upstream (included in CM) it'll be here, otherwise no. Absolutely stock. Consider me a third party buildbot slave
Very nice ROM. Just to let everyone know I just finished flashing with the Open GApps Pico and it's working fine. I know, it's bad form to use something that's not recommended.
One quick question, do we get any notification that the new nightly is ready to flash or do we just check the download site?
dlbarron said:
Very nice ROM. Just to let everyone know I just finished flashing with the Open GApps Pico and it's working fine. I know, it's bad form to use something that's not recommended.
One quick question, do we get any notification that the new nightly is ready to flash or do we just check the download site?
Click to expand...
Click to collapse
For now just the download site. I may setup something similar to the pushbullet feed Chroma has if people are interested but haven't spent the time to do it yet. New 11-23 build is up now though
Edit: Woot, looks like they fixed the system rw mounting. Hm but my test file disappeared on reboot.. maybe not yet
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..
Hi guys,
as LineageOS 15.1 is just around the corner and I had a few spare CPU cycles, here's the current build which I did as a 'code of honor'-member. Just flash with TWRP as usual, add gapps (stock are too big) and optionally root.
Watch out as the whole rom might still lack a few features.
Sources are on https://github.com/LineageOS
Credits to anyone who worked on them including intel for their buggy CPUs enabling me to build.
Build date: 2018-03-02
Download: https://go.stargazer.at/bacon
FAQs.:
Q: What patches did you include?
A: None. Pure LineageOS as it would come from the build server
Q: So this IS the official LineageOS rom?
A: In theory it's the same thing, but I am NOT a linageos developer
Q: What Gapps package did you use?
A: Nano. Stock is too big as it wouldn't fit on /system
Q: Support?
A: None officially. But ask - maybe someone has an idea.
Q: What works?
A: Phone rings, I'm able to answer and do calls, BT works, Wifi... annoying texts already arriving. I assume it's working.
Q: Bugs?
A: You tell.
Q: Is it complete?
A: I doubt it. Some translations are still missing. Keep in mind it's an early version of lineageOS
Q: Why did you build it?
A: Because I did not want to wait for the official release and live on the edge.
Q: Why does a girl build roms?
A: Short answer: because I can.
is the camera working? apparently that is the reason why the official build have been delayed
borzowsky said:
is the camera working? apparently that is the reason why the official build have been delayed
Click to expand...
Click to collapse
Honestly, I did not check yet as camera is not one of my basic needs. Will do so as soon as I get home.
If it does not work yet, I do not intend to fix too much stuff as I want to stay on the official sources. If there's a patch to cherrypick from gerrit, it's something we may talk about.
Camera does not work yet, but as far as I can see there are a few things in review to be submitted. Stay tuned as I will be building the rom again as soon as those changes are merged. In the meanwhile I may do some tinkering on my local build.
References:
https://review.lineageos.org/c/206914/
Long live bacon
cb5264 said:
Camera does not work yet...
Click to expand...
Click to collapse
I noticed that your build has SELinux enforcing but this may be why the camera isn't working; something that still needs fixing.
cb5264 said:
Camera does not work yet, but as far as I can see there are a few things in review to be submitted. Stay tuned as I will be building the rom again as soon as those changes are merged. In the meanwhile I may do some tinkering on my local build.
References:
https://review.lineageos.org/c/206914/
Click to expand...
Click to collapse
I've been keeping tabs on this every day and no one has touched it for weeks [emoji24] hopefully they just have code they're working on offline and just have to upload it and merge. Waiting is killing me though. Good to know it's getting close but probably will still wait since I'll probably do a full wipe once it's ready and don't want to do it twice.
Sent from my Nexus 7 using Tapatalk
remedya said:
I noticed that your build has SELinux enforcing but this may be why the camera isn't working; something that still needs fixing.
Click to expand...
Click to collapse
I doubt that it's SELinux. Looking at the logcat the problem root seems to be the HAL and that we should use the CAF stack. Besides that some clocks seem to be out of sync (mainly front camera). If it would be SELinux, logcat/dmesg would show.
Download doesnt work
I will fix it as I compile the next version.
cb5264 said:
Camera does not work yet, but as far as I can see there are a few things in review to be submitted. Stay tuned as I will be building the rom again as soon as those changes are merged. In the meanwhile I may do some tinkering on my local build.
References:
https://review.lineageos.org/c/206914/
Click to expand...
Click to collapse
Some changes on 19 March.
Download link fixed btw
remedya said:
Some changes on 19 March.
Click to expand...
Click to collapse
Are these the changes needed to fulfill the LineageOS Device Support Requirement/camera recorder?
cb5264 said:
Download link fixed btw
Click to expand...
Click to collapse
Error 7
---------- Post added at 08:37 PM ---------- Previous post was at 08:19 PM ----------
Lol and now the download link is gone. Just stop. Wait for the official there is clearly a reason why its not been officially released yet.
First look at Build 2003 is really fine. Thanks for your hard work, Lady
Cam seems "two steps from hell" ...
https://review.lineageos.org/#/q/project:LineageOS/android_device_oneplus_bacon
interesting enough ?
The_Voice_70 said:
First look at Build 2003 is really fine. Thanks for your hard work, Lady
Cam seems "two steps from hell" ...
https://review.lineageos.org/#/q/project:LineageOS/android_device_oneplus_bacon
interesting enough ?
Click to expand...
Click to collapse
You had no problems flashing?
It's happening!
Sent from my A0001 using Tapatalk
TbagBaggins said:
You had no problems flashing?
Click to expand...
Click to collapse
Nope. No Problems.
The_Voice_70 said:
Nope. No Problems.
Click to expand...
Click to collapse
Im getting error 7. No other rom gives me error 7. Download link works on and off have tried installing twice same error.
Use latest official TWRP 3.2.1.0. No Problems with it. Error 7 seams to be old Recovery.
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?