Database Develop

[Q] Possible to use HTC Dream with UMTS Band VI?

Hi all,
Brand new owner of a T-mobile G1 here, got a possibly low level question. I will be living in an area with only UMTS band VI coverage for the next 4-6 months. I see that band VI is a subset of the frequencies used in band V. I have seen a couple of posts around the web suggesting that some band V phones can be used on band VI. I assume it has something to do with code in the radio stack or somewhere in the OS? I am working on flashing Cyanomod 6.1.0-RC1-DS onto my Dream tonight/tomorrow (so I don't know yet if it will just work out of box haha). Anyone have any advice/thoughts? I apologize if this has been asked/answered before - I have done a lot of searching/reading and haven't been able to figure out the answer. Thanks in advance!
-David
Reference links <er, um, apparently i can't post outside links here yet as a new user so i'll replace them with instructions for making google give you the link as the first hit >
UMTS frequencies -- google "umts frequency bands"
video of 3G iPad supposedly working on band VI -- google "ipad foma 800Mhz"
discussion of iPhone4 and band VI -- google "iPhone 4 frequency changes"
(also posted at cyanogenmod's general HTC Magic forums under the title possible-to-use-htc-dream-with-umts-band-vi )

[Q] Anyone know of a custom ROM with modified NFC support?

Does anyone know if there are any custom ROMs for the Nexus 6 that have some NFC optimizations for the Broadcom BCM20795 controllers? There are some known issues in Android where the NFC (IsoDep): maximum transceive length is hard-coded (261 Bytes), although some NFC Controllers are able to send more than 2000 Bytes.
https://code.google.com/p/android/issues/detail?id=76598
According to the Broadcom announcement the Broadcom BCM20795 extends data rates to 848 kbps and should support extended length APDUs. However, the code for the native NFC manager does not look as if it is capable of handling this just yet.
https://android.googlesource.com/platform/packages/apps/Nfc/+/master/nci/src/com/android/nfc/dhimpl/NativeNfcManager.java
Some vendors like Samsung and Sony are modifying these components for their hardware and the Galaxy S5 and Xperia Z3 and Z3 compact but Motorola has not done so for the Nexus 6., so I am wondering if anyone in the development community has done this yet. It appears to be a relatively straightforward fix if you can modify the NativeNFCManager.java and build it with the new values< (assumed to be IsoDep transceive length of 65279 bytes as reported by TagInfo)

Im sorry to comment on this old thread..
Anyway, I can confirm that the Galaxy S5 and some Xperia models are capable of handling extended length apdus, and the manufactures must have somehow changed the settings in NativeNFCManager.java.
I dont know any customs roms which have changed the code in the NativeNFCManager, so i decided to this my self. Im happy to share the results of this test...
But even if its possible, it will not change the fact that the phones which are already out there are not capable of handling extended commands. Google needs to change this!!
So everyone who is interested in this issue please leave a comment on this issue https://code.google.com/p/android/issues/detail?id=76598!

[Q] WP 10 on with Root Tool on 640

Hay folks. I saw that is possible to get WP 10 working on the lumia 930/Icon by changing the device id to emulate a 1520. So theoretically the same procedure can be used for the lumia 640. Would I just have to change [HKEY_LOCAL_MACHINE\System\Platform\DeviceTargeting Info] to something with similar hardware like the 830 or some other device ? Did anyone give this a try ?

Why would you need to? The 640 is already supported. In fact, I think it was supported before the 1520 was.
http://windows.microsoft.com/en-us/windows/preview-supported-phones

Because it's actually not supported thanks to a bug in the firmware that the phones shipped with. Once you upgrade to the TP 10 you can't downgrade.
And until they fix it there are no builds available even though they claim that the phone is supported and that was the reason I bought it in the first place.

[Q] Is 'seed' the code name of all 2nd gen Android One with Snapdragon 410 chip?

I just want to know if they (i-mobile IQ II, General Mobile 4G, etc) all have the same code name 'seed'?

Android One phones with Similar specs to GMG4. Yes.

tom1491 said:
I just want to know if they (i-mobile IQ II, General Mobile 4G, etc) all have the same code name 'seed'?
Click to expand...
Click to collapse
Every single Android One device with a Snapdragon 410 beating inside it is a seed.
Second gen MTK variants were originally named as 'sprout' by LAVA and INFINIX, but I said, **** you, and changed them to 'seedmtk' Official TWRP is now available for both variants, with CM13 already available for Snapdragon ones and on the way for MTK.

MSF Jarvis said:
Every single Android One device with a Snapdragon 410 beating inside it is a seed.
Second gen MTK variants were originally named as 'sprout' by LAVA and INFINIX, but I said, **** you, and changed them to 'seedmtk' Official TWRP is now available for both variants, with CM13 already available for Snapdragon ones and on the way for MTK.
Click to expand...
Click to collapse
Thanks a lot guy!

Enable Galileo use in the USA?

The best I've been able to surmise, is that every model of the X4 has Galileo disabled in the USA. It seems to be a geo-fence lockout, since people have reported that Galileo satellites become usable as they fly over the ocean to Europe. And the opposite occurs when returning to the USA. Motorola does not seem receptive my requests for enabling the feature, even though the FCC made a ruling in December 2018 that Galileo could now be utilized in the USA.
Anyone have any idea where the USA geo-fence for Galileo use is implemented? Would that be hard-wired on the Snapdragon chipset (I'm thinking unlikely), in the radio firmware, or in Android? If in radio or Android, I'm curious if any custom ROMs have this feature enabled?
Thanks for any help.

From another thread on another site, it seems like there is a blacklist setting per GNSS provider (GPS, Glonass, Galileo, Beidou, etc)
Example Link
data/data/com.android.providers.settings/databases/settings.db
It's not clear to me if this needs to be changed prior to ROM compile, or can be changed after the ROM is installed.
Curious if any ROM builders or rooted folks would be willing to test this to see if we can get Galileo enabled on the Moto X4 in the USA?

Can anyone confirm they can track Galileo satellites while in the USA with a rooted ROM? If so, which ROM?
You can use the gpstest app to confirm. Look for the dark blue EU flag.
You can read more in this article written by the app author.

ndoggac,
I have the exact same issue / questions you have. I'm in the US. 2020 model Moto G Power. "Supports" Galileo but none seen. So far my questions on Motorola forum have not been replied to.
Looks like we found the same blacklist/whitelist /geofencing info. It also looks like it might be as simple as a change in value in a system variable.
Hoping someone who routinely hacks on androids can offer how involved making a change like this might be.
Also wondering if anyone in the 48 states has any phone that's using Galileo and or Beidou?
I also found and installed "adb" which might be the right path to making the change, but I'm not wanting to brick my phone by screwing around too much!