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] I9305 LTE - Future of the userbuilt CyanogenMod / my I9305

Hi there,
after extending my Vodafone subscription for another 2 years they sent me a SGS3 I9305... Over the last years i was using SGS and SGS II with CM... After googling half a day and reading the other half of the day i got stuck - not knowing what do know with the I9305 because I am addicted to Cyanogenmod since I first bought the SGS... With the SGS II it became even better and now I don´t know if I should laugh or cry holding a flagship smartphone in my hands which is not ( officialy ) supported by the Firmware / Rom I love. This Forum looks like the place to ask a few of my questions related to the future of my I9305, Cyanogenmod and a few other things... so here we go:
-Why is the cyanogenmod team not developing for the I9305?
-Will they take over the work that is put into the "userbuilt" Version and add official support for the I9305?
-Will the "userbuilt" Version stay something like a "sidekick" or can we expect nightlies / fixes on a regular basis?
-Will the "userbuilt" Version stay on top of new releases / versions of Android?
-Does Codeworkx now "officially" support the "userbuilt" Version or was he just "snooping around" and giving some advice?
-Is the I9305 already "born dead" and should I sell it and wait for another Samsung device that´ll be supported again?
I really don´t know what to do... The Vodafone ( Germany ) Stock Rom is pain in the a** and flashing other "experimentals Roms" is no good for me either. I love and admire what the Cyanogenmod developers are doing and how much "brain matter" and energy they put into their project, but from my ( quite selfish ) point of view it feels wrong to give up on the users which were given a f****n I9305 by their Mobile-Providers and not the I9300...
Please enlighten me and if there is hope to use the I9305 like it was possible with SGS and SGS II in combination with CM please give me a hint how to achieve that. I´d really appreciate some CYANO-LOVE for my "not so smart" smartphone...
Many thanks in advance and greetings from good old germany - Clever&Smart

I think the closest thing you're going to get is liquids rom which is very close to cyanogen if not better. At the moment it's not stable enough for me but I'm sure after a few updates it will be worth using.
For now I've customised ripper rom to get the pure look. And it works flawlessly. And let's face it you can't beat having a Sammy base so that the camera works as it was intended to!
But be patient things change pretty quick on here and maybe codeworks will change his mind
Sent from my GT-I9305 using xda premium

Amplified (the maintainer of Liquid Smooth I9305) has a say in official I9305 CM support but I don't know why you wouldn't just go for Liquid Smooth, we have a dedicated Dev that happily takes logcats, fixes problems, will be pushing out updates and most of all we know he will be sticking around unlike Codeworkx. Yes he has done SOO much but unfortunately he doesn't have our device and refuses to support Samsung for good reasons too so he can only do so much. Do as much as you can to help around and if we all do our bit we will see a flourishing I9305 forum.
Sent from my GT-I9305 using xda premium

Magik_Breezy said:
Amplified (the maintainer of Liquid Smooth I9305) has a say in official I9305 CM support but I don't know why you wouldn't just go for Liquid Smooth, we have a dedicated Dev that happily takes logcats, fixes problems, will be pushing out updates and most of all we know he will be sticking around unlike Codeworkx. Yes he has done SOO much but unfortunately he doesn't have our device and refuses to support Samsung for good reasons too so he can only do so much. Do as much as you can to help around and if we all do our bit we will see a flourishing I9305 forum.
Sent from my GT-I9305 using xda premium
Click to expand...
Click to collapse
Am I understanding your answer right? Is the Liquid Smooth ROM a ROM from the CyanogenMod Development Tree ?

Its they're own based of some from cm and aosp
It's pretty close though!
http://forum.xda-developers.com/showthread.php?p=38033836
I too was sadden by the lack developmental roms on here but I love this device so oh well
Sent from my GT-I9305 using xda premium

Here you go mate
http://forum.xda-developers.com/showthread.php?p=38243046
[ROM][GT-I9305][JB][4.2.2] CyanogenMod 10.1 unofficial builds
Sent from my GT-I9305 using xda app-developers app

djembey said:
Here you go mate
http://forum.xda-developers.com/showthread.php?p=38243046
[ROM][GT-I9305][JB][4.2.2] CyanogenMod 10.1 unofficial builds
Sent from my GT-I9305 using xda app-developers app
Click to expand...
Click to collapse
That is still the exact same CM, now you just dont have to screen through 46 pages to know what is going on
Sent from my GT-I9305 using xda premium

