Related
So trying to choose between the Moto X and the Nexus 5, I came across the biggest difference between these phones, their development. Moto X has little to none and Nexus 5 has more than any phone out there. This was an easy win for Nexus 5 I thought. Until I read Moto X users saying that flashing ROMs and kernels are normally to fix issues that the stock versions have and that they don't need Custom ROMs and kernels because what they get is stable, smooth, and lasts long enough (battery wise).
I thought back to why I flash ROMs on Note II and my previous phone SII, and fair enough, I used to do it because I wanted to fix issues that came with stock versions. Now, I hate flashing ROMs, I just want to use my phone. Anyways, looking at the development on the Nexus 5, it seems much of it is to fix the speakers, camera, battery life, etc.
Then I thought that Custom ROMs are important to stay up to date with Google's updates but then Motorola released their update faster than Google did with their Nexus 4. They are also updating their 1.5 year old phones (Not the Razr HD or the Razr HD Maxx probably because of their TI chipset). So it looks like Moto X users are in good hands as far as updates are concerned.
What do you guys think? Would you rather have a fully functional stable stock ROM on a phone that has no development otherwise or would you rather get a phone with tons of development to fix issues that the stock ROM has?
I am asking because there may be an angle to development that I haven't considered. Many customizable things included in ROMs on Nexus 5 are available via Xposed on Moto X.
Until I read Moto X users saying that flashing ROMs and kernels are normally to fix issues that the stock versions have and that they don't need Custom ROMs and kernels because what they get is stable, smooth, and lasts long enough (battery wise).
Click to expand...
Click to collapse
That's a very narrow perspective. There are lots of reasons one might want to flash a ROM or kernel; the "one size fits all" mentality of other vendors such as Apple and Microsoft need not apply here. Custom ROMs open the door to different features that the OEM might not have considered or wanted to spend time on, and allow the creativity of the general public to enhance the phone in ways that are unique to them or only fits a certain niche that wouldn't be profitable for a big company to try and cater to. It certainly isn't just about "fixing issues".
Though custom ROMs certainly aren't the only feature I would look for in a phone, I might hesitate before buying a phone that little support or, even worse, a locked bootloader with no current workaround or hack for the simple reason that even if there's nothing I'm interested in today, there might be something cool that I want to try out tomorrow.
MaxCarnage said:
there might be something cool that I want to try out tomorrow.
Click to expand...
Click to collapse
If you had bought something like the Moto X one year ago, what feature made by the ROM developers on the Nexus 4 would you really want to try out?
I've been debating this myself. I have a Nexus 5 now that I'm testing with TMO prepaid for a month. So far, the phone is really nice and as you said, the level of development is astounding. BUT, I have to leave VZW in order to keep the phone. That's very hard to do when I get a hefty discount on the service and still have unlimited data. I can get LTE pretty much everywhere I go. With TMO, I'm lucky to get Edge data in some places or even a signal at all inside buildings.
I love the look and feel of the X. It's is a great piece of hardware and with the Dev edition, I could stay on VZW. I also like the fact that it runs basically stock Android along with additions that are actually useful and well done. The dev community is very limited though and will most likely stay that way. Moto was quick to get the 4.4 update out but it remains to be seen if that pace will continue. You would hope so but nothing is guaranteed. The X2 may be out next year putting the update schedule for the current model on the back burner.
I had the original Nexus One and the Galaxy Nexus. I've always been a diehard AOSP guy. Every phone I've owned in between has always been on a custom AOSP based ROM in order to get close to that Nexus experience. I'm attracted to custom ROMs not because they fix bugs, but because they allow me to always stay on a current version of Android (no waiting for carrier updates) and add some nice features to the basic AOSP design. Custom kernels can also improve overall performance and battery life even if you decide to stay stock otherwise. The Nexus line will always have the edge in this regard.
I wanted to be blown away with the N5 and content with TMO but I'm second guessing my decision each day.....
darkgoon3r96 said:
So trying to choose between the Moto X and the Nexus 5, I came across the biggest difference between these phones, their development. Moto X has little to none and Nexus 5 has more than any phone out there. This was an easy win for Nexus 5 I thought. Until I read Moto X users saying that flashing ROMs and kernels are normally to fix issues that the stock versions have and that they don't need Custom ROMs and kernels because what they get is stable, smooth, and lasts long enough (battery wise).
I thought back to why I flash ROMs on Note II and my previous phone SII, and fair enough, I used to do it because I wanted to fix issues that came with stock versions. Now, I hate flashing ROMs, I just want to use my phone. Anyways, looking at the development on the Nexus 5, it seems much of it is to fix the speakers, camera, battery life, etc.
Then I thought that Custom ROMs are important to stay up to date with Google's updates but then Motorola released their update faster than Google did with their Nexus 4. They are also updating their 1.5 year old phones (Not the Razr HD or the Razr HD Maxx probably because of their TI chipset). So it looks like Moto X users are in good hands as far as updates are concerned.
What do you guys think? Would you rather have a fully functional stable stock ROM on a phone that has no development otherwise or would you rather get a phone with tons of development to fix issues that the stock ROM has?
I am asking because there may be an angle to development that I haven't considered. Many customizable things included in ROMs on Nexus 5 are available via Xposed on Moto X.
Click to expand...
Click to collapse
I am running the N5 stock and have no reason to root or flash a custom Rom. Never thought I would say that about my phone but I am actually content with the N5 the way it is. There are some cool features that devs add in but then you get sucked into this never ending flashing frenzy which I have been in for years.
It is good to actually enjoy the phone now and keep the software on it for more then a few days. lol
Anyway, the screen alone on the N5 is enough for what I consider a big step up from the Moto X. I have friends with Moto X's which I actually recommended to them since they are on Verizon and it was being offered for free on contract. I do think it is a great phone with some great features. Not enough there to sway my decision to get one over a N5 though.
I do applaud Motorola for their unbelievable quick update and I bet we start to see some other maunfacturers start stepping up their game as well. We have seen this recently with HTC also.
The question to ask yourself is what is important to you. Another good thing with the Moto X is it generally stocks with the stock Android feel so it almost resembles Nexus software.
Bottom line, when I turn on my N5 after playing with the Moto X, the Moto X does not in any way make me want to buy one for myself.
---------- Post added at 11:34 AM ---------- Previous post was at 11:32 AM ----------
fallingd0wn said:
I've been debating this myself. I have a Nexus 5 now that I'm testing with TMO prepaid for a month. So far, the phone is really nice and as you said, the level of development is astounding. BUT, I have to leave VZW in order to keep the phone. That's very hard to do when I get a hefty discount on the service and still have unlimited data. I can get LTE pretty much everywhere I go. With TMO, I'm lucky to get Edge data in some places or even a signal at all inside buildings.
I love the look and feel of the X. It's is a great piece of hardware and with the Dev edition, I could stay on VZW. I also like the fact that it runs basically stock Android along with additions that are actually useful and well done. The dev community is very limited though and will most likely stay that way. Moto was quick to get the 4.4 update out but it remains to be seen if that pace will continue. You would hope so but nothing is guaranteed. The X2 may be out next year putting the update schedule for the current model on the back burner.
I had the original Nexus One and the Galaxy Nexus. I've always been a diehard AOSP guy. Every phone I've owned in between has always been on a custom AOSP based ROM in order to get close to that Nexus experience. I'm attracted to custom ROMs not because they fix bugs, but because they allow me to always stay on a current version of Android (no waiting for carrier updates) and add some nice features to the basic AOSP design. Custom kernels can also improve overall performance and battery life even if you decide to stay stock otherwise. The Nexus line will always have the edge in this regard.
I wanted to be blown away with the N5 and content with TMO but I'm second guessing my decision each day.....
Click to expand...
Click to collapse
Why not go to a MVNO that uses AT&T towers? Would still be much chepaer then Verizon and they offer much better coverage then T-Mo.
[email protected] said:
I am running the N5 stock and have no reason to root or flash a custom Rom. Never thought I would say that about my phone but I am actually content with the N5 the way it is. There are some cool features that devs add in but then you get sucked into this never ending flashing frenzy which I have been in for years.
Click to expand...
Click to collapse
Don't you want to improve the Audio and the battery life by trying out the kernels and the mods made here?
Anyway, the screen alone on the N5 is enough for what I consider a big step up from the Moto X.
Click to expand...
Click to collapse
I assume you mean resolution? I was under the impression that 1080p and 720p are not that different under daily usage?
It all comes down to your habits. I love flashing new ROM's, I sometimes try multiple ROM's per week. So for me, development means a lot. It's why I switched from the S4 to the N5. The S4 just received 4.3 and was locked down by Knox. Plus, with the N5 being an unlocked phone, you can flash any ROM on any carrier, so you won't ever have to drool over another carrier's ROM.
mjs2011 said:
It all comes down to your habits. I love flashing new ROM's, I sometimes try multiple ROM's per week. So for me, development means a lot. It's why I switched from the S4 to the N5. The S4 just received 4.3 and was locked down by Knox. Plus, with the N5 being an unlocked phone, you can flash any ROM on any carrier, so you won't ever have to drool over another carrier's ROM.
Click to expand...
Click to collapse
I also flash a ton of ROMs every week and also used to enjoy it, but I am getting tired of it now... I want to live life more than flash ROMs (if that makes sense)
darkgoon3r96 said:
If you had bought something like the Moto X one year ago, what feature made by the ROM developers on the Nexus 4 would you really want to try out?
Click to expand...
Click to collapse
Anything and everything. The top reason I don't even consider not getting a Nexus device anymore is the development scene. Look, you're viewing the huge development community on the Nexus line as people who are "fixing" a "broken" stock image. That's not really true. The stock image is perfectly fine. The developers are merely making things that they deem better than how stock handled it. For instance, a developer might think that the on-screen buttons are too large on stock, taking up way too much screen real-estate. They would then develop a way to remove it, but still be able to navigate. They might make something like PIE controls. Now, I may agree that the buttons really are too large, but I like the nav bar. So I might just resize it, instead of working around it.
I guess the point I'm making is, all of those modifications you see to "improve" the stock image are there to "improve" it, but what counts as an "improvement" is completely subjective. There are different people in the world with vastly differentiating opinions about things, so they will make something to improve something else as they see fit. The development sections here on XDA are merely huge repositories of any modification that anyone who was willing to make, made. Looking at them all as collectively-required flashable improvements isn't how it should be viewed. That's the beauty of having a large development community. You can pick and choose, depending on your personal opinions, which modifications are improvements and flash them. Another way to think of it is cookie-cutter vs modular. Do you want a phone that appeals the masses,;a one-size fits all, or a phone that is completely customizable?
darkgoon3r96 said:
Don't you want to improve the Audio and the battery life by trying out the kernels and the mods made here?
Click to expand...
Click to collapse
Battery life has been great on stock for me. Absolutley no complaints here. I have ran so many custom kernels on prior phones and never saw a large boost in battery from them. Lots of times it would actually be worse.
The speaker volume can definitley use a boost and the camera needs some fixing. I know there is some dev work for both of these issues but I am going to hang a little and see if Google fixes it. If not, I might think about rooting solely for those 2 things. If Google fixes it, absolutley no reason for me to root this time around.
Anyway, as a prior flashoholic there is no better phone then a Nexus for people who like to flash Roms and like every feature on the sun. No other phones custom Roms work as good as they do on a Nexus.
Development is like the first determining factor for me when buying phones.
darkgoon3r96 said:
I assume you mean resolution? I was under the impression that 1080p and 720p are not that different under daily usage?
Click to expand...
Click to collapse
Screen size. A 5" screen starts the sweet spot for a device that uses on-screen buttons. I always felt shorted on prior 4.7" screens with on screen buttons. Like there wasn't enough viewing real estate. Sure you can remove the on-screen buttons but then you would need something that always to longer to activate then the actual buttons being present.
I also think the quality and colors of the N5 screen are just gorgous.
darkgoon3r96 said:
So trying to choose between the Moto X and the Nexus 5, I came across the biggest difference between these phones, their development. Moto X has little to none and Nexus 5 has more than any phone out there. This was an easy win for Nexus 5 I thought. Until I read Moto X users saying that flashing ROMs and kernels are normally to fix issues that the stock versions have and that they don't need Custom ROMs and kernels because what they get is stable, smooth, and lasts long enough (battery wise).
I thought back to why I flash ROMs on Note II and my previous phone SII, and fair enough, I used to do it because I wanted to fix issues that came with stock versions. Now, I hate flashing ROMs, I just want to use my phone. Anyways, looking at the development on the Nexus 5, it seems much of it is to fix the speakers, camera, battery life, etc.
Then I thought that Custom ROMs are important to stay up to date with Google's updates but then Motorola released their update faster than Google did with their Nexus 4. They are also updating their 1.5 year old phones (Not the Razr HD or the Razr HD Maxx probably because of their TI chipset). So it looks like Moto X users are in good hands as far as updates are concerned.
What do you guys think? Would you rather have a fully functional stable stock ROM on a phone that has no development otherwise or would you rather get a phone with tons of development to fix issues that the stock ROM has?
I am asking because there may be an angle to development that I haven't considered. Many customizable things included in ROMs on Nexus 5 are available via Xposed on Moto X.
Click to expand...
Click to collapse
I just got rid of my moto x for the N5 for this very reason. The moto x is a great device and probably the best carrier controlled device to date.
That being said, it drove me nuts to be locked down with a locked bootloader and no development. Knowing the n5 is open and has all the Dev support means I have control over MY phone, not AT&T and not Motorola.
After dealing with the locked down s4, I promised myself I would never get another device without an unlockable bootloader. I caved when the moto x came out and as I said it's one amazing device but at the end of the day, I'll be sticking with nexus devices from here on out.
To me it's not worth giving up that freedom but for you it may not matter.
Sent from my Nexus 5
Development totally cones into it for me. One of the biggest considerations.
-----------------------
Sent via tapatalk.
I do NOT reply to support queries over PM. Please keep support queries to the Q&A section, so that others may benefit
brooksyx said:
Development is like the first determining factor for me when buying phones.
Click to expand...
Click to collapse
rootSU said:
Development totally cones into it for me. One of the biggest considerations.
Click to expand...
Click to collapse
Please elaborate. I want to know which features exactly do Custom ROMs provide that you won't be able to get from the xposed mod that you would want that much.
capathy21 said:
That being said, it drove me nuts to be locked down with a locked bootloader and no development. Knowing the n5 is open and has all the Dev support means I have control over MY phone, not AT&T and not Motorola.
Sent from my Nexus 5
Click to expand...
Click to collapse
If I do get the Moto X, then I will get the Developer Unlocked model.
brooksyx said:
Development is like the first determining factor for me when buying phones.
Click to expand...
Click to collapse
Same here, after my first Nexus phone, I could never go back to a phone that didn't have a strong dev. community behind it. For me; tablets and phones are as much about the journey of playing with ROM/kernel/mods as they are a communication device.
darkgoon3r96 said:
Please elaborate. I want to know which features exactly do Custom ROMs provide that you won't be able to get from the xposed mod that you would want that much.
If I do get the Moto X, then I will get the Developer Unlocked model.
Click to expand...
Click to collapse
No stock rom mod can touch the stability and features of cyanogenmod. It is the only way to do anroid. In fact I prefer iOS over stock android. But CM is awesome.
brooksyx said:
No stock rom mod can touch the stability and features of cyanogenmod. It is the only way to do anroid. In fact I prefer iOS over stock android. But CM is awesome.
Click to expand...
Click to collapse
To be honest, CM's future plans SERIOUSLY excite me.. Like that recent conversation feature
CyanogenMod, AOKP, AOSPA support, along with great kernel devs. The Nexus 5 is essentially guaranteed support for these things, and these are things I like.
darkgoon3r96 said:
Please elaborate. I want to know which features exactly do Custom ROMs provide that you won't be able to get from the xposed mod that you would want that much.
Click to expand...
Click to collapse
Who said anything about roms or features? Its all about kernels.
But if you look at ROMS like PAC, you'll see what features true roms can offer over xposed
-----------------------
Sent via tapatalk.
I do NOT reply to support queries over PM. Please keep support queries to the Q&A section, so that others may benefit
Hey guys, I'm pretty sure no one has seen me in the G Flex section. I did work for the M8, G3 etc back in the day. I just picked up a G Flex the other day with T-Mobile excited to put Lollipop on it. Came home and searched the threads to see there isn't lollipop for it nor is there any AOSP ROMs for it. I understand the issues behind it but I just wanted to say these issues doesn't prevent ASOP running on our G Flex. There's still possibilities. I came from the ZTE Zmax, and we had 1 dev working on our phone and got CM12.1 up and running with full stability in a month. I read somewhere that LG confirmed that the G Flex will NOT get lollipop because of some issues that was causing it to be buggy. LG basically stalled development on the G Flex until the 18 months that Google gave as an requirement for Software updates was over. The 18 month period for the G Flex ended back in May. So LG basically used that as an excuse to not update our phone, which is very stupid and it sucks but we have developers in this community that are smarter than LG Devs. We don't need a kernel source to build a functional kernel, even though a source would help tremendously. The ZTE Zmax, ZTE Awe ($30 phone), LG Tribue ($40 Phone) are all running CM12.1 with no kernel source and locked Bootloaders. For sensor and Audio issues you could simply TRY and use libs from other devices that compare like the G2. That's what the dev for the ZTE Zmax did. I see development started for lollipop but ended months ago. I also see a couple people working on CM11 and others quietly working on their own CM12 build. I'm not here to criticize, because I know this kind of stuff isn't easy. I'm just simply giving advice on something that may or may not have been tried yet. It's been almost a year since lollipop launched and you would expect a Flagship device to have lollipop or at least an AOSP ROM by now. Android M is being launched in a few months. Let's get this project back up and running and don't stop until its finished! We have plenty of donators including me. If help is needed ask other experienced Devs, CM Devs, even Devs on the Android Forums. This phone has way too much potential to just forget about.
I'm already accepting that we may not get anything and gotten used to a tweaked stock rom. There's a reason cheaper phones have lollipop already, they're going to have larger user bases by default. There is really no reason to pick up a flex even under an upgrade deal when there are plenty of competing phones that already have thriving communities, and I wish I did more research before I got mine. So really it comes down to someone only picking it up to get something different and even hindered.
That said, if some crazy dev does decide to pick the phone I'll be pleasantly surprised but preaching like this forum has been for weeks now isn't going to do anything when we have no devs actively working or even looking at us. I'm really hoping I get proven wrong and I'm definitely ready to throw some money at a reputable dev but seriously now, we don't even have stable cm11 ports and people are hoping for lollipop.
RushNY said:
I'm already accepting that we may not get anything and gotten used to a tweaked stock rom. There's a reason cheaper phones have lollipop already, they're going to have larger user bases by default. There is really no reason to pick up a flex even under an upgrade deal when there are plenty of competing phones that already have thriving communities, and I wish I did more research before I got mine. So really it comes down to someone only picking it up to get something different and even hindered.
That said, if some crazy dev does decide to pick the phone I'll be pleasantly surprised but preaching like this forum has been for weeks now isn't going to do anything when we have no devs actively working or even looking at us. I'm really hoping I get proven wrong and I'm definitely ready to throw some money at a reputable dev but seriously now, we don't even have stable cm11 ports and people are hoping for lollipop.
Click to expand...
Click to collapse
That's the problem, that fact that Lollipop is almost a year old and we don't even have 4.4.4 KitKat. We're about 2 years behind. This is why I said, lets go around and recruit. There are some Devs that don't even need the device in hand to build. They build and use testers. It seems like when there are kernel related issues Devs give up because they have little to no kernel knowledge. There's ways around that. Like I said, the CM11 port may not be stable but its still silently being worked on, just not finished in the timeframe people expect. And I've seen a couple people quietly working on their own CM12 builds. CM12 is already booting, its just in the same condition as CM11, which no one figured out how to fix yet, which is Sound, Bluetooth etc. I believe this device will get Lollipop soon, but only if people are eager and motivated to get the job done.
Sent from my LG-D959 using XDA Free mobile app
Just want to say that im finished with the Flex. Just Sold it and bought an Huawei Mate 7... and it is just awsome FU LG! Never again!
mckoffly said:
Just want to say that im finished with the Flex. Just Sold it and bought an Huawei Mate 7... and it is just awsome FU LG! Never again!
Click to expand...
Click to collapse
I have my Huawei Mate 2 with lollipop. It goes for 2 days with heavy use when it had Android 4 so I'll have to see what it will do now. The reason I put it down was because the camera sucked but with the update it seems to work fine. I love the LG form factor with the power and volume buttons and even the gui is cool but I'll try the Mate 2 and see. Mate 2 has a brighter screen, but the lg has wifi calling so lots of pluses and minuses. My fried got the Mate 7. Awesome phone but he was used to the long batter of the Mate 2 so returned it.
You guys MIGHT wanna check out playfulgod's CM11 thread, all the new development from the past month has been going on there. We now have sound working!!!
The d959
Does anyone know if the latest cm11 build with sound and data for the d959 will work? Saw the multiple .zip files but none for 959 in the main thread(cm11)
Read! Reply over there BTW, more likely to get help. And he's gonna build for d959 when data works on lswhateveritscalled. Sound works on all.
I know we've all heard it before. I ditched this phone to basically get lollipop. But after a few weeks I realized what I'd been hearing since launch. I don't hold this screen right up in my face. I don't care about pixels. What I do care about? The awesome size and battery life. Mine never stutters. Forget lollipop. I'm fine with the flex the way she is. I would like to see more development. But if we get it we do and if we don't we don't. I still have an awesome and powerful phone and cm12.1 would run awesome.
wcr84 said:
I know we've all heard it before. I ditched this phone to basically get lollipop. But after a few weeks I realized what I'd been hearing since launch. I don't hold this screen right up in my face. I don't care about pixels. What I do care about? The awesome size and battery life. Mine never stutters. Forget lollipop. I'm fine with the flex the way she is. I would like to see more development. But if we get it we do and if we don't we don't. I still have an awesome and powerful phone and cm12.1 would run awesome.
Click to expand...
Click to collapse
http://www.phonearena.com/news/Comp...ow-leaks-includes-Samsung-Sony-and-LG_id74400
Sent from My LG G Flex LG-F340K Stock KitKat V20D on LTE Network using XDA Free Mobile app
/me lurks
This thread is a good initiative...flex forums have been so dead over the months, it pains me to see such a great phone relegated to the grave...here to help..can donate and test
Hey Everyone,
I'm fairly new to the Android community. I got an R1 and have since rooted it and de-bloated it. But I was wondering what the state of Cyanogenmod is. I've heard they've stopped development on it. Is there any chance they (or someone) will add support for the Blu R1 HD?
I'm interested in getting a full AOSP experience without the closed source google services kit software.
-Jeff
Don't hold me to this, but I personally believe CM13 support will not be too difficult. It'll be later versions of Android that will pose a problem.
Also, CM13 for the R1 HD is being worked on. It's just a matter of time.
ss2man44 said:
Don't hold me to this, but I personally believe CM13 support will not be too difficult. It'll be later versions of Android that will pose a problem.
Also, CM13 for the R1 HD is being worked on. It's just a matter of time.
Click to expand...
Click to collapse
Oh, it is? Thats great. I have plenty of patience
I'm in the same exact boat, have rooted/de-bloated and installed trebuchet and other features, but really would like to see CM support.
jeffburg said:
Hey Everyone,
I'm fairly new to the Android community. I got an R1 and have since rooted it and de-bloated it. But I was wondering what the state of Cyanogenmod is. I've heard they've stopped development on it. Is there any chance they (or someone) will add support for the Blu R1 HD?
I'm interested in getting a full AOSP experience without the closed source google services kit software.
-Jeff
Click to expand...
Click to collapse
ss2man44 said:
Don't hold me to this, but I personally believe CM13 support will not be too difficult. It'll be later versions of Android that will pose a problem.
Also, CM13 for the R1 HD is being worked on. It's just a matter of time.
Click to expand...
Click to collapse
I don't understand too much about android ROM development, but what would prevent CM14 development/future versions from being developed?
contacted Blu and they told me that they are looking forward to working on updating as many devices as they can to the new platform as soon as possible!......righhtttt!!!
Once the dev. on the kernel is in line for a cm13 port , cm14 (which is already being worked on) hopefully might be a possibility.
Fullmetal99012 said:
I don't understand too much about android ROM development, but what would prevent CM14 development/future versions from being developed?
Click to expand...
Click to collapse
Me either, but I think it would be the drivers. I would suspect with CM13 they can use it's current drivers but with anything Android 7.0 they would need new drivers.
Blu has updated a few devices haven't they? They have to develop the drivers and then run it through the carriers approval I believe? I'm sure they are looking at how much money they expect to make from the R1 HD in 4-6 months. Some of this might depend on their plans of a new phone they plan to release. R1 HD is a big seller.... but what about in 6 months?
A device tree is very likely being compiled for this device now that the kernel source has been released. A CM 13 build I'd imagine is also in the works with other custom roms likely to follow. I would just sit back and keep your eye out. As soon as customs ROMs are released you should easily find them in R1 HD Forums on XDA. I wouldnt hold your breath for anything beyond android 6.0 on this device tho! Marshmallow ROMs will be more then sufficient for these devices and most devs really don't like to hear when this or that will be updated or released.
Jstame said:
I wouldnt hold your breath for anything beyond android 6.0 on this device tho! Marshmallow ROMs will be more then sufficient for these devices and most devs really don't like to hear when this or that will be updated or released.
Click to expand...
Click to collapse
No, I'm pretty sure once devs can build AOSP 6.0 for this device, it'll get 7.0, even if BLU abandons it. I mean, you do realize that you're on a website famous for, among other things, providing unofficial updates to unsupported devices, right?
cmason37 said:
No, I'm pretty sure once devs can build AOSP 6.0 for this device, it'll get 7.0, even if BLU abandons it. I mean, you do realize that you're on a website famous for, among other things, providing unofficial updates to unsupported devices, right?
Click to expand...
Click to collapse
Yeah I know exactly where I am bro. The fact that its such a low cost device and the unlikely hood of Blu updating the kernel source to 7.0 makes it very very unlikely there will ever be any kind of 7.0 update on these phones. Plenty of unofficial updates of ROMs are released but not many are above the "official" releases like going from 5.0 to 6.0 or 6.0 to 7.0. Were still waiting to see how Devs react to the R1 HD now since its not a big name mainstream device. So like I was saying if we don't see Blu update to 7.0 which is doubtful, we prob won't see any kind of Nuaget. Not saying its impossible without a Blu update just wouldn't hold my breath waiting on a Dev to take on that task on this particular device....
Jstame said:
Yeah I know exactly where I am bro. The fact that its such a low cost device and the unlikely hood of Blu updating the kernel source to 7.0 makes it very very unlikely there will ever be any kind of 7.0 update on these phones. Plenty of unofficial updates of ROMs are released but not many are above the "official" releases like going from 5.0 to 6.0 or 6.0 to 7.0. Were still waiting to see how Devs react to the R1 HD now since its not a big name mainstream device. So like I was saying if we don't see Blu update to 7.0 which is doubtful, we prob won't see any kind of Nuaget. Not saying its impossible without a Blu update just wouldn't hold my breath waiting on a Dev to take on that task on this particular device....
Click to expand...
Click to collapse
"Not a big name mainstream device"
Totally man. The number 1 selling phone on Amazon isn't a "big name, mainstream device." If anything this phone is proving how Android development is dwindling.
There was a article that said Blu would release Android 7.0 for the R1 HD. I don't know how reliable or legitimate it is.
dba415 said:
There was a article that said Blu would release Android 7.0 for the R1 HD. I don't know how reliable or legitimate it is.
Click to expand...
Click to collapse
They probably did say it, BLU has a history of promising upgrades, they rarely deliver. I don't know if the blame is theirs or their Chinese partners, not delivering. But even at that if BLU was smart they would hire a team of developers to actually develop roms instead of just simple branding tweaks on the manufacturer supplied firmware. BLU needs to tweak their sales routine, currently they sell flashy looking phones on the cheap, but if they would change their focus to selling entry to mid level phones with better support, they could really make a name for themselves.
Dear OnePlus 3t owners,
Is it sensible to buy a new OP3T after OP decided to kill updates post-O?
On this device, easy root, no updates but plenty of community support.
On others (S8, XZ Premium, other mainstream flagships), loss of features with root, somewhat more updates with less community support.
Please help me take my decision, and any and all help is greatly appreciated!
It depends if you want a phone to play around and mod or you want a phone to have longer updates although longer updates are not a guarantee in any brand even Google promises updates for 2 years only. 3t is still a pretty good device and I think we'll have good dev support for atleast a couple of years
Sent from my OnePlus3T using XDA Labs
No update ? Hmm, don't know where you see this, OpenBeta 13 has just been release today.
Personally, I bought the OnePlus 3T like one week ago for 350e on Ebay, very happy with with.
Before it, I bought a OnePlus 5 day one, and, well, if I'm here today, it's because I was very disappointed (*cough* Jelly Effect *cough* ), and I bought the OnePlus 3T because I need a new device right now: I prepare a trip in South Korea, and need a new device to replace the time bomb OnePlus 2 (sorry about my life topic).
I share the idea about the fact that the OnePlus 3T was the true Flagship Killer: low price for very good specs.
You can see that the device is still in top 3 devices on XDA (behind Samsung Galaxy S8/S8+ and LG G6), and for me, it's an indicator that the OnePlus 3T still has a bright future.
So yeah, OnePlus won't update the OnePlus 3T after Android O (but still security update tho), but he, we are on XDA, so plenty of custom ROMs available!
After all, I can't either ""force"" you to buy or not the OnePlus 3T. It depends on multiple points
-How many you want to put in your phone ?
-What is a good smartphone for you ?
-Do you care about officials updates of custom ROMs is ok for you ?
1. No updates: I actually meant "no major version updates".
2. So you have bought the 5 and saw that the 3T was better in comparison?
3. Are custom ROMs stable as stock on this device? (My 1st OP device, hope ROMs are as stable as stock to the contrary of Samsung)
4. Is the camera on custom ROMs any good (as in decent) without camera blobs from OnePlus?
Thanks for your advice! I'm actually biased towards buying the device but I have had my reservations
Well, I'm a tinkerer but I really prefer more updates as I do prefer longevity (3-4 years of college, not enough $$$ to spend on phones). Thank you a lot!
I don't think it'll matter. Android O will be a nice send off and I think said that they'll provide security updates also. The community will support this phone for many android revisions and groups/people like PA or Sultan got the same camera quality on their AOSP roms
Also, you said that you bought the 3T to replace your "time-bomb" OP2. How is the 2 a time bomb exactly? And could the 3T become one too?
I'm content with the device on O but as soon as P rolls out a problem arises. Community ROMs are not exactly stable (coming from Samsung, no idea w/ OP3T though) and I've read somewhere that PA and/or Sultan received the blobs from OP through bribery or something ... What do you think?
So you have bought the 5 and saw that the 3T was better in comparison?
Click to expand...
Click to collapse
Jelly Effect is a deal breaker for me. Search for it on internet, you will see.
Are custom ROMs stable as stock on this device?
Click to expand...
Click to collapse
For now, I don't know. I just flash a custom kernel on my device, but still under OxygenOS for now.
Is the camera on custom ROMs any good (as in decent) without camera blobs from OnePlus?
Click to expand...
Click to collapse
As I said, I don't know. But some recognized devs build ROMs which camera which seems to be as good as stock one (such as SultanXDA's ROM or ParanoidAndroid)
Also, you said that you bought the 3T to replace your "time-bomb" OP2. How is the 2 a time bomb exactly? And could the 3T become one too?
Click to expand...
Click to collapse
The OnePlus 2 was produced with the Snapdragon 810, which is, let's be honest, a sh*t. My user experience with it was pretty bad. Also, I don't know if you saw, but the Nexus 6P (which also has the Snapdragon 810) is victims of problems with this processor: actually, some users have a phone which can't even boot anymore. A user find a solution, but actually, the phone now uses 4 cores (the little cluster) instead of 8 (little + big cluster): I don't want the OnePlus 2 to ends like this, so I bought a new phone, just to be sure.
Aaaaand I f*cked up my answer. Of course, this posts contains answer to your questions @WaseemAlkurdi
Custom roms are far more stable on the 3t then on Samsung devices. Less hacking needed.
Updates are kinda over rated at this point. With the 3t you can just build it yourself. Though I would avoid Los based or PA based roms. Those tend to have the most issues with things like instability.
Think of it this way: would you buy this phone and use it as is, or would you out a custom ROM on it?
It might not get any updates from UP after O, but it's gonna get at least 3 more years of support from Lineage and others.
There are a plethora of "stable" custom built ROMs by several very talented developers.
To say that community ROMs are not stable is an EXTREMELY uninformed comment.
I've been running some form of a custom ROM for the past 7 years over a a multitude of phones following well known developers that in my opinion and experience put out better device software than the factory.
If you do choose the OP3T, you'll not be disappointed as it's a quality device with excellent community support.
Like could I build "OxygenOS P" myself?
And if LOS and PA ROMs aren't stable, is AOSP so? And that makes for a tradeoff for camera quality, as an earlier comment said that camera is the best on PA and Sultan (Sultan's being LOS based AFAIK)
@giant22000
Seems like it's going to be the OnePlus 3t after all, and what remains to be done is convincing my dad that an unknown China OEM (in local market's view - not our view) can make solid hardware.
"To say that community ROMs are not stable is an EXTREMELY uninformed comment."
This is relative. Coming from various Samsung devices, namely the Galaxy Grand 2 and the Galaxy Star (the crappiest device known to mankind) and servicing others including flagship models, it does happen that custom ROMs are, to say the best, variable in stability, ranging from crappiest (CM on the Galaxy S Duos and on the Star) to semi-stable (the stuff on high-end phones.
@ast00
I am a tinkerer by nature, no Android phone is mine unless the bootloader is unlocked, custom ROM, kernel, overclock, and later on, development.
I am only concerned about official updates as this may mean eventually being deserted by the community. Is this the case here?
@casual_kikoo
Thanks for your detailed answers!
Yes AOSP tend to be more stable then the other two. Just look at the thread and you will see issues with bootloops and other things. Yet AOSP based roms do not suffer from this.
The camera is good enough no matter the range. I tested both and to be honest it made little difference.
No you are not gonna build Oxygen OS as it is closed source but then again why would you want to?
Stability, mate. Heard that OOS is the most stable, then comes AOSP, then comes LOS.
And if it were possible to build OOS, the update issue would be fixed of course. But alas, it isn't possible, as you said.
No. Most ROMs run on the 3 and the 3T. I mean you flash the same zip for both phones.
This is good because our community is the size of 2 phone's communities. You will have plenty of support later on.
Take nexus 5 as example, its still getting regular rom updates such as PA or lineage, this device will be no different.. it will receive android updates from xda community for a long time
Hey I just got this phone a couple of weeks back and while its been awhile I used to be a recognized developer on XDA years ago and was wondering if there are any active developers (still) for this device as I notice the list of active development is basically 0. I am planning on building for the device but would like to know who if anyone is developing currently and what the goals are as it seems without anything outside of stock deodexed and (really the biggest one being the kernel with twrp) we have nothing for this phone even now. This makes it seem like either the proprietary information is extremely difficult (although I see the tree is working for the most part) or we just lack developers. Which is it? Thank you and I apologize if this is in the wrong place. I'd like to see what is the current state of things and see if any developers want to work together on this and at least get a clean aosp build or lineage os build. Stepping stones. Certainly with the Note being as similar as it is this shouldn't be lacking to the state it is today.
Hello jcole20
That would be awesome if some devs started doing something with the RP2! If I had the knowledge, I would!! I've had the RP2 since June of this year. I had some issues with it at first but they have been worked out. I really like the phone and it would be cool to see some devs show the RP2 some love lol. Hopefully you can get something started! Take care!
Dennis
jcole20 said:
Hey I just got this phone a couple of weeks back and while its been awhile I used to be a recognized developer on XDA years ago and was wondering if there are any active developers (still) for this device as I notice the list of active development is basically 0. I am planning on building for the device but would like to know who if anyone is developing currently and what the goals are as it seems without anything outside of stock deodexed and (really the biggest one being the kernel with twrp) we have nothing for this phone even now. This makes it seem like either the proprietary information is extremely difficult (although I see the tree is working for the most part) or we just lack developers. Which is it? Thank you and I apologize if this is in the wrong place. I'd like to see what is the current state of things and see if any developers want to work together on this and at least get a clean aosp build or lineage os build. Stepping stones. Certainly with the Note being as similar as it is this shouldn't be lacking to the state it is today.
Click to expand...
Click to collapse
I am sure people would love to see some device specific development. I have read that since the release of project treble most people just flash the system image from other roms. I specifically would love to see a stockish rom so I don't loose chroma but still get updated security patches.
I ordered this phone from amazon to try out. I am checking out the community and stuff in the 10 day trial period they give you. I really like the phone... i just hate the software side of things. I feel like its super premium hardware with outdated software... that probably isnt even going to get security patches. Anyway... off to see whats available.
Krazy_Calvin said:
I ordered this phone from amazon to try out. I am checking out the community and stuff in the 10 day trial period they give you. I really like the phone... i just hate the software side of things. I feel like its super premium hardware with outdated software... that probably isnt even going to get security patches. Anyway... off to see whats available.
Click to expand...
Click to collapse
Most functionalities work on Pie GSIs out-of-box (you need to manually install ims.apk in order to receive SMS while on LTE, see relevant threads here, or look for it on some GSI threads such as Havoc 2.9). exFAT also works on supported GSI (with arter97's kernel), while it's not supported on stock. The only problems I have so far are bluetooth-related, and also the inability to set SELinux to permissive (not sure which might be the real cause as arter97 stated the SELinux could be permissive).
Bluetooth media audio doesn't work at all on GSI, partly due to the crippling overlays (which prevents aptX from working, and probably some other limitations). Phone calls work with a bluetooth headset, but for some reasons I couldn't properly route phone calls to my Huawei Watch 2 (which means I always have to take the call from my phone directly).
Given the mostly positive result with numerous GSIs (and that some users are happy with stock ROM, or stock-based ROM modifications), active ROM developments for the device itself doesn't seem to be at a high priority (as some might be able to contribute patches for this device to their favorite GSI instead)...
I'm currently working on my own build of LOS. I haven't seen to much active development either I'm new to rom building but looks like we could use all the help we can get!
I think the only active dev we have for this phone is Arter97's kernel and people tinkering with GSIs to get them working as they should. I wish there was more being done with the stock ROM because I like a lot of it's features, but am having a hard time dealing with it's overall instability. I'd be happy to help develop or test in whatever way I can, though.
jcole20 said:
Hey I just got this phone a couple of weeks back and while its been awhile I used to be a recognized developer on XDA years ago and was wondering if there are any active developers (still) for this device as I notice the list of active development is basically 0. I am planning on building for the device but would like to know who if anyone is developing currently and what the goals are as it seems without anything outside of stock deodexed and (really the biggest one being the kernel with twrp) we have nothing for this phone even now. This makes it seem like either the proprietary information is extremely difficult (although I see the tree is working for the most part) or we just lack developers. Which is it? Thank you and I apologize if this is in the wrong place. I'd like to see what is the current state of things and see if any developers want to work together on this and at least get a clean aosp build or lineage os build. Stepping stones. Certainly with the Note being as similar as it is this shouldn't be lacking to the state it is today.
Click to expand...
Click to collapse
Yeah, it’s definitely just total lack of interest from other devs. We even have a guy with a prototype Razer Phone 2 with an intact DRM partition and unlocked bootloader (Allowing Netflix HD and Vudu HDX) but we couldn’t even pay anyone to try to port it.
I think if we had a fully working AOSP tree that it would possibly bring other devs into the scene. Who knows though, it has never been a popular device despite how great it is.
LSS4181 said:
Most functionalities work on Pie GSIs out-of-box.
Click to expand...
Click to collapse
Noob question:
Do we have to wait for a stock Android 10 for the device to be able to flash Android 10 GSIs?
EMJI79 said:
Noob question:
Do we have to wait for a stock Android 10 for the device to be able to flash Android 10 GSIs?
Click to expand...
Click to collapse
A stock Android 10 (which means a stock vendor image for Android 10) is not necessarily required to have a usable Android 10 ROM (though it may speed up the development to some extent, if it does have one), but for GSI, having a stock Android 10 vendor image can be better (currently it's a hit-or-miss on existing Android 10 GSIs).
Another device that I have, Google Pixel C, never had stock Android 9 (so never had stock vendor images for Android 9, only for up to Android 8.1), but custom Android 9 ROMs are already available (thanks to followmsi's efforts) and are working well. For Android 9 ROMs, the build system builds new vendor images along with system image.
It's just whether we're going to see our device's trees being made possible, so we can start from there to develop our own custom ROMs. The existing materials might be a good starting point in making trees.
- Working with proprietary blobs (from Lineage)
- arter97's kernel (can be useful for making a kernel tree, though one can also consider using stock kernel source as a base)
- Razer factory images and kernel sources (for studying stock ROM/kernel details, and extracting necessary system and vendor blobs)
If you can port LineageOS to this device, great!
I don't understand why people aren't flocking to this device. I came from the LG G6 that probably will be stuck on Oreo forever that is way more popular. The RP2 is cheap, has killer specs + a micro SD card slot + a newer version of Android. Should be a developers dream, you would think. *shrug*
Not sure if anyone's active on this device at present. With RP2's 9.0 MR2 available on the official factory images page the latest proprietary blobs (as well as stock kernel source) are now publicly accessible.
Actually arter97 once mentioned that his RP2 kernel is almost inline with his OP6 kernel (which is also sdm845 and shares some similarities), so it's possible that OP6 (enchilada) trees may be a good starting point, but I'm not sure if any configurations are needed to keep 120Hz working as high refresh rate is relatively uncommon.
My time is very limited so I won't be able to dedicate too much time to experiment on this. At present most functionalities work fine with GSI (including Bluetooth, although tricky and aptX still not working).
IDK how relevant this is anymore but as a new razor phone 2 user to be soon I have been keeping up and it seems that @f(x)THaxxorX could be a possible candidate of what you're looking for I've been keeping up with development on the phone seems like he is doing pretty well even if we get patched gsi which properly work is better than nothing.