Database Develop

[LATEST] Chromecast -Prerooted w/ Android 4.4.2 Google Play & Kodi -PRINSTALLED

[LATEST] Chromecast -Prerooted w/ Android 4.4.2 Google Play & Kodi -PREINSTALLED
yup that's what i'm trying to suggest if you have any advice info plz contribute.
if anyone could sry i didn't look everywhere i figured i would come to the source.
+whats the maximum hdd space and type of file system and HDD used on the chromecast?
+can a slimbean or similar custom firmware be modified to run play services directly from chromecast?
can someone explain the ARM x86 of the chromecast? is that what this is built on?
and how it differs from standard droid or the method in which it can be combined
into a custom android rom such as for a tablet.
if someone comes up with this i would buy baked bored all day xD preloaded with kodi and 5.0+

What are you even talking about? What does "I would buy baked bored all day" mean?

daveid said:
What are you even talking about? What does "I would buy baked bored all day" mean?
Click to expand...
Click to collapse
oh sorry i mean if a manufacturer such as google or a private kickstarter for example created a device utilizing the wireless hdmi dongle but had a full os running (preferably baked or preinstalled on the processor itself) like android slimbean. you could have the drivers and minimum defaults baked into the processor but write all upgrade data and what not to the prerooted system drive.
basically im just saying this could be far better if we unlocked the potential.
i use bluestacks and do something very similar already via a pc but that's just me and it's is a process.
as far as ease of use their could be nothing better than a custom rom for chromecast with android 5.0 rooted and preinstalled. if know one can see that clearly i am in the wrong place.

just a thought i love google but it would be pretty amazing to see chromecast (or similar software) put onto a flash drive than transferred to a smart wifi enabled tv via sd slot or usb. i mean I REALIZE that does not exist. it sure would be cool if it did. woulda saved me $35 bucks and a buggy peace of hardware with many stability issues on older hdmi versions.
edit.... yes it would be a massive overhaul of chromecast and require much more work if is even possible to make compatible large scale. i am very thankful with what i have.. just making an offering (like all my posts) to the internet.

All the information you need is in the [FAQ] and [INDEX] threads. Please review those at the top of this section. You can ask for clarification in the FAQ thread on anything you didn't find.
Thread closed.
Thanks!

Request for other operating systems on Android One

This is a request thread for developers to port non-Android OSes to Android One devices.
Hello there users and devs of Android One!
Here in this thread, I will put forward the rationale for developers to port mobile operating systems that don't have a robot as a logo to our devices.
Android One is well supported by Google and (somewhat shockingly) MediaTek. Source code can be found on Google's official repositories and as a result, the custom ROM development scene is very much alive. The only thing lacking are the ports of other platforms. We have the install base to test ports (I think), we have CM support (this helps with porting some systems such as FirefoxOS and Ubuntu Touch) and we surely have devs who can do it (you know who you are and I hope that you're reading this).
As for users, please comment down below for what operating systems y'all would like to see on your phones so that we can grab the attention of those heroes behind the screen! Developers can reply to a request directly or PM me if you want to talk. It would be nice if you coders would respond.
P.S. Thanks for all the ROMs and the entire community is grateful for the works you all did for Android One users around the globe! :good:

buy a nexus device and u will have that OS

Android One devices are like cheap nexus devices
The reason many buy Android One phones is to get the vanilla experience for cheap. Some buy it because it's a Google device, therefore, easy to tinker with. Also Nexus devices may not be found easily at retail shops in some countries. That's why I bought Android One. What this thread is hoping to achieve is to (at least) get discussion started on other OSes in our phones. It's very likely that there are people here who bought Android One because of the Nexus-like experience being more accessible.

Will really appreciate the work to port other OS to android One... Hope someone makes that happen

Yes.Can't wait to see another os

FirefoxOS has already been ported to sprout, by Shahidujjaman Khan Anik. He said that he'll make a thread soon.
https://facebook.com/story.php?stor...129499414:2:0:1451635199:-7540004895718870160

Great!
That's really nice! I wanted to try my hand at porting it myself, but I ran into an issue during the build process. Glad to hear that someone was successful in doing so!
Hopefully this is only the beginning of OS diversity on Android One.
P.S. Best of luck to the developer and I'll start testing on my device soon.
P.P.S. I'm considering making a thread for him, is that allowed and could I hand over management and/or ownership to the dev after creation?