Magik_Breezy said:
That is still the exact same CM, now you just dont have to screen through 46 pages to know what is going on
Sent from my GT-I9305 using xda premium
Click to expand...
Click to collapse
But - correct me if I am wrong - I think it´s still "not maintained" and codeworkx is flaming everybody who is not a development pro because he is mad... and under these circumstances it doesn´t seem to be very wise to install it right now - right ?

cleverandsmart said:
But - correct me if I am wrong - I think it´s still "not maintained" and codeworkx is flaming everybody who is not a development pro because he is mad... and under these circumstances it doesn´t seem to be very wise to install it right now - right ?
Click to expand...
Click to collapse
You have 2 options.
1. Install it and try it.. It's not maintained yet and it's Unofficial build as Codeworkx don't own an i9305.....
2. Wait until CM project have full support for i9305..... You can wait forever. ....
It's completely up to you mate
Sent from my GT-I9305 using xda app-developers app

cleverandsmart said:
-Why is the cyanogenmod team not developing for the I9305?
-Will they take over the work that is put into the "userbuilt" Version and add official support for the I9305?
-Will the "userbuilt" Version stay something like a "sidekick" or can we expect nightlies / fixes on a regular basis?
-Will the "userbuilt" Version stay on top of new releases / versions of Android?
-Does Codeworkx now "officially" support the "userbuilt" Version or was he just "snooping around" and giving some advice?
-Is the I9305 already "born dead" and should I sell it and wait for another Samsung device that´ll be supported again?
Click to expand...
Click to collapse
To answer your questions in order,
We don't have an official maintainer because
i: hardly anyone owns this device;
ii: of the few people who do own this device, most are not able to maintain it, and none have previously maintained devices for CM;
iii: codeworkx is not willing to maintain it because, in very short, Samsung are very nearly the worst OEM when it comes to supporting third-party development; besides which, he doesn't own the device, which makes it very difficult for him to work on the port.
If a maintainer appears, we'll get official nightlies. I wouldn't hold your breath.
As above, if a maintainer appears, he or she will likely take over the existing device tree and the unofficial version will just become irrelevant.
If someone makes new builds, yes. There are a few of us who can do that until something major breaks, since builds really only require time rather than knowledge.
Codeworkx does not, and has never, supported this device or offered to maintain it. He just took pity on us because no-one here has enough porting experience to do it properly otherwise. That said, he has fixed a lot of bugs, and at this point in time the build is pretty much comparable in stability to the t0lte builds.
Since you care about AOSP ROMs - sell it, get a Nexus 4. If for some reason you don't want that, just don't get a Samsung device - seriously. Almost any manufacturer save HTC would be better; Sony in particular seem to be flavour of the month. Samsung are really, really bad in this one regard (i.e., releasing proper sources). There's still a lot that's not yet released, and what's there took far too long to get.
With regard to the LiquidSmooth ROM, it's hard to judge exactly what Amplified can do. He hasn't updated the LiquidSmooth device tree except with the changes codeworkx has made. He also implied a while back that C/C++ aren't his preferred languages, in which case I would expect hardware support to improve slowly at best. I don't mean any of that as criticism of Amplified, of course, I just don't want to tell you that all will be well without knowing beyond doubt whether Amplified can fix driver issues down the line.
Having said that, the unofficial CM build really is entirely usable, and I expect LiquidSmooth is much the same. I daresay the former will be kept up-to-date by the community until Android 5 appears, at which point porting will probably require a skilled developer again. The progress of the latter is up to Amplified.

No mention of KitKat yet?

In theory based on the platitudes fed to and accepted by the media, surprised no, "Is it here yet?" posts
On a more "cereal" note, if the point it works with lower resources is true, it would be a reason for me to update and start from scratch.
After I peak out of my from a bunker 20 fathoms below sea level.... I will let others test first!

rushless said:
In theory based on the platitudes fed to and accepted by the media, surprised no, "Is it here yet?" posts
On a more "cereal" note, if the point it works with lower resources is true, it would be a reason for me to update and start from scratch.
After I peak out of my from a bunker 20 fathoms below sea level.... I will let others test first!
Click to expand...
Click to collapse
Check the OP of the CARBON thread.
Unless a serious bug is identified, these early November builds will be the final updates for the 4.3 branch, as the Carbon Team has started working on 4.4
Click to expand...
Click to collapse
Be patient, it's coming!

