Related
Hi all,
I have a concept for a single update application that would be driven from the AndroidSPIN release database so all developers could use it for ROM, Themes, Applications and anything releases to devices.
If you wouldn't mind taking a couple of minutes to read this post, I would greatly appreciate it.
http://www.androidspin.com/forum/viewtopic.php?f=260&t=226
I'd really love to get a group together to collaborate and either help design this and/or write an application and back end to do it.
Let me know what you think.
Thanks
Simon
Sounds like an awesome idea, I'd love to help any way I can, but I dont fit in any of the needed positions for the post. Looking forward to see what develops though
Fantastic idea!
I only ever use XDA so god knows what I'm missing out on elsewhere and to be honest after searching the word android on google and trawling through one crap site after another becomes tiresome so hence the 'XDA only' policy.
Sorry I can't offer any programming skills but you have my support on this project whole heartedly, not that it counts for much I know buh MeH!
Hope you can get this off the ground.
As I mentioned to Simon already, I was thinking about building an update application for my ROM. I love the idea of having an on-phone ROM database, update capability, something that can easily be used by any developer in the community.
Some initial thoughts on functionality:
- Browse ROMs
- Download ROMs to SD Card
- Monitor specific ROMs for updates
- Monitor currently running ROM for updates
I'm willing to lend a hand on the Android side of things, but this will be a large undertaking and we will also need some people to contribute to the UI, server side of things, etc.
I do iPhone UI design for applications now (I don't have an iPhone, but most of my contracts and clients are iPhone based), but let me know and I can whip up anything you guys need UI related.
Send me a PM and I can get the ball rolling on how the functionality can be laid out as well.
Even tho I know I wouldnt be able to help out with this. I know I would love to test this out if you needed it.
Its a great idea!!!
I know a teeny bit of Java, and I'm working on becoming an Android developer, so if anything needs doing on the Android side of things, I'm willing to contribute.
Although I may not know as much as some others, I'm definitely a fast learner. I have a few books on Android development I'm reading through right now.
michinohatoresu said:
I know a teeny bit of Java, and I'm working on becoming an Android developer, so if anything needs doing on the Android side of things, I'm willing to contribute.
Although I may not know as much as some others, I'm definitely a fast learner. I have a few books on Android development I'm reading through right now.
Click to expand...
Click to collapse
Well, we can reuse a lot of code from Cyanogen updater.
akirah said:
Well, we can reuse a lot of code from Cyanogen updater.
Click to expand...
Click to collapse
Well, of course.
If anything else needs doing, however, I volunteer what spare time I have.
akirah said:
Well, we can reuse a lot of code from Cyanogen updater.
Click to expand...
Click to collapse
Could be easily done, would require quite a lot of laborious work ripping out all the stuff you wouldn't need though.
I would take a look at this but unfortunately I have another Android project on at the moment which is taking all my development spare time.
@SimonNWalker What sort of backend having you got going? REST? SOAP?
Ups wrong theread
not that it matters (since i kept the source 100% open)....
you have my blessing to tear the cmupdater to shreds if it will give us a unified solution to all our ROM cravings
firefart has done a good job of keeping the code pretty clean so there shouldnt be too many issues with grabbing it
and the new code for the screenshots for themes could probably be used to the advantage of this project with ease
I'm not really interested in a rom updater, but a market replacement with an "upgrade all" feature (à la apt-get / yum) drawing from multiple repositories would be most exciting.
The Cyanogen updater could be used, it just needs some modifications. Stuff like sub-sections and update all
Would probably need a new method to keep track of the updates aswell, I don't think json would be sufficient for a lot of applications and updates. Unless somebody could make some kind of script to automate the process when it gets uploaded.
willmav5000 said:
Would probably need a new method to keep track of the updates aswell, I don't think json would be sufficient for a lot of applications and updates. Unless somebody could make some kind of script to automate the process when it gets uploaded.
Click to expand...
Click to collapse
The only other method I would consider, besides JSON, is an advanced and well thought out web-based form that the developer is forced to complete upon uploading a ROM. This would place more burden on the server, but should be relatively easy to attach the provided ROM information to the rom database.
Think: Check boxes for firmware compatibilities, check boxes for device compatibilities, version number, change log, etc.
Maybe something a little like this?
Wow this would be/ is gonna be awsome!
I would suggest also that you can backup your sd card settings (and maybe also sms...) to an ftp server (or some other server you can install on your pc) from this app...
like (incremential) backup>partition>wipe>install update>boot>getbackupback
problem is to get the server adress back after wipe. maybe stored in web database and encrypted with phone imei number? or uploaded as google
whatever...
or just not wiping that single adress
just saying ^^
willmav5000 said:
Would probably need a new method to keep track of the updates aswell, I don't think json would be sufficient for a lot of applications and updates. Unless somebody could make some kind of script to automate the process when it gets uploaded.
Click to expand...
Click to collapse
JSON is just a file format. The CM Updater works via a static JSON file that gets updated manually. The way I'd design this (which is what I asked a couple of posts back) is a dynamic web service (probably REST based) which delivered JSON dynamically. Wouldn't be too difficult at all.
As SimonWalker said he's using PHP + MySQL I'm guessing that's already being done.
@garok89: CM Updater is completely open-source therefore blessings are not needed to use the source. Really don't understand all the "credit" crap here on XDA.
senab said:
@garok89: CM Updater is completely open-source therefore blessings are not needed to use the source. Really don't understand all the "credit" crap here on XDA.
Click to expand...
Click to collapse
I know it is open and I don't need to give my blessing for people to use the source. I did so because a lot of people don't feel comfortable using other peoples code without permission, regardless of whether or not its 100% open source.
And as for the 'credit crap'... I don't see you asking for your name to be removed from the 'about' section of the app
I am not asking for any credit
Anyway, lets not get off topic...
Guys, before this becomes Android Open Alliance, the sequel (you all remember how that went), I think we better set up a way to work together first and then toss in the speculative stuff later.
How about starting simple; set up a wave?
Android-x86 is a project to get android up and running on x86 architecture. It is currently ran by just two people, and 1.6 is more or less completely functional on Eeepc and Dell Mini's.
However, progress has slowed, and the developers are beginning to lose interest due to the current community following. A large amount of the followers of the project demand things, and give little back, often getting angry if they are not instantly provided what they want. This is a scourge of most opensource or hack projects, but especially so here, as the project has had little interest from other devs, leaving them on their own.
Whilst I do not have the ability to give a whole lot of help myself (yet), I desperately think this project should succeed, and am asking any able developers with free time who are up for seeing Android up on a new platform to give it a go.
The google discussion group is here: http://groups.google.com/group/android-x86
The homepage is here: http://www.android-x86.org/
Thanks for reading, and thanks for any support you are able to give these guys.
Hi everyone,
I apologize if if this is not the appropriate place to post this info, but I thought it would be of interest to some people here. You may have seen stories in the news recently about the privacy-monitoring extension for Android called TaintDroid that was developed by researchers at Penn State, Intel Labs, and Duke University. An excellent summary can be found on Ars Technica.
The reason I'm posting to this forum is that we are proud to have made our source code available last night. If you want to play around with the code, you can find it at the TaintDroid website (search "taintdroid appanalysis"). Along with links to the source code, you will find instructions for getting the code up and running on a Nexus One. We have also set up a Google Group for users who want to discuss anything related to the project.
Our only caveats are that we are merely researchers so 1) you use the code at your own risk, and 2) we do not have the resources to offer proper support. We hope that by releasing the code to the public a self-sustaining community of interested users will form.
We hope that you find our code interesting and useful. Happy hacking!
-landon
Thanks for releasing the code. Look forward to using it on an incredible rom soon.
http://appanalysis.org/tdro1d.html
I'm assuming that's the link. Couple of questions.
1.I see it's on 2.1 rom, does it work with 2.2? Especially as it uses the 2.6.32 kernel.
2.Since the Desire is basically a Nexus One with sense, has it been tested on that platform or with sense?
Thanks for releasing the source and instructions!
This is what Android needs, as Google is not taking good care of the privacy of it's users.
It's impossible to install apps now, because most of them want really wide rights, but you have no idea what they do with those rights.
TaintDroid at least gives a possibility to peek into what is being leaked.
Soon some of the app makers will start to encrypt their calls to try and and mask what they are leaking. If/when this happens, it should be a warning sign to users about that particular app.
Important: The docs are up. The live copy can be found on http://docs.insertcoin-roms.org/ and the Git repository on https://github.com/Manko10/InsertCoin-Docs/. For information on how to participate, see the wiki.
Hi,
This thread is related to the InsertCoin ROM by baadnewz (see this thread: http://forum.xda-developers.com/showthread.php?t=1198684). Since I haven't written 10 postings yet, I can't post to that thread nor create a new one in that forum.
InsertCoin has become a quite popular ROM for the HTC Sensation. It has had 200,000 downloads yet and numbers still raise. With increasing popularity it becomes more and more difficult to get hold of information you need concerning installation, problems, modification, tweaking etc. The result is a very high number of redundant questions on the forums and confused newcomers.
The project
Thus being said, it is time to create a good and centralized knowledgebase which helps new users to dive straight into using InsertCoin, keeps the development thread cleaner and helps to push the project forward since energy can be focused more on implementing new features and fixing bugs than on answering the same questions all over again.
baadnewz attempted to launch a Wiki once, but it ceased and shut down (as well as the whole baadnewz.eu server which was the last more or less valuable resource for help outside XDA-Developers.com).
Now my idea is to create a new official InsertCoin documentation project. I talked to baadnewz and he assured it would be promoted and integrated into the official website once it comes to life. The project I'm heading for is a community-driven one. I would work for it as much as I can but I can't do it alone. I'm not experienced enough in many (especially technical areas) of InsertCoin development and Android development in general. There are many things to learn about InsertCoin. And to be honest: I also don't have the time to write all the stuff by myself. Once I had written everything, it would already be outdated. So this project is only possible if other people participate actively.
How shall the documentation be implemented?
I thought of a project hosted on GitHub. Users can fork the project, make changes and send pull requests. For infrequent submissions, we could also provide a special submission form.
A staging server would then pull the HEAD revision regularly, format it and publish it as a website.
Sounds complicated? But it isn't. Git is pretty much straightforward and also users without technical knowledge can learn it very quickly (yes, there are great graphical tools for it). And of course, the documentation would also include a noob-proof guide to contribution.
But why Git? Why not a Wiki?
A Wiki might seem to be easier, but in fact a Wiki has to be updated regularly. Patches for bugs and security holes have to be applied. Additionally, we had to fight spam. Especially when we use some well known software such as MediaWiki, spam bots would love it. That can be a lot of work.
But the main reason is portability. A Wiki is a Wiki, nothing more. Exporting the contents into other formats would be a tedious process. However, when using plain text files with a simple markup language such as Markdown, they can be exported to all formats we like. Not only can the staging server parse it to HTML, but it can also be exported to PDF, CHM files (does anybody still use these?) and many more formats.
All right, but what is to be documented?
Well, a lot. Things I have though of are
Installation
Where to get InsertCoin ROM?
Which version?
How to flash InsertCoin?
How to upgrade from previous versions?
To wipe or not to wipe (and when)?
Kernels
Which Kernels are there?
Where to get them?
What are the differences?
Advantages/disadvantages of specific Kernels
How to install a new Kernel/revert to stock?
What is a Kernel and why can't I install it via the Market? (dumb question, yes, but important to know)
Known problems
Any reported bugs still present in version X?
How do I report my own bugs?
Why does feature Y not work (and never will)?
Features
Why to choose InsertCoin?
How to submit feature requests?
Requirements
What do I need to run InsertCoin?
Which baseband version do I need?
Where do I get a new baseband version and which one to choose?
Does it work on device X, too?
Which is the oldest supported version for custom kernels?
Add-ons
Which add-ons are there?
Where to get them?
How to flash them?
What to be aware of?
How to get rid of malfunctioning add-ons?
Customization
Which themes are there?
How do I install them?
How do I revert back to the default theme?
How to set up custom boot splash and boot animation?
FAQ
Things users ask all the time
Things users might ask regularly in the future
Milestones
Any planned features for future releases?
How many ROMs to release tomorrow?
Participation
How to submit patches?
How to improve the documentation?
How to pay a round for baad?
General information
What else could be valuable information?
How do I backup and restore my data most efficiently and least time consuming for upgrades which force a full wipe?
etc.
The list goes on. It's up to us how much it'll grow. Make suggestions please. Don't hesitate!
And now you come into play!
Do you think, such a project could become a success? Do you have suggestions, ideas, criticism? Post it here. Please.
Would you like to contribute? Post an answer. You would be one of the glorious pioneers.
If I get enough positive feedback and support by people who want to contribute I will start working on the base system, set up the Git repository, write the staging software and launch the project. If not, it would have been at least worth the effort. But you would contribute and give something back to the community, wouldn't you? Sure, indeed...! ;-)
Cheers
Manko10
Do you think, such a project could become a success? Do you have suggestions, ideas, criticism? Post it here. Please.
Would you like to contribute? Post an answer. You would be one of the glorious pioneers.
Click to expand...
Click to collapse
of course it'll succeed cause it'll be much easier with plain updated steps (n00b proof )
I would like to contribute if u may allow
THIS IS AWESOME
Of course you can contribute. Everyone is pretty much welcome to do that.
For Baad and InsertCoin itself, I think it would be a perfect success. I myself have been looking for a central resource database for InsertCoin, but always resort to just searching the thread, which is not exactly the most efficient method.
I don't know much on the technical ROM-based side of things, but I am a web developer, so I'm sure I'd be able to help in the deployment of such a website. I also happen to have a vBulletin license I'm not using. If Baad wants to expand his ideas even further and have a sort of official InsertCoin forum, all to himself, I could most definitely lend a hand for that.
I'm thinking large scale here; and upon writing this, further ideas have just popped into my head, but I'll save that for later, but hey, Baad is largely-awesome.
If you happen to have an MSN or Skype, Manko, I'd love to talk to you further
i have a better idea for talking / chatting in a more centralized way: IRC
#baadnwz-roms on freenode
I don't know much on the technical ROM-based side of things, but I am a web developer
Click to expand...
Click to collapse
So am I.
I'm quite sure, baad will help us as good as he can but he is of course very busy with the ROMS. So it's better to have many guys in the project who know more about the technical stuff.
I would try to help too, if You like. If You don't need IC pro's only
We need everyone (IC pros are needed, but not only).
First of all we need people who have fun writing and maintaining (!) good and understandable documentation.
Guys
if you do this - it will be bloody FANTASTIC!
noobproof guide needed badly
Make it so. Sounds like it could become a great resource.
It will, but only if enough people participate.
why not add chatbox on the coming site, isnt much better? 24/7 we can have conversation as like me, am from the philippines, and my time is different to others
Well, the documentation would also be there 24/7. I think for live talking we should better use IRC (#baadnwz-roms on irc.freenode.net). Embedded chats on websites consume a lot of bandwidth.
lol!, i guess so, yeah, maybe irc is much better. anyways, maybe i can contribute some design for future use.
Just jeep in mind that IC is also made by baadnewz for the Desire (and the wildfire too?). I'd like to write some things for the Desire version of IC.
koenvbeek said:
Just jeep in mind that IC is also made by baadnewz for the Desire (and the wildfire too?). I'd like to write some things for the Desire version of IC.
Click to expand...
Click to collapse
yes once the project starts, desire will be there too
for wf i made 2 roms long time ago, and then i sold the phone
Ill contribute if i can I love this rom
wow... this sounds freaking awsome. i would most definately help with coding once the repositories are set up ^_^
I think it would be really beneficial for everyone especially for the folks who are new to the ROM. 600+ pages of comments are a LOT to read through!
Make it so. (with Jean Luc Picard's Voice ) Nice idea.
Would like to contribute sth, though I have a really tight schedule lately...
Hi!
After only being a user for a long time, I've recently begun to develop for Android as well, and I think that I have identified quite a few niches that could use better apps. However, I've never collaborated on an Open Source project, and I'm really unsure what the written and unwritten rules of the subculture are. Could anyone point me in the direction of good resources to learn about them? I know I can probably find those through Google, but I wouldn't know if I'd end up on any site owned by Stallman or Shuttleworth and I'd rather be part of the mainstream, so to speak.
To indicate what kind of questions I'd like to have answered, without requiring anyone to answer them here: What level of expertise is required? Can I just join anyone and upload to their repository, relying on them to sort out the parts they want? When can or should I fork a project? When is it considered rude to take code snippets from someone? How sure can I be that the project's owner won't change the license and steal my code? How would those questions be answered if money is involved? Is it considered reasonable to make an Open Source application that people pay for in the Play Store? How would I handle contributions to such a project? What would be the best license to ensure that I both contribute to the Open Source movement and protect myself against people stealing code? (I. e. just forking it and slapping their name on it.) And many, many more - as I said, I'm really unsure how to start out with this.
Thanks very much in advance!
Regards,
David
Maybe I can help you on a few of those points. First off, feel free to fork anything you feel like, whenever you feel like something needs to change. Also feel free to push any changes you make back to the original project. The project owner can decide what to merge in. As for lisening, please note Im NOT A LAWYER, however, I think I can offer some general knowledge. If code is under a typical open source license, the code at that particular point in time is free to be viewed by anyone. A lot of open source licenses, though not all, are considered 'copy-left', in that any code DERIVED from the liscensed code also has to follow the same license (GPL comes to mind). This helps from people 'stealing' your code at a later point under a closed license. As for taking code snippets, it depends on the license of the code. If you grab a piece of code from a GPL codebase, whatever you're using that code in also has to be GPL licensed. You are in essence taking their code, and modified it. Learning more about different open source licenses might be something to look into, depending on how far you want to delve into this As for making people pay on Play store for open source projects, its certainly acceptable. A lot of people make money from open source software by prividing some form of 'support'. Whether thats tech support, or whether its compiling, packaging, and making it available (as you might do for an android app) you are providing some sort of service aside from the actual code that people will pay for. I've seen a few projects go this route. Hope this gives you more answers than it does questions! The OSS community I've found to be a pretty easy going group of people, so long as you follow a little common courtesy, and have a bit of common sense. Cheers!
Thanks a lot for your reply! It has certainly helped me to make my mind at ease - I know that Open Source people can often be _very_ friendly and open, but it seems like you really do not want to get on their bad side if you intend to be a developer. That's also why I especially worry about being rude, not about doing something illegal - the licenses themselves seem to be quite permissive.
Quick followup question on the money thing, though - is it accepted by Google if I offer a paid app in the Play Store and at the same time free on F-Droid? Or would I have to ask someone to compile and upload it there without my official participation? Because that would kinda be the ideal model for me - Open Source, free app on F-Droid and sideloaded, "lite" and paid versions in the Play Store. Something like that would be good to know before I actually begin thinking about deploying some app.