Dirty Unicorns Oreo ROM (v12) is entering RC2 status. It would be awesome if someone would step forward to be a Marlin maintainer for DU. I think the Nougat maintainer moved on to another device.
I'd try it myself if I had any free time and the knowledge to build and tune it.
Just throwing it out there.
DU don't want their rom being discussed on XDA I think maybe better to talk about it on their G+ Page. They have a maintainer for Pixel XL, Oreo Branches are their so work is been done on this device. The first wave of RC's was the devices that were ready at the time more will come :good:
Sorry. I wasn't aware of the secrecy / isolation from XDA.
I was probably also looking in the wrong area of github as I didn't see any new Marlin commits.
liam_davenport said:
DU don't want their rom being discussed on XDA I think maybe better to talk about it on their G+ Page. They have a maintainer for Pixel XL, Oreo Branches are their so work is been done on this device. The first wave of RC's was the devices that were ready at the time more will come :good:
Click to expand...
Click to collapse
I thought discussion was fine, but no spreading their work around the forum. Is that wrong?
And do they really have an P-XL maintainer? Last I checked Marlin and Sailfish were not supported devices anymore.
uodii said:
I thought discussion was fine, but no spreading their work around the forum. Is that wrong?
And do they really have an P-XL maintainer? Last I checked Marlin and Sailfish were not supported devices anymore.
Click to expand...
Click to collapse
Discussion maybe allowed I could be wrong. They dropped Marlin? I didn't see a post about that
liam_davenport said:
Discussion maybe allowed I could be wrong. They dropped Marlin? I didn't see a post about that
Click to expand...
Click to collapse
https://docs.google.com/document/d/1XgpWBV4zTo51EPDPyZvT6FB46Cpzv5p4Trby8RmYid8/edit?usp=drivesdk
I was gonna do a private sailfish build, but noticed the marlin tree looked very outdated and I'm no good with GitHub. At this time I can just repo sync and build. So it's above my pay grade at the moment.
If posting this link is against the rules the post in general can just be deleted
uodii said:
https://docs.google.com/document/d/1XgpWBV4zTo51EPDPyZvT6FB46Cpzv5p4Trby8RmYid8/edit?usp=drivesdk
I was gonna do a private sailfish build, but noticed the marlin tree looked very outdated and I'm no good with GitHub. At this time I can just repo sync and build. So it's above my pay grade at the moment.
If posting this link is against the rules the post in general can just be deleted
Click to expand...
Click to collapse
Ahh that sucks guy I won't be buying Google Phones anymore thx for the confirmation :good:
I hadn't seen that list. Well that ends that wait for me. Time to see which of the current ROM offerings comes closest as I've gotten used to DU Nougat on my XL.
liam_davenport said:
Discussion maybe allowed I could be wrong. They dropped Marlin? I didn't see a post about that
Click to expand...
Click to collapse
Yes they did, the maintainer got a pixel 2 xl and gave his Marlin to his wife
No longer supported. Which is fine the "creator" of Dirty Unicorns is a giant douchebag anyways. I prefer to support devs who aren't huge pricks.
Hopefully someone would be willing to build some unofficial roms. If I wasn't a total noob at this I would do it
Their official Twitter account tweeted me this, so I think we should stay optimistic about an Oreo DU Rom.
https://twitter.com/_DirtyUnicorns_/status/951823267588968448?s=17
117micc said:
Their official Twitter account tweeted me this, so I think we should stay optimistic about an Oreo DU Rom.
https://twitter.com/_DirtyUnicorns_/status/951823267588968448?s=17
Click to expand...
Click to collapse
I hope it comes to pass
Been checking everyday seen a aosip and screwd build also they are oreo but earlier releases. I did build du but was early wip and havent built sice i might do a build this weekend. I since moved from moto devices to pixel see how it goes partitions are a pain
joeeboogz said:
Been checking everyday seen a aosip and screwd build also they are oreo but earlier releases. I did build du but was early wip and havent built sice i might do a build this weekend. I since moved from moto devices to pixel see how it goes partitions are a pain
Click to expand...
Click to collapse
Please build DU would be awesome if you can. Thank you
joeeboogz said:
Been checking everyday seen a aosip and screwd build also they are oreo but earlier releases. I did build du but was early wip and havent built sice i might do a build this weekend. I since moved from moto devices to pixel see how it goes partitions are a pain
Click to expand...
Click to collapse
Would be sweet if a AOSIP room dropped for the Pixel XL
epikroms said:
Would be sweet if a AOSIP room dropped for the Pixel XL
Click to expand...
Click to collapse
It's in the works :good:
liam_davenport said:
It's in the works :good:
Click to expand...
Click to collapse
Good to hear. Is Mikey Criggs with you on that one or are you porting it over?
I saw this today! It's happening!
Sent from my Pixel XL using Tapatalk
Edit: won't let me upload picture, I saw on the du official Google+ that have a working du v12. It's bootable, but still being worked on
RR is a lot better
Related
Okay, so after no updates for a month and no sign of any sign of AOSP for the Note 3, I have decided to take things into my own hands. Or so I would like to believe. The problem? I have never built AOSP or Cyanogenmod before, let alone for a device that isn't even supported. So I was hoping the wonderful XDA community could help me out.
The only thing I really can't figure out is how to build CM/AOSP for an unsupported device using a device tree. Someone posted this tree on Github a month ago - https://github.com/OUDhs/android_device_samsung_hltetmo
Then there is a Cyanogenmod kernel for just regular hlte (not hltetmo), posted 10 days ago - https://github.com/CyanogenMod/android_kernel_samsung_hlte
And then there are blobs for mi5 (not mi7), posted 2 days ago - https://github.com/DoItForTheRatchets/vendor_hlte
So my questions are:
Are these any indication of progress on AOSP for the Note 3?
Can I/anyone build CM/AOSP from these for the hltetmo.
I know people have gotten CM on the Note 3; we have all seen the blurry pic one, but here is someone else on October 24th - https://plus.google.com/u/0/+TonyLayher/posts/A4J8eRH8Rht
gakio12 said:
Okay, so after no updates for a month and no sign of any sign of AOSP for the Note 3, I have decided to take things into my own hands. Or so I would like to believe. The problem? I have never built AOSP or Cyanogenmod before, let alone for a device that isn't even supported. So I was hoping the wonderful XDA community could help me out.
The only thing I really can't figure out is how to build CM/AOSP for an unsupported device using a device tree. Someone posted this tree on Github a month ago - https://github.com/OUDhs/android_device_samsung_hltetmo
Then there is a Cyanogenmod kernel for just regular hlte (not hltetmo), posted 10 days ago - https://github.com/CyanogenMod/android_kernel_samsung_hlte
And then there are blobs for mi5 (not mi7), posted 2 days ago - https://github.com/DoItForTheRatchets/vendor_hlte
So my questions are:
Are these any indication of progress on AOSP for the Note 3?
Can I/anyone build CM/AOSP from these for the hltetmo.
I know people have gotten CM on the Note 3; we have all seen the blurry pic one, but here is someone else on October 24th - https://plus.google.com/u/0/+TonyLayher/posts/A4J8eRH8Rht
Click to expand...
Click to collapse
It looks like it's progress or at least people are tinkering around with it. However, you would need a full tree for the device if you wanted to build it from source, know enough to get your own tree, or be able to fork from other device tree's to get something going. The new Nexus has the same chip so that may make things quicker with getting a full working device tree. I'm just quoting based on my own understanding of things, so please correct me if I'm wrong.
I've been wanting to know the same. I've built AOSP ROMs before (namely AOKP for my Note 1 pulling from CM's device tree) and would do the same if the files were available for the Note 3. A few devs have teased the community with screenshots, but until they post their code a tease and a cruel joke is all that it is. I really wish these devs would put their source code up even if it is incomplete and let the community at large get this thing in gear since obviously they can't do it fast enough single-handedly. Holding back code until it's "ready" defeats the entire purpose of open source development in the first place! We have the kernel but no one has a full device tree out yet, only a limited one for recovery purposes (mainly the TeamWin one from TWRP).
Any updates on cm10 or cm11 for the note 3
Sent from my SM-N900T
Within hours of any (usable) device tree updates you'll see an explosion of new CM-based firmwares in the Dev sections.
I'll be building BeanStalk for hltetmo, probably 100 ppl will upload unofficial CM 11, it'll be a giant party for all.
CrashTestDroid said:
Within hours of any device tree updates you'll see an explosion of new CM-based firmwares in the Dev sections.
I'll be building BeanStalk for hltetmo, probably 100 ppl will upload unofficial CM 11, it'll be a giant party for all.
Click to expand...
Click to collapse
Sooo... When's this party begin? :angel::fingers-crossed:
Can't wait for this
Sent from my SM-N900T using Tapatalk
Me neither even got rid of my note and went with n5 cause I couldn't wait but im back tk the beast just need cm
Sent from my SM-N900T
Ker~Man said:
Sooo... When's this party begin? :angel::fingers-crossed:
Click to expand...
Click to collapse
When a hlte device tree is buildable, looks like CM is making additions and others like nikkdotcom
gakio12 said:
Okay, so after no updates for a month and no sign of any sign of AOSP for the Note 3, I have decided to take things into my own hands. Or so I would like to believe. The problem? I have never built AOSP or Cyanogenmod before, let alone for a device that isn't even supported. So I was hoping the wonderful XDA community could help me out.
The only thing I really can't figure out is how to build CM/AOSP for an unsupported device using a device tree. Someone posted this tree on Github a month ago - https://github.com/OUDhs/android_device_samsung_hltetmo
Then there is a Cyanogenmod kernel for just regular hlte (not hltetmo), posted 10 days ago - https://github.com/CyanogenMod/android_kernel_samsung_hlte
And then there are blobs for mi5 (not mi7), posted 2 days ago - https://github.com/DoItForTheRatchets/vendor_hlte
So my questions are:
Are these any indication of progress on AOSP for the Note 3?
Can I/anyone build CM/AOSP from these for the hltetmo.
I know people have gotten CM on the Note 3; we have all seen the blurry pic one, but here is someone else on October 24th - https://plus.google.com/u/0/+TonyLayher/posts/A4J8eRH8Rht
Click to expand...
Click to collapse
Its getting real close. I imagine some other stuff is needed like qcom hardware updates and stuff. I'd give it another few weeks or so. BUT I imagine it'll be available soon.
I noticed nikkdotcom has a thread over in general for trying to get it running; he is asking for assistance in getting it to work.
CrashTestDroid said:
When a hlte device tree is buildable, looks like CM is making additions and others like nikkdotcom
Click to expand...
Click to collapse
That would be accurate.
Nikkdotcom GitHub here: https://github.com/nikkdotcom/android_device_samsung_hltetmo
---------- Post added at 01:18 AM ---------- Previous post was at 01:10 AM ----------
gakio12 said:
I noticed nikkdotcom has a thread over in general for trying to get it running; he is asking for assistance in getting it to work.
Click to expand...
Click to collapse
Im looking for someone who knows a little better than me about building without the proper blobs for the device. Once the right blobs are available, it will be custom ROMs galore!
What blobs do you need? I thought blobs had to be extracted from the TW stock ROM. GPU blobs should be able to come from any other S800 device right (like the Nexus 5)?
Sent from my SM-N900T using xda app-developers app
geekcentercreations said:
That would be accurate.
Nikkdotcom GitHub here: https://github.com/nikkdotcom/android_device_samsung_hltetmo
---------- Post added at 01:18 AM ---------- Previous post was at 01:10 AM ----------
Im looking for someone who knows a little better than me about building without the proper blobs for the device. Once the right blobs are available, it will be custom ROMs galore!
Click to expand...
Click to collapse
I'd be more than happy to lend a hand.
ProTekk said:
I'd be more than happy to lend a hand.
Click to expand...
Click to collapse
That is great news! We need someone with experience like you. I remember you from other devices, namely the s3.
Would you be able to reach out to the OP and try and get things rolling?
Have you found anything useful on github?
idtheftvictim said:
That is great news! We need someone with experience like you. I remember you from other devices, namely the s3.
Would you be able to reach out to the OP and try and get things rolling?
Have you found anything useful on github?
Click to expand...
Click to collapse
There's enough on GitHub right now for a starting point. I've just started to poke around this morning so I can't say much. Tbh, I've been fairly content with TouchWiz so that's been one reason I haven't had a strong interest in working on AOSP
idtheftvictim said:
That is great news! We need someone with experience like you. I remember you from other devices, namely the s3.
Would you be able to reach out to the OP and try and get things rolling?
Have you found anything useful on github?
Click to expand...
Click to collapse
Really? Content with touchwiz? Hmmm...I wish I knew more, I would be started trying to build cm awhile ago
Sent from my SM-N900T using xda app-developers app
Here is the most likely furthest along tree for anyone.
https://github.com/utkanos/android_device_samsung_hltetmo
It just seems like we might not see stuff on this device. Looking back on this thread people talked like it would be released in a week but I think it's going to be a lot longer than that.
idtheftvictim said:
Really? Content with touchwiz? Hmmm...I wish I knew more, I would be started trying to build cm awhile ago
Sent from my SM-N900T using xda app-developers app
Click to expand...
Click to collapse
That stuff is 2 months old. Nothing in two months? Man...no progress
Sent from my SM-N900T using xda app-developers app
I've never seen a device of this caliber take this long to receive an AOSP ROM! Wish I knew how guys, I'm tired of the TW ROMS, need some action in this forum already
Is their any CM 14.1 rom's for the Pixel XL?
This belongs in the Q & A section.
Long story short - No.
TWRP is only at RC stage right now. I'd say until that's at least stable ROM development will be minimal.
Sent from my Pixel XL
raiden said:
Is their any CM 14.1 rom's for the Pixel XL?
Click to expand...
Click to collapse
Dude, you've posted this in the wroooong place... Just a heads-up before you get ripped by someone else...
---------- Post added at 01:30 AM ---------- Previous post was at 01:28 AM ----------
ffchampmt said:
This belongs in the Q & A section.
Long story short - No.
TWRP is only at RC stage right now. I'd say until that's at least stable ROM development will be minimal.
Sent from my Pixel XL
Click to expand...
Click to collapse
And you are incorrect... Dirty Unicorns exists.
Ker~Man said:
And you are incorrect... Dirty Unicorns exists.
Click to expand...
Click to collapse
He said minimal not non-existent.
JAYNO20 said:
He said minimal not non-existent.
Click to expand...
Click to collapse
The OP's question was whether there are any Cm14.1 ROMs for the device. The namely "short" answer was "No" and continued to say ROM development is minimal. While correct that ROM development is indeed minimal, the OP's question was if there ARE ANY. I think people are "thanking" the wrong reply...
Ker~Man said:
The OP's question was whether there are any Cm14.1 ROMs for the device. The namely "short" answer was "No" and continued to say ROM development is minimal. While correct that ROM development is indeed minimal, the OP's question was if there ARE ANY. I think people are "thanking" the wrong reply...
Click to expand...
Click to collapse
Cm14.1 is different to dirty unicorns so the right anwesee was no
Ker~Man said:
The OP's question was whether there are any Cm14.1 ROMs for the device. The namely "short" answer was "No" and continued to say ROM development is minimal. While correct that ROM development is indeed minimal, the OP's question was if there ARE ANY. I think people are "thanking" the wrong reply...
Click to expand...
Click to collapse
I don't think they are thanking the wrong reply (not that it matters in the slightest). I understood his reply exactly how I stated in my reply. The ROM availability is MINIMAL not NON-EXISTENT. Just means don't expect ROMS upon ROMS upon ROMS.. the development right now is MINIMAL. Seems pretty easy to me...
JAYNO20 said:
I don't think they are thanking the wrong reply (not that it matters in the slightest). I understood his reply exactly how I stated in my reply. The ROM availability is MINIMAL not NON-EXISTENT. Just means don't expect ROMS upon ROMS upon ROMS.. the development right now is MINIMAL. Seems pretty easy to me...
Click to expand...
Click to collapse
Since you all apparently can't handle being wrong, you can be right, by proxy. Hats off!
Ker~Man said:
Since you all apparently can't handle being wrong, you can be right, by proxy. Hats off!
Click to expand...
Click to collapse
Sounds like YOU might be the one that can't handle being wrong...
JAYNO20 said:
Sounds like YOU might be the one that can't handle being wrong...
Click to expand...
Click to collapse
LMFAO! You've got me there!
Both DU and CM are derived from AOSP.
But one cannot possibly consider DU to be CM or vice-versa.
DU is far more AOSP than CM is too, IMO
It can even be argued that CM should not be considered AOSP.
In any event, CM is probably a long ways off (I'm guessing).
And will never be as reliable/smooth as a more truly AOSP based ROM such as DU.
DU is in release candidate status now, with the only issue being that Okay Google isn't working yet.
Otherwise it's 99.99% a daily driver already and I'm loving it.
Dirty Unicorns team did a great job on this ROM and it's only on its third release. Thanks, Spaceman. :good:
Btw, if/when CM does show up for the Pixel, there is a very good chance you'll be able to get APT-X high def bluetooth codec working on it.
See the aptx link in my sig below for more info.
And I'm darn sure going to try and get APT-X working in DU when the source is released to public.
CZ Eddie said:
Both DU and CM are derived from AOSP.
But one cannot possibly consider DU to be CM or vice-versa.
DU is far more AOSP than CM is too, IMO
It can even be argued that CM should not be considered AOSP.
In any event, CM is probably a long ways off (I'm guessing).
And will never be as reliable/smooth as a more truly AOSP based ROM such as DU.
DU is in release candidate status now, with the only issue being that Okay Google isn't working yet.
Otherwise it's 99.99% a daily driver already and I'm loving it.
Dirty Unicorns team did a great job on this ROM and it's only on its third release. Thanks, Spaceman. :good:
Btw, if/when CM does show up for the Pixel, there is a very good chance you'll be able to get APT-X high def bluetooth codec working on it.
See the aptx link in my sig below for more info.
And I'm darn sure going to try and get APT-X working in DU when the source is released to public.
Click to expand...
Click to collapse
I have "okay google" partially working. It won't turn on unless my screen is on, and then it always asks me to do the setup, but if you hit do it later it let's you proceed to asking whatever you'd like.
zaksimmermon said:
and then it always asks me to do the setup, but if you hit do it later it let's you proceed to asking whatever you'd like.
Click to expand...
Click to collapse
Yep, it's the same for everyone.
Broken.
I rarely use the always-on voice activation. Never really got into the habit of it.
I've got a pull-down quick setting toggle I press when I want to ask Google something.
Actually I've also got a swipe-up to ask Google something.
I feel kinda funny saying "OK Google" in public.
---------- Post added at 12:04 AM ---------- Previous post was at 12:01 AM ----------
raiden said:
Is their any CM 14.1 rom's for the Pixel XL?
Click to expand...
Click to collapse
Keep an eye out for Lineage to take over some CM duties?
I have "0" info on this, haven't looked into it at all.
I don't really care about CM much these days.
But this link might be helpful to you?
https://www.neowin.net/news/lineage-os-to-continue-the-work-of-the-cyanogenmod-community
Do you know when we can expect a ROM based on Android O?
Can't say for sure. May never see an official release from Nextbit/Razer, but I'm sure custom rom devs will release it when it's ready.
davehasninjas said:
Can't say for sure. May never see an official release from Nextbit/Razer, but I'm sure custom rom devs will release it when it's ready.
Click to expand...
Click to collapse
Didn't Nextbit or Razer hire the devs from Paranoid Android? If they are working on the Robin ROM, I'm pretty sure it's safe to say we'll get Oreo. However Razer announced a gaming phone a while ago, so there is no way to tell.
Baconator724 said:
Didn't Nextbit or Razer hire the devs from Paranoid Android? If they are working on the Robin ROM, I'm pretty sure it's safe to say we'll get Oreo. However Razer announced a gaming phone a while ago, so there is no way to tell.
Click to expand...
Click to collapse
One of the Developer's for PA is also one of the 30 teams members of nextbit.
There are quite a few links like these which mention Lineage OS 15 (Oreo) supported devices and robin is one of them! I cant wait for the release!
http://www.lineageosdownloads.com/lineage-os-15-supported-device-list/
protonsavy said:
There are quite a few links like these which mention Lineage OS 15 (Oreo) supported devices and robin is one of them! I cant wait for the release!
http://www.lineageosdownloads.com/lineage-os-15-supported-device-list/
Click to expand...
Click to collapse
Except those are all fake. The LOS maintainers won't actually know if a device will support LOS 15 until they actually try porting it in the first place. As of now, they haven't tried for the Nextbit Robin yet, so we don't know if the Robin could actually get LOS 15 yet.
If you wanna keep tabs on what devices are currently being worked on, go to https://review.lineageos.org/#/q/statuspen and look for anything being commited to the lineageos-15.0 branch for android_device_nextbit_ether.
Software updates till February as they say on Twitter. Apart from nextbits cloud framework the OS is pretty much stock AOSP and it seems to me they're really good with releasing kernel source and providing updates almost every three months.
Robin, on N, is a mess. If it does eventually get O, it will be a while. We cannot upgrade it to O until we fix out the bugs we have on N first.
What are the bugs on N? I'm thinking about buying one. Is it worth it?
oh1blksheep said:
What are the bugs on N? I'm thinking about buying one. Is it worth it?
Click to expand...
Click to collapse
Camera, GPS, battery blah the list goes on. The kernels a mess because of bad sources. I wouldnt recommend it , it would be better getting a moto G device or similar at this stage.
DarkExistence said:
Camera, GPS, battery blah the list goes on. The kernels a mess because of bad sources. I wouldnt recommend it , it would be better getting a moto G device or similar at this stage.
Click to expand...
Click to collapse
I have two devices, and I don't have troubles with it.
HeaDekBatHblu said:
I have two devices, and I don't have troubles with it.
Click to expand...
Click to collapse
Doesn't make a difference, the code base is a mess. If your buying for a Dev device, dont. Even the top lineage Devs are struggling to make it as stable as it is (and it's not very stable, messy as hell!) As an every day device it's ok but there are better phones now a days in the price range, and support is basically dead for robin now.
DarkExistence said:
Doesn't make a difference, the code base is a mess. If your buying for a Dev device, dont. Even the top lineage Devs are struggling to make it as stable as it is (and it's not very stable, messy as hell!) As an every day device it's ok but there are better phones now a days in the price range, and support is basically dead for robin now.
Click to expand...
Click to collapse
Development is not dead at all. Have you seen Gerrit for many of the ROMs??? The CarbonROM Dev already has pushes to Gerrit for O. Lineage still gets device specific changes. ParanoidAndroid has a private kernel source for ether so their working on it behind the scenes. AICP and many other ROMs use the Lineage kernel, so there aren't many differences to those that use that kernel. O development is still ongoing, and this device is still great for the price. The ROMs at the moment, are very stable in my opinion.
xWolf13 said:
Development is not dead at all. Have you seen Gerrit for many of the ROMs??? The CarbonROM Dev already has pushes to Gerrit for O. Lineage still gets device specific changes. ParanoidAndroid has a private kernel source for ether so their working on it behind the scenes. AICP and many other ROMs use the Lineage kernel, so there aren't many differences to those that use that kernel. O development is still ongoing, and this device is still great for the price. The ROMs at the moment, are very stable in my opinion.
Click to expand...
Click to collapse
I know, I'm the AICP maintainer for ether lol... And discuss with the official lineage maintainers for ether daily ..
I meant official development, btw, meaning a lot of the bugs won't be fixed because we need official updates to be able to fix them.
O development for lineage ether hasn't even begun yet, N bugs need to be fixed before O begins, and that will take awhile.
DarkExistence said:
I know, I'm the AICP maintainer for ether lol... And discuss with the official lineage maintainers for ether daily ..
I meant official development, btw, meaning a lot of the bugs won't be fixed because we need official updates to be able to fix them.
O development for lineage ether hasn't even begun yet, N bugs need to be fixed before O begins, and that will take awhile.
Click to expand...
Click to collapse
My apologies if I seemed aggressive. Official development seems to be like any other manufacturer, however, as we all know, software support is ending soon. I've been following Gerrit and have noticed the ongoing development by our developers (including you). IIRC camera was borked on one of the nightlies, but was immediately fixed. IMO, we are now depending on development from our ether devs rather than official support since Nextbit have been ghosting for the past few months.
oh1blksheep said:
What are the bugs on N? I'm thinking about buying one. Is it worth it?
Click to expand...
Click to collapse
Keep in mind what DarkExistence said, and realize the Robin's closest equivalent is a Nexus 5. If you can get better & newer hardware for a little more money, do so. I got mine as an "emergency" replacement when I was short on funds a few months ago. I lucked into an eBay sale & discount code which brought the phone to about 100.00. I'm happy with it, but I wish Razer would have made good sources available & gave full permission for them to be hosted elsewhere. So the devs didn't get so frustrated with what should be a decent phone to run custom ROMs on.
Sent from my Robin using XDA Labs
So how us the Robin treating you. Did you root? ARE you using any ROMs
oh1blksheep said:
What are the bugs on N? I'm thinking about buying one. Is it worth it?
Click to expand...
Click to collapse
Yes, for $130 it's worth buying. The bugs on android N are not nearly as bad as what some claim them to be.
Here's as list of what I can recall:
1. Enhance colors distorts colors (so turn it off)
2. Screen static displays when unlocking phone for 1/10th of a second with some roms
3. You can hear The Speakers turn off after sound has stopped playing if You listen closely
4. Headphones with a mic sometimes cut out and play through internal Speakers although there is as work around for this
5. Audio fx does not work
Other than any of those there is not much i can personally complain about and I own 2 robins. About to get a moto g4 plus because it's time for something that has a larger XDA fourm and something that has been confirmed to get android O (wich nextbit has yet to announce a decision to besides "we have been discussing it").
If I were You and my budget was under $200 i'd get The robin.
If You can spend $225 get The g4 plus without a doubt. Hope this helps
oh1blksheep said:
So how us the Robin treating you. Did you root? ARE you using any ROMs
Click to expand...
Click to collapse
I like it, especially for the price. Currently using CarbonROM rooted with Magisk. Just realize you're getting a phone with zero support from the manufacturer, so don't spend more than you're willing to lose.
Sent from my Robin using XDA Labs
DarkExistence said:
I know, I'm the AICP maintainer for ether lol... And discuss with the official lineage maintainers for ether daily ..
I meant official development, btw, meaning a lot of the bugs won't be fixed because we need official updates to be able to fix them.
O development for lineage ether hasn't even begun yet, N bugs need to be fixed before O begins, and that will take awhile.
Click to expand...
Click to collapse
Well thank you for being the maintainer on Ether. I just ordered the phone. 129.00 for a phone with these specs. Couldn't pass it up. I'm sure you will eventually make AICP stable. Thank you for your honesty.
Just like the title says really. Which developers will be definitely getting the OP 5T in the near future ?
I really wonder if unified builds are going to be possible with 5 and 5T. What really matters to me is the community support more than the device itself. On my OP3 I had great support and I think now it's time to change the device. I'm considering 5T but I need to see my favorite ROMs here first.
second this.
charackthe said:
I really wonder if unified builds are going to be possible with 5 and 5T. What really matters to me is the community support more than the device itself. On my OP3 I had great support and I think now it's time to change the device. I'm considering 5T but I need to see my favorite ROMs here first.
Click to expand...
Click to collapse
Any particular roms you are hoping for in particular ?
SlyUK said:
Any particular roms you are hoping for in particular ?
Click to expand...
Click to collapse
Especially Resurrection Remix Official and/or Zenity Tweaks version. I can't live without RR's customizations and QS toggles.
Yes I also need the dev support more than anything else. Besides that it is also a great device. Hope sultan makes his los.
If PureFusion ends up coming, I'm definitely making the switch to 5T
Me
(even if I'm still not consider myself as a real dev )
@martinusbe said he's getting one (great dev of GZOSP and Validus ROMs).
I like using carrier features on T-Mobile (e.g. WIFi calling and VoLTE). Anyone feel that FreedomOS will port over by someone?
Blu_Spark has already arrived, with some publicity:
https://www.xda-developers.com/blu-spark-oneplus-5t/
@eng.stk
First to arrive must be in the Fast Lane !
I really hope that some Roms start to appear next week so I can buy it
I think that Lord Boeffla might be coming to the 5T as well, not 100% sure but he did say he will know in the coming days. Fingers crossed, I've used his kernels since my Galaxy S3.
Sent from my brain, to my thumbs, and entered into a OnePlus 2 input device.
Alex Cruz (and possibly another dev), a DirtyUnicorns dev has confirmed that he purchased the 5T. I know they don't like being on this site for various reasons, but it's nice to know DU will be coming for the 5T!
OnePlus software team said OxygenOS will have unified builds so 5 builds should be able to work on 5T also
I'm really hoping FreedomOS comes to the 5T.
xByt3z said:
I'm really hoping FreedomOS comes to the 5T.
Click to expand...
Click to collapse
It has https://forum.xda-developers.com/oneplus-5t/development/rom-freedomos-2-0-2-t3709708
I'm quite sure Paranoid Android will come along at some point in the near future.
BoboBrazil said:
OnePlus software team said OxygenOS will have unified builds so 5 builds should be able to work on 5T also
Click to expand...
Click to collapse
No its not work now.
SlyUK said:
It has https://forum.xda-developers.com/oneplus-5t/development/rom-freedomos-2-0-2-t3709708
Click to expand...
Click to collapse
Correct! I ported it over from the 5. Fortunately it didn't take long to do, worked with NevaX1 to get it up
I have bought this phone and I'm curious if there is any custom roms other than MIUI?
Diar990 said:
I have bought this phone and I'm curious if there is any custom roms other than MIUI?
Click to expand...
Click to collapse
There are no other custom ROMs yet, but there are several factors that make me believe that there will soon be good support for this device.
First off, xiaomi most of the time doesn't wait long these days before revealing their kernel source.
Furthermore this device is a typical mid-ranger that in a way scratches the upper range, so it is predestined to make people curious about its potential and is very affordable at the same time.
We don't have cristal balls for these questions, but for me the odds are good - otherwise I wouldn't have bought this phone myself ; )
I think this device has better chance to get custom ROMs than 5G version, because it has same chipset like Redmi Note 10 Pro or Poco X3 NFC. These devices already have custom ROMs, so it is possible to make custom ROM with the help of their device trees. I will maybe buy this phone and attempt to do it once I have more free time, however I would be glad if more experienced developer did it
I'm really hoping for PixelPlusUI or Pixel Experience on this. would be perfect.
I am not at all confident for this device, about custom roms.
RN 10 Pro came out not even a month earlier, and you can already find twrp plus many roms in development.
For Mi 11 Lite nothing yet...and I don't think it's much harder to mod.
It is a device born unlucky in my opinion, they have produced few and sells little, and will have little or zero community.
I'll wait another month, and if nothing comes out I'll sell it.
It's a pity, because i really love form factor and weight, and is fast and reliable. But for me modding is essential, i dont like miui.
some devs are workin on one:
youngherna/kernel_xiaomi_courbet
Contribute to youngherna/kernel_xiaomi_courbet development by creating an account on GitHub.
github.com
sorry to steal your thunder
laviniu_c said:
sorry to steal your thunder
Click to expand...
Click to collapse
What does it mean?
However, great news! Hope to see some usable LOS or similar soon
You saved me from selling courbet, on the 30th day
And i'm really loving this phone
LMGTFY - Let Me Google That For You
For all those people who find it more convenient to bother you with their question rather than to Google it for themselves.
bfy.tw
im assuming the devs are gonna wanna let us mere mortals know when it's ready. so i stole their thunder a bit by finding that repo/work in progress.
laviniu_c said:
some devs are workin on one:
youngherna/kernel_xiaomi_courbet
Contribute to youngherna/kernel_xiaomi_courbet development by creating an account on GitHub.
github.com
Click to expand...
Click to collapse
Uh... actually that's a custom Kernel, not a custom ROM.
GitHub - youngherna/android_device_xiaomi_courbet
Contribute to youngherna/android_device_xiaomi_courbet development by creating an account on GitHub.
github.com
Parnas72 said:
Uh... actually that's a custom Kernel, not a custom ROM.
Click to expand...
Click to collapse
It usually starts right there.
No kernel for the device, no custom rom.
This is great news!
Oh, and you can already find a courbet device repo there btw : )
Phil_Smith said:
It usually starts right there.
No kernel for the device, no custom rom.
This is great news!
Oh, and you can already find a courbet device repo there btw : )
Click to expand...
Click to collapse
does it mean custom kernel custom rom?
Lollauser said:
I am not at all confident for this device, about custom roms.
RN 10 Pro came out not even a month earlier, and you can already find twrp plus many roms in development.
For Mi 11 Lite nothing yet...and I don't think it's much harder to mod.
It is a device born unlucky in my opinion, they have produced few and sells little, and will have little or zero community.
I'll wait another month, and if nothing comes out I'll sell it.
It's a pity, because i really love form factor and weight, and is fast and reliable. But for me modding is essential, i dont like miui.
Click to expand...
Click to collapse
yes... same to me.. But i hope it will get a community...
Ahhh, you doubters can see now.
Unofficial CrDroid an PE have just been released on the telegram channel (sorry, not allowed to post the link here, but you will figure it out).
I flashed CrDroid and it is super stable and feature-rich - total recommendation!
Phil_Smith said:
Ahhh, you doubters can see now.
Unofficial CrDroid an PE have just been released on the telegram channel (sorry, not allowed to post the link here, but you will figure it out).
I flashed CrDroid and it is super stable and feature-rich - total recommendation!
Click to expand...
Click to collapse
Oh there it is right here:
[EOL][ROM][11][OFFICIAL] crDroid 7.13
*** Disclaimer I am not responsible for any damage you made to your device You have been warned crDroid is designed to increase performance and reliability over stock Android for your device also attempting to bringing many of the best features...
forum.xda-developers.com
Phil_Smith said:
Ahhh, you doubters can see now.
Unofficial CrDroid an PE have just been released on the telegram channel (sorry, not allowed to post the link here, but you will figure it out).
I flashed CrDroid and it is super stable and feature-rich - total recommendation!
Click to expand...
Click to collapse
Yesssssss
You (and the developers of course) just made my morning brighter
crDroid is my favourite, also