As per the iPhone thread...
How much would you pay (from the App Market) for an Android based Orbiter with full functionality?
remember, android phones will be on every carrier worldwide shortly.
The HTC Dream and Magic are excellent especally with Android 1.5
Samsung, Lenovo, Acer, Motorola, SonyEricsson have all committed to producing Android based phones.
Many other companies are also looking at Android for all sorts of things such as tablets and small netbooks & laptops
Does Android have access to the underlying bluetooth? This is important for Mobile Orbiter usage.
-Thom
yes.
http://source.android.com/projects/bluetooth-faq
Quote from: richard.e.morton on May 03, 2009, 04:53:16 PM
As per the iPhone thread...
How much would you pay (from the App Market) for an Android based Orbiter with full functionality?
remember, android phones will be on every carrier worldwide shortly.
The HTC Dream and Magic are excellent especally with Android 1.5
Samsung, Lenovo, Acer, Motorola, SonyEricsson have all committed to producing Android based phones.
Many other companies are also looking at Android for all sorts of things such as tablets and small netbooks & laptops
We'd contribute to this for sure :-)
Andrew
Wow... The original Q, as yet not answered, was how much we would be willing to pay.
Not sure, but if it works correctly, I'd pay up to $5. I'd love to help you test, as well, if you're looking. Running 1.5 on my G1 for the last few months, with the UnionFS apps2sd hack.
I think $5-$10 seems pretty fair to be honest. To make the most of the app it would have to work on more than just a G1 though as that phone will be long forgotten within a year or 2 as android establishes itself (IMHO)
we still need to put together a development fund:
One would need:
* a Google Dev phone (unsigned and unlocked for dev work)
* android SDK
* a copy of the current JavaMO to borrow code from
At the very least, this would be a straight mobile orbiter using the Bluetooth Dongle proxy, and would take maybe 30 hours of work to port. I'm not sure, because i am not familiar with the more interesting gotchas of the android platform that may be.
-Thom
bluetooth and UI will be different. Otherwise most of the JavaMO code can be used.
br, Hari
ps: I never took money for my contributions, so please don't get me wrong. But 5/10$ is not really an incentive for many devs that want to earn money for their work. Given the small market penetration of Android, how many sold copies would one expect in the next year? Let's assume 200, but I think thats quite high for the intersection of lmce/android users. That pays about a day of a developer..
YES. Just YES.
$50 would get you few buys. This is an open sourse project, and whilstI appreciate that that means free as in libre, It should also be as close to free gratis as possible. OS should be a labour of love, not of money, and whilst I can't program, If I could, I wouldn't expect to be paid for a OS piece of kit. That comes through advertising, which comes through popularity, which comes through freeness. Firefox is a good example of this,as is Linux. No-one has ever had to pay for using them, and their founders are fairly rich. Not Billionaires, admittedly, but they don't exactly have financial problems.
Whilst I'm not a developer, I do not view LMCE as anything other than a labour of love. An amazing, Fantastic, even orgasmic labour of love, but a labour of love none the less.
Che, no offense, but you have not undestood how open source works.
To stay on topic, http://android.git.kernel.org/?p=platform/frameworks/base.git;a=blob;f=core/java/android/bluetooth/BluetoothSocket.java;h=fd8885ece9935e2f4909940c582bfa6a803afd41;hb=master
that is the RFC from last month for RFCOMM. I don't see server side rfcomm support in there..
br, Hari
argh, /me was not looking hard enough, thats the server side: http://android.git.kernel.org/?p=platform/frameworks/base.git;a=blob;f=core/java/android/bluetooth/BluetoothServerSocket.java;h=ca467011c91ec92fb4ff5ef3af9fba1c4a49b45b;hb=master
Not bad, one should be able to plug that together with the existing commandprocessor. If Android is capable of drawing png/jpg on some canvas and reporting keypresses/pointer events back, we are pretty set (yes, I assume it can :-p)
br, Hari
Quote from: hari on June 07, 2009, 09:29:02 PM
ps: I never took money for my contributions, so please don't get me wrong. But 5/10$ is not really an incentive for many devs that want to earn money for their work. Given the small market penetration of Android, how many sold copies would one expect in the next year? Let's assume 200, but I think thats quite high for the intersection of lmce/android users. That pays about a day of a developer..
I agree with you Hari...so maybe in these cases we should make contributions in a more general sense. Maybe the fund would provide all of the dev tools and hardware for development of any new platform such as this. Another possibility is that some Dev's may not want to be 'paid' in anyway but would be happy to receive some new LinuxMCE "toy's" as a way of thanking them for their efforts...these would be gifted in a decoupled way so the Dev in question had no feeling of obligation as such.
Anyway just some ideas from...we as a company are open to all of the above (and any other proposals that might emerge in discussions here)
Andrew
yup, in the end, I really would just want to be able to realistically keep up with the glut of hardware flowing into the market and e able to support it.
It is nice being able to occasionally pay bills and expenses by doing a large driver project or two, but those are very few and far between.
So really, i'm open with whatever works :)
-Thom
My next mobile phone will be whatever linuxmce has the best support for -there's talk of developing for both android and the iphone. I'm willing to contribute $40 to one of these, but I prefer to wait to see which makes greater strides.
We're going to probably support the iPhone/iPhone before Android.
Just to give my 2 cents, I would contribute to an android orbiter. I do not have either a android phone nor a iphone, but it would make more sense to have an orbiter for the android phones considering that only AT&T has the iphone. Android phones will be available on cdma and gsm networks such as verizon, sprint, AT&T, and t-mobile, making android a better choice for linuxmce. The bigger the pool of users, the bigger the pool of people who would contribute for development now and for future versions of an orbiter. :=)
Quote from: widescreen on June 25, 2009, 04:05:00 PM
Just to give my 2 cents, I would contribute to an android orbiter. I do not have either a android phone nor a iphone, but it would make more sense to have an orbiter for the android phones considering that only AT&T has the iphone. Android phones will be available on cdma and gsm networks such as verizon, sprint, AT&T, and t-mobile, making android a better choice for linuxmce. The bigger the pool of users, the bigger the pool of people who would contribute for development now and for future versions of an orbiter. :=)
I think both would be great additions...but it has to be said that currently there are more users with iPhones than Android based phones. This could change over time as more phone manufacturers build products around Android...but for now thats the case.
Andrew
It would be really cool if a android orbiter was integrated with androids UI (using its menu button to bring up the computing, sleep menu, power, more, etc buttons), so the tilt function, and maybe even a widget view just whats playing (and maybe some other things).
Is it posible to get the information out of linuxmce so it can be rendered in the orbiter (in this case the android handset)?
If true, then I'm intrested in take part in this project.
Gaute
mobile orbiters are very simple programs.
They recieve images of fully rendered screens from the core over RFCOMM,
they send back keypresses and screen touches over RFCOMM,
they send back bluetooth location information.
In the end, we would make a touch screen UI variation, which would take advantage of the phone's screen, and build a UI for it, but due to the nature of how Orbiter works, making one with a "native" UI would be exceedingly difficult
-Thom
Okey, I see... But how about making a extra varitation (not necessary a extra HADesigner variation) for use on a widget?
You'll need to spend some time with the system's tools to find out why going that route will be exceptionally strenuous.
Dude, it's really very simple. Get down into the code and do some research. A lot of people just talk on here. Are you going to be one of those people? Or are you going to DO something?
I am very fed up with people who MIGHT do something if EVERYTHING along the way is PERFECT and WILL WORK OUT GREAT! STOP BEING LITTLE BABIES. GROW A PAIR AND TAKE SOME RESPONSIBILITY!
Come on, fellas. If you want to make this system better, DIG IN, AND DO SOME _REAL WORK_ WITH ME.
I know it may seem like i'm ripping you a new one, but this comes from many months of frustration, I'm through being nice to those people who MIGHT help. EITHER HELP or DON'T.
-Thom
Quote from: tschak909 on August 16, 2009, 05:29:05 PM
You'll need to spend some time with the system's tools to find out why going that route will be exceptionally strenuous.
Dude, it's really very simple. Get down into the code and do some research. A lot of people just talk on here. Are you going to be one of those people? Or are you going to DO something?
I am very fed up with people who MIGHT do something if EVERYTHING along the way is PERFECT and WILL WORK OUT GREAT! STOP BEING LITTLE BABIES. GROW A PAIR AND TAKE SOME RESPONSIBILITY!
Come on, fellas. If you want to make this system better, DIG IN, AND DO SOME _REAL WORK_ WITH ME.
I know it may seem like i'm ripping you a new one, but this comes from many months of frustration, I'm through being nice to those people who MIGHT help. EITHER HELP or DON'T.
-Thom
I fully understand your frustration and I cannot say I disagree, but maybe you should just take a break from answering posts like these for a while.
Yeah, you're right.
sorry.
-Thom
I second Zaerc.
And for what it is worth, if members from the core team will continue to shout at and insult users, I will spend my spare time for another project.
br, Hari
I'm going to order a android phone, and going to start look at the development of a android orbiter...
But what do you think is the best way of develop it? Building it from scratch or use the JavaMO as a base?
The JavaMO could be used as a base.
-Thom
I'm in for this 2 :)
it seems the Android stack has its own unique problems, particularly that the phone itself cannot be an RFCOMM server, which is required by our bluetooth code.
-Thom
Quote from: tschak909 on October 20, 2009, 12:21:31 PM
it seems the Android stack has its own unique problems, particularly that the phone itself cannot be an RFCOMM server, which is required by our bluetooth code.
-Thom
thom, check this out:
http://code.google.com/p/android-bluetooth/
Do you think It still will be a problem? I was looking into the android dev resources and about to dig into a android tutorial, but if it android is useless with lmce, i wont bother. thanks
looks like it is saying that the RFCOMM server feature will be available in the November 2009 release...
I would want this even if not owning a phone with android, especially since these little boards seem to be able to run android..... :)
http://www.youtube.com/watch?v=05aFF0fx4hs (http://www.youtube.com/watch?v=05aFF0fx4hs)
http://www.youtube.com/watch?v=EpB0gQXMPpY (http://www.youtube.com/watch?v=EpB0gQXMPpY)
Mini2440 with android and linuxmce, count me in. I'm seeing a lot of possibilities
Richard
I've been a member for a while but I have never posted so here goes.....
I am not a developer, I am a register nurse who is learning *nix quickly so forgive me if some of the things I say seem amiss. I love the idea of LinuxMCE and will be implementing it very soon. Since I am not a developer, I thought I would contribute by documenting my process/progress and advertise as much as possible. I can't code (yet) but I am no leach either and will document, document, document or whatever else I can do to contribute.
That being said, here is my two cents: I have been riding the fence for some time about Android vs IPhone. I'd love to see the Android take over because of its true openess if nothing else. It doesn't have the market share today, but I feel as though it could capture it in the near future. Plus all of the other devices that it'll potentially run on. So, I would love to see LinuxMCE make use of the Android OS!
Again, since I am not a developer (nor a leach), I can and will contribute financially to this effort. I am not made of money so don't get any ideas about future projects when I say this but,.......I'll give $100 toward this effort and look into getting/shipping an unlocked device for a worthy developer sometime later if it hasn't happened already.
I have to wait till November too because of personal reasons and wanting to wait for the new release of Android, but hey, that's right around the corner!
Skates
It appears that Android 2.0 will have RFCOMM support. Please see the following like for details.
http://developer.android.com/sdk/android-2.0.html (http://developer.android.com/sdk/android-2.0.html)
Quote from: JDFire on October 27, 2009, 11:52:57 PM
It appears that Android 2.0 will have RFCOMM support. Please see the following like for details.
http://developer.android.com/sdk/android-2.0.html (http://developer.android.com/sdk/android-2.0.html)
saw this:
# Connect to a remote device using RFCOMM and send/receive data
# Advertise RFCOMM services and listen for incoming RFCOMM connection
I have seen posts from HTC stating that they are working on an update for their devices currently running android 1.5 and 1.6. i assume other devices will be compatible also. In addition there are several upcoming devices with 2.0. My phone had a drinking problem (got wet with rum at a party lol) I'm pondering whether or not to go with a android for the possibility of using it with Lmce. any opinions?
I have the new Motorola Droid and will be looking to port an orbiter to this platform, but I am having one bitch of a time getting 810 back up and running at home. I have reinstalled at least 15 times, and have had varied results all bad. As soon as I can get a stable system running, I will start looking at the code to do this.
Quote from: skates44 on October 22, 2009, 05:46:54 PM
I've been a member for a while but I have never posted so here goes.....
I am not a developer, I am a register nurse who is learning *nix quickly so forgive me if some of the things I say seem amiss. I love the idea of LinuxMCE and will be implementing it very soon. Since I am not a developer, I thought I would contribute by documenting my process/progress and advertise as much as possible. I can't code (yet) but I am no leach either and will document, document, document or whatever else I can do to contribute.
That being said, here is my two cents: I have been riding the fence for some time about Android vs IPhone. I'd love to see the Android take over because of its true openess if nothing else. It doesn't have the market share today, but I feel as though it could capture it in the near future. Plus all of the other devices that it'll potentially run on. So, I would love to see LinuxMCE make use of the Android OS!
Again, since I am not a developer (nor a leach), I can and will contribute financially to this effort. I am not made of money so don't get any ideas about future projects when I say this but,.......I'll give $100 toward this effort and look into getting/shipping an unlocked device for a worthy developer sometime later if it hasn't happened already.
I have to wait till November too because of personal reasons and wanting to wait for the new release of Android, but hey, that's right around the corner!
Skates
I could have written this post myself with the exception of being an RN. I have an iPhone, but I can't believe how quickly Android has taken hold of the Smart Phone market!!! Skates, I absolutely agree that Android is the better fit because it is an open platform. I have never felt comfortable with how restricted the iPhone is...even the jailbroken versions. I'll pledge another $100 to whomever is responsible for getting a fully functioning Orbiter on the Android interface. I want to contribute more than just my $$, but I have other commitments at the moment. I am so eager to be a part of this community, and I think that getting an orbiter that can unlock all the functionality of LinuxMCE on a popular smartphone interface is a vital component to its future success! I believe Android will bridge across every Wireless provider, and soon! That makes it the best candidate at being available to the largest audience. It could even be the death knell for Symbian, Palm, and even Windows Mobile...at least as they currently reside as closed source and $$. I'm not arguing against the iPhone just yet, it is going to be around for a very long time, and hopefully Jobs lets it off its leash.
I have followed this forum for awhile now, and I have to give a respectful thanks to the small group of dedicated developers who have put so much time and effort into this project (you know who you are). I admire your immense efforts!
I want to start digging into the code, and I have planned to tie off my loose ends to my current commitments in order to become a contributor to this effort, and even starting a local club (or support group) in my area. Long live LinuxMCE!!!
Hey I haven't posted for a while here but wanted to share some info on Android Dev. I noticed a few posts that were a little off about the DEV. First is that you don't need the hardware. Google makes an awesome emulator that works very well. Also use Eclipse for development. The Android SDK gives you all you need plus the emulator and wizards. And its OpenSource.
I know its not an orbiter but someone does have a free app that is a mythtv remote.
http://code.google.com/p/mythmote/
http://code.google.com/p/mythdroid/
Scott
Might already been thought of or maybe impossible or something but I was thinking:
Why not add the possibility to control the MD with an android phone by the accelerometer? Just like it was a gyro mouse.
I am in for 100.
*edited out error
Side note... droid has a magnetomer. In verizons infinite wisdom, the only cases they had at my store had magnetic clasps, which will ruin the phone in this capacity. Do not get a case w a magnet.
Grrr...why oh why does this community just want to pay people to do things, time after time I see this happen here and it completely thwarts the whole spirit of open source. Greed, necessity, whatever it is, all this paid development crap is not helping the cause IMO. If you're going to do it in your spare time do it because it's a hobby and you want to or if you just want it, but don't have the skillset then learn, there are plenty of people here helping me learn right now. The means are there, you guys just need to put some of your own time into it and stop just throwing money at it. The problem is that there just aren't enough people doing work on the system, no matter how much money you throw at it, that's still going to be the problem! Dig in
This is so self-evident, but: to begin 'learning' of the system is rather difficult. I, for example, have spent a lot of time reading this forum and wiki, yet, am unable to do any practical development. It does not mean I'm not committed to this, however.
It would be great to have some workshop around this?? Europe&US??
I just picked up a Motorola Droid - it's sweet. The only thing it can't do is be a LinuxMCE Orbiter... Has anyone started work on this? I can volunteer to do testing or work along side someone over the next few weeks. I probably won't have time to do hardcore development work until after winter.
I plan on it , as soon as I get my system back up the way I want it. One MD do go. I think I am going to look into using wireless Lan instead of bluetooth. I will let you know in the next few weeks.
Ideally, we should be able to choose. Personally, I don't care which is used.
I agree and if I can get one working I can try the other. But I want to get one working first.
Yes. Have you looked into Android development at all? I'm planning on setting up a dev environment next week if I have time.
Started messing with it. It is java which is my area of expertise.
Do you have an idea of what needs to be done to get JavaMO running on it? Should be pretty straight forward to get it to run, and then put some Android wrappers for install and launch I would guess.
Haven't really looked at it on android yet. I messed with it a little on the nokia 5800. Bluetooth is the big issue, that's why I may try something with the wifi if possible.
Ok. We'll see where it goes then. Keep eachother up to date on progress.
I got an Android development environment, and I think I've got Android development figured out for the most part - it's pretty nice actually. I looked at the JavaMO code - it seems that it's not going to be terribly useful, except as a reference for a complete rewrite. JavaMO is heavily dependent on JavaME libraries which are not available in Android.
Supporting WiFi is a very different track than supporting Bluetooth. The Bluetooth Orbiters are mobile orbiters, which are very different than networked orbiters. That means none of the JavaMO will be helpful for a network orbiter, which would require a Java-based DCE library.
I'm continuing my investigation into other methods. If I turn up nothing, I plan on porting JavaMO to Android.
Jimbodude,
I had a quick look the other day at all this as well and I actually came up with the opposite opinion on it.
I didn't think that there was a big dependancy on the JavaME libraries really... what did you think the problem bits would be?
Is your aim to write a complete orbiter in Android or to get JavaMO working - as these are completely different tasks. I am interested in both but I think getting the JavaMO working first is probably a good first step. I went to have a go at this but my dev machine's HD seems to have failed.
Supporting Wi-Fi (or just socket connections rather than Bluetooth) should not be very hard and probably just needs another device created that makes use of the BD stuff. The BD stuff actually has code already in it that allows it work (for testing) over sockets. This would not support proximity detection etc that Bluetooth does however.
I will try and help you out in whatever way I can. I think that the Android dev libraries provide a lot of potential for implementing a complete orbiter but will either need java based DCE comms or some form of proxy device arrangement.
Will update if I make any progression....
Regards
Darren
Almost every class uses the javax.mobileedition packages, which are not available in Android. These are used for Bluetooth comms, for rendering, and for hardware control (such as backlight power). To replace them would seem to require a similar, but different, implementation using Android libraries.
I think a lot of this dependency could be removed, however, to make a more generic implementation of the core features that could support both JavaME and Android, with some specific implementation bits created for each platform. I'm not sure if it's worth the effort, though.
I have some other things going on for the next 2 weeks, so I'll have to put this aside for a bit. Don't let that stop anyone from having a go at it - the code is not terribly complex, and I would bet that someone with some Android dev experience could pull this off in a few days or less.
I'm on vacation right now but when I get home I have 2 priorities.
1. Get my system working with a single remote control. (Wife comes first).
2. Start working on the android mobile orbiter. To be honest I'd like to get remote functionality working first on the droid and then add the fluff of album, currently playing, etc. If this takes a complete rework I think it maybe best to break it down into different functional steps/components.
The code is not nearly as complex as you are thinking... Take a look - the phone isn't doing much computation work outside of drawing the image on the screen and figuring out what buttons have been pressed. Excuse me for my bluntness earlier - by "complete rewrite", I didn't mean it would be a difficult one, nor should it require much design work - unless you want it to, I guess. From what I can see, the work pretty much consists of changing out the JavaME libraries for Android ones... All I meant was that JavaME and Android probably can't share a version given the way this is written now.
I may have over-exaggerated by saying "almost all classes depend on JavaME libraries" - in fact, less than half of the classes depend on JavaME (about 25 out of 60), and they are mostly not too complex.
I also mis-typed the package name - its "javax.microedition" not "javax.mobileedition".
Went through the javamo code and it should be fine as a basis for writing the equivalent using the android framework.
I agree, probably more effort than its worth to share same codebase - but have not discounted it yet.
Will have a go at it on the weekend.
Where has everyone else reached on this?
Started to look at it this week. I think it is going to take a bit more than was discussed in previous posts, simply because of the differnce in graphics libraries between javaME and android. When I get some more time next week I will start to do some more on this.
Just got back from holidays for the last couple of weeks.
I managed to have a look at it before I went. Made some basic progress - in that I could port over the existing JavaMO code to run on android. I am using Socket connections rather than Bluetooth. Will get it working with that first I think.
Was in the process of setting up a test harness to send/receive BD commands to/from the phone. Will try that further this week or weekend.
Regards
Darren
Quote from: darrenmason on January 27, 2010, 02:03:05 AM
Just got back from holidays for the last couple of weeks.
I managed to have a look at it before I went. Made some basic progress - in that I could port over the existing JavaMO code to run on android. I am using Socket connections rather than Bluetooth. Will get it working with that first I think.
Was in the process of setting up a test harness to send/receive BD commands to/from the phone. Will try that further this week or weekend.
Regards
Darren
Any progress Darren? I was thinking about doing this myself when I noticed all of the chatter on the forum about it. No sense in wasting someone's effort.
castle
Hi,
Doing little bits when I get a chance. Been reading up on the Android platform lately to get a better idea of how the intent stuff works etc.
Probably code a bit more over the next few weeks.
Feel free to jump in and have a go.
Regards
Darren
Darren - I have a Google Nexus One now, so if you need a tester, let me know! (still on 0710 tho, btw!)
You guys are aware that someone made a svn commit with an apk file right? Looks to be JavaMO ported to Android.
Any details on that addition? I may have more free time to look into this in the coming weeks.
Quote from: los93sol on March 12, 2010, 05:21:35 PM
You guys are aware that someone made a svn commit with an apk file right? Looks to be JavaMO ported to Android.
Any updates gentlemen? Just want to know before I waste my time on something that's already close to completion.
Can someone please grab this from svn and verify that this works?
-Thom
Quote from: Newguy2 on April 19, 2010, 04:45:40 PM
Any updates gentlemen? Just want to know before I waste my time on something that's already close to completion.
The update so far when anyone has asked has been silence. Because of that, I doubt anyone is working actively on it. If you get an Android orbiter working, it will not be time wasted. The only wasted time so far has been waiting for people to tell us that they are not doing anything...
I'd suggest you go search out this apk file in SVN and see what it does. I asked about it earlier and have had silence since - so I doubt it's active. You may also want to look at the RPC plugin, which is also in SVN. There is no documentation for it outside of the source code. Hari is the one who wrote it, I believe. I have not used it, but it sounds like the web-based features would work well for Android-based applications.
Whichever approach you choose - please keep everyone up to date on your progress with either a wiki page or a thread in the developer's section.
I have not had a chance to look at this in a while. The wife gave birth to our first last week, so fun has been on hold for a while. Well not all fun, just gadget fun.
From SVN;
"Early alpha, strait transform of the original JavaMO, still runs through the j2se, and is not actually ported to run in android native.
It is an orbiter in apk format but also requires the j2se runner.
Ive had it work in the virtual 2.0 environment that runs in my sdk, but no luck yet on the dream. I believe it to be a memory limitation.
needs testing"
Checked in by f8al, I havn't tried it.
My progress has been slow to non-existant. Currently working on two other things that are higher priority for me at the moment.
I don't think anyone has progressed too far so it wouldn't be a waste of effort to have a go at it.
Regards
Darren
I was asking my self if i could use the source and change the preview of the orbiter .Could u tell me ? If u allow me could u please send me the source ?
And other did u stop the development of the Android orbiter ?
The work that was done in this thread did not progress much further. Instead I developed a ProxyOrbiter client in Android that was simpler to develop and utilises existing backend functionality. This provides a reasonable user experience and is suitable for performing most interactions.
See this thread for details
http://forum.linuxmce.org/index.php?topic=10811.0
And the code for this is here
http://svn.charonmedia.org/trac.cgi/browser/people/darrenmason/AndroidTouchOrbiter
Hoping to update this with increased functionality in line with the work that Andrew and the Dianemo guys are doing.
regards
Darren
the URL for the code is no longer accurate.
Using the charonmedia URL should have been avoided since April 2008... ;)
http://svn.linuxmce.org/trac.cgi/browser/people/darrenmason/AndroidTouchOrbiter
is the correct one.
Sorry posde didn't realise. Additionally sent the post from work where svn.linuxmce.org is blocked but svn.charonmedia.org is not....
The svn server on charonmedia is no longer maintained by us.
Interesting, that they block the svn.linuxmce.org server... I wonder why. Maybe you can find out the reason for the blocking.
Quote from: darrenmason on June 10, 2011, 01:47:43 AM
The work that was done in this thread did not progress much further. Instead I developed a ProxyOrbiter client in Android that was simpler to develop and utilises existing backend functionality. This provides a reasonable user experience and is suitable for performing most interactions.
See this thread for details
http://forum.linuxmce.org/index.php?topic=10811.0
And the code for this is here
http://svn.charonmedia.org/trac.cgi/browser/people/darrenmason/AndroidTouchOrbiter
Hoping to update this with increased functionality in line with the work that Andrew and the Dianemo guys are doing.
regards
Darren
Proxy Client works well ,i hoped for some application for Android like the Dianemo for the iOS ,that app looks nice (i've seen it on pics i dont have device to try it).
Hope that you will progress with the application with the guys from Dianemo, i'm newbie in java and android as well so i cant help much :( .
Regards,
Daci