Closed GoogleCodeExporter closed 9 years ago
well. as you cannot write new messages with smsdroid itself, this is rather
useless.
right?
i could implement that in websms.
Original comment by felix.bechstein
on 27 May 2010 at 6:11
Yeah you are correct. WebSMS would be the better app to place it in. Some kind
of
draft Folder.
Thanks for the fast response btw.
Original comment by kai.eil...@gmail.com
on 27 May 2010 at 6:24
in fact it would hit both apps ;)
Original comment by felix.bechstein
on 27 May 2010 at 7:17
Issue 258 has been merged into this issue.
Original comment by felix.bechstein
on 26 Jun 2010 at 9:20
Original comment by felix.bechstein
on 18 Nov 2010 at 7:53
Original comment by felix.bechstein
on 18 Nov 2010 at 8:07
Hi. I see where i can save the draf, great!! Please tell me how to load a save
draft?
Regards jacques
Original comment by jacwm...@gmail.com
on 18 Nov 2010 at 8:26
drafts are saved in internal sms database.
use the stock smsapp to send them or smsdroid for more comfort ;)
for now smsdroid can "forward" them, but i'll change this behavior with next
version, to let you send the drafts directly.
Original comment by felix.bechstein
on 19 Nov 2010 at 5:52
the current development build allows sending drafts:
http://code.google.com/p/websmsdroid/downloads/detail?name=SMSdroid-0.2.4-dev-20
101119.apk
Original comment by felix.bechstein
on 19 Nov 2010 at 6:32
Great! Thanks!!
Regards Jacques
Original comment by jacwm...@gmail.com
on 19 Nov 2010 at 6:40
I went back to smsdroid 0.2.4 because in the answering field did come a text
input field and a send button??
I could not send sms anymore???
I also did go back with websms to 3.2.1 that was my last backup, because i
could not trace why not sending sms anymore?
In 3.3.1 there is not the sms and char counter anymore??
Please can you just check if betamax and if then get the sms couter out and
leave the char counter?
Or will I add this idea in issue 239?
Thanks Regards nice weekend Jacques
ps sms sending works fine again but I don'nt know what causes the problem??
Original comment by jacwm...@gmail.com
on 20 Nov 2010 at 3:26
websms 3.3 had a bug which prevents it from sending messages with a ' in it.
v3.3.1 fixed this.
BUT: without beeing more specific on "can not send" i can do nothing to fix it..
at least send me your logs after sending failed.
and what is the problem with the text field + send button?
just enter text, press send.
Original comment by felix.bechstein
on 21 Nov 2010 at 9:12
Hi, Yesterday When I was upgrading the smsdroid and websms, t-mobile smsserver
(thats on my other phone, where I send the test smsses to) was not working, so
i'm very sorry for this because it was a concurence of conditions that the
problem occured. Now running the new version of websms 3.3.1 with draft saving
and smsdroid 0.2.4 dev version with the possebilety of draft sending and text
send field in the place of answering field, working Great!! Thanks for that and
sorry for the inconvenience!! The counter in websms starts coming in view with
100 chars thats what i also did not noticed.
My conclusion was totally wrong!
Nice weekend further!
regards Jacques
Original comment by jacwm...@gmail.com
on 21 Nov 2010 at 2:44
In HTC Desire HD (Android 2.2.1) somehow it is not possible to find nor send
the draft messages in SMSdroid. They are available in Stock app. A draft saved
with WebSMS can also not be loaded in Stock app. Any clue what goes wrong?
Original comment by alexande...@gmail.com
on 1 Jan 2011 at 3:49
please try this smsdroid build. saving drafts is working for me. they are shown
in stock sms app and smsdroid.
but please be sure to enter a recipient for the message.
Original comment by felix.bechstein
on 2 Jan 2011 at 2:05
Attachments:
When entering a recipient, I now see the drafts that I saved with WebSMS in the
Stock sms app.
However, unforunately also with this build (above) and new v0.5.1 I cannot see
the drafts in SMSdroid.
For the rest I really like the apps + Betamax connection, so I made the
donation. If I could see the drafts as well, it would be perfect!
Original comment by alexande...@gmail.com
on 7 Jan 2011 at 2:31
Original issue reported on code.google.com by
kai.eil...@gmail.com
on 26 May 2010 at 9:04