Source is www.bitesms.com/cydia/beta4.6

Beta 1, released on 21 December (to configure buttons look in biteSMS, Settings, QC and QR under Buttons. Tip, please note the [Edit] button to allow you to re-order the buttons)

Beta1a, released on 21 December.

Beta2, released on 13 January.

Beta2a, released on 20 January.

Beta3, released on 28 January.

Beta4, released on 4 February.

Beta5, released on 11 February (LAST BETA before PUBLIC)

Here’s the list of items for Release 4.6:

(Beta1) Quick Compose: Set your “Button Display Order”, “Displayed or Not” and “Gesture” preferences for the existing Open, Call and Send buttons. In addition if you prefer say a Close button instead of a Call button, you can customize that as well.

(Beta1) As above for Quick Reply.

(Beta1a) Added support for the Apple “Repeat Alert” feature. So this should just work now.

(Beta2) Templates.

(Beta2) Use of the camera icon to more quickly allow Smileys, Add Contact and Templates to be inserted.

(Beta2) Option to remove the red X circle on Quick Compose and Quick Reply if the Close button is configured as active in the new Quick Compose and Quick Reply “Buttons >” settings.

(Beta2) In settings, against your Mobile Number(s) where it shows the number of credits remaining, we now also show the expiry date (for new credit purchases only, or simply use the “Restore >” option to update this expiry information).

(Beta2) On the biteSMS icon, we now show a failed ! symbol if you have a message that failed to send in the past week.

(Beta2) For an incoming call, Quick Compose will now not appear if you press the volume key (to silence the incoming call) in lock mode.

(Beta2) If your mobile carrier supports sending an SMS to an email address (and it currently works for you in the biteSMS application) this will now also work in Quick Compose as well. So, it’s quick and easy to send yourself an email reminder!

(Beta2) Bug Fixes 1) Repeat alert feature should now only remind if it’s supposed to 2) Reworked QC/QR gesture handling as some users experienced issues accessing cut&paste menu options 3) Fixed QC/QR message count badge in wrong position if less than 3 buttons displayed 4) Edit signature settings text field now correctly re-sizes on orientation change 5) If pressing [Open] from Quick Compose or Quick Reply and passcode is enabled in the biteSMS application, any draft text is now carried across.

(Beta3) Scheduled SMS. This Beta3 WILL NOT SEND SCHEDULED SMS MESSAGES. This is all the nice GUI stuff, the scheduled sending logic will come in Beta4.

(Beta4) Scheduled SMS Logic completed.

(Beta4) Added new setting for Quick Compose and Quick Reply to enable / disable CLOSE action for hardware home button.

(Beta4) If you locked your iPhone while biteSMS was running, then upon unlock it would restart (to ensure conversations were synchronized). This is now fixed, and thus biteSMS no longer restarts itself.

(Beta3) Fix badge issue (hopefully!).

(Beta2a) Bug Fixes, and minor enhancements:

• Pressing camera icon again now closes the biteSMS pop-up sub-menu.
  
• Added a “Delete All” button under the templates settings.
  
• Replaced biteSMS pop-up sub-menu buttons with icons, this gives us more room, and does not cause translation issues.
  
• Changed the camera icon to a + icon.
• Refined the templates list, color and bullet point added
• Bug: The layout of the license cell in the about screen was incorrect if there was an unactivated license, now fixed.
  
• Bug: Using the + widget in compose New Message to choose an international contact (with biteSMS set to “Int’l use biteSMS”) did not switch to the biteSMS network. It’s fixed now.
  
• Bug: Open notes in portrait, switch to landscape mode, open QC, bring up the smiley/template window. This will be behind the keyboard. Now fixed
  
• Bug: http://forums.bitesms.com/forums/6/topics/1864?... (keyboard landscape issue with pop-up keys). Now fixed.
  
• Bug: Quick Reply “Close on Send” ON causing badge issues. NOW FIXED!
  
• Bug: Template settings “Note” text not shifting correctly after delete, or with more than one page need to bounce to see it. Fixed.
  
• Bug: Buttons> settings, once in Edit mode you can drag the buttons below the “Red X (Close)” row which is not related. Fixed.
  
• Bug: In the template screen, swipe a finger on an item to delete it.. after delete or swipe to cancel it should not still be in Edit mode. Fixed
  

(Beta5) list:

• Completely redesigned the privacy settings screen, so privacy outcomes are now much clearer and are also implemented properly.
• Changed smiley as per http://forums.bitesms.com/forums/1/topics/1331?...
• When calling biteSMS to compose a new message (say from Contacts) for a specific recipient, this now works with backgrounder active as well.
• If Mobile Carrier scheduled event, then we now don’t undim the phone (we still undim for sending via biteSMS network).
• Fixed bug: enter smiley in text field, then press schedule icon, shows ascii instead.
• Fixed bug: crash (usually) if scheduling an event for immediate sending.
• Camera button on popup is now disabled once message is too large to fit any more photos (as per Apple native behavior).
• Fixed bug: When there is only one template and swipe to delete, the application crashes.

Looking forward to it!

We aim to please…;-)

This is awesome Martin. Been looking forward to something like this.

Just out of curiosity, what is your plan for scheduled SMS? I have a feeling this one is hard to implement.

It’s coming in Release 4.6, but we have not started on it yet, as we are doing the beta1 above, and then templates for beta2. The User Interface will be the hardest bit, everything else has been worked out.

Wow.. This was quick… 4.6 here we go!!!! xD

weehooo! cant wait!

haha.. bitesms keeps getting better and better.. thanks!!

Thanks for the update Martin. Y’all are amazing! Keep up the good work.

