Database Develop

Development is going to be good!

Alot of Developers have bought this phone!! development for Xperia T / TX and V is going to be good! so far we have 2 elite developers 2 recog developers,, correct me if i am wrong

FXP have 4 members
Bin4ry, Defer, Kali, Jerpelea

Codeworkx!
Tilal6991 too for paranoid android

Gok for kernel is gonna be beast.

Lol @ 4. Good start but not exactly a lot. Yet.
...

Not to doubt or anything but, what is Sony support looking like? I know dev support often is limited by the manufacturer. This isn't exactly the most active section either. Will having devs draw people in? Or will lack of people pull devs away?
Strong chance I'm getting the att version (TL) but, I will admit to being worried about lack of support after a year and having a year left one contract with no official support and lack of dev support because something flashier came out.

Snow_fox said:
Not to doubt or anything but, what is Sony support looking like? I know dev support often is limited by the manufacturer. This isn't exactly the most active section either. Will having devs draw people in? Or will lack of people pull devs away?
Strong chance I'm getting the att version (TL) but, I will admit to being worried about lack of support after a year and having a year left one contract with no official support and lack of dev support because something flashier came out.
Click to expand...
Click to collapse
well this is my first sony device, but looks promising, if sony stays open and doesn't screw up like samsung did, even if they are on updates, we'll have CM team for regural updates. actually, i hope this is first device i'll have for more than a year.
we'll see.
Sent from my Xperia T

