Database Users

Camera libraries available for Sony Ericsson phones

sosad dat it only includes 2011 lineup
http://developer.sonyericsson.com/wp/2011/11/17/camera-libraries-available-for-sony-ericsson-phones/
Camera libraries available for Sony Ericsson phones
As promised when we announced our support of independent developers, we have now made the camera library binaries for a number of Sony Ericsson phones available under a special end user license agreement (EULA). You can use these camera libraries to handle the camera hardware in our 2011 Xperia™ phones except Xperia™ PLAY, which has a different camera module.
Download and find out more after the jump.
As we stated a while back, we recognise custom ROMs as an important part of the Android™ ecosystem. When we decided to support the FreeXperia group working on the custom ROMs for Sony Ericsson phones, we quickly found out they had problems with our cameras. This is because the camera technology used by Sony Ericsson is a very advanced – we actually consider it to be the best in the market. However it is a closed implementation, so we can’t share the source code for it.
However, after some discussions with the FreeXperia team, we agreed to allow the FreeXperia team to use our libraries (which can be seen as drivers) for the cameras. But these libraries could not be used as they were, since they had dependencies to other modules in the phone that could not be included in the custom ROM project. To solve this, we rebuilt the libraries and provided them with a special EULA.
These newly rebuilt camera libraries are now modified with less dependencies to other libraries. We have recompiled the libraries without code changes but with different build flags. You can use these camera libraries under a special EULA-license. There are several important conditions you need to comply with, for example:
The Software can be copied and distributed under the condition that the original copyright notice and disclaimer of warranty will stay intact and the Licensee will not charge money or fees for the Software, whether as a stand-alone product, or as part of a compilation or anthology.
Several more conditions apply – please read the full EULA and make sure you are complying before using the camera libraries in any software. Download the camera libraries and find the full EULA text in the zip. Here you can also find a short instruction on how to start using these libraries. For more information on how use libraries like these, please see the FreeXperia project related thread on the XDA forum. We don’t have any possibilities in providing further support on this.
At last but not least, we want to say thanks to all of you in the community supporting this work, we really appreciate it. Even though we might not be able to support every single request we get, we are doing our best to support the community going forward.
Karl-Johan Dahlström
Head of Developer Relations
Sony Ericsson
More information
Download the camera libraries for the 2011 Xperia phones.
Find out how Sony Ericsson is supporting independent developers.
Learn how to build a Linux kernel.
Visit our unlock boot loader web service.

sounds good. anyone who understand this may improve the photo quality.
i can't wait to

anakinlam95 said:
sosad dat it only includes 2011 lineup
http://developer.sonyericsson.com/wp/2011/11/17/camera-libraries-available-for-sony-ericsson-phones/
Camera libraries available for Sony Ericsson phones
As promised when we announced our support of independent developers, we have now made the camera library binaries for a number of Sony Ericsson phones available under a special end user license agreement (EULA). You can use these camera libraries to handle the camera hardware in our 2011 Xperia™ phones except Xperia™ PLAY, which has a different camera module.
Download and find out more after the jump.
As we stated a while back, we recognise custom ROMs as an important part of the Android™ ecosystem. When we decided to support the FreeXperia group working on the custom ROMs for Sony Ericsson phones, we quickly found out they had problems with our cameras. This is because the camera technology used by Sony Ericsson is a very advanced – we actually consider it to be the best in the market. However it is a closed implementation, so we can’t share the source code for it.
However, after some discussions with the FreeXperia team, we agreed to allow the FreeXperia team to use our libraries (which can be seen as drivers) for the cameras. But these libraries could not be used as they were, since they had dependencies to other modules in the phone that could not be included in the custom ROM project. To solve this, we rebuilt the libraries and provided them with a special EULA.
These newly rebuilt camera libraries are now modified with less dependencies to other libraries. We have recompiled the libraries without code changes but with different build flags. You can use these camera libraries under a special EULA-license. There are several important conditions you need to comply with, for example:
The Software can be copied and distributed under the condition that the original copyright notice and disclaimer of warranty will stay intact and the Licensee will not charge money or fees for the Software, whether as a stand-alone product, or as part of a compilation or anthology.
Several more conditions apply – please read the full EULA and make sure you are complying before using the camera libraries in any software. Download the camera libraries and find the full EULA text in the zip. Here you can also find a short instruction on how to start using these libraries. For more information on how use libraries like these, please see the FreeXperia project related thread on the XDA forum. We don’t have any possibilities in providing further support on this.
At last but not least, we want to say thanks to all of you in the community supporting this work, we really appreciate it. Even though we might not be able to support every single request we get, we are doing our best to support the community going forward.
Karl-Johan Dahlström
Head of Developer Relations
Sony Ericsson
More information
Download the camera libraries for the 2011 Xperia phones.
Find out how Sony Ericsson is supporting independent developers.
Learn how to build a Linux kernel.
Visit our unlock boot loader web service.
Click to expand...
Click to collapse
2011 line of [email protected]#$% [email protected]#%$ phones...
MASSIVE FACE PALM.
What i find so funny.. is how the x10 gets nothing.
They must have buried the source code disks for the x10 in the SUN.
Because it's nearly impossible to find anything on any 2010 device.

