Related
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 ?
I definitely appreciate the roms that SDBags and every other developer has made, but I was hoping for more options available, specifically in AOSP Roms. I love the transformer lineup because it is super useful as a cheaper high performing school laptop for note taking and has a stylus for taking notes with. But honestly, I rarely have cared for asus's stock software compared to AOSP, and AOSP definitely will give me much speedier performance, much more customization and much more recent updates overall.
Can any developers let me know why there haven't been more available AOSP Roms lately, or maybe its a problem with the tf701t hardware making it harder to Rom for? Or maybe not many people are buying this tablet? I just want an idea of what I would be in for if I buy this tablet soon.
Also, has any of the Tf700 tablet developers been asked to help develop for this tablet? (Just an Idea)
This is not a bashing on any developers who are making this Rom. Especially with SDBags. I have used his CROMI Roms on the TF300t all the time and they are AWESOME!!! I was just curious why the tablet hasn't gotten much attention in the ROMs section from hearing all sorts of good things from this tablet
royredman said:
I definitely appreciate the roms that SDBags and every other developer has made, but I was hoping for more options available, specifically in AOSP Roms. I love the transformer lineup because it is super useful as a cheaper high performing school laptop for note taking and has a stylus for taking notes with. But honestly, I rarely have cared for asus's stock software compared to AOSP, and AOSP definitely will give me much speedier performance, much more customization and much more recent updates overall.
Can any developers let me know why there haven't been more available AOSP Roms lately, or maybe its a problem with the tf701t hardware making it harder to Rom for? Or maybe not many people are buying this tablet? I just want an idea of what I would be in for if I buy this tablet soon.
Also, has any of the Tf700 tablet developers been asked to help develop for this tablet? (Just an Idea)
This is not a bashing on any developers who are making this Rom. Especially with SDBags. I have used his CROMI Roms on the TF300t all the time and they are AWESOME!!! I was just curious why the tablet hasn't gotten much attention in the ROMs section from hearing all sorts of good things from this tablet
Click to expand...
Click to collapse
Not many devs bought the device, we only have cm11 source available, I don't have time to make loads of roms from source, although I might have a surprise for you soon.
It's about time other people started learning how to build from source don't you think? How about you give it a go?
sbdags said:
Not many devs bought the device, we only have cm11 source available, I don't have time to make loads of roms from source, although I might have a surprise for you soon.
It's about time other people started learning how to build from source don't you think? How about you give it a go?
Click to expand...
Click to collapse
So you would teaching? [emoji56]
What do you want to know?
sbdags said:
Not many devs bought the device, we only have cm11 source available, I don't have time to make loads of roms from source, although I might have a surprise for you soon.
It's about time other people started learning how to build from source don't you think? How about you give it a go?
Click to expand...
Click to collapse
I totally understand where you are going at. You are a great developer and I am not asking specifically you, just mainly other developers that haven't shown their awesome work for this tablet. And, do you know anywhere good to get a tutorial how to build a rom for this device?
Is building a rom for this device much harder than building a rom for another device, like the tf300t? Does the Tegra 4 chip really hard to work with when creating the ROMS for this tablet? Is there a way I can test the rom onto an emulator build of the tf701 on the computer so then I wont risk my tablet being bricked due to my ignorance? sorry for all the questions.
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.
... 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..
You're a power user. Can the Sony Xperia X keep up? Rate this thread to express how "healthy" the development scene is for the Sony Xperia X. A higher rating indicates available root methods, kernels, and custom ROMs.
Then, drop a comment if you have anything to add!
really bad comparing to other devices
I don't agree. We got official Paranoid omni and lineageOs, some stock custom rom with mods and some very talented dev into open Xperia device community. This phone has the lastest OS given by Google and enhanced by Sony (aosp source availaable even for 7.1.1).
We will have Android 8 and, with it the new update system... That means more custom rom possibility.
Gazatus said:
I don't agree. We got official Paranoid omni and lineageOs, some stock custom rom with mods and some very talented dev into open Xperia device community. This phone has the lastest OS given by Google and enhanced by Sony (aosp source availaable even for 7.1.1).
We will have Android 8 and, with it the new update system... That means more custom rom possibility.
Click to expand...
Click to collapse
lineageos? is there any?
coconutxyz said:
lineageos? is there any?
Click to expand...
Click to collapse
LINEAGE ?????
Where is?
No official Lineage. I hope, the official SailfishOS port will arrive soon.
And when this happens, the X will rise.
Dev community pretty bad as of right now... There's a lot of hope but still years behind dev community behind motorola/oneplus/etc
mase76 said:
No official Lineage. I hope, the official SailfishOS port will arrive soon.
And when this happens, the X will rise.
Click to expand...
Click to collapse
SailfishOS is an absolute deal breaker for me, as you will have to pay for SailfishOS for the Xperia X.
I don't see a reason why I should pay for a OS, which still lacks of features and probably will be released anyway when the xperia x is completly death.
Did you ever try SFOS? The usage is much cooler than
Android. And there will be an runtime env for Android apps.
I don't have a problem to pay for good things. But nobody
forces you to buy an Xperia X or pay for an alternative OS.
And you know, that an Android with Google services isn't
as free as you think?
Ok, it is getting offtopic.
If we'll could talk with Xiaomi Redmi Note 3 dev community, maybe we have other expectations with the development for this and Xperia X Compact device(s).
BTW, I been wanted show you that: https://forum.xda-developers.com/redmi-note-3/development/rom-aosp-oreo-t3664605
Regards.
Very bad compared to my 3 years old Asus Zenfone
This even getting Oreo
https://forum.xda-developers.com/zenfone-5/development/rom-aosp-oreo-tank0412-t3663733
Their Snapdragon 650 is a good SoC for Development, more, searching fix some errors that Sony let...
The problem is our own Dev here, is very low...
IDK why.
We'll should to port some things from Xiaomi's Phones (Xiaomi Redmi Note 3 Snapdragon and Xiaomi Mi Max), or, fuse our Dev with them Dev for making "bigger" to Snapdragon 650 SoC, at least.
SahilCrazy said:
SailfishOS is an absolute deal breaker for me, as you will have to pay for SailfishOS for the Xperia X.
I don't see a reason why I should pay for a OS, which still lacks of features and probably will be released anyway when the xperia x is completly death.
Click to expand...
Click to collapse
u know that jolla give you the option to compile sailfish x for yourself right? And you know that they need to make money because they paid sony for licenses etc. and have taxes and coworker etc.? It's not like that jolla is a one-man show in a cellar like some others here like to think or are by themself
Guys please don't say our dev community strength sucks that's just unfair and of poor taste. WHY? Because.
Sony Xperia X wasn't much of a hit phone anyway it was expensive and was reviewed as a poor excuse for a flagship phone when it was released so nobody even bothered buy one there were better options back then and this phone did not deserve any attention in fact I only bought this phone because it was so damn cheap when I bought it last year. (from a 2nd hand seller for 150$)
I won't expect lots of devs and variety on custom ROMs for this phone, but I'm happy and grateful that we still got great devs here even if there's only a few.
cyanides13 said:
Guys please don't say our dev community strength sucks that's just unfair and of poor taste. WHY? Because.
Sony Xperia X wasn't much of a hit phone anyway it was expensive and was reviewed as a poor excuse for a flagship phone when it was released so nobody even bothered buy one there were better options back then and this phone did not deserve any attention in fact I only bought this phone because it was so damn cheap when I bought it last year. (from a 2nd hand seller for 150$)
I won't expect lots of devs and variety on custom ROMs for this phone, but I'm happy and grateful that we still got great devs here even if there's only a few.
Click to expand...
Click to collapse
Now, is the "most seller" together to the Xiaomi A1.
With this, maybe we could see something for make to develop even more for this SoC.
Community development is bad, but not the worst. Unfortunately, "Bootloader unlock allowed" is "No" on my phone so I can't use anything community developed/maintained regardless.
IMO it's alright. We're still under cover of Sony's AOSP and various official projects (Omni and PA), and outside of that there are Unofficial LOS and Treble by Chippa_ahttps://forum.xda-developers.com/member.php?u=6994234 and Sjll respectively. Some of those ROMs are usable as daily driver.
Props to any and all developers who have been keeping this phone alive.