Hey, Samsung posted the source code for I897UCKK4 a few days ago. Is there any confirmation if and when AT&T is going to release the ROM? I'm surprised I haven't seen more talk about this in the forums, or updated ROMs from the devs. Is everyone just too infatuated with ICS?
We already knew that...
Sent from my Dell Streak 7 using XDA App
Thanks for comment! that was great.
I've been meaning to ask, and hopefully someone with more knowledge takes some time to clarify this for me.
I've been reading around on the Developement section and apparently the KK4 source Samsung released is a partial source. What exactly is the preferred source hoped for by the devs here at XDA? Source code for ROM from Samsung, source for ROM from ATT? Kernel source?
I know there are some features not present on 897 leaks that are present on i9000 based ROMs (BLN, HSUPA) and I keep reading that source is needed to impalement those features, but which source code exactly?
agreed, I'd love to know the difference.
Yes it's a partial source, only some ROM stuff, which really isn't very helpful.
What we want is source for the kernel so that all of those features you mentioned that I9000 has that the native kernels are lacking.
Although hsupa isn't going to happen, that is in the modem, which is closed source. The trade off fir that is support for the audience chip fire noise cancellation on I897 kernel/modem combos.
There is kernel source, if you unzip it there is ROM(partial) and KERNEL source.
Thanks for clarifying studacris!
Related
We could possibly convince the CM team to cook CM for our device too. We need to request them in their forums.
Please add your requests to these threads.
http://forum.cyanogenmod.com/topic/39663-cm-for-galaxy-r-gti9103/
http://forum.cyanogenmod.com/topic/40719-please-port-cyanogenmod-to-galaxy-r-i9103/
http://forum.cyanogenmod.com/topic/30930-samsung-galaxy-r-z-gt-i9103/
http://forum.cyanogenmod.com/topic/37018-please-give-us-cyanogen-mod-for-samsung-galaxy-r-i9103/
I don't think it's gonna make much difference. None of mods/devs have ever answered to any of those threads.
I think that our guys will port it faster.
m.kochan10 said:
I don't think it's gonna make much difference. None of mods/devs have ever answered to any of those threads.
I think that our guys will port it faster.
Click to expand...
Click to collapse
The reason is the requests are too few for anyone to notice.
The Devs wont make a ROM for just 5 or 6 people. We need to have a mass request.
Let us give it a try
You may be right, It doesn't harm to try. But I don't think creating new threads is a good idea since we already have....nine of them. Opening new threads will just make mods pissed. We need to chose the one major thread - in section Unofficial Ports (that's the place for unsupported devices), and write there.
I agree with you 100%.
But the question is, which thread do we support?
From what I've seen, the cyanogenmod team won't just take on a new phone like that. Maybe after we have a stable unofficial port, but not til then. Look at how the huawei ideos 1850 progressed, it got a lot of attention after someone ported it for themselves, and now it has official CM. keep going guys but if you really want CM then I think it's better to help get AOSP for R than to spam CM forums...
Sent from my GT-I9103 using XDA App
I absolutely agree, that none gets cm just like that: "-please give us cyanogen!" "-Ok here you go"
(There are already nine threads - every new user seems to want to have his own thread Even I opened one in donators lounge )
Another example. I don't remember what it was for device, but users contacted directly one of cm devs and then created a donation thread, collected money and bought him a phone. Once they got CM development started for real.
I think the max what they can do for us is welcome a new developer from us with this device and let him do CM for R :/. Thats could happen with LG GT540 and there was a veeeeeeeeeeeeery big spam about CM for it.
+1
CM is the beast..
I guess after our device gets ICS it will step into the world of real dev'ing.
If someone has good experience with repos and AOSP + CM7 stuff please help me with my git repo here:
http://github.com/EmoBoiix3/android_device_samsung_galaxyr
Although we don't have many devs who own this device, it feels very nice that we have a couple of members who are willing to put their best efforts to port the ROM.
We could show our gratitude and support when they bring out the early builds by donating. Please show your support friends.
+1
Must need cm7
Sent from my GT-I9103 using xda premium
And regarding the ICS for our phone, I can sense some delay. Samsung leaks firmwares frequently during development. Probably because they know that we guys flash it and report bugs here. It would save them time on testing.
Couple of builds have leaked for Galaxy SII.
None for ours yet. Same with Optimus 2x. The users from O2x forum say that the OEMs are waiting for NVidia to release the sources.
We can expect ICS for i9103 in Q2
^^
thats a sad bit of news
ICS
Official ICS for SGR is due Q1 of 2012. I think only after release of the official rom, devs will start working
Good news as the first Tegra 2 device running Android 4 (ICS) will be on sale starting 15 Jan. 2012.
The device is Acer Iconia Tab A200 and it will be a milestone for a ICS port for all the other devices sharing the same CPU/GPU.
The original story here:
Acer Expands Popular Tablet Lineup With Iconia Tab A200, a Full-Featured HD Tablet at an Attractive $329 Price
What about CM?
Hello,
Is anyone still developing of the cyanogenmod for Galaxy R GT-I9103?
I'ld like to offer free allocation for your builds on cyanogenmod.su or any new domain you want!
I have over 1K users, who will be happy to test CM7 or CM9 builds, make bugreports and donate.
Maybe you know someone else who develops cyanogenmod, I'll be grateful for any response.
We have few devs that work on AOSP and CM7. Check these threads:
http://forum.xda-developers.com/showthread.php?t=1558637
http://forum.xda-developers.com/showthread.php?t=1548775
Yes , that's good . If someone in the CM team is good with kernels maybe they can help me
Defy-ing all limits.
I've happily owned a G2X for almost 7 months now, and have used a custom rom for essentially the entire time.
Prior to the G2X, i used the HTC HD2 - a Windows 6.5 phone that gained notoriety after having android ported to it through the hard work of developers.
However, one thing that I feel is truly missing from the development community here is what most HD2 devs did; that is, they disclosed the problems with their ROM in the first post of their threads.
So, rather than having to hunt through a 200+ page thread, not knowing what build people are referring to, in order to find out issues with a ROM, it would very much simplify the ROM selection process if devs would disclose known issues such as "non working camera" etc.
Obviously every issue cant be accounted for, but I think the big ones being posted would help clarify a lot of things.
Thoughts?
Edit:
For example, here's a link to one of tytung's HD2 roms (he's one of the more popular developers for the HD2):
http://forum.xda-developers.com/showthread.php?t=1434860
If you scroll down, you'll see he has a list of "working" and "not working" features.
Nobody has any interest in something like this?
Well the thing is all our rooms are based off stock,cm7, or cm9 in one way or another. So everyone knows of the known issues. If its a weird issue out of the norm its usually stated.
Sent from my Galaxy Nexus using xda premium
Reasoning above doesn't hold up, because each rom has things that are fixed or not fixed individually.
I'm not sure of the reasoning, and i guess different devs might have different reasons. Depending on their priorities and skill levels.
Of course if someone is cooking and theming and/or just vanilla compiling then maybe there's less reason (and perhaps more reason to deemphasize bugs?).
Anyways, i agree that an informative first post with a real change log and working and non working features is a very handy thing to have.
Sent from my LG-P999
kwes1020 said:
Well the thing is all our rooms are based off stock,cm7, or cm9 in one way or another. So everyone knows of the known issues. If its a weird issue out of the norm its usually stated.
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
I don't think everyone knows the issues. In fact, if you're new to the community you certainly wont.
Stating the problems is what sparked a ton of competition in the HD2 dev community. The first guy to fix the camera, first guy to fix bluetooth powerdrain etc always got a ton of donations and a better rep. I just don't see that competition here at all.
I don't care about a custom bootloader image or some custom wallpapers. I care about the issues being fixed, and I would love to know which devs are the ones fixing them!
rkarsk said:
I don't think everyone knows the issues. In fact, if you're new to the community you certainly wont.
Stating the problems is what sparked a ton of competition in the HD2 dev community. The first guy to fix the camera, first guy to fix bluetooth powerdrain etc always got a ton of donations and a better rep. I just don't see that competition here at all.
I don't care about a custom bootloader image or some custom wallpapers. I care about the issues being fixed, and I would love to know which devs are the ones fixing them!
Click to expand...
Click to collapse
It really doesn't matter who fixed them, as long as they're fixed. It's not a competition over here. The devs here help each other, especially with ICS. If one of us has a fix for something, it's shared and we all get it. Majority of the people doing the reading that they're supposed to do know the issues that we have with this phone. It just comes down to, are you willing to read to get all of the facts?
Mr. Apocalypse said:
It really doesn't matter who fixed them, as long as they're fixed. It's not a competition over here. The devs here help each other, especially with ICS. If one of us has a fix for something, it's shared and we all get it. Majority of the people doing the reading that they're supposed to do know the issues that we have with this phone. It just comes down to, are you willing to read to get all of the facts?
Click to expand...
Click to collapse
Exactly. We don't do this for competition. We do this as a hobby and we all learn from each other. And even the best developers out there are still learning. If you think developers do this for money you are sadly mistaken, money is in app development not roms.
We all have families, kids, school, jobs and a real life. Therefore free time is hard to come by.
You can go to any development thread skim over the last two pages and have the known issues.
bluenote73 said:
Reasoning above doesn't hold up, because each rom has things that are fixed or not fixed individually.
I'm not sure of the reasoning, and i guess different devs might have different reasons. Depending on their priorities and skill levels.
Of course if someone is cooking and theming and/or just vanilla compiling then maybe there's less reason (and perhaps more reason to deemphasize bugs?).
Anyways, i agree that an informative first post with a real change log and working and non working features is a very handy thing to have.
Sent from my LG-P999
Click to expand...
Click to collapse
If you can't see the reasoning. Then I would like to see the roms you have posted that are not based on one of the bases I listed.
There is this thing called github that most of us use. If you want a "real" change log its there that you'll find it.
Sent from my Galaxy Nexus using xda premium
kwes1020 said:
You can go to any development thread skim over the last two pages and have the known issues.
Click to expand...
Click to collapse
The above isn't even remotely true.
Are you done speaking for all developers yet? I would guess each one can speak for themselves, don't you think?
kwes1020 said:
If you can't see the reasoning. Then I would like to see the roms you have posted that are not based on one of the bases I listed.
Click to expand...
Click to collapse
I guess your reading comprehension isn't very good. I explained why and how there may be differences. If your experience is mainly doing what I called "vanilla compiling" or theming then I guess I could see how you would generalize that all ROMs will be the same though.
kwes1020 said:
There is this thing called github that most of us use. If you want a "real" change log its there that you'll find it.
Click to expand...
Click to collapse
I'm not sure why you feel the need and give yourself the permission to get up on your high horse here. I'm aware of source control and I was using it and writing C code nearly 20 years ago although I'm not a programmer now nor was I then but thanks for informing me. I also note the lack of a git or other source control published in the first post of your ROM in the dev section. As I'm sure you know many (most?) other ROM's don't either in there.
Not sure what you're afraid of to be getting your back up. Nobody cares if you just barely learned how, or are an expert at, writing code. People will appreciate a community contribution regardless.
bluenote73 said:
The above isn't even remotely true.
Are you done speaking for all developers yet? I would guess each one can speak for themselves, don't you think?
I guess your reading comprehension isn't very good. I explained why and how there may be differences. If your experience is mainly doing what I called "vanilla compiling" or theming then I guess I could see how you would generalize that all ROMs will be the same though.
I'm not sure why you feel the need and give yourself the permission to get up on your high horse here. I'm aware of source control and I was using it and writing C code nearly 20 years ago although I'm not a programmer now nor was I then but thanks for informing me. I also note the lack of a git or other source control published in the first post of your ROM in the dev section. As I'm sure you know many (most?) other ROM's don't either in there.
Not sure what you're afraid of to be getting your back up. Nobody cares if you just barely learned how, or are an expert at, writing code. People will appreciate a community contribution regardless.
Click to expand...
Click to collapse
Well plainly you have not read the umpteen million threads regarding lg and nvidias lack of open source. If you want the source for any of the roms I've posted that are based off of a stock rom. My source is right there in the rom. Decompile it and look at it. Just like i decompiled it and modded it. You want the source for my cm/aosp based roms its on my github. Want the source for aokp? Its on github and gerrit.
People clearly appreciate my contributions in the android community. I'd say 1000s of downloads and being kanged countless times can prove that. And in case you haven't noticed their aren't many devs in the g2x community. And certainly hardly any of them are going to come answer a thread posted in the wrong section.
Lastly I am not on any high horse nor have I ever been. I have done more then my part to help and contribute to this community. When you post something constructive then you can try to bring your constructive criticism my way.
That is all have a good day. We will post our threads how we want to. Please learn to read a few replies and the answers are there.
Sent from my Galaxy Nexus using xda premium
kwes1020 said:
Well plainly you have not read the umpteen million threads regarding lg and nvidias lack of closed source. If you want the source for any of the roms I've posted that are based off of a stock rom. My source is right there in the rom. Decompile it and look at it. Just like i decompiled it and modded it. You want the source for my cm/aosp based roms its on my github. Want the source for aokp? Its on github and gerrit.
People clearly appreciate my contributions in the android community. I'd say 1000s of downloads and being kanged countless times can prove that. And in case you haven't noticed their aren't many devs in the g2x community. And certainly hardly any of them are going to come answer a thread posted in the wrong section.
Lastly I am not on any high horse nor have I ever been. I have done more then my part to help and contribute to this community. When you post something constructive then you can try to bring your constructive criticism my way.
That is all have a good day. We will post our threads how we want to. Please learn to read a few replies and the answers are there.
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
Pretty sure this response answers the OP's question far better than I ever could have. Thanks for demonstrating.
There is a similar thread in the Captivate section (posted by sixstringsg) so I thought I would bring one here. The purpose of this thread is to encourage people to make KANG builds of CM7&9 and provide a place for them to post links to their builds. KANGS may include code that is not fully tested or they may simply be clean, up-to-date builds straight from the repo... and thus, are lightly supported if at all. If you build KANGS... post them in this thread.
I have been building these KANGS (they really call them UNOFFICIAL's now ) for my wifes phone for a while now and thought it time to post some for you guys. I recently dropped CM7 in favor of taking the wife up to CM9. Most of the builds are "clean"... meaning that I haven't cherry picked any of the changes awaiting approval in gerrit HERE
If you are coming from a Samsung ROM wipe everything. If you are coming from CM7 or another ICS ROM, at least wipe cache, dalvik, and system. You may get away with not wiping data (I do mostly).
Flashing this KANG is an open admission that you hate your phone and are intent on bricking it. I accept no responsibility for any damage that you inflict upon your phone. Kangs from Androtransfer.com WILL download using the phones browser, but you may have to rename the file .zip from .htm before you flash. If you use Firefox or Opera for downloading it, it works properly. For some reason the stock Android browser and Chrome don't parse the link correctly.
Latest KANG... download from here
Flash the 4/29 gapps with CM9. Download from here
If you want to start building CM9 for epicmtd... GO HERE
...more to come later. I will add info about cherry picking, etc...
Once you have your build environment configured, here are a couple of things that I do.
Open the local_manifest.xml (located in .repo folder) adding the following line...
<project name="koush/proprietary_vendor_samsung" path="vendor/samsung" remote="github"/>
This will sync all the samsung proprietary files and basically allow you to make builds for a phone you don't have.
For the epic, I have added these lines...
<project name="CyanogenMod/android_device_samsung_epicmtd" path="device/samsung/epicmtd" remote="github"
<project name="CyanogenMod/android_kernel_samsung_victory" path="kernel/samsung/victory" remote="github"/>
This syncs the kernel source as the kernel is built in-line and is not prebuilt.
<project name="EpicCM/epictools.git" path="epictools" remote="github" revision="ics"/>
Currently epictools allows you to turn off the backlight of the capacitive buttons unless they are pressed. Could be nice if you are watching a movie in bed on your phone.
More details... HERE (github.com/epicCM)
Cherry picking details... coming soon
FIRST!
What's different in that build?
Sent from my SPH-D700 CM9 ANDROID 4.0.4
Zeinzu said:
What's different in that build?
Sent from my SPH-D700 CM9 ANDROID 4.0.4
Click to expand...
Click to collapse
My guess would be nothing... we have unofficials in the gnex forum... that the guy does just to get it out to people quicker... nothing special just faster than their build bot.
Zeinzu said:
What's different in that build?
Sent from my SPH-D700 CM9 ANDROID 4.0.4
Click to expand...
Click to collapse
That build is clean (no cherry picks) built with latest merges from the cyanogenmod ics branch.
so... unofficial "nightlies"?
Thanks for putting this up op
Sent from my SPH-D700
I updated OP to clarify why I posted this thread. Just as you said... to prevent 30 different threads of people posting KANG builds... this will be the ONE.
Since KANGs are ever changing, there is no reason to update the OP as the Kanger will post a link to his latest KANG near the end. We have the same type of threads going in Captivate and Crespo.
If this thread is deemed "not welcome" than by all means delete it. As I see it, interest in the epic is waning. I am merely trying to encourage.
This is intended as a KANG thread... not a thread for my specific kang. It is not the same as the beta 3 version. There have been merges since that ROM was built. Can I name them all? Nope.
lownox said:
This is intended as a KANG thread... not a thread for my specific kang. It is not the same as the beta 3 version. There have been merges since that ROM was built. Can I name them all? Nope.
Click to expand...
Click to collapse
OK to clarify you are saying this is newer than Beta 3 as it has merges not yet incorporated in the official CM9 thread and if anyone else makes a Kang they should just add it in a post? That part won't work. It will make it hard to find individual Kangs. If you can't maintain the OP with others' Kangs then I can stick in links, if everyone thinks this thread is useful and adds something for the Epic community.
Sent from my SPH-D700 using xda premium
I am happy to update the OP with links if other people start making KANGS. Most of the time they will be posting their builds to some central location and people reading the thread can simply follow the link, see what the latest build date is, and choose to download it or not.
My page, for example, says that if the build is anything other than a "clean" build I will note what has been cherry picked. Cherry picks aren't always stable and sometimes they even cause problems. Since there are no "nightlies" for CM9 epicmtd... Kangs are a way to be able to run the latest merged changes and maybe some cherry picks.
In my next build, I will include some cherry picks. All the forums here seem to run a little bit different. I really wasn't expecting the bit of harshness I got here. I guess I took for granted that everyone knew about Kangs (or Unofficial) builds and what they were.
legit rom!
A lot gets merged everyday. merged changes are here.
review.cyanogenmod.com
I am currently making a build with the following cherry picks... It will be building for a while. So TO BE CLEAR... will be a build with all current merged changes and four cherry picks associated with 2 overall changes...
Electrion beam animation
Option to adjust navbar glow animation duration
Here are links to the picks in gerrit. Take a look.
http://review.cyanogenmod.com/#/c/12959/
http://review.cyanogenmod.com/#/c/15578/
http://review.cyanogenmod.com/#/c/16183/
http://review.cyanogenmod.com/#/c/16184/
lownox said:
A lot gets merged everyday. merged changes are here.
review.cyanogenmod.com
I am currently making a build with the following cherry picks... It will be building for a while. So TO BE CLEAR... will be a build with all current merged changes and four cherry picks associated with 2 overall changes...
Electrion beam animation
Option to adjust navbar glow animation duration
Here are links to the picks in gerrit. Take a look.
http://review.cyanogenmod.com/#/c/12959/
http://review.cyanogenmod.com/#/c/15578/
http://review.cyanogenmod.com/#/c/16183/
http://review.cyanogenmod.com/#/c/16184/
Click to expand...
Click to collapse
I don't see cm7
Sent from my SPH-D700 using Tapatalk 2
lownox said:
[...]I really wasn't expecting the bit of harshness I got here. I guess I took for granted that everyone knew about Kangs (or Unofficial) builds and what they were.
Click to expand...
Click to collapse
Each device forum on XDA operates as it's own community. We have regulars. We have standards. We have issues we've ironed out throughout the device's lifetime.
"Kang" has generally been used to refer to stolen or leaked coding. Up until recently, it had been more of an insult to call someones rom a "kang." Terms like "unofficial" or "variant" likely would have been greeted with less suspicion. But, more specifically, you should always have a well stated OP with a clear purpose. Starting a thread by saying something like "here I will be posting official cm9 roms with no changes and any one can feel free to post theirs" is never a good idea. Especially since things can become gray-area when talking about CyanogenMod source.
Basically, you need a well-stated and well formatted OP defining what it is you're sharing and how it differs from the CM9 and CM7 threads we already have here.
The only thing I noticed is the phantom vm notification
Sent from my SPH-D700
I would like to add my 2 cents, or five, or ten, on this subject, and this being a public forum, there's nothing stopping me.
I don't really see how this thread is any different than a thread in the theme forum that has links to various theme's threads.
When I saw this thread it had been up for a while, so I didn't see how the OP was initially laid out, therefore I cannot speak on that matter, but I can say this: I feel that in its current state, the OP perfectly states the intent and design of this thread. Also, on a personal note, I'm very glad its here.
I won't say that interest in epic development is waning, but there's really no arguement that compared to a few months ago, there isn't near as much going on.
I also hope that this will encourage more devs to try their hand at ICS and CM based ROMs. I would love to see some slim ics or codename android jumpin off in this forum.
I really enjoy the epic forum and community, especially now, our forumm is well monitored and tight knit. But I also enjoy seeing new developers and new dev teams adding to the variety in our forum. This will never happen if we keep jumping on newcomers with a hostile attitude. I'm not saying anyone means to do so, but it does come off that way from time to time. This is my perspective, a member of this community for over a year, so imagine how someone new would take it.
I would like to personally extend my grattitude and a warm welcome to the epic community to the OP.
I'm sure most of us, if not all appreciate your presence.
Sent from my SPH-D700 using xda premium
Welcome to the Epic community OP:thumbup:
Sent from my SPH-D700 using xda premium
For those who followed the CM9 beta3 development cycle, we posted many test builds and received much helpful feedback toward improving beta3. We will soon post beta4-pre builds in the same fashion. Additionally, Team Epic is working on fixing some poor code quality issues in preparation for enabling official CM9 nightly builds in order to make this a more automatic process.
It seems many of the posters here are missing the latest Epic development news. If you follow +Epic CM and +CyanogenMod on Google+ you will know stuff often before it hits XDA.
Anyone wonder why there are devs on this device who are running their own custom roms, yet no one is PUBLICLY developing for it? They all have personal roms, and are unwilling to post them for us to use? Anyone know why?
Well there are no roms and development because we can't. Samsung didn't release the source code for the wifi chip so we can't mess around with stuff as much.
I don't know of anyone having personal roms or anything similar of the sort so where did you hear that? (As rude as that sounds I am genuinely curious)
Zadeis said:
Well there are no roms and development because we can't. Samsung didn't release the source code for the wifi chip so we can't mess around with stuff as much.
I don't know of anyone having personal roms or anything similar of the sort so where did you hear that? (As rude as that sounds I am genuinely curious)
Click to expand...
Click to collapse
That explains some of it... But I have seen some members sig lines say things like:
DEVICES I own:
Galaxy Tab +, rom= personal rom
or
my own rom that Im not sharing due to xda community on that forum
I'm not trying to start a flame against any specific member (which is why Im not naming names), Im just curious as to why they dont actually share their work...
Well my take on that is since we can't mess with it they most likely made small changes and there is no point in releasing it or they made a rom and it is there own rom and it has been released thus the 'personal' title.
In terms of the no sharing I think I know who you are talking about and he/she has recently released a rom in the development section if you look.
Zadeis said:
Well my take on that is since we can't mess with it they most likely made small changes and there is no point in releasing it or they made a rom and it is there own rom and it has been released thus the 'personal' title.
In terms of the no sharing I think I know who you are talking about and he/she has recently released a rom in the development section if you look.
Click to expand...
Click to collapse
Lol I DO know and I saw their Rom.... Actually tried flashing it.... I'm glad that they finally released.... I love seeing development explode..? maybe that's just what I'm waiting for??
Sent from my LG-P999 using XDA
I am running my own personal created ROM, but as suggested above, the changes are minimal and so releasing the ROM would really be pointless. I am testing tweaks and mods here and there, but I really haven't found something super beneficial worthy of being released to the community.
Once Samsung releases some wifi driver source (or ICS source), then development *should* pick up.
Sent from my SPH-D700 using xda premium
I heard over on Android Authority that Samsung has release its JellyBean source code for the i1900. I know our phones have a different processor, so it's not going to work on our phones, but given that they share at least a name, should I be hopeful that there could be some goodness in there to help move our Skyrocket's along with JellyBean (e.g. CyanogenMod 10.1), or even hopes of an official JellyBean release from Samsung?
http://www.androidauthority.com/samsung-releases-android-jelly-bean-source-code-galaxy-s2-137715/
There is already a Samsung JB leak in Development forum, you should have taken a look there.
Trinition said:
I heard over on Android Authority that Samsung has release its JellyBean source code for the i1900. I know our phones have a different processor, so it's not going to work on our phones, but given that they share at least a name, should I be hopeful that there could be some goodness in there to help move our Skyrocket's along with JellyBean (e.g. CyanogenMod 10.1), or even hopes of an official JellyBean release from Samsung?
http://www.androidauthority.com/samsung-releases-android-jelly-bean-source-code-galaxy-s2-137715/
Click to expand...
Click to collapse
Do you read any of our threads before posting useless new threads?
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
Should have done a search? I did, thanks. Searched for "jelly bean source". No hits. So I posted.
And a leaked *compiled* ROM does not equal source. Now it does answer my question about the Skyrocket getting Jelly Bean, and further implies there will eventually be a source delivery. That does not mean that the regular S2 Jelly Bean source available now can't offer a more immediate impact.
Also note that the UCLK4 thread in the development forum is slightly over one day old as of now. At the time I posted this thread, it was about 12 hours old. And the one in the General section was started after.
In fact, I saw the S2 news at AA much earlier yesterday but decided to wait to ask so others with more knowledge and experience could preemptively answer my question. But, via my search, I didn't find my answer.
So, yes, I agree my thread is now irrelevant. But at the time, it was hardly as clear as the smug replies in this thread suggest.
Sorry for my rudeness in response to yours. I know you guys have to put up with a lot of newbs. But the robotic and condescending dismissals are just as annoying to see over and over again, especially after I *did* do my due diligence.
Sent from my SAMSUNG-SGH-I727 using xda app-developers app
I didn't mean anything harsh in my reply, but answered half of your question, a half that seemed to me the most important one (our phone having official Samsung JB).
To answer one more thing: the sources are good for some things, namely if your goal is to patch the new kernel to the old driver binaries (the kind of work that's necessary for old and non-supported phones to run the latest OS found on their latest siblings with the same chipset) - but if your goal is to run the full OS with official latest drivers that it's built to run with, without precompiled binaries the source is good for nothing. And the patching work is futile if the official release is a month-two away.