Hi,
I'd like to know if we might get an AOSP based ROM like Resurrection Remix or Lineage OS someday. Anyone working on something?
I really hate TouchWiz my phone seems clunky with it.
Thanks in advance
PS: not asking for an ETA btw just if we might get something within say a year
Edit: talking about A5 BTW
i think that the better thing is to contact Lineage for ananswer ....
without Lineage ( same with cyanogenmod before) there are not customs roms because these teams use Lineage work .
The another way for customs devs is to use AOSP google sources and phone three sources (not builded for thos phone at this time ===> it's loooooong and hard to build this source itself it need knowledges and generaly all teams and others devs use these ones already built by lineage with manufacturers like samsung sources)
Related
I managed to compile cm12.1 for the D800 using vendor and device files from TheMuppets, and Kernel from Lg-devs.
I dirty flashed over cm12, still discovering issues. You MUST flash a cm12.1 gapps if you had gapps before or you will boot loop. Also highly recommend uninstall/re-install other google apps (like "keep").
Works:
Booting up
Wifi
LTE Data(using T-mobile APN)
Voice
Rotation (be sure you have the latest baseband)
I have the OEM case with the window on it for the watch thing:
The watch thing doesn't appear because that is not implemented(yet) in CM but it does sleep and wake with the magnet thing.
Knock to Wake
Double tap status bar to sleep
Stuff not tested:
LTE or voice on AT&T APN (I use T-mobile on this device) Please provide feedback
pretty much everything else
Not Working:
Does not grant me 3 wishes even if one of those wishes is for an iPhone
Download here:
Removed by OP for now
Contributors
SergeantWagner, cyanogenmod, TheMuppets, CAF
ROM OS Version: 5.1.x Lollipop
ROM Kernel: Linux 3.4.x
ROM Firmware Required: LG G2 D800
Based On: CyanogenMod
Version Information
Status: Nightly
Created 2015-06-30
Last Updated 2015-06-30
reserved
Do you have @Rashed97 consent and permission? Just like the thread below, this will probably get closed.
http://forum.xda-developers.com/lg-g2/development/cm12-1-caf-5-1-1-variants-dt2w-t3122206
I have not. I'll reach out to him and see what's up. Closing this thread in the mean time (if I can figure out how)
Edit: could not figure out how to close the thread so I took down the download links.
SergeantWagner said:
I have not. I'll reach out to him and see what's up. Closing this thread in the mean time (if I can figure out how)
Edit: could not figure out how to close the thread so I took down the download links.
Click to expand...
Click to collapse
It's all good man, just wanted to inform you that Rashed didn't want his CM sources out yet until finished and didn't want ya getting 'punished' so to speak
Pseudo_Soldier said:
It's all good man, just wanted to inform you that Rashed didn't want his CM sources out yet until finished and didn't want ya getting 'punished' so to speak [emoji14]
Click to expand...
Click to collapse
However, there are at least 5-6 roms which are using these sources, so... [emoji14]
Because, as far as I'm concerned - RR, Bliss, 2x Euphoria, AICP and some builds by zg85 (for d802) - all of them are more or less based on lg-devs sources.
Hbohd said:
However, there are at least 5-6 roms which are using these sources, so... [emoji14]
Because, as far as I'm concerned - RR, Bliss, 2x Euphoria, AICP and some builds by zg85 (for d802) - all of them are more or less based on lg-devs sources.
Click to expand...
Click to collapse
From how I understand it, those use official CM sources as Rashed has not pushed CAF into CM yet. Yes they work on the CAF bootstacks but are not fully based on the rest of Rashed CM work. It's confusing to me tbh, I was simply referencing the previous closure not stating rules or anything. No source has been posted for these builds in OP so I can't be sure.
Hbohd said:
However, there are at least 5-6 roms which are using these sources, so... [emoji14]
Because, as far as I'm concerned - RR, Bliss, 2x Euphoria, AICP and some builds by zg85 (for d802) - all of them are more or less based on lg-devs sources.
Click to expand...
Click to collapse
Right, and drgravy is a member of lg devs, so he is allowed to use his own work.
Other ROMs have seaked permission from rashed and the lg devs.
The problem is people go all lolololololololopensource and don't have enough respect to ask the guys working on it, and giving proper credits.
I reached out to @Rashed97 to see what I can do to help move things along, my main goal was to try to get official nightlies kicked off for the D800, and using the sources mentioned in the OP it has been stable for me for about a day so far. It looks like his main concern with the linked post was it may be dangerous to flash with the wrong bootstacks and he doesn't want peeps to claim his work as their own. Perfectly understandable. So I won't upload builds until rashed is cool with it, but if you want to try this yourself you can compile using the sources mentioned above with minimal configuration changes. I got my d800 on the cheap from e-bay so I'm not too worried about bricking it, but if you are worried about yours maybe you should just wait .
What would it take to see a base AOSP ROM put together for the LG G4? I know there's some folks working hard at bringing CM to the G4, but what about an AOSP unmodified ROM with drivers, of course? I've always wondered if that is a better option than say a ROM like CM which has loads of known bugs and issues.
Maybe an AOSP super-stock setup which we could modify after via Xposed / Mods to add in what we want would be a better option?
CJ-Wylde said:
What would it take to see a base AOSP ROM put together for the LG G4? I know there's some folks working hard at bringing CM to the G4, but what about an AOSP unmodified ROM with drivers, of course? I've always wondered if that is a better option than say a ROM like CM which has loads of known bugs and issues.
Maybe an AOSP super-stock setup which we could modify after via Xposed / Mods to add in what we want would be a better option?
Click to expand...
Click to collapse
After we finish the device tree and everything is working, it can be then used to build whatever Rom you desire
You rock, thank you for the quick response! I'm not even sure what kind of rom I desire. I just know it would be neat to go full on basic AOSP and add from there without some of the clutter and bugs introduced with CM's stuff, although CM has always been an enjoyable experience. Whoot for guys like you!
I know this is old thread... but what source tree are we talking about here? Obviously not AOSP itself, i think... right?
CM source?
Maybe i'm missing something about branches of AOSP... and other trees..
many thanks
mythos234 said:
After we finish the device tree and everything is working, it can be then used to build whatever Rom you desire
Click to expand...
Click to collapse
thenextdon13 said:
I know this is old thread... but what source tree are we talking about here? Obviously not AOSP itself, i think... right?
CM source?
Maybe i'm missing something about branches of AOSP... and other trees..
many thanks
Click to expand...
Click to collapse
They talked about device tree here. An example for a pure AOSP one for the device LG H815 is here:
https://github.com/cile381/android_device_h815
See this for an explanation :
http://wp.me/p6ZeCY-3p
AOSP source contains the sources to build a ROM which are the same for all devices and a device tree is a device specific description on how to build or as the above link states:
“A device tree is a tree data structure with nodes that describe the physical devices in a system”
.
Sent from my LG-H815 using XDA Labs
Thank you, steadfasterX.
That provides some clarity, although I think there is still a bit missing for me--
Ugh, i can't post links because of spam rules.. :-/ makes describing things harder.
How did you find the github cile381/android_device_h815 as being the AOSP tree for that phone? My understanding was that the AOSP main repo is here:
android.googlesource.com
And so related to my question previously.. i guess i'm confused specifically who the 'we' is that mythos234 references, and where that source would be located...
many thanks!
CyanogenMod was brilliant for old devices. You could take CM9, tweak it around, and install it on something like the Galaxy Ace GT-S5830. You could breathe life into an old device.
Will there be older versions of LineageOS to accomplish the same thing? For example, an Android 4.2 Jelly Bean LineageOS? Or will it go no lower than Nougat 7.1?
Doofitator said:
CyanogenMod was brilliant for old devices. You could take CM9, tweak it around, and install it on something like the Galaxy Ace GT-S5830. You could breathe life into an old device.
Will there be older versions of LineageOS to accomplish the same thing? For example, an Android 4.2 Jelly Bean LineageOS? Or will it go no lower than Nougat 7.1?
Click to expand...
Click to collapse
Any device that was actively being developed when CM ended should be picked up by Lineage OS. If the device was no longer supported by CM, it is not likely to be supported now.
It goes back to 6.0.1 but no further.
It will do both, apparently.....
Someone appears to have updated the cm-12.1 branch, FWIW. I'm wondering if they're slowly working backwards.
Sent from my HTC One M8 using Tapatalk
MJPollard said:
Someone appears to have updated the cm-12.1 branch, FWIW. I'm wondering if they're slowly working backwards.
Click to expand...
Click to collapse
That would be my assumption since it's probably a lot easier to find people with knowledge to build CM13/12.1 than people with building knowledge for CM7 per say.
LilAnt530 said:
That would be my assumption since it's probably a lot easier to find people with knowledge to build CM13/12.1 than people with building knowledge for CM7 per say.
Click to expand...
Click to collapse
Funny you should say that, because I had to do just that very thing. I own an old phone (Motorola Atrix 4G) that never officially got support beyond CM7, so I've created my own custom CM7 for it (I'm using it as a glorified media player, but it's also allowed me to hone up on my Android ROM tinkering skills). When CM became LinOS, I created a Github organization (https://github.com/CM-Archive) to preserve the CM "gingerbread" branch, and found that there were a few things that need to be changed in order to make a clean compile. I'd offer to bring the "gingerbread" branch on LineageOS up to date for those few people who really need the CM7 code, as I've already done the work and know what needs to be changed, but as I've never made any contributions to CM or any ROM project, I don't know how to go about it. Can anyone tell me what I need to do? Something easy to follow, not "Get the frimfram and keloplotz the FTL missengibble on the gonfropple."
MJPollard said:
Funny you should say that, because I had to do just that very thing. I own an old phone (Motorola Atrix 4G) that never officially got support beyond CM7, so I've created my own custom CM7 for it (I'm using it as a glorified media player, but it's also allowed me to hone up on my Android ROM tinkering skills). When CM became LinOS, I created a Github organization (https://github.com/CM-Archive) to preserve the CM "gingerbread" branch, and found that there were a few things that need to be changed in order to make a clean compile. I'd offer to bring the "gingerbread" branch on LineageOS up to date for those few people who really need the CM7 code, as I've already done the work and know what needs to be changed, but as I've never made any contributions to CM or any ROM project, I don't know how to go about it. Can anyone tell me what I need to do? Something easy to follow, not "Get the frimfram and keloplotz the FTL missengibble on the gonfropple."
Click to expand...
Click to collapse
That's pretty epic dude! I have an LG Lucid vs840 from that had a CM9 out fot it was considering doing the same thing. As for helping them with their efforts I have no idea where to start.
But I do have a question, do you think it'd be very hard to update the cm7 cm9 or cm11 to Marshmallow devices? This might sound foolish but im still curious lol
The CM repo is moved wholesale to LineageOS, so if you know how to build, you could still build any version you like from the new source, provided that the older version was there previously in CM. I've built Lineage 13 (CM13) for several of my devices just now since I still need Xposed.
You can't expect any useful updates for <CM12.1 though, as CM had stopped working on them long ago. Not worth the extra effort of maintaining them, plus unfixable security holes.
Not looking to maintain them, simply to update them to compile from the LinOS repo. Specifically, the default.xml in the android package needs the references to CyanogenMod changed to LineageOS, and other references need to be changed as well. Once that's done, nothing further needs to be done.
Sent from my HTC One M8 using Tapatalk
Hi im looking for lineageOS 13.0-20170513-nightly-x2 this must be the last official version of that rom right?
i got it at my device but delete the zip and i dont found any working download link...
did someone got it for me please?
thx chris
jhedfors said:
Any device that was actively being developed when CM ended should be picked up by Lineage OS. If the device was no longer supported by CM, it is not likely to be supported now.
Click to expand...
Click to collapse
You say that, but there was CM for my old 2011 LG phone but I would be tremendously surprised if a LOS ROM ever shows up because there doesn't seem to be any active development for that device anymore. Makes me sad because I would love to have LOS on it (and security updates newer than 2012) but I wouldn't bank on it... the newest CM ROM I can find for it is from 2015.
I'm trying to build Stock AOSP (Not LineageOS) straight from Google for the OnePlus 3/3T?
I searched for a guide, but haven't found one.
Thanks in advance!
You can't
AOSP source is available for Pixel and Nexus devices
But you can build CAF for OnePlus 3, is clean and close to AOSP
Sent from my ONEPLUS A3003 using Tapatalk
Since you're doing it on your own I suggest using a rom here as a base GZR recently posted GZOSP a Oreo base for Developers to use as a base for their roms you should check it out it's a great start if you're new to development
liam_davenport said:
Since you're doing it on your own I suggest using a rom here as a base GZR recently posted GZOSP a Oreo base for Developers to use as a base for their roms you should check it out it's a great start if you're new to development
Click to expand...
Click to collapse
That would be doing him a great dis-service. Buy using anothers base you dont learn everything you need and rely on others code way too much. Not to mention if a cm/los issue happens (underlying bug in their base code so you are waiting for them to fix it) This is the reason that whole project will not work.
Starting from scratch is a great start and a place everyone should start
... If he's never built a rom before then starting from scratch is most definitely *not* the place to start. GZOSP would likely be the best place to start as at least you can sync all and it actually builds. Would learn a ton just by figuring out how to remove all the GroundZero naming to make it your "own" rom.
There aren't any default AOSP device tree's available for OP3(you'd *have* to use someone else's code and it would likely require manually fixing it to build) so can't start there really, and good luck trying to find which branch(s) of caf and which repo's you need to build.. Writing device trees from scratch by yourself for aosp is drunkeness unless you've done it before and *know* what you're doing.
--
TLDR: There's no guide because it's not a thing currently. Would start with GZOSP if I were you.
HolyAngel said:
... If he's never built a rom before then starting from scratch is most definitely *not* the place to start. GZOSP would likely be the best place to start as at least you can sync all and it actually builds. Would learn a ton just by figuring out how to remove all the GroundZero naming to make it your "own" rom.
There aren't any default AOSP device tree's available for OP3(you'd *have* to use someone else's code and it would likely require manually fixing it to build) so can't start there really, and good luck trying to find which branch(s) of caf and which repo's you need to build.. Writing device trees from scratch by yourself for aosp is drunkeness unless you've done it before and *know* what you're doing.
--
TLDR: There's no guide because it's not a thing currently. Would start with GZOSP if I were you.
Click to expand...
Click to collapse
I mean in Biology, you don't start at the organism, you start at the atom. You start at the base and build from there.
Hello guys
I am a little android developer who has succeeded to build LinegeOS 14.1 for Xperia E3 device. As I have seen here, this device never had good developers, ROMs or recoveries; but I want to change that.
I have been starting to work on this device some time ago and I think it will not be too complicated to build a decent Nougat ROM for this device and a good recovery (such as TWRP). Since I do not own this device, I need your help to test everything that I can build from git sources.
I have created a group for this on Telegram:
MOD EDIT: Link Removed
You are free to join, but I prefer that people who joins wants to be a tester. And remember, the more testers there are, the better the development will go.
Reserved for announcements
Hello, nice to see something like this. in which phase is project? REGARDS!!!
Also curious if this project is still alive.
I want to test
Hi @rmnhg,
i got an old T3 from my girlfriend so i can do anything i want with it.
How far is your common efforts here https://github.com/infus38/android_device_sony_seagull ?
I see other Yukon devices have stable LOS 14.1.
Can I check out and compile this repo?
Best Regards