[ROM] [Work in Progress] [Mantis] LineageOS 14.1 for Fire TV Stick 4K - Fire TV Original Android Development

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.

Related

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

[Request] Hardening AOKP security?

Dear Developers of AOKP,
first of all: Thank you so much for this awesome ROM which I am using since 3 years by now! Since security has been in the media periodically for quite some time now, I feel like this is the right time to ask: Would you please harden AOKP to include the very latest security enhancements? What bothers me in particular is that it seems even though so much development is being done, vulnerabilities like Mempodroid still seem to be present in the latest builds (using AOKP 4.4.2 for M7UL). A good way to check this is to use the X-RAY Security Scanner. Please fix these vulnerabilities.
Furthermore, would you please implement a feature to toggle hardening like triggered with the app SecDroid? This neat little project unfortunately has been abandoned, but yet the idea should be clear. The developer of SecDroid also released a Guide on how to harden Android. Maybe AOKP can use the Source of SecDroid somehow?
For me, AOKP always will be the best ROM out there. I can proudly say that having donated to the project makes me feel great and I'm looking foward to see AOKP implementing the latest and greatest security enhancements out there. Thank you ahead!
SecUpwN said:
Dear Developers of AOKP,
first of all: Thank you so much for this awesome ROM which I am using since 3 years by now! Since security has been in the media periodically for quite some time now, I feel like this is the right time to ask: Would you please harden AOKP to include the very latest security enhancements? What bothers me in particular is that it seems even though so much development is being done, vulnerabilities like Mempodroid still seem to be present in the latest builds (using AOKP 4.4.2 for M7UL). A good way to check this is to use the X-RAY Security Scanner. Please fix these vulnerabilities.
Furthermore, would you please implement a feature to toggle hardening like triggered with the app SecDroid? This neat little project unfortunately has been abandoned, but yet the idea should be clear. The developer of SecDroid also released a Guide on how to harden Android. Maybe AOKP can use the Source of SecDroid somehow?
For me, AOKP always will be the best ROM out there. I can proudly say that having donated to the project makes me feel great and I'm looking foward to see AOKP implementing the latest and greatest security enhancements out there. Thank you ahead!
Click to expand...
Click to collapse
A few of us are interested in this and we'll see what can be done
BytecodeMe said:
A few of us are interested in this and we'll see what can be done
Click to expand...
Click to collapse
Awesome! What are you planning to do?
SecUpwN said:
Dear Developers of AOKP,
first of all: Thank you so much for this awesome ROM which I am using since 3 years by now! Since security has been in the media periodically for quite some time now, I feel like this is the right time to ask: Would you please harden AOKP to include the very latest security enhancements? What bothers me in particular is that it seems even though so much development is being done, vulnerabilities like Mempodroid still seem to be present in the latest builds (using AOKP 4.4.2 for M7UL). A good way to check this is to use the X-RAY Security Scanner. Please fix these vulnerabilities.
Furthermore, would you please implement a feature to toggle hardening like triggered with the app SecDroid? This neat little project unfortunately has been abandoned, but yet the idea should be clear. The developer of SecDroid also released a Guide on how to harden Android. Maybe AOKP can use the Source of SecDroid somehow?
For me, AOKP always will be the best ROM out there. I can proudly say that having donated to the project makes me feel great and I'm looking foward to see AOKP implementing the latest and greatest security enhancements out there. Thank you ahead!
Click to expand...
Click to collapse
Even if every vulnerability fix was included in source, (for now) it will still not be secured. Unless you compile your own builds with a different platform key, your builds will not be secure. This applies to nearly every AOSP-based custom ROM.
We've talked about it, and we might implement something for milestone releases. But security is a huge huge problem to take on with custom ROMs and there are a lot of heads to the dragon to take down
Sent from my HTC One using Tapatalk
Romanbb said:
We've talked about it, and we might implement something for milestone releases. But security is a huge huge problem to take on with custom ROMs and there are a lot of heads to the dragon to take down.
Click to expand...
Click to collapse
True point. But I'm sure that folks who can add unicorn sparkles to a ROM will even discover and implement some really cool security enhancements & fixes for the already known vulnerabilities. After all, this is a suggestion and to be seen without pressure. Waiting for your next awesome release for M7UL, @Romanbb! You're doing a great job!
SecUpwN said:
True point. But I'm sure that folks who can add unicorn sparkles to a ROM will even discover and implement some really cool security enhancements & fixes for vulnerabilities. After all, this is a suggestion and to be seen without pressure. Waiting for your next awesome release for M7UL, @Romanbb!
Click to expand...
Click to collapse
For sure. I'm definitely not against security enhancements by any measure.
Why isn't it possible to create a tool that can repackage ROMs with custom keys, say, using a Windows computer or Xposed Framework?
Also, isn't Mempodroid what allows us to give apps SU permission?
pan.droid said:
Also, isn't Mempodroid what allows us to give apps SU permission?
Click to expand...
Click to collapse
No. Mempodroid is an EXPLOIT and a vulnerability, please don't mistaken it with SuperSU.
SecUpwN said:
please don't mistaken it with SuperSU.
Click to expand...
Click to collapse
Okay. Just so long as you don't *mistake* 'SU' with SuperSU=)
AOKP Kitkat Rom
The Android Open Kang Project (AOKP) team has released nightly builds for a number of Android running device which bring Android 4.4.2 KitKat update for these devices. One such build is also available for Sony Xperia Z, which runs Android 4.3 Jelly Bean.
gteknet said:
The Android Open Kang Project (AOKP) team has released nightly builds for a number of Android running device which bring Android 4.4.2 KitKat update for these devices.
Click to expand...
Click to collapse
As you might have guessed, AOKP runs through all my veins. I'd probebly never use anything else, if not forced to. As soon as a new nightly is out, I'm using it. But what exactly is the AOKP team doing to make their build more secure?
One of the features that I'd LOVE to have would be encrypted calls between AOKP builds without having to be online or installing additional software. Would such be possible somehow?
Thread cleaned
I suggest several members use the ignore user option if they want to remain members on XDA
I will be keeping an eye on posting. Cut out the infantile crap or you will be removed
This is a development site, take your garbage to a social media site
Senior Moderator
@kennyglass123, thanks for cleaning it up. I really appreciate your effort. Unfortunately though, no member of the AOKP team has answered my initial question yet. Could someone please do so?
SecUpwN said:
As you might have guessed, AOKP runs through all my veins. I'd probebly never use anything else, if not forced to. As soon as a new nightly is out, I'm using it. But what exactly is the AOKP team doing to make their build more secure?
Click to expand...
Click to collapse
Sadly, this question is still open. Since I'm using M7 (Gerneric GSM), maybe @Whitehawkx can answer this?

