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!
Related
It looks like there are a variety of other devices that have the same chipset - I've perused around other threads where some people had some success doing it (samsung vibrant has the same wifi chipset). I was curious if this was on any of the devs radars at all - theres an entire community of pentesters and infosec folks twitching and biting their nails over the idea that one can run standard industry tools (like the aircrack suite) on this platform.
I've been able to install ubuntu on my xoom, however the kernel module for the chipset (bcm4329) doesn't currently support monitor mode.
Thoughts / ideas / advice?
I think this would be fun to have....
Sent from my Xoom using XDA Premium App
I started a thread a couple of days ago wondering the same thing...
http://forum.xda-developers.com/showthread.php?t=983646
am interested as well!!
I work for the android development team at Broadcom and I didn't even know that the xoom used the bcm4329. That's interesting. Unfortunately, I can't really give you any information on your problem.
smaskell said:
I work for the android development team at Broadcom and I didn't even know that the xoom used the bcm4329. That's interesting. Unfortunately, I can't really give you any information on your problem.
Click to expand...
Click to collapse
Think theres a chance it can be tweaked at the android level?
Moved. Please post in the correct section. Thank you.
If other phones that have the same chipset work in monitor mode, it should be possible to port the code over to the existing wireless module we have now.
That said, it will probably be a bit of work porting from the version of Android on the Captivate (2.1, 2.2?) to 3.0.
news
http://forum.xda-developers.com/showthread.php?t=1892535
xoom have bcm4329, maybe it work.
who test ?
android omap kernel (3.0.1) :
https://android.googlesource.com/kernel/omap
git clone https://android.googlesource.com/kernel/omap.git
git checkout android-omap-panda-3.0
linaro kernel from ti (3.1.0) :
http://git.linaro.org/gitweb?p=landing-teams/leb/ti/kernel.git;a=summary
git clone git://git.linaro.org/landing-teams/leb/ti/kernel.git
git checkout android-release-2011-11-3
They all have SGX 540 driver.
I think port one of them to kindle fire is possible.
Anyone has interest in it?
It would probably be best that you didn't label posts such as this [Kernel][Port]. This thread is labeled as if you ported a kernel and are releasing it. It just comes off a little misleading. I would suggest labeling it [Suggestion] or [Request].
Would that give a smoother experience? The OMAP 4 chip is of the fastest in the market right now yet Fire is a bit sluggish despite the immense power it "hides" underneath its lid.
The Galaxy Nexus seems to be one generation faster yet their hardware is almost identical, whould this (Google's) kernel give the Speed (that Amazon "stole" from us) back?
Downloaded, works great!
Oh wait, this isn't actually a kernel thread and there isn't any development information here.
Please change the title and move to general. Major WASTE of time!
Sent from my ADR6400L using Tapatalk
It's interesting as soon as it boots.
Hopefully the Amazon kernel isn't very different to any of the SDP-supporting kernels. I guess there's one way to find out... (as well as other, less interesting and safer, ways...)
randallu said:
It's interesting as soon as it boots.
Hopefully the Amazon kernel isn't very different to any of the SDP-supporting kernels. I guess there's one way to find out... (as well as other, less interesting and safer, ways...)
Click to expand...
Click to collapse
http://moooom.dyndns.info/?p=107
Somebody got a bootable kernel and started ICS with it.
We can get source later.
Hi, a developer called pulser_g2 made this petition for Samsung to be more open and be a lot more developer friendly, this petition is for all Samsung android devices. So I thought I would post it here in the hope a few of you may consider singing it please
http://www.change.org/petitions/sam...t-achieve-full-potential-of-purchased-devices
Thank you
I don't see the point in signing this as SAMFIRMWARE already releases a bunch of firmwares for Samsung.
Sent from my GT-i9220 using Tapatalk
kotaro_14 said:
I don't see the point in signing this as SAMFIRMWARE already releases a bunch of firmwares for Samsung.
Sent from my GT-i9220 using Tapatalk
Click to expand...
Click to collapse
that's not what they're requesting
Samsung releases kernel sources but rest are not. This is the precise reason why CM crew is having trouble getting things like hardware codec support working like the stock rom
I think it's ok to demand full source to be released but i'm not sure if they can release the full source for things that they didn't produce (ie yamaha dac)
ph00ny said:
that's not what they're requesting
Samsung releases kernel sources but rest are not. This is the precise reason why CM crew is having trouble getting things like hardware codec support working like the stock rom
I think it's ok to demand full source to be released but i'm not sure if they can release the full source for things that they didn't produce (ie yamaha dac)
Click to expand...
Click to collapse
I agree - according to wikipedia the Android system is open source, so by definition all code should be available to all developers. I'm a bit of a noob to this, but my understanding is that as long as code is properly referenced, it can be re-used/improved etc.
Even something like sound and video drivers should be available to be used enhanced - it would make the system so much better. Voodoo Sound is a classic example of someone have to spend a heck of a lot of time tweaking and playing with a system until they find the right combination. How much better would our wonderful Note be if drivers, codecs and other fundamental kernel-related items were truly available to all?
Signed it
Sent from my GT-N7000 using xda premium
As far as I know, Broadcom promised to get android on our small little computer Raspberry Pi but their is no news of it till now
So I started this thread to discuss all the possible ways to Port Android to RasPi
Project Name: IncrediPi
This thread on MADTeam Forums: http://madteam.co/forum/development-106/(discussion)-incredipi-porting-android-for-raspberry-pi/
This thread here on XDA: http://forum.xda-developers.com/showthread.php?t=2321557
Rules of this thread:
No spamming and No Flaming
No Fights to be continued here
Abuse/Disrespect towards newbies or any member!
Use only english
Help each other with problems
One of my uncles also has RasPi and he knows hell lot of knowledge in Programming!
Biggest problem we will see in this project is hardware drivers... Broadcom is kinda closed source I remember how my devices Galaxy Y got a semi-stable CM... Galaxy Y uses Broacom so I know the pain when we started developing xD
I hope we can see Android Running on Pi Someday :fingers-crossed:
Similar articles:
http://www.raspberrypi.org/archives/tag/android
http://androidpi.wikia.com/wiki/Android_Pi_Wiki
http://www.linuxtoday.com/upload/bu...-based-raspberry-pi-station-130528005512.html
Will update this thread with more such links everyday
ALSO SEE: I am not a developer, Just trying to gather information from people
Similar Threads to this on XDA:
http://forum.xda-developers.com/showthread.php?t=2046717
http://forum.xda-developers.com/showthread.php?t=1667072
http://forum.xda-developers.com/showthread.php?t=1811089
http://forum.xda-developers.com/showthread.php?t=1808965
http://forum.xda-developers.com/showthread.php?t=1808965
I just saw this: https://github.com/raspberrypi/firmware/issues/70
He says he got the system booting fine but due to the lack of egl drivers the h/w isn't accelerating... I'll catch hold of that guy! I hope we are able to make it work
I was after this also, in what i can help let me know.
Also, at this moment the main issue is the broadcom driver,!!
Br
M3mn0t
m3mn0t said:
I was after this also, in what i can help let me know.
Also, at this moment the main issue is the broadcom driver,!!
Br
M3mn0t
Click to expand...
Click to collapse
Yes, I also own a Galaxy Y which uses similar GPU and CPU! It took 2000+ Signs in a petition for them to provide us test egl binaries! I hope with the same method broadcom will release drivers for Pi
I will never loose hope
Sent from my GT-S5360 using Tapatalk 2
Last update from raspberry pi was at july 2012....almost a year ago.I think its time to broadcom provide that drivers. I will get more inside this subject, broadcom drivers, them i will try something, also it would be perfect that some developers get into this thread.
Br
Arnav.G said:
Yes, I also own a Galaxy Y which uses similar GPU and CPU! It took 2000+ Signs in a petition for them to provide us test egl binaries! I hope with the same method broadcom will release drivers for Pi
I will never loose hope
Sent from my GT-S5360 using Tapatalk 2
Click to expand...
Click to collapse
m3mn0t said:
Last update from raspberry pi was at july 2012....almost a year ago.I think its time to broadcom provide that drivers. I will get more inside this subject, broadcom drivers, them i will try something, also it would be perfect that some developers get into this thread.
Br
Click to expand...
Click to collapse
Yeah....
I am studying C right now...
Also, Please some developers needed here
Ok!
I was working on a Website for this project and its nearly complete....
I will share it here!
Also, I have started looking into other porting processes! Just like HTC HD2 has so many OS's RasPi will also have
What version of android does your Uncle have running?
There have been cyanogenmod 7 running on the Raspberry Pi for a while without any hardware acceleration, the main problem developers are having are getting anything above android 4.0 running without hardware acceleration.
dombeef said:
What version of android does your Uncle have running?
There have been cyanogenmod 7 running on the Raspberry Pi for a while without any hardware acceleration, the main problem developers are having are getting anything above android 4.0 running without hardware acceleration.
Click to expand...
Click to collapse
Can you link me to CynogenMod 7 for Pi?
For EGL Libs we have to start a petition against broadcom asking for the drivers But unfortunately we have to!
This is something that i have to dig deep before start anything, because i want to understand very well every aspect of this project.
What confuses me is, if there is already an arm 6 cellphone android with the same broadcom chip for graphics, why we cannot start from there?!! keep in mind the raspberry pi uses the same arm 6 cpu \ broadcom gpu
Br
Arnav.G said:
Can you link me to CynogenMod 7 for Pi?
For EGL Libs we have to start a petition against broadcom asking for the drivers But unfortunately we have to!
Click to expand...
Click to collapse
m3mn0t said:
This is something that i have to dig deep before start anything, because i want to understand very well every aspect of this project.
What confuses me is, if there is already an arm 6 cellphone android with the same broadcom chip for graphics, why we cannot start from there?!!
Br
Click to expand...
Click to collapse
Main problem is that no manufacturer except samsung provides Broacom chip on their phones!
also, In my country Pi is out of stock :/
The closest Armv6 Phone which uses Broadcom chip is Galaxy Y and it has a quite similar GPU and CPU as compared to that of in Pi! *I HAVE THIS DEVICE*
But I am not sure if we can engineer its drivers to make it work with Pi!
Also we struggled alot to get a semi stable CyanogenMod 7!
UPDATE :victory:
I was going through MADTeam Forums and then saw a post on Raspberry Pi Opensource GPU Drivers!
http://www.raspberrypi.org/archives/2221
That means we still have hopes on getting it Stable!
Before we start we need to make a proper device tree! I'll be sending PM's to some BCM Devs
Arnav.G said:
Main problem is that no manufacturer except samsung provides Broacom chip on their phones!
also, In my country Pi is out of stock :/
The closest Armv6 Phone which uses Broadcom chip is Galaxy Y and it has a quite similar GPU and CPU as compared to that of in Pi! *I HAVE THIS DEVICE*
But I am not sure if we can engineer its drivers to make it work with Pi!
Also we struggled alot to get a semi stable CyanogenMod 7!
Click to expand...
Click to collapse
Here in portugal, You can find it anywhere eheheh, the 512 mb ram version. Now what i will search and understand is, if we have a gingerbread version already working in a raspberry pi, but without any hw accelaration, maybe with the original firmware from galaxy Y we can start work with the broadcom driver, do you see the light at the end of the tunel?!
Br
m3mn0t said:
Here in portugal, You can find it anywhere eheheh, the 512 mb ram version. Now what i will search and understand is, if we have a gingerbread version already working in a raspberry pi, but without any hw accelaration, maybe with the original firmware from galaxy Y we can start work with the broadcom driver, do you see the light at the end of the tunel?!
Br
Click to expand...
Click to collapse
I didn't get you :/
Anyways I shared the Opensource GPU Drivers! I still have hope that we can get HW Acceleration done in Gingerbread but I don't know about ICS or JB4.1/4.2
Arnav.G said:
Can you link me to CynogenMod 7 for Pi?
For EGL Libs we have to start a petition against broadcom asking for the drivers But unfortunately we have to!
Click to expand...
Click to collapse
Just a little googling will get you them: Android on the Raspberry Pi.
But you still didnt answer my question of what your uncle's Pi was running. He might just be running android 2.3 which has been released by developers for a while now.
dombeef said:
Just a little googling will get you them: Android on the Raspberry Pi.
But you still didnt answer my question of what your uncle's Pi was running. He might just be running android 2.3 which has been released by developers for a while now.
Click to expand...
Click to collapse
Nopes....
My Uncle bought a RasPi for Google Lunar XPrize! If you don't know what is that then: "Its a mission for teams all over the world to send a robot to the moon and make it run for 500 meters on the surface of the moon! They are making parts of the sensors of the robot with RasPi I am a small part of it "
Arnav.G said:
I am studying C right now...
Click to expand...
Click to collapse
I'm sure you will be able to provide us nice stuff then!
galaxyfreak said:
I'm sure you will be able to provide us nice stuff then!
Click to expand...
Click to collapse
I'll give my best
Any progress with the build and anywhere to snatch a copy?
Im building my own set of smart glasses and was hoping to run the UI on my Raspberry Pi. If I cant I will have to just run it over a series of adaptors from my S3 to the glasses.
I need Android running well enough to voice search, Bluetooth to a Mini Rii and receive messages via ZipWhip.
Am I too early to this party?
Are there any dates for the first stable release that we can test it ?
Anything new?
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