Snow_fox said:
Not to doubt or anything but, what is Sony support looking like? I know dev support often is limited by the manufacturer. This isn't exactly the most active section either. Will having devs draw people in? Or will lack of people pull devs away?
Strong chance I'm getting the att version (TL) but, I will admit to being worried about lack of support after a year and having a year left one contract with no official support and lack of dev support because something flashier came out.
Click to expand...
Click to collapse
Support is looking good for devs to get started and this can be seen from the speed CM10 has become available and is progressing on this device. I don't see the lack of activity in this forum as a bad thing and for a dev it's a good thing because they're not hassled every 2 mins with the same repeated support questions or for ETA's (don't do it ). Devs don't choose devices because they're popular, they choose them because they're good to work on and because they personally like the device as remember this is a hobby after all. I for one, if I do get this phone will hope for it to remain as one of the quieter forums but once people start finishing their contracts I can see it attracting a number of people. I finish mine end of this month so that's when I'll be choosing but that choice is based on how easy it'll be to work with as I like to have a play with compiling myself but only for myself really.

I actually chose this device precisely hoping that it wouldn't become too popular. It becomes crazy when people start almost harassing you for a release.
With a less popular device its much more fun.

^aha your right
hello developer!

i think xperia t will get popular because it is the bond phone and the tx looks great in terms of design so it will get popular

Snow_fox said:
Not to doubt or anything but, what is Sony support looking like? I know dev support often is limited by the manufacturer. This isn't exactly the most active section either. Will having devs draw people in? Or will lack of people pull devs away?
Strong chance I'm getting the att version (TL) but, I will admit to being worried about lack of support after a year and having a year left one contract with no official support and lack of dev support because something flashier came out.
Click to expand...
Click to collapse
TL developer support is going to highly depend on the bootloader locking situation.
As I understand it, AT&T has a bad habit of forcing bootloader locks. I refuse to support any device that has a locked bootloader which is not officially unlockable - even if the lock gets broken unofficially, it's the principle of the thing.
tilal6991 said:
I actually chose this device precisely hoping that it wouldn't become too popular. It becomes crazy when people start almost harassing you for a release.
With a less popular device its much more fun.
Click to expand...
Click to collapse
Yeah. The Infuse was a less popular device, and as a result, the developer community was highly cooperative for a while. Unfortunately, the device itself was a nightmare to work with so it was ditched by many. Although, interestingly enough, now that some of the worst aspects of this device development-wise have been identified, the Infuse is becoming kind of fun to work with again.
In the case of the T - all evidence seems to indicate that it's going to be a highly pleasant device to work with, AND if it's not a super-popular device, it may have a more pleasant development community than some of the more popular devices.
There's an existing well-established team of developers with Sony experience, AND there are also a number of Samsung Exynos refugees that have already made the jump or (in my case) are just waiting to see what their local version of the T has to offer.
That said - based on the developers I've seen hopping over, things are going to be heavily weighed in the AOSP-based firmware side of things. Sony's recent devices have become very attractive to developers of AOSP derivatives due to:
Sony's cooperation with the community in terms of technical information and source releases (see DASH)
Most Sony devices are based on Qualcomm chipsets, and over the past year, CodeAurora has emerged as a high quality reference codebase. (CAF has existed for a long time, but it's not really until this year that I saw people using it heavily.)
Sony's explicit AOSP support, both in terms of binary releases to support JBQ's Xperia S project, and frequent commits to AOSP. In fact, they have one developer working part-time on the AOSP Xperia S tree!
However, going back to Snow_fox's comments - if you want a device that is guaranteed not to be dropped early, purchase a Nexus. With any non-Nexus device, you are always taking risks.
Look at the Samsung Exynos situation - A year ago, Samsung devices were looking like your best bet for ongoing developer support. However, over the past year, a variety of things have changed:
Samsung constantly releases broken HALs that require all sorts of workarounds, and don't play nicely with backwards-compatibility solutions that work on other devices. ICS and JB bringup on Exynos4 devices has been an utter nightmare, leading to the entire team of CM on Exynos devices burning out or coming damn close to it
Samsung decided to use their phones as an outlet for gigantic batches of defective eMMC flash chips. They put workarounds in their firmware but didn't tell anyone. The end result is that you have to tread carefully with any 2011-model Samsung device. Their poor handling of the eMMC disaster has left a sour taste in many developers' mouths.
As a result, many developers are leaving, not necessarily for a device that is flashier, but one that is at least more developer-friendly. I think that in many cases, the Xperia TL will be a downgrade for me compared to my Galaxy Note... But dealing with the Exynos in the Note is driving me utterly insane.

AvRS said:
Support is looking good for devs to get started and this can be seen from the speed CM10 has become available and is progressing on this device. I don't see the lack of activity in this forum as a bad thing and for a dev it's a good thing because they're not hassled every 2 mins with the same repeated support questions or for ETA's (don't do it ). Devs don't choose devices because they're popular, they choose them because they're good to work on and because they personally like the device as remember this is a hobby after all. I for one, if I do get this phone will hope for it to remain as one of the quieter forums but once people start finishing their contracts I can see it attracting a number of people. I finish mine end of this month so that's when I'll be choosing but that choice is based on how easy it'll be to work with as I like to have a play with compiling myself but only for myself really.
Click to expand...
Click to collapse
I will have to decide on December 1st what phone I'm going to myself.
I personally understand the appeal of a quieter forum where the same issues aren't asked every couple of minutes.. Once or twice, I've actually had trouble finding a solution wading through the, "How do I ________" and most of them had the response, "do a search" :silly:
tilal6991 said:
I actually chose this device precisely hoping that it wouldn't become too popular. It becomes crazy when people start almost harassing you for a release.
With a less popular device its much more fun.
Click to expand...
Click to collapse
Yeah.... there are a lot of ungrateful members. I find myself in an awkward position because, I'm not skilled enough to develop a ROM but, I'm know I'm reliant on whatever XDA puts out to stay up to date with the latest ROMs.
Entropy512 said:
TL developer support is going to highly depend on the bootloader locking situation.
As I understand it, AT&T has a bad habit of forcing bootloader locks. I refuse to support any device that has a locked bootloader which is not officially unlockable - even if the lock gets broken unofficially, it's the principle of the thing.
Click to expand...
Click to collapse
If I were in a position to take that stance, I would myself.
[/QUOTE]
There's an existing well-established team of developers with Sony experience, AND there are also a number of Samsung Exynos refugees that have already made the jump or (in my case) are just waiting to see what their local version of the T has to offer.
That said - based on the developers I've seen hopping over, things are going to be heavily weighed in the AOSP-based firmware side of things. Sony's recent devices have become very attractive to developers of AOSP derivatives due to:
Sony's cooperation with the community in terms of technical information and source releases (see DASH)
Most Sony devices are based on Qualcomm chipsets, and over the past year, CodeAurora has emerged as a high quality reference codebase. (CAF has existed for a long time, but it's not really until this year that I saw people using it heavily.)
Sony's explicit AOSP support, both in terms of binary releases to support JBQ's Xperia S project, and frequent commits to AOSP. In fact, they have one developer working part-time on the AOSP Xperia S tree!
However, going back to Snow_fox's comments - if you want a device that is guaranteed not to be dropped early, purchase a Nexus. With any non-Nexus device, you are always taking risks.
[/Quote]
That unfortunately isn't really entirely an option for me. I'm on a family plan and have no capability of getting out of it at the moment. I don't have enough data to make 16 gigs with no SD card feasible.
I really got lucky when my Captivate had identical hardware to the Nexus S and Samsung was actually good about supporting the devs.
Look at the Samsung Exynos situation - A year ago, Samsung devices were looking like your best bet for ongoing developer support. However, over the past year, a variety of things have changed:
Samsung constantly releases broken HALs that require all sorts of workarounds, and don't play nicely with backwards-compatibility solutions that work on other devices. ICS and JB bringup on Exynos4 devices has been an utter nightmare, leading to the entire team of CM on Exynos devices burning out or coming damn close to it
Samsung decided to use their phones as an outlet for gigantic batches of defective eMMC flash chips. They put workarounds in their firmware but didn't tell anyone. The end result is that you have to tread carefully with any 2011-model Samsung device. Their poor handling of the eMMC disaster has left a sour taste in many developers' mouths.
As a result, many developers are leaving, not necessarily for a device that is flashier, but one that is at least more developer-friendly. I think that in many cases, the Xperia TL will be a downgrade for me compared to my Galaxy Note... But dealing with the Exynos in the Note is driving me utterly insane.
Click to expand...
Click to collapse
Do you think that may have some weight on why Google decided to hop to LG for a Nexus device?
Either way, it sounds like I'll be on the Xperia TL or LG Optimus G this upgrade. The decision isn't exactly becoming easier to make though. At least I managed to scratch off the HOX+

i chose xperia phones becase developers say they are not hard to develop , i have an xperia ray and i have a buttload of roms to choose from... i cant decide so i need to fash every 2week!! (flashaholic :l)

also because sony provides solution for bootloader unlock

Here's what I know so far for the TL. Keep in mind none of this is official, and it is preliminary, so could change.
1) The bootloader will NOT be unlockable on any device that has an active SIMlock. e.g. any device sold on AT&T with a contract subsidy is not going to have an unlockable bootloader. This is almost 100% definite.
2) The bootloader should be unlockable for users who pay full price for the device from AT&T, e.g. anyone who can receive an immediate SIM unlock with AT&T's policies. That said, while AT&T says that any person with a full-price device should be able to immediately remove SIMlocks, often it's a major hassle, and I worry that the bootloader unlock "allowability" process will be even less integrated. Don't count on unlocking your bootloader if you purchase full-price directly from AT&T.
3) Sony may sell the device directly (again - they MAY do it, it's not guaranteed), direct-purchase devices will almost surely have an unlockable bootloader (Not guaranteed, but very likely).

Well,TX seems doesn't support for the rom made to T:crying:

niuzhd said:
Well,TX seems doesn't support for the rom made to T:crying:
Click to expand...
Click to collapse
of course not. It's a different device

Coming from laggy XS, now holding TX,
Sony is doing it right this time, TX design and ICS are so smooth, fast and bug free( at least haven't encounter any yet), TBH I don't have any intention to flash Rom or wait for update (JB).
Sent from my LT29i using xda app-developers app

Waiting for my first room tanks all
Envoyé depuis mon LT30p avec Tapatalk

[Q] CyanogenMod on the z?

I want this hardware with cm or pure aosp software, and I'd love it if you all could share some of your knowledge:
What are the challenges, obstacles, and chances of cm on this device happening?
I don't know much about Sony and their way of locking or unlocking the bootloader, so what can we expect here?
Codeworkx praise Sony for their recent contribution to the community, can we expect this to continue?
Are there any new proprietary additions to this phone compared to the other xperia line, something new that will prevent cm running smoothly?
How are the free xperia team going with their work?
Please share and enlighten me.

Just wait for FXP http://code.google.com/p/freexperia/
---------- Post added at 08:07 PM ---------- Previous post was at 08:06 PM ----------
Also
http://freexperiaproject.com/

dioggo92 said:
Just wait for FXP http://code.google.com/p/freexperia/
---------- Post added at 08:07 PM ---------- Previous post was at 08:06 PM ----------
Also
http://freexperiaproject.com/
Click to expand...
Click to collapse
Cool, but have they succeed with proper ports of cm to xperia, no battery issues, no camera issues, all hardware working properly?
The z has the new "dual camera thingy" (i can't remember what the press release called it) for proper hdr, and considering this is a somewhat new invention, will Sony give out proprietary sources/drivers to create open source versions?

CyanogenMod went well for my arc S, and is coming alon great for my Xperia T.
I can't imagine why the XZ will be any worse.
I think it will actually be better as the XZ will be released on 4.1, with the promise of 4.2 coming soon after.
I can't see poor development being an issue with this device.

You never know until release what the exact problems with a device are going to be.
That said, given how Sony is diverging less and less from reference sources for various platforms with each generation and the fact that it has the exact same SoC as the Nexus 4 - it's looking VERY promising.

Entropy512 said:
You never know until release what the exact problems with a device are going to be.
That said, given how Sony is diverging less and less from reference sources for various platforms with each generation and the fact that it has the exact same SoC as the Nexus 4 - it's looking VERY promising.
Click to expand...
Click to collapse
So exciting! really looking forward!

cant wait to see this phone..also cant wait to see stock Android on this.

Entropy512 said:
You never know until release what the exact problems with a device are going to be.
That said, given how Sony is diverging less and less from reference sources for various platforms with each generation and the fact that it has the exact same SoC as the Nexus 4 - it's looking VERY promising.
Click to expand...
Click to collapse
Cyanogen launched M builds, which are most stable builds and a few phones launched them. Do you know what is reason, why M builds aren't available on any Sony phone yet (for example Xperia T) ? I thought M builds will be available on phones, which are easier to develop - for example, Nexus, US SGS3, latest Sony phones etc. Thanx

-A-P-M- said:
Cyanogen launched M builds, which are most stable builds and a few phones launched them. Do you know what is reason, why M builds aren't available on any Sony phone yet (for example Xperia T) ? I thought M builds will be available on phones, which are easier to develop - for example, Nexus, US SGS3, latest Sony phones etc. Thanx
Click to expand...
Click to collapse
Hmm, wonder if cm doesn't officially support Sony, that it is only the free xperia TM that does the conversion. But I dunno for sure
Edit: nope, never mind : http://wiki.cyanogenmod.org/index.php?title= Devices
A lot of Sony officially supported. I just never read the list

Eddiemc said:
Hmm, wonder if cm doesn't officially support Sony, that it is only the free xperia TM that does the conversion. But I dunno for sure
Edit: nope, never mind : http://wiki.cyanogenmod.org/index.php?title= Devices
A lot of Sony officially supported. I just never read the list
Click to expand...
Click to collapse
Fxp are the official maintainers for Sony devices for cm. Once the build is stable it is approved by cm and supported, that's how it works for now.
But I'm guessing it'll change as more people will buy Sony and with more developer support who knows might speed up. For now only 4 people (Fxp) manage over 25 Sony devices to get cyanogenmod on them.
Sent from my Xperia S running 4.2.1 using xda premium

mzr7 said:
Fxp are the official maintainers for Sony devices for cm. Once the build is stable it is approved by cm and supported, that's how it works for now.
But I'm guessing it'll change as more people will buy Sony and with more developer support who knows might speed up. For now only 4 people (Fxp) manage over 25 Sony devices to get cyanogenmod on them.
Sent from my Xperia S running 4.2.1 using xda premium
Click to expand...
Click to collapse
How's your xperia s running with that rom (assuming you're running cm, aosp, or aosp)?
I'm asking to get an idea of what to expect in terms of cm/aosp on the z.
I looked at a few videos of Sony's 4.1.1 rom on the pre prod models of the z and i was not very impressed with their work.
I "need" to be able to run cm or any aosp rom as soon as it's in my hands. Yea, I know it's a bit stupid then to not buy a nexus, but i want z hardware (and water proof) and expandable memory. Since nexus won't give me that, perhaps Sony can..?
I'm willing to sacrifice some functions, as long as the camera works (don't need effects, just clear pics) and the battery is good. (bravia and stamina can be sacrificed too, as long as cm doesn't drain more than stock sony)
Atm I'm on sgs3 and cm doesn't work very well battery wise (with 6-9% idle drain pr hour) and also too many camera issues. Having to cripple all the "smart" functions of a smartphone to get acceptable battery just doesn't make sense, so please share some of your views on Sony/cm in this regard.

mzr7 said:
Fxp are the official maintainers for Sony devices for cm. Once the build is stable it is approved by cm and supported, that's how it works for now.
But I'm guessing it'll change as more people will buy Sony and with more developer support who knows might speed up. For now only 4 people (Fxp) manage over 25 Sony devices to get cyanogenmod on them.
Sent from my Xperia S running 4.2.1 using xda premium
Click to expand...
Click to collapse
Im not familiar with Sony's dev community, because Xperia Z will be my first Sony's Android phone. Im wondering If Codeworkx get Xperia Z, he will became official maintainer with Fxp for Xperia Z ? Is Codeworkx's CM10 build for Xperia T different to Fxp's CM10 build, or they work together?
Thanx

-A-P-M- said:
Im not familiar with Sony's dev community, because Xperia Z will be my first Sony's Android phone. Im wondering If Codeworkx get Xperia Z, he will became official maintainer with Fxp for Xperia Z ? Is Codeworkx's CM10 build for Xperia T different to Fxp's CM10 build, or they work together?
Thanx
Click to expand...
Click to collapse
Codeworkx is different from Fxp. Anywho Fxp has listed z in its supported devices now on its website so yeah i think you can count them in.
It'll depend on codeworkx if he wants to join Fxp or not. I don't have the Xperia t so can't be sure about what you asked. I'll check the thread out and let you know.
Sent from my Xperia S using xda premium
---------- Post added at 09:40 AM ---------- Previous post was at 09:28 AM ----------
Eddiemc said:
How's your xperia s running with that rom (assuming you're running cm, aosp, or aosp)?
I'm asking to get an idea of what to expect in terms of cm/aosp on the z.
I looked at a few videos of Sony's 4.1.1 rom on the pre prod models of the z and i was not very impressed with their work.
I "need" to be able to run cm or any aosp rom as soon as it's in my hands. Yea, I know it's a bit stupid then to not buy a nexus, but i want z hardware (and water proof) and expandable memory. Since nexus won't give me that, perhaps Sony can..?
I'm willing to sacrifice some functions, as long as the camera works (don't need effects, just clear pics) and the battery is good. (bravia and stamina can be sacrificed too, as long as cm doesn't drain more than stock sony)
Atm I'm on sgs3 and cm doesn't work very well battery wise (with 6-9% idle drain pr hour) and also too many camera issues. Having to cripple all the "smart" functions of a smartphone to get acceptable battery just doesn't make sense, so please share some of your views on Sony/cm in this regard.
Click to expand...
Click to collapse
Oh my version! Well this new group popped up they made cm10.1 for Xperia S can't be used as a daily driver as of now was just testing it they launched it about a week ago still fixing it up . Other than that i am running cm10.
As far as your questions go Sony supports developers! If you want to get cm on your device don't get it from a carrier! Get it unlocked like me unlock the bootloader and start flashing!
Xperia z shares many similarities in hardware with the nexus 4 so I'm guessing that would mean faster development. The only issue I can think of is camera since its a Sony proprietary! Like with the Xperia S. Had to wait till Fxp got a hold of a leaked beta jb driver. Still doesn't support 1080p video. But it works! On the other hand xperia T has full camera I think and cm10.1 is being worked on.
Bottom line you won't get it asap but you'll get it! Cause here is the thing Sony supports developers and stuff but mostly people go out get a Samsung or htc. Maybe that's why development is a bit slow paced.
If I were you I'd wait a month maybe? Just to see how things go over here in the development forum.
Keep visiting xperiablog.com (everything related to xperias)
And also http://freexperiaproject.com
You'll get an idea of how it's going.
Or you could get it play with the stock Sony rom! Till development kicks in Ps you'll fall in love with the media apps I'm telling you!!
http://forum.xda-developers.com/showthread.php?t=2099499 (here's the rom I'm running right now)
Sent from my Xperia S 4.2.1 using xda premium

AW: [Q] CyanogenMod on the z?
For you to know.
We work together on the CM trees for Sonydevices with codeworkx. There is no difference between FXP releases and CM releases except the buildserver and the more updated FXP releases, because wr dont push our changes everytime directly to git.
So no difference between codeworkx work and FXP work. We all on the same ship and work TOGETHER on the stuff. Sometimes more sometimes less, because anyone can have private problems or just no time for the hobby.
Dont worry about CM support. We will support any WORLD phone from Sony in CM asap.
Regards

Bin4ry said:
......
Dont worry about CM support. We will support any WORLD phone from Sony in CM asap.
Regards
Click to expand...
Click to collapse
Bin4ry, perhaps you can share some thoughts on cm on this device: Proprietary camera sensor.., battery workings, bootloader and customization, what to expect..?
Support is one thing, working rom is another. Are there any major issues to be expected, or do you reckon this will be smooth sailing? Also, how are the other sony/xperia devices running with cm now? Any big issues?
Thanks mate

I'm sure that CM will run on Z pretty much the same as it runs on nexus 4 . Tell you why . The main point is that they use the same SoC , next, quallcom's documentation is open source because Q has a developer friendly policy :thumbup:
Though some hardships might be faced when dealing with telephone part and camera which will obviously need some time to get fully working. However considering the coding level of CM developers I beleive that thet will put things on right places in a couple of builds .
Sent from my GT-I9300 using xda premium

-A-P-M- said:
Cyanogen launched M builds, which are most stable builds and a few phones launched them. Do you know what is reason, why M builds aren't available on any Sony phone yet (for example Xperia T) ? I thought M builds will be available on phones, which are easier to develop - for example, Nexus, US SGS3, latest Sony phones etc. Thanx
Click to expand...
Click to collapse
I covered this a few weeks ago on Google+, but mainly:
A decision was made to "pull an aries" with CM10.1. That means rebasing as much as possible onto the Mako kernel base, just like the Galaxy S (aries) family device maintainers rebased onto the Nexus S kernel base.
The bad: In the short run, when the effort is underway, the device will appear to be behind others.
The good: Once the effort is complete, it should be MUCH easier to keep the device up to date. See the original Galaxy S (aries) family of devices. You know, "the device that just won't die".
There was a pretty big influx of new developers to the platform a month ago, and some of us are still getting up to speed and learning things. For example, I've been focusing on what could best be described as "polishing" on CM10... Taking those little minor annoyances and squashing them. I'll transition over to 10.1 when I'm done. It's kind of nice that I can actually do something like this... Instead of fighting generic platform brokenness all over, I'm working on polishing up a few very minor annoyances. Seriously, my list of things to work on is "broken scaling of anamorphic videos over HDMI"... That's a lot better than "HDMI no worky" on Samsung Exynos devices.
Bin4ry said:
For you to know.
We work together on the CM trees for Sonydevices with codeworkx. There is no difference between FXP releases and CM releases except the buildserver and the more updated FXP releases, because wr dont push our changes everytime directly to git.
So no difference between codeworkx work and FXP work. We all on the same ship and work TOGETHER on the stuff. Sometimes more sometimes less, because anyone can have private problems or just no time for the hobby.
Dont worry about CM support. We will support any WORLD phone from Sony in CM asap.
Regards
Click to expand...
Click to collapse
As I understand it, the FXP builds will sometimes contain things that have yet to be merged into the main CM baseline via Gerrit.
For those coming from Samsung devices that codeworkx or I or any of the other CM people have worked on - Think of it as the difference between nightlies and the occasional experimental "test build" from maintainers. With the main difference being that FXP builds are always built each week whether or not there might actually be a difference.
(Correct me if I'm wrong here please.)

Entropy512 said:
You never know until release what the exact problems with a device are going to be.
That said, given how Sony is diverging less and less from reference sources for various platforms with each generation and the fact that it has the exact same SoC as the Nexus 4 - it's looking VERY promising.
Click to expand...
Click to collapse
Exactly, with key lime pie coming up, all we can do is wait

beeboss said:
I'm sure that CM will run on Z pretty much the same as it runs on nexus 4 . Tell you why . The main point is that they use the same SoC , next, quallcom's documentation is open source because Q has a developer friendly policy :thumbup:
Though some hardships might be faced when dealing with telephone part and camera which will obviously need some time to get fully working. However considering the coding level of CM developers I beleive that thet will put things on right places in a couple of builds .
Sent from my GT-I9300 using xda premium
Click to expand...
Click to collapse
I'm also absolutely sure it will be smooth as nexus 4

after 3 weeks
We have everything working,... according to changelog...backlight is ok now, even the FMRadio is working now...
So Can we expect made working the last thing - CAMERA ?:victory::good:
PS: i know this is "headshot" question...but i would like to know whether there is some problem and there will be NO camera...or if i just should wait for some weeks ?

[Q] ROM Development?

Love my Z1 so far but..
Wondering about 3 things at the moment,
1. Will Sony ever fix the camera issue for the bootloader?
2. If so, Will there be a great amount of ROM development like for example the Galaxy series.
3. Are we gonna see some nice updates from Sony in the near future? ( Camera fix, 4.3/4.4?)

zippy1990 said:
Love my Z1 so far but..
Wondering about 3 things at the moment,
1. Will Sony ever fix the camera issue for the bootloader?
2. If so, Will there be a great amount of ROM development like for example the Galaxy series.
3. Are we gonna see some nice updates from Sony in the near future? ( Camera fix, 4.3/4.4?)
Click to expand...
Click to collapse
Sony will definitely sort the camera issue out with regards to the bootloader.
We have two fantastic devs already, krabappel2548 & DooMLoRD, more will come if they think the Z1 is worth developing for.
Updates will come when and where Sony sees fit to release them but we all hope for 4.4
Sent from my C6903 using XDA Premium 4 mobile app

I only miss lack of working recovery for 534!
I have unlocked bootloader of my old Z and after some time it brick's (nothing to do with unlocking) fortunately they exchanged it under warranty, but now i prefer not to unlock bootloader and only root (which is must!). Original ROM is very good

I'm really not missing having custom rom's because after rooting I'm using Xposed - have about 25 modules installed and my phone may as well have a custom rom on it because all the features I usually look for are there! With "Auto Hide Soft Keys" installed I've got the full screen size back and I'm really very very happy overall.
Normally I'd have installed a 'slim' or 'AOSP' type rom just for speed reasons, but the damn Snapdragon 800 is so fast it really doesn't matter that Sony preloaded a little bit of bloatware - and its not as pervasive & space consuming as Samsungs bloat.
The only features I'm missing are the kernel level features (Touch-to-wake please DooMLoRD!), but there's only one custom kernel for now and it requires a UB, so I'm waiting on that till they fix the TA partition stuff (though I know you can just restore the TA partition to fix the camera I don't feel the need to yet).
And to answer the questions:
1) Yes
2) Wait and see
3) Yes or they'll be abandoning their flagship phone to word of mouth and stale OS - not going to happen.

