Related
I've noticed that a some developers (myself included) would be substantially aided in their efforts if they had access to one or more Galaxy S test devices.
I don't know how successful this will be however I've created this thread as a central place for developers to “apply” for device donations and for members to put their (presumably broken) devices up for donation.
My phone is broken, can someone fix it?
If your phone is broken and you want it fixed then a Samsung Service Centre or your place of purchase is the place to get it done. However if for some reason Samsung won't fix your phone then you can list it here and it might inadvertently get fixed, but please make sure you read this whole post very carefully!
Deciding to donate... zero liability!
If you do decide to list a device here regardless of whether you're donating or lending it to someone the developer that you donate/lend it to is in no way liable for what happens to your phone. The purpose of this thread is so users can donate devices for experimental development. As such there is definitely a chance devices could get bricked or permanently damaged (if they're not already). If your warranty isn't already voided then it certainly will be. If you're not willing to accept this then do not donate!
I would like to think that developers who have been donated devices will return the device to the donator upon request, regardless of whether the phone was donated or lent. However, just in case I would like “donators” to make clear what they expect in regards to their donation, whether they intend to donate, lend, donation time-frame etc.
Which developer gets which phone?
I think it should be up to the donator to decide what projects are more worthy or more relevant to the donator. I'm not going to assign phones to projects unless the donator requests that I do so.
How are broken devices useful?
Obviously that depends on what the developer is doing. To some developers a bricked device may be totally useless. However, for developers working on low-level interfacing (JTAG etc.) then bricked devices are basically the perfect test subject.
Shipping the device and costs.
I think it's only fair that people donating their phone shouldn't have to pay the cost to ship the phone to the developer. However, the return shipping costs (if the donator wants the phone returned) should be negotiated on per donation basis.
If the phone turns on the donator MUST disable all security features, in particular the mobile tracker functionality!
Applying/Listing
Developers or donators should fill out the following forms respectively.
--- Developer Application ---
Project Title:
Project Description:
Device Requirements:
Example 1. A Bell I9000M that in the past had access to download mode.
Example 2. Any device that charges.
Location:
Extra Information:
--- Donator Application ---
Donation Type: [Donating/Lending]
Phone Type:
Phone Status:
Example 1. Stuck in boot loop. Never had access to 3-button download mode... even tried the oven!
Example 2. Doesn't respond to power button or charger... it's dead!
Location:
Developer Requirements:
Example 1. Need the device back in a month.
Example 2. If the device gets fixed I would like it returned.
Extra Information:
----------------------------------- Developers -----------------------------------
Benjamin Dobell < celtichazard* (Returned)
dagentooboy
----------------------------------- Donators -----------------------------------
celtichazard -> Benjamin Dobell* (Returned)
Bold - Assigned
Regular - Unassigned
* - Lent
Project Title: Heimdall (and JTAG Research)
Project Description:
Heimdall is an open-source, cross-platform replacement for Odin. It is currently in alpha and is in need of testing. For more detailed information refer to the Heimdall thread.
I'm also interested in doing some JTAG research that will hopefully help bring "fully bricked" phones back to life.
Device Requirements:
Any Galaxy S (or derivative) phone in any state what-so-ever.
Location:
Melbourne, Australia
Extra Information:
I'm good with being lent or donated devices. I'm also happy to return donated devices if I'm able to fix them.
It might be worth also having "qualifications" as one of the things. Because otherwise, even 10 year olds can request phones...
I am concerned about the liability statement though honestly.. I live in Melbourne, but I am concerned that there isn't a reasonable expectation that the mobile will be working when it is returned (but yes, I'd love to see Heimdell succeed). Also, there isn't any clauses which ensure that provide leverage for mobile's to be returned.
andrewluecke said:
It might be worth also having "qualifications" as one of the things. Because otherwise, even 10 year olds can request phones...
Click to expand...
Click to collapse
I don't think it should be up to me to decide who is qualified. However I will add something to the original thread that makes it clear it is the donators choice as to who they donate to (I'm not going to automatically assign phones to people).
Lending
--- Donator Application ---
Donation Type: Lending
Phone Type:Samsung Galaxy S i9000 european version
Phone Status:
Stuck in boot loop. Never had access to 3-button download mode... even tried the oven!
Location: Country : Mexico State: Chihuahua City: Juarez
Developer Requirements:
If the device gets fixed I would like it returned.
Extra Information: The device was flashed with AT&T Rom
celtichazard will be lending me his bricked phone so that I can perform some JTAG research into unbricking Galaxy S phones.
If anyone is interested in this research and would like to donate to help cover the cost of shipping, JTAG adapters, wires, components, solder etc. that would be very much appreciated.
The Junkheap sounds like a really good idea .
The JTAG research you are talking about; I have no clue what it is. Is it also related to your Heimdall project? Because that did sound interesting.
Also, I checked out your website at the donate link, and the subjects are so horribly technical, I have no clue what that is about either. So I guess it must be really low-level high-tech ^^.
Edit: donated a little bit. Heimdall could potentially be very practical for all of us .
jjwa said:
The Junkheap sounds like a really good idea .
The JTAG research you are talking about; I have no clue what it is. Is it also related to your Heimdall project? Because that did sound interesting.
Also, I checked out your website at the donate link, and the subjects are so horribly technical, I have no clue what that is about either. So I guess it must be really low-level high-tech ^^.
Edit: donated a little bit. Heimdall could potentially be very practical for all of us .
Click to expand...
Click to collapse
First of all, thank you very much for the donation.
The research that I'll be doing with celtichazard's phone is in regards to finding a way to unbrick any bricked Galaxy S phone. The research is not immediately related to Heimdall. However, if I do manage to work out how to unbrick a phone it will definitely be beneficial for everyone. It will also have a positive effect on the development of Heimdall, as it will allow me to try more experimental functionality without worrying about having to send my phone off to the UK for repair if something goes wrong.
Project Title: JTAG
Project Description:
Trying to figure out a way to unbrick "fully bricked" phones.
Device Requirements:
Any Galaxy S (or derivative) phone in a "fully bricked" state.
Also a fully working one would be nice so I can dump the bootloader.
Location:
Madrid, Spain
Extra Information:
JTAG can bring a bricked phone back to life. If I figure out how to make this work your phone will be fully working. If not then it will still be bricked. I would be willing to return the phone in whatever state it is in when I am done. If you are in the United States a USPS flat rate priority mail box to me is $15. If you have a device that you want to ship let me know and if I need it I will pay for shipping one way.
andrewluecke said:
I am concerned about the liability statement though honestly.. I live in Melbourne, but I am concerned that there isn't a reasonable expectation that the mobile will be working when it is returned (but yes, I'd love to see Heimdell succeed). Also, there isn't any clauses which ensure that provide leverage for mobile's to be returned.
Click to expand...
Click to collapse
I only just realised you edited your post.
The liability statement is mostly in place to ensure developers aren't held responsible for damage (which may or may not have been their fault) or postage related issues.
I understand your concerns in regards to having the device returned, but quite simply there is absolutely no way to enforce such a policy. International law is largely a myth so attempting to enforce any such clause would be near impossible. If you're donating to someone within the same country then you certainly could write-up a contract. I'm not a lawyer, but if a donator wants to organise such a contract with a developer then they're certainly free to do so.
The best thing you can do is to make sure you donate to a reasonably well known developer. If the person you're donating to has a reputation to uphold then you've definitely got some leverage if things get nasty.
Regardless I sincerely hope that we won't see that sort of situation here.
dagentooboy is still looking for someone to donate or lend him a phone. His JTAG research is similar to the work I'll be doing and is extremely important. The more people we have working on it the more likely we'll come across a fix.
If someone has a bricked phone they are willing to donate/lend that would be fantastic.
I suggest to link the developer requests and the donator offers in the first post.
This should help to get a faster overview what is needed/offered.
The link to each post is in the upper right corner of each post.
And i would suggest to use this junkheap for all SGS phones (captivate, vibrant, epic 4g, fascinate & i9000), because most of rom/kernel mods could easily be ported to all sgs phones and development would be faster if developers could have access to all sgs phones.
neldar said:
I suggest to link the developer requests and the donator offers in the first post.
This should help to get a faster overview what is needed/offered.
The link to each post is in the upper right corner of each post.
Click to expand...
Click to collapse
Great idea, I just finished updating the first post.
neldar said:
And i would suggest to use this junkheap for all SGS phones (captivate, vibrant, epic 4g, fascinate & i9000), because most of rom/kernel mods could easily be ported to all sgs phones and development would be faster if developers could have access to all sgs phones.
Click to expand...
Click to collapse
Yeah all phones are accepted depending on what particular developers are after. However thus-far I believe myself and dagentooboy have been willing to accept any SGS phone (including derivatives).
yeah any GSM galaxy s phone would be fine... if it is CDMA I won't be able to test the cell side (to make sure I didn't break it).
Project Title: UnBrickable Mod
Project Description:
An end user solution to unbricking fully bricked phones with only a wire and soldering skills
Device Requirements:
an i9000 device which can have the processor removed and not replaced.
Location:
Louisiana, USA
Extra Information:
UnBrickable Mod has been performed on the Captivate and I'd like to get this modification out to you guys in the i9000 sector. This mod allows you to flash bootloaders and not think twice. Thereby increasing development and allowing for repurposing of our phones at the end of their lives as a Ubuntu device, or similar.
This modification will be fully documented and open-source. It will help the entire community get out of a jam without any additional hardware if they have the skills to solder two points on the board. I must locate these points and it requires removal of the processor. I can return the device which will be inoperative if required.
See video for explanation of how easy it will be to unbrick with UnBrickable Mod.
The execution of a single device will allow resurrection of all others.
Project Title: Thor (an alternative to Heimdall)
Project Description:
Thor is aiming to be more stable and up-to-date.
Here is an XDA thread about it.
Here is a list of new features that I want to test:
1) Ability to flash from BL/AP/CP/CSC .tar archives directly
2) Ability do download latest firmware and flash it automatically
3) Ability to flash compressed (.lz4) files directly (newly discovered)
4) You can shut down the device from GUI immediately (no reboot)
5) PIT viewer built-in, with more accurate information
6) Ability to do NAND Erase All (actually it just erases userdata)
7) Ability to do DevInfo (information about the device: model, carrier id, region, serial code)
Device Requirements:
1) Any Samsung device with Odin v3 protocol
2) Lending only, as my parents would tell me to **** off
Location:
Obviously you don't need this.
Extra Information:
None
Project: PostmarketOS, UBPorts on galaxystmd
Old device: but I have multiple. Willing to send one to device to multiple developers with experience and desire to port for proof-of-concept and/or restoring functionality to this device via mainline Linux (PMOS).
UBTouch would be a secondary effort: as it had been ported during the initial launch, but did not get migrated to the UBPorts project.
3rd effort would be porting latest Lineage, modded/optimized ROM, stripped down/optimized kernel. "One final rodeo."
1 Device per person Per Effort.
So realistically I would give each person up to three devices.
Has anyone tried it yet, what was the outcome?
Is it possible?
Please share your ideas, views and suggestions here.
I think i read somewhere about it, but the project is not continue, unfortunatelly :/
search, maybe you'll find something
Hey Abhishek...
Why do you need to create another thread...??
There are two ongoing threads on the same topic... And if you are interested please head on to those to find out the info about porting android on bada..
Dont create unnecessary threads.... I suggest delete this... or after sometime all we will see in the Bada Section is useless threads....
*facepalm*
Read other topics WWW.ANDROIDPORT.NEt there is the wavedroid project.
Go away and come back when you have some progress for us wavedroid.
Still wondering if wavedroid is a money making exercise or a genuine attempt at getting Android over. The delays don't help the impression this is an exercise being led by folks more eager than actually having the skills to accomplish the task.
I'll be the first to eat my hat if this ever comes to fruition, but I won't be donating anything to something that at this point seems to have only updates on various delays.
Hows this for an interesting post on the JetDroid website...
Not sure why you need the expensive software, it is nice and would help but 95% of the works is already completed for you guys.
To start:
Look for phones with same hardware then use that parts from their android and put the parts into a custom version. You can reuse the /sbin and /system folders from the android sdk virtual machine or if you want better performance use the /sbin and /system of a similar hardware phone android version and just add your init , init.rc , zimage and package this into a rom or dual boot like we do.
CPU:
The wave / Samsung-Intrinsity S5PC110 cpu is much more supported than our s3c6410 and used even by Apple so look at idroid , samsung crespo , HTC 4G android , samsung i9000 for sources for your android files to start from.
Screen:
The screen is possibly the same as S8000 or Spica, wave 3.3" the rest is in other samsung opensource files you just need to mix and match parts.
Obstacles:
The biggest problem might be the cpu and screen + andreno or powervx or Mali display driver but android.so will work until you get to the video driver.
Camera:
Camera is in M910 samsung opensource files / other 5MP camera, there is only a few 5MP camera from that samsung uses so might need to work on the code if you can not find it from a same camera android phone version that is already working.
Now make a good WaveDroid version:
Once you have all this and have it working then you can build a clean custom version of android optmized for your phone. CM for HTC 4G phones might work with almost no or little changes possibly just in the kernel.
The samsung opensource website has the SCH-W850 / SPH-W8500 / SPH-W8550 , this could share some hardware with Samsung Wave as well, similar number codes. Look for a recent code release nov/dec 2010 or later.
Click to expand...
Click to collapse
After reading that, I felt I could almost make an android port myself lol. Clearly there are some very knowledgeable and experienced persons out there.
What really bugs me is the Wavedroid folks have been asking for money for months, yet have shown not a shred of proof they have accomplished anything. Secondly, folks have been asking (rightfully so), why you have not implemented a Paypal widget so people can see just how much money you have raised so far. I know you are using illegal software and thus don't want to let everyone into your inner circle to see the progress, but you have shown and proved absolutely nothing. There are more doubts than positive feelings at the moment.
Please don't let this thread grow to one of two-three pages which is worth nothing, there is already another one just for this purpose
Android port is stuck because programmers dont have any programm to edit the bootloader of wave,so they can not do the port...
If anyone knows any free programm to edit ARM 7 files (like IDA 5.7) please give it to them.
But if nobody knows any programm for this case the have to wait until they have enough money form donations to buy the IDA 5.7
(sorry for my english)
This is outrageous, the fact that you need commercial tools to do what your looking to do clearly denotes your level of incompetence. Look at idroid. i didnt see them asking people for money to buy tools?? And i would say that Apple did a much better job locking down the i range then samsung did with the Wave. If you have stumbled at the starting block just forfeit the race.
Prove to us that you know what the f**k your doing and then you can have your donations.
Generally i supported this project, but then you asked for money. Money changes everything.
sabianadmin said:
This is outrageous, the fact that you need commercial tools to do what your looking to do clearly denotes your level of incompetence. Look at idroid. i didnt see them asking people for money to buy tools?? And i would say that Apple did a much better job locking down the i range then samsung did with the Wave. If you have stumbled at the starting block just forfeit the race.
Prove to us that you know what the f**k your doing and then you can have your donations.
Generally i supported this project, but then you asked for money. Money changes everything.
Click to expand...
Click to collapse
I agree with U
Asking for money, without providing any scrap of proof that anything is even going on, is what irks people here. Not even a simply paypal donation widget exists so folks can see what the $ count is too.
Too many red flags on this one. I know I'm not the first to ask for proof, or even just something other than "we are working it, it'll be done soooooon, give us all your moneys roflwtflolbbq"
So many other android ports happened without need for this software. And also may I point out what seems total ineptitude on the wavedroid team's part. The Galaxy S contains pretty much the identical hardware as the Wave does. In fact you find me a phone that has identical hardware, one running android, the other something else, and tell me we already have as near an android phone as you're going to get. Compared to other port projects, this should have been done in a weekend to be honest.
wavedroid are bogus, and will accomplish nothing just like all the so called Android to Wave projects and groups previously.
I agree with sabian. I don't know a **** about how difficult or easy is this, but i'm pretty sure that there are good developers around here. Why couldn't you start a new project?
I aggre with you guys,it is very odd that they ask for money without doing anythink...
I just posted that if you know any free software that works with ARM7 files it would be good to inform then...
But they have a very good reason to ask for money because if they can not edit the bootloader they can not load anythink else from bada...if they do that the project it would be almost done because wave and galaxy s have similar hardware so with some fixes to scripts they will have a very good androidport to wave..
Was the app built on top of open sourced code? Is it coming back? I've got a bad feeling, like we're not going to see a properly functioning HDMI app any time soon ...
not sure what the issue is but the official thread is here
http://forum.androidcentral.com/htc...llhdmi-official-fullhdmi-beta-discussion.html
xeren said:
Was the app built on top of open sourced code? Is it coming back? I've got a bad feeling, like we're not going to see a properly functioning HDMI app any time soon ...
Click to expand...
Click to collapse
From what I've gleaned the only open source stuff he modified had to do with the HDMI chip in the kernel. As far as I know he has released source to those particular bits.
He _NEVER_ has to release the source to the APK if he doesn't want to. (As more than likely it is an "in-house" effort.)
Fair & square, he did the work.
If he wants cash, he'll get it.
If he wants reputation, he'll get it.
(Although I doubt it will take people very long to see what he's doing and release an entirely free implementation IF he has in fact released the source for the kernel modifications he made. If not, http://www.gnu.org/licenses/gpl-violation.html is one click away.)
Supply and demand
EDIT: Just checked and as of 3/3/11 at 10:03 PM central time, he has _NOT_ released his kernel source modifications (gee, wonder why) and is in direct violation of the GPL.
Even androidcentral has forced him to take his links down to his "illegal" kernels.
In my opinion, this guy needs to get his act together. He's pulling a solo-Samsung and doing nothing but hurting the development community.
Here's a quick page for everyone to digest to understand what exactly he is doing that is against the GPL and its terms and could put him at the peril of a lawsuit: http://stackoverflow.com/questions/2721290/propietary-modules-within-gpl-and-bsd-kernels
To sum everything up, I see one of four things happening from this current scenario:
A) He releases the source modifications, and goes on living a semi happy life that will always be plagued with people remembering his defiance to follow the GPL.
Within weeks of his modifications being released I predict another individual developer will code up some hooks to link in with his kernel modifications, and bam: Free (hopefully) HDMI output app for everyone from a past or new XDA dev, and paid app for the chumps that support GPL violators or people that truly believe what he was doing is correct.
B) He realizes that once his kernel modifications are out that his apk will be useless, so he chooses not to release the mods at all thus ending this chapter in HDMI development. (And possibly ending litigations against him that may have been initiated at the request of people notifying the GNU foundation on him. Although it is rare that they would file suit against someone not CURRENTLY taking payments for GPL'd code (note he hasn't "released it" for pay yet))
C) He pulls an nvidia/samsung with his kernel module, creating two portions. One LGPL that he releases the source to and must be compiled alongside the kernel, and he includes a binary kernel module that MAY or may not kernel panic your kernel when you attempt to modprobe it. (But I don't think he can do that as he didn't create the entire work of the HDMI driver source. The license for that particular file is GPL, so he MUST release it as far as I can see.)
There is also an option D - he mans up and releases _ALL_ of his work and is revered & cheered for being a good soul. Although he will still suffer from some discredit because of his GPL folly.
In my opinion, the only reason he is not releasing the kernel modifications is because once they are released, ANYONE will easily be able to make an apk to control the output, thus ending any form of possible revenue from this "project" for him.
My gut feeling says he intended to release the kernel modification source AFTER he had racked up some sales. (Which would have been atrociously dumb from a legal stand point)
Whew!
I have been following all of his work, and he did attempt to make the modified kernel drivers public to any kernel devs that wanted to use them and incorporate them into their kernels. Not realizing that it was a violation to modify without posting source code, he soon after voluntary removed the kernel link. He has been very busy developing his work and will release source code with all the new kernels in his next free public beta release due out very soon. If you want to know more you can read the op posted on A/C.
Sent from my mobile HDMI device
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.