haha you guys are crazy fast. When will it stop

@martin hope you didn’t forget the passcode bug :) thanks

Great surprise:o i never think that qe can have a new version so faster.. And eirh templates and scheduled SMS! Thanks guys!
What Are your ideas to’ implement templates?

Simple, make the UI really nice and easy to use, so that Templates become an everyday event!

yeahhh, you are about to win me over again, although ireal private beta 6 is looking coool too

I would say that maybe you guys should consider fixing most of the current bugs in this release. There are some bugs right now that are pretty annoying.

Things I have noticed:
1. Unread Badge bug. Happens sporadically, but still happens.
2. Bugs with Search feature hanging when viewing a message in old conversations.
3. BiteSMS closes and reopens when phone is unlocked. And sometimes just opens on its own. (I know that it was designed to work like this, but its EXTREMELY annoying, takes too much time, and it doesn’t look right when the app is closing and opening on its own.)
4. Pressing Volume rocker when receiving a call either by accident or to silence the call brings up QC, and you have to close it before you can answer the call which can be a ROYAL pain.
5. When inserting a contact in a new message in the BiteSMS app, and you press the button to bring up the numbers, instead of the numberpad coming up, the whole keyboard shows with the numbers at the top. In the native app, if you were to press the number button, just the number pad would come up. I noticed that when in QC, when you press the number button, the number pad comes up like it should in BiteSMS.
6. The shadow in the text box in QR and QC is not transparent/opaque. So when you scroll in the text box, the shadow goes over the text instead of the text going over the shadow and it looks weird.

Thats all i have really noticed so far.

I agree with hornet, although it’ll stall my feature i want, i’d much rather have a release totally designed on nothing more than bug fixes rather than have new features unless these features are extremely simple and fool proof. Even then few new features should be added. Just my thoughts. Love the previous release, but when are you going to go for nothing but bugs and compatibility with apps (such as backgrounder?)?

@ hornet920
point 2) it’s not a bug.. they dont implement yet…because to load the 200th sms in a conversaton they have to load all the 200 sms like is write the app right now.. so if you find the 1000th sms the app have to load 1000 messages in memory.. so until they rewrite the app to load only 50 messages around the searched sms they can’t enable the view of old messages (is simply disabled because app don’t crash.. but stops) because it will crash.. so very difficult to implememt

Hornet920 hit it spot on!!!

please consider doing a 4.5.5 or something to fix the bugs or things the forums are saying are wrong

Martin – Look at Hornets post where he talks about the slide to unlock causes a reopen. In 4.4 this never happened. A lot of people have brought up that it is annoying.

i think we become too much ossessive with bugs stuff from 4.4… bugs are normal! doesn’t exist an app that haven’t at least 3 or 4 bugs because doesn’t exist the perferct app… none of this bugsmake bite unusable..and all not shows everytime…
come on guys are little things… not so big trouble!

I REALLY LOVE YOU GUYS… REALLY! :D

My issue with Hornets post is he posts like he know the difference between a bug and a feature not yet implemented, so let me make it clear to all.

1. Unread Badge bug. Happens sporadically, but still happens.

I am not convinced this is the case, and get very few emails, and no-body can reproduce it for me. If you can, I am happy to get it fixed.

2. Bugs with Search feature hanging when viewing a message in old conversations.

It’s not a bug, it’s just the phone is very busy and slow rendering all the bubbles. In order to make it go faster we have to rewrite the Apple firmware layer that manages these bubble creations, and that’ll take a long time to do, so for now it’s just slow for old messages that’s all. So, it’s an unimplemented feature to make it go faster, it’s not a bug.

3. BiteSMS closes and reopens when phone is unlocked. And sometimes just opens on its own. (I know that it was designed to work like this, but its EXTREMELY annoying, takes too much time, and it doesn’t look right when the app is closing and opening on its own.)

Discussed at length before, as the Apple firmware is not designed to be aware of sending SMS events inside the SpringBoard, so this is our chosen solution at present, right or wrong it’s our solution to a problem, it’s not a bug.

4. Pressing Volume rocker when receiving a call either by accident or to silence the call brings up QC, and you have to close it before you can answer the call which can be a ROYAL pain.

Get serious, use the Power button, and if you must use the volume button, then until we add this feature, it’ll continue to work like that.

5. When inserting a contact in a new message in the BiteSMS app, and you press the button to bring up the numbers, instead of the numberpad coming up, the whole keyboard shows with the numbers at the top. In the native app, if you were to press the number button, just the number pad would come up. I noticed that when in QC, when you press the number button, the number pad comes up like it should in BiteSMS.

Not aware of this issue, would you mind sending me a screenshot so I can see the issue.

6. The shadow in the text box in QR and QC is not transparent/opaque. So when you scroll in the text box, the shadow goes over the text instead of the text going over the shadow and it looks weird.

Can someone send me a better graphic for this, Sneike?

Sorry, when scheduled SMS?? Is feature that have more votes than other! :)

@simone but is alto the hardest to implement..lately in 4.6 version

Me and my friend both get the badge “bug” as well. I’ll get a list of similarities between our phones so we can get that problem fixed. What info would you like outside of substrates and phone models/versions/jb method?

Edit by Martin, really I just need you to disable all MS add-ons, apart from biteSMS, reboot, and then see if it occurs.

@ray661: a bug couldn’t happen randomly (he can only if is wanted).. there are some differences when the bug shows and the bug don’t…. if you discover when happen they can fix it but if you don’t know and to martin dowsn’t happen this bug (and me neither) they don’t know where look at the problem and fix it is veeeery veery difficult…