x10 wont go anywhere....even x10 as old phone also they not share the drivers libraries. thats mean our development for x10 wont go so far. They just gave another reason why we should not buy x10 at these days and why we should start looking for new phone.

Problem....
Hi all..i copied the 3 files for my arc and into the correct folder as instructed..
then i rebooted..
now the phone is on 'sony ericsson' screen..reboot n rebooted..
erm..
anyway to remove the 3 files again?

hinata76 said:
Hi all..i copied the 3 files for my arc and into the correct folder as instructed..
then i rebooted..
now the phone is on 'sony ericsson' screen..reboot n rebooted..
erm..
anyway to remove the 3 files again?
Click to expand...
Click to collapse
Are you trying to use arc camera lib files on x10? Only way to repair is recovery restore if it is working or flashtool a ftf rom or seus...
Sent from my X10i using xda premium

hinata76 said:
Hi all..i copied the 3 files for my arc and into the correct folder as instructed..
then i rebooted..
now the phone is on 'sony ericsson' screen..reboot n rebooted..
erm..
anyway to remove the 3 files again?
Click to expand...
Click to collapse
If u copied the files given by SE in ur arc so u are doing it wrong
that files are for development purposes
Repair ur phone using pc companion

The Gingerbread Man said:
Are you trying to use arc camera lib files on x10? Only way to repair is recovery restore if it is working or flashtool a ftf rom or seus...
Sent from my X10i using xda premium
Click to expand...
Click to collapse
no im using on arc..then the whole phone just died..
just reflashed now okay!
almost got my fingers burnt..lol.

Don't know if anyone or the devs notice this:
Dec 8, 2011
Sony Ericsson Xperia™ X10 add-on for the Android SDK
The Sony Ericsson Xperia™ X10 add-on for the Android SDK includes the complete Android system with additions customizing it for the X10 : Sony Ericsson splash screen; X10 colour backgrounds; A "skin" of the X10 which is a simple graphic of the front of the phone; A hardware.ini file to set the operating parameters for screen, camera, audio and so on. Link:http://developer.sonyericsson.com/wportal/devworld/downloads/download/dw-102216-xperia-x10sdkadd-onr1?cc=gb&lc=en
Can this help with the camera development?

Can anyone make normal flash for x10?
Sent from my xperia "z10i"

Petition for Samsung to be more open

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

Porting S Voice to other device. Is this Illegal??

I have been a fan of XDA and appreciate the development and support the devs provide. But last few days a thought is bugging me continuously. We saw a lot of posts about S Voice and other apps being ported to other devices. Specially for S Voice, I believe that it's illegal as this could potentially cause Samsung to lose sales. My views:
1] We know that this is re-designed vlingo. vlingo is available in market, S Voice is NOT. Clear indication that they (as in Samsung) don't want the app to be used with other devices and they are not willing to sell it separately. Using vlingo from market is NOT same as using S Voice.
2] Did Samsung give us the permission to use/modify and distribute the app?
3] There is some infrastructure costs associated with running the services. It costs money to install and maintain servers and network. I work in enterprise storage management, so I am aware of costs associated with such massive infrastructure. Who pays for the non-SGS3 devices using the services?
4] Did Samsung every promise that SGS2/Nexus or other phones will get S Voice? So, why should we assume that other Samsung-device owners have the divine right to use a feature meant for SGS3?
5] It is one of the main USP for SGS3. Check here. This is listed as the top-most feature in the SGS3 product page. Hacking this app to be used with other phones is going to harm the phone sale. Is that not clear enough?
6] When Samsung started blocking connections from other devices - was that not an indication that they want the service exclusive for SGS3?
7] How is this different from movie piracy? The uploader never gains anything, but the studios/producers lose money.
8] What if Samsung starts locking their device in future with locked bootloaders/DRM/encryption because of such activities? Can we then blame Samsung for locking the devices?
9] Android is open source - but why assume that every feature in any Android is also open source? If someone can show me that S Voice is open source software, I will retract my statement.
It's sad that most people here equate freedom with piracy. Freedom and piracy are not same thing. Such act in the name of open source and community-feeling does not make it right. Maybe Samsung won't do anything about it -- but it does NOT make this act any better. It will just prove that Samsung considers this to be a petty nuisance (I am not using the word crime as I know nobody is doing this for any monetary gain).
Though I support open initiative with regards to Android, but I can't support such act.
Last check this statement from Samsung in VERGE
An initial test version of S Voice which was found online has been blocked as Samsung Electronics does not want consumers to judge the quality of the voice feature based on a test version. When the product is launched, users of GALAXY S III will be able to fully experience S Voice.