Happy to see Firefox OS on android One. Hope to see more of them too
Btw is hike available on firefox OS by any means?

News.....
I search for ubuntu touch for sprout and found that same dev that compiled firefox os has compiled a version of Ubuntu Touch!
https://www.androidfilehost.com/?w=files&flid=44454
I can't wait to test it.
If someone has test one of this, please give us some feedback

lzimbrea said:
I search for ubuntu touch for sprout and found that same dev that compiled firefox os has compiled a version of Ubuntu Touch!
https://www.androidfilehost.com/?w=files&flid=44454
I can't wait to test it.
If someone has test one of this, please give us some feedback
Click to expand...
Click to collapse
Give that man a medal (and thanks)

hp5942 said:
Give that man a medal (and thanks)
Click to expand...
Click to collapse
Hope to see soon a xda thread with this two roms

BTW what are pros and cons among Firefox OS and ubuntu touch? I never used them and if anyone has flashed them, can they please provide reviews. Thanks

lzimbrea said:
I search for ubuntu touch for sprout and found that same dev that compiled firefox os has compiled a version of Ubuntu Touch!
https://www.androidfilehost.com/?w=files&flid=44454
I can't wait to test it.
If someone has test one of this, please give us some feedback
Click to expand...
Click to collapse
I heard that that build of Ubuntu Touch doesn't boot.
But I hope that he, being as good as he is, will get it running soon!

hp5942 said:
BTW what are pros and cons among Firefox OS and ubuntu touch? I never used them and if anyone has flashed them, can they please provide reviews. Thanks
Click to expand...
Click to collapse
When i will be able to install I will give my feedback, bug list and a quick review.
Only thing that i know for now is that camera doesn't work on firefox os.

lzimbrea said:
When i will be able to install I will give my feedback, bug list and a quick review.
Only thing that i know for now is that camera doesn't work on firefox os.
Click to expand...
Click to collapse
I too will flash Firefox os tomorrow. Someone reported here that Ubuntu touch did not boot, so I'll download that later

quick update
ubuntu touch system.img does not installing.... so I cannot boot it
firefox os boot up and works fine for now,
-camera does not work indeed...
-sometimes random crashes
for me it is not a daily driver for now....

Installed Firefox OS
Bugs
1. Sim 2 does not work
2. Cannot connect to mobile data
3. Camera does not work
As @lzimbrea said, not recommended as daily driver

hp5942 said:
Installed Firefox OS
Bugs
1. Sim 2 does not work
2. Cannot connect to mobile data
3. Camera does not work
As @lzimbrea said, not recommended as daily driver
Click to expand...
Click to collapse
Anyway users have to give it a try! Is first different os for sprout.
Maybe an update will fix some bugs and make it a daily driver
Personally I wait for ubuntu touch build.... Firefox os is a bit immature for now.
Congratulations to dev for his efforts!

What about windows ?Did anybody port it?

Cannot compute
Windows mainly runs on the x86 architecture, while most Android devices like ours run on the ARM architecture. Mainstream Windows will not run and Windows 10 Mobile is closed-source; what this means is that the code is inaccessible for anyone wanting to port it. Unless Satya Nadella sees fit to open up Windows source code, this won't happen.

[BRAINSTORM] What if you had a high powered Mini, AOSP and a dev kit...

For all the developers on this board, what if you had...
a higher powered Mini
AOSP, let's say Marshmallow or better
all the dev tools you'd need to get to work
...what would you, could you dream to develop this computer to do?
TV box? Gaming console? Android PC? Smart home device?
Please share with us your brainstorm ideas on this. Have fun with it and don't think about what's already out on the market... think out of the box, reach for the stars, and all the other cliches you can think of. Please share in the comments below.
Thanks!

For me, I'd love to see a higher powered version of the Mini. It's the right form factor for kiosk deployment. I'm exploring development of a kiosk/presentation system that's Android based, and will probably center its development around a device like the Mini.
Of course, I could see something like the Mini with a more stable version of Remix giving Chromebooks a run for the money in a classroom setting. Use it in the class, unplug it, take it home, plug it into your TV and do your homework. With much, much less overhead and replacement costs than are associated with broken Chromebooks in schools. (No glass to break or hinges to abuse.)

