Related
I would like to start learning how to put roms together. I would like to start with developing a 2.2 rom compiled from galaxy s I900 source. Is there anyone here that can point me in the direction of a good tutorial on how to start? I have been using other peoples work for like a year and a half and would really like to create rather than use. I am a total noob when it comes to developing so any help would be great. thx
Go here;
http://forum.xda-developers.com/forumdisplay.php?f=613
Read a lot before you ask.
Good luck!
You can't develop a rom using only kernel source.
Sent from my SCH-I500 using XDA App
Its not kernel only. I am not a total moron. It is the 2.2os downloaded from samsung for the galaxy s i9000
yutzyscott said:
Its not kernel only. I am not a total moron. It is the 2.2os downloaded from samsung for the galaxy s i9000
Click to expand...
Click to collapse
All I have to say is good luck with that.
fallingup said:
All I have to say is good luck with that.
Click to expand...
Click to collapse
In all seriousness do you stay apprised in any way shape or form of android related news our just enjoy smearing the forums with your illinformed ramblings and negativity? Speak of what you know and don't be so eager to dismiss anyone with the fortitude to increase their own knowledge base on an operating system such as this when its these people who we all depend on to better our experience with said operating system. As it is these people for whom google turns to when it comes to ideas on how to better their future stock releases. Thank you for the vote of confidence.
Sent from my SCH-I500 using XDA App
You do realize fallingup has written more android code than your phone can hold?
The reason they seem testy is they(actual developers) have been spending all their free time trying to get Samsungs crappy code to compile, and every couple of hours some one asks for an easy how to guide for porting Froyo.
Spend some time reading the forums. Find out what is already being done, then learn the basics of rom development. THEN, ask intelligent questions on how help develop Froyo for our phones.
Asking for an easy way to cook roms is the equivalent of the kid in the back seat asking "are we there yet" every 30 seconds. If you really want to learn how to cook roms, try a couple easy ones with the kitchen I linked to, then learn how to work on roms without the kitchen. Then work on Froyo. There is no easy way.
I didn't ask for an easy how to thinking that I could have it done by tomorrow or even that I could figure it out at all. I simply asked for a starting point and stated in the OP that I am a know nothing when it comes to developing. As far as my last post I meant no disrespect to fallingup in fact it was my mistake to quote his post. I actually intended on quoting jt1134 so, to fallingup, I have used your stuff many times and have nothing but respect for what you do. I apologize for the misquote. I in no way think myself to be super genius to the 10th power nor do I believe that I can actually do anything worth while with this code. I'm just bored and want to learn. I'm also an Android addict.
P.S. Thank you for the link. Also you'll notice in my last post now that you know of my misquote, that I am actually 100% behind people like fallingup. I would never knowingly give a verbal bashing like that to him.(god I feel like **** now)
You meant to quote ME? Wow.
In all seriousness, and no disrespect intended, I'll explain a few things.
The code Samsung provides is NOT the full OS. Not even close. It's the kernel, plus a few android packages. In most cases, the android packages are EXACT copies of the code that has been available from Google for months, and in other cases has one line changes referencing a Makefile that doesn't exist. This is no way gets us any closer to a 2.2 rom other than the kernel. What we REALLY need is a working 2.2 ota build or leaked package to move forward any faster. That is MUCH more important than the garbage that Samsung has been releasing to us.
If you are a noob to development, then GOOD LUCK. If you are an advanced developer with intimate knowledge of android, then GOOD LUCK. There are quite a few of us working on aosp ports to the SGS phone series, and so far it has not been completed for a SINGLE device.
There are no guides that will explain exactly what is needed to accomplish this goal. There is no one who is going to hold anyone else's hands through it. Hacking is a meritocracy, meaning you'll get help with advanced topics when you show you have done your research, put effort into resolving the issue on your own, and ask intelligent and informed questions that give exact details of the situation.
If you would like to continue to show a poor attitude, then go for it on your own. Wait for us to release a working rom. If you would like to actually learn and invest some time in moving forward, the GO FOR IT, you are VERY WELCOME to do so. Read the porting guides written by google, try some stuff out, and come over to IRC and get your hack on.
I'm tired. I'm generally a nice guy, sorry!
jt1134 said:
You meant to quote ME? Wow.
In all seriousness, and no disrespect intended, I'll explain a few things.
The code Samsung provides is NOT the full OS. Not even close. It's the kernel, plus a few android packages. In most cases, the android packages are EXACT copies of the code that has been available from Google for months, and in other cases has one line changes referencing a Makefile that doesn't exist. This is no way gets us any closer to a 2.2 rom other than the kernel. What we REALLY need is a working 2.2 ota build or leaked package to move forward any faster. That is MUCH more important than the garbage that Samsung has been releasing to us.
If you are a noob to development, then GOOD LUCK. If you are an advanced developer with intimate knowledge of android, then GOOD LUCK. There are quite a few of us working on aosp ports to the SGS phone series, and so far it has not been completed for a SINGLE device.
There are no guides that will explain exactly what is needed to accomplish this goal. There is no one who is going to hold anyone else's hands through it. Hacking is a meritocracy, meaning you'll get help with advanced topics when you show you have done your research, put effort into resolving the issue on your own, and ask intelligent and informed questions that give exact details of the situation.
If you would like to continue to show a poor attitude, then go for it on your own. Wait for us to release a working rom. If you would like to actually learn and invest some time in moving forward, the GO FOR IT, you are VERY WELCOME to do so. Read the porting guides written by google, try some stuff out, and come over to IRC and get your hack on.
Click to expand...
Click to collapse
Now I have the right person quoted. Did you even read my post??? Let me repeat a key part so that you can understand and maybe you can stop battering the new guy.
"I didn't ask for an easy how to thinking that I could have it done by tomorrow or even that I could figure it out at all. I simply asked for a starting point and stated in the OP that I am a know nothing when it comes to developing."
I have admitted to my know nothingness. I simply want to learn. You could respond with something such as Galaxy S 2.2 is not a good place to start the learning process. Or you could have left it alone entirely and just thought that the link posted by "sgtmack" was sufficient enough. After all it did answer the exact question I asked. You might know a lot more about code and code writing than me but you have to admit, "your kind of an arrogant ass!" Now I would like to end this banter by allowing you to respond in whatever way you deem necessary. I myself will give this no further thought as I would like to move on now. That and I believe I have made myself look bad enough now.
As for fallingup and sgtmack, thanks for the hard work and helpful advice.
yutzyscott, do you not realize that jt and dirrk are the ones that got us the voodoo kernel? do you know they are the ones that got the kernel booting in the first place using samsung's ****ty source code? without jt, there would be nothing to build a rom around. wtf do you mean ill-informed when jt probably knows more than most people about developing for this phone? pay some ****ing respect for people that deserve it.
Yeah I do but, when this whole thing started I did not read who the post was by but, rather I just read the post. While I appreciate his work and am actually using it, my pride was hurt and its hard to interpret someones tone on a forum. I was under the impression in the beginning of all this that it would be known that I downloaded the 2.2 ota pushed to the original galaxy s and not the source they have been working with and making leaps and bounds with despite the road blocks. I was interested in learning how to port it (the ota I mean) rather than just sitting on my hands waiting to use anothers work. Chances are that I would never even come close to understanding what I was looking at but, I had to try. Now I'm sorry I asked. I quit...I was wrong, sorry! Leaving it to the experts. I'll go back to helping people with simple basic problems on droidforums.net and continue being an expert on using the real experts work.
This doesn't need to be turned into a flame thread. So here's my advice: join us on irc.freenode.net #samsung-fascinate and ask questions there. learn how to build a kernel, and maybe try to find out how exactly to port roms from other devices. Its a tough business, especially when we don't even get working kernel source from the manufacturer.
There are a ton of people that are working on the galaxy s phones, trying to get AOSP and the like on them. These phones are quite different than any other android phones, just with the way that the hardware / partitions are, so there is a lot to work through and document. Once one of the SGS phones is running aosp, im sure the others wont be too far behind. I wouldn't bother porting another crappy samsung rom, cause it will still have a lot of the crap that we are trying to get rid of by running aosp.
Thanks. And to jt, im sorry for being an argumentative ****. Thanks for all your hard work and despite the fact that there are many having issues with voodoo I am one of the many who it is working beautifully for.
Sent from my SCH-I500 using XDA App
yutzyscott said:
Thanks. And to jt, im sorry for being an argumentative ****. Thanks for all your hard work and despite the fact that there are many having issues with voodoo I am one of the many who it is working beautifully for.
Sent from my SCH-I500 using XDA App
Click to expand...
Click to collapse
Hey no hard feelings man. This was the first thing I saw after waking up today so I got rubbed the wrong way. Apologies. Feel free to catch me on IRC and I'm always happy to answer any questions relating to compiling stuff for our phones
jt1134 said:
Hey no hard feelings man. This was the first thing I saw after waking up today so I got rubbed the wrong way. Apologies. Feel free to catch me on IRC and I'm always happy to answer any questions relating to compiling stuff for our phones
Click to expand...
Click to collapse
Me too. I was drunk last night and after three hours of sleep I started responding on this thread.
Sent from my SCH-I500 using XDA App
yutzyscott said:
Me too. I was drunk last night and after three hours of sleep I started responding on this thread.
Sent from my SCH-I500 using XDA App
Click to expand...
Click to collapse
Thats always a good excuse
this was an entertaining thread lol.. misunderstandings is one of the biggest downfalls of online conversation.
Not meant to be offensive. Just funny. http://www.geekologie.com/2010/10/a_day_in_the_life_of_internet.php
Sent from my SCH-I500 using XDA App
Alpha0.6 Release notes:
Another minor release. While working on bigger problems that will take a while I wanted to push out an update for some things that have happened in the last few days. This is primarily to get Flemmard's work out for more testing. This contains the start of CyanogenMod settings. However, most of the settings are not functional on tablets yet.
With this release I will also provide two flashable zips to allow you to easily switch between lcd density 120 and 160. The default is still 160 because it offers the greatest compatibility. Any lcd density value between 160 and 120 will ruin market compatibility. For those that would like a "higher resolution" look and feel, you may flash the 120 lcd density update.zip. This will copy a new build.prop and will update the launcher for proper display. I strongly recommend changing the font size in Settings->System->Fonts if you chose to do this. The 160 lcd density update is provided to easily revert the change.
Touchscreen fixes
Ability to hide the combined bar(navigation buttons and clock) for full screen. This uses the ICS api so it will require app support(not all apps have been updated). This is an option under Settings->[Interface]->System->Combined Bar (Credits to Flemmard)
Scrollable quick settings. This will require tweaking later to allow it to be bigger on the Touchpad but fixes overflow issue on 7" tablets with the new Bluetooth toggle. (Credits to Flemmard)
Reboot to recovery is working via the power menu(hold down power button). Note: reboot will sometimes shutdown rather than rebooting.
Preliminary support for Rom Manager. In order to use this you will need Rom Manager Premium because it is not official yet. In order to use it you will need to execute "Flash ClockworkMod Recovery" in Rom Manager. Confirm the model is cm_tenderloin, say yes that you have installed manually, and check ClockworkMod 3.x. Now you can use Rom Manager to flash update.zips. Official support should come soon.
Other general changes from syncing with latest changes
Alpha 0.6 released, made a pack of all files like I've done for other releases (450 downloads).
ACME Installer2/Uninstaller
gapps_ics_4.0.3_v11
moboot_0.3.5
UniversalNovacomInstaller
update-cm-9.0.0-RC0-Touchpad-alpha0.6-fullofbugs
update-cwm_tenderloin-1012
Tweaks / (update-lcd_density_120-alpha0.6/update-lcd_density_160-alpha0.6) change screen density between 160 (default) and 120, flash with CWM like normal.
Download
LINK REMOVED
https://rapidshare.com/files/3229394435/CM9-alpha0-6-all-files.zip
i think today is the day i flash this =)
flashed it using recovery, no problems here, all seems to be fine so far.
theronkinator said:
Alpha 0.6 released, made a pack of all files like I've done for other releases (450 downloads).
ACME Installer2/Uninstaller
gapps_ics_4.0.3_v11
moboot_0.3.5
UniversalNovacomInstaller
update-cm-9.0.0-RC0-Touchpad-alpha0.6-fullofbugs
update-cwm_tenderloin-1012
Tweaks / (update-lcd_density_120-alpha0.6/update-lcd_density_160-alpha0.6) change screen density between 160 (default) and 120, flash with CWM like normal.
Download
https://rapidshare.com/files/3229394435/CM9-alpha0-6-all-files.zip
Click to expand...
Click to collapse
If you respect Dalingrin and his work, please edit your post and redirect link for files back to rootzwiki...he had specifically requested this.
qkster said:
If you respect Dalingrin and his work, please edit your post and redirect link for files back to rootzwiki...he had specifically requested this.
Click to expand...
Click to collapse
I would rather NOT have to go through an extra site to get this. I think this kind of post is awesome. No redirect and no having to wade through garbage to find anything. Just a simple zip with everything.
L33t Masta said:
I would rather NOT have to go through an extra site to get this. I think this kind of post is awesome. No redirect and no having to wade through garbage to find anything. Just a simple zip with everything.
Click to expand...
Click to collapse
Its not about that.. its about respecting the wishes of the dev, which clearly the post is not respecting..
L33t Masta said:
I would rather NOT have to go through an extra site to get this. I think this kind of post is awesome. No redirect and no having to wade through garbage to find anything. Just a simple zip with everything.
Click to expand...
Click to collapse
The problem with that is that dalingrin asked specifically that this NOT be done.
It's not exactly theft, but definitely bad form.
And do we really want to alienate the dev's that are coding this for us?
I'm quite thankful for his work, and I'll be happy to give his site the traffic if dalgrin would like it to be that way.
Imagine a coworker of yours swiped everything you did, and handed it to your boss and said, "Look what got accomplished this week!"
It's just not cool.
I'd like to go on record by "ANTI-THANKING" this post, but unfortunately that's not possible.
L33t Masta said:
I would rather NOT have to go through an extra site to get this. I think this kind of post is awesome. No redirect and no having to wade through garbage to find anything. Just a simple zip with everything.
Click to expand...
Click to collapse
We all like direct link, however it is more important that everyone respect Dalingrin's wish.
Sent from my Desire HD
sean is here. said:
The problem with that is that dalingrin asked specifically that this NOT be done.
It's not exactly theft, but definitely bad form.
And do we really want to alienate the dev's that are coding this for us?
I'm quite thankful for his work, and I'll be happy to give his site the traffic if dalgrin would like it to be that way.
Imagine a coworker of yours swiped everything you did, and handed it to your boss and said, "Look what got accomplished this week!"
It's just not cool.
I'd like to go on record by "ANTI-THANKING" this post, but unfortunately that's not possible.
Click to expand...
Click to collapse
We all know who made the update so that's not the issue here. The issue is not having to get redirected to another site that's going to tell us the exact same information. If anything he should post something here on XDA (a much better community that RootzWiki IMO) and have the exact same stuff here. Why make us go to a certain site?
L33t Masta said:
We all know who made the update so that's not the issue here. The issue is not having to get redirected to another site that's going to tell us the exact same information. If anything he should post something here on XDA (a much better community that RootzWiki IMO) and have the exact same stuff here. Why make us go to a certain site?
Click to expand...
Click to collapse
Because it's HIS choice to make. That's called perogative.
What he should post here, because YOU think it's a better forum?!
L33t Masta said:
We all know who made the update so that's not the issue here. The issue is not having to get redirected to another site that's going to tell us the exact same information. If anything he should post something here on XDA (a much better community that RootzWiki IMO) and have the exact same stuff here. Why make us go to a certain site?
Click to expand...
Click to collapse
Hey Masta
It was a request by the developer. A simple request to link to the op of his thread is what is deserved. He wants to keep question and counts as he should. I don't like it when people repost mirrors of my stuff either. These threads aren't needed because many are already out linking back to source files.
Not to mention, without dalingrin and team, we wouldn't have such nice toys. They make ground breaking systems, the least we can do is honor their wishes. Would hate to see source closed up due to people not doing what's asked.
Sent from my PG86100 using Tapatalk
Leoisright said:
Hey Masta
It was a request by the developer. A simple request to link to the op of his thread is what is deserved. He wants to keep question and counts as he should. I don't like it when people repost mirrors of my stuff either. These threads aren't needed because many are already out linking back to source files.
Not to mention, without dalingrin and team, we wouldn't have such nice toys. They make ground breaking systems, the least we can do is honor their wishes. Would hate to see source closed up due to people not doing what's asked.
Sent from my PG86100 using Tapatalk
Click to expand...
Click to collapse
I agree, also to mention that by you distributing a linux kernel and also the gapps, you are violating many other agreements. That's why the other site has links to each GIT or repository and you have to download them seperate. This protects everyone as the source can be verified. If someone were to post a zipped up virus / Trojan / keylogger the end user would never know it. Also it's against XDA rules. I'm not trying to be mean, it's just XDA can be called out and has been called out in the past for distributing GAPPS and Linux Kernel without sighting the source.
Link removed, however it's ok to link to the dev's thread and discuss here. Unless you would also like to link to the source's where members can download and build their own roms. Thanks and I hope everyone understands.
Well I didn't see where he said no mirrors at all. But I know I've had problems with goo.gl or whatever it is in the past. Also I didn't claim it was my own. I'll just carry on helping at other sites instead then. Where the members aren't as technically minded and are constantly asking what they need and can't figure out the mess on rootzwiki, so having just one link helps them all no end.
I'm a new user here. I think a link in the first post in this discussion would be useful. A link to the download at rootzwiki is better than no link at all in my opinion but perhaps I am missing something and the link is actually posted somewhere?
motionpotion said:
I'm a new user here. I think a link in the first post in this discussion would be useful. A link to the download at rootzwiki is better than no link at all in my opinion but perhaps I am missing something and the link is actually posted somewhere?
Click to expand...
Click to collapse
The problem is that Dalingrin (one of the dev's that's been working on this project) has specifically asked that people NOT provide external links to his work. He wants to be able to keep track of how many people DL their stuff and do Q&A, via rootzwiki.
In an effort to not piss the guy off, some people respect his wishes.
thanks!!
Just wanted to say thank you.. good job and keep it up!!
Hello I'm a newb!
I'm sorry, but this is the unfortunate state I find myself in.
When I first found this site, what I was expecting to find was a ICS for my phone. I could not have guessed what I would learn here. I had no idea I had a counter in my phone to worry about when installing open sourced roms? Next after much more reading I am to learn the source code Google releases is not complete, and uses binary drivers? Now I am to learn about CIQ, and my phone is spying on me? Wow!
Before I say anything else I want to express my thanks to this community. This has been such a resource I had no idea that it would be when I started. Thank you!
Now on to my question that after learning about all of that I don't seem to have a clear answer to. What I wanted when I first considered getting an Android phone, was to build from source, and run my own rom. I still want this, even more so since I learned about CIQ.
1. Due to the counter on my phone
2. I am to understand multiple images that make the phone work (boot, firmware, system)
3. The binary drivers.
Is this at all a reasonable goal?
Are there more flash images that I haven't read about yet?
Would having a direct from Google rom even be desirable?
I own a stock SGH-I777, I have done nothing to it yet.
Lastly about this site:
Is there anything you think I should read about on the forums?
Any language I should know, as in what does hellraiser imply/mean?
Any Android experience you think might benefit a could be developer?
Counter can be reset and avoided all together.
Sorry I don't know much about AOSP building, but your better off starting with compiling CM and learn from there unless you are really experienced in coding.
Speaking of, the image used to not increment the counter does, or does not still contain CIQ? I suspect it does? I would like a phone at some point w/o CIQ, and fully open source. Ty for reminding me.
NEME5I5 said:
Speaking of, the image used to not increment the counter does, or does not still contain CIQ? I suspect it does? I would like a phone at some point w/o CIQ, and fully open source.
Click to expand...
Click to collapse
AT&T Galaxy S2 SGH-I777 has never had CIQ.
LiLChris06 said:
AT&T Galaxy S2 SGH-I777 has never had CIQ.
Click to expand...
Click to collapse
I'm shocked AT&T choose not to bug their customers? I assumed since I saw mention of it being on Samsung, that it was on all their phones?
NEME5I5 said:
I'm shocked AT&T choose not to bug their customers? I assumed since I saw mention of it being on Samsung, that it was on all their phones?
Click to expand...
Click to collapse
No it was just some phones, I think the skyrocket had it at some point.
Sent from my SGH-I777 using Tapatalk 2 Beta-5
Ok, so I rooted my first cell phone. It would seem heimdall latest has a bug that will brick your phone. (I'm on Mac OS Lion) I used the 1.3.1 instead, and it worked fine.
I saw many more sites, and this was quite easy. The way they showed it was very complex. Since I'm new at this should I wait to try out a ICS rom till after Samsung releases their source code, and the devs have had a chance to get it stable? How complete is the open source version of ICS? There was a note on the fsf.org page that linked me over here that some of the parts were still binary. Is it still true?
I think long term I want to get away from the official releases.
Well, you came this far, might as well flash an ICS rom now. If the leaks are any indication of status, the Samsung release will be pretty stable but the included kernel is problematic because it can cause hardbricking. Besides, you want to get away from stock, and all of the big roms released thus far are pretty darn stable; I don't know anything about binary parts or any of the coding, but plenty of people have no problem running CM or AOKP. Even the Samsung-based roms all look AOSP-like nowadays because they use Apex or Nova (not many devs like Touchwiz anymore). So take your pick, they're all good roms and most look like AOSP to some extent, with a few (mainly CM and AOKP) striving for pure AOSP.
Make sure to read and follow this guide carefully for flashing stuff, and have fun!
Ok here is where I have a problem. I have no idea about half of what you said? I know AOSP means "Android open source project" by inference of another reply. I even think CWM means "clockwork mod." (don't even know what this is yet) Saw a youtube video that mentioned it.
What is hard bricking, and what should I read to prevent it? I came here for a ICS rom, and it sounds like the two trying to be most open source are my preference.
NEME5I5 said:
Ok here is where I have a problem. I have no idea about half of what you said? I know AOSP means "Android open source project" by inference of another reply. I even think CWM means "clockwork mod." (don't even know what this is yet) Saw a youtube video that mentioned it.
What is hard bricking, and what should I read to prevent it? I came here for a ICS rom, and it sounds like the two trying to be most open source are my preference.
Click to expand...
Click to collapse
Read, read, and read some more. If you don't understand the post above then there is no way you would be able to compile a rom for this phone, which is what I gathered from your op
Sent from my HTC One XL using Tapatalk 2
Yeh. Just give me the new thing! I want that shiny biscuit! Zomg! "Check MY device out. Its got AOKP on it. BAM.". "Oh cool how does that work?". "Pfft who cares. Its shiny!!!"
Sent from my SGH-I777 using xda premium
NEME5I5 said:
Ok here is where I have a problem. I have no idea about half of what you said? I know AOSP means "Android open source project" by inference of another reply. I even think CWM means "clockwork mod." (don't even know what this is yet) Saw a youtube video that mentioned it.
What is hard bricking, and what should I read to prevent it? I came here for a ICS rom, and it sounds like the two trying to be most open source are my preference.
Click to expand...
Click to collapse
Prother, by no mean to offense you, but seriously, if you don't know those fundamental technical terms, I strongly suggest you to hold off what you about to do and spend more time reading.
Let me go off and do a search the post for you, where you can get used to those terms.
Hang tight, prother.
Pirateghost said:
Read, read, and read some more. If you don't understand the post above then there is no way you would be able to compile a rom for this phone, which is what I gathered from your op
Sent from my HTC One XL using Tapatalk 2
Click to expand...
Click to collapse
So I will. To be honest I don't see the connection between the new jargon, and development I learn in school. There is definately much to learn here. I was expecting this to be like Zaurus development from back when I was active, it's very clear to me that this is a very different beast.
Here is one, I'm sure there is other thread.
http://forum.xda-developers.com/showthread.php?t=1466228&highlight=abbreviation
votinh said:
Here is one, I'm sure there is other thread.
http://forum.xda-developers.com/showthread.php?t=1466228&highlight=abbreviation
Click to expand...
Click to collapse
Thank you friend. I may not have my own rom at the end of summer, but I should be on my way to understanding what would be needed for one.
Well the terms I wanted are not present on that list, most of that I was familiar with. To be honest, some of it I have not seen before as well. What is hellraiser, and some of the other xda developed jargon? I do have a tab open to that part of the forums, I just hadn't made it over there yet. I started on the forums for my device, then Android OS, and lastly general. Is there any other place I should pay special attention to that would help me?
Phalanx7621 said:
Yeh. Just give me the new thing! I want that shiny biscuit! Zomg! "Check MY device out. Its got AOKP on it. BAM.". "Oh cool how does that work?". "Pfft who cares. Its shiny!!!"
Sent from my SGH-I777 using xda premium
Click to expand...
Click to collapse
Ok? I'm not sure I understand, is there something you don't like about the aokp rom that doesn't work very well?
I want off of the carrier provided images based on personal conviction. Google's development practices smack of cathedral, as do all of the 3rd party companies. In a sense they are abusing the spirit of free software by using a signed kernel to impede (if not actually prevent) our right to modify hardware we own. Any normal user of the software provided by the community (bazaar) can only help the cause.
I plan to share what I personally learn with close friends who live in my area. The more people we liberate, the better for everyone else. I simply applaud the work done here.
You can safely ignore Phalanx's post, he's just mocking you and other new users for not reading carefully and being stupid. You're at least trying to read and understand stuff, so I don't see any reason you should be put down the way he's doing so.
Here are a couple other links I think you'll find useful (please click my thanks button if you agree!):
ROM vs Kernel
Odex vs Deodex
Make sure to read all of the links posted in the sticky at the top of this forum, too. But note that by no means is this everything you need to read.
Mind you, all this reading is meant mostly for end-users, so that we learn how to safely and smartly modify our phones. Actual original developing beyond using what's already provided by the devs is a whole different story, and I'm sure there's even more to read up on that.
Good luck, happy flashing, and if you plan to develop later down the line, good luck with that too!
karate104 said:
You can safely ignore Phalanx's post, he's just mocking you and other new users for not reading carefully and being stupid. You're at least trying to read and understand stuff, so I don't see any reason you should be put down the way he's doing so.
Here are a couple other links I think you'll find useful (please click my thanks button if you agree!):
ROM vs Kernel
Odex vs Deodex
Make sure to read all of the links posted in the sticky at the top of this forum, too. But note that by no means is this everything you need to read.
Mind you, all this reading is meant mostly for end-users, so that we learn how to safely and smartly modify our phones. Actual original developing beyond using what's already provided by the devs is a whole different story, and I'm sure there's even more to read up on that.
Good luck, happy flashing, and if you plan to develop later down the line, good luck with that too!
Click to expand...
Click to collapse
Ty for all your help. I'm glad you're all so thorough, it was like peeling an onion. The more I was looking at rooting my phone, the more there was to learn. All of you have done an amazing job making this approachable to a brand new user.
Ah I don't assume anymore about what people are trying to say, not everyone is a native english speaker. So I try to be understanding.
Yup I'll be at this for a while, I'm happy to have made some introductions, and maybe some time down the road I can even hope to contribute in some small way.
From a relative noob:
Follow the directions in the " [GUIDE] How to Flash Custom Binaries Without Ever Incrementing the Flash Counter!! " thread. Then pick a rom you want to try and follow the CWM directions ... after that , find a ROM you like. If you don't want to void your warranty, wait for your carrier to provide the closest thing to what you want ... but, I'm happy with my flashed ICS ROM.
NEME5I5 said:
Ty for all your help. I'm glad you're all so thorough, it was like peeling an onion. The more I was looking at rooting my phone, the more there was to learn. All of you have done an amazing job making this approachable to a brand new user.
Ah I don't assume anymore about what people are trying to say, not everyone is a native english speaker. So I try to be understanding.
Yup I'll be at this for a while, I'm happy to have made some introductions, and maybe some time down the road I can even hope to contribute in some small way.
Click to expand...
Click to collapse
Just like everyone else has said. Read read read. Search for answers for your questions before you ask on forums. U will be fine as long as u can read and follow simple directions. Good luck to u. If u haven't flashed a rom yet I would recommend aokp. Awesome rom.
Sent from my SGH-I777 using XDA
Just a few questions I have for you guys over the last couple months I've seen alot of Miui threads openend and ICS opened?
Are you really considered a developer if you just switch a few files from a rom that a actual developer build from source and made it boot on our phone?
Reason I ask because I've talked to a few developers and they tell me that it sucks how porting a miui, ICS rom has become so easy when it took them hours to build from source?
Just want get your guys insight
Not taking shots at no one so don't start crying about it and tell me it took you hours when there are threads everywhere on how to port these.
Sent from my MB855 using xda premium
None of my work counts as development so copypasta porting doesn't count. If it does, then what I did with the deblur/debloat script should count as a universal ROM for moto android devices.
I've heard people complain about copy and paste devs for a long time. Had alot of drama over it when I had the epic. Bottom line is it still takes know how. You have to know what and where to copy. And it still takes a lot of time. And some of the best roms I've used were from so called copy and paste devs. As long as they give credit to where it came from. Most devs learn from looking at what someone else has done anyway. Bottom line the more roms and devs the better. I appreciate your work here, but I see nothing good coming from a thread like this. No affense.My 2 cents.
Sent from my MB855 using Tapatalk 2
now I'm in no way crying but,.....what's the deal bud.....we do alot more than copy paste my friend every rom I do gets smali edits, I have to decompile/recompile several jars in different builds **** in gummy I have to edit the entire framework.jar just to get market working.....is it built from source, no, do I work hard on it without a doubt yes, i can't understand why you needed to open a thread to try to debunk my work..... reason I say my work .... I worked on miui, bill does it now, and does a pretty damn good job of it too..and you think its only copy paste getting miui working.....lol....that one is a beast of its own...takes several several changes to get our to just freaking boot.....I'm working on 4 ics based on the photon and 4 for the atrix.......and for both phones requires several edits ..... i mean seriously all we're doing is allowing more choices more options more roms..... I think you have a very wrong idea of what actually is done on these roms.....**** if it were only as easy as copy paste ....don't ya think we'd have had more of these roms sooner and made by different people, only reason miui got here is yepitsme gave up I picked up slack and took of with it then handed her off to bill.....so again I say whats the deal bud....should be happy our aging phone is seeing so much activity....now I do apologize if I have went out of line here but I couldn't help but feel a, little attacked here directly....and by two of the guys I freaking looked up to on here....all I can say is wow I guess I should just close my threads then since porting doesn't count..... and to say don't cry and tell you it took hours cause there are guides............who made the thread in the first place and the purpose of it is?? I'm in no way crying but not going to be called out like this and not respond, which your a very smart guy so I know that you knew exactly what would happen in opening a thread like this....sometimes it does take hours copy/paste you have no clue.....every new cm9 joker puts out we have to flash each lib one at a time to se e which one isn't playing nice,.but thats just copy pasting isn't it, edits to the build prop, updater script.....smali edits to numerous files, jars,apks....but thats just copy paste too I guess.....or maybe its how at times we flash each rom several times and troubleshoot each issue everyone has not just release and say nothing....but thats just pasting too....you really have no clue maybe should read a couple of those guides you are reffering to cause even in them they tell you this isn't all you have to do...**** some of them even say I can only point to what might work not that this guide works for every phone no matter what...
Sent from my MB855 using xda premium
I see points for either side of the coin but a discussion like this will not be good for the Photon forum. To have developers/contributors against themselves is exactly what has happened in other threads and it never ends up a positive for anyone. I feel there is a place for all kinds of work as long as no work is being stolen and credit is being given. It allows for more options and benefits us all. We could all debate this further but I think we know where this would be heading.
RockoDev said:
Just a few questions I have for you guys over the last couple months I've seen alot of Miui threads openend and ICS opened?
Are you really considered a developer if you just switch a few files from a rom that a actual developer build from source and made it boot on our phone?
Reason I ask because I've talked to a few developers and they tell me that it sucks how porting a miui, ICS rom has become so easy when it took them hours to build from source?
Just want get your guys insight
Not taking shots at no one so don't start crying about it and tell me it took you hours when there are threads everywhere on how to port these.
Sent from my MB855 using xda premium
Click to expand...
Click to collapse
Are you really considered a developer is you forget sh and root in a rom?
remember, we arent taking shots.. just wanna know how it took hours and yet forget stuff like that. dont be willing to start a fire if you cant handle the heat.
bottom line is this as far as im concerned, i could give two craps less about miui, or any of the other cm clones. however i think (most of them) they bring something to the table. and give people choices, if the users really thought it was crap they wouldnt use it..
after working with so many prepaid devices and telling the users that if they want stuff done for roms/kernels then they need to find a dev to get the phone, or one of them needs to step up. so to see more and more people on the photon jump up to help is really nice and reminds me of why i loved this community so much (yes even you willysp ;P ).
if someone isnt making the roms then youd have threads of people complaining cuz they wanted them, so more people are happy in the end because they are made as well as offering choices.
i could go into more but as it is this thread is gunna turn enough into a blood bath so ill try to at least keep my part in it as civil as possible
So I can learn?.... Ok. I really do wanna learn but I think they def need to give credit to the originals. But if they don't like something of one ROM and decide they wanna change it and then let others take it for a spin, whose to stop em?
Sent from my Motorola Electrify using XDA
RockoDev said:
Just a few questions I have for you guys over the last couple months I've seen alot of Miui threads openend and ICS opened?
Are you really considered a developer if you just switch a few files from a rom that a actual developer build from source and made it boot on our phone?
Reason I ask because I've talked to a few developers and they tell me that it sucks how porting a miui, ICS rom has become so easy when it took them hours to build from source?
Just want get your guys insight
Not taking shots at no one so don't start crying about it and tell me it took you hours when there are threads everywhere on how to port these.
Sent from my MB855 using xda premium
Click to expand...
Click to collapse
Let me set the record straight:
FIRST AND FOREMOST: I DO NOT CLAIM TO BE A DEVELOPER.
SECOND: MIUI is NOT just cut and paste. If I had SOURCE for it, I would BUILD it SOURCE. As MIUI has NOT released it, I CANNOT do that. I DO PORT it, and I label it as such. But, to act like all I do is cut and paste, you're way off base.
1) I have to edit the framework files just to get it to fully boot with service/data, and the options that the users of my build have grown accustomed to. I have to test libs each time that Joker releases a new CM9, as not all are compatible.
2) I have to test libs with each MIUI release, as they often build with ARM7b, which is NOT compatible with our beloved Tegra 2 processor.
3) I then make 2 versions (Aroma based and CWM flash).
4) I credit everyone whose work I used to do what I do. That being said, if I port something, you're darn right I should get credit for the work I do.
5) The reson SO MANY (2) MIUI threads have popped up is that Spleef initially started the ports. At a point in late March, I took over doing the ports and he took to other roms. I have been asked recently by MIUI.us to start a separate thread so that I can keep the OP up to date and standardize it to the format that they wanted.
Now, on to my other CONTRIBUTIONS:
1) Fixes thread-yes, may be slightly out of date, but it's helped a LOT of people
2) How-tos thread-sure...I need to add more to it and plan to when I get the time.
3) Anyone here like Kitchen Sink? I ask as Joker and I have spent HOURS working together on that rom getting it to where it is. Not to mention if you use version 2.11, then you're using something I assembled, as it was done while Joker was on away on Vacation.
4) I am usually found on ALL the Photon/Atrix threads helping people with their issues ranging from flashing issues to data issues, etc.
5) Check out how many ROMs I've helped on.
Another thing, I don't have the title Developer...and didn't apply for it. I am a Contributor. I CAREFULLY examined the criteria for each and decided that I would apply for being a Contributor as I DON'T at this time do SOURCE work.
Funny how someone who isn't doing source either would put "dev" in their name when they don't seem to have a single source-built item to their credit, then have a problem with what I do.
Funny that I count there are 3 Rocko-rom variants 2.3.5 posted. See me starting a thread to ask why you have so many Blur based roms?
I would personally LOVE to have the opportunity to talk to ANY of the DEVS you cite as having an issue with the fact that I port MIUI.
moparfreak426 said:
So I can learn?.... Ok. I really do wanna learn but I think they def need to give credit to the originals. But if they don't like something of one ROM and decide they wanna change it and then let others take it for a spin, whose to stop em?
Sent from my Motorola Electrify using XDA
Click to expand...
Click to collapse
your absolutely right anyone can do this it just takes some patience and a little knowledge....we give credit, thanks, and links to every rom we port over..... I'm guilty of forgetting things in roms. I know I am, sometimes things get forgotten or ill use the wrong damn file...lol.....I'm not taking shots or trying to start no crap but I woke up this morning to this thread and couldn't believe what I was reading.... I mean hell rocko rom was jokers originally and look at it now, we all start some where, true I don't do source right now.......but thats not to say I never will I've had joker trying to teach me for a while now but we live our lives so time is short
Sent from my MB855 using xda premium
shabbypenguin said:
Are you really considered a developer is you forget sh and root in a rom?
)
Click to expand...
Click to collapse
Not sure who did that...we had an issue with SU in MIUI on one build due to incompatibility with MIUI and the 0.6.whatever SU xbin
Th3Bill; said:
Funny how someone who isn't doing source either would put "dev" in their name when they don't seem to have a single source-built item to their credit, then have a problem with what I do.
Funny that I count there are 3 Rocko-rom variants 2.3.5 posted. See me starting a thread to ask why you have so many Blur based roms?
Click to expand...
Click to collapse
I'm not trying to pick any sides in this because I like both of your work, but damn he got you.
Sent from my MB855 using XDA
shabbypenguin said:
......reminds me of why i loved this community so much (yes even you willysp ;P )........
Click to expand...
Click to collapse
Why in the world are you taking a shot at me in this thread?
I think, this thread is something, that shouldn't be here. It's all about choices. I don't like the ROMs of all devs here, so I made my own. But I am still glad they are here. And I appreciate their work.
Think I saw in the new evo thread that Rocko is heading there. Maybe triing to stir the pot before he leaves? Personaly I would like to see this thread closed.
Sent from my MB855 using Tapatalk 2
bricky23 said:
Think I saw in the new evo thread that Rocko is heading there. Maybe triing to stir the pot before he leaves? Personaly I would like to see this thread closed.
Sent from my MB855 using Tapatalk 2
Click to expand...
Click to collapse
AMEN!
A developer is anyone who developed something for Android. Themes, roms, hacks, root methods, modifications, even scripts. Just because someone doesn't build from source doesn't mean they don't bring something to the community.
Sent from my MB855 using XDA
willysp said:
Why in the world are you taking a shot at me in this thread?
Click to expand...
Click to collapse
lol was just poking fun at ya man hence the
jokersax11 said:
A developer is anyone who developed something for Android. Themes, roms, hacks, root methods, modifications, even scripts. Just because someone doesn't build from source doesn't mean they don't bring something to the community.
Sent from my MB855 using XDA
Click to expand...
Click to collapse
Can I get an AMEN
Sent from my CM9 beast
shabbypenguin said:
Are you really considered a developer is you forget sh and root in a rom?
remember, we arent taking shots.. just wanna know how it took hours and yet forget stuff like that. dont be willing to start a fire if you cant handle the heat.
bottom line is this as far as im concerned, i could give two craps less about miui, or any of the other cm clones. however i think (most of them) they bring something to the table. and give people choices, if the users really thought it was crap they wouldnt use it..
after working with so many prepaid devices and telling the users that if they want stuff done for roms/kernels then they need to find a dev to get the phone, or one of them needs to step up. so to see more and more people on the photon jump up to help is really nice and reminds me of why i loved this community so much (yes even you willysp ;P ).
if someone isnt making the roms then youd have threads of people complaining cuz they wanted them, so more people are happy in the end because they are made as well as offering choices.
i could go into more but as it is this thread is gunna turn enough into a blood bath so ill try to at least keep my part in it as civil as possible
Click to expand...
Click to collapse
No!!!!! I am not have never claimed to be.....
Sent from my MB855 using xda premium
To those that may be offended by my position let me clarify. I was on the Evo for the first price drop. A ton of ROMs suddenly appeared that were no more than a font or color change by folks claiming to be devs. To me, simple edits like that are not development or ROMs. I've seen the same with themes, swap a font and call yourself a dev. There are script releases by "devs" that all that was done was change the device name or partition location. To me none of that stuff counts as honest development.
Another example is ROMs from the JoyOS port guides. Copypasta and a couple build.prop edits and look you have JoyOS. That in itself is not development to me. Now if you have to go through and do framework/smali edits to get it to work, that's a whole different story. That requires know how, skill and time.
spleef, Th3Bill and others, I'm sorry if you took my previous post personally. I consider you guys a dev and your work is well beyond anything I have released. Digging around in the code to get things to work is not easy. There are many with contributor titles really should read developer. (again, in thinking about it I really am not one of them). I was also speaking about android as a whole and not specifically the photon forum.
jokersax11 said:
A developer is anyone who developed something for Android. Themes, roms, hacks, root methods, modifications, even scripts. Just because someone doesn't build from source doesn't mean they don't bring something to the community.
Click to expand...
Click to collapse
I can't speak for others but I agree with you on this only to a point. It goes back to the first paragraph in this post. To me, a font change or other very minor changes isn't development. I'm speaking in general however. When it comes to the Photon specifically, there's a lot of actual deving being done and folks that are very deserving of dev status (again, I am not placing myself in that category).
To All,
A lot of crap has happened to me personally over the past couple months. My attitude is lousy at best and I think it time I walk away for awhile. If I have offended I am sorry. Feel free to grab any of my work and run with it. I also have the following unfinished projects up for grabs;
2.3.5 sudo-Blur ROM with root ODEXed and De-ODEXed built straight from the 2.3.5 leak. (USB is intermittent but not sure if its the phone or the ROM)
webtop+ 2.3.5 leak (missing apps)
Copypasta JoyOS port (never connects to service)
This thread will be more like an advanced user/development "bible", to help keep the threads I am linking to clean, and to put all the information in one place. This information will also be put in the advanced section of the amaze bible doc, and also the WIKI we are working on.. I want to make sure anyone who wants this information has NO problem finding it!
I've seen a lot of people who have been making comments about "wanting to learn" at the same time that I am seeing the developers/contributors in these forums start offering "how-to's" for some of the more advanced functions.. I've also seen some comments from users who have not made any significant/consistent contributions - the secret they may not be aware of, if you can successfully read and understand enough to do the stuff we do in these forums, then YOU can take that to a new level.. and offer something back.
I will update this thread with some of the different threads/tutorials that already exist, and I would like to see people give feedback on the types of information that might be useful.. instead of just propositioning people who already develop, who may be busy with other things - let's crowd source some of our own development, after all, we all started somewhere..
Everything here, and all those how-to threads will be added to the amaze wiki - which will eventually replace the current always up to date amaze bible(doc)(which we need help updating btw, anyone on XDA can help contribute by helping do THAT here). HINT: ANYONE can help contribute to our knowledge base in the wiki! Please do! Before you give negative feedback to any dev, I want you to ask yourself - what have I contributed?
First, the bible I already posted some Advanced Android 101: So you wanna go to the next level?
If maybe building from source isn't your thing, you could look in the Everything Development Thread which has an ongoing discussion about how to COOK(or customize) a rom, a good first step toward conquering bigger and better things.. if you want to give this a go, read that thread, ask good questions, and help us create a solid starting point for future developers!
Next, with the recent release of the source for the ICS kernel, there has been a lot of interest in getting that running - Here you can learn how to Build Your Own Kernel, and then you can easily find posts by several devs working on getting these kernels fully working.. currently the issue is getting WIFI working(which we knew might be an issue), but THIS is something that users can help figure out..
If you can setup the build environment for building your own kernel, then you can ALSO [TUTORIAL]How to compile CM9 for the Amaze 4G - if you can learn how to do this, you will learn the right questions to ask to research how you may contribute to the project..
This post I have posted many useful links to different guides for porting - no one guide is going to be perfect, but if you read them and try them out.. you will learn a TON, and maybe even have a successful port! Remember, porting heavy framework changes like AOSP, sense4, aokp, etc - some of it is kernel dependent and will require more than any guide can spell out.. trial and error my friends.
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Are there any more development/advanced tutorials in the amaze forums I missed? Any in any other forums you have seen that are well written? Any questions you have about something not covered can be asked here, but please post in the relevant thread if your question relates to it! I would really like this thread to be more for feedback about what we can help YOU do, so if you have any suggestions/questions regarding how we can help you do that, please post!
This post will have some of the related but not easily categorized, random information I find in the future..
Man I really want to start but my computer is way to sluggish
Sent from my HTC_Amaze_4G using Xparent Green Tapatalk 2
eggydrums said:
Man I really want to start but my computer is way to sluggish
Sent from my HTC_Amaze_4G using Xparent Green Tapatalk 2
Click to expand...
Click to collapse
Well, compiling is processor intensive, even if the computer is sluggish, a semi-decent processor and a fair amount of ram do all of the work once you finish.. and there is stuff in the bible for customizing themes and more under Advanced Android 101: So you wanna go to the next level? Then there's the Everything Development Thread, that doesn't require a powerful computer at all, you're just switching out files before flashing.. and I am going to start posting some of the stuff I've learned in there soon too!
If you have anything you'd like to see, or anything you might have to offer.. feel free to post it
http://forum.xda-developers.com/showthread.php?p=28647619
Would this help? Found it in One S forum... but idk jack about developing (way to much work for too little result) so idk if it helps
Sent from my HTC One S using xda premium
glacierguy said:
http://forum.xda-developers.com/showthread.php?p=28647619
Would this help? Found it in One S forum... but idk jack about developing (way to much work for too little result) so idk if it helps
Sent from my HTC One S using xda premium
Click to expand...
Click to collapse
You mean the video it links to? That is all I got in the xda app.. if the video has anything new it could be added to the everything development thread, they were working on instructions there for using dsixda kitchen..
Sent from my HTC_Amaze_4G using xda app-developers app
I just want to learn to develop rom so that I can contribute to this amazing sight. I asked in the g 2 forums and not once did I ever get any help. Super savvy with computers modding well at least flashing that is haha. But I know with a little guidance I can be a big contribution to the site. So any words of advice would be great and some links to guides will be even more great haha. Thank you so much in advance
Sent from my HTC_Amaze_4G using xda premium
Spastic909 said:
I just want to learn to develop rom so that I can contribute to this amazing sight. I asked in the g 2 forums and not once did I ever get any help. Super savvy with computers modding well at least flashing that is haha. But I know with a little guidance I can be a big contribution to the site. So any words of advice would be great and some links to guides will be even more great haha. Thank you so much in advance
Sent from my HTC_Amaze_4G using xda premium
Click to expand...
Click to collapse
Well, first, go into different roms, and look at their changelog - see if you can figure out what they are changing - don't just look at the roms in these forums.. look in other forums too. Download a rom, look at the updater-script to see if there is anything there that is making the change in that you saw in the changelog.. look at the files the updater script specifically sets permissions for(if it does), as those files are usually modified, hence why they have to set permisions.. look at the /system/etc folder.
Get a program like winmerge(I think that is what it is), or filemerge for mac, or some other program that will compare files AND directories line by line.. compare a stock rom to a modified rom- as long as it compares directories too, it will output which files the stock rom didn't have, which have been changed, what has been changed- THIS is the easiest way to figure it out for yourself. Piece by piece.
For example, right now I am trying to figure out why the custom kernel here isn't changing my clock speed - if I unpack the zip file, I see he has replaced the init.qcom.post_boot.sh file, and if I compare that with the stock rom, or the energy rom I am using, I see he commented out the lines that change the frequency.. so I look at the updater script, the aroma_config file, and each file tells me what it is doing.. I see the badass.sh file creates a file called 89badass in the init.d folder.. part by part you can figure out exactly what he was doing, how he was making the changes.
There is no real "guide" that is going to help as much as finding a way to figure it out for yourself.. programs like filemerge and winmerge are free and easy to find, and DEFINITELY give you a good place to start. Technically making your own rom is just making changes to a stock rom until you are actually reCODING something - but those changes can be pretty huge and technical, and do awesome things.. you just got to figure out what they are, and how to do them.
Everything above should give you a good place to start..
Silentbtdeadly said:
Well, first, go into different roms, and look at their changelog - see if you can figure out what they are changing - don't just look at the roms in these forums.. look in other forums too. Download a rom, look at the updater-script to see if there is anything there that is making the change in that you saw in the changelog.. look at the files the updater script specifically sets permissions for(if it does), as those files are usually modified, hence why they have to set permisions.. look at the /system/etc folder.
Get a program like winmerge(I think that is what it is), or filemerge for mac, or some other program that will compare files AND directories line by line.. compare a stock rom to a modified rom- as long as it compares directories too, it will output which files the stock rom didn't have, which have been changed, what has been changed- THIS is the easiest way to figure it out for yourself. Piece by piece.
For example, right now I am trying to figure out why the custom kernel here isn't changing my clock speed - if I unpack the zip file, I see he has replaced the init.qcom.post_boot.sh file, and if I compare that with the stock rom, or the energy rom I am using, I see he commented out the lines that change the frequency.. so I look at the updater script, the aroma_config file, and each file tells me what it is doing.. I see the badass.sh file creates a file called 89badass in the init.d folder.. part by part you can figure out exactly what he was doing, how he was making the changes.
There is no real "guide" that is going to help as much as finding a way to figure it out for yourself.. programs like filemerge and winmerge are free and easy to find, and DEFINITELY give you a good place to start. Technically making your own rom is just making changes to a stock rom until you are actually reCODING something - but those changes can be pretty huge and technical, and do awesome things.. you just got to figure out what they are, and how to do them.
Everything above should give you a good place to start..
Click to expand...
Click to collapse
I'm gonna start trying to figure this out before my first android I was totally computer retarded my parents died when I was 14 and I had to quit school and start working so at 32 yrs old now this is pretty tough so thank you for trying to help folks like me learn and keep up with all this new technology. I think I'm starting to get it a little reading goes a long way.
sent from one badass htc amaze with ics [email protected]
eggydrums said:
Man I really want to start but my computer is way to sluggish
Sent from my HTC_Amaze_4G using Xparent Green Tapatalk 2
Click to expand...
Click to collapse
i build kernels on an old laptop with a intel centrino duo, 512mb of ram, and ubuntu 10.04. if yours beats that, you will be fine (takes me 5 mins to build kernels)
ziggy46 said:
i build kernels on an old laptop with a intel centrino duo, 512mb of ram, and ubuntu 10.04. if yours beats that, you will be fine (takes me 5 mins to build kernels)
Click to expand...
Click to collapse
I assume ir runs windows xp?
Sent from my HTC_Amaze_4G using Tapatalk 2
EclipzeRemix said:
I assume ir runs windows xp?
Sent from my HTC_Amaze_4G using Tapatalk 2
Click to expand...
Click to collapse
yup, and it has a sticker that says windows vista capable. WHICH IS A LIE!!!!
i got the laptop for free though. its a compaq presario v3016us. i think some ram was taken out of it before i got it. (im gonna buy 2gb soon)
quick question. How do I check the change log or is there a link to it or so I can use I think that's what I'm asking!
Sent from my HTC_Amaze_4G using xda premium