Database Develop

[Q] Integrating Updates into Current Builds

Not trying to be a troll - I'm looking for some insight.
It appears to me that there is a degree of inefficiency with the progress of the Camera updates being made on the HP TouchPad. Those updates are on a static and aged build of CM9.
What does it take to have the code/ROM updates for the working camera ported over to the more recent builds of CM9 and CM10?
I know the inside joke/anti-troll repellant response of "two weeks" or "soon" are out there. That's not what I'm looking for. I'm really trying to understand why devs would continue to leave these advancements off of the more recent/enhanced builds?
Is the answer really just that the single dev (or team) wants a static version to perfect the driver so it doesn't have to keep "changing the wheel on a moving car"?
--McBean

McBeanTIO said:
Not trying to be a troll - I'm looking for some insight.
It appears to me that there is a degree of inefficiency with the progress of the Camera updates being made on the HP TouchPad. Those updates are on a static and aged build of CM9.
What does it take to have the code/ROM updates for the working camera ported over to the more recent builds of CM9 and CM10?
I know the inside joke/anti-troll repellant response of "two weeks" or "soon" are out there. That's not what I'm looking for. I'm really trying to understand why devs would continue to leave these advancements off of the more recent/enhanced builds?
Is the answer really just that the single dev (or team) wants a static version to perfect the driver so it doesn't have to keep "changing the wheel on a moving car"?
--McBean
Click to expand...
Click to collapse
Dorregaray explained it in a RootzWiki post: http://rootzwiki.com/topic/16347-de...hw-acceleration-fix/page__st__170#entry965452. I think changes have been made to upstream CM9 that make inclusion of the camera fixes more complicated.

bananagranola said:
Dorregaray explained it in a RootzWiki post: http://rootzwiki.com/topic/16347-de...hw-acceleration-fix/page__st__170#entry965452. I think changes have been made to upstream CM9 that make inclusion of the camera fixes more complicated.
Click to expand...
Click to collapse
the new code for the camera is simply not commited to the CM9 repo at the moment. It is awaiting approval by someone who can review the code. However, it is possible to "Cherry Pick" the code updates into a new build. I was doing exactly that this morning, with some difficulty, and did not end up with a better product than what is currently available, ie. blue screen on boot sometimes...

-SGA- said:
the new code for the camera is simply not commited to the CM9 repo at the moment. It is awaiting approval by someone who can review the code. However, it is possible to "Cherry Pick" the code updates into a new build. I was doing exactly that this morning, with some difficulty, and did not end up with a better product than what is currently available, ie. blue screen on boot sometimes...
Click to expand...
Click to collapse
Ooh. Good to know. I had thought that there were changes that needed to be made to existing CM before the camera stuff would be compatible with it. The fact that it's all ready to go is excellent news!

bananagranola said:
Ooh. Good to know. I had thought that there were changes that needed to be made to existing CM before the camera stuff would be compatible with it. The fact that it's all ready to go is excellent news!
Click to expand...
Click to collapse
Yes, it seems like most of the fixes that needed to be made for the memory split have been implemented in theory. However, I imagine the blue screen issue would need to be solved before the code is merged into CM9, as it makes it less than stable. Be it as it might, I think we would still do fine with unofficial CM9 camera builds if the code is never merged at all.

[Q] What is the situation of CyanogenMod?

CyanogenMod recently pushed out stables for CM10.2 on a select range of devices announcing that, with this, their efforts would be solely focused towards the CM11 code branches. However, they also announced that any devices which received that RC1 of CM10.2 would too continue into CM11.
My question, considering we are still unfortunate enough to be on somewhat unstable nightlies (the notification sound delay, UI issues, application crashes) is, what will be the future of CyanogenMod on the O4x? Will we even make it to stable CM10.2?
Hopefully we can! This is such a brilliant device as you all know well, and the hardware restrictions of KitKat are supposed to be lowered anyway
For clarification, this is not a complaint, the work of the CyanogenMod Team is always much appreciated. I, and so many of you, have donated and thanked them and tested their software for them. This is merely to gain an understanding of where our device is headed so as to aid everybody here in the decision of whether to stick with the device or, should worse come to worse.... look for another :-/

