Database Develop

[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] 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.

Cyanogenmod for R1?

Hey Everyone,
I'm fairly new to the Android community. I got an R1 and have since rooted it and de-bloated it. But I was wondering what the state of Cyanogenmod is. I've heard they've stopped development on it. Is there any chance they (or someone) will add support for the Blu R1 HD?
I'm interested in getting a full AOSP experience without the closed source google services kit software.
-Jeff

Don't hold me to this, but I personally believe CM13 support will not be too difficult. It'll be later versions of Android that will pose a problem.
Also, CM13 for the R1 HD is being worked on. It's just a matter of time.

ss2man44 said:
Don't hold me to this, but I personally believe CM13 support will not be too difficult. It'll be later versions of Android that will pose a problem.
Also, CM13 for the R1 HD is being worked on. It's just a matter of time.
Click to expand...
Click to collapse
Oh, it is? Thats great. I have plenty of patience

I'm in the same exact boat, have rooted/de-bloated and installed trebuchet and other features, but really would like to see CM support.
jeffburg said:
Hey Everyone,
I'm fairly new to the Android community. I got an R1 and have since rooted it and de-bloated it. But I was wondering what the state of Cyanogenmod is. I've heard they've stopped development on it. Is there any chance they (or someone) will add support for the Blu R1 HD?
I'm interested in getting a full AOSP experience without the closed source google services kit software.
-Jeff
Click to expand...
Click to collapse

ss2man44 said:
Don't hold me to this, but I personally believe CM13 support will not be too difficult. It'll be later versions of Android that will pose a problem.
Also, CM13 for the R1 HD is being worked on. It's just a matter of time.
Click to expand...
Click to collapse
I don't understand too much about android ROM development, but what would prevent CM14 development/future versions from being developed?

contacted Blu and they told me that they are looking forward to working on updating as many devices as they can to the new platform as soon as possible!......righhtttt!!!
Once the dev. on the kernel is in line for a cm13 port , cm14 (which is already being worked on) hopefully might be a possibility.

Fullmetal99012 said:
I don't understand too much about android ROM development, but what would prevent CM14 development/future versions from being developed?
Click to expand...
Click to collapse
Me either, but I think it would be the drivers. I would suspect with CM13 they can use it's current drivers but with anything Android 7.0 they would need new drivers.
Blu has updated a few devices haven't they? They have to develop the drivers and then run it through the carriers approval I believe? I'm sure they are looking at how much money they expect to make from the R1 HD in 4-6 months. Some of this might depend on their plans of a new phone they plan to release. R1 HD is a big seller.... but what about in 6 months?

A device tree is very likely being compiled for this device now that the kernel source has been released. A CM 13 build I'd imagine is also in the works with other custom roms likely to follow. I would just sit back and keep your eye out. As soon as customs ROMs are released you should easily find them in R1 HD Forums on XDA. I wouldnt hold your breath for anything beyond android 6.0 on this device tho! Marshmallow ROMs will be more then sufficient for these devices and most devs really don't like to hear when this or that will be updated or released.

Jstame said:
I wouldnt hold your breath for anything beyond android 6.0 on this device tho! Marshmallow ROMs will be more then sufficient for these devices and most devs really don't like to hear when this or that will be updated or released.
Click to expand...
Click to collapse
No, I'm pretty sure once devs can build AOSP 6.0 for this device, it'll get 7.0, even if BLU abandons it. I mean, you do realize that you're on a website famous for, among other things, providing unofficial updates to unsupported devices, right?

cmason37 said:
No, I'm pretty sure once devs can build AOSP 6.0 for this device, it'll get 7.0, even if BLU abandons it. I mean, you do realize that you're on a website famous for, among other things, providing unofficial updates to unsupported devices, right?
Click to expand...
Click to collapse
Yeah I know exactly where I am bro. The fact that its such a low cost device and the unlikely hood of Blu updating the kernel source to 7.0 makes it very very unlikely there will ever be any kind of 7.0 update on these phones. Plenty of unofficial updates of ROMs are released but not many are above the "official" releases like going from 5.0 to 6.0 or 6.0 to 7.0. Were still waiting to see how Devs react to the R1 HD now since its not a big name mainstream device. So like I was saying if we don't see Blu update to 7.0 which is doubtful, we prob won't see any kind of Nuaget. Not saying its impossible without a Blu update just wouldn't hold my breath waiting on a Dev to take on that task on this particular device....

