Update* Jan 3 2012
I now create the user on the server, and retrieve info:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Update* Jan 1 2012
An update from this Project is that I found out that Google doesn't use XMPP for the chatting, but only for authentication. I did some stuff to the Google+ *cough* apk, and saw some interesting code. They have implementations of their project "protobuf", and some private client called "Bunch". Also if you guys don't know yet, Huddle will be available for devices other than Android or iOS through SMS. Google you fail when you know that XMPP already a Group Chat. Oh well, what ever the reasons are the project continues, and will be out as soon as possible.
Initial description* Dec 31 2011
Awhile ago I had posted a thread asking for help and stopped development of this project. I decided to finish this and start all over. I had some help from a another friend coder and RustyGrom as well for his finding of his XMPP string. I'm coding this in C# and I'm writing the client from scratch, no libraries or anything. Here's my current progress and picture of the testing client:
Old thread:http://forum.xda-developers.com/showthread.php?t=1327585
--Simran
I think it's a great idea.
An update from this Project is that I found out that Google doesn't use XMPP for the chatting, but only for authentication. I did some stuff to the Google+ *cough* apk, and saw some interesting code. They have implementations of their project "protobuf", and some private client called "Bunch". Also if you guys don't know yet, Huddle will be available for devices other than Android or iOS through SMS. Google, you fail when you know that XMPP already a Group Chat. Oh well, what ever the reasons are, the project continues, and will be out as soon as possible.
Updated progress as of Jan 3. View OP!
Related
For those of you on Hero ROMs... read this:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
It's great having lots of manufacturer provided applications in the ROM of your mobile device, but what happens if one of them breaks? It's not as easy as just contacting the developer for an updated version is it!
This is exactly the problem being faced by users of 'HTC Peep', the Twitter client on the HTC Hero.
Last night, the unique id number assigned to each Tweet exceeded 4,294,967,295, in an event we covered as 'Twitpocalyse II'. This is the highest number that can be stored in an unsigned 32 bit integer. If the developer of a Twitter client uses this method to store the Tweet ID, then unexpected things will happen. Hence, since this occured, Peep users have been unable to use the application, instead being greeted by the error message above (after which the application either closes or refuses to load new tweets).
We have contacted HTC to ask how long Hero users should expect to wait for a fix, but if you are affected, it might be time to try out Twidroid, Twitterride or perhaps Swift!
UPDATE: HTC have responded to this issue. They have said "Thanks for helping to make us aware of the details of this problem. We have are investigating the issue and are working with Twitter on a solution. We apologize to our users for any inconvenience this has caused."
We'll bring you more information as it comes in.
Source: http://www.downloadsquad.com/2009/09/23/htc-hero-users-hit-by-twitpocalyse-bug/
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Google's Android Market now has a web client. Finally! And guess what else, it's already live. Hit the source link below to get exploring. It's very simple, really, you can browse the entire Market catalog on your desktop or however else you're accessing the web, you can purchase anything that takes your fancy, and then -- via the magic of over-the-air transfers -- it downloads and installs onto your Android handset. A neat My Market Account section will let you nickname your registered devices to make them more recognizable as well.
Google has also just announced that Android will soon support in-app purchases. Widespread developer interest has been cited as the major reason for doing it, so you've got those lovable coders to thank for the oncoming wave of micropayments you'll have to deal with in your Android apps. The in-app purchasing SDK is releasing to devs today and will be "live to users prior to the end of this quarter."
Update: Invalid request. Yep, that's the message we keep getting when we try and download an app. Google promises that it should be working soon...
Update 2: And now it appears to be working!
Link
Just a few days late
Sent from your favorite carrier, black and yellow!
What do you work for Engadget or something? All you're doing is copy/pasting their stuff.
Last week called, it wants it's announcement back.
Hey guys!
Today I'd like to present to you, my first (ever) WPF application!
It's part of Universal Android Toolkit (See my signature), which is still WIP, but I thought I'd present it to you as a stand-a-lone app.
So don't go thinking weirdly if you see it in Universal Android Toolkit, once I've released the newest version (Which is gonna be friggin' sweet).
Anyways, it does what the thread title says. It gets detailed system information from your device.
This information includes, but is not limited to:
Build ID
ROM Name
Build Codename
Build Version
Device Model Number
Device Board
CPU Type
Manufacturer
Dalvik Heap Size
Default Alarm Tone
Default Ringtone
Carrier
GPRS Class
and
Client Base
Of course this isn't everything, but I'd like to keep some stuff until the release of UAT. Ya know, kinda keeping stuff secret (CaptainSparklez' voice)
Now, before loooking at the screenshots, please bear in mind, that this is literally the first WPF (Windows Presentation Foundation) application that I've ever created and released to the public!
So be nice when it comes to the design of things.
I'm a Linux guy, so I kept the close and minimize buttons on the top-left of the screen, where they belong
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
The source can be found on my GitHub (Although I'll sync it later on, and not at the time of posting this, due to me still needing to add some stuffs, like a title...)
This program is no longer supported by me! Check out Universal Android Toolkit for this kind of thing!
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I'm happy to announce that I and @Dante_xu (official Phoenix OS forum admin) have set up an official Slack team for all Phoenix OS users and for the Phoenix OS team.
Slack is a communication tool that let's users interact in group/private chats in categorized channels.
Currently the main purpose of this tool is community-based support.
You can solve problems together, share ideas and establish complete solutions to be published on XDA & Phoenix forums and on Phoenix OS site.
You can also get in touch with Phoenix OS team representatives directly. Do have in mind that it's a small team and their time is limited.
In the future, more Phoenix OS team officials are anticipated to join and engage with the community. This is just the beginning of improvements in Phoenix community management.
If you want to join the Slack team you need to:
Have at least 10 posts written on official Phoenix OS forum OR XDA-Developers forum. We can't risk having spammers around.
Send a PM invitation request with your e-mail address to Vioner or dante You can use the following scheme:
Hi,
Please send me a Slack invite to e-mail address: YOUR E-MAIL
Thank you
Click to expand...
Click to collapse
Once the message is sent (you can tick to track if the message was read) just wait for an e-mail with an invite.
Register using the link from the e-mail.
To learn more about Slack check this video: CLICK
See you on Slack!
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Unfortunately, last year Telegram decided to remove the official Telegram app for Wear OS from Play Store forcing users to install the old application(with some compatibility problems with notfications, stickers and media). When I started developing Weargram I wanted to create an app functional, modern and simple to update. This was possible thanks to TDLib(Telegram Database Library) and Jetpack Compose for Wear OS. Thanks to these powerful tools I can easily keep the app updated.
Current features:
Standalone app (Smartphone app is not required)
Creating a new chat
Send and receive voice notes and text messages
Receiving images
Explore users profile
Channels, group and Supergroup supported
Notifications
Features under development:
Send/Receive Stickers and GIFs
Receive Video Notes
Animated Emoji
Layout and performance improvement
Auto-download and more settings
Archived chats support
Localization
Improved notifications
The app will have a small price and will be published soon.
@Fra078 Are you up to creating a browser app for WearOS that would be somewhat useful considering that the majority of the current ones in the Playstore are close to being useless as useless can get?
Made an account just for this post, can't wait!
Thread closed. @Fra078 Please check your PM inbox. Thank you.
-Regards: Badger50