Database Develop

Development is going to be good!

Alot of Developers have bought this phone!! development for Xperia T / TX and V is going to be good! so far we have 2 elite developers 2 recog developers,, correct me if i am wrong

FXP have 4 members
Bin4ry, Defer, Kali, Jerpelea

Codeworkx!
Tilal6991 too for paranoid android

Gok for kernel is gonna be beast.

Lol @ 4. Good start but not exactly a lot. Yet.
...

Not to doubt or anything but, what is Sony support looking like? I know dev support often is limited by the manufacturer. This isn't exactly the most active section either. Will having devs draw people in? Or will lack of people pull devs away?
Strong chance I'm getting the att version (TL) but, I will admit to being worried about lack of support after a year and having a year left one contract with no official support and lack of dev support because something flashier came out.

Snow_fox said:
Not to doubt or anything but, what is Sony support looking like? I know dev support often is limited by the manufacturer. This isn't exactly the most active section either. Will having devs draw people in? Or will lack of people pull devs away?
Strong chance I'm getting the att version (TL) but, I will admit to being worried about lack of support after a year and having a year left one contract with no official support and lack of dev support because something flashier came out.
Click to expand...
Click to collapse
well this is my first sony device, but looks promising, if sony stays open and doesn't screw up like samsung did, even if they are on updates, we'll have CM team for regural updates. actually, i hope this is first device i'll have for more than a year.
we'll see.
Sent from my Xperia T