Exactly my thoughts. Though I am not sure what can be done to stop it.
Sent from my GT-I9100 using Tapatalk 2

rd_nest said:
I have been a fan of XDA and appreciate the development and support the devs provide. But last few days a thought is bugging me continuously. We saw a lot of posts about S Voice and other apps being ported to other devices. Specially for S Voice, I believe that it's illegal as this could potentially cause Samsung to lose sales. My views:
1] We know that this is re-designed vlingo. vlingo is available in market, S Voice is NOT. Clear indication that they (as in Samsung) don't want the app to be used with other devices and they are not willing to sell it separately. Using vlingo from market is NOT same as using S Voice.
2] Did Samsung give us the permission to use/modify and distribute the app?
3] There is some infrastructure costs associated with running the services. It costs money to install and maintain servers and network. I work in enterprise storage management, so I am aware of costs associated with such massive infrastructure. Who pays for the non-SGS3 devices using the services?
4] Did Samsung every promise that SGS2/Nexus or other phones will get S Voice? So, why should we assume that other Samsung-device owners have the divine right to use a feature meant for SGS3?
5] It is one of the main USP for SGS3. Check here. This is listed as the top-most feature in the SGS3 product page. Hacking this app to be used with other phones is going to harm the phone sale. Is that not clear enough?
6] When Samsung started blocking connections from other devices - was that not an indication that they want the service exclusive for SGS3?
7] How is this different from movie piracy? The uploader never gains anything, but the studios/producers lose money.
8] What if Samsung starts locking their device in future with locked bootloaders/DRM/encryption because of such activities? Can we then blame Samsung for locking the devices?
9] Android is open source - but why assume that every feature in any Android is also open source? If someone can show me that S Voice is open source software, I will retract my statement.
It's sad that most people here equate freedom with piracy. Freedom and piracy are not same thing. Such act in the name of open source and community-feeling does not make it right. Maybe Samsung won't do anything about it -- but it does NOT make this act any better. It will just prove that Samsung considers this to be a petty nuisance (I am not using the word crime as I know nobody is doing this for any monetary gain).
Though I support open initiative with regards to Android, but I can't support such act.
Last check this statement from Samsung in VERGE
An initial test version of S Voice which was found online has been blocked as Samsung Electronics does not want consumers to judge the quality of the voice feature based on a test version. When the product is launched, users of GALAXY S III will be able to fully experience S Voice.
Click to expand...
Click to collapse
Samsung will have known about this,
If they explicitly didnt want it to be shared with other android phones they could have prevented this easy in one of 2 ways,
1. integrate it into touchwiz framework
2. link the phones imei or unique identifier to the app and set up a database on the servers, similar to siri's protection.
Samsung wanted this app to be freely available as they have done nothing to protect its redistribution. I dont think they mind this because they have NO competitor in the Android market and are far superior to any other OEM that produces android phones.
PS. The Android OS is open source but there are many applications that have closed source to protect their business. Touchwiz source is never fully open sourced and neither is Sense.
I remember a year ago with the CM team asking for help from Samsung for little bits of protected code to get the camera fully functioning on the stock android rom (CM7 ROM).
JD

