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.
Related
I mostly work with Nexus 6, but since it is so easy to tack on the 5 as well....
Lets just say that this applies equally to Nexus 5 and should be *really* helpful...
http://forum.xda-developers.com/nexus-6/general/root-t3231211
One thing to be aware of... I haven't even tested to see if it boots and won't be able to until Sunday. I can't imagine why it wouldn't though, since the device specific patch is, literally, trivial (works on 6 and 9).
Bugs, features, etc., please use the issue trackers on my or phhusson's github projects, as it applies to the particular components.
doitright said:
I mostly work with Nexus 6, but since it is so easy to tack on the 5 as well....
Lets just say that this applies equally to Nexus 5 and should be *really* helpful...
http://forum.xda-developers.com/nexus-6/general/root-t3231211
One thing to be aware of... I haven't even tested to see if it boots and won't be able to until Sunday. I can't imagine why it wouldn't though, since the device specific patch is, literally, trivial (works on 6 and 9).
Bugs, features, etc., please use the issue trackers on my or phhusson's github projects, as it applies to the particular components.
Click to expand...
Click to collapse
This should be exciting i can't wait to see what comes of this! Good luck to you! :good:
navy676 said:
This should be exciting i can't wait to see what comes of this! Good luck to you! :good:
Click to expand...
Click to collapse
If you try it out, you can find out. I need testers to make sure that everything is working as it is expected to.
doitright said:
If you try it out, you can find out. I need testers to make sure that everything is working as it is expected to.
Click to expand...
Click to collapse
Good luck to your work
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
Hey guys! Just flashed the Android Q beta and have some thoughts:
First of all for some reason OnePlus removed navigation gestures, there isn't even the original OnePlus gestures. Common, that should have been easy to add.
Since OnePlus made the fingerprint work I assumed dash charging would work too, but this isn't the case.
I've seen people complain about not being heard on calls, but that works for me, the real problem is I can't send a text message, no matter what SMS app I use.
When fully powering off the phone it takes an absurd amount of time to shut down, it says "shutting down.." for a good 20 seconds.
Besides these issues everything works fine, I flashed TWRP and Magisk and will be trying this out, I hope they release some updates because as of now this isn't really usable as a daily driver.
Already a thread of Q here:
https://forum.xda-developers.com/oneplus-6t/how-to/oneplus-6t-androidq-beta-release-links-t3928174
peanutpajamas said:
Hey guys! Just flashed the Android Q beta and have some thoughts:
First of all for some reason OnePlus removed navigation gestures, there isn't even the original OnePlus gestures. Common, that should have been easy to add.
Since OnePlus made the fingerprint work I assumed dash charging would work too, but this isn't the case.
I've seen people complain about not being heard on calls, but that works for me, the real problem is I can't send a text message, no matter what SMS app I use.
When fully powering off the phone it takes an absurd amount of time to shut down, it says "shutting down.." for a good 20 seconds.
Besides these issues everything works fine, I flashed TWRP and Magisk and will be trying this out, I hope they release some updates because as of now this isn't really usable as a daily driver.
Click to expand...
Click to collapse
you can text if you send a screenshot or pic attached to it then the text goes through no matter what messaging app u use
bradhoschar said:
Already a thread of Q here:
https://forum.xda-developers.com/oneplus-6t/how-to/oneplus-6t-androidq-beta-release-links-t3928174
Click to expand...
Click to collapse
I thought that was just the links..
My thoughts are this sucks and op should be ashamed of themselves.they released a backport
This isn't meant as a daily driver [emoji19] it's not a beta build, it's a Dev build. Buggy as hell, no features, just a first try.
The only bad thing OnePlus did is releasing it to all because most users are to stupid to understand.
superiscch said:
The only bad thing OnePlus did is releasing it to all because most users are to stupid to understand.
Click to expand...
Click to collapse
This needs to be in bold with a size font of like 50.
For those of you in here complaining, that are too damn lazy to read, put some effort into reading this. Quoted from the release thread:
As the name suggests, this build of Android Q is best suited for developers and early adopters. As it is still in an early stage of development. That said, we do not recommend flashing this ROM if you have little to no experience in software development or flashing custom ROMs. Proceed at your own RISK!
Click to expand...
Click to collapse
superiscch said:
This isn't meant as a daily driver [emoji19] it's not a beta build, it's a Dev build. Buggy as hell, no features, just a first try.
The only bad thing OnePlus did is releasing it to all because most users are to stupid to understand.
Click to expand...
Click to collapse
I think your right to a certain extent, but I also feel like lately OnePlus hasn't been doing what they have become known for, oneplus users want fast updates to try out the latest of Android.
this build while intended for development was made with very little thought, most other OEMs on the list actually made it useable, take essential for example, yes there are a few bugs but it can send a text and doesn't crash when you click on auto brightness. Even though it was for "devs".
OnePlus could have definitely done a better job at this, very dissatisfied.
SpasilliumNexus said:
This needs to be in bold with a size font of like 50.
For those of you in here complaining, that are too damn lazy to read, put some effort into reading this. Quoted from the release thread:
Click to expand...
Click to collapse
No we are not too dumb to read and I understand how a " developer preview" works. I had 4 developer previews with P on my essential last year. Even the first two of that weren't very good but at least stable, especially if u or anyone have run or tried any of the Google gsi's or pixel Q gsi port of the last preview. What we are saying is why did they take away things that were already fixed and working and give us this crap. It's a slap to the face to release a less stable version than what is already out there. Me and protodevano made our own version of a Q ified vendor and in doing so could flash those said ROMs. This crap is clearly backwards movement and is the reason so many of us are irritated. It's not cuz we can't read or understand. OnePlus messed up and was late to the game and clearly hurried up with whatever dumb thing they could to catch up to the other oems and turn in something for the masses. Completely clueless everyone else would have more stable versions. That is fair to be annoyed at.
Lastly in regards to their last part. I probably have more experience in flashing, manipulating firmware, and dissecting, and decrypting all types of firmware
Than most people on the fajita threads.i wrote the book on gsi flashing with the essential. I fixed the volte issues for users. I made Oreo ROMs emulate pie for Shamu with rounded UI.. I'm the guy people look to when they would like to know if something is possible. I push the limits. This Q is not even possible to push anything with. And a piss poor representation. Don't make excuses if u didn't try any other Q ROMs before yesterday's OnePlus release.
fullofhell said:
No we are not too dumb to read and I understand how a " developer preview" works. I had 4 developer previews with P on my essential last year. Even the first two of that weren't very good but at least stable, especially if u or anyone have run or tried any of the Google gsi's or pixel Q gsi port of the last preview. What we are saying is why did they take away things that were already fixed and working and give us this crap. It's a slap to the face to release a less stable version than what is already out there. Me and protodevano made our own version of a Q ified vendor and in doing so could flash those said ROMs. This crap is clearly backwards movement and is the reason so many of us are irritated. It's not cuz we can't read or understand. OnePlus messed up and was late to the game and clearly hurried up with whatever dumb thing they could to catch up to the other oems and turn in something for the masses. Completely clueless everyone else would have more stable versions. That is fair to be annoyed at.
Lastly in regards to their last part. I probably have more experience in flashing, manipulating firmware, and dissecting, and decrypting all types of firmware
Than most people on the fajita threads.i wrote the book on gsi flashing with the essential. I fixed the volte issues for users. I made Oreo ROMs emulate pie for Shamu with rounded UI.. I'm the guy people look to when they would like to know if something is possible. I push the limits. This Q is not even possible to push anything with. And a piss poor representation. Don't make excuses if u didn't try any other Q ROMs before yesterday's OnePlus release.
Click to expand...
Click to collapse
Don't argue with fanboys.
They can't see beyond OnePlus is best shyte..
If anyone want to see a video or a quick look than check this
https://youtu.be/Yhw6463pTPg
-snip-
PatrickLoewer said:
Has someone problems going back to custom roms?
I downgraded to the Pie Image linked in the OnePlus Android Q official post. This is working fine, i can boot and flash TWRP as well, but as soon as i install any room i go straight back to "Qualcom CrashDump Mode".
Tried the original fastboot partitions from "rom-stock-fastboot-roms-oneplus-6t" aswell, those are working fine for me as well. But soon as i flash any custom rom (tried 3 different ones) i go straight into the "Qualcom CrashDump Mode" (fastboot is no longer working after that so i have to use the MSM Tool to restore the phone).
Tried dirty flashing or a complete clean flash (wiping all partitions except Internal Storage) both result in the same Qualcom Crash screen.
Using the MSM Tool gets me a working Pie everytime, also using the original fastboot rooms works as well, it's only custom roms .... (tried with and without flashing magisk/opengapps)
Edit: International Version, no T-Mobile or McLaren Edition
Click to expand...
Click to collapse
It's cuz u still have one slot Q. When u install a rom it goes to that slot. From a booted up os, reboot to twrp, flash the pie downgrade zip again, then format, u should be good.or the quicker route would be use msm
fullofhell said:
It's cuz u still have one slot Q. When u install a rom it goes to that slot. From a booted up os, reboot to twrp, flash the pie downgrade zip again, then format, u should be good.or the quicker route would be use msm
Click to expand...
Click to collapse
Was not the problem, but the MSM Tool didn't worked with the version i had.
indian84 said:
Don't argue with fanboys.
They can't see beyond OnePlus is best shyte..
Click to expand...
Click to collapse
Cute attempt at the assumption, but you're far from getting that one right. Try again.
SpasilliumNexus said:
Cute attempt at the assumption, but you're far from getting that one right. Try again.
Click to expand...
Click to collapse
Burnnnnn
fullofhell said:
--WoT--
Click to expand...
Click to collapse
No matter how buggy or broken they are, they are meant for developers to adapt software and hardware on them before final builds are out to the general public. Not for randoms to treat them as finals, as few here and a lot on the OP forums have done.
I just rebooted the phone. It says to enter in a PIN and none of the PINS that I normally use work. What are my options now that I can't get past the PIN setup to start Android?
Xpiatio said:
I just rebooted the phone. It says to enter in a PIN and none of the PINS that I normally use work. What are my options now that I can't get past the PIN setup to start Android?
Click to expand...
Click to collapse
Fairly sure you have to wipe and not choose "secure startup" (or similar) in the set up. That feature (encryption) is not working currently.
They could make a PRE-Alpha build, say DO NOT INSTALL THIS, and zillions of lDIOTS would download it because they want the latest update, no matter what, THEN, will get on here, OP's website and other places to complain about it.
It's like these clowns hanging out windows, rail cars and what not to get a selfie so they can get "likes"....lDIOTS
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.