Re: [ROM][WIP] Unofficial CM7 (Gingerbread) - 7/9/2011
The Sprint build will pull binaries from the same location. So unless you overwrite them with Sprint blobs you'll get the same thing, just configured with Sprint branding. If cnd is missing (and yeah, I haven't added that to the repository yet), copy it over from a stock ROM to the indicated vendor path or just comment that line out from the device mk file. Really. Look at device_thunderc.mk. The only conditional bits are where it sets the ERI file, the kernel and modules, the carrier ID, and the google branding. Everything else is shared (whether or not this is a good idea, I dunno).
I use swype, but last I checked the stock keyboard worked fine too with Spanish and US English (as well as it can be expected to work), and I've just ignored the build warnings.
The connection errors are because git is preferring the IPv6 AAAA records to the IPv4 A records. Unless you've got an IPv6 tunnel set up, you're not going to be able to connect to them. It's then going to fall back on the IPv4 A records which will work for you. You can probably configure git to prefer IPv4 by default and thus quash the needless warnings.
The Sprint build will pull binaries from the same location. So unless you overwrite them with Sprint blobs you'll get the same thing, just configured with Sprint branding. If cnd is missing (and yeah, I haven't added that to the repository yet), copy it over from a stock ROM to the indicated vendor path or just comment that line out from the device mk file. Really. Look at device_thunderc.mk. The only conditional bits are where it sets the ERI file, the kernel and modules, the carrier ID, and the google branding. Everything else is shared (whether or not this is a good idea, I dunno).
I use swype, but last I checked the stock keyboard worked fine too with Spanish and US English (as well as it can be expected to work), and I've just ignored the build warnings.
The connection errors are because git is preferring the IPv6 AAAA records to the IPv4 A records. Unless you've got an IPv6 tunnel set up, you're not going to be able to connect to them. It's then going to fall back on the IPv4 A records which will work for you. You can probably configure git to prefer IPv4 by default and thus quash the needless warnings.