Jump to content

Google Nexus 6 by Motorola Users Thread


WiWavelength

Recommended Posts

You probably have to give the app system permissions with something like this: 

EDIT: the app I linked installs it in a separate directory. You'd have to set the permissions with a terminal if you want it in that priv-app directory.

 

Actually, it looks like you can set the APK's permissions with ES file manager under "properties" after you move it to /priv-app.

Link to comment
Share on other sites

You probably have to give the app system permissions with something like this: 

EDIT: the app I linked installs it in a separate directory. You'd have to set the permissions with a terminal if you want it in that priv-app directory.

 

Actually, it looks like you can set the APK's permissions with ES file manager under "properties" after you move it to /priv-app.

Its telling me it cant mount system partition as read/write. Does this app support 5.x+

  • Like 1
Link to comment
Share on other sites

You probably have to give the app system permissions with something like this: 

EDIT: the app I linked installs it in a separate directory. You'd have to set the permissions with a terminal if you want it in that priv-app directory.

 

Actually, it looks like you can set the APK's permissions with ES file manager under "properties" after you move it to /priv-app.

I got the file in the directory with root explorer, and it looks like all permissions are set.

 

Permissions are set: RWXRWX

  • Like 1
Link to comment
Share on other sites

Nothing happens in the dialer, maybe I can try sideloading the ODEX file as well..

 

https://www.dropbox.com/s/gcil60yefk07ca7/HiddenMenu.odex?dl=0

 

Are you currently using a Sprint SIM?  If not, most other providers' SIMs seem to lock out dialer codes.

 

Regardless, you can skip the dialer code and use a shortcut maker to create an Activity directly to the Debug menu, for example.  I know that I previously posted instructions somewhere here on S4GRU.

 

AJ

Link to comment
Share on other sites

https://www.dropbox.com/s/gcil60yefk07ca7/HiddenMenu.odex?dl=0

 

Are you currently using a Sprint SIM? If not, most other providers' SIMs seem to lock out dialer codes.

 

Regardless, you can skip the dialer code and use a shortcut maker to create an Activity directly to the Debug menu, for example. I know that I previously posted instructions somewhere here on S4GRU.

 

AJ

I am on a sprint sim, I will give this a go and look around for the shortcut instructions.
Link to comment
Share on other sites

I agree that the battery life is great on the N6. And I find that the camera is much better than I expected it to be. It gets as good of a signal as my GS4. I'm amazed to be getting 5+ hours of sot.

 

Sent from my Nexus 6 using Tapatalk

  • Like 1
Link to comment
Share on other sites

As an update to the SMS issues, I've now repeatedly verified that at least in the San Francisco market, Sprint B41 has delayed and duplicate SMS just like B25 and B26. Clear B41 does not have these issues. 

 

My current theory is that sending an SMS for some reason isn't triggering the LTE connection to become active. If LTE is already active then the text usually goes through immediately, regardless of the band. However if the connection is idle (as is usually the case on wifi), then the SMS hangs and may duplicate. If the LTE connection happens to be active when Android attempts to send it again, then it goes through. Otherwise it is delayed for another cycle, which appears to have progressively longer wait times between attempts. It seems like it could be an issue with the Nexus 6's modem and perhaps a power saving feature on Samsung equipment?

 

Since Sprint still doesn't seem to acknowledge that this is a known issue with the Nexus 6, does anyone know the best way to escalate it? Or at least verify that they are taking it seriously? I'm not sure if this is something Sprint can fix on their end, or if Motorola needs to acknowledge it and patch the modem in an OTA? 

Link to comment
Share on other sites

As an update to the SMS issues, I've now repeatedly verified that at least in the San Francisco market, Sprint B41 has delayed and duplicate SMS just like B25 and B26. Clear B41 does not have these issues. 

 

My current theory is that sending an SMS for some reason isn't triggering the LTE connection to become active. If LTE is already active then the text usually goes through immediately, regardless of the band. However if the connection is idle (as is usually the case on wifi), then the SMS hangs and may duplicate. If the LTE connection happens to be active when Android attempts to send it again, then it goes through. Otherwise it is delayed for another cycle, which appears to have progressively longer wait times between attempts. It seems like it could be an issue with the Nexus 6's modem and perhaps a power saving feature on Samsung equipment?

 

Since Sprint still doesn't seem to acknowledge that this is a known issue with the Nexus 6, does anyone know the best way to escalate it? Or at least verify that they are taking it seriously? I'm not sure if this is something Sprint can fix on their end, or if Motorola needs to acknowledge it and patch the modem in an OTA? 

 

will be interesting to see if the 5.1 radio update fixes this which is rumored to be soon...

 

http://www.forbes.com/sites/ewanspence/2014/12/17/android-lollipop-5-1-release/

Link to comment
Share on other sites