I am not a developer but a power user (business oriented) using a mixture of computers at the office those mac's and linux pc.'s.
Then I have purchased two remix minis for my office to test and see if they could replace desktop computers. As Radon_22 said cleverly, my idea was to achieve "mobile computing!" without carrying heavy laptops by the help of home tv's. So remix mini was the good device, remix os was the brilliant but with a limited memory it couldn't replace the computer.
We business users will like to see more RAM options (4GB min.) to replace pc's.
Please give us more RAM to help the businesses all around the world to simplify IT infrastructure.
Thanks to Jide people those made great idea came true.

I'd be in for a Remix Mini with Shield like internals and horsepower along with either the ability to put apps to the sd card or 64+gb of internal memory or both. With the changes to Android M and especially N, 16gb of internal memory is no longer enough.

As a web devoloper i have everything but a web browser with devtools enabled. If there would be a special developer version of browser (chromium preferably) i will be the most happy Remix Mini user!

Compiling Unofficial CyanogenMod 14.1 for Nexus 6

Hello XDA Community,
I am interested in using the unofficial build of CyanogenMod 14.1 available here, but I would like to learn how to compile on my own from the repository provided by the developer. Unfortunately, I do not know how to go about doing this. Could someone please help me out? I have looked at the CyanogenMod Wiki entry for how to compile CyanogenMod for the Nexus 6, but the information is out of date according to what I was told in a post I made on Stack Exchange's Android Q&A site. The only thing that I understand about the build process is that I need to use Linux, so I have set up a virtual machine in VMware running the latest version of Ubuntu. Where do I go from here?
Thank you,
David B.

David B. said:
Hello XDA Community,
I am interested in using the unofficial build of CyanogenMod 14.1 available here, but I would like to learn how to compile on my own from the repository provided by the developer. Unfortunately, I do not know how to go about doing this. Could someone please help me out? I have looked at the CyanogenMod Wiki entry for how to compile CyanogenMod for the Nexus 6, but the information is out of date according to what I was told in a post I made on Stack Exchange's Android Q&A site. The only thing that I understand about the build process is that I need to use Linux, so I have set up a virtual machine in VMware running the latest version of Ubuntu. Where do I go from here?
Thank you,
David B.
Click to expand...
Click to collapse
To be honest You will be better off dual booting. Compiling with a VM normally has more issues then not.
Then I would look at Google developer page.
Also keep in mind that compiling from CM means you get all the bugs they never fixed. You would be better off going with AOSP and then finding the features you want to add and then add them yourself.

zelendel said:
To be honest You will be better off dual booting. Compiling with a VM normally has more issues then not.
Then I would look at Google developer page.
Also keep in mind that compiling from CM means you get all the bugs they never fixed. You would be better off going with AOSP and then finding the features you want to add and then add them yourself.
Click to expand...
Click to collapse
I would love to build my own CyanogenMod based on AOSP and then merge in the features, but I don't even know how to build directly from AOSP.
Honestly, all I really want is stock with all of the additional developer mode features that CyanogenMod has along with root access. I love the ability to use root without extra apps, and wireless ADB is sweet when I'm too lazy to go get my USB cable. And of course, I want to be able to use future versions of Android on my phone even though 7.0.1 is supposed to be the last version for Shamu. Could I somehow merge those aspects together and just pull patches from AOSP, build, and flash?
Also what's wrong with using a VM to compile? I've read that problems occur if you don't have enough RAM allocated to the VM, but I've assigned it 16GB so that should not be a problem. As for attaching my phone to the VM, I am using VMware, which has better support for removable devices than VirtualBox.
I'm sorry if I misunderstand something you said. It's probably obvious, but I know pretty much nothing about what I am doing which means I'm likely to ask lots of questions that seem ridiculous to those that are well-versed in this sort of thing.

David B. said:
I would love to build my own CyanogenMod based on AOSP and then merge in the features, but I don't even know how to build directly from AOSP.
Honestly, all I really want is stock with all of the additional developer mode features that CyanogenMod has along with root access. I love the ability to use root without extra apps, and wireless ADB is sweet when I'm too lazy to go get my USB cable. And of course, I want to be able to use future versions of Android on my phone even though 7.0.1 is supposed to be the last version for Shamu. Could I somehow merge those aspects together and just pull patches from AOSP, build, and flash?
Also what's wrong with using a VM to compile? I've read that problems occur if you don't have enough RAM allocated to the VM, but I've assigned it 16GB so that should not be a problem. As for attaching my phone to the VM, I am using VMware, which has better support for removable devices than VirtualBox.
I'm sorry if I misunderstand something you said. It's probably obvious, but I know pretty much nothing about what I am doing which means I'm likely to ask lots of questions that seem ridiculous to those that are well-versed in this sort of thing.
Click to expand...
Click to collapse
You do know that there is an app for SU built into CM right? So it is no extra apps then any other rom.
Could you yes but it will be lots of work due to what CM changes in the source code. It is one of the many reasons (on top of years old bugs that were never fixed) That many teams stopped using them as a source. The Shamu will be supported by 3rd party developers for a while to come.
Normally ram is an issue but other issues also happen.
I dont know anything about having to attach your device to VM as I have never used VM due to advise from the developers here.
Asking questions is not that big of a deal as long as you do your research. There are tons of TUT on the site about setting up a build setup. Just use the search and spend a few days reading. Mainly where the licenses are concerned. Also commit authorship. Which is you make your own rom it is very important.

