Database Develop

[Q] windows 8 on galaxy note gt-n7000

can we have windows 8 ported on our galaxy note?

ravepark said:
can we have windows 8 ported on our galaxy note?
Click to expand...
Click to collapse
I would be very interested if there is a way to do it.

Same here, but I don't think it is possible
Sent from my GT-N7000 using XDA

??
Why would you wanna go to windows 8 with android around ? Android on G-note is much more powerful than with windows.

incase you haven't checked the "apollo" and it's capabilities please do a brief research...
windows phone 8 is on a whole new level of competition here...
considering the release of windows 8 for our computers... and the Microsoft E3 press conference... i doubt that "crappy" tag someone just gave above this comment...
i've been using windows mobile 6, 6.1, 6.5, windows phone 7, mango... and galaxy note is my first android device...
before galaxy note i was using htc hd2 and i still have that device... (but galaxy note is my primary device) so i thought if we can port android on a windows phone why can't we port windows to an android phone?

and for the respected people who are interested in this idea... i think we need another version of MAGLDR (like we had in htc hd2) and maybe we can install the "apollo" on our SD card...
we may have a dual boot device!

if you can find (or develop) the drivers, yes... it can be ported.
and yes, i dare say any winblows product is crap

you may "dare" **** your pants or eat crap sir/madam, nobody cares about that... and if you find this post soooo uninteresting or "crappy" why bother replying nonsense thoughts of your p-brain which (...is actually dehydrated) aren't useful for anyone?!
and thanks for the motivation you just gave me... :]
i posted this question to discuss, maybe help real developers/people not assclowns/disrespectful people who don't even respect the hardworking developers who create these operating systems for us...

Its my humble opinion !!!
I was also a user of Windows and bada OS' . And with android around they are not even in the competition. And this is my own opinion, so i'll move it off.

Android is, indeed, more powerful than Windows. But, different strokes for different folks.
Since we have sources now, I'm pretty sure more developers will come along soon and hopefully, for your sake, a developer that can port Windows 8. The more variety, the better, for us all.

andreww88 said:
Android is, indeed, more powerful than Windows. But, different strokes for different folks.
Since we have sources now, I'm pretty sure more developers will come along soon and hopefully, for your sake, a developer that can port Windows 8. The more variety, the better, for us all.
Click to expand...
Click to collapse
the last line this person wrote is what i had in my mind...

ravepark said:
and for the respected people who are interested in this idea... i think we need another version of MAGLDR (like we had in htc hd2) and maybe we can install the "apollo" on our SD card...
we may have a dual boot device!
Click to expand...
Click to collapse
Agree would be awesome and fair competition)

ravepark said:
can we have windows 8 ported on our galaxy note?
Click to expand...
Click to collapse
Not in TEN MILLION seconds!

Being fair, would it be worth to port it in d note cuz, it involves a lot of time and much more risk( With mmc brick bugs in stable releases themselves).
Sent from my GT-N7000 using xda premium

DuperMan said:
Not in TEN MILLION seconds!
Click to expand...
Click to collapse
LOL sir i don't even know if there is an apollo device out in the market... it is due to release to my knowledge...

ravepark said:
can we have windows 8 ported on our galaxy note?
Click to expand...
Click to collapse
If you want the windows UI, you can install launcher 7. It's a launcher for your note with the theme of windows 8. try it

JoshuaTumanda said:
If you want the windows UI, you can install launcher 7. It's a launcher for your note with the theme of windows 8. try it
Click to expand...
Click to collapse
it's not just for the launcher... it's for the windows phone experience
the developers can try porting mango for now untill apollo releases.. :]

andreww88 said:
Since we have sources now, I'm pretty sure more developers will come along soon and hopefully, for your sake, a developer that can port Windows 8. The more variety, the better, for us all.
Click to expand...
Click to collapse
don't hold your breath. those sources are linux based as android is linux based. do you expect devs to develop a winblows OS based on a linux kernel?
maybe.... just maybe.... when the winblows kernel is freely available and somebody is really interested to port or develop the drivers, then maybe you might have a winblows "experience" on your note. and while you're at it, why not wish for iOS port to Note?
keep wishing........
people hate it when the absurdity of their delusions hits them smack in the face.
Zapped through server hops to XDA forums

praetorius said:
don't hold your breath. those sources are linux based as android is linux based. do you expect devs to develop a winblows OS based on a linux kernel?
maybe.... just maybe.... when the winblows kernel is freely available and somebody is really interested to port or develop the drivers, then maybe you might have a winblows "experience" on your note. and while you're at it, why not wish for iOS port to Note?
keep wishing........
people hate it when the absurdity of their delusions hits them smack in the face.
Zapped through server hops to XDA forums
Click to expand...
Click to collapse
Cheers :]

