Android 5.0 Lollipop woes worsen with Nexus text message issues
The Android 5.0 Lollipop update recently started making its way to devices, including some Nexus phones and tablets. However, the upgrade hasn’t all been plain sailing so far, and we’ve already heard of several problems with the update. Now Android 5.0 Lollipop woes worsen with news of Nexus text message issues.
Last week we started hearing of various difficulties with 5.0 Lollipop when some Nexus device users reported WiFi connectivity issues. This was added to later in the week when users of devices running Android 5.0 started to complain about the missing silent mode on their handsets. Also some Nexus 7 (2013) owners reported that they were no longer able to use video playback.
Now a further concern is being reported by some users of the Nexus 4 and Nexus 5 on the AOSP Issue Tracker site. The bug has left some unable to send text messages, but as yet the problem seems to only involve certain carriers, implying that this stems from particular software or equipment that they use. Specific users reported to be affected so far are on Vodafone Netherlands, Mobistar Belgium and other operators, with other regions also affected including India.
Receiving text messages seems to be fine but when sending messages some people are receiving an error code 38. Interestingly Google has acknowledged this bug in response to a tech blog who asked them about it. The site was told that Google knows about the issue and said that it also affects the Nexus 6 that is soon to be released, thereby backing up the theory that the issue revolves around how some carriers are interacting with Lollipop.
We imagine that Google is working hard on a fix for this issue as we speak, so hopefully everything will be ironed out soon. We expect that by the time Android Lollipop reaches other devices (such as the Samsung Galaxy Note 4 and Galaxy S5) the issues reported so far will have been resolved with further updates.
Are you a Nexus 4 or Nexus 5 user with a phone currently running Android 5.0 Lollipop? If so, has your device been affected by this text messaging problem or any other issues? Drop us a comment in the box below.
Source: Tweakers
Via: Phone Arena
Comments
7 thoughts on “Android 5.0 Lollipop woes worsen with Nexus text message issues”
I just received 5.0 upgrd on nex5. phone doesn’t run smoothly like in kitkat, it lags. messaging app doesn’t work, im forced to use hangouts for sms. doesn’t like it so much though. viva from kosovo
I had the 5.0 upgrade on a 2012 Nexus 7. It’s been rendered unusable. Most appsa don’t work at all and those that do are unbearably slow. And I’m not the only one. See the Google forum “It’s become a glorified brick” is one comment amongst many.
Both of my family’s 2012 Nexus 7s are the same way now after the 5.0 update. I don’t know why tech media is putting faith in Google to fix the issues either. 2012 N7s were already rendered difficult to use by the last KitKat updates. Lollipop was supposed to fix all that and instead the problems have been made worse. We’ve pretty much decided to toss out our N7s and switch to non-Google-branded tablets.
I have 5.0 on both my nexus 7 and N10 and found no problems so far. I don’t care for the smaller faint looking type though. Had problem playing video on the 7. Irebooted it and it has been fine since.
Yes effected messaging. Official email not getting received send from touchdown app and default SMS app even not working properly
I’m in the US and on the T-Mobile network. I’ve already experienced two instances where text messages and especially MMS weren’t able to be sent or received. Something in the Lollipop upgrade changed my APN settings and they had to be modified the first time, and then most recently, a T-Mobile rep had me build a completely new APN setting, which resolved my inability to send and receive text and MMS messages. The problem also cut me off completely from all data and internet connection.
Very stressful but T-Mobile came through and got it resolved. I’m looking forward to my OnePlus One phone, which I’ll be getting my hands on in just two more days!
I have Tesco Mobile error 38 in the UK. Seems to only affect people on O2 that I send messages to, SMS just does not send. A real pain in the backside seen as I can’t text my mum, among others.