Jump to content

CellularInfo for iOS: Beta Released (was Coming soon)


nahum365

Recommended Posts

http://support.sprint.com/support/article/FAQs_about_Sprint_WiFi_calling/173e331f-8423-453e-93cb-4688f6a91f67

 

 

Look about half way down the page under the header that says "What phones support Wi-Fi Calling?"

 

Soon™  ????

 

EDIT:  confirmed.  Wifi calling is active on 8.3 and Carrier bundle 19.1.

  • Like 1
Link to comment
Share on other sites

Unfortunately I won't be able to find a new method to get the information until a jailbreak is available. :(

Maybe we'll get lucky and there'll be a jailbreak Soon[emoji769].

 

 

Sent from my iPhone using Tapatalk

  • Like 2
Link to comment
Share on other sites

Wow, so wifi calling, new features, bug fixes, and a potentially way better carrier bundle for band switching--or CellularInfo. This is going to haunt me today. I love the convenience of this app too much to let it go.

 

 

Sent from my iPhone 6+

  • Like 2
Link to comment
Share on other sites

Wow, so wifi calling, new features, bug fixes, and a potentially way better carrier bundle for band switching--or CellularInfo. This is going to haunt me today. I love the convenience of this app too much to let it go.

 

 

Sent from my iPhone 6+

I can't say enough about this app however wifi calling is too tempting. Now all it says is Null.

Link to comment
Share on other sites

Unfortunately I won't be able to find a new method to get the information until a jailbreak is available. :(

Maybe we'll get lucky and there'll be a jailbreak Soon[emoji769].

 

 

Sent from my iPhone using Tapatalk

Out of curiosity, what did they change that broke the app?

Link to comment
Share on other sites

Out of curiosity, what did they change that broke the app?

There was a private method from the CoreTelephony framework I was using, "CTServerConnectionCellMonitorCopyCellInfo()" to be exact.

It's no longer there, probably removed or renamed.

 

 

Sent from my iPhone using Tapatalk

  • Like 1
Link to comment
Share on other sites

There was a private method from the CoreTelephony framework I was using, "CTServerConnectionCellMonitorCopyCellInfo()" to be exact.

It's no longer there, probably removed or renamed.

 

 

Sent from my iPhone using Tapatalk

They heard about what you were doing. Aholes.

  • Like 1
Link to comment
Share on other sites

There was a private method from the CoreTelephony framework I was using, "CTServerConnectionCellMonitorCopyCellInfo()" to be exact.

It's no longer there, probably removed or renamed.

 

 

Sent from my iPhone using Tapatalk

 

I googled that and nothing even came up.  Not sure how you came across that method but I will not update iOS now.  I love your app!

Link to comment
Share on other sites

They heard about what you were doing. Aholes.

It's not the first time Apple has broken one of my projects. Back when Siri first came out, me and a couple other guys decided to port Siri to older devices like the iPhone 4 and iPod touch 4. Others had done it, but they were distributing the Siri files themselves- illegal. So we devised a system that made the device download the Siri files from the iOS 5.0.1 OTA update. After we got everything working, Apple randomly took down that OTA and put it back up a couple hours later with some permissions changed, completely breaking our port. It was such a small change, almost a tiny little "ha screw you guys" from Apple. We fixed it within a week though. Hopefully this is a small change too. Just gotta find it.

 

I googled that and nothing even came up. Not sure how you came across that method but I will not update iOS now. I love your app!

That method wasn't my discovery, if you google a bit more you'd probably find it. I've contacted the guy that originally found it to see if he has an alternative but I'm pretty sure I'm gonna have to find this one myself.

 

 

Sent from my iPhone using Tapatalk

  • Like 2
Link to comment
Share on other sites

I miss CellularInfo more than I thought I would, but love how stable 8.3 is. I was looking around the app store and came across an app called Cellular Info. I haven't spent the 2.99 to see if it really works but I'm curious about it since it claims to show the data we're looking for and is being distributed in the app store. My point for bringing it up is not so much to encourage replacing this app, but more so to explore how it might be working (if even it's just an oversight by the app approval God's).

 

https://appsto.re/us/qMaO4.i

Link to comment
Share on other sites

Nahum, if I were you, I would trademark the name "Cellular Info", because when I look at the release notes for that app, it was updated on April 11th and the update notes say "Application renamed to Cellular Info".

 

-Anthony

  • Like 1
Link to comment
Share on other sites

I miss CellularInfo more than I thought I would, but love how stable 8.3 is. I was looking around the app store and came across an app called Cellular Info. I haven't spent the 2.99 to see if it really works but I'm curious about it since it claims to show the data we're looking for and is being distributed in the app store. My point for bringing it up is not so much to encourage replacing this app, but more so to explore how it might be working (if even it's just an oversight by the app approval God's).

 

https://appsto.re/us/qMaO4.i

All it does is show your carrier and the current connected technology. It also includes the max speed for the connection. No band info, dBm signal strengths, or any other "geeky" info. All the information shown is available in the iOS SDK.

 

Nahum, if I were you, I would trademark the name "Cellular Info", because when I look at the release notes for that app, it was updated on April 11th and the update notes say "Application renamed to Cellular Info".

 

-Anthony

Not sure of the process for that. I'll look into it soon.

For now let's just assume that no App Store apps can reproduce CellularInfo's features.

 

 

Sent from my iPhone using Tapatalk

  • Like 2
Link to comment
Share on other sites

All it does is show your carrier and the current connected technology. It also includes the max speed for the connection. No band info, dBm signal strengths, or any other "geeky" info. All the information shown is available in the iOS SDK.

 

