Jump to content

iMessage issues.


Danielj1981

Recommended Posts

What's up guys, the past couple of days I have been having problems with iMessage on my i5. Running software version 6.1.2, with jailbreak.

 

All of my messages were going thru as text instead of iMessages. I went to messaging settings and it said that iMessage was "waiting on activation". I turned iMessage on and off 3 times and it finally starts working again. I wonder if this is jailbreak related or if something funky just started happening with iMessage itself. I haven't had this problem before, and it came out of nowhere on mine and my wife's i5.

 

I don't think it is signal related, because it is doing it on wifi as well. All I know is it is aggrivating!!

 

Daniel

 

 

Sent from my iPhone 5 using Tapatalk

Link to comment
Share on other sites

I turned iMessage off by it is annoying on 3G. Just doesn't work.

I generally don't have an issue at all on 3G here using it. It's just been the past couple of days. It's been "waiting on activation" whatever that means lol. iMessage uses such small amounts of data. Even in slow service areas It usually works well for me :(

 

 

Sent from my iPhone 5 using Tapatalk

Link to comment
Share on other sites

I have the rare problem with iMessage on EVDO, and it works decent on 1x. But picture messaging sure doesn't. And I'm jailbroken on 6.1.2 as well.

 

 

Sent from Josh's iPhone 5 using Tapatalk 2

Link to comment
Share on other sites

Did you turn on two factor authorization maybe?

 

I don't have any issues with iMessage. In fact at my apartment that works and MMS doesn't.

I didn't change anything that I know of. It's weird...because now it has been steady without issue all night last night and so far today. (Scratches head) and I agree, when I'm on wifi iMessage usually works better than SMS and mms. Just the last 3 days have been rough, without a clear reason why. I will keep an eye on it. If It comes back and I figure it out, I will post. Thanks guys.

 

 

Sent from my iPhone 5 using Tapatalk

Link to comment
Share on other sites

Do you have a Mac? Did you install the just-released 10.8.4 ML update? There were some changes made to the OS X client. Sign out of iMessage on all your devices and then sign back in.

 

It's funny how quick people are to blame "the jailbreak". If evasi0n caused an issue with iMessage there would be a huge backlash and it would be all over the tech news sites. If anything, your device may be experiencing a problem with a buggy app or tweak you installed - but it almost certainly has nothing to do with the jailbreak itself.

Link to comment
Share on other sites

Do you have a Mac? Did you install the just-released 10.8.4 ML update? There were some changes made to the OS X client. Sign out of iMessage on all your devices and then sign back in.

 

It's funny how quick people are to blame "the jailbreak". If evasi0n caused an issue with iMessage there would be a huge backlash and it would be all over the tech news sites. If anything, your device may be experiencing a problem with a buggy app or tweak you installed - but it almost certainly has nothing to do with the jailbreak itself.

 

I do have an iMac. It did an update last week. I'm not sure if it had anything to do with it or not. As I never use iMessage on the Mac. I do however use it on the iPad. I did what u recommended and logged out of iMessage and apple altogether and signed back in.

 

On a side note I wasn't blaming evasi0n. I love the jailbreak. I just didn't know what caused the issue(still really don't) and mentioned the jail break because it is an important piece of the puzzle here.

 

 

Sent from my iPhone 5 using Tapatalk

Link to comment
Share on other sites

My wife's 4s was having issues during the same time period and I have her phone on 6.1.2 (not jailbroken). She was having issues even when on wifi; everything was coming through on her iPad though which is 6.1.3. I signed her out of iMessage all together, waited about a half hour then singed back in - seemed to work - But could have just been cooincidental. I'm thinking there was something on Apple's end with 6.1.2 devices?

Link to comment
Share on other sites

So I did some experimenting here....I just logged my iPad 3 (running iOS 6.1.3) back into iMessage to see what would happen.

 

As soon as I went to send an iMessage to my wife from my i5, my iMessage when screwy again. I'm rely starting to wonder if being logged into two iOS devices with different software versions, is the culprit here.

 

Logged iPad back out and iMessage "activation" issue went away again... Hmmmmm

 

 

Sent from my iPhone 5 using Tapatalk

Link to comment
Share on other sites

Could be. I have both an iPad 2 and a iPhone 5 and have no issue with iMessage on them. However, my iMac can't run 10.8 so I don't have the opportunity to use it on my desktop.

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

  • Posts

    • Historically, T-Mobile has been the only carrier contracting with Crown Castle Solutions, at least in Brooklyn. I did a quick count of the ~35 nodes currently marked as "installed" and everything mapped appears to be T-Mobile. However, they have a macro sector pointed directly at this site and seem to continue relying on the older-style DAS nodes. Additionally, there's another Crown Castle Solutions node approved for construction just around the corner, well within range of their macro. I wouldn’t be surprised to see Verizon using a new vendor for their mmWave build, especially since the macro site directly behind this node lacks mmWave/CBRS deployment (limited to LTE plus C-Band). However, opting for a multi-carrier solution here seems unlikely unless another carrier has actually joined the build. This node is equidistant (about five blocks) between two AT&T macro sites, and there are no oDAS nodes deployed nearby. Although I'm not currently mapping AT&T, based on CellMapper, it appears to be right on cell edge for both sites. Regardless, it appears that whoever is deploying is planning for a significant build. There are eight Crown Castle Solutions nodes approved for construction in a 12-block by 2-block area.
    • Starlink (1900mhz) for T-Mobile, AST SpaceMobile (700mhz and 850mhz) for AT&T, GlobalStar (unknown frequency) for Apple, Iridium (unknown frequency) for Samsung, and AST SpaceMobile (850mhz) for Verizon only work on frequency bands the carrier has licensed nationwide.  These systems broadcast and listen on multiple frequencies at the same time in areas much wider than normal cellular market license areas.  They would struggle with only broadcasting certain frequencies only in certain markets so instead they require a nationwide license.  With the antennas that are included on the satellites, they have range of cellular band frequencies they support and can have different frequencies with different providers in each supported country.  The cellular bands in use are typically 5mhz x 5mhz bands (37.5mbps total for the entire cell) or smaller so they do not have a lot of data bandwidth for the satellite band covering a very large plot of land with potentially millions of customers in a single large cellular satellite cell.  I have heard that each of Starlink's cells sharing that bandwidth will cover 75 or more miles. Satellite cellular connectivity will be set to the lowest priority connection just before SOS service on supported mobile devices and is made available nationwide in supported countries.  The mobile device rules pushed by the provider decide when and where the device is allowed to connect to the satellite service and what services can be provided over that connection.  The satellite has a weak receiving antenna and is moving very quickly so any significant obstructions above your mobile device antenna could cause it not to work.  All the cellular satellite services are starting with texting only and some of them like Apple's solution only support a predefined set of text messages.  Eventually it is expected that a limited number of simultaneous voice calls (VoLTE) will run on these per satellite cell.  Any spare data will then be available as an extremely slow LTE data connection as it could potentially be shared by millions of people.  Satellite data from the way these are currently configured will likely never work well enough to use unless you are in a very remote location.
    • T-Mobile owns the PCS G-block across the contiguous U.S. so they can just use that spectrum to broadcast direct to cell. Ideally your phone would only connect to it in areas where there isn't any terrestrial service available.
    • So how does this whole direct to satellite thing fit in with the way it works now? Carriers spend billions for licenses for specific areas. So now T-Mobile can offer service direct to customers without having a Terrestrial license first?
  • Recently Browsing

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