All the blah blah about "as is", you being responsible for what you choose to do and do to your device, no guarantees implied nor stated... And all the usual to install. I wont be paying much attention to bugs, however, PLEASE post them as you find them to let others know what they can expect.
This build is a ONE-OFF and you should look at the original thread by @Krizthian for possible future builds. https://forum.xda-developers.com/google-nexus-5/development/rom-crdroid-v4-0-google-nexus-5-t3767591
Special thanks to @haze_nme who provided the device and kernel for without which this build would not be possible. Please visit his post and give the thanks button a BIG slap! https://forum.xda-developers.com/showpost.php?p=76807742&postcount=315
Of course, thanks to the crDroid team for providing the ROM source itself; and making it so easy to build using LineageOS device trees.:good:
Changes from the default source:
Code:
[FONT="Verdana"] Added the MiXplorer [url]https://forum.xda-developers.com/showthread.php?t=1523691[/url]
I got the OK first too include in my unofficial ROMs that I build, visit the forum, they are very helpful for this VERY powerful file explorer. [url]https://forum.xda-developers.com/showthread.php?t=1523691[/url]
You can thank @HootanParsa for building it, and letting me include it:good: Be sure to share some thanks.
Switched over to the ResurrectionRemox launcher. I had issues with the default launcher in crDroid. Also on another device, and I think I have read some other users had the same on even more devices.
Vinyl Music Player and removed crDroid music.
It has more features but is based off the same original app in crDroid. Including a dark theme!
Just to be polite I checked with the dev to get his ok, even though its open source. It can also be fund on F-Droid
OmniClock replaces the standard deskclock. Sourced from OmniROM, so a big thanks to them. It has a nicer dark skinn also.
[/FONT]
I have only done a rudimentary test on it. I flashed PICO Gapps, and there aint much room left in the system partition.
Source: https://github.com/crdroidandroid
Device: https://github.com/hazenme/android_device_lge_hammerhead
Kernel: https://github.com/hazenme/android_kernel_lge_hammerhead
Vendor: https://github.com/TheMuppets/proprietary_vendor_lge
You can download this build, and flash at your own risk, from:
crDroidAndroid-8.1-20180614-hammerhead-v4.4-DiamondJohnDroid.zip
MD5: 25e05c3f02d34968f308ac6b4ad32b8b
Thanks a bunch, I am eager to test this out and will update once I get a chance.
Good news, love crdroid rom, downloading. , thanks
Thank you so much for taking this project, I'm waiting for updates
Greetings
Krizthian said:
Thank you so much for taking this project, I'm waiting for updates
Click to expand...
Click to collapse
I wouldnt be too grateful, it was a one-off build of a secondary/spare device I have. While I await updates to my daily devices' kernel and device tree
DiamondJohn said:
This build is a ONE-OFF and you should look at the original thread by @Krizthian for possible future builds. https://forum.xda-developers.com/google-nexus-5/development/rom-crdroid-v4-0-google-nexus-5-t3767591
...snip....
Special thanks to @haze_nme who provided the device and kernel for without which this build would not be possible. Please visit his post and give the thanks button a BIG slap! https://forum.xda-developers.com/showpost.php?p=76807742&postcount=315
...snip....
Source: https://github.com/crdroidandroid
Device: https://github.com/hazenme/android_device_lge_hammerhead
Kernel: https://github.com/hazenme/android_kernel_lge_hammerhead
Vendor: https://github.com/TheMuppets/proprietary_vendor_lge
Click to expand...
Click to collapse
Maybe I too should be looking at the commits made into @Hazenmetrees to possibly see what needs to be done against my actual device.
DiamondJohn said:
I wouldnt be too grateful, it was a one-off build of a secondary/spare device I have. While I await updates to my daily devices' kernel and device tree
Maybe I too should be looking at the commits made into @Hazenmetrees to possibly see what needs to be done against my actual device.
Click to expand...
Click to collapse
Oreo for RAZR M perhaps?
That'd be quite the display if you could get that to work, assuming that is still your daily device. I have an N5 spare as well, but the WiFi chip broke : (
4.4 is working like a champ here. Many thanks. Tried to install ElementalX 9.02 but it wouldn't take. Will investigate further soon.
Galaxyninja66 said:
Oreo for RAZR M perhaps?
That'd be quite the display if you could get that to work, assuming that is still your daily device. I have an N5 spare as well, but the WiFi chip broke : (
Click to expand...
Click to collapse
Cast your mind back. My Razr is dead! Upgrading the kernel (and the device tree) is a big task. We were very lucky for Nougat, as the XT897 was pretty damn close and it had an official LOS build. ie the device tree and kernel were basically ready to kang. As far as I know, there is no official Oreo for the xt897 and therefore, unless you spend the time and effort, there is no Oreo for the xt907/xt905/xt926 etc etc.
For now I use and build for an GT-i9506 as my daily, and I also have an N5 as a "spare", which is half dead (mic is flakey which makes a phonee useless). I build for the N5 as "practice" for the S4, and I shared the results here, as I saw the current builds were quite old; [sarcasm]and I'm such a nice guy[/sarcasm]
DiamondJohn said:
Cast your mind back. My Razr is dead! Upgrading the kernel (and the device tree) is a big task. We were very lucky for Nougat, as the XT897 was pretty damn close and it had an official LOS build. ie the device tree and kernel were basically ready to kang. As far as I know, there is no official Oreo for the xt897 and therefore, unless you spend the time and effort, there is no Oreo for the xt907/xt905/xt926 etc etc.
For now I use and build for an GT-i9506 as my daily, and I also have an N5 as a "spare", which is half dead (mic is flakey which makes a phonee useless). I build for the N5 as "practice" for the S4, and I shared the results here, as I saw the current builds were quite old; [sarcasm]and I'm such a nice guy[/sarcasm]
Click to expand...
Click to collapse
Hmmm... messed up Nexus 5 you say... maybe we can trade mother boards via mail?
eh who am I kidding my Nexus 5 is worthless to me, the modem still works making it's purpose as a backup phone fulfilled
Thank you so much!!!!!!
@DiamondJohn : thanks man
4.5 will be?
see post https://forum.xda-developers.com/showpost.php?p=77301143&postcount=50
OP request.
THREAD CLOSED
Related
"The G2 Dream Team" (and they well deserve that name) has released not one, but TWO lollipop builds for the LG G2. Both ROMs are based on the same build tree, but one ROM is CM12 and the other is a LiquidSmooth 4.0 ROM. Despite being built from the same build tree, they carry different features. They are stable and usable for daily drivers, but they may carry some bugs, like a non-functional video playback, NFC issues for LS/VS980 but it should all be sorted out in the near future. Head over to the threads to read more!:
Liquidsmooth 4.0:
http://forum.xda-developers.com/lg-g2/development/rom-liquidsmooth-v4-0-lg-g2-t2948395
CM12:
http://forum.xda-developers.com/lg-g2/development/rom-cyanogenmod-12-0-lg-g2-t2944269
Older posts:
An increasing amount of devices have been receiving unofficial Android Lollipop 5.0 ports, like the HTC One M8 and the LG Optimus L9. Today another device can be added to the list of phones receiving a treatment with the taste of Android Lollipop, the LG G2. While there generally has been a wide contribution from the community; testing, sharing files and giving ideas, two XDA members stood out in particular in order to create the build, @ylukasy and @InfinitusDesigner. The port is still in a very early pre-alpha stage, and the bugs are barely known yet, but the ROM boots and has even been rooted! While it might be wisest to wait until an official thread has been made before grabbing your devices and start flashing, @ylukasy has already provided a download link for the ROM, and calls for people to help discover the bugs so that they can be eliminated. Please notice that the ROM might not be stable enough to be used as a daily driver, but owners of a LG G2 are officially an important step closer to having a stable Lollipop ROM!
If this post caught your interest and you're willing to take the risk, head over to the last pages in the following thread: http://forum.xda-developers.com/lg-g2/general/unofficial-cm12-nexus-5-posted-t2936398
As previously mentioned, a lot of things are not sorted out yet, and the build might not be for your device number, so make sure you read the entire thread before continuing, or simply wait untill an official thread is made.
Update:
An official thread has been posted and it can be found by following this link: http://forum.xda-developers.com/lg-g2/development/rom-android-lollipop-fast-clean-t2941922
The build is a port of the Nexus 5 ROM, and users of the ROM have been saying that the rom is very fast and fluid, calls work, camera works (although the quality is inferior), but other users have been reporting random reboots and incompatibilities with certain apps such as YouTube or WhatsApp.
by vPro97
This post will be updated regularly when new information regarding Lollipop ports surface.
Fantastic News! Will get round to trying it shortly, thanks for the link!
While I have my doubts about it being functional (or even booting) on my LS980, I'll give it a shot and see what happens.
Nice to see things moving at breakneck speeds these days.
On a side note, I just read the AnandTech review of the Nexus 6 and am happy to report that my well over a year old G2 beats it in several benchmarks so I'm pretty satisfied at the moment, especially considering I got it for free. I mean really...
In before "no build for xxxx?!?!?!?"
Anyone know how to port a d802 rom to d800?
Ready to try it out and see what happened..??
his build is from the same source the other was he doesn't deserve credit for it. it's using cm12 kernel and dev claims it's using nexus 5 port yet requires gapps and no signs of any nexus 5 code at all.
Wouldn't it be alot easier to just post the download link here?
₪LG G2₪
Zyner said:
Wouldn't it be alot easier to just post the download link here?
₪LG G2₪
Click to expand...
Click to collapse
It's not my work, and there are some steps which must be followed in order to make it work. I am just objectively informing any news regarding Android Lollipop for the LG G2.
OP has been updated.
The download link was removed before i could get the v3 version so im stuck with v2 and ive been using it as my daily (yeah it reboots every 5 minuets and i can leave wifi on or it will bootloop) But honestly thats the fun in testing this stuff out
MrNegative370 said:
The download link was removed before i could get the v3 version so im stuck with v2 and ive been using it as my daily (yeah it reboots every 5 minuets and i can leave wifi on or it will bootloop) But honestly thats the fun in testing this stuff out
Click to expand...
Click to collapse
Me too.
Is there anyone that can share privately the V3 version with me ? :fingers-crossed:
here is something better:
http://forum.xda-developers.com/lg-g2/development/rom-cyanogenmod-12-0-lg-g2-t2944269
Jam4l said:
here is something better:
http://forum.xda-developers.com/lg-g2/development/rom-cyanogenmod-12-0-lg-g2-t2944269
Click to expand...
Click to collapse
TY !
Can anyone port the Nexus 5 ROM?
Updating this thread later today if nothing gets in the way.
Hi everybody!!
I need a tester please:
I built pure AOSP for the D802 from sources of Android right now, has anybody time to test it?
It is an experimental build and I didn't test it right now, so I don't know if it is working, please make a backup from your current rom.
The build comes with an built in CWM recovery and should be with root access. It can be flashed with the same instructions like the CM 12 build.
Edit: Bootloop right now ... Anybody, can you take a logcat?
http://builds.hubdroid.com/otherroms/aosp_d802-ota-102.zip
Thank you in advance!! Please anybody who tries it: can you send me a pm?
Flo0008 said:
Hi everybody!!
I need a tester please:
I built pure AOSP for the D802 from sources of Android right now, has anybody time to test it?
It is an experimental build and I didn't test it right now, so I don't know if it is working, please make a backup from your current rom.
The build comes with an built in CWM recovery and should be with root access. It can be flashed with the same instructions like the CM 12 build.
http://builds.hubdroid.com/otherroms/aosp_d802-ota-102.zip
Thank you in advance!! Please anybody who tries it: can you send me a pm?
Click to expand...
Click to collapse
I'd love to test this for you, but I'm on Sprint LS980 Would you mind making a build for us?
iamterence said:
I'd love to test this for you, but I'm on Sprint LS980 Would you mind making a build for us?
Click to expand...
Click to collapse
Yes sure, but right now, I have to solve the bug, that the d802 wouldnt boot, so this may take some more time until I build it for other devices too.
Regards
SlimRoms is a custom android operating system. Our main goal is to offer users a slimmed down yet feature rich alternative to other android operating systems.
The entire SlimTeam work together to bring you this tailor-made beauty straight from Android Open Source Project (AOSP) source code.
All of the sources can be publicly viewed through GitHub and you can stop by our public Gerrit to submit patches of any type.
Slim7 is the project name for SlimRoms based on Android 7.1.1 Nougat and offers the following original features:
Slim Navbar & Hardware key rebinding
Single tap action, long press action, double tap action!-We’ve got you covered.
Slim Actions & Chamber of secrets
Customise your device to the fullest -You’re a wizard!
SlimRecents
A Faster alternative to stock recents -Your device, your choice.
SlimLauncher
An Open source, feature filled launcher! -Make yourself at home
Status bar customisations
Clock and Date? Battery? -More fun than you can shake a stick at.
Important links:
slimroms.org - Our official website and your source for anything SlimRoms related.
Downloads - Slimify your device!
Unofficial Downloads J500F and M - Build0.13
Unofficial Downloads J500FN - Build0.13
For information on bugs, requirements, notes and more, read the second post.
Installation instructions - Follow these steps if you want SlimRoms on your device.
FAQ - Have a question? Consider reading our FAQ first, you might find your answer there!.
Report-bugs - Found a bug? Send it our way!
Kernel Source - The source of your device's kernel.
Get in touch! - You can contact SlimRoms at these places if you have questions, requests or feedback.
Google+
Twitter
Facebook
Disclaimer: We are not responsible for any damages to your device.
Can you pour me some coffee?
XDA:DevDB Information
SlimRoms Slim7 Android Nougat, ROM for the Samsung Galaxy J5
Contributors
EsromG5
Source Code: https://github.com/SlimRoms
ROM OS Version: 7.x Nougat
ROM Kernel: Linux 3.10.x
ROM Firmware Required: Bootloader LP and Modem MM (modem mm for FM works)
Based On: Aosp, Slim
Version Information
Status: Testing
Current Beta Version: Build0.13
Beta Release Date: 2017-02-15
Created 2017-02-15
Last Updated 2017-03-04
Reserved
What works?
RIL (Calls, sms, data)
Bluetooth (also with audio)
Camcorder
Camera general (1080p works fine)
Video Playback
Dados and RIL
Wifi
Audio
Sensors
LED
Flash
Hostpot
InCall
GPS
OTG
FM (use modem MM)
What does not work?
No, you tell me
Notice:
n/a
First
Good job, waiting for FN
second ....
good job bro.. i m so lucky that I own j5f :fingers-crossed:
wooow j5 developement is skyrocking this month, i will install it when theres the proper incall audio (im not crying for fix, just sayin)
Why don't you concentrate first resolving issues on the other roms? What is the sense of releasing every kind of roms but with the same issues?
Booted on FN, but System UI has stopped
Telepracity said:
Booted on FN, but System UI has stopped
Click to expand...
Click to collapse
Without patch?
Deleted
JosephDM said:
Why don't you concentrate first resolving issues on the other roms? What is the sense of releasing every kind of roms but with the same issues?
Click to expand...
Click to collapse
WelI think it is just as good making normal roms. The in-call isue and other bugs are related across all N roms so that means that if it gets fixed on one then you'll have all the other roms fixed in a small matter of time and now you have 3 working Nougat roms instead of one non functioning rom
EsromG5 said:
Without patch?
Click to expand...
Click to collapse
With a patch from lineage os
MM kernel
Amarius1 said:
WelI think it is just as good making normal roms. The in-call isue and other bugs are related across all N roms so that means that if it gets fixed on one then you'll have all the other roms fixed in a small matter of time and now you have 3 working Nougat roms instead of one non functioning rom
Click to expand...
Click to collapse
Not at all. At the moment you have a lot of not working ROM that are not going to work, because if you look at their github, you'll see that authors most likely lack knowledge needed to make them work. Building every ROM available using the same base is a waste of time (and distraction for users) if one can't even fix your issues in one of them. Plus moving to newer version of android without having the previous one fully working is a suicide run. Nougat has a lot of complex changes in it's sources and it doesn't even fully work on some officially supported devices, so don't expect a good ROM of Android 7.1.1 anytime soon and flooding forums with multiple ROMs having the same issues is not going to help it.
Koloses said:
Not at all. At the moment you have a lot of not working ROM that are not going to work, because if you look at their github, you'll see that authors most likely lack knowledge needed to make them work. Building every ROM available using the same base is a waste of time (and distraction for users) if one can't even fix your issues in one of them. Plus moving to newer version of android without having the previous one fully working is a suicide run. Nougat has a lot of complex changes in it's sources and it doesn't even fully work on some officially supported devices, so don't expect a good ROM of Android 7.1.1 anytime soon and flooding forums with multiple ROMs having the same issues is not going to help it.
Click to expand...
Click to collapse
Well... You are right sir. In-call audio is really really important and I wish someone knew why it was happening..
I didn't mean in call audio. I meant this ROM doesn't even boot normally and they have no clue why, yet instead of trying to debug they release bunch of not working builds. Camera doesn't work and it will not work since you'd either have to use updated open source HAL or revert Nougat media changes and it won't be a surprise if I'll tell you they have no idea how to do it. The only real devs, who knew what they were doing left because their work was posted by someone else and now he's making blind commits in hope that things will magically fix themself. They won't. I might as well tell you that development on J5 is dead unless someone new with actual knowledge steps in. Don't expect any significant changes. We can't even take patches from any other msm8916 devices, because they have more advanced development and use a lot of open source projects instead of prebuilt libs like we do. Even camera in CM13 is not fully fixed because open source cam doesn't work for us and after debugging it for 3 weeks I've still didn't come up with reliable solution to make it work (only made some errors dissapear).
Koloses said:
Not at all. At the moment you have a lot of not working ROM that are not going to work, because if you look at their github, you'll see that authors most likely lack knowledge needed to make them work. Building every ROM available using the same base is a waste of time (and distraction for users) if one can't even fix your issues in one of them. Plus moving to newer version of android without having the previous one fully working is a suicide run. Nougat has a lot of complex changes in it's sources and it doesn't even fully work on some officially supported devices, so don't expect a good ROM of Android 7.1.1 anytime soon and flooding forums with multiple ROMs having the same issues is not going to help it.
Click to expand...
Click to collapse
You're not totally sure.
Creating new roms is just to try to see if there are different results and not just to flood the forum with crap.
The name of the forum is XDA - DEVELOPERS, this means that it is of full use to developers, if the person does not know how to help, it just stays silent while someone else can do it. Your help in testing is much appreciated since we are trying to do something free for you, and still prefer to say things like that.
I thank you and respect your concept, but try to help instead.
Amarius1 said:
Well... You are right sir. In-call audio is really really important and I wish someone knew why it was happening..
Click to expand...
Click to collapse
The problem with incall and other stuff is already encountered by SoUnd001, but the big problem is that we're not hitting what it does so it's not booted, you're getting errors with incall and stuff because of the patch you're installing, not because of Rom or current kernel.
NOTICE:
I'm finishing a build for J500FN, we know it may not start properly, but I want to know the result for these users. I hope the sooner I have it all working.
Koloses said:
Not at all. At the moment you have a lot of not working ROM that are not going to work, because if you look at their github, you'll see that authors most likely lack knowledge needed to make them work. Building every ROM available using the same base is a waste of time (and distraction for users) if one can't even fix your issues in one of them. Plus moving to newer version of android without having the previous one fully working is a suicide run. Nougat has a lot of complex changes in it's sources and it doesn't even fully work on some officially supported devices, so don't expect a good ROM of Android 7.1.1 anytime soon and flooding forums with multiple ROMs having the same issues is not going to help it.
Click to expand...
Click to collapse
Considering our device only has Marshmallow we can afford to deal with some bugs. If i read correctly RR 6.0.1 only has the radio bug so we have a working Marshmallow rom. The next logical step is to make Nougat and they do not have a kernel thats Nougat based so thats why they are running into problems and why we have to use patches. Im almost 100% sure that once we get official Nougat to our device, 99% of the bugs in these roms will disappear
[email protected]@!3Z said:
Considering that they have built nougat from source when our device only has Marshmallow we can afford to deal with some bugs. If i read correctly RR 6.0.1 only has the radio bug so we have a working Marshmallow rom. The next logical step is to make Nougat and they do not have a kernel thats Nougat based so thats why they are running into problems and why we have to use patches. Im almost 100% sure that once we get official Nougat to our device, 99% of the bugs in these roms will disappear
Click to expand...
Click to collapse
I think there will not be an official nougat firmware from Samsung.
Gent' said:
I think there will not be an official nougat firmware from Samsung.
Click to expand...
Click to collapse
In the Skies telegram group there was confirmation for official Nougat
EsromG5 said:
You're not totally sure.
Creating new roms is just to try to see if there are different results and not just to flood the forum with crap.
Click to expand...
Click to collapse
FYI: ALL custom ROM are using the same hardware repo's maintained by CAF, CM(Lineage now) or AOSP. There won't be any different results. The most important repos are all the same. The fact that you don't know that and your friend's github sources show that there is nothing to be helped. You're just playing games with users pretending you could make things work. What for? In the end they will be the ones left with nothing but promises. People, who could actually do something left, because someone took their work and published it to take all the applause for it and now you're blindly trying changes hoping they would somehow fix things.
[email protected]@!3Z said:
Considering that they have built nougat from source
Click to expand...
Click to collapse
They built from the source already made by ganesh. Their own changes are blindly trying things that have no right to work in the first place. Builiding android from someone's ready sources is like walk in a park.
Gent' said:
I think there will not be an official nougat firmware from Samsung.
Click to expand...
Click to collapse
Certainly not for J5 2015, maybe 2016 but it could benefit us anyway since these devices are similiar.
I'm done, Moderator will probably soon come and delete my posts since all they care about is keeping forum clean. You may consider this device dead at the moment.
[email protected]@!3Z said:
Considering that they have built nougat from source when our device only has Marshmallow we can afford to deal with some bugs.
Click to expand...
Click to collapse
I understand from your post that Sound001 or EsromG5 did the hard work, but its not like that.
@Nick Verse and @ganesh varma were the ones who built cm12.1 and cm13 from source. They were also working on cm14 source while they were working on cm13.
So, please edit your post and dont mislead people.
Koloses said everything.
Since Nick and Ganesh left J5 development because their project which were working on was posted by someone else, the issues of Nougat CM/AOSP based roms wont be solved.
This:
I might as well tell you that development on J5 is dead unless someone new with actual knowledge steps in.
Click to expand...
Click to collapse
I have the idea for an unified build from quite some time, but only now I'm trying to bring it to life.
Looking at LineageOS github and gerrit you can see that other devices (klte, m8) have the same stupid amount of variants, but they have merged them into one device repo.. So why can't this happen for the Note4?
Following their steps I've created an unified android_device_samsung_trlte (that includes SM-N910F/trltexx, SM-N910G/trltedt, SM-N910T/trltetmo, SM-N910W8/trltecan, SM-N910P/trltespr, SM-N910R4/trlteusc and SM-N910V/trltevzw), this proprietary_vendor_samsung and added this commit to the android_device_samsung_trlte-common that I'm currently using.
For now I'm able to use those repos to build a LineageOS-14.1 build that boots up, but w/o sim and camera being recognized.. For what I've tested (on trltexx) wifi and (strangely) bluetooth are working. Something is probably wrong with specific device blobs not being recognized/used properly.
It needs some work but I think this is a good base to start with.
trltexx/trltedt blobs are from here;
trltetmo/trltecan blobs are from here;
trltespr/trlteusc blobs are from here;
trltevzw is using trltespr blobs for now (there are no guaranteed working blobs repos for it at the moment, the only (WIP) way is to establish which are needed and extract them from hsbadr's builds).
The kernel is the same that I'm using for the not unified builds (android_kernel_samsung_trlte), at the moment testing if the klte's way of using the international variant defconfig works for us too.. other options are to add something like this commit to remove the need of a variant defconfig or merge the different defconfigs into one and use that instead.
Source:
unified_android_device_samsung_trlte
unified_android_device_samsung_trlte-common
unified_proprietary_vendor_samsung
android_kernel_samsung_trlte
I was going to share this anyway, but I'm sharing it now (even if there are still major problems) because I have a very limited free time where I can work on it, so, maybe, someone of you will join/fork/clone this project and help me out, finalizing it earlier and better (the support of experienced developers is needed and much appreciated).
I'm now going to mention the SeniorMembers/RecognizedContributors/RecognizedDevelopers that, maybe, have interest in this project.
@fattire @hsbadr @SaintZ93 @SferaDev @TheBr0ken @ZION959
If you get it to work, @_mone, I'll switch my daily builds to this unified one.
On a related matter, there seems to be a typo in the name of one of your repos: unified_andorid_device_samsung_trlte.
Let me also add @lilferraro to the list of devs, as I use his device tree to build for trltespr.
I built this and it boots, with the same issues you have (no SIM detected, camera is busted). Took a bunch of of logs. Getprop shows ro.build.fingerprint is trltetmo (which is right), ro.bootimage.build.fingerprint is trlte. Wifi and bluetooth are working. Mediaserver/libcameraservice service crashes repeatedly. I agree with you that having a unified tree for the entire Note 4 line is the way to go. I tried manually copying the blobs from /system/blobs/tmo/ to /system/lib and /system/vendor/lib but it didn't help.
what proprietary blobs did you use for sprint?
All device trees for the note 4 pie builds are up at
GitHub.com/tripLr-dev
User forum at Telegram
https://t.me/triplr_dev_users
Thanks to @_mone
And @ripee
I will do a test build of my Ubuntu Touch port using this unified repo and report back if anyone is interested. My port still needs a couple things to work but the stuff that works now should be enough to give me a good idea if it will work or not.
tigerpro357 said:
I will do a test build of my Ubuntu Touch port using this unified repo and report back if anyone is interested. My port still needs a couple things to work but the stuff that works now should be enough to give me a good idea if it will work or not.
Click to expand...
Click to collapse
Let us know what you need
Source code
GitHub.com/triplr-dev
Contact me on telegram t.me/telegram to get you in touch with testers and developers. .
I am EXTREMELY interested in a touch port.
Thanks
Also GitHub.com/underscoremone for all the older stuff
I actually have my work on github already, I am also on telegram in the ubports groups, and if you would like to help my repo is probably the best place to start (unless you prefer duplicating work) I only have sensors and the stylus left for hardware (both of which I have been trying to get working) the stylus is an issue on the ubports side but I dont understand the code enough for mir. I haven't had a chance to test the unified repo yet, but I will once I have a few minutes to actually do it.
I wonder how it work to create xda threads for Ubuntu touch, since they seem to have their own forums.
I think adding Ubuntu touch to xda would be an additional resource for users and developers.
tripLr said:
I wonder how it work to create xda threads for Ubuntu touch, since they seem to have their own forums.
I think adding Ubuntu touch to xda would be an additional resource for users and developers.
Click to expand...
Click to collapse
I agree, as all I really see on xda as far as Ubuntu Touch goes is prebuilt downloads which is good for letting people try it, but when I started I initially looked into xda but found no help. I do hope to see that change in the future though
Nice to see someone actually wanting to still develop for this device.. I love this Note4 still.
doubledragon5 said:
Nice to see someone actually wanting to still develop for this device.. I love this Note4 still.
Click to expand...
Click to collapse
Same here
We have several developers for note 4 snapdragon and exynos
T.me/triplr_dev_users
See you there
Roms
Tiny.cc/triplr
Tiny.cc/ripee
And many links in XDA for ROM threads
Post comments in XDA, and bug reports and logs in telegram
Android 10 in progress
Thanks @_mone
The lineage-17.1 thread is up!
[ROM][UNOFFICIAL][10] LineageOS 17.1 [tblte][trlte][trlteduos]
If you don't mind not having a working fingerprint sensor, or audio through the headphone jack, then Q is stable enough for daily use. As always when coming from an older rom version, it is highly recommended not to waste your time dirty flashing and just clean flash.
Q is still a work in progress, so I will still be releasing Pie builds, though maybe not as often. As in years past, once the Q bugs have been fixed up to the current Pie level, I will post about when my last Pie build will be. I will upload it to the Downloads tab located at the top of each page of this thread, and link it in the OP.
This is unofficial lineageos 16 for Motorola Clark. It is only compatible with nougat firmware - you must have the nougat bootloader and modem flashed on your device.
Tons of thanks to hashbang for all of his work
Kernel Source-
https://github.com/randomblame/android_kernel_motorola_msm8992
Device tree-
https://github.com/randomblame/android_device_motorola_clark
Current status of rom-
Daily Driver
Broken-
Camera post processing- rotation is not accounted for in hal with latest round of hacks credit to AgathosAnthropos for fixing image capture by disabling the calls to pp, hold device in landscape for photos
Tethering - it works but device will soft reboot when tethering stops
Dual sim variants are NOT supported! I do not have the hardware to test and fix at this time - bugreports appreciated
Working - everything else?
Try it yourself (Requires Nougat Firmware and as always wipe data+cache)
Latest Releases:
1/12/2020 https://www.androidfilehost.com/?fid=4349826312261700035
8/1/2019 https://www.androidfilehost.com/?fid=6006931924117928331
Don't forget to grab a compatible version of gapps for 9.0
https://opengapps.org
Once again this rom REQUIRES that the stock nougat firmware was properly flashed to work correctly... It will check before installation that you have the correct modem version installed.
*If your radio does not work you may have the wrong modem
*If you can not switch lockscreen to pin or pattern you may have the wrong modem.
*Modem flashes fail quietly sometimes please make sure you have properly flashed it before reporting issues.
Great! [emoji6]
Enviado desde mi Nexus 5X mediante Tapatalk
I'll be happy to test once there is a working rom
I've been updating op, it seems to just be getting shorter as I fix things. The rom now compiles with default manifest only needs device tree and kernel source now. something is failing quietly and preventing boot. I'm just working the problem slowly getting it sorted out.
Can't wait to see more from this
We wait impatiently.
Spent a couple more hours going through init narrowing it down failure happens just before zygote startsI currently have my pure propped up in charging position so I can work more on it it's had a hard life
Thank You so much
randomblame said:
I've been updating op, it seems to just be getting shorter as I fix things. The rom now compiles with default manifest only needs device tree and kernel source now. something is failing quietly and preventing boot. I'm just working the problem slowly getting it sorted out.
Click to expand...
Click to collapse
I have been searching and search for lineage OS roms for my XT1575 but the bootloader is Ax052 which is not supported by 14.1 Lineage. I Hope you find a fix for this.
Moto X Pure XT1575 said:
I have been searching and search for lineage OS roms for my XT1575 but the bootloader is Ax052 which is not supported by 14.1 Lineage. I Hope you find a fix for this.
Click to expand...
Click to collapse
Hi, I have the Lineague 14.2 installed. What I did to eliminate the bootloader check was to edit the uptader-script
Fixing error caused by missing taskstats kernel feature
Hi randomblame,
A quick review please, could you tell us the intended purpose of your project.
Meaning like I'm thinking it's for a "Moto X Pure 2015 (clark)" device isn't it?
Would that be for everyone on this XT1575 device which has upgraded to a stock Nougat kernel and modem?
Or could/would others benefit from it as well with your research here - other moto's?
Any and all answers - thoughts are welcome in understanding the project...
Thanks for the lady power on XDA,
RIF
This device can have a new future. Think about it !
I will look into bootloader incompatibility once I get it running seems like it shouldn't be a big deal. I'm also toying with the idea of a new kernel 3.18 seems like low hanging fruit considering Motorola was kind enough to give us good searchable git history on GitHub of both kernels and the 3.18 source for the Moto z seems to have most of the msm8992 support still. My next step is going to be a new device tree starting as bare bones as possible and populating it properly to figure out this issue. I'll throw up a PayPal link again later a less broken device would be helpful USB port is bad and this is probably the fourth screen I've installed on it but touch only works when it feels like it lol
randomblame said:
I will look into bootloader incompatibility once I get it running seems like it shouldn't be a big deal. I'm also toying with the idea of a new kernel 3.18 seems like low hanging fruit considering Motorola was kind enough to give us good searchable git history on GitHub of both kernels and the 3.18 source for the Moto z seems to have most of the msm8992 support still. My next step is going to be a new device tree starting as bare bones as possible and populating it properly to figure out this issue. I'll throw up a PayPal link again later a less broken device would be helpful USB port is bad and this is probably the fourth screen I've installed on it but touch only works when it feels like it lol
Click to expand...
Click to collapse
I'm trying to follow along with your posts best as is possible for me - but, so sorry I and as well many others are lame to understand the under-the-hood workings of Android.
Are you saying in such a way that the Moto Pure XT1575, will maybe and with your research efforts move forward to a true PIE OS possibly?
Maybe I'm reading to much into your words.
But, as I follow your posts, you'll advance us Pure device owners beyond the Nougat kernel - or at least try too?
Or yet with your efforts will this yield something like HashBang did for the XT1575 device when a Nougat OS wasn't even a thought of possibility from Motorola for us.
Back then, HashBang had worked the Nougat OS on the Marshmallow kernel and modem - I'm very green to all of this - but that's what I understood.
Still that's good none the less if that will come here from you with PIE on Nougat internals...
Beings Motorola support is dead for our device for anything future of an OS update - not to mention security patches.
If you would spell it out better as any interested XT1575 owners now could grasp the concept here in your efforts - create a buzz for a greater community following. More MXP owners to jump on board as gained support from well wishers.
Is it to early yet for that? Is there a fear that someone could steal it out from under you? Unexpected negativity, or is it just the way you wish to present this to us for the present.
I'm still going to watch and support this project with high hopes no matter what may come in the end...
Could you benefit knowledge from a LineageOS 16 for Moto Z. download?
https://www.cyanogenmods.org/forums/topic/download-moto-z-lineage-os-16-android-9/
For people like me,
Device Tree = https://source.android.com/devices/architecture/dto
and on XDA
https://forum.xda-developers.com/android/software/guide-how-to-make-device-tree-phone-t3698419
As for any active developers still left for the XT1575 a big thank you to you all, seems to me like a daunting task to crawl inside of android moreless understand things once your there...
Kernels are only loosly linked to Android versions, Google maintains the Android-common kernel repos which are usually quite far behind mainline Linux, and caf who maintains Qualcomm specific kernels are further behind in general. Literallyany feature required by Android can be backported to an old kernel I'm sure 2.6.27 could run pie but it would need so many patches it would be an unrecognizable mess. It will become progressively more of a nuisance as time goes on to keep patching up 3.10 Pie "requires" 4.4 for new devices but only needs kernel features from 3.18 which I've backported to 3.10. with each new version of Android more assumptions are made about how modern the devices kernel is and what features it has so moving to a newer kernel would be nice and like I said 3.18 seems doable but it will still be quite a bit of work.
Thank you @randomblame I was able to grasp most of that...
Maybe it's too early but, how does Googles Android security patches figure into this - if they are possible to bring us forth from Oct 2017?
Remembering I'm a laymen to the nuts and bolts of android.
I understand your post #16 - Super !
Security patch version is irrelevant when you are building from the latest source
Obnoxiously after a few builds the dedicated 250gb SSD is full and I have to make clean which takes ages, I nooped every thing but the basics didn't include telephony or wifi, ril, audio, Bluetooth GPS nfc etc and left it to build overnight will test after work trying to narrow down the problem
Surface flinger is the culprit
I have the device laying around and getting no use. Will sure donate some $$$. Seeing a los16 with all working hardware would be great.
Only got a couple hours to work on it this weekend, there is an issue where /system/vendor is not symlinked to /vendor early enough and calls for things in /vendor fail thus the issue, since we don't have a physical /vendor partition it can not be mounted immediately via the kernel. Tis annoying. I can change the calls to /system/vendor or maybe make it symlinked earlier when I get a chance
Hello,
@sir_bazz mentioned that this needed its own thread, thus I'm creating one.
I've been building LineageOS 14.1 from the official LineageOS source repository for my personal devices for some time now, and it finally occurred to me that others might find them useful.
These builds are created every Saturday night from a 100% unaltered LineageOS repository, which is synchronized with upstream every day. I must stress that there are NO MODIFICATIONS at all; if it worked/didn't work in the last official Cyanogenmod/LineageOS releases, it works/doesn't work in my builds. At Apple we called these "sustaining builds" -- they keep devices in sync with the latest security patches, but receive no new features.
Deb is at https://lineageos.disavowed.jp/deb/. Flo is at https://lineageos.disavowed.jp/flo/. There are other devices being built as well ... if you would like me to add a 14.1 or 15.1 device to the weekly build roster, please let me know.
I hope this helps out folks who want to extend the service lifetime of their gear. Share and enjoy.
Edit: per moderator request, I need to provide a link to the source repository used to generate these builds to comply with XDA's interpretation of the GPL. It is the stock LineageOS repository, located at git://github.com/LineageOS/android.git. TheMuppets binary repository was used for the vendor blobs; it is at https://github.com/TheMuppets/
Have been testing the latest weekly for a couple of days now, and no issues to report.
My Deb device is relegated to a dedicated Pogo tablet and I think Lineage 14.1 is a better match for my use as there's noteably more memory available after system startup than with the Pie ROMs I've tested.
It just feels much smoother.
Would've been more than happy with monthly updates but thanks for building the ROM and also making weeklies available for us Nexus 7 diehards.
sir_bazz said:
Have been testing the latest weekly for a couple of days now, and no issues to report.
My Deb device is relegated to a dedicated Pogo tablet and I think Lineage 14.1 is a better match for my use as there's noteably more memory available after system startup than with the Pie ROMs I've tested.
It just feels much smoother.
Would've been more than happy with monthly updates but thanks for building the ROM and also making weeklies available for us Nexus 7 diehards.
Click to expand...
Click to collapse
Likewise. I was just about to junk a (relatively) new N7 (flo) on stock MM. but wanted to give a newer ROM a try (Oreo). I didn't like my O options and stumbled upon these N builds on the backend of another thread. Flashed/Magisk couple Mods. Been up a week now and not one problem whatsoever!
Really appreciate the work as this ROM (I had never used a LinOS rom before) is running so well the N7 is almost my daily house driver again. The N7 FF really has never been matched/surpassed and once you've become accustomed to it its just hard to give up that "sweet spot".
wileyc said:
Hello,
@sir_bazz mentioned that this needed its own thread, thus I'm creating one.
I've been building LineageOS 14.1 from the official LineageOS source repository for my personal devices for some time now, and it finally occurred to me that others might find them useful.
These builds are created every Saturday night from a 100% unaltered LineageOS repository, which is synchronized with upstream every day. I must stress that there are NO MODIFICATIONS at all; if it worked/didn't work in the last official Cyanogenmod/LineageOS releases, it works/doesn't work in my builds. At Apple we called these "sustaining builds" -- they keep devices in sync with the latest security patches, but receive no new features.
Deb is at https://lineageos.disavowed.jp/deb/. Flo is at https://lineageos.disavowed.jp/flo/. There are other devices being built as well ... if you would like me to add a 14.1 or 15.1 device to the weekly build roster, please let me know.
I hope this helps out folks who want to extend the service lifetime of their gear. Share and enjoy.
Click to expand...
Click to collapse
Hi, I've just updated both my Hammerhead 15.1 and Flo 14.1. Everything has gone smoothly and all is working. I was just hoping you could clarify something that occurred to me regarding the builds.
When you say there are no modifications, does that mean that the basic ROM is frozen at the point when LineageOS stopped releasing official builds, and does that also mean that builds in between the monthly security updates are all the same or can there be other security/bug fixing updates from LineageOS? Also Lineage 15 was never official for the Nexus 5 or 7? I'm a bit in the dark as to how these things work.
Thanks in advance.
anivegmin said:
Hi, I've just updated both my Hammerhead 15.1 and Flo 14.1. Everything has gone smoothly and all is working. I was just hoping you could clarify something that occurred to me regarding the builds.
When you say there are no modifications, does that mean that the basic ROM is frozen at the point when LineageOS stopped releasing official builds, and does that also mean that builds in between the monthly security updates are all the same or can there be other security/bug fixing updates from LineageOS? Also Lineage 15 was never official for the Nexus 5 or 7? I'm a bit in the dark as to how these things work.
Thanks in advance.
Click to expand...
Click to collapse
No worries. By "no modifications", I mean that these are built directly from a clone of the LineageOS repository. I've made absolutely no changes to the source code. No kernel tweaks, no new features, no hidden spyware, no bugfixes (no matter how much I am tempted to do so!).
The LineageOS folks merge the monthly Google security patches into the 14.1 and 15.1 trees, but they don't make official builds for devices that no longer have a maintainer. Their official recommendation is to build it yourself if you want to keep your devices patched, but a non-trivial number of users can't make their own builds, so ...
... since I'm doing builds for my own devices anyway, it would be a good thing to make them available to others. Thus I have done so
Edit: argh, rereading I realize I didn't directly answer your exact question. From an end-user perspective, these builds are indeed frozen in time compared to the last official LineageOS build. Security patches happen as described above.
The Nexus 7 never received an official 15.1 build as far as I can tell, so I'm generating 14.1 for it.
The Nexus 5 is a bit of a grey area, in that builds generated from the 15.1 branch work fine with the exception of Bluetooth (from what I hear, as I don't use Bluetooth on my device). It appears to require a device repartition if you want to use Google apps, though, so I'm building both 14.1 and 15.1 to keep options option.
wileyc said:
No worries. By "no modifications", I mean that these are built directly from a clone of the LineageOS repository. I've made absolutely no changes to the source code. No kernel tweaks, no new features, no hidden spyware, no bugfixes (no matter how much I am tempted to do so!).
The LineageOS folks merge the monthly Google security patches into the 14.1 and 15.1 trees, but they don't make official builds for devices that no longer have a maintainer. Their official recommendation is to build it yourself if you want to keep your devices patched, but a non-trivial number of users can't make their own builds, so ...
... since I'm doing builds for my own devices anyway, it would be a good thing to make them available to others. Thus I have done so
Edit: argh, rereading I realize I didn't directly answer your exact question. From an end-user perspective, these builds are indeed frozen in time compared to the last official LineageOS build. Security patches happen as described above.
The Nexus 7 never received an official 15.1 build as far as I can tell, so I'm generating 14.1 for it.
The Nexus 5 is a bit of a grey area, in that builds generated from the 15.1 branch work fine with the exception of Bluetooth (from what I hear, as I don't use Bluetooth on my device). It appears to require a device repartition if you want to use Google apps, though, so I'm building both 14.1 and 15.1 to keep options option.
Click to expand...
Click to collapse
OK. Thanks for the explanation. Sorry to ask again, but does that mean that I only have to update once a month for the security updates, and that the other weekly builds are basically just repeats? Or am I misunderstanding?
anivegmin said:
OK. Thanks for the explanation. Sorry to ask again, but does that mean that I only have to update once a month for the security updates, and that the other weekly builds are basically just repeats? Or am I misunderstanding?
Click to expand...
Click to collapse
They're repeats. I'm doing them weekly to reduce the amount of time between the security patch hitting the tree and having a patched build available.
wileyc said:
They're repeats. I'm doing them weekly to reduce the amount of time between the security patch hitting the tree and having a patched build available.
Click to expand...
Click to collapse
OK. That's clear now. Thanks for your time.
smw6230 said:
I was just about to junk a (relatively) new N7 (flo) on stock MM
(...)
the N7 is almost my daily house driver again. The N7 FF really has never been matched/surpassed and once you've become accustomed to it its just hard to give up that "sweet spot".
Click to expand...
Click to collapse
Outstanding. That is exactly the reason why I'm making these builds. There's no reason to trash perfectly good hardware. Kudos to the LineageOS folks for keeping the tree patched -- the only thing missing were, um, actual builds.
Hi !
Thank you for your LOS 14.1 updating release, but I have error 7 with TWRP when I try flash it.
arkansis said:
Hi !
Thank you for your LOS 14.1 updating release, but I have error 7 with TWRP when I try flash it.
Click to expand...
Click to collapse
Make certain you're flashing the correct image. Boot into the bootloader and verify that the platform is the same as the build variant you are flashing. Good luck.
Thank you so much for this @wileyc , is possible to add 15.1 for flo?
Enviado desde mi Nexus 7 mediante Tapatalk
Thank you so much for keeping 14.1 alive!!!
DorianX said:
Thank you so much for this @wileyc , is possible to add 15.1 for flo?
Click to expand...
Click to collapse
I'm afraid not. These are built from unmodified LineageOS source repo; I'm just providing sustaining builds, not doing new development/porting.
Thank you for these!! This rom runs perfect on the FLO. I hope you continue the updates for a long time!!
wileyc said:
There are other devices being built as well ... if you would like me to add a 14.1 or 15.1 device to the weekly build roster, please let me know.
Click to expand...
Click to collapse
Good day sir, would you consider adding to the roster and doing sustaining builds for the Moto Z Play, https://wiki.lineageos.org/devices/addison?
Many thanks for providing these builds for the Nexus 7 2013.
braveheartleo said:
Good day sir, would you consider adding to the roster and doing sustaining builds for the Moto Z Play, https://wiki.lineageos.org/devices/addison?
Click to expand...
Click to collapse
No problem at all. I've added it to the weekly roster, and a one-off build is at https://lineageos.disavowed.jp/addison/.
wileyc said:
No problem at all. I've added it to the weekly roster, and a one-off build is at https://lineageos.disavowed.jp/addison/.
Click to expand...
Click to collapse
Awesome turnaround sir. And thank you very much. ?
Thanks for running these builds! Out of curiosity what's the monthly cost like? You running these on a home machine or something like DigitalOcean?
Hi. One Question, can i update over last zeelogs LOS Build?