LG Nexus 4 Owners Thread

Forums › Android › LG Nexus 4 Owners Thread

1 | ... | 50 | 51 | 52 | 53 | 54 | 55 | 56

119 posts

Master Geek

#784614 20-Mar-2013 17:30

shadybrothers: I'm caseless at the moment. feels good in my hand.

Don't drop it :>

d3Xt3r

687 posts

Ultimate Geek

Trusted

#784640 20-Mar-2013 18:10

shadybrothers: I'm caseless at the moment. feels good in my hand.

Not a big fan of cases myself, but after seeing someone or the other break their N4 almost every single day (on G+), I decided to buy androidcentral.com's Lloyd TPU case (with St. Patrick's Day discount!). Since it's TPU, I can easily take it off when I'm using my phone in a safe place (or if I want to show it off). And it still looks cool even with the case on - shows everyone where _my_ loyalties lie. :)

shadybrothers

236 posts

Master Geek

#784788 21-Mar-2013 08:04

d3Xt3r: androidcentral.com's Lloyd TPU case (with St. Patrick's Day discount!)

IMO looks horrible / tacky. My phone looks beautiful ;)

this is a slap in the face!

JamesL

956 posts

Ultimate Geek
Inactive user

#784814 21-Mar-2013 09:30

Is MMS working for others on Telecom, I'm not sure I've actually tried.. but I noticed that when people send me an MMS all I get is a notification in the notification bar saying "Message not downloaded - Touch to review etc"

When I touch the notification it just sends me to an empty new text message screen.

I'm using the default mobile networks that were configured and I can't see what would be wrong with them. I've used these in the past with my SGS2 and could send/receive fine

APN Name: TelecomDefault
APN: wap.telecom.co.nz
Proxy:
Port:
Username:
Password:
Server:
MMSC:
MMS proxy:
MMS port:
MCC:
MNC:
APN type: default,supl

APN Name: TelecomMMS
APN: wap.telecom.co.nz
Proxy:
Port:
Username:
Password:
Server:
MMSC: http://lsmmsc.xtra.co.nz
MMS proxy: 210.55.11.73
MMS port: 8080
MCC: 530
MNC: 05
APN type: mms (type this in lower case)

JamesL

956 posts

Ultimate Geek
Inactive user

#784839 21-Mar-2013 10:33

Ok, an update.

Got a mate with a Nexus 4 and he sent me an MMS which shows up in the notification bar but when you press it it just takes you to a "New Message" screen

Same thing happened when I sent him a MMS message

Telecom or Android issue?

mecow

145 posts

Master Geek

ID Verified

#784842 21-Mar-2013 10:36

JamesL: Ok, an update.

Got a mate with a Nexus 4 and he sent me an MMS which shows up in the notification bar but when you press it it just takes you to a "New Message" screen

Same thing happened when I sent him a MMS message

Telecom or Android issue?

I have the same problem, but I am on Telecom too. Not sure where the problem started. Are you on a custom rom?

NzBeagle

961 posts

Ultimate Geek

Trusted

#784845 21-Mar-2013 10:39

Just tried sending and receiving from my N4, it's on VF, the other party was on Telecom using an s3. Worked fine, even got a preview in the notification tray. Don't know anyone with an N4 on Telecom to try on sorry.

Equinox IT

Cloud spending continues to surge globally, but most organisations haven’t made the changes necessary to maximise the value and cost-efficiency benefits of their cloud investments. Download the whitepaper From Overspend to Advantage now.

JamesL

956 posts

Ultimate Geek
Inactive user

#784850 21-Mar-2013 10:44

Running stock rom, rooted with franco kernel

My mate is completely stock unrooted and we're both on Telecom

Disrespective

1925 posts

Uber Geek

#784890 21-Mar-2013 11:43

Has he sent a MMS before? For whatever reason I won't receive one (after a new rom install) until i've sent one.

Psilan

856 posts

Ultimate Geek

#784895 21-Mar-2013 11:53

Disrespective: Has he sent a MMS before? For whatever reason I won't receive one (after a new rom install) until i've sent one.

This is correct, and is usually the recommendation from VF/TC support.

PS: I hate MMS. So expensive and almost pointless.

Voyager referral - https://refer.voyager.nz/68QKJ8XKK

JamesL

956 posts

Ultimate Geek
Inactive user

#784898 21-Mar-2013 12:00

I've sent multiple before and no he hasn't sent one before

I don't send them regularly but a few contacts send me them of which I get the same issue

JamesL

956 posts

Ultimate Geek
Inactive user

#785743 23-Mar-2013 00:57

Thinking it might be a AOSP stock messaging app + Telecom issue

Browsing the XDA forums I saw someone having issues with a AOSP ROM on a SGS2 getting the same problem.