Snow_fox said:
Not to doubt or anything but, what is Sony support looking like? I know dev support often is limited by the manufacturer. This isn't exactly the most active section either. Will having devs draw people in? Or will lack of people pull devs away?
Strong chance I'm getting the att version (TL) but, I will admit to being worried about lack of support after a year and having a year left one contract with no official support and lack of dev support because something flashier came out.
Click to expand...
Click to collapse
Support is looking good for devs to get started and this can be seen from the speed CM10 has become available and is progressing on this device. I don't see the lack of activity in this forum as a bad thing and for a dev it's a good thing because they're not hassled every 2 mins with the same repeated support questions or for ETA's (don't do it ). Devs don't choose devices because they're popular, they choose them because they're good to work on and because they personally like the device as remember this is a hobby after all. I for one, if I do get this phone will hope for it to remain as one of the quieter forums but once people start finishing their contracts I can see it attracting a number of people. I finish mine end of this month so that's when I'll be choosing but that choice is based on how easy it'll be to work with as I like to have a play with compiling myself but only for myself really.

I actually chose this device precisely hoping that it wouldn't become too popular. It becomes crazy when people start almost harassing you for a release.
With a less popular device its much more fun.

^aha your right
hello developer!

i think xperia t will get popular because it is the bond phone and the tx looks great in terms of design so it will get popular

Snow_fox said:
Not to doubt or anything but, what is Sony support looking like? I know dev support often is limited by the manufacturer. This isn't exactly the most active section either. Will having devs draw people in? Or will lack of people pull devs away?
Strong chance I'm getting the att version (TL) but, I will admit to being worried about lack of support after a year and having a year left one contract with no official support and lack of dev support because something flashier came out.
Click to expand...
Click to collapse
TL developer support is going to highly depend on the bootloader locking situation.
As I understand it, AT&T has a bad habit of forcing bootloader locks. I refuse to support any device that has a locked bootloader which is not officially unlockable - even if the lock gets broken unofficially, it's the principle of the thing.
tilal6991 said:
I actually chose this device precisely hoping that it wouldn't become too popular. It becomes crazy when people start almost harassing you for a release.
With a less popular device its much more fun.
Click to expand...
Click to collapse
Yeah. The Infuse was a less popular device, and as a result, the developer community was highly cooperative for a while. Unfortunately, the device itself was a nightmare to work with so it was ditched by many. Although, interestingly enough, now that some of the worst aspects of this device development-wise have been identified, the Infuse is becoming kind of fun to work with again.
In the case of the T - all evidence seems to indicate that it's going to be a highly pleasant device to work with, AND if it's not a super-popular device, it may have a more pleasant development community than some of the more popular devices.
There's an existing well-established team of developers with Sony experience, AND there are also a number of Samsung Exynos refugees that have already made the jump or (in my case) are just waiting to see what their local version of the T has to offer.
That said - based on the developers I've seen hopping over, things are going to be heavily weighed in the AOSP-based firmware side of things. Sony's recent devices have become very attractive to developers of AOSP derivatives due to:
Sony's cooperation with the community in terms of technical information and source releases (see DASH)
Most Sony devices are based on Qualcomm chipsets, and over the past year, CodeAurora has emerged as a high quality reference codebase. (CAF has existed for a long time, but it's not really until this year that I saw people using it heavily.)
Sony's explicit AOSP support, both in terms of binary releases to support JBQ's Xperia S project, and frequent commits to AOSP. In fact, they have one developer working part-time on the AOSP Xperia S tree!
However, going back to Snow_fox's comments - if you want a device that is guaranteed not to be dropped early, purchase a Nexus. With any non-Nexus device, you are always taking risks.
Look at the Samsung Exynos situation - A year ago, Samsung devices were looking like your best bet for ongoing developer support. However, over the past year, a variety of things have changed:
Samsung constantly releases broken HALs that require all sorts of workarounds, and don't play nicely with backwards-compatibility solutions that work on other devices. ICS and JB bringup on Exynos4 devices has been an utter nightmare, leading to the entire team of CM on Exynos devices burning out or coming damn close to it
Samsung decided to use their phones as an outlet for gigantic batches of defective eMMC flash chips. They put workarounds in their firmware but didn't tell anyone. The end result is that you have to tread carefully with any 2011-model Samsung device. Their poor handling of the eMMC disaster has left a sour taste in many developers' mouths.
As a result, many developers are leaving, not necessarily for a device that is flashier, but one that is at least more developer-friendly. I think that in many cases, the Xperia TL will be a downgrade for me compared to my Galaxy Note... But dealing with the Exynos in the Note is driving me utterly insane.

AvRS said:
Support is looking good for devs to get started and this can be seen from the speed CM10 has become available and is progressing on this device. I don't see the lack of activity in this forum as a bad thing and for a dev it's a good thing because they're not hassled every 2 mins with the same repeated support questions or for ETA's (don't do it ). Devs don't choose devices because they're popular, they choose them because they're good to work on and because they personally like the device as remember this is a hobby after all. I for one, if I do get this phone will hope for it to remain as one of the quieter forums but once people start finishing their contracts I can see it attracting a number of people. I finish mine end of this month so that's when I'll be choosing but that choice is based on how easy it'll be to work with as I like to have a play with compiling myself but only for myself really.
Click to expand...
Click to collapse
I will have to decide on December 1st what phone I'm going to myself.
I personally understand the appeal of a quieter forum where the same issues aren't asked every couple of minutes.. Once or twice, I've actually had trouble finding a solution wading through the, "How do I ________" and most of them had the response, "do a search" :silly:
tilal6991 said:
I actually chose this device precisely hoping that it wouldn't become too popular. It becomes crazy when people start almost harassing you for a release.
With a less popular device its much more fun.
Click to expand...
Click to collapse
Yeah.... there are a lot of ungrateful members. I find myself in an awkward position because, I'm not skilled enough to develop a ROM but, I'm know I'm reliant on whatever XDA puts out to stay up to date with the latest ROMs.
Entropy512 said:
TL developer support is going to highly depend on the bootloader locking situation.
As I understand it, AT&T has a bad habit of forcing bootloader locks. I refuse to support any device that has a locked bootloader which is not officially unlockable - even if the lock gets broken unofficially, it's the principle of the thing.
Click to expand...
Click to collapse
If I were in a position to take that stance, I would myself.
[/QUOTE]
There's an existing well-established team of developers with Sony experience, AND there are also a number of Samsung Exynos refugees that have already made the jump or (in my case) are just waiting to see what their local version of the T has to offer.
That said - based on the developers I've seen hopping over, things are going to be heavily weighed in the AOSP-based firmware side of things. Sony's recent devices have become very attractive to developers of AOSP derivatives due to:
Sony's cooperation with the community in terms of technical information and source releases (see DASH)
Most Sony devices are based on Qualcomm chipsets, and over the past year, CodeAurora has emerged as a high quality reference codebase. (CAF has existed for a long time, but it's not really until this year that I saw people using it heavily.)
Sony's explicit AOSP support, both in terms of binary releases to support JBQ's Xperia S project, and frequent commits to AOSP. In fact, they have one developer working part-time on the AOSP Xperia S tree!
However, going back to Snow_fox's comments - if you want a device that is guaranteed not to be dropped early, purchase a Nexus. With any non-Nexus device, you are always taking risks.
[/Quote]
That unfortunately isn't really entirely an option for me. I'm on a family plan and have no capability of getting out of it at the moment. I don't have enough data to make 16 gigs with no SD card feasible.
I really got lucky when my Captivate had identical hardware to the Nexus S and Samsung was actually good about supporting the devs.
Look at the Samsung Exynos situation - A year ago, Samsung devices were looking like your best bet for ongoing developer support. However, over the past year, a variety of things have changed:
Samsung constantly releases broken HALs that require all sorts of workarounds, and don't play nicely with backwards-compatibility solutions that work on other devices. ICS and JB bringup on Exynos4 devices has been an utter nightmare, leading to the entire team of CM on Exynos devices burning out or coming damn close to it
Samsung decided to use their phones as an outlet for gigantic batches of defective eMMC flash chips. They put workarounds in their firmware but didn't tell anyone. The end result is that you have to tread carefully with any 2011-model Samsung device. Their poor handling of the eMMC disaster has left a sour taste in many developers' mouths.
As a result, many developers are leaving, not necessarily for a device that is flashier, but one that is at least more developer-friendly. I think that in many cases, the Xperia TL will be a downgrade for me compared to my Galaxy Note... But dealing with the Exynos in the Note is driving me utterly insane.
Click to expand...
Click to collapse
Do you think that may have some weight on why Google decided to hop to LG for a Nexus device?
Either way, it sounds like I'll be on the Xperia TL or LG Optimus G this upgrade. The decision isn't exactly becoming easier to make though. At least I managed to scratch off the HOX+

i chose xperia phones becase developers say they are not hard to develop , i have an xperia ray and i have a buttload of roms to choose from... i cant decide so i need to fash every 2week!! (flashaholic :l)

also because sony provides solution for bootloader unlock

Here's what I know so far for the TL. Keep in mind none of this is official, and it is preliminary, so could change.
1) The bootloader will NOT be unlockable on any device that has an active SIMlock. e.g. any device sold on AT&T with a contract subsidy is not going to have an unlockable bootloader. This is almost 100% definite.
2) The bootloader should be unlockable for users who pay full price for the device from AT&T, e.g. anyone who can receive an immediate SIM unlock with AT&T's policies. That said, while AT&T says that any person with a full-price device should be able to immediately remove SIMlocks, often it's a major hassle, and I worry that the bootloader unlock "allowability" process will be even less integrated. Don't count on unlocking your bootloader if you purchase full-price directly from AT&T.
3) Sony may sell the device directly (again - they MAY do it, it's not guaranteed), direct-purchase devices will almost surely have an unlockable bootloader (Not guaranteed, but very likely).

Well,TX seems doesn't support for the rom made to T:crying:

niuzhd said:
Well,TX seems doesn't support for the rom made to T:crying:
Click to expand...
Click to collapse
of course not. It's a different device

Coming from laggy XS, now holding TX,
Sony is doing it right this time, TX design and ICS are so smooth, fast and bug free( at least haven't encounter any yet), TBH I don't have any intention to flash Rom or wait for update (JB).
Sent from my LT29i using xda app-developers app

Waiting for my first room tanks all
Envoyé depuis mon LT30p avec Tapatalk

Coustom roms to Xiaomi note pro - Anyone?

Xiaomi promises to update to Android 6 our beloved Note pro, when are this gonna happen?
Other phones with same processor Snap 810 already has android 6 running like one plus 2.
Xiaomi keep giving us useless updates, and when comes with one good update is full of bugs. - No real developing for our Note pro.
Some coustom roms (3 roms and android 5.1.1 - Mokke and CM12.1 (batery drain problem and developer abandoned this roms), Flyme (full of chinese stuff dont get me wrong, but i can not read chinese, at least the apps could be in english. no google play and gives error installing gapps, ota update gives error and can not install any update)- so little developing.
Any one can give us a real working rom (not Miui) whithout this problems and if it can be android 6?

I don't think there's much going to be in terms of development. If you check github for mokee on the other thread, there's bit of activity.
I think we all agree that the phone is not that impressive especially issues with overheating 810. I don't care what miui fanboys say but it definitely heats up when charging and browsing at the same time. You can't touch your face with top corner of the phone due to the hear. I guess we were wrong if we thought if we able to flash other rooms other miui.
Heck, my galaxy s2 is still getting weekly updates for LP and MM rows. Disappointing. Just going to get nexus 6p
Sent from my MI NOTE Pro using Tapatalk

If updates and roms are important to you then you picked the wrong oem for that.

zelendel said:
If updates and roms are important to you then you picked the wrong oem for that.
Click to expand...
Click to collapse
Not a bad OEM at all, I do like Xiaomi but they do make some bad decisions sometimes. Wish there was more development from the community.

this is a great phone, with great specs, but with poor developing, i hope that one or two developers can give us a really great android 6 rom

Given up on the mi note pro and bought G5, guess what nothing happening here in the way of roms either, my wife has the note pro now.

Kahun said:
Not a bad OEM at all, I do like Xiaomi but they do make some bad decisions sometimes. Wish there was more development from the community.
Click to expand...
Click to collapse
You have to understand that the main developers wont touch their devices. Every now and then someone might port the rom or bring it up but it is always just some random person. The main devs for big teams avoid this OEM like the plague

zelendel said:
If updates and roms are important to you then you picked the wrong oem for that.
Click to expand...
Click to collapse
Obviously, I can see that you typical fanboy
Sent from my MI NOTE Pro using Tapatalk

Gurusev_Uppal said:
Obviously, I can see that you typical fanboy
Sent from my MI NOTE Pro using Tapatalk
Click to expand...
Click to collapse
First off don't be mad because you did t do your research before getting a device.
Second I would watch how you speak to me before you end up removed.

helderfp said:
this is a great phone, with great specs, but with poor developing, i hope that one or two developers can give us a really great android 6 rom
Click to expand...
Click to collapse
To an extent, the heating issues are a fact for mi note pro and other mi phones are getting aosp roms but not much for mi note pro which is flagship device.
Having said that other oem phones with 810 are getting updates and there is overheating issues
Sent from my MI NOTE Pro using Tapatalk

zelendel said:
You have to understand that the main developers wont touch their devices. Every now and then someone might port the rom or bring it up but it is always just some random person. The main devs for big teams avoid this OEM like the plague
Click to expand...
Click to collapse
And why the main devs for big teams avoid this OEM like the plague any reason?

helderfp said:
And why the main devs for big teams avoid this OEM like the plague any reason?
Click to expand...
Click to collapse
There are many reasons. The first being that this OEM seldom puts out the proper source code. Violating the GPL is a common thing for china/Asia based devices. Not something 3rd party devs like very much. Then you also have the fact that the MIUI team are known Kangers to the point of removing authorship on commits. We all know how well that goes over. You have to remember where MIUI started. Right here. There is a reason they were banned for so long from here. Another is the warez market that replaces the PlayStore in China based devices. Need I go on?

Don't worry we will see soon Android 6 on the new Miui 8 for our phone...and since there is no problem, there is no need to get new roms but would not be bad to have more choise, also if I would like they care more about camera that is not enough optimized for its quality
Sent from my Mi Note Pro using Tapatalk

Now I know seem very negative about this OEM and in truth I am. The greatest joy I get is when users like you guys do it anyway. Just because the devs for the teams don't get the devices to support doesn't mean hope is lost. It all depends on how much effort you guys want to put in. You have the devices now so you have 2 choices. 1. Take what they give you and accept it. Or 2. Refuse to and make things happen. The first is the easiest road to take.
There are thousands of threads to help. Read up and see what you guys can do. Remember that is how xda started. Taking what oems gave us and making them better. The ball is and always has been in the users court.

Gurusev_Uppal said:
I think we all agree that the phone is not that impressive especially issues with overheating 810. I don't care what miui fanboys say but it definitely heats up when charging and browsing at the same time. You can't touch your face with top corner of the phone due to the hear.
Click to expand...
Click to collapse
I'm not a fanboy of anything (except maybe Fanboy's Adblock List) but I don't experience any of those "810 issues" that get mentioned so much. I use the phone on a daily basis and it never overheats. Granted, I don't play games, so if you do, YMMV. In my usage scenario, the phone can get a little warm when simultaneously charging and using GPS navigation with screen always on but just when browsing? This I really don't get.
To me the phone is actually quite impressive, especially considering how much (or how little) I paid for it. The only annoyance is that the battery capacity could be larger than the ~3000 mAh. That being said, I don't think it's a power drain issue as it's primarily the screen time that is sucking the battery juice, and that is to be expected. So if they could fit a 4000-5000 mAh battery into it, it would have made a marked difference. Other than that, the phone is great.
The little developer attention it gets is because of its limited availability in the West, which is where most (and the best part of) the community-driven development happens. And even in China, the Note Pro has been the most expensive Xiaomi device ever sold to-date. With it, Xiaomi were trying to break into another market segment, or perhaps at least establish themselves as a company that does "premium" phones too. It was never really supposed to sell in high numbers, and for this reason the availability of promotional pricing was also limited. Most of the time, the phone was not really cheap already in China, and when resold abroad through middlemen that also had to earn their cut, it was never going to become a proposition for the masses.
Basically, for high developer activity you need to have a wide user base in the cultural West, due to in particular better work-life balance and the open-source ethos. Missing out on this is Xiaomi's biggest weakness, especially aggravated in America due to the lack of local 4G band support. If you want a lot of development, buy a Nexus device, although these days it pretty much guarantees you'll be overpaying for the hardware. Some Xiaomi devices also get quite a lot of development but for this you should choose a lower-cost one that is or will eventually be released globally. The Redmi Note 3 Pro is one example of such a device and it has already overtaken the Mi Note Pro in terms of development despite being released much later.
As for myself, I prefer MIUI to AOSP/CM in terms of interface although I'm not really happy with the direction its development seems to have taken (MIUI becoming more bloated and less customizable). It would of course be great to have an alternative in case I have to jump the ship but the hype with the version bump from Android 5.1 to 6.0 (which should more accurately be numbered 4.5.1 and 4.6) again I don't get.
Just my 2¢...

zelendel said:
You have to understand that the main developers wont touch their devices. Every now and then someone might port the rom or bring it up but it is always just some random person. The main devs for big teams avoid this OEM like the plague
Click to expand...
Click to collapse
That's understandable but it's not the OEM but the actual device. Firstly if you look at phones like the main Mi series or the Redmi series they have HUGE amount of development. The reason for that? .. Kernel sources were released early we didn't have to wait over a year and the user base is absolutely huge unlike the Mi Note Pro that's exclusive only to China no other Asian countries such as India. So you are like comparing OEM's that released a phone e.g HTC One (GLOBALLY) which everyone can get to a Mi Note Pro (EXCLUSIVE TO CHINA) that's why there is hardly any development going + the delay of kernel sources and forgot to mention a lot of people got for the cheaper option such as Mi Note which has a lot more development as the USER BASE IS BIGGER. Simple? If you were developing an app what would you develop it for first? Android or Blackberry OS? Obviously Android as it has a bigger USER BASE. Same goes for the phones developers work on ROMs with a lot bigger user base where they will reach a lot bigger audience.

Even Xiaomi shows this with their actions:
The new MIUI8 Beta gets released for Mi Note, which is much wider spread (due to it's price difference). Even though the Pro has a much better SD810 compared to the Mi Note. That also went for most experiments like a Windows ROM for the Mi Note, but not for the Mi Note Pro.

Kahun said:
That's understandable but it's not the OEM but the actual device. Firstly if you look at phones like the main Mi series or the Redmi series they have HUGE amount of development. The reason for that? .. Kernel sources were released early we didn't have to wait over a year and the user base is absolutely huge unlike the Mi Note Pro that's exclusive only to China no other Asian countries such as India. So you are like comparing OEM's that released a phone e.g HTC One (GLOBALLY) which everyone can get to a Mi Note Pro (EXCLUSIVE TO CHINA) that's why there is hardly any development going + the delay of kernel sources and forgot to mention a lot of people got for the cheaper option such as Mi Note which has a lot more development as the USER BASE IS BIGGER. Simple? If you were developing an app what would you develop it for first? Android or Blackberry OS? Obviously Android as it has a bigger USER BASE. Same goes for the phones developers work on ROMs with a lot bigger user base where they will reach a lot bigger audience.
Click to expand...
Click to collapse
See you are looking at this wrong. There is a hug diff between developers of roms and app developers. App developers want people using their apps. It's a great way to make money. Rom developers really couldn't care less.
The fact that it is only available in Asia is not really a big deal. Most developers here (myself encluded) have been importing devices for decades. Hell I was using a China based tilt for the FFC before apple ever released the first one stateside. So if developers wanted the device they could easily get it.

zelendel said:
See you are looking at this wrong. There is a hug diff between developers of roms and app developers. App developers want people using their apps. It's a great way to make money. Rom developers really couldn't care less.
The fact that it is only available in Asia is not really a big deal. Most developers here (myself encluded) have been importing devices for decades. Hell I was using a China based tilt for the FFC before apple ever released the first one stateside. So if developers wanted the device they could easily get it.
Click to expand...
Click to collapse
So tell me the reason they stay away apart from taking ages with kernel sources

Kahun said:
So tell me the reason they stay away apart from taking ages with kernel sources
Click to expand...
Click to collapse
You have to understand that MIUI has a history here. The team is known for taking the code of other devs and removing the authorship of the commit. (they were caught out and then they closed the source) There have been many supporters over the years. I was a huge fan when they started because the Theme engine had great potential. Key word is "had". The main developer for APT tool was a huge supporter for a while and then even he dropped all support for Xiaomi and MIUI.
The GPL is also a very big deal to most developers. It embodies that which Linux/Android is built on. Even when they do release it, it is never complete and needs fixing. This only happens because they are behind the China firewall.
If you notice it is not just this OEM. It is many others. If you look in team groups and pay attention you will notice a pattern. There are OEMs that are avoided. Xiaomi has been one of them for years. Huawei has also been one for a long time. Heck they were even on a ban list for Gov employees. And the dreaded Generic named device. Now this is for many reasons. Quality control, After sales ,support, GPL (android), Security concerns, The iphoneish look (this matters to many, far more then you would think). So there are some reasons. Hope this has offered some insight.

Is the OnePlus 3t sensible after the issuance of its death certificate?

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

Any custom rom for this device?

Some ROM as lineage OS for this device?

Seems to be very poorly supported here on XDA. No real devs appear to have become involved with the device, which is a shame. I've had the device for around a month and have already moved to a Pocofone due to the lack of interest in this device here on XDA.

lmulli said:
Seems to be very poorly supported here on XDA. No real devs appear to have become involved with the device, which is a shame. I've had the device for around a month and have already moved to a Pocofone due to the lack of interest in this device here on XDA.
Click to expand...
Click to collapse
We haven't had TWRP yet but it may be getting close, then there should be at least one or two ROMs fairly quickly from what I gather. There's been more activity on the Telegram group than here on XDA.

I hope it will soon be available Pixel Experience rom for our device.
That will be awesome.
Best rom ever.

For me it's kind of confusing considering that Moto One Power uses Android One and has identical internal components from what I believe it shouldn't be hard to port..?
Correct me if I'm wrong.

haasta said:
I hope it will soon be available Pixel Experience rom for our device.
That will be awesome.
Best rom ever.
Click to expand...
Click to collapse
Would love Pixel Experience ROM for the Moto G7 Plus. Just bought mine and even though the stock ROM is pretty uncluttered there's some issues. TWRP was pretty easy to install after requesting code from Motorola to unlock the bootloader.

Why is dev support so bad for this phone?

I have an old mi note 5 pro which I gave to my girlfriend and that phone already has many stable android 10 ROMs, along with havoc and pixel experience, and it didn't even get an official android 10 update.
This phone has official android 10 from xiaomi but there aren't any aosp based ROMs on it. All the major ones have been abandoned and there aren't too many in general anyway. Why is that happening? Is it specifically hard to make ROMs for this phone?

lvnatic said:
I have an old mi note 5 pro which I gave to my girlfriend and that phone already has many stable android 10 ROMs, along with havoc and pixel experience, and it didn't even get an official android 10 update.
This phone has official android 10 from xiaomi but there aren't any aosp based ROMs on it. All the major ones have been abandoned and there aren't too many in general anyway. Why is that happening? Is it specifically hard to make ROMs for this phone?
Click to expand...
Click to collapse
what do you mean by dev support so bad?iff you can question dev like this "quote" (Is it specifically hard to make ROMs for this phone)..why dont you try to make one?dont throw stupid question on this forum..to make a custom rom first you need free time..second need a team to develop 1 rom..third you not getting paid for what you did (yes you can put your donation link in the post but not all user will donate to you..dumn kiddo

Basically stick with MIUI if you want a functional phone with updates for like 2 years. Then you can rely on 3rd party developers. But then again software for your device is not guaranteed. Or better should had bought OnePlus 7/t/pro instead. Xiaomi has a very bad record of updating their device. It's called planned obsolescence. It's better if you learn how to make ROMs if you want to keep your device updated. You can't trust and rely on anyone these days.

Cheaper devices which have lost support tend to get better dev support.
I'd imagine more android 10 roms when the official kernel sources for it are released. If it were never to get Android 10, then devs may see it worthwhile to backport kernels.

lvnatic said:
I have an old mi note 5 pro which I gave to my girlfriend and that phone already has many stable android 10 ROMs, along with havoc and pixel experience, and it didn't even get an official android 10 update.
This phone has official android 10 from xiaomi but there aren't any aosp based ROMs on it. All the major ones have been abandoned and there aren't too many in general anyway. Why is that happening? Is it specifically hard to make ROMs for this phone?
Click to expand...
Click to collapse
Because you haven't out baked any ROMs.
Sent from my Mi 9T Pro using Tapatalk

Let's not act like the folks at the MI forums and discuss it rationally instead of lashing out at OP.
My guess is that K20 series is rather new series and has lower salse than extremely successful devices like Note 5 pro. So it has smaller dev base and availability of raw materials yet.

Instead of giving cliche answers like "developers have life too", "why don't you make rom yourself".
Why can't we discuss lack of Android 10 roms for our device? OP asked the right question.
As far as I know, we don't have stable device tree for Q. Xiaomi doesn't release device trees. Abhishek(dev of LineageOS 10) has a working device tree but he wants to make it stable and then release the sources. Once he releases that i think then we will get more Q based custom roms.

Yeah It is not worthy changing to custom rom. Better stay on stock atm

Because it's still a rather new phone, atleast the global one. Custom ROMs in general seem to be dying, probably because official ROMs are getting better and better compared to the times when i had my HTC HD2.

I don't know why everyone is so butthurt about this post, I'm legitimately curious why this is happening. I'm not bashing the devs at all, maybe 10 year old children that can't even comprehend a text should stick to their telegram groups.
Thanks to everyone who posted something actually useful, it seems the official device tree hasn't been released it, hopefully xiaomi will take care of this soon.

lvnatic said:
I don't know why everyone is so butthurt about this post, I'm legitimately curious why this is happening. I'm not bashing the devs at all, maybe 10 year old children that can't even comprehend a text should stick to their telegram groups.
Thanks to everyone who posted something actually useful, it seems the official device tree hasn't been released it, hopefully xiaomi will take care of this soon.
Click to expand...
Click to collapse
At the moment there is a bit of inactivity whilst many devs are waiting for android 10 sources to be released by Xiaomi. I'm guessing most devs don't want to waste time working on fixing Pie ROMs when they know everyone will abandon them once stable 10 ROMs arrive.
Give it a month or so and you'll see done movement again.

Robbo.5000 said:
At the moment there is a bit of inactivity whilst many devs are waiting for android 10 sources to be released by Xiaomi. I'm guessing most devs don't want to waste time working on fixing Pie ROMs when they know everyone will abandon them once stable 10 ROMs arrive.
Give it a month or so and you'll see done movement again.
Click to expand...
Click to collapse
Good point, I haven't considered that. This phone is very popular and I was really curious why there are so few custom ROMs, maybe we will get more goodies on android 10.

lvnatic said:
I don't know why everyone is so butthurt about this post, I'm legitimately curious why this is happening. I'm not bashing the devs at all, maybe 10 year old children that can't even comprehend a text should stick to their telegram groups.
Thanks to everyone who posted something actually useful, it seems the official device tree hasn't been released it, hopefully xiaomi will take care of this soon.
Click to expand...
Click to collapse
because you too stupid too make comparerison with your stupid redmi note 5 over 2019 k20 pro/Mi 9T pro device dumb ass..they way you said (dev support so bad) make you look so stupid..thats all..and 1 more thing..you can say dev support so slow..not dev support so bad since they not work for you kiddo..

xNovaLeader said:
because you too stupid too make comparerison with your stupid redmi note 5 over 2019 k20 pro/Mi 9T pro device dumb ass..they way you said (dev support so bad) make you look so stupid..thats all..and 1 more thing..you can say dev support so slow..not dev support so bad since they not work for you kiddo..
Click to expand...
Click to collapse
Really don't need this kind of rage, take it easy. I believe op was just asking. Just a curiosity... Despite your concerns about the words he used to start the talk. I believe it is pretty easy to understand he was not demanding anything from the good guys, the devs, or even trying to complaining about it.
Seems that there's no way to have a civilized conversation about it without getting someone any hassle, saying "why don't you develop? Douchebag".... Not first time I saw this. Weird thing indeed...

From the Moderator oka1
This conversation is going nowhere productive.... They rarely do.
Remember, everyone posts their work for free, if you do not like their work, I suggest you make your own ROM and show us your skills .......... Which likely, are non-existent with the exception of running your mouth.
.........As Such ..... THIS THREAD IS CLOSED
~~~ Oka1