zelendel said:
You do know that there is an app for SU built into CM right? So it is no extra apps then any other rom.
Could you yes but it will be lots of work due to what CM changes in the source code. It is one of the many reasons (on top of years old bugs that were never fixed) That many teams stopped using them as a source. The Shamu will be supported by 3rd party developers for a while to come.
Normally ram is an issue but other issues also happen.
I dont know anything about having to attach your device to VM as I have never used VM due to advise from the developers here.
Asking questions is not that big of a deal as long as you do your research. There are tons of TUT on the site about setting up a build setup. Just use the search and spend a few days reading. Mainly where the licenses are concerned. Also commit authorship. Which is you make your own rom it is very important.
Click to expand...
Click to collapse
Okay, so I have done some research and have a solution for how to use root with stock Android, but as soon as stock Android support is dropped from the Nexus 6 I will have to compile it myself which I am not sure how to do and would like to learn. Do you have any suggestions for what to go to learn since everything I am finding is not about compiling, but is instead about using an existing build?

David B. said:
Okay, so I have done some research and have a solution for how to use root with stock Android, but as soon as stock Android support is dropped from the Nexus 6 I will have to compile it myself which I am not sure how to do and would like to learn. Do you have any suggestions for what to go to learn since everything I am finding is not about compiling, but is instead about using an existing build?
Click to expand...
Click to collapse
Here you go
https://source.android.com/source/initializing.html
Mind you getting root is more then adding an app for it. You will also have to do some kernel edits.

zelendel said:
Here you go
https://source.android.com/source/initializing.html
Mind you getting root is more then adding an app for it. You will also have to do some kernel edits.
Click to expand...
Click to collapse
Thanks! I also found this. I have not really looked at it too much yet, but it seems like it has the potential to help me with what I want. Why would I need to make kernel edits? I thought all I needed to do was use TWRP to flash SuperSU after flashing the ROM.

