Here it is :
1. How exactly are updates pushed to aosp? Are they pushed only when they announce a release like the new 4.0.4? Looking at this page https://android-review.googlesource.com/ it appears the updates are in real time but why is it that we are waiting for 4.0.4?
2. Let's say I build from the latest aosp now including the proprietary drivers specific to my nexus device. Is the result exactly the same as factory ota image? Or does Google make some small specific changes specific to devices?
3. Why is it that non nexus devices that get ICS unofficial roms even after the official release from the manufacturer still lack some functionally? Why is it not possible to use the proprietary libraries and drivers from the official update?
4. Does this page https://android-review.googlesource.com/ include all the changes the Google makes to aosp? What are the important ones compared to 4.0.3?
5. How do rom developers like teamkang or gummy etc port their 4.0.3 roms to 4.0.4? Do they have to add their extra code manually to each file or do code management tools like git take care of everything?
Sorry about the long questions I'm just really curious.
Thanks!
ArmanUV said:
Here it is :
1. How exactly are updates pushed to aosp? Are they pushed only when they announce a release like the new 4.0.4? Looking at this page https://android-review.googlesource.com/ it appears the updates are in real time but why is it that we are waiting for 4.0.4?
2. Let's say I build from the latest aosp now including the proprietary drivers specific to my nexus device. Is the result exactly the same as factory ota image? Or does Google make some small specific changes specific to devices?
3. Why is it that non nexus devices that get ICS unofficial roms even after the official release from the manufacturer still lack some functionally? Why is it not possible to use the proprietary libraries and drivers from the official update?
4. Does this page https://android-review.googlesource.com/ include all the changes the Google makes to aosp? What are the important ones compared to 4.0.3?
5. How do rom developers like teamkang or gummy etc port their 4.0.3 roms to 4.0.4? Do they have to add their extra code manually to each file or do code management tools like git take care of everything?
Sorry about the long questions I'm just really curious.
Thanks!
Click to expand...
Click to collapse
1. All Nexus OS versions are AOSP. We are waiting for the OTA because Google only sends the update to a few people at a time, because sending it to everyone all at once would make their servers very unhappy.
2. You'd just be missing the radio I believe.
3. The proprietary stuff is for their skinned OS versions, and is not necessarily usable for vanilla Android.
4 and 5 are beyond me :/
Sent from my Galaxy Nexus
I s it possible the rooted Galaxy Nexus to get the OTA ICS 4.0.4?
ragnarokx said:
1. All Nexus OS versions are AOSP. We are waiting for the OTA because Google only sends the update to a few people at a time, because sending it to everyone all at once would make their servers very unhappy.
2. You'd just be missing the radio I believe.
3. The proprietary stuff is for their skinned OS versions, and is not necessarily usable for vanilla Android.
4 and 5 are beyond me :/
Sent from my Galaxy Nexus
Click to expand...
Click to collapse
thanks. you misunderstood my first question though. I know that nexus images are based off aosp. What I meant is that the changes on android gerrit review system are public and in real time. So why is it that a release like 4.0.4 is a big deal?
CakraMas said:
I s it possible the rooted Galaxy Nexus to get the OTA ICS 4.0.4?
Click to expand...
Click to collapse
Not the best place to ask this question but I think if you're on yajuko and you have stock bootloader (not cwm) then you may be able to get ota but you'll lose root.
4.0.4 ota is compiled by google from it's internal tree.
What you see in gerrit is the reviewing process for the master branch (and a few others), where everyone can submit, which should be updated (merged) with google internal tree everytime a ota/source gets released.
ArmanUV said:
thanks. you misunderstood my first question though. I know that nexus images are based off aosp. What I meant is that the changes on android gerrit review system are public and in real time. So why is it that a release like 4.0.4 is a big deal?
Not the best place to ask this question but I think if you're on yajuko and you have stock bootloader (not cwm) then you may be able to get ota but you'll lose root.
Click to expand...
Click to collapse
Because those sources are actually not released until google starts the ota update. They develop behind closed doors then release all new code at once with the ota. Some people dont like this but i dont think it matters prrsonally.
---------- Post added at 06:53 AM ---------- Previous post was at 06:51 AM ----------
5. Github has a diff function that can compare any two files and even merge the code together. So the devs likely use diff to check all new code and merge.
4. You can look thru all the commits to actually see the newest code changes to see whats important etc.
bk201doesntexist said:
4.0.4 ota is compiled by google from it's internal tree.
What you see in gerrit is the reviewing process for the master branch (and a few others), where everyone can submit, which should be updated (merged) with google internal tree everytime a ota/source gets released.
Click to expand...
Click to collapse
so Gerrit commits are just a very small percentage of all the changes, right?
and does that mean that ota updates may be (slightly) different from aosp compiles?
and that they are no changes to aosp between releases?
thanks!
ArmanUV said:
so Gerrit commits are just a very small percentage of all the changes, right?
and does that mean that ota updates may be (slightly) different from aosp compiles?
and that they are no changes to aosp between releases?
thanks!
Click to expand...
Click to collapse
gerrit commits to the master branch are most of time submitted by people working outside of google.
yes, compiling from the master branch of aosp is slightly diferent than from compiling through release tags (4.0.3_r1, 4.0.4_r1.1).
tagged releases are the same as an OTA, except it doesn't have radio/bootloader images, since they're binaries. they don't change, ever. now the builds compiled from aosp master branch do change, even if it is only under the hood changes.
Related
CM9 NIGHTLY (UNOFFICIAL SEMI-KANG) FOR CDMA TORO
Hey! This is my first post here on XDA, though I've been a long time user of these very forums, since the OG Droid root.
This is also my first ROM, though the credit should really go to the Cyanogenmod team. This is a pull from the ICS branch of CM's git repository,
built on Ubuntu x64. The proprietary .so files were pulled from Team-Kang's repo, because theirs was the only files I could actually get running.
I'm running this as my main install, and so far there's been no problems at all.
THIS IS NOT STABLE.
This is the equivalent of a nightly from CM, though much less polished. It can be considered a pre-alpha nightly build.
I am not liable for anything this ROM may do to your phone.
I'm doing this because I always enjoyed Cyanogen's ROMs straight without any mods or tweaks. I knew exactly what was running on my
phone. This is a straight pull from git. I haven't included any extra pulls from git or gerrit, nor anything else. It's pure Cyan.
I will do nightly releases of this ROM. CM's source is constantly changing, and I'll try and keep up with that, at least until the
build servers are doing automated nightly compiles.
Download:
thewcubed.com/update-cm-9.0.0-RC0-GN-CDMA-KANG-signed.zip
To install:
Download the ROM to your phone.
Download a GApps zip to your phone. (I use kejar31's zip)
Make sure you have the latest version of CWM's recovery.
Boot to recovery.
Backup your current system and data partitions.
Wipe data, cache, and the dalvik-vm cache. (I always do it twice to be on the safe side.)
Flash the ROM.
Flash GApps zip.
Reboot.
(tentative) Hooray!
If the download is too slow, I'll try and upload this to a couple mirrors. I don't know if my server's going to be able to handle a request flood on a 10Mb/s upload line.
Glad your making a Rom, but...
1) its in the wrong forum and
2) you dont have a link because of your "probation" status of < 10 posts
Good luck with your work though!
Also there's (unofficial) builds by a CM developer in the development section already:
http://forum.xda-developers.com/showthread.php?t=1397122
@kenyu73
I know that this isn't in the Dev section, but I can't switch it yet due to the 10 post limit. It should still be valid in the General section though.
The URL is still valid, simply copying and pasting it begins a download of the zip.
@got_milk
There may be unofficial builds, but those are for GSM devices. I apologize for not clarifying in the title that this is for CDMA/LTE versions of the Galaxy Nexus.
toroidal_loop said:
CM9 NIGHTLY (UNOFFICIAL SEMI-KANG)
Hey! This is my first post here on XDA, though I've been a long time user of these very forums, since the OG Droid root.
This is also my first ROM, though the credit should really go to the Cyanogenmod team. This is a pull from the ICS branch of CM's git repository,
built on Ubuntu x64. The proprietary .so files were pulled from Team-Kang's repo, because theirs was the only files I could actually get running.
I'm running this as my main install, and so far there's been no problems at all.
THIS IS NOT STABLE.
This is the equivalent of a nightly from CM, though much less polished. It can be considered a pre-alpha nightly build.
I am not liable for anything this ROM may do to your phone.
I'm doing this because I always enjoyed Cyanogen's ROMs straight without any mods or tweaks. I knew exactly what was running on my
phone. This is a straight pull from git. I haven't included any extra pulls from git or gerrit, nor anything else. It's pure Cyan.
I will do nightly releases of this ROM. CM's source is constantly changing, and I'll try and keep up with that, at least until the
build servers are doing automated nightly compiles.
Download:
thewcubed.com/update-cm-9.0.0-RC0-GN-CDMA-KANG-signed.zip
To install:
Download the ROM to your phone.
Download a GApps zip to your phone. (I use kejar31's zip)
Make sure you have the latest version of CWM's recovery.
Boot to recovery.
Backup your current system and data partitions.
Wipe data, cache, and the dalvik-vm cache. (I always do it twice to be on the safe side.)
Flash the ROM.
Flash GApps zip.
Reboot.
(tentative) Hooray!
If the download is too slow, I'll try and upload this to a couple mirrors. I don't know if my server's going to be able to handle a request flood on a 10Mb/s upload line.
Click to expand...
Click to collapse
I love seeing new developers come here everyday
One small issue though, this is posted in the wrong section. This should be posted in the GSM Galaxy Nexus Android Development or CDMA Galaxy Nexus Android Development (depending whether its GSM or CDMA)
toroidal_loop said:
@kenyu73
I know that this isn't in the Dev section, but I can't switch it yet due to the 10 post limit. It should still be valid in the General section though.
The URL is still valid, simply copying and pasting it begins a download of the zip.
@got_milk
There may be unofficial builds, but those are for GSM devices. I apologize for not clarifying in the title that this is for CDMA/LTE versions of the Galaxy Nexus.
Click to expand...
Click to collapse
Did you ever ask the guys from cm team before you post the kang build?I dont think this allowed.
Sent from my Galaxy Nexus using Tapatalk
Getting your post count up and then posting in Development would have been the thing to do. This will get lost in General, and I can't see it being moved to Development or everyone and his mate would be using that loophole.
@afilopou The CyanogenMod source is released under the Apache 2.0 license. This ROM isn't built for commercial gain, I'm crediting the CM team as the writers of the code, nor am I attempting to alter the code and then copyright it. The concept of "open-source" is that one can do something like this, building and redistributing.
@Kalavere I'm not trying to get this moved to the Dev. If there's enough interest in it, I'll repost the thread to Dev when I'm able. The problem I had was that there wasn't a vanilla build of CM that I could find anywhere for the CDMA/LTE toro.
toroidal_loop said:
@afilopou The CyanogenMod source is released under the Apache 2.0 license. This ROM isn't built for commercial gain, I'm crediting the CM team as the writers of the code, nor am I attempting to alter the code and then copyright it. The concept of "open-source" is that one can do something like this, building and redistributing.
Click to expand...
Click to collapse
Perfect .Just mention it because i dont want to see another locked thread
Hello, everyone!
Dunno if it was asked before or is it thу right place to ask this, but anyway:
Is CM team going to release official CM rom? May be even someone know how soon it will be? I don't like samsung stock rom because of the bloatware it has, but I think I am not the only one.
Thanks in advance!
kortik9 said:
Hello, everyone!
Dunno if it was asked before or is it thу right place to ask this, but anyway:
Is CM team going to release official CM rom? May be even someone know how soon it will be? I don't like samsung stock rom because of the bloatware it has, but I think I am not the only one.
Thanks in advance!
Click to expand...
Click to collapse
Don't know if there will be an official build, but unofficial build by crpalmer works great.
Rutr said:
Don't know if there will be an official build, but unofficial build by crpalmer works great.
Click to expand...
Click to collapse
Yup, I saw that, just wondering if we will get official anytime soon.
kortik9 said:
Hello, everyone!
Dunno if it was asked before or is it thу right place to ask this, but anyway:
Is CM team going to release official CM rom? May be even someone know how soon it will be? I don't like samsung stock rom because of the bloatware it has, but I think I am not the only one.
Thanks in advance!
Click to expand...
Click to collapse
I've never quite figured out why people get so hung up on "official"... When there is an official build of CM, it will still be me maintaining it and the only differences will be that:
* you'll get nightly and M builds which makes them more frequent
* you'll get slower device specific updates to the core software (right now I change it and build it, when it's official it can take weeks to get a change in the frameworks approved and you won't see it until it's approved).
that said, it will be official but doing so takes effort from me and from other people that are very busy and so all I can say is it isn't official yet.
crpalmer said:
I've never quite figured out why people get so hung up on "official"... When there is an official build of CM, it will still be me maintaining it and the only differences will be that:
* you'll get nightly and M builds which makes them more frequent
* you'll get slower device specific updates to the core software (right now I change it and build it, when it's official it can take weeks to get a change in the frameworks approved and you won't see it until it's approved).
that said, it will be official but doing so takes effort from me and from other people that are very busy and so all I can say is it isn't official yet.
Click to expand...
Click to collapse
Actually before creating this thread I saw your "unofficial" build thread and checked your profile to see if you are somehow connected to CM dev team, but you have no information in your profile. I don't like unofficial builds because often they have something tuned\installed\uninstalled, but I like how CM works and I don't want anything else, this is why I want official build. But in this case I think I should try your build, as you maintain official ones anyway.
Thanks for clarifying this!
kortik9 said:
Actually before creating this thread I saw your "unofficial" build thread and checked your profile to see if you are somehow connected to CM dev team, but you have no information in your profile. I don't like unofficial builds because often they have something tuned\installed\uninstalled, but I like how CM works and I don't want anything else, this is why I want official build. But in this case I think I should try your build, as you maintain official ones anyway.
Thanks for clarifying this!
Click to expand...
Click to collapse
Not necessarily having visibility into any framework changes I've made is a pretty reasonable concern. There's only one change that I have already submitted for review so nothing too magical going on behind the scenes. Everything else is available in my public git repos for anyone to verify.
Most of the time official builds start out as unofficial builds. At least that's what I've noticed.
Presenting CM13 unofficial. Built from mostly pure CyanogenMod sources, with a few tweaks that I try to keep updated on my github. This is only possible due to the work of Ziyan and MWisBest.
Instructions
First time flashing CM13 to your toroplus (or coming from another ROM)?
Unlock & install a recovery
Wipe data & cache partitions
Flash CyanogenMod.
Optional: Install the Google Apps addon package.
Updating from a previous build?
Just install the latest ROM zip. If you had Google Apps installed, they will be reinstalled automatically.
Click to expand...
Click to collapse
Downloads
Latest cm-13.0 build: https://www.androidfilehost.com/?fid=24588212152305191
Final cm-12.1 build: https://www.androidfilehost.com/?fid=24438995911970260
All builds: https://www.androidfilehost.com/?w=files&flid=23531
Unofficial TWRP recovery: https://www.androidfilehost.com/?fid=24459283995311440
Google Apps: http://opengapps.org/
- Platform: ARM
- Android: 6.0
- Variant: pico (recommended), or nano
Bugs
LTE Data does not work. (3G works)
XDA:DevDB Information
UNOFFICIAL CyanogenMod 13.0 (DDK 1.9), ROM for the Samsung Galaxy Nexus
Contributors
musical_chairs
Source Code: https://github.com/CyanogenMod
ROM OS Version: 6.0.x Marshmallow
ROM Kernel: Linux 3.0.x
Based On: CyanogenMod
Version Information
Status: Beta
Created 2014-09-25
Last Updated 2016-07-15
now with Marshmallow!
Will this be updated to work with the new GPU drivers? Thank you!
Sent from my LG-LS980 using XDA Free mobile app
illinoissparks18 said:
Will this be updated to work with the new GPU drivers? Thank you!
Sent from my LG-LS980 using XDA Free mobile app
Click to expand...
Click to collapse
Short answer: yes. I'm going to try grabbing the relevant code from MWisBest's githib. If it turns out to be too involved for my limited skills, it will have to wait until Ziyan submits the changes to CM.
musical_chairs said:
Short answer: yes. I'm going to try grabbing the relevant code from MWisBest's githib. If it turns out to be too involved for my limited skills, it will have to wait until Ziyan submits the changes to CM.
Click to expand...
Click to collapse
OK I am going to be on board with testing for sure. I left a post in the now no longer current official thread that I flashed the last official build yesterday and I had perfect 3G to LTE to 3G handoff, rock solid WiFi strength, basically everything seemed to work very well. I am looking forward to seeing how things progress. I haven't been able to keep any of the official CM builds from bootlooping until now. Hopefully you stick with it because I am getting better performance from this device than I have seen in a long while
Sent from my Galaxy Nexus using Xparent Gray Tapatalk 2
musical_chairs said:
Short answer: yes. I'm going to try grabbing the relevant code from MWisBest's githib. If it turns out to be too involved for my limited skills, it will have to wait until Ziyan submits the changes to CM.
Click to expand...
Click to collapse
Awesome!! Thank you!!
Sent from my LG-LS980 using XDA Free mobile app
I should've had a machete to hack through the jungle of build errors from pulling a modified OmniROM device tree into a CyanogenMod build. Looks like the build is rolling now though, with any luck it might just complete successfully - who knows, it might even boot.
The only thing slower around here than me is my poor old computer.
Its kind of ironic that the Galaxy Nexus was the first official LTE device for Sprint and I am only just recently starting to get LTE on a semi regular basis.
@musical_chairs, take your time with your builds. I assure you that they are appreciated. Now that this device is actually getting decent (for Sprint) signal and still has current builds makes it more enjoyable to use than just about any time I can remember....I just miss Imoseyon's Lean kernels. I got GREAT battery on those. They were compiled in the now deceased (I think) CMRemix ROMs but the LTE is definitely a plus
Update: For now, I have stopped working on building CyanogenMod with the DDK 1.9 drivers. I was ending up with a completely unsustainable mess of a device tree, and was still running into build errors. If new drivers are what you want, use FML. I'll focus on keeping the regular CM builds updated for the time being.
musical_chairs said:
Update: For now, I have stopped working on building CyanogenMod with the DDK 1.9 drivers. I was ending up with a completely unsustainable mess of a device tree, and was still running into build errors. If new drivers are what you want, use FML. I'll focus on keeping the regular CM builds updated for the time being.
Click to expand...
Click to collapse
Link to toroplus build for fml?
Zeinzu said:
Link to toroplus build for fml?
Click to expand...
Click to collapse
I'm following its developements, but haven't had time to try it personally yet.
http://forum.xda-developers.com/galaxy-nexus/sprint-develop/rom-fml-fork-life-10-13-2014-t2903695
Thanks for trying anyhow. I'm glad cm11 still has a fighting chance with the GNex, thanks to you, and all the others who are able to help out.
We're all waiting for cm12 to get to a buildable state. In the meantime, I've been working on upgrading my build box. My old machine was just barely capable of building android, the 'new' one isn't new but it was a real beast in its day. Time for a clean build has dropped from a day and a half to two and a half hours. I'm happy...
jd14771 said:
just curious, how difficult is it to compile roms? Do you need to know how to write your own code or is it over glorified copy and pasting with packages and stuff?
Click to expand...
Click to collapse
I do a lot of copying and pasting, a lot of reading guides, and a whole lot of google-ing. I don't know how to write my own code, but I have lots of experience with applying patches. Compiling roms is not that hard if you're a Linux user, have a working knowledge of the command line, and have a basic understanding of git. Take away any one of those things and it becomes a whole lot harder.
jd14771 said:
Yeah i haven't gotten to play with linux, nor do i know what git's are (i think they are large batch's of code posted in plain text?) . always wanted to try but don't have the time.
Click to expand...
Click to collapse
git is the software the devs use to keep track of changes in the code. Most Android devs have their git repositories on Github, those are probably what you are thinking of. Every little change (called a 'commit') has its own unique hash number. It's pretty amazing, you can look through somebody else's commits and find one that fixes a bug you are working on, or split tens of thousands of changes in half, then in half again, then in half again, etc., and pinpoint the exact commit that causes a bug on your system - though that's more useful in Linux kernel development than in Android.
I don't really have the time either, but it's such a fun hobby...
Using quickboot?
Coming from Vanir. Really like the facility quickboot gives. Anyone "enabled" it? I can't seem actually show the field to turn it on. Settings search finds it, but that's it... Noticed Dev options is hidden also. What's up?
Props for keeping CM11 updated. Really like I can actually use SMS in Hangouts.
I haven't been following the nightly changes since toroplus went dark, but I ran a build today--nothing special, just the latest cm...whatever changes they are. I could post it but don't know if I should make another thread or just link to it in here.
Anything substantial get added to general cm in the last few months?
I tried to run a build of cm12 but it looks like things still aren't ready for building yet, either that or I'm not sure how to switch back and forth between the cm11 repo and cm12 without getting repo update errors.
yotvb531 said:
I tried to run a build of cm12 but it looks like things still aren't ready for building yet, either that or I'm not sure how to switch back and forth between the cm11 repo and cm12 without getting repo update errors.
Click to expand...
Click to collapse
I got cm12 built and booting for toro for the first time today. I'm trying to get mobile data working on that, then I'll give toroplus a shot. Looks like it shouldn't be too much trouble. Feel free to post any of your builds here, or start your own thread if you prefer.
Here's my cm11 build from yesterday--equivalent to a plain nightly. It's been running fine since I dirty flashed it last night. Md5sum is linked as well and noted below.
https://www.dropbox.com/s/lp4j3yayuktmlot/cm-11-20141227-UNOFFICIAL-toroplus.zip?dl=1
https://www.dropbox.com/s/z1b72j7oh70eg5w/cm-11-20141227-UNOFFICIAL-toroplus.zip.md5sum?dl=1
MD5 Sum: e6c265c57e00b4949362d6ff53c9a799
Well I got cm12 built and booting on toroplus, unfortunately the RIL is completely borked, so no cell service at all at this point. I'll keep working on that, in the mean time check out the updated cm11 build in the post right above this one.
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.
Hello,
As some people heard, i really try to get Android Wear 2.0 for our beloved SmartWatch 3.
And it's possible, sources, device trees, all exist to build a working own compiled Android Wear 2.0.
So this thread tells about the current process of the port
PROGRESS
Code:
Repo synced
First build finished (not buildable yet due no blobs included
GAPPS Porting in progress
Fixed to 99% the device tree
Updating Blobs to M1D64T in progress
Using own Device tree
SOURCES
Device Tree for tetra:
https://github.com/Sony-SmartWatch-3-OSS/android_device_tree_tetra_eng_prerelease
Device Kernel for tetra (unmodified):
https://android.googlesource.com/kernel/bcm/+/android-wear-6.0.1_r0.99
(we can use MM kernel on Nougat too, maybe some patches needed but that's okay)
Prebuilts/Blobs for tetra:
https://github.com/Sony-SmartWatch-3-OSS/vendor_prebuilts_tetra
For Discussions go to this thread please: https://forum.xda-developers.com/smartwatch-3/general/companion-thread-android-wear-2-0-t3565693
If you want to help me on this project, write to me via telegram: https://t.me/PDesire
I need that so much any ETA ?
By the way keep up the good work !
Nice to see someone is working on this :victory:
Sent from my Sony Xperia Z5 using XDA Labs
Thanks for your job.
Enviado desde mi Redmi Note 3 mediante Tapatalk
great!!! thanks
Dear PDesire,,
My support can be only moral..... :crying:
And I hoping good news soon from you
Thx again for your great hard work :good:
thankx you great hard work and good luck my friend
I checked out your device tree. It looks like it's based off an Open Devices tree. I don't think we need the following lines
Code:
include device/sony/common-headers/KernelHeaders.mk
-include device/sony/common-kernel/KernelConfig.mk
in BoardConfig.mk.
Also, what about the HALs? Asteroid OS used the system.img from a stock build, but we will need to build from source. I do not think it is open source, as it is not available on google git servers.
EDIT: I do not think building from source will work. This is what I found the Google Android building group:
Certain components of Android (and therefore Wear) come from third parties and have licenses which require the source code to be made available (e.g. the Linux kernel). The components made available via the AOSP repositories for releases like Wear are, afaik, the components which have that type of license.
Wear is a release which has taken the same path as Honeycomb. I can understand that for open source fans and people looking to tinker with a working system it’s somewhat disappointing to see, but those are the choices Google has made.
Click to expand...
Click to collapse
Looks like the only way to go forward is to port it from a pre-compiled version for another watch, like they did for the Galaxy Gear devices.
EDIT 2: Refer:
https://groups.google.com/forum/#!s...nce/android-building/R0r9BBn4M3g/-KexIWTCDwAJ
https://groups.google.com/forum/#!s...nce/android-building/vx0Hcy88Ofs/USxAUaKVAwAJ
These sources are incomplete and only include GPL licensed projects. It is not the complete source, just like google releases preview sources for AOSP preview builds (M, N etc). I suggest you not waste your quota in downloading the source.
drakonizer said:
I checked out your device tree. It looks like it's based off an Open Devices tree. I don't think we need the following lines
Code:
include device/sony/common-headers/KernelHeaders.mk
-include device/sony/common-kernel/KernelConfig.mk
in BoardConfig.mk.
Also, what about the HALs? Asteroid OS used the system.img from a stock build, but we will need to build from source. I do not think it is open source, as it is not available on google git servers.
Click to expand...
Click to collapse
Yeah I've seen these, and already fixed. Patch comes soon.
Things for WLAN and BT for example are on google repo too and if a library or something is missing we can use it from M1D64T
EDIT: I do not think building from source will work. This is what I found the Google Android building group:
Looks like the only way to go forward is to port it from a pre-compiled version for another watch, like they did for the Galaxy Gear devices.
EDIT 2: Refer:
https://groups.google.com/forum/#!s...nce/android-building/R0r9BBn4M3g/-KexIWTCDwAJ
https://groups.google.com/forum/#!s...nce/android-building/vx0Hcy88Ofs/USxAUaKVAwAJ
These sources are incomplete and only include GPL licensed projects. It is not the complete source, just like google releases preview sources for AOSP preview builds (M, N etc). I suggest you not waste your quota in downloading the source.
Click to expand...
Click to collapse
Lel then I can't understand why the build is working xD at least I am building in time and already 14% finished
I know some libs we have to grab from the Marshmallow FW but that shouldn't be a big deal
At least we also need some things from Preview 2 so we can get our AW 2.0 Preview 2 working
So I try my best to grab much from source and if required also from FW, but all in all its possible for our SmartWatch 3 to get Android Wear 2.0
Your PDesire
but there's one thing i don't understand ... why r u using preview 2 instead of a feature complete newer version or the final version?
xpatze85x said:
but there's one thing i don't understand ... why r u using preview 2 instead of a feature complete newer version or the final version?
Click to expand...
Click to collapse
Because there aren't any sources of the final version.
@PDesire :
You're the man...keep up a good work ???
Hey @PDesire , any news? I'm sooooo hyped!!!
Thank bro I hope
Thanks for this!
So current status is:
Code:
Repo synced
First Test build stopped to fix things on device tree
Expected in future:
Code:
Blobs dump
Fully fixed Device tree
Creating vendor for tetra
Adding overlays for framework to device tree
Some mix with armv7-a-neon generic
Gapps Dump
Expected in far future:
Code:
Creating an OSS project for tetra (like sonyxperiadev but for tetra)
So guys I will do more tomorrow as I am awake already from Friday 7AM - 3AM Saturday (right now GMT +1) and working on it and I need my sleep xD
So Goodnight guys and I can confirm our dream of Android Wear 2.0 for SmartWatch 3 comes nearer
Your PDesire
PDesire said:
So Goodnight guys and I can confirm our dream of Android Wear 2.0 for SmartWatch 3 comes nearer
Click to expand...
Click to collapse
And I can confirm my donation is coming when a working build is ready, and I suppose others are coming, isn't it guys? ???
Is it possible that this could give us Android pay or will that only work with official AW2?
Sent from my SM-G920F using XDA-Developers Legacy app
Neo Cortex said:
Is it possible that this could give us Android pay or will that only work with official AW2?
Sent from my SM-G920F using XDA-Developers Legacy app
Click to expand...
Click to collapse
No. That'll only work on an official firmware, unfortunately...
Thank you very much, hope you will finish it without problems~!