Related
Wrong: CYANOGENMOD 7 RELEASED, HARMONY SUPPORT, DIDN'T NOTICE ANY POSTS REFERING TO IT
Right: CM7 was released, with Harmony support.
Wrong: SHAME THAT NVIDIA ARE NOT SUPPORTING DEVELOPMENT FOR HARMONY CHIP FROM 2.2 ONWARDS IF REPORTS ARE TRUE
Right: It's a shame that nVidia isn't supporting Harmony developers from 2.2 onwards, if reports are true.
Mod Edit: All caps is annoying. Please don't use it. Thanks.
Yes if you actually look at the other CM7 threads you will see that the Vega changes have been added to the official tree now.....
and how can you go and say that we have cm7 (2.3) and then complain about the lack of nvidia support beyond 2.2 in the same post, completely contradicts itself....
but doesnt the tegra 2 already power a bunch of honeycomb tablets already?
mintvilla said:
but doesnt the tegra 2 already power a bunch of honeycomb tablets already?
Click to expand...
Click to collapse
there are two types of tegra 2 boards, Harmony which the vega has supported to android 2.2 and Ventana which the xoom has, supported beyond 2.2
Useless posts removed, OP reformatted. All caps is just annoying.
Also, thank you Lennyuk for your expertise. I actually wasn't aware of the two Tegra 2 revisions. What are the differences between Harmony and Ventana?
willverduzco said:
Useless posts removed, OP reformatted. All caps is just annoying.
Also, thank you Lennyuk for your expertise. I actually wasn't aware of the two Tegra 2 revisions. What are the differences between Harmony and Ventana?
Click to expand...
Click to collapse
as far as I know there is not actually a great deal of differences between the two, I think the ventana board has an extra GPU slot, that might be it.
Lennyuk said:
as far as I know there is not actually a great deal of differences between the two, I think the ventana board has an extra GPU slot, that might be it.
Click to expand...
Click to collapse
Interesting. I wonder why that would be since these SOCs don't have modular components, with the GPU being directly integrated into the SOC itself... Weird.
UPDATE 12 APRIL 2011:
Sorry folks looks like I caused a bit of confusion. Since this is a developer forum my comments
were targeted at Tegra Honeycomb developers and for this we’d like to focus on Ventana. For shipping or production products, customers should contact the device makers directly for OS support plans. They are responsible for the OS shipping on their device.
In relation to our linux kernel git repository, NVIDIA will continue to provide full open-source support for all of our kernel components and will push more of that upstream over time.
Andrew Edelsten
Tegra Developer Relations
NVIDIA CorporationTop
Sent from my HTC Desire using XDA App
Interesting update something for developers to get teeth into sometime
Sent from my HTC Desire using XDA App
Mod Edit: All caps is annoying. Please don't use it. Thanks.[/QUOTE]
haha to right
UPDATE 13 APRIL 2011
A lot has been read into a very short post about a Tegra development kit. I'd like to clear up a few points.
First, nothing changes in what we’re delivering to the open source community or customers. NVIDIA will continue to post the Tegra kernel to kernel.org and publish our Android code to our public git servers. Additionally, we will continue to make our BSP (codecs, GPU driver etc) available to all our hardware partners. We will continue to do this and nothing about these processes has changed.
For our partners' Android devices, NVIDIA provides support until the hardware partner chooses to no longer support the device. So, for instance, NVIDIA will support the Xoom on all versions of Android Motorola requests until Motorola ceases to support the Xoom. The same goes for ViewSonic with the G-Tablet, Notion Ink with the Adam, Acer with the Iconia, LG with the Optimus 2X and so on.
In relation to my original reply, that was a response to a specific question about a Tegra 250 Development Kit. Given the confusion, we will work with owners of Tegra 250 Development Kits individually to determine their needs. The term "Harmony" is an internal codename for the Tegra 250 Development Kit. It is not a tablet reference design. Each shipping tablet is a custom design with varying hardware components and requires a custom OS image from the OEM who made the tablet.
Finally, while we cannot support or give out third party peripheral drivers or provide the Android 3.0 source before Google does, we do want to explore whether we can assist the open source ROM makers. We will be reaching out to them today.
*
Sent from my HTC Desire using XDA App
Caps from original nvidia forum post.
Stop being so anal anyway
Sent from my HTC Desire using XDA App
Can anyone translate this for me? Are we (Advent Vega users) getting the Tegra 2 update? And is this the one for Honeycomb?
From what I can tell, Yes. Or am I reading this wrong?
GaiusSensei said:
Can anyone translate this for me? Are we (Advent Vega users) getting the Tegra 2 update? And is this the one for Honeycomb?
From what I can tell, Yes. Or am I reading this wrong?
Click to expand...
Click to collapse
There is no "Tegra 2" Update
You are getting confused.
Basically when the Tegra2 boards were given to manufacturers they had one of two designs
Harmony which the vega has
or Ventana which newer tablets have
These are not set in stone, they were just designs that then get built to specific needs by each manufacturer.
Nvidia are not releasing their own stock images beyond android 2.2 for Harmony however they have made it very clear that it is down to each manufacturer to do this, Nvidia will support the manufacturers for as long as they want to continue service on each device.
Advent do not yet know if the manufacturer (Shuttle) will give us a HC rom, however at least 2 other clones of the Vega have confirmed it, so it looks promising.
Point of View is supposed to deliver us a fresh HC ROM, I would be really thankful!
All I need is a rom w/o cellphone stuff, just tablet things to work always with optimizations and no slow downs.. That's why I bought a tablet with tegra... but after news like this, customers like me get pretty sad and will regret buying another device from them. Gz;
Hi! We just released a bit of code we thought this group might be interested in.
Over at our Android Open-Source Project git servers, the source code
for Android version 4.0 (Ice Cream Sandwich) is now available.
Here's how to get it:Follow the instructions at
http://source.android.com/source/downloading.htmlCheck out the
'ics-release' branch:repo init -u
https://android.googlesource.com/platform/manifest -b android-4.0.1_r1
That's it! However since this is a large push, please be aware that it
will take some time to complete. If you sync before it's done, you'll
get an incomplete copy that you won't be able to use, so please wait
for us to give the all-clear before you sync.
This is actually the source code for version 4.0.1 of Android, which
is the specific version that will ship on the Galaxy Nexus, the first
Android 4.0 device. In the source tree, you will find a device build
target named "full_maguro" that you can use to build a system image
for Galaxy Nexus. Build configurations for other devices will come
later.
Unfortunately we still don't have our Gerrit code review servers back
online. That remains our top priority though, and we hope to have them
back soon.
This release includes the full history of the Android source code
tree, which naturally includes all the source code for the Honeycomb
releases. However, since Honeycomb was a little incomplete, we want
everyone to focus on Ice Cream Sandwich. So, we haven't created any
tags that correspond to the Honeycomb releases (even though the
changes are present in the history.)
JBQ, on behalf of the AOSP team.
--
Jean-Baptiste M. "JBQ" Queru
Software Engineer, Android Open-Source Project, Google.
Questions sent directly to me that have no reason for being private
will likely get ignored or forwarded to a public forum with no further
warning.
Click to expand...
Click to collapse
http://groups.google.com/group/android-building/browse_thread/thread/4f85d9242667a85f
Just read this on AndroidPolice. Very excited!!!
Game.....on!
Sent from my PG86100 using XDA App
Developers make some rom's!!!!!! (Please)
this thread should make its way over to the development section. Thanks for the find op
Update: Already there
I'm actually curious about how long it will take for someone to make an A500 ICS ROM based on this. There is bound to be someone to do it, but who gets the #1 spot?
Whoever does it, it won't be soon. Build requirements are kinda steep...
https://groups.google.com/group/and...355d4256bdf4906?hl=en_US&lnk=gst&q=16gb&pli=1
They're not necessarily requirements, but more or less just recommendations. A more average computer could still compile ICS, but it will just take a lot longer. And I'm betting Thor will be the first to cook us a ROM. Hopefully soon
Sent from my HTC Glacier using xda premium
FloatingFatMan said:
Whoever does it, it won't be soon. Build requirements are kinda steep...
https://groups.google.com/group/and...355d4256bdf4906?hl=en_US&lnk=gst&q=16gb&pli=1
Click to expand...
Click to collapse
Those are only recommendations for developer workstations. It is certainly possible to compile it even on a low-grade office PC if you give it a week.
Hence my saying it won't be soon...
FloatingFatMan said:
Hence my saying it won't be soon...
Click to expand...
Click to collapse
Your still not understanding my friend. Unless your definition of soon is in 30 minutes. Peter Alfonso that develops for the OG Droid and a few other devices compiled his in about 1 hour and 45 minutes. That was a laptop core i7 and 8gb of ram.
Thats not whats going to be time consuming. The hard part will be finding/getting the hardware inside our devices to work. I asked THOR on his forum about ICS on the iconia, his response:
done know for now... depends how many proprietary stuff the a500 uses....
I'm worried the camera, sensors and battery as these seam to be tampered with...
for the moment I'm busy with other stuff will see when I get some time to sneak a peak at the code...
Click to expand...
Click to collapse
Time will tell.
I'm sure FFM understands that. As you say, the hard part is getting the hardware to work, but with a slower machine, how many test builds can you do in a day? With a big fast machine that can build in a few hours vs a laptop that might take a few days can make a huge difference of when you get to your final release.
But hey.. i don't know anything, so why don't I just shut up...
It takes about 3.5 hours for me to build a new version of ICS. I'm on a 3 year old laptop which is why it takes so long. It would be great to have a much newer machine to build with as it would help to make things go faster.
So I guess that Google engineer was taling out of his butt then.
We all know the sources for the HDMI are not relesed by Sony which makes it difficult for the developers to incorporate HDMI in their ROMs.. So this is a petition for Sony to release the sources for HDMI..
PLease Sign it.. And Hope for the best..
http://www.change.org/petitions/sony-release-the-sources-for-hdmi-for-xperia-2011-family
Edit: please respond here once you sign..
I signed it but we need a ton of signings to get them to give use what we need so plz people sign in and don't let Sony do what thay did with the x8 and put us in the corner. As well.
we could even help you Sony to make you line of phones rule over the like of HTC/sg3 so plz help us
Sent from my LT18i with sence3.5 using xda premium
big jd said:
i signed it but we need a ton of signings to get them to give use what we need so plz people sign in and don't let sony do what thay did with the x8 and put us in the corner. As well.
We could even help you sony to make you line of phones rule over the like of htc/sg3 so plz help us
sent from my lt18i with sence3.5 using xda premium
Click to expand...
Click to collapse
1+
Signed
Sent from my LT15i using xda premium
I really doubt that they would release hdmi source as this Proprietary source is not only used within their mobile devices but also in their other products like TV, walkman etc. But ok worth a shot lol! ;o
Signed!!!
+1
Signed
Seems like my phone useless without it when using custom room.
Signed
Signed.
signed
signed
signed
Signed, I think it's hard for Sony to do it, it's all about proprietary thingies in the HDMI/DRM/CEC that make it takes time for Sony to do it, and for them, the 2011 line are done and doesn't worth spending time and resources on them and they're trying to focus on 2012 and 2013 lines...
Signed
Via Xperia Active
Done Signing!
Signed.
Sent from my Xperia Pro via XDA
Xajel said:
Signed, I think it's hard for Sony to do it, it's all about proprietary thingies in the HDMI/DRM/CEC that make it takes time for Sony to do it, and for them, the 2011 line are done and doesn't worth spending time and resources on them and they're trying to focus on 2012 and 2013 lines...
Click to expand...
Click to collapse
Stop giving them bloody excuses!
Release the HDMI driver NOW Sony.
PS: signed.
signed too... but how many we did need?
paul5425 said:
Stop giving them bloody excuses!
Release the HDMI driver NOW Sony.
PS: signed.
Click to expand...
Click to collapse
It's not an excuse it's the truth. It's just like asking Microsoft to release windows 7 source code. Meh!
Sony's HDMI has sources which communicates with it's propriety softwares named "xloud" & "Bravia". Releasing HDMI source would just make their inventions open to any developers. So it would just let for example samsung, sharp, LG use bravia & xloud on their devices/appliances. Which would have a very3x bad impact on sony as a company since it's their flagship softwares we're talking about.
In non technical explanation... It's just like giving your neighbors your WIFI's passphrase and letting them use it.
Riyal said:
It's not an excuse it's the truth. It's just like asking Microsoft to release windows 7 source code. Meh!
Sony's HDMI has sources which communicates with it's propriety softwares named "xloud" & "Bravia". Releasing HDMI source would just make their inventions open to any developers. So it would just let for example samsung, sharp, LG use bravia & xloud on their devices/appliances. Which would have a very3x bad impact on sony as a company since it's their flagship softwares we're talking about.
In non technical explanation... It's just like giving your neighbors your WIFI's passphrase and letting them use it.
Click to expand...
Click to collapse
I think this needs some more in-depth technical clarification as to what is being asked here (this after all is meant to be a TECHNICAL site, so people here should be able to cope.
Now, perhaps I am getting confused here and talking about another issue entirely but, on the Pro at least, from what I can understand ROMs like Cyanogenmod do not support HDMI. Why does Cyanogenmod not support HDMI? Is it because Cynaogenmod have just been slow to make HDMI work, or is it that Sony do not provide the drivers, or is it because the Cynaogenmod team have some odd ideological stance concerning open-source software?
What I'm getting at here is surely Sony is providing some sort of pre-compiled binary driver to make the HDMI work? Surely we shouldn't actually need the source itself?
In summary, what I am trying to ask is what is the current status regarding general HDMI support available, and what advantages will having the source bring?
Hi guys!
First it's many months i don't come here on xda.
Second i haven't this device
...but i playing with this SoC from 2 months in a developers board (Odroid-XU-E).As you,i can go at 1.8 Ghz with A15 and 640 Mhz max with gpu when i build kernels for it..No luck until now in enabling 8 cores...also if for you is a bit useless,being the SoC in a phone on battery(where my board instead is AC powered!)but i know there were a lot of drama about it months ago about the CCI-400 bug
...and something is moving.look here those diff\patches
https://lkml.org/lkml/2013/10/1/264
https://lkml.org/lkml/2013/10/1/259
Thanks buddy. but i think samsung unofficially announced about not to support all 8 cores functional At one time.
Also what abiut heating and Boooom problem? I means, It may blast our mobile if not supported fully?
Edit: Seen that samsung official working on it.
A Suggestion: Change the thread name to True octa core.
Sent from my GT-I9500 using XDA Premium 4 mobile app
Any pros to enlighten me what this actually means? Will this patch actually work?
Does it utilize the CCI400(which was believed to be broken) or other approach?
Sent from my GT-I9500 using xda app-developers app
sert00 said:
Hi guys!
First it's many months i don't come here on xda.
Second i haven't this device
...but i playing with this SoC from 2 months in a developers board (Odroid-XU-E).As you,i can go at 1.8 Ghz with A15 and 640 Mhz max with gpu when i build kernels for it..No luck until now in enabling 8 cores...also if for you is a bit useless,being the SoC in a phone on battery(where my board instead is AC powered!)but i know there were a lot of drama about it months ago about the CCI-400 bug
...and something is moving.look here those diff\patches
https://lkml.org/lkml/2013/10/1/264
https://lkml.org/lkml/2013/10/1/259
Click to expand...
Click to collapse
a word from @AndreiLux to make things clear..
thanks !
Will this patch actually work?
Click to expand...
Click to collapse
For us, basically no. These patches are for device-tree based kernels which our platform specific one isn't.
For the ODROID-XU / eventual theoretical DT based i9500 kernel it might be a possibility.
I see there's some non-standard alterations to the CCI driver related to the coherency ports, but they didn't even answer in the mailing list as to why they are there.
gdonanthony said:
a word from @AndreiLux to make things clear..
thanks !
Click to expand...
Click to collapse
i m also waiting for him. Posted the link in Previous thread of @AndreiLux buddy.
Sent from my GT-I9500 using XDA Premium 4 mobile app
AndreiLux said:
For us, basically no. These patches are for device-tree based kernels which is not part of ours.
For the ODROID-XU / eventual theoretical DT based i9500 kernel it might be a possibility.
I see there's some non-standard alterations to the CCI driver related to the coherency ports, but they didn't even answer in the mailing list as to why they are there.
Click to expand...
Click to collapse
@sert00 so here is the answer ... damn so sad about this things going on... and im hoping somethings will get better soon
thanks AndreiLux
AndreiLux said:
For us, basically no. These patches are for device-tree based kernels which our platform specific one isn't.
For the ODROID-XU / eventual theoretical DT based i9500 kernel it might be a possibility.
I see there's some non-standard alterations to the CCI driver related to the coherency ports, but they didn't even answer in the mailing list as to why they are there.
Click to expand...
Click to collapse
Does that mean it's a hardware level possibility, and just need to be implemented by clever brains?
They mentioned it was tested on 5410 dev board, dunno what that actually means..
Also regarding DT kernel, if I'm not wrong Linux is now forcing devs to switch to DT? So do you foresee any future for i9500 to actually have a DT kernel?
Forgive me if I was talking nonsense, I'm quite noob.
Sent from my GT-I9500 using xda app-developers app
lch920619x said:
Does that mean it's a hardware level possibility, and just need to be implemented by clever brains?
They mentioned it was tested on 5410 dev board, dunno what that actually means..
Also regarding DT kernel, if I'm not wrong Linux is now forcing devs to switch to DT? So do you foresee any future for i9500 to actually have a DT kernel?
Forgive me if I was talking nonsense, I'm quite noob.
Sent from my GT-I9500 using xda app-developers app
Click to expand...
Click to collapse
I doubt Samsung will ever switch the current generation to a DT model much like they never update older phone's kernels, but backport the needed bits. They're talking about the SMDK board which are LSI internal development boards. It is a STUPID amount of effort to switch over to a DT kernel, any hope is that some third-party gets some kind of update on the matter and be able to pull from that. Even the XU has only some half-hearted DT support and they work mostly on the platform kernel which is similar to ours.
Alternatively I could just pull the relevant MCPM backend and that new EDCS from the patch and try to get hack something together. But I would want to at least those patches to be actually accepted into mainline and have the 5410 supported there before one begins on an adventure into unknown territory.
AndreiLux said:
I doubt Samsung will ever switch the current generation to a DT model much like they never update older phone's kernels, but backport the needed bits. They're talking about the SMDK board which are LSI internal development boards. It is a STUPID amount of effort to switch over to a DT kernel, any hope is that some third-party gets some kind of update on the matter and be able to pull from that. Even the XU has only some half-hearted DT support and they work mostly on the platform kernel which is similar to ours.
Alternatively I could just pull the relevant MCPM backend and that new EDCS from the patch and try to get hack something together. But I would want to at least those patches to be actually accepted into mainline and have the 5410 supported there before one begins on an adventure into unknown territory.
Click to expand...
Click to collapse
I have to admit i got some difficulties understanding part of your post.
However I think I grasp the main idea and I'm looking forward to seeing how things will work once you try to implement the patch. Thanks for your effort.
BTW I'm using Chinese C version ROM(ZCUCMH1 to be specific), if I flash perseus ontop of my ROM, camera will refuse to open and report camera failure.
Not asking you to solve it but just curious if you can tell me what will possibily cause this?
Also if you have time can you point out what exactly is stopping us from having a fully functional AOSP build?
We got full kernel source code due to GPL, don't we?
And in another post you said it's nothing to do with documentation.
So what is it?
Sent from my GT-I9500 using xda app-developers app
thanks for the answer andreilux!i posted it only as a info.also on odroid board will be ready only when mainlined on 3.13 kernel,as sad by a linux developer,and there's tons of works to do to others stuffs to works!
Many rom projects like Cyanogen mod, Paranoid droid rom and many others were released only for renowned company phones like Galaxy Series, Nexus series etc etc, where as millions & billions of MTK soc phones that contribute alot to the daily millions of Android activations are left out. Many MTK phones developers started request threads for cyanogen mod and other rom communities to build/release a rom for MTK phones but those request were neglected till date.
Now with the start of new rom project "Omni", MTK phone devs are hoping that this rom will also be compiled & released for MTK phones. We want Omni pioneers to release this rom for millions & billions of MTK phones.
We are willing to help you guys making Omni rom project better & grow.
Regards
Wouldn't have it been easier to read some posts in the forum?
This will happen. When you're able to watch the presentation video (which will be up in the next few days) you'll notice that @XpLoDWilD shows Omni running on the Oppo R819, a quad-core MTK device.
jerdog said:
This will happen. When you're able to watch the presentation video (which will be up in the next few days) you'll notice that @XpLoDWilD shows Omni running on the Oppo R819, a quad-core MTK device.
Click to expand...
Click to collapse
There are a lot of things in the way. Also, any MTK devices that ship without kernel sources (there are a lot of them) are still out of luck.
The R819 is a game changer here - Oppo really wants it to receive community firmware support and has been EXTREMELY cooperative with us in terms of getting us documentation.
Entropy512 said:
The R819 is a game changer here - Oppo really wants it to receive community firmware support and has been EXTREMELY cooperative with us in terms of getting us documentation.
Click to expand...
Click to collapse
So they are giving you access to the MTK framework sources? Or do you have to reimplement the dual sim support (I have never seen any open source ROM with dual sim support)? I'd really love to help a bit, having some MTK6577 phones lying around here.
I too have two MTK phones .....they are a powerful if it got development projects like this ...it will be the no.1 vendor in chip set marketing and ...I support for OMNI PROJECT
Sent from my Fly IQ451 using XDA Premium 4 mobile app
C-o-M said:
So they are giving you access to the MTK framework sources? Or do you have to reimplement the dual sim support (I have never seen any open source ROM with dual sim support)? I'd really love to help a bit, having some MTK6577 phones lying around here.
Click to expand...
Click to collapse
I'm not sure about the state of dsim support. We do have access to quite a bit, however some items even the OEM we're working with doesn't have access to source for, and it's also a nasty licensing minefield.
There's much better potential than there has been previously, however there are still some nasty technical and legal challenges. For example, MTK's 4.2 firmware appears to be using all sorts of hwcomposer backcompat hacks to use what is effectively a 4.0 (ICS) HWC.
Entropy512 said:
I'm not sure about the state of dsim support. We do have access to quite a bit, however some items even the OEM we're working with doesn't have access to source for, and it's also a nasty licensing minefield.
There's much better potential than there has been previously, however there are still some nasty technical and legal challenges. For example, MTK's 4.2 firmware appears to be using all sorts of hwcomposer backcompat hacks to use what is effectively a 4.0 (ICS) HWC.
Click to expand...
Click to collapse
With this I assume device will not receive 4.4 barely 4.3 but can I ask how is to work with OEM?
Sent from my Xperia U using xda app-developers app
XperianPro said:
With this I assume device will not receive 4.4 barely 4.3 but can I ask how is to work with OEM?
Sent from my Xperia U using xda app-developers app
Click to expand...
Click to collapse
Nobody can predict what happens in the future.
In terms of working with OEMs, not sure what your question is, but one thing we do bring to the table with Omni is considerable experience in working with OEMs. And that should be rather beneficial for everyone
Will you be allowed to release all sources needed to build the ROM?
There are sources for various MTK devices (MT6577/MT6575) that can be used already. I assume it would be no problem for the omni team to integrate them into their builds.
darkguy2008 said:
There are sources for various MTK devices (MT6577/MT6575) that can be used already. I assume it would be no problem for the omni team to integrate them into their builds.
Click to expand...
Click to collapse
We have more recent ones that are being used to bring up MTK devices.
At the BBQ, Xplod demonstrated an Oppo r819 running Omni, which is an MT6589
pulser_g2 said:
We have more recent ones that are being used to bring up MTK devices.
At the BBQ, Xplod demonstrated an Oppo r819 running Omni, which is an MT6589
Click to expand...
Click to collapse
So with this you mean that those sources work for MT6577 devices?
I wish you guys the best of luck, but conserning MTK and their closed sources policy, i really don't believe those sources (and im talking about the framework /RIL) will be Open Source.
If we are lucky enought we may get some working builds for some of the phones (if an brand gives you support), but concerning the MTK licenses, well its an MINE FIELD.
An good example is the on-going Cyanogen project by FAEA for the F2S (MT6589), they got the green light from MTK, BUT the project will remain Closed Source, so no one will get those sources...
B.Regards
superdragonpt said:
An good example is the on-going Cyanogen project by FAEA for the F2S (MT6589), they got the green light from MTK, BUT the project will remain Closed Source, so no one will get those sources...
Click to expand...
Click to collapse
AFAIK, you are wrong:
chasepoes said:
Well I know of one dev. who is develloping CM port voor MTK658x devices (usinf Faea mobile). For now he has to operate under a NDA agreement, but once finished his source will be come available.
Click to expand...
Click to collapse
darkguy2008 said:
So with this you mean that those sources work for MT6577 devices?
Click to expand...
Click to collapse
Unknown. And as I've said, it's a licensing nightmare.
It may be that certain components will have to be developed in a "some people have the source but can only release blobs" - I would prefer to avoid this if at all possible. The issue is if any of those "files with nasty license" are in things that can't be cleanly separated, it will present a MAJOR issue.
Entropy512 said:
Unknown. And as I've said, it's a licensing nightmare.
It may be that certain components will have to be developed in a "some people have the source but can only release blobs" - I would prefer to avoid this if at all possible. The issue is if any of those "files with nasty license" are in things that can't be cleanly separated, it will present a MAJOR issue.
Click to expand...
Click to collapse
Well I assume something like the HTC Magic or the Defy can be done. They don't have the sources for the hardware GPU but they managed to enable hardware compositing after some work somehow. I don't think that MTK will oppose to the project using the libs and such instead of having full access to the code, usually that feels less restrictive for both the company and the devs, imho.
I may be talking rubbish though, I'd just like the MT6577 devices to get some lovin', because we've been fighting for quite some time against ZTE for them to release the kernel sources so we can develop ROMs for the V970M and more =/
darkguy2008 said:
Well I assume something like the HTC Magic or the Defy can be done. They don't have the sources for the hardware GPU but they managed to enable hardware compositing after some work somehow. I don't think that MTK will oppose to the project using the libs and such instead of having full access to the code, usually that feels less restrictive for both the company and the devs, imho.
I may be talking rubbish though, I'd just like the MT6577 devices to get some lovin', because we've been fighting for quite some time against ZTE for them to release the kernel sources so we can develop ROMs for the V970M and more =/
Click to expand...
Click to collapse
ZTE,I dont know much about this company but its worse than Sony I think...
Why not release kernel sources,what are developers doing at their company...
XperianPro said:
ZTE,I dont know much about this company but its worse than Sony I think...
Why not release kernel sources,what are developers doing at their company...
Click to expand...
Click to collapse
Pretty much most Chinese companies are like this. Oppo is VERY non-typical of a Chinese company, which is why they have a FAR better chance of global success than any other Chinese mobile OEM right now.
Entropy512 said:
Pretty much most Chinese companies are like this. Oppo is VERY non-typical of a Chinese company, which is why they have a FAR better chance of global success than any other Chinese mobile OEM right now.
Click to expand...
Click to collapse
How very true. I have high hopes for this project as my current device is an OPPO R819. I chose OPPO because exactly they try to be open with the developers, having the experience of Motorola and their locked bootloaders the past years while the Motorola DEFY was my main device. It took a long time for the DEFY to get its first custom kernel and it only happened thanks to some very persistent people. It shouldn't be like this, so as long I have a choice I'll opt for unlocked (and cheap...) devices.
Sent from my Nexus 7 using xda app-developers app