Nexus 5 announcement and owners thread

Forums › Android › Nexus 5 announcement and owners thread

1 | ... | 62 | 63 | 64 | 65 | 66 | 67 | 68 | 69 | 70 | 71 | 72 | ... | 87

1873 posts

Uber Geek

Trusted

#950882 12-Dec-2013 11:24

It sits fine, the ring in the middle of the charger is rubbery so it holds the phone in place. I prefer the naked look with this phone so don't have a case, i cant imagine it would have any problems holding it with a case.

dolsen

1476 posts

Uber Geek

Trusted

Lifetime subscriber

#950888 12-Dec-2013 11:38

garvani: It sits fine, the ring in the middle of the charger is rubbery so it holds the phone in place. I prefer the naked look with this phone so don't have a case, i cant imagine it would have any problems holding it with a case.

I brought two of those chargers as well. Seems to be very good quality (unlike some other stuff that you can get on that site). I expect they were built on the exact same line using the same components as the official N4 charger. It holds my wife's N4 in a case quite well so would expect the same with the N5. She did put the charger upside down and it did pick up a lot of dust, but, a quick wipe with a warm cloth removed the dust and restored the stickiness.

lazyinnet

22 posts

Geek

#950897 12-Dec-2013 12:04

garvani: It sits fine, the ring in the middle of the charger is rubbery so it holds the phone in place. I prefer the naked look with this phone so don't have a case, i cant imagine it would have any problems holding it with a case.

Looks awesome. Can you post a photo showing the distance between the bottom of the phone and the table? Thanks

mwilcox

119 posts

Master Geek

#950930 12-Dec-2013 12:21

dafman: My two LG WCP-300 wireless chargers have arrived from Amazon. Cost was approx $70 each.

Look great - small round footprint (about 70 mm). The top of the charger is made from similar material to the back of the N5 so the phone sits firmly on top. Flashing light indicates charging. Works a dream, recommended!

Got my official N5 wireless charger from amazon this morning. Works fine with a 2A wall adapter and the included USB cable, but not with any other USB cable or underpowered adapters. Not that big of a deal, but the included USB cable is quite short. The magnets are really strong.

toii

160 posts

Master Geek

#950943 12-Dec-2013 12:59

Are there any other Nexus 5 owners on Telecom XT network that are having similar problem to me with MMS?

I am getting force close of Hangouts with the exception shown below. It appears to be when it is trying to download an MMS that someone else has sent to me (it has happened with more than one other person trying to send to me). I am able to send and receive an MMS to myself OK.

On a previous phone (Galaxy S2) I used to get the same 'value length > LENGTH_QUOTE!' exception when I was running an AOSP-based firmware and receiving an MMS. This persisted for months then magically resolved itself. Running the standard Samsung firmware this problem didn't occur. 3rd party messaging apps didnt have this problem on that device.

12-12 11:28:33.841 E/Babel   (4327): java.lang.RuntimeException: Value length > LENGTH_QUOTE!
12-12 11:28:33.841 E/Babel   (4327):     at ij.d(SourceFile:1012)
12-12 11:28:33.841 E/Babel   (4327):     at ij.a(SourceFile:1673)
12-12 11:28:33.841 E/Babel   (4327):     at ij.b(SourceFile:875)
12-12 11:28:33.841 E/Babel   (4327):     at ij.DM(SourceFile:131)
12-12 11:28:33.841 E/Babel   (4327):     at com.google.android.apps.babel.

sms.MmsSendReceiveManager.a(SourceFile:439)
12-12 11:28:33.841 E/Babel   (4327):     at com.google.android.apps.babel.sms.MmsSendReceiveManager.a(SourceFile:373)
12-12 11:28:33.841 E/Babel   (4327):     at com.google.android.apps.babel.sms.p.a(SourceFile:367)
12-12 11:28:33.841 E/Babel   (4327):     at com.google.android.apps.babel.protocol.ServerRequest$RetrieveMmsRequest.execute(SourceFile:1487)

JamesL

956 posts

Ultimate Geek
Inactive user

#950948 12-Dec-2013 13:19

MMS on stock android has never worked on Telecom

The latest hangouts was supposed to fix MMS issues but it hasn't

toii

160 posts

Master Geek

#950953 12-Dec-2013 13:30

JamesL: MMS on stock android has never worked on Telecom

The latest hangouts was supposed to fix MMS issues but it hasn't

I just tried using the 8SMS app as default messaging app instead of Hangouts. I got someone near me to send 2 x MMS and they were both received ok. I made Hangouts my default messaging app again and then got them to send me another MMS and it caused Hangouts to force close with the same error in the log. Hmmmm.

I recall seeing something a while back about the original issue being something to do with the device identifier (or something like that) on the device not being understood by Telecom network with AOSP messaging app. This identifier was different on the device if using native firmware compared to AOSP firmware. I cant find where I read that any more. I have posted on Google Hangout forums about the error. Even if it cant receive the MMS it should not have an uncaught exception making the app force close.

Sharesies

Trade NZ and US shares and funds with Sharesies (affiliate link).

dafman

3928 posts

Uber Geek

Trusted

#950970 12-Dec-2013 14:09

toii: Are there any other Nexus 5 owners on Telecom XT network that are having similar problem to me with MMS?