csfrank271 said:
CyanogenMod recently pushed out stables for CM10.2 on a select range of devices announcing that, with this, their efforts would be solely focused towards the CM11 code branches. However, they also announced that any devices which received that RC1 of CM10.2 would too continue into CM11.
My question, considering we are still unfortunate enough to be on somewhat unstable nightlies (the notification sound delay, UI issues, application crashes) is, what will be the future of CyanogenMod on the O4x? Will we even make it to stable CM10.2?
Hopefully we can! This is such a brilliant device as you all know well, and the hardware restrictions of KitKat are supposed to be lowered anyway
For clarification, this is not a complaint, the work of the CyanogenMod Team is always much appreciated. I, and so many of you, have donated and thanked them and tested their software for them. This is merely to gain an understanding of where our device is headed so as to aid everybody here in the decision of whether to stick with the device or, should worse come to worse.... look for another :-/
Click to expand...
Click to collapse
probably no official CM11 for us, or 10.2 stable/rc, atleast in forseeable future. thankfully, we have some very skilled devs working on unofficial version of CM, & Vanir&Omni.

Flying_Bear said:
probably no official CM11 for us, or 10.2 stable/rc, atleast in forseeable future. thankfully, we have some very skilled devs working on unofficial version of CM, & Vanir&Omni.
Click to expand...
Click to collapse
Thank you, I was just wondering about the state of the official ROMs, it seems like the P880 has been forgotten about by CM
But, as you say, we are very lucky to have these fantastic devs building even better custom ROMs

Flying_Bear said:
probably no official CM11 for us, or 10.2 stable/rc, atleast in forseeable future. thankfully, we have some very skilled devs working on unofficial version of CM, & Vanir&Omni.
Click to expand...
Click to collapse
If everything is working right we should be able to submit it to cyanogenmod to get our nightlies back, but im not 100% sure

JoinTheRealms said:
If everything is working right we should be able to submit it to cyanogenmod to get our nightlies back, but im not 100% sure
Click to expand...
Click to collapse
Hopefully we can have the issues fixed
Can't wait to see the community development though, the new Android RunTime looks very fascinating :3

why dont u enter cyanogenmod and see with your eyes ? anyway. of course we dont see any support. its a miracle that we had that much support too. who will support a phone which doesnt even has the support of the official company ? LG only had 4.0.3 and 4.1.2 and thats all. isnt it already a miracle that we have 4.3.1 ? and we have also so many good developers that work for 4.4 ?

I don't understand why people want 4.4 so bad when it's one of the worst upgrades from Google i have ever seen. They had to launch 4.4.1 updates right away. You want a better software I agree thats needed but 4.4 isn't a solution.
Sent from my OptimusX4HD using xda app-developers app

Zhus06 said:
I don't understand why people want 4.4 so bad when it's one of the worst upgrades from Google i have ever seen. They had to launch 4.4.1 updates right away. You want a better software I agree thats needed but 4.4 isn't a solution.
Sent from my OptimusX4HD using xda app-developers app
Click to expand...
Click to collapse
Everyone wants KitKat because... Well, because it's new! Why not? I believe that pushing one's expectations beyond what is already achieved represents a strong impulse to improvement. Experimenting, trying new solutions, feeling the awesomeness of something that did not exist before is a powerful spring to the change, the change in itself is something that animates the developers and makes them work with no reward as if this was their job.
It has happened with all Android versions, and always there had been someone who felt amazed and wondered why should we need a new version.
kK can be (and probably is, but who am I to judge) one of the worst Android versions, but I am happy to see people trying to overcome all the problems related with making it work on a relatively old device, and I am happy if by testing what is being developed, and by giving my opinion I can be of some help to somebody.
Want to call it a game? Why not! Want to consider people like me as grown up kids that need something to play with? Well, yes, I am, and will always cheer a new Android version working on one of my devices with grateful heart.

Ricardo Cerqueira is no longer the maintainer of our device?
there is no one who will replace him?

It should be possible to join the CM team, if the 4.4 is running.
The tegra3 problems will hopefully not be a trap for it.
If there is a maintainer who can update CM once, there will be no real reason not to get official support.

Good news everybody!
On the CyanogenMod website, the P880 has been listed officially as one the devices to receive support further than the CM10.2 nightlies, which will be a win-win for everyone

Bye Bye CM !

DarkFantasy6 said:
Bye Bye CM !
Click to expand...
Click to collapse
Why do you say that? :-/

