Related
Hi all,
I know the N4 has enough source code in AOSP and elsewhere to be able to build an AOSP ROM, but it doesn't quite seem "official" and doesn't offer that undeniable security of "Nexus support" that many have come to know and love. Now, I know people have said it's due to the Qualcomm chip being so new that it would take time to officially work it in, and that it'll likely come around with 4.2.2. Even still, I'm paranoid (just having bought an N4 myself). Is anyone else worried about the N4's future? Or is it just buyer's paranoia?
I'd love to hear some thoughts on this!
Just paranoid, you can't build a fully working Nexus 7 ROM solely from AOSP either, thanks to Tegra.
Rusty! said:
Just paranoid, you can't build a fully working Nexus 7 ROM solely from AOSP either, thanks to Tegra.
Click to expand...
Click to collapse
I figured that it was just that. But I suppose I was just seeking some reassurance haha. Between the recent articles on LG only making "as many Nexus 4's as they want," the speculations going around about the Nexus 5, and this lack of any word on AOSP support, I just got awfully scared that the Nexus 4 might be one of those devices that isn't around and supported for very long.
Speculations....Don't you love them when device is new...
Give it another month or two and everything will go back to "normal", just like with any other device.
undercover said:
Speculations....Don't you love them when device is new...
Give it another month or two and everything will go back to "normal", just like with any other device.
Click to expand...
Click to collapse
Haha I know, I know. But this was a big buy for me; relatively expensive and I'm ditching VZW for it. I'm just worried that I'll regret it later on, I guess.
andoird213 said:
Haha I know, I know. But this was a big buy for me; relatively expensive and I'm ditching VZW for it. I'm just worried that I'll regret it later on, I guess.
Click to expand...
Click to collapse
Learn to support yourself?
If you are relying on others to satisfy your purchase, well sooner or later you'll be in an unsupported boat.
tweaked said:
Learn to support yourself?
If you are relying on others to satisfy your purchase, well sooner or later you'll be in an unsupported boat.
Click to expand...
Click to collapse
I've built AOSP for it myself, that isn't the issue; it's a more general statement. I'm not relying on anyone for satisfaction, but there's a certain plus to being in a larger community rather than in one where it's only a few who feel stuck with the device.
andoird213 said:
I've built AOSP for it myself, that isn't the issue; it's a more general statement. I'm not relying on anyone for satisfaction, but there's a certain plus to being in a larger community rather than in one where it's only a few who feel stuck with the device.
Click to expand...
Click to collapse
Thats true. This is the nexus. I think you are ok there.
tweaked said:
Thats true. This is the nexus. I think you are ok there.
Click to expand...
Click to collapse
Here's to that!
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.
Feedback Contact: Telegram: https://t.me/nethunter666
Github https://github.com/johanlike/Oneplus6-or-6T-Nethunter-Kernel
Woww seems interesting . But im hardly find it . You must be create this in kernel and rom place of xda
javad79 said:
Woww seems interesting . But im hardly find it . You must be create this in kernel and rom place of xda
Click to expand...
Click to collapse
Forum level is not enough, can not post only can be sent here
Amazing work. Will try as soon as I get my Oneplus 6t.
Anyone test this yet? I am interested in getting the Oneplus 6t, but I will only do so if nethunter is able to work for the device.
enragedpaza said:
Anyone test this yet? I am interested in getting the Oneplus 6t, but I will only do so if nethunter is able to work for the device.
Click to expand...
Click to collapse
I've installed it on my 6t and can report that this kernel is functional. From what I've seen it's still being updated/worked on by the dev, but as is I can access the nethunter terminal and run commands.
ecera said:
I've installed it on my 6t and can report that this kernel is functional. From what I've seen it's still being updated/worked on by the dev, but as is I can access the nethunter terminal and run commands.
Click to expand...
Click to collapse
Thank you for the response. Are there any hiccups you are experiencing? What ROM are you currently using?
enragedpaza said:
Thank you for the response. Are there any hiccups you are experiencing? What ROM are you currently using?
Click to expand...
Click to collapse
I'm currently on OOS Ob4. As far as hiccups the kernel is smooth and battery life is actually really good. As far as nethunter itself? One thing I've noticed is that if I run a commands in the Kali terminal let's say airodump-ng and it's running. If for whatever reason my screen times out and turns off for a bit, or even if I switch to another screen real quick to check something. I've noticed that many times the Kali terminal process is killed and well I have to start over again. Not sure if it's Kali itself or even a kernel/OOS issue. Overall though, it is functional and in very early development stages. So I'm sure it only gets better from here.
ecera said:
I'm currently on OOS Ob4. As far as hiccups the kernel is smooth and battery life is actually really good. As far as nethunter itself? One thing I've noticed is that if I run a commands in the Kali terminal let's say airodump-ng and it's running. If for whatever reason my screen times out and turns off for a bit, or even if I switch to another screen real quick to check something. I've noticed that many times the Kali terminal process is killed and well I have to start over again. Not sure if it's Kali itself or even a kernel/OOS issue. Overall though, it is functional and in very early development stages. So I'm sure it only gets better from here.
Click to expand...
Click to collapse
Okay cool, thank you for your response. Looks Like I will be back on android after years of being an iPhone user.
Where are the commits for Kali that you added to the holyangel kernel? I would like to see what changed.
Sent from my ONEPLUS A6013 using Tapatalk
ecera said:
I'm currently on OOS Ob4. As far as hiccups the kernel is smooth and battery life is actually really good. As far as nethunter itself? One thing I've noticed is that if I run a commands in the Kali terminal let's say airodump-ng and it's running. If for whatever reason my screen times out and turns off for a bit, or even if I switch to another screen real quick to check something. I've noticed that many times the Kali terminal process is killed and well I have to start over again. Not sure if it's Kali itself or even a kernel/OOS issue. Overall though, it is functional and in very early development stages. So I'm sure it only gets better from here.
Click to expand...
Click to collapse
Not a big issue, remove nethunter terminal from battery optimization, faced this in my op2 and it took me almost one week to figure out this ****ty reason, btw still using op2
awesome work bro, looking forward to your continued development on this project!
I am yet to see Nethunter work properly on a A/B device. Can you either post a Guide to Nethunter Installation guide in this Thread or create another thread under OP6T Guides???
AndroidDevices said:
I am yet to see Nethunter work properly on a A/B device. Can you either post a Guide to Nethunter Installation guide in this Thread or create another thread under OP6T Guides???
Click to expand...
Click to collapse
Video tutorial：
https://youtu.be/lOZSHSiQSWI
yzsroot said:
Video tutorial：
https://youtu.be/lOZSHSiQSWI
Click to expand...
Click to collapse
Would be nice if it was in English!
It's unfortunate that you will discontinue the project. Looked promising. :crying: I hope you change your mind and continue working on it.
I hope you reconsider your decision to discontinue this project, you brought something really important to the community and we are all grateful for it. I hope you can rise above those who made you feel that way because they're jealous and continue this project.
I also hope you think about it again when emotions settle. If you continue your development there will be many grateful users, as there already are, for sure! You did not promise to make no mistakes, you did not promise to be a perfect developer, you just tried to share your work and thats totally fine, if not even so crucial for the XDA community. You seem like someone who is still learning and growing on his efforts and thats great, XDA really needs people like you. Of course, one should always be open for constructive criticism, but you really dont have to justify yourself for anything. Degredation and making fun of your work isn't constructive, of course. Those two do definitely not belong here and it's sad to see that happening.
So anyone able to do a COMPLETE installation of Kali Nethunter on ANY A/B Device Successfully yet? I tried on OG Pixel XL, Pixel 2 XL, OP6, OP6t, Moto Z2 Force, etc, etc... English Instructions would be greatly appreciated!
I want to express how grateful I am that you even undertook this project. I am a net/data security consultant and I use various tools/OS's etc in my profession, and have used nethunter (still do) on my nexus 6. I hope you reconsider your choice to give up on the development. Most people that comment here, or anywhere on the internet, are uninformed, ignorant, and uneducated. It's individuals like you that provide a much needed service to the scene, and even if you do not decide to continue development, I greatly appreciate the effort you put into it thus far bro.
Does anyone know of anyone porting Lineage over to the Razer Phone 2?
Punk_Oll said:
Does anyone know of anyone porting Lineage over to the Razer Phone 2?
Click to expand...
Click to collapse
Not to my knowledge
I am syncing source now. I just got this phone and I am no well known developer or anything but I did help port cm in the past to different devices and would love to get it working on this phone. I will hopefully have a build up this week.
jcole20 said:
I am syncing source now. I just got this phone and I am no well known developer or anything but I did help port cm in the past to different devices and would love to get it working on this phone. I will hopefully have a build up this week.
Click to expand...
Click to collapse
Great! Will it be los 16 or 17?
EMJI79 said:
Great! Will it be los 16 or 17?
Click to expand...
Click to collapse
So you always start with stable os and then try and get it working on future/newer releases once you have a stable build. Ideally it will be 16 but honestly it may have to start at 15 even. I'll know more once I get it to build. I am still trying to figure out why no one has done this already for this device. I've had no issues getting vanilla gsis running on this phone so it's odd that no one is developing unless I'm missing something obvious (I've been out of the loop with Android for a few years) or nobody who builds has the phone they opted for a one plus/Samsung/rog etc. I'm hoping the reason is that we just lack developers not that there's a hurdle I'm not aware of. I last built Android on KitKat so I've been trying to get caught up on the development and changes since then. Our hardware is almost identical to the note and there's a ton of devices with aosp builds that share our peripherals so the majority of the data is there from what I can see.
jcole20 said:
I am syncing source now. I just got this phone and I am no well known developer or anything but I did help port cm in the past to different devices and would love to get it working on this phone. I will hopefully have a build up this week.
Click to expand...
Click to collapse
Thanks a lot for effort bro we are waiting, great device but no developer for custom rom
:good: that's amazing
jcole20 said:
So you always start with stable os and then try and get it working on future/newer releases once you have a stable build. Ideally it will be 16 but honestly it may have to start at 15 even. I'll know more once I get it to build. I am still trying to figure out why no one has done this already for this device. I've had no issues getting vanilla gsis running on this phone so it's odd that no one is developing unless I'm missing something obvious (I've been out of the loop with Android for a few years) or nobody who builds has the phone they opted for a one plus/Samsung/rog etc. I'm hoping the reason is that we just lack developers not that there's a hurdle I'm not aware of. I last built Android on KitKat so I've been trying to get caught up on the development and changes since then. Our hardware is almost identical to the note and there's a ton of devices with aosp builds that share our peripherals so the majority of the data is there from what I can see.
Click to expand...
Click to collapse
Great to hear! Hope it goes well!
I too was wondering if it was just a matter of lack of developers considering Razer has released the sources for the device on their developer portal (Link if anyone wants to check it out)
And a question, will the built in Dolby Atmos be a possibility to port over to run in Lineage?
anything further on plans for this?
I'm going to be building myself soon I'll post if I'm successful I've only built for one other device before so we will see.
Anyone get anywhere with this?
Please someone create a telegram group for Razer 2.
keaheng said:
Please someone create a telegram group for Razer 2.
Click to expand...
Click to collapse
https://t.me/razer_phone
I'm also curious whatever happened with this. Did the devs run into a big roadblock?
I've heard nothing it's getting to the point where I think I'm going to sell this phone.
Punk_Oll said:
Does anyone know of anyone porting Lineage over to the Razer Phone 2?
Click to expand...
Click to collapse
Well I'm try to set up my environment and try and breakfast a 17.1 lineage.
It's really difficult to learn and do if I make any head way I promise to share.
If anyone has any help, like uploads to GitHub for the build pull for creating please let me know.
Punk_Oll said:
Well I'm try to set up my environment and try and breakfast a 17.1 lineage.
It's really difficult to learn and do if I make any head way I promise to share.
If anyone has any help, like uploads to GitHub for the build pull for creating please let me know.
Click to expand...
Click to collapse
Still trying but not making much headway
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.