Uvaavu said:
3) Yes or they'll be abandoning their flagship phone to word of mouth and stale OS - not going to happen.
Click to expand...
Click to collapse
Sony and S/E HAVE done this before, look at the history...
Here is my answers to the 3 questions:
1. Proberbly not, it is a way to keep people from custom roms.
This way Sony can still claim "open bootloader" and "dev friendly", but Sony have done it this way for a reason...
2. Wait and see...
Without sources, the camera will proberbly not ever work on custom roms...
The way this phone is made, sony can in fact release sources as they have to, and leave out the sources for the camera...
3. Look at the Sony and S/E history... Android v4.3 is most certainly all you can expect, as they have to release 4.3 to meet Googles demands...
You will get bugfixes thoug...
I would have written "Sony is NOT stupid!" in the end of all 3 answers, but that looked a little angry...
- the fact is that Sony have NEVER done anything by mistake...!

Android L

Hello developers.Dont want to be annyoing but I'm new to this devicee and i kinda like it and tried lots and lots of roms for it, and you know that android L/Lollipop is coming soon out, and i want to ask if anyone is gonna like port it to our device because i know some really good developers like the major tonyp and other ones.So if yes i would be really really hyped for it like many other lol

i think that for the reply we have to wait CM12(?)sources comes out,but as i understood in the past our phone is supporting kitkat with a base that starts from ics sources,so we must wait and maybe isn't possible to port, but also for me it will be interesting if the devs can port a rom with lollipop.By the way i was thinking that we are running also some old version of the gapps to make it work with our device due to missing neon support(like youtube or google search for ex.),so don't know if it's possible