I am getting force close of Hangouts with the exception shown below. It appears to be when it is trying to download an MMS that someone else has sent to me (it has happened with more than one other person trying to send to me). I am able to send and receive an MMS to myself OK.

On a previous phone (Galaxy S2) I used to get the same 'value length > LENGTH_QUOTE!' exception when I was running an AOSP-based firmware and receiving an MMS. This persisted for months then magically resolved itself. Running the standard Samsung firmware this problem didn't occur. 3rd party messaging apps didnt have this problem on that device.

12-12 11:28:33.841 E/Babel   (4327): java.lang.RuntimeException: Value length > LENGTH_QUOTE!
12-12 11:28:33.841 E/Babel   (4327):     at ij.d(SourceFile:1012)
12-12 11:28:33.841 E/Babel   (4327):     at ij.a(SourceFile:1673)
12-12 11:28:33.841 E/Babel   (4327):     at ij.b(SourceFile:875)
12-12 11:28:33.841 E/Babel   (4327):     at ij.DM(SourceFile:131)
12-12 11:28:33.841 E/Babel   (4327):     at com.google.android.apps.babel. sms.MmsSendReceiveManager.a(SourceFile:439)
12-12 11:28:33.841 E/Babel   (4327):     at com.google.android.apps.babel.sms.MmsSendReceiveManager.a(SourceFile:373)
12-12 11:28:33.841 E/Babel   (4327):     at com.google.android.apps.babel.sms.p.a(SourceFile:367)
12-12 11:28:33.841 E/Babel   (4327):     at com.google.android.apps.babel.protocol.ServerRequest$RetrieveMmsRequest.execute(SourceFile:1487)

Check that Hangouts doesn't need updating. Mine showed an update last night, and the upgrade notes said something about fixing 4.4 crashes for MMS (or something very similar to that effect).

dafman

3928 posts

Uber Geek

Trusted

#950971 12-Dec-2013 14:11

mwilcox:
dafman: My two LG WCP-300 wireless chargers have arrived from Amazon. Cost was approx $70 each.

Look great - small round footprint (about 70 mm). The top of the charger is made from similar material to the back of the N5 so the phone sits firmly on top. Flashing light indicates charging. Works a dream, recommended!

Got my official N5 wireless charger from amazon this morning. Works fine with a 2A wall adapter and the included USB cable, but not with any other USB cable or underpowered adapters. Not that big of a deal, but the included USB cable is quite short. The magnets are really strong.

I just plugged the LG WCP-300 chargers directly into my existing micro-usb phone chargers (AC powered) and they both work fine. I have kept the supplied USB cables as spares.

JamesL

956 posts

Ultimate Geek
Inactive user

#950973 12-Dec-2013 14:20

toii:
JamesL: MMS on stock android has never worked on Telecom

The latest hangouts was supposed to fix MMS issues but it hasn't

I just tried using the 8SMS app as default messaging app instead of Hangouts. I got someone near me to send 2 x MMS and they were both received ok. I made Hangouts my default messaging app again and then got them to send me another MMS and it caused Hangouts to force close with the same error in the log. Hmmmm.

I recall seeing something a while back about the original issue being something to do with the device identifier (or something like that) on the device not being understood by Telecom network with AOSP messaging app. This identifier was different on the device if using native firmware compared to AOSP firmware. I cant find where I read that any more. I have posted on Google Hangout forums about the error. Even if it cant receive the MMS it should not have an uncaught exception making the app force close.

Correct, third party SMS/MMS apps seem to handle MMS whereas the stock messaging/hangouts doesn't

The reasoning is in this thread http://www.geekzone.co.nz/forums.asp?forumid=39&topicid=119554

toii

160 posts

Master Geek

#951017 12-Dec-2013 15:24

Correct, third party SMS/MMS apps seem to handle MMS whereas the stock messaging/hangouts doesn't

The reasoning is in this thread http://www.geekzone.co.nz/forums.asp?forumid=39&topicid=119554

That was the info I had seen earlier that I couldnt find again. Interestinlg the 8SMS app that is working is basically the stock MMS app from 4.3

old3eyes

9120 posts

Uber Geek

Subscriber

#951021 12-Dec-2013 15:28

JamesL: MMS on stock android has never worked on Telecom

The latest hangouts was supposed to fix MMS issues but it hasn't

Thanx for that. I got the update today but didn't get around to trying it out. Thanx for the update..

Regards,

Old3eyes

stevenz

2802 posts

Uber Geek

#951028 12-Dec-2013 15:35

MMS on Telecom was an issue way back when XT first launched - Is this Telecom's fault or Google's?

Very tempted to get a Nexus 5 just so I don't have to wait in potential futility for Samsung to release updates. Both the G2 and N5 have their ups & downs though.

@KnightNZ

JamesL

956 posts

Ultimate Geek
Inactive user

#951221 12-Dec-2013 20:47

Still no 4.4.2 update, mate who bought his N5 at the same time I got mine from 2degs got it today.

FML, always last to get it :(

garvani

1873 posts

Uber Geek

Trusted

#951274 12-Dec-2013 21:49

Got my N5 for about 2 1/2 weeks ago from 2degrees, got the update yesterday.

1 | ... | 62 | 63 | 64 | 65 | 66 | 67 | 68 | 69 | 70 | 71 | 72 | ... | 87