Jump to content

Google Nexus 6 by Motorola Users Thread


WiWavelength

Recommended Posts

So from what I understand, band 12 is 700MHz A-Block and is owned by T-Mobile. According to this site (http://www.tmonews.com/700mhz-lte-map/) there hasn't been b12 deployment here in Columbus just yet, and it looks like there's a spectrum issue just to the west of us as well.

 

I did enable it just for giggles and there was indeed no signal to be found.

  • Like 2
Link to comment
Share on other sites

So from what I understand, band 12 is 700MHz A-Block and is owned by T-Mobile. According to this site (http://www.tmonews.com/700mhz-lte-map/) there hasn't been b12 deployment here in Columbus just yet, and it looks like there's a spectrum issue just to the west of us as well.

 

I did enable it just for giggles and there was indeed no signal to be found.

 

Tmo owns some B12 around the country.  USCC and many other regionals also own Band 12 spectrum.  Band 12 is important for Sprint customers for compatibility with RRPP members and future LTE roaming.  It is not important for just T-Mobile.

  • Like 1
Link to comment
Share on other sites

Others have reported to me that when on T-mobile, the Sprint bands appear, also unusable.  My thoughts are this is for the rumored Google MVNO as well.

  • Like 4
Link to comment
Share on other sites

Tmo owns some B12 around the country.  USCC and many other regionals also own Band 12 spectrum.  Band 12 is important for Sprint customers for compatibility with RRPP members and future LTE roaming.  It is not important for just T-Mobile.

 

Thanks for the clarification. I'm certainly not an expert. It'll be interesting to see when exactly Google plans on opening up Nova now that the N6 is ready to go.

  • Like 2
Link to comment
Share on other sites

Help with this error trying to manual flash new 5.1

 

OKAY [  0.855s]

finished. total time: 4.220s

rebooting into bootloader...

OKAY [  0.001s]

finished. total time: 0.001s

target reported max download size of 536870912 bytes

archive does not contain 'boot.sig'

archive does not contain 'recovery.sig'

fastboot(32116,0xa0b921d4) malloc: *** mach_vm_map(size=1779851264) failed (error code=3)

*** error: can't allocate region

*** set a breakpoint in malloc_error_break to debug

failed to allocate 1778070480 bytes

error: update package missing system.img

geologic:shamu-lmy47d adamjsimon$ 

OKAY [  0.855s]

finished. total time: 4.220s

rebooting into bootloader...

OKAY [  0.001s]

finished. total time: 0.001s

target reported max download size of 536870912 bytes

archive does not contain 'boot.sig'

archive does not contain 'recovery.sig'

fastboot(32116,0xa0b921d4) malloc: *** mach_vm_map(size=1779851264) failed (error code=3)

*** error: can't allocate region

*** set a breakpoint in malloc_error_break to debug

failed to allocate 1778070480 bytes

error: update package missing system.img

geologic:shamu-lmy47d adamjsimon$ 

Link to comment
Share on other sites

Ambient display broken? Now when i pick up my device the screen will NOT turn on. the setting is turned on...

After side loading I had the same issue. Untoggling and retoggling seemed to fix it.

Link to comment
Share on other sites

So is this the phone equivalent of a 72 oz steak to get now that the engineering screen is back

 

I fixed your quote for you.

 

AJ

Link to comment
Share on other sites

Ok So long saga of trying to update my Nexus 6.... Heres the details...

 

Just a heads up to anyone with a nexus 6 trying to do manual update
 
WHATEVER you do - DO NOT lock your bootloader without having a fully bootable OS working
 
because you cant unlock without going into the developer options in the OS and enabling OEM unlock capability
 
fastboot will just kick back an error if you try to unlock without turning this option on - even if there isnt any OS installed
 
I almost bricked my Nexus 6 by locking it thinking I could unlock and it would auto wipe and fix the error I was getting... no such luck. Finally thought to use TWRP that was still setup as my recovery to sideload a third party rom (i couldnt get it to sideload stock) and then I could reenable oem unlock in dev options and then reflash everything from fastboot after unlocking
 
I kept getting a optimizing apps boot loop when I first tried manual update but I think I fixed it by issuing fastboot boot boot.img (using the boot.img from the factory image for 5.1)
 
just some info for anyone who might run into this problem
  • Like 1
Link to comment
Share on other sites

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.

Link to comment
Share on other sites

I know its in another language but I am pretty dang excited about the performance improvement im reading about to do with the update from 5.0.1 to 5.1.  Wonder how battery life is in comparison.  Mine was great when I first turned on the phone back in November and has gotten worse over time.  But I contribute that to the apps ive installed more than anything.

 

https://plus.google.com/+androidpit/posts/c9NQwmzzf9U

Link to comment
Share on other sites

Looks like a new build of 5.1 has appeared:

 

http://www.androidpolice.com/2015/03/13/new-android-5-1-build-lmy47e-surfaces-for-nexus-6-probably-wont-go-out-to-existing-devices/

 

According to the article it is probably only going to be present on devices shipped by Verizon, but apparently also includes a new radio. Anyone brave enough to give it a shot?

  • Like 1
Link to comment
Share on other sites

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.

There is no such option under developer options on my nexus 5 on 5.1.

 

Sent from my SM-T217S using Tapatalk

Link to comment
Share on other sites

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.

 

I believe you have to do the fastboot oem unlock *twice* and you can unlock the bootloader without having a bootable os.

 

 

Anybody know how to fix this "couldn't load widget" message at the top of the open apps switcher thing?

 

yes, boot into safe mode 

 

Reboot into safe mode (press power button, long press on "Power off")

 

https://www.google.com/search?q=couldn%27t+load+widget&oq=couldn%27t+load+widget&aqs=chrome..69i57&sourceid=chrome&es_sm=122&ie=UTF-8

 

 

There is no such option under developer options on my nexus 5 on 5.1.

 

Sent from my SM-T217S using Tapatalk

 

you have to tap the build# in the settings > about to enable the developer options.

 

This has been the case for a couple years now, i think since android 4.0..

Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.


  • large.unreadcontent.png.6ef00db54e758d06

  • gallery_1_23_9202.png

  • Posts

    • Since this is kind of the general chat thread, I have to share this humorous story (at least it is to me): Since around February/March of this year, my S22U has been an absolute pain to charge. USB-C cables would immediately fall out and it progressively got worse and worse until it often took me a number of minutes to get the angle of the cable juuuussst right to get charging to occur at all (not exaggerating). The connection was so weak that even walking heavily could cause the cable to disconnect. I tried cleaning out the port with a stable, a paperclip, etc. Some dust/lint/dirt came out but the connection didn't improve one bit. Needless to say, this was a MONSTER headache and had me hating this phone. I just didn't have the finances right now for a replacement.  Which brings us to the night before last. I am angry as hell because I had spent five minutes trying to get this phone to charge and failed. I am looking in the port and I notice it doesn't look right. The walls look rough and, using a staple, the back and walls feel REALLY rough and very hard. I get some lint/dust out with the staple and it improves charging in the sense I can get it to charge but it doesn't remove any of the hard stuff. It's late and it's charging, so that's enough for now. I decide it's time to see if that hard stuff is part of the connector or not. More aggressive methods are needed! I work in a biochem lab and we have a lot of different sizes of disposable needles available. So, yesterday morning, while in the lab I grab a few different sizes of needles between 26AWG and 31 AWG. When I got home, I got to work and start probing the connector with the 26 AWG and 31 AWG needle. The stuff feels extremely hard, almost like it was part of the connector, but a bit does break off. Under examination of the bit, it's almost sandy with dust/lint embedded in it. It's not part of the connector but instead some sort of rock-hard crap! That's when I remember that I had done some rock hounding at the end of last year and in January. This involved lots of digging in very sandy/dusty soils; soils which bare more than a passing resemblance to the crap in the connector. We have our answer, this debris is basically compacted/cemented rock dust. Over time, moisture in the area combined with the compression from inserting the USB-C connector had turned it into cement. I start going nuts chiseling away at it with the 26 AWG needle. After about 5-10 minutes of constant chiseling and scraping with the 26AWG and 31AWG needles, I see the first signs of metal at the back of the connector. So it is metal around the outsides! Another 5 minutes of work and I have scraped away pretty much all of the crap in the connector. A few finishing passes with the 31AWG needle, a blast of compressed air, and it is time to see if this helped any. I plug my regular USB-C cable and holy crap it clicks into place; it hasn't done that since February! I pick up the phone and the cable has actually latched! The connector works pretty much like it did over a year ago, it's almost like having a brand new phone!
    • That's odd, they are usually almost lock step with TMO. I forgot to mention this also includes the September Security Update.
    • 417.55 MB September security update just downloaded here for S24+ unlocked   Edit:  after Sept security update install, checked and found a 13MB GP System update as well.  Still showing August 1st there however. 
    • T-Mobile is selling the rest of the 3.45GHz spectrum to Columbia Capital.  
    • Still nothing for my AT&T and Visible phones.
  • Recently Browsing

    • No registered users viewing this page.
×
×
  • Create New...