Related
I'm trying now to cook my first rom for the kaiser. I've enjoyed trying other ROMs here, but basically I just want to take all the apps and settings I like best from others and put them together into one, without the things I don't use. I'm not doing it to be a 'chef', just to make my device work best for me.
Based on that, when I have a version I'm satisfied with and will be using, should I upload it to share, or just keep it to myself? Based on alex's comments on the Rom Kitchen pages, it looks like he'd prefer everyone just make their own, without sharing.
I think sharing something like this is perfectly fine as long as you give credit to who did the upfront work on the base you started with, the oem packages you used etc. Just be prepared that if you do share, you will instantly have a thread to "support".
One of the guys in the Wizard forum didn't want to deal with supporting his creation so he just put a link in his sig for the latest build he was using. Then if someone wanted to download and try it they could, but there was no "official" support for it since it was a personal "reheated" rom. I'm sure he got PM's directly.
So really your call and good luck with the cooking. More addicting than flashing IMO...
I'm not sure how I'll do on the cooking, it doesn't seem too complicated with the various tools that are out there, but just re-flashing over and over to find something isn't right or got missed is going to quickly become a pain.
I'm left thinking maybe I should take another look at auto installers as well. I may be better off to use a speedy Lite rom and setup the autoinstaller to make things easy after a flash. Hmm....
you will get lots of 'white mouses' for free by sharing ur ROM here.... lol
If you realy want to be good you need feedback, and what is bether than thousens of us flashaholics and want-to-be-cheffs to give you just that mister?
Hi,
I see that we have many many roms and 2 types of Sapphire (32B and 32A)
Now I have an idea to help users to install and change rom easierly.
Please read all idea before replying. Some ideas relate to others.
1. All developer should make 2 choices : 32A rom or 32B rom
2. 32B rom have data/app_s. Running system application on flash memory is more stable and faster than running on ext partition sdcard
3. Recovery should have new feature : Wipe data except data/app_s
Amon_RA should add this feature in his recovery.
4. Developers should remove his own theme, 3rd application (which can download from market), moded application ... from rom, rom will be more stable and smaller
5. If developer want share his theme or moded application or add new feature, he should share extend update in an update_extend.zip on his topic. I suggest him to use 1 folder on sdcard and command *.sh file
If you used iPhone, you will see that moded FW of iPhone OS doesn't include theme, extend application (which can download from Appstore). Why can't we do that? I think almost people just want to find a stable rom without theme, without extend application
Some good ideas
+1 from me
Moar standardization pleez
Sounds like the OP is ill-informed, and wants an iPhone.
funbacon said:
4. Developers should remove his own theme, 3rd application (which can download from market), moded application ... from rom, rom will be more stable and smaller
Click to expand...
Click to collapse
i've seen a few of these in the dream forum.
the developer releases the rom as a base package. ie. rom only, no (or very few customisations).
then add on packs are released to add 3rd party apps and customisations.
eg. http://forum.xda-developers.com/showthread.php?t=538456
this developer has released 4 different roms. each one comes as a base rom that is rooted, and each rom also then has an expansion pack.
themes are then installed as separate downloads.
the post is also very clearly laid out. i wish more developers took the time to create such understandable threads.
Isn't this request cramping developer's style?
Yes that is what you may want. But at the end of the day, they are doing it out of their enjoyment. It's their project and they have free reign on what they do and when they do it. Out of shear good will developers share. Its not up to us to make requests on how things should be. Our roles is to be supportive and grateful for their contributions.
That's not to say your ideas aren't valid... perhaps just not entirely feasible.
ice_prophecy said:
Isn't this request cramping developer's style?
Yes that is what you may want. But at the end of the day, they are doing it out of their enjoyment. It's their project and they have free reign on what they do and when they do it. Out of shear good will developers share. Its not up to us to make requests on how things should be. Our roles is to be supportive and grateful for their contributions.
That's not to say your ideas aren't valid... perhaps just not entirely feasible.
Click to expand...
Click to collapse
Good Say My friend
seems like a pretty simple request. but what was said earlier has merit as well, since it is really the developer's choice since its done for free.
but yeah, some sort of options like Enthomer is nice. But then again those updates made by AmonRa and Cyanogen is awesome as well. Fast, stable and useful.
Oh, and I strongly support the part on the way the threads are made. some are really easy to follow up on for change logs and stuff, some are messy.
funbacon said:
If you used iPhone, you will see that moded FW of iPhone OS doesn't include theme, extend application (which can download from Appstore). Why can't we do that? I think almost people just want to find a stable rom without theme, without extend application[/B]
Click to expand...
Click to collapse
Search the board (and the Android Market) for MetaMorph which does exactly that.
+1
well, although 'm not a dev, but as users this idea is pretty workable. at least we had lesser unneccesary thread and will look more neat and tidy. thats what make xda more professional and classy. way to go devs. +1 to the idea.
thanks.
OP, good idea, but not everyone may think like you, including the DEVs. There is nothing wrong with what you are stating, but it has been mentioned before that different DEVs want to work on different things; some people want to be unique.
One more thing, can you please not use the word should so much, please?
My wife uses it all the time..."you should clean this" " you should go here" " you should say this". thanks.
ice_prophecy said:
Isn't this request cramping developer's style?
Yes that is what you may want. But at the end of the day, they are doing it out of their enjoyment. It's their project and they have free reign on what they do and when they do it. Out of shear good will developers share. Its not up to us to make requests on how things should be. Our roles is to be supportive and grateful for their contributions.
That's not to say your ideas aren't valid... perhaps just not entirely feasible.
Click to expand...
Click to collapse
Agreed. Although some of the requests are somewhat reasonable, it's up to the devs to decide what they want to do with their free time and they are dedicating so much of it to making such great contributions to begin with.
We're not paying for the dev's services, so i dont think we have much pull on how they design their ROMS (nor should we)
I think if you want a specific ROM a specific way. YOU should be learning how to code and cook ROMS for yourself.
OzJD said:
Sounds like the OP is ill-informed, and wants an iPhone.
Click to expand...
Click to collapse
Read and lol'd. This is probably pretty close to the truth.
Well I for one salute the OP for finally taking a stand and telling the devs what we really want. After all it is all about ME and what I want and they should bloody well be grateful that I even bother to tell them what is wrong with their work, and they should fix it faster. I am a busy guy and can't be bothered to figure out this stuff for myself....
If any of that even vaguely resonates with you... here is a very small clue, completely free of charge...
The devs do this work for their own reasons. Some do it for the challenge, some do it for fun, some do it because they want something different, some do it for the glory. However, they all share it and make the results of their hard work available for the benefit of us end user types. Many even provide free support and hand holding, answering the same questions over and over.
You can politely ask for things to change. If you structure your request well enough and it makes sense, some devs may see the benefit and change. Others will not. Trying to dictate standards of documentation, presentation, features, or packaging just is not going to work, and quite frankly why should it. They are not doing it for you, you are just benefiting as a side effect of them being willing to release their work.
I am sure if you were willing to pay regular software developer rates for a particular feature set, you could find folks willing to accommodate you. Unless you are willing to do that, consider that you already get far more than you pay for.
rydr1 said:
OP, good idea, but not everyone may think like you, including the DEVs. There is nothing wrong with what you are stating, but it has been mentioned before that different DEVs want to work on different things; some people want to be unique.
One more thing, can you please not use the word should so much, please?
My wife uses it all the time..."you should clean this" " you should go here" " you should say this". thanks.
Click to expand...
Click to collapse
I'm Vietnamese and my English is not good. I just know saying " you should do something" is better than saying "you have to do something" or "you must to do something"
ice_prophecy said:
Isn't this request cramping developer's style?
Yes that is what you may want. But at the end of the day, they are doing it out of their enjoyment. It's their project and they have free reign on what they do and when they do it. Out of shear good will developers share. Its not up to us to make requests on how things should be. Our roles is to be supportive and grateful for their contributions.
That's not to say your ideas aren't valid... perhaps just not entirely feasible.
Click to expand...
Click to collapse
So I guess we should also stop giving developers suggestions and bug reports, because who wants to fix bugs for enjoyment? I disagree quite a lot with your post; it is in fact our role to make requests. How are ROMs supposed to get better without the input of its users? You completely contradict yourself by saying that we should not "make requests" but we should "be supportive," because by making requests, you are being supportive. By trying to better the project, you are being far more supportive than a silent user.
It's not like funbacon's suggestion has malicious intent. Neither is he trying to dictate what devs should and should not do. You don't have to agree with all of his points, but dismissing the whole thing because of one point, or the fact that he referenced the iPhone, is stupid. It's a suggestion, which most of you have said is a good idea, yet don't think it should be incorporated because... of the vocabulary used? Or maybe it's some other reason, but I have yet to see another valid reason.
Will this work in practice? That's another discussion. But I believe having some standards and general guidelines will be immensely helpful and make it simpler to try different ROMs.
Rydr1, you need counseling. Or a divorce.
bjtheone said:
Well I for one salute the OP for finally taking a stand and telling the devs what we really want. After all it is all about ME and what I want and they should bloody well be grateful that I even bother to tell them what is wrong with their work, and they should fix it faster. I am a busy guy and can't be bothered to figure out this stuff for myself....
If any of that even vaguely resonates with you... here is a very small clue, completely free of charge...
The devs do this work for their own reasons. Some do it for the challenge, some do it for fun, some do it because they want something different, some do it for the glory. However, they all share it and make the results of their hard work available for the benefit of us end user types. Many even provide free support and hand holding, answering the same questions over and over.
You can politely ask for things to change. If you structure your request well enough and it makes sense, some devs may see the benefit and change. Others will not. Trying to dictate standards of documentation, presentation, features, or packaging just is not going to work, and quite frankly why should it. They are not doing it for you, you are just benefiting as a side effect of them being willing to release their work.
I am sure if you were willing to pay regular software developer rates for a particular feature set, you could find folks willing to accommodate you. Unless you are willing to do that, consider that you already get far more than you pay for.
Click to expand...
Click to collapse
So... all the developers here make ROMs for themselves, but are nice enough to post it for everyone else to use?
Wow, haha. What a distorted view you have there. (Most?) developers aren't as selfish as you think they are. Developers make ROMs so the people who visit this forum can benefit from them, or at least that's the general reason. Why do you think they release updates often to fix bugs or add new functionality, or address issues and suggestions brought up by users?
Or, if I were to look at it from your point of view: users are just tools that devs use to make their ROM better.
Yeah, no. You shouldn't think so lowly of devs here. They should be appreciated, you know.
1.I will say that i've had android since day 1 and funbacon was around at that time to. helping and making changes himself to certain roms and apks etc...and helped other people, so he shouldnt be treated as a noob that doesnt know what he is talking about or that he is whining because that is not the case.
2. He made a suggestion that has to do with development and posted in the correct spot and he still hears **** from it? when there are people posting in deveoplment forums that has nothing to do it " what rom is the best, or what phone should i buy" and they dont get as much **** as your handing to someone that made a DEVELOPMENT suggestion and a good one. in the correct section. so people shouldnt be downing him for his work/suggestions
p.s funbacon...nice to see you around again
funbacon said:
I'm Vietnamese and my English is not good. I just know saying " you should do something" is better than saying "you have to do something" or "you must to do something"
Click to expand...
Click to collapse
No, funbacon, you took it wrong. Im just kidding about using that word. there is nothing wrong with you using it, there is something wrong with my wife using it.
I was just adding a little fun to the thread.
As I am working my way through the public transportation circuit back to my dev chair, I have a chance to ask for help if someone(s) are interested in helping the doubleshot development effort at large.
Development in the open source community is about two main points:
1. Being driven by your curiosity to learn something new or make something do whatever it does differently or better.
2. Distributing the workload of what we want or need between multiple people - many hands make light work and if everyone contributes something small collectively it turns into a whole lot of progress and success.
So here's something that would help us all out immensely even though it seems like a small issue on the surface:
.nb0 and .nbh files - how to break them down and an explanation of how exactly they work.
What they are is a proprietary format used to wrap up some of the installer files within OTA and software updates we get from HTC for this device. (Other HTC devices too)
We also need to have or have links to the software we need to break them down with.
This information and how to use it will make a tremendous difference in how quickly and effectively we can assimilate and process our official software updates and continue to deliver both S-OFF and Root solutions when they are stripped from us on OTA pushes.
I'm making too much progress on other fronts and with other issues to stop and take care of this, and the very limited searching I've been willing to spare on this front has lead to dead ends and dead (mostly megaupload) links to what we would need.
Honestly, I've got a lot of dev work I've gotten myself involved in with this device and the progress I make doing other stuff is greater then putting more time into this, based on the project files I have in process. If I was just starting with helping out on doubleshot development this would be what I would be spending time on - just where I'm at I lose momentum focusing on this.
I get PM's from people asking for advice or direction on how to help out in addition to a scattering of threads around here started by people with lot's of enthusiasm but no direction, and I definitely understand! I've been and (believe it or not) continue to be in that very same position!
Sometimes all people need is a nudge in a direction, a path pointed out to them that they can explore and learn about - this is just such a signpost on the way to becoming the developer some of you out there want to be.
Development basically = knowledge + implementation, and the more you know the more creatively you can leverage it to your advantage. We certainly have some creative people who have passed through or are here now surprising us every day.
From the impressively out of nowhere CM7 port kornyone gifted us with in the past to the jaw-dropping brute-force ICS work tbalden blazed a trail into ( and sucked a few people into along the way ) all the way down to the work XMC has been steadily chipping away at building tools for us to use and wrap it all together with - we really have some talent, passion and a lot of success in our small but effective corner of the XDA forums.
...and those are only a few of the people who have made a lot happen around here, there are and certainly have been others who have either left a mark on development for this device or continue to do so.
Excited? I am! There's so much cool stuff to do and who cares if we never get an 'official' ICS update? We (collectively) are producing software the manufacturers/carriers wish they could produce in a fraction of the time it would take them to do so.
What some may not realize, though, is that it isn't this person or that person making it happen, but the collective efforts of us all together that enhance and compliment the individual strengths we all bring to the table separately.
...and it's all built on us sharing what we know and helping each other out. Maybe some out there, especially the more casual viewers or unregistered lurkers don't realize just how much we work together - where the larger sub-forums are more scattered and individualized just because of their population.
As an aspiring dev, this should make our little corner even more appealing because that leaves a lot more new ground to cover and gives everyone who jumps in that much more of an impact on what we have available.
Maybe in other places you're the fiftieth person to make some lockring or point something out, but over here just about anything you get into is new ground for us - so we are definitely excited about everything anyone has to offer, no matter how trivial it may seem to you.
As many of you have gathered by now I'm a bit long winded at times, but it's all so exciting!
So back to the original point, which was that if someone or a handful of someone's wanted to do something to help out, and push development for the device forward but wasn't sure what to do, figuring out how those .nb0 and .nbh files work and finding some software to crack them open with would be a big help in gaining and maintaining S-OFF and Root for this device.
.nb0 files especially, because they are something within the OTA that is a single file that impacts multiple partitions, and we really haven't gotten a look inside of them at what exactly they are doing to our device and how.
The death of megaupload and sites like it cost the open source community a lot of tools that are in some cases still missing and in others maybe never to be replaced...at least not without someone taking the time to sit down and do so.
...could that be you?
gtmaster303 said:
Sorry blue, I got lost in your post. What exactly are you looking for?
A software that can do what with these files?
Click to expand...
Click to collapse
Cliff notes:
Blue6IX said:
The strength of XDA is the community itself and the knowledge it contains. If we want to truly leverage it here in the doubleshot forums, this is how it can be utilized the best.
Click to expand...
Click to collapse
Any and all info on the .nb0 or .nbh file format, anything people can gather.
How do we break them apart?
What is inside of them when we do?
What partitions does it flash it's pieces to, are the individual pieces signed or just the file itself?
Can we make these files?
...How?
.nb0 is inside the OTA packages, .nbh is a type of package like the PG59IMG.zip files, so the tools to work with them are different?
Here is an .nbh thread that could help get someone started...
NBHextract: Extract contents from NBH files with a tool but we don't have any of these files yet?
Here is the wiki page it links to which will help more:
NBH wiki page that it links to on that tool page which might help some more.
I bring up .nbh because that is one of the methods of insertion the auto-install tries to use when booting to hboot:
Blue6IX said:
When loading hboot, the files it automatically looks for on the sdcard are:
- PG59DIAG.zip
- PG59DIAG.nbh
- PG59IMG.zip
- PG59IMG.nbh
- PG59IMG.tar
- PG59IMG.aes
- PG59IMG.enc
Click to expand...
Click to collapse
...and the more people we have familiar with these files and spend time helping us to figure them out, the better equipped we will be to deal with new OTA packages and everything that goes with them.
What do we know? Collectively, here, not very much - if so, someone speak up and if not here's something people can help with.
How do we make .nbh files, or any of the other packages quoted there we don't have?
We've pretty thoroughly examined PG59IMG.zip files but the .nb0 files in them are still somewhat of a mystery - here are the ones from the 3 PG59IMG.zip files you can find links to here:
Restore to Stock
Files:
doubleshot_1-28-531-9_nb0.zip
Download Link
MD5: d5e8721090dbc048c711d7f42404286b
Size: 1.75 MB
doubleshot_1-55-531-3_nb0.zip
Download Link
MD5: dba1925982b4c5e0a41f3291942e09e0
Size: 1.75 MB
doubleshot_1-63-531-2_nb0.zip
Download Link
MD5: aaa9edc7b2c5ec91559ab01caebab8ac
Size: 1.75 MB
These zip files are in uncompressed form, simply zipped in store - small files but 2 each. Here you go, hope someone has fun with them!
Sent from a digital distance.
http://www.ubiquitense.com/technology/how-to-install-android-roms-with-nb0-file-extension/2800/
dont know if this is what you are looking for but maybe........
i think this is better?
http://android-dls.com/wiki/index.php?title=How_to_unpack_and_repack_NB0_file
tl;dr:
Blue is a noob with poor time management skills.
jk, I would love to see more people get involved with development. You can't really ***** about a lack of development and then not be willing to support it.
Sorry blue, I got lost in your post. What exactly are you looking for?
A software that can do what with these files?
Usually, all unknown file types I come across I run through winrar and see how it handles it.
Found this with a quick google:
http://filext.com/file-extension/NB0
I edited the first post, adding the second half to it starting with the quote below:
gtmaster303 said:
Sorry blue, I got lost in your post. What exactly are you looking for?
A software that can do what with these files?
Click to expand...
Click to collapse
As evidenced by my original posting, being concise is not my strong suit.
I posted that from the doubleshot while I was sitting somewhere waiting for people, and so it was a little all over the place even for me. Hope this post and the edits above clarify the intentions of this thread better?
Can someone explain how to break down the nb0 files and find tools to do it properly? See if you can sit down and crack one open and see what's inside.
See how many of the questions can be answered from above, and what other ones we don't know enough to ask are/their answer(s) are?
The doubleshot community benefits from it's developers having how-to references on the things we need to do, and pretty much everything we need to know is scattered all over XDA.
It takes time to funnel, qualify, and share that information here so we can use it.
Many more people will be able to dev for this device if they can come here and learn how to do it, and not have to resort to the XDA scavenger hunt that every other dev who started here had to go through.
If other people can see the value of and want to help out in searching out how to do things and get it here for us to use, the honest truth is that's a resource built by the developers here or not at all.
Learning how to do things and going through that experience and what the pitfalls are and finding where to get what you need to do it is basically development.
Sharing those experiences with XDA is what makes this community a resource.
Bringing it here gives people who want to dev and don't know where to start a learning project that can benefit everyone working here.
Something like this is a good trial for posing this question - there are a lot of things that we would benefit from having here and not just on XDA at large. If someone or people want to get together and solve this mystery because they were looking for a problem to solve, then here is the best way to turn that learning experience into a guide for the rest of us.
...and we can check that off our list of things we need to learn how to do.
I can make a post at some point with a concise listing of things we need to know about, with a link to a summary of what we know about each, and then we could use it as a checklist to start systematically solving our problems and making the device do what we need to do.
The strength of XDA is the community itself and the knowledge it contains. If we want to truly leverage it here in the doubleshot forums, this is how it can be utilized the best.
--------
So, when someone gets so energized by this as many of us have felt at some point - that overwhelming desire to help but complete confusion on where to start?
Go learn something we don't know and share how to do it or what it is here. We all benefit and people already here working on other things can just add how to do whatever that is to their methods.
Please don't think this is a case of me sitting here saying "i'm too lazy to learn how to do this, someone teach me" ...
...this is a case of "does anyone out there want to help explain what this is and how to use it? Here's a project if anyone wants it" ...
...i've written quite a few guides here as i've learned how to do things, and wouldn't pose this kind of question without having contributed first. So just offering a starting point to anyone else willing to do that too.
If there is interest in people taking the project on, I can make a checklist of what we need to know and we can have a point of reference on how to spend our time when looking for projects to do.
If no one's interested in learning this and sharing it here then I won't waste the time it would take to put such a list together and source everything. Eventually i'll figure this out and share it here if no one does, but we would grow as a community for others to do it. Just looking for ways to make everything work more smoothly here.
This place is whatever we make it to be, so do we want this?
You think it would help if we asked HTC dev what they're for?
I would love to help! But I don't know anything about being a Dev.
Hi Blue6IX,
I've read most of your post, but I don't quite understand to what purpose we need the contents of these files.
I mean, I got my Doubleshot, rooted/S-OFF'ed it with revolutionary/unrevoked and SIM unlocked it following this guide and installed an ICS ROM. Is there anything that prevents others from doing the same?
Also, I come from the Moto Milestone, which has a locked bootloader and no way to unlock, and still people managed to get ICS up and running (with 2.2 being the latest version Motorola wanted us to have on the device).
For the Doubleshot, you can just fire up a repo sync with CM9, get the preliminary msm8660 device tree(s) and create a doubleshot device tree. I know it will require some adaptations and coding, but IMHO this is nowhere near the problems other devices face.
Since I didn't really find any information on other hindrances, I would be glad to hear of them. Otherwise, I don't think analyzing HTC's/T-Mobile's original update files will be useful for anything?
Curiously yours,
Stefan
seidler2547 said:
...
I mean, I got my Doubleshot, rooted/S-OFF'ed it with revolutionary/unrevoked and SIM unlocked it following this guide and installed an ICS ROM. Is there anything that prevents others from doing the same?
...
Click to expand...
Click to collapse
Yea - for a while S-OFF was impossible for any device on the 1.55.531.3 software version ( or later ) with hboot 1.45.0013
There was also a time where they couldn't unlock the device and were basically stuck barely able to root.
For most people, S-ON and unlocked is the best it can get at the moment - making it pain to flash roms with custom kernels and completely unable to go back to the stock radio or hboot.
seidler2547 said:
Hi Blue6IX,
I've read most of your post, but I don't quite understand to what purpose we need the contents of these files.
...
Otherwise, I don't think analyzing HTC's/T-Mobile's original update files will be useful for anything?
Curiously yours,
Stefan
Click to expand...
Click to collapse
I cut out most of the post you made ... ( quoting a whole post unnecessarily is rather annoying ) ... But you really answered your own question here.
Do you know for certain they won't help now or in the future?
Have you checked to see?
How can you check if you can't break it open?
If you can, could you share directions how and working links to tools to do it with?
...the OTA and PG59IMG.zip packages are how the manufacturer updates the device and makes changes to things we can't - knowing how they do it can help lead to a way for us to do it.
Especially since we don't have a proper RUU and basically are left begging for scraps at the "official" software table for the device - knowing how the few legitimate software packages work we get becomes even more important.
Every time an OTA update comes out, the possibility exists to lose root, S-OFF or even a working device ( the next broken update will NOT be the first ).
As you mentioned being curious, well, you hit the nail on the head as to the entire purpose of the thread.
I'm curious, anyone serious about helping us keep root at the very least is too ( and if not, now know they should be and a bit about why ).
It's one of many, many pieces to the puzzle, but the more thoroughly we understand each puzzle piece itself, the better of a chance we have at actually putting it together.
Bottom line is we don't know, we should know, and the project of finding out and sharing it here is a great opportunity for someone who wants to learn how to be a dev and has no clue where to start.
This project is on my list, but I figured i'd post it here and create an opportunity for anyone interested in it...otherwise I'll get to it at some point.
For all the time I've put in the thread, I probably could have made progress on the answers to at least some of the questions I've posed. I'd rather see if investing that time in soliciting more participation is worthwhile. It's not something I need, but rather something WE need...
Anyone like a good mystery?
Sent from a digital distance.
Ok, I mentioned in annother thread that I am willing to learn developing so our phone dosent die. I've rrun into a bit of a hiccup in that I'm compeletly new to programming and I've either gotten no response or a negative one when I went looking for pointers. Fear not I am still not giving up it is just going to take longer than expected. So in interest of keeping development moving forward I'm putting out a call to arms. Are there any other aspiring developers out there? If so post in this thread what you are good at and what you can do. Perhaps we can collaborate and push out a rom in the near future. Personally I am an expert at graphic manipulation and can handle all of the ui, still working on the coding part. For everyone else, post things you would like to see and perhaps one of us could pick it up and run with it. Let's work together and make this work better than they ever thought it could!
Sent from my SGH-T839 using XDA
Sigh..
We can't work together if you don't have experience with coding.
If you really want to get a spark, you need to get a promising build onto github. And, you will need experience and attention to detail. Nobody wants to help if you don't comment your code, keep good changelogs, and maintain a good readme.
So far, I don't see it out there.
Furthermore, I can't afford to spend hours working on something that won't pay my mortgage. Most of us can't.
If I hit the lottery, maybe I'm your guy. In the meantime, we can't work together without a leader.
And, let's hope the next developer isn't lacing every file with a bunch of jibber jabber about "don't kang my sh*t, bro." Because, a collaborative effort would require plenty of sharing.
Just my two cents.
I would love to see a new Sense rom. but this place seems dead. Coming from the G1 I was surprised to see barely any roms. Even though the G1 is a ancent phone, it had quite a bit of rom and there's more activity over there than there is activity over here.
Sent from my SGH-T839 using xda premium
orange808 said:
Sigh..
We can't work together if you don't have experience with coding.
If you really want to get a spark, you need to get a promising build onto github. And, you will need experience and attention to detail. Nobody wants to help if you don't comment your code, keep good changelogs, and maintain a good readme.
So far, I don't see it out there.
Furthermore, I can't afford to spend hours working on something that won't pay my mortgage. Most of us can't.
If I hit the lottery, maybe I'm your guy. In the meantime, we can't work together without a leader.
And, let's hope the next developer isn't lacing every file with a bunch of jibber jabber about "don't kang my sh*t, bro." Because, a collaborative effort would require plenty of sharing.
Just my two cents.
Click to expand...
Click to collapse
I appreciate your honesty. But you misunderstand my intentions. I am not looking for someone to hold my hand and walk me through how to do everything. I, at most, am looking for info on how to start. I know I need expirence in coding before I can push out a rom, and that it will take a while to get that. That's why I started this thread. So, instead of waiting for me to finish the learning process we can get any other aspiring developers together to start something new in the meantime. I know there are others out there and if we all start posting what we can do and what we would like to see then maybe something may come from it. Thank you for point me to github, I'm sure I can learn some more from there. I understand about responsibilities getting in the way of hobbies, I have kids and a mortgage too, I'm just looking to get all the new developers together so that we can share and work together. I have a friend that writes code for websites for a living and I'm trying to get him on board to take this up as a hobby. Here's hoping.
Sent from my SGH-T839 using XDA
NightmyreWreckage said:
There are only three devs left for the Sidekick.
HewettBR, me (JiN1337), and nxd (kernel developer)
Reactive was a guy who tried to get everyone banned for using open source work, and thus in turn got banned himself.
I would be welcomed to help teach you a bit. I wish I had a learning curve when I was just beginning how to cook ROMS.
1. Download a ROM, unzip it, browse around files, and open files. Play with things.
2. When in doubt, Google it. It's likely someone else had the same problem before you and is a basis on how I fix 80% of ROM problems.
3. Always, always make a NANDROID. A foolish mistake is to flash your own ROM and not have a backup to go to, and than you have to start all over.
Click to expand...
Click to collapse
Thanks. I have a stack of books on android as tall as my hip lol. I feel like I'm in college all over again. Any help would be appreciated at this point. I'm on information overload.
Sent from my SGH-T839 using XDA
hi could you post some good beginners reading guides on anything related to whatever you do since im new. im new so i ask questions like http://forum.xda-developers.com/showthread.php?t=2392704
actually someone new won't even know what bluestack is.
i have to start reading up on all this stuff. it doesnt have to be on this site, just readings so i have a better understanding of all this
pleaseeeeeeeeee
phonebroken said:
hi could you post some good beginners reading guides on anything related to whatever you do since im new. im new so i ask questions like http://forum.xda-developers.com/showthread.php?t=2392704
actually someone new won't even know what bluestack is.
i have to start reading up on all this stuff. it doesnt have to be on this site, just readings so i have a better understanding of all this
Click to expand...
Click to collapse
Since you mentioned your eager to understand what goes on here at XDA I would highly recommend taking a look at this thread http://forum.xda-developers.com/showthread.php?t=2073370. It contains links to approximately 108 guides that explains everything from what is logcat and compiling Android from source to explaining about MODs and Tweaks, to how to compile and modify your own Android ROMs. Also if you still have any questions feel free to ask me I'll be happy to help you out .
Sent from my Nexus 10 using xda premium
great! though i need an overview guide --
like what is a rom?
why would you want to port or create roms?
why do you want to log?
same with the other topics
none of these seem especially helpful or specific to my problem :/
i think the "Tools and mods,tweaks" and "Misc" sections has the most helpful things
but the guides needs to be ranked. there's a lot of bad info out there
phonebroken said:
great! though i need an overview guide --
like what is a rom?
why would you want to port or create roms?
why do you want to log?
same with the other topics
none of these seem especially helpful or specific to my problem :/
i think the "Tools and mods,tweaks" and "Misc" sections has the most helpful things
but the guides needs to be ranked. there's a lot of bad info out there
Click to expand...
Click to collapse
To answer your questions:
like what is a rom?
A ROM as defined on the XDA wiki and the Android terms glossary thread is:
The ROM holds the Operating system and other components such as the bluetooth and wifi stacks. The ROM is accompanied by the Radio, Ext_ROM, SPL and IPL. Carriers such as T-mobile or Vodaphone taylor the ROM to their specifications and version numbers do not carry the same meaning across different carriers. IF the carrier you use supports the device well they will usually release regular ROM updates.
Click to expand...
Click to collapse
Rom/Firmware:Read-Only Memory and technically speaking, it refers to the internal storage of a device, which is supposed to contain the operating system instructions that needn’t be modified at all during the device’s normal operation.
Click to expand...
Click to collapse
why would you want to port or create roms?
Developers create and port ROM's for a variety of reasons. One reason is because they want the latest version of Android on a device that doesn't officially support the latest version of Android. For example the last officially supported version of Android on the Nexus S was 4.1.2 but developers compiled Android 4.3 for it so Nexus S users can enjoy all the latest features and benefits of Android 4.3. A second reason is because developers add features and performance enhancements that the original device manufacturer never could have envisioned or left out. Cyanogenmod, AOKP, and Paranoid Android are all perfect examples of custom ROM's that were developed to increase performance and add many new features. A third reason, is that if you like a ROM but it isn't available for your device, developer's will port it over do the device they want it on (Note: This process can range from very simple to extremely complex) so they have that ROM's features on there device. A fourth reason is theming, some times user's will create custom ROM's that include a heavily modified or changed user interface and then distribute the changes. However ROM's that are just themed and no other changes made are becoming less prevalent due to additions of universal theme engines such as the XPOSED Framework .
why do you want to log?
Logging allows developers to see where the problems are and what is causing certain functionality such as Wifi, graphics, touchscreen, app problems, etc. to not work correctly. The log gives a detailed report of what is not working and a starting point troubleshooting where the error occurs. Developers then look at the logs and fix the error messages they are receiving. Without logs it would be close to impossible to fix any problems you ran into when developing a ROM.
Another set of guides that is an excellent source of information is -NickHalden-'s Guide Ride-From a Newbie to a Dev, Get all you need here. It takes you like you wanted from just understanding the basics, all the way up to developing ROM's and other cool stuff yourself. It also includes a very helpful numerical order that you can follow along so you don't miss any important information along the way. Also I am curious as to what you mean by "but the guides needs to be ranked. there's a lot of bad info out there"? Can you give an example? Additionally you can rate threads and see the threads ratting if they have one at the top of the thread for what users have rated it, this is usually (Though not always) a good indication of how helpful people have found the information in that thread. And if you have any other questions let me know I'm always happy to answer them .
thanks so much! i obviously didn't know what i was getting myself into... you explain these basics really really clearly so you have a talent for it =)
oh the threads do have ratings. didn't notice it. that's great!!
i think that these helpful things should be more central, like the info you gave is very helpful, and places like wikipedia, etc. won't explain it's relevance very well
i have a question on mobile + tablet though. so most people likely don't user their phones to type very much, but being able to type is important to me and i don't think the current state is good
so i wanted to know when you think 'they' will develop a phone that is much bigger but smaller than the smallest current laptop
last i check the smallest was http://www.notebookcheck.net/Review-Lenovo-IdeaPad-Yoga-11S-Ultrabook.96315.0.html
and smallest keyboard were
http://www.ianker.com/product/98APIPAD-02BTA
http://androidspin.com/2012/09/19/j...-worlds-smallest-fordable-bluetooth-keyboard/
or a tablet with a keyboard that is smaller than the current state because it's too big
so basically the current is too small and too big for what some of us need, and i wanted to know if someone can predict when they're come out with the perfect size for some of us
phonebroken said:
thanks so much! i obviously didn't know what i was getting myself into... you explain these basics really really clearly so you have a talent for it =)
oh the threads do have ratings. didn't notice it. that's great!!
i think that these helpful things should be more central, like the info you gave is very helpful, and places like wikipedia, etc. won't explain it's relevance very well
i have a question on mobile + tablet though. so most people likely don't user their phones to type very much, but being able to type is important to me and i don't think the current state is good
so i wanted to know when you think 'they' will develop a phone that is much bigger but smaller than the smallest current laptop
last i check the smallest was http://www.notebookcheck.net/Review-Lenovo-IdeaPad-Yoga-11S-Ultrabook.96315.0.html
and smallest keyboard were
http://www.ianker.com/product/98APIPAD-02BTA
http://androidspin.com/2012/09/19/j...-worlds-smallest-fordable-bluetooth-keyboard/
or a tablet with a keyboard that is smaller than the current state because it's too big
so basically the current is too small and too big for what some of us need, and i wanted to know if someone can predict when they're come out with the perfect size for some of us
Click to expand...
Click to collapse
Regarding a central place to find information the easiest way to find it to often search either using XDA's "Search All Forums" button in the upper right hand corner, or to use Google and search something such as "xda {your search term here}" or "{your search term here} xda" (For example "xda root nexus 10" etc.). Another way to find things is simply browse through the massive amount of helpful information that can be found on XDA simply by browsing around, I have learned countless, countless things this way. If there is a specific subject or topic your interested in let me know and I'll be happy to help you look for it or point you in the right direction. To answer your keyboard question, this is a interesting dilemma as an incoming computer engineering student problems like the one your described are very fascinating to me. I suspect what will happen in the future (2-3 years or sooner) is that we will see fold-able screens that we can roll up and put in our pockets or much more flexible keyboards that you can roll up into your pocket will be developed. But overall the keyboard and real typing experience you mentioned is a very real dilemma.
phonebroken said:
thanks so much! i obviously didn't know what i was getting myself into... you explain these basics really really clearly so you have a talent for it =)
oh the threads do have ratings. didn't notice it. that's great!!
i think that these helpful things should be more central, like the info you gave is very helpful, and places like wikipedia, etc. won't explain it's relevance very well
i have a question on mobile + tablet though. so most people likely don't user their phones to type very much, but being able to type is important to me and i don't think the current state is good
so i wanted to know when you think 'they' will develop a phone that is much bigger but smaller than the smallest current laptop
last i check the smallest was http://www.notebookcheck.net/Review-Lenovo-IdeaPad-Yoga-11S-Ultrabook.96315.0.html
and smallest keyboard were
http://www.ianker.com/product/98APIPAD-02BTA
http://androidspin.com/2012/09/19/j...-worlds-smallest-fordable-bluetooth-keyboard/
or a tablet with a keyboard that is smaller than the current state because it's too big
so basically the current is too small and too big for what some of us need, and i wanted to know if someone can predict when they're come out with the perfect size for some of us
Click to expand...
Click to collapse
Something like this maybe?