If you want it to come true, put out a bounty.

Dual Boot Possible?

Was curious if anyone one has looked into dual booting on this device. Like Firefox OS and Android. If no one has checked into ill will when i get my phone back friday. If its not possible then maybe ill just try porting Firefox OS for our device. Already looked into the firefox porting and doesnt look like it will be that hard to get it on our devices. however i still prefer dualboot if possible.

TripFX said:
Was curious if anyone one has looked into dual booting on this device. Like Firefox OS and Android. If no one has checked into ill will when i get my phone back friday. If its not possible then maybe ill just try porting Firefox OS for our device. Already looked into the firefox porting and doesnt look like it will be that hard to get it on our devices. however i still prefer dualboot if possible.
Click to expand...
Click to collapse
Would be nice but I don't think its possible, but there was something in the galaxy s thread about it so idk.maybe talk to camcory about it.

Ya that's what gave me the idea about doing it for our phones. I wait on asking camroy til i get my phone in and get at least a native port of Firefox OS before worrying the dual boot part for now. Plus I'll have to test the port and see whats majorly broken and what is not. Worse case I know i can take a different approach and do like I did back in the day with my windows mobile 2003 phone and have it on the sdcard. So you start up like normal into (for this case just saying how the windows mobile/android boot worked) Windows Mobile. Then launch an app that shuts down windows mobile completely to free up resources then it boots up android GB (when i did this) from sdcard. It really wasn't hard to get it to do that. So i don't see why we couldn't do the same for this phone but Android and Firefox OS. Least the brighter side of using android and firefox is that they both are made for the same hardware where compared to my windows mobile phone it ran an xscale cpu ( Windows only cpu ). So it shouldn't feel slower than what it would by it's self. Android just wasn't made for intel xscale cpus.

TripFX said:
Ya that's what gave me the idea about doing it for our phones. I wait on asking camroy til i get my phone in and get at least a native port of Firefox OS before worrying the dual boot part for now. Plus I'll have to test the port and see whats majorly broken and what is not. Worse case I know i can take a different approach and do like I did back in the day with my windows mobile 2003 phone and have it on the sdcard. So you start up like normal into (for this case just saying how the windows mobile/android boot worked) Windows Mobile. Then launch an app that shuts down windows mobile completely to free up resources then it boots up android GB (when i did this) from sdcard. It really wasn't hard to get it to do that. So i don't see why we couldn't do the same for this phone but Android and Firefox OS. Least the brighter side of using android and firefox is that they both are made for the same hardware where compared to my windows mobile phone it ran an xscale cpu ( Windows only cpu ). So it shouldn't feel slower than what it would by it's self. Android just wasn't made for intel xscale cpus.
Click to expand...
Click to collapse
Well the s4 has dual boot and HTC is capable and what i was reading in the galaxy s forum it looks like i might be capable. And for firefox i see in the nexus s the camera and bluetooth doesnt work but i think cam has fixes for that so i guess youll find out once you compile the rom. If you need help with testing or anything let me know I'd be happy to help.

schuylkillparanormal said:
Well the s4 has dual boot and HTC is capable and what i was reading in the galaxy s forum it looks like i might be capable. And for firefox i see in the nexus s the camera and bluetooth doesnt work but i think cam has fixes for that so i guess youll find out once you compile the rom. If you need help with testing or anything let me know I'd be happy to help.
Click to expand...
Click to collapse
Well got my phone back already got AOIP on it and been testing out the device its self to make sure it wasn't defective and its not. So now I'm gonna start working the firefox os port with in the next few days. its been quite a while since I've done any programing and what not so not promising anything but I will definitely try. So bare with me on progress. Any how I know we can run firefox os on our phones. according to Mozilla ]https://developer.mozilla.org/en-US/docs/Mozilla/Firefox_OS/Introduction hardware requirements is arm6 cortex5 or better cortex 7 with neon, adreno 200. then the rest is standard wifi/3g gps and others like that. So yeah its possible. its just building the rom and fixing device specific bugs. Also yeah I wouldn't mind having internal beta testers when i get to that point. Just glad mozilla has a lot of useful resources on porting it.

TripFX said:
Well got my phone back already got AOIP on it and been testing out the device its self to make sure it wasn't defective and its not. So now I'm gonna start working the firefox os port with in the next few days. its been quite a while since I've done any programing and what not so not promising anything but I will definitely try. So bare with me on progress. Any how I know we can run firefox os on our phones. according to Mozilla ]https://developer.mozilla.org/en-US/docs/Mozilla/Firefox_OS/Introduction hardware requirements is arm6 cortex5 or better cortex 7 with neon, adreno 200. then the rest is standard wifi/3g gps and others like that. So yeah its possible. its just building the rom and fixing device specific bugs. Also yeah I wouldn't mind having internal beta testers when i get to that point. Just glad mozilla has a lot of useful resources on porting it.
Click to expand...
Click to collapse
Best of luck.