From logcat:
V/TransactionSettings(25791): APN setting: MMSC: http://lsmmsc.xtra.co.nz looked for: current IS NOT NULL
E/Mms:transaction(25791): Url: http://tnz-retrieve.sun2.lightsurf.net:80/?msgid=000_01551e175d552589_0&userId=3228257
E/Mms:transaction(25791): recvfrom failed: ETIMEDOUT (Connection timed out)
E/RetrieveTransaction(25791): java.io.IOException: recvfrom failed: ETIMEDOUT (Connection timed out)
E/RetrieveTransaction(25791): at com.android.mms.transaction.HttpUtils.handleHttpConnectionException(HttpUtils.java:296)
E/RetrieveTransaction(25791): at com.android.mms.transaction.HttpUtils.httpConnection(HttpUtils.java:280)
E/RetrieveTransaction(25791): at com.android.mms.transaction.Transaction.getPdu(Transaction.java:195)
E/RetrieveTransaction(25791): at com.android.mms.transaction.RetrieveTransaction.run(RetrieveTransaction.java:136)
E/RetrieveTransaction(25791): at java.lang.Thread.run(Thread.java:856)
E/RetrieveTransaction(25791): Caused by: java.net.SocketException: recvfrom failed: ETIMEDOUT (Connection timed out)
E/RetrieveTransaction(25791): at libcore.io.IoBridge.maybeThrowAfterRecvfrom(IoBridge.java:552)
E/RetrieveTransaction(25791): at libcore.io.IoBridge.recvfrom(IoBridge.java:516)
E/RetrieveTransaction(25791): at java.net.PlainSocketImpl.read(PlainSocketImpl.java:488)
E/RetrieveTransaction(25791): at java.net.PlainSocketImpl.access$000(PlainSocketImpl.java:46)
E/RetrieveTransaction(25791): at java.net.PlainSocketImpl$PlainSocketInputStream.read(PlainSocketImpl.java:240)
E/RetrieveTransaction(25791): at org.apache.http.impl.io.AbstractSessionInputBuffer.fillBuffer(AbstractSessionInputBuffer.java:103)
E/RetrieveTransaction(25791): at org.apache.http.impl.io.AbstractSessionInputBuffer.readLine(AbstractSessionInputBuffer.java:191)
E/RetrieveTransaction(25791): at org.apache.http.impl.conn.DefaultResponseParser.parseHead(DefaultResponseParser.java:82)
E/RetrieveTransaction(25791): at org.apache.http.impl.io.AbstractMessageParser.parse(AbstractMessageParser.java:174)
E/RetrieveTransaction(25791): at org.apache.http.impl.AbstractHttpClientConnection.receiveResponseHeader(AbstractHttpClientConnection.java:180)
E/RetrieveTransaction(25791): at org.apache.http.impl.conn.DefaultClientConnection.receiveResponseHeader(DefaultClientConnection.java:235)
E/RetrieveTransaction(25791): at org.apache.http.impl.conn.AbstractClientConnAdapter.receiveResponseHeader(AbstractClientConnAdapter.java:259)
E/RetrieveTransaction(25791): at org.apache.http.protocol.HttpRequestExecutor.doReceiveResponse(HttpRequestExecutor.java:279)
E/RetrieveTransaction(25791): at org.apache.http.protocol.HttpRequestExecutor.execute(HttpRequestExecutor.java:121)
E/RetrieveTransaction(25791): at org.apache.http.impl.client.DefaultRequestDirector.execute(DefaultRequestDirector.java:428)
E/RetrieveTransaction(25791): at org.apache.http.impl.client.AbstractHttpClient.execute(AbstractHttpClient.java:555)
E/RetrieveTransaction(25791): at org.apache.http.impl.client.AbstractHttpClient.execute(AbstractHttpClient.java:509)
E/RetrieveTransaction(25791): at android.net.http.AndroidHttpClient.execute(AndroidHttpClient.java:262)
E/RetrieveTransaction(25791): at com.android.mms.transaction.HttpUtils.httpConnection(HttpUtils.java:202)
E/RetrieveTransaction(25791): ... 3 more
E/RetrieveTransaction(25791): Caused by: libcore.io.ErrnoException: recvfrom failed: ETIMEDOUT (Connection timed out)
E/RetrieveTransaction(25791): at libcore.io.Posix.recvfromBytes(Native Method)
E/RetrieveTransaction(25791): at libcore.io.Posix.recvfrom(Posix.java:136)
E/RetrieveTransaction(25791): at libcore.io.BlockGuardOs.recvfrom(BlockGuardOs.java:164)
E/RetrieveTransaction(25791): at libcore.io.IoBridge.recvfrom(IoBridge.java:513)
E/RetrieveTransaction(25791): ... 20 more
E/RetrieveTransaction(25791): Retrieval failed.
D/ConnectivityService( 530): ConnectivityChange for mobile_mms: DISCONNECTED/DISCONNECTED

V/TransactionSettings(25791): APN setting: MMSC: http://lsmmsc.xtra.co.nz looked for: current IS NOT NULL
E/RetrieveTransaction(25791): java.lang.RuntimeException: Value length > LENGTH_QUOTE!
E/RetrieveTransaction(25791): at com.google.android.mms.pdu.PduParser.parseValueLength(PduParser.java:1011)
E/RetrieveTransaction(25791): at com.google.android.mms.pdu.PduParser.parsePartHeaders(PduParser.java:1668)
E/RetrieveTransaction(25791): at com.google.android.mms.pdu.PduParser.parseParts(PduParser.java:874)
E/RetrieveTransaction(25791): at com.google.android.mms.pdu.PduParser.parse(PduParser.java:130)
E/RetrieveTransaction(25791): at com.android.mms.transaction.RetrieveTransaction.run(RetrieveTransaction.java:139)
E/RetrieveTransaction(25791): at java.lang.Thread.run(Thread.java:856)
E/RetrieveTransaction(25791): Retrieval failed.

NzBeagle

961 posts

Ultimate Geek

Trusted

#785768 23-Mar-2013 08:13

kitinnz:
Kitinnz.... you are the man. I had no idea about the different ampage from the wall plugs. I just used my wall socket from the Nexus 4 and it didn't work and was convinced it was faulty. However after reading your post I have a working Orb again. Who would have thought that that slight diff in amps would have made such a difference.

Thanks heaps for your work on this

Awesome, glad your Orb is up and running! Yip, I had no idea that they output different ampage, I just thought they were all transferable - micro USB was micro USB, end of the story. After I did my trawl online I read through the Instruction Manual that came with the orb... page 4 in a highlighted bolded box "IMPORTANT Use only the power adapter and cable that come with your charger. Using a different power adapter may damage your phone or reduce charging efficiency". Probably should have read the instructions first...