[IDEA] Another Hand To Android From The XDA Team

[protozeloz]

Hello to all XDA developers and chefs

Before giving this idea i would like to introduce myself I'm a new programing student interested in the Java programing language, also interested in mobile programing. I've already tried searching for this idea and as far as my research went there has been none like this.

Here it goes

-Everyone know how much of a pain it is for several people to use the skinned versions of android on their phone (blur, sense, other), we all would like to get more stock android from our companies but it seems to become a unreachable dream. now many have said that they must find an workaround for this, yet no idea seems to become a reality....

now my idea consist in having to android packages on every phone from stock one package that will be installed for default and another package that the user may choose to install, the default package will come with a skin while the optional package will contain stock android, now the way to manage this two is via an application from witch the user by running it will decide to have stock rom or skinned.

Now this is the way I think this should work

-User opens the app
-App pops a warning to the user telling him its phone will be fully reseted
-The user accepts the consequences
-The app turns the phone into a recovery mode with a selection for witch package to recover from (for example return a #1 indicating that the user wants skins on his phone will install the package with the skin or a #2 to run a package with no skins at all)

why am I asking help from XDA? because of two things

-I currently don't know that much about programing
-I think XDA would be the best site for the idea to grow and become something significant

what are my plans with this idea? I'm currently writing an open letter to Google and the manufacturers to bring many options to the OS. I thought i would be a great idea not only to deliver this letter but to give the materials they could work on...

do I get anything if I help with developing such an idea?

I currently have no plans on taking credit or any remuneration of any kind from this "project" but I would clearly name those who made this idea possible, now if "bounties" where to come from this then you may earn them...

what are you asking me to do?

-Brainstorming, I would like to see how this idea gets refined.
-Development, when the idea is complete having many attempts to get the idea to work would be great.
-Testing and feedback, help the idea to work on as many devices as possible
-Support, when the protect gets completed i would like everyone to spread the voice. if its a great idea then it should be heard.


Thanks for your Time.

 

[protozeloz]

reserved.....

 

[K Dotty]

Cyanogen mod is basically stock android with a few mods and tweaks. If doesn't have all of the bloatware that skinned manufacturer roms have so its alot faster and I think stock android looks better than sense, etc.... Its been compiled for a wide range of phones.

 

[protozeloz]

Cyanogen mod is basically stock android with a few mods and tweaks. If doesn't have all of the bloatware that skinned manufacturer roms have so its alot faster and I think stock android looks better than sense, etc.... Its been compiled for a wide range of phones.

I know about the cynamogen mod have it on my pone,where I'm trying to go with this idea is that there might be other methods for the companies to deliver stuff to the end user and the dev. many know that for example with blur the phone does not work the same when it as blur removed, thats because the 'blur' its being integrated a lot with the OS and in some cases seems to be a pain to remove...

 

[momentarylapseofreason]

So basically, you have no programming experience and I would hope that English isn't your native language.

Your best bet for now would be to sit back and watch those ahead of you and ask questions as needed.

 

[guitargler]

I think he's suggesting that any code that came about from this would get pushed into stock and hopefully integrated by Google. Manufacturers wouldn't tamper with it; rather, they would make their custom skinned Android (so HTC Sense, or Samsung Touchwiz, or MotoBlur/NinjaBlur) be separate. Phones would require more system space to accommodate for the backups, but it wouldn't have to be astronomical, as only the parts of the system that the skin makers actually modified would be in those recovery partitions. So then the recovery utility launched by the included app would pull all of the packages from whichever partition (recovery_SENSE, for example, or recovery_VANILLA for stock) and push them into /system. So the phone's system would have three total partitions: /system, which would be mounted by the phone during normal boots, /recovery_[whatever_skin], which would hold the manufacturers version of anything they skinned, including apps, frameworks, anything they added, etc, and /recovery_VANILLA, which would only hold the stock versions of anything in the /recovery_[whatever_skin] partition, plus anything the manufacturers took out.
Furthermore, if the partitions are all made big enough, they could future-proof phones. recovery partitions would hold the entire system, skin (or lack of skin) and all, then Google would be made responsible for pushing out the updates to the /recovery_VANILLA partition, keeping all phones up to date. People who ACTUALLY want to sacrifice features for the skin and possible other features could do so. And because everything is backed up to your Google account, there'd be no problems. Everything would get synced at first, but after that you'd be smooth as butter.

I think if this was implemented, and Google told manufacturers they had to do this, it would do a whole lot in the way of moving us away from skins. I think as Google updates are pushed out and manufacturers are updating far less frequently, more and more people will switch to their stock partitions, and, through ad information, manufacturers would realize the skins are wack.

 

[protozeloz]

So basically, you have no programming experience and I would hope that English isn't your native language.

Your best bet for now would be to sit back and watch those ahead of you and ask questions as needed.

I actually don't mind if someone takes this and makes something out of it... I don't even want the credit, but I as well will be working and reading as much as I can to get something working, I know this may be hard or complicated but if I see this being implemented and people enjoying it I'll be happy

I think he's suggesting that any code that came about from this would get pushed into stock and hopefully integrated by Google. Manufacturers wouldn't tamper with it; rather, they would make their custom skinned Android (so HTC Sense, or Samsung Touchwiz, or MotoBlur/NinjaBlur) be separate. Phones would require more system space to accommodate for the backups, but it wouldn't have to be astronomical, as only the parts of the system that the skin makers actually modified would be in those recovery partitions. So then the recovery utility launched by the included app would pull all of the packages from whichever partition (recovery_SENSE, for example, or recovery_VANILLA for stock) and push them into /system. So the phone's system would have three total partitions: /system, which would be mounted by the phone during normal boots, /recovery_[whatever_skin], which would hold the manufacturers version of anything they skinned, including apps, frameworks, anything they added, etc, and /recovery_VANILLA, which would only hold the stock versions of anything in the /recovery_[whatever_skin] partition, plus anything the manufacturers took out.
Furthermore, if the partitions are all made big enough, they could future-proof phones. recovery partitions would hold the entire system, skin (or lack of skin) and all, then Google would be made responsible for pushing out the updates to the /recovery_VANILLA partition, keeping all phones up to date. People who ACTUALLY want to sacrifice features for the skin and possible other features could do so. And because everything is backed up to your Google account, there'd be no problems. Everything would get synced at first, but after that you'd be smooth as butter.

I think if this was implemented, and Google told manufacturers they had to do this, it would do a whole lot in the way of moving us away from skins. I think as Google updates are pushed out and manufacturers are updating far less frequently, more and more people will switch to their stock partitions, and, through ad information, manufacturers would realize the skins are wack.

Indeed thats what I'm thinking... I don't think space should be much of a problem, especially on hight end phones.


When I posted this my fist idea was to give someone an idea I don't mind how you implemented or who you decide to work with (I'll probably just slow you down anyways)

 

[elegos]

Cyanogen mod is basically stock android with a few mods and tweaks. If doesn't have all of the bloatware that skinned manufacturer roms have so its alot faster and I think stock android looks better than sense, etc.... Its been compiled for a wide range of phones.

Basically stock? AHAHAH
It's all but stock... so many changes, have you ever run a stock Gingerbread or even FroYo recently? Way faster than CM. The truth is that ATM CM is just a candy ROM ATM with large phone models support.

I'd really like to see a stock rom for older devices - here is where CM is proud of. But it's not stock.

As of the application support, you may use my ROM Updater ( http://www.elegosproject.org/android-rom-updater ) to setup repositories of stock ROMs (and in a near future extra downloads like kernels, themes and so on).