csfrank271 said:
On the CyanogenMod website, the P880 has been listed officially as one the devices to receive support further than the CM10.2 nightlies, which will be a win-win for everyone
Click to expand...
Click to collapse
I saw the latest list the have revealed now, this is great!!
Noticed though that they said MOST of the devices that have CM10.2 builds will move into CM11 nightly during the next weeks.. "Most" hopefully means the P880 as well!

faabak said:
I saw the latest list the have revealed now, this is great!!
Noticed though that they said MOST of the devices that have CM10.2 builds will move into CM11 nightly during the next weeks.. "Most" hopefully means the P880 as well!
Click to expand...
Click to collapse
Yes, hopefully!
But hey, a stable CM10.2 would even be fantastic, the community devs would appreciate it surely

We never got the m1 and stable so i hardly belive it that we get cm11. And without a good 3.4 kernel source from lg we wont feeo many adventafes of 4.4. but the awesome awesome optic would be nice Maybe im going to buy a Nexus 5. Im so frustrated of my lg optimus 2x and 4x. ONE update -.-

Question about Cataclysm.

Hey guys, just a quick question, is Cataclysm rom built off of a genuine stock system.img like the ones hosted on the google dev site? Or is some of it AOSP based? And if it is from stock genuine Android, isn't there some kind of legal issue with that? Just wondering this, I use Cataclysm and I LOVE IT! It's my daily driver! Thanks all!

H4X0R46 said:
Hey guys, just a quick question, is Cataclysm rom built off of a genuine stock system.img like the ones hosted on the google dev site? Or is some of it AOSP based? And if it is from stock genuine Android, isn't there some kind of legal issue with that? Just wondering this, I use Cataclysm and I LOVE IT! It's my daily driver! Thanks all!
Click to expand...
Click to collapse
The dev had an explanation of how it worked on the original thread. Android is open source and google releases sources for all the nexus devices and they also conveniently package them into flashable images to fix things. There was at least 1 release where the dev had to wait for the source to come out even though the factory images were out in order to do anything. So in short no there's no legal issue. The dev used open source files and modified them for non-profit. The reason no one else really does that type of mod is due to the fact that AOSP mods are widespread and people can just use others' code to incorporate them into the rom (or just use CM). Or if the dev is particularly dedicated then they might use an AOSP base because they want to keep up with all the bleeding edge enhancements to android which may or may not have any real benefit. When you target just 1 device by using its stock rom source then the mods have to be made for specifically that device (and why would anyone create code for 1 device when they could just use what works on virtually all devices) though the Nexuses are evidently similar enough to port between them hence the N5, 6, 5x, and 6p versions. The use of the stock source however meant that you kept the "rock solid stability" that Google's team of software engineers created so the dev could focus on adding features because the base he was working on was solid.

StykerB said:
The dev had an explanation of how it worked on the original thread. Android is open source and google releases sources for all the nexus devices and they also conveniently package them into flashable images to fix things. There was at least 1 release where the dev had to wait for the source to come out even though the factory images were out in order to do anything. So in short no there's no legal issue. The dev used open source files and modified them for non-profit. The reason no one else really does that type of mod is due to the fact that AOSP mods are widespread and people can just use others' code to incorporate them into the rom (or just use CM). When you target just 1 device by using its stock rom source then the mods have to be made for specifically that device (and why would anyone create code for 1 device when they could just use what works on virtually all devices) though the Nexuses are evidently similar enough to port between them hence the N5, 6, 5x, and 6p versions. The use of the stock source however meant that you kept the "rock solid stability" that Google's team of software engineers created so the dev could focus on adding features because the base he was working on was solid.
Click to expand...
Click to collapse
So all in all, Cataclysm is using stock Android and not AOSP, but done in a way that there are no legal issues? So in essence, flashing the system.img file from the dev site and adding Cataclysm mod to it is the the exact same difference as using the full Cataclysm installer? No AOSP added?

StykerB said:
.... "rock solid stability" that Google's team of software engineers created
Click to expand...
Click to collapse
That has a price:
- white ui, grey text on white bad readable; especially with sunlight;
- white background causes battery drain on amoled displays;
- pesky search bar; not removable or change to transparent;
- no option to change to a dark theme;
- N6 full resolution 2560 x 1440 not used;
- N6 native resolution = 493. G. sets it to 560 dpi;
- no option to kill running apps;
- code to use layers can't be used without rooting;
- G-apps not predestinated for layers.....etc.

