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 ?
Related
Hi all devs,
We just released a blogpost http://developer.sonyericsson.com/wp/2011/12/15/ice-cream-sandwich-alpha-rom-available-for-unlocked-xperia-phones/ announcing that we have made an ICS alpha ROM available for users with very good tech skills. This means that you should have an unlocked boot loader http://unlockbootloader.sonyericsson.com, and have the knowledge to switch between different ROMs (read our blog post for further disclaimers ; ) ). Also, please note that the released SW is only applicable for Xperia™ arc S, Xperia™ neo V and Xperia™ ray. Xperia™ arc will not work, as it has different partition layouts.
http://dl-developer.sonyericsson.com/Xperia/ICS/Alpha/Xperia_arcS_ICS_alpha_EULA.html
http://dl-developer.sonyericsson.com/Xperia/ICS/Alpha/Xperia_neoV_ICS_alpha_EULA.html
http://dl-developer.sonyericsson.com/Xperia/ICS/Alpha/Xperia_ray_ICS_alpha_EULA.html
This is the first time we have done an activity like this and I, and all others behind this really value your feedback https://www.surveymonkey.com/s/STRJKQF. The release of the ICS alpha ROM is our way of sharing where we are with the ICS upgrade project. My team at Developer World, also published an article last week outlining the different activities we have to pass before releasing an official ICS ROM http://developer.sonyericsson.com/wp/2011/12/07/ice-cream-sandwich-from-source-code-release-to-software-upgrade/. Looking at that article I would say that we are now in the Bringup phase. You will also quickly see that we have not passed certification and approval phase, since we were not allowed to have the radio module turned on. This means that you can’t make any phone calls or use Wi-Fi. However, I still thought that this will be valuable to the tech community. Youtube video: http://www.youtube.com/watch?v=QoIsNYR7XJ8
What you can do is to test ICS applications early on, and you can also give us feedback on this initiative, and what you think about the ICS alpha ROM. Did it meet your expectations? What things would you wish for. We have a link to a survey in the blog post, where you can submit your feedback. But hey, I can’t promise that we can take care of all requests, as I know you will have plenty… Lastly I believe this release will benefit the custom ROM developers so they can see where we are in our process and how we have solved different things.
Share your opinions!
/Karl-Johan “Kalle” Dahlström
Sony Ericsson Developer Program
http://www.sonyericsson.com/developer
This a great step from SE. We'll be happy to test and provide feedback.
Keep up the good work
That's awesome!
Thanks for releasing the alpha builds and supporting the modding community!
Keep up the good work
Sent from my iPad 2 using Tapatalk
WOOOW, SE Development Team is fantastic!
Little question:
Xperia arc not yet?
WOW! This is seriously fantastic! When you first announced you were supporting FXP and made camera libs avaiable, I thought that was amazing. But letting the community try you guys have achieved is so cool! This is the most awesome thing, I have ever seen a company do, seriously!
I have seen something similair before, where devs. make an alpha-release, and already from there, want different oppinions and built from that. Keep involving with the community SE!
FreeXperia Team want to say thanks to SonyEricsson for the great Communitywork you are doing!
Best Regards
That's nice, but I have two questions.
The final ICS for Xperia will look different, fresh, right? Becuase this one looks just like Gingerbread.
I noticed on that video, that you have to long press home button to get the list of running apps. Isn't ICS supposed to get rid of the menu button, by making it to work like home long press used to in Gingerbread?
great move from SE!!!
Hmmm what will happen if i flash this to my Play? Not the best idea right?
IE-coRe said:
Hmmm what will happen if i flash this to my Play? Not the best idea right?
Click to expand...
Click to collapse
I wouldn't think this would be a good idea lol.
Anyone read this its inside the "readme" Also, if you unlock the boot loader, you will not be able to download and install the final Ice Cream Sandwich software upgrade from Sony Ericsson.
For additional information on limitations and warranty, please see the Sony Ericsson Unlock boot loader service.
Spot on SE Dev team, you guys are leading the way these days when it comes to the support for the people that people ask what phone to get, as lets be honest everyone ask's there "Geek" friends what phone to get and the love that SE gives to us just goes to show you are a company that really does care what we the users want to see in the products we buy from you.
Great Work!!!
What about Vanilla 4.0?
sahibunlimited said:
Great Work!!!
What about Vanilla 4.0?
Click to expand...
Click to collapse
CM9 is the answhere.
why not arc...sigh....
KalleD said:
Share your opinions!
Click to expand...
Click to collapse
I already did mine through a comment on your blog post.
However, I will repost it here:
First of all, let me congratulate you for the effort and transparency you’re putting into this. This bridge Sony Ericsson is attempting to create in order to involve more experienced or curious consumers and developers is something that greatly makes me proud for picking your products in the first place.
Since you’ve already demonstrated to value our opinion, I hope you’ll consider mine:
Please, consider upgrading the kernel version to 3.0. The 2.6.32 you have on Gingerbread, and by looking at the demo you just posted it will also be on ICS, is severely outdated (October 2009). 2.6.32 was the official version for Froyo whereas 2.6.35 was for Gingerbread and 3.0 is for ICS. Anyone inside the kernel world knows that a great deal of optimizations separate these versions (RCU, CPU scaling, SLAB, MM, PM, …) which have a deep impact on the overall experience.
Sadly to say, Sony Ericsson competitors aren’t keeping themselves on 2.6.32 (all of them advanced to .35 on Gingerbread and probably 3.0 on ICS) and this may cause an undesirable discrepancy in experience not in favor of your products. I also know that this probably means rewriting a few libs or drivers there and there but you can’t deny it will be worth in the end.
In my opinion, the benefits of pushing the kernel version to 3.0 far outweigh the increased delay you may have on releasing ICS (1 month?). Do consider this.
Click to expand...
Click to collapse
Can ARC flash this rom?
Deaw^^ said:
Can ARC flash this rom?
Click to expand...
Click to collapse
Can you read?!?
Great move Sony Ericsson!
Please note that you can’t use the original Xperia™ arc or Xperia™ neo, as they have different partition layouts.
Click to expand...
Click to collapse
I am very disappointed!
btw great work SE!
waiting for Xperia Arc
and i hope the final version looks different, because current one looks like gingerbread
this has to be a first!!!
brilliant work SE!
kudos to u guys!
This is a brilliant device. Unfortunately so few development going on...
Sent from my One S using xda app-developers app
yuan_1202 said:
This is a brilliant device. Unfortunately so few development going on...
Sent from my One S using xda app-developers app
Click to expand...
Click to collapse
It is brilliant, so brilliant that I moved to this from my Nexus 4. Sony UI is something I can live with for a very long time due to everything being minimalistic and close to stock but better than stock in every way. If I wanted better development I would move back to Nexus 4 in a heart beat but I don't think I will ever go back to Nexus.
Sent from my C5503 using xda app-developers app
I agree
Its so bad that this device hasnt got the attention it deserves. I have pm krabbapel and he said he was going to make his carbon rom in the future, and doomlord said he didnt have the device so he wont be developing for it
FXP are already developing an CM rom for the ZR so this is a good start
I do agree even though SONY has its flagship Z1 Z and Z ultra, this is the sleeping giant workhorse that they need to highlight.
Starlith said:
It is brilliant, so brilliant that I moved to this from my Nexus 4. Sony UI is something I can live with for a very long time due to everything being minimalistic and close to stock but better than stock in every way. If I wanted better development I would move back to Nexus 4 in a heart beat but I don't think I will ever go back to Nexus.
Sent from my C5503 using xda app-developers app
Click to expand...
Click to collapse
Same here, I came from a Galaxy Nexus (Nexus S, Nexus One, and HTC G1 before that) and although I prefer stock Android, it lacks so many features. I found Sony's UI clean and refreshing without trying too hard. I haven't found a need to root this baby yet. My ZR on 4.1 does way more than my GNexus on 4.3 (minus the root features of course) out of the box. The small apps and killer camera are the icing on the cake. With that said, I like Sony's design and UI that I'm willing to upgrade my nexus 7 to an Xperia Tablet Z in the near future.
Sent from my Nexus 7 using Tapatalk 2
zytres said:
Its so bad that this device hasnt got the attention it deserves. I have pm krabbapel and he said he was going to make his carbon rom in the future, and doomlord said he didnt have the device so he wont be developing for it
Click to expand...
Click to collapse
It might be a long shot, but it was successfully done with the Oppo find 5 and the Faux Kernal...(I think!)
What they did was organise a donation fund to get Faux the phone...after that he was happy to develop his kernal for the phone.
Perhaps you could give Doomlord a poke to see if he would be willing to accept such a thing and then ask the ZR community to take part? (Or maybe ask the ZR people first to see if they would do it...then see if Doomlord would accept...)
Random idea, could work...
Darkfall231 said:
It might be a long shot, but it was successfully done with the Oppo find 5 and the Faux Kernal...(I think!)
What they did was organise a donation fund to get Faux the phone...after that he was happy to develop his kernal for the phone.
Perhaps you could give Doomlord a poke to see if he would be willing to accept such a thing and then ask the ZR community to take part? (Or maybe ask the ZR people first to see if they would do it...then see if Doomlord would accept...)
Random idea, could work...
Click to expand...
Click to collapse
xperia sp forum members donated funds to doomlord, and he developed for xSP maybe you could ask him first if he's on to the idea
+1.
Nice idea for our future.
I remember DoomLord replied that he probably won't be developing for XZR since he doesn't own the device.
Not sure if donation can help that though...
with such good specs at a low price i dont get why this is a low activity device...:crying:
yeah.. i think we can blame sony itself for this problem... I really like the ZR and I have it now.. been so satisfied with it... but, yeah, too few development.. and it will get only worst because sony will be launching the z1 mini.. which is really comparable to the zr... sony is trying to follow samsung - flooding the market with too many models that are closely similar to one another..
if someone heads up a donation box for Doomlord for him to buy the zr, I would gladly donate 50 dollars...
CressKH said:
I remember DoomLord replied that he probably won't be developing for XZR since he doesn't own the device.
Not sure if donation can help that though...
Click to expand...
Click to collapse
well try pm-ing doomlord about "donating" him a phone maybe its okay with him
---------- Post added at 12:44 PM ---------- Previous post was at 12:43 PM ----------
izzner said:
with such good specs at a low price i dont get why this is a low activity device...:crying:
Click to expand...
Click to collapse
its not available everywhere, if this continues (very few users and low development) the device will end up like the acro S look at the Acro S forums+ the fact that almost no RC or RD or RT are present in XZR forum makes it more likely that development will die after fxp supports ends
ngoralph said:
well try pm-ing doomlord about "donating" him a phone maybe its okay with him
---------- Post added at 12:44 PM ---------- Previous post was at 12:43 PM ----------
its not available everywhere, if this continues (very few users and low development) the device will end up like the acro S look at the Acro S forums+ the fact that almost no RC or RD or RT are present in XZR forum makes it more likely that development will die after fxp supports ends
Click to expand...
Click to collapse
there's 4 page development on Acro S! It's not much but still for a phone that expensive yet doesn't seem to have any great hardware it's quite much developments!
but for this phone that runs smoothly and better comparing to Xperia Z, ZL and has less size and less resolution (about 1/4 times which makes battery run double times) and less mass I think this device get fairly low attention comparing to others!! even for a developer this one must be much more exciting than Xperia Z!
sijav said:
there's 4 page development on Acro S! It's not much but still for a phone that expensive yet doesn't seem to have any great hardware it's quite much developments!
but for this phone that runs smoothly and better comparing to Xperia Z, ZL and has less size and less resolution (about 1/4 times which makes battery run double times) and less mass I think this device get fairly low attention comparing to others!! even for a developer this one must be much more exciting than Xperia Z!
Click to expand...
Click to collapse
sort of, however, sony priced the zr as if a flagship. truth to be told, it's marketed as a flagship in japan (xperia a), and it's no slug. still, with the relatively small price difference between z and zr, it's easy to see why people will get the z instead. the z is also released 6 month earlier.
besides, zr isn't released in as many markets as z.
as i've said before, since zr shares much with z, as long as development for z is there, zr will likely be supported as well, but without a dedicated dev using zr him/herself, it's hard to picture a very good development environment.
unless sony discount the zr significantly very soon. this is likely to continue.
(before you ask, japanese seem to have their own commnity and aren't participating in xda, so their large nos. mean nothing to us)
Why worry.. as long as there is Z development, we can port almost EVERYTHING to ZR (including ROM's an Kernels)
One more reason is that people who do contribute are not thanked properly I think.
totally agree
well i had a few devices before and now i have htc one s S4, galaxy s4, xperia ZR, iphone 5
before xperia ZR between all of my phone i would stand and say htc one s and iphone 5 have best batteries between my devices, between xperia x8, xperia acro S, Xperia go, xperia V, galaxy S3, iphone 5, galaxy s4, but now i can say ZR beat my one S battery and not only on battery it beats the battery on my one s it beats the performance of S4 it beats the options of all of my previous xperia phones, and when it comes to heat it even beats the hell out of my iphone too it hardly produce any heat in my hands specially compared to xperia V and galaxy s4.
this is an amazing device guys no doubt about it but why were we looking for development in the first place? when we had good hardware and sh**** software with cra*** software support we would come here and look for help, but we still have updates and support and this device is almost (not fully) complete it doesnt need overclock it doesnt need more battery saving options it doesnt need so much bug fixes.
the only thing it need is a better front camera which is impossible with firmware and kernels so most of all a few ports and customizations remains which is not totally important right?
when i first had my xperia acro S it didnt have any custom firmware for a very long time the only thing was available = rooting my device! believe me for a very long time it was like this.
so my advice is to take your time guys relax if something came out use it if not dont be disappointed you wont miss so much you still have a great device with so many good things on it.
dragunov_lq said:
this is an amazing device guys no doubt about it but why were we looking for development in the first place?
Click to expand...
Click to collapse
I absolutely agree!! Even I found nothing in the kernel to tweak
dragunov_lq said:
well i had a few devices before and now i have htc one s S4, galaxy s4, xperia ZR, iphone 5
before xperia ZR between all of my phone i would stand and say htc one s and iphone 5 have best batteries between my devices, between xperia x8, xperia acro S, Xperia go, xperia V, galaxy S3, iphone 5, galaxy s4, but now i can say ZR beat my one S battery and not only on battery it beats the battery on my one s it beats the performance of S4 it beats the options of all of my previous xperia phones, and when it comes to heat it even beats the hell out of my iphone too it hardly produce any heat in my hands specially compared to xperia V and galaxy s4.
this is an amazing device guys no doubt about it but why were we looking for development in the first place? when we had good hardware and sh**** software with cra*** software support we would come here and look for help, but we still have updates and support and this device is almost (not fully) complete it doesnt need overclock it doesnt need more battery saving options it doesnt need so much bug fixes.
the only thing it need is a better front camera which is impossible with firmware and kernels so most of all a few ports and customizations remains which is not totally important right?
when i first had my xperia acro S it didnt have any custom firmware for a very long time the only thing was available = rooting my device! believe me for a very long time it was like this.
so my advice is to take your time guys relax if something came out use it if not dont be disappointed you wont miss so much you still have a great device with so many good things on it.
Click to expand...
Click to collapse
This is EXACTLY why I'm still on locked BL! but anyway our device has lack of roms like Cyanogen Mod, AOSP, PAC MAN, AOSPA (Paranoid) and also bug free miui port! (which I like Pranoid and miui so much) I'm currently working on a port for miui (stock based one) but this is something hard to get! currently I'm getting bootloop at kernel and as I don't want to unlock my bootloader (I love BE2 ) it's really hard to get it booting, and I'm not sure if any developer wants to contribute or if I get any further than this but I'm trying to make it bookable at least
EDIT: good news is I just saw the miui boot screen, bad news is it's not more than 2 sec and still I don't have adb
EDIT: Do you guys have made or downloaded any rom based on stock 4.2.2? would you mind give me updater-script in your zip file /META-INF/com/google/android/updater-script
Thanks
EDIT: another good news is, got logcat ( have permission problems ) it would be great if anyone can give me an updater-script from downloaded or made stock rom (both 4.1.2 and 4.2.2 are welcome) please pm me
CyanogenMod recently pushed out stables for CM10.2 on a select range of devices announcing that, with this, their efforts would be solely focused towards the CM11 code branches. However, they also announced that any devices which received that RC1 of CM10.2 would too continue into CM11.
My question, considering we are still unfortunate enough to be on somewhat unstable nightlies (the notification sound delay, UI issues, application crashes) is, what will be the future of CyanogenMod on the O4x? Will we even make it to stable CM10.2?
Hopefully we can! This is such a brilliant device as you all know well, and the hardware restrictions of KitKat are supposed to be lowered anyway
For clarification, this is not a complaint, the work of the CyanogenMod Team is always much appreciated. I, and so many of you, have donated and thanked them and tested their software for them. This is merely to gain an understanding of where our device is headed so as to aid everybody here in the decision of whether to stick with the device or, should worse come to worse.... look for another :-/
csfrank271 said:
CyanogenMod recently pushed out stables for CM10.2 on a select range of devices announcing that, with this, their efforts would be solely focused towards the CM11 code branches. However, they also announced that any devices which received that RC1 of CM10.2 would too continue into CM11.
My question, considering we are still unfortunate enough to be on somewhat unstable nightlies (the notification sound delay, UI issues, application crashes) is, what will be the future of CyanogenMod on the O4x? Will we even make it to stable CM10.2?
Hopefully we can! This is such a brilliant device as you all know well, and the hardware restrictions of KitKat are supposed to be lowered anyway
For clarification, this is not a complaint, the work of the CyanogenMod Team is always much appreciated. I, and so many of you, have donated and thanked them and tested their software for them. This is merely to gain an understanding of where our device is headed so as to aid everybody here in the decision of whether to stick with the device or, should worse come to worse.... look for another :-/
Click to expand...
Click to collapse
probably no official CM11 for us, or 10.2 stable/rc, atleast in forseeable future. thankfully, we have some very skilled devs working on unofficial version of CM, & Vanir&Omni.
Flying_Bear said:
probably no official CM11 for us, or 10.2 stable/rc, atleast in forseeable future. thankfully, we have some very skilled devs working on unofficial version of CM, & Vanir&Omni.
Click to expand...
Click to collapse
Thank you, I was just wondering about the state of the official ROMs, it seems like the P880 has been forgotten about by CM
But, as you say, we are very lucky to have these fantastic devs building even better custom ROMs
Flying_Bear said:
probably no official CM11 for us, or 10.2 stable/rc, atleast in forseeable future. thankfully, we have some very skilled devs working on unofficial version of CM, & Vanir&Omni.
Click to expand...
Click to collapse
If everything is working right we should be able to submit it to cyanogenmod to get our nightlies back, but im not 100% sure
JoinTheRealms said:
If everything is working right we should be able to submit it to cyanogenmod to get our nightlies back, but im not 100% sure
Click to expand...
Click to collapse
Hopefully we can have the issues fixed
Can't wait to see the community development though, the new Android RunTime looks very fascinating :3
why dont u enter cyanogenmod and see with your eyes ? anyway. of course we dont see any support. its a miracle that we had that much support too. who will support a phone which doesnt even has the support of the official company ? LG only had 4.0.3 and 4.1.2 and thats all. isnt it already a miracle that we have 4.3.1 ? and we have also so many good developers that work for 4.4 ?
I don't understand why people want 4.4 so bad when it's one of the worst upgrades from Google i have ever seen. They had to launch 4.4.1 updates right away. You want a better software I agree thats needed but 4.4 isn't a solution.
Sent from my OptimusX4HD using xda app-developers app
Zhus06 said:
I don't understand why people want 4.4 so bad when it's one of the worst upgrades from Google i have ever seen. They had to launch 4.4.1 updates right away. You want a better software I agree thats needed but 4.4 isn't a solution.
Sent from my OptimusX4HD using xda app-developers app
Click to expand...
Click to collapse
Everyone wants KitKat because... Well, because it's new! Why not? I believe that pushing one's expectations beyond what is already achieved represents a strong impulse to improvement. Experimenting, trying new solutions, feeling the awesomeness of something that did not exist before is a powerful spring to the change, the change in itself is something that animates the developers and makes them work with no reward as if this was their job.
It has happened with all Android versions, and always there had been someone who felt amazed and wondered why should we need a new version.
kK can be (and probably is, but who am I to judge) one of the worst Android versions, but I am happy to see people trying to overcome all the problems related with making it work on a relatively old device, and I am happy if by testing what is being developed, and by giving my opinion I can be of some help to somebody.
Want to call it a game? Why not! Want to consider people like me as grown up kids that need something to play with? Well, yes, I am, and will always cheer a new Android version working on one of my devices with grateful heart.
Ricardo Cerqueira is no longer the maintainer of our device?
there is no one who will replace him?
It should be possible to join the CM team, if the 4.4 is running.
The tegra3 problems will hopefully not be a trap for it.
If there is a maintainer who can update CM once, there will be no real reason not to get official support.
Good news everybody!
On the CyanogenMod website, the P880 has been listed officially as one the devices to receive support further than the CM10.2 nightlies, which will be a win-win for everyone
Bye Bye CM !
DarkFantasy6 said:
Bye Bye CM !
Click to expand...
Click to collapse
Why do you say that? :-/
csfrank271 said:
On the CyanogenMod website, the P880 has been listed officially as one the devices to receive support further than the CM10.2 nightlies, which will be a win-win for everyone
Click to expand...
Click to collapse
I saw the latest list the have revealed now, this is great!!
Noticed though that they said MOST of the devices that have CM10.2 builds will move into CM11 nightly during the next weeks.. "Most" hopefully means the P880 as well!
faabak said:
I saw the latest list the have revealed now, this is great!!
Noticed though that they said MOST of the devices that have CM10.2 builds will move into CM11 nightly during the next weeks.. "Most" hopefully means the P880 as well!
Click to expand...
Click to collapse
Yes, hopefully!
But hey, a stable CM10.2 would even be fantastic, the community devs would appreciate it surely
We never got the m1 and stable so i hardly belive it that we get cm11. And without a good 3.4 kernel source from lg we wont feeo many adventafes of 4.4. but the awesome awesome optic would be nice Maybe im going to buy a Nexus 5. Im so frustrated of my lg optimus 2x and 4x. ONE update -.-
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.
... Is the question we get asked ALL the time on this forum. This is currently being written on my phone so there might be some typos. I'm going to try and explain why we as a community find it so hard to develop for this phone and maybe how we can solve it.
1. AOSP
Maybe one of the biggest issues with this phone - AOSP, and the device tree.
When Sony made this phone in 2014, Jellybean was originally made with this phone and it was very stable - whereas Sony rushed the Kitkat update, meaning that many, many bugs were left unfixed making the phone unstable. Sony couldn't be bothered to then support this phone any further and left us with this heap of a mess. They also rushed the kernel too - and this is where AOSP comes into play.
I recently posted in the AOSP support fourms about our phone and Sony said to boot into AOSP the phone would need to have extensive changes to the kernel to boot into AOSP. The reason they would have to make these changes (and by that they mean rework the entire ROM and firmware) is because Sony rushed the Kitkat update making everything unstable. This means that we have no full device tree meaning that building from source is very difficult. This is why Caio's CM11 is very buggy atm. Hopefully Caio and Kizoky will make a breakthrough soon. Good luck!
2. Why do we have so many Stock UI modified ROMs? (Yes, there is more to it than that)
It literally links in with the top post.
Because we have no full sources, we can't build free, custom ROMs that have nothing to do with Sony. If Sony gave us this (which right now Sony are not playing ball) we could, of course, build custom ROMs.
3. No support/repoduction? (I dont know if this phone is still being made)
Sony made a bad job of this phone; god, I would not buy this phone if it wasnt given to me. Support has ended for this phone because of its unpopularity; high cost, low-end specs, rushed updates. When Kitkat came out for us the update (as we know) was very rushed and a lot of users just... left this phone to mirgrate to different phones - my dad left this for a Galaxy A3 - and my god, what a phone that is for the price. Of course, a LOT of devs then left this phone, and so Sony left this phone as well.
This thread is in no way finished yet - there are many more things to add. I'm gonna get my hands dirty with this phone soon when summer break comes around for me, but ill start small until then. My plans are kernel first then maybe PA4 or CM developing, not sure yet.
Caio's and Kizoky's posts - thanks to them, @Caio99BR and @Kizoky
@Caio99BR
4. Why do the devs not like to develop for this device?
First because that reason #1 in first post, second because this is a low-end device, many of then not have a full developer (eg L1II, Xperia E) and when have most of then try to do something but is stopped by low knowledge or some impossible fix problem, third in my opinion is because confusion made in building a ROM to a new device.
5. Why are you building KitKat(CM11) and not JellyBean4.3(CM10.2)?
First problem: DualSim
Only CM11 support it, and we not have only the Single Variants, I have choiced this too for L3II, and this have been released with JB4.1.
After it this not have problems, the CM10.2 is more stable and with less ram consumption (like CM10.1 is more more stable and etc), but is more time lose if we back to it now, if someone want to make it, go and Good Luck
6. Why the greatest devs not make something to this device?
First thing is time, or if not time, just forgived this, 2 Recognized Developers (Yes, its a ****ing awesome flag) said "I have got this phone and I will do something for him", one posted at here on XDA, and other said it to me (member of FXP Team - greatest Team behind some Sony devices), today no one of two have made nothing, this last said "I will help you" but no, @Kizoky helped more than him, but I'm of subject.
By final its more a revolt than a answer, good devs after get flags, reputation, forgive simple things and not help others or not make that things he did to gain prestige.
Sorry if it not answer the ask, but it's the true, also sorry my english, its damaged.
@Kizoky
7. Low end phone
8. High price when phone released (Xperia E1 2014: 512mb 3MP Sony you are drunk vs. Xperia M 2013: 1024mb 5MP lower price)
9. Not available in the U.S
Good luck all with developing!
3. Why the devs not like to develop to this device?
First because that reason #1 in first post, second because this is a low-end devices, many of then not have a full developer (eg L1II, Xperia E) and when have most of then try to do something but is stopped by low knowledge or some impossible fix problem, third in my opinion is because confusion made in building a ROM to a new device.
4. Why are you building KitKat(CM11) and not JellyBean4.3(CM10.2)?
First problem: DualSim
Only CM11 support it, and we not have only the Single Variants, I have choiced this too for L3II, and this have been released with JB4.1.
After it this not have problems, the CM10.2 is more stable and with less ram consumption (like CM10.1 is more more stable and etc), but is more time lose if we back to it now, if someone want to make it, go and Good Lucky
---
Sorry if I'm using your space, but I like write some stupid/real things before sleep
1. Low end phone
2. High price when phone released (Xperia E1 2014: 512mb 3MP Sony you are drunk vs. Xperia M 2013: 1024mb 5MP lower price)
3. Not available in the U.S
Haha thanks you two for those additions! About to go through OP and add some stuff; but ill leave your posts up and I wont add that stuff you guys said
xeonyt12 said:
Haha thanks you two for those additions! About to go through OP and add some stuff; but ill leave your posts up and I wont add that stuff you guys said
Click to expand...
Click to collapse
OK XD, other thing to add:
- Why the greatest devs not make something to this device?
First thing is time, or if not time, just forgived this, 2 Recognized Developers (Yes, its a ****ing awesome flag) said "I have got this phone and I will do something for him", one posted at here on XDA, and other said it to me (member of FXP Team - greatest Team behind some Sony devices), today no one of two have made nothing, this last said "I will help you" but no, @Kizoky helped more than him, but I'm of subject.
By final its more a revolt than a answer, good devs after get flags, reputation, forgive simple things and not help others or not make that things he did to gain prestige.
Sorry if it not answer the ask, but it's the true, also sorry my english, its damaged.
Some fun facts:
* The touchscreen used in Xperia E1 is more old than JB, made for MTK devices
* The bar led is the same used Xperia E
* Maybe because the Camera sensor Sony not builded the Lollipop for this device, since it's too old too, and need some hacks in kernel to make it work (by now camera sensor is broken on my LP and after in MM ROM :/)
I think that's all, just for annotation.
Caio99BR said:
Some fun facts:
* The touchscreen used in Xperia E1 is more old than JB, made for MTK devices
* The bar led is the same used Xperia E
* Maybe because the Camera sensor Sony not builded the Lollipop for this device, since it's too old too, and need some hacks in kernel to make it work (by now camera sensor is broken on my LP and after in MM ROM :/)
I think that's all, just for annotation.
Click to expand...
Click to collapse
And sources for E1 is garbage
JB was rushed, and left buggy
KK was rushed, and left more buggy than JB
Sony didn't even bother to make this phone stable (and even refused to help E1 users)
Your CM11 is still has bugs, but it is more stable than Stock ROM, I wonder why..