Related
Hi with so many cyanogenMod 9 roms out there now and to help new comers choose between roms I thought I would start a poll to help decide which is better as the roms progress with newer builds.I will add new roms as they come hope this helps people to choose thanks.
why is this a checkbox poll? it should be radio buttons, since there can only be 1 "best"
I voted for Domination.. :good::good::good:
TeamNDVRu. The only build without any camera issues (not focusing on faces).
Shu. said:
TeamNDVRu. The only build without any camera issues (not focusing on faces).
Click to expand...
Click to collapse
Even paranoid android doesnt have camera problems
Sent from my HTC One X
Voted for TeamNDVRu. A2DP works only in this rom.
TeamNDVRu gets my vote mainly for having updates nearly on a daily basis, and feels pretty close to being an official nightly.
I also love team ndvru release it feels clean fash stable and most important it works.
What, TeamNDVRu? Which one is that?
Edit: nwm found it
instead of 5 versions of Cyangen, fixing the same problems over and over, they should be working together to make ONE Cyangen that actually works......
wesleyrpg said:
instead of 5 versions of Cyangen, fixing the same problems over and over, they should be working together to make ONE Cyangen that actually works......
Click to expand...
Click to collapse
Open source dude... actually the competition will make them work harder and eventually the end users will be benefited
Sent from my HTC One X
wesleyrpg said:
instead of 5 versions of Cyangen, fixing the same problems over and over, they should be working together to make ONE Cyangen that actually works......
Click to expand...
Click to collapse
They are working togather ... A bug once fixed in a ROM is pulled to other versions. There maybe some who don't :silly:
Hello Voted for CyanogenMod9 alpha 7 - TeamNDVRu:good:
jutley said:
Hi with so many cyanogenMod 9 roms out there now and to help new comers choose between roms I thought I would start a poll to help decide which is better as the roms progress with newer builds.I will add new roms as they come hope this helps people to choose thanks.
Click to expand...
Click to collapse
Why didn't you include the first CM9 that was available on xda, and the only one that has nightly builds? (Intrepresentation's originally and then picked up by tgascoigne)
http://forum.xda-developers.com/showthread.php?t=1661629
And I don't think Domination is really a "CM9" build, rather a Based-on-CM9 since it has many extra features and has differed significantly from a stock CM9 install (not that there is anything wrong with that).
The TeamNDVRu is the best, but the Endeavor Unleashed isn't bad
You got that spot on
TeamNDVRu
Votes
TeamNDVR
Sent from my HTC One X using Tapatalk 2
wesleyrpg said:
instead of 5 versions of Cyangen, fixing the same problems over and over, they should be working together to make ONE Cyangen that actually works......
Click to expand...
Click to collapse
THIS.
Choice is good, naturally but too many of the same thing and it doesn't benefit anyone in the end. In principle, competition may be good but it's almost like two stores under selling each other to get the customers or the glory or what have you.
If one team comes up with a solution, and the others copy it? then who is really benefiting here? where's the innovation in other releases?
These teams should really work together and find a FINAL CM9 build and THEN based their future ROMs on this official unofficial CM9 ROM.
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
Hello everybody.
So I was wondering, when CyanogenMod 12 comes out, will they still support all of the devices they have been supporting? Or at least, in specific, our device? I can't imagine why'd they drop support.
Also, I hear in the new Android version, the Linux 3.10 kernel is being used. As opposed to the current 3.4 kernel we are using. Does anybody know about any significant changes between the two?
This is very exciting if/when we get this on our device I personally will just wait on a CM or AOSP version of Android as stock never really does it for me.
I don't know, but the more I think about it, the more excited I get (also the more apprehensive I get since I'll have to upgrade my kernel sources).
I know I probably shouldn't bring this up, but I also can't wait to blow my friend's new iOS 8 update out of the water with CM12/L (Not like CM11 doesn't already do that )
Snepsts said:
Hello everybody.
So I was wondering, when CyanogenMod 12 comes out, will they still support all of the devices they have been supporting? Or at least, in specific, our device? I can't imagine why'd they drop support.
Also, I hear in the new Android version, the Linux 3.10 kernel is being used. As opposed to the current 3.4 kernel we are using. Does anybody know about any significant changes between the two?
This is very exciting if/when we get this on our device I personally will just wait on a CM or AOSP version of Android as stock never really does it for me.
I don't know, but the more I think about it, the more excited I get (also the more apprehensive I get since I'll have to upgrade my kernel sources).
I know I probably shouldn't bring this up, but I also can't wait to blow my friend's new iOS 8 update out of the water with CM12/L (Not like CM11 doesn't already do that )
Click to expand...
Click to collapse
I'm so excited about this. It will be sooooooo cool. I need to learn to develop ROMs and stuff, because if developer support dies for this phone I would want to keep the development going.
Well then start now rjm....... Better now then never
2SHAYNEZ
rjmxtech said:
I'm so excited about this. It will be sooooooo cool. I need to learn to develop ROMs and stuff, because if developer support dies for this phone I would want to keep the development going.
Click to expand...
Click to collapse
You'll have me doing the little bit I can for this device for the next 8-9 months I'm stuck with this thing
Don't worry about developing ROMs, all you really need to know is how to compile and maintain. I plan to attempt at some unofficial builds of a ROM or two once I can deem my kernel as done. But don't worry, the LG OGP is definitely booming with activity right now, and will probably only get better with the following months to come.
We already have:
Gummy
PAC
Beanstalk
CM11
AOKP
AICP
Vanir
and a pretty good range of stock ROMs.
Soon (and I mean within a month or so) I hope to add Carbon and Paranoid Android to this list, but we will have to see. I do not know how to compile unofficially or much about it, but it doesn't look extremely difficult. So my hopes are high.
Plus, as this device drops in price, we may get some more people to keep development for this device relevant. Although I did not see our device in the local AT&T store last time I was there...
We have a beautiful phone with the processing power to last as a quality device for another year at least. LG makes some pretty nice stuff.
Unfortunately, we will be seeing more and more of our users leave as the months drag on as this phone gains age
We'll have to see who lasts the longest with this phone as their primary device... lol.
I suspect we will reach our peek in ROMs soon a few months after Android L is up and running. Just my guess though.
Shayne has a good point though, now is definitely the time to start. So better hit the tutorials!
Snepsts said:
You'll have me doing the little bit I can for this device for the next 8-9 months I'm stuck with this thing
Don't worry about developing ROMs, all you really need to know is how to compile and maintain. I plan to attempt at some unofficial builds of a ROM or two once I can deem my kernel as done. But don't worry, the LG OGP is definitely booming with activity right now, and will probably only get better with the following months to come.
We already have:
Gummy
PAC
Beanstalk
CM11
AOKP
AICP
Vanir
and a pretty good range of stock ROMs.
Soon (and I mean within a month or so) I hope to add Carbon and Paranoid Android to this list, but we will have to see. I do not know how to compile unofficially or much about it, but it doesn't look extremely difficult. So my hopes are high.
Plus, as this device drops in price, we may get some more people to keep development for this device relevant. Although I did not see our device in the local AT&T store last time I was there...
We have a beautiful phone with the processing power to last as a quality device for another year at least. LG makes some pretty nice stuff.
Unfortunately, we will be seeing more and more of our users leave as the months drag on as this phone gains age
We'll have to see who lasts the longest with this phone as their primary device... lol.
I suspect we will reach our peek in ROMs soon a few months after Android L is up and running. Just my guess though.
Shayne has a good point though, now is definitely the time to start. So better hit the tutorials!
Click to expand...
Click to collapse
If you could keep Beanstalk going for our device if development stops I would greatly appreciate it. I'll try and help out too when I learn how in case development does stop.
rjmxtech said:
If you could keep Beanstalk going for our device if development stops I would greatly appreciate it. I'll try and help out too when I learn how in case development does stop.
Click to expand...
Click to collapse
I have a feeling that we don't have to worry about Beanstalk
No it won't stop..... Aicp has seemed to come to a hault .. Maybe you should jump on that rmj..... Read read read and then read .... Then compile yo stuff
2SHAYNEZ
shayneflashindaily said:
No it won't stop..... Aicp has seemed to come to a hault .. Maybe you should jump on that rmj..... Read read read and then read .... Then compile yo stuff
2SHAYNEZ
Click to expand...
Click to collapse
It seems as though a lot of ROMs by that particular dev get abandoned eventually... but that's none of my business.
Yes AICP would be a great one to start on, first thing is first though, rjm, get yourself on a Linux VM or a Linux computer. Also, I hope you have some decent specs or it'll be hell trying to do it.
For example, I have an AMD FX-6350, so I have 6 cores in my system. I can allocate 4 to my VM
And you'll want some RAM, too. Like 8 GB so if you're using a VM you can allocate 4 as well.
For the distro I suggest using Linux Mint 64-bit (has to be 64-bit).
And I really hope your host OS is 64-bit, because otherwise you are probably incapable of compiling ROMs.
Best of luck!
P.S: I downloaded Carbon sources today. We'll see how that goes.
Oh also be sure you have PLENTY of free space, those sources love hogging space. I just cleaned out my old VM and set up a new one with 200 GB of space allocated. Thank God for Terabyte HDDs
Staying on topic, the L/5.0 SDK was released today. Approx. two weeks until the official Nexus release, and hopefully not too long until we get a taste of that afterwards.
KitKat was great (it felt like the smoothest Android experience ever when I flashed my first KK ROM) but I'm ready for Lollipop!
Material design looks interesting, although I gotta say... the circle triangle square virtual buttons aren't the best design choice imo. Maybe it's to make switching from an iPhone to an Android easier for the iUsers that find the current system to difficult to understand :laugh: They sure like their shapes of rounded edge squares and circles.
I'm not kidding, actually. A friend of mine steals my phone all the time and she cannot figure out PIE to save her life...
shayneflashindaily said:
No it won't stop..... Aicp has seemed to come to a hault .. Maybe you should jump on that rmj..... Read read read and then read .... Then compile yo stuff
2SHAYNEZ
Click to expand...
Click to collapse
I don't think I want to compile AICP. Beanstalk is the only ROM IMO that really would be a loss if development stopped. The features of Beanstalk outnumber those of other ROMs
rjmxtech said:
I don't think I want to compile AICP. Beanstalk is the only ROM IMO that really would be a loss if development stopped. The features of Beanstalk outnumber those of other ROMs
Click to expand...
Click to collapse
What about compiling it for the sake of learning how to compile...?
Snepsts said:
What about compiling it for the sake of learning how to compile...?
Click to expand...
Click to collapse
Maybe
rjmxtech said:
I don't think I want to compile AICP. Beanstalk is the only ROM IMO that really would be a loss if development stopped. The features of Beanstalk outnumber those of other ROMs
Click to expand...
Click to collapse
Is Beanstalk as stable as cm11. Does it have a RC or something similar to PAC or M11?
dpalmer76 said:
Is Beanstalk as stable as cm11. Does it have a RC or something similar to PAC or M11?
Click to expand...
Click to collapse
I'm pretty sure Beanstalk only releases stable updates. From what I remember there aren't any nightlies, as it sometimes is months before a new update is released. That is another reason why I like Beanstalk better than other ROMs.
I will be happy to see official LG update for Android Lollipop 5.x Waiting for updates!
rahib172 said:
I will be happy to see official LG update for Android Lollipop 5.x Waiting for updates!
Click to expand...
Click to collapse
Not much news from lg on updates yet:
http://www.androidauthority.com/which-phones-android-lollipop-540232/
---------- Post added at 05:11 PM ---------- Previous post was at 05:05 PM ----------
rjmxtech said:
I don't think I want to compile AICP. Beanstalk is the only ROM IMO that really would be a loss if development stopped. The features of Beanstalk outnumber those of other ROMs
Click to expand...
Click to collapse
Probably a sort of noobish question, but anyway many roms are cm-based (including beanstalk), and even aokp is cm enabled. How dependent are these roms on cm, basically meaning could they sustain themselves without cm continuing support too?
abumy said:
Not much news from lg on updates yet:
http://www.androidauthority.com/which-phones-android-lollipop-540232/
---------- Post added at 05:11 PM ---------- Previous post was at 05:05 PM ----------
Probably a sort of noobish question, but anyway many roms are cm-based (including beanstalk), and even aokp is cm enabled. How dependent are these roms on cm, basically meaning could they sustain themselves without cm continuing support too?
Click to expand...
Click to collapse
I think CM official support is close to vital for these ROMs, mainly for the kernel, but also because they update the device thingy you use to build ROMs I do believe.
I am 90% sure we will receive updates from CM though. They sure know how to take care of their devices.
Any custom ROM will do, if we are talking about testing the new Android L. What's bothering me is the support for F240x devices. If CM, Beanstalk, VANIR/COMMOTIO or AICP (the one I am using for a long period of time), will release an update, will there be a KERNEL or ROM that will work for the F240x?
MitoTakatori said:
Any custom ROM will do, if we are talking about testing the new Android L. What's bothering me is the support for F240x devices. If CM, Beanstalk, VANIR/COMMOTIO or AICP (the one I am using for a long period of time), will release an update, will there be a KERNEL or ROM that will work for the F240x?
Click to expand...
Click to collapse
I really hope it is for your sake. Luckily the dev that makes F240 ROMs for you guys seems to know what he's doing, and I'm sure he'll keep working for you. As long as e980 has support he can use that kernel and use it for F240.
Snepsts said:
I really hope it is for your sake. Luckily the dev that makes F240 ROMs for you guys seems to know what he's doing, and I'm sure he'll keep working for you. As long as e980 has support he can use that kernel and use it for F240.
Click to expand...
Click to collapse
Hopefully.
stupid question:
why are there no aosp nougat roms for the htc 10 yet?
Sent from my HTC 10 using Tapatalk
nuumuun said:
stupid question:
why are there no aosp nougat roms for the htc 10 yet?
Sent from my HTC 10 using Tapatalk
Click to expand...
Click to collapse
AOSP/CM aren'f close to be stable at all, let alone on Nougat.
nuumuun said:
stupid question:
why are there no aosp nougat roms for the htc 10 yet?
Sent from my HTC 10 using Tapatalk
Click to expand...
Click to collapse
HTC said they would be releasing an update from MM to Nougat in the next couple of months.
can't wait months ... i need my fix now ?
Ariac Konrel said:
AOSP/CM aren'f close to be stable at all, let alone on Nougat.
Click to expand...
Click to collapse
i assumed they would be soon after an official release on nexus devices ...
so much for assumptions ?
nuumuun said:
i assumed they would be soon after an official release on nexus devices ...
so much for assumptions
Click to expand...
Click to collapse
AOSP on these devices is hand built based on trial and error, knowledge of coding off what lil source is a available, and the blood sweat and tears of other developers with bits and pieces from different hardware across many devices to get it to work, since it's like building custom firmware from the ground up through reverse engineering because everything is proprietary.
HTC is building nougat and testing, and they have all the source code and hardware drivers, firmware, etc, and I've seen some predictions it may come as early as quarter 4 I believe, and then we'll have custom sense roms. But the developers will have to build up AOSP, and they've worked their butts off to get CM with Marshmallow as far along as they have.
CharliesTheMan said:
AOSP on these devices is hand built based on trial and error, knowledge of coding off what lil source is a available, and the blood sweat and tears of other developers with bits and pieces from different hardware across many devices to get it to work, since it's like building custom firmware from the ground up through reverse engineering because everything is proprietary.
HTC is building nougat and testing, and they have all the source code and hardware drivers, firmware, etc, and I've seen some predictions it may come as early as quarter 4 I believe, and then we'll have custom sense roms. But the developers will have to build up AOSP, and they've worked their butts off to get CM with Marshmallow as far along as they have.
Click to expand...
Click to collapse
I'm going to go out on a limb and say that once HTC releases the Nougat update, especially the kernel source, 3rd party ROMs should come easier, or at least ease development. At least, that's what I've observed from my 5 years on XDA.
Last official news about the nougat update from HTC was back in August, stating Q4 for unlocked versions...
as for AOSP/CM, even though CM is still in alpha/MM its came a long way and can be used as a daily driver. So if any dev decides to take on nougat at any level after the HTC release/sources i'd be happy
There's an alleged leak of the Nougat update for the 10 here. Not sure how legit it is though, but if it turns out to be true then the update isn't too far away. On the plus side, it looks like HTC will finally allow us to customize the quick settings tiles.
RohinZaraki said:
There's an alleged leak of the Nougat update for the 10 here. Not sure how legit it is though, but if it turns out to be true then the update isn't too far away. On the plus side, it looks like HTC will finally allow us to customize the quick settings tiles.
Click to expand...
Click to collapse
that's actually screenshots of the HTC Bolt, or "HTC 10 Evo" depending on where you live. Translating the screenshots shows 3GB total RAM....
My experience in previous major version updates and HTC elevate participation makes me feel like they're already quite a ways into testing builds, and I have been VERY happy with HTC's rate of development and support life cycle on devices from the M7 forward. I think the nougat release for the HTC 10 is going to be sweet, as a personal side note.
Sent from my HTC 10 using Tapatalk
chrisz5z said:
that's actually screenshots of the HTC Bolt, or "HTC 10 Evo" depending on where you live. Translating the screenshots shows 3GB total RAM....
Click to expand...
Click to collapse
Yep you are right, can confirm it. Typing it from that device
But nonetheless nougat on the 10 will look the same and it will be out very soon I think. Shouldn't be that long anymore. Testing stage should be very advanced by now. But we will see if in November or December
chrisz5z said:
that's actually screenshots of the HTC Bolt, or "HTC 10 Evo" depending on where you live. Translating the screenshots shows 3GB total RAM....
Click to expand...
Click to collapse
Ah damn, that's a shame. On the plus side though, if that's a glimpse of how the Nougat update will look like then I'm excited all the same.
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.