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 ?

Hallo peeps!

Hi to everyone outhere. Just pulled out my 4x of the shipping box, thought i'd do a little introduction (hoping it won't disappoint anyone)
My name is Rudjgaard, 27 years old Italian...compiler (developer sounds too much for my level )
I come from the sony xperia's where i worked on miui v2 & 4 and currently maintain the ParanoidAndroid thread for sony mdpi line.
I'm unlocking bl now, then will dump system rom to give it a look (though i don't expect major differences) and hopefully by the end of the week will start working for the community.
I like working in tandem with other devs, i also offer my computer for remote compiling/programming if anyone needs decent specs.
Feel free to pm me anytime for anything regarding possible projects to personal help i'll do my best to help out.
I believe this should suffice for now, looking forward to this new part of community,
Best regards,
Rudj

hi! any chance for ParanoidAndroid from sources?

reas0n said:
hi! any chance for ParanoidAndroid from sources?
Click to expand...
Click to collapse
Well....it's my daily and only rom, i bought new phone when halo source was released so.....who knows....maybe....:angel:

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

Why is it so difficult to develop on this phone?

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

[ROM] [Work in Progress] [Mantis] LineageOS 14.1 for Fire TV Stick 4K

Hi community!
There is a WIP (Work in Progress) ROM being mainly developed by @Rortiz2 and @diegocr: https://github.com/LOSMantis
Current ROM Status:
- Not Stable
Not Working:
- Sound
- OMX
- Maybe more...
Developers out there that would like to join development are welcome!...
Notice: This is a WIP ROM. It needs to be compile from the source (build steps could be adapted from the Nexus Player https://wiki.lineageos.org/devices/fugu/build) if someone wants to try it out. Ready to flash builds would maybe be available when the ROM is more stable. Please do not ask for ETA, it is being developed in the spare time of the developers!

michael.santos said:
Hi community!
Anyone already seen this project on github: https://github.com/LOSMantis ?
It is a shame that this project are not being discussed here on XDA so more devs could help on this project...
Hope this post will "awake" some devs (maybe @Pretoriano80?) for this project...
This can be the project that will free our Fire TV Stick 4k from the crappy FireOS!
Click to expand...
Click to collapse
'I believe @diegocr and @Rotiz2 were working on it some and couldn't get the sound to work. Not sure if actively though...

This can be the project that will free our Fire TV Stick 4k from the crappy FireOS!
Click to expand...
Click to collapse
FireOS is very well maintained, even the oldest fireTVs/sticks getting still proper updates...

Sus_i said:
FireOS is very well maintained, even the oldest fireTVs/sticks getting still proper updates...
Click to expand...
Click to collapse
Yes, but full of bloatware, with some blocking mechanisms or black listed apps, no Google Play Store...
We are not allowed to change the home app easily, to use the standard Android settings without Amazon home app, not install already purchased apps on the Google Play Store and so on...

With root you can disable remove the "bloatware", although personally i dont think there is much i dont use. The fireOS TV is fairly smooth and easy to navigate. The android TV version is worse (IMO, I have a NVidea). You can disable the NIMH app, although i have yet to find any app it is blocking. The play store for androidTV is horrible. LauncherX is fairly easy to install. As with tank and sloan, i would expect issues with roms.

...

Rortiz2 said:
Can you and other people (that did this aswell) stop creating threads like this?
We're working on mantis yes but this takes its time...
For now all is working except OMX and Audio so it's not worth to release anything.
We will create the ROM thread when it's enough usable.
Just wait...
Regards.
Click to expand...
Click to collapse
Hi Rortiz2,
Why are you so mad about this thread? We did not ask for a working ROM or any release dates and we appreciate all your time and dedication to the project...
As I wrote in the subject, this is a WIP (Work in Progress) ROM... Have seen so many threads like this in other forums here on XDA where the ROM only boots but nothing works...
I have created this thread to allow other devs to join the project (if nobody talks about it, than nobody knows that a project already exists and can not help).
But if you would like to do this project alone, just tell me an I will delete this thread...
Best regards,
Michael

...

I got really excited when I saw this thread. I cannot wait for stock Android for the Firestick 4K. I will 100% donate to the dev's who get this working!!

Rortiz2 said:
It's ok, leave the thread here. If somebody wants to help there's no problem.
Click to expand...
Click to collapse
Just throwing out an idea here but would getting some kind of test build out help? Perhaps getting some catlogs from the community could help find a solution? Again just throwing an idea out.

AngryManMLS said:
Just throwing out an idea here but would getting some kind of test build out help? Perhaps getting some catlogs from the community could help find a solution? Again just throwing an idea out.
Click to expand...
Click to collapse
+1 for a test build, I've got a bricked 4k that boots both the hacked bootloader and TWRP, but whatever image I install has no display...
So I would like to try anything else even if stuff is broken on it (just to see if I can get a display).
thx.

michael.santos said:
Hi community!
Anyone already seen this project on github: https://github.com/LOSMantis ?
It is a shame that this project are not being discussed here on XDA so more devs could help on this project...
Hope this post will "awake" some devs (maybe @Pretoriano80?) for this project...
This can be the project that will free our Fire TV Stick 4k from the crappy FireOS!
Click to expand...
Click to collapse
It's at developer's discretion to discuss or release test builds here and considering that this particular rom still has some major bugs (call them deal breakers if you want), then i personally agree with the devs not releasing it yet.
Also, i didn't tested personally, but probably a custom rom like this may also break some features available on stock rom.
This being said, i'm sure that it will be released as soon as the guys behind it will consider it stable enough.
P. S. BTW, thread title is misleading and probably aldo violates XDA rules.

Pretoriano80 said:
It's at developer's discretion to discuss or release test builds here and considering that this particular rom still has some major bugs (call them deal breakers if you want), then i personally agree with the devs not releasing it yet.
Click to expand...
Click to collapse
I totally understand and respect that. I did bring up having some kind of developer/user test build done just in case that could help further along getting said bugs fixed by getting catlogs that might help narrow down what is causing the issues. But if the devs feel that doing that would only slow things down (or even not help at all) then I respect that decision.
Also, i didn't tested personally, but probably a custom rom like this may also break some features available on stock rom.
Click to expand...
Click to collapse
That's the nature of things when it comes to Lineage OS ROMs (and AOSP in general). Sometimes devs are able to get the ROMs to have nearly all the functionality of the device working... and sometimes not. But I generally prefer Lineage myself due to the overall experience being faster since LOS tends to not have all the bloat that stock ROMs sometimes have - especially Amazon devices which feel so bloated down with garbage I will never use.

Pretoriano80 said:
It's at developer's discretion to discuss or release test builds here and considering that this particular rom still has some major bugs (call them deal breakers if you want), then i personally agree with the devs not releasing it yet.
Also, i didn't tested personally, but probably a custom rom like this may also break some features available on stock rom.
This being said, i'm sure that it will be released as soon as the guys behind it will consider it stable enough.
P. S. BTW, thread title is misleading and probably aldo violates XDA rules.
Click to expand...
Click to collapse
Hi Pretoriano80,
As I already replied to one of the devs, I never asked for a release date or ROM for flashing. The title also is marked as WIP (Work in Progress), that means that the ROM is in development and not ready for use...
I have seen that you already made a great job with the custom kernel. Thanks! Would you also like to help this project as it seems it also can use your kernel? Kernel dev with ROM devs would be the best team!
Thanks again to all devs that work hard for releasing new stuff for the Amazon devices...

How's the progress so far?

Looks like nothing much: https://github.com/LOSMantis/android_vendor_amazon_mantis
Too bad !!

dead project ?

I made a test build (with many warnings). Also I used the kernel from @Pretoriano80.
You can download it here: https://www.androidfilehost.com/?w=files&flid=324510
Please note that I couldn't test this out yet, so be careful of what you do. (Will try it out for myself soon)

Ungeskriptet said:
I made a test build (with many warnings). Also I used the kernel from @Pretoriano80.
You can download it here: https://www.androidfilehost.com/?w=files&flid=324510
Please note that I couldn't test this out yet, so be careful of what you do. (Will try it out for myself soon)
Click to expand...
Click to collapse
it's not worth to test since it's a dead project, it would be more usefull to begin a new project developing LineageOS 16 rom , At least we will be able to use the new Android/Google TV UI.

robin994 said:
it's not worth to test since it's a dead project, it would be more usefull to begin a new project developing LineageOS 16 rom , At least we will be able to use the new Android/Google TV UI.
Click to expand...
Click to collapse
LineageOS 16 won't ever be able to happen for the Mantis version because it doesn't support treble, the most it could do is LOS 14.1 since it's a legacy device.