Even when you buy physical books, due to the nature of copyright laws in basically every country that has them, you aren't really buying those physical items so much as paying a license fee for the rights to access the data encoded on them.
There are some extremely far-reaching consequences of this that most people fail to realize or think don't apply because of some matter of physicality (which doesn't matter one iota in the eyes of the law.)
Android also requires device maps to give you state-of-the-1980s base memory addresses for device MMIO.
There's no PCI(e) interface on your phone, or any other "safe" means of software discovering what hardware is in the device. Just like any 8-bit microcomputer you grew up with, hardware control is done by writing memory values to various hardcoded memory addresses. If the sound driver, for example, doesn't know the exact base address of the sound controller, it won't init the sound at all and may even accidentally crash the system if it ends up feeding the wrong commands into the wrong hardware subsystem.
Remember when Windows 95 and 98 would do auto-detect for non-PnP hardware and the ever-present warning that the process could hang the machine was present? Yep, exact same story here.
It's an earlier USB 1.1 revision, not a later USB 2.0 revision. (And you can only distinguish the two by plugging them in and using `lspci` or such. There's no means by external visual inspection to determine if the integrated USB hub is 1.1 or 2.0 - thanks, Apple!)
OS APIs on memory management, amongst other things, affects how V8's JIT needs to work. Instruction set stuff is done since Chrome is already on Android/ARM64.
Hell, let me add this: Verizon's earliest global phones were "technically" dual-SIM. The CDMA modem and GSM modem could function (although the firmware programming for this was absent) simultaneously and independently and used two independent subscriber identities.
From the perspective of the firmware, it was just two independent cell modems, and was handled much the same as a dual-SIM phone was, although with the hacks to make them appear as one for the sake of delivering the user experience Verizon sold the end user on.
It's not to do with "US networks" and the phone isn't trying to tell the network to refuse outbound calls. It's due to glitchiness in handling 3GPP and 3GPP2 networks at the same time in the same baseband modem.
Multi-SIM phones aren't common in the US because of incompatible networks and frequency bands, and a drive (by American consumers) for high-speed mobile data.
Most multi-SIM phones limit one or more SIMs to 2G GSM only, which limits those secondary SIMs to the T-Mobile network in most locations. (There are other 2G GSM networks, but ALL of those others are small regional networks with seriously limited coverage, and T-Mobile already has roaming agreements in place with all of them.)
Getting LTE and CDMA working in the same phone on a single SIM involved enough hacks as it is (this is why Verizon's earliest global phones used the SIM solely for the GSM modem and kept the CDMA modem totally separate, it took OEMs years to work out all the bugs). Getting it working over multiple SIMs is, of course, going to be a nightmare.
The rest of the world avoids this by:
1. Using a single technology stack (3GPP's GSM, UMTS, LTE, and NR), and completely eschewing (or having already completely shut down) anything on the 3GPP2 (cdmaOne, CDMA2000 1xRTT, and CDMA2000 1xEV-DO) technology stack.
2. Not charging subscribers for incoming calls. (but everyone pays premium calling rates to call a cell phone.)
3. Having consumers that are perfectly happy with their mobile internet running at 90s dial-up speeds (EDGE speeds in practice do not go over 70kbit/s on a moderately-used cell site).
Provisioning. T-Mobile doesn't have the system in place to remote-provision a eSIM. Project Fi works by using their own infrastructure to constantly reprovision the (e)SIM (this is also done for their traditional SIMs.)
Because Project Fi uses multiple subscriber identities (basically multiple independent SIM cards rolled into one, one for each underlying network - T-Mobile, Sprint, and US Cellular) and dynamically swaps them out throughout the day, they have to handle this themselves instead of relying on regular carrier procedures.
Apple is dual-LTE dual-standby when both operators are pure 3GPP (GSM/UMTS/LTE/NR) instead of 3GPP2 (CDMA) plus 3GPP (LTE). Getting CDMA and LTE to work in Android phones years ago was a fucking clusterfuck for OEMs.
The nation was based on the notion that property ownership gives individuals a stake in the system.
The type of property that this refers to, is real property. The clothes on your back don't give you a stake, the ground beneath your feet does. This is why some feel those that only rent their home should not have the right to vote.
CDMA2000 1xEV-DO is used in Europe on a few networks. Norway recently had an operator switch their 450MHz network from CDMA2000 EV-DO to LTE, Ukraine has one, mostly old Soviet bloc nations have 'em left. They're dying, though.
"true 4G", huh? It's "true 4G" if you ignore the downlink bandwidth requirement because it was set unrealistically. A novel air interface, unprecedented latencies, unprecedented spectral efficiencies (by far)... Unless you're intent on sucking IMT-R's dick, then AT&T shut down it's True 3G IMT-SC network in 2017.
Data sessions are routed back to the core network of the network issuing your SIM; you'll find that you can access region-locked content whilst internationally roaming if using mobile data. Only on a few outdated networks are you actually using that network's gateway whilst roaming.
Bootlickers tend to support the government subsidizing those that are less capable. Your rejection of my argument would, therefore, make you the bootlicker, and your comment thus is projection.
Slashdot Mirror
Even when you buy physical books, due to the nature of copyright laws in basically every country that has them, you aren't really buying those physical items so much as paying a license fee for the rights to access the data encoded on them.
There are some extremely far-reaching consequences of this that most people fail to realize or think don't apply because of some matter of physicality (which doesn't matter one iota in the eyes of the law.)
Android also requires device maps to give you state-of-the-1980s base memory addresses for device MMIO.
There's no PCI(e) interface on your phone, or any other "safe" means of software discovering what hardware is in the device. Just like any 8-bit microcomputer you grew up with, hardware control is done by writing memory values to various hardcoded memory addresses. If the sound driver, for example, doesn't know the exact base address of the sound controller, it won't init the sound at all and may even accidentally crash the system if it ends up feeding the wrong commands into the wrong hardware subsystem.
Remember when Windows 95 and 98 would do auto-detect for non-PnP hardware and the ever-present warning that the process could hang the machine was present? Yep, exact same story here.
I prefer the devil's lettuce, thank you very much.
It's an earlier USB 1.1 revision, not a later USB 2.0 revision. (And you can only distinguish the two by plugging them in and using `lspci` or such. There's no means by external visual inspection to determine if the integrated USB hub is 1.1 or 2.0 - thanks, Apple!)
OS APIs on memory management, amongst other things, affects how V8's JIT needs to work. Instruction set stuff is done since Chrome is already on Android/ARM64.
Sadly, we still let you on the Internet.
Probably a lot of Windows-specific segments that assume x86/x86_64 that break on Windows/ARM64 (or at least fail unit testing)
Hell, let me add this: Verizon's earliest global phones were "technically" dual-SIM. The CDMA modem and GSM modem could function (although the firmware programming for this was absent) simultaneously and independently and used two independent subscriber identities.
From the perspective of the firmware, it was just two independent cell modems, and was handled much the same as a dual-SIM phone was, although with the hacks to make them appear as one for the sake of delivering the user experience Verizon sold the end user on.
It's not to do with "US networks" and the phone isn't trying to tell the network to refuse outbound calls. It's due to glitchiness in handling 3GPP and 3GPP2 networks at the same time in the same baseband modem.
Multi-SIM phones aren't common in the US because of incompatible networks and frequency bands, and a drive (by American consumers) for high-speed mobile data.
Most multi-SIM phones limit one or more SIMs to 2G GSM only, which limits those secondary SIMs to the T-Mobile network in most locations. (There are other 2G GSM networks, but ALL of those others are small regional networks with seriously limited coverage, and T-Mobile already has roaming agreements in place with all of them.)
Getting LTE and CDMA working in the same phone on a single SIM involved enough hacks as it is (this is why Verizon's earliest global phones used the SIM solely for the GSM modem and kept the CDMA modem totally separate, it took OEMs years to work out all the bugs). Getting it working over multiple SIMs is, of course, going to be a nightmare.
The rest of the world avoids this by:
Provisioning. T-Mobile doesn't have the system in place to remote-provision a eSIM. Project Fi works by using their own infrastructure to constantly reprovision the (e)SIM (this is also done for their traditional SIMs.)
Because Project Fi uses multiple subscriber identities (basically multiple independent SIM cards rolled into one, one for each underlying network - T-Mobile, Sprint, and US Cellular) and dynamically swaps them out throughout the day, they have to handle this themselves instead of relying on regular carrier procedures.
Apple is dual-LTE dual-standby when both operators are pure 3GPP (GSM/UMTS/LTE/NR) instead of 3GPP2 (CDMA) plus 3GPP (LTE). Getting CDMA and LTE to work in Android phones years ago was a fucking clusterfuck for OEMs.
Let me draw you an ASCIIart Venn Diagram: ( people who root ) [a gap] ( people who get hacked ) Does perhaps that explain it?
And yet this type of thinking persists into the 21st century. Those that do not learn from history are doomed to repeat it.
The type of property that this refers to, is real property. The clothes on your back don't give you a stake, the ground beneath your feet does. This is why some feel those that only rent their home should not have the right to vote.
"3G GSM" or "3GSM" is actually UMTS/HSPA. It's still active on AT&T, T-Mobile, CellularOne of New Mexico, etc.
Roughly 15x15MHz of spectrum, depending on the local market. 5x5 1xEV-DO and 5x5 1xRTT on 850MHz (BC0) and 5x5 1xRTT on 1900MHz (BC1).
CDMA2000 1xEV-DO is used in Europe on a few networks. Norway recently had an operator switch their 450MHz network from CDMA2000 EV-DO to LTE, Ukraine has one, mostly old Soviet bloc nations have 'em left. They're dying, though.
T-Mobile also operates a GSM/UMTS/HSPA network on a standard band (Band 2, 1900MHz PCS.)
"true 4G", huh? It's "true 4G" if you ignore the downlink bandwidth requirement because it was set unrealistically. A novel air interface, unprecedented latencies, unprecedented spectral efficiencies (by far)... Unless you're intent on sucking IMT-R's dick, then AT&T shut down it's True 3G IMT-SC network in 2017.
Data sessions are routed back to the core network of the network issuing your SIM; you'll find that you can access region-locked content whilst internationally roaming if using mobile data. Only on a few outdated networks are you actually using that network's gateway whilst roaming.
Find out more, click here!
Stop going to places where incest is a common practice.
Bootlickers tend to support the government subsidizing those that are less capable. Your rejection of my argument would, therefore, make you the bootlicker, and your comment thus is projection.
Preach!