Jstame said:
Yeah I know exactly where I am bro. The fact that its such a low cost device and the unlikely hood of Blu updating the kernel source to 7.0 makes it very very unlikely there will ever be any kind of 7.0 update on these phones. Plenty of unofficial updates of ROMs are released but not many are above the "official" releases like going from 5.0 to 6.0 or 6.0 to 7.0. Were still waiting to see how Devs react to the R1 HD now since its not a big name mainstream device. So like I was saying if we don't see Blu update to 7.0 which is doubtful, we prob won't see any kind of Nuaget. Not saying its impossible without a Blu update just wouldn't hold my breath waiting on a Dev to take on that task on this particular device....
Click to expand...
Click to collapse
"Not a big name mainstream device"
Totally man. The number 1 selling phone on Amazon isn't a "big name, mainstream device." If anything this phone is proving how Android development is dwindling.

There was a article that said Blu would release Android 7.0 for the R1 HD. I don't know how reliable or legitimate it is.

dba415 said:
There was a article that said Blu would release Android 7.0 for the R1 HD. I don't know how reliable or legitimate it is.
Click to expand...
Click to collapse
They probably did say it, BLU has a history of promising upgrades, they rarely deliver. I don't know if the blame is theirs or their Chinese partners, not delivering. But even at that if BLU was smart they would hire a team of developers to actually develop roms instead of just simple branding tweaks on the manufacturer supplied firmware. BLU needs to tweak their sales routine, currently they sell flashy looking phones on the cheap, but if they would change their focus to selling entry to mid level phones with better support, they could really make a name for themselves.

Is there ever going to be an official Cyanogen ROM?

Just saying, the Z1 did have one, what's the delay on the Z2 and Z2pro?

I think is not get official support. I don't know why, because this phone have awesome good spec.

Yeah I honestly expected this phone to become a scene favorite and instead it barely gets any support

That's my only criticism about this phone, that it has no official CyanogenMod support. All my previous phones (Moto G, OnePlus One and LG G4) came with official CM support, but the ZUK Z2 doesn't not. I thought it would be okay by relying on community builds instead, but updates are few and far between with these builds. There seems to be some development for the Z2 ongoing over at the Lenovo Mobile forums, but it is all in Chinese and Google Translate does not do much to make it more legible.

P650SE said:
That's my only criticism about this phone, that it has no official CyanogenMod support. All my previous phones (Moto G, OnePlus One and LG G4) came with official CM support, but the ZUK Z2 doesn't not. I thought it would be okay by relying on community builds instead, but updates are few and far between with these builds. There seems to be some development for the Z2 ongoing over at the Lenovo Mobile forums, but it is all in Chinese and Google Translate does not do much to make it more legible.
Click to expand...
Click to collapse
I will start working on CM14 next week when my phone arrives, but pls don't except to much.

NeoChontrix said:
I will start working on CM14 next week when my phone arrives, but pls don't except to much.
Click to expand...
Click to collapse
Yeah, but this is unofficial??

Araa01 said:
Yeah, but this is unofficial??
Click to expand...
Click to collapse
I should be able to get it official when it is running without bugs.

Nice... I fingers crossed. Add on Xda when you compile.

Araa01 said:
Nice... I fingers crossed. Add on Xda when you compile.
Click to expand...
Click to collapse
Looks like someone at zukfans compiled cm14.1, idk if everything is working there but it may be worth a look.
http://zukfans.eu/community/threads/cm-14-1-android-7-1-1.1976/

NeoChontrix said:
Looks like someone at zukfans compiled cm14.1, idk if everything is working there but it may be worth a look.
http://zukfans.eu/community/threads/cm-14-1-android-7-1-1.1976/
Click to expand...
Click to collapse
No look on others developers. Your system work's better! I trust that. ?

P650SE said:
That's my only criticism about this phone, that it has no official CyanogenMod support. All my previous phones (Moto G, OnePlus One and LG G4) came with official CM support, but the ZUK Z2 doesn't not. I thought it would be okay by relying on community builds instead, but updates are few and far between with these builds. There seems to be some development for the Z2 ongoing over at the Lenovo Mobile forums, but it is all in Chinese and Google Translate does not do much to make it more legible.
Click to expand...
Click to collapse
Not just CM but I don't see it gets any official support from any other ROMs
Its really weird, it has a 820 and pretty good specs, I don't get why its so difficult to get a good reliable aosp ROM for it

