Jump to content

Google Nexus 5 by LG Users Thread!


nexgencpu

Recommended Posts

Screen on time?

Now, it's 1 hour and 37 minutes. But when I got home I had maybe 15 minutes of screen on time, with around 45% battery remaining and massive wake locks from google search.

Link to comment
Share on other sites

Now, it's 1 hour and 37 minutes. But when I got home I had maybe 15 minutes of screen on time, with around 45% battery remaining and massive wake locks from google search.

Strange. Everything looks normal. Try clearing cache for google search
Link to comment
Share on other sites

Clearing the cache and rebooting didn't work. Going to try the .nomedia file in sd card next, this has been driving me nuts. I charged the phone fully, and in 90 minutes on battery with five minutes screen on time it's down to 85% already.

Link to comment
Share on other sites

Clearing the cache and rebooting didn't work. Going to try the .nomedia file in sd card next, this has been driving me nuts. I charged the phone fully, and in 90 minutes on battery with five minutes screen on time it's down to 85% already.

.nomedia won't do anything.  That's for media scanner, which you don't have an issue with.  What is your signal like during that time?

Link to comment
Share on other sites

.nomedia won't do anything.  That's for media scanner, which you don't have an issue with.  What is your signal like during that time?

Around -45 dbm. The phone was sitting only a few feet from my router and airave. If that's not the problem, what is causing my audioin wake locks in google search? In that short time I already had 49 with 15 minutes keep awake time.

Link to comment
Share on other sites

Around -45 dbm. The phone was sitting only a few feet from my router and airave. If that's not the problem, what is causing my audioin wake locks in google search? In that short time I already had 49 with 15 minutes keep awake time.

Do you have "ok google" everywhere enabled? If so, try disabling it.
Link to comment
Share on other sites

Do you have "ok google" everywhere enabled? If so, try disabling it.

Disabling OK google everywhere helped a bit, the audioin wake locks seem to have stopped. Google search still had 2700 wake locks today. 15 hours on battery with 25 minutes screen on time and I'm down to 35% battery. I think I'm just going to wipe data and re flash the factory image, I don't know what else to try at this point.

 

Sent from my Nexus 5 using Tapatalk

Link to comment
Share on other sites

Disabling OK google everywhere helped a bit, the audioin wake locks seem to have stopped. Google search still had 2700 wake locks today. 15 hours on battery with 25 minutes screen on time and I'm down to 35% battery. I think I'm just going to wipe data and re flash the factory image, I don't know what else to try at this point.

 

Sent from my Nexus 5 using Tapatalk

That's really strange. Definitely try the factory image.
Link to comment
Share on other sites

"MMS" will work if you use hangouts messaging rather than SMS. I think I figured out what was causing all the wake locks. I flashed Android L and was still having the problem. I disabled Google now and it went away.

Link to comment
Share on other sites

"MMS" will work if you use hangouts messaging rather than SMS. I think I figured out what was causing all the wake locks. I flashed Android L and was still having the problem. I disabled Google now and it went away.

That's not MMS. Sending pictures over a Hangouts message wouldn't be an issue if everyone used it.

 

Sent from my Nexus 5 using Tapatalk

  • Like 1
Link to comment
Share on other sites

That's not MMS. Sending pictures over a Hangouts message wouldn't be an issue if everyone used it.

 

Sent from my Nexus 5 using Tapatalk

That's why I had it in quotes. You can also manually change APN settings and make it work, I just tested it between my nexus and g2. For whatever reason it needs to be off WiFi though.
Link to comment
Share on other sites

That's why I had it in quotes. You can also manually change APN settings and make it work, I just tested it between my nexus and g2. For whatever reason it needs to be off WiFi though.

Well that's promising at least. I assumed the APN settings within Hangouts and not the engineering screen? Or did you have to do both?

 

Sent from my Nexus 5 using Tapatalk

Link to comment
Share on other sites

Well that's promising at least. I assumed the APN settings within Hangouts and not the engineering screen? Or did you have to do both?

 

Sent from my Nexus 5 using Tapatalk

I changed it in hangouts and it didn't seem to do anything. After changing it in phone settings it worked. I've had my T-Mobile Sim in the phone while I was testing out L, the same APN menu doesn't appear under mobile networks with Sprint. I'm not sure how to make it work with Sprint.
Link to comment
Share on other sites

I changed it in hangouts and it didn't seem to do anything. After changing it in phone settings it worked. I've had my T-Mobile Sim in the phone while I was testing out L, the same APN menu doesn't appear under mobile networks with Sprint. I'm not sure how to make it work with Sprint.

You don't need to change the APN for Sprint. MMS APN is handled by the messaging application. I have read many reports that turning WiFi off allows MMS to go through.
Link to comment
Share on other sites

I was able to get MMS to send on Sprint, but not receive using hangouts by turning off merged conversations. Using a third party app (I tried chomp sms) I was able to get both send/receive to work with WiFi off.

Link to comment
Share on other sites

I was able to get MMS to send on Sprint, but not receive using hangouts by turning off merged conversations. Using a third party app (I tried chomp sms) I was able to get both send/receive to work with WiFi off.

Running L right now,chomp is working with MMS just fine...?
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

  • Similar Content

  • Posts

    • Fury Gran Coupe (My First Car - What a Boat...)
    • Definite usage quirks in hunting down these sites with a rainbow sim in a s24 ultra. Fell into a hole yesterday so sent off to T-Mobile purgatory. Try my various techniques. No Dish. Get within binocular range of former Sprint colocation and can see Dish equipment. Try to manually set network and everybody but no Dish is listed.  Airplane mode, restart, turn on and off sim, still no Dish. Pull upto 200ft from site straight on with antenna.  Still no Dish. Get to manual network hunting again on phone, power off phone for two minutes. Finally see Dish in manual network selection and choose it. Great signal as expected. I still think the 15 minute rule might work but lack patience. (With Sprint years ago, while roaming on AT&T, the phone would check for Sprint about every fifteen minutes. So at highway speed you could get to about the third Sprint site before roaming would end). Using both cellmapper and signalcheck.net maps to hunt down these sites. Cellmapper response is almost immediate these days (was taking weeks many months ago).  Their idea of where a site can be is often many miles apart. Of course not the same dataset. Also different ideas as how to label a site, but sector details can match with enough data (mimo makes this hard with its many sectors). Dish was using county spacing in a flat suburban area, but is now denser in a hilly richer suburban area.  Likely density of customers makes no difference as a poorer urban area with likely more Dish customers still has country spacing of sites.
    • Mike if you need more Dish data, I have been hunting down sites in western Columbus.  So far just n70 and n71 reporting although I CA all three.
    • Good catch! I meant 115932/119932. Edited my original post I've noticed the same thing lately and have just assumed that they're skipping it now because they're finally able to deploy mmWave small cells.
  • Recently Browsing

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