Related
I hate to do this but did you guys see this. I really wish we were so close on the Epic. Is our phone really so different(I admit I don't know much about the differences)?
I have been following a Twitter that I think should be showing the commits but haven't seen any changes in a while. Has anyone heard anything recently? Are people still working on it? Ready but wait for the source to GB? Or has it been given up on?
Waiting on source from GB
Sent from my SPH-D700 using XDA Premium App
I almost posted this the other day, but I figured i'd get flamed cause it probably affects us 0% that they have it
Posted by Mr. Z's Epic 4G.
No dude? When did the Fascinate get source?
EDIT: *Chanting* MAKE A PORT! MAKE A PORT! MAKE A PORT! MAKE A PORT!
We'd have a better change getting official gingerbread tonight than getting a port of thay imo
Posted by Mr. Z's Epic 4G.
I agree with Zanderman. Although ports seem to "sound easier" to accomplish, that isn't always the case. I've heard lots of talk about it being easier and a lot more productive if we got Devs to build it once source is released opposed to porting it. patience is key here, which a lot of us don't seem to have anymore -__- I'm confident our Devs will get it working soon tho, we just need good ol' Samsung to release code, which they like taking their sweet time with -__-
Sent from my SPH-D700 using XDA App
But isn't the only difference that affects the Rom, the different bands that Sprint and Verizon use? They're both CDMA, so if we built a AOSP GB Kernel, we could probably use their ROM, but if not, it'd be easier to port than the GSM Galaxy S and variants. Keyboard shouldn't affect the ROM much.
But they don't have Source either! How did they get it is my question.
Bump and a thanks if you answer my question
Because their developers decided they needed to build their own, and got it right. We have to wait becase we know we're getting future updates.
Posted by Mr. Z's Epic 4G.
Samsung has given us a kernel source. However, from all the devs, I have heard that this is not the source code for the kernel that is on our phones, and the resulting compiled kernel is not exactly the same as the stock flashed kernel.
The GPL doesn't obligate Samsung to release a source for a kernel, it obligates Samsung to release the source for our kernel.
Maybe if enough of us contact Samsung on this issue, they will release the correct source. I found a way to contact their open-source department about this.
Go to:
https://opensource.samsung.com/
Select Mobile => Mobile phone from the dropdown
Search on the page for SPH-D710 (that's our phones' model number)
On the far-right there is an envelope you can use to contact them.
Use it and ask that they release the actual source code for the shipped kernel version.
I think this came up on a few phones before, maybe it was my OG Epic. I think I remember they have 90 days or "in a timely manner" to release the source. When it all comes down to it, there really isn't much we, or anyone can do, to force it. It's almost an honor system.
Some of the devs around here will have better specifics though.
jirafabo said:
I think this came up on a few phones before, maybe it was my OG Epic. I think I remember they have 90 days or "in a timely manner" to release the source. When it all comes down to it, there really isn't much we, or anyone can do, to force it. It's almost an honor system.
Some of the devs around here will have better specifics though.
Click to expand...
Click to collapse
Did the OG Epic fellows ever manage to get Samsung to release the real source?
jirafabo said:
I think this came up on a few phones before, maybe it was my OG Epic. I think I remember they have 90 days or "in a timely manner" to release the source. When it all comes down to it, there really isn't much we, or anyone can do, to force it. It's almost an honor system.
Some of the devs around here will have better specifics though.
Click to expand...
Click to collapse
There is no 90 day grace period. The kernel source code must be made available when the compiled kernel is made available.
Really, the only recourse is to sue. And since Google owns the copyright, my guess is that they would have to be the ones to sue (not a lawyer, so not 100% sure).
The odds of Google suing Samsung are about as good as the odds of OJ finding the real killer, so we are basically screwed.
Situations like this seriously undermine the open source nature of Android. If it happens enough to where Android loses market share because people doubt Google's commitment to open source, then they might do something about it. Since this issue probably only matters to a few percent of Android users, that's not very likely.
Don't get me wrong - I'm still a big fan of Google, but their philosophy of "do no evil" cannot be maintained forever as a publicly traded corporation. In the long run, "shareholder value" and the bottom line will win. Even more the reason to do what we can to keep Android as open as possible.
Sent from my SPH-D710 using xda premium
Maybe if enough of us contact Samsung on this issue, they will release the correct source. I found a way to contact their open-source department about this.
Go to:
https://opensource.samsung.com/
Select Mobile => Mobile phone from the dropdown
Search on the page for SPH-D710 (that's our phones' model number)
On the far-right there is an envelope you can use to contact them.
Use it and ask that they release the actual source code for the shipped kernel version.
Some one with some pull around here needs to contact Cyanogen... He does work for Samsung after all.
Samsung Galaxy S II
I don't think it is clear whether
1) source is the wrong source
2) source is incomplete but builds ok
3) source is broken/buggy
4) source is correct, but build parameters are slightly off
Okay, so I just received a response from Samsung actually.
♦ classification : Mobile Phone ♦
♦ model name : SPH-D710 ♦
Dear Customer,
Thank you for your continuous interest in our product.
Supported kernel version(EG30) is correct.
Where did you check the version?
Sincerely yours,
You may find the source code
Click to expand...
Click to collapse
Could a dev chime in on how we know the source version provided is incorrect? I have seen this referenced numerous times, with it cited as a possible reason LOS seems exacerbated on custom ROMs. If no dev sees this, can anyone point to one of the threads where a dev said this so that we can ask them for more information?
manekineko said:
Okay, so I just received a response from Samsung actually.
Could a dev chime in on how we know the source version provided is incorrect? I have seen this referenced numerous times, with it cited as a possible reason LOS seems exacerbated on custom ROMs. If no dev sees this, can anyone point to one of the threads where a dev said this so that we can ask them for more information?
Click to expand...
Click to collapse
+1
I was surprised to get a response from them so quickly.
If we don't get a response from a dev it wouldn't be to hard to investigate ourselves.
-Compile kernel from source (they give instructions)
-Flash to phone
-show different version # compared to stock
I just got the same reply. We need some info on what to say back. Developers please chime in. Thanks
Sent From My Evo Killer!!!
Okay, so I tracked down one of the places where I've seen reference to the fact that the source Samsung released isn't right.
The ACS Stock Kernel thread says:
Well as everyone knows, the source released from samsung was some bull****... LoStKernel, makes the best use of that source and adds lots of tweaks, and in my opinion is the best compiled custom kernel available...
But, some people stand by the point that only the stock pulled kernel is free from LoS, or is the LoS is least Rampant for them in that kernel.. But they want CWM too!
Click to expand...
Click to collapse
I private messaged the dev of that kernel, chris41g.
I also contacted zedomax, since he's also a kernel dev and I figure as such he might know something about this.
If anyone can think of anyone else that can shed more light on this, feel free to chime in.
manekineko said:
Okay, so I tracked down one of the places where I've seen reference to the fact that the source Samsung released isn't right.
The ACS Stock Kernel thread says:
I private messaged the dev of that kernel, chris41g.
I also contacted zedomax, since he's also a kernel dev and I figure as such he might know something about this.
If anyone can think of anyone else that can shed more light on this, feel free to chime in.
Click to expand...
Click to collapse
Good. Please post when you get some info as I would love to email Samsung back about this.
Sent From My Evo Killer!!!
Evo3d people have some individuals who would request a kernel source whenever a new kernel was released. I forget specific names, but these people would get in touch with the legal department of HTC, and the source would usually be out within a month...
I've heard back from Zedomax and chris41g.
Zedo didn't know anything about this kernel source differing issue.
chris41g says that it is obvious the source and the stock kernel differ. According to him they have different version numbers and different configs, which should show up in dmesg and kmsgs. Unfortunately, he doesn't actually have an Epic 4G Touch, so he's not able to explain in more detail.
Can any who is on a compiled from source (not stock) kernel take a look at this and provide any more information on this?
If you talk.to Chris, tell him we can hook up my phone and he can access anything needed with TeamViewer like he did when he made one of his kernels
Sent from my Nexus S 4G using xda premium
JohnCorleone said:
If you talk.to Chris, tell him we can hook up my phone and he can access anything needed with TeamViewer like he did when he made one of his kernels
Sent from my Nexus S 4G using xda premium
Click to expand...
Click to collapse
Thanks, I messaged back Chris and let him know.
Keep up the work on this cause musclehead
Sent from my Nexus S 4G using xda premium
They will likely not release it in any other form. Chances are, they stripped proprietary bits from it before release, and didn't adjust the source to make usable after doing so. Its basically up to developers to fix it in this case.
If this is case, which I'm sure it likely is, as I've had conversations with Samsung about these types of things before, there really is no recourse other than someone stepping up and fixing the source. Samsung isn't required to release proprietary bits, and they're also not obligated to release source code that builds and boots the device right out of the box.
Good luck.
Sent from my SCH-I500 using XDA App
jt1134 said:
They will likely not release it in any other form. Chances are, they stripped proprietary bits from it before release, and didn't adjust the source to make usable after doing so. Its basically up to developers to fix it in this case.
If this is case, which I'm sure it likely is, as I've had conversations with Samsung about these types of things before, there really is no recourse other than someone stepping up and fixing the source. Samsung isn't required to release proprietary bits, and they're also not obligated to release source code that builds and boots the device right out of the box.
Good luck.
Sent from my SCH-I500 using XDA App
Click to expand...
Click to collapse
This makes no sense, as the "proprietary bits" are the changes that are made to the kernel that fall outside of the vanilla kernel that google releases. You're saying those changes dont have to be released makes no sense. Otherwise everyone would just be re-releasing the same stock kernel that google puts out. All changes to the kernel made outside of whatever comes stock MUST be released according the to the GPL. So it doesnt matter what conversations you may or may not have had with whatever Samsung personnel. All that needs to be provided in this case is the differences in what we have and what they released. If a non-disputable change is found and easily comparable, then they have no legal choice.
Sorry if this has been asked before but I haven't found a thread about it in the Epic forums. Is there a dev that is working on porting ICS to the Epic? I know the source is out there now and the Epic can be a bit of a pain to port to, but there seems to be no info on ICS on this phone. Thanks for any information anyone can provide.
Hexidecimal said:
Sorry if this has been asked before but I haven't found a thread about it in the Epic forums. Is there a dev that is working on porting ICS to the Epic? I know the source is out there now and the Epic can be a bit of a pain to port to, but there seems to be no info on ICS on this phone. Thanks for any information anyone can provide.
Click to expand...
Click to collapse
This will most likely be in the form of CM9, still a little bit away...We haven't even gotten full official CM7 yet. From my understanding the system partition needs to be made bigger (which is being worked on right now in CM7) in order for CIS to be able to sit on our phones. I am not a dev at all, but this sounds like it will be a pretty daunting task
Plus there is a lot of driver information they don't have that they need. WiMax (4G) will likely never be on there and you may have upgraded to a phone with ICS by the time there is a reasonable working model.
Sent from my SPH-D700 using XDA App
It is being worked on, but kind of at a standstill until stable MTD recovery is released.
I thought I'd clear some things up.
If I'm wrong please don't flame me, I'm only doing my best to subdue the general discontent in [sgh-t989]/[android development]...
Steve Kondik, also known as the creator of the godfather of all ROMS (cyanogenmod) personally owns one of our t989s (source:twitter). That, combined with the fact that this is a FLAGSHIP t-mo device probably means that our phone will be supported from the day that 9.0.0 drops.
Now, let me tell you what this means.
As you all know, for a device get non-kang CM9 our hardware must be fully supported. Camera, GPS, bluetooth, egl drivers all must work.
When a huge scale ROM like CM9 is cooked for so many devices I understand it goes something like this
[AOSP modified by Cyanogenmod(teamdouce)] +
[Android Kernel, also modified by Cyanogenmod]+
[Device tree]+
[A virgin sacrifice]=
CYANOGENMOD
Now the interesting bit, is that as soon as the device tree (Eg. Specific driver modifications for GPS, Camera, GPU) includes our device the device tree can be used to power OTHER AOSP ROMS like Miui
I know that gingerbread MIUI already makes use of the CM7 device tree, so in all likelihood they will use the CM9 device tree as well!!!
So in conclusion.
-Because CM9 has a high likelihood of dropping on our devices as soon as it comes out (most likely within the next 30 days)
-Because other AOSP-Based roms depend on the cyanogenmod device tree
-WE WILL HAVE A LOT OF FLASHING OPTIONS SOON
-Probably including CM9 AND MIUI v4 <<<<--------THAT **** CRAY
Thanks for your time, hope it helped
Don't forget the thanks button feels good when you push it.
there are a lot of other devices with cm9 alpha and we are still not an officially supported device. Still unofficially being worked on
I for one is not counting on it, frankly...
No matter how beautifully you phrase things, WE GOT NOTHING YET.
Sent from my SGH-T989 using XDA App
[A virgin sacrifice] =
SO FREK'IN EXCITED!!!!!
thanks for the info bro looking forward to it
jessejames111981 said:
there are a lot of other devices with cm9 alpha and we are still not an officially supported device. Still unofficially being worked on
Click to expand...
Click to collapse
the thing is, many of those are KANGed as in not officially supported by CM team
of the few that officially are supported is Nexus S i9020 and SGS i9000
even the "classic" SGS2 i9100 is not fully supported by CM yet, there's more bugs than... well it's not usable as a daily driver
that was just before the end of last year
they might have improved it a bit by now
even the Nexus S version of CM9 is still very buggy, that's why i have the stock official ICS4 instead on my Nexus S
Please please use words like
"death of an era." Instead of virgin sacrifice. I don't believe in that
Sent from my SGH-T989 using xda premium
iwasblown said:
Please please use words like
"death of an era." Instead of virgin sacrifice. I don't believe in that
Sent from my SGH-T989 using xda premium
Click to expand...
Click to collapse
I don't believe in idiots, can you make them all go away?
It takes time for this stuff guys. Anyone remember how long it took to jump from donut to eclair to get a stable rom? And look how few devices there were that actually ran android. This whole "if its not done in 2 weeks then its never happening" thing is a bit unfair. Let the devs dev and those who do not can wait for them quietly.
Why this statement?
From a glaxay better than yours.
tl;dr
I am basing my entire post on the fact that Steve Kondik has our device and should theoretically be working on it.
Click to expand...
Click to collapse
Steve Kondik aka Mr. Cyanogen also works for Samsung. I am sure he gets ALL Samsung devices...
corwest said:
It takes time for this stuff guys. Anyone remember how long it took to jump from donut to eclair to get a stable rom? And look how few devices there were that actually ran android. This whole "if its not done in 2 weeks then its never happening" thing is a bit unfair. Let the devs dev and those who do not can wait for them quietly.
Click to expand...
Click to collapse
It only takes 2 weeks to modify the stock rom or cm7/9.
Its the expectation that is built when people act like quantity is all that matters. There are basically only 2 people making roms; Samsung and CM team, everyone else just waits on these 2 so that they could tweak and modify one of those 2. The funniest part is that the use of the word "kanging" is thrown around among these other people.
housecat93 said:
I thought I'd clear some things up.
If I'm wrong please don't flame me, I'm only doing my best to subdue the general discontent in [sgh-t989]/[android development]...
Steve Kondik, also known as the creator of the godfather of all ROMS (cyanogenmod) personally owns one of our t989s (source:twitter). That, combined with the fact that this is a FLAGSHIP t-mo device probably means that our phone will be supported from the day that 9.0.0 drops.
Now, let me tell you what this means.
As you all know, for a device get non-kang CM9 our hardware must be fully supported. Camera, GPS, bluetooth, egl drivers all must work.
When a huge scale ROM like CM9 is cooked for so many devices I understand it goes something like this
[AOSP modified by Cyanogenmod(teamdouce)] +
[Android Kernel, also modified by Cyanogenmod]+
[Device tree]+
[A virgin sacrifice]=
CYANOGENMOD
Now the interesting bit, is that as soon as the device tree (Eg. Specific driver modifications for GPS, Camera, GPU) includes our device the device tree can be used to power OTHER AOSP ROMS like Miui
I know that gingerbread MIUI already makes use of the CM7 device tree, so in all likelihood they will use the CM9 device tree as well!!!
So in conclusion.
-Because CM9 has a high likelihood of dropping on our devices as soon as it comes out (most likely within the next 30 days)
-Because other AOSP-Based roms depend on the cyanogenmod device tree
-WE WILL HAVE A LOT OF FLASHING OPTIONS SOON
-Probably including CM9 AND MIUI v4 <<<<--------THAT **** CRAY
Thanks for your time, hope it helped
Don't forget the thanks button feels good when you push it.
Click to expand...
Click to collapse
I'd like to believe, I really would. And I hope this does come to fruition. However, even if it doesn't, the few ROMS we do have are pretty good, and our phone still outperforms almost anything else available right now, so I'll still be happy.
I do have one request, though. Can we figure out a way to make CM based ROMS happen without a virgin sacrifice? There are so many other things in life that require those, that they are starting to become scarce
The fact that lots of other phones have alphas and repositories available to even make kangs does not fare well for our device.
Sent from my HTC_Amaze_4G using xda premium
guys chillax..slayher already has it booting..and that's news from december
good to know, thanks
Great phone, needs more dev time and hopefully that comes along with it when ics hits.
We got shafted early with the nexus release so close to the T989 and a dev that promised things but ran away.
New year brings new hope. Great respect for the devs that care about our phone.
Sent from my SGH-T989 using XDA App
Let's hope the mods don't ban what little devs we have left...
Sent from my HTC_Amaze_4G using xda premium
AznDud333 said:
guys chillax..slayher already has it booting..and that's news from december
Click to expand...
Click to collapse
I don't follow, what do you mean by booting?
synergeticink said:
I don't follow, what do you mean by booting?
Click to expand...
Click to collapse
http://en.wikipedia.org/wiki/Booting
If you haven't visited RC's page on google+, he just posted another tease on CM9 for us and said "just a couple more buglets to solve." Cross your fingers that we're getting close.
Edit: you can append anything to the url. No placeholder.
super cool considering cm9 is not available for very many devices right now.
Currently, you can compile CM9 for a small number of devices- notably the Samsung Galaxy Nexus and Nexus S, the Samsung Galaxy Tab 10.1 (Wi-Fi and T-Mobile versions), the HP Touchpad and Motorola Xoom. The next devices to show up will likely be a whole array of Samsung phones (Exynos chipset), with devices based on the Qualcomm MSM8660 and 7×30 chipsets to follow.
Click to expand...
Click to collapse
Too bad I'm selling the LG. Oh well, I'd like to see some vids once it's all said and done.
@scott, I don't look at CM as my saving grace for supplying an ICS ROM. There are countless others out there that have supplied an ICS ROM for various devices, some of them are actually more stable than the ICS Kang builds.
the man is evil giving us the teases....I want to be testing that rom.
a user asked him where he would be releasing the CM9 for our phone once it's ready, and he gave this:
http://get.cm/
So I say let's keep an eye on it
He was replying to the guy who asked where to find the CM9 public repo for the p990.
Yeah the P990 (G2X/O2X) has had Nightly CM9 builds for some time now.
aquariuz23 said:
a user asked him where he would be releasing the CM9 for our phone once it's ready, and he gave this:
http://get.cm/
So I say let's keep an eye on it
Click to expand...
Click to collapse
A user.... ouch that I get denigrated to just A user...
That was me asking as I could never find any of his commits to the git repository. Still not sure if he has submitted anything yet, but I will get checking that link on a regular basis. I think I may also send a message to koush to see if he has what is needed to create CWM for our phones...
And he was replying to me - and I asked specifically about the 930. He +'d my name on the reply which is the only way I know he was talking with me...
even if cm9 for 930 publish,camera work fluently is or not is a big probrem
Man I can't wait for that to come out. I would figure our nitro would be a worthy candidate as its been pretty much made with ice in mind. Knowing att those jerks.....we wont get an official one till like the summer....if even then
Sent from my LG-P930 using XDA
According to the guys at the att store...that there is supposed to be a ics push sometime within the next 30 days....at least that is what they said when I bricked my phone and replaced it...they thought that maybe I got a push already...I kind of looked at them like they were crazy...then one said to the other that he read it in their "kms" system. When I worked for sprint KMS stood for Knowledge management system...it was essentially the end all be all of all possible knowledge about a phone or company policy.
I still think this is speculation and I won't say with 100 percent confidence that either of them were telling the truth.
If At&t does push ICS out, would that make it easier to compile CM9 for the VS920 (LG Spectrum)?
Amazing question I don't have a spectrum so I don't know
Sent from my LG-P930 using XDA
Epyoch said:
Amazing question I don't have a spectrum so I don't know
Sent from my LG-P930 using XDA
Click to expand...
Click to collapse
Spectrum is very similar (same SOC), but it uses a different radio (to account for CDMA). So unless the AT&T version of CM9 is specifically modded, it won't work for Spectrum.
There is now a placeholder on the CM mirror network. When available, downloads should show here.
http://download.cyanogenmod.com/?type=nightly&device=p930
Great news....so looking forward to ics
Sent from my LG-P930 using xda premium
dnorthington said:
There is now a placeholder on the CM mirror network. When available, downloads should show here.
http://download.cyanogenmod.com/?type=nightly&device=p930
Click to expand...
Click to collapse
That will probably be official...but in reality it's easy to trick...I mean put in the (device=) instead of p930 put fakephone and see what happens
Looks like the iPhone is next:
http://download.cyanogenmod.com/?type=nightly&device=iphone4s
Hey, they're also working on a port for the TI80 Calculator: http://download.cyanogenmod.com/?type=nightly&device=TI80
Turns out that they are deving for Your Mom too.
http://download.cyanogenmod.com/?type=nightly&device=YourMom