BEEM - Android XMPP Application: Issueshttp://elyzion.net/http://elyzion.net/themes/beem/favicon/favicon.ico?15180459462013-05-09T09:15:54ZBEEM - Android XMPP Application
Redmine BEEM - Android XMPP - Support #492 (New): I wont to Server path in your applications Beem-0.1.8 http://elyzion.net/issues/4922013-05-09T09:15:54ZAnonymous
<p>Respected sir,<br />I wont to Server path in your applications Beem-0.1.8 in android on code.<br />where code is server in your app.</p> BEEM - Android XMPP - Bug #489 (New): digest-uri wrong when using separate server http://elyzion.net/issues/4892013-03-25T14:50:50ZAnonymous
<p>Hi,</p>
<p>when configuring a separate server for connection, this<br />server IP or domain is used as the digest uri. This is wrong<br />for virtual hosts, which are very common.</p>
<p>Solution:<br />Introduce option to use domain of Jabber-ID as digest uri<br />(even when domain is not fully qualified as without ".com" or so,<br />like "myjabber" or "mygroup".</p>
<p>Example:</p>
<p>Jabber-ID: user@virthost<br />Server: xmpp.veryltd.com</p>
<p>In this case there is a virtual host "virthost" configured in jabber at<br />the server xmpp.veryltd.com. The digest uri therefore should be "virthost" <br />otherwise authentication fails.</p>
<p>Thanks a lot!</p>
<p><strong>What steps will reproduce the problem?</strong><br />1. <br />2. <br />3.</p>
<p><strong>What is the expected output? What do you see instead?</strong></p>
<p><strong>What version of Beem are you using? On what Android version? On what device?</strong></p>
<p>Please provide any additional information below.</p> BEEM - Android XMPP - Bug #488 (New): Voice call not working on different networkhttp://elyzion.net/issues/4882013-03-20T15:56:46ZYakub Moriswalayakubmoriss@gmail.com
<p>Hi Team,</p>
<p>I downloaded the Beem-Jingle project. I tested the voice call with having both the phone on same network(it means eiher both are on same wifi n/w or both are on 3G n/w) it was working perfectly fine. But When I tested with different network(it means one phone on wifi and other on 3G) I can send text message but I am not able to hear the voice in Voice call.</p>
<p>Its not giving me any error or exception in server as well as client side.</p>
<p>Please help if any buddy knows the solution or anything related to this problem.</p>
<p>Thanks,</p>
<p>Yakub Moriswala</p> BEEM - Android XMPP - Feature #486 (New): The New Version is......so far very nice ;-)http://elyzion.net/issues/4862013-03-14T19:10:05ZChris Weiland
<p>hello Frédéric ,</p>
<p>many thank you for the today Upgrade G</p>
<p>it work with my ccc.de Account and is work so far ...very very good.<br />I hope the App is not so a Akku Killer as the Jabiru App ;-)</p>
<p>many many thanks for this G</p>
<p>PS: have the Conection now with scram-sha-1 or have the conection changed ?</p>
<p>best regards<br />Chris</p> BEEM - Android XMPP - Bug #484 (Closed): Unable to authenticate after upgrade to rc2 http://elyzion.net/issues/4842013-03-02T18:43:23ZAnonymous
<p>After installing rc2, I am no longer able to successfully connect to my Openfire 3.8.0 server. My server logs report a buffer underflow, which I believe is during the TLS handshake.</p>
<p>I am using a self-signed cert (which I am prompted to accept, and select "Always") and have "Require SSL/TLS" enabled.</p>
<p>This has been working flawlessly on previous versions. The only thing I did was upgrade Beem.</p>
<p>2013.03.02 12:21:42 org.jivesoftware.openfire.nio.ClientConnectionHandler - [/x.x.x.x:46668] Data Read: org.apache.mina.filter.support.SSLHandler@9c4e62f (HeapBuffer[pos=0 lim=22 cap=64: 17 03 01 00 11 4B 10 D4 FD E6 1A CA 3B 52 B4 DF 2C AF F2 C9 57 C5])<br />2013.03.02 12:21:42 org.jivesoftware.openfire.nio.ClientConnectionHandler - [/x.x.x.x:46668] unwrap()<br />2013.03.02 12:21:42 org.jivesoftware.openfire.nio.ClientConnectionHandler - [/x.x.x.x:46668] inNetBuffer: java.nio.DirectByteBuffer[pos=0 lim=22 cap=16921]<br />2013.03.02 12:21:42 org.jivesoftware.openfire.nio.ClientConnectionHandler - [/x.x.x.x:46668] appBuffer: java.nio.DirectByteBuffer[pos=0 lim=33842 cap=33842]<br />2013.03.02 12:21:42 org.jivesoftware.openfire.nio.ClientConnectionHandler - [/x.x.x.x:46668] Unwrap res:Status = OK HandshakeStatus = NOT_HANDSHAKING<br />bytesConsumed = 22 bytesProduced = 1<br />2013.03.02 12:21:42 org.jivesoftware.openfire.nio.ClientConnectionHandler - [/x.x.x.x:46668] inNetBuffer: java.nio.DirectByteBuffer[pos=22 lim=22 cap=16921]<br />2013.03.02 12:21:42 org.jivesoftware.openfire.nio.ClientConnectionHandler - [/x.x.x.x:46668] appBuffer: java.nio.DirectByteBuffer[pos=1 lim=33842 cap=33842]<br />2013.03.02 12:21:42 org.jivesoftware.openfire.nio.ClientConnectionHandler - [/x.x.x.x:46668] Unwrap res:Status = BUFFER_UNDERFLOW HandshakeStatus = NOT_HANDSHAKING<br />bytesConsumed = 0 bytesProduced = 0<br />2013.03.02 12:21:42 org.jivesoftware.openfire.nio.ClientConnectionHandler - [/x.x.x.x:46668] appBuffer: java.nio.DirectByteBuffer[pos=0 lim=1 cap=33842]<br />2013.03.02 12:21:42 org.jivesoftware.openfire.nio.ClientConnectionHandler - [/x.x.x.x:46668] app data read: HeapBuffer[pos=0 lim=1 cap=1: 20] (20)</p>
<p>Device: Galaxy Nexus<br />Version: 4.2.2<br />Rooted: no</p>
<p>Thanks for looking at this - I use Beem every day!</p>
<p><strong>What steps will reproduce the problem?</strong><br />1. <br />2. <br />3.</p>
<p><strong>What is the expected output? What do you see instead?</strong></p>
<p><strong>What version of Beem are you using? On what Android version? On what device?</strong></p>
<p>Please provide any additional information below.</p>
<p><strong>What steps will reproduce the problem?</strong><br />1. <br />2. <br />3.</p>
<p><strong>What is the expected output? What do you see instead?</strong></p>
<p><strong>What version of Beem are you using? On what Android version? On what device?</strong></p>
<p>Please provide any additional information below.</p> BEEM - Android XMPP - Bug #483 (Closed): unable to install http://elyzion.net/issues/4832013-03-02T14:46:06ZAnonymous
<p>I'm unable to update or reinstall latest version of Beem from Play or Beem-0.1.8_rc1.apk with adb:</p>
<pre>
W/ActivityManager( 388): No content provider found for permission revoke: file:///data/data/com.android.providers.downloads/cache/downloadfile.apk
D/Finsky ( 5642): [1] PackageVerificationReceiver.checkPrerequisites: Skipping verification because own installation
D/Finsky ( 5642): [1] PackageVerificationReceiver.onReceive: Verification requested, id = 7
W/ActivityManager( 388): No content provider found for permission revoke: file:///data/data/com.android.providers.downloads/cache/downloadfile.apk
I/PackageManager( 388): Copying native libraries to /data/app-lib/vmdl-1175151202
I/PackageManager( 388): Running dexopt on: com.beem.project.beem
E/dalvikvm(10097): Bogus handler offset: 0xa
E/dalvikvm(10097): Trouble with item 1896 @ offset 0xa12b4
E/dalvikvm(10097): Swap of section type 2001 failed
E/dalvikvm(10097): ERROR: Byte swap + verify failed
E/dalvikvm(10097): Optimization failed
W/installd( 132): DexInv: --- END '/data/app/com.beem.project.beem-1.apk' --- status=0xff00, process failed
E/installd( 132): dexopt failed on '/data/dalvik-cache/data@app@com.beem.project.beem-1.apk@classes.dex' res = 65280
W/PackageManager( 388): Package couldn't be installed in /data/app/com.beem.project.beem-1.apk
</pre>
<p><strong>What steps will reproduce the problem?</strong><br />1. <br />2. <br />3.</p>
<p><strong>What is the expected output? What do you see instead?</strong></p>
<p><strong>What version of Beem are you using? On what Android version? On what device?</strong></p>
<p>Please provide any additional information below.</p>
<p><strong>What steps will reproduce the problem?</strong><br />1. <br />2. <br />3.</p>
<p><strong>What is the expected output? What do you see instead?</strong></p>
<p><strong>What version of Beem are you using? On what Android version? On what device?</strong></p>
<p>Please provide any additional information below.</p> BEEM - Android XMPP - Pull request #480 (Closed): code cleanuphttp://elyzion.net/issues/4802013-01-20T19:55:26ZJ Pinkava
<p>Only minor changes or cleanups</p>
<p>- update to latest SmileyParser<br />- replace deprecated onStart() with onStartCommand()<br />- remove some unused variables<br />- close some streams (silence some warnings)<br />- fix spelling of Remko Tronçon name (com/isode/stroke/*)</p>
<p><a class="external" href="https://pinky@bitbucket.org/pinky/beem">https://pinky@bitbucket.org/pinky/beem</a></p> BEEM - Android XMPP - Feature #476 (Closed): Add support for SCRAM-SHA-1 SASL Mechanismhttp://elyzion.net/issues/4762013-01-13T23:05:36ZFrédéric Barthéléry
<p>As specified in the <a href="http://tools.ietf.org/html/rfc6120" class="external">rfc6120</a></p>
<pre>
The SCRAM-SHA-1 or SASL-SCRAM-SHA-1-PLUS variants of the SCRAM mechanism
replace the SASL DIGEST-MD5 mechanism as XMPP's mandatory-to-implement
password-based method for authentication only.
</pre> BEEM - Android XMPP - Bug #472 (Assigned): Failed to login - error in SASL authentificationhttp://elyzion.net/issues/4722012-12-30T10:03:31ZAnonymous
<p>I'm unable to login with current hg version (1009:c76a6e4b37cf) of Beem. Login works fine with version 0.1.7 (or hg version up to 988:586e34fc7594) and stops working with 994:87c97dcb7136 (I'm unable to build anything inbetween).</p>
<p>Error is probably caused by invalid SASL response. Bellow are decoded base64 SASL challenge/response messages, the only visible diference is in <i>digest-uri</i> field.</p>
<p>V0.1.7: (works)</p>
<p>username="master_up",realm="njs.netlab.cz",cnonce="...",nc=00000001,qop=auth,digest-uri="xmpp/njs.netlab.cz",response=...,charset=utf-8,nonce="..."</p>
<p>HG version (does not authentificate)</p>
<p>username="master_up",realm="njs.netlab.cz",cnonce="...",nc=00000001,qop=auth,digest-uri="xmpp/lb1-hap.jabbim.cz",response=...,charset=utf-8,nonce="..."</p>
<p>I have no idea where the string 'lb1-hap.jabbim.cz' comes from.</p> BEEM - Android XMPP - Support #469 (Closed): Accept Unknown Certificate?http://elyzion.net/issues/4692012-12-13T18:33:54ZAnonymous
<p>Hello.<br />Please help me.<br />I am using openfire_3_7_1 for XMPP server.<br />But If BEMM Android Client try connect to the Server, raised exception "Accept Unknown Certificate?" - "TrustAnchor for CertPath not found".</p>
<p>Quickly help me.</p> BEEM - Android XMPP - Bug #457 (New): Activity com.beem.project.beem.ui.LoginAnim has leaked Serv...http://elyzion.net/issues/4572012-11-01T03:40:39ZAnonymous
<p>E/ActivityThread(10395): Activity com.android.contacts.vcard.ImportVCardActivity has leaked ServiceConnection com.android.contacts.vcard.ImportVCardActivity$ImportRequestConnection@4110e320 that<br />was originally bound here<br />E/ActivityThread(10395): android.app.ServiceConnectionLeaked: Activity com.android.contacts.vcard.ImportVCardActivity has leaked ServiceConnection com.android.contacts.vcard.ImportVCardActivity$I<br />mportRequestConnection@4110e320 that was originally bound here<br />E/ActivityThread(10395): at android.app.LoadedApk$ServiceDispatcher.<init>(LoadedApk.java:936)<br />E/ActivityThread(10395): at android.app.LoadedApk.getServiceDispatcher(LoadedApk.java:830)<br />E/ActivityThread(10395): at android.app.ContextImpl.bindService(ContextImpl.java:1117)<br />E/ActivityThread(10395): at android.content.ContextWrapper.bindService(ContextWrapper.java:370)<br />E/ActivityThread(10395): at com.android.contacts.vcard.ImportVCardActivity.startVCardService(ImportVCardActivity.java:1042)<br />E/ActivityThread(10395): at com.android.contacts.vcard.ImportVCardActivity.onCreateDialog(ImportVCardActivity.java:1000)<br />E/ActivityThread(10395): at android.app.Activity.createDialog(Activity.java:944)<br />E/ActivityThread(10395): at android.app.Activity.showDialog(Activity.java:2901)<br />E/ActivityThread(10395): at android.app.Activity.showDialog(Activity.java:2860)<br />E/ActivityThread(10395): at com.android.contacts.vcard.ImportVCardActivity$1.run(ImportVCardActivity.java:808)<br />E/ActivityThread(10395): at android.app.Activity.runOnUiThread(Activity.java:4170)<br />E/ActivityThread(10395): at com.android.contacts.vcard.ImportVCardActivity.importVCard(ImportVCardActivity.java:803)<br />E/ActivityThread(10395): at com.android.contacts.vcard.ImportVCardActivity.importVCard(ImportVCardActivity.java:788)<br />E/ActivityThread(10395): at com.android.contacts.vcard.ImportVCardActivity.startImport(ImportVCardActivity.java:932)<br />E/ActivityThread(10395): at com.android.contacts.vcard.ImportVCardActivity.onCreate(ImportVCardActivity.java:903)<br />E/ActivityThread(10395): at android.app.Activity.performCreate(Activity.java:4465)<br />E/ActivityThread(10395): at android.app.Instrumentation.callActivityOnCreate(Instrumentation.java:1049)<br />E/ActivityThread(10395): at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:1920)<br />E/ActivityThread(10395): at android.app.ActivityThread.handleLaunchActivity(ActivityThread.java:1981)<br />E/ActivityThread(10395): at android.app.ActivityThread.access$600(ActivityThread.java:123)<br />E/ActivityThread(10395): at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1147)<br />E/ActivityThread(10395): at android.os.Handler.dispatchMessage(Handler.java:99)<br />E/ActivityThread(10395): at android.os.Looper.loop(Looper.java:137)<br />E/ActivityThread(10395): at android.app.ActivityThread.main(ActivityThread.java:4424)<br />E/ActivityThread(10395): at java.lang.reflect.Method.invokeNative(Native Method)<br />E/ActivityThread(10395): at java.lang.reflect.Method.invoke(Method.java:511)<br />E/ActivityThread(10395): at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:784)<br />E/ActivityThread(10395): at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:551)<br />E/ActivityThread(10395): at dalvik.system.NativeStart.main(Native Method)<br />W/ActivityManager( 199): Unbind failed: could not find connection for android.os.BinderProxy@410d5380</p> BEEM - Android XMPP - Bug #454 (Closed): Cannot authenticate to gmail.comhttp://elyzion.net/issues/4542012-10-19T20:11:52ZAnonymous
<p>The market app has version 0.1.7 and so does the tip of the source tree, but when I build from source code and try to login to my Google account (<a class="email" href="mailto:hacksoft@gmail.com">hacksoft@gmail.com</a>) I cannot and get the following errors in the logcat:</p>
<p>D/AccountConfigureFragment( 7934): create progress dialog<br />D/AccountConfigureFragment( 7934): Xmpp login task<br />D/AccountConfigureFragment( 7934): jid <a class="email" href="mailto:hacksoft@gmail.com">hacksoft@gmail.com</a> server null<br />W/System.err( 7934): java.security.KeyStoreException: java.security.NoSuchAlgorithmException: KeyStore jks implementation not found<br />W/System.err( 7934): at java.security.KeyStore.getInstance(KeyStore.java:119)<br />W/System.err( 7934): at org.jivesoftware.smack.ServerTrustManager.<init>(ServerTrustManager.java:61)<br />W/System.err( 7934): at org.jivesoftware.smack.XMPPConnection.proceedTLSReceived(XMPPConnection.java:826)<br />W/System.err( 7934): at org.jivesoftware.smack.PacketReader.parsePackets(PacketReader.java:267)<br />W/System.err( 7934): at org.jivesoftware.smack.PacketReader.access$000(PacketReader.java:43)<br />W/System.err( 7934): at org.jivesoftware.smack.PacketReader$1.run(PacketReader.java:70)<br />W/System.err( 7934): Caused by: java.security.NoSuchAlgorithmException: KeyStore jks implementation not found<br />W/System.err( 7934): at org.apache.harmony.security.fortress.Engine.notFound(Engine.java:177)<br />W/System.err( 7934): at org.apache.harmony.security.fortress.Engine.getInstance(Engine.java:151)<br />W/System.err( 7934): at java.security.KeyStore.getInstance(KeyStore.java:116)<br />W/System.err( 7934): ... 5 more<br />E/AccountConfigureFragment( 7934): Unable to connect to Xmpp server<br />E/AccountConfigureFragment( 7934): SASL authentication PLAIN failed: invalid-authzid: <br />E/AccountConfigureFragment( 7934): at org.jivesoftware.smack.SASLAuthentication.authenticate(SASLAuthentication.java:337)<br />E/AccountConfigureFragment( 7934): at org.jivesoftware.smack.XMPPConnection.login(XMPPConnection.java:230)<br />E/AccountConfigureFragment( 7934): at org.jivesoftware.smack.Connection.login(Connection.java:344)<br />E/AccountConfigureFragment( 7934): at com.beem.project.beem.ui.wizard.AccountConfigureFragment$ConnectionTestTask.doInBackground(AccountConfigureFragment.java:431)<br />E/AccountConfigureFragment( 7934): at com.beem.project.beem.ui.wizard.AccountConfigureFragment$ConnectionTestTask.doInBackground(AccountConfigureFragment.java:384)<br />E/AccountConfigureFragment( 7934): at android.os.AsyncTask$2.call(AsyncTask.java:287)<br />E/AccountConfigureFragment( 7934): at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:305)<br />E/AccountConfigureFragment( 7934): at java.util.concurrent.FutureTask.run(FutureTask.java:137)<br />E/AccountConfigureFragment( 7934): at android.os.AsyncTask$SerialExecutor$1.run(AsyncTask.java:230)<br />E/AccountConfigureFragment( 7934): at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1076)<br />E/AccountConfigureFragment( 7934): at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:569)<br />E/AccountConfigureFragment( 7934): at java.lang.Thread.run(Thread.java:856)</p> BEEM - Android XMPP - Bug #449 (Closed): Beem Authentication Bughttp://elyzion.net/issues/4492012-08-12T12:39:59ZAnonymous
<p>Hi All,<br />So my JID is either in the form of <a class="email" href="mailto:555@sub.myname.net">555@sub.myname.net</a> or just 555 (I can't tell) and I'm trying to log into host sub.myname.net with a slightly modified xmpp server, but I don't think that's the problem and I can't seem to figure out what's wrong.. Any help/guidance would be apprciated..</p>
<p>When I set the JID to 555 in Beem (with the option to "Use my full JID as username" in either setting), I see a convo with my XMPP server that is like:<br /><pre>
<stream:stream to="555" xmlns="jabber:client" xmlns:stream="http://etherx.jabber.org/streams" version="1.0">
<stream:stream xmlns='jabber:client' xmlns:stream='http://etherx.jabber.org/streams' xml:lang='en' id='0314dcea-1729-4f45-8272-820fb14594f3' from='555' version='1.0'><stream:error><host-unknown xmlns="urn:ietf:params:xml:ns:xmpp-streams"/></stream:error></stream:stream>
<presence id="eU8sz-14" type="unavailable"></presence>
</stream:stream>
</pre></p>
<p>When I set my JID to the form of <a class="email" href="mailto:555@sub.myname.net">555@sub.myname.net</a> with "Use my full JID as username" <strong>off</strong> I see something like:<br /><pre>
<stream:stream xmlns="jabber:client" xmlns:stream="http://etherx.jabber.org/streams" to="sub.myname.net" version="1.0"/>
<stream:stream xmlns='jabber:client' xmlns:stream='http://etherx.jabber.org/streams' xml:lang='en' id='1c2d492b-7c31-42d2-8946-bf268981dbeb' from='sub.myname.net' version='1.0'>
<stream:features>
<mechanisms xmlns="urn:ietf:params:xml:ns:xmpp-sasl">
<mechanism>PLAIN</mechanism>
</mechanisms>
<auth xmlns="urn:ietf:params:xml:ns:xmpp-sasl" mechanism="PLAIN">NTU1NTU1VTlKTnhGb2JCRmp5RW1FSg==</auth>
<failure xmlns="urn:ietf:params:xml:ns:xmpp-sasl"><not-authorized/></failure>
</pre><br />There, "NTU1NTU1VTlKTnhGb2JCRmp5RW1FSg==" is the base64 encoding of "555555U9JNxFobBFjyEmEJ", with 555 being my JID before the @ and "U9JNxFobBFjyEmEJ" being my example password.</p>
<p>When I set my JID to the form of <a class="email" href="mailto:555@sub.myname.net">555@sub.myname.net</a> with "Use my full JID as username" <strong>on</strong> I see something identical to the previous, except the base64 encoding translates to: "<a class="email" href="mailto:555@sub.myname.net">555@sub.myname.net</a><NULL><a class="email" href="mailto:555@sub.myname.net">555@sub.myname.net</a><NULL>U9JNxFobBFjyEmEJ" (WITH delimiters).</p>
<p>Finally, when I use my Desktop PC and Jabber, using all normal settings, I see something like:<br /><pre>
<stream:stream xmlns="jabber:client" xmlns:stream="http://etherx.jabber.org/streams" to="sub.myname.net" version="1.0"/>
<stream:stream xmlns='jabber:client' xmlns:stream='http://etherx.jabber.org/streams' xml:lang='en' id='24672be6-d751-4928-a750-fbc20cce6e5f' from='sub.myname.net' version='1.0'>
<stream:features>
<mechanisms xmlns="urn:ietf:params:xml:ns:xmpp-sasl">
<mechanism>PLAIN</mechanism>
</mechanisms>
</stream:features>
<auth xmlns="urn:ietf:params:xml:ns:xmpp-sasl" xmlns:ga="http://www.google.com/talk/protocol/auth" mechanism="PLAIN" client-uses-full-bind-result="true">NTU1VTlKTnhGb2JCRmp5RW1FSg==</auth>
<success xmlns="urn:ietf:params:xml:ns:xmpp-sasl"/>
</pre></p>
<p>This base64 encoding translates simply into "<NULL>555<NULL>U9JNxFobBFjyEmEJ" with no domain and no duplicated JID. This is the only thing that authenticates successfully against my server.</p>
<p>(Note that I also don't understand how the server is supposed to discern between the end of the JID and the beginning of the password with the auth stanzas from Beem, since they lack the NULL byte delimieters, but maybe I'm missing something..)</p>
<p>Please advise.<br />Thanks!<br />Mike</p>
<p>(Note: I've gone and replaced all usernames, passwords and domains for privacy reasons.)</p>
<p>PS: <br />Looking at RFC 4616 (the spec for PLAIN SASL AUTH), the format of the auth XMPP stanza's base64-encoded contents should be "authzid<NULL>authcid<NULL>password", where the relationship between authzid and authcid are described as follows (sorry if this is remedial.. these are new terms to me):</p>
<pre>
Upon receipt of the message, the server will verify the presented (in the message) authentication identity (authcid) and password (passwd) with the system authentication database, and it will verify that the authentication credentials permit the client to act as the (presented or derived) authorization identity (authzid).
</pre>
<p>Looking at my code, it looks like authzid is disregarded. So it seems this whole problem is fixed by allowing some way for the transmitted base64-encoded string to read "noonecares<NULL>555<NULL>U9JNxFobBFjyEmEJ"</p> BEEM - Android XMPP - Bug #394 (Closed): “Talk” notificationhttp://elyzion.net/issues/3942012-01-23T00:36:37ZAnonymous
<p>I just installed Beem 0.1.7_rc1 from the Market.</p>
<p>When receiving messages, they show up as “Talk” (I guess as in Google Talk?) in the notification tray.<br />I guess they should show up as “Beem”, right?</p>
<p>This is on the Galaxy Nexus, Android 4.0.2.</p> BEEM - Android XMPP - Feature #66 (Closed): Smileyhttp://elyzion.net/issues/662009-03-27T18:25:27ZPhilippe Lagobalrogbarbu@gmail.com
<p>Integration de smiley dans l'IM, je sais pas trop comment faire: parser les messages en matchant des suites de caracteres a l'envoi comme a la reception...?</p>