NLBeev said:
That has a price:
- white ui, grey text on white bad readable; especially with sunlight;
- white background causes battery drain on amoled displays;
- pesky search bar; not removable or change to transparent;
- no option to change to a dark theme;
- N6 full resolution 2560 x 1440 not used;
- N6 native resolution = 493. G. sets it to 560 dpi;
- no option to kill running apps;
- code to use layers can't be used without rooting;
- G-apps not predestinated for layers.....etc.
Click to expand...
Click to collapse
Yes but would you rather not have something solid for people to build on? some of those things aren't even about stability... like the full resolution thing? assuming you're referring to onscreen buttons, and DPI is always on every device set in multiples of 80 for app standardization reasons. The overlay code for layers wasn't intended to be used for theming. Hence why google only used it for stuff like the ATT boot animation. and Google's apps and OS are separate and shouldn't be expected to adhere to a modding community's theme engine that they don't support. And dark themes were probably a design decision rather than actual stability issue.

StykerB said:
.....some of those things aren't even about stability... like the full resolution thing?....
Click to expand...
Click to collapse
You're right my list is not about stability only.
Using the N6 now for more than a year. I've seen a beta version with a dark theme, but it was removed. Why? Stability issues ?
To make the N6 acceptable for my daily use, especially battery life and readability, I had to change a lot of things. That has consequences for the stability. The N6 is still stable but I wouldn't say rock stable.

So all in all cataclysm is built using real Android? The main question in this thread lol But yea, AOSP does have it pros and cons as well as stock, I have to play devils advocate here and say that all roms do have their differences.

H4X0R46 said:
So all in all cataclysm is built using real Android? The main question in this thread lol But yea, AOSP does have it pros and cons as well as stock, I have to play devils advocate here and say that all roms do have their differences.
Click to expand...
Click to collapse
Yes what he did was use the stock android package. But make no mistake. AOSP is the real android. There are very few diff between what google releases and AOSP. The main diff is thie closed sourced stuff Google adds.

zelendel said:
Yes what he did was use the stock android package. But make no mistake. AOSP is the real android. There are very few diff between what google releases and AOSP. The main diff is thie closed sourced stuff Google adds.
Click to expand...
Click to collapse
Thanks! I was never sure just how much stuff is taken out of AOSP, but it's just small differences then. Glad I know that now! And hey, since we're on the subject, how are gapps legal? Aren't gapps those closed source bits that google DOES omit from AOSP? Play store and background things? Like, I know there's some legal thing where gapps shouldn't be preinstalled in an AOSP rom, but what's the grey area with gapps? Thanks again for the detailed description! Learning these things is good lol

If you have a look around, legal means very little here.
Google has only issued a C&D order to CM to not enclude it in their roms. This is why no aosp has them built in by default.

zelendel said:
If you have a look around, legal means very little here.
Google has only issued a C&D order to CM to not enclude it in their roms. This is why no aosp has them built in by default.
Click to expand...
Click to collapse
LOL I had a feeling that was the case here on XDA haha but I love Android and the development is HUGE! No other mobile OS can match Google's Android! Thanks for answering my questions man! Appreciate the help! Have a good rest of the night! Or day depending on where you're from, I'm from USA lol

H4X0R46 said:
LOL I had a feeling that was the case here on XDA haha but I love Android and the development is HUGE! No other mobile OS can match Google's Android! Thanks for answering my questions man! Appreciate the help! Have a good rest of the night! Or day depending on where you're from, I'm from USA lol
Click to expand...
Click to collapse
Im in the US as well. Well kinda lol I live in Alaska.
Yes it is but that might becoming to an end soon. With more and more people closing off their source. This is a good and bad thing. We will see what happens. Also more and more OEM are gonna lock down their devices so people will have to pic. Things like mobile pay or modding their device.