So I've been having the SMS duplicate or fail to send issue... It only has happened (that ive noticed) in fort Wayne and Richmond, IN. It didn't happen during the three weeks I spent in Frankfort, KY. I wonder if part of it is related to market hardware or software configurations.

 

Sent from my Nexus 6 using Tapatalk

  • Like 1
Link to comment
Share on other sites

So I've been having the SMS duplicate or fail to send issue... It only has happened (that ive noticed) in fort Wayne and Richmond, IN. It didn't happen during the three weeks I spent in Frankfort, KY. I wonder if part of it is related to market hardware or software configurations.

 

Sent from my Nexus 6 using Tapatalk

 

i think it's a N6 issue.  if you set the radio to 3G only and do an airplane cycle they seem to work everytime.  when you go back to LTE/CDMA and you are on LTE it seems like it screws up more than works...

Link to comment
Share on other sites

i think it's a N6 issue. if you set the radio to 3G only and do an airplane cycle they seem to work everytime. when you go back to LTE/CDMA and you are on LTE it seems like it screws up more than works...

I still believe it's an issue that is a mix between the Nexus 6 radio and Samsung equipment (either hardware or configuration), since it doesn't happen when connected to Clear B41.

 

The previous post says it worked fine in Frankfort, KY on LTE. Does anyone know if that's a Samsung market? What about Fort Wayne, Indiana?

 

Sent from my Nexus 6 using Tapatalk

  • Like 2
Link to comment
Share on other sites

I still believe it's an issue that is a mix between the Nexus 6 radio and Samsung equipment (either hardware or configuration), since it doesn't happen when connected to Clear B41.

 

The previous post says it worked fine in Frankfort, KY on LTE. Does anyone know if that's a Samsung market? What about Fort Wayne, Indiana?

 

Sent from my Nexus 6 using Tapatalk

My thought was Samsung equip. Fort Wayne and Richmond are Samsung. I think Frankfort is ericson.

 

Sent from my Nexus 6 using Tapatalk

  • Like 1
Link to comment
Share on other sites

I still believe it's an issue that is a mix between the Nexus 6 radio and Samsung equipment (either hardware or configuration), since it doesn't happen when connected to Clear B41.

 

The previous post says it worked fine in Frankfort, KY on LTE. Does anyone know if that's a Samsung market? What about Fort Wayne, Indiana?

 

Sent from my Nexus 6 using Tapatalk

Frankfort is Ericsson.

 

29xvoti.jpg

Link to comment
Share on other sites

So at least from my experience it is definitely connected to the hardware in the market. Issues with Samsung... No issues with ericcson.

 

Sent from my Nexus 6 using Tapatalk

I'm pretty sure I had SMS issues during a layover in Washington DC, which is ALU territory it seems. But I was only there for an hour, it was pretty busy, and I only sent a couple texts, so I can't really make a definitive conclusion. Can anyone in ALU territory chime in?

 

If it is indeed Samsung equipment related, does it fall on Sprint to fix this or Motorola?

 

Sent from my Nexus 6 using Tapatalk

Link to comment
Share on other sites

Are these all issues from the Sprint version or from both versions? I've had zero issues and mine is from google play.

 

Sent from my Nexus 6

They should identical. For the record though, I purchased mine directly from Motorola.

 

Sent from my Nexus 6 using Tapatalk

Link to comment
Share on other sites

I'm in SoCal (Alcatel-Lucent market) and I have the duplication problem. Bought my N6 from Sprint.

Ok, so it may be an issue in both Samsung and ALU markets. Can anyone else in an Ericsson market confirm that they do or do not have this issue?

 

Sent from my Nexus 6 using Tapatalk

Link to comment
Share on other sites

Ok, so it may be an issue in both Samsung and ALU markets. Can anyone else in an Ericsson market confirm that they do or do not have this issue?

 

Sent from my Nexus 6 using Tapatalk

 

Not sure if anyone else has noticed this. If you are on LTE and you send a sms and it immediately says "now" for the time stamp then it was sent then it's fine. However, if you send a sms and it says "sending" for longer than it should then it will duplicate to the person you're sending it to.

  • Like 1
Link to comment
Share on other sites

Not sure if anyone else has noticed this. If you are on LTE and you send a sms and it immediately says "now" for the time stamp then it was sent then it's fine. However, if you send a sms and it says "sending" for longer than it should then it will duplicate to the person you're sending it to.

Yeah I mentioned it several posts back. It doesn't always duplicate when it gets stuck like this. At least in Samsung markets, it seems to only duplicate if it changes towers or bands while stuck sending.

 

I've been texting to my Google Voice number to do all my testing. If you have another number you can use you should see if ALU always duplicates or if it's only when there is a handoff.

 

Sent from my Nexus 6 using Tapatalk

Link to comment
Share on other sites

For whatever it is worth, someone at Sprint proactively sent me a message from their forums asking for details about the issue.    It sounds like they have absolutely no idea yet what is causing the problem but are genuinely trying to narrow it down.  

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...