Related
I have been looking for a more secure _and_ private android rom and have been trying to follow CopperheadOS (CHOS) and Secure Spaces (SS) with only limited sucess. There seems to be a bit more press surrounding CopperheadOS and have heard some good things from sec oriented sites about it but at the same time SS seems to use isolation (something that quite a few sec types bring up and ref Qubes [desktop not mobile OS]) and I think that SS is used on the Blackphone (perhaps not a ringing endorsement but not bad?).
So, I can't find any comparisons, reputable or otherwise of the two Operating systems.
I like that CHOS is trying to go with the google-less ethos however there are about 3 apps I have that I think I can only get on google play (and at least one of them seems to depend on google play for some anti-piracy validation, annoying but damn good app). I am not sure if SS offers a google-less option, and even if it doesn't does that isolation make the google privacy issues a bit less of an issue? (like a space/virt-machine/qube whatever that has google stuff but is completely disconnected from the net?)
Most the individual reviews of both have been pretty superficial so its been all around disappointing that I can't find any in depth reviews not to mention comparisons!
Please tell me someone out there knows of some, or feel free to post the pros and cons of each, would make a *very* useful thread.
gaikokujinkyofusho said:
I have been looking for a more secure _and_ private android rom and have been trying to follow CopperheadOS (CHOS) and Secure Spaces (SS) with only limited sucess. There seems to be a bit more press surrounding CopperheadOS and have heard some good things from sec oriented sites about it but at the same time SS seems to use isolation (something that quite a few sec types bring up and ref Qubes [desktop not mobile OS]) and I think that SS is used on the Blackphone (perhaps not a ringing endorsement but not bad?).
So, I can't find any comparisons, reputable or otherwise of the two Operating systems.
I like that CHOS is trying to go with the google-less ethos however there are about 3 apps I have that I think I can only get on google play (and at least one of them seems to depend on google play for some anti-piracy validation, annoying but damn good app). I am not sure if SS offers a google-less option, and even if it doesn't does that isolation make the google privacy issues a bit less of an issue? (like a space/virt-machine/qube whatever that has google stuff but is completely disconnected from the net?)
Most the individual reviews of both have been pretty superficial so its been all around disappointing that I can't find any in depth reviews not to mention comparisons!
Please tell me someone out there knows of some, or feel free to post the pros and cons of each, would make a *very* useful thread.
Click to expand...
Click to collapse
Nothing? Really?
gaikokujinkyofusho said:
I have been looking for a more secure _and_ private android rom and have been trying to follow CopperheadOS (CHOS) and Secure Spaces (SS) with only limited sucess. There seems to be a bit more press surrounding CopperheadOS and have heard some good things from sec oriented sites about it but at the same time SS seems to use isolation (something that quite a few sec types bring up and ref Qubes [desktop not mobile OS]) and I think that SS is used on the Blackphone (perhaps not a ringing endorsement but not bad?).
So, I can't find any comparisons, reputable or otherwise of the two Operating systems.
I like that CHOS is trying to go with the google-less ethos however there are about 3 apps I have that I think I can only get on google play (and at least one of them seems to depend on google play for some anti-piracy validation, annoying but damn good app). I am not sure if SS offers a google-less option, and even if it doesn't does that isolation make the google privacy issues a bit less of an issue? (like a space/virt-machine/qube whatever that has google stuff but is completely disconnected from the net?)
Most the individual reviews of both have been pretty superficial so its been all around disappointing that I can't find any in depth reviews not to mention comparisons!
Please tell me someone out there knows of some, or feel free to post the pros and cons of each, would make a *very* useful thread.
Click to expand...
Click to collapse
Well spaces is actually not really an OS. it is more a feature for an OS. It is available for download only for the nexus devices (5 and 5x) but this is indeed a stock android with spaces feature included.
The blackphone is claimed to be the world's most secure phone. I had a blackphone 1, hacked it, with a remote hack, handed in POC at bugcrowd, cashed in, but David Puron the head developer has told me that they will not fix this bug anymore as they simply can't on this older version of android. The blackphone 1 has some severe software bugs (not necessarily more vulnerabilities), but development has completely stopped for that phone, and I was advised to buy the blackphone 2 instead. lol. No, thank you.
So if you want security and privacy on your device, well I guess a Nexus 5x or any other of the supported devices (I have the 5x) with copperheadOS is your best choice. CopperheadOS is not a google-less option, it is a complete open source android with no google at all, as in free software based on debian linux, that focuses on security. Fast patching!
If you want google on your device, well you know, then security and privacy are gone.
Hello,
After some investigation on https://github.com/MotorolaMobilityLLC/kernel-mtk/tree/MMI-NMA26.42-113 and inside the /etc/bluetooth/btstack.conf I found out the Moto E4 device is using the BlueZ stack, with the unpatched l2cap_core.c.
Just look, this is a sample from the official Motorola github kernel site (the prototype of the function l2cap_build_conf_req)
Code:
static int l2cap_build_conf_req(struct l2cap_chan *chan, void *data);
And this one is from the official Linux kernel source:
Code:
static int l2cap_build_conf_req(struct l2cap_chan *chan, void *data, size_t data_size);
data_size, where is data size on Motorola, this is the problem!
Fix it, Mediatek! Fix it, Motorola!
I forgot to mention, NMA26.42-113 promised October 2017 security level.
More proof: Just look at https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=e860d2c904d1a9f38a24eb44c9f34b8f915a6ea3
This shows exactly the spots that need to be changed!
You are dreaming if you think Motorola will release an update ....
Your answer is a custom rom with newer patches like the ones by Izaq......
Go check out the patch level of his DotOs & RR
That's why we come to XDA ..to root & flash custom roms .
KevMetal said:
You are dreaming if you think Motorola will release an update ....
Your answer is a custom rom with newer patches like the ones by Izaq......
Go check out the patch level of his DotOs & RR
That's why we come to XDA ..to root & flash custom roms .
Click to expand...
Click to collapse
True. Take time reading through pros/cons of each option (there are many); not all ROMs are equal and may lack the necessary customizations for this device. Ignore the happy extremes ("it's great"/"it sucks") as neither typically reflect reality. I generally stick with rooted stock on unlocked Moto devices enhanced with a few Magisk and Xposed modules. Everything just works and I'm not concerned with obscure vulnerabilities. Stability and solid battery life are top priorities. Very little bloatware added by Moto and most of it is useful; carrier crap is a different story (FWIW - I never purchase carrier branded phones). Responsible app selection and browsing behavior are cornerstones of good device hygiene. I also run a VPN based ad blocker and firewall which ads another virtual condom. My mobile is a productivity tool that needs to be there 7x24. For that stock is often, albeit not always, the best option. Good luck.
Thank you, but unfortunately a custom ROM is not an option. I use the Moto E4 as a daily driver, if I do this, then I lose stability. Plus Motorola says I might lose encryption if I unlock bootloader (and root the stock ROM) and I know custom ROMs often have broken encryption (not in sense of security, just doesn't work, bootloop, etc....).
iodev said:
Thank you, but unfortunately a custom ROM is not an option. I use the Moto E4 as a daily driver, if I do this, then I lose stability. Plus Motorola says I might lose encryption if I unlock bootloader (and root the stock ROM) and I know custom ROMs often have broken encryption (not in sense of security, just doesn't work, bootloop, etc....).
Click to expand...
Click to collapse
There are steps you can take to maintain data encryption on a unlocked device running a rooted Moto (stock) ROM. That said, if there is no compelling reason to root don't! There are many easy, practical ways to mitigate security concerns without resorting to paid apps & subscriptions that offer little benefit given the robust Android/Google Services security framework already in place. Rooting can undermine that model unless other precautions are taken ... most of them behavioral.
Reread my prior post. If you are loosing sleep over Blueborne simply disable the Bluetooth radio in public locations. Before doing that ask yourself why someone would target you and/or your device with a short range 'attack' that will likely yield nothing of interest. Mainstream media does a huge disservice identifying potential vulnerabilities without accompanying risk profile. Yes, Moto should fix it but they probably won't.
Davey126 said:
Reread my prior post. If you are loosing sleep over Blueborne simply disable the Bluetooth radio in public locations. Before doing that ask yourself why someone would target you and/or your device with a short range 'attack' that will likely yield nothing of interest. Mainstream media does a huge disservice identifying potential vulnerabilities without accompanying risk profile. Yes, Moto should fix it but they probably won't.
Click to expand...
Click to collapse
Yes, I am already doing that (seemed common sense to turn off Bluetooth when not using it, to ensure safety and preserve battery). Thank you anyway!
Yeah, they won't fix it ... they don't care.
iodev said:
Yes, I am already doing that (seemed common sense to turn off Bluetooth when not using it, to ensure safety and preserve battery). Thank you anyway!
Yeah, they won't fix it ... they don't care.
Click to expand...
Click to collapse
Boils down to resource management. This isn't a big threat and fixing it isn't going to sell more handsets in a world where 95% of customers/users don't weigh vendor security posture when making purchase decissions.
Davey126 said:
Boils down to resource management. This isn't a big threat and fixing it isn't going to sell more handsets in a world where 95% of customers/users don't weigh vendor security posture when making purchase decissions.
Click to expand...
Click to collapse
That's because people don't read CNET Security News
Instead they totally ignore that and when it hits them they go "Why me!?" instead of actually fixing it, so next time they also go "WHY does this happen to ME!?"
iodev said:
That's because people don't read CNET Security News
Instead they totally ignore that and when it hits them they go "Why me!?" instead of actually fixing it, so next time they also go "WHY does this happen to ME!?"
Click to expand...
Click to collapse
Surfacing potential and exposing bad behavior is a journalistic responsibility. That said, potential and reality are often distant partners that leaves the audience unsettled as risk assessment/mitigation are usually omitted. Read responsibly, my friend.
Davey126 said:
Surfacing potential and exposing bad behavior is a journalistic responsibility. That said, potential and reality are often distant partners that leaves the audience unsettled as risk assessment/mitigation are often omitted. Read responsibly, my friend.
Click to expand...
Click to collapse
Yeah, you're right, I'm sorry, I find it hard to differentiate between potential and reality (sometimes).
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
https://www.xda-developers.com/android-13-hardware-drivers-licenses/
February 16, 2022 10:26am Adam Conway
Google is changing how new Android 13 devices should store driver’s licensesCarrying a wallet has become less of a necessity for me thanks to my smartphone and Google Pay, but there are a few cards that I can’t go without. A driver’s license would be one such card, though a digital driver’s license offers multiple advantages over the traditional ID card. You can’t lose it, you can wipe it remotely if your phone gets stolen which means you’re less likely to get your identity stolen, and you’ll have an easier time bringing it up on request. Google introduced the Identity Credential API in Android 11 for storing identity cards, though now it appears that devices launching with Android 13 will require additional hardware for storing digital driver’s licenses.
As reported by Esper, a recent code change suggests that chipsets launching with Android 13 must support the Identity Credential Hardware Abstraction Layer (HAL) at feature version 202201 or later. 202201 of the Identity Credential HAL introduces support for presenting multiple documents during a single transaction, such as simultaneously sharing your driver’s license and motor vehicle registration. Google can’t mandate that devices upgrading to Android 13 must support it, but new devices that launch with Android 13 will need to, as enforced through a test in the Vendor Test Suite, or VTS.
For context, the VTS is an automated testing suite that validates the vendor implementation is compliant with Google requirements. It consists of a set of testing frameworks and test cases, testing both the Android system’s core HALs and libraries, and the low-level system software such as the kernel, modules, and firmware.
The Identity Credential HAL enables the storing of identity documents in the device’s secure hardware, which is met by the inclusion of a Trusted Execution Environment, or TEE. This is a dedicated area of the main applications processor for executing sections of code in an isolated environment. Not many devices have actually introduced the Identity Credential HAL despite TEE implementations being widespread.
Interestingly, there’s also the Identity Credential Direct Access HAL too, though its implementation won’t be required. It essentially allows for direct access via NFC to the secure enclave that holds a user’s documents even when the battery is too low to boot the OS. This is only possible when the secure hardware features a CPU and storage device separated from the applications processor. Very few devices meet this criterion, and the only devices that currently implement the Identity Credential HAL itself are Google Pixel devices.
While mobile driver’s licenses are gaining traction across the U.S., Google intends for the identity credentials API to be generic and to hold other secure documents, too. Motor vehicle registration and vaccination records are two potential use cases. The TSA plans to begin recognizing mobile driver’s licenses as valid IDs for domestic travel soon, and at least 30 U.S. states have already issued or plan to issue them. We’ve already seen as well that with iOS 15, Apple announced that the TSA would accept its digital IDs for domestic travel.
There are obviously a ton of security concerns when it comes to storing personal identification on your smartphone, but Google is taking steps to make it as safe as possible. There’s definitely an upside to carrying your documents digitally instead of a physical card that can be lost or stolen, but additional hardware for storing those documents will go a long way towards convincing authorities to use the Identity Credential API when developing these applications.
Click to expand...
Click to collapse
That is impressively backwards. Digital means *easier* to steal than something physical. Regardless of what kind of nonsense hardware is associated with it, gooble's control over their blobware means that this kind of thing OPENS UP THE DOOR to MASS identify theft.
Speaking as a computer engineer.... NO EFFIN WAY.
96carboard said:
That is impressively backwards. Digital means *easier* to steal than something physical. Regardless of what kind of nonsense hardware is associated with it, gooble's control over their blobware means that this kind of thing OPENS UP THE DOOR to MASS identify theft.
Speaking as a computer engineer.... NO EFFIN WAY.
Click to expand...
Click to collapse
You're entitled to your opinion. I think probably 99% of the folks who regularly read in the P6P section already know your opinion on that because you feel a need to visit so many threads and repeat this, and even repeat similar or the same things in multiple threads one right after the other. Whether you're right or wrong, doesn't matter. If you could please resist the temptation to repeat it in my threads, I'd greatly appreciate it.
Maybe make a thread specifically for your purpose.
Thank you.
96carboard said:
That is impressively backwards. Digital means *easier* to steal than something physical. Regardless of what kind of nonsense hardware is associated with it, gooble's control over their blobware means that this kind of thing OPENS UP THE DOOR to MASS identify theft.
Speaking as a computer engineer.... NO EFFIN WAY.
Click to expand...
Click to collapse
Much more fun to give myself to Google and let the ecosystem work for me.
/half sarcasm
Scary stuff. This feels like the precursor to vaccine passports, and social ranking like China. Scan your phone to see if you are allowed to eat here.
roirraW edor ehT said:
You're entitled to your opinion. I think probably 99% of the folks who regularly read in the P6P section already know your opinion on that because you feel a need to visit so many threads and repeat this, and even repeat similar or the same things in multiple threads one right after the other. Whether you're right or wrong, doesn't matter. If you could please resist the temptation to repeat it in my threads, I'd greatly appreciate it.
Maybe make a thread specifically for your purpose.
Thank you.
Click to expand...
Click to collapse
These things can't be repeated enough.
As we discussed xxxx I decided to prepare the bounty for anyone who will unlock 5G support for most/all countries. Feel free to support it (because Google doesn't want to...). You can find it there:
xxxxxx
Introduction and details are either in link or below in citation.
Hello everyone! I'm Sebastian and I'm part of XDA Community since 2010 (XDA profile)
Actually, It's not the first time I tried to encourage people to donate for anyone who will make a modification for an Android phone: Back in 2012 as LG 4X community we tried to either force LG to unlock bootloader by petitions or collect a bounty for possible developer who would do that unofficially.
Ten years passed and again me and other people faced a problem with a company which blocks the features on a phone for no reason. This time it's 5G for Pixel 6 (Pro), codename oriole/raven. My carrier (Orange Poland) uses basically the same 5G band/parameters as Magenta Austria (which is officially supported) and I can't use 5G because Google doesn't allow me just because. This is sad and disgusting.
For now at least we have working VoLTE/VoWiFi Magisk module which can be found here but that's it. Tensor SoC makes things even worse, because previous Pixels could be unlocked via Qualcomm tools.
I've tried to reach a few modders/devs by myself but either they have no idea or don't care...so I hope that money would be the best motivator
Okay, so now simple rules:
- All collected money goes to the person who will share a working software mod (Magisk/Xposed module, modem patch or whatever works), either for me on private message on XDA (and then we can share it for private testing for the ones who donated) or just share for public testing on XDA thread
Then after either private or public tests, bounty gets finished and the money will be sent.
- If we don't succeed or Google will come with official solution (doubt), I will cancel this campaign and contact the support to force the refund. In case of any problems, I recommend to leave any contact (email) while you donate to this bounty.
Also keep in mind that the modification will most likely require unlocked bootloader and/or root (although the less invasive solution, the better.
PS: Feel free to spam Google about that abomination here or other Support Google threads. It's time to them to finally explain to us why we can't use Pixel phones' features even if they are supported.
Click to expand...
Click to collapse
MOD EDIT: Links removed.
thanks for setting this up
Thanks Sebastian!
Already donated. Hope the campaign will succeed.
If the campaign fails, what happens to the money raised?
I think it's woth noting on your post.
itamargs said:
Thanks Sebastian!
Already donated. Hope the campaign will succeed.
If the campaign fails, what happens to the money raised?
I think it's woth noting on your post.
Click to expand...
Click to collapse
I will delete/cancel it and contact support to force the refund. Also if anyone has any doubts, he can suggest me how i could "authenticate" myself even more. I'm here for 12 years already and had a history with mods, TWRP and custom ROMs, I have not violated anyone's trust.
Edit: added description on campaign site, I will polish this thread a little after I take my PC
Edit2: Okay, everything is done. I'm about to make a thread on Oriole section as well as make some posts in threads related to 5G which I was looking on. Might try to share the info on some Telegram groups too
Have to consider your carrier's coverage, what bands they use for 5g and if they have a band whitelist just connecting to any 5g band won't do jack for you
maxius4 said:
Have to consider your carrier's coverage, what bands they use for 5g and if they have a band whitelist just connecting to any 5g band won't do jack for you
Click to expand...
Click to collapse
Well, I have an 5G antenna around 10m from my flat... I talked with my carrier about it, they tried to do anything but they couldn't. It's only Google's fault, every other manufacturer somehow supports 5G when modem supports it, but Google just won't do that.
I have also donated, fingers crossed this will eventually work. Thank you for your work!
reas0n said:
Well, I have an 5G antenna around 10m from my flat... I talked with my carrier about it, they tried to do anything but they couldn't. It's only Google's fault, every other manufacturer somehow supports 5G when modem supports it, but Google just won't do that.
Click to expand...
Click to collapse
Have to take into account this is more a carrier issue than googles, the issue is you not buying the phone from them but from Google and they are not going to go out of their way to support a phone that was not purchased from them
Thank you. You should also be posting same on pixel 6 forums to get more attention.
maxius4 said:
Have to take into account this is more a carrier issue than googles, the issue is you not buying the phone from them but from Google and they are not going to go out of their way to support a phone that was not purchased from them
Click to expand...
Click to collapse
Google doesn't even sell P6 in Poland. Also as I said in description: hardware supports it, my carrier uses same band/frequency as other carrier in Austria which is supported. If you still don't believe: take a look on Pixel 5 forums, they have a 5G unlock with Qualcomm tools. 100% it's Google's stupidity.
In the past I bought some Chinese phones and with global ROM they just worked..
The issue is the carrier and Google can not sell a phone with everything unlocked as it would run across a world of hurt from every country's on earth regulators that deal with spectrum use. Sure you can "unlock" it but with age of a phone comes vulnerabilities and fw updates to fix issues also your carrier / someone may care more than you want them to about you essentially breaking your country's communications/spectrum laws. Honestly, is it really worth all the trouble to make it work how you want it to or get a phone from your carrier with the support you want?
MOD ACTION:
Thread closed.
@reas0n
Please await my PM.