Related
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.
Hi Guys, it's been so many days Kernel Sources are released, and Syhost Provided Lollipop with RIL Bug, but now the excitement is increasing day by day. When the sources weren't released, Developers were saying to wait until Kernel Sources are released , to fix major bugs. But still no response. I appreciate Developers for Providing Custom Kernels and Updated Scripts in previous Roms.
I request you to post all Lollipop Related News over here. and about Developers work on Github.
Thankyou.
well,
just a suggestion
if u just want to know the LP work progress and collect the news/info into this thread,
maybe u should change the title,
cause the title it's little 'demanding'
and for the first start, maybe u could collect the link and put in here,
also give some brief update about the progress, for example
1. Mokee 5.0.1 (link to source thread/info) - status WIP - RIL bugs
and so on...
cheers
naved97 said:
Hi Guys, it's been so many days Kernel Sources are released, and Syhost Provided Lollipop with RIL Bug, but now the excitement is increasing day by day. When the sources weren't released, Developers were saying to wait until Kernel Sources are released , to fix major bugs. But still no response. I appreciate Developers for Providing Custom Kernels and Updated Scripts in previous Roms.
I request you to post all Lollipop Related News over here. and about Developers work on Github.
Thankyou.
Click to expand...
Click to collapse
asking for ETA both explicit or implicit is a no no no... it's top rules in XDA.
if you want it really soon, use Mokee by syhost and try to fix RIL bug using kernel source code.
beside how hard is to see armani-dev commit in CM12 in github?
https://github.com/armani-dev/android_device_xiaomi_armani/commits/cm-12.0
Sorry I didn't get you.?
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 .
If, like me, you despaired of CM ever releasing another "stable" version of CM-11, your wait is over.
I found out they had FINALLY done another M-SNAPSHOT code freeze, so I synced the source and built one of my own.
http://d-h.st/aihU
Link to Kernel source (if you feel you need it)
https://github.com/CyanogenMod/android_kernel_samsung_hlte
-blaine
Frankenbiker said:
If, like me, you despaired of CM ever releasing another "stable" version of CM-11, your wait is over.
I found out they had FINALLY done another M-SNAPSHOT code freeze, so I synced the source and built one of my own.
Link removed. Apparently we can't post links to builds any more without a full kernel code dump in the post.
If anyone is actually interested, PM me and I'll send you the link.
-blaine
Click to expand...
Click to collapse
This has been the case for as long as XDA has been GPL compliant. Any distribution of a binary (meaning kernel boot,img) that is not unmodified manufacturer's stock requires a link to kernel source, not a code dump. Anyone building CM from source should have no issues getting the link to source code and including it.
Frankenbiker said:
If, like me, you despaired of CM ever releasing another "stable" version of CM-11, your wait is over.
I found out they had FINALLY done another M-SNAPSHOT code freeze, so I synced the source and built one of my own.
http://d-h.st/aihU
Link to Kernel source (if you feel you need it)
https://github.com/CyanogenMod/android_device_samsung_msm8974-common
-blaine
Click to expand...
Click to collapse
There is no kernel source in that link. Please post proper kernel source.
Edit: Thank you for updating the link to kernel source
SlimRoms is a custom android operating system. The main goal is to offer users a slimmed down but still 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 the public Gerrit to submit patches of any type.
Important links:
slimroms.org - The official webpage where you find everything you need to know about SlimRoms.
Downloads - Download the rom for S6 from here
Kernel Source - The source of your device's kernel.
Get in touch! - Contact SlimRoms at these places if you have questions, requests or feedback.
Google+
Twitter
Facebook
Thanks!
The entire team who helped with the device tree to make this device get CM. Hats off guys. Really appreciate your hard work.
For dual boot, kindly follow this link.
If you have any other queries, kindly see this link for any issues other users face before posting here.
Working and Not working:
Everything as in CM
/* Supported devices */
Galaxy S6 International (SM-G920F/I, zerofltexx)
Galaxy S6 SK (SM-G920S, zeroflteskt)
Galaxy S6 KT (SM-G920K, zerofltektt)
Disclaimer: SlimRoms are not responsible for any damages to your device.
XDA:DevDB Information
SlimRom 6.0 for Galaxy S6 , ROM for the Samsung Galaxy S6
Contributors
a2441918
ROM OS Version: 6.0.x Marshmallow
Version Information
Status: Testing
Current Beta Version: 0.2
Beta Release Date: 2015-12-21
Created 2015-12-16
Last Updated 2015-12-23
No offense but you're the 3rd one to release a rom that has the exact same source as the original CM13 thread, and all others have been shutted down. You should invest your time helping the main branch fixing their stuff instead of dividing everybody. Releasing a ROM that is exactly the same with a different name is a total lack of respect to those who really worked hard to make this happen, plus your sources are not even public :/
virulentt said:
No offense but you're the 3rd one to release a rom that has the exact same source as the original CM13 thread, and all others have been shutted down. You should invest your time helping the main branch fixing their stuff instead of dividing everybody. Releasing a ROM that is exactly the same with a different name is a total lack of respect to those who really worked hard to make this happen, plus your sources are not even public :/
Click to expand...
Click to collapse
I have no sources. I have published the link to the kernel source. Every Rom is based off CM tree and it is not the same. Its SLIM.
a2441918 said:
I have no sources. I have published the link to the kernel source. Every Rom is based off CM tree and it is not the same. Its SLIM.
Click to expand...
Click to collapse
I'm pretty sure it's an XDA rule to publish the source of every rom/kernel. Otherwise it could contain malware/keylogger or could be fake. I took a look at SLIM's github and i didn't see anything related to the S6.
Dude you dont get it. According to XDA you should publish a source for the kernel and I did. Go ahead with the link I posted and it will direct you to the kernel source. It is not necessary that the kernel should belong to Slim.
I see no official source on your GitHub. Is this just a rebrand of CM 13 for S6?
Nevermind keep it coming
Sent from my SM-G920F using Tapatalk
bio4554 said:
I see no official source on your GitHub. Is this just a rebrand of CM 13 for S6?
Click to expand...
Click to collapse
Dude, I used Slim rom sources and this device kernel and vendor tree and built the rom. There is no need for sources in my github. And Slim and CM are different. I am not just rebranding. I am building this from source.
a2441918 said:
Dude, I used Slim rom sources and this device kernel and vendor tree and built the rom. There is no need for sources in my github. And Slim and CM are different. I am not just rebranding. I am building this from source.
Click to expand...
Click to collapse
It's like steeling the bigmac sauce's receipe to make your own burger restaurant, but saying that you use a different bread.
Omg whats the issue with you guys? I gave credit for the developers, linked to the kernel tree of the actual developer and now what is that you people need?
a2441918 said:
Omg whats the issue with you guys? I gave credit for the developers, linked to the kernel tree of the actual developer and now what is that you people need?
Click to expand...
Click to collapse
http://forum.xda-developers.com/gal...yanogenmod-13-galaxy-s6-t3269984/post64321767
Having a second ROM with same issues doesn't help at all. Why wouldn't you wait for it to be stable instead of releasing another alpha rom?
virulentt said:
http://forum.xda-developers.com/gal...yanogenmod-13-galaxy-s6-t3269984/post64321767
Having a second ROM with same issues doesn't help at all. Why wouldn't you wait for it to be stable instead of releasing another alpha rom?
Click to expand...
Click to collapse
You could have pointed that out in the first post itself rather than us spamming this thread. I will remove the download link and keep this thread closed for now.
virulentt said:
I'm pretty sure it's an XDA rule to publish the source of every rom/kernel. Otherwise it could contain malware/keylogger or could be fake. I took a look at SLIM's github and i didn't see anything related to the S6.
Click to expand...
Click to collapse
The only source required to be posted by GPLv2 and XDA requirements is kernel source. Also Slim and CM both have posted open permissions to build.
New build up. See OP for download link.
Download Link is dead for me.
a2441918 said:
New build up. See OP for download link.
Click to expand...
Click to collapse
ripv2 said:
Download Link is dead for me.
Click to expand...
Click to collapse
Try it out now mate.
Up and reachable Ill give it a shot!
a2441918 said:
Try it out now mate.
Click to expand...
Click to collapse
Any changelog ? and is this usable for edge version ? or it has same screen issue ?
bigbossclk said:
Any changelog ? and is this usable for edge version ? or it has same screen issue ?
Click to expand...
Click to collapse
I guess its usable. But a different build for S6 Edge is in the works.
Doesnt Boot on my 920f latest recovery clean install with and without gapps. Never finnishing Boot animation.