Hiya everybody!
I would love if someone could give me directions on where I can get good ROMs for flashing my brand new Artemis...
I'm brazilian, but I'm looking for a ROM in english with the best functions that people could get together....
I'm totally new to modding in here, tho I'm sorta pro in modding Motorola's MotoMING phone (my last one)
So if anyone could help me with directions of a newbie guide, I'd be glad....
I could write a newbie guide myself later on....when I lose the newbie status LOL
Check here for tips http://forum.xda-developers.com/forumdisplay.php?f=362
There are also quite a number or ROMs in there too.
Although I would definately recommend this one.. http://forum.xda-developers.com/showthread.php?t=365312 .. great speed, very light so you can add all your own apps and customize it how you like. Generally speakingm, after flashing alot of ROMs to my Orbit, I tend to stick with Meschle's ROMs and usually stick to his latest Vanilla. Although as I say there are alot of others, depends what your looking for from the ROM.
Any other questions Id be glad to help. I also have quite a collection of prgrams n customiations n stuff if your looking anything.
Thanks a lot for the hand!
It surely will come handy! I got the USPL to go over the CID locking system....
The carrier problem can be solved by the carrier itself, at least nowadays.....
To tell the truth, I'm in need of some tutorials on the best programs to have, what kind of stuff fits well in it...
I work with game design, and I'm starting to develop on python....I was wondering if there is anyway to run python programs in it too...
Last but not least, how much knowledge is necessary to work with Artemis?!?!!? LOL
Hmm unfortunately I dont do programming n such, i think you probably be better off asking those questions in the artemis developement / hacking section
If you were to develop Pocket PC applications, you may use eVC (free) or VS2005/8 (more expensive)
No idea about pythons.
How much knowledge? Probably nothing or as much as it is needed to read english. All you need is to experience and experiment to learn.
Regards,
Carty..
@fubofo
Thanks for answering again, man! I know that not everyone is a fan of programming stuff....
I got the ROM you said you were using and I'm gonna flash it today...hope it works and I don't end with a 15 hundred bucks brick....
@Carty
When I said knowledge, I ment time spent studying stuff made for it and etc...but still the ability to read english is way too complex for some people in my country....
I'll take a look at the eVC and see what can be done in it....
I have Eclipse's SDK and Visual Studio 2008 here....any of them is good for it?
hey guys,
don't know if this is the right place, but because Chefs should read this in first place, the general board seems not the right place either. But this is the same problem with application development either, so developers may read and post too. So not to bother you all furthermore, i'll start right through:
I wonder about
- 50 different ROM development projects (what could be a good sign, if this would not be)
- 48 concurenting projects which do not share know-how (reading statments like: "I will not tell you, what i did to the ROM to archieve...")
- 98 times uncoordinated simultaneous identical work is done(including, not concluding, tools, tweaks, apps, complete roms ...)
Why do we behave like the people because of which we've started this hole thing here? We do keep know-how secret like the builder and oem manufactorers do or did. Instead we should discuss our know how publically and organize our work and efforts as a community and not as individuals. There is enough space for every way of thinkin inside organized structures left (e.g. speed or stability optimized roms, ...) - but what the one project discovers or experiences should be known by the other projects too, that's what is called synergy. We all could profit. Thats the sence of a community. This feeling i miss here a bit to be honest.
And to get concrete i'd suggest further organizational investigations. Some guys did start some already good ideas like a complete guide to dumping, cooking, etc. or a thread where design stuff is listed and linked centrally, or for example the thread where ROM's get tested for speed and space independently. We should take this last idea further and add information to this comparison, about what was done to this ROM's to archieve the projects defined/assigned goals.
This way we could test RoM's concerning to manipulations and would be able to find out what is really happening in our systems (denpenency of [OEM]pakages) and what we can really do to improve a certain goal of tuning.
Furthermore we would not do identical work a thousand times, and so would be able to serve an easy diamond-click-kitchen to the community and last not least to ourself's.
There are not that many intentions possible in RoM development:
Speed
Space
Stability
Gaming
Office
Weird?
... ?
We should now start a thread (and maybe a database) to get our know how organized and start workin together instead of against each other. We (including, not concluding, me ;-) all do owe some guys here in the forums a debt of gratitude for their work and efforts. I'm happy to see that some people are donating, so some guys get a beer payed which is a nice honoration (but no payment). The more i'd be happy if not two developers do the same work simultaneous. Let's get that organized!?
So now i did state some philosophy, followed by some concrete input - now it's your turn to do so ;-)
Best regards
peet
I totally agree.
I do agree with you but this behaviour is found NOT JUST HERE, but in almost all organizations regardless of occupation. Some of us work as a Team more then others but individuality and uniqueness is part of human natures need to be competitive. I really wish we weren't like this.
The purpose for me on this forum is to share my knowledge on to others. I believe most people like to do the same. I think if there are secrets here, then I believe they are kept secrets for branding purposes. To make a name for themselves and to distinguish themselves from the rest.
Based on the post that I have been reading from ROM Threads, I always see chefs thanking each other for sharing. So sharing is happening but maybe not in the most efficient way.
Hmm....hope all these feelings being shared are not taken the wrong way here. Just me thoughts from Psych 101 and my experiences.
band27 said:
So sharing is happening but maybe not in the most efficient way.
Click to expand...
Click to collapse
I totally agree.
seeya
hallo,
i have a little problem to understand your thread. 99% of not-understanding is my english and 1% is your long text without any .. ähhm .. development.
can you say me in one sentence and no more than 10 words what you want?
okokur
I'd like to take the opportunity to say thanks to the majority who do share. A couple of months ago, to flash meant only showing off, and cooking was just for a good meal. With the upgrading, cooking tutorials, wiki and dozens of helpful replies to questions, I'm on my way to cooking my first ROM. Just wish I knew more to contribute something more technical myself. This board has some of the most helpful threads I've found. Thanks once again.
I agree, but there are a couple of problems with this.
1.) some people just don't want to work in a team.
2.) today, those who flash on a daily basis know all (or at least their favorite) Chefs by name, and what their ROM contains. This would be lost.
3.) continuing the previous thought, Chefs would lose motivation, if their name was one of 38 people who made the ROM, in the "credits".
4.) donations. would you spare 5-10$ each chef who contributed? that'll be one pricy Rom
I'm sure there are other problems with this as well, these are just of the top of my head..
but, I do support the idea, the development looks unefficient. At least from a users' point of view..
I've just reread your post, maybe i didn't quite get it. Do you mean something like a thread where all the new knowhows would be listed (though, WIKI is probably better).
slovoflud said:
though, WIKI is probably better
Click to expand...
Click to collapse
That's exactly what I thought after reading the opening post
A wiki doesnt force anyone to do anything, but those who want to share their knowledge do have one central place to do so. Probably would reduce the amount of 'stupid' questions as well, or am I the only one who doesnt feel like searching through a ****load of topics for answers
I really like this idea
I hope that rom developers starts working together, providing even better roms for the users
that would be great!
yes shure, wiki would be the right place to centralize know-how, the problem with the wiki is that most information doesn't get there. I mean, there is no board around containing this know-how that xda does. but this know-how must be searched first in thousands of threads and millions of posts. and that is hard work,guys.
i just changed from a Mteor to a Diamond and had to invest several days (or have it been weeks?) to get the story in the diamond wiki/boards. one problem is that a lot of outdated information is found and second that information is split that hard. and likewise know-how is split apart.
then i realized most times when i searched for some information, i found hits in kaiser or raphael or somewhere else forum. too there seems to be organized projects workin together in those places.
In Diamond board only few kitchen are found, and not really a lot information about them either. I tested some, but only one was able to build a RoM out of the box. And i remembered Kaiser kitchen and wondered why this is not possible here likewise. While searchin for information i had to realize that here is no kitchen found documented enough to start building my own RoM in a nutshell nor in 3 days, possibly in a week but realistic it'll be in a month maybe. all that just because i wanted my next device to be theftsafe (because providers do everything to keep that thing running as nobody does something [what shure would/and was possible] against stolen devices - no, they do not get excluded from networks (except very few providers) - nor do they get excluded international or worldwide. You may think now, okay then let your device be trackable through services like PiCO. Even that is ratted or hindered by providers, but that is another story.
About the money mentioned above: I was lost in the opinion i would be surfin a community here, which is something where money does not exist really. I am glad that people did donate for a bricked chefs device for example, and i appreciate donations to well doing developers and chefs, but this can't be a point in discussing a communities life or behaviour. But if you are thinkin this way (and i still don't know what you want here then), then please think a step further and realize that: If you offer (maybe as xda-organization or other) a workin kitchen for daus, where contents and trimming can get selected, licence information can get added and that all gets build in a "personalized" RoM, MAN a thousands of people would be even willing to pay a hundred bucks for that. And i bet even on donation basis there would be enough money to share. But back to community.
Some ingenious anonymous teacher did ask me above, what i'd want then, in one sentence. I can tell ya - i want a snicker right now. Thanks for your contribution to the community development. It's that helpful as those "you should use the search" statements of people tired of tellin people same info twice, while not gettin tired of tellin people that they would be tired of them askin tiring questions. Ey guys you really bore, ääh get me tired ;-)
But to get concrete again, i think because of the wide range of device configurations and languages it would be good to develop ONE kitchen together, where it is possible to select a source for building freely (e.g. your own RoM, a Chefs RoM, a providers RoM, or whatever), then give possibilty to change language, select tec. specs like pagefile, etc., select packages to exclude, apps and licences to include, select design patches, CFC and other tweaks, select tweaks and last not least burn your RoM.
That'd be kickin ass guys doesn't it?
I know it would nice to have just one ROM developed, but then again this is reality, people have different preferences. I am sure Chefs share their recipes between themselves.
anyway, u guys may wanna check this out
http://forum.xda-developers.com/showthread.php?t=469420
ervius have done a fine job there.
Kudos.
I completly agreed with your point. Ive seen a lot of ROMS from wanabe cheffs and others that are from great chefs which enhance the OS deaply. Its sad to see comments that not help in the evolution of our devices. Ive not many Mods around, perhaps most of them got their hands on the HD.
On the other hand everyone must be able to post any Cooked ROM they want, but they have to make sure that something is different about othe developements, like Language, or included APPS or particular tweaks.
the way i see it - MOST chefs don't do cooking for public... they cook for their own need and according to what they like - then they share with the public... there's nothing wrong with that... and they don't need to share anything...
and i have noticed they always help you out if you send them a private message.
my two cents
cloudedhopes said:
the way i see it - MOST chefs don't do cooking for public... they cook for their own need and according to what they like - then they share with the public... there's nothing wrong with that... and they don't need to share anything...
and i have noticed they always help you out if you send them a private message.
my two cents
Click to expand...
Click to collapse
I used to think like that too, not anymore.
Vise versa.
If you read any thread with a 'popular' ROM, it's easy to see that it's not made for Chefs personal use( perhaps it was originally, but then it becomes a project).
hi all,
first i have to state that i shure do not want to force anybody to nothing. but i see too much people doin identical investigations. therefore i wanted to ask for others opiinion.
somebody sayed, that people might not want to work together wich sounds kind of weird in a community while shure nobody gets forced to share, equal if know-how or work. and somebody said that chefs want to read their name above their work or thdy would loose interest to do something. if those peoples interest or motivation is only to distinguish themselfes it would be sad, but no prob-let them do so on their own.
me would like a ROM without my name, but which is realy coool a lot more.
so first point would be, that all chefs write their know-how down in the wiki, so we can see which way we should start making a universall ROM which can then get tweaked and ppersonalized individually but the base is always the same for all. if the base is really good, all people could profit from that BaseROM!
at the moment i cant see which packages are corresponding to others and cant get removed easily. tooo it would be nice if nataly chef would tell us how he did free that much space, e.g.
maybe some chefs are willing to join, so we start a real universal RoM-Kitchen?
i red ervuis thread only short, but that sounds in the right direction, i'll contact him and ask for support.
the main thing first would be to get real good structures (like ervius started) to build a minimum basicRoM which then can get extended - and we need some more input about flash/nand/rom/pagefile/etc use and manipulation.
lets do this organized and structured not to do the same things a hundred times, and to avoid all those incompatibilities between apps found here (in comination a lot even common apps do interact and the result over both/all is a non working configuration. therefore a "standard" should get found for tweaking, cooking and applications too.
how about that?
hallo,
i have a little problem ...
i asked you what you mean and wish the answer with less than 10 words.
you want so much from other people but you give nothing. if i read your thread at first time, i think about you, that what you write is not that what you really want. i think you have problems with cooking and you hope on an easy way become solution.
one kitchen means, one way to extract, one way to cook ... like a one way with no return. if you have trouble with this one kitchen, nobody can or will help you.
i flashed my first pda three years ago, now i have pda number 4 and i cooked my own roms. the reason, why i dont share it, i used original buyed software by softmaker, coreplayer and sktools with integrated registration-keys/methods. this was orig.software and cant be for sharing.
i dont think, that i can learn this things with one kitchen, with one group, with one project. i have to thank for so much people, who spend nights of nights alone for cooking and sharing.
and if i can help somebody, so i do it. but in xda-developers it was not so easy to help someone, because there so so much people who was faster than me ... much much fuster. god safes the "aloning".
Well, okokur, you have a point, but only to a certain degree. You say about bought licenses, that shouldn't be shared. Fair point, but be consequent, and look further. From the legal point of view, 99% of cooks don't write the code - they only manipulate dumped software - and it's hard to say if this is legal. Sooooo... what I'm pointing at?
That this way or the other, everybody is to him/herself. I only don't understand why some chefs are locking their roms against uncooking - it's like you stole a car, and put an alarm on it against thieves.... Ridiculous.
All cooks should take example from people liek CT or mondilv, who share openly their develpoment. And that's the way. If you are just a bit inclined, you can start cooking yourself. If you are not, you will lazily wait for a rom done for you, and complain about what is in rom, what isn't, etc..
So - my advice/opinion - you will never get cooperation like you wish, because that's human nature. But it would be enough, if cooks would leave their roms open - then people who want to learn, would learn.
I can only agree... for what I can do due to lack of time I always publish the full kitchen source in my/our repository, so the rom isn't just opened but I publish the full kitchen tree with all scripts almost commented and/or other useful stuff
If I can help in other ways please just write down a line
bye,
davide
mjaxa said:
Well, okokur, you have a point, but only to a certain degree. You say about bought licenses, that shouldn't be shared. Fair point, but be consequent, and look further. From the legal point of view, 99% of cooks don't write the code - they only manipulate dumped software - and it's hard to say if this is legal. Sooooo... what I'm pointing at?
That this way or the other, everybody is to him/herself. I only don't understand why some chefs are locking their roms against uncooking - it's like you stole a car, and put an alarm on it against thieves.... Ridiculous.
All cooks should take example from people liek CT or mondilv, who share openly their develpoment. And that's the way. If you are just a bit inclined, you can start cooking yourself. If you are not, you will lazily wait for a rom done for you, and complain about what is in rom, what isn't, etc..
So - my advice/opinion - you will never get cooperation like you wish, because that's human nature. But it would be enough, if cooks would leave their roms open - then people who want to learn, would learn.
Click to expand...
Click to collapse
you are right.
i think, i can share my rom without buyed software ... but for diamond there was so much roms, thats no needed share a rom without any interesting features.
recooking roms not possible ... for flasher only its enough. for cookers exists a trash-folder on desktop
cooperation like my wish ... i am to old for other oppinnions so i respect other oppinnions for 100%. (its reading like type mismatch error )
if i start with flashing and later i want cooking but that was to much infos and to much rules for cooking ... that i wish ONE KITCHEN with GFX-USING by klicking "KLICK-KLCK" and NO-ERRORS and NO-BLACK-SCREENS ... And if i read this thread the first time, i see me three years ago
i understand peetx for 100%
Hey there,
I'm another guy who's been creeping around the board for the last month and have been eager to modify a ROM to my own needs.
Basically it comes down to that i would love to have the ability to take a modified ROM and rip out some of the parts i do not want or use or for whatever reason.
For like the past two hours i've been trying to google tons of sentences and i heard the term "kitchen" dropped alot, but alas. I could find no more info then the plus-member-kitchen-deal from modaco...
So now i'm wondering, How -does- one modify a rom. Are there any tools available for my wishes. (If yes, can you name any? If no, what skills are required?)
I need a good shove in the right direction, but i dont feel like pm-ing a random rom developer, just because im a whining ***** about some usually small aspects of the otherwise great rom(s).
Removing apps/widgets from a rom really isn't difficult.
If you PM me with exactly what you'd like to remove, I'll explain in full
Cooking ROMS
Annihlator said:
Hey there,
I'm another guy who's been creeping around the board for the last month and have been eager to modify a ROM to my own needs.
Basically it comes down to that i would love to have the ability to take a modified ROM and rip out some of the parts i do not want or use or for whatever reason.
For like the past two hours i've been trying to google tons of sentences and i heard the term "kitchen" dropped alot, but alas. I could find no more info then the plus-member-kitchen-deal from modaco...
So now i'm wondering, How -does- one modify a rom. Are there any tools available for my wishes. (If yes, can you name any? If no, what skills are required?)
I need a good shove in the right direction, but i dont feel like pm-ing a random rom developer, just because im a whining ***** about some usually small aspects of the otherwise great rom(s).
Click to expand...
Click to collapse
You can't go wrong with using the CKDroid ROM if you are just looking for a custom ROM, however, Villain's ROMS are updated regulary and there is loads of support in the forums, it's not as hard as you think.
i wanna get into the dev community. I realized i use what people make, but unlike alot of people, i wanna give back a little. Basically what im asking for is someone for me to message throughout this whole ordeal, and help me with some step by step things, walkthroughs, videos, anything to help me get going. Id prefer them to be roms devs themselves. i also enjoy long walks on the beach and just getting to know each other
I'm in the same boat bro. I wanna get into it as well, although I don't have the time to devote to it right now.
Swyped From My MikRunny'd Superphone Using TapaTalk 2
SynysterSilence said:
i wanna get into the dev community. I realized i use what people make, but unlike alot of people, i wanna give back a little. Basically what im asking for is someone for me to message throughout this whole ordeal, and help me with some step by step things, walkthroughs, videos, anything to help me get going. Id prefer them to be roms devs themselves. i also enjoy long walks on the beach and just getting to know each other
Click to expand...
Click to collapse
there are numerous tutorials on xda, rootz, and other sites on building from source and/or making sense (oem skin) roms
theres no quick step to get going, though building straight from someones source (which isnt really developing) requires just a few commands once ur build environment is set up
really though, most rom devs (well maybe not most, but many) started with theming first to get gain a working knowledge of the structure/set up of a rom and what controls what...as well as basically smali editing/apk decompiling and the tools needed
aosp requires a semi working knowledge of java to actually build your own things rather than syncing and building someone elses
there are plenty of devs that enjoying helping new folks out...but its kind of understood that you ll do some research on your own and have some knowledge of what ur doing...its a lot to kind of ask someone to talk you through every single thing that goes into it
from my own personal experience it, it took me several months of theming before i felt confident enough to tackle a rom project...and even then they were rom collaborations with people a lot smarter than me (sbrissen, adrynalyne, imnuts, etc)
nitsuj17 said:
there are numerous tutorials on xda, rootz, and other sites on building from source and/or making sense (oem skin) roms
theres no quick step to get going, though building straight from someones source (which isnt really developing) requires just a few commands once ur build environment is set up
really though, most rom devs (well maybe not most, but many) started with theming first to get gain a working knowledge of the structure/set up of a rom and what controls what...as well as basically smali editing/apk decompiling and the tools needed
aosp requires a semi working knowledge of java to actually build your own things rather than syncing and building someone elses
there are plenty of devs that enjoying helping new folks out...but its kind of understood that you ll do some research on your own and have some knowledge of what ur doing...its a lot to kind of ask someone to talk you through every single thing that goes into it
from my own personal experience it, it took me several months of theming before i felt confident enough to tackle a rom project...and even then they were rom collaborations with people a lot smarter than me (sbrissen, adrynalyne, imnuts, etc)
Click to expand...
Click to collapse
so if i were to start off with theming, what tools/programs would i need for my windows 7 running computer?
SynysterSilence said:
so if i were to start off with theming, what tools/programs would i need for my windows 7 running computer?
Click to expand...
Click to collapse
JDK, SDK, apktool, gimp, notepad++,and there's a search tool that I can't remember off the top of my head. That's all I got right now. And all I'm gonna run for a while.
Swyped From My MikRunny'd Superphone Using TapaTalk 2
awesome, now where do i go to start learning how to theme?
SynysterSilence said:
awesome, now where do i go to start learning how to theme?
Click to expand...
Click to collapse
This might help...my really old fascinate theme guide http://forum.xda-developers.com/showthread.php?t=932856
nitsuj17 said:
This might help...my really old fascinate theme guide http://forum.xda-developers.com/showthread.php?t=932856
Click to expand...
Click to collapse
wow good stuff bro thanks alot
wow this is actually just about what im looking for. its not very in depth, mostly the basics from the looks of it, but it sure as hell is a great start. i appreciate it.
I'm taking a java course this summer to help me make some ROMs. I would recommend it.
Sent from my ADR6350 using xda premium
i would but i dont have the time nor the money for it. my dads got his masters in computers tho i could probably get help from him for things like that.
My parents gave me their old laptop, I have ubuntu on it. When I get the time, I want to create my ROM based on CM9. I want to learn Java too, because I would like to do some themeing too.
sjpritch25 said:
My parents gave me their old laptop, I have ubuntu on it. When I get the time, I want to create my ROM based on CM9. I want to learn Java too, because I would like to do some themeing too.
Click to expand...
Click to collapse
Theming doesn't require java knowledge