First to answer your original question. Because zuk had a contract with CM so z1 had Cyanogen OS and thus the open source CyanogenMod was a bonus so to say. Also we do have official CM in the face of MoKee. With some neat added features aswell. Just hoping they continue supporting the device with Nougat aswell
P.S. I have read in some post that MoKee has lots of chinese bloatware which aside from the Pinyin input seems to be incorrect.

baluuu said:
First to answer your original question. Because zuk had a contract with CM so z1 had Cyanogen OS and thus the open source CyanogenMod was a bonus so to say. Also we do have official CM in the face of MoKee. With some neat added features aswell. Just hoping they continue supporting the device with Nougat aswell
P.S. I have read in some post that MoKee has lots of chinese bloatware which aside from the Pinyin input seems to be incorrect.
Click to expand...
Click to collapse
Zui.is also based at least to some. degree on Cyanogen mod. E.g. they are using the cm theme engine, they have only hidden the launch icon. Idk what else is from cm since I removed Zui after one hour.

The incredible lack of support in the form of Roms and accessories are stopping me from buy this phone. The specs and 4G band support are perfect for me, but i dont what to stuck with a phone who even Zuk does not care..

Why are there so few Custom ROMs for this device?

Hey there,
I've been watching this forum for a while, but I still can't figure out why this device does not get more attention from ROM developers. AFAIK, there are only like one or two semi-active non-stable ROMs for this device. One of my previous phones was a Sony Z1 Compact, which was released almost 5 years ago, and there still is more activity in the Z1 ROM forum than here. Additionally, this device shipped with Oreo and therefore should support Project Treble, which should (theoretically) make it easier to create Custom ROMS. I'm not here to criticize, just genuinely curious, because I know for a fact that there are quite a few active developers who worked their butt off to make it able to backup the DRM keys on this device (thanks a lot btw!).

The amount of persons buying compact cellphone has reduced drastically over the years.
Sent from my Phh-Treble with GApps using Tapatalk

On the other hand, I don't feel a need for custom ROMs at all. Manually debloating the stock Sony ROM makes for a satisfactory, bug-free experience.

SirSoviet said:
On the other hand, I don't feel a need for custom ROMs at all. Manually debloating the stock Sony ROM makes for a satisfactory, bug-free experience.
Click to expand...
Click to collapse
This.
Of course there are many roms for old devices, but keep in mind this aren't Lollipop days anymore.
To me, starting from 7 Nougat, Android is a complete auto sufficient OS

I agree that now Android has what a standard user needs. However, a custom ROM is still necessary if one wants to get rid of Google Apps and take full control of the system and the phone.
So I hope at least Lineage OS will be developed for our xz1c.
Sent from my XZ1 Compact using XDA Labs

Here I am still waiting for a CarbonROM for XZ1 Compact.

SonyVLT25ISonyVLT25I said:
Here I am still waiting for a CarbonROM for XZ1 Compact.
Click to expand...
Click to collapse
You mean like this one?
https://forum.xda-developers.com/xperia-xz1-compact/development/8-1-x-carbonrom-cr-6-1-t3817402
Sure, it's unofficial and no longer updated,but it's still a build...

tonsofquestions said:
You mean like this one?
https://forum.xda-developers.com/xperia-xz1-compact/development/8-1-x-carbonrom-cr-6-1-t3817402
Sure, it's unofficial and no longer updated,but it's still a build...
Click to expand...
Click to collapse
Yeah, I saw this one, but as you have said it is: 1. unofficial. 2. No longer updated. Look like a strong points not to even try it, considering your phone being a daily driver, not just a test subject.

It's too soon for a smartphone that has only one year and some months in the market, and the price still around 300euros.
Wait some time and i'll be sure that some people start to make more noise about this model. Or another option, to start to learn Java or other tech to help the community!!
Check for example the Z5 compact (released on October 2015), has lot of different roms and still is a good deal (i have it running with LineageOS 14.1 till past Xmas)

Never Sony again for me. The Acro S had great support though. The good old days with proper Xposed. If I only could afford the S10. Got a S5 laying around, but I love the fingerprint scanner on this phone, so no going back to the S5.