Jump to content

UCFKnight

S4GRU Member
  • Posts

    288
  • Joined

  • Last visited

Everything posted by UCFKnight

  1. don't want it, too big and under the control of a Chinese company, not touching it.
  2. saturday will probably be my last day on campus for a while, as I'm graduating. Gotta be at CFE bright and early at 7:30am, not gonna enjoy that
  3. I went back to KTU84P, the L preview is cool but its too buggy for a daily driver and a lot of the apps don't work yet for it. I know the release was primarily for devs so I can wait for the full Android 4.5-5.0
  4. so I would assume with L on the horizon that all apps currently requiring the use of dalvik will have to switch over to ART now, or support both considering previous handsets that only use dalvik.
  5. I've had a few of the broadcasts appear on the Google Now screen, though they are supposed to appear in Hangouts. I had the Amber alerts turned off because I had it go off once during a conference meeting, scared the bejesus out of everyone. Presidential alerts I think only go off when the country is under attack or there is an immediate national emergency
  6. http://android.clients.google.com/packages/ota/google_hammerhead/c08cce45be6d759d6fd29480f01128b18f7d4a11.signed-hammerhead-KTU84P-from-KTU84M.c08cce45.zip Here is the OTA to KTU84P for those who know how to sideload
  7. think my tower has gone into cardiac arrest. Started getting 1x800 last night and this morning its alternating back and forth between 1x800 and RTT, before losing the connection completely to where I can't call out.
  8. I just went and disabled Band 26 using my MSL code until they fix the issue, stays on Band 25 or Band 41 just fine now
  9. highest I've gotten so far on Spark in my area is 12mbps down, 5 up, which is about on par with what I was getting on Band 25 over here. Don't mind the strength of it though, as long as it works I can't complain
  10. I'd say its pretty unlikely that the deal will go through considering the DOJ and FCC but, maybe there's a slim chance it could still make it through.
  11. Google would not have allowed that, not to mention it would have an effect on the battery.
  12. it shouldn't be hard, I did it last night and it went through fine. 1. Place the update file in the platform tools folder 2. Hook up your phone to the computer and make sure USB debugging is on under developer options 3. Hold Shift and Right Click Platform Tools, opening a command prompt window 4. do adb devices to make sure your phone is connected 5. do the adb reboot bootloader command 6. press volume down on your phone until you get to recovery and press power 7. When it gets to the screen with the robot and the red exclamation sign, hold power and press volume up 8. use volume down and select "apply update from ADB" 9. do adb sideload filename.zip with filename being whatever the name of the update file you give it if you did everything correctly it should install. If not, you did something wrong.
  13. Turned on my phone this morning and got Band 41
  14. make sure USB debugging is selected under developer options if its not showing up with adb devices
  15. just sideloaded the OTA, updating right now
  16. Haven't seen it posted anywhere yet except for a screen shot or two from twitter, but it won't be long
  17. I wonder if they're trying to force Google's hand at updating
  18. Has yet to be posted to the factory images for Developers, Sprint hasn't updated either, so I don't know https://developers.google.com/android/nexus/images#hammerhead
  19. on the .23 radio, only picking up band 25 in the area right now
×
×
  • Create New...