TheMysteryouse said:
Hello developers.Dont want to be annyoing but I'm new to this devicee and i kinda like it and tried lots and lots of roms for it, and you know that android L/Lollipop is coming soon out, and i want to ask if anyone is gonna like port it to our device because i know some really good developers like the major tonyp and other ones.So if yes i would be really really hyped for it like many other lol
Click to expand...
Click to collapse
We had to wait 3 months for CM11 M1 to come out after KitKat was released, and knowing that Lollipop is quite a large overhaul and that it fully uses the ART runtime, we can expect a larger delay for CM12 M1. And even when it comes out, it will be almost featureless. As far as I know, Lollipop sources haven't been yet released, so we'll have to wait and see.
Second, yes, we are running on old ICS sources, so unless the 3.x kernel becomes super stable so we can use newer drivers, if they are available for our device, we'll have a bad time.
Third, this is a subforum for Development Discussion, so this kind of thread is more welcomed in the General Discussion section or even Q&A.
Keep on modding Other than that, KitKat development has been quite amazing in the last few months, and considering that the O2X is a device released in 2011, we are more than been blessed regarding this device. Ludnica, brate, ludnica.

Jes jes hahaha. Well whatever happens we will maybe be able to get something of it.I will try my best.I dont rly know much about coding but i know some stuff and i am learning every day more and more so yeah.I hope if we all combine our inteligence we will get something.
Oh and the sources should be out on i think November 5th

