Related
Is there a reason why the dev community cannot get behind cyanogenmod and still get donated to? Is there some kind of politics involved that will not allow this relationship? I just think I would like to see the effort into one project that is solid, without all the themes and "personal" touches you see with everything else.
In a word it doesnt seem like much progress is being made, except for some screenshots from the dude and an alpha build from eugene. If Eugene, Som, Codeworkxs thedudesandroid, and the rest of the vibrant devs worked on a gingerbread based cyanogenmod, it would benefit everyone.
Move me, flame me, just dont one line answer me.
Yours to change and modify:
https://github.com/CyanogenMod
Ideologies differ. Work ethics differ. I think a move like this would be destined to fail.
Have you personally experienced both Macnut and Nero? Both ROMS are outstanding. I think the more fragmented the ROMS are, the more ideas, experiments, and innovation will occur. I think to push devs to a single common platform would be both stifling and detrimental to the android modding community as a whole.
Besides, all the devs have the same problem... Drivers. Until we start seeing Gingerbread leaks, all devs would have the same stumbling block anyway, whether they are working as one, or separately.
i'm fairly certain all CM ROMs have been halted and work has been pushed to CM7.0 Gingerbread based. With the Nexus S (NS) being the same thing with a few minor difference to all the other SGS phones and the NS source being openly available for people, we should see a true Gingerbread CM ROM for all the SGS phones once they figure out the necessary changes to make our variants work. This time it should be easier, thanks to all the Devs who came before and figured out Samsung's ass-backwards way of doing things.
Time and patience will reward with the greatest Android ROM the world has ever seen!
angryPirate12 said:
i'm fairly certain all CM ROMs have been halted and work has been pushed to CM7.0 Gingerbread based. With the Nexus S (NS) being the same thing with a few minor difference to all the other SGS phones and the NS source being openly available for people, we should see a true Gingerbread CM ROM for all the SGS phones once they figure out the necessary changes to make our variants work. This time it should be easier, thanks to all the Devs who came before and figured out Samsung's ass-backwards way of doing things.
Time and patience will reward with the greatest Android ROM the world has ever seen!
Click to expand...
Click to collapse
This makes me moist.
d33dvb said:
Is there a reason why the dev community cannot get behind cyanogenmod and still get donated to? Is there some kind of politics involved that will not allow this relationship? I just think I would like to see the effort into one project that is solid, without all the themes and "personal" touches you see with everything else.
In a word it doesnt seem like much progress is being made, except for some screenshots from the dude and an alpha build from eugene. If Eugene, Som, Codeworkxs thedudesandroid, and the rest of the vibrant devs worked on a gingerbread based cyanogenmod, it would benefit everyone.
Move me, flame me, just dont one line answer me.
Click to expand...
Click to collapse
my question for you, is why does it have to be cyanogenmod? Youre asking all devs to collaborate to come up with one big super-ROM, yet it will still only be under the name of one developer, Cyanogen?? This doesnt make much sense.
So basically what youre asking is, since you PERSONALLY would prefer to run cyanogenmod on your phone, you want all other Vibrant devs to concede their own projects to assist your personal favorite developer with his project??
Why doesnt CM help with a new Team Whiskey ROM?? If your answer is because CM is more popular and has more development-power in the Android world, then you have answered your own question in regards to the "politics" that may be behind it.
I feel a lot of people (not necessarily the OP) just seek the "cyanogenmod" title to their ROM, without even really knowing what it is. They just hear the name thrown around all over the place and want to feel like they are in the loop; which is just mindless, in my opinion.
Its great to have several devs, with several different projects. It gives the average user (non-dev) options, and different things to choose from and try.
If you went to a car show, and every car had the same exact engine in it, what would be interesting in that??
what a communist suggestion
I, personally, love that there are many diff ROM's to choose from. I love having that variety. I prefer <tw> ROM's, just because they theme it pretty much how I would theme a ROM (and they scream), If I was even remotely capable of Dev'ing. Eugene makes an awsome ROM too, But not to my personal taste. On my G1 I always used cm ROM's, but the way they work at this point that's not possible for a Vibrant. So I guess what I'm saying is, I'm glad they're not all concentrating on one ROM because we would still be waiting... stuck with RFS !
I just want that Cyanogen bluetooth stack on a regular (sans Touchwiz) Galaxy S rom with TV out. The Bluetoouth stack is the only reason why I am using Cyanogen outside of the speedy OS.
Sent from my SAMSUNG-GT-I9000 using Tapatalk
I get what you mean but I have to say that I love flashing different devs roms & kernels, I would hate to be slave to one idea...I could have gone iOs for that.....get it iOs 4! I kill myself sometimes...
vibrant
GingerR2JL4
TopShelf10 said:
my question for you, is why does it have to be cyanogenmod? Youre asking all devs to collaborate to come up with one big super-ROM, yet it will still only be under the name of one developer, Cyanogen?? This doesnt make much sense.
So basically what youre asking is, since you PERSONALLY would prefer to run cyanogenmod on your phone, you want all other Vibrant devs to concede their own projects to assist your personal favorite developer with his project??
Why doesnt CM help with a new Team Whiskey ROM?? If your answer is because CM is more popular and has more development-power in the Android world, then you have answered your own question in regards to the "politics" that may be behind it.
I feel a lot of people (not necessarily the OP) just seek the "cyanogenmod" title to their ROM, without even really knowing what it is. They just hear the name thrown around all over the place and want to feel like they are in the loop; which is just mindless, in my opinion.
Its great to have several devs, with several different projects. It gives the average user (non-dev) options, and different things to choose from and try.
If you went to a car show, and every car had the same exact engine in it, what would be interesting in that??
Click to expand...
Click to collapse
Agreed. It seems to be the "you want what you can't have" theory. It's going to be funny when there is finally a CM ROM and all these same ppl that wanted it are going to wonder why CM is so plain looking and isn't themed up. It's an endless cycle. CM offers support to multiple devices, which gets their name out there. But I can promise you if you've ran ROMs such as Nero + voodoo, even the best running CM isn't going to "blow it away" in performance, maybe some fun features, but that'll about do it.
I'm satisfied with TWs stuff. All I'm hoping for is that we can get drivers written to do our own ASOP roms, so we can one day have 2.3 and beyond.
im curious about this as well and being that i have no clue, i feel completely authorized to put in my .02 that i thought the primary reason we dont have cm for the galaxy was due to lack of aosp/drivers...
LOL, you sad bunch of folks think I have never flashed a rom on the vibrant? Sure I have, but they are all roms based off of samsuck files, with a theme pushed on top. This requires some skill and understanding, but it does not make you a "ROM D3V"
I am not in any way trying to push everyone to cyanogenmod, I am trying to get the "real devs" to work on things like GPS drivers and such as a whole, to benefit everyone, you think the tricks we learn as a group you cannot then use as an individual? You cannot say I am communist (lmao) because I want the devs to work together, I suppose that what people say about XDA is true, the users who are flaming me make it unbearable to have a real conversation. I mean just look there are several "FANBOY" posts already, and we are on post 13. No wonder the real devs ficking hate XDA. The sole reason I personally like cyan is because of the testing that it goes through, to make sure embarrassing bugs dont happen often. He has developed a rom for my G1, then both my Mytouch's and just miss running it on my vibrant, thats all. My G1 is sitting here running CM 6.1.0 and my phone still sits here on Ginger Clone, the best there is right now.
FYI when there was lack of drivers on the Dream/Magic someone re-wrote them, mmkay?
It has always seemed that the devs share fairly well. While they don't work together on one project, they share what is needed and form teams of likeminded people to push out better and better products. If you want to see what happens when you get everyone together and make them all focus on one big new release look at samsung itself. These small teams can operate with greater freedom to build and release mods and roms as they see fit. Xda is about sharing info and improving our machines. Would we really want to have gingerbread today without all the options and flavors that different dev teams put together. If you say yes, that's fine, but I like the variety and am happy to wait for what's next.
Sent from my SGH-T959 using XDA App
Moved of: Samsung Vibrant > Vibrant Android Development
To: Samsung Vibrant > Vibrant General
CM is not really comparable to the XDA devs' ROMs. CM is a complete ground-up build from AOSP. Nero, Macnut, etc are not; they are mods of existing unofficial Samsung ROMs. (Not to imply that Eugene/Sombionix et al's work is anything less than quality).
mindaika said:
CM is not really comparable to the XDA devs' ROMs. CM is a complete ground-up build from AOSP. Nero, Macnut, etc are not; they are mods of existing unofficial Samsung ROMs. (Not to imply that Eugene/Sombionix et al's work is anything less than quality).
Click to expand...
Click to collapse
Yeah, that's the thing. The skill set involved in getting AOSP (and the rest of CM) building properly is a different skill set than modifying a Samsung released ROM.
The approaches are almost entirely opposite - whereas most ROMs here take what the vendor provides and replace the junky bits with stuff that works better, the AOSP-based ROMs such as CM start from a bare bones google source repository that never had any of that junk to begin with.
Both approaches have their merits. As should be obvious by now, the former results in much more rapid progress since you can start right away with a working build from Samsung. The latter approach can take substantially longer, since you don't have a working base to start from (especially with a device like the SGS, which has hardware very different from most CM-supported devices).
Eugene had an AOSP 2.1 rom pretty well built. Needed some kinks worked out, but there didn't seem to be a lot of interest because all everyone wanted was froyo. I'm sure we're probably see at least a couple of AOSP efforts if/when froyo officially drops.
angryPirate12 said:
i'm fairly certain all CM ROMs have been halted and work has been pushed to CM7.0 Gingerbread based. With the Nexus S (NS) being the same thing with a few minor difference to all the other SGS phones and the NS source being openly available for people, we should see a true Gingerbread CM ROM for all the SGS phones once they figure out the necessary changes to make our variants work. This time it should be easier, thanks to all the Devs who came before and figured out Samsung's ass-backwards way of doing things.
Time and patience will reward with the greatest Android ROM the world has ever seen!
Click to expand...
Click to collapse
Yep, codeworkx and the CMSGS team have stopped worked on 6.1 and (along with Supercurio and others) are working on an AOSP Gingerbread port for SGS.
It makes sense--no point in continuing to try to build a 2.2 without source when the 2.3 source is already out.
This was just on my facebook :
MIUI ROM for Samsung Galaxy S
Dear owners of i9001, MIUI ROM for Samsung Galaxy S doubt of the interest of the port of MIUI ROM.
There will probably be not port to the i9001 because this phone is considered as a variant of the Galaxy S i9000. The reason is simple: there are not many users compared to the Galaxy S.. The only way is to make an unoffical port.
Thank you to stop ask questions for the i9001 or regional variations.
·
Now the only hope is an ICS ROM !! official or non-official
It has already been said that if there's no CM for the GT-I9001, there won't be any MIUI release either.
Bastards...after all they are not doing this for passion, they are doing this for where are more "fans" so they can have more money from donations.
Sent from my GT-I9001 using XDA App
kellermanv said:
Bastards...after all they are not doing this for passion, they are doing this for where are more "fans" so they can have more money from donations.
Sent from my GT-I9001 using XDA App
Click to expand...
Click to collapse
You cant judge a team of developers (in miui's case even a business with employees) when you dont know anything about them? Oh, and donations wont make a living for any developer, not even when their custom-roms are for multimillion selling devices only.
First, lets get some things clear about miui, and why I dont like MIUI and the people behind it: Miui is made by a chinese business with a couple of 10's of employees. Their miui source is mostly based on cyanogenmod 7.1 and some other aosp gingerbread parts. A major difference with team cm, is that miui is closed source (and thus abusing team cm's efforts in building cm roms, mods and tweak, and not sharing their own miui enhancements). Their goal is like every business: making profit, which is improbable / impossible by only making roms and depending on donations, so they're active in other (software) markets as well. They even released their own smartphone with miui preloaded.
Next to abusing one of the fundaments of linux (sharing, open source), they got a distant iOS-like theme, which makes it almost impossible to modify anything (modifying is a fundament of android). Personnaly, I dont care about miui not being ported to sgs+, and since there is no cm yet (hope yarde will get it working!), they cant port it either, since they'll need a cm kernel and some other things to work from..
Sent from my GT-I9001 using XDA App
hi everyone,
As you see the topic its about AOKP team which they have a new version of ICS porting method. First they started moding the devices like Nexus-S and Galaxy nexus. After succeding they came up with other new devices and ported ICS base rom to other devices such as HTC, Xoom,Galaxy Tab.Today i talked to Roman the Dev guy from this team about our beloved TF.Unfortunately he said they wont port this rom to TF. I just started this thread to ask this team for porting this rom. I think if they see our requests they might put their efforts to make it work on our devices. Im currently using build 23 of this rom on my Nexus-s.it comes with lots og built in features.
here is the link for the website.Head over it might be interesting for you.
http://aokp.co
Sent from my Nexus S using xda premium
You said yourself they already said no. Respect their decision and leave them alone; if you don't like the decision you can port it yourself.
From their point of view, I can see why they said no. We will--eventually, one day--get an update from Asus themselves, which will satisfy 99% of users. The remaining 1% will get mods based on the Asus stock roms, just like they do now. There's also already a partially completed port underway by somebody else.
Why would they waste their resources on the TF101 when there are plenty of other devices that have no ICS port, and no chance of getting one from their manufacturer, which they could work on?
Actually, the correct guy to ask for a port is this guy @ProTekkFZS . He recently went on a spree porting aokp to many devices. Roman only port to devices that he is currently using which are gal nexus, nexus s and gal tab.
Sent from my Galaxy Nexus using XDA App
if they dont want to port it got to respect that decision but if they would i would be sooooo happy a really great rom would use it
roman recieved a htc sensation from rootzwiki and he hasnt even ported it there yet so i wouldnt hold my breath dude... although it would be epic...
Sent from my Revolver Powered Asus Transformer
there is a plan for cm this is nothing compared to that and then there will be miui
pashinator said:
there is a plan for cm this is nothing compared to that and then there will be miui
Click to expand...
Click to collapse
1, MIUI won't come to tablets until Xiaomi makes a tablet UI version
2, CM is nowhere yet for the TF
3, Currently AOKP provides more control and access to things than CM. It was stated Cyanogen by himself that CM9 will NOT contain the old CMParts style settings, but rather have them in their respective submenus. AOKP goes on the CM7 way, having a separate app what can switch controls on-off. I'm already using it on my phone (ZTE Blade), and it's currently more stable than CM or even an AOSP build.
fonix232 said:
1, MIUI won't come to tablets until Xiaomi makes a tablet UI version
2, CM is nowhere yet for the TF
3, Currently AOKP provides more control and access to things than CM. It was stated Cyanogen by himself that CM9 will NOT contain the old CMParts style settings, but rather have them in their respective submenus. AOKP goes on the CM7 way, having a separate app what can switch controls on-off. I'm already using it on my phone (ZTE Blade), and it's currently more stable than CM or even an AOSP build.
Click to expand...
Click to collapse
1, Miui for tablets could become a reality without Xiaomi since they decided recently to change their code in Open source...so maybe one day
2, not yet, sure, even if CM has already talked about TF cm9 to come
3, here i think it really depends on the phone : with my Nexus S, aokp is pretty stable and smooth, but not as some other aosp (Pete Alfonso's) or CM (fitsnugly's kangs) for example.
Let's first get next Paul's builds, Asus's release then, and CM9 eventually.....at this point we all should be Fulfilled.
kptnk said:
1, Miui for tablets could become a reality without Xiaomi since they decided recently to change their code in Open source...so maybe one day
2, not yet, sure, even if CM has already talked about TF cm9 to come
3, here i think it really depends on the phone : with my Nexus S, aokp is pretty stable and smooth, but not as some other aosp (Pete Alfonso's) or CM (fitsnugly's kangs) for example.
Let's first get next Paul's builds, Asus's release then, and CM9 eventually.....at this point we all should be Fulfilled.
Click to expand...
Click to collapse
1. First of all, they haven't gone totally open source yet. And to include a tablet overlay, that would be a huge work. Not just graphics, but compatibility, screen issues, alignments, and such.
2. There will be a CM9 build, but only after CM9 is stable enough, and Asus released theirs so Bumble-Bee, RaYmAn, Roach, and the others can make a working one. So no CM9 for now
3. Yes it depends on that too, but show me any point of CM9 having more feature than AOKP. AOKP derives directly from CM9 sources, with the additional apps and features, plus fixes. So I consider it more mature.
Paul already published his sources for the TF, so we could easily grab his tree, change some stuff for AOKP, and make a build. I don't have quite the PC for such building processes, it would take days, and my electricity bill is already over the limit - so I can't do it definitely. But if there's someone else willing, everything can be made
fonix232 said:
1. First of all, they haven't gone totally open source yet. And to include a tablet overlay, that would be a huge work. Not just graphics, but compatibility, screen issues, alignments, and such.
2. There will be a CM9 build, but only after CM9 is stable enough, and Asus released theirs so Bumble-Bee, RaYmAn, Roach, and the others can make a working one. So no CM9 for now
3. Yes it depends on that too, but show me any point of CM9 having more feature than AOKP. AOKP derives directly from CM9 sources, with the additional apps and features, plus fixes. So I consider it more mature.
Paul already published his sources for the TF, so we could easily grab his tree, change some stuff for AOKP, and make a build. I don't have quite the PC for such building processes, it would take days, and my electricity bill is already over the limit - so I can't do it definitely. But if there's someone else willing, everything can be made
Click to expand...
Click to collapse
1 & 2, i agree, that's sure.
3, aokp has indeed for now more features than cm9 and kept cm7 idea with nominated menu, which is more than rich of full customization possibilities. My point was in fact on the stability, efficiency and smoothness : there are, for nexus s at least, aosp roms and some cm9 builds which are better than aokp. So not in terms of "quantity" but of a certain idea of quality. Certain idea, because it is of course a question of point of view. That said, i love Roman's work.
I wish i could build on Paul's and Roman's sources for our beloved TF, but even if my electricity bill could eventuelly bear it (for a time), i have neither the pc, nor the knowledge to do so, which is worse .....here's just a very greatful and curious user....
Hello Folks,
I am a Recognized XDA Developer and I work on Cyanogenmod for Samsung Galaxy SL I9003 which is an exact similar device to Galaxy Tab P1010 (TI OMAP3630).
We have got fully working CM9 and CM10 on Galaxy SL, with few minor issues with video recording and laggy interface. However, we are working on porting the new 3.0.8 kernel that was released on omapzoom. This new kernel would help us resolve issues that we have been affecting ICS and JB releases.
So far, we have managed to get the kernel booting with few basic stuff like Touchscreen, Panel, Audio, Keypad, Vibrator working. Galaxy SL is exactly similar to Galaxy Tab P1010 WIFI and it essentially shares the same kernel and I suspect that most of the userspace stuff also should be the same. I was informally asked by cdesai if I was interested to develop for this device, but I had to turn my back since I wasn't really having the time for it.
However, since we are working on a new kernel for Galaxy SL from scratch, I would really like to take the initiative of making something useful for P1010 too, keeping in mind the small user base for Galaxy SL, we thought our work could be useful for P1010 and would benefit more people.
We would like developers working on P1010 to come forward and let us know the current status of development on this device (Kernels, Custom Roms, Attempts at CM, etc), so that we could plan something accordingly. Also, we would be interested to know how many people actually own this device and would like to have CM over it. Let's use this topic as a playground!
Sources for Galaxy SL
Stable CM9 and CM10
Kernel: https://github.com/teamhacksung/android_kernel_samsung_latona
Device: https://github.com/teamhacksung/android_device_samsung_galaxysl
Experimental 3.0 Kernel
https://github.com/dhiru1602/android_kernel_samsung_latona
Thank you!
Let's do it people, I'm willing to help dhiru as well.
I'm in too
@dhiru (Y)
This is fantastic news, and thanks for considering the P1010 as everywhere else I've looked hasn't really got anywhere. While I'm afraid I won't be able to help with any of the development (I wish I could, but I'm too busy as it is), I can use my device for testing. Keep it up, and I can't wait until it's all sorted.
Personally, I'd love to have any version of CM on this tablet, as Android 2.3.6 is looking really dated now, and the interface is laggy compared to that of Android 4.1 devices. I've upgraded to CM10 on my Galaxy S and it's so much smoother than it was, I can only hope the same is possible for this device, as it's certainly capable.
Also, I know Motofoca over on the MadTeam forums was working on it (which you already know, most likely), but he's not mentioned anything towards progress in a while. I can't post a link though, considering I've got less than 10 posts, so you'll have to google it.
Any help I can give is gladly offered, now when it comes to coding I am rusty... In fact I think the rust has extra layers of rust but know what I am looking at and can spot the bugs and offer suggestions.
I have two of these and still think the actual build of them is excellent so would love to have some decent internals
Sent from my LT26i using xda app-developers app
Seems like there are not many who own this device. That's sad.
dhiru1602 said:
Seems like there are not many who own this device. That's sad.
Click to expand...
Click to collapse
I'm owning a P1000 too (as per the question of the OP) and I would really like to have a current CM 10.1 release with kernel 3.0 on it... I'm a java developer with some C++ background but I didn't have the time yet to dive into android development (neither high nor low level)..
If there is anything to test or provide info about just ask..
dhiru1602 said:
Seems like there are not many who own this device. That's sad.
Click to expand...
Click to collapse
P1010 here !
Greets from Perú
dhiru1602 said:
Seems like there are not many who own this device. That's sad.
Click to expand...
Click to collapse
I have a P1010 and I also like to help!!!
I wanna help too!
P1010 here! Can't Dev but will gladly test!
Sent from Razr Maxx running Full Throttle Killer Bean
I've got a 1010. I'm a themer, not a dev though..
i have it too. i'am an Indonesian.
friesoft said:
I'm owning a P1000 too (as per the question of the OP) and I would really like to have a current CM 10.1 release with kernel 3.0 on it... I'm a java developer with some C++ background but I didn't have the time yet to dive into android development (neither high nor low level)..
If there is anything to test or provide info about just ask..
Click to expand...
Click to collapse
I don't know whether this was a typo or not, but you can get CM10 or CM9.1 (stable) for the P1000 already. Just look on the cyanogenmod site for the P1. This is for the P1010 which is the WIFI only version of that tab and doesn't yet have a release of cyanogenmod for it.
dhiru1602 said:
Seems like there are not many who own this device. That's sad.
Click to expand...
Click to collapse
I've been waiting for this, I can test on my p1010
dhiru1602 said:
I am a Recognized XDA Developer and I work on Cyanogenmod for Samsung Galaxy SL I9003 which is an exact similar device to Galaxy Tab P1010 (TI OMAP3630).
..
Also, we would be interested to know how many people actually own this device and would like to have CM over it. Let's use this topic as a playground!
..
Thank you!
Click to expand...
Click to collapse
Hi, I have it. I also have some experience with kernel on Omap4 (I developed for 3.0.x and 3.2.x), but very little time to share at the moment.
Please post here in this thread any update or request.
Thanks
P1010 here also. Plenty of processing power and a website for storage and distribution...
Sent from my VM "Evo 3D" using 2ʞןɐʇɐdɐʇ .
I'm also willing to test. These tabs are great, just not many developers working with them.
p1010 with cm10
Looking forward to trying their huge creations from Ecuador ... CMs for the P1010, do not let this device die. Sorry for my English, I hope this well written ..
Hello guys, I also have a P1010! maybe I can help you as a tester, I have experience with flashing and rooting
CM 9.1 development might be slowed down or stopped for personal matters of devs. But can't we get AOSP 4.0 at least. I don't think it would be too much hassle to compile AOSP 4.0 as the drivers are already for that.
There are still many great devs in our SGY forum. Can't we try a little harder ?
spacecaker already compiled it and the touchscreen didnt work so it was abandoned and they moved onto cm9
the drivers were for graphics and not sound and so on
marcussmith2626 said:
spacecaker already compiled it and the touchscreen didnt work so it was abandoned and they moved onto cm9
the drivers were for graphics and not sound and so on
Click to expand...
Click to collapse
problem is, by the time i get ics in my first and favorite phone,i might already have a new phone(with kitkat)…
day by day,devs are abandoning our forum. and we keep waiting and waiting and waiting and waiting…
I'm not blaming them or creating any pressure on the dev but we just keep waiting…
madboy777 said:
problem is, by the time i get ics in my first and favorite phone,i might already have a new phone(with kitkat)…
day by day,devs are abandoning our forum. and we keep waiting and waiting and waiting and waiting…
I'm not blaming them or creating any pressure on the dev but we just keep waiting…
Click to expand...
Click to collapse
simple answer to that - do it youself lol
some things just cant be done and others cant be done overnight and may take months or years to work out
even if the galaxy y does get a stable ics it is still only armv6 which will have limitations in terms of apps and games
If you want the latest now best buy a new phone because you will be waiting a long time for this phone and even then it probably wont be able to do what you want of it
As said before Aosp is like much harder then CM
CM has optimized code for lots of devices.
although cm9.1 seems dead we are still trying our best to solve and fix stuff
it isnt just something that can be done in a month or such
Sent from my Acer S500 CloudMobile