Related
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
(I have no permissions for ROMs sections so posting this here)
So it looks things are slowly moving , and we are able to unlock bootloader and root our devices.
User @auras76 was kind enough to bring as the first ROM available, but I guess I am not the only one looking forward to get rid of EMUI and its poor customisation layer
I hope once firm .173 hits general release we start getting more dev interest, but the goal of this thread is to find out if any dev could be potentially interested (or already planning) to work on a non-EMUI ROM
I can imagine a bounty could be organised for users to support financially this action.
What are everyone's thoughts on this?
Doubt you will see much development of any major Rom's if there is not a free way to unlock your bootloader as there just won't be that many unlocked devices
I am fully aware of that, however let´s hope that changes if/when .171 FW is generally available and allows bootloader unlock.
I just wanted to check if there would be a way to attract some devs here, even by supporting their work (purchasing a device? 10$ per person???)
If you like custom ROMs so much buy a One Plus phone. Lots of custom ROMs and every custom ROM has bugs. There is no build of any custom ROM that doesn't have bugs and sometimes the bugs on "stable" versions of custom ROMs are so serious they impact the basic functionality of the phone.
If you think I'm exaggerating pick a custom ROM for the OP5, 5T, OP6 or 6T and look at the last several pages of user posts.
They will be users reporting bugs-often very serious ones.
If you pick an OP5 or 5T ROM many will no longer be in development. The last several pages before the ROM was abandoned will be users still reporting bugs that will never get fixed.
And that is on phones that are supposedly very development friendly.
The days of custom ROMs that improve a phone's functionality, speed and stability over the stock ROM died with Nexus phones but if you want to run a custom ROM anyway buying this phone makes pretty much no sense because Huawei is not developer friendly. They don't want owners of Huawei phones to unlock their bootloaders or run custom ROMs on Huawei devices. The same is true for Xiaomi and Samsung phones.
For that matter Google, the company behind Nexus phones which were the most developed friendly phones anyone could buy no longer wants people to use custom ROMs which is why they came up with the ROM certification program and safety net.
Apps that help phone owners bypass safety net are automatically banned from the Play Store. Whatever method Magisk uses to bypass Safety Net gets plugged by Google forcing the developer to come up with a new method that will stop working when it also gets plugged by Google.
The developer behind SuperSu said the writing was on the wall for original Android development several years ago and he knew what he was talking about.
Well, I thought XDA was exactly the place where people "like custom ROMS" and tinker with their phones.
I am coming exactly from OP phone so I know how scene works there.
OP phones are dev-friendly but not many people try different ROMs as Oxygen is probably the smoothest implementation layer of all manufacturers, so there is no need other to change other than fun.
But we are not talking about OP but Huawei here, which is the opposite case. Lousy software implementation, from battery management (see the Powergenie issues threads), to Huawei bloatware, notification handling, little customisation allowed.... So Huawei is not like OP but more like Xiaomi, heavily (not for good) customised Android version. And there might be not many OP ROMS, but check in Xiaomi land... many super stable versions that improve almost any Xiaomi device with AOSP or LOS versions.
As I said, maybe all it takes is to support a dev with a device for ROM release... I know I wouldn't be the only one looking forward to this.
Alright let's clear up what XDA is about.
It's a hub for developers. It's not a hub for people coming in with no knowledge demanding/posting hundreds of threads asking for ROMs for a device which is bootloader locked in most cases. Attitude like this steers developers away from devices because of noob communities. Look at the Samsung community on XDA.
Huwaei is still an infant when it comes to Android so they are learning the ins and outs of what works and what doesn't. Give em a break. They produce amazing devices with amazing technology. Just because it's locked doesn't mean you have to get your nickers in a twist because no one wants to develop for a new company on the Android scene. Give it some time. Maybe someone will come along and get the ball rolling for everyone and find a nice little backdoor in the bootloader and make it possible for everyone. Till then don't hold your breath and stamp your feet. Do your research before you flog out a grand on a device that might not have unofficial development for.
I really hope we can open this device up for more development, what could we do with unbridled access to the NPU, 3 rear cameras and the front 3d point cloud camera array
jhs39 said:
If you like custom ROMs so much buy a One Plus phone. Lots of custom ROMs and every custom ROM has bugs. There is no build of any custom ROM that doesn't have bugs and sometimes the bugs on "stable" versions of custom ROMs are so serious they impact the basic functionality of the phone. .
Click to expand...
Click to collapse
Had to pop in here to tell you you're completely wrong on that one.
Off the top of my head. No limits xXx for the OnePlus 5, not a single bug.
From Oreo 8.1 anyway.
A lot for devices have ROMs which surpass stock in more ways than one and have zero bugs
Further to my point and @ the OP.
The p20 pro has only seen ROMs because of the last few users / developers who have committed to Huawei/Honor devices and the fact that Honor view 10 ROMs work on the pro, in light of the changes made by Huawei IE: bootloader lock down, you will not see a lot of ROMs at all for your device in fact anyone who wants to root / flash / unlock their phones should not touch Huawei or Honor ever again, maybe (and that's a big maybe) the greedy pair of OEMs will see sense. But I doubt it.
Advice in short, dont buy their phones, I certainly won't ever again. They don't deserve it after what they've done.
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.
I'm looking for a new phone and the Europe S10+ is perfect
BUT
From what I'm understanding is that unlocking the bootloader and/or rooting it, trips KNOX and also voids the warranty, which would not be ideal for a 900€+ phone....
I want to know if all that is correct and the current scene for unlocking the bootloader, rooting and installing custom ROMs....
Thanks
riahc3 said:
I'm looking for a new phone and the Europe S10+ is perfect
BUT
From what I'm understanding is that unlocking the bootloader and/or rooting it, trips KNOX and also voids the warranty, which would not be ideal for a 900€+ phone....
I want to know if all that is correct and the current scene for unlocking the bootloader, rooting and installing custom ROMs....
Thanks
Click to expand...
Click to collapse
All correct.
There isnt going to be any scene for the S10 because it supports Treble 2, any GSI (including Q beta) works on it, and all of its magic is tied to samsung software.
At most there will be modified stock roms, but to be fair the stock OOB system is pretty good, even more so because the S10 is receiving monthly updates
opssemnik said:
There isnt going to be any scene for the S10 because it supports Treble 2, any GSI (including Q beta) works on it, and all of its magic is tied to samsung software.
Click to expand...
Click to collapse
Treble isnt open source? I understand it cannot be backported to older devices but newer ones that support it out of the box dont?
Basically, what you are saying is to get a OnePlus 7 Pro then, right?
riahc3 said:
Treble isnt open source? I understand it cannot be backported to older devices but newer ones that support it out of the box dont?
Basically, what you are saying is to get a OnePlus 7 Pro then, right?
Click to expand...
Click to collapse
Sorry for the long delay, my phone's screen was being replaced.
Treble is open source, only the drivers arent, but this is the same with each and every phone. What i meant is, there will not be a exclusive scene for the S10, you can simply download Universal roms from the universal forums here at xda, there is official Android Q beta 5, official Lineage, unnofficial omnirom, etc
Simply download an AARCH64 with A/B partitions
People havent done this on the S10 for simply being too new, but you can look into S9 running universal roms, since its exactly the same way
Mind you, samsung does offer monthly updates for the S10, mine has been on july patch for a few days already
Mind you also, while qualcomm S10s may still have a good camera in an AOSP rom using gcam, exynos phones will be in the dark with poor camera performance, as GCAM postprocessing is done using qualcomm libraries meant for qualcomm specific features, and the aosp camera certainly isnt good at all
Tripping KNOX won't void your warranty in the European countries! This is a mistake that has been made so many times... It's YOUR phone, YOU can do with it. The factory is NOT allowed to tell you what to do. (That's why I dislike Apple, but Samsung tries to tell us the same).
(Even worse for Samsung: they tell you it's IP67 or so, so when it's broken due to water it's still under warranty. Your problem is to 'convince' Samsung it's their fault that your phone broke)
Bright.Light said:
Tripping KNOX won't void your warranty in the European countries! This is a mistake that has been made so many times... It's YOUR phone, YOU can do with it. The factory is NOT allowed to tell you what to do. (That's why I dislike Apple, but Samsung tries to tell us the same).
(Even worse for Samsung: they tell you it's IP67 or so, so when it's broken due to water it's still under warranty. Your problem is to 'convince' Samsung it's their fault that your phone broke)
Click to expand...
Click to collapse
You have a source on this?
I dont believe it.
I heard it before, but I don't wanna do anything rash..gonna believe it kinda cuz I live in The Netherlands and this is the new country of opportunities
Reason I wanna root is that my s10 is from June and I have a s8 rooted when the warranty was gone and it's never had issues and is better then my s10 right now....
riahc3 said:
You have a source on this?
I dont believe it.
Click to expand...
Click to collapse
Sorry that I didn't reply. Here's an article: https://blog.iusmentis.com/2013/05/06/garantie-telefoons-mag-niet-vervallen-bij-root-of-jailbreak/
Recently a complete device tree was developed for all of the S20 family (except FE).
Many custom ROMs most of them went official.
Apparently, S20 FE has some different hardware ( WiFi chip and others) that prevent cross development and flashing.
What can regular users contribute with to help with the process that would make us catch up with the progress made with S20 family?
If anyone releases free bootloader unlock for (S20 FE Snapdragon US models), I think the development will be more available.
I'm not sure what the current state of play is nowadays but I've had phones where Verizon and Sprint bootloaders were locked but development was plentiful.
if a phone is very popular it'll usually attract support.
Assistance Requested LineageOS 18.1 | XDA Developers Forums (xda-developers.com)
Mostly there is a way to Unlock the Bootloader as far as I know you can Unlock the Bootloader for this Device
I'm Currently on SM-781B and the Bootloader is Unlockable, Correct me if I'm Wrong
for the first few years, while Samsung is supporting this phone surely the most stable, fully functional roms are going to be ONEUI based ones.
strip out all the Samsung, Microsoft and even a few Google apps. keep the camera algorithms and the 120hz as is but maybe swap the kernel to add a few features and workarounds etc ?
I'd love an AOSP rom on this phone but my experience has been the further you stray from the base firmware the more there is that never quite works right.