Sailfish OS for Nexus 6? (on multirom hopefully (so talking to you as well Tassadar))

I've looked into porting this myself based on the instructions provided from Jolla's website (found here https://sailfishos.org/develop/hadk/), it seems pretty straight forward. However apparently (according to Jolla) it cannot be done on a 32bit system even if I use Linux (which I do). I was wondering if anyone has entertained the thought of porting it, as there's a 2.0 version of the OS out now and I really want to try it. Kind of missing it from when I used to play around with it on my Nexus 5.
Conversely, if anyone knows a workaround to using a 32bit system, or if they have knowledge of it actually being possible on a 32bit system (could be Jolla is being overly cautious in requiring a 64bit system, but I believe it has something to do with working with MER), your advice would be forthcoming. Willing to put in the work, I just apparently don't have the tools according to Jolla and can't afford a new computer. My two Linux systems (one running Kubuntu, one running Backbox) are very capable. This is just the only prerequisite I don't meet.
As far as multirom, I'm curious if anything special has to be done besides the instructions from Jolla to make it compatible as a secondary rom at least.
Thanks in advance for all responses and patience. I may be a low contributor/noob to this site, but given the proper tools and advice I think I can pull it off. I haven't found anyone that's working on this for the Nexus 6, so if there is someone, obviously I'm willing to help or test.
Special note to Tassadar if you happen to see this: Multirom is the best thing that's happened to android since custom kernels. lol Big ups for your creation!

Awesome I hope more are interested too, I don't have resources to help either besides a test.
I can say that I have never been more impressed with a UI than the one I flashed on my n5 called Sailfish, Same as you I think.
To others of you have what's needed and haven't seen the ui please check it out. I thought it was minimal, sleek, and I believe it used mostly touch commands.

This thread is kinda in the wrong forum. Should be in q and a or general discussion.
But yes I would love to see this on my phone

First, don't post Q&A in development forums. Second, the first step in the guide states the device must be officially supported with CM 10.1.x, which this device isn't. Unless they just haven't updated their guide this will never be possible until it's updated to something based on Lollipop.

nuevosean said:
I've looked into porting this myself based on the instructions provided from Jolla's website (found here https://sailfishos.org/develop/hadk/), it seems pretty straight forward. However apparently (according to Jolla) it cannot be done on a 32bit system even if I use Linux (which I do). I was wondering if anyone has entertained the thought of porting it, as there's a 2.0 version of the OS out now and I really want to try it. Kind of missing it from when I used to play around with it on my Nexus 5.
Conversely, if anyone knows a workaround to using a 32bit system, or if they have knowledge of it actually being possible on a 32bit system (could be Jolla is being overly cautious in requiring a 64bit system, but I believe it has something to do with working with MER), your advice would be forthcoming. Willing to put in the work, I just apparently don't have the tools according to Jolla and can't afford a new computer. My two Linux systems (one running Kubuntu, one running Backbox) are very capable. This is just the only prerequisite I don't meet.
As far as multirom, I'm curious if anything special has to be done besides the instructions from Jolla to make it compatible as a secondary rom at least.
Thanks in advance for all responses and patience. I may be a low contributor/noob to this site, but given the proper tools and advice I think I can pull it off. I haven't found anyone that's working on this for the Nexus 6, so if there is someone, obviously I'm willing to help or test.
Special note to Tassadar if you happen to see this: Multirom is the best thing that's happened to android since custom kernels. lol Big ups for your creation!
Click to expand...
Click to collapse
Please read the Forum Rules on posting, Moved here...

FYI, android also has needed to be built on 64 bit only for several versions now. I think since Ice Cream Sandwich.. 32 bit just isn't cut out for it.

Sorry to raise this thread from the depths, but why haven't any devs pursued this?
I would love to try sailfish os on the nexus 6!
A $200 budget device was released just a few days ago in India that runs sailfish os natively, which is why i started looking into it for shamu.
Thought about picking one up, but the cellular bands aren't great for use in the U.S., and spec-wise doesn't hold a candle to shamu.
Through a little searching, it seems one person with the handle of mad_fitter on merproject irc attempted a port back in March, but never finished it afaict. Apparently, the fact that he had an intel chip prevented him from completing the final steps somehow...

This is an old post, but i love my phone and have dabbled with sailfish os before. If it could be ported that would be great and according to the the HADK documentation you can now use a cm 12.1 image instead of 10 to build it, whih was available for shamu. Someone could get the image from archive.org and use that. I have no experience with porting roms so i wouldn't be able to do it but if someone else could it would be great for the few of us that want it.

I would love to try this on my shamu, as well.
Has there been any development on this?

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.