Testing Platform available
I like the idea of L for P990. I recently bought a new phone. That spares my P990 for testing full time as I have another phone for regular use. Please let me should you like to test anything, I will happily share the results. The least I can do to aid further development.

[q] wtf fxp ?????

If you didnt know yesterday the FXP team announced that it would begin lollipop nightlies for 12 Xperia devices, in which our SP isnt included. While reading the list with the 12 devices i realised that devices that are WAY less powerfull like the E3 will get support, and our device which in my expierience seems to run lollipop with ease doesnt get support.
This really frustrated me, as i dont understand why would they do that. Does anyone have an explanation ???
Btw happy holidays everyone

Different phones = different problems. Some phones are more easy to make ports. And other fact is what the XSP developer community is not too big, we don't have much developers working on our phone. More popular phones have more developers, bringing ports more quickly. We have some devs working to bring Lollipop to us, already have a almost fully working build of 5.0 for LBL, which is more harder to port. Unlocked BL only maybe is coming soon. What rest for us is only wait. If someone can't wait is easy: just learn how to develop a ROM and build it for yourself.

Dammer Martins said:
Different phones = different problems. Some phones are more easy to make ports. And other fact is what the XSP developer community is not too big, we don't have much developers working on our phone. More popular phones have more developers, bringing ports more quickly. We have some devs working to bring Lollipop to us, already have a almost fully working build of 5.0 for LBL, which is more harder to port. Unlocked BL only maybe is coming soon. What rest for us is only wait. If someone can't wait is easy: just learn how to develop a ROM and build it for yourself.
Click to expand...
Click to collapse
If it works for LBL, it will definitely for UBL Just saying

bamiasHELLAS said:
If you didnt know yesterday the FXP team announced that it would begin lollipop nightlies for 12 Xperia devices, in which our SP isnt included. While reading the list with the 12 devices i realised that devices that are WAY less powerfull like the E3 will get support, and our device which in my expierience seems to run lollipop with ease doesnt get support.
This really frustrated me, as i dont understand why would they do that. Does anyone have an explanation ???
Btw happy holidays everyone
Click to expand...
Click to collapse
Newer devices first.Even XZ is not listed,so there is no way SP could make up in the list.