Jump to content

adamjamessimon

S4GRU Premier Sponsor
  • Posts

    185
  • Joined

  • Last visited

Posts posted by adamjamessimon

  1. ^the tower was hooked up via microwave backhaul (I could see it from my field work location) so perhaps this microwave infrastructure explains delays in bluegrass cellular allowing LTE roaming... Kentucky is one of the least connected states in terms of fiber and high speed availability so it would not surprise me if bluegrass cellular has a vast number of towers connected via microwave as opposed to hard-line.

     

    Sent from my Nexus 6 using Tapatalk

  2. I just spent two days in middle of nowhere western Kentucky fully roaming on bluegrass cellular with my Nexus 6. I did not see any increase in my roaming usage despite my Nexus 6 indicating it was roaming on bluegrass cellular. I was limited to 3G speed at the time and I was in a location indicated as off network/sprint nationwide (roaming) on the Sprint coverage map. So... Not sure how helpful this is for everyone here but my experience would seem to indicate an agreement where data on bluegrass cellular is treated as native for the purposes of data accounting.

     

    Sent from my Nexus 6 using Tapatalk

  3. I wonder how they'll activate it on the Nexus 6. It seems that certain bands are disabled and enabled based on the SIM that's inserted. For example, a Sprint SIM disables Band 12 and only enables bands 25, 26, and 41. When people try enabling band 12 manually it basically breaks the phone and requires the radio to be reflashed to work again.

     

    Is this something they can push down remotely (ie update the "application" on the UICC to report that it uses additional bands now), or will it require a software update to enable the roaming bands?

     

    Sent from my Nexus 6

    I enabled band 12 without any issues....

     

    Sent from my Nexus 6 using Tapatalk

  4. I'm ready for Appalachain Wireless roaming! At least on BG you are on 3G. AW is only 1x. :-(

     

    Wow. July 2015 eh? That is exciting! Is a lot going to come online then, or is it going to be a carrier here and there through 2015?

     

    Seems like a new phone will be a must that supports 700MHz. The M9 or S6 going to support 700MHz on Sprint LTE roaming?

    Didnt get specifics on rollout. I know the nexus 6 is fully compatible with the roaming offerings.

     

    Sent from my Nexus 6 using Tapatalk

  5. The small carriers have had LTE roaming on sprint for a while. What's holding up Sprint is that a lot of these CCA carriers don't have accessible LTE networks of their own (or are LTEira) so Sprint has nothing to roam on.

    I'm just looking forward to roaming onto bluegrass cellular

     

    Sent from my Nexus 6 using Tapatalk

    • Like 1
  6. Did you play with any of the band priorities or enable/disable any LTE bands? just curious because I had done this with mine and I suspect this may be the cause of the issue. Also when yours does that have you tried a different sim card (Verizon, tmobile, at&t, cricket, etc)? I am going to request a new sim card from Sprint today and see if it helps.

    I haven't tried a different Sim from another carrier but I have played with priorities, scan time, and enabled band 12 without having any issues.

     

    Sent from my Nexus 6 using Tapatalk

  7. I wonder if the google mvno will make all of these data network vs CDMA texting, calling on data vs CDMA, etc confusions and issues go away with a truly seem less experience... Would be nice. Suppose it would take some coding on googles part to determine optimum network transport method at any given moment.

     

    Sent from my Nexus 6 using Tapatalk

  8. I think he means enable usb debugging.

     

    normally you have to enable dev options > usb debugging then approve the device when first connecting via adb.

     

    on a brand new phone, you can boot to bootloader without ever loading the OS, go to fastboot devices (the device won't be authorized), however as long as it shows the device is recognized, you can type fastboot oem unlock, then do it again and it will unlock without having to have previously booted to OS, unlocked dev settings, enabled usb debugging, authorized the device/computer via adb.

     

     

    before I learned this, I used to boot up the phone and *skip* the google login, enable dev, enable usb, authorize ADB, then reboot-bootloader, then finally fastboot oem unlock

    No, I know what I was saying. Try it yourself. Its enabled by default in the developer options when you first enable the Dev options. Go to Dev options, disable enable OEM unlock. Then go to fastboot and try to unlock. I guarantee you won't be able to do it.

     

    Sent from my Nexus 6 using Tapatalk

  9. I REPEAT DO NOT LOCK YOUR BOOTLOADER WITHOUT HAVING A FULLY BOOTABLE ROM INSTALLED THAT INCLUDES THE ABILITY TO MAKE SURE THE "ENABLE OEM UNLOCK" OPTION IN THE DEVELOPER OPTIONS CAN BE TURNED ON. YOU WILL BE THE SADDEST OF PANDAS IF YOU DO WITHOUT HAVING THIS ABILITY. YOU WILL BASICALLY HALF BRICK YOUR DEVICE. THIS GOES FOR ANY DEVICE WITH LOLLIPOP.

×
×
  • Create New...