Developer Support

Just wondering what other developers have decided or shown interest in grabbing a OnePlus 3. I am thinking of getting one, but the cost is a bit steep to just support a device that I may not even use as a daily device. If there is a small amount of developers, I will be more likely to get one because I believe that users deserve to use their phone how they want, not how the OEM wants them to. This is more or less a roll call to see who will be supporting the device from a dev standpoint.
read something about
- Grarak already release unofficial CM13
- martin from Ground zero roms, finished tipsy but not having the phone yet
- paranoid android should bring out rom in next couple of days (new team)
Dinjesk said:
read something about
- Grarak already release unofficial CM13
- martin from Ground zero roms, finished tipsy but not having the phone yet
- paranoid android should bring out rom in next couple of days (new team)
Click to expand...
Click to collapse
Anyone kernel side?
DespairFactor said:
Anyone kernel side?
Click to expand...
Click to collapse
untill so far i have only seen or heard about @haikalizz
doubting @Boeffla will consider as he is taking kernel development a notch down.
Dinjesk said:
untill so far i have only seen or heard about @haikalizz
doubting @Boeffla will consider as he is taking kernel development a notch down.
Click to expand...
Click to collapse
I am considering it, I have plans to bring kexec hardboot to the device if I get it
DespairFactor said:
I am considering it, I have plans to bring kexec hardboot to the device if I get it
Click to expand...
Click to collapse
Yes, please consider - early adopters will lure more and more devs for sure.
And OP is dev-friendly too (according to the OP - you won't void your warranty by flashing custom ROMs/Kernels).
I was fully surprised to see the first unofficial CM13 ROM from Grarak one hour after the announcement yesterday
_PrEzi_ said:
Yes, please consider - early adopters will lure more and more devs for sure.
And OP is dev-friendly too (according to the OP - you won't void your warranty by flashing custom ROMs/Kernels).
I was fully surprised to see the first unofficial CM13 ROM from Grarak one hour after the announcement yesterday
Click to expand...
Click to collapse
My problem is the price point still for a device that I I'll likely be supporting to ensure users get what they want rather than using it as a daily driver for a while. I support several Nexus devices and have done a bit on each OnePlus device in the past. I just want it to be a feasible purchase considering how large my support roster is already.
DespairFactor said:
My problem is the price point still for a device that I I'll likely be supporting to ensure users get what they want rather than using it as a daily driver for a while. I support several Nexus devices and have done a bit on each OnePlus device in the past. I just want it to be a feasible purchase considering how large my support roster is already.
Click to expand...
Click to collapse
I can perfectly understand that. You - like me - do like to do things either perfectly or at least v. good or better leave them be if they are only 'ok'.
Nevertheless - please do consider. I am not promising anything but my guts tell me OP3 will have a larger userbase than the OP2.
And again - no promises - but I like beer and also like to send 'virtual beer/pizzas' to the devs I feel are putting big efforts to keep the users happy. Probably other humble users too :highfive:
Would be killer to have you onboard.
Yes come on board. I like your kernel.
Gesendet von meinem Nexus 6P mit Tapatalk
DespairFactor said:
I am considering it, I have plans to bring kexec hardboot to the device if I get it
Click to expand...
Click to collapse
Do you intend to bring Ubermallow/Uberstock to OP3 as well?If your answer is yes, I'm ordering this phone right away.
Sent from my Nexus 5X using XDA-Developers mobile app
To be honest, I'm pretty sure that this device will attract a lot of devs, both kernel and rom wise. So while I'd love to have the dark side on board, you shouldn't stress your budget when you're not planning to use the phone. Just my $0.02.
gururoop said:
Do you intend to bring Ubermallow/Uberstock to OP3 as well?If your answer is yes, I'm ordering this phone right away.
Sent from my Nexus 5X using XDA-Developers mobile app
Click to expand...
Click to collapse
derdjango said:
To be honest, I'm pretty sure that this device will attract a lot of devs, both kernel and rom wise. So while I'd love to have the dark side on board, you shouldn't stress your budget when you're not planning to use the phone. Just my $0.02.
Click to expand...
Click to collapse
inzaghi75 said:
Yes come on board. I like your kernel.
Gesendet von meinem Nexus 6P mit Tapatalk
Click to expand...
Click to collapse
For right now I will blind build a kernel and try to get kexec working. If I somehow get the budget to grab one, I will. I hear there is a BrokenOS coming, but do not ask anyone about it, just wait for a release. I will not bring UBER ROMs to this device because we do not run CAF based sources.
OFFICIAL BeanStalk ROM and Temasek is comming on Saturday by me
Regards,
Taker
Taker18 said:
OFFICIAL BeanStalk ROM and Temasek is comming on Saturday by me
Regards,
Taker
Click to expand...
Click to collapse
Just a friendly request, please keep on One rom and maintain it well. I am sure that many devs will come for OP3 because of its open nature and having a unofficial port of their rom might discourage them. So, please, focus on quality rather than quantity. I don't doubt that you can maintain 2 roms. But, as you are more with Beanstalk, please continue with it. You can go for maintaining more roms one source for custom roms gets stable and no dev from a particular rom comes. Don't take it wrong but just a friendly request.
Thanks.
And BTW, better if you maintain only for the devices you have. And if you are maintaining for a device you don't even have, maintaining more than 1 rom for it becomes too weird and not good for the device users as you won't be able to contribute much to device specific stuff that way. So, if you don't own device, for now, it will be better if you just maintain one rom at max so that some developer who owns device can maintain and he doesn't get discouraged (happened with op2 and happens with opx too)
Sent from my OnePlus2 using XDA Labs
Naman Bhalla said:
Just a friendly request, please keep on One rom and maintain it well. I am sure that many devs will come for OP3 because of its open nature and having a unofficial port of their rom might discourage them. So, please, focus on quality rather than quantity. I don't doubt that you can maintain 2 roms. But, as you are more with Beanstalk, please continue with it. You can go for maintaining more roms one source for custom roms gets stable and no dev from a particular rom comes. Don't take it wrong but just a friendly request.
Thanks.
And BTW, better if you maintain only for the devices you have. And if you are maintaining for a device you don't even have, maintaining more than 1 rom for it becomes too weird and not good for the device users as you won't be able to contribute much to device specific stuff that way. So, if you don't own device, for now, it will be better if you just maintain one rom at max so that some developer who owns device can maintain and he doesn't get discouraged (happened with op2 and happens with opx too)
Sent from my OnePlus2 using XDA Labs
Click to expand...
Click to collapse
I agree, it is hard to maintain several projects at once for one device, let alone a few. IIRC, a lot of you come across from other OP devices too, not sure if you are dropping support on previous devices.
Well, I'm too working on a kernel for this phone (albeit don't have device)
Sent from my Moto X using Tapatalk
##W4TCH0UT## said:
Well, I'm too working on a kernel for this phone (albeit don't have device)
Click to expand...
Click to collapse
Good. Though I think for better support to users, one, especially a kernel developer, must have the device. Users can't always get the best of bug reports and it becomes a lot hectic to support devices (like it happened on OP2 ) Infact, it doesn't give a good pressing on a developer's image to be honest. Take your decision but believe me, it will be better if you get the device and maintain.
Thanks.
Best Regards
Sent from my OnePlus2 using XDA Labs
Naman Bhalla said:
Good. Though I think for better support to users, one, especially a kernel developer, must have the device. Users can't always get the best of bug reports and it becomes a lot hectic to support devices (like it happened on OP2 ) Infact, it doesn't give a good pressing on a developer's image to be honest. Take your decision but believe me, it will be better if you get the device and maintain.
Thanks.
Best Regards
Sent from my OnePlus2 using XDA Labs
Click to expand...
Click to collapse
OnePlus 2, was a bad device, I actually had it, they just did a poor job, but either way, if you don't want my support that's fine as well.
DespairFactor said:
OnePlus 2, was a bad device, I actually had it, they just did a poor job, but either way, if you don't want my support that's fine as well.
Click to expand...
Click to collapse
I think you know me. Remember me from one group we created ? I think of you can get a device, do support it. Infact, in one way, people support of you support them. So, get a device, support the device and a lot chances are that people will support you and you might be able to overcome all expenditures on the device. And believe me, many devs told me this too. And I know your kernel from 6P. Will be great if you can support, and prolly you *might* have a surprise too (I am not saying anything, but, well) . We do need your support, but it will be best if you can support when you have a device too. It will generate people's trust upon you and also you won't need to get with wrong bug reports.
Sent from my OnePlus2 using XDA Labs