Indeed, yes. It's true that KitKat will run on lower specification devices, however, that doesn't mean EOL devices will be resurrected. The lower specification "thing" is more of OEMs to consider, so they can push budget devices with the latest version of Android, KitKat; instead of still producing Gingerbread devices.
Of course, away from that subject. It should effectively mean, our devices currently on ICS/4.0.x+ should see an increase in performance, including our Nooks.
So when will we receive 4.4 KitKat on our Nooks? The general rule is never to ask for ETAs, but CyanogenMod has provided for us. CM10.1 is complete and finalised. They're trying to complete work on CM10.2, instead of jettisoning all of the current developers efforts. So they/CyanogenMod will be working on CM10.2 for some time, until they can finish it. That doesn't mean to say CM11 will come after CM10.2. No, you can expect CM11 nightly builds by the end of this month. And yes, it'll be called CM11, not CM10.3.
CM11 release date source.

Maybe someone with more knowledge (like @verygreen?) can chime in here, but I thought the fact that our Nooks (HD & HD+) are OMAP4-based means that we won't have the necessary drivers, since TI bailed out of the market. At least, that's what people have surmised, given that Google isn't releasing KitKat for the Gnex, which is OMAP 4430.
I hope I'm wrong, as the better low memory performance of 4.4 would be great to see on the HD+. Even better, it might even resurrect my old Nook Color! XD
Sent from my Nexus 4 using XDA Premium 4 mobile app

psyberian said:
Maybe someone with more knowledge (like @verygreen?) can chime in here, but I thought the fact that our Nooks (HD & HD+) are OMAP4-based means that we won't have the necessary drivers, since TI bailed out of the market. At least, that's what people have surmised, given that Google isn't releasing KitKat for the Gnex, which is OMAP 4430.
I hope I'm wrong, as the better low memory performance of 4.4 would be great to see on the HD+. Even better, it might even resurrect my old Nook Color! XD
Sent from my Nexus 4 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
google may not have provided a rom for gnex but they have one in the xda forums already...since the nook hd+ is a supported cyanogenmod device I expect it will see CM11...probably omnirom since they are showing up in alot of places....and carbon.

famewolf said:
google may not have provided a rom for gnex but they have one in the xda forums already...since the nook hd+ is a supported cyanogenmod device I expect it will see CM11...probably omnirom since they are showing up in alot of places....and carbon.
Click to expand...
Click to collapse
im so excited for 4.4 on our nooks!

cm13?

Dear Fellufz,
CM13 Nightlys are officially available. Any chance to bring this to work for this little sweet device? As I can see, there is a Custom rom based on CM12.1 .... Maybe we could build something onto it to make cm13 work? ( at least make it a WiP, nobody needs bluetooth)
Any thought's on this?`

I definitely hope so and I think developers will be getting onboard for this. It is still relatively new to the market but especially at this price point and the black Friday deals, this is flying off the shelves. Its just such a nice little tablet to play and experiment with roms and see how we can push it for great general use. Looking forward to trying various roms on this thing. CM13 can't come soon enough for this.

I'd imagine alot of people will be looking go get it as its only £35 in the UK I don't know what the us price is
Sent from my Amazon Fire 2015

Hi,
flex420 said:
Dear Fellufz,
CM13 Nightlys are officially available. Any chance to bring this to work for this little sweet device? As I can see, there is a Custom rom based on CM12.1 .... Maybe we could build something onto it to make cm13 work? ( at least make it a WiP, nobody needs bluetooth)
Any thought's on this?`
Click to expand...
Click to collapse
Do these CM13 Nightlys apply to the NEW Amazon tablet?
Fire, 17,7 cm (7 Zoll) Display, WLAN, 8 GB ?

titanic1955 said:
Hi,
Do these CM13 Nightlys apply to the NEW Amazon tablet?
Fire, 17,7 cm (7 Zoll) Display, WLAN, 8 GB ?
Click to expand...
Click to collapse
No they do NOT. There are only like 4 devices now that get the official nighties all being flagship phones. I doubt this device will ever have official support. It will probably get CM 13...eventually. I doubt that anyone will build it for a while though. There are way too many changes to the SRC as more and more code is pushed to the GIT. When CM official full releases come about, then is the time to expect CM 13.

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