JupiterdroidXDA said:
Samsung will have known about this,
If they explicitly didnt want it to be shared with other android phones they could have prevented this easy in one of 2 ways,
1. integrate it into touchwiz framework
2. link the phones imei or unique identifier to the app and set up a database on the servers, similar to siri's protection.
Samsung wanted this app to be freely available as they have done nothing to protect its redistribution. I dont think they mind this because they have NO competitor in the Android market and are far superior to any other OEM that produces android phones.
PS. The Android OS is open source but there are many applications that have closed source to protect their business. Touchwiz source is never fully open sourced and neither is Sense.
I remember a year ago with the CM team asking for help from Samsung for little bits of protected code to get the camera fully functioning on the stock android rom (CM7 ROM).
JD
Click to expand...
Click to collapse
My view is that we took the application and made it compatible with other devices, Samsung never explicitly gave the permission.
Maybe they thought it would be easier to upgrade the app if it's not integrated into the TW. But I fear such activity may force them to become less dev-friendly in future.
It's a different story if in future they make the code available for CM9 or other projects separately. I just hope not, but the way it's being spread over the internet, I fear they will react in some way. Also throws a bad light over XDA.

JupiterdroidXDA said:
Samsung wanted this app to be freely available as they have done nothing to protect its redistribution.
Click to expand...
Click to collapse
They obviously didn't want it to be freely available because they have blocked it now.
Anyway, I don't get this mentality that if something is not impossible to take, it's ok to take it.

I will ask about the validity of ripping/porting the samsung apps and post back to this thread. If there is anything illegal about it (and im not sure there is unless the apps have been licensed specifically to the Galaxy S3) then any links on xda will be taken down.
I cant do anything about the rest of the internet though lol.
Mark.

mskip said:
I will ask about the validity of ripping/porting the samsung apps and post back to this thread. If there is anything illegal about it (and im not sure there is unless the apps have been licensed specifically to the Galaxy S3) then any links on xda will be taken down.
I cant do anything about the rest of the internet though lol.
Mark.
Click to expand...
Click to collapse
Much appreciated. I wanted this to be brought to the notice of MODs. Nobody wants XDA to be in bad light for such a petty affair.
As for the apps (specially S Voice) being exclusive to SGS3, I think so. That's what I infer from Samsung's statement in Verge:
http://www.theverge.com/2012/5/22/3037943/samsung-blocking-s-voice-app-leak
But please do verify with relevant authorities and take appropriate actions (if required).

Mac OS X doesn't require a product key, but that doesn't mean my friend can just use my installation DVD legally, it all depends on the T&C's
The fact Samsung have blocked it for other devices should give an indication of their decision towards people using this software on another device. They may not send the FBI to kick down your door and arrest you, but cracking it to spoof a SGSIII for example would probably get a DMCA take-down notice pretty quickly. They almost certainly won't want all and sundry freely enjoying one of the big features of their new flagship device.

I have e-mailed Samsung PR dept on their views about this issue. Not sure if they check their Inbox

Unless we hear otherwise from Samsung, we will follow the normal site policy. In this case (though it is an edge case) for the moment we're allowing it.

If this is the case, then all devs who port roms from other models are in breach also.
Is this thread trying to stop dev work, and has the OP loaded the program, if he has shame on him for going against his beliefs, now let us and the devs get on with it.:what:
Sent from my GT-I9300 using Tapatalk 2
Edit: phone model is Arc, now why did I change the prop build?

OP - Care to share how this is any different from all of the Sense ports to other devices? It's not.
I also like how you thanked Mark for checking into this - and that you were waiting to hear.... And then not even an hour later you go and contact Samsung PR? It sounds to me like you have an ax to grind.

I think everything that needs to be covered has been

Omni Rom For MTK Devices

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

A Petition for sony to add Camera2 API support

THey guys i just created this petition for sony to add Camera2 API , in a Sony forum , Sony Xperia Staff stated that they will add this feature if there is a huge demand on it .
" we will consider this for the future if there is a popular demand "
http://talk.sonymobile.com/t5/Software-Updates/Camera2-API/td-p/974742
So i just created this petition to show the great demand of users , please share it all over xda
https://www.change.org/p/sony-mobil...pport-to-xperia-smartphones?just_created=true
Thank you!

res.

I'm pretty sure a petition already exists

@muzab a
I looked everywhere i couldn't find one , now just share this one so we can reach thousands
Thank You

http://email.change.org/mpss/c/hQA/...YsbFj-2Fnr1tIwpy-2BPjoUzKExudIx-2BxnqUA-3D-3D
---------- Post added at 11:28 AM ---------- Previous post was at 11:28 AM ----------
Delete yr one and use this

This is something else , my petiotion is for Camera2 API , check the sony website they said they will support it if they find huge demand.
that petition has nothing to do with that

Guys please share it , just copy the link and post on other threads, we need to reach thousands so sony can see it and see the demand

Are you really that naive? Support for the device ended after ICS 4.0.4 and you really expect them to add support to Camera2 API (which by the way is an Lollipop feature)?