zelendel said:
Im in the US as well. Well kinda lol I live in Alaska.
Yes it is but that might becoming to an end soon. With more and more people closing off their source. This is a good and bad thing. We will see what happens. Also more and more OEM are gonna lock down their devices so people will have to pic. Things like mobile pay or modding their device.
Click to expand...
Click to collapse
Yea it's awful that people are making everything closed source! I'm a person who loves to tinker with my things, modded game consoles and phones and all, my hobby haha I just hope Android always stays open source! AOSP anyways. And are they starting to make Android devices more secure and non moddable? I hope the Nexus line always stays developer friendly, because I bought a Nexus for the sake of tinkering with it lol

H4X0R46 said:
Yea it's awful that people are making everything closed source! I'm a person who loves to tinker with my things, modded game consoles and phones and all, my hobby haha I just hope Android always stays open source! AOSP anyways. And are they starting to make Android devices more secure and non moddable? I hope the Nexus line always stays developer friendly, because I bought a Nexus for the sake of tinkering with it lol
Click to expand...
Click to collapse
Honestly. It because of script kiddies. The ones that just build from others source and post roms. Doing nothing but changing some text. To be honest all it would take is Google to stop pushing code to aosp. Android development would die off at that point.
Yeah if you look at things like Samsung, some devices are not even rootable, Sony, if you unlock the bootloader you lose the camera functions, even China based companies are locking bootloaders. Xiaomi just started doing this and have refused to give some the unlock because it goes against their business plan.
As for the nexus. We should be OK but then you have things like the Mm kernel that was a pain to get root on. And you lose mobile payments. Also more and more apps are looking for things like root and xposed and then refusing to work if they are installed.

zelendel said:
Honestly. It because of script kiddies. The ones that just build from others source and post roms. Doing nothing but changing some text. To be honest all it would take is Google to stop pushing code to aosp. Android development would die off at that point.
Yeah if you look at things like Samsung, some devices are not even rootable, Sony, if you unlock the bootloader you lose the camera functions, even China based companies are locking bootloaders. Xiaomi just started doing this and have refused to give some the unlock because it goes against their business plan.
As for the nexus. We should be OK but then you have things like the Mm kernel that was a pain to get root on. And you lose mobile payments. Also more and more apps are looking for things like root and xposed and then refusing to work if they are installed.
Click to expand...
Click to collapse
I've definitely heard of apps looking for root and for xposed framework (both of which I can't live without and use), and a lot of phones from certain companies are completely out of my interest because of no moddability. I wonder if it's even possible to root newer Samsung phones because of Knox security, and I won't even touch an Xperia, I've heard that they merge a lot of partitions, like boot and recovery and things like that, too confusing and not worth it to me. I just hope Android development stays strong in the Nexus scene at least, I love my Nexus!

Also, why do almost all AOSP ROMs have the "KitKat" sounds? Is that just what's released in AOSP? The "knocking" sounds I mean.

H4X0R46 said:
Also, why do almost all AOSP ROMs have the "KitKat" sounds? Is that just what's released in AOSP? The "knocking" sounds I mean.
Click to expand...
Click to collapse
To be honest I never noticed. I don't use any of the stock sounds.

H4X0R46 said:
I've definitely heard of apps looking for root and for xposed framework (both of which I can't live without and use), and a lot of phones from certain companies are completely out of my interest because of no moddability. I wonder if it's even possible to root newer Samsung phones because of Knox security, and I won't even touch an Xperia, I've heard that they merge a lot of partitions, like boot and recovery and things like that, too confusing and not worth it to me. I just hope Android development stays strong in the Nexus scene at least, I love my Nexus!
Click to expand...
Click to collapse
I dont think the Nexus line will see many issues other then root becoming harder to get.
Some Samsung devices cant be rooted. Like my buddy that is a samsung fan has a note 4, note 5 and a few Galaxy s5 in his house and all of them are locked down.
More and more people are too worried about things like warranty to even bother really. I even waited on updating the n6 until root was gotten for it.

Pretty sure those can be rooted but you trip Knox which voids warranty. I haven't looked at Sammy phones since I had my S4 but I know the Note 4 and S5 had ROMs.

HipKat said:
Pretty sure those can be rooted but you trip Knox which voids warranty. I haven't looked at Sammy phones since I had my S4 but I know the Note 4 and S5 had ROMs.
Click to expand...
Click to collapse
Nope no root for the note 5. Only some can be. The tmobile version doesn't lock the bootloader but the rest do.
As tripping Knox is not an option for many as it voids their warranty but flashing roms does that anyway.

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.