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?
Hello to all on this forum.
I have a Flash application that I want to develop into an Android app. I would not require some of the bells and whistles that are currently on the application, but a simple sub-set of how it works now. The flash application can be found here:
FastFood.com/nutrition/
(Hope this URL is allowed here as it will help people understand what I want to do.)
I have all the source files and programming for this and hoped they would be of some help in developing the Android app. But of course, I have no idea if this is any help at all to whoever develops the app for me.
Anyway, before trying to source a developer to do this for me, I thought I should ask a few questions to see if this is even something practical. So I hope some of you can give me some guidance regarding my questions.
1) Are most applications stand alone in the mobile phone, or is it common for some of these apps to access the network to get the necessary data required to operate? My purpose requires a database that is currently 14 megs, and must be accessible to the app, although only small portions of it are needed at any one time.
2) Are there varying systems within the Android family, or versions of the operating system that need to be accounted for?
3) Are there good reasons to develop for both Android and iPhone together? I mean from a cost to develop point of view? Or would it likely be just as effective to develop for Android, then move on to iPhone, or others, as is appropriate?
4) I am guessing that if you have looked at the flash version of our Calorie Counter, you could probably give an educated guess as to what it might cost to replicate a scaled down version for Android. So please, take a stab at it if you can.
Thanks
Hi Guys, I had a bit of a genius idea for an App. Anyways I have got a quote from someone who can create it for me, what I am wondering is though, how difficult do Google make it to get an app uploaded. Do I need a developer license or upfront payment etc. I don't plan on releasing anymore (not anytime soon), what sort of difficulties/costs are involved? Also how does device compatibility work, do I need to list all compatibly devices or its it just based on O/S version?
hey guys can someone tell me is there any way to add play store time remaining feature to android 4.2.1 ?
And i request developers to please work on this feature it is very helpful feature....
XDA Visitor said:
hey guys can someone tell me is there any way to add play store time remaining feature to android 4.2.1 ?
And i request developers to please work on this feature it is very helpful feature....
Click to expand...
Click to collapse
Hello, and welcome to XDA!
I find those things inaccurate, as the notification area estimate (including percent complete) rarely matches (or comes close to) the Play Store app estimate. That also begs the question on responsibility...are you talking having time remaining within the app, or in the notification area?
Right now for either, it's a fight against time. With the former, you are dealing with an older version of Google Play and Google Play Services, the responsibility of Google and that version (guessing 6.x where current is 8.x) is critical security updates only (if any at all) - no feature requests allowed. The latter scenario, probably relies on the former for information, but if not, it would be the responsibility of your ROM developer (e.g. Samsung Touchwiz 4.2/CM10.1/et cetera). They are in the situation of getting only critical security updates (if any at all) as well. After all, Android 4.2.1 enters it's fourth year of existence in November, and the attitude of Google is once a new codename has been officially released, all attention goes towards the new version (so the older stuff quickly becomes "abandonware").
CyanogenMod has been good on keeping older Android versions alive. Not so much for themselves, but for the older ROM's that borrow their code. The recent StageFright problem (dubbed SF1.0 as there is now a new batch of vulnerabilities) CM went back as far as 10.1/4.2.2 to patch the problems. With latest SF2.0 and the recent release of Marshmallow/6.0 I don't know if CyanogenMod will go that far back for their fixes this time (I am watching, as I have some Android 4.4.4 stuff to patch and plan to base off of CM11).
That was the long. The short being, since 4.2.1 is no longer a priority, I don't see it happening. Sorry.
Hi everyone,
I'm new to this forum and have joined as I've started working on a private/commercial version of AOSP. I've worked in mobile apps natively and more recently using React Native for the last 5 years and am enjoying hacking and playing around the source.
The main usage for build of AOSP is for a bespoke vehicle tracking device with a few additional features. So far I've managed to build AOSP, flash onto a device, and most recently set the tracking app as the home app so that it boots on launch.
The question that I can't find a solid answer to online is does anyone the best way of going about modifying AOSP so that we can deploy an OTA zip update and have the OS download and update it?
I'm not sure if this is necessarily the best way/use of time. I'm guessing it might be easier to just update the app itself internally and not develop OTA updates for the OS? I think at this stage I'm just after opinions before I spend too much time getting stuck into it. My only concern would be that we have 100+ devices out there and no ability to update the OS... although if it's a basic build of AOSP that just removes a few pre-installed apps, has a custom bootlogo and replaces the home app, maybe that's not necessary?
Any advice at this early stage would be gratefully received! Additionally, any tips for development or something a noob would benefit from would be great.
Thanks,
Joel