David B. said:
Thanks! I also found this. I have not really looked at it too much yet, but it seems like it has the potential to help me with what I want. Why would I need to make kernel edits? I thought all I needed to do was use TWRP to flash SuperSU after flashing the ROM.
Click to expand...
Click to collapse
SuperSU edits the kernel when you flash it. Most of what allows root is in the kernel.
Yes that is a great resource. Just take your time and read it. You could have a working set up and build in about 2 days (given the first sync of the source code could take more then 24 hours depending on your connection.

zelendel said:
SuperSU edits the kernel when you flash it. Most of what allows root is in the kernel.
Yes that is a great resource. Just take your time and read it. You could have a working set up and build in about 2 days (given the first sync of the source code could take more then 24 hours depending on your connection.
Click to expand...
Click to collapse
One thing that I still cannot figure out after all of this reading is what to do to get AOSP to build for devices that are not officially supported by it. Granted, this is not a problem for the Nexus 6 right now, but it will be eventually, and I want to know how to handle it when it does become an issue. I've started cloning the repository. My connection gets a top download speed of 60Mbps so it should be reasonably fast.

David B. said:
One thing that I still cannot figure out after all of this reading is what to do to get AOSP to build for devices that are not officially supported by it. Granted, this is not a problem for the Nexus 6 right now, but it will be eventually, and I want to know how to handle it when it does become an issue. I've started cloning the repository. My connection gets a top download speed of 60Mbps so it should be reasonably fast.
Click to expand...
Click to collapse
At that point you will need to know what you are doing as you will have to make the code changes to make it bootable. I hate to say it but the n6 maybe doa after this as anything after 7.1 will need dual partition setup which the n6 doesn't have

zelendel said:
At that point you will need to know what you are doing as you will have to make the code changes to make it bootable. I hate to say it but the n6 maybe doa after this as anything after 7.1 will need dual partition setup which the n6 doesn't have
Click to expand...
Click to collapse
What's stopping the phone from being repartitioned in the same way you repartition a hard drive?

David B. said:
What's stopping the phone from being repartitioned in the same way you repartition a hard drive?
Click to expand...
Click to collapse
The main issue is none of the software for the n6 are made to work with it. All the drivers have to be rewritten. Also all of the new Vulcan graphics drivers won't work on the n6. This is why it didn't get all the features of 7.0

zelendel said:
The main issue is none of the software for the n6 are made to work with it. All the drivers have to be rewritten. Also all of the new Vulcan graphics drivers won't work on the n6. This is why it didn't get all the features of 7.0
Click to expand...
Click to collapse
I had not heard of this before. I was researching it online a bit and I cannot figure out which features are missing from the Nexus 6 version of Nougat. Also, Nougat has to support older hardware for devices that don't support Vulkan, so there's no reason they can't do that for Android O, and it they don't, surely someone smarter than I will be able to hack it together.

David B. said:
I had not heard of this before. I was researching it online a bit and I cannot figure out which features are missing from the Nexus 6 version of Nougat. Also, Nougat has to support older hardware for devices that don't support Vulkan, so there's no reason they can't do that for Android O, and it they don't, surely someone smarter than I will be able to hack it together.
Click to expand...
Click to collapse
That's the thing is android O will only be official supported by devices that can use it. Remember the nexus 6 support ended in October so there won't be an official O release for it.
Will there be a hacked together set up? Oh I'm sure there will be. It will just be without the Vulcan graphics drivers and the new update system which needs the dual partition layout.
The missing features are no background updates, no Vulcan drivers among other things

zelendel said:
That's the thing is android O will only be official supported by devices that can use it. Remember the nexus 6 support ended in October so there won't be an official O release for it.
Will there be a hacked together set up? Oh I'm sure there will be. It will just be without the Vulcan graphics drivers and the new update system which needs the dual partition layout.
The missing features are no background updates, no Vulcan drivers among other things
Click to expand...
Click to collapse
Well if the only things I lose are Vulkan and background updates, I am cool with that. It sounds like Vulkan is intended for games, and since I hate mobile gaming, an adapted build that works with the existing graphics drivers is not a concern at all. As for background updates, I would rather not have those because I like to know when my phone receives updates.

David B. said:
Well if the only things I lose are Vulkan and background updates, I am cool with that. It sounds like Vulkan is intended for games, and since I hate mobile gaming, an adapted build that works with the existing graphics drivers is not a concern at all. As for background updates, I would rather not have those because I like to know when my phone receives updates.
Click to expand...
Click to collapse
The Vulcan driver will be replacing the graphics drivers for everything soon. I can't think of much as I never use stock software.

zelendel said:
The Vulcan driver will be replacing the graphics drivers for everything soon. I can't think of much as I never use stock software.
Click to expand...
Click to collapse
I am sorry, but I am afraid I do not quite understand what it is that you said. What can't you think of?

David B. said:
I am sorry, but I am afraid I do not quite understand what it is that you said. What can't you think of?
Click to expand...
Click to collapse
There were many features that came with 7.0 like the new advanced doze and some other stuff. I dont use stock software and to be honest most of the stuff from 7.0 wasnt even really worth the update to me.
I have had a nexus since day 1 on and off and this was the first time I wasnt excited about the update. Even less with the new updates coming and google locking android down more as well as them moving most of the new stuff to closed sourced stuff. Heck even just having the bootloader unlocked is causing things not to work.

zelendel said:
There were many features that came with 7.0 like the new advanced doze and some other stuff. I dont use stock software and to be honest most of the stuff from 7.0 wasnt even really worth the update to me.
I have had a nexus since day 1 on and off and this was the first time I wasnt excited about the update. Even less with the new updates coming and google locking android down more as well as them moving most of the new stuff to closed sourced stuff. Heck even just having the bootloader unlocked is causing things not to work.
Click to expand...
Click to collapse
Really? What doesn't work with the unlocked bootloader?

David B. said:
Really? What doesn't work with the unlocked bootloader?
Click to expand...
Click to collapse
Things like android pay and saftynet. They are now starting to look for unlocked bootloaders. then you have those that are blocking apps due to root or xposed.

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