travismheim

today i am able to update prl continually instead of getting a message saying there is no new PRL available. strange.

 

going from 1x to eHRPD just once is usually fine. i see the behavior when i go from roaming to sprint several times on a drive, in a short period of time. maybe it has to do with the roaming partner that it is coming off of. I am primarily US Cellular.

That could be it. I go in and out of roaming coverage a fair amount (usually Verizon) each week for work and never experienced anything like that.

 

Sent from my Nexus 5 using Tapatalk

another thing this new update does: it actually checks whether a new PRL is available instead of simply applying the same one regardless.  if no new update, it tells you.  this sort of sucks as, even with this update, if i go to roaming back to sprint back to roaming and to sprint, etc the phone will not connect to eHRPD, just EVDO.  A PRL or profile update was the only way to get back to eHRPD.

I can still update the PRL/Profile as many times as I want back to back. It still applies the same PRL if there isn't a new one. I will also go from roaming 1x and reconnect to Sprint eHRPD without any input on my part, you may have something wrong with your phone.

 

 

Ughh... So they can't make phones rugged enough anymore so you need to get a case... but then they can't make USB ports worth a crap, so after a year or two you end up breaking the USB port... but then they can't make wireless chargers that work through the cases you need to put on...

 

 

UGH....

I have the nexus charger, and two other random brand ones I bought online. I can put a regular cotton sock between the charger and the phone and it will work but that's about it. The case I use is similar to an otterbox defender and it won't work. A thinner case may work with it, but at that point I might as well use the phones bare.

 

Sent from my Nexus 5 using Tapatalk

How successful is wireless charging on a phone that supports it with a rugged case like a Seidio Convert?

It doesn't work at all on my Nexus 5 or LG G2 (VZW) if I have my cases on either phone.

 

Sent from my SM-T217S using Tapatalk

"Usage" is screen on time, and screen off audio streaming. Standby is time off the charger since 100%

 

 

Sent from my iPhone 6+

Thanks. I've been seriously considering taking the plunge and trying out an iPhone for the very first time. Sprint offered me a $50 bill credit if I lease or buy an iPhone 6 with easy pay. Since 5.0 my standby battery life has tanked though usage time has improved. It seems like the iPhone gets significantly better battery life which would be a huge plus.

 

Is the 16GB model adequate? I've been using the 16GB version of the Nexus 5 for a while and never really came close to using all of the memory. My music is usually streamed, or cached for offline use in Spotify and Google Play and pictures stay on the cloud in Photos. By far my biggest storage hog is my nandroid back ups, but I'm not sure if iOS has something similar (or if its really even necessary).

 

Sent from my SM-T217S using Tapatalk

Is there a way to check screen on time in battery stats?

 

Sent from my SM-T217S using Tapatalk

Contract ends in September, but I believe I'm eligible to upgrade now to the iPhone 6/6s.

They recently changed everyone to use 24 month upgrade cycle instead of 20, might want to double check if you are still eligible. A lot of people were upset about it.

 

Sent from my SM-T217S using Tapatalk

In the recent past, Hangouts/Voice integration used a link to send MMS images instead of sending the image directly over the network. Has that been fixed?

Yes.

 

Sent from my SM-T217S using Tapatalk

I'm still going to try it for a while and see how it goes. I do have a question though. Since sms now goes over the data channel only, what happens when you are in a 1x area (native or roaming)? Will the sms just not go through? If so, I guess when I go to an area like that, is it best to disable the integration?

 

Sent from my Note 4.

If you have no data connectivity and choose to send by Google Voice in Hangouts, the message will not send and it will say message not sent, touch to retry. If that happens, you can easily toggle it to send via regular SMS instead.

 

However, data does work while only connected to 1x, roaming data needs to be enabled obviously if you aren't in native coverage. 1x data is slow, but I rarely have trouble sending Google Voice messages while on it (native or roaming).

 

Sent from my Nexus 5 using Tapatalk

 

 

Meanwhile, Google Hangouts on computer requires a bullshit Chrome extension. Hey, I may have Chrome on my desktop, but I would rather continue with Safari for personal use and Firefox for professional use.

 

And then there is the Google Hangouts mobile app. With integration, are SMS being sent/received via actual SMS protocol or via data transport? I have no idea. I want transparency and redundancy. With an SMS app, I use SMS via actual SMS protocol -- no data usage. With Google Voice, I use SMS via data transport. I get to pick and choose between the two based on circumstances. SMS protocol is great while roaming; data transport is great while on Wi-Fi.

 

Google may not want to support another platform via browser. I don't really agree with it, but I understand why they want Hangouts/Google Voice in Chrome and not a competing browser they don't have control over.

 

When you integrate Google Voice with Hangouts, there is a toggle to send via SMS/MMS, via Google Voice, and via Hangouts next to where you enter your message. Each message shows how it was sent (SMS, Google Voice, or Hangouts).

 

 

 

Sent from my Nexus 5 using Tapatalk

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

 

Not my phone, but it's definitely something new. Friend of mine grabbed that screenshot for me.

 

Sent from my Nexus 5 using Tapatalk

 

 

