Results 1 to 3 of 3
Discuss SMS Changes on 1.1.3 - Why iSMS does not support it yet at the Free Toolchain Software (Cydia App's) - Hackint0sh.org; Well, I finally get some time to investigate the changes of SMS on 1.1.3 firmware. ...
  1. #1
    Advanced Array

    Join Date
    Dec 2007
    Posts
    42
    Post Thanks / Like
    Downloads
    0
    Uploads
    0
    Rep Power
    0

    Thumbs down SMS Changes on 1.1.3 - Why iSMS does not support it yet

    Well, I finally get some time to investigate the changes of SMS on 1.1.3 firmware.

    I used to thought that there are only permission and path issues on that firmware. But after some test, I found I'm wrong. The adjusted iSMS can send out messages, but could NOT modify the database, and also the messages I send in iSMS does not appear in the MobileSMS!

    Then I tried to dig into the db schema and found that there're several new triggers are introduced. In these triggers, a customized sqlite3 function is used. That means, with theses trigger on, we could not modify the data with external tools!

    Now, let us think again, what's new in the 1.1.3 SMS ?
    1) Group Sending Support,
    2)removal of 1000+ message capacity limit.
    Well, In order to support the 2 enhancements, Apple engineers performed some patch on both the database schema and CoreTelephony API to achieve this.

    Changes I found so far:
    a. Introduced several triggers, tables and columns to support the new but simple [GROUP]1---*[Message]1---*[recipients] model. Yes, the model is not so complicate to me, from a java guy's perspective who with ORM idea.
    b. UI data is polluting in the message table, each message record seems now need a height value to be displayed correctly in the apple SMS
    c. CoreTelephony API is changed to need 2 extra paremter to create the Core message object. CT api user now should took the responbility to maintain the message groups...

    Looks like that apple engineers are really lacking of time to think about how to make out a good software product with good design.

    So, my thumb down to the 1.1.3 SMS, it really sucks.


    iSMS update: I have managed to step over almost all of the above pitfalls and only one step from the sucess The only issue to me is the time.....

    Cheers,

    Shawn
    Last edited by acdc; 02-27-2008 at 08:05 PM.



  2. #2
    Senior Professional Array

    Join Date
    Dec 2007
    Posts
    177
    Post Thanks / Like
    Downloads
    0
    Uploads
    0
    Rep Power
    15

    Default

    When you think isms are ready to 1.1.3?

  3. #3
    E0x
    E0x is offline
    Advanced Array

    Join Date
    Oct 2007
    Posts
    35
    Post Thanks / Like
    Downloads
    0
    Uploads
    0
    Rep Power
    0

    Default

    Quote Originally Posted by acdc View Post
    Well, I finally get some time to investigate the changes of SMS on 1.1.3 firmware.

    I used to thought that there are only permission and path issues on that firmware. But after some test, I found I'm wrong. The adjusted iSMS can send out messages, but could NOT modify the database, and also the messages I send in iSMS does not appear in the MobileSMS!

    Then I tried to dig into the db schema and found that there're several new triggers are introduced. In these triggers, a customized sqlite3 function is used. That means, with theses trigger on, we could not modify the data with external tools!

    Now, let us think again, what's new in the 1.1.3 SMS ?
    1) Group Sending Support,
    2)removal of 1000+ message capacity limit.
    Well, In order to support the 2 enhancements, Apple engineers performed some patch on both the database schema and CoreTelephony API to achieve this.

    Changes I found so far:
    a. Introduced several triggers, tables and columns to support the new but simple [GROUP]1---*[Message]1---*[recipients] model. Yes, the model is not so complicate to me, from a java guy's perspective who with ORM idea.
    b. UI data is polluting in the message table, each message record seems now need a height value to be displayed correctly in the apple SMS
    c. CoreTelephony API is changed to need 2 extra paremter to create the Core message object. CT api user now should took the responbility to maintain the message groups...

    Looks like that apple engineers are really lacking of time to think about how to make out a good software product with good design.

    So, my thumb down to the 1.1.3 SMS, it really sucks.


    iSMS update: I have managed to step over almost all of the above pitfalls and only one step from the sucess The only issue to me is the time.....

    Cheers,

    Shawn
    excellent work , keep going

 

 

Similar Threads

  1. iSMS
    By jjesurun in forum Free Toolchain Software (Cydia App's)
    Replies: 9
    Last Post: 11-13-2008, 08:50 PM
  2. iSMS
    By jjesurun in forum Free Toolchain Software (Cydia App's)
    Replies: 1
    Last Post: 11-12-2008, 12:15 AM
  3. [iSMS Webapp (not the native iSMS.app)] Save iPhone's SMS
    By myselft in forum Web Applications
    Replies: 4
    Last Post: 04-08-2008, 07:23 PM
  4. Isms
    By xeronex in forum Free Toolchain Software (Cydia App's)
    Replies: 2
    Last Post: 01-31-2008, 05:35 PM
  5. iSMS question
    By Nuttynutter123 in forum General
    Replies: 3
    Last Post: 01-30-2008, 05:10 PM

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  
Powered by vBulletin®
Copyright © 2014 vBulletin Solutions, Inc. All rights reserved.
Search Engine Friendly URLs by vBSEO
(c) 2006-2012 Hackint0sh.org
All times are GMT +2. The time now is 04:50 PM.
twitter, follow us!