Related
I was wondering if anyone knows if it will be possible to have all the OEM marketplaces on a given phone so we can make our choices based on hardware \ network availability (going for AWS which has fewer devices) and enjoy all the niceties such as HTC's dialer and LG's voice as SIP applications?
Thanks!
OEM's are not allowed to modify the Dialer or SIP. Carriers can have their own section on the marketplace for their phones. I know AT&T has one but haven't heard if any others do or will.
Ren13B said:
OEM's are not allowed to modify the Dialer or SIP. Carriers can have their own section on the marketplace for their phones. I know AT&T has one but haven't heard if any others do or will.
Click to expand...
Click to collapse
it seems LG got its own
xson said:
it seems LG got its own
Click to expand...
Click to collapse
they don't have their own marketplace, but MS has allowed for manufacturers and carriers to have their own section within the marketplace. The idea is that companies such as LG can get exclusive content to help them push their phones. This also means that those with an LG phone will still be able to access the general market place, which is a great idea.
Let me draw a comparison... I've heard that Amazon are looking into starting their own market place for Android, meaning that all phones sold through Amazon will have the Amazon market place instead of Google's. What does this mean? Only apps submitted to the Amazon market place will come up on those phones, not the ones in Google's. This is the downfall of separate market places is that developers have to spend more time making sure their applications meet all the different market place conditions, unlike WP where they submit to one place, but don't neglect individuality for the manufacturers/carriers.
ahhhhhhhhhhhhhhhhhhhhhh
Thank you, this is quite a good clarification!
So do you know if it will be possible to get into the marketplace sections from other companies so we can get the special programs? Or will I actually have to make a choice (Also there is a lack of Samsung and LG phones for T-mobile\windmobile\mobilicity )
most likely if you can't find it in the general market place, but you know a particular manufacturer has made it, it's because they have access to some of the phone's features which we as general developers do not yet (as in the Silverlight APIs haven't been created for them yet). Give it time and apps of that type will become available and all the exclusiveness should hopefully be redundant.
No custom roms... No unlocks... Nothing..... Why??
Because it is a secure device like the dell venue pro. The other HTC devices (gen 1) had a long standing HTC bootloader exploit.
Actually, I don't think it's really any more secure. It's just because, frankly, the world runs on GSM. The US and a very few other countries use CDMA, but the international hacking community has relatively little interest in CDMA devices - they couldn't use one even if they could buy one.
The DFT guys claim to have a working bootloader unlock for the CDMA devices (Arrive and Verizon Trophy) and, given that, I'm sure custom ROMs will come eventually. It will take time, though; I think DFT didn't even have the devices until a few months ago.
As for homebrew, most of the original HTC homebrew (TouchXplorer, Advanced Explorer, etc.) worked fine on the Arrive. Additionally, there's lots of device-agnostic homebrew that works on anything (assuming it has been dev-unlocked).
The problem is the interop-lock. I (and a few others) are researching universal interop-unlocks, but so far we haven't made one work. Aside from LG, no devices have a registry editor already available, so we have to take over another program and make it edit the registry for us. The only apps that have successfully been used for this so far are network configuration apps, because they have a lot of configuration data and we can often modify it. The Arrive is permanently locked to a single network, so there's no point in it having a network configuration app.
On my list of reasons why I prefer GSM over CDMA, "can use hackable network configuration tools" would normally be pretty far down the list. Since the release of Mango and the interop-lock, though, it's become much more important on WP7. I don't really have anything against Sprint as a company - they just use a poor choice of wireless technology. CDMA is to GSM as Imperial is to Metric; the US keeps on using it and everybody else thinks we're crazy for it.
This actually belongs in the Q/A section, but if you look at most other devices (droid custom, windows mobile, etc) the GSM customizations are much more numerous than their CDMA counterparts.
Pretty much GoodDayToDie nailed it as to why the CDMA counterparts don't see a lot of action. Most of the major teams live in countries where GSM is the norm.
Thread Closed
This is not Development. It is a device specific question, i will from now on not move these, they will be closed.
Please refer to the read before posting sticky
Hi Guys,
I've been coming here for a number of years and have always been frustrated by the naming of the forums, used to get really fed up with remembering that the HTC Tytn II was an XDA Stellar which was a Kaiser etc. etc. I can't even remember what the orbit's other names were now. Anyhow, the forums now are getting split up mainly by American Operators which is fine if you live in the US, but the roots of this forum are European so it puzzles me why this is the case (I know there are many many US participants here, but it's getting really confusing again)
I've seen so many threads on here that have been posted in the wrong forum for the wrong device because perhaps they were on "Three UK" or "o2" Germany and thought that mapped to X operator in the US. I've even read a thread just the other day where people can't figure out if their phone, which was a Canadian phone, would work with the roms from Y phone in the US.
This gets me onto the title of this thread. Seriously, how many forums do we need for the Galaxy S III, there are four "General" threads, four "Q&A" threads etc. etc. Surely 90%+ of the posts in these forums are common to all the devices.
Would it not be better to classify threads by device ID and then have a mapping somewhere for all operators in the world to the device ID. I'm sure the majority of people who use this forum will know the device ID of the device they are interested in off by heart anyhow.
BTW, I did search for an explanation about why the forum is formatting in an American way, but didn't find one, so if there is an explanation about why and perhaps even a past (But recent) discussion on this, then please point me to it. If this hasn't been discussed for a while, would this be a good time to review it again?
Cheers,
Mark.
I heard that sometimes the hardware is different, such as the lte for our american devices. The T-Mobile s3 is branded t-999, not whatever the international version is branded.
Sent from my SGH-T959 using xda app-developers app
markfid said:
Hi Guys,
I've been coming here for a number of years and have always been frustrated by the naming of the forums, used to get really fed up with remembering that the HTC Tytn II was an XDA Stellar which was a Kaiser etc. etc. I can't even remember what the orbit's other names were now. Anyhow, the forums now are getting split up mainly by American Operators which is fine if you live in the US, but the roots of this forum are European so it puzzles me why this is the case (I know there are many many US participants here, but it's getting really confusing again)
I've seen so many threads on here that have been posted in the wrong forum for the wrong device because perhaps they were on "Three UK" or "o2" Germany and thought that mapped to X operator in the US. I've even read a thread just the other day where people can't figure out if their phone, which was a Canadian phone, would work with the roms from Y phone in the US.
This gets me onto the title of this thread. Seriously, how many forums do we need for the Galaxy S III, there are four "General" threads, four "Q&A" threads etc. etc. Surely 90%+ of the posts in these forums are common to all the devices.
Would it not be better to classify threads by device ID and then have a mapping somewhere for all operators in the world to the device ID. I'm sure the majority of people who use this forum will know the device ID of the device they are interested in off by heart anyhow.
BTW, I did search for an explanation about why the forum is formatting in an American way, but didn't find one, so if there is an explanation about why and perhaps even a past (But recent) discussion on this, then please point me to it. If this hasn't been discussed for a while, would this be a good time to review it again?
Cheers,
Mark.
Click to expand...
Click to collapse
Its because in america devices can be completely different depending on the carrier, they all like to have there on tweaked versions, which result in hardware changes which mean ROMS will not work on each without changes, so they are split up to stop people flashing stuff for other versions of the device and bricking it.
Normally there is a international version which will pretty much cover the rest of the world.
This is more about the organization of various device sections than the devices themselves, so I'm moving this to About XDA.
zacthespack said:
Its because in america devices can be completely different depending on the carrier, they all like to have there on tweaked versions, which result in hardware changes which mean ROMS will not work on each without changes, so they are split up to stop people flashing stuff for other versions of the device and bricking it.
Normally there is a international version which will pretty much cover the rest of the world.
Click to expand...
Click to collapse
This is exactly why. It is annoying but the only way to keep things separate. ROMs and kernels will not work on both devices, therefore we created separate forums for each. Its a pain... but blame the carriers for each wanting to be "Special."
I'm not entirely sure which forum would be most appropriate to post this under, but this seems like a decent candidate, so I'm starting here. If this would fit better somewhere else, please feel to redirect me, and/or even move the thread if appropriate. I think I've read all the appropriate sticky threads et cetera, but if I do make / am making a faux pas, please let me know.
As you're probably aware (https://www.xda-developers.com/t-mobile-att-require-volte-phone-calls-shut-down-3g/), T-Mobile is expected to shut down its non-VoLTE voice service in January of 2021. As a result, it's imperative for anyone who gets phone service through them to have a phone with working VoLTE support before that point. As that includes me, I've been looking into that.
I currently have a Samsung Galaxy S5, purchased through T-Mobile back in 2015 (if I'm not mistaken, it's a SM-G900T). There seem to be fairly solid statements that this model does support VoLTE under the stock ROM, and indeed T-Mobile support seems to think that it should be working.
I run LineageOS - specifically klte, which matches that model. I'm currently on the August 30th, 2020 "nightly" build of version 16.0 (which was the latest available for that model as of earlier today), on top of TWRP 3.3.1 (ditto). I only recently upgraded from TWRP 2.8.7 and (IIRC) LineageOS 14.1, which I'd been running since sometime in 2017 for reasons that are out of scope but I can describe briefly if desired. The upgrade was specifically in hopes that newer LineageOS would have VoLTE support options which the earlier version did not, but that seems to have been a futile hope.
After some fairly extensive digging (mostly online, but with some poking around on my own device and in my own backups et cetera), I've concluded that while it is theoretically possible to have VoLTE support on this device under LineageOS, it's likely to be effectively impossible in practice. Threads such as https://forum.xda-developers.com/galaxy-s5/devs-only/port-ims-manager-to-klte-t3551084 (not the only place I've looked, but probably the last before giving up) seem to indicate that the only way to get it to work - short of reverse engineering enough of the underlying system to be able to reimplement Samsung's closed IMS implementation for that model - would be to find a Galaxy S5 with the stock ROM and working VoLTE, and copy the appropriate files out of that and into the correct places on the LineageOS-based version of the system.
I thought I'd kept a backup of the stock ROM which my S5 came with, but I haven't managed to find any sign of it in my archives. I don't think I have any other way to get at the correct files, never mind figure out where they need to go and get them there; I certainly couldn't justify buying another S5 just to be able to extract the stock ROM.
As linked from the thread referenced above, there do appear to be, or have been, other custom ROMs for the Galaxy S5 which include - or included - VoLTE support. However, I'm otherwise quite happy with LineageOS, and don't want to switch to another custom ROM line - especially since I want to avoid the data loss that would come with wiping my phone to install another ROM, unless there's absolutely no way to avoid it.
Are there any prospects for my being able to get VoLTE working on this phone under LineageOS? If so, what would I need to do to manage that, within the January deadline?
If not, or if what prospects there are don't pan out, I'm going to need to acquire a new smartphone which will be able to have VoLTE under LineageOS, and preferably one which will at least approximate meeting the other criteria which led me to select the Galaxy S5 in the first place and stick with it all this time. In particular, A: I all but insist on a conveniently user-swappable battery (I carry at least one fully-charged spare in my back pocket at all times), not so much for field battery life extension as to be able to replace the battery rather than the phone when the battery inevitably bloats and dies (I'm on something like my seventh battery for this S5), B: I really like having separate dedicated "home", "back", and (for lack of a better term) "active applications list" buttons, and the only model I know for sure has them is the S5 itself, and C: I very much want to have a traditional headphone jack. Expandable storage, in the form of a suitable SD-card slot, would also be nice but is not strictly required.
What models can I expect to be able to get VoLTE working on under LineageOS, with good support in other regards, within that January deadline? The model-support information I've been able to find in searching thus far does not seem to provide any clear indication on this point.
I don't expect recommendations on what smartphone models will be able to also meet my other criteria, although of course it would be nice; that would probably fit better under the "what phone should I buy next?" thread over in General Q&A.
No chance for adding volte. It's utopic to believe you could eben keep you phone setup.
You don't share your reason for using lineageOS. If it's about avoiding preinstalled apps, you can instead debloat stock rom.
kurtn said:
No chance for adding volte. It's utopic to believe you could eben keep you phone setup.
Click to expand...
Click to collapse
I was afraid of that, but I did still have some hope.
Is that klte/S5-specific, or is it a more general statement about LineageOS at large, which holds true regardless of phone model?
If the latter, then LineageOS is soon to become unusable for anyone with T-Mobile service, which seems like a major problem that people would already be working actively to try to correct. (I also think I heard that other providers may make a similar change, which would make the problem more widespread; I specifically half-remember articles about AT&T in that regard. No concrete backup for that at the moment, though.)
If the former, then what phone models are there for which VoLTE does or can readily be made to work under LineageOS?
kurtn said:
You don't share your reason for using lineageOS. If it's about avoiding preinstalled apps, you can instead debloat stock rom.
Click to expand...
Click to collapse
I'm a little surprised that the reasons would even be asked about, given that this is a LineageOS-specific forum; I wouldn't expect the people here to be up for directing people away from LineageOS to other ROMs.
My original impetus for using LineageOS (at the time, CyanogenMod) was simply one of principle about avoiding proprietary software and vendor lock-in/lockdown/et cetera. I also like the ability to control updates on my own, both in terms of being able to determine when I update to a new version and of being able to continue to get updates independent of whether the manufacturer/carrier/etc. continues to release them.
Avoiding preinstalled apps is certainly one aspect of it, but it's by no means the only one.
I also doubt that I could simply debloat the stock ROM, for the simple reason that I don't think I *have* the stock ROM - or if I do, it's years out of date (as I said, 2015). I left a search running overnight, and on that basis have managed to find the backup copy of the stock image that was on the phone when I received it, but unless trying to extract the necessary stack components for VoLTE support from it might be viable after all I don't know how useful that will turn out to be.
(I'm probably going to invest some time into looking into that today, anyway, but I don't really expect to get any results out of it.)
Alias Bongo said:
I was afraid of that, but I did still have some hope.
Is that klte/S5-specific, or is it a more general statement about LineageOS at large, which holds true regardless of phone model?
If the latter, then LineageOS is soon to become unusable for anyone with T-Mobile service, which seems like a major problem that people would already be working actively to try to correct. (I also think I heard that other providers may make a similar change, which would make the problem more widespread; I specifically half-remember articles about AT&T in that regard. No concrete backup for that at the moment, though.)
If the former, then what phone models are there for which VoLTE does or can readily be made to work under LineageOS?
I'm a little surprised that the reasons would even be asked about, given that this is a LineageOS-specific forum; I wouldn't expect the people here to be up for directing people away from LineageOS to other ROMs.
My original impetus for using LineageOS (at the time, CyanogenMod) was simply one of principle about avoiding proprietary software and vendor lock-in/lockdown/et cetera. I also like the ability to control updates on my own, both in terms of being able to determine when I update to a new version and of being able to continue to get updates independent of whether the manufacturer/carrier/etc. continues to release them.
Avoiding preinstalled apps is certainly one aspect of it, but it's by no means the only one.
I also doubt that I could simply debloat the stock ROM, for the simple reason that I don't think I *have* the stock ROM - or if I do, it's years out of date (as I said, 2015). I left a search running overnight, and on that basis have managed to find the backup copy of the stock image that was on the phone when I received it, but unless trying to extract the necessary stack components for VoLTE support from it might be viable after all I don't know how useful that will turn out to be.
(I'm probably going to invest some time into looking into that today, anyway, but I don't really expect to get any results out of it.)
Click to expand...
Click to collapse
I think your chances for volte are better if you change from samsung to motorola.
kurtn said:
I think your chances for volte are better if you change from samsung to motorola.
Click to expand...
Click to collapse
That's unfortunately fairly vague, as a basis for going out and buying a smartphone.
What I'm looking for in terms of "VoLTE does or can readily be made to work under LineageOS" is something for which a statement like one of the following can be made:
"Yes, VoLTE works on this model under LineageOS out of the box; you don't need to do anything special to get it working, just flash LineageOS and go."
"Yes, it's possible to get VoLTE working on this model under LineageOS; here's what you need to do to get it working, beyond just flashing LineageOS."
Do you know of any specific smartphone models for which you can make one of those statements?
While I'm not against investigating and experimenting and trying things out to get things to work, and in fact sometimes that can even be fun, I do not want to do that in a production environment - and I'm under deadline (albeit with a few months to go), with limited resources for experimenting (in the form of money to buy smartphones which might work), before this becomes a critical production environment.
(Also, I've found what look like IMS-related files in the backup copy of the stock ROM, which don't seem to exist in the LineageOS that's currently running on my phone. Depending on what they look like on further examination, I may try pulling them in and seeing if anything changes; worst-case scenario, I should just have to boot to recovery and restore a backup.)
Alias Bongo said:
That's unfortunately fairly vague, as a basis for going out and buying a smartphone.
What I'm looking for in terms of "VoLTE does or can readily be made to work under LineageOS" is something for which a statement like one of the following can be made:
"Yes, VoLTE works on this model under LineageOS out of the box; you don't need to do anything special to get it working, just flash LineageOS and go."
"Yes, it's possible to get VoLTE working on this model under LineageOS; here's what you need to do to get it working, beyond just flashing LineageOS."
Do you know of any specific smartphone models for which you can make one of those statements?
While I'm not against investigating and experimenting and trying things out to get things to work, and in fact sometimes that can even be fun, I do not want to do that in a production environment - and I'm under deadline (albeit with a few months to go), with limited resources for experimenting (in the form of money to buy smartphones which might work), before this becomes a critical production environment.
(Also, I've found what look like IMS-related files in the backup copy of the stock ROM, which don't seem to exist in the LineageOS that's currently running on my phone. Depending on what they look like on further examination, I may try pulling them in and seeing if anything changes; worst-case scenario, I should just have to boot to recovery and restore a backup.)
Click to expand...
Click to collapse
Yes. Moto e2 lte surnia has volte in LineageOS out of the box.
kurtn said:
Yes. Moto e2 lte surnia has volte in LineageOS out of the box.
Click to expand...
Click to collapse
Thanks! I'll investigate that option, then, in addition to any others that present themselves.
Alias Bongo said:
(Also, I've found what look like IMS-related files in the backup copy of the stock ROM, which don't seem to exist in the LineageOS that's currently running on my phone. Depending on what they look like on further examination, I may try pulling them in and seeing if anything changes; worst-case scenario, I should just have to boot to recovery and restore a backup.)
Click to expand...
Click to collapse
Unsurprisingly, it doesn't seem to be that simple. The files involved in this are themselves few enough, and most although not all of them don't seem to exist in the currently-running image, so they can be copied in without further ado - but there are enough references to them in other files, which either *do* exist (and so would need to be edited, in a way that leaves things compatible with both systems) or seem likely to themselves (need to) be referenced elsewhere, that the whole thing turns into a mess of cascading complexity.
Short of input from someone with expertise on IMS/VoLTE implementation from some other model, I suspect this won't turn out to be a viable avenue to pursue, at least not unless and until I have my hands on a Galaxy S5 which isn't my production phone and as such can be used for experimentation. Even then, I'll probably need to basically build my own custom ROM (or custom local build of LineageOS, at least) rather than just inserting files into a system built from an existing one.
I've looked briefly into the Moto E2, and while it does look like the newest/final models of it would support VoLTE in a way that LineageOS would plausibly be able to handle, it's also at least nearly as old as the S5 and is less capable and desirable in other ways. It'd be better than nothing, but not something I would prefer as my first choice.
I'm hoping that other people chime in with more models to suggest. As this is going to become increasingly important as more carriers shut down their 3G/2G networks, and VoLTE becomes the only way to do voice calling, I'd ideally like to see a page - possibly this thread, possibly another one, possibly a Wiki page - with as comprehensive a listing of phone models which *are* known to have working VoLTE support under LineageOS (and/or possibly other non-stock ROMs) as possible, including links to any necessary how-to directions per model and notes on any special criteria (e.g., carrier-specific support or support differences between regions or the like). I hoped something like that would already exist, given the apparent upcoming VoLTEpocalypse - but as it doesn't seem to (or at least I haven't managed to find one thus far), it wouldn't hurt to start trying to create one.
My understanding is that Verizon is apparently going to make the "VoLTE mandatory" transition in January, much the same as T-Mobile, and AT&T is planning to do it sometime in 2022. With Sprint out of the picture after the T-Mobile merger, that's basically all of the major US wireless carriers that I'm aware of, so this will be universal (at least in the USA) before too very long. Some amount of preparation to make sure the custom-ROM field will remain viable past that point would seem appropriate; I'm surprised by how little activity in that area I've been able to find thus far.
Alias Bongo said:
Unsurprisingly, it doesn't seem to be that simple. The files involved in this are themselves few enough, and most although not all of them don't seem to exist in the currently-running image, so they can be copied in without further ado - but there are enough references to them in other files, which either *do* exist (and so would need to be edited, in a way that leaves things compatible with both systems) or seem likely to themselves (need to) be referenced elsewhere, that the whole thing turns into a mess of cascading complexity.
Short of input from someone with expertise on IMS/VoLTE implementation from some other model, I suspect this won't turn out to be a viable avenue to pursue, at least not unless and until I have my hands on a Galaxy S5 which isn't my production phone and as such can be used for experimentation. Even then, I'll probably need to basically build my own custom ROM (or custom local build of LineageOS, at least) rather than just inserting files into a system built from an existing one.
I've looked briefly into the Moto E2, and while it does look like the newest/final models of it would support VoLTE in a way that LineageOS would plausibly be able to handle, it's also at least nearly as old as the S5 and is less capable and desirable in other ways. It'd be better than nothing, but not something I would prefer as my first choice.
I'm hoping that other people chime in with more models to suggest. As this is going to become increasingly important as more carriers shut down their 3G/2G networks, and VoLTE becomes the only way to do voice calling, I'd ideally like to see a page - possibly this thread, possibly another one, possibly a Wiki page - with as comprehensive a listing of phone models which *are* known to have working VoLTE support under LineageOS (and/or possibly other non-stock ROMs) as possible, including links to any necessary how-to directions per model and notes on any special criteria (e.g., carrier-specific support or support differences between regions or the like). I hoped something like that would already exist, given the apparent upcoming VoLTEpocalypse - but as it doesn't seem to (or at least I haven't managed to find one thus far), it wouldn't hurt to start trying to create one.
My understanding is that Verizon is apparently going to make the "VoLTE mandatory" transition in January, much the same as T-Mobile, and AT&T is planning to do it sometime in 2022. With Sprint out of the picture after the T-Mobile merger, that's basically all of the major US wireless carriers that I'm aware of, so this will be universal (at least in the USA) before too very long. Some amount of preparation to make sure the custom-ROM field will remain viable past that point would seem appropriate; I'm surprised by how little activity in that area I've been able to find thus far.
Click to expand...
Click to collapse
Totally agree, I'm surprised this news hasn't gotten more attention in the community. First came to mind, "ah crap, no more custom roms." (perse).
I started a thread on this on the LG v50 forums to raise awareness, hopefully there can be workarounds:
https://forum.xda-developers.com/v50-thinq/help/att-t-mobile-to-off-3g-networks-disable-t4163491
--
By forcing VOLTE, this can potentially lock out some unlocked phones and also exclude custom roms, forcing users to buy carrier branded phones. In addition, shutting down 3G and forcing 4G VOLTE will ensure that lots of customers upgrade/buy new phones when their current phone may be perfectly fine otherwise(unnecessary costs and more perfectly working phones in the land fill in vain).
IIRC, you could use a stock from on your S5 and just remove the bad parts. It's no substitute for AOSP but you got to do what you got to do. Plus it's free. The stock files should be available and you can use recovery to image your phone so you don't lose your data. That is the route I would go and can't really do on my S3.
Other phone selections are looking GRIM in terms of removable batteries, reasonable size, etc. You can look to the V20 or G5 from LG but you will have to do the above process and that is almost where I'm at. Poked and prodded rom isn't the end, I did it for years on my gS2 when AOSP couldn't get HW fully functional.
Motorola has models that do work but they are mostly sealed units and everything is really hard to find as its plastered all over XDA in posts from years ago. Do all rom links even work?
While we were sleeping people got taken over by the machine and the devs didn't know what was coming or couldn't figure out the proprietary implementations.
The question with Tmo is also, is band 12 mandatory or will other phones work on 2 and 4 and volte over that. Nobody has even asked the question. I'm going to try to be safe.
DUP deleted
So odd that such a fatal issue seems to be imminently coming without some progress being made to avert it because unneeded and dangerous 5g is crowding out 2g & 3g. The s5 and note 4 are THE gold standard of excellent screen and hardware and thus the only real choices of replaceable battery phones - the REAL reason that phone mfg force millions of phones to be tossed in the landfills - shame on them! Custom Roms provide extremely important current security updates and allow apks that are updated and no longer work on slightly older android 6 versions (chase, Starbucks, united, etc). Pretty bad to discover after factory resetting a phone that play store won't let you download current or working version.
Perhaps we can crowd fund developers to attack this looming disaster soon?
uds0 said:
So odd that such a fatal issue seems to be imminently coming without some progress being made to avert it because unneeded and dangerous 5g is crowding out 2g & 3g. The s5 and note 4 are THE gold standard of excellent screen and hardware and thus the only real choices of replaceable battery phones - the REAL reason that phone mfg force millions of phones to be tossed in the landfills - shame on them! Custom Roms provide extremely important current security updates and allow apks that are updated and no longer work on slightly older android 6 versions (chase, Starbucks, united, etc). Pretty bad to discover after factory resetting a phone that play store won't let you download current or working version.
Perhaps we can crowd fund developers to attack this looming disaster soon?
Click to expand...
Click to collapse
Attack
ＧΛËＬＤＵＶΛＬ (@[email protected])
We're in the process to backport VoLTE support to /e/OS on Samsung Galaxy S9 (Exynos). We're looking for strong expertise here. If you know some true experts in the VoLTE support field, please get in touch! (mailto: [email protected]) #VoLTE #engineering...
mastodon.social
Hi everybody...
It used to be much easier to find the answer to something... but Google is all ads trash now.
I have seen the answers to this question all over the place. Out of days of searching, I have only gotten lots of bad info.
I really just want to know, for sure:
Is there any Samsung Fold 3 sold anywhere in the world, that you can root AND use in the U.S.?
And if so, what is the model?
TiA
It's right here in the forums man...
Link to post on Rooting: https://forum.xda-developers.com/t/...lash-official-firmware-noob-friendly.4404473/
Models: SM-F926B / SMF926N / SM-F9260
How-To Find: How to find the Model: on your phone → Settings → About Phone → The third row says the Model number and you need to remove the part with the part of /xx, for example, SM-F926B/DS and you only need to type SM-F926B
The U/U1 Models that are sold in the US (Locked/Unlocked) are the ones that cannot be rooted at this time.
EVERY version can run in the US provided it's SIM UNLOCKED and has the right radios, but what I understand is that the 5G radios are the only difference and there are some international models that will work in the US, you just have to look and maybe read more. I have no intention of rooting my Fold 3 at this time, so I have not looked too much into this, but this is just what I found looking here on this forum and even just on the first page.
Thanks. I knew I'd take a little heat. But as you can see, I've been here since 2009... and with a name like AlienPDA... you know what I started on. So I'm not noobing out, I'm just autistic and I like clear answers. Life was easier back then -=)
I am trying to replace a Nexus 6. I haven't found another phone that came close to its specs, (mind you, it's rooted and OC'd to the bleeding edge, 3GHz) in nearly a decade. The screen alone destroys most phones: Resolution, 1440 x 2560 pixels, 16:9 ratio (~493 ppi density), and two VERY CLEAR front-firing speakers.
And now that phones have a silly aspect ratio made for skinny jeans, it looked like I was never going to replace my Nexus.
The fold is the closest a phone has come, and with the Fold 4 coming out, the 3 is in a good price range. But I need root to run a few work programs and provide tether.
> EVERY version can run in the US provided it's SIM UNLOCKED and has the right radios, but what I understand is that the 5G radios are the only difference and there are some international models that will work in the US, you just have to look and maybe read more. I
That part is the part I was referring to in my post. The bands. I've stayed with my carrier all these years, because I have a grandfathered (true) unlimited data plan, and their coverage has the least holes. I know this is because of the bands... and I'd hate to create holes by dropping certain bands.
The nice thing about XDA, we're so big, usually someone has had to have tried XYZ setup.
But I haven't found a post, where someone:
bought a Fold 3, international,
rooted it,
and put it on a U.S. carrier.
So, seemingly, everything stated about the Fold 3, has been hearsay.
Here's an example:
AnnaNguyen said:Thank you William again I just did it and I confirm works on SM-F926U
But... I personally, after reading that, tried the same thing, and it DID NOT work.
So... my option is then to make a new post...
"Samsung Fold 3 SM-F926U not taking root via Magisk"
And then someone will reply... "We already told you that U.S. Fold doesn't take root"
But, but... I mean... it's right there. She said she did it??? Right?
Your reply was, "the info is everywhere, you just need to look..."
Your reply
> The U/U1 Models that are sold in the US (Locked/Unlocked) are the ones that cannot be rooted at this time.
On the first page of the link YOU PROVIDED:
> Thank you William again I just did it and I confirm works on SM-F926U
So...
Do you understand my confusion perhaps?
Apparently either you or Anna are wrong.
But if Anna is wrong, then my question stands.
I'm not dumb, I just cannot make informed decisions on conflicting information.
Totally understand why that might be confusing, but if in doubt look at the thread title.
If the root method included the SM-F926U/U1 model it would have been listed. Since it's not then it is a fair presumption that the model was not included.
As for if the phones will work in the USA will depend on the bands they support. The models SM-F9260/B/N were originally designed and sold with other regions in mind, so they may lack certain bands for use in the USA. You will have to research the bands supported on the 3 models and compare them to the bands your carrier uses.
I know it's not a specific answer to your question but it is a recent experience. A previous phone I had (note 20) was an international model and I can say that it did work, but only in a very generic way. It had limited band support for my carrier so it didn't work that well. Suffice it to say I didn't keep the phone and I returned it. While I had wanted to root the phone in all honesty it would be pointless if I wasn't able to get good performance out of it on the cell network.
> Totally understand why that might be confusing, but if in doubt look at the thread title.
> If the root method included the SM-F926U/U1 model it would have been listed. Since it's not then it is a fair presumption that the model was not included.
Do remember... Talderon's reply to me:
> It's right here in the forums man...
Is it? Is it?
Let's pretend I am an AI... and I am being programmed solely by this fora.
It's a bit more than confusing...
[it is easy, from a human perspective, you're presuming a point of "starting", we all 'started our life on this planet', some X time ago, and have a corpus of knowledge thusly].
But the AI, it's newly born. All the info on here, IS the point of starting.
So, referentially, regardless if the title of that post is limiting the models that it applies to, how do you decide then, that saying it works on "U", isn't NEW information to be added to canon, especially since the author of the thread himself, thanked the person, and didn't correct them.
So IS IT REALLY in the forum, if it's miscible with bad info?
I reread the thread and there really isn't anything in there that debunks it works on "U". Why would the OP thank a person that obviously stated an incompatible model?
I mean, I know personally it doesn't work, now... but if I am being told that the information I seek is on this forum, but the information is bad, how is any of this helpful? I am right back at the question I posed, unanswered unequivocally by the forum.
Keeping this as basic as possible.
1. The SN-F926U/U1 models are not rootable at this time. Anything else said to the contrary should not be believed, debated or given a second thought.
2. It is unknown if a root method for the SN-F926U/U1 will ever be found. If you do not see any threads about work being done on a root method then it means no one is working on one.
3. If and when the SN-F926U/U1 becomes rootable someone will post the method and instructions for use. The thread title will clearly say SN-F926U/U1. Only when you see the threat and flood of people posting about successfully using said method should you consider the information as valid.
4. The international models were built and designed to function and connect to cell networks outside of the USA. The bands they support will vary some depending on the model
5. USA carriers may/might allow a sim/network unlocked international model to connect to the carriers cell network. However it is up to the carrier to determine what services and features are supported.
6. You need to research the cell network bands your carrier uses. Then look up the bands the fold 3 models your thinking of using. Using that information find the model that works on the most number of bands used by your carrier.
7. You can also call your cell carrier, provide the model number(s) your interested in using and ask them is the model supported and what features will or won't work.
8. Because of internatonal carrier and hardware differences you should not expect or have any expectation that an international model will have the same performance level as that of a model designed and sold for use in the USA.
9. If no one has posted the information you seek it means that either of the following is true:
*what your asking doesn't work
*No one has tried what you are asking
*You need to adjust your search terms
1. The SN-F926U/U1 models are not rootable at this time. Anything else said to the contrary should not be believed, debated or given a second thought.
2. It is unknown if a root method for the SN-F926U/U1 will ever be found. If you do not see any threads about work being done on a root method then it means no one is working on one.
3. If and when the SN-F926U/U1 becomes rootable someone will post the method and instructions for use. The thread title will clearly say SN-F926U/U1. Only when you see the threat and flood of people posting about successfully using said method should you consider the information as valid.
--------------------------------------------------------
Well... Shouldn't someone maybe then remove the post where someone claims that they successfully rooted the SN-F926U, so people don't buy the SN-F926U thinking it can be rooted?
I kinda feel like this is where the "gap in understanding" is at.
--- I want to do X, can I?
"Just look in the forums your answer is there"
--- Well it says I can do X here.
"That's not right, ignore that... but everything else is accurate"
--- ??????
Mods have the ability to remove incorrect info right?
As a forum of various members from all over we are required too exercise common sense and reasoning when we read the forum and apply the tools, instructions and methods. Even the thread in question indicates one needs a "Galaxy fold 3 and common sense'.
For example if one is not ready to accept the risks and consequences (i.e. Knox being disabled and apps not working because they require Knox) they should not root a device.
Another example is where one post is made where someone says it works on the U model by extension does not make that one post to be true. Especially when you take into consideration other pieces of information like it has been stated numerous times already the U/U1 is not rootable, the thread title not including U/U1, the requirement of the root process listed that OEM unlocking in developer options menu be present (which the U/U1 models do not have), and no other thread exists detailing how/with what (and proof that the method works) to root the SM-F926U/U1.
Also I disagree that an understanding gap exists.. Even with that one post left alone enough content already exists that (and even this thread) will address any further issues about it.
That all being said if you want to discuss it further you should contact the forum moderators via PM.
Ok... For one, you didn't post enough information to answer your question.
There are 2 variants of the Nexus 6, XT1100, and XT1103, and they themselves have different band coverage.
Additionally it would be in your best interest to start with the bands your carrier uses, not what the phone supports. You have a grandfathered plan, there will be bands that will almost certainly be locked out from your plan's coverage. Chances are your Nexus is only using one or two, start with *#*#4636#*#* and see what bands you're currently using, then check if a fold supports it.
Ugh, been sick, so forgot about this thread.
Glad you got some more answers and details.