Every single aspect of your phone? Every single photo, setting, folder arrangement, alarms, app data, etc.? Or just the apps that you've downloaded, and the basics like contacts and calandar. And is it every single android on the market? Or just a select few.

 

 

Sent from my iPhone 6+

Since Lollipop, everything can be backed up. Folders, apps, settings, arrangement, WiFi, contacts etc. Photo back up has to be turned on if you've never used the option within the photos app.

 

Every time I reset my Nexus, during the Lollipop set up it asks if I want to restore and which device I want to restore from. I haven't tried restoring my Nexus from my G2 or Tab 3 backups so I'm not sure how well it works between vastly different devices but the option is there. I'm not sure I would even want to try it, since my tablet has a lot of pre installed bloat from Samsung that I don't want on my phone.

 

There's also a an option to copy another device via NFC, but I haven't had the chance to try it since each time I have been re flashing the new system image on the same phone. I realistically won't be able to try it until I upgrade to a new device.

 

Sent from my Nexus 5 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..

I meant there is nothing about enable OEM unlock in developer options on my nexus 5. I wonder if it has to do with the new feature on the nexus 6 that makes it impossible to use a stolen phone, I forgot what they called it.

Right. I should have said that a solution gas been determined, though not necessarily applied yet.

 

I still think the 1900 hardware should be left, especially in rural areas like mine, with very large areas served by individual sites. These are cases where the radios run at their maximum power levels. The more carriers that a radio is required to broadcast, the less power is available to be put into any individual carrier.

 

Throwing all of the CDMA stuff on one radio and the one or eventually two LTE carriers onto another would be a great way to increase LTE 1900 coverage.

Rural areas usually only have one PCS 1X carrier, and one evdo carrier on the CDMA side. I don't really see a need to keep multiple panels and radios up unless its a high capacity site.

 

Sent from my SM-T217S using Tapatalk

I think you answered it in a reply to someone else. I don't want to receive texts in Hangouts on my phone, I want to continue using the texting app. However, I want to be able to send and receive texts on my computer/tablet. It sounds like that is possible?

It sounds like you can disable SMS in hangouts and use your SMS app as normal. You'll probably get duplicates of everything through hangouts via google voice though.

 

Sent from my SM-T217S using Tapatalk

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

Mike, wanted to touch base, I don't see the option to install the new beta.

It came up on google play a few minutes ago for me.

Its an error but nothing that can't be fixed. You just need to flash manually it was a pain for me. I'll look for the instructions when I'm on a PC and post

I can still flash it manually, that's how I got 5.0, 5.0.1, and now 5.1 on it. I was just wondering why I can't use the flash-all batch file since 5.0 was released.

 

 

Are you trying to flash from inside the adb folder? Or just a command prompt opened from the adb folder. Just a command prompt from the folder stopped working for me, but once I started dragging and dropping it in (and removing once I was done) it worked again.

Yeah, I've always unpacked the image to that folder. Just to be clear, you're referring to the platform tools folder right? The cut down version on XDA was labeled adb, but installation from android studio puts it in an obscure location.

 

The only thing I've found searching the issue on my own is several people using an older outdated version of platform tools.

It would be nice to see all of 90, 81, 390 and 86 all LTE for travelers but I guess they dont see it as a priority right now.

I would settle for 90, and 81 at this point. It can be a painful drive when traveling.

Worked for me last night, full version and the stripped one. Give the stripped version on XDA a try. Its quite a bit smaller so it wouldn't take much to give it a shot.

I tried that one from XDA on 5.0.1 and it gave me the same result. I may give it a try a little later but after finishing setting everything back up on 5.1 I would be a little disappointed if it did happen to work and wiped everything again.

Everything still seems to work after flashing 5.1 so far.

I like the feature that emulates the mag strip on cards, allowing for phone payment pretty much anywhere. It's been a while since anyone did anything new regarding mobile payments.

Since 5.0, I haven't been able to use the flash-all batch for flashing the factory images. I get an error every time, using the newest SDK platform-tools (now rev22) in android studio. Any idea why its causing this? I don't mind manually flashing, but it's a little annoying.

 

archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
failed to allocate 1046070000 bytes
error: update package missing system.img
Press any key to exit..

See this excerpt about one of the top features of Android 5.1. There are few things you are misunderstanding about Android 5.1 HD voice and Sprint's HD voice. What Android 5.1 is proposing is that calls between any Android users with devices using Android 5.1 is that their calls will be HD voice and they specifically call out Verizon and Tmobile getting upgrades being able to take advantage of this. Sprint's HD voice is limited to only calls between Sprint customers with HD voice capable devices. That is a huge difference in that the former applies to a larger pool of Android users while the latter applies to only Sprint customers. This has nothing to do with Sprint stripping out the HD voice capability BETWEEN Sprint customers...of course that will remain.

 

My point was why doesn't the article list Sprint as being able to take advantage of Android 5.1's HD voice support especially when its cell towers are able to support HD voice?

 

http://www.androidcentral.com/whats-new-android-51-some-big-and-small-changes-updated-lollipop-release#slide3

 

The HD voice call out for T-Mobile and Verizon is VoLTE using whatever the HD codec is, I can't remember off the top of my head. It doesn't call out Sprint because they don't support VoLTE yet.