Yeah, I was waiting for a table when I found and typed that out. When I got home to my computer I realized it probably wasn't exactly what I thought. I think the line that got me is Detect LTE operation bands supported by your carrier. When read quickly that's a very sneaky line.

Link to comment
Share on other sites

Not sure of the process for that. I'll look into it soon.

For now let's just assume that no App Store apps can reproduce CellularInfo's features.

 

 

Sent from my iPhone using Tapatalk

Oh I can probably guarantee that no App Store app can reproduce what our CellularInfo can do. I'm just saying you should trademark the name so that people, like this guy on the App Store, can't make money off of it. I'll do some research also about trademarking a name too.

 

-Anthony

Link to comment
Share on other sites

After some further investigation.. I have some bad news. iOS now checks if the app is running as root before returning the information from CoreTelephony. 
The error is:

"Caller not allowed to perform action: TelephonyApiTest.240, action = sandboxed lookup, code = 1: Operation not permitted, uid = 501, euid = 501, gid = 501, egid = 501, asid = 0"

and it returns no info. This kills all hope of a non-jailbreak CellularInfo. If an 8.3 jailbreak is released I'll be sure to release an un-sandboxed version for jailbroken users. 

  • Like 1
Link to comment
Share on other sites

After some further investigation.. I have some bad news. iOS now checks if the app is running as root before returning the information from CoreTelephony. 

The error is:

"Caller not allowed to perform action: TelephonyApiTest.240, action = sandboxed lookup, code = 1: Operation not permitted, uid = 501, euid = 501, gid = 501, egid = 501, asid = 0"

and it returns no info. This kills all hope of a non-jailbreak CellularInfo. If an 8.3 jailbreak is released I'll be sure to release an un-sandboxed version for jailbroken users. 

Well now I have to decide whether to have firm email on my phone or jailbreak and not.

 

This may be the influence of my return to andriod.

  • Like 3
Link to comment
Share on other sites

After some further investigation.. I have some bad news. iOS now checks if the app is running as root before returning the information from CoreTelephony.

The error is:

"Caller not allowed to perform action: TelephonyApiTest.240, action = sandboxed lookup, code = 1: Operation not permitted, uid = 501, euid = 501, gid = 501, egid = 501, asid = 0"
and it returns no info. This kills all hope of a non-jailbreak CellularInfo. If an 8.3 jailbreak is released I'll be sure to release an un-sandboxed version for jailbroken users.
Well a video was released the other day of iOS 8.4 beta being jailbroken, so we may be in luck. We shall see.

 

-Anthony

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

    • Since this is kind of the general chat thread, I have to share this humorous story (at least it is to me): Since around February/March of this year, my S22U has been an absolute pain to charge. USB-C cables would immediately fall out and it progressively got worse and worse until it often took me a number of minutes to get the angle of the cable juuuussst right to get charging to occur at all (not exaggerating). The connection was so weak that even walking heavily could cause the cable to disconnect. I tried cleaning out the port with a stable, a paperclip, etc. Some dust/lint/dirt came out but the connection didn't improve one bit. Needless to say, this was a MONSTER headache and had me hating this phone. I just didn't have the finances right now for a replacement.  Which brings us to the night before last. I am angry as hell because I had spent five minutes trying to get this phone to charge and failed. I am looking in the port and I notice it doesn't look right. The walls look rough and, using a staple, the back and walls feel REALLY rough and very hard. I get some lint/dust out with the staple and it improves charging in the sense I can get it to charge but it doesn't remove any of the hard stuff. It's late and it's charging, so that's enough for now. I decide it's time to see if that hard stuff is part of the connector or not. More aggressive methods are needed! I work in a biochem lab and we have a lot of different sizes of disposable needles available. So, yesterday morning, while in the lab I grab a few different sizes of needles between 26AWG and 31 AWG. When I got home, I got to work and start probing the connector with the 26 AWG and 31 AWG needle. The stuff feels extremely hard, almost like it was part of the connector, but a bit does break off. Under examination of the bit, it's almost sandy with dust/lint embedded in it. It's not part of the connector but instead some sort of rock-hard crap! That's when I remember that I had done some rock hounding at the end of last year and in January. This involved lots of digging in very sandy/dusty soils; soils which bare more than a passing resemblance to the crap in the connector. We have our answer, this debris is basically compacted/cemented rock dust. Over time, moisture in the area combined with the compression from inserting the USB-C connector had turned it into cement. I start going nuts chiseling away at it with the 26 AWG needle. After about 5-10 minutes of constant chiseling and scraping with the 26AWG and 31AWG needles, I see the first signs of metal at the back of the connector. So it is metal around the outsides! Another 5 minutes of work and I have scraped away pretty much all of the crap in the connector. A few finishing passes with the 31AWG needle, a blast of compressed air, and it is time to see if this helped any. I plug my regular USB-C cable and holy crap it clicks into place; it hasn't done that since February! I pick up the phone and the cable has actually latched! The connector works pretty much like it did over a year ago, it's almost like having a brand new phone!
    • That's odd, they are usually almost lock step with TMO. I forgot to mention this also includes the September Security Update.
    • 417.55 MB September security update just downloaded here for S24+ unlocked   Edit:  after Sept security update install, checked and found a 13MB GP System update as well.  Still showing August 1st there however. 
    • T-Mobile is selling the rest of the 3.45GHz spectrum to Columbia Capital.  
    • Still nothing for my AT&T and Visible phones.
  • Recently Browsing

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