Lineage OS???

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

Question Why no custom ROMs yet?

Hello,
I've been missing for quite a long time from XDA, but I'm about to get a new phone soon (maybe another OnePlus?) and I came here to check for new custom ROMs updates.
But it seems I cannot find any custom ROM for the OnePlus 10 Pro (yet?), why is that?
Thanks for the info.
No msm unbrick tool, no sources and so on.
Oneplus sucks every phone a little bit more! 10 pro is definitely my last OP phone
You can try GSI roms, but they're buggy (e.g. fingerprint sensor is not working)
Also you cannot unbrick your phone unless you send it to 1+ which makes development hard
Source tree is different default compilable sources.i hope someone could port it.
All of the above! Everything is different now a days with "all" OEM's, Google, Carrier's, etc.
But if some motivated Developers get the device, then who knows what mods will come our way....
Also, Magisk Modules are the modding wave !
Cheers
galaxys said:
All of the above! Everything is different now a days with "all" OEM's, Google, Carrier's, etc.
But if some motivated Developers get the device, then who knows what mods will come our way....
Also, Magisk Modules are the modding wave !
Cheers
Click to expand...
Click to collapse
What mods are you using mate?
There are already custom ROM for Xiaomi 12/Pro which also use Snapdragon 8 gen 1 so maybe there's luck but OnePlus sources are lacking and I asked Luke1337 and he is not interested in blind building since he ain't got the device.
See a my reply to other post on oneplus 10 pro
ectoplasma22 said:
There are already custom ROM for Xiaomi 12/Pro which also use Snapdragon 8 gen 1 so maybe there's luck but OnePlus sources are lacking and I asked Luke1337 and he is not interested in blind building since he ain't got the device.
Click to expand...
Click to collapse
İ can't found it .could u share for me .it has same tree our devices i could work it.
metrixx02 said:
İ can't found it .could u share for me .it has same tree our devices i could work it.
Click to expand...
Click to collapse
There's a telegram group, check the pinned posts
Xiaomi 12 | OFFICIAL
Xiaomi 12 Official Group • English only chat • Read Rules ( /rules ) • Channel : @Xiaomi12GlobalUpdates • Photography group : @Xiaomi12GlobalPhotography • Off-Topic Group : @PocoOffTopic • Customization Group : @PocophoneCustomization
t.me
I've found this: https://github.com/OnePlusOSS/android_kernel_msm-5.10_oneplus_sm8450
And this: https://github.com/OnePlusOSS/android_kernel_modules_and_devicetree_oneplus_sm8450
But, sadly, I've also read this post: https://forum.xda-developers.com/t/how-not-to-guide.4458091/post-87108519
It's truly a sad time to be an android user....
But i've got a little thought in the back of my head that i can't shake, i think things will change.
No idea how it'll happen, may take a while, maybe after the release of the T / R 10 devices.
Time will tell, but yep it's certainly a crap time for Android; when a google flagship and oneplus devices don't have a single official ROM (pixel has AOSP unofficial afaik) it's time to re-evaluate your purchases a lot more carefully.
dladz said:
It's truly a sad time to be an android user....
But i've got a little thought in the back of my head that i can't shake, i think things will change.
No idea how it'll happen, may take a while, maybe after the release of the T / R 10 devices.
Time will tell, but yep it's certainly a crap time for Android; when a google flagship and oneplus devices don't have a single official ROM (pixel has AOSP unofficial afaik) it's time to re-evaluate your purchases a lot more carefully.
Click to expand...
Click to collapse
Yeah, I remember the old times here on XDA, there was so many threads proposing many different flavors.
I used to flash and try new ROMs almost everyday...
Now I have to get a new phone, I came here to check and I've realized it all changed.
It's even hard to find ROMs for Google Pixels and OnePlus phones, I don't know what happened but it's kinda frustrating...
Guys just relax and give some time for developers.good news for sm8450 chipset is someone ported device and vendor tree for Xiaomi phones.i hope not far our phones .just relax.
metrixx02 said:
Guys just relax and give some time for developers.good news for sm8450 chipset is someone ported device and vendor tree for Xiaomi phones.i hope not far our phones .just relax.
Click to expand...
Click to collapse
Honestly mate, I've had enough phones to know that it should have happened by now.
I'm very patient, no problem in waiting, but every single OnePlus device has had several ROMs by this point bar none
metrixx02 said:
Guys just relax and give some time for developers.good news for sm8450 chipset is someone ported device and vendor tree for Xiaomi phones.i hope not far our phones .just relax.
Click to expand...
Click to collapse
Don't worry, we are just talking and comforting each other...
But well, I remember ROMs used to be posted here (almost) even before phones were available to be bought.
And since it seems that Google Pixels too lack of ROMs, I have a feelings things has changed lately somehow... but we all hope you are right man!
Why do you need google roms? are they better?
Otherwise it finds 2-3 threads about to change to global or EU version.
But that is not you want?
lorenx said:
Don't worry, we are just talking and comforting each other...
But well, I remember ROMs used to be posted here (almost) even before phones were available to be bought.
And since it seems that Google Pixels too lack of ROMs, I have a feelings things has changed lately somehow... but we all hope you are right man!
Click to expand...
Click to collapse
Google has made a lot of changes to the OS that just make everything a headache for custom ROM devs so that's not helping. The writing is on the wall for the Android ROM community and once Google finally forces hardware attestation the inability to easily hide root or unlocked bootloaders at all will kill off a lot more interest. The future of mobile phones is one of two separate walled gardens.
EtherealRemnant said:
Google has made a lot of changes to the OS that just make everything a headache for custom ROM devs so that's not helping. The writing is on the wall for the Android ROM community and once Google finally forces hardware attestation the inability to easily hide root or unlocked bootloaders at all will kill off a lot more interest. The future of mobile phones is one of two separate walled gardens.
Click to expand...
Click to collapse
The only issue is erofs partitions. Everything else can be edited to change values. Maybe devs will have to find a way to make the rw. That's the issue I see for the future. But pa said they made a build with erofs for op7 so maybe they are looking into it.
toolhas4degrees said:
The only issue is erofs partitions. Everything else can be edited to change values. Maybe devs will have to find a way to make the rw. That's the issue I see for the future. But pa said they made a build with erofs for op7 so maybe they are looking into it.
Click to expand...
Click to collapse
There's also the fact that A/B partitions lead to plenty of bricks and the devs get blamed for it plus the issues that come with AVB 2.0, manufacturers not releasing full kernel sources... It's all a circus.

Categories

Resources