So is there anyone who can port an AOSP 9 ROM for NEXUS 5, when Google publish the source online ?
Doubt it, not even Oreo is stable enough
Maybe @amaces or @nasty007 can manage to boot it but don't get your hopes up.
edu24lal said:
Doubt it, not even Oreo is stable enough
Click to expand...
Click to collapse
almost all the Rom is stable, with the exception of Bluetooth.
DarkMaxOff said:
almost all the Rom is stable, with the exception of Bluetooth.
Click to expand...
Click to collapse
I agree, except oreo roms are slow even with a custom kernel ... Nougat still faster
edu24lal said:
I agree, except oreo roms are slow even with a custom kernel ... Nougat still faster
Click to expand...
Click to collapse
CrDroid 4.4 with stock kernel very smooth and fast, but I changed kernel to Breakfast, my battery so weak
Android 9.0 Pie on Nexus 5 - it's a matter of time!
edu24lal said:
Doubt it, not even Oreo is stable enough
Click to expand...
Click to collapse
Dirty Unicorns Oreo is quite stable n smooth for me.
So ofcourse Pie is very much possible even if it's not completely stable.
Botty-Ivan said:
So is there anyone who can port an AOSP 9 ROM for NEXUS 5, when Google publish the source online ?
Click to expand...
Click to collapse
I started syncing the source code. But i can't give eta or release, build date etc. My internet connection is slow.
playerkirk1 said:
Oreo is daily driver stable on Nexus 5, has been for a long time. I wouldn't be surprised that with all the extra optimization Google's done in Pie that once we get a fully working rom it'll work just as if not better than Oreo
Click to expand...
Click to collapse
But why there is no lineage os ?
I downloaded 60 percent of Android Pie source code. I hope i will build at evening. Probably it won't boot at first build. I will work on bugs etc. Don't wait me. It can take 1-2 weeks for a stable build.
playerkirk1 said:
Obviously that's not up to me, I'm not a Lineage OS Dev. They probably dropped support cause of the age of the phone unlike other devs.
Click to expand...
Click to collapse
No that's not the reason, please educate yourself on the subject. The reason why the Nexus 5 doesn't have official support/builds of LineageOS 15.1 is because of some bugs that haven't been fixed. As long they don't get fixed there will be no official builds.
playerkirk1 said:
As I said, I'm not an LOS Dev. People shouldn't be asking me why there isn't any official builds. I never claimed to be right, I just made a guess. Also, why does it matter if there's an official version or not? LOS isn't the be all end all for ROMs, there's other ROMs out there that people can use, like RR, or DU. There's also the unofficial version of LOS, but I haven't tried it out.
Click to expand...
Click to collapse
I didn't mean to be hostile in any way I just wanted to get all speculation out of the way. I don't want people to get a wrong idea about why there are no official LineageOS builds. Was getting tired of the "is Bluetooth calling fixed" messages on threads of Oreo ROMs. You are right about the choice of ROMs but it's always nice to see some official support. But I do think Dev's will eventually drop support for this device, everything comes to an end so we will see less and less ROM's available for the Nexus 5 eventually as it get's older.
I started compiling the source code. I am handling errors.
I built it successfully. I will install. I hope it will boot. (folder name is false, don't mind it)
EDIT: Not booted. ROM is very buggy. I will work on it.
metahex12 said:
I built it successfully. I will install. I hope it will boot. (folder name is false, don't mind it)
EDIT: Not booted. ROM is very buggy. I will work on it.
Click to expand...
Click to collapse
Try setting SELinux to permissive!
Also, could you share your build if that's not a problem for you?
ewentualpl said:
Try setting SELinux to permissive!
Also, could you share your build if that's not a problem for you?
Click to expand...
Click to collapse
Okay, i will upload it today for testers but there is no boot anim or adb (you can access partial logs from recovery). I am an Android Developer in a company. I can't work on it everytime. I will do my best in this weekend. (I am starting today)
ewentualpl said:
Try setting SELinux to permissive!
Also, could you share your build if that's not a problem for you?
Click to expand...
Click to collapse
It is already permissive. Problem is probably kernel and some SELinux policies.
I found the problem in logcat.
Here:
Code:
<3>[ 2.598985] init: /init.rc: 65: invalid command 'load_system_props'
<3>[ 2.599110] init: could not import file '/init.recovery.logd.rc' from '/init.rc'
<3>[ 2.599252] init: could not import file '/init.recovery.vold_decrypt.rc' from '/init.rc'
<3>[ 2.599358] init: /init.recovery.hammerhead.rc: 17: invalid command 'ln'
I will try to fix it today. Then it will boot probably.
metahex12 said:
I found the problem in logcat.
Here:
Code:
<3>[ 2.598985] init: /init.rc: 65: invalid command 'load_system_props'
<3>[ 2.599110] init: could not import file '/init.recovery.logd.rc' from '/init.rc'
<3>[ 2.599252] init: could not import file '/init.recovery.vold_decrypt.rc' from '/init.rc'
<3>[ 2.599358] init: /init.recovery.hammerhead.rc: 17: invalid command 'ln'
I will try to fix it today. Then it will boot probably.
Click to expand...
Click to collapse
Please more logs
Related
So far I've got the basic A51x/A70x support added to my linux-tegra-nv-3.4 branch.
What works:
- The kernel boots
- Panel (partially?)
- USB
- Android is trying to start
Whatnot:
- everything else
So my first goal is to get display up. Currently, I've got a black screen after the bootloader logo, and the following logs:
dmesg
logcat
If anyone can help with this, hit me on hangouts, my g+ profile can be found on my xda profile. I'd appreciate any help, this would be a huge step forward for these devices.
Great work so far !
I quickly looked at your logs, there is some problem with the GPU and SurfaceFlinger can't start.
I'm not very good with Kernel specific devs, but at this point maybe you will have to upgrade hardware libs (egl, etc.).
Maybe you can try to use some Nexus 7 2012 vendor blobs : https://developers.google.com/android/nexus/drivers#grouperktu84p
Shreps said:
Great work so far !
I quickly looked at your logs, there is some problem with the GPU and SurfaceFlinger can't start.
I'm not very good with Kernel specific devs, but at this point maybe you will have to upgrade hardware libs (egl, etc.).
Maybe you can try to use some Nexus 7 2012 vendor blobs : https://developers.google.com/android/nexus/drivers#grouperktu84p
Click to expand...
Click to collapse
Agree on both
really awesome work
and we're already using hwcomposer.tegra.so from grouper
Shreps said:
Great work so far !
I quickly looked at your logs, there is some problem with the GPU and SurfaceFlinger can't start.
I'm not very good with Kernel specific devs, but at this point maybe you will have to upgrade hardware libs (egl, etc.).
Maybe you can try to use some Nexus 7 2012 vendor blobs : https://developers.google.com/android/nexus/drivers#grouperktu84p
Click to expand...
Click to collapse
Newer ones may be needed for 3.4, dunno... also, I may have just missed something simple...
Code:
W/SurfaceFlinger( 266): no suitable EGLConfig found, trying a simpler query
F/SurfaceFlinger( 266): no suitable EGLConfig found, giving up
...
D/NvOsDebugPrintf( 270): NvRmPrivGetChipIdStub: Could not read Tegra chip id/rev
D/NvOsDebugPrintf( 270): Expected on kernels without Tegra3 support, using Tegra2
Anyways, I'm still working on 3.1, refactoring Acer's mess with the kernel files outside the kernel files... minimizing those changes will ease 3.4 development a lot, as it's confusing to watch out for Acer ifdef's all around the kernel
Hi, any news of this project?
chacal1906 said:
Hi, any news of this project?
Click to expand...
Click to collapse
I don't have the device ATM, so I can't do anything related to this.
OK, received an A700 for free to work on this project and I made quite some progress; I fixed almost everything, so 3.4 is like, usable as a daily driver now. Are there any users left to enjoy it? I'm going to start official Unlegacy Android builds (4.4 and 6.0, then 7.1 later on) shortly more details will follow later. The changes include switching to slightly newer blobs for slightly better 2D/3D performance with 3.4.
Hi, great to see you back. ?
My A510 is still alive. ?
The battery is not the best anymore, but it's is always ready to test your great work.
HornetRider said:
Hi, great to see you back.
My A510 is still alive.
The battery is not the best anymore, but it's is always ready to test your great work.
Click to expand...
Click to collapse
Great, I'm in need of an A510 tester message me on Hangouts
Ziyan said:
message me on Hangouts
Click to expand...
Click to collapse
Done [emoji106]
When will we see a working version?
Hi !
It's nice to see that someone is still working on A700/510 !
I have a A700 and if you need feedback, don't hesitate !
Ziyan said:
OK, received an A700 for free to work on this project and I made quite some progress; I fixed almost everything, so 3.4 is like, usable as a daily driver now. Are there any users left to enjoy it? I'm going to start official Unlegacy Android builds (4.4 and 6.0, then 7.1 later on) shortly more details will follow later. The changes include switching to slightly newer blobs for slightly better 2D/3D performance with 3.4.
Click to expand...
Click to collapse
Have you abandoned the project?
I found the builds on Jenkins. I even ran them on my a700. If remove checks from the installer, they are flashed.
But the recovery does not work.
Ziyan said:
OK, received an A700 for free to work on this project and I made quite some progress; I fixed almost everything, so 3.4 is like, usable as a daily driver now. Are there any users left to enjoy it? I'm going to start official Unlegacy Android builds (4.4 and 6.0, then 7.1 later on) shortly more details will follow later. The changes include switching to slightly newer blobs for slightly better 2D/3D performance with 3.4.
Click to expand...
Click to collapse
sir yes sir! ancient tab is ready for reincarnation
i dont check the a700 forum often though, so if something needs eyes please quote, mention, or pm me. ill get an email and know to check back
edit: we may need a newer and functional TWRP version for some of the newer OS versions =/
Sterist said:
sir yes sir! ancient tab is ready for reincarnation
i dont check the a700 forum often though, so if something needs eyes please quote, mention, or pm me. ill get an email and know to check back
edit: we may need a newer and functional TWRP version for some of the newer OS versions =/
Click to expand...
Click to collapse
TWRP3 ready
Kaban4ik86 said:
Have you abandoned the project?
I found the builds on Jenkins. I even ran them on my a700. If remove checks from the installer, they are flashed.
But the recovery does not work.
Click to expand...
Click to collapse
A thread will be opened soon. Until then - feel free to use the aosp-6.0 builds from Jenkins (they're almost fully complete)
Ziyan said:
TWRP3 ready
A thread will be opened soon. Until then - feel free to use the aosp-6.0 builds from Jenkins (they're almost fully complete)
Click to expand...
Click to collapse
is the recovery mirrored somewhere? and what/where is this jenkins repository
Sterist said:
is the recovery mirrored somewhere? and what/where is this jenkins repository
Click to expand...
Click to collapse
jenkins.unlegacy-android.org/view/All/builds picasso2 builds…
But recovery don't work on my a700. Black screen... If press "Menu" button tablet reboots...
This sounds great, I am already running the UA build on my Nexus, time to dust of the A700 !
Kaban4ik86 said:
jenkins.unlegacy-android.org/view/All/builds picasso2 builds…
But recovery don't work on my a700. Black screen... If press "Menu" button tablet reboots...
Click to expand...
Click to collapse
what checks need to be removed?
I tried flashing with twrp 2.7.1 (newest publicly available) and ctr 3.3
twrp failed at unexpected contents (I previously wiped all partitions)
and ctr auto-rebooted in the process when I wasn't looking, and it apparently failed as well.
this was using the newest "stable" 6.0.1 build
Sterist said:
what checks need to be removed?
I tried flashing with twrp 2.7.1 (newest publicly available) and ctr 3.3
twrp failed at unexpected contents (I previously wiped all partitions)
and ctr auto-rebooted in the process when I wasn't looking, and it apparently failed as well.
this was using the newest "stable" 6.0.1 build
Click to expand...
Click to collapse
*.zip/META-INF/com/google/android/updater-script
Code:
if range_sha1("/dev/block/platform/sdhci-tegra.3/by-name/CAC", "36,0,32767,32768,32770,32849,32851,33341,65535,65536,65538,98304,98306,98385,98387,98877,106070,131072,131074,163840,163842,163921,163923,196608,196610,229376,229378,229457,229459,262144,262146,294912,294914,294993,294995,295485,313343") == "afd609f9867238c1cd370d82772817d744182c79" then
if range_sha1("/dev/block/platform/sdhci-tegra.3/by-name/CAC", "50,32767,32768,32770,32849,32851,33341,65535,65536,65538,66050,97792,98304,98306,98385,98387,98877,106070,106582,130560,131072,131074,131586,163328,163840,163842,163921,163923,164435,196096,196608,196610,197122,228864,229376,229378,229457,229459,229971,261632,262144,262146,262658,294400,294912,294914,294993,294995,295485,313343,313344") == "6b72a7b11b65c9ef1bb4c57ab78076d1ccd2e0e9" then
ui_print("Verified the updated system image.");
else
abort("system partition has unexpected non-zero contents after OTA update");
endif;
else
abort("system partition has unexpected contents after OTA update");
endif;
Overview:
Code:
[B]Experimental CyanogenMod 12.1 compiled with [URL="http://releases.linaro.org/14.10/components/android/toolchain/4.9"]Linaro 4.9 (14.10) Toolchain[/URL].[/B]
This is CyanogenMod 12.1 built straight from source with Code Review
cherry-picks and my own custom device trees and kernel.
CDMA carrier setup:
The following only needs to be done once to allow init to properly setup your carrier specific system properties.
This will set ro.boot.carrier to your specific carrier identifier and will persist through future flashes of this ROM.
Code:
From the bootloader issue the following commands depending on your carrier:
'fastboot oem config carrier verizon' (Verizon)
'fastboot oem config carrier pageplus' (Page Plus)
'fastboot oem config carrier reliance' (Reliance Mobile)
'fastboot oem config carrier sprint' (Boost Mobile)
Builds:
CM-12.1 06-08-2015 (MD5: (2414f09586228eb94bcda47c1f149ed0)
MMS Flashable Zip Fix Thanks @starkly_raving @Alberto97
TK Gapps Mini Modular 5.1 (05-30-2015)
Build Archives
Source Code:
codyf86/android_device_motorola_falcon
codyf86/android_device_motorola_msm8226-common
codyf86/android_kernel_motorola_msm8226 (Stock CM kernel Not even stock anymore kernel xD)
Code Review Cherry-Picks: (Latest build)
healthd: Use android blue for charge percentage
PowerManagerService: Fix updating of mUserActivitySummary
Add option to set default custom function to button recents (1/2)
Add option to set default custom function to button recents (2/2)
cmsdk: do not crash system if CustomTileListenerService isn't present
Note: When Items drop off the above list 9/10 they have been merged.
Changelog:
Code:
I don't believe in change logs; I believe in Github.
Please look above at the Code Review and also through
the source code commits to see what's changed.
The proof is in the [STRIKE]pudding[/STRIKE] Github.
Nice man ... Will be giving this a shot. Do you have a bug tracker set up or do you want logs and reports posted here?
Yummy. Also trying this out for sure.
Edit: Sub'd, Muuahahaha!....Oh.
starkly_raving said:
Nice man ... Will be giving this a shot. Do you have a bug tracker set up or do you want logs and reports posted here?
Click to expand...
Click to collapse
Feel free to post logs / bugs here. Mainly have time to build after work on weekdays. On the weekends is when I can actually work on fixing things.
For device specific things just post the bugs / logs here. For CM specific bugs I would use JIRA and post a link to the bug here. (More helpful/useful to the CM team to make an actual JIRA bug report.)
3 WORDS: STABLE AS ****!
thanks for the rom, this will forsure be my daily driver. only little problem is the no service icon (xt1031) but data is working. soft reboot fixes it though!
Can anyone please comment on the speed of this ROM since it is Linaro based? The other 5.1 ROMs on my phone are pretty responsive, but if even more speed can be gained with our limited hardware, that will be great.
@CodyF86,
Having a problem with the download link. Rom starts downloading but does not download the whole 251mb. Only partial download. Tried about ten times but still same result. Tried with a different browser but same result.
Edit: Nevermind. Downloaded the rom from my phone and copied it from download folder on phone to internal storage.
Hello there @CodyF86 ! Thanks for you work! One little request. Do you think you will be able to add a mirror or upload your work to another claudbased storage? Like MEGA or Mediafire or AndroidFileHost or whichever you want. This one you are using is insanely unstable for me. It gets interrupted every 5 minutes. I'll be really glad if you could change it or add other(s).
Cheers.
I'll upload to Google drive starting tonight also. Driving home from work, will do another one.
CodyF86 said:
I'll upload to Google drive starting tonight also. Driving home from work, will do another one.
Click to expand...
Click to collapse
Thank you very much! And sorry for bothering you with this. I really want to test your ROM since al Linaro builds seem gone from this forum. Thanks again. Drive safe
Cheers.
New build posted. Main link is to Google drive now.
Some more ARM assembly fun if you look under the kernel source commits.
Will fix the signal indicator so you don't have to do a soft reboot for it to work this weekend. Need to go through the soak test build.prop and compare a few other things...just need time this weekend.
CodyF86 said:
New build posted. Main link is to Google drive now.
Some more ARM assembly fun if you look under the kernel source commits.
Will fix the signal indicator so you don't have to do a soft reboot for it to work this weekend. Need to go through the soak test build.prop and compare a few other things...just need time this weekend.
Click to expand...
Click to collapse
thanks for both: new link and new build Can I dirty flash it over the build before? Just installed the first release lol
Cheers.
I've been dirty flashing; should be good to go.
Update: yes, this ROM is very fast indeed! Thanks for sharing.
This ROM is very fast! Especially for a CM ROM (which in my experience have gotten horribly slow over the last few versions) I haven't experienced nearly as many redraws, stutters, freezes or any other general unpleasantness. Good job @CodyF86
starkly_raving said:
This ROM is very fast! Especially for a CM ROM (which in my experience have gotten horribly slow over the last few versions) I haven't experienced nearly as many redraws, stutters, freezes or any other general unpleasantness. Good job @CodyF86
Click to expand...
Click to collapse
Same here. great work! Not as many customizable like other 5.1 based out there, but is enough fast and stable. Thanks.
just wondering what recovery you are using and do partitions need changed from stock?
What models are supported?
@CodyF86
thanks for your work!
I've a strange bug on last cm...every time i reboot time and data change and the year switch to 2025. I've read its time_daemon related bug...can you control? I've this issue with last cm12 builds
Shawnsch said:
just wondering what recovery you are using and do partitions need changed from stock?
Click to expand...
Click to collapse
CWM 6.0.5.1 I think 6.0.4.7 is the last one posted on CMs website, I'll post the latest one in the OP tonight, but they're basically the same. Nothing needs to be changed from stock.
Orjakone said:
What models are supported?
Click to expand...
Click to collapse
Theoretically they all should work, but I need someone to the GSM version to try it out.
The_Poison said:
@CodyF86
thanks for your work!
I've a strange bug on last cm...every time i reboot time and data change and the year switch to 2025. I've read its time_daemon related bug...can you control? I've this issue with last cm12 builds
Click to expand...
Click to collapse
Weird, I haven't noticed that, but tbh I haven't actually payed attention to what year my phone shows / I don't even have it set up to show me I'll have to look and see if mine does it also.
Will do another one tonight / it's the weekend can play around with it get some things done now.
Hi World,
I've been building a ROM nightly, pulling from LineageOS, LineageOMS, and SultanXDA.
It's been fine for me, so I thought I'd share it for others to use too.
This is my first go at posting this kind of thing, so please go easy on me.
Sources:
https://github.com/LineageOS
https://github.com/LineageOMS
https://github.com/sultanxda
Credits
LineageOS team
Substratum team
@Sultanxda
Before Flashing...
You MUST be on the correct Firmware for this image to flash. Download them here:
OnePlus 3T
OnePlus 3
Downloads:
XDA
Android File Host
Flash the firmware image in TWRP. From there in, it's the usual instructions. Flash in TWRP, optionally use GAPPS and Magisk/SuperSU/Lineage-Addon.
Usual risks apply.
If there is any other information I should be including here, please let me know.
XDA:DevDB Information
Lineage OS with SultanXDA tweaks and OMS, ROM for the OnePlus 3
Contributors
prmcmanus
ROM OS Version: 7.x Nougat
ROM Firmware Required: OB8
Based On: LineageOS
Version Information
Status: Nightly
Created 2017-06-18
Last Updated 2017-06-18
Changelog
In the attachments.
This is the how I'm capturing Change Logs until I set up my own repo. Advice is welcomed if there are better methods.
Code:
repo forall -pc ' git log --since=$(cat /home/mcmanus/android/changelog/lastbuild_OP3.txt) --date-order ' > /home/mcmanus/android/changelog/OP3-changelog-$(date +%Y-%m-%d).txt
date +%d.%m.%Y > /home/mcmanus/android/changelog/lastbuild_OP3.txt
Reserved
Good start bro!! ?
@prmcmanus
Welcome brother..[emoji120]
There is already a sultanxda based + oms supported build, so please will you tell us about changlog...
Anyway We appreciate your work and contribution for 3(T)...[emoji4]
mukesh22584 said:
@prmcmanus
Welcome brother..[emoji120]
There is already a sultanxda based + oms supported build, so please will you tell us about changlog...
Anyway We appreciate your work and contribution for 3(T)...[emoji4]
Click to expand...
Click to collapse
Thanks I didn't realise there was already a similar ROM, which is why I built this one.
It looks like the other is adding other features, whereas I'm sticking to the sources for now, so that's be the difference between the two.
I'll get the change log in the reserved post
Hi! Thank you for your work!
Please consider taking features from this unofficial Sultan's build by @matssa as, according to him, he will stop building for OP3 as OP5 comes out.
Would be awesome if your rom kinda 'inherited' his work into the future
Nezorflame said:
Hi! Thank you for your work!
Please consider taking features from this unofficial Sultan's build by @matssa as, according to him, he will stop building for OP3 as OP5 comes out.
Would be awesome if your rom kinda 'inherited' his work into the future
Click to expand...
Click to collapse
Hi @Nezorflame, I didn't realise this ROM existed until yesterday! Looks interesting, and definitely more involved than what I'm currently doing. I won't be implementing anything from that ROM until development ceases on it. If/when that happens, I'll definitely look into it
prmcmanus said:
Hi @Nezorflame, I didn't realise this ROM existed until yesterday! Looks interesting, and definitely more involved than what I'm currently doing. I won't be implementing anything from that ROM until development ceases on it. If/when that happens, I'll definitely look into it
Click to expand...
Click to collapse
He did mention that he is gonna keep his repos up for anybody who wants to continue updating and building his version.
Sent from my ONEPLUS A3000 using Tapatalk
prmcmanus said:
Hi @Nezorflame, I didn't realise this ROM existed until yesterday! Looks interesting, and definitely more involved than what I'm currently doing. I won't be implementing anything from that ROM until development ceases on it. If/when that happens, I'll definitely look into it
Click to expand...
Click to collapse
Looking forward to it! One thing would be nice though, even if we forget about the features - OTA update
Started using your builds as Matssa is about stop supporting his builds. Got no issues, runs stable and smooth. Looking forward to future updates. Update notes would definitely help this rom grow, ota as well
Switching to this ROM as well as matssa will do only one, final build. @prmcmanus please consider my previous request
Would be really cool if this Dev picks up right where Matsaa leaves off.
Nezorflame said:
Hi! Thank you for your work!
Please consider taking features from this unofficial Sultan's build by @matssa as, according to him, he will stop building for OP3 as OP5 comes out.
Would be awesome if your rom kinda 'inherited' his work into the future
Click to expand...
Click to collapse
Stupifier said:
Would be really cool if this Dev picks up right where Matsaa leaves off.
Click to expand...
Click to collapse
I think calling me a Dev might be overly-generous at this point, but I'll learn as I go and do what I can.
I work a 4-on 4-off shift pattern, so I'll look into Matssa's ROM more in a couple of days, and I aim to pick it up.
prmcmanus said:
I think calling me a Dev might be overly-generous at this point, but I'll learn as I go and do what I can.
I work a 4-on 4-off shift pattern, so I'll look into Matssa's ROM more in a couple of days, and I aim to pick it up.
Click to expand...
Click to collapse
That's good news! Matssa managed to get lock screen blur working like on official Lineage. Sultan's builds and your current builds don't have this feature so I'm looking forward to see you pick his ROM up.
Sent from my ONEPLUS A3000 using Tapatalk
Yes! Finally just a LineageOS ROM with sultan kernel and OMS without all the extra stuff
THANK YOU!
OTA updates would be one nice thing to add... For the rest it's perfect as is
@prmcmanus
I've just downloaded your build to flash..
Why are you not updating your thread, I've seen you're making build daily ( may be nightly)...[emoji106]
mukesh22584 said:
@prmcmanus
I've just downloaded your build to flash..
Why are you not updating your thread, I've seen you're making build daily ( may be nightly)...[emoji106]
Click to expand...
Click to collapse
'Cos it's the first ROM I've shared and I don't know what everyone wants to know
I've been a bit suspicious of the fact all the builds are coming out at a very similar size, so I've started from a clean slate on the last two builds and they still turn out similar.
Not had a chance to look at Matssa's build properly yet.
OTA will be the first thing I implement, given that it's what is being requested
prmcmanus said:
'Cos it's the first ROM I've shared and I don't know what everyone wants to know
I've been a bit suspicious of the fact all the builds are coming out at a very similar size, so I've started from a clean slate on the last two builds and they still turn out similar.
Not had a chance to look at Matssa's build properly yet.
OTA will be the first thing I implement, given that it's what is being requested
Click to expand...
Click to collapse
I've flashed your latest build and everything seems fine... Just unable to install V4A...
Will report you after a battery cycle....
@prmcmanus idle drain is so solid let's check active drain..and also installed V4A after many attempt...
Thanks for build...
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 in this ROM
* 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.
*/
Introduction
I use Lineage for my Moto Z, and was bummed out that I wasn't going to get any security updates. So, I decided to learn how to build it myself!
I'm no coder, and I have mad respect for those who actually code and make all of these ROMs possible. That being said, all I know how to do is build the thing from the Lineage repos. I CANNOT FIX BUGS. Period. I would if I could, but I simply don't know how. I can try tiny, very small things, but no guarantees.
I plan on trying to upload builds monthly as time permits, but I have a full time job and other obligations, so it may be irregular. But I like updates as much as everyone, so I'll do my best to build as often as I can.
Click to expand...
Click to collapse
Installation instructions
Flash using latest TWRP. Upgrades, or "dirty flashes", should be fine between builds.
If you are coming from Lineage 14.1 Official builds, you must first flash the migration zip. The installer won't work when working with different keys. Find it here
Make sure to flash Gapps BEFORE you reboot.
Click to expand...
Click to collapse
Changelog
2017-1-20
-Re-forked repo for easy syncing to Lineage official
-January 5 Security Patch
Click to expand...
Click to collapse
Not Working
-You Tell Me
Click to expand...
Click to collapse
Downloads
Lineage 14.1 UNOFFICIAL
FAQ
*Can you fix this bug?
-Probably not
*Can you do more frequent/daily/hourly builds?
-No
*It's not working!
-Please post your build version & information so I can check if it's a bad build, or if something broke in the code
Click to expand...
Click to collapse
Thanks To/Credits
* @Alberto97 , for his awesome work on our device & for providing the fixes that never went into the official build
* Lineage OS Team
Click to expand...
Click to collapse
Donations are appreciated, but certainly not necessary:
Litecoin: LV94DBg14pxNE4SSReKEhcCJKr5ee42o6H
Dogecoin: DCzWV2QimjpwYz73rXbc4UjEdw7yWCCES3
Click to expand...
Click to collapse
Additional source links:
https://github.com/zander21510/android_kernel_motorola_msm8953
https://github.com/zander21510/android_device_motorola_addison
XDA:DevDB Information
Lineage 14.1 Unofficial for Addison, ROM for the Moto Z Play
Contributors
zander21510
Source Code: https://github.com/LineageOS/android.git
ROM OS Version: 7.x Nougat
ROM Kernel: Linux 3.10.x
Based On: Lineage
Version Information
Status: Alpha
Created 2017-12-30
Last Updated 2017-01-20
News & Updates
CHANGELOG:
2017-1-20
-Re-forked repo for easy syncing to Lineage official
-January 5 Security Patch
2017-1-5
-Forked repo from Alberto97's sources
-Fixed camera issue, now using Motorola proprietary repo
-Changed fingerprint sleep to act as home button instead (my personal preference!)
2016-12-30
-Initial build
-Camera not working
could you please add 0xC113 bootloader support? from Alberto's AOSP fix I take it shouldn't be a hard fix to make:
-require version-bootloader=0xC105|0xC106|0xC107|0xC112
+require version-bootloader=0xC105|0xC106|0xC107|0xC112|0xC113
zander21510 said:
Retried build using Alberto97's sources from 14.1-next- camera still broken. I'm guessing it has something to do with a change in the Lineage source code, but I really have no idea. Other than that, everything else seems to be working fine. If anyone wants to give me a lead on the camera problem, maybe I can do something about it.
Click to expand...
Click to collapse
Just to be clear, I assume by broken camera you mean camera on a system level, affecting any use of camera by any application, right ?
Ultramanoid said:
Just to be clear, I assume by broken camera you mean camera on a system level, affecting any use of camera by any application, right ?
Click to expand...
Click to collapse
as far as I can tell, yes. I'm doing another build today to see if there's anything I can do about it
zander21510 said:
as far as I can tell, yes. I'm doing another build today to see if there's anything I can do about it
Click to expand...
Click to collapse
Wonder what they could have changed over at Lineage to break it, since camera stuff is pretty device-specific and no one is working on this device now. Good luck at any rate.
taking some baby steps with developing! I forked Alberto97's repos and made a couple of changes...including this one:
WebmonkeyJMK said:
could you please add 0xC113 bootloader support? from Alberto's AOSP fix I take it shouldn't be a hard fix to make:
-require version-bootloader=0xC105|0xC106|0xC107|0xC112
+require version-bootloader=0xC105|0xC106|0xC107|0xC112|0xC113
Click to expand...
Click to collapse
I'll do some testing and upload a build later today
New build with fixed camera and Nov 17 bootloader support.
zander21510 said:
Introduction
Installation instructions
Changelog
Not Working
Downloads
Lineage 14.1 UNOFFICIAL
FAQ
Thanks To/Credits
Donations are appreciated, but certainly not necessary:
Additional source links:
https://github.com/zander21510/android_kernel_motorola_msm8953
https://github.com/zander21510/android_device_motorola_addison
XDA:DevDB Information
Lineage 14.1 Unofficial for Addison, ROM for the Moto Z Play
Contributors
zander21510
Source Code:https://github.com/LineageOS/android.git
ROM OS Version: 7.x Nougat
ROM Kernel: Linux 3.10.x
Based On: Lineage
Version Information
Status: Alpha
Created 2017-12-30
Last Updated 2017-01-05
Click to expand...
Click to collapse
Thanks for your effort man. I really appreciate it. Can you tell me what the security patch level is though?
Mr_prfssnl said:
Thanks for your effort man. I really appreciate it. Can you tell me what the security patch level is though?
Click to expand...
Click to collapse
Still on Dec 5, guess the Jan patch hasn't been merged yet.
So trying to get some things working on my daily driver...my company uses Microsoft Intune Company Portal for access to my work email, which does the standard root checking & etc. On the last official Lineage build, it worked just fine so long as root was shut off in developer tools (if the root zip was installed).
One thing it does which is a bit irritating is that it seems to assume your phone is rooted if you use a rom with test keys, which would be all unofficial builds by default, including mine. So in order to get my work email I'm making signed builds for myself along with the regular unsigned builds. If anyone is interested I can upload signed builds here in case you have some reason you need a signed build. Other than that, I'm not sure there's really any advantage to having a signed build vs an unsigned one. One big disadvantage, you can't migrate to or from any other builds, so you'd be stuck with me unless you wipe
zander21510 said:
One big disadvantage, you can't migrate to or from any other builds, so you'd be stuck with me unless you wipe
Click to expand...
Click to collapse
Here are the scripts to migrate from unsigned to signed or the other way around, to dirty-flash without issue :
https://forum.xda-developers.com/showpost.php?p=70452245&postcount=2
Ultramanoid said:
Here are the scripts to migrate from unsigned to signed or the other way around, to dirty-flash without issue :
https://forum.xda-developers.com/showpost.php?p=70452245&postcount=2
Click to expand...
Click to collapse
From what I understand, these only work if you're going between Lineage keys and test keys, not any other keys
Is ther any way to get substratum themes working on this rom i have tried oms and lineage selection but nothing is getting themed.
zander21510 said:
From what I understand, these only work if you're going between Lineage keys and test keys, not any other keys
Click to expand...
Click to collapse
You're right, what was I thinking...
How did you get updated proprietary blobs?
zander21510 said:
Forked Alberto97s device & kernel so I could try and fix bugs, and also started using a different repo for the proprietary blobs, that fixed the camera issue! So now it looks like everything is working, android security patch is still on Dec 5 though, but everything else is current. Let me know if there are issues
Click to expand...
Click to collapse
Thanks for this (and to Alberto97, if you're out there...).
Like you, I finally couldn't take it any more and began building on my own. I, too, had a fully functional phone except for the camera.
I jumped through a few hoops trying to get the proprietary blobs, and finally scraped them out of your build. I installed XT1635-02_ADDISON_7.1.1_NPNS26.118-22-2-8_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC and tried extract-files.sh but that didn't get everything. I didn't try a deeper look, as I was eager to get my phone working again. I unzipped your ROM and extract-files.sh worked. I rebuilt and now the camera works with my build.
How did you get those blobs? Also, do you know if Motorola publishes stock ROMs for addison, or do we always have to get them second-hand from something like lolinet?
Thanks in advance for any info. I'm probably not worthy of taking responsibility after the loss of Alberto97, but I'd be willing to lend a hand or coordinate the effort somehow.
MIke
mikehat said:
Thanks for this (and to Alberto97, if you're out there...).
Like you, I finally couldn't take it any more and began building on my own. I, too, had a fully functional phone except for the camera.
I jumped through a few hoops trying to get the proprietary blobs, and finally scraped them out of your build. I installed XT1635-02_ADDISON_7.1.1_NPNS26.118-22-2-8_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC and tried extract-files.sh but that didn't get everything. I didn't try a deeper look, as I was eager to get my phone working again. I unzipped your ROM and extract-files.sh worked. I rebuilt and now the camera works with my build.
How did you get those blobs? Also, do you know if Motorola publishes stock ROMs for addison, or do we always have to get them second-hand from something like lolinet?
Thanks in advance for any info. I'm probably not worthy of taking responsibility after the loss of Alberto97, but I'd be willing to lend a hand or coordinate the effort somehow.
MIke
Click to expand...
Click to collapse
I just added this repo (https://github.com/TheMuppets/proprietary_vendor_motorola) to the manifest, you can do that in lieu of the "extract proprietary blobs" step. I noticed there was a fork of it on Alberto97's github (but it was out of date), so I poked around and found TheMuppets one was still being updated, including fixes for addison. So made a build and presto- no more camera issues.
I guess there's some gray legal area when it comes to the proprietary Motorola stuff, that's why it's not listed as an option in the official Lineage build instructions.
Its back to official status https://wiki.lineageos.org/devices/addison
tabletmen said:
Its back to official status https://wiki.lineageos.org/devices/addison
Click to expand...
Click to collapse
It doesn't have a maintainer!
I have problems with the WiFi not turning on
Hi all, I'm trying to build DU on walleye, however I keep running into this error
[ 99% 1439/1440] glob vendor/*/*/*/*/*/*/Android.bp
ninja: error: 'INSTALLED_KERNEL_HEADERS', needed by '/home/everett/~du/out/target/product/walleye/obj/STATIC_LIBRARIES/libgptutils_intermediates/gpt-utils.o', missing and no known rule to make it
17:57:10 ninja failed with: exit status 1
build/core/main.mk:21: recipe for target 'run_soong_ui' failed
make: *** [run_soong_ui] Error 1
Wondering if anyone has a fix, thanks
What kernel source are you using?
providing the log before that would also help.
gbmasterdoctor said:
What kernel source are you using?
Click to expand...
Click to collapse
I'm using Nathan's Kernel Source based on Linux Stable
munchy_cool said:
providing the log before that would also help.
Click to expand...
Click to collapse
Sorry about that, when I get home i'll provide the full logs from the build
munchy_cool said:
providing the log before that would also help.
Click to expand...
Click to collapse
https://pastebin.com/3ybqZEq4
There are the full logs, sorry for not providing them before.
EDIT: Slightly different failure occurs when renaming Kernel source to wahoo and compiling
https://pastebin.com/bRFEBTTj
TCUofficial said:
https://pastebin.com/3ybqZEq4
There are the full logs, sorry for not providing them before.
EDIT: Slightly different failure occurs when renaming Kernel source to wahoo and compiling
https://pastebin.com/bRFEBTTj
Click to expand...
Click to collapse
the one below
Code:
ninja: error: 'kernel/google/wahoo/arch/arm64/configs/flash-walleye_defconfig', needed by '/home/everett/~du/out/target/product/walleye/obj/KERNEL_OBJ/.config', missing and no known rule to make it
17:59:08 ninja failed with: exit status 1
is because the kernel configuration you want to use is not there. you can check in kernel/google/wahoo/arch/arm64/configs
this one
Code:
ninja: error: 'INSTALLED_KERNEL_HEADERS', needed by '/home/everett/~du/out/target/product/walleye/obj/STATIC_LIBRARIES/libgptutils_intermediates/gpt-utils.o', missing and no known rule to make it
17:47:56 ninja failed with: exit status 1
build/core/main.mk:21: recipe for target 'run_soong_ui' failed
is because its not able to find that file.
if you can point me to your device, kernel, vendor trees i can have a look.
munchy_cool said:
if you can point me to your device, kernel, vendor trees i can have a look.
Click to expand...
Click to collapse
Device tree was modified from AICP, I have it here: https://github.com/TCU14/device_google_walleye
The proprietary vendors are also from AICP, here: https://github.com/AICP/proprietary_vendor_google
The kernel source is here: https://github.com/android-linux-stable/wahoo
Thanks for the help, I'm doing my best to fix things on my own and am trying to improve. Unfortunately errors are not my forte
TCUofficial said:
Device tree was modified from AICP, I have it here: https://github.com/TCU14/device_google_walleye
The proprietary vendors are also from AICP, here: https://github.com/AICP/proprietary_vendor_google
The kernel source is here: https://github.com/android-linux-stable/wahoo
Thanks for the help, I'm doing my best to fix things on my own and am trying to improve. Unfortunately errors are not my forte
Click to expand...
Click to collapse
so we need to do it right.
1. fork the repo, then clone it. dont clone and push as a new repo because it's going to be hard to track changes if you get serious about this.
this line below
Code:
TARGET_KERNEL_CONFIG := flash-walleye_defconfig
specifies what kernel config the build is looking for.
https://github.com/TCU14/device_google_walleye/blob/master/walleye/BoardConfig.mk
where does it look for those configs?
well it looks for those configs here
https://github.com/android-linux-stable/wahoo/tree/android-msm-wahoo-4.4-oreo-m2/arch/arm64/configs
so as you can see you dont have that config. so you can use wahoo_defconfig.
Even I am new to this, so i might not be the best guide but i will try my best.
munchy_cool said:
so we need to do it right.
1. fork the repo, then clone it. dont clone and push as a new repo because it's going to be hard to track changes if you get serious about this.
this line below
Code:
TARGET_KERNEL_CONFIG := flash-walleye_defconfig
specifies what kernel config the build is looking for.
https://github.com/TCU14/device_google_walleye/blob/master/walleye/BoardConfig.mk
where does it look for those configs?
well it looks for those configs here
https://github.com/android-linux-stable/wahoo/tree/android-msm-wahoo-4.4-oreo-m2/arch/arm64/configs
so as you can see you dont have that config. so you can use wahoo_defconfig.
Even I am new to this, so i might not be the best guide but i will try my best.
Click to expand...
Click to collapse
Thanks for that, just forked AICP and made my changes, new tree is here: https://github.com/TCU14/device_google_walleye-1
I'll see if I can build or if another error pops up, again thanks for the help
EDIT: Nvm, I am stupid. Back to the kernel headers issue :/
TCUofficial said:
EDIT: Nvm, I am stupid. Back to the kernel headers issue :/
Click to expand...
Click to collapse
make sure to do
Code:
make clean
after a build fails.
Doesn't that do the same thing as make clobber?
TCUofficial said:
Doesn't that do the same thing as make clobber?
Click to expand...
Click to collapse
yes.
munchy_cool said:
yes.
Click to expand...
Click to collapse
Thanks for the help, it's currently building. Fixed some of the issues, haven't updated my repos yet though
TCUofficial said:
Thanks for the help, it's currently building. Fixed some of the issues, haven't updated my repos yet though
Click to expand...
Click to collapse
good luck let us know how it goes.
Ok, the touchscreen appears to have shat itself. Other then that, it booted fine with no hiccups.
Idk what's after the setup because of the touch issue. Grabbing a logcat now, seeing if I can possibly fix it.
EDIT: Can't get logcat because I can't allow debugging... this is ****ing hilarious to me
EDIT: Flashing FlashKernel fixed the touchscreen issue, however Google Services Framework is now force closing. constantly. Going to rebuild with FlashKernel if I can, and use different GAPPS in the build
TCUofficial said:
EDIT: Flashing FlashKernel fixed the touchscreen issue, however Google Services Framework is now force closing. constantly. Going to rebuild with FlashKernel if I can, and use different GAPPS in the build
Click to expand...
Click to collapse
glad you are having more success than i did initially Enjoy
UPDATE: Flash gives me the Kernel headers issue, however I still need to flash the zip for touch. Google Services Framework is still acting stupid, so I'm going to try and build without the PixelGapps vendor. If successful, it should work fine if we flash the Gapps after the first initial boot of the ROM. I'll test MindTheGapps, OpenGapps, BeansGapps, etc and find the most stable out of all of them for the ROM. If the rom works and is stable(Nothing obviously broken) I'll add a Google Plus link in my signature and post another update. For now, I cannot post on XDA as DU is thoroughly against it.
TCUofficial said:
For now, I cannot post on XDA as DU is thoroughly against it.
Click to expand...
Click to collapse
why is DU against posting builds on xda?
munchy_cool said:
why is DU against posting builds on xda?
Click to expand...
Click to collapse
No clue, the closest they have gotten to actually posting was announcing builds were available for Taimen and having users from XDA test the builds. Other then that, they are strongly against it for reasons unknown