Ok, but then biteSMS shouldn’t add the prefix in long messages. So I still think it’s a bug. Hopefully they implement real delivery report soon as this would also solve this problem I think.

its not downloading here – dunno what to do. Source there, all there but 404 error comes all the time. Please anyone could post the deb somewhere

@big_berny naah i think that also for real delivery there’s this problem!

Noticed a small bug when biteSMS is backgrounded and using other apps.

While replying in QR in another app (such as Safari), if you switch back to biteSMS, the preview list of all your texts will show the last received text rather than the last bubble which is the one you sent.

Also noticed another bug that was mentioned above, the SMS sound will sound as if you have a new text or repeat sound when all texts have already been seen.

Hope that makes sense. Was able to reproduce it too.

With Proswitcher and multifl0w out, multitasking on the iPhone has gotten a lot bigger and having biteSMS cooperate would be awesome!

Now that we can have a close button on QC and QR, maybe we can have the ability to hide the red X in the top left.

Hey Martin and Crew!! I just wanted to wish you guys the most AWESOME and WELL DESERVED Holidays you can have!! This new beta is super cool!! Your hard work and effort is appreciated guys!! Take care!!!

@phate89: I’m quite sure that not because it seems to be a problem with the syntax. But there’s another solution to enable delivery reports by setting a flag as the iphone delivery app does. And with my old Sony Ericsson mobile it worked with long messages, too. So there has to be a solution!

@big_berny i’m sure that for the codes it’s not a bite bug because it’s an operator thing.. And Also iphonedelivery developer has this problem..

updating to the newest version

New bug with gestures (?): It takes me several taps to send something now. I hit send by tapping it quickly (the gesture is just tap) and it just depresses the button and then nothing happens. I end up having to click it several times. No good.

@ctny50 – I’ve had similar experiences, especially with the Send Button… I edited my buttons so that Close was on the far left, Call in the Center, and Send on the right…

HTH!

@ ec0yne … funny i have the same exact set up right now. i was using only a 2 button set-up (close on the left, send on the right) when i noticed the bug. i then figured it must be the 2 button layout and switched back to 3 only to find that i still had problems. hmmmm.

I have the problem with my close button when i have the 2 button set up, close left send right. FYI people, we’re not going to get this bug fixed anytime soon :((((

@phate89: I don’t want to offend you but did you read my post? I said there HAS TO BE a solution for delivery reports in long messages as it works on all other handys (with the same operator).

And regarding iphone-delivery-report it’s simply not true:
“So It replaces the bit 5 in the second byte of the PDU payload to request a delivery report. Regarding long SMS, since they are basically concateneted SMS, only the last one is patched. Orignaly the first fragment was patched but the delivery report was receive before the message itself. It was pretty disturbing for some :D” (http://code.google.com/p/iphone-delivery-report…)
So it works with iphone-delivery-report.

for the operator thing or you split the sms and send the first with code and others without works it but it’s not anymore the same message and it’s only the same solution..because it simply add the code before the phone number you send… so like i said (yes i read what you wrote) until they don’t include the reald delivery notification there’s no way to do this..
and for the iphonedeliveryreport is a fix arrived a week ago with last version… i don’t see this last upgrade

Ok, so let’s hope that the implement real delivery notification soon! :)

^I hope that the developers won’t. What for? We’ve got delivery notification on Cydia, working and doing fine. Why do the devs should waste their time to implement into biteSMS thing, which is already out and easy-to-get? Think about it.

Btw. haven’t noticed any bugs so far.

@ptrq so if they implement natively you can know if a Message is delivered directly in bitesms in a eas and immediate way.. You can enable it for a single SMS while you’re writing it In app or in qr/qc easily and you have the message near the icon that tell you is delivered.. In few wirds easier to’ use and more usable

@ptqr: But it’s not nicely implemented as in the native app.

Just have a look at this screen: http://img192.imageshack.us/img192/8541/bitesms…
In the native app it looks much better while in BiteSMS it just adds the sign to the text. So you always have to remove it when forwarding a message for example. And you can’t simply remove the sign form your sent messages.

I think a good solution would be if the BiteSMS-devs would support the iPhone-delivery-reports-app. Because then they don’t need to implement the whole code but it could still look much better. As you can see here ( http://code.google.com/p/iphone-delivery-report… ) the developer has implemented a kind of interface (new fields in database) which makes it very easy to implement iPhone-delivery-reports-support with just a few new code lines.

in quickreply the send button is not working and it does all sorts of funny things wen we click send. it appears again and again after clicking on send once. wats up wid u guys? anyway how to revert back to 4.5 version ?

Buttons work fine on mine… Maybe you changed the button settings?

To revert back to 4.5, just remove the beta repo and reinstall biteSMS..

I am having keyboard alignment issue with QR/QC
I am using iAcces for input (English & Chinese)
but in landscape mode, the letters are mis-aligned
http://img37.imageshack.us/img37/4747/img0439.png
I have reported the issue to iAcces but haven’t got any reply yet
can someone please check which side the problem lies?
This has been happening from biteSMS 4.5 and iAcces 3 (now it’s version 4)

BUG:
I get Safe Mode Crashes when I use QR or QC popups and while I’m using another application too and I try to use the Copy/Paste feature. I get Safe Mode Crashes with or without Action Menu + Action Menu Plus Pack installed.

Happy Holidays to all! ;)

found a new bug…wen u change the buttons on QC n QR n include close instead of open…and u get a QR msg…u have to double click the close button in order to close the sms inspite of the gesture being set to just tap in the QR settings…but however if u click on the sms entry screen in QR and then single tap the close button it works…it seems to be tat u have to click in the sms entry area so tat the keyboard pops out and then only u can close the sms by single tap on the close button. else u ll have to double tap inorder to close the sms without having to pop the keyboard out…

Just reading the first page:

(quotes)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?(/quotes)

I had this as well. I turned off Marked as Read in the Quick Reply menu, resprung my phone, turned on Marked as Read, resprung my phone, and it worked.