There is no code that guarantees the state must go through CONNECTING before being CONNECTED. To avoid potential bugs, call setActive anyway here.
|1 year ago|
|.builds||1 year ago|
|.github||1 year ago|
|art||1 year ago|
|fastlane||1 year ago|
|gradle/wrapper||1 year ago|
|src||1 year ago|
|.gitignore||2 years ago|
|CHANGELOG.md||1 year ago|
|Gemfile||1 year ago|
|Gemfile.lock||1 year ago|
|LICENSE||9 years ago|
|README.md||1 year ago|
|build.gradle||1 year ago|
|cheogram.doap||1 year ago|
|gradle.properties||2 years ago|
|gradlew||1 year ago|
|gradlew.bat||1 year ago|
|proguard-rules.pro||2 years ago|
|screenshots.png||3 years ago|
|screenshots.xcf||3 years ago|
|settings.gradle||3 years ago|
This is a fork of Conversations to implement features of use to the Sopranica project.
The Cheogram Android app allows you to join a worldwide communication network. It especially focuses on features useful to users who want to contact those on other networks as well, such as SMS-enabled phone numbers.
Based on the app Conversations, but with unique features:
- Messages with both media and text, including animated media
- Unobtrusive display of subject lines, where present
- Links to known contacts are shown with their name
- Integrates with gateways' add contact flows
- When using a gateway to the phone network, integrate with the native Android Phone app
- Address book integration
Where to get service:
Cheogram Android requires you have an account with a Jabber service. You can run your own service, or use one provided by someone else, for example: https://snikket.org/hosting/
Art in screenshots is from https://www.peppercarrot.com by David Revoy, CC-BY. Artwork has been modified to crop out sections for avatars and photos, and in some cases add transparency. Use of this artwork does not imply endorsement of this project by the artist.
If you have any questions about this app, or wish to report a bug, please come by the chatroom at xmpp:firstname.lastname@example.org?join or on the web.
If you have code or patches you wish to contribute, the maintainer's preferred mechanism is a git pull request. Push your changes to a git repository somewhere, for example:
git remote rename origin upstream git remote add origin email@example.com:~yourname/cheogram-android git push -u origin master
Then generate the pull request:
git fetch upstream master git request-pull -p upstream/master origin
And copy-paste the result into a plain-text email to: firstname.lastname@example.org
You may alternately use a patch-based approach as described on https://git-send-email.io
Contributions follow an inbound=outbound model -- you (or your employer) keep all copyright on your patches, but agree to license them according to this project's COPYING file.