@RollingRoman uhh noobs again , this forum is for all sony devices and you can see it in any sony device forum , but for sure we only mean devices that are still in support

RollingRoman said:
Are you really that naive? Support for the device ended after ICS 4.0.4 and you really expect them to add support to Camera2 API (which by the way is an Lollipop feature)?
Click to expand...
Click to collapse
Man..please, forgot about ended support 4.0.4, it's xperia 2011 series..... For that, hope that CM12 would release lollipop update with Camera2 API..
Now we're talking about the Z series (maybe T2 Ultra and C3 too) which got official lollipop update and yes, Camera2 API is a part of lollipop feature. We're hoping sony to release an update featured with Camera2 API and this is cross-sony device section.. So it means all "SONY" related thing is here.. sorry, no hard feeling no harshing.. PEACE NO WAR brother..

@daniLaLaLaLaLa Thank you

Ref

M7ammad said:
Ref
Click to expand...
Click to collapse
Signed. I hope we succeed.I also wrote to Sony. Here is their answer:
Dear Mr. Tochev,
Thank you for contacting Sony Xperia Support.
With regards to your inquiry, we would like to inform you that Android™ 5.0 supports the new camera features via android.hardware.camera2, and Google™ defines three modes for the new camera features:
1.Legacy mode (no support RAW capture)
2.Limited mode (optional capability for RAW capture)
3.Full mode (optional capability for RAW capture)
Currently, Xperia™ supports Legacy mode in our Lollipop update which incorporate features and functionality in addition to our already renowned camera experience.
As always, we monitoring our customer expectations and regarding supporting taking pictures in RAW format, we will consider this for the future if there is a popular demand.
They write the exxact same thing everytime.We have to push them harder to succeed.

@BlAckXpeRia
Let's show them the demand

Actually i think its nothing more than scripted customer care reply...It will take a lot of work for them to incorporate camera 2 api in our devices and i don't think they will bother..maybe incorporate it in future devices or something.

ref

M7ammad said:
@BlAckXpeRia
Let's show them the demand
Click to expand...
Click to collapse
I think we did it! Look at the Z3+. It supports all manual functions exept RAW.

BlAckXpeRia said:
I think we did it! Look at the Z3+. It supports all manual functions exept RAW.
Click to expand...
Click to collapse
''We did it'' one may say only when Sony pushes this API on all LP devices. Untill then, and i think they will keep it that way because they need to seel the new phone somehow, we should keep raising our voice, as it is not fair to have a damn good hardware that is ''ruined'' by lousy software. They need to enhance it ASAP in my opinion, or else Sony is risking a bad reputation going even worse...

bubimir13 said:
''We did it'' one may say only when Sony pushes this API on all LP devices. Untill then, and i think they will keep it that way because they need to seel the new phone somehow, we should keep raising our voice, as it is not fair to have a damn good hardware that is ''ruined'' by lousy software. They need to enhance it ASAP in my opinion, or else Sony is risking a bad reputation going even worse...
Click to expand...
Click to collapse
I think it will come atleast for Z2 and Z3. They are really similar. But no matter what Sony does, I am stuck with them. I just can't get away from that beautiful design and software. All other manufactures have things I hate(LG-plastic, Samsung-software, nexus line and motorola- awful camera). My only problem with Sony is the new API. And they don't forget their devices-even the 2012 xperia z has lollipop and may get M.

Its not guaranteed to come to z3 or even z2, z1 and grampa z we can now easily forget since z has an expired 18 months period and z1 is close to expiration... Further on, LG G$ as it stands has way more superior camera then z3, Samsung is also investing hugely in marketing, and only thing Sony needs to do basically to survive is to a) improve software department, not so much the overall UI but software in camera for instance, it lags behind Samsung, Apple and LG as things stand, but they mosty use Sony's hardware, more limited one, so there is no objection for not handling software part more effectivley. and B) to improve customer relations, as we all know Sony is always lagging with announcments for new software features, heck they event dont know if the M2 or T3 are in plans for LP upgrade (which is lousy)!!!!
Onwards, remember the explanation provided for question wheter Sony will publish and software update for camera2 API or not, Sony gave as a bunch of c**p and basically told us ''oh, go f**k yourself with that'' masked in ''if there will be public demand we will then see...''
Of corse there is public demand, why wouldn't there be on since people always appreciate good featured updates. Look at Samsung, they are doing everything they can to fix camera things, publishing updates more oftenlly then Sony Social networks CM published something on either Social network used by Sony.